3. 3 Nokia 2022
Introduction to 3GPP IoT technologies
• During the specification of the previous 3GPP generations (2G, 3G, 4G), no particular attention was
paid to the IoT use case
• Many IoT modules are using the networks, especially in the 2G layer, but the network has not been
optimized for the IoT use case
• High battery consumption
• Costly devices
• Cannot work in extremely bad coverage
• This opened the door for several non-3GPP technologies (LoRa, Sigfox, Ingenu etc)
• 3GPP then specified these IoT technologies: EC-GSM, LTE-M, NB-IoT
4. 4 Nokia 2022
Market Trend: Fast Growing number of connected devices
Machina Research – Connected IoT devices by connectivity (world wide)
0.00
2,000,000.00
4,000,000.00
6,000,000.00
8,000,000.00
10,000,000.00
12,000,000.00
14,000,000.00
16,000,000.00
18,000,000.00
20,000,000.00
22,000,000.00
24,000,000.00
26,000,000.00
28,000,000.00
2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024
Connections - Wide area fixed
Connections - Short range
Connections - MAN
Connections - Low power wide area
Connections - 4G
Connections - 3G
Connections - 2G
• 6 major connectivity technologies
• Number of connected devices will grow 22% YoY
• Next 3 years: 5B+ connected devices added,
(72% short range, LPWA growing fast)
• 2016 - 1.4B connected devices will be added
(1B+ short range - ~50% in North America & Europe)
Connections 2016 net
adds
2017 net
adds
2018 net
adds
2G 37,854 32,536 25,542
3G 67,012 75,202 69,903
4G 31,472 57,689 93,223
LPWA 42,594 149,228 274,292
MAN 97,754 100,353 97,965
Satellite 1,108 1,253 1,388
Short Range 1,065,672 1,281,794 1,453,181
Wide Area Fixed 44,747 40,050 35,205
Total 1,388,213 1,738,106 2,050,699
7. 7 Nokia 2022
NB-IoT benefits
Spectrum Availability
continuous coverage, high mobility and reliability
The current version of NB-IoT addresses the needs for
• Low cost devices
• Massive device density
• Long battery life
• Extreme coverage
8. 8 Nokia 2022
Low cost devices
Spectrum Availability
continuous coverage, high mobility and reliability
Several design choices have been made to enable low-complexity UE implementation.
Some of these are listed below
• Low sampling rate due to lower UE bandwidth
• Significantly reduced transport block sizes for both downlink and uplink
• A UE only requires single antenna
• No need for a turbo decoder at the UE since turbo coding is only used in uplink
• No Connected mode mobility measurement is required. A UE only needs to perform
mobility measurement during the Idle mode
• Allow only half-duplex frequency-division duplexing (FDD) operation
• No parallel processing is required. All the physical layer procedures and
transmission and reception of physical channels occur in sequential manner
Estimated device costs in 2016: 4$ In 2020: 2$ - 3$
9. 9 Nokia 2022
Massive device density (I)
Spectrum Availability
continuous coverage, high mobility and reliability
• 3GPP spec 45.820 specifies target capacity for IoT solutions:
- https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?spe
cificationId=2719
- “Meter-like” traffic model to be used in capacity simulations
- Building penetration losses
- Each household in London uses 40 IoT devices => 53k devices per cell sector with
current intersite distance (1.7 km)
• 3GPP discussion document R1-157248 presents capacity simulation results
- http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_83/Docs/R1-157248.zip
- One PRB used for NB-IoT (i.e. one NB-IoT carrier per cell sector)
- Using roughly same assumptions as specified in 45.820
=> 71k devices per cell sector can be supported
10. 10 Nokia 2022
Massive device density (II)
Spectrum Availability
continuous coverage, high mobility and reliability
• The calculations in previous slide assumes no unnecessary signaling
• Original release 8 LTE specification requires Periodic Tracking Area Update
(PTAU) at least every 186 minutes
- Timer 3412 is sent to UE in Attach Accept or Tracking Area Update Accept message
• 3GPP release 12 feature ”Power Saving Mode” defines extended PTAU timer
of up to 32 x 320 hours (427 days)
- Reduce network signalling as well as device power consumption
- Needs support in HSS and in MME
- This functionality is in principle available for all devices, also smartphones
11. 11 Nokia 2022
Long battery life – Power Saving Mode
Spectrum Availability
continuous coverage, high mobility and reliability
• Many device types just need to send periodic (or aperiodic) reports, and do not need to be able to
receiving paging messages
• One approach is to power the device off (i.e. the application powers the LTE modem off) after each
transmission, but this introduces additional signaling (attach/detach, EPS bearer setup and release),
which also eats into the battery life
• As alternative, Release 12 introduces Power Saving Mode (needs support from MME, HSS, UE,
transparent to the RAN)
• After each transmission from the UE (data or Periodic TAU), it continues to listen for paging messages
during T3324 and then goes into deep sleep for the duration of T3412_extended (up to 427 days)
TAU period
PSM UE reachable
- Both timer values can be suggested by
the device and overruled by the
network
- Attach and EPS bearer contexts are
kept during the deep sleep. Mobile-
terminated data is kept by the network
- Suitable for mobile-originated
applications
12. 12 Nokia 2022
Long battery life – eDRX
Spectrum Availability
continuous coverage, high mobility and reliability
• Release 13 introduces enhanced DRX (needs support in HSS, MME, RAN,
UE)
• The DRX period is extended from 2.6 secs up to almost 3 hours. When the
eDRX cycle expires, a ”Paging Transmission Window” opens, where there
are multiple occasions to page the UE
• Most suited for mobile-terminated applications. Applicable to all UE
categories
13. 13 Nokia 2022
Battery life
• 45.820 model
• Battery capacity: 5Wh
Battery life (years)
PA efficiency 40% 45% 50%
Packet size, reporting interval
MCL
144 dB
MCL
154 dB
MCL
164 dB
MCL
144 dB
MCL
154 dB
MCL
164 dB
MCL
144 dB
MCL
154 dB
MCL
164 dB
50 bytes, 2 hours 18,9 10,1 2,3 19,2 10,5 2,4 19,4 10,9 2,6
200 bytes, 2 hours 17,4 5,1 1,1 17,7 5,5 1,2 18,0 5,8 1,3
50 bytes, 1 day 35,1 30,9 16,5 35,2 31,2 17,2 35,2 31,5 17,8
200 bytes, 1 day 34,6 24,8 10,2 34,7 25,5 10,9 34,8 26,1 11,5
Mode Power Consumption @ 23dBm with PA efficiency
40% 45% 50%
transmitting
current drawn
589mW 533mW 489mW
receiving
current drawn
90mW 90mW 90mW
idle current 2.4mW 2.4mW 2.4mW
power save
current
15µW 15µW 15µW
10 year battery life met for all scenarios with daily transaction
14. 14 Nokia 2022
Coverage enhancements
Spectrum Availability
continuous coverage, high mobility and reliability
Main features to enhance the coverage are the following
• Repetitions of transmissions on the physical layer
- Number of repetitions depends on UE coverage. Works in both uplink and downlink
• Downlink power boosting is possible due to the narrow-band nature of the signal
- The PRB containing the NB-IoT carrier can be boosted 6 dB compared to legacy LTE PRBs
• Use of ”single-tone” (15 kHz or even 3.75 kHz) improves the uplink transmission
- Instead of using full 180 kHz bandwidth (12 x 15 kHz), only a single subcarrier may be used
• Note that these features also need to compensate for the low UE output power and
single UE antenna
• More details later in the slide set!
15. 15 Nokia 2022
Aligned assumptions - In-band deployment
Release 13 eMTC and NB-IoT coverage evaluation
Internal use only
The maximum UL eMTC coverage is at
MCL=161dB, with a PHY data rate of 0.3
kbps
- The same PHY data rate can be achieved in
UL NB-IoT at MCL=161dB
The maximum UL NB-IoT coverage is at
approx. MCL=167dB, with a PHY data rate of
0.1 kbps
1
2
1 2
17. 17 Nokia 2022
• The 200 kHz bandwidth necessitates new physical channels
• The small bandwidth together with the single HARQ process puts severe limitation to
the sustained throughput
• The use of repetitions (aka TTI bundling) enables extreme coverage but comes with a
price in form of device latency / throughput / power consumption and network capacity
• Control and user plane optimization reduces the signaling load
Main differences between NB-IoT and legacy LTE
18. 18 Nokia 2022
Physical channels
Downlink:
• NPSS: Synchronization
• NSSS: Synchronization
• NPBCH: Master System Information
• NPDCCH: Downlink control information
• NPDSCH: Downlink data + some signalling
• NRS: Phase reference signal
Uplink:
• NPRACH: Random access
• NPUSCH: Uplink data + HARQ acks
• DMRS: Demodulaton reference signal
Spectrum Availability
• NB-IoT channels are primarily multiplexed in time instead of in frequency
• New channel structures are needed because legacy LTE channels occupy more than one PRB
• No PUCCH, PHICH or PCFICH defined for NB-IOT carriers. An explicit HARQ ACK/NACK
feedback is applied
19. 19 Nokia 2022
NB-IoT – Downlink
• DL uses OFDMA with 15 kHz subcarrier spacing, 12 subcarriers available in 1 NB-IoT carrier
• Reusing same OFDM numerology as LTE ensures the co-existence performance with LTE in the
downlink
• DL signals and channels – NPSS/NSSS, NRS, NPBCH, NPDCCH, NPDSCH
• New synchonization signals (NPSS/NSSS) introduced
• Provides time/frequency synchronization, cell ID and 80ms timing for NPBCH detection
• New common reference signals (NRS) introduced
• Defined for single antenna port and 2 antenna ports transmission schemes based on LTE CRS
20. 20 Nokia 2022
NPSS (Narrowband Primary Synchronization Signal)
• NPSS is transmitted every 10ms in subframe #5, uses 11 subcarriers (#0-10) and occupies the last
11 OFDM symbols of the subframe
• First 3 OFDM symbols are avoided (LTE PDCCH is located here)
• All cells share same PSS (LTE uses 3 PSSs, NSSS carries the full PCI)
• NPDSCH/NPDCCH are not mapped to subframes containing NPSS
• No NRS on subframes containing NPSS
• NPSS is punctured by LTE CRS in in-band operation mode
• Coverage enhancement is provided by allowing the UE to read multiple (identical) NPSS blocks =>
Increased synchronization time
Deployment CL=144 dB CL=154 dB CL=164 dB
Stand-alone 40 ms 40 ms 120 ms
Guard-band 40 ms 40 ms 720 ms
In-band 40 ms 40 ms 800 ms
21. 21 Nokia 2022
NSSS (Narrowband Secondary Synchronization Signal)
• NSSS indicates one of 504 PCIDs and 80ms boundary for NBPCH detection (LTE SSS gives the cell
identity group, has then to be combined with PSS to get PCID)
• NSSS is transmitted every 20ms in subframe #9, uses 12 subcarriers and occupies the last 11 OFDM
symbols of the subframe
• First 3 OFDM symbols are avoided (LTE PDCCH is located here)
• NPDSCH/NPDCCH are not mapped to subframes containing NSSS
• No NRS on subframes containing NSSS
• NSSS is punctured by LTE CRS in in-band operation mode
• Coverage enhancement is provided by allowing the UE to read multiple (identical) NSSS blocks =>
Increased synchronization time
22. 22 Nokia 2022
NRS (Narrowband Reference Signal)
• NRS is used to provide phase reference for the
demodulation of the downlink channels
• NRSs are time-and frequency multiplexed with
information bearing symbols in su bframes
carrying NPBCH, NPDCCH and NPDSCH using
8 resource elements per sub frame per antenna
port
• In the PRB pair to carry NPSS and NSSS, a NB-
IoT UE shall not expect NRS
23. 23 Nokia 2022
NPBCH
• NPBCH is transmitted every 10ms in subframe #0 and occupies the last 11 OFDM symbols of the
subframe
• NPDSCH/NPDCCH are not mapped to subframes containing NPBCH
• Coverage enhancement because NPBCH consists of 8 independently decodable blocks spanning
80 ms, MIB content remains unchanged for 640 ms (LTE uses 40 ms)
80ms
10ms
NPBCH
decodable block
80ms
10ms
NPBCH
decodable block
MIB content remains unchanged (640ms)
24. 24 Nokia 2022
NPBCH
• MIB payload is 34 bits and has a 16-bit CRC, tail biting convolutional code is used
• MIB content:
Field Size (bits)
SFN 4
HyperSFN 2
NB-SIB1 scheduling info 4
System info value tag 5
Access barring info 1
Operation mode 2
Based on operation mode
5
(1) in-band with same PCI CRS and PRB info 5
(2) in-band with different
PCI
Num of LTE CRS ports 1
Raster offset 2
Spare 2
(3) guard-band
Raster offset 2
Spare 3
(4) stand-alone Spare 5
Spare 11
CRC 16
Total Size 50
25. 25 Nokia 2022
NPDCCH
• Content:
• Scheduling information for downlink channels
• Scheduling information for uplink channels
• HARQ acknowledgement for the uplink data channel
• Paging indication
• Random Access Response scheduling
• Tail-biting convolutional code (TBCC) is used to reduce UE complexity (no need for turbo
decoding)
• May use multiple PRBs in time (LTE PDCCH uses multiple PRBs in frequency)
26. 26 Nokia 2022
NPDSCH
• NPDSCH
• Carries data from higher layers as well as paging messages, system information and the RAR message
• NPDSCH code word occupies the entire PRB and may be mapped to {1,2,3,4,5,6,8,10} subframes
• Maximum TBS is 680 bits, tail biting convolutional code, QPSK only
• Single process HARQ with adaptive and asynchronous re-transmission
• MCS/TBS definition
ITBS 11 and 12 are valid only in
stand-alone and guard-band
operation modes
ITBS
No of subframes
1 2 3 4 5 6 8 10
0 16 32 56 88 120 152 208 256
1 24 56 88 144 176 208 256 344
2 32 72 144 176 208 256 328 424
3 40 104 176 208 256 328 440 568
4 56 120 208 256 328 408 552 680
5 72 144 224 328 424 504 680
6 88 176 256 392 504 600
7 104 224 328 472 584 680
8 120 256 392 536 680
9 136 296 456 616
10 144 328 504 680
11 176 376 584
12 208 440 680
27. 27 Nokia 2022
NB-IoT – Uplink
• Transmissions
• Single tone transmissions are supported: 3.75 kHz and 15 kHz.
• Multi-tone transmissions are supported, based on SC-FDMA with 15 kHz UL subcarrier spacing.
• 3, 6, or 12 tones can be allocated
• UL channels – NPRACH, NPUSCH
• No Uplink control channel – ACK/NACK is carried by the NPUSCH, no CQI and SR support
28. 28 Nokia 2022
NPRACH
• NPRACH is a new design for PRACH since the legacy LTE Physical Random Access Channel
(PRACH) uses bandwidth of 1.08 MHz and that is more than NB-IoT bandwidth (180kHz)
• There are two preamble formats as shown in the table below (Ts = 1/(15000x2048) seconds) with two
different preamble cyclic prefix lengths
- The CP length is 66.67us (Format 0) for cell radius up to 10 km and 266.7us (Format 1) for cell radius up to 40 km
- Each symbol, with fixed symbol value 1, is modulated on a 3.75 kHz tone with symbol duration of 266.67us
29. 29 Nokia 2022
NPRACH
• The physical layer random access preamble is based on single-subcarrier frequency hopping symbol
groups
• The basic idea of the design is to spread the random access preamble in time, instead of spreading it
in frequency (as the Zadoff-Chu sequences based PRACH design in legacy LTE)
• To reduce the overhead, it is possible to combine several OFDM symbols and add one single CP
- The 5 symbols and the CP constitute a single group
• The preamble consists of 4 groups of symbols in time and occupies one tone (of 3.75 kHz) in
frequency
• The transmission hops from one group to another
• The hopping is used to facilitate accurate time-of-arrival estimation at the BS
30. 30 Nokia 2022
NPUSCH
NPUSCH has two formats
• Format 1
• Used for carrying uplink data and uses the same LTE turbo code for error correction
• The maximum transport block size of NPUSCH Format 1 is 1000 bits, which is much lower than that
in LTE
• NPUSCH supports single-tone transmission based on either 15 kHz or 3.75 kHz numerology
- To reduce peak-to-average power ratio (PAPR), single-tone transmission uses p/2-BPSK or p /4-QPSK with phase
continuity between symbols
• NPUSCH also supports multi-tone transmission based on the same legacy LTE numerology
- In this case, the UE can be allocated with 12, 6, or 3 tones with QPSK modulation
- While only the 12-tone format is supported by legacy LTE UEs, the 6-tone and 3-tone formats are introduced for
NB-IoT UEs who due to coverage limitation cannot benefit from higher UE bandwidth allocation
• NPUSCH uses the same slot structure as legacy LTE PUSCH with 7 OFDM symbols per slot and the
middle symbol as the demodulation reference symbol (DMRS)
32. 32 Nokia 2022
NPUSCH
NPUSCH has two formats
• Format 2
• Used for signaling HARQ acknowledgement for NPDSCH, and uses a repetition code for error
correction
• Both 3.75 and 15 kHz subcarrier spacing are supported in transmission of ACK and/or NACK
• Only single tone transmission with p/2-BPSK modulation
• NPUSCH Format 2 also has 7 OFDM symbols per slot, but uses the middle three symbols as DMRS
- DMRS are used for channel estimation
33. 33 Nokia 2022
Repetition principle
• Maximum number of repetitions
• NPRACH: 2048
• NPUSCH: 128
• NPDCCH: 2048
• NPDSCH: 2048
• UE determines it coverage level (RSRP) by measuring downlink
received signal power and comparing with system information
thresholds
• After reading system information on NPRACH resource
configuration, the UE can determine the NPRACH resource
configured and the numbers of repetitions needed for its estimated
coverage level.
• From the transmitted preambles, the eNB knows the coverage level
of the UE
• eNB can then decide the appropriate number of repetitions on
NPDCCH / NPUSCH / NPDSCH
• Naturally, a high number of repetitions mean slow throughput, high
latency, low device battery life and huge use of network resources!
36. 36 Nokia 2022
NB-IoT throughput – perfect conditions
• Downlink
• Instantaneous peak rate (in-band) is 170 kbps (TBS=680 bits, TTI=4ms) for in-band operation mode. This can be viewed
as cell throughput.
• Sustained peak rate is approximately 26.2 kbps without considering NPBCH/NPSS/NSSS overhead, and 19.6 kbps when
25% overhead is taken into account. This can be viewed as device throughput.
• Uplink
• Instantaneous peak rate is 250 kbps (TBS=1000 bits, TTI=4ms) using all 12 tones. This can be viewed as cell throughput.
• Sustained peak rate is approximately 62.5 kbps without considering NPRACH overhead, and 56.3 kbps when 10%
overhead is taken into account. This can be viewed as device throughput.
38. 38 Nokia 2022
Uplink Power Control – NB-IoT
The setting of the UE Transmit power for a Narrowband Physical Uplink Shared Channel (NPUSCH)
transmission is defined as follows
• The UE transmit power PNPUSCH,c(i) for NPUSCH transmission in NBIoT UL slot i for the serving cell c
is given by
- If the number of repetitions of the allocated NPUSCH RUs is greater than 2
- Otherwise
Better to send with max
power than to repeat
Do not exceed max
output power
39. 39 Nokia 2022
Uplink Power Control
• Uplink power is proportional
with calculated downlink
path loss
• Value of alpha:
- Random access response: 1
- Scheduled grant, PUSCH format
two:1
- Scheduled grant, PUSCH format
one: Provided by higher layers
• Depends on uplink
bandwidth
- 12 tones: 10.8 dB
- 6 tones: 7.8 dB
- 3 tones: 4.8 dB
- 1 tone: 0 dB
- ¼ tone: -6 dB
• Random access response (msg3):
- preambleInitialReceivedTargetPower +
ΔPREAMBLE_Msg3
• Scheduled grant:
- Provided by higher layers
40. 40 Nokia 2022
User Plane EPS Optimisations
• Many NB-LTE applications expected to have no mobility, e.g. smart meters for electricity,
gas and water
• Means that device connects to the same eNode B for every data transfer
• New procedure to handle transitions between RRC Connection and Idle mode
• RRC Connection Resume
• eNode B and UE remember connection configuration when UE moves to RRC Idle
• connection can be ‘resumed’ rather than ‘setup’ when UE moves to RRC Connected
• known as ‘User Plane EPS
Optimisation’
41. 41 Nokia 2022
U-plane solution for small data transmission
U-plane small data transmission
optimisation
• Introduces RRC Suspend and Resume
procedures to re-use suspended context
• Optional for UE and Network
• Supports IP and non-IP small data
• Optimizations introduced to support reduced
signaling (from 9 to 4 messages) for
transition towards connected mode
• Re-establishment of radio bearers without
SERVICE REQUEST and security
procedures
• P-GW can forward the small data to the AS
using P2P tunnel or encapsulate it within
UDP/IP packet for transmission towards AS
UE eNB MME SGW
UL data
DL data
1: eNB decides to Suspend the RRC Connection
2: S1-AP UE Ctxt Deactive
3: Release Access Bearer Req
4: Release Access Bearer Resp
5: S1-AP UE Ctxt Deactive Ack
6: MME enters
'ECM-IDLE'
7: RRC Connection Suspend
(Resume Id)
8: UE enters
'RRC-IDLE'
and 'ECM-IDLE'
http://msc-generator.sourceforge.net v4.5
Suspend and Resume
42. 42 Nokia 2022
Control Plane EPS Optimisations
• NB-IoT provides support for transferring application data across the SRB
• application data transferred as Non-Access Stratum (NAS) SRB towards MME
• similar to SMS
• Avoids requirement for data bearer
• UE can attach without establishing a default bearer
• known as ‘Control Plane EPS Optimisation’
43. 43 Nokia 2022
C-plane Small Data transport
MO SD via SGi (no MSISDN required)
• Initial NAS PDU encapsulates Small Data
- Release Assistance Information indicates whether
reply is expected or connection can be released
• EPS Bearer Identity (EBI) identifies
connection
• S11-U established when needed
• Signals 9 and onwards only if response is
required
• Efficiency compared to SMS
- Higher capacity beyond SMS 140 octets
- Compact signalling is designed for one-shot
message
• Option to build sequencing or ACK
- API application interface to SCS/AS
UE eNodeB MME S-GW P-GW
2. S1-AP Initial UE Message ( NAS
Data PDU with EBI)
0. UE is ECM
Idle
4. Modify Bearer Request
5. Modify Bearer Request
6. Modify Bearer Response
7. Modify Bearer Response
8.Uplink data
3. Check Integrity and
decrypts data
9. Downlink data
1.RRC Connection establishment (NAS
DATA PDU with EBI)
10. Data encryption
and Integrity
protection
11. Downlink S1-AP msg
(NAS Data PDU with EBI)
12.RRC DL Message (NAS data PDU with
EBI)
13. No further
activity detected
14. S1 release procedure (see section 5.3.5)
8.Uplink data
9. Downlink data
11. S1-AP UE context release
command
44. 44 Nokia 2022
Improve NB-IoT link budget with +20 dB coverage on LTE 144dB normal coverage
NB-IoT Coverage enhancements
• Extends by (up to) 20dB the coverage (mainly by
repetitions for NB-IoT devices Indoor).
• Dedicated configurable parameters allows to configure
the number of repetitions for each physical channels
• Repetition settings allowed for Normal or Robust or
Extreme coverage
• Fine tuning from 144dB MCL for normal coverage
to 164dB MCL for extreme coverage
• The more the repetitions are, the lower the data
rate is
• Repetition settings can either be used just for the
initial packet or throughout the RRC connection
• Uplink transmission gaps for long uplink (i.e.
NPUSCH/NPRACH) transmissions is introduced for
Extreme coverage
• 180kHz UE RF bandwidth
• Half duplex mode
• DL: OFDMA with 15 kHz
• UL: Single tone transmission
• TM2
Channel NPDCCH NPDSCH NPUSCH NPUSCH NPRACH
Deployment Mode Standalone inband Standalone inband Format 1 Format 2
Repetitions - Normal
Coverage (144dB MCL)
1 2 1 1 1 1 4
Repetitions - Robust
Coverage (154dB MCL)
2 64 1 16 4 4 16
Repetitions - Extreme
Coverage (164dB MCL)
128 512 32 256 128 128 128
Inband (144dB): 2ms (2xNPDCCH) + 4ms + 4ms (NPDSCH) + 12ms + 2ms (NPUSCH ) + 3ms = 27 ms
Inband (154dB): 64ms (64xNPDCCH) + 4ms + 64ms (16xNPDSCH) + 12ms + 8ms (4xNPUSCH ) + 3ms = 155 ms
Inband (164dB): 512ms (512xNPDCCH) + 4ms + 1024ms (256xNPDSCH) + 12ms + 256ms (128xNPUSCH ) + 3ms = 1811 ms
Inband (144dB): 2 ms (2xNPDCCH) + 8 ms + 32 ms (NPUSCH single tone) + 3 ms = 45 ms
Inband (154dB): 64 ms (64xNPDCCH) + 8 ms + 128 ms (4xNPUSCH single tone) + 3 ms = 203 ms
Inband (164dB): 512 ms (512xNPDCCH) + 8 ms + 4096 ms (128xNPUSCH single tone) + 3 ms = 4619 ms
48. 48 Nokia 2022
FL16A – LTE3033
• This feature introduces a 3GPP pre-Rel. 13 functionality for in-band NB-LTE
• The feature requires special UEs supporting the pre-Rel 13 NB-LTE functionality
• The following new physical channels are introduced for NB-LTE cells
• NB-PBCH / NB-PDSCH / NB-PSS / NB-SSS / NB-PDCCH / NB-PRACH / NB-PUSCH
• The RRC signaling is based on 3GPP R12 with Nokia proprietary extensions
• Selected limitations:
• Cell selection is supported but not cell re-selection (SIB3 not available)
• Repetitions are not supported so only basic LTE coverage (MCL = 140 dB)
• Initial MSC can be configured (MCS0 - MCS9), but no link adaptation
• No uplink power control, full UE power is used
• No DRX
• No paging, only UE-originated transmissions
49. 49 Nokia 2022
FL17A: LTE3071, LTE3509, LTE3668, LTE3669, LTE3819
• LTE3071 introduces basic 3GPP Rel. 13 functionality for NB-IoT
• FSMF baseband, basic coverage (legacy LTE, MCL = 144)
• Only Mobile-Originated transactions
• Other FL17A features bring:
• LTE3668: Coverage enhancements (MCL >= 164 dB), but only single coverage level
in a cell
• LTE3669: Paging
• LTE3509: Airscale (without baseband pooling)
• LTE3819: Compatibility with LTE-M (10 MHz, FSMF)
• Only subset of the 3GPP features are implemented in FL17A features
50. 50 Nokia 2022
3GPP specification Supported in FL17A
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 NPUSCH:15 kHz single tone and 3, 6, and 12 multi tones;
3.75 kHz single tone
15 kHz single tone. Reduces uplink throughput to 15 kbps. Note that
11 different devices can each be allocated a single tone and thus the
cell capacity can be fully utilized (one tone is reserved for Ack/Nack)
NPUSCH and NPRACH can be multiplexed in same subframe NPUSCH and NPRACH are in different subframes
Idle mode mobility by cell re-selection Cell selection
Dynamic Timing Advance alignment Initial TA alignment
Dynamic downlink power control Static downlink power
Dynamic uplink power control Initial power level derived from RACH preamble process is used for the
whole duration of the RRC connection
Dynamic link adaptation Initial MCS (decided by operator parameters) is used for the whole
duration of the RRC connection
DRB and SRB can be used for data transmission SRB can be used
NPRACH format 0 (10 km cell radius) and format 1 (35 km cell
radius)
NPRACH format 1 (cell radius 35 km)
3 coverage levels (normal, robust, extreme) with MCL up to 164 dB Single coverage level, all devices use same amount of repetitions
FL17A versus 3GPP release 13
51. 51 Nokia 2022
LTE3071
• This feature introduces a 3GPP Rel. 13 functionality for NB-IoT
• It aims to provide a possibility for low cost terminal, re-use of LTE infrastructure, improved coverage and
extremely low data volumes per device
• In-band deployment is supported
• In-band deployment means that a hosting normal LTE cell dedicates one PRB for NB-IoT use
• Only subset of the 3GPP features are implemented in LTE3071
• The main physical characteristics of the NB-IoT carrier are:
• Downlink: OFDMA, 15 KHz subcarrier spacing
• Uplink: Single tone OFDMA with 15 kHz carrier spacing (3.75 kHz and multi-tone not supported)
• Repetitions are not supported on NPDSCH / NPUSCH so only basic LTE coverage (MCL = 144 dB)
• No paging, only UE-originated transmissions. eDRX not supported
• 3GPP c-plane solution 2 is supported, so data bits are going over SRB and no DRBs are used for
NB-IoT => Core network modifications required!
• One NB-IoT carrier (PRB) per cell
53. 53 Nokia 2022
Deployment options
• In-band / standalone / guardband?
• Frequency band?
• NB-IoT in all or some of the LTE cells?
54. 54 Nokia 2022
In-band / standalone / guardband
• In-band supported in LTE3071, standalone in LTE3543, guardband in LTE3570
55. 55 Nokia 2022
In-band / standalone / guardband
In-band
• Coexistence with current LTE cell with best TCO. The drawbacks are (1) impact legacy LTE and (2)
the overheads of LTE CRS and PDCCH inside
Standalone
• Good for the spectrum blocks less than 5 MHz and good downlink coverage. Dedicated resources
leading to higher investment and less efficient TCO. Also 3-RAT (or even 4-RAT) RF sharing may
introduce deployment limitations
Guardband
• No interference and spectrum optimized. The drawback is the emissions on outer bands (even the
risk of regulations) and RF SW upgrades for digital filtering needed. Guardband is located between
effective BW and the boarder. Considering 10MHz bandwidth, guardband is located between 9MHz
and 10MHz. If center is fc, LTE goes to fc+5MHz and guard-band starts from fc+4.5MHz.
56. 56 Nokia 2022
In-band deployment – Impact on legacy LTE
In case the NB-IoT is deployed as in-band solution, there are some consequences for the
legacy LTE traffic
• Reduced BTS TX power
• Capacity reduction
• Fragmented PUSCH region
• Restrictions on legacy LTE features in host cell (see earlier slide, will disappear in later
releases)
57. 57 Nokia 2022
Impact on legacy LTE – reduced TX power
BTS TX power reduction
• Downlink power boost
can increase the NB-
IoT PRB power up to 6
dB. This power is
taken from the other
PRBs
• Only minor impact
5 MHz 10 MHz 15 MHz 20 MHz
RBG Size 2 3 4 4 PRB
PRB Total 25 50 75 100
DL Power Total 20 20 20 20 Watts
Power per PRB 0.80 0.40 0.27 0.20 Watts
NB-IoT Power Boost 6 6 6 6 dB
NB IoT PRB Tx Power 3.18 1.59 1.06 0.80 Watts
Unused PRB within RBG 1 2 3 3 PRB
Unused DL Power 0.8 0.8 0.8 0.6 Watts
Power Deficit 1.58 0.39 0.00 0.00 Watts
Legacy Cell PRB to remove Power Deficit 23 47 71 96 PRB
Legacy Cell Power Reduction per PRB 0.07 0.01 0.00 0.00 Watts
Legacy Cell Power Reduction per PRB 0.4 0.1 0.0 0.0 dB
58. 58 Nokia 2022
Impact on legacy LTE – capacity reduction
Capacity reduction
• In Nokia implementation, the PRBs in the NB-IoT PRB group cannot be used for legacy LTE traffic
• Not even if there is no NB-IoT traffic in the cell
5 MHz 10 MHz 15 MHz 20 MHz
RBG Size 2 3 4 4
PRB Total 25 50 75 100
59. 59 Nokia 2022
Impact on legacy LTE – PUSCH fragmentation
• If the uplink NB-IoT PRB is located in the middle of the PUSCH region, it may be needed to allocate
segmented PUSCH resources to the UE
- Only UEs from Release 10 onwards support a dual PUSCH resource set
• If dynamic PUCCH allocation (LTE1800: Dynamic PUCCH Allocation) is not used, the uplink NB-IoT
PRB can simply be placed in the PUSCH PRB at the border between PUCCH and PUSCH regions
• If dynamic PUCCH allocation is used, the choice is between:
- Select a PUSCH PRB far enough inside the PUSCH region that the PRB will never be used for
PUCCH. This will in most time periods fragment the PUSCH region
- Use LTE768: Flexible UL Bandwidth and blank the outermost PRBs (from both edges), and then
place the NB-IoT PRB there. Since LTE768 works from both sides of the carrier, we will be
blanking twice as many PRBs as needed for NB-IoT
61. 61 Nokia 2022
Outdoor to Indoor penetration loss
By material
• Different building materials has different
path loss properties and frequency
dependensy:
Concreate -> high frequency dependency
Glass -> low freqeuncy dependency.
• Recommendations:
• <1-2GHz bands for mMTC and deep
indoor coverage of MBB
• 2-6GHZ for MBB capacity and URLLC
• > 6 GHZ for extreme MBB (small cells)
62. 62 Nokia 2022
Should NB-IoT be implemented in all LTE sites?
• Deploying on all cells means
- Possible extra cost to upgrade to FSMF hardware
- Possibly extra license cost
- The impact to legacy LTE traffic (previous slides) happens in all LTE cells
• Deploying on a subset of sites means
- Reduced coverage and potential interference from the LTE to the non-NB sites (following slides)
- Reduced NB-IoT capacity
• Less sites with NB-IoT capability
• The reduced NB-IoT coverage will lead to a higher number of repetitions
63. 63 Nokia 2022
NB-IoT in all cells? Coverage
• Urban area case studies from NY shows ~100% coverage
for NB-IoT, even at level -1
• Rural area cases studies from Denmark shows ~100%
coverage for light” outdoor to indor penetration loss ,
reducing to 83% for level -1
91 %
61%
98 %
83 %
NB-IoT LTE-M LTE
~100 %
Rural Coverage Probability
NB-IoT provides ~100% indoor coverage in both Urban and Rural area - Rural deep indoor and basement requires densification
64. 64 Nokia 2022
• Friis underground garage is one of the deepest in Denmark (with 4 levels). Another 4-level garage is
Dalgashus in Herning
• First level’s height is 4.1m, the others are approximately 2.5m => Total depth: 11,6m
• Total area is 80x100m, with 850 parking slots
Measuring outdoor-to-indoor penetration loss for underground IoT
devices
Outdoor measurements Underground garage layout
dBm
120 m 100 m
Total 850 parking slots
100 m
80
m
65. 65 Nokia 2022
• The estimated lowest indoor path loss in the underground garage is 118 dB
- A macro cell with 10MHz@800MHz and 56 dBm EIRP (43dBm, 18 dBi, 5dB losses) was assumed.
Results: LTE-M and NB-IoT provides coverage down to level -1 to -2
118 dB (min. Indoor)
-1
-2
-3
-4
174 dB (max. Meas.)
136 dB / 10 dB / 100 %
152 dB / 6 dB / 76 %
Avg. Loss / Std / Coverage
Indoor level Measured relative signal loss
156 dB (max. LTE-M)
Link Loss
Location index
164 dB (max. NB-IoT)
165 dB / 9 dB / 16 %
<140 dB (max. LTE)
Zero coverage
68. 68 Nokia 2022
Battery life, one report per hour
110 120 130 140 150 160 170
3
4
5
6
7
8
9
MCL (dB)
Battery
Life
(Years)
Battery Life - 1 Report per Hour
NB-IoT, stand-alone, multi-tone
NB-IoT, guard-band, multi-tone
NB-IoT, in-band, multi-tone
NB-IoT, in-band, single-tone
69. 69 Nokia 2022
• With partial deployment, NB-IoT
devices cannot attach to the best
cell if that cell does not support
NB-IoT
- High pathloss since they cannot
attach to the best cell
- High interference from non-NB-IoT
cells, especially from best cell
Partial Deployment of In-band NB-IoT in Network
Serving
Cell
Best Cell
70. 70 Nokia 2022
• NB-IoT may be deployed in only a fraction of all LTE cells
• Other cells (non-NB-IoT cells) may either use the PRB used by NB-IoT for LTE or leave it
unused
- Affects interference experienced by NB-IoT devices
Partial Deployment of In-band NB-IoT in Network
LTE PDCCH NB-IoT LTE PDSCH Unused
Cell with NB-IoT deployed
Cell with NB-IoT not deployed
and PRB used for LTE
Cell with NB-IoT not deployed
and PRB unused
71. 71 Nokia 2022
• Penetration loss of 20 and 30 dB shown
• Coupling loss is less than 164 dB even with deployment in only 50% of cells, so NB-IoT deployment is feasible
- Interference will determine whether NB-IoT can be supported
Pathloss Distribution
• ISD of 1732 m
60 70 80 90 100 110 120 130 140 150 160 170
0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1
Coupling loss (dB)
CDF
Coupling loss CDFs with penetration loss = 20 dB, power-boost = 6 dB (ISD = 1732 m)
NB-IoT in 100% of cells
NB-IoT in 75% of cells
NB-IoT in 50% of cells
70 80 90 100 110 120 130 140 150 160 170 180
0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1
Coupling loss (dB)
CDF
Coupling loss CDFs with penetration loss = 30 dB, power-boost = 6 dB (ISD = 1732 m)
NB-IoT in 100% of cells
NB-IoT in 75% of cells
NB-IoT in 50% of cells
20dB
Penetration Loss
30dB
Penetration Loss
72. 72 Nokia 2022
SINR Distribution
• ISD of 1732 m – 20 dB penetration loss, synchronous network
-30 -20 -10 0 10 20 30
0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1
SINR (dB)
CDF
SINR CDFs with penetration loss = 20 dB, power-boost = 6 dB (ISD = 1732 m)
NB-IoT in 100% of cells
NB-IoT in 75% of cells, LTE in 25% cells
NB-IoT in 50% of cells, LTE in 50% cells
NB-IoT in 75% cells, 25% cells blank
NB-IoT in 50% cells, 50% cells blank
-16 -14 -12 -10 -8 -6 -4
0
0.05
0.1
0.15
0.2
0.25
SINR (dB)
CDF
SINR CDFs with penetration loss = 20 dB, power-boost = 6 dB (ISD = 1732 m)
NB-IoT in 100% of cells
NB-IoT in 75% of cells, LTE in 25% cells
NB-IoT in 50% of cells, LTE in 50% cells
NB-IoT in 75% cells, 25% cells blank
NB-IoT in 50% cells, 50% cells blank
• SINR of -13dB used as the cut-off point for NB-IoT coverage
• With PRB blanking, cell area coverage is ~100%
- True even if only 50% of the cells support NB-IoT
• Without PRB blanking and 75% of cells supporting NB-IoT, cell area coverage is ~95%
73. 73 Nokia 2022
SINR Distribution
• ISD of 1732 m – 30 dB penetration loss, synchronous network
• SINR of -13dB used as the cut-off point for NB-IoT coverage
• With PRB blanking, cell area coverage is ~98% and ~96% with 75% and 50% of cells supporting NB-IoT
• Without PRB blanking and 75% of cells supporting NB-IoT, cell area coverage is ~94%
-30 -20 -10 0 10 20 30
0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1
SINR (dB)
CDF
SINR CDFs with penetration loss = 30 dB, power-boost = 6 dB (ISD = 1732 m)
NB-IoT in 100% of cells
NB-IoT in 75% of cells, LTE in 25% cells
NB-IoT in 50% of cells, LTE in 50% cells
NB-IoT in 75% cells, 25% cells blank
NB-IoT in 50% cells, 50% cells blank
-20 -18 -16 -14 -12 -10 -8 -6
0
0.05
0.1
0.15
0.2
0.25
SINR (dB)
CDF
SINR CDFs with penetration loss = 30 dB, power-boost = 6 dB (ISD = 1732 m)
NB-IoT in 100% of cells
NB-IoT in 75% of cells, LTE in 25% cells
NB-IoT in 50% of cells, LTE in 50% cells
NB-IoT in 75% cells, 25% cells blank
NB-IoT in 50% cells, 50% cells blank
74. 74 Nokia 2022
PRB blanking
• LTE944 Uplink PUSCH masking
• Specific PUSCH PRBs can be blanked in non-NB-IoT cells
• LTE1800 Downlink interference shaping
• Continous area of PDSCH PRBs located at the edge of the carrier can be blanked
• The downlink NB-IoT PRB can for example be PRB#4 for 20 MHz deployment =>
PRBs 0, 1, 2, 3 and 4 should be blanked
• Can be done in ”preferred” or ”blanked” mode
LTE system
bandwidth
3 MHz 5 MHz 10 MHz 15 MHz 20 MHz
PRB indices
for
NPSS/NSSS
transmission
2, 12
2, 7, 17,
22
4, 9, 14, 19, 30,
35 40, 45
2, 7, 12, 17, 22,
27, 32, 42, 47,
52, 57, 62, 67, 72
4, 9, 14, 19, 24,
29, 34, 39, 44,
55, 60, 65, 70,
75, 80, 85, 90, 95
75. 75 Nokia 2022
NB-IoT in all cells?
• Enabling NB-IoT on all cells gives best possible coverage, which improves
• Locations which can be served by NB-IoT
• Device throughput, latency, battery life in hard-to-reach locations
• Network NB-IoT capacity (more cells and less need for retransmissions)
• If some LTE cells do not have NB-IoT, inter-cell interference can be mitigated
by using PRB blanking techniques
76. 76 Nokia 2022
NB-IoT and/or LTE-M (eMTC)
Factors to consider
• Better coverage with NB-IoT
• Less LTE PRBs needed for NB-IoT
• NB-IoT can be deployed outside legacy LTE PRBs
• Higher device throughput with LTE-M
• Better mobility with LTE-M
• LTE-M supports voice
• LTE-M supported in all LTE frequency bands
• Device availability and eco system
77. 77 Nokia 2022
Dimensioning
For dimensioning the RAN part of the NB-IoT networks, the following should be considered
• How many “messages” per eNB per day? The capacity license is based on this concept
• How many simultaneous RRC connections? The admission control is taking this into account when it decides if a
new connection can be established
• How high is the utilization of the radio interface?
• Dimensioning of baseband capacity (independent of actual NB-IoT traffic)
Note that first 3 areas can to some extent be influenced by parameters in addition to device traffic pattern and number of
devices
For the items 2 & 3:
• Initial IoT capacity is relatively high, at least for the “meter” use case
• Initial IoT traffic is expected to be low
• Long term predictions of IoT traffic will not be particularly reliable
• The equipment capacity might increase faster than the traffic needs
=> Consider if it is necessary to try to make detailed dimensioning, or just assume that “there will be enough capacity”
78. 78 Nokia 2022
Traffic models
• A wide variety of IoT devices will be deployed, and there will be multiple different traffic profiles
• Meter-type (water meters etc.): Small reports coming in regular intervals. How frequent? Many devices on exactly the same time?
• Trackers: Small reports, which may come very frequently, e.g. every 30 seconds
• Cameras: Either continuous video streams or pictures
• Payment devices: Needs two-way communication – maybe relatively long connection with only few packets
• Etc., etc.
• Not much study has been done on the traffic profiles of the various use cases. Until now the default traffic model is the
assumption made by 3GPP (next slide)
• Some academic studies on IoT traffic profiles available (following slide)
• 3GPP traffic profile may grossly underestimate the traffic
• Meter-type devices may send data more frequent than hourly (once per 10 minutes according to the study in next slide)
• Information from one gas metering company is that a report is 160 bytes = 1280 bits on application layer, with traces showing one
report per 10 minutes
• Another study shows report from smart meters coming every 60 seconds
• Typically the operator will provide the number of devices for each use case, but not what the traffic profile will be
79. 79 Nokia 2022
3GPP IoT traffic model (45.820 Annex E)
Mobile Autonomous Reporting (MAR) exception reports
E.g. smoke detectors, power failure notifications from smart
meters, tamper notifications etc.
Mobile Autonomous Reporting (MAR) periodic reports
E.g. smart utility (gas/water/electric) metering reports,
smart agriculture etc.
Network originated reports
E.g. trigger the device to send an uplink report as a result of
the network command e.g. request for a smart meter
reading
Software update/reconfiguration model
Software updates or patches of Cellular IoT devices. Rare,
but large payload sizes expected for complete software
updates
UL: 20 bytes
UL: 20 - 200 bytes
Pareto distributed
DL: Ack
DL: 20 bytes
UL: 20 – 200 bytes
Pareto distributed
DL: 200 - 2000 bytes
Pareto distributed
Report type Packet size
Months to years (reaction time
up to 10 second latency)
40%: Once per day
40%: Once every 2 hours
15%: Once per hour
5%: Once per 30 min
=> Mean = 0.47 times per hour
40%: Once per day
40%: Once every 2 hours
15%: Once per hour
5%: Once per 30 min
=> Mean = 0.47 times per hour
180 days
Inter-arrival time
81. 81 Nokia 2022
Possible IoT traffic profile
Dataset Regularity Sensor/Device Type Use case Frequency
Pecan Street Highly regular Smart meter Energy 1 min
Wunderground Semi regular Temperature/Humidity Weather 5 min – 1 hour
Geolife Bursty GPS Vehicular 3 sec – 3 hours
Austin Traffic Cyclical Bluetooth Urban Infrastructure 2 sec – 2 hours
Divvy Bikes Random
Trigger
Station Counter Urban Infrastructure 30 sec – 3 hours
Overall Dataset size: 325 devices with 65 from each dataset
Dataset length: 120 days with 80:40 Train-Test split
Resolution: 1 second.
Overall IoT requests: ~15 million (Testing period)
82. 82 Nokia 2022
IoT messages per day
• The capacity license for LTE IoT is based on the number of “messages” per day per eNB
• Both NB-IoT and LTE-M messages are counted
• In practice, this is counted as the number of normally released RRC connections. Below are the used counters:
• The value of these counters will be summed over 24 hours and summed for all the cells in an eNB and then compared to the capacity
license
• 1 – 1000 events => 1 capacity license
• 1001 – 2000 events => 2 capacity licenses etc.
• Note that the settings of the inactivity timers can impact on the number of RRC releases and therefore on the capacity usage
• Timers should in principle be set so that one message (e.g. data packet from the UE followed a few seconds after by acknowledgement
from the server) can be carried in one RRC connection while multiple messages (e.g. position update every 10 seconds) need multiple
RRC connections
Counter id Meaning NetAct name
M8066C7 UE movement to ECM idle state due to user inactivity NB_IOT_UE_CTX_REL_UE_INACTIVE
M8066C9 UE movement to ECM idle state due to detach NB_IOT_UE_CTX_REL_DETACH
M8066C10 UE movement to ECM idle state due to normal call release NB_IOT_UE_CTX_REL_NORMAL
M8061C45 UE movement to ECM Idle state due to user inactivity. (LTE-M) UE_REL_UE_INACTIVE_LTEM
M8061C47 UE movement to ECM idle state due to UE detach. (LTE-M) UE_REL_DETACH_LTEM
M8061C48 UE Movement to ECM idle state due to normal call release. (LTE-M) UE_REL_NORMAL_REL_LTEM
83. 83 Nokia 2022
• Dedicated NB-IoT admission control threshold based on number of users. Maximum number of NB-IoT users is configurable
up to 420
• In-band deployment on FSMF (LTE3071)
- Normal LTE and Cat-M1 (if LTE3819) RRC connected users share the same pool of users in the cell while NB-IoT users are defined
in a separate pool
- Up to 420 NB-IoT users can be defined (statically) in addition to (WB + Cat-M1) users and with a maximum of 840 (WB + Cat-M1 +
NB-IoT Inband) users in total per Host cell
• In-band deployment on AirScale (LTE3509 AirScale without Baseband pooling)
- Normal LTE and NB-IoT and Cat-M1 (if LTE3819) RRC connected UEs share the common pool
- The maximum number of NB-IoT RRC connections still limited by parameter
• The values of the inactivity timers as well as the device traffic profiles have big impact on the number of simultaneous IoT
RRC connections. Also the number of repetitions has impact
• Not yet any tool to make accurate calculations, but rough estimations can quickly be made. For example:
• Typical RRC connection duration = 10 seconds
• 420 simultaneous RRC connections during busy hour => 420 x 3600 = 1512000 connection seconds
• 151 200 IoT messages can be handled during busy hour (assuming perfect spread over time etc.)
Simultaneous RRC connections
84. 84 Nokia 2022
• The following hardware is required for NB-IoT:
• FSMF, or
• Airscale
• The activation of NB-IoT generates additional LNCEL objects at the eNode B, i.e.
both the legacy LTE cells and the NB-IoT cells are managed as separate cells
• This impacts hardware dimensioning when evaluating the requirement for Cell Sets
• For example, a Basic Cell Set can normally support up to 6 legacy LTE cells
• When NB-IoT is enabled, a Basic Cell Set remains capable of supporting 6 cells but
some of those cells may be allocated to NB-IoT, e.g. a Basic Cell Set can support 3
legacy LTE cells plus 3 NB-IoT cells
Hardware Dimensioning
85. 85 Nokia 2022
24
2
1
0.5
BHCA 0.47
#UE 52547
#UE attempts/cell/s 6.8
UL message size (bytes) 200
NPRACH periodicity [ms] 160
NPRACH bandwidth (tones) 48
RACH collision probability [%] 2.5
NPRACH reception probability [%] 90
max RACH load 1.2
RACH attempts (from traffic model) [1/s] 7.6
NPRACH occasions [1/s] 7.6
Max #UEs (RACH) 52733
Maximum number of NPDCCH repetitions (R_max ) 4
NPDCCH starting subframe period (G ) 2
NPDCCH periodicity (search space length) [ms] 8
NPDCCH occasion/s 125
#DCI per UE call 12
#UE/s (NPDCCH limit) 8
NPDCCH transmission length [ms] 2
NPDCCH -> NPDSCH gap [ms] 4
TBS transmission time on NPDSCH [ms] 4
NPDSCH -> NPUSCH (A/N) gap [ms] 12
NPUSCH (A/N) length [ms] 2
NPUSCH (A/N) / NPUSCH -> NPDCCH gap [ms] 3
HARQ percentage [%] 10
Total DL TBS transmission time [ms] 30
NPDCCH transmission length [ms] 2
NPDCCH -> NPUSCH gap [ms] 8
TBS transmission time on NPUSCH [ms] 32
NPUSCH -> NPDCCH (A/N) gap [ms] 3
HARQ percentage [%] 10
Total UL TBS transmission time [ms] 50
NPRACH transmission lenght [ms] 26
NPDCCH scheduling time [ms] 8
Number of NPDCCH per RACH procedure 3
DL message transmission lenght [ms] 30
UL message transmission lenght [ms] 50
NPRACH reception probability 90
Total Call setup time [ms] 211
UL MCS (User defined) 3-QPSK
TBS index 3
Transport Block Size for NPUSCH [bits] 208
UL BLER [%] 10
Number of TBSs required to send the message 9
NPUSCH transmission duration [ms] 446
Average NB-IoT Call duration (including CS) [ms] 657
Average throughput per NB-IoT UE (Tx) [kbit/s] 3.59
NPUSCH overhead [%] 16
UL resources utilisation factor [%] 90
Average number of UEs/Cell (TX) 64398
Interarrival (h) / Share
NPUSCH
capacity
NPDSCH
timing
NPUSCH
timing
Call
Setup
timing
UL
settings
Traffic
model
NPRACH
capacity
MAR
reports
NPDCCH
capacity
NB-IoT dimensioning tool from Network Engineering
Nokia Internal Use
NB-IoT Capacity calculator
• Capacity calculator estimates capacity of NPRACH,
NPDCCH and NPUSCH channels
• Aligned with LTE3071
- No coverage enhancements, so limited number of
repetitions
- No paging, so only MO traffic model
• Perfect radio conditions assumed, so tool gives best
case capacity rather than real capacity
86. 86 Nokia 2022
Exercise: NB-IoT dimensioning tool
Nokia Internal Use
100% of the
devices transmits
one message per
hour
By halving the time
between NPRACH
occasions (i.e.
doubling the
NPRACH capacity)
almost 50k devices
can be supported in
the cell
89. 89 Nokia 2022
NB-IoT performance monitoring
• eNB counters and KPIs
• eNB Traffica
• eNB logfiles (Emil)
• eNB Per Call Measurement Data (PCMD)
• Core network counters
90. 90 Nokia 2022
eNB counters and KPIs
• NB-IoT will logically have its own cell but will share the eNB with legacy LTE
• The legacy eNB level counters will not be incremented by NB-IoT events
• New M8066 NB-IoT measurement with 25 counters is cell level (see next slide for list of
counters)
91. 91 Nokia 2022
PI ID Network element name NetAct name Description
M8066C0 Maximum number of RRC connected NB-IoT UEs NB_IOT_RRC_CONN_MAX Highest value for number of NB-IoT UEs in RRC_CONNECTED state over the measurement
period.
M8066C1 Sum of RRC Connected NB-IoT UEs NB_IOT_RRC_CONN_SUM Sum of sampled values for measuring the number of simultaneously 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.
M8066C2 Attempted RRC Connection Establishment for NB-IoT UEs NB_IOT_RRC_CONN_ESTAB_ATT Number of attempted RRC Connection Establishment procedures.
From UE's point of view, the transition from ECM-IDLE to ECM-CONNECTED is started.
M8066C3 Successful RRC Connection Establishment for NB-IoT UEs NB_IOT_RRC_CONN_ESTAB_SUCC Number of successful completions of an RRC connection establishment.
M8066C4 Attempted UE-associated logical S1-Connection Establishments for NB-IoT
UEs
NB_IOT_S1_SIGN_CONN_ESTAB_ATT Number of attempted UE-associated logical S1-connection establishments from eNB to MME
M8066C5 Successful UE-associated logical S1-Connection Establishments for NB-
IoT UEs
NB_IOT_S1_SIGN_CONN_ESTAB_SUCC Number of successful UE-associated logical S1-connection establishments from eNB to MME.
M8066C6 Denominator for average number of RRC connected NB-IoT UEs NB_IOT_RRC_CONN_UE_DENOM Number of samples taken for counter NB_IOT_RRC_CONN_SUM. It is used as the denominator
for the average calculation.
M8066C7 UE movement to ECM idle state due to user inactivity NB_IOT_UE_CTX_REL_UE_INACTIVE Number of transitions to ECM_IDLE due to "user inactivity"
M8066C8 UE movement to ECM idle state due to insufficient radio resources NB_IOT_UE_CTX_REL_RRNA Number of transitions to ECM_IDLE due to "Radio resources not available".
M8066C9 UE movement to ECM idle state due to detach NB_IOT_UE_CTX_REL_DETACH Number of transitions to ECM_IDLE due to UE detach.
M8066C10 UE movement to ECM idle state due to normal call release NB_IOT_UE_CTX_REL_NORMAL Number of transitions to ECM_IDLE due to normal call release.
M8066C11 UE movement to ECM idle state (eNB initiated) NB_IOT_UE_CTX_REL_ENB_INIT Number of transitions to ECM_IDLE due to any kind of RAN reasons.
Note: this includes the more specific release causes as well.
M8066C12 UE movement to ECM idle state (MME initiated) NB_IOT_UE_CTX_REL_MME_INIT Number of transitions to ECM_IDLE due to any kind of EPC reasons.
Note: this includes the more specific release causes as well.
M8066C13 Accumulated time duration in RRC_CONNECTED for NB-IoT UEs NB_IOT_RRC_CONN_TIME_SUM Total time of NB-IoT UEs in RRC_CONNECTED state, i.e. from the establishment of an RRC
connection to its release.
M8066C14 MAC PDU volume in UL for NB-IoT UEs NB_IOT_MAC_PDU_VOL_UL Size of transport blocks scheduled on NPUSCH. The volume of MAC PDUs is considered.
M8066C15 MAC PDU volume in DL for NB-IoT UEs NB_IOT_MAC_PDU_VOL_DL Size of transport blocks scheduled on NPDSCH. The volume of MAC PDUs is considered.
M8066C16 Number of used NB-IoT UL resources NB_IOT_RESOURCES_USED_UL Number of concurrently used NB-IoT subcarriers in UL, which are measured during a 1 millisecond
interval and accumulated over the measurement period.
M8066C17 Total number of one millisecond intervals reserved for NB-IoT UEs in UL NB_IOT_TIME_RESERVED_UL Number of 1 millisecond intervals, in which UL resources for NB-IoT UEs were configured
(NPRACH) or allocated (NPUSCH) in the cell.
M8066C18 Used NB-IoT DL resources NB_IOT_RESOURCES_USED_DL Number of concurrently used NB-IoT PRB in DL, which are measured during a 1 millisecond
interval and accumulated over the measurement period.
M8066C19 Available NB-IoT DL resources NB_IOT_RESOURCES_AVAIL_DL Number of concurrently available NB-IoT PRBs in DL, which are measured during a 1 millisecond
interval and accumulated over the measurement period.
M8066C20 RRC paging requests (records) for NB-IoT UEs NB_IOT_RRC_PAGE_REQ Number of RRC paging requests (records) for NB-IoT UEs.
M8066C21 Discarded RRC paging requests (records) for NB-IoT UEs due to paging
record list overflow
NB_IOT_RRC_PAGE_REQ_DISC_OVL Number of dropped RRC paging records for NB-IoT UEs due to paging record list overflow.
M8066C22 Discarded RRC paging requests (records) for NB-IoT UEs due to paging
occasion overlap
NB_IOT_RRC_PAGE_REQ_DISC_OVLAP Number of dropped RRC paging records for NB-IoT UEs due to overlapping paging occasions (POs).
M8066C23 Attempted RRC Connection Establishments with cause "mt-Access" for NB-
IoT UEs
NB_IOT_RRC_ESTAB_MT_ATT Number of attempted RRC Connection Establishment requests with cause "mt-Access" for NB-IoT UEs.
M8066C24 Successful RRC Connection Establishments with cause "mt-Access" for NB-
IoT UEs
NB_IOT_RRC_ESTAB_MT_SUCC Number of successful RRC Connection Establishments with cause "mt-Access" for NB-IoT Ues.
92. 92 Nokia 2022
NB-IoT counters for number and duration of RRC connections
• Fairly straightforward counters
• No obvious problems
• Can be used both for capacity KPIs (number of simultaneous RRC connections) as well
as for behavior KPIs (RRC connection duration)
PI ID Network element name NetAct name
M8066C0 Maximum number of RRC connected NB-IoT UEs NB_IOT_RRC_CONN_MAX
M8066C1 Sum of RRC Connected NB-IoT UEs NB_IOT_RRC_CONN_SUM
M8066C6 Denominator for average number of RRC connected NB-IoT UEs NB_IOT_RRC_CONN_UE_DENOM
M8066C13 Accumulated time duration in RRC_CONNECTED for NB-IoT UEs NB_IOT_RRC_CONN_TIME_SUM
93. 93 Nokia 2022
NB-IoT counters for connection establishments and releases
• Fairly straightforward counters
• No obvious problems
• Can be used to calculate setup success ratio and drop ratio
• No detailed failure cause counters
PI ID Network element name NetAct name
M8066C2 Attempted RRC Connection Establishment for NB-IoT UEs NB_IOT_RRC_CONN_ESTAB_ATT
M8066C3 Successful RRC Connection Establishment for NB-IoT UEs NB_IOT_RRC_CONN_ESTAB_SUCC
M8066C4 Attempted UE-associated logical S1-Connection Establishments for NB-IoT UEs NB_IOT_S1_SIGN_CONN_ESTAB_ATT
M8066C5 Successful UE-associated logical S1-Connection Establishments for NB-IoT UEs NB_IOT_S1_SIGN_CONN_ESTAB_SUCC
M8066C23 Attempted RRC Connection Establishments with cause "mt-Access" for NB-IoT UEs NB_IOT_RRC_ESTAB_MT_ATT
M8066C24 Successful RRC Connection Establishments with cause "mt-Access" for NB-IoT UEs NB_IOT_RRC_ESTAB_MT_SUCC
M8066C7 UE movement to ECM idle state due to user inactivity NB_IOT_UE_CTX_REL_UE_INACTIVE
M8066C9 UE movement to ECM idle state due to detach NB_IOT_UE_CTX_REL_DETACH
M8066C10 UE movement to ECM idle state due to normal call release NB_IOT_UE_CTX_REL_NORMAL
M8066C11 UE movement to ECM idle state (eNB initiated) NB_IOT_UE_CTX_REL_ENB_INIT
M8066C12 UE movement to ECM idle state (MME initiated) NB_IOT_UE_CTX_REL_MME_INIT
M8066C20 RRC paging requests (records) for NB-IoT UEs NB_IOT_RRC_PAGE_REQ
M8066C21 Discarded RRC paging requests (records) for NB-IoT UEs due to paging record list overflow NB_IOT_RRC_PAGE_REQ_DISC_OVL
M8066C22 Discarded RRC paging requests (records) for NB-IoT UEs due to paging occasion overlap NB_IOT_RRC_PAGE_REQ_DISC_OVLAP
94. 94 Nokia 2022
NB-IoT counters for resource utilization
PI ID Network element name NetAct name
M8066C14 MAC PDU volume in UL for NB-IoT UEs NB_IOT_MAC_PDU_VOL_UL
M8066C15 MAC PDU volume in DL for NB-IoT UEs NB_IOT_MAC_PDU_VOL_DL
M8066C16 Number of used NB-IoT UL resources NB_IOT_RESOURCES_USED_UL
M8066C17 Total number of one millisecond intervals reserved for NB-IoT UEs in UL NB_IOT_TIME_RESERVED_UL
M8066C18 Used NB-IoT DL resources NB_IOT_RESOURCES_USED_DL
M8066C19 Available NB-IoT DL resources NB_IOT_RESOURCES_AVAIL_DL
95. 95 Nokia 2022
NB-IoT KPI formulas
• Reporting Suite System Program
Report (RSLTE000 / RSLTE001)
contains a few NB-IoT KPIs
• RSLTE077 report contains most
of the NB-IoT KPIs
KPI Formula name
LTE_1748a Maximum number of NB-IoT RRC Connected UEs
LTE_1749a MAC PDU volume in UL for NB-IoT UEs
LTE_1750a MAC PDU volume in DL for NB-IoT UEs
LTE_1751a Downlink MAC PDU throughput for NB-IoT UEs
LTE_1752a Uplink MAC PDU throughput for NB-IoT UEs
LTE_1753a Downlink bytes per RRC connection
LTE_1754a Uplink bytes per RRC connection
LTE_1755a Abnormal transactions to ECM Idle for NB-IoT UEs
LTE_1756a Retainability for NB IoT-UEs
LTE_1764a Number of cells with NB IoT enabled
LTE_1766a RRC connection establishment attempts for NB-IoT UEs
LTE_1777a Ratio between simultaneous NB-IoT and total RRC connections
LTE_1778a Ratio between NB-IoT and total LTE PDCP SDU volume
LTE_1779a Ratio between NB-IoT and total LTE RRC connection setup attempts
LTE_1780a Successfully terminated NB-IoT RRC connections
LTE_6170a E-UTRAN RRC Connection Setup Success Ratio for NB IoT UEs
LTE_6171a E-UTRAN Average RRC Connected NB IoT UEs
LTE_6172a E-UTRAN UE-associated logical S1-Connection Establishment Success Ratio for NB IoT UEs
LTE_6173a E-UTRAN UE Transaction to ECM-IDLE State Drop Ratio for NB IOT UEs
LTE_6174a E-UTRAN Total Ratio of Successful NB IoT Sessions
LTE_6175a E-UTRAN UL Resource Utilization Ratio for NB IoT UEs
LTE_6176a E-UTRAN DL Resource Utilization Ratio for NB IoT UEs
LTE_6177b E-UTRAN Average Session Duration for NB IoT UEs
LTE_6185a E-UTRAN RRC Connection Setup Attempts for NB IoT UEs
LTE_6280a E-UTRAN RRC Connection Setup Success Ratio with cause mt-Access for NB IoT UEs
LTE_6281a E-UTRAN RRC Connection Setup Attempts with cause mt-Access for NB IoT UEs
LTE_6282a E-UTRAN Percentage of Completed RRC connection requests with mt-Access cause for NB-IoT UEs
LTE_6283a E-UTRAN RRC Paging Discard Ratio for NB-IoT UEs due to paging buffer overflow
96. 96 Nokia 2022
IoT Cloud
IoT
Platforms
NPO for Internet of Things
Overview of NPO IoT services
Control
Measurements
Things
IoT Nw design, data build,
pre-launch optimization
for acceptance, capacity
planning
Forecasting and
Analytics based on
Artificial Intelligence and
data correlation
Backhaul capacity
assessment, capacity
planning & integration
in the existing MBB NW
Maps, PoI, IoT sensor
data, IoT Nw
performances, API
IoT Backhaul
Network
15/02/2023
LoRa, Sigfox, eNB-IoT,ECGSM
LTE-M, 5G
Network Planning &
Assessment
eNB-IoT,ECGSM LTE-M,
5G Predictive Serivices
IoT aaS
IoT NW Optimization and Assurance
LoRa, Sigfox, eNB-
IoT,ECGSM LTE-M, 5G
Network Planning &
Assessment
97. 97 Nokia 2022
IoT NW Planning & Assessment
Key business drivers
Design
Building the new IoT NW,
depending on the technology
selected: NB-IoT. Cat-M, ECGSM,
LoRa needs specific expertise and
tools. Radio NW Design, Model
Tuning, Radio Access &
Backhauling, Data build
preparation, among the activities
done.
Interference Detection
Depending on the selected
technogy and spectrum
avaialbilty, there are major
concerns about internal and
external interference detection
and how the IoT system can cope
with that
M2M traffic detection
One of the tasks of the IoT
network should be as well to
carry the existing M2M traffic on
legacy MBB NWs.. The detection
of the M2M traffic patterns, the
device type can help to migrate
such traffic in the new IoT
network thus unloading the
commercial network
Nw Acceptance
Checking the IoT network
performances before the
commercial avaialbility and
tuning paramters or doing RF
shaping will help operators to
successfuly launch the new IoT
network assuring the desired
performances
98. 98 Nokia 2022
IoT NW Planning & Assessment
Operator challenges
IoT experience
IoT brings new technologies where
new designs and traffic rules needs to
be applied for a successful
deployment. As all new technologies
lack of expertise can lead to wrong
designs and increase of CAPEX & OPEX
Interference Reduction
Minimization of the interference is one
of the most difficult tasks in network
optimization. In technologies as NB-
IoT LoRA, Cat-M, a network with
minimized interference brings strong
advantages for the operator and end-
user.
IoT use cases
IoT at the end is based on selected
use cases however it’s not clear
which are the key use cases and
how they can bring help as well on
the traditional legacy NW
Optimization
Tools & Expertise
Operators face several issues in
finding the right tools for
optimizing multiple layers and track
the end-user quality in multiple
technologies. Deep multivendor
expertise level is required to have a
the “full picture view” and take
decisions
99. 99 Nokia 2022
Use cases and services
IoT NW Planning & Assessment
Calculate the IoT Radio
coverage and traffic profile
to meet the expected
requirements-. Coverage
predictions, model tuning.
Identify the traffic to be
carried by each base station
or gateway and investigate
the possible transport and
back-hauling options
Identification of M2M traffic
patterns on the legacy MBB
network as well as the
device type for a rapid
migration on the new IoT
NW.
Minimization of interference
with identification of irregular
coverage and polluters. Tilt,
Power, Azimuth simulations,
PCI collisions, confusions for
the NB-IoT and LTE-M
standalone but as well for
LoRa.
IoT Radio Design IoT Radio Access IoT Assessment Interference
Minimization
Parameter planning and
selection of the features to
be used on field. Selection of
Nokia reccomended values
coming from IoT world wide
experience. PCI/RSI plan for
Stand Alone NB-IoT or Cat.M
Define the traffic profile for
each use case and as well
forecast the impact of
increased traffic over time
Identify if packets are
retransmitted or lost and
the cause of it it’s a major
help when tuning the
network for commercial
launch of for IoT
optimization
Data build IoT capacity planning IoT deep packet
analysis
Performance check before
commercial launch, parameter
tuning or physical
optimization are among the
activities of the IoT
Acceptance. Multilayer
performance check
IoT Acceptance
100. 10
0
Nokia 2022
Use cases and services
Pollution Detection
Customizable
Pollution
Settings
MUSA Polluter
Ranking
After MUSA
optimization with
Antenna tilting
improvement in
the coverage
pollution
MUSA
Pollution Map
101. 10
1
Nokia 2022
Use cases and services
Interference minimization: Pollution Detection
Variables:
• Number of cells in each pixel (excluding BS)
• Delta level in dB of each cell from BS
• Classification & equivalence of server classes
(from SINR)
• Distance in meters from the BS
• Minimum RSRP level of the BS.
102. 10
2
Nokia 2022
Use cases and services
Multilayer Coverage Simulation
Evaluation of the tilt/azimuth change on co-sites with antenna shared over multiple
technologies
Import of multiple technology measurement files in parallel e.g.
LTE FDD1800Mhz, NB-IoT 1800Mhz, UMTS 900Mhz, Cat-M 900Mhz
103. 10
3
Nokia 2022
Use cases and services
Load Simulation Scenarios
Static and Dynamic load simulation
“Static” Load Simulations
• With uniform load distribution
• With specific load at cell level.
“Dynamic” Load Simulations
• Network and traffic growth forecast
• Traffic distribution from counters
• Traffic distribution estimated from
measurement.
Time
Load
104. 10
4
Nokia 2022
Use cases and services
PCI/RSI Analyzer
Check of PCI
Collisions,
Confusions,
Violations and
correction of
the problem
PCI, RSI and
grpsAssPUSCH
planning
105. 10
5
Nokia 2022
Why Nokia
IoT Radio Design
Load Simulation
Irregular Coverage
Recognition
Pollution & Interference
Radio Access & Bachaul
planning
Multilayer Coverage
Simulation
PCI & RSI planning &
assessment
Value Argumentation
106. 10
6
Nokia 2022
Why Nokia
Why Nokia
Value Argumentation
Value Argumentation
Guiding the operator to the best
and most cost effective solutions
including macro, in-building, Wi-Fi,
small cell and backhaul.
Detection of M2M traffic patterns
through advanced machine
learning techniques
Nokia proprietary tools &
patented methods
Consultative approach
Advanced machine
learning Tools & methods
Network, device, apps & subscriber
experience
Proven multivendor capabilities
Holistic approach
Multivendor
capabilities
107. 10
7
Nokia 2022
Feature ID Feature title Category Release (FDD)
LTE3071 NB-IoT Inband RRM Telecom FDD-LTE 17A
LTE3509 NB-IoT: Inband on Airscale without Baseband Pooling RRM Telecom FDD-LTE 17A
LTE3543 NB-IoT Standalone QoS, services and end user experience FDD-LTE 18
LTE3570 NB-IoT Guardband 15/20MHz QoS, services and end user experience FDD-LTE 18SP
LTE3571 NB-IoT: Co-existence with UL CoMP and eICIC QoS, services and end user experience FDD-LTE 18A
LTE3667 NB-IoT with Baseband Pooling QoS, services and end user experience FDD-LTE 18A
LTE3668 NB-IoT: Coverage enhancements RRM Telecom FDD-LTE 17A
LTE3669 NB-IoT: Paging support RRM Telecom FDD-LTE 17A
LTE3721 NB-IoT Multitone in uplink QoS, services and end user experience FDD-LTE 18SP
LTE3722
NB-IoT: Additional configurations (4Rx, 4Tx or 1Tx eNB
support)
QoS, services and end user experience FDD-LTE 18
LTE3819 IoT: Cat-M and NB-IoT on same frequency carrier RRM Telecom FDD-LTE 17A
LTE4036 NB-IoT: Non-anchor carrier QoS, services and end user experience FDD-LTE 19A
LTE4040 Cat-M1 and NB-IoT on same LTE cell – Phase II QoS, services and end user experience FDD-LTE 18
LTE4063 NB-IoT: Online parameters and SIB modification QoS, services and end user experience FDD-LTE 18SP
LTE4117 NB-IoT: Inter-frequency Idle mode Mobility Mobility FDD-LTE 18A
LTE4147 NB-IoT Performance Monitoring Performance Monitoring FDD-LTE 19A
LTE4162 3 SA NB-IoT carriers with special duplexing gap QoS, services and end user experience FDD-LTE 18A
LTE4194 NB-IoT Inband with CPRI-A radios QoS, services and end user experience FDD-LTE 18
LTE4212 Cat-M1 & NB-IoT: TM1 Support for 1Tx eNB Configurations Coverage, capacity and peak rates FDD-LTE 18SP
LTE4409
NB-IoT: Enhancements and Improved Feature interactions
(OTDOA, FDD-TDD CA)
QoS, services and end user experience FDD-LTE 18
LTE4414 NB-IoT: Intra-frequency Idle mode Mobility Mobility FDD-LTE 18
LTE4415 NB-IoT Inband with LTE Baseband Pooling QoS, services and end user experience FDD-LTE 18
LTE4448
Cat-M1 & NB-IoT: Coexistence with CRG (Cell Resource
Group)
QoS, services and end user experience FDD-LTE 18A
LTE4468 NB-IoT Peak Rate 105 kbps QoS, services and end user experience FDD-LTE 19A
LTE4475 NB-IoT: Multiple Coverage Levels QoS, services and end user experience FDD-LTE 18
LTE4499 NB-IoT Guardband QoS, services and end user experience FDD-LTE 18SP
LTE4547 NB-IoT: 100km cell range Coverage, capacity and peak rates FDD-LTE 19
LTE4677 IoT Edge solution integration BTS Site Solution FDD-LTE 18A
LTE4739 Cat-M/NB-IoTUE context and bearer preemption QoS, services and end user experience FDD-LTE 18A
LTE4852 Guardband NB-IoT for FDD mMIMO Coverage, capacity and peak rates FDD-LTE 19B
LTE4858 Standalone NB-IoT in B85 QoS, services and end user experience FDD-LTE 19
LTE4867 NB-IoT: Enhanced cell id based location service QoS, services and end user experience FDD-LTE 19B
LTE5205 NB-IoT Guardband/Inband with Baseband Pooling Coverage, capacity and peak rates FDD-LTE 19
LTE5243 NB-IoT: 3 Standalone Carriers Coverage, capacity and peak rates FDD-LTE 19
LTE5268 NB-IoT: Coexistence with UL CoMP QoS, services and end user experience FDD-LTE 19
108. 10
8
Nokia 2022
Feature ID Feature title Feature category Release
CB007788
NB-IoT: Asymmetrical DL/UL PRB blanking for Guardband and
NR Coexistence
RRM and Telecom SRAN 21B
LTE3869 NB-IoT Cell Trace Operability SRAN 20A
LTE4196 NB-IoT: Inband support in 3MHz RRM and Telecom SRAN 20C
LTE4598 NB-IoT: Idle Mode Load Balancing by Redirection RRM and Telecom SRAN 20B
LTE4898 NB-IoT: Multiple non-anchor carriers RRM and Telecom SRAN 20C
LTE4908 NB-IoT peak rate 159 kbps RRM and Telecom SRAN 20A
LTE5289 NB-IoT: Access Barring RRM and Telecom SRAN 20A
LTE5306
NB-IoT: Release Assistance Indication & Inactivity Timer per
Coverage Level
RRM and Telecom SRAN 20A
LTE5329 Flexible UL CoMP co-exist with NB-IOT RRM and Telecom SRAN 20C
LTE5393 NB-IoT Guardband/Inband with Baseband Pooling (20MHz, 4Rx) RRM and Telecom SRAN 20A
LTE5418 NB-IoT: 100km Cell Range (Guardband/Inband) Site Solution SRAN 20B
LTE5635 NB-IoT Guardband Coexistence with NR RRM and Telecom SRAN 20C
SR002819 AFAA support for NB-IOT Site Solution SRAN 20C
