BIG DATA &

NETWORK ENGINEERING

LTE3071 NB-IoT
Updated with RP001597 “Support of LTE in-band NB-IoT with RF sharing in
SRAN "

Part 1&2

Please, always check the latest version of NEI slides.

1 © Nokia 2016 Controlled Document, for internal use
 Part 1

2 © Nokia 2016 Nokia Internal Use

LTE3071 NB-IoT
Table of contents

Introduction Technical Inter –

Details dependencies
Motivation and Feature Detailed Functionality
Interdependencies with
Overview Description
other features and
functions
1

5 © Nokia 2016 Nokia Internal Use

LTE3071 NB-IoT

Introduction

Table of contents

<chapter:introduction>

6 © Nokia 2016 Nokia Internal Use

Introduction
IoT use cases

Internet of Things

Massive IoT connectivity Critical IoT connectivity

• Simple cheap devices • „Always available“

• Low energy consumption • Very low latency
• Massive number of devices • Flexibility
• Full coverage, low datarate • Example: Connected cars
• Example: Smart meters

7 © Nokia 2016 Nokia Internal Use

Introduction
Massive IoT connectivity (key enablers)

Low deployment cost Long battery life

$
IoT support introduction should be limited The battery replacement interval is a
to simple, centrally-triggered software Support for massive very important cost factor. Many IoT
upgrade, without any new hardware and devices must thus operate for
number of various
site visits needs. As a result both CAPEX a very long time.
and OPEX can be minimized. devices

Many devices will be located indoors,

To make simple, low data rates devices
often in basements (like smart meters)
popular and commonly used, total cost of
or in underground parking lots (parking
ownership must be really low.
control system). Enhanced coverage needed
Current target – device cost < 5USD. for proper handling of such devices is a must.

Low device cost $ Enhanced coverage

8 © Nokia 2016 Nokia Internal Use

Introduction
Radio technology space

• Coverage: 164 dB • Network upgrade: SW • Coverage: 156 dB • Network upgrade: SW

• Module cost: $2-4 • Spectrum: GSM /LTE • Module cost: $3-5 • Spectrum: LTE (1.4 MHz or
• Battery life: +10 years (200kHz or shared) • Battery life: +10 years shared)
• Scalability: +50k/cell* • Scalability: +50k/cell*
• Bit rate per UE : <56kbit/s • Bit rate per UE : <1Mbit/s

RAN Rel. 13 NB-IoT 200kHz RAN Rel. 13 LTE-M 1.4MHz

Massive IoT • Coverage: 164 dB • Network upgrade: SW
• Module cost: $3-5 • Spectrum: GSM (200kHz or
connectivity • Battery life: +10 years shared)
• Simple cheap devices • Scalability: +50k/cell*
• Low energy consumption • Bit rate per MS : <70kbit/s
• Massive number of devices
• Improved coverage, low datarate
Internet of Things GERAN Rel. 13 EC-GSM
*Note: Assumptions according to the Traffic Model defined by 3GPP (3GPP TS 45.820). Different assumptions will lead to different numbers.

9 © Nokia 2016 Nokia Internal Use

Introduction
Internet of Things example use cases classification

 Medium size messages

 Frequent in time Blood pressure
Fitness bands monitors Agriculture monitors Patient monitors
 Applicable where LTE system is already in place
Trackers:
 Network resources utilization: up to 6PRBs • Car tracker
 Coverage: up to 156 dB (Pathloss) • Kids tracker
• Pet tracker Smart Meters
Smoke detectors
Control Panels
Smart Watches
LTE-M
 Small messages
 Not frequent in time Blood pressure
Agriculture monitors
 Applicable where LTE system is already in place monitors

 Network resources utilization: 1PRB

 Coverage: up to 164 dB (Pathloss)
Smart Meters Smoke detectors
Control Panels NB-IoT
 Small messages
 Not frequent in time Blood pressure
Agriculture monitors
 Applicable where GSM system is already in place and no LTE monitors
 Network resources utilization: 1TSL for signalling and data
traffic multiplexed with legacy users
 Coverage: up to 164 dB (Pathloss) Smart Meters Smoke detectors
Control Panels EC-GSM

10 © Nokia 2016 Nokia Internal Use

Introduction
3GPP IoT traffic model (45.820 Annex E)

Report type Packet size Inter-arrival time

Mobile Autonomous Reporting (MAR) exception UL: 20 bytes Months to years (reaction time
reports up to 10 second latency)
 E.g. smoke detectors, power failure notifications from smart
meters, tamper notifications etc.

Mobile Autonomous Reporting (MAR) periodic UL: 20 - 200 bytes 40%: Once per day
reports Pareto distributed 40%: Once every 2 hours
15%: Once per hour
 E.g. smart utility (gas/water/electric) metering reports, smart
5%: Once per 30 min
agriculture etc. DL: Ack => Mean = 0.47 times per hour

Network originated reports DL: 20 bytes 40%: Once per day

 E.g. trigger the device to send an uplink report as a result of 40%: Once every 2 hours
15%: Once per hour
the network command e.g. request for a smart meter reading UL: 20 – 200 bytes 5%: Once per 30 min
Pareto distributed => Mean = 0.47 times per hour

Software update/reconfiguration model DL: 200 - 2000 bytes 180 days

 Software updates or patches of Cellular IoT devices. Rare, Pareto distributed
but large payload sizes expected for complete software
updates

11 © Nokia 2016 Nokia Internal Use

Introduction
NB-IoT 200kHz
Brief description NB-IoT
Impact on the Air 200kHz
Interface Dimensioning
• Narrowband LTE (NB-IoT) is designed for support of • HSDPA capacity is increased by 25%
Range <35km
low throughput, low complexity and low energy • HSUPA capacity is increased by 15%
consumption Machine Type Communications. Inband Battery life >10 years
operation with legacy LTE system is possible. • Lorem ipsum dolor sit amet, consectetuer
adipiscing elit,
• NB-IoT specified by Rel-13 3GPP TR 45.820 Frequency bands LTE bands
• sed diam nonummy nibh euismod tincidunt ut laoreet
dolore magna aliquam
Bandwidth erat
200kHz volutpat.
or shared
NB-IoT
GSM
channels
DL: OFDMA with 15 kHz subcarrier
200kHz
Impact on … spacing
Modulation UL: Single
• Ut wisi enim ad minim tone quis
veniam, nostrud–exerci
transmissions 3.75 and
NB-IoT 15 kHz, Multi-tone SC-FDMA with 15 kHz
tation ullamcorpersubcarrier
suscipit lobortis
spacing nisl ut aliquip ex
ea commodo consequat
NB-IoT Max throughput < 56 kbps UL, < 26kbps DL
• Nam liber tempor cum soluta nobis eleifend option
Linkcongue
budget nihil imperdiet doming id quod mazim
164 dB

Capacity +50k IoT devices per sector

12 © Nokia 2016 Nokia Internal Use

Introduction
NB-IoT 200kHz

• Single NB-IoT carrier occupies one LTE PRB in the 10 ms

frequency domain (180 kHz) NPUSCH NPUSCH

180 kHz
(6 tones) (6 tones)
• NB-IoT downlink: UL NPUSCH NPUSCH
(12 tones) (12 tones)
NPRACH

NPUSCH (3 tones)

• The same as for LTE - based on OFDMA with 15 kHz

subcarrier spacing. Also slot, subframe, and frame durations NPUSCH, single-tone
are identical to those in LTE as well as Number of OFDM
symbols per slot
• NB-IoT uplink: 3GPP defines multi-tone and single-tone
• Only Normal CP is supported for NB-IoT. transmissions
• Maintaining LTE structure for NB-IoT ensure • Multi-tone transmission is based on legacy LTE
orthogonality between the NB-IoT PRB and legacy LTE SC-FDMA with the same 15 kHz subcarrier spacing, 0.5
PRBs, valid especially for in-band scenarios ms slot, and 1 ms subframe.
1 ms

subframe subframe subframe subframe subframe subframe

• Two options for single-tone transmission exists: 15 kHz
and 3.75 kHz.
• The 15 kHz option is identical to LTE and thus
Same as LTE

slot slot

0.5 ms
achieves the best coexistence performance with LTE in
symbol symbol symbol symbol symbol symbol symbol the uplink
• Only 15 KHz UL single tone option selected for NPUSCH
CP signal
with LTE3071.
13 © Nokia Networks 2016 Nokia Internal Use
Introduction
NB-IoT 200kHz - Modes of operation

3GPP defines 3 different modes of operation

for NB-IoT:
• ‘In-band operation’ utilizing resource blocks
within a normal LTE carrier and shares
some HW and SW resources with host LTE NB-IoT
cell (FL17SP) GSM
channels
• ‘Stand-alone operation’ utilizing for example 200kHz
the spectrum currently being used by GERAN
systems as a replacement of one or more GSM
carriers, brand new cell without resource
sharing with other legacy LTE cells (FL17A) NB-IoT

• ‘Guard band operation’ utilizing the unused

resource blocks within a LTE carrier’s guard-
band (FL17A+) NB-IoT

14 © Nokia Networks 2016 Nokia Internal Use

Introduction
Low cost devices

Release 8 Release 8 Release 12 Release 13 Release 13

Category 4 Category 1 Category 0 Cat-M1 Cat-NB1
Downlink peak rate 150 Mbps 10 Mbps 1 Mbps 1 Mbps <26 kbps
Uplink peak rate 50 Mbps 5 Mbps 1 Mbps 1 Mbps <56 kbps

NB-IoT device is Number of antennas 2 2 1 1 1

Full/Half Half
characterized by Duplex mode Full duplex Full duplex Half duplex
duplex duplex
lower: complexity, UE receive
20 MHz 20 MHz 20 MHz 1.4 MHz 200 kHz
power consumption bandwidth
and the price UE transmit power 23 dBm 23 dBm 23 dBm 20 dBm 23 dBm
Modem complexity 100% 80% 40% 20% 15%

NB-IoT UE complexity reduction may be achieved due to half duplex, single

antenna usage and smaller bandwidth. At the same time it implies smaller data
rates, leading to smaller energy consumption as well as the lower device price.

15 © Nokia Networks 2016 Nokia Internal Use

Introduction
Coverage improvements

• IoT optimized technologies have target of 15-20 dB coverage improvement comparing to legacy
solutions
• One of the techniques is Power Spectral Density (PSD) boosting where less resources are used in
the frequency domain to concentrate transmitted power
• Repetition is also well known technique, wanted signal is constructed from many transmissions
• Note that coverage techniques compromise capacity and increase delays as more time is needed
for signal acquisition
Normal
operation PSD boosting PSD boosting + repetitions
resources
Spectrum

Data

Data Data Data

Time

16 © Nokia Networks 2016 Nokia Internal Use

Introduction
Before & after

Before After

• M2M/IoT traffic was served by legacy • NB-IoT technology was developed to

networks ineffectively serve massive number of IoT devices
• A lot of small messages would create • Optimized for improved coverage
control plane blocking • Simplified modem helps to reduce
• Problems with coverage for devices in implementation costs
critical locations • Easy deployment by software upgrade
• Modem cost blocks massive deployment of the legacy network

17 © Nokia 2016 Nokia Internal Use

LTE3071 NB-IoT

Technical Details

Table of contents

<chapter:technical_details>

18 © Nokia 2016 Nokia Internal Use

Technical Details Sales information
Dependency Table (LTE) BSW/ASW ASW
Release information
Release/version RL release eNodeB NetAct
FDD LTE FDD-LTE 17A FL17A NetAct 17.8
TDD LTE - - -
Flexi Zone Micro (FZM/FZP) FDD-LTE 17A FLF17A NetAct 17.8
Flexi Zone Controller (FZC) - - -
Single RAN SRAN17A SBTS17A NetAct 17.8

Release information – general

HW & IOT HW requirements MME SAE GW UE Specified by 3GPP
FSMF, FZM, (AirScale Rel. 13
Rel-13 TR 45.820
support comes with Cat-NB1
LTE3509)

19 © Nokia 2016 Nokia Internal Use

Technical Details
FL17A NB-IoT Overview
LTE carrier
Basic 3GPP Rel. 13 in-band NB-IoT functionality is
introduced with LTE 3071 feature.

NB IoT
- New cell concept and deployment options:
• FDD mode, half duplex operations, 200 kHz UE RF bandwidth
for both downlink and uplink
• DL: OFDMA with 15 kHz subcarrier spacing, TM2
• UL: single tone transmissions –15 kHz, 2 RX MRC* receiver
- The data transmission over SRB1bis (data over NAS) 10 ms

- First level coverage (without coverage enhancement) NPUSCH NPUSCH

180 kHz
(6 tones) (6 tones)
NPRACH
with MCL pathloss target up to 144dB is supported UL NPUSCH NPUSCH
(12 tones) (12 tones)
NPUSCH (3 tones)

- FSMF and FZM deployments

NPUSCH, single-tone

Airscale support comes separately with LTE3509

Higher coverage levels are supported with LTE3668 NB-IoT
Coverage Enhancements
Paging support for NB-IoT will be activated with LTE3669
MRC* Maximum Ratio Combining
20 © Nokia 2016 Nokia Internal
Technical Details
NB-IoT support for SRAN17A

• NB-IoT is introduced into SRAN with RP001597 feature

• The RP001597 feature basically consists of porting the below LTE features to SBTS:
• LTE3071 NB-IoT Inband
• LTE3509 NB-IoT: Inband on Airscale without Baseband Pooling
• LTE3668 NB-IoT: Coverage enhancements
• LTE3819 IoT: Cat-M and NB-IoT on same frequency carrier
• LTE3669 NB-IoT: Paging support
• RP001597 allows for:
• in-band NB-IoT cells on both FSMr3 and FSMr4 HW releases
• up to 20dB coverage enhancement so that to reach 164dB for the Maximum coupling loss (MCL) of
the NB-IoT cell
• simultaneous activation of Cat-M and in-band NB-IoT in a hosting LTE cell 2Tx2Rx 10MHz on FSMr3
• paging of NB-IoT UE for mobile terminated connections in normal or extreme coverage

21 © Nokia 2016 Nokia Internal

Technical Details
LTE 3071 NB-IoT – Inband operation

• One NB-IoT carrier can be configured for each legacy

5/10/15/20 MHz FDD LTE cell in a 2x2 configuration.
LTE carrier
• Allocation of DL NB-IoT carrier is predefined by 3GPP. The
location of downlink and uplink can be configured separately.
• Selected UL PRB should not overlap with PUCCH or PRACH

NB IoT
area (also with UL PUCCH area expansions).
• eNB power is shared between NB-IoT and LTE, power
ramping
for NB-IoT is possible.
• Dedicated RRC connected limit for NB-IoT UEs. This static
limit reduces number of legacy RRC connected UEs to keep
the total eNB limit unchanged.
• There is no paging support with LTE3071, hence only mobile
originated calls can be handled.
22 © Nokia 2016 Nokia Internal Use
Technical Details
LTE 3071 NB-IoT – Inband operation

• Since the same OFDM modulation with 15 kHz R1 R0 R1 R0 R1 R0 R1 R0

subcarrier spacing is used in DL there is no

interference between R0 R1 R0 R1 R0 R1 R0 R1

NB-IoT and legacy LTE, providing that NB-IoT signals R1 R0 R1 R0 R1 R0 R1 R0

are not mapped to the resource elements occupied by

1 PRB

1 PRB
the legacy LTE. R0 R1 R0

NB-IoT
R1 R0 R1 R0

NB-IoT
R1

• A protection of legacy cell resource elements is R1 R0 R1 R0 R1 R0 R1 R0

supported for the fixed first 3 OFDM symbols R0 R1 R0 R1 R0 R1 R0 R1

(wideband PDCCH area) and for CRS area. NB-IoT is

punctured out to accommodate legacy LTE control R1 R0 R1 R0 R1 R0 R1 R0

channels and CRS. (a) Downlink in-band operation

• With LTE3071 only one NB-IoT PRB per hosting LTE

cell is supported. Hosting legacy cell PCI is used for
NB-IoT.
• Dedicated power settings can be applied for NB-IoT
23 ©resource
Nokia 2016 elements, the maximum
Nokia Internal Use DL power offset is 6
Technical Details
Channel Raster
• According to 3GPP LTE carriers are allocated with 100 kHz channel raster, and channel center refers to
the unused DC subcarrier in LTE. NB-IoT carrier center refers to the PRB center.
• There is frequency offset between center of legacy LTE + multiple of 100kHz and center of NB-LTE carrier,
depending whether even or odd number of PRBs are in use
10/20MHz - {2.5kHz, 17.5kHz,
22.5kHz, 37.5kHz, 42.5kHz}.
5/15MHz - {7.5kHz, 12.5kHz,
27.5kHz, 32.5kHz, 47.5kHz}.

fLTE=100n kHz fLTE=100n kHz

fNB-IoT=(100n-180m-7.5)kHz fNB-IoT=(100n+180m+7.5)kHz fNB-IoT=(100n-180m-97.5)kHz fNB-IoT=(100n+180m+97.5)kHz

(180m-7.5) kHz (180m+7.5) kHz (180m-97.5) kHz (180m+97.5) kHz

5/15 MHz LTE, m=4,5,6… 10/20 MHz LTE, m=3,4,5…
24 © Nokia 2016 Nokia Internal Use
Technical Details
PRB selection for in-band operation
• NB-IoT UE follows 3GPP raster rules; it means that is tuned not to the PRB center, but 100kHz multiplicity
• NB-IoT carrier is used for UE initial synchronization, that is why frequency error have to be minimized, and PRB
indexes with the lowest offset selected (+/-7.5 or 2.5 kHz). They are referred as an anchor carriers
(NBIOT_FDD: inbandPRBIndexDL) . Middle 6 PRBs of the LTE carrier are restricted due to occupation by
synchronization and broadcast channels
PRB index 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
PRB offset 12 11 10 9 8 7 6 5 4 3 2 1 1 2 3 4 5 6 7 8 9 10 11 12
PRB frequency 5832.5 6012.5 6192.5 6372.5 6552.5 6732.5 6912.5 7092.5 7272.5 7452.5 7632.5 7812.5 8187.5 8367.5 8547.5 8727.5 8907.5 9087.5 9267.5 9447.5 9627.5 9807.5 9987.5 10168

if (odd bandwidth and offset <0) FDL_delta = - 180*m - 7.5kHz if (odd bandwidth and offset >0) FDL_delta = + 180*m + 7.5kHz

LTE system bandwidth 5 MHz 10 MHz 15 MHz 20 MHz

2, 7, 12, 17, 22, 27, 32, 42, 47, 4, 9, 14, 19, 24, 29, 34, 39, 44, 55,
DL PRB indices 2, 7, 17, 22 4, 9, 14, 19, 30, 35 40, 45
52, 57, 62, 67, 72 60, 65, 70, 75, 80, 85, 90, 95

• NB-IoT UL PRB can be configured from any uplink PRB (NBIOT_FDD: inbandPRBIndexUL) not used for
PRACH/PUCCH and possible PRACH/PUCCH if dynamic PUCCH enabled in host LTE cell.
• PRB from the outer region outside area in host LTE cell by PUCCH blanking.
• PRB from the inner region of PUSCH. The adjacent PRB near PUCCH is preferred to avoid uplink resource fragment if dynamic
PUCCH is not enabled.
25 © Nokia 2016 Nokia Internal Use
Technical Details
NB-IoT – Downlink
• DL uses OFDMA with 15 kHz subcarrier spacing, 12 subcarriers available in 1 NB-IoT carrier,
10ms frame, 100 kHz channel raster

• Narrow 200 kHz UE bandwidth does not allow for legacy channels utilization, new DL channels:
• Narrowband Primary and Secondary Synchonization signals NPSS/NSSS - time/frequency synchronization,
cell ID and timing for NPBCH detection.
• Narrowband Common Reference Signals NRS for 2 antenna ports transmission schemes
• Narrowband Physical Broadcast Channel NPBCH conveys Narrowband Master Information Block MIB-NB.
• Narrowband Physical Dowlink Control Channel NPDCCH carries scheduling information for both DL and UL
data channels, HARQ ack and random access response scheduling information.
• Narrowband Physical Dowlink Shared Channel NPDSCH carries data from the higher layers, system
information and the random access response messages.

26 © Nokia 2016 Nokia Internal Use

Technical Details
NB-IoT – Uplink Physical Channels

• Narrowband Physical Random Access Channel NPRACH carries preamble for Random Access
procedure. NPRACH operates on 3.75 kHz subcarrier spacing and predefined hopping schemes with
repetitions.
• Narrowband Physical Uplink Shared Channel NPUSCH. Among several NPUSCH transmissions
options defined by 3GPP (single-, multi-tone, 15 or 3.75 kHz subcarrier spacing) 15 kHz single-tone
will be supported for FL17SP LTE3071, 12 subcarriers available.
• The use of a dedicated PUCCH, as used in LTE for carrying uplink control information, is not
necessary as its function can be integrated to NPRACH and NPUSCH. ACK/NACK is carried by the
NPUSCH, no CQI and SR support. 48 subcarriers x 3.75 kHz
12 subcarriers x 15 kHz

NPUSCH
180 KHz

180 KHz

12x single
carrier 15kHz

8 ms Single UE NPRACH, 4 repetitions, 4 x (4 x 1.6ms) = 25.6 ms

27 © Nokia 2016 Nokia Internal Use

Technical Details

NPSS/NSSS

28 © Nokia 2016 Nokia Internal Use

Technical Details
NPSS
• Two synchronization channels are available:
primary NPSS and secondary NSSS.
• NPSS is used for a first frame and subframe
synchronization, with NPSS UE determines the frame
boundary.
• NPSS carries Zadoff-Chu sequence mapped to the lowest
LTE PDCCH
11 subcarriers within the NB-IoT PRB. The sequence is
LTE CRS
fixed and therefore carries no information about cell id.
•
NPSS
NPSS is transmitted every 10 ms in subframe #5 and
occupies the last 11 OFDM symbols of the subframe.
• NPDSCH/NPDCCH are not mapped to subframes
containing NPSS, no NRS on subframes containing NPSS
• NPSS is punctured by LTE CRS

29 © Nokia 2016 Nokia Internal Use

Technical Details
NSSS
• NSSS (Narrowband Secondary Synchronisation Signal) indicates
PCID and 80 ms boundary (for NPBCH detection).
In LTE3071 the PCID is same as legacy host LTE cell.
• The NSSS sequence is generated from a length-131 frequency
domain Zadoff-Chu sequence, binary scrambled and cyclically
shifted depending on the radio frame number.
LTE PDCCH
• The root of the ZC sequence and binary scrambling sequence
LTE CRS
are determined by narrowband physical cell identity NPCID.
Like in LTE, 504 PCI values are defined. NSSS

• 80 ms boundary is indicated by one of 4 time-domain cyclic shifts

• NSSS is transmitted in subframe #9, every even number radio
frame, uses 12 subcarriers and occupies the last 11 OFDM
symbols of the subframe.
• NPDSCH/NPDCCH are not mapped to subframes containing
NSSS, no NRS on subframes containing NSSS, punctured by LTE
CRS.

30 © Nokia 2016 Nokia Internal Use

Technical Details

NRS

31 © Nokia 2016 Nokia Internal Use

Technical Details
NRS
• The downlink cell specific physical reference N0 N1 N0 N1 LTE CRS
signal NB-IoT (NRS) is used to channel
estimation and measurement purposes. N0 NRS-Antenna Port 0
N1 N0 N1 N0
• NB-IoT uses the same PCI as host cell, it is N1 NRS-Antenna Port 1
indicated in MIB.
• Since only 2 antenna ports are supported in N0 N1 N0 N1
LTE3071 for NB-IoT, also host cell
configuration is fixed to 2 antenna ports
only. N1 N0 N1 N0

• NRS is defined for 2 antenna ports transmission

schemes. NRS uses a cell-specific frequency
shift derived as NB-IoT Cell ID mod 6.
• There are no NRS in subframes containing
NPSS/NSSS
• NRS can be boosted by up to 6 dB, power offset
is indicated in SIB.
32 © Nokia 2016 Nokia Internal Use
Technical Details

NPBCH

33 © Nokia 2016 Nokia Internal Use

Technical Details
NPBCH
• NPBCH (Narrowband Physical Broadcast
Channel) is used to carry the Narrowband Master LTE PDCCH
Information Block (MIB-NB)
LTE CRS
• NPBCH is transmitted every 10 ms in subframe #0
NRS antenna port 0
• NPDSCH/NPDCCH are not mapped to subframes
NRS antenna port 0
containing NPBCH
• The modulation is QPSK, thus in each subframe NPBCH

#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
reference signal (NRS).
elements (4 antenna ports).

34 © Nokia 2016 Nokia Internal Use

Technical Details

System Information

35 © Nokia 2016 Nokia Internal Use

Technical Details
Narrowband System Information SI-NB
• There are new narrowband dedicated versions of System Information Broadcast:
MIB-NB, SIB1-NB, SIB2-NB. All other system information blocks (without NB suffix) are not applicable
to NB-IoT.
• UE shall neither initiate the RRC connection establishment procedure until a valid version of the MIB-
NB, SIB1-NB and SIB2-NB are gathered.

MIB-NB defines the most essential information of the cell required to receive further system
information; contains all information required to acquire SIB1-NB. Fixed schedule with a periodicity
of 640 ms.

SIB1-NB cell access/selection, contains all information required to acquire other SI-NB messages.
Fixed schedule with a periodicity of 2560 ms.

SIB2-NB radio resource configuration information; SIB2-NB periodicity is indicated within SIB1-NB
message.

36 © Nokia 2016 Nokia Internal Use

 Technical Details
MIB-NB scheduling
• 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, respectively. It means that each block spans 80 ms. All 8 repetitions are identical in
terms of coded and scrambled bits.
• 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

37 © Nokia 2016 Nokia Internal Use

Technical Details
MIB-NB content
Field Size (bit s)
SFN Most signif icant bit s (MSBs), t he remaining LSBs are implicit ly derived f rom t he MIB-
SFN 4
NB st art (64 f rames st art ing f rom 000000, t he last radio f rame: 111111)
HyperSFN 2 Two LSBs of t he hyper f rame number. Remaining bit s present in SIB1-NB.
NB-SIB1 scheduling info 4 SIB1-NB scheduling and size,
Syst em info value t ag 5 Value t ag, changed t o announce changes in SI-NB ot her t han MIB-NB.
Access barring info 1 In LTE3071, access barring is not support ed and t he f ield always set t o 'FALSE'
Operat ion mode 2 Inband f or LTE3071
Based on operat ion mode
Indicat es an in-band deployment and t hat t he NB-IoT and LTE cell share t he same
(1) in-band wit h CRS and physical cell id and have t he same number of NRS and CRS port s. In LTE3071, if t he host
5
same PCI PRB info cell is using 2TX and if operat ion mode is inband (i.e. act NBIoT = 'INBAND',), eNB will
broadcast t his f ield.
Num of LTE
1
CRS port s
(2) in-band wit h 5
Rast er
different PCI 2
offset
Spare 2
Rast er
2
(3) guard-band offset
Spare 3
(4) st and-alone Spare 5
Spare 11
CRC 16
Tot al Size 50

38 © Nokia 2016 Nokia Internal Use

Technical Details
SIB1-NB scheduling
• SIB1-NB contains the scheduling Starting radio frame
Value of Number of
information for the SI-NB message schedulin NPDSCH
SIB1-NB TBS
R NB-SIB1 PCID number for NB-SIB1
repetitions
gInfoSIB1- repetition
common setting: window, radio frame NB-r13 s
PCID mod 4 = 0 SFN mod 256 = 0
PCID mod 4 = 1 SFN mod 256 = 16
offset, and SI-NB message specific 0 4 208 4
PCID mod 4 = 2 SFN mod 256 = 32

setting: periodicity, repetition pattern and 1 8 208 PCID mod 4 = 3 SFN mod 256 = 48
2 16 208 PCID mod 2 = 0 SFN mod 256 = 0
TBS. 3 4 328
8
PCID mod 2 = 1 SFN mod 256 = 16
PCID mod 2 = 0 SFN mod 256 = 0
328
•
4 8 16
TBS for SIB1-NB and the repetitions 5 16 328
PCID mod 2 = 1 SFN mod 256 = 1

made within the 2560 ms are indicated 6 4 440

7 8 440 NBIOTPR:
by schedulingInfoSIB1-NB-r13 field in 8 16 440 numSib1RepNB
the MIB-NB. 9 4 680
10 8 680
• The starting frame for the first 11 16 680
transmission of the SIB1-NB is derived 12~15 Reserved Reserved

from the cell PCID and the number of

repetitions within the 2560 ms period The eNB determines the TBS for SIB1-NB by choosing the smallest one
from {208, 328, 440, 680} which is equal to or larger than the SIB1-NB message size

39 © Nokia 2016 Nokia Internal Use

Technical Details
SIB1-NB scheduling
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 DL 0 1 2 3 4 5 6 7 8 9

second frame, 8 subframes sequence. SIB1-NB TB is Starting radio frame

composed of 8 NB-IoT downlink subframes. R NB-SIB1 PCID number for NB-SIB1
repetitions

• Within 256 radio frames period SIB1-NB sequence is PCID mod 4 = 0 SFN mod 256 = 0
PCID mod 4 = 1 SFN mod 256 = 16
repeated 4, 8 or 16 times, depending on the 4
PCID mod 4 = 2 SFN mod 256 = 32

schedulingInfoSIB1-NB-r13. Repetitions are equally PCID mod 4 = 3 SFN mod 256 = 48

PCID mod 2 = 0 SFN mod 256 = 0
distributed within 256 frames period. 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

40 © Nokia 2016 Nokia Internal Use

Technical Details
Main SIB1-NB fields for SIB2-NB message scheduling
Field comments
Indicates the control region size of the • SIB2-NB messages are transmitted
eutraControlRegionSize- E-UTRA cell for the in-band operation periodically within time domain windows
r13 mode, in number of OFDM symbols. In
LTE3071, fixed value of 3 symbols.
(SI-window, NBIOTPR: siWindowLenNB).
• SIB2-NB TBS is determined by eNB by
nrs-CRS-PowerOffset-r13 NRS power boost selecting the smallest value from the SI TBS
pool {b56, b120, b208, b256, b328, b440,
Periodicity of the SI-message in radio
b552, b680}, big enough to carry SIB
si-Periodicity-r13 frames
NBIOT_FDD->sib2PeriodicityNB. content.
si-RepetitionPattern-r13 NBIOT_FDD->sib2RepPatternNB. • Depending on the TBS configuration
TBS size, calculated value based on SIB
SIB2-NB is transmitted over 2 or 8
si-TB-r13 consecutive NB-IoT downlink subframes
message size
Common SI scheduling window for all within SI-window
si-WindowLength-r13 SIs. Unit in milliseconds (56/120 bits 2, remaining 8 subframes)
NBIOT_FDD->siWindowLenNB
Offset in number of radio frames to
calculate the first radio frame for SI
si-RadioFrameOffset-r13 message transmission in the SI window. If
the field is absent, no offset is applied.
NBIOT_FDD->siRadioFrameOffNB
41 © Nokia 2016 Nokia Internal Use
Technical Details
SIB2-NB scheduling example
subframe
SFN
0
0 1 2 3 4
SIB1
5
NPSS
6 7 8 9
NSSS
siRadioFrameOffNB=2
• SIB2-NB is broadcasted in the valid sub-
1 8 consecutive valid subframes NPSS
offset

2
3
SIB2,r0,t0 SIB2,r0,t1 SIB2,r0,t2
SIB2,r0,t6 SIB2,r0,t7
SIB1 NPSS
NPSS
SIB2,r0,t3 SIB2,r0,t4 SIB2,r0,t5 NSSS frames, except for NPSS/ NSSS/ NPBCH/
4
MIB
SIB1 NPSS sib2RepPatternNB=every4th NSSS SIB1-NB.

siWindowLenNB=160ms
5 NPSS
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
• Single SIB2-NB is transmitted over 2 or 8

sib2PeriodicityNB=256
SI window
8 SIB1 NPSS NSSS
9 NPSS

SI-periodicity
10
11
SIB2,r2,t0 SIB2,r2,t1 SIB2,r2,t2
SIB2,r2,t6 SIB2,r0,t7
SIB1 NPSS
NPSS
SIB2,r2,t3 SIB2,r2,t4 SIB2,r2,t5 NSSS consecutive valid subframes. Offset in
MIB
12
13
SIB1 NPSS
NPSS
NSSS
radio frames for the start of the SI window
14
15
SIB2,r3,t0 SIB2,r3,t1 SIB2,r3,t2
SIB2,r3,t6 SIB2,r3,t7
SIB1 NPSS
NPSS
SIB2,r3,t3 SIB2,r3,t4 SIB2,r3,t5 NSSS
siRadioFrameOffNB
16 SIB1 NPSS NSSS

•
17 NPSS
SIB2-NB is repeated every
MIB

MIB NPSS
….
…… NSSS SIB1 SIB2 …
sib2RepPatternNB frame (example: every
…
… ... …
… 4th frame)
256 SIB1 NPSS NSSS
offset

•
257 NPSS
258
259
SIB2,r0,t0 SIB2,r0,t1 SIB2,r0,t2
SIB2,r0,t6 SIB2,r0,t7
SIB1 NPSS
NPSS
SIB2,r0,t3 SIB2,r0,t4 SIB2,r0,t5 NSSS Repetitions are within SI-window,
MIB
260
261
SIB1 NPSS
NPSS
NSSS
siWindowLenNB
262 SIB2,r1,t0 SIB2,r1,t1 SIB2,r0,t2 SIB1 NPSS SIB2,r1,t3 SIB2,r1,t4 SIB2,r1,t5 NSSS

•
263 SIB2,r1,t6 SIB2,r1,t7 NPSS
264
265
SIB1 NPSS
NPSS
NSSS Whole SIB2-NB sequence is transmitted
266
267
MIB
SIB2,r2,t0 SIB2,r2,t1 SIB2,r2,t2
SIB2,r2,t6 SIB2,r0,t7
SIB1 NPSS
NPSS
SIB2,r2,t3 SIB2,r2,t4 SIB2,r2,t5 NSSS
every sib2PeriodicityNB period
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

42 © Nokia 2016 Nokia Internal Use

Let’s have a short coffee break!

43 © Nokia 2016 Nokia Internal Use

LTE3071 NB-IoT

NPDCCH

44 © Nokia 2016 Nokia Internal Use

Technical Details
NPDCCH
• NPDCCH Narrowband Physical Downlink Control Channel LTE PDCCH

• Scheduling information for both DL and UL data LTE CRS

channels (DCI)
CCE0
• UL data channel HARQ acknowledgement
CCE1
• Random access response (RAR) scheduling
NRS antenna port 0
information.
NRS antenna port 1
• 3 OFDM symbols are reserved for legacy LTE control
region, as well as legacy CRS for 2 LTE antenna ports and
For LTE3071 2 CCEs are aggregated
NB-IoT NRS for 2 antenna ports
to carry single DCI in one subframe
• 2 Control Channel Elements CCEs are defined - upper 6 (NPDCCH format 1 and aggregation
subcarriers are allocated to one CCE and lower 6 level 2)
subcarriers are allocated to the It allows utilization of a lower coding
other CCE. rate and improved coverage.
• QPSK and TM2 is supported.

45 © Nokia 2016 Nokia Internal Use

Technical Details
DCI Formats

• DCI (Downlink Control Information) is used to signal UL and DL scheduling grants to the UE
DCI N0 for UL grant
Relevant fields: Flag for Format N0/N1 differentiation, NPUSCH resources, MCS, NDI, UL HARQ.

DCI N1 for DL grant

Relevant fields: Flag for Format N0/N1 differentiation, NPDSCH resources, MCS, NDI.

• During Random Access procedure UE has been assigned with different radio network temporary
identifier (RNTI), one for random access (RA-RNTI), and a UE specific identifier (C-RNTI). Identifiers
are implicitly indicated in the NPDCCH's CRC.
• DCI CRC scrambled with C-RNTI  the first bit in the message indicates whether DCI format N0
or N1 is contained. DCI CRC is scrambled with the RA-RNTI  DCI format N1.

46 © Nokia 2016 Nokia Internal Use

Technical Details
DCI Formats

• DCI format N0 is used for the scheduling of NPUSCH.

N0 (NPUSCH scheduling) The relevant field for DCI format N0 is:

Field Size (bits)
• Flag for format N0/N1 differentiation
Flag for N0/N1 differentiation 1
Subcarrier indication 6
• Subcarrier indication
Resource assignment 3
• Resource block assignment
Scheduling delay 2 • Modulation and coding scheme and redundancy
MCS 4 version
RV 1 • New data indicator
Repetition number 3 • Cyclic shift for DM RS and OCC index
NDI 1 • The rest is ignored.
DCI subframe repetition number 2
CRC 16
Total 39

47 © Nokia 2016 Nokia Internal Use

Technical Details
DCI Formats

• DCI format N1 is used for the scheduling of NPDSCH.

N1 (NPDSCH scheduling ) The relevant field for DCI format N1 is:
Field Size (bits)
• Flag for format N0/N1 differentiation
Flag for N0/N1 differentiation 1
• Resource block assignment
NPDCCH order indicator 1
Scheduling delay 3
• HARQ assignment
Resource assignment 3
• Modulation and coding scheme
MCS 4 • New data indicator
Repetition number 4 • The rests are ignored.
NDI 1
HARQ-ACK resource 4
DCI subframe repetition number 2
CRC 16
Total 39

48 © Nokia 2016 Nokia Internal Use

Technical Details
NPDCCH Search Space

• All the possible DL locations for NPDCCH are called 'Search Spaces’.
• CSS Common search space is defined for RARs, MSG3 retransmission and MSG4, USS UE specific
search space is all valid PDCCH opportunities.
• Initial DCI repetition is hardoced to 2 with the maximum number of repetitions Rmax
NBIOTPR: npdcchMaxNumRepRa.

• NPDCCH opportunities are available in all subframes which are not occupied by static allocations
(NPBCH, NPSS/NSSS, SIB1-NB/SIB2-NB).
• Example for Common USS and CSS search space:
G=2, Rmax=4, T=8
FN 0 1 2 3
SFN 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
Excluded MIB SIB1 PSS SSS MIB PSS MIB SIB1 PSS SSS MIB PSS
Search space
NPDCCH occasion 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2

49 © Nokia 2016 Nokia Internal Use

LTE3071 NB-IoT

NPDSCH

50 © Nokia 2016 Nokia Internal Use

Technical Details
NPDSCH

• Narrowband Physical Downlink Shared Channel NPDSCH carries

data from the higher layers, system information and the RAR
messages
• 3 OFDM symbols are reserved for legacy LTE control region, as
well as legacy CRS for 2 LTE antenna ports and NB-IoT NRS for 2
antenna ports, thus 104 REs are available per subframe. 12
subcarriers allocation is always used.
NRS LTE PDCCH
• NPDSCH codeword occupies the entire PRB and is mapped to
NPDSCH LTE CRS
the 4 subsequent valid subframes. Time extension for NPDSCH
will be supported.
• No repetition is provided for LTE3071 (only normal coverage
supported), apart from NPDSCH carrying SIB content.
• The modulation is QPSK (MCS0-10), only TM2 is supported. No
Link adaptation, user selected MCS.

51 © Nokia 2016 Nokia Internal Use

Technical Details
NPDSCH

• A maximum transport block size (TBS) of 680 bit is supported with

4 subframes (tail biting convolutional code, QPSK)
MCS/TBS size definition
• Single process HARQ with adaptive and asynchronous re-transmission 4
ITBS subframes
• All the subframes that contain NPSS/NSSS/NPBCH/SIB1-NB are not Bits
available for NPDSCH transmission (valid DL subframe). 0 88
1 144
• NPDSCH is allocated in 4 consecutive NB-IoT DL subframe(s) not 2 176
excluded for NPSS/NSSS or used for SI messages transmission. 3 208
4 256
5 328
6 392
FN 0 1 2 7 472
SFN 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 8 536
MIB SIB1 PSS SSS MIB SIB1 PSS MIB SIB1 PSS SSS 9 616
Valid SF 10 680

52 © Nokia 2016 Nokia Internal Use

Technical Details
NPDSCH Scheduling

4ms*
NPDCCH NPDSCH NPDCCH
Peak DL throughput: 680bits/4ms=170kbps
680 bits Sustained DL throughput: 680bits/27ms=26kbps
* 4ms is the best case; actual timing depends on the number of free
NPUSCH (A/N)
subsequent subframes dictated by SIB1 occurrence, see slide 50

27ms

• NPDSCH transmission starts in the valid DL subframe at least 4 ms after the end of associated DCI format N1
conveyed via NPDCCH. The reason of such gap is reduced computing capability of low cost IoT devices, they need
time for NPDCCH decoding.
• After NPDSCH transmission completed, the UE needs to send back HARQ acknowledgement using NPUSCH
Format 2. The allocation of NPUSCH resources for HARQ are indicated in DCI.
• Again, due to the limited computing resources of IoT device, time offset between the end of NPDSCH and the
associated HARQ ACK is needed. At least 12 ms, since NPDSCH transport block is up to 680 bits, while DCI is
only 23 bits.
• Next scheduling request conveyed by NPDCCH is expected not earlier than 3ms, in the next search space.

53 © Nokia 2016 Nokia Internal Use

LTE3071 NB-IoT

NPRACH

54 © Nokia 2016 Nokia Internal Use

Technical Details
NPRACH
• Narrowband Physical Random Access Channel NPRACH transmits preamble for RACH
procedure. NPRACH is used to signal to the cell that the UE is camping on it and wants to get
access.
• The preamble is based on symbol groups on a single subcarrier. Each symbol group has a cyclic
prefix (CP) followed by 5 symbols.

• Preamble formats 1 is used, with CP length of 266.7 μs it gives up to 35 km maximum cell range.
The five symbols have a duration of 1.333 ms, giving a total length of 1.6 ms.

55 © Nokia 2016 Nokia Internal Use

Technical Details
NPRACH
• NPRACH is based on 3.75 kHz single-tone with frequency hopping. One NPRACH preamble
consists of 4 symbol groups, transmitted without gaps.
• UE selects the subcarrier for the transmission of the first preamble symbol group. The next 3 symbol
groups are determined by an algorithm which depends only on the location of the first one.
• First level single-subcarrier hopping is used between 1st/2nd and between 3rd/4th symbol groups (3.75 kHz)
• Second level 6-subcarrier hopping is used between 2nd/3rd symbol groups (22.5 kHz, 6-subcarriers)

Frequency Random hopping • Pseudo-random hopping is used

CP
symbol group
CP
between repetitions of groups of 4
CP symbol group
CP
• Each sequence is repeated (default 4
22.5 kHz
22.5 kHz
times)
CP

CP 3.75 kHz
CP

CP 3.75 kHz
NPRACH sequence
1st repetition
1 PRACH Tx = 4 symbol groups 1 PRACH Tx = 4 symbol groups
NPRACH sequence
Time

56 © Nokia 2016 Nokia Internal Use

Technical Details
NPRACH configuration
• Time domain:
• NPRACH starts from frame defined by NBIOTPR: nprachStartTime, repeated every NBIOTPR: nprachPeriod
(default 160 ms) and within each period there are repetitions set by NBIOTPR: nprachNumRepPreamble
(default 4 repetitions).
• Frequency domain:
• The full NPRACH bandwidth is 180kHz with 48 subcarriers (3.75kHz each)

48 subcarriers x 3.75 kHz

12 subcarriers x 15 kHz

NPRACH NPRACH NPRACH NPRACH The Random

PUSCH
sequence
4 x 1.6 ms = 6.4
repetition repetition repetition Access

180 KHz
Preamble ID
180 KHz

12x single ms

carrier 15kHz corresponds to

the start
subcarrier index
of NPRACH
8 ms Single UE NPRACH, 4 repetitions, 25.6 ms

4xNPRAC NPUSCH area 4xNPRAC NPUSCH

H 25.6ms H 25.6ms area
NPRACH
starting time NPRACH period 160ms

57 © Nokia 2016 Nokia Internal Use

Technical Details
NPRACH multiplexing
• NB-IoT UEs can are multiplexed in the subcarrier frequency domain when accessing NPRACH
resources
• The hopping pattern is semi-statically configured (3.75/22.5/3.75KHz, pseudo-random offset in the
subcarriers domain for the next sequence of 4 NPRACH), then if collision for the first NPRACH
occurrence is avoided, overlapping on the subsequent NPRACHes does not appear.
Subcarrier index
47
.
.
.
11
NPRACH multiplexing
example for 12
subcarriers (Note: for the
sake of simplicity; for
LTE3071 all the 48
subcarriers are
Time available)
0

58 © Nokia 2016 Nokia Internal Use

Technical Details
Random Access UE eNB

• Random Access procedure of NB-IoT is similar to legacy LTE,

contention-based random access procedure.

raRespWinSizeNB
Random Access
1. UE transmits a Random Access Preamble via NPRACH format 1. NPRACH msg1
In case preamble transmission is not successful, UE repeats it RAR scheduling
according to the NBIOTPR: nprachMaxNumPreambleCE settings NPDCCH

(default 5). Random Access Response

msg2
NPDSCH
2. The eNB calculates the RA-RNTI based on the first radio frame RRC: Connection Request
number which the preamble was received. RA-RNTI=1+ SFN_id/4, msg3

raContResoTimNB
NPUSCH

where SFN_id is the index of the first radio frame of the specified RRCConnectionSetup scheduling
NPDCCH
NPRACH.
RRCConnectionSetup-NB
msg4
3. The eNB sends DCI Format N1 for Random Access Response RAR NPDSCH

scheduling over NPDCCH. Related DCI is recognized by UE since it RRCSetupComplete scheduling

is scrambled with the RA-RNTI. NPDCCH

RRCConnectionSetupComplete-NB
4. Then RAR (msg2) is sent over NPDSCH, containing timing NPUSCH
msg5
advance command and allocation of uplink resources for
scheduled transmission. RAR is expected inside the RAR response
window NBIOTPR: raRespWinSizeNB.
59 © Nokia 2016 Nokia Internal Use
Technical Details
Random Access UE eNB

5. The UE sends RRCConnectionRequest-NB (msg3) over NPUSCH

6. The eNB sends DCI Format N1 for RRCConnectionSetup-NB (msg4)

raRespWinSizeNB
Random Access
scheduling over NPDCCH. NPRACH msg1

7. The eNB sends RRCConnectionSetup-NB (msg4) over NPDSCH, RAR scheduling

NPDCCH
inside the contention resolution timer NBIOTPR: raContResoTimNB
Random Access Response
to indicate the successful completion of the RACH procedure. NPDSCH
msg2

8. In case msg4 is not received within timer period, RACH access RRC: Connection Request
msg3

raContResoTimNB
NPUSCH
procedure is repeated, providing that nprachMaxNumPreambleCE

T300-NB
RRCConnectionSetup scheduling
settings is not reached NPDCCH

9. The eNB sends scheduling of RRCConnectionSetupComplete-NB RRCConnectionSetup-NB

msg4
NPDSCH
(msg5) in DCI Format N0
RRCSetupComplete scheduling
10. The UE sends RRCConnectionSetupComplete-NB (msg5) over NPDCCH

NPUSCH, and moves into RRC_Connected mode. RRCConnectionSetupComplete-NB

NPUSCH
msg5
Timer T300-NB supervises the RRC connection establishment procedure for NB-IoT.
Timer guard the period between RRCConnectionRequest and reception of RRCConnectionSetup
or RRCConnectionReject message for NB-IoT.

60 © Nokia 2016 Nokia Internal Use

LTE3071 NB-IoT

NPUSCH

61 © Nokia 2016 Nokia Internal Use

Technical Details
NPUSCH
• The eNB supports 15kHz single-tone NPUSCH in LTE3071, 12 tones. Single-tone operation together with 4RU
ITBS
close to 0 dB PAPR modulations helps to ensure coverage extension by PSD boosting. Bits
0 88
• NPUSCH format 1 is for UL-SCH data (Resource unit RU=8ms) 1 144
• NPUSCH format 2 is for UL control information (ACK/NACK, RU=2ms). 2 176
3 208
• For format 1, Turbo coding with 2 redundancy versions (RV0 and RV2) are used. To reduce peak-to-
4 256
average power ratio (PAPR), single-tone transmission uses π/2-BPSK and π/4-QPSK with phase
5 328
continuity between symbols. For format 2, only π/2-BPSK is supported
6 392
• 1 HARQ process with adaptive asynchronous HARQ is used for re-transmissions. 7 472
• One transport block can be scheduled over more than 1 resource units in time in 3GPP, For LTE3071, 8 536
fixed 4 RU is supported for format1 (4*8ms=32 ms) and 1RU for format2 (2 ms). 9 616
10 680
12 subcarriers x 15 kHz

Format1 transport block= 4RU = 32 ms Format2 transport block= 1RU = 2 ms

180 KHz

1RU = 8 ms

62 © Nokia 2016 Nokia Internal Use

Technical Details
NPUSCH scheduling
• A grant for NPUSCH transmission is indicated in the NPDCCH via DCI format N0.
• Start time of the NPUSCH, the number of repetitions (hardcoded to 1), the number of RUs used for one transport
block (hardcoded to 4 for format 1) and subcarrier position
• MCS index and the transport block size
• For normal coverage supported with LTE3071 no NPUSCH repetition is foreseen
• The time offset between the end of NPDCCH and the beginning of the associated NPUSCH is at
least 8 ms. After completing the NPUSCH transmission, the UE monitors NPDCCH to learn
whether NPUSCH is received correctly by the base station, or a retransmission is needed.

Peak DL throughput: 680bits/32ms=21kbps

Sustained DL throughput: 680bits/45ms=15.1kbps
NPDCCH NPDCCH
32ms *2 ms (2xNPDCCH) + 8 ms + 32 ms (NPUSCH) + 3 ms = 45 ms

680 bits The ACK/NACK is transmitted in NPDCCH by the new data

indicator (NDI) in the DCI format N0. Positive UL HARQ
NPUSCH
45ms* feedback is signaled via toggled NDI, or for the last UL data
transmission no feedback at all. Negative UL HARQ
feedback is signaled via non-toggled NDI.

63 .
© Nokia 2016 Nokia Internal Use
LTE3071 NB-IoT

Power Control

66 © Nokia 2016 Nokia Internal Use

Technical Details
Power Control
• Static power allocation for DL is used by eNodeB.
• The NB-IoT downlink power boost parameter (dlPwrBoost) is employed in inband NB-IoT PRB.
• In UL direction open loop power control is supported.
• Initial power level derived from RACH preamble process is used for the whole duration of the RRC
connection
• Power headroom
Measured quantity
Reported value
• NB-PHR is computed based on a 15kHz single-tone value (dB)
POWER_HEADROOM_0 [-23]  PH  [5]
transmit power for NPUSCH data POWER_HEADROOM_1 [5]  PH  [8]
[8]  PH  [11]
• 4 reportable values of PHR. There is no POWER_HEADROOM_2
POWER_HEADROOM_3 PH ≥ [11]
PHR modification after msg3.
PRACH: PUSCH:
• W/o repetition: • Open loop power control
preambleInitialReceivedTargetPower +
powerRampingStep
• W/ repetition: Pmax

67 © Nokia 2016 Nokia Internal Use

LTE3071 NB-IoT

RRM and Scheduler

68 © Nokia 2016 Nokia Internal Use

Technical Details
NB-IoT RRM recap
Uplink Downlink
• Frequency domain:15KHz single tone for NPUSCH, • Frequency domain: 12 subcarriers, 15KHz tone
12 subcarriers, 3.75 kHz single tone for NPRACH, 48 • Fixed 4 subframes TTI length
subcarriers
• The NPDSCH and NPDCCH transmission take place
• NPUSCH format 1 with data : 4 RUs (32 subframes) in subframes not reserved for NPBCH, NPSS/NSSS,
• NPUSCH format 2 ACK/NACK : 1 RU (2 subframes) NB-SIBs. In case of conflict with common channels in
downlink, the transmission will be skipped.
• The NPUSCH transmission takes place in subframes
not reserved for NPRACH in uplink. • NPDCCH aggregation level fixed to 2 CCEs, DCI
spans over 1 NPDCCH subframe.
• NPRACH and NPUSCH multiplexing in same TTI are
not supported • NPDCCH UE-specific search space and Common
search space (CSS) for RAR/Msg3
• Open loop power control retransmission/Msg4
• No link adaptation, statically configured UL MCS, • Static configurable power level
QPSK MCS0-10
• No link adaptation, statically configured DL MCS,
QPSK MCS0-10

69 © Nokia 2016 Nokia Internal Use

Technical Details
NB-IoT RRM

Uplink Hierarchy of transmissions to/from NB-IoT UEs

The eNB supports up to 11 UEs (in 15kHz single tone) in
the cell transmitting simultaneously in UL. One tone is • Prioritized lists
reserved for uplink ACK/NACK. • First In First Out within the list

Downlink PRIORITY 1
MSG4
• One UE scheduled per TTI in DL direction
MSG3 PRIORITY 2

Scheduler
MSG2 PRIORITY 3
• Half duplex scheduling
UL user data ReTx PRIORITY 4
• No channel awareness DL user data ReTx PRIORITY 5

• No QoS or guaranteed bit rates UL/DL user data Tx PRIO 6

• Mobility for NB-IoT happens via UE idle mode cell

selection.
• One adaptive, asynchronous HARQ process

70 © Nokia 2016 Nokia Internal Use

Technical Details
Link Adaptation

• There is no link adaptation for NB-IoT LTE3071, just configurable initial MCS per cell, separately for UL and DL
(NBIOTPR: iniMcsDl, NBIOTPR: iniMcsUl).
• The downlink and uplink MCS range is 0-10 for NB-IoT in LTE3071 (3GPP downlink:11, 12 will be used for
standalone/guardband NB-IoT; uplink: 11, 12 for multi-tone QPSK).
• Fixed pi/2 BPSK modulation for message 2 on NPDSCH

Number of MCS Index Modulation TBS Index

ITBS
resource IMCS Order ITBS
units
4
0 1 0
0 88 1 1 2
1 144 2 2 1
2 176 3 2 3
3 208 4 2 4
4 256 5 2 5
5 328 6 2 6
6 392
7 472
7 2 7
8 536 8 2 8
9 616 9 2 9
. 10 680 10 2 10

71 © Nokia 2016 Nokia Internal Use

Technical Details
HARQ recap

•
N0 (PUSCH scheduling)
Single HARQ process in both downlink and uplink, to enable low-complexity UE Field
Size
(bits)
implementation. UL ACK/NACK is transmitted in NPDCCH by the new data indicator (NDI) in the Flag for N0/N1
differentiation 1
DCI format N0. Subcarrier indication 6

•
Resource assignment 3
Positive UL HARQ feedback is signaled via toggled NDI of DCI format N0, negative feedback via Scheduling delay 2
non-toggled NDI. ACK for the last UL data transmission - no feedback at all. MCS 4
RV 1

• Positive UL HARQ feedback for msg3 is signaled via non-transmission of DCI format N0. Repetition number
NDI
3
1
Negative
NPDCCH UL HARQ feedback via non-toggled NPDCCH
NDI within DCI format N0. DCI subframe repetition
number 2
CRC 16
Total 39

NPUSCH

• The DL HARQ is carried by the NPUSCH format 2. The size of resource unit for A/N transmission
is 2 ms for 15 kHz, there is no repetition for ACK/NACK configured.
NPDCCH NPDSCH NPDCCH

.
NPUSCH (A/N)

72 © Nokia 2016 Nokia Internal Use

Technical Details
Bearer Management
• For LTE30171 eNB supports only data transmission via control plane (Control Plane CIoT EPS optimizations,
CP2 solution). User plane data is encapsulated in the Control Plane messages and using Signaling Radio
Bearer (SRB1bis). Data radio bearer (DRB) is not used
• An uplink Non-Access Stratum (NAS) signaling message or uplink NAS message carrying data can be
transmitted in an uplink RRC container message (i.e. MSG5 RRC Connection Setup Complete message).
• AS security is not utilized, PDCP layer is bypassed
• RRC connection reconfiguration and RRC connection re-establishment are not supported. When maximum
number of RLC retransmissions is reached , RRC connection is released.
UE eNB MME
RRC: RRCConnectionRequest
RRC: RRCConnectionSetup
RRC: RRCConnectionSetupComplete 1. S1: INITIAL UE MESSAGE
(dedicatedInfoNAS
) (NAS-PDU)

RRC: DLInformationTransfer 2a. S1: DOWNLINK NAS TRANSPORT

(dedicatedInfoNAS
) (NAS-PDU)

73 © Nokia 2016 Nokia Internal Use

Technical Details
RRC connected
• NB-IoT users are defined in a separate pool on top of normal LTE active users pool
NBIOT_FDD: maxNumRrcNB.
• The maximum number of NB-IoT users in the NB-IoT cells is up to 280*
• The total number of users per (host LTE + inband NB-IoT) cells is up to 840 users independently of the BW defined, so
with a maximum of 2520 users per HW board.
(up to) 3 cells (up to) 6 cells
Max # active users per 20MHz 15MHz 10MHz 5MHz 10MHz 5MHz
NB-IoT Inband cell
280 280 280 280 280 280

• As a consequence, the maximum number of Active users in LTE WB hosting cells might be reduced compared to legacy
values depending on the NB-IoT capacity statically defined.
• For instance:
- in 10MHz cells, legacy WB capacity of 600 users will be reduced if NB-IoT exceed 240 users
- in 20MHz cells, legacy WB capacity of 840 users will be reduced when Nb-IoT users is defined

• The actual limit for the number of RRC connected users comes from the radio interface and RRC threshold for NB-IoT
by admission control reduces number of overload messages exchanged by lower layers.
*Modified from 420 to 280 by LTERLCR-20060
74 © Nokia 2016 Nokia Internal Use
Technical Details
NB-IoT inactivity timers
• LTE3071 introduces two inactivity timers to monitor activity of NB-IoT connections
• SRB inactivity timer base on UL/DL SRB buffer data : srbInactivityTimerNB.
- The timer starts when both SRB UL buffer & SRB DL buffer are empty. Upon timer expiry UESTATE will be informed by an
inactivity indication (‘SRB inactive’). Timer is stopped when new data arrives to the buffer.

• C-Plane inactivity timer based on S1 interface NAS PDU messages: cpInactivityTimerNB

- The timer determines when the S1 connection shall be released. The timer monitors activity on S1AP interface for UE-
associated S1 logical connection traffic. It's started with UE-associated S1 logical connection establishment and restarted
on reception or sending S1AP message that contains NAS PDU IE.
- When the cpInactivityTimerNB expires, C-Plane has to check the status of the SRB activity. If the SRB activity status is
set to “SRB active”, no further action has to be done. If the status is set to “SRB inactive”, the eNB sends S1AP: UE
CONTEXT RELEASE REQUEST to MME with Cause value set to “User Inactivity” and RRC Connection Release – NB.
Timer Start Restart At expiry
cpInactivity Reception of : Reception of: If the SRB status is set to “SRB
TimerNB S1AP: DOWNLINK NAS S1AP: DOWNLINK NAS inactive” (srbInactivityTimerNB
TRANSPORT TRANSPORT expires), the eNB sends S1AP:
or or UE CONTEXT RELEASE
S1AP: CONNECTION S1AP: UPLINK NAS REQUEST to MME with Cause
ESTABLISHMENT TRANSPORT value set to “User Inactivity”.
INDICATION

75 © Nokia 2016 Nokia Internal Use

Technical Details
NB-IoT inactivity timers
• Inactivity timers settings are a compromise between few simultaneous RRC connections/high RRC
signaling load (short inactivity timer) and many simultaneous RRC connections/low RRC signaling
load (long inactivity timer)
• Settings of inactivity timers depends on the traffic profile.
- When typical traffic profile considers just single message (e.g. single Smart meter reading) lower values are recommended
to keep RRC connected time short and reduce total number of RRC connected UE
- Higher values are recommended when several subsequent messages are exchanged. It saves signaling resources since
release and establishment of radio bearer is avoided.

5s, 100UEs 10s, 100UEs Example:

Connected UEs vs
Number of connected UEs

Peak 15 Peak 28 inactivity timer

Assumptions: Connected
state time: 1s transmission
Average 10
Average 18.3 + inactivity. 60s Mean inter-
arrival time

76 © Nokia 2016 Nokia Internal Use

LTE3071 NB-IoT

NPDCCH monitoring details

77 © Nokia 2016 Nokia Internal Use

Technical Details
Narrowband physical downlink control channel related procedures

NPUSCH format1 transmission NPDSCH (RAR) transmission

NPDCCH NPUSCH NPDCCH
NPDCCH NPDSCH
… 3ms … (RAR) …

n n+k n+k+m n+k+m +3

n+1: n+k-1 n
NPDCCH is not
monitored
by the UE

• If a NB-IoT UE detects NPDCCH with DCI Format N0 ending in subframe n or receives a NPDSCH carrying a
random access response grant ending in subframe n, and if the corresponding NPUSCH format 1 transmission
starts from n+k, the UE is not required to monitor NPDCCH in any subframe starting from subframe n+1 to
subframe n+k-1 (indicated by white).

• Moreover, if a NB-IoT UE has a NPUSCH (f1 or f2) transmission ending in subframe (n+k+m) , the UE is not
required to monitor NPDCCH in any subframe starting from subframe (n+k+m)+1 to subframe (n+ k+m) + 3 – as
next scheduling request conveyed by NPDCCH is expected not earlier than 3ms after NPUSCH.

78 © Nokia 2016 Nokia Internal Use

Technical Details
Narrowband physical downlink control channel related procedures
NPDSCH user data or paging transmission
NPDCCH NPDSCH NPDCCH • If a NB-IoT UE detects NPDCCH with DCI Format N1 or N2 ending in
12ms subframe n, and if the corresponding NPDSCH transmission starts from
n+k, the UE is not required to monitor NPDCCH in any subframe starting
n n+k n + k+m n + k+ m + 12 from subframe n+1 to subframe n+k-1.
n+1: n+k-1 • If a NB-IoT UE receives a NPDSCH transmission ending in subframe
NPDCCH
(n+k+m), and if the UE is not required to transmit a corresponding
is not
monitored NPUSCH format 2, the UE is not required to monitor NPDCCH in any
by the UE subframe starting from subframe (n+k+m)+1 to subframe (n+k+m)+12.

NPDCCH NPDSCH NPUSCH f2

… • If a NB-IoT UE detects NPDCCH with DCI Format N1 ending in
subframe n, and if the corresponding NPUSCH format 2 transmission
n n+k starts from subframe n+k, the UE is not required to monitor NPDCCH in
n+1: n+k-1 any subframe starting from subframe n+1 to subframe n+k-1.
NPDCCH is not monitored
by the UE

79 © Nokia 2016 Nokia Internal Use

LTE3071 NB-IoT

Interdependencies

Table of contents

<chapter:interdependencies>

80 © Nokia 2016 Nokia Internal Use

Interdependencies

NB-IoT stands for a quite new system with own channels and RRM. Narrow band
limitations 200kHz receiver and transmitter with no support for other technologies. That is why
most of the legacy LTE features are not supported in the NB-IoT cell.
NB-IoT cell
- Legacy LTE channels can not be read by NB-IoT receiver
- NB-IoT uses its own RRM procedures and operates on the single PRB resources
- All legacy LTE related RRM features and resources optimization features are not relevant
for NB-IoT cell, e.g. legacy mobility, Inter-system HO, CA, ETWS, CMAS, OTDOA, MBMS,
GBR and QCIs, CRAN, all voice related, VoLTE and emergency calls,
- NB-IoT system was designed to support TM2 Tx and 2Rx with MRC receiver
- Any other Tx or Rx schemes are not supported by NB-IoT cell. 4Tx transmission schemes
can not be used in the host cell since it is not compatible with NRS design.
- IRC is not supported by NB-IoT cell, however can be activated in the host LTE cell
- DRX with LTE3071 operates in idle mode only.
- Connected DRX and DRX extensions are not relevant for NB-IoT cell.

81 © Nokia 2016 Nokia Internal Use

Interdependencies

The following features cannot be enabled in the hosting LTE cell together with
limitations inband NB-IoT:
host LTE cell LTE3128 LTE-M
NB-IoT and Cat-M can’t be enabled in the same cell due to scheduler implementation.
NB-IoT and Cat-M can be enabled in different cells in one eNB. Note that support will be
allowed with LTE3819 and LTE4040 features.
LTE187 Single TX path mode
LTE1063 Uplink SU MIMO for 4 RX paths
LTE1402 Uplink CoMP
LTE1691 Uplink intra-eNB CoMP 4Rx
NB-IoT LTE3071 is designed assuming support for 2TX and 2RX schemes. As some
elements (e.g. LTE CRS) overlaps with inband NB-IoT channels, other transmission
schemes are not supported for the host LTE cell. Extension to 4Tx, 4Rx and 1Tx will come
with LTE3722.

82 © Nokia 2016 Nokia Internal Use

Interdependencies

The following features cannot be enabled in the hosting LTE cell together with
limitations inband NB-IoT:
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.

83 © Nokia 2016 Nokia Internal Use

Interdependencies

The following features cannot be enabled in the hosting LTE cell together with
limitations inband NB-IoT:
host LTE cell LTE1709 Liquid Cell
TM9 CSI-RS may interference to NB-IoT
LTE1542 - FDD Supercell
Super Cell requires specific DSP deployment (not supported in FL17).
LTE2091 - Extended SuperCell
LTE2445 - Combined Supercell
Combined Supercell requires specific DSP deployment (not supported in FL17).
LTE1117 eMBMS
eMBMS may has the interference to/from NB-IoT.
LTE1113 / LTE1496 eICIC
NB-IoT has interference on eICIC ABS subframes

84 © Nokia 2016 Nokia Internal Use

Interdependencies

The following features cannot be enabled in the hosting LTE cell together with
limitations inband NB-IoT:
host LTE cell LTE1891 MicroDTX
MicroDTX may muste the subframes impacting NB-IoT
LTE495 OTDOA
OTDOA may has the interference to/from NB-IoT.
AirScale HW
Only FSMr3 will be supported for NB-IoT and wideband host LTE cell.
LTE819 DL inter-cell interference generation
Dummy load generation on both host LTE cell and NB-IoT cell are not supported.

85 © Nokia 2016 Nokia Internal Use

Interdependencies

Following features can be enabled in the hosting wideband LTE cell together with
limitations inband NB-IoT, but some consideration on the interaction should be addressed.
host LTE cell LTE1103/LTE1203 Load Based Power Saving
The host and NB-IoT cells will be shutdown together. It's suggested not to add host cell or
NB-IoT cell into Power Saving List.
LTE2664 Load based PUCCH
Load based PUCCH will dynamically change the number of PUCCH resources. The
uplink NB-IoT position in this feature should be selected considering the maximum
PUCCH and PRACH may extend.
LTE46 Channel-aware Scheduler (UL)
LTE46 is not supported in an NB-IoT cell. When LTE46 is activated, SRS may interfere
with NB-IoT PRB, there is consistency check to avoid NB-IoT activation in PUSCH area
with LTE46. If PUCCH blanking is enabled, an NB-IoT PRB can be in blanked area, so
that SRS
in host cell will not cause interference to NB-IoT.

86 © Nokia 2016 Nokia Internal Use

Please fill in a short survey
Your feedback is valuable to us!

KIND REQUEST TO YOU:

PLEASE FILL IN THE SURVEY NOW
SURVEY IN THE WEBEX PANEL

To get the certificate proving

participation in the training please login
to NEDC with your Nokia credentials
and download the certificate after
completing the training.

87 © Nokia 2016 Nokia Internal Use

LTE3071 NB-IoT

NB-IoT extensions
outlook
Table of contents

88 © Nokia 2016 Nokia Internal Use

Technical Details
FL17A NB-IoT extensions
• LTE3668 NB-IoT: Coverage enhancements (+20dB)
- This feature extends the coverage for NB-IoT (Inband) mainly by repetitions. Up to 3 coverage
levels can be configured (normal + robust + extreme). The eNB will select coverage level per UE
based on the level of NPRACH UE sent.
• LTE3509 NB-IoT: Support on Airscale without Baseband Pooling
- Support for 2Tx/2Rx inband NB-IoT
• LTE3543 NB-IoT Standalone
- Standalone NB-IoT over FSMr3 and AirScale.
• LTE3669 Paging support
- Improved NB-IoT implementation by introducing Paging for NB-IoT MT (Mobile Terminated) calls.
It applies to either Inband or Standalone mode.
• LTE3125 e-DRX Idle

89 © Nokia 2016 Nokia Internal Use

Technical Details
NB-IoT features outlook
• LTE3722: support 4T4R and 1Tx
- Support for 2Tx/4Rx inband/standalone NB-IoT, support 4TX for host LTE cell, but only 2TX for
NB-IoT inband cell, dual TM1 operation

90 © Nokia 2016 Nokia Internal Use

 Part 2

91 © Nokia 2016 Nokia Internal Use

 NETWORK ENGINEERING

LTE3071 NB-IoT
Updated with RP001597 “Support of LTE in-band NB-IoT with RF sharing in SRAN "

Part 2

Please, always check the latest version of NEI slides.

92 © Nokia 2016 Controlled Document, for internal use
LTE3071 NB-IoT
Table of contents

Benefits and Configuration Deployment Dimensioning

Gains Management Aspects Aspects
Simulation, Lab and Parameters and Activation, Configuration Dimensioning Impacts
Field Findings Parameterization Examples, Fault Mgmt, and Examples
Scenarios Trial Area

Energy Performance Compliance End-to-End

Savings Aspects Aspects Operability
Aspects 3GPP, IETF, ETSI OSS and Core
Energy Savings Counters and KPIs,
Feature Impact Analysis Interworking
Examples and
Calculations and Verification

95 © Nokia 2016 Nokia Internal Use

Technical Details
FL17A NB-IoT Overview
LTE carrier
Basic 3GPP Rel. 13 in-band NB-IoT functionality is
introduced with LTE 3071 feature.

NB IoT
- New cell concept and deployment options:
• FDD mode, half duplex operations, 200 kHz UE RF bandwidth
for both downlink and uplink
• DL: OFDMA with 15 kHz subcarrier spacing, TM2
• UL: single tone transmissions –15 kHz, 2 RX MRC* receiver
- The data transmission over SRB1bis (data over NAS) 10 ms

- First level coverage (without coverage enhancement) NPUSCH NPUSCH

180 kHz
(6 tones) (6 tones)
NPRACH
with MCL pathloss target up to 144dB is supported UL NPUSCH NPUSCH
(12 tones) (12 tones)
NPUSCH (3 tones)

- FSMF and FZM deployments

NPUSCH, single-tone

Airscale support comes separately with LTE3509

Higher coverage levels are supported with LTE3668 NB-IoT
Coverage Enhancements
Paging support for NB-IoT will be activated with LTE3669
MRC* Maximum Ratio Combining
96 © Nokia 2016 Nokia Internal
Technical Details
NB-IoT support for SRAN17A

• NB-IoT is introduced into SRAN with RP001597 feature

• The RP001597 feature basically consists of porting the below LTE features to SBTS:
• LTE3071 NB-IoT Inband
• LTE3509 NB-IoT: Inband on Airscale without Baseband Pooling
• LTE3668 NB-IoT: Coverage enhancements
• LTE3819 IoT: Cat-M and NB-IoT on same frequency carrier
• LTE3669 NB-IoT: Paging support
• RP001597 allows for:
• in-band NB-IoT cells on both FSMr3 and FSMr4 HW releases
• up to 20dB coverage enhancement so that to reach 164dB for the Maximum coupling loss (MCL) of
the NB-IoT cell
• simultaneous activation of Cat-M and in-band NB-IoT in a hosting LTE cell 2Tx2Rx 10MHz on FSMr3
• paging of NB-IoT UE for mobile terminated connections in normal or extreme coverage

97 © Nokia 2016 Nokia Internal

LTE3071 NB-IoT Part 1 refresher
LTE 3071 NB-IoT – Inband operation
LTE carrier
• One NB-IoT carrier can be configured for each legacy
5/10/15/20 MHz FDD LTE cell in a 2x2 configuration.

NB IoT
• Allocation of DL NB-IoT carrier is predefined by 3GPP. The
location of downlink and uplink can be configured separately.
• There is no paging support with LTE3071, hence only mobile
originated calls can be handled. R1 R0 R1 R0 R1 R0 R1 R0

• The same OFDM modulation with 15 kHz subcarrier spacing R0 R1 R0 R1 R0 R1 R0 R1

is used in DL there is no interference between R1 R0 R1 R0 R1 R0 R1 R0

NB-IoT and legacy LTE.

1 PRB
R0 R1 R0 R1 R0 R1 R0 R1

NB-IoT NB-IoT

• A protection of legacy cell resource elements is supported for R1 R0 R1 R0 R1 R0 R1 R0

the fixed first 3 OFDM symbols (wideband PDCCH area) and R0 R1 R0 R1 R0 R1 R0 R1

for CRS area. R1 R0 R1 R0 R1 R0 R1 R0

(a) Downlink in-band operation

98 © Nokia 2016 Nokia Internal Use

LTE3071 NB-IoT Part 1 refresher
NB-IoT – Downlink
• DL uses OFDMA with 15 kHz subcarrier spacing, 12 subcarriers available in 1 NB-IoT carrier,
10ms frame.

• Narrow 200 kHz UE bandwidth does not allow for legacy channels utilization, new DL channels
are introduced:
• Narrowband Primary and Secondary Synchonization signals NPSS/NSSS - time/frequency synchronization,
cell ID and timing for NPBCH detection,
• Narrowband Common Reference Signals NRS for 2 antenna ports transmission schemes,
• Narrowband Physical Broadcast Channel NPBCH conveys Narrowband Master Information Block MIB-NB,
• Narrowband Physical Downlink Control Channel NPDCCH carries scheduling information for both DL and
UL data channels, HARQ Ack and random access response scheduling information,
• Narrowband Physical Downlink Shared Channel NPDSCH carries data from the higher layers, system
information and the random access response messages..
99 © Nokia 2016 Nokia Internal Use
LTE3071 NB-IoT Part 1 refresher
NB-IoT – Uplink Physical Channels

• Narrowband Physical Uplink Shared Channel NPUSCH. Among several NPUSCH transmissions options defined by
3GPP (single-, multi-tone, 15 or 3.75 kHz subcarrier spacing) 15 kHz single-tone will be supported for FL17SP
LTE3071, 12 subcarriers available.
Format1 transport block= 4RU = 32 ms Format2 transport block= 1RU = 2 ms
12 subcarriers

180 KHz
x 15 kHz

1RU = 8 ms

• Narrowband Physical Random Access Channel NPRACH carries preamble for Random Access procedure. NPRACH
operates on 3.75 kHz subcarrier spacing and predefined hopping schemes with repetitions. NPRACH window
repeated every NBIOTPR: nprachPeriod
48 subcarriers
x 3.75 kHz
180 KHz

Single UE NPRACH, 4 repetitions, 4 x (4 x 1.6ms) = 25.6 ms

100 © Nokia 2016 Nokia Internal Use

LTE3071 NB-IoT

Benefits and Gains

Table of contents

<chapter:benefits_and_gains>

101 © Nokia 2016 Nokia Internal Use

Benefits and Gains
NB-IoT technology
• NB-IoT is a cost-optimized technology
developed to serve massive number of IoT
devices
NB-IoT
• NB-IoT provides with extended coverage, e.g for Cost-efficient and
reaching sensors, tracking and metering devices at remote reliable coverage
locations or within building basements
• Easy and fast deployment on Nokia LTE networks via Lowest Longest Deepest geo-
software upgrade module costs battery life graphic+indoor
• Allows for massive deployment by NB-IoT UE coverage
simplification by 85% with user equipment Cat-NB1
• Optimized for low-data volume metering, control, tracking
and sensor devices
• Standardized for global use in 3GPP Rel.13
• Allowing for “install and leave alone” device operation Fastest Interworking, Licensed

Globa Reliabl
with >10years device battery life rollout and evolution, frequency
maximum longevity by spectrum
• IoT businesses and underlying connections protected asset reuse 3GPP ecosystem

SW l e
against (malicious) interference by use of licensed
spectrum

102 © Nokia 2016 Nokia Internal Use

Benefits and Gains
LTE3071

Benefits Drawbacks
• LTE 3071 provides with framework for • Allocation of NB-IoT carrier consumes
NB-IoT UE operation PRB resources; in DL direction not only
• The main benefit is that with the feature single PRB, but the whole RBG
legacy network can be seamlessly allocation group
migrated by means of SW upgrade and • The first release of NB-IoT is
allows for serving of NB-IoT devices. incompatible with some generic legacy
features, what may bring degradation of
the host cell operation.
• Improved coverage will not be
supported by LTE3071; it will come with
further extension features

103 © Nokia 2016 Nokia Internal Use

Benefits and Gains

NB-IoT benefits over the unlicensed technologies (e.g. LoRa,

SigFox)
• No additional site, backhaul, BTS HW nor implementation capex / opex
• Increased coverage and penetration e.g. to inside building basements => avoid
redesigning and expanding the macro network
• Avoid building of separate back-office systems for unlicensed technology
• Avoid integration cost of mobile based use-cases and stationary unlicensed use cases

104 © Nokia 2016 Nokia Internal Use

Benefits and Gains
NB-IoT DL Data Rates
• Timing diagram for NB-IoT downlink data transmission FN 0
SFN 0 1 2 3 4 5 6 7 8 9 0
4ms* MIB SIB1 PSS SSS MI
Valid SF * 4ms is the best case; actual timing depends on
NPDCCH NPDSCH NPDCCH
the number of free subsequent subframes
680 bits NPDCCH TTI=2, dictated by SIB1 occurrence
NPUSCH Format 2 TTI=2 ms

NPUSCH (A/N)

27ms
• Instantaneous peak rate (in-band) is is given by:
TBSmax/TNPDSCH = 170 kbps (TBS=680 bytes, TTI=4ms)
• Sustained throughput:
TBSmax/(TNPDCCH + 4ms + TNPDSCH + 12ms + TNPUSCH + 3ms) kbps
Sustained peak rate is approximately 26.2 kbps without considering NPBCH/NPSS/NSSS
overhead, and 15.7 kbps when 40% DL overhead is taken into account (PBCCH, SIBx, PSS, SSS)

105 © Nokia 2016 Nokia Internal Use

Benefits and Gains
NB-IoT UL Data Rates
• Timing diagram for NB-IoT downlink data transmission
NPDCCH NPDCCH
32ms
NPDCCH TTI=2,
NPUSCH Format 1 TTI=32 ms
680 bits
NPUSCH
45ms*

• Instantaneous throughput is given by:

TBSmax/TNPDSCH = 21.2 kbps (TBS=680 bytes, TTI=32ms)
• Sustained throughput:
TBSmax/(TNPDCCH + 8ms + TNPUSCH + 3ms) kbps
Approximately 15.4 kbps without considering NPRACH overhead
NPRACH occasion is every 160 ms and lasts for 25.6 ms, 16% overhead reduces
sustained peak rate to 12.9 kbps

106 © Nokia 2016 Nokia Internal Use

Benefits and Gains
Simulations
• Product specific system level simulator is under development, hence T&I results are shown for
reference
• NOTE: The results of simulations demonstrate trends (not absolute values) expected after
feature activation. The presented simulations should be analyzed with respect to the
assumptions taken. Analysis is based on 3GPP features using single user link analysis.
Product may have different constraints from the assumptions used in this analysis.

• Simulation assumptions:
• Single user link-level analysis
• 2Tx-2Rx at eNB, 1Tx-1Rx at UE, 23 dBm UE power class, half-duplex
• Antenna gain: 16 dBi at eNB, 0 dBi at UE
• 6 dB PSD boosting for NB-IoT, NB-IoT uses 12 or 1 tones in the uplink (15 kHz)
• TU 1 Hz channel for NB-IoT,
• Invalid subframes and subframes used for common channels/signals (e.g. PBCH, PSS/SSS, SIs) are not
considered in this analysis

107 © Nokia 2016 Nokia Internal Use

Benefits and Gains
Simulations NB-IoT Data Rates
• Instantaneous and sustained data rates are aligned with theoretical calculations
(overheads are not considered)
3
NB-IoT, In-band, Downlink UE Throughput 3
NB-IoT, In-band, Uplink UE Throughput
10 10
Instantaneous DL throughput Normal Coverage
Normal Sustained DL throughput coverage improvements
coverage Coverage area – not
~170kbps improvements LTE3071
2
area – not 10 applicable

Throughput (kbps)
Throughput (kbps)

2
10 LTE3071
applicable
~21kbps
~26kbps
1 ~15kbps
10

1 Instantaneous UL throughput, multi-tone UL

10
Instantaneous UL throughput, single-tone UL (15 kHz)
Sustained UL throughput, multi-tone UL
Sustained UL throughput, single-tone UL (15 kHz)
0
10
110 120 130 140 144dB 150 160 170 110 120 130 140 144dB 150 160 170
PL (dB) PL (dB)

108 © Nokia 2016 Nokia Internal Use

Benefits and Gains
Simulations: latency and battery life
• Packet delivery time (just TBS delivery) • Battery life (without battery self-discharging)
• 200 bytes packet size

NB-IoT, In-band, Packet Delivery Time NB-IoT, In-band, Battery Life

1200 35

1100 Multi-tone UL
Normal Single-tone UL (15 kHz) 30 ~34years
coverage Normal Coverage
1000
Coverage coverage improvements
25 area – not
Packet Delivery Time (ms)

900 improvements
area – not

Battery Life (Years)

LTE3071
800
LTE3071 20 applicable
700 applicable 1 report per day, multi-tone UL
1 report per day, single-tone UL (15 kHz)
15
600 1 report per hour, multi-tone UL
1 report per hour, single-tone UL (15 kHz)
500 10

400
~330ms 5
~7 years
300

200 0
110 120 130 140 144dB 150 160 170 110 120 130 140 144dB 150 160 170
PL (dB) PL (dB)

109 © Nokia 2016 Nokia Internal Use

LTE3071 NB-IoT

Configuration
Management
Table of contents

<chapter:configuration_management>

110 © Nokia 2016 Nokia Internal Use

Configuration Management
Definition of terms and rules for parameter classification*
The ‘Basic Parameters’ category contains The ‘Advanced Parameters’ category contains
primary parameters which should be considered the parameters for network optimisation and fine
during cell deployment and must be adjusted to a tuning:
particular scenario:
• Decent network performance should be achieved without tuning
• Network Element (NE) identifiers these parameters
• Planning parameters, e.g. neighbour definitions, frequency, • Universal defaults ensuring decent network performance need to
scrambling codes, PCI, RA preambles be defined for all parameters of this category. If this is not
• Parameters that are the outcome from dimensioning, i.e. basic possible for a given parameter it must be put to the ‘Basic
parameters defining amount of resources Parameters’ category
• Basic parameters activating basic functionalities, e.g. power • Parameters requiring detailed system knowledge and broad
control, admission control, handovers experience unless rules for the ‘Basic Parameters’ category are
• Parameters defining operators’ strategy, e.g. traffic steering, violated
thresholds for power control, handovers, cell reselections, basic • All parameters (even without defaults, e.g. optional structures)
parameters defining feature behaviour related to advanced and very complex features

The ‘Obsolete parameters’ category is intended for parameters that are candidates to be removed
from the product in a future release: * - purpose: Categories of parameters have been defined to simplify network
parametrization. Parameterization effort shall be focused mainly on Basic ones.
• Parameters always used with default value
• Parameters that are not used by operators Categorization is reflected in a ‘view’ definition in NetAct CM Editor.
• Parameters that are not relevant anymore

111 © Nokia 2016 Nokia Internal Use

 Configuration Management

LNBTS NBIOTP Profiles for IoT

R ‘semi-static’ parameters • New NBIOT_FDD MOC grouping
NB-IoT relevant parameters
nprachCpLen
SIB configuration parameters • NBIOTPR Profiles for IoT ‘semi-
srbInactivityTimerNB
LNCEL LNCEL cpInactivityTimerNB static’ parameters
(host) (NB-IoT) • With LTE3071 parameters for first level
First level coverage (LTE3071) coverage only
lrcId = 1 lrcId = 2 nprachProfNBNorCov structure – NPRACH
CellTechnology= LNCEL_FDD CellTechnology = NB-IoT-FDD • Second and third coverage levels with
rachProfNBNorCov structure – NB-IoT RACH
PLMN (LTE cell) PLMN (NB-IoT cell) cssProfNorCov structure – NPDCCH CSS LTE3840
Cell Id (LTE cell) Cell Id (NB-IoT cell) rlcProfNBNorCov structure – NB-IoT RLC
TAC (LTE cell)
nbIoTMode = inband
TAC (NB-IoT cell)
nbIoTMode = inband
macProfNBNorCov structure – NB-IoT MAC • NB-IoT cell reconfiguration is not
schedProfNBNorCov structure – NB-IoT
nbIotLinkedCellId = 2 nbIotLinkedCellId = 1 Scheduler supported in current release so
…
…
Second level coverage (LTE3840)
all the NB-IoT related parameters
LNCEL_FD NBIOT_FD update/creation requires cell lock
D D …
Third level coverage (LTE3840) to take effects.
inbandPRBIndexUL
inbandPRBIndexDL
… • Direct Lock/ unlock/
syncSigTxMode reset/shutdown of inband
maxNumRrcNB
dlPwrBoost NB-IoT cell is not supported,
nbIoTProfId = {profile #1} host cell have to be locked

112 © Nokia 2016 Nokia Internal Use

Configuration Management
New parameters

Abbreviated name Full name PKDB link

LNCEL: nbIotLinkedCellId NBIoT inband linked cell ID between
NB-IoT host cell and concrete cell
LNCEL: nbIoTMode NB-IoT operation mode

NBIOT_FDD: inbandPRBIndexDL NBIoT inband downlink PRB index

NBIOT_FDD: inbandPRBIndexUL NBIoT inband uplink PRB index

NBIOT_FDD: nbIoTProfId Instance ID of the assigned NBIOTPR

profile
NBIOT_FDD: dlPwrBoost Downlink channel power boost for
inband NB-IoT

113 © Nokia 2016 Nokia Internal Use

Configuration Management
New parameters

Abbreviated name Full name PKDB link

NBIOT_FDD: maxNumRrcNB Max Number RRC

NBIOT_FDD: syncSigTxMode Synchronization signals transmission

mode: Enumeration
LNMME: mmeRatSupport MME RAT support

LNCEL: tExtendedWait Timer ExtendedWaitTime-r10

114 © Nokia 2016 Nokia Internal Use

Configuration Management
New parameters
SIB configuration

Abbreviated name Full name PKDB link

NBIOTPR: numSib1RepNB Number of SIB1-NB repetitions

NBIOTPR: sib2PeriodicityNB The periodicity of SIB2-NB

NBIOTPR: sib2RepPatternNB The repetition pattern of SIB2-NB

NBIOTPR: siRadioFrameOffNB Offset of the start of SI-NB window

NBIOTPR: siWindowLenNB SI-NB window length

115 © Nokia 2016 Nokia Internal Use

Configuration Management
New parameters
NPDCCH search space configuration

Abbreviated name Full name PKDB link

NBIOTPR: cssProfNBNorCov Common Search Space profile for NB-
IoT first level coverage
NBIOTPR: npdcchMaxNumRepRa Maximum number of repetitions for
NPDCCH common search space for RA

116 © Nokia 2016 Nokia Internal Use

Configuration Management
New parameters
MAC configuration

Abbreviated name Full name PKDB link

NBIOTPR: macProfNBNorCov MAC profile for NB-IoT first level
coverage
NBIOTPR: Logical channel SR prohibit timer for
logicalChanSrProhibitTimerNB NB-IoT

NBIOTPR: tReTxBsrTimeNB Retransmit BSR timer for NB-IoT

117 © Nokia 2016 Nokia Internal Use

Configuration Management
New parameters
NPRACH configuration

Abbreviated name Full name PKDB link

NBIOTPR: nprachProfNBNorCov NPRACH profile for NB-IoT first level
coverage
NBIOTPR: Max number of preamble attempts of
nprachMaxNumPreambleCE NPRACH
NBIOTPR: nprachNumRepPreamble Number of repetitions per preamble
attempt of NPRACH
NBIOTPR: nprachStartTime NPRACH start time

NBIOTPR: nprachPeriod NPRACH periodicity

118 © Nokia 2016 Nokia Internal Use

Configuration Management
New parameters
RACH configuration

Abbreviated name Full name PKDB link

NBIOTPR: rachProfNBNorCov RACH profile for NB-IoT first level
coverage
NBIOTPR: raContResoTimNB Contention resolution timer for NB-IoT

NBIOTPR: raRespWinSizeNB RA response window size for NB-IoT

119 © Nokia 2016 Nokia Internal Use

Configuration Management
New parameters
RLC configuration

Abbreviated name Full name PKDB link

NBIOTPR: rlcProfNBNorCov RLC profile for NB-IoT first level
coverage
NBIOTPR: maxRetxThreNB Max retransmission threshold
for NB-IoT
NBIOTPR: tPollRetrNB Poll retransmit for NB-IoT

120 © Nokia 2016 Nokia Internal Use

Configuration Management
New parameters
Scheduler configuration

Abbreviated name Full name PKDB link

NBIOTPR: schedProfNBNorCov Scheduler profile in NB-IoT normal
coverage
NBIOTPR: iniMcsDl Initial MCS in downlink

NBIOTPR: iniMcsUl Initial MCS in uplink

121 © Nokia 2016 Nokia Internal Use

Configuration Management
New parameters
Timers

Abbreviated name Full name PKDB link

NBIOTPR: srbInactivityTimerNB SRB inactivity timer

NBIOTPR: cpInactivityTimerNB C-Plane inactivity timer

NBIOTPR: t300NB Timer of T300 for NB-IoT

NBIOTPR: t310NB Timer of T310 for NB-IoT

122 © Nokia 2016 Nokia Internal Use

Configuration Management
Related parameters

Abbreviated name Full name PKDB link

MBSFNCEL: mbsfnCelId MBSFN Cell identifier

LNBTS: actCRAN Activate Centralized RAN: Boolean

ULCOMP: ulCoMpCellList Uplink CoMP Cell List: Number

LNCEL: actEicic Activate enhanced inter-cell

interference coordination:
LNCEL: actMicroDtx Activate eNode B power saving - Micro
DTX: Boolean

123 © Nokia 2016 Nokia Internal Use

Configuration Management
Related parameters

Abbreviated name Full name PKDB link

LNCEL: actOtdoa PRS activation: Boolean

LNCEL: csgType Closed Subscriber Group type:

Enumeration
LNCEL_FDD: actCatM Activate LTE-M feature: Boolean

LNCEL_FDD: actCombSuperCell Activate combined supercell

configuration:
LNCEL_FDD: actLiquidCell Activate liquid cell configuration:

LNCEL_FDD: actSuperCell Activate supercell configuration:

124 © Nokia 2016 Nokia Internal Use

LTE3071 NB-IoT

Deployment
Aspects
Network graphic boxes Network element boxes
Table of contents

<chapter:deployment_aspects>

125 © Nokia 2016 Nokia Internal Use

Deployment Aspects
Frequency layer selection for NB-IoT
eUTRA Band Total Downlink 3GPP
• Selection of frequency band number
Band
spectrum
Uplink [MHz]
[MHz] Rel.
for NB-IoT depends on the operator 1 2100 2x60 MHz 1920 - 1980 2110 -2170 Rel. 13
resources and spectrum policy 2 1900 2x60 MHz 1850 - 1910 1930 - 1990 Rel. 13
3 1800 2x75 MHz 1710 - 1785 1805 - 1880 Rel. 13
• NB-IoT in-band solution requires LTE 5 850 2x25 MHz 824 - 849 869 - 894 Rel. 13
network in operation 8 900 2x35 MHz 880 - 915 925 - 960 Rel. 13
10 1700 2x60 MHz 1710 - 1770 2110 - 2170 Rel. 14
• Generally it is expected that lower 12 700 2x18 MHz 699.4 - 714.8 729.4 - 744.8 Rel. 13
bands (<1 GHz) provides with higher 13 700 2x10 MHz 777 - 787 746 - 756 Rel. 13

cell range, the lower frequency bands 17 700 2x10 MHz 704.0 - 714.8 734.0 - 744.8 Rel. 13
18 800 2x15 MHz 815 - 830 860 - 875 Rel. 13
have smaller building penetration loss 19 800 2x15 MHz 830 - 845 875 - 890 Rel. 13

• However one has to be aware that 20 800 2x30 MHz 832 - 862 791 -821 Rel. 13
25 1900 2x65 MHz 1850 - 1915 1930 - 1995 Rel. 14
3GPP Release 13 [36.521] specifies 26 850 2x35 MHz 814 - 849 859 - 894 Rel. 13
IoT usage on the selected bands only. 28 700 2x25 MHz 703 - 738 758 - 794 Rel. 13
Further enhancements are expected 31 450 2 x 5 MHz 452.5 - 457.5 462.5 - 467.5 Rel. 14
66 2100 2x70 MHz 1710 - 1780 2110 - 2200 Rel. 13
with Release 14.
70 1700 2x15 MHz 1695 – 1710 1995 – 2020 Rel. 14

126 © Nokia 2016 Nokia Internal Use

Deployment Aspects
Impact on legacy LTE performance
• The main impact on the legacy LTE cell is due to LTE3071 incompatibility with some features activated in
the host cell.
Legacy LTE feature not compatible with
Compatibility issue Solution
NB-IoT in same cell
NB-IoT and Cat-M can’t be enabled in the same cell FL17A LTE3819 LTE-M/NB-IoT on same LTE
LTE3128 NB-IoT due to scheduler implementation. NB-IoT and Cat-M 10MHz cell in, FL18 LTE4040 for other
can be enabled in different cells in one eNB Bandwidths

LTE187 Single TX path mode Structure of NB-IoT channels selected for in-band
LTE568 DL Adaptive Closed Loop MIMO (4x2) LTE3071 feature assumes 2-port CRS structure.
Hence host legacy cell have to operate with 2TX LTE3722 NB-IoT: Additional configurations
LTE1987 DL adaptive CL SU MIMO (4x4) transmission schemes only. (4Rx, 4Tx or 1Tx eNB support) (FL18
1Tx and 4Tx modes are not compatible with candidate)
LTE2582 DL 4x4 MIMO with Carrier LTE3071, and it should be considered during NB-IoT
Aggregation host cell selection.
LTE1063 Uplink SU MIMO for 4 RX paths

LTE1402 Uplink CoMP Host cell: LTE3571 NB-IoT: Enhancements and

Improved Feature interactions - Phase I (FL18
LTE1691 Uplink intra-eNB CoMP 4Rx Exceptions also for specific RX modes using DSP
candidate)
allocations conflicting with NB-IoT (e.g. LTE2605).
UL COMP for NB-IoT: LTE3730 NB-IoT:
Additionally host cell should not be included in the
LTE2605 4RX diversity 20MHz optimized Enhancements and Improved Feature
CoMP set.
configurations interactions - Phase II (FL18 SP candidate)

Note: Subject to change; some limits will be solved by separate features or during forthcoming NB-IoT features development
phase.
127 © Nokia 2016 Customer Confidential
Deployment Aspects
Impact on legacy LTE performance

Legacy LTE feature not compatible with

Compatibility issue Solution
NB-IoT in same cell

LTE2180 FDD-TDD downlink carrier aggregation

2CC

LTE2270 LTE TDD+FDD inter eNB CA basic BTS

Inter eNB CA TDD+FDD is not supported in
LTE2316 FDD-TDD downlink carrier aggregation the host LTE cell due to conflicting
LTE3571 NB-IoT: Enhancements and
3CC requirements on DSP deployment in eNB
Improved Feature interactions - Phase I
FDD. There is no specific feature flag for
LTE2735 FDD-TDD downlink carrier aggregation (FL18 candidate)
FDD+TDD CA because
with AirScale System Module configurations 'actInterEnbDLCAggr' is commonly used
LTE2337 FDD-TDD downlink carrier aggregation also for FDD+FDD CA
3CC - 2 FDD & 1 TDD
LTE2623 FDD-TDD downlink carrier aggregation
4CC

128 © Nokia 2016 Customer Confidential

Deployment Aspects
Impact on legacy LTE performance
Legacy LTE feature not
compatible with Compatibility issue Solution
NB-IoT in same cell
LTE3730 NB-IoT: Enhancements and Improved Feature interactions - Phase II
LTE1709 Liquid Cell TM9 CSI-RS may interference to NB-IoT
(FL18 SP candidate)
LTE1542 FDD Supercell
Combined Supercell requires specific LTE3673:IoT Coexistence with High-Speed UEs & Supercell
LTE2091 Extended SuperCell DSP deployment ( currently not (FL17A-SP or FL18). Supercell for NB-IoT users: LTE3730 NB-IoT:
supported). Enhancements and Improved Feature interactions - Phase II (FL18 SP candidate)
LTE2445 Combined Supercell
eMBMS may have interference to/from LTE3730 NB-IoT: Enhancements and Improved Feature interactions - Phase II
LTE1117 LTE eMBMS
NB-IoT. (FL18 SP candidate)
LTE1113 eICIC LTE3571 NB-IoT: Enhancements and Improved Feature interactions - Phase I
NB-IoT has interference on eICIC ABS (FL18 candidate)
LTE1496 eICIC subframes. LTE3730 NB-IoT: Enhancements and Improved Feature interactions - Phase II
(FL18 SP candidate)
MicroDTX may mute the subframes
LTE1891 MicroDTX
impacting NB-IoT
LTE3571 NB-IoT: Enhancements and Improved Feature interactions - Phase I
LTE495 OTDOA PRS subframes will interfere with Nb-IoT.
(FL18 candidate)
LTE819 DL inter-cell Dummy load generation on both host LTE
interference generation cell and NB-IoT cell are not supported
LTE1900, LTE2470, LTE2291, CRAN will not be supported in the host
Under study for FL18A
LTE2564 centralized RAN cell.
129 © Nokia 2016 Customer Confidential
Deployment Aspects
Selection of PRBs for NB-IoT cell

• NB-IoT DL PRB can be configured from predefined PRB indexes, allowing for the lowest frequency
error NBIOT_FDD: inbandPRBIndexDL

LTE system bandwidth 5 MHz 10 MHz 15 MHz 20 MHz

2, 7, 12, 17, 22, 27, 32, 42, 47, 4, 9, 14, 19, 24, 29, 34, 39, 44, 55,
DL PRB indices 2, 7, 17, 22 4, 9, 14, 19, 30, 35 40, 45
52, 57, 62, 67, 72 60, 65, 70, 75, 80, 85, 90, 95

• NB-IoT UL PRB can be configured from any uplink PRB not used for PRACH/PUCCH and possible
PRACH/PUCCH if dynamic PUCCH enabled in host LTE cell NBIOT_FDD: inbandPRBIndexUL
• Selection of UL PRB should also avoid fragmentation of PUSCH resources. Since Rel. 8/9 UE are
able to allocate only contiguous PRBs in UL, improperly selected PRB may lead to the degradation of
UL throughput performance.

130 © Nokia 2016 Nokia Internal Use

Deployment Aspects
Selection of UL PRB for NB-IoT cell

• The approach of PRB selection depends on whether LTE1130 Dynamic PUCCH allocation is activated
• If LTE1130 Dynamic PUCCH allocation is not in use the adjacent PRB near PUCCH is preferred.
• Non-overlapped PRACH area have be selected by PRACH offset (prachFreqOffset)

Separated PUSCH areas fragmentation of PUSCH resources

NB-IoT
PRACH NOK

PUSCH area 1 PUSCH area 2

NB-IoT

PRACH OK

PUSCH area

• Another option is PRB from the outer region outside area in host LTE cell by LTE768 PUCCH blanking .
Disadvantage of such solution is unused PRB; the feature blanks PUCCH on both sides of the spectrum.
Moved PUCCH Moved PUCCH
NB-IoT

PRACH Unused PRB resources

131 © Nokia 2016 Nokia Internal Use

Deployment Aspects
Selection of UL PRB for NB-IoT cell

• If LTE1130 Dynamic PUCCH allocation is in use. The features estimates PUCCH resources, based on
parameters set by operator and activated features. Since number of PRBs for PUCCH is not explicitly
defined, it have to be tracked from the counters (PRB used PUCCH (M8011C49)).
• NB-IoT carrier have to be adjacent to PUCCH. PRACH allocation should be opposite to the NB-IoT carrier
(APUCCH: selectPrachRegion)
Note: In current design,
PUCCH area, PUCCH area, when LTE1130 is activated
APUCCH: selectPrachRegion=
M8011C49/2 M8011C49/2 (actAutoPucchAlloc=true),
InnerUpperEdge
MaxPucchResourceSize is
NB-IoT

set to 12, what means that

NB-IoT

PUCCH PRACH PUCCH

lowest NB-IoT PRB is 7th
from each edge.

• There is also option to locate NB-IoT carrier in the outer, blanked PUCCH areas. It causes UL capacity
degradation since one of the outer areas is unused.
Blanked APUCCH: selectPrachRegion= Blanked
PUCCH InnerUpperEdge PUCCH
NB-IoT

PUCCH PRACH PUCCH

132 © Nokia 2016 Nokia Internal Use

Deployment Aspects
NB-IoT power boosting

• DL power of NB-IoT carrier is derived from the eNB DL power equally distributed among all the PRBs.
Example for 10 MHz and 43dBm eNB DL power:
PowerDL NB-IoT = PowerHost LTE - 10 ∙ log (NPRB Host) = 43 - 10 ∙ log (50) = 26 dBm (0.4 W)

LTE BW [MHz] 5 MHz 10 MHz 15 MHz 20 MHz

DL power per PRB [W] 0.8 0.4 0.27 0.2

26dBm
0.4 W

43dBm / 20 W

• DL power can be insufficient for reaching deep indoor mobiles, that is why power boost up to 6dB is
foreseen for the NB-IoT carrier

133 © Nokia 2016 Nokia Internal Use

Deployment Aspects
NB-IoT power boosting

• Scheduler allocates resources in the RBG (Resource Block Group), with size depending on the LTE BW.
The whole RBG with NB-IoT carrier is excluded from the legacy traffic allocation. It means that power of
the non-used PRBs in the RBG can be used for NB-IoT carrier boosting.

LTE BW [MHz] 5 MHz 10 MHz 15 MHz 20 MHz

RBG Size
2 3 4 4
[PRB]

• For 15/20MHz, the NB-IoT PRB power boost can be achieved from 3 neighbor PRBs in same RBG,
while for 5/10MHz, it can be taken from 1/2 neighbor PRBs in same RBG.
• When it is not sufficient, wideband power reduction is applied
NB-IoT
10MHz example Power boost
NB-IoT

RBG=3
134 © Nokia 2016 Nokia Internal Use
Deployment Aspects
NB-IoT power boosting

• Power reduction of other PRBs in wide band host cell is needed when sum of unused RBG PRBs in [W]
exceeds NB-IoT carrier power boost. Mostly in concerns 5MHz LTE BW.
• Power reduction is applied by the system automatically.
LTE BW [MHz] 5 MHz 10 MHz 15 MHz 20 MHz
DL power per PRB [W] 0.8 0.4 0.27 0.2
Unused PRB power [W] 0.8 0.8 0.8 0.6 (RBG-1) ∙ DL_PowerPRB
Max DL power per PRB (w/boost) [W] 1.6 1.2 1.06 0.8 RBG ∙ DL_PowerPRB
NB-IoT carrier power @3dB boost [W] 1.60 0.80 0.53 0.40 2 ∙ DL_PowerPRB
NB-IoT carrier power @6dB boost [W] 3.18 1.59 1.06 0.80 3.97 ∙ DL_PowerPRB
Host LTE cell power reduction per PRB @6dB (DL_PowerNB-IoT – Max_DL_PowerNB-IoT)/(NPRB–RBG
0.07 0.01 0 0
[W]
Host LTE cell power reduction per PRB @6dB
0.4 0.1 0 0
[dB]

NB-IoT power boost calculator

(NPO Chris Johnson)

135 © Nokia 2016 Nokia Internal Use

Deployment Aspects
Selection of initial MCS for NB-IoT cell

• NB-IoT cell does not support link adaptation procedure. Hence selected UL (NBIOTPR: iniMcsUl )
and DL MCS (NBIOTPR: iniMcsDl ) is used during the whole IoT call duration. Please also note that
only first level coverage with pathloss target up to 144dB is supported with the feature.
• Selection of UL MCS has the higher importance as only uplink originated messages are supported.
The lowest MCS are the most robust, however its low TBS size cause message fragmentation and
increases message transfer. Examples: 200 bytes message size, EPA model

[#] [ms] [dB] [kbps]

136 © Nokia 2016 Nokia Internal Use

Deployment Aspects
Host LTE cell capacity loss

• DL Scheduler allocation is organized in RBG groups. Unused PRBs from the group containing
NB-IoT carrier can not be used for legacy traffic, what causes degradation of the throughput.
10MHz example

NB-IoT
RBG

LTE BW [MHz] 5 MHz 10 MHz 15 MHz 20 MHz

RBG Size [PRB] 2 3 4 4

DL Capacity loss 8% 6% 5% 4%

137 © Nokia 2016 Nokia Internal Use

Deployment Aspects
Object Model
LNBTS NBIOTP Profiles for IoT
R ‘semi-static’ parameters

nprachCpLen
SIB configuration parameters
srbInactivityTimerNB
cpInactivityTimerNB
LNCEL LNCEL
(host) (NB-IoT)
First level coverage (LTE3071)
lrcId = 1 lrcId = 2 nprachProfNBNorCov structure – NPRACH
CellTechnology= LNCEL_FDD CellTechnology = NB-IoT-FDD rachProfNBNorCov structure – NB-IoT RACH
PLMN (LTE cell) PLMN (NB-IoT cell) cssProfNorCov structure – NPDCCH CSS
Cell Id (LTE cell) Cell Id (NB-IoT cell) rlcProfNBNorCov structure – NB-IoT RLC
TAC (LTE cell) TAC (NB-IoT cell) macProfNBNorCov structure – NB-IoT MAC
nbIoTMode = inband nbIoTMode = inband schedProfNBNorCov structure – NB-IoT
nbIotLinkedCellId = 2 nbIotLinkedCellId = 1 Scheduler
…
…
Second level coverage (LTE3840)
LNCEL_FD NBIOT_FD …
D D
Third level coverage (LTE3840)
inbandPRBIndexUL
…
inbandPRBIndexDL
syncSigTxMode
maxNumRrcNB
dlPwrBoost
nbIoTProfId = {profile #1}

138 © Nokia 2016 Nokia Internal Use

Deployment Aspects
LTE3071 limitation

• Features which are exclusive with LTE3071 have to be deactivated in the host cell, even though
these consistency checks are not explicitly specified.
• MBSFNCEL: mbsfnCelId, actMBMS
• eMBMS will be disabled in wideband host LTE cell by not configuring MBSFNCEL managed object for that LNCEL instance. BTS
level deactivation (actMBMS) is not needed.
• LNBTS: actCRAN=false ,CRAN will not be supported in eNB if there is NB-IoT cell in this BTS
• ULCOMP: ulCoMpCellList, actUlCoMp
• NB-IoT cell and WB-host cell are excluded from Uplink CoMP Cell List that other cells belong to. BTS level ULCoMP deactivation
(actULCoMP) is not needed.
• LNCEL: actEicic=false, NB-IoT has interference on eICIC ABS subframes
• LNCEL: actMicroDtx=false, MicroDTX may muste the subframes impacting NB-IoT
• LNCEL: actOtdoa=false, OTDOA PRS may has the interference to/from NB-IoT.

139 © Nokia 2016 Nokia Internal Use

Deployment Aspects
LTE3071 limitation

• Features which are exclusive with LTE3071 have to be deactivated in the host cell, even though
these consistency checks are not explicitly specified.
• LNCEL: csgType=openAccess, The wideband host LTE cell can't be set to CSG cell.
• LNCEL_FDD: actCatM=false, Simplify the implementation and verification. NB-IoT and Cat-M can be enabled in
different cells in one eNB.
• LNCEL_FDD: actCombSuperCell=false Combined Supercell requires specific DSP deployment.
• LNCEL_FDD: actLiquidCell=false, LNCEL_FDD: actSuperCell=false, Super Cell and Liquid cell requires specific
DSP deployment (not supported in FL17). Liquid cell: TM9 CSI-RS may interference to NB-IoT

140 © Nokia 2016 Nokia Internal Use

 Note: at the time of materials
Deployment Aspects preparation final Site Manager
Feature activation version was not available.
Details may differ in the
product version.
• STEP 1 – Host cell

LNBTS NBIOTP
actNBIoT value is set to “inband R

LNCEL LNCEL
(host) (NB-IoT)

inbandLinkedCellId shall be set to the

associated NB-IoT concrete cell’s lcrID

LNCEL_FD NBIOT_FD
D D

ulChBw, dlChBw shall be set to either

5, 10, 15 or 20 MHz

141 © Nokia 2016 Nokia Internal Use

Deployment Aspects
Feature activation

• STEP 2 – Creation of NB-IoT cell

Legacy LTE host cell NB-IoT cell
LNBTS NBIOTP
R

2TX2RX host LNCEL LNCEL

(host) (NB-IoT)
cell
configuration

NB-IoT cell type assigned

LNCEL_FD NBIOT_FD
to the sam antenna ports D D
as the legacy LTE host
cell

142 © Nokia 2016 Nokia Internal Use

 LNBTS NBIOTPR
Deployment Aspects
Feature activation LNCEL LNCEL
(host) (NB-IoT)

• STEP 3 – configuration of NBIOT_FDD-0 object

NBIOT_FDD-0 object
LNCEL_FD NBIOT_FD
D D

Single NB-IoT carrier possible with LTE3071

2TX2RX host DL power boost

cell
configuration Single NBIOTPR profile

Legacy and NB-IoT RRC connected users < 840

PRB predefined for DL

Remember PUSCH and PRACH restrictions

Only first level coverage level

Number of ports for NPSS/NSSS

143 © Nokia 2016 Nokia Internal Use
 LNBTS NBIOTPR
Deployment Aspects
Feature activation LNCEL LNCEL
(host) (NB-IoT)

• STEP 4 – add NBIOTPR profile on the LNBTS level

LNCEL_FD NBIOT_FD
D D

NBIOTPR object
Single NBIOTPR object for first level coverage

C-plane inactivity

Only normal cyclic prefix supported with

LTE3071

SIB1-NB repetitions

SIB2-NB offset

SIB2-NB window

SRB inactivity
Note: All the paging related parameters are not applicable to LTE3071

144 © Nokia 2016 Nokia Internal Use

 LNBTS NBIOTPR
Deployment Aspects
Feature activation LNCEL LNCEL
(host) (NB-IoT)

• STEP 5 – remaining NBIOTPR profile parameters LNCEL_FD NBIOT_FD

D D

SIB2-NB periodicity

SIB2-NB repetition pattern

t300NB supervises the RRC connection

establishment procedure
t301NB supervises the RRC reestablishment
procedure; NOT SUPPORTED with LTE3071
Timer t310NB supervises the recovery from
physical layer problems
t300NB guards the period between RRCConnectionRequest
and reception of RRCConnectionSetup or RRCConnectionReject.

t310NB starts upon detecting physical layer problems i.e. upon receiving
n310 consecutive out-of sync indications from lower layers and stops upon
receiving n311 consecutive in-sync indications from lower layers

145 © Nokia 2016 Nokia Internal Use

 LNBTS NBIOTPR
Deployment Aspects
Feature activation LNCEL LNCEL
(host) (NB-IoT)

• STEP 6 – CSS profile for first level coverage

LNCEL_FD NBIOT_FD
D D

Max number of repetitons 4 and starting

subframes = 2, results in search space
equal to 8 SF

• STEP 7 – MAC profile for first level coverage

MAC prohibit timer, to delay the transmission of
an SR in NB-IoT, to wait the potential UL grant
for the UL transmission.

BSR (Buffer Status Reporting)timer, regular

BSRs are repeated for cases when the UE has
data available for transmission and no
corresponding UL grant is received

146 © Nokia 2016 Nokia Internal Use

 LNBTS NBIOTPR
Deployment Aspects
Feature activation LNCEL LNCEL
(host) (NB-IoT)

• STEP 8 – NPRACH profile

48 subcarriers x 3.75 kHz

NPRACH NPRACH NPRACH NPRACH
sequence repetition repetition repetition
4 x 1.6 ms = 6.4 LNCEL_FD NBIOT_FD

180 KHz
ms D D

Single UE NPRACH, 4 repetitions, 25.6 ms

Max number of preamble attempts

NPRACH periodicty

Start time of the NPRACH resource in one period

NPRACH subcarrier offset; LTE3071=0 for 48

subcarriers

Preamble attempt per NPRACH

NPRACH preambles; LTE3071=48

147 © Nokia 2016 Nokia Internal Use

Deployment Aspects
Feature activation UE eNB

• STEP 9 – RACH profile

raRespWinSizeNB
Random Access
NPRACH msg1
Contention
resolution timer RAR scheduling
NPDCCH

RA response timer Random Access Response

NPDSCH
msg2

RRC: Connection Request

raContResoTimNB timer defines the maximum amount of time msg3

raContResoTimNB
NPUSCH
allowed for the contention resolution . The eNB sends
RRCConnectionSetup scheduling
RRCConnectionSetup-NB (msg4) over NPDSCH, inside the
NPDCCH
contention resolution timer. In case msg4 is not received within timer
RRCConnectionSetup-NB
period, RACH access procedure is repeated, providing that NPDSCH
msg4
nprachMaxNumPreambleCE settings is not reached
RRCSetupComplete scheduling
NPDCCH
raRespWinSizeNB window size for the random access response.
RAR (msg2) is sent over NPDSCH. RAR is expected inside the RAR RRCConnectionSetupComplete-NB
msg5
NPUSCH
response window.

148 © Nokia 2016 Nokia Internal Use

Deployment Aspects
Feature activation

• STEP 10 – RLC profile

RLC retransmission threshold

Poll retransmit

maxRetxThreNB the maximum number of poll retransmission for the

transmitting side of an AM RLC entity in NB-IoT. 3GPP:
LNBTS NBIOTPR
maxRetxThreshold-r13

tPollRetrNB LNCEL LNCEL

parameter specifies the parameter t-pollRetransmit-r13 of [36.331]. (host) (NB-IoT)
This timer is used by the transmitting side of an AM RLC entity in order
to retransmit a poll. 3GPP: t-PollRetransmit-r13

LNCEL_FD NBIOT_FD
D D

149 © Nokia 2016 Nokia Internal Use

 LNBTS NBIOTPR
Deployment Aspects
Feature activation LNCEL LNCEL
(host) (NB-IoT)

• STEP 11 – Scheduler profile

LNCEL_FD NBIOT_FD
D D

Initial MCS DL

Initial MCS UL

NPDCCH repetition; LTE3071=2

NPDSCH repetition; LTE3071=1

NPUSCH repetition; LTE3071=1

ACK repetition; LTE3071=1

MSG4 repetition; LTE3071=1

150 © Nokia 2016 Nokia Internal Use

Deployment Aspects
Supported configurations
• Inband NB-IoT cells don’t require any additional BB HW, IQ data of inband NB-IoT cells is contained
inside the IQ data of the host cell. AirScale is not supported by LTE3071. Supported NB-IoT
configurations:

Single HW board (either FSMF or FBBA/C) within a Basic Cell Set

3*5/10/15/20MHz 2Tx/2Rx cells + 3 NB-IoT cells

2 HW boards (FSMF + FBBC/A) with extended Cell Set

6*5/10/15/20MHz 2Tx/2Rx cells + 6 NB-IoT cells OR

3 HW boards (FSMF + 2 FBBC/A) with XL-Cell-Set

9*5/10/15/20MHz 2Tx/2Rx cells + 9 NB-IoT cells OR

FZM
1*5/10/15/20MHz 2Tx/2Rx cells+ 1*NB-IoT 2Tx/2Rx cells

151 © Nokia 2016 Nokia Internal Use

Deployment Aspects
RF module

• Inband NB-IoT cells are transparent to the RF modules

• Inband NB-IoT and hosting LTE can be RF shared with GSM or WCDMA assuming first
level RF sharing is supported for the hosting LTE cell itself
• Only OBSAI and Nokia-CPRI protocols are supported
• All the RF modules supporting 2Tx2Rx are feasible for inband NB-IoT,
as listed by Supported Configurations xls. Please note bands restrictions for NB-IoT
stated by 3GPP.

152 © Nokia 2016 Nokia Internal Use

Deployment Aspects
S1 and MME
IP Control IP Gateway
• NB-IoT traffic has different nature than the one
coming from the legacy LTE users. A lot of small
messages is not well suited for the network SGW(IoT) PGW(IoT)
MME Pool (IoT)
optimized towards mobile broadband.
• That is why it is suggested to provide separate IP Control IP Gateway
core network optimized for IoT traffic
• Simplified core, lack of legacy specific features,
e.g. Voice Support, VoLTE , allows for better
utilization of resources. MME Pool (MBB) SGW(MBB)PGW(MBB)

MME type connected to eNB is indicated by S1 for NB-IoT can be selected via two different methods:
LNMME: mmeRatSupport
• Dedicated S1 for NB-IoT UEs (i.e. NB-IoT gets its own separate
• only legacy LTE (‘WB-EUTRA MME’), S1 selected always)
• only NB-IoT (‘NB-IoT MME’) • PLMN based S1 selection (Inband NB-IoT traffic is directed to
• both legacy LTE and NB-IoT (‘integrated MME’). same core as legacy LTE traffic of the hosting cell)

153 © Nokia 2016 Nokia Internal Use

Deployment Aspects
Alarms
• No new alarms are expected in LTE3071.

• One legacy alarm (Cell Setup Failure) will be re-used to indicate that host cell or
inband NB-IoT cell was disabled.

154 © Nokia 2016 Nokia Internal Use

Deployment Aspects
Devices and chipsets for NB-IoT

• In general, commercial modules for both NB-IoT & Cat-M are expected 1Q17

• Main players:
• Intel announced the XMM7115 NB-IoT chipset and the XMM7315 Cat-M/NB-IoT
• Neul NB-IoT chipset
• Sequans introduced Monarch Cat-M chipset, which will also support NB-IoT,
partnering with Gemalto for commercial modules
• Qualcomm Cat-M chipset (MDM9206)

155 © Nokia 2016 Nokia Internal Use

Deployment Aspects
Devices and chipsets for NB-IoT

Planned Estimated D: Demo L: Launch

156 © Nokia 2016

Let’s have a short coffee break!

157 © Nokia 2016 Nokia Internal Use

LTE3071 NB-IoT

Dimensioning
Aspects
Table of contents

<chapter:dimensioning>

158 © Nokia 2016 Nokia Internal Use

Dimensioning
Dimensioning tools
NB-IoT Link budget tool NB-IoT Capacity calculator
24

• Link budget calculates

Downlink Uplink
Operat ing band [MHz] 850
MAR 2
Int erarrival (h) / Share
Sensors deployment St at ionary report s 1
General
NB- IoT carrier conf igurat ion In- band 0.5
paramet ers
Legacy LTE channel bandwidt h [MHz] 10
Legacy LTE DL t ransmission scheme
Tx ant enna power [dBm]
Ant enna gain [dBi]
Feeder loss [dB]
2Tx MIMO (TM2/ 3/ 4)
43.0
18.0
0.5
23.0
0.0
-
Traffic
model
BHCA
#UE
#UE at t empt s/ cell/ s
0.47
52547
6.8
cell ranges taking into
Transmit t ing

account LTE3071
DL NB- IoT Power Boost ing [dB] 0.0 - UL message size (byt es) 200
end Legacy cell power reduct ion per PRB [dB] 0.0 - NPRACH periodicit y [ms] 160
Tx power increase [dB] 3.0 0.0 48
NPRACH bandwidt h (t ones)
Ef f ect ive NB- IoT EIRP per user [dBm] 46.5 23.0
RACH collision probabilit y [%] 2.5
Feeder loss [dB] - 0.5
Receiving
end
Ant enna gain [dBi]
Noise f igure [dB]
Addit ional gains [dB]
Ref erence Signal (legacy LTE) [%]
0.0
5.0
0.0
9.52%
18.0
3.0
0.0
-
NPRACH
capacit y
NPRACH recept ion probabilit y [%]
max RACH load
RACH at t empt s (f rom t raf f ic model) [1/ s]
90
1.2
7.6
parameterization and
NPRACH occasions [1/ s] 7.6
PDCCH (legacy LTE) [%]
NB Primary Synchronizat ion Signal (NPSS) [%]
NB Secondary Synchronizat ion Signal (NSSS) [%]
NB Ref erence Signal (NRS) [%]
19.05%
7.20%
3.93%
9.52%
-
-
-
-
Max # UEs (RACH)
Maximum number of NPDCCH repet it ions (R_max )
NPDCCH st art ing subf rame period (G )
52733
4
2
overheads.
NB Broadcast Channel (NPBCH) [%] 5.95% - NPDCCH NPDCCH periodicit y (search space lengt h) [ms] 8

• Capacity calculator
SIB1- NB repet it ions 4 - capacit y NPDCCH occasion/ s 125
NB Syst em Inf ormat ion Block 1 (SIB1- NB) [%] 0.77% - #DCI per UE call 12
SIB2- NB lengt h [subf rames] 8 - # UE/ s (NPDCCH limit ) 8
SIB2- NB repet it ion pat t ern [radio f rames] 16 -
Syst em SIB2- NB periodicit y [ms] 2560 -
NPDCCH t ransmission lengt h [ms] 2
NPDCCH -> NPDSCH gap [ms] 4

estimates capacity of
overhead SIB2- NB window lengt h [ms] 160 -
NB Syst em Inf ormat ion Block 2 (SIB2- NB) [%] 0.19% - TBS t ransmission t ime on NPDSCH [ms] 4
Maximum number of NPDCCH repet it ions (R_max ) 16 - NPDSCH NPDSCH -> NPUSCH (A/ N) gap [ms] 12
NPDCCH st art ing subf rame period (G) 2 -
NPDCCH repet it ion level 2 -
t iming NPUSCH (A/ N) lengt h [ms] 2
NPDCCH overhead [%]
NPRACH periodicit y [ms]
NPRACH repet it ion level
NPRACH overhead [%]
4.95%
-
-
-
-
160
4
16.25%
NPUSCH (A/ N) / NPUSCH -> NPDCCH gap [ms]
HARQ percent age [%]
Tot al DL TBS t ransmission t ime [ms]
3
10
30
NPRACH, NPDCCH and
NPDCCH t ransmission lengt h [ms] 2
Addit ional overhead [%]
Tot al syst em overhead [%]
Message size [byt es]
Number of NPDSCH subf rames / NPUSCH Resource Unit s
0.00%
61.10%
10
4
0.00%
16.25%
200
4
NPUSCH
t iming
NPDCCH -> NPUSCH gap [ms]
TBS t ransmission t ime on NPUSCH [ms]
NPUSCH -> NPDCCH (A/ N) gap [ms]
8
32
3
NPUSCH channels. As
expected that mobile
Number of NPUSCH t ones per user - 1 HARQ percent age [%] 10
Modulat ion and coding scheme (User def ined) 0- QPSK 10- QPSK Tot al UL TBS t ransmission t ime [ms] 50
Residual BLER t arget rBLER = 10%
Service Number of message repet it ions 1 1 NPRACH t ransmission lenght [ms] 26
Transport Block Size f or NPDSCH / NPUSCH [bit s] 88 680 NPDCCH scheduling t ime [ms] 8
Number of TBSs required t o send t he message
Est imat ed user t hroughput (single UE) [kbps]
Modulat ion ef f iciency (dat a bit s/ modulat ed symbol)
Ef f ect ive Coding Rat e
1
0.31
0.34
0.17
3
5.83
1.81
0.91
Call
Set up
t iming
Number of NPDCCH per RACH procedure
DL message t ransmission lenght [ms]
UL message t ransmission lenght [ms]
3
30
50
originated traffic will be
dominating, only UL data
Channel model Enhanced Pedest rian A 1Hz NPRACH recept ion probabilit y 90
NB- IoT t ransmission scheme 2Tx- 1Rx 1Tx- 2Rx Tot al Call set up t ime [ms] 211
Required SINR @ BLER10% [ref erence] [dB] 6.56 11.84 UL MCS (User def ined) 3- QPSK
Repet it ions gain [dB] 0.00 0.00
TBS index 3
Required SINR at cell edge [dB] 6.56 11.84

Channel
Int erf erence Margin [dB]
Number of received subcarriers [dB]
Thermal noise densit y [dBm/ Hz]
Subcarrier bandwidt h [kHz]
3.00
10.79
- 173.93
15
3.00
0.00
UL
set t ings
Transport Block Size f or NPUSCH [bit s]
UL BLER [%]
Number of TBSs required t o send t he message
208
10
9
channels are considered.
NPUSCH t ransmission durat ion [ms] 446
Noise power per subcarrier [dBm] - 132.17

• Tools are available here.

Receiver sensit ivit y [dBm] - 109.82 - 117.33
Average NB- IoT Call durat ion (including CS) [ms] 657
Maximum Allowable Pat h Loss [dB] Average t hroughput per NB- IoT UE (Tx) [kbit / s] 3.59
153.34 154.83
(clut t er not considered) NPUSCH NPUSCH overhead [%] 16
Link used f or cell range calculat ions Limit ing link capacit y UL resources ut ilisat ion f act or [%] 90
RSRP (clut t er not considered) [dBm] - 120.62 - 122.11
Average number of UEs/ Cell (TX) 64398

Dense Urban Urban Suburban Rural (quasi)

Maximum Allowable Pat h Loss (limit ing link) [dB]
153.34
(clut t er not considered)
eNB ant enna height [m] 30 30 30 50
Sensor ant enna height [m] 0.5 0.5 0.5 0.5
Average penet rat ion loss [dB] 18.0 13.0 8.0 3.0

159 © Nokia 2016 St andard deviat ion out door [dB]

St andard deviat ion of penet rat ion loss [dB] Nokia Internal Use
9.0
0.0
8.0
0.0
8.0
0.0
7.0
0.0
Combined st andard deviat ion [dB] 9.00 8.00 8.00 7.00
Locat ion probabilit y 942 911 861 783
Cell area probabilit y [%] 98.00% 97.01% 95.00% 92.01%
Locat ion / Cell edge probabilit y [%] 94.20% 91.10% 86.10% 78.30%
Dimensioning

NB-IoT coverage

160 © Nokia 2016 Nokia Internal Use

Dimensioning
Link Budget

• LTE3071 supports only first level coverage, in the range of legacy LTE. Further coverage
enhancements are subject of subsequent FL17SP features.
Note that selected bands are allowed
Downlink Uplink for NB-IoT within Rel 13
Operating band [MHz] 900
Sensors deployment Stationary
General
NB-IoT carrier configuration In-band
parameters Only TM2 for LTE3071
Legacy LTE channel bandwidth [MHz] 10
Legacy LTE DL transmission scheme 2Tx MIMO (TM2/3/4)
Tx antenna power [dBm] 43.0 23.0 Host legacy LTE cell power
Power per PRB [W] 0.40 -
Antenna gain [dBi] 18.0 0.0 DL power boosting up to 6 dB
Transmitting Feeder loss [dB] 0.5 -
end DL NB-IoT Power Boosting [dB] 6.0 - Legacy cell power reduction due to
Legacy Cell Power Reduction per PRB [dB] 0.1 - power boost
Tx power increase [dB] 3.0 0.0
EIRP per NB-IoT UE calculated from
Effective NB-IoT EIRP per user [dBm] 52.5 23.0
the PSD and power boost for 1PRB
Feeder loss [dB] - 0.5
Receiving Antenna gain [dBi] 0.0 18.0 Preliminary values
end Noise figure [dB] 5.0 3.0
Additional gains [dB] 0.0 0.0
161 © Nokia 2016 Nokia Internal Use
Dimensioning
Link Budget

Reference Signal (legacy LTE) [%] 9.52% - numSib1RepNB

PDCCH (legacy LTE) [%] 19.05% -
NB Primary Synchronization Signal (NPSS) [%] 7.20% - Depends on the SIB2 TBS: 56/120 bits TBS 2
NB Secondary Synchronization Signal (NSSS) [%] 3.93% - subframes, remaining
NB Reference Signal (NRS) [%] 9.52% - 8 subframes
NB Broadcast Channel (NPBCH) [%] 5.95% -
SIB1-NB repetitions 4 - sib2RepPatternNB
NB System Information Block 1 (SIB1-NB) [%] 0.77% -
SIB2-NB length [subframes] 8 - sib2PeriodicityNB
SIB2-NB repetition pattern [radio frames] 16 -
SIB2-NB periodicity [ms] 2560 - siWindowLenNB
System SIB2-NB window length [ms] 160 -
overhead NB System Information Block 2 (SIB2-NB) [%] 0.19% - npdcchMaxNumRepRa
Maximum number of NPDCCH repetitions (R_max) 4 -
NPDCCH starting subframe period (G) 2 - npdcchStartSfRa; LTE3071=2
NPDCCH repetition level 2 -
Number of subscribers per cell 50000 - Assumed for NPDCCH overhead calculations
Subscriber BHCA 0.47 -
NPDCCH overhead [%] 13.00% - Assumed for NPDCCH overhead calculations
NPRACH periodicity [ms] - 160
NPRACH repetition level - 4
nprachPeriod
NPRACH overhead [%] - 16.25%
Additional overhead [%] 0.00% 0.00%
Total system overhead [%] 69.15% 16.25% nprachNumRepPreamble

162 © Nokia 2016 Nokia Internal Use

Dimensioning
Link Budget

LTE3071 supports only UE

Message size [bytes] 10 200 originated UL messages. Please
Number of NPDSCH subframes / NPUSCH align DL message size with limited
Resource Units 4 4 link.
Number of NPUSCH tones per user - 1
Modulation and coding scheme (User defined) 2-QPSK 2-QPSK
Residual BLER target rBLER = 10% There is no link adaptation for
Service LTE3071, selected MCS is used for
Number of message repetitions 1 1
Transport Block Size for NPDSCH / NPUSCH [bits] 176 144 all the transmission. It impacts TBS
size, and thus achievable
Number of TBSs required to send the message 1 13
throughputs and overheads
Estimated user throughput (single UE) [kbps] 0.50 2.11
Modulation efficiency (data bits/modulated symbol) 0.85 0.38 MCSs can be used to balance UL
Effective Coding Rate 0.42 0.19 and DL links.

163 © Nokia 2016 Nokia Internal Use

Dimensioning
Link Budget

LTE3071 supports only single

Enhanced Pedestrian antenna at UE and 2 antennas at
Channel model A 1Hz eNB
NB-IoT transmission scheme 2Tx-1Rx 1Tx-2Rx
Required SINR @ BLER10% [reference] [dB] 9.05 1.78
Repetitions gain [dB] 0.00 0.00
Required SINR at cell edge [dB] 9.05 1.78
Interference Margin [dB] 3.00 3.00
Channel Thermal noise density [dBm/Hz] -173.93
DL is weaker since there is just
Subcarrier bandwidth [kHz] 15 single antenna at UE. MCS can be
Noise power per subcarrier [dBm] -132.17 selected accordingly to balance
Receiver sensitivity [dBm] -107.33 -127.39 links.
Maximum Allowable Path Loss [dB]
(clutter not considered) 156.85 164.89
Link used for cell range calculations Limiting link Allows for checking UL or DL cell
RSRP (clutter not considered) [dBm] -118.13 -126.17 ranges independently

Note: 3GPP Normal coverage pathloss (144dB) has different assumptions

164 © Nokia 2016 Nokia Internal Use

Dimensioning
Link Budget
Dense Urban Urban Suburban Rural (quasi)
Maximum Allowable Path Loss (limiting link)
[dB] 161.58
(clutter not considered) Differs from the legacy LTE, since
eNB antenna height [m] 30 30 30 50 IoT devices (e.g. Smart meters ) are
Sensor antenna height [m] 0.5 0.5 0.5 0.5 expected at lower heights
Average penetration loss [dB] 18.0 13.0 8.0 3.0
Standard deviation outdoor [dB] 9.0 8.0 8.0 7.0
Standard deviation of penetration loss [dB] 0.0 0.0 0.0 0.0 Improved NB-IoT coverage is not
Combined standard deviation [dB] 9.00 8.00 8.00 7.00 considered yet, since LTE3071 cope
with first level coverage only
Location probability
Cell area probability [%] 99.00% 99.02% 99.02% 99.02%
Propagation Location / Cell edge probability [%] 96.90% 96.70% 96.70% 96.50%
Log first level Fading margin [dB] 16.80 14.71 14.71 12.68
Gain Against Shadowing [dB] 0.00 0.00 0.00 0.00
Maximum Allowable Path Loss [dB]
(clutter considered) 126.78 133.87 138.87 145.90
RSRP (clutter considered) [dBm] -94.07 -101.15 -106.15 -113.18
Intercept Point (w/o clutter correction) [dB] 128.16 128.16 127.56 124.50
Slope 1 [dB] 35.22 35.22 35.22 33.77
Slope 2 [dB] 39.92 39.92 39.92 38.11
Clutter correction factor [dB] 3.00 0.00 -9.64 -23.01

Cell Range [km] 0.78 1.45 3.93 20.66

Inter Site Distance for 3-sector grid [km] 1.17 2.18 5.90 30.98

165 © Nokia 2016 Nokia Internal Use

Dimensioning
3GPP pathloss definition

• Normal pathloss (144 dB) 3GPP Channel NB-PDSCH NB-PUSCH

Data rate (kbps) 0.44 0.31
definition mentioned in the slideset
Transmitter
refers to the Maximum Coupling Max Tx power (dBm) 46 23
Loss MCL (1) Actual Tx power (dBm) 35 23

• MCL doesn’t consider antenna Receiver

gain, feeder losses and other (2) Thermal noise density (dBm/Hz) -174 -174

factors taken into account in the (3) Receiver noise figure (dB) 5 3
link budget for cell range (4) Interference margin (dB) 0 0

estimation; this is just reference (5) Occupied channel bandwidth (Hz) 180,000 15,000

value (6) Effective noise power

-116.4 -129.2
= (2) + (3) + (4) + 10 log ((5)) (dBm)
• For cell range estimation Maximum (7) Required SINR (dB) 6.56 0.52 NOKIA simulated
Allowable Pathloss MAPL is used, SINRs used for
(8) Receiver sensitivity = (6) + (7) (dBm) -109.9 -128.7
reference
considering all the aspects above. (9) Rx processing gain 0 0
(10) MCL = (1) -(8) + (9) (dB) 144.9 151.7

166 © Nokia 2016 Nokia Internal Use

Dimensioning
NB-IoT inband (LTE3071) Link budget v1.0
3GPP pathloss definition Operat ing band [MHz]
Downlink
900
Uplink

Sensors deployment St at ionary

General
NB- IoT carrier conf igurat ion In- band
paramet ers 0 dB antenna gain
• The same numbers can Legacy LTE channel bandwidt h [MHz]
Legacy LTE DL t ransmission scheme
10
2Tx MIMO (TM2/ 3/ 4) aligned with 3GPP
Tx ant enna power [dBm] 43.0 23.0
obtained in NB-IoT LB Ant enna gain [dBi]
Feeder loss [dB]
0.0
0.0
0.0
-
MCL
Transmit t ing
when antenna gain, end
DL NB- IoT Power Boost ing [dB]
Legacy cell power reduct ion per PRB [dB]
6.0
0.1
-
-
Tx power increase [dB] 3.0 0.0 0 dB feeder loss
feeder loss and Ef f ect ive NB- IoT EIRP per user [dBm] 35.0 23.0
aligned with 3GPP
Feeder loss [dB] - 0.0
interference margin are Receiving
end
Ant enna gain [dBi]
Noise f igure [dB]
0.0
5.0
0.0
3.0
MCL
aligned with 3GPP Addit ional gains [dB]
Message size [byt es]
0.0
10
0.0
200
Number of NPDSCH subf rames / NPUSCH Resource Unit s 4 4
• Note that 3GPP assumed Number of NPUSCH t ones per user
Modulat ion and coding scheme (User def ined)
-
0- QPSK
1
0- BPSK

6dB power boost for Service

Residual BLER t arget
Number of message repet it ions 1
rBLER = 10%
1
Transport Block Size f or NPDSCH / NPUSCH [bit s] 88 88
NB-IoT Number of TBSs required t o send t he message
Est imat ed user t hroughput (single UE) [kbps]
1
0.21
20
1.39
Modulat ion ef f iciency (dat a bit s/ modulat ed symbol) 0.53 0.23
Ef f ect ive Coding Rat e 0.27 0.23
Channel model Enhanced Pedest rian A 1Hz
NB- IoT t ransmission scheme 2Tx- 1Rx 1Tx- 2Rx
Required SINR @ BLER10% [ref erence] [dB] 6.56 0.52
Repet it ions gain [dB] 0.00 0.00
Required SINR at cell edge [dB] 6.56 0.52
Int erf erence Margin [dB]
Number of received subcarriers [dB]
0.00
10.79
0.00
0.00
0 dB interference
Channel Thermal noise densit y [dBm/ Hz] - 173.93 margin aligned with
Subcarrier bandwidt h [kHz] 15
Noise power per subcarrier [dBm] - 132.17 3GPP MCL
Receiver sensit ivit y [dBm] - 109.82 - 128.65
Maximum Allowable Pat h Loss [dB]
144.84 151.65
(clut t er not considered)
Link used f or cell range calculat ions Limit ing link
RSRP (clut t er not considered) [dBm] - 123.62 - 130.43

167 © Nokia 2016 Nokia Internal Use

Dimensioning

NB-IoT capacity

168 © Nokia 2016 Nokia Internal Use

Dimensioning
NB-IoT Capacity Target
• NB-IoT was defined by 3GPP taking into account typical inter site distance and
household density for urban area. Each location should handle up to 40 IoT devices.
• Capacity target is 52547 devices within a cell site sector
R
ISD
Cell site
sector area

Case Household Density Inter-site Distance Number of devices Number of

per Sq km (ISD) (m) within a household devices within a
cell site sector
Urban 1517 1732 m 40 52547

169 © Nokia 2016 Nokia Internal Use

Dimensioning
3GPP IoT traffic model (45.820 Annex E)

Report type Packet size Inter-arrival time

Mobile Autonomous Reporting (MAR) exception UL: 20 bytes Months to years (reaction time
reports up to 10 second latency)
 E.g. smoke detectors, power failure notifications from smart
meters, tamper notifications etc.

Mobile Autonomous Reporting (MAR) periodic UL: 20 - 200 bytes 40%: Once per day
reports Pareto distributed 40%: Once every 2 hours
15%: Once per hour
 E.g. smart utility (gas/water/electric) metering reports, smart
5%: Once per 30 min
agriculture etc. DL: Ack => Mean = 0.47 times per hour

Network originated reports DL: 20 bytes 40%: Once per day

 E.g. trigger the device to send an uplink report as a result of 40%: Once every 2 hours
15%: Once per hour
the network command e.g. request for a smart meter reading UL: 20 – 200 bytes 5%: Once per 30 min
Pareto distributed => Mean = 0.47 times per hour

Software update/reconfiguration model DL: 200 - 2000 bytes 180 days

 Software updates or patches of Cellular IoT devices. Rare, Pareto distributed
but large payload sizes expected for complete software
updates

170 © Nokia 2016 Nokia Internal Use

Dimensioning
Traffic model

• As paging is not supported in LTE3071, only UE initiated Mobile autonomous

reporting MAR are expected. Network cannot initiate connection for a NB-IoT cell.
• 3GPP target of 50k UE served per cell is fulfilled under 45.820 traffic model, where
distribution of messages size and their periodicity is defined. Generally NB-IoT supports
infrequent, small messages.
• From 3GPP distribution of MAR reports 0.47 BHCA is obtained with Pareto distributed
message size of 20-200 bytes.
• Number of attempts during BH:

#𝑈𝐸∙𝐵𝐻𝐶𝐴 52547∙0.47
𝐴𝑡𝑡𝑒𝑚𝑝𝑡𝑠/𝑐𝑒𝑙𝑙/𝑠 = = = 6.8
3600 3600

171 © Nokia 2016 Nokia Internal Use

Dimensioning
NPRACH capacity
• RACH attempts per cell due UE transition from idle to connected depends on the number of devices
per cell and BHCA.
• We can assume certain probability for correct NPRACH reception PNPRACH which impacts number of
NPRACH messages needed.
#𝑈𝐸∙𝐵𝐻𝐶𝐴 52547∙0.47
𝑅𝐴𝐶𝐻 𝑎𝑡𝑡𝑒𝑚𝑝𝑡𝑠/𝑠 = = 3600∙0.9 = 7.6
3600 ∙ 𝑃𝑁𝑃𝑅𝐴𝐶𝐻

• The number of NPRACH preambles is limited, and RACH channel can be accessed by number of
UEs simultaneously, so when estimating NPRACH capacity expected RACH load and allowed
collision probability Pcoll should be assumed.
• RACH occasion is repeated every NPRACH periodicity nprachPeriod NPRACH slot

4xNPUSCH 4xNPRAC 4xNPUSCH 4xNPUSCH 4xNPUSCH 4xNPUSCH 4xNPUSCH 4xNPRAC 4xNPUSCH

32ms H 25.6ms 32ms 32ms 32ms 32ms 32ms H 25.6ms 32ms
NPRACH repetitions 160ms

−1 𝑃𝑐𝑜𝑙𝑙
ܴ‫ݏ݊݋݅ݏܽܿܿ݋ ܪܥܣ‬/‫= ݏ‬ 48 ∙ ln 1 −
𝑛𝑝𝑟𝑎𝑐ℎ𝑃𝑒𝑟𝑖𝑜𝑑 [𝑠] 100

172 © Nokia 2016 Nokia Internal Use

Dimensioning
NPRACH capacity

• Offered RACH traffic should not be higher than NPRACH occasions/s

𝑁𝑃𝑅𝐴𝐶𝐻 𝑜𝑐𝑐𝑎𝑠𝑠𝑖𝑜𝑛𝑠/𝑠 > 𝑅𝐴𝐶𝐻 𝑎𝑡𝑡𝑒𝑚𝑝𝑡𝑠/𝑠

• For the default traffic model and 90% of NPRACH reception probability the target of the offered
RACH traffic of 7.6 RACH/s can be guaranteed with collision probability lower than 2.5%
(48 preambles, NPRACH repetition every 160 ms).

NPRACH periodicit y [ms] 160

NPRACH bandwidt h (t ones) 48
RACH collision probabilit y [%] 2.5
NPRACH
NPRACH recept ion probabilit y [%] 90
capacit y RACH at t empt s (f rom t raf f ic model) [1/ s] 7.6
NPRACH occasions [1/ s] 7.6
Max # UEs (RACH) 52733

173 © Nokia 2016 Nokia Internal Use

Dimensioning
NPDCCH capacity
UE eNB
• NPDCCH is used for UL and DL scheduling during call Random Access
msg1
NPRACH
setup and further message transmission. RAR scheduling

• Call setup requires at least 3 NPDCCH messages, NPDCCH

Random Access Response
msg2
•
NPDSCH
When transmitted UL message is fragmented into TBSs, RRC: Connection Request
msg3
each NPUSCH scheduling needs separate DCI, so NPUSCH

RRCConnectionSetup scheduling
additionally #TBS NPDCCHs are needed, without HARQ NPDCCH

repetition RRCConnectionSetup-NB
NPDSCH
msg4

• In UL direction 11 UEs can be scheduled simultaneously, RRCSetupComplete scheduling

NPDCCH
providing that they are using different subcarriers, hence RRCConnectionSetupComplete-NB msg5
scheduling of another subcarrier transmission might occur NPUSCH

during transmission on the previously selected subcarrier

174 © Nokia 2016 Nokia Internal Use

Dimensioning
NPDCCH capacity
• Single UE can be scheduled during each search space. Example Rmax=4, 8 SF for search space.
FN 0 1 2 3
SFN 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
Excluded MIB SIB1 PSS SSS MIB PSS MIB SIB1 PSS SSS MIB PSS
Search space
NPDCCH occasion 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2

• Max NPDCCH repetition can be 4, 8 or 16 subframes, what corresponds search spaces of 8, 16

and 32 subframes respectively. Maximum number of scheduled UEs:
1000
𝑀𝑎𝑥 𝑈𝐸𝑁𝑃𝐷𝐶𝐶𝐻 # = 𝑅𝑚𝑎𝑥 ∙𝐺
3 + #𝑇𝐵𝑆
• Additional overhead for common channels have to be considered as well.
G 2 2 2 npdcchStartSfRa
Rmax 4 8 16 npdcchMaxNumRepRa Example: Message size 200
Search space [SF] 8 16 32
bytes, MCS3, TBS size 208 bits,
DCI # /s 125 63 31 1000/(search space [ms]) #TBS=9
# scheduled UEs /s
8 4 2 (0.75*DCI/s)/12
(w/overhead)
175 © Nokia 2016 Nokia Internal Use
Dimensioning
Total MAR message transmission time
• Average NB-IoT Call duration:
T= TCS + TTx
- TCS call setup time to establish the RRC connection
- TTx time for data transfer
• Each scheduled UL and DL transmission follows timings for NPDSCH (27ms) and NPUSCH
(45ms)
• In case message content does not fit into the single TBS (max 680 bits @MCS10) it is split into
subsequent transmissions, hence total transmission time is multiplication of the single
NPDSCH/NPUSCH process duration. It is assumed that the issue is only for NPUSCH since
NPDSCH is used here (MAR reporting) only for RACH signaling, with content fitting into single
NPDCCH NPDCCH
TBS. 32ms 32ms

680 bits 680 bits

NPUSCH NPUSCH
45ms* 45ms*

176 © Nokia 2016 Nokia Internal Use

Dimensioning UE eNB
Call setup time
Random Access
NPRACH msg1
• 27 ms is needed for the whole Random Access
NPRACH 25.6 ms
NPDSCH message, including Random Access
NPRACH
NPDCCH time, 45 ms for NPUSCH Random Access
NPRACH
8 ms
• Each NPDCCH have to be scheduled RAR scheduling
NPDCCH
in the separate search space 27 ms Random Access Response
msg2
NPDSCH
• Total 194 ms for RACH procedure RRC: Connection Request
45 ms

(without HARQ and NPRACH 8 ms

NPUSCH
msg3
RRCConnectionSetup scheduling
repetitions) NPDCCH
27 ms
RRCConnectionSetup-NB
NPDSCH msg4
8 ms RRCSetupComplete scheduling
NPDCCH
45 ms
RRCConnectionSetupComplete-NB
NPUSCH
Total: 194 ms msg5

177 © Nokia 2016 Nokia Internal Use

Dimensioning
Call setup time
NPDCCH transmission length [ms] 2
• NPRACH sequence can be repeated up to NPDCCH -> NPDSCH gap [ms] 4
nprachMaxNumPreambleCE settings (default 5), we can TBS transmission time on NPDSCH [ms] 4
assume certain probability for correct NPRACH reception NPDSCH -> NPUSCH (A/N) gap [ms] 12
NPUSCH (A/N) length [ms] 2
PNPRACH which impacts average time for NPRACH. NPUSCH (A/N) / NPUSCH -> NPDCCH gap [ms] 3
TNPRACH = (25.6 ∙ PNPRACH ) + (2∙ 25.6 ∙ (1 - PNPRACH ) ∙ HARQ percentage [%] 10
Total DL TBS transmission time [ms] 30
PNPRACH) + (3∙ 25.6 ∙ (1 - PNPRACH )2 ∙ PNPRACH) …. = 25.6 ∙ NPDCCH transmission length [ms] 2
PNPRACH ∙ 1/[1-(1- PNPRACH)2] = 25.6/PNPRACH NPDCCH -> NPUSCH gap [ms] 8
TBS transmission time on NPUSCH [ms] 32
• Assuming PNPRACH = 90%, TNPRACH = 28.4 ms NPUSCH -> NPDCCH (A/N) gap [ms] 3
• The same approach can be selected for HARQ procedure HARQ percentage [%] 10
Total UL TBS transmission time [ms] 50
for NPUSCH and NPDSCH: NPRACH transmission lenght [ms] 26
• PNPUSCH = 90%, TNPUSCH = 45 / 0.9 = 50 ms NPDCCH scheduling time [ms] 8
Number of NPDCCH per RACH procedure 3
• PNPDSCH = 90%, TNPDSCH = 27 / 0.9 = 30 ms DL message transmission lenght [ms] 30
UL message transmission lenght [ms] 50
NPRACH reception probability 90
Total Call setup time [ms] 211
• Hence modified RACH procedure time: 211 ms

178 © Nokia 2016 Nokia Internal Use

Dimensioning
Total MAR message transmission time
• 3GPP specifies MAR message size Pareto distributed, with 20-200 bytes size. For simplification only
the worst case 200 bytes will be considered.
• NPUSCH TBS size depends on the UL MCS selected, number of TBSs to be transmitted can be then
calculated, taking into account BLER
𝐵𝐿𝐸𝑅
8 ∙ 𝑀𝑒𝑠𝑠𝑎𝑔𝑒𝑈𝐿 [𝑏𝑦𝑡𝑒𝑠] ∙ (1 + )
#𝑇𝐵𝑆 = 100
𝑇𝐵𝑆𝑠𝑖𝑧𝑒 [𝑏𝑖𝑡𝑠] 4RU
ITBS
Bits
• Having number of needed TBSs one can easily calculate Ttx taking into account 0 88
transmission process duration: TTX [ms]= #TBS ∙ TNPUSCH [ms] 1 144
2 176
BHCA 0.47
Traffic #UE 52547
3 208
model #UE at t empt s/ cell/ s 6.8 4 256
UL message size (byt es) 200 5 328
UL MCS (User def ined) 2- QPSK 6 392
TBS index 1 7 472
UL
Transport Block Size f or NPUSCH [bit s] 144 8 536
UL BLER [%] 10 9 616
set t ings
Number of TBSs required t o send t he message 13 10 680
NPUSCH t ransmission durat ion [ms] 644
Average NB- IoT Call durat ion (including CS) [ms] 855
179 © Nokia 2016 Nokia Internal Use
Dimensioning
NPUSCH capacity
• Average throughput for NB-IoT UE can be estimated taking into account amount of data to be
transmitted and total time needed for the transmission (with call setup and TBS fragmentation)
8 ∙ 𝑀𝑒𝑠𝑠𝑎𝑔𝑒𝑈𝐿 [𝑏𝑦𝑡𝑒𝑠]
A𝑣𝑒𝑟𝑎𝑔𝑒_𝑈𝐸_𝑡ℎ𝑟𝑜𝑢𝑔𝑝ℎ𝑢𝑡[𝑘𝑏𝑝𝑠] =
𝑇𝐶𝑆 + #𝑇𝐵𝑆 ∙ 𝑇𝑇𝑋
• NB-IoT capacity in terms of served subscribers in BH can be estimated considering average time
of resources occupation by single UE. Providing that NPDCCH and NPRACH limits are met
NPUSCH resources should be analyzed assuming certain utilization factor (11 subcarriers
available for NPUSCH). NPRACH overhead should be considered as well.
1 11 ∙ 3600 ∙ (1 − 𝑁𝑃𝑅𝐴𝐶𝐻𝑜𝑣𝑒𝑟ℎ𝑒𝑎𝑑 ) ∙ 𝑈𝐿𝑢𝑡𝑖𝑙𝑖𝑠𝑎𝑡𝑖𝑜𝑛
𝑁𝑃𝑅𝐴𝐶𝐻𝑜𝑣𝑒𝑟ℎ𝑒𝑎𝑑 = ∙ 25.6 [ms] #𝑈𝐸_𝐵𝐻 =
𝑁𝑃𝑅𝐴𝐶𝐻𝑃𝑒𝑟𝑜𝑑𝑖𝑐𝑖𝑡𝑦 [𝑚𝑠]
𝑇𝐶𝑆 [𝑠] + (#𝑇𝐵𝑆 ∙ 𝑇𝑇𝑋 [𝑠])

Average t hroughput per NB- IoT UE (Tx) [kbit / s] 3.59

NPUSCH overhead [%] 16
UL resources ut ilisat ion f act or [%] 90
Average number of UEs/ Cell (TX) 64398

180 © Nokia 2016 Nokia Internal Use

LTE3071 NB-IoT

Energy Savings
Aspects
Table of contents

<chapter:energy_savings_aspects>

181 © Nokia 2016 Nokia Internal Use

Energy Savings Aspects
Battery life – PA efficiency impact

• 45.820 model
• Battery capacity: 5Wh
Mode Power Consumption @ 23dBm with PA efficiency Battery life (years)
40% 45% 50% PA efficiency 40% 45% 50%
Packet size, reporting MCL MCL MCL
transmitting interval 144 dB 144 dB 144 dB
589mW 533mW 489mW
current drawn 50 bytes, 2 hours 18,9 19,2 19,4
receiving
90mW 90mW 90mW 200 bytes, 2 hours 17,4 17,7 18,0
current drawn
50 bytes, 1 day 35,1 35,2 35,2
idle current 2.4mW 2.4mW 2.4mW 200 bytes, 1 day 34,6 34,7 34,8
power save
15µW 15µW 15µW
current
Source: T&I simulations

• >10 year battery life met for all scenarios

182 © Nokia 2016 Nokia Internal Use

LTE3071 NB-IoT

Performance
Aspects
Table of contents

<chapter:performance_aspects>

183 © Nokia 2016 Nokia Internal Use

Dimensioning
New counters
• There are new, NB-IoT specific counters defined for monitoring of the feature
performance
• 20 counters in total, considering the following aspects:
• RRC connection establishment
• S1-Connection Establishments
• Number of RRC connected Cat-NB1 UE
• UE movement idle state reason
• MAC PDU volume
• NB-IoT resources and time
• Measurement 8066 – LTE NB-IoT has to be started

184 © Nokia 2016 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

NB_IOT_RRC_CONN_MAX This counter represents the highest value for number of NB-IoT UEs in
(M8066C0) RRC_CONNECTED state over the measurement period.

#LTE NB-IoT Trigger event: This counter is updated after each sampling interval with the peak
number of NB-IoT UEs in RRC_CONNECTED state during the measurement
period.

Granularity: 1 sec

Use case:
Maximum number of RRC connected NB UEs
Monitoring of the number of RRC connected for NB UEs in the same way as
LTE_5242b, LTE_5842a for legacy UEs.

185 © Nokia 2016 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

NB_IOT_RRC_CONN_SUM This counter provides the sum of sampled values for measuring the number of simultaneously
(M8066C1) RRC Connected NB-IoT UEs. This counter divided by the denominator
NB_IOT_DENOM_RRC_CONN_UE provides the average number of RRC Connected NB-IoT UEs
per cell.
#LTE NB-IoT
Trigger event: This counter is updated after each sampling interval with the sample taken from the
number of NB-IoT UEs in RRC_CONNECTED state.

Granularity: 1 sec

Use case:
Average number of RRC connected NB UEs
Monitoring of the number of RRC connected for NB UEs in the same way as LTE_5242b,
LTE_5842a for legacy UEs.
Average number of NB_IOT_RRC_CONN_SUM
=
RRC connected NB UEs NB_IOT_RRC_CONN_UE_DENOM

186 © Nokia 2016 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

NB_IOT_RRC_CONN_ESTAB_A This counter provides the number of attempted RRC Connection Establishment
TT procedures. From UE's point of view, the transition from ECM-IDLE to ECM-
(M8066C2) CONNECTED is started.
Trigger event: The counter is updated on the receipt of an RRC:ConnectionRequest-NB
message.
#LTE NB-IoT
Use case:
RRC Connection Setup Success Ratio
The KPI proposed is monitoring RRC Connection Setup Success Ratio in the same way
as LTE_5218f for non NB UEs.
Impact: due to limited UE power, some setup degradations may happen more often for
SRB1bis during RRC Connection Setup procedure.

RRC Connection Setup NB_IOT_RRC_CONN_ESTAB_SUCC

= ×100%
Success Ratio related to NB_IOT_RRC_CONN_ESTAB_ATT
NB UEs

187 © Nokia 2016 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

NB_IOT_RRC_CONN_ESTAB_SU This counter provides the number of successful completions of an RRC connection
CC establishment.
(M8066C3)
Trigger event: The counter is updated on the receipt of an
RRC:ConnectionSetupComplete-NB message.
#LTE NB-IoT
Use case:
RRC Connection Setup Success Ratio
The KPI proposed is monitoring RRC Connection Setup Success Ratio in the same way
as LTE_5218f for non NB UEs.
Impact: due to limited UE power, some setup degradations may happen more often for
SRB1bis during RRC Connection Setup procedure.

RRC Connection Setup NB_IOT_RRC_CONN_ESTAB_SUCC

= ×100%
Success Ratio related to NB_IOT_RRC_CONN_ESTAB_ATT
NB UEs

188 © Nokia 2016 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

NB_IOT_S1_SIGN_CONN_ESTA This counter provides the number of attempted UE-associated logical S1-connection
B_ATT establishments from eNB to MME
(M8066C4)
Trigger event: This counter is updated on the transmission of an S1AP:INITIAL UE
MESSAGE by the eNodeB to the MME.
#LTE NB-IoT
Use case:
Logical S1 Signaling Connection Success Ratio
Above KPI is monitoring logical S1 Signaling Connection Success Ratio between eNB
and MME for NB UEs in the same way as LTE_5526a for non NB UEs. Also it is used for
pricing purposes.

Logical S1 Signaling NB_IOT_S1_SIGN_CONN_ESTAB_SUCC

= ×100%
Connection Success NB_IOT_S1_SIGN_CONN_ESTAB_ATT
Ratio

189 © Nokia 2016 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

NB_IOT_S1_SIGN_CONN_ESTA This counter provides the number of successful UE-associated logical S1-connection
B_SUCC establishments from eNB to MME.
(M8066C5)
Trigger event: The counter is updated on receipt by the eNB of the first message from
MME which succeeds INITIAL UE MESSAGE message on a UE-associated
#LTE NB-IoT
logical S1-connection.

Use case:
Logical S1 Signaling Connection Success Ratio
Above KPI is monitoring logical S1 Signaling Connection Success Ratio between eNB
and MME for NB UEs in the same way as LTE_5526a for non NB UEs. Also it is used for
pricing purposes.

Logical S1 Signaling NB_IOT_S1_SIGN_CONN_ESTAB_SUCC

= ×100%
Connection Success NB_IOT_S1_SIGN_CONN_ESTAB_ATT
Ratio

190 © Nokia 2016 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

NB_IOT_RRC_CONN_UE_DENO This counter provides the number of samples taken for counter
M NB_IOT_RRC_CONN_SUM. It is used as the denominator for the average calculation.
(M8066C6)
Trigger event: This counter is incremented by value 1 when the number of RRC
connected NB-IoT UEs - provided by a single sample - is added to counter
#LTE NB-IoT
NB_IOT_RRC_CONN_SUM.

Use case:
Average number of RRC connected NB UEs
Monitoring of the number of RRC connected for NB UEs in the same way as LTE_5242b,
LTE_5842a for legacy UEs.

Average number of NB_IOT_RRC_CONN_SUM

=
RRC connected NB UEs NB_IOT_RRC_CONN_UE_DENOM

191 © Nokia 2016 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

NB_IOT_UE_CTX_REL_UE_INA This counter provides the number of transitions to ECM_IDLE due to "user inactivity"
CTIVE
Trigger event: The counter is updated on transmission of an S1AP:UE CONTEXT RELEASE
(M8066C7) REQUEST message sent by the eNB to the MME with release cause "user inactivity".

#LTE NB-IoT Use case:

Abnormal UE movement to idle state
There is no possibility to monitor E-RAB Drop Ratio, because no data radio bearer is going to be
established, but at least with this counter operator will be able to see any abnormal UE movement
to ECM-Idle state.

E-UTRAN UE NB_IOT_UE_CTX_REL_ENB_INIT + NB_IOT_UE_CTX_REL_MME_INIT - NB_IOT_UE_CTX_REL_UE_INACTIVE - NB_IOT_UE_CTX_REL_DETACH -

Transaction to = NB_IOT_UE_CTX_REL_NORMAL
×100%
ECM-IDLE State NB_IOT_UE_CTX_REL_ENB_INIT + NB_IOT_UE_CTX_REL_MME_INIT
Drop Ratio for NB
IOT UEs

192 © Nokia 2016 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

NB_IOT_UE_CTX_REL_DETAC This counter provides the number of transitions to ECM_IDLE due to UE detach.
H
Trigger event: The counter is updated on receipt of of an S1AP:UE CONTEXT RELEASE
(M8066C9) COMMAND sent by the MME to the eNB with release cause "detach"

#LTE NB-IoT Use case:

Abnormal UE movement to idle state
There is no possibility to monitor E-RAB Drop Ratio, because no data radio bearer is going to be
established, but at least with this counter operator will be able to see any abnormal UE movement
to ECM-Idle state.

E-UTRAN UE NB_IOT_UE_CTX_REL_ENB_INIT + NB_IOT_UE_CTX_REL_MME_INIT - NB_IOT_UE_CTX_REL_UE_INACTIVE - NB_IOT_UE_CTX_REL_DETACH -

Transaction to = NB_IOT_UE_CTX_REL_NORMAL
×100%
ECM-IDLE State NB_IOT_UE_CTX_REL_ENB_INIT + NB_IOT_UE_CTX_REL_MME_INIT
Drop Ratio for NB
IOT UEs

193 © Nokia 2016 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

NB_IOT_UE_CTX_REL_NORMA This counter provides the number of transitions to ECM_IDLE due to normal call release.
L
Trigger event: The counter is updated on receipt of of an S1AP:UE CONTEXT RELEASE
(M8066C10) COMMAND sent by the MME to the eNB with release cause "Normal release"

#LTE NB-IoT Use case:

Abnormal UE movement to idle state
There is no possibility to monitor E-RAB Drop Ratio, because no data radio bearer is going to be
established, but at least with this counter operator will be able to see any abnormal UE movement
to ECM-Idle state.

E-UTRAN UE NB_IOT_UE_CTX_REL_ENB_INIT + NB_IOT_UE_CTX_REL_MME_INIT - NB_IOT_UE_CTX_REL_UE_INACTIVE - NB_IOT_UE_CTX_REL_DETACH -

Transaction to = NB_IOT_UE_CTX_REL_NORMAL
×100%
ECM-IDLE State NB_IOT_UE_CTX_REL_ENB_INIT + NB_IOT_UE_CTX_REL_MME_INIT
Drop Ratio for NB
IOT UEs

194 © Nokia 2016 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

NB_IOT_UE_CTX_REL_ENB_INI This counter provides the number of transitions to ECM_IDLE due to any kind of RAN reasons.
T
Note: this includes the more specific release causes as well.
(M8066C11)
Trigger event: The counter is updated on transmission of an S1AP: UE CONTEXT RELEASE
#LTE NB-IoT REQUEST message sent by the eNB to the MME - irrespective of the release cause.

Use case:
Abnormal UE movement to idle state
There is no possibility to monitor E-RAB Drop Ratio, because no data radio bearer is going to be
established, but at least with this counter operator will be able to see any abnormal UE movement
to ECM-Idle state.

E-UTRAN UE NB_IOT_UE_CTX_REL_ENB_INIT + NB_IOT_UE_CTX_REL_MME_INIT - NB_IOT_UE_CTX_REL_UE_INACTIVE - NB_IOT_UE_CTX_REL_DETACH -

Transaction to = NB_IOT_UE_CTX_REL_NORMAL
×100%
ECM-IDLE State NB_IOT_UE_CTX_REL_ENB_INIT + NB_IOT_UE_CTX_REL_MME_INIT
Drop Ratio for NB
IOT UEs

195 © Nokia 2016 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

NB_IOT_UE_CTX_REL_MME_IN This counter provides the number of transitions to ECM_IDLE due to any kind of EPC reasons.
IT
Note: this includes the more specific release causes as well.
(M8066C12)
Trigger event: The counter is updated on receipt of of an S1AP:UE CONTEXT RELEASE
#LTE NB-IoT COMMAND sent by the MME to the eNB - irrespective of the release cause.

Use case:
Abnormal UE movement to idle state
There is no possibility to monitor E-RAB Drop Ratio, because no data radio bearer is going to be
established, but at least with this counter operator will be able to see any abnormal UE movement
to ECM-Idle state.

E-UTRAN UE NB_IOT_UE_CTX_REL_ENB_INIT + NB_IOT_UE_CTX_REL_MME_INIT - NB_IOT_UE_CTX_REL_UE_INACTIVE - NB_IOT_UE_CTX_REL_DETACH -

Transaction to = NB_IOT_UE_CTX_REL_NORMAL
×100%
ECM-IDLE State NB_IOT_UE_CTX_REL_ENB_INIT + NB_IOT_UE_CTX_REL_MME_INIT
Drop Ratio for NB
IOT UEs

196 © Nokia 2016 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

NB_IOT_RRC_CONN_TIME_SU This counter provides the total time of NB-IoT UEs in RRC_CONNECTED state, i.e. from the
M establishment of an RRC connection to its release.
(M8066C13) Trigger event: The counter is updated on the transmission of an RRCConnectionRelease-NB
message by the time difference between this RRCConnectionRelease-NB message and the
#LTE NB-IoT corresponding RRCConnectionSetupComplete-NB message.

Use case:
Average session duration of NB UEs
The total time in the numerator of the formula considers only NB UEs which have successfully
completed RRC Connection Setup procedure.

Logical S1 Signaling NB_IOT_RRC_CONN_TIME_SUM

= ×100%
Connection Success NB_IOT_RRC_CONN_ESTAB_SUCC
Ratio

197 © Nokia 2016 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

NB_IOT_MAC_PDU_VOL_UL This counter provides the size of transport blocks scheduled on NPUSCH. The volume of MAC
(M8066C14) PDUs is considered.

Trigger event: The counter is updated when such a MAC PDU is scheduled in UL.
#LTE NB-IoT
Retransmissions are included.

Use case:
MAC PDU volume related to NB UEs in UL and DL
Utilization Ratio in DL/UL
The above two KPIs proposed are monitoring MAC PDU volume and PRB Utilization Ratio for NB
UEs in the same way as NPO KPIs for non NB UEs. Both of these KPIs can be used to monitor
MAC PDU available throughput (MAC PDU volume / measurement period / PRB Utilization Ratio).

198 © Nokia 2016 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

NB_IOT_MAC_PDU_VOL_DL This counter provides the size of transport blocks scheduled on NPDSCH. The volume of MAC
(M8066C15) PDUs is considered.

Trigger event: The counter is updated when such a MAC PDU is scheduled in DL.
#LTE NB-IoT
Retransmissions are included.

Use case:
MAC PDU volume related to NB UEs in UL and DL
Utilization Ratio in DL/UL
The above two KPIs proposed are monitoring MAC PDU volume and PRB Utilization Ratio for NB
UEs in the same way as NPO KPIs for non NB UEs. Both of these KPIs can be used to monitor
MAC PDU available throughput (MAC PDU volume / measurement period / PRB Utilization Ratio).

199 © Nokia 2016 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

NB_IOT_RESOURCES_USED_U This counter provides the number of concurrently used NB-IoT subcarriers in UL,
L which are measured during a 1 millisecond interval and accumulated over the
(M8066C16) measurement period.

#LTE NB-IoT Trigger event: This counter is updated after each 1 ms interval, in which UL
resources for NB-IoT UEs were reserved. It is incremented by the number of
subcarriers (granularity of 3.75 kHz) used in parallel by any NB-IoT UE. (15 kHz
subcarriers result in an increment of 4 per interval).
Note: In case of NB-IoT inband mode, this 1 ms interval corresponds to a
subframe of the hosting WB cell, i.e. a subframe containing one or more host
PRBs allocated to NB-IoT UEs. These PRBs are considered unusable from host
cell perspective.

200 © Nokia 2016 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

NB_IOT_TIME_RESERVED_UL This counter provides the number of 1 millisecond intervals, in which UL resources for NB-IoT UEs
(M8066C17) were configured (NPRACH) or allocated (NPUSCH) in the cell.

Trigger event: This counter is updated after each 1 ms interval, in which UL resources for NB-IoT
#LTE NB-IoT UEs were configured or allocated.
Note: In case of NB-IoT inband mode, this 1 ms interval corresponds to a subframe of the hosting
WB cell, i.e. contains one or more host PRBs allocated to NB-IoT UEs, which are considered
unusable from host cell perspective.

Use case:
Utilization Ratio in UL
PRB Utilization Ratio for NB UEs in the same way as NPO KPIs for non NB UEs. It can be used to
monitor MAC PDU available throughput (MAC PDU volume / measurement period / PRB
Utilization Ratio).

Utilization Ratio NB_IOT_TIME_RESERVED_UL

= ×100%
in UL NB_IOT_RRC_CONN_TIME_SUM

201 © Nokia 2016 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

NB_IOT_RESOURCES_USED_D This counter provides the number of concurrently used NB-IoT PRB in DL, which are measured
L during a 1 millisecond interval and accumulated over the measurement period.
(M8066C18) Trigger event: This counter is updated after each 1 ms interval, in which DL resources for NB-IoT
UEs were reserved. It is incremented by the number of PRB (granularity of 180 kHz) used in
#LTE NB-IoT parallel by any NB-IoT UE.
Note: In case of NB-IoT inband mode, this 1 ms interval corresponds to a subframe of the hosting
WB cell, i.e. a subframe containing one or more host PRBs allocated to NB-IoT UEs. These PRBs
are considered unusable from host cell perspective.

202 © Nokia 2016 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

NB_IOT_RESOURCES_AVAIL_D This counter provides the number of concurrently available NB-IoT PRBs in DL,
L which are measured during a 1 millisecond interval and accumulated over the
(M8066C19) measurement period.

#LTE NB-IoT Trigger event: This counter is updated after each 1 ms interval, in which DL
resources for NB-IoT UEs were reserved. It is incremented by the number of
available PRBs (granularity of 180 kHz) in parallel by any NB-IoT UE.

Note: In case of NB-IoT inband mode, this 1 ms interval corresponds to a

subframe of the hosting WB cell, i.e. contains one or more host PRBs allocated to
NB-IoT UEs, which are considered unusable from host cell perspective.

203 © Nokia 2016 Nokia Internal Use

Performance Aspects
LTE3071 NB-IoT

• Host cell performance monitoring after NB-IoT activation

Feature impact How to measure
Decreased DL capacity in the host cell due to PRB Average PDCP Layer Active Cell Throughput DL
resources reserved for NB-IoT inband cell LTE_5292d
When NB-IoT carrier is deployed, the number of PRBs available
for PDSCH is reduced. Consequently, DL capacity is in such a
case decreased. Effect will be visible only if the given cell has
heavy UL load
Decreased UL capacity in the host cell due to PRB Average PDCP Layer Active Cell Throughput UL
resources reserved for NB-IoT inband cell LTE_5289d
When NB-IoT carrier is deployed, the number of PRBs available
for PUSCH is reduced. Consequently, UL capacity is in such a
case decreased. Effect will be visible only if the given cell has
heavy UL load

204 © Nokia 2016 Nokia Internal Use

Performance Aspects
LTE3071 NB-IoT

• Host cell performance monitoring after NB-IoT activation

Feature impact How to measure
Decreased amount of mean/peak active UEs/RRC Average number of active users per cell (LTE_717a)
connected UEs served by the host cell. Maximum number of active users per cell (LTE_718a)
If Average/Maximum number of RRC connected users suggests Average of RRC connected users (LTE_805a)
that the AC limits will be soon met in the host cell, RRC Maximum of RRC connected users (LTE_806a)
connected limit for NB-IoT have to verified.

Decreased UL peak UE throughput As there are no available counters or KPIs to check UE peak
NB-IoT carrier consumes UL PRB resources what may impact throughput, TTI traces need to be checked.
UL peak throughput.
Additionally, when allocation of UL NB-IOT carrier yields UL
resources fragmentation, PUSCH is physically divided into
several scheduling areas. Peak UE throughput will be
decreased as one user can be scheduled in only one scheduling
area at the same time

205 © Nokia 2016 Nokia Internal Use

Performance Aspects
Example MCS0 vs MCS10 latency, 200 bytes UL
Latency message, no repetitions, default timings, no HARQ
Synchronisation and SI acquisition
Synchronization 20 [ms]
• There is QoS constraints defined for MIB acquisition 640 [ms]
transmission of MAR reports SIB1 acquisition 160 [ms]
SIB2 acquisition 160 [ms]
• 3GPP states 10s of delay for transmission Call setup
NPRACH waiting time 160 [ms]
of Exception report (e.g. smoke detector NPRACH duration 26 [ms]
or alarm NPDCCH scheduling time 8 [ms]
NPRACH -> NPDCCH (RAR scheduling) 6 [ms]
• Periodicity of such events is rare; it means DL: Random Access Response
27 [ms]
transmission
that synchronisation and SI messages UL: RRC Connectiion Request 45 [ms]
acquisition have to be counted as well DL: RRC Connection Setup 27 [ms]
DL: RRC Connection Setup Complete 45 [ms]
Total call setup time 354 [ms]
UL Data transmission
UL MCS MCS0 MCS10
NACK + DCI (UL grant) 26 [ms]
TBS size 88 680 [bits]
Number of TBSs required to send the
20 3
message
Average UL transmission time 900 135 [ms]
UL Data transmission
Total UL message transmission time 2234 1469 [ms]

206 © Nokia 2016 Nokia Internal Use

Please fill in a short survey
Your feedback is valuable to us!

KIND REQUEST TO YOU:

PLEASE FILL IN THE SURVEY NOW
SURVEY IN THE WEBEX PANEL

To get the certificate proving

participation in the training please login
to NEDC with your Nokia credentials
and download the certificate after
completing the training.

207 © Nokia 2016 Nokia Internal Use

LTE3071 NB-IoT

Compliance
Aspects
Table of contents

<chapter:compliance_aspects>

208 © Nokia 2016 Nokia Internal Use

Compliance Aspects

• NB-IoT technology has been standardized within

Release 13 3GPP framework
• For more details please check 3GPP TS 45.820
• Only Cat-NB1 UE category has a possibility
to support NB-IoT
• Legacy UEs cannot be handled by NB-IoT cell;
nevertheless they can be served by legacy host
LTE cell

Cooperation between eNB and

UE, needed for proper NB-IoT
handling, is standardized by
3GPP
209 © Nokia 2016 Nokia Internal Use
Compliance Aspects
Limitations / Simplification in Feature LTE3071 (comparing with 3GPP)
3GPP specification Supported in LTE3071

In-band, guard-band and standalone deployment In-band

Multiple PRBs can be used for NB-IoT Single PRB can be used for NB-IoT
Uplink:15 kHz single tone and 3, 6, and 12 multi Only 15kHz single tone NPUSCH is supported, 3.75kHz and
tones; 3.75 kHz single tone 15kHz multi-tone NPUSCH (3,6,12) are out of scope

Idle mode mobility by cell re-selection Cell selection

Coverage levels up to 164 dB supported Only first level coverage (144dB MCL) is supported, coverage
enhancements (154 and 164dB MCL) are not supported
Various transmission and reception schemes Only 2T2R are supported in both host LTE and inband NB-
IoT cells

210 © Nokia 2016 Nokia Internal Use

Compliance Aspects
Limitations / Simplification in Feature LTE3071 (comparing with 3GPP)
3GPP specification Supported in LTE3071

Various configurations of subframes per TBS Fixed number of subframes for NPDSCH is used
Fixed number of resource unit for NPUSCH is used

Configurable downlink and uplink transmission gap Fixed scheduling delay is used, Downlink and Uplink
Transmission Gap is not supported
Dynamic TA alignment Initial TA alignment

Dynamic downlink power control Static downlink power

Dynamic uplink power control Only uplink open loop power control (parameters
broadcasted by SIB)

211 © Nokia 2016 Nokia Internal Use

Compliance Aspects
Limitations / Simplification in Feature LTE3071 (comparing with 3GPP)
3GPP specification Supported in LTE3071

DRB and SRB can be used for data transmission SRB can be used
NPRACH format 0 (CP length = 67 us) and format 1 NPRACH format 1 (cell radius 35 km)
(CP length = 267 us)
Repetitions on NPRACH, NPDSCH, NPDCCH, No repetitions on NPDSCH and NPUSCH. Limited repetitions
NPUSCH on NPRACH (can be up to 32) and NPDCCH (hard coded to
2)
Both Mobile Originated Calls and Mobile Terminated Paging not supported
Calls (by paging) supported
All the NB SIBs supported SIBs other than SIB1-NB and SIB2-NB are not supported

Update of System Information with paging System Information updates with paging is not supported
Idle DRX Idle eDRX function is not supported

212 © Nokia 2016 Nokia Internal Use

Compliance Aspects
Limitations / Simplification in Feature LTE3071 (comparing with 3GPP)
3GPP specification Supported in LTE3071
NPDCCH with 1 CCE NPDCCH with 1 CCE is not supported

NPRACH and NPUSCH multiplexing in same TTI NPRACH and NPUSCH multiplexing in same TTI is
not supported

Valid subframes configuration Configuration of valid subframe is not supported

213 © Nokia 2016 Nokia Internal Use

LTE3071 NB-IoT

End-to-End
Operability
Table of contents

<chapter:end_to_end_operability>

214 © Nokia 2016 Nokia Internal Use

End-to-End Operability

• EPC core is suggested for optimized IoT-driven network operation

• The following mandatory features are needed for NB-IoT:
• EPC:
- Small data transmission for IP devices
- Small data transmission for non-IP devices
• SDM
- NB-IoT ACCESS SUPPORT: HSS support for NB-IoT
- SMALL DATA: Small data transmisson for non-IP devices
• Optionally for EPC:
- BATTERY SAVING: Power saving mode
- COVERAGE ENHANCEMENT: Coverage enhancement paging

215 © Nokia 2016 Nokia Internal Use