Professional Documents
Culture Documents
Issue 05
Date 2020-07-27
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: https://www.huawei.com
Email: support@huawei.com
Contents
1 Change History.........................................................................................................................1
1.1 SRAN16.1 05 (2020-07-27)..................................................................................................................................................1
1.2 SRAN16.1 04 (2020-07-03)..................................................................................................................................................2
1.3 SRAN16.1 03 (2020-05-21)..................................................................................................................................................2
1.4 SRAN16.1 02 (2020-04-07)..................................................................................................................................................4
1.5 SRAN16.1 01 (2020-03-30)..................................................................................................................................................4
1.6 SRAN16.1 Draft B (2020-03-09)........................................................................................................................................ 5
1.7 SRAN16.1 Draft A (2020-01-20)........................................................................................................................................ 7
3 Overview................................................................................................................................. 10
4 LTE FDD and NR Flash Dynamic Spectrum Sharing...................................................... 12
4.1 Principles.................................................................................................................................................................................. 12
4.1.1 Principles of Flash Dynamic Spectrum Sharing...................................................................................................... 12
4.1.2 Key Technologies of Flash Dynamic Spectrum Sharing....................................................................................... 15
4.2 Network Analysis.................................................................................................................................................................. 18
4.2.1 Benefits................................................................................................................................................................................. 18
4.2.2 Impacts.................................................................................................................................................................................. 20
4.3 Requirements......................................................................................................................................................................... 35
4.3.1 Licenses................................................................................................................................................................................. 35
4.3.2 Software................................................................................................................................................................................37
4.3.3 Hardware.............................................................................................................................................................................. 44
4.3.4 Networking.......................................................................................................................................................................... 48
4.3.5 Others.................................................................................................................................................................................... 49
4.4 Operation and Maintenance............................................................................................................................................. 50
4.4.1 Data Configuration........................................................................................................................................................... 50
4.4.1.1 Data Preparation............................................................................................................................................................ 50
4.4.1.2 Using MML commands................................................................................................................................................ 58
4.4.1.3 Using the MAE-Deployment...................................................................................................................................... 59
4.4.2 Activation Verification..................................................................................................................................................... 60
5 Parameters.............................................................................................................................. 62
6 Counters.................................................................................................................................. 63
7 Glossary................................................................................................................................... 64
8 Reference Documents...........................................................................................................65
1 Change History
Technical Changes
Change Description Parameter Base Station
Change Model
Editorial Changes
● Added a schematic diagram showing the positions of uplink physical channel
resource coordinated scheduling. For details, see 4.1.1 Principles of Flash
Dynamic Spectrum Sharing.
Technical Changes
None
Editorial Changes
● Revised the description of the percentage of resources to be preferentially
allocated to LTE. For details, see 4.1.1 Principles of Flash Dynamic Spectrum
Sharing.
● Revised the description of the SSB dual-beam function. For details, see 4.1.2
Key Technologies of Flash Dynamic Spectrum Sharing.
● Revised the description of the impact of this function on downlink power
control. For details, see 4.2.2 Impacts.
● Added the description of the mutually exclusive relationship between this
function and 3D coverage pattern. For details, see 4.3.2 Software.
● Added the description of the requirements on frequency bands supported by
RF modules. For details, see 4.3.3 Hardware.
● Added the description of cell co-coverage requirements and the requirements
on the PSD corresponding to the maximum transmit power of cells. For
details, see 4.3.3 Hardware.
● Revised the description of the setting notes for the SIB1 period, Format3 RB
number, and Format4 RB number parameters. For details, see 4.4.1.1 Data
Preparation.
● Revised the description of the MML commands for configuring the frequency-
domain position of the LTE PUCCH and the number of RBs for the NR PUCCH
For details, see 4.4.1.2 Using MML commands.
Technical Changes
Change Description Parameter Base Station
Change Model
Editorial Changes
● Added the description of the frequency band frame offset. For details, see
4.1.1 Principles of Flash Dynamic Spectrum Sharing and 4.4.1.1 Data
Preparation.
● Revised the descriptions of the percentage of resources preferentially
allocated, spectrum power sharing mode, and coordinated scheduling of
downlink physical channel resources. For details, see 4.1.1 Principles of Flash
Dynamic Spectrum Sharing.
● Revised the description of the configuration of the number of common
control resource RBs. For details, see 4.1.1 Principles of Flash Dynamic
Spectrum Sharing, 4.4.1.1 Data Preparation, and 4.4.1.2 Using MML
commands.
● Revised the description of gain ranges. For details, see 4.2.1 Benefits.
● Added the description of network impact when MBSFN subframes are
configured on TM9-dedicated carriers. For details, see 4.2.2 Impacts.
● Revised the description of the impacted function uplink frequency selective
scheduling. For details, see 4.2.2 Impacts.
● Added the description of the mutually exclusive relationship with basic
functions of downlink scheduling. For details, see 4.3.2 Software.
● Modified the cell specifications of the UBBPe6 and added the description that
the uplink and downlink bandwidths of LTE and NR cells must be the same.
For details, see 4.3.3 Hardware.
● Add the description of the method used to determine whether NR UEs
support CRS rate matching. For details, see 4.3.5 Others.
● Add the description of the number of cells in a spectrum sharing cell group
and spectrum sharing cell group specifications, and the description of
configuration suggestions for the four frame allocation parameter. For details,
see 4.4.1.1 Data Preparation.
● Revised the description of the MML configuration of the number of RBs for
the NR PUCCH. For details, see 4.4.1.2 Using MML commands.
Technical Changes
Change Description Parameter Base Station
Change Model
Editorial Changes
● Revised the description of RB resources occupied by the NR PUCCH. For
details, see 4.1.2 Key Technologies of Flash Dynamic Spectrum Sharing.
● Revised the description of coordinated scheduling of LTE and NR downlink
physical channel resources. For details, see 4.1.2 Key Technologies of Flash
Dynamic Spectrum Sharing.
● Added the description of the impact relationship between this function and
RAN sharing on the LTE side and multi-operator sharing on the NR side. For
details, see 4.2.2 Impacts.
● Revised the description of the mutually exclusive relationship between this
function and the Flexible PUCCH Configuration function. For details, see 4.3.2
Software.
● Added the description that cells enabled with this function must be bound to
baseband processing units supporting this function on the LTE side. For
details, see 4.4.1.1 Data Preparation.
Technical Changes
Change Description Parameter Base Station
Change Model
Editorial Changes
● Added the description of the impact on the user-plane CPU usage of boards
and on ping delay, and revised the description of the function switch
controlling the impacted function downlink massive CA. For details, see 4.2.2
Impacts.
● Revised the description of licenses. For details, see 4.3.1 Licenses.
● Revised the description of the cell specifications of LTE baseband processing
units. For details, see 4.3.3 Hardware.
● Revised the description of the setting notes for the number of common
control resource RBs. For details, see 4.4.1.1 Data Preparation.
Technical Changes
Change Description Parameter Base Station
Change Model
Editorial Changes
● Revised the description of the NR SSB sending position. For details, see 4.1.2
Key Technologies of Flash Dynamic Spectrum Sharing.
● Added the description of the parameter specifying the number of RBs for
common control resources. For details, see 4.1.2 Key Technologies of Flash
Dynamic Spectrum Sharing, 4.4.1.1 Data Preparation, and 4.4.1.2 Using
MML commands.
● Added the description of gain conditions concerning the SIB1 period. For
details, see 4.2.1 Benefits, 4.4.1.1 Data Preparation, and 4.4.1.2 Using MML
commands.
● Revised the description of the impact on LTE quality-related counters that are
measured over the full band. For details, see 4.2.2 Impacts.
● Added the description of the impact relationship with LTE guard band
deployment, and uplink RB reservation. For details, see 4.2.2 Impacts.
● Added the description of the mutually exclusive relationship with paging
message interference randomization and uplink PUSCH RB reservation for
MCPTT voice services. For details, see 4.3.2 Software.
● Revised the description of the working modes of the UBBPe5 and UBBPe6
boards and their LTE cell specifications. For details, see 4.3.3 Hardware.
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 Feature
Parameter Description documents apply only to the corresponding software
release. For future software releases, refer to the corresponding updated product
documentation.
3 Overview
This feature supports both NSA and SA networking. Unless otherwise specified, the
descriptions apply to both networking scenarios.
This feature is a trial feature in SA networking. The disclaimer for trial features is
as follows:
● 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.
4.1 Principles
This function enables LTE and NR to dynamically share time-frequency resources
on a spectrum segment based on the traffic volumes of LTE and NR networks. The
details can be found in 4.1.1 Principles of Flash Dynamic Spectrum Sharing.
During spectrum sharing, uplink and downlink physical channel resources are
coordinated and scheduled to prevent interference between LTE and NR. The
details are described in 4.1.2 Key Technologies of Flash Dynamic Spectrum
Sharing.
● Configuring the frame offset and TA offset (to ensure the complete alignment
of radio frames and subframes)
– Set the LTE parameter CellFrameOffset.FrameOffset or
ENodeBFrameOffset.FddFrameOffset, which specifies the frame offset
on the LTE side. If both parameters are configured, the value of the
CellFrameOffset.FrameOffset parameter prevails. Set the NR parameter
gNodeBParam.FrameOffset or gNBFreqBandConfig.FrameOffset,
which specifies the frame offset on the NR side. If both parameters are
configured, the value of the gNBFreqBandConfig.FrameOffset
parameter prevails.
– Set the NR parameter NRDUCell.TaOffset, which specifies the TA offset.
After this function is enabled, LTE cells and NR cells in the associated spectrum
sharing cell groups can share spectrum resources on a spectrum segment. Figure
4-1 shows flash dynamic spectrum sharing between LTE and NR.
Table 4-1 Counters for measuring the numbers of uplink and downlink available
RBs in LTE and NR cells
Counter ID Counter Name
1526759050 L.ChMeas.PRB.UL.Actual.Avail
1526759051 L.ChMeas.PRB.DL.Actual.Avail
1911827161 N.PRB.UL.Actual.Avail.Avg
1911827160 N.PRB.DL.Actual.Avail.Avg
In addition to LTE and NR flash dynamic spectrum sharing, this function supports
spectrum sharing modes specified by the LTE parameter
SpectrumCloud.SpctShrMode. If this parameter is set to
LTE_NR_PWR_DYN_SHR_WITH_SPCT, LTE and NR also share spectrum power
when they share spectrum, and the percentage of power allocated to a RAT is
equal to the percentage of spectrum allocated to that RAT. If this parameter is set
to LTE_NR_PWR_INDEPENDENT, LTE and NR use separate spectrum power when
they share spectrum. The following elaborates spectrum power sharing using a 2 x
40 W RF module as an example. If spectrum power is shared, both LTE and NR can
be configured with a transmit power within the range of 2 x 20 W to 2 x 40 W. In
this case, LTE and NR minimally share the total power of 2 x 20 W. If spectrum
power is not shared, LTE and NR can individually be configured with the transmit
power of 2 x 20 W. That is, LTE and NR each use the 2 x 20 W power. Assume that
the power specifications are always the same, regardless of the power
configuration mode in use. The independent power configuration mode results a
better capacity performance but a higher power consumption. The spectrum
power sharing mode reduces the power consumption but also leads to a capacity
performance loss. Therefore, when the power is sufficient, the independent power
configuration mode is preferred. When the power is insufficient, the spectrum
power sharing mode can be used.
When LTE and NR share the same CPRI optical fibers and the CPRI bandwidth is
insufficient, LTE and NR can be configured to share the same carrier and CPRI data
resources through the LTE parameter
LteNrSpctShrCellGrp.LteNrCoCarrCoCpriDataSw. If the LTE and NR co-carrier
co-CPRI data switch and CPRI compression function are both enabled, the CPRI
compression ratios must be the same between LTE and NR cells. For details about
the configuration requirements, see 4.3.5 Others.
The uplink physical channel resources are coordinated and scheduled as follows:
● LTE and NR sounding reference signals (SRSs): Spectrum resources are
dynamically allocated in the time domain based on the traffic volume
requirements of LTE and NR networks to improve resource usage.
● NR physical uplink control channel (PUCCH): The NR PUCCH occupies
symmetrical RBs at the two ends of the bandwidth. The number of RBs
occupied by the NR PUCCH is configured using the NR parameters
NRDUCellPucch.Format1RbNum, NRDUCellPucch.CsiDedicatedRbNum,
NRDUCellPucch.Format3RbNum, NRDUCellPucch.Format4RbNum, and
NRDUCellPucch.Format4CsiDedicatedRbNum. In NSA networking, the NR
PUCCH does not include the common PUCCH. In SA networking, the NR
PUCCH always includes the common PUCCH, which occupies two RBs. For
details about the common PUCCH, see Channel Management in 5G RAN
Feature Documentation.
● LTE PUCCH: The position of the LTE PUCCH depends on the RBs fixedly
reserved by the gNodeB for the NR PUCCH. The gNodeB reserves four RBs for
the NR PUCCH in 10 MHz or 15 MHz bandwidth scenarios, and reserves six
RBs for the NR PUCCH in 20 MHz bandwidth scenarios. If the number of RBs
configured for the NR PUCCH does not exceed the number of RBs reserved for
it, the LTE PUCCH is symmetrically configured adjacent to the NR PUCCH at
the two ends of the bandwidth. If the number of RBs configured for the NR
PUCCH exceeds the number of RBs reserved for it, the start position of the
LTE PUCCH at the lower end and the end position of the LTE PUCCH at the
upper end are configured through the LTE parameters
CellRbReserve.RbRsvMode, CellRbReserve.RbRsvType,
CellRbReserve.RbRsvStartIndex, and CellRbReserve.RbRsvEndIndex. The
specific position varies depending on the number of RBs configured for the
NR PUCCH. It is recommended that the LTE PUCCH be symmetrically
configured adjacent to the NR PUCCH at the two ends of the bandwidth, so
that the NR PUCCH and LTE PUCCH occupy consecutive RBs. The number of
RBs occupied by the LTE PUCCH is specified by parameter configurations or is
dynamically adjusted. For details, see the descriptions of the PUCCH in
Physical Channel Resource Management in eRAN Feature Documentation. In
this function, the LTE PUCCH can occupy a maximum of 16 RBs. If the number
of RBs occupied by the LTE PUCCH exceeds this value, SRSs may be interfered
and network performance may be affected.
● LTE physical random access channel (PRACH): The LTE PRACH is configured
adjacent to the LTE PUCCH at the lower end. The LTE PRACH always occupies
six RBs.
● NR PRACH: The NR PRACH is configured adjacent to the LTE PUCCH at the
upper end. The frequency-domain start position of the NR PRACH is
determined based on the configuration of the LTE PUCCH. The NR PRACH
always occupies six RBs.
● LTE and NR physical uplink shared channels (PUSCHs): The total available
PUSCH resources for LTE and NR equal the total spectrum resources minus
the resources occupied by the LTE and NR PUCCH and PRACH. The total
available PUSCH resources for LTE and NR are dynamically shared between
LTE and NR based on traffic requirements.
matching. UEs that do not support CRS rate matching are prohibited from
accessing the NR spectrum sharing cell.
● The LTE CSI-RS/CRS/DMRS/SS/PBCH and NR CSI-RS/TRS/SSB/PDCCH avoid
conflicts with each other through static coordinated scheduling.
● The LTE CRS avoids a conflict with the NR SSB and SIB1 on the PDSCH
through parameter configurations. That is, MBSFN subframes must be
configured for LTE cells in positions aligned with the NR SSB subframes and
subframes occupied by SIB1 on the NR PDSCH. This ensures that the LTE
MBSFN subframes overlap with the NR SSB subframes and subframes
occupied by SIB1 on the NR PDSCH in the time domain. As the CRS is sent
only in PDCCH symbols in an LTE MBSFN subframe, conflicts between the LTE
CRS and NR SSB and SIB1 on the NR PDSCH are avoided. MBSFN subframes
are configured using the following LTE parameters:
– CellMbsfnSfEnhConfig.SubframeAllocationMode: Indicates the MBSFN
subframe allocation mode.
– CellMbsfnSfEnhConfig.RadioFrameAllocPrd: Indicates the MBSFN
subframe allocation period.
– CellMbsfnSfEnhConfig.RadioFrameAllocOfs: Indicates the MBSFN
subframe allocation offset.
– CellMbsfnSfEnhConfig.OneFrameAllocation and
CellMbsfnSfEnhConfig.FourFrameAllocation: Indicate the positions of
MBSFN subframes.
The MBSFN subframe configuration is affected by the SSB period and
activation of the SSB dual-beam function. For details, see the configuration
suggestions in 4.4.1.1 Data Preparation.
● The LTE CRS uses static coordinated scheduling to avoid conflicts with the RRC
messages on the NR PDSCH.
● The NR PDCCH and LTE PDCCH/PCFICH/PHICH avoid conflicts with each
other. The LTE PDCCH occupies one symbol (in the case of 2T2R or 2T4R) or
two symbols (in the case of 4T4R), and the number of symbols occupied by
the NR PDCCH can be set to 1 or 2 by using NR parameters
NRDUCellPdcch.SpctShrStartSymbol and
NRDUCellPdcch.OccupiedSymbolNum. For details about the configuration
suggestions, see 4.4.1.1 Data Preparation.
● The LTE and NR PDSCHs avoid conflicts with each other through dynamic
coordinated scheduling. In addition, the LTE PDSCH actively avoids conflicts
with the NR SSB/CSI-RS/TRS/DMRS/PDCCH through dynamic scheduling, and
the NR PDSCH actively avoids conflicts with the LTE CRS/CSI-RS/SS/PBCH/
PHICH/PCFICH/PDCCH through dynamic scheduling.
The preceding avoidance mechanisms are implemented by configuring the
SSB frequency-domain position, which involves the following NR parameters:
– NRDUCell.SsbDescMethod: Indicates the description method of the SSB
frequency-domain position. In NSA networking, it is recommended that
this parameter be set to SSB_DESC_TYPE_NARFCN, which indicates
absolute frequencies. This is because the step of absolute frequencies is
shorter, which improves the spectrum usage. In SA networking, this
parameter must be set to SSB_DESC_TYPE_GSCN, which indicates the
Global Synchronization Channel Number (GSCN). This is because UEs
need to determine the NR SSB frequency-domain position based on the
4.2.1 Benefits
This function increases cell downlink throughput as follows:
● In the case of LTE-to-NR spectrum sharing, the average downlink throughput
of NR cells is increased. Average downlink throughput of an NR cell is equal
to N.ThpVol.DL.Cell/N.ThpTime.DL.Cell.
● In the case of NR-to-LTE spectrum sharing, the average downlink throughput
of LTE cells is increased. Average downlink throughput of an LTE cell is equal
to L.Thrp.bits.DL/L.Thrp.Time.Cell.DL.HighPrecision.
Table 4-2 and Table 4-3 list the gains provided by this function in different
networking compared with when a typical static refarming solution is enabled.
The different gain levels can be achieved only when certain conditions are met.
● The LTE cell gain can be achieved only when both the following conditions are
met:
– The LTE cell is fully loaded and no online UEs exist in the NR cell.
– The SSB period for the NR cell (specified by the NR parameter
NRDUCell.SsbPeriod) is set to MS20(20) or a larger value.
– The NR cell SIB1 period (specified by the NR parameter
NRDUCell.Sib1Period) is set to MS40(40).
– The NR cell does not use two SSB beams.
– The LTE cell works in TM4 mode.
● The NR cell gain can be achieved only when both the following conditions are
met:
– The NR cell is fully loaded and no online UEs exist in the LTE cell.
– The SSB period for the NR cell is set to MS20(20) or a larger value.
– The NR cell SIB1 period is set to MS40(40).
– The NR cell does not use two SSB beams.
If one of the preceding conditions is not met, the gain will be lower than those
listed in the tables above, but will not be negative.
4.2.2 Impacts
Network Impacts
● LTE-to-NR spectrum sharing has the following impacts on LTE networks:
– LTE is interfered by the NR synchronization signals, PBCH, reference
channels, and system information. The interference leads to inaccurate
measurement results of LTE quality-related counters that are measured
over the full band. The counters include the signal to interference plus
noise ratio (SINR), reference signal received quality (RSRQ), full-band
channel quality indicator (CQI), precoding matrix indication (PMI), and
rank indication (RI). Consequently:
▪ The average cell uplink and downlink initial block error rate (IBLER)
and residual block error rate (RBLER) increase.
Average cell uplink IBLER = (L.Traffic.UL.SCH.QPSK.ErrTB.Ibler +
L.Traffic.UL.SCH.16QAM.ErrTB.Ibler + L.Traffic.UL.SCH.
64QAM.ErrTB.Ibler + L.Traffic.UL.SCH.256QAM.ErrTB.Ibler)/
(L.Traffic.UL.SCH.QPSK.TB + L.Traffic.UL.SCH.16QAM.TB +
L.Traffic.UL.SCH.64QAM.TB + L.Traffic.UL.SCH.256QAM.TB). Table
4-4 lists the related counters.
Average cell downlink IBLER = (L.Traffic.DL.SCH.QPSK.ErrTB.Ibler +
L.Traffic.DL.SCH.16QAM.ErrTB.Ibler + L.Traffic.DL.SCH.
64QAM.ErrTB.Ibler + L.Traffic.DL.SCH.256QAM.ErrTB.Ibler)/
(L.Traffic.DL.SCH.QPSK.TB + L.Traffic.DL.SCH.16QAM.TB +
L.Traffic.DL.SCH.64QAM.TB + L.Traffic.DL.SCH.256QAM.TB). Table
4-5 lists the related counters.
Average cell uplink RBLER = (L.Traffic.UL.SCH.QPSK.ErrTB.Rbler +
L.Traffic.UL.SCH.16QAM.ErrTB.Rbler + L.Traffic.UL.SCH.
64QAM.ErrTB.Rbler + L.Traffic.UL.SCH.256QAM.ErrTB.Rbler)/
(L.Traffic.UL.SCH.QPSK.TB + L.Traffic.UL.SCH.16QAM.TB +
L.Traffic.UL.SCH.64QAM.TB + L.Traffic.UL.SCH.256QAM.TB). Table
4-6 lists the related counters.
Average cell downlink RBLER = (L.Traffic.DL.SCH.QPSK.ErrTB.Rbler
+ L.Traffic.DL.SCH.16QAM.ErrTB.Rbler + L.Traffic.DL.SCH.
64QAM.ErrTB.Rbler + L.Traffic.DL.SCH.256QAM.ErrTB.Rbler)/
(L.Traffic.DL.SCH.QPSK.TB + L.Traffic.DL.SCH.16QAM.TB +
L.Traffic.DL.SCH.64QAM.TB + L.Traffic.DL.SCH.256QAM.TB). Table
4-7 lists the related counters.
Table 4-4 Counters used for measuring the average cell uplink IBLER
on the LTE side
Counter ID Counter Name
1526728186 L.Traffic.UL.SCH.QPSK.ErrTB.Ibler
1526728188 L.Traffic.UL.SCH.16QAM.ErrTB.Ibler
1526728190 L.Traffic.UL.SCH.64QAM.ErrTB.Ibler
1526749528 L.Traffic.UL.SCH.256QAM.ErrTB.Ibler
1526727366 L.Traffic.UL.SCH.QPSK.TB
1526727367 L.Traffic.UL.SCH.16QAM.TB
1526727368 L.Traffic.UL.SCH.64QAM.TB
1526749524 L.Traffic.UL.SCH.256QAM.TB
Table 4-5 Counters used for measuring the average cell downlink
IBLER on the LTE side
Counter ID Counter Name
1526728180 L.Traffic.DL.SCH.QPSK.ErrTB.Ibler
1526728182 L.Traffic.DL.SCH.16QAM.ErrTB.Ibler
1526728184 L.Traffic.DL.SCH.64QAM.ErrTB.Ibler
1526739660 L.Traffic.DL.SCH.256QAM.ErrTB.Ibler
1526727354 L.Traffic.DL.SCH.QPSK.TB
1526727355 L.Traffic.DL.SCH.16QAM.TB
1526727356 L.Traffic.DL.SCH.64QAM.TB
1526739656 L.Traffic.DL.SCH.256QAM.TB
Table 4-6 Counters used for measuring the average cell uplink
RBLER on the LTE side
Counter ID Counter Name
1526728187 L.Traffic.UL.SCH.QPSK.ErrTB.Rbler
1526728189 L.Traffic.UL.SCH.16QAM.ErrTB.Rbler
1526728191 L.Traffic.UL.SCH.64QAM.ErrTB.Rbler
1526749530 L.Traffic.UL.SCH.256QAM.ErrTB.Rbler
1526727366 L.Traffic.UL.SCH.QPSK.TB
1526727367 L.Traffic.UL.SCH.16QAM.TB
1526727368 L.Traffic.UL.SCH.64QAM.TB
1526749524 L.Traffic.UL.SCH.256QAM.TB
Table 4-7 Counters used for measuring the average cell downlink
RBLER on the LTE side
Counter ID Counter Name
1526728181 L.Traffic.DL.SCH.QPSK.ErrTB.Rbler
1526728183 L.Traffic.DL.SCH.16QAM.ErrTB.Rbler
1526728185 L.Traffic.DL.SCH.64QAM.ErrTB.Rbler
1526739661 L.Traffic.DL.SCH.256QAM.ErrTB.Rbler
1526727354 L.Traffic.DL.SCH.QPSK.TB
1526727355 L.Traffic.DL.SCH.16QAM.TB
1526727356 L.Traffic.DL.SCH.64QAM.TB
1526739656 L.Traffic.DL.SCH.256QAM.TB
▪ The access success rate, handover success rate, and RRC connection
reestablishment success rate decrease.
Access success rate = L.RRC.ConnReq.Succ/L.RRC.ConnReq.Att.
Table 4-8 lists the related counters.
Handover success rate = (L.HHO.IntraeNB.IntraFreq.ExecSuccOut +
L.HHO.IntraeNB.InterFreq.ExecSuccOut +
L.HHO.IntereNB.IntraFreq.ExecSuccOut +
L.HHO.IntereNB.InterFreq.ExecSuccOut)/
(L.HHO.IntraeNB.IntraFreq.ExecAttOut +
L.HHO.IntraeNB.InterFreq.ExecAttOut +
L.HHO.IntereNB.IntraFreq.ExecAttOut +
L.HHO.IntereNB.InterFreq.ExecAttOut). Table 4-9 lists the related
counters.
Table 4-8 Counters used for measuring the access success rate
Counter ID Counter Name
1526726659 L.RRC.ConnReq.Succ
1526726658 L.RRC.ConnReq.Att
Table 4-9 Counters used for measuring the handover success rate
Counter ID Counter Name
1526726997 L.HHO.IntraeNB.IntraFreq.ExecSuccO
ut
1526727000 L.HHO.IntraeNB.InterFreq.ExecSuccO
ut
1526727003 L.HHO.IntereNB.IntraFreq.ExecSuccO
ut
1526727006 L.HHO.IntereNB.InterFreq.ExecSuccO
ut
1526726996 L.HHO.IntraeNB.IntraFreq.ExecAttOut
1526726999 L.HHO.IntraeNB.InterFreq.ExecAttOu
t
1526727002 L.HHO.IntereNB.IntraFreq.ExecAttOut
1526727005 L.HHO.IntereNB.InterFreq.ExecAttOut
1526727086 L.RRC.ReEst.Succ
1526727085 L.RRC.ReEst.Att
Table 4-11 Counters used for measuring the bearer service drop rate
1526727546 L.E-RAB.AbnormRel
1526727547 L.E-RAB.NormRel
Table 4-12 Counters used for measuring the LTE cell uplink and
downlink throughput
1526728259 L.Thrp.bits.UL
1526728998 L.Thrp.Time.Cell.UL.HighPrecision
1526728261 L.Thrp.bits.DL
1526728997 L.Thrp.Time.Cell.DL.HighPrecision
Table 4-13 Counters used for measuring the uplink and downlink
throughput of LTE UEs
1526728259 L.Thrp.bits.UL
1526729415 L.Thrp.bits.UE.UL.SmallPkt
1526729416 L.Thrp.Time.UE.UL.RmvSmallPkt
1526728261 L.Thrp.bits.DL
1526729005 L.Thrp.bits.DL.LastTTI
1526729015 L.Thrp.Time.DL.RmvLastTTI
Table 4-14 Counters used for measuring the NR cell uplink and downlink
throughput
Counter ID Counter Name
1911816696 N.ThpVol.UL.Cell
1911816697 N.ThpTime.UL.Cell
1911816694 N.ThpVol.DL.Cell
1911816695 N.ThpTime.DL.Cell
Table 4-15 Counters used for measuring the uplink and downlink
throughput of NR UEs
Counter ID Counter Name
1911816645 N.ThpVol.UL
1911816851 N.ThpVol.UE.UL.SmallPkt
1911816853 N.ThpTime.UE.UL.RmvSmallPkt
1911816643 N.ThpVol.DL
1911816848 N.ThpVol.DL.LastSlot
1911816850 N.ThpTime.DL.RmvLastSlot
NOTE
NR is not interfered by the LTE synchronization signals, PBCH, reference channels, and
system information. Therefore, NR quality-related counters that are measured over the
full band are not affected.
● This function involves the estimation and allocation of spectrum resources on
both the LTE and NR sides, and therefore has the following impacts on the
two sides:
– Increased board user-plane CPU usage
Function Impacts
● Impacted functions on the LTE side
Function Function Switch Reference Description
Name (eRAN Feature
Documentation
)
4.3 Requirements
4.3.1 Licenses
This function requires both feature and capacity licenses.
Table 4-16 Feature licenses (for 3900 and 5900 series base stations)
RAT Featur Feature Model License NE Sales
e ID Name Control Item Unit
LTE MRFD- LTE FDD LT1S0LFNS LTE FDD and eNode per
FDD 160222 and NR S00 NR Flash B Cell
Flash Dynamic
Dynamic Spectrum
Spectrum Sharing(LTE
Sharing FDD)
(LTE FDD)
Table 4-17 Capacity licenses (for 3900 and 5900 series base stations)
RAT Model License Control Item NE Sales
Unit
When 5000 series RF modules are used, customers must purchase the Spectrum
Sharing License for 5000 Series RF Module. When other RF modules are used,
customers must purchase the RF Spectrum Sharing License. When 5000 series RF
modules and other RF modules are both used, customers must purchase both
hardware licenses.
4.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
Prerequisite Functions
● Prerequisite functions on the LTE side
Function Function Switch Reference Description
Name (eRAN Feature
Documentation
)
a: The mutually exclusive relationship exists only when LTE FDD and NR
share spectrum power during spectrum sharing.
b: When LTE FDD and NR Flash Dynamic Spectrum Sharing is enabled, the
CellRbReserve.RbRsvMode, CellRbReserve.RbRsvType,
CellRbReserve.RbRsvStartIndex, and CellRbReserve.RbRsvEndIndex
parameters can be used as an alternative to the flexible PUCCH
configuration function.
4.3.3 Hardware
Huawei devices (including the eNodeB and gNodeB) running SRAN16.1 or a later
version must be used on the radio access network.
Boards
● LTE: For baseband processing units, only the UBBPd, UBBPe, and UBBPg
support this function. The specific board model and the number of cells
supported by each board after function activation are listed in Table 4-18. For
main control boards, only the UMPTb, UMPTe, UMPTg, and UMPTga support
this function.
● NR: For baseband processing units, only the UBBPg2, UBBPg2a, UBBPg3, and
UBBPg3b support this function. The number of cells supported by each
baseband processing unit is the same as that before this function is enabled.
For main control boards, only the UMPTe, UMPTg, and UMPTga support this
function.
LTE FDD, LM, GL, UBBPe5 ● LTE FDD or LM: Nine 2T2R, 2T4R, or
or other working 4T4R cells. Among them, a
modes involving maximum of six can be enabled
LTE FDD with LTE FDD and NR Flash
Dynamic Spectrum Sharing; other
cells are common cells.
● Multimode other than LM: Six 2T2R,
2T4R, or 4T4R cells. Among them, a
maximum of three can be enabled
with LTE FDD and NR Flash
Dynamic Spectrum Sharing; other
cells are common cells.
LTE FDD, LM, GL, UBBPe6 ● LTE FDD or LM (with BBP.SRT set to
or other working DEFAULT): Twelve 2T2R, 2T4R, or
modes involving 4T4R cells. Among them, a
LTE FDD maximum of six can be enabled
with LTE FDD and NR Flash
Dynamic Spectrum Sharing; other
cells are common cells.
● LM (with BBP.SRT set to
NBIOT_ENHANCE): Nine 2T2R,
2T4R, or 4T4R cells. Among them, a
maximum of six can be enabled
with LTE FDD and NR Flash
Dynamic Spectrum Sharing; other
cells are common cells.
● Multimode other than LM: Nine
2T2R, 2T4R, or 4T4R cells. Among
them, a maximum of three can be
enabled with LTE FDD and NR Flash
Dynamic Spectrum Sharing; other
cells are common cells.
LTE FDD, LM, GL, UBBPg Same as that before this function is
or other working enabled
modes involving
LTE FDD
RF Modules
3900 and 5900 series base stations. All 3000 series and 5000 series RF modules
that meet the following conditions support this function:
● LTE and NR share the same RF module.
● The RF module works on the 700 MHz, 800 MHz, 850 MHz, 900 MHz, 1800
MHz, 2100 MHz, 2600 MHz, or AWS frequency band.
● The RF module supports 2T2R, 2T4R, or 4T4R.
Cells
LTE and NR cells must meet all of the following requirements:
● LTE and NR cells must both work on 10 MHz, 15 MHz, or 20 MHz uplink and
downlink bandwidths.
● The TX/RX modes of LTE and NR cells must be both 2T2R, 2T4R, or 4T4R.
When the TX/RX mode is 2T2R or 2T4R, the recommended number of CRS
ports for LTE cells (specified by the Cell.CrsPortNum parameter) is 2. When
the TX/RX mode is 4T4R, the recommended number of CRS ports for LTE cells
is 4.
● LTE and NR cells must have the same operating frequency band and center
frequency.
● The power spectral density (PSD) of the LTE and NR cells using the maximum
transmit power must be the same.
● LTE and NR cells must be deployed in 1:1 co-coverage mode and they must be
served by the same transmit channels of an RF module.
4.3.4 Networking
This function requires an intra-BBU CPRI MUX topology, which poses no special
requirements on board installation positions. LTE and NR cells can be established
on the same baseband processing unit or on different baseband processing units.
The following illustrates the networking requirements using LTE and NR cells
established on different baseband processing units as an example.
● Intra-BBU CPRI MUX topology in separate-MPT scenarios: LTE and NR share a
BBU, and only the LTE baseband processing unit or only the NR baseband
processing unit is connected directly to the RRU through an optical fiber, as
shown in Figure 4-3.
● Intra-BBU CPRI MUX topology in co-MPT scenarios: LTE and NR share a BBU,
and only the LTE baseband processing unit or only the NR baseband
processing unit is connected directly to the RRU through an optical fiber, as
shown in Figure 4-4.
4.3.5 Others
● MRFD-160222 LTE FDD and NR Flash Dynamic Spectrum Sharing (LTE FDD)
and MRFD-160262 LTE FDD and NR Flash Dynamic Spectrum Sharing (NR)
must be used simultaneously.
● It is recommended that this function be enabled on NR FDD networks using
time synchronization to reduce the NR SSB overhead and ensure the
performance of LTE FDD and NR FDD networks.
● NR UEs must support the CRS rate matching function. This function allows
the gNodeB to indicate the RE position of the LTE CRS, so that NR UEs can
avoid a conflict with the LTE CRS. UEs support the CRS rate matching function
when the rateMatchingLTE-CRS IE is included in the BandNR IE and the value
of the rateMatchingLTE-CRS IE is "supported". For details, see section 5.1.4.2
"PDSCH resource mapping with RE level granularity" in 3GPP TS 38.214
V15.5.0.
Only the NR UEs that support CRS rate matching on the live network support
LTE FDD and NR Flash Dynamic Spectrum Sharing. NR UEs that do not
support CRS rate matching cannot access NR FDD cells enabled with LTE FDD
and NR Flash Dynamic Spectrum Sharing. They access LTE cells enabled with
LTE FDD and NR Flash Dynamic Spectrum Sharing or access NR FDD cells not
enabled with this function.
● If the LTE and NR co-carrier co-CPRI data switch and CPRI compression
function are both enabled, the CPRI compression ratios must be the same
between the LTE and NR cells. The CPRI compression type of LTE cells is
specified by the Cell.CPRICompression parameter, and the CPRI compression
type of NR cells is specified by the NRDUCellTrp.CpriCompression parameter.
Table 4-19 describes the configuration requirements.
CAUTION
units, cell activation may fail when the baseband processing units supporting this
function are fully occupied while other baseband processing units do not support
this function.
MBB LTE Pri Res Ratio in LteNrSpctShrCellGrp.Lt Set this parameter based
LTE and NR Spct Shr eNrSpctShrLtePriResRa- on the network plan.
tio This parameter value
varies with the spectrum
allocation policy. The
following lists the
configuration
suggestions for ensuring
the network
performance when
different spectrum
allocation policies are
adopted:
● If spectrum resources
need to be
preferentially
allocated to LTE, it is
recommended that
this parameter be set
to a value within the
range of 51 to 80.
● If spectrum resources
need to be
preferentially
allocated to NR, it is
recommended that
this parameter be set
to a value within the
range of 20 to 49.
● If spectrum resources
need to be evenly
allocated to LTE and
NR, it is
recommended that
this parameter be set
to 50.
a: In the current version, an LTE spectrum sharing cell group can contain only
one LTE cell.
b: For details about the configuration principles of these four parameters, see
the description of the LTE PUCCH in 4.1.2 Key Technologies of Flash Dynamic
Spectrum Sharing.
c: If both the frame offset (specified by the CellFrameOffset.FrameOffset
parameter) and the FDD frame offset (specified by the
ENodeBFrameOffset.FddFrameOffset parameter) are configured, the frame
offset (specified by the CellFrameOffset.FrameOffset parameter) takes effect
for the LTE cell.
MS5(5) 9586980
MS10(10) 8521760
MS20(20) 8390656
Without the SSB dual- ● When the SSB period is set to MS5(5), set this
beam function parameter to 11684132.
● When the SSB period is set to MS10(10), set this
parameter to 10618912.
● When the SSB period is set to MS20(20), set this
parameter to 10487808.
● When the SSB period is set to MS40(40) or a
larger value, set this parameter to 10485760.
With the SSB dual-beam ● When the SSB period is set to MS5(5), set this
function parameter to 15878436.
● When the SSB period is set to MS10(10), set this
parameter to 14813216.
● When the SSB period is set to MS20(20), set this
parameter to 14682112.
● When the SSB period is set to MS40(40) or a
larger value, set this parameter to 14680064.
a: In the current version, an NR spectrum sharing cell group can contain only
one NR cell.
b: If both the gNodeBParam.FrameOffset and
gNBFreqBandConfig.FrameOffset parameters are configured, the frame offset
specified by the gNBFreqBandConfig.FrameOffset parameter takes effect for
the LTE cell.
NOTICE
Before activating this function in LTE and NR cells, start signaling tracing on the
MAE-Access. Otherwise, messages regarding the activation of this function cannot
be observed after this function is activated.
LTE FDD and NR Flash Dynamic Spectrum Sharing takes effect when the following
conditions are met on both the eNodeB and gNodeB sides:
Perform the following steps to start eNodeB message tracing on the MAE-Access:
Step 1 Log in to the MAE-Access. Choose Monitor > Signaling Trace > Signaling Trace
Management. In the navigation tree of the displayed window, expand LTE >
Application Layer > Inter-RAT Huawei-Proprietary Interface Trace.
Step 2 In the displayed dialog box, select an NE and set related parameters. Then, click
Finish to start an inter-RAT Huawei-proprietary interface tracing task.
Step 3 After this function is activated in LTE and NR cells, messages are traced over the
inter-RAT Huawei-proprietary interface. View the value of the lnss-group-status-
change-info > nr-ul-cell-information/nr-dl-cell-information > spectrum-
sharing-status IE in the LNR_INTER_RAT_SPECTRUM_CHANGE_INDICATION
message. The value is ss-dynamic-sharing.
----End
Perform the following steps to start gNodeB message tracing on the MAE-Access:
Step 1 Log in to the MAE-Access. Choose Monitor > Signaling Trace > Signaling Trace
Management. In the navigation tree of the displayed window, expand NR >
Application Layer > Inter-RAT Huawei-Proprietary Interface Trace.
Step 2 In the displayed dialog box, select an NE and set related parameters. Then, click
Finish to start an inter-RAT Huawei-proprietary interface tracing task.
Step 3 After this function is activated in LTE and NR cells, messages are traced over the
inter-RAT Huawei-proprietary interface. View the value of the lnss-group-status-
change-info > nr-ul-cell-information/nr-dl-cell-information > spectrum-
sharing-status IE in the LNR_INTER_RAT_SPECTRUM_CHANGE_INDICATION
message. The value is ss-dynamic-sharing.
----End
5 Parameters
You can find the EXCEL files of parameter reference and used reserved parameter list for
the software version used on the live network from the product documentation delivered
with that version.
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
Step 1 Open the EXCEL file of the used reserved parameter list.
Step 2 On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT
columns to locate the reserved parameter, which may be only a bit of a parameter.
View its information, including the meaning, values, impacts, and product version
in which it is activated for use.
----End
6 Counters
The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● 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.
----End
7 Glossary
8 Reference Documents
● 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception"
● Feature parameter description documents in eRAN Feature Documentation
– Carrier Aggregation
– Scheduling
– Physical Channel Resource Management
– VoLTE
– MIMO
– eMIMO (FDD)
– UL CoMP
– DRX and Signaling Control
– Intra-RAT Mobility Load Balancing
– LCS
– Extended CP
– Random Access Control
– SFN
– Compact Bandwidth (FDD)
– GSM and LTE FDD Dynamic Spectrum Sharing
– Flexible Bandwidth based on Overlap Carriers (FDD)
– GSM and LTE Zero Bufferzone
– GSM and LTE Buffer Zone Optimization
– UL Refarming Zero Bufferzone
– UMTS and LTE Zero Bufferzone
– CDMA and LTE Zero Bufferzone
– Uplink Coordinated Scheduling
– CSPC
– Adaptive ICIC
– Relay
– eMTC