You are on page 1of 435

eRAN

NB-IoT Radio and Performance


Basics Feature Parameter
Description

Issue 05
Date 2017-08-30

HUAWEI TECHNOLOGIES CO., LTD.


Copyright Huawei Technologies Co., Ltd. 2017. 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 05 (2017-08-30) Huawei Proprietary and Confidential i


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description Contents

Contents

1 About This Document.................................................................................................................. 1


1.1 Scope.............................................................................................................................................................................. 1
1.2 Disclaimer for Trial Features..........................................................................................................................................2
1.3 Intended Audience.......................................................................................................................................................... 2
1.4 Change History............................................................................................................................................................... 3
1.5 Differences Between eNodeB Types.............................................................................................................................. 9

2 Overview....................................................................................................................................... 12
2.1 Background...................................................................................................................................................................12
2.2 Introduction.................................................................................................................................................................. 13
2.3 Benefits......................................................................................................................................................................... 13
2.4 Architecture.................................................................................................................................................................. 13
2.5 Feature Overview......................................................................................................................................................... 14
2.5.1 MLBFD-12000101 Standalone Deployment.............................................................................................................14
2.5.2 MLBFD-12000102 LTE Guardband Deployment.....................................................................................................14
2.5.3 MLBFD-12000103 LTE In-band Deployment.......................................................................................................... 14
2.5.4 MLBFD-12000202 Single-tone.................................................................................................................................15
2.5.5 MLBFD-12000203 Support of NB-IoT UE.............................................................................................................. 15
2.5.6 MLBFD-12000204 Data over NAS.......................................................................................................................... 16
2.5.7 MLBFD-12100205 Data over User Plane (Trial)......................................................................................................16
2.5.8 MLBFD-12000226 Modulation: DL QPSK, UL QPSK/BPSK................................................................................ 17
2.5.9 MLBFD-12000227 AMC.......................................................................................................................................... 17
2.5.10 MLBFD-12000228 RRC Connection Management................................................................................................17
2.5.11 MLBFD-12000229 Broadcast of System Information............................................................................................ 18
2.5.12 MLBFD-12000223 Physical Channel Management............................................................................................... 18
2.5.13 MLBFD-12000224 DL Asynchronous HARQ....................................................................................................... 18
2.5.14 MLBFD-12000225 UL Asynchronous HARQ....................................................................................................... 18
2.5.15 MLBFD-12000230 Random Access Procedure...................................................................................................... 18
2.5.16 MLBFD-12000231 Paging...................................................................................................................................... 18
2.5.17 MLBFD-12000232 Cell Access Radius up to 35 km..............................................................................................19
2.5.18 MLBFD-12000233 Admission Control...................................................................................................................19
2.5.19 MLBFD-12000234 Basic Scheduling..................................................................................................................... 19
2.5.20 MLBFD-12000235 Uplink Power Control..............................................................................................................19
2.5.21 MLBFD-12000236 DRX.........................................................................................................................................19

Issue 05 (2017-08-30) Huawei Proprietary and Confidential ii


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description Contents

2.5.22 MLBFD-12000237 Cell Selection and Re-selection...............................................................................................19


2.5.23 MLBFD-12000238 UL 2-Antenna Receive Diversity............................................................................................ 19
2.5.24 MLBFD-12100240 DL 4-Antenna Transmit Diversity...........................................................................................20
2.5.25 MLBFD-12100242 Active Queue Management (AQM)........................................................................................ 20
2.5.26 MLBFD-12100243 Congestion Control..................................................................................................................20
2.5.27 MLBFD-12100244 SCTP Congestion Control....................................................................................................... 20
2.5.28 MLOFD-120220 Idle Mode eDRX......................................................................................................................... 20
2.5.29 MLOFD-120201 NB-IoT Coverage Extension....................................................................................................... 21
2.5.30 MLOFD-120230 Multi-tone....................................................................................................................................21
2.5.31 MLOFD-121202 UL 4-Antenna Receive Diversity................................................................................................ 21
2.5.32 MLOFD-121204 SFN..............................................................................................................................................21

3 Technical Description.................................................................................................................22
3.1 Basic Concepts............................................................................................................................................................. 22
3.1.1 Physical Channels......................................................................................................................................................22
3.1.2 Frequency-Domain Structure.................................................................................................................................... 23
3.1.3 Time-Domain Structure............................................................................................................................................. 24
3.1.4 Coverage Level..........................................................................................................................................................26
3.1.5 Aggregation Level..................................................................................................................................................... 26
3.2 Deployment Mode........................................................................................................................................................ 26
3.2.1 Standalone Deployment.............................................................................................................................................26
3.2.2 LTE Guardband Deployment.....................................................................................................................................27
3.2.3 LTE In-band Deployment.......................................................................................................................................... 29
3.3 Cell Management..........................................................................................................................................................31
3.3.1 Related Concepts....................................................................................................................................................... 31
3.3.1.1 Cell..........................................................................................................................................................................32
3.3.1.2 PRB.........................................................................................................................................................................32
3.3.1.3 Sector...................................................................................................................................................................... 35
3.3.1.4 Sector Equipment................................................................................................................................................... 35
3.3.1.5 RF Modules............................................................................................................................................................ 35
3.3.1.6 Baseband Equipment.............................................................................................................................................. 35
3.3.1.7 Cell-specific Sector Equipment.............................................................................................................................. 36
3.4 Idle Mode Management................................................................................................................................................36
3.4.1 Overview................................................................................................................................................................... 36
3.4.2 PLMN Selection........................................................................................................................................................ 37
3.4.3 Automatic PLMN Selection...................................................................................................................................... 38
3.4.4 Manual PLMN Selection........................................................................................................................................... 39
3.4.5 Roaming.....................................................................................................................................................................39
3.4.6 Cell Selection and Reselection.................................................................................................................................. 39
3.4.6.1 Cell Search..............................................................................................................................................................40
3.4.6.2 Cell Selection..........................................................................................................................................................40
3.4.6.3 Neighboring Cell Measurement for Cell Reselection.............................................................................................42
3.4.6.4 Cell Reselection...................................................................................................................................................... 42

Issue 05 (2017-08-30) Huawei Proprietary and Confidential iii


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description Contents

3.4.6.5 TA Registration.......................................................................................................................................................44
3.4.6.6 TA Update...............................................................................................................................................................44
3.4.6.7 Attach/Detach......................................................................................................................................................... 44
3.4.7 Cell Reservation and Access Control........................................................................................................................ 44
3.4.7.1 Cell Reservation and Barring................................................................................................................................. 45
3.4.7.2 Access Control........................................................................................................................................................45
3.4.8 Paging........................................................................................................................................................................ 46
3.4.9 System Information Broadcast.................................................................................................................................. 50
3.5 Connection Management.............................................................................................................................................. 52
3.5.1 Random Access......................................................................................................................................................... 52
3.5.1.1 Overview................................................................................................................................................................ 52
3.5.1.2 Random Access Procedure..................................................................................................................................... 53
3.5.1.3 NPRACH Resource Configuration.........................................................................................................................55
3.5.1.4 NPRACH Detection Threshold.............................................................................................................................. 58
3.5.2 RRC Connection Setup..............................................................................................................................................58
3.5.3 RRC Connection Resume.......................................................................................................................................... 60
3.5.4 NB-IoT MME Selection............................................................................................................................................ 61
3.5.5 Data Transmission..................................................................................................................................................... 61
3.5.6 Signaling Connection Release................................................................................................................................... 64
3.6 Scheduling.................................................................................................................................................................... 65
3.6.1 Definition...................................................................................................................................................................65
3.6.2 Scheduler Working Principle..................................................................................................................................... 66
3.6.3 Uplink Scheduling..................................................................................................................................................... 68
3.6.3.1 Uplink Scheduling Procedure................................................................................................................................. 68
3.6.3.2 Uplink Scheduling Triggering................................................................................................................................ 69
3.6.3.3 Uplink Scheduling for Retransmissions................................................................................................................. 69
3.6.3.4 Uplink Scheduling for Initial Transmissions.......................................................................................................... 70
3.6.4 Downlink Scheduling................................................................................................................................................ 72
3.6.4.1 Downlink Scheduling Procedure............................................................................................................................ 72
3.6.4.2 Downlink Scheduling for Retransmissions............................................................................................................ 73
3.6.4.3 Downlink Scheduling for Initial Transmissions..................................................................................................... 73
3.7 Power Control...............................................................................................................................................................76
3.7.1 Downlink Power Control...........................................................................................................................................76
3.7.2 Uplink Power Control................................................................................................................................................81
3.7.2.1 NPRACH Power Control........................................................................................................................................81
3.7.2.2 NPUSCH Power Control........................................................................................................................................ 81
3.8 Admission Control, Congestion Control, and Overload Control................................................................................. 83
3.9 DRX..............................................................................................................................................................................87
3.9.1 DRX-related Concepts...............................................................................................................................................88
3.9.2 Startup of a DRX Cycle.............................................................................................................................................89
3.9.3 Operation in a DRX Cycle.........................................................................................................................................89
3.10 Idle Mode eDRX........................................................................................................................................................ 92

Issue 05 (2017-08-30) Huawei Proprietary and Confidential iv


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description Contents

3.10.1 eDRX Time Synchronization Mechanism...............................................................................................................92


3.10.2 eDRX Paging Mechanism....................................................................................................................................... 93
3.10.3 eDRX Paging Handling........................................................................................................................................... 94
3.10.4 eDRX Negotiation and Paging................................................................................................................................ 94
3.10.5 Scheduling of eDRX Paging Messages................................................................................................................... 96
3.11 NB-IoT Coverage Extension...................................................................................................................................... 96
3.12 Multi-tone................................................................................................................................................................... 97
3.13 Multiple-Antenna Reception...................................................................................................................................... 99
3.13.1 Overview................................................................................................................................................................. 99
3.13.2 Receive Diversity.................................................................................................................................................... 99
3.13.3 Receiver Technologies...........................................................................................................................................102
3.14 Multiple-Antenna Transmission............................................................................................................................... 104
3.14.1 Overview............................................................................................................................................................... 104
3.14.2 Transmit Diversity................................................................................................................................................. 104

4 Related Features.........................................................................................................................106
4.1 MLBFD-12000101 Standalone Deployment..............................................................................................................107
4.2 MLBFD-12000102 LTE Guardband Deployment......................................................................................................107
4.3 MLBFD-12000103 LTE In-band Deployment........................................................................................................... 108
4.4 MLBFD-12000202 Single-tone.................................................................................................................................. 111
4.5 MLBFD-12000203 Support of NB-IoT UE............................................................................................................... 112
4.6 MLBFD-12000204 Data over NAS............................................................................................................................112
4.7 MLBFD-12100205 Data over User Plane (Trial).......................................................................................................112
4.8 MLBFD-12000226 Modulation: DL QPSK, UL QPSK/BPSK................................................................................. 113
4.9 MLBFD-12000227 AMC........................................................................................................................................... 113
4.10 MLBFD-12000228 RRC Connection Management................................................................................................. 114
4.11 MLBFD-12000229 Broadcast of System Information............................................................................................. 114
4.12 MLBFD-12000223 Physical Channel Management.................................................................................................114
4.13 MLBFD-12000224 DL Asynchronous HARQ.........................................................................................................115
4.14 MLBFD-12000225 UL Asynchronous HARQ.........................................................................................................115
4.15 MLBFD-12000230 Random Access Procedure....................................................................................................... 116
4.16 MLBFD-12000231 Paging....................................................................................................................................... 116
4.17 MLBFD-12000232 Cell Access Radius up to 35 km............................................................................................... 116
4.18 MLBFD-12000233 Admission Control....................................................................................................................116
4.19 MLBFD-12000234 Basic Scheduling...................................................................................................................... 117
4.20 MLBFD-12000235 Uplink Power Control...............................................................................................................117
4.21 MLBFD-12000236 DRX..........................................................................................................................................118
4.22 MLBFD-12000237 Cell Selection and Re-selection................................................................................................ 118
4.23 MLBFD-12000238 UL 2-Antenna Receive Diversity............................................................................................. 119
4.24 MLBFD-12100240 DL 4-Antenna Transmit Diversity............................................................................................119
4.25 MLBFD-12100243 Congestion Control...................................................................................................................119
4.26 MLOFD-120220 Idle Mode eDRX.......................................................................................................................... 120
4.27 MLOFD-120201 NB-IoT Coverage Extension........................................................................................................ 120

Issue 05 (2017-08-30) Huawei Proprietary and Confidential v


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description Contents

4.28 MLOFD-120230 Multi-tone.....................................................................................................................................121


4.29 MLOFD-121202 UL 4-Antenna Receive Diversity................................................................................................. 121

5 Network Impact......................................................................................................................... 122


5.1 MLBFD-12000101 Standalone Deployment..............................................................................................................123
5.2 MLBFD-12000102 LTE Guardband Deployment......................................................................................................123
5.3 MLBFD-12000103 LTE In-band Deployment........................................................................................................... 123
5.4 MLBFD-12000202 Single-tone..................................................................................................................................126
5.5 MLBFD-12000203 Support of NB-IoT UE............................................................................................................... 126
5.6 MLBFD-12000204 Data over NAS........................................................................................................................... 126
5.7 MLBFD-12100205 Data over User Plane (Trial).......................................................................................................127
5.8 MLBFD-12000226 Modulation: DL QPSK, UL QPSK/BPSK................................................................................. 127
5.9 MLBFD-12000227 AMC........................................................................................................................................... 127
5.10 MLBFD-12000228 RRC Connection Management.................................................................................................127
5.11 MLBFD-12000229 Broadcast of System Information............................................................................................. 128
5.12 MLBFD-12000223 Physical Channel Management................................................................................................ 128
5.13 MLBFD-12000224 DL Asynchronous HARQ........................................................................................................ 128
5.14 MLBFD-12000225 UL Asynchronous HARQ........................................................................................................ 128
5.15 MLBFD-12000230 Random Access Procedure....................................................................................................... 129
5.16 MLBFD-12000231 Paging....................................................................................................................................... 129
5.17 MLBFD-12000232 Cell Access Radius up to 35 km...............................................................................................129
5.18 MLBFD-12000233 Admission Control....................................................................................................................129
5.19 MLBFD-12000234 Basic Scheduling...................................................................................................................... 130
5.20 MLBFD-12000235 Uplink Power Control...............................................................................................................130
5.21 MLBFD-12000236 DRX..........................................................................................................................................130
5.22 MLBFD-12000237 Cell Selection and Re-selection................................................................................................130
5.23 MLBFD-12000238 UL 2-Antenna Receive Diversity............................................................................................. 131
5.24 MLBFD-12100240 DL 4-Antenna Transmit Diversity............................................................................................131
5.25 MLBFD-12100243 Congestion Control...................................................................................................................132
5.26 MLOFD-120220 Idle Mode eDRX.......................................................................................................................... 132
5.27 MLOFD-120201 NB-IoT Coverage Extension........................................................................................................ 132
5.28 MLOFD-120230 Multi-tone.....................................................................................................................................132
5.29 MLOFD-121202 UL 4-Antenna Receive Diversity................................................................................................. 133

6 Engineering Guidelines for NB-IoT Basic Features........................................................... 134


6.1 When to Use............................................................................................................................................................... 134
6.2 Required Information................................................................................................................................................. 134
6.3 Planning...................................................................................................................................................................... 135
6.3.1 RF Planning............................................................................................................................................................. 135
6.3.2 Network Planning.................................................................................................................................................... 135
6.3.3 Hardware Planning.................................................................................................................................................. 136
6.4 Deployment................................................................................................................................................................ 136
6.4.1 Requirements........................................................................................................................................................... 136
6.4.2 Precautions...............................................................................................................................................................137

Issue 05 (2017-08-30) Huawei Proprietary and Confidential vi


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description Contents

6.4.3 Hardware Adjustment..............................................................................................................................................138


6.4.4 Data Preparation and Activation..............................................................................................................................138
6.4.4.1 Data Preparation................................................................................................................................................... 138
6.4.4.2 Using the CME..................................................................................................................................................... 164
6.4.4.3 Using MML Commands....................................................................................................................................... 164
6.4.4.4 MML Command Examples.................................................................................................................................. 167
6.4.5 Activation Observation............................................................................................................................................170
6.4.6 Deactivation.............................................................................................................................................................171
6.4.6.1 Using the CME..................................................................................................................................................... 171
6.4.6.2 Using MML Commands....................................................................................................................................... 171
6.4.6.3 MML Command Examples.................................................................................................................................. 171
6.5 Performance Monitoring.............................................................................................................................................171
6.6 Parameter Optimization.............................................................................................................................................. 173
6.7 Possible Issues............................................................................................................................................................ 179

7 Engineering Guidelines for Idle Mode eDRX..................................................................... 181


7.1 When to Use............................................................................................................................................................... 181
7.2 Required Information................................................................................................................................................. 181
7.3 Planning...................................................................................................................................................................... 181
7.4 Deployment................................................................................................................................................................ 181
7.4.1 Requirements........................................................................................................................................................... 182
7.4.2 Precautions...............................................................................................................................................................182
7.4.3 Hardware Adjustment..............................................................................................................................................183
7.4.4 Data Preparation and Activation..............................................................................................................................183
7.4.4.1 Data Preparation................................................................................................................................................... 183
7.4.4.2 Using the CME..................................................................................................................................................... 184
7.4.4.3 Using MML Commands....................................................................................................................................... 184
7.4.4.4 MML Command Examples.................................................................................................................................. 185
7.4.5 Activation Observation............................................................................................................................................185
7.4.6 Deactivation.............................................................................................................................................................185
7.4.6.1 Using the CME..................................................................................................................................................... 185
7.4.6.2 Using MML Commands....................................................................................................................................... 185
7.4.6.3 MML Command Examples.................................................................................................................................. 186
7.5 Performance Monitoring.............................................................................................................................................186
7.6 Parameter Optimization.............................................................................................................................................. 186
7.7 Possible Issues............................................................................................................................................................ 186

8 Engineering Guidelines for NB-IoT Coverage Extension................................................. 187


8.1 When to Use............................................................................................................................................................... 187
8.2 Required Information................................................................................................................................................. 187
8.3 Planning...................................................................................................................................................................... 187
8.4 Deployment................................................................................................................................................................ 187
8.4.1 Requirements........................................................................................................................................................... 188
8.4.2 Precautions...............................................................................................................................................................188

Issue 05 (2017-08-30) Huawei Proprietary and Confidential vii


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description Contents

8.4.3 Hardware Adjustment..............................................................................................................................................188


8.4.4 Data Preparation and Activation..............................................................................................................................188
8.4.4.1 Data Preparation................................................................................................................................................... 188
8.4.4.2 Using the CME..................................................................................................................................................... 189
8.4.4.3 Using MML Commands....................................................................................................................................... 189
8.4.4.4 MML Command Examples.................................................................................................................................. 189
8.4.5 Activation Observation............................................................................................................................................189
8.4.6 Deactivation.............................................................................................................................................................190
8.4.6.1 Using the CME..................................................................................................................................................... 190
8.4.6.2 Using MML Commands....................................................................................................................................... 190
8.4.6.3 MML Command Examples.................................................................................................................................. 190
8.5 Performance Monitoring.............................................................................................................................................190
8.6 Parameter Optimization.............................................................................................................................................. 191
8.7 Possible Issues............................................................................................................................................................ 191

9 Engineering Guidelines for Multi-tone................................................................................ 192


9.1 When to Use............................................................................................................................................................... 192
9.2 Required Information................................................................................................................................................. 192
9.3 Planning...................................................................................................................................................................... 192
9.4 Deployment................................................................................................................................................................ 192
9.4.1 Requirements........................................................................................................................................................... 192
9.4.2 Precautions...............................................................................................................................................................193
9.4.3 Hardware Adjustment..............................................................................................................................................193
9.4.4 Data Preparation and Activation..............................................................................................................................193
9.4.4.1 Data Preparation................................................................................................................................................... 193
9.4.4.2 Using the CME..................................................................................................................................................... 194
9.4.4.3 Using MML Commands....................................................................................................................................... 194
9.4.4.4 MML Command Examples.................................................................................................................................. 194
9.4.5 Activation Observation............................................................................................................................................194
9.4.6 Deactivation.............................................................................................................................................................195
9.4.6.1 Using the CME..................................................................................................................................................... 195
9.4.6.2 Using MML Commands....................................................................................................................................... 196
9.4.6.3 MML Command Examples.................................................................................................................................. 196
9.5 Performance Monitoring.............................................................................................................................................196
9.6 Parameter Optimization.............................................................................................................................................. 196
9.7 Possible Issues............................................................................................................................................................ 196

10 Engineering Guidelines for Multiple-Antenna Reception............................................. 197


10.1 When to Use............................................................................................................................................................. 198
10.2 Required Information............................................................................................................................................... 198
10.3 Planning.................................................................................................................................................................... 199
10.4 Deployment.............................................................................................................................................................. 199
10.4.1 Requirements......................................................................................................................................................... 199
10.4.2 Precautions.............................................................................................................................................................200

Issue 05 (2017-08-30) Huawei Proprietary and Confidential viii


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description Contents

10.4.3 Hardware Adjustment............................................................................................................................................200


10.4.4 Data Preparation and Feature Activation...............................................................................................................208
10.4.4.1 Data Preparation................................................................................................................................................. 208
10.4.4.2 Using the CME................................................................................................................................................... 210
10.4.4.3 Using MML Commands..................................................................................................................................... 210
10.4.4.4 MML Command Examples................................................................................................................................ 211
10.4.5 Activation Observation..........................................................................................................................................213
10.4.6 Deactivation...........................................................................................................................................................214
10.4.6.1 Using the CME................................................................................................................................................... 214
10.4.6.2 Using MML Commands..................................................................................................................................... 214
10.4.6.3 MML Command Examples................................................................................................................................ 214
10.5 Performance Monitoring...........................................................................................................................................215
10.6 Parameter Optimization............................................................................................................................................ 216
10.7 Possible Issues.......................................................................................................................................................... 216

11 Engineering Guidelines for Multiple-Antenna Transmission.......................................217


11.1 When to Use..............................................................................................................................................................218
11.2 Required Information................................................................................................................................................218
11.3 Planning.................................................................................................................................................................... 219
11.4 Deployment...............................................................................................................................................................219
11.4.1 Requirements......................................................................................................................................................... 219
11.4.2 Precautions.............................................................................................................................................................220
11.4.3 Hardware Adjustment............................................................................................................................................ 220
11.4.4 Data Preparation and Feature Activation...............................................................................................................220
11.4.4.1 Data Preparation................................................................................................................................................. 220
11.4.4.2 Using the CME................................................................................................................................................... 220
11.4.4.3 Using MML Commands..................................................................................................................................... 220
11.4.5 Activation Observation.......................................................................................................................................... 221
11.4.6 Deactivation........................................................................................................................................................... 221
11.4.6.1 Using the CME................................................................................................................................................... 222
11.4.6.2 Using MML Commands..................................................................................................................................... 222
11.5 Performance Monitoring...........................................................................................................................................222
11.6 Parameter Optimization............................................................................................................................................ 222
11.7 Possible Issues.......................................................................................................................................................... 222

12 Parameters................................................................................................................................. 224
13 Counters.................................................................................................................................... 382
14 Glossary..................................................................................................................................... 423
15 Reference Documents............................................................................................................. 424

Issue 05 (2017-08-30) Huawei Proprietary and Confidential ix


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 1 About This Document

1 About This Document

1.1 Scope
This document describes Narrowband Internet of Things (NB-IoT) features, including their
technical principles, related features, network impact, and engineering guidelines.

This document covers the following features:

l MLBFD-120001 NB-IoT Network Deployment


MLBFD-12000101 Standalone Deployment
MLBFD-12000102 LTE Guardband Deployment
MLBFD-12000103 LTE In-band Deployment
l MLBFD-120002 3GPP NB-IoT Specifications Compliant
MLBFD-12000202 Single-tone
MLBFD-12000203 Support of NB-IoT UE
MLBFD-12000204 Data over NAS
MLBFD-12100205 Data over User Plane (trial)
MLBFD-12000223 Physical Channel Management
MLBFD-12000224 DL Asynchronous HARQ
MLBFD-12000225 UL Asynchronous HARQ
MLBFD-12000226 Modulation: DL QPSK, UL QPSK/BPSK
MLBFD-12000227 AMC
MLBFD-12000228 RRC Connection Management
MLBFD-12000229 Broadcast of system information
MLBFD-12000230 Random Access Procedure
MLBFD-12000231 Paging
MLBFD-12000232 Cell Access Radius up to 35 km
MLBFD-12000233 Admission Control
MLBFD-12000234 Basic Scheduling
MLBFD-12000235 Uplink Power Control

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 1


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 1 About This Document

MLBFD-12000236 DRX
MLBFD-12000237 Cell Selection and Re-selection
MLBFD-12000238 UL 2-Antenna Receive Diversity
MLBFD-12100240 DL 4-Antenna Transmit Diversity
MLBFD-12100242 Active Queue Management (AQM)
MLBFD-12100243 Congestion Control
MLBFD-12100244 SCTP Congestion Control
l MLOFD-120201 NB-IoT Coverage Extension
l MLOFD-120220 Idle Mode eDRX
l MLOFD-120230 Multi-tone
l MLOFD-121202 UL 4-Antenna Receive Diversity
l MLOFD-121204 SFN
Any parameters, alarms, counters, or managed objects (MOs) described herein apply only to
the corresponding software release. For future software releases, refer to the corresponding
updated product documentation.

1.2 Disclaimer for 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
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.

1.3 Intended Audience


This document is intended for personnel who:
l Need to understand the features described herein
l Work with Huawei products

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 2


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 1 About This Document

1.4 Change History


This section provides information about the changes in different document versions. There are
two types of changes:
l Feature change
Changes in features and parameters of a specified version as well as the affected entities
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.

eRAN12.1 05 (2017-08-30)
This issue includes the following changes.
Change Change Description Parameter Change Affected
Type Entity

Feature Enabled the adjustment of pilot Added the Macro and


change power broadcast in SIB2 by setting CellChPwrCfg.AntOutput micro
the proportion of NB-IoT cell Pwr parameter. eNodeBs
output power in scenarios where Added the
repeaters are used to amplify RRU AntRsPwrSwitch option
output power. For details, see the to the
following sections: CellAlgoSwitch.Repeater
l 3.7.1 Downlink Power Switch parameter.
Control Activated the reserved
l 6.4.4.1 Data Preparation parameter
l 6.4.4.3 Using MML eNBCellRsvdPara.RsvdU
Commands 16Para8.
l 6.4.4.4 MML Command
Examples

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 3


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 1 About This Document

Change Change Description Parameter Change Affected


Type Entity

Allowed the number of Activated the following Macro and


retransmissions to be increased by reserved parameter: micro
the first scheduling for eNBCellRsvdPara.RsvdU eNodeBs
retransmissions in downlink. 8Para22
Allowed this number to be used by
the subsequent scheduling for
retransmissions. For details, see
3.6.4.2 Downlink Scheduling for
Retransmissions.
Added a constraint that the initial
MCS index for downlink RAR and
Msg4 transmission during initial
access depends on the value of
eNBCellRsvdPara.RsvdU8Para22
. For details, see 3.6.4.3 Downlink
Scheduling for Initial
Transmissions.

Editorial Stated that NB-IoT supports RAN None N/A


change sharing and allows the
configuration of one primary
operator and a maximum of three
secondary operators. For details,
see 6.4.4.1 Data Preparation.
Revised the following sections:
l 3.2.3 LTE In-band
Deployment
l 3.4.6.3 Neighboring Cell
Measurement for Cell
Reselection

eRAN12.1 04 (2017-06-29)
This issue includes the following changes.
Change Change Description Parameter Affected
Type Change Entity

Feature Added the requirement that the None Macro and


change TIMESRC.AUTOSWITCH parameter be set micro
to OFF when Idle Mode eDRX is enabled, eNodeBs
and the eNodeB uses frequency
synchronization and is configured with the
Network Time Protocol (NTP) time source to
achieve time synchronization with the MME.
For details, see 3.10.1 eDRX Time
Synchronization Mechanism.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 4


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 1 About This Document

Change Change Description Parameter Affected


Type Change Entity

Editorial Added the reference of RF modules None N/A


change supporting NB-IoT to 3900 Series Base
Station Technical Description of 3900 Series
Base Station Product Documentation.
Revised descriptions in the document.

eRAN12.1 03 (2017-05-29)
This issue includes the following changes.
Change Change Description Parameter Affected
Type Change Entity

Feature Added the requirement that the None Macro and


change ENodeBFrameOffset.FddFrameOffset micro
and CellFrameOffset.FrameOffset eNodeBs
parameters must be set to the same
value in NB-IoT and LTE FDD or LTE
TDD co-site deployment scenarios.
For details, see 6.4.1 Requirements.

Reduced the actual minimum receive Added the Macro and


level in a cell by configuring delta- ENBCELLRSVD micro
RxLevMin, so that UEs in an area of PARA.RsvdU8Par eNodeBs
coverage level 2 can camp on the cell a17 parameter.
more easily.
For details, see 3.11 NB-IoT Coverage
Extension.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 5


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 1 About This Document

Change Change Description Parameter Affected


Type Change Entity

Enabled the backoff, access barring, and Added the Macro and
random access flow control functions PreambleSchEnh micro
and allowed the eNodeB to include the Switch option to eNodeBs
extendedWaitTime IE in RRC the
Connection Release messages when the CellAlgoSwitch.U
air interface is overloaded in a cell. lSchExtSwitch
For details, see 3.8 Admission Control, parameter.
Congestion Control, and Overload Added the
Control. UlRaUserSchOpt
Sw option to the
CellAlgoSwitch.U
lSchSwitch
parameter.
Added the
Extendedwaittime
Switch option to
the
CellAlgoSwitch.M
TCCongControlS
witch parameter.

Editorial Revised descriptions in the document. None N/A


change

eRAN12.1 02 (2017-04-26)
This issue includes the following changes.
Change Change Description Parameter Affected
Type Change Entity

Feature Enabled the time for the eNodeB to wait Added the Macro and
change an RRC Connection Setup Complete NbCellDlSchCEAl micro
message to be configurable by the go.UuMessageWait eNodeBs
NbCellDlSchCEAl- ingTimer
go.UuMessageWaitingTimer parameter. parameter.
For details, see 3.5.2 RRC Connection
Setup.

Enabled the maximum repetition count Added the Macro and


for NPDCCH CSS1 (CSS for paging) to PCCHCfg.MaxNu micro
be configurable by the mRepetitionForPa eNodeBs
PCCHCfg.MaxNumRepetitionFor- ging parameter.
Paging parameter. For details, see
3.6.4.3 Downlink Scheduling for
Initial Transmissions.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 6


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 1 About This Document

Change Change Description Parameter Affected


Type Change Entity

Enabled the PRACH start time for each Added the Macro and
coverage level to be configurable by the following micro
CellRachCECfg.PrachStartTime parameters: eNodeBs
parameter. For details, see 3.5.1 l RACHCfg.Prac
Random Access. hStartTimeCfgI
nd
l CellRachCECf
g.PrachStartTi
me

Enabled the PRACH detection threshold Added the Macro and


for each coverage level to be CellRachCECfg.P micro
configurable by the rachDetectionThld eNodeBs
CellRachCECfg.PrachDetectionThld parameter.
parameter. For details, see 3.5.1
Random Access.

Supported the normal access of NB-IoT Added the Macro and


UEs complying with 3GPP Release 13 following switches micro
(2017-03), and the reception of paging to the eNodeBs
messages by these UEs when they use GlobalProcSwitch.
Idle Mode eDRX stipulated in 3GPP UeCompatSwitch
Release 13 (2017-03). parameter:
l NbR13Compat
Sw
l HashedIdComp
atSw

Editorial None None N/A


change

eRAN12.1 01 (2017-03-08)
This issue includes the following changes.
Change Change Description Parameter Affected
Type Change Entity

Feature Added the limitation on the number of LTE None Macro and
change FDD RBs that can be reserved for NB-IoT in micro
LTE in-band deployment. The recommended eNodeBs
maximum number is 9. For details, see 3.2.3
LTE In-band Deployment.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 7


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 1 About This Document

Change Change Description Parameter Affected


Type Change Entity

Added descriptions about LOFD-001070 None Macro and


Symbol Power Saving providing fewer gains micro
when NB-IoT and LTE FDD cells share the eNodeBs
same PA. For details, see the following
sections:
l 4.1 MLBFD-12000101 Standalone
Deployment
l 4.2 MLBFD-12000102 LTE Guardband
Deployment
l 4.3 MLBFD-12000103 LTE In-band
Deployment

Enabled NB-IoT UEs complying with 3GPP None Macro and


TS 36.213 V13.3.0 (2016-09) to access NB- micro
IoT cells by selecting eNodeBs
DCI_SF_REP_NUM_COMP_SWITCH
under the CellAlgoSwitch.NbCellAlgoSwitch
parameter.

Added the low-precision frame number Added the Macro and


synchronization solution when Idle Mode TASM.LPF micro
eDRX is enabled and the NSYNCSW eNodeBs
TASM.CLKSYNCMODE parameter is set to parameter.
FREQ(FREQ), but the MME does not
support the premature sending of paging
messages to the eNodeB. An IEEE1588 V2
clock is configured for the eNodeB. The GPS
time provided by the IEEE1588 V2 clock
meets the synchronization precision
requirements posed by Idle Mode eDRX
between the eNodeB and MME. For details,
see the following sections:
l 3.10.1 eDRX Time Synchronization
Mechanism
l 7.4.1 Requirements
l 7.4.4 Data Preparation and Activation

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 8


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 1 About This Document

Change Change Description Parameter Affected


Type Change Entity

Editorial Optimized the formulas for calculating the None N/A


change NB-IoT frequency offsets and frequencies in
LTE in-band deployment. For details, see
3.3.1.2 PRB.
Revised descriptions in 6.3.1 RF Planning.
Added descriptions about admission control.
For details, see 3.8 Admission Control,
Congestion Control, and Overload Control.
Added configurations of RLC PDCP
parameter groups for user plane CIoT EPS
optimization. For details, see 6.4.4 Data
Preparation and Activation.

eRAN12.1 Draft B (2016-12-30)


This issue includes the following changes.

Change Change Description Parameter Affected


Type Change Entity

Feature Updated the impact of NB-IoT deployment in None Macro and


change LTE in-band mode on LTE FDD. For details, micro
see 5.3 MLBFD-12000103 LTE In-band eNodeBs
Deployment.

Editorial None None N/A


change

eRAN12.1 Draft A (2016-11-30)


This document is created for eRAN12.1.

1.5 Differences Between eNodeB Types


Feature Support by Macro, Micro, and LampSite eNodeBs
Feature ID Feature Name Supported Supported Supported
by Macro by Micro by
eNodeBs eNodeBs LampSite
eNodeBs

MLBFD-120001 NB-IoT Network Yes Yes No


Deployment

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 9


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 1 About This Document

Feature ID Feature Name Supported Supported Supported


by Macro by Micro by
eNodeBs eNodeBs LampSite
eNodeBs

MLBFD-12000101 Standalone Yes Yes No


Deployment

MLBFD-12000102 LTE Guardband Yes Yes No


Deployment

MLBFD-12000103 LTE In-band Yes Yes No


Deployment

MLBFD-120002 3GPP NB-IoT Yes Yes No


Specifications
Compliant

MLBFD-12000202 Single-tone Yes Yes No

MLBFD-12000203 Support of NB-IoT UE Yes Yes No

MLBFD-12000204 Data over NAS Yes Yes No

MLBFD-12100205 Data over User Plane Yes Yes No


(trial)

MLBFD-12000223 Physical Channel Yes Yes No


Management

MLBFD-12000224 DL Asynchronous Yes Yes No


HARQ

MLBFD-12000225 UL Asynchronous Yes Yes No


HARQ

MLBFD-12000226 Modulation: DL Yes Yes No


QPSK, UL QPSK/
BPSK

MLBFD-12000227 AMC Yes Yes No

MLBFD-12000228 RRC Connection Yes Yes No


Management

MLBFD-12000229 Broadcast of system Yes Yes No


information

MLBFD-12000230 Random Access Yes Yes No


Procedure

MLBFD-12000231 Paging Yes Yes No

MLBFD-12000232 Cell Access Radius up Yes Yes No


to 35 km

MLBFD-12000233 Admission Control Yes Yes No

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 10


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 1 About This Document

Feature ID Feature Name Supported Supported Supported


by Macro by Micro by
eNodeBs eNodeBs LampSite
eNodeBs

MLBFD-12000234 Basic Scheduling Yes Yes No

MLBFD-12000235 Uplink Power Control Yes Yes No

MLBFD-12000236 DRX Yes Yes No

MLBFD-12000237 Cell Selection and Re- Yes Yes No


selection

MLBFD-12000238 UL 2-Antenna Receive Yes Yes No


Diversity

MLBFD-12100240 DL 4-Antenna Yes No No


Transmit Diversity

MLBFD-12100242 Active Queue Yes Yes No


Management (AQM)

MLBFD-12100243 Congestion Control Yes Yes No

MLBFD-12100244 SCTP Congestion Yes Yes No


Control

MLOFD-120201 NB-IoT Coverage Yes Yes No


Extension

MLOFD-120220 Idle Mode eDRX Yes Yes No

MLOFD-120230 Multi-tone Yes Yes No

MLOFD-121202 UL 4-Antenna Receive Yes No No


Diversity

MLOFD-121204 SFN Yes Yes No

NOTE

The micro eNodeBs in this document refer to the BTS3912E.

Function Implementation in Macro, Micro, and LampSite eNodeBs


None

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 11


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 2 Overview

2 Overview

2.1 Background
The Internet of Things (IoT) is an important part of the information technology of the future.
IoT is expected to enable people-thing and thing-thing interconnections by combining
communications technologies and networks. There are three types of IoT scenarios, each with
different bandwidth, power, and connectivity requirements, as shown in Figure 2-1.

Figure 2-1 IoT applications

l High rate
These are services such as video surveillance and electronic billboards, where there is
access to an external power supply and there are no special requirements regarding
power consumption.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 12


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 2 Overview

l Moderate rate
These are services such as smart home appliances and Internet of Vehicles applications,
where there is access to an external power supply and there are still at least some
requirements regarding power consumption.
l Low rate
These are services such as wireless meter reading and industrial sensors, where there are
requirements for massive connections. Low rate services typically run on battery
powered devices, must be able to wait in standby mode for extremely long periods, and
run for extended periods on very little power. Low rate services must also be extremely
inexpensive.
Conventional wireless networks are not well designed for the huge number of low-rate
connections that IoT requires at such low costs and with very little power. Conventional
wireless networks are too expensive and too power hungry. 3GPP introduced Narrowband
Internet of Things (NB-IoT) to accommodate these scenarios.

2.2 Introduction
NB-IoT introduced a new radio interface technology for wireless IoT. It is mainly used for
low power, low rate scenarios that require deep coverage, and a massive volume of
connections.

2.3 Benefits
NB-IoT provides the following benefits:
l Maximum spectrum utilization
NB-IoT supports standalone deployment, LTE guardband deployment, and LTE in-band
deployment, fully utilizing spectrum resources and increasing spectral efficiency.
l Support for a large number of low-rate users
The low-rate, low-activity, machine-to-machine (M2M) application service model
supports a large number of users.
l Deep coverage
NB-IoT provides coverage enhancement with the help of repetitive data transmission and
power spectrum density (PSD) increase.
l Low power of UEs
The NB-IoT protocol stack is optimized for streamlined signaling processing and
signaling interaction, reducing UE power consumption.

2.4 Architecture
Figure 2-2 illustrates the end-to-end network architecture of NB-IoT.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 13


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 2 Overview

Figure 2-2 Network architecture of NB-IoT

l NB-IoT UE
Communicates with the eNodeB over the air interface.
l eNodeB
Performs functions such as air interface access processing and cell management. The
eNodeB communicates with the IoT evolved packet core (EPC) through an S1-lite
interface and sends non-access stratum (NAS) data to the IoT EPC for processing.
l IoT EPC
Interacts with the NAS of the UE and forwards IoT data to the IoT platform for
processing.
l IoT platform
Converges IoT data from access networks and forwards different types of data to their
corresponding application servers.
l Application server
Receives and processes IoT data.

2.5 Feature Overview


NB-IoT is a new narrowband radio technology designed to address the requirements of the
IoT.

2.5.1 MLBFD-12000101 Standalone Deployment


Standalone deployment is a deployment scenario in which operators deploy NB-IoT using
existing idle spectrum resources. These resources can be operator spectrum fragments with
non-standard bandwidths or refarmed from other radio access technologies (RATs). For
details, see 3.2.1 Standalone Deployment.

2.5.2 MLBFD-12000102 LTE Guardband Deployment


Guardband deployment is a deployment scenario in which operators deploy NB-IoT in guard
bands within existing LTE spectrum resources. For details, see 3.2.2 LTE Guardband
Deployment.

2.5.3 MLBFD-12000103 LTE In-band Deployment


In-band deployment is a deployment scenario in which operators deploy NB-IoT using
existing LTE FDD in-band RBs. For details, see 3.2.3 LTE In-band Deployment.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 14


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 2 Overview

2.5.4 MLBFD-12000202 Single-tone


Single-tone transmission is used on uplink physical channels for NB-IoT. It occupies a single
subcarrier of 3.75 or 15 kHz.
Single-tone transmission is mandatory for UEs. The narrowband physical random access
channel (NPRACH) uses a 3.75 kHz subcarrier. The narrowband physical uplink shared
channel (NPUSCH) uses a 15 kHz subcarrier.

2.5.5 MLBFD-12000203 Support of NB-IoT UE


The requirements of NB-IoT on UEs are defined in 3GPP TS 36.306 (Release 13).
During scheduling, eNodeBs must consider the configured radio access capabilities of the
UEs.

Table 2-1 Downlink physical layer parameter values set by the field ue-Category-NB
UE Category Max. DL-SCH Max. Bits of a DL- Total Soft
Transport Block SCH Transport Channel Bits
Bits Received Block Received
Within a TTI Within a TTI

NB1 680 680 2112

Table 2-2 Uplink physical layer parameter values set by the field ue-Category-NB
UE Category Max. UL-SCH Transport Max. Bits of a UL-SCH
Block Bits Transmitted Transport Block
Within a TTI Transmitted Within a
TTI

NB1 1000 1000

Table 2-3 Layer-2 buffer size set by the field ue-Category-NB


UE Category Layer-2 Buffer Size (Bytes)

NB1 4000

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 15


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 2 Overview

Table 2-4 Half-duplex FDD operation type set by the field ue-Category-NB
UE Category Half-Duplex FDD Operation Type

NB1 Type B
NOTE
In this operation type, uplink and downlink
transmission are separated by a guard interval,
during which UEs neither monitor the
Narrowband Physical Downlink Control Channel
(NPDCCH) nor perform uplink transmission.

2.5.6 MLBFD-12000204 Data over NAS


This feature implements the control plane Cellular Internet of Things (CIoT) EPS
optimizations stipulated in 3GPP TS. 24.301. This feature involves only the control plane.
The UE and eNodeB transmit user data with no need for data radio bearers (DRBs). Figure
2-3 shows the control plane protocol stack, in which the RLC and RRC layers interact directly
without the PDCP layer and the NAS is responsible for data security.

Figure 2-3 Protocol stack for the control plane CIoT EPS optimization function

Uplink data is carried by NAS messages in uplink RRC messages, and downlink data is
carried by NAS messages in downlink RRC messages.

2.5.7 MLBFD-12100205 Data over User Plane (Trial)


NOTE

Before using this feature, read 1.2 Disclaimer for Trial Features.

This feature implements the user plane CIoT EPS optimization function stipulated in 3GPP
TS. 36.300.
Unlike the control plane CIoT EPS optimization function, the user plane CIoT EPS
optimization function involves the PDCP layer between the RRC and RLC layers, as shown
in Figure 2-4. The PDCP layer supports data encryption and integrity protection for data
transmitted over the Uu interface. Service data is transmitted by the default bearer on the user
plane. Before data transmission, one or two DRBs are established between the UE and
eNodeB. To reduce signaling overhead of access procedures and meet the low power
consumption requirement for UEs, this function has simplified the access procedures with

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 16


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 2 Overview

support for suspension of RRC connections and UE context storage on the eNodeB and UE.
When the UE accesses the network again, the UE and eNodeB can quickly restore the UE
context, with no need for security activation and RRC reconfiguration procedures. Message
interactions over the Uu interface are reduced as a result. When the UE moves between the
coverage areas of different eNodeBs, the UE context is transmitted over the X2 interface to
recover the RRC connection. For details about this feature, see 3GPP TS 36.300.

Figure 2-4 Control plane protocol stack for the user plane CIoT EPS optimization function

NB-IoT UEs must support the control plane CIoT EPS optimization function and can
optionally support the user plane CIoT EPS optimization function.

2.5.8 MLBFD-12000226 Modulation: DL QPSK, UL QPSK/BPSK


This feature provides the following modulation schemes that can be used by eNodeBs and
UEs:
l Quadrature phase shift keying (QPSK)
This modulation scheme applies to both uplink and downlink channels.
l Binary phase shift keying (BPSK)
This modulation scheme applies only to uplink channels.

This feature allows eNodeBs and UEs to select a modulation scheme based on the current
channel conditions, balancing the user data rate against the frame error rate (FER) during
transmission. For details about this feature, see 3GPP TS 36.211.

2.5.9 MLBFD-12000227 AMC


Adaptive modulation and coding (AMC) allows an eNodeB to adaptively select the optimal
modulation and coding scheme (MCS) based on channel conditions and UE coverage level.
AMC helps improve spectral efficiency, increase throughput, and meet quality of service
(QoS) requirements without placing additional strain on system resources or impacting the
transmit power.

2.5.10 MLBFD-12000228 RRC Connection Management


The RRC connection is a layer 3 connection set up between the eNodeB and a UE. RRC
connection management involves layer 3 connection setup, maintenance, and release. For
details, see 3.5 Connection Management.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 17


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 2 Overview

2.5.11 MLBFD-12000229 Broadcast of System Information


System information (SI) includes:
l Basic information for UEs to access NB-IoT networks, such as basic radio and channel
parameters
l Information about cell selection and reselection parameters used by UEs in RRC_IDLE
mode
l Information about neighboring cells

SI broadcast over the broadcast control channel (BCCH) can be read by UEs in RRC_IDLE
mode, without requiring RRC connection establishment. For details, see 3.4.9 System
Information Broadcast.

2.5.12 MLBFD-12000223 Physical Channel Management


A physical channel is used for coding, hybrid automatic repeat request (HARQ) processing,
modulation, multi-antenna processing, and mapping signals to the appropriate physical time-
frequency resources. A transport channel at the transport layer can be mapped to one or
multiple physical channels at the physical layer.

For details about this feature, see 3.1 Basic Concepts.

2.5.13 MLBFD-12000224 DL Asynchronous HARQ


HARQ helps resist transmission errors and increases system capacity. With downlink
asynchronous HARQ, a downlink retransmission can be performed a certain number of
subframes (specified in the 3GPP specifications) after the initial transmission or a previous
retransmission. NB-IoT supports only a single downlink HARQ process.

2.5.14 MLBFD-12000225 UL Asynchronous HARQ


With uplink asynchronous HARQ, an uplink retransmission can be performed a number of
subframes (specified in 3GPP specifications) after the initial transmission or a previous
retransmission. NB-IoT supports only a single uplink HARQ process.

2.5.15 MLBFD-12000230 Random Access Procedure


Random access is used for UE uplink synchronization and connection setup requests by UEs.
It is used for the following three events:
l A UE in RRC_IDLE mode attempts its first access to the network.
l A UE in RRC_CONNECTED mode is out of synchronization in the uplink but has
received downlink data.
l A UE in RRC_CONNECTED mode is out of synchronization in the uplink and has
uplink data to transmit.

For details about this feature, see 3.5.1 Random Access.

2.5.16 MLBFD-12000231 Paging


In a paging procedure, paging messages are sent to a particular UE in RRC_IDLE mode, or to
inform all UEs in RRC_IDLE mode of SI updates. For details, see 3.4.8 Paging.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 18


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 2 Overview

2.5.17 MLBFD-12000232 Cell Access Radius up to 35 km


To improve radio network coverage, 3GPP TS 36.211 (Release 13) defines two types of cyclic
prefix (CP) lengths for NPRACH subframes: 66.7 s and 266.7 s. When the CP length is
266.7 s, the maximum cell radius is 35 km.

2.5.18 MLBFD-12000233 Admission Control


When a new service attempts to access a cell, admission control checks the limits of the
system resources, including load and user volume. If the system is overloaded, the service
request is rejected. If the maximum allowable user volume has been reached, the admission
fails, and the involved UE attempts to preempt resources allocated to other UEs. A UE
initiating an RRC Connection Request with the cause value of "mo-Exception-Data" can
preempt resources of UEs that include a cause value other than "mo-Exception-Data" in the
RRC Connection Request message.

2.5.19 MLBFD-12000234 Basic Scheduling


This feature covers scheduling for NPDCCH, Narrowband Physical Downlink Shared
Channel (NPDSCH), and NPUSCH transmission. This feature implements data transmission
to and reception from NB-IoT UEs with different coverage levels, ensuring normal service
provisioning within a certain capacity limit. For details, see 3.6 Scheduling.

2.5.20 MLBFD-12000235 Uplink Power Control


NB-IoT supports only open-loop power control in the uplink for the NPUSCH and NPRACH.

Power control for the NPUSCH decreases interference on neighboring cells and increases the
data rates of UEs at the local cell edge while ensuring cell throughput.

Power control for the NPRACH enables UEs to use the optimal low power to send preambles
while ensuring the random access success rate, thereby decreasing interference on
neighboring cells and decreasing UE power consumption.

For details about uplink power control, see 3.7.2 Uplink Power Control.

2.5.21 MLBFD-12000236 DRX


Discontinuous reception (DRX) is a technology in which a UE in RRC_CONNECTED mode
can switch between active and sleep states to save power. When the UE in
RRC_CONNECTED mode needs to receive downlink data or signaling, the UE turns on its
receiver and enters the active state. In other situations, the UE turns off its receiver and enters
the sleep state to reduce power consumption. For details about DRX, see 3.9 DRX.

2.5.22 MLBFD-12000237 Cell Selection and Re-selection


Cell selection and reselection is the process by which UEs in RRC_IDLE mode determine
which cells to camp on so that they can have the best QoS in the NB-IoT system. For details,
see 3.4.6 Cell Selection and Reselection.

2.5.23 MLBFD-12000238 UL 2-Antenna Receive Diversity


Receive diversity is a multiple-antenna technology designed to improve reception, overcome
fading and interference, expand system capacity, and increase data rates.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 19


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 2 Overview

2.5.24 MLBFD-12100240 DL 4-Antenna Transmit Diversity


Transmit diversity uses multiple antennas to transmit redundant signals, after encoding based
on the low correlation between the time and frequency characteristics of radio waves
transmitted on different spatial channels. These signals and their copies, with their different
degrees of fading, are then combined at the receiver end. The diversity gains delivered by this
procedure improve transmission reliability. For details, see 3.14 Multiple-Antenna
Transmission.

2.5.25 MLBFD-12100242 Active Queue Management (AQM)


AQM, which proactively controls the queue length, is introduced to minimize congestion.
When air interface resources are insufficient, AQM estimates the length of the data packet
queue of bearer services and adaptively drops TCP data packets in case of congestion.
Congestion control at the sender is triggered in advance to prevent congestion deterioration.
For details, see AQM Feature Parameter Description.

2.5.26 MLBFD-12100243 Congestion Control


When a large number of NB-IoT UEs simultaneously access the network, the eNodeB triggers
the backoff function on the RACH or triggers access barring based on the network congestion
status. This reduces the probability of excessive signaling messages on the network. For
details, see 3.8 Admission Control, Congestion Control, and Overload Control.

2.5.27 MLBFD-12100244 SCTP Congestion Control


SCTP congestion control uses downlink SCTP congestion detection, backpressure
mechanism, and signaling congestion control to relieve signaling congestion. SCTP
congestion control prevents signaling bursts from causing an eNodeB breakdown. For details,
see SCTP Congestion Control Feature Parameter Description.

2.5.28 MLOFD-120220 Idle Mode eDRX


Idle Mode eDRX supports a long paging cycle. The UE negotiates with the mobility
management entity (MME) about the paging cycle and periodically monitors the paging
channel. A long period results in a lower monitoring overhead. When there is a mobile-
terminated (MT) service request for the UE in RRC_IDLE mode, the MME calculates when
the UE will monitor the paging channel. Before this time arrives, the MME sends a paging
message to the eNodeB, and the eNodeB sends this message to the UE within the paging
transmission window (PTW). Figure 2-5 shows the procedure.

Figure 2-5 Paging procedure for UEs enabled with the eDRX and in RRC_IDLE mode

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 20


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 2 Overview

Idle Mode eDRX requires time synchronization in hyper system frame number (HSFN)
between the eNodeB and MME, as described in 3.10 Idle Mode eDRX.

2.5.29 MLOFD-120201 NB-IoT Coverage Extension


This feature provides coverage enhancement by increasing the PSD and by using repeated
transmission.
l PSD increase
The system bandwidth for NB-IoT is 180 kHz, much smaller than that of LTE FDD.
Given the same transmit power, the PSD for NB-IoT is significantly higher than that of
LTE FDD, even more so in the uplink, where the bandwidth required for a single
subcarrier is so small.
l Repetition of transmission
An NB-IoT cell can be maximally divided into three coverage levels based on the signal
strength. In areas with good coverage, high data rates can be reached using a few
repetitions or even without repetition. In areas with poor coverage, coverage
performance can be ensured by using more repetitions. The data rates in these areas are
low.

For details about this feature, see 3.11 NB-IoT Coverage Extension.

2.5.30 MLOFD-120230 Multi-tone


3GPP specifications stipulate that NB-IoT should support single-tone and multi-tone
transmission in the uplink. Single-tone transmission is mandatory for UEs, while multi-tone
transmission is optional. There are three types of multi-tone transmission: 3-tone, 6-tone, and
12-tone. This means that an eNodeB can allocate 3, 6, or 12 subcarriers (15 kHz each) at a
time for uplink data transmission. The eNodeB flexibly schedules multi-tone-capable UEs to
reduce the data transmission delay and UE power consumption. For details about multi-tone
transmission, see 3.12 Multi-tone.

2.5.31 MLOFD-121202 UL 4-Antenna Receive Diversity


This feature is similar to MLBFD-12000238 UL 2-Antenna Receive Diversity. The primary
difference is that the eNodeB requires four receive antennas in this feature. For details, see
3.13 Multiple-Antenna Reception.

2.5.32 MLOFD-121204 SFN


SFN allows physical cells served by multiple radio frequency (RF) modules working on the
same frequency to be combined into one logical cell. This cell is called an SFN cell and the
area served by an RF module is called a physical cell. With SFN, different cells' signals that
are originally interfered by one another turn into enhanced multipath signals from one cell.
Therefore, SFN offers the following benefits:

l Increases the SINR at the cell edge


l Decreases interference from intra-frequency neighboring cells
l Improves user experience at the cell edge

For details, see SFN Feature Parameter Description.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 21


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

3 Technical Description

3.1 Basic Concepts


The basic concepts of NB-IoT explained in this section include the physical channels, the
frequency-domain structure, time-domain structure, and coverage and aggregation levels.

3.1.1 Physical Channels


There are three types of downlink physical channels for NB-IoT:
l Narrowband Physical Broadcast Channel (NPBCH)
Responsible for transmitting master information blocks (MIBs)
l NPDCCH
Responsible for carrying the downlink control information (DCI)
l NPDSCH
Responsible for carrying downlink data.
There are two types of uplink physical channels for NB-IoT:
l NPUSCH
Responsible for carrying uplink data
l NPRACH
Responsible for carrying random access messages
Figure 3-1 illustrates the mapping between the physical and transport channels.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 22


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Figure 3-1 Mapping between the physical and transport channels

3.1.2 Frequency-Domain Structure

Frequency-Domain Structure of Downlink Physical Channels


Each NB-IoT downlink physical channel has a bandwidth of 180 kHz. It is divided into 12
subcarriers, each of which occupies 15 kHz, as shown in Figure 3-2.

Figure 3-2 Frequency-domain structure of downlink physical channels

Frequency-Domain Structure of Uplink Physical Channels


Uplink physical channels support single-tone and multi-tone transmission. Single-tone
transmission occupies a single subcarrier of either 3.75 kHz or 15 kHz. There are three types
of multi-tone transmission: 3-tone, 6-tone, and 12-tone. This means that an eNodeB can
allocate 3, 6, or 12 subcarriers (15 kHz each) at a time for uplink data transmission. An NB-
IoT uplink physical channel has a bandwidth of 180 kHz. It can be divided into 12 subcarriers

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 23


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

(15 kHz each) or 48 subcarriers (3.75 kHz each). In the current version, the NPUSCH
supports multi-tone transmission and 15 kHz single-tone transmission, and the NPRACH
supports only 3.75 kHz single-tone transmission.

Figure 3-3 Frequency-domain structure of uplink physical channels

3.1.3 Time-Domain Structure


Time-Domain Structure of Downlink Physical Channels
Downlink physical channel resources in the time domain are scheduled in units of subframes.
Each subframe lasts 1 ms and corresponds to two timeslots. Each frame consists of 10
subframes, and each super frame consists of 1024 frames. Figure 3-4 shows the details.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 24


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Figure 3-4 Time-domain structure of downlink physical channels

Time-Domain Structure of Uplink Physical Channels


Uplink physical channel resources in the time domain are measured in timeslots. Each
timeslot lasts 2 ms for 3.75 kHz subcarrier spacing and lasts 0.5 ms for 15 kHz subcarrier
spacing. Uplink physical channel resources are scheduled in units of resource units (RUs).
The duration of each RU varies with the scenarios, as described in Table 3-1.

Table 3-1 RU duration in different scenarios


NPUSC Subcarri Number Number Duration Duration Scenario
H Format er of of of Each of Each
Spacing Subcarri Timeslot Timeslot RU (ms)
ers s per RU (ms)

1 (for 3.75 kHz 1 16 2 32 Single-


common tone
data 15 kHz 1 16 0.5 8
transmissi 3 8 4 Multi-tone
on)
6 4 2

12 2 1

2 (for UCI 3.75 kHz 1 4 2 8 Single-


transmissi tone
on) 15 kHz 1 4 0.5 2

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 25


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

NOTE

The current version does not support 3.75 kHz single-tone transmission over the NPUSCH, including
the NPUSCH for uplink control information (UCI) transmission.

3.1.4 Coverage Level


Previously, if all the UEs in a given coverage area were using the same power and MCS, to
ensure reliable transmission, the power consumption of the UEs would be increased and
network capacity would be decreased. With the "coverage level" concept, each NB-IoT cell is
divided into different coverage levels. The UE selects an appropriate coverage level based on
signal strength, to process services. Low coverage levels have strong signals and high rates.
High coverage levels have weak signals and low rates.

3.1.5 Aggregation Level


The NPDCCH resource unit allocated to a UE is the control channel element (CCE). Each
CCE occupies half of the frequency-domain resources of an RB. NB-IoT supports two
aggregation levels, 1 and 2, which indicate the number of CCEs required by DCI
transmission. Aggregation level 2 indicates that the DCI transmission occupies two CCEs,
that is, the entire frequency-domain resources of an RB.

3.2 Deployment Mode

3.2.1 Standalone Deployment


This section describes the MLBFD-12000101 Standalone Deployment feature.

There are two options for standalone deployment, refarming or the use of idle spectrum.

l Refarming
Refarming enables part of the spectrum for a RAT to be used by NB-IoT, without
affecting the functionality of that RAT. Typically, GSM spectrum resources are refarmed
for NB-IoT, with guard bands used to set them apart. The GSM network is then
replanned to minimize the impact of the refarming on GSM services.
The following figure uses 1:1 co-site deployment as an example. In this example, two
GSM carriers are allocated to the NB-IoT network with a guard band of 100 kHz
reserved between NB-IoT and GSM. In refarming deployment, the GSM frequencies
across the entire buffer zone area need to be refarmed to reduce interference even if NB-
IoT is not deployed.
NOTE

If the adjacent GSM frequency is a BCCH frequency, a guard band of 300 kHz is reserved.

Figure 3-5 Refarming deployment

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 26


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

l Using idle spectrum resources


Operators may own spectrum resources with non-standard bandwidths which are not in
use because they do not meet the communications requirements of certain RATs. NB-IoT
can use these resources for narrowband communications. Deploying NB-IoT on idle
spectrum resources requires sufficient guard bands be reserved between NB-IoT and
those RATs, preventing existing networks from being affected. The application scenarios
are as follows:
GSM idle spectrums are used to deploy the NB-IoT network, as shown in Figure
3-6.

Figure 3-6 NB-IoT deployment on GSM idle spectrum resources

UMTS idle spectrums are used to deploy the NB-IoT network, as shown in Figure
3-7.

Figure 3-7 NB-IoT deployment on UMTS idle spectrum resources

LTE idle spectrums are used to deploy the NB-IoT network, as shown in Figure
3-8.

Figure 3-8 NB-IoT deployment on LTE idle spectrum resources

Whether to use standalone deployment is specified by the PRB.DeployMode parameter.


When standalone deployment is used, the center frequency of the NB-IoT cell carrier must be
a multiple of 100 kHz, and the value of the PRB.DlFreqOffset parameter must be
NEG_0DOT5(NEG_0DOT5).

3.2.2 LTE Guardband Deployment


This section describes the MLBFD-12000102 LTE Guardband Deployment feature.
To prevent adjacent-carrier interference or inter-RAT interference for existing RATs, in
addition to the useable bandwidth assigned for regular use, a certain amount of extra
bandwidth must be reserved as a buffer zone. This bandwidth is referred to as a "guard band".

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 27


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

The guard band between carriers is generally at least 180 kHz. NB-IoT is a narrowband
communication technology, requiring just 180 kHz of bandwidth for the uplink and another
180 kHz for the downlink. Services can be deployed on the guard bands of existing RATs,
eliminating the need for new spectrum resources and improving the utilization of old
spectrum.
In guard band deployment, NB-IoT services are now deployed on LTE FDD guard bands, as
shown in Figure 3-9. This deployment mode must meet the requirements specified in 3GPP
TS 36.101 (Release 13).

Figure 3-9 LTE guard band deployment

When LTE FDD cells use a bandwidth greater than or equal to 10 MHz, the guard bands
provide enough bandwidth to deploy NB-IoT. Figure 3-10 is an example of LTE guard band
deployment on 10 MHz of LTE FDD bandwidth. In accordance with 3GPP TS 36.802
(Release 13), LTE guard band deployment requires that the LTE FDD cell bandwidth be at
least 5 MHz. When LTE FDD cells use a 5 MHz bandwidth, LTE guard band deployment
makes the guard band become insufficient, causing interference to adjacent frequency bands.
Therefore, an LTE FDD cell bandwidth of at least 10 MHz is required for LTE guard band
deployment in this version.

Figure 3-10 LTE guard band deployment on 10 MHz of LTE FDD bandwidth

NOTE

For details about the LTE spectrum template, see 3GPP TS 36.104 V10.11.0.

Whether to use LTE guard band deployment is specified by the PRB.DeployMode parameter.
In LTE guard band deployment, the LTE FDD system bandwidth and center frequency must
be specified for NB-IoT deployment position verification. That is, the PRB.LteBandWidth
and PRB.LteDlEarfcn parameters must be configured.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 28


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

NOTE

LTE guard band deployment must comply with the local laws and regulations. The uplink and downlink
E-UTRA absolute radio frequency channel numbers (EARFCNs) and frequency offsets for NB-IoT must
be planned with the assistance of Huawei technical support.

3.2.3 LTE In-band Deployment


This section describes the MLBFD-12000103 LTE In-band Deployment feature.

In-band deployment is a typical deployment scenario, in which operators deploy NB-IoT


using existing LTE FDD in-band RBs, as shown in Figure 3-11.

Figure 3-11 LTE in-band deployment

LTE in-band deployment has the following requirements:


l Hardware
LTE in-band deployment requires that NB-IoT share main control boards, radio
frequency (RF) modules, and antenna systems with LTE FDD. When an LTE FDD cell
becomes faulty, the mutual NB-IoT cell also becomes unavailable. An NB-IoT cell fault,
however, does not affect the LTE FDD cell.
l LTE FDD system bandwidth
In accordance with 3GPP TS 36.802 (Release 13), LTE in-band deployment requires that
the LTE FDD cell bandwidth be at least 3 MHz. The in-band deployment of NB-IoT in
LTE cells using 3 MHz bandwidth has a large impact on LTE FDD performance.
Therefore, an LTE FDD cell bandwidth of at least 5 MHz is required for LTE in-band
deployment in this version. Whether to use LTE in-band deployment is specified by the
PRB.DeployMode parameter. The ID of an LTE FDD cell where in-band RBs are
reserved for NB-IoT is specified by the PRB.LteCellId parameter.
l NB-IoT RB positions
LTE in-band deployment requires that LTE FDD cells be established prior to NB-IoT
cells and uplink/downlink RBs in LTE FDD cells be reserved for NB-IoT. NB-IoT RB
positions must meet the requirements specified in 3GPP TS 36.101 (Release 13).
Downlink RB positions available and recommended for NB-IoT are listed in the
following table.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 29


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Table 3-2 Downlink RB positions

LTE FDD Downlink RB Positions Downlink RB Positions


Cell Available for NB-IoT Recommended for NB-
Bandwidth IoT

5 MHz 2, 7, 17, 22 7, 17

10 MHz 4, 9, 14, 19, 30, 35, 40, 45 19, 30

15 MHz 2, 7, 12, 17, 22, 27, 32, 42, 47, 52, 57, 32, 42
62, 67, 72

20 MHz 4, 9, 14, 19, 24, 29, 34, 39, 44, 55, 60, 44, 55
65, 70, 75, 80, 85, 90, 95

Uplink RB positions recommended for NB-IoT are at band edges excluding the positions
for the LTE FDD PRACH and static PUCCH. If the PUCCH is dynamically configured
(that is, if the PucchSwitch option of the CellAlgoSwitch.PucchAlgoSwitch parameter
is selected), uplink RB positions recommended are at the first or last RB of the available
resources of LTE FDD.
If NB-IoT resources conflict with LTE FDD PRACH resources, NB-IoT cells
cannot work properly.
If NB-IoT positions conflict with static LTE FDD PUCCH positions, less PUCCH
resources will be available.
l LTE FDD RB reservation for NB-IoT
LTE FDD RB reservation policies for NB-IoT are controlled by the
CellRbReserve.RbRsvType and CellRbReserve.RbRsvMode parameters. The first
parameter specifies whether uplink or downlink RBs are reserved. The second parameter
specifies whether the reserved RBs are used for NB-IoT deployment.
It is recommended that no more than nine RBs be reserved for NB-IoT in an LTE FDD
cell. If more than nine RBs are reserved, only nine RBs can take effect as follows:
a. RBs reserved for NB-IoT deployment take effect preferentially.
b. RBs take effect in ascending order of the CellRbReserve.Index parameter value.
In downlink, NB-IoT subcarriers are orthogonal to LTE FDD subcarriers and therefore
no guardbands are required between them.
In uplink, NB-IoT NPRACH subcarriers are not orthogonal to LTE FDD subcarriers
because an NPRACH can use only a 3.75 kHz subcarrier for single-tone transmission.
RBs adjacent to NB-IoT RBs can be used as guardbands for interference mitigation. In
practice, however, RBs are not reserved for this purpose because the impact of
interference is not greater than the impact of reservation of one or two RBs.
l NB-IoT's conflict avoidance for LTE FDD
[Uplink]
If uplink NB-IoT RBs conflict with LTE FDD SRS resources, there will be interference
between them. To enable NB-IoT's conflict avoidance for LTE FDD, the
PRB.UlAllSymbolSendFlag parameter can be set to FALSE. Under this setting,
however, uplink NB-IoT capacity may decrease by 8% to 20%.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 30


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

To determine whether an LTE FDD cell has SRS resources, you can check the
SRSCFG.SrsCfgInd parameter. If it is set to BOOLEAN_TRUE, the LTE FDD cell has
SRS resources.
If uplink NB-IoT RBs are more closer to the band edge while LTE FDD PUCCH
resources are more closer to the band center, there will be no conflict between uplink
NB-IoT RBs and LTE FDD SRS resources.
[Downlink]
Downlink NB-IoT RB resources must be punctured (reserved) for LTE FDD PDCCH
and cell-specific reference signal (CRS) according to 3GPP TS 36.211 (Release 13).
Currently, three symbols are reserved for PDCCH, as shown in the following figure.

Figure 3-12 Downlink RB resources

In addition, the PCIs of NB-IoT and LTE FDD cells must leave the same remainder after
being divided by a number so that the NB-IoT cell can use LTE FDD CRS measurement
results. To simplify network planning, the current version requires that NB-IoT and LTE
FDD cells use the same PCI. The PCI is specified by the Cell.PhyCellId parameter.

3.3 Cell Management

3.3.1 Related Concepts


Figure 3-13 shows the concepts related to cell management.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 31


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Figure 3-13 Cell-related concepts

3.3.1.1 Cell
A cell is an area where wireless communications services are provided. It is a fundamental
unit of a radio network. An NB-IoT cell is added by running the ADD CELL command with
the Cell.NbCellFlag parameter set to TRUE(TRUE). All the cells together jointly cover the
entire radio network. In the current version, an NB-IoT cell can only be a normal cell.

3.3.1.2 PRB
As a carrier in an NB-IoT cell, the physical resource block (PRB) configuration consists of
the identity of the NB-IoT cell served by the carrier, the deployment mode, and EARFCN-

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 32


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

related information. A PRB can be added by running the ADD PRB command and is
configured as required.

NOTE

In the current version, each NB-IoT cell corresponds to a single PRB. In later versions, one NB-IoT cell
can correspond to multiple PRBs.

Cell Frequency Band


The frequency bands supporting NB-IoT are stipulated in 3GPP TS 36.101 (Release 13). The
frequency band of a specific NB-IoT cell is specified by the PRB.FreqBand parameter.

Cell Bandwidth
NB-IoT cells have a fixed bandwidth of 180 kHz.

Cell PRB Center Frequency


The downlink center frequency of the PRB for a cell can be calculated using the following
formula:

FDL_loT = FDL_low + 0.1 x (NDL NOffs-DL) + 0.0025 x (2 x MDL + 1)

l FDL_low and NOffs-DL are defined in 3GPP TS 36.104 (Release 13).


l NDL is specified by the PRB.DlEarfcn parameter.
l MDL is specified by the PRB.DlFreqOffset parameter.

The uplink center frequency of the PRB for a cell can be calculated using the following
formula:

FUL_loT = FUL_low + 0.1 x (NUL NOffs-UL) + 0.0025 x (2 x MUL)

l FUL_low and NOffs-UL are defined in 3GPP TS 36.104 (Release 13).


l NUL is specified by the PRB.UlEarfcn parameter and MUL is specified by the
PRB.UlFreqOffset parameter if PRB.UlEarfcnCfgInd is set to CFG(Configure).
l NUL and MUL are automatically calculated if PRB.UlEarfcnCfgInd is set to
NOT_CFG(Not configure).

In LTE in-band deployment, operators deploy NB-IoT using existing LTE FDD in-band RBs,
and therefore the PRB center frequency of an NB-IoT cell must be consistent with the RB
center frequency of the corresponding LTE FDD cell. The NB-IoT frequency offset and
frequency are calculated using the following method:

In the downlink:

Obtain the downlink frequency offset. The specific offset relates to the LTE FDD cell
bandwidth and RB position, as described in Table 3-3, which complies with 3GPP TS 36.213
(Release 13).

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 33


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Table 3-3 NB-IoT downlink frequency offset in LTE in-band deployment

LTE FDD Cell RB Position Downlink


Bandwidth Frequency
Offset

5 MHz 2 and 7 2

17 and 22 1

10 MHz 4, 9, 14, and 19 0

30, 35, 40, and 45 1

15 MHz 2, 7, 12, 17, 22, 27, and 32 2

42, 47, 52, 57, 62, 67, and 72 1

20 MHz 4, 9, 14, 19, 24, 29, 34, 39, and 44 0

55, 60, 65, 70, 75, 80, 85, 90, and 95 1

Then use the following formulas to calculate the downlink frequency:

l DlRBRsvIndex < NRB/2, NbDlEarfcn = LteDlEarfcn + (180 x DlRBRsvIndex 90 x


NRB + 90 2.5 x (2 x NbDlFreqOffset + 1) 7.5)/100
l DlRBRsvIndex NRB/2, NbDlEarfcn = LteDlEarfcn + (180 x DlRBRsvIndex 90 x
NRB + 90 2.5 x (2 x NbDlFreqOffset + 1) +7.5)/100

In the uplink:

First use the following formula to calculate the uplink frequency, and rounds the calculated
value to an integer:

NbUlEarfcn = LteUlEarfcn + (180 x UlRBRsvIndex 90 x NRB + 90 + 50)/100

Then use the following formula to calculate the uplink frequency offset based on the
calculated uplink frequency:

NbUlFreqOffset = 20 x LteUlEarfcn + 36 x UlRBRsvIndex 18 x NRB + 18 20 x


NbUlEarfcn

l NRB is the number of RBs of the LTE FDD cell.


l DlRBRsvIndex is the index of a downlink RB reserved for NB-IoT deployment.
l UlRBRsvIndex is the index of an uplink RB reserved for NB-IoT deployment.
l LteDlEarfcn is the downlink E-UTRA absolute radio frequency channel number
(EARFCN) of the LTE FDD cell.
l NbDlEarfcn is the downlink EARFCN of the NB-IoT cell.
l NbDlFreqOffset is the downlink frequency offset of the NB-IoT cell.
l LteUlEarfcn is the uplink EARFCN of the LTE FDD cell.
l NbUlEarfcn is the uplink EARFCN of the NB-IoT cell.
l NbUlFreqOffset is the uplink frequency offset of the NB-IoT cell.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 34


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

3.3.1.3 Sector
A sector is the radio coverage area of an antenna. Sectors are added by running the ADD
SECTOR command. Each sector uses one or more radio carriers to provide coverage. Sectors
are combined with carriers to form cells.

NOTE

For a co-MPT base station, if services of different RATs are carried on the same transmit channel,
configure the same SECTOR MO for these RATs.

A sector can be omnidirectional or directional, depending on the antenna type. The following
table describes the sector types.

Sector Definition Benefits


Type

Omnidirecti An omnidirectional sector uses an In light-traffic areas, the


onal sector omnidirectional antenna to provide a 360 deployment of
circular coverage area with the antenna as omnidirectional sectors
the coverage center. reduces the investment in
antenna equipment.

Directional Directional sectors use directional antennas In heavy-traffic areas, the


sector for coverage. Each directional antenna deployment of directional
covers a 60 or 120 sector area when six or sectors supports large traffic
three sectors, respectively, are configured on volume. In addition,
an eNodeB. The azimuth of each sector is directional sectors support
slightly greater than 60 or 120 degrees. The more flexible area and
overlapping ensures seamless coverage. sector planning.

3.3.1.4 Sector Equipment


Sector equipment is a set of antennas used for the same sector. A sector is linked to a set of
antennas comprising a specific piece of sector equipment by running the ADD SECTOR or
ADD SECTOREQM command.

NOTE

For a co-MPT base station, if services of different RATs are carried on the same transmit channel,
configure the SECTOREQM MO by RAT.

3.3.1.5 RF Modules
RF modules include RRUs and RFUs. An RF module is added by running the ADD RRU
command. After execution of this command, the ADD RRUCHAIN command must be
executed to specify the CPRI ports on baseband processing units (BBPs) for connecting the
added RF module.

3.3.1.6 Baseband Equipment


A piece of baseband equipment consists of one or more BBPs.
A BBP is added by running the ADD BRD command. It can be added to a piece of baseband
equipment by running the ADD BASEBANDEQM command.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 35


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

In NB-IoT eNodeBs, a piece of baseband equipment must support both uplink and downlink
transmissions. It is recommended that each piece of baseband equipment include only one
BBP. Each BBP can belong to only one piece of baseband equipment.
Baseband equipment is bound to cells by running the ADD EUCELLSECTOREQM
command.

3.3.1.7 Cell-specific Sector Equipment


When binding sector equipment to a cell, you can specify the baseband equipment for the cell
at the same time.
The sector equipment and baseband equipment specific to a cell are added by running the
ADD EUCELLSECTOREQM command. If baseband equipment is not configured for a
cell, the BBP directly connected to the RRU serving the cell is used by default.
The PRB can be bound to sector equipment by running the ADD
PRBTOEUCELLSECTOREQM command.

3.4 Idle Mode Management

3.4.1 Overview
The main activities of UEs in RRC_IDLE mode are public land mobile network (PLMN)
selection, cell selection and reselection, and tracking area (TA) registration. Figure 3-14
shows the relationships among them.

Figure 3-14 Relationships among PLMN selection, cell selection and reselection, and TA
registration

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 36


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

The following describes the main activities of UEs in RRC_IDLE mode:


l PLMN selection
UEs select a PLMN and register on the PLMN.
l Cell selection
UEs select cells in the chosen PLMN and camp on those cells so that UEs can monitor
system information and paging messages to obtain services.
l Cell reselection
When camping on a given cell, UEs regularly search for a better cell based on the cell
reselection criteria, to correctly receive system information and successfully initiate
services.
l TA registration
UEs register their locations with the EPC through a TA registration procedure so that the
EPC can page them within a TA and request that they initiate services.
l Cell reservation and access control
Cell reservation and access control are two mechanisms operators use to control their
networks. In cell reservation, specific cells can be reserved for only UEs of special
classes (for example, for the network management purpose of operators). In access
control, the UEs that can initiate calls in a cell are identified by UE class.
l System information broadcast and paging
In system information broadcast, data such as parameters related to cell selection and
reselection is broadcast over the BCCH to UEs. In paging, paging messages are used to
inform all UEs in a cell of any changes in the system information and to carry paging-
related information.
To ensure a satisfactory access success rate and to shorten access time, UEs in
RRC_IDLE mode select cells based on the signal quality and according to the
parameters in the system information. When camping on the cell, UEs regularly reselect
better cells for camping based on cell reselection criteria. Cell reselection increases the
probability that a UE will properly receive system information and successfully initiate
services.

3.4.2 PLMN Selection


Figure 3-15 shows the PLMN selection procedure. When a UE is powered on, or re-enters a
network coverage area, the UE first selects the last registered PLMN (RPLMN) or a PLMN in
the equivalent PLMN (EPLMN) list and attempts to register on that PLMN. If the registration
on that PLMN is successful, the UE displays the selected PLMN on the screen, and can then
obtain services from an operator. If the most recent RPLMN is unavailable or if the
registration on that PLMN fails, another PLMN can be automatically or manually selected
according to the priorities of PLMNs stored in the Universal Subscriber Identity Module
(USIM). For details about PLMN selection, see section 4.4 in 3GPP TS 23.122.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 37


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Figure 3-15 PLMN selection procedure

3.4.3 Automatic PLMN Selection


If a UE fails to register on its most recent RPLMN or EPLMN, the UE attempts to select
another PLMN. In automatic network selection mode, the UE selects a PLMN in the
following order of preference:
1. The equivalent home PLMN (EHPLMN) with the highest priority if the EHPLMN list is
available and contains at least one EHPLMN, or the home PLMN (HPLMN) if the
EHPLMN list is empty or unavailable.
2. Each combination of PLMN with RAT in the "User Controlled PLMN Selector with
Access Technology" data file in the USIM, in order of priority.
3. Each combination of PLMN with RAT in the "Operator Controlled PLMN Selector with
Access Technology" data file in the USIM, in order of priority.
4. Other combinations of PLMNs with RATs providing high-quality signals, in a random
order. A high-quality signal is defined as the reference signal received power (RSRP)
value of a cell in the combination of PLMN with RAT being greater than or equal to -110
dBm.
5. Other combinations of PLMNs with RATs in descending order of signal quality.

If the UE finds a suitable cell in a PLMN during this PLMN selection procedure, the UE
attempts to register on that PLMN. If the registration is successful, the UE camps on the
suitable cell; otherwise, the UE tries the next PLMN.

If the registration on none of the PLMNs is successful or if no PLMN is available, the UE


cannot obtain any services.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 38


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

NOTE

Normal service and operator service are two types of services provided to UEs in RRC_IDLE mode in
the suitable cell and reserved cell, respectively. For details about the suitable cell and reserved cell, see
section 4.3 in 3GPP TS 36.304.
NB-IoT does not support limited service.

3.4.4 Manual PLMN Selection


When a UE fails to register on its last RPLMN or EPLMN, the UE attempts to select another
PLMN. In manual network selection mode, the UE displays a list of detected PLMNs in the
same order as the PLMNs to be selected in automatic network selection mode.
In manual PLMN selection mode, a UE can also register with forbidden PLMNs. If the UE
succeeds in registering on the selected PLMN, the PLMN is no more a forbidden PLMN to
the UE. The forbidden PLMNs are determined by the EPC.

3.4.5 Roaming
When roaming, the UE obtains services from the visited PLMN (VPLMN), a PLMN other
than its HPLMN. For example, the UE may obtain services from a PLMN in another country
(an international roaming area). When a UE with the roaming service moves out of the
coverage area of its HPLMN, the UE can obtain services from another PLMN according to
the PLMN data stored in its USIM. The operator determines whether roaming is allowed for
the UE.
After the UE registers with a VPLMN, it periodically searches for its HPLMN and attempts to
return to there. The time interval between consecutive searches for the HPLMN is defined by
the operator and stored in the USIM. The time interval between consecutive searches by NB-
IoT UEs for the HPLMN ranges from 2 to 240 hours. If the time interval is not stored in the
USIM, the default value of 72 hours is used.

3.4.6 Cell Selection and Reselection


After selecting a PLMN, the UE selects a cell in the PLMN to camp on. After camping on a
cell, the UE monitors system information, performs measurements on the serving cell and
neighboring cells, and selects a better cell to camp on based on measurement rules and cell
reselection criteria.
Before the UE selects a cell to camp on, it performs a cell search procedure. After the UE
finds a cell, it performs cell selection or reselection based on the selection or reselection
related parameters in the system information or in the RRC Connection Release message.
Figure 3-16 shows the cell selection and cell reselection procedures. Either stored
information cell selection (preferred) or initial cell selection can be used to search for a
suitable cell. For details, see section 5.2.2 in 3GPP TS 36.304.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 39


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Figure 3-16 Cell selection and reselection procedures

3.4.6.1 Cell Search


Cell search is a procedure that the UE uses to achieve time and frequency synchronization
with a cell, obtains the PCI, and learns the signal quality and other information about the cell
based on that PCI. Before selecting or reselecting to a cell, a UE performs a cell search on all
carrier frequencies.

In the NB-IoT system, synchronization signals are specially used for cell search. There are
two types of synchronization signals: the narrowband primary synchronization signal (NPSS)
and the narrowband secondary synchronization signal (NSSS). More information about these
two types of signals can be found in 3GPP TS 36.211 (Release 13). The cell search procedure
is as follows:
1. The UE monitors the NPSS and NSSS to achieve frame synchronization, that is, time
synchronization with the cell, and to obtain the PCI.
2. The UE monitors the downlink reference signal to determine the signal quality of the
cell.
3. The UE monitors the NPBCH to acquire other information about the cell.

3.4.6.2 Cell Selection

Triggering
When a UE switches from RRC_CONNECTED mode to RRC_IDLE mode or after it selects
a PLMN, the UE must select a cell to camp on.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 40


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

When the UE switches from RRC_CONNECTED mode to RRC_IDLE mode, it first attempts
to select the last cell that it camped on in RRC_CONNECTED mode or it selects a suitable
cell on the frequency that is allocated through the RRC Connection Release message. If such
a cell is not available, the UE attempts to find a suitable cell by performing a Stored
Information Cell Selection procedure. If the UE fails to find a suitable cell, the UE performs
an Initial Cell Selection procedure.

NOTE

In the current version, the RRC Connection Release message does not contain the frequency allocated to
the UE.
l Stored information cell selection
The Stored Information Cell Selection procedure requires stored information related to
carrier frequencies and cell parameters. The information is obtained from previously
detected SI messages of cells. This information can help speed up cell selection.
l Initial cell selection
In this procedure, the UE scans all carrier frequencies in the evolved universal terrestrial
radio access network (E-UTRAN) according to its capabilities to find a suitable cell. On
each carrier frequency, the UE searches only for the cell with strongest signal. If the UE
finds a suitable cell, it selects that cell to camp on.

Cell Selection Criteria


During cell selection, a UE selects a cell to camp on when both Srxlev and Squal are greater
than zero.
Srxlev = Qrxlevmeas Qrxlevmin Pcompensation Qoffsettemp

Squal = Qqualmeas Qqualmin Qoffsettemp

l Qrxlevmeas is the measured RX signal level (RSRP) of the cell.


l Qrxlevmin is the lowest cell RX signal level. It is broadcast in SIB1 and specified by the
CellSel.QRxLevMin parameter.
l Pcompensation is the result of the function: max (PMax UE Maximum Output Power,
0).
PMax is the maximum allowed uplink transmit power of the UE in a cell. It is
broadcast in SIB1 and specified by the CellResel.PMaxCfgInd parameter.
UE Maximum Output Power is the maximum output power that the UE can
physically achieve. It is unconfigurable on the network side.
l Qqualmeas is the measured RX signal quality (RSRQ) of the cell.
l QqualMin is the lowest cell RX signal quality required for the cell to become a suitable
cell. It is broadcast in SIB1 and specified by the CellSel.QQualMin parameter.
l Qoffsettemp is the value of connEstFailOffset broadcast in SIB2. SIB2 contains this
variable only when an RRC connection setup fails.
NOTE

In the current version, Qoffsettemp cannot be sent over the Uu interface.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 41


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

3.4.6.3 Neighboring Cell Measurement for Cell Reselection


During cell reselection, a UE performs measurement of neighboring cells based on the signal
quality of the serving cell. The UE measures only the neighboring cells broadcast in the
system information.
l Intra-frequency measurement
The intra-frequency measurement threshold s-IntraSearchP is broadcast in SIB3 and
specified by the CellResel.SIntraSearch parameter. The UE uses the value of s-
IntraSearchP as the value of SIntraSearchP, and determines whether to perform
measurement in intra-frequency neighboring cells based on the values of Srxlev and
SIntraSearchP.
If the value of Srxlev is greater than that of SIntraSearchP, the UE does not perform
measurement in intra-frequency neighboring cells.
If the value of Srxlev is less than or equal to that of SIntraSearchP, the UE performs
measurement in intra-frequency neighboring cells.
l Inter-frequency measurement
The inter-frequency measurement threshold s-NonIntraSearch is broadcast in SIB3 and
specified by the CellResel.SNonIntraSearch parameter. The UE uses the value of s-
NonIntraSearch as the value of SnonIntraSearchP, and determines whether to perform inter-
frequency measurement based on the values of Srxlev and SnonIntraSearchP.
If the value of Srxlev is greater than that of SnonIntraSearchP, the UE does not perform
inter-frequency measurement.
If the value of Srxlev is less than or equal to that of SnonIntraSearchP, the UE performs
measurement in inter-frequency neighboring cells.
The intra-frequency neighboring cells, target EARFCNs, and inter-frequency neighboring
cells indicated in SIB4/SIB5 can be configured in the EutranIntraFreqNCell,
EutranInterNFreq, and EutranInterFreqNCell MOs, respectively.
l If no neighboring cells are configured, the cell reselection thresholds specified in the
CellResel MO are used for cell reselection.
l If the numbers configured exceed the numbers allowed on the Uu interface, the eNodeB
includes only the top data configurations in SIB4/SIB5.
After the eNodeB is reset, the sequence of data configurations may change. If it changes,
the data configurations contained in SIB4/SIB5 also change. Therefore, it is
recommended that data configurations do not exceed the Uu interface capability.
Specifically, the numbers of configured intra-frequency neighboring cells, target
EARFCNs, and inter-frequency neighboring cells on each target EARFCN do not exceed
16, 8, and 16, respectively.

3.4.6.4 Cell Reselection


After camping on a cell, the UE monitors the system information, performs measurements on
the serving and neighboring cells, and selects the best cell to camp on based on measurement
rules and cell reselection criteria.
A UE uses the cell reselection criteria to reselect an intra-frequency or inter-frequency cell.
The UE evaluates only the neighboring cells that meet the cell selection criteria.
The following parameters broadcast in SIB3 are used for calculating the Srxlev value of intra-
frequency neighboring cells:

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 42


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

l Qrxlevmin is the lowest cell RX signal level. It is broadcast in SIB3 and specified by the
CellResel.QRxLevMin parameter.
l PMax is the maximum transmit power that the UE can apply to uplink transmission in
the neighboring cell. It is broadcast in SIB3 and specified by the CellResel.PMax
parameter.
The following parameters broadcast in SIB5 are used for calculating the Srxlev values of
inter-frequency neighboring cells:
l Qrxlevmin is the lowest cell RX signal level. It is broadcast in SIB5 and specified by the
EutranInterNFreq.QRxLevMin parameter.
l PMax is the maximum transmit power that the UE can apply to uplink transmission in
neighboring cells. It is broadcast in SIB5 and specified by the EutranInterNFreq.PMax
parameter.
The cell-ranking criteria R_s for the serving cell and R_n for neighboring cells are defined as
follows:
R_s = Qmeas,s + Qhyst Qoffsettemp

R_n = Qmeas,n Qoffset Qoffsettemp

l Qmeas,s is the measured RSRP value of the serving cell.


l Qhyst is the reselection hysteresis for the serving cell. It is broadcast in SIB3 and
specified by the CellResel.Qhyst parameter.
l Qmeas,n is the measured RSRP value of the neighboring cell.
l Qoffset is equal to q-OffsetCell broadcast in SIB4 for intra-frequency neighboring cells
or q-OffsetFreq broadcast in SIB5 for inter-frequency neighboring cells. If q-OffsetCell
is not broadcast in SIB4 or q-OffsetFreq is not broadcast in SIB5, the UE sets q-
OffsetCell or q-OffsetFreq to 0. q-OffsetCell in SIB4 is specified by the
EutranIntraFreqNCell.CellQoffset parameter. q-OffsetFreq in SIB5 is specified by the
EutranInterNFreq.QoffsetFreq parameter.
l Qoffsettemp is not supported in the current version. This field is not delivered over the Uu
interface. The UE sets this field to 0.
The UE reselects a neighboring cell based on the cell reselection criteria only when the signal
quality of the neighboring cell is better than that of the serving cell. If the signal quality of
multiple neighboring cells is better than that of the serving cell, the UE reselects a
neighboring cell with the greatest R_n value. Specifically, the UE reselects to a neighboring
cell when both the following conditions are met:
l The new cell ranks higher than the serving cell during the cell reselection period. The
cell reselection period for an intra-frequency neighboring cell is broadcast in SIB3 and
specified by the CellResel.TReselForNb parameter. The cell reselection time for an
inter-frequency neighboring cell is broadcast in SIB5 and specified by the
CellResel.TReselInterFreqForNb parameter.
l The UE has camped on the serving cell for more than 1s.
During cell reselection, the UE needs to check whether access to a neighboring cell is allowed
according to the "cellAccessRelatedInfo" IE in SIB1 received from the neighboring cell. If the
neighboring cell is barred, it must be excluded from the candidate list. If the neighboring cell
is unsuitable, the UE does not consider this cell and other cells on the same frequency as
candidates for reselection for a maximum of 300 seconds. The neighboring cell is considered
unsuitable if it is part of the forbidden TAs for roaming or it does not belong to the RPLMN
or an EPLMN.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 43


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

3.4.6.5 TA Registration
A UE informs the EPC of its TA by TA registration. The TA is a concept introduced to the
LTE/System Architecture Evolution (SAE) system for location management of UEs. A TA is
identified by a tracking area identity (TAI), which consists of the mobile country code
(MCC), mobile network code (MNC), and tracking area code (TAC). According to 3GPP
specifications, the TAIs of NB-IoT networks need to be independently configured and cannot
be the same as those of the E-UTRAN. In addition, interoperations between NB-IoT and E-
UTRAN are not allowed.
TA registration can be performed in two ways: TA update and Attach/Detach.

3.4.6.6 TA Update
UEs perform TA updates by sending TA update requests when any of the following conditions
are met (For details, see section 5.3.3.0 in 3GPP TS 23.401):
l The UE detects that it has entered a new TA when it finds that the TAI in the system
information is different from any TAI stored in its USIM.
l The periodic TA update timer expires. This timer length is delivered to the UE through a
non-access stratum (NAS) message.
l The RRC connection is released for load balancing.
l The UE receives an NAS level RRC connection setup failure message from the RRC
layer of the UE.
l The preferred network behavior information about or eDRX parameters for the UE
change and become inconsistent with the information stored on the MME.
The UE informs the EPC of its TA by TA update. The EPC will send paging messages to all
eNodeBs in the TA.

3.4.6.7 Attach/Detach
When a UE needs to obtain services from a network but is not registered to that network, the
UE performs an Attach procedure for TA registration. For the detailed Attach procedure, see
section 5.3.2.1 in 3GPP TS 23.401 (Release 13).
After a successful Attach procedure, the UE is allocated an IP address. The mobile equipment
identity (MEI) of the UE will be sent to the MME for authentication.
If the UE fails to connect to the EPC or the EPC does not allow UE access, a Detach
procedure is initiated. After the Detach procedure is finished, the EPC no longer pages the
UE.

3.4.7 Cell Reservation and Access Control


Cell reservation and access control are two mechanisms operators use to control their
networks.
l Cell reservation employs cell status indication and special reservations to control cell
selection and reselection procedures. Cells can be reserved for only UEs in RRC_IDLE
mode.
l Access control is implemented for UEs on the basis of access classes. To implement
access control, one or more access classes are allocated to a UE and stored in the USIM.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 44


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

3.4.7.1 Cell Reservation and Barring


UEs are notified of cell status by the following information in SIB1:
l cellBarred
It specifies whether a cell is a barred cell. The cell barred status is specified by the
CellAccess.CellBarred parameter. If a cell belongs to multiple PLMNs, the cell barred
status is shared by all the PLMNs.
l cellReservedForOperatorUse
It specifies whether a cell is a reserved cell. The cell reserved status is specified by the
CellOp.CellReservedForOp parameter. Each PLMN has its own cell reserved status.
If a cell is neither barred nor reserved for operator use, UEs can consider this cell a candidate
during cell selection and reselection procedures.
If a cell is not barred but is reserved for operator use during cell selection and reselection
procedures, UEs treat this cell as follows:
l If UEs of access classes 11 to 15 camp on their HPLMN or an EHPLMN, the UEs can
treat this cell as a candidate.
l Otherwise, UEs treat this cell as a barred cell.
If a cell is barred, UEs behave as follows during cell selection and reselection procedures:
l UEs cannot select or reselect this cell.
l UEs reselect another unbarred cell as follows:
When "intraFreqReselection" (specified by the CellAccess.IntraFreqResel
parameter) in SIB1 indicates that intra-frequency reselection is allowed, UEs may
select another cell on the same frequency if reselection criteria are fulfilled. When
CellAccess.IntraFreqResel in SIB1 indicates that intra-frequency reselection is not
allowed, the UEs do not reselect another cell on the same frequency as the barred
cell.
UEs exclude the barred cell from candidates for cell selection or reselection for 300
seconds.

3.4.7.2 Access Control


Access classes are applicable to UE access over the air interface. There are 16 access classes,
numbered from 0 to 15. The information about access classes 0 to 9 and 11 to 15 is stored in
USIMs. The information about access class 10 is signaled to UEs through system information
broadcast to indicate whether cells allow emergency calls. NB-IoT does not support access
class 10. For details about the list of barred access classes and how UEs determine their
access classes, see chapter 4 "Access control" in 3GPP TS 22.011 V10.0.0 and section 3.4
"Access control" in 3GPP TS 23.122 V10.0.0.
Access class control is a method for controlling UEs' network access, as defined in 3GPP TS
36.331. For details, see 3.8 Admission Control, Congestion Control, and Overload
Control.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 45


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

3.4.8 Paging
Triggering of Paging
Paging is a procedure that can be initiated either by an MME to transmit paging messages to a
UE in RRC_IDLE mode, or by an eNodeB to inform all UEs in RRC_IDLE mode of an SI
message change.
l Transmitting paging messages to a UE in RRC_IDLE mode
The paging messages contain a tracking area list (TAL) for the concerned cell or UE. In
the cell or in all the cells within the TAs on the list, the eNodeBs transmit paging
messages over the paging control channel (PCCH) to page the UE. The paging messages
also contain the UE identity, which can be the SAE-temporary mobile subscriber identity
(S-TMSI) or international mobile subscriber identity (IMSI) of the UE.
l Informing all UEs in RRC_IDLE mode of an SI message change
The eNodeB transmits paging messages or NPDCCH messages (DCI format N2) to
notify all UEs in RRC_IDLE mode in the cell when the SI message changes. In the next
SI message modification period, it transmits the updated SI message. To ensure that all
of these UEs receive the system information, the eNodeB transmits the paging messages
or NPDCCH messages on all possible occasions in discontinuous reception (DRX)
cycles.
Though paging can be triggered by different NEs, the paging mechanism on the Uu interface
is the same.

Paging Mechanism on the Uu Interface


UEs in RRC_IDLE mode receive paging messages using DRX to save power. The positions
of the NPDCCH control information in paging messages transmitted over the Uu interface are
fixed. These positions are indicated by the paging frames (PFs) and paging occasion (PO)
subframes. One PF is equal to one radio frame, which in turn may contain one or more POs,
as shown in Figure 3-17. A PO is a downlink subframe that contains the NPDCCH control
information and paging radio network temporary identifier (P-RNTI). In accordance with
3GPP specifications, the P-RNTI value is fixed. UEs read NPDCCH control information
according to the P-RNTI. If a new paging message is sent to the UE, the UE reads the paging
message from the NPDSCH as indicated by the DCI.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 46


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Figure 3-17 Paging mechanism

NOTE

When the repetition count of NPDCCH information in a paging message is set to 1 and the signal quality
is good, a paging message occupies only one valid subframe. Under other circumstances, a paging
message can occupy multiple valid subframes.

The PF number and PO subframe number can be calculated based on the IMSI of the UE,
DRX cycle, and number of PO subframes in a DRX cycle. Frame numbers are stored in the SI
that contains the DRX parameters of the UE. When the DRX parameters change, PF number
and PO subframe number change accordingly.

The SFN of a PF is derived from the following formula: SFN mod T = (T div N) x (UE_ID
mod N)

Table 3-4 lists the subframe number i_s of a PO, which is derived from the following
formula: i_s = floor (UE_ID/N) mod Ns, where floor (UE_ID/N) represents rounding
(UE_ID/N) down to the nearest integer.

Table 3-4 Subframe number i_s of a PO

Ns PO when i_s PO when i_s PO when i_s PO when i_s


=0 =1 =2 =3

1 9 N/A N/A N/A

2 4 9 N/A N/A

4 0 4 5 9

The variables in these formulas are as follows:

l T is a DRX cycle, which is contained in "defaultPagingCycle" of SIB2 and specified by


the PCCHCfg.DefaultPagingCycleForNb parameter.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 47


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

NOTE

l In accordance with 3GPP TS 36.304, the NB-IoT UE does not support a specific paging cycle.
l In the S1 setup process, the eNodeB sends the MME the information about the eNodeB-
specific default NB-IoT paging DRX cycle. Based on the default paging DRX cycle, the MME
determines whether paging response times out. The default paging DRX cycle is specified by
the GlobalProcSwitch.S1DefaultPagingDrxForNb parameter. It is recommended that the
length of the default paging DRX cycle be greater than or equal to the "defaultPagingCycle"
IE value for all NB-IoT cells.
l N equals min(T, nB). The PCCHCfg.NbForNbIoT parameter specifies nB.
l Ns is max(1, nB/T).
l UE_ID equals IMSI mod 4096.
If the paging is triggered by the MME, the UE_ID value is the UE Identity Index
Value contained in the paging message sent over the S1 interface.
If the paging is triggered by the eNodeB, the UE_ID is unavailable, and the UE uses
the default UE_ID value of 0.
In addition to DRX, the paging procedure can also work with eDRX. For details, see 3.10 Idle
Mode eDRX.

Paging Handling Procedure


During a system information update, the eNodeB generates an NPDCCH message (DCI
format N2, flag set to 0) that contains a system information change at each subsequent PO. To
page a specific UE, the eNodeB calculates the approaching PO for the UE, generates a paging
message, and sets the Paging Record IE. If the eNodeB sends the paging record IE another
UE or a PDCCH message containing a system information change in this PO, the eNodeB
includes all the information in the paging message. In this case, the paging message contains
the paging record or the system information changes for multiple UEs. Therefore, the eNodeB
does not send NPDCCH messages with system information changes any more.
UEs in RRC_IDLE mode use DRX to reduce power consumption. In each DRX cycle, a UE
reads the NPDCCH information only in its own POs. Multiple UEs may have the same PO.
A UE in RRC_IDLE mode starts its receiver to monitor the NPDCCH at POs in each DRX
cycle. After the UE detects its own paging message, the UE sends a paging response, which is
generated at the NAS, to the MME. The paging response from the UE to the MME is
indicated by mt-Access, the value of the Establishment Cause IE in the RRC Connection
Request message.
If the UE does not obtain the P-RNTI on the NPDCCH, or if the UE obtains the P-RNTI but
does not detect its paging record, the UE stops the receiver and enters the DRX sleep state to
reduce power consumption.

Scheduling of Paging Messages


The Paging Record List in a paging message over the Uu interface can contain the
information for multiple UEs, and therefore multiple UEs can be paged with a single paging
message.
The eNodeB sends paging messages to UEs according to the strategy specified by the
PCCHCfg.PagingStrategy parameter.
l First in first out (FIFO)
If PCCHCfg.PagingStrategy is set to PAGING_STRATEGY_FIFO(First-in First-out
Strategy), the eNodeB preferentially sends the paging messages for UEs that arrive

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 48


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

earlier in a paging occasion and sends the paging messages for other UEs in the next
paging cycle.
l Priority differentiation
If PCCHCfg.PagingStrategy is set to PAGING_STRATEGY_DIFFPRI(Priority
Differentiation Strategy), the eNodeB preferentially selects paging messages that have
paging priorities and then selects PS paging messages that do not have paging priorities.
The eNodeB then sends the paging messages that have paging priorities in a paging
occasion and sends the remaining paging messages in the next paging cycle.
The paging message priorities are carried in the paging message sent by the MME to the
eNodeB. PS paging messages are indicated by value PS of the CN Domain field in
paging messages sent by the MME to the eNodeB.

Extended Paging
Most NB-IoT UEs are not very mobile. Therefore, an NB-IoT UE is preferentially paged in
the last cell it camped on and then paged in an extended area only if the previous paging fails,
which saves Uu interface resources and reduce UE power consumption. Figure 3-18 shows
an extended paging procedure.

Figure 3-18 Extended paging procedure

1. When a UE's connection is released, the eNodeB includes the following information in a
UE Context Release Complete message sent to the MME:
UE's current cell and coverage level
Recommended cell list and eNodeB list. The recommended cell list includes the
intra-frequency neighboring cells of the current cell, and the eNodeB list includes
the eNodeBs serving the cells in the recommended cell list.
2. The MME stores the information received in the UE Context Release Complete message.
When paging the UE, the MME includes the coverage level and recommended cell list in
the paging message to the eNodeB.
NOTE

The MME determines the paging scope based on the recommended eNodeB list.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 49


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

3. When the eNodeB receives the paging message from the MME, it determines the
extended paging policy based on the number of the current paging times and the total
number of planned paging times:
The eNodeB preferentially pages the UE in the last cell it camped on, and if the paging
fails, proceeds to page the UE in the recommended cells, and pages the UE in the entire
TA if the previous two paging attempts fail.

3.4.9 System Information Broadcast


The SI is divided into various information blocks based on the contents of the SI message.
There is one master information block (MIB) and seven system information blocks (SIBs),
including SIB1 to SIB5, SIB14, and SIB16. Figure 3-19 shows the relationships between the
MIB and SIBs.

Figure 3-19 Relationships between SI messages

l The MIB is transmitted over the BCCH through an independent RRC message. The
BCCH has a predefined transport format. The UE receives the MIB on the BCCH
without obtaining other information from the network.
l The SIB1 is transmitted over the DL-SCH through an independent RRC message.
l Other SIBs are transmitted over the downlink shared channel (DL-SCH) through SI
messages, and the scheduling periods can be set separately. SIBs with the same
scheduling period can be transmitted through the same SI message, whereas the SIBs
with different scheduling periods must be transmitted through different SI messages.
SIB1 carries the scheduling periods of all SI messages and mapping information from
SIBs to SI messages.

The different types of content contained in the MIB, and in each SIB, are described in the
following table.

SI Block Content

MIB Deployment mode, scheduling period of SIB1, access barring switch,


H-SFN, SFN, and SystemInfoValueTag

SIB1 Parameters related to cell access and cell selection, and scheduling
information of SI messages

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 50


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

SI Block Content

SIB2 Common radio parameters used by all the UEs in a cell

SIB3 Common cell reselection parameters for all cells and intra-frequency
cell reselection parameters

SIB4 Intra-frequency neighboring cell list, reselection parameters of each


neighboring cell used for cell reselection, and intra-frequency cell
reselection blacklist

SIB5 l Inter-frequency EARFCN list and reselection parameters of each


EARFCN used for cell reselection
l Inter-frequency neighboring cell list and reselection parameters of
each neighboring cell used for cell reselection
l Inter-frequency cell reselection blacklist

SIB14 Access control information, which is used to bar the access of UEs
belonging to certain classes

SIB16 Global Positioning System (GPS) time and Coordinated Universal


Time (UTC)

NOTE

NB-IoT does not support intra-frequency and inter-frequency cell reselection blacklists in the current
version.

System Information Scheduling


SI messages are scheduled as follows:
l The scheduling period for the MIB is fixed at 640 ms. The MIB is transmitted eight
times in a scheduling period. Each MIB occupies eight subframes and is scheduled in
every subframe 0 of eight consecutive radio frames.
l The scheduling period for the SIB1 is 2560 ms. The number of times that SIB1 can be
repeatedly scheduled in a scheduling period is specified by the
CellSiMap.NbSib1RepetitionNum parameter, which can be set to 4, 8, or 16. The
specific value is contained in the MIB. Each SIB1 occupies eight subframes and is
scheduled in every alternate subframe 4 of 16 consecutive radio frames.
l The scheduling periods for SIB2 to SIB5, SIB14, and SIB16 are specified by the
CellSiMap.NbSib2Period, CellSiMap.NbSib3Period, CellSiMap.NbSib4Period,
CellSiMap.NbSib5Period, CellSiMap.NbSib14Period, and CellSiMap.NbSib16Period
parameters. All these parameter values are carried in SIB1. SIB2 to SIB5, SIB14, and
SIB16 are mapped onto SI messages. An SI message can be transmitted only within a
specific duration in the scheduling period, and the specific duration is SI window. Only
one type of SI message can be transmitted in an SI window.

System Information Update


A UE reads SI messages in the following scenarios:

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 51


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

l The UE is powered on and is selecting a cell to camp on.


l The UE is reselecting to a cell.
l The UE has returned from an area where there was no coverage.
SI messages are updated at an interval specified by the BcchCfg.ModifyPeriodCoeffForNb
parameter, which is an integer multiple of the paging cycle.
After obtaining the correct SI message, the UE does not read the message repeatedly. It
rereads and updates the SI message only in the following scenarios:
l The UE receives an SI message change notification in the paging message transmitted
from the eNodeB.
l 24 hours have elapsed since the last time the UE received a correct SI message.
When it receives an SI message change notification in the paging message, the UE does not
immediately update the SI message. Instead, it receives the updated SI message from the
eNodeB in the next message modification period. The message modification period of the SI
message starts from radio frame for which SFN mod n = 0. During the n modification period,
the eNodeB transmits the paging message to inform UEs in RRC_IDLE mode about the SI
message change when a paging cycle arrives. When the n+1 modification period arrives, the
eNodeB transmits the updated SI message. In Figure 3-20, different colors indicate different
SI messages.

Figure 3-20 SI message update procedure

When SI messages (excluding the SIB14 and SIB16) are updated, the eNodeB changes the
value of "systemInfoValueTag" in the MIB and the value of "systemInfoValueTagSI" in the
SIB1. The UE reads the values and compares them with the values that it read last time. If the
values change, it is an indication that SI messages change. If the values do not change, it is an
indication that SI messages do not change.
The UE reads the SI message again 24 hours after receiving an SI message. In this case, the
UE reads all SI messages regardless of whether the values of "systemInfoValueTag" and
"systemInfoValueTagSI" change.

3.5 Connection Management

3.5.1 Random Access

3.5.1.1 Overview
Random access must be performed before a UE can establish communication with the
network. During random access, the UE sends an access request to the eNodeB and then the

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 52


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

eNodeB responds to the request and allocates a RACH. Through random access, the UE
obtains uplink synchronization signals from the network and requests dedicated resources for
data transmission.

NB-IoT UEs initiate a random access procedure when one of the following conditions is met:
l The UE initiates a random access procedure while in RRC_IDLE mode or after being
paged.
l The eNodeB needs to send downlink data to a UE in RRC_CONNECTED mode and
finds that the UE is out-of-synchronization in the uplink.
l The UE is in RRC_CONNECTED mode when data for the UE arrives, but the UE has
not received a UL Grant message from the eNodeB. Under this condition:
If the NbCellUlSchCEAlgo.NbLogicChSrProhibitTimer parameter is set to
NOT_CFG, the UE immediately initiates a random access procedure but the
probability of successful pre-scheduling for the UE decreases.
If the NbCellUlSchCEAlgo.NbLogicChSrProhibitTimer parameter is set to a
value other than NOT_CFG (PP2 is recommended), the UE starts this timer and
initiates a random access procedure until the timer expires. The timer configuration
increases the probability of successful pre-scheduling for the UE. However, if this
timer is set to a too large value, the UE's access delay increases.

3.5.1.2 Random Access Procedure


In the current version, NB-IoT supports only contention-based random access, which is
illustrated in Figure 3-21.

Figure 3-21 Contention-based random access procedure

1. The UE reads RACH configuration information from SIB2, selects a coverage level
based on the RSRP threshold contained in SIB2 and the measured RSRP, and sends a
random access request to the eNodeB in the selected coverage level. The RSRP threshold
is specified by the RACHCfg.NbRsrpFirstThreshold and
RACHCfg.NbRsrpSecondThreshold parameters.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 53


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

The UE sends the random access request to the eNodeB with the transmit power
specified by PPRACH. Detailed information about PPRACH can be found in 3.7.2 Uplink
Power Control.
2. Upon receiving the preamble, the eNodeB applies for a temporary cell RNTI (C-RNTI)
and applies for uplink and downlink resources for scheduling. Then, the eNodeB sends a
random access response over the DL-SCH to each UE. The response contains the RA-
preamble identifier, timing alignment information, initial UL grant, and temporary C-
RNTI. One DL-SCH can carry random access responses to multiple UEs.
After sending the preamble, the UE monitors the NPDCCH and waits for a random
access response within a random access response window:
If the UE receives a response containing an RA-preamble identifier which is the
same as the identifier contained in the transmitted random access preamble, the
response was successful, and the RA-preamble identifier is used for uplink
transmission.
If the UE does not receive a response within the random access window or fails to
verify the response, the response fails. In this case, if the number of random access
attempts is smaller than the upper limit, the UE retries random access. Otherwise,
random access fails. The maximum allowable number of random access attempts is
contained in SIB2 and specified by the RACHCfg.preambleTransMax parameter.
The maximum allowable number of random access attempts in a specific coverage
level is specified by the CellRachCECfg.MaxNumPreambleAttempt parameter.
3. The UE sends Msg3 using the resources contained in the random access response. The
UE transmits uplink scheduled data over the uplink shared channel (UL-SCH). The size
of the transport block, which is fixed at 88 bits, is specified in the random access
response. The information in the transport block sent by the UE varies in different
random access scenarios:
Initial RRC connection setup
The RRC Connection Request message is sent by the UE over the CCCH and
contains the cause of RRC connection setup, for example, mt-Access, mo-
Signalling, mo-Data, mo-Exception-Data, or delayTolerantAccess-v1330. This
message also contains the MAC CE consisting of DVI and PHR for requesting
uplink transmission resources and contains the NAS UE_ID.
Other scenarios
At least the C-RNTI of the UE is transmitted.
4. After the UE sends Msg3, a contention resolution timer starts. The contention resolution
timer is specified by the CellRachCECfg.ContentionResolutionTimer parameter and its
length can be obtained from SIB2. Within the timer length, the eNodeB performs
contention resolution at the MAC layer and informs the UE of the resolution through the
C-RNTI on the NPDCCH or through the UE Contention Resolution Identity IE on the
DL-SCH.
The UE monitors the NPDCCH before the timer expires. The UE considers the
contention resolution as successful, notifies upper layers, and stops the timer if both of
the following conditions are met:
The UE obtains the C-RNTI from the NPDCCH.
The UE obtains the temporary C-RNTI over the NPDCCH, the MAC packet data
unit (PDU) is successfully decoded, and the MAC PDU contains information
matching the CCCH service data unit (SDU) transmitted in Msg3.
Once the contention resolution completes, the entire contention-based random access
procedure is complete. If the contention resolution timer expires, the UE considers the

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 54


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

contention resolution to have failed. The UE then performs the entire procedure again, as
long as the number of random access attempts has not reached the maximum allowed. If
the number of random access attempts has reached this maximum, the random access
procedure fails.

3.5.1.3 NPRACH Resource Configuration


NPRACH resource configuration involves the configuration of the PRACH subcarrier offset,
PRACH occupation duration, PRACH start time, and PRACH transmission period for each
coverage level.
NPRACH resources support up to three coverage levels. In the current version, NPRACH
resources are allocated to different coverage levels based on time division. In addition, the
PRACH subcarrier offsets must be set to the same value for all coverage levels. The PRACH
subcarrier offset is specified by the CellRachCECfg.PrachSubcarrierOffset parameter.
The PRACH occupation duration for each coverage level is calculated as follows:
l When the RACHCfg.NbCyclicPrefixLength parameter is set to 66DOT7(66DOT7), the
PRACH occupation duration equals the product of 5.6 ms and the value of the
CellRachCECfg.PrachRepetitionCount parameter.
l When the RACHCfg.NbCyclicPrefixLength parameter is set to 266DOT7(266DOT7),
the PRACH occupation duration equals the product of 6.4 ms and the value of the
CellRachCECfg.PrachRepetitionCount parameter.
The configurations of PRACH start time and PRACH transmission period vary with the
setting of the RACHCfg.PrachStartTimeCfgInd parameter.

Configurations of PRACH Start Time and PRACH Transmission Period When


RACHCfg.PrachStartTimeCfgInd Is Set to NOT_CFG(Not configure)
When the RACHCfg.PrachStartTimeCfgInd parameter is set to NOT_CFG(Not configure):
l The eNodeB automatically sets the PRACH start time for each coverage level to values
that meet the following conditions:
The PRACH start time for coverage level 0 must be fixed at 8 ms.
The PRACH start time for the next coverage level must be at least equal to the sum
of PRACH occupation duration and PRACH start time for the previous adjacent
coverage level.
There must be at least a 40 ms difference between the PRACH start time for two
adjacent coverage levels.
According to 3GPP TS 36.321, the random access RNTI (RA-RNTI) equals 1 plus
SFN/4. To prevent access failures caused when the same RA-RNTI is used for UEs
in different coverage levels, it is recommended that the difference between the
PRACH start time for different coverage levels be at least 40 ms.
The smallest value of {8 ms, 16 ms, 32 ms, 64 ms, 128 ms, 256 ms, 512 ms, 1024
ms} that meets the preceding conditions is used.
l The PRACH transmission period is specified by the
CellRachCECfg.PrachTransmissionPeriod parameter. This parameter must be set to
the same value for all coverage levels. The PRACH transmission period must be at least
equal to the sum of the PRACH occupation duration and PRACH start time configured
for the highest coverage level, as shown in Figure 3-22. If the PRACH transmission
period does not meet these requirements, NB-IoT cell activation fails.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 55


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Figure 3-22 Relationships among PRACH transmission period, PRACH occupation


duration, and PRACH start time

For example, if three coverage levels, CL0, CL1, and CL2 are configured, the
CellRachCECfg.PrachRepetitionCount parameter for these three coverage levels is set to
REP_2(REP_2), REP_8(REP_8), and REP_32(REP_32), respectively, and the
RACHCfg.NbCyclicPrefixLength parameter is set to 66DOT7(66DOT7), the PRACH
occupation duration for CL0, CL1, and CL2 is 5.6 x 2 ms, 5.6 x 8 ms, and 5.6 x 32 ms,
respectively. The PRACH start time for CL0 is 8 ms. Accordingly:
l The PRACH start time for CL1 must be at least 48 ms (the sum of the PRACH start time
for CL0 (8 ms) and MAX {40 ms, 5.6 x 2 ms}). The smallest value in the value range
that meets this condition is 64 ms, which is then used as the PRACH start time for CL1.
l The PRACH start time for CL2 must be at least 108.8 ms (the sum of the PRACH start
time for CL1 (64 ms) and MAX {40 ms, 5.6 x 8 ms}). The smallest value in the value
range that meets this condition is 128 ms, which is then used as the PRACH start time
for CL2.
l The PRACH transmission period must be at least the sum of the PRACH occupation
duration and PRACH start time for the highest coverage level. The PRACH occupation
duration is 5.6 x 32 ms, and the PRACH start time is 128 ms, so the PRACH
transmission period must be at least 307.2 ms.

Configurations of PRACH Start Time and PRACH Transmission Period When


RACHCfg.PrachStartTimeCfgInd Is Set to CFG(Configure)
When the RACHCfg.PrachStartTimeCfgInd parameter is set to CFG(Configure):
l The PRACH start time for each coverage level is specified by the
CellRachCECfg.PrachStartTime parameter.
l The PRACH transmission period is specified by the
CellRachCECfg.PrachTransmissionPeriod parameter. This parameter must be set to
the same value for all coverage levels.
l The PRACH start time and PRACH transmission period must meet all of the conditions
described below. If any condition is not met, NB-IoT cell activation fails.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 56


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

There must be at least a 40 ms difference between the PRACH start time for any
two coverage levels.
The PRACH transmission period must be at least equal to the sum of the PRACH
start time and PRACH occupation duration of any coverage level.
The configurations of the PRACH start time, PRACH transmission period, and
PRACH occupation duration must meet the requirement that the PRACH resources
of all coverage levels do not overlap in a super frame. Specifically, the PRACH
resources allocated to a coverage level cannot overlap with all PRACH resources
allocated to other coverage levels.
Figure 3-23 presents an example of how to determine whether the PRACH resources for
transmission period i of coverage level 0 (CL0i) overlap with those for transmission period j
of coverage level 1 (CL1j).

Figure 3-23 An example of the PRACH resource overlap determination

Calculate the center points of CL0i and CL1j, and the spacing between these two center points
as follows:
Center point of CL0i = PRACH transmission period for CL0 x i + PRACH start time for CL0
+ PRACH occupation duration for CL0/2
Center point of CL1j = PRACH transmission period for CL1 x j + PRACH start time for CL1
+ PRACH occupation duration for CL1/2
Spacing between these center points (L) = Center point of CL1j Center point of CL0i. If
the calculated result of the spacing is a negative value, the absolute value is used for PRACH
resource overlap determination.
l If the spacing is at least half of the sum of PRACH occupation durations for CL0 and
CL1, the PRACH resources for CL0i do not overlap with those for CL1j.
l If the spacing is less than half of the sum of PRACH occupation durations for CL0 and
CL1, the PRACH resources for CL0i overlap with those for CL1j.

Table 3-5 presents an example of how to plan the PRACH start time for different coverage
levels in three co-sited cells. To reduce the interference between NPRACH signals for
coverage level 2 in these three cells, the NPRACH resource overlap time for coverage level 2
must be minimized.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 57


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Table 3-5 An example of how to plan the PRACH start time for different coverage levels in
three co-sited cells
Cell PRACH Start Time PRACH Start Time PRACH Start Time for
for Coverage Level 0 for Coverage Level 1 Coverage Level 2

Cell 0 SF256 (subframe 256) SF512 (subframe 512) SF8 (subframe 8)

Cell 1 SF8 (subframe 8) SF512 (subframe 512) SF256 (subframe 256)

Cell 2 SF8 (subframe 8) SF512 (subframe 512) SF128 (subframe 128)

3.5.1.4 NPRACH Detection Threshold


When configuring the CellRachCECfg.PrachRepetitionCount parameter for each coverage
level, operators must also configure the CellRachCECfg.PrachDetectionThld parameter for
NPRACH detection.
l Setting the CellRachCECfg.PrachDetectionThld parameter to a high level results in a
lower probability of missing PRACH detection but a higher probability of false PRACH
detection.
l Setting the CellRachCECfg.PrachDetectionThld parameter to a low level results in a
lower probability of false PRACH detection but a higher probability of missing PRACH
detection.

3.5.2 RRC Connection Setup


SRB1bis and SRB1 are set up during RRC connection setup. When control plane CIoT EPS
optimization is enabled, SRB1bis does not involve the PDCP layer. As such, security
activation and SRB1bis data encryption and integrity protection are not required during RRC
connection setup. When the user plane CIoT EPS optimization function is enabled, SRB1bis
is used before security activation, and SRB1 is used after security activation. Unlike SRB1bis,
SRB1 involves the PDCP layer. Figure 3-24 shows the RRC connection setup procedure.

Figure 3-24 RRC connection setup procedure

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 58


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

1. The UE sends the eNodeB an RRC Connection Request message containing the cause of
RRC connection setup.
NOTE

l The cause of RRC connection setup is related to NAS procedures and NAS session types. For
details, see 3GPP TS 24.301. When the UE needs to report exception conditions, the cause of
RRC connection setup is "mo-ExceptionData."
l The RRC Connection Request message contains the UE_ID field. If the upper layer provides
the S-TMSI, the UE signals the S-TMSI to the eNodeB. If no S-TMSI is available, the UE
signals a random value ranging from 0 to 240-1 to the eNodeB. In NB-IoT, the international
mobile subscriber identity (IMSI) of the UE is unknown to the eNodeB.
2. The eNodeB sets up the context for the UE.
If the eNodeB receives multiple RRC Connection Request messages from a UE within
an amount of time specified by the RrcConnStateTimer.FilterReptRrcConnReqTimer
parameter, the eNodeB handles only the one that was received last.
Within the window specified by both the UeTimerConst.T300ForNb parameter and the
RrcConnStateTimer.FilterReptRrcConnReqTimer parameter, the eNodeB calculates
the number of RRC Connection Request messages sent by a UE, not including abnormal
transmission scenarios. If the number of RRC Connection Request messages sent by a
UE is greater than the value of the GlobalProcSwitch.RrcConnPunishThd parameter,
the eNodeB responds to the UE with an RRC Connection Reject message containing the
extended wait time IE, the value of which is determined by the
RrcConnStateTimer.ExtendedWaitTime parameter. Upon receiving the message, the
UE sends another RRC Connection Request message only after the extended waiting
time expires.
3. When the control plane CIoT EPS optimization function is enabled, the eNodeB
performs admission and allocates SRB1bis resources to the UE. When the user plane
CIoT EPS optimization function is enabled, the eNodeB performs admission and
allocates SRB1bis and SRB1 resources to the UE.
The eNodeB admits signaling connections.
If the resource allocation is successful, the subsequent steps proceed. If the resource
allocation fails, the eNodeB responds to the UE with an RRC Connection Reject
message.
In the case of overload, the eNodeB responds to the UE with an RRC Connection
Reject message. Upon receiving the RRC Connection Reject message, the UE must
wait a period of time before resending a request. The wait time is specified by the
RrcConnStateTimer.ExtendedWaitTime parameter.
4. The eNodeB sends an RRC Connection Setup message containing SRB1bis resource
configurations to the UE.
5. The UE configures radio resources based on the SRB1bis resource information indicated
by the RRC Connection Setup message, and then sends an RRC Connection Setup
Complete message to the eNodeB. After the eNodeB receives the RRC Connection
Setup Complete message, the RRC connection is set up.
The timer for the eNodeB to wait an RRC Connection Setup Complete message is as
follows:
When the NbCellDlSchCEAlgo.UuMessageWaitingTimer parameter is set to 0,
ENodeBConnStateTimer.UuMessageWaitingTimer is used.
When the NbCellDlSchCEAlgo.UuMessageWaitingTimer parameter is set to a
non-zero value, the NbCellDlSchCEAlgo.UuMessageWaitingTimer parameter is
used.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 59


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

3.5.3 RRC Connection Resume


For the NB-IoT UE supporting the user plane CIoT EPS optimization function, the RRC
connection can be suspended upon RRC release and UE context be stored, and later the RRC
connection can be resumed using the stored UE context. Figure 3-25 shows the RRC
connection resume procedure.

Figure 3-25 RRC connection resume procedure

1. The UE sends an RRC Connection Resume Request message to the eNodeB.


NOTE

l The cause of RRC connection resume is related to NAS procedures and NAS session types.
For details, see 3GPP TS 24.301. When the UE needs to report exception conditions, the cause
value is "mo-ExceptionData."
l The RRC Connection Resume Request message contains the ResumeIdentity assigned by the
eNodeB upon RRC connection suspension.
2. The eNodeB searches for the UE context based on the ResumeIdentity.
If the eNodeB receives multiple RRC Connection Resume Request messages from a UE
within the time specified by the RrcConnStateTimer.FilterReptRrcConnReqTimer
parameter, the eNodeB handles only the latest received one.
Within the window specified by both the UeTimerConst.T300ForNb parameter and the
RrcConnStateTimer.FilterReptRrcConnReqTimer parameter, the eNodeB calculates
the number of RRC Connection Resume Request messages received from the same UE,
except in abnormal data transmission scenarios. If the number of RRC Connection
Resume Request messages received from the same UE is greater than the value of the
GlobalProcSwitch.RrcConnPunishThd parameter, the eNodeB responds to the UE
with an RRC Connection Reject message containing the extended wait time IE, the value
of which is determined by the RrcConnStateTimer.ExtendedWaitTime parameter.
Upon receiving the message, the UE sends another RRC Connection Resume Request
message only after the extended waiting time expires.
3. The eNodeB performs admission, and allocates SRB1bis and SRB1 resources to the UE.
The eNodeB admits signaling connections without any judgment.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 60


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

If the resource allocation is successful, the subsequent steps proceed. If the resource
allocation fails, the eNodeB responds to the UE with an RRC Connection Reject
message.
In the case of overload, the eNodeB responds to the UE with an RRC Connection
Reject message. Upon receiving the RRC Connection Reject message, the UE must
wait a period before resending a request. The wait time is specified by the
RrcConnStateTimer.ExtendedWaitTime parameter.
4. If the eNodeB successfully finds the UE context, the eNodeB sends the UE an RRC
Connection Resume message over SRB1, which contains radio resource configurations
and NextHopChainingCount for the UE to configure radio resources and activate
security configurations.
5. After the configuration is complete, the UE sends an RRC Connection Resume Complete
message with PLMN to the eNodeB. The reception of the RRC Connection Resume
Complete message by the eNodeB indicates that the RRC connection resume procedure
is complete. The timer for the eNodeB to wait for an RRC Connection Resume Complete
message is specified by the ENodeBConnStateTimer.WaitRrcConnSetupCmpTimer
parameter.

3.5.4 NB-IoT MME Selection


Huawei NB-IoT eNodeBs support control plane and user plane CIoT EPS optimization.
Whether to use only the control plane CIoT EPS optimization function, both of them, or
neither of them needs to be configured based on the MME's capability of supporting EPS
optimized transmission for NB-IoT, which is specified by the
MmeCapInfo.NbCiotEpsOptCap parameter. The MmeCapInfo.NbLteSupportCap
parameter specifies whether the MME supports LTE FDD and LTE TDD.
If MmeCapInfo.NbCiotEpsOptCap is set to CP or CP_UP, then both S1.MmeRelease and
S1INTERFACE.MmeRelease must be set to Release_R13.
NOTE

When the MmeCapInfo.NbCiotEpsOptCap parameter is set to CP(CP) or CP_UP(CP_UP), S1 links


will be interrupted if the MME supports only LTE FDD and LTE TDD.
If the MmeCapInfo MO is not configured or if MmeCapInfo.NbCiotEpsOptCap is set to
NOT_SUPPORT(NOT_SUPPORT), the NB-IoT cell fails to be activated.

For NB-IoT UEs supporting the user plane CIoT EPS optimization function, the eNodeB
preferentially selects an MME supporting this function to process their services. If no such an
MME is available, the eNodeB selects an MME supporting the control plane CIoT EPS
optimization function for service processing. For LTE FDD and LTE TDD UEs, the eNodeB
can select an MME with the MmeCapInfo.NbLteSupportCap parameter set to
SUPPORT(SUPPORT) for service processing.
NB-IoT eNodeBs can select the MME based on the NAS node selection function (NNSF),
configured policy (priority-, capacity-, or load-based), or on cell configurations. For details,
see S1-flex Feature Parameter Description.

3.5.5 Data Transmission


Basic Procedure
After control plane CIoT EPS optimization is enabled, UEs can transmit data to and receive
data from the EPC only after establishing an RRC connection. Figure 3-26 shows the data
transmission between the UE and EPC.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 61


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Figure 3-26 Data transmission between the UE and EPC after the control plane CIoT EPS
optimization function is enabled

1. The UE sends an RRC Connection Setup Complete message to the eNodeB.


2. On receiving the message, the eNodeB sends an Initial UE message to the MME,
including the NAS PDU IE, and information of the TAI and E-UTRAN cell global
identifier (ECGI).
3. The MME sends the eNodeB a Connection Establishment Indication message, which
contains the MME UE S1AP ID and eNB UE S1AP ID, for normal data transmission
between the UE and EPC.
4. Data is transmitted between the UE and MME.
After the user plane CIoT EPS optimization function is enabled, UEs can transmit data to and
receive data from the EPC after an RRC connection is established or resumed. Figure 3-26
shows the data transmission between the UE and EPC.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 62


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Figure 3-27 Data transmission between the UE and EPC after the user plane CIoT EPS
optimization function is enabled

1. The UE sends an RRC Connection Setup Complete message to the eNodeB.


2. On receiving the message, the eNodeB sends an Initial UE Message to the MME,
including the NAS PDU, TAI, and ECGI.
3. The MME sends an Initial UE Context Setup Request message to the eNodeB,
requesting the eNodeB to establish the UE context. On receiving the message, the
eNodeB triggers UE context establishment.
4. The eNodeB triggers an RRC security activation procedure to provide security and
integrity protection for data transmitted over the Uu interface.
5. The eNodeB triggers an RRC reconfiguration procedure to establish a DRB.
6. The eNodeB sends an Initial UE Context Setup Complete message to the MME,
indicating that the UE context has been established.
7. The MME sends a Modify Bearer Request message to the S-GW to establish the E-
UTRAN radio access bearer (E-RAB) in the EPC.
8. The uplink and downlink data is transmitted between the UE and S-GW through the E-
RAB.

Data Transmission Priority


The following lists the priorities of the uplink and downlink data transmitted between the UE
and EPC in descending order:

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 63


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Data of UEs with CSS1 > Data of UEs with CSS2 > Data of UEs with UE specific search
space (USS)
CSS is short for common search space. For details about the search space, see 3.6
Scheduling.

3.5.6 Signaling Connection Release


Signaling connection release consists of dedicated S1 connection release and RRC connection
release. Figure 3-28 shows a signaling connection release procedure.

Figure 3-28 Signaling connection release procedure

A signaling connection release procedure can be triggered by the MME or by the eNodeB:
l Triggered by the MME
The MME sends a UE Context Release Command message to the eNodeB when a
service process is complete on the NAS set up between the UE and MME or when the
MME aborts a service.
l Triggered by the eNodeB
The eNodeB sends a UE Context Release Request message to the MME after having
detected an exception, such as the expiry of the UE inactivity timer, a lack of data
transmission or reception on the UE side, or expiry of the Uu message waiting timer or
S1 message waiting timer. The eNodeB then waits for a UE Context Release Command
message from the MME.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 64


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

The eNodeB performs the following operations during a signaling connection release
procedure:

1. Releases transport resources and initiates RRC connection release over the Uu interface.
2. Sends an RRC Connection Release message to the UE, instructing the UE to release
radio resources.
3. Releases radio resources.
4. Sends a UE Context Release Complete message to the MME, indicating that the
resources have been released.
5. Releases the UE context. Then, the UE switches from the RRC_CONNECTED mode to
the RRC_IDLE mode.

The UE inactivity timer is specified by the RrcConnStateTimer.NbUeInactiveTimer


parameter. The Uu message waiting timer is specified by the
ENodeBConnStateTimer.UuMessageWaitingTimer or
NbCellDlSchCEAlgo.UuMessageWaitingTimer parameter, and the S1 message waiting
timer is specified by the ENodeBConnStateTimer.S1MessageWaitingTimer parameter.

3.6 Scheduling

3.6.1 Definition

Scheduling
NB-IoT uses shared-channel transmissions in which time-frequency resources are
dynamically shared among UEs. eNodeBs perform scheduling to allocate time-frequency
resources for uplink and downlink transmissions.

Schedulers
NB-IoT schedulers are located above the physical layer. The basic function of schedulers is to
allocate system resources to UEs for uplink and downlink transmissions.

The schedulers allow an optimal balance between single-user performance and overall
network capacity.

RU
Uplink resources are measured in resource units (RUs). The durations of RUs with different
subcarrier spacing in multiple scenarios are described in Table 3-1.

MCS
The MCS includes BPSK and QPSK.
l BPSK modulates one bit into a modulation symbol.
l QPSK modulates two bits into a modulation symbol.

High-order modulation modes are used in scenarios with high channel quality. A higher
modulation order (more bits per modulation symbol) helps improve transmission efficiency.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 65


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Search Space
The search space for the NPDCCH is classified into the CSS and USS. The CSS is further
classified into CSS1 (CSS for paging) and CSS2 (CSS for RAR/Msg3 retransmission/Msg4).
For details, see section 16.6 of 3GPP TS 36.213 (Release 13).

3.6.2 Scheduler Working Principle


An NB-IoT scheduler is positioned at the MAC layer to allocate resources on the UL-
SCH/DL-SCH to UEs and select appropriate MCSs for the transmission of system
information and user data.
Figure 3-29 shows the working principle of downlink schedulers.

Figure 3-29 Working principle of downlink schedulers

Figure 3-30 shows the working principle of uplink schedulers.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 66


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Figure 3-30 Uplink scheduling working principle

Inputs to the Scheduler


The sync status of UE-related inputs indicates the uplink synchronization status for UEs.
The data-related inputs include Data buffer status (DL), BSR (UL), and HARQ feedback, as
described in the following table.

Input Data Type Description

Data buffer status (DL) The amount of to-be-scheduled data in the Radio Link
Control (RLC) buffer.

Buffer status report (UL) A report to the eNodeB to indicate the amount of data in the
UL buffer of the UE.

HARQ feedback A response indicating whether data has been correctly


transmitted or retransmitted. HARQ feedback can be
acknowledgment (ACK), negative acknowledgment
(NACK), or discontinuous transmission (DTX).

Channel state inputs indicate that an uplink scheduler schedules resources for UEs and
allocates resources to UEs based on signal to interference plus noise ratios (SINRs), which
indicate uplink channel conditions. The eNodeB obtains SINRs by measuring demodulation
reference signals (DMRSs).

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 67


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Basic Scheduler Function


The basic scheduler functions include priority calculation, MCS/repetition selection, and
resource allocation, as described in the following table.

Basic Function Description

Priority calculation The scheduler determines the scheduling priority and


selected UEs based on the inputs.

MCS/Repetition selection The scheduler determines the MCS for each UE and
repetition counts based on the inputs.

Resource allocation The scheduler determines the scheduling duration and


positions of resources to be allocated to a UE based on the
data volume and the MCSs.

Outputs from the Scheduler


The scheduler outputs the following items:
l Scheduled UEs
l MCSs and repetition counts
l Scheduling duration and positions of resources

3.6.3 Uplink Scheduling

3.6.3.1 Uplink Scheduling Procedure


The scheduler performs sequential uplink scheduling in each TTI based on assigned priorities,
as shown in Figure 3-31.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 68


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Figure 3-31 Uplink scheduling procedure

3.6.3.2 Uplink Scheduling Triggering


Uplink scheduling can be triggered in the following scenarios:
l The eNodeB receives the DVI indicator carried in the Msg3 and the DVI indicator is not
0.
l The eNodeB receives the BSR indicator carried in the MAC CE in a message other than
Msg3 and the BSR indicator is not 0.

3.6.3.3 Uplink Scheduling for Retransmissions


Uplink scheduling involves NPUSCH, UCI, and Msg3 scheduling. Among them, UCI is not
retransmitted; NPUSCH and Msg3 can be retransmitted through asynchronous adaptive
HARQ retransmissions.
l In asynchronous HARQ retransmissions, a UE sends HARQ feedback four TTIs after the
initial transmission of the eNodeB, and the eNodeB retransmits the data at least four
TTIs after receiving a NACK.
l In adaptive HARQ retransmissions, the retransmitted TBS is the same as the initially
assigned TBS.
The maximum number of uplink HARQ retransmissions is specified by the
CellUlschAlgo.NbUlHarqMaxTxCount parameter. Uplink HARQ retransmissions are
stopped when the number of uplink HARQ retransmissions reaches the maximum.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 69


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

3.6.3.4 Uplink Scheduling for Initial Transmissions


This function includes UE selection, MCS selection, repetition count selection, and resource
allocation.

The MCS selection, repetition count selection, and resource allocation apply to the NPUSCH,
UCI, and Msg3.

UE Selection
The UEs to be scheduled are queued in descending order of service priority as follows:

UEs with CSS1 > UEs with CSS2 > UEs with the USS

MCS and Repetition Count Selection


MCS and repetition count selection for NPUSCH scheduling involves signal to interference
plus noise ratio (SINR) adjustment.

SINR Adjustment

SINR indicates uplink channel quality, based on which NB-IoT selects MCSs and repetition
counts for uplink scheduling. Due to the impact of channel fading on signals, the SINR at the
reporting time is significantly different from that at the scheduling time. Therefore, the SINR
needs to be adjusted based on the HARQ-ACK/HARQ-NACK feedback to uplink data.

The principles of SINR adjustment are as follows:

l If the current channel quality is lower than that required by the MCS the scheduler
selects, the block error rate (BLER) of data packets increases. The eNodeB then
decreases the SINR based on the HARQ-NACK feedback.
l If the current channel quality is higher than that required by the MCS the scheduler
selects, the BLER of data packets decreases. The eNodeB then increases the SINR based
on the HARQ-ACK feedback.

MCS and Repetition Count Selection

l When the eNodeB cannot acquire the measured SINR, MCSs and repetition counts are
specified by NbCellUlSchCEAlgo.UlInitialMcs and
NbCellUlSchCEAlgo.UlInitialTransRptCount, respectively.
l When the eNodeB has acquired the measured SINR, the eNodeB selects appropriate
MCSs and repetition counts based on the SINR.
NOTE

If a UE supports only single-tone transmission and the MCS index is set to or reselected as 11 or 12, the
MCS index actually selected will be 10.

For UCI, MCS selection is not involved.

For Msg4, the UCI repetition count is specified by


NbCellUlSchCEAlgo.AckNackTransRptCountMsg4.

For common data transmission, the UCI repetition count is specified by


NbCellUlSchCEAlgo.AckNackTransRptCount.

The Msg3 repetition count is specified by NbCellUlSchCEAlgo.UlInitialTransRptCount.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 70


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Resource Allocation
If a cell serves more than one UE, the amount of available NPUSCH/UCI resources is equal
to the amount of uplink resources across the entire channel bandwidth minus the amount of
resources occupied by the NPRACH and guard bandwidth.

The amount of time available for uplink scheduling is determined by the duration of the
NPUSCH, UCI, and Msg3 scheduling, as described in the following table.

Scheduling Type Description

NPUSCH Determined by the buffer status and SINR (including adjusted SINR)
scheduling after filtering.

UCI scheduling Determined by the UE's repetition counts.

Msg3 scheduling Determined by the coverage level, MCS, and repetition count.

Resource allocation involves allocating resources for NPUSCH scheduling, UCI scheduling,
and Msg3 scheduling.

NPUSCH Scheduling

The eNodeB uses the NPDCCH pre-allocation results, defined uplink timing constraints, start
position constraints, and uplink DTX constraints to determine the available NPUSCH start
position and duration, and allocates NPUSCH resources to UEs for scheduling.

l Uplink timing constraints


In accordance with 3GPP TS 36.213 (Release 13), the interval between the NPUSCH
start position and DCI end position is greater than or equal to 8 ms.
l Start position constraints
In accordance with section 6.4.3.1 of 3GPP TS 36.212 (Release 13), the relationship
between the NPUSCH start position and DCI end position (Sn) always meets one of the
following formulas:
Start position = Sn + 1 + 8
Start position = Sn + 1 + 16
Start position = Sn + 1 + 32
Start position = Sn + 1 + 64
l Uplink DTX constraints
In accordance with section 10.1.3.6 of 3GPP TS 36.211 (Release 13), the NPUSCH
transmission stops for 40 ms after each data transmission of 256 ms. During the 40 ms,
uplink and downlink scheduling for this UE is not allowed, but uplink data for other UEs
can be transmitted.

UCI Scheduling

Based on the NPDSCH pre-allocation results, defined downlink timing constraints, start
position constraints, and uplink DTX constraints, the eNodeB determines the available UCI
start position and UCI duration, and allocates NPUSCH resources to UEs for downlink
scheduling.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 71


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

l Downlink timing constraints


In accordance with 3GPP TS 36.213 (Release 13), the interval between the UCI start
position and NPDSCH end position is greater than or equal to 12 ms.
l Start position constraints
In accordance with 3GPP TS 36.212 (Release 13), the relationship between the UCI start
position and NPDSCH end position (Sn) meets one of the following formulas:
Start position = Sn + 1 + 12
Start position = Sn + 1 + 12 + 2
Start position = Sn + 1 + 12 + 4
Start position = Sn + 1 + 12 + 5
l Uplink DTX constraints
In accordance with section 10.1.3.6 in 3GPP TS 36.211 (Release 13), the UCI
transmission stops for 40 ms after each data transmission of 256 ms. During the 40 ms,
uplink and downlink scheduling for this UE is not allowed, but uplink data for other UEs
can be transmitted.

Msg3 Scheduling

Based on the NPDCCH scheduling results, defined uplink timing constraints, start position
constraints, and uplink DTX constraints, the eNodeB determines the available Msg3 start
position and NPUSCH duration, and allocates NPUSCH resources to UEs for scheduling.

l Timing constraints
In accordance with 3GPP TS 36.213 (Release 13), the interval between the Msg3 start
position and Random Access Response (RAR) end position is greater than or equal to 12
ms.
l Start position constraints
In accordance with 3GPP TS 36.212 (Release 13), the relationship between the
NPUSCH start position and end position for Msg3 scheduling in the RAR message (Sn)
meets one of the following formulas:
Start position = Sn + 1 + 12
Start position = Sn + 1 + 16
Start position = Sn + 1 + 32
Start position = Sn + 1 + 64
l Uplink DTX constraints
In accordance with section 10.1.3.6 in 3GPP TS 36.211 (Release 13), the Msg3
transmission stops for 40 ms after each data transmission of 256 ms. During the 40 ms,
uplink and downlink scheduling for this UE is not allowed, but uplink data for other UEs
can be transmitted.

3.6.4 Downlink Scheduling

3.6.4.1 Downlink Scheduling Procedure


The scheduler performs sequential downlink scheduling in each TTI based on priorities, as
shown in Figure 3-32.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 72


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Figure 3-32 Downlink scheduling procedure

3.6.4.2 Downlink Scheduling for Retransmissions


Downlink scheduling uses asynchronous adaptive HARQ retransmissions:

l In asynchronous HARQ retransmissions, a UE sends HARQ feedback four TTIs after the
initial transmission of the eNodeB, and the eNodeB retransmits the data at least four
TTIs after receiving a NACK.
l In adaptive HARQ retransmissions, the retransmitted TBS is the same as the initially
assigned TBS.

Downlink scheduling determines the repetition count used in a HARQ retransmission as


follows:
l If the eNBCellRsvdPara.RsvdU8Para22 parameter is set to 0, the repetition count is the
same as that assigned during the initial transmission.
l If the eNBCellRsvdPara.RsvdU8Para22 parameter is not set to 0, the repetition count is
increased by the first scheduling for retransmissions. This repetition count will be used
by the subsequent scheduling for retransmissions (if there are).

The maximum number of downlink HARQ retransmissions is specified by the


CellDlschAlgo.NbDlHarqMaxTxCount parameter. Downlink HARQ retransmissions are
stopped when the number of downlink HARQ retransmissions reaches the maximum.

3.6.4.3 Downlink Scheduling for Initial Transmissions


This function includes UE selection, MCS selection, repetition count selection, and resource
allocation.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 73


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

UE Selection
The UEs to be scheduled are queued in descending order by procedure priority as follows:
UEs with CSS1 > UEs with CSS2 > UEs with the USS

MCS and Repetition Count Selection


During initial access, MCSs and repetition counts are specified by the
NbCellDlSchCEAlgo.DlInitialMcs and NbCellDlSchCEAlgo.DlInitialTransRptCount
parameters, respectively. The initial MCS for RAR and Msg4 depends on the value of
ENBCELLRSVDPARA.RsvdU8Para22:
l If the value is not 0, the initial MCS index is equal to the smaller between 4 and the
value of NbCellDlSchCEAlgo.DlInitialMcs.
l If the value is 0, the initial MCS index is equal to the value of
NbCellDlSchCEAlgo.DlInitialMcs.
To ensure reliable downlink transmission during service interaction, The eNodeB adjusts
MCSs and repetition counts based on the number of received ACK and NACK messages.
The adjustment principles are as follows:
l If the current channel quality is lower than that required by the MCS the scheduler
selects, the BLER of data packets increases. Then, the eNodeB decreases the MCS index
based on the HARQ-NACK feedback. When the MCS index is adjusted to 0, the
repetition counts will be adjusted accordingly.
l If the channel quality is higher than that required by the MCS the scheduler selects, the
BLER of data packets decreases. The eNodeB then increases the MCS index based on
the HARQ-ACK feedback. When the MCS index is adjusted to the largest value, the
repetition counts will be adjusted accordingly.
NOTE

l In LTE in-band deployment mode, if the MCS index is set or adjusted to 11 or 12, the MCS
index actually selected will be 10. Therefore, it is recommended that the MCS index be not set
to 11 or 12 in LTE in-band deployment mode.
l When COVERAGE_EXTENSION_SWITCH under the CellDlschAlgo.NbCellAlgoSwitch
parameter is set to Off, the MCS index will be 0 and the repetition count will be 1.

Resource Allocation
The amount of time allowed for downlink scheduling is determined by the expected allocated
number of RUs based on the UE's buffer status, coverage level, and repetition count.
NPDCCH scheduling protocol constraints
To determine the available NPDSCH start position and NPDSCH duration, and to allocate
NPDSCH resources to UEs, the eNodeB uses the NPDCCH scheduling results and the
following:
l Downlink timing constraints: In accordance with 3GPP TS 36.213 (Release 13), the
interval between the NPDSCH start position and DCI end position must be greater than
or equal to 4 ms.
l Start position constraints: In accordance with section 6.4.3.1 of 3GPP TS 36.212
(Release 13), the relationship between the NPDSCH start position and the DCI end
position (Sn) must be relative to the maximum repetition count, as described in the
following table.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 74


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Maximum Relationship Between NPDSCH Start Position and


Repetition Count Sn

Rmax < 128 Start position = Sn + 1 + 4


Start position = Sn + 1 + 4 + 4
Start position = Sn + 1 + 4 + 8
Start position = Sn + 1 + 4 + 12
Start position = Sn + 1 + 4 + 16
Start position = Sn + 1 + 4 + 32
Start position = Sn + 1 + 4 + 64
Start position = Sn + 1 + 4 + 128

Rmax 128 Start position = Sn + 1 + 4


Start position = Sn + 1 + 4 + 16
Start position = Sn + 1 + 4 + 32
Start position = Sn + 1 + 4 + 64
Start position = Sn + 1 + 4 + 128
Start position = Sn + 1 + 4 + 256
Start position = Sn + 1 + 4 + 512
Start position = Sn + 1 + 4 + 1024

RAR message scheduling


The RAR window size must be set to an appropriate value so that RAR messages can be
transmitted within the window. In NB-IoT:
l For coverage level 0, the RAR window size is 10 times the NPDCCH period.
l For coverage levels 1 and 2, the RAR window size is 5 times the NPDCCH period.
NPDCCH period = CellPdcchCECfg.PdcchMaxRepetitionCnt x
CellPdcchCECfg.PdcchPeriodFactor
Timer adjustment principles
If the NPDCCH period is adjusted, determine whether the related timers need to be adjusted
as follows:
l If a timer uses the NPDCCH period as its unit, you are advised not to adjust it generally.
l If a timer uses s or ms as its unit, you are advised to adjust it. The ratio of the adjusted
timer length to the adjusted NPDCCH period should equal or approach the pre-
adjustment ratio.
Example
The NPDCCH period for coverage level 0 is 16 ms, the conflict resolution timer lasts for 8
NPDCCH periods, and the NB-IoT timer T300 lasts for 10,000 ms.
If the NPDCCH period is adjusted to 64 ms, then the conflict resolution timer does not need
to be adjusted generally but the NB-IoT timer T300 needs to be adjusted, for example, to
40,000 ms. If the NPDCCH period is adjusted to a very large value while the timers that use s
or ms as their unit are not adjusted, terminals may fail to access the cell.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 75


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Paging message scheduling constraints

The start position for a paged UE cannot be occupied so that the UE can receive paging
messages. To ensure successful paging, the following configuration requirements must be
met:
l When the PCCHCfg.MaxNumRepetitionForPaging parameter is set to
NULL(Invalid), the number of the enumerated value of the PCCHCfg.NbForNbIoT
parameter must be greater than or equal to that of the
CellPdcchCECfg.PdcchMaxRepetitionCnt parameter. For example, when the
PCCHCfg.NbForNbIoT parameter is set to HALF_T~3, 3 is the number of this
enumerated value.
l When the PCCHCfg.MaxNumRepetitionForPaging parameter is not set to
NULL(Invalid), the number of the enumerated value of the PCCHCfg.NbForNbIoT
parameter must be greater than or equal to that of the
PCCHCfg.MaxNumRepetitionForPaging parameter.

3.7 Power Control

3.7.1 Downlink Power Control


NB-IoT uses fixed power allocation for downlink power control. Time division multiplexing
is used for different channels. Each subframe uses a fixed channel and has the same total
power. The downlink power can be calculated based on the narrowband reference signal
(NRS) power.

NRS Power Allocation


NRSs are transmitted in all downlink subframes and used for downlink channel estimation
and data demodulation.

The NRS power is indicated by the energy per resource element (EPRE) and specified as
follows:

l In non-SFN scenarios, the NRS power is specified by the


PDSCHCfg.ReferenceSignalPwr parameter.
l In SFN scenarios:
If the eUCellSectorEqm.ReferenceSignalPwr parameter is set to 32767, the NRS
power is calculated based on the setting of PDSCHCfg.ReferenceSignalPwr.
Otherwise, the NRS power is specified by the
eUCellSectorEqm.ReferenceSignalPwr parameter.

The PDSCHCfg.ReferenceSignalPwr parameter specifies the pilot power output by the


RRU. Generally, the pilot power broadcast in SIB2 is equal to the value of
PDSCHCfg.ReferenceSignalPwr. However, this will lead to incorrect UE path loss
calculation in some scenarios, for example, when repeaters are used to amplify RRU output
power. In these scenarios, use the AntRsPwrSwitch option of the
CellAlgoSwitch.RepeaterSwitch parameter to adjust the pilot power broadcast in SIB2:
l If this option is deselected, use the value of PDSCHCfg.ReferenceSignalPwr as the
pilot power broadcast in SIB2.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 76


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

l If this option is selected, calculate the pilot power broadcast in SIB2 as follows:
a. Set the wideband transmit power at each antenna port by using the
CellChPwrCfg.AntOutputPwr parameter.
b. Set the proportion of NB-IoT cell output power (OutputPowerRate) by using the
eNBCellRsvdPara.RsvdU16Para8 parameter.
c. Calculate the gain (, dB) of amplified power relative to un-amplified power at the
antenna port:
= 10lg(CellChPwrCfg.AntOutputPwr x OutputPowerRate) - RruOutputPwr
where
CellChPwrCfg.AntOutputPwr's unit is W, which needs to be converted into mW.
RruOutputPwr (dBm) is the maximum transmit power at the antenna port calculated
based on NRSs.
OutputPowerRate:
If the eNBCellRsvdPara.RsvdU16Para8 parameter value is not 0, it is used in the
preceding formula.
If the eNBCellRsvdPara.RsvdU16Para8 parameter value is 0, then:
n In LTE in-band deployment scenarios, the proportion of NB-IoT cell output
power is used in the preceding formula. The eNodeB automatically calculates
this proportion and the proportion of LTE FDD cell output power when the
LTE FDD cell meets the following conditions:
The AntRsPwrSwitch option of the CellAlgoSwitch.RepeaterSwitch
parameter of the LTE FDD cell is selected.
The eNBCellRsvdPara.RsvdU16Para8 parameter of the LTE FDD cell is set
to 0.
n In other scenarios, the value 1000 is used in the preceding formula.
d. Calculate the pilot power broadcast in SIB2.
AntReferenceSignalPwr (dBm) = PDSCHCfg.ReferenceSignalPwr +

NPDSCH Power Calculation


In power control for the NPDSCH, OFDM symbols in a given timeslot can be classified as
type A or type B. Type A symbols are those without reference signals, and type B symbols are
those with reference signals.

Number of Type A Symbol Type B Symbol Number of


Antenna Ports Reference Signal
REs for Type B
Symbols

1 0, 1, 2, 3, and 4 5 and 6 2

2 0, 1, 2, 3, and 4 5 and 6 4

The RE power of type A symbols is identical.


l When there is one cell antenna port, the RE power is identical to the NRS power.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 77


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

l When there are two cell antenna ports, the RE power is half of the NRS power.

The non-pilot RE power of type B symbols is identical.


l When there is one cell antenna port, the RE power is identical to the NRS power.
l When there are two cell antenna ports, the RE power is half of the NRS power.

In standalone and LTE guard band deployment modes, the following formulas are true:
l When there is one cell antenna port:

Scenario Calculation Formula

Non-SFN P(NPDSCH_A) = P(NPDSCH_B) =


(PDSCHCfg.ReferenceSignalPwr/10 + 10 x lg12) dBm

SFN P(NPDSCH_A) = P(NPDSCH_B) =


(eUCellSectorEqm.ReferenceSignalPwr/10 + 10 x lg12) dBm

l When there are two cell antenna ports:

Scenario Calculation Formula

Non-SFN P(NPDSCH_A) = P(NPDSCH_B) =


(PDSCHCfg.ReferenceSignalPwr/10 + 10 x lg12 3) dBm

SFN P(NPDSCH_A) = P(NPDSCH_B) =


(eUCellSectorEqm.ReferenceSignalPwr/10 + 10 x lg12 3) dBm

In LTE in-band deployment mode, the first three symbols of each subframe must be punctured
for LTE FDD PDCCH, and do not consume power in NB-IoT cells.

Four REs of certain OFDM symbols in each subframe must be punctured due to its
coexistence with the CRS in an LTE FDD cell. They do not consume NB-IoT cell power. The
symbols occupied by the CRS, with different LTE FDD antenna configurations, are described
in the following table.

Number of LTE FDD CRS Symbol Index


Antenna Ports

1 and 2 0, 4, 7, and 11

4 0, 1, 4, 7, 8, and 11

The actual transmit power of symbols punctured by the CRS in NB-IoT cells is as follows:

l When there is one cell antenna port:

Scenario Calculation Formula

Non-SFN NPDSCH_Inband = (PDSCHCfg.ReferenceSignalPwr/10 + 10 x lg10)


dBm

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 78


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Scenario Calculation Formula

SFN NPDSCH_Inband = (eUCellSectorEqm.ReferenceSignalPwr/10 + 10


x lg10) dBm

l When there are two cell antenna ports:


Scenario Calculation Formula

Non-SFN NPDSCH_Inband = (PDSCHCfg.ReferenceSignalPwr/10 + 10 x lg10


3) dBm

SFN NPDSCH_Inband = (eUCellSectorEqm.ReferenceSignalPwr/10 + 10


x lg10 3) dBm

The transmit power of other symbols is calculated in the same way as that in standalone and
LTE guard band deployment modes.

NOTE

NB-IoT cells support no more than two antenna ports.

NPSS Power Calculation


In NB-IoT cells, time division multiplexing is implemented between the NPSS and other
downlink channels. The NPSS punctures for the LTE FDD PDCCH in all deployment modes,
so the first three symbols of each NPSS subframe do not consume NB-IoT cell power. The
power calculation for other symbols varies with the deployment modes.
l In standalone and LTE guardband deployment modes
When there is one cell antenna port:
Scenario Calculation Formula

Non-SFN P(NPSS_A) = P(NPSS_B) = (PDSCHCfg.ReferenceSignalPwr/10


+ 10 x lg11) dBm

SFN P(NPSS_A) = P(NPSS_B) =


(eUCellSectorEqm.ReferenceSignalPwr/10 + 10 x lg11) dBm

When there are two cell antenna ports:


Scenario Calculation Formula

Non-SFN P(NPSS_A) = P(NPSS_B) = (PDSCHCfg.ReferenceSignalPwr/10


+ 10 x lg11 3) dBm

SFN P(NPSS_A) = P(NPSS_B) =


(eUCellSectorEqm.ReferenceSignalPwr/10 + 10 x lg11 3)
dBm

l In LTE in-band deployment mode, the transmit power including that of LTE FDD CRS is
described in the following table.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 79


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Scena Number Whether Transmit Power Including That of LTE


rio of PCI mod 3 FDD CRS in LTE In-band Deployment
Antenn Is 2 in an Mode
a Ports LTE FDD
Cell

Non- 1 Yes NPSS_Inband =


SFN (PDSCHCfg.ReferenceSignalPwr/10 + 10 x
lg10) dBm

No NPSS_Inband =
(PDSCHCfg.ReferenceSignalPwr/10 + 10 x
lg9) dBm

2 Yes NPSS_Inband =
(PDSCHCfg.ReferenceSignalPwr/10 + 10 x
lg8 3) dBm

No NPSS_Inband =
(PDSCHCfg.ReferenceSignalPwr/10 + 10 x
lg7 3) dBm

SFN 1 Yes NPSS_Inband =


(eUCellSectorEqm.ReferenceSignalPwr/10
+ 10 x lg10) dBm

No NPSS_Inband =
(eUCellSectorEqm.ReferenceSignalPwr/10
+ 10 x lg9) dBm

2 Yes NPSS_Inband =
(eUCellSectorEqm.ReferenceSignalPwr/10
+ 10 x lg8 3) dBm

No NPSS_Inband =
(eUCellSectorEqm.ReferenceSignalPwr/10
+ 10 x lg7 3) dBm

NSSS Power Calculation


In NB-IoT cells, time division multiplexing is implemented between the NSSS and other
downlink channels. The NSSS punctures for the LTE FDD PDCCH in all deployment modes,
so the first three symbols of each NSSS subframe do not consume NB-IoT cell power. The
power calculation for other symbols is the same as that of the symbols of the NPDSCH.

NPBCH Power Calculation


In NB-IoT cells, time division multiplexing is implemented between the NPBCH and other
downlink channels. The NPBCH punctures for the LTE FDD PDCCH and CRS in all
scenarios, so the power calculation of NPBCH subframes is the same as that of the NPDSCH
in LTE in-band scenarios.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 80


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

NPDCCH Power Calculation


In NB-IoT cells, time division multiplexing is implemented between the NPDCCH and other
downlink channels.
l When the NPDCCH aggregation level is 2, each scheduling unit of NPDCCH occupies
all the frequency resources of the NB-IoT cells. Its power is calculated in the same way
as for the NPDSCH.
l When the NPDCCH aggregation level is 1, each scheduling unit of NPDCCH occupies
six subcarriers. NPDCCH resources can be allocated to two UEs in the current subframe.
If only one scheduling unit of NPDCCH resources is allocated in the current subframe,
the NPDCCH power is half that of NPDSCH. Otherwise, the power is calculated in the
same way as for the NPDSCH.

3.7.2 Uplink Power Control


NB-IoT supports only open-loop power control in the uplink to reduce UE power
consumption and system overhead.

3.7.2.1 NPRACH Power Control


The purpose of power control for the NPRACH is to ensure the random access success rate, to
minimize transmit power, reduce interference with neighboring cells, and to conserve UE
power.
In a cell configured with coverage level 0, the transmit power of the NPRACH is calculated
using the following formula:
PNPRACH = min{PCMAX,
NARROWBAND_PREAMBLE_RECEIVED_TARGET_POWER + PL}_[dBm]
l PCMAX is the UE's maximum transmit power, which is specified by the
Cell.UePowerMax parameter.
l NARROWBAND_PREAMBLE_RECEIVED_TARGET_POWER is the target power
expected by the eNodeB when the requirements for the preamble detection performance
are met. It is specified by the RACHCfg.PreambInitRcvTargetPwr parameter.
l PL is the downlink path loss estimated by the UE. This value is obtained based on the
RSRP measurement value and the transmit power of the CRS. The transmit power of the
CRS is set using the eUCellSectorEqm.ReferenceSignalPwr parameter in SFN
scenarios and using the PDSCHCfg.ReferenceSignalPwr parameter in non-SFN
scenarios. The Alpha filtering coefficient for RSRP measurement values is specified by
the CellUlpcDedic.FilterRsrp parameter. The UE acquires the two parameters from
SIBs.
In a cell not configured with coverage level 0, the UE always uses PCMAX as the transmit
power of the NPRACH.

3.7.2.2 NPUSCH Power Control


The NPUSCH supports only open-loop power control.
If the current NPUSCH scheduling repetition count is greater than 2, the UE always uses
PCMAX as the transmit power. Otherwise, the transmit power of the NPUSCH (unit: dBm) is
calculated using the following formula:

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 81


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

where

l i indicates the current timeslot.


l c indicates the serving cell.
l PCMAX is the UE's maximum transmit power, which is specified by the
Cell.UePowerMax parameter.
l MNPUSCH is the number of subcarriers. When single-tone transmission uses a subcarrier
spacing of 3.75 kHz, MNPUSCH is set to 1/4. When single-tone transmission uses a
subcarrier spacing of 15 kHz, MNPUSCH is set to 1. When multi-tone transmission is used,
MNPUSCH equals the number of subcarriers, which is 3, 6, or 12.
l PL is the downlink path loss estimated by the UE. This value is obtained based on the
RSRP measurement value and the transmit power of the CRS. The transmit power of the
CRS is set using the eUCellSectorEqm.ReferenceSignalPwr parameter in SFN
scenarios and using the PDSCHCfg.ReferenceSignalPwr parameter in non-SFN
scenarios. The Alpha filtering coefficient for RSRP measurement values is specified by
the CellUlpcDedic.FilterRsrp parameter. The UE acquires the two parameters from
SIBs.
l PO_NPUSCH is the receive power determined by the eNodeB. It indicates the receive
power density for the NPUSCH expected by the eNodeB when the correct NPUSCH
demodulation is ensured.
PO_NPUSCH,c = P0_NORMINAL_NPUSCH,c + P0_UE_NPUSCH,c
If the current NPUSCH carries Msg3 during a random access, PO_UE_NPUSCH is set to 0

and
where
PO_PRE is the target power expected by the NPRACH and is specified by the
RACHCfg.PreambInitRcvTargetPwr parameter.

is the Msg3's power offset relative to a preamble and is specified by


the CellUlpcComm.DeltaPreambleMsg3 parameter.
Otherwise, P0_NORMINAL_NPUSCH indicates the transmit power density expected by the
eNodeB for normal NPUSCH demodulation. It is specified by the
CellUlpcComm.P0NominalPUSCH parameter. P0_UE_NPUSCH is the power offset
relative to P0_NORMINAL_NPUSCH for the UE. This value reflects the impact of the UE's
coverage level, service type, and channel quality on the transmit power of the NPUCCH.
P0_UE_NPUSCH is now set to 0 by default.
l indicates the path loss compensation factor. If the current NPUSCH carries Msg3 in
random access or UCI, is set to 1. Otherwise, is specified by the
CellUlpcComm.PassLossCoeff parameter, whose recommended value is AL1(1). If
CellUlpcComm.PassLossCoeff is inappropriately set, the receive power of NPUSCH
format 2 (for UCI transmission) is much higher than that of NPUSCH format 1 (for
common data transmission) and consequently causes strong interference to adjacent
subcarriers, as the two NPUSCH formats use the same P0_NORMINAL_NPUSCH. For details
about the two NPUSCH formats, see Table 3-1.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 82


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

3.8 Admission Control, Congestion Control, and Overload


Control
Admission Control
When a new service attempts to access a cell, admission control checks the limits of the
system resources, including load and user volume.
1. If the CPU resource is insufficient, the eNodeB rejects the access request. For details
about how the eNodeB checks whether the CPU resource is insufficient, see Flow
Control Feature Parameter Description.
2. If the maximum allowable user volume has been reached, the admission fails. The
maximum allowable user volume is determined as follows:
If the CellRacThd.AcUserNumber parameter is set to a value less than or equal to
the maximum allowable number of RRC_CONNECTED UEs in a cell, this
parameter value is used as the maximum allowable user volume.
If this parameter is set to a value greater than the maximum allowable number of
RRC_CONNECTED UEs in a cell, the latter is used as the maximum allowable
user volume.
If the total number of UEs served by a board exceeds the board capacity, the
maximum allowable user volume is preferentially subject to the board capacity.
NOTE

For details about the maximum allowable number of RRC_CONNECTED UEs in a cell and that
supported by main control boards and baseband boards, see 3900 Series Base Station Technical
Description.
3. If the admission fails, the involved UE attempts to preempt resources allocated to other
UEs. High-priority UEs are allowed to preempt the resources allocated to low-priority
UEs when NbUeNumPreemptSwitch under the
ENodeBAlgoSwitch.UeNumPreemptSwitch parameter is turned on. UE priorities are
determined based on the RRC connection setup cause. The following lists the RRC
connection setup causes in the descending order of priority:
a. Mobile Originated Exception Data (mo-Exception-Data)
b. Paging
c. Mobile Terminated Access (mt-Access)
d. Mobile Originated Signaling (mo-Signaling)
e. Mobile Originated Data (mo-Data)
f. delayTolerantAccess-v1330
For services whose value of "Pre-emption Vulnerability" in the ARP is "not pre-
emptable", the allocated resources cannot be preempted.
4. When NB-IoT and LTE FDD cells are co-sited, NB-IoT and LTE FDD cells share RRC
resources. When no idle RRC resources are available, LTE FDD UEs initiating RRC
connection requests can preempt the RRC resources occupied by NB-IoT UEs if
ENODEBALGOSWITCH.LTEPreemptNbSwitch is turned on.
LTE FDD UEs preferentially preempt the resources occupied by low-priority NB-
IoT UEs. NB-IoT UEs with the RRC connection setup cause of
delayTolerantAccess-v1330 are considered to have the lowest priority, and their

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 83


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

resources are preempted prior to other UEs. NB-IoT UEs whose value of "Pre-
emption Vulnerability" is "not pre-emptable" are the last choice for resource
preemption.
To prevent excessive RRC resource preemption from affecting NB-IoT UE access,
a minimum number of RRC_CONNECTED UEs is reserved for NB-IoT. This
minimum number equals the product of
ENodeBNbPara.NbRsvMinUserNumRatio and the maximum number of
RRC_CONNECTED UEs supported by the eNodeB. When the number of
RRC_CONNECTED UEs in NB-IoT is less than or equal to this minimum number,
LTE FDD UEs are not allowed to preempt the RRC resources occupied by NB-IoT
UEs.

Congestion Control
Congestion control consists of backoff and access barring.
l Backoff
A large number of random access requests lead to a high load or even a reset of the
eNodeB. Random access flow is limited by controlling the number of preambles to be
processed. The eNodeB sends different backoff time indications to UEs based on the
NPRACH congestion status. The UE initiates a new network access request at a random
time based on the backoff time indication in the received message, so as to avoid
conflicts. The backoff function is controlled by BackOffSwitch under the
CellAlgoSwitch.RachAlgoSwitch parameter.
If some UEs on the live network do not support the maximum backoff index 12 defined
in 3GPP TS 36.321 (Release 13), operators must also turn on PreambleSchEnhSwitch
under the CellAlgoSwitch.UlSchExtSwitch parameter.
l Access barring
To protect the existing system and UEs from the possible impact of a sudden spike in UE
access, the eNodeB implements access barring based on dynamic load.
Access barring is defined in 3GPP TS 36.331 (Release 13). When a cell or all the MMEs
connected to an eNodeB are congested, the eNodeB broadcasts access class control
parameters in SIB14. UEs then determine whether to initiate access requests in the
current cell based on the received parameters. The EABAlgoSwitch option of the
CellAlgoSwitch.MTCCongControlSwitch parameter specifies whether to enable this
function.
The eNodeB can use the CellEABAlgoPara.ABForExceptionData parameter to control
whether NB-IoT UEs with the access cause of mo-ExceptionData can access the
network, and can use the ABForSpecialAC parameter to indicate NB-IoT UEs with
access classes 11 to 15 can initiate the access.
The cell congestion status is determined based on flow control status or CPU load,
depending on the value of the eNodeBFlowCtrlPara.DynAcBarPolicyMode parameter.
The access barring type is specified by the CellEABAlgoPara.EABCategory parameter.
UE access to the network in a given measurement period is allowed or barred based on
the following conditions:
The measurement period starts when the access barring algorithm switch is turned on.
The length of the measurement period is specified by
CellEABAlgoPara.EABStatPeriod parameter.
The triggering condition for access barring is as follows:
Proportion of cell congestion duration CellEABAlgoPara.EABTriggerThd

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 84


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

If this triggering condition is met, UEs belonging to certain access classes are
barred from accessing the network for a duration specified by the
CellEABAlgoPara.EABStatPeriod parameter.
The leaving condition for access barring is as follows:
Proportion of cell congestion duration CellEABAlgoPara.EABCancelThd
If the leaving condition is met for a number (N) of consecutive measurement
periods, UEs belonging to certain access classes are allowed to access the network.
N is specified by the CellEABAlgoPara.EABCancelCondSatiPeriod parameter.
UEs read the AB messages in the SIB14 period. The SIB14 period is specified by
the CellSiMap.NbSib14Period parameter.
In Figure 3-33 (parameter values from Table 3-6 are used as examples):
a. When the proportion of cell congestion within 20s is greater than 90%, or if all the
MMEs connected to the eNodeB deliver overload messages, the eNodeB will send
an SIB14 message to the UE.
b. To ensure that the UE can receive the SIB14 message, the eNodeB must send
paging messages or NPDCCH messages to notify the UE of system message
changes. After the reception of a change notice, the UE obtains ab_Enabled from
the MIB message. If access barring is enabled, the UE obtains a new AB message in
the SIB14 period.
c. UEs belong to access class 0, based on the bit information in the AB message, are
barred from accessing the network for a period of time equal to the measurement
period.
d. If the leaving condition is met for two consecutive periods (the proportion of cell
congestion within 20s is smaller than 70%), the eNodeB will not send the SIB14
message and stop access barring on UEs.

Figure 3-33 Access barring

Table 3-6 AB parameter value examples

Parameter Name Parameter ID Example Value

EAB Control Statistic CellEABAlgoPara.EABS 20s


Periods tatPeriod

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 85


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Parameter Name Parameter ID Example Value

EAB Control Trigger CellEABAlgoPara.EABT 90%


Threshold riggerThd

EAB Control Cancel CellEABAlgoPara.EABC 70%


Threshold ancelThd

EAB Cancel Condition CellEABAlgoPara.EABC 2


Satisfied Period ancelCondSatiPeriod

EAB Category CellEABAlgoPara.EABC CATEGORY_A


ategory

NB-IoT SIB14 Period CellSiMap.NbSib14Perio RF512


d

NB-IoT Access Barring CellEABAlgoPara.ABFo BOOLEAN_FALSE


For Exception Data rExceptionData

NB-IoT Access Barring CellEABAlgoPara.ABFo AC11BARSTATE(AC11B


For AC11-15 rSpecialAC ARSTATE),
AC12BARSTATE(AC12B
ARSTATE),
AC13BARSTATE(AC13B
ARSTATE),
AC14BARSTATE(AC14B
ARSTATE),
AC15BARSTATE(AC15B
ARSTATE)

Overload Control
Overload control is implemented when there is a sudden spike in external services. NEs
control input and output flows to prevent overload and improve equipment stability. Overload
control improves NE stability by reducing the possibility of NE resets. It can also reduce the
risk of a decreased access success rate and provide a more stable user experience.
l MME-overload-triggered overload control
The objective of MME-overload-triggered overload control is to relieve the impact of
MME overload caused by a large number of UEs accessing the network.
When an MME is overloaded, it sends an OVERLOAD START message to the eNodeB,
indicating that the eNodeB needs to start flow control. The eNodeB then limits UE
access based on their RRC connection setup causes. When MME overload is relieved, it
sends an OVERLOAD STOP message to the eNodeB indicating that the eNodeB should
stop flow control. For details, see 3GPP TS 36.413.
l Random access flow control
A large number of random access requests lead to a high load or even a reset of the
eNodeB. Random access flow is limited by controlling the number of preambles to be
processed. The eNodeB adaptively adjusts the number of preambles to be processed
based on the CPU usage of the BBP control plane or the congestion status of air interface
resources. If the air interface is congested in a cell, the random access flow control is
controlled by UlRaUserSchOptSw under the CellAlgoSwitch.UlSchSwitch parameter.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 86


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

l Flow control on RRC Connection Request or RRC Connection Resume Request


messages
An RRC Connection Request or RRC Connection Resume Request message is the initial
message of a procedure. When an eNodeB accepts an RRC Connection Request or RRC
Connection Resume Request message, a lot of subsequent processing is required,
causing excessive overhead. Therefore, initial access request control is necessary to
reduce the load on the eNodeB.
To ensure user experience of high-priority services, initial access request control
processes access requests based on configured priorities. Ensured control-plane services
are prioritized in the following order:
a. Mobile Originated Exception Data (mo-Exception-Data)
b. Paging
c. Mobile Terminated Access (mt-Access)
d. Mobile Originated Signaling (mo-Signaling)
e. Mobile Originated Data (mo-Data)
f. delayTolerantAccess-v1330
When an eNodeB is overloaded, it rejects or discards some RRC Connection Request or
RRC Connection Resume Request messages it receives based on the CPU usage of the
main control board or baseband board.
If the eNodeB load is heavy for too long, the eNodeB controls the number of signaling
messages received from peer NEs to reduce the load as follows:
A reduction of the SCTP buffer threshold can decrease the amount of signaling
from the MME to the eNodeB and reduce the MME's downlink load on the
eNodeB.
The eNodeB reduces the frequency of UE accesses to the network using access
barring to reduce the uplink load.
l Paging load control
Excessive paging requests will lead to an extreme increase in the volume of paging
messages and must be controlled. To ensure user experience for high-priority services,
paging flow control will be implemented based on paging priorities.

Application Description
A sudden spike in UE access leads to cell air interface resource congestion, causes difficulty
in UE access, and degrades network performance. Under these circumstances, operators are
advised to:
l Enable the backoff function.
l Enable the access barring function.
l Enable the random access flow control function.
l Turn on ExtendedwaittimeSwitch under the CellAlgoSwitch.MTCCongControlSwitch
parameter to allow the eNodeB to include the extendedWaitTime IE in RRC Connection
Release messages. This IE delays UE access and thereby relieves the resource
congestion over the air interface.

3.9 DRX
DRX is a technology in which a UE can switch between active and sleep states to save power.
When the UE needs to receive downlink data, the UE turns on its receiver and enters the

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 87


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

active state. When there is no need to receive downlink data, the UE turns off its receiver and
enters the sleep state.

3.9.1 DRX-related Concepts

On Duration
When the UE is in DRX connected mode, it does not always keep its receiver off. It
periodically turns on its receiver and monitors the NPDCCH for incoming signaling for a
consecutive period. This consecutive period is called On Duration, which is defined by the
CellDrxPara.NbOnDurationTimer parameter.

DRX Cycle
A DRX cycle is the interval between two On Durations. A DRX cycle consists of an On
Duration and a possible period of sleep time, as shown in Figure 3-34.

Figure 3-34 DRX cycle

NOTE

The On Duration Timer will stop after certain conditions are met.

The DRX period can be divided into active time and sleep time based on UE behavior. NB-
IoT supports only the long DRX cycles. The long NB-IoT DRX cycle is specified by the
CELLDRXPARA.NbLongDrxCycle parameter, which is set as follows:
l This parameter is set to SF256 in versions earlier than V100R012C10SPC210.
l This parameter is set based on the network plan in V100R012C10SPC210 and later
versions.

Active Time
In active time, the UE turns on its receiver and monitors the NPDCCH. Active time is equal
to On Duration plus other possible periods during which the UE needs to turn on its receiver,
for example, when other DRX timers are running. DRX timers include the DRX Inactivity
Timer, DRX Retransmission Timer, and DRX UL Retransmission Timer.

If the duration of a DRX cycle is specified:


l A longer active time reduces service delay but increases UE power consumption.
l A shorter active time saves power but increases delay.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 88


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Sleep Time
During a DRX cycle, if a UE is not active, it is in sleep mode. A UE in sleep mode does not
monitor the NPDCCH, but it can still transmit and receive NPUSCH/NPDSCH messages
scheduled during active time. When no data is transmitted, the UE can turn off its receiver.

3.9.2 Startup of a DRX Cycle


If the following formula is met in a given moment:
[(SFN x 10) + SSFN] mod (CellDrxPara.NbLongDrxCycle) = DRX start offset
The On Duration timer starts at that moment, that is, the DRX cycle starts.

NOTE

l SFN: System Frame Number


l SSFN: System Subframe Number

3.9.3 Operation in a DRX Cycle


The DRX cycle includes active time and sleep time, as shown in Figure 3-35.

Figure 3-35 Switchover between DRX active and sleep time

Table 3-7 describes the related DRX timers.

Table 3-7 DRX timers


Timer Parameter ID Definit Description
ion

On Duration CellDrxPara.Nb Functio This timer starts at the beginning of a


Timer OnDurationTime n DRX cycle and specifies the time during
r which the UE can monitor the NPDCCH.

Startup This timer starts at the first subframe of a


DRX cycle.

Timing The UE's NPDCCH period is used as a


measurement unit.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 89


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Timer Parameter ID Definit Description


ion

Stop l The timer stops when the transmission


of the last repeated block in the
NPDCCH message to the UE is
complete.
l This timer stops after it expires.

Expiry After this timer expires, the UE enters the


sleep state, no longer monitoring the
NPDCCH.

DRX CellDrxPara.Nb Functio This timer determines whether the UE


Inactivity DRXInactivityTi n active time extends due to the arrival of
Timer mer transmitted or retransmitted data.

Startup During uplink and downlink scheduling,


this timer can start or restart after the
HARQ RTT Timer expires.

Timing The UE's NPDCCH period is used as a


measurement unit.

Stop l The timer stops when the transmission


of the last repeated block in the
NPDCCH message to the UE is
complete.
l This timer stops after it expires.

Expiry After this timer expires, the UE enters the


sleep state, no longer monitoring the
NPDCCH.

DRX CellDrxPara.NB Functio This timer specifies the maximum amount


Retransmissio DRXReTxTimer n of time the UE will wait for downlink
n Timer retransmission in active time. If the UE
has not received the downlink
retransmitted data before this timer
expires, the UE will no longer accept it.

Startup During uplink and downlink scheduling,


this timer can start or restart after the
HARQ RTT Timer expires.

Timing The UE's NPDCCH period is used as a


measurement unit.

Stop This timer stops if the UE receives the


retransmitted data before the timer
expires.

Expiry After this timer expires, the UE takes no


further action.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 90


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Timer Parameter ID Definit Description


ion

DRX UL CellDrxPara.Nb Functio This timer specifies the maximum amount


Retransmissio DRXUlReTxTime n of time the UE will wait for uplink
n Timer r retransmission in active time. If the UE
has not received the uplink retransmission
scheduling indicator before this timer
expires, the UE will no longer monitor the
NPDCCH.

Startup During uplink and downlink scheduling,


this timer can start or restart after the
HARQ RTT Timer expires.

Timing The UE's NPDCCH period is used as a


measurement unit.

Stop l This timer stops if the UE receives the


retransmitted data before the timer
expires.
l The timer stops when the transmission
of the last repeated block in the
NPDCCH message to the UE is
complete.

Expiry After this timer expires, the UE takes no


further action.

HARQ RTT N/A Functio This timer specifies the interval between
Timer n the initial downlink data transmission and
the first downlink HARQ retransmission.
This timer is used to determine when to
start the timer related to a prolonged DRX
active time.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 91


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Timer Parameter ID Definit Description


ion

Startup This timer starts after the last repeated


block of NPDSCH or NPUSCH resources.
l Downlink HARQ RTT Timer duration
= k + N + 3 + deltaPDCCH
where
k indicates the interval between the last
transmission subframe and the first
subframe in the HARQ feedback, N
indicates transmission duration of the
HARQ feedback, and 3 +
deltaPDCCH indicates the interval
between the last subframe in the
HARQ feedback and the most
upcoming NPDCCH opportunity (a
minimum of 3 ms).
l Uplink HARQ RTT Timer duration = 4
+ deltaPDCCH
where
4 + deltaPDCCH indicates the interval
between the end subframe of the
NPUSCH and the most upcoming
NPDCCH opportunity (a minimum of
4 ms).

Timing Timing is based on the number of


subframes.

Stop This timer stops after it expires.

Expiry When this timer stops, the DRX Inactivity


Timer, DRX Retransmission Timer, or
DRX UL Retransmission Timer starts.

3.10 Idle Mode eDRX


This section describes the optional feature MLOFD-120220 Idle Mode eDRX.

3.10.1 eDRX Time Synchronization Mechanism


In accordance with section 4.5.13.3 of 3GPP TS 23.682 (Release 13), the eNodeB aligns its
H-SFN with the MME's by matching the eDRX start times (setting a reference time for H-
SFN 0). Then the eNodeB and MME separately calculate the current H-SFN. To ensure that
UEs can correctly receive paging messages in eDRX, the recommended time synchronization
precision between the eNodeB and MME is 1s to 2s. The eNodeB and MME ensure their own
time synchronization precision without exchanging synchronization signaling between them.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 92


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

eNodeB clock synchronization is classified into time synchronization and frequency


synchronization. For details, see Synchronization Feature Parameter Description.
l When the eNodeB parameter TASM.CLKSYNCMODE is set to FREQ(FREQ),
eNodeB clock synchronization can be configured using either of the following methods:
Turn on TASM. LPFNSYNCSW controlling low-precision frame synchronization
to enable the configured IEEE1588 V2 clock for the eNodeB. The GPS time
provided by the IEEE1588 V2 clock meets the clock synchronization requirements
of Idle Mode eDRX between the eNodeB and MME. The MME does not need to
support the premature sending of paging messages to the eNodeB.
Configure a Network Time Protocol (NTP) clock source, and run the SET
FNSYNCTIME command to set the date and time for NB-IoT frame
synchronization to achieve time synchronization with the MME. This method does
not support automatic time source switchovers. The TIMESRC.TIMESRC
parameter must be set to NTP, and the TIMESRC.AUTOSWITCH parameter must
be set to OFF. As the synchronization precision of the eNodeB can only reach
5.12s, the MME must support the premature sending of paging messages so that
UEs can be paged within the PTW. It is recommended that the eNodeB synchronize
the time with the NTP clock source every two hours. If the MME uses a GPS clock
for synchronization, the UTC time needs to be converted into the GPS time, and the
SET LEAPSECONDSINFO command needs to be executed to set the leap second
offset between the UTC and GPS. For the leap second adjustment value, see the
announcements of leap seconds provided by the International Earth Rotation and
Reference Systems Service, formerly known as the Earth Orientation Center.
l When the eNodeB parameter TASM.CLKSYNCMODE is set to TIME(TIME), the
eNodeB needs to achieve time synchronization with the MME based on the initial GPS
time.

3.10.2 eDRX Paging Mechanism


UEs stay in the deep sleep state for most of an eDRX paging cycle and monitor the paging
channel only in the PTW. An eDRX paging cycle is much longer than a common paging
cycle. Specifically, an eDRX paging cycle is measured in HSFNs (1 HSFN = 1024 SFNs),
and its length is within the range of {10.24s x 2^i} where i can be any value from 1 to 10.
Therefore an eDRX paging cycle can last a maximum of 2.92 hours. The length of a PTW is
an integer multiple of 2.56s, with a maximum length of 40.96s, which is the product of 16 and
2.56s.
The eNodeB and UE use the negotiated eDRX cycle TeDRX, H, the PTW length L, and
UE_ID_H to calculate the start SFN (PW_start SFN) and end SFN (PW_end SFN) of the
PTW, and deliver or monitor the paging message in the PTW. UE_ID_H is the hash ID
calculated by the S-TMSI using CRC-32. For example, if the eDRX cycle TeDRX, H negotiated
between the MME and UE is 8 HSFNs and the start position of the PTW is PH 2, the end
position of the PTW can be calculated based on the PTW length L, as shown in Figure 3-36.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 93


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Figure 3-36 Relationships between the HSFN, PH, and PTW

eDRX UEs monitor the paging channel in the PTW indicated by the PF and PO. The
monitoring mechanism is the same as that for DRX UEs described in 3.4.8 Paging.

3.10.3 eDRX Paging Handling


If SI changes in a UE's sleep duration, the eNodeB generates a PDCCH message including the
"systemInfoModification-eDRX" field in every PO starting from some multiple of 1024
HSFNs. The eNodeB continuously sends the PDCCH message to the UE in multiple DRX
cycles, indicating an SI change. Different UEs have different eDRX cycles, but all eDRX
cycles are multiples of 1024 HSFNs. Therefore, whenever the eNodeB sends an SI change
notification message, the UE is in the active state and can receive the message.
If the eNodeB needs to send an eDRX paging message to a specific UE, the eNodeB
calculates the first PO in the PTW corresponding to the UE's eDRX cycle, generates a paging
message, and fills in the paging record. If the PO is already occupied by the paging record or
"systemInfoModification-eDRX" for another UE, the eNodeB combines the information and
sends the paging message.
UEs in RRC_IDLE mode start their receivers to monitor the NPDCCH at POs in the PTW in
each eDRX cycle. After the UE parses its own paging message, it sends a paging response
message to the MME. In addition, the UE sends the eNodeB an RRC Connection Request
message in which the value of "Establishment Cause" is mt-Access.
If the UE parses the P-RNTI but does not find its own paging record, or if the UE does not
parse P-RNTI from the NPDCCH message, the UE immediately disables the receiver and
enters the DRX state. If the UE does not receive a paging message in the PTW or if the PTW
expires, the UE immediately disables the receiver and enters the eDRX sleep state.

3.10.4 eDRX Negotiation and Paging


UEs in the RRC_IDLE mode can intermittently listen to paging messages while using
extended discontinuous reception (eDRX), after negotiating with the EPC, if UEs' power
consumption needs to be reduced and mobile terminated services (MT services) have
requirements on delay. Figure 3-37 shows the signaling procedures for eDRX negotiation and
paging.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 94


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Figure 3-37 Signaling procedures for eDRX negotiation and paging

1. The eNodeB includes the HSFN in the MIB and in SIB1. An HSFN lasts 10.24s, which
is the unit of an eDRX cycle.
2. The UE obtains the HSFN and determines whether to use DRX or eDRX based on its
own capabilities. If a UE uses eDRX, it includes the eDRX cycle length in an Attach
Request/TAU Request message sent to the MME.
3. If the MME accepts the eDRX request, it configures a different eDRX cycle and the size
of the PTW for the UE according to the predefined policy, and includes the information
in an Attach Accept/TAU Accept message to the UE. If the MME rejects the eDRX
request, the UE uses the DRX paging mechanism.
4. The UE and MME stores the "Extended DRX Parameters" after negotiation, and uses the
stored parameter values as the eDRX cycle later.
5. When an MME has a paging message for the UE, it calculates the HSFN and paging
hyperframe (PH) for the UE based on the negotiated eDRX cycle.
6. The MME sends the paging message to the eNodeB before the PH time for the UE
arrives.
7. On receiving the paging message, the eNodeB uses the eDRX cycle carried in the
message to calculate the time of the HSFN and PH. The eNodeB also calculates the PO
for the UE based on the configured paging cycle, and sends the paging message to the
UE at the calculated time.
The UE calculates the paging message delivery time the same way the eNodeB does, and
monitors and receives the paging message during this time.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 95


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

When Idle Mode eDRX is enabled, the UE periodically monitors the paging channel and can
receive MT services. In traditional power saving mode, however, the UE cannot receive MT
services unless it proactively accesses the network. It will take a long time generally for a UE
to proactively access the network, depending on the mobile-originated (MO) data reporting
period and TAU period. Therefore, Idle Mode eDRX is suitable for machine-to-machine
(M2M) services that require short delays for downlink MT services (for example, tracking the
locations of children and elderly people).

3.10.5 Scheduling of eDRX Paging Messages


eDRX paging messages in the PTW are scheduled in the same way as DRX paging messages.
For details about the scheduling of DRX paging messages, see 3.4.8 Paging.

3.11 NB-IoT Coverage Extension


This section describes the optional feature MLOFD-120201 NB-IoT Coverage Extension.
Before the concept of "coverage level" was introduced, all UEs in the coverage area used the
same power and the same MCS. To ensure reliable transmission, the power consumption of
the UEs would be increased and network capacity would be decreased. With the "coverage
level" concept, NB-IoT cells are classified into different coverage levels. The UE selects an
appropriate coverage level based on the signal strength, to process services. Low coverage
levels have strong signals and high rates. High coverage levels have weak signals and low
rates.
NB-IoT supports three coverage levels: 0, 1, and 2. The coverage level is specified by the
Cell.CoverageLevelType parameter. By default, only the normal coverage scenario is
supported. That is, only coverage level 0 is supported. Without this feature enabled, uplink
and downlink scheduling are performed based on the minimum allowable number of
repetitions, and coverage enhancement cannot be provided. Consequently, the network does
not respond to random access requests initiated by UEs in a coverage level other than
coverage level 0.

Figure 3-38 Coverage levels

The NB-IoT Coverage Extension feature is controlled by


COVERAGE_EXTENSION_SWITCH under the CellAlgoSwitch.NbCellAlgoSwitch

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 96


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

parameter. When this feature is enabled, uplink and downlink scheduling selects the repetition
count based on the UE signal quality and coverage level. In this way, UEs in coverage
enhancement areas can access the network normally. It is recommended that the
Cell.CoverageLevelType parameter be adjusted when this feature is enabled. More
information about parameter adjustment can be found in 8.6 Parameter Optimization.
In LTE in-band deployment or LTE guard band deployment, UEs in an area of coverage level
2 may fail to camp on a cell even when the minimum receive level of the cell is set to a very
small value. To enable such UEs to camp on the cell, operators can reduce the actual
minimum receive level of the cell by configuring the delta-RxLevMin, which is specified by
the ENBCELLRSVDPARA.RsvdU8Para17 parameter.

3.12 Multi-tone
This section describes the optional feature MLOFD-120230 Multi-tone.
According to 3GPP TS 36.211 (Release 13), NB-IoT supports single-tone and multi-tone
transmissions in the uplink. Single-tone transmission is mandatory for UEs, while multi-tone
transmission is optional. There are three types of multi-tone transmission: 3-tone, 6-tone, and
12-tone. This means that an eNodeB can allocate 3, 6, or 12 subcarriers (15 kHz each),
respectively, at a time for uplink data transmission. In areas with favorable coverage, multi-
tone transmission increases data rates and reduces the transmission delay and power
consumption for uplink data transmission.
Multi-tone is controlled by MULTITONE_SWITCH under the
CellAlgoSwitch.NbCellAlgoSwitch parameter. Figure 3-39 shows the multi-tone triggering
procedure.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 97


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Figure 3-39 Multi-tone triggering procedure

1. When multi-tone is enabled, the eNodeB sends SIB2 carrying the "nprach-
SubcarrierMSG3-RangeStart-r13" field to a multi-tone-capable UE, notifying the UE of
the start position of NPRACH resources.
2. The multi-tone-capable UE uses the allocated NPRACH resources to initiate a random
access request.
3. The eNodeB allocates multi-tone Msg3 resources to the UE if the number of repetitions
of NPRACH information is less than or equal to 32 times. Otherwise, the eNodeB
allocates single-tone Msg3 resources to the UE.
4. If the UE supports multi-tone transmission, it uses the allocated Msg3 resources to send
the eNodeB an RRC Connection Request message carrying the "multiToneSupport"
field.
5. The eNodeB determines whether the UE supports multi-tone transmission based on the
received information, and allocates multiple subcarriers to the multi-tone-capable UE for
uplink data transmission. The eNodeB determines the number of subcarriers to be
allocated based on factors such as the power headroom report (PHR), initial offset of the
resources to be allocated, and whether the resources to be allocated conflict with
NPRACH resources.
6. The UE uses the allocated uplink resources for uplink data transmission and uplink
scheduling.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 98


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

NOTE

l The length of Msg3 is always 88 bits, and the scheduling delay of Msg3 is almost the same,
regardless of whether single-tone transmission or multi-tone transmission is used.
l NPRACH resources consist of two parts: One is used by multi-tone-capable UEs to send random
access requests and the other used by single-tone-capable UEs to send random access requests. The
access capability of single-tone-capable UEs is decreased. Therefore, in the current version "nprach-
SubcarrierMSG3-RangeStart-r13" is fixed at value 1, which means that Msg3 always uses single-
tone transmission.
l The eNodeB uses only Msg3 to determine whether a UE supports multi-tone transmission and to
notify the UE of resources for uplink data transmission.

3.13 Multiple-Antenna Reception


This section describes the following features:

l MLBFD-12000238 UL 2-Antenna Receive Diversity


l MLOFD-121202 UL 4-Antenna Receive Diversity

3.13.1 Overview
Multiple-antenna reception is a technique in which signals received by multiple antennas are
combined using a special algorithm. Multiple-antenna reception must be supported by both
the eNodeB and UEs. The sub-sections that follow describe how multiple-antenna reception
works on the eNodeB side.

3.13.2 Receive Diversity


With receive diversity, each UE transmits data using a single transmit antenna and dedicated
time-frequency resource while the eNodeB receives the data using multiple antennas and then
combines the received data. This process maximizes the SINR, delivers diversity and array
gains, and improves cell capacity and coverage.

The radio channel from the transmitter to the receiver may experience time-varying deep
fading of 10 dB to 20 dB due to its fading characteristics, which will lead to SINR
fluctuations at the receiver. If the receiver uses multiple antennas for data reception, the
combined signals experience a lower probability of deep fading than the signals received by a
single antenna, because deep fading is not likely to occur on the signals received by all of the
antennas at once. The white noise received by the different antennas is random, and therefore
the power of the combined noise remains unchanged. However, the energy of the combined
signal increases several-fold.

Diversity Gains

Diversity gains are subject to the diversity orders of spatial channels. If the TX and RX
antenna channels are mutually orthogonal, and signals from all TX antennas are the same, an
MxN (M TX antennas, and N RX antennas) system delivers theoretical diversity gains of MxN
compared with the 1x1 system. The diversity order (MxN) theoretically represents the fault
tolerance capability of a spatial channel. Theoretically, the fault tolerance capability of an
MxN system is MxN times that of a 1x1 system.

Diversity gains indicate improved SINR stability and signal reliability at the receiver end.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 99


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Figure 3-40 Diversity gains

Array Gains
Compared with a 1x1 system, a 1xN system and an Mx1 system bring array gains of 10 lg(N)
dB and 10 lg(M) dB, respectively.
Array gains indicate higher SINR and better signal quality at the receiver end, as shown in
Figure 3-41.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 100


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Figure 3-41 Array gains

Principles of Receive Diversity

Figure 3-42 shows the principles of receive diversity.

Figure 3-42 Principles of receive diversity

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 101


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

In Figure 3-42, the UE sends signal x to antennas r1 to rM of the eNodeB on different


channels. The eNodeB applies a weight wi to each received signal, and then combines the
weighted signals into signal y. The combined signal can be expressed as follows:

y = W (Hx + N)

l W = (w1 ... wM)


A 1xM vector composed of the receive antenna weights.
l H = (h1 ... hM)T
An Mx1 channel matrix where hi indicates the channel coefficient, and T indicates the
transposition of the matrix. The amplitude and phase of a signal will change after passing
through the channel. The new signal is equal to the product of the signal multiplied by
the channel coefficient.
l N = (n1 ... nM)T
An Mx1 vector composed of the noise received by the RX antennas.
l x = the transmit signal.

Signal combining, especially the calculation of the weights to be applied to each antenna, is
key to receive diversity.

3.13.3 Receiver Technologies


Multiple-antenna reception is supported on the NPUSCH and NPRACH. The involved
receiver technologies are maximum ratio combining (MRC) and interference rejection
combining (IRC). In the current version, only MRC is supported. Therefore, this section
mainly describes the principles involved in MRC.

MRC must meet certain equalization criterion, for example, a minimum mean square error
(MMSE) or maximum signal to interference noise ratio (MSINR). In the current version,
MMSE MRC is used.

Both MMSE and MSINR require the calculation of Ruu, a covariance matrix of interference
and noise power. For MRC, Ruu is a diagonal matrix and only the entries on the main
diagonal need to be calculated. For IRC, Ruu is not a diagonal matrix and all the entries in the
matrix need to be calculated.

Concepts
l MMSE
MMSE is the minimum mean square error between the actual and estimated values of a
TX signal. The estimated value is obtained based on RX signals.
l White noise
White noise is noise whose PSD is evenly distributed over the entire frequency domain.
l Colored interference
Colored interference is interference whose PSD is not evenly distributed over the entire
frequency domain.

Working Principles of MRC

Figure 3-43 uses MMSE as an example to show the general working principles of a receiver.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 102


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

Figure 3-43 General working principle of a receiver

The variables in Figure 3-43 are as follows:


l x0 is the signal.
l Ik is the interference, where k is the index of the interference source. k ranges from 1 to
m, where m indicates the number of interference sources.
l hk(p) is the channel coefficient for the TX signal (k = 0) or interference (k = 1, ..., m). p is
the index of an RX antenna, which can be 0 or 1.
l np is the white noise on RX antenna p, also known as additive white Gaussian noise
(AWGN).
l w(p) is the weighting of RX antenna p.
l rp is the signal on RX antenna p.
l y is the combined signal.

TX signal x0 and interference Ik are transmitted through their radio channels hk(p),
superimposed at the RX antennas, added to white noises np, and converted into RX signals rp.
The combined signal is calculated as follows:
y=WxR
Different receivers generate different weights (W) and perform equalization and combination
in different ways depending on these weights.

An MMSE MRC receiver can generate the weights (w(p)) that minimize the mean square error
between the combined signal (y) and the original signal (x0) when interference is similar to
white noise.
Assume that the original signal's power is Es, and the original signal, noise, and interference
are independent of each other. Then, the RX antenna weights (W) are calculated as follows,
where Ruu is a diagonal matrix of the interference and noise power measured by the eNodeB:

For MRC, assume that a covariance matrix of total estimated white noise and interference on
RU i is equal to Ruu. If the entries not on the diagonal are set to zero for MRC, Ruu can be
expressed as follows:

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 103


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

NRX indicates the number of RX antennas.

Then, the output signals after MRC processing can be expressed as follows:

where
R(i) indicates the RX signal vector.
H(i) indicates the channel vector.

3.14 Multiple-Antenna Transmission


This section describes the MLBFD-12100240 DL 4-Antenna Transmit Diversity feature.

3.14.1 Overview
Multiple-antenna transmission is a technique in which signals transmitted using multiple
antennas are processed using a special algorithm. Multiple-antenna transmission must be
supported by the eNodeB, but that is not necessary for UEs. This section describes multiple-
antenna transmission on the eNodeB side.

3.14.2 Transmit Diversity


Transmit diversity uses multiple antennas to transmit signals and their copies after encoding
based on the low correlation between spatial channels and the characteristics of radio waves
in time and frequency domains. These signals and their copies with different fading degrees
are then combined at the receiver. This process brings diversity gains and improves
transmission reliability.
MLBFD-12100240 DL 4-Antenna Transmit Diversity requires that the eNodeB have a
minimum of four transmit channels and four physical antennas. To prevent the need to adjust
feeder connections after RRU channels have already been connected to the physical antennas,
NB-RS port mapping has been introduced to map NB-RS ports to RRU channels, and beyond
that, to the physical antennas. Here, NB-RS ports refer to antenna ports (logical ports) for
transmitting NB-IoT reference signals. The number of NB-RS antenna ports is specified by
the Cell.CrsPortNum parameter. When this parameter is set to CRS_PORT_2(2 ports),
space frequency block coding (SFBC) is used.
The TX/RX mode is specified by the Cell.TxRxMode parameter, and the relationship between
NB-RS antenna ports and RRU channels is configured by the Cell.CrsPortMap parameter.
For example, if the TX/RX mode is 4T4R and two NB-RS ports are configured, it is
recommended that the Cell.CrsPortMap parameter be set to 4T2P_0101(4T2P_0101). NB-
RS antenna ports 0, 0, 1, and 1 are mapped to physical antennas +45, -45, +45, and -45.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 104


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 3 Technical Description

NOTE

Antenna ports mentioned in this document are logical ports used for transmission. They do not have
one-to-one relationship with physical antennas. Signals on one antenna port can be transmitted over one
or more physical antennas.

The following figure shows signal processing at the transmitter when SFBC is enabled.

l x1 and x2 are signals to be transmitted before being precoded.


l Asterisk (*) represents the conjugation of a matrix.
l f1 and f2 are subcarriers.
l Ports 0 and 1 are the antenna ports used for transmission.
SFBC encodes signals x1 and x2 over different antenna ports and subcarriers, and then:

l Transmits signals x1 and x2 over subcarriers f1 and f2 of port 0, respectively.


l Transmits signals -x2* and x1* over subcarriers f1 and f2 of port 1, respectively.

By transmitting the copies of signals x1 and x2 over different antenna ports and subcarriers,
SFBC brings diversity gains.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 105


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 4 Related Features

4 Related Features

This chapter describes the relationships between NB-IoT features and other features.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 106


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 4 Related Features

4.1 MLBFD-12000101 Standalone Deployment


Prerequisite Features
None

Mutually Exclusive Features


None

Impacted Features
Feature ID Feature Description
Name

LOFD-001070 Symbol When NB-IoT and LTE FDD cells share the same power
Power amplifier (PA), Symbol Power Saving provides fewer
Saving gains in LTE FDD cells. This is because the NB-IoT and
LTE FDD pilot symbols are staggered from each in the
time-domain and the PSS, SSS, MIB, and SIBs of NB-
IoT cells occupy more symbols in the time domain than
those of LTE FDD cells, reducing the chances of basic
symbol power saving.

4.2 MLBFD-12000102 LTE Guardband Deployment


Prerequisite Features
None

Mutually Exclusive Features


None

Impacted Features
Feature ID Feature Name Description

LBFD-001003 Scalable Bandwidth LTE guard band deployment requires that the
LTE FDD cell bandwidth be at least 10
MHz.

LOFD-001051 Compact Bandwidth In LTE guard band deployment, to avoid


mutual interference, NB-IoT cannot be
deployed on a guard band that has been
reduced after the introduction of compact
bandwidth.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 107


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 4 Related Features

Feature ID Feature Name Description

LOFD-001070 Symbol Power When NB-IoT and LTE FDD cells share the
Saving same power amplifier (PA), Symbol Power
Saving provides fewer gains in LTE FDD
cells. This is because the NB-IoT and LTE
FDD pilot symbols are staggered from each
in the time-domain and the PSS, SSS, MIB,
and SIBs of NB-IoT cells occupy more
symbols in the time domain than those of
LTE FDD cells, reducing the chances of
basic symbol power saving.

4.3 MLBFD-12000103 LTE In-band Deployment


Prerequisite Features
None

Mutually Exclusive Features


Feature ID Feature Name Description

LOFD-070220 eMBMS Phase 1 based on In the current version, NB-IoT


Centralized MCE conflicts with evolved multimedia
Architecture broadcast/multicast service
(eMBMS) MBSFN subframes in
LOFD-080215 eMBMS Service Continuity LTE in-band deployment mode, and
therefore the LTE In-band
Deployment feature is mutually
exclusive with the eMBMS Phase 1
based on Centralized MCE
Architecture feature.

LOFD-001031 Extended CP In the current version, both the NB-


IoT cell and the corresponding LTE
FDD cell do not support the
Extended CP feature in LTE in-band
deployment.

LOFD-081223 Extended Cell Access Radius LTE in-band deployment requires


Beyond 100km that NB-IoT cells share antenna
systems with LTE FDD cells. The
maximum radius of NB-IoT cells is
35 km, and one antenna system
cannot support ultra-long-distance
coverage and normal coverage at the
same time. Therefore, the
corresponding LTE FDD cells do not
support this feature.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 108


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 4 Related Features

Feature ID Feature Name Description

LOFD-081221 Super Combined Cell The Super Combined Cell feature


mainly applies to high-speed
mobility scenarios, whereas NB-IoT
currently does not support high-
speed mobility scenarios.

LOFD-001025 Adaptive Power LTE In-band Deployment is


Consumption mutually exclusive with the dynamic
voltage adjustment function of the
Adaptive Power Consumption
feature.

LOFD-001039 RF Channel Intelligent An NB-IoT cell in LTE in-band


Shutdown deployment mode becomes
unavailable when its corresponding
LOFD-001074 Intelligent Power-Off of LTE FDD cell is unavailable.
Carriers in the Same Therefore, LTE In-band Deployment
Coverage of UMTS Network is mutually exclusive with energy
LOFD-001042 Intelligent Power-Off of conservation features.
Carriers in the Same
Coverage

LOFD-001040 Low Power Consumption


Mode

MRFD-121133 Multi-RAT Carrier Joint


Intelligent
Shutdown(eNodeB)

LOFD-001070 Symbol Power Saving Enhanced symbol power saving can


be enabled only when UEs are
capable of identifying and handling
MBSFN subframes. In the current
version, conflicts with MBSFN
subframes cannot be avoided in LTE
in-band deployment, and therefore
LTE in-band deployment is mutually
exclusive with enhanced symbol
power saving.

Impacted Features
Feature ID Feature Name Description

LBFD-001003 Scalable Bandwidth LTE in-band deployment requires that the


LTE FDD cell bandwidth be at least 5
MHz.

LBFD-002025 Basic Scheduling LTE in-band deployment requires that


uplink frequency hopping (FH) be disabled

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 109


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 4 Related Features

Feature ID Feature Name Description

LBFD-001015 Enhanced Scheduling in the LTE FDD cells corresponding to


NB-IoT cells, and that the resources
LBFD-070106 PDSCH Efficiency reserved for NB-IoT be not allocated to
Improvement LTE FDD services.
LBFD-081104 UL Compensation
Scheduling

LBFD-00101502 Dynamic Scheduling

LBFD-002024 Congestion Control When flow control is triggered because of


a CPU overload, extended access barring
(EAB) is performed in NB-IoT cells.

LBFD-060102 Enhanced UL NB-IoT causes interference to LTE FDD


Frequency Selective SRS and therefore RBs used for NB-IoT
Scheduling should be excluded in frequency selective
scheduling.

LBFD-060103 Enhanced DL The subband CQI measurement should


Frequency Selective exclude the RBs occupied by NB-IoT.
Scheduling

LOFD-070208 Coordinated NB-IoT causes interference to LTE FDD


Scheduling based SRS, affecting the measured RSRP.
Power Control (Cloud
BB)

LOFD-003029 SFN

LOFD-070205 Adaptive SFN/SDMA NB-IoT causes interference to LTE FDD


SRS, affecting the measured RSRP.
When TM10 in the Adaptive SFN/SDMA
feature is used, some REs of the RB for
NB-IoT deployment are used to transmit
LTE FDD channel state information-
reference signals (CSI-RSs).
Consequently, the downlink capacity of
NB-IoT is decreased.

LOFD-001007 High Speed Mobility NB-IoT causes interference to LTE FDD


SRS, and therefore a measurement of
LOFD-001008 Ultra High Speed timing advance (TA) in the sub-band of the
Mobility RB for NB-IoT may fail. Consequently, a
longer measurement time is required for
uplink synchronization.

LOFD-001051 Compact Bandwidth In LTE in-band deployment, NB-IoT


cannot be deployed on the RBs of compact
bandwidth to avoid mutual interference.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 110


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 4 Related Features

Feature ID Feature Name Description

MLOFD-121280 eMTC Introduction If NB-IoT is deployed on an RB of a


narrow band available to eMTC, the RB
will not be allocated to eMTC, and
consequently the uplink and downlink
capacity of eMTC are decreased. It is
recommended that NB-IoT be deployed on
recommended RBs described in 3.2.3 LTE
In-band Deployment.

LEOFD-111307 eMIMO If TM10 is used, some REs of the RB for


NB-IoT deployment are used to transmit
LTE FDD CSI-RSs. Consequently, the
downlink capacity of NB-IoT is decreased.

LOFD-001070 Symbol Power Saving When NB-IoT and LTE FDD cells share
the same power amplifier (PA), Symbol
Power Saving provides fewer gains in LTE
FDD cells. This is because the NB-IoT and
LTE FDD pilot symbols are staggered
from each in the time-domain and the PSS,
SSS, MIB, and SIBs of NB-IoT cells
occupy more symbols in the time domain
than those of LTE FDD cells, which then
reduce the chances of basic symbol power
saving.

4.4 MLBFD-12000202 Single-tone


Prerequisite Features
Feature ID Feature Name Description

MLBFD-12000234 Basic Scheduling Single-tone transmission is


used in the uplink and
therefore is dependent on
uplink scheduling.

Mutually Exclusive Features


None

Impacted Features
None

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 111


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 4 Related Features

4.5 MLBFD-12000203 Support of NB-IoT UE


Prerequisite Features
Feature ID Feature Name Description

MLBFD-12000234 Basic Scheduling During scheduling, eNodeBs must


consider the radio access capabilities of
the UEs.

Mutually Exclusive Features


None

Impacted Features
None

4.6 MLBFD-12000204 Data over NAS


Prerequisite Features
Feature ID Feature Name Description

MLBFD-12000228 RRC Connection The Data over NAS feature is dependent


Management on the RRC Connection Management
feature. The MME must support control
plane CIoT EPS optimization.

Mutually Exclusive Features


None

Impacted Features
None

4.7 MLBFD-12100205 Data over User Plane (Trial)


NOTE

Before using this feature, read 1.2 Disclaimer for Trial Features.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 112


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 4 Related Features

Prerequisite Features
Feature ID Feature Name Description

MLBFD-12000228 RRC Connection The Data over User Plane feature allows NB-
Management IoT service data to be carried on DRBs
established for it. It also enables the eNodeB
to preferentially select an MME supporting
the user plane CIoT EPS optimization
function for NB-IoT UEs.

MLBFD-12000203 Support of NB-IoT The Data over User Plane feature allows NB-
UE IoT service data to be carried on DRBs
established for it. This feature requires that
UEs support the user plane CIoT EPS
optimization function.

Mutually Exclusive Features


None

Impacted Features
None

4.8 MLBFD-12000226 Modulation: DL QPSK, UL QPSK/


BPSK
Prerequisite Features
None

Mutually Exclusive Features


None

Impacted Features
None

4.9 MLBFD-12000227 AMC


Prerequisite Features
None

Mutually Exclusive Features


None

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 113


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 4 Related Features

Impacted Features
None

4.10 MLBFD-12000228 RRC Connection Management


Prerequisite Features
Feature ID Feature Name Description

MLBFD-12000229 Broadcast of system The information required for cell


information access is broadcast in SI messages.

MLBFD-12000237 Cell Selection and Re- UEs in the RRC_IDLE mode can
selection initiate services after camping on a
cell.

Mutually Exclusive Features


None

Impacted Features
None

4.11 MLBFD-12000229 Broadcast of System Information


Prerequisite Features
None

Mutually Exclusive Features


None

Impacted Features
None

4.12 MLBFD-12000223 Physical Channel Management


Prerequisite Features
None

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 114


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 4 Related Features

Mutually Exclusive Features


None

Impacted Features
None

4.13 MLBFD-12000224 DL Asynchronous HARQ


Prerequisite Features
None

Mutually Exclusive Features


None

Impacted Features
Feature ID Feature Name Description

MLBFD-12000236 DRX When DRX is enabled, the wait time for


HARQ retransmission is specified by the
CellDrxPara.NBDRXReTxTimer
parameter.

4.14 MLBFD-12000225 UL Asynchronous HARQ


Prerequisite Features
None

Mutually Exclusive Features


None

Impacted Features
Feature ID Feature Name Description

MLBFD-12000236 DRX When DRX is enabled, the wait time


for HARQ retransmission is specified
by the
CellDrxPara.NbDRXUlReTxTimer
parameter.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 115


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 4 Related Features

4.15 MLBFD-12000230 Random Access Procedure


Prerequisite Features
None

Mutually Exclusive Features


None

Impacted Features
None

4.16 MLBFD-12000231 Paging


Prerequisite Features
None

Mutually Exclusive Features


None

Impacted Features
None

4.17 MLBFD-12000232 Cell Access Radius up to 35 km


Prerequisite Features
None

Mutually Exclusive Features


None

Impacted Features
None

4.18 MLBFD-12000233 Admission Control


Prerequisite Features
None

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 116


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 4 Related Features

Mutually Exclusive Features


None

Impacted Features
None

4.19 MLBFD-12000234 Basic Scheduling


Prerequisite Features
None

Mutually Exclusive Features


None

Impacted Features
None

4.20 MLBFD-12000235 Uplink Power Control


Prerequisite Features
None

Mutually Exclusive Features


None

Impacted Features
Feature ID Feature Name Description

MLBFD-12000234 Basic The uplink power control feature provides UE


Scheduling power headroom (PH) for uplink scheduling.
The MCS and repetition count are allocated to
the UE based on PH.

MLBFD-12000230 Random Access The random access procedure provides the


Procedure uplink power control algorithm with information
such as the preamble format and the number of
times the UE sends the preamble.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 117


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 4 Related Features

4.21 MLBFD-12000236 DRX


Prerequisite Features
None

Mutually Exclusive Features


None

Impacted Features
Function Name Description

Scheduling DRX has the following impact on scheduling:


l When the eNodeB is not transmitting SI or paging messages to
the UE, the eNodeB enables resource scheduling for only UEs
in the active state.
l In DRX mode, the UE sends a random access request when
there is data in the UE buffer, regardless of whether the UE is
in the active state. Even if the UE is in the sleep state, it
immediately switches to the active state and begins to monitor
the NPDCCH. When the UE receives the data initially sent on
the NPDCCH, the eNodeB starts the DRX Inactivity Timer to
increase the active time until the UE obtains resources.

4.22 MLBFD-12000237 Cell Selection and Re-selection


Prerequisite Features
Feature ID Feature Name Description

MLBFD-12000229 Broadcast of system The cell selection and reselection


information information is broadcast in system
messages.

Mutually Exclusive Features


None

Impacted Features
None

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 118


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 4 Related Features

4.23 MLBFD-12000238 UL 2-Antenna Receive Diversity


Prerequisite Features
None

Mutually Exclusive Features


None

Impacted Features
None

4.24 MLBFD-12100240 DL 4-Antenna Transmit Diversity


Prerequisite Features
None

Mutually Exclusive Features


Function Name Description

Channel calibration 4T4R cells do not support channel calibration, regardless of


whether they are served by an integrated RRU or combined
RRUs.

Impacted Features
Feature ID Feature Description
Name

LEOFD-111305 Virtual 4T4R In LTE in-band deployment, no virtual 4T4R signal


conversion is performed in NB-IoT cells. Therefore,
when DL 4-Antenna Transmit Diversity is enabled
with Virtual 4T4R, the downlink initial block error
rate (IBLER) increases, downlink SINR decreases,
and the cell downlink throughput decreases.

4.25 MLBFD-12100243 Congestion Control


Prerequisite Features
None

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 119


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 4 Related Features

Mutually Exclusive Features


None

Impacted Features
None

4.26 MLOFD-120220 Idle Mode eDRX


Prerequisite Features
Feature ID Feature Name Description

MLBFD-12000305 Synchronization The eNodeB must support time or


frequency synchronization.

MLBFD-12000229 Broadcast of system The eNodeB needs to broadcast the HSFN.


information

MLBFD-12000231 Paging Paging messages must be sent within the


PTW.

Mutually Exclusive Features


None

Impacted Features
None

4.27 MLOFD-120201 NB-IoT Coverage Extension


Prerequisite Features
Feature ID Feature Name Description

MLBFD-12000234 Basic Scheduling The number of repetitions used to


achieve coverage extension is
controlled in scheduling.

Mutually Exclusive Features


None

Impacted Features
None

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 120


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 4 Related Features

4.28 MLOFD-120230 Multi-tone


Prerequisite Features
Feature ID Feature Name Description

MLBFD-12000234 Basic Scheduling Multi-tone transmission is dependent


on uplink scheduling.

Mutually Exclusive Features


None

Impacted Features
None

4.29 MLOFD-121202 UL 4-Antenna Receive Diversity


Prerequisite Features
None

Mutually Exclusive Features


Function Name Description

Channel calibration 4T4R cells do not support channel calibration, regardless of


whether they are served by an integrated RRU or combined
RRUs.

Impacted Features
None

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 121


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 5 Network Impact

5 Network Impact

This chapter describes the impact of NB-IoT features on network capacity and performance.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 122


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 5 Network Impact

5.1 MLBFD-12000101 Standalone Deployment


System Capacity
None

Network Performance
None

5.2 MLBFD-12000102 LTE Guardband Deployment


System Capacity
None

Network Performance
In LTE guard band deployment, if the NB-IoT cell shares the same RF modules with the LTE
FDD cell, the power allocation for LTE FDD and NB-IoT cells changes because the PSD of
NB-IoT is high. Specifically, after the NB-IoT cell is activated, the average throughput and
average MCS index may decrease for UEs at the center of the LTE FDD cell, and the residual
block error rate (RBLER) may increase. If DL 256QAM is enabled, the peak throughput of
UEs using the 256QAM modulation scheme at the center of the LTE FDD cell is 1.5 times
that of UEs using the 64QAM modulation scheme at the center of the LTE FDD cell.

5.3 MLBFD-12000103 LTE In-band Deployment


System Capacity
If a resource conflict between the NPUSCH and LTE FDD SRS in LTE in-band deployment is
avoided by setting the PRB.UlAllSymbolSendFlag parameter to FALSE(FALSE), the single-
RU bit rate is increased for NB-IoT. However, the MCS index may be lowered and the uplink
capacity of NB-IoT may be decreased by 8% to 20%.

NB-IoT deployment on LTE FDD in-band RBs reduces the RBs available to an LTE FDD cell
because RBs need to be reserved for NB-IoT deployment and for guard bandwidth.
l If NB-IoT uplink and downlink are deployed on RBs recommended in 3.2.3 LTE In-
band Deployment, the theoretical LTE FDD RBs and single-UE peak data rate are
decreased, as described in Table 5-1.
l If NB-IoT uplink and downlink are not deployed on recommended RBs, fragmented RBs
exist, and consequently more RBs may be affected in an LTE FDD cell. This is because
the protocol-defined uplink and downlink RB allocation principles (allocation of
continuous uplink carrier resources, uplink 2/3/5 allocation principles, symmetrical
PUCCH resource allocation, and downlink RBG allocation principles) do not support the
allocation of some fragmented RBs. For details on LTE FDD uplink and downlink RB
allocation, see Scheduling Feature Parameter Description.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 123


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 5 Network Impact

l If NB-IoT uplink is not deployed on an edge RB, LTE FDD cell uplink RB resources
become discontinuous, and consequently the single-UE peak throughput decreases (the
single UE scheduling requirements for the PUSCH stipulated in 3GPP TS 36.211 are
met). The throughput decrease is related to the position of the RB reserved for NB-IoT
uplink deployment. The minimum single-UE peak throughput decrease equals the
proportion of the RBs reserved to the total cell bandwidth. The maximum single-UE
peak throughput decrease can reach 50%.

Table 5-1 Decreases in theoretical LTE FDD RBs and single-UE peak data rate each
time an RB is reserved
System Theoretical Downlink Theoretical Uplink Single-
Bandwidt Downlink Single-UE Uplink RB UE Peak Data
h RB Loss Peak Data Loss Rate Loss
Rate Loss

5 MHz 4% 8% to 14.5% 4% 1% to 4.5%

10 MHz 2% 6% to 10.5% 2% 3.5% to 7%

15 MHz 1.3% 5% to 7.5% 1.3% 3% to 12.5%

20 MHz 1% 4% to 7.5% 1% 3.5% to 7%

If there are multiple online UEs in an LTE FDD cell, the average uplink and downlink
experienced rates are affected each time an RB is reserved. Table 5-2 describes the detailed
impact.

Table 5-2 Impact on average uplink and downlink experienced rates each time an RB is
reserved
System Bandwidth Average UE Experienced Rate Loss

5 MHz 10% to 25%

10 MHz 8% to 20%

15 MHz 5% to 15%

20 MHz 3% to 10%

Table 5-1 and Table 5-2 describe the impact of RB reservation on LTE FDD cell capacity and
average uplink and downlink experienced rates in a typical scenario, that is, in a scenario
where the following conditions are met:
l The inter-site distance is 500 meters.
l Each cell has 10 online UEs.
l The network load is about 20%.
l The ratio of large-sized packets to small-sized packets is 1:4.
In any of the following scenarios, the impact on LTE FDD cell capacity and average uplink
and downlink experienced rates is greater than that described in the tables above:

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 124


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 5 Network Impact

l When the CellPdcchAlgo.PdcchSymNumSwitch parameter is set to ON or


ECFIADAPTIONON, the control format indicator (CFI) increases and the downlink
throughput is further decreased because of fragmented allocable resources and increased
average number of UEs scheduled at a time. The specific throughput decrease is related
to the increase in the average CFI, and can reach up to 15%.
l Due to fragmented allocable resources, the number of scheduling times increases for
each UE and the scheduling delay excluding that of the last TTI increases. If the network
load is not heavy and the total traffic remains unchanged, the average uplink and
downlink experienced rates decrease. The rate decrease is about one to four times the
ratio of RBs reserved to the total number of RBs in the cell.
l The network impact is also related to the network load and service model in multi-user
scenarios. Generally, a lighter network load, a larger proportion of small-sized packets,
or fewer online UEs indicate greater impact on LTE FDD cell capacity and average
uplink and downlink experienced rates.

Different configurations of scheduling parameters for LTE FDD common messages such as
system messages and RAR messages result in different proportions of common message
overhead in the downlink and different impacts on resource allocation. A shorter scheduling
period for LTE FDD system messages or PRACH resources leads to a greater downlink
common message overhead and a lower peak throughput. A smaller LTE FDD system
bandwidth results in a greater impact on the downlink peak throughput.

Network Performance
l Impact of LTE FDD on NB-IoT
In LTE in-band deployment, the RB carrying NB-IoT is interfered with by the adjacent
channel leakage of LTE FDD uplink signals. Consequently, the overall noise floor
increases, and the NB-IoT coverage shrinks. The interference is related to the uplink
signal reception strength in the LTE FDD cell, and the adjacent channel leakage ratio
(ACLR) of LTE FDD UEs.
l Impact of NB-IoT on LTE FDD
Each NB-IoT cell occupies one LTE FDD PRB, and an extra uplink PRB may be
reserved as the guard band. Consequently, all existing LTE FDD KPIs are affected. The
impact on KPIs is less than the proportion of the PRBs reserved for NB-IoT deployment
to the entire LTE FDD cell bandwidth.
The 3.75 kHz subcarrier used by the NPRACH causes interference on adjacent LTE
FDD RBs, leading to an increase in the LTE BLER. The influence depends on the uplink
signal strength and ACLR of NB-IoT UEs.
NB-IoT deployment on LTE FDD in-band RBs results in fragmented allocable resources
because RBs need to be reserved for NB-IoT deployment and for the guard band. When
there are multiple online UEs in the LTE FDD cell, the average number of UEs
scheduled at a time may increase. Consequently, the average interference level in the
LTE FDD cell and average uplink and downlink MCS indexes fluctuate, and the CCE
usage improves. The interference and MCS index fluctuation or CCU usage
improvement is related to the position of the reserved RB and locations of UEs to be
scheduled. In addition, the BLER, throughput, and MCS index may vary depending on
different scenarios. The related non-KPI indexes may also change.
In addition, in LTE in-band deployment, certain symbols of the downlink RB allocated to
NB-IoT must be reserved for LTE FDD PDCCH, and therefore, if time synchronization
is not achieved, NB-IoT creates interference on the PDCCH. When the NB-IoT network
load reaches 100%, the PDCCH receives interference signals 6 dB stronger than before,

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 125


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 5 Network Impact

and the BLER/CFI/CCE level of the PDCCH is affected. The 6 dB interference increase
in a single RB has only very little impact on the PDCCH that is included in all RBs. In
heavy load scenarios, the theoretical impact (relative value) of the interference increase
is estimated to be 10 x log (1 + (4 x Number of reserved RBs/Total number of RBs)) dB.
The impact of the interference increase on the BLER varies depending on the scenario.
Specifically, the BLER may be increased by 1% to 5%.
As NB-IoT shares the same RF modules with LTE FDD, the power allocation for LTE
FDD and NB-IoT changes because the PSD of NB-IoT is high. Specifically, after an NB-
IoT cell is deployed on the same RF module with the corresponding LTE FDD cell, the
average throughput and average MCS index may decrease for UEs at the center of the
LTE FDD cell, and the RBLER may increase. If the DL 256QAM feature is enabled, the
impact on the peak throughput of UEs using the 256QAM modulation scheme at the
center of the LTE FDD cell is 1.5 times that on the peak throughput of UEs using the
64QAM modulation scheme at the LTE FDD cell center.
When the uplink PSD of an NB-IoT cell is greater than the PSD of neighboring uplink
RBs in an LTE FDD cell, the NB-IoT cell causes interference to the neighboring RBs in
the LTE FDD cell if the NB-IoT cell load is high. The interference level depends on the
difference in the PSD.
NB-IoT generally provides a continuous coverage area. In 1:1 deployment mode, a
certain amount of transmit power for neighboring LTE FDD cells is reclaimed and
allocated to NB-IoT, which reduces interference. The impact of transmit power
reclamation on SINR/channel quality indicator (CQI)/RANK2 proportion/MCS is less
than that on RSRP.

5.4 MLBFD-12000202 Single-tone


System Capacity
None

Network Performance
None

5.5 MLBFD-12000203 Support of NB-IoT UE


System Capacity
None

Network Performance
None

5.6 MLBFD-12000204 Data over NAS


System Capacity
None

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 126


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 5 Network Impact

Network Performance
None

5.7 MLBFD-12100205 Data over User Plane (Trial)


NOTE

Before using this feature, read 1.2 Disclaimer for Trial Features.

System Capacity
None

Network Performance
None

5.8 MLBFD-12000226 Modulation: DL QPSK, UL QPSK/


BPSK
System Capacity
This feature enables eNodeBs to select an appropriate modulation scheme for UEs based on
channel conditions, which increases spectral efficiency.

Network Performance
None

5.9 MLBFD-12000227 AMC


System Capacity
This feature increases spectral efficiency.

Network Performance
None

5.10 MLBFD-12000228 RRC Connection Management


System Capacity
None

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 127


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 5 Network Impact

Network Performance
None

5.11 MLBFD-12000229 Broadcast of System Information


System Capacity
None

Network Performance
When the SI_OFFSET_ADAPTIVE_CFG_SWITCH option under the
CellAlgoSwitch.NbCellAlgoSwitch parameter is selected for a cell, the system information
frame offset of the cell is adaptively configured using different values of PCI mod 3. This
reduces the inter-cell interference caused by system information broadcast and increases the
probability of successfully demodulating system information by UEs.

5.12 MLBFD-12000223 Physical Channel Management


System Capacity
None

Network Performance
None

5.13 MLBFD-12000224 DL Asynchronous HARQ


System Capacity
This feature increases the cell downlink throughput and reduces downlink transmission delay.

Network Performance
When HARQ retransmission scheduling uses a lowered MCS or bit rate, the downlink
RBLER and service drop rate are improved but downlink throughput is decreased. When the
maximum number of downlink HARQ retransmissions retains the default value, downlink
throughput decreases slightly. The smaller the maximum number of downlink HARQ
retransmissions, the greater the downlink throughput loss.

5.14 MLBFD-12000225 UL Asynchronous HARQ


System Capacity
This feature increases the network uplink throughput and reduces the uplink transmission
delay.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 128


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 5 Network Impact

Network Performance
When HARQ retransmission scheduling uses a lowered MCS or bit rate, the uplink RBLER
and service drop rate are improved, the voice packet loss rate is decreased, but uplink
throughput is decreased. When the maximum number of uplink HARQ retransmissions
retains the default value, uplink throughput decreases slightly. The smaller the maximum
number of uplink HARQ retransmissions, the greater the uplink throughput loss.

5.15 MLBFD-12000230 Random Access Procedure


System Capacity
None

Network Performance
None

5.16 MLBFD-12000231 Paging


System Capacity
None

Network Performance
None

5.17 MLBFD-12000232 Cell Access Radius up to 35 km


System Capacity
None

Network Performance
None

5.18 MLBFD-12000233 Admission Control


System Capacity
None

Network Performance
If network congestion is reducing system capacity, the use of an admission control algorithm
decreases the access success rate.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 129


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 5 Network Impact

5.19 MLBFD-12000234 Basic Scheduling


System Capacity
Appropriately planned basic scheduling algorithm parameters (including the initial MCS,
initial repetition count, maximum HARQ transmission count, and NPDCCH period) for
NPDCCH, NPDSCH, and NPUSCH scheduling can increase uplink and downlink system
capacity.

Network Performance
Appropriately planned basic scheduling algorithm parameters can improve network
performance counters for the entire process from the initial UE access to data transmission.

5.20 MLBFD-12000235 Uplink Power Control


System Capacity
None

Network Performance
The purpose of power control for the NPRACH is to ensure the random access success rate,
minimize transmit power, reduce interference with neighboring cells, and to reduce UE power
consumption.

Power control for the NPUSCH decreases interference with neighboring cells and increases
the data rates for UEs in the local cell edge while ensuring cell throughput.

5.21 MLBFD-12000236 DRX


System Capacity
None

Network Performance
The sleep state introduced by DRX helps reduce UE power consumption but increases the
service delay. The uplink and downlink single-UE peak data rates decrease as a result.

5.22 MLBFD-12000237 Cell Selection and Re-selection


System Capacity
None

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 130


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 5 Network Impact

Network Performance
Cell selection and reselection ensure sufficient network coverage so that UEs in RRC_IDLE
mode will not become out of service when moving between cells.

5.23 MLBFD-12000238 UL 2-Antenna Receive Diversity


System Capacity
None

Network Performance
None

5.24 MLBFD-12100240 DL 4-Antenna Transmit Diversity


System Capacity
If DL 4-Antenna Transmit Diversity doubles the total transmit power for a given number of
antenna ports, DL 4-Antenna Transmit Diversity delivers 10% to 20% better average
downlink cell throughput than DL 2-Antenna Transmit Diversity. The throughput gains,
however, are affected by interference from neighboring cells.
l Strong interference from neighboring cells results in increased power in the serving cell
and neighboring cells and a nearly imperceptible increase in the signal-to-noise ratio
(SNR). Consequently, the power and capacity gains are small.
l Weak interference from neighboring cells results in a noticeable increase in the power in
the serving cell and SNR. Consequently, the power and capacity gains are large.
If the interference from neighboring cells is extremely strong, the throughput provided by DL
4-Antenna Transmit Diversity is not better than that provided by DL 2-Antenna Transmit
Diversity. However, if there is no interference from neighboring cells, DL 4-Antenna
Transmit Diversity increases the downlink throughput by up to 20%.

Network Performance
If DL 4-Antenna Transmit Diversity doubles the total transmit power for a given number of
antenna ports, DL 4-Antenna Transmit Diversity provides coverage that is 1 dB to 3 dB
stronger than DL 2-Antenna Transmit Diversity. In addition, DL 4-Antenna Transmit
Diversity occupies fewer downlink subcarriers and thereby reduces their utilization.
Other network KPIs, such as the RRC connection setup success rate and the call drop rate
remain the same after DL 4-Antenna Transmit Diversity is deployed.
In LTE in-band deployment, when channel calibration is enabled for LTE FDD combined
RRUs:
l If an NB-IoT cell is activated during the LTE FDD channel calibration, channel
calibration affects NB-IoT services. Specifically, the bit error rate (BER) increases on the
NPDCCH and NPDSCH by up to 10%.
l If no NB-IoT cell is activated during LTE FDD channel calibration, channel calibration
does not affect NB-IoT services.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 131


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 5 Network Impact

5.25 MLBFD-12100243 Congestion Control


System Capacity
When the EnodebFlowCtrlPara.DynAcBarPolicyMode parameter is set to
CPULOAD(CPULOAD) and the EnodebFlowCtrlPara.CpuLoadThd parameter is set to a
value less than 80%, the access of a large number of UEs is barred even though the CPU
resources are not fully utilized. In this case, user experience is affected and the busy hour call
attempts (BHCA) specifications may fail to be reached.

Network Performance
When the RRC connection setup success rate decreases due to the flow control implemented
on the main control board or BBP board, access control helps gradually bar UE access so as to
relieve the cell congestion. The RRC connection setup success rate increases as a result, but
the access experience is affected.
If RACH is congested, backoff is triggered to relieve the congestion and thereby improve the
RRC connection setup success rate. Backoff also reduces the number of times UEs transmit a
preamble, causing a possible increase in the call drop rate.

5.26 MLOFD-120220 Idle Mode eDRX


System Capacity
None

Network Performance
This feature prongs the UE paging cycle, which saves power.

5.27 MLOFD-120201 NB-IoT Coverage Extension


System Capacity
None

Network Performance
This feature enables the NB-IoT to have a wide coverage area, improves the access success
rate in the coverage enhancement area, and reduces the service drop rate.

5.28 MLOFD-120230 Multi-tone


System Capacity
Multi-tone transmission significantly increases the single-UE peak uplink data rate.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 132


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 5 Network Impact

Network Performance
Multi-tone transmission significantly increases the single-UE peak uplink data rate, and
reduces the transmission delay and power consumption for uplink data transmission.

5.29 MLOFD-121202 UL 4-Antenna Receive Diversity


System Capacity
UL 4-Antenna Receive Diversity provides 10% to 50% better average cell uplink throughput
than UL 2-Antenna Receive Diversity. The throughput gains, however, are affected by
interference.
l When the interference is weak, the gains in the average cell uplink throughput are large.
The gains reach the maximum when only white noise exists.
l When the interference is strong, the gains in the average cell uplink throughput are small.

Network Performance
UL 4-Antenna Receive Diversity improves the coverage by 1 dB to 3 dB due to its large
diversity gains and array gains, compared with UL 2-Antenna Receive Diversity. UL 4-
Antenna Receive Diversity also occupies fewer uplink subcarriers and thereby reduces their
utilization.
However, UL 4-Antenna Receive Diversity also increases the scope where call drops may
occur and increases interference for cell edge users (CEUs). This increase can be avoided by
preventing overshoot coverage during network planning.
Other network KPIs, such as the RRC connection setup success rate and the call drop rate are
not affected by UL 4-Antenna Receive Diversity.
In LTE in-band deployment, when channel calibration is enabled for LTE FDD combined
RRUs:
l If an NB-IoT cell is activated during the LTE FDD channel calibration, channel
calibration affects NB-IoT services. Specifically, the BER increases on the NPDCCH
and NPDSCH by up to 10%.
l If no NB-IoT cell is activated during LTE FDD channel calibration, channel calibration
does not affect NB-IoT services.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 133


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

6 Engineering Guidelines for NB-IoT Basic


Features

6.1 When to Use


MLBFD-120001 NB-IoT Network Deployment is a basic feature. NB-IoT networks must be
deployed in at least one of the following modes:

l Standalone
l LTE guard band
l LTE in-band

MLBFD-120002 3GPP NB-IoT Specifications Compliant is a basic feature. It is enabled by


default to support network access of NB-IoT UEs.

6.2 Required Information


Before you deploy NB-IoT, collect information about frequency bands, cell radius, and RF
power. The cell radius is necessary for proper network planning and RF power data is needed
for proper RF power planning.

Collect the information about protocols supported by NB-IoT UEs on the live network. The
collected protocol information is used to plan the settings of 3GPP incompatibility switches.
For details, see 6.4.2 Precautions.

If neighboring cells need to be configured, collect the following information about the intra-
frequency neighboring cells, inter-frequency EARFCNs, and inter-frequency neighboring
cells:

l Mobile network codes (MNCs)


l Mobile country codes (MCCs)
l Base station identifications (BS IDs)
l Cell identities (CIs)
l Frequencies

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 134


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

6.3 Planning

6.3.1 RF Planning
If NB-IoT shares RF units with other modes, the current power usage of RF must be taken
into consideration for RF planning.
l If RF units have power headroom, NB-IoT can be deployed directly.
l In refarming deployment scenarios where some GSM spectrums are allocated to NB-IoT,
NB-IoT can be deployed directly.
l If RF units do not have any power headroom, power back-off must be performed for NB-
IoT deployment. The power back-off does not have much impact on the coverage of the
existing network.
In LTE in-band scenarios, an NB-IoT cell and its corresponding LTE FDD cell share the same
RF channel power and the following requirements must be met:
1. The total power of an NB-IoT cell and its corresponding LTE FDD cell cannot exceed
the upper power threshold of the RF channel. For details about the power specifications
of RF modules, see 3900 Series Base Station Technical Description.
2. The PSD of an NB-IoT cell must be no more than 6 dB higher than that of an LTE FDD
cell.

6.3.2 Network Planning


The NB-IoT networking is determined based on the coverage aims, guard band requirements,
and live network conditions.
1:1 deployment is preferred in network planning because it ensures intensive coverage and
does not require a large guard band or adjustment of RF planning in the existing network. 1:1
deployment is recommended for scenarios with a long inter-site distance, large downtilt angle,
and a narrow guard band.
Other deployment ratios require a larger guard band and affect intensive coverage. Therefore,
a maximum of 1:4 deployment is recommended. The following figure shows an example of
1:3 deployment.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 135


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Figure 6-1 1:3 deployment diagram

The 1:N (N > 1) deployment is not supported in LTE in-band deployment. This is because
downlink signals in NB-IoT cells are severely interfered with due to the near-far effect when
the 1:N deployment is used, and NB-IoT UEs cannot normally process services. In addition,
the severe interference from LTE FDD to NB-IoT cannot be avoided by reserving extra RBs
as LTE FDD PDCCH signals and pilot signals are transmitted on all RBs.

6.3.3 Hardware Planning


N/A

6.4 Deployment

6.4.1 Requirements

Other Features
For details, see 4 Related Features.

Hardware
l The main control board must be an LMPT or UMPT.
l The baseband board must be an LBBPd1/LBBPd2/LBBPd3/LBBPd5, a UBBPd3/
UBBPd4/UBBPd5/UBBPd6, or a UBBPe1/UBBPe2/UBBPe3/UBBPe4.
l The RF modules supporting NB-IoT are described in 3900 Series Base Station Technical
Description of 3900 Series Base Station Product Documentation.
l LTE in-band deployment requires that NB-IoT cells share main control boards, RF
modules, and antenna systems with LTE FDD cells.
l NB-IoT does not support separate-MPT with LTE FDD.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 136


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

l NB-IoT does not support inter-BBU baseband interconnection.


l In CPRI networking, NB-IoT does not support inter-RAT cascading or cascading CPRI
ports of different rates. For details about CPRI networking, see CPRI MUX Feature
Parameter Description.
l The NB-IoT requirements for CPRI 1T1R I/Q data bandwidth are listed in the following
table.
Deployment Mode 1T1R I/Q Data Bandwidth

Standalone 115.2 Mbit/s

LTE guardband 115.2 Mbit/s

LTE in-band 92.16 Mbit/s

License
To establish an NB-IoT cell, you need to apply for a capacity license. For details, see License
Control Item Lists (CIoT). Purchase hardware and board licenses as required.

Others
l UEs must support the NB-IoT functions stipulated in 3GPP specifications (Release 13).
l The EPC must support the control plane CIoT EPS optimization function stipulated in
3GPP specifications (Release 13) when this function is implemented between the
eNodeB and EPC.
l The EPC must support the user plane CIoT EPS optimization function stipulated in
3GPP specifications (Release 13) when this function is implemented between the
eNodeB and EPC.
l If NB-IoT and LTE FDD/TDD share the same RF module or baseband board, NB-IoT
must meet the following requirements:
The value of the ENodeBFrameOffset.FddFrameOffset parameter must be the
same as that of the corresponding eNodeB-level parameter of LTE FDD/TDD.
The value of the CellFrameOffset.FrameOffset parameter must be the same as that
of the corresponding cell-level parameter of LTE FDD/TDD.

6.4.2 Precautions
If some NB-IoT UEs in a cell comply with 3GPP TS 36.213 V13.3.0 (2016-09), select
DCI_SF_REP_NUM_COMP_SWITCH under the CellAlgoSwitch.NbCellAlgoSwitch
parameter. If this switch is not selected, these UEs cannot access NB-IoT networks.
When this switch is selected, the NB-IoT UEs that do not comply with 3GPP TS 36.213
V13.3.0 (2016-09) must be upgraded. If they are not upgraded, these NB-IoT UEs cannot
access NB-IoT networks.
The 3GPP Release 13 (2017-03) changed the compatibility policy for NB-IoT UEs.
NbR13CompatSw is introduced to the GlobalProcSwitch.UeCompatSwitch parameter to
determine whether to adopt the new compatibility policy.
l When some NB-IoT UEs in a cell comply with 3GPP Release 13 (2017-03),
NbR13CompatSw must be selected. Otherwise, these NB-IoT UEs cannot access NB-
IoT networks.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 137


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

l When this option is selected, the NB-IoT UEs that do not comply with 3GPP Release 13
(2017-03) must be upgraded. If they are not upgraded, these NB-IoT UEs cannot access
NB-IoT networks.

6.4.3 Hardware Adjustment


None

6.4.4 Data Preparation and Activation

6.4.4.1 Data Preparation

Required Data
The following table describes the parameters that must be set in a SECTOR MO to configure
a sector.

Parameter Name Parameter ID Setting Notes

Sector ID SECTORID Ensure that each sector ID is


unique.

Sector Name SECNAME N/A

Location Name LOCATIONNAME N/A

User Label USERLABEL N/A

Antenna Number ANTNUM N/A

Cabinet No. of Antenna ANT1CN N/A


1

Subrack No. of Antenna ANT1SRN N/A


1

Slot No. of Antenna 1 ANT1SN N/A

Channel No. of Antenna ANT1N N/A


1

Cabinet No. of Antenna ANT2CN N/A


2

Subrack No. of Antenna ANT2SRN N/A


2

Slot No. of Antenna 2 ANT2SN N/A

Channel No. of Antenna ANT2N N/A


2

Create Default Sector CREATESECTOREQM N/A


Equipment

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 138


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

Default Sector SECTOREQMID N/A


Equipment ID

The following table describes the parameters that must be set in a SECTOREQM MO to
configure a piece of sector equipment.

Parameter Name Parameter ID Setting Notes

Sector Equipment ID sectorEqmId N/A

Sector ID sectorId N/A

Antenna Number ANTNUM N/A

Cabinet No. of Antenna ANT1CN N/A


1

Subrack No. of Antenna ANT1SRN N/A


1

Slot No. of Antenna 1 ANT1SN N/A

Channel No. of Antenna ANT1N N/A


1

Antenna 1 RX/TX Mode ANTTYPE1 N/A

TX Antenna 1 Master/ TXBKPMODE1 Set this parameter to


Slave Mode MASTER(Master).
Do not set this parameter to
SLAVE(Slave) because the
eNodeB does not support
the configuration of master
and slave antennas.

Cabinet No. of Antenna ANT2CN N/A


2

Subrack No. of Antenna ANT2SRN N/A


2

Slot No. of Antenna 2 ANT2SN N/A

Channel No. of Antenna ANT2N N/A


2

Antenna 2 RX/TX Mode ANTTYPE2 N/A

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 139


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

TX Antenna 2 Master/ TXBKPMODE2 Set this parameter to


Slave Mode MASTER(Master).
Do not set this parameter to
SLAVE(Slave) because the
eNodeB does not support
the configuration of master
and slave antennas.

The following table describes the parameters that must be set in a BASEBANDEQM MO to
configure baseband equipment information.

Parameter Name Parameter ID Setting Notes

Baseband BASEBANDEQMID Each baseband equipment ID identifies a


Equipment ID piece of baseband equipment.
One piece of baseband equipment can
include multiple BBPs. For example, in the
MML command ADD
BASEBANDEQM:BASEBANDEQMID
=0,BASEBANDEQMTYPE=ULDL,UM
TSDEMMODE=NULL,SN1=2,SN2=1;,
SN1 and SN2 represent the slot numbers of
two BBPs, indicating that the baseband
equipment with ID 0 includes two BBPs.
However, it is recommended that one piece
of baseband equipment includes only one
BBP.
A BBP cannot belong to multiple pieces of
baseband equipment.

Baseband BASEBANDEQMTY N/A


Equipment Type PE

The following table describes the parameters that must be set in a CnOperator MO to
configure an operator.

Parameter Name Parameter ID Setting Notes

CN Operator ID CnOperatorId N/A

CN Operator name CnOperatorName N/A

CN Operator type CnOperatorType You can set only one primary


operator and a maximum of three
secondary operators for an eNodeB.

Mobile country code Mcc N/A

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 140


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

Mobile network code Mnc N/A

The following table describes the parameters that must be set in a CnOperatorTa MO to
configure a tracking area for an operator.

Parameter Name Parameter ID Setting Notes

Local tracking area ID TrackingAreaId N/A

CN Operator ID CnOperatorId N/A

Tracking area code Tac N/A

NB-IoT TA Flag NbIotTaFlag In accordance with section 5.3.3 of


3GPP TS 23.401 V13.7.0, NB-IoT
does not support inter-RAT
mobility, and therefore the TAI
configured for the NB-IoT must
differ from those configured for
LTE FDD and LTE TDD.

The following table describes the parameters that must be set in an MmeCapInfo MO to
configure the MME capability information for NB-IoT.

Parameter Name Parameter ID Setting Notes

MME Capability MmeCapCfgId N/A


Configuration ID

S1 Configuration Type S1CfgType N/A

S1 ID S1Id N/A

S1 Interface ID S1InterfaceId N/A

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 141


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

NB-IoT CIoT EPS NbCiotEpsOptCap If the MME does not support


Optimization Capability control plane CIoT EPS
optimization for NB-IoT CIoT, set
this parameter to
NOT_SUPPORT(NOT_SUPPOR
T). NB-IoT services are not
connected to the MME by the
eNodeB.
If the MME supports control plane
CIoT EPS optimization, set this
parameter to CP(CP). Before
setting this parameter to CP(CP),
ensure that at least one TAI for NB-
IoT is configured on the S1
interface between an eNodeB and
the MME.
When the MME supports both the
control plane and user plane CIoT
EPS optimization functions, set this
parameter to CP_UP(CP_UP).
Before setting this parameter to
CP_UP(CP_UP), ensure that at
least one TAI for NB-IoT is
configured on the S1 interface
between an eNodeB and the MME.

MME Support LTE NbLteSupportCap If the MME supports LTE FDD and
Capability LTE TDD, set this parameter to
SUPPORT(SUPPORT).

When user plane CIoT EPS optimization is enabled, parameters in the RlcPdcpParaGroup
MO must be set.

Parameter Name Parameter ID Setting Notes

RLC PDCP parameter RlcPdcpParaGroupId N/A


group ID

Category Type CatType Set this parameter to NBIOT(NB-


IoT).

NB-IoT PDCP Discard NbPdcpDiscardTimer Set this parameter to its default


Timer value.

NB-IoT Downlink NbDlPdcpDiscardTimer Set this parameter to its default


PDCP Discard Timer value.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 142


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

RLC-UM or RLC-AM RlcMode Set this parameter to


mode RlcMode_AM(Acknowledge
Mode).

MaxretxThreshold for UeMaxRetxThreshold Set this parameter to its default


UE value.

MaxRetxThreshold for ENodeBMaxRetxThres- Set this parameter to its default


eNodeB hold value.

NB-IoT Poll Retransmit NbUePollRetxTimer Set this parameter to its default


Timer for UE value.

NB-IoT Poll Retransmit NbEnodebPollRetxTim- Set this parameter to its default


Timer for eNodeB er value.

Discardtimer Separate UlDlDiscardtimerSwitch You are advised to set this


Config Switch parameter to OFF(Off).

When user plane CIoT EPS optimization is enabled, parameters in the QciPara MO must be
set.

Parameter Name Parameter ID Setting Notes

QoS Class Identifier Qci NB-IoT supports only the non-


guaranteed bit rate (Non-GBR)
services with the QoS class
identifier (QCI) ranging from 5 to
9.

NB-IoT RLC PDCP NbRlcPdcpParaGroupId N/A


Para Group ID

The following table describes the parameters that must be set in a Cell MO to configure a cell.

Parameter Name Parameter ID Setting Notes

Local Cell ID LocalCellId N/A

Cell Name CellName N/A

NB-IoT Cell Flag NbCellFlag Set this parameter to a fixed value


TRUE(TRUE) for NB-IoT cells.

Coverage Level Type CoverageLevelType N/A

Uplink cyclic prefix UlCyclicPrefix Set the parameters to a fixed value


length NORMAL_CP(Normal).

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 143


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

Downlink cyclic prefix DlCyclicPrefix Set the parameters to a fixed value


length NORMAL_CP(Normal).

Cell ID CellId N/A

Physical cell ID PhyCellId Set this parameter to the same value


as that of the corresponding LTE
FDD cell in LTE in-band
deployment.

Cell FDD TDD FddTddInd Set this parameter to a fixed value


indication CELL_FDD(FDD).

Flag of Multi-RRU Cell MultiRruCellFlag Set this parameter to its


recommended value.

Mode of Multi-RRU MultiRruCellMode This parameter needs to be


Cell configured only when
Cell.MultiRruCellFlag is set to
BOOLEAN_TRUE(True), and
this parameter must be set to
SFN(SFN) in this condition.

CRS Port Number CrsPortNum Set this parameter based on the


number of downlink channels. For
example, set this parameter to
CRS_PORT_2(2 ports) in 2T
mode and to CRS_PORT_1(1
port) in 1T1R mode.
This parameter cannot be set to
CRS_PORT_1(1 port) for a 2T2R,
2T4R, or 4T4R NB-IoT cell.
In LTE in-band deployment, if the
Cell.CrsPortNum and
Cell.TxRxMode parameters for the
corresponding LTE FDD cell are set
to CRS_PORT_4(4 ports) and
4T4R, these parameters for the NB-
IoT cell must be set to
CRS_PORT_2(2 ports) and
4T4R; if these parameters for the
corresponding LTE FDD cell are set
to other values, these parameters
for the NB-IoT cell must be set to
the same values as those for the
LTE FDD cell.

Cell transmission and TxRxMode Set this parameter to the same value
reception mode as the number of antennas in the
sector where the cell is located.

User label UserLabel N/A

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 144


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

Work mode WorkMode Set this parameter to its


recommended value.

The following table describes the parameters that must be set in a Prb MO to configure
physical resource blocks (PRBs).

Parameter Name Parameter ID Setting Notes

Local Cell ID LocalCellId N/A

PRB ID PrbId N/A

Deploy Mode DeployMode Set this parameter as required.

LTE Bandwidth LteBandWidth Set this parameter only in LTE


guardband scenarios. Set this
parameter to the same bandwidth as
that of the corresponding LTE FDD
cell in LTE guardband deployment
mode.

LTE Downlink LteDlEarfcn Set this parameter only in LTE


EARFCN guardband scenarios. Set this
parameter to the same value as the
downlink EARFCN of an LTE FDD
cell in LTE guardband deployment
mode.

LTE Cell ID LteCellId Set this parameter only in LTE in-


band deployment mode. Set this
parameter to the same value as the
local cell ID of the corresponding LTE
FDD cell in LTE in-band deployment
mode.

Frequency Band FreqBand Set this parameter to the same value


as that of the Cell.FreqBand
parameter for the corresponding LTE
FDD cell in LTE in-band deployment.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 145


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

Downlink EARFCN DlEarfcn The downlink EARFCN must be


located in the frequency band
specified by the Frequency Band
parameter.
In LTE guardband deployment, the
value of this parameter must be within
the LTE FDD guardband.
In LTE in-band deployment, the value
of this parameter is calculated based
on the RBs reserved in LTE FDD cells
for NB-IoT deployment.

Downlink Frequency DlFreqOffset In standalone deployment, this


Offset parameter must be set to
NEG_0DOT5(NEG_0DOT5).
In LTE guardband deployment, this
parameter must be set to a value other
than NEG_0DOT5(NEG_0DOT5).
In LTE in-band deployment, this
parameter can be set as follows:
l When the corresponding LTE FDD
cell uses a 5 MHz or 15 MHz
bandwidth, this parameter must be
set to NEG_2(NEG_2) if the RB
used for NB-IoT deployment is
located on the first half of the LTE
FDD cell bandwidth, and must be
set to POS_1(POS_1) if the RB
used for NB-IoT deployment is
located on the last half of the LTE
FDD cell bandwidth.
l When the corresponding LTE FDD
cell uses a 10 MHz or 20 MHz
bandwidth, this parameter must be
set to POS_0(POS_0) if the RB
used for NB-IoT deployment is
located on the first half of the LTE
FDD cell bandwidth, and must be
set to NEG_1(NEG_1) if the RB
used for NB-IoT deployment is
located on the last half of the LTE
FDD cell bandwidth.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 146


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

Uplink EARFCN UlEarfcnCfgInd In standalone and LTE guardband


Configuration deployment, it is recommended that
Indication this parameter be set to
NOT_CFG(NOT_CFG).
For LTE in-band scenarios, it is
recommended that this parameter be
set to CFG(CFG).

Uplink EARFCN UlEarfcn Configure this parameter only when


the Uplink EARFCN Configuration
Indication parameter is set to
CFG(Configure). The value of this
parameter must be located in the
frequency band specified by the
Frequency Band parameter.
In LTE in-band deployment, the value
of this parameter is calculated based
on the RBs reserved in LTE FDD cells
for NB-IoT deployment.

Uplink Frequency UlFreqOffset Configure this parameter only when


Offset the Uplink EARFCN Configuration
Indication parameter is set to
CFG(Configure).
In standalone deployment mode, set
this parameter to POS_0(POS_0).
In LTE in-band deployment, the value
of this parameter is calculated based
on the RBs reserved in LTE FDD cells
for NB-IoT deployment.

Uplink All Symbol UlAllSymbolSendFlag This parameter is not configured in


Send Flag standalone and LTE guardband
deployment modes. In LTE in-band
deployment mode, when the LTE
FDD cells are configured with SRSs
and the SRSs may be transmitted on
RBs dedicated to NB-IoT, it is
recommended that this parameter be
set to FALSE(FALSE). Otherwise,
set this parameter to TRUE(TRUE).

The following table describes the parameters that must be set in an eUCellSectorEqm MO to
configure a piece of sector equipment for a cell.

Parameter Name Parameter ID Setting Notes

Local cell ID LocalCellId N/A

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 147


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

Sector equipment ID SectorEqmId N/A

Reference signal power ReferenceSignalPwr Set this parameter to the invalid value
32767 in non-SFN scenarios, where
cells use the reference signal power
specified in the PDSCHCfg MO.

Baseband equipment BaseBandEqmId If this parameter is set to 255, no


ID baseband equipment is specified for
the cell. In this case, the cell can use
any baseband equipment of the
eNodeB.
When NB-IoT is deployed in two
different modes including the LTE in-
band mode, the NB-IoT cell deployed
in LTE in-band mode must share the
same baseband equipment with the
corresponding LTE FDD cell.

Sector CPRI SectorCpriCompres- In this version, set this parameter to a


Compression sion fixed value NULL(Invalid),
indicating that the CPRI compression
type of carriers depends on the value
of the CRPI Compression parameter
in a Cell MO.

Auto Config Flag AutoCfgFlag N/A

The following table describes the parameters that must be set in a CellOp MO to configure a
cell operator.

Parameter Name Parameter ID Setting Notes

Local cell ID LocalCellId N/A

Local tracking area ID TrackingAreaId N/A

Cell reserved for CellReservedForOp Set this parameter to its


operator recommended value.

The following table describes parameters that must be set in a PDSCHCfg MO to set the
narrowband referential signal (NRS) power.

Parameter Name Parameter ID Setting Notes

Local cell ID LocalCellId N/A

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 148


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

Reference signal ReferenceSignalPwr Set this parameter based on the


power network plan during eNodeB
deployment.

The following table describes the parameters that must be set in a RACHCfg MO to
configure the random access channel (RACH) power.

Parameter Name Parameter ID Setting Notes

Local cell ID LocalCellId N/A

Preamble initial PreambInitRcvTar- Set this parameter to


received target power getPwr DBM_112(-112dBm).

NB-IoT Cyclic Prefix NbCyclicPrefixLength Set this parameter to its


Length recommended value.

NB-IoT RSRP First NbRsrpFirstThreshold Set this parameter to its


Threshold recommended value.

NB-IoT RSRP Second NbRsrpSecondThres- Set this parameter to its


Threshold hold recommended value.

PRACH Start Time PrachStartTimeCfgInd Set this parameter to its


Config Indication recommended value. When a
different PRACH start time needs to
be configured for each coverage
level, set this parameter to
CFG(Configure). For details, see
3.5.1.3 NPRACH Resource
Configuration.

The following table describes the parameters that must be set in a CellRachCECfg MO
configure the cell-level physical random access channel (PRACH) that differs according to
coverage levels.

Parameter Name Parameter ID Setting Notes

Local Cell ID LocalCellId N/A

Coverage Level CoverageLevel N/A

Contention Resolution ContentionResolution- Set this parameter to its


Timer Timer recommended value.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 149


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

PRACH Start Time PrachStartTime Set this parameter to its


recommended value. If the value of
this parameter needs to be modified,
modify it by referring to 3.5.1.3
NPRACH Resource Configuration.
WARNING
If the modified value does not meet the
NPRACH resource configuration
requirements, NB-IoT cell activation
fails.

PRACH Transmission PrachTransmissionPer- In this version, the different coverage


Period iod levels of a cell must be configured
with the same PRACH transmission
period. For details, see 3.5.1.3
NPRACH Resource Configuration.

PRACH Subcarrier PrachSubcarrierOffset In this version, the different coverage


Offset levels of a cell must be configured
with the same PRACH subcarrier
offset. To avoid the impact of
PRACH and UCI resource
overlapping on cell access
performance, this parameter cannot
be set to SC0(SC0) or SC2(SC2) in
the current version.

PRACH Repetition PrachRepetitionCount If this parameter is incorrectly set,


Count the PRACH resources for different
coverage levels overlap or the
random access RNTIs (RA-RNTIs)
for different coverage levels are the
same. As a result, the corresponding
cell cannot be activated. For details,
see 3.5.1.3 NPRACH Resource
Configuration.

PRACH Detection PrachDetectionThld Set this parameter to its


Threshold recommended value.

Maximum Number of MaxNumPreambleAt- Set this parameter to its


Preamble Attempt tempt recommended value.

The following table describes the parameters that must be set in a PCCHCfg MO to configure
air interface paging.

Parameter Name Parameter ID Setting Notes

Local cell ID LocalCellId N/A

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 150


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

NB-IoT Default DefaultPagingCycle- Set this parameter to its default


Paging Cycle ForNb value.
This parameter must work together
with the PCCHCFG.NbForNbIoT
parameter. The product of the
configured values of these two
parameters must be greater than or
equal to 1. Otherwise, UEs may fail
to receive paging messages.

NB-IoT nB NbForNbIoT This parameter must work together


with the
PCCHCFG.DefaultPagingCycle-
ForNb parameter. The product of the
configured values of these two
parameters must be greater than or
equal to 1. Otherwise, UEs may fail
to receive paging messages.
In addition, the value of this
parameter is related to the maximum
repeated times of NPDCCH. A large
number of NPDCCH repeated times
indicates a small number of paging
groups. This parameter can be set to
its maximum value FOUR_T only
when the maximum repeated times
of NPDCCH are 1.

Paging Message PagingStrategy Set this parameter to its


Sending Strategy recommended value.

Maximum Number of MaxNumRepetitionFor- Set this parameter to its


Paging Repetition Paging recommended value.

The following table describes the parameters that must be set in a GlobalProcSwitch MO to
configure the S1 default paging DRX value and UE compatibility switch.

Parameter Name Parameter ID Setting Notes

S1 Default Paging S1DefaultPagingDrx- The value of this parameter cannot


DRX Value for NB- ForNb be smaller than the value of
IoT PCCHCfg.DefaultPagingCycle-
ForNb for any NB-IoT cell under the
same eNodeB. Otherwise, the
probability of paging failures will
increase.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 151


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

Ue Compatibility UeCompatSwitch When some NB-IoT UEs in a cell


Switch comply with 3GPP Release 13
(2017-03), select NbR13CompatSw
under this parameter.
For details, see 6.4.2 Precautions.

The following table describes the parameters that must be set in an RrcConnStateTimer MO
to configure the eNodeB timer information.

Parameter Name Parameter ID Setting Notes

NB-IoT Ue inactive NbUeInactiveTimer When the number of online users


timer especially users under the coverage
level 2 is large, the channel
resources are insufficient and cannot
be scheduled timely. In this case, the
inactive timer may expire. It is
recommended that this parameter be
set to a large value in this scenario.

RRC Connection RrcConnRelTimer Set this parameter to its default


Release Timer value.

Filter Repeated FilterReptRrcConnReq- Set this parameter to its default


RRCConnReq Timer Timer value.

The following table describes the parameters that must be set in an ENodeBConnStateTimer
MO to configure the eNodeB timer information. These parameters are shared by LTE FDD.

Parameter Name Parameter ID Setting Notes

S1 Message Waiting S1MessageWaitingTimer Set this parameter to its default


Timer value.

Uu Message Waiting UuMessageWaitingTimer Set this parameter to its default


Timer value.

The following table describes the parameters that must be set in a CellPdcchCECfg MO to
configure the PDCCH resource allocation for NB-IoT cells with different coverage levels.

Parameter Name Parameter ID Setting Notes

Local Cell ID LocalCellId N/A

Coverage Level CoverageLevel N/A

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 152


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

PDCCH Maximum PdcchMaxRepetitionCnt Set this parameter to its


Repetition Count recommended value.

PDCCH Period Factor PdcchPeriodFactor Set this parameter to its


recommended value.

PDCCH Initial Trans PdcchTransRptCntFactor Set this parameter to its


Rept Count Factor recommended value.

NOTE

l PDCCH period for a given coverage level = CellPdcchCECfg.PdcchPeriodFactor x


CellPdcchCECfg.PdcchMaxRepetitionCnt
l In this version, the window length for receiving the RAR message is five PDCCH periods. If the
PDCCH period is set to too small a value, the UE will not receive the RAR message within the
specified window, and be unable to access the network.

The following table describes the parameters that must be set in an NbCellUlSchCEAlgo MO
to configure uplink scheduling parameters for a coverage level. The coverage level-related
parameters in this MO are valid only when MLOFD-120201 NB-IoT Coverage Extension is
activated.

Parameter Name Parameter ID Setting Notes

Local Cell ID LocalCellId N/A

Coverage Level CoverageLevel N/A

Uplink Initial MCS UlInitialMcs Set this parameter to its


recommended value.

UL Initial UlInitialTransRptCount Set this parameter to its


Transmission recommended value.
Repetition Count

ACK/NACK AckNackTransRptCount Set this parameter to its


Transmission recommended value.
Repetition Count

Msg4 ACK/NACK AckNackTransRpt- Set this parameter to its


Trans Repetition CountMsg4 recommended value.
Count

The following table describes the parameters that must be set in an NbCellDlSchCEAlgo MO
to configure downlink scheduling parameters for a coverage level. The coverage level-related
parameters in this MO are valid only when MLOFD-120201 NB-IoT Coverage Extension is
activated.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 153


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

Local Cell ID LocalCellId N/A

Coverage Level CoverageLevel N/A

Downlink Initial DlInitialMcs Set this parameter to its


MCS recommended value.

DL Initial DlInitialTransRptCount Set this parameter to its


Transmission recommended value.
Repetition Count

Uu Message Waiting UuMessageWaitingTimer Set this parameter to its


Timer recommended value.

The following table describes the parameters that must be set in a CellUlpcComm MO to
configure cell uplink power control information.

Parameter Name Parameter ID Setting Notes

Local cell ID LocalCellId N/A

Path loss coefficient PassLossCoeff Set this parameter to AL1(1) for


NB-IoT cells.

P0 nominal PUSCH P0NominalPUSCH Set this parameter to -105 for NB-


IoT cells.

The following table describes the parameters that must be set in a CellUlpcDedic MO to
configure NPUSCH power control settings.

Parameter Name Parameter ID Setting Notes

Local cell ID LocalCellId N/A

RSRP filtering FilterRsrp Set this parameter to its


coefficient recommended value.

The following table describes the parameters that must be set in a CellSiMap MO to
configure the message mapping relationships of the system.

Parameter Name Parameter ID Setting Notes

Local cell ID LocalCellId N/A

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 154


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

NB-IoT SIB1 NbSib1RepetitionNum When the radio environment is


Repetition Number good, set this parameter to a small
value. Otherwise, set this parameter
to a large value.

NB-IoT SIB2 Period NbSib2Period Do not set this parameter to too


large a value. This parameter should
NB-IoT SIB3 Period NbSib3Period be set to a value to the user volume.
NB-IoT SIB4 Period NbSib4Period It is recommended that parameters
from NB-IoT SIB2 Period to NB-
NB-IoT SIB5 Period NbSib5Period IoT SIB16 Period be set to
different values. Otherwise, more
NB-IoT SIB14 Period NbSib14Period
resources are consumed.
NB-IoT SIB16 Period NbSib16Period

The following table describes the parameters that must be set in a CellDrxPara MO to
configure cell-level DRX settings.

Parameter Name Parameter ID Setting Notes

Local cell ID LocalCellId N/A

DRX Algorithm DrxAlgSwitch If UEs have power-saving


Switch requirements, set this parameter to
ON(On).

NB-IoT On Duration NbOnDurationTimer Set this parameter to its


Timer recommended value.

NB-IoT DRX NbDrxInactivityTimer Set this parameter to its


Inactivity Timer recommended value. If the
recommended value is not used,
ensure that the cycle of the
corresponding coverage level
calculated based on the value of
this parameter does not exceed the
value of the NB-IoT Long DRX
Cycle parameter. Otherwise, UEs
of the corresponding coverage level
will not support DRX.

NB-IoT DRX NbDrxReTxTimer Set this parameter to its


Retransmission Timer recommended value.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 155


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

NB-IoT Long DRX NbLongDrxCycle Set this parameter to SF256 in


Cycle versions earlier than
V100R012C10SPC210.
Set this parameter to its
recommended value in
V100R012C10SPC210 and later
versions. Ensure that the cycle
calculated based on the value of the
NB-IoT On Duration Timer
parameter does not exceed the
value of this parameter. Otherwise,
DRX cannot be enabled for UEs of
the corresponding coverage level.

NB-IoT DRX Uplink NbDrxUlReTxTimer Set this parameter to its


Retransmission Timer recommended value.

The following table describes the parameters that must be set in a CellSel MO to configure
cell selection information.

Parameter Name Parameter ID Setting Notes

Local cell ID LocalCellId N/A

Minimum required RX QRxLevMin The value of this parameter is


level related to the coverage level of the
cell. If the coverage enhancement
capability is strong, the signal
reception strength on the UE side is
weak. In this case, set this
parameter to a small value.

Minimum required RX QQualMin Set this parameter to its default


quality level value.

The following table describes the parameters that must be set in a CellResel MO to configure
common cell reselection information.

Parameter Name Parameter ID Setting Notes

Local cell ID LocalCellId N/A

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 156


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

Hysteresis value for Qhyst When most of the NB-IoT UEs


ranking criteria under a cell are deployed in fixed
positions, cell reselection caused by
signal fluctuation increases power
consumption of the UEs. Set this
parameter to a high value to
increase the cell reselection
difficulty. This reduces power
consumption.

Ue max power allowed PMaxCfgInd N/A


configure indicator

Max transmit power PMax N/A


allowed

Threshold for intra freq SIntraSearchCfgInd Set this parameter to its default
measurements value.
configure indicator

Threshold for intra SIntraSearch The value of this parameter is


frequency related to the coverage level of the
measurements cell. If the coverage enhancement is
large, set this parameter to a small
value.

NB-IoT Intra-Freq TReselForNb Set this parameter to its default


Reselection Time value.

Threshold for non-intra SNonIntraSearchCfgInd Set this parameter to its default


freq measurements value.
configure indicator

Threshold for non-intra SNonIntraSearch The value of this parameter is


frequency related to the coverage level of the
measurements cell. If the coverage enhancement is
large, set this parameter to a small
value.

NB-IoT Inter-Freq TReselInterFreqForNb Set this parameter to its default


Reselection Time value.

In the cell coverage area, if a UE is stable (for instance a meter reader) and is not in cell edge,
it is recommended that neighboring cells not be configured so as to save overhead over the air
interface.
The following table describes the parameters that must be set in a EutranExternalCell MO
to configure an external E-UTRAN cell.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 157


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

Mobile country code Mcc N/A

Mobile network code Mnc N/A

eNodeB ID eNodeBId N/A

Cell ID CellId N/A

Downlink EARFCN DlEarfcn Set this parameter as planned.

Physical cell ID PhyCellId N/A

Tracking area code Tac N/A

Cell name CellName N/A

Uplink Frequency Offset UlFreqOffset Set this parameter as planned.

Downlink Frequency DlFreqOffset Set this parameter as planned.


Offset

NB-IoT Cell Flag NbCellFlag The cell must be a NB-IoT cell. Set
this parameter to TRUE(TRUE).

The following table describes the parameter that must be set in a EutranIntraFreqNCell MO
to configure intra-frequency neighboring cell information.

Parameter Name Parameter ID Setting Notes

Mobile country code Mcc N/A

Mobile network code Mnc N/A

eNodeB ID eNodeBId N/A

Cell ID CellId N/A

Cell offset CellQoffset N/A

Local cell name LocalCellName N/A

Neighbour cell name NeighbourCellName N/A

Physical cell ID PhyCellId N/A

The following table describes the parameter that must be set in a EutranInterFreqNCell MO
to configure inter-frequency neighboring cell information.

Parameter Name Parameter ID Setting Notes

Mobile country code Mcc N/A

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 158


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

Mobile network code Mnc N/A

eNodeB ID eNodeBId N/A

Cell ID CellId N/A

Local cell name LocalCellName N/A

Neighbour cell name NeighbourCellName N/A

The following table describes the parameters that must be set in a EutranInterNFreq MO to
configure a neighboring inter-frequency EARFCN.

Parameter Name Parameter ID Setting Notes

Minimum required QRxLevMin Set this parameter to its default value.


RX level

PMAX configure PmaxCfgInd Set this parameter to its default value.


indicator

PMAX Pmax Set this parameter to its default value.

Downlink EARFCN DlEarfcn Set this parameter as planned.

Frequency offset QoffsetFreq Configure this parameter when the


frequency camping requirements are
different.
If inter-frequency neighboring cells
have different lowest coverage levels,
it is recommended that this parameter
be set to different values for different
EARFCNs.

Uplink Frequency UlFreqOffset Set this parameter as planned.


Offset

Downlink DlFreqOffset Set this parameter as planned.


Frequency Offset

The following table describes the parameters that must be set in a CellAlgoSwitch MO to
configure the SIB16 switch, extended access barring (EAB) switch, RACH backoff switch,
and NB-IoT cell algorithm switch.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 159


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

Lte Utc Broadcast LteUtcBroadcastSwitch If UTC time is broadcast in SIB16, the


Switch overhead over the air interface
increases.
If the UE time can be synchronized in
other ways, for example, obtaining time
from the EMM information on the
MME or from the timer server on the
Internet through NTP, the SIB16
broadcast can be disabled.

Congestion Control MTCCongControlSwitch It is recommended that


Switch for MTC EABAlgoSwitch under this parameter
UE be selected in the cell when the eNodeB
or its connected MMEs are overloaded.
It is recommended that
ExtendedwaittimeSwitch under this
parameter be selected in the cell with
congested air interface resources.

RACH algorithm RachAlgoSwitch Select the BackOffSwitch option of this


switch parameter.

NB-IoT Cell NbCellAlgoSwitch It is recommended that the


Algorithm Switch SI_OFFSET_ADAPTIVE_CFG_SWI
TCH option under this parameter be
selected when time synchronization is
implemented on the NB-IoT network or
there is a comparatively high probability
of UEs failing to demodulate system
information.
If some NB-IoT UEs in a cell comply
with 3GPP TS 36.213 V13.3.0
(2016-09), select
DCI_SF_REP_NUM_COMP_SWITC
H under this parameter. For details, see
6.4.2 Precautions.

Uplink schedule UlSchSwitch It is recommended that


switch UlRaUserSchOptSw under this
parameter be selected in cells with air
interface resource congestion.

Uplink Schedule UlSchExtSwitch If some UEs on the live network do not


Extended Switch support the maximum backoff index 12
defined in 3GPP TS 36.321 (Release
13), operators must select the
PreambleSchEnhSwitch option under
this parameter.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 160


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

Repeater Switch RepeaterSwitch If repeaters are used to amplify RRU


output power, select the
AntRsPwrSwitch option.

If the eNodeB or its connected MMEs are overloaded, it is recommended that the EAB switch
be turned on for the cell and the related parameters be configured as required.
The following table describes the parameter that must be set in an eNodeBFlowCtrlPara MO
to configure dynamic access barring.
Parameter Name Parameter ID Setting Notes

Dynamic AC DynAcBarPolicyMode It is recommended that the same access


Barring Policy control parameters be configured for
Mode cells on the same board.

The following table describes the parameters that must be set in a CellEABAlgoPara MO to
configure access control.

Parameter Name Parameter ID Setting Notes

EAB Category EABCategory By default, access control is


implemented on all UEs If you want to
implement access control on roaming
UEs only, set this parameter to
CATEGORY_B(Category_b) or
CATEGORY_C(Category_c).

NB-IoT Access ABForExceptionData By default, NB-IoT UEs whose RRC


Barring For connection setup cause is mo-
Exception Data ExceptionData are allowed to access the
network. If a large proportion of UEs is
accessing the network with this cause
value, set this parameter to
BOOLEAN_TRUE(BOOLEAN_TRU
E) to bar their access.

NB-IoT Access ABForSpecialAC By default, NB-IoT UEs belonging to


Barring For access classes 11 to 15 are allowed to
AC11-15 access the network. If UEs belonging to
a specific access class initiate excessive
network access requests, their access
can be independently barred.
NOTE
In accordance with 3GPP TS 36.331, access
classes 12 to 14 are valid only in the home
PLMN country, and access classes 11 and 15
are valid only in the HPLMN and EHPLMN.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 161


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

The following table describes the parameter that must be set in a CellRacThd MO to control
the maximum number of UEs that can be admitted to a cell.

Parameter Name Parameter ID Setting Notes

Admission Control AcUserNumber Set this parameter to a comparatively


User Number small value when there are a large
number of online NB-IoT UEs.

The following table describes the parameters that must be set in a CellChPwrCfg MO to
configure cell channel power if repeaters are used to amplify RRU output power.
Parameter Name Parameter ID Setting Notes

Local cell ID LocalCellId -

Antenna Output AntOutputPwr This parameter needs to be set only


Power when the AntRsPwrSwitch option of
the CellAlgoSwitch.RepeaterSwitch
parameter is selected. You are advised to
set this parameter based on the actual
repeater output power.

The following table describes the parameters that must be set in an ENBCELLRSVDPARA
MO to configure the proportion of cell output power when repeaters are used to amplify RRU
output power.
Parameter Name Parameter ID Setting Notes

Local cell ID LocalCellId -

Reserved U16 RsvdU16Para8 Set this parameter only when the


Parameter 8 AntRsPwrSwitch option of the
CellAlgoSwitch.AntRsPwrSwitch
parameter is selected. You are advised to
set this parameter to the proportion of
cell output power.
In LTE in-band deployment, you are
advised to set this parameter to 0 in both
NB-IoT and LTE FDD cells if this
option is selected in both cells.

Scenario-specific Data
In LTE in-band deployment mode, RBs need to be reserved in LTE FDD cells for NB-IoT
deployment. The following table describes the parameters that must be set in a
CellRbReserve MO to configure the reserved RBs. The RB reservation will cause
reestablishment of the LTE FDD cell, and consequently ongoing services in the cell will be
interrupted.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 162


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

Local Cell ID LocalCellId N/A

Index Index The value of each index must be unique.

RB Reserve Type RbRsvType N/A

RB Reserve Start RbRsvStartIndex l When RB Reserve Type is set to


Index DOWNLINK_MODE(DOWNLINK_
MODE), the value of this parameter
needs to meet the RB position specified
in 3.2.3 LTE In-band Deployment.
l When RB Reserve Type is set to
UPLINK_MODE(UPLINK_MODE), it
is recommended that this parameter be
set to an edge RB (avoid LTE RBs that
transmit PRACH resource information or
RBs that are statically configured to
transmit PUCCH resource information)
to reduce the impact on the uplink single-
UE peak rate in LTE FDD cells.
l If the PRB.UlEarfcnCfgInd parameter is
set to NOT_CFG(Not configure), this
parameter must be set to the same value
for the uplink and downlink RBs
reserved for NB-IoT deployment in an
LTE FDD cell.

RB Reserve End RbRsvEndIndex Set this parameter to a value that is the same
Index as that of RB Reserve Start Index.

RB Reserve Mode RbRsvMode l When the corresponding RBs are used to


deploy NB-IoT, set this parameter to
NB_DEPLOYMENT(NB_DEPLOYM
ENT).
l When the corresponding RBs are not
used to deploy NB-IoT but serve as
uplink guard band or used in downlink
puncturing for buffer zone, set this
parameter to
NB_RESERVED(NB_RESERVED).

The following table describes the parameters that must be set in an ENodeBAlgoSwitch MO
to allow FDD UEs to preempt the RRC resources occupied by NB-IoT UEs in NB-IoT and
LTE FDD co-site deployment scenarios.

Parameter Name Parameter ID Setting Notes

LTE User Preempt LTEPreemptNbSwitch It is recommended that this parameter


NB-IoT User Switch be set to ON(On).

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 163


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Setting Notes

UE number UeNumPreemptSwitch It is recommended that


preemption switch NbUeNumPreemptSwitch under this
parameter be selected.

The following table describes the parameter that must be set in an ENodeBNbPara MO to
configure the minimum proportion of UEs in RRC_CONNECTED mode reserved for NB-IoT
in NB-IoT and LTE FDD co-site deployment scenarios.

Parameter Name Parameter ID Setting Notes

NB-IoT Reserved NbRsvMinUserNumRa- Set this parameter as required.


Minimum User tio
Number Ratio

6.4.4.2 Using the CME


For detailed operations, see CME-based Feature Configuration.

In LTE in-band deployment, ensure that the LTE FDD cell has been activated before
activating an NB-IoT cell.

6.4.4.3 Using MML Commands


Before configuring an NB-IoT cell, ensure that the required hardware has been configured to
support NB-IoT, including the main control board, baseband processing units, and RF units.
For details, see section "Configuring Device Data" in 3900 Series Base Station Initial
Configuration Guide. The transport data should also have been configured. For details about
how to configure the transport data, see section "Configuring Transport Data" in 3900 Series
Base Station Initial Configuration Guide. Both the S1.MmeRelease and
S1INTERFACE.MmeRelease parameters must be set to Release_R13.

Step 1 (Optional) If an RRU is added, configure a sector and a set of sector equipment.
1. Run the ADD SECTOR command to add a sector.
NOTE

Cells can work in 1T2R or 2T2R mode. Accordingly, the sector serving the cell must be
configured with the required number of antennas (specified by ANTNUM). For example, to add a
1T2R sector, run the ADD SECTOR command with ANTNUM set to 2.
2. Run the ADD SECTOREQM command to add a set of sector equipment.
NOTE

If the CREATESECTOREQM parameter in the ADD SECTOR command is set to


TRUE(TRUE), ADD SECTOREQM is not required. The default value of this parameter is
FALSE(FALSE).

Step 2 (Optional) To bind baseband equipment to the cell, run the ADD BASEBANDEQM
command.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 164


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Step 3 (Optional) To configure the operator and tracking area information, perform the following
steps:
1. Run the ADD CNOPERATOR command to add an operator.
2. Run the ADD CNOPERATORTA command to add a tracking area.

Step 4 Run the MOD MMECAPINFO command to configure the MME's capability of supporting
NB-IoT.

Step 5 (Optional) When user plane CIoT EPS optimization is enabled, run the ADD
RLCPDCPPARAGROUP command to add an RLC PDCP parameter group.

Step 6 (Optional) When user plane CIoT EPS optimization is enabled, run the MOD QCIPARA
command to add the mapping between the QCIs of non-GBR services and the RLC PDCP
parameter groups.
NOTE

The parameter settings in the QciPara MO take effect only when the
GlobalProcSwitch.QciParaEffectFlag parameter is set to ON(On).

Step 7 Run the ADD CELL command to add a cell.

Step 8 (Optional) To reserve LTE FDD in-band RBs for NB-IoT deployment, run the ADD
CELLRBRESERVE command. The RB reservation will cause reestablishment of the LTE
FDD cell, and consequently ongoing services in the cell will be interrupted.

Step 9 Run the ADD PRB command to add a PRB.

Step 10 Run the ADD EUCELLSECTOREQM command to bind the sector equipment and
baseband equipment (which is optional) to the cell.

Step 11 Run the ADD PRBTOEUCELLSECTOREQM command to associate the PRB to the sector
equipment.

Step 12 Run the ADD CELLOP command to add an operator for the cell.

Step 13 Run the MOD PDSCHCFG command to configure the power of the cell reference signal.

Step 14 Run the MOD RACHCFG command to configure the parameters related to RACH.

Step 15 Run the MOD CELLRACHCECFG command to configure the parameters related to the
PRACH for all coverage levels.

Step 16 (Optional) To optimize the parameters related to the paging over the Uu interface, run the
MOD PCCHCFG command.

Step 17 (Optional) To optimize the S1 default paging DRX value for NB-IoT, run the MOD
GLOBALPROCSWITCH command.

Step 18 (Optional) When some NB-IoT UEs in a cell comply with 3GPP Release 13 (2017-03), run
the MOD GLOBALPROCSWITCH command to turn on the switches controlling UE
compatibility with NB-IoT specified in 3GPP Release 13. When these switches are turned on,
NB-IoT UEs that do not comply with 3GPP Release 13 (2017-03) cannot access the network.

Step 19 (Optional) To optimize the values of timers related to RRC connection control, run the MOD
RRCCONNSTATETIMER command.

Step 20 (Optional) To optimize the value of the Uu message waiting timer, run the MOD
ENODEBCONNSTATETIMER command.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 165


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Step 21 (Optional) To optimize the PDCCH resource allocation for different coverage levels in an
NB-IoT cell, run the MOD CELLPDCCHCECFG command.

Step 22 (Optional) To optimize the uplink scheduling algorithm parameters for different coverage
levels in an NB-IoT cell, run the MOD NBCELLULSCHCEALGO command.

Step 23 (Optional) To optimize the downlink scheduling algorithm parameters for different coverage
levels, run the MOD NBCELLDLSCHCEALGO command.

Step 24 Run the MOD CELLULPCCOMM command to modify the NB-IoT cell uplink power
control parameters.

Step 25 (Optional) To optimize dedicated parameters related to power control on the NPUSCH, run
the MOD CELLULPCDEDIC command.

Step 26 (Optional) To modify the SIB-to-SI mapping, run the MOD CELLSIMAP command.

Step 27 (Optional) To activate DRX in RRC_CONNECTED mode, run the MOD CELLDRXPARA
command.

Step 28 Run the MOD CELLSEL command to configure the cell selection information.

Step 29 (Optional) To configure cell reselection information, run the MOD CELLRESEL command.

Step 30 Perform the following procedures to configure neighboring cells:


1. (Optional) To configure inter-site intra-frequency or inter-frequency external cells for
NB-IoT, run the MOD EUTRANEXTERNALCELL command.
2. (Optional) To configure intra-frequency neighboring NB-IoT cells, run the MOD
EUTRANINTRAFREQNCELL command.
3. (Optional) To configure inter-frequency EARFCNs for NB-IoT, run the MOD
EUTRANINTERNFREQ command.
4. (Optional) To configure inter-frequency neighboring cells for NB-IoT, run the MOD
EUTRANINTERFREQNCELL command.

Step 31 Run the MOD CELLALGOSWITCH command to enable the backoff function, and if
required, the access barring function.
1. (Optional) To modify the dynamic access barring policy mode, run the MOD
ENODEBFLOWCTRLPARA command.
2. Run the MOD CELLEABALGOPARA command to set the access barring-related
parameters.

Step 32 (Optional) When the air interface is congested in a cell, run the MOD
CELLALGOSWITCH command to enable random access flow control and to allow the
eNodeB to include the extendedWaitTime IE in RRC Connection Release messages.

Step 33 (Optional) If some UEs on the live network do not support the maximum backoff index 12
defined in 3GPP TS 36.321 (Release 13), run the MOD CELLEABALGOPARA command
to select the PreambleSchEnhSwitch option.

Step 34 (Optional) When the maximum number of UEs that can be admitted to an NB-IoT cell needs
to be controlled, run the MOD CELLRACTHD command to set Admission Control User
Number.

Step 35 (Optional) To enable UTC broadcast or adaptive configuration of system information frame
offset, run the MOD CELLALGOSWITCH command.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 166


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Step 36 (Optional) If repeaters are used to amplify RRU output power in LTE in-band deployment,
perform the following operations:
1. Run the MOD CELLALGOSWITCH command to turn on AntRsPwrSwitch in both
NB-IoT and LTE FDD cells.
2. Run the MOD CELLCHPWRCFG command to set the antenna transmit power of both
NB-IoT and LTE FDD cells.
3. Run the MOD ENBCELLRSVDPARA command to set the proportion of NB-IoT cell
output power and the proportion of LTE FDD cell output power.
Step 37 (Optional) If repeaters are used to amplify RRU output power in guardband or standalone
deployment, perform the following operations:
1. Run the MOD CELLALGOSWITCH command to turn on AntRsPwrSwitch in the
NB-IoT cell.
2. Run the MOD CELLCHPWRCFG command to configure the antenna output power of
the NB-IoT cell.
3. Run the MOD ENBCELLRSVDPARA command to set the proportion of NB-IoT cell
output power.
Step 38 (Optional) When some NB-IoT UEs in a cell comply with 3GPP TS 36.213 V13.3.0
(2016-09), run the MOD CELLALGOSWITCH command to turn on the related switches
under the NB-IoT Cell Algorithm Switch. When these switches are turned on, NB-IoT UEs
that do not comply with 3GPP TS 36.213 V13.3.0 (2016-09) cannot access the network.
Step 39 Run the ACT CELL command to activate the cell.

----End

Co-site Deployment of NB-IoT and LTE FDD Cells


Step 1 (Optional) To configure LTE FDD UEs to preempt RRC resources occupied by NB-IoT UEs
in case of RRC resource insufficiency, run the MOD ENODEBALGOSWITCH command
with LTE User Preempt NB-IoT User Switch set to ON(On).
Step 2 (Optional) To allow resource preemption between NB-IoT UEs, run the MOD
ENODEBALGOSWITCH command to select NbUeNumPreemptSwitch under the UE
number preemption switch parameter.
Step 3 (Optional) To prevent excessive preemption of RRC resources by LTE FDD UEs, run the
MOD ENODEBNBPARA command with NB-IoT Reserved Minimum User Number
Ratio specified.

----End

6.4.4.4 MML Command Examples


//(Optional) Adding a sector and a set of sector equipment if an RRU is added
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;
//(Optional) Adding baseband equipment
ADD BASEBANDEQM:
BASEBANDEQMID=0,UMTSDEMMODE=NULL,BASEBANDEQMTYPE=ULDL,SN1=2,SN2=1;
//(Optional) Adding an operator
ADD CNOPERATOR: CnOperatorId=0, CnOperatorName="mobile",
CnOperatorType=CNOPERATOR_PRIMARY, Mcc="460", Mnc="01";
//Adding a tracking area for an operator
ADD CNOPERATORTA: TrackingAreaId=0, CnOperatorId=0, Tac=33,
NbIotTaFlag=BOOLEAN_TRUE;

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 167


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

//Configuring the MME to support the user plane CIoT EPS optimization function
and LTE FDD/LTE TDD services
ADD MMECAPINFO: MmeCapCfgId=0, S1CfgType= S1_CFG, S1Id=0, NbCiotEpsOptCap=CP_UP,
NbLteSupportCap=SUPPORT;
//(Optional) Configuring the RLC PDCP parameter groups for user plane CIoT EPS
optimization
ADD RLCPDCPPARAGROUP: RlcPdcpParaGroupId=130, CatType=NBIOT, RlcMode=RlcMode_AM,
UlDlDiscardtimerSwitch=OFF;
//(Optional) Configuring the QCIs of non-GBR services using user plane CIoT EPS
optimization
MOD GLOBALPROCSWITCH: QciParaEffectFlag=ON;
MOD QCIPARA: Qci=5, NbRlcPdcpParaGroupId=130;
MOD QCIPARA: Qci=6, NbRlcPdcpParaGroupId=130;
MOD QCIPARA: Qci=7, NbRlcPdcpParaGroupId=130;
MOD QCIPARA: Qci=8, NbRlcPdcpParaGroupId=130;
MOD QCIPARA: Qci=9, NbRlcPdcpParaGroupId=130;
//Adding an NB-IoT cell (cell 0)
ADD CELL: LocalCellId=0, CellName="NBCell0", 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_FALSE, TxRxMode=1T1R,
UserLabel="NBCell0";
//(Optional) Reserving LTE FDD RBs for NB-IoT deployment in LTE in-band mode
(Assume that the LTE FDD cell bandwidth is 20 MHz, and downlink RB 44 and uplink
RB 0 are reserved for NB-IoT.)
ADD CELLRBRESERVE: LocalCellId=0, Index=0, RbRsvMode=NB_DEPLOYMENT,
RbRsvType=DOWNLINK_MODE, RbRsvStartIndex=44, RbRsvEndIndex=44;
ADD CELLRBRESERVE: LocalCellId=0, Index=1, RbRsvMode=NB_DEPLOYMENT,
RbRsvType=UPLINK_MODE, RbRsvStartIndex=0, RbRsvEndIndex=0;
//Configuring the PRB for NB-IoT in LTE in-band deployment (Assume that the
frequency band is band 8, the uplink EARFCN is 21511, and the downlink EARFCN is
3590.)
ADD PRB: LocalCellId=0, PrbId=0, DeployMode=IN_BAND, FreqBand=8,
UlEarfcnCfgInd=CFG, UlEarfcn=21511, UlFreqOffset=NEG_2, DlEarfcn=3590,
DlFreqOffset=POS_0, LteCellId=1;
//Configuring the PRB for an NB-IoT cell in standalone deployment
ADD PRB: LocalCellId=0,PrbId=0,DeployMode=STAND_ALONE,FreqBand=8,
UlEarfcnCfgInd=NOT_CFG, DlEarfcn=3600,DlFreqOffset=NEG_0DOT5;
//Configuring the PRB for an NB-IoT cell in LTE guardband deployment
ADD PRB: LocalCellId=0,PrbId=0,DeployMode=GUARD_BAND,FreqBand=8,
UlEarfcnCfgInd=NOT_CFG, DlEarfcn=3552,DlFreqOffset=NEG_2, LteBandWidth=
LTE_SYSTEM_BW_10M,LteDlEarfcn=3600;
//Adding sector equipment
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0, BaseBandEqmId=0;
//Adding the mapping relationship between a PRB and sector equipment
ADD PRBTOEUCELLSECTOREQM: LocalCellId=0, SectorEqmId=0, PrbId=0;
//Adding an operator for the cell
ADD CELLOP: LocalCellId=0, TrackingAreaId=0;
//Configuring NRS power allocation
MOD PDSCHCFG: LocalCellId=0, ReferenceSignalPwr=272;
//Configuring RACH information
MOD RACHCFG: LocalCellId=0,
PreambInitRcvTargetPwr=DBM_112,NbCyclicPrefixLength=66DOT7,
NbRsrpFirstThreshold=-128, NbRsrpSecondThreshold=-137,
PrachStartTimeCfgInd=NOT_CFG;
//Configuring the cell-level PRACH for three coverage levels
MOD CELLRACHCECFG:LocalCellId=0,CoverageLevel=0,ContentionResolutionTimer=
PP_8,PrachTransmissionPeriod= SF640,PrachSubcarrierOffset=
SC36,PrachRepetitionCount=REP_2,MaxNumPreambleAttempt=REP_4, PrachDetectionThld=
LEVEL_3;
MOD CELLRACHCECFG:LocalCellId=0,CoverageLevel=1,ContentionResolutionTimer=
PP_8,PrachTransmissionPeriod= SF640,PrachSubcarrierOffset=
SC36,PrachRepetitionCount=REP_8,MaxNumPreambleAttempt=REP_4, PrachDetectionThld=
LEVEL_2;
MOD CELLRACHCECFG:LocalCellId=0,CoverageLevel=2,ContentionResolutionTimer=
PP_8,PrachTransmissionPeriod= SF640,PrachSubcarrierOffset=
SC36,PrachRepetitionCount=REP_32,MaxNumPreambleAttempt=REP_4, PrachDetectionThld=
LEVEL_0;

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 168


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

//(Optional) Setting the default paging cycle and number of paging groups for NB-
IoT
MOD PCCHCFG: LocalCellId=0, PagingStrategy=PAGING_STRATEGY_DIFFPRI,
DefaultPagingCycleForNb=rf512, NbForNbIoT=ONE_64TH_T,
MaxNumRepetitionForPaging=REP_32;
//(Optional) Setting the S1 default paging DRX value for NB-IoT
MOD GLOBALPROCSWITCH: S1DefaultPagingDrxForNb=512;
// (Optional) Turning on NbR13CompatSw
MOD GLOBALPROCSWITCH: UeCompatSwitch=NbR13CompatSw-1;
//(Optional) Setting the NB-IoT UE inactivity timer
MOD RRCCONNSTATETIMER: NbUeInactiveTimer=30;
//Setting the S1 message waiting timer and Uu message waiting timer
MOD ENODEBCONNSTATETIMER: S1MessageWaitingTimer=20, UuMessageWaitingTimer=35;
//(Optional) Configuring the cell-level PDCCH configurations for three coverage
levels
MOD CELLPDCCHCECFG: LocalCellId=0, CoverageLevel=0,
PdcchMaxRepetitionCnt=REP_8,PdcchPeriodFactor=G_2,PdcchTransRptCntFactor=ONER_EIGH
TR;
MOD CELLPDCCHCECFG: LocalCellId=0, CoverageLevel=1,
PdcchMaxRepetitionCnt=REP_16,PdcchPeriodFactor=G_2,PdcchTransRptCntFactor=ONER_EIG
HTR;
MOD CELLPDCCHCECFG: LocalCellId=0, CoverageLevel=2,
PdcchMaxRepetitionCnt=REP_32,PdcchPeriodFactor=G_2,PdcchTransRptCntFactor=QUARTERR
;
//(Optional) Configuring the cell uplink scheduling information for three
coverage levels
MOD NBCELLULSCHCEALGO: LocalCellId=0, CoverageLevel=0,
UlInitialMcs=MCS_9,UlInitialTransRptCount=REP_1,AckNackTransRptCount=REP_2,AckNack
TransRptCountMsg4=REP_4;
MOD NBCELLULSCHCEALGO: LocalCellId=0, CoverageLevel=1,
UlInitialMcs=MCS_0,UlInitialTransRptCount=REP_2,AckNackTransRptCount=REP_4,AckNack
TransRptCountMsg4=REP_8;
MOD NBCELLULSCHCEALGO: LocalCellId=0, CoverageLevel=2,
UlInitialMcs=MCS_0,UlInitialTransRptCount=REP_32,AckNackTransRptCount=REP_32,AckNa
ckTransRptCountMsg4=REP_64;
//(Optional) Configuring the cell downlink scheduling information and Uu message
waiting timers for three coverage levels
MOD NBCELLDLSCHCEALGO: LocalCellId=0, CoverageLevel=0,
DlInitialTransRptCount=REP_1, DlInitialMcs=MCS_10, UuMessageWaitingTimer=35;
MOD NBCELLDLSCHCEALGO: LocalCellId=0, CoverageLevel=1,
DlInitialTransRptCount=REP_1, DlInitialMcs=MCS_1, UuMessageWaitingTimer=45;
MOD NBCELLDLSCHCEALGO: LocalCellId=0, CoverageLevel=2,
DlInitialTransRptCount=REP_16, DlInitialMcs=MCS_0, UuMessageWaitingTimer=65;
//Modifying the NB-IoT cell uplink power control parameters
MOD CELLULPCCOMM: LocalCellId=0, PassLossCoeff=AL1, P0NominalPUSCH=-105;
//(Optional) Setting the NPUSCH power control dedicated information
MOD CELLULPCDEDIC: LocalCellId=0, FilterRsrp=UU_FC6_FILTER_COEFF;
//(Optional) Setting cell SIB-to-SI mapping
MOD CELLSIMAP: LocalCellId=0, NbSib1RepetitionNum=16, NbSib2Period=RF512,
NbSib3Period=RF2048;
//(Optional) Configuring DRX
MOD CELLDRXPARA:LOCALCELLID=0, DrxAlgSwitch=ON;
//(Optional) Configuring DRX parameters
MOD CELLDRXPARA: LocalCellId=0, NbDrxInactivityTimer=PP3, NbDrxReTxTimer=PP4,
NbDrxUlReTxTimer=PP4, NbLongDrxCycle=SF2048, NbOnDurationTimer=PP3;
//Configuring cell selection information
MOD CELLSEL: LocalCellId=0, QRxLevMin=-70, QQualMin=-23;
//(Optional) Configuring cell reselection information
MOD CELLRESEL: LocalCellId=0, Qhyst=DB2_Q_HYST, SNonIntraSearchCfgInd=CFG,
SNonIntraSearch=9, QRxLevMin=-65, PMaxCfgInd=CFG, PMax=-27,
SIntraSearchCfgInd=CFG, SIntraSearch=29, TReselForNb=5, TReselInterFreqForNb=6;
//(Optional) Configuring E-UTRAN external cell information
ADD EUTRANEXTERNALCELL: Mcc="460", Mnc="20", eNodeBId=255, CellId=1, NbCellFlag
=TRUE, DlEarfcn=3000, DlFreqOffset=NEG_0DOT5, UlEarfcnCfgInd=CFG, UlEarfcn=21000,
UlFreqOffset=POS_0, PhyCellId=1, Tac=1;
//(Optional) Configuring intra-frequency neighboring cell information
ADD EUTRANINTRAFREQNCELL: LocalCellId=0, Mcc="460", Mnc="20", eNodeBId=255,
CellId=1, CellIndividualOffset=dB1, CellQoffset=dB1;
//(Optional) Adding inter-frequency neighboring frequencies

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 169


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

ADD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=3106,


DlFreqOffset=NEG_0DOT5,UlEarfcnCfgInd=CFG, UlEarfcn=21106, UlFreqOffset=POS_0,
MeasBandwidth=MBW50, QoffsetFreq=dB2, QRxlevmin=-64, PmaxCfgInd=CFG, Pmax=23;
//(Optional) Configuring inter-frequency neighboring cell information
ADD EUTRANINTERFREQNCELL: LocalCellId=0, Mcc="460", Mnc="20", eNodeBId=2,
CellId=1, CellQoffset=dB2;
//Activating the access barring and backoff functions
MOD CELLALGOSWITCH:LOCALCELLID=0,MTCCongControlSwitch=EABAlgoSwitch-1,
RachAlgoSwitch=BackOffSwitch-1;
//(Optional) Setting the dynamic access barring policy mode
MOD ENODEBFLOWCTRLPARA: DynAcBarPolicyMode=FLOWCONTROL;
//Configuring access barring parameters
MOD CELLEABALGOPARA: LocalCellId=0, EABTriggerThd=80, EABStatPeriod=30,
EABCategory=CATEGORY_A, EABCancelThd=50, EABCancelCondSatiPeriod=1,
ABForExceptionData=BOOLEAN_TRUE,
ABForSpecialAC=AC11BARSTATE-1&AC12BARSTATE-1&AC13BARSTATE-1&AC14BARSTATE-1&AC15BAR
STATE-1;
//(Optional) Enabling random access flow control and allowing the eNodeB to
include the extendedWaitTime IE in RRC Connection Release messages
MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=UlRaUserSchOptSw-1,
MTCCongControlSwitch=ExtendedwaittimeSwitch-1;
//(Optional) Turning on PreambleSchEnhSwitch
MOD CELLALGOSWITCH: LocalCellId=0, UlSchExtSwitch=PreambleSchEnhSwitch-1;
//(Optional) Configuring the maximum number of UEs that can be admitted to a cell
MOD CELLRACTHD: LocalCellId=0, AcUserNumber=600;
//(Optional) Enabling the UTC time broadcast
MOD CELLALGOSWITCH:LOCALCELLID=0, LteUtcBroadcastSwitch=ON;
//(Optional) Enabling adaptive configuration of system information frame offset
MOD CELLALGOSWITCH:LOCALCELLID=0,
NbCellAlgoSwitch=SI_OFFSET_ADAPTIVE_CFG_SWITCH-1;
//(Optional) Setting both the proportion of NB-IoT cell output power and the
proportion of LTE FDD cell (cell 1) output power to 0 when repeaters are used to
amplify RRU output power in LTE in-band deployment mode
MOD CELLALGOSWITCH: LocalCellId=0, RepeaterSwitch=AntRsPwrSwitch-1;
MOD CELLALGOSWITCH: LocalCellId=1, RepeaterSwitch=AntRsPwrSwitch-1;
MOD CELLCHPWRCFG: LocalCellId=0, AntOutputPwr=20;
MOD CELLCHPWRCFG: LocalCellId=1, AntOutputPwr=20;
MOD ENBCELLRSVDPARA: LocalCellId=0, RsvdU16Para8=0;
MOD ENBCELLRSVDPARA: LocalCellId=1, RsvdU16Para8=0;
//(Optional) Setting the proportion of NB-IoT cell output power to 1000 when
repeaters are used to amplify RRU output power in LTE guardband or standalone
deployment mode
MOD CELLALGOSWITCH: LocalCellId=0, RepeaterSwitch=AntRsPwrSwitch-1;
MOD CELLCHPWRCFG: LocalCellId=0, AntOutputPwr=20;
MOD ENBCELLRSVDPARA:LocalCellId=0, RsvdU16Para8=1000;

//(Optional) Selecting DCI_SF_REP_NUM_COMP_SWITCH


MOD CELLALGOSWITCH: LOCALCELLID=0, NbCellAlgoSwitch=DCI_SF_REP_NUM_COMP_SWITCH-1;
//Activating the cell
ACT CELL: LocalCellId=0;

Co-site Deployment of NB-IoT and LTE FDD Cells


//(Optional) Enabling LTE FDD UEs to preempt RRC resources occupied by NB-IoT UEs
MOD ENODEBALGOSWITCH: LTEPreemptNbSwitch=ON;
//(Optional) Enabling resource preemption between NB-IoT UEs
MOD ENODEBALGOSWITCH: UeNumPreemptSwitch=NbUeNumPreemptSwitch-1;
//(Optional) Configuring the minimum proportion of UEs in RRC_CONNECTED mode
reserved for NB-IoT
MOD ENODEBNBPARA: NbRsvMinUserNumRatio=10;

6.4.5 Activation Observation


Step 1 Run the DSP CELL command to check cell status.

If the value of the Cell instance state parameter is Normal, the cell has been activated.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 170


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Step 2 Use a UE to access the cell. If the UE successfully accesses the cell, the cell is working
properly.

----End

6.4.6 Deactivation

6.4.6.1 Using the CME


For detailed operations, see CME-based Feature Configuration.

6.4.6.2 Using MML Commands


l Deactivate a cell.
Run the DEA CELL command to deactivate the cell.
l Deactivate the cell-level DRX.
Run the MOD CELLDRXPARA command to set the DRX Algorithm Switch
parameter to OFF(Off).
l Deactivate the access barring function.
Run the MOD CELLALGOSWITCH command to configure
EABAlgoSwitch(EABAlgoSwitch) under the Congestion Control Switch for MTC
UE parameter to Off.
l //Deactivating the UTC broadcast function.
Run the MOD CELLALGOSWITCH command to set Lte Utc Broadcast Switch to
OFF(Off).

6.4.6.3 MML Command Examples


//Deactivating the cell
DEA CELL: LocalCellId=0;
//Deactivating the DRX function
MOD CELLDRXPARA:LOCALCELLID=0, DrxAlgSwitch=OFF;
//Deactivating the access barring function
MOD CELLALGOSWITCH:LOCALCELLID=0,MTCCongControlSwitch=EABAlgoSwitch-0;
//Deactivating the UTC broadcast function
MOD CELLALGOSWITCH:LOCALCELLID=0, LteUtcBroadcastSwitch=OFF;

6.5 Performance Monitoring


After deploying NB-IoT, observe KPIs related to the access success rate, call drop rate,
number of UEs, residual BLER (RBLER), throughput, and paging.

l Access success rates, involving:


RRC connection setup success rate
RRC connection setup success rate = {100} x L.NB.RRC.ConnReq.Succ /
(L.NB.RRC.ConnReq.Att + L.NB.RRC.ResumeFail.RRCSetup)
RRC connection resume success rate
RRC connection resume success rate = {100} x L.NB.RRC.ResumeReq.Succ /
L.NB.RRC.ResumeReq.Att

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 171


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

l Call drop rate


Formula: {100} x (L.NB.UECNTX.AbnormRel)/(L.NB.UECNTX.NormRel +
L.NB.UECNTX.AbnormRel)
l Counters related to UE quantity
Counter ID Counter Name

1526744783 L.NB.Traffic.User.Avg

1526744784 L.NB.Traffic.User.Avg.CoverageLevel0

1526744785 L.NB.Traffic.User.Avg.CoverageLevel1

1526744786 L.NB.Traffic.User.Max

1526744787 L.NB.Traffic.User.Max.CoverageLevel0

1526744788 L.NB.Traffic.User.Max.CoverageLevel1

1526744789 L.NB.Traffic.User.Max.CoverageLevel2

l RBLER
Uplink RBLER
Uplink RBLER = {100} x (L.NB.Traffic.UL.SCH.ErrTB.Rbler) /
(L.NB.Traffic.UL.SCH.TB)
Downlink RBLER
Downlink RBLER = {100} x (L.NB.Traffic.DL.SCH.ErrTB.Rbler) /
(L.NB.Traffic.DL.SCH.TB)
l Throughput
Uplink UE throughput
Formula: L.NB.Thrp.bits.UL/L.NB.Thrp.Time.UL
Downlink UE throughput
Formula: L.NB.Thrp.bits.DL/L.NB.Thrp.Time.DL
l Counters related to paging
Counter ID Counter Name Counter Description

1526744780 L.NB.Paging.S1.Rx Number of paging messages received over


the S1 interface in a cell. This counter
reflects the signaling overhead brought by
UEs in RRC_IDLE mode.

1526744782 L.NB.Paging.UU.Su NB-IoT UEs have low mobility and most


cc UEs are fixed in a cell. Paging messages
are sent preferentially in the cell.
Therefore, the paging success rate of the
cell can be estimated. Paging success rate
= L.NB.Paging.UU.Succ /
L.NB.Paging.UU.Att

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 172


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Counter ID Counter Name Counter Description

1526744690 L.NB.Paging.UU.At NOTE


t NB-IoT UEs have low mobility and most UEs
are fixed in a cell. The EPC preferentially sends
paging messages in the cell. Therefore, the
paging success rate of the cell can be estimated
using the preceding formula.
If a paging fails, the EPC sends the paging
messages in other cells or eNodeBs. If this
occurs frequently, the preceding formula cannot
be used to estimate the paging success rate.
You can obtain the precise paging success rate
from the EPC.

1526744691 L.NB.Paging.Dis.Pc Number of paging messages discarded due


hCong to PCH congestion in a cell.

l Counters related to DRX in connected mode


L.NB.Traffic.User.Cdrx.Avg: It indicates the average number of UEs that enter
DRX mode in connected mode in a cell.
L.NB.Active.Time and L.NB.Sleep.Time: They indirectly indicate the power
saving effect of UEs in a cell.
l Counters related to access barring
Counter ID Counter Name

1526745767 L.NB.AB.Trigger.Num

1526745768 L.NB.AB.Cancel.Num

1526745769 L.NB.AB.Adjust.Num

1526745770 L.NB.AB.Control.Dur

6.6 Parameter Optimization


The following table provides suggestions on optimizing EAB-related parameters in the
CellEABAlgoPara MO.

Parameter Name Parameter ID Optimization Suggestion

EAB Control EABStatPeriod With other conditions unchanged, a long


Statistic Periods statistic period is difficult to meet the
trigger condition and the congestion
state is difficult to remove. Once the
trigger condition is met, the period when
a user is prohibited from accessing
increases.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 173


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Optimization Suggestion

EAB Control EABTriggerThd With other conditions unchanged, when


Trigger Threshold this parameter is set to a large value,
trigger conditions are hard to meet, and
the congestion state is difficult to
relieve. Consequently, the impact on
user experience is small.

EAB Control EABCancelThd With other conditions unchanged, when


Cancel Threshold this parameter is set to a large value,
cancellation conditions are hard to meet,
and the congestion state is difficult to
relieve. Consequently, the impact on
user experience is small.

EAB Cancel EABCancelCondSati- With other conditions unchanged, when


Condition Satisfied Period this parameter is set to a small value,
Period trigger conditions are easy to meet, and
the congestion state is difficult to
relieve. Consequently, the impact on
user experience is small.

The following table provides suggestions on optimizing uplink scheduling parameter settings
for NB-IoT in the NbCellUlSchCEAlgo MO.

Parameter Name Parameter ID Optimization Suggestion

Uplink Initial MCS UlInitialMcs A large value indicates a large uplink


initial MCS index, high spectrum
efficiency, and low demodulation
success rate.
A small value indicates a small uplink
initial modulation and coding scheme
(MCS), low spectrum efficiency, and
high demodulation success rate.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 174


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Optimization Suggestion

UL Initial UlInitialTransRptCount A large value indicates a large number


Transmission of transmission repetition times, low
Repetition Count SINR demodulation threshold, high
demodulation success rate, and more
transmission resources.
A small value indicates a small number
of transmission repetition times, high
SINR demodulation threshold, low
demodulation success rate, and less
transmission resources.
When this parameter is set to a large
value, the transmission delay increases,
and the RRC connection may be
abnormally released during data
transmission due to the coordination
failure of this parameter with multiple
timers. It is recommended that this
parameter be set to the recommended
value.

ACK/NACK AckNackTransRpt- A large value indicates a large number


Transmission Count of ACK/NACK transmission repetition
Repetition Count times, good receive performance, high
demodulation success rate, and more
transmission resources.
A small value indicates a small number
of ACK/NACK transmission repetition
times, poor receive performance, low
demodulation success rate, and less
transmission resources.
When this parameter is set to a large
value, the transmission delay increases,
and the RRC connection may be
abnormally released during data
transmission due to the coordination
failure of this parameter with multiple
timers. It is recommended that this
parameter be set to the recommended
value.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 175


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Optimization Suggestion

Msg4 ACK/NACK AckNackTransRpt- A large value indicates a large number


Trans Repetition CountMsg4 of ACK/NACK transmission repetition
Count times for Msg4, good receive
performance, high demodulation
success rate, and more transmission
resources.
A small value indicates a small number
of ACK/NACK transmission repetition
times for Msg4, poor receive
performance, low demodulation success
rate, and less transmission resources.
When this parameter is set to a large
value, the transmission delay increases,
and the coordination between this
parameter and multiple timers need to
be considered. For example, the
maximum length of the contention
resolution timer is 10.24s, as stipulated
in 3GPP specifications. When the
NPDCCH period is large and this
parameter is set to a large value, the
contention resolution may fail to be
completed. It is recommended that this
parameter be set to the recommended
value.

The following table provides suggestions on optimizing downlink scheduling parameter


settings for NB-IoT in the NbCellDlSchCEAlgo MO.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 176


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Optimization Suggestion

DL Initial DlInitialTransRptCount A large value indicates a large number


Transmission of initial transmission repetition times
Repetition Count and consumption of more time domain
resources.
A small value indicates a small number
of initial transmission repetition times
and consumption of less time domain
resources.
In scenarios with a large number of
users and high coverage level, a too
large value increases the delay, occupied
resources, and congestion level.
When this parameter is set to a large
value, the transmission delay increases,
and the coordination between this
parameter and multiple timers need to
be considered. For example, the
maximum length of the contention
resolution timer is 10.24s, as stipulated
in 3GPP specifications. When the
NPDCCH period is large and this
parameter is set to a large value, the
contention resolution may fail to be
completed. It is recommended that this
parameter be set to the recommended
value.

Downlink Initial DlInitialMcs A large value indicates a large downlink


MCS initial MCS index, high spectrum
efficiency, and low demodulation
success rate.
A small value indicates a small
downlink initial MCS index, low
spectrum efficiency, and high
demodulation success rate.

The following table provides suggestions on optimizing parameters related to the NB-IoT
downlink NPDCCH scheduling algorithm, which are in the CellPdcchCECfg MO.

Parameter Name Parameter ID Optimization Suggestion

PDCCH Maximum PdcchMaxRepetitionCn A larger value of this parameter


Repetition Count t indicates a larger maximum repetition
count for the NPDCCH in the
corresponding coverage level, a larger
NPDCCH period, and a longer
scheduling interval.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 177


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Optimization Suggestion

PDCCH Period PdcchPeriodFactor The NPDCCH period for a coverage


Factor level can be obtained by the PDCCH
period factor multiplied by the
maximum number of PDCCH repetition
counts for the coverage level.
A larger value of this parameter results
in a longer NPDCCH period for the
coverage level and a longer scheduling
interval.
A smaller value of this parameter results
in a shorter NPDCCH period for the
coverage level and a shorter scheduling
interval.
When both this parameter and the
PDCCH Maximum Repetition Count
parameter are set to a large value, the
scheduling delay increases, and the
coordination between these parameters
and multiple timers need to be
considered. For example, the maximum
length of the contention resolution timer
is 10.24s, as stipulated in 3GPP
specifications. When the sum of
NPDCCH transmission duration,
scheduling delay, Msg4 NPDSCH
transmission duration, and Msg4 ACK/
NACK transmission duration exceeds
10.24s, the contention resolution fails to
be completed. It is recommended that
this parameter be set to the
recommended value.

PDCCH Initial PdcchTransRptCntFac- A smaller value of this parameter


Trans Rept Count tor indicates a smaller number of NPDCCH
Factor DCI initial transmission repetition times
of UEs under a coverage level and more
initial scheduling chances in an
NPDCCH period.
A larger value of this parameter
indicates a larger number of NPDCCH
DCI initial transmission repetition times
of UEs under a coverage level and fewer
initial scheduling chances in an
NPDCCH period.

The following table provides suggestions on optimizing parameters related to NB-IoT paging,
which are in the PCCHCFG MO.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 178


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Parameter Name Parameter ID Optimization Suggestion

NB-IoT Default DefaultPagingCycle- If the UE does not support eDRX, it is


Paging Cycle ForNb recommended that this parameter be set
to a large value so as to reduce UE
power consumption.

NB-IoT nB NbForNbIoT With a heavy paging load, increasing


the value of this parameter improves the
paging capacity per time unit and
decreases the downlink data
transmission capacity.
With a low paging load and insensitive
paging delay of the system, decreasing
the value of this parameter decreases
the paging capacity per time unit and
increases downlink data transmission
capacity.

Maximum Number MaxNumRepetitionFor- When the coverage of paging services is


of Paging Repetition Paging greater than or equal to that of MO
services, it is recommended that this
parameter be set to the initial PDCCH
transmission repetition count for the
highest coverage level, that is,
CellPdcchCECfg.PdcchMaxRepetitio
nCnt x
CellPdcchCECfg.PdcchTransRptCnt-
Factor.
When the coverage of paging services is
less than that of MO services, this
parameter can be set to a slightly small
value to reduce the power consumption
of UEs in RRC_IDLE mode.

6.7 Possible Issues


Fault Description
Cell status is abnormal.

Fault Handling
Step 1 Start cell status monitoring on the U2000 client to check the cell status. For detailed handling
methods when a cell outage occurs, refer to Cell Outage Detection and Recovery Feature
Parameter Description.

Step 2 View alarms on the U2000 client. If any alarm has been reported, clear the alarm according to
3900 Series Base Station Alarm Reference. The following table lists the common alarms.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 179


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 6 Engineering Guidelines for NB-IoT Basic Features

Table 6-1 Common alarm list


Alarm ID Alarm Name

ALM-26816 Licensed Feature Unusable

ALM-26818 No License Running in System

ALM-29240 Cell Unavailable

ALM-29243 Cell Capability Degraded

ALM-29245 Cell Blocked

ALM-29242 No Traffic Volume in the Cell

----End

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 180


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 7 Engineering Guidelines for Idle Mode eDRX

7 Engineering Guidelines for Idle Mode


eDRX

7.1 When to Use


This feature is recommended when the following conditions are met:

l UEs stay in the RRC_IDLE state and support this feature. The power consumption of
these UEs needs to be reduced.
l The EPC supports this feature.

7.2 Required Information


None

7.3 Planning
RF Planning
N/A

Network Planning
N/A

Hardware Planning
N/A

7.4 Deployment

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 181


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 7 Engineering Guidelines for Idle Mode eDRX

7.4.1 Requirements

Other Features
See 4.26 MLOFD-120220 Idle Mode eDRX for details.

Hardware
None

License
Feature ID Feature Name Model License Sales Unit
Control Item

MLOFD-12022 Idle Mode ML1S00IMED Idle Mode Per Cell


0 eDRX 00 eDRX(NB-IoT)

Others
l The EPC must support Idle Mode eDRX.
l UEs must support Idle Mode eDRX.
l When the eNodeB uses frequency synchronization, the eNodeB must be configured with
an IEEE1588 V2 clock to achieve time synchronization with the MME, if the MME does
not support the premature sending of paging messages to the eNodeB.
l When the eNodeB uses frequency synchronization and the MME supports the premature
sending of paging messages to the eNodeB, the eNodeB can also be configured with an
NTP clock source to achieve time synchronization with the MME.

7.4.2 Precautions
According to 3GPP TS 23.682 Release 13 (September 2016), if the eNodeB and MME use
different time standards, they must both use the GPS time to calculate the H-SFN. Currently,
the eNodeB supports only GPS time conversion. If the MME supports only the UTC, it is
recommended that the MME convert the UTC to GPS time.

3GPP TS 36.304 Release 13 (2017-03) changed the method Hash ID is calculated for UEs
using Idle Mode eDRX. HashedIdCompatSw is introduced to the
GlobalProcSwitch.UeCompatSwitch parameter to determine whether to use the new Hash ID
calculation method.
l When some NB-IoT UEs in a cell support Idle Mode eDRX specified in 3GPP Release
13 (2017-03), HashedIdCompatSw must be selected. If this option is not selected, these
NB-IoT UEs cannot normally receive paging messages when using Idle Mode eDRX.
l When this option is selected, the NB-IoT UEs that do not support Idle Mode eDRX
specified in 3GPP Release 13 (2017-03) must be upgraded. If they are not upgraded,
these NB-IoT UEs cannot normally receive paging messages when using Idle Mode
eDRX.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 182


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 7 Engineering Guidelines for Idle Mode eDRX

7.4.3 Hardware Adjustment


None

7.4.4 Data Preparation and Activation

7.4.4.1 Data Preparation


The following table describes the parameter that must be set in a CellAlgoSwitch MO to
configure the eDRX switch.

Parameter Name Parameter ID Setting Notes

NB-IoT Cell NbCellAlgoSwitch Set


Algorithm Switch IDLE_EDRX_SWITCH(IDLE_EDR
X_SWITCH) to On. Otherwise,
paging eDRX UEs will fail.

The following table describes the parameter that must be set in a GlobalProcSwitch MO to
set the UE compatibility switch.

Parameter Name Parameter ID Setting Notes

Ue Compatibility UeCompatSwitch When some NB-IoT UEs in a cell


Switch support Idle Mode eDRX specified in
3GPP Release 13 (2017-03), select
HashedIdCompatSw under this
parameter.
For details, see 7.4.2 Precautions.

The following table describes the parameter that must be set in a TASM MO to configure
HSFN synchronization parameters.

Parameter Name Parameter ID Setting Notes

Low Precision Frame LPFNSYNCSW Turn on this switch when the eNodeB
No. Synchronization uses frequency synchronization and is
Switch configured with an IEEE1588 V2 clock
to achieve time synchronization with
the MME.

CIoT Frame No. FNSYNCSW Turn on this switch when the eNodeB
Synchronization uses frequency synchronization and is
Switch configured with an NTP clock source
to achieve time synchronization with
the MME, and when Idle Mode eDRX
is required.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 183


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 7 Engineering Guidelines for Idle Mode eDRX

Parameter Name Parameter ID Setting Notes

Date DATE Set the eDRX start time to the same


value for the eNodeB and MME. If the
Time TIME eNodeB is connected to multiple
MMEs, these MMEs must be
configured with the same start time.

Leap Seconds LEAPSECONDSCHGD When the eNodeB uses frequency


Change Date ATE synchronization and is configured with
an NTP clock source to achieve time
Leap Seconds LEAPSECONDSCHGT synchronization with the MME, and
change Time IME when its connected MME uses GPS
Current CRTGPSTOUTCLEAP- time, the UTC time needs to be
LeapSeconds Offset SECONDS converted into the GPS time. When
between the UTC there is a leap second change, you need
and the GPS to set these parameters. For the leap
second adjustment value, see the
Next LeapSeconds NEXTGPSTOUTCLEA announcements of leap seconds
Offset between the PSECONDS provided by the International Earth
UTC and the GPS Rotation and Reference Systems
Service, formerly known as the Earth
Orientation Center.

7.4.4.2 Using the CME


For detailed operations, see CME-based Feature Configuration.

7.4.4.3 Using MML Commands


Clock synchronization must have been configured for the eNodeB before Idle Mode eDRX is
activated. For details about how to configure clock synchronization, see Synchronization
Feature Parameter Description.
When the eNodeB is configured to use frequency synchronization, use either of the following
methods to configure eDRX time synchronization:
l If the eNodeB is configured with an IEEE1588 V2 clock, the MME does not need to
support the premature sending of paging messages to the eNodeB. For details on how to
configure an IEEE1588 V2 clock, see Synchronization Feature Parameter Description.
l If the eNodeB is configured with an NTP clock source, that is, if the
TIMESRC.TIMESRC parameter is set to NTP, the TIMESRC.AUTOSWITCH
parameter must be set to OFF. In addition, the MME must support the premature
sending of paging messages to the eNodeB. For details on how to configure an NTP
clock source, see Time Management Feature Parameter Description.

Step 1 (Optional) When the eNodeB is configured to use frequency synchronization, configure an
IEEE1588 V2 clock for the eNodeB to achieve time synchronization with the MME, and at
the same time run the MML command SET CLKSYNCMODE to turn on Low Precision
Frame No. Synchronization Switch.
Step 2 (Optional) When the eNodeB is configured to use frequency synchronization and is
configured with an NTP clock source to achieve time synchronization with the MME, run the

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 184


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 7 Engineering Guidelines for Idle Mode eDRX

MML command SET FNSYNCTIME to set the eDRX synchronization start time and start
the eDRX frame synchronization function.

Step 3 (Optional) When the eNodeB is configured to use frequency synchronization and is
configured with an NTP clock source to achieve time synchronization with the MME, and
when its connected MME uses GPS time, run the MML command SET
LEAPSECONDSINFO to set the leap second offset between the UTC and GPS.

Step 4 Run the MML command MOD CELLALGOSWITCH to turn on


IDLE_EDRX_SWITCH(IDLE_EDRX_SWITCH).

Step 5 (Optional) When some NB-IoT UEs in a cell comply with 3GPP Release 13 (2017-03), run
the MOD GLOBALPROCSWITCH command to select HashedIdCompatSw under the Ue
Compatibility Switch parameter.

----End

7.4.4.4 MML Command Examples


//(Optional) Setting the low-precision frame No. synchronization switch
SET CLKSYNCMODE: CLKSYNCMODE=FREQ, FRAMESYNCSW=OFF, LPFNSYNCSW=ON;
//(Optional) Configuring the NB-IoT frame No. synchronization parameters
SET FNSYNCTIME: FNSYNCSW=ON, DATE=2006&09&08, TIME=10&05&20;
//(Optional) Setting the leap second offset between the UTC and GPS
SET LEAPSECONDSINFO: LEAPSECONDSCHGDATE=2017&01&07, LEAPSECONDSCHGTIME=07&59&59,
CRTGPSTOUTCLEAPSECONDS=17, NEXTGPSTOUTCLEAPSECONDS=18;
//Enabling eDRX
MOD CELLALGOSWITCH:LOCALCELLID=0, NbCellAlgoSwitch=IDLE_EDRX_SWITCH-1;
//(Optional) Turning on HashedIdCompatSw
MOD GLOBALPROCSWITCH: UeCompatSwitch=HashedIdCompatSw-1;

7.4.5 Activation Observation


Step 1 If the value of L.NB.Paging.S1.Rx.eDRX is not 0, there are eDRX paging messages that are
sent to the eNodeB over the S1 interface.

Step 2 Number of common paging times = L.NB.Paging.S1.Rx - L.NB.Paging.S1.Rx.eDRX. If


there is no paging flow control and the value of L.NB.Paging.UU.Att - (L.NB.Paging.S1.Rx
- L.NB.Paging.S1.Rx.eDRX) is not 0, there is eDRX paging message that is sent to the UE
over the Uu interface, indicating that eDRX has been enabled.

----End

7.4.6 Deactivation
This feature can be deactivated by using the CME or MML commands.

7.4.6.1 Using the CME


For detailed operations, see CME-based Feature Configuration.

7.4.6.2 Using MML Commands


Step 1 Run the MML command MOD CELLALGOSWITCH to set
IDLE_EDRX_SWITCH(IDLE_EDRX_SWITCH) to Off.

----End

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 185


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 7 Engineering Guidelines for Idle Mode eDRX

7.4.6.3 MML Command Examples


//Disabling the eDRX function of a cell
MOD CELLALGOSWITCH:LOCALCELLID=0, NbCellAlgoSwitch=IDLE_EDRX_SWITCH-0;

7.5 Performance Monitoring


None

7.6 Parameter Optimization


None

7.7 Possible Issues


Time synchronization related alarms indicate time synchronization failures, which can be
solved by following the instructions provided in the troubleshooting section for the specific
clock source in Synchronization Feature Parameter Description.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 186


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 8 Engineering Guidelines for NB-IoT Coverage Extension

8 Engineering Guidelines for NB-IoT


Coverage Extension

8.1 When to Use


NB-IoT terminals (for example, smart meters and intelligent parking systems) may be
deployed indoors or underground, which requires intensive coverage. For these coverage
enhancement scenarios, the NB-IoT Coverage Extension feature needs to be enabled.

8.2 Required Information


Before deploying NB-IoT Coverage Extension, collect information about the NB-IoT service
application scenario, network deployment mode, cell coverage radius, and RF power.

8.3 Planning
RF Planning
N/A

Network Planning
N/A

Hardware Planning
N/A

8.4 Deployment

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 187


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 8 Engineering Guidelines for NB-IoT Coverage Extension

8.4.1 Requirements

Other Features
For details, see 4.27 MLOFD-120201 NB-IoT Coverage Extension.

Hardware
None

License
Feature ID Feature Name Model License Sales Unit
Description

MLOFD-12020 NB-IoT ML1SNBCVE NB-IoT per cell


1 Coverage X00 Coverage
Extension Extension(NB-
IoT)

Others
None

8.4.2 Precautions
None

8.4.3 Hardware Adjustment


None

8.4.4 Data Preparation and Activation

8.4.4.1 Data Preparation


The following table describes the parameter that must be set in a CellAlgoSwitch MO to
configure the NB-IoT Coverage Extension feature.

Parameter Name Parameter ID Setting Notes

NB-IoT Cell NbCellAlgoSwitch If NB-IoT networks have requirements for


Algorithm Switch coverage extension, set
COVERAGE_EXTENSION_SWITCH(C
OVERAGE_EXTENSION_SWITCH) to
On.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 188


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 8 Engineering Guidelines for NB-IoT Coverage Extension

The following table describes the parameter that must be set in a eNBCellRsvdPara MO to
configure the delta-RxLevMin.

Parameter Name Parameter ID Setting Notes

Reserved U8 RsvdU8Para17 It is recommended that this parameter


Parameter 17 be set to a large value when the cell
coverage is large. Setting this
parameter to a large value increases the
difficulty for UEs to camp on other
cells.

8.4.4.2 Using the CME


For detailed operations, see CME-based Feature Configuration.

8.4.4.3 Using MML Commands


Step 1 Run the MML command MOD CELLALGOSWITCH to select
COVERAGE_EXTENSION_SWITCH(COVERAGE_EXTENSION_SWITCH) under
the NB-IoT Cell Algorithm Switch parameter.

Step 2 (Optional) If some UEs in an area of coverage level 2 cannot camp on a cell, run the MOD
ENBCELLRSVDPARA command to modify with the Reserved U8 Parameter 17
parameter specified to set the delta-RxLevMin.

----End

8.4.4.4 MML Command Examples


//Activating NB-IoT Coverage Extension
MOD CELLALGOSWITCH:LocalCellId=0,NbCellAlgoSwitch=COVERAGE_EXTENSION_SWITCH-1;
//(Optional) Configuring the delta-RxLevMin through RsvdU8Para17
MOD ENBCELLRSVDPARA: RsvdU8Para17=3;

8.4.5 Activation Observation


On the U2000, observe the following performance counters. If the values of the counters
accumulate, the NB-IoT Coverage Extension feature has been activated.

Table 8-1 Performance counters related to NB-IoT Coverage Extension

Counter ID Counter Name

1526744763 L.NB.ChMeas.NPUSCH.Repetition.16

1526744764 L.NB.ChMeas.NPUSCH.Repetition.32

1526744765 L.NB.ChMeas.NPUSCH.Repetition.64

1526744766 L.NB.ChMeas.NPUSCH.Repetition.128

1526744680 L.NB.ChMeas.NPDSCH.Repetition.16

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 189


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 8 Engineering Guidelines for NB-IoT Coverage Extension

Counter ID Counter Name

1526744681 L.NB.ChMeas.NPDSCH.Repetition.32

1526744682 L.NB.ChMeas.NPDSCH.Repetition.64

1526744683 L.NB.ChMeas.NPDSCH.Repetition.128to256

8.4.6 Deactivation

8.4.6.1 Using the CME


For detailed operations, see CME-based Feature Configuration.

8.4.6.2 Using MML Commands


Step 1 Run the MOD CELLALGOSWITCH command to set the
COVERAGE_EXTENSION_SWITCH(COVERAGE_EXTENSION_SWITCH) under
the NB-IoT Cell Algorithm Switch parameter to Off.

----End

8.4.6.3 MML Command Examples


//Deactivating NB-IoT Coverage Extension
MOD CELLALGOSWITCH:LocalCellId=0,NbCellAlgoSwitch=COVERAGE_EXTENSION_SWITCH-0;

8.5 Performance Monitoring


After NB-IoT coverage extension is used, more UEs can be accommodated by an NB-IoT
cell.

l The values of the counters related to UE quantity will increase.


Counter ID Counter Name

1526744783 L.NB.Traffic.User.Avg

1526744785 L.NB.Traffic.User.Avg.CoverageLevel1

1526744786 L.NB.Traffic.User.Max

1526744788 L.NB.Traffic.User.Max.CoverageLevel1

1526744789 L.NB.Traffic.User.Max.CoverageLevel2

l The values of the counters related to RRC connection setup will increase.
Counter ID Counter Name

1526744790 L.NB.RRC.ConnReq.Att

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 190


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 8 Engineering Guidelines for NB-IoT Coverage Extension

Counter ID Counter Name

1526744792 L.NB.RRC.ConnReq.Att.CoverageLevel1

1526744798 L.NB.RRC.ConnReq.Succ

1526744800 L.NB.RRC.ConnReq.Succ.CoverageLevel1

1526744805 L.NB.RRC.ConnSetup

1526744807 L.NB.RRC.ConnSetup.CoverageLevel1

8.6 Parameter Optimization


The following table lists the parameter that can be optimized after the NB-IoT Coverage
Extension feature is enabled. The parameter is in the Cell MO.

Parameter Parameter ID Setting Notes


Name

Coverage Level CoverageLevelT When three coverage levels are configured, it is


Type ype recommended that this parameter be set to
COVERAGE_LEVEL_0:1,
COVERAGE_LEVEL_1:1, and
COVERAGE_LEVEL_2:1.
When two coverage levels are configured, it is
recommended that this parameter be set to
COVERAGE_LEVEL_0:1,
COVERAGE_LEVEL_1:1, and
COVERAGE_LEVEL_2:0.

8.7 Possible Issues


None

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 191


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 9 Engineering Guidelines for Multi-tone

9 Engineering Guidelines for Multi-tone

9.1 When to Use


It is recommended that this feature be enabled when NB-IoT services have high requirements
for rates and power consumption, and UEs in the network are multi-tone-capable UEs.

9.2 Required Information


Before you deploy the Multi-tone feature, collect the coverage, data rate, power consumption
requirements, and UE capabilities for NB-IoT services.

9.3 Planning
RF Planning
N/A

Network Planning
N/A

Hardware Planning
N/A

9.4 Deployment

9.4.1 Requirements
Other Features
For details, see 4.28 MLOFD-120230 Multi-tone.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 192


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 9 Engineering Guidelines for Multi-tone

Hardware
The baseband board must be an LBBPd1/LBBPd2/LBBPd3/LBBPd5, a UBBPd3/UBBPd4/
UBBPd5/UBBPd6, or a UBBPe1/UBBPe2/UBBPe3/UBBPe4.

License
Feature ID Feature Name Model License Sales Unit
Control Item

MLOFD-12023 Multi-tone ML1S00MLTN Multi-tone(NB- per cell


0 00 IoT)

Others
UEs must be multi-tone-capable UEs.

9.4.2 Precautions
None

9.4.3 Hardware Adjustment


None

9.4.4 Data Preparation and Activation

9.4.4.1 Data Preparation


The following table lists the parameter that must be set in a CellAlgoSwitch MO to configure
the Multi-tone switch.

Parameter Name Parameter ID Setting Notes

NB-IoT Cell NbCellAlgoSwitch It is recommended that


Algorithm Switch MULTITONE_SWITCH(MULTIT
ONE_SWITCH) under this
parameter be set to On.

The following table lists the parameters that must be set in a CellDmrsCfg MO to configure
the demodulation reference signal (DMRS) of the cell.

Parameter Name Parameter ID Setting Notes

Local Cell ID LocalCellId N/A

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 193


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 9 Engineering Guidelines for Multi-tone

Parameter Name Parameter ID Setting Notes

DMRS Three Tone ThreeToneBaseSeq Set this parameter to a value different


Base Sequence from that of the neighboring cells to
ensure that the DMRS sequence
generated is different. Otherwise,
interference occurs.

DMRS Six Tone Base SixToneBaseSeq Set this parameter to a value different
Sequence from that of the neighboring cells to
ensure that the DMRS sequence
generated is different. Otherwise,
interference occurs.

DMRS Twelve Tone TwelveToneBaseSeq Set this parameter to a value different


Base Sequence from that of the neighboring cells to
ensure that the DMRS sequence
generated is different. Otherwise,
interference occurs.

9.4.4.2 Using the CME


For detailed operations, see CME-based Feature Configuration.

9.4.4.3 Using MML Commands


Step 1 Run the MOD CELLALGOSWITCH command to set the
MULTITONE_SWITCH(MULTITONE_SWITCH) under the NB-IoT Cell Algorithm
Switch parameter to On.

Step 2 Run the ADD CELLDMRSCFG command to ensure that the values of all parameters are
different from those of the neighboring cells. Otherwise, the DMRS sequence generated by
multi-tone-capable UEs is the same and interference occurs.

----End

9.4.4.4 MML Command Examples


//Activating Multi-tone
MOD CELLALGOSWITCH: LocalCellId=0,NbCellAlgoSwitch=MULTITONE_SWITCH-1;
//Configuring the parameters related to DMRS for NB-IoT cells
ADD CELLDMRSCFG: LocalCellId=0,ThreeToneBaseSeq=0, SixToneBaseSeq=0,
TwelveToneBaseSeq=0;

9.4.5 Activation Observation


Enable a UE to access a cell in the cell center and continuously perform UL services. After
this feature is activated, perform activation observation on the U2000 by using either of the
following methods:

Method 1: Observing the throughput

Step 1 Log in to the U2000 client.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 194


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 9 Engineering Guidelines for Multi-tone

Step 2 Choose Monitor > Signaling Trace > Signaling Trace Management.

Step 3 In the navigation tree on the left of the Signaling Trace Management window, choose LTE
> User Performance Monitoring > NB Throughput Monitoring. The NB Throughput
Monitoring dialog box is displayed.

Step 4 Select an eNodeB, and click Next.

Step 5 Set tracing parameters, and click Finish. Then, the tracing task starts.

Step 6 On the right pane of the Signaling Trace Management window, right-click the
corresponding monitoring task and select Query Result from the shortcut menu to view the
results of the Uplink MAC Throughput item.

----End

Expected result:

If the value of the uplink MAC throughput is significantly greater than that before Multi-tone
is deployed, Multi-tone has taken effect.
NOTE

The uplink MAC throughput can also be measured on the UE side. The method used to measure the
uplink MAC throughput on the UE side may differ from that on the U2000 side. Consequently, the
uplink MAC throughput measured on the UE side may slightly differ from that measured on the U2000
side. It is recommended that the uplink MAC throughput measured on the UE side be used.

Method 2: Observing the number of scheduling times

Step 1 Log in to the U2000 client.

Step 2 Choose Monitor > Signaling Trace > Signaling Trace Management.

Step 3 In the navigation tree on the left of the Signaling Trace Management window, choose LTE
> User Performance Monitoring > NB Scheduling Monitoring. The NB Scheduling
Monitoring dialog box is displayed.

Step 4 Select an eNodeB, and click Next.

Step 5 Set tracing parameters, and click Finish. Then, the tracing task starts.

Step 6 On the right pane of the Signaling Trace Management window, right-click the
corresponding monitoring task and select Query Result from the shortcut menu to view the
values of items ThreeTone ULSCH Num, SixTone ULSCH Num, and TwelveTone
ULSCH Num.

----End

Expected result:

If the value of any previous item is not zero, Multi-tone has taken effect.

9.4.6 Deactivation

9.4.6.1 Using the CME


For detailed operations, see CME-based Feature Configuration.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 195


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 9 Engineering Guidelines for Multi-tone

9.4.6.2 Using MML Commands


Run the MOD CELLALGOSWITCH command to set the
MULTITONE_SWITCH(MULTITONE_SWITCH) under the NB-IoT Cell Algorithm
Switch parameter to Off.

9.4.6.3 MML Command Examples


//Deactivating Multi-tone
MOD CELLALGOSWITCH:LocalCellId=0,NbCellAlgoSwitch=MULTITONE_SWITCH-0;

9.5 Performance Monitoring


None

9.6 Parameter Optimization


None

9.7 Possible Issues


None

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 196


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 10 Engineering Guidelines for Multiple-Antenna Reception

10 Engineering Guidelines for Multiple-


Antenna Reception

This chapter describes the engineering guidelines for the MLOFD-121202 UL 4-Antenna
Receive Diversity feature.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 197


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 10 Engineering Guidelines for Multiple-Antenna Reception

10.1 When to Use


UL 4-Antenna Receive Diversity is recommended when uplink coverage performance needs
to be improved.

10.2 Required Information


Network information needs to be collected before deploying multiple-antenna reception.

Coverage Area
l Coverage area type: dense urban areas, urban areas, suburban districts, rural areas, or
highways
l Service types and their coverage requirements
l User quantity and user distribution
l KPI requirements

Frequency Band
l Frequency band owned by the operator
l Adjacent frequency bands and frequency band distribution of other wireless
communications systems in the area, which are used to analyze interference from other
frequencies or frequency bands

Map
Whether a digital map of the coverage area is available for system performance simulation
needs to be verified.

Antenna
The following information needs to be collected:

l Antenna model
l Number of ports
l Manufacturer
l Electrical specifications, including the operating frequency band, polarization, and gains
l Mechanical specifications, including the antenna size, weight, and connector
l Antenna directivity diagram

If a new antenna is to be added, check whether space is sufficient and whether the space
meets the requirements for installing the antenna. If an old antenna is to be replaced with a
new one, check whether the installation conditions are fulfilled for the new antenna.

Feeder
Information about the feeder type and loss needs to be collected.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 198


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 10 Engineering Guidelines for Multiple-Antenna Reception

Coupler
When couplers are used, information about the coupler type and specifications such as delay
and insertion loss needs to be collected.

10.3 Planning
RF Planning
Estimate the uplink budget and capacity based on the information collected by referring to
10.2 Required Information and then complete RF planning.

Network Planning
N/A

Hardware Planning
4T4R includes multiple-antenna reception and transmission. It is recommended that hardware
for multiple-antenna reception and transmission be planned together. For details about
hardware planning, see 10.4.3 Hardware Adjustment.

10.4 Deployment

10.4.1 Requirements

Other Features
See 4.29 MLOFD-121202 UL 4-Antenna Receive Diversity.

Hardware
The eNodeB must be configured with a minimum of four receive channels and four physical
antennas.
The baseband board must be a UBBPd4/UBBPd5/UBBPd6 or a UBBPe2/UBBPe4.

License
The operator has purchased the feature license and hardware license.
l Feature license
Feature ID Feature Name Model License Sales Unit
Control Item

MLOFD-12120 UL 4-Antenna ML1S0U4 UL 4-Antenna per Cell


2 Receive ARD00 Receive
Diversity Diversity(per
Cell)(NB-IoT)

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 199


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 10 Engineering Guidelines for Multiple-Antenna Reception

l Hardware license
In uplink reception, each baseband board is equipped with two baseband receive
channels for a cell, and each RF module is equipped with two RF receive channels for a
cell. Since UL 4-Antenna Receive Diversity requires four receive channels, the operator
needs to purchase the licenses for additional two baseband receive channels and two RF
receive channels for each cell. Otherwise, cell activation fails.

Model License Control NE Sales Unit


Item

ML1S00RFRC00 RF Receive Macro eNodeB per Channel


Channel(per
Channel)(NB-IoT)

ML1S00BBRC00 BB Receive Macro eNodeB per Channel


Channel(per
Channel)(NB-IoT)

10.4.2 Precautions
If two antennas are combined to serve a cell, MLOFD-121202 UL 4-Antenna Receive
Diversity requires that all of the following conditions be met:

l The antennas have the same azimuth and downtilt angle.


l The spacing between the antennas meets the isolation requirement.
l The feeders between the antennas and RF modules have the same length and loss.

If these conditions are not met, uplink performance deteriorates.

10.4.3 Hardware Adjustment


For 2T4R and 4T4R cells, it is recommended that integrated antennas be used, with a spacing
of less than 1 wavelength between antenna arrays. The purpose is to increase the downlink
throughput of UEs with low SINR, support multiple-antenna technique evolution, reduce the
number of modules on each site, and facilitate network optimization. Also, two spatially
separated antennas can be combined to serve a cell. The purpose is to reuse existing antennas
and increase uplink throughput.

2T4R Cell (Integrated RRU)


Figure 10-1 and Figure 10-2 show the topologies for a 2T4R cell served by a 2T4R RRU. An
integrated antenna is recommended. Two combined antennas each with two ports can also be
used. If combined antennas are to be used, the feeder connection mode shown in Figure 10-2
is recommended and the installation must meet the requirements described in 11.4.2
Precautions.

In addition to a 2T4R RRU, a 4T4R RRU can be used to serve a 2T4R cell. When a 4T4R
RRU is used, channels A and B must work in TX/RX mode while channels C and D must
work in RX mode. The TX/RX mode can be set using the ADD SECTOREQM or MOD
SECTOREQM command.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 200


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 10 Engineering Guidelines for Multiple-Antenna Reception

Figure 10-1 Topology for a 2T4R cell with an integrated antenna (integrated RRU)

Figure 10-2 Topology for a 2T4R cell with combined antennas (integrated RRU)

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 201


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 10 Engineering Guidelines for Multiple-Antenna Reception

NOTE

l If a 2T4R RRU and an integrated antenna are used, the feeder connection mode shown in Figure
10-2 can also be used. As the antenna arrays of an integrated antenna are spaced about one
wavelength apart, the difference in performance between the two modes shown in Figure 10-1 and
Figure 10-2 can be ignored. However, the non-cross-connection mode shown in Figure 10-1 is
recommended to facilitate the installation.
l If a 4T4R RRU is used to serve a 2T4R cell, the topologies shown in Figure 10-7 and Figure 10-8
are recommended. The reason is to facilitate upgrade from a 2T4R cell to a 4T4R cell, avoiding a
second installation.

2T4R Cell (1T2R+1T2R; 1T2R RRUs)


Two combined 1T2R RRUs can be used to serve a 2T4R cell. Figure 10-3 and Figure 10-4
show the topologies for a 2T4R cell served by two 1T2R RRUs. An integrated antenna is
recommended. Two combined antennas each with two ports can also be used. If combined
antennas are to be used, the feeder connection mode shown in Figure 10-4 is recommended
and the installation must meet the requirements described in 11.4.2 Precautions.

Figure 10-3 Topology for a 2T4R cell with an integrated antenna (1T2R+1T2R; 1T2R RRUs)

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 202


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 10 Engineering Guidelines for Multiple-Antenna Reception

Figure 10-4 Topology for a 2T4R cell with combined antennas (1T2R+1T2R; 1T2R RRUs)

NOTE

If any TX channel is faulty, roll back the TX/RX mode of the cell from 2T4R to 1T2R.

2T4R Cell (2T2R+0T2R; 2T2R RRUs)


Two 2T2R RF modules can be combined to serve a 2T4R cell, with one RF module working
in 2T2R mode and the other in 0T2R mode.
If an integrated antenna is used, the feeder connection mode shown in Figure 10-5 is
recommended to facilitate upgrade from a 2T4R cell to a 4T4R cell, avoiding a second
installation. If combined antennas are to be used, the feeder connection mode shown in
Figure 10-6 is recommended and the installation must meet the requirements described in
11.4.2 Precautions.

NOTE

2T2R+0T2R is recommended while 1T2R+1T2R is not recommended.


l If combined antennas are used and the two transmit antenna ports for the 1T2R+1T2R cell are
provided by two RF modules, then the downlink throughput decreases if the feeder lengths and
feeder losses of the antennas are different or the azimuths or downtilt angles of the two antennas are
different.
l If multiple RATs share the same antenna system, enable the 0T2R RF module for NB-IoT and the
RRU for GSM or UMTS to share the same antenna system, so that the 2T2R RF module with a
separate antenna system can be used only for NB-IoT network planning and optimization.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 203


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 10 Engineering Guidelines for Multiple-Antenna Reception

Figure 10-5 Topology for a 2T4R cell with an integrated antenna (2T2R+0T2R, 2T2R RRUs)

Figure 10-6 Topology for a 2T4R cell with combined antennas (2T2R+0T2R, 2T2R RRUs)

4T4R Cell (Integrated RRU)


An integrated antenna is recommended. Two combined antennas each with two ports can also
be used. If combined antennas are to be used, the feeder connection mode shown in Figure
10-8 is recommended and the installation must meet the requirements described in 11.4.2
Precautions.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 204


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 10 Engineering Guidelines for Multiple-Antenna Reception

Figure 10-7 Topology for a 4T4R cell with an integrated antenna (integrated RRU)

Figure 10-8 Topology for a 4T4R cell with combined antennas (integrated RRU)

4T4R Cell (2T2R+2T2R; 2T2R RRUs)


The transmit channels of RRUs and the antennas must be connected in non-cross-connection
mode, as shown in Figure 10-9 and Figure 10-10, regardless of whether an integrated
antenna or combined antennas are used.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 205


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 10 Engineering Guidelines for Multiple-Antenna Reception

Figure 10-9 Topology for a 4T4R cell with an integrated antenna (2T2R+2T2R; 2T2R RRUs)

Figure 10-10 Topology for a 4T4R cell with combined antennas (2T2R+2T2R; 2T2R RRUs)

4T4R Cell (2T2R+2T2R; 2T4R RRUs)


The transmit channels of RRUs and the antennas must be connected in non-cross-connection
mode, as shown in Figure 10-11 and Figure 10-12, regardless of whether an integrated
antenna or combined antennas are used.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 206


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 10 Engineering Guidelines for Multiple-Antenna Reception

NOTE

If any transmit channel is faulty, roll back the TX/RX mode of the cell from 4T4R to 2T2R and then to
1T1R. That is, the TX/RX mode cannot be rolled back to 2T4R or 1T2R if the antennas are not adjusted.

Figure 10-11 Topology for a 4T4R cell with an integrated antenna (2T2R+2T2R; 2T4R
RRUs)

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 207


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 10 Engineering Guidelines for Multiple-Antenna Reception

Figure 10-12 Topology for a 4T4R cell with combined antennas (2T2R+2T2R; 2T4R RRUs)

10.4.4 Data Preparation and Feature Activation

10.4.4.1 Data Preparation

Required Data
The following table describes the parameters that must be set in a SECTOR MO to configure
a sector.

Parameter Name Parameter ID Setting Notes

Sector ID SECTORID Set this parameter to a unique value.

Sector Name SECNAME N/A

Location Name LOCATIONNAME N/A

Antenna Number ANTNUM N/A

Cabinet No. of ANT1CN Set the cabinet No. of all antennas based on
Antenna 1 the network plan.

Subrack No. of ANT1SRN Set the subrack No. of all antennas based on
Antenna 1 the network plan.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 208


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 10 Engineering Guidelines for Multiple-Antenna Reception

Parameter Name Parameter ID Setting Notes

Slot No. of Antenna ANT1SN Set the slot No. of all antennas based on the
1 network plan.

Channel No. of ANT1N Set the channel No. of all antennas based on
Antenna 1 the network plan.

Create Default CREATESECTORE N/A


Sector Equipment QM

Default Sector SECTOREQMID N/A


Equipment ID

The following table describes the parameters that must be set in a SECTOREQM MO to
configure a set of sector equipment.

Parameter Name Parameter ID Setting Notes

Sector Equipment sectorEqmId N/A


ID

Sector ID sectorId N/A

Antenna Number ANTNUM N/A

Cabinet No. of ANT1CN Set this parameter based on the network


Antenna 1 plan.

Subrack No. of ANT1SRN Set this parameter based on the network


Antenna 1 plan.

Slot No. of Antenna ANT1SN Set this parameter based on the network
1 plan.

Channel No. of ANT1N Set this parameter based on the network


Antenna 1 plan.

Antenna 1 RX/TX ANTTYPE1 Set this parameter based on the network


Mode plan.

TX Antenna 1 TXBKPMODE1 Set this parameter to MASTER(Master).


Master/Slave Mode This parameter must not be set to
SLAVE(Slave) because eNodeBs do not
support antennas working in active/standby
mode.

The following table describes the parameters that must be set in an eUCellSectorEqm MO to
bind a set of sector equipment to a cell.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 209


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 10 Engineering Guidelines for Multiple-Antenna Reception

Parameter Name Parameter ID Setting Notes

Local cell ID LocalCellId N/A

Sector equipment SectorEqmId N/A


ID

Scenario-specific Data
The following table describes the parameters that must be set in a Cell MO to configure a cell
and NB-RS port mapping.

Parameter Name Parameter ID Setting Notes

Local Cell ID LocalCellId N/A

CRS Port Number CrsPortNum Set this parameter based on the number of
downlink channels. Set this parameter to
CRS_PORT_2(2 ports) in 2T or 4T mode
and to CRS_PORT_1(1 port) in 1T mode.

Cell transmission TxRxMode Set this parameter to the same value as that
and reception mode of the SECTOR.ANTNUM parameter. For
NB-IoT cells, this parameter can only be set
to 1T1R, 1T2R, 2T2R, 2T4R, or 4T4R.

CRS Antenna Port CrsPortMap Set this parameter to 4T2P_0101


Mapping (4T2P_0101) when the Cell.TxRxMode
parameter is set to 4T4R and the
Cell.CrsPortNum parameter is set to
CRS_PORT_2(2 ports).
In LTE in-band deployment mode, if the
Cell.CrsPortNum and Cell.TxRxMode
parameters for the corresponding LTE FDD
cell are set to CRS_PORT_4(4 ports) and
4T4R, these parameters for the NB-IoT cell
must be set to CRS_PORT_2(2 ports) and
4T4R; if these parameters for the
corresponding LTE FDD cell are set to other
values, these parameters for the NB-IoT cell
must be set to the same values as those for
the LTE FDD cell.

10.4.4.2 Using the CME


For detailed operations, see CME-based Feature Configuration.

10.4.4.3 Using MML Commands


Step 1 Add a sector, a set of sector equipment (including antennas), and a cell (including its TX/RX
mode).

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 210


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 10 Engineering Guidelines for Multiple-Antenna Reception

For MLOFD-121202 UL 4-Antenna Receive Diversity, set the TX/RX mode of a cell to 2T4R
or 4T4R by referring to 10.4.4.4 MML Command Examples:
l 2T4R Cell (Integrated RRU)
l 2T4R Cell (1T2R+1T2R; 1T2R RRUs)
l 2T4R Cell (2T2R+0T2R; 2T2R RRUs)
l 4T4R Cell (Integrated RRU)
l 4T4R Cell (2T2R+2T2R; 2T2R RRUs)
l 4T4R Cell (2T2R+2T2R; 2T4R RRUs)
Step 2 Run the ACT CELL command to activate the cell.

----End

10.4.4.4 MML Command Examples

2T4R Cell (Integrated RRU)


For the topology for a 2T4R cell served by an integrated 2T4R RRU, see Figure 10-1 and
Figure 10-2 in 10.4.3 Hardware Adjustment.
ADD SECTOR:
SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT
1SN=0,ANT1N=R0A,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=FALSE;
ADD SECTOREQM:
SECTOREQMID=0,SECTORID=0,ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT1SN=0,ANT1N=R0A,ANTTYPE1=
RXTX_MODE,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANTTYPE2=RXTX_MODE,ANT3CN=0,ANT3S
RN=60,ANT3SN=0,ANT3N=R0C,ANTTYPE3=RX_MODE,ANT4CN=0,ANT4SRN=60,ANT4SN=0,ANT4N=R0D,A
NTTYPE4=RX_MODE;
ADD CELL: LOCALCELLID=0, NBCELLFLAG= TRUE, CELLNAME="
cell0",CoverageLevelType=COVERAGE_LEVEL_0-1&COVERAGE_LEVEL_1-1&COVERAGE_LEVEL_2-1,
FREQBAND=12,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=5020,ULBANDWIDTH=CELL_BW_N50,DLBANDWID
TH=CELL_BW_N50,CELLID=0,PHYCELLID=0,FDDTDDIND=CELL_FDD,ROOTSEQUENCEIDX=0,CUSTOMIZE
DBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,MU
LTIRRUCELLFLAG=BOOLEAN_FALSE,TXRXMODE=2T4R;
ADD EUCELLSECTOREQM: LOCALCELLID=0,SECTOREQMID=0;

2T4R Cell (1T2R+1T2R; 1T2R RRUs)


For the topology for a 2T4R cell served by combined 1T2R RRUs, see Figure 10-3 and
Figure 10-4 in 10.4.3 Hardware Adjustment.
Example:
ADD SECTOR:
SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT
1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANT3CN=0,ANT3SRN=61,ANT3SN=
0,ANT3N=R0A,ANT4CN=0,ANT4SRN=61,ANT4SN=0,ANT4N=R0B,CREATESECTOREQM=FALSE;
ADD SECTOREQM:
SECTOREQMID=0,SECTORID=0,ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT1SN=0,ANT1N=R0A,ANTTYPE1=
RXTX_MODE,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANTTYPE2=RX_MODE,ANT3CN=0,ANT3SRN
=61,ANT3SN=0,ANT3N=R0A,ANTTYPE3=RXTX_MODE,ANT4CN=0,ANT4SRN=61,ANT4SN=0,ANT4N=R0B,A
NTTYPE4=RX_MODE;
ADD CELL: LOCALCELLID=0, NBCELLFLAG= TRUE, CELLNAME="
cell0",CoverageLevelType=COVERAGE_LEVEL_0-1&COVERAGE_LEVEL_1-1&COVERAGE_LEVEL_2-1,
FREQBAND=12,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=5020,CELLID=0,PHYCELLID=0,FDDTDDIND=CE
LL_FDD,ROOTSEQUENCEIDX=0,CUSTOMIZEDBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=N
OT_CFG,UEPOWERMAXCFGIND=NOT_CFG,MULTIRRUCELLFLAG=BOOLEAN_FALSE,TXRXMODE=2T4R;
ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0;

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 211


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 10 Engineering Guidelines for Multiple-Antenna Reception

2T4R Cell (2T2R+0T2R; 2T2R RRUs)


For the topology for a 2T4R cell served by combined 2T2R mRFUd modules with one
working in 2T2R mode and the other in 0T2R mode, see Figure 10-5 and Figure 10-6 in
10.4.3 Hardware Adjustment.
Example:
ADD RRUCHAIN: RCN=0, TT=CHAIN, BM=COLD, HSN=3, HPN=0;
ADD RRUCHAIN: RCN=1, TT=CHAIN, BM=COLD, HSN=3, HPN=1;
ADD SUBRACK: CN=0, SRN=4, TYPE=RFU;
ADD RRU: CN=0, SRN=4, SN=0, TP=TRUNK, RCN=0, PS=0, RT=MRFU, RS=LO, RXNUM=2,
TXNUM=2;
ADD RRU: CN=0, SRN=4, SN=1, TP=TRUNK, RCN=1, PS=0, RT=MRFU, RS=LO, RXNUM=2,
TXNUM=2;
ADD SECTOR: SECTORID=0, SECNAME="huawei",LOCATIONNAME="huawei", ANTNUM=4,
ANT1CN=0, ANT1SRN=4, ANT1SN=0, ANT1N=R0A, ANT2CN=0, ANT2SRN=4, ANT2SN=0,
ANT2N=R0B, ANT3CN=0, ANT3SRN=4, ANT3SN=1, ANT3N=R0A, ANT4CN=0, ANT4SRN=4,
ANT4SN=1, ANT4N=R0B, CREATESECTOREQM=FALSE;
ADD SECTOREQM: SECTOREQMID=0, SECTORID=0, ANTNUM=4, ANT1CN=0, ANT1SRN=4,
ANT1SN=0, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0, ANT2SRN=4, ANT2SN=0,
ANT2N=R0B, ANTTYPE2=RXTX_MODE, ANT3CN=0, ANT3SRN=4, ANT3SN=1, ANT3N=R0A,
ANTTYPE3=RX_MODE, ANT4CN=0, ANT4SRN=4, ANT4SN=1, ANT4N=R0B, ANTTYPE4=RX_MODE;
ADD CELL: LOCALCELLID=0, NBCELLFLAG= TRUE, CELLNAME="
cell0",CoverageLevelType=COVERAGE_LEVEL_0-1&COVERAGE_LEVEL_1-1&COVERAGE_LEVEL_2-1,
FREQBAND=12,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=5020,UlBandWidth=CELL_BW_N25,
DlBandWidth=CELL_BW_N25, CellId=25, PhyCellId=25, FddTddInd=CELL_FDD,
RootSequenceIdx=33, CustomizedBandWidthCfgInd=NOT_CFG,
EmergencyAreaIdCfgInd=NOT_CFG, UePowerMaxCfgInd=NOT_CFG,
MultiRruCellFlag=BOOLEAN_FALSE, TxRxMode=2T4R;
ADD EUCELLSECTOREQM: LOCALCELLID=0,SECTOREQMID=0;

4T4R Cell (Integrated RRU)


For the topology for a 4T4R cell served by an integrated 4T4R RRU, see Figure 10-7 and
Figure 10-8 in 10.4.3 Hardware Adjustment.
Example:
ADD SECTOR:
SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT
1SN=0,ANT1N=R0A,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,SECTOREQMI
D=0;
ADD CELL: LOCALCELLID=0, NBCELLFLAG= TRUE, CELLNAME="
cell0",CoverageLevelType=COVERAGE_LEVEL_0-1&COVERAGE_LEVEL_1-1&COVERAGE_LEVEL_2-1,
FREQBAND=12,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=5020,ULBANDWIDTH=CELL_BW_N50,DLBANDWID
TH=CELL_BW_N50,CELLID=0,PHYCELLID=0,FDDTDDIND=CELL_FDD,ROOTSEQUENCEIDX=0,CUSTOMIZE
DBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,MU
LTIRRUCELLFLAG=BOOLEAN_FALSE,CRSPORTNUM=CRS_PORT_2,TXRXMODE=4T4R,
CRSPORTMAP=4T2P_0101;
ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0;

4T4R Cell (2T2R+2T2R; 2T2R RRUs)


For the topology for a 4T4R cell served by combined 2T2R RRUs, see Figure 10-9 and
Figure 10-10 in 10.4.3 Hardware Adjustment.
Example:
ADD SECTOR:
SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT
1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANT3CN=0,ANT3SRN=61,ANT3SN=
0,ANT3N=R0A,ANT4CN=0,ANT4SRN=61,ANT4SN=0,ANT4N=R0B,CREATESECTOREQM=TRUE,SECTOREQMI
D=0;

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 212


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 10 Engineering Guidelines for Multiple-Antenna Reception

ADD CELL: LOCALCELLID=0, NBCELLFLAG= TRUE, CELLNAME="


cell0",CoverageLevelType=COVERAGE_LEVEL_0-1&COVERAGE_LEVEL_1-1&COVERAGE_LEVEL_2-1,
FREQBAND=12,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=5020,ULBANDWIDTH=CELL_BW_N50,DLBANDWID
TH=CELL_BW_N50,CELLID=0,PHYCELLID=0,FDDTDDIND=CELL_FDD,ROOTSEQUENCEIDX=0,CUSTOMIZE
DBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,MU
LTIRRUCELLFLAG=BOOLEAN_FALSE,CRSPORTNUM=CRS_PORT_2,TXRXMODE=4T4R,
CRSPORTMAP=4T2P_0101;
ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0;

4T4R Cell (2T2R+2T2R; 2T4R RRUs)


For the topology for a 4T4R cell served by combined 2T4R RRUs, see Figure 10-11 and
Figure 10-12 in 10.4.3 Hardware Adjustment.

Example:
ADD SECTOR:
SECTORID=0,SECNAME="huawei",LOCATIONNAME="huawei",ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT
1SN=0,ANT1N=R0A,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANT3CN=0,ANT3SRN=61,ANT3SN=
0,ANT3N=R0A,ANT4CN=0,ANT4SRN=61,ANT4SN=0,ANT4N=R0B,CREATESECTOREQM=FALSE;
ADD SECTOREQM:
SECTOREQMID=0,SECTORID=0,ANTNUM=4,ANT1CN=0,ANT1SRN=60,ANT1SN=0,ANT1N=R0A,ANTTYPE1=
RXTX_MODE,ANT2CN=0,ANT2SRN=60,ANT2SN=0,ANT2N=R0B,ANTTYPE2=RXTX_MODE,ANT3CN=0,ANT3S
RN=61,ANT3SN=0,ANT3N=R0A,ANTTYPE3=RXTX_MODE,ANT4CN=0,ANT4SRN=61,ANT4SN=0,ANT4N=R0B
,ANTTYPE4=RXTX_MODE;
ADD CELL: LOCALCELLID=0, NBCELLFLAG= TRUE, CELLNAME="
cell0",CoverageLevelType=COVERAGE_LEVEL_0-1&COVERAGE_LEVEL_1-1&COVERAGE_LEVEL_2-1,
FREQBAND=12,ULEARFCNCFGIND=NOT_CFG,DLEARFCN=5020,ULBANDWIDTH=CELL_BW_N50,DLBANDWID
TH=CELL_BW_N50,CELLID=0,PHYCELLID=0,FDDTDDIND=CELL_FDD,ROOTSEQUENCEIDX=0,CUSTOMIZE
DBANDWIDTHCFGIND=NOT_CFG,EMERGENCYAREAIDCFGIND=NOT_CFG,UEPOWERMAXCFGIND=NOT_CFG,MU
LTIRRUCELLFLAG=BOOLEAN_FALSE,CRSPORTNUM=CRS_PORT_2,TXRXMODE=4T4R,
CRSPORTMAP=4T2P_0101;
ADD EUCELLSECTOREQM:LOCALCELLID=0,SECTOREQMID=0;

10.4.5 Activation Observation

Using the U2000


Step 1 Start a received signal strength indicator (RSSI) monitoring task on the U2000 client.
1. Log in to the U2000 client, and choose Monitor > Signaling Trace > Signaling Trace
Management.
2. In the navigation tree of the Signaling Trace Management tab page, choose Trace Type
> LTE > Cell Performance Monitoring and then double-click NB RSSI Monitoring.
3. In the displayed dialog box, select an eNodeB and set the Local Cell ID of the cell to be
traced. Then, click Finish to start a tracing task.

Step 2 On the Signaling Trace Management tab page, double-click the tracing task to view the NB-
IoT RSSI tracing result. Four receive antennas have been configured and UL 4-Antenna
Receive Diversity has been activated if none of the following values are N/A:
l antenna 0 RSSI(dBm)
l antenna 1 RSSI(dBm)
l antenna 2 RSSI(dBm)
l antenna 3 RSSI(dBm)

----End

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 213


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 10 Engineering Guidelines for Multiple-Antenna Reception

Using the Web LMT


Step 1 Start an NB-IoT RSSI monitoring task on the Web LMT.
1. On the Web LMT, click Monitor. In the navigation tree, choose Monitor > LTE
Monitoring.
2. Double-click Cell Performance Monitoring.
3. In the displayed Cell Performance Monitoring dialog box, select the NB-IoT RSSI
monitoring item, and specify the monitoring period, local cell ID, and cell type. Click
Submit to start the monitoring.

Step 2 View the NB-IoT RSSI monitoring results in the displayed dialog box. Four receive antennas
have been configured and UL 4-antenna receive diversity has been activated if none of the
following values are N/A:
l antenna 0 RSSI(dBm)
l antenna 1 RSSI(dBm)
l antenna 2 RSSI(dBm)
l antenna 3 RSSI(dBm)

----End

10.4.6 Deactivation

10.4.6.1 Using the CME


For detailed operations, see CME-based Feature Configuration.

10.4.6.2 Using MML Commands


Perform the following steps to deactivate multiple-antenna reception:

Step 1 Run the DEA CELL command to deactivate a cell.

Step 2 Modify a sector, a set of sector equipment (including antennas), and a cell (including its
TX/RX mode) by running the MML commands listed in 10.4.6.3 MML Command
Examples:
l Using Integrated RRUs
l Using Combined RRUs

Step 3 Run the ACT CELL command to activate the cell.

----End

10.4.6.3 MML Command Examples


Run the commands for different topologies to deactivate this feature.

Using Integrated RRUs


If the baseband board and integrated RRUs are connected as described in 10.4.3 Hardware
Adjustment, run the following commands to change the TX/RX mode, for example, to 1T1R:

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 214


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 10 Engineering Guidelines for Multiple-Antenna Reception

DEA CELL: LocalCellId=0;


MOD SECTOREQM: SECTOREQMID=0, OPMODE=DELETE, ANTNUM=3, ANT1CN=0, ANT1SRN=60,
ANT1SN=0, ANT1N=R0B, ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0C, ANT3CN=0,
ANT3SRN=60, ANT3SN=0, ANT3N=R0D;
MOD SECTOR: SECTORID=0, SECNAME="huawei", LOCATIONNAME="huawei", OPMODE=DELETE,
ANTNUM=3, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0B, ANT2CN=0, ANT2SRN=60,
ANT2SN=0, ANT2N=R0C, ANT3CN=0, ANT3SRN=60, ANT3SN=0, ANT3N=R0D;
MOD CELL: LocalCellId=0, CrsPortNum=CRS_PORT_1, TxRxMode=1T1R;
ACT CELL: LocalCellId=0;

Using Combined RRUs


If the baseband board and combined RRUs are connected as described in 10.4.3 Hardware
Adjustment, run the following commands to change the TX/RX mode, for example, to 1T1R:
DEA CELL: LocalCellId=0;
MOD SECTOREQM: SECTOREQMID=0, OPMODE=DELETE, ANTNUM=3, ANT1CN=0, ANT1SRN=60,
ANT1SN=0, ANT1N=R0B, ANT2CN=0, ANT2SRN=61, ANT2SN=0, ANT2N=R0A, ANT3CN=0,
ANT3SRN=61, ANT3SN=0, ANT3N=R0B;
MOD SECTOR: SECTORID=0, SECNAME="huawei", LOCATIONNAME="huawei", OPMODE=DELETE,
ANTNUM=3, ANT1CN=0, ANT1SRN=60, ANT1SN=0, ANT1N=R0B, ANT2CN=0, ANT2SRN=61,
ANT2SN=0, ANT2N=R0A, ANT3CN=0, ANT3SRN=61, ANT3SN=0, ANT3N=R0B;
MOD CELL: LocalCellId=0, CrsPortNum=CRS_PORT_1, TxRxMode=1T1R;
ACT CELL: LocalCellId=0;

10.5 Performance Monitoring


Method 1

Check the RSSI values of the four antennas in the cell performance tracing result by referring
to 10.4.5 Activation Observation. If none of the values are N/A, UL 4-Antenna Receive
Diversity has been activated.

Method 2

Condition: Separately enable the UL 2-Antenna Receive Diversity and UL 4-Antenna Receive
Diversity features in the same cell, and ensure that the cell bandwidth and other parameters
such as the UE transmit power remain unchanged.

Method: Calculate the distribution of uplink MCS indexes and average uplink throughput
when UL 4-Antenna Receive Diversity and UL 2-Antenna Receive Diversity are enabled.

Result: You can find that the uplink MCS index and average uplink throughput increase after
UL 4-Antenna Receive Diversity is enabled. In addition, check the uplink throughput by
performing drive tests; you can find that the uplink throughput increases.

Formula for calculating the MCS index:

(1 x L.NB.ChMeas.NPUSCH.MCS.1 + 2 x L.NB.ChMeas.NPUSCH.MCS.2 + ... + 12 x


L.NB.ChMeas.NPUSCH.MCS.12)/(L.NB.ChMeas.NPUSCH.MCS.0 +
L.NB.ChMeas.NPUSCH.MCS.1 + L.NB.ChMeas.NPUSCH.MCS.2 + ... +
L.NB.ChMeas.NPUSCH.MCS.12)

Formula for calculating the uplink throughput: L.NB.Thrp.bits.UL/L.NB.Thrp.Time.UL

NOTE

In uplink 4-antenna receive diversity, if the receive power for some antennas is imbalanced due to
interference or feeder length difference, the gains of 4-antenna receive diversity are negatively affected
compared with 2-antenna receive diversity.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 215


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 10 Engineering Guidelines for Multiple-Antenna Reception

10.6 Parameter Optimization


None

10.7 Possible Issues


Description
A TX antenna and an RX antenna are faulty, and the configured TX/RX mode becomes
unavailable.

Handling
If a TX antenna and an RX antenna are faulty, the cell using the faulty antennas falls back to
the maximum TX/RX mode supported by the number of available TX and RX antennas. The
cell falls back in the sequence of 4T4R -> 2T4R -> 2T2R -> 1T2R -> 1T1R.
The eNodeB automatically adjusts the Cell.CrsPortMap parameter to the default value to
ensure normal running. After the antennas for 4T4R become available, the eNodeB
automatically restores this parameter to its original value.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 216


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter 11 Engineering Guidelines for Multiple-Antenna
Description Transmission

11 Engineering Guidelines for Multiple-


Antenna Transmission

This chapter describes the engineering guidelines for the MLBFD-12100240 DL 4-Antenna
Transmit Diversity feature.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 217


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter 11 Engineering Guidelines for Multiple-Antenna
Description Transmission

11.1 When to Use


When the transmit power for each RRU channel is insufficient, 4T2P (P refers to NB-RS
ports) is more likely to double the transmit power than 2T2P, improving the downlink
coverage. Therefore, MLBFD-12100240 DL 4-Antenna Transmit Diversity is recommended
when the requirements for this feature are met.

11.2 Required Information


Network information needs to be collected before deploying multiple-antenna transmission.

Coverage Area
l Coverage area type: dense urban areas, urban areas, suburban districts, rural areas, or
highways
l Service types and their coverage requirements
l User quantity and user distribution
l KPI requirements

Frequency Band
l Frequency band owned by the operator
l Adjacent frequency bands and frequency band distribution of other wireless
communications systems in the area, which are used to analyze interference from other
frequencies

Map
Whether a digital map of the coverage area is available for system performance simulation
needs to be verified.

Antenna
The following information needs to be collected:
l Antenna model
l Number of ports
l Manufacturer
l Electrical specifications, including the operating frequency band, polarization, and gains
l Mechanical specifications, including the antenna size, weight, and connector
l Antenna directivity diagram
If a new antenna is to be added, check whether space is sufficient and whether the space
meets the requirements for installing the antenna. If an old antenna is to be replaced with a
new one, check whether the installation conditions are fulfilled for the new antenna.

Feeder
Information about the feeder type and loss

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 218


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter 11 Engineering Guidelines for Multiple-Antenna
Description Transmission

Coupler
When couplers are used, information about the coupler type and specifications such as delay
and insertion loss must be collected.

11.3 Planning
RF Planning
Estimate the downlink budget and capacity based on the information collected by referring to
11.2 Required Information and then complete RF planning.

Network Planning
N/A

Hardware Planning
See 11.4.3 Hardware Adjustment for details.

11.4 Deployment

11.4.1 Requirements

Other Features
See 4.24 MLBFD-12100240 DL 4-Antenna Transmit Diversity for details.

Hardware
The eNodeB must be configured with a minimum of four transmit channels and four physical
antennas.

The baseband board must be a UBBPd4/UBBPd5/UBBPd6 or a UBBPe2/UBBPe4.

License
MLBFD-12100240 DL 4-Antenna Transmit Diversity is a basic feature, and therefore is not
under license control.

In downlink transmission, since the NB-RS can be transmitted over a maximum of two
antenna ports and each baseband board is equipped with two baseband transmit channels for a
cell, operators do not need to purchase licenses for additional baseband transmit channels. DL
4-Antenna Transmit Diversity requires four RF transmit channels, and each RF module is
equipped with two RF transmit channels by default. Therefore, operators need to purchase the
licenses for two additional RF transmit channels. Otherwise, cell activation fails.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 219


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter 11 Engineering Guidelines for Multiple-Antenna
Description Transmission

Model License Control NE Sales Unit


Item

ML1S00RFTC00 RF Transmit Macro eNodeB per Channel


Channel(per
Channel)(NB-IoT)

Others
None

11.4.2 Precautions
If two antennas are combined to serve a cell, MLBFD-12100240 DL 4-Antenna Transmit
Diversity requires that all of the following conditions be met:
l The antennas have the same azimuth and downtilt.
l The spacing between the antennas meets the isolation requirement.
l The feeders between the antennas and RF modules have the same length and loss.

If these conditions are not met, downlink performance deteriorates.

11.4.3 Hardware Adjustment


See the following sub-sections in 10.4.3 Hardware Adjustment for details about hardware
installation for MLBFD-12100240 DL 4-Antenna Transmit Diversity.
l 4T4R Cell (Integrated RRU)
l 4T4R Cell (2T2R+2T2R; 2T2R RRUs)
l 4T4R Cell (2T2R+2T2R; 2T4R RRUs)

11.4.4 Data Preparation and Feature Activation

11.4.4.1 Data Preparation


The data preparation for multiple-antenna transmission is the same as that for multiple-
antenna reception. For details, see 10.4.4.1 Data Preparation.

11.4.4.2 Using the CME


For detailed operations, see CME-based Feature Configuration.

11.4.4.3 Using MML Commands


Step 1 Add a sector, a set of sector equipment (including antennas), and a cell (including its TX/RX
mode).

The TX/RX mode of a cell using DL 4-Antenna Transmit Diversity is 4T4R, and DL 4-
Antenna Transmit Diversity is configured together with UL 4-Antenna Receive Diversity. For
details, see 10.4.4.4 MML Command Examples.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 220


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter 11 Engineering Guidelines for Multiple-Antenna
Description Transmission

l 4T4R Cell (Integrated RRU)


l 4T4R Cell (2T2R+2T2R; 2T2R RRUs)
l 4T4R Cell (2T2R+2T2R; 2T4R RRUs)

Step 2 Run the ACT CELL command to activate the cell.

----End

11.4.5 Activation Observation

Using the U2000


Step 1 Log in to the U2000 client, and choose Monitor > Signaling Trace > Signaling Trace
Management.

Step 2 In the navigation tree of the Signaling Trace Management tab page, choose Base Station
Device and Transport > RRU/RFU/BRU Output Power Monitoring. The
RRU/RFU/BRU Output Power Monitoring dialog box is displayed.

Step 3 View the RF output power monitoring results.


l In standalone or LTE guard band deployment mode, if the difference between the
displayed and configured output power of the four NB-IoT channels is less than 0.5 dB,
four transmit antennas have been configured. This feature has taken effect.
l In LTE in-band deployment mode, if the difference between the displayed and
configured output power of the four LTE FDD channels is less than 0.5 dB, four transmit
antennas have been configured. This feature has taken effect.

----End

Using the Web LMT


Step 1 Start an RF output power monitoring task on the Web LMT.
1. In the LMT main window, click Monitor.
2. In the navigation tree, choose Common Monitoring > RRU/RFU Output Power
Monitoring.
3. Set related parameters in the RRU/RFU Output Power Monitoring dialog box.

Step 2 View the RF output power monitoring results.


l In standalone or LTE guard band deployment mode, if the difference between the
displayed and configured output power of the four NB-IoT channels is less than 0.5 dB,
four transmit antennas have been configured. This feature has taken effect.
l In LTE in-band deployment mode, if the difference between the displayed and
configured output power of the four LTE FDD channels is less than 0.5 dB, four transmit
antennas have been configured. This feature has taken effect.

----End

11.4.6 Deactivation

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 221


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter 11 Engineering Guidelines for Multiple-Antenna
Description Transmission

11.4.6.1 Using the CME


For detailed operations, see CME-based Feature Configuration.

11.4.6.2 Using MML Commands


Perform the following steps to deactivate multiple-antenna transmission:

Step 1 Run the DEA CELL command to deactivate the cell.

Step 2 Modify a sector, a set of sector equipment (including antennas), and a cell (including its
TX/RX mode). The configurations of DL 4-Antenna Transmit Diversity is modified together
with those of UL 4-Antenna Receive Diversity. For details about the involved commands, see
the following sub-sections in 10.4.6.3 MML Command Examples:
l Using Integrated RRUs
l Using Combined RRUs

Step 3 Run the ACT CELL command to activate the cell again.

----End

11.5 Performance Monitoring


Condition: Operate under the same conditions such as the same cell, bandwidth, and UE
transmit power.

Method: Calculate the distribution of downlink MCS indexes and average downlink
throughput when DL 2-Antenna Transmit Diversity and DL 4-Antenna Transmit Diversity are
enabled.

Result: You can find that the downlink MCS index and average downlink throughput increase
after DL 4-Antenna Transmit Diversity is enabled. In addition, check the downlink throughput
by performing drive tests; you can find that the downlink throughput increases.

Formula for calculating the MCS index: (1 x L.NB.ChMeas.NPDSCH.MCS.1 + 2 x


L.NB.ChMeas.NPDSCH.MCS.2 + ... + 12 x L.NB.ChMeas.NPDSCH.MCS.12) /
(L.NB.ChMeas.NPDSCH.MCS.0 + L.NB.ChMeas.NPDSCH.MCS.1 +
L.NB.ChMeas.NPDSCH.MCS.2 + ... + L.NB.ChMeas.NPDSCH.MCS.12)

Formula for calculating the downlink throughput: L.NB.Thrp.bits.DL/L.NB.Thrp.Time.DL

11.6 Parameter Optimization


None

11.7 Possible Issues


Description
A TX antenna and an RX antenna are faulty, and the configured TX/RX mode becomes
unavailable.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 222


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter 11 Engineering Guidelines for Multiple-Antenna
Description Transmission

Handling
If a TX antenna and an RX antenna are faulty, the cell using the faulty antennas falls back to
the maximum TX/RX mode supported by the number of available TX and RX antennas. The
cell falls back in the sequence of 4T4R -> 2T4R -> 2T2R -> 1T2R -> 1T1R.
The eNodeB automatically adjusts the Cell.CrsPortMap parameter to the default value to
ensure normal running. After the antennas for 4T4R become available, the eNodeB
automatically restores this parameter to its original value.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 223


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

12 Parameters

Table 12-1 Parameters


MO Parame MML Feature Feature Description
ter ID Comma ID Name
nd

CellChP AntOutp MOD LBFD-0 Dynami Meaning: Indicates the transmit power for the entire
wrCfg utPwr CELLC 02016 / c channel bandwidth at each antenna connector. If the
HPWRC TDLBF Downlin AntRsPwrSwitch option of the RepeaterSwitch
FG D-00201 k Power parameter is selected, this parameter value is used to
LST 6 Allocati calculate the reference signal (RS) power to be
CELLC on delivered in system information block type 2 (SIB2).
HPWRC GUI Value Range: 20~40
FG Unit: W
Actual Value Range: 20~40
Default Value: 20

CellAlg Repeater MOD LBFD-0 Dynami Meaning: Indicates the type of reference signal (RS)
oSwitch Switch CELLA 02016 c power to be delivered in system information block
LGOSW Downlin type 2 (SIB2). If the AntRsPwrSwitch option is
ITCH k Power selected, the RS power calculated based on the
LST Allocati transmit power of the antenna port and output power
CELLA on rate is delivered in SIB2. If the AntRsPwrSwitch
LGOSW option is deselected, the RS power specified by the
ITCH ReferenceSignalPwr parameter is delivered in SIB2.
This parameter applies only to LTE FDD and NB-IoT.
GUI Value Range:
AntRsPwrSwitch(AntRsPwrSwitch)
Unit: None
Actual Value Range: AntRsPwrSwitch
Default Value: AntRsPwrSwitch:Off

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 224


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

eNBCell RsvdU1 MOD None None Meaning:


RsvdPar 6Para8 ENBCE Indicates the U16 reserved parameter 8 that is
a LLRSV reserved for future requirements.
DPARA
LST Note on parameter replacement: Reserved parameters
ENBCE are temporarily used in patch versions and will be
LLRSV replaced with new parameters. For example, the ID of
DPARA a new parameter can signify the parameter function.
Therefore, avoid using this parameter. This parameter
applies only to LTE FDD and LTE TDD.
GUI Value Range: 0~65535
Unit: None
Actual Value Range: 0~65535
Default Value: 0

eNBCell RsvdU8 MOD None None Meaning:


RsvdPar Para22 ENBCE Indicates the U8 reserved parameter 22 that is
a LLRSV reserved for future requirements.
DPARA
LST Note on parameter replacement: Reserved parameters
ENBCE are temporarily used in patch versions and will be
LLRSV replaced with new parameters. For example, the ID of
DPARA a new parameter can signify the parameter function.
Therefore, avoid using this parameter. This parameter
applies only to LTE FDD and LTE TDD.
GUI Value Range: 0~255
Unit: None
Actual Value Range: 0~255
Default Value: 0

TIMES AUTOS SET None None Meaning: Indicates whether to enable automatic time
RC WITCH TIMES source switchover. When the switch is turned on, the
RC system switches over the time source when time
DSP synchronization fails. When the switch is turned off,
TIMES the system does not switch over the time source.
RC GUI Value Range: OFF(Off), ON(On)
LST Unit: None
TIMES Actual Value Range: OFF, ON
RC
Default Value: ON(On)

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 225


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

ENodeB FddFra MOD MRFD- FDD Meaning: Indicates the offset of the start time of a cell
FrameO meOffse ENODE 101231 and frame against a reference clock source. This offset
ffset t BFRAM MRFD- TDD applies to all LTE FDD cells served by an eNodeB.
EOFFS 101222 Carrier This parameter applies only to LTE FDD and NB-IoT.
ET Aggrega GUI Value Range: 0~261120,275943~307200
LST tion(TD
D) Unit: Ts
ENODE
BFRAM FDD Actual Value Range: 0~261120,275943~307200
EOFFS and Default Value: 0
ET TDD
Carrier
Aggrega
tion(FD
D)

CellFra FrameO ADD None None Meaning: Indicates the offset of the start time of a cell
meOffse ffset CELLF frame against a reference clock source.
t RAME GUI Value Range: 0~261120,275943~307200
OFFSE
T Unit: Ts

MOD Actual Value Range: 0~261120,275943~307200


CELLF Default Value: 0
RAME
OFFSE
T
LST
CELLF
RAME
OFFSE
T

eNBCell RsvdU8 MOD None None Meaning:


RsvdPar Para17 ENBCE Indicates the U8 reserved parameter 17 that is
a LLRSV reserved for future requirements.
DPARA
LST Note on parameter replacement: Reserved parameters
ENBCE are temporarily used in patch versions and will be
LLRSV replaced with new parameters. For example, the ID of
DPARA a new parameter can signify the parameter function.
Therefore, avoid using this parameter. This parameter
applies only to LTE FDD and LTE TDD.
GUI Value Range: 0~255
Unit: None
Actual Value Range: 0~255
Default Value: 0

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 226


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

CellAlg UlSchE MOD LOFD-1 Traffic Meaning:


oSwitch xtSwitch CELLA 10205 / Model Indicates whether to enable extended functions of
LGOSW TDLOF Based uplink scheduling.
ITCH D-11022 Perform
LST 7 ance UlPacketLenAwareSchSw: Indicates whether to
CELLA LOFD-0 Optimiz optimize uplink packet length awareness performance.
LGOSW 01048 / ation Packet length awareness performance is optimized in
ITCH TDLOF TTI the uplink only if this option is selected. This option
D-00104 Bundlin applies only to LTE FDD and LTE TDD.
8 g EnhExtQCITtiBundlingSwitch: Indicates whether to
LOFD-0 VoIP enable TTI bundling for push-to-talk (PTT) services
01016 / Semi- with QCI 65, QCI 66, or enhanced extended QCIs. If
TDLOF persisten this option is selected, the number of transmission
D-00101 t opportunities increases within the air interface delay
6 Scheduli budget of PTT services, and uplink coverage is
LOFD-0 ng improved. This option applies only to LTE FDD and
81218 / Enhance LTE TDD.
TDLOF d EnhExtQCISpsSchSwitch: Indicates whether to
D-08121 Extende enable semi-persistent scheduling during talk spurts of
5 d QCI PTT services with QCI 65, QCI 66, or enhanced
LBFD-0 Dynami extended QCIs. If this option is selected, semi-
0101502 c persistent scheduling is applied. If this option is
/ Scheduli deselected, dynamic scheduling is applied. This option
TDLBF ng applies only to LTE FDD and LTE TDD.
D-00101 Basic
502 UlVoipRbRsvSwitch: Indicates whether to reserve
Scheduli PUSCH RBs for UEs running voice services in the
TDLBF ng uplink. This option does not take effect if the uplink
D-00202 AMC cell bandwidth is less than 5 MHz. This option applies
5/ only to LTE FDD.
LBFD-0 MCPTT
02025 Voice UlThpEnhSwitch: Indicates whether to enable the
Manage enhanced uplink throughput improvement function. If
TDLBF ment
D-00100 this option is selected, the eNodeB calculates the
6 PUCCH overhead based on the actual number of RBs
occupied by the PUCCH when the number of UEs is
TDLOF small in the cell, which improves the uplink
D-12110 throughput. If this option is deselected, the eNodeB
6 calculates the PUCCH overhead based on the current
PUCCH resource configuration. This option applies
only to LTE TDD.
UlDataFitterRbCalcSwitch: Indicates whether to
enable the algorithm of RB calculation based on
uplink data volume matching. The algorithm takes
effect only when this option and the SchedulerCtrlPo-
werSwitch option of the UlSchSwitch parameter are
selected. When this algorithm takes effect, the number
of required RBs is estimated based on the UE

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 227


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

capability and the data volume to be scheduled. If this


algorithm does not take effect, the number of required
RBs is estimated based on the UE spectral efficiency
and the data volume to be scheduled. This option
applies only to LTE FDD.
UlFssOptForAttach: Indicates whether to perform
uplink frequency selective scheduling based on the
value of Interf in the network entry phase. If this
option is selected, uplink frequency selective
scheduling is performed based on the interference
level during network access. If this option is
deselected, uplink frequency selective scheduling is
performed based on the SINR during network access.
This option can be selected when the
ULFSSAlgoSwitch option of the UlSchSwitch
parameter is selected. This option applies only to LTE
TDD.
SrbProbeSchSwitch: Indicates whether to proactively
schedule uplink signaling. If this option is selected,
the eNodeB triggers proactive scheduling of uplink
signaling for once when the eNodeB determines that
data correctly scheduled in the downlink is control-
plane signaling that requires the uplink signaling
feedback and does not receive the feedback within a
specified period of time. This option applies only to
LTE FDD and LTE TDD.
UlSchCtrlPwrUserSetOptSw: Indicates whether to
enable the algorithm of selecting UE sets for the
scheduler-controlled power function. This algorithm
takes effect only when this option and the
SchedulerCtrlPowerSwitch option of the UlSchSwitch
parameter are selected. When this algorithm takes
effect, pre-scheduled UEs of a lower priority are not
included in the UE set selected by the scheduler.
When this algorithm does not take effect, all pre-
scheduled UEs are included in the UE set selected by
the scheduler. This option applies only to LTE FDD
and LTE TDD.
UlPttSchOptSwitch: Indicates whether to enable
dynamic scheduling for PTT services with QCI 65,
QCI 66, or enhanced extended QCIs. If this option is
selected, for PTT service UEs that are scheduled
dynamically in the uplink, the eNodeB triggers uplink
dynamic scheduling when the scheduling interval is
greater than the uplink voice scheduling interval
threshold. This ensures timely uplink scheduling for

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 228


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

voice service users in heavy traffic scenarios,


preventing packet discarding upon the timeout of
PDCP packet discarding timer. If this option is
deselected, the eNodeB does not trigger uplink
dynamic scheduling for PTT services in the preceding
scenario. This option applies only to LTE FDD and
LTE TDD.
UlPttDataSizeEstSwitch: Indicates whether to
estimate uplink traffic volume for dynamic scheduling
of PTT services with QCI 65, QCI 66, or enhanced
extended QCIs. If this option is selected, the eNodeB
estimates uplink traffic volume for dynamic
scheduling of PTT services, reducing the packet delay
and packet loss rate and increasing voice quality of
PTT services. If this option is deselected, the function
does not take effect. This option applies only to LTE
FDD and LTE TDD.
EnhancedSchForSparseSwitch: Indicates whether ping
packets are subject to the preallocation bandwidth
percentage restriction and whether to change the
method of calculating the number of RBs to be
allocated for SR-based dynamic scheduling of ping
packets. If this option is selected, ping packets are not
subject to the preallocation bandwidth percentage
restriction, and the number of RBs to be allocated for
SR-based dynamic scheduling of ping packets is
calculated based on the size of the ping packets. If this
option is deselected, ping packets are subject to the
preallocation bandwidth percentage restriction, and
the number of RBs to be allocated for SR-based
dynamic scheduling of ping packets is calculated
based on the average spectral efficiency. For FDD,
this option indicates only whether ping packets are
subject to the preallocation bandwidth percentage
restriction. This option applies only to LTE FDD and
LTE TDD.
UlSigSrSchDateLenAdapt: Indicates whether to
enable data amount adaptation for SR-based
scheduling of uplink signaling. The adaptation is
enabled only if this option is selected. When the
adaptation is enabled, the eNodeB adaptively allocates
the amount of to-be-scheduled data and the number of
RBs based on the signaling identification result in SR-
based scheduling of uplink signaling. This option
applies only to LTE FDD and LTE TDD.
UlFssWindSearchDirRandSw: Indicates whether to
randomize the search window direction in uplink

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 229


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

frequency selective scheduling. The randomization is


enabled only if this option is selected. When the
randomization is enabled, the eNodeB randomly
specifies a search window direction for a cell in
frequency selective scheduling. This option applies
only to LTE FDD.
UlCellCenterMCSOptSwitch: Indicates whether to
optimize MCSs for uplink transmission by UEs in the
cell center. The optimization is enabled only if this
option is selected. When the optimization is enabled,
the throughput of full-buffer services of UEs in or
near the cell center increases. This option applies only
to LTE FDD and LTE TDD.
PuschSchEscPucchSwitch: If this option is selected,
PUCCH interference coordination takes effect,
reducing PUCCH interference. This option applies
only to LTE TDD.
HarqMcsOptSwitch: If this option is selected, the
instantaneous DMRS measurement value can be used
to select an MCS index for retransmission. This option
applies only to LTE TDD.
PreambleSchEnhSwitch: If this option is selected, the
preamble scheduling and demodulation success rates
increase. If this option is deselected, the preamble
scheduling and demodulation success rates do not
increase. If this option is deselected in NB-IoT
scenarios, the maximum backoff index included in
MAC PDU is 12. If this option is selected in NB-IoT
scenarios, the maximum backoff index included in
MAC PDU is 7. This accommodates certain UEs not
supporting higher backoff indexes.
UlPAMCSwitch: If this option is selected, AMC
maximizing the uplink perceived throughput takes
effect and AMC adjustment and MCS index selection
are performed in an optimized way. This option
applies only to LTE FDD and LTE TDD.
UlMultiClusterSwitch: Indicates whether to enable the
uplink multi-cluster function. This function is enabled
only when the option is selected. Uplink
discontinuous resource allocation is supported when
this function is enabled. This option applies only to
LTE FDD.
GUI Value Range: UlPacketLenAwar-
eSchSw(UlPacketLenAwareSchSw),
EnhExtQCITtiBundlingSwitch(EnhExtQCITtiBund-

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 230


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

lingSwitch), EnhExtQCISpsSchS-
witch(EnhExtQCISpsSchSwitch),
UlVoipRbRsvSwitch(UlVoipRbRsvSwitch),
UlThpEnhSwitch(UlThpEnhSwitch),
UlDataFitterRbCalcSwitch(UlDataFitterRbCalcS-
witch), UlFssOptForAttach(UlFssOptForAttach),
SrbProbeSchSwitch(SrbProbeSchSwitch),
UlSchCtrlPwrUserSetOptSw(UlSchCtrlPwrUserSe-
tOptSw), UlPttSchOptSwitch(UlPttSchOptSwitch),
UlPttDataSizeEstSwitch(UlPttDataSizeEstSwitch),
EnhancedSchForSparseSwitch(EnhancedSchForSpar-
seSwitch), UlSigSrSchDateLenA-
dapt(UlSigSrSchDateLenAdapt), UlFssWindSearch-
DirRandSw(UlFssWindSearchDirRandSw),
UlCellCenterMCSOptSwitch(UlCellCenterMCSOptS-
witch), PuschSchEscPucchS-
witch(PuschSchEscPucchSwitch),
HarqMcsOptSwitch(HarqMcsOptSwitch),
PreambleSchEnhSwitch(PreambleSchEnhSwitch),
UlPAMCSwitch(UlPAMCSwitch), UlMultiClusterS-
witch(UlMultiClusterSwitch)
Unit: None
Actual Value Range: UlPacketLenAwareSchSw,
EnhExtQCITtiBundlingSwitch, EnhExtQCISpsSchS-
witch, UlVoipRbRsvSwitch, UlThpEnhSwitch,
UlDataFitterRbCalcSwitch, UlFssOptForAttach,
SrbProbeSchSwitch, UlSchCtrlPwrUserSetOptSw,
UlPttSchOptSwitch, UlPttDataSizeEstSwitch,
EnhancedSchForSparseSwitch, UlSigSrSchDateLe-
nAdapt, UlFssWindSearchDirRandSw,
UlCellCenterMCSOptSwitch, PuschSchEscPucchS-
witch, HarqMcsOptSwitch, PreambleSchEnhSwitch,
UlPAMCSwitch, UlMultiClusterSwitch
Default Value: UlPacketLenAwareSchSw:Off,
EnhExtQCITtiBundlingSwitch:Off,
EnhExtQCISpsSchSwitch:Off,
UlVoipRbRsvSwitch:Off, UlThpEnhSwitch:Off,
UlDataFitterRbCalcSwitch:On,
UlFssOptForAttach:Off, SrbProbeSchSwitch:Off,
UlSchCtrlPwrUserSetOptSw:Off,
UlPttSchOptSwitch:Off, UlPttDataSizeEstSwitch:Off,
EnhancedSchForSparseSwitch:Off,
UlSigSrSchDateLenAdapt:Off, UlFssWindSearchDir-
RandSw:Off, UlCellCenterMCSOptSwitch:Off,
PuschSchEscPucchSwitch:Off,
HarqMcsOptSwitch:Off, PreambleSchEnhSwitch:Off,
UlPAMCSwitch:Off, UlMultiClusterSwitch:Off

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 231


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

CellAlg UlSchS MOD LOFD-0 VoIP Meaning:


oSwitch witch CELLA 01016 / Semi- Indicates whether to enable uplink scheduling
LGOSW TDLOF persisten functions for the cell.
ITCH D-00101 t
LST 6 Scheduli SpsSchSwitch: Indicates whether to enable semi-
CELLA LOFD-0 ng persistent scheduling during talk spurts of VoLTE
LGOSW 01048 / TTI services. If this option is selected, semi-persistent
ITCH TDLOF Bundlin scheduling is applied. If this option is deselected,
D-00104 g dynamic scheduling is applied. This option applies
8 only to LTE FDD and LTE TDD.
Dynami
LBFD-0 c SinrAdjustSwitch: Indicates whether to adjust the
0101502 Scheduli measured SINR based on ACK/NACK messages in
/ ng the UL hybrid automatic repeat request (HARQ)
TDLBF Basic processes. This option applies only to LTE FDD and
D-00101 Scheduli LTE TDD.
502 ng PreAllocationSwitch: Indicates whether to enable
LBFD-0 MBR>G preallocation in the uplink. If this option is selected:
02025 / BR (1) If the SmartPreAllocationSwitch option is
TDLBF Configu deselected and a UE is in the discontinuous reception
D-00202 ration (DRX) state, preallocation is disabled for the UE in
5 the uplink; (2) If the SmartPreAllocationSwitch option
UL 2x2
LBFD-0 is deselected and the UE is not in the DRX state,
MU-
70102 / preallocation is enabled for the UE in the uplink; (3) If
MIMO
TDLBF the SmartPreAllocationSwitch option is selected and
D-07010 UL 2x4 the SmartPreAllocationDuration parameter value is
2 MU- greater than 0, smart preallocation is enabled for the
MIMO UE in the uplink; (4) If the SmartPreAllocationSwitch
LOFD-0
AMC option is selected and the SmartPreAllocationDuration
01002
parameter value is 0, preallocation is disabled for the
LOFD-0 Uplink UE in the uplink. If this option is deselected,
01058 / Coverag preallocation is disabled for the UE in the uplink. If
TDLOF e bearer-level preallocation or bearer-level smart
D-00105 Improve preallocation is enabled for a QCI, cell-level
8 ment for preallocation and cell-level smart preallocation do not
Video apply to UEs with the QCI. This option applies only to
LBFD-0
01006 / Enhance LTE FDD and LTE TDD.
TDLBF d UL
Frequen UlVmimoSwitch: Indicates whether to enable multi-
D-00100
cy user MIMO (MU-MIMO) in the uplink. If this option
6
Selectiv is selected, the eNodeB performs MU-MIMO pairing
LOFD-1 e among UEs based on related principles. UEs forming
20205 Scheduli a pair transmit data using the same time-frequency
LBFD-0 ng resources, which improves the system throughput and
60102 spectral efficiency. This option applies only to LTE
UL FDD and LTE TDD.
TDLEO 2x64
FD-121 MU- TtiBundlingSwitch: Indicates whether to enable
608 MIMO transmission time interval (TTI) bundling. If TTI

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 232


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

TDLEO UL bundling is enabled, more transmission opportunities


FD-121 4x64 are available to UEs within the delay budget for
609 MU- VoLTE services on the Uu interface, thereby
TDLEO MIMO improving uplink coverage. This option applies only
FD-121 UL to LTE FDD and LTE TDD.
610 8x64 ImIcSwitch: Indicates whether to enable the
MU- intermodulation (IM) interference cancellation for
MIMO UEs. When data is transmitted in both the uplink and
downlink, uplink signals generate two IM components
symmetrically beside the Direct Current (DC)
subcarrier on the downlink receive channel due to the
nonlinearity of the UE receive channel. If this option
is selected, IM component elimination is performed
for UEs. If this option is deselected, IM component
elimination is not performed for UEs. This option
applies only to LTE FDD cells working on frequency
band 20. This option applies only to LTE FDD.
SmartPreAllocationSwitch: Indicates whether to
enable uplink smart preallocation when the
PreAllocationSwitch option is selected. If both the
PreAllocationSwitch and this option are selected and
the SmartPreAllocationDuration parameter in the
CellPreallocGroup MO is set to a value greater than 0,
uplink smart preallocation is enabled. Otherwise,
uplink smart preallocation is disabled. This option
applies only to LTE FDD and LTE TDD.
PuschDtxSwitch: Indicates whether the eNodeB uses
the PUSCH discontinuous transmission (DTX)
detection result during uplink scheduling. If this
option is selected for an LTE FDD cell, the eNodeB
determines whether to perform adaptive
retransmission, and also adjusts the CCE aggregation
level of the PDCCH carrying downlink control
information (DCI) format 0 based on the PUSCH
DTX detection result during uplink scheduling. If an
LTE FDD cell is established on an LBBPc, this option
takes effect only if the cell uses less than four RX
antennas and normal cyclic prefix (CP) in the uplink
and the SrsCfgInd parameter in the SRSCfg MO is set
to BOOLEAN_TRUE(True). Note that the LBBPc
does not support PUSCH DTX detection for VMIMO
UEs. For an LTE TDD cell, this option takes effect
only when the uplink-downlink subframe
configuration is set to SA2 or SA5. If this option takes
effect, the eNodeB adjusts the CCE aggregation level
based on the PUSCH DTX detection results. Note that
LTE TDD cells established on LBBPc boards do not

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 233


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

support PUSCH DTX detection. This option applies


only to LTE FDD and LTE TDD.

UlIblerAdjustSwitch: Indicates whether to enable the


uplink IBLER adjustment algorithm. If this option is
selected, the target IBLER is adjusted for UEs based
on the channel quality and fluctuation to increase the
cell throughput. This option applies only to LTE FDD
and LTE TDD. If this option is selected independently
for FDD cells with the UlTargetIBlerAdaptType
option deselected, the algorithm does not take effect.

UlEnhancedFssSwitch: Indicates whether to enable


uplink load-based enhanced frequency selective
scheduling. This option applies only to LTE FDD.

UlIicsAlgoSwitch: Indicates whether to enable the


uplink interference-intensity-based coordinated
scheduling (UL IICS) algorithm. If this option is
selected, interference can be reduced based on
accurate detection of user attributes and scheduling
resource coordination, increasing the cell edge
throughput. This option applies only to LTE TDD.

UlEnhancedSrSchSwitch: Indicates whether uplink re-


scheduling is performed only when the On Duration
timer for the DRX long cycle starts. Uplink re-
scheduling is required if the number of HARQ
retransmissions for a scheduling request (SR) reaches
the maximum value but the scheduling still fails. If
this option is selected, uplink re-scheduling is
performed only when the On Duration timer for the
DRX long cycle starts. If this option is deselected,
uplink re-scheduling is performed immediately when
the number of HARQ retransmissions for SR reaches
the maximum value but the scheduling still fails. It is
recommended that this option be selected for live
networks. This option applies only to LTE FDD and
LTE TDD.

SchedulerCtrlPowerSwitch: Indicates whether the


uplink scheduler performs scheduling without
considering power control restrictions. If this option is
selected, the uplink scheduler performs scheduling
without considering power control restrictions,
ensuring full utilization of the transmit power for all
UEs. If this option is deselected, the uplink scheduler
considers power control restrictions while performing
scheduling. In this case, the transmit power cannot be
fully used for UEs at the cell edge or between the cell

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 234


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

edge and cell center. This option applies only to LTE


FDD and LTE TDD.

UlMinGbrSwitch: Indicates whether to ensure uplink


minimum guaranteed bit rate (GBR). If this option is
selected, the minimum GBR of non-GBR services is
ensured by increasing the scheduling priority of UEs
whose non-GBR service rates are lower than the
minimum GBR. This option applies only to LTE FDD
and LTE TDD.

UlMbrCtrlSwitch: Indicates whether to enable uplink


scheduling based on the maximum bit rate (MBR) and
guaranteed bit rate (GBR) on the GBR bearer. If this
option is selected, the eNodeB performs uplink
scheduling on GBR bearers based on the MBR and
GBR. If this option is deselected, the eNodeB
performs uplink scheduling on GBR bearers based
only on the GBR. This option applies only to LTE
FDD and LTE TDD.

MbrUlSchSwitch: Indicates whether the eNodeB


performs uplink scheduling based on the MBR. If this
option is selected, the eNodeB prioritizes UEs based
on the MBRs during uplink scheduling. This option
applies only to LTE TDD.

UeAmbrUlSchSwitch: Indicates whether the eNodeB


performs uplink scheduling based on the aggregate
maximum bit rate (AMBR) of UEs. If this option is
selected, the eNodeB prioritizes UEs based on the
AMBRs of UEs during uplink scheduling. This option
applies only to LTE TDD.

UlEnhancedDopplerSwitch: Indicates whether to


enable enhanced uplink scheduling based on mobility
speed estimation. If this option is selected, enhanced
uplink scheduling based on mobility speed estimation
is enabled. In enhanced uplink scheduling based on
mobility speed estimation, the eNodeB uses Doppler
measurement results to identify low-speed UEs to
further improve uplink performance of low-speed
UEs. If this option is deselected, enhanced uplink
scheduling based on mobility speed is disabled.
Enhanced uplink scheduling based on mobility speed
takes effect only when the DopMeasLevel parameter
is set to CLASS_1(CLASS_1) and the
UlEnhancedDopplerSwitch option is selected. This
option does not apply to cells established on LBBPc
boards. This option applies only to LTE FDD.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 235


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

UlRaUserSchOptSw: Indicates whether the eNodeB


raises the scheduling priority of UEs sending uplink
access signaling, including MSG5 and the RRC
Connection Reconfiguration Complete message. If
this option is selected, the eNodeB raises the
scheduling priority of UEs sending uplink access
signaling. If this option is deselected, the eNodeB
does not raise the scheduling priority of UEs sending
uplink access signaling. In NB-IoT scenarios with air
interface resource congestion, this option restricts the
number of preambles to perform flow control on UEs
accessing the cell.
UlLast2RetransSchOptSwitch: Indicates whether to
optimize the scheduling policy for the last two
retransmissions. If this option is selected, the
scheduling policy is optimized for the last two
retransmissions. If the UE transmit power is not
limited, adaptive retransmission is used, and the
number of RBs increases in the last two
retransmissions to increase the receive success rate of
the last two retransmissions and decrease uplink
RBLER. If this option is deselected, the scheduling
policy is not optimized for the last two
retransmissions. This option applies only to LTE FDD
and LTE TDD.
UlInterfFssSwitch: Indicates whether to enable
interference-based uplink frequency-selective
scheduling. This option applies only to LTE FDD.
UlSmallRBSpectralEffOptSw: Indicates whether to
improve the spectral efficiency of small RBs in the
uplink. If this option is selected, the spectral efficiency
of small RBs in the uplink is optimized, ensuring that
the transmission block size calculated based on
optimized spectral efficiency is not less than the traffic
volume to be scheduled. If this option is deselected,
the spectral efficiency of small RBs in the uplink is
not optimized. This option applies only to LTE FDD
and LTE TDD.
PuschUsePucchRbSwitch: Indicates whether PUCCH
RBs can be occupied by the PUSCH. In scenarios
with a single user: If this option is selected, PUCCH
RBs can be occupied by the PUSCH; if this option is
deselected, PUCCH RBs cannot be occupied by the
PUSCH. In scenarios with multiple users, PUCCH
RBs cannot be occupied by the PUSCH regardless of
the setting of this option. This option applies only to
LTE FDD and LTE TDD.

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 236


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

PuschDtxSchOptSwitch: If this option is selected, the


eNodeB determines whether to perform adaptive
retransmission based on the PUSCH DTX detection
result during uplink scheduling. This option takes
effect only when the uplink-downlink subframe
configuration SA2 or SA5 is used. If an LTE TDD cell
is established on an LBBPc, PUSCH DTX detection is
not supported. This option applies only to LTE TDD.
PrachRbReuseSwitch: If this option is selected, the
PUSCH and PRACH transmissions can use the same
resource. If this option is deselected, the PUSCH and
PRACH transmissions cannot use the same resource.
This option applies only to LTE FDD and LTE TDD.
ULFSSAlgoswitch: If this option is deselected, uplink
frequency-selective scheduling is disabled. If this
option is selected, uplink frequency-selective
scheduling is enabled. This option applies only to LTE
TDD.
SrSchDataAdptSw: Indicates whether to enable data
amount adaptation in SR-based scheduling. Data
amount adaptation in SR-based scheduling is enabled
only when this option is selected. This option applies
only to LTE FDD.
UlFssUserThdStSwitch: If this option is selected, the
UE number threshold is optimized for uplink
frequency selective scheduling. If this option is
deselected, the UE number threshold is not optimized
for uplink frequency selective scheduling. This option
applies only to LTE FDD and LTE TDD.
HighOrderVMIMOSwitch: Indicates whether to
enable high order VMIMO. If this option is selected,
high order VMIMO is enabled. If this option is
deselected, high order VMIMO is disabled. This
option applies only to LTE TDD.
VMIMOReduceMCSRiseRBSwitch: Indicates
whether VMIMO pairing is performed for UEs whose
MCS index is reduced to increase the number of RBs.
If this option is selected, VMIMO is performed for
UEs whose MCS index is reduced to increase the
number of RBs. If this option is deselected, VMIMO
is not performed for UEs whose MCS index is
reduced to increase the number of RBs. This option
applies only to LTE TDD.
VoLTEUeVmimoSwitch: Indicates whether VMIMO
pairing is performed for VoLTE UEs. If this option is

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 237


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

selected, VMIMO pairing is performed for VoLTE


UEs. If this option is deselected, VMIMO pairing is
not performed for VoLTE UEs. This option applies
only to LTE TDD.
TtiBundlingForVideoSwitch: If this option is selected,
TTI bundling is enabled for UEs running video
services in weak coverage areas, improving video
service coverage at the cell edge. If this option is
deselected, TTI bundling is disabled for UEs running
video services in weak coverage areas. This option
applies only to LTE FDD.
GUI Value Range: SpsSchSwitch(SpsSchSwitch),
SinrAdjustSwitch(SinrAdjustSwitch),
PreAllocationSwitch(PreAllocationSwitch),
UlVmimoSwitch(UlVmimoSwitch),
TtiBundlingSwitch(TtiBundlingSwitch),
ImIcSwitch(ImIcSwitch), SmartPreAllocationS-
witch(SmartPreAllocationSwitch),
PuschDtxSwitch(PuschDtxSwitch),
UlIblerAdjustSwitch(UlIblerAdjustSwitch),
UlEnhancedFssSwitch(UlEnhancedFssSwitch),
UlEnhancedSrSchSwitch(UlEnhancedSrSchSwitch),
SchedulerCtrlPowerSwitch(SchedulerCtrlPowerS-
witch), UlIicsAlgoSwitch(UlIicsAlgoSwitch),
UlMinGbrSwitch(UlMinGbrSwitch),
UlMbrCtrlSwitch(UlMbrCtrlSwitch),
MbrUlSchSwitch(MbrUlSchSwitch),
UeAmbrUlSchSwitch(UeAmbrUlSchSwitch),
UlEnhancedDopplerSwitch(UlEnhancedDopplerS-
witch), UlRaUserSchOptSw(UlRaUserSchOptSw),
UlLast2RetransSchOptSwitch(UlLast2RetransSchOpt
Switch), UlInterfFssSwitch(UlInterfFssSwitch),
UlSmallRBSpectralEffOptSw(UlSmallRBSpectralEf-
ficiencyOptSw), PuschUsePucchRbS-
witch(PuschUsePucchRbSwitch), PuschDtxSchOptS-
witch(PuschDtxSchOptSwitch),
ULFSSAlgoSwitch(ULFSSAlgoSwitch),
PrachRbReuseSwitch(PrachRbReuseSwitch),
SrSchDataAdptSw(SrSchDataAdptSw),
UlFssUserThdStSwitch(UlFssUserThdStSwitch),
HighOrderVMIMOSwitch(HighOrderVMIMOS-
witch), VMIMOReduceMCSRiseRBS-
witch(VMIMOReduceMCSRiseRBSwitch),
VoLTEUeVmimoSwitch(VoLTEUeVmimoSwitch),
TtiBundlingForVideoSwitch(TtiBundlingForVideoS-
witch)
Unit: None

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 238


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

Actual Value Range: SpsSchSwitch,


SinrAdjustSwitch, PreAllocationSwitch,
UlVmimoSwitch, TtiBundlingSwitch, ImIcSwitch,
SmartPreAllocationSwitch, PuschDtxSwitch,
UlIblerAdjustSwitch, UlEnhancedFssSwitch,
UlEnhancedSrSchSwitch, SchedulerCtrlPowerSwitch,
UlIicsAlgoSwitch, UlMinGbrSwitch,
UlMbrCtrlSwitch, MbrUlSchSwitch,
UeAmbrUlSchSwitch, UlEnhancedDopplerSwitch,
UlRaUserSchOptSw, UlLast2RetransSchOptSwitch,
UlInterfFssSwitch, UlSmallRBSpectralEffOptSw,
PuschUsePucchRbSwitch, PuschDtxSchOptSwitch,
ULFSSAlgoSwitch, PrachRbReuseSwitch,
SrSchDataAdptSw, UlFssUserThdStSwitch,
HighOrderVMIMOSwitch, VMIMOReduceMCSRi-
seRBSwitch, VoLTEUeVmimoSwitch,
TtiBundlingForVideoSwitch
Default Value: SpsSchSwitch:Off,
SinrAdjustSwitch:On, PreAllocationSwitch:On,
UlVmimoSwitch:Off, TtiBundlingSwitch:Off,
ImIcSwitch:Off, SmartPreAllocationSwitch:On,
PuschDtxSwitch:On, UlIblerAdjustSwitch:Off,
UlEnhancedFssSwitch:On, UlEnhancedSrSchS-
witch:On, SchedulerCtrlPowerSwitch:Off,
UlIicsAlgoSwitch:Off, UlMinGbrSwitch:Off,
UlMbrCtrlSwitch:Off, MbrUlSchSwitch:Off,
UeAmbrUlSchSwitch:Off, UlEnhancedDopplerS-
witch:On, UlRaUserSchOptSw:Off,
UlLast2RetransSchOptSwitch:On,
UlInterfFssSwitch:Off, UlSmallRBSpectralEf-
fOptSw:Off, PuschUsePucchRbSwitch:Off,
PuschDtxSchOptSwitch:Off, ULFSSAlgoSwitch:On,
PrachRbReuseSwitch:Off, SrSchDataAdptSw:On,
UlFssUserThdStSwitch:Off, HighOrderVMIMOS-
witch:Off, VMIMOReduceMCSRiseRBSwitch:Off,
VoLTEUeVmimoSwitch:Off, TtiBundlingForVideoS-
witch:Off

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 239


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

CellAlg MTCCo MOD LEOFD- eNodeB Meaning:


oSwitch ngContr CELLA 120303 Supporti Indicates whether to enable congestion control
olSwitch LGOSW MLBFD ng MTC algorithms for machine type communication (MTC)
ITCH -121002 Congesti and NB-IoT UEs.
LST 43 on
CELLA Control EABAlgoSwitch: Indicates whether to enable
MLOFD extended access barring (EAB). When EAB is
LGOSW -121280 eMTC
ITCH enabled, an eNodeB implements access class control
/ Introduc for EAB-applicable UEs if the E-UTRAN or EPC is
TDLEO tion overloaded. EAB is enabled only if this option is
FD-121 selected. When MtcSwitch is set to ON, you are
611 advised to select the EABAlgoSwitch option to reduce
the impact caused by a large number of MTC UEs.
ExtendedwaittimeSwitch: Indicates whether an
eNodeB includes the extendedWaitTime parameter
into the message sent to UEs when the UEs' RRC
connection setup requests are rejected due to EPC
overload or their RRC connections are released.
If this option is selected, an eNodeB includes the
extendedWaitTime parameter into the message sent to
UEs in either of the following conditions:
- After receiving an overload message from the MME,
the eNodeB rejects the RRC connection setup requests
with the cause value DelayTolerant or releases the
RRC connections with the cause value DelayTolerant.
- The eNodeB releases the RRC connections when the
NB-IoT cell is congested.
If this option is deselected, the eNodeB does not
include the extendedWaitTime parameter into the
message sent to UEs in the preceding situations.
GUI Value Range:
EABAlgoSwitch(EABAlgoSwitch),
ExtendedwaittimeSwitch(ExtendedwaittimeSwitch)
Unit: None
Actual Value Range: EABAlgoSwitch,
ExtendedwaittimeSwitch
Default Value: EABAlgoSwitch:Off,
ExtendedwaittimeSwitch:Off

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 240


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

NbCell UuMess MOD MLBFD RRC Meaning: Indicates the timer governing the period the
DlSchC ageWaiti NBCEL -120002 Connect eNodeB waits for a Uu response message from a UE.
EAlgo ngTimer LDLSC 28 ion If the timer expires, the eNodeB initiates to release the
HCEAL Manage UE. If this parameter is set to 0, the
GO ment UuMessageWaitingTimer parameter in the
LST ENodeBConnStateTimer MO, rather than this
NBCEL parameter, takes effect. If this parameter is set to 1 to
LDLSC 200, this parameter takes effect. This parameter
HCEAL applies only to NB-IoT.
GO GUI Value Range: 0~200
Unit: s
Actual Value Range: 0~200
Default Value: 0

PCCHC MaxNu MOD MLBFD Paging Meaning: Indicates the maximum number of
fg mRepeti PCCHC -120002 repetitions in the NPDCCH common search space for
tionForP FG 31 NB-IoT paging. For details about this parameter, see
aging LST descriptions of the npdcch-NumRepetitionPaging IE
PCCHC in 3GPP TS 36.331. When this parameter is set to
FG NULL, npdcch-NumRepetitionPaging uses the
CellPdcchCECfg.PdcchMaxRepetitionCnt parameter
value corresponding to the maximum coverage level
by default. When this parameter is not set to NULL,
npdcch-NumRepetitionPaging uses the
MaxNumRepetitionForPaging parameter value. This
parameter applies only to NB-IoT.
GUI Value Range: REP_1(REP_1), REP_2(REP_2),
REP_4(REP_4), REP_8(REP_8), REP_16(REP_16),
REP_32(REP_32), REP_64(REP_64),
REP_128(REP_128), REP_256(REP_256),
REP_512(REP_512), REP_1024(REP_1024),
REP_2048(REP_2048), NULL(Invalid)
Unit: None
Actual Value Range: REP_1, REP_2, REP_4, REP_8,
REP_16, REP_32, REP_64, REP_128, REP_256,
REP_512, REP_1024, REP_2048, NULL
Default Value: NULL(Invalid)

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 241


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

CellRac PrachSta MOD MLBFD Random Meaning: Indicates the PRACH start time. When
hCECfg rtTime CELLR -120002 Access PrachStartTimeCfgInd is set to CFG, this parameter
ACHCE 30 Procedu can be set to different values for different coverage
CFG re levels of a cell. However, the PRACH start time
LST interval between coverage levels must not be less than
CELLR 40 ms. Otherwise, cells fail to be activated. This
ACHCE parameter applies only to NB-IoT.
CFG GUI Value Range: SF8(SF8), SF16(SF16),
SF32(SF32), SF64(SF64), SF128(SF128),
SF256(SF256), SF512(SF512), SF1024(SF1024)
Unit: None
Actual Value Range: SF8, SF16, SF32, SF64, SF128,
SF256, SF512, SF1024
Default Value: SF8(SF8)

RACHC PrachSta MOD MLBFD Random Meaning: Indicates whether PRACH start time is
fg rtTimeC RACHC -120002 Access configurable. When this parameter is set to
fgInd FG 30 NOT_CFG, PRACH start time is not configurable.
LST The PRACH start time for coverage level 0 is always
RACHC 8 ms. The PRACH start time for coverage level 1 and
FG that for coverage level 2 are determined based on the
following factors: the sum of the PRACH start time
and PRACH time length for the previous coverage
level, and the restriction that the PRACH start time
interval between coverage levels is not less than 40
ms. When this parameter is set to CFG, the PRACH
start time for each coverage level is configurable. The
PRACH start time interval between coverage levels
must not be less than 40 ms. Otherwise, cells fail to be
activated. This parameter applies only to NB-IoT.
GUI Value Range: NOT_CFG(Not configure),
CFG(Configure)
Unit: None
Actual Value Range: NOT_CFG, CFG
Default Value: NOT_CFG(Not configure)

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 242


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

CellRac PrachDe MOD MLBFD Random Meaning: Indicates the PRACH detection threshold.
hCECfg tectionT CELLR -120002 Access LEVEL_0 indicates the lower detection threshold and
hld ACHCE 30 LEVEL_3 indicates the upper detection
CFG threshold.When PrachRepetitionCount is set to
LST REP_1(REP_1), REP_2(REP_2), REP_4(REP_4), or
CELLR REP_128(REP_128), this parameter takes effect as it
ACHCE is set to LEVEL_3. This parameter applies only to
CFG NB-IoT.
GUI Value Range: LEVEL_0(LEVEL_0),
LEVEL_1(LEVEL_1), LEVEL_2(LEVEL_2),
LEVEL_3(LEVEL_3)
Unit: None
Actual Value Range: LEVEL_0, LEVEL_1,
LEVEL_2, LEVEL_3
Default Value: LEVEL_3(LEVEL_3)

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 243


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

GlobalP UeCom MOD LBFD-0 Termina Meaning:


rocSwitc patSwitc GLOBA 81103/ l Indicates whether to enable compatibility optimization
h h LPROC TDLBF Awarene functions for UEs to control differentiated handling of
SWITC D-08110 ss abnormal UEs.
H 3 Differen
LST tiation AbnormalUeHandleSwitch: Indicates whether to
GLOBA enable handling of abnormal UEs. This function is
LPROC enabled only if this option is selected. This option
SWITC applies only to LTE FDD and LTE TDD.
H UltraFlashCsfbComOptSw: Indicates whether to
enable the optimization of UE incompatibility risks in
ultra-flash CSFB. If this option is selected, an eNodeB
triggers an ultra-flash CSFB procedure based on the
private IE "SRVCC based eCSFB operation possible"
that the MME sends to the eNodeB. If this option is
deselected, the eNodeB does not trigger an ultra-flash
CSFB procedure based on this IE. This option applies
only to LTE FDD and LTE TDD.
ForbidR8R9UeAccessB41Sw: indicates whether to
forbid R8 and R9 UEs to access frequencies ranging
from 2575 MHz to 2595 MHz within band 41. Such
access is forbidden only if this option is selected. It is
recommended that this option be selected when there
are UEs reporting that they support band 41 but
actually do not support frequencies ranging from 2575
MHz to 2595 MHz within band 41. This option
applies only to LTE FDD and LTE TDD.
MOUeCompatEffectSw: Indicates whether the
UeCompat MO takes effect. If this option is selected,
the UeCompat MO but not the UeCompatOpt MO
takes effect. If this option is deselected, the
UeCompatOpt MO but not the UeCompat MO takes
effect. This option applies only to LTE FDD and LTE
TDD.
PerExtendBitSw: Indicates whether to encode
extended bit indicators for Uu messages if extended
IEs specified by later 3GPP releases are not included
in Uu message code. If this option is selected,
extended bit indicators are not encoded. If this option
is deselected, extended bit indicators are encoded.
This option applies only to LTE FDD and LTE TDD.
InterFddTddMeasComOptSw: Indicates whether to
enable compatibility optimization on inter-duplex-
mode measurements for UEs. If a UE can send inter-
duplex-mode measurement reports but actually cannot
perform inter-duplex-mode measurements, this UE

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 244


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

incompatibility issue may cause an increase in the


service drop rate. If this option is selected, the
eNodeB is not allowed to deliver inter-duplex-mode
measurement configurations to such UEs. This option
applies only to LTE FDD and LTE TDD.
NbR13CompatSw: Indicates whether to enable error
correction of 3GPP Release 13 on NB-IoT-related
functions. For details about the functions of this
option, see 3GPP TS 36.211, 36.213, 36.302, 36.331,
36.212, 36.321, 36.300, 36.302, 36.403, 36.322, and
36.323. eNodeBs can interconnect with UEs
complying with 3GPP Release 13 published in
February 2017 only after this option is selected. This
option applies only to NB-IoT.
HashedIdCompatSw: Indicates whether the eNodeB
calculates Hashed ID for eDRX paging using the
method defined in 3GPP TS 36.304 published in
February 2017. When this option is selected, the
eNodeB calculates Hashed ID for eDRX paging using
the protocol-defined method. When this option is
deselected, the eNodeB calculates Hashed ID for
eDRX paging using the Huawei proprietary method.
GUI Value Range: AbnormalUeHandleS-
witch(AbnormalUeHandleSwitch), UltraFlashCsfbCo-
mOptSw(UltraFlashCsfbComOptSw),
ForbidR8R9UeAccessB41Sw(ForbidR8R9UeAccess
B41Sw),
MOUeCompatEffectSw( MOUeCompatEffectSw),
PerExtendBitSw(PerExtendBitSw),
InterFddTddMeasComOptSw(InterFddTddMeasCo-
mOptSw), NbR13CompatSw(NbR13CompatSw),
HashedIdCompatSw(HashedIdCompatSw)
Unit: None
Actual Value Range: AbnormalUeHandleSwitch,
UltraFlashCsfbComOptSw,
ForbidR8R9UeAccessB41Sw,
MOUeCompatEffectSw, PerExtendBitSw,
InterFddTddMeasComOptSw, NbR13CompatSw,
HashedIdCompatSw
Default Value: AbnormalUeHandleSwitch:Off,
UltraFlashCsfbComOptSw:Off,
ForbidR8R9UeAccessB41Sw:Off,
MOUeCompatEffectSw:Off, PerExtendBitSw:Off,
InterFddTddMeasComOptSw:Off,
NbR13CompatSw:Off, HashedIdCompatSw:Off

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 245


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

CellAlg NbCell MOD MLOFD Idle Meaning:


oSwitch AlgoSwi CELLA -120220 Mode Indicates the NB-IoT cell-level algorithm switch.
tch LGOSW MLOFD eDRX IDLE_EDRX_SWITCH: Indicates whether eDRX
ITCH -120201 NB-IoT paging is supported. eDRX paging can be delivered in
LST MLOFD Coverag the local cell only when this option is selected. This
CELLA -120230 e parameter applies only to NB-IoT.
LGOSW Extensio
ITCH MLBFD n COVERAGE_EXTENSION_SWITCH: Indicates
-120002 whether to enable the NB-IoT cell coverage extension
29 Multi- function. When this option is selected, the NB-IoT
tone cell coverage extension function is supported, and the
MLBFD
-120002 Broadca eNodeB supports coverage extension during
01 st of scheduling.When this option is deselected, common
System coverage is supported, which means that coverage
Informat extension cannot be achieved.This parameter applies
ion only to NB-IoT.
3GPP MULTITONE_SWITCH: Indicates whether to enable
R13 the NB-IoT Multi-tone feature. For uplink data
NB-IoT transmission, when this option is selected, an eNodeB
Specific can allocate multiple subcarriers at a time to a multi-
ations tone-capable UE. When this option is deselected, the
Multi-tone feature is not supported, and the eNodeB
allocates only one subcarrier at a time to a multi-tone-
capable UE for uplink data transmission. This option
applies only to NB-IoT.
DCI_SF_REP_NUM_COMP_SWITCH: Indicates
whether the value of the "DCI subframe repetition
number" field in the search space table complies with
the value defined in section 16.6 of 3GPP TS 36.213
released in September 2016. If this option is selected,
the value of the "DCI subframe repetition number"
field complies with the protocol-defined value. If this
option is deselected, the value of the "DCI subframe
repetition number" field uses a Huawei-defined value.
This option applies only to NB-IoT.
SI_OFFSET_ADAPTIVE_CFG_SWITCH: Indicates
the adaptive configuration of the NB-IoT system
information (SI) frame offset. If this option is selected,
adaptive configuration takes effect for NB-IoT SI
frame offset. If this option is deselected, adaptive
configuration does not take effect for NB-IoT SI
frame offset, and the si-RadioFrameOffset IE is not
delivered. This option applies only to NB-IoT.
GUI Value Range:
IDLE_EDRX_SWITCH(IDLE_EDRX_SWITCH),
COVERAGE_EXTENSION_SWITCH(COVERAGE
_EXTENSION_SWITCH),

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 246


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

MULTITONE_SWITCH(MULTITONE_SWITCH),
DCI_SF_REP_NUM_COMP_SWITCH(DCI_SF_RE
P_NUM_COMP_SWITCH),
SI_OFFSET_ADAPTIVE_CFG_SWITCH(SI_OFFS
ET_ADAPTIVE_CFG_SWITCH)
Unit: None
Actual Value Range: IDLE_EDRX_SWITCH,
COVERAGE_EXTENSION_SWITCH,
MULTITONE_SWITCH,
DCI_SF_REP_NUM_COMP_SWITCH,
SI_OFFSET_ADAPTIVE_CFG_SWITCH
Default Value: IDLE_EDRX_SWITCH:Off,
COVERAGE_EXTENSION_SWITCH:Off,
MULTITONE_SWITCH:Off,
DCI_SF_REP_NUM_COMP_SWITCH:Off,
SI_OFFSET_ADAPTIVE_CFG_SWITCH:Off

TASM CLKSY SET MRFD- BTS Meaning: Indicates the clock synchronization mode of
NCMO CLKSY 210501 Clock a BS, which can be frequency synchronization or time
DE NCMO synchronization.
DE GUI Value Range: FREQ(FREQ), TIME(TIME),
DSP HYBRID(HYBRID)
CLKST Unit: None
AT
Actual Value Range: FREQ, TIME, HYBRID
LST
CLKSY Default Value: FREQ(FREQ)
NCMO
DE

TASM LPFNS SET None None Meaning: Indicates the switch of low-precision frame
YNCS CLKSY No. synchronization. When this switch is turned on,
W NCMO the frame No. synchronization function is enabled,
DE and the SFN and HSFN are automatically aligned
DSP after the system clock is locked. When this switch is
CLKST turned off, the frame No. synchronization function is
AT disabled. This switch applies to NB-IoT and eDRX.
LST GUI Value Range: OFF(OFF), ON(ON)
CLKSY Unit: None
NCMO Actual Value Range: OFF, ON
DE
Default Value: OFF(OFF)

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 247


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

Prb Deploy ADD MLBFD Standalo Meaning: Indicates the NB-IoT PRB deployment
Mode PRB -120001 ne mode. STAND_ALONE indicates that out-of-band
MOD 01 Deploy LTE spectrum resources are used to deploy NB-IoT
PRB MLBFD ment PRB. GUARD_BAND indicates that NB-IoT PRB is
-120001 LTE deployed on the LTE guardband. IN_BAND indicates
LST that PRB is deployed on the LTE RB resources, which
PRB 02 Guardba
nd means that less RBs are available for LTE. This
MLBFD parameter applies only to NB-IoT.
-120001 Deploy
03 ment GUI Value Range:
LTE In- STAND_ALONE(STAND_ALONE),
band GUARD_BAND(GUARD_BAND),
Deploy IN_BAND(IN_BAND)
ment Unit: None
Actual Value Range: STAND_ALONE,
GUARD_BAND, IN_BAND
Default Value: STAND_ALONE(STAND_ALONE)

Prb DlFreqO ADD MLBFD Standalo Meaning: Indicates the frequency offset of the PRB
ffset PRB -120001 ne downlink central frequency to the downlink
MOD 01 Deploy frequency. For details, see 3GPP TS 36.101. This
PRB MLBFD ment parameter applies only to NB-IoT.
LST -120001 LTE GUI Value Range: NEG_2(NEG_2),
PRB 02 Guardba NEG_1(NEG_1), NEG_0DOT5(NEG_0DOT5),
MLBFD nd POS_0(POS_0), POS_1(POS_1)
-120001 Deploy Unit: None
03 ment
Actual Value Range: NEG_2, NEG_1, NEG_0DOT5,
LTE In- POS_0, POS_1
band
Deploy Default Value: NEG_0DOT5(NEG_0DOT5)
ment

Prb LteBand ADD MLBFD LTE Meaning: Indicates the LTE cell bandwidth. This
Width PRB -120001 Guardba parameter takes effect only when DeployMode is set
MOD 02 nd to GUARD_BAND. This parameter applies only to
PRB Deploy NB-IoT.
ment GUI Value Range:
LST
PRB LTE_SYSTEM_BW_10M(LTE_SYSTEM_BW_10M
),
LTE_SYSTEM_BW_15M(LTE_SYSTEM_BW_15M
),
LTE_SYSTEM_BW_20M(LTE_SYSTEM_BW_20M
)
Unit: None
Actual Value Range: LTE_SYSTEM_BW_10M,
LTE_SYSTEM_BW_15M, LTE_SYSTEM_BW_20M
Default Value: None

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 248


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

Prb LteDlEa ADD MLBFD LTE Meaning: Indicates the downlink EARFCN of an LTE
rfcn PRB -120001 Guardba cell. This parameter takes effect only when
MOD 02 nd DeployMode is set to GUARD_BAND. This
PRB Deploy parameter applies only to NB-IoT.
ment GUI Value Range:
LST
PRB 0~68485,255144~256143,260894~262143
Unit: None
Actual Value Range:
0~68485,255144~256143,260894~262143
Default Value: None

Prb LteCellI ADD MLBFD LTE In- Meaning: Indicates the LTE cell ID. This parameter
d PRB -120001 band takes effect only when DeployMode is set to
MOD 03 Deploy IN_BAND. This parameter applies only to NB-IoT.
PRB ment GUI Value Range: 0~255
LST Unit: None
PRB Actual Value Range: 0~255
Default Value: None

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 249


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

CellAlg PucchAl MOD LBFD-0 Physical Meaning:


oSwitch goSwitc CELLA 02003 / Channel PucchSwitch: Indicates whether to enable PUCCH
h LGOSW TDLBF Manage resource adjustment. If this option is selected, the
ITCH D-00200 ment eNodeB initiates PUCCH resource adjustment when
LST 3 Breathin PUCCH resources are insufficient or excessive. If this
CELLA LEOFD- g Pilot option is deselected, the eNodeB cannot adjust
LGOSW 111306 PUCCH PUCCH resource.
ITCH LOFD-0 Flexible PucchFlexCfgSwitch: Indicates whether to enable
01093 Configu flexible PUCCH configuration. This option does not
LOFD-0 ration take effect if an LBBPc is used or the cell bandwidth
02015 RACH is 1.4 MHz or 3 MHz. If flexible PUCCH
Optimiz configuration is enabled, frequency-domain uplink
ation ICIC and uplink frequency hopping scheduling do not
take effect. If this option is selected, the same number
of RBs (specified by the PucchExtendedRBNum
parameter in the PUCCHCfg MO) are separately
added to both ends of the uplink band allocated for the
PUCCH. The total number of extension PUCCH RBs
equals the PucchExtendedRBNum parameter value
multiplied by 2, and the extension RBs can be used for
PUSCH scheduling. If this option is deselected,
flexible PUCCH configuration is disabled. This option
applies only to LTE FDD.
Dl2CCAckResShareSw: Indicates whether to enable
PUCCH ACK channel resource sharing for downlink
2CC CA. The eNodeB divides the ACK code channel
resources on the PCC for downlink 2CC CA into four
groups. If this option is deselected, CA UEs scheduled
on each SCC associated with this PCC are allowed to
use the ACK channel resources in only one group. If
this option is selected, CA UEs scheduled on each
SCC associated with this PCC can use the ACK
channel resources in any group. This option applies
only to LTE FDD and LTE TDD.
SCCAckResourceCfgSW: Indicates whether to enable
SCC ACK resource configuration. If this option is
selected, the eNodeB controls the maximum number
of RBs that can be used by PUCCH format 3 and the
maximum number of code channels that can be used
by SCC ACKs in 2CC CA scenarios according to the
settings of the Format3RBNum and
Max2CCAckChNum parameters in the PUCCHCfg
MO, respectively. If this option is deselected, the
eNodeB controls the maximum number of RBs that
can be used by PUCCH format 3 and the maximum
number of code channels that can be used by SCC

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 250


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

ACKs in 2CC CA scenarios. This option applies only


to LTE FDD and LTE TDD.
EmtcAckModeSw: Indicates the ACK feedback mode
of eMTC UEs. If this option is deselected, eMTC UEs
always send ACKs in bundling mode. If this option is
selected, eMTC UEs always send ACKs in
multiplexing mode when the eNodeB sends all the csi-
NumRepetitionCE, mPDCCH-NumRepetition, and
pucch-NumRepetitionCE-format1 IEs only once. If
the eNodeB repeatedly sends any of these IEs, eMTC
UEs send ACKs in bundling mode. This option is
deselected by default. This option applies only to LTE
TDD.
GUI Value Range: PucchSwitch(PucchSwitch),
PucchFlexCfgSwitch(PucchFlexCfgSwitch),
Dl2CCAckResShareSw(Dl2CCAckResShareSw),
SCCAckResourceCfgSw(SCCAckResourceCfgSw),
EmtcAckModeSw(EmtcAckModeSw)
Unit: None
Actual Value Range: PucchSwitch,
PucchFlexCfgSwitch, Dl2CCAckResShareSw,
SCCAckResourceCfgSw, EmtcAckModeSw
Default Value: PucchSwitch:On,
PucchFlexCfgSwitch:Off,
Dl2CCAckResShareSw:On,
SCCAckResourceCfgSw:Off, EmtcAckModeSw:Off

CellRbR RbRsvT ADD MLBFD LTE In- Meaning: Indicates whether the PRBs to be reserved
eserve ype CELLR -120001 band at the physical layer are uplink or downlink ones. This
BRESE 03 Deploy parameter applies only to LTE FDD and NB-IoT.
RVE ment GUI Value Range:
MOD UPLINK_MODE(UPLINK_MODE),
CELLR DOWNLINK_MODE(DOWNLINK_MODE)
BRESE Unit: None
RVE
Actual Value Range: UPLINK_MODE,
LST DOWNLINK_MODE
CELLR
BRESE Default Value: None
RVE

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 251


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

CellRbR RbRsv ADD MLBFD LTE In- Meaning: Indicates the purpose for reserving RBs.
eserve Mode CELLR -120001 band The value NB_RESERVED indicates that the
BRESE 03 Deploy specified RBs are reserved as a guardband in the
RVE ment uplink or to reduce the interference between LTE and
MOD NB-IoT cells in the downlink. The value
CELLR NB_DEPLOYMENT indicates that the specified RBs
BRESE are to be used for deploying NB-IoT. The value
RVE RB_MASKING indicates that the specified RBs are to
be used for manual RB masking. The value
LST RB_MASKING_WITH_SRS indicates that the
CELLR specified RBs are to be used for manual RB and SRS
BRESE masking. This parameter applies only to LTE FDD
RVE and NB-IoT.
GUI Value Range:
NB_RESERVED(NB_RESERVED),
NB_DEPLOYMENT(NB_DEPLOYMENT),
RB_MASKING(RB_MASKING),
RB_MASKING_WITH_SRS(RB_MASKING_WITH
_SRS)
Unit: None
Actual Value Range: NB_RESERVED,
NB_DEPLOYMENT, RB_MASKING,
RB_MASKING_WITH_SRS
Default Value: None

CellRbR Index ADD MLBFD LTE In- Meaning: Indicates the index of a reserved RB
eserve CELLR -120001 band configuration for the cell. This parameter applies only
BRESE 03 Deploy to LTE FDD and NB-IoT.
RVE ment GUI Value Range: 0~99
MOD Unit: None
CELLR
BRESE Actual Value Range: 0~99
RVE Default Value: None
RMV
CELLR
BRESE
RVE
LST
CELLR
BRESE
RVE

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 252


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

Prb UlAllSy ADD MLBFD LTE In- Meaning: Indicates whether all PRB uplink symbols
mbolSen PRB -120001 band are used for sending. When this parameter is set to
dFlag MOD 03 Deploy TRUE, all NB-IoT PRB uplink symbols are sent.
PRB ment When this parameter is set to FALSE, not all NB-IoT
PRB uplink symbols are sent. In in-band scenarios,
LST NB-IoT PRB symbols do not conflict with LTE SRS
PRB symbols to avoid interference. This parameter applies
only to NB-IoT.
GUI Value Range: FALSE(FALSE), TRUE(TRUE)
Unit: None
Actual Value Range: FALSE, TRUE
Default Value: TRUE(TRUE)

SRSCfg SrsCfgI MOD LBFD-0 Physical Meaning: Indicates whether to configure sounding
nd SRSCF 02003 / Channel reference signal (SRS) resources for UEs in a cell.
G TDLBF Manage The value BOOLEAN_TRUE indicates that SRS
LST D-00200 ment resources are available in the cell and can be
SRSCF 3 DL 4- configured for UEs in the cell. The value
G TDLAO Layer BOOLEAN_FALSE indicates that no SRS resource is
FD-081 MIMO available in the cell, and therefore no UE in the cell is
409 Based configured with SRS resources. This parameter does
on TM9 not take effect on: (1) FDD cell that is established on
TDLEO an LBBPc and uses four or more RX antennas. (2)
FD-121 DL FDD cell that is established on an LBBPc and uses
615 Flexible extended cyclic prefix (CP) in the uplink. (3) TDD
TDLOF 3D- cell established on an LBBPc. If this parameter does
D-00104 Beamfor not take effect on a cell but SRS resources are
9 ming available in the cell, SRS resources can be configured
Single for UEs in the cell. This parameter applies only to
Streami LTE FDD and LTE TDD.
ng GUI Value Range: BOOLEAN_FALSE(False),
Beamfor BOOLEAN_TRUE(True)
ming
Unit: None
Actual Value Range: BOOLEAN_FALSE,
BOOLEAN_TRUE
Default Value: BOOLEAN_TRUE(True)

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 253


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

Cell PhyCellI ADD LOFD-0 Compac Meaning: Indicates the physical cell ID. For details,
d CELL 01051 t see 3GPP TS 36.331.
MOD LBFD-0 Bandwi GUI Value Range: 0~503
CELL 02009 / dth
Unit: None
LST TDLBF Broadca
D-00200 st of Actual Value Range: 0~503
CELL
9/ system Default Value: None
MLBFD informat
-120002 ion
29

Cell NbCellF ADD None None Meaning: Indicates whether a local cell is an NB-IoT
lag CELL cell. When this parameter is set to TRUE, the local
MOD cell is an NB-IoT cell. When this parameter is set to
CELL FALSE, the local cell is not an NB-IoT cell. This
parameter applies only to NB-IoT.
LST
CELL GUI Value Range: FALSE(FALSE), TRUE(TRUE)
Unit: None
Actual Value Range: FALSE, TRUE
Default Value: FALSE(FALSE)

Prb FreqBan ADD MLBFD Standalo Meaning: Indicates the frequency band to which the
d PRB -120001 ne PRB belongs. For details, see 3GPP TS 36.104. This
MOD 01 Deploy parameter applies only to NB-IoT.
PRB MLBFD ment GUI Value Range: 1~256
LST -120001 LTE Unit: None
PRB 02 Guardba
nd Actual Value Range: 1~256
MLBFD
-120001 Deploy Default Value: None
03 ment
LTE In-
band
Deploy
ment

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 254


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

Prb DlEarfc ADD MLBFD Standalo Meaning: Indicates the PRB DL EARFCN. For
n PRB -120001 ne details, see 3GPP TS 36.104. This parameter applies
MOD 01 Deploy only to NB-IoT.
PRB MLBFD ment GUI Value Range:
LST -120001 LTE 0~68485,255144~256143,260894~262143
PRB 02 Guardba Unit: None
MLBFD nd
Deploy Actual Value Range:
-120001 0~68485,255144~256143,260894~262143
03 ment
LTE In- Default Value: None
band
Deploy
ment

Prb UlEarfc ADD MLBFD Standalo Meaning: Indicates the PRB uplink EARFCN, which
n PRB -120001 ne is optional. This parameter takes effect only when
MOD 01 Deploy UlEarfcnCfgInd is set to CFG(Configure). Otherwise,
PRB MLBFD ment the eNodeB calculates this parameter value based on
-120001 LTE the rule that RB positions in the uplink and downlink
LST are consistent. This parameter applies only to NB-IoT.
PRB 02 Guardba
MLBFD nd GUI Value Range: 18000~65535,131072~133221
-120001 Deploy Unit: None
03 ment
Actual Value Range: 18000~65535,131072~133221
LTE In-
band Default Value: None
Deploy
ment

Issue 05 (2017-08-30) Huawei Proprietary and Confidential 255


Copyright Huawei Technologies Co., Ltd.
eRAN
NB-IoT Radio and Performance Basics Feature Parameter
Description 12 Parameters

MO Parame MML Feature Feature Description


ter ID Comma ID Name
nd

Prb UlFreqO ADD MLBFD Standalo Meaning: Indicates the frequency offset of the PRB
ffset PRB -120001 ne uplink central frequency to the uplink frequency. This
MOD 01 Deploy parameter takes effect only when UlEarfcnCfgInd is
PRB MLBFD ment set to CFG(Configure). Otherwise, the eNodeB
-120001 LTE calculates this parameter value based on the rule that
LST RB positions in the uplink and downlink are
PRB 02 Guardba
nd consistent. For details, see 3GPP TS 36.101. This
MLBFD parameter applies only to NB-IoT.
-120001 Deploy
03 ment GUI Value Range: NEG_10(NEG_10),
LTE In- NEG_9(NEG_9), NEG_8(NEG_8), NEG_7(NEG_7),
band NEG_6(NEG_6), NEG_5(NEG_5), NEG_4(NEG_4),
Deploy NEG_3(NEG_3), NEG_2(NEG_2), NEG_1(NEG_1),
ment POS_0(POS_0), POS_1(POS_1), POS_2(POS_2),
POS_3(POS_3), POS_4(POS_4), POS_5(POS_5),
POS_6(POS_6), POS_7(POS_7), POS_8(POS_8),
POS_9(POS_9)
Unit: None
Actual Value Range: NEG_10, NEG_9, NEG_8,
NEG_7, NEG_6, NEG_5, NEG_4, NEG_3, NEG_2,
NEG_1, POS_0, POS_1, POS_2, POS_3, POS_4,
POS_5, POS_6, POS_7, POS_8, POS_9