ALD Management(SRAN9.0 02)

8/10/2019 ALD Management(SRAN9.0 02)

1/211

SingleRAN

ALD Management Feature Parameter Description

Issue 02

Date 2014-06-30

HUAWEI TECHNOLOGIES CO., LTD.


2/211


3/211

Contents

1 About T his Document..................................................................................................................11.1 Scope....... .......................................................................................................................................................................1

1.2 Intended Audience..........................................................................................................................................................2

1.3 Change H istory...............................................................................................................................................................2

1.4 Difference s Between Base Station Types.......................................................................................................................3

2 Overvie w.........................................................................................................................................42.1 Introducti on....................................................................................................................................................................4

2.2 RET Ante nna................................................................................................................................................................12

2.3 TMA....... ......................................................................................................................................................................13

2.4 SASU...... ......................................................................................................................................................................14

2.5 AAS Mod ule.................................................................................................................................................................14

2.5.1 Overvie w...................................................................................................................................................................14

2.5.2 AAS M odules with Passive Antennas.......................................................................................................................14

3 ALD De vice Data Configuration..............................................................................................16

4 ALD Ma nagement Functions....................................................................................................174.1 RET Ante nna Functions...............................................................................................................................................17

4.1.1 Connect ions Between RET Antennas and RRUs/RFUs............................................................................................17

4.1.2 Operatio ns on RET Antennas....................................................................................................................................26

4.2 TMA Fun ctions.............................................................................................................................................................28

4.2.1 Connect ions Between the TMA, RRU/RFU, and RET Antenna..............................................................................28

4.2.2 Operatio ns on the TMA.............................................................................................................................................34

4.3 SASU Fu nctions...........................................................................................................................................................35

4.3.1 Connect ions Between the SASU, RRU/RFU, and RET Antenna.............................................................................35

4.3.2 Operatio ns on the SASU............................................................................................................................................37

4.4 AAS Func tions.............................................................................................................................................................38

4.4.1 Connect ions Between the AAS Module with Passive Antennas, RRU/RFU, and BBU...........................................38

4.4.2 Operatio ns on AAS Modules.....................................................................................................................................41

5 Related Features...........................................................................................................................43

6 Impact on the Network...............................................................................................................44

7 Engineering Guidelines (ALD Manual Deployment on Multimode Base Station).......45

SingleRANALD Management Feature Parameter Description Contents

Issue 02 (2014-06-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

ii


4/211

7.1 When to Use ALD Management..................................................................................................................................45

7.2 Required Information...................................................................................................................................................45

7.3 Planning........................................................................................................................................................................45

7.4 Deployment..................................................................................................................................................................45

7.4.1 Requirements.............................................................................................................................................................45

7.4.2 Overall Process (RETs/TMAs/SASUs).....................................................................................................................46

7.4.3 Overall Process (AAS Modules)...............................................................................................................................49

7.4.4 Data Pre paration........................................................................................................................................................49

7.4.5 Initial C onfiguration..................................................................................................................................................50

7.4.6 Commis sioning..........................................................................................................................................................51

7.4.7 Activati on Observation..............................................................................................................................................52

7.4.8 Deactiva tion...............................................................................................................................................................52

7.4.9 Reconfi guration.........................................................................................................................................................52

7.5 Performan ce Monitoring...............................................................................................................................................53

7.6 Parameter Optimization................................................................................................................................................53

7.7 Troubleshooting............................................................................................................................................................53

8 Engineer ing Guidelines (ALD Manual Deployment on eGBTS/NodeB/eNodeB Side)............................................................................................................................................................548.1 When to U se ALD Management..................................................................................................................................54

8.2 Required I nformation...................................................................................................................................................54

8.3 Planning.. ......................................................................................................................................................................54

8.4 Deployme nt..................................................................................................................................................................54

8.4.1 Require ments.............................................................................................................................................................54


8.4.3 Precauti ons.................................................................................................................................................................76

8.4.4 Initial C onfiguration on the GUI...............................................................................................................................79

8.4.5 Initial C onfiguration on a Single Base Station Using MML Commands..................................................................80

8.4.6 Commis sioning..........................................................................................................................................................85

8.4.7 Activati on Observation..............................................................................................................................................85

8.4.8 Deactiva tion...............................................................................................................................................................86

8.4.9 Reconfiguration.........................................................................................................................................................86

8.5 Performance Monitoring...............................................................................................................................................88

8.6 Parameter Optimization................................................................................................................................................88

8.7 Troublesh ooting............................................................................................................................................................88

9 Engineer ing Guidelines (ALD Manual Deployment on GBTS Side)...............................899.1 When to U se ALD Management..................................................................................................................................89

9.2 Required I nformation...................................................................................................................................................89

9.3 Planning.. ......................................................................................................................................................................89

9.4 Deployme nt..................................................................................................................................................................89

9.4.1 Require ments.............................................................................................................................................................89




iii


5/211

9.4.3 Precautions...............................................................................................................................................................108

9.4.4 Initial Configuration on the GUI.............................................................................................................................109

9.4.5 Initial Configuration on a Single Base Station Using MML Commands................................................................110

9.4.6 Commissioning........................................................................................................................................................113

9.4.7 Activation Observation............................................................................................................................................113

9.4.8 Deactivation.............................................................................................................................................................113

9.4.9 Reconfiguration.......................................................................................................................................................113

9.5 Performance Monitoring.............................................................................................................................................114

9.6 Parameter Optimization..............................................................................................................................................114

9.7 Troubleshooting..........................................................................................................................................................115

10 Engineering Guidelines (ALD Automatic Deployment).................................................11610.1 When to Use ALD Automatic Deployment.............................................................................................................116

10.2 Required Information...............................................................................................................................................11610.3 Planning....................................................................................................................................................................116

10.4 Deploym ent..............................................................................................................................................................116

10.4.1 Proces s...................................................................................................................................................................117

10.4.2 Requir ements.........................................................................................................................................................117

10.4.3 Data P reparation....................................................................................................................................................118

10.4.4 Creatin g an ALD Automatic Deployment Task....................................................................................................122

10.4.5 Initial Configuration..............................................................................................................................................124

10.4.6 Comm issioning......................................................................................................................................................127

10.4.7 Activat ion Observation..........................................................................................................................................12710.4.8 Checki ng that ALD Automatic Deployment Is Complete.....................................................................................128

10.4.9 Deacti vation...........................................................................................................................................................128

10.4.10 Recon figuration...................................................................................................................................................130

10.5 Performa nce Monitoring...........................................................................................................................................131

10.6 Paramete r Optimization............................................................................................................................................131

10.7 Troubles hooting........................................................................................................................................................132

10.8 Appendi x: ALD Automatic Configuration Process..................................................................................................133

11 Parame ters.................................................................................................................................151

12 Counte rs....................................................................................................................................204

13 Glossar y.....................................................................................................................................205

14 Referen ce Documents.............................................................................................................206



iv


6/211

1 About This Document1.1 Scope

This document describes antenna line device (ALD) management and provides engineeringguidelines. ALD management involves two GSM basic features, three UMTS basic features,and one LTE optional feature, as listed in Table 1-1 .

Table 1-1 Features related to ALD management

Mode Feature ID Feature Name

GSM MRFD-210601 Connection with TMA (Tower MountedAmplifier)

MRFD-210602 Remote Electrical Tilt

UMTS MRFD-210601 Connection with TMA (Tower MountedAmplifier)

MRFD-210602 Remote Electrical Tilt

WRFD-060003 Same Band Antenna Sharing Unit (900 MHz)

LTE FDD LOFD-001024 Remote Electrical Tilt Control

LTE TDD TDLOFD-001024 Remote Electrical Tilt Control

This document applies to macro base stations (BTS3900, BTS3900L, BTS3900A, BTS3900AL,BTS3900C, and DBS3900) and LampSite base stations.

Any managed objects (MOs), parameters, alarms, or counters described below correspond tothe software release delivered with this document. Any future updates will be described in the

product documentation delivered with the latest software release.

In this document, the following naming conventions apply for LTE terms.

SingleRANALD Management Feature Parameter Description 1 About This Document


1


7/211

Includes FDD and TDD Includes FDD Only Includes TDD Only

LTE LTE FDD LTE TDD

eNodeB LTE FDD eNodeB LTE TDD eNodeB

In addition, the "G", "U", "L", and "T" in RAT acronyms refer to GSM, UMTS, LTE FDD andLTE TDD, respectively.

1.2 Intended AudienceThis document is intended for personnel who:

l Need to understand the features described hereinl Work with Huawei products

1.3 Change HistoryThis section provides information about the changes in different document versions.

There are two types of changes, which are defined as follows:

l Feature change

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

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

SRAN9.0 02 (2014-06-30)

Compared with Issue 01 (2014-04-21), Issue 02 (2014-06-30) includes the following changes.

Change Type Change Description Parameter Change

Feature change None None

Editorial change Optimized the description aboutthe AAS module with passiveantennas to prevent incorrectconfiguration.

None

SRAN9.0 01 (2014-04-21)

This issue does not include any changes.



2


8/211

SRAN9.0 Draft B (2014-02-28)

Compared with Issue Draft A (2014-01-20), Draft B (2014-02-28) includes the followingchanges.

Change Type Change Description ParameterChange

Feature change None None

Editorial change Added a description of how to choose the methodof configuring ALD device data. For details, seesections 3 ALD Device Data Configuration .

None

SRAN9.0 Draft A (2014-01-20)Compared with Issue 03 (2013-12-23) of SRAN8.0, Draft A (2014-01-20) of SRAN9.0 includesthe following changes.

Change Type Change Description ParameterChange

Feature change Added a description of ALD automaticdeployment. For details, see sections 10Engineering Guidelines (ALD AutomaticDeployment) .

Added descriptions of running the DSPBTSRETSUBUNIT (GBTS) or

DSP RETSUBUNIT (eGBTS/NodeB/eNodeB)command to query the name of the last loadedconfiguration file and the load time in section4.1.2 Operations on RET Antennas .

None

Editorial change None None

1.4 Differences Between Base Station TypesThe features described in this document are implemented in the same way on macro base stationsand LampSite base stations.



3


9/211

2 Overview2.1 Introduction

ALD is a generic term for antenna devices, such as the remote electrical tilt (RET) antenna,tower-mounted amplifier (TMA), same-band antenna sharing unit (SASU), and active antennasystem (AAS) module. Currently, a maximum of six ALDs can be cascaded on a control portof a remote radio unit (RRU)/radio frequency unit (RFU) to enable the RET function, and thenumber of each type of ALD varies in different application scenarios.

Table 2-1 lists the capabilities of GSM, UMTS, LTE FDD, and LTE TDD radio accesstechnology (RAT) systems to configure and manage different types of ALDs. Table legend: Yes:supported; No: not supported.

Table 2-1 Capabilities of GSM, UMTS, and LTE RAT systems to configure and managedifferent types of ALDs

RAT System RET TMA SASU AAS

GSM Yes Yes No Yes

UMTS Yes Yes Yes Yes

LTE FDD Yes Yes No Yes

LTE TDD Yes No No No

NOTE

The RET cannot be used when a 4T4R RRU serves as two 2T2R RRUs in LTE TDD mode.

Table 2-2 , Table 2-3 , Table 2-4 and Table 2-5 list the capabilities of RF modules to supportdifferent types of ALDs.

Table legend: Yes: supported; No: not supported; /: N/A

If an RF port does not support RET antennas, control signals cannot be transmitted or receivedon this RF port.

SingleRANALD Management Feature Parameter Description 2 Overview


4


10/211

Table 2-2 Capabilities of ports on RF modules with two RF ports to support different types of ALDs

RFModule

RATSystem

RET(ANT_ A Port)

TMA(ANT_ A Port)

RET(ANT_ B Port)

TMA(ANT_ B Port)

RET(RETPort)

TMA(RETPort)

DRFU GSM No No No No / /

GRFU GSM Yes Yes No Yes / /

RRU3004

GSM No No No No Yes No

RRU3008

GSM Yes Yes No Yes Yes No

WRFU UMTS Yes Yes No Yes / /

WRFUa UMTS Yes Yes No Yes / /

WRFUd UMTS Yes Yes No Yes / /

WRFUe UMTS Yes Yes No Yes / /

RRU3801E

UMTS Yes Yes No Yes Yes No

RRU3804


RRU3805


RRU3806


RRU3824


RRU3826


RRU3828


RRU3829


RRU3838


RRU3839


CRFUd LTEFDD

Yes Yes No Yes / /



5


11/211

RFModule

RATSystem

RET(ANT_ A Port)

TMA(ANT_ A Port)

RET(ANT_ B Port)

TMA(ANT_ B Port)

RET(RETPort)

TMA(RETPort)

CRFUe LTEFDD Yes Yes No Yes / /

LRFU LTEFDD

Yes Yes No Yes / /

LRFUe LTEFDD

Yes Yes No Yes / /

RRU3201

LTEFDD

Yes Yes No Yes Yes No

RRU320

3

LTE

FDD


RRU3220

LTEFDD

No No No No Yes No

RRU3221

LTEFDD


RRU3222

LTEFDD


RRU3229

LTEFDD


RRU3268

LTEFDD


RRU3628

LTEFDD


RRU3638

LTEFDD


RRU3808

UMTS,LTEFDD, UL


MRFU GSM,UMTS,LTEFDD,GU, GL

Yes Yes No Yes / /

MRFUd GSM,UMTS,LTEFDD,GU, GL

Yes Yes No Yes / /



6


12/211

RFModule

RATSystem

RET(ANT_ A Port)

TMA(ANT_ A Port)

RET(ANT_ B Port)

TMA(ANT_ B Port)

RET(RETPort)

TMA(RETPort)

MRFUe GSM,UMTS,LTEFDD,GU, GL

Yes Yes No Yes / /

RRU3908

GSM,UMTS,LTEFDD,GU, GL


RRU3926 GSM,UMTS,LTEFDD,GU, GL


RRU3928



RRU3929



RRU3936

GSM,UMTS,LTEFDD,GU, GL,UL


RRU3938



RRU3939

GSM,LTEFDD, GL




7


13/211

RFModule

RATSystem

RET(ANT_ A Port)

TMA(ANT_ A Port)

RET(ANT_ B Port)

TMA(ANT_ B Port)

RET(RETPort)

TMA(RETPort)

RRU3961 GSM,UMTS,LTEFDD,GU, GL,UL, GUL

Yes Yes Yes Yes Yes No

RRU3251

LTETDD

Yes No No No Yes No

Table 2-3 Capabilities of ports on RF modules with four RF ports to support different types of ALDs

RFModule

RATSystem

RET(ANT_APort)

TMA(ANT_APort)

RET(ANT_BPort)

TMA(ANT_BPort)

RET(ANT_CPort)

TMA(ANT_CPort)

RET(ANT_ DPort)

TMA(ANT_DPort)

RET(RETPort)

TMA(RETPort)

RRU3

240

LTE

FDD

Yes Yes No Yes No Yes No Yes Yes No

RRU3260

LTEFDD


RRU3632

LTEFDD


RRU3642

LTEFDD


RRU3841

LTEFDD

Yes Yes Yes Yes No Yes No Yes Yes No

RRU3262

LTEFDD


RRU3832

UMTS,LTEFDD,UL




8


14/211

RFModule

RATSystem

RET(ANT_A

Port)

TMA(ANT_A

Port)

RET(ANT_B

Port)

TMA(ANT_B

Port)

RET(ANT_C

Port)

TMA(ANT_C

Port)

RET(ANT_

DPort)

TMA(ANT_D

Port)

RET(RET

Port)

TMA(RET

Port)

RRU3942

GSM,UMTS,LTEFDD,GU,GL,UL


RRU3232

LTETDD

Yes No No No No No No No Yes No

RRU3235

LTETDD


RRU3252

LTETDD


RRU3256

LTETDD


RRU3702

LTETDD


Table 2-4 Capabilities of ports on RF modules with six RF ports to support RETs

RFModule

RATSystem

ANT_0Port

ANT_1Port

ANT_2Port

ANT_3Port

ANT_4Port

ANT_5Port

pRRU UMTS,LTEFDD, UL

No No No No No No

Table 2-5 Capabilities of ports on RF modules with eight RF ports to support RETs

RFModule

RATSystem

ANT_1Port

ANT_2Port

ANT_3Port

ANT_4Port

ANT_5Port

ANT_6Port

ANT_7Port

ANT_8Port

CALPort

RETPort

RRU3253

LTETDD

No No No No No No No No Yes Yes



9


15/211

RFModule

RATSystem

ANT_1Port

ANT_2Port

ANT_3Port

ANT_4Port

ANT_5Port

ANT_6Port

ANT_7Port

ANT_8Port

CALPort

RETPort

RRU3259 LTETDD No No No No No No No No Yes Yes

Table 2-6 lists the capabilities of RF modules to support RET antennas.

Table 2-6 Capabilities of RF modules to support RET antennas

RF Module RAT System AISGProtocolSupported

RET AntennaVoltage

RET AntennaCurrent

DRFU GSM 1.1 12 V 2.3 A

GRFU GSM 1.1/2.0 12 V 2.3 A

RRU3004 GSM 1.1 12 V 2.3 A

RRU3008 GSM 1.1/2.0 12 V 2.3 A

WRFU UMTS 1.1/2.0 12 V 2.3 A

WRFUa UMTS 1.1/2.0 12 V 2.3 A

WRFUd UMTS 1.1/2.0 12 V 2.3 AWRFUe UMTS 1.1/2.0 12 V 2.3 A

RRU3801E UMTS 1.1 12 V 2.3 A

RRU3804 UMTS 1.1/2.0 12 V 2.3 A

RRU3805 UMTS 1.1/2.0 12 V 2.3 A

RRU3806 UMTS 1.1/2.0 12 V 2.3 A

RRU3824 UMTS 1.1/2.0 12 V 2.3 A

RRU3826 UMTS 1.1/2.0 12 V 2.3 A

RRU3828 UMTS 1.1/2.0 12 V 2.3 A

RRU3829 UMTS 1.1/2.0 12 V 2.3 A

RRU3838 UMTS 1.1/2.0 12 V 2.3 A

RRU3839 UMTS 1.1/2.0 12 V 2.3 A

CRFUd LTE FDD 1.1/2.0 12 V 2.3 A

CRFUe LTE FDD 1.1/2.0 12 V 2.3 A

LRFU LTE FDD 1.1/2.0 12 V 2.3 A



10


16/211


RET AntennaVoltage

RET AntennaCurrent

LRFUe LTE FDD 1.1/2.0 12 V 2.3 ARRU3201 LTE FDD 1.1/2.0 12 V 2.3 A

RRU3203 LTE FDD 1.1/2.0 12 V 2.3 A

RRU3220 LTE FDD 1.1/2.0 12 V 2.3 A

RRU3221 LTE FDD 1.1/2.0 12 V 2.3 A

RRU3222 LTE FDD 1.1/2.0 12 V 2.3 A

RRU3229 LTE FDD 1.1/2.0 12 V 2.3 A

RRU3240 LTE FDD 1.1/2.0 12 V 2.3 A

RRU3260 LTE FDD 1.1/2.0 12 V 2.3 A

RRU3268 LTE FDD 1.1/2.0 12 V 2.3 A

RRU3628 LTE FDD 1.1/2.0 12 V 2.3 A

RRU3632 LTE FDD 1.1/2.0 12 V 2.3 A

RRU3638 LTE FDD 1.1/2.0 12 V 2.3 A

RRU3642 LTE FDD 1.1/2.0 12 V 2.3 A

RRU3841 LTE FDD 1.1/2.0 12 V 2.3 A

RRU3262 LTE FDD 1.1/2.0 12 V 2.3 A

RRU3808 UMTS, LTEFDD, UL

1.1/2.0 12 V 2.3 A

RRU3832 UMTS, LTEFDD, UL

1.1/2.0 12 V 2.3 A

MRFU GSM, UMTS,LTE FDD, GU,GL

1.1/2.0 12 V 2.3 A

MRFUd GSM, UMTS,LTE FDD, GU,GL

1.1/2.0 12 V 2.3 A

MRFUe GSM, UMTS,LTE FDD, GU,GL

1.1/2.0 12 V 2.3 A

RRU3908 GSM, UMTS,LTE FDD, GU,GL

1.1/2.0 12 V 2.3 A



11


17/211


RET AntennaVoltage

RET AntennaCurrent


1.1/2.0 12 V 2.3 A


1.1/2.0 12 V 2.3 A


1.1/2.0 12 V 2.3 A

RRU3936 GSM, UMTS,LTE FDD, GU,GL, UL

1.1/2.0 12 V 2.3 A


1.1/2.0 12 V 2.3 A

RRU3939 GSM, LTEFDD, GL

1.1/2.0 12 V 2.3 A

RRU3942 GSM, UMTS,LTE FDD, GU,

GL, UL

1.1/2.0 12 V 2.3 A

RRU3961 GSM, UMTS,LTE FDD, GU,GL, UL, GUL

1.1/2.0 12 V 2.3 A

RRU3702 LTE TDD 1.1/2.0 12 V 2.3 A

RRU3232 LTE TDD 1.1/2.0 24 V/12 V 2.3 A

RRU3252 LTE TDD 1.1/2.0 24 V/12 V 2.3 A

RRU3256 LTE TDD 1.1/2.0 24 V/12 V 2.3 A

RRU3235 LTE TDD 1.1/2.0 12 V 2.3 A

RRU3253 LTE TDD 1.1/2.0 24 V/12 V 2.3 A

RRU3251 LTE TDD 1.1/2.0 24 V/12 V 2.3 A

RRU3259 LTE TDD 1.1/2.0 24 V/12 V 2.3 A

2.2 RET AntennaOne RET antenna consists of one remote control unit (RCU) and one or more RET subunits.



12


18/211

l The RCU is the control unit of an RET antenna. It receives and runs the control commandsfrom the base station and drives the stepper motor. The stepper motor drives the phaseshifter inside the antenna device, and the phase shifter adjusts the antenna tilt. InterfaceRS485 functions as the control interface of the RCU.

l RET subunits are antenna devices that can be independently controlled.

An RET antenna may comprise more than one RET subunit combined in a single physical entity.The RET antenna is classified into the following types:

l A single-antenna RET antenna ( SINGLE_RET ) has only one RET subunit.l A multi-antenna RET antenna ( MULTI_RET ) has multiple RET subunits, each of which

supports the configuration file download and downtilt setting. A multi-antenna RETantenna can be regarded as a set of single-antenna RET antennas installed in a radome.

The RET antenna has the following benefits:

l Remote adjustment eliminates onsite operations. Antenna maintenance is not subject to siteconditions such as weather and location.

l High adjustment efficiency reduces network optimization and maintenance costs.l Adjustable downtilt prevents coverage distortion, which improves signal coverage and

decreases neighboring cell interference.

Compared with antennas with mechanical downtilts, RET antennas have the disadvantages of higher cost and higher complexity.

2.3 TMAA TMA is a low noise amplifier (LNA) installed next to the antenna. It improves the signal-to-noise ratio (SNR), sensitivity, and uplink coverage of a base station.

TMAs are classified into two types: common TMA and smart TMA. Unlike common TMAs,smart TMAs support the Antenna Interface Standards Group (AISG) protocol. Unless otherwisestated in this document, "TMA" refers to a smart TMA.

TMAs have a built-in smart bias-tee (SBT) that performs the following functions:

l Converts RS485 signals received from the RCU to on-off-keying (OOK) signals, andconverts OOK signals received from the RRU or RFU to RS485 signals

l Feeds DC power from the remote radio unit (RRU)/radio frequency unit (RFU) to the RCU

NOTE

l The SBT provides DC power supply and control commands through the feeder for the RCU. The SBTis applied on the RET antenna side.

l When an RRU or RFU connects to a TMA, at least one RF port supporting RET antennas must connectto this TMA so that the RRU/RFU can transmit control signals to the TMA. For details about capabilitiesof RF modules to support RET antennas, see Table 2-2 and Table 2-3 .

The TMA provides the following functions:

l Amplifies uplink signals to compensate for attenuation from an antenna to an RRU or RFUl Balances signal amplification between the uplink and downlink

A TMA has one or two subunits and supports amplification of one or two uplink RF signals.



13


19/211

2.4 SASU

An SASU is a Huawei customized device for antenna sharing between intra-band GSM andUMTS modes at a multimode site. Antenna sharing helps operators reduce their capitalexpenditure (CAPEX). Currently, the SASU supports only the 900 MHz and 2100 MHzfrequency bands.

The SASU uses two subunits to amplify uplink signals of GSM and UMTS systems.

2.5 AAS Module

2.5.1 OverviewAn AAS module is a combination of RF modules and antennas.

The passive antennas and RCUs in the AAS provide the ante nna and R ET functions, respectively,for the RRU/RFU that are connected to the AAS module.

For details about an AAS product, see the hardware description of the AAS product. Differenttypes of AAS modules have different sets of integrated dual-polarized antennas. For example,the AAU3901 is configured with three sets of integrated dual-polarized antennas and theAAU3910 is configured with two sets of them. For details about the mapping between AAU3901or AAU3910 integrated antennas and either of the following: inserted modules, RET functions,and external ports, see AAU3901 Hardware Description and AAU3910 Hardware

Description , respectively.

2.5.2 AAS Modules with Passive AntennasAn AAS module with passive antennas, and the built-in RCUs remotely control the downtiltsof these antennas provides the RET function for RRUs/RFUs in the same way as the RETfunction on conventional antennas. The AAS module with passive antennas supports inaccordance with the protocol AISG 2.0.

The AAS module supports the RET function by using the Management Unit (MU), theRETPORT on the AAS active module, or the RRU/RFU. You can choose only one method based

on onsite connections and AAS capabilities. Table 2-7 lists the capabilities of AAS modules tosupport the RET function.

Table 2-7 AAS module support for RET

AASModule

Application Mode

Using theMU(Single-AntennaMode)

Using theMU(AntennaCascading Mode)

Using theAAS RU

Using theRRU/RFU

AAU3901 UMTS Supported Notsupported

NotSupported

Notsupported



14


20/211

AASModule

Application Mode

Using theMU(Single-Antenna

Mode)

Using theMU(AntennaCascading

Mode)

Using theAAS RU

Using theRRU/RFU

AAU3902 UMTS, LTEFDD, GL

Notsupported

Supported NotSupported

Supported

AAU3910 GSM,UMTS, LTE,GU, GL, UL

Notsupported

Notsupported

Supported Supported



15


21/211

3 ALD Device Data ConfigurationALD device data can be configured in the following ways:

l ALD manual deployment: All the ALD device data must be manually configured.l ALD automatic deployment: Most of the initial configuration data of the ALD device is

automatically configured by the system, and a small amount of data is manually correctedand supplemented.

The following table lists whether each type of ALD device supports ALD manual deploymentor ALD automatic deployment in SRAN9.0.

Table 3-1 ALD devices that support ALD manual/automatic deployment

ConfigurationMethod

RET TMA SASU AAS

ALD manualdeployment

Supported Supported Supported Supported

ALD automaticdeployment

Supported Supported Not supported Not supported

NOTE

In scenarios in which the RET antenna is connected through the GATM, the RET antenna does not supportALD automatic deployment.

When you configure ALD device data, ALD automatic deployment is recommended. Use ALDmanual deployment in scenarios in which ALD automatic deployment is not supported.

SingleRANALD Management Feature Parameter Description 3 ALD Device Data Configuration


16


22/211

4 ALD Management Functions4.1 RET Antenna Functions

4.1.1 Connections Between RET Antennas and RRUs/RFUsRET antennas and RRUs/RFUs can be connected in a regular or daisy chain scenario. Whensplitters are used, RET antennas and RRUs/RFUs can be connected in a sector splitting scenario.

Regular Scenario

In a regular scenario, an RRU can be connected to one RET antenna through the RET port(RETPORT) or RF port (ANTENNAPORT). The RFU does not have an RETPORT andtherefore can be connected to one RET antenna only through the ANTENNAPORT.

l Connection to the RET antenna through the RETPORT

An AISG multi-wire cable connects the RETPORT on the RRU to the RCU of the RETantenna, as shown in Figure 4-1 . With the integrated BT, the RRU can send RS485 controlsignals and feed 12 V DC power to the RCU through the RETPORT. Therefore, no SBTis required. This connection mode is recommended when the distance between the RRUand the RET antenna is shorter than 20 m. For the data configurations in this connectionmode, see the following scenarios:

eGBTS/NodeB/eNodeB: scenario 1 in section 8.4 Deployment . GBTS: scenario 1 in section 9.4 Deployment . Base station using ALD automatic deployment: scenario 1 or 4 in section 10.4

Deployment .

SingleRANALD Management Feature Parameter Description 4 ALD Management Functions


17


23/211

Figure 4-1 Connection to the RET antenna through the RETPORT

l Connection to the RET antenna through the ANTENNAPORT

An SBT is required in this connection mode. Feeders and jumpers connect the RRU or RFU, SBT, and RET antenna, and an AISG multi-wire cable connects the SBT to the RCUof the RET antenna, as shown in Figure 4-2 . The RRU or RFU combines OOK signals, 12V DC power, and RF signals, and sends the combined signals to the SBT through feeders.The SBT splits the combined signals into two links. RF signals are sent to the RET antennaon one link. On the other link, OOK signals are converted to RS485 control signals and 12V DC power is forwarded to the RCU through an AISG multi-wire cable. For the dataconfigurations in this connection mode, see the following scenarios: eGBTS/NodeB/eNodeB: scenario 2 in section 8.4 Deployment . GBTS: scenario 2 in section 9.4 Deployment . Base station using ALD automatic deployment: scenario 1 or 4 in section 10.4

Deployment .



18


24/211

Figure 4-2 Connection to the RET antenna through the ANTENNAPORT

Connection modes shown in Figure 4-1 and Figure 4-2 also apply to a multimode basestation. For details about data configuration, see chapter 7 Engineering Guidelines (ALDManual Deployment on Multimode Base Station) .

l Connection to the RET antenna through the RETPORT (with an external BT)

This connection mode applies to RRUs without a BT that are installed 20 m or farther awayfrom RET antennas, such as the RRU3801C (20 W) for UMTS, and RRU3220 for LTE.Without a BT, RF ports cannot provide 12 V DC power for RET antennas. In this case,connect the RETPORT on an RRU to an external Bias Tee (BT) and connect an externalSBT to an RET antenna for power supply to the antenna, as shown in Figure 4-3 . The BTis the passive component that couples RF signals or OOK signals with feeder signals. TheBT is applied on the base station side. For the data configurations in this connection mode,see the following scenarios:



19


25/211

eGBTS/NodeB/eNodeB: scenario 1 in section 8.4 Deployment . GBTS: scenario 1 in section 9.4 Deployment . Base station using ALD automatic deployment: scenario 1 or 4 in section 10.4

Deployment .

Figure 4-3 Connection to the RET antenna through the RETPORT (with an external BT)

Daisy Chain ScenarioIn a daisy chain scenario, two or more RCUs are connected by AISG multi-wire cables. Theupper-level RCU provides RS485 control signals and power for the lower-level RCU. In Figure4-4 , RRUs are cascaded by connecting to the RET antennas through the RETPORT. Thisconnection mode applies to the scenario where antennas for multiple sectors are centrallyinstalled, for example, on the same pole or tower. In Figure 4-5 , RRUs/RFUs are cascaded byconnecting to the RET antennas through the ANTENNAPORT. The connection through theANTENNAPORT requires SBTs, and cascading can reduce the number of required SBTs. Insuch a case, the RET antennas can be configured on the RRU or RFU that provides RS485 signalsand power for the RET antennas.

In this scenario, the SCENARIO parameter for all RET antennas must be set toDAISY_CHAIN , and the RET antennas are identified by serial numbers.



20


26/211

For the data configurations in the connection modes shown in Figure 4-4 and Figure 4-5 , seethe following scenarios:

l eGBTS/NodeB/eNodeB: scenario 1 and 2 in section 8.4 Deployment .l GBTS: scenario 1 and 2 in section 9.4 Deployment .l Base station using ALD automatic deployment: scenario 1 or 4 in section 10.4

Deployment .

Figure 4-4 Connection to the RET antenna through the RETPORT



21


27/211


Connection modes shown in Figure 4-4 and Figure 4-5 also apply to a multimode base stationwith independent antennas. The configured RRUs/RFUs serve different modes.

The RET antenna data of a multimode base station must be configured only in a single mode.For details about data configuration, see chapter 7 Engineering Guidelines (ALD ManualDeployment on Multimode Base Station) . In Figure 4-4 , if RRU(1) is managed by the GBTS/eGBTS or eNodeB (the RET data is configured on the GBTS/eGBTS or eNodeB side), the

SCENARIO parameters must be set to DAISY_CHAIN for RET antennas connected to RRU(1) and RRU(2). If RRU(1) is managed by the NodeB (the RET data is configured on the NodeBside), the SCENARIO parameters must be set to DAISY_CHAIN and 2G_EXTENSION for the RET antennas connected to RRU(1) and RRU(2), respectively.

Some RF modules, such as the RRU3942 and RRU3841, have four RF ports. These RF moduleshave two or more RF ports to support RET functions in addition to the RETPORT. For details,see Table 2-3 . Two RF ports on these RF modules can be paired and connected to one antennato provide various transmit or receive functions. When the RRU3942 or RRU3841 is used, youcan refer to RRU3942 Hardware Description or RRU3841 Hardware Description .

The following description assumes that the RRU3942 uses a 2T4R configuration. "T" and "R"indicate transmission and reception, respectively. RF ports ANT_A and ANT_C on theRRU3942 are paired and connected to one antenna, and RF ports ANT_B and ANT_D are pairedand connected to the other antenna.

When the RRU3942 is installed less than 20 m away from RET antennas, the RRU3942 isconnected to the RET antennas through the RETPORT. The RET antennas are cascaded becausethe RRU3942 has only one RETPORT, as shown in Figure 4-6 .



22


28/211


29/211


In this connection mode, RF port ANT_A is the control port for the two RET antennas connectedto the RRU3942. For the data configuration for this connection mode, see scenario 2 in section8.4 Deployment for an eGBTS/NodeB/eNodeB or scenario 2 in section 9.4 Deployment for aGBTS.

Sector Splitting Scenario

The sector splitting scenario applies to UMTS only. In this scenario, the RRU or RFU isconnected to splitters and then RET antennas, as shown in Figure 4-8 .



24


30/211

Figure 4-8 Sector splitting scenario

In this scenario, the SCENARIO parameter for all RET antennas must be set toSECTOR_SPLITTING , and the RET antennas are identified by serial numbers. For the dataconfiguration of this connection mode for an eGBTS/NodeB/eNodeB, see scenario 2 in section8.4 Deployment . This connection mode does not apply to the GBTS.

GATM ScenarioThe GSM Antenna and TMA Control module (GATM) scenario applies to the GBTS only. Inthis scenario, a DRFU, which cannot provide OOK signals or support BT function, can beconnected to an RET antenna through a BT and SBT, as shown in Figure 4-9 . The GATM

provides OOK signals and 12 V DC power for the BT. Then the BT combines OOK signals, 12V DC power, and RF signals sent by the DRFU and sends the combined signals to the SBTthrough feeders. The SBT splits the combined signals received into two links. RF signals are



25


31/211

sent to the RET antenna on one link. On the other link, OOK signals are converted to RS485control signals and 12 V DC power is forwarded to the RCU through an AISG multi-wire cable.

Because of its hardware limitations, the GATM supports only RET antennas compatible withAISG1.1 protocols and does not support RET antennas compatible with AISG2.0 protocols.

Figure 4-9 GATM scenario

For the data configuration for this connection mode, see scenario 5 in section 9.4Deployment .

4.1.2 Operations on RET AntennasThe base station can perform operations, including configuration file loading, antennacalibration, and downtilt setting, on each RET subunit separately.

l Configuration file loading

A configuration file describes the relationship between the RCU and the RET subunitdowntilt. The configuration file is provided by the RET antenna manufacturer. Some RETantennas have been loaded with default configuration files before delivery. For antennaswithout default configuration files, run the following command to load the configurationfiles: GBTS: LOD BTSRETCFGDATA . Before you run this command, run the DLD

BTSALDFILE command to download the configuration file from the file server to the base station controller (BSC) operation and maintenance unit (OMU).



26


32/211

eGBTS/NodeB/eNodeB: DLD RETCFGDATA

Ensure that correct configuration files have been loaded to the RET antennas before antennacalibration. If an incorrect configuration file is loaded, the RET antenna will experienceunexpected errors. In this case, you can run the DSP BTSRETSUBUNIT (GBTS) or DSP

RETSUBUNIT (eGBTS/NodeB/eNodeB) command to query the name of the last loadedconfiguration file and the load time. You are advised to load the configuration file to theRET antennas of one or two base stations, and check whether the actual downtilts are thesame as the configured downtilts. If the downtilts are the same, the configuration file iscorrect.

NOTE

Run the following command to query dynamic information about RET additional data:

GBTS: DSP BTSRETDEVICEDATA

eGBTS/NodeB/eNodeB: DSP RETDEVICEDATA

If any information is incorrect in the command output, for example, the values of Max tilt and Min

tilt are NULL , no configuration file was loaded or the configuration file is lost.l Antenna calibration

After an RET antenna is installed, run the following command to calibrate the RET antenna: GBTS: CLB BTSRET eGBTS/NodeB/eNodeB: CLB RET

During the calibration, the RCU adjusts the RET antenna within the downtilt range so thatthe RET antenna operates properly. If the RET antenna is not calibrated, the base stationreports ALM-26753 RET Antenna Not Calibrated.

NOTE

An RET antenna does not need to be calibrated again after it is reset or powered off.

l Downtilt setting

1. After the RET antenna is calibrated, run the following command to query the supporteddowntilt range:

GBTS: DSP BTSRETDEVICEDATA

eGBTS/NodeB/eNodeB: DSP RETDEVICEDATA

NOTE

The downtilt range of an RET antenna varies according to the manufacturer and model.

2. Run the following command to set an RET subunit downtilt:

GBTS: MOD BTSRETSUBUNITeGBTS/NodeB/eNodeB: MOD RETSUBUNIT

Setting the downtilt of an RET subunit affects the coverage of the RET antenna. Set thedowntilt based on the engineering design.

The base station can perform operations on the RCU separately, including softwaredownload and RCU reset.

l RCU software download

Run the following command to download the RCU software: GBTS: LOD BTSALDSW . Before you run this command, run the DLD

BTSALDFILE command to download the RCU software from the file server to theBSC OMU.



27


33/211

eGBTS/NodeB/eNodeB: DLD ALDSW

For details about the RCU software, see the documents provided by the RET antennamanufacturer.

l RCU reset

Run the following command to reset the RCU: GBTS: RST BTSALD eGBTS/NodeB/eNodeB: RST ALD

Resetting the RCU does not change the RET antenna downtilt.

4.2 TMA Functions

4.2.1 Connections Between the TMA, RRU/RFU, and RET AntennaIf an RRU or RFU is to be connected to an RET antenna through a TMA, the RRU or RFUcontrol port must be connected to the TMA control port.

Connection to the RET Antenna Through the ANTENNAPORT (with a TMA)

A TMA is connected to an RRU or RFU and RET antenna, and is powered by the RRU or RFU.

With the integrated SBT, the TMA splits combined signals from the RRUs or RFUs into twolinks. RF signals are sent to the RET antenna on one link. On the other link, OOK signals areconverted to RS485 control signals and 12 V DC power is forwarded to the RCU through anAISG multi-wire cable.

Figure 4-10 shows how an RRU or RFU with two RF ports is connected to the TMA and RETantenna.



28


34/211

Figure 4-10 Connection to the RET antenna through the ANTENNAPORT (with a TMA)

For the data configurations in this connection mode, see the following scenarios:

l eGBTS/NodeB/eNodeB: scenario 3 in section 8.4 Deployment .

l GBTS: scenario 3 in section 9.4 Deployment .

l Base station using ALD automatic deployment: scenario 2 or 5 in section 10.4Deployment .

Figure 4-11 shows how two RF modules are cascaded and then connected to the TMA and RETantenna. In this mode, RF ports ANT_A on the two RF modules are connected to the TMA andRET antenna, and either RF port ANT_A can be the control port for the RET antenna connected

to the two RF modules.



29


35/211

Figure 4-11 Two cascaded RF modules connected to the TMA and RET antenna

For the data configurations in this connection mode, see the following scenarios:

l

eGBTS/NodeB/eNodeB: scenario 3 in section 8.4 Deployment .l GBTS: scenario 3 in section 9.4 Deployment .l Base station using ALD automatic deployment: scenario 6 in section 10.4 Deployment .

When RRUs with four RF ports are connected to two antennas, two RF ports on these RRUscan be paired and connected to one antenna. The following description assumes that theRRU3942 uses a 2T4R configuration. RF ports ANT_A and ANT_C on the RRU3942 are pairedand connected to one antenna, and RF ports ANT_B and ANT_D are paired and connected tothe other antenna. Figure 4-12 shows how the RRU3942 is connected to the TMA and RETantenna.



30


36/211

Figure 4-12 RRU3942 (2T4R) connected to the TMA and RET antenna

In this connection mode, RF ports ANT_A and ANT_B are the control ports for Antenna(1) andAntenna(2), respectively. For the data configurations in this connection mode, see the followingscenarios:

l eGBTS/NodeB/eNodeB: scenario 3 in section 8.4 Deployment .l GBTS: scenario 3 in section 9.4 Deployment .l Base station using ALD automatic deployment: scenario 7 in section 10.4 Deployment .

Connection to the RET Antenna Through the RETPORT (with a TMA)

This connection mode applies to RRUs without a BT, such as the RRU3004 for GSM,RRU3801C (20 W) for UMTS, and RRU3220 for LTE. Without a BT, RF ports cannot provide



31


37/211

12 V DC power for antennas. In this case, connect the RETPORT on an RRU to an external BTto provide power for antennas, as shown in Figure 4-13 .

The signal transmission process is as follows:

1. The RRU supplies 12 V DC power and sends RS485 control signals to the external BTthrough an AISG multi-wire cable.

2. The BT converts RS485 control signals to OOK signals, combines the OOK signals andRF signals, and sends the combined signals to the TMA.

3. The TMA splits the combined signals into two links. RF signals are sent to the RET antennaon one link. On the other link, OOK signals are converted to RS485 control signals and 12V DC power is forwarded to the RCU through an AISG multi-wire cable. For the dataconfiguration for this connection mode, see scenario 4 in section 8.4 Deployment for aneGBTS/NodeB/eNodeB or scenario 4 in section 9.4 Deployment for a GBTS.



32


38/211

Figure 4-13 Connection to the RET antenna through the RETPORT (with a TMA)

Connection to the TMA Through the GATM

Connections between the GATM and TMA apply to the GBTS only. In this scenario, a DRFUis connected to a TMA through a GATM and BT, as shown in Figure 4-14 . The GATM feeds12 V DC power to the BT. Then, the BT combines the OOK signals, 12 V DC power, and RFsignals and sends the combined signals to the TMA.

The GATM can supply power only to the connected TMA. The TMA provides the default gains,not the configured gains. You need to configure parameters related to the power switch andcurrent alarm threshold for the port on the GATM connecting to the TMA. For details about data

preparation, see Table 9-11 . Then, configure parameters related to the RX channel attenuation.



33


39/211

For details about data preparation, see Table 9-9 . RET data is not involved in this connectionmode.

Figure 4-14 Connection to the RET antenna through the GATM

4.2.2 Operations on the TMANOTE

The gain of the TMA with fixed gain is not configurable.

TMA gain and working mode are configurable.l Setting TMA working mode

By default, the TMA is set to NORMAL working mode to ensure normal operation. If yourun the following command with the MODE parameter set to BYPASS , the TMA servesas a straight-through feeder and does not amplify signals:

GBTS: MOD BTSTMASUBUNIT eGBTS/NodeB/eNodeB: MOD TMASUBUNIT

l Setting TMA gain

1. Run the following command to query the value range of TMA gain:

GBTS: DSP BTSTMADEVICEDATA



34


40/211

eGBTS/NodeB/eNodeB: DSP TMADEVICEDATA

2. Run the following command to set TMA subunit gain:

GBTS: MOD BTSTMASUBUNIT

eGBTS/NodeB/eNodeB: MOD TMASUBUNIT

The base station can perform operations on the TMA separately, including software downloadand TMA reset.

l TMA software download

Run the following command to download the TMA software: GBTS: LOD BTSALDSW . Before you run this command, run the DLD

BTSALDFILE command to download the TMA software from the file server to theBSC OMU.

eGBTS/NodeB/eNodeB: DLD ALDSW

For details about the TMA software, see the documents provided by the TMA manufacturer.l TMA reset

Run the following command to reset the TMA: GBTS: RST BTSALD eGBTS/NodeB/eNodeB: RST ALDResetting the TMA does not change the TMA gain and working mode.

4.3 SASU Functions

4.3.1 Connections Between the SASU, RRU/RFU, and RET AntennaFigure 4-15 shows how the SASU, RRUs/RFUs, and RET antenna are connected when RRUs/RFUs for GSM (referred to as 2G) and UMTS (referred to as 3G) share one RET antenna andthe SASU is installed less than 20 m away from the RET antenna. With the integrated SBT, theSASU splits combined 3G signals from the RRUs/RFUs into two links. RF signals and 2G signalsare combined and sent to the RET antenna on one link. On the other link, OOK signals areconverted to RS485 control signals and 12 V DC power is forwarded to the RCU through anAISG multi-wire cable.



35


41/211

Figure 4-15 SASU directly connected to the RET antenna

SASU data can be configured only on the NodeB side. Because the SASU is an active device,you need to turn on the power switch for the 3G RRU control port on the NodeB side, and specify

current alarm thresholds. For connection mode in Figure 4-15 , set the DCSWITCH parameter for the SASU to OFF . Otherwise, the RET antenna will short-circuit. For the data configurationfor this connection mode, see scenario 5 in section 8.4 Deployment .

Figure 4-16 shows how the SASU, RRUs/RFUs, TMA, and RET antenna are connected whenthe SASU is installed greater than 20 m away from the RET antenna. The SASU combines 2Gand 3G signals and sends the combined signals to the TMA. The TMA splits the combinedsignals into two links. RF signals are sent to the RET antenna on one link. On the other link,OOK signals are converted to RS485 control signals and 12 V DC power is forwarded to theRCU through an AISG multi-wire cable.



36


42/211

Figure 4-16 SASU connected to the TMA and RET antenna

SASU data can be configured only on the NodeB side. In this connection mode, the DCSWITCH parameter for the SASU cannot be set to OFF because the TMA is an active device.If the DCSWITCH parameter is set to UMTS , specify the DCLOAD parameter for SASUsubunits so that the TMA connected to the SASU can be acknowledged by the base transceiver station (BTS). For the data configuration for this connection mode, see scenario 6 in section 8.4Deployment .

4.3.2 Operations on the SASUThe SASU DC power switch, gain, and working mode are configurable only on the NodeB side.

l Setting the DC power switch



37


43/211

When the SASU is connected to the RET antenna through a TMA, run the MOD SASUcommand with the DCSWITCH parameter set to any value except OFF . When the SASUis directly connected to the RET antenna, set the DCSWITCH parameter for the SASU toOFF . Otherwise, the RET antenna will short-circuit.

l Setting SASU working modeBy default, the SASU is set to NORMAL working mode to ensure normal operation. If you run the MOD SASUSUBUNIT command with the MODE parameter set toBYPASS , the SASU serves as a straight-through feeder and does not amplify signals.

l Setting SASU gain

1. Run the DSP SASUDEVICEDATA command to query the value range of SASU gain.

2. Run the MOD SASUSUBUNIT command to set SASU subunit gain.

The base station can perform operations on the SASU separately, including software downloadand SASU reset.

l SASU software down load

Run the DLD ALDSW command to download the SASU software.

For details about the SASU software, see the documents provided by the SASUmanufacturer.

l SASU reset

Run the RST ALD command to reset the SASU.

Resetting the SASU does not change the SASU gain and working mode.

4.4 AAS Functions4.4.1 Connections Between the AAS Module with PassiveAntennas, RRU/RFU, and BBU

An AAS module with passive antennas has two types of external ports: an RET port (RETPORT)and an RF port (ANTENNAPORT). The ANTENNAPORT can be at the bottom of the AAAUor on the AAPU. Some AAS modules, for example, the AAU3910, have AISG ports that can

be connected to RRUs or RFUs for the RET function. Table 2-7 lists the capabilities of AASmodules to support the RET function.

Scenario 1: Using the MU for the RET function on the AAS Module

As shown in Figure 4-17 , RRUs or RFUs connect to an AAS module with passive antennasthrough external ports on the AAS module. Choose an appropriate external port to connect theRRU or RFU to the AAS module. The integrated RCU provides the RET function for the AASmodule with passive antennas and the RCU is controlled by the MU. In this scenario, the RETfunction for the AAS module with passive antennas must be set by the mode that manages theAAS module. For example, to enable GSM RRUs/RFUs to use the RET function for the AASmodule with passive antennas, the RET function must be set in the UMTS mode that managesthe AAS module with passive antennas.

Before setting the RET function, you must configure the AAS module. Compared with the RETfunction on conventional antennas, the RET function on the AAS module with passive antennas



38


44/211

does not require you to configure power supply switches or current alarm thresholds. Instead,you can directly configure the RET function:

l For the AAU3901, RETTYPE must be set to MULTI_RET . You can determine whichantenna to use for the RET function according to the RET subunit.

l For other AAS modules, RETTYPE and SCENARIO must be set to SINGLE_RET andDAISY_CHAIN , respectively. You can determine which antenna to use for the RETfunction according to the serial number of the integrated antenna. If you need to use onlyone set of antennas for the RET function, set SCENARIO to DAISY_CHAIN . In this case,specify the VENDORCODE and SERIALNO parameters because the antennas in the AASmodule are working in daisy chain mode. For the serial numbers of the integrated antennasin the AAS module, see the hardware description of the AAS module. For the dataconfiguration for this connection mode, see scenario 7 in section 8.4 Deployment .

Figure 4-17 Connections to the RRUs/RFUs and BBU (MU for RET function)

Scenario 2: Using the RRU/RFU for the RET function on the AAS ModuleWhen the RET function for an AAS module with passive antennas is provided by an RRU or RFU connecting to the AAS module, the connections between the RRU or RFU and the AASmodule are similar to the connections between the RRU or RFU and the conventional RETantennas except for the AISG port configuration, as shown in Figure 4-18 . In this scenario, theAAS module functions as the conventional RET antennas. Therefore, the configuration can be

performed in the same way as that for conventional RET antennas.

You can configure the RET function: RETTYPE and SCENARIO must be set toSINGLE_RET and DAISY_CHAIN , respectively. You can determine which antenna to usefor the RET function according to the antenna serial number.

If you need to use only one set of antennas for the RET function, set SCENARIO toDAISY_CHAIN . In this case, specify the VENDORCODE and SERIALNO parameters

because the antennas in the AAS module are working in daisy chain mode. For the serial numbersof the integrated antennas in the AAS module, see the hardware description of the AAS module.

For other data configurations,



39


45/211

l If the RRU is to use an RETPORT to send RET signals to the AAS module, see scenario1 in section 8.4 Deployment for an eGBTS/NodeB/eNodeB or scenario 1 in section 9.4Deployment for a GBTS.

l If the RET function is provided by the RRU or RFU through an ANTENNAPORT, see

scenario 2 in section 8.4 Deployment for an eGBTS/NodeB/eNodeB or scenario 2 insection 9.4 Deployment for a GBTS.

Figure 4-18 Connections to the RRUs/RFUs and BBU (RRU/RFU for RET function)

Scenario 3: Using the Active Module (RU) on the AAS for the RET function

When the RET function for an AAS module with passive antennas is controlled by the activemodule on the AAS module, the active module forwards the RET signals received from the BBUto the passive module using an RETPORT, as shown in Figure 4-19 . In this case, the activemodule works as a conventional RET device and therefore configurations on this active moduleare the same as those on a conventional RET device.

For the AAU3910, RETTYPE and SCENARIO must be set to SINGLE_RET and

DAISY_CHAIN , respectively. You can determine which set of antennas to use for the RETfunction according to the antenna serial number. If you need to use only one set of antennas for the RET function, set SCENARIO to DAISY_CHAIN . In this case, specify theVENDORCODE and SERIALNO parameters because the antennas in the AAS module areworking in daisy chain mode. For the serial numbers of the integrated antennas in the AASmodule, see the hardware description of the AAS module. For other data configurations for thisconnection mode for an eGBTS/NodeB/eNodeB, see scenario 8 in section " 8.4 Deployment ."



40


46/211

Figure 4-19 Connections to the RRUs/RFUs and BBU (RU for RET function)

4.4.2 Operations on AAS Modules

AAS Modules with Passive Antennas

When the RET function for an AAS module with passive antennas is controlled by the MU,related operations on the AAS module are performed in the following way:

l For the AAU3910, the operations are performed on each RET subunit independently because the passive antennas in the AAS module function as a set of multiple antennas.

l For other AAS modules, the operations are performed on each antenna independently because each RET subunit of the passive antennas in the AAS module functions as a singleantenna working in daisy chain mode.

When the RET function for an AAS module with passive antennas is controlled by the RRU or RFU, related operations are performed on each antenna independently because each RET subunitof the passive antennas in the AAS module functions as a single antenna working in daisy chainmode.

When the RET function for an AAS module with passive antennas is controlled by the activemodule on the AAS module, related operations are performed on each antenna independently

because each RET subunit of the passive antennas in the AAS module functions as a singleantenna working in daisy chain mode.

l Scanning

You can scan all the AAS modules connected to an RF module (except for the AAU3901).When the RET function for a specific AAS module is controlled by an RF module, the RETfunction for the module cannot be scanned on or controlled by other RF modules that arealso connected to the AAS module.

If multiple RF modules share the AAS module, running the SCN ALD command may failto scan all the RET function controlled by each RF module at a time. In this case, you can



41


47/211

run the SCAN ADL command for each of the RF modules that control the RET functionfor AAS modules that have not been scanned.

l Configuration file loading

Loading configuration files is not required because AAS modules with passive antennascome with built-in configurations files. If ALM-26754 RET Antenna Data Loss is reported,the configuration files have been lost. In such a case, you can run the DLD RETCFGDATAcommand to reload configuration files for the AAS module. Note that this command appliesonly to eGBTSs/NodeBs/eNodeBs.

l Antenna calibration

After an AAS module with passive antennas is installed, run the CLB RET command onthe eGBTS/NodeB/eNodeB LMT to calibrate the antennas. During the calibration, RCUsadjust the antennas within the downtilt range until the antennas operate properly. If thecalibration fails, ALM-26753 RET Antenna Not Calibrated is generated.

NOTE

After the AAS module is reset or powered off, it does not need to be calibrated again.

l Downtilt setting

After the AAS module is calibrated, run the DSP RETDEVICEDATA command on theeGBTS/NodeB/eNodeB LMT to query the supported downtilt range. Then, run the MODRETSUBUNIT command to set the downtilts for RET subunits. Because setting RETsubunit downtilt affects the coverage of the related antennas, specify parameters based onthe engineering design.

NOTE

Each RET subunit supports a unique downtilt range.

In an AAS module with passive antennas, the base station can download software and reset theRCU for each RCU separately.

l RCU software download

Run the DLD ALDSW command on the eGBTS/NodeB/eNodeB LMT to download theRCU software provided by Huawei. For details, see AAS-related documents provided byHuawei.

l RCU reset

Run the RST ALD command on the eGBTS/NodeB/eNodeB LMT to reset an RCU. RCUreset does not change the antenna's downtilt.



42


48/211

5 Related Features N/A

SingleRANALD Management Feature Parameter Description 5 Related Features


43


49/211

6 Impact on the Network N/A

SingleRANALD Management Feature Parameter Description 6 Impact on the Network


44


50/211

7 Engineering Guidelines (ALD ManualDeployment on Multimode Base Station)

7.1 When to Use ALD ManagementIt is recommended that ALD management be used when ALDs have been installed and the ALDscomply with the AISG protocol. The AISG protocol has two versions, AISG v1.1 and AISGv2.0. Both are supported in SRAN8.0 and later.

7.2 Required Information N/A

7.3 Planning N/A

7.4 Deployment

7.4.1 RequirementsThe GSM and UMTS modes have no requirements for deploying this feature.

In the LTE system, this feature is under license control. Table 7-1 lists the license control itemsfor this feature.

Table 7-1 License control items for optional features of ALD management

Feature License Control Item Name

LOFD-001024 Remote Electrical TiltControl

Remote Electrical Tilt Control (FDD)

SingleRANALD Management Feature Parameter Description

7 Engineering Guidelines (ALD Manual Deployment onMultimode Base Station)


45


51/211

Feature License Control Item Name

TDLOFD-001024 Remote Electrical TiltControl

Remote Electrical Tilt Control (TDD)

7.4.2 Overall Process (RETs/TMAs/SASUs)Determine the location of the ALD control port on the RRU or RFU. The ALD control port

provides power and OOK signals for the ALD. You can locate the port based on the site's cableconnections.

Device data in a co-MPT multimode base station needs to be configured only once. For a co-MPT multimode base station, you only need to determine which RRU/RFU port is the control

port for the ALD device and configure the power switch, current threshold and ALD data once.

For a separate-MPT base station, the RRU or RFU can be managed by a single mode or multiplemodes. Determine the mode that manages the RRU or RFU and configure all data for the ALD

powered by this RRU or RFU in this mode. This procedure involves the following two scenarios:

NOTE

MPT is short for main processing and transmission unit.

Scenario 1: RRU/RFU Is Managed by a Single Mode

The RRU or RFU is working in a single-mode or multimode base station, and provides power and OOK signals for the ALD.

Determine the mode that manages the RRU or RFU and configure all ALD data in this mode.

Scenario 2: RRU/RFU Is Managed by Multiple Modes

The RRU or RFU is working in a multimode base station, and provides power and OOK signalsfor the ALD.

Parameters related to the ALD control port in this scenario are RF module common parameters.During the data preparation, initial configuration, and feature reconfiguration, the common

parameters must be set to consistent values for all modes that manage the RRU or RFU. Table7-2 lists the common ALD parameters for RF modules in each mode.




46


52/211

Table 7-2 Common ALD parameters for RF modules in each mode

Object GBTSParameterName

eGBTS/NodeB/ eNodeB/Co-MPTBase StationParameter Name

Recommended Setting

Control port(RET

port as acontrol

port)

RET ALDPower Switch

ALD Power Switch For a separate-MPT base station, set this parameter to ON in all modes. TheRETPORT and ANTENNAPORTswitches on one RRU cannot be turnedon simultaneously.

RET ALDCurrent AlarmThresholdType

Current AlarmThreshold

For a separate-MPT base station, each of these parameters must be set to the samevalue in all modes. For recommendedvalues, see Table 8-18 .

RET ALDUnder CurrentOccur Threshold(mA)

UndercurrentAlarm Occur Threshold

RET ALDUnder CurrentClear Threshold(mA)

UndercurrentAlarm Clear Threshold

RET ALDOver CurrentOccur Threshold(mA)

Overcurrent AlarmOccur Threshold

RET ALDOver CurrentClear Threshold(mA)

Overcurrent AlarmClear Threshold

Control port (RF port as acontrol

port andANT_Aas anexample)

ANT_A ALDPower Switch

ALD Power Switch For a separate-MPT base station, set this parameter to ON in all modes. TheRETPORT and ANTENNAPORTswitches on one RRU cannot be turnedon simultaneously.

ANT_A ALDCurrent AlarmThresholdType

Current AlarmThreshold Type

For a separate-MPT base station, each of these parameters must be set to the samevalue in all modes. For recommendedvalues, see Table 8-17 .




47


53/211

Object GBTSParameterName

eGBTS/NodeB/ eNodeB/Co-MPTBase StationParameter Name

Recommended Setting

ANT_A ALDOver CurrentOccur Threshold(mA)

UndercurrentAlarm Occur Threshold

ANT_A ALDOver CurrentClear Threshold(mA)

UndercurrentAlarm Clear Threshold

ANT_A ALDUnder CurrentOccur Threshold(mA)

Overcurrent AlarmOccur Threshold

ANT_A ALDUnder CurrentClear Threshold(mA)

Overcurrent AlarmClear Threshold

RRU/RFU RXchannelattenuation

AntennaTributary 1Factor

Attenuation If no TMA is used, set this parameter to0.

If a 12 dB TMA is used, set this parameter to a value within the rangefrom 4 dB to 11 dB.

If a 24 dB TMA is used, set this parameter to a value within the rangefrom 11 dB to 22 dB.

For a separate-MPT base station, each of these parameters must be set to the same

value in all modes.

NOTE

When an RF port except ANT_A is used as a control port, common ALD parameters are named in thefollowing ways:l For a GBTS, common ALD parameters are named by analogy based on Table 7-2 . For example, when

ANT_B is used as the control port, ANT_B ALD Power Switch is the correct parameter namel For an eGBTS, NodeB, eNodeB, or co-MPT base station, common ALD parameters are named in the

same way as those listed in Table 7-2 .

Other ALD-related parameters, except the RF module common parameters, must be set only inone mode of the separate-MPT base station. Choose one from the modes that manage the RRU




48


54/211

or RFU providing power and OOK signals for the ALD. Then, configure all data for the ALDonly in this mode.

NOTE

l The mode in which the other ALD-related parameters are set must be the same in the data preparation,initial configuration, activation observation, and reconfiguration.

l Only one maintenance link can be established between the RRU or RFU and the ALDs. Therefore,ALD data can be configured only in one mode of a multimode base station. If ALD data is conf