3D Beamforming (ERAN12.1 05)
3D Beamforming (ERAN12.1 05)
3D Beamforming (ERAN12.1 05)
Issue 05
Date 2018-01-22
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......................................................................................................................................... 4
3 SSB....................................................................................................................................................5
3.1 Principles........................................................................................................................................................................ 5
3.2 Network Analysis........................................................................................................................................................... 6
3.2.1 Benefits........................................................................................................................................................................ 6
3.2.2 Impacts.........................................................................................................................................................................7
3.3 Requirements.................................................................................................................................................................. 9
3.3.1 Licenses....................................................................................................................................................................... 9
3.3.2 Software.......................................................................................................................................................................9
3.3.3 Hardware................................................................................................................................................................... 10
3.3.4 Others.........................................................................................................................................................................11
3.4 Operation and Maintenance..........................................................................................................................................12
3.4.1 Data Configuration.................................................................................................................................................... 12
3.4.1.1 Data Preparation..................................................................................................................................................... 12
3.4.1.2 Using MML Commands......................................................................................................................................... 15
3.4.1.3 Using the CME....................................................................................................................................................... 18
3.4.2 Activation Verification.............................................................................................................................................. 18
3.4.3 Network Monitoring.................................................................................................................................................. 19
4 8T8R Cells..................................................................................................................................... 20
4.1 Principles...................................................................................................................................................................... 20
4.2 Network Analysis......................................................................................................................................................... 20
4.2.1 Benefits...................................................................................................................................................................... 20
4.2.2 Impacts.......................................................................................................................................................................20
4.3 Requirements................................................................................................................................................................ 21
4.3.1 Licenses..................................................................................................................................................................... 21
4.3.2 Software.....................................................................................................................................................................21
4.3.3 Hardware................................................................................................................................................................... 23
4.3.4 Others.........................................................................................................................................................................23
5 Parameters..................................................................................................................................... 29
6 Counters........................................................................................................................................ 42
7 Glossary......................................................................................................................................... 45
8 Reference Documents................................................................................................................. 46
1.1 Scope
This document describes LEOFD-121204 3D Beamforming, including its technical
principles, related features, network impact, and engineering guidelines.
Feature compatibility with specific terminal models is not presented in this document. For
compatibility information, contact Huawei engineers.
Any parameters, alarms, counters, or managed objects (MOs) described herein apply only to
the corresponding software release. For future software releases, refer to the corresponding
updated product documentation.
This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD,
and "eNodeB" refers to LTE FDD eNodeB.
eRAN12.1 05 (2018-01-22)
This issue includes the following changes.
Feature Added support for 8T8R cells. For details, see 4 None
change 8T8R Cells.
eRAN12.1 04 (2017-08-30)
This issue includes the following changes.
eRAN12.1 03 (2017-05-31)
This issue includes the following changes.
eRAN12.1 02 (2017-04-26)
This issue includes the following changes.
eRAN12.1 01 (2017-03-08)
This issue includes the following changes.
2 Overview
Based on the increasing traffic volume in densely populated urban areas, the capacity
requirements in next few years are predicted to increase threefold to sixfold, and the spectrum
resources in the 1.8 GHz to 2.6 GHz bands are so limited that they should be fully utilized.
This feature uses active antenna units (AAUs) to provide the Static Shared Beam (SSB)
function and to serve 8T8R cells. If multiple carriers are configured on the same AAU, it is
recommended that the same function (SSB or 8T8R cells) be used on all these carriers.
l SSB generates two beams on the vertical plane to serve two 4T4R cells at each 8T8R
AAU, as shown in Figure 2-1.
l In each 8T8R cell, 8-antenna receive diversity is available in the uplink, and 4x2 or 4x4
MIMO is available in the downlink.
3 SSB
3.1 Principles
SSB uses beamforming to generate two cells, inner and outer, at an AAU on the vertical
plane. The two cells operate on the same frequency. This function is used for capacity
expansion at hotspots. It is an option for operators that require capacity expansion but have no
additional frequencies available.
NOTE
This function is mainly used for downlink capacity expansion, for example, when there is a cell resource
shortage.
The RETSUBUNIT.TILT parameter is set to different values for different remote electrical
tilt (RET) subunits, allowing SSB to generate two beams on the vertical plane. The two beams
are used for the inner and outer cells, as shown in Figure 3-1.
For load balancing, the eNodeB instructs UEs that have just accessed the inner or outer cell to
perform intra-frequency measurements when both of the following conditions are met:
l The downlink physical resource block (PRB) usage of the serving cell is greater than the
value of the CellVMS.VmsPrbLoadTh parameter.
l The downlink PRB usage of the serving cell minus that of a neighboring cell is greater
than the value of the CellVMS.VmsPrbDiffTh parameter.
The eNodeB selects UEs that each meet both of the following conditions for load balancing:
l The UE reports intra-frequency handover event A3, the offset for which is equal to
IntraFreqHoGroup.IntraFreqHoA3Offset minus CellVMS.VmsA3Offset. For the
definition of event A3, see Overview of Mobility Management in Connected Mode
Feature Parameter Description.
l The PRB usage of the UE is greater than 2%.
3.2.1 Benefits
The SSB function increases system capacity considerably in urban areas where there is
contiguous coverage. In a cell served by an eNodeB with a 2T2R 3-sector configuration, SSB
increases the average downlink cell traffic volume and average downlink UE throughput by
60%–100% when LOFD-001003 DL 4x2 MIMO and LOFD-001005 UL 4-Antenna Receive
Diversity are both enabled.
The increases are closely related to cell loads, whether the cells using SSB provide contiguous
coverage, and how UEs are distributed across inner and outer cells. The gains of this function
are higher if the cell load is higher, the cell coverage is more contiguous, and the percentage
of UEs in each inner cell is closer to 50%.
The increases are also affected by cell bandwidth. The inner and outer cells must have the
same bandwidth, in order not to affect channel calibration. When the available bandwidth is
less than 5 MHz, SSB works only at active ports on AAUs. A smaller available bandwidth
causes less accurate channel calibration and therefore fewer gains produced by this function.
This function is suitable for high-traffic scenarios in urban areas. It is recommended when the
busy-hour PRB usage of the cells is at least 50%. Do not use this feature when the inter-site
distance exceeds 500 m.
Downlink PRB usage = L.ChMeas.PRB.DL.Used.Avg/L.ChMeas.PRB.DL.Avail x 100%
3.2.2 Impacts
Network Impacts
l User-perceived downlink throughput
In an eNodeB with a 2T2R 3-sector configuration, SSB may cause a decrease in user-
perceived throughput in idle periods (for example, when the PRB usage is less than 20%)
or when the inner- and outer-cell loads are imbalanced.
l Downlink peak data rate
In a cell served by an eNodeB with a 2T2R 3-sector configuration, SSB causes an
increase in the percentage of times rank 1 is reported and therefore a lower percentage of
UEs that achieve their peak data rates in the case of downlink 2x2 multiple-input
multiple-output (MIMO). In addition, in the cells generated by SSB, the channel
correlation between antennas is higher than that in common 4T4R cells. As a result, UEs
cannot reach their expected peak data rates in the case of downlink 4x4 MIMO.
l Downlink coverage
On a network with non-contiguous coverage from cells generated by using SSB, if SSB
causes cell power to be lower than neighboring 2T2R cell power, the local cell coverage
shrinks.
l Other network performance indicators
In an eNodeB with a 2T2R 3-sector configuration, SSB causes an increase in the number
of cells and a decrease in the SINR. It may result in a lower handover success rate, more
RRC connection reestablishments, and a higher service drop rate than the performance
indicators before SSB is used.
Impacted Features
Feature ID/ Feature/Function Description
Function Switch Name
LEOFD-111305 Virtual 4T4R Virtual 4T4R and the SSB function are
suitable for different scenarios. It is
recommended that one of them be
selected in specific scenarios.
3.3 Requirements
3.3.1 Licenses
This function requires the license for 3D Beamforming. The other two licenses in the
following table are recommended so that this function can achieve its optimal performance.
Feature ID Feature Name Model Sales Unit
3.3.2 Software
Prerequisite Features
None
3.3.3 Hardware
Base Station Models
Only 3900 or 5900 series base stations are compatible with this function.
Boards
The baseband processing units (BBPs) must be UBBPe4 boards. Note that the two 4T4R cells
created by SSB are automatically set up on the same BBP, and they together account for a
single unit of 8T8R cell capacity of the BBP. If the two 4T4R cells are manually bound to
different BBPs, the cells will fail to be set up. When there are 4T4R and 8T8R cells on a BBP,
the cell capacity of the BBP is consumed on a per 8T8R cell basis.
RF Modules
AAU5972s must be used.
AAU5972s in the 1.8 GHz band contain both radio and antenna modules. Power supplies
must be directly connected to the AAUs, and those AAUs must be connected to the BBUs of
eNodeBs through CPRI optical cables. AAU5972s in other bands contain only antenna
modules. They must be connected to external radio units. These AAUs supply power to the
radio units, which are then connected to BBUs through CPRI optical cables. AISG cables do
not need to be connected to the AAUs. For details about how to install AAU5972s, see
AAU5972 Installation Guide.
Typically, each eNodeB requires three AAUs, each of which will serve two cells (one inner
and one outer) for SSB. Each eNodeB will serve a total of six cells.
When AAU5972s are used, the configured power per channel for inner and outer cells must
meet the following requirements:
l For AAU5972s in the 1.8 GHz band, the configured power per channel for each of the
inner and outer cells must be less than or equal to 30 W. Typically, inner and outer cells
are assigned the same power: 4 x 30 W. The typical power configuration for a 20 MHz
cell is that CRS power is 16.9 dBm, PA is –3, and PB is 1.
l For AAU5972s in the other bands, the configured power per channel for each of the
inner and outer cells must be less than or equal to 40 W. Typically, inner and outer cells
are assigned the same power: 4 x 40 W. The typical power configuration for a 20 MHz
cell is that CRS power is 18.2 dBm, PA is –3, and PB is 1.
3.3.4 Others
For each eNodeB, three cells will change to six cells on two layers, with each cell covering a
120-degree arc, as illustrated in Figure 3-2.
Network planning will focus on PCIs, neighboring cells, and PRACH root sequence
indexes.
l If the RS power decreases, network planning and optimization should consider downtilt
angles, angles between beams, RS power, and the settings of PA and PB.
Parameters
Table 3-1 and Table 3-2 describe the parameters used for activation and optimization,
respectively. This section does not describe the parameters related to cell establishment.
//Adding back the following information as RMV CELL has been executed
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=0, HSN=2, HPN=0;
//Adding an AAU
ADD RRU: CN=0, SRN=60, SN=0, TP=TRUNK, RCN=0, PS=0, RT=AIRU, RS=LO, RXNUM=8,
TXNUM=8, MNTMODE=NORMAL, RFDCPWROFFALMDETECTSW=OFF;
//Adding a sector
ADD SECTOR: SECTORID=0, ANTNUM=0, CREATESECTOREQM=FALSE;
//Adding RET antennas for the cells (Pay attention to the information provided in
the note at the end of this section.)
MOD ANTENNAPORT: CN=0, SRN=60, SN=0, PN=R0A, PWRSWITCH=ON;
ADD RET: DEVICENO=0, CTRLCN=0, CTRLSRN=60, CTRLSN=0, RETTYPE=SINGLE_RET,
SCENARIO=DAISY_CHAIN, VENDORCODE="HW", SERIALNO="M2194G30002A01Ay1";
ADD RET: DEVICENO=1, CTRLCN=0, CTRLSRN=60, CTRLSN=0, RETTYPE=SINGLE_RET,
SCENARIO=DAISY_CHAIN, VENDORCODE="HW", SERIALNO="M2194G30001B01By1";
//Setting downtilt angles for the RET antennas (Typically, downtilt angle for the
inner cell = downtilt angle for the outer cell + 6 degrees)
MOD RETSUBUNIT:DEVICENO=0,SUBUNITNO=1,TILT=120;
MOD RETSUBUNIT:DEVICENO=1,SUBUNITNO=1,TILT=60;
//Adding back the following information as RMV CELL has been executed
ADD CELLOP: LocalCellId=0, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
ADD CELLOP: LocalCellId=1, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
//Setting power
MOD PDSCHCFG: LocalCellId=0, ReferenceSignalPwr=169;
MOD PDSCHCFG: LocalCellId=1, ReferenceSignalPwr=169;
The following is an example of MML commands used to reconstruct a 2T2R or 4T4R cell for
SSB at passive ports on an AAU.
//Removing original cell configurations
DEA CELL: LocalCellId=1;
RMV EUCELLSECTOREQM: LocalCellId=1, SectorEqmId=1;
RMV CELL: LocalCellId=1;
RMV SECTOREQM: SECTOREQMID=1;
RMV SECTOR: SECTORID=1;
//Adding back the following information as RMV CELL has been executed
ADD RRUCHAIN: RCN=1, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=0, HSN=2, HPN=0;
ADD RRUCHAIN: RCN=2, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=0, HSN=2, HPN=0;
//Adding a sector
ADD SECTOR: SECTORID=1, ANTNUM=8, ANT1CN=0, ANT1SRN=61, ANT1SN=0, ANT1N=R0A,
ANT2CN=0, ANT2SRN=61, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=61, ANT3SN=0,
ANT3N=R0C, ANT4CN=0, ANT4SRN=61, ANT4SN=0, ANT4N=R0D, ANT5CN=0, ANT5SRN=62,
ANT5SN=0, ANT5N=R0A, ANT6CN=0, ANT6SRN=62, ANT6SN=0, ANT6N=R0B, ANT7CN=0,
ANT7SRN=62, ANT7SN=0, ANT7N=R0C, ANT8CN=0, ANT8SRN=62, ANT8SN=0, ANT8N=R0D,
CREATESECTOREQM=FALSE;
//Adding RET antennas (Skip this step if RET antennas have been added for the
cells served by the active ports on the AAU.)
MOD ANTENNAPORT: CN=0, SRN=60, SN=0, PN=R0A, PWRSWITCH=ON;
ADD RET: DEVICENO=0, CTRLCN=0, CTRLSRN=60, CTRLSN=0, RETTYPE=SINGLE_RET,
SCENARIO=DAISY_CHAIN, VENDORCODE="HW", SERIALNO="M2194G30002A01Ay1";
ADD RET: DEVICENO=1, CTRLCN=0, CTRLSRN=60, CTRLSN=0, RETTYPE=SINGLE_RET,
SCENARIO=DAISY_CHAIN, VENDORCODE="HW", SERIALNO="M2194G30001B01By1";
/*Adding the relationships between the RRUs and the RET antennas
(Do not set the TILT parameter if it has been specified for the cells served by
the active ports on the AAU.)*/
MOD RETSUBUNIT: DEVICENO=0, SUBUNITNO=1, CONNCN1=0, CONNSRN1=61, CONNSN1=0,
CONNPN1=R0A, TILT=120;
MOD RETSUBUNIT: DEVICENO=1, SUBUNITNO=1, CONNCN1=0, CONNSRN1=62, CONNSN1=0,
CONNPN1=R0A, TILT=60;
//Adding back the following information as RMV CELL has been executed
ADD CELLOP: LocalCellId=2, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
//Setting power
MOD PDSCHCFG: LocalCellId=2, ReferenceSignalPwr=182;
MOD PDSCHCFG: LocalCellId=3, ReferenceSignalPwr=182;
//Enabling passive-port channel calibration for the AAU (The period must be 30
min for both inner and outer cells. If the two cells have different period
settings, the value for the outer cell takes effect in both cells.)
MOD RRUJOINTCALPARACFG: LOCALCELLID=2, AauPassivePortCalibPeriod=6;
MOD RRUJOINTCALPARACFG: LOCALCELLID=3, AauPassivePortCalibPeriod=6;
//Activating the cells (Cells served by the passive ports on an AAU can be
activated only when the relationships between the RRUs and the RET antennas have
been added.)
ACT CELL: LOCALCELLID=2;
ACT CELL: LOCALCELLID=3;
NOTE
The serial number of each RET antenna can be queried by running the SCN ALD command.
If the sixth digit from right to left of a serial number is A (for example, M2194G30002A01Ay1), the
RET antenna must be configured to serve the inner cell. If the digit is B (for example,
M2194G30001B01By1), the RET antenna must be configured to serve the outer cell.
Figure 3-3 Example scatter diagram of PRB usage and traffic volume
4 8T8R Cells
4.1 Principles
Each AAU can be configured to serve one or more 8T8R cells. The cell bandwidth must be at
least 5 MHz. In these cells, 8-antenna receive diversity is available in the uplink, and 4x2 or
4x4 MIMO is available in the downlink. Transmission mode 9 (TM9) is currently not
supported. For details about MIMO, see MIMO Feature Parameter Description.
Uplink 8-antenna receive diversity requires at least eight receive channels. The eight receive
channels can receive a single UE's signals from different directions to improve reception
quality.
The numbers of receive and transmit channels for individual cells are specified by the
Cell.TxRxMode parameter.
4.2.1 Benefits
Uplink 8-antenna receive diversity in 8T8R cells offers the following benefits over uplink 2-
antenna receive diversity.
Gains Impact Factor
The average uplink UE throughput increases For a single UE, the farther it is from the
by 10% to 70%. cell center, the higher the gains are.
For a cell, the more the cell-edge UEs, the
higher the gains.
4.2.2 Impacts
Network Impacts
None
Feature Impacts
Feature ID/ Feature/Function Description
Function Switch Name
4.3 Requirements
4.3.1 Licenses
This function requires the license for 3D Beamforming. The other two licenses in the
following table are recommended so that this function can achieve its optimal performance.
Feature ID Feature Name Model Sales Unit
The license in the following table is recommended for networks with a high penetration rate
of 4R UEs to achieve the optimal performance of this function.
4.3.2 Software
Prerequisite Features
None
LAOFD-120201 DL CoMP
LOFD-001031 Extended CP
4.3.3 Hardware
Boards
The BBPs must be UBBPe4 boards.
RF Modules
AAU5972s must be used.
AAU5972s in the 1.8 GHz band contain both radio and antenna modules. Power supplies
must be directly connected to the AAUs, and those AAUs must be connected to the BBUs of
eNodeBs through CPRI optical cables. AAU5972s in other bands contain only antenna
modules. They must be connected to external radio units. These AAUs supply power to the
radio units, which are then connected to BBUs through CPRI optical cables. For details about
how to install AAU5972s, see AAU5972 Installation Guide.
The following are the constraints on the maximum power per channel in AAU5972s:
l For AAU5972s in the 1.8 GHz band, the power must not exceed 47.7 dBm. (The
maximum power configuration is 4 x 60 W. For example, CRS power is 19.9 dBm, PA is
–3, and PB is 1 for a 20 MHz cell.)
l For AAU5972s in other bands, the power must not exceed 49 dBm. (The maximum
power configuration is 4 x 80 W. For example, CRS power is 21.2 dBm, PA is –3, and
PB is 1 for a 20 MHz cell.)
4.3.4 Others
No requirements
Parameters
Table 4-1 describes the parameters used for function activation. This section does not
describe the parameters related to cell establishment.
//Setting the following data if the cabinet number, subrack number, and slot
number of the AAU are different from those of the previous RRU
//(Skip this command if the cabinet number, subrack number, and slot number of
the AAU are the same as those of the previous RRU.)
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=0, HSN=2, HPN=0;
The following is an example of MML commands used to reconstruct a 2T2R or 4T4R cell
into an 8T8R cell at passive ports on an AAU.
//Deactivating the original cell
DEA CELL: LocalCellId=1;
//Removing the original antennas
RMV RET: DEVICENO=1, CTRLCN=0, CTRLSRN=61, CTRLSN=0, RETTYPE=SINGLE_RET,
SCENARIO=DAISY_CHAIN, VENDORCODE="HW";
//Adding RET antennas (Skip this step if RET antennas have been added for the
cells served by the active ports on the AAU.)
MOD ANTENNAPORT: CN=0, SRN=60, SN=0, PN=R0A, PWRSWITCH=ON;
ADD RET: DEVICENO=0, CTRLCN=0, CTRLSRN=60, CTRLSN=0, RETTYPE=SINGLE_RET,
SCENARIO=DAISY_CHAIN, VENDORCODE="HW", SERIALNO="M2194G30002A01Ay1";
ADD RET: DEVICENO=1, CTRLCN=0, CTRLSRN=60, CTRLSN=0, RETTYPE=SINGLE_RET,
SCENARIO=DAISY_CHAIN, VENDORCODE="HW", SERIALNO="M2194G30001B01By1";
//Adding the relationships between the RRUs and the RET antennas (Do not set the
TILT parameter if it has been specified for the cells served by the active ports
on the AAU.)
MOD RETSUBUNIT: DEVICENO=0, SUBUNITNO=1, CONNCN1=0, CONNSRN1=61, CONNSN1=0,
CONNPN1=R0A, TILT=60;
MOD RETSUBUNIT: DEVICENO=1, SUBUNITNO=1, CONNCN1=0, CONNSRN1=62, CONNSN1=0,
CONNPN1=R0A, TILT=60;
//Activating the cell (Cells served by the passive ports on an AAU can be
activated only when the relationships between the RRUs and the RET antennas have
been added.)
ACT CELL: LOCALCELLID=1;
On the U2000 client, start a received signal strength indicator (RSSI) monitoring task to
monitor the RSSIs of antennas. If the RSSIs of antennas 0 to 7 are all valid values, uplink 8-
antenna receive diversity has taken effect.
5 Parameters
RETSU TILT MOD MRFD- Connect Meaning: Indicates the antenna tilt of the RET
BUNIT RETSU 210601 ion with subunit. If this parameter is set to 32767, it is invalid
BUNIT MRFD- TMA and the actual tilt is not changed.
MOD 210602 (Tower GUI Value Range: -300~300,32767
RETTIL Mounte
WRFD- d Unit: 0.1degree
T 060003 Amplifi Actual Value Range: -30~30,3276.7, step:0.1
LST LEOFD- er)
RETSU Default Value: 32767
121204 Remote
BUNIT
Electrica
l Tilt
Same
Band
Antenna
Sharing
Unit
(900Mh
z)
3D
Beamfor
ming
CellVM VmsHo MOD LEOFD- 3D Meaning: Indicates the maximum number of UEs that
S UeNum CELLV 121204 Beamfor can be transferred within 10s. This parameter is used
Th MS ming to prevent too many UEs from being transferred at a
LST time to neighboring cells to cause significant impact
CELLV on neighboring cells. This parameter applies only to
MS LTE FDD.
GUI Value Range: 1~10
Unit: None
Actual Value Range: 1~10
Default Value: 1
CellVM VmsPrb MOD LEOFD- 3D Meaning: Indicates the PRB usage threshold for
S LoadTh CELLV 121204 Beamfor triggering MLB. MLB is triggered if the PRB usage of
MS ming the serving cell is higher than this parameter value.
LST This parameter applies only to LTE FDD.
CELLV GUI Value Range: 1~99
MS Unit: %
Actual Value Range: 1~99
Default Value: 80
CellVM VmsPrb MOD LEOFD- 3D Meaning: Indicates the threshold of PRB usage
S DiffTh CELLV 121204 Beamfor difference between the serving cell and a neighboring
MS ming cell. When the result of the PRB usage of the serving
LST cell minus that of a neighboring cell in a cluster is
CELLV greater than the parameter value, this neighboring cell
MS can be a target cell for MLB. This parameter applies
only to LTE FDD.
GUI Value Range: 1~99
Unit: %
Actual Value Range: 1~99
Default Value: 40
IntraFre IntraFre ADD LBFD-0 Coverag Meaning: Indicates the offset for event A3. If the
qHoGro qHoA3 INTRA 0201801 e Based parameter is set to a large value, an intra-frequency
up Offset FREQH / Intra- handover is performed only when the signal quality of
OGROU TDLBF frequenc the neighboring cell is significantly better than that of
P D-00201 y the serving cell and other triggering conditions are
MOD 801 Handov met. For details, see 3GPP TS 36.331. This parameter
INTRA LEOFD- er applies only to LTE FDD and LTE TDD.
FREQH 121204 3D GUI Value Range: -30~30
OGROU Beamfor Unit: 0.5dB
P ming
Actual Value Range: -15~15
LST
INTRA Default Value: 2
FREQH
OGROU
P
ENodeB EutranV MOD TDLBF Support Meaning: Indicates whether the VoIP services are
AlgoSwi oipSupp ENODE D-08110 of enabled in the E-UTRAN cell. This parameter is used
tch ortSwitc BALGO 1 VoLTE for determining whether the establishment, incoming
h SWITC handover , admission, and reestablishment of VoIP
H services is allowed. This parameter applies only to
LST LTE FDD and LTE TDD.
ENODE GUI Value Range: OFF(Off), ON(On)
BALGO Unit: None
SWITC
H Actual Value Range: OFF, ON
Default Value: ON(On)
EDlMaxTXPwrSwitch:Off,
BFModeUserPwrSwitch:Off, SigPowerIncreaseS-
witch:Off, BFModeUserAdptPwrSwitch:Off,
BfEnhChnPwrFormSwitch:Off, DlNonStandardBw-
MaxPwrSwitch:Off
CellAlg PwrDera MOD LEOFD- 3D Meaning: Indicates whether to apply the power
oSwitch tSwitch CELLA 121204 Beamfor decrease mechanism on reference signal (RS) power
LGOSW ming and physical synchronization channel (PSCH) power.
ITCH If this parameter is set OFF, the physical downlink
LST shared channel (PDSCH) transmit power is lowered,
CELLA the RS power and PSCH power are not lowered. If
LGOSW this parameter is set to ON, all of the PDSCH power,
ITCH RS power, and PSCH power are lowered. This
parameter applies only to LTE FDD and LTE TDD.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
SECTO ANTCF ADD None None Meaning: Indicates the antenna configuration mode of
REQM GMOD SECTO sector equipment. If this parameter is set to
E REQM ANTENNAPORT, the antenna port list must be
MOD configured. If this parameter is set to BEAM, RRU
SECTO and beamforming parameters must be configured.
REQM This parameter can be set to BEAM only on the LTE
side.
LST
SECTO GUI Value Range:
REQM ANTENNAPORT(ANTENNAPORT),
BEAM(BEAM)
Unit: None
Actual Value Range: ANTENNAPORT, BEAM
Default Value: ANTENNAPORT(ANTENNAPORT)
eUCellS CellBea ADD LEOFD- eMIMO Meaning: Indicates the beamforming attribute of the
ectorEq mMode EUCEL 111307 cell. This parameter has three values: NORMAL,
m LSECT ADVANCED_BEAMFORMING, and
OREQ MASSIVE_MIMO_Ph1. The value NORMAL
M indicates that the cell is a normal cell. The value
MOD ADVANCED_BEAMFORMING indicates that the
EUCEL cell uses AAU-based advanced beamforming. The
LSECT value MASSIVE_MIMO_Ph1 indicates that the cell is
OREQ a massive MIMO Ph1 cell. This parameter applies
M only to LTE FDD.
LST GUI Value Range: NORMAL(NORMAL),
EUCEL ADVANCED_BEAMFORMING(ADVANCED_BEA
LSECT MFORMING),
OREQ MASSIVE_MIMO_Ph1(MASSIVE_MIMO_Ph1)
M Unit: None
Actual Value Range: NORMAL,
ADVANCED_BEAMFORMING,
MASSIVE_MIMO_Ph1
Default Value: NORMAL(NORMAL)
SECTO RRUCN ADD None None Meaning: Indicates the cabinet number of the RRU to
REQM SECTO which a sector antenna is connected. The parameter
REQM takes effect only in LTE.
MOD GUI Value Range: 0~62
SECTO Unit: None
REQM
Actual Value Range: 0~62
LST
SECTO Default Value: None
REQM
SECTO RRUSR ADD None None Meaning: Indicates the subrack number of the RRU to
REQM N SECTO which a sector antenna is connected. The parameter
REQM takes effect only in LTE.
MOD GUI Value Range: 4~5,60~254
SECTO Unit: None
REQM
Actual Value Range: 4~5,60~254
LST
SECTO Default Value: None
REQM
SECTO RRUSN ADD None None Meaning: Indicates the slot number of the RRU to
REQM SECTO which a sector antenna is connected. The parameter
REQM takes effect only in LTE.
MOD GUI Value Range: 0~8
SECTO Unit: None
REQM
Actual Value Range: 0~8
LST
SECTO Default Value: None
REQM
SECTO BEAMS ADD None None Meaning: Indicates the beam coverage shape of sector
REQM HAPE SECTO equipment, specified by the expanding angle of a
REQM sector. The parameter takes effect only in LTE.
MOD GUI Value Range: SEC_120DEG(SEC_120DEG),
SECTO SEC_60DEG(SEC_60DEG),
REQM SEC_90DEG(SEC_90DEG),
LST SEC_180DEG(SEC_180DEG)
SECTO Unit: None
REQM Actual Value Range: SEC_120DEG, SEC_60DEG,
SEC_90DEG, SEC_180DEG
Default Value: None
SECTO BEAM ADD None None Meaning: Indicates the azimuth offset of the main lobe
REQM AZIMU SECTO direction of horizontal beam coverage and the RF
THOFF REQM module direction. If this parameter is set to None, the
SET MOD main lobe of beams and RF module are in the same
SECTO direction. If this parameter is set to LEFT_HALF, the
REQM azimuth deflects 1/2 sector angle counterclockwise. If
this parameter is set to RIGHT_HALF, the azimuth
LST deflects 1/2 sector angle clockwise. For example, the
SECTO horizontal azimuth deflects 60° counterclockwise with
REQM BEAMSHAPE set to SEC_120DEG and
BEAMAZIMUTHOFFSET set to LEFT_HALF. The
parameter takes effect only in LTE.
GUI Value Range: None(None),
LEFT_HALF(LEFT_HALF),
RIGHT_HALF(RIGHT_HALF)
Unit: None
Actual Value Range: None, LEFT_HALF,
RIGHT_HALF
Default Value: None
SECTO BEAML ADD None None Meaning: Indicates the vertical beam split. If this
REQM AYERS SECTO parameter is set to None, the vertical coverage area is
PLIT REQM not split. If this parameter is set to INNER_LAYER,
MOD the inner sector is covered after a beam layer split. If
SECTO this parameter is set to OUTER_LAYER, the outer
REQM sector is covered after a beam layer split. The
parameter takes effect only in LTE.
LST
SECTO GUI Value Range: None(None),
REQM INNER_LAYER(INNER_LAYER),
OUTER_LAYER(OUTER_LAYER)
Unit: None
Actual Value Range: None, INNER_LAYER,
OUTER_LAYER
Default Value: None
Cell TxRxM ADD None None Meaning: Indicates the transmission and reception
ode CELL mode of the cell.
MOD GUI Value Range: 1T1R, 1T2R, 2T2R, 2T4R, 4T4R,
CELL 8T8R, 2T8R, 4T8R, 64T64R
LST Unit: None
CELL Actual Value Range: 1T1R, 1T2R, 2T2R, 2T4R,
4T4R, 8T8R, 2T8R, 4T8R, 64T64R
Default Value: None
CellAlg DynAdj MOD LOFD-0 Adaptiv Meaning: Indicates the switch used to enable or
oSwitch VoltSwit CELLA 01025 e Power disable dynamic voltage adjustment. If this switch is
ch LGOSW Consum on, the power amplifier (PA) bias voltage is adjusted
ITCH ption based on the load of the eNodeB, which reduces
LST power consumption of the PA and improves energy
CELLA efficiency of the eNodeB. Dynamic voltage
LGOSW adjustment applies only to FDD cells with a
ITCH bandwidth higher than 5 MHz. This parameter applies
only to LTE FDD.
GUI Value Range:
DynAdjVoltSwitch(DynAdjVoltSwitch)
Unit: None
Actual Value Range: DynAdjVoltSwitch
Default Value: DynAdjVoltSwitch:Off
6 Counters
7 Glossary
8 Reference Documents