LTE FDD and NR Spectrum Sharing (SRAN18.1 - Draft A)

SingleRAN
LTE FDD and NR Spectrum Sharing

Feature Parameter Description
Issue Draft A
Date 2021-12-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2022. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
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.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://www.huawei.com
Email: support@huawei.com
Issue Draft A Copyright © Huawei Technologies Co., Ltd. i

(2021-12-30)
SingleRAN
LTE FDD and NR Spectrum Sharing Feature
Parameter Description Contents
Contents
1 Change History.........................................................................................................................1
1.1 SRAN18.1 Draft A (2021-12-30)........................................................................................................................................ 1
2 About This Document.............................................................................................................8

2.1 General Statements................................................................................................................................................................ 8
2.2 Applicable RAT......................................................................................................................................................................... 9
2.3 Features in This Document.................................................................................................................................................. 9
2.4 Differences.............................................................................................................................................................................. 10
3 LTE FDD and NR Flash Dynamic Spectrum Sharing...................................................... 12

3.1 Principles.................................................................................................................................................................................. 12
3.1.1 Basic Functions of Flash Dynamic Spectrum Sharing...........................................................................................13
3.1.1.1 Principles........................................................................................................................................................................... 13
3.1.1.2 Key Technologies............................................................................................................................................................ 15
3.1.2 Enhanced Functions of Flash Dynamic Spectrum Sharing................................................................................. 21
3.1.2.1 Flexible Spectrum Priority Mode.............................................................................................................................. 21
3.1.2.2 Flexible Power Allocation Mode............................................................................................................................... 23
3.1.2.3 Co-carrier Co-CPRI Data.............................................................................................................................................. 24
3.1.2.4 LTE Key Event Assurance............................................................................................................................................. 24
3.1.3 Application Scenarios of Simultaneous Use of Flash Dynamic Spectrum Sharing and Other Functions
............................................................................................................................................................................................................ 25
3.1.4 HDSS based on Asymmetric Beam..............................................................................................................................28
3.1.4.1 Principles........................................................................................................................................................................... 29
3.1.4.2 Key Technologies............................................................................................................................................................ 30
3.1.4.3 Enhanced Functions...................................................................................................................................................... 32
3.1.4.4 Simultaneous Use of HDSS based on Asymmetric Beam and Other Functions...................................... 34
3.2 Network Analysis.................................................................................................................................................................. 35
3.2.1 Benefits................................................................................................................................................................................. 35
3.2.2 Impacts.................................................................................................................................................................................. 39
3.3 Requirements......................................................................................................................................................................... 66
3.3.1 Licenses................................................................................................................................................................................. 66
3.3.2 Software................................................................................................................................................................................68
3.3.3 Hardware.............................................................................................................................................................................. 79
3.3.4 Networking.......................................................................................................................................................................... 87
3.3.5 Others.................................................................................................................................................................................... 94
Issue Draft A Copyright © Huawei Technologies Co., Ltd. ii

(2021-12-30)
SingleRAN
3.4 Operation and Maintenance............................................................................................................................................. 95

3.4.1 Data Configuration........................................................................................................................................................... 95
3.4.1.1 Data Preparation............................................................................................................................................................ 95
3.4.1.2 Using MML Commands............................................................................................................................................. 111
3.4.1.3 Using the MAE-Deployment.................................................................................................................................... 116
3.4.2 Activation Verification................................................................................................................................................... 116
3.4.3 Network Monitoring...................................................................................................................................................... 118
4 Hybrid DSS Based on Asymmetric Bandwidth............................................................. 119

4.1 Principles............................................................................................................................................................................... 119
4.1.1 Basic Functions of Hybrid DSS Based on Asymmetric Bandwidth................................................................. 119
4.1.1.1 Principles......................................................................................................................................................................... 119
4.1.1.2 Key Technologies......................................................................................................................................................... 122
4.1.2 Enhanced Functions of Hybrid DSS Based on Asymmetric Bandwidth........................................................127
4.1.2.1 Flexible Spectrum Priority Modes.......................................................................................................................... 127
4.1.2.2 Flexible Power Allocation Mode............................................................................................................................. 129
4.1.2.3 Co-carrier Co-CPRI Data............................................................................................................................................130
4.1.3 Application Scenarios of Simultaneous Use of Hybrid DSS Based on Asymmetric Bandwidth and
Other Functions.......................................................................................................................................................................... 131
4.1.4 HDSS based on Asymmetric Beam........................................................................................................................... 134
4.1.4.1 Principles......................................................................................................................................................................... 134
4.1.4.2 Key Technologies......................................................................................................................................................... 136
4.1.4.3 Enhanced Functions.................................................................................................................................................... 138
4.1.4.4 Simultaneous Use of HDSS based on Asymmetric Beam and Other Functions....................................140
4.2 Network Analysis................................................................................................................................................................ 141
4.2.1 Benefits............................................................................................................................................................................... 141
4.2.2 Impacts............................................................................................................................................................................... 144
4.3 Requirements....................................................................................................................................................................... 164
4.3.1 Licenses............................................................................................................................................................................... 164
4.3.2 Software............................................................................................................................................................................. 165
4.3.3 Hardware........................................................................................................................................................................... 175
4.3.4 Networking....................................................................................................................................................................... 183
4.3.5 Others................................................................................................................................................................................. 186
4.4 Operation and Maintenance.......................................................................................................................................... 187
4.4.1 Data Configuration......................................................................................................................................................... 187
4.4.1.1 Data Preparation..........................................................................................................................................................187
5 DSS-based Flexible PDSCH Scheduling.......................................................................... 213

5.1 Principles............................................................................................................................................................................... 213
5.2 Network Analysis................................................................................................................................................................ 213
Issue Draft A Copyright © Huawei Technologies Co., Ltd. iii

(2021-12-30)
SingleRAN
5.2.1 Benefits............................................................................................................................................................................... 213

5.2.2 Impacts............................................................................................................................................................................... 213
5.3 Requirements....................................................................................................................................................................... 214
5.3.1 Licenses............................................................................................................................................................................... 214
5.3.2 Software............................................................................................................................................................................. 214
5.3.3 Hardware........................................................................................................................................................................... 215
5.3.4 Others................................................................................................................................................................................. 215
5.4 Operation and Maintenance.......................................................................................................................................... 215
5.4.1 Data Configuration......................................................................................................................................................... 215
5.4.1.1 Data Preparation..........................................................................................................................................................215
6 Parameters............................................................................................................................217
7 Counters................................................................................................................................ 219
8 Glossary................................................................................................................................. 220
9 Reference Documents........................................................................................................ 221
Issue Draft A Copyright © Huawei Technologies Co., Ltd. iv

(2021-12-30)
SingleRAN
Parameter Description 1 Change History
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 SRAN18.1 Draft A (2021-12-30)

This issue introduces the following changes to SRAN17.1 09 (2021-11-27).
Technical Changes
Change Description Parameter Base Station
Change Model
Added support for configurable TA Added the ● 3900 and 5900

offsets on the LTE side. For details, see: CellFrameOffset. series base
● 3.1.1.1 Principles, 3.2.2 Impacts, TaOffset stations
3.4.1.1 Data Preparation, and parameter. ● DBS3900
3.4.1.2 Using MML Commands LampSite and
● 4.1.1.1 Principles, 4.2.2 Impacts, DBS5900
4.4.1.1 Data Preparation, and LampSite
4.4.1.2 Using MML Commands
Added support for LTE and NR SRS Modified ● 3900 and 5900
resource allocation optimization. For parameters: series base
details, see: Added the stations
● 3.1.1.2 Key Technologies, 3.4.1.1 LTE_NR_SRS_ALL ● DBS3900
Data Preparation, and 3.4.1.2 OC_OPT_SW LampSite and
Using MML Commands option to the DBS5900
● 4.1.1.2 Key Technologies, 4.4.1.1 LteNrSpctShrCell LampSite
Data Preparation, and 4.4.1.2 Grp.LteNrSpctShr
Using MML Commands Switch parameter.
Issue Draft A Copyright © Huawei Technologies Co., Ltd. 1

(2021-12-30)
SingleRAN

Change Model
Added support for simultaneous use Modified ● 3900 and 5900

with WBB. For details, see: parameters: series base
● 3.1.1.2 Key Technologies, 3.4.1.1 Added the stations
Data Preparation, and 3.4.1.2 WBB_MBB_CONT ● DBS3900
Using MML Commands ROL_OPT_SW LampSite and
● 4.1.1.2 Key Technologies, 4.4.1.1 option to the DBS5900
Data Preparation, and 4.4.1.2 SpectrumCloud.S LampSite
Using MML Commands pectrumCloudEn
hSwitch
parameter.
Added support for inter-RAT Modified ● 3900 and 5900

preferential guarantee for GBR parameters: series base
services. For details, see: Added the stations
● 3.1.2.1 Flexible Spectrum Priority GBR_PRI_ALLOC_ ● DBS3900
Mode, 3.4.1.1 Data Preparation, SW option to the LampSite and
and 3.4.1.2 Using MML LteNrSpctShrCell DBS5900
Commands Grp.LteNrSpctShr LampSite
● 4.1.2.1 Flexible Spectrum Priority Switch parameter.
Modes, 4.4.1.1 Data Preparation,
and 4.4.1.2 Using MML
Commands
Added the required CPRI compression None ● 3900 and 5900

ratio when the co-carrier co-CPRI data series base
function is used together with CPRI stations
compression. For details, see 3.1.3 ● DBS3900
Application Scenarios of LampSite and
Simultaneous Use of Flash Dynamic DBS5900
Spectrum Sharing and Other LampSite
Functions and 4.1.3 Application
Scenarios of Simultaneous Use of
Hybrid DSS Based on Asymmetric
Bandwidth and Other Functions.
Added support for the use of LTE FDD None ● 3900 and 5900
and NR Flash Dynamic Spectrum series base
Sharing in 17.5 MHz compact stations
bandwidth scenarios. For details, see ● DBS3900
3.2.2 Impacts and 3.3.3 Hardware. LampSite and
DBS5900
LampSite
Deleted the impact that pRRU deep None DBS3900

dormancy in intelligent mode does not LampSite and
take effect when it is enabled together DBS5900
with LTE FDD and NR Flash Dynamic LampSite
Spectrum Sharing. For details, see
3.2.2 Impacts.

(2021-12-30)
SingleRAN

Change Model
Added the impact relationship None ● 3900 and 5900

between LTE FDD and NR Flash series base
Dynamic Spectrum Sharing and RB stations
allocation for downlink experience ● DBS3900
optimization. For details, see 3.2.2 LampSite and
Impacts. DBS5900
LampSite
Removed the mutually exclusive None ● 3900 and 5900

relationship between LTE FDD and NR series base
Flash Dynamic Spectrum Sharing and stations
eMTC introduction, and added the ● DBS3900
impact relationship between them. For LampSite and
details, see 3.2.2 Impacts and 3.3.2 DBS5900
Software. LampSite
Removed mutually exclusive None ● 3900 and 5900

relationships between LTE FDD and NR series base
Super uplink with SUL and NR FDD co- ● DBS3900
deployment, and between Hybrid DSS LampSite and
Based on Asymmetric Bandwidth and DBS5900
Super uplink with SUL and NR FDD co- LampSite
deployment, and added impact
relationships. For details, see 3.2.2
Impacts, 3.3.2 Software, 4.2.2
Impacts, and 4.3.2 Software.
Added impact relationships between None ● 3900 and 5900

LTE FDD and NR Flash Dynamic series base
Spectrum Sharing and NR inter-carrier stations
dynamic power sharing, and between ● DBS3900
Hybrid DSS Based on Asymmetric LampSite and
Bandwidth and NR inter-carrier DBS5900
dynamic power sharing. For details, LampSite
see 3.3.2 Software and 4.3.2
Software.
Added impact relationships between None ● 3900 and 5900

LTE FDD and NR Flash Dynamic series base
Spectrum Sharing and LTE FDD and stations
NR Flash Dynamic Power Sharing, and ● DBS3900
between Hybrid DSS Based on LampSite and
Asymmetric Bandwidth and LTE FDD DBS5900
and NR Flash Dynamic Power Sharing. LampSite
For details, see 3.3.2 Software and
4.3.2 Software.

(2021-12-30)
SingleRAN

Change Model
Removed mutually exclusive None ● 3900 and 5900

low power consumption mode, and ● DBS3900
between Hybrid DSS Based on LampSite and
Asymmetric Bandwidth and low power DBS5900
consumption mode. For details, see LampSite
3.3.2 Software and 4.3.2 Software.
Added the mutually exclusive None ● 3900 and 5900

relationship between LTE FDD and NR series base
TM4 and TM6 Adaptation. For details, ● DBS3900
see 3.3.2 Software. LampSite and
DBS5900
LampSite
Removed the mutually exclusive None ● 3900 and 5900

the following functions: enhanced ● DBS3900
symbol power saving, RF channel LampSite and
intelligent shutdown, Dynamic Massive DBS5900
Beam, and Full-buffer UE-specific CSI- LampSite
RS for CM. For details, see 3.3.2
Software.
Added mutually exclusive relationships None ● 3900 and 5900

between LTE FDD and NR Flash series base
Dynamic Spectrum Sharing and Hybrid stations
DSS Based on Asymmetric Bandwidth ● DBS3900
and the following functions: Rate- LampSite and
matching-pattern-configuration-free DBS5900
PDCCH rate matching, and intelligent LampSite
PIM interference avoidance. For
details, see 3.3.2 Software and 4.3.2
Software.
Removed the mutually exclusive None 3900 and 5900

relationship between Hybrid DSS series base
Based on Asymmetric Bandwidth and stations
enhanced symbol power saving. For
details, see 4.3.2 Software.

(2021-12-30)
SingleRAN

Change Model
Added support for PSD adaptation for Modified ● 3900 and 5900
NR cells. For details, see: parameter: Added series base
● 3.1.2.2 Flexible Power Allocation the stations
Mode, 3.3.2 Software, 3.4.1.1 Data PWR_SPCT_DENS ● DBS3900
Preparation, and 3.4.1.2 Using ITY_ADAPT_SW LampSite and
MML Commands option to the DBS5900
NRDUCellAlgoSw LampSite
● 4.1.2.2 Flexible Power Allocation itch.SpectrumClo
Mode, 4.3.2 Software, 4.4.1.1 Data udEnhSwitch
Preparation, and 4.4.1.2 Using parameter.
MML Commands
Added support for the 32T32R TX/RX None 3900 and 5900
mode. For details, see: series base
● 3.1.2.3 Co-carrier Co-CPRI Data, stations
3.2.1 Benefits, 3.3.2 Software,
3.3.3 Hardware, 3.4.1.1 Data
Preparation, and 3.4.1.2 Using
MML Commands
● 4.1.2.3 Co-carrier Co-CPRI Data,
4.2.1 Benefits, 4.3.3 Hardware,
4.4.1.1 Data Preparation, and
Added support for LTE FDD and NR None 3900 and 5900
Flash Dynamic Spectrum Sharing and series base
Hybrid DSS Based on Asymmetric stations
Bandwidth in the intra-board cold
backup ring topology. For details, see
3.3.4 Networking and 4.3.4
Networking.
Added common bandwidth scenarios None ● 3900 and 5900

where Hybrid DSS Based on series base
Asymmetric Bandwidth is supported. stations
For details, see 4.1.1.1 Principles, ● DBS3900
4.2.1 Benefits, 4.2.2 Impacts, and LampSite and
4.3.3 Hardware. DBS5900
LampSite

(2021-12-30)
SingleRAN

Change Model
Added support for the 25 MHz NR cell Added the 3900 and 5900
bandwidth. For details, see 4 Hybrid NRDUCellCoreset series base
DSS Based on Asymmetric .CommonCtrlRes stations
Bandwidth. StartSymbol
parameter.
Modified
parameter: Added
the
UE_PDCCH_FULL_
BANDWIDTH_CF
G_SW option to
the
NRDUCellPdcch.P
dcchAlgoExtSwit
ch parameter.
Modified the PDCCH rate matching UE Modified ● 3900 and 5900
compatibility rectification function. For parameter: Added series base
details, see 4.1.1.2 Key Technologies, the stations
4.4.1.1 Data Preparation, and 4.4.1.2 PDCCH_RATEMA ● DBS3900
Using MML Commands. TCH_COMPATIBL LampSite and
E_SW option to DBS5900
the LampSite
NRDUCellPdsch.R
ateMatchSwitch
parameter to
replace the
NRDUCellRsvdEx
t02.RsvdParam37
parameter.
Added support for simultaneous use of None 3900 and 5900

Hybrid DSS Based on Asymmetric series base
Bandwidth with NB-IoT deployed in stations
LTE guard band mode. For details, see
4.1.3 Application Scenarios of
Simultaneous Use of Hybrid DSS
Based on Asymmetric Bandwidth
and Other Functions, 4.2.2 Impacts,
4.4.1.1 Data Preparation, and 4.4.1.2
Using MML Commands.
Added support for the 700 MHz None 3900 and 5900
frequency band. For details, see 4.3.3 series base
Hardware. stations

(2021-12-30)
SingleRAN

Change Model
Added support for HDSS based on None 3900 and 5900

Asymmetric Beam. For details, see 3 series base
LTE FDD and NR Flash Dynamic stations
Spectrum Sharing and 4 Hybrid DSS
Based on Asymmetric Bandwidth.
Simplified parameter configurations Modified ● 3900 and 5900

for LTE FDD and NR Flash Dynamic parameter: series base
Spectrum Sharing and Hybrid DSS Deleted the stations
Based on Asymmetric Bandwidth. For LTE_SS_PBCH_RM ● DBS3900
details, see descriptions throughout _SW and LampSite and
the document. ZP_TRS_AVOIDA DBS5900
NCE_MODE_SW LampSite
options from the
NRDUCellAlgoSw
itch.SpectrumClo
udEnhSwitch
parameter.
Added support for DSS-based Flexible Added the ● 3900 and 5900
PDSCH Scheduling. For details, see 5 NRDUCellDlSchR series base
DSS-based Flexible PDSCH es.SpctShrPdschS stations
Scheduling. tartSymbol ● DBS3900
parameter. LampSite and
DBS5900
LampSite
Editorial Changes
● Changed the name of mutually exclusive function from "Intra-base-station
joint transmission for DL CoMP" to "Intra-base-station DL CoMP". For details,
see 3.3.2 Software and 4.3.2 Software.
● Modified the configuration suggestions on the percentage of spectrum
resources to be preferentially allocated to LTE for MBB services. For details,
see 3.4.1.1 Data Preparation and 4.4.1.1 Data Preparation.
● Revised descriptions in this document.

(2021-12-30)
SingleRAN
Parameter Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
This document is intended to acquaint readers with:
● The technical principles of features and their related parameters
● The scenarios where these features are used, the benefits they provide, and
the impact they have on networks and functions
● Requirements of the operating environment that must be met before feature
activation
● Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance
NOTE
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 optimal gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this
document apply only to the corresponding software release. For future software
releases, refer to the corresponding updated product documentation.
Trial Features
Trial features are features that are not yet ready for full commercial release for
certain reasons. For example, the industry chain (terminals/CN) may not be
sufficiently compatible. However, these features can still be used for testing
purposes or commercial network trials. Anyone who desires to use the trial
features shall contact Huawei and enter into a memorandum of understanding
(MoU) with Huawei prior to an official application of such trial features. Trial
features are not for sale in the current version but customers may try them for
free.

(2021-12-30)
SingleRAN
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.
2.2 Applicable RAT

This document applies to LTE FDD and NR.
2.3 Features in This Document

This document describes the following features.
RAT Feature ID Feature Name Chapter/Section
LTE FDD MRFD-16022 LTE FDD and NR Flash 3 LTE FDD and NR
2 Dynamic Spectrum Flash Dynamic
Sharing (LTE FDD) Spectrum Sharing
NR FDD MRFD-16026 LTE FDD and NR Flash

2 Dynamic Spectrum
Sharing (NR)
LTE FDD MRFD-17122 Hybrid DSS Based on 4 Hybrid DSS Based

1 Asymmetric on Asymmetric
Bandwidth(LTE FDD) Bandwidth
NR FDD MRFD-17126 Hybrid DSS Based on

1 Asymmetric
Bandwidth(NR)
NR FDD FOFD-051250 DSS-based Flexible PDSCH 5 DSS-based Flexible

Scheduling (NR FDD) PDSCH Scheduling

(2021-12-30)
SingleRAN
2.4 Differences
Table 2-1 Differences between NR FDD and NR TDD
Function Name Difference Chapter/Section
LTE FDD and NR Flash Supported only in NR 3 LTE FDD and NR Flash
Dynamic Spectrum FDD Dynamic Spectrum
Sharing Sharing
Hybrid DSS Based on Supported only in NR 4 Hybrid DSS Based on

Asymmetric Bandwidth FDD Asymmetric Bandwidth
DSS-based Flexible Supported only in NR 5 DSS-based Flexible

PDSCH Scheduling FDD PDSCH Scheduling
Table 2-2 Differences between NSA and SA

LTE FDD and NR Flash ● Whether the NR 3 LTE FDD and NR Flash
Dynamic Spectrum PUCCH includes the Dynamic Spectrum
Sharing common PUCCH Sharing
differs between NSA
networking and SA
networking.
● The configuration
suggestions for the
SSB frequency domain
position and four
frame allocation
parameters differ
between NSA
networking and SA
networking.
● This function provides
different gains in NSA
networking and SA
networking.
● The neighboring NR
frequency cannot be
configured as a
dynamic spectrum
sharing frequency in
NSA networking.

(2021-12-30)
SingleRAN
Hybrid DSS Based on ● Whether the NR 4 Hybrid DSS Based on

Asymmetric Bandwidth PUCCH includes the Asymmetric Bandwidth
common PUCCH
differs between NSA
networking and SA
networking.
● This function provides
different gains in NSA
networking and SA
networking.
DSS-based Flexible None 5 DSS-based Flexible

PDSCH Scheduling PDSCH Scheduling
Table 2-3 Differences between high frequency bands and low frequency bands of
NR
LTE FDD and NR Flash Supported only in low 3 LTE FDD and NR Flash
Dynamic Spectrum frequency bands Dynamic Spectrum
Sharing Sharing
Hybrid DSS Based on Supported only in low 4 Hybrid DSS Based on

Asymmetric Bandwidth frequency bands Asymmetric Bandwidth
DSS-based Flexible Supported only in low 5 DSS-based Flexible

PDSCH Scheduling frequency bands PDSCH Scheduling
This document refers to frequency bands belonging to FR1 (410–7125 MHz) as

low frequency bands, and those belonging to FR2 (24250–52600 MHz) as high
frequency bands. For details about FR1 and FR2, see section 5.1 "General" in 3GPP
TS 38.104 V15.5.0.

(2021-12-30)
SingleRAN
Parameter Description 3 LTE FDD and NR Flash Dynamic Spectrum Sharing
3 LTE FDD and NR Flash Dynamic

Spectrum Sharing
3.1 Principles
Some operators lack dedicated NR FDD spectrum resources in the early stages of
5G deployment, while others possess the dedicated NR FDD spectrum resources,
but encounter low spectrum usage due to the low penetration rate of 5G
terminals in the early stages. LTE FDD and NR Flash Dynamic Spectrum Sharing
enables the sharing of uplink and downlink spectrum resources between LTE FDD
and NR FDD. For those operators lacking dedicated NR FDD spectrum resources,
this feature can be used to allow LTE FDD to share its existing spectrum with NR
FDD, enabling fast 5G deployment. For operators who possess sufficient dedicated
NR FDD spectrum resources, this feature enables NR FDD to share spectrum with
LTE FDD, improving spectrum utilization. For ease of description, LTE and NR are
used to refer to LTE FDD and NR FDD, respectively.
This feature supports NSA, SA, and NSA and SA hybrid networking. Unless
otherwise specified, the descriptions apply to all networking scenarios. This feature
is applicable to 3900 and 5900 series base stations and DBS3900 LampSite and
DBS5900 LampSite. Unless otherwise specified, the descriptions hereafter apply to
both types of base stations.
This feature is a trial feature when applied to the DBS3900 LampSite and DBS5900
LampSite. 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 scenarios shall contact Huawei and enter into a memorandum of
understanding (MoU) with Huawei prior to an official application of such trial
scenarios. 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

(2021-12-30)
SingleRAN
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.
The detailed principles and key technologies of LTE FDD and NR Flash Dynamic
Spectrum Sharing are described in 3.1.1 Basic Functions of Flash Dynamic
Spectrum Sharing. The enhanced functions are described in 3.1.2 Enhanced
Functions of Flash Dynamic Spectrum Sharing. Dynamic spectrum sharing can
also be used together with other functions, and the simultaneous use of these
functions is elaborated in 3.1.3 Application Scenarios of Simultaneous Use of
Flash Dynamic Spectrum Sharing and Other Functions.
3.1.1 Basic Functions of Flash Dynamic Spectrum Sharing
3.1.1.1 Principles
LTE FDD and NR Flash Dynamic Spectrum Sharing enables LTE and NR cells to
dynamically share time-frequency resources on a shared spectrum segment based
on their traffic volumes. The LTE and NR cells share the entire bandwidth and
must be configured with the same bandwidth. Figure 3-1 shows LTE FDD and NR
Flash Dynamic Spectrum Sharing.
Figure 3-1 LTE FDD and NR Flash Dynamic Spectrum Sharing
This function is enabled by turning on function switches and configuring spectrum

sharing cell groups. In addition, the LTE and NR cells participating in spectrum
sharing must have aligned radio frames and subframes.

(2021-12-30)
SingleRAN
● Turning on function switches

– LTE: Set the SpectrumCloud.SpectrumCloudSwitch parameter to
LTE_NR_SPECTRUM_SHR.
– NR: Select the LTE_NR_FDD_SPCT_SHR_SW option of the
NRDUCellAlgoSwitch.SpectrumCloudSwitch parameter.
● 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 through 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 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
CellFrameOffset.FrameOffset parameter is used. Set the NR parameter
gNodeBParam.FrameOffset or gNBFreqBandConfig.FrameOffset,
which specifies the frame offset on the NR side. If both parameters are
configured, the gNBFreqBandConfig.FrameOffset parameter is used.
– Set the LTE parameter CellFrameOffset.TaOffset and NR parameter
NRDUCell.TaOffset.
After this function is enabled, LTE and NR cells in the associated spectrum sharing
cell groups can share time-frequency resources on a shared spectrum segment.
Figure 3-2 shows the time-frequency resource sharing between LTE and NR cells.
● Time domain: Flash spectrum sharing is supported on a 1 ms basis, meaning
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 cells based on their traffic
volumes.

(2021-12-30)
SingleRAN
Figure 3-2 Time-frequency resource sharing between LTE and NR cells
3.1.1.2 Key Technologies

Some channels may conflict with each other during LTE and NR spectrum sharing.
Such conflicts can be avoided by properly coordinating uplink and downlink
physical channel resource scheduling, improving spectrum usage.
Uplink Physical Channels

Figure 3-3 shows the positions of uplink physical channels after this function is
enabled.
Figure 3-3 Positions of uplink physical channels

(2021-12-30)
SingleRAN
The uplink physical channel resources are coordinated and scheduled as follows:
● LTE and NR sounding reference signals (SRSs): SRSs can be configured either
for both LTE and NR or for only NR. SRS configuration is controlled by the
LTE_UE_SRS_NOT_CONFIG_SW option of the
SpectrumCloud.SpectrumCloudEnhSwitch parameter.
– When this option is selected, SRSs resources are only allocated to NR and
are not allocated to LTE.
– When this option is deselected, SRS resources are allocated to both LTE
and NR.
In this scenario, LTE reserves subframes 0 and 5 for NR as cell-specific
SRS subframes. When LTE UEs are scheduled on subframes during which
NR SRSs are transmitted, the uplink MCS index decreases, affecting the
uplink data rates of LTE UEs. LTE and NR SRS resource allocation
optimization can be enabled by selecting the
LTE_NR_SRS_ALLOC_OPT_SW option of the
LteNrSpctShrCellGrp.LteNrSpctShrSwitch parameter. After the
optimization, LTE reserves only subframe 0 for NR as the cell-specific SRS
subframe, reducing the impact of NR SRS subframes on the uplink data
rates of LTE UEs.
● NR physical uplink control channel (PUCCH): The NR PUCCH occupies
symmetrical RBs at the two ends of the bandwidth. The number of RBs for
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 or NSA and
SA hybrid networking, the NR PUCCH always includes the common PUCCH,
which occupies four RBs. For details about the common PUCCH, see
descriptions of the PUCCH in Channel Management in 5G RAN Feature
Documentation.
● LTE PUCCH: The position of the LTE PUCCH depends on the RB resources
fixedly reserved by the gNodeB for the NR PUCCH. In the 10 MHz bandwidth,
the gNodeB always reserves four RBs for the NR PUCCH, and the LTE PUCCH
is moved towards the center frequency by one RB at both the upper and
lower ends. In the 15 MHz bandwidth scenario, the gNodeB always reserves
four RBs for the NR PUCCH, and the LTE PUCCH does not need to be moved
towards the center frequency. In the 20 MHz bandwidth scenario, the gNodeB
always reserves six RBs for the NR PUCCH, and the LTE PUCCH does not need
to be moved towards the center frequency. If the number of RBs configured
for the NR PUCCH does not exceed the number of fixedly reserved RBs, the
LTE PUCCH is symmetrically configured adjacent to the NR PUCCH at both
ends of the frequency domain. If the number of RBs configured for the NR
PUCCH exceeds the number of reserved RBs, 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 positions vary 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 both ends
of the frequency domain, so that the NR PUCCH and LTE PUCCH occupy
consecutive RBs.

(2021-12-30)
SingleRAN
The following uses a 20 MHz bandwidth as an example to illustrate how to

determine the start and end positions of the LTE PUCCH. In a 20 MHz
bandwidth, NR has 106 available RBs in the uplink, and LTE has 100 available
RBs in the uplink. Assume that 10 RBs are configured for the NR PUCCH, then
the NR PUCCH occupies five RBs at each end of the frequency domain: RBs 0
to 4 at the lower end and RBs 101 to 105 at the upper end. As NR has six
more RBs (RBs 100 to 106) than LTE in the frequency domain, that is, NR has
three more RBs than LTE at each end of the frequency domain, LTE needs to
reserve two RBs at each end (RBs 0 and 1 at the lower end, and RBs 98 and
99 at the upper end) for NR so that the NR PUCCH can occupy five RBs at
each end of the frequency domain. In this case, you need to set the
CellRbReserve.RbRsvStartIndex parameter to 2 (RBs 0 and 1 are reserved for
NR), and the CellRbReserve.RbRsvEndIndex parameter to 97 (RBs 98 and 99
are reserved for NR). For details, see Figure 3-4.
Figure 3-4 Example of the start and end positions of the LTE PUCCH
The number of RBs for the LTE PUCCH is specified by parameter

configurations or is dynamically adjusted. For details, see 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, it
may interfere with SRSs, affecting network performance.
● LTE physical random access channel (PRACH): The LTE PRACH is configured
adjacent to the LTE PUCCH at the lower end, and 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, and the NR PRACH
always occupies six RBs.
● LTE and NR physical uplink shared channels (PUSCHs): The total available
shared PUSCH resources for LTE and NR equal the total spectrum resources

(2021-12-30)
SingleRAN
minus the resources occupied by the LTE and NR PUCCHs and PRACHs. The
total available shared PUSCH resources for LTE and NR are dynamically
shared between them based on traffic requirements.
Downlink Physical Channels

Downlink physical channel resources are coordinated and scheduled as follows:
● The LTE SS/PBCH and NR synchronization signal and PBCH block (SSB) are
transmitted on different occasions. The NR 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 use of two SSB beams for
cell coverage is called the SSB dual-beam function, further details of
which can be found in Beam Management in 5G RAN Feature
Documentation.
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.
● With the exception of system information and messages transmitted before
RRC reestablishment during initial access, the data transmitted on the NR
PDSCH actively avoids conflicts with LTE CRSs through CRS rate matching. NR
UEs must support 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.
– The LTE_HO_TO_DSS_NR_OPT_SW option of the NR parameter
gNodeBParam.LteHandoverAlgoSwitch can be selected to prohibit UEs
that do not support CRS rate matching from being handed over to the NR
cell.
– The DSS_FREQ_INDICATION option of the LTE parameter
NrNFreq.AggregationAttribute can be selected to configure the
neighboring NR frequency of the LTE cell as a spectrum sharing
frequency. UEs that do not support CRS rate matching are prohibited
from being handed over or redirected to this frequency. This function is
supported only in SA networking or NSA and SA hybrid networking, and
is not supported in NSA networking.
– When the number of LTE CRS ports (specified by the LTE parameter
Cell.CrsPortNum) is 1, the LTE_CRS_PORT_1_RM_SW option of the NR
parameter gNBDULteNrSpctShrCg.FddLteNrSpctShrSwitch can be
selected so that the NR PDSCH performs CRS rate matching in the
pattern of one LTE CRS port. CRS rate matching in the pattern of one LTE
CRS port is supported only when cells use the independent power
configuration mode (LTE parameter SpectrumCloud.SpctShrMode set to
LTE_NR_PWR_INDEPENDENT). If CRS rate matching in the pattern of
one LTE CRS port is not enabled, the NR PDSCH performs CRS rate
matching in the pattern of two LTE CRS ports even when only one CRS
port is configured.
When two or four CRS ports are configured, the NR PDSCH performs CRS
rate matching in the pattern of two or four LTE CRS ports.

(2021-12-30)
SingleRAN
● The LTE CSI-RS/CRSs/DMRS/SS/PBCH and NR CSI-RS/TRSs/SSB/PDCCH avoid

conflicts with each other through statically coordinated scheduling.
● LTE CRSs and the NR SSB and SIB1 on the NR PDSCH avoid conflicts with
each other.
LTE CRSs avoid conflicts with the NR SSB and SIB1 on the NR PDSCH through
parameter configurations, whereby MBSFN subframes are 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 CRSs are sent only in PDCCH symbols in an
LTE MBSFN subframe, conflicts between LTE CRSs and the 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 or
CellMbsfnSfEnhConfig.FourFrameAllocation: Indicate the positions of
MBSFN subframes.
The MBSFN subframe configuration is affected by the SSB period and
activation status of the SSB dual-beam function. For details, see the
configuration suggestions in 3.4.1.1 Data Preparation.
For details about the concepts related to MBSFN subframes, see related
descriptions in eMBMS in eRAN Feature Documentation. For details about the
impact of MBSFN subframe configuration on the network, see the network
analysis description in eMBMS in eRAN Feature Documentation.
● LTE CRSs and RRC messages on the NR PDSCH avoid conflicts with each other.
LTE CRSs use statically 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 one or two LTE
CRS ports) or two symbols (in the case of four LTE CRS ports), 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 configuration
suggestions, see 3.4.1.1 Data Preparation.
● The LTE and NR PDSCHs avoid conflicts with each other through dynamically
coordinated scheduling. In addition, the LTE PDSCH actively avoids conflicts
with the NR SSB/CSI-RS/TRSs/DMRS/PDCCH through dynamic scheduling, and
the NR PDSCH actively avoids conflicts with the LTE CRSs/CSI-RS/SS/PBCH/
PHICH/PCFICH/PDCCH through dynamic scheduling.
– The NR PDSCH can avoid the LTE CSI-RS at the RE or subframe level.
When the LTE_CSI_RS_AVOID_POLICY_SW option of the LTE parameter
LteNrSpctShrCellGrp.LteNrSpctShrSwitch and the
LTE_CSI_RS_AVOID_SW option of the NR parameter
gNBDULteNrSpctShrCg.FddLteNrSpctShrSwitch are both selected,
conflicts are avoided at the RE level. That is, the NR PDSCH avoids the

(2021-12-30)
SingleRAN
REs occupied by the LTE CSI-RS. In other circumstances, conflicts are

avoided at the subframe level. That is, the NR PDSCH avoids the
subframes occupied by the LTE CSI-RS.
When the TX/RX mode of the LTE and NR cells is 8T8R, RE-level
avoidance between the NR PDSCH and LTE CSI-RS is not supported.
– The NR PDSCH supports RB- and symbol-level avoidance of the LTE SS/
PBCH through rate matching. You can select the
LTE_SS_PBCH_RM_OPT_SW option of the NR parameter
NRDUCellAlgoSwitch.SpectrumCloudEnhSwitch to enable the NR
PDSCH to use one pattern for SS/PBCH rate matching. When this option
is deselected, the NR PDSCH uses two patterns for SS/PBCH rate
matching. This option can be set based on the network plan. When the
NR PDSCH uses two rate matching patterns, the avoidance is more
accurate and at the same time more pattern resources are consumed,
compared with when one rate matching pattern is used.
● The NR PDCCH and PDSCH can share spectrum resources in TDM and FDM
modes. The spectrum resource sharing in TDM mode is supported by default
and does not require parameter configuration. The spectrum resource sharing
in FDM mode is supported only when PDCCH rate matching is enabled by
selecting the PDCCH_RATEMATCH_SW option of the NR parameter
NRDUCellPdsch.RateMatchSwitch. PDCCH rate matching applies only to
peak rate scenarios. For details about its network impact, see Scheduling in
5G RAN Feature Documentation.
● The position of the downlink additional DMRS can be configured on the NR
PDSCH by setting the NR parameter NRDUCellPdsch.DlAdditionalDmrsPos,
to improve user experience. In mobility scenarios, this parameter is set to
POS1. In fixed-point scenarios, this parameter is set to NOT_CONFIG.
● The NR PDSCH and SSB can share spectrum resources in TDM and FDM
modes. The spectrum resource sharing in FDM mode is supported only when
SSB rate matching is enabled by selecting the SSB_RATEMATCH_SW option
of the NR parameter NRDUCellPdsch.RateMatchSwitch. The spectrum
resource sharing in TDM mode is supported by default and does not require
parameter configuration. SSB rate matching applies only to peak rate
scenarios. For details about its network impact, see Scheduling in 5G RAN
Feature Documentation.
In addition, the NR SSB frequency domain can be configured to improve the
spectrum usage on the NR side. The details are as follows:
– 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 needs to 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 by the value of the
NRDUCell.SsbDescMethod parameter. The specific parameter value for
this function must be confirmed by Huawei engineers.

(2021-12-30)
SingleRAN
Before configuring the preceding two parameters, you need to ensure 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, you need
to set the NRDUCellCoreset.CommonCtrlResRbNum parameter to RB48. If
the NRDUCellPdcch.OccupiedSymbolNum parameter is set to 2SYM, you
need to set the NRDUCellCoreset.CommonCtrlResRbNum parameter to
RB24 or RB48.
3.1.2 Enhanced Functions of Flash Dynamic Spectrum Sharing
3.1.2.1 Flexible Spectrum Priority Mode
Configuration of the Percentages of Spectrum Resources to Be Preferentially

Allocated
To ensure proper resource allocation, the percentages of resources preferentially
allocated to the LTE and NR cells for MBB services can be set based on their traffic
volume requirements. The resources here refer to the PUSCH and PDSCH
resources. The percentage for LTE is specified by the
LteNrSpctShrCellGrp.LteNrSpctShrLtePriResRatio parameter, and the
percentage for NR is equal to 100% minus the value of this parameter. Spectrum
resources are allocated based on these percentages as follows:
● When the ratios of actual traffic volume requirements of the LTE and NR cells
to the total spectrum resources are both less than, or both exceed, the
percentages of resources preferentially allocated, spectrum resources are
allocated based on the percentages of resources preferentially allocated to
each cell.
● When the actual traffic volume requirement of the cells of one RAT (RAT 1)
exceeds the percentage of resources preferentially allocated to that RAT, and
the actual traffic volume requirement of the cells of the other RAT (RAT 2)
does not, the unused resources for RAT 2 can be occupied by RAT 1. For
example, if the percentage of resources preferentially allocated to the LTE cell
is 60%, and the actually required LTE resource percentage is 70%, and if the
percentage of resources preferentially allocated to the NR cell is 40%, and the
actually required NR resource percentage is 35%, the unused 5% of resources
for the NR cell can be used by the LTE cell. As a result, the LTE cell can use
65% of the shared spectrum resources.
In addition to the preceding allocation principles, the setting of the

LNR_RES_ALLOC_ADAPT_SW option of the
LteNrSpctShrCellGrp.LteNrSpctShrSwitch parameter also affects the actual
allocation of spectrum resources.
● If this option is selected, the system allocates spectrum resources based on

the percentage specified by the
LteNrSpctShrCellGrp.LteNrSpctShrLtePriResRatio parameter, for whichever
direction (uplink or downlink) with the larger sum of traffic volumes of the
LTE and NR cells. For the other direction, the system dynamically allocates
spectrum resources based on the actual traffic volume requirements of the
LTE and NR cells. For example, if the sum of the uplink traffic volumes of the

(2021-12-30)
SingleRAN
LTE and NR cells is greater than the sum of the downlink traffic volumes of
the LTE and NR cells, the uplink spectrum resources are allocated to the LTE
and NR cells based on the percentage specified by the
LteNrSpctShrCellGrp.LteNrSpctShrLtePriResRatio parameter. The downlink
spectrum resources are allocated to the LTE and NR cells based on their actual
traffic volume requirements.
● If this option is deselected, the system allocates the sum of the uplink and
downlink spectrum resources of the LTE and NR cells based on the value of
the LteNrSpctShrCellGrp.LteNrSpctShrLtePriResRatio parameter.
Table 3-1 lists the counters used for measuring the shared spectrum resources
occupied by the LTE and NR cells in the uplink and downlink.
Table 3-1 Counters for measuring the number of uplink and downlink available
RBs in LTE and NR cells
Counter ID Counter Name
1526759050 L.ChMeas.PRB.UL.Actual.Avail
1526759052 L.ChMeas.PRB.UL.PUSCH.Actual.Avai
l
1526759051 L.ChMeas.PRB.DL.Actual.Avail
1911827161 N.PRB.UL.Actual.Avail.Avg
1911827162 N.PRB.UL.PUSCH.Actual.Avail.Avg
1911827160 N.PRB.DL.Actual.Avail.Avg
Inter-RAT Preferential Guarantee for GBR Services

If the percentage of resources preferentially allocated to a RAT is less than the
percentage required by guaranteed bit rate (GBR) services of that RAT, experience
of GBR services of that RAT will be affected. For example, if the percentage of
resources preferentially allocated to LTE is 40% and the percentage required by
GBR services is 60%, 20% of GBR service requirements cannot be satisfied,
affecting GBR service experience.
The function of inter-RAT preferential guarantee for GBR services is introduced.

This function defines the priority of GBR services as follows: The priority of LTE
GBR services is higher than that of NR non-GBR services, and the priority of NR
GBR services is higher than that of LTE non-GBR services. In the preceding
example, the unsatisfied LTE GBR services can occupy the resources of NR non-
GBR services. In this way, GBR service experience is preferentially guaranteed.
This function is enabled when the GBR_PRI_ALLOC_SW option of the LTE

parameter LteNrSpctShrCellGrp.LteNrSpctShrSwitch is selected. For details
about LTE GBR and non-GBR services, see Scheduling in eRAN Feature
Documentation. For details about NR GBR and non-GBR services, see QoS
Management in 5G RAN Feature Documentation.

(2021-12-30)
SingleRAN
3.1.2.2 Flexible Power Allocation Mode

This function supports flexible power allocation modes specified by the LTE
parameter SpectrumCloud.SpctShrMode. When this parameter is set to
LTE_NR_PWR_DYN_SHR_WITH_SPCT, the LTE and NR cells share the same power,
and the percentage of power allocated to a RAT is equal to the percentage of
spectrum allocated to that RAT. When this parameter is set to
LTE_NR_PWR_INDEPENDENT, the LTE and NR cells use independently configured
spectrum power.
Figure 3-5 elaborates on these power allocation modes using a 2 x 40 W RF

module as an example. In independent power configuration mode, the LTE and NR
cells can each only be configured with the maximum transmit power of 2 x 20 W.
In spectrum power sharing mode, the power configured for the LTE and NR cells
must be greater than or equal to the power in independent power configuration
mode. The LTE and NR cells can both be configured with a transmit power within
the range of 2 x 20 W to 2 x 40 W, and minimally share the total power of 2 x 20
W. The spectrum power sharing mode helps save the transmit power by 2 x 20 W
(2 x 40 W – 2 x 20 W), compared with the independent power configuration
mode.
Figure 3-5 Power allocation mode
Assuming that the cell power configurations are the same, independent power
configuration mode results in better capacity performance but a higher power
consumption, whereas spectrum power sharing mode reduces power consumption
but leads to capacity performance loss. Therefore, when the power is sufficient,
independent power configuration mode is preferred. When the power is
insufficient, spectrum power sharing mode can be used.
In spectrum power sharing mode, the power spectral density (PSD) of the NR cell
can be adaptively adjusted. When the transmit power required by the NR cell
exceeds the configured power, the gNodeB adaptively reduces the PSD of the NR
cell to ensure that the NR cell can use more spectrum resources, improving the
spectral efficiency of UEs in the NR cell. This function is enabled when the
PWR_SPCT_DENSITY_ADAPT_SW option of the NR parameter
NRDUCellAlgoSwitch.SpectrumCloudEnhSwitch is selected. After this function is

(2021-12-30)
SingleRAN
enabled, the gNodeB adaptively adjusts the PSD of data channels to improve the
spectral efficiency of UEs in the NR cell.
When spectrum power sharing mode is used, and the LTE and NR baseband
processing units need to be connected to the RRU through their respective optical
fibers, the LNR_PWR_WITH_SPCT_OPT_SW option of the LTE parameter
SpectrumCloud.SpectrumCloudEnhSwitch must be selected. When independent
power configuration mode is used, LTE and NR can use their respective optical
fibers over the CPRI interface without the need of selecting this option.
3.1.2.3 Co-carrier Co-CPRI Data

After LTE FDD and NR Flash Dynamic Spectrum Sharing is enabled, the LTE and
NR cells each occupy a portion of CPRI bandwidth. When LTE and NR share the
same CPRI optical fibers (either the LTE baseband processing unit or the NR
baseband processing unit is connected directly to the RRU through an optical
fiber) and the CPRI bandwidth is insufficient, they can be configured to share the
same carrier and CPRI data resources in order to meet CPRI bandwidth
requirements. The LTE and NR co-carrier co-CPRI data function is controlled by the
LTE parameter LteNrSpctShrCellGrp.LteNrCoCarrCoCpriDataSw and enables LTE
and NR cells to share a portion of CPRI bandwidth. 32T32R cells do not support
the co-carrier co-CPRI data function.
When the LTE and NR co-carrier co-CPRI data function is used together with the
CPRI compression function, the CPRI compression ratios between LTE and NR cells
must be the same. When the LTE and NR co-carrier co-CPRI data function is used
together with the uplink interference suppression function on the LTE side, the
uplink interference suppression value must be consistently set between LTE and
NR cells. For details about the configuration requirements, see 3.1.3 Application
Scenarios of Simultaneous Use of Flash Dynamic Spectrum Sharing and Other
Functions.
3.1.2.4 LTE Key Event Assurance

The LTE key event assurance function preferentially ensures the capacity of LTE
cells in NSA networking when LTE cells are heavily loaded in scenarios such as
concerts, sports events, and major holidays. This function is enabled by selecting
the LTE_BIG_EVENT_ASSURANCE_SW option of the LTE parameter
LteNrSpctShrCellGrp.LteNrSpctShrSwitch. When this function is required, you
need to set the LteNrSpctShrCellGrp.LteBigEventUeNumThld and
LteNrSpctShrCellGrp.LteBigEventUeNumThldOffset parameters to specify the
LTE key event user number threshold and the threshold offset. In addition, you
also need to set the NR parameter
gNBDULteNrSpctShrCg.LteBigEventAssureUeNumThld, which specifies the user
number threshold for LTE key event assurance for NR cells. This function is
applicable only to the Option 3x architecture in NSA networking
The LTE key event assurance function is triggered when both of the following
conditions are met:
● Number of LTE UEs in RRC connected mode >
LteNrSpctShrCellGrp.LteBigEventUeNumThld +
LteNrSpctShrCellGrp.LteBigEventUeNumThldOffset
● Number of NR UEs in RRC connected mode ≤
gNBDULteNrSpctShrCg.LteBigEventAssureUeNumThld

(2021-12-30)
SingleRAN
When the LTE key event assurance function is triggered, the uplink and downlink
data split modes for NR cells change to MCG only. The NR cells are in the LTE key
event assurance state, and all the shared spectrum resources are allocated to LTE
cells to ensure the capacity of LTE cells.
When the number of LTE UEs in RRC connected mode becomes less than or equal
to LteNrSpctShrCellGrp.LteBigEventUeNumThld minus
LteNrSpctShrCellGrp.LteBigEventUeNumThldOffset, both the LTE and NR cells
exit the LTE key event assurance state and enter the non-LTE-key-event-assurance
state.
In addition, a 5-minute protection timer is introduced to NR cells to protect NR
cells from ping-pong switchovers between the LTE key event guarantee state and
the non-LTE-key-event-assurance state.
3.1.3 Application Scenarios of Simultaneous Use of Flash

Dynamic Spectrum Sharing and Other Functions
Simultaneous Use with NB-IoT
For 3900 and 5900 series base stations, LTE FDD and NR Flash Dynamic Spectrum
Sharing can work together with NB-IoT deployed in LTE guard band mode.
In this scenario, the spectrum occupied by the NB-IoT cell and the spectrum
occupied by the NR cell overlap, causing severe mutual interference. As a result,
the NB-IoT cell or NR cell becomes unavailable. Specifically:
● If an NB-IoT cell is configured and activated prior to an NR cell, the NR cell
cannot be activated.
● If an NR cell is configured and activated prior to an NB-IoT cell, the NB-IoT
cell cannot be activated.
To eliminate the interference, spectrum resources need to be reserved for the NB-
IoT cell, and the reserved spectrum resources are unavailable for the NR cell. The
uplink and downlink RBs reserved for NB-IoT are configured through the
NRDUCellRbReserve.RbRsvMode, NRDUCellRbReserve.RbRsvType,
NRDUCellRbReserve.RbRsvStartIndex, and NRDUCellRbReserve.RbRsvEndIndex
parameters.
The uplink and downlink RBs reserved for NB-IoT must be confirmed by Huawei
engineers. Table 3-2 lists the recommended number of uplink and downlink RBs
to be reserved in different LTE and NR cell bandwidth scenarios. The
recommended configuration preferentially ensures the NB-IoT cell performance
while considers the NR cell throughput.
For details about NB-IoT deployed in LTE guard band mode, see NB-IoT Basics
(FDD) in eRAN Feature Documentation.

(2021-12-30)
SingleRAN
Table 3-2 Recommended reserved spectrum resources for the NB-IoT cell in
typical scenarios
LTE and NR Cell Bandwidth Number of Uplink and Downlink RBs

Reserved for NB-IoT
20 MHz 3
15 MHz 2
10 MHz 1
Simultaneous Use with CPRI Compression

In LTE and NR spectrum sharing, when the co-carrier co-CPRI data function and
the 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 3-3 describes the configuration
requirements. For details about CPRI compression, see CPRI Compression in eRAN
Feature Documentation and CPRI Compression in 5G RAN Feature Documentation.
Table 3-3 Configuration requirements on the CPRI compression types of the LTE
and NR cells
Bandwidth CPRI CPRI Compression CPRI Compression

Compression Type of LTE Cells Type of NR Cells
Ratio
10 MHz No CPRI NO_COMPRESSION NO_COMPRESSION

compression
3:2 CPRI NORMAL_COMPRESSI 1DOT5_COMPRESSIO

compression ON N
2.2:1 CPRI 2_2_COMPRESSION 2DOT2_COMPRESSIO

Compressiona N
15 MHz or 20 No CPRI NO_COMPRESSION NO_COMPRESSION

MHz compression
2:1 CPRI NORMAL_COMPRESSI 2_COMPRESSION

compression ON

Compressiona N
a: The 2.2:1 CPRI compression ratio is required when the cell TX/RX mode is
32T32R, so that CPRI compression can be used together with the co-carrier co-
CPRI data function.

(2021-12-30)
SingleRAN
Simultaneous Use with LTE Uplink Interference Suppression

For the DBS3900 LampSite and DBS5900 LampSite, when the co-carrier co-CPRI
data function in spectrum sharing and the uplink interference suppression function
are both enabled, the UlInterfSuppressCfg.UlIntrfSuppressionValue parameter
for LTE cells must be set to the same value as that of the
NRDUCellTrp.UlRxPowerAttenuationValue parameter for NR cells. For details
about uplink interference suppression on the LTE side, see pRRU Uplink
Interference Suppression in eRAN Feature Documentation.
Simultaneous Use with LTE Downlink Semi-persistent Scheduling

When LTE FDD and NR Flash Dynamic Spectrum Sharing is used together with LTE
downlink semi-persistent scheduling, the upper limit on the proportion of RBs that
can be allocated for LTE downlink semi-persistent scheduling is configurable
(through the SpectrumCloud.DlSpsRestrictRatio parameter). This proportion
together with the percentage of spectrum resources to be preferentially allocated
to LTE for MBB services (specified by the
LteNrSpctShrCellGrp.LteNrSpctShrLtePriResRatio parameter) determines the
proportion of RBs allocated for LTE downlink semi-persistent scheduling as
follows: The proportion of RBs allocated for LTE downlink semi-persistent
scheduling = (SpectrumCloud.DlSpsRestrictRatio x
LteNrSpctShrCellGrp.LteNrSpctShrLtePriResRatio) x 100%. For details about LTE
downlink semi-persistent scheduling, see VoLTE in eRAN Feature Documentation.
Simultaneous Use with Downlink Intra-FR Inter-band CA

When downlink intra-FR inter-band CA is enabled after LTE FDD and NR Flash
Dynamic Spectrum Sharing, the NR PUCCH occupies more RBs. The RBs occupied
by the NR PUCCH are likely to conflict with the RBs occupied by the LTE PUCCH. In
this case, the LTE PUCCH RB configuration needs to be modified through the LTE
parameters CellRbReserve.RbRsvMode, CellRbReserve.RbRsvType,
CellRbReserve.RbRsvStartIndex, and CellRbReserve.RbRsvEndIndex. It is
recommended that the LTE PUCCH be symmetrically configured adjacent to the
NR PUCCH at both ends of the frequency domain.
In addition, the number of RBs occupied by the NR PUCCH must be as follows:

● NSA networking: Number of RBs occupied by the NR PUCCH =
(NRDUCellPucch.Format1RbNum + NRDUCellPucch.Format3RbNum +
NRDUCellPucch.Format4RbNum + NRDUCellPucch.CsiDedicatedRbNum +
NRDUCellPucch.Format4CsiDedicatedRbNum)/2 – Number of RBs occupied
by the guard band at either end of the NR frequency domain
● SA networking, and NSA and SA hybrid networking: Number of RBs occupied
by the NR PUCCH = (NRDUCellPucch.Format1RbNum +
NRDUCellPucch.Format3RbNum + NRDUCellPucch.Format4RbNum +
NRDUCellPucch.CsiDedicatedRbNum +
NRDUCellPucch.Format4CsiDedicatedRbNum)/2 – Number of RBs occupied
by the guard band at either end of the NR frequency domain + Number of
RBs occupied by the NR common PUCCH at either end of the frequency
domain
In NSA networking, the NR PUCCH does not include the common PUCCH. In SA
networking or NSA and SA hybrid networking, the NR PUCCH always includes the

(2021-12-30)
SingleRAN
common PUCCH, which occupies four RBs, with two RBs at each end of the
frequency domain. For details about the common PUCCH, see descriptions of the
PUCCH in Channel Management in 5G RAN Feature Documentation.
In addition, you are advised to deactivate the LTE and NR cells before performing
the preceding configurations and activate the cells after the configurations are
complete.
Simultaneous Use with WBB

When LTE FDD and NR Flash Dynamic Spectrum Sharing is used with wireless
broadband (WBB), it is recommended that the WBB_MBB_CONTROL_OPT_SW
option of the SpectrumCloud.SpectrumCloudEnhSwitch parameter be selected.
When this option is selected, the base station allocates resources to LTE WBB and
MBB services based on the actually available LTE spectrum resources. The
percentages of resources actually allocated to WBB and MBB services comply with
the settings of the CellWttxParaCfg.MbbUserDlPrbUpLimit,
CellWttxParaCfg.MbbUserUlPrbUpLimit,
CellWttxParaCfg.WbbUserDlPrbUpLimit, and
CellWttxParaCfg.WbbUserUlPrbUpLimit parameters. For details about WBB, see
WBB in eRAN Feature Documentation.
To ensure spectral efficiency, it is recommended that the following equations be
met: CellWttxParaCfg.MbbUserDlPrbUpLimit +
CellWttxParaCfg.WbbUserDlPrbUpLimit = 100, and
CellWttxParaCfg.MbbUserUlPrbUpLimit +
CellWttxParaCfg.WbbUserUlPrbUpLimit = 100.
3.1.4 HDSS based on Asymmetric Beam

Static Multiple Beam is one of the LTE FDD multi-sector solutions. Static Multiple
Beam generates at least two beams on the horizontal plane by means of
beamforming, with each beam serving a sector split cell, thereby maximizing
network capacity. HDSS based on Asymmetric Beam enables the two or more LTE
FDD sector split cells served by the beams generated by Static Multiple Beam to
dynamically share the same spectrum resources with an NR FDD cell, improving
spectrum utilization.
Static Multiple Beam can be used in smart 8T8R and 32T32R massive MIMO
modes. In smart 8T8R mode, it supports two beams, which correspond to two LTE
FDD sector split cells. In 32T32R massive MIMO mode, it supports two to four
beams, which correspond to two to four LTE FDD sector split cells. For details
about Static Multiple Beam in smart 8T8R mode, see Smart 8T8R (FDD). For
details about Static Multiple Beam in 32T32R massive MIMO mode, see Massive
MIMO (FDD). The principles of HDSS based on Asymmetric Beam are the same in
these two scenarios, with the only difference in the number of LTE FDD sector split
cells. The following uses the smart 8T8R scenario as an example for illustration.
For ease of description, LTE and NR cells are used to refer to LTE FDD sector split
cells served by the beams generated by Static Multiple Beam and NR FDD cells,
respectively.
This function supports NSA, SA, and NSA and SA hybrid networking. Unless
otherwise specified, the descriptions apply to all networking scenarios. This
function applies to 3900 and 5900 series base stations.

(2021-12-30)
SingleRAN
3.1.4.1 Principles
This function enables the two LTE FDD sector split cells served by the two beams
generated by Static Multiple Beam in smart 8T8R mode (referred to as LTE cells)
and an NR FDD cell (referred to as NR cell) to dynamically share time-frequency
resources on a shared spectrum segment based on their traffic volumes. Figure
3-6 illustrates the working principles of this function. The two LTE cells and the NR
cell must be configured with the same bandwidth, which can be 10 MHz, 15 MHz,
and 20 MHz, and must be added to associated spectrum sharing cell groups.
Specifically:

volumes. The two LTE cells are allocated the same resources.
Figure 3-6 HDSS based on Asymmetric Beam

sharing cell groups. In addition, the LTE and NR cells sharing spectrum resources
must have aligned radio frames and subframes.
● Turning on function switches on the LTE and NR sides

LTE_NR_SPECTRUM_SHR for both LTE cells.
NRDUCellAlgoSwitch.SpectrumCloudSwitch parameter.
● Configuring spectrum sharing cell groups
– Add planned LTE cells to an LTE spectrum sharing cell group by setting
LteNrSpctShrCellGrp.LteNrSpectrumShrCellGrpId. Both LTE cells must
be added to the LTE spectrum sharing cell group.

(2021-12-30)
SingleRAN

– Add a planned NR cell to the NR spectrum sharing cell group by setting
– Set the LTE parameter CellFrameOffset.FrameOffset or
on the LTE side. If both parameters are configured on the LTE side, the
value of the CellFrameOffset.FrameOffset parameter is used. The two
LTE cells must be configured with the same frame offset. 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 is used.
– Set the LTE parameter CellFrameOffset.TaOffset and NR parameter
NRDUCell.TaOffset.

The uplink and downlink physical channel resource scheduling of LTE and NR cells
need to be properly coordinated during LTE and NR spectrum sharing in this
function. This is to avoid conflicts and improve spectrum utilization.

The two LTE cells in this function use the same spectrum resources through spatial
multiplexing. 3.1.4.2 Key Technologies shows the positions of uplink physical
channels on the spectrum shared by LTE and NR cells.

(2021-12-30)
SingleRAN
The uplink physical channel resources of the LTE cells need to be merged before
spectrum sharing with the NR cell. Table 3-4 describes how the channel resources
are merged.
Table 3-4 Uplink physical channel resource merging of LTE cells
Chan Merging Mode

nel
PUCC The combined PUCCH and PRACH resources of the two LTE cells is used
H as the total resources of the two channels allocated to the LTE cells. If
these resources are not fully occupied by the PUCCH and PRACH of the
PRAC two LTE cells, the idle resources can be used by the PUSCH of the LTE
H cells.
SRS The larger amount of SRS time-frequency resources between the two
LTE cells is considered as shared SRS resources allocated to the LTE and
NR cells.
PUSC The larger amount of PUSCH resources between the two LTE cells is
H considered as the PUSCH resources allocated to LTE cells.
Spectrum resources allocated to the NR cell are equal to the total shared
spectrum resources minus the spectrum resources allocated to the two LTE cells.
The spectrum resources allocated to the two LTE cells are the sum of the channel
resources described in Table 3-4.

(2021-12-30)
SingleRAN
For details about the coordinated scheduling of uplink physical channel resources,
see 3.1.1.2 Key Technologies.

The downlink physical channel resources of the LTE cells need to be merged
before spectrum sharing with the NR cell. Table 3-5 describes how the channel
resources are merged.
Table 3-5 Downlink physical channel resource merging of LTE cells
Channel Merging Mode
CRS Choose the LTE performance preferred or NR performance

preferred policy based on the network plan.
● LTE performance preferred: LTE cells must have different
PCIs as well as different PCI mod 3 values. In this case, LTE
cells have two or three CRS patterns. The
LTE_CRS_RATEMATCH_ALL_SYM_SW option of the
NRDUCellAlgoSwitch.SpectrumCloudEnhSwitch
parameter must be selected to enable rate matching on all
RBs in the symbols where LTE CRSs appear, so as to
eliminate the interference of LTE cells on the NR cell.
● NR performance preferred: LTE cells must have different
PCIs but the same PCI mod 3 value. In this case, LTE cells
have the same CRS pattern. The
parameter must be deselected to allow the gNodeB to
perform CRS rate matching based on one LTE CRS pattern.
SS/PBCH The SS/PBCH time-frequency domain positions of the LTE cells

are the same.
PDCCH The larger number of PDCCH symbols between the two LTE
cells is used as the number of PDCCH symbols of these LTE
cells.
PDSCH The larger amount of PDSCH resources between the two LTE
cells is used as the amount of PDSCH resources of these LTE
cells.
For details about the coordinated scheduling of downlink physical channel

resources, see 3.1.1.2 Key Technologies.
3.1.4.3 Enhanced Functions
Flexible Spectrum Priority Mode

The two LTE cells must be added to the same LTE spectrum sharing cell group, and
must be configured with the same percentage of spectrum resources to be

(2021-12-30)
SingleRAN
preferentially allocated. For details about the flexible spectrum priority mode, see
3.1.2.1 Flexible Spectrum Priority Mode.
Flexible Power Allocation Mode

The two LTE cells must be configured with the same power allocation mode. For
details about the power allocation mode, see 3.1.2.2 Flexible Power Allocation
Mode.
Co-carrier Co-CPRI Data

For details, see 3.1.2.3 Co-carrier Co-CPRI Data.
LTE Key Event Assurance

cells in NSA networking when the LTE cells are heavily loaded in scenarios such as
LteNrSpctShrCellGrp.LteNrSpctShrSwitch, and LTE parameters
LteNrSpctShrCellGrp.LteBigEventUeNumThld and
LteNrSpctShrCellGrp.LteBigEventUeNumThldOffset need to be configured to
specify the LTE key event user number threshold and the threshold offset. The NR
parameter gNBDULteNrSpctShrCg.LteBigEventAssureUeNumThld also needs to
be configured, which specifies the user number threshold for LTE key event
assurance for NR cells. This function is applicable only to Option 3x architecture in
NSA networking.
The LTE key event assurance function is triggered when the following conditions
are met:
● Either of the LTE cells meets this condition: Number of LTE UEs in RRC
connected mode > LteNrSpctShrCellGrp.LteBigEventUeNumThld +
data split modes for the NR cell change to MCG only. The NR cell enters the LTE
key event assurance state, and all the shared spectrum resources are allocated to
the two LTE cells to ensure their capacity.
When the number of LTE UEs in RRC connected mode in both LTE cells becomes
less than or equal to LteNrSpctShrCellGrp.LteBigEventUeNumThld minus
LteNrSpctShrCellGrp.LteBigEventUeNumThldOffset, the NR cell exits the LTE
key event assurance state and enters the non-LTE-key-event-assurance state.
To protect the NR cell from ping-pong switchovers between these two states, a 5-
minute protection timer is introduced to the NR cell.

(2021-12-30)
SingleRAN
3.1.4.4 Simultaneous Use of HDSS based on Asymmetric Beam and Other

Functions

The LTE and NR cells enabled with HDSS based on Asymmetric Beam must have
the same CPRI compression ratio. For details about the configuration
requirements, see Simultaneous Use with CPRI Compression in 3.1.3
Application Scenarios of Simultaneous Use of Flash Dynamic Spectrum
Sharing and Other Functions.

When HDSS based on Asymmetric Beam is used together with LTE downlink semi-
persistent scheduling, the upper limit on the proportion of RBs that can be
allocated for LTE downlink semi-persistent scheduling is configurable (through the
SpectrumCloud.DlSpsRestrictRatio parameter). It is recommended that this
parameter be set to the same value, and that the SpsSchSwitch option of the
CellAlgoSwitch.DlSchSwitch parameter be set to the same value for the two LTE
cells. This proportion together with the percentage of spectrum resources to be
preferentially allocated to LTE for MBB services (specified by the LTE parameter
LteNrSpctShrCellGrp.LteNrSpctShrLtePriResRatio) determines the proportion of
RBs allocated for LTE downlink semi-persistent scheduling as follows: The
proportion of RBs allocated for LTE downlink semi-persistent scheduling =
(SpectrumCloud.DlSpsRestrictRatio x
LteNrSpctShrCellGrp.LteNrSpctShrLtePriResRatio/100)%.

When downlink intra-FR inter-band CA is enabled after HDSS based on
Asymmetric Beam is enabled, the NR PUCCH occupies more RBs. The RBs occupied
recommended that the start position of the LTE PUCCH at the lower end of the
frequency domain (CellRbReserve.RbRsvStartIndex) and the end position of the
LTE PUCCH at the upper end of the frequency domain
(CellRbReserve.RbRsvEndIndex) be symmetrically configured adjacent to the NR
PUCCH. The two LTE cells must have the same PUCCH RB configuration.
complete.
Simultaneous Use with LTE PRACH Frequency-Domain Position Adaptation

When HDSS based on Asymmetric Beam is enabled, PRACH frequency-domain
position adaptation is turned on for only one LTE cell, and the PRACH frequency-
domain positions between these two LTE cells are different, more resources are
allocated to the LTE cells and fewer resources are allocated to the NR cell.
Therefore, it is recommended that the PrachFreqAdjSwitch option of the

(2021-12-30)
SingleRAN
CellAlgoSwitch.RachAlgoSwitch parameter be set to the same value for the two

LTE cells.
Simultaneous Use with LTE Uplink Semi-persistent Scheduling and LTE TTI
Bundling
When HDSS based on Asymmetric Beam is enabled, uplink semi-persistent
scheduling is enabled in only one LTE cell and takes effect, and TTI bundling is
enabled only in the other LTE cell and takes effect, the resources for semi-
persistent scheduling and those for TTI bundling are respectively merged for these
two LTE cells, and consequently the resources for the NR cell decrease. Therefore,
it is recommended that the two LTE cells use the same settings of the
TtiBundlingSwitch and SpsSchSwitch options of the
CellAlgoSwitch.UlSchSwitch parameter.
3.2 Network Analysis
3.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.
The gains provided by this function vary depending on the networking type and
whether HDSS based on Asymmetric Beam is enabled. Table 3-6 and Table 3-7
list the gains provided when HDSS based on Asymmetric Beam is disabled
compared with a typical static refarming solution. Table 3-8 and Table 3-9 list the
gains when HDSS based on Asymmetric Beam is enabled compared with a typical
static refarming solution.
Table 3-6 Average cell downlink throughput gain in NSA networking (with HDSS
based on Asymmetric Beam disabled)
Cell TX Total LTE NR LTE Cell NR Cell

Mode Bandwid Bandwid Bandwid Downlink Downlink
th tha tha Throughput Throughput
Gainb Gainb
2T 10 MHz 5 MHz 5 MHz 174%–195% 166%–174%
15 MHz 10 MHz 5 MHz 128%–143% 259%–302%
20 MHz 10 MHz 10 MHz 172%–192% 161%–189%
4T 10 MHz 5 MHz 5 MHz 174%–195% 155%–167%
15 MHz 10 MHz 5 MHz 128%–143% 241%–257%

(2021-12-30)
SingleRAN

Gainb Gainb
20 MHz 10 MHz 10 MHz 172%–192% 150%–163%
8T 10 MHz 5 MHz 5 MHz 170%–190% 150%–167%
15 MHz 10 MHz 5 MHz 125%–140% 236%–257%
20 MHz 10 MHz 10 MHz 170%–190% 145%–163%
32T 10 MHz 5 MHz 5 MHz 160%–180% 150%–167%
15 MHz 10 MHz 5 MHz 118%–133% 236%–257%
20 MHz 10 MHz 10 MHz 160%–180% 145%–163%
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 a
static refarming solution. If LTE and NR share spectrum power while sharing
spectrum, the NR cell gain decreases by 10% to 20%, and the LTE cell gain is
not affected. If LTE and NR use separate spectrum power while sharing
spectrum, the LTE and NR cell gains are not affected.
Table 3-7 Average cell downlink throughput gain in SA networking and NSA and
SA hybrid networking (with HDSS based on Asymmetric Beam disabled)

Gainb Gainb
2T 10 MHz 5 MHz 5 MHz 170%–195% 166%–174%
15 MHz 10 MHz 5 MHz 125%–143% 259%–302%
20 MHz 10 MHz 10 MHz 168%–192% 161%–189%
4T 10 MHz 5 MHz 5 MHz 170%–195% 155%–167%
15 MHz 10 MHz 5 MHz 125%–143% 241%–257%
20 MHz 10 MHz 10 MHz 168%–192% 150%–163%
8T 10 MHz 5 MHz 5 MHz 170%–190% 150%–167%
15 MHz 10 MHz 5 MHz 125%–140% 236%–257%
20 MHz 10 MHz 10 MHz 165%–190% 145%–163%
32T 10 MHz 5 MHz 5 MHz 150%~180% 150%–167%
15 MHz 10 MHz 5 MHz 108%~133% 236%–257%

(2021-12-30)
SingleRAN

Gainb Gainb
20 MHz 10 MHz 10 MHz 147%~180% 145%–163%

Table 3-8 Average cell downlink throughput gain in NSA networking (with HDSS
based on Asymmetric Beam enabled)
Gainb Gainb
8T LTE 40 MHz 20 MHz 20 MHz 92%–100% 165%–190%

preferred
10 MHz 5 MHz 5 MHz 170%–190% 90%–100%
15 MHz 10 MHz 5 MHz 125%–140% 141%–154%
20 MHz 10 MHz 10 MHz 170%–190% 90%–100%
8T NR 10 MHz 5 MHz 5 MHz 136%–152% 150%–167%

preferred
15 MHz 10 MHz 5 MHz 100%–112% 236%–257%
20 MHz 10 MHz 10 MHz 136%–152% 145%–163%
32T LTE 10 MHz 5 MHz 5 MHz 150%~180% 90%–100%

preferred
15 MHz 10 MHz 5 MHz 108%~133% 141%–154%
20 MHz 10 MHz 10 MHz 150%~180% 90%–100%
32T NR 10 MHz 5 MHz 5 MHz 122%–136% 150%–167%

preferred
15 MHz 10 MHz 5 MHz 90%–100% 236%–257%
20 MHz 10 MHz 10 MHz 122%–136% 145%–163%

(2021-12-30)
SingleRAN

Gainb Gainb

Table 3-9 Average cell downlink throughput gain in SA networking and NSA and
SA hybrid networking (with HDSS based on Asymmetric Beam enabled)
Cel Total LTE NR LTE Cell NR Cell
l Bandwidt Bandwidt Bandwidt Downlink Downlink
TX h ha ha Throughput Throughput
Mo Gainb Gainb
de
8T 40 MHz 20 MHz 20 MHz 92%–100% 165%–190%

LTE
pref 10 MHz 5 MHz 5 MHz 170%–190% 90%–100%
erre 15 MHz 10 MHz 5 MHz 125%–140% 141%–154%
d
20 MHz 10 MHz 10 MHz 170%–190% 90%–100%
8T 10 MHz 5 MHz 5 MHz 136%–152% 150%–167%

NR
pref 15 MHz 10 MHz 5 MHz 100%–112% 236%–257%
erre 20 MHz 10 MHz 10 MHz 136%–152% 145%–163%
d
32T 10 MHz 5 MHz 5 MHz 150%~180% 90%–100%

LTE
pref 15 MHz 10 MHz 5 MHz 108%~133% 141%–154%
erre 20 MHz 10 MHz 10 MHz 150%~180% 90%–100%
d
32T 10 MHz 5 MHz 5 MHz 122%–136% 150%–167%

NR
pref 15 MHz 10 MHz 5 MHz 90%–100% 236%–257%
erre 20 MHz 10 MHz 10 MHz 122%–136% 145%–163%
d

(2021-12-30)
SingleRAN
Cel Total LTE NR LTE Cell NR Cell

l Bandwidt Bandwidt Bandwidt Downlink Downlink
TX h ha ha Throughput Throughput
Mo Gainb Gainb
de

Specific gains can only be achieved when certain conditions are met.
● The LTE cell gain can only be achieved when all of 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 only be achieved when all of 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).
Actual gains achieved will be less than those listed in the table above if one of the
preceding conditions is not met. However, gains will not be negatively impacted as
a result.
3.2.2 Impacts
Network Impacts
● LTE-to-NR spectrum sharing has the following impacts on LTE networks:
– NR synchronization signals, the PBCH, reference channels, and system
information interfere with LTE. The interference leads to LTE quality-
related counters over the full band being inaccurately measured. 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:

(2021-12-30)
SingleRAN
▪ 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
3-10 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
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)/
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)/
Table 3-10 Counters used for measuring the average cell uplink
IBLER on the LTE side
1526728186 L.Traffic.UL.SCH.QPSK.ErrTB.Ibler
1526728188 L.Traffic.UL.SCH.16QAM.ErrTB.Ibler
1526727366 L.Traffic.UL.SCH.QPSK.TB
1526727367 L.Traffic.UL.SCH.16QAM.TB

(2021-12-30)
SingleRAN
Table 3-11 Counters used for measuring the average cell downlink
1526728180 L.Traffic.DL.SCH.QPSK.ErrTB.Ibler
1526728182 L.Traffic.DL.SCH.16QAM.ErrTB.Ibler
1526727354 L.Traffic.DL.SCH.QPSK.TB
1526727355 L.Traffic.DL.SCH.16QAM.TB
RBLER on the LTE side
1526728187 L.Traffic.UL.SCH.QPSK.ErrTB.Rbler
1526728189 L.Traffic.UL.SCH.16QAM.ErrTB.Rbler
1526728181 L.Traffic.DL.SCH.QPSK.ErrTB.Rbler
1526728183 L.Traffic.DL.SCH.16QAM.ErrTB.Rbler

(2021-12-30)
SingleRAN
▪ The access success rate, handover success rate, and RRC connection
reestablishment success rate decrease.
Access success rate = RRC Setup Success Rate
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 3-14 lists the related
counters.
RRC connection reestablishment success rate = L.RRC.ReEst.Succ/
L.RRC.ReEst.Att. Table 3-15 lists the related counters.
Table 3-14 Counters used for measuring the handover success rate
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

(2021-12-30)
SingleRAN
Table 3-15 Counters used for measuring the RRC connection

reestablishment success rate
1526727086 L.RRC.ReEst.Succ
1526727085 L.RRC.ReEst.Att
▪ The bearer service drop rate increases.

Bearer service drop rate = Service Drop Rate
– The spectrum resources available for LTE are reduced, resulting in a
fluctuation in the average uplink and downlink throughput of the LTE
cell, a decrease in the average uplink and downlink throughput of UEs,
and an increase in the uplink and downlink voice packet loss rates in the
cell.
▪ Average uplink cell throughput = Cell Uplink Average Throughput
▪ Average downlink cell throughput = Cell Downlink Average

Throughput
▪ Average uplink UE throughput = User Uplink Average Throughput
▪ Average downlink UE throughput = User Downlink Average

Throughput
▪ Uplink voice packet loss rate in a cell = Uplink Packet Loss Rate
(VoIP)
▪ Downlink voice packet loss rate in a cell = Downlink Packet Loss

Rate (VoIP)
● NR-to-LTE spectrum sharing has the following impacts on NR networks:
The spectrum resources available for NR are reduced, resulting in a
fluctuation in the average uplink and downlink throughput of the NR cell, and
a decrease in the average uplink and downlink throughput of UEs.
– Average uplink cell throughput = Cell Uplink Average Throughput (DU)
– Average downlink cell throughput = Cell Downlink Average Throughput
(DU)
– Average uplink UE throughput = User Uplink Average Throughput (DU)
– Average downlink UE throughput = User Downlink Average Throughput
(DU)
NOTE
LTE synchronization signals, the PBCH, reference channels, and system information do
not interfere with NR. As a result, NR quality-related counters 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

(2021-12-30)
SingleRAN
▪ Average user-plane CPU usage of an eNodeB board:

L.Traffic.Board.UPlane.CPULoad.AVG
▪ Average user-plane CPU usage of a gNodeB board:

VS.NRBoard.UPlane.CPULoad.Avg
– Increased ping delay
● After this function is enabled on the LTE and NR sides, if MBSFN subframes
are configured on TM9-dedicated carriers, the number of control format
indicators (CFIs) and control channel element (CCE) usage change as the CFI
range differs between MBSFN subframes and common subframes. The CCE
usage can be calculated using the following formula: CCE usage =
(L.ChMeas.CCE.CommUsed + L.ChMeas.CCE.ULUsed +
L.ChMeas.CCE.DLUsed)/L.ChMeas.CCE.Avail.
● If the LTE key event assurance function is enabled and the NR cell enters the
LTE heavy traffic state, the impacts are as follows:
– The values of the N.PDCP.Vol.UL.X2U.TrfPDU.Rx and
N.PDCP.Vol.DL.X2U.TrfPDU.Tx counters increase.
– The values of the L.Thrp.bits.UL.RLC.Send and L.Thrp.bits.DL.RLC.Send
counters increase.
● If the co-carrier co-CPRI data function is enabled and the UE is located near
the cell center, the gNodeB implements time synchronization between the LTE
and NR networks. This has the following impacts:
– On the LTE side: The values of counters L.TA.UE.Index0 to
L.TA.UE.Index6 slightly increase, and the values of counters
L.RA.TA.UE.Index0 to L.RA.TA.UE.Index11 slightly fluctuate.
– On the NR side:
▪ The values of counters N.RA.TA.UE.Index0 to N.RA.TA.UE.Index12

slightly increase.
▪ If CA is also enabled, the average uplink throughput (Cell‧Uplink‧

Average‧Throughput‧(DU)) of both the PCell and SCells fluctuates.
▪ If super uplink is also enabled, the average uplink throughput (Cell‧

Uplink‧Average‧Throughput‧(DU)) of the SUL cell fluctuates.
● If the LTE TA offset (specified by the CellFrameOffset.TaOffset parameter) is
changed from 0TS to another value, the values of counters L.TA.UE.Index0 to
L.TA.UE.Index15 and the values of counters L.RA.TA.UE.Index0 to
L.RA.TA.UE.Index11 slightly fluctuate.
Function Impacts
● Impacted functions on the LTE side

(2021-12-30)
SingleRAN
Function Function Switch Reference Description

Name (eRAN Feature
Documentation)
Uplink CA CaUl2CCSwitch Carrier The number of

option of the Aggregation uplink RBs available
CaMgtCfg.CellC for LTE decreases,
aAlgoSwitch which reduces the
parameter throughput of UEs
for which FDD uplink
carrier aggregation
(CA) takes effect.
Downlink CA None Carrier The number of

Aggregation downlink RBs
available for LTE
decreases, which
reduces the
throughput of UEs
for which FDD
downlink CA takes
effect.
Flexible CA MultiCarrierFlex Carrier The number of

from CaSwitch option Aggregation uplink and downlink
Multiple of the RBs available for LTE
Carriers CaMgtCfg.CellC decreases, and the
aAlgoSwitch selected serving cell
parameter combination may
change as a result.
Downlink DlMassiveCaSwi Carrier It is not

Massive CA tch option of the Aggregation recommended that
CaMgtCfg.CellC LTE cells enabled
aAlgoSwitch with this function be
parameter used as PCells, as the
PUCCH overhead
increases so that the
SRS cannot be
configured. As a
result, LTE network
throughput
decreases.
LTE SpectrumCoordi LTE Spectrum The number of

Spectrum nationSwitch Coordination uplink RBs available
Coordination option of the for LTE decreases,
CaMgtCfg.CellC which reduces the
aAlgoSwitch proportion of UEs for
parameter which LTE Spectrum
Coordination takes
effect.

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation)
UL Multi- UlMultiClusterS Scheduling The number of

Cluster witch option of uplink RBs available
the for LTE decreases,
CellAlgoSwitch. which reduces the
UlSchExtSwitch benefit provided by
parameter UL Multi-Cluster.
Uplink None Scheduling The number of

frequency uplink RBs available
selective for LTE decreases,
scheduling which reduces the
gain provided by
uplink frequency
selective scheduling.
Uplink short- CellUlschAlgo.In Scheduling The number of

interval SPS tvlOfUlSpsWith uplink RBs available
Skipping for LTE decreases,
which reduces the
benefit provided by
uplink short-interval
SPS to UEs.
SRS SRSCfg.SrsCfgIn Physical Channel As LTE must share

d Resource SRS resources with
Management NR, the LTE cell
triggers the
expansion of the
cell-specific SRS
subframes in
advance, which
prolongs the SRS
period of LTE UEs.
Uplink semi- SpsSchSwitch VoLTE The number of

persistent option of the uplink RBs available
scheduling CellAlgoSwitch. for LTE decreases,
UlSchSwitch which reduces the
parameter benefit provided by
uplink semi-
persistent
scheduling.

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation)
Downlink SpsSchSwitch VoLTE The number of

semi- option of the downlink RBs
persistent CellAlgoSwitch. available for LTE
scheduling DlSchSwitch decreases, which
parameter reduces the benefit
provided by
downlink semi-
persistent
scheduling.
TTI bundling TtiBundlingSwit VoLTE The number of

ch option of the uplink RBs available
CellAlgoSwitch. for LTE decreases.
UlSchSwitch Consequently, the
parameter maximum number of
UEs that can enter
the TTI bundling
state decreases.
Uplink RB UlVoipRbRsvSwi VoLTE It is not

reservation tch option of the recommended that
CellAlgoSwitch. uplink RB reservation
UlSchExtSwitch be enabled together
parameter with LTE FDD and
NR Flash Dynamic
Spectrum Sharing.
This is because
interference is
generated to voice
service UEs that
occupy the reserved
RBs in neighboring
LTE cells in cases
where reserved RBs
are configured in the
shared spectrum and
some of the shared
spectrum is occupied
by NR.
Uplink MU- UlVmimoSwitch MIMO The number of

MIMO option of the uplink RBs available
CellAlgoSwitch. for LTE decreases,
UlSchSwitch which increases the
parameter pairing success rate
of uplink MU-MIMO.
Consequently, the
BLER increases.

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation)
TM9 4T_TM9_ADAPT MIMO When an LTE cell is

adaptation ATION_SW configured with
option of the MBSFN subframes,
CellMimoParaCf TM9 adaptation
g.MimoSwitch does not take effect.
parameter
Downlink EmimoMuMimo eMIMO (FDD) The number of

MU-MIMO Switch and downlink RBs
4TxTM9MuMim available for LTE
oSwitch options decreases, which
of the increases the pairing
CellAlgoSwitch. success rate of
EmimoSwitch downlink MU-MIMO.
parameter Consequently, the
BLER increases.
UL CoMP CellAlgoSwitch. UL CoMP LTE UEs perform

UplinkCompSwi measurement in the
tch same manner as
that before LTE FDD
and NR Flash
Dynamic Spectrum
Sharing is enabled.
The LTE CRS
transmission avoids
the NR SSB, leading
to inaccurate LTE
RSRP measurement
results.
Consequently, the
number of cell edge
users (CEUs) in the
LTE cell decreases,
that is, the number
of UEs for which UL
CoMP takes effect
decreases.

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation)
DRX CellDrxPara.Drx DRX and The number of RBs

AlgSwitch Signaling Control available for LTE
decreases, leading to
a decrease in the
average number of
scheduling times. 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.
Dynamic CellAlgoSwitch. DRX and The number of RBs

DRX DynDrxSwitch Signaling Control available for LTE
a decrease in the
average number of
number of UEs that
enter DRX mode, as
well as the
frequency of UEs
DRX mode increase.
Intra-RAT CellAlgoSwitch. Intra-RAT If the PRB usage of

mobility load MlbAlgoSwitch Mobility Load LTE changes or the
balancing Balancing number of RBs
available for LTE
changes, the intra-
RAT MLB policy
changes.

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation)
LCS ENodeBAlgoSwi LCS The positioning

tch.LcsSwitch reference signal
(PRS) required for
positioning causes
interference to NR,
increasing the bit
error rate (BER) on
the NR side. As a
result, the
performance of NR
cells deteriorates.
Therefore, LTE FDD
and NR Flash
Dynamic Spectrum
Sharing should not
be enabled with this
function.
High speed Cell.HighSpeedF High Speed Downlink automatic

mobility lag Mobility frequency control
(AFC) of high speed
mobility requires the
SFN function to
achieve its optimal
benefits. However,
LTE FDD and NR
Flash Dynamic
Spectrum Sharing
cannot be enabled
together with the
SFN function. As a
result, when high
speed mobility is
enabled together
with LTE FDD and
NR Flash Dynamic
Spectrum Sharing,
the benefit produced
by downlink AFC
decreases.

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation)
Ultra high Cell.HighSpeedF High Speed Downlink AFC of

speed lag Mobility ultra high speed
mobility mobility requires the
SFN function to
achieve its optimal
benefits. However,
LTE FDD and NR
Flash Dynamic
Spectrum Sharing
cannot be enabled
together with the
SFN function. As a
result, when ultra
high speed mobility
is enabled together
with LTE FDD and
NR Flash Dynamic
Spectrum Sharing,
the benefit produced
by downlink AFC
decreases.

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation)
LTE guard Prb.DeployMod NB-IoT Basics ● For 3900 and

band e (FDD) 5900 series base
deployment stations, when
LTE FDD and NR
Flash Dynamic
Spectrum Sharing
is used together
with NB-IoT
deployed in LTE
guard band
mode, uplink and
downlink RBs are
reserved for NB-
IoT to reduce the
interference
between NB-IoT
and NR. For
details, see 3.1.3
Application
Scenarios of
Simultaneous
Use of Flash
Dynamic
Spectrum
Sharing and
Other Functions.
The RB
reservation
decreases the
spectrum
resources
available for the
NR cell, reducing
the NR cell
throughput.
● For DBS3900
LampSite and
DBS5900
LampSite, LTE
FDD and NR
Flash Dynamic
Spectrum Sharing
cannot be used
together with NB-
IoT deployed in
LTE guard band
mode.

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation)
Dynamic CellAlgoSwitch. Energy Dynamic voltage

voltage DynAdjVoltSwit Conservation adjustment does not
adjustment ch and Emission take effect when
Reduction enabled together
with LTE FDD and
NR Flash Dynamic
Spectrum Sharing, as
its triggering
conditions cannot be
met.
pRRU deep EnodebMpruEs. Energy For DBS3900

dormancy in MpruDormancy Conservation LampSite and
intelligent DlEarfcn and Emission DBS5900 LampSite,
mode Reduction when LTE FDD and
NR Flash Dynamic
Spectrum Sharing is
enabled together
with pRRU deep
dormancy in
intelligent mode, the
demodulation
performance of the
common PUCCH in
NR cells deteriorates.
DL CoMP Tm9JtSwitch DL CoMP (FDD) DL CoMP with TM9

with TM9 option of the does not take effect
CellAlgoSwitch. when used together
DlCompSwitch with LTE FDD and
parameter NR Flash Dynamic
Spectrum Sharing, as
the conditions for DL
CoMP with TM9 to
take effect cannot be
met.
eNodeB- CellAlgoSwitch.I ICIC When LTE FDD and

based nterfRandSwitc NR Flash Dynamic
interference h Spectrum Sharing is
randomizatio enabled, the amount
n of spectrum
resources available
for LTE decreases. As
a result, the benefits
provided by eNodeB-
based interference
randomization
decrease.

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation)
Uplink CellUlschAlgo.U ICIC When LTE FDD and

interference lRbAllocationStr NR Flash Dynamic
randomizatio ategy set to Spectrum Sharing is
n FS_INRANDOM_ enabled, the amount
ADAPTIVE of spectrum
resources available
for LTE decreases. As
a result, the benefits
provided by uplink
interference
randomization
decrease.
RAN sharing EnodeBSharing RAN Sharing When RAN sharing

with Mode.EnodeBSh with common carrier
common aringMode set is enabled together
carrier to with LTE FDD and
SHARED_FREQ NR Flash Dynamic
or Spectrum Sharing,
HYBRID_SHARE the number of
D available RBs for an
LTE operator is
calculated as follows:
(Total number of
RBs – Number of RBs
shared with NR) x
RB allocation
proportion
configured for the
operator.

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation)
Compact Cell.Customized Compact When LTE FDD and

bandwidth BandWidthCfgI Bandwidth NR Flash Dynamic
nd (FDD) Spectrum Sharing is
enabled, the
compact bandwidth
function supports
only the following
bandwidths:
● 9.6 MHz
● 9.8 MHz
● 14.6 MHz
● 14.8 MHz
● 17.5 MHz
● 19.6 MHz
● 19.8 MHz
When a compact
bandwidth of 9.6
MHz or 9.8 MHz is
used, the NR SSB
cannot be configured
due to the few
number of available
RBs. Therefore, it is
recommended that
the number of LTE
CRS ports (specified
by the
Cell.CrsPortNum
parameter) be set to
1 or 2 for LTE cells.
This configuration
suggestion applies
only to SA
networking.
This impact
relationship exists
only when 3900 or
5900 series base
stations are used.
Uplink data NSA_DC_UL_PA NSA Networking If LTE key event

transmission TH_SELECTION_ based on EPC assurance is enabled,
path SW option of the uplink data
selection NsaDcMgmtConf transmission path
ig.NsaDcAlgoSw selection does not
itch parameter take effect.

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation)
eMTC EMTC_SWITCH eMTC eMTC introduction

introduction option of the significantly
CellEmtcAlgo.E decreases the
mtcAlgoSwitch resources available
parameter for the NR cell.
When LTE FDD and
NR Flash Dynamic
Spectrum Sharing is
enabled together
with eMTC
introduction, the NR
SSB must be
deployed at the
lower end of the
frequency domain to
avoid conflicts with
eMTC RBs and
ensure the normal
access of NR UEs.
LTE FDD and NR
Flash Dynamic
Spectrum Sharing
can work with eMTC
introduction only
when the UBBPg is
used.
Inter-carrier INTER_CARRIER Massive MIMO When LTE FDD and

power _PWR_SHR_SWI (FDD) NR Flash Dynamic
sharing TCH option of Spectrum Sharing is
the enabled, the power
SectorSplitGrou that can be shared
p.IntelligentBea between carriers
mSchSwitch decreases.
parameter
LTE FDD and LTE_NR_DYN_P LTE and NR When LTE FDD and
NR Flash OWER_SHARIN Power Sharing NR Flash Dynamic
Dynamic G_SW option of Power Sharing is
Power the enabled, the power
Sharing CellDynPowerS sharing capability of
haring.Dynamic LTE spectrum
PowerSharingS sharing cells is lower
witch parameter than that of
common cells. As a
result, the power
sharing benefits
decrease.

(2021-12-30)
SingleRAN
● Impacted functions on the NR side

Function Function Switch Reference (5G Description
Name RAN Feature
Documentation
)
Downlink INTRA_FR_INTE Carrier If downlink intra-FR

intra-FR R_BAND_CA_SW Aggregation inter-band CA is
inter-band option of the enabled after LTE
CA NRDUCellAlgoS FDD and NR Flash
witch.CaAlgoSw Dynamic Spectrum
itch parameter Sharing is enabled,
the related
configuration
requirements
described in 3.1.3
Application
Scenarios of
Simultaneous Use
of Flash Dynamic
Spectrum Sharing
and Other
Functions must be
met. Otherwise,
downlink intra-FR
inter-band CA does
not take effect, or
the NR cell will go
out of service.
When LTE FDD and
NR Flash Dynamic
Spectrum Sharing is
enabled for a cell,
the cell is not
configured as an
SCell for a UE if the
UE does not support
LTE CRS rate
matching in the
operating band of
the cell.
Downlink None Power Control When LTE FDD and

Power NR Flash Dynamic
Control Spectrum Sharing is
enabled, the
downlink power
cannot be increased.

(2021-12-30)
SingleRAN

Name RAN Feature
Documentation
)
RAN sharing SHARED_FREQ Multi-Operator When RAN sharing

with option of the Sharing with common carrier
common gNBSharingMod is enabled together
carrier e.gNBMultiOpS with LTE FDD and
haringMode NR Flash Dynamic
parameter Spectrum Sharing,
the number of
available RBs for an
NR operator is
(Total number of
shared with LTE) x
RB allocation
proportion
configured for the
operator.
Operator- RB_DYNAMIC_S Multi-Operator When both the

specific RB HARING_SW Sharing function of operator-
management and specific limitation on
MAX_RB_LIMIT_ the maximum
SW options of number of available
the RBs and LTE FDD
NRDUCellAlgoS and NR Flash
witch.RanSharin Dynamic Spectrum
gAlgoSwitch Sharing are enabled,
parameter the maximum
number of RBs
available for an
operator is
calculated using the
following formula:
Maximum number
of RBs available for
an operator =
Available bandwidth
of the NR cell (not
the bandwidth
configured for the
NR cell) x Maximum
percentage of
downlink RBs.

(2021-12-30)
SingleRAN

Name RAN Feature
Documentation
)
Uplink RB UL_RB_RSV_SW VoNR It is not

reservation option of the recommended that
NRCellAlgoSwit uplink RB reservation
ch.VonrSwitch be enabled together
parameter with LTE FDD and
NR Flash Dynamic
Spectrum Sharing.
This is because if the
reserved RBs are
configured in the
shared spectrum and
some of the shared
by LTE, interference
will be generated to
voice UEs that
occupy the reserved
RBs in neighboring
NR cells.
NR DU cell RB_DYNAMIC_C Network Slicing When both the NR

resource ONTROL_SW DU cell resource
management option of the management
between NRDUCellAlgoS between network
network witch.NetworkS slices function and
slices liceAlgoSwitch LTE FDD and NR
parameter Flash Dynamic
Spectrum Sharing
are enabled, the
number of RBs
available for a
network slice group
is calculated using
the following
formula: Number of
RBs available for a
network slice group
= Available
bandwidth of the NR
cell (not the
bandwidth
configured for the
NR cell) x
Percentage of RBs
configured for the
network slice group.

(2021-12-30)
SingleRAN

Name RAN Feature
Documentation
)
Super uplink FLEX_SUPER_UP Super Uplink When LTE FDD and

with SUL and LINK_SW option NR Flash Dynamic
NR FDD co- of the Spectrum Sharing is
deployment NRDUCellAlgoS enabled together
witch.SuperUpli with super uplink
nkSwitch with SUL and NR
parameter FDD co-deployment,
the amount of uplink
spectrum resources
that can be allocated
to implement super
uplink decreases if
the LTE FDD or NR
traffic volume
increases. As a result,
the uplink
throughput of the
SUL carrier
decreases.
Super uplink with
SUL and NR FDD co-
deployment cannot
take effect in an LTE
cell when LTE FDD
and NR Flash
Dynamic Spectrum
Sharing is enabled
together with one of
the following
functions: uplink
semi-persistent
scheduling, eMTC, or
compact bandwidth.
This is because these
functions periodically
or continuously
occupy spectrum
resources.
DC DC_COMPONEN Scheduling When LTE FDD and

component T_RATEMATCH_ NR Flash Dynamic
rate SW option of the Spectrum Sharing is
matching NRDUCellPdsch. enabled,
RateMatchSwitc configurations for
h parameter DC component rate
matching will
become invalid.

(2021-12-30)
SingleRAN

Name RAN Feature
Documentation
)
PDCCH rate PDCCH_RATEM Scheduling When PDCCH rate

matching ATCH_SW matching is enabled
option of the together with LTE
NRDUCellPdsch. FDD and NR Flash
RateMatchSwitc Dynamic Spectrum
h parameter Sharing, the number
of downlink RBs
available for LTE
decreases.
Load-based NRDUCellDlSch. Scheduling When basic

adaptive DlSchPolicy set functions of LTE FDD
downlink to ADAPTIVE and NR Flash
scheduling Dynamic Spectrum
Sharing take effect,
the number of
available downlink
RBs in an NR cell
decreases. As a
result, the downlink
PRB usage may be
lower than the
downlink scheduling
heavy-load PRB
usage threshold for
triggering the load-
based adaptive
downlink scheduling
function, reducing
the scenarios where
the load-based
adaptive downlink
scheduling function
can provide benefits.
RB allocation NRDUCellDlSch Scheduling When RB allocation

for downlink Res.DlExpOptRb for downlink
experience IncreasePct set experience
optimization to a non-zero optimization takes
value effect together with
LTE FDD and NR
Flash Dynamic
Spectrum Sharing,
the capacity on the
LTE side decreases.

(2021-12-30)
SingleRAN

Name RAN Feature
Documentation
)
High-speed NRDUCell.HighS High Speed When High-speed

Railway peedFlag Mobility Railway Superior
Superior Experience and LTE
Experience FDD and NR Flash
Dynamic Spectrum
Sharing are both
enabled, the high
moving speeds of
UEs in high-speed
cells adversely affect
the performance of
flash dynamic
spectrum sharing
UEs. In addition,
flash dynamic
spectrum sharing
UEs do not support
two downlink
additional DMRS
positions, affecting
the PDSCH
demodulation
performance of UEs
in high-speed cells.
Therefore, it is
recommended that
these two functions
not be used together.
Uplink UL_FALLBACK_T NSA Networking If LTE key event

fallback to O_LTE_SWITCH based on EPC assurance is enabled,
LTE option of the uplink fallback to
NRCellNsaDcCo LTE does not take
nfig.NsaDcAlgo effect.
Switch
parameter
Uplink data NSA_DC_UL_PAT NSA Networking If LTE key event

transmission H_SELECTION_S based on EPC assurance is enabled,
path W option of the uplink data
selection NRCellNsaDcCo transmission path
nfig.NsaDcAlgo selection does not
Switch take effect.
parameter

(2021-12-30)
SingleRAN

Name RAN Feature
Documentation
)
Compact NRDUCell.Custo Scalable When compact

bandwidth mizedBwConfigI Bandwidth bandwidth is
nd set to enabled together
CONFIG with LTE FDD and
NR Flash Dynamic
Spectrum Sharing
and a compact
bandwidth of 9.6
MHz or 9.8 MHz is
used, the NR SSB
cannot be configured
due to the few
number of available
RBs. Therefore, it is
recommended that
the number of CRS
ports (specified by
the
Cell.CrsPortNum
parameter) be set to
1 or 2 for the LTE
cell. This
configuration
suggestion applies
only to SA
networking.
This impact
relationship exists
only when 3900 or
5900 series base
stations are used.

(2021-12-30)
SingleRAN

Name RAN Feature
Documentation
)
UE UE_BW_ADAPTI Scalable When LTE FDD and

bandwidth VE_SW option of Bandwidth NR Flash Dynamic
adaptation the Spectrum Sharing is
NRDUCellBwp.B enabled with UE
wpConfigSwitch bandwidth
parameter adaptation:
● The frequency-
domain positions
of the PRACH and
PUCCH are
confined to the
bandwidth range
specified by the
NRDUCellBwp.Ul
MinCarrierBw
parameter, and
the frequency-
domain position
of PDCCH
Coreset0 is
confined to the
bandwidth range
specified by the
NRDUCellBwp.Dl
MinCarrierBw
parameter.
● If the
NRDUCell.Custo
mizedUlBandwid
th parameter is
set to
CELL_BW_17DOT
5M, the
NRDUCellBwp.Ul
MinCarrierBw
parameter must
be set to 10M.
● If the
NRDUCell.Custo
mizedDlBandwid
th parameter is
set to
CELL_BW_17DOT
5M, the
NRDUCellBwp.Dl
MinCarrierBw

(2021-12-30)
SingleRAN

Name RAN Feature
Documentation
)
parameter must
be set to 10M.
Unbalanced NRDUCellCover Cell When the function

transmit age.TransmitPo Management of unbalanced
power werOffsetChn0, transmit power
configuration NRDUCellCover configurations
s between age.TransmitPo between channels is
channels werOffsetChn1, enabled together
NRDUCellCover with LTE FDD and
age.TransmitPo NR Flash Dynamic
werOffsetChn2, Spectrum Sharing,
or and the spectrum
NRDUCellCover power sharing mode
age.TransmitPo is used, the number
werOffsetChn3 of downlink
set to a non-zero available RBs in the
value NR cell decreases.
Energy FLEX_FREQ_SCH Energy When LTE FDD and

saving based _ENERGY_SAVIN Conservation NR Flash Dynamic
on flexible G_SW option of and Emission Spectrum Sharing
frequency- the Reduction takes effect together
domain NRDUCellAlgoS with energy saving
scheduling witch.PowerSavi based on flexible
ngSwitch frequency-domain
parameter scheduling, the gains
of energy saving
based on flexible
frequency-domain
scheduling decrease,
and the capacity on
the LTE side
decreases.
NR inter- NR_DYN_POWE NR Inter-Carrier When LTE FDD and

carrier R_SHARING_SW Dynamic Power NR Flash Dynamic
dynamic option of the Sharing Spectrum Sharing is
power NRDUCellAlgoS enabled, the power
sharing witch.DynPower that can be shared
SharingSwitch between NR carriers
parameter decreases.

(2021-12-30)
SingleRAN

Name RAN Feature
Documentation
)
Sharing NRDUCellAlgoS sharing capability of
witch.DynPower NR spectrum sharing
SharingSwitch cells is lower than
parameter that of common
cells. As a result, the
power sharing
benefits decrease.
3.3 Requirements
3.3.1 Licenses
This function requires both feature and capacity licenses. Table 3-16 and Table
3-17 list the required feature licenses. Table 3-18 and Table 3-19 list the required
capacity licenses.
Table 3-16 Feature licenses (for 3900 and 5900 series base stations)
RAT Feature Feature Name Model License NE Sales
ID Control Item Unit
LTE MRFD-1 LTE FDD and LT1S0L LTE FDD and eNodeB per
FDD 60222 NR Flash FNSS00 NR Flash Cell
Dynamic Dynamic
Spectrum Spectrum
Sharing (LTE Sharing(LTE
FDD) FDD)
NR MRFD-1 LTE FDD and NR0S0 LTE FDD and gNodeB per
60262 NR Flash 0FNSS0 NR Flash Cell
Dynamic 0 Dynamic
Spectrum Spectrum
Sharing (NR) Sharing (NR)

(2021-12-30)
SingleRAN
Table 3-17 Feature licenses (for DBS3900 LampSite and DBS5900 LampSite)
LTE MRFD-1 LTE FDD and LT1SDY LTE FDD and eNodeB per
FDD 60222 NR Flash NSHR0 NR Flash Carrie
Dynamic 0 Dynamic r per
Spectrum Spectrum pRRU
Sharing (LTE Sharing
FDD) (LampSite
FDD)
NR MRFD-1 LTE FDD and NR0SD LTE FDD and gNodeB per
60262 NR Flash YNSHR NR Flash Carrie
Dynamic 00 Dynamic r per
Spectrum Spectrum pRRU
Sharing (NR) Sharing
(LampSite NR)
Table 3-18 Capacity licenses (for 3900 and 5900 series base stations)
RAT Model License Control Item NE Sales
Unit
LTE FDD LT1SRFSPCS0 RF Spectrum Sharing eNodeB per Band

0 License(FDD) per RU
LTE FDD LT1S5000RFSS Spectrum Sharing License eNodeB per Band

for 5000 Series RF per RU
Module(FDD)
NR NR0S0RFSSL0 RF Spectrum Sharing gNodeB per Band

0 License (NR) per RU
NR NR0SSSLRFM Spectrum Sharing License gNodeB per Band

00 for 5000 Series RF Module per RU
(NR)
Table 3-19 Capacity licenses (for DBS3900 LampSite and DBS5900 LampSite)
Unit
LTE FDD LT1SFDSPCS3 Spectrum Sharing License eNodeB per Band

0 for LampSite pRRU (LTE per pRRU
FDD)
LTE FDD LT1SFDSPCS5 Spectrum Sharing License eNodeB per Band

0 for 5000 Series LampSite per pRRU
pRRU(LTE FDD)

(2021-12-30)
SingleRAN

Unit
NR NR0SSPECTT0 Spectrum Sharing License gNodeB per Band

0 for LampSite pRRU (NR) per pRRU
NR NR0SSPECTT5 Spectrum Sharing License gNodeB per Band

0 for 5000 Series LampSite per pRRU
pRRU (NR)
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
capacity licenses.
Customers must purchase the Spectrum Sharing License for 5000 Series LampSite
pRRU when 5000 series LampSite pRRUs are used. When non-5000 series
LampSite pRRUs are used, customers must purchase the Spectrum Sharing License
for LampSite pRRU. When 5000 series LampSite pRRUs and non-5000 series
LampSite pRRUs are both used, customers must purchase both capacity 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
● Prerequisite functions on the LTE side
Name (eRAN Feature
Documentation
)
Normal CP Cell.UlCyclicPref Extended CP Set this parameter to

ix NORMAL_CP.
PRACH RACHCfg.PrachF Random Access Set this parameter to

frequency reqOffsetStrate Control FULLY_AUTOMATIC.
offset gy
strategy

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation
)
CSI-RS CellCsiRsParaCf Dedicated This function is

Period g.CsiRsPeriod Carrier for TM9 required only when
the
CellCsiRsParaCfg.Csi
RsSwitch parameter
is set to FIXED_CFG
or ADAPTIVE_CFG.
● If the NR SSB
period (specified
by the NR
parameter
NRDUCell.SsbPer
iod) is greater
than or equal to
MS20(20),
CellCsiRsParaCfg.
CsiRsPeriod must
be set to ms10 or
a larger value.
● If the NR SSB
period is less than
or equal to
MS10(10),
CellCsiRsParaCfg.
CsiRsPeriod must
be set to ms20 or
a larger value.
PHICH PHICHCfg.Phich Physical Channel LTE FDD and NR

resource Resource Resource Flash Dynamic
Management Spectrum Sharing
requires this function
only when the cell
bandwidth is 10
MHz. When required,
set this parameter to
ONE_SIXTH, HALF,
or ONE.
SRS SRSCfg.SrsCfgIn Physical Channel Set this parameter to

configuration d Resource BOOLEAN_TRUE.
indicator Management

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation
)
SRS SRSCfg.SrsSubfr Physical Channel When automatic SRS

subframe ameCfg Resource neighboring cell
configuration Management measurement is
enabled (the
NCellSrsMeasPara.S
rsAutoNCellMeasS-
witch parameter set
to ON), the
SRSCfg.SrsSubframe
Cfg parameter must
be set to SC2.
When automatic SRS
neighboring cell
measurement is
disabled, the
SRSCfg.SrsSubframe
Cfg parameter must
be set to SC3, SC7,
SC14, or SC0.
Cell-specific SrsSubframeRec Physical Channel Select this option of

SRS fSwitch option Resource this parameter only
subframe of the Management when the
reconfigurati CellAlgoSwitch. LTE_UE_SRS_NOT_C
on SrsAlgoSwitch ONFIG_SW option
parameter of the
SpectrumCloud.Spe
ctrumCloudEnhSwit
ch parameter is
deselected.
Uplink CellUlschAlgo.A Scheduling Set this parameter to

adaptive daptHarqSwitch ADAPTIVE_HARQ_S
HARQ W_ON or
ADAPTIVE_HARQ_S
W_SEMI_ON.
● Prerequisite functions on the NR side

(2021-12-30)
SingleRAN

Name RAN Feature
Documentation
)
Basic None Scheduling The

functions of NRDUCellPdsch.DlD
downlink mrsMaxLength
scheduling parameter must be
set to 1SYMBOL.
Search Space NRDUCellPdcch. Channel The

Zero SearchSpaceZer Management NRDUCellPdcch.Sea
o rchSpaceZero
parameter must be
set to DEFAULT.
Configurable NRDUCell.SsbTi Channel The

time-domain mePos Management NRDUCell.SsbTimeP
position in os parameter must
the single be set to DEFAULT.
SSB beam
case
Mutually Exclusive Functions

● Mutually exclusive functions on the LTE side
Function Name Function Switch Reference (eRAN
Feature
Documentation)
SFN Cell Cell.MultiRruCellMode set SFN

to SFN and there is more
than one set of sector
equipment, or to
MPRU_AGGREGATION and
there is more than one
sector equipment group
Inter-frequency CellAlgoSwitch.InterFreqDir High Speed Mobility

directional handover ectHoSwitch
Low-speed UE CellAlgoSwitch.LowSpeedIn High Speed Mobility
outmigration terFreqHoSwitch
GSM and LTE FDD GLDynSpectrumShareS- GSM and LTE FDD
Dynamic Spectrum witch option of the Dynamic Spectrum
Sharing CellAlgoSwitch.DynSpectru Sharing
mShareSwitch parameter

(2021-12-30)
SingleRAN

Feature
Documentation)
GSM and LTE SpectrumCloud.SpectrumCl GSM and LTE

Spectrum oudSwitch set to Spectrum
Concurrency GL_SPECTRUM_CONCURRE Concurrency
NCY
Flexible Bandwidth DdCellGroup.DdBandwidth Flexible Bandwidth

Based on Overlap based on Overlap
Carriers Carriers (FDD)
GSM and LTE Zero GLZeroBufferZoneSwitch GSM and LTE Zero
Bufferzone option of the Bufferzone
CellAlgoSwitch.DynSpectru
mShareSwitch parameter
GSM and LTE Buffer AvoidGeranInterfSwitch GSM and LTE Buffer
Zone Optimization option of the Zone Optimization
CellAlgoSwitch.AvoidInterf
Switch parameter
UL Refarming Zero AvoidUtranInterfSwitch UL Refarming Zero
Switch parameter
UMTS and LTE Zero UMTS_LTE_ZERO_BUFFER_Z UMTS and LTE Zero
Bufferzone ONE_SW option of the Bufferzone
ULZeroBufferZone.ZeroBufZ
oneSwitch parameter
UMTS and LTE SpectrumCloud.SpectrumCl UMTS and LTE
Spectrum Sharing oudSwitch set to Spectrum Sharing
UL_SPECTRUM_SHARING
UMTS and LTE SpectrumCloud.SpectrumCl UMTS and LTE

Spectrum Sharing oudSwitch set to Spectrum Sharing
Based on DC-HSDPA DC_HSDPA_BASED_UL_SPEC Based on DC-HSDPA
TRUM_SHR
CDMA and LTE Zero AvoidCDMAInterfSwitch CDMA and LTE Zero

Switch parameter
UL CRA UL_COORD_RES_ALLOC_SW Uplink Coordinated
ITCH option of the Scheduling
UlCsAlgoPara.UlCsSw
parameter

(2021-12-30)
SingleRAN

Feature
Documentation)
UL CPC UL_COORD_PC_SWITCH Uplink Coordinated

option of the Scheduling
UlCsAlgoPara.UlCsSw
parameter
Coordinated CellCspcPara.CellCspcSwitc CSPC

Scheduling based h
Power Control
PUSCH FH CellUlschAlgo.UlHoppingTy None

pe
LTE flexible CellLteFlexBw.LteFlexBwSw None
bandwidth itch
Adaptive Inter-Cell Activated using the ACT Adaptive ICIC
Interference AICIC command on the
Coordination eCoordinator
Out of Band Relay OutOfBandRelaySwitch Relay

option of the
CellAlgoSwitch.RelaySwitch
parameter
In-Band Relay InBandRelayDeNbSwitch, Relay

InBandRelayReNbSwitch,
and InBandRelayDistantDe-
ploySw options of the
parameter
Manual RB blocking CellRbReserve.RbRsvMode Scheduling

set to RB_MASKING or
RB_MASKING_WITH_SRS
Cell radius greater Cell.CellRadius Extended Cell Range

than 100 km
Superior Uplink CellAlgoExtSwitch.UlCovera Superior Uplink

Coverage geEnhancementSw Coverage (FDD)
eMBMS CellMBMSCfg.MBMSSwitch eMBMS
Virtual 4T4R Virtual4T4RSwitch option of Virtual 4T4R (FDD)
the
CellAlgoSwitch.EmimoSwit
ch parameter

(2021-12-30)
SingleRAN

Feature
Documentation)
UMTS and LTE UMTS_LTE_DYN_POWER_SH UMTS and LTE

Dynamic Power ARING_SW option of the Dynamic Power
Sharing CellDynPowerShar- Sharing
ing.DynamicPowerShar-
ingSwitch parameter
Cross LTE Carriers LTE_DYN_POWER_SHARING Dynamic Power
Dynamic Power _SW option of the Sharing Between LTE
Sharing CellDynPowerShar- Carriers
ingSwitch parameter
Extreme power LTE_EXTREME_POWER_SHA Dynamic Power
sharing RING_SW option of the Sharing Between LTE
CellDynPowerShar- Carriers
ingSwitch parameter
GSM and LTE CellAlgoSwitch.GLPwrShare GSM and LTE
Dynamic Power Dynamic Power
Sharing Sharing
Super Combined Cell SuperCombCellSwitch Super Combined Cell
option of the (FDD)
CellAlgoSwitch.SfnAlgoSwit
ch parameter
RF channel dynamic RF_CHN_DYN_MUTING_SW Energy Conservation
muting option of the and Emission
CellRfChnDynMut- Reduction
ing.RfChnDynMutingAlgoS-
witch parameter
Dynamic TDM eICIC CellAlgoSwitch.EicicSwitch TDM eICIC (FDD)
Paging message PagingInterfRandSwitch ICIC
interference option of the
randomization CellAlgoSwitch.DlSchSwitc
h parameter
Short TTI SHORT_TTI_SW option of Short TTI (FDD)
the
CellShortTtiAlgo.SttiAlgoS
witch parameter
Zero Guard Band CONTIG_INTRA_BAND_CAR Seamless Intra-Band
Between Contiguous R_SW option of the Carrier Joining (FDD)
Intra-Band Carriers ContigIntraBand-
Carr.ContigIntraBand-
CarrSw parameter

(2021-12-30)
SingleRAN

Feature
Documentation)
LTE in-band CellRbReserve.RbRsvMode NB-IoT Basics (FDD)

deployment set to NB_RESERVED or
NB_DEPLOYMENT
Uplink PUSCH RB CellRbReserve.RbRsvMode PTT

reservation for set to MCPTT_RB_RESERVED
MCPTT voice
services
TM4 and TM6 CL_TM_ADAPTATION_OPT_ Low-Band Booster

Adaptation SW option of the
CellMimoParaCfg.MimoSwi
tch parameter
Intelligent PIM PIM_INTERF_SMART_AVOID Interference
interference _SW option of the Detection and
avoidance PimInterfSmartA- Suppression
void.PimAlgoSwitch
parameter
Beam number BEAM_NUM_ADJ_SWITCH Massive MIMO

adjustment option of the (FDD)
SectorSplitGroup.SectorSpli
tSwitch parameter, and the
Cell.TxRxMode parameter
set to 32T32R
Downlink turbo pilot SectorSplitGroup.TurboPilot Massive MIMO

PowerOffset set to a non- (FDD)
zero value, and
Cell.TxRxMode set to 8T8R
or 32T32R
Compact bandwidth Cell.CustomizedBandWidth Compact Bandwidth

CfgInd set to CFG, and (FDD)
Cell.TxRxMode set to
32T32R
Cell Power Limita PDSCHCfg.EmfPowerLimitS On-Demand TX

witch set to ON, and Power Allocation
PDSCHCfg.CellPowerLimit Under EME
set to a value other than 0
PUCCH Flexible PucchFlexCfgSwitch option Physical Channel

Configurationb of the Resource
CellAlgoSwitch.PucchAlgoS Management
witch parameter
ePDCCH CellPdcchAlgo.EpdcchAlgoS Physical Channel
witch Resource
Management

(2021-12-30)
SingleRAN

Feature
Documentation)
Extended PHICH PHICHCfg.PhichDuration Physical Channel

Resource
Management
Uplink data NSA_DC_UL_PATH_SELECTI NSA Networking
transmission path ON_SW option of the based on EPC
selectionc NsaDcMgmtConfig.NsaDcAl
goSwitch parameter
Unequal downlink PDSCHCfg.TxPowerOffsetA Smart 8T8R (FDD)
port powerd nt2
PDSCHCfg.TxPowerOffsetA
nt3
Uplink SRS-based CellUlschAlgo.UlSrsFreqSel Smart 8T8R (FDD)
frequency selective SchSinrThld set to a value
schedulingd other than 255
a: This 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
settings of the CellRbReserve.RbRsvMode, CellRbReserve.RbRsvType,
CellRbReserve.RbRsvStartIndex, and CellRbReserve.RbRsvEndIndex
parameters can be used as an alternative to the flexible PUCCH
configuration function.
c: This mutually exclusive relationship exists only when the
SpectrumCloud.SpectrumCloudEnhSwitch parameter is selected.
d: This mutually exclusive relationship exists only when HDSS based on
Asymmetric Beam is enabled.
● Mutually exclusive functions on the NR side
Function Function Switch Reference (5G RAN

Name Feature
Documentation)
PUCCH RB PUCCH_RBRES_ADAPTIVE_SWITCH Channel

adaptation option of the Management
NRDUCellPucch.PucchAlgoSwitch
parameter
PDCCH UE_PDCCH_SYM_NUM_ADAPT_SW Channel

symbol option of the Management
number NRDUCellPdcch.PdcchAlgoExtSwit
adaptation ch parameter
SSB beam NRDUCellCsirs.SsbBeamSwitching- Channel
switching Mode set to MAC_CE_MODE Management

(2021-12-30)
SingleRAN

Name Feature
Documentation)
SRS COMMON_PUCCH_AVOID_SRS_SW Channel

transmission option of the Management
using NRDUCellSrs.SrsAlgoSwitch
common parameter
PUCCH
resources
R16 Type2 R16_TYPE2_SW option of the None

NRDUCellPdschPre-
code.DlCodebookTypeSwitch
parameter
Configuratio NRDUCellPdcch.MaxCommonPdcc Channel

n of the hAggLvl set to AGGLVL16 Management
maximum
aggregation
level for the
common
PDCCH
Spectral- INTER_FREQ_CONNECTED_MLB_S Mobility Load

efficiency- W option of the Balancing
based NRCellAlgoSwitch.MlbAlgoSwitch
connected parameter, and the
mode MLB NRCellMlb.MlbTriggerMode
parameter set to
SPEC_EFF_BASED_USER_NUM
Intra-base- INTRA_GNB_DL_JT_SW option of CoMP

station DL the
CoMP NRDUCellAlgoSwitch.CompSwitch
parameter
Cell NRDUCell.NrDuCellNetworking- Cell Combination

Combination Mode set to
HYPER_CELL_COMBINE_MODE
Inter-base- INTER_GNB_DL_JT_SW option of None

station the
downlink NRDUCellAlgoSwitch.CompSwitch
joint parameter
transmission
Extended NRDUCell.CellRadius Extended Cell Range

Cell Range
Hyper Cell NRDUCell.NrDuCellNetworking- Hyper Cell

Mode set to HYPER_CELL

(2021-12-30)
SingleRAN

Name Feature
Documentation)
Compact NRDUCell.CustomizedBwConfigInd Scalable Bandwidth

bandwidth set to CONFIG, and
NRDUCellTrp.TxRxMode set to
32T32R
Rate- PDCCH_NO_PATTERN_RATE_MATC Scheduling

matching- H_SW option of the
pattern- NRDUCellPdcch.PdcchAlgoSwitch
configuration parameter
-free PDCCH
rate
matching
Intelligent PIM_INTERF_SMART_AVOID_SW Interference

PIM option of the NRDUCellPimIntr- Avoidance
interference fAvd.PimAlgoSwitch parameter
avoidance
Basic None Scheduling

functions of
downlink
schedulinga
3D coverage NRDUFddCellTrpBeam.CoverageSc Beam Management

patternb enario
RF channel RF_SHUTDOWN_SW option of the Energy Conservation

intelligent NRDUCellAlgoSwitch.PowerSaving and Emission
shutdownc Switch parameter Reduction
Unbalanced NRDUCellCoverage.TransmitPower Cell Management

transmit OffsetChn0,
power NRDUCellCoverage.TransmitPower
configuration OffsetChn1,
s between NRDUCellCoverage.TransmitPower
channelsd OffsetChn2,
NRDUCellCoverage.TransmitPower
OffsetChn3,
OffsetChn4,
OffsetChn5,
OffsetChn6 or
OffsetChn7 set to a non-zero value

(2021-12-30)
SingleRAN

Name Feature
Documentation)
Energy FLEX_FREQ_SCH_ENERGY_SAVING_ Energy Conservation

saving based SW option of the and Emission
on flexible NRDUCellAlgoSwitch.PowerSaving Reduction
frequency- Switch parameter
domain
schedulinge
a: LTE FDD and NR Flash Dynamic Spectrum Sharing is mutually exclusive

with the NRDUCellPdsch.DlAdditionalDmrsPos parameter (set to POS2)
in the basic functions of downlink scheduling.
b: When both LTE FDD and NR Flash Dynamic Spectrum Sharing and the
SSB rate matching function (controlled by the SSB_RATEMATCH_SW
option of the NRDUCellPdsch.RateMatchSwitch parameter) are enabled,
the NRDUFddCellTrpBeam.CoverageScenario parameter must be set to
DEFAULT. When the SSB rate matching function is not enabled, the
NRDUFddCellTrpBeam.CoverageScenario parameter can be set to
DEFAULT or SCENARIO_201 for 2T2R, 2T4R, 4T4R cells, and can be set to
DEFAULT (Only two SSB beams take effect in 32T32R cells),
SCENARIO_201, SCENARIO_202, SCENARIO_210, or SCENARIO_220 for
8T8R or 32T32R cells.
c: This mutually exclusive relationship exists only when the cell TX/RX mode
is 8T8R.
d: This mutually exclusive relationship exists only when HDSS based on
Asymmetric Beam is enabled.
e: This mutually exclusive relationship exists only when the PSD adaptation
function is enabled.
3.3.3 Hardware
Huawei devices (including the eNodeB and gNodeB) must be used on the radio
access network.
Base Station Models

● LTE
– 3900 and 5900 series base stations. 3900 series base stations must be
configured with the BBU3910, and 5900 series base stations must be
configured with the BBU5900 or BBU5900A.
– DBS3900 LampSite and DBS5900 LampSite. DBS3900 LampSite must be
configured with the BBU3910, and DBS5900 LampSite must be
configured with the BBU5900. These base station types do not support
HDSS based on Asymmetric Beam.
● NR
– 3900 and 5900 series base stations. 3900 series base stations must be

(2021-12-30)
SingleRAN
– DBS3900 LampSite and DBS5900 LampSite. DBS3900 LampSite must be

configured with the BBU3910, and DBS5900 LampSite must be
configured with the BBU5900. These base station types do not support
HDSS based on Asymmetric Beam.
Boards
● LTE
When the cell TX/RX mode is 2T2R, 2T4R, or 4T4R, only the UBBPd, UBBPe,
and UBBPg support this function. Table 3-20 lists the cell number
specifications of different baseband processing units after this function is
enabled. When the cell bandwidth is 17.5 MHz, only the UBBPe and UBBPg
support this function. For main control boards, only the UMPTb, UMPTe,
UMPTg, and UMPTga support this function.
When the cell TX/RX mode is 8T8R, only the UBBPe4, UBBPe6, UBBPe18, and
UBBPg support this function. When HDSS based on Asymmetric Beam is not
enabled, the cell number specifications of the baseband processing unit are
the same as those before this function is enabled. When HDSS based on
Asymmetric Beam is enabled, the cell number specifications of different
baseband processing units are listed in Table 3-21. For main control boards,
only the UMPTe, UMPTg, and UMPTga support this function.
When the cell TX/RX mode is 32T32R, only the UBBPg2a and UBBP boards of
later versions support this function. The cell number specifications of these
baseband processing units are the same as those before this function is
enabled. For main control boards, only the UMPTe, UMPTg, and UMPTga
support this function.
● NR
When the cell TX/RX mode is 2T2R, 2T4R, or 4T4R, only the UBBPg1,
UBBPg1a, UBBPg2, UBBPg2a, UBBPg3, and UBBPg3b support this function.
The cell number specifications of these baseband processing units are the
same as those before this function is enabled. For main control boards, only
the UMPTe, UMPTg, and UMPTga support this function.
When the cell TX/RX mode is 8T8R, only the UBBPg supports this function.
The cell number specifications of the baseband processing unit are the same
as those before this function is enabled. For main control boards, only the
UMPTe, UMPTg, and UMPTga support this function.

(2021-12-30)
SingleRAN
Table 3-20 Cell number specifications of LTE baseband processing units (with
HDSS based on Asymmetric Beam disabled)
Working Baseband Supported Cell Supported Spectrum
Mode Processing Number Sharing Cell Number
Unit Model Specifications Specifications
(Compared with
That Before This
Function Is Enabled)
LTE FDD or UBBPd5 Decrease or remain A maximum of three

LMa unchanged cells can be enabled
The cell number with LTE FDD and NR
specifications decrease Flash Dynamic
from six (2T2R) cells Spectrum Sharingb.
to three cells, or
remain three (2T4R or
4T4R) cells.
LTE FDD or UBBPd6 Decrease A maximum of three

LM The cell number cells can be enabled
specifications decrease with LTE FDD and NR
from six (2T2R, 2T4R, Flash Dynamic
or 4T4R) cells to three Spectrum Sharing.
cells.
LTE FDD or UBBPe1 Remain unchanged All three cells can be

LM Three (2T2R) cells enabled with LTE FDD
and NR Flash
Dynamic Spectrum
Sharing.
LTE FDD or UBBPe2 Remain unchanged All three cells can be

LM Three (2T2R, 2T4R or enabled with LTE FDD
4T4R) cells and NR Flash
Dynamic Spectrum
Sharing.
LTE FDD or UBBPe3 Remain unchanged A maximum of three

LM Six (2T2R) cells, or cells can be enabled
three (2T4R or 4T4R) with LTE FDD and NR
cells Flash Dynamic
Spectrum Sharing,
while the rest are
common cells.
LTE FDD or UBBPe4/ Remain unchanged A maximum of three

LM UBBPe18 Six (2T2R, 2T4R, or cells can be enabled
4T4R) cells, or three with LTE FDD and NR
(8T8R) cells Flash Dynamic
Spectrum Sharing,
while the rest are
common cells.

(2021-12-30)
SingleRAN

(Compared with
That Before This
LTE FDD, LM, UBBPe5 Remain unchanged ● LTE FDD or LM: A

GL, or other ● LTE FDD or LM: maximum of six
working nine (2T2R, 2T4R, cells can be
modes or 4T4R) cells enabled with LTE
involving LTE FDD and NR Flash
FDD ● Woking mode Dynamic Spectrum
combinations other Sharing, while the
than LM: six (2T2R, rest are common
2T4R, or 4T4R) cells.
cells
● Woking mode
combinations other
than LM: A
maximum of three
cells can be
enabled with LTE
FDD and NR Flash
Dynamic Spectrum
Sharing, while the
rest are common
cells.

(2021-12-30)
SingleRAN

(Compared with
That Before This
LTE FDD, LM, UBBPe6 Remain unchanged ● LTE FDD or LM

GL, or other ● LTE FDD or LM (with BBP.SRT set
working (with BBP.SRT set to DEFAULT): A
modes to DEFAULT): 12 maximum of six
involving LTE (2T2R, 2T4R, or cells support LTE
FDD 4T4R) cells FDD and NR Flash
Dynamic Spectrum
● LM (with BBP.SRT Sharing, while the
set to rest are common
NBIOT_ENHANCE) cells.
: nine (2T2R, 2T4R,
or 4T4R) cells ● LM (with BBP.SRT
set to
● Woking mode NBIOT_ENHANCE)
combinations other : A maximum of six
than LM: nine cells support LTE
(2T2R, 2T4R, or FDD and NR Flash
4T4R) cells Dynamic Spectrum
● LTE FDD: six (8T8R) Sharing, while the
cells rest are common
cells.
● Woking mode
combinations other
than LM: A
maximum of three
cells can be
enabled with LTE
FDD and NR Flash
Dynamic Spectrum
Sharing, while the
rest are common
cells.
● LTE FDD: A
maximum of six
cells can be
enabled with LTE
FDD and NR Flash
Dynamic Spectrum
Sharing.
LTE FDD, LM, UBBPg Remain unchanged Same as the cell

GL, or other number specifications
working before this function is
modes enabled
involving LTE
FDD

(2021-12-30)
SingleRAN

(Compared with
That Before This
a: LM refers to LTE FDD and NB-IoT.

b: The UBBPe1 is used as an example for illustrating the cell number
specifications. If this board also serves cells enabled with LTE FDD and NR
Uplink Spectrum Sharing, this board supports a maximum of three cells enabled
with LTE FDD and NR Flash Dynamic Spectrum Sharing and with LTE FDD and
NR Uplink Spectrum Sharing.
HDSS based on Asymmetric Beam enabled)
Working Baseband Supported LTE Cell Number Specifications
Mode Processing Unit
Model
LTE FDD UBBPe4/UBBPe6/ Three LTE sector split groups are supported,
UBBPe18 with two LTE cells in each group. A maximum
of three LTE sector split groups support this
function.
LTE FDD UBBPg The supported LTE sector split group

specifications are the same as those before
this function is enabled.
To prevent LTE cell activation failures due to insufficient baseband processing

resources, cells enabled with this function must be bound to baseband processing
units that also support it. Otherwise, cell activation may fail in cases where the
baseband processing units that support this function are fully occupied, leaving
only those that do not support it.
RF Modules
● 3900 and 5900 series base stations: All 3000 and 5000 series RF modules that
meet the following conditions support this function:
– LTE and NR share the same RF module.
– The 10 MHz, 15 MHz, or 20 MHz bandwidth is supported and can be
configured.
– The 700 MHz, 800 MHz, 850 MHz, 900 MHz, 1800 MHz, 2100 MHz, 2600
MHz, AWS, or PCS frequency band is supported and can be configured.
– The following TX/RX modes are supported and can be configured: 2T2R,
2T4R, 4T4R, 8T8R, and 32T32R.
When HDSS based on Asymmetric Beam is not enabled, of all 8T8R RF
modules, the AAU5972 (active module), 8T8R RRUs, and 8T8R RRUs

(2021-12-30)
SingleRAN
combined by 4T4R RRUs support this function. When HDSS based on

Asymmetric Beam is enabled, only 1800 MHz and 2100 MHz 8T8R RRUs
Of all 32T32R RF modules, the AAU5711a (1.8 GHz or 2.6 GHz),
AAU5726 (1.8 GHz and 2.1 GHz), AAU5726 (AWS+PCS), and AAU5733
(2.6 GHz) support this function.
When the cell TX/RX mode is 32T32R, the 2.2:1 CPRI compression ratio is
required to support the simultaneous use between CPRI compression and
the co-carrier co-CPRI data function. The corresponding RF modules can
be AAU5726 (1.8 GHz and 2.1 GHz), and AAU5726 (AWS+PCS).
When LTE FDD and NR Flash Dynamic Spectrum Sharing needs to be used
with NB-IoT deployed in LTE guard band mode, only the RRU3262, RRU3965,
RRU5309, RRU5508, RRU5512, and RRU5909 can be used. In addition, the
RRU5508 and RRU5512 support only the 700 MHz frequency band.
● DBS3900 LampSite and DBS5900 LampSite: All 3000 (excluding the
pRRU3901) and 5000 series pRRUs that meet the following conditions support
this function:
– LTE and NR share the same RF module.
– The pRRUs involved in an RF combination must use the same channels.
Specifically, they must all use channels A and B, or use channels C and D.
– The 700 MHz, 800 MHz, 850 MHz, 900 MHz, 1800 MHz, 2100 MHz, 2600
MHz, AWS, or PCS frequency band is supported and can be configured.
– 2T2R is supported and can be configured.
Cells
LTE and NR cells must meet all of the following requirements:
● Bandwidth
The LTE and NR cell bandwidths are both 10 MHz, 15 MHz, or 20 MHz, and
LTE and NR cells must have the same uplink and downlink bandwidths.
In addition to the preceding standard cell bandwidths, this function can be
used with the compact bandwidth function. For details about the non-
standard bandwidths supported by this function, see descriptions of compact
bandwidth in 3.2.2 Impacts.
NOTICE
When a non-standard bandwidth is used, in addition to the hardware

requirements described in this section, the hardware requirements of compact
bandwidth must also be met. For details about the hardware requirements of
compact bandwidth, see related descriptions in Compact Bandwidth (FDD) of
eRAN Feature Documentation and in Scalable Bandwidth of 5G RAN Feature
Documentation.
● TX/RX mode
– 3900 and 5900 series base stations: The TX/RX modes of LTE and NR cells
must be the same and must be one of 2T2R, 2T4R, 4T4R, 8T8R, and
32T32R. When the TX/RX mode is 2T2R or 2T4R, the recommended

(2021-12-30)
SingleRAN
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. When the TX/RX mode is 8T8R, the
number of CRS ports for LTE cells must be 4. When the TX/RX mode is
32T32R, the number of CRS ports for LTE cells must be 4.
– DBS3900 LampSite and DBS5900 LampSite: 2T2R
● LTE and NR cells must have the same operating frequency band and center
frequency.
● The PSD of the LTE and NR cells must be the same. If the total power of the
LTE and NR cells exceeds the maximum transmit power of the RF module, the
power of the cells needs to be reduced or the RF module needs to be
replaced.
● The PA value must meet the following requirements when even power
distribution is used for the PDSCH:
– In the case of 2T2R, 2T4R, or 4T4R cell TX/RX mode: When the cell
bandwidth is 10 MHz and the spectrum power sharing mode is used, the
CellDlpcPdschPa.PaPcOff parameter cannot be set to DB_6_P_A or
DB_4DOT77_P_A.
– In the case of 8T8R cell TX/RX mode
▪ When HDSS based on Asymmetric Beam is not enabled: Assume that

the cell bandwidth is 10 MHz and the spectrum power sharing mode
is used. If the CellDlpcPdsch.RemainingPwrUseStrategy parameter
for the LTE cell is not set to PORT_PWR_BALANCING, the
CellDlpcPdschPa.PaPcOff parameter cannot be set to DB_6_P_A or
DB_4DOT77_P_A.
▪ When HDSS based on Asymmetric Beam is enabled: Assume that the

cell bandwidth is 10 MHz and the spectrum power sharing mode is
used. If the PDSCHCfg.LogicalPortSwapSwitch parameter for the
two LTE cells is set to the same value, the CellDlpcPdschPa.PaPcOff
parameter cannot be set to DB_6_P_A or DB_4DOT77_P_A.
– In the case of 32T32R cell TX/RX mode: Assume that the cell bandwidth is
10 MHz and the spectrum power sharing mode is used. If one or three
LTE cells are configured, the BEAM_NUM_ADJ_SWITCH option of the
SectorSplitGroup.SectorSplitSwitch parameter is selected, or the
SectorSplitGroup.TM4WeightScheme parameter is set to
DEFAULT_MODE, the CellDlpcPdschPa.PaPcOff parameter cannot be set
to DB_6_P_A or DB_4DOT77_P_A.
● LTE and NR cells must be deployed in 1:1 co-coverage mode, and must be
served by the same transmit channels of an RF module.
● When HDSS based on Asymmetric Beam is required, the two LTE cells must
have different PCIs as well as different PCI mod 3 values to preferentially
ensure LTE performance. If NR performance needs to be preferentially
ensured, the two LTE cells must have different PCIs but the same PCI mod 3
value.

(2021-12-30)
SingleRAN
3.3.4 Networking
3900 and 5900 Series Base Stations
When the LTE and NR co-carrier co-CPRI data function is not enabled (the LTE
parameter LteNrSpctShrCellGrp.LteNrCoCarrCoCpriDataSw is set to OFF):
● If the independent power configuration mode is used, there are no special
networking requirements.
● If the spectrum power sharing mode is used, the
LNR_PWR_WITH_SPCT_OPT_SW option of the
SpectrumCloud.SpectrumCloudEnhSwitch parameter must be selected to
solve the power allocation conflicts caused by inconsistent LTE and NR latency
when each uses their respective optical fibers over the CPRI interface.
When the co-carrier co-CPRI data function is enabled (the LTE parameter
LteNrSpctShrCellGrp.LteNrCoCarrCoCpriDataSw is set to ON), this function only
supports the intra-BBU single-fiber CPRI MUX topology in separate-MPT and co-
MPT LTE/NR scenarios or the intra-board cold backup ring topology in co-MPT
LTE/NR scenarios. These topologies do not pose special requirements on board
installation positions. In intra-BBU single-fiber CPRI MUX topology, LTE and NR
cells can be established on the same or different baseband processing units. The
following example illustrates the networking requirements using LTE and NR cells
established on different baseband processing units. In intra-board cold backup ring
topology, LTE and NR cells must be established on the same baseband processing
unit.
● Intra-BBU CPRI MUX topology in separate-MPT LTE/NR scenarios: LTE and NR
share a BBU, and either the LTE or NR baseband processing unit is connected
directly to the RRU through an optical fiber, as shown in Figure 3-8.

(2021-12-30)
SingleRAN
Figure 3-8 Intra-BBU CPRI MUX topology in separate-MPT LTE/NR scenarios
● Intra-BBU CPRI MUX topology in co-MPT LTE/NR scenarios: LTE and NR share
a BBU, and either the LTE or NR baseband processing unit is connected
directly to the RRU through an optical fiber, as shown in Figure 3-9.

(2021-12-30)
SingleRAN
Figure 3-9 Intra-BBU CPRI MUX topology in co-MPT LTE/NR scenarios
● Intra-board cold backup ring topology in co-MPT LTE/NR scenarios: In this

topology, LTE and NR share a BBU, and both the LTE and NR baseband
processing units are connected directly to the RRU through an optical fiber to
form a ring topology, as shown in Figure 3-10.

(2021-12-30)
SingleRAN
Figure 3-10 Intra-board cold backup ring topology in co-MPT LTE/NR

scenarios
DBS3900 LampSite and DBS5900 LampSite

The co-carrier co-CPRI data function must be enabled by setting the LTE
parameter LteNrSpctShrCellGrp.LteNrCoCarrCoCpriDataSw to ON.
When the preceding requirement is met, this function requires an intra-BBU CPRI
MUX topology in separate-MPT and co-MPT scenarios, and requires BBU+DCU
interconnection in co-MPT scenarios. These topologies do not pose special
requirements on board installation positions. LTE and NR cells can be established
on the same or different baseband processing units. The following example
illustrates the networking requirements using LTE and NR cells established on
different baseband processing units.
share a BBU, and either the LTE or NR baseband processing unit is connected
directly to the RHUB through an optical fiber, as shown in Figure 3-11.

(2021-12-30)
SingleRAN
a BBU, and either the LTE or NR baseband processing unit is connected
directly to the RHUB through an optical fiber, as shown in Figure 3-12.

(2021-12-30)
SingleRAN
● BBU+DCU interconnection in co-MPT LTE/NR scenarios: Either the LTE or NR

baseband processing unit in the BBU is connected to the DCU through an
optical fiber, and the DCU is connected to the RHUB or hRRU through optical
connections on the MEDC, as shown in Figure 3-13.

(2021-12-30)
SingleRAN
Figure 3-13 BBU+DCU interconnection in co-MPT LTE/NR scenarios
NOTE
In this topology, it is recommended that the NR baseband processing unit be used for
the optical connection to the DCU to reduce the transmission bandwidth overhead of
the BBU backplane.
For the DBS3900 LampSite and DBS5900 LampSite, LTE and NR cells support only
one sector equipment group. When the RHUB5965 is used, each sector equipment
group supports a maximum of 24 pRRUs. When another RHUB model is used,
each sector equipment group supports a maximum of 16 pRRUs.

(2021-12-30)
SingleRAN
3.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 in all cells in the planned
deployment area to reduce the interference caused by the near-far effect.
● NR FDD networks require time synchronization. This function requires the
coordination between the LTE FDD and NR FDD networks, and therefore LTE
FDD networks also need to meet time synchronization requirements. For
details about how to configure time synchronization, see Synchronization in
eRAN Feature Documentation and Synchronization in 5G RAN Feature
Documentation.
● 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 this function or access NR FDD cells not enabled with this function.
In NSA networking, when NR UEs that do not support CRS rate matching are
handed over from a neighboring NR FDD cell not enabled with spectrum
sharing to an NR FDD spectrum sharing cell and the handover is rejected, the
following KPIs decrease:
– SgNB Addition Success Rate
– SgNB Addition Success Rate (CU)
– Inter-SgNB PSCell Change Success Rate (CU)
– Inter-SgNB IntraFreq PSCell Change Success Rate (CU)
In SA networking, when NR UEs that do not support CRS rate matching are
handed over from a neighboring NR FDD cell not enabled with spectrum
sharing to an NR FDD spectrum sharing cell and the handover is rejected:
– The values of the following KPIs decrease:
▪ QoS flow setup success rate = QoS Flow Setup Success Rate (CU)
▪ UE context setup success rate = (N.UECntx.Est.Succ/

N.UECntx.Est.Att) x 100%
▪ PDU session establishment success rate = (N.PDUSession.Est.Succ/

N.PDUSession.Est.Att) x 100%
▪ E-UTRAN-to-NR incoming handover preparation success rate =

(N.HO.InterRAT.E2N.PrepSuccIn/N.HO.InterRAT.E2N.PrepAttIn) x
100%
– The values of the following counters increase:

(2021-12-30)
SingleRAN
▪ N.QosFlow.FailEst.UeCapability
▪ N.UECntx.FailEst.UeCapability
▪ N.PDUSession.FailEst.UeCapability
▪ N.RRCRedirection.N2E.UeCapability
▪ L.IRATHO.E2N.Prep.FailOut.PrepFailure
3.4 Operation and Maintenance
3.4.1 Data Configuration
CAUTION
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.
3.4.1.1 Data Preparation

Table 3-22 and Table 3-26 describe the parameters used for function activation.
Table 3-25 and Table 3-27 describe the parameters used for function
optimization. This section does not describe parameters related to cell
establishment.
The configuration of some parameters can result in automatic cell restarts during
function activation and deactivation, and modifying the parameter settings of one
RAT will cause both LTE and NR cells to automatically restart. As such, it is
recommended that you deactivate cells prior to parameter configuration and
reactivate them after parameter configuration is complete. This will prevent the
cells from being repeatedly restarted during parameter configuration.

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 3-22 LTE parameters used for activation
Parameter Name Parameter ID Setting Notes
Spectrum Cloud Switch SpectrumCloud.Spectru Set this parameter to

mCloudSwitch LTE_NR_SPECTRUM_SH
R.

(2021-12-30)
SingleRAN
Spectrum Cloud SpectrumCloud.Spectru Set this parameter based

Enhancement Switch mCloudEnhSwitch on the network plan.
● When SRS resource
allocation to LTE is
not required, select
the
LTE_UE_SRS_NOT_CO
NFIG_SW option of
this parameter.
Otherwise, deselect
this option.
The
LTE_UE_SRS_NOT_CO
NFIG_SW option can
only be selected when
all of the following
conditions are met:
– The
SRSCfg.SrsSubfra
meCfg parameter
is set to SC3.
– The
SrsSubframeRecfS
witch option of
the
CellAlgoSwitch.Sr
sAlgoSwitch
parameter is
deselected.
● When the spectrum
power sharing mode
is used, and the LTE
and NR baseband
processing units need
to be connected to
the RRU through their
respective optical
fibers, select the
LNR_PWR_WITH_SPC
T_OPT_SW option.
When the
independent power
configuration mode is
used, LTE and NR can
use their respective
optical fibers over the
CPRI interface without
needing to select this
option.

(2021-12-30)
SingleRAN
● Select the
WBB_MBB_CONTROL
_OPT_SW option of
this parameter when
the simultaneous use
with WBB is required.
LTE and NR Spectrum SpectrumCloud.LteNrSp Set this parameter based

Sharing Cell Group IDa ectrumShrCellGrpId on the network plan.
Spectrum Sharing Mode SpectrumCloud.SpctShr Set this parameter to

Mode LTE_NR_PWR_DYN_SHR
_WITH_SPCT or
LTE_NR_PWR_INDEPEN
DENT based on the
network plan.
LTE and NR Spectrum LteNrSpctShrCellGrp.Lt Set this parameter based

Sharing Cell Group IDa eNrSpectrumShrCellGr- on the network plan. The
pId value of the
LteNrSpctShrCellGrp.Lt
eNrSpectrumShrCellGr-
pId parameter must be
the same as that of the
gNBDULteNrSpctShrCg.
LteSpctShrCellGrpId
parameter.

(2021-12-30)
SingleRAN
MBB LTE Pri Res Ratio in LteNrSpctShrCellGrp.Lt Set this parameter based
LTE and NR Spct Shr eNrSpctShrLtePriResRa- on the network plan. The
tio value of this parameter
varies with the spectrum
allocation policy, and the
following lists the
configuration
suggestions for ensuring
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.
need to be
preferentially
allocated to NR, it is
recommended that
range of 20 to 49.
need to be evenly
allocated to LTE and
NR, it is
recommended that
to 50.
If this parameter is set to
a value less than 20 or
greater than 80, the
access success rate may
decrease or the service
drop rate may increase in
high load scenarios.

(2021-12-30)
SingleRAN
DL SPS Restrict Ratio SpectrumCloud.DlSpsRe Set this parameter based

strictRatio on the network plan. The
proportion of RBs
allocated for LTE
downlink semi-persistent
scheduling =
(SpectrumCloud.DlSpsR
estrictRatio x
eNrSpctShrLtePriResRa-
tio/100)%.
LTE and NR Co Carrier LteNrSpctShrCellGrp.Lt Set this parameter based
Co CPRI Data Switch eNrCoCarrCoCpriDa- on the network plan.
taSw This parameter can be
set to ON only when LTE
and NR share the same
CPRI optical fibers, and
the CPRI bandwidth is
insufficient. When the
cell TX/RX mode is
32T32R, this parameter
cannot be set to ON.
RB Reserve Modeb CellRbReserve.RbRsvMo Set this parameter to

de LNR_SPECTRUM_SHR_R
B_RESERVED.
RB Reserve Typeb CellRbReserve.RbRsvTy Set this parameter to

pe UPLINK_MODE.
RB Reserve Start Indexb CellRbReserve.RbRsvSta Set this parameter based

rtIndex on the network plan.
RB Reserve End Indexb CellRbReserve.RbRsvEn Set this parameter based

dIndex on the network plan.
Subframe Allocation CellMbsfnSfEnhCon- Set this parameter to

Mode fig.SubframeAllocation- FOUR_FRAME.
Mode

(2021-12-30)
SingleRAN
Four Frame Allocation CellMbsfnSfEnhCon- ● In NSA networking,

fig.FourFrameAlloca- the configuration
tion suggestions for this
parameter vary
depending on the SSB
period. For details, see
Table 3-23.
● In SA networking, the
configuration
suggestions for this
parameter vary
depending on the SSB
period and the
activation status of
the SSB dual-beam
function. For details,
see Table 3-24.
Radio Frame Allocation CellMbsfnSfEnhCon- Set this parameter to N4.

Period fig.RadioFrameAllocPrd
Radio Frame Allocation CellMbsfnSfEnhCon- Set this parameter to 0.

Offset fig.RadioFrameAllocOfs
Frame Offsetc CellFrameOffset.Frame Set this parameter to a

Offset value confirmed by
Huawei engineers.
FDD Frame Offsetc ENodeBFrameOffset.Fd Set this parameter to a

dFrameOffset value confirmed by
Huawei engineers.

(2021-12-30)
SingleRAN
TA Offset CellFrameOffset.TaOffs This parameter must be

et set to a value consistent
with the TA offset on the
NR side specified by the
NRDUCell.TaOffset
parameter. That is, the
following configuration
requirements must be
met:
● When the
CellFrameOffset.TaOf
fset parameter is set
to 0Ts, the
NRDUCell.TaOffset
parameter must be
set to 0Tc.
● When the
to 400Ts, the
NRDUCell.TaOffset
parameter must be
set to 15600Tc.
● When the
to 624Ts, the
NRDUCell.TaOffset
parameter must be
set to 39936Tc.
a: In the current version, an LTE spectrum sharing cell group can contain only
one LTE cell.
b: In upgrade scenarios, these four parameters inherit the configurations of the
source version and do not need to be configured. In new deployment scenarios,
the configurations of these parameters follow the instructions on how to
configure the LTE PUCCH in 3.1.1.2 Key Technologies.
c: If both the CellFrameOffset.FrameOffset and
ENodeBFrameOffset.FddFrameOffset parameters are configured, the frame
offset specified by the CellFrameOffset.FrameOffset parameter takes effect for
the LTE cell.
Table 3-23 Configuration suggestions for Four Frame Allocation in NSA

networking
GUI Value of SSB Period Setting Notes
MS5(5) 9586980

(2021-12-30)
SingleRAN
GUI Value of SSB Period Setting Notes
MS10(10) 8521760
MS20(20) 8390656
MS40(40) or a larger 8388608

value
Table 3-24 Configuration suggestions for Four Frame Allocation in SA

networking
Application Scenario Setting Notes
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 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 MS40(40) or a
larger value, set this parameter to 14680064.
Table 3-25 LTE parameters used for optimization

Aggregation Attribute NrNFreq.AggregationAt Select the

tribute DSS_FREQ_INDICATION
option of this parameter
based on the network
plan. This function is
supported only in SA
networking or NSA and
SA hybrid networking,
and is not supported in
NSA networking.

(2021-12-30)
SingleRAN
LNR Spectrum Sharing LteNrSpctShrCellGrp.Lt The

Switch eNrSpctShrSwitch LNR_RES_ALLOC_ADAP
T_SW option of this
parameter together with
the
tio parameter
determines the spectrum
resource allocation mode
for LTE and NR cells. For
details, see 3.1.2.1
Flexible Spectrum
Priority Mode.
When the function of
inter-RAT preferential
guarantee for GBR
services is required,
select the
GBR_PRI_ALLOC_SW
option of this parameter.
LNR Spectrum Sharing LteNrSpctShrCellGrp.Lt When the NR PDSCH

Switch eNrSpctShrSwitch needs to avoid the LTE
CSI-RS at the RE level
according to the network
plan, select the
LTE_CSI_RS_AVOID_POL
ICY_SW option of this
parameter.
This option cannot be
selected when the TX/RX
mode of the LTE cell is
8T8R.
LNR Spectrum Sharing LteNrSpctShrCellGrp.Lt When the LTE key event

Switch eNrSpctShrSwitch assurance function is
required according to the
network plan, select the
LTE_BIG_EVENT_ASSUR
ANCE_SW option of this
parameter.

(2021-12-30)
SingleRAN
LNR Spectrum Sharing LteNrSpctShrCellGrp.Lt Select the

Switch eNrSpctShrSwitch LTE_NR_SRS_ALLOC_OP
T_SW option of this
parameter when LTE and
NR SRS resource
allocation optimization is
required based on the
network plan.
The preceding option can
be selected only when
the following conditions
are all met:
● The cell TX/RX mode
is not 32T32R.
● The
Cell.HighSpeedFlag
parameter must be
set to LOW_SPEED.
● The
CellUlschAlgo.UlSrsF
reqSelSchSinrThld
parameter must be
set to 255, and the
reqSelSchSinrThld
parameter must be
set to 255.
● The
NSA_DC_UL_PATH_S
ELECTION_SW option
of the
NsaDcMgmtConfig.N
saDcAlgoSwitch
parameter is
deselected.
● The
LTE_UE_SRS_NOT_CO
NFIG_SW option of
the
SpectrumCloud.Spec
trumCloudEnhSwitch
parameter is
deselected.
LTE Big Event UE LteNrSpctShrCellGrp.Lt Retain the default value.

Number Threshold eBigEventUeNumThld

(2021-12-30)
SingleRAN
LTE Big Event UE LteNrSpctShrCellGrp.Lt Retain the default value.

Number Threshold eBigEventUeNumThl-
Offset dOffset
Table 3-26 NR parameters used for activation

Spectrum Cloudification NRDUCellAlgoSwitch.S Select the

Switch pectrumCloudSwitch LTE_NR_FDD_SPCT_SHR
_SW option of this
parameter.
NR Spectrum Sharing NRDUCellSpctCloud.Nr Set this parameter based

Cell Group IDa SpctShrCellGrpId on the network plan.
NR Spectrum Sharing gNBDULteNrSpctShrCg. Set this parameter based

Cell Group IDa NrSpctShrCellGrpId on the network plan.
LTE Spectrum Sharing gNBDULteNrSpctShrCg. Set this parameter based

Cell Group IDa LteSpctShrCellGrpId on the network plan. The
value of the
LteSpctShrCellGrpId
parameter must be the
same as that of the
pId parameter.
Common Control NRDUCellCoreset.Com This parameter only
Resource RB Number monCtrlResRbNum needs to be set when the
NRDUCellPdcch.Occupi
edSymbolNum
parameter is set to
2SYM. Set this
parameter to RB24 or
RB48.
SSB Frequency Position NRDUCell.SsbDescMeth It is recommended that

Describe Method od this parameter be set to
SSB_DESC_TYPE_NARFC
N in NSA networking,
and to
SSB_DESC_TYPE_GSCN
in SA networking.
SSB Frequency Position NRDUCell.SsbFreqPos Set this parameter to a

value confirmed by
Huawei engineers.

(2021-12-30)
SingleRAN
SSB Period NRDUCell.SsbPeriod Set this parameter based

on the network plan.
SIB1 Period NRDUCell.Sib1Period Set this parameter to

MS40(40).
Format1 RB Number NRDUCellPucch.Format Set this parameter based

1RbNum on the network plan. For
details about the
configuration
suggestions for different
scenarios, see the data
preparation section in
the "PUCCH Channel
Management" chapter of
Channel Management.
details about the cells for
which this parameter
takes effect, see the
parameter meaning.
For details about the
configuration
the "PUCCH Channel
Channel Management
Format3 CSI-dedicated NRDUCellPucch.CsiDedi Set this parameter based
RB Number catedRbNum on the network plan. For
details about the
configuration
the "PUCCH Channel
Channel Management.

(2021-12-30)
SingleRAN

parameter meaning.
configuration
the "PUCCH Channel
Channel Management.
Format4 CSI-dedicated NRDUCellPucch.Format Set this parameter based
RB Number 4CsiDedicatedRbNum on the network plan. For
details about the
configuration
the "PUCCH Channel
Channel Management.
Spectrum Sharing Start NRDUCellPdcch.SpctShr When one or two LTE
Symbol StartSymbol CRS ports are configured
and NR traffic volume
requirements are greater
than LTE traffic volume
requirements, set this
parameter to SYM1;
when NR traffic volume
requirements are lower
than LTE traffic volume
parameter to SYM2.
Otherwise, the
proportion of CCE
allocation failures
increases in cells with
large traffic volume
requirements, affecting
the average uplink and
downlink UE throughput.
When four LTE CRS ports
are configured, set this
parameter to SYM2.

(2021-12-30)
SingleRAN
Occupied Symbol NRDUCellPdcch.Occupi Set this parameter to

Number edSymbolNum 2SYM when the
NRDUCellPdcch.SpctShr
StartSymbol parameter
is set to SYM0 or SYM1,
and to 1SYM when the
is set to SYM2.
Frame Offsetb gNodeBParam.FrameOf Set this parameter to a

fset value confirmed by
Huawei engineers.
Frame Offsetb gNBFreqBandConfig.Fra Set this parameter to a

meOffset value confirmed by
Huawei engineers.
TA Offset NRDUCell.TaOffset This parameter must be

set to a value consistent
LTE side specified by the
CellFrameOffset.TaOffs
et parameter. That is, the
met:
● When the
to 0Ts, the
NRDUCell.TaOffset
parameter must be
set to 0Tc.
● When the
to 400Ts, the
NRDUCell.TaOffset
parameter must be
set to 15600Tc.
● When the
to 624Ts, the
NRDUCell.TaOffset
parameter must be
set to 39936Tc.
RB Reserve Modec NRDUCellRbReserve.Rb Set this parameter to

RsvMode NB_GB_RB_RESERVED.

(2021-12-30)
SingleRAN
RB Reserve Typec NRDUCellRbReserve.Rb Set this parameter to

RsvType UPLINK_MODE or
DOWNLINK_MODE to
reserve uplink and
downlink RBs,
respectively.
RB Reserve Start Indexc NRDUCellRbReserve.Rb Set this parameter to a

RsvStartIndex value confirmed by
Huawei engineers. The
recommended
configuration is
described in 3.1.3
Application Scenarios
of Simultaneous Use of
Flash Dynamic
Spectrum Sharing and
Other Functions.
RB Reserve End Indexc NRDUCellRbReserve.Rb Set this parameter to a

RsvEndIndex value confirmed by
recommended
configuration is
described in 3.1.3
Flash Dynamic
Spectrum Sharing and
Other Functions.
Spectrum Cloudification NRDUCellAlgoSwitch.S Set this parameter based

Enhance Switch pectrumCloudEnhS- on the network plan.
witch When HDSS based on
Asymmetric Beam is
enabled, select the
LTE_CRS_RATEMATCH_
ALL_SYM_SW option if
LTE performance needs
to be preferentially
ensured, and deselect
this option if NR
performance needs to be
preferentially ensured.

(2021-12-30)
SingleRAN
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 NR cell.
c: These four parameters need to be configured when LTE FDD and NR Flash
Dynamic Spectrum Sharing is used together with NB-IoT deployed in LTE guard
band mode.
Table 3-27 NR parameters used for optimization

Rate Match Switch NRDUCellPdsch.RateMa Select the

tchSwitch PDCCH_RATEMATCH_S
W and
SSB_RATEMATCH_SW
options of this parameter
plan. These two options
can be individually or
both selected.
Downlink Additional NRDUCellPdsch.DlAddit Set this parameter to

DMRS Position ionalDmrsPos POS1 in mobility
scenarios, and to
NOT_CONFIG in fixed-
point scenarios.
LTE Handover Algo gNodeBParam.LteHand Select the

Switch overAlgoSwitch LTE_HO_TO_DSS_NR_OP
T_SW option of this
parameter based on the
network plan.

(2021-12-30)
SingleRAN
FDD LNR Spectrum gNBDULteNrSpctShrCg. Select the

Sharing Switch FddLteNrSpctShrSwitch LTE_CSI_RS_AVOID_SW
and
LTE_CRS_PORT_1_RM_S
W options of this
network plan. These two
options can be
individually or both
selected.
The
LTE_CSI_RS_AVOID_SW
option cannot be
selected when the TX/RX
mode of the LTE cell is
8T8R.

Enhance Switch pectrumCloudEnhS- LTE_SS_PBCH_RM_OPT_
witch SW option of this
network plan.

Enhance Switch pectrumCloudEnhS- PWR_SPCT_DENSITY_A
witch DAPT_SW option of this
network plan.
LTE Big Event Assurance gNBDULteNrSpctShrCg. Retain the default value.

UE Number Thld LteBigEventAssureUe-
NumThld

Before using MML commands, refer to 3.2.2 Impacts and 3.3.2 Software and
complete the parameter configurations for related functions based on the impact,
dependency, and mutually exclusive relationships between the functions, as well
as the actual network scenario.
This function must be activated or deactivated on both the LTE and NR sides.
When HDSS based on Asymmetric Beam is required, parameters need to be
configured for both LTE cells on the LTE side. Only some command examples for
such scenarios are provided below.
Activation Command Examples (with HDSS based on Asymmetric Beam

Disabled)
Activation command examples on the LTE side
//Deactivating the cell
DEA CELL: LocalCellId=0;

(2021-12-30)
SingleRAN
//Binding the cell that requires this function to a baseband processing unit supporting this function
MOD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=1, BaseBandEqmId=12;
//(Optional when the cell TX/RX mode is 32T32R) Setting the percentage of spectrum resources to be
preferentially allocated to LTE MBB services, and turning on the LTE and NR co-carrier co-CPRI data switch
ADD LTENRSPCTSHRCELLGRP: LteNrSpectrumShrCellGrpId=0, LteNrSpctShrLtePriResRatio=50,
LteNrCoCarrCoCpriDataSw=ON;
//(Optional, required only when the cell TX/RX mode is 8T8R) Configuring subframe-level avoidance of the
LTE CSI-RS by NR)
MOD LTENRSPCTSHRCELLGRP: LteNrSpectrumShrCellGrpId=0,
LteNrSpctShrSwitch=LTE_CSI_RS_AVOID_POLICY_SW-0;
//Turning on the switch controlling LTE FDD and NR Flash Dynamic Spectrum Sharing, adding an LTE cell to
an LTE spectrum sharing cell group, setting the spectrum sharing mode (assuming that SRS resources need
to be configured for LTE UEs), turning on the switch controlling power allocation optimization in spectrum
power sharing mode, turning on the WBB/MBB control policy optimization switch, and setting the LTE
downlink SPS restrict ratio
ADD SPECTRUMCLOUD: LocalCellId=0, SpectrumCloudSwitch=LTE_NR_SPECTRUM_SHR,
LteNrSpectrumShrCellGrpId=0, SpctShrMode=LTE_NR_PWR_DYN_SHR_WITH_SPCT,
SpectrumCloudEnhSwitch=LTE_UE_SRS_NOT_CONFIG_SW-0&LNR_PWR_WITH_SPCT_OPT_SW-1&WBB_MBB_
CONTROL_OPT_SW-1, DlSpsRestrictRatio=30;
//Setting the start position of the LTE PUCCH at the lower end and the end position of the LTE PUCCH at
the upper end (assuming that the number of RBs configured for the NR PUCCH exceeds the number of
reserved RBs in a 10 MHz cell)
ADD CELLRBRESERVE: LocalCellId=0, Index=1, RbRsvMode=LNR_SPECTRUM_SHR_RB_RESERVED,
RbRsvType=UPLINK_MODE, RbRsvStartIndex=3, RbRsvEndIndex=46;
//Configuring MBSFN subframes (using the SA networking without the SSB dual-beam function as an
example)
MOD CELLMBSFNSFENHCONFIG: LocalCellId=0, SubframeAllocationMode=FOUR_FRAME,
FourFrameAllocation=10487808, RadioFrameAllocPrd=N4, RadioFrameAllocOfs=0;
//Setting the frame offset and TA offset
ADD CELLFRAMEOFFSET: LocalCellId=0, FrameOffsetMode=CustomFrameOffset, FrameOffset=0,
TaOffset=0Ts;
//Activating the cell
ACT CELL: LocalCellId=0;
Activation command examples on the NR side

DEA NRCELL: NrCellId=0;
//Adding an LTE spectrum sharing cell group and an NR spectrum sharing cell group
ADD GNBDULTENRSPCTSHRCG: NrSpctShrCellGrpId=0, LteSpctShrCellGrpId=0;
LTE CSI-RS by NR)
MOD GNBDULTENRSPCTSHRCG: NrSpctShrCellGrpId=0, LteSpctShrCellGrpId=0,
FddLteNrSpctShrSwitch=LTE_CSI_RS_AVOID_SW-0;
//Adding the NR cell to the NR spectrum sharing cell group
ADD NRDUCELLSPCTCLOUD: NrDuCellId=0, NrSpctShrCellGrpId=0;
//Setting the number of RBs for the NR PUCCH (using cells for which downlink intra-FR inter-band CA does
not take effect (INTRA_FR_INTER_BAND_CA_SW option of the NRDUCellAlgoSwitch.CaAlgoSwitch
parameter deselected) and cells for which the NSA TDM pattern type strategy is not set to LTE uplink
preferred (NRDUCellAlgoSwitch.NsaTdmPatternTypeStrategy set to a value other than
LTE_UL_PREFERRED) as an example)
MOD NRDUCELLPUCCH: NrDuCellId=0, Format1RbNum=RB2, Format3RbNum=RB4,
CsiDedicatedRbNum=RB4, Format4RbNum=RB0, Format4CsiDedicatedRbNum=RB0;
//Configuring symbols occupied by the NR PDCCH
//When one or two LTE CRS ports are configured
MOD NRDUCELLPDCCH: NrDuCellId=0, SpctShrStartSymbol=SYM1, OccupiedSymbolNum=2SYM;
//When four LTE CRS ports are configured
//Setting the frame offset
MOD GNODEBPARAM: FrameOffset=0;
//Setting the TA offset
MOD NRDUCELL: NrDuCellId=0, FrequencyBand=N1, TaOffset=0TC;
//Turning on the switch controlling LTE FDD and NR Flash Dynamic Spectrum Sharing
MOD NRDUCELLALGOSWITCH: NrDuCellId=0, SpectrumCloudSwitch=LTE_NR_FDD_SPCT_SHR_SW-1;
//(Optional, required when the NRDUCellPdcch.OccupiedSymbolNum parameter is set to 2SYM)
Configuring the number of RBs for common control resources
MOD NRDUCELLCORESET: NrDuCellId=0, CommonCtrlResRbNum=RB24;
//Setting the SSB frequency-domain position
MOD NRDUCELL: NrDuCellId=0, DuplexMode=CELL_FDD, SsbDescMethod=SSB_DESC_TYPE_NARFCN,
SsbFreqPos=426860;

(2021-12-30)
SingleRAN
//Configuring the SSB and SIB1 periods

MOD NRDUCELL: NrDuCellId=0, SsbPeriod=MS20, Sib1Period=MS40;
//(Optional, required when LTE FDD and NR Flash Dynamic Spectrum Sharing is used together with NB-IoT
deployed in LTE guard band mode) Configuring reserved RBs for NB-IoT
ADD NRDUCELLRBRESERVE: NrDuCellId=0, Index=0, RbRsvMode=NB_GB_RB_RESERVED,
RbRsvType=DOWNLINK_MODE, RbRsvStartIndex=0, RbRsvEndIndex=3;
ACT NRCELL: NrCellId=0;

Enabled)
//Deactivating cells
//Binding cells that require this function to a baseband processing unit supporting this function
//(Optional, set based on the network plan) Setting the percentage of spectrum resources to be
//Turning on the switch controlling LTE FDD and NR Flash Dynamic Spectrum Sharing, adding LTE cells to
an LTE spectrum sharing cell group, setting the spectrum sharing mode (assuming that SRS resources need
to be configured for LTE UEs), turning on the switch controlling power allocation optimization in spectrum
power sharing mode, and setting the LTE downlink SPS restrict ratio
SpectrumCloudEnhSwitch=LNR_PWR_WITH_SPCT_OPT_SW-1, DlSpsRestrictRatio=30;
SpectrumCloudEnhSwitch=LNR_PWR_WITH_SPCT_OPT_SW-1, DlSpsRestrictRatio=30;
//Setting the start position of the LTE PUCCH at the lower end of the frequency domain and the end
position of the LTE PUCCH at the upper end of the frequency domain (assuming that the number of RBs
configured for the NR PUCCH exceeds the number of reserved RBs in a 10 MHz cell)
//Configuring MBSFN subframes (using SA networking without the SSB dual-beam function as an example)
ADD CELLFRAMEOFFSET: LocalCellId=0, FrameOffsetMode=CustomFrameOffset, FrameOffset=0;
ADD CELLFRAMEOFFSET: LocalCellId=3, FrameOffsetMode=CustomFrameOffset, FrameOffset=0;
//Activating the cells

//Adding the NR cell to the NR spectrum sharing cell group

(2021-12-30)
SingleRAN

//When four LTE CRS ports are configured
//Turning on the switch controlling LTE FDD and NR Flash Dynamic Spectrum Sharing
//(Optional, required when the NRDUCellPdcch.OccupiedSymbolNum parameter is set to 2SYM)
Configuring the number of RBs for common control resources
MOD NRDUCELLCORESET: NrDuCellId=0, CommonCtrlResRbNum=RB24;
SsbFreqPos=426860;
//(Optional, required when LTE FDD and NR Flash Dynamic Spectrum Sharing is used together with NB-IoT
//Turning on LTE_CRS_RATEMATCH_ALL_SYM_SW (assuming that LTE performance needs to be
preferentially ensured)
MOD NRDUCELLALGOSWITCH: NrDuCellId=0,
SpectrumCloudEnhSwitch=LTE_CRS_RATEMATCH_ALL_SYM_SW-1;
Optimization Command Examples (with HDSS based on Asymmetric Beam

Disabled)
Optimization command examples on the LTE side
//(Optional, required when NR performs CRS rate matching in the pattern of one LTE CRS port) Adjusting
the PA configuration of the cell
MOD CELLDLPCPDSCHPA: LocalCellId=0, PaPcOff=DB0_P_A;
//Configuring the dynamic spectrum sharing frequency indication
ADD NRNFREQ: LocalCellId=0, DlArfcn=100, AggregationAttribute=DSS_FREQ_INDICATION-1;
//(Optional when the cell TX/RX mode is not 8T8R) Configuring RE-level avoidance of the LTE CSI-RS by NR
//Turning on the LTE and NR shared spectrum allocation adaptation switch
LteNrSpctShrSwitch=LNR_RES_ALLOC_ADAPT_SW-1;
//Turning on the switch controlling inter-RAT preferential guarantee for GBR services
MOD LTENRSPCTSHRCELLGRP: LteNrSpectrumShrCellGrpId=0, LteNrSpctShrSwitch=GBR_PRI_ALLOC_SW-1;
//Turning on the LTE and NR SRS resource allocation optimization switch
LteNrSpctShrSwitch=LTE_NR_SRS_ALLOC_OPT_SW-1;
//Turning on the LTE key event assurance switch, and configuring the LTE key event UE number threshold
and LTE key event UE number threshold offset
LteNrSpctShrSwitch=LTE_BIG_EVENT_ASSURANCE_SW-1, LteBigEventUeNumThld=200,
LteBigEventUeNumThldOffset=100;
Optimization command examples on the NR side

//Configuring optimized handover from an LTE cell to an NR spectrum sharing cell
MOD GNODEBPARAM: FrameOffset=0, LteHandoverAlgoSwitch=LTE_HO_TO_DSS_NR_OPT_SW-1;
//Configuring the PDCCH rate matching and SSB rate matching functions
MOD NRDUCELLPDSCH: NrDuCellId=0,
RateMatchSwitch=PDCCH_RATEMATCH_SW-1&SSB_RATEMATCH_SW-1;
//Configuring the position of the downlink additional DMRS (using mobility scenarios as an example)
MOD NRDUCELLPDSCH: NrDuCellId=0, DlAdditionalDmrsPos=POS1;

(2021-12-30)
SingleRAN
//Configuring RE-level avoidance of the LTE CSI-RS by NR (optional when the cell TX/RX mode is not 8T8R)
and CRS rate matching in the pattern of one LTE CRS port
FddLteNrSpctShrSwitch=LTE_CRS_PORT_1_RM_SW-1&LTE_CSI_RS_AVOID_SW-1;
//Turning on the LTE SS/PBCH rate matching optimization switch and PSD adaptation switch
SpectrumCloudEnhSwitch=LTE_SS_PBCH_RM_OPT_SW-1&PWR_SPCT_DENSITY_ADAPT_SW-1;
//Configuring the LTE key event assurance UE number threshold
MOD GNBDULTENRSPCTSHRCG: NrSpctShrCellGrpId=0, LteBigEventAssureUeNumThld=10;

Enabled)
//Configuring the dynamic spectrum sharing frequency indication
//Turning on the LTE key event assurance switch, and configuring the LTE key event UE number threshold
and LTE key event UE number threshold offset
LteNrSpctShrSwitch=LTE_BIG_EVENT_ASSURANCE_SW-1, LteBigEventUeNumThld=200,
LteBigEventUeNumThldOffset=100;

//Configuring optimized handover from an LTE cell to an NR spectrum sharing cell
MOD GNODEBPARAM: FrameOffset=0, LteHandoverAlgoSwitch=LTE_HO_TO_DSS_NR_OPT_SW-1;
//Setting the LTE key event assurance UE number threshold
MOD GNBDULTENRSPCTSHRCG: NrSpctShrCellGrpId=0, LteBigEventAssureUeNumThld=10;
Deactivation Command Examples (with HDSS based on Asymmetric Beam

Disabled)
The following provides only deactivation command examples. You can determine
whether to restore the settings of other parameters based on actual network
conditions.
Deactivation command examples on the LTE side
//Removing cell RB reservation configurations
RMV CELLRBRESERVE: LocalCellId=0, Index=1;
//(Optional, required when MBSFN subframes are not configured before function activation and are
configured upon function activation) Rolling back the configurations of MBSFN subframes
MOD CELLMBSFNSFENHCONFIG: LocalCellId=0, SubframeAllocationMode=NOT_CONFIG;
//Turning off the switch controlling LTE FDD and NR Flash Dynamic Spectrum Sharing
MOD SPECTRUMCLOUD: LocalCellId=0, SpectrumCloudSwitch=OFF;
//Removing the LTE cell from the LTE spectrum sharing cell group
RMV SPECTRUMCLOUD: LocalCellId=0;
RMV LTENRSPCTSHRCELLGRP: LteNrSpectrumShrCellGrpId=0;

(2021-12-30)
SingleRAN
Deactivation command examples on the NR side

//Removing the NR cell from the NR spectrum sharing cell group
RMV NRDUCELLSPCTCLOUD: NrDuCellId=0;
RMV GNBDULTENRSPCTSHRCG: NrSpctShrCellGrpId=0;

Enabled)
//Removing cell RB reservation configurations
//(Optional, required when MBSFN subframes are not configured before function activation and are
configured upon function activation) Rolling back the configurations of MBSFN subframes
//Removing the LTE cells from the LTE spectrum sharing cell group

3.4.1.3 Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.
3.4.2 Activation Verification

Check whether LTE FDD and NR Flash Dynamic Spectrum Sharing has taken effect
using MML commands or by tracing signaling messages. Whether the LTE key
event assurance function is enabled can be queried using MML commands.
When HDSS based on Asymmetric Beam is enabled, activation verification needs

to be performed in both LTE cells.

(2021-12-30)
SingleRAN
Using MML Commands

The basic functions of LTE FDD and NR Flash Dynamic Spectrum Sharing take
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.
gNodeB MML command DSP GNBDULTENRSPCTSHRCG is Dynamic
Sharing.
The enhanced function LTE key event assurance takes effect when both of the
following conditions are met:
● The value of Heavy Traffic Status in the output of the eNodeB command
DSP LTENRSPCTSHRCELLGRP is LTE_HEAVY_TRAFFIC or
LTE_NON_HEAVY_TRAFFIC.
● The value of Heavy Traffic Status in the output of the gNodeB command
DSP GNBDULTENRSPCTSHRCG is LTE Heavy Traffic Assurance or Not LTE
Heavy Traffic Assurance. The value LTE Heavy Traffic Assurance indicates
that this function is in use.
Tracing Signaling Messages
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:

(2021-12-30)
SingleRAN
Management. In the navigation tree of the displayed window, expand NR >
----End
3.4.3 Network Monitoring

After this function is enabled, monitor the network gains and impacts of this
function using the counters listed in 3.2 Network Analysis. When HDSS based on
Asymmetric Beam is enabled, network monitoring needs to be performed in both
LTE cells.

(2021-12-30)
SingleRAN
Parameter Description 4 Hybrid DSS Based on Asymmetric Bandwidth
4 Hybrid DSS Based on Asymmetric

Bandwidth
4.1 Principles
3GPP Release 16 defines large-bandwidth NR FDD cells to further improve the 5G
network experience. However, the use of spectrum resources of large-bandwidth
NR FDD cells is low in the early stages of 5G deployment due to the low
penetration rate of 5G terminals. Hybrid DSS Based on Asymmetric Bandwidth
allows LTE FDD and large-bandwidth NR FDD cells to dynamically share the same
spectrum resources, improving spectrum utilization. It is applicable to operators
that have both LTE FDD and large-bandwidth NR FDD networks.
For ease of description, LTE and NR are used to refer to LTE FDD and NR FDD,
respectively.
This feature supports NSA, SA, and NSA and SA hybrid networking. Unless
otherwise specified, the descriptions apply to all networking scenarios. This feature
applies only to 3900 and 5900 series base stations.
The detailed principles and key technologies of Hybrid DSS Based on Asymmetric
Bandwidth are described in 4.1.1 Basic Functions of Hybrid DSS Based on
Asymmetric Bandwidth. The enhanced functions are described in 4.1.2 Enhanced
Functions of Hybrid DSS Based on Asymmetric Bandwidth. Hybrid DSS Based
on Asymmetric Bandwidth can also be used together with other functions, and the
simultaneous use of these functions is elaborated in 4.1.3 Application Scenarios
of Simultaneous Use of Hybrid DSS Based on Asymmetric Bandwidth and
Other Functions.
4.1.1 Basic Functions of Hybrid DSS Based on Asymmetric

Bandwidth
4.1.1.1 Principles
This function enables LTE and NR cells to dynamically share time-frequency
resources on a shared spectrum segment based on their traffic volumes. The LTE

(2021-12-30)
SingleRAN
and NR cells sharing spectrum resources are configured with different bandwidths.
The NR cell bandwidth is greater than the LTE cell bandwidth, the LTE cell
bandwidth is equal to the shared spectrum, and the NR cell bandwidth minus the
shared spectrum is equal to the NR dedicated spectrum. Figure 4-1 illustrates
spectrum sharing between LTE and NR cells with different bandwidths.
Figure 4-1 Working principles of Hybrid DSS Based on Asymmetric Bandwidth
Table 4-1 lists the applicable cell bandwidths.
Table 4-1 Cell bandwidths to which Hybrid DSS Based on Asymmetric Bandwidth
can be applied
LTE Cell Bandwidth NR Cell Bandwidth
10 MHz 15 MHz
10 MHz 20 MHz
15 MHz 20 MHz
20 MHz 25 MHz
20 MHz 30 MHz

(2021-12-30)
SingleRAN
20 MHz 40 MHz
This function is enabled by turning on function switches, configuring NR dedicated

spectrum resources, and configuring spectrum sharing cell groups. In addition, the
LTE and NR cells sharing spectrum resources must have aligned radio frames and
subframes.
● Turning on function switches on the LTE and NR sides
LTE_NR_SPECTRUM_SHR, and select the
LNR_SPECTRUM_SHR_ASYM_SW option of the
NRDUCellAlgoSwitch.SpectrumCloudSwitch parameter, and select the
LTE_NR_FDD_SPCT_SHR_ASYM_SW option of the
NRDUCellAlgoSwitch.SpectrumCloudEnhSwitch parameter.
● Configuring NR dedicated spectrum resources
NR dedicated spectrum resources are configured at one end of the NR
bandwidth. The NR dedicated uplink spectrum resources can be identical to or
differ from NR dedicated downlink spectrum resources.
– When only the NR parameters
gNBDULteNrSpctShrCg.NrReservedRbStartIndex and
gNBDULteNrSpctShrCg.NrReservedRbEndIndex are used to configure
the dedicated spectrum, the same dedicated spectrum resources are
configured in the uplink and downlink.
– In addition to the preceding two parameters, if the NR parameters
gNBDULteNrSpctShrCg.NrUlReservedRbStartIndex and
gNBDULteNrSpctShrCg.NrUlReservedRbEndIndex are configured, the
uplink dedicated spectrum configuration takes the values of these two
parameters, and the downlink dedicated spectrum configuration still
takes the values of the
gNBDULteNrSpctShrCg.NrReservedRbEndIndex parameters.
● Configuring LTE and NR spectrum sharing cell groups
– Add a planned LTE cell to an LTE spectrum sharing cell group by setting
LteNrSpctShrCellGrp.LteNrSpectrumShrCellGrpId.
– Add a planned NR cell to the NR spectrum sharing cell group by setting

(2021-12-30)
SingleRAN
– Frame offset: Set the LTE parameter CellFrameOffset.FrameOffset or

on the LTE side. If both parameters are configured, the value of the
CellFrameOffset.FrameOffset parameter is used. 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 is used.
– TA offset: Set the LTE parameter CellFrameOffset.TaOffset and NR
parameter NRDUCell.TaOffset.
After this function is enabled, LTE and NR cells in the associated spectrum sharing
cell groups can share spectrum resources on a shared spectrum segment. Figure
4-2 shows the time-frequency resource sharing between LTE and NR cells.
volumes.
Figure 4-2 Time-frequency resource sharing between LTE and NR cells

Some channels will conflict with each other during LTE and NR spectrum sharing.
Such conflicts can be avoided by properly coordinating uplink and downlink
physical channel resource scheduling, improving spectrum usage.

(2021-12-30)
SingleRAN

Figure 4-3 shows the positions of uplink physical channels after this function is
enabled.
The uplink physical channel resources are coordinated and scheduled as follows:
● LTE and NR sounding reference signals (SRSs): SRSs can be configured either
for both LTE and NR or for only NR. SRS configuration is controlled by the
– When this option is selected, SRSs resources are only allocated to NR and
are not allocated to LTE.
– When this option is deselected, SRS resources are allocated to both LTE
and NR.
In this scenario, LTE reserves subframes 0 and 5 for NR as cell-specific
SRS subframes. When LTE UEs are scheduled on subframes during which
NR SRSs are transmitted, the uplink MCS index decreases, affecting the
uplink data rates of LTE UEs. LTE and NR SRS resource allocation
optimization can be enabled by selecting the
LTE_NR_SRS_ALLOC_OPT_SW option of the
LteNrSpctShrCellGrp.LteNrSpctShrSwitch parameter. After the
optimization, LTE reserves only subframe 0 for NR as the cell-specific SRS
subframe, reducing the impact of NR SRS subframes on the uplink data
rates of LTE UEs.
● LTE PUCCH: The LTE PUCCH is configured in the shared spectrum and the
number of RBs for the LTE PUCCH adheres to the common configuration

(2021-12-30)
SingleRAN
rules. The LTE PUCCH is not restricted by the deployment position of the NR
PUCCH. For details, see 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, it may interfere with SRSs, affecting
network performance.
● NR PUCCH: The NR PUCCH is deployed in the NR dedicated spectrum. The
number of RBs for 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 or NSA and
SA hybrid networking, the NR PUCCH always includes the common PUCCH,
which occupies four RBs. For details about the common PUCCH, see the
descriptions of the PUCCH in Channel Management in 5G RAN Feature
Documentation.
● LTE PRACH: The LTE PRACH is configured adjacent to the LTE PUCCH at the
lower end, and always occupies six RBs.
● NR PRACH: The NR PRACH is deployed in the NR dedicated spectrum. The
number of RBs for the NR PRACH is configured by a parameter. For details
about the PRACH, see Channel Management in 5G RAN Feature
Documentation.
● LTE and NR PUSCHs: The total available shared PUSCH resources for LTE and
NR equal the total shared spectrum resources minus the resources occupied
by the LTE PUCCH and LTE PRACH. The total available shared PUSCH
resources for LTE and NR are dynamically shared between them based on
traffic requirements.

Downlink physical channel resources are coordinated and scheduled as follows:
● The frequency-domain positions of the NR SSB and system information on the
NR PDSCH are within the NR dedicated spectrum. Therefore, the NR SSB and
system information do not conflict with the LTE system information, CRSs/CSI-
RS, or SS/PBCH.
● In the NR shared spectrum, the NR PDSCH uses CRS rate matching to avoid
conflicts with LTE CRSs. NR UEs scheduled in the shared spectrum must
support 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. UEs that do not support CRS rate matching can be scheduled only in
the dedicated spectrum.
When the number of LTE CRS ports (specified by the LTE parameter
Cell.CrsPortNum) is 1, the LTE_CRS_PORT_1_RM_SW option of the NR
parameter gNBDULteNrSpctShrCg.FddLteNrSpctShrSwitch can be selected
so that the NR PDSCH performs CRS rate matching in the pattern of one LTE
CRS port. CRS rate matching in the pattern of one LTE CRS port is supported
only when the cells use the independent power configuration mode (LTE
parameter SpectrumCloud.SpctShrMode set to
LTE_NR_PWR_INDEPENDENT). If CRS rate matching in the pattern of one
LTE CRS port is not enabled, the NR PDSCH performs CRS rate matching in
the pattern of two LTE CRS ports even when only one CRS port is configured.

(2021-12-30)
SingleRAN
When two or four CRS ports are configured, the NR PDSCH performs CRS rate
matching in the pattern of two or four LTE CRS ports.
● The LTE CSI-RS/CRSs/DMRS/SS/PBCH and NR CSI-RS/TRSs/PDCCH avoid
conflicts with each other through statically coordinated scheduling.
● The conflict avoidance between the NR UE-specific PDCCH and LTE PDCCH/
PCFICH/PHICH is related to the setting of the
UE_PDCCH_FULL_BANDWIDTH_CFG_SW option of the
NRDUCellPdcch.PdcchAlgoExtSwitch parameter. The UE-specific PDCCH is
configured through NR parameters NRDUCellPdcch.SpctShrStartSymbol and
NRDUCellPdcch.OccupiedSymbolNum.
– When this option is selected, the NR UE-specific PDCCH and the LTE
PDCCH/PCFICH/PHICH are transmitted on different symbols and
therefore do not conflict with each other. The LTE PDCCH occupies at
least one symbol (in the case of one or two LTE CRS ports) or two
symbols (in the case of four LTE CRS ports), and the number of symbols
occupied by the NR UE-specific PDCCH can be set to 1 or 2 by using NR
parameters.
– When this option is deselected, the NR UE-specific PDCCH spans over the
NR dedicated spectrum, and the NR UE-specific PDCCH and LTE PDCCH/
PCFICH/PHICH are transmitted in different frequency-domain positions to
avoid each other. The NR UE-specific PDCCH can occupy one to three
symbols, depending on parameter configurations.
● The frequency-domain position of the NR common PDCCH is within the NR
dedicated spectrum. Therefore, the NR common PDCCH and LTE PDCCH/
PCFICH/PHICH are transmitted in different frequency-domain positions to
avoid each other. When the NR parameter
NRDUCellCoreset.CommonCtrlResStartSymbol is set to a valid value, the
common PDCCH is configured through the
NRDUCellCoreset.CommonCtrlResStartSymbol and
NRDUCellCoreset.CommonCtrlResRbNum parameters. When the NR
parameter NRDUCellCoreset.CommonCtrlResStartSymbol is set to an
invalid value, the NR common PDCCH and UE-specific PDCCH are both
configured through the NRDUCellPdcch.SpctShrStartSymbol,
NRDUCellPdcch.OccupiedSymbolNum, and
NRDUCellCoreset.CommonCtrlResRbNum parameters.
● The LTE and NR PDSCHs mutually avoid conflicts with each other through
dynamically coordinated scheduling. In addition, the LTE PDSCH actively
avoids conflicts with the NR CSI-RS/TRSs/PDCCH through dynamic scheduling,
and the NR PDSCH actively avoids conflicts with the LTE CRSs/CSI-RS/SS/
PBCH/PHICH/PCFICH/PDCCH through dynamic scheduling.
– The NR PDSCH can avoid conflicts with the LTE CSI-RS at the RE or
subframe level. When the LTE_CSI_RS_AVOID_POLICY_SW option of the
LTE parameter LteNrSpctShrCellGrp.LteNrSpctShrSwitch and the
LTE_CSI_RS_AVOID_SW option of the NR parameter
gNBDULteNrSpctShrCg.FddLteNrSpctShrSwitch are both selected,
conflicts are avoided at the RE level. That is, the NR PDSCH avoids the
REs occupied by the LTE CSI-RS. In other circumstances, conflicts are
avoided at the subframe level. That is, the NR PDSCH avoids the
subframes occupied by the LTE CSI-RS.
When the TX/RX mode of the LTE and NR cells is 8T8R, RE-level
avoidance between the NR PDSCH and LTE CSI-RS is not supported.

(2021-12-30)
SingleRAN
– The NR PDSCH supports RB- and symbol-level avoidance of the LTE SS/
PBCH through rate matching. You can select the
LTE_SS_PBCH_RM_OPT_SW option of the NR parameter
NRDUCellAlgoSwitch.SpectrumCloudEnhSwitch to enable the NR
PDSCH to use one pattern for SS/PBCH rate matching. When this option
is deselected, the NR PDSCH uses two patterns for SS/PBCH rate
matching. This option can be set based on the network plan. When the
NR PDSCH uses two rate matching patterns, the avoidance is more
accurate and at the same time more pattern resources are consumed,
compared with when one rate matching pattern is used.
● The NR PDCCH and PDSCH can share spectrum resources in TDM and FDM
modes. The spectrum resource sharing in TDM mode is supported by default
and does not require parameter configuration. The spectrum resource sharing
in FDM mode is supported only when PDCCH rate matching is enabled by
selecting the PDCCH_RATEMATCH_SW option of the NR parameter
NRDUCellPdsch.RateMatchSwitch. PDCCH rate matching applies only to
peak rate scenarios. For details about its network impact, see Scheduling in
5G RAN Feature Documentation.
When this function is enabled, the PDCCH_RATEMATCH_COMPATIBLE_SW
option of the NR parameter NRDUCellPdsch.RateMatchSwitch can be
selected to solve compatibility issues of some UEs.
● The position of the downlink additional DMRS can be configured on the NR
PDSCH by setting the NR parameter NRDUCellPdsch.DlAdditionalDmrsPos,
to improve user experience. In mobility scenarios, this parameter is set to
POS1. In fixed-point scenarios, this parameter is set to NOT_CONFIG.
● The NR PDSCH performs rate matching for all RB resources on LTE CRS
symbols to eliminate the interference of neighboring LTE cells on the NR
spectrum sharing cell.
– If the LTE spectrum sharing cell and other neighboring LTE cells are
configured with the same number of CRS ports, the
LTE_CRS_RATEMATCH_ALL_SYM_SW option of the NR parameter
NRDUCellAlgoSwitch.SpectrumCloudEnhSwitch is selected to support
this function. In this case, rate matching is performed based on the
configured number of CRS ports.
– If the number of CRS ports configured for the LTE spectrum sharing cell
differs from that configured for other neighboring LTE cells, the
LTE_CRS_RM_ALL_SYM_4PORT_SW option of the NR parameter
NRDUCellAlgoSwitch.SpectrumCloudEnhSwitch is selected to support
this function. In this case, if the NR PDSCH performs CRS rate matching
in the pattern of the configured number of LTE CRS ports, the
interference of neighboring LTE cells on the NR spectrum sharing cell
cannot be completely eliminated. Therefore, rate matching is performed
in the pattern of four LTE CRS ports.
● The NR PDSCH and SSB can share spectrum resources in TDM and FDM
modes. The spectrum resource sharing in TDM mode is supported only when
SSB rate matching is enabled by selecting the SSB_RATEMATCH_SW option
of the NR parameter NRDUCellPdsch.RateMatchSwitch. The spectrum
resource sharing in FDM mode is supported by default and does not require
parameter configuration. SSB rate matching applies only to peak rate
scenarios. For details about its network impact, see Scheduling in 5G RAN
Feature Documentation.

(2021-12-30)
SingleRAN
The NR SSB frequency domain can be configured to improve spectrum

resource usage on the NR side. The details are as follows:
– 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. In SA networking, this parameter needs to be set to
SSB_DESC_TYPE_GSCN, which indicates the 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 by the value of the
NRDUCell.SsbDescMethod parameter. The specific parameter value for
this function must be confirmed by Huawei engineers.
Before configuring the preceding two parameters, you need to ensure that the
number of RBs for common control resources in the cell meets the
requirements of Hybrid DSS Based on Asymmetric Bandwidth. If the
NRDUCellPdcch.OccupiedSymbolNum parameter is set to 1SYM, you need
to set the NRDUCellCoreset.CommonCtrlResRbNum parameter to RB48. If
the NRDUCellPdcch.OccupiedSymbolNum parameter is set to 2SYM, you
need to set the NRDUCellCoreset.CommonCtrlResRbNum parameter to
RB24 or RB48.
4.1.2 Enhanced Functions of Hybrid DSS Based on Asymmetric

Bandwidth
4.1.2.1 Flexible Spectrum Priority Modes
Configuration of the Percentages of Spectrum Resources to Be Preferentially

Allocated
To ensure proper allocation of shared resources, the percentages of shared
resources preferentially allocated to the LTE and NR cells for MBB services can be
set based on their traffic volume requirements. The resources here refer to the
PUSCH and PDSCH resources. The percentage for LTE is specified by the
LteNrSpctShrCellGrp.LteNrSpctShrLtePriResRatio parameter, and the
percentage for NR is equal to 100% minus the value of this parameter. Shared
spectrum resources are allocated based on these percentages as follows:
● When the ratios of actual traffic volume requirements of the LTE and NR cells
to the total shared spectrum resources are both less than, or both exceed, the
percentages of resources preferentially allocated, spectrum resources are
allocated based on the percentages of resources preferentially allocated to
each cell.
● When the actual traffic volume requirement of the cells of one RAT (RAT 1)
exceeds the percentage of resources preferentially allocated to that RAT, and
the actual traffic volume requirement of the cells of the other RAT (RAT 2)
does not, the unused resources for RAT 2 can be occupied by RAT 1. For
example, if the percentage of resources preferentially allocated to the LTE cell
is 60%, and the actually required LTE resource percentage is 70%, and if the

(2021-12-30)
SingleRAN
percentage of resources preferentially allocated to the NR cell is 40%, and the

actually required NR resource percentage is 35%, the unused 5% of resources
for the NR cell can be used by the LTE cell. As a result, the LTE cell can use
65% of the shared spectrum resources.
In addition to the preceding allocation principles, the setting of the
LNR_RES_ALLOC_ADAPT_SW option of the
LteNrSpctShrCellGrp.LteNrSpctShrSwitch parameter also affects the actual
allocation of spectrum resources.
● If this option is selected, the system allocates spectrum resources based on
the percentage specified by the
LteNrSpctShrCellGrp.LteNrSpctShrLtePriResRatio parameter, for whichever
direction (uplink or downlink) with the larger sum of traffic volume
requirements of the LTE and NR cells. For the other direction, the system
dynamically allocates spectrum resources based on the actual traffic volume
requirements of the LTE and NR cells. For example, if the sum of the uplink
traffic volumes of the LTE and NR cells is greater than the sum of the
downlink traffic volumes of the LTE and NR cells, the uplink spectrum
resources are allocated to the LTE and NR cells based on the percentage
specified by the LteNrSpctShrCellGrp.LteNrSpctShrLtePriResRatio
parameter. The downlink spectrum resources are allocated to the LTE and NR
cells based on their actual traffic volume requirements.
● If this option is deselected, the system allocates the sum of the uplink and
downlink spectrum resources of the LTE and NR cells based on the value of
the LteNrSpctShrCellGrp.LteNrSpctShrLtePriResRatio parameter.
Table 4-2 lists the counters used for measuring the shared spectrum resources
occupied by the LTE and NR cells in the uplink and downlink.
Table 4-2 Counters for measuring the number of uplink and downlink available
RBs in LTE and NR cells
1526759050 L.ChMeas.PRB.UL.Actual.Avail
1526759052 L.ChMeas.PRB.UL.PUSCH.Actual.Avai
l
1526759051 L.ChMeas.PRB.DL.Actual.Avail
1911827161 N.PRB.UL.Actual.Avail.Avg
1911827162 N.PRB.UL.PUSCH.Actual.Avail.Avg
1911827160 N.PRB.DL.Actual.Avail.Avg
Inter-RAT Preferential Guarantee for GBR Services

If the percentage of resources preferentially allocated to a RAT is less than the
percentage required by guaranteed bit rate (GBR) services of that RAT, experience
of GBR services of that RAT will be affected. For example, if the percentage of
resources preferentially allocated to LTE is 40% and the percentage required by

(2021-12-30)
SingleRAN
GBR services is 60%, 20% of GBR service requirements cannot be satisfied,

affecting GBR service experience.
The function of inter-RAT preferential guarantee for GBR services is introduced.
This function defines the priority of GBR services as follows: The priority of LTE
GBR services is higher than that of NR non-GBR services, and the priority of NR
GBR services is higher than that of LTE non-GBR services. In the preceding
example, the unsatisfied LTE GBR services can occupy the resources of NR non-
GBR services. In this way, GBR service experience is preferentially guaranteed.
This function is enabled when the GBR_PRI_ALLOC_SW option of the LTE
parameter LteNrSpctShrCellGrp.LteNrSpctShrSwitch is selected. For details
about LTE GBR and non-GBR services, see Scheduling in eRAN Feature
Documentation. For details about NR GBR and non-GBR services, see QoS
Management in 5G RAN Feature Documentation.
4.1.2.2 Flexible Power Allocation Mode

This function supports flexible power allocation modes specified by the LTE
parameter SpectrumCloud.SpctShrMode. When this parameter is set to
LTE_NR_PWR_DYN_SHR_WITH_SPCT, the LTE and NR cells share the same power
on the shared spectrum, and the percentage of power allocated to a RAT is equal
to the percentage of shared spectrum allocated to that RAT. When this parameter
is set to LTE_NR_PWR_INDEPENDENT, the LTE and NR cells use independently
configured spectrum power on the shared spectrum.
Figure 4-4 uses a 2 x 60 W RF module serving a 20 MHz LTE cell and a 30 MHz
NR cell to illustrate power allocation modes.
In independent power configuration mode, the maximum transmit power that can
be configured for the LTE cell is 2 x 24 W, and that for the NR cell is 2 x 36 W. The
LTE and NR cells each use 2 x 24 W power on the shared spectrum, and the NR
cell exclusively uses 2 x 12 W power.
In spectrum power sharing mode, the power configured for the LTE and NR cells
must be greater than or equal to the power in independent power configuration
mode. The LTE cell can be configured with a transmit power ranging from 2 x 24
W to 2 x 40 W, and the NR cell can be configured with a transmit power ranging
from 2 x 36 W to 2 x 60 W. The LTE and NR cells can minimally share the total
power of 2 x 24 W on the shared spectrum, and the NR cell exclusively uses the 2
x 12 W power. The spectrum power sharing mode helps save the transmit power
by 2 x 24 W (2 x 60 W – 2 x 36 W), compared with the independent power
configuration mode.

(2021-12-30)
SingleRAN
Figure 4-4 Power allocation mode
Assuming that the cell power configurations are the same, the independent power
configuration mode results in better capacity performance but higher power
consumption, whereas the spectrum power sharing mode reduces power
consumption but leads to a capacity performance loss. Therefore, when the power
is sufficient, independent power configuration mode is preferred. When the power
is insufficient, spectrum power sharing mode can be used.
In spectrum power sharing mode, the PSD of the NR cell can be adaptively
adjusted. When the transmit power required by the NR cell exceeds the configured
power, the gNodeB adaptively reduces the PSD of the NR cell to ensure that the
NR cell can use more spectrum resources, improving the spectral efficiency of NR
UEs. This function is enabled when the PWR_SPCT_DENSITY_ADAPT_SW option
of the NR parameter NRDUCellAlgoSwitch.SpectrumCloudEnhSwitch is selected.
After this function is enabled, the gNodeB adaptively adjusts the PSD of data
channels to improve the spectral efficiency of UEs in the NR cell.
When spectrum power sharing mode is used, and the LTE and NR baseband
processing units need to be connected to the RRU through their respective optical
fiber, the LNR_PWR_WITH_SPCT_OPT_SW option of the LTE parameter
SpectrumCloud.SpectrumCloudEnhSwitch must be selected. When independent
power configuration mode is used, LTE and NR can use their respective optical
fiber over the CPRI interface without selecting this option.
4.1.2.3 Co-carrier Co-CPRI Data

After Hybrid DSS Based on Asymmetric Bandwidth is enabled, the LTE and NR cells
each occupy a portion of CPRI bandwidth. When LTE and NR share the same CPRI
optical fibers (either the LTE baseband processing unit or the NR baseband
processing unit is connected directly to the RRU through an optical fiber) and the
CPRI bandwidth is insufficient, they can be configured to share the same carrier
and CPRI data resources in order to meet CPRI bandwidth requirements. The LTE
and NR co-carrier co-CPRI data function enables LTE and NR cells to share a

(2021-12-30)
SingleRAN
portion of CPRI bandwidth, and is enabled when the LTE parameter

LteNrSpctShrCellGrp.LteNrCoCarrCoCpriDataSw is set to ON. 32T32R cells do
not support the co-carrier co-CPRI data function.
When the LTE and NR co-carrier co-CPRI data function is enabled, only the
spectrum power sharing mode is supported. That is, the
SpectrumCloud.SpctShrMode parameter must be set to
LTE_NR_PWR_DYN_SHR_WITH_SPCT.
When the LTE and NR co-carrier co-CPRI data function and the CPRI compression
function are both enabled, the CPRI compression ratios must be the same between
the LTE and NR cells. For details about the configuration requirements, see 4.1.3
Application Scenarios of Simultaneous Use of Hybrid DSS Based on
Asymmetric Bandwidth and Other Functions.
4.1.3 Application Scenarios of Simultaneous Use of Hybrid

DSS Based on Asymmetric Bandwidth and Other Functions
Simultaneous Use with NB-IoT Deployed in LTE Guard Band Mode
For 3900 and 5900 series base stations, Hybrid DSS Based on Asymmetric
Bandwidth can work together with NB-IoT deployed in LTE guard band mode. The
NB-IoT can only be deployed at one end of the guard band on the LTE side.
In this scenario, the spectrum occupied by the NB-IoT cell and the spectrum
occupied by the NR cell overlap, causing severe mutual interference. As a result,
the NB-IoT cell or NR cell becomes unavailable. Specifically:
● If the NB-IoT cell is configured and activated prior to the NR cell, the NR cell
cannot be activated.
● If the NR cell is configured and activated prior to the NB-IoT cell, the NB-IoT
cell cannot be activated.
To eliminate the interference, spectrum resources need to be reserved for the NB-
IoT cell, and the reserved spectrum resources are unavailable for the NR cell. The
uplink and downlink RBs reserved for NB-IoT are configured through the
NRDUCellRbReserve.RbRsvMode, NRDUCellRbReserve.RbRsvType,
NRDUCellRbReserve.RbRsvStartIndex, and NRDUCellRbReserve.RbRsvEndIndex
parameters.
The uplink and downlink RBs reserved for NB-IoT must be confirmed by Huawei
engineers. Table 4-3 lists the recommended number of uplink and downlink RBs
to be reserved in different LTE and NR cell bandwidth scenarios. The
recommended configuration preferentially ensures the NB-IoT cell performance
while considers the NR cell throughput.
For details about NB-IoT deployed in LTE guard band mode, see NB-IoT Basics
(FDD) in eRAN Feature Documentation.

(2021-12-30)
SingleRAN
Table 4-3 Recommended reserved spectrum resources for the NB-IoT cell in
typical scenarios
LTE Cell NR Cell Bandwidth Number of Uplink and Downlink
Bandwidth RBs Reserved for NB-IoT
10 MHz 15 MHz 2
10 MHz 20 MHz 3
15 MHz 20 MHz 3
20 MHz 25 MHz 4
20 MHz 30 MHz 4
20 MHz 40 MHz 5
20 MHz 50 MHz 5

When the co-carrier co-CPRI data function and the 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-4 describes
the configuration requirements.
Table 4-4 Configuration requirements on the CPRI compression types of the LTE
and NR cells
Bandwidth CPRI CPRI Compression CPRI Compression
Compression Type of LTE Cells Type of NR Cells
Ratio
10 MHz 2:1 CPRI ENHANCED_COMPRE 2_COMPRESSION

compression SSION

Compressiona N
15 MHz/20 2:1 CPRI NORMAL_COMPRESSI 2_COMPRESSION

MHz compression ON

Compressiona N
a: The 2.2:1 CPRI compression ratio is required when the cell TX/RX mode is
32T32R, so that CPRI compression can be used together with the co-carrier co-
CPRI data function.

(2021-12-30)
SingleRAN
In Hybrid DSS Based on Asymmetric Bandwidth, the co-carrier co-CPRI data

function needs to work together with CPRI compression in the following scenarios:
● The LTE cell bandwidth is 10 MHz, the NR cell bandwidth is greater than 10
MHz and less than or equal to 20 MHz, and the cell TX/RX mode is greater
than 2T2R. The BBP.WM parameter is set to SPEC_MODE3 for the baseband
processing unit in the baseband equipment to which the LTE cell sector
equipment is bound.
● The LTE cell bandwidth is 10 MHz, the NR cell bandwidth is greater than 10
MHz and less than or equal to 20 MHz, and the cell TX/RX mode is greater
than 2T2R. The BBP.WM parameter is set to SPEC_MODE1 and the
BBP.BBWS parameter is set to LTE_FDD, LTE_FDD and NBIOT, UMTS and
LTE_FDD, UMTS and LTE_FDD and NBIOT for the baseband processing unit in
the baseband equipment to which the LTE cell sector equipment is bound.
For details about CPRI compression, see CPRI Compression in eRAN Feature
Documentation and CPRI Compression in 5G RAN Feature Documentation.

When Hybrid DSS Based on Asymmetric Bandwidth is used together with LTE
downlink semi-persistent scheduling, the upper limit on the proportion of RBs that
can be allocated for LTE downlink semi-persistent scheduling is configurable
(through the SpectrumCloud.DlSpsRestrictRatio parameter). This proportion
together with the percentage of spectrum resources to be preferentially allocated
to LTE for MBB services (specified by the LTE parameter
LteNrSpctShrCellGrp.LteNrSpctShrLtePriResRatio) x 100%.
Simultaneous Use with WBB

If Hybrid DSS Based on Asymmetric Bandwidth is used together with WBB, it is
recommended that the WBB_MBB_CONTROL_OPT_SW option of the
SpectrumCloud.SpectrumCloudEnhSwitch parameter be selected. When this
option is selected, the base station allocates resources to LTE WBB and MBB
services based on the actually available LTE spectrum resources. The percentages
of resources actually allocated to WBB and MBB services comply with the settings
of the CellWttxParaCfg.MbbUserDlPrbUpLimit,
CellWttxParaCfg.MbbUserUlPrbUpLimit,
CellWttxParaCfg.WbbUserDlPrbUpLimit, and
CellWttxParaCfg.WbbUserUlPrbUpLimit parameters. For details about WBB, see
WBB in eRAN Feature Documentation.
To ensure spectral efficiency, it is recommended that the following equations be
met: CellWttxParaCfg.MbbUserDlPrbUpLimit +
CellWttxParaCfg.WbbUserDlPrbUpLimit = 100,
CellWttxParaCfg.MbbUserUlPrbUpLimit +
CellWttxParaCfg.WbbUserUlPrbUpLimit = 100.

(2021-12-30)
SingleRAN
4.1.4 HDSS based on Asymmetric Beam

Static Multiple Beam is one of the LTE FDD multi-sector solutions. Static Multiple
Beam generates at least two beams on the horizontal plane by means of
beamforming, with each beam serving a sector split cell, thereby maximizing
network capacity. HDSS based on Asymmetric Beam enables the two or more LTE
FDD sector split cells served by the beams generated by Static Multiple Beam to
dynamically share the same spectrum resources with an NR FDD cell, improving
spectrum utilization.
Static Multiple Beam can be used in smart 8T8R and 32T32R massive MIMO
modes. In smart 8T8R mode, it supports two beams, which correspond to two LTE
FDD sector split cells. In 32T32R massive MIMO mode, it supports two to four
beams, which correspond to two to four LTE FDD sector split cells. For details
about Static Multiple Beam in smart 8T8R mode, see Smart 8T8R (FDD). For
details about Static Multiple Beam in 32T32R massive MIMO mode, see Massive
MIMO (FDD). The principles of HDSS based on Asymmetric Beam are the same in
these two scenarios, with the only difference in the number of LTE FDD sector split
cells. The following uses the smart 8T8R scenario as an example for illustration.
For ease of description, LTE and NR cells are used to refer to LTE FDD sector split
cells served by the beams generated by Static Multiple Beam and NR FDD cells,
respectively.
This function supports NSA, SA, and NSA and SA hybrid networking. Unless
otherwise specified, the descriptions apply to all networking scenarios. This
function applies to 3900 and 5900 series base stations.
4.1.4.1 Principles
This function enables the two LTE FDD sector split cells served by the two beams
generated by Static Multiple Beam in smart 8T8R mode (referred to as LTE cells)
and an NR FDD cell (referred to as NR cell) to dynamically share time-frequency
resources on a shared spectrum segment based on their traffic volumes. Figure
4-5 illustrates the working principles of this function. The two LTE cells must be
configured with the 20 MHz bandwidth, and the NR cell must be configured with
the 40 MHz bandwidth. In addition, LTE and NR cells must be added to associated
spectrum sharing cell groups. Specifically:
volumes. The two LTE cells are allocated the same resources.

(2021-12-30)
SingleRAN
Figure 4-5 HDSS based on Asymmetric Beam

sharing cell groups. In addition, the LTE and NR cells sharing spectrum resources
must have aligned radio frames and subframes.
● Turning on function switches on the LTE and NR sides and configuring NR

dedicated spectrum resources
LTE_NR_SPECTRUM_SHR, and select the
LNR_SPECTRUM_SHR_ASYM_SW option of the
SpectrumCloud.SpectrumCloudEnhSwitch parameter for both LTE cells.
NRDUCellAlgoSwitch.SpectrumCloudSwitch parameter, and select the
LTE_NR_FDD_SPCT_SHR_ASYM_SW option of the
NRDUCellAlgoSwitch.SpectrumCloudEnhSwitch parameter.
– Configuring NR dedicated spectrum resources
NR dedicated spectrum resources are configured at one end of the NR
bandwidth. The amount of NR dedicated uplink spectrum resources can
be identical to or differ from that of NR dedicated downlink spectrum
resources.
▪ If dedicated spectrum resources are configured only by using NR

parameters gNBDULteNrSpctShrCg.NrReservedRbStartIndex and
gNBDULteNrSpctShrCg.NrReservedRbEndIndex, the same
dedicated spectrum resources are configured in the uplink and
downlink.
▪ In addition to the preceding two parameters, if NR parameters

gNBDULteNrSpctShrCg.NrUlReservedRbStartIndex and
gNBDULteNrSpctShrCg.NrUlReservedRbEndIndex are configured,
the uplink dedicated spectrum configuration takes the values of
these two parameters, while the downlink dedicated spectrum
configuration still takes the values of the

(2021-12-30)
SingleRAN
gNBDULteNrSpctShrCg.NrReservedRbEndIndex parameters.
– Configuring LTE and NR spectrum sharing cell groups
▪ Add planned LTE cells to an LTE spectrum sharing cell group by

setting LTE parameters SpectrumCloud.LteNrSpectrumShrCellGrpId
and LteNrSpctShrCellGrp.LteNrSpectrumShrCellGrpId. Both LTE
cells must be added to the LTE spectrum sharing cell group.
▪ Configure an association between the LTE spectrum sharing cell

group and an NR spectrum sharing cell group through NR
parameters gNBDULteNrSpctShrCg.NrSpctShrCellGrpId and
▪ Add a planned NR cell to the NR spectrum sharing cell group by

setting NR parameters NRDUCellSpctCloud.NrDUCellId and
– Configuring the frame offset and TA offset (to ensure the alignment of
radio frames and subframes)
▪ Frame offset: 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 is used. The two LTE
cells must be configured with the same frame offset. 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 is used.
▪ TA offset: Set the LTE parameter CellFrameOffset.TaOffset and NR

parameter NRDUCell.TaOffset.

The uplink and downlink physical channel resource scheduling of LTE and NR cells
need to be properly coordinated during LTE and NR spectrum sharing in this
function. This is to avoid conflicts and improve spectrum utilization.

The two LTE cells in this function use the same spectrum resources through spatial
multiplexing. 3.1.4.2 Key Technologies shows the positions of uplink physical
channels on the spectrum shared by LTE and NR cells.

(2021-12-30)
SingleRAN
The uplink physical channel resources of the LTE cells need to be merged before
spectrum sharing with the NR cell. Table 4-5 describes how the channel resources
are merged.
Table 4-5 Uplink physical channel resource merging of LTE cells
Chan Merging Mode

nel
PUCC The combined PUCCH and PRACH resources of the two LTE cells is used
H as the total resources of the two channels allocated to the LTE cells. If
these resources are not fully occupied by the PUCCH and PRACH of the
PRAC two LTE cells, the idle resources can be used by the PUSCH of the LTE
H cells.
SRS The larger amount of SRS time-frequency resources between the two
LTE cells is considered as shared SRS resources allocated to the LTE and
NR cells.
PUSC The larger amount of PUSCH resources between the two LTE cells is
H considered as the PUSCH resources allocated to LTE cells.
Spectrum resources allocated to the NR cell are equal to the total shared
spectrum resources minus the spectrum resources allocated to the two LTE cells.
The spectrum resources allocated to the two LTE cells are the sum of the channel
resources described in Table 4-5.

(2021-12-30)
SingleRAN
For details about the coordinated scheduling of uplink physical channel resources,
see 3.1.1.2 Key Technologies.

The downlink physical channel resources of the LTE cells need to be merged
before spectrum sharing with the NR cell. Table 4-6 describes how the channel
resources are merged.
Table 4-6 Downlink physical channel resource merging of LTE cells
Channel Merging Mode
CRS Choose the LTE performance preferred or NR performance

preferred policy based on the network plan.
● LTE performance preferred: LTE cells must have different
PCIs as well as different PCI mod 3 values. In this case, LTE
cells have two or three CRS patterns. The
parameter must be selected to enable rate matching on all
RBs in the symbols where LTE CRSs appear, so as to
eliminate the interference of LTE cells on the NR cell.
● NR performance preferred: LTE cells must have different
PCIs but the same PCI mod 3 value. In this case, LTE cells
have the same CRS pattern. The
parameter must be deselected to allow the gNodeB to
perform CRS rate matching based on one LTE CRS pattern.
SS/PBCH The SS/PBCH time-frequency domain positions of the LTE cells

are the same.
PDCCH The larger number of PDCCH symbols between the two LTE
cells is used as the number of PDCCH symbols of these LTE
cells.
PDSCH The larger amount of PDSCH resources between the two LTE
cells is used as the amount of PDSCH resources of these LTE
cells.
For details about the coordinated scheduling of downlink physical channel

resources, see 4.1.1.2 Key Technologies.
4.1.4.3 Enhanced Functions
Flexible Spectrum Priority Mode

The two LTE cells must be added to the same LTE spectrum sharing cell group, and
must be configured with the same percentage of spectrum resources to be

(2021-12-30)
SingleRAN
preferentially allocated. For details about the flexible spectrum priority mode, see
3.1.2.1 Flexible Spectrum Priority Mode.
Flexible Power Allocation Mode

The two LTE cells must be configured with the same power allocation mode. For
details about the power allocation mode, see 3.1.2.2 Flexible Power Allocation
Mode.
Co-carrier Co-CPRI Data

For details, see 3.1.2.3 Co-carrier Co-CPRI Data.
LTE Key Event Assurance

cells in NSA networking when the LTE cells are heavily loaded in scenarios such as
LteNrSpctShrCellGrp.LteNrSpctShrSwitch, and LTE parameters
LteNrSpctShrCellGrp.LteBigEventUeNumThld and
LteNrSpctShrCellGrp.LteBigEventUeNumThldOffset need to be configured to
specify the LTE key event user number threshold and the threshold offset. The NR
parameter gNBDULteNrSpctShrCg.LteBigEventAssureUeNumThld also needs to
be configured, which specifies the user number threshold for LTE key event
assurance for NR cells. This function is applicable only to Option 3x architecture in
NSA networking.
The LTE key event assurance function is triggered when the following conditions
are met:
● Either of the LTE cells meets this condition: Number of LTE UEs in RRC
connected mode > LteNrSpctShrCellGrp.LteBigEventUeNumThld +
data split modes for the NR cell change to MCG only. The NR cell enters the LTE
key event assurance state, and all the shared spectrum resources are allocated to
the two LTE cells to ensure their capacity.
When the number of LTE UEs in RRC connected mode in both LTE cells becomes
less than or equal to LteNrSpctShrCellGrp.LteBigEventUeNumThld minus
LteNrSpctShrCellGrp.LteBigEventUeNumThldOffset, the NR cell exits the LTE
key event assurance state and enters the non-LTE-key-event-assurance state.
To protect the NR cell from ping-pong switchovers between these two states, a 5-
minute protection timer is introduced to the NR cell.

(2021-12-30)
SingleRAN
4.1.4.4 Simultaneous Use of HDSS based on Asymmetric Beam and Other

Functions

The LTE and NR cells enabled with HDSS based on Asymmetric Beam must have
the same CPRI compression ratio. For details about the configuration
requirements, see Simultaneous Use with CPRI Compression in 4.1.3
Application Scenarios of Simultaneous Use of Hybrid DSS Based on
Asymmetric Bandwidth and Other Functions.

When HDSS based on Asymmetric Beam is used together with LTE downlink semi-
persistent scheduling, the upper limit on the proportion of RBs that can be
allocated for LTE downlink semi-persistent scheduling is configurable (through the
SpectrumCloud.DlSpsRestrictRatio parameter). It is recommended that this
parameter be set to the same value, and that the SpsSchSwitch option of the
CellAlgoSwitch.DlSchSwitch parameter be set to the same value for the two LTE
cells. This proportion together with the percentage of spectrum resources to be
preferentially allocated to LTE for MBB services (specified by the LTE parameter
LteNrSpctShrCellGrp.LteNrSpctShrLtePriResRatio/100)%.

When downlink intra-FR inter-band CA is enabled after HDSS based on
Asymmetric Beam is enabled, the NR PUCCH occupies more RBs. The RBs occupied
recommended that the start position of the LTE PUCCH at the lower end of the
frequency domain (CellRbReserve.RbRsvStartIndex) and the end position of the
LTE PUCCH at the upper end of the frequency domain
(CellRbReserve.RbRsvEndIndex) be symmetrically configured adjacent to the NR
PUCCH. The two LTE cells must have the same PUCCH RB configuration.
complete.
Simultaneous Use with LTE PRACH Frequency-Domain Position Adaptation

When HDSS based on Asymmetric Beam is enabled, PRACH frequency-domain
position adaptation is turned on for only one LTE cell, and the PRACH frequency-
domain positions between these two LTE cells are different, more resources are
allocated to the LTE cells and fewer resources are allocated to the NR cell.
Therefore, it is recommended that the PrachFreqAdjSwitch option of the

(2021-12-30)
SingleRAN
CellAlgoSwitch.RachAlgoSwitch parameter be set to the same value for the two

LTE cells.
Simultaneous Use with LTE Uplink Semi-persistent Scheduling and LTE TTI
Bundling
When HDSS based on Asymmetric Beam is enabled, uplink semi-persistent
scheduling is enabled in only one LTE cell and takes effect, and TTI bundling is
enabled only in the other LTE cell and takes effect, the resources for semi-
persistent scheduling and those for TTI bundling are respectively merged for these
two LTE cells, and consequently the resources for the NR cell decrease. Therefore,
it is recommended that the two LTE cells use the same settings of the
TtiBundlingSwitch and SpsSchSwitch options of the
CellAlgoSwitch.UlSchSwitch parameter.
4.2.1 Benefits
This function increases cell downlink throughput as follows:
● Average downlink throughput of an NR cell = N.ThpVol.DL.Cell/
N.ThpTime.DL.Cell
● Average downlink throughput of an LTE cell = L.Thrp.bits.DL/
L.Thrp.Time.Cell.DL.HighPrecision
Table 4-7 and Table 4-8 list the gains provided by this function in NSA, SA, and
NSA and SA hybrid networking compared with a typical static refarming solution.
Table 4-7 Average cell downlink throughput gain (with HDSS based on
Asymmetric Beam disabled)

Gainb Gainb
2T 15 MHz 10 MHz 5 MHz 90%–100% 250%–300%
20 MHz 10 MHz 10 MHz 90%–100% 175%–200%
20 MHz 15 MHz 5 MHz 90%–100% 355%–400%
25 MHz 20 MHz 5 MHz 95%–100% 465%–500%
30 MHz 20 MHz 10 MHz 95%–100% 250%–295%
40 MHz 20 MHz 20 MHz 95%–100% 175%–200%
4T 15 MHz 10 MHz 5 MHz 90%–100% 240%–290%
20 MHz 10 MHz 10 MHz 90%–100% 165%–190%
20 MHz 15 MHz 5 MHz 90%–100% 350%–390%

(2021-12-30)
SingleRAN

Gainb Gainb
25 MHz 20 MHz 5 MHz 95%–100% 455%–485%
30 MHz 20 MHz 10 MHz 95%–100% 240%–280%
40 MHz 20 MHz 20 MHz 95%–100% 165%–190%
8T 40 MHz 20 MHz 20 MHz 92%–100% 162%–190%
20 MHz 15 MHz 5 MHz 95%–100% 355%–400%
20 MHz 10 MHz 10 MHz 95%–100% 165%–190%
15 MHz 10 MHz 5 MHz 95%–100% 240%–280%
25 MHz 20 MHz 5 MHz 95%–100% 455%–485%
30 MHz 20 MHz 10 MHz 95%–100% 240%–280%
32T 40 MHz 20 MHz 20 MHz 83%–95% 162%–190%
20 MHz 15 MHz 5 MHz 85%–95% 355%–400%
20 MHz 10 MHz 10 MHz 85%–95% 165%–190%
15 MHz 10 MHz 5 MHz 85%–95% 240%–280%
25 MHz 20 MHz 5 MHz 85%–95% 455%–485%
30 MHz 20 MHz 10 MHz 85%–95% 240%–280%

static refarming solution. If the LTE_CRS_RATEMATCH_ALL_SYM_SW or
NRDUCellAlgoSwitch.SpectrumCloudEnhSwitch is selected, the NR cell gain
decreases by 15% to 30%, and the LTE cell gain is not affected.
Table 4-8 Average cell downlink throughput gain (with HDSS based on
Asymmetric Beam enabled)

Gainb Gainb
8T LTE 40 MHz 20 MHz 20 MHz 92%–100% 100%–114%

performa
nce 20 MHz 15 MHz 5 MHz 95%–100% 200%–220%
preferred 20 MHz 10 MHz 10 MHz 95%–100% 132%~140%

(2021-12-30)
SingleRAN

Gainb Gainb
15 MHz 10 MHz 5 MHz 95%–100% 164%–180%
25 MHz 20 MHz 5 MHz 95%–100% 220%–260%
30 MHz 20 MHz 10 MHz 95%–100% 164%–180%
8T NR 40 MHz 20 MHz 20 MHz 76%–80% 165%–190%

performa
nce 20 MHz 15 MHz 5 MHz 57%–60% 355%–400%
preferred 20 MHz 10 MHz 10 MHz 76%–80% 165%–190%
15 MHz 10 MHz 5 MHz 76%–80% 240%–280%
25 MHz 20 MHz 5 MHz 76%–80% 455%–485%
30 MHz 20 MHz 10 MHz 76%–80% 240%~280%
32T LTE 40 MHz 20 MHz 20 MHz 83%–95% 100%–114%

performa
nce 20 MHz 15 MHz 5 MHz 85%–95% 200%–220%
15 MHz 10 MHz 5 MHz 85%–95% 164%–180%
25 MHz 20 MHz 5 MHz 85%–95% 220%–260%
30 MHz 20 MHz 10 MHz 85%–95% 164%–180%
32T NR 40 MHz 20 MHz 20 MHz 66%–76% 165%–190%

performa
nce 20 MHz 15 MHz 5 MHz 68%–76% 355%–400%
15 MHz 10 MHz 5 MHz 68%–76% 240%–280%
25 MHz 20 MHz 5 MHz 68%–76% 455%–485%
30 MHz 20 MHz 10 MHz 68%–76% 240%–280%

static refarming solution. If the LTE_CRS_RATEMATCH_ALL_SYM_SW or
NRDUCellAlgoSwitch.SpectrumCloudEnhSwitch is selected, the NR cell gain
decreases by 15% to 30%, and the LTE cell gain is not affected.
Specific gains can only be achieved when certain conditions are met.

(2021-12-30)
SingleRAN
● The LTE cell gain can only be achieved when all of 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 gain can only be achieved when all of 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).
Actual gains achieved will be less than those listed in the table above if one of the
preceding conditions is not met. However, gains will not be negatively impacted as
a result.
4.2.2 Impacts
Network Impacts
● The impacts on the LTE side are as follows:
– NR reference channels interfere with LTE. The interference leads to LTE
quality-related counters over the full band being inaccurately measured.
These counters include the SINR, RSRQ, full-band CQI, PMI, and RI.
Consequently:
▪ The average cell uplink and downlink IBLER and 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)/
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)/
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)/
Average cell downlink RBLER = (L.Traffic.DL.SCH.QPSK.ErrTB.Rbler
+ L.Traffic.DL.SCH.16QAM.ErrTB.Rbler + L.Traffic.DL.SCH.

(2021-12-30)
SingleRAN
64QAM.ErrTB.Rbler + L.Traffic.DL.SCH.256QAM.ErrTB.Rbler)/
Table 4-9 Counters used for measuring the average cell uplink IBLER
on the LTE side
1526728186 L.Traffic.UL.SCH.QPSK.ErrTB.Ibler
1526728180 L.Traffic.DL.SCH.QPSK.ErrTB.Ibler
1526728187 L.Traffic.UL.SCH.QPSK.ErrTB.Rbler

(2021-12-30)
SingleRAN
1526728181 L.Traffic.DL.SCH.QPSK.ErrTB.Rbler
▪ The access success rate, handover success rate, and RRC connection
reestablishment success rate decrease.
Access success rate = RRC Setup Success Rate
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-13 lists the related
counters.
RRC connection reestablishment success rate = L.RRC.ReEst.Succ/
L.RRC.ReEst.Att. Table 4-14 lists the related counters.

(2021-12-30)
SingleRAN
Table 4-13 Counters used for measuring the handover success rate
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
Table 4-14 Counters used for measuring the RRC connection

reestablishment success rate
1526727086 L.RRC.ReEst.Succ
1526727085 L.RRC.ReEst.Att
▪ The bearer service drop rate increases.

Bearer service drop rate = Service Drop Rate
– After this function is enabled, there are less spectrum resources available
for LTE. This results in a fluctuation in the average uplink and downlink
throughput of the LTE cell, a decrease in the average uplink and downlink
throughput of UEs, and an increase in the uplink and downlink voice
packet loss rates in the LTE cell.
▪ Average uplink cell throughput = Cell Uplink Average Throughput
▪ Average downlink cell throughput = Cell Downlink Average

Throughput
▪ Average uplink UE throughput = User Uplink Average Throughput
▪ Average downlink UE throughput = User Downlink Average

Throughput
▪ Uplink voice packet loss rate in a cell = Uplink Packet Loss Rate
(VoIP)

(2021-12-30)
SingleRAN
▪ Downlink voice packet loss rate in a cell = Downlink Packet Loss

Rate (VoIP)
● The impacts on the NR side are as follows:
After this function is enabled there are less spectrum resources available for
NR. This results in a fluctuation in the average uplink and downlink
throughput of the NR cell, and in a decrease in the average uplink and
downlink throughput of UEs.
– Average uplink cell throughput = Cell Uplink Average Throughput (DU)
(DU)
– Average uplink UE throughput = User Uplink Average Throughput (DU)
(DU)
NOTE
LTE synchronization signals, the PBCH, reference channels, and system information do
not interfere with NR. As a result, NR quality-related counters 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:
– Increased board user-plane CPU usage
▪ Average user-plane CPU usage of an eNodeB board:

L.Traffic.Board.UPlane.CPULoad.AVG
▪ Average user-plane CPU usage of a gNodeB board:

VS.NRBoard.UPlane.CPULoad.Avg
– Increased ping delay on the LTE side
● After this function is enabled on the LTE and NR sides, if MBSFN subframes
are configured on TM9-dedicated carriers, the number of control format
indicators (CFIs) and control channel element (CCE) usage change as the CFI
range differs between MBSFN subframes and common subframes. The CCE
usage can be calculated using the following formula: CCE usage =
(L.ChMeas.CCE.CommUsed + L.ChMeas.CCE.ULUsed +
L.ChMeas.CCE.DLUsed)/L.ChMeas.CCE.Avail.
● When this function works together with the co-carrier co-CPRI data function,
the LTE cell bandwidth is 10 MHz, the NR cell bandwidth is greater than 10
MHz and less than 20 MHz, and the LTE cell is established prior to the NR
cell, the LTE cell will be reestablished to support the co-carrier co-CPRI data
function.
● If the co-carrier co-CPRI data function is enabled and the UE is located near
the cell center, the gNodeB implements time synchronization between the LTE
and NR networks. This has the following impacts:
– On the LTE side: The values of counters L.TA.UE.Index0 to
L.TA.UE.Index6 slightly increase, and the values of counters
L.RA.TA.UE.Index0 to L.RA.TA.UE.Index11 slightly fluctuate.
– On the NR side:
▪ The values of counters N.RA.TA.UE.Index0 to N.RA.TA.UE.Index12

slightly increase.

(2021-12-30)
SingleRAN
▪ If CA is also enabled, the average uplink throughput (Cell Uplink

Average Throughput (DU)) of both the PCell and SCells fluctuates.
▪ If super uplink is also enabled, the average uplink throughput (Cell

Uplink Average Throughput (DU)) of the SUL cell fluctuates.
● If the LTE TA offset (specified by the CellFrameOffset.TaOffset parameter) is
changed from 0TS to another value, the values of counters L.TA.UE.Index0 to
L.TA.UE.Index15 and the values of counters L.RA.TA.UE.Index0 to
L.RA.TA.UE.Index11 slightly fluctuate.
Function Impacts
● Function impacts on the LTE side
Name (eRAN Feature
Documentation)
Uplink CA CaUl2CCSwitch Carrier The number of

option of the Aggregation uplink RBs available
CaMgtCfg.CellC for LTE decreases,
aAlgoSwitch which reduces the
parameter throughput of UEs
for which FDD uplink
CA takes effect.
Downlink CA None Carrier The number of

Aggregation downlink RBs
available for LTE
decreases, which
reduces the
throughput of UEs
for which FDD
downlink CA takes
effect.
Flexible CA MultiCarrierFlex Carrier The number of

from CaSwitch option Aggregation uplink and downlink
Multiple of the RBs available for LTE
Carriers CaMgtCfg.CellC decreases, and the
aAlgoSwitch selected serving cell
parameter combination may
change as a result.

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation)
Downlink DlMassiveCaSwi Carrier It is not

massive CA tch option of the Aggregation recommended that
CaMgtCfg.CellC LTE cells enabled
aAlgoSwitch with this function be
parameter used as PCells, as the
PUCCH overhead
increases so that the
SRS cannot be
configured. As a
result, LTE network
throughput
decreases.
LTE SpectrumCoordi LTE Spectrum The number of

Spectrum nationSwitch Coordination uplink RBs available
Coordination option of the for LTE decreases,
CaMgtCfg.CellC which reduces the
aAlgoSwitch proportion of UEs for
parameter which LTE Spectrum
Coordination takes
effect.
UL Multi- UlMultiClusterS Scheduling The number of

Cluster witch option of uplink RBs available
the for LTE decreases,
CellAlgoSwitch. which reduces the
UlSchExtSwitch benefit provided by
parameter UL Multi-Cluster.
Uplink None Scheduling The number of

frequency uplink RBs available
selective for LTE decreases,
scheduling which reduces the
benefit provided by
uplink frequency
selective scheduling.
Uplink short- CellUlschAlgo.In Scheduling The number of

interval SPS tvlOfUlSpsWith uplink RBs available
Skipping for LTE decreases,
which reduces the
benefit provided by
uplink short-interval
SPS to UEs.

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation)
SRS SRSCfg.SrsCfgIn Physical Channel As LTE must share

d Resource SRS resources with
Management NR, the LTE cell
triggers the
expansion of the
cell-specific SRS
subframes in
advance, which
prolongs the SRS
period of LTE UEs.
Uplink semi- SpsSchSwitch VoLTE The number of

persistent option of the uplink RBs available
scheduling CellAlgoSwitch. for LTE decreases,
UlSchSwitch which reduces the
parameter benefit provided by
uplink semi-
persistent
scheduling.
Downlink SpsSchSwitch VoLTE The number of

semi- option of the downlink RBs
persistent CellAlgoSwitch. available for LTE
scheduling DlSchSwitch decreases, which
parameter reduces the benefit
provided by
downlink semi-
persistent
scheduling.
TTI Bundling TtiBundlingSwit VoLTE The number of

ch option of the uplink RBs available
CellAlgoSwitch. for LTE decreases.
UlSchSwitch Consequently, the
parameter maximum number of
UEs that can enter
the TTI bundling
state decreases.
Uplink MU- UlVmimoSwitch MIMO The number of

MIMO option of the uplink RBs available
CellAlgoSwitch. for LTE decreases,
UlSchSwitch which increases the
parameter pairing success rate
of uplink MU-MIMO.
Consequently, the
BLER increases.

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation)
Downlink EmimoMuMimo eMIMO (FDD) The number of

MU-MIMO Switch and downlink RBs
4TxTM9MuMim available for LTE
oSwitch options decreases, which
of the increases the pairing
CellAlgoSwitch. success rate of
EmimoSwitch downlink MU-MIMO.
parameter Consequently, the
BLER increases.
UL CoMP CellAlgoSwitch. UL CoMP LTE UEs perform

UplinkCompSwi measurement based
tch on the full
bandwidth. The LTE
CRS transmission
avoids the NR SSB,
leading to inaccurate
LTE RSRP
measurement
results.
Consequently, the
number of CEUs in
the LTE cell
decreases, that is,
the number of UEs
for which UL CoMP
takes effect
decreases.
DRX CellDrxPara.Drx DRX and The number of RBs

AlgSwitch Signaling Control available for LTE
a decrease in the
average number of
number of UEs that
enter DRX mode, as
well as the
frequency of UEs
DRX mode increase.

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation)
Dynamic CellAlgoSwitch. DRX and The number of RBs

DRX DynDrxSwitch Signaling Control available for LTE
a decrease in the
average number of
number of UEs that
enter DRX mode, as
well as the
frequency of UEs
DRX mode increase.
Intra-RAT CellAlgoSwitch. Intra-RAT If the PRB usage of

mobility load MlbAlgoSwitch Mobility Load LTE changes or the
balancing Balancing number of RBs
available for LTE
changes, the intra-
RAT MLB policy
changes.
LCS ENodeBAlgoSwi LCS The PRS required for

tch.LcsSwitch positioning causes
interference to NR,
increasing the BER
on the NR side. As a
result, the
performance of NR
cells deteriorates.
Therefore,
positioning and
Hybrid DSS Based on
Asymmetric
Bandwidth should
not be enabled at
the same time.

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation)
High speed Cell.HighSpeedF High Speed Downlink AFC of

mobility lag Mobility high speed mobility
requires the SFN
function to achieve
its optimal benefits.
However, Hybrid DSS
Based on
Asymmetric
Bandwidth cannot
be enabled together
with the SFN
function. Therefore,
when high speed
mobility is enabled
together with Hybrid
DSS Based on
Asymmetric
Bandwidth, the
benefit produced by
downlink AFC
decreases.
Ultra high Cell.HighSpeedF High Speed Downlink AFC of

speed lag Mobility ultra high speed
mobility mobility requires the
SFN function to
achieve its optimal
benefits. However,
Hybrid DSS Based on
Asymmetric
Bandwidth cannot
be enabled together
with the SFN
function. Therefore,
when ultra high
speed mobility is
enabled together
with Hybrid DSS
Based on
Asymmetric
Bandwidth, the
benefit produced by
downlink AFC
decreases.

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation)
Dynamic CellAlgoSwitch. Energy Dynamic voltage

voltage DynAdjVoltSwit Conservation adjustment does not
adjustment ch and Emission take effect when
Reduction enabled together
with Hybrid DSS
Based on
Asymmetric
Bandwidth, as its
triggering conditions
cannot be met.
DL CoMP Tm9JtSwitch DL CoMP (FDD) DL CoMP with TM9

with TM9 option of the does not take effect
CellAlgoSwitch. when it is used
DlCompSwitch together with Hybrid
parameter DSS Based on
Asymmetric
Bandwidth, as its
triggering conditions
cannot be met.
eNodeB- CellAlgoSwitch.I ICIC A decrease in the

based nterfRandSwitc number of RBs
interference h available for LTE
randomizatio reduces the benefits
n provided by eNodeB-
based interference
randomization.
Uplink CellUlschAlgo.U ICIC A decrease in the

interference lRbAllocationStr number of RBs
randomizatio ategy set to available for LTE
n FS_INRANDOM_ reduces the benefits
ADAPTIVE provided by uplink
interference
randomization.

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation)
RAN sharing EnodeBSharing RAN Sharing When RAN sharing

with Mode.EnodeBSh with common carrier
common aringMode set is enabled together
carrier to with Hybrid DSS
SHARED_FREQ Based on
or Asymmetric
HYBRID_SHARE Bandwidth, the
D number of available
RBs for an LTE
operator is
(Total number of
shared with NR) x
RB allocation
proportion
configured for the
operator.
Flexible TM4 FLEX_TM4_MU_ Low-Band A decrease in the

MU-MIMO MIMO_SW Booster number of downlink
option of the RBs available for LTE
CellMimoParaCf will increase the
g.MimoSwitch pairing success rate
parameter of downlink MU-
MIMO but also
increase the BLER.

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation)
LTE guard Prb.DeployMod NB-IoT Basics ● For 3900 and

band e (FDD) 5900 series base
deployment stations, when
Hybrid DSS Based
on Asymmetric
Bandwidth is used
together with NB-
IoT deployed in
LTE guard band
mode, uplink and
downlink RBs are
reserved for NB-
IoT to reduce the
interference
between NB-IoT
and NR. For
details, see 4.1.3
Application
Scenarios of
Simultaneous
Use of Hybrid
DSS Based on
Asymmetric
Bandwidth and
Other Functions.
The RB
reservation
decreases the
spectrum
resources
available for the
NR cell, reducing
the NR cell
throughput.
● For DBS3900
LampSite and
DBS5900
LampSite, Hybrid
DSS Based on
Asymmetric
Bandwidth cannot
be used together
with NB-IoT
deployed in LTE
guard band
mode.

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation)
Uplink UlInterfSuppres None A decrease in the

single-side sCfg.UlSingleSid number of RBs
in-band eIntrfImpMitSw available for LTE
interference reduces the benefits
impact provided by uplink
mitigation single-side in-band
interference impact
mitigation.
Inter-carrier INTER_CARRIER Massive MIMO When Hybrid DSS

power _PWR_SHR_SWI (FDD) Based on
sharing TCH option of Asymmetric
the Bandwidth is
SectorSplitGrou enabled, the power
p.IntelligentBea that can be shared
mSchSwitch between carriers
parameter decreases.
Sharing CellDynPowerS sharing capability of
haring.Dynamic LTE spectrum
PowerSharingS sharing cells is lower
witch parameter than that of
common cells. As a
result, the power
sharing benefits
decrease.
● Function impacts on the NR side

Name RAN Feature
Documentation
)
Downlink None Power Control After Hybrid DSS

power Based on
control Asymmetric
Bandwidth is
enabled, the
downlink power
cannot be increased.

(2021-12-30)
SingleRAN

Name RAN Feature
Documentation
)
RAN sharing SHARED_FREQ Multi-Operator When RAN sharing

with option of the Sharing with common carrier
common gNBSharingMod is enabled together
carrier e.gNBMultiOpS with Hybrid DSS
haringMode Based on
parameter Asymmetric
Bandwidth, the
number of available
RBs for an NR
operator is
(Total number of
shared with LTE) x
RB allocation
proportion
configured for the
operator.
Uplink RB UL_RB_RSV_SW VoNR Uplink RB

reservation option of the reservation should
NRCellAlgoSwit not be enabled
ch.VonrSwitch together with Hybrid
parameter DSS Based on
Asymmetric
Bandwidth. This is
because if the
reserved RBs are
configured in the
shared spectrum and
some of the shared
by LTE, interference
is generated on voice
UEs that occupy the
reserved RBs in
neighboring NR cells.

(2021-12-30)
SingleRAN

Name RAN Feature
Documentation
)
NR DU cell RB_DYNAMIC_C Network Slicing When both the NR

resource ONTROL_SW DU cell resource
management option of the management
between NRDUCellAlgoS between network
network witch.NetworkS slices function and
slices liceAlgoSwitch Hybrid DSS Based on
parameter Asymmetric
Bandwidth are
enabled, the number
of RBs available for a
network slice group
is calculated using
the following
formula: Number of
RBs available for a
network slice group
= Available
bandwidth of the NR
cell (not the
bandwidth
configured for the
NR cell) x
Percentage of RBs
configured for the
network slice group.
DC DC_COMPONEN Scheduling After Hybrid DSS

component T_RATEMATCH_ Based on
rate SW option of the Asymmetric
matching NRDUCellPdsch. Bandwidth is
RateMatchSwitc enabled,
h parameter configurations for
DC component rate
matching become
invalid.

(2021-12-30)
SingleRAN

Name RAN Feature
Documentation
)
High-speed NRDUCell.HighS High Speed When High-speed

Railway peedFlag Mobility Railway Superior
Superior Experience and
Experience Hybrid DSS Based on
Asymmetric
Bandwidth are both
enabled, the high-
speed mobility of
UEs in high-speed
cells adversely
affects the
performance of
Hybrid DSS Based on
Asymmetric
Bandwidth. In
addition, UEs
enabled with Hybrid
DSS Based on
Asymmetric
Bandwidth do not
support two
downlink additional
DMRS positions,
affecting the PDSCH
demodulation
performance of UEs
in high-speed cells.
Therefore, it is
recommended that
these two functions
not be used together.
Unbalanced NRDUCellCover Cell When the function

transmit age.TransmitPo Management of unbalanced
power werOffsetChn0, transmit power
configuration NRDUCellCover configurations
s between age.TransmitPo between channels is
channels werOffsetChn1, used together with
NRDUCellCover Hybrid DSS Based on
age.TransmitPo Asymmetric
werOffsetChn2, Bandwidth, and the
or spectrum power
NRDUCellCover sharing mode is
age.TransmitPo used, the number of
werOffsetChn3 downlink available
set to a non-zero RBs in the NR cell
value decreases.

(2021-12-30)
SingleRAN

Name RAN Feature
Documentation
)
Compact NRDUCell.Custo Scalable After Hybrid DSS

bandwidth mizedBwConfigI Bandwidth Based on
nd set to Asymmetric
CONFIG Bandwidth is
enabled, compact
bandwidth supports
only the following
bandwidths:
● 14.8 MHz
● 19.6 MHz
● 19.8 MHz
This impact
relationship exists
only when 3900 or
5900 series base
stations are used.

(2021-12-30)
SingleRAN

Name RAN Feature
Documentation
)
Super uplink FLEX_SUPER_UP Super Uplink When Hybrid DSS

with SUL and LINK_SW option Based on
NR FDD co- of the Asymmetric
deployment NRDUCellAlgoS Bandwidth is
witch.SuperUpli enabled together
nkSwitch with super uplink
parameter with SUL and NR
FDD co-deployment,
the amount of uplink
spectrum resources
that can be allocated
to implement super
uplink decreases if
the LTE FDD or NR
traffic volume
increases. As a result,
the uplink
throughput of the
SUL carrier
decreases.
Super uplink with
SUL and NR FDD co-
deployment cannot
take effect in an LTE
cell when Hybrid
DSS Based on
Asymmetric
Bandwidth is
enabled together
with uplink semi-
persistent scheduling
or compact
bandwidth. This is
because these
functions periodically
or continuously
occupy spectrum
resources.
NR inter- NR_DYN_POWE NR Inter-Carrier When Hybrid DSS

carrier R_SHARING_SW Dynamic Power Based on
dynamic option of the Sharing Asymmetric
power NRDUCellAlgoS Bandwidth is
sharing witch.DynPower enabled, the power
SharingSwitch that can be shared
parameter between NR carriers
decreases.

(2021-12-30)
SingleRAN

Name RAN Feature
Documentation
)
Sharing NRDUCellAlgoS sharing capability of
witch.DynPower NR spectrum sharing
SharingSwitch cells is lower than
parameter that of common
cells. As a result, the
power sharing
benefits decrease.
4.3 Requirements
4.3.1 Licenses
This function requires both feature and capacity licenses. Table 4-15 and Table
4-16 list the required feature and capacity licenses.
Table 4-15 Feature licenses

LTE MRFD-1 LTE FDD and LT1S0L LTE FDD and eNodeB per
FDD 60222 NR Flash FNSS00 NR Flash Cell
Dynamic Dynamic
Spectrum Spectrum
Sharing (LTE Sharing(LTE
FDD) FDD)
NR MRFD-1 LTE FDD and NR0S0 LTE FDD and gNodeB per
60262 NR Flash 0FNSS0 NR Flash Cell
Dynamic 0 Dynamic
Spectrum Spectrum
Sharing (NR) Sharing (NR)
LTE MRFD-1 Hybrid DSS LT1SH Hybrid DSS eNodeB per

FDD 71221 Based on DSSBO Based on Cell
Asymmetric AB Asymmetric
Bandwidth(LTE Bandwidth
FDD) (LTE FDD)

(2021-12-30)
SingleRAN

NR MRFD-1 Hybrid DSS NR0S0 Hybrid DSS gNodeB per

71261 Based on HDBAB Based on Cell
Asymmetric 00 Asymmetric
Bandwidth(NR Bandwidth
) (NR)
Table 4-16 Capacity licenses

Unit
LTE FDD LT1SRFSPCS0 RF Spectrum Sharing eNodeB per Band

0 License(FDD) per RU
LTE FDD LT1S5000RFSS Spectrum Sharing License eNodeB per Band

for 5000 Series RF per RU
Module(FDD)
NR NR0S0RFSSL0 RF Spectrum Sharing gNodeB per Band

0 License (NR) per RU
NR NR0SSSLRFM Spectrum Sharing License gNodeB per Band

00 for 5000 Series RF Module per RU
(NR)
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
capacity 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 on the LTE side

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation
)
Normal CP Cell.UlCyclicPref Extended CP Set this parameter to

ix NORMAL_CP.
PRACH RACHCfg.PrachF Random Access Set this parameter to

frequency reqOffsetStrate Control FULLY_AUTOMATIC.
offset gy
strategy
CSI-RS CellCsiRsParaCf Dedicated This function is

Period g.CsiRsPeriod Carrier for TM9 required only when
the
CellCsiRsParaCfg.Csi
RsSwitch parameter
is set to FIXED_CFG
or ADAPTIVE_CFG.
● If the NR SSB
period (specified
by the NR
parameter
NRDUCell.SsbPer
iod) is greater
than or equal to
MS20(20),
CellCsiRsParaCfg.
CsiRsPeriod must
be set to ms10 or
a larger value.
● If the NR SSB
period is less than
or equal to
MS10(10),
CellCsiRsParaCfg.
CsiRsPeriod must
be set to ms20 or
a larger value.
PHICH PHICHCfg.Phich Physical Channel This function is

resource Resource Resource required only when
Management the cell bandwidth is
10 MHz. When this
function is required,
ONE_SIXTH, HALF,
or ONE.
SRS SRSCfg.SrsCfgIn Physical Channel Set this parameter to

configuration d Resource BOOLEAN_TRUE.
indicator Management

(2021-12-30)
SingleRAN

Name (eRAN Feature
Documentation
)
SRS ACK/ SRSCfg.AnSrsSi Physical Channel Set this parameter to

NACK muTrans Resource BOOLEAN_TRUE.
simultaneous Management
transmission
SRS SRSCfg.SrsSubfr Physical Channel When automatic SRS

subframe ameCfg Resource neighboring cell
configuration Management measurement is
enabled (the
NCellSrsMeasPara.S
rsAutoNCellMeasS-
witch parameter set
to ON), set the
SRSCfg.SrsSubframe
Cfg parameter to
SC2.
When automatic SRS
neighboring cell
measurement is
disabled, set the
SRSCfg.SrsSubframe
Cfg parameter to
SC3, SC7, SC14, or
SC0.
Cell-specific SrsSubframeRec Physical Channel Select this option of

SRS fSwitch option Resource this parameter only
subframe of the Management when the
reconfigurati CellAlgoSwitch. LTE_UE_SRS_NOT_C
on SrsAlgoSwitch ONFIG_SW option of
parameter the
SpectrumCloud.Spe
ctrumCloudEnhSwit
ch parameter is
deselected.
Uplink CellUlschAlgo.A Scheduling Set this parameter to

adaptive daptHarqSwitch ADAPTIVE_HARQ_S
HARQ W_ON or
ADAPTIVE_HARQ_S
W_SEMI_ON.
● Prerequisite functions on the NR side

(2021-12-30)
SingleRAN

Name RAN Feature
Documentation
)
Basic None Scheduling Set the

functions of NRDUCellPdsch.DlD
downlink mrsMaxLength
scheduling parameter to
1SYMBOL.
Search Space NRDUCellPdcch. Channel Set the

Zero SearchSpaceZer Management NRDUCellPdcch.Sea
o rchSpaceZero
parameter to
DEFAULT.
Configurable NRDUCell.SsbTi Channel Set the

time-domain mePos Management NRDUCell.SsbTimeP
position in os parameter to
the single DEFAULT.
SSB beam
case

● Mutually exclusive functions on the LTE side
Function Function Switch Reference (eRAN

Name Feature
Documentation)
SFN Cell Cell.MultiRruCellMode set to SFN SFN

and there is more than one set of
sector equipment, or to
MPRU_AGGREGATION and there is
more than one sector equipment
group
Inter- CellAlgoSwitch.InterFreqDirectHoS High Speed Mobility

frequency witch
directional
handover
Low-speed CellAlgoSwitch.LowSpeedInterFreq High Speed Mobility

UE HoSwitch
outmigration
GSM and LTE GLDynSpectrumShareSwitch GSM and LTE FDD

FDD option of the Dynamic Spectrum
Dynamic CellAlgoSwitch.DynSpectrumShar- Sharing
Spectrum eSwitch parameter
Sharing

(2021-12-30)
SingleRAN

Name Feature
Documentation)
GSM and LTE SpectrumCloud.SpectrumCloudSwi GSM and LTE

Spectrum tch set to Spectrum
Concurrency GL_SPECTRUM_CONCURRENCY Concurrency
Flexible DdCellGroup.DdBandwidth Flexible Bandwidth
Bandwidth based on Overlap
Based on Carriers (FDD)
Overlap
Carriers
GSM and LTE GLZeroBufferZoneSwitch option of GSM and LTE Zero

Zero the Bufferzone
Bufferzone CellAlgoSwitch.DynSpectrumShar-
eSwitch parameter
GSM and LTE AvoidGeranInterfSwitch option of GSM and LTE Buffer
Buffer Zone the Zone Optimization
Optimization CellAlgoSwitch.AvoidInterfSwitch
parameter
UL AvoidUtranInterfSwitch option of UL Refarming Zero

Refarming the Bufferzone
Zero CellAlgoSwitch.AvoidInterfSwitch
Bufferzone parameter
UMTS and UMTS_LTE_ZERO_BUFFER_ZONE_S UMTS and LTE Zero

LTE Zero W option of the Bufferzone
Bufferzone ULZeroBufferZone.ZeroBufZoneSw
itch parameter
UMTS and SpectrumCloud.SpectrumCloudSwi UMTS and LTE
LTE tch set to UL_SPECTRUM_SHARING Spectrum Sharing
Spectrum
Sharing
UMTS and SpectrumCloud.SpectrumCloudSwi UMTS and LTE

LTE tch set to Spectrum Sharing
Spectrum DC_HSDPA_BASED_UL_SPECTRUM_ Based on DC-HSDPA
Sharing SHR
Based on
DC-HSDPA
CDMA and AvoidCDMAInterfSwitch option of CDMA and LTE Zero

LTE Zero the Bufferzone
Bufferzone CellAlgoSwitch.AvoidInterfSwitch
parameter
UL CRA UL_COORD_RES_ALLOC_SWITCH Uplink Coordinated

option of the UlCsAlgoPara.UlCsSw Scheduling
parameter

(2021-12-30)
SingleRAN

Name Feature
Documentation)
UL CPC UL_COORD_PC_SWITCH option of Uplink Coordinated

the UlCsAlgoPara.UlCsSw Scheduling
parameter
Coordinated CellCspcPara.CellCspcSwitch CSPC

Scheduling
based Power
Control
PUSCH FH CellUlschAlgo.UlHoppingType None
LTE flexible CellLteFlexBw.LteFlexBwSwitch None

bandwidth
Adaptive Activated using the ACT AICIC Adaptive ICIC

Inter-Cell command on the eCoordinator
Interference
Coordination
Out of Band OutOfBandRelaySwitch option of Relay

Relay the CellAlgoSwitch.RelaySwitch
parameter
In-band relay InBandRelayDeNbSwitch, Relay

InBandRelayReNbSwitch, and
InBandRelayDistantDeploySw
options of the
parameter
Manual RB CellRbReserve.RbRsvMode set to Scheduling

blocking RB_MASKING or
RB_MASKING_WITH_SRS
eMTC EMTC_SWITCH option of the eMTC

Introduction CellEmtcAlgo.EmtcAlgoSwitch
parameter
Cell radius Cell.CellRadius Extended Cell Range

greater than
100 km
Superior CellAlgoExtSwitch.UlCoverageEnh Superior Uplink

Uplink ancementSw Coverage (FDD)
Coverage
eMBMS CellMBMSCfg.MBMSSwitch eMBMS

Virtual 4T4R Virtual4T4RSwitch option of the Virtual 4T4R (FDD)
CellAlgoSwitch.EmimoSwitch
parameter

(2021-12-30)
SingleRAN

Name Feature
Documentation)
UMTS and UMTS_LTE_DYN_POWER_SHARING UMTS and LTE

LTE Dynamic _SW option of the Dynamic Power
Power CellDynPowerShar- Sharing
Sharing ing.DynamicPowerSharingSwitch
parameter
Dynamic LTE_DYN_POWER_SHARING_SW Dynamic Power

power option of the CellDynPowerShar- Sharing Between LTE
sharing ing.DynamicPowerSharingSwitch Carriers
between LTE parameter
carriers
Extreme LTE_EXTREME_POWER_SHARING_S Dynamic Power

power W option of the Sharing Between LTE
sharing CellDynPowerShar- Carriers
ing.DynamicPowerSharingSwitch
parameter
GSM and LTE CellAlgoSwitch.GLPwrShare GSM and LTE

Dynamic Dynamic Power
Power Sharing
Sharing
Super SuperCombCellSwitch option of Super Combined Cell

Combined the CellAlgoSwitch.SfnAlgoSwitch (FDD)
Cell parameter
RF channel CellRfShutdown.RfShutdownSwitc Energy Conservation

intelligent h and Emission
shutdown Reduction
RF channel RF_CHN_DYN_MUTING_SW option Energy Conservation
dynamic of the CellRfChnDynMut- and Emission
muting ing.RfChnDynMutingAlgoSwitch Reduction
parameter
Dynamic CellAlgoSwitch.EicicSwitch TDM eICIC (FDD)

TDM eICIC
Paging PagingInterfRandSwitch option of ICIC

message the CellAlgoSwitch.DlSchSwitch
interference parameter
randomizatio
n
Short TTI SHORT_TTI_SW option of the Short TTI (FDD)

CellShortTtiAlgo.SttiAlgoSwitch
parameter

(2021-12-30)
SingleRAN

Name Feature
Documentation)
Zero Guard CONTIG_INTRA_BAND_CARR_SW Seamless Intra-Band

Band option of the ContigIntraBand- Carrier Joining (FDD)
Between Carr.ContigIntraBandCarrSw
Contiguous parameter
Intra-Band
Carriers
Uplink CellRbReserve.RbRsvMode set to PTT

PUSCH RB MCPTT_RB_RESERVED
reservation
for MCPTT
voice services
Cell Power PDSCHCfg.EmfPowerLimitSwitch On-Demand TX

Limit set to ON, and Power Allocation
PDSCHCfg.CellPowerLimit set to a Under EME
non-zero value

PIM option of the PimInterfSmartA- Detection and
interference void.PimAlgoSwitch parameter Suppression
avoidance
Beam BEAM_NUM_ADJ_SWITCH option Massive MIMO

number of the (FDD)
adjustment SectorSplitGroup.SectorSplitSwitch
parameter, and the Cell.TxRxMode
parameter set to 32T32R
Downlink SectorSplitGroup.TurboPilotPower- Massive MIMO

turbo pilot Offset set to a non-zero value, and (FDD)
Cell.TxRxMode set to 8T8R or
32T32R
Compact Cell.CustomizedBandWidthCfgInd Compact Bandwidth

bandwidth set to CFG, and Cell.TxRxMode set (FDD)
to 8T8R or 32T32R
PUCCH PucchFlexCfgSwitch option of the Physical Channel

Flexible CellAlgoSwitch.PucchAlgoSwitch Resource
Configuratio parameter Management
na
ePDCCH CellPdcchAlgo.EpdcchAlgoSwitch Physical Channel

Resource
Management
Extended PHICHCfg.PhichDuration Physical Channel
PHICH Resource
Management

(2021-12-30)
SingleRAN

Name Feature
Documentation)
Uplink data NSA_DC_UL_PATH_SELECTION_SW NSA Networking

transmission option of the based on EPC
path NsaDcMgmtConfig.NsaDcAlgoSwit
selectionb ch parameter
LTE in-band CellRbReserve.RbRsvMode set to NB-IoT Basics (FDD)

deployment NB_RESERVED or
NB_DEPLOYMENT
Compact Cell.CustomizedBandWidthCfgInd Compact Bandwidth

bandwidth (FDD)
a: When Hybrid DSS Based on Asymmetric Bandwidth is enabled, the
settings of the CellRbReserve.RbRsvMode, CellRbReserve.RbRsvType,
CellRbReserve.RbRsvStartIndex, and CellRbReserve.RbRsvEndIndex
parameters can be used as an alternative to the flexible PUCCH
configuration function.
b: The mutually exclusive relationship exists only when the
SpectrumCloud.SpectrumCloudEnhSwitch parameter is selected.
● Mutually exclusive functions on the NR side

Name Feature
Documentation)
PUCCH RB PUCCH_RBRES_ADAPTIVE_SWITCH Channel

adaptation option of the Management
NRDUCellPucch.PucchAlgoSwitch
parameter
PDCCH UE_PDCCH_SYM_NUM_ADAPT_SW Channel

symbol option of the Management
number NRDUCellPdcch.PdcchAlgoExtSwit
adaptation ch parameter
R16 Type2 R16_TYPE2_SW option of the None
NRDUCellPdschPre-
code.DlCodebookTypeSwitch
parameter
Spectral- INTER_FREQ_CONNECTED_MLB_S Mobility Load

efficiency- W option of the Balancing
based NRCellAlgoSwitch.MlbAlgoSwitch
connected parameter, and the
mode MLB NRCellMlb.MlbTriggerMode
parameter set to
SPEC_EFF_BASED_USER_NUM

(2021-12-30)
SingleRAN

Name Feature
Documentation)
Intra-base- INTRA_GNB_DL_JT_SW option of CoMP

station DL the
CoMP NRDUCellAlgoSwitch.CompSwitch
parameter
Cell NRDUCell.NrDuCellNetworking- Cell Combination

Combination Mode set to
HYPER_CELL_COMBINE_MODE
Inter-base- INTER_GNB_DL_JT_SW option of None

station the
downlink NRDUCellAlgoSwitch.CompSwitch
joint parameter
transmission
Extended NRDUCell.CellRadius Extended Cell Range

Cell Range
Compact NRDUCell.CustomizedBwConfigInd Scalable Bandwidth

bandwidth set to CONFIG, and
NRDUCellTrp.TxRxMode set to
8T8R or 32T32R

PIM option of the NRDUCellPimIntr- Avoidance
interference fAvd.PimAlgoSwitch parameter
avoidance
Basic None Scheduling

functions of
downlink
schedulinga
Rate- PDCCH_NO_PATTERN_RATE_MATC Scheduling

matching- H_SW option of the
pattern- NRDUCellPdcch.PdcchAlgoSwitch
configuration parameter
-free PDCCH
rate
matchingb
SSB Rate SSB_RATEMATCH_SW option of the Scheduling

Matchingc NRDUCellPdsch.RateMatchSwitch
parameter
DC DC_COMPONENT_RATEMATCH_S Scheduling
Component W option of the
Rate NRDUCellPdsch.RateMatchSwitch
Matchingc parameter

(2021-12-30)
SingleRAN

Name Feature
Documentation)
3D coverage NRDUFddCellTrpBeam.CoverageSc Beam Management

patternd enario
RF channel RF_SHUTDOWN_SW option of the Energy Conservation

intelligent NRDUCellAlgoSwitch.PowerSaving and Emission
shutdown Switch parameter Reduction
Energy FLEX_FREQ_SCH_ENERGY_SAVING_ Energy Conservation
saving based SW option of the and Emission
on flexible NRDUCellAlgoSwitch.PowerSaving Reduction
frequency- Switch parameter
domain
schedulinge
a: Hybrid DSS Based on Asymmetric Bandwidth is mutually exclusive with

the NRDUCellPdsch.DlAdditionalDmrsPos parameter (set to POS2) in the
basic functions of downlink scheduling.
b: This mutually exclusive relationship exists when rate matching is enabled
for all symbols in LTE CRSs (by selecting the
NRDUCellAlgoSwitch.SpectrumCloudEnhSwitch parameter).
c: This mutually exclusive relationship exists when the PDCCH rate
matching UE compatibility rectification function is enabled.
d: If both Hybrid DSS Based on Asymmetric Bandwidth and the SSB rate
matching function (controlled by the SSB_RATEMATCH_SW option of the
NRDUCellPdsch.RateMatchSwitch parameter) are enabled, SSB beams
must use the default coverage scenario. That is, the
NRDUCellTrpBeam.CoverageScenario parameter must be set to DEFAULT.
e: This mutually exclusive relationship exists when the PSD adaptation
function is enabled.
4.3.3 Hardware
Huawei devices (including the eNodeB and gNodeB) must be used on the radio
access network.
Base Station Models

● LTE
3900 and 5900 series base stations. 3900 series base stations must be
● NR
3900 and 5900 series base stations. 3900 series base stations must be

(2021-12-30)
SingleRAN
Boards
● LTE
When the cell TX/RX mode is 2T2R, 2T4R, or 4T4R, only the UBBPd, UBBPe,
and UBBPg support this function. Table 4-17 lists the cell number
specifications of different baseband processing units after this function is
enabled. For main control boards, only the UMPTb, UMPTe, UMPTg, and
UMPTga support this function.
When the cell TX/RX mode is 8T8R, only the UBBPe4, UBBPe6, UBBPe18, and
UBBPg support this function. When HDSS based on Asymmetric Beam is not
enabled, the cell number specifications of the baseband processing units are
the same as those before this function is enabled. When HDSS based on
Asymmetric Beam is enabled, the cell number specifications of different
baseband processing units are listed in Table 4-18. For main control boards,
only the UMPTe, UMPTg, and UMPTga support this function.
● NR
When the cell TX/RX mode is 2T2R, 2T4R, or 4T4R, only the UBBPg2,
UBBPg2a, UBBPg3, and UBBPg3b support this function. The cell number
specifications of these baseband processing units are the same as those
before this function is enabled. For main control boards, only the UMPTe,
UMPTg, and UMPTga support this function.
When the cell TX/RX mode is 8T8R, only the UBBPg supports this function.
The cell number specifications of the baseband processing unit are the same
as those before this function is enabled. For main control boards, only the
UMPTe, UMPTg, and UMPTga support this function.

(2021-12-30)
SingleRAN
HDSS based on Asymmetric Beam disabled)
(Compared with
That Before This
LTE FDD or UBBPd5 Decrease or remain A maximum of three

LMa unchanged cells can be enabled
The cell number with Hybrid DSS
specifications decrease Based on Asymmetric
from six (2T2R) cells Bandwidth.
to three cells, or
remain three (2T4R or
4T4R) cells.
LTE FDD or UBBPd6 Decrease A maximum of three

LM The cell number cells can be enabled
specifications decrease with Hybrid DSS
from six (2T2R, 2T4R, Based on Asymmetric
or 4T4R) cells to three Bandwidth.
cells.

LM Three (2T2R) cells cells can be enabled
with Hybrid DSS
Based on Asymmetric
Bandwidth.

LM Three (2T2R, 2T4R or cells can be enabled
4T4R) cells with Hybrid DSS
Based on Asymmetric
Bandwidth.

LM Six (2T2R) cells, or cells can be enabled
three (2T4R or 4T4R) with Hybrid DSS
cells Based on Asymmetric
Bandwidth, while the
rest are common cells.

(2021-12-30)
SingleRAN

(Compared with
That Before This
LTE FDD or UBBPe4/ Remain unchanged ● A maximum of

LM UBBPe18 ● Six (2T2R, 2T4R or three cells can be
4T4R) cells enabled with
Hybrid DSS Based
● Three (8T8R) cells on Asymmetric
Bandwidth, while
the rest are
common cells.
● A maximum of
three cells can be
enabled with
Hybrid DSS Based
on Asymmetric
Bandwidth.
LTE FDD, LM, UBBPe5 Remain unchanged ● LTE FDD or LM: A

GL, or other ● LTE FDD or LM: maximum of six
working nine (2T2R, 2T4R, cells can be
modes or 4T4R) cells enabled with
involving LTE Hybrid DSS Based
FDD ● Woking mode on Asymmetric
combinations other Bandwidth, while
than LM: six (2T2R, the rest are
2T4R, or 4T4R) common cells.
cells
● Woking mode
combinations other
than LM: A
maximum of three
cells can be
enabled with
Hybrid DSS Based
on Asymmetric
Bandwidth, while
the rest are
common cells.

(2021-12-30)
SingleRAN

(Compared with
That Before This
LTE FDD, LM, UBBPe6 Remain unchanged ● LTE FDD or LM

GL, or other ● LTE FDD or LM (with BBP.SRT set
working (with the BBP.SRT to DEFAULT): A
modes parameter set to maximum of six
involving LTE DEFAULT): cells can be
FDD enabled with
– 12 (2T2R, 2T4R Hybrid DSS Based
or 4T4R) cells on Asymmetric
– Six (8T8R) cells Bandwidth, while
● LM (with BBP.SRT the rest are
set to common cells.
NBIOT_ENHANCE) ● LM (with BBP.SRT
: nine (2T2R, 2T4R, set to
or 4T4R) cells NBIOT_ENHANCE)
● Woking mode : A maximum of six
combinations other cells can be
than LM: nine enabled with
(2T2R, 2T4R, or Hybrid DSS Based
4T4R) cells on Asymmetric
Bandwidth, while
the rest are
common cells.
● Woking mode
combinations other
than LM: A
maximum of three
cells can be
enabled with
Hybrid DSS Based
on Asymmetric
Bandwidth, while
the rest are
common cells.

(2021-12-30)
SingleRAN

(Compared with
That Before This
LTE FDD, LM, UBBPg Decrease or remain ● In the case of the

GL, or other unchanged 2T2R, 2T4R, or
working 4T4R TX/RX mode:
modes The cell number
involving LTE specifications of
FDD this baseband
processing unit are
the same as those
before this function
is enabled.
● In the case of the
8T8R or 32T32R
mode: The cell
number
specifications of
this baseband
processing unit are
only half of those
before this function
is enabled.
a: LM refers to LTE FDD and NB-IoT.
HDSS based on Asymmetric Beam enabled)
Working Baseband Supported LTE Cell Number Specifications
Mode Processing Unit
Model
LTE FDD UBBPe4/UBBPe6/ Three LTE sector split groups are supported,
UBBPe18 with two LTE cells in each group. A maximum
of three LTE sector split groups support this
function.
LTE FDD UBBPg The supported LTE sector split group

specifications are the same as those before
this function is enabled.

units that also support it. Otherwise, cell activation may fail in cases where the

(2021-12-30)
SingleRAN
baseband processing units that support this function are fully occupied, leaving
only those that do not support it.
RF Modules
All 5000 series RF modules that meet the following conditions support this
function:
● The RF module is shared by LTE and NR.
● The following NR bandwidths are supported and can be configured: 15 MHz,
20, MHz, 25 MHz, 30 MHz, and 40 MHz.
● The following frequency bands are supported and can be configured: 700
MHz, 1800 MHz, 2100 MHz, and 2600 MHz.
● The following TX/RX modes are supported and can be configured: 2T2R, 2T4R,
4T4R, 8T8R, and 32T32R.
Of all 8T8R RF modules, only 8T8R RRUs support this function.
When HDSS based on Asymmetric Beam is not enabled, of all 32T32R RF
modules, the AAU5711a (1.8 GHz or 2.6 GHz), AAU5726 (1.8 GHz and 2.1
GHz), AAU5726 (AWS+PCS), and AAU5733 (2.6 GHz) support this function.
When HDSS based on Asymmetric Beam is enabled, only 1800 MHz and 2100
MHz 8T8R RRUs support this function. The AAU5711a, AAU5726, and
AAU5733 support the 15 MHz or 20 MHz NR cell bandwidth.
When the cell TX/RX mode is 32T32R, the 2.2:1 CPRI compression ratio is
required to support the simultaneous use between CPRI compression and the
co-carrier co-CPRI data function. The corresponding RF modules can be
AAU5726 (1.8 GHz and 2.1 GHz), and AAU5726 (AWS+PCS).
NOTICE
When the NR cell bandwidth is 15 MHz or 20 MHz, the requirements on RF

modules described in 3.3.3 Hardware must also be met.
Cells
LTE and NR cells must meet all of the following requirements:
● Supported bandwidth
3900 and 5900 series base stations:
Supported bandwidths are classified into standard bandwidths and non-
standard bandwidths.
– Standard bandwidths: See Table 4-19.
Table 4-19 Standard cell bandwidths to which Hybrid DSS Based on

Asymmetric Bandwidth can be applied
10 MHz 15 MHz

(2021-12-30)
SingleRAN
10 MHz 20 MHz
15 MHz 20 MHz
20 MHz 25 MHz
20 MHz 30 MHz
20 MHz 40 MHz
– Non-standard bandwidths: The NR cell can also work on a non-standard

bandwidth when the compact bandwidth function is enabled. Table 4-20
lists the non-standard bandwidths supported by the NR cell and the
corresponding LTE standard cell bandwidths.
Table 4-20 Non-standard bandwidths to which Hybrid DSS Based on

Asymmetric Bandwidth can be applied
10 MHz 14.8 MHz
15 MHz 19.6 MHz
15 MHz 19.8 MHz
NOTICE
The NR cell can work on a non-standard bandwidth only when the

compact bandwidth function is enabled. When a non-standard bandwidth
is used, in addition to the hardware requirements described in this
section, the hardware requirements of compact bandwidth must also be
met. For details about the hardware requirements of compact bandwidth,
see related descriptions in Scalable Bandwidth of 5G RAN Feature
Documentation.
● TX/RX mode
The TX/RX modes of LTE and NR cells must be the same and must be one of
2T2R, 2T4R, 4T4R, 8T8R, and 32T32R. 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. When the TX/RX mode is
8T8R, the number of CRS ports for LTE cells must be 4. When the TX/RX mode
is 32T32R, the number of CRS ports for LTE cells must be 4.
● LTE and NR cells must have the same operating frequency band, and the
center frequency spacing between the LTE and NR cells must be an integer
multiple of 300 kHz.
● The PSD of the LTE and NR cells must be the same. If the total power of the
LTE and NR cells exceeds the maximum transmit power of the RF module, the

(2021-12-30)
SingleRAN
power of the cells needs to be reduced or the RF module needs to be

replaced.
● LTE and NR cells must be deployed in 1:1 co-coverage mode, and must be
served by the same transmit channels of an RF module.
● When HDSS based on Asymmetric Beam is required, the two LTE cells must
have different PCIs as well as different PCI mod 3 values to preferentially
ensure LTE performance. If NR performance needs to be preferentially
ensured, the two LTE cells must have different PCIs but the same PCI mod 3
value.
4.3.4 Networking
When the LTE and NR co-carrier co-CPRI data function is not enabled (the LTE
parameter LteNrSpctShrCellGrp.LteNrCoCarrCoCpriDataSw is set to OFF):
● If the independent power configuration mode is used, there are no special
networking requirements.
● If the spectrum power sharing mode is used, the
LNR_PWR_WITH_SPCT_OPT_SW option of the
SpectrumCloud.SpectrumCloudEnhSwitch parameter must be selected to
solve the power allocation conflicts caused by inconsistent LTE and NR latency
when each uses their respective optical fibers over the CPRI interface.
When the co-carrier co-CPRI data function is enabled (the LTE parameter
LteNrSpctShrCellGrp.LteNrCoCarrCoCpriDataSw is set to ON), this function only
supports the intra-BBU single-fiber CPRI MUX topology in separate-MPT and co-
MPT LTE/NR scenarios or the intra-board cold backup ring topology in co-MPT
LTE/NR scenarios. These topologies do not pose special requirements on board
installation positions. In intra-BBU single-fiber CPRI MUX topology, LTE and NR
cells can be established on the same or different baseband processing units. The
following example illustrates the networking requirements using LTE and NR cells
established on different baseband processing units. In intra-board cold backup ring
topology, LTE and NR cells must be established on the same baseband processing
unit.
share a BBU, and either the LTE baseband processing unit or the NR baseband
processing unit is connected directly to the RRU through an optical fiber, as
shown in Figure 4-7.

(2021-12-30)
SingleRAN
a BBU, and either the LTE baseband processing unit or the NR baseband
processing unit is connected directly to the RRU through an optical fiber, as
shown in Figure 4-8.

(2021-12-30)
SingleRAN
● Intra-board cold backup ring topology in co-MPT LTE/NR scenarios: In this

topology, LTE and NR share a BBU, and both the LTE and NR baseband
processing units are connected directly to the RRU through an optical fiber to
form a ring topology, as shown in Figure 4-9.

(2021-12-30)
SingleRAN
Figure 4-9 Intra-board cold backup ring topology in co-MPT LTE/NR scenarios
4.3.5 Others
● This function takes effect only when MRFD-171221 Hybrid DSS Based on
Asymmetric Bandwidth(LTE FDD) and MRFD-171261 Hybrid DSS Based on
Asymmetric Bandwidth (NR) are both enabled.
● It is recommended that this function be enabled in all cells in the planned
deployment area to reduce the interference caused by the near-far effect.
● NR FDD networks require time synchronization. This function requires the
coordination between the LTE FDD and NR FDD networks, and therefore LTE
FDD networks also need to meet time synchronization requirements. For
details on how to configure time synchronization, see Synchronization in
eRAN Feature Documentation and Synchronization in 5G RAN Feature
Documentation.
● NR UEs need to support the CRS rate matching function. This function allows
the gNodeB to indicate the RE positions of the LTE CRSs, so that NR UEs can
avoid conflicts with the LTE CRSs. 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 Hybrid DSS Based on Asymmetric Bandwidth. NR UEs that do not
support CRS rate matching can access NR FDD cells enabled with Hybrid DSS
Based on Asymmetric Bandwidth, but the uplink and downlink throughput of
these NR UEs decrease.

(2021-12-30)
SingleRAN
CAUTION
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.

Table 4-21 and Table 4-23 describe the parameters used for function activation.
Table 4-22 and Table 4-24 describes the parameters used for function
optimization. This section does not describe parameters related to cell
establishment.
The configuration of some parameters can result in automatic cell restarts during
function activation and deactivation, and modifying the parameter settings of one
RAT will cause both LTE and NR cells to automatically restart. As such, it is
recommended that you deactivate cells prior to parameter configuration and
reactivate them after parameter configuration is complete. This will prevent the
cells from being repeatedly restarted during parameter configuration.
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-21 LTE parameters used for activation

Spectrum Cloud Switch SpectrumCloud.Spectru Set this parameter to

mCloudSwitch LTE_NR_SPECTRUM_SH
R.
Spectrum Cloud SpectrumCloud.Spectru Select the

Enhancement Switch mCloudEnhSwitch LNR_SPECTRUM_SHR_A
SYM_SW option of this
parameter.

(2021-12-30)
SingleRAN
Spectrum Cloud SpectrumCloud.Spectru Set this parameter based

Enhancement Switch mCloudEnhSwitch on the network plan.
● When SRS resource
allocation to LTE is
not required, select
the
LTE_UE_SRS_NOT_CO
NFIG_SW option of
this parameter.
Otherwise, deselect
this option.
The
LTE_UE_SRS_NOT_CO
NFIG_SW option can
all of the following
conditions are met:
– The
SRSCfg.SrsSubfra
meCfg parameter
is set to SC3.
– The
SrsSubframeRecfS
witch option of
the
CellAlgoSwitch.Sr
sAlgoSwitch
parameter is
deselected.
● When the spectrum
power sharing mode
is used, and the LTE
and NR baseband
processing units need
to be connected to
the RRU through their
respective optical
fiber, select the
LNR_PWR_WITH_SPC
T_OPT_SW option.
When the
independent power
configuration mode is
used, LTE and NR can
use their respective
optical fiber over the
CPRI interface without
the need of selecting
this option.

(2021-12-30)
SingleRAN
● Select the
WBB_MBB_CONTROL
_OPT_SW option of
this parameter when
the simultaneous use
with WBB is required.
LTE and NR Spectrum SpectrumCloud.LteNrSp Set this parameter based

Sharing Cell Group IDa ectrumShrCellGrpId on the network plan.
Spectrum Sharing Mode SpectrumCloud.SpctShr Set this parameter to

Mode LTE_NR_PWR_DYN_SHR
_WITH_SPCT or
LTE_NR_PWR_INDEPEN
DENT based on the
network plan.
When the LTE and NR
co-carrier co-CPRI data
function is enabled (the
LTE parameter
eNrCoCarrCoCpriDa-
taSw is set to ON), this
parameter can only be
set to
LTE_NR_PWR_DYN_SHR
_WITH_SPCT.
LTE and NR Spectrum LteNrSpctShrCellGrp.Lt Set this parameter based

Sharing Cell Group IDa eNrSpectrumShrCellGr- on the network plan. The
pId value of the
pId parameter must be
the same as that of the
LteSpctShrCellGrpId
parameter.

(2021-12-30)
SingleRAN
MBB LTE Pri Res Ratio in LteNrSpctShrCellGrp.Lt Set this parameter based
LTE and NR Spct Shr eNrSpctShrLtePriResRa- on the network plan. The
tio value of this parameter
varies with the spectrum
allocation policy, and the
following lists the
configuration
suggestions for ensuring
network performance
when different spectrum
allocation policies are
adopted:
need to be
preferentially
allocated to LTE, it is
recommended that
range of 51 to 80.
need to be
preferentially
allocated to NR, it is
recommended that
range of 20 to 49.
need to be evenly
allocated to LTE and
NR, you are advised
to set this parameter
to 50.
a value less than 20 or
greater than 80, the
access success rate may
decrease or the service
drop rate may increase
in high load scenarios.

(2021-12-30)
SingleRAN
DL SPS Restrict Ratio SpectrumCloud.DlSpsRe Set this parameter based

strictRatio on the network plan. The
proportion of RBs
allocated for LTE
downlink semi-persistent
scheduling =
(SpectrumCloud.DlSpsR
estrictRatio x
tio/100)%.
LTE and NR Co Carrier LteNrSpctShrCellGrp.Lt Set this parameter based
Co CPRI Data Switch eNrCoCarrCoCpriDa- on the network plan.
taSw This parameter can be
set to ON only when LTE
and NR share the same
CPRI optical fibers, and
the CPRI bandwidth is
insufficient. When the
cell TX/RX mode is
32T32R, this parameter
cannot be set to ON.
Frame Offsetb CellFrameOffset.Frame Set this parameter to a

Offset value confirmed by
Huawei engineers.
FDD Frame Offsetb ENodeBFrameOffset.Fd Set this parameter to a

dFrameOffset value confirmed by
Huawei engineers.

(2021-12-30)
SingleRAN
TA Offset CellFrameOffset.TaOffs This parameter must be

et set to a value consistent
NR side specified by the
NRDUCell.TaOffset
parameter. That is, the
met:
● When the
to 0Ts, the
NRDUCell.TaOffset
parameter must be
set to 0Tc.
● When the
to 400Ts, the
NRDUCell.TaOffset
parameter must be
set to 15600Tc.
● When the
to 624Ts, the
NRDUCell.TaOffset
parameter must be
set to 39936Tc.
a: In the current version, an LTE spectrum sharing cell group can contain only
one LTE cell.
b: If both the CellFrameOffset.FrameOffset and
ENodeBFrameOffset.FddFrameOffset parameters are configured, the frame
offset specified by the CellFrameOffset.FrameOffset parameter takes effect for
the LTE cell.

(2021-12-30)
SingleRAN
Table 4-22 LTE parameters used for optimization

LNR Spectrum Sharing LteNrSpctShrCellGrp.Lt The

Switch eNrSpctShrSwitch LNR_RES_ALLOC_ADAP
T_SW option of this
parameter together with
the
tio parameter
determines the spectrum
resource allocation mode
for LTE and NR cells. For
details, see 4.1.2.1
Flexible Spectrum
Priority Modes.
When the function of
inter-RAT preferential
guarantee for GBR
services is required,
select the
GBR_PRI_ALLOC_SW
option of this parameter.

Switch eNrSpctShrSwitch LTE_CSI_RS_AVOID_POL
ICY_SW option of this
parameter.
The
LTE_CSI_RS_AVOID_POL
ICY_SW option cannot
be selected when the LTE
cell TX/RX mode is 8T8R.

(2021-12-30)
SingleRAN

Switch eNrSpctShrSwitch LTE_NR_SRS_ALLOC_OP
T_SW option of this
parameter when LTE and
NR SRS resource
allocation optimization is
required based on the
network plan.
The preceding option can
the following conditions
are all met:
● The cell TX/RX mode
is not 32T32R.
● The
Cell.HighSpeedFlag
parameter must be
set to LOW_SPEED.
● The
reqSelSchSinrThld
parameter must be
set to 255, and the
reqSelSchSinrThld
parameter must be
set to 255.
● The
NSA_DC_UL_PATH_S
ELECTION_SW option
of the
NsaDcMgmtConfig.N
saDcAlgoSwitch
parameter is
deselected.
● The
LTE_UE_SRS_NOT_CO
NFIG_SW option of
the
SpectrumCloud.Spec
trumCloudEnhSwitch
parameter is
deselected.

(2021-12-30)
SingleRAN
Table 4-23 NR parameters used for activation


Switch pectrumCloudSwitch LTE_NR_FDD_SPCT_SHR
_SW option of this
parameter.

Enhance Switch pectrumCloudEnhS- LTE_NR_FDD_SPCT_SHR
witch _ASYM_SW option of
this parameter.
NR Reserved RB Start gNBDULteNrSpctShrCg. Set this parameter based

Index NrReservedRbStartIn- on the network plan.
dex This parameter must be
set to a value
corresponding to the
frequency-domain
position at either end of
the NR spectrum.
If the
NrUlReservedRbStartIn-
dex parameter is also
configured, the uplink
dedicated spectrum
configuration takes the
value of the
NrUlReservedRbStartIn-
dex parameter, and the
downlink dedicated
spectrum configuration
still takes the value of
the
NrReservedRbStartIn-
dex parameter.

(2021-12-30)
SingleRAN
NR Reserved RB End gNBDULteNrSpctShrCg. Set this parameter based

Index NrReservedRbEndIndex on the network plan.
If the
NrUlReservedRbEndIn-
dex parameter is also
configured, the uplink
dedicated spectrum
configuration takes the
value of the
NrUlReservedRbEndIn-
dex parameter, and the
downlink dedicated
spectrum configuration
still takes the value of
the
NrReservedRbEndIndex
parameter.
NR Uplink Reserved RB gNBDULteNrSpctShrCg. Set this parameter based

Start Index NrUlReservedRbStar- on the network plan.
tIndex This parameter must be
set to a value
corresponding to the
frequency-domain
position at either end of
the NR spectrum.
NR Uplink Reserved RB gNBDULteNrSpctShrCg. Set this parameter based

End Index NrUlReservedRbEndIn- on the network plan.
dex
NR Spectrum Sharing NRDUCellSpctCloud.Nr Set this parameter based
Cell Group IDa SpctShrCellGrpId on the network plan.
NR Spectrum Sharing gNBDULteNrSpctShrCg. Set this parameter based

Cell Group IDa NrSpctShrCellGrpId on the network plan.
LTE Spectrum Sharing gNBDULteNrSpctShrCg. Set this parameter based

Cell Group IDa LteSpctShrCellGrpId on the network plan. The
value of the
LteSpctShrCellGrpId
parameter must be the
same as that of the
pId parameter.

(2021-12-30)
SingleRAN
SSB Frequency Position NRDUCell.SsbDescMeth It is recommended that

Describe Method od this parameter be set to
SSB_DESC_TYPE_NARFC
N in NSA networking. In
SA networking, set this
parameter to
SSB_DESC_TYPE_GSCN.
SSB Frequency Position NRDUCell.SsbFreqPos Set this parameter to a

value confirmed by
Huawei engineers.
SSB Period NRDUCell.SsbPeriod Set this parameter based

on the network plan.
SIB1 Period NRDUCell.Sib1Period Set this parameter to

MS40(40).

details about the
configuration
the "PUCCH Channel
Channel Management.
parameter meaning.
configuration
the "PUCCH Channel
Channel Management.

(2021-12-30)
SingleRAN
Format3 CSI-dedicated NRDUCellPucch.CsiDedi Set this parameter based

RB Number catedRbNum on the network plan. For
details about the
configuration
the "PUCCH Channel
Channel Management.
parameter meaning.
configuration
the "PUCCH Channel
Channel Management.
Format4 CSI-dedicated NRDUCellPucch.Format Set this parameter based
RB Number 4CsiDedicatedRbNum on the network plan. For
details about the
configuration
the "PUCCH Channel
Channel Management.

(2021-12-30)
SingleRAN
PDCCH Algorithm NRDUCellPdcch.PdcchA Set this parameter based

Extension Switch lgoExtSwitch on the network plan. If
the UE-specific PDCCH
can span over the entire
NR bandwidth, select the
UE_PDCCH_FULL_BAND
WIDTH_CFG_SW option.
If the UE-specific PDCCH
spans over the dedicated
NR bandwidth, deselect
the
UE_PDCCH_FULL_BAND
WIDTH_CFG_SW option.
It is recommended that
this option be
deselected, which is the
default value.

(2021-12-30)
SingleRAN
Spectrum Sharing Start NRDUCellPdcch.SpctShr When the

Symbol StartSymbol UE_PDCCH_FULL_BAND
WIDTH_CFG_SW option
of the
NRDUCellPdcch.PdcchAl
goExtSwitch parameter
is selected, the
configuration
suggestions are as
follows:
● When one or two LTE
CRS ports are
configured and NR
traffic volume
requirements are
greater than LTE
traffic volume
parameter to SYM1;
when NR traffic
volume requirements
are lower than LTE
traffic volume
parameter to SYM2.
Otherwise, the
proportion of CCE
allocation failures
increases in cells with
large traffic volume
requirements,
affecting the average
uplink and downlink
UE throughput.
● When four LTE CRS
ports are configured,
SYM2.
When the
UE_PDCCH_FULL_BAND
WIDTH_CFG_SW option
of the
is deselected, the
configuration
suggestions are as
follows:

(2021-12-30)
SingleRAN
Set this parameter to

SYM0.
Occupied Symbol NRDUCellPdcch.Occupi Set this parameter to

Number edSymbolNum 2SYM or 3SYM when the
is set to SYM0 or SYM1,
and to 1SYM when the
is set to SYM2.
It is recommended that
the
NRDUCellPdcch.Occupi
edSymbolNum
parameter be set to
2SYM to ensure
sufficient resources for
proper service operation
when the following
conditions are met: The
NR cell bandwidth is 25
MHz or 30 MHz, the
UE_PDCCH_FULL_BAND
WIDTH_CFG_SW option
of the NR parameter
goExtSwitch is
deselected, and the
NRDUCellCoreset.Com
monCtrlResStartSymbol
parameter is set to an
invalid value. There are
no special requirements
in other NR cell
bandwidth scenarios.
Common Control NRDUCellCoreset.Com If the NR common

Resource Start Symbol monCtrlResStartSymbol PDCCH and UE-specific
PDCCH are transmitted
on the same symbols, set
this parameter to an
invalid value. If the NR
common PDCCH and UE-
specific PDCCH are
transmitted on different
symbols, it is
recommended that this
parameter be set to
SYM0.

(2021-12-30)
SingleRAN
Common Control NRDUCellCoreset.Com It is recommended that

Resource RB Number monCtrlResRbNum the
NRDUCellCoreset.Com
monCtrlResRbNum
parameter be set to
RB24(24 RBs x 2
Symbols) to ensure
sufficient resources for
services when the
following conditions are
met: The NR cell
bandwidth is 25 MHz or
30 MHz, the
UE_PDCCH_FULL_BAND
WIDTH_CFG_SW option
of the
is deselected, and the
NRDUCellCoreset.Com
monCtrlResStartSymbol
parameter is set to
SYM0. In other scenarios,
there is no special
requirement.
Frame Offsetb gNodeBParam.FrameOf Set this parameter to a

fset value confirmed by
Huawei engineers.
Frame Offsetb gNBFreqBandConfig.Fra Set this parameter to a

meOffset value confirmed by
Huawei engineers.

(2021-12-30)
SingleRAN
TA Offset NRDUCell.TaOffset This parameter must be

set to a value consistent
LTE side specified by the
CellFrameOffset.TaOffs
et parameter. That is, the
met:
● When the
to 0Ts, the
NRDUCell.TaOffset
parameter must be
set to 0Tc.
● When the
to 400Ts, the
NRDUCell.TaOffset
parameter must be
set to 15600Tc.
● When the
to 624Ts, the
NRDUCell.TaOffset
parameter must be
set to 39936Tc.
RB Reserve Modec NRDUCellRbReserve.Rb Set this parameter to

RsvMode NB_GB_RB_RESERVED.
RB Reserve Typec NRDUCellRbReserve.Rb Set this parameter to

RsvType UPLINK_MODE or
DOWNLINK_MODE to
reserve uplink and
downlink RBs,
respectively.

(2021-12-30)
SingleRAN
RB Reserve Start Indexc NRDUCellRbReserve.Rb Set this parameter to a

RsvStartIndex value confirmed by
recommended
configuration is
described in 4.1.3
Hybrid DSS Based on
Asymmetric Bandwidth
and Other Functions.
RB Reserve End Indexc NRDUCellRbReserve.Rb Set this parameter to a

RsvEndIndex value confirmed by
recommended
configuration is
described in 4.1.3
Hybrid DSS Based on
Asymmetric Bandwidth
and Other Functions.
Spectrum Cloudification NRDUCellAlgoSwitch.S Set this parameter based

Enhance Switch pectrumCloudEnhS- on the network plan.
witch When HDSS based on
Asymmetric Beam is
enabled, select the
LTE_CRS_RATEMATCH_
ALL_SYM_SW option if
LTE performance needs
to be preferentially
ensured, and deselect
this option if NR
performance needs to be
preferentially ensured.
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 NR cell.
c: These four parameters need to be configured when Hybrid DSS Based on
Asymmetric Bandwidth is used together with NB-IoT deployed in LTE guard
band mode.

(2021-12-30)
SingleRAN
Table 4-24 NR parameters used for optimization

Rate Match Switch NRDUCellPdsch.RateMa Select the

tchSwitch PDCCH_RATEMATCH_S
W and
SSB_RATEMATCH_SW
options of this parameter
plan. These two options
can be individually or
both selected.
If the
PDCCH_RATEMATCH_S
W option of this
parameter is selected,
the
PDCCH_RATEMATCH_C
OMPATIBLE_SW option
of the NR parameter
NRDUCellPdsch.RateMa
tchSwitch can be
selected to solve the
compatibility issues of
some UEs.
Downlink Additional NRDUCellPdsch.DlAddit Set this parameter to

DMRS Position ionalDmrsPos POS1 in mobility
scenarios, and to
NOT_CONFIG in fixed-
point scenarios.
FDD LNR Spectrum gNBDULteNrSpctShrCg. Select the

Sharing Switch FddLteNrSpctShrSwitch LTE_CSI_RS_AVOID_SW
and
LTE_CRS_PORT_1_RM_S
W options of this
network plan. These two
options can be
individually or both
selected.
When the TX/RX mode
of the NR cell is 8T8R,
the
LTE_CSI_RS_AVOID_SW
option cannot be
selected.

(2021-12-30)
SingleRAN

Enhance Switch pectrumCloudEnhS- LTE_SS_PBCH_RM_OPT_
witch SW option of this
network plan.

Enhance Switch pectrumCloudEnhS- LTE_CRS_RATEMATCH_
witch ALL_SYM_SW or
LTE_CRS_RM_ALL_SYM_
4PORT_SW option of
this parameter based on
the network plan to
reduce the interference
of neighboring LTE cells
on the NR spectrum
sharing cell. The former
is selected when the LTE
spectrum sharing cell
and other neighboring
LTE cells are configured
with the same number
of CRS ports, and the
latter is selected when
the LTE spectrum sharing
cell and other
neighboring LTE cells are
configured with different
number of CRS ports.

Enhance Switch pectrumCloudEnhS- PWR_SPCT_DENSITY_A
witch DAPT_SW option of this
network plan.

Before using MML commands, refer to 4.2.2 Impacts and 4.3.2 Software and
complete the parameter configurations for related functions based on the impact,
dependency, and mutually exclusive relationships between the functions, as well
as the actual network scenario.
This function must be activated or deactivated on both the LTE and NR sides.
When HDSS based on Asymmetric Beam is required, parameters need to be
configured for both LTE cells on the LTE side.

(2021-12-30)
SingleRAN

Disabled)
//Binding the cell that requires this function to a baseband processing unit supporting this function
//(Optional when the cell TX/RX mode is 32T32R) Setting the percentage of spectrum resources to be
LTE CSI-RS by NR)
//Turning on the switch controlling Hybrid DSS Based on Asymmetric Bandwidth, adding the LTE cell to an
LTE spectrum sharing cell group, setting the spectrum sharing mode (assuming that SRS resources need to
be configured for LTE UEs), turning on the switch controlling power allocation optimization in spectrum
SpectrumCloudEnhSwitch=LNR_SPECTRUM_SHR_ASYM_SW-1&LNR_PWR_WITH_SPCT_OPT_SW-1,
LteNrSpectrumShrCellGrpId=0, SpctShrMode=LTE_NR_PWR_DYN_SHR_WITH_SPCT, DlSpsRestrictRatio=30;
TaOffset=0Ts;

LTE CSI-RS by NR)
FddLteNrSpctShrSwitch=LTE_CSI_RS_AVOID_SW-0;
//Adding an NR cell to the NR spectrum sharing cell group
MOD NRDUCELLPDCCH: NrDuCellId=0, PdcchAlgoExtSwitch=UE_PDCCH_FULL_BANDWIDTH_CFG_SW-0,
SpctShrStartSymbol=SYM0, OccupiedSymbolNum=2SYM;
//Turning on the switch controlling Hybrid DSS Based on Asymmetric Bandwidth
MOD NRDUCELLALGOSWITCH: NrDuCellId=0, SpectrumCloudSwitch=LTE_NR_FDD_SPCT_SHR_SW-1,
SpectrumCloudEnhSwitch=LTE_NR_FDD_SPCT_SHR_ASYM_SW-1;
//Configuring the NR dedicated spectrum (using a 30 MHz NR cell as an example)
MOD GNBDULTENRSPCTSHRCG: NrSpctShrCellGrpId=0, LteSpctShrCellGrpId=0, NrReservedRbStartIndex=0,
NrReservedRbEndIndex=51, NrUlReservedRbStartIndex=0, NrUlReservedRbEndIndex=52;
//Configuring the number of RBs for common control resources
MOD NRDUCELLCORESET: NrDuCellId=0, CommonCtrlResStartSymbol=SYM0, CommonCtrlResRbNum=RB24;
SsbFreqPos=426860;

(2021-12-30)
SingleRAN
//(Optional, required when Hybrid DSS Based on Asymmetric Bandwidth is used together with NB-IoT

Enabled)
//Deactivating the cells
//Binding the cells that require this function to a baseband processing unit supporting this function
//(Optional, set based on the network plan) Setting the percentage of spectrum resources to be
preferentially allocated to LTE MBB services, and turning off the LTE and NR co-carrier co-CPRI data switch
LteNrCoCarrCoCpriDataSw=OFF;
//Turning on the switch controlling Hybrid DSS Based on Asymmetric Bandwidth, adding the LTE cells to an
LTE spectrum sharing cell group, setting the spectrum sharing mode (assuming that SRS resources need to
be configured for LTE UEs), turning on the switch controlling power allocation optimization in spectrum
TaOffset=0Ts;
TaOffset=0Ts;

//Adding an NR cell to the NR spectrum sharing cell group
MOD NRDUCELLPDCCH: NrDuCellId=0, PdcchAlgoExtSwitch=UE_PDCCH_FULL_BANDWIDTH_CFG_SW-0,
SpctShrStartSymbol=SYM0, OccupiedSymbolNum=2SYM;
//Turning on the switch controlling Hybrid DSS Based on Asymmetric Bandwidth

(2021-12-30)
SingleRAN
//Configuring the NR dedicated spectrum range

MOD GNBDULTENRSPCTSHRCG: NrSpctShrCellGrpId=0, LteSpctShrCellGrpId=0, NrReservedRbStartIndex=0,
NrReservedRbEndIndex=102, NrUlReservedRbStartIndex=0, NrUlReservedRbEndIndex=103;
//Configuring the number of RBs for common control resources
MOD NRDUCELLCORESET: NrDuCellId=0, CommonCtrlResStartSymbol=SYM0, CommonCtrlResRbNum=RB24;
SsbFreqPos=426860;
//Turning on LTE_CRS_RATEMATCH_ALL_SYM_SW (assuming that LTE performance needs to be
preferentially ensured)

Disabled)
//(Optional, required when NR performs CRS rate matching in the pattern of one LTE CRS port) Adjusting
the PA configuration of the cell
MOD CELLDLPCPDSCHPA: LocalCellId=0, PaPcOff=DB0_P_A;
MOD LTENRSPCTSHRCELLGRP: LteNrSpectrumShrCellGrpId=0, LteNrSpctShrSwitch=
LTE_CSI_RS_AVOID_POLICY_SW-1;
//Turning on the switch controlling inter-RAT preferential guarantee for GBR services
MOD LTENRSPCTSHRCELLGRP: LteNrSpectrumShrCellGrpId=0, LteNrSpctShrSwitch=GBR_PRI_ALLOC_SW-1;
//Turning on the LTE and NR SRS resource allocation optimization switch
LteNrSpctShrSwitch=LTE_NR_SRS_ALLOC_OPT_SW-1;

//Configuring the PDCCH rate matching and PDCCH rate matching UE compatibility rectification functions
RateMatchSwitch=PDCCH_RATEMATCH_SW-1&PDCCH_RATEMATCH_COMPATIBLE_SW-1;
and CRS rate matching in the pattern of one LTE CRS port
FddLteNrSpctShrSwitch=LTE_CRS_PORT_1_RM_SW-1&LTE_CSI_RS_AVOID_SW-1;
//Turning on LTE_CRS_RATEMATCH_ALL_SYM_SW (based on the assumption that the LTE spectrum sharing
cell and other neighboring LTE cells are configured with the same number of CRS ports)

Enabled)
//Turning on the LTE and NR shared spectrum allocation adaptation switch and the switch controlling inter-
RAT preferential guarantee for GBR services
LteNrSpctShrSwitch=LNR_RES_ALLOC_ADAPT_SW-1&GBR_PRI_ALLOC_SW-1;

(2021-12-30)
SingleRAN
//Turning on LTE_CRS_RATEMATCH_ALL_SYM_SW (based on the assumption that the LTE spectrum sharing
cell and other neighboring LTE cells are configured with the same number of CRS ports)

Disabled)
The following provides only deactivation command examples. You can determine
whether to restore the settings of other parameters based on actual network
conditions.
//Turning off the switch controlling Hybrid DSS Based on Asymmetric Bandwidth
MOD SPECTRUMCLOUD: LocalCellId=0, SpectrumCloudSwitch=OFF,
SpectrumCloudEnhSwitch=LNR_SPECTRUM_SHR_ASYM_SW-0;
//Removing the LTE cell from the LTE spectrum sharing cell group


Enabled)
//Removing LTE cells from the LTE spectrum sharing cell group

(2021-12-30)
SingleRAN


For detailed operations, see Feature Configuration Using the MAE-Deployment.

Check whether Hybrid DSS Based on Asymmetric Bandwidth has taken effect
using MML commands or tracing signaling messages.
When HDSS based on Asymmetric Beam is enabled, activation verification needs
to be performed in both LTE cells.
Using MML Commands

Hybrid DSS Based on Asymmetric Bandwidth takes effect when the following
conditions on both the eNodeB and gNodeB sides are met:
eNodeB MML command DSP LTENRSPCTSHRCELLGRP is
DYNAMIC_SHARING.
gNodeB MML command DSP GNBDULTENRSPCTSHRCG is Dynamic
Sharing.
Tracing Signaling Messages
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.
Hybrid DSS Based on Asymmetric Bandwidth takes effect when the following
conditions on both the eNodeB and gNodeB sides are met:
Perform the following steps to start eNodeB message tracing on the MAE-Access:
Management. In the navigation tree of the displayed window, expand LTE >

(2021-12-30)
SingleRAN
----End
Perform the following steps to start gNodeB message tracing on the MAE-Access:
Management. In the navigation tree of the displayed window, expand NR >
----End

function using the counters listed in 4.2 Network Analysis. When HDSS based on
Asymmetric Beam is enabled, network monitoring needs to be performed in both
LTE cells.

(2021-12-30)
SingleRAN
Parameter Description 5 DSS-based Flexible PDSCH Scheduling
5 DSS-based Flexible PDSCH Scheduling
5.1 Principles
In LTE 4T scenarios, LTE CRSs need to occupy symbols 0 and 1, and the NR PDCCH
can only be deployed on symbol 2. The NR PDSCH needs to be scheduled
following the NR PDCCH. After this function is enabled, if the LTE PDCCH does not
occupy symbol 0 or 1, the NR PDSCH can be scheduled starting from symbol 0 or
1 in rate matching mode so that the NR cell can obtain more available spectrum
resources. This function is supported when the NR parameter
NRDUCellDlSchRes.SpctShrPdschStartSymbol is set to SYM0 or SYM1.
5.2.1 Benefits
This function increases the average downlink throughput of the relevant NR cell.
Average downlink throughput of an NR cell = N.ThpVol.DL.Cell/
N.ThpTime.DL.Cell
5.2.2 Impacts
Network Impacts
This function has the following impacts:
● The average uplink and downlink throughput of the LTE cell decrease, so do
the average uplink and downlink throughput of LTE UEs.
– Average uplink cell throughput = Cell Uplink Average Throughput
– Average uplink UE throughput = User Uplink Average Throughput
● The control format indicator (CFI) value on the LTE side changes. Therefore,
the control channel element (CCE) usage, which is calculated using the

(2021-12-30)
SingleRAN
following formula, changes: CCE usage = (L.ChMeas.CCE.CommUsed +

L.ChMeas.CCE.ULUsed + L.ChMeas.CCE.DLUsed)/L.ChMeas.CCE.Avail.
Function Impacts
None
5.3 Requirements
5.3.1 Licenses
The following license is required only when 3900 or 5900 series base stations are
used.
RAT Feature Feature Name Model Description NE Sales

ID Unit
NR FOFD-0 DSS-based NR0S0 DSS-based gNodeB per

51250 Flexible DSSSF0 Flexible Cell
PDSCH 0 PDSCH
Scheduling Scheduling
(NR FDD) (NR FDD)
5.3.2 Software
Function Name Function Switch Reference
LTE FDD and NR LTE_NR_FDD_SPCT_SHR_S LTE FDD and NR Spectrum

Flash Dynamic W option of the Sharing
Spectrum Sharing NRDUCellAlgoSwitch.Spe
ctrumCloudSwitch
parameter
PDCCH rate PDCCH_RATEMATCH_SW Scheduling

matchinga option of the
NRDUCellPdsch.RateMat
chSwitch parameter
a: When the NRDUCellDlSchRes.SpctShrPdschStartSymbol parameter is set to
SYM0, the PDCCH rate matching function is required.

None

(2021-12-30)
SingleRAN
5.3.3 Hardware
Base Station Models
None
Boards
None
RF Modules
None
Cells
None
5.3.4 Others
None

Table 5-1 describes the parameters used for function activation. This section does
not describe parameters related to cell establishment.
Table 5-1 Parameters used for activation

Spectrum Sharing NRDUCellDlSchRes.Spct Set this parameter to

PDSCH Start Symbol ShrPdschStartSymbol SYM0 or SYM1 based on
the network plan when
DSS-based Flexible
PDSCH Scheduling is
required.
SYM0, the
PDCCH_RATEMATCH_S
W option of the
NRDUCellPdsch.RateMa
tchSwitch parameter
must be selected.

(2021-12-30)
SingleRAN

Before using MML commands, refer to 5.2 Network Analysis and 5.3.2 Software
and complete the parameter configurations for related functions based on the
impact, dependency, and mutually exclusive relationships between the functions,
as well as the actual network scenario.
Activation Command Examples

//Enabling DSS-based Flexible PDSCH Scheduling
MOD NRDUCELLDLSCHRES: NrDuCellId=0, SpctShrPdschStartSymbol=SYM1;
Deactivation Command Examples

//Disabling DSS-based Flexible PDSCH Scheduling
MOD NRDUCELLDLSCHRES: NrDuCellId=0, SpctShrPdschStartSymbol=NOT_CONFIG;

For detailed operations, see .

Observe the changes in the average downlink throughput of the NR cell before
and after this function is enabled to determine whether it has taken effect.
Specifically, observe and record the average downlink throughput of the NR cell
before and after enabling this function. The average downlink throughput of an
NR cell is equal to N.ThpVol.DL.Cell/N.ThpTime.DL.Cell. If the average downlink
throughput of the NR cell after this function is enabled is greater than that before
this function is enabled, this function has taken effect.

function using the counters listed in 5.2 Network Analysis.

(2021-12-30)
SingleRAN
Parameter Description 6 Parameters
6 Parameters
The following hyperlinked EXCEL files of parameter documents match the

software version with which this document is released.
● Node Parameter Reference: contains device and transport parameters.
● eNodeBFunction Parameter Reference: contains all parameters related to
radio access functions, including air interface management, access control,
mobility control, and radio resource management.
● eNodeBFunction Used Reserved Parameter List: contains the reserved
parameters that are in use and those that have been disused.
● gNodeBFunction Parameter Reference: contains all parameters related to
radio access functions, including air interface management, access control,
● gNodeBFunction Used Reserved Parameter List: contains the reserved
parameters that are in use and those that have been disused.
NOTE
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.
FAQ 1: How do I find the parameters related to a certain feature from

parameter reference?
Step 1 Open the EXCEL file of parameter reference.
Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID.
Step 3 Click OK. All parameters related to the feature are displayed.
----End
FAQ 2: How do I find the information about a certain reserved parameter

from the used reserved parameter list?
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.

(2021-12-30)
SingleRAN
Parameter Description 6 Parameters
View its information, including the meaning, values, impacts, and product version
in which it is activated for use.
----End

(2021-12-30)
SingleRAN
Parameter Description 7 Counters
7 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,
● gNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
NOTE
You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from

performance counter reference?
Step 1 Open the EXCEL file of performance counter reference.

Step 2 On the Counter Summary(En) sheet, filter the Feature ID column. Click Text
Filters and choose Contains. Enter the feature ID.
Step 3 Click OK. All counters related to the feature are displayed.
----End

(2021-12-30)
SingleRAN
Parameter Description 8 Glossary
8 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

(2021-12-30)
SingleRAN
Parameter Description 9 Reference Documents
9 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
– 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)

(2021-12-30)
SingleRAN
– 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)
– Smart 8T8R (FDD)
– PTT
– On-Demand TX Power Allocation Under EME
– Dedicated Carrier for TM9
– Seamless Intra-Band Carrier Joining (FDD)
– Compact Bandwidth (FDD)
– High Speed Mobility
– CPRI Compression
– pRRU Uplink Interference Suppression
– RAN Sharing
– NSA Networking based on EPC
– Synchronization
– Low-Band Booster
● Feature parameter description documents in 5G RAN Feature Documentation:
– Carrier Aggregation
– Scheduling
– Channel Management
– Mobility Load Balancing
– Energy Conservation and Emission Reduction
– Power Control
– Multi-Operator Sharing
– Beam Management
– VoNR
– Network Slicing
– CoMP
– Cell Combination
– Hyper Cell
– Scalable Bandwidth
– Super Uplink

(2021-12-30)
SingleRAN
– Extended Cell Range

– High Speed Mobility
– CPRI Compression
– NSA Networking based on EPC
– Cell Management
– Synchronization
● Dynamic Power Sharing Between LTE Carriers
● LTE Spectrum Coordination
● GSM and LTE Spectrum Concurrency
● UMTS and LTE Dynamic Power Sharing
● UMTS and LTE Spectrum Sharing
● UMTS and LTE Spectrum Sharing Based on DC-HSDPA

(2021-12-30)

LTE FDD and NR Spectrum Sharing (SRAN18.1 - Draft A)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LTE FDD and NR Spectrum Sharing (SRAN18.1 - Draft A)

Uploaded by

Copyright:

Available Formats

SingleRAN

LTE FDD and NR Spectrum Sharing

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue Draft A Copyright © Huawei Technologies Co., Ltd. i

2 About This Document.............................................................................................................8

3 LTE FDD and NR Flash Dynamic Spectrum Sharing...................................................... 12

Issue Draft A Copyright © Huawei Technologies Co., Ltd. ii

3.4 Operation and Maintenance............................................................................................................................................. 95

4 Hybrid DSS Based on Asymmetric Bandwidth............................................................. 119

5 DSS-based Flexible PDSCH Scheduling.......................................................................... 213

Issue Draft A Copyright © Huawei Technologies Co., Ltd. iii

5.2.1 Benefits............................................................................................................................................................................... 213

Issue Draft A Copyright © Huawei Technologies Co., Ltd. iv

This chapter describes changes not included in the "Parameters", "Counters",

1.1 SRAN18.1 Draft A (2021-12-30)

Added support for configurable TA Added the ● 3900 and 5900

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 1

Change Description Parameter Base Station

Added support for simultaneous use Modified ● 3900 and 5900

Added support for inter-RAT Modified ● 3900 and 5900

Added the required CPRI compression None ● 3900 and 5900

Deleted the impact that pRRU deep None DBS3900

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 2

Change Description Parameter Base Station

Added the impact relationship None ● 3900 and 5900

Removed the mutually exclusive None ● 3900 and 5900

Removed mutually exclusive None ● 3900 and 5900

Added impact relationships between None ● 3900 and 5900

Added impact relationships between None ● 3900 and 5900

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 3

Change Description Parameter Base Station

Removed mutually exclusive None ● 3900 and 5900

Added the mutually exclusive None ● 3900 and 5900

Removed the mutually exclusive None ● 3900 and 5900

Added mutually exclusive relationships None ● 3900 and 5900

Removed the mutually exclusive None 3900 and 5900

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 4

Change Description Parameter Base Station

Added common bandwidth scenarios None ● 3900 and 5900

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 5

Change Description Parameter Base Station

Added support for simultaneous use of None 3900 and 5900

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 6

Change Description Parameter Base Station

Added support for HDSS based on None 3900 and 5900

Simplified parameter configurations Modified ● 3900 and 5900

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 7

2 About This Document

2.1 General Statements

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 8

2.2 Applicable RAT

2.3 Features in This Document

RAT Feature ID Feature Name Chapter/Section

NR FDD MRFD-16026 LTE FDD and NR Flash

LTE FDD MRFD-17122 Hybrid DSS Based on 4 Hybrid DSS Based

NR FDD MRFD-17126 Hybrid DSS Based on

NR FDD FOFD-051250 DSS-based Flexible PDSCH 5 DSS-based Flexible

Issue Draft A Copyright © Huawei Technologies Co., Ltd. 9

Hybrid DSS Based on Supported only in NR 4 Hybrid DSS Based on

DSS-based Flexible Supported only in NR 5 DSS-based Flexible

Table 2-2 Differences between NSA and SA