NETWORK

ENGINEERING
LTE4414 NB-IoT intra-frequency idle mode
mobility
SR001602 LTE 18 IoT features for SRAN
Network Engineering Information
• Doc ID: 5ac5dafdde26750012b75df7
• 1.3
• Maciej Pakulski
• Approved
• 23-10-2017

Please, always check the latest versionof NEI slides.

1 © Nokia 2018
Training organizational aspects
General
• Training duration: 1h
• Materials: available in the webNEI platform
• Recording: available within 7 working days
after the training in the webNEI platform
https://webnei.emea.nsn-net.net/
Learning index
Joining this session you will have an opportunity to
get points for Learning Index.
Link to NLDH with short instruction will be
distributed at the end of presentation.
2 © Nokia 2018 Nokia Internal Use
Survey
Survey will be run close to the end of
presentation
Q&A
After the Q&A session all questions and answers will
be also posted in the NetEng ASK.
ASK platform replaces questions directed to CS
experts (via email of during our training sessions) or
NetEng Support mailbox.
https://ask.emea.nsn-net.net/questions/
Disclaimer

• Please note that the NEI materials are for internal use only. If they shall be used as a source for
the customer presentation, it is mandatory to align the contents with the Product Management
and/or local sales teams at first!
• The results of simulations shown in this presentation are examples only. They demonstrate
trends (not absolute values) expected after feature activation. The presented simulations should
be analyzed with respect to the assumptions taken. They may differ from results achievable in
real networks.
• This NEI slide deck reflects the state of the feature/solution as it is at the moment of the NEI
slide deck release and is being updated up to C5 (release available) milestone.

3 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility

Document ID: 5ac5dafdde26750012b75df7

Document location: https://webnei.emea.nsn-net.net/#/webnei/5ac5dafdde26750012b75df7/1
Organization: MN CS Network Engineering

Version Description of Changes Date Doc Owner Doc Status Reviewed by Approver Approval Date

0.1 Creation of draft version 10-10-2017 Maciej Pakulski Draft Internal:

Brylka, Marek (Nokia - PL/Wroclaw);
Grzybowski Piotr (Nokia -
PL/Wroclaw) ; Gorzelewski, Pawel
(Nokia - PL/Wroclaw) Chirowski, Michal
(Nokia - PL/Wroclaw); Pol, Maciej
(Nokia - PL/Wroclaw)
External:
Liu, Ly (Nokia - CN/Beijing);
Bu, Hong (Nokia - CN/Beijing); Tao,
Jacob 1. (Nokia - CN/Beijing)

0.2 Incorporation of review remarks 23-10-2017 Maciej Pakulski Draft

0.3 Consolidated version for final approval 06-11-2017 Maciej Pakulski Draft Piotr Grzybowski
Jacek Kotwiński

1.0 Approved version 13-11-2017 Maciej Pakulski Approved 10-11-2017

1.1 Extension of EarlyBird to NEI format 26-02-2018 Maciej Pakulski Approved Piotr Grzybowski 01-03-2018
Jacek Kotwiński

1.2 Editorial corrections 15-03-2018 Maciej Pakulski Approved

4 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility *
Table of contents

Introduction Technical Benefits and Inter – Configuration

Details Gains dependencies Management
Motivation and Feature Detailed Functionality Parameters and
Simulation, Lab and Field Interdependencies with
Overview Description Parameterization
Findings other features and
functions Scenarios
1

Deployment Performance
Aspects Aspects
Activation, Configuration Counters and KPIs,
Examples, Fault Mgmt, Feature Impact Analysis
Trial Area and Verification

* No differences in implementation in SRAN18 (SR001602) (status for 19/03/2018)

Please track upcoming related release notes to get familiarized with the latest solutions
5 © Nokia 2018 Nokia Internal Use
LTE4414 NB-IoT intra-frequency idle mode mobility

Introduction

Table of contents

<chapter:introduction>

6 © Nokia 2018 Non-binding & customer confidential

LTE4414 NB-IoT intra-frequency idle mode mobility
Feature in a nutshell

The feature enables Intra-frequency cell reselection for NB-IoT devices. The cell reselection functionality is
made possible thanks to the introduction of System Information SIB3-NB.
The availability of the feature enriches the NB-IoT ecosystem
• Basic support of mobility for NB-IoT allows for introduction of applications based on NB-IoT devices
tracking
• The NB-IoT reliability is improved for static NB-IoT devices, as the UEs will be able to reselect to a better
cell
Cell re-selection function can be enabled / disabled per NB-IoT cell
by controlling eNB SIB3-NB broadcasting in that particular cell x
Idle mode
Note 1: Inter-frequency mobility in Idle mode is enabled through NB-IoT cell
cell
LTE4117 (FL18SP/FL18A) A
reselection
Note 2 : Connected-mode mobility is not supported in 3GPP Rel13
for NB-IoT and thus not part of this feature.
NB-IoT cell
B

7 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility
Before & after

Before After

• The NB-IoT device is always attached to one
single NB-IoT cell
• This restrict NB-IoT applications only to
stationary devices.
• Even if the device is not moving, the radio
conditions may change over time, but the
device will always be served by the initial
cell
• The idle mode cell reselection makes it
possible for an NB-IoT device to change the
cell it uses
• The non-stationary NB-IoT devices can be
served by a NB-IoT cell
• The NB-IoT device can reselect to a better
cell

8 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility

Technical Details

Table of contents

<chapter:technical_details>

9 © Nokia 2018 Non-binding & customer confidential

Technical Details Sales information
Dependency Table (LTE) BSW/ASW ASW

Release information
Release/version RL release eNodeB NetAct
FDD LTE FDD-LTE 18 FL18 NetAct 18
TDD LTE N/A N/A N/A
Flexi Zone Micro (FZM/FZP) N/A N/A N/A
Flexi Zone Controller (FZC) N/A N/A N/A
Single RAN SRAN18 SBTS18 NetAct 18

Release information – general

HW & IOT HW requirements MME SAE GW UE Specified by 3GPP
Rel. 13
AirScale, FSMF N/A N/A Rel-13 TR 45.820
Cat-NB1

10 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility
Narrowband System Information SI-NB
The NB-IoT solution uses dedicated versions of System Information Broadcast. The system information blocks
from the host LTE cell are not visible to NB-IoT UEs.

most essential information about the cell;

contains all information required to acquire
MIB-
SIB1-NB; MIB-NB
NBschedule with a periodicity of 640 ms
fixed
cell access/selection; contains all information
required to acquire other SI-NB messages;
SIB1-NB fixed schedule with a periodicity of 2560 ms .

radio resource configuration information;

SIB2-NB periodicity is indicated within SIB1-
NB message.
SIB2-NB

Common parameters for intra-frequency idle

mode cell reselection (hysteresis, threshold,
SIB3-NB offset, rxlev and rxqual levels)
NEW: LTE4414 (only part of SIB3, though)

11 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility
NPBCH - Refresher
• NPBCH (Narrowband Physical Broadcast Channel) is
used to carry the Narrowband Master Information LTE PDCCH
Block (MIB-NB)
LTE CRS
• NPBCH is transmitted every 10 ms in subframe #0
NRS ante nna port 0
• NPDSCH/NPDCCH are not mapped to subframes
NRS ante nna port 0
containing NPBCH
NPBCH
• The modulation is QPSK, thus in each subframe #0 200
bits are available
• The NPBCH demodulation is based on NB-IoT NPBCH uses all except the first 3 OFDM symbols for LTE
control channel and reserved LTE CRS resource elements (4
reference signal (NRS).
antenna ports).

12 © Nokia 2018 Nokia Internal Use

 LTE4414 NB-IoT intra-frequency idle mode mobility
MIB-NB scheduling - Refresher
• The MIB-NB uses a fixed schedule with a periodicity of 640 ms and repetitions made within 640 ms.
• After physical layer baseband processing, the resulting MIB-NB is split into 8 blocks
• Each block is transmitted on the first subframe (SF0) and repeated in SF0 of the next 7 consecutive radio
frames (so, each block spans 80 ms).
• This process is continued until the whole MIB-NB is transmitted. A MIB remains unchanged over the 640 ms
transmission time interval (TTI).

640 ms
80 ms 80 ms 80 ms 80 ms 80 ms 80 ms 80 ms 80 ms
SFN 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
NPBCH block

SFN 32 SFN 33 SFN 34 SFN 35 SFN 36 SFN 37 SFN 38 SFN 39

10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms
Subframe 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9
MIB-NB/NPBCH NPSS NSSS

13 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility
SIB1-NB scheduling - Refresher
RNB-SIB1 SFN\SF#4 0 8 16 24 32 40 48 56 64 72 80 88 96 104 112 120 128 136 144 152 160 168 176 184 192 200 208 216 224 232 240 248 256
4 PCI mod 4 = 0 4 r0 r1 r2 r3
4 repetitions

RNB-SIB1 SFN\SF#4 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
4 PCI mod 4 = 0 4 r0,t0 r0,t1 r0,t2 r0,t3 r0,t4 r0,t5 r0,t6 r0,t7
8 frames sequence, repetition #0
• SIB1-NB transmission occurs in subframe #4, every other frame, 8 DL 0 1 2 3 4 5 6 7 8 9

subframes sequence. SIB1-NB TB is composed of 8 NB-IoT

Starting radio frame
downlink subframes. R NB-SIB1 PCID number for NB-SIB1
repetitions
• Within 256 radio frames period the SIB1-NB sequence is repeated 4, PCID mod 4 = 0 SFN mod 256 = 0

8 or 16 times, depending on the schedulingInfoSIB1-NB-r13. 4

PCID mod 4 = 1 SFN mod 256 = 16
PCID mod 4 = 2 SFN mod 256 = 32
Repetitions are equally distributed within 256 frames period. PCID mod 4 = 3 SFN mod 256 = 48
PCID mod 2 = 0 SFN mod 256 = 0
8
PCID mod 2 = 1 SFN mod 256 = 16
PCID mod 2 = 0 SFN mod 256 = 0
16
PCID mod 2 = 1 SFN mod 256 = 1

14 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility
SIB2-NB scheduling - Refresher subframe
SFN
0
0 1 2 3 4
SIB1
5
NPSS
6 7 8 9
NSSS
siRadioFrameOffNB=2
offset
• SIB2-NB is broadcast in the valid sub-frames,
1 8 consecutive valid subframes
NPSS
2
3
SIB2,r0,t0 SIB2,r0,t1 SIB2,r0,t2
SIB2,r0,t6 SIB2,r0,t7
SIB1 NPSS
SIB2,r0,t3 SIB2,r0,t4 SIB2,r0,t5
NPSS
NSSS except for NPSS/ NSSS/ NPBCH/ SIB1-NB.
MIB
4 SIB1 NPSS sib2RepPatternNB=every4th NSSS
5 NPSS • Single SIB2-NB is transmitted over 2 or 8

siWindowLenNB=160ms
6 SIB2,r1,t0 SIB2,r1,t1 SIB2,r0,t2 SIB1 NPSS SIB2,r1,t3 SIB2,r1,t4 SIB2,r1,t5 NSSS
7 SIB2,r1,t6 SIB2,r1,t7 NPSS
consecutive valid subframes. Offset in radio

sib2PeriodicityNB=256
SI window
8 SIB1 NPSS NSSS
9 NPSS
frames for the start of the SI window

SI-periodicity
10 SIB2,r2,t0 SIB2,r2,t1 SIB2,r2,t2 SIB1 NPSS SIB2,r2,t3 SIB2,r2,t4 SIB2,r2,t5 NSSS
11 SIB2,r2,t6 SIB2,r0,t7 NPSS
MIB
12
13
SIB1 NPSS
NPSS
NSSS
siRadioFrameOffNB
14 SIB2,r3,t0 SIB2,r3,t1 SIB2,r3,t2 SIB1 NPSS SIB2,r3,t3 SIB2,r3,t4 SIB2,r3,t5 NSSS
15
16
SIB2,r3,t6 SIB2,r3,t7
SIB1
NPSS
NPSS NSSS • SIB2-NB is repeated every sib2RepPatternNB
17 NPSS
frame (example: every 4th frame)
MIB
….
MIB NPSS …… NSSS SIB1 SIB2 … • Repetitions are within SI-window,
… ... …
…
256 SIB1 NPSS NSSS
…
offset
siWindowLenNB
257 NPSS
258 SIB2,r0,t0 SIB2,r0,t1 SIB2,r0,t2 SIB1 NPSS SIB2,r0,t3 SIB2,r0,t4 SIB2,r0,t5 NSSS
259
260
MIB
SIB2,r0,t6 SIB2,r0,t7
SIB1
NPSS
NPSS NSSS
• Whole SIB2-NB sequence is transmitted every
261
262 SIB2,r1,t0 SIB2,r1,t1 SIB2,r0,t2 SIB1
NPSS
NPSS SIB2,r1,t3 SIB2,r1,t4 SIB2,r1,t5 NSSS sib2PeriodicityNB period
263 SIB2,r1,t6 SIB2,r1,t7 NPSS
264 SIB1 NPSS NSSS
265 NPSS
266 SIB2,r2,t0 SIB2,r2,t1 SIB2,r2,t2 SIB1 NPSS SIB2,r2,t3 SIB2,r2,t4 SIB2,r2,t5 NSSS
267 SIB2,r2,t6 SIB2,r0,t7 NPSS
MIB
268 SIB1 NPSS NSSS
269 NPSS
270 SIB2,r3,t0 SIB2,r3,t1 SIB2,r3,t2 SIB1 NPSS SIB2,r3,t3 SIB2,r3,t4 SIB2,r3,t5 NSSS
271 SIB2,r3,t6 SIB2,r3,t7 NPSS
272 SIB1 NPSS NSSS
273 NPSS

15 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility
SIB3-NB introduced by LTE4414

• This feature introduces support of SIB3-NB for Intra-frequency idle mode mobility to provide the UE with
cell re-selection information for intra-frequency.
- supported irrespective of the NB-IoT mode and hardware platform (FDD 5-20 MHz legacy BW on Airscale, FSMF and FZM platforms).

• Connected mode mobility is not supported in 3GPP Rel13 for NB-IoT and thus not part of this feature.
• Cell re-selection function can be enabled / disabled per NB-IoT cell by controlling eNB SIB3-NB broadcasting
to UE by O&M settings of schedulingInfoList parameter in SIB1-NB.
• SIB3-NB should be scheduled in SIB1-NB and periodically broadcasted to NB-IoT UEs in idle mode
• SIB3-NB configuration is defined by three variables
- SIB3-NB periodicity siMessagePeriodicityNB (defined for SIB3-NB)
- SIB3-NB repetition pattern siMessageRepPatternNB (defined for SIB3-NB)
- Overall global SIB window length siWindowLenNB

16 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility
SIB3-NB contents
Field Structure_Name FDD source ASN1_Type Range_Or_Length Optional Comment

SystemInformationBlockType3-NB-r13 SEQUENCE
> cellReselectionInfoCommon-r13 SEQUENCE

{dB0,dB1,dB2,dB3,dB4,dB5,dB6,dB8,dB10,dB12,dB1
>> q-Hyst-r13 Reuse SIB->qHyst ENUMERATED 4,dB16,dB18,dB20,dB22,dB24}

> cellReselectionServingFreqInfo-r13 SEQUENCE

>> s-NonIntraSearch-r13 ReselectionThreshold Reuse SIB->threshSrvLow INTEGER (0..31)

> intraFreqCellReselectionInfo-r13
>> q-RxLevMin-r13 Q-RxLevMin Reuse SIB->qrxlevminintraF
SEQUENCE
INTEGER
Section of SIB3 present
(-70..-22)
>> q-QualMin-r13
>> p-Max-r13
Q-QualMin-r9
P-Max
Reuse SIB->qQualMinR9 ???
Reuse SIB->pMaxIntraF
INTEGER
INTEGER in SIB3-NB
(-34..-3)
(-30..33)
OPTIONAL
OPTIONAL
-- Need OP
-- Need OP
>> s-IntraSearchP-r13 ReselectionThreshold Reuse SIB->sIntrasearch INTEGER (0..31)
new parameter SIB->tReselNB see next
>> t-Reselection-r13 T-Reselection-NB-r13 slide ENUMERATED {s0,s3,s6,s9,s12,s15,s18,s21}

> freqBandInfo-r13 NS-PmaxList-NB-r13 not support SEQUENCE OF (1..maxNS-Pmax-NB-r13) (1..4) OPTIONAL -- Need OR
>> #0 NS-PmaxValue-NB-r13 SEQUENCE

>>> additionalPmax-r13 P-Max INTEGER (-30..33) OPTIONAL -- Need OR

>>> additionalSpectrumEmission-r13 AdditionalSpectrumEmission INTEGER (1..32)

> multiBandInfoList-r13 not support SEQUENCE OF (1..maxMultiBands) (1..8) OPTIONAL -- Need OR

>> #0 NS-PmaxList-NB-r13 SEQUENCE OF (1..maxNS-Pmax-NB-r13) (1..4) OPTIONAL -- Need OR

>>> #0 NS-PmaxValue-NB-r13 SEQUENCE
>>>> additionalPmax-r13 P-Max INTEGER (-30..33) OPTIONAL -- Need OR

>>>> additionalSpectrumEmission-r13 AdditionalSpectrumEmission INTEGER (1..32)

> lateNonCriticalExtension OCTET STRING
IntraFreqCellReselectionInfo-NB- -- Cond
> intraFreqCellReselectionInfo-v1350 v1350 SEQUENCE OPTIONAL Qrxlevmin
>> delta-RxLevMin-v1350 SIB3-NB (-8..-1)
INTEGER contents
17 © Nokia 2018 FL18 Baseline 3GPP 36.331 V13.4.0(2016-12)
LTE4414 NB-IoT intra-frequency idle mode mobility
SIB3-NB scheduling subframe
SFN
x+0
0
MIB-NB
1 2 3 4
SIB1-NB
5
NPSS
6 7 8 9
NSSS
siRadioFrameOffNB=2
offset
• The same transmission scheme is used as for SIB2-NB.
x+1
x+2
MIB-NB
MIB-NB SIB3,r0,t0
8 consecutive
SIB3,r0,t1 SIB3,r0,t2 SIB1-NB
valid subframes
NPSS
NPSS
SIB3,r0,t3 SIB3,r0,t4 SIB3,r0,t5 NSSS • Common parameters with SIB2-NB:
x+3 MIB-NB SIB3,r0,t6 SIB3,r0,t7 NPSS
x+4 MIB-NB SIB1-NB NPSS SIB3RepPatternNB=every4th NSSS • Offset in radio frames for the start of
x+5 MIB-NB NPSS
the SI window siRadioFrameOffNB,

siWindowLenNB=160ms
x+6 MIB-NB SIB3,r1,t0 SIB3,r1,t1 SIB3,r0,t2 SIB1-NB NPSS SIB3,r1,t3 SIB3,r1,t4 SIB3,r1,t5 NSSS

sib3PeriodicityNB=640
x+7 MIB-NB SIB3,r1,t6 SIB3,r1,t7 NPSS
• SI-window length siWindowLenNB.

SI window
x+8 MIB-NB SIB1-NB NPSS NSSS
x+9 MIB-NB NPSS
• Single SIB3-NB is transmitted over 2 or 8 consecutive

SI-periodicity
x + 10 MIB-NB SIB3,r2,t0 SIB3,r2,t1 SIB3,r2,t2 SIB1-NB NPSS SIB3,r2,t3 SIB3,r2,t4 SIB3,r2,t5 NSSS
x + 11
x + 12
MIB-NB
MIB-NB
SIB3,r2,t6 SIB3,r0,t7
SIB1-NB
NPSS
NPSS NSSS valid subframes*.
x + 13 MIB-NB NPSS
x + 14 MIB-NB SIB3,r3,t0 SIB3,r3,t1 SIB3,r3,t2 SIB1-NB NPSS SIB3,r3,t3 SIB3,r3,t4 SIB3,r3,t5 NSSS • SIB3-NB is repeated every siRepPatternNB frame
x + 15 MIB-NB SIB3,r3,t6 SIB3,r3,t7 NPSS
x + 16
x + 17
MIB-NB
MIB-NB
NPSS
NPSS
NSSS
(example: every 4th frame)
MIB-NB
MIB-NB
• Whole SIB3-NB sequence is transmitted every
MIB-NB
MIB-NB
….
…… … siPeriodicityNB period
•
MIB-NB … ... …
… MIB-NB … Note: siRepPatternNB and siPeriodicityNB will be
x + 64 MIB-NB SIB1-NB NPSS NSSS
x + 65
x + 66
MIB-NB
MIB-NB SIB3,r0,t0 SIB3,r0,t1 SIB3,r0,t2 SIB1-NB
NPSS
NPSS SIB3,r0,t3 SIB3,r0,t4 SIB3,r0,t5 NSSS
offset
also used for new SIBs, e.g. SIB4-NB coming with
x + 67
x + 68
MIB-NB
MIB-NB
SIB3,r0,t6 SIB3,r0,t7
SIB1-NB
NPSS
NPSS NSSS
LTE4117.
x + 69 MIB-NB NPSS
x + 70 MIB-NB SIB3,r1,t0 SIB3,r1,t1 SIB3,r0,t2 SIB1-NB NPSS SIB3,r1,t3 SIB3,r1,t4 SIB3,r1,t5 NSSS
x + 71 MIB-NB SIB3,r1,t6 SIB3,r1,t7 NPSS
x + 72 MIB-NB SIB1-NB NPSS NSSS
x + 73 MIB-NB NPSS *SIB3-NB TBS is determined by eNB by selecting the smallest value from the SI TBS
x + 74 MIB-NB SIB3,r2,t0 SIB3,r2,t1 SIB3,r2,t2 SIB1-NB NPSS SIB3,r2,t3 SIB3,r2,t4 SIB3,r2,t5 NSSS
x + 75 MIB-NB SIB3,r2,t6 SIB3,r0,t7 NPSS pool {b56, b120, b208, b256, b328, b440, b552, b680}. SIB3-NB is transmitted over 2
x + 76 MIB-NB SIB1-NB NPSS NSSS (TBS 56/120) or 8 (remaining TBSs) consecutive
x + 77 MIB-NB NPSS
NB-IoT downlink subframes
x + 78 MIB-NB SIB3,r3,t0 SIB3,r3,t1 SIB3,r3,t2 SIB1-NB NPSS SIB3,r3,t3 SIB3,r3,t4 SIB3,r3,t5 NSSS
x + 79 MIB-NB SIB3,r3,t6 SIB3,r3,t7 NPSS
x + 80 MIB-NB NPSS NSSS
x + 81 MIB-NB NPSS

18 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility
Example of SIB2-NB and SIB3-NB interactions.
siWindowLenNB = 160 ms

SIB2RepPatternNB=every4th
siWindowLenNB = 160 ms

siRepPatternNB=every4th • SIB2-NB is transmitted as first,

with siRadioFrameOffNB offset.
• Then SIB3-NB is transmitted, in the
subsequent SI-window (common for both)
defined by siWindowLenNB.
• SIB2-NB and SIB3-NB occurrence in
subsequent SI windows depends on the
SIB2PeriodicityNB and siPeriodicityNB

19 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility
SIB2-NB and SIB3-NB configurations MIB-NB

MIB-NB siWindowLenNB = 160 ms

SIB1-NB

SIB1-NB siWindowLenNB = 160 ms

SIB2-NB siWindowLenNB = 160 ms

SIB2-NB SIB3-NB

SIB3-NB siWindowLenNB = 160 ms

SIB2MessagePeriodicityNB
(for SIB2-NB) = 640 ms

SIB2MessagePeriodicityNB
(for SIB2-NB) = 640 ms
siMessagePeriodicityNB
siMessagePeriodicityNB (for SIB3-NB) = 1280 ms
(for SIB3-NB) = 640 ms

20 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility
Idle mode mobility limitations

• The LTE4414 supports only limited idle mode mobility*

- Incomplete SIB3-NB contents is supported – allowing only for intra-frequency idle mode cell
reselection (no intra-frequency measurements)
- Moreover, SIB4-NB is not in the feature scope
• As a result, only common information for intra-frequency cell reselection will be broadcasted (part of
SIB3-NB) without neighboring cell related information

*the missing functionalities will be introduced by LTE4117 feature

21 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility

Benefits and Gains

Table of contents

<chapter:benefits_and_gains>

22 © Nokia 2018 Non-binding & customer confidential

LTE4414 NB-IoT intra-frequency idle mode mobility
Benefits and Gains

• The LTE4414 introduces basic mobility for the NB-IoT devices.

• One of the benefits is increased robustness of the data exchange with stationary NB-
IoT devices, thanks to the possibility of reevaluating radio reception quality and
capability to select best (or simply better) cell
- The touch-free life of an NB-IoT device can span several years ,and during that time the radio environment
may significantly change (e.g. construction of buildings in the vicinity, roll-out of new base stations). With
this feature the NB-IoT device will always be served by the best available cell.
• Another benefit is the possibility of developing applications for mobile NB-IoT
devices.
- Even if only idle mode cell reselection is supported (no fast-moving devices, just some infrequent or low
scale movements), several new use cases and applications are made possible

23 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility

Interdependencies

Table of contents

<chapter:interdependencies>

24 © Nokia 2018 Non-binding & customer confidential

LTE4414 NB-IoT intra-frequency idle mode mobility

prerequisites LTE3071 NB-IoT Inband

This is a mandatory prerequisite in case of inband NB-IoT
deployment – the NB-IoT cell need to be set up and activated
before the LTE4414 can be configured
 More details available on WebNEI: link,

LTE3543 NB-IoT standalone

This is a mandatory prerequisite in case of standalone NB-IoT
deployment – the NB-IoT cell need to be set up and activated
before the LTE4414 can be configured
 More details available on WebNEI: link

25 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility

prerequisites LTE3509 Inband NB-IoT on Airscale without Baseband

Pooling.
This is a mandatory prerequisite in case of inband NB-
IoT deployment on AirScale platform – the NB-IoT cell need to
be set up and activated before the LTE4414 can be configured
 More details available on WebNEI: link

Note: only one of the prerequisites is mandatory in a given case,

because the features LTE3071, LTE3543 and LTE3509 are different
flavors of NB-IoT deployment

26 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility

extensions LTE4117 NB-IoT Inter-frequency idle mode mobility

LTE4117 completes Intra-frequency cell reselection for NB-IoT devices
with the support of SIB4-NB including neighboring cell information
relevant for intra-frequency cell re-selection

On top of this, LTE4117 enables Inter-frequency cell reselection for NB-

IoT devices:
- New IEs added to SIB3-NB for inter-frequency and intra-frequency cell re-
selection
- Support of SIB5-NB to include neighboring cell information relevant for
inter-frequency cell re-selection
- Introduced stepwise (LTE4117-A in FL18SP, LTE4417-B in FL18A)
(CRL22737)

27 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility

The following features cannot be enabled in the hosting LTE cell together with inband NB-
limitations IoT (and therefore can need to be deactivated prior to LTE4414 activation):
host LTE cell LTE2180 – FDD-TDD downlink carrier aggregation 2CC
LTE2270 – LTE TDD+FDD inter eNB CA basic BTS
LTE2316 – FDD-TDD downlink carrier aggregation 3CC
LTE2735 – FDD-TDD downlink carrier aggregation with AirScale System Module
configurations
LTE2337 - FDD-TDD downlink carrier aggregation 3CC - 2 FDD & 1 TDD;
LTE2623 – FDD-TDD downlink carrier aggregation 4CC
LTE2504 LTE U-plane SW deployment on 4 DSPs
Inter eNB CA TDD+FDD is not supported in the host LTE cell due to conflicting requirements on
DSP deployment in eNB FDD. There is no specific feature flag for FDD+TDD CA because
'actInterEnbDLCAggr' is commonly used also for FDD+FDD CA.

28 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility

The following features cannot be enabled in the hosting LTE cell together with inband NB-
limitations IoT (and therefore can need to be deactivated prior to LTE4414 activation):
host LTE cell LTE1709 Liquid Cell
TM9 CSI-RS may interfere with NB-IoT
LTE1542 - FDD Supercell
Super Cell requires specific DSP deployment
LTE2091 - Extended SuperCell
LTE2445 - Combined Supercell
Combined Supercell requires specific DSP deployment
LTE1117 eMBMS
eMBMS may may interfere with NB-IoT (interference in both directions).
LTE1113 / LTE1496 eICIC
NB-IoT may generate interference on eICIC ABS subframes

29 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility

The following features cannot be enabled in the hosting LTE cell together with inband NB-
limitations IoT (and therefore can need to be deactivated prior to LTE4414 activation) :
host LTE cell LTE1891 MicroDTX
MicroDTX may mute the subframes impacting NB-IoT
LTE495 OTDOA
OTDOA may interfere with NB-IoT (interference in both directions).
LTE819 DL inter-cell interference generation
Dummy load generation on both host LTE cell and NB-IoT cell are not supported.

30 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility

Configuration
Management
Table of contents

<chapter:configuration_management>

31 © Nokia 2018 Non-binding & customer confidential

Configuration Management
Related Parameters (new)

Abbreviated
Full name Description Range and step Default
name
Timer Cell
NBIOT_FDD-tReselNB Reselection for NB- Defines the cell reselection timer value for NB-IoT {0,3,6,9,12,15, 18, 21} [sec] 3 sec
IoT
NBIOTPR- List of scheduled SI- Structure – contains array of scheduled NB-IoT SI messages. Currently
sibSchedulingListNB Messages for NB-IoT includes only scheduling information of SIB3-NB.
NBIOTPR- Periodicity of the NB-IoT SI-message {640, 1280, 2560, 5120, 1280 ms
siMessagePeriodicityNB SI-Message 10240, 20480, 40960} [ms]
Periodicity in NB-IoT

NBIOTPR- SI-Message Repetition The repetition pattern of the NB-IoT SI-Message (expressed as numer {(0) every2ndRF, (1) (2)
siMessageRepPatternNB Pattern in NB-IoT od radio frames). every4thRF, (2) every8thRF, every8th
(3) every16thRF} RF

NBIOTPR- SI-Message of SIB SIB NB Type. Only SibType3 is supported. {(1) SIB3-NB; (2)SIB4-NB; (1)
siMessageSibTypeNB Type for NB-IoT (3) SIB5-NB; (4) SIB14-NB; SIB3-NB
(5) SIB16-NB}

REQUIRES BTS REQUIRES CELL LOCKING ONLINE MODIFIABLE

RESTART
32 © Nokia 2018 Non-binding & customer confidential
Configuration Management
Related Parameters (existing)

Abbreviated
Full name Description Range and step Default
name
Cell reselection
Provides the hysteresis value in dB for ranking criteria in the NB-IoT cell 0…24 dB, step:
qHyst procedure hysteresis 2dB
reselection procedure. 2dB
value
Specifies the threshold for the serving frequency used in reselection evaluation 0...62 dB, step 2 4
threshSrvLow Threshold serving low
towards lower priority EUTRAN frequency or RAT. dB
qrxlevminintraF Min. required RX level Provides the minimum required RX RSRP level (in dBm) for the intra-frequency -140..-44 dBm, N/A
for intra-freq neighboring EUTRA NB-IoT cells. step 2
neighboring cells
pMaxIntraF Pmax intra-frequency Pmax to be used for the intra-frequency neighboring EUTRA cells. If pmax is -30...33 dBm, step N/A
neighboring E-UTRA absent, the maximum power according to the UE capability is used. 1 dBm
sIntrasearch Intra-frequency The Sintrasearch parameter defines the threshold (in dB) for intra-frequency
measurements threshold measurements.
0...62 dB, step 2 62
The UE can omit measurements of intra-frequency neighbor cells if the serving cell
dB
is above that threshold.
qQualMinR9 Min required RSRQ in
-34...-3 dB, step 1
inter-freq neighbor cells Minimum required RSRQ level (in dB) in intra-frequency neighbor NB-IoT cells. N/A
dB
(Rel9)

REQUIRES BTS REQUIRES CELL LOCKING ONLINE MODIFIABLE

RESTART
33 © Nokia 2018 Non-binding & customer confidential
Configuration Management
Related parameters

Abbreviated name Full name PKDB link

NBIOT_FDD:tReselNB Timer​​Cell​​Reselection​for​​N​B​-​Io​T

NBIOTPR:sibSchedulingListNB ​List​of​scheduled​​S​I​-​Messages​for​​N​B​
-​Io​T

NBIOTPR:siMessagePeriodicityNB SI-Message Periodicity in NB-IoT

SI-Message Repetition Pattern in NB-
NBIOTP:siMessageRepPatternNB
IoT

NBIOTPR:siMessageSibTypeNB SI-Message of SIB Type for NB-IoT

34 © Nokia 2018 Nokia Internal Use

Configuration Management
Related parameters

Abbreviated name Full name PKDB link

Cell​reselection​procedure​hysteresis​
SIB:qHyst
value

SIB:threshSrvLow ​Threshold serving low

Min. required RX level for intra-freq
SIB:qrxlevminintraF
neighboring cells
Pmax intra-frequency neighboring E-
SIB:pMaxIntraF
UTRA
I​ ntra​-frequency​measurements​
SIB:sIntrasearch
threshold

SIB:qQualMinR9 ​Minimum​required​​R​S​R​Q​in​cell​​(​Rel​
9​)

35 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility

Deployment
Aspects
Network graphic boxes Network element boxes
Table of contents

<chapter:deployment_aspects>

36 © Nokia 2018 Non-binding & customer confidential

LTE4414 NB-IoT intra-frequency idle mode mobility
Feature configuration 1/3

• SIB3-NB should be scheduled in SIB1-NB and periodically broadcasted to NB-IoT UEs in idle mode.
Feature activation
• There is no dedicated activation flag. Operator can decide whether SIB3-NB is to be broadcast by adding/removing SIB3-NB
related configurations from sibSchedulingListNB (i.e. SIB3 configured = transmitted, not configured = not transmitted)
Feature configuration
• From LTE4414 with SIB3-NB support, the structure NBIOTPR->sibSchedulingListNB is introduced, to define which SIBx-NB
messages are broadcast, and to provide their periodicity/repetition patterns. Note: this structure is applicable only for SIB3-NB and
higher SIBs (future SIB extensions)
- sibSchedulingListNB::siMessageSibTypeNB used to define which SIBx-NB type is to be broadcasted (only SIB3-NB in LTE4414).
- sibSchedulingListNB::siMessagePeriodicityNB used to define respective SIBx-NB periodicity
- sibSchedulingListNB::siMessageRepPatternNB used to define repetition pattern of the respective SIBx-NB
• The configuration used previously (with only SIB2-NB present), with NBIOTPR->sib2PeriodicityNB/sib2RepPatternNB to configure the
periodicity and repetition pattern of SIB2-NB is still used for SIB2-NB
• An additional new parameter is introduced: tReselNB – cell reselection timer for NB-IoT (range: 0..21 sec, step: 3, default: 3s)

37 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility
Feature configuration 2/3

Feature configuration
• The SIB3-NB configuration requires the following parameters to be set:
- An instance of the structure MRBTS/LNBTS/NBIOTPR-sibSchedulingListNB needs to be created and the following
fields of the structure shall be configured
• siMessageSibTypeNB - for SIB3-NB set to „1”, possible values 1:SIB3-NB; 2:SIB4-NB;3:SIB5-NB;4:SIB14-NB;5: SIB16-NB;
• siMessagePeriodicityNB - the value of theSBIB3-NB periodicity, default value: 1280 ms, possible values 640, 1280, 2560, 5120, 10240, 20480,
40960 (ms)
• siMessageRepPatternNB - the value of the SIB3-NB repetition pattern, default value: 2, range and values: 0:every2ndRF;
1:every4thRF; 2:every8thRF; 3:every16thRF
- Additionally, the existing common idle mode cell reselection parameters are reused:
• MRBTS/LNBTS/LNCEL/SIB/qHyst – the hysteresis for ranking criteria during cell reselection,
• MRBTS/LNBTS/ LNCEL/SIB/threshSrvLow – the low threshold for the serving frequency,
• MRBTS/LNBTS/ LNCEL/SIB/qrvlevminintraF – minimum required RX level in the cell,

38 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility
Feature configuration 3/3

Feature configuration
- …continued:
• MRBTS/LNBTS/ LNCEL/SIB/pMaxIntraF – max power to be used in the neighboring cell,
• MRBTS/LNBTS/ LNCEL/SIB/sIntrasearch – the threshold for intra-frequency measurements
• MRBTS/LNBTS/ LNCEL/SIB/qQualMinR9 – minimum required RSRQ in the cell,
- Additional parameter that is used in SIB3-NB scheduling is MRBTS/LNBTS/NBIOTPR/siWindowLengthNB – common
System Information window length (valid for all SIBx-NB), default value: 640 ms

Feature verification
• It is not possible to verify directly that the feature works as intended, since there are no dedicated counters. The
verification is possible only indirectly by testing UE behavior, or by checking UE logs where possible. In a lab
environment the verification is possible using a dedicated terminal and analysing RRC messages with the help
of a protocol analyzer.

39 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility
SIB3-NB impact on capacity

• The necessity of transmitting of SIB3-NB reduces the numer of available resources for other downlink
transmission (NPDCCH and NPDSCH resources)
• The actual capacity loss caused by SIB3-NB transmission depends on the settings of the parameters
(periodicity, repetition pattern, SI window length) and on the SIB3-NB length (Transport Block size).
• For the example values:
- SIB3-NB repetition pattern: 8 frames
- SIB3-NB periodicity: 1280 ms
- SI window length: 640 ms
the downlink capacity loss is:
- 15.7% for the case of SIB3-NB TB size 8 subframes,
- 3.9% for the case of SIB3-NB TB size 2 subframes,
For details of the example, see next slide. For more details, see the NB-IoT resource grid tool here

40 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility
Capacity impact – SIB3-NB TB size 8 frames
• SI window length: 640 ms
• Number of SIB1-NB repetitions: 4 (in 2560 ms period)
• SIB2-NB repetition pattern: 8 frames
• SIB2-NB periodicity: 1280 ms
• SIB2-NB TB size: 8 frames
• SIB3-NB repetition pattern: 8 frames
• SIB3-NB periodicity: 1280 ms

• Total number of subframes within single SIB3-NB repetition (1280 ms): 1280
• MIB-NB overhead: 128 subframes
• NPSS overhead: 128 subframes
• NSSS overhead: 64 subframes
• SIB1-NB overhead: 16 subframes
• SIB2-NB overhead: 128 subframes => total overhead 464

• Number of remaining free subframes with SIB3-NB off: 816

• SIB3-NB overhead: 128 subframes
• Number of remaining free subframes with SIB3-NB on: 688
• Capacity loss caused by SIB3-NB: 15.7%
• Gross SIB3-NB overhead (relative to total numer of subframes): 10%

White blocks = remaining

shared channel capacity
41 © Nokia 2018 Nokia Internal Use
LTE4414 NB-IoT intra-frequency idle mode mobility
Capacity impact - SIB3-NB TB size 2 frames
• SI window length: 640 ms
• Number of SIB1-NB repetitions: 4 (in 2560 ms period)
• SIB2-NB repetition pattern: 8 frames
• SIB2-NB periodicity: 1280 ms
• SIB2-NB TB size: 8 frames
• SIB3-NB repetition pattern: 8 frames
• SIB3-NB periodicity: 1280 ms

• Total number of subframes within single SIB3-NB repetition (1280 ms): 1280
• MIB-NB overhead: 128 subframes
• NPSS overhead: 128 subframes
• NSSS overhead: 64 subframes
• SIB1-NB overhead: 16 subframes
• SIB2-NB overhead: 128 subframes => total overhead 464

• Number of remaining free subframes with SIB3-NB off: 816

• SIB3-NB overhead: 32 subframes
• Number of remaining free subframes with SIB3-NB on: 784
• Capacity loss caused by SIB3-NB: 3.9%
• Gross SIB3-NB overhead (relative to total numer of subframes): 2.5%

42 © Nokia 2018 Nokia Internal Use

LTE4414 NB-IoT intra-frequency idle mode mobility

Performance
Aspects
Table of contents

<chapter:performance_aspects>

43 © Nokia 2018 Non-binding & customer confidential

LTE4414 NB-IoT intra-frequency idle mode mobility
Network performance monitoring
No new counters and KPIs have been introduced with LTE4414. The activation of the feature does not impact
the host cell. The NB-IoT cell is, however, impacted, since the available NB-IoT capacity is slightly decreased,
due to need to use some resources for SIB3-NB transmission. The legacy counters listed below can be
monitored to assess the impact. Note, however, that if the load in the NB-IoT cell is low, this impact will not be
detectable (still enough capacity to handle the offered traffic)

Feature impact How to measure

Increase in the DL NB-IoT resource utilization ratio. The KPI shows the ratio of E-UTRAN DL Resource Utilization Ratio for NB-IoT
the used and available PRBs for NB-IoT UEs in DL direction in the observation UEs
period. LTE_6176a =
The presence of additional periodic System Information messages (SIB3-NB) 100*sum([NB_IOT_RESOURCES_USED_DL]) /
will decrease the amount of the available NB-IoT DL NPDSCH resources. sum([NB_IOT_RESOURCES_AVAIL_DL])
Therefore, with unchanged offered traffic the utilization ratio will increase.

44 © Nokia 2018 Non-binding & customer confidential

Copyright and confidentiality
The contents of this document are proprietary and
confidential property of Nokia Solutions and Networks. This
document is provided subject to confidentiality obligations
of the applicable agreement(s).
This document is intended for use of Nokia Solutions and
Networks customers and collaborators only for the purpose
for which this document is submitted by Nokia Solution and
Networks. No part of this document may be reproduced or
made available to the public or to any third party in any
form or means without the prior written permission of Nokia
Solutions and Networks. This document is to be used by
properly trained professional personnel. Any use of the
contents in this document is limited strictly to the use(s)
specifically created in the applicable agreement(s) under
which the document is submitted. The user of this document
may voluntarily provide suggestions, comments or other
feedback to Nokia Solutions and Networks in respect of the
contents of this document ("Feedback"). Such Feedback may
45 © Nokia 2018 Nokia Internal Use
be used in Nokia Solutions and Networks products and
related specifications or other documentation. Accordingly,
if the user of this document gives Nokia Solutions and
Networks Feedback on the contents of this document, Nokia
Solutions and Networks may freely use, disclose, reproduce,
license, distribute and otherwise commercialize the feedback
in any Nokia Solutions and Networks product, technology,
service, specification or
other documentation.
Nokia Solutions and Networks operates a policy of ongoing
development. Nokia Solutions and Networks reserves the
right to make changes and improvements to any of the
products and/or services described in this document or
withdraw this document at any time without prior notice.
The contents of this document are provided "as is". Except
as required by applicable law, no warranties of any kind,
either express or implied, including, but not limited to, the
implied warranties of merchantability and fitness for a
particular purpose, are made in relation to the accuracy,
reliability or contents of this document. NOKIA
SOLUTIONS AND NETWORKS SHALL NOT BE
RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS
DOCUMENT or for any loss of data or income or any
special, incidental, consequential, indirect or direct damages
howsoever caused, that might arise from the use of this
document or any contents of this document.
This document and the product(s) it describes are protected
by copyright according to the
applicable laws.
Nokia is a registered trademark of Nokia Corporation. Other
product and company names mentioned herein may be
trademarks or trade names of their respective owners.
© Nokia Solutions and Networks 2014