Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Issue Draft A
Date 2018-12-30
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
1 Change History.............................................................................................................................. 1
1.1 eRAN15.1 Draft A (2018-12-30)................................................................................................................................... 1
3 Overview......................................................................................................................................... 5
4 Intra-Frequency Split.................................................................................................................... 8
4.1 Principles........................................................................................................................................................................ 8
4.2 Network Analysis......................................................................................................................................................... 14
4.2.1 Benefits...................................................................................................................................................................... 14
4.2.2 Impacts.......................................................................................................................................................................16
4.3 Requirements................................................................................................................................................................ 18
4.3.1 Licenses..................................................................................................................................................................... 18
4.3.2 Software.....................................................................................................................................................................19
4.3.3 Hardware................................................................................................................................................................... 21
4.3.4 Others.........................................................................................................................................................................23
4.4 Operation and Maintenance..........................................................................................................................................24
4.4.1 Data Configuration.................................................................................................................................................... 24
4.4.1.1 Data Preparation..................................................................................................................................................... 24
4.4.1.2 Using MML Commands......................................................................................................................................... 29
4.4.1.3 Using the CME....................................................................................................................................................... 33
4.4.2 Activation Verification.............................................................................................................................................. 33
4.4.3 Network Monitoring.................................................................................................................................................. 34
5 Inter-Frequency Split.................................................................................................................. 38
5.1 Principles...................................................................................................................................................................... 38
5.2 Network Analysis......................................................................................................................................................... 38
5.2.1 Benefits...................................................................................................................................................................... 38
5.2.2 Impacts.......................................................................................................................................................................39
5.3 Requirements................................................................................................................................................................ 39
5.3.1 Licenses..................................................................................................................................................................... 39
5.3.2 Software.....................................................................................................................................................................39
5.3.3 Hardware................................................................................................................................................................... 40
5.3.4 Others.........................................................................................................................................................................41
5.4 Operation and Maintenance..........................................................................................................................................41
5.4.1 Data Configuration.................................................................................................................................................... 41
5.4.1.1 Data Preparation..................................................................................................................................................... 41
5.4.1.2 Using MML Commands......................................................................................................................................... 44
5.4.1.3 Using the CME....................................................................................................................................................... 46
5.4.2 Activation Verification.............................................................................................................................................. 46
5.4.3 Network Monitoring.................................................................................................................................................. 47
6 Parameters..................................................................................................................................... 48
7 Counters........................................................................................................................................ 49
8 Glossary......................................................................................................................................... 50
9 Reference Documents................................................................................................................. 51
1 Change History
This chapter describes changes not included in the "Parameters", "Counters", "Glossary", and
"Reference Documents" chapters. These changes include:
l Technical changes
Changes in functions and their corresponding parameters
l Editorial changes
Improvements or revisions to the documentation
Technical Changes
Change Description Parameter Change Base Station Model
Added soft split PDCCH Added the 3900 and 5900 series base
allocation optimization. For SsrdPdcchAllocOptSwitch stations
details, see 4.1 Principles. option to the
ENodeBAlgoSwitch.SSRD
AlgoSwitch parameter.
Editorial Changes
Revised descriptions in this document.
This document only provides guidance for feature activation. Feature deployment and feature
gains depend on the specifics of the network scenario where the feature is deployed. To achieve
the desired gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this document
apply only to the corresponding software release. For future software releases, refer to the
corresponding updated product documentation.
Trial Features
Trial features are features that are not yet ready for full commercial release for certain
reasons. For example, the industry chain (terminals/CN) may not be sufficiently compatible.
However, these features can still be used for testing purposes or commercial network trials.
Anyone who desires to use the trial features shall contact Huawei and enter into a
memorandum of understanding (MoU) with Huawei prior to an official application of such
trial features. Trial features are not for sale in the current version but customers may try them
for free.
Customers acknowledge and undertake that trial features may have a certain degree of risk
due to absence of commercial testing. Before using them, customers shall fully understand not
only the expected benefits of such trial features but also the possible impact they may exert on
the network. In addition, customers acknowledge and undertake that since trial features are
free, Huawei is not liable for any trial feature malfunctions or any losses incurred by using the
trial features. Huawei does not promise that problems with trial features will be resolved in
the current version. Huawei reserves the rights to convert trial features into commercial
features in later R/C versions. If trial features are converted into commercial features in a later
version, customers shall pay a licensing fee to obtain the relevant licenses prior to using the
said commercial features. If a customer fails to purchase such a license, the trial feature(s)
will be invalidated automatically when the product is upgraded.
3 Overview
Soft split resource duplex (SSRD), or soft split, splits one cell into two cells, each covering
different areas. This feature uses baseband weighting to create two beams that are orthogonal
to each other, as shown in Figure 3-1.
Figure 3-2 shows a beam before and after SSRD. The red and blue beams after the split each
serve an independent cell. UEs in two cells from a split access the network separately,
perform their own neighboring cell measurements, and are handed over independent of each
other. The eNodeB determines which beam serves a UE based on the reference signal
received power (RSRP) of a UE on each beam, and then selects UEs served by an orthogonal
beam group for pairing. In this way, time-frequency resources are reused, increasing the cell
throughput.
SSRD improves eNodeB capacity by increasing the number of cells without adding new sites,
as shown in Figure 3-5.
4 Intra-Frequency Split
4.1 Principles
The basic function of intra-frequency split is not under switch control. Intra-frequency cells
from a split cannot fully leverage RB resources if their physical resource block (PRB) usages
are low or there is a huge difference of the PRB usage between the cells, limiting gains from
the split. If a large proportion of UEs reside in an area where two split beams overlap, RBs
may not be reused for these UEs, and gains offered by an intra-frequency split is limited.
Intra-frequency split provides the following enhanced functions to resolve these issues.
Step Description
Enable multi- This function can be enabled before or after a split. This function does
beam not cause deterioration in cell performance before a split.
measurement. Figure 4-3 to Figure 4-6 show the measurement beams. x and y indicate
the azimuths of the red and blue beams. A negative value indicates a
clockwise beam deflection from the center.
NOTE
If soft split multi-beam measurement is not deployed, only one beam group is
used for intra-frequency split measurement, as shown in Figure 4-3.
Analyze Use the soft split design tool to analyze measurements and evaluate
measurements. whether the cell is suitable for an intra-frequency split.
NOTE
For details about the soft split design tool, contact Huawei engineers.
Step Description
Figure 4-3 Orthogonal and mutually exclusive beam group 0 (beam azimuths: 30° and –30°)
Figure 4-4 Orthogonal and mutually exclusive beam group 1 (beam azimuths: –45° and 15°)
Figure 4-5 Orthogonal and mutually exclusive beam group 2 (beam azimuths: –60° and 0°)
Figure 4-6 Orthogonal and mutually exclusive beam group 3 (beam azimuths: 45° and –15°)
PDCCH allocation failure rate of paired UEs or joint-scheduling UEs is high, this function
increases the downlink modulation and coding scheme (MCS) index, the downlink PRB
usage, and the number of paired RBs. As a result, the downlink cell throughput, downlink
spectral efficiency, and downlink user-perceived rate improve.
The resource allocation algorithm requires the scheduling optimization algorithm. Therefore,
soft split PDCCH allocation optimization requires soft split scheduling optimization.
4.2.1 Benefits
When to Use
l An intra-frequency split is recommended for macro eNodeBs with three sectors working
in 8T8R mode. The gains are larger for heavily-loaded eNodeBs. An intra-frequency
split is recommended for continuous coverage. This facilitates network planning and
improves overall network performance.
l An intra-frequency split is recommended when all of the following conditions are met:
– The RSRP of the cell (before being split) exceeds –90 dBm.
– The cell edge level exceeds –110 dBm.
– Only services of CQIs 8 to 11 are ongoing, and the eNodeB is heavily loaded.
– A large number of UEs have assessed the network.
– Capacity expansion is required.
The total combined power of the two intra-frequency cells after the split must be greater
than or equal to the power of the original cell.
NOTE
l To obtain the downlink RSRP, subscribe to periodic measurement reports (MRs) from UEs.
l Average downlink RSRP refers to the average downlink RSRP of all UEs in the cell for which
SSRD is enabled.
l The edge level of the cell for which SSRD is enabled equals the value at the point where the
CDF distribution of the downlink RSRP of all UEs in the cell is 5%.
l An intra-frequency split increases the number of cell edges. As such, it is not suitable in
scenarios where coverage is limited, such as urban areas where there are a large number
of high-rise buildings.
l If you plan to enable an intra-frequency split for an area, first enable soft split multi-
beam measurement and then use the soft split design tool to analyze whether an intra-
frequency split is suitable for the area and determine the optimal beam group.
l If the network is heavily loaded or the loads of two cells from a split are unbalanced, it is
recommended that you enable soft split scheduling optimization and soft split downlink
power sharing.
l It is recommended that soft split PDCCH allocation optimization be enabled when the
PDCCH allocation failure rate is high on heavy-load networks.
Gains
NOTE
The gains offered by intra-frequency split are subject to network conditions, such as interference,
networking mode, user distribution, and user services. If most UEs reside in one of the two cells split
from a sector, an intra-frequency split may reduce the user-perceived rate and cell capacity. If the
proportion of rank 2 UEs before a split is high (over 50%), gains offered by an intra-frequency split are
smaller.
l Two cells from a split perform uplink scheduling and receive data independently,
doubling the uplink resource reuse rate.
NOTE
If an RB is allocated to both cells from a split, interference increases by 2 dB to 5 dB. The actual
interference is dependent on many factors, including user distribution and uplink load. Such an
interference increase does not have a great impact on uplink demodulation performance,
particularly the IBLER, which would remain stable in the case of such an interference increase.
l In contrast with adaptation between 8T8R beamforming and MIMO (without MU
beamforming), this function produces the following benefits when UEs are evenly
distributed:
– The average spectral efficiency of two cells from a split increases by 25% to 30%.
– The total throughput of two cells from a split is 25% to 30% greater than that of the
original cell when they are fully loaded.
l If there is a huge difference between the numbers of UEs in the two cells from a split, the
following functions are recommended to achieve optimal performance:
– Soft split beam adjustment: This function improves the spectral efficiency of the
optimal beam serving a single cell by 20% and capacity of a split cell by about
10%. In contrast with the scenario where only the basic function of intra-frequency
split is enabled, the average downlink SINR in the cell increases by up to 1 dB
when soft split multi-beam measurement is enabled.
– Soft split scheduling optimization: This function produces gains which depend on
the proportion of UEs in the area where two beams overlap (which is only 5% to
10% if UEs are evenly distributed in the cell) and the ratio of UEs in the primary
cell to those in the split cell. If the proportion of UEs in the area where two beams
overlap is greater than 20% or the ratio of UEs in the primary cell to those in the
split cell exceeds 3:1, joint scheduling is performed for two cells to improve
capacity of the heavy-load cell. The capacity increase is calculated by the following
formula:
Capacity increase in the heavy-load cell = 10% x Proportion of remaining PRBs
allocated to the light-load cell
– It is recommended that soft split scheduling optimization and soft split downlink
power sharing be enabled to further increase the capacity of heavy-load cells (by
about 5%) and average throughput of heavy-load split cells (by about 10%).
– If the PDCCH allocation failure rate is high on heavy-load networks, it is
recommended that soft split PDCCH allocation optimization be enabled to improve
the pairing success rate, MCS index after pairing, and downlink cell throughput.
l Intra-frequency split achieves the best performance if the following optional
requirements are met:
– The coverage angle of the sector of the cell before split ranges from 100° to 140°.
– The average inter-site distance is less than 2000 m.
– The downlink PRB usage is greater than 80% during busy hours.
– The proportion of high-speed UEs (moving speed greater than 30 km/h) is less than
30%.
4.2.2 Impacts
Network Impacts
l The number of cells in the same coverage area is doubled and the number of inter-cell
handovers increases, slightly affecting the handover success rate and service drop rate in
the area covered by the original cell.
l The cell signal strength will be slightly weaker for UEs in the area where the two cells
from a split overlap, and the experience of such UEs will deteriorate in light-load
scenarios. This is because beams fade in such an area.
l Assuming the same amount of total power is used for two cells from a split as that used
for the original cell, the average coverage level of two cells from a split decreases by
approximately 0.5 dB, and the average downlink SINR in the cells also decreases.
l Due to an increase in the number of cells and neighboring cells after a split, interference
is more likely to occur, and the average cell CQI decreases by 1 dB to 2 dB. The
decrease in the average QCI varies in different scenarios, because different scenarios
have different CQI baselines.
l The average modulation and coding scheme (MCS) index decreases by a larger margin
than the average CQI. This is because the CQI decrease also affects the MCS index. The
decrease in the average cell MCS index varies in different scenarios.
l Two cells from a split have the same PCI mod 3 value. As a result, UEs in the area where
coverage of the two cells overlaps experience severe CRS interference, and the DTX
proportion, IBLER, and RBLER slightly increase. After a split, the proportions of TM9
UEs, TM9 rank 3 UEs, and TM9 rank 4 UEs decrease.
l If there are many active UEs, soft split PDCCH allocation optimization may increase the
downlink CCE allocation failure rate. Downlink CCE allocation failure rate =
L.ChMeas.CCE.DL.AllocFail/(L.ChMeas.PDCCH.AggLvl1Num +
L.ChMeas.PDCCH.AggLvl2Num + L.ChMeas.PDCCH.AggLvl4Num +
L.ChMeas.PDCCH.AggLvl8Num + L.ChMeas.CCE.DL.AllocFail)
Function Impacts
Function Function Switch Reference Description
Name
4.3 Requirements
4.3.1 Licenses
Data configurations of the new cell from a split must be the same as those of the cell before a
split. PCIs of cells after a split should be set to that of the new split cell. You need to apply for
licenses of features that need to be deployed for the new split cell.
To implement intra-frequency split, a cell needs to be added on the RRU serving the original
cell. For details about applying licenses of adding a cell on an RRU, see License
Management.
The following capacity licenses can be applied for only based on the primary cell. Other
capacity licenses need to be applied for based on the split cell.
l UBBP First-Mode License(LTE TDD)
l RF Output Power (per 20W)(TDD)
l RF Transmit Channel (per Channel)(TDD)
l RF Receive Channel (per Channel)(TDD)
NOTE
See Table 4-1. If common public radio interface (CPRI) compression is required, purchase the
corresponding license. For details, see CPRI Compression.
4.3.2 Software
Prerequisite Functions
Function Function Switch Reference Description
Name
4.3.3 Hardware
Boards
l The UBBPd9 or UBBPe (including UBBPe4, UBBPe6, and UBBPei) must be used, and
the BBP.CCNE parameter must be set to ON if the UBBPd9 is used.
l The BBP and primary BBP specified for a cell from a split must be the same board.
l Two cells in a split cell group must be served by the same BBP.
l If common cells and cells from a split are served by the same BBP:
– All cells must be bound with the baseband equipment specific to this BBP.
– 8T8R cells from a split and 4T4R common cells cannot be served by the same BBP.
l If the number of physical cells exceeds the BBP specifications, baseband equipment
serving these cells must be bound to the BBP.
l For the cell quantity specifications of BBP boards supporting intra-frequency split after
normal CPRI compression, see Table 4-1. If normal CPRI compression is not in use,
these specifications may not be supported.
l The CPRI compression bandwidth requirements do not change after intra-frequency
split.
NOTE
RF Modules
8T8R RRUs supporting external channel calibration (with a CAL port)
Cells
l PCI planning
– The PCIs of two cells from a split must be different.
– PCI mod 3 values of two cells from a split must be the same. For example, the PCIs
of two cells in a split cell group can be set to 0 and 3.
– For cells before a split, use an identical PCI planning policy for eNodeBs providing
contiguous coverage. For example, PCI mod 3 values of such eNodeBs must be
either the same or different.
l Neighboring cell configuration: Neighboring cells need to be added for cells from a split
which function as normal logical cells. Neighboring cells can be manually or
automatically added. For how to add neighboring cells automatically, see ANR
Management.
l Power configuration: The total power of the two intra-frequency cells from a split must
be greater than or equal to that before the split.
l Antenna: The equivalent array spacing for antenna working frequencies is 0.46 to 0.54
times the wavelength. Huawei ATD4516R5 or ATD4516R8 antennas must be used.
SSRD is implemented on antennas with a 90-degree beamwidth for each antenna
element. If three sectors are deployed using such antennas, an antenna weight must be
configured, and the BfAnt.BEAMWIDTH parameter must be set to 65. For details, see
Antenna Weight Management (TDD). If 3-sector networking is changed to 6-sector
networking, you are advised to retain the parameter settings in the BfAnt MO for the
original wide-beam antennas for possible restoration of 3-sector networking.
4.3.4 Others
Due to new functions or features, new beam weight files may be introduced in the new
software version after an upgrade. When upgrading or rolling back the software version,
perform operations on the beam weight file according to the following table.
The new beam weight file is The beam weight file does The original beam weight
not used in the target not need to be activated. file does not need to be
software version. activated.
The new beam weight file is Run the ACT BFANTDB Run the ACT BFANTDB
used in the target software command to reactivate the command to activate the
version. beam weight file. original beam weight file.
NOTE
If a new beam weight file is installed after a software upgrade and then a software rollback is performed:
l Before the original beam weight file is activated, the new beam weight file is still stored in the
eNodeB.
l After the old beam weight file is activated, the new beam weight file is deleted.
Primary Local Cell SsrdCellGroup.Pri A cell splits into a primary cell and a split
ID maryLocalCellID cell after intra-frequency split.
l For a newly deployed eNodeB, add two
cells, one as the primary cell and the
other as the split cell.
l For an existing eNodeB, add only one
cell that is used as the split cell. The
existing cell functions as the primary
cell.
Weight Number eUCellSectorEqm. The weight numbers of the primary cell and
WeightNo split cell must be different. The weight
numbers must be set to the antenna device
number of the cells.
NOTE
To query the antenna device number, run the
DSP BFANT command. Determine the antenna
device number for a cell based on the queried
amplitude and phase.
TDD SRS SRSCfg.TddSrsCfg The settings of this parameter for the two
Configuration Mode Mode cells from a split must be the same. They
must be either
EXPERIENCE_ENHANCED or
ACCESS_ENHANCED.
NOTE
To enable two intra-frequency cells split from a cell to support TM9, set the following TM9-related
parameters consistently for both cells. For detailed parameter settings, see Beamforming (TDD).
l TM9Switch option of the CellAlgoSwitch.EnhMIMOSwitch parameter
l CellCsiRsParaCfg.CsiRsSwitch
l CellCsiRsParaCfg.CsiRsPeriod
l CellCsiRsParaCfg.CsiRsConfigUserNumTh
l CellCsiRsParaCfg.CsiRsConfigUserRatioTh
l CellCsiRsParaCfg.CsiRsUnconfigUserNumTh
l CellCsiRsParaCfg.CsiRsUnconfigUserRatioTh
l CellDlschAlgo.MaxMimoRankPara (This parameter must be set to SW_MAX_SM_RANK_4
because intra-frequency split supports a maximum of four layers in TM9.)
l CellCsiRsParaCfg.CsiRsSetJudgeTimer
l CellCsiRsParaCfg.CsiRsSetJudgeHysTimer
l CellCsiRsParaCfg.CsiRsPortNum
a: A split increases uplink interference. Smart interference rejection combining (IRC) and
physical uplink control channel (PUCCH) IRC can be enabled to reduce interference
caused by an intra-frequency split. For details about IRC, see MRC and IRC Receivers.
b: A value greater than 0 leads to smaller values of the following counters than the value 0
and may lead to a decrease in the cell throughput. A value less than 0 leads to higher values
of the following counters and may lead to an increase in the cell throughput.
l L.Traffic.PRB.SSRD.DLMIMOCoBF.Avg
l L.Traffic.PRB.SSRD.DLBFCoBF.Avg
l L.Traffic.PRB.SSRD.DLBFCoMIMO.Avg
The parameter settings in the following examples are used for reference only. Set the parameters based
on network requirements, for example, the TILT parameter in the ADD BFANT command.
l eNodeB reconstruction
//Deactivating the original cell
DEA CELL: LOCALCELLID=0;
//Changing the settings of the MultiCellShareMode and CPRICompression
parameters for the original cell
MOD CELL: LOCALCELLID=0, CPRICOMPRESSION=NORMAL_COMPRESSION,
MULTICELLSHAREMODE=SPLIT;
//Adding a split cell
ADD CELL:
LOCALCELLID=100,CELLNAME="CELL_SSRD_100",FREQBAND=41,ULEARFCNCFGIND=NOT_CFG,DL
EARFCN=40340,ULBANDWIDTH=CELL_BW_N100,DLBANDWIDTH=CELL_BW_N100,CELLID=100,PHYC
ELLID=100,FDDTDDIND=CELL_TDD,SUBFRAMEASSIGNMENT=SA2,SPECIALSUBFRAMEPATTERNS=SS
P7,ROOTSEQUENCEIDX=0,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=N
OT_CFG,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_FALSE,CPRICOMPRESSION
=NORMAL_COMPRESSION,TXRXMODE=8T8R,MULTICELLSHAREMODE=SPLIT;
//Activating the weight database file
ACT BFANTDB: OPMODE=SWFILE;
//Adding beamforming antennas
ADD BFANT: DEVICENO=11, MANUFACTORY=HuaweiAgisson, CONNSRN=60,
MODELNO="Soft_Split_Left_BandD2",TILT=6,BAND=41;
ADD BFANT: DEVICENO=12, MANUFACTORY=HuaweiAgisson, CONNSRN=60,
MODELNO="Soft_Split_Right_BandD2",TILT=6,BAND=41;
//Associating the two cells with the same sector equipment and setting the
weight numbers
ADD EUCELLSECTOREQM: LOCALCELLID=100, SECTOREQMID=0, WEIGHTNO=12,
CELLBEAMMODE=NORMAL;
MOD EUCELLSECTOREQM: LOCALCELLID=0, SECTOREQMID=0, WEIGHTNO=11;
//Adding the two cells to a split cell group
ADD SSRDCELLGROUP: PrimaryLocalCellID=0, SsrdLocalCellID=100;
//Adding operator information of a cell
ADD CELLOP: LocalCellId=100, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
//Turning off the quick channel calibration switch
MOD CELLALGOSWITCH: LOCALCELLID=0, EnhChnCalSwitch=QUICK_CHN_CAL_SWITCH-0;
MOD CELLALGOSWITCH: LOCALCELLID=100, EnhChnCalSwitch=QUICK_CHN_CAL_SWITCH-0;
//Activating the split cell and then the primary cell
//Two cells generated after a split are served by the same RRU. You are
advised to activate the primary cell immediately after activating the split
cell. This ensures that the split takes effect immediately in two cells.
ACT CELL: LOCALCELLID=100;
ACT CELL: LOCALCELLID=0;
//(Optional. Perform this step if soft split multi-beam measurement, soft
split scheduling optimization, soft split downlink power sharing, or soft
split PDCCH allocation optimization is enabled) Adding beamforming antennas
for multi-beam measurement and modifying cell-specific sector equipment
//Running the ADD BFANT command to add beamforming antennas for multi-beam
measurement with the BAND parameter set to 0 (recommended value) when soft
split multi-beam measurement, soft split scheduling optimization, soft split
downlink power sharing, or soft split PDCCH allocation optimization is enabled
ADD BFANT: DEVICENO=2, MANUFACTORY=HuaweiAgisson, CONNSRN=60,
MODELNO="Soft_Split_Beam_Common", TILT=2, BAND=0;
ADD BFANT: DEVICENO=3, MANUFACTORY=HuaweiAgisson, CONNSRN=60,
MODELNO="Soft_Split_Beam_Common", TILT=2, BAND=0;
MOD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0, WeightNo=2;
MOD EUCELLSECTOREQM: LocalCellId=100, SectorEqmId=0, WeightNo=3;
//(Optional) Enabling soft split multi-beam measurement
MOD ENODEBALGOSWITCH: SSRDAlgoSwitch=SsrdMultiBeamMeasSwitch-1;
//(Optional) Configuring a CRS split beam indicator, which specifies a group
of beams as the broadcast beams serving cells from a split (based on analysis
of soft split multi-beam measurement results)
MOD BFANT: DEVICENO=2, CrsSplitBeamIndicator=0;
MOD BFANT: DEVICENO=3, CrsSplitBeamIndicator=1;
//(Optional) Enabling soft split scheduling optimization (this function can
be enabled only if soft split multi-beam measurement is enabled)
MOD ENODEBALGOSWITCH: SSRDAlgoSwitch=SsrdSchOptSwitch-1;
//(Optional) Enabling soft split downlink power sharing (this function can be
enabled only if soft split scheduling optimization is enabled)
MOD ENODEBALGOSWITCH: SSRDAlgoSwitch=SsrdDlPwrShareSwitch-1;
//(Optional) Enabling soft split PDCCH allocation optimization (this function
If this function requires the ACT BFANTDB command for activation after cells are activated, this
function can be activated by running this command, but not by using the CME.
Step 2 Run the DSP BFANT command to check whether the values of the amplitude and phase of
physical ports are valid. If the values are invalid, run the LST BFANT command to check
whether the settings of the Manufactory, Antenna Model Number, Tilt, Beamwidth, and
Band parameters comply with Table 4-3. If any of these parameters do not comply with
Table 4-3, run the MOD BFANT command to change the settings.
Step 3 Run the DSP CELL command to query the Reason for latest state change parameter of two
cells from a split. If the value of this parameter is Cell setup successfully in the command
output, cells from a split have been set up successfully.
Step 5 Run the DSP BFANT command. If the command output provides more than two antenna
records, the weight database file has been activated.
Step 6 Run the LST ENODEBALGOSWITCH command to query the switches controlling soft
split multi-beam measurement, soft split scheduling optimization, soft split downlink power
sharing, and soft split PDCCH allocation optimization. If these switches are on, these
functions have been successfully enabled.
----End
> Suc SSRD CompRB Num MIMO and BF Average number of PRBs used during
coordinated scheduling for MIMO in the
local split cell and beamforming in
neighboring split cells
> Suc SSRD CompRB Num MIMO and Average number of PRBs used during
MIMO coordinated scheduling for MIMO in local
and neighboring split cells
> Suc SSRD CompRB Num BF and BF Average number of PRBs used during
coordinated scheduling for beamforming in
local and neighboring split cells
> Suc SSRD CompRB Num BF and MIMO Average number of PRBs used during
coordinated scheduling for beamforming in
the local split cell and MIMO in
neighboring split cells
Observe the following counters to learn UE pairing information after soft split scheduling
optimization is enabled.
The average downlink MCS index in a heavy-load split cell increases, while that in a light-
load split cell decreases. You can obtain MCS indexes by monitoring DL Average MCS on
the FMA. To obtain the FMA, contact Huawei engineers.
You can also start a Uu interface tracing task on the U2020 and observe p-a in an
RRC_CONN_SETUP message to monitor the performance of soft split downlink power
sharing.
5 Inter-Frequency Split
5.1 Principles
An inter-frequency split is when a cell is split into two inter-frequency cells. An inter-
frequency split is not under switch control, and can be deployed by configuring related
parameters if the requirements in 5.3 Requirements are met. For the related parameters, see
5.4.1.1 Data Preparation.
5.2.1 Benefits
When to Use
l Inter-frequency is suitable for macro eNodeBs with three sectors working in 8T8R/
64T64R mode. There are no load requirements for this feature, but the gains are larger
for heavily-loaded eNodeBs.
l Inter-frequency split is recommended in scenarios with high interference or limited
coverage. Specifically:
– Heavily loaded single-carrier eNodeBs that require capacity expansion but provide
poor coverage
– Multi-carrier eNodeBs providing poor coverage
l Inter-frequency split is not recommended where there are densely distributed high-rise
buildings.
Gains
Inter-frequency split:
l An inter-frequency split provides higher power density for the overall coverage and leads
to better handover KPIs than adaptation between 8T8R beamforming and MIMO. It
increases the average eNodeB capacity by 10% to 20%.
l An inter-frequency split causes less inter-cell co-channel interference and provides better
coverage than an intra-frequency split.
NOTE
The gains offered by inter-frequency split are subject to network conditions, such as interference,
networking mode, user distribution, and user services. Inter-frequency split may reduce the user
experience rate and cell capacity if most UEs reside in one of the two cells split from a sector.
5.2.2 Impacts
Network Impacts
The handover success rate increases, the service drop rate decreases, and the signal strength
improves.
Function Impacts
Function Function Switch Reference Description
Name
5.3 Requirements
5.3.1 Licenses
To implement inter-frequency split, a cell needs to be added on the RRU serving the original
cell. Apply for related licenses, such as "eNodeB TDD Basic Software" and "RF Multi
Carrier(per Carrier)(TDD)". For details about license application, see License Management.
5.3.2 Software
Prerequisite Functions
None
5.3.3 Hardware
Base Station Models
3900 and 5900 series base stations
Boards
l This function requires 8T8R or 64T64R BBPs.
l The number of cells doubles after a split. If the cell quantity after a split exceeds the cell
quantity limit of the BBPs in use, add BBPs. For BBP specifications, see 3900 & 5900
Series Base Station Product Documentation.
RF Modules
8T8R RRUs supporting external channel calibration (with a CAL port) or 64T64R AAU5281
Cells
l Neighboring cell configuration and antenna: Same as those for intra-frequency split. For
details, see Cells.
l Power configuration: For eNodeB reconstruction, if one more carrier must be added,
ensure that the total power for all the cells after a split does not exceed the maximum
rated power of the RRU.
5.3.4 Others
For details, see 4.3.4 Others.
Weight Number eUCellSectorEqm. The weight numbers of the primary cell and
WeightNo the split cell must be different. It is
recommended that the weight number be set
to the antenna device number of the cell.
NOTE
l A cell splits into a primary cell and a split
cell after inter-frequency split.
l To query the antenna device number, run the
DSP BFANT command. Determine the
antenna device number for a cell based on
the queried amplitude and phase.
Table 5-2 Number of inter-frequency cells from a split for values of the
BfAnt.CoverageScenario parameter
BfAnt.CoverageSc Horizontal Vertical Number of Inter-
enario Beamwidth Beamwidth Frequency Split
Cells
SCENARIO_2 65° 8° 2
SCENARIO_3 45° 8° 2
PA for even power CellDlpcPdschPa.P If the eNodeB already provides two carriers
distribution aPcOff and the power for each carrier must be
retained, you are advised to change the
PB PDSCHCfg.PB values of the CellDlpcPdschPa.PaPcOff
and PDSCHCfg.PB parameters to double
the CRS power of cells from a split,
ensuring the expected gains of inter-
frequency split.
The parameter settings in the following examples are used for reference only. Set the parameters based
on network requirements, for example, the TILT parameter in the ADD BFANT command.
l 64T64R cells
//For a newly deployed eNodeB, add two cells as cells from a split. For an
existing eNodeB, add only one cell as the split cell. The existing cell is
used as the primary cell.
//The two cells can work on different frequencies but they must have the same
uplink-downlink subframe configuration and the same special subframe
configuration.
ADD
CELL:LOCALCELLID=0,CELLNAME="cell0",NBCELLFLAG=FALSE,FREQBAND=42,ULEARFCNCFGIN
D=NOT_CFG,DLEARFCN=42490,ULBANDWIDTH=CELL_BW_N75,DLBANDWIDTH=CELL_BW_N75,CELLI
D=100,PHYCELLID=100,FDDTDDIND=CELL_TDD,SUBFRAMEASSIGNMENT=SA2,SPECIALSUBFRAMEP
ATTERNS=SSP7,EUCELLSTANDBYMODE=ACTIVE,ROOTSEQUENCEIDX=0,CUSTOMIZEDBANDWIDTHCFG
IND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCEL
LFLAG=BOOLEAN_FALSE,CPRICOMPRESSION=NORMAL_COMPRESSION,TXRXMODE=64T64R;
ADD
CELL:LOCALCELLID=1,CELLNAME="cell1",NBCELLFLAG=FALSE,FREQBAND=42,ULEARFCNCFGIN
D=NOT_CFG,DLEARFCN=42690,ULBANDWIDTH=CELL_BW_N75,DLBANDWIDTH=CELL_BW_N75,CELLI
D=200,PHYCELLID=200,FDDTDDIND=CELL_TDD,SUBFRAMEASSIGNMENT=SA2,SPECIALSUBFRAMEP
ATTERNS=SSP7,EUCELLSTANDBYMODE=ACTIVE,ROOTSEQUENCEIDX=0,CUSTOMIZEDBANDWIDTHCFG
IND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCEL
LFLAG=BOOLEAN_FALSE,CPRICOMPRESSION=NORMAL_COMPRESSION,TXRXMODE=64T64R;
//Activating the weight database file
ACT BFANTDB: OPMODE=SWFILE;
//Adding two beamforming antennas
ADD
BFANT:DEVICENO=0,MANUFACTORY=HuaweiAgisson,CONNSRN=60,MODELNO="MassiveSplitCel
l0",TILT=6,BAND=42,CoverageScenario=SCENARIO_2;
ADD
BFANT:DEVICENO=1,MANUFACTORY=HuaweiAgisson,CONNSRN=60,MODELNO="MassiveSplitCel
l1",TILT=6,BAND=42,CoverageScenario=SCENARIO_2;
//Associating the two cells with the same sector equipment
ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0,WEIGHTNO=0;
ADD EUCELLSECTOREQM:LOCALCELLID=1,SECTOREQMID=0,WEIGHTNO=1;
//Changing the values of A4A5 Based Interfreq A1 RSRP Threshold and A4A5
Based Interfreq A2 RSRP Threshold (The following values are for reference
only. Set these thresholds based on network conditions.)
MOD
INTERFREQHOGROUP:LOCALCELLID=0,INTERFREQHOGROUPID=0,INTERFREQHOA1THDRSRP=-85,I
NTERFREQHOA2THDRSRP=-85;
MOD
INTERFREQHOGROUP:LOCALCELLID=1,INTERFREQHOGROUPID=0,INTERFREQHOA1THDRSRP=-85,I
NTERFREQHOA2THDRSRP=-85;
//Turning off the quick channel calibration switch
MOD CELLALGOSWITCH:LOCALCELLID=0,ENHCHNCALSWITCH=QUICK_CHN_CAL_SWITCH-0;
MOD CELLALGOSWITCH:LOCALCELLID=1,ENHCHNCALSWITCH=QUICK_CHN_CAL_SWITCH-0;
//Adding operator information of a cell
ADD CELLOP:LOCALCELLID=0,TRACKINGAREAID=0,MMECFGNUM=CELL_MME_CFG_NUM_0;
ADD CELLOP:LOCALCELLID=1,TRACKINGAREAID=0,MMECFGNUM=CELL_MME_CFG_NUM_0;
//Changing the CRS power (The following values are examples. Change them
based on network conditions.)
MOD PDSCHCFG:LOCALCELLID=0,REFERENCESIGNALPWR=-28;
MOD PDSCHCFG:LOCALCELLID=1,REFERENCESIGNALPWR=-28;
//Activating cells in a random sequence
ACT CELL:LOCALCELLID=1;
ACT CELL:LOCALCELLID=0;
l 8T8R cells
//For a newly deployed eNodeB, add two cells as cells from a split. For an
existing eNodeB, add only one cell as the split cell. The existing cell is
used as the primary cell.
//The two cells can work on different frequencies but they must have the same
uplink-downlink subframe configuration and the same special subframe
configuration.
ADD
CELL:LOCALCELLID=0,CELLNAME="cell0",NBCELLFLAG=FALSE,FREQBAND=39,ULEARFCNCFGIN
D=NOT_CFG,DLEARFCN=38375,ULBANDWIDTH=CELL_BW_N75,DLBANDWIDTH=CELL_BW_N75,CELLI
D=0,PHYCELLID=0,FDDTDDIND=CELL_TDD,SUBFRAMEASSIGNMENT=SA2,SPECIALSUBFRAMEPATTE
RNS=SSP6,SSP6DWPTSMODE=TRUNCATION,EUCELLSTANDBYMODE=ACTIVE,ROOTSEQUENCEIDX=0,C
USTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG,UEPOWERMAXCFGIN
D=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_FALSE,CPRICOMPRESSION=NORMAL_COMPRESSION,TX
RXMODE=8T8R;
ADD
CELL:LOCALCELLID=1,CELLNAME="cell1",NBCELLFLAG=FALSE,FREQBAND=39,ULEARFCNCFGIN
D=NOT_CFG,DLEARFCN=38525,ULBANDWIDTH=CELL_BW_N75,DLBANDWIDTH=CELL_BW_N75,CELLI
D=1,PHYCELLID=1,FDDTDDIND=CELL_TDD,SUBFRAMEASSIGNMENT=SA2,SPECIALSUBFRAMEPATTE
RNS=SSP6,SSP6DWPTSMODE=TRUNCATION,EUCELLSTANDBYMODE=ACTIVE,ROOTSEQUENCEIDX=0,C
USTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG,UEPOWERMAXCFGIN
D=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_FALSE,CPRICOMPRESSION=NORMAL_COMPRESSION,TX
RXMODE=8T8R;
//Activating the weight database file
ACT BFANTDB: OPMODE=SWFILE;
//Adding two beamforming antennas
ADD
BFANT:DEVICENO=0,MANUFACTORY=HuaweiAgisson,CONNSRN=60,MODELNO="Soft_Split_Left
_BandF",TILT=6,BAND=39;
ADD
BFANT:DEVICENO=1,MANUFACTORY=HuaweiAgisson,CONNSRN=60,MODELNO="Soft_Split_Righ
t_BandF",TILT=6,BAND=39;
//Associating the two cells with the same sector equipment
ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0,WEIGHTNO=0;
ADD EUCELLSECTOREQM:LOCALCELLID=1,SECTOREQMID=0,WEIGHTNO=1;
//Changing the values of A4A5 Based Interfreq A1 RSRP Threshold and A4A5
Based Interfreq A2 RSRP Threshold (The following values are for reference
only. Set these thresholds based on network conditions.)
MOD
INTERFREQHOGROUP:LOCALCELLID=0,INTERFREQHOGROUPID=0,INTERFREQHOA1THDRSRP=-85,I
NTERFREQHOA2THDRSRP=-85;
MOD
INTERFREQHOGROUP:LOCALCELLID=1,INTERFREQHOGROUPID=0,INTERFREQHOA1THDRSRP=-85,I
NTERFREQHOA2THDRSRP=-85;
//Turning off the quick channel calibration switch
MOD CELLALGOSWITCH:LOCALCELLID=0,ENHCHNCALSWITCH=QUICK_CHN_CAL_SWITCH-0;
MOD CELLALGOSWITCH:LOCALCELLID=1,ENHCHNCALSWITCH=QUICK_CHN_CAL_SWITCH-0;
//Adding operator information of a cell
ADD CELLOP:LOCALCELLID=0,TRACKINGAREAID=0,MMECFGNUM=CELL_MME_CFG_NUM_0;
ADD CELLOP:LOCALCELLID=1,TRACKINGAREAID=0,MMECFGNUM=CELL_MME_CFG_NUM_0;
//Changing the CRS power (The following values are examples. Change them
based on network conditions.)
MOD PDSCHCFG:LOCALCELLID=0,REFERENCESIGNALPWR=-28;
MOD PDSCHCFG:LOCALCELLID=1,REFERENCESIGNALPWR=-28;
//Activating cells in a random sequence
ACT CELL:LOCALCELLID=1;
ACT CELL:LOCALCELLID=0;
If this function requires the ACT BFANTDB command for activation after cells are activated, this
function can be activated by running this command, but not by using the CME.
Band parameters comply with Table 5-1. If any of these parameters do not comply with
Table 5-1, run the MOD BFANT command to change the settings.
Step 3 Run the DSP CELL command to query the Reason for latest state change parameter of two
cells from a split. If the value of this parameter is Cell setup successfully in the command
output, cells from a split have been set up successfully.
Step 4 Run the LST EUCELLSECTOREQM command to query the eUCellSectorEqm.weightNo
parameter set for the two cells served by the same sector equipment. If the values are
different, intra-frequency split has been deployed successfully.
Step 5 Run the DSP BFANT command. If the command output provides more than two antenna
records, the weight database file has been activated.
----End
6 Parameters
The following hyperlinked EXCEL files of parameter reference match the software version
with which this document is released.
l Node Parameter Reference: contains device and transport parameters.
l eNodeBFunction Parameter Reference: contains all parameters related to radio access
functions, including air interface management, access control, mobility control, and radio
resource management.
NOTE
You can find the EXCEL files of parameter reference for the software version on the live network from
the product documentation delivered with that version.
FAQ: How do I find the parameters related to a certain feature from parameter
reference?
Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and choose
Contains. Enter the feature ID, for example, LOFD-001016 or TDLOFD-001016.
Step 3 Click OK. All parameters related to the feature are displayed.
----End
7 Counters
The following hyperlinked EXCEL files of performance counter reference match the software
version with which this document is released.
l Node Performance Counter Summary: contains device and transport counters.
l eNodeBFunction Performance Counter Summary: contains all counters related to radio
access functions, including air interface management, access control, mobility control,
and radio resource management.
NOTE
You can find the EXCEL files of performance counter reference for the software version used on the live
network from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from performance counter
reference?
Step 2 On the Counter Summary(En) sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, LOFD-001016 or TDLOFD-001016.
Step 3 Click OK. All counters related to the feature are displayed.
----End
8 Glossary
9 Reference Documents