5G RAN Feature Documentation 5G RAN2.1 - 07 20201229173029
5G RAN Feature Documentation 5G RAN2.1 - 07 20201229173029
Contents
6.2 LTE and NR Spectrum Sharing
SingleRAN
LTE and NR Spectrum Sharing Feature
Parameter Description
Issue 06
Date 2020-08-05
HUAWEI TECHNOLOGIES CO., LTD.
Website: https:/
Email: [email protected]
6.2 Contents
1 Change History
1.1 SRAN15.1 06 (2020-08-05)
1.2 SRAN15.1 05 (2020-03-25)
1.3 SRAN15.1 04 (2019-09-05)
1.4 SRAN15.1 03 (2019-07-20)
1.5 SRAN15.1 02 (2019-06-29)
1.6 SRAN15.1 01 (2019-06-06)
1.7 SRAN15.1 Draft E (2019-05-10)
1.8 SRAN15.1 Draft D (2019-04-10)
1.9 SRAN15.1 Draft C (2019-03-18)
1.10 SRAN15.1 Draft B (2019-02-22)
1.11 SRAN15.1 Draft A (2018-12-30)
4 Parameters
5 Counters
6 Glossary
7 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 SRAN15.1 06 (2020-08-05)
Technical Changes
None
Editorial Changes
Technical Changes
None
Editorial Changes
Revised the description of time synchronization. For details, see 3.1.1 Static Spectrum
Sharing, 3.1.2 Dynamic Spectrum Sharing, 3.4.2.1 Data Preparation, and 3.4.2.2 Using MML Commands.
Technical Changes
None
Editorial Changes
Modified the description of network impact. For details, see 3.2.2 Impacts.
Added the description of requirements on radio access devices. For details, see 3.3.3
Hardware.
Added MML configuration examples of binding a cell that requires this function to a
baseband processing unit supporting this function. For details, see 3.4.2.2 Using MML
Commands.
Revised descriptions in this document. For details, see descriptions throughout the
document.
1.4 SRAN15.1 03 (2019-07-20)
Technical Changes
None
Editorial Changes
Deleted the description of the inter-BBU CPRI MUX topology. For details, see 3.3.4
Networking.
Revised the description of the uplink PRB usage. For details, see 3.4.1 When to Use.
Revised descriptions in this document. For details, see descriptions throughout the
document.
1.5 SRAN15.1 02 (2019-06-29)
Technical Changes
None
Editorial Changes
Technical Changes
None
Editorial Changes
Revised the description of the technical principles of static spectrum sharing and dynamic
spectrum sharing. For details, see 3.1 Principles.
1.7 SRAN15.1 Draft E (2019-05-10)
Technical Changes
Added support for 700 MHz and AWS by None 3900 and 5900
5000 series RRUs. For details, see 3.3.3 series base stations
Hardware.
Editorial Changes
Technical Changes
None
Editorial Changes
Added the description of requirements on the frequency band, center frequency, and
standard bandwidth. For details, see 3.1 Principles and 3.3.3 Hardware.
Revised the description of time synchronization requirements. For details, see 3.3.4
Networking.
Technical Changes
Added support for NR by 3900 series base None 3900 and 5900
stations. For details, see 3.3.3 Hardware. series base stations
Editorial Changes
Revised the description of configuration suggestions for frame offset. For details, see 3.4.2.1
Data Preparation.
Technical Changes
Updated the RF modules that support LTE None 3900 and 5900
FDD and NR Uplink Spectrum Sharing. For series base stations
details, see 3.3.3 Hardware.
Editorial Changes
Revised the description of principles. For details, see 3.1 Principles.
Added the description of time synchronization requirements. For details, see 3.3.4
Networking.
Revised the description of the simultaneous use with FDD+TDD Carrier Aggregation.
For details, see 3.3.5 Others.
Revised the description of data preparation and MML configuration. For details, see
3.4.2.1 Data Preparation and 3.4.2.2 Using MML Commands.
Technical Changes
Editorial Changes
Revised the networking conditions for the LTE and NR co-carrier co-CPRI data
function. For details, see 3.1.2 Dynamic Spectrum Sharing.
Added the description of the impact of this function on SRS. For details, see 3.2.2 Impacts.
Revised the description of networking requirements. For details, see 3.3.4 Networking.
Added the description of the requirements on the simultaneous use with FDD+TDD
Carrier Aggregation and CPRI Compression. For details, see 3.3.5 Others.
Revised the description of data configuration of LTE and NR static uplink spectrum
sharing. For details, see 3.4.2 Data Configuration.
Revised the description of activation verification by using counters. For details, see 3.4.3
Activation Verification.
Revised descriptions in this document. For details, see descriptions throughout the
document.
Purpose
Software Interfaces
MRFD-131223 LTE FDD and NR Uplink Spectrum 3 LTE FDD and NR Uplink Spectrum
Sharing (LTE FDD) Sharing
3.1 Principles
5G is usually deployed in the C-band frequency band in the early stage of 5G network
construction. C-band's uplink coverage is inferior to its downlink coverage, and that affects
the deployment of 5G networks. UL and DL Decoupling can be used in areas with limited
NR uplink coverage to allow downlink data to be transmitted in C-band and uplink data to
be transmitted in a sub-3 GHz frequency band. If operators do not have dedicated sub-3
GHz uplink spectrum for 5G, UL and DL Decoupling cannot be used. LTE FDD and NR
Uplink Spectrum Sharing is introduced to allow for the sharing of uplink low-band
spectrum resources between LTE FDD and NR. The uplink low-band spectrum sharing
serves as a basis for NR UL and DL Decoupling and improves NR uplink coverage. Figure
3-1 shows LTE FDD and NR uplink spectrum sharing. For details about UL and DL
Decoupling, see UL and DL Decoupling.
Figure 3-1 LTE FDD and NR uplink spectrum sharing
In addition, both static and dynamic uplink spectrum sharing is supported. Operators can
choose static sharing or dynamic sharing based on their network plans. Unless otherwise
specified, the following descriptions apply to both static sharing and dynamic sharing.
Dynamic sharing is recommended to achieve higher spectral efficiency.
For ease of description, LTE is used to refer to LTE FDD, for example, LTE FDD cells are
referred to as LTE cells. The NR cells in this function refer to NR supplementary uplink
(SUL) cells.
3.1.1 Static Spectrum Sharing
Technical Principles
In static spectrum sharing, eNodeB and gNodeB share spectrum resources based on a pre-
configured percentage of LTE and NR uplink physical channel resources, as shown in Figure
3-2.
10 MHz 3 46
15 MHz 2 72
20 MHz 1 98
Assume that 12 RBs are configured for the LTE PUCCH in 15 MHz bandwidth
scenarios. Then, the LTE PUCCH occupies RBs with indexes 2 to 7 at the lower end,
and occupies RBs with indexes 67 to 72 at the upper end.
LTE physical random access channels (PRACH): The LTE PRACH is configured
adjacent to the LTE PUCCH at the lower end. Six RBs are reserved for the LTE
PRACH.
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 specified by the
NRDUCell.PrachFreqStartPosition parameter. Six RBs are reserved for the NR PRACH.
For example, if the LTE PUCCH occupies RBs with indexes 69 to 72 at the upper end in
15 MHz bandwidth scenarios, the NRDUCell.PrachFreqStartPosition parameter must be
set to 63 so that the NR PRACH occupies RBs with indexes 63 to 68. The LTE PUCCH
and NR PRACH require the configurations of other related parameters. For details about
how to configure these parameters, see 3.4.2.1 Data Preparation.
LTE and NR physical uplink shared channels (PUSCHs): The total resources available
for the LTE and NR PUSCHs equal the total available spectrum resources minus the
resources occupied by the LTE and NR PUCCHs and PRACHs. LTE and NR statically
share the total available PUSCH resources based on a pre-configured percentage.
The configuration of the frequency-domain start position of the NR PRACH involves the
RB index relationship between LTE and NR. As NR occupies some LTE guard band, the
number of available RBs for NR is greater than the number of available RBs for LTE. In
addition, LTE and NR spectrum sharing requires that the center frequencies of LTE and NR
be aligned, and the RB index relationship between LTE and NR is as follows:
In 10 MHz bandwidth scenarios, NR can use 52 RBs, with the RB indexes ranging from
0 to 51; LTE can use 50 RBs, with the RB indexes ranging from 0 to 49. The RB index
deviation between NR and LTE is 1. Specifically, the index of a certain RB on the NR
side equals the index on the LTE side plus one.
In 15 MHz bandwidth scenarios, NR can use 79 RBs, with the RB indexes ranging from
0 to 78; LTE can use 75 RBs, with the RB indexes ranging from 0 to 74. The RB index
deviation between NR and LTE is 2. Specifically, the index of a certain RB on the NR
side equals the index on the LTE side plus two.
In 20 MHz bandwidth scenarios, NR can use 106 RBs, with the RB indexes ranging
from 0 to 105; LTE can use 100 RBs, with the RB indexes ranging from 0 to 99. The RB
index deviation between NR and LTE is 3. Specifically, the index of a certain RB on the
NR side equals the index on the LTE side plus three.
Function Configuration
This function requires that LTE and NR be configured with the same clock source and be
time synchronized. The function switches and related parameters on the two sides must be
configured.
Configure LTE parameters TASM.MODE, TASM.CLKSRC, PEERCLK.PN,
PEERCLK.PNT, PEERCLK.PS, and TASM.CLKSYNCMODE. The NR SUL cell is
already time synchronized with the NR C-band cell. Therefore, in separate-MPT
LTE/NR scenarios, when the clock sources configured for the LTE and NR sides are
inconsistent, the clock source for the LTE side must be changed to the same as that for
the NR side, and time synchronization must be achieved. In co-MPT LTE/NR scenarios,
the LTE and NR sides already share the clock source and are time synchronized, and
reconfiguration is not required. If the requirements on the clock source and time
synchronization are not met, the NR cell fails to be activated.
On the LTE side, set the SpectrumCloud.SpectrumCloudSwitch parameter to
LTE_NR_UPLINK_SPECTRUM_SHR to enable static spectrum sharing. In addition,
perform the following configurations:
Add LTE cells to an LTE spectrum sharing cell group by configuring the
SpectrumCloud.LocalCellId and
SpectrumCloud.LteNrSpectrumShrCellGrpId parameters.
Set the LTE and NR uplink spectrum sharing mode to static by setting the
LteNrSpctShrCellGrp.LteNrUlSpectrumShrMode parameter to
STATIC_SHARING. The uplink spectrum sharing mode on the LTE side must be
identical with that on the NR side.
Configure the percentage of uplink spectrum allocated to NR via the
LteNrSpctShrCellGrp.RateOfUlSpectrumAllocToNr parameter. The uplink
spectrum allocated to NR based on this percentage indicates the LTE available
spectrum excluding the LTE guard band.
The actual percentage of uplink spectrum allocated to NR slightly differs from the
parameter setting, and can be calculated using the following formula: Actual
percentage of uplink spectrum allocated to NR = (Number of RBs occupied by the
NR PUCCH + Number of RBs occupied by the NR PRACH + Number of RBs
occupied by the NR PUSCH)/Total number of shared RBs = (Total number of shared
RBs – Number of RBs occupied by the LTE PUCCH – Number of RBs occupied by
the LTE PRACH – Number of RBs occupied by the LTE PUSCH)/Total number of
shared RBs.
To ensure the provisioning of basic LTE and NR services, both of the following
requirements must be met:
The number of RBs occupied by the LTE PUCCH must be greater than or equal to
4. LTE PRACH always occupies 6 RBs. Therefore, LTE must have at least 10
RBs.
The number of RBs in LTE available bandwidth occupied by the NR PUCCH
must be equal to 6 (in 10 MHz bandwidth scenarios), 4 (in 15 MHz bandwidth
scenarios), or 2 (in 20 MHz bandwidth scenarios). NR PRACH always occupies 6
RBs. That is, a 10 MHz, 15 MHz, and 20 MHz NR cell occupies at least 12 in-
band RBs, 10 in-band RBs, and 8 in-band RBs, respectively.
The NR PUCCH occupies both the LTE guard band and LTE available bandwidth, and other
physical channels occupy only the LTE available bandwidth.
Configure the LTE and NR co-carrier co-CPRI data switch via the
LteNrSpctShrCellGrp.LteNrCoCarrCoCpriDataSw parameter. This parameter
can be set to ON only when LTE and NR use the CPRI MUX topology. When this
parameter is set to ON, the requirements on the CPRI bandwidth are reduced.
On the NR side, select the LTE_NR_UL_SPECTRUM_SHARING_SW option of the
NRDUCellAlgoSwitch.SpectrumCloudSwitch parameter to enable static spectrum sharing.
In addition, perform the following configurations:
Configure the association between the LTE spectrum sharing cell group and the NR
spectrum sharing cell group via the gNBDULteNrSpctShrCg.NrSpctShrCellGrpId and
gNBDULteNrSpctShrCg.LteSpctShrCellGrpId parameters.
Add NR SUL cells to the NR spectrum sharing cell group by setting the
NRDUCellSpctCloud.NrDuCellId and NRDUCellSpctCloud.NrSpctShrCellGrpId
parameters.
Set the uplink spectrum sharing mode to static by setting the
gNBDULteNrSpctShrCg.LteNrUlSpectrumShrMode parameter to
STATIC_SHARING. The uplink spectrum sharing mode on the NR side must be
identical with that on the LTE side.
In addition to the preceding parameter configurations, you also need to set the parameters
in Technical Principles.
3.1.2 Dynamic Spectrum Sharing
Technical Principles
In dynamic spectrum sharing, LTE and NR uplink physical channels share spectrum
resources based on the service priority (negotiated between the eNodeB and gNodeB) and
spectrum sharing priority (specified by the
LteNrSpctShrCellGrp.LteNrUlSpectrumShrPriority parameter), as shown in Figure 3-
3.
Figure 3-3 Dynamic uplink spectrum sharing
10 MHz 4 45
Bandwidth Start RB Index at the Lower End RB Index at the Upper
End End
15 MHz 3 71
20 MHz 2 97
Assume that 12 RBs are configured for the LTE PUCCH in 15 MHz bandwidth
scenarios. Then, the LTE PUCCH occupies RBs with indexes 3 to 8 at the lower end,
and occupies RBs with indexes 66 to 71 at the upper end.
LTE PRACH: The LTE PRACH always occupies 6 RBs. It is recommended that RBs
adjacent to the LTE PUCCH at the lower end be reserved for the LTE PRACH. The
frequency-domain position of RBs can also be parameter configured. For details, see
descriptions of the PRACH frequency-domain position in Random Access Control in
eRAN Feature Documentation. The LTE PRACH frequency-domain position must not
overlap with the frequency-domain positions of the LTE PUCCH, NR PUCCH, and NR
PRACH.
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
LTE PUCCH. The NR PRACH always occupies 6 RBs.
LTE and NR PUSCHs: The total resources available for the LTE and NR PUSCHs equal
the total available spectrum resources minus the resources occupied by the LTE and NR
PUCCHs and PRACHs. The total LTE and NR available PUSCH resources are
dynamically shared between LTE and NR PUSCHs based on the service priority and
spectrum priority.
Function Configuration
This function requires that LTE and NR be configured with the same clock source and be
time synchronized. The function switches and related parameters on the two sides must be
configured.
Configure LTE parameters TASM.MODE, TASM.CLKSRC, PEERCLK.PN,
PEERCLK.PNT, PEERCLK.PS, and TASM.CLKSYNCMODE. The NR SUL cell is
already time synchronized with the NR C-band cell. Therefore, in separate-MPT
LTE/NR scenarios, when the clock sources configured for the LTE and NR sides are
inconsistent, the clock source for the LTE side must be changed to the same as that for
the NR side, and time synchronization must be achieved. In co-MPT LTE/NR scenarios,
the LTE and NR sides already share the clock source and are time synchronized, and
reconfiguration is not required. If the requirements on the clock source and time
synchronization are not met, the NR cell fails to be activated.
On the LTE side, set the SpectrumCloud.SpectrumCloudSwitch parameter to
LTE_NR_UPLINK_SPECTRUM_SHR to enable dynamic spectrum sharing. In
addition, perform the following configurations:
Add LTE cells to a spectrum sharing cell group by configuring the
SpectrumCloud.LocalCellId and
SpectrumCloud.LteNrSpectrumShrCellGrpId parameters.
Set the LTE and NR uplink spectrum sharing mode to dynamic by setting the
LteNrSpctShrCellGrp.LteNrUlSpectrumShrMode parameter to
DYNAMIC_SHARING. The uplink spectrum sharing mode on the LTE side must
be identical with that on the NR side.
Configure the radio access technology (RAT) priority in LTE and NR spectrum
sharing via the LteNrSpctShrCellGrp.LteNrUlSpectrumShrPriority parameter.
This parameter can be set to LTE_PRI, NR_PRI, or LTE_NR_FAIR. For example,
when this parameter is set to LTE_PRI, LTE takes precedence over NR in dynamic
uplink spectrum sharing.
Configure the percentage of uplink spectrum allocated to NR via the
LteNrSpctShrCellGrp.RateOfUlSpectrumAllocToNr parameter. This
configured percentage takes effect in the following scenarios:
After dynamic spectrum sharing is enabled, the shared spectrum is initially
allocated to LTE and NR based on this percentage.
After dynamic spectrum sharing is disabled, the shared spectrum is statically
shared between LTE and NR based on this percentage.
Details about this parameter can be found in "Function Configuration" in 3.1.1 Static
Spectrum Sharing.
Configure the LTE and NR co-carrier co-CPRI data switch via the
LteNrSpctShrCellGrp.LteNrCoCarrCoCpriDataSw parameter. This parameter
can be set to ON only when LTE and NR use the CPRI MUX topology. When this
parameter is set to ON, the requirements on the CPRI bandwidth are reduced.
On the NR side, select the LTE_NR_UL_SPECTRUM_SHARING_SW option of the
NRDUCellAlgoSwitch.SpectrumCloudSwitch parameter to enable dynamic spectrum
sharing. In addition, perform the following configurations:
Configure the association between the LTE spectrum sharing cell group and the NR
spectrum sharing cell group via the gNBDULteNrSpctShrCg.NrSpctShrCellGrpId and
gNBDULteNrSpctShrCg.LteSpctShrCellGrpId parameters.
Add NR SUL cells to the NR spectrum sharing cell group by setting the
NRDUCellSpctCloud.NrDuCellId and NRDUCellSpctCloud.NrSpctShrCellGrpId
parameters.
Set the uplink spectrum sharing mode to dynamic by setting the
gNBDULteNrSpctShrCg.LteNrUlSpectrumShrMode parameter to
DYNAMIC_SHARING. The uplink spectrum sharing mode on the NR side must be
identical with that on the LTE side.
In addition to the preceding parameter configurations, you also need to set the parameters
in Technical Principles.
3.2 Network Analysis
3.2.1 Benefits
This function together with UL and DL Decoupling improves the NR uplink throughput via
the establishment of SUL cells, and helps achieve fast NR deployment. For details about
the benefits provided by UL and DL Decoupling, see UL and DL Decoupling.
3.2.2 Impacts
Network Impacts
This function affects only LTE networks. It has no impact on NR networks. This function
reduces the number of uplink RBs available for the LTE PUSCH, decreasing the uplink
throughput of LTE UEs. The greater the uplink load, the larger this impact.
Uplink throughput of LTE UEs = (L.Thrp.bits.UL –
L.Thrp.bits.UE.UL.SmallPkt)/L.Thrp.Time.UE.UL.RmvSmallPkt. Table 3-4 lists the
related counters.
Table 3-4 Counters used for measuring the uplink throughput of LTE UEs
1526728259 L.Thrp.bits.UL
1526729415 L.Thrp.bits.UE.UL.SmallPkt
1526729416 L.Thrp.Time.UE.UL.RmvSmallPkt
Function Impacts
takes effect.
scheduling.
decreases,
which
increases the
pairing success
rate of uplink
MU-MIMO.
Consequently,
the BLER
increases.
3.3 Requirements
3.3.1 Licenses
LTE MRFD- LTE FDD and NR LT1S0FNUSS00 LTE FDD and NR eNodeB per
FDD 131223 Uplink Spectrum Uplink Spectrum Cell
Sharing (LTE Sharing (LTE
FDD) FDD) (per Cell)
RAT Feature Feature Name Model Description NE Sales
ID Unit
NR MRFD- LTE FDD and NR NR0S0FNUSS00 LTE FDD and NR gNodeB per
131263 Uplink Spectrum Uplink Spectrum Cell
Sharing (NR) Sharing (NR) (per
Cell)
LTE FDD LT1S5000RFSS Spectrum Sharing License for eNodeB per Band
5000 Series RF Module (FDD) per 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.
3.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
indicator Resource
Management
PUCCH PucchSwitch option of the Physical Only static uplink spectrum sharing
resource CellAlgoSwitch.PucchAlgoSwitch Channel requires this function. When static
adjustment parameter Resource uplink spectrum sharing is enabled
Management deselect this option to allow static
configuration of PUCCH resources
Adaptive Activated using the ACT AICIC command on the Adaptive ICIC
Inter-Cell eCoordinator
Interference
Coordination
SRS Resource
neighboring Management
cell
measurement
a: Superior Uplink Coverage is mutually exclusive with only LTE and NR dynamic uplink
spectrum sharing.
Huawei devices (including the eNodeB and gNodeB) must be used on the radio access
network side.
Boards
RF Modules
LTE and NR SUL must share the same RF module. The RRUs listed in Table 3-5 support
this function.
Table 3-5 RRUs supporting this function
a: 5000 series RRUs refer to RRUs named RRU5xxx, for example, RRU5909.
Cells
LTE and NR SUL cells must work on a 10 MHz, 15 MHz, or 20 MHz bandwidth, and have
the same operating frequency band, frequency number, and standard bandwidth. The
antenna TX/RX mode must be 2T2R, 2T4R, or 4T4R. This function does not support sector
split cells.
3.3.4 Networking
In separate-MPT scenarios, this function requires an intra-BBU CPRI MUX, an intra-BBU
dual star, or an inter-BBU dual star topology. In co-MPT scenarios, this function requires
an intra-BBU load sharing, an intra-BBU CPRI MUX, or an inter-BBU load sharing
topology.
Separate-MPT Scenarios
Intra-BBU CPRI MUX topology: LTE and NR share a BBU, and only the LTE
baseband processing unit is connected directly to the RRU through an optical fiber, as
shown in Figure 3-4.
Figure 3-4 Intra-BBU CPRI MUX topology
Intra-BBU dual star topology: LTE and NR share a BBU, and the LTE and NR baseband
processing units are connected to an RRU through their own optical fibers, as shown in
Figure 3-5.
Inter-BBU dual star topology: LTE and NR use different BBUs, and the LTE and NR
baseband processing units are connected to an RRU through their own optical fibers.
The LTE and NR main control boards are connected through CI interconnection cables
for inter-RAT clock lock, as shown in Figure 3-6.
Figure 3-6 Inter-BBU dual star topology
Co-MPT Scenarios
Intra-BBU load sharing topology: LTE and NR share a BBU, and the LTE and NR
baseband processing units are connected to an RRU through their own optical fibers, as
shown in Figure 3-7.
Figure 3-7 Intra-BBU load sharing topology
Intra-BBU CPRI MUX topology: LTE and NR share a BBU, and only the LTE
baseband processing unit is connected directly to the RRU through an optical fiber, as
shown in Figure 3-8.
Figure 3-8 Intra-BBU CPRI MUX topology
Inter-BBU load sharing topology: LTE and NR are deployed in different BBUs, and the
LTE and NR baseband processing units are connected to an RRU through their own
optical fibers. The LTE and NR main control boards are connected through a CI
interconnection cable for inter-RAT clock lock. Figure 3-9 shows the inter-BBU load
sharing topology.
Figure 3-9 Inter-BBU load sharing topology
3.3.5 Others
MRFD-131223 LTE FDD and NR Uplink Spectrum Sharing (LTE FDD) and MRFD-
131263 LTE FDD and NR Uplink Spectrum Sharing (NR) must be simultaneously used.
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
SUL cells. The CPRI compression type of LTE cells is configured via the
Cell.CPRICompression parameter, and the CPRI compression type of NR SUL cells
is configured via the NRDUCellTrp.CpriCompression parameter. Table 3-6 describes the
configuration requirements.
Table 3-6 Configuration requirements on the CPRI compression types of the LTE and NR SUL
cells
When this function is used together with FDD+TDD Uplink Carrier Aggregation or
FDD+TDD Downlink Carrier Aggregation:
If LTE TDD and NR TDD (SUL) are deployed in the same frequency band, and if
LTE FDD and NR Uplink Spectrum Sharing is enabled together with UL and DL
Decoupling in the LTE FDD frequency band, LTE FDD and NR Uplink Spectrum
Sharing is mutually exclusive with FDD+TDD CA.
If LTE TDD and NR TDD (SUL) are deployed in different frequency bands, and if
LTE FDD and NR Uplink Spectrum Sharing is enabled together with UL and DL
Decoupling in the LTE FDD frequency band, LTE FDD and NR Uplink Spectrum
Sharing can be used together with FDD+TDD CA as long as the following conditions
are met:
The effective value of LTE TDD cell frame offset (specified by the
CellFrameOffset.FrameOffset or ENodeBFrameOffset.TddFrameOffset
parameter. If these parameters are both configured, the value of the
CellFrameOffset.FrameOffset parameter prevails.) is identical with the
effective value of NR TDD cell frame offset (specified by the
gNodeBParam.FrameOffset parameter).
The effective value of LTE TDD cell frame offset is greater than that of the LTE
FDD cell frame offset (specified by the CellFrameOffset.FrameOffset or
ENodeBFrameOffset.FddFrameOffset parameter). The difference between
these two values is identical with the effective value of the TA offset of the NR
TDD cell (specified by the NRDUCell.TaOffset parameter). Table 3-7 describes the
configuration requirements.
Table 3-7 Configuration requirements on the difference between the frame offset
effective values of LTE TDD and LTE FDD cells and on the TA offset effective value of
NR TDD cells
a: Difference between the frame offset effective values of LTE TDD and LTE FDD cells =
Difference Between Effective Value of NR Other Restriction
the Frame Offset TDD Cell TA Offset
Effective Values of
LTE TDD and LTE
FDD Cellsa
Frame offset effective value of LTE TDD cells – Frame offset effective value of LTE FDD
cells
The configurations of LTE FDD, LTE TDD, and NR TDD cell frame offsets and the
NR TDD cell TA offset must be confirmed with Huawei engineers.
3.4 Operation and Maintenance
This function can be used in LTE cells with a light uplink load (uplink PRB usage < 30%),
since it decreases the amount of uplink spectrum available for LTE. The uplink PRB usage
of an LTE cell can be obtained by dividing L.ChMeas.PRB.UL.Used.Avg by
L.ChMeas.PRB.UL.Avail. You are advised to use the average uplink PRB usage in busy
hours.
3.4.2 Data Configuration
If the activation of this function is to be verified through signaling message tracing, you
need to start signaling tracing on the U2020 before activating this function in LTE and NR
SUL cells. Otherwise, activation-related messages cannot be observed after this function is
activated.
3.4.2.1 Data Preparation
describes the parameters used for function activation on the LTE side. Table 3-9
Table 3-8
describes the parameters used for function activation on the NR side. This section does not
describe parameters related to cell establishment.
Since the configuration of some of these parameters can result in automatic cell restarts, 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 restarting during parameter configuration.
Table 3-8 LTE parameters used for activation
a: If both the frame offset (specified by the CellFrameOffset.FrameOffset parameter) and the FDD frame off
(specified by the ENodeBFrameOffset.FddFrameOffset parameter) are configured, the frame offset (specifi
the CellFrameOffset.FrameOffset parameter) takes effect for the LTE cell.
b: The frame offset of the LTE FDD cell must meet the following configuration requirements: The LTE FDD, L
and LTE NB-IoT cells served by the same RRU or the same baseband processing unit must be configured w
same frame offset. LTE FDD cells involved in CA must be configured with the same frame offset.
c: In separate-MPT LTE/NR scenarios, if time synchronization needs to be reconfigured on the LTE side as p
network plan, these six parameters need to be configured.
Group ID LteNrSpctShrCellGrp.LteNrSpectrumSh
parameter.
The LTE PUCCH and NR PRACH must be configured together. Table 3-10 and Table 3-11
describe the configuration suggestions for related parameters.
Table 3-10 Configuration suggestions for the LTE PUCCH and NR PRACH (L.Traffic.User.Avg ≤
300)
LTE CellCqiAdaptiveCfg.CqiPeriodAdaptive Use the default value. Use the default value.
PUCCH
LTE CellCqiAdaptiveCfg.UserCqiPeriod Use the default value. Use the default value.
PUCCH
Physical Related Parameter Configuration Suggestion Configuration Suggestion
Channel (CA Not Enabled) (CA Enabled)
LTE CellQciPara.SriPeriod Use the default value. Use the default value.
PUCCH
LTE PUCCHCfg.SriPeriodAdaptive Use the default value. Use the default value.
PUCCH
PUCCHCfg.DeltaShift PUCCHCfg.DeltaShift
parameter is set to parameter is set to
DS2_DELTA_SHIFT(d DS2_DELTA_SHIFT(d
s2): s2):
Set this parameter Set this parameter
to 38 in 10 MHz to 38 in 10 MHz
bandwidth bandwidth
scenarios. scenarios.
Set this parameter Set this parameter
to 65 in 15 MHz to 64 in 15 MHz
bandwidth bandwidth
scenarios. scenarios.
Set this parameter Set this parameter
to 91 in 20 MHz to 90 in 20 MHz
bandwidth bandwidth
scenarios. scenarios.
Table 3-11 Configuration suggestions for the LTE PUCCH and NR PRACH (L.Traffic.User.Avg >
300)
LTE CellCqiAdaptiveCfg.CqiPeriodAdaptive Use the default value. Use the default value.
PUCCH
LTE CellCqiAdaptiveCfg.UserCqiPeriod Use the default value. Use the default value.
PUCCH
LTE CellQciPara.SriPeriod Use the default value. Use the default value.
PUCCH
DS1_DELTA_SHIFT(d DS1_DELTA_SHIFT(d
s1), set this parameter s1), set this parameter
to 110. to 120.
When the When the
PUCCHCfg.DeltaShift PUCCHCfg.DeltaShift
parameter is set to parameter is set to
DS2_DELTA_SHIFT(d DS2_DELTA_SHIFT(d
s2), set this parameter s2), set this parameter
to 56. to 66.
LTE PUCCHCfg.SriPeriodAdaptive Use the default value. Use the default value.
PUCCH
Table 3-12describes the parameters used for function activation on the LTE side. Table 3-13
describes the parameters used for function activation on the NR side. This section does not
describe parameters related to cell establishment.
Since the configuration of some of these parameters can result in automatic cell restarts, 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 restarting during parameter configuration.
Table 3-12 LTE parameters used for activation
Sharing Priority
a: If both the frame offset (specified by the CellFrameOffset.FrameOffset parameter) and the FDD frame off
(specified by the ENodeBFrameOffset.FddFrameOffset parameter) are configured, the frame offset (specifi
the CellFrameOffset.FrameOffset parameter) takes effect for the LTE cell.
b: The frame offset of the LTE FDD cell must meet the following configuration requirements: The LTE FDD, L
and LTE NB-IoT cells served by the same RRU or the same baseband processing unit must be configured w
same frame offset. LTE FDD cells involved in CA must be configured with the same frame offset.
c: In separate-MPT LTE/NR scenarios, if time synchronization needs to be reconfigured on the LTE side as p
network plan, these six parameters need to be configured.
Check whether this function has taken effect by using MML commands, observing
counters, or tracing signaling messages.
The LTE and NR static spectrum sharing function 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 static sharing.
The value of the Spectrum Sharing Status parameter in the output of the gNodeB
MML command DSP GNBDULTENRSPCTSHRCG is static sharing.
The LTE and NR dynamic spectrum sharing function 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.
Observing Counters
The LTE and NR static or dynamic spectrum sharing function takes effect when the
following conditions for eNodeB and gNodeB are all met:
Observe the following counter on the eNodeB side:
L.ChMeas.PRB.UL.Avail (counter ID: 1526728434): This counter value is less than
the number of RBs corresponding to the cell bandwidth specified by the
Cell.UlBandWidth parameter.
Observe the following counter on the gNodeB side:
(counter ID: 1911816582): This counter value is less than the number
N.PRB.UL.Avail.Avg
of RBs corresponding to the cell bandwidth specified by the Cell.UlBandWidth
parameter.
Before activating this function in LTE and NR SUL cells, start signaling tracing on the
U2020. Otherwise, activation-related messages cannot be observed after this function is
activated.
The LTE and NR static or dynamic spectrum sharing function takes effect when the
following conditions for eNodeB and gNodeB are all met:
Perform the following steps to start eNodeB message tracing on the U2020:
1. Log in to the U2020. 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.
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.
3. After this function is activated in LTE and NR SUL 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 > spectrum-sharing-status IE in the
LNR_INTER_RAT_SPECTRUM_CHANGE_INDICATION message. The value
is expected to be ss-static-sharing or ss-dynamic-sharing.
Perform the following steps to start gNodeB message tracing on the U2020:
1. Log in to the U2020. 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.
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.
3. After this function is activated in LTE and NR SUL 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 > spectrum-sharing-status IE in the
LNR_INTER_RAT_SPECTRUM_CHANGE_INDICATION message. The value
is ss-static-sharing or ss-dynamic-sharing.
3.4.4 Network Monitoring
The LTE uplink throughput decrease can be monitored using the counters listed in 3.2.2
Impacts. The NR SUL cell uplink throughput increase is described in the "Network
Monitoring" section in UL and DL Decoupling.
4 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.
5 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.
6 Glossary
7 Reference Documents
UL and DL Decoupling