Beruflich Dokumente
Kultur Dokumente
Issue 01
Date 2017-03-10
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.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
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
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
11 Reference Documents............................................................................................................... 67
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 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.
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.
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
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.
NOTE
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.
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.
For details about the RET function for passive antennas, see ALD Management Feature
Parameter Description.
Figure 2-3 Connection method required by the RET function for active antennas
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.
Take AAU3902 as an example. The relationships between the logical channel, logical port,
and antenna polarization are as follows.
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.
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.
Figure 3-1 Working principle of AAS Virtual Four Uplink Channels for LTE (side view)
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)
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.
Figure 5-1 Working principle of AAS Vertical Multiple Sectors for LTE (side view)
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.
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.
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)
8 Related Features
Table 8-1 lists the prerequisite features and mutually exclusive features related to AAS.
NOTE
9 Network Impact
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.
Configuration Management
The following MML commands and parameters have been introduced on the eNodeB side to
accommodate this feature.
Performance Management
None.
Fault Management
Table 9-3 lists the alarms with online help information that was updated after this feature was
introduced.
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.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.
License
Feature ID Feature Name License Control NE Sales Unit
Item
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.
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.
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.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.
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.4.3 NEs
This feature is implemented on the eNodeB.
9.4.4 Hardware
None.
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.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.
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.
10 Engineering Guidelines
A downtilt angle is equal to the sum of mechanical downtilt angle and configured downtilt
angle:
Table 10-1 lists the ranges of mechanical downtilt angles and electrical downtilt angles.
10.1.1 Requirements
Passive antennas are not license-controlled.
Polar Type POLARTYPE Set this parameter based on the AAS Equipment
specifications. plan
Table 10-3 describes the parameters that must be set in an RETSUBUNIT MO.
10.1.3 Precautions
None.
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.
AAMU User- Cabinet No., Subrack No., Slot No., RRU N/A
defined Topo Position, RRU Chain No., AAS
sheet Position
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
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
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.
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.2.1 Requirements
Active antennas are not license-controlled.
Table 10-6 describes the parameters that must be set in a VRETSUBUNIT MO.
10.2.3 Precautions
None.
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.
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
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
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
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.
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.3 Planning
RF Planning
The suggestions for RF planning are as follows:
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.
For the parameters that must be set in a VRETSUBUNIT MO, see Table 10-6.
10.3.4.3 Precautions
None.
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
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
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
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
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 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
//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.
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.
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
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%
10.4.3 Planning
RF Planning
The suggestions for RF planning are as follows:
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.
4.9 Gbit/s 4 2 2 1
6.144 Gbit/s 4 2 2 1
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.
For the parameters that must be set in a VRETSUBUNIT MO, see Table 10-6.
10.4.4.3 Precautions
None.
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.
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
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
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.
----End
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.
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%
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.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.
– 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.
10.5.4.3 Precautions
None.
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.
NOTE
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
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.
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
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.
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%
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.
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.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.
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.
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.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.
NOTE
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
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.
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 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
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.
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%
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.
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.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.
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%
11 Reference Documents