IoT RF Design Guideline LoRa V01 Internal

IoT RF DESIGN GUIDELINES: LoRa
Internal document – Do not circulate outside Nokia
Document issue: 1.0

Document status: DRAFT01
Date:
Author Tibor Asztalos

Owner Tibor Asztalos
Organization GS/NPO_BL/TE/Advanced RF Design Team
Approver Pierre SABATIER
Document ID LTE/IRC/APP/xxx
Document location TypeDocLocationHere
Change History
Version Status Date Author Owner Reviewed by Reviewed Approver Approval Description of changes
date date
0.1 DRAFT 20-12-2016 T. ASZTALOS T. ASZTALOS GS/NPO_BL/TE/ARFD05-12-2013 P.SABATIER 20-12-2016 First draft
1.0 DRAFT 14-12-16 T. ASZTALOS T. ASZTALOS GS/NPO_BL/TE/ARFD20-12-2016 P. SABATIER 20-12-2016 First release
20-12-2016– LTE/IRC/APP/ <Nokia - Proprietary - Use pursuant to Company © Nokia 2016

instruction >
1 / 59
Contents
1 Introduction .......................................................................................................................... 4
1.1 Object ..................................................................................................................................... 4
1.2 Scope of this document ...................................................................................................... 4
1.3 Audience for this document ............................................................................................... 4
1.4 IoT RF Design purpose ......................................................................................................... 5
1.5 RNP Tools ............................................................................................................................... 5
2 IoT Networks ......................................................................................................................... 7
2.1 LoRaWAN ................................................................................................................................ 7
2.1.1 LoRa EU .................................................................................................................................. 9
2.1.2 LoRa US .................................................................................................................................. 9
2.2 IoT Capacity considerations................................................................................................ 11
2.2.1 LoRa capacity ........................................................................................................................ 11
3 IoT Link Budgets ................................................................................................................... 13
3.1 Factors impacting coverage range .................................................................................... 13
3.2 LoRa Link Budget .................................................................................................................. 14
3.2.1 Receiver sensitivity............................................................................................................... 14
3.2.2 Example Link Budget ............................................................................................................ 16
4 IoT:LoRa Coexistence with other technologies................................................................ 19
4.1 Coexistence of LoRa operating in EU 863-870MHz band .............................................. 19
4.2 Coexistence of LoRa operating in US 902-928MHz band.............................................. 20
5 IoT RF Design considerations ............................................................................................. 21
5.1 SITE ACQUISITION................................................................................................................. 21
5.1.1 Site survey ............................................................................................................................. 21
5.1.2 Antenna.................................................................................................................................. 22

instruction >
2 / 59
5.2 Reference CW measurements for model tuning ............................................................. 24
5.2.1 Calibration measurements.................................................................................................. 24
6 9955 LPWA: LoRa.................................................................................................................. 27
6.1 Defining Network Configuration......................................................................................... 28
6.1.1 Creating a LPWA planning project ...................................................................................... 28
6.1.2 Setting up project general parameters............................................................................. 29
6.1.3 Importing Geo & Antenna Databases ................................................................................ 33
6.1.4 Setting up Project environment ......................................................................................... 35
6.1.5 Propagation Model Selection .............................................................................................. 36
6.2 Coverage analyses................................................................................................................ 38
6.2.1 Signal Level Coverage analysis ........................................................................................... 39
6.2.2 DL/UL CINR analysis ............................................................................................................. 42
6.2.3 DL/UL Service coverage ...................................................................................................... 43
6.2.4 DL/UL Throughput coverage .............................................................................................. 44
6.3 Subscriber list based analysis ............................................................................................. 45
7 9955 workarounds ............................................................................................................... 47
7.1 LoRa workaround with rnp 9955 V7.3.1 ........................................................................... 47
7.1.1 LoRa customized settings ................................................................................................... 47
7.1.2 LoRa predictions ................................................................................................................... 50
7.1.3 Subscriber list based analysis ............................................................................................. 55
8 REFERENCES .......................................................................................................................... 57
9 Abbreviations ........................................................................................................................ 59

instruction >
3 / 59
1 Introduction
1.1 Object
This document describes the process of dimensioning and

designing the radio system of an IoT network.
Low Power Wide Area (LPWA) refers to technologies that

enable wireless internet of things (IoT) networks.
In this guideline design recommendations for LPWA

networks of LoRa (Long Range) are formulated.
1.2 Scope of this document
This document contains:
 IoT:LoRa RF design considerations
 IoT:LoRa Traffic profile
 IoT:LoRa Link Budget example
 IoT Design solutions for coverage
 All the parameters settings for 9955 radio planning tools
1.3 Audience for this document
The audience for this document is the people involved in:
 IoT Radio Network design and Planning
 IoT Radio Network engineering
 IoT Radio Network optimization

instruction >
4 / 59
1.4 IoT RF Design purpose
The network topology of IoT systems is comprised of simple nodes (End Devices) that
collect and transmit a limited amount of data to a central controller or Gateway which provides
connectivity to the Internet and cloud services. Hence, an IoT Network is composed of one (or
several) Gateway(s) and a possibly high number of End Devices (clients), such as wireless sensors,
smart meters, home automation systems and wearables. Gateways (GWs) are usually connected
via a wired Local Area Network (LAN) to the Internet in order to allow communications between
the wireless End Device clients and the network’s application server(s).
Nodes and gateways must be designed to minimize power consumption, provide reliable
and robust network connections and extend wireless connectivity range as far as possible.
Achieving good range depends on the antenna gain, receiver sensitivity and transmitter
power. The antenna gain is usually limited by cost and device form factor. Receiver sensitivity
sets the lower limit on power that can still be received and understood and receiver sensitivity
determines how well it can distinguish the desired transmission from other signals and noise in
the area. Thus, having a receiver with both good sensitivity and selectivity makes it possible to
achieve longer range. A primary factor affecting radio sensitivity is the data rate. The lower the
data rate, the narrower the receiver bandwidth is and the greater the sensitivity of the radio.
On the transmitter side, range is determined by the output power level. A 6 dB increase
in link budget will double the range in an outdoor, line-of-sight environment. However,
regulatory standards limit the allowed output power, and increasing the transmitter power also
increases the current consumption, which can have a negative effect on battery life.
1.5 RNP Tools
Although there may exist on the market dedicated to IoT technology simulation/planning tools
available in this document it is assumed that radio planner is jointly handling several different
technologies while using NOKIA selected/validated RNP tools. Therefore, 9955 V7.3.1 (Atoll
platform) is the assumed as the used RNP tool for IoT RF design. Support of LPWA design
features is available from release 9955 V7.3.1 b9754 onwards. Nevertheless, the methodology
can be adapted and used with another RNP tool, tool version, provided that LPWA is supported.
Issuing radio network coverage predictions by using a dedicated RNP tool, allows for the
consideration of several key factors that cannot otherwise be taken into account, these being:
 Modeling of the real environment (area heights, morphostructure, topography);

 Use of complex and more accurate propagation model (with model calibration)

instruction >
5 / 59
 The distribution of the offered traffic – particularly important when the distribution is
non uniform;
 Site Modeling – location, antenna location, height and azimuth, cable length, etc. Relative
site locations will influence the captured traffic and the inter-cell interference.
 Realistic interference evaluation – other tools, like Link Budget (LKB), focusing on worst
case scenarios, cannot catch this essential and very often limiting aspect for a network’s
performance
 Change/calibrate/tune design based on field measurements – dedicated RNP tool allows
improvement of design accuracy by comparing initial predictions with those of
measurements taken after the network implementation or even tuning accordingly the
used propagation model.
Accounting for the above facts during a network design process, usage of a dedicated RNP
tool greatly enhances the accuracy of the estimation of the designed network performance.

instruction >
6 / 59
2 IoT Networks
LPWA IoT solutions can be divided into proprietary (i.e. non-3GPP) LPWA technologies and (3GPP)
cellular IoT; SigFox and LoRa are both proprietary technologies deployed in unlicensed bands.
For all these technologies, deployment in spectrum lower than 1GHz spectrum helps achieve
maximum coverage, but higher bands in the spectrum may still be used.
The 3GPP Release recently finalized three, new cellular LTE-based IoT standards—Cat-M1, NB-
IoT, and EC-GSM—that offer a cellular alternative to proprietary unlicensed Low-Power Wide-
Area Network (LPWA) technologies.
Figure 1: 3GPP (NB-LTE, LTE-M , EC-GSM) and non-3GPPsolutions (LoRa, Sigfox) IoT
2.1 LoRaWAN
LoRa is a wireless technology that has been developed to enable low data rate communications
to be made over long distances by sensors and actuators for M2M and Internet of Things, IoT
applications.
LoRaWAN or Long Range Wide Area Network, is based on Semtech’s LoRaTM PHY chip, specifically
designed and optimised to provide low-power WANs with features to support low-cost mobile
secure two-way communication in IoT, see [1] & [2]. LoRaWANs use of sub-GHz ISM bands also
means the network can penetrate the core of large structures and subsurface deployments

instruction >
7 / 59
within a range of 2km. LoRaWAN is quickly gaining traction with IoT businesses due to its low cost
with a number of initiatives and hardware companies adopting it.
Main features include:
 building penetration and urban range 2-5km, 15km suburban, 45km rural range
 adaptive low data rate, 0.3 - 50kbps
 ultra low power usage, estimated 10 years end-node operation with two AAA batteries
 supports private & public networks
 integrated security & embedded identification and authentication
 Multiple channels used (typically 8).
 Channel frequencies and bandwidth (normally 500 kHz, 250 kHz or 125 kHz) defined for
each network
 Transmit power maximum defined by regulator (in EU 100 mW)
 Typically regulator defines how often a node is allowed to transmit (duty cycle, in EU 1%)
 Half-duplex communication but sensors typically reachable only after sending
LoRaWAN operates in the sub-gigahertz frequency bands and it’s specification varies from
region to region because of regulatory requirement.
LoRa networks operate in unlicensed ISM (Industrial, Scientific and Medical) frequencies:
 Europe 863 MHz – 870 MHz (and 433 MHz – 434 MHz)
 USA 902 MHz – 928 MHz
 China 779 MHz – 787 MHz
Unlicensed ISM bands in sub GHz frequencies:
 Penetrates well to buildings
 Offers long communication range
LoRa modulation is a proprietary spread spectrum modulation scheme that is a derivative of

Chirp Spread Spectrum (CSS) modulation which trades data rate for sensitivity within a fixed
channel bandwidth. Spreading Factor (SF) varies between 6-12.
3 device classes, difference is when device can receive data:
• Class A: Only immediately after send

instruction >
8 / 59
• Class B: At fixed time intervals. Nodes listen sync beacons and then listen at agreed times
• Class C: All the time, except when sending or receiving
2.1.1 LoRa EU
LoRaWAN defines ten channels for Europe. Out of which 8 channels are multi data rate from 293
bps to 5.5 kbps.
• One channel can operate at higher data rate with a speed of 11 kbps.
• And, one FSK channel at 50 kbps
• The maximum power allowed is +14dBm.
Figure 2: LoRa EU Modulation Settings
2.1.2 LoRa US
LoRaWAN for North America operates in the 915 MHz ISM Band divided into the following
channel plans:

instruction >
9 / 59
• Upstream – 64 channels numbered 0 to 63 utilizing LoRa 125 kHz BW varying from DR0
to DR3 starting at 902.3 MHz and incrementing linearly by 200 kHz to 914.9MHz
• Upstream – 8 channels numbered 64 to 71 utilizing LoRa 500 kHz BW at DR4 starting at

903.0 MHz and incrementing linearly by 1.6 MHz to 914.2 MHz
• Downstream – 8 channels numbered 0 to 7 utilizing LoRa 500 kHz BW at DR10 to DR13)

starting at 923.3 MHz and incrementing linearly by 600 kHz to 927.5 MHz
• Default radiated transmit output power: 20 dBm
• The maximum output power is +30 dBm.
LoRaWAN does not make use of GFSK modulation in the US902-928 ISM band.
Devices, when transmitting with 125 kHz BW may use a maximum of +30 dBm. The transmission
should never last more than 400 ms. Devices, when transmitting with 500 kHz BW may use a
maximum of +26 dBm
Figure 3: LoRa US Modulation Settings

instruction >
10 / 59
2.2 IoT Capacity considerations
The capacity requirements target in 3GPP TR 45.820, [9], has been set to 40 devices per
household, based on assumptions for London, which correspond to 39413 devices per typical
omni cell with cell site radius of 500m.
Based on 3GPP TR 45.820, IoT Capacity evaluation is performed by running system level
simulations using traffic models defined in TR 45.820 Annex E and the system level simulation
assumptions in Annex D, see [9].
2.2.1 LoRa capacity
The capacity metric is defined as spectral efficiency in number of reports/125 kHz/hour.
The major IoT assumptions are the 900MHz carrier and LoRA 125kHz working bandwidth, and
cell site radius of 500m per site assuming the omni antennas. The IoT Users dropped uniformly
in entire cell with DL/UL 1Tx-1Rx scheme only. For the further details, please see [9].
As Specified in TR 45.820 as the simulation target, it is calculated by assuming 40 devices per

urban household. The IoT Traffic models for Cellular IoT: Application payload size is Pareto
distributed with parameters: alpha = 2.5, minimum (beta) = 20 bytes, cutoff = 200 bytes. The
reports are only very rarely large. 50%, 75%, and 90% of sizes are less than 27, 35, and 50
bytes respectively. The mean size is 32 bytes (256bits).
Case Household Density Cell site sector Number of devices Number of devices within
per sq km radius, R (m) within a household a cell site sector
Urban 1517 500 m 40 39413
Table 1: the target IoT device density per cell
IoT Mobile Autonomous Reporting (MAR) periodic reports assumption: Periodic uplink
reporting is expected to be common for cellular IoT applications such as smart utility
(gas/water/electric) metering reports, smart agriculture, smart environment etc.
Characteristic
Application payload size distribution Pareto distribution with shape parameter alpha = 2.5
and minimum application payload size = 20 bytes
with a cut off of 200 bytes i.e. payloads higher than
200 bytes are assumed to be 200 bytes.
Periodic inter-arrival time Split of inter-arrival time periodicity for MAR periodic
is: 1 day (40%), 2 hours (40%), 1 hour (15%), and 30
minutes (5%)
Table 2: the target IoT traffic model Assumptions

instruction >
11 / 59
Based on the assumptions in the above MAR periodic reports, the average IoT activity is very
low at 0.00013 packets report per second per device, i.e. the average 7 report per cell per
second, and 588k reports per day.
In the following table, the general IoT capacity estimation may be obtained with the related
inputs: 125kHz BW is used with the total BW 200kHz. The IoT report size at 32byte per packet
and the activity is at 0.00013 packet report per second per device. The max DL/UL data volume
are about 2 million bytes per hour per cell based on the SX1301 specification, [2]. The LoRA
report transmission is assumed with 10% frame erasure rate. With the available network
feedbacks and proposal, about 4.8 reports/second per cell are assumed for Poisson distributed
report rates per cell in TR 45.820, which follows variable LoRA DL/UL data rate of 0.13 ~ 16kbps.
LoRa
Available BW in kHz 200 kHz
Devices density in cell 39413 devices
LoRA report size 32 bytes
Common
LoRA activity 0.00013 pkt/s/device
Inputs
BW utilization (total 125kHz) 63%
max DL/UL data volume
2000000 bytes/hour/cell
(bytes/hour/cell)
Report frame erasure rate 10%
Input Poisson distributed report
4.76 report/s/cell
rates per cell
average arrival rate of reports 5.11 pkt/s/cell
network packet rate R
4.29 pkt/s/cell
(pkt/s/cell)
network packet rate R
Output (pkt/hour/cell) 15429 pkts/hour/cell
DL/UL data volume
(bytes/hour/cell) 493714 bytes/hour/cell
max Capacity report rate in #
33061 devices/cell
devices/cell
Table 3: LoRA Capacity estimation per cell site
Based on the above inputs as one example, the LoRA shows that the max capacity report rate is
about 33k devices per cell, which may generate 15.4k packet per hour per cell, and delivered the
max DL/UL data volume at 494kbytes per hours per cell.

instruction >
12 / 59
3 IoT Link Budgets
In case of a coverage limited IoT nework design the very first network planning step consists in
determining appropriate values for the inter-GW (intersite) distance in the different
morphoclasses. These intersite distance values are required by the planner to place sites in the
radio network planning tool for the first predictions. In case of the GW locations are known (i.e.
existing site locations are used for implementing the IoT network) this step may be skipped.
A link budget (LKB) requires information about the desired level of coverage, the hardware to be
used and the propagation characteristics of the area to calculate the maximum path loss that
can be tolerated between the GW and end device nodes/equipment. The calculated maximum
allowed path loss (MAPL) is used to predict the cell radius and derive the coverage area of the
cell.
3.1 Factors impacting coverage range
Different propagation effects and equipment characteristics will impact the performance of a
wireless IoT network, hence the size and shape of the coverage area. We can group these
parameters in three categories:
At GW side:
 transmitted power
 receive sensitivity (for nodes to GW transmissions)
 antenna used (plus cable/connector losses if external antennas are used)
 antenna height and
 antenna orientation unless Omni
Environment:
 Physical environment: physical obstacles to the radio wave propagation

 Physical environment: distance between the transmitter and the receiver
 Physical environment: propagation channel model/channel characteristics
 Radio environment: interferences from other GWs/clients on your own network or from
neighboring network
 Radio environment: radio interferences from other sources

instruction >
13 / 59
Client side:
 transmitted power (when the client device is transmitting)

 sensitivity (for GW to client device transmissions)
 antenna used
 orientation of the client's antenna relative to the GW's antenna&position
3.2 LoRa Link Budget
3.2.1 Receiver sensitivity
The transmitted signal eventually reaches the receiver. There, results depend on the Receive
Sensitivity of that device - i.e., the minimum power required to handle arriving frames at a given
link speed. Receive Sensitivity is a given characteristic of an IoT device and will vary across
products.
The following table shows the sensitivity threshold (minimum) requirement for a typical LoRa EU
network GW device.
Table 4: Receiver sensitivity for a typical LoRa wireless GW device for EU modulations
Equivalent
Sensitivity
Mode bit rate
(dBm)
(kb/s)
FSK 1.2 1.2 -122
LoRa SF = 12 0.293 -137
LoRa SF = 11 0.537 -134.5
LoRa SF = 10 0.976 -132
LoRa SF = 9 1.757 -129
LoRa SF = 8 3.125 -126
LoRa SF = 7 5.468 -123
LoRa SF = 6 9.375 -118
Note that in case of LoRa equipment, receive sensitivity is generally stated either as a function
of spreading factors (SF) or as a function of network speed, as different spreading factor and
encoding rate is requested to fulfil these different data rate requirements (see Table 4).
Performances vary per supported standard and product family.

instruction >
14 / 59
The following tables shows the estimated target SNR rates for an IoT device assuming a LoRa
GW Noise Figure (NF) of 6 dB and an end device NF of 8 dB.
Table 5: Lora GW minimum SNR requirements
Spreading GW Sensitivity Estimated NF in

Mode BW symbol rate Rs
factor (SF) (dBm) SNR in dB dB
LoRa SF = 12 SF=12 125 kHz 30.5 sym/s -137.0 dBm -20.0 dB 6.0 dB
Table 6: LoRa End Device minimum SNR requirements
Device
Spreading Estimated NF in
Mode BW symbol rate Rs Sensitivity
factor (SF) SNR in dB dB
(dBm)
LoRa SF = 6 SF=6 125 kHz 1953.1 sym/s -113.0 dBm 2.0 dB 8.0 dB
Table 5 & Table 6 listed minimum SNR (SNRmin) requirements relate to presented sensitivity
figures via receiver sensitivity definition of:

instruction >
15 / 59
As the client device moves away (if mobile) from the GW, the signal level/quality decreases and
the wireless GW will automatically switch to a lower but more robust link speed (higher SF).
3.2.2 Example Link Budget
MAPL is computed according the to the equation:

Equation 1: Calculation of Maximum Allowable Pathloss (MAPL) in DL/UL
MAPLi,k dB  EIRPi dBm  Reference _ sensitivit y k dBm

  Losses dB   Mar gins dB
  Gains dB
where
MAPLi,k Maximum allowable pathloss of receiver i
using MCS k
EIRPi Equivalent isotropic radiated power
(i.e. transmit power + antenna gain) of
the transmitter
 Losses Sum of all losses in dB (e.g. cable and
connector loss, body loss, penetration
loss)
 Margins Sum of all margins in dB (e.g. shadowing

margin, Rayleigh Fading Margin)
 Gains Sum of all gains in dB (e.g. antenna gain)
The following LKB example is with indicating some typical values for the above parameters.
Assume the following GW and end node (device) parameters of:

instruction >
16 / 59
Table 7: Typical LoRa LKB input parameters
Parameter Unit
GW max transmit power dBm 25
GW antenna gain dBi 11.2

GW cable/connector losses dB 0.5
Device max transmit power dBm 14

Device Cable/connector losses dB 0
Device antenna gain dBi 0
Device Type - Class A
Where LoRa device is assumed as a typical device in EU market.
An example LoRa UL outdoor LKB for Urban is presented as below. Snapshot was issued by using
the LoRa Link Budget Tool referenced as [4] in section 8 of this ocument.
UL BUDGET - Urban - ISM Europe - 125KHz
LoRa SF = LoRa SF = LoRa SF =

Urban 11 12 11 10
LoRa SF = 9 LoRa SF = 8 LoRa SF = 7 LoRa SF = 6
Service Bit Rate bps 293 bps 537 bps 977 bps 1758 bps 3125 bps 5469 bps 9375 bps
Symbol Rate bps 31 bps 61 bps 122 bps 244 bps 488 bps 977 bps 1953 bps
Chip Rate Kcps 125 Kcps 125 Kcps 125 Kcps 125 Kcps 125 Kcps 125 Kcps 125 Kcps
Coding Rate 4/5 4/5 4/5 4/5 4/5 4/5 4/5
Channel Model PedA 3km/h PedA 3km/h PedA 3km/h PedA 3km/h PedA 3km/h PedA 3km/h PedA 3km/h
GW required SINR dB -17.5 dB -15.0 dB -12.5 dB -9.5 dB -6.5 dB -3.5 dB 1.5 dB
GW Noise Figure dB 6.0 dB 6.0 dB 6.0 dB 6.0 dB 6.0 dB 6.0 dB 6.0 dB
GW Sensitivity dBm -135 dBm -132 dBm -130 dBm -127 dBm -124 dBm -121 dBm -116 dBm
GW Antenna Gain dBi 11.2 dBi 11.2 dBi 11.2 dBi 11.2 dBi 11.2 dBi 11.2 dBi 11.2 dBi
Cable & Connector Losses dB 0.5 dB 0.5 dB 0.5 dB 0.5 dB 0.5 dB 0.5 dB 0.5 dB
Cell Area Coverage Probability % 95% 95% 95% 95% 95% 95% 95%
Outdoor Shadowing Standard Deviation dB 8.0 dB 8.0 dB 8.0 dB 8.0 dB 8.0 dB 8.0 dB 8.0 dB
Outdoor Shadowing Margin dB 8.6 dB 8.6 dB 8.6 dB 8.6 dB 8.6 dB 8.6 dB 8.6 dB
Signal Selection Diversity (SSD) Gain dB 4.0 dB 4.0 dB 4.0 dB 4.0 dB 4.0 dB 4.0 dB 4.0 dB
Penetration Margin dB 36 dB 36 dB 36 dB 36 dB 36 dB 36 dB 36 dB
Interference Margin dB 3 dB 3 dB 3 dB 3 dB 3 dB 3 dB 3 dB
Device Type Class A Class A Class A Class A Class A Class A Class A

Device Max Transmit Power dBm 14 dBm 14 dBm 14 dBm 14 dBm 14 dBm 14 dBm 14 dBm
Device Antenna Gain dBi 0.0 dBi 0.0 dBi 0.0 dBi 0.0 dBi 0.0 dBi 0.0 dBi 0.0 dBi
MAPL dB 115.6 dB 113.1 dB 110.6 dB 107.6 dB 104.6 dB 101.6 dB 96.6 dB

Cell Range Km 0.6 Km 0.5 Km 0.4 Km 0.3 Km 0.3 Km 0.2 Km 0.2 Km
Site covered area Km2 0.7 Km2 0.5 Km2 0.3 Km2 0.2 Km2 0.2 Km2 0.1 Km2 0.1 Km2
Nb. of sites Sites 154 212 292 429 632 930 1770
Figure 4: LoRa Urban UL LKB

instruction >
17 / 59
Note that a deep basement penetration margin of 36 dB was assumed for the above LKB
example.
MAPL is computed for different LoRa modes, different SF values which define the different
offered LoRa service characteristics (bit rates in bps).
In DL one can derive:

DL BUDGET - Urban - ISM Europe - 125KHz
LoRa SF = LoRa SF = LoRa SF =

Urban 12 11 10
LoRa SF = 9 LoRa SF = 8 LoRa SF = 7 LoRa SF = 6
Service Bit Rate bps 293 bps 537 bps 977 bps 1758 bps 3125 bps 5469 bps 9375 bps
Symbol Rate bps 31 bps 61 bps 122 bps 244 bps 488 bps 977 bps 1953 bps
Chip Rate Kcps 125 Kcps 125 Kcps 125 Kcps 125 Kcps 125 Kcps 125 Kcps 125 Kcps
Coding Rate 4/5 4/5 4/5 4/5 4/5 4/5 4/5
Channel Model PedA 3km/h PedA 3km/h PedA 3km/h PedA 3km/h PedA 3km/h PedA 3km/h PedA 3km/h
Device required SINR dB -14.5 dB -12.0 dB -9.5 dB -6.5 dB -3.5 dB -0.5 dB 4.5 dB
Device Noise Figure dB 8.0 dB 8.0 dB 8.0 dB 8.0 dB 8.0 dB 8.0 dB 8.0 dB
Device Sensitivity dBm -130 dBm -127 dBm -125 dBm -122 dBm -119 dBm -116 dBm -111 dBm
GW Antenna Gain dBi 11.2 dBi 11.2 dBi 11.2 dBi 11.2 dBi 11.2 dBi 11.2 dBi 11.2 dBi
Cable & Connector Losses dB 0.5 dB 0.5 dB 0.5 dB 0.5 dB 0.5 dB 0.5 dB 0.5 dB
Cell Area Coverage Probability % 95% 95% 95% 95% 95% 95% 95%
Outdoor Shadowing Standard Deviation dB 8.0 dB 8.0 dB 8.0 dB 8.0 dB 8.0 dB 8.0 dB 8.0 dB
Outdoor Shadowing Margin dB 8.6 dB 8.6 dB 8.6 dB 8.6 dB 8.6 dB 8.6 dB 8.6 dB
Signal Selection Diversity (SSD) Gain dB 4.0 dB 4.0 dB 4.0 dB 4.0 dB 4.0 dB 4.0 dB 4.0 dB
Penetration Margin dB 36 dB 36 dB 36 dB 36 dB 36 dB 36 dB 36 dB
Interference Margin dB 3 dB 3 dB 3 dB 3 dB 3 dB 3 dB 3 dB
Device Type Class A Class A Class A Class A Class A Class A Class A

GW Max Transmit Power dBm 25 dBm 25 dBm 25 dBm 25 dBm 25 dBm 25 dBm 25 dBm
Device Antenna Gain dBi 0.0 dBi 0.0 dBi 0.0 dBi 0.0 dBi 0.0 dBi 0.0 dBi 0.0 dBi
MAPL dB 121.6 dB 119.1 dB 116.6 dB 113.6 dB 110.6 dB 107.6 dB 102.6 dB

Cell Range Km 0.9 Km 0.7 Km 0.6 Km 0.5 Km 0.4 Km 0.3 Km 0.3 Km
Site covered area Km2 1.4 Km2 1.0 Km2 0.7 Km2 0.5 Km2 0.3 Km2 0.2 Km2 0.1 Km2
Nb. of sites Sites 71 98 135 199 292 429 817
RNP Design Level -115.9 dBm -113.4 dBm -110.9 dBm -107.9 dBm -104.9 dBm -101.9 dBm -96.9 dBm
Figure 5: LoRa Urban DL LKB
The MAPL derived via the LKB reflects the path-loss to be spent over the air! Based on the
minimum amongst UL MAPL and DL MAPL the RNP design threshold of ‘RNP design level’ is
derived. This is an important design parameter as it is indicating the expected level of received
signal (RSSI) in DL at where cell edge is predicted based on minimum MAPL. The areas on the
resulting coverage plot where the calculated value of this minimum RSSI design threshold is
reached are assumed to provide coverage. ‘RSSI design level’ is computed for 95% of reliability
(accounted in ‘Shadow margin’).

instruction >
18 / 59
4 IoT:LoRa Coexistence with other technologies
With the introduction of LPWAN (Low-Power Wide-Area Network) for different long range – low
bit rate applications, there is a concern of interference caused by these networks on the existing
networks.
The aim of document [17] in part 8 is to present these potential interference cases and provide
antenna isolation recommendation for interference-free coexistence between these LPWAN
networks and existing technologies.
Depending on the region or country, LoRa could be used in different frequency bands, and
therefore different coexistence scenarios may exists, depending on the possible spectrum
configurations. Since LoRa transmitters could be coexisting in the same geographical area with
existing technologies, there is a concern that potential interference from legacy BS transmitters
could interfere with LoRa BS receiver and vice-versa.
Example scenarios:
in EU 433MHz and China 470-510MHz frequency bands, coexistence issues with TETRA or with
LTE450MHz (E-UTRA Band 31) may appear.
For EU 863-870MHz ISM band, the most critical coexistence scenario is the potential
interference with E-UTRA Band 20 (LTE800MHz).
For US 902-928MHz ISM band, the coexistence with the cellular systems operating in E-UTRA
Band 8.
In this section further, the focus is on the EU863-870MHz band and US902-928MHz band. Note
that coexistence of LoRa in other specified bands is very similar with these two main scenarios,
therefore they are not studied in particular.
4.1 Coexistence of LoRa operating in EU 863-870MHz band
One of the most common cases of LoRa coexistence is between LoRa operating in EU 863-
870MHz and LTE 800MHz (E-UTRA Band 20).
The LoRa network channels can be freely attributed by the network operator, and they are used
for both UL and DL, there are no dedicated zones for UL and DL, like in US 902-928MHz band.
The LTE E-UTRA Band 20 is defined as 832-862MHz for UL and 791-821MHz for DL.

instruction >
19 / 59
Therefore, at a first look, the critical scenario is LoRa DL interfering the LTE UL, meaning that
the LoRa gateways may impact the LTE800 Base Station reception when collocated on the same
tower.
The reverse scenario, LTE UL interfering the LoRa DL, meaning that the LTE User Equipment
would impact the LoRa end-device, is considered less critical, due to lower powers involved and
localized impact only – that particular LoRa end-device is impacted, not all devices in the area.
In document [17] example isolation calculations are indicated and way of implementing those by
means of antenna separation is recommended.
4.2 Coexistence of LoRa operating in US 902-928MHz band
One other common case of LoRa coexistence is between LoRa operating in US 902-928MHz and
2G/3G/4G operating in 900MHz band (e.g. E-UTRA Band 8).
In US 902-928MHz band, LoRa network channels are attributed in separated parts of the band,
dedicated for uplink or downlink transmission: the LoRa uplink can be between approximately
902-915MHz and the LoRa downlink can be between approximately 923-928MHz.
On the other hand, the LTE E-UTRA Band 8 is defined as 880-915MHz for UL and 925-960MHz
for DL. However, due to allocation for LoRa, the remaining spectrum available for the other
mobile systems is 883-902MHz for uplink and 928-947MHz for downlink.
At a first look, it can be noticed that this scenario is not critical, as the spectrum allocation
ensures uplink-to-uplink and downlink-to-downlink adjacencies, which is common and does not
put a risk of coexistence, especially if the same site locations are being used by both systems.
It can be seen that downlink-to-uplink scenarios, which are the worst cases, are not critical, due
to frequency separation. In fact, both systems protect their own uplink bands and therefore the
uplink of the other system also, consequently.

instruction >
20 / 59
5 IoT RF Design considerations
5.1 SITE ACQUISITION
Like for the other technologies deployed, LPWA site acquisition must be taken into account at
the beginning of the radio planning phase, as the sites analyzed must correspond to those which
are going to be implemented on the field.
Usually the customer should provide candidate sites positions and the existing positions which
could be re-used in order to avoid new sites implementation.
The customer request is generally to re-use a maximum of existing sites and to not have any
new sites implementation. This is particularly feasible in case of IoT due the IoT coverage gain
over these other technologies.
5.1.1 Site survey
Even when sites positions are given by the customer, they must be analysed and validated by
NOKIA.
Radio site search and validation is an important step in radio network planning and
implementation.
It allows identifying:
If a site is eligible for required coverage, by detecting if there are masks (near
obstruction like higher building or trees) which have not been seen with radio planning
tool
Detection of pattern distortion risk due to the environment and the structure near the
antenna
Analysis of the antenna height compared to the nearest environment. For continuous
coverage type of deployment, sites must not be too high compared to its environment,
as it can increase inter-cell interference.
All the type of equipment available on the rooftop, and their frequency band. Based on
that it can be deduced what type of antenna is required, and where to position it in order
to avoid interferences created by co-sitting.
Spurious signals in the UL band.

instruction >
21 / 59
All the site survey rules for outdoor sites is available in the doc linked as [16] in part 8
During a site selection any interference should be detected. The interference detection process
is detailed in the document referenced as [15] in part 8 of this document.
5.1.2 Antenna
Average antenna height rules:

To avoid interferences antennas should not be placed on roof top or towers whose heights are
much higher than the mean environment one where they are placed.
Antenna should be placed close to rooftop in the direction where it is pointing.
Below some default height values which can provide a view of antenna height per environment
type.
These values are only indications as the antenna heights placed on roof top for dense urban and
urban environments and mainly in suburban depend essentially on building heights.
Dense urban: 30m<= antenna height <50m
Urban: 20m <= antenna height <40m
Suburban: 15m <= antenna height < 25m
Rural: 25m<= antenna height <45m (for rural case the height above 30m is not to avoid
rooftop obstacle but to maximize coverage)
Minimum antenna height on rooftop:

There is a minimum height to respect when an antenna is installed on a rooftop. In any case the
minimum value between middle of the antenna and rooftop should not be lower than 5m.
For antenna placed in middle of large rooftop and to avoid rooftop effect the following rule
must be respected:
Min antenna height = Tangent (0.5*antenna vertical beamwidth + max tilt value supported+ 5°) *
distance between antenna & rooftop edge (the distance concerned is the one in the antenna
azimuth direction)
Antenna selection:
Antenna & OEM basics are detailed in the presentation referenced as [13] in part 8 of this
document.
In the document [14] the process to validate antenna link is detailed.

instruction >
22 / 59
The basic rules for antenna selection are summarized in the following items:
 Frequency band
o VSWR stability in the frequency band
o Stability of the gain in the frequency band
 Gain
 Polarization:
o The two main possibilities are dual- polarized antennas in +/-45° polarization or
vertical polarized antennas.
o Selection depends on the environment as the vertical polarization has a

coverage advantage essentially on rural environment, but it is constraining in
term of place as two antennas are required to support Rx diversity; that’s why
dual-polarized antennas are used most of the time whatever the environment is
o Antenna decoupling is with dual polarized antenna as 30dB are ensured inside a
same radome
o Two linear antennas must be separated by a minimum of 0.5m which induces

another mast or on the roof top, which is very constraining
 Directivity antenna type: omni-directional or sector antenna.
o For outdoor macro-cells network, the antennas essentially used are sectors, as
they allow a better efficiency to manage interferences, with azimuth and tilt.
o Omni-directional antennas do not have variable tilt
 Radiating pattern must be adapted with the area to cover
o Vertical beam width: vertical angular sector in which the attenuation is lower
than 3dB.
- From 6° to 9° for common sector antennas used in 900MHz band to

2.6GHz band
- 15° for common sector antennas used in 700MHz band
o Horizontal beam width: horizontal angular sector in which the attenuation is

lower than 3dB. The most common H beam width sector antenna used is 65°; but 90° are
also used on the field
o Front to back ratio: essentially for sector antennas, must be at least equal to
25dB

instruction >
23 / 59
 Combined mechanical & electrical tilt range
o 2° to 12° for antennas in frequency bands 850MHz and 900MHz
o 2° to 8° for antennas in frequency band range 1800MHz to 2600MHz
o 2° to 16° for antennas in 700MHz frequency band
5.2 Reference CW measurements for model tuning
It is highly recommended to tune a model based on CW measurements performed following the

specific approach detailed in the next part.
It is not recommended to tune a model based on scanner drive tests done on existing network
positioned with GPS and measurements samples binned during the post-treatment:
• Geo positioning with GPS is not sufficient since GPS latency takes too long, and GPS
accuracy is not good enough in dense urban / urban zones.
• Scanner measurements on existing network depend on the information accuracy about

this network. There are generally differences observed on azimuth, tilts and even cables
losses between the database and the field. This generates several dB error on the model
accuracy.
• Performing samples binning after the measurement collection generates some geo-
positioning error, since constant vehicular speed is assumed, which is not correct
especially in cities and at traffic lights.
• Rx antenna provided with the scanner is provided by scanner manufacturer. Patterns

and gain should be re-checked and verified for each frequency band since great
differences have been observed on many projects for any scanner provider.
UE drive tests could not be used for model calibration, since UE measurement accuracy depends
on how the UE is positioned, and can fluctuate between 7dB to 22dB error compared to
accurate receiver with rooftop antenna.
5.2.1 Calibration measurements
CW measurements must be done very precisely, as these measurements are the reference to
tune a propagation model.

instruction >
24 / 59
The measurements must be done following the recommendations in order to guarantee a good
accuracy in the signal strength measured, and also a very precise geo positioning of the samples
on the database used, whatever the database precision is.
The methodology used is very specific on data collection organization, accuracy and explanation.
Position, road choice and information collected must be adapted around the main activity.
 Dedicated Tx site must be used with generally omni antenna
 Dedicated Rx chain with CW receiver with data collection adapted and wheel trigger to
average samples every 40 wavelength to respect lee criterion (so binning is done
dynamically during the measurements collection)
 A specific geo positioning approach must be followed as it can have a great impact on
model accuracy if samples are not correctly positioned
The following recommendations must be followed in order to have some sufficient sites and
enough environments characterized by the measurements done in the area where the model
must be tuned:
 Good RF clearance (no nearby obstructions). Prefer an omni directional antenna on

stations without surrounding obstacles. Use a sectored antenna if obstructions are
present in the neighborhood to decrease the reflections from the backside.
 Various antenna heights considered.
 Various terrain around each station (dense urban, urban, suburban, rural, flat, hilly…)
 Clutter categories should all be equally represented with a minimum of 1000

measurement bins in each category.
 For dense urban and urban areas 80% of the sites must have their heights in line with
average buildings one, which is generally around 30m to 40m. 20% of sites could have
heights of around 50m to 60m in order to reach high distance range (3km for1800MHz
to 2100MHz and 5km for 900MHz)
 For suburban and rural the sites measured must have their heights in line with the type
of deployment required by the customer. For example if the customer wants to use 60m
towers, and if it is allowed, then measurements must be done with this height range. It is
recommended to keep the measured site height range from 30m to 60m at most if
possible.
 For each frequency band, a minimum of about 6 macro sites should be measured for a
model calibrated on a city with a minimum of 20.000 averaged samples (the exact
number is terrain dependent i.e. what route length can be traversed). If several cities

instruction >
25 / 59
represented by similar environments are measured in the same country, the number of
site per cities can be reduced to 4.
 For each frequency band, a minimum of 25 macro sites should be measured to

characterize the environments of medium size country (like France) with a minimum of
100.000 averaged samples.
The process and the application method are detailed in [12] in part 8 of this document.

instruction >
26 / 59
6 9955 LPWA: LoRa
The 9955 RNP LPWA module enables you to design and optimize LPWA-based wireless IoT
networks. Note that feature is available starting with tool version V7.3.1 onwards. Although
module is linked to extra licensing requirement, regular 9955 licenses do not cover this
technology.
For those designers owing only regular 9955 licenses with LPWA not included a dedicated
section, see section 7, describing some 9955 workarounds of designing LPWA networks by using
other available modules, was included (ex. WiFi,…).
Figure 6: Selecting 9955 LPWA module
You can use 9955 RNP to predict radio coverage, carry out calculations on fixed locations of
end-devices, and evaluate network capacity.
Figure 7: 9955 LPWA Network Tab
Supported LPWA technologies by this module are:
• LoRA
• UNB
• WMBus

instruction >
27 / 59
9955 RNP supports licensed as well as unlicensed frequency bands, technology-specific channel
configurations, and modulation techniques with or without link adaptation, and transmission and
reception diversity. You can create coverage predictions to analyze the following and other
parameters for LPWA channels in downlink and uplink:
• Signal levels
• Number of servers
• Carrier-to-interference-and-noise ratio
• Services areas
• Throughputs per cell
Moreover, the 9955 RNP LPWA ACP can be used for LPWA site selection based on server
redundancy as well as signal level and quality objectives. The ACP can also be used to optimize
operational IoT networks.
Note: no traffic modelling & MC simulations are supported.
6.1 Defining Network Configuration
This step deals with setting up a relevant RNP model in the RNP Tool of a LPWA network by
counting for the assumed type of environment, used network equipment performances,
assumed terminal capabilities, target traffic model, user service profiles, available type of
services. Defining a network configuration consists in a number of different steps the planner
shall follow:
 Creating a LPWA planning project

 Setting up project general parameters
 Importing Geo & Antenna databases
 Setting up project environments
 Propagation model selection
 Positioning of sites (APs)
 Transmitters/Cells configuration
6.1.1 Creating a LPWA planning project
This is the very first preparation step for a new LPWA project. When setting up a new LPWA RNP
project in the 9955 tool you should pass some of the following preparation steps, before
entering any of network data:

instruction >
28 / 59
 create a project based on the LPWA project template (9955 FileNewFrom a
Document Template)
 Coordinate system setup (9955 Tools menuOptions)
 Optionally, you may import some already existent (predefined) user configuration
options (9955 Tools menu User Configuration Load). This might already
define/include the geographic data to work with, computation and focus zones, define
folder configuration, populate prediction list but also to define some useful tool macros.
 Define way of computation (distributed/local) and related folder configuration (9955
Tools menu Distributed Calculation and 9955 Data Predictions Tab Properties)
 Set up/check project defaults (if differs from those from the template).
Coordinate system setup. Different coordinate systems are used all over the world. In a new
9955 project coordinate system setup should be done at: 9955 Tools menu Options .
This step should be the very first one in case of any new RNP project set-up.
It is mandatory that coordinate system of all the used maps and sites to be the same and to
match with the one the project was set up. Otherwise, one might be faced with wrong
positioning of network elements on the map which may compromise any planning effort spent
with this project.
For a very good overview on coordinate systems and geographical projection, but as well as for
explanation on how they are implemented in 9955, please check [6].
For more information on parameters to be entered as well as their recommended default values
please check [7] and [8].
6.1.2 Setting up project general parameters
This is the second and largest step of preparation of a new LPWA RNP project.
This step concerns the setup of general equipment and technology info in the 9955 RNP Tool.
These issues are linked to:
 Definition of LPWA Frequency Bands

 Selection of appropriate channel configuration
 Definition of LPWA radio bearers
 Definition/configuration of LPWA reception equipment types
 Checking of available Station Templates
 Definition of LPWA Services

instruction >
29 / 59
 Definition of LPWA Terminal (End Device) types
 Other Project Defaults: Default Prediction Resolution, Default propagation model …
LPWA Frequency Bands: 9955 LPWA module comes with a set of predefined LPWA frequency
band and frequency channel configurations. This list shall be completed only if the target
frequency band or channel parameters of the going to be implemented network are not found in
the list.
Table 8: LPWA Frequency Bands
9955 supports currently three different LPWA standards: LoRa, UNB and WMBus.
9955 default LPWA Frequency Band definitions are accordingly to these possible options.
Additionally, these accounts of supported different working bands (hence the variety of
definitions in the above table).
Correspondingly, the radio bearer table can be set up with the different bearer types/bearer
characteristics of these different technologies.
Table 9: LPWA Radio Bearers
Definition of LPWA reception equipment types is another important LPWA project preparation
step. LPWA reception equipment models both the reception characteristics of GW (cell)

instruction >
30 / 59
equipments and end devices (user terminals). Bearer selection thresholds and channel quality
indicator graphs are defined in these equipment models.
Table 10: Radio Bearer selection thresholds
Bearer Selection tables: graphs which relate to different bearer indexes, defined in the LPWA
Radio Bearers table, to their respective selection thresholds. Note in the above example, which
stands for LoRa, that only LoRa bearers can be selected by this LoRa equipment. Specific care
shall be taken in order to select only the right working bearers from the full range of available
different LPWA technology bearers.
It is possible to define different selection thresholds, corresponding to the same bearers, for
different reception equipment/mobility type.
Checking of available Station Templates is highly recommended as by using these existent

(predefined) templates creating network basic configuring will be very fast.
Table 11: LPWA Station Templates

instruction >
31 / 59
Note that Station Templates come with some defaults like frequency, channel configuration,
antenna configuration which need to be usually adapted to the current project’s need. This
adaptation has to be done after placing sites based on existing station templates.
Figure 8: LPWA Station Template Cell parameters
Note that by setting those three technology specific cell parameters the target supported LPWA
technology is selected for the project’s GWs model (LoRa in the above example).
Service definition should be project and technology specific as well, i.e. directly linked to the
customer’s requirement/targets. For this reason, no default service definitions to use could be
recommended although 9955 is providing some default values/ranges of some of the
parameters.
Table 12: LoRa Service definition example

instruction >
32 / 59
9955 Terminal type definitions should be project and technology specific, as well. Definitions
should be given according to the available information on the intended to be used end device
types. Some example definitions are given in the table below:
Table 13: LoRa Terminals
Other project defaults, like default propagation model, default resolution or folder configuration
where pathloss matrices are kept can be set at ‘Predictions’ properties:
Figure 9: Prediction Properties
6.1.3 Importing Geo & Antenna Databases
Requirements regarding geodatabase needs depend on the recommended type of propagation

model. For recommendations on model propagation selection please check section 6.1.5.
9955 offers import filters for the most commonly used geographic data formats.

instruction >
33 / 59
You can use these filters to import DTM, clutter information, traffic, vector files or scanned
images.
Geo maps should be best in the following format:
Table 14: 9955 Geodatabase formats
Format Can contain Geo-referenced

BIL DTM (16 bits), clutter heights (16 bits), Yes via .hdr files
clutter classes (8 bits), traffic (8 bits),
image (1-24 bits), population (8-32
bits), Generic (8-32 bits)
TIFF DTM, clutter height and classes, traffic, Yes via associated .tfw files if
Image, population, generic they exist
PlaNET© DTM, clutter height and classes, traffic, Yes via index files
Image, text and vector data
BMP DTM, clutter height and classes, traffic, Yes after manually entering
Image, population, generic northwest and southwest point
coordinates of the image
DXF® Vector data, vector traffic, population, Yes
generic
SHP Vector data, Vector traffic, population, Yes
generic
MIF/MID Vector data, Vector traffic, population, Yes
generic, building data
IST DTM, clutter height and classes, traffic, Yes via .hdr files
Image, population, generic
Erdas Imagine DTM, clutter height and classes, traffic, Yes automatically embedded in
Image, population, generic the data file
Morpho maps may indicate the following standardized clutter classes, which can easily be
interpreted by the RNP tool. For different classes a mapping will need to be performed.
Table 15: 9955 Standard clutter classes
Code Clutter-structure Description
0 not classified e.g. edge of a database
1 buildings Isolated cluster of high towers of skyscrapers or high buildings
2 dense urban 5-15 stories, areas within urban perimeters, inner city, very little vegetation,
high density of buildings, most buildings are standing close together, narrow
pedestrian zones and streets

instruction >
34 / 59
Code Clutter-structure Description
3 mean urban 3-8 stories, areas within urban perimeters, major streets are visible, most
buildings are standing close together, little vegetation, buildings, narrow
pedestrian zones and streets included
4 suburban 2 -4 stories, most buildings are standing close together, little vegetation
5 residential 1-2 stories, middle density of buildings with gardens. Both inside or outside
the city center. e.g. detached houses, villas
6 village 1-2 stories, low density of buildings with gardens outside of a city.
7 rural Wide open land with small isolated buildings, incl. agriculture and low tree
density
8 industrial Factories, warehouses, garages, shipyard, commercial buildings like shopping

centers, offices, terminals of airports etc.
9 open in urban Streets and open places in urban environments
10 forest All kind of forest, closed tree environments outside of a city
11 parks City parks, mixture of trees and low tree density, municipal parks, plantations,
golf courses
12 open area e.g. desert, beach, runways of an airport, big streets etc. huge parking areas
13 water Lakes, rivers, sea, all kind of fresh- and saltwater
6.1.4 Setting up Project environment
This section deals with LPWA parameters categories of: Mobility Types, User Profiles and
Environment.
The mobility type is characterizing the radio environment where the signal is transmitted. It
should be project specific.
The following mobility definitions are coming with the default LPWA template:
Table 16: 9955 Default LPWA mobility types
These are:

instruction >
35 / 59
 Fixed (no mobility)
 Pedestrian B speed 3 km/h mobility
For user profiles, no defaults can be provided for any project, they should be customized based
on the provided end device traffic behaviour information indicated by the customer.
Environment type definitions are linking together ‘User Profiles’ with ‘Mobility types’ (the
environment those users are acting in) by indicating density of users (#of users/square km) with
possible clutter weighting of distribution.
Example types of environments are:

Table 17: 9955 Default LPWA environnement types
6.1.5 Propagation Model Selection
In order to make reliable simulations with an accurate propagation model, the propagation
modelling is of capital importance.
Many propagation models are available for path loss calculation. However, each propagation
model is valid for a given range of parameters. Be careful in the results’ interpretation when
your project parameters are out of this range.
Propagation model selection is not a trivial issue: it should be done according to some
fixed in a contract design targets (there might be some prediction accuracy/network
performance requirements of the customer which can be fulfilled only by using some specific,
adapted to the modelled scenario, propagation model) and be in line with the available and
already imported geodatabases. The table below is summarizing different possible requirements
linked to different pathloss prediction methods and as well is indicating Nokia recommended
type(s) of propagation model(s) to use in those circumstances.
In 9955 new propagation models can be added by the user through the add-ins as module
concept.

instruction >
36 / 59
Table 18: 9955 Propagation Model Selections
Prediction Type Required Maps Propagation Model Comments
Empirical  Digital Terrain Map (DTM) Standard  Fast processing

prediction Propagation Model
 Morpho Map = clutter  Cheap maps
(SPM)
heights or clutter classes
 Ortho image (optional)
Deterministic  Digital Terrain Map (DTM) 2x2D or 3D Ray  Results will be

Prediction Tracing (IRT highly accurate
 Morpho Map = clutter
models)
heights or clutter classes  Possible to predict
for a wide range of
 Building Database receiver heights
 Ortho image (optional)
The following IRT models are supported by 9955 and recommended by Nokia:
 Volcano, developed by Siradel

 WinProp, developed by AWE-Communications
 Crosswave, developed by OrangeLabs
As a rule of thumb:
 For small scale LPWA networks Nokia recommends purchasing building maps and using an
IRT model (either Volcano, Crosswave or WinProp). If the prediction speed becomes
prohibitive or building database is not available one can use instead IRT an empirical SPM
model, specifically tuned for macro or small cells, see below.
 Building database and IRT model usage is recommended as well in cases of large or
medium size networks in areas where antenna radiations are obstructed by some
surrounding buildings (antenna locations are below the rooftop level of some of the
surrounding buildings) and/or the environment is strongly multipath.
Due to difficulties to have 3D database, ARFD team has created some pseudo outdoor
propagation model based on SPM formula for other technologies like LTE, UMTS or GSM. These
are recommended to be used for outdoor LPWA analysis purpose as this scenario is quite similar
to those of outdoor macro cells one.

instruction >
37 / 59
Default recommended SPM tuned models
In case no tuned model is available, and there is no time to make CW measurements and to
tune one, some default SPM models are available in default 9955 templates which can be
created with 9955V731. These are described in [11] in part 8 of this document.
These models cannot be considered as a tuned ray tracing ones, and presented to a customer
but they can be used with a reasonable reliability on a geographical raster database, and doesn’t
required a 3D database.
These default models are detailed in xls file referenced as [5] in part 8 of this document.
The SPM default models are proposed for 2D and 2.5D geographical databases
These models have been tuned on CW measurements all around the world.
They are not as accurate as a specific tuned model on a given area but ensure a limited risk
I<ERR>I <2dB & standard deviation <8dB
If geographical databases are used with clutter heights, then not these but SPM with
clutter heights models can be used.
Contact ARFD design team (owner of this document) to support and define the most
appropriate propagation model!!
6.2 Coverage analyses
Coverage analysis fundamentally remains the most critical step in the design of any network.
Appropriate selection of propagation models and the fade margins for the area coverage
probability are key factors to eliminate cell design that leads to interference or quality
degradation in the network.
A coverage prediction provided by the RNP tool provide a statistical approach for the analysis,
its main purpose is to get a best guess of what one would measure in some given location if
the analyzed network would be operational. Alternatively, by accounting for a safety margin
(see ‘Cell Edge Coverage probability’ below) one would ensure that taken measurement would
exceed with a certain probability (higher than 50%) predicted (more conservative) levels.
One can see that after the project setup steps (presented in section 6.1) one can proceed with
some predictions which can be:
• cell load independent (signal level coverage)

instruction >
38 / 59
• cell load dependent (all the quality analyses)
9955 approach of signal level predictions: at each pixel of the network coverage area, a non-
interfering probe mobile is placed (the probe mobile does not cause any interference in the
system). The pathloss is computed for each probe mobile location; this is the computed path
loss, plus a shadowing margin. The shadowing margin is calculated by the tool based on the cell
edge coverage probability level set by the user and on the model standard deviation associated
to the mobile clutter class. These parameters are commented below:
• Model standard deviation (dB) at the receiver position: The standard deviation
characterizes the propagation environment, and can be set independently for each
clutter type in 9955 V7.3.1.
• Cell edge coverage probability level (%): In 9955 V7.3.1 a cell edge coverage
probability level in % has to be set for each tool prediction. The tool calculates the
shadowing margin to be applied for each clutter type based on the given reliability level
and on the shadowing standard deviation.
The coverage probability level can be expressed as the probability that the received signal
reaches at least the required minimum power level (dBm); or that the predicted path loss is able
to overcome the shadowing.
Important: in case of LKB derived ‘RSSI design level’ is used as design parameter in a prediction
where the scope is cell edge to be predicted, coverage area to be derived, no shadow margin
option has to be used. This is because ‘RSSI design level’ is already computed in the LKB for 95%
of reliability (shadow margin already accounted).
6.2.1 Signal Level Coverage analysis
The following facts might impact strongly requested coverage types to be carried out:
 there is a contractually agreed coverage KPI (ex. RSSI level of -100 dBm is provided in
98% of the network area with 95% of reliability level)
 continuous signal level coverage is expected while throughput KPIs are defined for cell
edge performances
 indoor coverage type is targeted, indoor performance KPI was defined
Before running any predictions please ensure that:
 all required project parameters are set as mentioned in the previous sections and target
of the planning is clearly defined

instruction >
39 / 59
 site locations were found based on friendly sites/green field planning
 Implemented were an initial network configuration by providing proper Transmitter/Cell
configurations
The planning process for this coverage analysis step may consist of:
 Issue coverage plot based on Best Server (‘Coverage by Transmitter’) prediction for the
worst limiting scenario (Insert the parameters either from UL or DL link budget for this),
taken with no margin
 try to fix a right coverage footprint of the cells by solving suspected overshooting
problems (if any) or not clear dominance area of the cells
 Reiterate process for some modified site configuration/network layout
 generate coverage statistics and try to provide uniform coverage; pay particular
attention to sectors with too large or too reduced coverage areas
 Identify coverage holes and optimize coverage
 Generate Signal Strength plots (‘Coverage by Signal Level’) in DL for all the major cases
defined by the design targets/design requirements. Ensure that coverage area, i.e. places
where signal level is stronger than RNP RSSI design threshold provided by LKB, is in
planning target.
 Assess the Signal Level (RSSI) coverage performance by generating statistics
 Change site config/network layout and reiterate process if RSSI level in high priority
areas is not sufficient

instruction >
40 / 59
Figure 10: LoRa - Coverage by Signal Level
 Issue ‘Overlapping Zones’ study (‘Overlapping Zones’ type of prediction) for the above
case, taken with some same margin (ex. 4 dB)
 configure, at the display options, a higher number of ‘Value Intervals’ for the going to be
displayed ‘Number of Servers’ than available number of channels (ex. fix 4 intervals in
case of default channel number of 3); generate coverage statistics and check the ‘size’
(indicated percentage of focus zone) of areas where the number of covering servers is
higher than available number of channels; those areas, with no regards on the frequency
plan (which can still be missing) will be with high risk of interference as there will exist all
the time at least two servers working on the same channel/carrier;
 perform additional local analyses by using the ‘Point Analysis’ feature, in order to check
what are the predicted signal levels coming from the overlapping servers in some critical
places; if result is not satisfactory try to conclude on the main source for this high risk of
interference (ex. check which covering servers are working on the same carrier) and
 reiterate process for some modified site configuration (antenna azimuth & tilt, if the
case, reduce Tx Power) by trying to implement one of the two following solutions:
o create cell dominance of a chosen cell in that area (if possible)
o remove from the area one or more of the cells contributing to this high risk

instruction >
41 / 59
6.2.2 DL/UL CINR analysis
The scope of this step is a more detailed interference analysis.

Analysis can be performed based on assumed network load conditions (no simulations available
in LPWA). Typically, one will proceed with assuming some given fixed UL/DL traffic load of the
LPWA cells (GWs). These levels are 80% for high loaded, 50% for moderately loaded and 30% for
lightly loaded conditions. Recommended is that analysis to be carried out for at least the high
load conditions (most interference limited).
The planning process for this analysis can be summarized as follows:
 Issue DL/UL raster CINR prediction plot, (‘Coverage by C/(I+N) Level (DL)’, ‘Coverage by
C/(I+N) Level (UL)’), with no margin, by using a representative Terminal type and selected
mobility type.
 generate statistics and quantify results; compare against possible existing defined
quality KPI
 Perform CINR predictions for a different channel plan if result is not satisfactory
  Identify problematic interference areas and iterate back to the first step of the
planning process if necessary after site/cell configuration has been changed accordingly.

instruction >
42 / 59
Figure 11: LoRa - interference analysis
6.2.3 DL/UL Service coverage
This next (and optional) step concerns issuing service coverage plots, which correspond to the
already optimized network signal level and interference conditions.
This can be performed as well based on assumed fixed UL/DL traffic loads of the LPWA cells.
The planning process for this target can be summarized as follows:
 Issue DL/UL raster Service bearer coverage ( ‘Service Area Analysis (DL)’, ‘Service Area
Analysis (UL)’) prediction plots, with no margins, by using the same representative
Terminal and mobility types as for CINR predictions.
 Generate statistics (Reports), histograms on the obtained results; compare against
possible defined KPIs
  Identify problematic Service Coverage areas and iterate back to the first step of the
planning process if necessary after site/cell configuration has been changed accordingly.

instruction >
43 / 59
Figure 12: LoRa - Service Area prediction
6.2.4 DL/UL Throughput coverage
This step has its target of assessing obtained throughput performances. This means that
usually, available capacity provided in the optimized coverage area is checked, unless capacity
related KPIs were defined while network need to be optimized in order to achieve those.
9955 provides the following types of throughput coverage predictions:
 Peak MAC Channel Throughput

 Effective MAC Channel Throughput
 Application Channel Throughput
options, which are available for either a ‘Coverage by Throughput (DL)’ or a ‘Coverage by
Throughput (UL)’.
Alternatively, options of:
 Peak MAC Cell Capacity

 Effective MAC Cell Capacity
 Application Cell Capacity
can be selected.

instruction >
44 / 59
Nokia recommends evaluation of the more accurate Effective Throughput/Effective Capacity as
these accounts of actual BLER performances of the receiver equipments.
The planning process for this target can be summarized as follows:
 Issue DL raster ‘Coverage by Throughput (DL)’ prediction plot, by using the same
representative Terminal and mobility types as for CINR & Service coverage predictions.
 Issue UL raster ‘Coverage by Throughput (UL)’ prediction plot, by using the same
representative Terminal and mobility types as for CINR & Service coverage predictions.
 Generate statistics (Reports), histograms on the obtained results.
6.3 Subscriber list based analysis
Although 9955 LPWA does not offer Monte Carlo simulation functionality it supports user
performance analysis based on a subscriber list.
Subscribers, i.e. locations on end devices, can be distributed anywhere in the coverage area.
Figure 13: LoRa – Subscriber List based analysis
Detailed results of predicted RF performances are provided:

instruction >
45 / 59
Figure 14: Subscribers predicted performances
Additionally, one can inspect and check performances at individual subscriber locations:
Figure 15: Subscriber predicted performance

instruction >
46 / 59
7 9955 workarounds
This section contains the different steps to perform LoRa predictions with current 9955 version
by using other than LPWA technology module. These proposed 9955 work arounds are with
limited applicability (they should not be applied in all circumstances), they are not valid by
default to all IoT technologies and regions, they have to be field validated as work around.
To have the 9955 configuration for some LPWA workaround, specific atl files should be used in
which appropriate settings have been done.
To have these atl files please contact ARFD team
7.1 LoRa workaround with rnp 9955 V7.3.1
To have the 9955 configuration for LoRa workaround, the atl files of ‘LoRa_templateV01.ATL’
should be used, see [3]. This contains predefined settings to model LoRa by using the 9955 WiFi
technology module.
Figure 16: Using 9955 WiFi template to model LoRa
7.1.1 LoRa customized settings
Frequency bands

instruction >
47 / 59
Figure 17: LoRa EU frequency band definition
According to Figure 17 a LoRa frequency band is declared in the European ISM band of 868 MHz.
A channel bandwidth of 125 kHz is specified.
Reception Equipments
Figure 18: LoRa GW reception equipment definition
Reception equipment definitions are with considering estimated (see Table 5 and Table 6) CINR
(C/I+N) values.
Radio Bearers

instruction >
48 / 59
Figure 19: LoRa Radio Bearers
Services
Figure 20: LoRa Service definition
Terminals

instruction >
49 / 59
Figure 21: LoRa Terminal definition
7.1.2 LoRa predictions
This workaround allows the same as section 6.2 presented coverage analyses to be carried out.
Although, some definitions will account of the workaround qualities presented in the previous
section 7.1.1.
Typical predictions:
• Coverage by Best Server
• Coverage by Signal level
• Overlapping Zones
• Coverage by C/(I+N) Level
• Service Area Analysis
• Coverage by Throughput
A ‘Coverage by Best Server’ prediction allows visualization of cell footprints, i.e. areas where a
given cell has the quality of being the best serving. It helps managing cell sizes and removing
overshooting problems.

instruction >
50 / 59
Figure 22: LoRa Coverage by Best Server
Figure 23: LoRa Coverage by Signal Level

instruction >
51 / 59
The ‘Coverage by signal level’ plot is performed relative to signal level thresholds that can be
operator specified or linked to different service availabilities defined by device sensitivity figures
or LKB RNP design levels. In this later case predicted signal levels will directly indicate service
availability ranges being defined based on LKB MAPLs for different LoRa services (mapped onto
downlink RSSI)
Figure 24: Overlapping zones 4dB
The criterion to be applied for server overlaps is not technology specific, and its efficiency has
already been measured on other technologies like GSM, CDMA, W-CDMA and LTE networks.
Within 4dB of the best server
– % area with 4 servers or more should be < 2%.
– % of area with 2 servers or more should be < 35%
Within 10dB of the best server
– % of area with 7 servers or more should be < 2%.

instruction >
52 / 59
Figure 25: LoRa Coverage by CINR
Figure 26: Coverage by CINR Properties

instruction >
53 / 59
Figure 27: LoRa Service Area DL
Figure 28: Effective Service area (UL&DL)

instruction >
54 / 59
Figure 29: Coverage by DL Throughput
7.1.3 Subscriber list based analysis
Subscribers, i.e. locations on end devices, can be distributed anywhere in the coverage area.

instruction >
55 / 59
Figure 30: Subscriber list based analysis
Detailed results of predicted RF performances are calculated:
Figure 31: Subscribers’ computed performances

instruction >
56 / 59
8 REFERENCES
[1] Semtech, ‘A technical overview of LoRa and LoRaWAN’, [Online]. Available:
http://www.semtech.com/wireless-rf/iot/LoRaWAN101_final.pdf
[2] Semtech, ‘SX1272/73 - 860 MHz to 1020 MHz Low Power Long Range Transceiver’,
[Online]. Available: http://www.semtech.com/images/datasheet/sx1272.pdf
[3] IoT 9955 template, ‘LoRa_templateV01.ATL’, atl file for LoRa workaround
[4] LoRa NOKIA Link Budget tool & presentation
Sharenet Livelink: https://sharenet-

ims.int.net.nokia.com/livelink/livelink?func=ll&objId=549741006&objAction=browse&viewType=1
[5] 9955 SPM Default propagation models recommended for 400-5500 MHz ed9.xlsx
[6] 3DF 01955 6080 BGZZA, ‘A9155 Application Note : Coordinate Systems and Geographic
Projections’,
https://mdms-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=64155525&objAction=browse&viewType=1
[7] ‘User Manual 9955V7.3.1’, D549691914
https://sharenet-
ims.int.net.nokia.com/livelink/livelink?func=ll&objId=549706310&objAction=browse&vie
wType=1
[8] ‘Technical Reference Guide 9955 V7.3.1’,
https://sharenet-
ims.int.net.nokia.com/livelink/livelink?func=ll&objId=549706310&objAction=browse&vie
wType=1
[9] 3GPP TR 45.820, “Cellular system support for ultra-low complexity and low throughput
Internet of Things (CIoT)”, release 13, 2015-11. [Online]. Available:
http://www.3gpp.org/ftp/Specs/archive/45_series/45.820/45820-d10.zip
[10] Qualcomm, Incorporated, “Narrowband IoT (NB-IoT),” RP-151621, 3GPP TSG RAN
Meeting #69, Sept. 2015. [Online]. Available:
http://www.3gpp.org/ftp/tsg_ran/TSG_RAN/TSGR_69/Docs/RP-151621.zip
[11] 9955 default propagation models recommended for 400 - 5500 MHz frequency bands

instruction >
57 / 59
Kiosklive : LTE/IRC/APP/032646
Sharenet Livelink : https://sharenet-
[12] CW Measurements guideline

https://sharenet-
[13] Antennas & OEM basics

https://wcdma-ll.app.ALCATEL-
LUCENT.com/livelink/livelink.exe?func=ll&objId=68078685&objAction=browse&viewType=1
[14] Antenna link validation

Kiosklive reference: LTE/IRC/APP/032642
https://wcdma-ll.app.alcatel-
[15] Interference Detection on new networks

https://sharenet-
[16] RF and Environment survey guideline

https://sharenet-
[17] Antenna Isolation Guideline between LPWAN and existing technologies
[18] ASP/ACP tool description

[19] Winprop description and settings

[20] Crosswave user manual

[21] Volcano user guide

https://mdms-ll.app.alcatel-

instruction >
58 / 59
9 Abbreviations
Acronym Definition
ACP Automatic Cell Planning
CINR Carrier to Interference plus Noise Ratio
CSS Chirp Spread Spectrum
GW Gateway
IoT Internet of Things
ISM Industrial, Scientific and Medical
KPI Key Performance Indicator
LKB Link Budget
LoRa Long Range
LPWA Low Power Wide Area network
MAPL Maximum Allowed PathLoss
NB-IoT Narrowband IoT
OFDMA orthogonal frequency-division multiple-access
PRB Physical Ressource Block
RNP Radio Network Planning
RSSI Received Signal Strength Indocator
SC-FDMA single-carrier frequency-division multiple-access
SF Spreading Factor
SNR Singnal to Noise Ratio
WiFi (Wi- Wireless Fidelity. Wireless Local Area Networking standard based on IEEE
Fi) 802.11

instruction >
59 / 59

IoT RF Design Guideline LoRa V01 Internal

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IoT RF Design Guideline LoRa V01 Internal

Uploaded by

Copyright:

Available Formats

IoT RF DESIGN GUIDELINES: LoRa

Internal document – Do not circulate outside Nokia

Document issue: 1.0

Author Tibor Asztalos

20-12-2016– LTE/IRC/APP/ <Nokia - Proprietary - Use pursuant to Company © Nokia 2016

1.1 Object ..................................................................................................................................... 4

1.2 Scope of this document ...................................................................................................... 4

1.3 Audience for this document ............................................................................................... 4

1.4 IoT RF Design purpose ......................................................................................................... 5

1.5 RNP Tools ............................................................................................................................... 5

2 IoT Networks ......................................................................................................................... 7

2.1 LoRaWAN ................................................................................................................................ 7

2.1.1 LoRa EU .................................................................................................................................. 9

2.1.2 LoRa US .................................................................................................................................. 9

2.2 IoT Capacity considerations................................................................................................ 11

2.2.1 LoRa capacity ........................................................................................................................ 11

3 IoT Link Budgets ................................................................................................................... 13

3.1 Factors impacting coverage range .................................................................................... 13

3.2 LoRa Link Budget .................................................................................................................. 14

3.2.1 Receiver sensitivity............................................................................................................... 14

3.2.2 Example Link Budget ............................................................................................................ 16

4 IoT:LoRa Coexistence with other technologies................................................................ 19

4.1 Coexistence of LoRa operating in EU 863-870MHz band .............................................. 19

4.2 Coexistence of LoRa operating in US 902-928MHz band.............................................. 20

5 IoT RF Design considerations ............................................................................................. 21

5.1 SITE ACQUISITION................................................................................................................. 21

5.1.1 Site survey ............................................................................................................................. 21

20-12-2016– LTE/IRC/APP/ <Nokia - Proprietary - Use pursuant to Company © Nokia 2016

5.2.1 Calibration measurements.................................................................................................. 24

6 9955 LPWA: LoRa.................................................................................................................. 27

6.1 Defining Network Configuration......................................................................................... 28

6.1.1 Creating a LPWA planning project ...................................................................................... 28

6.1.2 Setting up project general parameters............................................................................. 29

6.1.3 Importing Geo & Antenna Databases ................................................................................ 33

6.1.4 Setting up Project environment ......................................................................................... 35

6.1.5 Propagation Model Selection .............................................................................................. 36

6.2 Coverage analyses................................................................................................................ 38

6.2.1 Signal Level Coverage analysis ........................................................................................... 39

6.2.2 DL/UL CINR analysis ............................................................................................................. 42

6.2.3 DL/UL Service coverage ...................................................................................................... 43

6.2.4 DL/UL Throughput coverage .............................................................................................. 44

6.3 Subscriber list based analysis ............................................................................................. 45

7 9955 workarounds ............................................................................................................... 47

7.1 LoRa workaround with rnp 9955 V7.3.1 ........................................................................... 47

7.1.1 LoRa customized settings ................................................................................................... 47

7.1.2 LoRa predictions ................................................................................................................... 50

7.1.3 Subscriber list based analysis ............................................................................................. 55

20-12-2016– LTE/IRC/APP/ <Nokia - Proprietary - Use pursuant to Company © Nokia 2016

This document describes the process of dimensioning and

Low Power Wide Area (LPWA) refers to technologies that

In this guideline design recommendations for LPWA

1.2 Scope of this document

This document contains:

 IoT:LoRa RF design considerations

 IoT:LoRa Traffic profile

 IoT:LoRa Link Budget example

 IoT Design solutions for coverage

 All the parameters settings for 9955 radio planning tools

1.3 Audience for this document

The audience for this document is the people involved in:

 IoT Radio Network design and Planning

 IoT Radio Network engineering

 IoT Radio Network optimization