Professional Documents
Culture Documents
Contents
6.2 LTE FDD and NR Spectrum Sharing
SingleRAN
LTE FDD and NR Spectrum Sharing
Feature Parameter Description
Issue 03
Date 2020-05-21
HUAWEI TECHNOLOGIES CO., LTD.
Website: https:/
Email: support@huawei.com
6.2 Contents
1 Change History
1.1 SRAN16.1 03 (2020-05-21)
1.2 SRAN16.1 02 (2020-04-07)
1.3 SRAN16.1 01 (2020-03-30)
1.4 SRAN16.1 Draft B (2020-03-09)
1.5 SRAN16.1 Draft A (2020-01-20)
3 Overview
5 Parameters
6 Counters
7 Glossary
8 Reference Documents
1 Change History
This chapter describes changes not included in the "Parameters", "Counters", "Glossary", and
"Reference Documents" chapters. These changes include:
Technical changes
Changes in functions and their corresponding parameters
Editorial changes
Improvements or revisions to the documentation
1.1 SRAN16.1 03 (2020-05-21)
Technical Changes
Added the impact relationship between this None 3900 and 5900 series
function and Cell Switch-off Based on base stations
Automatic Co-coverage Identification. For
details, see 4.2.2 Impacts.
Change Description Parameter Change Base Station Model
Added the impact relationship between this None 3900 and 5900 series
function and multi-carrier coordinated energy base stations
saving. For details, see 4.2.2 Impacts.
Editorial Changes
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 and SIB1 period parameters. 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.
1.2 SRAN16.1 02 (2020-04-07)
Technical Changes
Change Description Parameter Change Base Station
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 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
Modified the counters for measuring the None 3900 and 5900 series
numbers of uplink and downlink available RBs. base stations
For details, see 4.1.1 Principles of Flash Dynamic
Spectrum Sharing.
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.
1.4 SRAN16.1 Draft B (2020-03-09)
Technical Changes
Removed the mutually exclusive relationship None 3900 and 5900 series
with the following functions: high speed base stations
mobility, ultra high speed mobility, uplink
delay-based scheduling strategy, high-
mobility-triggered idle mode, dynamic voltage
adjustment, eNodeB-based interference
randomization, uplink interference
randomization, and LTE FDD and NR Uplink
Spectrum Sharing. Added the impact
relationship with the following functions: high
speed mobility, ultra high speed mobility,
dynamic voltage adjustment, eNodeB-based
interference randomization, and uplink
interference randomization. For details, see
4.2.2 Impacts and 4.3.2 Software.
Added the mutually exclusive relationship with None 3900 and 5900 series
UE-specific PDCCH symbol number base stations
adaptation. For details, see 4.3.2 Software.
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 BBPe5 and BBPe6 boards and
their LTE cell specifications. For details, see 4.3.3 Hardware.
Revised the description of requirements on NR UEs. For details, see 4.3.5 Others.
Revised the description of the configuration suggestions for the parameter specifying
the percentage of resources that can be preferentially allocated to LTE. For details, see
4.4.1.1 Data Preparation.
Revised the description of MML command examples. For details, see 4.4.1.2 Using MML
commands.
Purpose
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.
2.2 Applicable RAT
MRFD-160222 LTE FDD and NR Flash 4 LTE FDD and NR Flash Dynamic
Dynamic Spectrum Sharing Spectrum Sharing
(LTE FDD)
2.4 Differences
Table 2-1 Differences between NR FDD and NR TDD
Function Name Difference Chapter/Section
LTE FDD and NR Flash Only NR FDD supports this 4 LTE FDD and NR Flash Dynamic
Dynamic Spectrum Sharing function. Spectrum Sharing
LTE FDD and NR Flash Whether the NR 4 LTE FDD and NR Flash Dynamic
Dynamic Spectrum Sharing Spectrum Sharing
PUCCH includes
the common
PUCCH differs
between NSA
networking and SA
networking.
The configuration
suggestions for the
SSB frequency
position, four frame
allocation, and SIB1
period parameters
differ between NSA
networking and SA
networking.
This feature
provides different
Function Name Difference Chapter/Section
gains in NSA
networking and SA
networking.
Table 2-3 Differences between high frequency bands and low frequency bands
Function Name Difference Chapter/Section
LTE FDD and NR Flash This function is supported only 4 LTE FDD and NR Flash Dynamic
Dynamic Spectrum Sharing in low frequency bands. Spectrum Sharing
In this document, low frequency bands refer to those that belong to FR1 (410 MHz – 7125
MHz), and high frequency bands refer to those that belong to FR2 (24250 MHz – 52600 MHz).
For details about the definitions of FR1 and FR2, see section 5.1 "General" in 3GPP TS 38.104
(V15.5.0).
3 Overview
Some operators do not possess dedicated NR spectrum resources in the early stage of 5G
deployment. Other operators have dedicated NR spectrum resources, but face the issue of low
spectrum usage due to a low penetration rate of 5G terminals in the early stage. LTE FDD and
NR Flash Dynamic Spectrum Sharing allows for the sharing of uplink and downlink spectrum
resources between LTE FDD and NR. For operators that do not possess dedicated NR spectrum
resources, this feature can be used to enable LTE to share existing LTE spectrum with NR,
allowing fast 5G deployment. For operators having dedicated NR spectrum resources, this
feature enables NR to share spectrum with LTE, improving the spectrum usage. For ease of
description, LTE will hereafter be used to refer to LTE FDD.
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.
4.1.1 Principles of Flash Dynamic Spectrum Sharing
The LTE FDD and NR Flash Dynamic Spectrum Sharing function is enabled by turning on
function switches and configuring spectrum sharing cell groups. In addition, the LTE and NR
cells added to spectrum sharing cell groups must have completely aligned radio frames and
subframes.
Turning on function switches
Set the LTE parameter SpectrumCloud.SpectrumCloudSwitch to
LTE_NR_SPECTRUM_SHR.
Select the LTE_NR_FDD_SPCT_SHR_SW option of the NR parameter
NRDuCellAlgoSwitch.SpectrumCloudSwitch.
Configuring spectrum sharing cell groups
Add planned LTE cells to an LTE spectrum sharing cell group by setting
LTE parameters SpectrumCloud.LteNrSpectrumShrCellGrpId and
LteNrSpctShrCellGrp.LteNrSpectrumShrCellGrpId.
Configure an association between the LTE spectrum sharing cell group and
an NR spectrum sharing cell group using NR parameters
gNBDULteNrSpctShrCg.NrSpctShrCellGrpId and
gNBDULteNrSpctShrCg.LteSpctShrCellGrpId.
Add planned NR cells to the NR spectrum sharing cell group by setting NR
parameters NRDUCellSpctCloud.NrDUCellId and
NRDUCellSpctCloud.NrSpctShrCellGrpId.
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.
Time domain: Flash spectrum sharing is supported on a 1 ms basis. That is, spectrum
resources can be coordinated and scheduled every 1 ms.
Frequency domain: Dynamic spectrum sharing is performed per RB. Spectrum
resources are dynamically allocated to LTE and NR based on the traffic volumes of
LTE and NR networks.
Figure 4-1 Flash dynamic spectrum sharing between LTE and NR
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.
4.1.2 Key Technologies of Flash Dynamic Spectrum Sharing
Inter-RAT interference is generated during LTE and NR spectrum sharing. The interference can
be avoided by properly coordinated scheduling of uplink and downlink physical channel
resources, so as to improve the spectrum usage.
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.
The downlink physical channel resources are coordinated and scheduled as follows:
The NR Synchronization Signal and PBCH block (SSB) is transmitted in fixed
positions in Case A.
If a single SSB beam is used for cell coverage, the NR SSB is transmitted in
the position indicated by index 3.
If two SSB beams are used for cell coverage, the NR SSB is transmitted in
positions indicated by index 2 and index 3.
The LTE SS/PBCH and NR SSB are transmitted in different occasions. For details,
see section 4.1 "Cell Search" in 3GPP TS 38.213 V15.5.0.
The information transmitted on the NR PDSCH except for SIB1 avoids a conflict with
the LTE cell-specific reference signal (CRS) by CRS rate matching. For details about
CRS rate matching, see section 5.1.4.2 "PDSCH resource mapping with RE level
granularity" in 3GPP TS 38.214 V15.5.0. LTE FDD and NR Flash Dynamic Spectrum
Sharing requires that NR UEs support CRS rate 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 the SSB dual-
beam function. For details, see the configuration suggestions in 4.4.1.1 Data Preparation.
The SSB dual-beam function enables the use of two SSB beams for cell coverage, and
is elaborated in Beam Management in 5G RAN Feature Documentation.
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
GSCN. After the NR SSB frequency-domain position is determined, UEs
can access the cell.
NRDUCell.SsbFreqPos: The frequency-domain position type indicated by
this parameter is determined based on the value of the
NRDUCell.SsbDescMethod parameter. The frequency-domain position type
must be confirmed by Huawei engineers.
Before configuring the preceding two parameters, if the
NRDUCellPdcch.OccupiedSymbolNum parameter is set to 2SYM, you need to set the
NR parameter NRDUCellCoreset.CommonCtrlResRbNum to RB24 or RB48. This
ensures that the number of RBs for common control resources in the cell meets the
requirements of LTE FDD and NR Flash Dynamic Spectrum Sharing. If the
NRDUCellPdcch.OccupiedSymbolNum parameter is set to 1SYM, this parameter does
not need to be configured.
The NR PDCCH and PDSCH can share spectrum resources in frequency division
multiplexing (FDM) mode, which is controlled by the PDCCH_RATEMATCH_SW
option of the NR parameter NRDUCellPdsch.RateMatchSwitch.
The number of guaranteed RBs for the NR PDCCH can be configured
through the NR parameter NRDUCellPdcch.GuaranteedRbNum. The NR
PDCCH resource requirements are preferentially met. When the number of
PDCCH RBs required by an NR cell is greater than the value of this
parameter, PDCCH RBs are allocated based on the service requirement.
When the number of PDCCH RBs required by an NR cell is smaller than
the value of this parameter, PDCCH RBs are allocated based on the value of
this parameter.
The downlink additional DMRS position can be configured for the NR
PDSCH by setting the NR parameter NRDUCellPdsch.DlAdditionalDmrsPos
to POS1, to improve user experience in high-speed mobility scenarios. In
non-high-speed mobility scenarios, this parameter needs to be set to
NOT_CONFIG.
The NR PDSCH and SSB can share spectrum resources in time division multiplexing
(TDM) mode, which is controlled by the SSB_RATEMATCH_SW option of the NR
parameter NRDUCellPdsch.RateMatchSwitch.
4.2 Network Analysis
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.
and Table 4-3 list the gains provided by this function in different networking compared
Table 4-2
with when a typical static refarming solution is enabled.
Table 4-2 Average cell downlink throughput gain in NSA networking
Cell TX Total LTE NR LTE Cell Downlink NR Cell Downlink
Mode Bandwidth Bandwidtha Bandwidtha Throughput Gainb Throughput Gainb
a: LTE bandwidth and NR bandwidth in a static refarming solution when this function is not
enabled
b: LTE cell gain and NR cell gain provided by this function compared with when a static
refarming solution is enabled. If LTE and NR share spectrum power while sharing spectrum,
the NR cell gain decreases by 5% to 8%, and the LTE cell gain is not affected. If LTE and NR
use separate spectrum power when they share spectrum, the LTE and NR cell gains are not
affected.
Table 4-3 Average cell downlink throughput gain in SA networking
Cell TX Total LTE NR LTE Cell Downlink NR Cell Downlink
Mode Bandwidth Bandwidtha Bandwidtha Throughput Gainb Throughput Gainb
a: LTE bandwidth and NR bandwidth in a static refarming solution when this function is not
enabled
b: LTE cell gain and NR cell gain provided by this function compared with when a static
refarming solution is enabled. If LTE and NR share spectrum power while sharing spectrum,
the NR cell gain decreases by 5% to 8%, and the LTE cell gain is not affected. If LTE and NR
use separate spectrum power when they share spectrum, the LTE and NR cell gains are not
affected.
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
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
Counter ID Counter Name
1526727356 L.Traffic.DL.SCH.64QAM.TB
1526739656 L.Traffic.DL.SCH.256QAM.TB
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.ExecSuccOu
1526727000 L.HHO.IntraeNB.InterFreq.ExecSuccOu
1526727003 L.HHO.IntereNB.IntraFreq.ExecSuccOu
1526727006 L.HHO.IntereNB.InterFreq.ExecSuccOu
1526726996 L.HHO.IntraeNB.IntraFreq.ExecAttOut
1526726999 L.HHO.IntraeNB.InterFreq.ExecAttOut
Counter ID Counter Name
1526727002 L.HHO.IntereNB.IntraFreq.ExecAttOut
1526727005 L.HHO.IntereNB.InterFreq.ExecAttOut
Table 4-10 Counters used for measuring the RRC connection
reestablishment success rate
Counter ID Counter Name
1526727086 L.RRC.ReEst.Succ
1526727085 L.RRC.ReEst.Att
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
Average uplink throughput of a UE = (L.Thrp.bits.UL –
L.Thrp.bits.UE.UL.SmallPkt)/L.Thrp.Time.UE.UL.RmvSmal
lPkt. Average downlink throughput of a UE = (L.Thrp.bits.DL
– L.Thrp.bits.DL.LastTTI)/L.Thrp.Time.DL.RmvLastTTI.
Table 4-13 lists the related counters.
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
1911816696 N.ThpVol.UL.Cell
1911816697 N.ThpTime.UL.Cell
1911816694 N.ThpVol.DL.Cell
1911816695 N.ThpTime.DL.Cell
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
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
Average user-plane CPU usage of a board in an eNodeB:
L.Traffic.Board.UPlane.CPULoad.AVG
Average user-plane CPU usage of a gNodeB board:
VS.NRBoard.UPlane.CPULoad.Avg
Function Impacts
available for
LTE
decreases,
which reduces
the throughput
of UEs for
which FDD
uplink carrier
aggregation
(CA) takes
effect.
as PCells, the
PUCCH
overhead is so
large that the
SRS cannot be
configured.
Consequently,
LTE network
throughput
decreases.
decreases,
which
increases the
pairing
success rate of
downlink MU-
MIMO.
Consequently,
the BLER
increases.
decreases,
and therefore
the average
number of
scheduling
times
decreases. As
a result, the
average
number of UEs
that enter DRX
mode, as well
as the
frequency of
UEs entering
and exiting
DRX mode
increase.
Flash Dynamic
Spectrum
Sharing should
not be enabled
with this
function.
to achieve the
optimal gains.
However, LTE
FDD and NR
Flash Dynamic
Spectrum
Sharing cannot
be enabled
together with
the SFN
function.
Therefore,
when ultra high
speed mobility
is enabled
together with
LTE FDD and
NR Flash
Dynamic
Spectrum
Sharing, the
gain produced
by downlink
AFC
decreases.
two cells,
increasing bit
errors.
Sharing is
enabled, the
amount of
spectrum
resources
available for
LTE
decreases. As
a result, the
gains provided
by uplink
interference
randomization
decrease.
Identification
feature does
not take effect
when LTE
FDD and NR
Flash Dynamic
Spectrum
Sharing is
enabled. This
is because the
LTE carrier
cannot be
independently
shut down
when LTE
FDD and NR
share the
carrier.
4.3 Requirements
4.3.1 Licenses
LTE MRFD- LTE FDD and LT1S0LFNSS00 LTE FDD and NR eNodeB per Cell
FDD 160222 NR Flash Flash Dynamic
Dynamic Spectrum
Spectrum Sharing(LTE FDD)
Sharing (LTE
FDD)
NR MRFD- LTE FDD and NR0S00FNSS00 LTE FDD and NR gNodeB per Cell
160262 NR Flash Flash Dynamic
Dynamic Spectrum Sharing
Spectrum (NR)
Sharing (NR)
LTE FDD LT1S5000RFSS Spectrum Sharing License for eNodeB per Band per
5000 Series RF Module(FDD) RU
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
configuratio Resource
n Managemen
t
GSM and LTE GLDynSpectrumShareSwitch option of the GSM and LTE FDD
FDD Dynamic CellAlgoSwitch.DynSpectrumShareSwitch parameter Dynamic Spectrum
Spectrum Sharing
Sharing
GSM and LTE GLZeroBufferZoneSwitch option of the GSM and LTE Zero
Zero CellAlgoSwitch.DynSpectrumShareSwitch parameter Bufferzone
Bufferzone
GSM and LTE AvoidGeranInterfSwitch option of the GSM and LTE Buffer
Function Name Function Switch Reference (eRAN
Feature
Documentation)
Adaptive Activated using the ACT AICIC command on the Adaptive ICIC
Inter-Cell eCoordinator
Interference
Coordination
Sharing
a: The mutually exclusive relationship exists only when LTE FDD and NR share spectrum
Function Name Function Switch Reference (eRAN
Feature
Documentation)
a: LTE FDD and NR Flash Dynamic Spectrum Sharing is mutually exclusive with the
NRDUCellPdsch.DlAdditionalDmrsPos parameter (set to a value other than NOT_CONFIG and
POS1) in the basic functions of downlink scheduling.
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.
LTE:
3900 and 5900 series base stations. 3900 series base stations must be configured with
the BBU3900 or BBU3910, and 5900 series base stations must be configured with the
BBU5900 or BBU5900A.
NR:
3900 and 5900 series base stations. 3900 series base stations must be configured with
the BBU3910.
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, and UBBPg3
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.
Table 4-18 Cell specifications of LTE baseband processing units
Working Mode Baseband Processing Supported LTE Cell Specifications
Unit Model
LTE FDD or LMa UBBPd5 The cell specifications decrease from six 2T2R
cells or three 2T4R or 4T4R cells to three cells.
All of the three cells can be enabled with LTE
FDD and NR Flash Dynamic Spectrum
Sharingb.
LTE FDD or LM UBBPd6 The cell specifications decrease from six 2T2R,
2T4R, or 4T4R cells to three cells. All of the
three cells can be enabled with LTE FDD and
NR Flash Dynamic Spectrum Sharing.
LTE FDD or LM UBBPe1 Three 2T2R cells. All of them can be enabled
with LTE FDD and NR Flash Dynamic
Spectrum Sharing.
LTE FDD or LM UBBPe2 Three 2T2R, 2T4R, or 4T4R cells. All of them
can be enabled with LTE FDD and NR Flash
Dynamic Spectrum Sharing.
LTE FDD or LM UBBPe3 Six 2T2R cells, or three 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 or LM UBBPe4 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, or UBBPe5 LTE FDD or LM: Nine 2T2R, 2T4R,
other working modes or 4T4R cells. Among them, a
involving LTE FDD maximum of six can be enabled with
LTE FDD and NR Flash Dynamic
Spectrum Sharing; other cells are
common cells.
Working Mode Baseband Processing Supported LTE Cell Specifications
Unit Model
LTE FDD, LM, GL, or UBBPe6 LTE FDD or LM (with BBP.SRT set
other working modes to DEFAULT): Twelve 2T2R, 2T4R,
involving LTE FDD 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.
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, or UBBPg Same as that before this function is enabled
other working modes
involving LTE FDD
To prevent LTE cell activation failures due to insufficient baseband processing resources, cells
enabled with this function must be bound to baseband processing units supporting this function.
If cells are not bound to such baseband processing 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.
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 supports 2T2R, 2T4R, or 4T4R.
Cells
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-2.
Figure 4-2 Intra-BBU CPRI MUX topology in separate-MPT scenarios
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-3.
Figure 4-3 Intra-BBU CPRI MUX topology in co-MPT scenarios
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.
Table 4-19 Configuration requirements on the CPRI compression types of the LTE and NR
cells
Bandwidth CPRI Compression CPRI Compression Type for CPRI Compression Type for
Ratio LTE Cells NR Cells
If the activation of this function is to be verified through signaling message tracing, you need to
start signaling tracing on the MAE-Access before activating this function in LTE and NR cells.
Otherwise, messages regarding the activation of this function cannot be observed after this
function is activated.
4.4.1.1 Data Preparation
and Table 4-23 describe the parameters used for function activation, Table 4-24 describes
Table 4-20
the parameters used for optimization. This section does not describe parameters related to cell
establishment.
Since the configuration of some parameters can result in automatic cell restarts in function
activation and deactivation, it is recommended that you deactivate the cells prior to parameter
configuration and reactivate them after parameter configuration is complete. This will prevent
these cells from repeatedly being restarted during parameter configuration.
To prevent LTE cell activation failures due to insufficient baseband processing resources, cells
enabled with this function must be bound to baseband processing units supporting this function.
If cells are not bound to such baseband processing 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.
Table 4-20 LTE parameters used for activation
Paramet Parameter ID Setting Notes
er Name
Table 4-21.
In SA networking, the
configuration suggestions
for this parameter vary
depending on the SSB
period and whether the
SSB dual-beam function is
used. For details, see Table
4-22.
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.
Table 4-21 Configuration suggestions for Four Frame Allocation in NSA networking
GUI Value of SSB Period Setting Notes
MS5(5) 9586980
MS10(10) 8521760
MS20(20) 8390656
Without the SSB dual-beam When the SSB period is set to MS5(5), set this
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.
Table 4-23 NR parameters used for activation
Parameter Parameter ID Setting Notes
Name
Symbol
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.
Table 4-24 NR parameters used for optimization
Parameter Name Parameter ID Setting Notes
This function must be activated or deactivated on both the LTE and NR sides.
Check whether LTE FDD and NR Flash Dynamic Spectrum Sharing has taken effect using
MML commands or tracing signaling messages. The spectrum sharing mode in use can be
queried using MML commands.
LTE FDD and NR Flash Dynamic Spectrum Sharing takes effect when both of the following
conditions are met:
The value of the Spectrum Sharing Status parameter in the output of the eNodeB
MML command DSP LTENRSPCTSHRCELLGRP is DYNAMIC_SHARING.
The value of the Spectrum Sharing Status parameter in the output of the gNodeB
MML command DSP GNBDULTENRSPCTSHRCG is Dynamic Sharing.
The spectrum sharing mode is indicated by the Spectrum Sharing Mode parameter in the output
of the eNodeB MML command LST SPECTRUMCLOUD. The value can be
LTE_NR_PWR_DYN_SHR_WITH_SPCT or LTE_NR_PWR_INDEPENDENT.
After this function is enabled, monitor the network gains and impacts of this function using the
counters listed in 4.2 Network Analysis.
5 Parameters
The following hyperlinked EXCEL files of parameter reference match the software version with
which this document is released.
Node Parameter Reference: contains device and transport parameters.
gNodeBFunction Parameter Reference:contains all parameters related to radio access
functions, including air interface management, access control, mobility control, and
radio resource management.
You can find the EXCEL files of parameter reference for the software version used 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?
1. Open the EXCEL file of parameter reference.
2. On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, FBFD-020100.
3. Click OK. All parameters related to the feature are displayed.
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.
gNodeBFunction Performance Counter Summary:
contains all counters related to radio access
functions, including air interface management, access control, mobility control, and
radio resource management.
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?
1. Open the EXCEL file of performance counter reference.
2. On the Counter Summary(En) sheet, filter the Feature ID column. Click Text
Filters and choose Contains. Enter the feature ID, for example, FBFD-020100.
3. Click OK. All counters related to the feature are displayed.
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
NB-IoT Basics (FDD)
Extended Cell Range
Superior Uplink Coverage (FDD)
eMBMS
Virtual 4T4R (FDD)
DL CoMP (FDD)
GSM and LTE Dynamic Power Sharing
Super Combined Cell (FDD)
Energy Conservation and Emission Reduction
TDM eICIC (FDD)
ICIC
Short TTI (FDD)
PTT
On-Demand TX Power Allocation Under EME
Dedicated Carrier for TM9 (FDD)
Seamless Intra-Band Carrier Joining (FDD)
Feature parameter description documents in 5G RAN Feature Documentation:
Carrier Aggregation
Scheduling
Channel Management
Power Control
Multi-Operator Sharing
Beam Management
VoNR
Dynamic Power Sharing Between LTE Carriers