SFN (eRAN15.1 - Draft B) PDF

eRAN
SFN Feature Parameter Description
Issue Draft B
Date 2019-02-22
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2019. 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: http://www.huawei.com
Email: support@huawei.com
Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. i

eRAN
SFN Feature Parameter Description Contents
Contents
1 Change History.............................................................................................................................. 1
1.1 eRAN15.1 Draft B (2019-02-22)....................................................................................................................................1
1.2 eRAN15.1 Draft A (2019-01-05)................................................................................................................................... 1
2 About This Document.................................................................................................................. 5

2.1 General Statements......................................................................................................................................................... 5
2.2 Applicable RAT.............................................................................................................................................................. 6
2.3 Features in This Document.............................................................................................................................................6
2.4 Differences Between NB-IoT and FDD......................................................................................................................... 8
2.5 Differences Between FDD and TDD..............................................................................................................................9
3 Overview....................................................................................................................................... 12
3.1 Introduction.................................................................................................................................................................. 12
3.2 Application Scenarios...................................................................................................................................................13
4 General Principles....................................................................................................................... 19
4.1 Independent Scheduling and Joint Scheduling............................................................................................................. 19
4.2 UE Scheduling Attribute Decision (FDD)....................................................................................................................20
4.3 UE Scheduling Attribute Decision (TDD)................................................................................................................... 25
4.4 Downlink Joint Transmission....................................................................................................................................... 29
4.5 Uplink Independent Reception (FDD)......................................................................................................................... 29
4.6 Uplink Joint Reception (FDD)..................................................................................................................................... 31
4.7 Uplink Independent Reception (TDD)......................................................................................................................... 32
4.8 Uplink Joint Reception (TDD)..................................................................................................................................... 33
4.9 Coordination Between Adaptive SFN/SDMA and Multiple-Antenna Techniques......................................................34
5 SFN (FDD).....................................................................................................................................36
5.1 Principles...................................................................................................................................................................... 36
5.2 Network Analysis......................................................................................................................................................... 36
5.2.1 Benefits...................................................................................................................................................................... 36
5.2.2 Impacts.......................................................................................................................................................................38
5.3 Requirements................................................................................................................................................................ 46
5.3.1 Licenses..................................................................................................................................................................... 46
5.3.2 Software.....................................................................................................................................................................47
5.3.3 Hardware................................................................................................................................................................... 51
5.3.4 Networking................................................................................................................................................................ 52
Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. ii

eRAN
5.3.5 Others.........................................................................................................................................................................53
5.4 Operation and Maintenance..........................................................................................................................................53
5.4.1 Data Configuration.................................................................................................................................................... 53
5.4.1.1 Data Preparation..................................................................................................................................................... 53
5.4.1.2 Using MML Commands......................................................................................................................................... 60
5.4.1.3 Using the CME....................................................................................................................................................... 65
5.4.2 Activation Verification.............................................................................................................................................. 66
5.4.3 Network Monitoring.................................................................................................................................................. 68
6 SFN (TDD).................................................................................................................................... 70
6.1 Principles...................................................................................................................................................................... 70
6.2.1 Benefits...................................................................................................................................................................... 70
6.2.2 Impacts.......................................................................................................................................................................72
6.3 Requirements................................................................................................................................................................ 77
6.3.1 Licenses..................................................................................................................................................................... 77
6.3.2 Software.....................................................................................................................................................................77
6.3.3 Hardware................................................................................................................................................................... 80
6.3.4 Networking................................................................................................................................................................ 80
6.3.5 Others.........................................................................................................................................................................81
6.4 Operation and Maintenance..........................................................................................................................................81
6.4.1 Data Configuration.................................................................................................................................................... 81
6.4.1.1 Data Preparation..................................................................................................................................................... 81
6.4.1.2 Using MML Commands......................................................................................................................................... 86
6.4.1.3 Using the CME....................................................................................................................................................... 89
6.4.2 Activation Verification.............................................................................................................................................. 89
6.4.3 Network Monitoring.................................................................................................................................................. 90
7 4x4 MIMO in the Overlapping Areas Between the Physical Cells of an SFN Cell........ 93
7.1 Principles...................................................................................................................................................................... 93
7.2.1 Benefits...................................................................................................................................................................... 94
7.2.2 Impacts.......................................................................................................................................................................94
7.3 Requirements................................................................................................................................................................ 98
7.3.1 Licenses..................................................................................................................................................................... 98
7.3.2 Software.....................................................................................................................................................................98
7.3.3 Hardware................................................................................................................................................................... 99
7.3.4 Others.......................................................................................................................................................................100
7.4 Operation and Maintenance........................................................................................................................................100
7.4.1 Data Configuration (FDD).......................................................................................................................................100
7.4.1.1 Data Preparation................................................................................................................................................... 100
7.4.1.2 Using MML Commands....................................................................................................................................... 101
7.4.1.3 Using the CME..................................................................................................................................................... 102
7.4.2 Data Configuration (TDD)...................................................................................................................................... 102
Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. iii

eRAN

7.4.2.3 Using the CME..................................................................................................................................................... 104
7.4.3 Activation Verification............................................................................................................................................ 104
7.4.4 Network Monitoring................................................................................................................................................ 104
8 SFN HetNet Smart Cluster Organization (FDD).................................................................105

8.1 Principles.................................................................................................................................................................... 105
8.2 Network Analysis....................................................................................................................................................... 105
8.2.1 Benefits.................................................................................................................................................................... 105
8.2.2 Impacts.....................................................................................................................................................................105
8.3 Requirements.............................................................................................................................................................. 106
8.3.1 Licenses................................................................................................................................................................... 106
8.3.2 Software...................................................................................................................................................................106
8.3.3 Hardware................................................................................................................................................................. 106
8.3.4 Others.......................................................................................................................................................................106
8.4 Operation and Maintenance........................................................................................................................................107
9 Adaptive SFN/SDMA (FDD)...................................................................................................108

9.1 Principles.................................................................................................................................................................... 108
9.2 Network Analysis....................................................................................................................................................... 109
9.2.1 Benefits.................................................................................................................................................................... 109
9.2.2 Impacts.....................................................................................................................................................................110
9.3 Requirements.............................................................................................................................................................. 113
9.3.1 Licenses................................................................................................................................................................... 114
9.3.2 Software................................................................................................................................................................... 114
9.3.3 Hardware..................................................................................................................................................................115
9.3.4 Others.......................................................................................................................................................................115
9.4 Operation and Maintenance........................................................................................................................................ 115
9.4.1 Data Configuration.................................................................................................................................................. 115
9.4.1.3 Using the CME..................................................................................................................................................... 119
9.4.2 Activation Verification.............................................................................................................................................119
9.4.3 Network Monitoring................................................................................................................................................ 120
10 Adaptive SFN/SDMA (TDD)................................................................................................ 121

10.1 Principles.................................................................................................................................................................. 121
10.2 Network Analysis..................................................................................................................................................... 122
10.2.1 Benefits.................................................................................................................................................................. 122
10.2.2 Impacts...................................................................................................................................................................122
10.3 Requirements............................................................................................................................................................ 125
10.3.1 Licenses................................................................................................................................................................. 125
10.3.2 Software.................................................................................................................................................................126
Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. iv

eRAN
10.3.3 Hardware............................................................................................................................................................... 126

10.3.4 Others.....................................................................................................................................................................126
10.4 Operation and Maintenance......................................................................................................................................126
10.4.1 Data Configuration................................................................................................................................................ 126
10.4.1.1 Data Preparation................................................................................................................................................. 127
10.4.1.2 Using MML Commands..................................................................................................................................... 128
10.4.1.3 Using the CME................................................................................................................................................... 129
10.4.2 Activation Verification.......................................................................................................................................... 129
10.4.3 Network Monitoring.............................................................................................................................................. 129
11 Inter-BBP SFN (FDD)..............................................................................................................130

11.1 Principles.................................................................................................................................................................. 130
11.2.1 Benefits.................................................................................................................................................................. 131
11.2.2 Impacts...................................................................................................................................................................131
11.3 Requirements............................................................................................................................................................ 131
11.3.1 Licenses................................................................................................................................................................. 131
11.3.2 Software................................................................................................................................................................. 131
11.3.3 Hardware................................................................................................................................................................132
11.3.4 Networking............................................................................................................................................................ 132
11.3.5 Others.....................................................................................................................................................................137
11.4 Operation and Maintenance...................................................................................................................................... 137
11.4.1.3 Using the CME................................................................................................................................................... 138
11.4.2 Activation Verification...........................................................................................................................................138
12 Inter-BBP SFN (TDD)............................................................................................................. 139

12.1 Principles.................................................................................................................................................................. 139
12.2.1 Benefits.................................................................................................................................................................. 140
12.2.2 Impacts...................................................................................................................................................................140
12.3 Requirements............................................................................................................................................................ 140
12.3.1 Licenses................................................................................................................................................................. 140
12.3.2 Software.................................................................................................................................................................140
12.3.3 Hardware............................................................................................................................................................... 141
12.3.4 Networking............................................................................................................................................................ 142
12.3.5 Others.....................................................................................................................................................................145
Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. v

eRAN
12.4.1.3 Using the CME................................................................................................................................................... 146

13 Inter-BBP Adaptive SFN/SDMA (FDD)..............................................................................147

13.1 Principles.................................................................................................................................................................. 147
13.2.1 Benefits.................................................................................................................................................................. 147
13.2.2 Impacts...................................................................................................................................................................147
13.3 Requirements............................................................................................................................................................ 147
13.3.1 Licenses................................................................................................................................................................. 147
13.3.2 Software.................................................................................................................................................................148
13.3.3 Hardware............................................................................................................................................................... 148
13.3.4 Others.....................................................................................................................................................................148
13.4.1.3 Using the CME................................................................................................................................................... 148
14 Inter-BBP Adaptive SFN/SDMA (TDD)............................................................................. 150

14.1 Principles.................................................................................................................................................................. 150
14.2.1 Benefits.................................................................................................................................................................. 150
14.2.2 Impacts...................................................................................................................................................................150
14.3 Requirements............................................................................................................................................................ 150
14.3.1 Licenses................................................................................................................................................................. 151
14.3.2 Software.................................................................................................................................................................151
14.3.3 Hardware............................................................................................................................................................... 151
14.3.4 Others.....................................................................................................................................................................151
14.4.1.3 Using the CME................................................................................................................................................... 152
15 Inter-eNodeB SFN Based on eNodeB Coordination (FDD)............................................ 153

15.1 Principles.................................................................................................................................................................. 153
15.2.1 Benefits.................................................................................................................................................................. 155
Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. vi

eRAN
15.2.2 Impacts...................................................................................................................................................................155
15.3 Requirements............................................................................................................................................................ 156
15.3.1 Licenses................................................................................................................................................................. 156
15.3.2 Software.................................................................................................................................................................157
15.3.3 Hardware............................................................................................................................................................... 158
15.3.4 Networking............................................................................................................................................................ 159
15.3.5 Others.....................................................................................................................................................................160
15.4.1.3 Using the CME................................................................................................................................................... 163
16 Inter-eNodeB SFN Based on eNodeB Coordination (TDD)............................................164

16.1 Principles.................................................................................................................................................................. 164
16.2.1 Benefits.................................................................................................................................................................. 166
16.2.2 Impacts...................................................................................................................................................................166
16.3 Requirements............................................................................................................................................................ 166
16.3.1 Licenses................................................................................................................................................................. 167
16.3.2 Software.................................................................................................................................................................167
16.3.3 Hardware............................................................................................................................................................... 167
16.3.4 Networking............................................................................................................................................................ 168
16.3.5 Others.....................................................................................................................................................................170
16.4.1.3 Using the CME................................................................................................................................................... 173
17 Inter-eNodeB Adaptive SFN/SDMA based on eNodeB Coordination (FDD)............ 174

17.1 Principles.................................................................................................................................................................. 174
17.2.1 Benefits.................................................................................................................................................................. 174
17.2.2 Impacts...................................................................................................................................................................174
17.3 Requirements............................................................................................................................................................ 174
17.3.1 Licenses................................................................................................................................................................. 175
17.3.2 Software.................................................................................................................................................................175
17.3.3 Hardware............................................................................................................................................................... 175
17.3.4 Others.....................................................................................................................................................................176
Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. vii

eRAN

17.4.1.3 Using the CME................................................................................................................................................... 176
18 Inter-eNodeB Adaptive SFN/SDMA based on eNodeB Coordination (TDD)............177

18.1 Principles.................................................................................................................................................................. 177
18.2.1 Benefits.................................................................................................................................................................. 177
18.2.2 Impacts...................................................................................................................................................................177
18.3 Requirements............................................................................................................................................................ 177
18.3.1 Licenses................................................................................................................................................................. 178
18.3.2 Software.................................................................................................................................................................178
18.3.3 Hardware............................................................................................................................................................... 178
18.3.4 Others.....................................................................................................................................................................179
18.4.1.3 Using the CME................................................................................................................................................... 179
19 Adaptive SFN/SDMA with TM9/TM10 (Trial) (FDD)..................................................... 180

19.1 Principles.................................................................................................................................................................. 180
19.2.1 Benefits.................................................................................................................................................................. 181
19.2.2 Impacts...................................................................................................................................................................181
19.3 Requirements............................................................................................................................................................ 181
19.3.1 Licenses................................................................................................................................................................. 181
19.3.2 Software.................................................................................................................................................................181
19.3.3 Hardware............................................................................................................................................................... 182
19.3.4 Networking............................................................................................................................................................ 183
19.3.5 Others.....................................................................................................................................................................183
19.4.1.3 Using the CME................................................................................................................................................... 185
Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. viii

eRAN
20 PDCCH DCS in SFN (TDD)..................................................................................................187

20.1 Principles.................................................................................................................................................................. 187
20.2.1 Benefits.................................................................................................................................................................. 189
20.2.2 Impacts...................................................................................................................................................................190
20.3 Requirements............................................................................................................................................................ 190
20.3.1 Licenses................................................................................................................................................................. 190
20.3.2 Software.................................................................................................................................................................190
20.3.3 Hardware............................................................................................................................................................... 190
20.3.4 Others.....................................................................................................................................................................191
20.4.1.3 Using the CME................................................................................................................................................... 192
21 PDCCH SDMA in SFN (TDD)..............................................................................................193

21.1 Principles.................................................................................................................................................................. 193
21.2.1 Benefits.................................................................................................................................................................. 195
21.2.2 Impacts...................................................................................................................................................................195
21.3 Requirements............................................................................................................................................................ 195
21.3.1 Licenses................................................................................................................................................................. 196
21.3.2 Software.................................................................................................................................................................196
21.3.3 Hardware............................................................................................................................................................... 196
21.3.4 Others.....................................................................................................................................................................196
21.4.1.3 Using the CME................................................................................................................................................... 198
22 Inter-RRU CBF in Adaptive SFN/SDMA (TDD)...............................................................199

22.1 Principles.................................................................................................................................................................. 199
22.2.1 Benefits.................................................................................................................................................................. 200
22.2.2 Impacts...................................................................................................................................................................200
22.3 Requirements............................................................................................................................................................ 200
22.3.1 Licenses................................................................................................................................................................. 200
22.3.2 Software.................................................................................................................................................................201
Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. ix

eRAN
22.3.3 Hardware............................................................................................................................................................... 201

22.3.4 Others.....................................................................................................................................................................201
22.4.1.3 Using the CME................................................................................................................................................... 202
23 Parameters................................................................................................................................. 203
24 Counters.................................................................................................................................... 204
25 Glossary..................................................................................................................................... 205
26 Reference Documents............................................................................................................. 206
Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. x

eRAN
SFN Feature 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:
l Technical changes
Changes in functions and their corresponding parameters
l Editorial changes
Improvements or revisions to the documentation
1.1 eRAN15.1 Draft B (2019-02-22)

This issue includes the following changes.
Technical Changes
None
Editorial Changes
For FDD:
l Modified the description of function impacts related to the multi-carrier function for the
SFN function. For details, see 5.2.2 Impacts.
l Changed the maximum number of physical cells supported by the MAC layer. For
details, see 11.3.4 Networking.
For TDD: There is no change.
1.2 eRAN15.1 Draft A (2019-01-05)

This issue introduces the following changes to eRAN13.1 06 (2018-11-12).
Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. 1

eRAN
Technical Changes
Change Description Parameter RAT Base Station
Change Model
Added smart carrier selection None FDD l 3900 and 5900

based on virtual grids and series base
UMTS and LTE Zero stations
Bufferzone to the table of l DBS3900
function impacts for the SFN LampSite and
function. For details, see 5.2.2 DBS5900
Impacts. LampSite
Added smart carrier selection None TDD l 3900 and 5900

based on virtual grids to the series base
table of function impacts for the stations
SFN function. For details, see l DBS3900
6.2.2 Impacts. LampSite and
DBS5900
LampSite
Added the following functions None FDD l 3900 and 5900

to the list of mutually exclusive series base
functions for the SFN function. stations
For details, see 5.3.2 Software. l DBS3900
l Intelligent beam shaping LampSite and
l LTE FDD and NR Uplink DBS5900
Spectrum Sharing LampSite
l WTTx MU-MIMO
Added DL CoMP with TM9 to None FDD l 3900 and 5900

the list of mutually exclusive series base
functions for 4x4 MIMO in the stations
overlapping areas between the l DBS3900
physical cells of an SFN cell. LampSite and
For details, see 7.3.2 Software. DBS5900
LampSite
Added the SFN HetNet smart None FDD l 3900 and 5900
cluster organization function. series base
For details, see 8 SFN HetNet stations
Smart Cluster Organization l DBS3900
(FDD). LampSite and
DBS5900
LampSite

eRAN
Change Description Parameter RAT Base Station

Change Model
Added fast UE scheduling Added the FDD l 3900 and 5900

attribute decision for adaptive AsfnFastAttS series base
SFN and added support for TM9 witch option to stations
in adaptive SFN cells each the l DBS3900
served by a maximum of six CellAlgoSwitc LampSite and
RRUs. For details, see: h.SfnAlgoSwitc DBS5900
l 4.2 UE Scheduling h parameter. LampSite
Attribute Decision (FDD)
l 9 Adaptive SFN/SDMA
(FDD)
l 19 Adaptive SFN/SDMA
with TM9/TM10 (Trial)
(FDD)
Added NPREO constant None FDD l 3900 and 5900

optimization to the table of series base
function impacts for the stations
adaptive SFN/SDMA function. l DBS3900
For details, see 9.2.2 Impacts. LampSite and
DBS5900
LampSite
Added compatibility of None FDD l 3900 and 5900

BBU3910C with the SFN, series base
adaptive SFN/SDMA, and stations
adaptive SFN/SDMA with TM9/ l DBS3900
TM10 functions. For details, LampSite and
see: DBS5900
l 5.3.3 Hardware LampSite
l 9.3.3 Hardware
l 19.3.3 Hardware
Added DL CoMP with TM9 to None FDD 3900 and 5900

functions for the inter-eNodeB stations
SFN based on eNodeB
coordination function. For
details, see 15.3.2 Software.
Added DL CoMP with TM9 to None FDD l 3900 and 5900

functions for the adaptive SFN/ stations
SDMA with TM10 function. For l DBS3900
details, see 19.3.2 Software. LampSite and
DBS5900
LampSite

eRAN
Editorial Changes
Revised descriptions in this document.

eRAN
SFN Feature Parameter Description 2 About This Document
2 About This Document
2.1 General Statements

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

eRAN
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.
Feature Differences Between RATs

The feature difference section only describes differences in switches or principles.
Unless otherwise stated, descriptions in this document apply to all RATs. If a description does
not apply to all RATs, the specific RAT that it does apply to will be stated.
For example, in the statement "TDD cells are compatible with enhanced MU-MIMO", "TDD
cells" indicates that this function cannot be used in non-TDD cells.
2.2 Applicable RAT

This document applies to FDD/NB-IoT/TDD.
2.3 Features in This Document

This document describes the following FDD features.
Feature ID Feature Name Section
LOFD-003029 SFN 5 SFN (FDD)
7 4x4 MIMO in the

Overlapping Areas
Between the Physical Cells
of an SFN Cell
8 SFN HetNet Smart

Cluster Organization
(FDD)
11 Inter-BBP SFN (FDD)
LOFD-070205 Adaptive SFN/SDMA 9 Adaptive SFN/SDMA

(FDD)
13 Inter-BBP Adaptive
SFN/SDMA (FDD)
LOFD-081208 Inter-eNodeB SFN Based on 15 Inter-eNodeB SFN

Coordinated eNodeB Based on eNodeB
Coordination (FDD)

eRAN
LOFD-081209 Inter-eNodeB Adaptive 17 Inter-eNodeB Adaptive

SFN/SDMA Based on SFN/SDMA based on
Coordinated eNodeB eNodeB Coordination
(FDD)
LAOFD-111204 Adaptive SFN/SDMA with 19 Adaptive SFN/SDMA

TM10 (Trial) with TM9/TM10 (Trial)
(FDD)
This document describes the following NB-IoT features.
MLOFD-121204 SFN 5 SFN (FDD)

7 4x4 MIMO in the
Overlapping Areas
of an SFN Cell
This document describes the following TDD features.
TDLOFD-001075 SFN 6 SFN (TDD)
7 4x4 MIMO in the

Overlapping Areas
of an SFN Cell
TDLOFD-002008 Adaptive SFN/SDMA 10 Adaptive SFN/SDMA

(TDD)
TDLOFD-001098 Inter-BBP SFN 12 Inter-BBP SFN (TDD)
TDLOFD-001081 Inter-BBP Adaptive SFN/ 14 Inter-BBP Adaptive

SDMA SFN/SDMA (TDD)
TDLOFD-001080 Inter-eNodeB SFN Based on 16 Inter-eNodeB SFN

Coordinated eNodeB Based on eNodeB
Coordination (TDD)
TDLOFD-001082 Inter-eNodeB Adaptive 18 Inter-eNodeB Adaptive

SFN/SDMA Based on SFN/SDMA based on
Coordinated eNodeB eNodeB Coordination
(TDD)

eRAN
TDLOFD-070227 PDCCH DCS in SFN 20 PDCCH DCS in SFN

(TDD)
TDLOFD-081221 PDCCH SDMA in SFN 21 PDCCH SDMA in SFN

(TDD)
2.4 Differences Between NB-IoT and FDD

NB-IoT NB-IoT FDD FDD Difference Section
Feature Feature Feature Feature
ID Name ID Name
MLOFD-1 SFN LOFD-003 SFN NB-IoT supports 5 SFN

21204 029 only intra-eNodeB (FDD)
common SFN, 7 4x4
including intra- and MIMO in
inter-BBP SFN. It the
does not support Overlappi
adaptive SFN/space ng Areas
division multiple Between
access (SDMA) or the
inter-eNodeB SFN. Physical
NB-IoT does not Cells of an
support sounding SFN Cell
reference signal 11 Inter-
(SRS) or physical BBP SFN
uplink control (FDD)
channel (PUCCH)
measurements,
handovers, or super
combined cells.
NOTE
Intra-eNodeB common SFN can be used in standalone, guardband, or in-band NB-IoT deployment
scenarios.

eRAN
2.5 Differences Between FDD and TDD

FDD FDD TDD TDD Difference Section
ID Name ID Name
LOFD-003 SFN TDLOFD- SFN Uplink independent 5 SFN

029 001075 reception and uplink (FDD)
joint reception work 6 SFN
differently between (TDD)
FDD and TDD.
7 4x4
The SFN function is MIMO in
compatible with the
different base station Overlappi
models in FDD and ng Areas
TDD. Between
the
Physical
Cells of an
SFN Cell
TDLOFD- Inter-BBP None 11 Inter-

001098 SFN BBP SFN
(FDD)
12 Inter-
BBP SFN
(TDD)
LOFD-070 Adaptive TDLOFD- Adaptive UE scheduling 9 Adaptive

205 SFN/ 002008 SFN/ attribute decision is SFN/
SDMA SDMA different in FDD and SDMA
TDD. (FDD)
10
Adaptive
SFN/
SDMA
(TDD)
TDLOFD- Inter-BBP None 13 Inter-

001081 Adaptive BBP
SFN/ Adaptive
SDMA SFN/
SDMA
(FDD)
14 Inter-
BBP
Adaptive
SFN/
SDMA
(TDD)

eRAN

ID Name ID Name
LOFD-081 Inter- TDLOFD- Inter- None 15 Inter-

208 eNodeB 001080 eNodeB eNodeB
SFN Based SFN Based SFN
on on Based on
Coordinate Coordinate eNodeB
d eNodeB d eNodeB Coordinat
ion (FDD)
16 Inter-
eNodeB
SFN
Based on
eNodeB
Coordinat
ion (TDD)
LOFD-081 Inter- TDLOFD- Inter- None 17 Inter-

209 eNodeB 001082 eNodeB eNodeB
Adaptive Adaptive Adaptive
SFN/ SFN/ SFN/
SDMA SDMA SDMA
Based on Based on based on
Coordinate Coordinate eNodeB
d eNodeB d eNodeB Coordinat
ion (FDD)
18 Inter-
eNodeB
Adaptive
SFN/
SDMA
based on
eNodeB
Coordinat
ion (TDD)
LAOFD-11 Adaptive N/A N/A This feature is 19

1204 SFN/ supported only by Adaptive
SDMA FDD. SFN/
with TM10 SDMA
(Trial) with TM9/
TM10
(Trial)
(FDD)
N/A N/A TDLOFD- PDCCH This feature is 20

070227 DCS in supported only by PDCCH
SFN TDD. DCS in
SFN
(TDD)

eRAN

ID Name ID Name
N/A N/A TDLOFD- PDCCH This feature is 21

081221 SDMA in supported only by PDCCH
SFN TDD. SDMA in
SFN
(TDD)

eRAN
SFN Feature Parameter Description 3 Overview
3 Overview
3.1 Introduction
A single-frequency LTE network experiences strong interference between cells, especially at
cell edges. The SFN function is introduced by Huawei to solve this problem. With SFN
enabled, multiple physical cells are combined into one logical cell, eliminating cell edges
between the physical cells and reducing interference between them.
SFN allows multiple overlapping physical cells served by multiple radio frequency (RF)
modules working on the same frequency to be combined into one logical cell. The physical
cells must work on the same frequency and have the same bandwidth. The physical resource
block (PRB) resources available in an SFN cell are the same as the original PRB resources of
one constituent physical cell.
In the following descriptions of this document, the cell formed through combination is called
an SFN cell and the radio communications area served by an RF module is called a physical
cell. After being combined, all physical cells in an SFN cell use the same physical cell
identifier (PCI). The physical cells in an SFN cell can be intra-BBP, inter-BBP, or inter-
eNodeB cells.
For FDD, a maximum of six physical cells can be combined. For TDD, a maximum of seven
physical cells served by RRUs can be combined, and a maximum of six physical cells served
by pRRUs can be combined.
The SFN operating principles for different types of RF modules are the same in this
document. This document uses RRUs as an example.
NOTE
pRRUs are low-power RRUs introduced in the Huawei LampSite solution. A pRRU group is composed
of 1 to 16 pRRUs that are RF combined.
When two RRUs are combined to serve a physical cell, the physical cell is the coverage areas of the two
RRUs.
Figure 3-1 illustrates a transition from non-SFN cells to an SFN cell, where some edges of
the three non-SFN cells become part of the SFN cell center.

eRAN
Figure 3-1 Transition from non-SFN cells to an SFN cell
In this document, SFN is a collective term for common SFN and adaptive SFN. Common
SFN refers to the following functions: SFN, inter-BBP SFN, and inter-eNodeB SFN based on
eNodeB coordination. Adaptive SFN refers to the adaptive SFN/SDMA function and other
functions using adaptive SFN/SDMA.
3.2 Application Scenarios

For FDD, SFN is applicable for the following scenarios:
l Outdoor coverage
l Indoor coverage
l Indoor and outdoor joint coverage
l High-speed railway coverage
For NB-IoT, SFN is applicable for the following scenarios:
l Outdoor coverage
l Indoor coverage
l Indoor and outdoor joint coverage
For TDD, SFN is applicable for the following scenarios:
l Outdoor coverage
l Indoor coverage
Outdoor Coverage
When RRUs are deployed in densely populated outdoor areas, the RRUs are spaced close
together to ensure adequate coverage. This deployment, however, leads to high interference
between physical cells and results in the following:

eRAN
l Control channels cannot be properly demodulated.

l The signal to interference plus noise ratio (SINR) of physical downlink shared channel
(PDSCH) for cell edge users (CEUs) decreases. This decreases cell throughput and user
experience deteriorates.
If SFN is used, most of the overlapping cell edges of the original common cells become part
of the SFN cell center, as illustrated in Figure 3-2. This change mitigates the interference and
reduces the number of handovers between common cells.
Figure 3-2 Combining the coverage areas of multiple RRUs into one SFN cell in outdoor
areas
Indoor Coverage
Indoor coverage faces the following challenges:
l Service drops may occur in an elevator when the elevator moves quickly between
different floors. Service drops may also occur because of sudden changes in signal
strength when the elevator door is opened or closed.
l A UE experiences frequent handovers when it is moved between different floors.
l It is difficult to plan radio network parameters (such as PCI and neighbor relationship)
when there are a large number of indoor cells.
To meet the preceding challenges, SFN provides the following two solutions:
l RRUs are combined to serve an SFN cell, as shown in Figure 3-3.
l pRRU groups are combined to serve an SFN cell, as shown in Figure 3-4.

eRAN
Figure 3-3 Indoor coverage with RRUs combined to serve an SFN cell
As illustrated in Figure 3-3, six RRUs are deployed in the 18-floor building to serve six
physical cells before SFN is used. Handovers are triggered when a UE moves across different
cells. After SFN is used, a single SFN cell served by six RRUs provides coverage for the
entire building, reducing the number of handovers between the physical cells.

eRAN
Figure 3-4 Indoor coverage with pRRU groups combined to serve an SFN cell
As shown in Figure 3-4, pRRU groups are deployed in different floors. A pRRU group can be
composed of 1 to 16 pRRUs that are RF combined through an RHUB. Multiple pRRU groups
can be combined to serve an SFN cell. In an SFN cell, a pRRU group maps a physical cell,
reducing handovers due to UE movement.
NOTE
pRRUs in a pRRU group can be connected to different RHUBs. In this scenario, RHUBs must be
cascaded.
One RHUB can support a maximum of two cross-RHUB SFN cells. For example, if a pRRU group of
SFN cell 1 is set up on RHUB 1 and RHUB 2, a pRRU group of SFN cell 2 can be set up on RHUB 2
and RHUB 3.
Outdoor and Indoor Joint Coverage (FDD)

Outdoor and indoor joint coverage faces the following challenges:
l When UEs move between outdoor and indoor areas, service drops may occur in outdoor-
indoor overlapping areas owing to delayed handovers because the signal strength
seriously fluctuates in these areas.
l In indoor areas (especially in higher floors), indoor-to-outdoor handovers may occur
when radio signals severely fluctuate due to outdoor-to-indoor interference.
As illustrated in Figure 3-5, outdoor and indoor RRUs are combined to serve one SFN cell
for:
l Reducing the probability of service drops due to handovers in indoor-outdoor

overlapping areas.
l Mitigating outdoor-to-indoor interference.

eRAN
Figure 3-5 Outdoor and indoor joint coverage
High-Speed Railway Coverage (FDD)

If common cells are deployed for high-speed railway coverage, too many handovers occur
because of high-speed movement but limited cell radii. Excessive handovers affect user
experience.
As shown in Figure 3-6, two RRUs are combined to serve an SFN cell, expanding the
effective cell radius and reducing the number of handovers when UEs move across different
physical cells.

eRAN
Figure 3-6 High-speed railway coverage

eRAN
SFN Feature Parameter Description 4 General Principles
4 General Principles
4.1 Independent Scheduling and Joint Scheduling

When independent scheduling is used, the UE occupies time-frequency resources of a single
RRU. Independent scheduling can be used for UEs that are located in the center of a physical
cell and near an RRU, such as UEs 3 and 4 in Figure 4-1. Such UEs receive less interference
from other RRUs. RRU 3 and RRU 2 independently allocate resources to UE 3 and UE 4,
respectively.
When joint scheduling is used, the time-frequency resources of multiple RRUs are uniformly
scheduled for any UE that is located in the coverage area of all these RRUs. Joint scheduling
can be used for UEs in the coverage overlaps between physical cells, such as UE 1 and UE 2
in Figure 4-1. These two UEs can receive signals from multiple RRUs at the same time.
Independently scheduled UEs and jointly scheduled UEs are identified based on whether the
UE occupies time-frequency resources of a single RRU or multiple RRUs.
l Independently scheduled UEs
Independently scheduled UEs are those which occupy the time-frequency resources of
only one RRU. Their working RRU list only contains this one RRU. A working RRU is
an RRU that can receive signals from or send signals to a UE, and the strength of the
arrival signals meets requirements. There can be multiple working RRUs for a UE.
l Jointly scheduled UEs
Jointly scheduled UEs are those which occupy the time-frequency resources of multiple
RRUs. Their working RRU list contains multiple RRUs.
After adaptive SFN is enabled, the eNodeB uses joint scheduling or independent scheduling
in an adaptive manner to allocate resources to a UE, as shown in Figure 4-1.

eRAN
Figure 4-1 Adaptive use of independent and joint scheduling
4.2 UE Scheduling Attribute Decision (FDD)

In the UE scheduling attribute decision procedure, the eNodeB creates a list of working RRUs
based on uplink measurement results, and then determines whether the UE is an
independently or jointly scheduled UE based on the number of working RRUs in the list. UE
scheduling attributes are determined separately in the uplink and downlink. The decision
period is specified by the CellDlschAlgo.UeAttJudgePeriod parameter.
Downlink UE Scheduling Attribute Decision

Figure 4-2 shows the procedure for determining UE scheduling attributes in the downlink.

eRAN
Figure 4-2 Procedure for determining UE scheduling attributes in the downlink
The procedure is as follows:

1. When a measurement event triggers UE scheduling attribute decision for a UE, the
eNodeB calculates downlink equivalent reference signal received power (RSRP) values
based on the RSRP values of signals from the UE to each RRU.
2. The eNodeB sorts the RRUs in descending order of downlink equivalent RSRP values.
3. The eNodeB selects the RRU with the largest downlink equivalent RSRP value as the
target RRU of the UE.
4. The eNodeB checks the UE capabilities. The check is triggered only when the
TM10Switch option of the CellAlgoSwitch.EnhMIMOSwitch parameter is selected and

eRAN
the cell load exceeds the threshold specified by the CellDlschAlgo.SfnDlHighLoadThd

parameter.
5. The eNodeB calculates the difference between the equivalent RSRP of the target RRU
and that of other RRUs (this difference is termed isolation degree) and compares the
differences with a decision threshold. If a difference is less than the threshold, the
eNodeB adds the corresponding RRU to the working RRU list. The decision threshold is
set based on an isolation degree threshold offset and a UE scheduling attribute decision
RSRP hysteresis.
Depending on the load status of an SFN cell, different decision thresholds are used, as
shown in Figure 4-3.
– When the load of the SFN cell is changing from a heavy load to a light load, if the
PRB usage of the SFN cell becomes lower than or equal to the value of the
CellDlschAlgo.SfnDlLowLoadThd parameter, the value of the
CellDlschAlgo.DlLowLoadSdmaThdOffset parameter is used as the isolation
degree threshold offset. In this scenario, the eNodeB attempts to enable UEs in the
SFN cell to be jointly scheduled by multiple RRUs, therefore improving user
experience.
– When the load of the SFN cell is changing from a light load to a heavy load, if the
PRB usage of the SFN cell becomes higher than or equal to the value of the
CellDlschAlgo.SfnDlHighLoadThd parameter, the value of the
CellDlschAlgo.DlHighLoadSdmaThdOffset parameter is used as the isolation
degree threshold offset. In this scenario, the eNodeB attempts to enable UEs in the
SFN cell to be independently scheduled for implementing space division
multiplexing to increase spectral efficiency and cell capacity.
If adaptive SFN is enabled in a cell served by four to six RRUs, changes in UE
scheduling attributes cause the PRB usage to change. The PRB usage change can result
in ping-pong switching between UE scheduling attributes and between transmission
modes. To prevent this, set the CellDlschAlgo.SfnDlLowLoadThd parameter to a
smaller value.
The CellDlschAlgo.UeAttJudgeRsrpHyst parameter can be set to prevent ping-pong
RRU inclusion in and exclusion from the working RRU list.
Figure 4-3 Determining the load status of an SFN cell and selecting a decision threshold
If the SfnDlSchAttriAdjsSwitch option of the CellAlgoSwitch.SfnAlgoSwitch

parameter is selected, the eNodeB adjusts UE scheduling attributes adaptively based on
service status.

eRAN
If the AsfnFastAttSwitch option of the CellAlgoSwitch.SfnAlgoSwitch parameter is

selected, UE scheduling attributes are adjusted in each TTI based on the amount of
required resources and the amount of available resources as follows:
– When the amount of required resources in a TTI does not exceed the amount of
available resources in the TTI, the value of
CellDlschAlgo.DlLowLoadSdmaThdOffset is used as the isolation degree
threshold offset. In this scenario, the eNodeB attempts to enable UEs in the SFN
cell to be jointly scheduled by multiple RRUs to improve user experience.
– When the amount of required resources in a TTI exceeds the amount of available
resources in the TTI, the value of the CellDlschAlgo.DlHighLoadSdmaThdOffset
parameter is used as the isolation degree threshold offset. In this scenario, the
eNodeB attempts to enable UEs in the SFN cell to be independently scheduled for
implementing space division multiplexing to increase spectral efficiency and cell
capacity.
6. The eNodeB determines the UE's scheduling attribute.
– If the working RRU list contains only one RRU, the UE is an independently
scheduled UE.
– If the working RRU list contains multiple RRUs, the UE is a jointly scheduled UE.
7. The eNodeB determines a transmission mode. If the TM10Switch option of the
CellAlgoSwitch.EnhMIMOSwitch parameter is selected and the cell load is higher than
the value of the CellDlschAlgo.SfnDlHighLoadThd parameter:
– If the UE complies with 3GPP Release 10 or 11, when it is independently scheduled
and the isolation degree is less than a preset threshold, the eNodeB uses TM9 or
TM10.
– If the UE complies with 3GPP Release 10 or 11, when it is independently scheduled
and the isolation degree is greater than a preset threshold or when it is jointly
scheduled, the eNodeB uses TM3 or TM4.
– If the UE complies with 3GPP Release 8 or 9, the eNodeB uses TM3 or TM4.
Uplink UE Scheduling Attribute Decision

Figure 4-4 shows the procedure for determining UE scheduling attributes in the uplink.

eRAN
Figure 4-4 Procedure for determining UE scheduling attributes in the uplink
1. When a measurement event triggers UE scheduling attribute decision for a UE, each
RRU measures the SINR and RSRP of signals from the UE. The eNodeB sorts the
SINRs and RSRP values in descending order.
2. The eNodeB selects a target RRU.
– The selection is based only on the SINR when the SfnTarRruAdptSelSwitch
option of the CellAlgoSwitch.SfnAlgoSwitch parameter is deselected. The eNodeB
selects the RRU with the highest SINR as the target RRU.
– The selection is based on the SINR or RSRP adaptively when the
SfnTarRruAdptSelSwitch option of the CellAlgoSwitch.SfnAlgoSwitch
parameter is selected. SINR is preferentially used for selection at first. If the
distance between the RRUs in an SFN cell is large and their coverage radiuses vary
significantly, the SINRs measured by RRUs are not accurate. In this scenario, the
eNodeB automatically uses RSRP for selecting the target RRU. It selects an RRU
with the largest RSRP and whose RSRP difference with other RRUs is greater than
or equal to the value of the CellUlschAlgo.TarRruSelRsrpOffsetThd parameter. If
no RRU meets the RSRP requirement, the target RRU selected based on the SINR
is used.
3. The eNodeB calculates the uplink RSRP difference between each non-target RRU and
the target RRU.

eRAN
4. The eNodeB compares the RSRP difference with a configured threshold. If the RSRP
difference for an RRU is less than or equal to the threshold, the RRU is added to the
working RRU list of the UE.
– If there is only one RRU in the working RRU list, independent scheduling is used.
– If there are multiple RRUs in the working RRU list, joint scheduling is used.
If the working RRU lists of two UEs do not overlap, the same RBs can be scheduled for
both of the UEs, which will increase uplink throughput when the
CellAlgoSwitch.SfnUlSchSwitch parameter is set to ADAPTIVE.
The two UEs in this scenario are called a UE pair. Two UEs (for example, UE A and UE
B) can be paired when they meet all the following conditions:
– The strength difference between signals received by UE A's target RRU from UE A
and signals received by this RRU from UE B is greater than the pairing
determination threshold specified by the CellUlschAlgo.SfnUlPairRsrpThd
parameter.
– The strength difference between signals received by UE B's target RRU from UE B
and signals received by this RRU from UE A is greater than the pairing
determination threshold specified by the CellUlschAlgo.SfnUlPairRsrpThd
parameter.
– The total RBs required by the two UEs outnumber the available RBs. The available
RBs are the remaining RBs after the RBs that have been scheduled are deducted
from the total RBs.
4.3 UE Scheduling Attribute Decision (TDD)

In the UE scheduling attribute decision procedure, the eNodeB creates a list of working RRUs
based on uplink measurement results, and then determines whether the UE is an
independently or jointly scheduled UE based on the number of working RRUs in the list. UE
scheduling attributes are determined separately in the uplink and downlink. The decision
period is specified by the CellDlschAlgo.UeAttJudgePeriod parameter.
Downlink UE Scheduling Attribute Decision

Figure 4-5 shows the procedure for determining UE scheduling attributes in the downlink.

eRAN
Figure 4-5 Procedure for determining UE scheduling attributes in the downlink
1. When a measurement event triggers UE scheduling attribute decision for a UE, the
eNodeB calculates the downlink equivalent RSRP values based on the RSRP values of
signals from the UE to each RRU.
3. The eNodeB selects the RRU with the largest downlink equivalent RSRP value as the
target RRU of the UE.
4. The eNodeB calculates the difference between the equivalent RSRP of the target RRU
and that of other RRUs (this difference is termed isolation degree) and compares the
differences with a decision threshold. If a difference is less than the threshold, the
eNodeB adds the corresponding RRU to the working RRU list.
When adaptive SFN/SDMA is enabled, the SFN cell can use a fixed or adaptive isolation
degree decision threshold. The adaptive threshold is adjusted based on load status. The
CellAlgoSwitch.SfnLoadBasedAdptSwitch parameter specifies whether a fixed or
adaptive threshold is used in the SFN cell.
– When this parameter is set to OFF, the SFN cell uses a fixed isolation degree
decision threshold.
– When this parameter is set to ON, the SFN cell uses an adaptive isolation degree
decision threshold adjusted based on load status. The eNodeB periodically measures
and updates the load status of a cell. The period is specified by the
CellDlschAlgo.SfnDlLoadPeriod parameter.

eRAN
When the CellAlgoSwitch.SfnLoadBasedAdptSwitch parameter is set to ON, the

SfnDl2LoadLevelAdptSwitch option of the CellAlgoSwitch.SfnAlgoSwitch parameter
can be selected to enable optimized load-based adaptive adjustment.
– If this option is deselected, load levels are not differentiated for SFN cells in the
downlink.
– If this option is selected, two load levels (light and heavy) are differentiated for
SFN cells in the downlink, as shown in Figure 4-6.
n When the load of the SFN cell is changing from a heavy load to a light load, if
the PRB usage of the SFN cell becomes lower than or equal to the value of the
CellDlschAlgo.SfnDlLowLoadThd parameter, the value of the
CellDlschAlgo.DlLowLoadSdmaThdOffset parameter is used as the isolation
degree threshold offset. In this scenario, the eNodeB attempts to enable UEs in
the SFN cell to be jointly scheduled by multiple RRUs, therefore improving
user experience.
n When the load of the SFN cell is changing from a light load to a heavy load, if
the PRB usage of the SFN cell becomes higher than or equal to the value of the
CellDlschAlgo.SfnDlHighLoadThd parameter, the value of the
CellDlschAlgo.DlHighLoadSdmaThdOffset parameter is used as the isolation
degree threshold offset. In this scenario, the eNodeB attempts to enable UEs in
the SFN cell to be independently scheduled for implementing space division
multiplexing to increase spectral efficiency and cell capacity.
Figure 4-6 Determining the load status of an SFN cell and selecting a decision
threshold
If the CellAlgoSwitch.SfnLoadBasedAdptSwitch parameter has been set to ON and the

SfnDl2LoadLevelAdptSwitch option of the CellAlgoSwitch.SfnAlgoSwitch parameter
has been selected, the SfnDlSchAttriAdjsSwitch option of the
CellAlgoSwitch.SfnAlgoSwitch parameter can be selected to enable the eNodeB to
adjust UE scheduling attributes adaptively based on service status.
– If the working RRU list contains only one RRU, the UE is an independently
scheduled UE.
– If the working RRU list contains multiple RRUs, the UE is a jointly scheduled UE.
Uplink UE Scheduling Attribute Decision

Figure 4-7 shows the procedure for determining UE scheduling attributes in the uplink.

eRAN
Figure 4-7 Procedure for determining UE scheduling attributes in the uplink

1. When a measurement event triggers UE scheduling attribute decision for a UE, each
RRU measures the SINR and RSRP of the UE.
2. The eNodeB sorts the SINRs and RSRP values in descending order.
3. The eNodeB selects the RRU with the highest SINR as the target RRU.
4. The eNodeB calculates the uplink RSRP difference between each non-target RRU and
the target RRU. If the RSRP difference between an RRU and the target RRU does not
exceed a specified threshold, this non-target RRU belongs to the working RRU list of the
UE.
When adaptive SFN/SDMA is enabled, the SFN cell can use a fixed or adaptive isolation
degree decision threshold. The adaptive threshold is adjusted based on load status. The
CellAlgoSwitch.SfnLoadBasedAdptSwitch parameter specifies whether a fixed or
adaptive threshold is used in the SFN cell.
– When this parameter is set to OFF, the SFN cell uses a fixed isolation degree
decision threshold.
– When this parameter is set to ON, the SFN cell uses an adaptive isolation degree
decision threshold adjusted based on load status. The eNodeB periodically measures
and updates the load status of a cell. The period is specified by the
CellUlschAlgo.SfnUlLoadPeriod parameter. When the network load is light, the

eRAN
SFN cell uses a high isolation degree decision threshold to make full use of RRU
resources, improving user experience. When the network load is heavy, the SFN
cell uses a low isolation degree decision threshold to facilitate spatial multiplexing,
improving spectral efficiency.
– If there is only one RRU in the working RRU list, independent scheduling is used.
– If there are multiple RRUs in the working RRU list, joint scheduling is used.
4.4 Downlink Joint Transmission

Downlink joint transmission is a technique in which multiple RF modules serving an SFN cell
use the same time-frequency resources to send the same data on physical channels, as shown
in Figure 4-8. Unlike the cells before the combination, physical downlink control channels
(PDCCHs) and PDSCHs do not experience interference between RRUs in the SFN cell,
which makes downlink joint transmission possible. Downlink joint transmission increases the
SINR for CEUs in physical cells, improving service experience at cell edges.
For details on physical channels and scheduling, see Physical Channel Resource Management
and Scheduling. In the case of NB-IoT cells, see NB-IoT Basics (FDD).
Figure 4-8 Downlink joint transmission
4.5 Uplink Independent Reception (FDD)

If independent reception is used in the uplink, as shown in Figure 4-9, the BBP receives the
PUSCH and PUCCH data from only the target RRU. For an NB-IoT cell, the BBP receives
the NB-IoT PUSCH (NPUSCH) data from only the target RRU.
If the options of the CellAlgoSwitch.SfnUplinkCompSwitch parameter are all deselected,
independent reception is used in the uplink.

eRAN
Figure 4-9 Example of uplink independent reception
The mechanism for selecting the target RRU is as follows:

l During a UE random access procedure, the BBP monitors the physical random access
channel (PRACH) at each RRU.
For FDD:
If SRS measurement is used, the BBP selects an RRU with the most preamble power
from the RRUs receiving the same preamble as the target RRU. SRS measurement is
used when the SRSCfg.SrsCfgInd parameter is set to BOOLEAN_TRUE and the
SRSCfg.FddSrsCfgMode parameter is set to DEFAULTMODE. For NB-IoT, the BBP
selects the RRU with the largest NPRACH SINR as the target RRU.
If the PUCCH measurement is used, the BBP selects the RRU with the largest RSRP
value of channel quality indicator (CQI) signals transmitted on the PUCCH as the target
RRU. PUCCH measurement is used when the SRSCfg.SrsCfgInd parameter is set to
BOOLEAN_FALSE or the SRSCfg.FddSrsCfgMode parameter is set to
ADAPTIVEMODE, and the PucchMeasOptSwitch option of the
CellAlgoSwitch.PucchAlgoSwitch parameter is selected. SRSs occupy uplink resources
and can affect the uplink peak throughput of individual UEs. Therefore, if uplink
throughput is limited, PUCCH measurement is recommended. For details about SRSs,
see Physical Channel Resource Management.
If PUCCH measurement instead of SRS measurement is used in an SFN cell, fewer
uplink resources are consumed, increasing User Uplink Average Throughput.
However, PUCCH measurement performance is poorer than SRS measurement
performance because the PUCCH measurement period is longer than the SRS
measurement period. As a result, the CQI reporting frequency decreases and the average
CQI fluctuates. In addition, downlink UE data rates decrease slightly and the service
drop rate increases slightly.
For NB-IoT, the BBP monitors the NB-IoT PRACH (NPRACH) at each RRU, and
selects the RRU with the largest NPRACH SINR as the target RRU.
If a UE encounters failure in the initial transmission or retransmission of the first uplink
data, the BBP selects the RRU with the highest SINR as the target RRU. The RRU
SINRs are obtained based on the UE demodulation reference signal (DMRS)
measurement.

eRAN
l After random access:

For FDD, wideband SRS measurements are used to determine whether to change the
target RRU. The BBP selects the RRU with the highest SRS SINR as the target RRU.
For NB-IoT, the BBP selects the RRU with the highest DMRS SINR or RSRP as the
target RRU. DMRS measurements are used to determine whether to change the target
RRU because SRS measurements are not supported.
4.6 Uplink Joint Reception (FDD)

In uplink joint reception, the BBP receives PUSCH data from both the target RRU and
cooperating RRUs and demodulates the data together. Therefore, uplink joint reception gains
are produced. Cooperating RRUs refer to the RRUs which were originally creating strong
interference on the target RRU's transmissions, but the interfering signals are now converted
into useful signals through cooperation.
For an NB-IoT cell, the BBP receives NPUSCH data.
Figure 4-10 shows joint reception. When any option of the
CellAlgoSwitch.SfnUplinkCompSwitch parameter is selected, joint reception is used in the
uplink.
Cooperating RRUs are selected based on uplink SRS, DMRS, or PUCCH measurements. An
RRU is selected as a cooperating RRU if the difference between its uplink signal strength and
that of the target RRU does not exceed the value of the CellUlCompAlgo.SfnUlCompThd
parameter. No more than two RRUs can be selected as cooperating RRUs.
If a UE in an SFN cell is moving, then inaccurate measurement of uplink signals received by
RRUs may cause the eNodeB to select an incorrect target RRU for the UE. To ensure that the
eNodeB selects a correct target RRU, it is recommended that the SfnTarRruAdptSelSwitch
option of the CellAlgoSwitch.SfnAlgoSwitch parameter be selected.
NOTE
Alternatively, the SfnTarRruSelEnhSwitch option of the CellAlgoSwitch.SfnAlgoSwitch parameter

can be selected. However, this option will be removed in later versions and its functionality will be
replaced by that of the SfnTarRruAdptSelSwitch option.

eRAN
Figure 4-10 Joint reception
Joint reception can be used among 1R RRUs, 2R RRUs, or 4R RRUs, among 1R and 2R
RRUs, and among 2R and 4R RRUs. If joint reception is used among 4R RRUs or among 2R
and 4R RRUs, only two RRUs can be involved.
A 1R or 2R serving cell supports high-order CoMP when the SfnUplinkComp3CellSwitch
option of the CellAlgoSwitch.SfnUplinkCompSwitch parameter is selected and the
CellAlgoSwitch.UlHighOrderCompSwitch parameter is set to ON. A maximum of three
cooperating cells can be selected for this cell.
4.7 Uplink Independent Reception (TDD)

If independent reception is used in the uplink, as shown in Figure 4-11, the BBP receives the
PUSCH and PUCCH data from only the target RRU.
If the options of the CellAlgoSwitch.SfnUplinkCompSwitch parameter are all deselected,
independent reception is used in the uplink.

eRAN
Figure 4-11 Example of uplink independent reception
The eNodeB measures SRSs or DMRSs and selects the RRU with the highest SRS or DMRS
SINR as the target RRU.
If the TTI-level layer-2 (MAC layer) selective reception function is enabled, the uplink
coverage improves. In TTI-level layer-2 selective reception, multiple working RRUs of a UE
demodulate PUSCH data for the UE and then report the demodulation results to the MAC
layer. (TTI is short for transmission time interval.) Based on the demodulation results, the
MAC layer combines the correctly demodulated PUSCH data.
This function is controlled by the SfnUll2SelectiveRcvSwitch option of the

CellAlgoSwitch.SfnAlgoSwitch parameter.
l If this option is selected, layer-2 selective reception is enabled and multiple working
RRUs receive PUSCH data for selective reception at the MAC layer.
l If this option is deselected, only the target RRU receives PUSCH data for non-selective
reception at the MAC layer.
4.8 Uplink Joint Reception (TDD)

In uplink joint reception, the BBP receives PUSCH data from both the target RRU and
cooperating RRUs and demodulates the data together. Therefore, uplink joint reception gains
are produced. Cooperating RRUs refer to the RRUs which were originally creating strong
interference on the target RRU's transmissions, but the interfering signals are now converted
into useful signals through cooperation.
Figure 4-12 shows joint reception. When any option of the

CellAlgoSwitch.SfnUplinkCompSwitch parameter is selected, joint reception is used in the
uplink.
Cooperating RRUs are selected based on the measurement result of uplink SRSs or DMRSs.
An RRU is selected as a cooperating RRU if the uplink signal strength difference between it
and the target RRU does not exceed the value of the CellUlCompAlgo.SfnUlCompThd
parameter. No more than two RRUs can be selected as cooperating RRUs.

eRAN
If a UE in an SFN cell is moving, then inaccurate measurement of uplink signals received by

RRUs may cause the eNodeB to select an incorrect target RRU for the UE. To ensure that the
eNodeB selects a correct target RRU, it is recommended that the SfnTarRruAdptSelSwitch
option of the CellAlgoSwitch.SfnAlgoSwitch parameter be selected.
NOTE
Alternatively, the SfnTarRruSelEnhSwitch option of the CellAlgoSwitch.SfnAlgoSwitch parameter

can be selected. However, this option will be removed in later versions and its functionality will be
replaced by that of the SfnTarRruAdptSelSwitch option.
Figure 4-12 Joint reception
Joint reception can be used among 2R RRUs, 4R RRUs, or 8R RRUs, and among RRUs of
2R, 4R, and 8R combinations. If the RRUs are of different numbers of receive antennas, only
two RRUs can be involved.
4.9 Coordination Between Adaptive SFN/SDMA and

Multiple-Antenna Techniques
Multi-user MIMO (MU-MIMO) can be used with adaptive SFN/SDMA to further increase
cell throughput. In TDD cells, multi-user beamforming (MUBF) and coordinated
beamforming (CBF) can also be used with adaptive SFN/SDMA.
MU-MIMO in Adaptive SFN/SDMA

In MU-MIMO mode, multiple UEs use the same time-frequency resources for data
transmission in the uplink. In addition to diversity and array gains (as offered by uplink
receive diversity), MU-MIMO also offers multiplexing gains. System gains brought by MU-
MIMO are subject to the SINRs of MIMO UEs and channel correlations between UEs. For
details about the principles of MU-MIMO, see MIMO.
In FDD cells, when adaptive SFN/SDMA and MU-MIMO are used together, UE pairing
policies differ between jointly scheduled UEs and independently scheduled UEs. For a UE

eRAN
that has been paired for first-layer transmission, the pairing policies for second-layer
transmission are as follows:
l If the UE is a jointly scheduled UE (for example, UE A), it can be paired with an
independently scheduled UE whose target RRU is the same as that for UE A, or with
another jointly scheduled UE whose target RRU is the same as that for UE A and
working RRUs are included in the working RRU list of UE A. After UE pairing
succeeds, the eNodeB uses MU-MIMO to receive data from the UEs' respective target
RRUs for demodulation.
l If the UE is an independently scheduled UE, it must be paired with another
independently scheduled UE served by the same target RRU.
In TDD cells, when adaptive SFN/SDMA and MU-MIMO are used together, UE pairing
policies differ between jointly scheduled UEs and independently scheduled UEs. For a UE
that has been paired for first-layer transmission, the pairing policies for second-layer
transmission are as follows:
l If the UE is a jointly scheduled UE (for example, UE A), it can be paired with an
independently scheduled UE whose target RRU is the same as that for UE A, or with
another jointly scheduled UE whose target RRU is the same as that for UE A and
working RRUs are included in the working RRU list of UE A. To mitigate inter-stream
interference between paired UEs and improve uplink performance, the eNodeB
preferentially selects a UE whose working RRU list does not include the target RRU
involved in first-layer pairing. After UE pairing succeeds, the eNodeB uses MU-MIMO
to receive data from the UEs' respective target RRUs for demodulation.
l If the UE is an independently scheduled UE, it must be paired with another
independently scheduled UE served by the same target RRU.
MUBF in Adaptive SFN/SDMA (TDD)

MUBF is applicable to the UEs with high channel correlations and considerable spatial
diversities. In MUBF mode, multiple downlink data streams can be transported using the
same time and frequency resources, which increases cell throughput. When adaptive SFN/
SDMA is enabled, independently scheduled UEs under each RRU can be paired for MUBF.
For details about the principles of MUBF, see Beamforming (TDD).
Inter-RRU CBF in Adaptive SFN/SDMA (TDD)

For details, see 22 Inter-RRU CBF in Adaptive SFN/SDMA (TDD).

eRAN
SFN Feature Parameter Description 5 SFN (FDD)
5 SFN (FDD)
5.1 Principles
The SFN function enables multiple RRUs to be combined to serve a single SFN cell. This
function requires that the percentage of UEs in the overlapping areas between the physical
cells served by the RRUs exceed 20%. To combine RRUs or pRRUs to serve an SFN cell, set
the Cell.MultiRruCellMode parameter to SFN. To combine pRRU groups to serve an SFN
cell, set this parameter to MPRU_AGGREGATION.
In the uplink, either independent or joint reception is used. For details on uplink independent
reception and joint reception, see 4.5 Uplink Independent Reception (FDD) and 4.6 Uplink
Joint Reception (FDD), respectively. In the downlink, multi-RRU joint transmission is used.
For details, see 4.4 Downlink Joint Transmission.
Joint scheduling is used in SFN cells. Joint scheduling is enabled in the uplink when the
CellAlgoSwitch.SfnUlSchSwitch parameter is set to JOINT and enabled in the downlink
when the CellAlgoSwitch.SfnDlSchSwitch parameter is set to JOINT. For details on joint
scheduling, see 4.1 Independent Scheduling and Joint Scheduling.
This section describes intra-BBP SFN. The eNodeB uses this function to combine physical
cells served by the same BBP into an SFN cell.
NOTE
The SFN operating principles for RRUs and RFUs are the same in this document. This document uses
RRU as an example.
5.2 Network Analysis
5.2.1 Benefits
The SFN function provides the following benefits:
l Reduced interference and increased SINR in the overlapping areas between physical
cells, and therefore improved user experience in these areas. The lower the SINR before
the combination, the greater the gains after the combination.
l Extended cell coverage and fewer UE handovers between physical cells.

eRAN
For FDD:
If three RRUs are combined to serve an SFN cell in a densely populated urban outdoor area
and the total Downlink Resource Block Utilizing Rate of the common cells before the
combination is less than 45%, the cell throughput remains unchanged but User Downlink
Average Throughput increases by 30% to 80% after the combination. When the network
load rate is 100%, the average PDCCH and PDSCH SINRs increase by 2 dB to 3 dB. The
specific gains depend on the inter-RRU distance, UE distribution, and traffic model.
If two pRRU groups (five pRRUs each) are combined to serve an indoor SFN cell and the
total Downlink Resource Block Utilizing Rate of the common cells before the combination
is less than 60%, User Downlink Average Throughput increases by 10% to 50% after the
combination. When the network load rate is 100%, the average PDCCH and PDSCH SINRs
increase by 10 dB to 20 dB. The specific gains depend on the deployment density of pRRUs
before the combination, number of pRRUs used to form the SFN cell, UE distribution, and
traffic model.
For any given set of supported functions, and environmental condition, if the conditions
required to use SFN are met, the expected KPI changes in SFN cells compared with common
cells are listed in the following table.
Table 5-1 Expected KPI changes in SFN cells compared with common cells
KPI Expected Change
Cell Downlink Average Throughput No decrease
Cell Uplink Average Throughput No decrease
User Downlink Average Throughput Increase
User Uplink Average Throughput Increase
E-RAB Setup Success Rate No decrease
RRC Setup Success Rate No decrease
Intra-Frequency Handover Out Success No decrease

Rate
Service Drop Rate No increase
Uplink Resource Block Utilizing Rate Increase
Downlink Resource Block Utilizing Rate Increase
NOTE
The expected KPI changes in the table are not applicable to subway and high-speed railway scenarios.
l The values of the following indicators may increase significantly:

– Cell Uplink Average Throughput, Cell Downlink Average Throughput, User
Uplink Average Throughput, and User Downlink Average Throughput
If the traffic volume and data transmission duration of an SFN cell have a different
change curve from the total traffic volume and total data transmission duration of
all cells combined into the SFN cell, Cell Downlink Average Throughput and

eRAN
Cell Uplink Average Throughput may change significantly after the combination.
For example, the traffic volume of an SFN cell may be two times the total traffic
volume of the physical cells before the combination. At the same time, the data
transmission duration of the SFN cell could be 1.5 times that of the physical cells
before the combination. In this instance, Cell Uplink Average Throughput and
Cell Downlink Average Throughput would increase after the combination.
Similarly, the values of User Uplink Average Throughput and User Downlink
Average Throughput also increase significantly.
– L.ResOpt.CCELimit.PRB.DL
The value of this counter increases because the PDCCH resources of the SFN cell
become fewer than those of common cells.
NOTE
All counters for calculating these indicators are measured on the basis of a single SFN cell.
For NB-IoT:
For example, three RRUs are combined to serve an NB-IoT SFN cell in a densely populated
urban outdoor area. If the cell load is low, the throughput of the SFN cell is the same, the
average downlink SINR increases by about 2 dB, and the service drop rate decreases after the
combination. The cell load is regarded low when the following condition is met: After the
30% downlink subcarrier usage for common channel overheads is deducted, the total
downlink subcarrier usage of the common NB-IoT cells used to form the SFN cell is less than
45%. The specific gains depend on the inter-RRU distance, UE distribution, and traffic model.
The downlink subcarrier usage of an NB-IoT cell and the average user-perceived downlink
UE throughput are calculated using the following formulas:
Downlink subcarrier usage of an NB-IoT cell =
L.NB.PRB.ChMeas.Subcarrier.DL.Used.Avg/L.NB.PRB.ChMeas.Subcarrier.DL.Avail x
100%
Average user-perceived downlink UE throughput = L.NB.Thrp.bits.DL/
L.NB.Thrp.Time.DL
In in-band scenarios, if SFN is enabled for LTE cells, it is recommended that SFN be also
enabled for NB-IoT cells.
NOTE
These gains are obtained on the assumption that UEs are evenly distributed in the SFN cell and services
are initiated at a random time.
5.2.2 Impacts
Network Impacts
Enabling the SFN feature decreases the overall system capacity to some extent.
After common cells are combined into an SFN cell, if the load of the SFN cell is heavier than
that of the common cells used to form it, the load of the neighboring common cells will
increase and the SINR will decrease slightly.
If an SFN cell is comprised of physical cells whose coverage is limited, uplink path loss and
downlink path loss are inconsistent in the SFN cell. As a result, the access performance
deteriorates for CEUs, affecting the counters related to cell access.

eRAN
For FDD, the impacts are as follows:

l If three RRUs are combined to serve an SFN cell in a densely populated urban outdoor
area and the total downlink PRB usage of common cells before the combination is less
than 45%, the gain in User Downlink Average Throughput decreases with the increase
of the Downlink Resource Block Utilizing Rate. If the total Downlink Resource Block
Utilizing Rate exceeds 45%, a negative gain will be produced. If the total Downlink
Resource Block Utilizing Rate of the common cells before the combination exceeds
100%, Cell Downlink Average Throughput may decrease because the number of PRBs
available after forming the SFN cell is limited. The specific impacts depend on the inter-
RRU distance, UE distribution, and traffic model.
l If two pRRU groups (five pRRUs each) are combined to serve an indoor SFN cell and
the total Downlink Resource Block Utilizing Rate of the common cells used to form
the SFN cell is less than 60%, the gain in User Downlink Average Throughput
decreases with the increase of the Downlink Resource Block Utilizing Rate, or a
negative gain can be produced. The specific impacts depend on the deployment density
of pRRUs before the combination, number of pRRUs used to form the SFN cell, UE
distribution, and traffic model.
l If an SFN cell is comprised of physical cells with different numbers of transmit channels,
UEs reporting rank 2 in a 1T physical cell of this SFN cell encounter the following
changes compared with UEs in a common 1T cell: The User Downlink Average
Throughput, PDSCH modulation and coding scheme (MCS) index, and downlink CQI
decrease; the downlink RBLER increases.
l If SRS measurement is not enabled for common cells and uplink interference is weak,
User Uplink Average Throughput in the SFN cell decreases after common cells are
reconstructed to build an SFN cell.
For NB-IoT:
If the NB-IoT downlink subcarrier usage increases, the gain in user-perceived throughput
decreases. If the total NB-IoT downlink subcarrier usage (excluding common channel
overheads, which account for 30% of the subcarrier resources) exceeds 45%, user-perceived
downlink throughput decreases.
If the total downlink subcarrier usage of the NB-IoT cells used to form the SFN cell exceeds
100%, downlink cell throughput will decrease because downlink subcarrier resources are
insufficient after the SFN cell is formed.
NOTE
The preceding impacts are measured based on the assumption that UEs are evenly distributed in the SFN
cell and that services are initiated at a random time.
Function Impacts
l Functions related to cell planning

eRAN
Functio Function Referen Description

n Switch ce
Name
Flexible DdCellGroup. Flexible When cells with punctured RBs are used to
bandwid DdBandWidth Bandwidt form SFN cells, the number of UEs
th based h based transmitting SRSs decreases because less
on on bandwidth is available for transmitting
overlapp Overlap SRSs. As a result, fewer UEs are allowed
ing Carriers in SFN cells.
carriers (FDD)
Compac Cell.Customized Compact When cells with punctured RBs are used to
t BandWidthCfgI Bandwidt form SFN cells, the number of UEs
bandwid nd h (FDD) transmitting SRSs decreases because less
th bandwidth is available for transmitting
SRSs. As a result, fewer UEs are allowed
in SFN cells.
Uplink UlVmimoSwitc MIMO When the options of the

2x4 h option of the CellAlgoSwitch.SfnUplinkCompSwitch
MU- CellAlgoSwitch parameter are selected for an SFN cell with
MIMO .UlSchSwitch uplink 2x4 MU-MIMO enabled, uplink
parameter joint reception takes effect in precedence
over MU-MIMO.
Uplink UlVmimoSwitc MIMO When the options of the

2x2 h option of the CellAlgoSwitch.SfnUplinkCompSwitch
MU- CellAlgoSwitch parameter are selected for an SFN cell with
MIMO .UlSchSwitch uplink 2x2 MU-MIMO enabled, uplink
parameter joint reception takes effect in precedence
over MU-MIMO.
l Functions related to mobility and load management

n Switch ce
Name
High Cell.HighSpeed High If downlink AFC is enabled, only intra-

speed Flag Speed BBP SFN (RRUs serving an SFN cell
mobility Mobility directly connect to the same BBP) is
supported, and inter-BBP SFN and inter-
eNodeB SFN based on eNodeB
coordination are not supported.
l Functions related to resource management

eRAN
Functio Function Referenc Description

n Name Switch e
UL CPC UL_COORD_P Uplink UL CPC does not take effect in SFN cells
C_SWITCH Coordinat because SFN works in low-load scenarios
option of the ed but UL CPC does not.
UlCsAlgoPara. Schedulin
UlCsSw g
parameter
Uplink PUSCHCfg.Qa Modulatio When the LBBPd3 is used and uplink

64QAM m64Enabled n 64QAM is enabled for an SFN cell served
Schemes by 4R+4R RRUs, joint reception does not
work in the cell.
CSI EmimoCsiEnha eMIMO When both PUCCH measurement and

reportin nceSwitch (FDD) CSI reporting enhancement are enabled in
g option of the an SFN cell, CSI reporting enhancement
enhance CellAlgoSwitch. does not take effect.
ment EmimoSwitch
parameter
Coordin EmimoCpsSwit eMIMO In an SFN cell, co-channel interference

ated ch option of the (FDD) between physical cells is reduced. The
pilot CellAlgoSwitch. gains of coordinated pilot scheduling are
scheduli EmimoSwitch lower for an SFN cell than for a common
ng parameter cell.
Breathin BreathingPilotS Breathing In an SFN cell, co-channel interference

g Pilot witch option of Pilot between physical cells is reduced. In this
the scenario, the gains offered by breathing
CellDlschAlgo. pilot are lowered.
BreathingPilotA
lgoSwitch
parameter
Adaptiv AdptCellEdgeP Schedulin The SFN function combines physical cells

e power wrAllocSw g into an SFN cell, and the signal quality
allocatio option of the improves for some UEs located at the
n for CellAlgoSwitch. edges of the physical cells. Adaptive
cell- CellDlCoverEn power allocation for cell-edge UEs stops
edge hanceSwitch taking effect for these UEs after the
UEs parameter combination.
CSPC CspcAlgoPara. CSPC CSPC can be activated in SFN cells with

CspcAlgoSwitch the CellRacThd.CellCapacityMode
parameter set to NORMALCAPACITY,
but not in SFN cells with this parameter
set to LARGECAPACITY.

eRAN
Functio Function Referenc Description

n Name Switch e
Single SINGLE_CA_P None This function takes effect only for 4T

carrier WR_SHARE_S cells. If the physical cells constituting an
power W_FOR_4T SFN cell include non-4T physical cells,
sharing option of the this function does not take effect in the
for 4T PDSCHCfg.Tx SFN cell.
ChnPowerCfgS
w parameter
l Functions related to carrier aggregation

n Switch ce
Name
CA cell N/A Carrier PUCCH measurement cannot be used in

Aggregat SFN cells where the downlink
ion aggregation of three or more component
carriers is enabled.
l Functions related to CoMP

n Switch ce
Name
UL CPC UL_COORD_P Uplink UL CPC does not take effect in SFN cells
C_SWITCH Coordina because SFN works in low-load scenarios
option of the ted but UL CPC does not.
UlCsAlgoPara.Ul Scheduli
CsSw parameter ng

eRAN

n Switch ce
Name
UL UlJointReceptio UL If SFN is used with UL CoMP and uplink

CoMP nSwitch option of CoMP SRS measurement is selected, the
cell the cooperating common cells require SRS
CellAlgoSwitch. resources. If UL CoMP is enabled
UplinkCompSwit between SFN cells or between an SFN
ch parameter cell and a common cell, SRS
measurement is required for selecting
cooperating UEs and cells. SRS resources
must be preferentially allocated to UEs in
an SFN cell to perform SRS measurement
for selecting target RRUs and
determining UE scheduling attributes.
When there are a large number of UEs in
an SFN cell, the SRS resources used by
measurement for selecting cooperating
UEs and cells will be insufficient.
Therefore, UL CoMP between SFN cells
or between an SFN cell and a common
cell allows a smaller number of UL
CoMP UEs.
DL FDDHomNetDlC DL If the antenna modes of the physical cells

CoMP ompSwitch, CoMP forming an SFN cell are different, the
cell FDDHetNetDlCo (FDD) SFN cell will not be selected as a
mpSwitch, and cooperating cell for DL CoMP. DL
Tm9JtSwitch CoMP cannot be used between such SFN
options of the cells.
CellAlgoSwitch.
DlCompSwitch
parameter
l Functions related to interference mitigation

eRAN
Functio Function Switch Referen Description

n ce
Name
Dynami CellAlgoSwitch. TDM The impacts are as follows:

c TDM EicicSwitch eICIC l If SFN is enabled between micro cells
eICIC (FDD) associated with different macro cells,
dynamic TDM eICIC may not
produce optimal performance gains.
l SFN provides gains in macro cells
with light load, whereas dynamic
TDM eICIC provides gains in macro
cells with heavy load. It is not
recommended that SFN and dynamic
TDM eICIC be both enabled between
macro cells.
l If SFN is enabled between macro and
micro cells, dynamic TDM eICIC is
not supported because the SFN cell
uses a single ID.
l Functions related to RAN-terminal coordination

Functio Function Switch Referen Description
n ce
Name
Disconti CellDrxPara.Drx DRX and In an SFN cell where uplink SRS

nuous AlgSwitch Signaling measurement is used, DRX prolongs the
receptio Control SRS measurement period because SRS
n measurement is performed only in active
time.
Dynami CellAlgoSwitch. DRX and In an SFN cell where uplink SRS

c DRX DynDrxSwitch Signaling measurement is used, DRX prolongs the
Control SRS measurement period because SRS
measurement is performed only in active
time.
l Functions related to LTE evolution

eRAN
Functio Function Switch Referenc Description

n e
Name
Smart SMART_CARRI Multi- Virtual grids cannot be constructed for

carrier ER_SELECTIO carrier SFN cells.
selectio N_SW option of Unified
n based the Schedulin
on MultiCarrUnifie g
virtual dSch.MultiCarrie
grids rUnifiedSchSw
parameter
l Functions related to multi-RAT coordination

n e
Name
UMTS UMTS_LTE_ZE UMTS After the UMTS and LTE Zero

and LTE RO_BUFFER_Z and LTE Bufferzone function is enabled, only RB
Zero ONE_SW option Zero resources in the UMTS preferential
Bufferzo of the Bufferzon spectrum can be allocated for SRS
ne ULZeroBufferzo e transmission. As fewer resources can be
ne.ZeroBufZoneS used for SRS transmission, the
witch parameter performance of the SFN cell
deteriorates.
l Functions related to CIoT

n e
Name
Multi- None NB-IoT When the Cell.MultiRruCellMode

carrier Enhancem parameter is set to SFN for a multi-
ents carrier cell, the anchor and non-anchor
(FDD) carriers are separately used for intra-
frequency networking.
l Functions related to CloudAIR

eRAN

n e
Name
GSM SpectrumCloud.S GSM and When cells with shared RBs are used to
and LTE pectrumCloudSwi LTE form SFN cells, the number of UEs
spectru tch Spectrum transmitting SRSs decreases because
m Concurre less bandwidth is available for
concurre ncy transmitting SRSs. As a result, fewer
ncy UEs are allowed in SFN cells.
Dynami LTE_DYN_POW Dynamic Dynamic power sharing between LTE

c power ER_SHARING_S Power carriers is performed based on physical
sharing W option of the Sharing cells that share one RF module. When
between CellDynPowerSh Between this function is enabled in an SFN cell,
LTE aring.DynamicPo LTE dynamic power sharing between LTE
carriers werSharingSwitch Carriers carriers cannot provide maximum gains.
parameter If one of the RF modules serving an
SFN cell does not support power
sharing, this function will provide
negative gains. Therefore, this function
is not recommended for SFN cells.
5.3 Requirements
5.3.1 Licenses
RAT Feature ID Feature Name Model Sales Unit
FDD LOFD-003029 SFN LT1S000SFN00 Per cell
NB-IoT MLOFD-12120 SFN ML1S000SFN0 Per cell

4 0
NOTE
"Per cell" in the Sales Unit column refers to the physicals cells used to form an SFN cell.
The number of feature licenses and capacity licenses required for an SFN cell depends on the
number of RRUs serving the SFN cell. For example, if an SFN comprises three physical cells
and DL 2x2 MIMO is enabled, three license units are required for each of the following
license control items: Number of cells, SFN, and DL 2x2 MIMO.
If an SFN cell is served by combined RRUs each consisting of two RRUs, one license unit is
required for a combined RRU.

eRAN
5.3.2 Software
Prerequisite Functions
RAT Function Function Reference Description
Name Switch
NB-IoT SFN Cell.MultiRruC 5 SFN (FDD) In LTE in-band

ellMode networking
scenarios, NB-
IoT SFN
requires FDD
SFN.
Mutually Exclusive Functions

Function Function Reference Description
Name Switch
Cell radius None Extended Cell None

greater than Range
100 km
Extended CP Cell.DlCyclic Extended CP The application scenarios are

Prefix different. Extended CP is used in
the extended coverage scenario,
while SFN is used in scenarios
such as indoor coverage, indoor
and outdoor joint coverage,
densely populated urban areas,
and high-speed railways.
Uplink SU- ULSUMIMO MIMO None

MIMO 2LayersSwitc
h option of the
CellAlgoSwitc
h.UlSuMimoA
lgoSwitch
parameter
Downlink 4TxTM9Mu eMIMO None

MU-MIMO in MimoSwitch (FDD)
TM9 option of the
CellAlgoSwitc
h.EmimoSwitc
h parameter

eRAN

Name Switch
Fast beam EmimoFbaSw eMIMO Fast beam alignment does not

alignment itch option of (FDD) take effect in SFN cells.
the
CellAlgoSwitc
h.EmimoSwitc
h parameter
Static Shared None Massive None

Beam MIMO (FDD)
Dynamic None Massive None

Shared Beam MIMO (FDD)
Intelligent MM_INTEL Massive None

beam shaping LIGENT_BE MIMO (FDD)
AM_SHAPIN
G_SW option
of the
SectorSplitGr
oup.SectorSpli
tSwitch
parameter
l Functions related to access management

Name Switch
Detection of ExceedRadius Random None

contention- RaDetectionS Access Control
based random w option of the
access beyond CellAlgoSwitc
cell radius h.RachAlgoS
witch
parameter
Optimization NonContRaO Random None

of non- ptSwitch Access Control
contention- option of the
based random CellAlgoSwitc
access beyond h.RachAlgoS
cell radius witch
parameter

eRAN

Name Switch
Unbalanced PDSCHCfg.T Power Control None

transmit power xPowerOffset
configurations Ant0
between PDSCHCfg.T
channels xPowerOffset
Ant1
PDSCHCfg.T
xPowerOffset
Ant2
PDSCHCfg.T
xPowerOffset
Ant3
l Functions related to multi-RAT coordination

Function Function Switch Reference
Name
CDMA and AvoidCDMAInterfSwitch CDMA and LTE Zero

LTE Zero option of the Bufferzone
Bufferzone CellAlgoSwitch.AvoidInterfSwit
ch parameter
UL Refarming AvoidUtranInterfSwitch option UL Refarming Zero Bufferzone

Zero of the
Bufferzone CellAlgoSwitch.AvoidInterfSwit
ch parameter
l Functions related to RAN services

Name
WTTx MU- Tm9FourLayerPairSwitch WTTx MU-MIMO (FDD)

MIMO option of the
CellAlgoExtSwitch.WttxMuMim
oSwitch parameter

eRAN

Name Switch
CDMA and AvoidCDMAI CDMA and None

LTE Zero nterfSwitch LTE Zero
Bufferzone option of the Bufferzone
CellAlgoSwitc
h.AvoidInterfS
witch
parameter
UMTS and UL_SPECTR UMTS and LTE If the

LTE Spectrum UM_SHARIN Spectrum PDSCHCfg.CellPowerLimit
Sharing G option of Sharing parameter, which specifies the
the maximum transmit power of a
SpectrumClo single channel in an LTE cell, is
ud.SpectrumC set to a value greater than 0, this
loudSwitch function is mutually exclusive
parameter with the SFN function.
GSM and LTE GL_SPCT_C GSM and LTE If the

Spectrum ONCURREN Spectrum PDSCHCfg.CellPowerLimit
Concurrency CY_PH2_SW Concurrency parameter, which specifies the
Phase 2 option of the maximum transmit power of a
SpectrumClo single channel in an LTE cell, is
ud.SpectrumC set to a value greater than 0, this
loudSwitch function is mutually exclusive
parameter with the SFN function.
LTE FDD and LTE_NR_UP LTE and NR None

NR Uplink LINK_SPEC Spectrum
Spectrum TRUM_SHR Sharing
Sharing option of the
SpectrumClo
ud.SpectrumC
loudSwitch
parameter
l Functions related to equipment

Name
Intelligent InterRatCellShut- Energy Conservation and

power-off of down.Forceshutdownswitch Emission Reduction
carriers in the
same coverage
as UMTS
network
l Functions related to networking

eRAN

Name
Out-of-band OutOfBandRelaySwitch option Relay

relay of the
CellAlgoSwitch.RelaySwitch
parameter
In-band relay InBandRelayDeNbSwitch and Relay

InBandRelayReNbSwitch
options of the
parameter
l Functions related to eCoordinator-related features

Name
GSM and LTE GLZeroBufferZoneSwitch GSM and LTE Zero

Zero option of the Bufferzone
Bufferzone CellAlgoSwitch.DynSpectrumSh
areSwitch parameter
GSM and LTE GLDynSpectrumShareSwitch GSM and LTE FDD Dynamic

FDD Dynamic option of the Spectrum Sharing
Spectrum CellAlgoSwitch.DynSpectrumSh
Sharing (LTE areSwitch parameter
FDD)
Adaptive inter- None Adaptive ICIC

cell interference
cancellation
5.3.3 Hardware
Base Station Models

For FDD, the following base stations are compatible with this function:
l 3900 and 5900 series base stations

l DBS3900 LampSite and DBS5900 LampSite
l BTS3912E
l BTS3911E
For NB-IoT, the following base stations are compatible with this function:


eRAN
Boards
l The BBP must be LBBPd or UBBP.
l The BBU must be BBU3910C.
RF Modules
An SFN cell can be served by one or more types of the following RF modules: RRU, RFU,
pRRU, and pRRU group.
RF modules must support the same frequency band.
RRUs can be set to work in 1T1R, 1T2R, 2T2R, 2T4R or 4T4R mode.
In the LampSite solution, SFN requires that 2T2R pRRUs be used.
Cells
The cell bandwidth is 5 MHz, 10 MHz, 15 MHz, or 20 MHz.
5.3.4 Networking
When intra-eNodeB physical cells are combined to form an SFN cell, the difference in their
coverage radiuses cannot exceed 1 km. If the difference exceeds 1 km, then the delay in
receiving signals from different physical cells deviates widely. In this case, if the power
difference between signals received from different physical cells is slight, the downlink
demodulation performance deteriorates.
An SFN cell can consist of physical cells that use different antenna modes. The antenna
configuration of the constituent physical cell that has the largest number of antennas is used as
the antenna configuration of the SFN cell. Possible configurations are listed in Table 5-2. If
four cell-specific reference signal (CRS) ports are configured for an SFN cell that includes 2T
physical cells, the 2T physical cells must be set up on BBPs that support 4T cells. Such BBPs
include LBBPd2, UBBPd4, UBBPd5, UBBPd6, UBBPe2, and UBBPe4.
Table 5-2 Antenna mode mapping between SFN cells and physical cells
Antenna Number of CRS Ports Antenna Mode of Physical

Mode of SFN Cells
Cells
1T1R CRS_PORT_1 1T1R
1T2R CRS_PORT_1 1T1R and 1T2R
2T2R CRS_PORT_1 or CRS_PORT_2 1T1R, 1T2R, and 2T2R
2T4R CRS_PORT_1 or CRS_PORT_2 1T1R, 1T2R, 2T2R, and 2T4R
4T4R CRS_PORT_1 or CRS_PORT_2 1T1R, 2T2R, 2T4R, and 4T4R
4T4R CRS_PORT_4 2T2R, 2T4R, and 4T4R

eRAN
5.3.5 Others
None
5.4 Operation and Maintenance
5.4.1 Data Configuration
5.4.1.1 Data Preparation

The parameters used for function activation are listed in the following tables. This section
does not describe parameters related to cell establishment. For details about the initial cell
configuration, see the base station initial configuration guides.
An SFN cell requires two to six sets of sector equipment or one to six sector equipment
groups. If RRUs are used, configure sector equipment. If pRRU groups are used, configure
sector equipment groups.
Table 5-3 Common parameters used for activation

Parameter Parameter ID Setting Notes
Name
Local Cell ID Cell.LocalCellI None

d
Flag of Multi- Cell.MultiRruC BOOLEAN_TRUE

RRU Cell ellFlag
Mode of Multi- Cell.MultiRruC l To combine RRUs or pRRUs to serve an SFN

RRU Cell ellMode cell, set this parameter to SFN.
l To combine pRRU groups to serve an SFN cell,
set this parameter to MPRU_AGGREGATION.
Physical Cell Cell.SectorEqm Set this parameter to a value that is equal to the
Number of SFN Num number of physical cells to be combined into an SFN
Cell cell.
Cell Cell.TxRxMod l If all RRUs work in 1T1R mode, set this

transmission e parameter to 1T1R.
and reception l If all RRUs work in 1T2R mode or both 1T1R
mode RRUs and 1T2R RRUs exist, set this parameter to
1T2R.
l If all RRUs work in 2T2R mode, set this
parameter to 2T2R.
l If all RRUs work in 2T4R mode or both 2T4R
RRUs and 2T2R RRUs exist, set this parameter to
2T4R.
l If all RRUs work in 4T4R mode or 4T4R RRUs
are included, set this parameter to 4T4R.

eRAN

Name
CRS Port Cell.CrsPortNu l Set this parameter to CRS_PORT_1 if there is

Number m one TX antenna for a logical cell.
l Set this parameter to CRS_PORT_2 if there are
two TX antennas for a logical cell.
l Set this parameter to CRS_PORT_2 or
CRS_PORT_4 if the logical cell has four TX
antennas and each physical cell also has four
antennas.
l When the number of TX antennas for a logical
cell is 4:
– It is recommended that this parameter be set to
CRS_PORT_2 if the logical cell includes
macro physical cells with two antennas.
– It is recommended that this parameter be set to
CRS_PORT_4 if the number of antennas is
two only for the micro physical cells of the
logical cell.
CRS Antenna Cell.CrsPortM Set this parameter to its recommended value.

Port Mapping ap
SFN UL CellAlgoSwitc JOINT

Scheduling h.SfnUlSchSwi
Switch tch
SFN DL CellAlgoSwitc JOINT

Scheduling h.SfnDlSchSwi
Switch tch
This following table describes the parameters that must also be set if RRUs are combined to
serve an FDD SFN cell.
Table 5-4 Parameters that must also be set for function activation if RRUs are combined to
serve an FDD SFN cell
Name
Local cell ID eUCellSectorE None

qm.LocalCellId
Sector eUCellSectorE Set this parameter to the sector equipment ID

equipment ID qm.SectorEqm specified when the sector equipment is added.
Id

eRAN

Name
Reference eUCellSectorE Set this parameter if different power needs to be set

signal power qm.ReferenceS for different pieces of sector equipment.
ignalPwr
Baseband eUCellSectorE None

equipment ID qm.BaseBandE
qmId
This following table describes the parameters that must also be set if pRRU groups are
combined to serve an FDD SFN cell.
Table 5-5 Parameters that must also be set for function activation if pRRU groups are
combined to serve an FDD SFN cell
Name
Create Default SECTOR.CRE l For an SFN cell in 1T1R or 2T2R mode, you are
Sector ATESECTORE advised to set the Create Default Sector
Equipment QM Equipment parameter to TRUE.
l For an SFN cell in 2T4R or 4T4R mode, if the
TX/RX modes of all RRUs are 2T4R or 4T4R,
you are advised to set the Create Default Sector
Equipment parameter to TRUE for the sectors of
all the RRUs; if the TX/RX mode of an RRU is
2T2R, set the Create Default Sector Equipment
parameter to FALSE for the sector of this RRU.
Local cell ID EuSectorEqm None

Group.LocalCe
llId
Sector EuSectorEqm None

Equipment Group.SectorE
Group ID qmGroupId
Baseband EuSectorEqm None

equipment ID Group.BaseBa
ndEqmId
Reference EuSectorEqm Set this parameter if different power needs to be set

signal power Group.Referen for different sector equipment groups.
ceSignalPwr
serve an NB-IoT SFN cell.

eRAN
serve an NB-IoT SFN cell
Name
Local Cell ID EuPrbSectorE None

qm.LocalCellId
PRB ID EuPrbSectorE None

qm.PrbId
Sector EuPrbSectorE None

Equipment ID qm.SectorEqm
Id
Reference EuPrbSectorE Set this parameter if different power needs to be set

Signal Power qm.ReferenceS for different pieces of sector equipment used by
ignalPwr PRBs.
combined to serve an NB-IoT SFN cell.
combined to serve an NB-IoT SFN cell
Name
Local Cell ID EuPrbSectorE None

qmGroup.Loca
lCellId
PRB ID EuPrbSectorE None

qmGroup.PrbI
d
Sector EuPrbSectorE None

Equipment qmGroup.Sect
Group ID orEqmGroupId
Reference EuPrbSectorE Set this parameter if different power needs to be set

Signal Power qmGroup.Refe for different sector equipment groups used by PRBs.
renceSignalPw
r
Local Cell ID PrbSectorEqm None

GrpItem.Local
CellId
Sector PrbSectorEqm None

Equipment ID GrpItem.Secto
rEqmId

eRAN

Name
PRB ID PrbSectorEqm None

GrpItem.PrbId
Sector PrbSectorEqm None

Equipment GrpItem.Secto
Group ID rEqmGroupId
The parameters used for function optimization are listed in the following tables.
The following table describes the parameters that need to be set in the EuCellPriBBEqm MO
to specify the primary baseband equipment information.

Name
Local cell ID EuCellPriBBE None

qm.LocalCellId
Primary EuCellPriBBE None

Baseband qm.PriBaseBa
Equipment ID ndEqmId
The following table describes the parameters that need to be set in the PDSCHCFG MO to
specify the RS power.

Name
Local cell ID PDSCHCfg.Lo This parameter must be set if the

calCellId eUCellSectorEqm.ReferenceSignalPwr or
EuSectorEqmGroup.ReferenceSignalPwr
parameter is set to 32767.
Reference PDSCHCfg.Re This parameter must be set if the

signal power ferenceSignalP eUCellSectorEqm.ReferenceSignalPwr or
wr EuSectorEqmGroup.ReferenceSignalPwr
The following table describes the parameters that need to be set in the SRSCfg MO to specify
the SRS configuration information.

eRAN

Name
SRS SRSCfg.SrsCfg BOOLEAN_TRUE

Configuration Ind
Indicator
FDD SRS SRSCfg.FddSr DEFAULTMODE

Configuration sCfgMode
Mode
The following table describes the parameter that needs to be set in the CellRacThd MO to
specify the cell capacity mode.

Name
Cell Capacity CellRacThd.Ce Set this parameter based on the number of UEs in an
Mode llCapacityMode SFN cell.
If this parameter is set to NORMALCAPACITY or
LARGECAPACITY for a cell with a bandwidth of
10 MHz or higher that serves no more than 400 UEs,
or with a bandwidth of 5 MHz that serves no more
than 200 UEs, the user-perceived uplink and
downlink throughput will decrease by about 5%
because the SRS or PUCCH transmission period is
prolonged.
The following table describes the parameters that need to be set in the ENodeBAlgoSwitch
MO to set the common handover optimization switch.
Parameter Parameter ID Option Setting Notes

Name
Handover ENodeBAlgoS BasedSriGapO It is recommended that this option

Common witch.HoCom ptSwitch be selected for UEs in non-DRX
Optimized mOptSwitch mode in SFN cells to address the
Switch impact of gap configuration on
scheduling requests (SRs).
NOTE
If this option is selected, the
transmission of scheduling request
indicators (SRIs) is considered during
measurement gap configuration for
UEs that are not in DRX mode, and
the probability of service drops
decreases. If this option is deselected,
the transmission of SRIs is not
considered and service drops occur.

eRAN

Name
ENodeBAlgoS DrxBasedSriG It is recommended that this option

witch.HoCom apOptSwitch be selected for UEs in DRX mode
mOptSwitch in SFN cells to address the impact
of gap configuration on SRs.
NOTE
If this option is selected, the
transmission of SRIs is considered
during measurement gap
configuration for UEs in DRX mode,
and the probability of service drops
decreases. If this option is deselected,
the transmission of SRIs is not
considered and service drops occur.
The following table describes the parameters that need to be set in the CellAlgoSwitch MO to
set the SFN algorithm switch, PUCCH algorithm switch, uplink joint reception antenna
number combination switch, and SFN uplink CoMP switch.

Name
SFN Algorithm CellAlgoSwitc SfnTarRruAdp For FDD, it is recommended that

Switch h.SfnAlgoSwit tSelSwitch this option be selected. This option
ch and the SfnTarRruSelEnhSwitch
option cannot be both selected.
For NB-IoT, this option must be
deselected.
PUCCH CellAlgoSwitc PucchMeasOp If uplink throughput is limited,

algorithm switch h.PucchAlgoS tSwitch you are advised to select this
witch option.
When this option is selected, the
SRSCfg.FddSrsCfgMode
parameter cannot be set to
DEFAULTMODE and the
Cell.HighSpeedFlag parameter
can only be set to LOW_SPEED.
When coverage is limited, PUCCH
RSRP measurements are not very
accurate. The working RRUs
determined based on PUCCH
measurements are inconsistent
with the working RRUs
determined based on DMRS
measurements. As a result, the
percentage of jointly scheduled
UEs increases and the cell load
also increases.

eRAN

Name
UL JR Antenna CellAlgoSwitc Ul1R1RJRSwi It is recommended that this option

Number h.UlJRAntNu tch be selected when there is 1R
Combined mCombSw antenna configuration in the SFN
Switch cell.
CellAlgoSwitc Ul1R2RJRSwi It is recommended that this option

h.UlJRAntNu tch be selected when there are both 1R
mCombSw and 2R antenna configurations in
the SFN cell.
CellAlgoSwitc Ul1R4RJRSwi Set this option to its recommended

h.UlJRAntNu tch value.
mCombSw

h.UlJRAntNu tch value.
mCombSw
SFN Uplink CellAlgoSwitc IntraBaseBand Set this option to its recommended

Comp Switch h.SfnUplinkC Switch value.
ompSwitch
CellAlgoSwitc InterBaseBand Set this option to its recommended

h.SfnUplinkC Switch value.
ompSwitch
CellAlgoSwitc SfnUplinkCom Set this option to its recommended

h.SfnUplinkC p3CellSwitch value.
ompSwitch
The following table describes the parameter that needs to be set in the CellUlCompAlgo MO
to specify the threshold used to determine UE selection for UL CoMP in an SFN cell.

Name
Sfn UL CoMP CellUlCompAl Set this parameter to its recommended value.

Threshold go.SfnUlComp This parameter must be set if uplink joint reception is
Thd enabled in the SFN cell.
5.4.1.2 Using MML Commands
Activation Command Examples

To ensure optimal resource usage, the activation of an SFN cell may deactivate and reactivate
some cells served by the eNodeB.
Configuring an SFN Cell for a Newly Deployed eNodeB

eRAN
Scenario 1: Configuring an FDD SFN cell using RRUs or pRRUs

The following command examples assume that an SFN cell is served by three RRUs and the
TX/RX mode of the physical cells is 2T2R. The parameter values are for reference only and
should be adjusted as required.
Adding sectors
ADD
SECTOR:SECTORID=0,ANTNUM=2,ANT1CN=0,ANT1SRN=60,ANT1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN
=60,ANT2SN=0,ANT2N=R0B,CREATESECTOREQM=TRUE,SECTOREQMID=0;
ADD
ADD
Adding an SFN cell

ADD CELL: LocalCellId=0, CellName="FDD_SFN", NBCELLFLAG=FALSE, FreqBand=7,
UlEarfcnCfgInd=NOT_CFG, DlEarfcn=3000, UlBandWidth=CELL_BW_N100,
DlBandWidth=CELL_BW_N100, CellId=100, PhyCellId=100, FddTddInd=CELL_FDD,
RootSequenceIdx=0, CustomizedBandWidthCfgInd=NOT_CFG,
EmergencyAreaIdCfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG,
MultiRruCellFlag=BOOLEAN_TRUE, MultiRruCellMode=SFN, SectorEqmNum=3,
TxRxMode=2T2R;
Binding sector equipment to the cell, with the local cell ID and sector equipment ID set to the
same values as those set in preceding commands. The reference signal (RS) power of each
physical cell must be set if the physical cells of an SFN cell are served by RF modules with
different power.
ADD EUCELLSECTOREQM: LOCALCELLID=0,SECTOREQMID=0;
Setting SFN uplink and downlink scheduling switches

MOD CELLALGOSWITCH: LOCALCELLID=0,SFNULSCHSWITCH=JOINT,SFNDLSCHSWITCH=JOINT;
Activating the cell

ACT CELL: LocalCellId=0;
Scenario 2: Configuring an SFN cell using pRRU groups

The following assumes that an SFN cell is served by two pRRU groups, each with four
pRRUs. The parameter values serve as examples only and should be adjusted as required.
Adding sectors. Set SECTOR.CREATESECTOREQM to TRUE to create sector equipment.
ADD SECTOR: SECTORID=10, ANTNUM=2, ANT1CN=0, ANT1SRN=71, ANT1SN=1, ANT1N=R0A,
ANT2CN=0, ANT2SRN=71, ANT2SN=1, ANT2N=R0B, CREATESECTOREQM=TRUE, SECTOREQMID=10;

eRAN
Adding a cell
ADD CELL: LocalCellId=0, CellName="cell0", NBCELLFLAG=FALSE, FreqBand=7,
MultiRruCellFlag=BOOLEAN_TRUE, MultiRruCellMode=MPRU_AGGREGATION, TxRxMode=2T2R;
Adding the cell operator

ADD CELLOP: LocalCellId=0, TrackingAreaId=0;
Adding sector equipment groups 0 and 1. The RS power of each physical cell must be set if
the physical cells of an SFN cell are served by RF modules with different power.
ADD EUSECTOREQMGROUP: LocalCellId=0, SectorEqmGroupId=0;
ADD EUSECTOREQMGROUP: LocalCellId=0, SectorEqmGroupId=1;
Adding four sets of sector equipment to each group (The four sets of sector equipment are RF
combined to serve a physical cell)
ADD EUSECTOREQMID2GROUP: LocalCellId=0, SectorEqmGroupId=0, SectorEqmId=10;

Activating the cell

Scenario 3: Configuring an NB-IoT SFN cell using RRUs

The following command examples assume that an SFN cell is served by three RRUs and the
TX/RX mode of the physical cells is 2T2R. The parameter values are for reference only and
should be adjusted as required.
Adding sectors
ADD
ADD
ADD
Adding an SFN cell

ADD CELL: LocalCellId=0, CellName="NBIOT_SFN", NbCellFlag=TRUE,
CoverageLevelType=COVERAGE_LEVEL_0-1&COVERAGE_LEVEL_1-1&COVERAGE_LEVEL_2-1,
CellId=0, PhyCellId=0, FddTddInd=CELL_FDD, EuCellStandbyMode=ACTIVE,
CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_TRUE, MultiRruCellMode=SFN,
SectorEqmNum=3, TxRxMode=2T2R;
Adding a PRB (assuming that an LTE cell with the local cell ID 1 has been configured in the
in-band deployment scenario and is working normally)

eRAN
ADD PRB: LocalCellId=0, PrbId=0, DeployMode=IN_BAND, FreqBand=8,

UlEarfcnCfgInd=CFG, UlEarfcn=21511, UlFreqOffset=NEG_2, DlEarfcn=3518,
DlFreqOffset=POS_0, LteCellId=1;

Adding sector equipment for the PRB

ADD EUPRBSECTOREQM:LOCALCELLID=0, PrbId=0, SECTOREQMID=0;

Activating the cell

Scenario 4: Configuring an NB-IoT SFN cell using pRRU groups

The following description uses the combination of two pRRUs into a pRRU group for SFN
cell deployment as an example. The parameter settings in the following commands are used
for reference only. Set the parameters based on network requirements.
Adding sectors
ADD SECTOR: SECTORID=61, SECNAME="CPRI0_RHUB1_pRRU1", ANTNUM=6, ANT1CN=0,
ANT1SRN=61, ANT1SN=0, ANT1N=R0A, ANT2CN=0, ANT2SRN=61, ANT2SN=0, ANT2N=R0B,
ANT3CN=0, ANT3SRN=61, ANT3SN=0, ANT3N=R0C, ANT4CN=0, ANT4SRN=61, ANT4SN=0,
ANT4N=R0D, ANT5CN=0, ANT5SRN=61, ANT5SN=0, ANT5N=R0E, ANT6CN=0, ANT6SRN=61,
ANT6SN=0, ANT6N=R0F, CREATESECTOREQM=TRUE, SECTOREQMID=61;
ADD SECTOR: SECTORID=71, SECNAME="CPRI0_RHUB2_pRRU1", ANTNUM=6, ANT1CN=0,
ANT1SRN=71, ANT1SN=0, ANT1N=R0A, ANT2CN=0, ANT2SRN=71, ANT2SN=0, ANT2N=R0B,
ANT3CN=0, ANT3SRN=71, ANT3SN=0, ANT3N=R0C, ANT4CN=0, ANT4SRN=71, ANT4SN=0,
ANT4N=R0D, ANT5CN=0, ANT5SRN=71, ANT5SN=0, ANT5N=R0E, ANT6CN=0, ANT6SRN=71,
ANT6SN=0, ANT6N=R0F, CREATESECTOREQM=TRUE, SECTOREQMID=71;
Adding an SFN cell

ADD CELL: LocalCellId=0, CellName="NB-IOT", NbCellFlag=TRUE,
CoverageLevelType=COVERAGE_LEVEL_0-1&COVERAGE_LEVEL_1-1&COVERAGE_LEVEL_2-1,
CellId=0, PhyCellId=213, FddTddInd=CELL_FDD, EuCellStandbyMode=ACTIVE,
CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_TRUE,
MultiRruCellMode=MPRU_AGGREGATION, TxRxMode=2T2R;
Adding a PRB
ADD PRB: LocalCellId=0, PrbId=0, DeployMode=IN_BAND, FreqBand=8,
UlEarfcnCfgInd=CFG, UlEarfcn=21689, UlFreqOffset=POS_2, DlEarfcn=3545,
DlFreqOffset=POS_0, LteCellId=1, AnchorCarrierFlag=TRUE;
Adding a PRB sector equipment group and PRB sector equipment group objects
ADD EUPRBSECTOREQMGROUP: LocalCellId=0, PrbId=0, SectorEqmGroupId=0;
ADD PRBSECTOREQMGRPITEM: LocalCellId=0, SectorEqmId=61, PrbId=0,
SectorEqmGroupId=0;
ADD PRBSECTOREQMGRPITEM: LocalCellId=0, SectorEqmId=71, PrbId=0,
SectorEqmGroupId=0;
Adding the cell operator and setting cell-specific reference signal power
ADD CELLOP: LocalCellId=0, TrackingAreaId=0, MMECfgNum=CELL_MME_CFG_NUM_0;
MOD PDSCHCFG: LocalCellId=0, ReferenceSignalPwr=-21;
Activating the cell

eRAN
Configuring an SFN Cell for an Existing eNodeB

Radio parameters such as PCIs, RACH root sequences, and neighbor relationships have been
replanned to adapt to the new cell topology.
In this example:
l There are three physical cells: 0, 1, and 2.
l Cells 0, 1, and 2 use sector equipment 0, 1, and 2, respectively.
l The cell ID of the new SFN cell is the same as that of cell 0.
l The cell capacity mode (specified by the CellRacThd.CellCapacityMode parameter) of
cell 0 remains unchanged after the SFN cell reconstruction. To use a different cell
capacity mode, change the value of the CellRacThd.CellCapacityMode parameter.
Deactivating cells 0, 1, and 2
DEA CELL: LocalCellId=0;
Changing the parameter settings for cell 0

MOD CELL: LocalCellId=0, MultiRruCellFlag=BOOLEAN_TRUE, MultiRruCellMode=SFN,
SectorEqmNum=3;
Removing sector equipment 1 and 2 from cells 1 and 2, respectively

RMV EUCELLSECTOREQM: LocalCellId=1, SectorEqmId=1;
Binding sector equipment 1 and 2 to cell 0

ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=1;
Activating the SFN cell

Optimization Command Examples

Optimizing the SFN Cell Configuration for a Newly Deployed eNodeB
Modifying the RS power for the PDSCH
Changing the SRS configuration indicator and the SRS configuration mode
MOD SRSCFG: LocalCellId=10, SrsCfgInd=BOOLEAN_TRUE,FDDSrsCfgMode= DEFAULTMODE;
Specifying a cell capacity mode

MOD CELLRACTHD: LocalCellId=10, CellCapacityMode=SMALLCAPACITY;
Setting the uplink joint reception switch and the antenna number combination switch for
uplink joint reception
MOD CELLALGOSWITCH: LocalCellId=0, SfnUplinkCompSwitch=IntraBaseBandSwitch-1,
UlJRAntNumCombSw=Ul1R2RJRSwitch-1;
Setting the admission threshold of UL CoMP in SFN cell

eRAN
MOD CELLULCOMPALGO: LocalCellId=0, SfnUlCompThd=-5;
Optimizing the SFN Cell Configuration for an Existing eNodeB
Changing the SRS configuration indicator and the SRS configuration mode
MOD SRSCFG: LocalCellId=0, SrsCfgInd=BOOLEAN_TRUE, FDDSrsCfgMode=DEFAULTMODE;
Changing the PCI and RACH root sequence of cell 0 by running MOD CELL if these
parameters are replanned
MOD CELL:LOCALCELLID=0,PHYCELLID=0,ROOTSEQUENCEIDX=0;
Removing the original neighbor relationships, and adding newly planned neighbor
relationships
RMV EUTRANINTRAFREQNCELL:LOCALCELLID=1,MCC="450",MNC="06",ENODEBID=100,CELLID=2;
ADD EUTRANINTRAFREQNCELL:LOCALCELLID=1,MCC="450",MNC="06",ENODEBID=100,CELLID=3;
Specifying a cell capacity mode

MOD CELLRACTHD: LocalCellId=0, CellCapacityMode=SMALLCAPACITY;

Deactivation Command Examples

Deactivating an SFN cell
5.4.1.3 Using the CME

For detailed operations for FDD, see CME-based Feature Configuration.
SFN supports simplified configuration on the CME. The relevant steps are as follows:
Step 1 After creating a planned data area, choose SFN Combination from the main menu on the
CME.
Step 2 Specify cells to be combined into an SFN cell in the following sheet of the summary data file,
and then import the file into the CME.

eRAN
NOTE
l Only one cell to be combined must be specified as the primary cell of an SFN cell.
l A cell to be combined must be unique in the sheet.
l A cell to be combined can be an SFN cell or a common cell, but must have been configured.
l If an SFN cell has multiple eNodeB IDs (for example, when the cells to be combined include an
inter-eNodeB SFN cell), Mode of Multi-RRU Cell can only be set to SFN.
Step 3 Choose Export Incremental Scripts from the main menu on the CME to export the
incremental scripts in the planned area and then activate the scripts.
Step 4 Deliver configuration data and activate the SFN cell.
----End
NOTE
In the simplified configuration on the CME, both SFN UL Scheduling Switch and SFN DL Scheduling
Switch are set to JOINT by default.
For NB-IoT:
l Fast batch activation

This feature can be batch activated using the Feature Operation and Maintenance
function of the CME. For detailed operations, see the following section in the CME
product documentation or online help: CME Management > CME Guidelines >
Enhanced Feature Management > Feature Operation and Maintenance.
l Single/batch configuration
This feature can be activated for a single eNodeB or a batch of eNodeBs on the CME.
For detailed operations, see CME-based Feature Configuration.
5.4.2 Activation Verification

When SFN is used in high-speed railway scenarios, the SINR gain may be negative at the
boundaries between physical cells due to the frequency offset. If the SINR gain is negative,
the current SINR is different from the actual SINR used for demodulation. It is recommended
that the CQIs before and after the SFN application be compared to observe the SFN gain.
Performance Monitoring
Check the following counters on the U2020 client.
Table 5-8 Counters related to the SFN function

Counter ID Counter Name
1526733200 L.ULSFNJR.User.Avg
1526733201 L.ChMeas.PRB.UL.ULSFNJR.Used.Avg
1526733202 L.CellSectorEQUIP.ULSFNJR.User.Avg
1526733203 L.CellSectorEQUIP.ChMeas.PRB.UL.UL
SFNJR.Used.Avg
1526743759 L.Thrp.bits.DL.BorderUE.JointTransmit

eRAN
1526743762 L.Thrp.bits.DL.LastTTI.BorderUE.Joint
Transmit
1526743763 L.Thrp.Time.DL.RmvLastTTI.BorderUE
.JointTransmit
Check the monitoring results:

Uplink joint reception has taken effect if the value of any of the following counters is not
zero:
l L.ULSFNJR.User.Avg
l L.ChMeas.PRB.UL.ULSFNJR.Used.Avg
l L.CellSectorEQUIP.ULSFNJR.User.Avg
l L.CellSectorEQUIP.ChMeas.PRB.UL.ULSFNJR.Used.Avg
Using MML Commands

Run the DSP CELL command. If the command output meets the following conditions, the
SFN cell has been activated:
l The value of Cell instance state is Normal.
l The value of Cell topology type is SFN Type or MPRU Aggregation Type.
l The values of all RRUs' Work Status are Normal.
Cell-Level Performance Monitoring

Users can perform packet injection in the cell until the cell throughput reaches the maximum
and monitor the RB usage on the U2020 to check whether the SFN function has been
activated.
If the number of RBs of an SFN cell is a multiple (an integer greater than 1) of the number of
RBs in a single physical cell, the SFN function has taken effect. For example, in an SFN cell
consisting of two physical cells, if the number of RBs is 100 (two times the number of RBs in
a single physical cell) when the cell bandwidth is 10 MHz, the SFN function has taken effect.
UE-Level Performance Monitoring

UE-Level Performance Monitoring in an FDD SFN Cell
In an area covered by an FDD SFN cell, move a UE from the cell center (where the signal
strength is –75 dBm) of a physical cell to an area where multiple physical cells overlap, and
have the UE perform uplink and downlink services. During this period, view the following
results to check whether the SFN function for FDD has been activated:
l Uplink RSRP of each RRU's SRS (dBm)
l Uplink SINR of the UE (dB)
l Uplink and downlink UE scheduling attributes
l SINR of each RRU's DMRS (dB)

eRAN
Based on the SFN monitoring results, perform the following analysis:

l Check the RRUs in the working RRU list. If the list contains all RRUs, SFN has been
activated.
l Based on the value of UL RRU Flag, determine whether uplink joint reception has taken
effect.
NOTE
If a physical cell is faulty, the eNodeB cannot perform joint reception for UEs in the cell. However, this
information is not always updated immediately on the U2020. There is a delay of approximately 2s in
updating the information displayed on the GUI.
UE-Level Performance Monitoring in an NB-IoT SFN Cell

In an area covered by an NB-IoT SFN cell, move a UE from the cell center (where the signal
strength is –75 dBm) of a physical cell to an area where multiple physical cells overlap, and
have the UE perform uplink and downlink services. You can then observe the selection of
uplink target RRUs in the NB-IoT SFN cell and the SINR and RSRP measurement results by
checking the tracing results of the following items:
l RSRP of uplink DMRS (dBm)
5.4.3 Network Monitoring

SFN can be monitored by starting SFN detection monitoring tasks and measuring counters.

eRAN
Starting SFN Detection Monitoring Tasks

On the U2020 client, start SFN detection monitoring tasks to check the RRU usage in SFN
scenarios.
On the U2020 client, view the monitoring results of the objects listed in Table 5-9.
Table 5-9 Example of SFN detection monitoring results

Monitoring Object Definition
UL User Mode In the uplink, UEs can be classified into jointly

scheduled UEs and independently scheduled UEs.
DL User Mode In the downlink, UEs can be classified into jointly

Physical Cell Identifier This item indicates the physical cell ID of an SFN
cell.
UL RRU eNodeB ID This item indicates the eNodeB ID of an RRU used

for uplink transmission.
UL Sector Equipment or This item indicates the sector equipment ID or sector

Equipment Group Flag equipment group ID.
UL RRU Flag This item indicates the attribute of an uplink RRU.

Uplink RRUs can be classified into:
l Target RRU
l Work RRU
l Other RRU
l Work RRU (Joint Reception)
l Target RRU (Joint Reception)
l Other RRU (Joint Reception)
Measuring Counters
For details about the counters to be monitored, see 24 Counters. The
L.CellSectorEQUIP.SFN.UL.PRB.Used.Avg counter is used to measure the average number
of PRBs occupied by the PUSCH, PUCCH, and PRACH for all UEs served by a set of sector
equipment in an SFN cell.
The target RRU may change for UEs in an SFN cell. As a result,
L.CellSectorEQUIPGroup.SFN.RRC.ConnReq.Att and
L.CellSectorEQUIPGroup.SFN.RRC.ConnReq.Succ may be counted on different sets of
sector equipment. Therefore, the value of
L.CellSectorEQUIPGroup.SFN.RRC.ConnReq.Succ may be greater than the value of
L.CellSectorEQUIPGroup.SFN.RRC.ConnReq.Att for a particular set of sector
equipment. However, the values of these counters for the entire SFN cell are not affected.

eRAN
SFN Feature Parameter Description 6 SFN (TDD)
6 SFN (TDD)
6.1 Principles
The SFN function enables multiple RRUs to be combined to form a single SFN cell. This
function requires that the percentage of UEs in the overlapping areas between the physical
cells served by the RRUs exceed 20%. To combine RRUs or pRRUs to serve an SFN cell, set
the Cell.MultiRruCellMode parameter to SFN. To combine pRRU groups to serve an SFN
cell, set this parameter to MPRU_AGGREGATION.
In the uplink, either independent or joint reception is used. For details on uplink independent
reception and joint reception, see 4.7 Uplink Independent Reception (TDD) and 4.8 Uplink
Joint Reception (TDD), respectively. In the downlink, multi-RRU joint transmission is used.
For details, see 4.4 Downlink Joint Transmission.
Joint scheduling is used in SFN cells. Joint scheduling is enabled in the uplink when the
CellAlgoSwitch.SfnUlSchSwitch parameter is set to JOINT and enabled in the downlink
when the CellAlgoSwitch.SfnDlSchSwitch parameter is set to JOINT. For details on joint
scheduling, see 4.1 Independent Scheduling and Joint Scheduling.
This section describes intra-BBP SFN. The eNodeB uses this function to combine physical
cells served by the same BBP into an SFN cell.
6.2.1 Benefits
The SFN function provides the following benefits:
l Reduced interference and increased SINR in the overlapping areas between physical
cells, and therefore improved user experience in these areas. The lower the SINR before
the combination, the greater the gains after the combination.
l Extended cell coverage and fewer UE handovers between physical cells.
The average throughput for a single UE increases by about 53% in the downlink and by about
59% at the cell edge in the downlink when three RRUs serve an SFN cell in a typical dense
urban area and the load rate reaches 100%.

eRAN
l The average PDCCH SINR and PDSCH SINR increase by 2 dB to 3 dB when three
RRUs serve a single SFN cell in a typical dense urban area.
l The average PDCCH SINR and PDSCH SINR increase by 5 dB to 6 dB when seven
RRUs serve a single SFN cell in a typical dense urban area.
The specific gains depend on the inter-RRU distance, UE distribution, and traffic model.
In typical indoor coverage scenarios, SFN networking delivers higher average cell throughput
than single-RRU networking or multi-RRU common networking and the average PDCCH
SINR and PDSCH SINR increase significantly.
total Downlink Resource Block Utilizing Rate of the common cells before the combination
is less than 60%, User Downlink Average Throughput increases by 10% to 50% after the
combination. When the network load rate is 100%, the average PDCCH and PDSCH SINRs
increase by 10 dB to 20 dB. The specific gains depend on the deployment density of pRRUs
before the combination, number of pRRUs used to form the SFN cell, UE distribution, and
traffic model.
When the supported functions and environment remain the same and the condition for using
the SFN function is met, the expected KPI changes in SFN cells compared with common cells
are listed in the following table.
Table 6-1 Expected KPI changes in SFN cells compared with common cells
KPI Expected Change
Cell Downlink Average Throughput No decrease
Cell Uplink Average Throughput No decrease
User Downlink Average Throughput Increase
User Uplink Average Throughput Increase

Rate
Service Drop Rate No increase
Uplink Resource Block Utilizing Rate Increase
Downlink Resource Block Utilizing Rate Increase
l The values of the following indicators may increase significantly:

– Cell Uplink Average Throughput, Cell Downlink Average Throughput, User
Uplink Average Throughput, and User Downlink Average Throughput
If the traffic volume and data transmission duration of an SFN cell have a different
change curve from the total traffic volume and total data transmission duration of
all cells combined into the SFN cell, Cell Uplink Average Throughput and Cell
Downlink Average Throughput may change significantly after the combination.

eRAN
For example, the traffic volume of an SFN cell may be two times the total traffic
volume of the physical cells before the combination. At the same time, the data
transmission duration of the SFN cell could be 1.5 times that of the physical cells
before the combination. In this instance, Cell Uplink Average Throughput and
Cell Downlink Average Throughput would increase after the combination.
Similarly, the values of User Uplink Average Throughput and User Downlink
Average Throughput also increase significantly.
– L.ResOpt.CCELimit.PRB.DL
The value of this counter increases because the PDCCH resources of the SFN cell
become fewer than those of common cells.
NOTE
All counters for calculating these indicators are measured on the basis of a single SFN cell.
These gains are obtained on the assumption that UEs are evenly distributed in the SFN cell and services
are initiated at a random time.
6.2.2 Impacts
Network Impacts
Enabling the SFN feature decreases the overall system capacity to some extent.
After common cells are combined into an SFN cell, if the load of the SFN cell is heavier than
that of the common cells used to form it, the load of the neighboring common cells will
increase and the SINR will decrease slightly.
If an SFN cell is comprised of physical cells whose coverage is limited, uplink path loss and
downlink path loss are inconsistent in the SFN cell. As a result, the access performance
deteriorates for CEUs, affecting the counters related to cell access.
In a typical dense urban area where the network load rate is 100%, Cell Downlink Average
Throughput of a single SFN cell served by three RRUs decreases to approximately 51% of
that of three single-RRU common cells. The specific impacts depend on the inter-RRU
distance, UE distribution, and traffic model.
total Downlink Resource Block Utilizing Rate of the common cells used to form the SFN
cell is less than 60%, the gain in User Downlink Average Throughput decreases with the
increase of the Downlink Resource Block Utilizing Rate, or a negative gain can be
produced. The specific impacts depend on the deployment density of pRRUs before the
combination, number of pRRUs used to form the SFN cell, UE distribution, and traffic model.
NOTE
The preceding impacts are measured based on the assumption that UEs are evenly distributed in the SFN
cell and that services are initiated at a random time.
Function Impacts

eRAN

Name Switch
Uplink 2x4 UlVmimoSwit MIMO When the options of the

MU-MIMO ch option of CellAlgoSwitch.SfnUplinkCom
the pSwitch parameter are selected
CellAlgoSwitc for an SFN cell with uplink 2x4
h.UlSchSwitc MU-MIMO enabled, uplink joint
h parameter reception takes effect in
precedence over MU-MIMO.
Uplink 2x8 UlVmimoSwit MIMO When the options of the

MU-MIMO ch option of CellAlgoSwitch.SfnUplinkCom
the pSwitch parameter are selected
Uplink 4x8 HighOrderV MIMO When the options of the

MU-MIMO MIMOSwitch CellAlgoSwitch.SfnUplinkCom
option of the pSwitch parameter are selected
Single-stream CellAlgoSwitc Beamforming If this function is enabled and

beamforming h.BfAlgoSwitc (TDD) there are jointly scheduled UEs
h in an SFN cell, the phases of the
received signals at the UEs are
random. This compromises the
gains brought by this function,
but system gains are still
increased.
Downlink 2- TM9Switch Beamforming If the

layer MIMO option of the (TDD) CellCsiRsParaCfg.CsiRsPortN
based on TM9 CellAlgoSwitc um parameter is set to
h.EnhMIMOS CSI_RS_PORT_4 or
witch CSI_RS_PORT_8 for an SFN
parameter cell, independently or jointly
scheduled TM9 UEs can
perform CSI measurement for
CQI, PMI, and RI feedback
based on the CSI-RSs sent by
the SFN cell, increasing the
average cell throughput and
improving user experience.

eRAN

Name Switch
Downlink 4- l TM9Switc Beamforming If the

layer MIMO h option of (TDD) CellCsiRsParaCfg.CsiRsPortN
based on TM9 the um parameter is set to
CellAlgoS CSI_RS_PORT_4 or
witch.Enh CSI_RS_PORT_8 for an SFN
MIMOSwit cell, independently or jointly
ch scheduled TM9 UEs can
parameter perform CSI measurement for
l CellDlsch CQI, PMI, and RI feedback
Algo.Max based on the CSI-RSs sent by
MimoRank the SFN cell, increasing the
Para average cell throughput and
improving user experience.
Turbo receiver CellAlgoSwitc Turbo ComCoverUlCompSwitch

h.TurboReceiv Receiver (under the
erSwitch CellAlgoSwitch.SfnUplinkCom
pSwitch parameter) and
CellAlgoSwitch.TurboReceiver
Switch cannot be on at the same
time.
l Functions related to mobility and load management

Name Switch
High speed Cell.HighSpee High Speed If downlink AFC is enabled,

mobility dFlag Mobility only intra-BBP SFN (RRUs
serving an SFN cell directly
connect to the same BBP) is
supported, and inter-BBP SFN
and inter-eNodeB SFN based on
eNodeB coordination are not
supported.
l Functions related to CoMP

Name Switch
DL CoMP cell IntraDlComp DL CoMP When DL CoMP is enabled,

Switch option (TDD) SFN cells cannot be added to a
of the DL CoMP cluster.
CellAlgoSwitc
h.DlCompSwit
ch parameter

eRAN
l Functions related to RAN-terminal coordination

Name Switch
DRX CellDrxPara. DRX and In an SFN cell where uplink

DrxAlgSwitch Signaling SRS measurement is used, DRX
Control prolongs the SRS measurement
period because SRS
measurement is performed only
in active time.
Dynamic DRX CellAlgoSwitc DRX and In an SFN cell where uplink

h.DynDrxSwit Signaling SRS measurement is used, DRX
ch Control prolongs the SRS measurement
period because SRS
measurement is performed only
in active time.
l Functions related to LTE evolution

Name Switch
Smart carrier SMART_CA Multi-carrier Virtual grids cannot be

selection based RRIER_SEL Unified constructed for SFN cells.
on virtual grids ECTION_SW Scheduling
option of the
MultiCarrUni
fiedSch.Multi
CarrierUnifie
dSchSw
parameter

Name Switch
Location ENodeBAlgoS LCS If OTDOA-based positioning is

service witch.LcsSwit used in SFN scenarios, the
ch positioning accuracy decreases.
This is because a UE cannot
distinguish the source RRU of
the positioning reference signals
(PRSs) received during
reference signal time difference
(RSTD) measurements and
provides only the ID of the SFN
cell where the PRSs are
received. (OTDOA is short for
Observed Time Difference Of
Arrival.)

eRAN

Name Switch
Dynamic LTE_DYN_P Dynamic Dynamic power sharing between

power sharing OWER_SHA Power Sharing LTE carriers is performed based
between LTE RING_SW Between LTE on physical cells that share one
carriers option of the Carriers RF module. When this function
CellDynPowe is enabled in an SFN cell,
rSharing.Dyn dynamic power sharing between
amicPowerSh LTE carriers cannot provide
aringSwitch maximum gains. If one of the
parameter RF modules serving an SFN cell
does not support power sharing,
this function will provide
negative gains. Therefore, this
function is not recommended for
SFN cells.
l Functions related to equipment

Name Switch
Low power CellLowPowe Energy In low power consumption

consumption r.LowPwrSwit Conservation mode, a cell can normally use
mode ch and Emission the following energy saving
Reduction methods: reducing the transmit
power for services in the cell,
reducing the transmit power for
reference signals, shutting down
some of the transmit channels,
and shutting down the carrier of
the cell. However, shutting down
some of the transmit channels is
not supported in an SFN cell.

Name Switch
eCoordinator- CellAlgoSwitc Interference Interference randomization takes

based h.InterfRandS Randomizing effect at the cell level. Therefore,
interference witch (TDD) inter-RRU interference
randomization randomization does not take
effect in an SFN cell.

eRAN
6.3 Requirements
6.3.1 Licenses
Feature ID Feature Name Model Sales Unit
TDLOFD-0010 SFN LT1ST00SFN0 Per Cell

75 0
NOTE
"Per cell" in the Sales Unit column refers to the physicals cells used to form an SFN cell.
The number of feature licenses and capacity licenses required for an SFN cell depends on the
number of RRUs serving the SFN cell. For example, if an SFN comprises three physical cells
and DL 2x2 MIMO is enabled, three license units are required for each of the following
license control items: Number of cells, SFN, and DL 2x2 MIMO.
6.3.2 Software
None

Name Switch
Extended CP Cell.DlCyclic Extended CP The application scenarios are

Prefix different. Extended CP is used in
the extended coverage scenario,
while SFN is used in indoor
coverage and outdoor coverage
scenarios.
Adaptive CellBf.Adapt Beamforming None

MUBF Start MubfStartThl (TDD)
Threshold d
Uplink SU- ULSUMIMO MIMO None

MIMO 2LayersSwitc
h option of the
CellAlgoSwitc
h.UlSuMimoA
lgoSwitch
parameter

eRAN

Name Switch
Massive None Massive None

MIMO MIMO (TDD)
introduction
Inter-cell InterCellDmi D-MIMO In inter-cell D-MIMO scenarios,

downlink D- moJTSwitch (TDD) only common cells can be added
MIMO option of the to the D-MIMO cluster.
CellAlgoSwitc In LampSite scenarios, inter-cell
h.DMIMOAlg D-MIMO is compatible with
oSwitch SFN if the SFN cell is set up on
parameter a single pRRU.
l Functions related to access management

Name
Detection of ExceedRadiusRaDetectionSw Random Access Control

contention- option of the
based random CellAlgoSwitch.RachAlgoSwit
access beyond ch parameter
cell radius
Optimization of NonContRaOptSwitch option Random Access Control

non-contention- of the
based random CellAlgoSwitch.RachAlgoSwit
access beyond ch parameter
cell radius

Name Switch
Intra- None Soft Split None

frequency Resource
split Duplex (TDD)
Inter-eNodeB CellDlschAlgo. Inter-eNodeB None

multi-carrier MultiCarrierCo Multi-Carrier
coordinated SchAlgoSw Coordinated
scheduling Scheduling
(TDD)
l Functions related to interference mitigation

eRAN

Name
Interference UlInterfSuppressionSwitch Interference Detection and

detection and option of the Suppression
suppression CellAlgoSwitch.AvoidInterfSwi
tch parameter
Remote CellRicAlgo.RemoteInfAdpAvo Interference Detection and

interference idSwitch Suppression
adaptive
avoidance

Name Switch
Turbo TurboBfSwitc WTTx Turbo None

beamforming h option of the Beamforming
CellAlgoSwitc (TDD)
h.MuBfAlgoS
witch
parameter
4-antenna AntSelEnhan WTTx Turbo None

selective ceBfSwitch Beamforming
transmission option of the (TDD)
CellAlgoSwitc
h.BfAlgoSwitc
h parameter
eMBMS CellMBMSCf eMBMS The current version does not

g.MBMSSwitc support eMBMS in SFN
h scenarios. Therefore, eMBMS
and SFN cannot take effect at
the same time.
l Functions related to networking

Name
Out-of-band OutOfBandRelaySwitch Relay

relay option of the
parameter
In-band relay None Relay

eRAN

Name
Adaptive inter- None Adaptive ICIC

cell interference
cancellation
6.3.3 Hardware
Base Station Models

The following base stations are compatible with this function:

Boards
The restrictions on hardware planning for outdoor coverage are as follows:
l 2T2R SFN cells cannot be configured on the LBBPc.

l The BBP.WM parameter must be set to TDD_ENHANCE for the LBBPc and LBBPd.
In indoor coverage scenarios, if the BBP is LBBPc or LBBPd, the BBP.WM parameter must
be set to TDD.
RF Modules
RF modules refer to RRUs, pRRUs, and pRRU groups.
RF modules must support the same frequency band.
RRUs can be set to work in 2T2R, 4T4R or 8T8R mode.
In the LampSite solution, SFN requires that 2T2R pRRUs be used.
The Topo Type parameter in the RRUCHAIN managed object (MO) must be set to CHAIN
or RING.
Cells
The cell bandwidth is 10 MHz or 20 MHz.
6.3.4 Networking
SFN supports uplink-downlink configurations 1 and 2 and special subframe configuration 7.
When intra-eNodeB physical cells are combined to form an SFN cell, the difference in their
coverage radiuses cannot exceed 1 km. If the difference exceeds 1 km, then the delay in
receiving signals from different physical cells deviates widely. In this case, if the power
difference between signals received from different physical cells is slight, the downlink
demodulation performance deteriorates.

eRAN
6.3.5 Others
None

The parameters used for function activation are listed in the following tables. This section
does not describe parameters related to cell establishment. For details about the initial cell
configuration, see the base station initial configuration guides.
An SFN cell requires two to seven sets of sector equipment or one to six sector equipment
groups. If RRUs are used, configure sector equipment. If pRRU groups are used, configure
sector equipment groups.
Table 6-2 Common parameters used for activation

Name
Cell ID Cell.CellId None
Physical cell ID Cell.PhyCellId None
Subframe Cell.Subframe This parameter specifies the uplink-downlink

assignment Assignment subframe configuration of an E-UTRAN TDD cell.
For details about uplink-downlink subframe
configurations, see 3GPP TS 36.211.
Special Cell.SpecialSu This parameter specifies the special subframe

subframe bframePatterns configuration of an E-UTRAN TDD cell. For details
patterns about special subframe configurations, see 3GPP TS
36.211.
Flag of Multi- Cell.MultiRruC BOOLEAN_TRUE

RRU Cell ellFlag
Mode of Multi- Cell.MultiRruC l To combine RRUs or pRRUs to serve an SFN

RRU Cell ellMode cell, set this parameter to SFN.
l To combine pRRU groups to serve an SFN cell,
set this parameter to MPRU_AGGREGATION.
Physical Cell Cell.SectorEqm Set this parameter to a value that is equal to the
Number of SFN Num number of physical cells to be combined into an SFN
Cell cell.

eRAN

Name
Cell Cell.TxRxMod l For outdoor coverage scenarios, set this parameter

transmission e to:
and reception – 4T4R if the physical cells constituting the SFN
mode cell are all 4T4R cells or 2T2R and 4T4R cells
– 8T8R if the physical cells constituting the SFN
cell are all 8T8R cells, 8T8R and 4T4R cells,
8T8R and 2T2R cells, or 8T8R, 4T4R, and
2T2R cells
– 2T2R if the physical cells constituting the SFN
cell are all 2T2R cells
l For indoor coverage scenarios, set this parameter
to 2T2R.
SFN UL CellAlgoSwitc JOINT

Scheduling h.SfnUlSchSwi
Switch tch
SFN DL CellAlgoSwitc JOINT

Switch tch
serve an SFN cell.
serve an SFN cell
Name
Local cell ID eUCellSectorE None

qm.LocalCellId
Sector eUCellSectorE Set this parameter to the sector equipment ID

equipment ID qm.SectorEqm specified when the sector equipment is added.
Id
Reference eUCellSectorE Set this parameter if different power needs to be set

signal power qm.ReferenceS for different pieces of sector equipment.
ignalPwr
Baseband eUCellSectorE None

equipment ID qm.BaseBandE
qmId

eRAN

Name
Reference eUCellSectorE None

Signal Power qm.ReferenceS
Margin ignalPwrMargi
n
combined to serve an SFN cell.
combined to serve an SFN cell
Name
Create Default SECTOR.CRE TRUE

Sector ATESECTORE
Equipment QM
Local cell ID EuSectorEqm None

Group.LocalCe
llId
Sector EuSectorEqm None

Equipment Group.SectorE
Group ID qmGroupId
Baseband EuSectorEqm None

equipment ID Group.BaseBa
ndEqmId
Reference EuSectorEqm Set this parameter if different power needs to be set

signal power Group.Referen for different sector equipment groups.
ceSignalPwr
The parameters used for function optimization are listed in the following tables.
The following table describes the parameters that need to be set in the EuCellPriBBEqm MO
to specify the primary baseband equipment information.

Name
Local cell ID EuCellPriBBE None

qm.LocalCellId

eRAN

Name
Primary EuCellPriBBE If primary baseband equipment is not configured for

Baseband qm.PriBaseBa a cell, the eNodeB selects a BBP for the cell among
Equipment ID ndEqmId all BBPs that have not been bound to cells.
If this parameter is configured, the cell uses the
specified primary baseband equipment. In this case,
the eNodeB selects a BBP for the cell among the
BBPs included in the primary baseband equipment.
The following table describes the parameters that need to be set in the PDSCHCFG MO to
specify the RS power.

Name
Local cell ID PDSCHCfg.Lo This parameter must be set if the

calCellId eUCellSectorEqm.ReferenceSignalPwr or
EuSectorEqmGroup.ReferenceSignalPwr
Reference PDSCHCfg.Re None

signal power ferenceSignalP
wr
The following table describes the parameters that need to be set in the CellAlgoSwitch MO to
set the SFN algorithm switch, uplink joint reception antenna number combination switch, and
SFN uplink CoMP switch.

Name
SFN Algorithm CellAlgoSwitc SfnUll2Selectiv None

Switch h.SfnAlgoSwitc eRcvSwitch
h
CellAlgoSwitc SfnTarRruAdp This option and the

h.SfnAlgoSwitc tSelSwitch SfnTarRruSelEnhSwitch option
h cannot be both selected.
UL JR Antenna CellAlgoSwitc Ul2R8RJRSwi Set this option to its recommended

Number h.UlJRAntNum tch value.
Combined CombSw
Switch
h.UlJRAntNum tch value.
CombSw

eRAN

Name

CombSw

CombSw
SFN Uplink CellAlgoSwitc IntraBaseBand Set this option to its recommended

Comp Switch h.SfnUplinkCo Switch value.
mpSwitch It is recommended that this option
be set only in DBS3900 or
DBS5900 and not be set in
LampSite eNodeBs.
CellAlgoSwitc InterBaseBand Set this option to its recommended

h.SfnUplinkCo Switch value.
LampSite eNodeBs.
CellAlgoSwitc ComCoverUlC Set this option to its recommended

h.SfnUplinkCo ompSwitch value.
LampSite eNodeBs.
CellAlgoSwitc SfnUplinkCom Set this option to its recommended

h.SfnUplinkCo p3CellSwitch value.
LampSite eNodeBs.
The following table describes the parameter that needs to be set in the CellUlCompAlgo MO
to specify the threshold used to determine the selection of UEs for UL CoMP in an SFN cell.

Name
Sfn UL CoMP CellUlCompAl Set this parameter to its recommended value.

Threshold go.SfnUlComp This parameter must be set if uplink joint reception is
Thd enabled in the SFN cell.

eRAN

To ensure optimal resource usage, the activation of an SFN cell may deactivate and reactivate
some cells served by the eNodeB.
Configuring an SFN Cell for a Newly Deployed eNodeB
RRUs or pRRUs can only be separately deployed.
Scenario 1: Configuring an SFN cell using RRUs or pRRUs
The following description uses an SFN cell served by three RRUs as an example. The
parameter settings in the following commands are used for reference only. Set the parameters
based on network requirements.
Adding sectors (example: adding 4T4R sectors with SECTOR.CREATESECTOREQM set
to TRUE)
ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0B, ANT3CN=0, ANT3SRN=60, ANT3SN=0,
ANT3N=R0C, ANT4CN=0, ANT4SRN=60, ANT4SN=0, ANT4N=R0D, CREATESECTOREQM=TRUE,
SECTOREQMID=0;
SECTOREQMID=1;
SECTOREQMID=2;
Adding SFN cells (example: adding 4T4R SFN cells)

ADD CELL: LOCALCELLID=0, CELLNAME="TDD_SFN", NBCELLFLAG=FALSE, FREQBAND=41,
ULEARFCNCFGIND=NOT_CFG, DLEARFCN=40340, ULBANDWIDTH=CELL_BW_N100,
DLBANDWIDTH=CELL_BW_N100, CELLID=100, PHYCELLID=100, FDDTDDIND=CELL_TDD,
SUBFRAMEASSIGNMENT=SA2, SPECIALSUBFRAMEPATTERNS=SSP7, EUCELLSTANDBYMODE=ACTIVE,
ROOTSEQUENCEIDX=0, CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,
EMERGENCYAREAIDCFGIND=NOT_CFG, UEPOWERMAXCFGIND=NOT_CFG,
MULTIRRUCELLFLAG=BOOLEAN_TRUE, MULTIRRUCELLMODE=SFN, SECTOREQMNUM=3,
TXRXMODE=4T4R;
Adding sector equipment for the cell

ADD EUCELLSECTOREQM: LOCALCELLID=0, SECTOREQMID=0, BASEBANDEQMID=0;
Setting the joint scheduling mode

MOD CELLALGOSWITCH: LOCALCELLID=0, SFNULSCHSWITCH=JOINT, SFNDLSCHSWITCH=JOINT;
Activating the cell

Scenario 2: Configuring an SFN cell using pRRU groups

The following assumes that an SFN cell is served by two pRRU groups, each with four
pRRUs. The parameter values serve as examples only and should be adjusted as required.
Configuring sectors. Set SECTOR.CREATESECTOREQM to TRUE to create sector
equipment.

eRAN

Configuring the SFN cell

ADD CELL: LOCALCELLID=0, CELLNAME="TDD_SFN", NBCELLFLAG=FALSE, FREQBAND=41,
ULEARFCNCFGIND=NOT_CFG, DLEARFCN=40340, ULBANDWIDTH=CELL_BW_N100,
DLBANDWIDTH=CELL_BW_N100, CELLID=100, PHYCELLID=100, FDDTDDIND=CELL_TDD,
SUBFRAMEASSIGNMENT=SA2, SPECIALSUBFRAMEPATTERNS=SSP7, EUCELLSTANDBYMODE=ACTIVE,
ROOTSEQUENCEIDX=0, CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,
EMERGENCYAREAIDCFGIND=NOT_CFG, UEPOWERMAXCFGIND=NOT_CFG,
MULTIRRUCELLFLAG=BOOLEAN_TRUE, MULTIRRUCELLMODE= MPRU_AGGREGATION, TXRXMODE=2T2R;

Adding baseband equipment

ADD BASEBANDEQM: BASEBANDEQMID=0, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL, SN1=3;
Adding sector equipment groups 0 and 1

ADD EUSECTOREQMGROUP: LocalCellId=0, SectorEqmGroupId=0, BASEBANDEQMID=0;
ADD EUSECTOREQMGROUP: LocalCellId=0, SectorEqmGroupId=1, BASEBANDEQMID=0;
Adding four sets of sector equipment to each group (The four sets of sector equipment are RF
combined to serve a physical cell)

Activating the cell

Configuring an SFN Cell for an Existing eNodeB
Radio parameters such as PCIs, RACH root sequences, and neighbor relationships have been
replanned to adapt to the new cell topology.
In this example:
l There are three physical cells: 0, 1, and 2.

eRAN
l Cells 0, 1, and 2 use sector equipment 0, 1, and 2, respectively.

l The cell ID of the new SFN cell is the same as that of cell 0.
l The cell capacity mode (specified by the CellRacThd.CellCapacityMode parameter) of
cell 0 remains unchanged after the SFN cell reconstruction. To use a different cell
capacity mode, change the value of the CellRacThd.CellCapacityMode parameter.
Deactivating cells 0, 1, and 2
Changing the parameter settings for cell 0

MOD CELL: LocalCellId=0, MultiRruCellFlag=BOOLEAN_TRUE, MultiRruCellMode=SFN,
SectorEqmNum=3;
Removing sector equipment 1 and 2 from cells 1 and 2, respectively

Binding sector equipment 1 and 2 to cell 0

Activating the SFN cell


Optimizing the SFN Cell Configuration for a Newly Deployed eNodeB
Modifying the RS power for the PDSCH

Optimizing the SFN Cell Configuration for an Existing eNodeB

Changing the PCI and RACH root sequence of cell 0 by running MOD CELL if these
parameters are replanned
MOD CELL:LOCALCELLID=0,PHYCELLID=0,ROOTSEQUENCEIDX=0;
Removing the original neighbor relationships, and adding newly planned neighbor
relationships

eRAN




Using MML Commands

Run the DSP CELL command. If the command output meets the following conditions, the
SFN cell has been activated:
l The value of Cell instance state is Normal.
l The value of Cell topology type is SFN Type or MPRU Aggregation Type.
l The values of all RRUs' Work Status are Normal.
Cell-Level Performance Monitoring

Users can perform packet injection in the cell until the cell throughput reaches the maximum
and monitor the RB usage on the U2020 to check whether SFN has been activated.
If the number of RBs of an SFN cell is a multiple (an integer greater than 1) of the number of
RBs in a single physical cell, SFN has taken effect. For example, in an SFN cell consisting of
two physical cells, if the number of RBs is 100 (two times the number of RBs in a single
physical cell) when the cell bandwidth is 10 MHz, SFN has taken effect.

In an area covered by an SFN cell, a UE moves from the center (the signal strength is –75
dBm) of a physical cell to an overlapping area of multiple physical cells and performs uplink
and downlink services. During this period, view the following results to check whether the
SFN function has been activated:
l Uplink RSRP of each RRU's SRS (dBm)
l Uplink SINR of the UE (dB)

eRAN
l Uplink and downlink UE scheduling attributes

Based on the SFN monitoring results, perform the following analysis:
l Check the RRUs in the working RRU list. If the list contains all RRUs, SFN has been
activated.
l Based on the value of UL RRU Flag, determine whether uplink joint reception has taken
effect.
NOTE
If a physical cell is faulty, the eNodeB cannot perform joint reception for UEs in the cell. However, this
information is not always updated immediately on the U2020. There is a delay of approximately 2s in
updating the information displayed on the GUI.

SFN can be monitored using the following methods:
l Starting monitoring tasks for SFN detection, UE-level MUBF, and cell-level MUBF
l Measuring counters
Starting SFN Detection, UE-Level MUBF, and Cell-Level MUBF Monitoring

Tasks
On the U2020 client, start SFN detection, UE-level MUBF, and cell-level MUBF monitoring
tasks to monitor the RRU utilization, and MUBF- and CBF-capable UE pairing status when
SFN is enabled.

eRAN
On the U2020 client, view the monitoring results of the objects listed in Table 6-5.
Table 6-5 Example of SFN detection monitoring results
UL User Mode In the uplink, UEs can be classified into jointly

DL User Mode In the downlink, UEs can be classified into jointly

Physical Cell Identifier This item indicates the physical cell ID of an SFN
cell.
UL RRU eNodeB ID This item indicates the eNodeB ID of an RRU used

for uplink transmission.
UL Sector Equipment or This item indicates the sector equipment ID or sector

Equipment Group Flag equipment group ID.
UL RRU Flag This item indicates the attribute of an uplink RRU.

Uplink RRUs can be classified into:
l Target RRU
l Work RRU
l Other RRU
l Work RRU (Joint Reception)
l Target RRU (Joint Reception)
l Other RRU (Joint Reception)
Table 6-6 and Table 6-7 describe the UE- and cell-level MUBF monitoring results,
respectively.
Table 6-6 Example of UE-level MUBF monitoring results
Number of Successful MUBF Indicates the number of RBs that are allocated to
Pairing RB successfully paired UEs within a period (one second).
Number of Successful SFNCBF Indicates the number of RBs that are allocated to
Pairing RB successfully paired UEs within a period (one second).
Table 6-7 Example of cell-level MUBF monitoring results
Number of Successful MUBF Indicates the number of RBs that are allocated to
Pairing RB successfully paired UEs for MUBF.

eRAN
Number of Users' Successful Indicates the number of successfully paired UE pairs

MUBF Pairing Users for MUBF.
Number of Enable MUBF Pairing Indicates the number of RBs that are allocated to
RB paired UEs for MUBF.
Measuring Counters
For details about the counters to be monitored, see 24 Counters. The
L.CellSectorEQUIP.SFN.UL.PRB.Used.Avg counter is used to measure the average number
of PRBs occupied by the PUSCH for all UEs served by a set of sector equipment in an SFN
cell.
The target RRU may change for UEs in an SFN cell. As a result,
L.CellSectorEQUIPGroup.SFN.RRC.ConnReq.Att and
L.CellSectorEQUIPGroup.SFN.RRC.ConnReq.Succ may be counted on different sets of
sector equipment. Therefore, the value of
L.CellSectorEQUIPGroup.SFN.RRC.ConnReq.Succ may be greater than the value of
L.CellSectorEQUIPGroup.SFN.RRC.ConnReq.Att for a particular set of sector
equipment. However, the values of these counters for the entire SFN cell are not affected.

eRAN 7 4x4 MIMO in the Overlapping Areas Between the
SFN Feature Parameter Description Physical Cells of an SFN Cell
7 4x4 MIMO in the Overlapping Areas

Between the Physical Cells of an SFN Cell
7.1 Principles
2T2R SFN cells normally benefit from a maximum of 2x2 MIMO. 4x4 MIMO has been
introduced for the overlapping areas between the physical cells of an SFN cell. This can
generate the performance gains of 4x4 MIMO for SFN cells without changing the SFN
networking. With this function, 4x4 MIMO is implemented for TM9 UEs (and also TM10
UEs in the case of FDD) in the overlapping areas between the physical cells of an SFN cell.
This function is controlled by the SfnJtSwitch option of the CellAlgoSwitch.SfnAlgoSwitch

parameter.
The eNodeB configures CSI-RSs on four ports for an SFN cell when certain conditions are
met in the overlapping areas. After the configuration, a UE can enter the 4x4 MIMO state.
The conditions for configuring CSI-RSs on four ports are as follows:
l The UE has at least four receive antennas and is capable of TM9 (or TM10, which can be
used in the case of FDD).
l The difference between the UE-received highest RSRP and second highest RSRP of two
RRUs in the SFN cell is less than the value of the
CellDlschAlgo.OverlapRsrpIsolationThd parameter.
l For FDD:
– The downlink data volume of the UE is greater than or equal to the value of the
CellDlschAlgo.DlUserDataThld parameter, that is, there are large-packet downlink
transmissions to the UE.
– The MCS index for rank-2 transmission in TM3 is 24 or higher.
l For TDD:
– The downlink throughput reaches the peak value when rank-2 transmission in TM3
is used. In addition, the MCS index is greater than or equal to the MCS index
threshold specified by the CellDlschAlgo.RankChangeAttemptMcsThld parameter
and the IBLER is less than or equal to the IBLER threshold specified by the
CellDlschAlgo.RBDamageNearPointIblerTh parameter.

– The CellBfMimoParaCfg.BfMimoAdaptiveSwitch parameter is set to

MIMO_BF_ADAPTIVE, and the CellMimoParaCfg.MimoAdaptiveSwitch
parameter is set to OC_ADAPTIVE or OL_ADAPTIVE.
The eNodeB configures TM9 for UEs that meet the 4x4 MIMO conditions in the overlapping
areas between the physical cells of an SFN cell if the 4x4 MIMO function is enabled, no
matter it is enabled alone or after TM9-related functions are enabled. In the case of FDD, the
eNodeB configures TM9 or TM10 for UEs that meet the 4x4 MIMO conditions in the
overlapping areas between the physical cells of an SFN cell based on their capabilities if the
4x4 MIMO function is enabled after TM10-related functions are enabled.
For TDD, this function can be used only when both the CellAlgoSwitch.SfnUlSchSwitch and
CellAlgoSwitch.SfnDlSchSwitch parameters are set to JOINT.
7.2.1 Benefits
It is recommended that 4x4 MIMO be enabled in the overlapping areas between the physical
cells of an SFN cell in low-speed scenarios.
For FDD: After 4x4 MIMO is enabled in the overlapping areas between the physical cells of
an SFN cell, the downlink throughput of TM9 UEs in the 4x4 MIMO state in the overlapping
areas increases by 5% to 20% when the percentage of UEs in the overlapping areas is greater
than 20% and the average SINR is greater than 20 dB.
For TDD: After 4x4 MIMO is enabled in the overlapping areas between the physical cells of
an SFN cell, the downlink throughput of TM9 UEs in the 4x4 MIMO state in the overlapping
areas increases by 5% to 20% when the percentage of UEs in the overlapping areas is greater
than 20% and the average SINR is greater than 25 dB.
7.2.2 Impacts
Network Impacts
None

Function Impacts
Name Switch
FDD Downlink Dl256QamSwit Modulation When the

256QAM ch option of the Schemes percentage of
CellAlgoSwitc UEs in the
h.Dl256QamAl overlapping
goSwitch areas between
parameter the physical
cells exceeds
20%, 4x4
MIMO in the
overlapping
areas between
the physical
cells of an SFN
cell has the
following
impacts:
l If downlink
256QAM is
disabled and
the average
SINR
exceeds 20
dB, the
downlink
throughput
of TM9 UEs
in the 4x4
MIMO state
in the
overlapping
areas
increases by
5% to 20%.
l If downlink
256QAM is
enabled, the
average
SINR is less
than 25 dB,
and the
percentage
of rank-3
and rank-4
transmission
s is low,
then the
downlink


Name Switch
throughput
gains for
TM9 UEs in
the 4x4
MIMO state
in the
overlapping
areas may
decrease.
Therefore,
4x4 MIMO
in the
overlapping
areas
between the
physical
cells of an
SFN cell is
not
recommende
d in this
scenario.


Name Switch
TDD Downlink Dl256QamSwit Modulation When the

256QAM ch and Schemes percentage of
Dl256QamAcc UEs in the
essorySwitch overlapping
options of the areas between
CellAlgoSwitc the physical
h.Dl256QamAl cells exceeds
goSwitch 20%, 4x4
parameter MIMO in the
overlapping
areas between
the physical
cells of an SFN
cell has the
following
impacts:
l If downlink
256QAM is
disabled and
the average
SINR
exceeds 25
dB, the
downlink
throughput
of TM9 UEs
in the 4x4
MIMO state
in the
overlapping
areas
increases by
5% to 20%.
l If downlink
256QAM is
enabled, the
average
SINR is less
than 30 dB,
and the
percentage
of rank-3
and rank-4
transmission
s is low,
then the
downlink
throughput


Name Switch
gains for
TM9 UEs in
the 4x4
MIMO state
in the
overlapping
areas may
decrease.
Therefore,
4x4 MIMO
in the
overlapping
areas
between the
physical
cells of an
SFN cell is
not
recommende
d in this
scenario.
FDD CA cell N/A Carrier In downlink CA

Aggregation scenarios, 4x4
MIMO in the
overlapping
areas of an SFN
cell can be used
only for UEs on
their PCCs.
7.3 Requirements
7.3.1 Licenses
None
7.3.2 Software
RAT Function Function Switch Reference
Name
FDD SFN Cell.MultiRruCellMode SFN

TDD


Name Switch
FDD DL CoMP FDDHomNetD DL CoMP 4x4 MIMO in the

cell lCompSwitch, (FDD) overlapping areas
FDDHetNetDl between the physical
CompSwitch, cells of an SFN cell
and cannot be used together
Tm9JtSwitch with DL CoMP due to
options of the issues related to CSI-RS
CellAlgoSwitc cooperation between
h.DlCompSwitc functions.
h parameter
FDD Virtual Virtual4T4RS Virtual 4T4R 4x4 MIMO does not take
4T4R witch option of (FDD) effect in the overlapping
the areas between the
CellAlgoSwitc physical cells of an SFN
h.EmimoSwitc cell with virtual 4T4R
h parameter enabled.
TDD None N/A N/A N/A
7.3.3 Hardware
Base Station Models

3900 and 5900 series base stations
For TDD, the following base stations are compatible with this function:
DBS3900 LampSite and DBS5900 LampSite
Boards
For FDD: If RRUs are combined to serve an SFN cell, the BBP must be LBBPd2, UBBPd4,
UBBPd5, UBBPd6, UBBPe2, UBBPe4, UBBPe5, or UBBPe6.
For TDD: If pRRUs are combined to serve an SFN cell, the BBP can be any BBP that
LampSite eNodeBs support.

RF Modules
This function has the same RF module requirements as the SFN function. For FDD, see 5.3.3
Hardware. For TDD, see 6.3.3 Hardware.
7.3.4 Others
For FDD, there are no requirements.
For TDD, if uplink SRS measurement is used, 4x4 MIMO in the overlapping areas of an SFN
cell does not take effect in either of the following scenarios because the eNodeB cannot
allocate SRS resources to UEs:
The SFN cell supports downlink CA but does not support uplink CA.
The SFN cell supports uplink CA, but UEs do not.
7.4.1 Data Configuration (FDD)

For the parameters used for activation, see the data preparation for the SFN function. Table
7-1 describes the additional parameters required for the activation of this function. Table 7-2
describes the parameters used for optimization.
Table 7-1 Parameters used for activation

Name
maximum CellDlschAlgo. N/A Set this parameter to its

number of MaxMimoRan recommended value.
MIMO layers kPara
SFN Algorithm CellAlgoSwitc SfnJtSwitch Set this option to its recommended

Switch h.SfnAlgoSwitc value.
h
CSI-RS Switch CellCsiRsPara N/A ADAPTIVE_CFG

Cfg.CsiRsSwitc
h

Table 7-2 Parameters used for optimization

Name
Overlap RSRP CellDlschAlgo. Set this parameter to its recommended value.

Isolation OverlapRsrpIso
Threshold lationThd
MCS Thld for CellDlschAlgo. Set this parameter to its recommended value.
Rank Change RankChangeAt
Attempt temptMcsThld
CSI-RS Period CellCsiRsPara 20 ms

Cfg.CsiRsPerio
d
CSI-RS Config CellCsiRsPara 1

User Ratio Cfg.CsiRsConfi
Threshold gUserRatioTh
CSI-RS CellCsiRsPara 0
Unconfig User Cfg.CsiRsUnco
Ratio Threshold nfigUserRatioT
h

User Number Cfg.CsiRsConfi
Threshold gUserNumTh

Number nfigUserNumT
Threshold h
CSI-RS Set CellCsiRsPara 20

Judge Cfg.CsiRsSetJu
Hysteresis dgeHysTimer
Timer

Judge Timer Cfg.CsiRsSetJu
dgeTimer
Downlink User CellDlschAlgo. Set this parameter to its recommended value.

Data Threshold DlUserDataThl
d

//Setting the maximum number of MIMO layers to 4
MOD CELLDLSCHALGO: LOCALCELLID=0, MaxMimoRankPara= SW_MAX_SM_RANK_4;
//Enabling 4x4 MIMO in the overlapping areas of an SFN cell
MOD CELLALGOSWITCH: LocalCellId=0, SfnAlgoSwitch=SfnJtSwitch-1;

//Turning on the CSI-RS switch

MOD CELLCSIRSPARACFG: LOCALCELLID=0, CsiRsSwitch=ADAPTIVE_CFG;

//Setting CSI-RS-related parameters
MOD CELLCSIRSPARACFG: LocalCellId=0, CsiRsSwitch=ADAPTIVE_CFG, CsiRsPeriod=ms20,
CsiRsConfigUserNumTh=1, CsiRsUnconfigUserNumTh=200, CsiRsConfigUserRatioTh=1,
CsiRsUnconfigUserRatioTh=0, CsiRsSetJudgeHysTimer=20, CsiRsSetJudgeTimer=1;
//Setting the downlink user data volume threshold
MOD CELLDLSCHALGO: LocalCellId=0, DlUserDataThld=400;

//Turning off the CSI-RS switch
MOD CELLCSIRSPARACFG: LocalCellId=0, CsiRsSwitch=NOT_CFG;
//Disabling 4x4 MIMO in the overlapping areas of an SFN cell

7.4.2 Data Configuration (TDD)

For the parameters used for activation, see the data preparation for the SFN function. Table
7-3 describes the additional parameters required for the activation of this function. Table 7-4
describes the parameters used for optimization.

Name
maximum CellDlschAlgo. N/A Set this parameter to its

number of MaxMimoRan recommended value.
MIMO layers kPara
BfMIMO CellBfMimoPa N/A MIMO_BF_ADAPTIVE

adaptive switch raCfg.BfMimo
AdaptiveSwitch
MIMO CellMimoPara N/A OC_ADAPTIVE or

Adaptive Cfg.MimoAdap OL_ADAPTIVE
Switch tiveSwitch
SFN Algorithm CellAlgoSwitc SfnJtSwitch Set this option to its recommended

Switch h.SfnAlgoSwit value.
ch
CSI-RS Switch CellCsiRsPara N/A ADAPTIVE_CFG

Cfg.CsiRsSwit
ch


Name
Overlap RSRP CellDlschAlgo. Set this parameter to its recommended value.

Isolation OverlapRsrpIso
Threshold lationThd
MCS Thld for CellDlschAlgo. Set this parameter to its recommended value.
Rank Change RankChangeAt
Attempt temptMcsThld
RB Damage CellDlschAlgo. It is recommended that this parameter be set to the

Cell Near Point RBDamageNea default value when downlink 256QAM is disabled,
User IBLER rPointIblerTh and to 15 or a smaller value when downlink 256QAM
Thd is enabled.
CSI-RS Period CellCsiRsPara 20 ms

Cfg.CsiRsPerio
d

User Ratio Cfg.CsiRsConf
Threshold igUserRatioTh
Ratio Threshold nfigUserRatio
Th

User Number Cfg.CsiRsConfi
Threshold gUserNumTh

Number nfigUserNumT
Threshold h

Judge Cfg.CsiRsSetJu
Hysteresis dgeHysTimer
Timer

Judge Timer Cfg.CsiRsSetJu
dgeTimer

//Setting the maximum number of MIMO layers to 4
MOD CELLDLSCHALGO: LOCALCELLID=0, MaxMimoRankPara= SW_MAX_SM_RANK_4;

//Setting the BfMIMO adaptive switch and MIMO Adaptive Switch parameters
MOD CELLBFMIMOPARACFG: LocalCellId=0, BfMimoAdaptiveSwitch=MIMO_BF_ADAPTIVE;
MOD CELLMIMOPARACFG: LocalCellId=0, MimoAdaptiveSwitch=OC_ADAPTIVE;
//Enabling 4x4 MIMO in the overlapping areas of an SFN cell
//Turning on the CSI-RS switch

//Setting CSI-RS-related parameters
MOD CELLCSIRSPARACFG: LocalCellId=0, CsiRsSwitch=ADAPTIVE_CFG, CsiRsPeriod=ms20,
CsiRsConfigUserNumTh=1, CsiRsUnconfigUserNumTh=200, CsiRsConfigUserRatioTh=1,
CsiRsUnconfigUserRatioTh=0, CsiRsSetJudgeHysTimer=20, CsiRsSetJudgeTimer=1;

//Turning off the CSI-RS switch
//Disabling 4x4 MIMO in the overlapping areas of an SFN cell


Check the following counters on the U2020 client. 4x4 MIMO has taken effect in the
overlapping areas of an SFN cell if the value of any of the following counters is not zero.
Table 7-5 Counters related to 4x4 MIMO in the overlapping areas of an SFN cell
1526732737 L.ChMeas.RI.Rank3
1526732738 L.ChMeas.RI.Rank4

The network monitoring method for this function is the same as that for the SFN function. For
FDD, see 5.4.3 Network Monitoring. For TDD, see 6.4.3 Network Monitoring.

eRAN
SFN Feature Parameter Description 8 SFN HetNet Smart Cluster Organization (FDD)
8 SFN HetNet Smart Cluster Organization

(FDD)
8.1 Principles
In an LTE multi-frequency homogeneous network, there are overlaps between the edges of
inter-frequency cells providing the same coverage. The data rates of cell-edge UEs are too
low to meet the development requirements of video and other services.
The mobile agile operation for service (mAOS) can automatically plan combinations of SFN
cells working on different carrier frequencies online to form an SFN multi-frequency
heterogeneous network without changing the antenna system. The change in the network
improves the performance perceived by cell-edge UEs. The SFN cells in the combinations
must meet the following conditions:
l There is little or no overlap between the edges of the SFN cells.
l The edge of one SFN cell is in the center of at least one of the other SFN cells.
The mAOS also monitors KPI changes every hour. If KPIs deteriorate due to improper
planning by the mAOS, the mAOS automatically performs a fast rollback. The mAOS allows
for the customization of a threshold for rollback in case KPIs deteriorate.

8.2.1 Benefits
After the network is changed from multi-frequency homogeneous SFN to multi-frequency
heterogeneous SFN using the SFN HetNet smart cluster organization function, Cell
Downlink Average Throughput increases by 5% to 10%, and User Downlink Average
Throughput of cell-edge UEs increases by 5% to 20%.
8.2.2 Impacts
Network Impacts
None

eRAN
Function Impacts
Name Switch
CA cell N/A Carrier If the edges of inter-frequency

Aggregation cells do not overlap, the
percentage of the overlapping
areas between the cell centers of
these inter-frequency cells may
decrease, and the percentage of
UEs for which CA takes effect
also decreases. As a result, the
Cell Downlink Average
Throughput of CA UEs
decreases.
8.3 Requirements
8.3.1 Licenses
None
8.3.2 Software
Function Name Function Switch Reference
SFN Cell.MultiRruCellMode 5 SFN (FDD)

None
8.3.3 Hardware
This function requires the same hardware as the SFN function. For details, see 5.3.3
Hardware.
8.3.4 Others
None

eRAN

For details, see the SFN HetNet Smart Cluster Organization Feature Description in the mAOS
Product Documentation.

eRAN
SFN Feature Parameter Description 9 Adaptive SFN/SDMA (FDD)
9 Adaptive SFN/SDMA (FDD)
9.1 Principles
Adaptive SFN/SDMA, together with the SFN function, allows for joint scheduling of UEs in
the overlapping areas between physical cells and independent scheduling of UEs in physical
cell centers, which increases cell throughput. Space division multiple access (SDMA) is used
for resource multiplexing between different physical cells.
The differences between the adaptive SFN/SDMA function and the SFN function are as
follows:
l With the SFN function, the eNodeB always uses joint scheduling.
l With the adaptive SFN/SDMA function, the eNodeB selects an appropriate scheduling
mode (joint or independent scheduling) for the UEs based on UE scheduling attributes.
Adaptive scheduling is used in adaptive SFN cells. Adaptive scheduling is enabled in the
uplink when the CellAlgoSwitch.SfnUlSchSwitch parameter is set to ADAPTIVE and
enabled in the downlink when the CellAlgoSwitch.SfnDlSchSwitch parameter is set to
ADAPTIVE.
For details about UE scheduling attribute decision, see 4.2 UE Scheduling Attribute
Decision (FDD). For details about scheduling time-frequency resources for UEs, see 4.1
Independent Scheduling and Joint Scheduling.
To improve voice quality for VoLTE UEs in adaptive SFN cells, joint scheduling can be
always used for these UEs by selecting the SfnVoLteDlJSchSwitch and
SfnVoLteUlJSchSwitch options of the CellAlgoSwitch.SfnAlgoSwitch parameter.
When the load of an adaptive SFN cell is heavy and the load among multiple RRUs is not
balanced, it is recommended that the PrbUsage option of the CellMLB.MultiRRUMode
parameter be selected to prevent the overload of a single RRU, increase the resource usage,
and improve system capacity.
If the SfnDlRblerOptSwitch option of the CellAlgoSwitch.SfnAlgoSwitch parameter is
selected, the optimization to resolve consecutive downlink block errors is enabled.
If both the TM9Switch option of the CellAlgoSwitch.EnhMIMOSwitch parameter and the
AsfnFastAttSwitch option of the CellAlgoSwitch.SfnAlgoSwitch parameter are selected,
fast UE scheduling attribute decision is enabled to balance subframe-level loads.

eRAN
When the CellAlgoSwitch.SfnUlSchSwitch parameter is set to ADAPTIVE, it is

recommended that the SchedulerCtrlPowerSwitch option of the
CellAlgoSwitch.UlSchSwitch parameter be selected to ensure that UE transmit power is fully
utilized so as to increase User Uplink Average Throughput.
9.2.1 Benefits
In indoor coverage areas, when two (for example) pRRU groups with five pRRUs in each
group are serving a heavily loaded SFN cell, the adaptive SFN/SDMA function increases Cell
Downlink Average Throughput by 0%–70% compared with the SFN function.
In densely populated urban outdoor areas, when three (for example) RRUs are serving a
heavily loaded SFN cell, the adaptive SFN/SDMA function increases Cell Downlink
Average Throughput by 0%–80%, compared with the SFN function. In addition, when the
Uplink Resource Block Utilizing Rate of a common SFN cell exceeds 50%, the adaptive
SFN/SDMA function increases Cell Uplink Average Throughput by 0%–10%.
For any given cell traffic volume, the PRB usage decreases and the User Uplink Average
Throughput and User Downlink Average Throughput increase in an adaptive SFN/SDMA
cell, compared with a common SFN cell.
If adaptive SFN/SDMA is deployed for a large number of cells, the SINR of the entire
network increases.
l If three RRUs are serving an SFN cell in a densely populated urban outdoor area and the
network load rate is 100%, the average PDCCH and PDSCH SINRs increase by 2 dB to
3 dB.
l If multiple pRRU groups are serving an SFN cell in an indoor area and the network load
rate is 100%, the average PDCCH and PDSCH SINRs increase by 5 dB to 15 dB. The
specific amount depends on the deployment density of the pRRUs before the SFN cell is
formed and on the number of pRRUs serving the SFN cell.
The following table lists the expected KPI changes in adaptive SFN/SDMA cells, compared
with common SFN cells and common cells, with the supported functions and environmental
factors held constant and the cell load not reached the maximum supported.
Table 9-1 Expected KPI changes in adaptive SFN/SDMA cells compared with common SFN
cells and common cells
KPI Expected KPI Changes Expected KPI Changes in

in Adaptive SFN/ Adaptive SFN/SDMA Cells
SDMA Cells Compared with Common
Compared with Cells
Common SFN Cells
Cell Downlink Average Increase No decrease

Throughput
Cell Uplink Average Increase No decrease

Throughput

eRAN
KPI Expected KPI Changes Expected KPI Changes in

in Adaptive SFN/ Adaptive SFN/SDMA Cells
SDMA Cells Compared with Common
Compared with Cells
Common SFN Cells
User Downlink Average Increase No decrease

Throughput
User Uplink Average Increase No decrease

Throughput
E-RAB Setup Success Decrease No decrease

Rate
RRC Setup Success Rate Decrease No decrease
Intra-Frequency No decrease No decrease

Handover Out Success
Rate
Service Drop Rate Increase No increase
Uplink Resource Block Decrease Increase

Utilizing Rate
Uplink Resource Block Decrease Increase

Utilizing Rate
9.2.2 Impacts
Network Impacts
For independently scheduled UEs, downlink CRSs are jointly transmitted by multiple RRUs
but the PDSCH is transmitted independently by a single RRU, causing an inconsistency
between the CRS and PDSCH SINRs. The inconsistency affects UE peak rates. Given the
same CRS SINR, the peak rate of an adaptive SFN cell is lower than that of either a common
SFN cell and a common cell.
The adaptive SFN/SDMA function allows more UEs to be scheduled in a TTI than the SFN
function, but it also makes it more likely that there will not be enough CCE resources.
Therefore, the value of L.ResOpt.CCELimit.PRB.DL increases significantly.
In a heavily loaded common SFN cell where PDCCH resources are insufficient, the adaptive
SFN/SDMA function increases the cell capacity but does not increase User Downlink
Average Throughput compared with the SFN function. There is no increase in User
Downlink Average Throughput because the cell serves a larger number of UEs when it is
heavily loaded.
If 2T and 4T physical cells are combined to form an SFN cell and four CRS ports are
configured for the SFN cell, 4T gains can be obtained in the 4T independent scheduling areas.
However, there is performance loss in the 2T independent scheduling areas. The performance
loss is about 5% in TM4 or higher than 5% in TM3. Therefore, the configuration of four CRS
ports is not recommended in this scenario.

eRAN
When adaptive SFN/SDMA is enabled in the uplink, UEs independently scheduled in the
uplink will be paired. Uplink measurement results, like the SINR, for these UEs become
different from those for jointly scheduled UEs. As a result, the target RRU selection results
and the number of selection times may change.
Function Impacts
Name Switch
Uplink CA CaUl2CCSwitc Carrier If uplink CA is enabled but SRS

h option of the Aggregation resources of the primary serving
CaMgtCfg.Cell cell (PCell) or SCell conflict with
CaAlgoSwitch the resources for other channels,
parameter the eNodeB may discard SRS
configuration in accordance with
section 8.2 "UE sounding
procedure" in 3GPP TS 36.213.
Consequently, the SRS
measurement in the adaptive SFN
cell (either as a PCell or as an
SCell) becomes inaccurate. In this
scenario, the eNodeB performs
only joint scheduling for CA UEs
in the adaptive SFN cell. As a
result, the proportion of UEs for
which joint scheduling is
performed in the adaptive SFN cell
increases.
Downlink CA CaDl3CCSwitc Carrier When both adaptive SFN and

h option of the Aggregation downlink CA are enabled and an
CaMgtCfg.Cell adaptive SFN cell serves as an
CaAlgoSwitch SCell for a UE, the UE cannot
parameter send SRSs in this SCell and its
scheduling attribute cannot be
determined by the eNodeB. In this
scenario, the eNodeB performs
only joint scheduling for the UE.
As a result, the proportion of UEs
for which joint scheduling is
performed in an adaptive SFN cell
increases.
Uplink 2x4 UlVmimoSwitc MIMO After adaptive SFN is enabled in

MU-MIMO h option of the the uplink, UE pairing between
CellAlgoSwitc RRUs takes precedence over UE
h.UlSchSwitch pairing within an RRU, and MU-
parameter MIMO no longer takes effect for
UEs paired between RRUs.

eRAN

Name Switch
Uplink 2x2 UlVmimoSwitc MIMO After adaptive SFN is enabled in

MU-MIMO h option of the the uplink, UE pairing between
CellAlgoSwitc RRUs takes precedence over UE
h.UlSchSwitch pairing within an RRU, and MU-
parameter MIMO no longer takes effect for
UEs paired between RRUs.
Downlink MU- EmimoMuMi eMIMO (FDD) In an adaptive SFN cell consisting

MIMO in TM4 moSwitch of 2T and 4T physical cells, if the
option of the downlink working RRUs for a UE
CellAlgoSwitc include a 2T RRU, the UE will not
h.EmimoSwitc be selected in UE pairing for MU-
h parameter MIMO.
Downlink MU- 4TxTM9MuMi eMIMO (FDD) In an adaptive SFN cell consisting

MIMO in TM9 moSwitch of 2T and 4T physical cells, if the
option of the downlink working RRUs for a UE
CellAlgoSwitc include a 2T RRU, the UE will not
h.EmimoSwitc be selected in UE pairing for MU-
h parameter MIMO.
Precise AMC PreciseAmcSw eMIMO (FDD) Adaptive SFN/SDMA affects the

itch option of accuracy of calculated interference
the from neighboring cells and further
CellAlgoSwitc affects the performance of precise
h.EmimoSwitc AMC. Therefore, it is
h parameter recommended that precise AMC
be disabled.
Downlink FreqSelSwitch Scheduling If an SFN cell is composed of

frequency option of the three or more physical cells, it
selective CellAlgoSwitc does not support downlink
scheduling h.DlSchSwitch frequency-selective scheduling.
parameter
eMTC EMTC_SWIT eMTC When adaptive SFN/SDMA is

introduction CH option of enabled, joint scheduling is always
the used for eMTC UEs.
CellEmtcAlgo.
EmtcAlgoSwitc
h parameter

eRAN

Name Switch
DL CoMP cell FDDHomNetD DL CoMP DL CoMP and adaptive SFN/

lCompSwitch, (FDD) SDMA can be enabled at the same
FDDHetNetDl time. However, only joint
CompSwitch, scheduling can be used for CoMP
and UEs in cooperating cells because
Tm9JtSwitch no RSRP information about RRUs
options of the serving neighboring cells is
CellAlgoSwitc available and UE scheduling
h.DlCompSwitc attributes cannot be determined.
h parameter
Multi-band MbfcsSwitch Multi-band When adaptive SFN/SDMA is in

optimal carrier option of the Optimal use, the error in the gain
selection CellAlgoSwitc Carrier estimation for handovers to or
h.MlbAlgoSwit Selection from SFN cells increases.
ch parameter Therefore, the benefits derived
from multi-band optimal carrier
selection (MBOCS) in this
situation are reduced.
High speed Cell.HighSpee High Speed Adaptive SFN/SDMA is not

mobility dFlag Mobility recommended for high-speed
scenarios, where UE scheduling
attributes change frequently.
High speed ProcSwitchBas High Speed If this function and high speed
specified policy edOnUserSpee Mobility specified policy management are
management d option of the both enabled, joint transmission is
CellAlgoSwitc always used for high-speed UEs
h.HighSpeedSc and SDMA is used only for low-
hOptSwitch speed UEs.
parameter
NPREO Cell-level Channel State When NPREO constant

constant parameter: Management optimization is enabled, the
optimization CellDlpcPdsch accuracy of neighboring cell
Pa.CellNpreoA interference calculation is affected
djThreshold and the performance of UE-level
NPREO constant optimization is
UE-level affected. Therefore, you are
parameter: advised not to enable UE-level
CellDlpcPdsch NPREO constant optimization.
Pa.UeNpreoAd
jThreshold
9.3 Requirements

eRAN
9.3.1 Licenses
LOFD-070205 Adaptive SFN/ LT1S0ASFSD0 Per Cell

SDMA 0
9.3.2 Software
Name
SFN Cell.MultiRruCellMode SFN

Function Function Switch Reference Description
Name
GSM and LTE CellAlgoSwitch.G GSM and LTE None

Dynamic LPwrShare Dynamic
Power Sharing Power Sharing
Flexible DdCellGroup.DdB Flexible None

bandwidth andWidth Bandwidth
based on based on
overlapping Overlap
carriers Carriers
(FDD)
Intra-eNodeB CellCspcPara.Intr CSPC If the

CSPC aEnbCspcSw CellAlgoSwitch.SfnDlSchSwitc
h parameter is set to
ADAPTIVE, the intra-eNodeB
CSPC function does not take
effect.
Super SuperCombCellS Super None

combined cell witch option of the Combined Cell
CellAlgoSwitch.Sf (FDD)
nAlgoSwitch
parameter

eRAN

Name
Virtual 4T4R Virtual4T4RSwitc Virtual 4T4R None

h option of the (FDD)
CellAlgoSwitch.E
mimoSwitch
parameter
9.3.3 Hardware
Base Station Models


l BTS3912E
l BTS3911E
Boards
This function requires the same boards as the SFN function. For details, see 5.3.3 Hardware.
RF Modules
This function requires the same RF modules as the SFN function. For details, see 5.3.3
Hardware.
9.3.4 Others
None

For the parameters used for activation, see 5.4.1.1 Data Preparation in 5 SFN (FDD). Table
9-2 describes the parameters that are set differently for the activation of this function. Table
9-3 describes the parameters used for optimization.

eRAN

Name
SFN UL CellAlgoSwitc It is recommended that this parameter be set to

Scheduling h.SfnUlSchSwi JOINT.
Switch tch If this parameter is set to ADAPTIVE, it is
recommended that the SchedulerCtrlPowerSwitch
option of the CellAlgoSwitch.UlSchSwitch
parameter be selected.
SFN DL CellAlgoSwitc ADAPTIVE

Switch tch

Name
SFN Algorithm CellAlgoSwitc SfnDlSchAttri It is recommended that this option

Switch h.SfnAlgoSwitc AdjsSwitch be selected when the
h CellAlgoSwitch.SfnDlSchSwitch
parameter is set to ADAPTIVE.
CellAlgoSwitc SfnVoLteDlJSc It is recommended that this option

h.SfnAlgoSwitc hSwitch be selected when the
CellAlgoSwitc SfnVoLteUlJSc It is recommended that this option

CellAlgoSwitc SfnDlRblerOp It is recommended that this option

h.SfnAlgoSwitc tSwitch be selected when the
SFN Downlink CellDlschAlgo. N/A Set this parameter to its

Load Period SfnDlLoadPeri recommended value.
od

eRAN

Name

High Load SfnDlHighLoa recommended value.
Threshold dThd If the cell load exceeds the
threshold, the percentage of
independently scheduled UEs
increases. This parameter takes
effect when the
CellAlgoSwitch.SfnDlSchSwitch

Low Load SfnDlLowLoad recommended value.
Threshold Thd If the cell load is lower than the
threshold, the percentage of
independently scheduled UEs
decreases. This parameter takes
effect when the
Downlink High CellDlschAlgo. N/A If the

Load SDMA DlHighLoadSd CellAlgoSwitch.SfnDlSchSwitch
Threshold maThdOffset parameter is set to ADAPTIVE, it
Offset is recommended that this
parameter be set to 10 if there are
two or three physical cells in an
SFN cell or to 15 if there are four
to six physical cells in an SFN
cell.
If the AsfnFastAttSwitch option
of the
CellAlgoSwitch.SfnAlgoSwitch
parameter is selected, it is
recommended that the default
value of this parameter be
retained.
NOTE
If this parameter is set to a small
value, independent scheduling is used
for a UE even if the strengths of
signals from the UE to two physical
cells are close. Consequently, the
difference between CRS SINR and
PDSCH SINR is large, User
Downlink Average Throughput
decreases significantly, or service
drops can occur.

eRAN

Name
Downlink Low CellDlschAlgo. N/A Set this parameter to its

Load SDMA DlLowLoadSd recommended value.
Threshold maThdOffset This parameter takes effect when
Offset the
UE Attribute CellDlschAlgo. N/A It is recommended that this

Judge Period UeAttJudgePer parameter be set to 200ms.
iod This parameter takes effect when
the
UE Attribute CellDlschAlgo. N/A Set this parameter to its

Judge RSRP UeAttJudgeRsr recommended value.
Hysteresis pHyst This parameter takes effect when
the
Target RRU CellUlschAlgo. N/A None

Select RSRP TarRruSelRsrp
Offset OffSetThd
Threshold
SFN Uplink CellUlschAlgo. N/A Set this parameter to its

Pair RSRP SfnUlPairRsrp recommended value.
Threshold Thd

MOD CELLALGOSWITCH: LOCALCELLID=0,SFNULSCHSWITCH=JOINT,SFNDLSCHSWITCH=ADAPTIVE;

Setting the downlink load measurement period, downlink heavy-load threshold, downlink
light-load threshold, and isolation degree decision threshold offset of downlink heavy-load
level for the SFN cell
MOD CELLDLSCHALGO: LOCALCELLID=0,SfnDlLoadPeriod =30,SfnDlHighLoadThd=
50,SfnDlLowLoadThd=20,DlHighLoadSdmaThdOffset=2;
Setting the uplink load measurement period for the SFN cell
MOD CELLULSCHALGO: LOCALCELLID=0,SfnUlLoadPeriod =1800;

eRAN

Setting the SFN uplink and downlink scheduling switches for deactivating adaptive SFN

SFN supports simplified configuration on the CME. The relevant steps are as follows:
Step 1 After creating a planned data area, choose SFN Combination from the main menu on the
CME.
Step 2 Specify cells to be combined into an SFN cell in the following sheet of the summary data file,
and then import the file into the CME.
NOTE
l Only one cell to be combined must be specified as the primary cell of an SFN cell.
l A cell to be combined must be unique in the sheet.
l A cell to be combined can be an SFN cell or a common cell, but must have been configured.
l If an SFN cell has multiple eNodeB IDs (for example, when the cells to be combined include an
inter-BBU SFN cell), Mode of Multi-RRU Cell can only be set to SFN.
Step 3 Choose Export Incremental Scripts from the main menu on the CME to export the
incremental scripts in the planned area and then activate the scripts.
Step 4 Deliver configuration data and activate the SFN cell.
----End
NOTE
In the simplified configuration on the CME, both SFN UL Scheduling Switch and SFN DL Scheduling
Switch are set to JOINT by default. If you want to enable Adaptive SFN/SDMA, manually modify the
parameter settings.

See UE-level performance monitoring in 5.4.2 Activation Verification. If both jointly
scheduled UEs (with multiple working RRUs) and independently scheduled UEs (with one
working RRU) exist, adaptive SFN/SDMA has been enabled.
Performance Monitoring
You can monitor the following counters on the U2020 to check whether adaptive SFN/SDMA
has been activated.

eRAN
Table 9-4 Counters for monitoring adaptive SFN/SDMA

1526728342 L.SFN.User.DLJ2I
1526729649 L.CellSectorEQUIP.SFN.ULISch.User.Avg
1526729651 L.CellSectorEQUIP.SFN.ULISch.PRB.Avg
1526729653 L.CellSectorEQUIPGroup.SFN.ULISch.User.Av
g
1526729655 L.CellSectorEQUIPGroup.SFN.ULISch.PRB.Av
g
Based on the monitoring results, perform the following analysis:

l If the value of L.SFN.User.DLJ2I is not zero, adaptive SFN/SDMA has taken effect.
l Uplink independent scheduling has taken effect if the value of any of the following
counters is not zero:
– L.CellSectorEQUIP.SFN.ULISch.User.Avg
– L.CellSectorEQUIP.SFN.ULISch.PRB.Avg
– L.CellSectorEQUIPGroup.SFN.ULISch.User.Avg
– L.CellSectorEQUIPGroup.SFN.ULISch.PRB.Avg
NOTE
If the UE used for monitoring is running full buffer services, wait for a period specified by the SFN
Downlink Load Period parameter before performing activation verification. If the network load is light
and joint scheduling is performed for the UE during initial access, the eNodeB will measure the
Downlink Resource Block Utilizing Rate in the specified period and adjust the UE scheduling attribute
decision threshold based on the measurement result. If the network load is heavy, a UE is more likely to
be independently scheduled.

details, see 5.4.3 Network Monitoring.

eRAN
SFN Feature Parameter Description 10 Adaptive SFN/SDMA (TDD)
10 Adaptive SFN/SDMA (TDD)
10.1 Principles
Adaptive SFN/SDMA, together with the SFN function, allows for joint scheduling of UEs in
the overlapping areas between physical cells and independent scheduling of UEs in physical
cell centers, increasing cell throughput. SDMA is used for resource reuse between different
physical cells.
The differences between the adaptive SFN/SDMA function and the SFN function are as
follows:
l With the SFN function, the eNodeB always uses joint scheduling.
l With the adaptive SFN/SDMA function, the eNodeB selects an appropriate scheduling
mode (joint or independent scheduling) for the UEs based on UE scheduling attributes.
Adaptive scheduling is used in adaptive SFN cells. Adaptive scheduling is enabled in the
uplink when the CellAlgoSwitch.SfnUlSchSwitch parameter is set to ADAPTIVE and
enabled in the downlink when the CellAlgoSwitch.SfnDlSchSwitch parameter is set to
ADAPTIVE.
For details about UE scheduling attribute decision, see 4.3 UE Scheduling Attribute
Decision (TDD). For details about scheduling time-frequency resources for UEs, see 4.1
Independent Scheduling and Joint Scheduling.
To improve voice quality for VoLTE UEs in adaptive SFN cells, joint scheduling can be
always used for these UEs by selecting the SfnVoLteDlJSchSwitch and
SfnVoLteUlJSchSwitch options of the CellAlgoSwitch.SfnAlgoSwitch parameter.
When the load of an adaptive SFN cell is heavy and the load among multiple RRUs is
imbalanced, it is recommended that the PrbUsage option of the CellMLB.MultiRRUMode
parameter be selected to prevent the overload of a single RRU, increase the resource usage,
and improve system capacity.
If the SfnDlRblerOptSwitch option of the CellAlgoSwitch.SfnAlgoSwitch parameter is
selected, the optimization to resolve consecutive downlink bit errors is enabled.
When the CellAlgoSwitch.SfnUlSchSwitch parameter is set to ADAPTIVE, it is
recommended that the SchedulerCtrlPowerSwitch option of the
CellAlgoSwitch.UlSchSwitch parameter be selected to ensure that UE transmit power is fully
utilized so as to increase User Uplink Average Throughput.

eRAN
10.2.1 Benefits
Adaptive SFN/SDMA is recommended when traffic in the SFN cell is heavy.
The average downlink throughput of a single UE at the cell edge increases by about 39%
when three RRUs serve an SFN cell in a typical dense urban area and the load ratio is 100%.
In indoor coverage areas, when two (for example) pRRU groups with five pRRUs in each
group are serving a heavily loaded SFN cell, the adaptive SFN/SDMA function increases Cell
Downlink Average Throughput by 0%–70% compared with the SFN function.
The following table lists the expected KPI changes in cells with the supported functions and
environmental factors held constant and the load not reached the maximum supported.
KPI Expected KPI Changes in Adaptive
SFN Cells Compared with Common
Cells
Cell Downlink Average Throughput Increase for low load; no decrease for
moderate or high load
Cell Uplink Average Throughput Increase for low load; no decrease for
User Downlink Average Throughput Increase for low load; no decrease for
User Uplink Average Throughput Increase for low load; no decrease for

Rate
Service Drop Rate No deterioration
10.2.2 Impacts
Network Impacts
In a typical dense urban area where the network load rate is 100%, Cell Downlink Average
Throughput of a single SFN cell served by three RRUs decreases to 85%–95% of that of a
common cell.
Since the CRSs are jointly transmitted but PDSCH data is independently transmitted to
independently scheduled UEs, the RI value obtained based on CRS measurement is
inconsistent with the RI value supported by the PDSCH. If rank 2 in TM3 is used for an

eRAN
independently scheduled UE for which the isolation degree is low, the RI value inconsistency
can cause consecutive bit errors or even cause the MCS index to drop to 0. Different
performance assurance methods can be used depending on target RRUs:
l If the target RRU is a 2T or 4T RRU, it is recommended that the SfnDlRblerOptSwitch
option of the CellAlgoSwitch.SfnAlgoSwitch parameter be selected. When this option is
selected, the eNodeB identifies the UEs for which rank 2 in TM3 is used and uses rank 1
fixedly in scheduling for these UEs to ensure UE performance. (The identification takes
1s.)
l If the target RRU is an 8T RRU, the eNodeB uses the TM adaptation algorithm to switch
the transmission mode for the UEs for which rank 2 in TM 3 is used to TM8 (the
switching takes about 2s). In TM8, DMRSs are used for PDSCH channel estimation, and
RI value inconsistency will not occur.
Note that consecutive bit errors or MCS index dropping to 0 continues during the
identification and switching periods.
Function Impacts
Name Switch
Uplink CA CaUl2CCSwitc Carrier If uplink CA is enabled and SRS

h option of the Aggregation resources of the PCell or SCell
CaMgtCfg.Cell conflict with other channels, the
CaAlgoSwitch eNodeB may discard SRS
parameter configuration according to section
8.2 "UE sounding procedure" in
3GPP TS 36.213. Consequently,
the SRS measurement in the
adaptive SFN cell (either as a
PCell or as an SCell) becomes
inaccurate. In this scenario, the
eNodeB performs only joint
scheduling for CA UEs in the
adaptive SFN cell. As a result, the
proportion of UEs for which joint
scheduling is performed in the
adaptive SFN cell increases.
UE number- ENodeBAlgoS Admission and In adaptive SFN/SDMA scenarios,

based radio witch.UeNumP Congestion when the cell load is relatively
resource reemptSwitch Control heavy, there will be both a large
preemption number of independently
scheduled UEs and a large number
of jointly scheduled UEs. If both
guaranteed bit rate (GBR) and
non-GBR services are running and
unevenly distributed, the QoS of
GBR services is affected by hybrid
scheduling.

eRAN

Name Switch
Service-based PreemptionSw Admission and In adaptive SFN/SDMA scenarios,

radio resource itch option of Congestion when the cell load is relatively
preemption the Control heavy, there will be both a large
CellAlgoSwitc number of independently
h.RacAlgoSwit scheduled UEs and a large number
ch parameter of jointly scheduled UEs. If both
these services are unevenly
distributed, the QoS of GBR
services is affected by hybrid
scheduling.
Transport TACALG.TR Transport In adaptive SFN/SDMA scenarios,

resource MULPRESW Resource when the cell load is relatively
preemption TACALG.TR Management heavy, there will be both a large
MDLPRESW number of independently
scheduled UEs and a large number
of jointly scheduled UEs. If both
these services are unevenly
distributed, the QoS of GBR
services is affected by hybrid
scheduling.
Downlink FreqSelSwitch Scheduling Since CRSs are jointly transmitted

frequency option of the by all RRUs in an SFN cell, the
selective CellAlgoSwitc subband channel quality indicated
scheduling h.DlSchSwitch by the obtained subband CQI
parameter deviates from that in the actual
scheduling for some jointly or
independently scheduled UEs,
which affects frequency selective
scheduling.
Preferential use CellDlschAlgo. Scheduling Preferential use of resource

of resource RbgAllocStrate allocation type 1 does not take
allocation type gy effect for independently scheduled
1 UEs in SFN cells.

eRAN

Name Switch
Uplink l EuCoSchU UL ICS (TDD) In the IP RAN Cloud BB

interference LICSCfg.Ul scenarios, a cell cannot be added
coordination IcsAlgoSwit to the cluster if the
ch CellAlgoSwitch.SfnUlSchSwitch
l NCellSrsM parameter is set to ADAPTIVE
easPara.Srs for the cell.
AutoNCell
MeasSwitch
l UL_ICS_S
WITCH of
the
CellAlgoSw
itch.UlIcSw
itch
parameter
Multi-band MbfcsSwitch Multi-band When adaptive SFN/SDMA is in

optimal carrier option of the Optimal use, the error in the gain
selection CellAlgoSwitc Carrier estimation for handovers to or
h.MlbAlgoSwit Selection from SFN cells increases.
ch parameter Therefore, the benefits derived
from MBOCS in this situation are
reduced.
eMTC EMTC_SWIT eMTC When adaptive SFN/SDMA is

introduction CH option of enabled, joint scheduling is always
the used for eMTC UEs.
CellEmtcAlgo.
EmtcAlgoSwitc
h parameter
10.3 Requirements
10.3.1 Licenses
TDLOFD-002008 Adaptive SFN/ LT1SADASFN00 Per Cell

SDMA

eRAN
10.3.2 Software

Downlink CellAlgoSwitch.InterfRandSwitch ICIC

interference
randomization
Uplink interference CellUlschAlgo.UlRbAllocationStrategy ICIC

randomization
10.3.3 Hardware
Base Station Models


Boards
RF Modules
Hardware.
10.3.4 Others
None

eRAN

For the parameters used for activation, see the "Data Preparation" section in 6 SFN (TDD).
Table 10-1 describes the parameters that are set differently for the activation of this function.
Table 10-2 describes the parameters used for optimization.

Name
SFN UL CellAlgoSwitc It is recommended that this parameter be set to

Scheduling h.SfnUlSchSwi ADAPTIVE. If this parameter is set to ADAPTIVE,
Switch tch it is recommended that the SchedulerCtrlPowerS-
witch option of the CellAlgoSwitch.UlSchSwitch
parameter be selected.
SFN DL CellAlgoSwitc ADAPTIVE

Switch tch

Name
SFN Load- CellAlgoSwitc N/A None

based Adaptive h.SfnLoadBase
Switch dAdptSwitch
SFN Algorithm CellAlgoSwitc SfnDlSchAttri This option is valid only when the
Switch h.SfnAlgoSwitc AdjsSwitch SfnDl2LoadLevelAdptSwitch
h option is selected.
CellAlgoSwitc SfnVoLteDlJSc It is recommended that this option

CellAlgoSwitc SfnVoLteUlJSc It is recommended that this option

CellAlgoSwitc SfnDlRblerOp It is recommended that this option

h.SfnAlgoSwitc tSwitch be selected when the
CellAlgoSwitc SfnDl2LoadLe This option is valid only when

h.SfnAlgoSwitc velAdptSwitch CellAlgoSwitch.SfnLoadBasedAd
h ptSwitch is set to ON.

eRAN

Name
SFN Downlink CellDlschAlgo. N/A None

Load Period SfnDlLoadPeri
od

High Load SfnDlHighLoa
Threshold dThd

Low Load SfnDlLowLoad
Threshold Thd
Downlink High CellDlschAlgo. N/A Set this parameter to its

Load SDMA DlHighLoadSd recommended value.
Offset the
Downlink Low CellDlschAlgo. N/A Set this parameter to its

Load SDMA DlLowLoadSd recommended value.
Offset the
SFN Uplink CellUlschAlgo. N/A None

Load Period SfnUlLoadPeri
od

Setting the adaptive scheduling mode
MOD CELLALGOSWITCH: LOCALCELLID=0, SFNULSCHSWITCH=ADAPTIVE,
SFNDLSCHSWITCH=ADAPTIVE, UlSchSwitch=SchedulerCtrlPowerSwitch-1;

Setting the load-based adaptive adjustment switch for adaptive SFN/SDMA
MOD CELLALGOSWITCH: LOCALCELLID=0, SFNLOADBASEDADPTSWITCH=ON;
Setting the downlink load measurement period, downlink heavy-load threshold, downlink
light-load threshold, and isolation degree decision threshold offset of downlink heavy-load
level for the SFN cell
MOD CELLDLSCHALGO: LOCALCELLID=0, SfnDlLoadPeriod =30,SfnDlHighLoadThd=
50,SfnDlLowLoadThd=20,DlHighLoadSdmaThdOffset=2;
Setting the uplink load measurement period for the SFN cell

eRAN
MOD CELLULSCHALGO: LOCALCELLID=0, SfnUlLoadPeriod =1800;

Setting the SFN uplink and downlink scheduling switches for deactivating adaptive SFN


The activation verification method for this function is the same as that for the SFN function.
For details, see 6.4.2 Activation Verification.


eRAN
SFN Feature Parameter Description 11 Inter-BBP SFN (FDD)
11.1 Principles
An inter-BBP SFN cell consists of physical cells that are deployed on different BBPs (which
can be of the same type or different types). In Figure 11-1 where BBU3900 is used as an
example, SFN cell 2 consists of three physical cells. The physical cells served by RRU 4 and
RRU 5 are deployed on BBP 1, and the physical cell served by RRU 6 is deployed on BBP 2.
This inter-BBP SFN deployment mode minimizes the changes in physical connections
between RRUs and BBUs during SFN network reconstruction, reducing the need for on-site
O&M.
Figure 11-1 Inter-BBP SFN cell
For an inter-BBP SFN cell, the primary BBP processes both Layer-2 and Layer-1 data but the
secondary BBPs process only Layer-1 data. Layer-1 data of each RRU is processed on the
connected BBP, which can be the primary or secondary BBP. Layer-2 data of all RRUs is
processed only on the primary BBP.
When an inter-BBP SFN cell is activated, the eNodeB automatically selects a BBP as the
primary BBP of the inter-BBP SFN cell. After the SFN cell is activated, the details of the
primary BBP can be queried by running the DSP CELL command.

eRAN
If RRUs and pRRUs (or RRUs and pRRU groups) are combined to serve an SFN cell, this
SFN cell must be an inter-BBP SFN cell. The sets of sector equipment and the sector
equipment groups must be deployed on different BBPs. To combine RRUs and pRRUs (or
RRUs and pRRU groups) to serve an SFN cell, set the Cell.MultiRruCellMode parameter to
SFN.
11.2.1 Benefits
The benefits of this function are the same as those of the SFN function. For details, see 5.2.1
Benefits.
11.2.2 Impacts
Network Impacts
If RRUs and pRRUs (or RRUs and pRRU groups) are combined to serve an SFN cell, the
uplink initial transmit power of UEs served by the macro eNodeBs will increase and therefore
uplink interference will also increase.
Other impacts are the same as those of the SFN function. For details, see 5.2.2 Impacts.
Function Impacts
None
11.3 Requirements
11.3.1 Licenses
None
11.3.2 Software

None

eRAN
11.3.3 Hardware
Base Station Models


l BTS3912E
l BTS3911E

l BTS3912E
l BTS3911E
Boards
When the BBPs involved in an inter-BBP SFN cell reside in the same BBU3900, at least one
BBP must be installed in slot 2 or 3 of the BBU.
RF Modules
If RRUs and pRRUs (or RRUs and pRRU groups) are combined to serve an SFN cell, the
TX/RX mode of the RRUs can be set to 1T1R or 2T2R.
Other requirements are the same as those of the SFN function. For details, see 5.3.3
Hardware.
Cells
An inter-BBP SFN cell has the following requirements for inter-BBP uplink and downlink
transmission bandwidths:
l 2T2R, 2T4R, or 4T4R cells: 600 Mbit/s

l 1T1R cells: 500 Mbit/s
NOTE
For NB-IoT, when inter-BBP cells are combined to form an SFN cell, the required inter-BBP
uplink and downlink transmission bandwidths are 10 Mbit/s.
11.3.4 Networking
Two BBPs in a BBU3900 support a maximum of eight inter-BBP physical cells, such as those
served by RRU 6 and RRU 7 shown in Figure 11-1.
If RRUs and pRRUs (or RRUs and pRRU groups) are combined to serve an SFN cell and the
member physical cells include a 2T2R cell, this 2T2R member physical cell can be served by
a combination of two 1T1R RRUs but not the combination of an RRU and a pRRU (or an
RRU and a pRRU group).

eRAN
The MAC layer resources of an SFN cell must be deployed on only one BBP. You can run the
ADD EUCELLPRIBBEQM or MOD EUCELLPRIBBEQM command to map the MAC
layer resources to a BBP, and run the DSP CELL command to query the BBP where the
MAC layer resources are deployed. For the maximum number of physical cells supported by
the MAC layer, see Table 11-1 and Table 11-2. An SFN cell will fail to be set up if the
number of physical cells to be processed by the MAC layer exceeds the maximum number.
Table 11-1 (For FDD) Maximum number of physical cells supported by the MAC layer
BBP Maximum Number of FDD Physical
Cells Supported by the MAC Layer
LBBPd3, LBBPd5, GSM&LTE dual-mode Equal to the number of FDD physical cells
UBBPd3, or GSM&LTE dual-mode supported by Layer 1
UBBPd4
UBBPd5, UBBPd6, UBBPe3, UBBPe4, Equal to 1.5 times the number of FDD
UBBPe5, UBBPe6, or UBBPei physical cells supported by Layer 1
NOTE
If the calculated number is not an integer, it is
rounded down to the nearest integer.
LBBPd1, LBBPd2, single-mode UBBPd3, Equal to 2 times the number of FDD

single-mode UBBPd4, UBBPe1, or physical cells supported by Layer 1
UBBPe2
Table 11-2 (For NB-IoT) Maximum number of physical cells supported by the MAC layer
Applicable BBP Maximum Number of NB-IoT
RAT Physical Cells Supported by
the MAC Layer
NB-IoT LBBPd1, LBBPd2, LBBPd3, 12

LBBPd5, UBBPd3, or UBBPd4
NB-IoT UBBPd5 or UBBPd6 15
NB-IoT UBBPe1, UBBPe2, UBBPe3, or 18

UBBPe4
NB-IoT UBBPe5 or UBBPe6 24

eRAN

the MAC Layer
LM (indicating l LBBPd1, LBBPd2, UBBPd3, Equal to 2 times the number of NB-

FDD+NB-IoT) or UBBPd4 IoT physical cells supported by
l LBBPd3 or LBBPd5: Layer 1
Three 20 MHz 2T2R cells +
three 10 MHz 2T2R cells +
three 200 kHz 2T2R cells
l LBBPd5:
l UBBPd5:
three 10 MHz 2T2R cells +
l UBBPd6:
Three 20 MHz 4T4R FDD
cells + three 10 MHz 4T4R
FDD cells + three 200 kHz
4T4R NB-IoT cells
LM (indicating l UBBPd5: Equal to 1.5 times the number of

FDD+NB-IoT) Three 20 MHz 2T2R cells + NB-IoT physical cells supported by
three 400 kHz 2T2R cells Layer 1
l UBBPd6: NOTE
Three 20 MHz 4T4R cells + If the calculated number is not an
integer, it is rounded down to the
nearest integer.
l UBBPe1, UBBPe2, UBBPe3,
UBBPe4, or UBBPe5
LM (indicating l LBBPd3 or LBBPd5: Equal to the number of NB-IoT

FDD+NB-IoT) Three 20 MHz 2T2R cells + physical cells supported by Layer 1
l UBBPe6
UM (indicating UBBPd6 Equal to 2 times the number of NB-

UMTS+NB-IoT) IoT physical cells supported by
Layer 1
UM (indicating UBBPe3, UBBPe4, UBBPe5, or Equal to 1.5 times the number of

UMTS+NB-IoT) UBBPe6 NB-IoT physical cells supported by
Layer 1
NOTE
If the calculated number is not an
nearest integer.

eRAN

the MAC Layer
ULM (indicating UBBPd6, UBBPe3, UBBPe4, Equal to 1.5 times the number of
UMTS+FDD UBBPe5, or UBBPe6 NB-IoT physical cells supported by
+NB-IoT) Layer 1
NOTE
nearest integer.
TM (indicating UBBPe6 Equal to the number of NB-IoT

TDD+NB-IoT) physical cells supported by Layer 1
TM (indicating UBBPe4 Equal to 1.5 times the number of

TDD+NB-IoT) NB-IoT physical cells supported by
Layer 1
NOTE
nearest integer.
One NB-IoT carrier corresponds to one NB-IoT physical cell at Layer 1.

If a cell number specification is provided for a BBP, the corresponding number indicated in
the last column of the preceding table is applicable only to this specification. If no cell
number specification is provided for a BBP, the corresponding number indicated in the last
column is applicable to any combination of cell number specifications of the BBP. For details
about the cell number specifications of each BBP, see 3900 Series Base Station Technical
Description.
If any physical or common cell on a BBP serving an inter-BBP SFN cell is bound to baseband
equipment, all other cells on this BBP and all the cells on other BBPs serving this inter-BBP
SFN cell must be bound to baseband equipment. This will prevent the failure of baseband
resource allocation in some cells as a result of baseband equipment conflicts between
automatic and manual baseband equipment binding. The following are the related MML
commands:
l The ADD BASEBANDEQM command is used to configure baseband equipment.
l The ADD EUCELLSECTOREQM command is used to bind the cells served by RRUs
or RFUs to baseband equipment.
l The ADD EUSECTOREQMGROUP command is used to bind the cells served by
pRRU groups to baseband equipment.
In inter-BBP SFN scenarios, the primary baseband equipment needs to be bound to the SFN
cell, the remaining primary BBP resources need to be queried, and the primary BBP resources
need to be queried and adjusted. The following describes the restrictions on these processes.
Binding the Primary Baseband Equipment

primary BBP of the inter-BBP SFN cell.

eRAN
When the ADD EUCELLPRIBBEQM, MOD EUCELLPRIBBEQM, or MOD

BASEBANDEQM command is executed and the primary baseband equipment differs from
that to be bound, the SFN cell will be reestablished. Exercise caution before running these
commands.
NOTE
l If an SFN cell has been bound to primary baseband equipment, only a BBP in the primary baseband
equipment can be selected as the primary BBP of the SFN cell. If an SFN cell has not been bound to
primary baseband equipment, only a BBP not bound to any SFN cell can be selected as the primary
BBP of the SFN cell.
l If any of the cells configured on an eNodeB needs to be bound to primary baseband equipment, it is
recommended that all the cells configured on the eNodeB be bound to primary baseband equipment.
If the recommendation is not implemented, a large number of primary BBP resource fragments exist
and the activation of some cells may fail.
After the SFN cell is activated, the details of the primary BBP can be queried by running the
DSP CELL command.
Query of the Remaining Primary BBP Resources

Before expanding capacity, confirm that there are enough primary BBP resources. If there are
not, the expansion may fail. You can query information about the primary BBP resources by
running the DSP PRIBBPRESINFO command.
NOTE
The command only returns information of BBPs configured with at least one cell. For BBPs with no
cells configured, capacity expansion must be performed based on BBP processing capabilities.
Query and Adjustment of Primary BBP Resources

When an eNodeB allocates primary BBP resources, the allocation may fail. If the allocation
fails, run the DSP PRIBBPADJUST and STR PRIBBPADJUST commands to adjust
primary BBP resources while ensuring that the number of cells deactivated is the least.
NOTE
If primary BBP resources fail to be allocated to multiple cells or if cells that do not require primary BBP
resource adjustment are faulty, deactivate these faulty cells and then adjust and activate the cells that
require primary BBP resource adjustment one by one until adjustment is completed for all the cells
served by the eNodeB.
Table 11-3 Restrictions on querying and adjusting primary BBP resources
Item Description
Application Network capacity is expanded.

scenarios
Prerequisites l The CPU usage is lower than 50%. The adjustment will increase the
CPU usage.
l Cells other than those that require primary BBP resource adjustment
are all activated and all BBPs are available.

eRAN
Item Description
Requirements l The DSP PRIBBPADJUST and STR PRIBBPADJUST commands

for the query cannot be run simultaneously. Otherwise, a message indicating
and adjustment command execution failure is displayed.
process l Configuration data cannot be added, modified, or deleted in the
adjustment process. Otherwise, the STR PRIBBPADJUST
command execution process is aborted.
l If the eNodeB fails to obtain a resource allocation solution within 30
minutes after the STR PRIBBPADJUST command is run, the
search times out. In this case, adjust SFN networking based on BBP
capabilities.
NOTE
During the adjustment, the algorithm for adjusting primary BBP resources is used.
If the resource allocation solution recommended by the algorithm for adjusting
primary BBP resources does not meet the rules used by the algorithm for pre-
allocating primary BBP resources, the number of inter-BBP cells increases,
leading to a high inter-BBP bandwidth usage.
11.3.5 Others
None

The data preparation for this function is the same as that for the SFN function. For details, see
5.4.1.1 Data Preparation.

When only RRUs or pRRUs are combined to serve an SFN cell, the commands used are the
same as those for the SFN function. For details, see 5.4.1.2 Using MML Commands.
The following provides an example for SFN deployment using RRUs and pRRUs (or RRUs
and pRRU groups).
RRUs and pRRUs (or pRRU groups) support different CPRI compression types. If the
physical cells of an SFN cell are served by RRUs and pRRUs (or RRUs and pRRU groups),
the CPRI compression type of each physical cell must be set in the ADD
EUCELLSECTOREQM and ADD EUSECTOREQMGROUP commands.
The following assumes that an SFN cell is served by two RRUs and a sector equipment group
with four pRRUs. The parameter values serve as examples only and should be adjusted as
required.
Adding sectors for RRUs

eRAN
ADD
ADD
Adding sectors for pRRUs in a pRRU group

Adding an SFN cell

ADD CELL: LocalCellId=0, CellName="FDD_SFN", NBCELLFLAG=FALSE, FreqBand=7,
MultiRruCellFlag=BOOLEAN_TRUE, MultiRruCellMode=SFN, SectorEqmNum=3,
TxRxMode=2T2R;

Adding the mapping relationship between the cell and sector equipment
ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0, ReferenceSignalPwr=182;
ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=1, ReferenceSignalPwr=182;
ADD EUSECTOREQMGROUP: LocalCellId=0, SectorEqmGroupId=0, ReferenceSignalPwr=-78;

Activating the cell


The CME-based configuration for this function is the same as that for the SFN function. For
details, see 5.4.1.3 Using the CME.

For details, see 5 SFN (FDD).

details, see 5 SFN (FDD).

eRAN
SFN Feature Parameter Description 12 Inter-BBP SFN (TDD)
12 Inter-BBP SFN (TDD)
12.1 Principles
An inter-BBP SFN cell consists of physical cells that are deployed on different BBPs (which
can be of the same type or different types). In Figure 12-1 where BBU3900 is used as an
example, SFN cell 2 consists of three physical cells. The physical cells served by RRU 4 and
RRU 5 are deployed on BBP 1, and the physical cell served by RRU 6 is deployed on BBP 2.
This inter-BBP SFN deployment mode minimizes the changes in physical connections
between RRUs and BBUs during SFN network reconstruction, reducing the need for on-site
O&M.
Figure 12-1 Inter-BBP SFN cell
For an inter-BBP SFN cell, the primary BBP processes both Layer-2 and Layer-1 data but the
secondary BBPs process only Layer-1 data. Layer-1 data of each RRU is processed on the
connected BBP, which can be the primary or secondary BBP. Layer-2 data of all RRUs is
processed only on the primary BBP.
primary BBP of the inter-BBP SFN cell. After the SFN cell is activated, the details of the
primary BBP can be queried by running the DSP CELL command.

eRAN
12.2.1 Benefits
The benefits of this function are the same as those of the SFN function. For details, see 7.2.1-
Benefits.
12.2.2 Impacts
Network Impacts
The network impacts of this function are the same as those of the SFN function. For details,
see 6.2.2 Impacts.
Function Impacts
Function Name Function Switch Reference Description
Uplink-downlink Cell.SubframeAssig Subframe Type 1 is not

subframe nment Configuration supported.
configuration (TDD)
type1&2
12.3 Requirements
12.3.1 Licenses
TDLOFD-001098 Inter-BBP SFN LT1SBBPSFN00 per BBU
12.3.2 Software

None

eRAN
12.3.3 Hardware
Base Station Models


Boards
BBPs can be combined in LBBPc-only, LBBPd-only, UBBP-only, LBBPc+LBBPd, or
LBBPd+UBBP mode for an SFN cell. Table 12-1 describes BBP combination switching and
the impact of switching on an inter-BBP SFN cell.
Table 12-1 BBP combination switching and the impact of switching on an inter-BBP SFN
cell
BBP BBP Combination After Whether the SFN Cell Needs to Be

Combination Switching Re-established
Before
Switching
LBBPc only LBBPc only No
LBBPc only LBBPd only, UBBP only, Yes (The cell is re-established
or LBBPd+UBBP immediately.)
LBBPc only LBBPc+LBBPd Yes (The cell is re-established

immediately.)
LBBPd only, LBBPc only Yes (The cell is re-established

UBBP only, or immediately.)
LBBPd+UBBP
LBBPd only, LBBPd only, UBBP only, No

UBBP only, or or LBBPd+UBBP
LBBPd+UBBP
LBBPd only, LBBPc+LBBPd Yes (The cell is re-established

UBBP only, or immediately.)
LBBPd+UBBP
LBBPc+LBBPd LBBPc only Yes (The cell is re-established in the

wee hours when there are no users on
the network.)
LBBPc+LBBPd LBBPd only, UBBP only, Yes (The cell is re-established in the
or LBBPd+UBBP wee hours when there are no users on
the network.)
LBBPc+LBBPd LBBPc+LBBPd No

eRAN
RF Modules
Hardware.
Cells
None
12.3.4 Networking
Inter-BBP SFN supports only uplink-downlink configuration 2 and special subframe
configuration 7.
When four or more RRUs are used to serve an inter-BBP SFN cell, the BBPs for this SFN cell
must not be only LBBPc boards.
The MAC resources of an SFN cell must be deployed on only one BBP. For details about the
logical cell specifications supported by the MAC layer, see Table 12-2.
Table 12-2 Logical cell specifications supported by the MAC layer
BBP Model Specification
LBBPc When the cell bandwidth is 20 MHz: One cell served by one to three
RRUs
When the cell bandwidth is 10 MHz:
l One cell served by two or three RRUs
l Three cells each served by one RRU
l One cell served by two RRUs + one cell served by one RRU
LBBPd When the cell bandwidth is 10 or 20 MHz:

l Three cells each served by one or two RRUs
l One cell served by four RRUs + one cell served by one or two RRUs
l One cell served by three RRUs + one cell served by one to three
RRUs
l One cell served by five to seven RRUs
UBBPd4/ When the cell bandwidth is 10 or 20 MHz:

UMDUa1 l Three cells each served by one or two RRUs
l One cell served by four RRUs + one cell served by one or two RRUs
l One cell served by three RRUs + one cell served by one to three
RRUs
l One cell served by five to seven RRUs
UBBPd6/ When the cell bandwidth is 10 or 20 MHz, any combination of cell

UBBPd9/ configurations is supported if there are no more than 6 cells and no more
UBBPe4/ than 9 RRUs.
UMDUa3

eRAN
BBP Model Specification
UBBPei When the cell bandwidth is 10 or 20 MHz, any combination of cell

configurations is supported if there are no more than 12 cells and no more
than 15 RRUs.
If any physical or common cell on a BBP serving an inter-BBP SFN cell is bound to baseband
equipment, all other cells on this BBP and all the cells on other BBPs serving this inter-BBP
SFN cell must be bound to baseband equipment. This will prevent the failure of baseband
resource allocation in some cells as a result of baseband equipment conflicts between
automatic and manual baseband equipment binding. The following are the related MML
commands:
l The ADD BASEBANDEQM command is used to configure baseband equipment.

l The ADD EUCELLSECTOREQM command is used to bind the cells served by RRUs
to baseband equipment.
l The ADD EUSECTOREQMGROUP command is used to bind the cells served by
pRRU groups to baseband equipment.
If the BBU configured with an SFN cell houses LBBPc and other types of BBPs, Layer 1
must be bound to one of the BBPs and Layer 2 must be bound to baseband equipment based
on the cell bandwidth before the SFN cell can be activated.
If the BBU does not house any LBBPc, layer 1 and layer 2 need to be bound to baseband
equipment based on the cell bandwidth.
In inter-BBP SFN scenarios, the primary baseband equipment needs to be bound to the SFN
cell, the remaining primary BBP resources need to be queried, and the primary BBP resources
need to be queried and adjusted. The following describes the restrictions on these processes.
Binding the Primary Baseband Equipment

primary BBP of the inter-BBP SFN cell.
When the ADD EUCELLPRIBBEQM, MOD EUCELLPRIBBEQM, or MOD

BASEBANDEQM command is executed and the primary baseband equipment differs from
that to be bound, the SFN cell will be reestablished. Exercise caution before running these
commands.
NOTE
l If an SFN cell has been bound to primary baseband equipment, only a BBP in the primary baseband
equipment can be selected as the primary BBP of the SFN cell. If an SFN cell has not been bound to
primary baseband equipment, only a BBP not bound to any SFN cell can be selected as the primary
BBP of the SFN cell.
l If any of the cells configured on an eNodeB needs to be bound to primary baseband equipment, it is
recommended that all the cells configured on the eNodeB be bound to primary baseband equipment.
If the recommendation is not implemented, a large number of primary BBP resource fragments exist
and the activation of some cells may fail.
After the SFN cell is activated, the details of the primary BBP can be queried by running the
DSP CELL command.

eRAN
Query of the Remaining Primary BBP Resources

Before expanding capacity, confirm that primary BBP resources are sufficient. If they are not,
the expansion may fail. You can query information about the primary BBP resources by
running the DSP PRIBBPRESINFO command.
NOTE
l Only information about the remaining primary BBP resources of common 8T8R cells, common
4T4R cells, common 2T2R cells, SFN cells (a combination of 8T8R, 4T4R, 2T2R, 4T4R+8T8R,
4T4R+2T2R, 8T8R+2T2R, or 4T4R+8T8R+2T2R cells), and LampSite cells can be queried.
l The query results contain only information of the BBPs configured with at least one cell. For BBPs
not configured with cells, capacity expansion must be performed based on BBP processing
capabilities.
Query and Adjustment of Primary BBP Resources

When an eNodeB allocates primary BBP resources, the allocation may fail. Therefore, after
capacity expansion, the DSP PRIBBPADJUST and STR PRIBBPADJUST commands need
to be executed to adjust primary BBP resources while ensuring that the number of cells
deactivated is the least.
NOTE
If primary BBP resources fail to be allocated to multiple cells or if cells that do not require primary BBP
resource adjustment are faulty, deactivate these faulty cells and then adjust and activate the cells that
require primary BBP resource adjustment until adjustment is completed for all the cells served by the
eNodeB.
Table 12-3 Restrictions on querying and adjusting primary BBP resources

Item Description
Application l Network capacity is expanded.

scenarios l Primary BBP resources fail to be allocated for the adjustment cell.
l Primary BBP resources of only 8T8R cells, 4T4R cells, 2T2R cells,
SFN cells, and LampSite cells can be queried and adjusted.
l Primary BBP resources on the UBBPe board cannot be queried or
adjusted.
Prerequisites l The CPU usage is lower than 50%. The adjustment will increase the
CPU usage.
l Cells other than those requiring primary BBP resource adjustment are
all activated and all BBPs are available.

eRAN
Item Description
Requirements l Primary BBP resources can be adjusted only within the primary BBP
for the query group.
and adjustment l The DSP PRIBBPADJUST and STR PRIBBPADJUST commands
process cannot be run simultaneously. Otherwise, a message indicating
command execution failure is displayed.
l Configuration data cannot be added, modified, or deleted in the
adjustment process. Otherwise, the STR PRIBBPADJUST command
execution process is aborted.
l If the eNodeB fails to obtain a resource allocation solution within 30
minutes after the STR PRIBBPADJUST command is run, the search
times out. In this case, adjust SFN networking based on BBP
capabilities.
NOTE
During the adjustment, the algorithm for adjusting primary BBP resources is used.
If the resource allocation solution recommended by the algorithm for adjusting
primary BBP resources does not meet the rules used by the algorithm for pre-
allocating primary BBP resources, the number of inter-BBP cells increases, leading
to a high inter-BBP bandwidth usage.
12.3.5 Others
None

The data preparation for this function is the same as that for the SFN function. For details, see
6.4.1.1 Data Preparation.
If an SFN cell is served by RRUs connected to both LBBPc and LBBPd or to both LBBPc
and UBBP and the PUCCHCFG.DeltaShift parameter is set to DS1_DELTA_SHIFT, the
parameter value will be automatically changed to DS2_DELTA_SHIFT after the SFN cell is
activated.

The activation method for this function is the same as that for the SFN function. For details,
see 6.4.1.2 Using MML Commands.

eRAN

N/A




eRAN
SFN Feature Parameter Description 13 Inter-BBP Adaptive SFN/SDMA (FDD)
13 Inter-BBP Adaptive SFN/SDMA (FDD)
13.1 Principles
Inter-BBP adaptive SFN/SDMA works with the SFN, adaptive SFN/SDMA, and inter-BBP
SFN functions. It allows inter-BBP RRUs to be combined to serve an adaptive SFN cell.
13.2.1 Benefits
The benefits of this function are the same as those of the adaptive SFN/SDMA function. For
details, see 9.2.1 Benefits.
13.2.2 Impacts
Network Impacts
The network impacts of this function are the same as those of the adaptive SFN/SDMA
function. For details, see 9.2.2 Impacts.
Function Impacts
None
13.3 Requirements
13.3.1 Licenses
None

eRAN
13.3.2 Software
Adaptive SFN/SDMA l CellAlgoSwitch.SfnUlS SFN

chSwitch
l CellAlgoSwitch.SfnDlS
chSwitch
Inter-BBP SFN None SFN

None
13.3.3 Hardware
This function requires the same hardware as the SFN and inter-BBP SFN functions. For
details, see 5.3.3 Hardware and 11.3.3 Hardware.
13.3.4 Others
None

The data preparation for this function is the same as that for the adaptive SFN/SDMA
function. For details, see 9.4.1.1 Data Preparation.

The MML-based configuration for this function is the same as that for the adaptive SFN/
SDMA function. For details, see 9.4.1.2 Using MML Commands.


eRAN

The activation verification method for this function is the same as that for the adaptive SFN/
SDMA function. For details, see 9 Adaptive SFN/SDMA (FDD).

The network monitoring method for this function is the same as that for the adaptive SFN/
SDMA function. For details, see 9 Adaptive SFN/SDMA (FDD).

eRAN
SFN Feature Parameter Description 14 Inter-BBP Adaptive SFN/SDMA (TDD)
14 Inter-BBP Adaptive SFN/SDMA (TDD)
14.1 Principles
Inter-BBP adaptive SFN/SDMA works with the SFN, adaptive SFN/SDMA, and inter-BBP
SFN functions. It allows inter-BBP RRUs to be combined to serve an adaptive SFN cell.
14.2.1 Benefits
14.2.2 Impacts
Network Impacts
Function Impacts
None
14.3 Requirements

eRAN
14.3.1 Licenses
TDLOFD-001081 Inter-BBP LT1SBBPADA00 per BBU

Adaptive SFN/
SDMA
14.3.2 Software

chSwitch
chSwitch

None
14.3.3 Hardware
This function requires the same hardware as the SFN and inter-BBP SFN functions. For
details, see 6.3.3 Hardware and 12.3.3 Hardware.
14.3.4 Others
None

The data preparation for this function is the same as that for the adaptive SFN/SDMA
function. For details, see 10.4.1.1 Data Preparation.

eRAN

SDMA function. For details, see Activation Command Examples.


The activation verification method for this function is the same as that for the adaptive SFN/
SDMA function. For details, see 10.4.2 Activation Verification.

SDMA function. For details, see 10.4.3 Network Monitoring.

eRAN 15 Inter-eNodeB SFN Based on eNodeB Coordination
SFN Feature Parameter Description (FDD)
15 Inter-eNodeB SFN Based on eNodeB

Coordination (FDD)
15.1 Principles
Physical cells in an SFN cell can belong to the same BBU or different BBUs. If physical cells
belong to different BBUs, the BBUs must be deployed using a Cloud BB architecture. The
function used to combine physical cells belonging to different BBUs to form an SFN cell is
inter-eNodeB SFN based on eNodeB coordination. In the following descriptions, this function
is called inter-eNodeB SFN.
During the combination of physical cells belonging to different BBUs to form an SFN cell,
the inter-eNodeB SFN function minimizes the changes in physical connections between
RRUs and BBUs, reducing the number of site visits required and simplifying network
operations and maintenance.
Network Planning
Different BBUs are interconnected through a universal switching unit (USU), as shown in
Figure 15-1.
Only the USU3910 allows RRUs connected to different BBUs to constitute an SFN cell.

Figure 15-1 Inter-eNodeB SFN networking based on eNodeB coordination
An inter-eNodeB SFN cell is set up on one of the BBUs. This BBU is referred to as the
primary BBU or the primary eNodeB of the SFN cell. The other BBUs are auxiliary BBUs or
auxiliary eNodeBs. The physical cells on an auxiliary eNodeB that constitute the SFN cell are
referred to as auxiliary cells.
The BBPs in the primary BBU are called primary BBPs. After a cell is activated, the primary
BBP of the cell can be queried by running the DSP CELL command on the primary BBU.
To create an SFN cell by running the ADD CELL command on the primary eNodeB, set the
Cell.EuCellStandbyMode parameter to ACTIVE.
Reliability
To ensure that service provisioning continues even if all the physical cells of an SFN cell
unexpectedly stop working, operators can configure a standby cell on an auxiliary eNodeB to
increase reliability. A standby cell can be added by running the ADD CELL command with
the Cell.EuCellStandbyMode parameter set to STANDBY on an auxiliary eNodeB. A
standby cell can be an SFN cell or a common cell.
A standby cell is automatically activated for service provisioning when any of the following
faults persists for up to 4 minutes:
l The control-plane link between the primary and auxiliary eNodeBs is interrupted.
l The data links between the primary and auxiliary eNodeBs are not working properly.
If this happens, engineers need to run the RST SFNAUXRES command to restore the
services in the auxiliary cells. The standby cell is activated only if data links to all RRUs
on the auxiliary eNodeBs are faulty.

l The primary BBPs are faulty.

If this happens, the primary eNodeB will attempt to allocate new primary BBPs for the
SFN cell. If the allocation is successful, the fault is rectified. If the allocation fails, the
primary eNodeB will deactivate the SFN cell and the RRUs on the auxiliary eNodeBs
will be automatically switched to the standby cell to ensure service continuity.
l The primary eNodeB does not transmit data properly.
l The main control board of the primary eNodeB is faulty.
l The SFN cell configured on the primary eNodeB has been unexpectedly deactivated.
l The clock accuracy deviation of the primary or auxiliary eNodeB exceeds 1.5 μs.
After a fault is rectified, the standby cell is automatically deactivated. The RRUs of auxiliary
eNodeBs are automatically switched to the SFN cell to ensure service continuity. The
Cell.StandbyCellSfnRecoveTime parameter specifies the automatic SFN recovery time of
inter-BBU cells on auxiliary BBUs after related SFN faults are rectified.
NOTE
l When the inter-BBU control-plane link is functional, the operating frequency of the standby cell
must be the same as that of the SFN cell configured on the primary BBU. Otherwise, the standby
cell cannot be activated.
l If local resources on auxiliary eNodeBs are abnormal, a standby cell cannot be set up.
l An inter-eNodeB SFN cell cannot serve as a standby cell.
l A standby cell that has been successfully activated cannot be activated again within 10 minutes after
an upgrade or reset of the eNodeB.
l If automatic neighbor relation (ANR) is not activated, neighboring cells must be configured for the
standby cell when the standby cell is added.
15.2.1 Benefits
Benefits.
15.2.2 Impacts
Network Impacts
see 5.2.2 Impacts.

Function Impacts
Name Switch
Downlink 4x4 Tm3Tm4Max4 MIMO If the

MIMO LayerCtrlSwit Tm3Tm4Max4LayerCtrlSwitch
ch option of the option of the
eNodeBAlgoS ENodeBAlgoSwitch.Compatibilit
witch.Compati yCtrlSwitch parameter is selected
bilityCtrlSwitch for a cell with inter-eNodeB SFN
parameter based on eNodeB coordination
enabled and some physical cells of
this SFN cell are served by
eNodeBs of versions earlier than
eRAN11.1, the demodulation
performance of UEs of CAT6 or
higher that support TM3/TM4 4-
layer MIMO will deteriorate in the
joint scheduling area, reducing
User Downlink Average
Throughput.
It is recommended that the
Tm3Tm4Max4LayerCtrlSwitch
option be deselected or that all
eNodeBs be upgraded to
eRAN11.1 or a later version.
UL CoMP cell UlJointRecepti UL CoMP UL CoMP can work with inter-

onSwitch eNodeB SFN based on eNodeB
option of the coordination on a centralized
CellAlgoSwitc Cloud BB network, but cannot on
h.UplinkComp a distributed Cloud BB network.
Switch
parameter
15.3 Requirements
15.3.1 Licenses
LOFD-081208 Inter-eNodeB LT1SISFNBC0 Per eNodeB

SFN Based on 0
Coordinated
eNodeB
If the licenses of both the primary and auxiliary BBUs do not meet service requirements,
ALM-26819 Data Configuration Exceeding Licensed Limit is reported only on the primary

BBU. If the licenses of the primary BBU meet service requirements but those of the auxiliary
BBU do not, this alarm is reported on the auxiliary BBU.
15.3.2 Software

Name
Low power CellLowPower.L Energy None

consumption owPwrSwitch Conservation
mode and Emission
Reduction
Dynamic CellAlgoSwitch.D Energy None

voltage ynAdjVoltSwitch Conservation
adjustment and Emission
Reduction
Ultra high Cell.HighSpeedFl High Speed None

speed mobility ag Mobility
Flexible DdCellGroup.Dd Flexible None

bandwidth BandWidth Bandwidth
based on based on
overlapping Overlap
carriers Carriers (FDD)
GSM and LTE GL_SPECTRUM GSM and LTE None

spectrum _CONCURREN Spectrum
concurrency CY option of the Concurrency
SpectrumCloud.S
pectrumCloudSwit
ch parameter
Dynamic power LTE_DYN_POW Dynamic Power Inter-eNodeB SFN cells cannot

sharing between ER_SHARING_S Sharing Between be added to power sharing
LTE carriers W option of the LTE Carriers groups.
CellDynPowerSh
aring.DynamicPo
werSharingSwitch
parameter


Name
UMTS and LTE UMTS_LTE_DY UMTS and LTE

Dynamic Power N_POWER_SHA Dynamic Power
Sharing RING_SW and Sharing
LTE_DYN_POW
ER_SHARING_S
W options of the
CellDynPowerSh
aring.DynamicPo
werSharingSwitch
parameter
DL CoMP cell FDDHomNetDlC DL CoMP Inter-eNodeB SFN cells do not

ompSwitch, (FDD) support DL CoMP.
FDDHetNetDlCo
mpSwitch, and
Tm9JtSwitch
options of the
CellAlgoSwitch.D
lCompSwitch
parameter
Super combined SuperCombCellS Super Combined None

cell witch option of Cell (FDD)
the
CellAlgoSwitch.S
fnAlgoSwitch
parameter
15.3.3 Hardware
Base Station Models


l BTS3912E
l BTS3911E
Boards
In distributed Cloud BB mode, the BBP in a BBU that serves an inter-eNodeB SFN cell must
be UBBPd, UBBPe, or UBBPei.
RF Modules
Hardware.

Cells
An inter-eNodeB SFN cell has the following requirements for inter-eNodeB uplink and
downlink transmission bandwidths:
l 2T2R, 2T4R, or 4T4R cells: 400 Mbit/s
l 1T1R cells: 310 Mbit/s
15.3.4 Networking
In inter-eNodeB SFN, the same software version must be loaded for different BBUs
connected to the same USU. The USU software version must match the BBU software
version. For the version mapping, see the relevant release notes. For details on USUs, see
USU3910-based Multi-BBU Interconnection.
If the distributed Cloud BB architecture is used, only physical cells served by BBUs
interconnected through the same USU can be combined to form an SFN cell.
A BBU allows for a maximum of six physical cells to be members of inter-eNodeB SFN cells.
When inter-eNodeB physical cells are combined to form an SFN cell, the difference in their
coverage radiuses cannot exceed 500 m. If the difference exceeds 500 m, inter-eNodeB clock
precision errors can cause the downlink demodulation performance to deteriorate.
An inter-eNodeB SFN cell must meet the following requirements:
l The BBUs are time-synchronized. The clock accuracy deviation of the primary or
auxiliary eNodeB must not exceed 1.5 μs.
l The eNodeB IDs of the primary and auxiliary eNodeBs are unique in the network.
l The ADD CELLAUXENBBIND or ADD SFNCELLBIND command has been
executed on the primary eNodeB to bind the SFN cell to the auxiliary eNodeB. After the
binding, the SFN cell can use the sector equipment resources of the auxiliary eNodeB.
NOTE
In later versions, the SFNCELLBIND MO will be replaced by the CELLAUXENBBIND MO. In

this version, the configuration interface supports the configuration synchronization and delivery of
both MOs. Operators should avoid using the SFNCELLBIND MO.
l If the ADD CELLAUXENBBIND command is used, the PLMN ID of the auxiliary
eNodeB can be set differently from that of the SFN cell. Ensure that the configurations
meet the following requirements to prevent inter-BBU link setup failures, which can
result in malfunctions of the inter-eNodeB SFN cell.
– If the ENodeBSharingMode.ENodeBSharingMode parameter is set to
INDEPENDENT, SHARED_FREQ, or SEPARATED_FREQ_SPEC for the
auxiliary eNodeB, the CellAuxEnbBind.Mcc and CellAuxEnbBind.Mnc
parameters must be set to the MCC and MNC of the primary operator of the
auxiliary eNodeB, respectively.
SEPARATED_FREQ for the auxiliary eNodeB, the CellAuxEnbBind.Mcc and
CellAuxEnbBind.Mnc parameters can be set to the MCC and MNC of any
operator of the auxiliary eNodeB, respectively.
HYBRID_SHARED for the auxiliary eNodeB, the CellAuxEnbBind.Mcc and
CellAuxEnbBind.Mnc parameters can be set to the MCC and MNC of an operator
in any carrier-sharing operator group of the auxiliary eNodeB.

If the setting of the ENodeBSharingMode.ENodeBSharingMode parameter is changed

for the auxiliary eNodeB after the inter-eNodeB SFN cell works normally, check that the
CellAuxEnbBind.Mcc and CellAuxEnbBind.Mnc parameter settings on the primary
eNodeB meet the requirements.
l If the ADD SFNCELLBIND command is used, ensure that the configurations meet the
following requirements to prevent inter-BBU link setup failures, which can result in
malfunctions of the inter-eNodeB SFN cell.
INDEPENDENT, SHARED_FREQ, or SEPARATED_FREQ_SPEC for the
auxiliary eNodeB, the MCC and MNC settings of the primary operator of the
primary eNodeB must be the same as those of the primary operator of the auxiliary
eNodeB.
SEPARATED_FREQ for the auxiliary eNodeB, the MCC and MNC settings of the
primary operator of the primary eNodeB must be the same as those of any operator
of the auxiliary eNodeB.
HYBRID_SHARED for the auxiliary eNodeB, the MCC and MNC settings of the
primary operator of the primary eNodeB must be the same as those of an operator in
any carrier-sharing operator group of the auxiliary eNodeB.
configurations meet the requirements. If the requirements are not met, auxiliary cells will
malfunction.
15.3.5 Others
None

Table 15-1 and Table 15-2 describe the parameters used for function activation and
optimization, respectively.
Parameter Name Parameter ID Setting Notes
Local cell ID CellAuxEnbBind.LocalCell None

Id
Slave site eNodeB ID CellAuxEnbBind.EnodebId Set this parameter to the ID

of the auxiliary eNodeB to
be bound.

Mobile Country Code CellAuxEnbBind.Mcc None
Mobile Network Code CellAuxEnbBind.Mnc None
Sector equipment ID SfnAuxResBind.SectorEqm Set this parameter to the ID

Id of the sector equipment
configured on the auxiliary
eNodeB.
Main eNodeB ID SfnAuxResBind.eNodebId None
Main eNodeB Local cell SfnAuxResBind.LocalCellI None

ID d
Reference signal power SfnAuxResBind.ReferenceS None

ignalPwr

Parameter Name Parameter ID Option Setting Notes
Cell Standby Mode Cell.EuCellStandbyM N/A Set this parameter to

ode ACTIVE when you create
an SFN cell on the
primary eNodeB. The
SFN cell must be
manually activated on the
primary eNodeB.
Set this parameter to
STANDBY when you add
a standby cell on the
auxiliary eNodeB. The
standby cell does not need
to be manually activated.
OverBBUsSwitch ENodeBAlgoSwitch. UlSfnJROve Select this option.

OverBBUsSwitch rBBUsSwitch
Standby Cell SFN Cell.StandbyCellSfnR N/A None

Recovery Time ecoveTime
Local tracking area CellOp.TrackingArea N/A When a standby cell is

ID Id configured, cell operator
information must be
configured.
Sector CPRI SfnAuxResBind.Sect N/A None

Compression orCpriCompression
Virtual Cell ID SfnAuxResBind.Visu N/A None

alCellId


Perform the following configurations after an SFN cell has been configured. In the examples
provided in this section, BBU 0 and BBU 1 are the primary and auxiliary BBUs, respectively.
Four RRUs connected to BBU 0 and two RRUs connected to BBU 1 are combined to serve an
SFN cell. The eNodeB ID of the primary eNodeB is 100 and that of the auxiliary eNodeB is
101. The MCC and MNC of the primary operator of the auxiliary eNodeB are 000 and 00,
respectively.
Data Configuration on the Primary eNodeB
Configuring the binding relationship between the primary eNodeB and the auxiliary eNodeB
ADD CELLAUXENBBIND: LOCALCELLID=0,ENODEBID=101,MCC="000",MNC="00";
Activating the SFN cell on the primary eNodeB

NOTE
It is recommended that the SFN cell be activated after the data configuration on the auxiliary eNodeB is
complete.
Data Configuration on the Auxiliary eNodeB

Binding the sector equipment of the auxiliary eNodeB and the SFN cell of the primary
eNodeB
ADD SFNAUXRESBIND:SECTOREQMID=0,ENODEBID=100,LOCALCELLID=0;
ADD SFNAUXRESBIND:SECTOREQMID=1,ENODEBID=100,LOCALCELLID=0;

Configuring standby cells on all auxiliary eNodeBs
If the standby cell is an SFN cell, set SFN-related parameters based on their settings for the
SFN cell on the primary eNodeB.
If the standby cell is an SFN cell, set Cell.EuCellStandbyMode to STANDBY, and specify
the number of sets of sector equipment of the SFN cell according to the number of RRUs to
be combined. The other parameters except the PCI are set the same as the SFN cell on the
primary eNodeB.
ADD
CELL:LOCALCELLID=0,CELLNAME="FDD_SFN",NBCELLFLAG=FALSE,FREQBAND=7,ULEARFCNCFGIND=N
OT_CFG,DLEARFCN=3000,ULBANDWIDTH=CELL_BW_N100,DLBANDWIDTH=CELL_BW_N100,CELLID=100,
PHYCELLID=101,FDDTDDIND=CELL_FDD,EUCELLSTANDBYMODE=STANDBY,ROOTSEQUENCEIDX=0,CUSTO
MIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CF
G,MULTIRRUCELLFLAG=BOOLEAN_TRUE,MULTIRRUCELLMODE=SFN,SECTOREQMNUM=2,TXRXMODE=2T2R;
If the standby cell is a common cell, set the Cell.MultiRruCellFlag parameter to

BOOLEAN_FALSE and the Cell.EuCellStandbyMode parameter to STANDBY. The other
parameters except the PCI are set the same as the SFN cell on the primary eNodeB.
ADD
CELL:LOCALCELLID=0,CELLNAME="FDD_SFN",NBCELLFLAG=FALSE,FREQBAND=7,ULEARFCNCFGIND=N
OT_CFG,DLEARFCN=3000,ULBANDWIDTH=CELL_BW_N100,DLBANDWIDTH=CELL_BW_N100,CELLID=100,
PHYCELLID=101,FDDTDDIND=CELL_FDD,EUCELLSTANDBYMODE=STANDBY,ROOTSEQUENCEIDX=0,CUSTO
MIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CF
G,MULTIRRUCELLFLAG=BOOLEAN_FALSE,TXRXMODE=2T2R;

Adding sector equipment (taking the SFN cell as a standby cell for example)
ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0;
ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=1;
Changing the SFN recovery time of the standby cell on the auxiliary BBU
MOD CELL: LocalCellId=0,EuCellStandbyMode=STANDBY,StandbyCellSfnRecoveTime=255;
Setting UlSfnJROverBBUsSwitch
MOD ENODEBALGOSWITCH: OverBBUsSwitch=UlSfnJROverBBUsSwitch-1;


This function can be batch activated using the Feature Operation and Maintenance
This function can be activated for a single eNodeB or a batch of eNodeBs on the CME.

In addition, the relationship between primary and auxiliary cells in an SFN cell can be queried
by running the LST CELL command.


SFN Feature Parameter Description (TDD)
16 Inter-eNodeB SFN Based on eNodeB

Coordination (TDD)
16.1 Principles
Physical cells in an SFN cell can belong to the same BBU or different BBUs. If physical cells
belong to different BBUs, the BBUs must be deployed using a Cloud BB architecture. The
function used to combine physical cells belonging to different BBUs to form an SFN cell is
inter-eNodeB SFN based on eNodeB coordination. In the following descriptions, this function
is called inter-eNodeB SFN.
During the combination of physical cells belonging to different BBUs to form an SFN cell,
the inter-eNodeB SFN function minimizes the changes in physical connections between
RRUs and BBUs, reducing the number of site visits required and simplifying network
operations and maintenance.
Network Planning
Different BBUs are interconnected through a universal switching unit (USU), as shown in
Figure 16-1.
Both the USU3900 and USU3910 allow RRUs connected to different BBUs to constitute an
SFN cell. In the following figure, the USU3910 is used as an example.

Figure 16-1 Inter-eNodeB SFN networking based on eNodeB coordination
An inter-eNodeB SFN cell is set up on one of the BBUs. This BBU is referred to as the
primary BBU or the primary eNodeB of the SFN cell. The other BBUs are auxiliary BBUs or
auxiliary eNodeBs. The physical cells on an auxiliary eNodeB that constitute the SFN cell are
referred to as auxiliary cells.
The BBPs in the primary BBU are called primary BBPs. After a cell is activated, the primary
BBP of the cell can be queried by running the DSP CELL command on the primary BBU.
To create an SFN cell by running the ADD CELL command on the primary eNodeB, set the
Cell.EuCellStandbyMode parameter to ACTIVE.
Reliability
To ensure that service provisioning continues even if all the physical cells of an SFN cell
unexpectedly stop working, operators can configure a standby cell on an auxiliary eNodeB to
increase reliability. A standby cell can be added by running the ADD CELL command with
the Cell.EuCellStandbyMode parameter set to STANDBY on an auxiliary eNodeB. A
standby cell can be an SFN cell or a common cell.
A standby cell is automatically activated for service provisioning when any of the following
faults persists for up to 4 minutes:
l The control-plane link between the primary and auxiliary eNodeBs is interrupted.
l The data links between the primary and auxiliary eNodeBs are not working properly.
If this happens, engineers need to run the RST SFNAUXRES command to restore the
services in the auxiliary cells. The standby cell is activated only if data links to all RRUs
on the auxiliary eNodeBs are faulty.

l The primary BBPs are faulty.

If this happens, the primary eNodeB will attempt to allocate new primary BBPs for the
SFN cell. If the allocation is successful, the fault is rectified. If the allocation fails, the
primary eNodeB will deactivate the SFN cell and the RRUs on the auxiliary eNodeBs
will be automatically switched to the standby cell to ensure service continuity.
l The primary eNodeB does not transmit data properly.
l The main control board of the primary eNodeB is faulty.
l The SFN cell configured on the primary eNodeB has been unexpectedly deactivated.
l The clock precision deviation of the primary eNodeB exceeds 1.5 μs.
l The clock precision deviation of auxiliary eNodeBs ranges from 1.5 μs to 10 μs.
After a fault is rectified, the standby cell is automatically deactivated. The RRUs of auxiliary
eNodeBs are automatically switched to the SFN cell to ensure service continuity. The
Cell.StandbyCellSfnRecoveTime parameter specifies the automatic SFN recovery time of
inter-BBU cells on auxiliary BBUs after related SFN faults are rectified.
NOTE
l When the inter-BBU control-plane link is functional, the operating frequency of the standby cell
must be the same as that of the SFN cell configured on the primary BBU. Otherwise, the standby
cell cannot be activated.
l If local resources on auxiliary eNodeBs are abnormal, a standby cell cannot be set up.
l An inter-eNodeB SFN cell cannot serve as a standby cell.
l A standby cell that has been successfully activated cannot be activated again within 10 minutes after
an upgrade or reset of the eNodeB.
l If automatic neighbor relation (ANR) is not activated, neighboring cells must be configured for the
standby cell when the standby cell is added.
16.2.1 Benefits
Benefits.
16.2.2 Impacts
Network Impacts
see 6.2.2 Impacts.
Function Impacts
None
16.3 Requirements

16.3.1 Licenses
TDLOFD-001080 Inter-eNodeB SFN LT1SBBUSFN00 per BBU

Based on
Coordinated
eNodeB
The license unit must be purchased separately for both the primary and auxiliary BBUs.
If the licenses of both the primary and auxiliary BBUs do not meet service requirements,
ALM-26819 Data Configuration Exceeding Licensed Limit is reported only on the primary
BBU. If the licenses of the primary BBU meet service requirements but those of the auxiliary
BBU do not, this alarm is reported on the auxiliary BBU.
16.3.2 Software

Low power CellLowPower.Low Energy None

consumption mode PwrSwitch Conservation and
Emission Reduction
Dynamic power LTE_DYN_POWE Dynamic Power Inter-eNodeB SFN

sharing between R_SHARING_SW Sharing Between cells cannot be
LTE carriers option of the LTE Carriers added to power
CellDynPowerShar sharing groups.
ing.DynamicPower
SharingSwitch
parameter
16.3.3 Hardware
Base Station Models

Boards
For inter-eNodeB SFN, the BBPs in each BBU cannot be all LBBPc boards.
RF Modules
Hardware.
16.3.4 Networking
In inter-eNodeB SFN, the same software version must be loaded for different BBUs
connected to the same USU. The USU software version must match the BBU software
version. For the version mapping, see the relevant release notes. For details about USUs, see
USU3910-based Multi-BBU Interconnection and USU3900-based Multi-BBU
Interconnection.
In indoor coverage scenarios, inter-eNodeB SFN is not supported.
When inter-eNodeB physical cells are combined to form an SFN cell, the difference in their
coverage radiuses cannot exceed 500 m. If the difference exceeds 500 m, inter-eNodeB clock
precision errors can cause the downlink demodulation performance to deteriorate.
The eNodeB IDs of the primary and auxiliary eNodeBs are unique in the network.
The ADD CELLAUXENBBIND or ADD SFNCELLBIND command has been executed on

the primary eNodeB to bind the SFN cell to the auxiliary eNodeB. After the binding, the SFN
cell can use the sector equipment resources of the auxiliary eNodeB.
NOTE
In later versions, the SFNCELLBIND MO will be replaced by the CELLAUXENBBIND MO. In this
version, the configuration interface supports the configuration synchronization and delivery of both
MOs. Operators should avoid using the SFNCELLBIND MO.
An inter-eNodeB SFN cell deployed using a USU3910 must meet the following requirements:
l If the ADD CELLAUXENBBIND command is used, the PLMN ID of the auxiliary
eNodeB can be set differently from that of the SFN cell. Ensure that the configurations
meet the following requirements to prevent inter-BBU link setup failures, which can
result in malfunctions of the inter-eNodeB SFN cell.
INDEPENDENT or SHARED_FREQ for the auxiliary eNodeB, the
CellAuxEnbBind.Mcc and CellAuxEnbBind.Mnc parameters must be set to the
MCC and MNC of the primary operator of the auxiliary eNodeB, respectively.
SEPARATED_FREQ for the auxiliary eNodeB, the CellAuxEnbBind.Mcc and
CellAuxEnbBind.Mnc parameters can be set to the MCC and MNC of any
operator of the auxiliary eNodeB, respectively.
HYBRID_SHARED for the auxiliary eNodeB, the CellAuxEnbBind.Mcc and
CellAuxEnbBind.Mnc parameters can be set to the MCC and MNC of an operator
in any carrier-sharing operator group of the auxiliary eNodeB.

CellAuxEnbBind.Mcc and CellAuxEnbBind.Mnc parameter settings on the primary

eNodeB meet the requirements.
l If the ADD SFNCELLBIND command is used, ensure that the configurations meet the
following requirements to prevent inter-BBU link setup failures, which can result in
malfunctions of the inter-eNodeB SFN cell.
INDEPENDENT or SHARED_FREQ for the auxiliary eNodeB, the MCC and
MNC settings of the primary operator of the primary eNodeB must be the same as
those of the primary operator of the auxiliary eNodeB.
SEPARATED_FREQ for the auxiliary eNodeB, the MCC and MNC settings of the
primary operator of the primary eNodeB must be the same as those of any operator
of the auxiliary eNodeB.
HYBRID_SHARED for the auxiliary eNodeB, the MCC and MNC settings of the
primary operator of the primary eNodeB must be the same as those of an operator in
any carrier-sharing operator group of the auxiliary eNodeB.
configurations meet the requirements. If the requirements are not met, auxiliary cells will
malfunction.
To plan the primary eNodeB of an inter-eNodeB SFN cell, perform the following steps:
Step 1 Count how many RRUs are serving each SFN cell, and sort them from those with the most
RRUs to those with the least. Then identify the primary eNodeB of each SFN cell on the list,
starting with the one with the most RRUs.
Step 2 Select the eNodeBs that provide the most RRUs serving an SFN cell as candidate primary
eNodeBs of the SFN cell.
Step 3 Check whether each eNodeB meets all the following conditions:
l Layer 2 resources meet the BBP specification requirements described in Table 12-2.
l The total number of out-of-eNodeB and into-eNodeB physical cells does not exceed 14
times the number of data-transmission optical cables connecting the eNodeB and USU.
NOTE
– The number of data-transmission optical cables connecting the eNodeB and USU cannot
exceed 4 or the total number of LBBPd and UBBP boards installed in slots 0, 1, 2, and 3 on
the eNodeB, whichever is less.
– An into-eNodeB physical cell for an eNodeB (for example, eNodeB 0) is defined as follows:
The physical cell serves an SFN cell whose primary eNodeB is eNodeB 0, but the RRU of the
physical cell is connected to an eNodeB different from eNodeB 0.
– An out-of-eNodeB physical cell for an eNodeB (for example, eNodeB 0) is defined as follows:
The RRU of the physical cell is connected to eNodeB 0, but the physical cell serves an SFN
cell whose primary eNodeB is not eNodeB 0.
– "Physical cell" mentioned in this section corresponds to one carrier of each RRU.
– The LBBPc board does not support the configuration of 8T8R L2 logical cells.
In Figure 16-2, there are two into-eNodeB physical cells (cells served by RRU 1 and
RRU 2) and two out-of-eNodeB physical cells (cells served by RRU 5 and RRU 6) for
eNodeB 0, and there are two into-eNodeB physical cells (cells served by RRU 3 and
RRU 4) and one out-of-eNodeB physical cell (cell served by RRU 7) for eNodeB 1.

Figure 16-2 Inter-eNodeB SFN cells based on eNodeB coordination
If one or more eNodeBs meet all of the preceding conditions, go to Step 4. If no eNodeB
meets all of the preceding conditions, go to Step 5.
Step 4 Select an eNodeB as the primary eNodeB of an SFN cell. If only one eNodeB meets all of the
preceding conditions, the eNodeB functions as the primary eNodeB of the SFN cell. If
multiple eNodeBs meet all of the preceding conditions, the eNodeB that provides the
minimum number of RRUs processed at Layer 2 is preferentially selected as the primary
eNodeB of the SFN cell.
NOTE
The total number of RRUs processed at Layer 2 is the total number of RRUs serving all of the SFN cells
configured on the eNodeB, including RRUs connected to different eNodeBs.
Step 5 Select the eNodeB providing the second largest number of RRUs serving an SFN cell as the
candidate primary eNodeB of the SFN cell and repeat Step 3 until the primary eNodeB is
selected.
Step 6 Repeat Step 1 to Step 5 to select the primary eNodeBs for all the SFN cells.
----End
16.3.5 Others
None

NOTE
Inter-eNodeB SFN based on eNodeB coordination requires that the

ENODEBFRAMEOFFSET.TddFrameOffset parameter be set to the same value for primary and
auxiliary eNodeBs by running the MOD ENODEBFRAMEOFFSET command.


Local cell ID CellAuxEnbBind.LocalCe None

llId
Slave site eNodeB ID CellAuxEnbBind.Enodeb Set this parameter to the ID of the

Id auxiliary eNodeB to be bound.
Mobile Country Code CellAuxEnbBind.Mcc None
Mobile Network Code CellAuxEnbBind.Mnc None
Sector equipment ID SfnAuxResBind.SectorEq Set this parameter to the ID of the

mId sector equipment configured on
the auxiliary eNodeB.
Main eNodeB ID SfnAuxResBind.eNodebId Set this parameter to the ID of the

primary eNodeB.
Main eNodeB Local SfnAuxResBind.LocalCell Set this parameter to the ID of the

cell ID Id local cell of the primary eNodeB.

Name
Cell Standby Cell.EuCellStandbyM N/A Set this parameter to

Mode ode ACTIVE when you
create an SFN cell on
the primary eNodeB.
The SFN cell must be
manually activated on
the primary eNodeB.
Set this parameter to
STANDBY when you
add a standby cell on
the auxiliary eNodeB.
The standby cell does
not need to be
manually activated.
OverBBUsSwit ENodeBAlgoSwitch. UlSfnJROverBBUs Select this option.

ch OverBBUsSwitch Switch
Standby Cell Cell.StandbyCellSfnR N/A None

SFN Recovery ecoveTime
Time


Name
Local tracking CellOp.TrackingArea N/A When a standby cell is

area ID Id configured, cell
operator information
must be configured.

Perform the following configurations after an SFN cell has been configured. In the examples
provided in this section, BBU 0 and BBU 1 are the primary and auxiliary BBUs, respectively.
Four RRUs connected to BBU 0 and two RRUs connected to BBU 1 are combined to serve an
SFN cell. The eNodeB ID of the primary eNodeB is 100 and that of the auxiliary eNodeB is
101. The MCC and MNC of the primary operator of the auxiliary eNodeB are 000 and 00,
respectively.
Data Configuration on the Primary eNodeB
Configuring the binding relationship between the primary eNodeB and the auxiliary eNodeB
ADD CELLAUXENBBIND: LOCALCELLID=0,ENODEBID=101,MCC="000",MNC="00";
Activating the SFN cell on the primary eNodeB

NOTE
It is recommended that the SFN cell be activated after the data configuration on the auxiliary eNodeB is
complete.
Data Configuration on the Auxiliary eNodeB

Binding the sector equipment of the auxiliary eNodeB and the SFN cell of the primary
eNodeB
ADD SFNAUXRESBIND: SECTOREQMID=0,ENODEBID=100,LOCALCELLID=0,BASEBANDEQMID=0;
ADD SFNAUXRESBIND: SECTOREQMID=1,ENODEBID=100,LOCALCELLID=0,BASEBANDEQMID=0;

Configuring standby cells on all auxiliary eNodeBs
If the standby cell is an SFN cell, set SFN-related parameters based on their settings for the
SFN cell on the primary eNodeB.
If the standby cell is an SFN cell, set Cell.EuCellStandbyMode to STANDBY, and specify
the number of sets of sector equipment of the SFN cell according to the number of RRUs to
be combined. The other parameters except the PCI are set the same as the SFN cell on the
primary eNodeB.
ADD CELL:
LOCALCELLID=0,CELLNAME="TDD_SFN",NBCELLFLAG=FALSE,FREQBAND=41,ULEARFCNCFGIND=NOT_C
FG,DLEARFCN=40340,ULBANDWIDTH=CELL_BW_N100,DLBANDWIDTH=CELL_BW_N100,CELLID=100,PHY
CELLID=100,FDDTDDIND=CELL_TDD,SUBFRAMEASSIGNMENT=SA2,SPECIALSUBFRAMEPATTERNS=SSP7,

EUCELLSTANDBYMODE=STANDBY,ROOTSEQUENCEIDX=0,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMER
GENCYAREAIDCFGIND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_TRUE,M
ULTIRRUCELLMODE=SFN,SECTOREQMNUM=2,TXRXMODE=4T4R;
If the standby cell is a common cell, set the Cell.MultiRruCellFlag parameter to

BOOLEAN_FALSE and the Cell.EuCellStandbyMode parameter to STANDBY. The other
parameters except the PCI are set the same as the SFN cell on the primary eNodeB.
ADD CELL:
LOCALCELLID=0,CELLNAME="TDD_SFN",NBCELLFLAG=FALSE,FREQBAND=41,ULEARFCNCFGIND=NOT_C
FG,DLEARFCN=40340,ULBANDWIDTH=CELL_BW_N100,DLBANDWIDTH=CELL_BW_N100,CELLID=100,PHY
CELLID=100,FDDTDDIND=CELL_TDD,SUBFRAMEASSIGNMENT=SA2,SPECIALSUBFRAMEPATTERNS=SSP7,
EUCELLSTANDBYMODE=STANDBY,ROOTSEQUENCEIDX=0,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMER
GENCYAREAIDCFGIND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_FALSE,
TXRXMODE=4T4R;
Adding sector equipment (taking the SFN cell as a standby cell for example)
ADD EUCELLSECTOREQM: LOCALCELLID=0,SECTOREQMID=0,BASEBANDEQMID=0;
ADD EUCELLSECTOREQM: LOCALCELLID=0,SECTOREQMID=1,BASEBANDEQMID=0;
Changing the SFN recovery time of the standby cell on the auxiliary BBU
MOD CELL: LocalCellId=0,EuCellStandbyMode=STANDBY,StandbyCellSfnRecoveTime=255;
Setting UlSfnJROverBBUsSwitch
MOD ENODEBALGOSWITCH: OverBBUsSwitch=UlSfnJROverBBUsSwitch-1;



In addition, the relationship between primary and auxiliary cells in an SFN cell can be queried
by running the LST CELL command.


eRAN 17 Inter-eNodeB Adaptive SFN/SDMA based on eNodeB
SFN Feature Parameter Description Coordination (FDD)
17 Inter-eNodeB Adaptive SFN/SDMA

based on eNodeB Coordination (FDD)
17.1 Principles
This function allows inter-eNodeB RRUs to be combined to serve an adaptive SFN cell.
17.2.1 Benefits
17.2.2 Impacts
Network Impacts
Function Impacts
None
17.3 Requirements

17.3.1 Licenses
LOFD-081209 Inter-eNodeB LT1SIASSBC00 Per eNodeB

Adaptive SFN/
SDMA Based on
Coordinated
eNodeB
17.3.2 Software

chSwitch
chSwitch
Inter-BBP adaptive SFN/ None SFN

SDMA
Inter-eNodeB SFN based on Cell.EuCellStandbyMode SFN

eNodeB coordination

None
17.3.3 Hardware
Base Station Models
l BTS3912E
l BTS3911E
Boards
In distributed Cloud BB mode, the BBP in a BBU that serves an inter-eNodeB SFN cell must
be UBBPd, UBBPe, or UBBPei.

RF Modules
Hardware.
17.3.4 Others
None

The data preparation for this function is the same as that for the adaptive SFN/SDMA and
inter-eNodeB SFN based on eNodeB coordination functions. For details, see 9.4.1.1 Data
Preparation and 15.4.1.1 Data Preparation.

SDMA and inter-eNodeB SFN based on eNodeB coordination functions. For details, see
9.4.1.2 Using MML Commands and 15.4.1.2 Using MML Commands.

This function can be batch activated using the Feature Operation and Maintenance
This function can be activated for a single eNodeB or a batch of eNodeBs on the CME.

The activation verification of this function is the same as that of the adaptive SFN/SDMA and
inter-eNodeB SFN based on eNodeB coordination functions. For details, see 9.4.2 Activation
Verification and 15.4.2 Activation Verification.

The network monitoring for this function is the same as that for the adaptive SFN/SDMA and
inter-eNodeB SFN based on eNodeB coordination functions. For details, see 9.4.3 Network
Monitoring and 15.4.3 Network Monitoring.

SFN Feature Parameter Description Coordination (TDD)
18 Inter-eNodeB Adaptive SFN/SDMA

based on eNodeB Coordination (TDD)
18.1 Principles
This function allows inter-eNodeB RRUs to be combined to serve an adaptive SFN cell.
18.2.1 Benefits
18.2.2 Impacts
Network Impacts
Function Impacts
None
18.3 Requirements

18.3.1 Licenses
TDLOFD-001082 Inter-eNodeB LT1SBBUADA00 per BBU

Adaptive SFN/
SDMA Based on
Coordinated
eNodeB
18.3.2 Software

chSwitch
chSwitch
Inter-BBP adaptive SFN/ None SFN

SDMA
Inter-eNodeB SFN based on Cell.EuCellStandbyMode SFN

eNodeB coordination

None
18.3.3 Hardware
Base Station Models

Boards
This function has the same board requirements as the SFN, inter-BBP SFN, and inter-eNodeB
SFN based on eNodeB coordination functions. For details, see 6.3.3 Hardware, 12.3.3
Hardware, and 16.3.3 Hardware.

RF Modules
This function has the same RF module requirements as the SFN, inter-BBP SFN, and inter-
eNodeB SFN based on eNodeB coordination functions. For details, see 6.3.3 Hardware,
12.3.3 Hardware, and 16.3.3 Hardware.
18.3.4 Others
None

The data preparation for this function is the same as that for the adaptive SFN/SDMA and
inter-eNodeB SFN based on eNodeB coordination functions. For details, see 10.4.1.1 Data
Preparation and 16.4.1.1 Data Preparation.

SDMA and inter-eNodeB SFN based on eNodeB coordination functions. For details, see
10.4.1.2 Using MML Commands and 16.4.1.2 Using MML Commands.


For details, see inter-eNodeB SFN based on eNodeB coordination and adaptive SFN in 10.4.2
Activation Verification and 16.4.2 Activation Verification.

For details, see inter-eNodeB SFN based on eNodeB coordination and adaptive SFN in 10.4.3
Network Monitoring and 16.4.3 Network Monitoring.

eRAN
SFN Feature Parameter Description 19 Adaptive SFN/SDMA with TM9/TM10 (Trial) (FDD)
19 Adaptive SFN/SDMA with TM9/TM10

(Trial) (FDD)
19.1 Principles
In an adaptive SFN cell, CRSs are used for channel estimation. UEs demodulate data
transmitted over the PDSCH based on the estimation results. Since the CRSs are jointly
transmitted but PDSCH data is independently transmitted to independently scheduled UEs,
the CRS SINR and PDSCH SINR of independently scheduled UEs are inconsistent. This
results in inaccurate channel estimation, impacts PDSCH demodulation performance, and
causes User Downlink Average Throughput to decrease.
To reduce the impacts, TM9 and TM10 are used with adaptive SFN. When TM9 and TM10
are used, demodulation reference signals (DMRSs) are used for PDSCH channel estimation
and channel state information-reference signals (CSI-RSs) are used by the UEs to obtain CSI.
The use of CSI-RS and DMRS instead of CRS for PDSCH measurement and demodulation
helps resolve mobility- and coverage-related KPI issues and further increase the cell capacity,
the spectral efficiency of downlink independently scheduled UEs, and the user-perceived
throughput when single-frequency networking is used.
In TM9, the DMRS uses nSCID for scrambling. 3GPP specifications only define two values for
nSCID.
If an adaptive SFN cell is served by two RRUs, it is recommended that the

AsfnFastAttSwitch option of the CellAlgoSwitch.SfnAlgoSwitch parameter be selected so
that the eNodeB can optimize the transmission mode selection results for UEs.
If an adaptive SFN cell is served by more than two RRUs, the AsfnFastAttSwitch option of
the CellAlgoSwitch.SfnAlgoSwitch parameter must be selected. This allows for TM9 to be
used in this cell and the eNodeB can dynamically adjust the working RRU lists for TM9 UEs.
(TM9 cannot be used in the cell if there are more than six RRUs serving the cell.)
In TM10, the DMRS uses a virtual cell identifier (VCID) for scrambling. The value range of
VCIDs is 0 to 503. TM10 can be used for an adaptive SFN cell served by two or more
combined RRUs. Before using adaptive SFN with TM10, the TM10Switch option of the
CellAlgoSwitch.EnhMIMOSwitch parameter must be selected and the
CellCsiRsParaCfg.CsiRsSwitch parameter must be set to ADAPTIVE_CFG.

eRAN
19.2.1 Benefits
When this function is enabled for an SFN cell served by a macro eNodeB and all UEs in the
SFN cell are independently scheduled, the capacity of the SFN cell can reach up to 80% to
90% of the total capacity of all physical cells in the SFN cell. The cell capacity is higher than
that achieved before this function is used in the SFN cell.
When the resource usage of a cell is greater than 60% and the total percentage of TM9 and
TM10 UEs is greater than 60%, User Downlink Average Throughput can be increased by
up to 20%.
If the TM9Switch option of the CellAlgoSwitch.EnhMIMOSwitch parameter is already

selected for an adaptive SFN cell served by two RRUs, selecting the AsfnFastAttSwitch
option of the CellAlgoSwitch.SfnAlgoSwitch parameter will increase the User Downlink
Average Throughput by 1% to 15% for this cell.
19.2.2 Impacts
Network Impacts
When adaptive SFN/SDMA with TM9/TM10 is enabled, the eNodeB additionally transmits
CSI-RSs. Due to the increase in CSI-RS overheads, the scheduling of UEs that do not support
CSI-RSs is restricted in CSI-RS subframes. Therefore, the User Downlink Average
Throughput of these UEs decreases.
Function Impacts
None
19.3 Requirements
19.3.1 Licenses
There are currently no license requirements for trial features.
19.3.2 Software
Adaptive SFN/ l CellAlgoSwitch.SfnUlSchSwitch SFN

SDMA l CellAlgoSwitch.SfnDlSchSwitch

eRAN

Ultra high speed Cell.HighSpeedFla High Speed Mobility None

mobility g
DL CoMP with FDDHomNetDlCo DL CoMP (FDD) DL CoMP with

TM9 mpSwitch, TM9 cannot be
FDDHetNetDlCom enabled together
pSwitch, and with adaptive SFN/
Tm9JtSwitch SDMA with TM9 or
options of the TM10.
CellAlgoSwitch.Dl
CompSwitch
parameter
DL CoMP with FDDHomNetDlCo DL CoMP (FDD) DL CoMP with

TM10 mpSwitch and TM10 cannot be
FDDHetNetDlCom enabled together
pSwitch options of with adaptive SFN/
the SDMA with TM9.
CellAlgoSwitch.Dl
CompSwitch
parameter
Virtual 4T4R Virtual4T4RSwitch Virtual 4T4R (FDD) None

option of the
CellAlgoSwitch.Em
imoSwitch
parameter
19.3.3 Hardware
Base Station Models


Boards
RF Modules
Hardware.

eRAN
19.3.4 Networking
Adaptive SFN cells use the TM10 transmission mode. When configuring VCIDs for physical
cells of an adaptive SFN cell, ensure that adjacent cells have different values of VCID modulo
3. The method of planning VCIDs is the same as that of planning PCIs.
19.3.5 Others
If the network load increases and the percentage of TM9 and TM10 UEs on the network has
exceeded 60%, it is recommended that TM9 or TM10 be used.

For the parameters used for activation, see the data preparation for the adaptive SFN/SDMA
function. Table 19-1 describes the parameters that are set additionally for the activation of
this function. For the parameters used for optimization, see the data preparation for 4x4
MIMO in the overlapping areas between the physical cells of an SFN cell. Table 19-2
describes the parameters that are set additionally for the optimization of this function.

Name
Enhanced CellAlgoSwitch.En TM9Switch Select this option when the

MIMO hMIMOSwitch CellAlgoSwitch.SfnDlSchSwitch
Switch parameter is set to ADAPTIVE.
TM10Switc Select this option when the


eRAN

Name
SFN CellAlgoSwitch.Sfn AsfnFastAtt This option must be selected for an

Algorithm AlgoSwitch Switch adaptive SFN cell served by more
Switch than two RRUs.
This option can be selected for an
adaptive SFN cell served by two
RRUs.
It is recommended that this option be
selected when the TM9Switch option
of the
CellAlgoSwitch.EnhMIMOSwitch
parameter is selected.
This option has the following board
requirements:
l The main control board is a
UMPT.
l The BBP is not an LBBPd.

Name
Virtual Cell eUCellSectorEqm. Set this parameter when RRUs are combined to serve
ID VisualCellId an SFN cell and the TM10Switch option of the
CellAlgoSwitch.EnhMIMOSwitch parameter is
selected.
Virtual Cell EuSectorEqmGrou Set this parameter when pRRUs are combined to
ID p.VisualCellId serve an SFN cell and the TM10Switch option of the
CellAlgoSwitch.EnhMIMOSwitch parameter is
selected.
You can also set CSI-RS-related parameters. For details, see 7.4.1.1 Data Preparation in 7
4x4 MIMO in the Overlapping Areas Between the Physical Cells of an SFN Cell.

Turning on the CSI-RS switch
Turning on AsfnFastAttSwitch for an adaptive SFN cell served by more than two RRUs (This
switch must be turned on for such an adaptive SFN cell.)

eRAN
MOD CELLALGOSWITCH: LocalCellId=0, SfnAlgoSwitch=AsfnFastAttSwitch-1;
Enabling TM9
MOD CELLALGOSWITCH: LocalCellId=0, EnhMIMOSwitch=TM9Switch-1;
Enabling TM10
NOTE
TM9Switch and TM10Switch cannot be both turned on.

Changing the Virtual Cell ID parameter value when TM10 is enabled and RRUs are used
MOD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0, BaseBandEqmId=1,
VisualCellId=1;
Changing the Virtual Cell ID parameter value when TM10 is enabled and pRRUs are used
MOD EUSECTOREQMGROUP: LocalCellId=0, SectorEqmGroupId=0, BaseBandEqmId=1,
VisualCellId=1;
Turning on AsfnFastAttSwitch for an adaptive SFN cell served by two RRUs

Setting CSI-RS-related parameters

MOD CELLCSIRSPARACFG: LOCALCELLID=0, CsiRsSwitch=ADAPTIVE_CFG, CsiRsPeriod=ms20,
CsiRsConfigUserRatioTh=60, CsiRsUnconfigUserRatioTh=50;

Turning off the CSI-RS switch
Disabling TM9
Disabling TM10
Turning off AsfnFastAttSwitch for an adaptive SFN cell served by more than two RRUs


Check the following counters on the U2020 client.

eRAN
Table 19-3 TM9- and TM10-related performance counters

1526732888 L.CellSectorEQUIP.SFN.Traffic.User.TM9.Avg
1526732889 L.CellSectorEQUIPGroup.SFN.Traffic.User.TM
9.Avg
1526742076 L.Traffic.User.TM10.Avg
l If the value of L.CellSectorEQUIP.SFN.Traffic.User.TM9.Avg or

L.CellSectorEQUIPGroup.SFN.Traffic.User.TM9.Avg is not zero, TM9 has taken
effect.
l If the value of L.Traffic.User.TM10.Avg is not zero, TM10 has taken effect.

After the adaptive SFN/SDMA with TM9 function is enabled, UEs that support TM9 are
more likely to be independently scheduled. Therefore, the percentage of independently
scheduled UEs increases. The amount of increase is determined by the number of UEs that
support TM9.
Percentage of independently scheduled UEs = L.CellSectorEQUIP.SFN.DLISch.User.Avg/
L.CellSectorEQUIP.SFN.DL.User.Avg x 100%
The other monitoring counters are the same as those of the SFN function. For details, see
5.4.3 Network Monitoring.

eRAN
SFN Feature Parameter Description 20 PDCCH DCS in SFN (TDD)
20 PDCCH DCS in SFN (TDD)
20.1 Principles
PDCCH DCS in SFN (DCS is short for dynamic cell selection) was introduced to mitigate
interference on the PDCCH between SFN cells and to increase the PDCCH SINR. This
function is controlled by the SFNPDCCHDCSSWITCH option of the

eRAN
Figure 20-1 Working principles of PDCCH DCS in SFN
In the network shown in Figure 20-1, UE 1 is located at the edges of cells 1 and 2, and UE 2
is located in cell 2 and is far away from cell 1.
l If PDCCH DCS in SFN is not enabled, all the RRUs serving cell 1 transmit PDCCH
signals to UE 1 and all the RRUs serving cell 2 transmit PDCCH signals to UE 2. UE 1
receives PDCCH signals from both cells and PDCCH signals from cell 2 cause
interference to UE 1.
l If PDCCH DCS in SFN is enabled, RRUs are dynamically selected for PDCCH
transmission. Only the working RRUs of a UE are allocated normal transmit power for
PDCCH signals. The other RRUs are not allocated transmit power. As shown in Figure
20-1, only RRU 3 transmits PDCCH signals to UE 1, and only RRUs 4 and 6 transmit
PDCCH signals to UE 2, which significantly mitigates PDCCH interference from cell 2
to UE 1.

eRAN
NOTE
When PDCCH DCS in SFN is enabled, RRUs use different CCE resources to transmit PDCCH
signals to different UEs.
This function relies on the creation of a working RRU list, which can be performed when
adaptive SFN/SDMA is enabled. The process is similar to that used in adaptive SFN/SDMA.
In the procedure, the eNodeB determines the working RRU list as follows:
1. The eNodeB calculates the downlink equivalent RSRP values of the signals that each
RRU sends to the UE, based on the RSRP values of the signals that the UE sends to the
RRUs in the SFN cell.
3. The eNodeB selects the RRU with the largest equivalent RSRP value as the target RRU
used to transmit PDCCH to the UE.
4. The eNodeB creates a working RRU list based on isolation degrees.
a. The eNodeB sorts the RRUs into two groups, A and B. The RRU with the largest
equivalent RSRP value is put into group A and the other RRUs into group B. It then
calculates the isolation degree between RRU groups A and B. The isolation degree
equals the ratio of the total RSRP of RRU group A to the total RSRP of RRU group
B.
b. The eNodeB compares the isolation degree with a configured threshold. If the
isolation degree is lower than the threshold specified by the
CellPdcchAlgo.SfnPdcchDcsThd parameter, the eNodeB moves the RRU with the
largest equivalent RSRP in RRU group B to RRU group A, and calculates the
isolation degree again. The eNodeB repeats this process until the isolation degree is
greater than or equal to the specified threshold. When the isolation degree is greater
than or equal to the specified threshold, the RRUs contained in RRU group A form
the working RRU list of the UE.
If the CellPdcchAlgo.PDCCHAggLvlAdaptStrage parameter is set to
STRATEGYBASEDONCOVERAGE, the eNodeB determines that all RRUs serving
the SFN cell are the working RRUs for PDCCH transmission for the following UEs:
UEs providing hybrid automatic repeat request (HARQ) feedback in multiplexing mode,
UEs using PUCCH format 3, and UEs using PUCCH format 1bcs. This ensures that
PDCCH performance does not deteriorate for these UEs.
20.2.1 Benefits
When three RRUs serve an SFN cell in a typical dense urban area and the PDCCH load rate is
100%, PDCCH DCS in SFN increases the PDCCH coverage by about 0.5 dB and the user
capacity of the PDCCH by about 9%. The user capacity of the PDCCH refers to the average
number of UEs that can be allocated CCE resources when UEs are evenly distributed.
It is recommended that PDCCH DCS in SFN be activated when the PDCCH load is heavy,
PDCCH interference between SFN cells is severe, and adaptive SFN/SDMA has been
activated. If PDCCH SDMA in SFN has been activated, deactivate it before you activate
PDCCH DCS in SFN.

eRAN
20.2.2 Impacts
The impacts of this function are the same as those of the adaptive SFN/SDMA function. For
details, see 10.2.2 Impacts.
20.3 Requirements
20.3.1 Licenses
TDLOFD-070227 PDCCH DCS in LT1SPDCSIS00 per Cell

SFN
20.3.2 Software

chSwitch
chSwitch

PDCCH SDMA in SFN CellPdcchAlgo.SfnPdcchS SFN

dmaThd
20.3.3 Hardware
Base Station Models
Boards

eRAN
RF Modules
Hardware.
20.3.4 Others
None


Name
SFN Algorithm CellAlgoSwitch.Sfn SfnPdcchDcsSwitc This option is valid only

Switch AlgoSwitch h when the
CellAlgoSwitch.SfnDlS
chSwitch parameter is
set to ADAPTIVE.

Name
SFN Pdcch DCS CellPdcchAlgo.SfnPdcchDcsThd None

Threshold

Setting the switch for PDCCH DCS in SFN
MOD CELLALGOSWITCH: LOCALCELLID=0, SFNALGOSWITCH=SfnPdcchDcsSwitch-1;

Setting the threshold for PDCCH DCS in SFN

eRAN
MOD CELLPDCCHALGO: LOCALCELLID=0, SfnPdcchDcsThd=40;
When an SFN cell functions as the standby cell, set the CellPdcchAlgo.SfnPdcchDcsThd
parameter for the standby cell based on its setting for the SFN cell configured on the primary
eNodeB.
When a common cell functions as the standby cell, do not set this parameter for the standby
cell.

Disabling PDCCH DCS in SFN
MOD CELLALGOSWITCH: LOCALCELLID=0, SFNALGOSWITCH=SfnPdcchDcsSwitch-0;




eRAN
SFN Feature Parameter Description 21 PDCCH SDMA in SFN (TDD)
21 PDCCH SDMA in SFN (TDD)
21.1 Principles
PDCCH SDMA in SFN was introduced to increase the PDCCH capacity of SFN cells. This
function is controlled by the SFNPDCCHSDMASWITCH option of the

eRAN
Figure 21-1 Working principles of PDCCH SDMA in SFN
In the network shown in Figure 21-1, UE 1 is located in the coverage area of RRU 1 in cell 1
and is far from other RRUs. UE 2 is located in the coverage area of RRU 2 in cell 1 and is far
from other RRUs. UE 3 is located in the coverage area of RRU 4 in cell 2 and is far from
other RRUs. UE 4 is located in the edge area covered by both RRU 5 and RRU 6 in cell 2.

eRAN
l If PDCCH SDMA in SFN is not enabled, all the RRUs serving cell 1 transmit PDCCH
signals to UE 1 and UE 2 and all the RRUs serving cell 2 transmit PDCCH signals to UE
3 and UE 4.
l If PDCCH SDMA in SFN is enabled, the eNodeB allocates PDCCH resources to a UE
only at the working RRUs of the UE. PDCCH CCE resources of different RRUs in the
SFN cell can be reused by UEs. In the example illustrated in Figure 21-1, UE 1 receives
only the PDCCH signals transmitted by RRU 1 in cell 1 and UE 2 receives only the
PDCCH signals transmitted by RRU 2 in cell 1. UE 1 and UE 2 can reuse the CCE
resources of cell 1. UE 3 receives only the PDCCH signals transmitted by RRU 4 in cell
2 and UE 4 receives only the PDCCH signals transmitted by RRU 5 and RRU 6 in cell 2.
UE 3 and UE 4 can reuse the CCE resources of cell 2.
NOTE
When PDCCH SDMA in SFN is enabled, RRUs reuse CCE resources to transmit PDCCH signals
to different UEs.
This function relies on the creation of a working RRU list, which can be performed when
adaptive SFN/SDMA is enabled. The process is the same as that used in the PDCCH DCS in
SFN feature. For details, see 20 PDCCH DCS in SFN (TDD). The isolation degree decision
threshold is specified by the CellPdcchAlgo.SfnPdcchSdmaThd parameter.
If the CellPdcchAlgo.PDCCHAggLvlAdaptStrage parameter is set to

STRATEGYBASEDONCOVERAGE, the eNodeB determines that all RRUs serving the
SFN cell are the working RRUs for PDCCH transmission for the following UEs: UEs
providing HARQ feedback in multiplexing mode, UEs using PUCCH format 3, and UEs
using PUCCH format 1bcs. This ensures that PDCCH performance does not deteriorate for
these UEs.
21.2.1 Benefits
When three RRUs serve an SFN cell in a typical dense urban area and the PDCCH load ratio
is 100%, PDCCH SDMA in SFN increases the user capacity of the PDCCH by about 24%.
The user capacity of the PDCCH refers to the average number of UEs that can be allocated
CCE resources when UEs are evenly distributed.
It is recommended that PDCCH SDMA in SFN be activated when the PDCCH load is heavy,
a large number of UEs are scheduled in each TTI, and adaptive SFN/SDMA has been
activated. If PDCCH DCS in SFN has been activated, deactivate it before you activate
PDCCH SDMA in SFN.
21.2.2 Impacts
21.3 Requirements

eRAN
21.3.1 Licenses
TDLOFD-081221 PDCCH SDMA LT1SPSISFN00 per Cell

in SFN
21.3.2 Software

chSwitch
chSwitch

PDCCH DCS in SFN CellPdcchAlgo.SfnPdcchD SFN

csThd
21.3.3 Hardware
Base Station Models
Boards
RF Modules
Hardware.
21.3.4 Others
None

eRAN


SFN Algorithm CellAlgoSwitch.SfnA SfnPdcch This option is valid only when

Switch lgoSwitch SdmaSwit the
ch CellAlgoSwitch.SfnDlSchSw
itch parameter is set to
ADAPTIVE.

SFN PDCCH CellPdcchAlgo.SfnPd N/A None

SDMA Threshold cchSdmaThd
SFN Algorithm CellAlgoSwitch.SfnA SfnPucch Set this option to its

Switch lgoSwitch AckSdma recommended value.
Switch This option is valid only when
the SfnPdcchSdmaSwitch
option is selected.

When an SFN cell functions as the standby cell, set the CellPdcchAlgo.SfnPdcchSdmaThd
parameter for the standby cell based on its setting for the SFN cell configured on the primary
eNodeB.
When a common cell functions as the standby cell, do not set this parameter for the standby
cell.
Turning on the switch for the PDCCH SDMA in SFN function
MOD CELLALGOSWITCH: LOCALCELLID=0,
SFNALGOSWITCH=SfnPdcchSdmaSwitch-1&SfnPucchAckSdmaSwitch-1;

eRAN

Setting the threshold for the PDCCH SDMA in SFN function
MOD CELLPDCCHALGO: LOCALCELLID=0, SfnPdcchSdmaThd=24;

Disabling the PDCCH SDMA in SFN function
MOD CELLALGOSWITCH: LOCALCELLID=0,
SFNALGOSWITCH=SfnPdcchSdmaSwitch-0&SfnPucchAckSdmaSwitch-0;




eRAN
SFN Feature Parameter Description 22 Inter-RRU CBF in Adaptive SFN/SDMA (TDD)
22 Inter-RRU CBF in Adaptive SFN/

SDMA (TDD)
22.1 Principles
If inter-RRU CBF is enabled for an SFN cell, UEs with a low correlation under different
RRUs are selected to pair for spatial multiplexing. Signals transmitted to the paired UEs are
weighted using CBF, mitigating interference between UEs served by different RRUs. Inter-
RRU CBF in an SFN cell is controlled by the MuBfSwitch option of the
CellAlgoSwitch.MuBfAlgoSwitch parameter and the SfnCbfSwitch option of the
Figure 22-1 shows an SFN cell served by RRUs 0, 1, and 2. UE 1 resides in the overlapping
coverage area of the three RRUs. It uses RRU 1 as its target RRU, but can also receive strong
signals from RRUs 0 and 2. UE 2 is covered only by RRU 2. Spatial multiplexing is used
between UE 1 and UE 2. CBF directs null signals to UE 1 by adjusting weights for UE 2. This
mitigates the interference on UE 1 and generates only a little signal loss for UE 2. As a result,
the throughput of the SFN cell increases.
Figure 22-1 Inter-RRU CBF (1)

eRAN
As shown in Figure 22-2, UE 1 resides in the overlapping coverage area of RRUs 0, 1, and 2
while UE 2 resides in the overlapping coverage area of RRUs 1 and 2. Spatial multiplexing is
used between UE 1 and UE 2. CBF directs null signals transmitted by RRU 2 to UE 1 by
adjusting weights. In addition, CBF directs null signals transmitted by RRU 1 to UE 2 by
adjusting weights. These measures mitigate the mutual signal interference between UE 1 and
UE 2 and increase the throughput of the SFN cell.
Figure 22-2 Inter-RRU CBF (2)
22.2.1 Benefits
22.2.2 Impacts
22.3 Requirements
22.3.1 Licenses
None

eRAN
22.3.2 Software

chSwitch
chSwitch

None
22.3.3 Hardware
Base Station Models
Boards
LBBPc boards do not support CBF.
2T2R SFN cells do not support CBF.
It is recommended that CBF be enabled when the UBBP serves as the primary BBP.
RF Modules
Hardware.
22.3.4 Others
None

Table 22-1 describes the parameters used for function activation. No parameter is involved in
function optimization.

eRAN

Name
SFN Algorithm CellAlgoSwitch.Sfn SfnCbfSwitch Select this option.

Switch AlgoSwitch You are advised to select
the MuBfSwitch option
of the
CellAlgoSwitch.MuBfA
lgoSwitch parameter
before selecting the
SfnCbfSwitch option.
This option is valid only
when the
SfnDl2LoadLevelAdpt
Switch option is
selected.

Enabling inter-RRU CBF
MOD CELLALGOSWITCH: LOCALCELLID=0, MuBfAlgoSwitch=MuBfSwitch-1,
SfnAlgoSwitch=SfnCbfSwitch-1;

N/A

Disabling inter-RRU CBF
MOD CELLALGOSWITCH: LOCALCELLID=0, MuBfAlgoSwitch=MuBfSwitch-0,
SfnAlgoSwitch=SfnCbfSwitch-0;




eRAN
SFN Feature Parameter Description 23 Parameters
23 Parameters
The following hyperlinked EXCEL files of parameter reference match the software version
with which this document is released.
l Node Parameter Reference: contains device and transport parameters.
l eNodeBFunction Parameter Reference: contains all parameters related to radio access
functions, including air interface management, access control, mobility control, and radio
resource management.
NOTE
You can find the EXCEL files of parameter reference for the software version on the live network from
the product documentation delivered with that version.
FAQ: How do I find the parameters related to a certain feature from parameter
reference?
Step 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, for example, LOFD-001016 or TDLOFD-001016.
Step 3 Click OK. All parameters related to the feature are displayed.
----End

eRAN
SFN Feature Parameter Description 24 Counters
24 Counters
The following hyperlinked EXCEL files of performance counter reference match the software
version with which this document is released.
l Node Performance Counter Summary: contains device and transport counters.
l eNodeBFunction Performance Counter Summary: contains all counters related to radio
access functions, including air interface management, access control, mobility control,
and radio resource management.
NOTE
You can find the EXCEL files of performance counter reference for the software version used on the live
network from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from performance counter
reference?
Step 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, for example, LOFD-001016 or TDLOFD-001016.
Step 3 Click OK. All counters related to the feature are displayed.
----End

eRAN
SFN Feature Parameter Description 25 Glossary
25 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
SFN Feature Parameter Description 26 Reference Documents
26 Reference Documents
1. Physical Channel Resource Management

2. Scheduling
3. Base station initial configuration guides
4. MIMO
5. USU3910-based Multi-BBU Interconnection
6. USU3900-based Multi-BBU Interconnection
7. Beamforming (TDD)
8. NB-IoT Basics (FDD)
9. NB-IoT Enhancements (FDD)
10. 3900 Series Base Station Technical Description
11. CDMA and LTE Zero Bufferzone
12. CSPC
13. D-MIMO (TDD)
14. DL CoMP (FDD)
15. DL CoMP (TDD)
16. DRX and Signaling Control
17. eMBMS
18. eMIMO (FDD)
19. eMTC
20. GSM and LTE Spectrum Concurrency
21. GSM and LTE FDD Dynamic Spectrum Sharing
22. GSM and LTE Dynamic Power Sharing
23. GSM and LTE Zero Bufferzone
24. LCS
25. LTE and NR Spectrum Sharing
26. Dynamic Power Sharing Between LTE Carriers
27. Massive MIMO (FDD)
28. Massive MIMO (TDD)

eRAN
SFN Feature Parameter Description 26 Reference Documents
29. Short TTI (FDD)

30. Turbo Receiver
31. Relay
32. UL CoMP
33. UL Refarming Zero Bufferzone
34. UMTS and LTE Dynamic Power Sharing
35. UMTS and LTE Zero Bufferzone
36. UMTS and LTE Spectrum Sharing
37. WTTx Turbo Beamforming (TDD)
38. Super Combined Cell (FDD)
39. Extended Cell Range
40. Transport Resource Management
41. Breathing Pilot
42. Inter-eNodeB Multi-Carrier Coordinated Scheduling (TDD)
43. Multi-band Optimal Carrier Selection
44. SFN HetNet Smart Cluster Organization Feature Description
45. Interference Detection and Suppression
46. Interference Randomizing (TDD)
47. High Speed Mobility
48. Power Control
49. Flexible Bandwidth based on Overlap Carriers (FDD)
50. Energy Conservation and Emission Reduction
51. Extended CP
52. Soft Split Resource Duplex (TDD)
53. UL ICS (TDD)
54. Uplink Coordinated Scheduling
55. Random Access Control
56. TDM eICIC (FDD)
57. Virtual 4T4R (FDD)
58. Modulation Schemes
59. Compact Bandwidth (FDD)
60. Carrier Aggregation
61. Adaptive ICIC
62. Admission and Congestion Control
63. Subframe Configuration (TDD)
64. Multi-carrier Unified Scheduling

SFN (eRAN15.1 - Draft B) PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

SFN (eRAN15.1 - Draft B) PDF

Загружено:

Авторское право:

Доступные форматы

eRAN

SFN Feature Parameter Description

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. i

2 About This Document.................................................................................................................. 5

Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. ii

Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. iii

7.4.2.1 Data Preparation................................................................................................................................................... 102

8 SFN HetNet Smart Cluster Organization (FDD).................................................................105

9 Adaptive SFN/SDMA (FDD)...................................................................................................108

10 Adaptive SFN/SDMA (TDD)................................................................................................ 121

Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. iv

10.3.3 Hardware............................................................................................................................................................... 126

11 Inter-BBP SFN (FDD)..............................................................................................................130

12 Inter-BBP SFN (TDD)............................................................................................................. 139

Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. v

12.4.1.3 Using the CME................................................................................................................................................... 146

13 Inter-BBP Adaptive SFN/SDMA (FDD)..............................................................................147

14 Inter-BBP Adaptive SFN/SDMA (TDD)............................................................................. 150

15 Inter-eNodeB SFN Based on eNodeB Coordination (FDD)............................................ 153

Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. vi

16 Inter-eNodeB SFN Based on eNodeB Coordination (TDD)............................................164

17 Inter-eNodeB Adaptive SFN/SDMA based on eNodeB Coordination (FDD)............ 174

Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. vii

17.4 Operation and Maintenance......................................................................................................................................176

18 Inter-eNodeB Adaptive SFN/SDMA based on eNodeB Coordination (TDD)............177

19 Adaptive SFN/SDMA with TM9/TM10 (Trial) (FDD)..................................................... 180

Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. viii

20 PDCCH DCS in SFN (TDD)..................................................................................................187

21 PDCCH SDMA in SFN (TDD)..............................................................................................193

22 Inter-RRU CBF in Adaptive SFN/SDMA (TDD)...............................................................199

Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. ix

22.3.3 Hardware............................................................................................................................................................... 201

Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. x

1.1 eRAN15.1 Draft B (2019-02-22)

1.2 eRAN15.1 Draft A (2019-01-05)

Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. 1

Added smart carrier selection None FDD l 3900 and 5900

Added smart carrier selection None TDD l 3900 and 5900

Added the following functions None FDD l 3900 and 5900

Added DL CoMP with TM9 to None FDD l 3900 and 5900

Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. 2

Change Description Parameter RAT Base Station

Added fast UE scheduling Added the FDD l 3900 and 5900

Added NPREO constant None FDD l 3900 and 5900

Added compatibility of None FDD l 3900 and 5900

Added DL CoMP with TM9 to None FDD 3900 and 5900

Added DL CoMP with TM9 to None FDD l 3900 and 5900

Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. 3

Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. 4

2 About This Document

2.1 General Statements

Issue Draft B (2019-02-22) Copyright © Huawei Technologies Co., Ltd. 5

Feature Differences Between RATs

2.2 Applicable RAT

2.3 Features in This Document

Feature ID Feature Name Section

LOFD-003029 SFN 5 SFN (FDD)

7 4x4 MIMO in the

8 SFN HetNet Smart

11 Inter-BBP SFN (FDD)