NETWORK ENGINEERING

LTE18 Transport IoT

complex

1 © Nokia 2017
Nokia internal use
LTE18 Transport IoT complex
Table of contents

Introduction Technical Inter –

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

Configuration Deployment Dimensioning

Management Aspects Aspects
Parameters and Activation, Configuration Dimensioning Impacts
Parameterization Examples, Fault Mgmt, and Examples
Scenarios Trial Area

5 © Nokia 2017
Nokia internal use
LTE18 Transport IoT complex

Introduction

Table of contents

<chapter:introduction>

6 © Nokia 2017
Nokia internal use
 LTE
Introduction
Legend BTS
Mobile Backhaul (MBH)
BTS routing network
Common node icons function
are used throughout
Backhaul switch
the presentation, as BTS integrated
switch
defined on this slide
Backhaul router
IPsec engine

Scheduler /
shaper function ToP Server

Controller /
core nodes
NetAct

IPv4 IPv6
Security Gateway
U C U C (SecGW)
Application binding to
transport IP interface
M S M S

U C U C IPsec tunnel
Application binding to
virtual IP interface
M S M S

Transport IP interface (VLAN or untagged

Ethernet; no application binding, used e.g. for T T
tunnel termination or redundancy)

7 © Nokia 2016
Nokia internal use
Introduction
Legend

Apart from icons/symbols on previous slide, new node is introduced specifically for the purpose of Cellular IoT
(CIoT) subject:
• CIoT Serving Gateway Node (C-SGN) – combined MME and S/P-GW function node, optimized for NB-IoT
traffic handling
• Following Evolved Packet Core (EPC) nodes icons are used in the document

MME

SGW, PGW, S/P-GW

C-SGN

8 © Nokia 2017
Nokia internal use
Introduction
IoT – Technology choices

Internet of Things

Massive IoT connectivity Critical IoT connectivity

• Simple cheap devices • „Always available“

• Low energy consumption • Very low latency
• Massive number of devices • Flexibility
• Improved coverage • Example: Connected cars
• Low datarates
• Example: Smart meters

9 © Nokia 2017
Nokia internal use
Introduction
Massive IoT connectivity (key enablers)

Low deployment cost Long battery life

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

Many devices will be located indoors,

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

Low device cost $ Enhanced coverage

10 © Nokia 2017
Nokia internal use
Introduction
IoT Radio connectivity (as defined by 3GPP Release 13)

• Coverage: +20dB (over legacy LTE) • Bit rate : <62kbit/s

Massive IoT • Module cost: $2-4 • Network upgrade: SW
connectivity • Battery life: +10 years • Spectrum: GSM /LTE (200 kHz or shared)
• Scalability: +50k/cell*
• Simple, cheap devices
• Low energy consumption
NB-IoT (200kHz)
• Massive number of devices • Coverage: +15dB (over legacy LTE) • Network upgrade: SW
• Improved coverage • Module cost: $3-5 • Spectrum: LTE (1.4 MHz or shared)
• Low datarate • Battery life: +10 years
• Scalability: +50k/cell*
Bit rate : <1Mbit/s
LTE-M (1.4MHz)
•

• Coverage: +20dB (over legacy EGPRS) • Bit rate : <70kbit/s

• Module cost: $3-5 • Network upgrade: SW
• Battery life: +10 years • Spectrum: GSM (200 kHz or shared)
• Scalability: +50k/cell*
EC-GSM (200KHz)
*Note: Assumptions according to the Traffic Model defined by 3GPP (3GPP TS 45.820). More details can be found on slide #. Different assumptions will lead to different numbers.

11 © Nokia 2017
Nokia internal use
Introduction
Internet of Things example use cases classification

→ Small messages
→ Not frequent in time Blood pressure
monitors Agriculture monitors
→ Applicable where LTE system is already in place
→ Network resources utilization: 1PRB
→ Coverage: up to 164 dB (Pathloss)
Smart Meters Smoke detectors
Control Panels NB-IoT
→ Medium size messages
→ Frequent in time Blood pressure
Fitness bands monitors Agriculture monitors Patient monitors
→ Applicable where LTE system is already in place
Trackers:
→ Network resources utilization: up to 6PRBs • Car tracker
→ Coverage: up to 156 dB (Pathloss) • Kids tracker
• Pet tracker Smart Meters
Smoke detectors
Control Panels
Smart Watches
LTE-M
→ Small messages
→ Not frequent in time Blood pressure
Agriculture monitors
→ Applicable where GSM system is already in place and no LTE monitors
→ Network resources utilization: 1TSL for signalling and data
traffic multiplexed with legacy users
→ Coverage: up to 164 dB (Pathloss) Smart Meters Smoke detectors
Control Panels EC-GSM

12 © Nokia 2017
Nokia internal use
Introduction
NB-IoT and LTE-M deployment comparison

Depending on operator needs/preferences following main factors can be taken into consideration when
deciding to deploy NB-IoT vs LTE-M option

NB-IoT LTE-M
Pathloss coverage [dB] 164 156
Message rate Not frequent Frequent
Message size Small Medium
Bit rate [kbps] <62 <1000
UE module cost [$] 2-4 3-5

13 © Nokia 2017
Nokia internal use
Introduction
LTE18 Transport IoT complex

Scope
• LTE18 Transport IoT document is focused on transport aspects of NB-IoT and LTE-M deployment in LTE BTS,
concerning LTE18 release feature scope
• Following IoT features are considered having biggest impact on transport aspects and introducing to LTE
BTS main functionalities respectively for:
- NB-IoT
• LTE17A LTE3071 NB-IoT Inband (webNEI link: part 1, part 2; radio related materials)
• LTE18 LTE3543 NB-IoT Standalone (webNEI link; radio related materials)
- LTE-M (aka eMTC, Cat-M)
• LTE17A LTE3128 LTE-M (webNEI link: part 1, part 2; radio related materials)
• There are also several extension features available (mainly impacting radio interface capabilities), these are
listed for reference in ‘Interdependencies’ chapter

14 © Nokia 2017
Nokia internal use
Introduction
NB-IoT Overview

Inband:
- LTE3071 introduces a 3GPP Rel. 13 inband NB-IoT mode
- FSMF deployment, without coverage enhancement will be supported via LTE3071
- FDD mode, half duplex operations, 200 kHz UE RF bandwidth for both downlink and uplink
- The data transmission over SRB1bis (data over NAS)

LTE3071 LTE3543 LTE3570

(upcoming)

NB IoT
NB IoT
NB IoT

LNCEL: nbIoTMode

LTE carrier LTE, WCDMA, or GSM carriers LTE carrier

inband standalone guard band

15 © Nokia 2017
Nokia internal use
Introduction
NB-IoT Overview

Standalone:
- LTE3543 introduces a standalone mode for NB-IoT functionality over FSMF and AirScale
- Standalone mode of operations supports FDD deployment only
- NB-IoT standalone is transmitted on own spectrum without a hosting LTE carrier
- Both TM1 (new comparing to the LTE3701) and TM2 are supported, only 2RX supported for standalone

LTE3071 LTE3543 LTE3570

(upcoming)

NB IoT
NB IoT
NB IoT

LNCEL: nbIoTMode

LTE carrier LTE, WCDMA, or GSM carriers LTE carrier

inband standalone guard band

16 © Nokia 2017
Nokia internal use
Introduction
NB-IoT Overview

Transport:
- Both inband and standalone NB-IoT mode deployment in Nokia LTE BTS support IoT data
and signaling traffic transfer via LTE BTS C-Plane interface
NB-IoT (C+U plane)
LTE C-plane

C
MBH
C C C MBH

Common MME for

Wideband LTE C-Plane Dedicated C-SGN for
and NB-IoT traffic NB-IoT traffic

17 © Nokia 2017
Nokia internal use
Introduction
LTE-M Overview

Main properties
• Key LTE-M functionality introduced to LTE BTS via LTE3128
• 6PRBs in frequency dimension (1.4MHz) allocated to LTE-M per cell
• Inband location, within existing LTE carrier
• Shared with legacy LTE, meaning that PRBs can be reused for legacy, non CAT-M UEs

LTE-M
LNCEL: actCatM

LTE carrier
inband

18 © Nokia 2017
Nokia internal use
Introduction
LTE-M Overview

Transport:
- LTE-M mode deployment in Nokia LTE BTS support IoT data and signaling traffic transfer via
LTE BTS U-Plane and C-Plane interfaces respectively (similar to normal LTE traffic)

C
LTE-M CP
LTE C-plane
U
LTE-M UP
C
C
C MBH LTE U-plane
U MBH U
C

U U

Common EPC for

Wideband LTE C-Plane Dedicated EPC for
and LTE-M traffic LTE-M traffic

19 © Nokia 2017
Nokia internal use
Introduction
Before & after

Before After

• M2M/IoT traffic was served by legacy
networks ineffectively
• A lot of small messages could cause
control plane blocking
• Problems with coverage for devices in
critical locations
• Cost of complex modems blocks massive
deployment
• NB-IoT and LTE-M were developed to
serve massive number of IoT devices
• Optimized for improved coverage and
lower power consumpion
• Simplified complexity of modems help to
reduce implementation costs
• Easy deployment by software upgrade of
the legacy network

20 © Nokia 2017
Nokia internal use
LTE18 Transport IoT complex

Technical Details

Table of contents

<chapter:technical_details>

21 © Nokia 2017
Nokia internal use
Technical Details
NB-IoT

Protocol stack
NB-IoT CP+UP
• S1-lite protocol stack is supported for NB-IoT (according to
3GPP TR 23.720) S1-AP

- The legacy LTE Transport Architecture is used to transport SCTP

NB-IoT CP traffic IP
- NB-IoT UP traffic is carried in S1-AP
Ethernet
- C-plane and U-Plane are carried over S1-C interface
S1-lite
TNL stack

22 © Nokia 2017
Nokia internal use
Technical Details
NB-IoT

LTE BTS IP interfaces

• All NB-IoT traffic is handled at LTE BTS side by LTE C-Plane
C C/U
IP address
MBH MBH
• Full flexibility with regard to LTE BTS IP address
configuration is maintained as for normal LTE C-Plane
operation, i.e.: C C/U

MBH MBH
- Relevant IP address can be dedicated or shared with any
other LTE plane
- Allocation to transport IP interface or virtual IP interface LTE
C1
MBH
• In case separate core (e.g. C-SGN) and separate backhaul
network is planned for NB-IoT, LTE505 Transport C2 NB-IoT
Separation for RAN Sharing can be used MBH

23 © Nokia 2017
Nokia internal use
Technical Details
NB-IoT

Transport QoS (1/2)

• From transport QoS perspective NB-IoT traffic receives the
same treatment as LTE C-Plane traffic, especially with regard
to:
- DSCP marking C1 EVC1 C2

MBH
- PCP marking
- Allocation to LTE BTS and backhaul nodes transport
queues
Single (common)
• If single transport IP interface is used in LTE BTS towards shaping rate for LTE
MME and (optionally) C-GSN only single (common for LTE C-plane and NB-IoT

C-Plane and NB-IoT traffic) UL shaping rate can be set

24 © Nokia 2017
Nokia internal use
Technical Details
NB-IoT

Transport QoS (2/2)

1 C2
• If separate transport IP interfaces are used in LTE BTS T1

towards MME and C-GSN, for example: C1

T2
MBH
(1) LTE C-Plane allocated to single virtual IP interface (C1),
C3
two transport IP interfaces configured (T1, T2), by IP
routing configuration LTE C-Plane traffic uses T1 and NB Separate (dedicated)
IoT traffic uses T2 shaping rate per LTE
C-plane and NB-IoT
(2) Two LTE C-Plane IP addresses allocated to dedicated
transport IP interfaces (LTE505 Transport Separation for
C3
C1
RAN Sharing required), separate for LTE C-Plane and MBH
C2
NB-IoT purposes respectively
…dedicated UL shaping rates can be set per LTE C-Plane and 2
C4

NB-IoT traffic
25 © Nokia 2017
Nokia internal use
Technical Details
NB-IoT

Transport security (1/2)

• To provide NB-IoT traffic encryption over backhaul network
IPsec functionality has to be used (LTE689 LTE IPsec
Support required)
• The same general properties and rules of IPsec
configuration apply to NB-IoT encryption, i.e. traffic subject
C
to encryption is defined basing on IPsec policies with MBH
following criteria for NB-IoT:
- source → LTE BTS C-Plane IP address
- destination → MME IP address or C-SGN IP address
- protocol → SCTP

26 © Nokia 2017
Nokia internal use
Technical Details
NB-IoT
LTE C-Plane + NB-IoT in
common IPsec tunnel
Transport security (2/2)
MBH
• Dedicated IPsec tunnel for NB-IoT: C

- In case common MME is used for LTE C-plane and NB-

IoT traffic, it is not possible to encrypt NB-IoT traffic
individually (both LTE C-plane and NB-IoT can be
encrypted or not), thus only common IPsec tunnel is
possible NB-IoT in dedicated IPsec
tunnel
- In case dedicated C-SGN is deployed for NB-IoT traffic,
also individual encryption (or lack of thereof) can be MBH
C
applied to NB-IoT, thus dedicated IPsec tunnel is
possible

27 © Nokia 2017 IPsec tunnel

Nokia internal use
Technical Details
NB-IoT
mmeRatSupport = Wideband-LTE

Core selection
C
• In case dedicated C-SGN is deployed for NB-IoT MBH
traffic, IoT core selection can be based on:
(1) Dedicated LNMME/mmeRatSupport
parameter introduced to LTE BTS together 1 mmeRatSupport = NB-IoT
with NB-IoT functionality
(2) Dedicated PLMN ID allocated to NB-IoT 2 PLMN ID = A
network
C
MBH

PLMN ID = B

28 © Nokia 2017 IPsec tunnel

Nokia internal use
Technical Details
NB-IoT

Transport separation C1 MBH

C3

• In case dedicated C-SGN is deployed for NB-IoT traffic, transport C2

MBH
network separation can be based on following options:
C4
(1) Two LTE C-plane IP addresses (dedicated for LTE C-plane and NB- 1
IoT) using transport (or virtual) IP interfaces, LTE505 required
(2) Single LTE C-plane IP address (common for LTE C-plane and NB-IoT)
2
using virtual IP interface and two transport IP interfaces, LTE505 not
required. C2
T1 MBH
• Since there is a single IP termination point for LTE C-plane available in C1
T2
option (2), there might be problems with proper traffic separation in MBH
downlink direction unless source based routing is deployed. Therefore C3

option (1) is considered easier (thus recommended).

29 © Nokia 2017 IPsec tunnel

Nokia internal use
Technical Details
NB-IoT C1 IPv6 C2

MBH
1
IPv6 support
• NB-IoT traffic at transport level is IP version agnostic, same
C2
properties and configuration rules apply to NB-IoT as to LTE
C-Plane IPv6 address use, according to LTE2299 Dual Stack C1 IPv6
IPv4/IPv6 for S1/X2 feature scope MBH
C3
2
• Exemplary scenarios:
(1) IPv6 backhaul network, common MME used for LTE C-
Plane and NB-IoT traffic
IPv4
(2) IPv6 backhaul network, dedicated S-GSN used for NB- C1 MBH
C2

IoT traffic C1
IPv6
(3) IPv4/IPv6 dual-stack LTE C-Plane IP address configured, MBH
e.g.: IPv4 meant for LTE C-Plane traffic, IPv6 meant for C3

3
NB-IoT traffic (LTE505 not required)
30 © Nokia 2017 IPsec tunnel
Nokia internal use
 p
Primary SCTP association
S
Technical Details Secondary SCTP association

NB-IoT

SCTP multi-homing Common MME, symmetrical SCTP multi-

• If SCTP multi-homing is deployed (at MME/S-GSN side using homing

LTE775 SCTP multi-homing (MME), at LTE BTS side using MBH

LTE648 SCTP Multi-homing, or both) it also applies to NB-IoT C1p C2p

traffic (as LTE C-Plane IP termination points are used by NB- C1s C2s

IoT) 1

• Both options are supported:

Dedicated S-GSN, symmetrical SCTP
(1) Common MME used for LTE C-Plane and NB-IoT traffic multi-homing

C2p
(2) Dedicated S-GSN used for NB-IoT traffic
C2s
• Additional C-Plane IP address is meant for redundancy, and C1p

not for traffic differentiation or load balancing C1s MBH C3p

• In case dedicated LTE C-Plane IP addresses pair is required for 2 C3s

NB-IoT, LTE505 is mandatory

31 © Nokia 2017 IPsec tunnel
Nokia internal use
Technical Details
LTE-M

Protocol stack
• Legacy S1 protocol stack is supported for LTE-M
- The legacy LTE Transport Architecture is used
to transport LTE-M CP and UP traffic LTE-M CP LTE-M UP
- LTE-M C-plane and U-Plane are carried over SCTP UDP
S1-C and S1-U interfaces respectively
IP IP
Ethernet Ethernet

S1-C S1-U
TNL stack TNL stack

32 © Nokia 2017
Nokia internal use
Technical Details
LTE-M

LTE BTS IP interfaces

• LTE-M traffic is handled at LTE BTS side by LTE C-Plane and LTE C
C/U
U-Plane IP addresses respectively for LTE-M CP and LTE-M UP U
MBH MBH
• Full flexibility with regard to LTE BTS IP address configuration is
maintained as for normal LTE C-Plane C

or LTE U-Plane operation, i.e.: U

C/U

MBH MBH
- Relevant IP address can be dedicated or shared with any
other LTE plane
- Allocation to transport IP interface or virtual IP interface LTE
CU1
MBH
• In case separate EPC and separate backhaul network is planned
for LTE-M, LTE505 Transport Separation for RAN Sharing can be CU2 LTE-M
used MBH

33 © Nokia 2017
Nokia internal use
Technical Details
LTE-M

Transport QoS (1/2)

• From transport QoS perspective LTE-M traffic receives the
same treatment as LTE C-Plane or LTE U-Plane traffic C
respectively, especially with regard to:
- DSCP marking (single value for C-Plane, U-Plane CU EVC1

marking according QCI to DSCP mapping) MBH

U

- PCP marking
- Allocation to LTE BTS and backhaul nodes transport
queues Single (common)
shaping rate for legacy
• If single C/U transport IP interface is used in LTE BTS LTE and LTE-M

towards core only single (common for legacy LTE and LTE-
M traffic) UL shaping rate can be set
Note: further separation can be achieved
34 © Nokia 2017 with dedicated LTE BTS C-Plane and U-
Nokia internal use Plane IP interfaces deployment
Technical Details C1

LTE-M U1

T1

Transport QoS (2/2) CU

T2
MBH
C2
• If separate transport IP interfaces are used in LTE BTS towards 1
U2
legacy EPC and LTE-M EPC, for example:
Separate (dedicated)
(1) LTE C/U-Plane allocated to single virtual IP interface (CU1), shaping rate per LTE-M core
legacy LTE and LTE-
two transport IP interfaces configured (T1, T2), by IP M
routing configuration LTE C/U-Plane traffic uses T1 and
C1
LTE-M traffic uses T2 2
U1
(2) Two LTE C/U-Plane IP addresses allocated to dedicated
transport IP interfaces (LTE505 Transport Separation for CU1

RAN Sharing required), separate for legacy LTE and LTE-M CU2
MBH
C2
purposes respectively
U2

…dedicated UL shaping rates can be set per legacy LTE and LTE-
M traffic LTE-M core

Note: further separation can be achieved

35 © Nokia 2017 with dedicated LTE BTS C-Plane and U-
Nokia internal use Plane IP interfaces deployment
Technical Details
LTE-M

Transport security (1/2)

• To provide LTE-M traffic encryption over backhaul network
IPsec functionality has to be used (LTE689 LTE IPsec
Support required)
• The same general properties and rules of IPsec
configuration apply to LTE-M encryption, i.e. traffic subject
CU
to encryption is defined basing on IPsec policies with MBH
following criteria for LTE-M (CP / UP respectively):
- source → LTE BTS C-Plane / U-Plane IP address
- destination → MME / S-GW IP addresses
- protocol → SCTP / UDP

Note: further separation can be achieved

36 © Nokia 2017 with dedicated LTE BTS C-Plane and U-
Nokia internal use Plane IP interfaces deployment
Technical Details Legacy LTE + LTE-M in
common IPsec tunnel
LTE-M
MBH
Transport security (2/2) CU

• Dedicated IPsec tunnel for LTE-M:

- In case common EPC is used for legacy LTE and LTE-M
traffic, it is not possible to encrypt LTE-M traffic LTE-M in dedicated IPsec
individually (both legacy LTE and LTE-M can be tunnel

encrypted or not), thus only common IPsec tunnel is MBH

possible CU

- In case dedicated EPC is deployed for LTE-M traffic, also

individual encryption (or lack of thereof) can be applied
to LTE-M, thus dedicated IPsec tunnel is possible
LTE-M core

Note: further separation can be achieved

37 © Nokia 2017 with dedicated LTE BTS C-Plane and U-
Nokia internal use Plane IP interfaces deployment
Technical Details
LTE-M

Core selection
• In case dedicated EPC is deployed for LTE-M traffic, IoT core selection can be based on
dedicated PLMN ID allocated to LTE-M network

PLMN ID = A

CU
LTE EPC
MBH
LTE-M
EPC

PLMN ID = B
Note: further separation can be achieved
38 © Nokia 2017 with dedicated LTE BTS C-Plane and U-
Nokia internal use Plane IP interfaces deployment
Technical Details
LTE-M C1

U1

Transport selection T1 MBH

CU1
• In case dedicated EPC is deployed for LTE-M T2
MBH C2
traffic, transport network selection can be based
on following options: 1 U2

(1) Single LTE C/U-plane IP address (common

for legacy LTE and LTE-M) using virtual IP
interface and two transport IP interfaces, 2 C1

LTE505 not required U1

(2) Two LTE C/U-plane IP addresses (dedicated CU1 MBH

for legacy LTE and LTE-M) using transport IP CU2
interfaces, LTE505 required MBH C2

U2

Note: further separation can be achieved

39 © Nokia 2017 with dedicated LTE BTS C-Plane and U-
Nokia internal use Plane IP interfaces deployment
Technical Details C

LTE-M CU
IPv6
MBH U
1
IPv6 support
• LTE-M traffic at transport level is IP version agnostic, same C1
properties and configuration rules apply to LTE-M as to LTE U1

C/U-Plane IPv6 address use, according to LTE2299 Dual CU

IPv6 MBH
Stack IPv4/IPv6 for S1/X2 feature scope
U2
2 C2
• Exemplary scenarios:
(1) IPv6 backhaul network and core, common EPC used for
legacy LTE and LTE-M traffic C1

U1
(2) IPv6 backhaul network and core, dedicated EPC used for CU1 IPv4 MBH
LTE-M traffic CU1
IPv6 MBH
(3) IPv4/IPv6 dual-stack LTE C/U-Plane IP address U2

configured, e.g.: IPv4 meant for legacy LTE traffic, IPv6 3 C2

meant for LTE-M traffic (LTE505 not required)

Note: further separation can be achieved
40 © Nokia 2017 with dedicated LTE BTS C-Plane and U-
Nokia internal use Plane IP interfaces deployment
 p
Primary SCTP association
S
Technical Details Secondary SCTP association

LTE-M

SCTP multi-homing Common MME, symmetrical SCTP multi-

• If SCTP multi-homing is deployed (at MME side using LTE775 homing

SCTP multi-homing (MME), at LTE BTS side using LTE648 SCTP MBH
Multi-homing, or both) it also applies to LTE-M CP traffic (as LTE C1p C2p

BTS C-Plane IP termination points are used by LTE-M CP) C1s C2s
1
• Both options are supported:
(1) Common MME used for LTE C-Plane and LTE-M CP traffic Dedicated MME, symmetrical SCTP multi-
homing
(2) Dedicated MME used for LTE-M CP traffic
C2p
• Additional C-Plane IP address is meant for redundancy, and not C2s
for traffic differentiation or load balancing C1p

• In case dedicated LTE C-Plane IP addresses pair is required for

C1s MBH C3p

LTE-M CP, LTE505 is mandatory 2 C3s

41 © Nokia 2017
Nokia internal use
LTE18 Transport IoT complex

Interdependencies

Table of contents

<chapter:interdependencies>

42 © Nokia 2017
Nokia internal use
Interdependencies
LTE18 Transport IoT complex

Radio related interdependencies are covered in detail in relevant webNEI materials (focused on
air interface aspects):
• LTE3071 NB-IoT Inband (webNEI link: part 1, part 2)
• LTE3543 NB-IoT Standalone (webNEI link)
• LTE3128 LTE-M (webNEI link: part 1, part 2)

Following slides provide main feature interdependencies for NB-IoT and LTE-M from transport
perspective.

43 © Nokia 2017
Nokia internal use
Interdependencies
LTE3071 NB-IoT Inband

extensions LTE3543 NB-IoT Standalone:

LTE3071 (inband NB-IoT) can be complemented with LTE3543
(standalone NB-IoT) using available radio bandwidth and via
proper cell configuration
 More details available on WebNEI: LTE3543 (link)

LTE3128 LTE-M:
LTE3071 (inband NB-IoT) can be complemented with LTE3128
(LTE-M) using available radio bandwidth and via proper cell
configuration
 More details available on WebNEI: LTE3128 (part 1, part 2)

44 © Nokia 2017
Nokia internal use
Interdependencies
LTE3071 NB-IoT Inband

extensions LTE505 Transport Separation for RAN Sharing:

LTE505 provides dedicated C-Plane IP address for NB-IoT, it is
required whenever separate backhaul network is required for
legacy LTE and NB-IoT traffic
 More details available on WebNEI: LTE505 (link)

LTE689 LTE IPsec Support:

LTE689 provides IPsec support in LTE BTS, allowing for NB-
IoT encryption over backhaul network
 More details available on WebNEI: LTE689 (link)

45 © Nokia 2017
Nokia internal use
Interdependencies
LTE3071 NB-IoT Inband

extensions LTE2299 Dual Stack IPv4/IPv6 for S1/X2:

IPv6 support for LTE C-Plane (including NB-IoT) and U-Plane
traffic
 More details available on WebNEI: LTE2299 (link)

46 © Nokia 2017
Nokia internal use
Interdependencies
LTE3071 NB-IoT Inband

extensions LTE775 SCTP multi-homing (MME):

Additional LTE C-Plane IP termination point supported at
MME/S-GSN side for redundancy purposes, also applicable
to NB-IoT traffic

LTE648 SCTP Multi-homing:

Additional LTE C-Plane IP termination point supported at LTE
BTS side for redundancy purposes, also applicable to NB-IoT
traffic

47 © Nokia 2017
Nokia internal use
Interdependencies
LTE3543 NB-IoT Standalone

prerequisites LTE3071 NB-IoT Inband:

LTE3071 is mandatory prerequisite for LTE3543, as it
introduces base NB-IoT functionality to LTE BTS
 More details available on WebNEI: LTE3071 (part 1, part 2)

48 © Nokia 2017
Nokia internal use
Interdependencies
LTE3543 NB-IoT Standalone

extensions LTE3128 LTE-M:

LTE3543 (standalone NB-IoT) can be complemented with
LTE3128 (LTE-M) using available radio bandwidth and via
proper cell configuration
 More details available on WebNEI: LTE3128 (part 1, part 2)

49 © Nokia 2017
Nokia internal use
Interdependencies
LTE3543 NB-IoT Standalone

extensions LTE505 Transport Separation for RAN Sharing:

LTE505 provides dedicated C-Plane IP address for NB-IoT, it is
required whenever separate backhaul network is required for
legacy LTE and NB-IoT traffic
 More details available on WebNEI: LTE505 (link)

LTE689 LTE IPsec Support:

LTE689 provides IPsec support in LTE BTS, allowing for NB-
IoT encryption over backhaul network
 More details available on WebNEI: LTE689 (link)

50 © Nokia 2017
Nokia internal use
Interdependencies
LTE3543 NB-IoT Standalone

extensions LTE2299 Dual Stack IPv4/IPv6 for S1/X2:

IPv6 support for LTE C-Plane (including NB-IoT) and U-Plane
traffic
 More details available on WebNEI: LTE2299 (link)

51 © Nokia 2017
Nokia internal use
Interdependencies
LTE3543 NB-IoT Standalone

extensions LTE775 SCTP multi-homing (MME):

Additional LTE C-Plane IP termination point supported at
MME/S-GSN side for redundancy purposes, also applicable
to NB-IoT traffic

LTE648 SCTP Multi-homing:

Additional LTE C-Plane IP termination point supported at LTE
BTS side for redundancy purposes, also applicable to NB-IoT
traffic

52 © Nokia 2017
Nokia internal use
Interdependencies
LTE3128 LTE-M

extensions LTE3071 NB-IoT Inband:

LTE3128 (LTE-M) can be complemented with LTE3071 (inband
NB-IoT) using available radio bandwidth and via proper cell
configuration
 More details available on WebNEI: LTE3071 (part 1, part 2)

LTE3543 NB-IoT Standalone:

LTE3128 (LTE-M) can be complemented with LTE3543
(standalone NB-IoT) using available radio bandwidth and via
proper cell configuration
 More details available on WebNEI: LTE3543 (link)

53 © Nokia 2017
Nokia internal use
Interdependencies
LTE3128 LTE-M

extensions LTE4222 Cat-M1: Improved Single-User Peak DL & UL

Throughput with Multiple-HARQ:
LTE3128 (basic LTE-M implementation) throughput per cell
can be extended using LTE4222 functionality
 More details available on WebNEI: LTE4222 (link)

54 © Nokia 2017
Nokia internal use
Interdependencies
LTE3128 LTE-M

extensions LTE505 Transport Separation for RAN Sharing:

LTE505 provides dedicated C-Plane and U-Plane IP addresses
for LTE-M, it is required whenever separate backhaul network
is required for legacy LTE and LTE-M traffic
 More details available on WebNEI: LTE505 (link)

LTE689 LTE IPsec Support:

LTE689 provides IPsec support in LTE BTS, allowing for LTE-M
encryption over backhaul network
 More details available on WebNEI: LTE689 (link)

55 © Nokia 2017
Nokia internal use
Interdependencies
LTE3128 LTE-M

extensions LTE2299 Dual Stack IPv4/IPv6 for S1/X2:

IPv6 support for LTE C-Plane and U-Plane traffic (including
LTE-M)
 More details available on WebNEI: LTE2299 (link)

56 © Nokia 2017
Nokia internal use
Interdependencies
LTE3128 LTE-M

extensions LTE775 SCTP multi-homing (MME):

Additional LTE C-Plane IP termination point supported at
MME/S-GSN side for redundancy purposes, also applicable
to LTE-M CP traffic

LTE648 SCTP Multi-homing:

Additional LTE C-Plane IP termination point supported at LTE
BTS side for redundancy purposes, also applicable to LTE-M
CP traffic

57 © Nokia 2017
Nokia internal use
LTE18 Transport IoT complex

Configuration
Management
Table of contents

<chapter:configuration_management>

58 © Nokia 2017
Nokia internal use
Configuration Management
LTE18 Transport IoT complex

Radio related parameters are covered in detail in relevant webNEI materials (focused on air
interface aspects):
• LTE3071 NB-IoT Inband (webNEI link: part 1, part 2)
• LTE3543 NB-IoT Standalone (webNEI link)
• LTE3128 LTE-M (webNEI link: part 1, part 2)

Following slides provide information regarding main parameters for NB-IoT and LTE-M from
transport perspective.

59 © Nokia 2017
Nokia internal use
Configuration Management
NB-IoT

New NB-IoT parameters are mainly introduced for air interface scope.

• There is one new parameter defining MME/C-SGN support with regard to legacy LTE and NB-
IoT traffic:
MRBTS/LNBTS/LNMME/mmeRatSupport
• 1:Wideband-LTE → given MME supports legacy LTE traffic only (default)
• 2:NB-IoT → given MME supports NB-IoT traffic only
• 3:Wideband-LTE and NB-IoT → given MME supports both legacy LTE and NB-IoT traffic

60 © Nokia 2017
Nokia internal use
Configuration Management
NB-IoT

Already available core parameters are used for NB-IoT purposes

• If MME/C-SGN selection for NB-IoT traffic is based on PLMN ID, then following parameters
should be configured for that purpose:
MRBTS/LNBTS/LNMME/accMmePlmnsList/mcc
MRBTS/LNBTS/LNMME/accMmePlmnsList/mnc
MRBTS/LNBTS/LNMME/accMmePlmnsList/mncLength

61 © Nokia 2017
Nokia internal use
Configuration Management
NB-IoT

Already available transport parameters are used for NB-IoT purposes

• NB-IoT IP termination address is defined in LTE BTS via (IPv4/IPv6 respectively):

MRBTS/LNBTS/FTM/IPNO/cPlaneIpAddress
MRBTS/LNBTS/FTM/IPNO/cPlaneIpv6Address

• NB-IoT dedicated IP address in LTE BTS (LTE505 required) can be defined in LTE BTS via
(IPv4/IPv6 respectively):
MRBTS/LNBTS/FTM/IPNO/addTransportNwIpAddrList/addCPlaneIpv4Address
MRBTS/LNBTS/FTM/IPNO/addTransportNwIpAddrList/addCPlaneIpv6Address

62 © Nokia 2017
Nokia internal use
Configuration Management
NB-IoT

Already available transport parameters are used for NB-IoT purposes (continued)

• In case SCTP dual-homing at LTE BTS needs to be configured (LTE648 required) for NB-IoT,
following parameters can be used (IPv4/IPv6 respectively):
MRBTS/LNBTS/FTM/IPNO/cPlaneIpAddressSec
MRBTS/LNBTS/FTM/IPNO/cPlaneIpv6AddressSec
MRBTS/LNBTS/FTM/IPNO/addTransportNwIpAddrList/addCPlaneIpv4AddressSec
MRBTS/LNBTS/FTM/IPNO/addTransportNwIpAddrList/addCPlaneIpv6AddressSec

63 © Nokia 2017
Nokia internal use
Configuration Management
NB-IoT

Already available transport parameters are used for NB-IoT purposes (continued)

• Other LTE BTS transport functions applicable to NB-IoT traffic are configured via parameters in
relevant MOCs:
IPRT – IPv4 routing
IPRTV6 – IPv6 routing
IPSECC – IPsec
L2SWI – LTE BTS integrated Ethernet switching

64 © Nokia 2017
Nokia internal use
Configuration Management
LTE-M

New LTE-M parameters are mainly introduced for air interface scope.

Already available core parameters are used for LTE-M purposes

• If MME/C-SGN selection for LTE-M traffic is based on PLMN ID, then following parameters
should be configured for that purpose:
MRBTS/LNBTS/LNMME/accMmePlmnsList/mcc
MRBTS/LNBTS/LNMME/accMmePlmnsList/mnc
MRBTS/LNBTS/LNMME/accMmePlmnsList/mncLength

65 © Nokia 2017
Nokia internal use
Configuration Management
LTE-M

Already available transport parameters are used for LTE-M purposes

• LTE-M CP IP termination address is defined in LTE BTS via (IPv4/IPv6 respectively):

MRBTS/LNBTS/FTM/IPNO/cPlaneIpAddress
MRBTS/LNBTS/FTM/IPNO/cPlaneIpv6Address

• LTE-M UP IP termination address is defined in LTE BTS via (IPv4/IPv6 respectively):

MRBTS/LNBTS/FTM/IPNO/uPlaneIpAddress
MRBTS/LNBTS/FTM/IPNO/uPlaneIpv6Address

66 © Nokia 2017
Nokia internal use
Configuration Management
LTE-M

Already available transport parameters are used for LTE-M purposes (continued)

• LTE-M dedicated IP addresses in LTE BTS (LTE505 required) can be defined in LTE BTS via
(IPv4/IPv6 respectively):
MRBTS/LNBTS/FTM/IPNO/addTransportNwIpAddrList/addCPlaneIpv4Address
MRBTS/LNBTS/FTM/IPNO/addTransportNwIpAddrList/addCPlaneIpv6Address
MRBTS/LNBTS/FTM/IPNO/addTransportNwIpAddrList/addUPlaneIpv4Address
MRBTS/LNBTS/FTM/IPNO/addTransportNwIpAddrList/addUPlaneIpv6Address

67 © Nokia 2017
Nokia internal use
Configuration Management
LTE-M

Already available transport parameters are used for LTE-M purposes (continued)

• In case SCTP dual-homing at LTE BTS needs to be configured (LTE648 required) for LTE-M CP,
following parameters can be used (IPv4/IPv6 respectively):
MRBTS/LNBTS/FTM/IPNO/cPlaneIpAddressSec
MRBTS/LNBTS/FTM/IPNO/cPlaneIpv6AddressSec
MRBTS/LNBTS/FTM/IPNO/addTransportNwIpAddrList/addCPlaneIpv4AddressSec
MRBTS/LNBTS/FTM/IPNO/addTransportNwIpAddrList/addCPlaneIpv6AddressSec

68 © Nokia 2017
Nokia internal use
Configuration Management
LTE-M

Already available transport parameters are used for LTE-M purposes (continued)

• Other LTE BTS transport functions applicable to LTE-M traffic are configured via parameters in
relevant MOCs:
IPRT – IPv4 routing
IPRTV6 – IPv6 routing
IPSECC – IPsec
L2SWI – LTE BTS integrated Ethernet switching

69 © Nokia 2017
Nokia internal use
LTE18 Transport IoT complex

Deployment
Aspects
Network graphic boxes Network element boxes
Table of contents

<chapter:deployment_aspects>

70 © Nokia 2017
Nokia internal use
Deployment Aspects
LTE18 Transport IoT complex

Radio related activation steps and scenarios are covered in detail in relevant webNEI materials
(focused on air interface aspects):
• LTE3071 NB-IoT Inband (webNEI link: part 1, part 2)
• LTE3543 NB-IoT Standalone (webNEI link)
• LTE3128 LTE-M (webNEI link: part 1, part 2)

Following slides cover exemplary deployment scenarios for NB-IoT and LTE-M from transport
perspective.

71 © Nokia 2017
Nokia internal use
 Deployment Aspects
LTE18 Transport IoT complex

Typical configuration scenarios covering IoT with main features required (from transport
perspective) are included in the table below:
Scenario #1 #2 #3 #4 #5 #6 #7 #8
NB IoT deployed yes yes yes yes yes yes yes yes
LTE-M deployed no no no yes yes yes yes yes
Separate core for legacy broadband and IoT traffic no yes yes no yes yes yes yes
Separate transport per legacy broadband and IoT traffic no no no no no yes no no
Multiple (two) operators no no yes no no no yes yes
OR Separate transport per each operator n/a n/a yes n/a n/a n/a yes yes
Backhaul traffic encryption no no yes no no no no yes

Features
LTE3071 NB-IoT Inband yes yes yes yes yes yes yes yes
LTE3128 LTE-M no no no yes yes yes yes yes
LTE2 S1 Flex
no no yes no yes yes yes yes
LTE4 RAN Sharing
LTE505 Transport Separation for RAN Sharing no no yes no no yes yes yes
LTE689 LTE IPsec Support no no yes no no no no yes

Highlighted scenarios are covered in detail on later slides

72 © Nokia 2017
Nokia internal use
Deployment Aspects
LTE18 Transport IoT complex

• Due to many possible variations and customer expectations, list of supported scenarios
presented on the previous slide is not complete
• In any scenario shown on previous slide traffic encryption in backhaul network using IPsec can
be enabled or not, also selectively (for some parts of the traffic or specific links)
• Following limitation to traffic separation at transport network layer apply for LTE18:
- Two separate transport networks can be supported, using dedicated set of C-Plane and U-
Plane IP termination interfaces at LTE BTS side in order to:
• Provide separation for legacy broadband and IoT traffic (if single operator is considered)
• Provide separation for each operator’s traffic (if two operators are considered)

73 © Nokia 2017
Nokia internal use
 NB-IoT (C+U plane)
LTE C-plane
Deployment Aspects
LTE18 Transport IoT complex

Scenario #2 details
• summary MME
Scenario #2 LTE BTS
C1
NB IoT deployed yes
LTE-M deployed no C
Separate core for legacy broadband and IoT traffic yes
MBH
Separate transport per legacy broadband and IoT traffic no
Multiple (two) operators no
C2
Separate transport per each operator n/a
Backhaul traffic encryption no
C-SGN
Features
LTE3071 NB-IoT Inband yes
LTE3128 LTE-M no
LTE2 S1 Flex
no
LTE4 RAN Sharing
LTE505 Transport Separation for RAN Sharing no
LTE689 LTE IPsec Support no

74 © Nokia 2017
Nokia internal use
 NB-IoT (C+U plane)
LTE C-plane
Deployment Aspects
LTE18 Transport IoT complex

Scenario #2 details (continued)

• Single transport IP address for LTE C-Plane at LTE BTS MME
(C1) LTE BTS
C2
• MME deployed for legacy broadband traffic, with (C2) C1
MBH
IP address
• C-SGN deployed for NB-IoT traffic, with (C3) IP address C3

• The same PLMN ID used for legacy broadband and

C-SGN
NB-IoT traffic
• Single operator, no transport separation, no backhaul
encryption

75 © Nokia 2017
Nokia internal use
 NB-IoT (C+U plane)
LTE C-plane
Deployment Aspects
LTE18 Transport IoT complex

Scenario #2 main LTE BTS parameters highlighted

MME
LTE BTS LNMME-1 (MME) LNMME-2 (C-SGN)
LTE BTS
C2
mmeRatSupport 1:Wideband-LTE 2:NB-IoT
C1
ipAddrPrim [C2] [C3] MBH
accMmePlmnsList/mcc 11 11
accMmePlmnsList/mnc 22 22 C3

accMmePlmnsList/mncLength 2 2
C-SGN
LTE BTS IPNO
cPlaneIpAddress [C1]

76 © Nokia 2017
Nokia internal use
 LTE-M CP
LTE C-plane
Deployment Aspects
LTE-M UP
LTE18 Transport IoT complex LTE U-plane
NB-IoT (C+U plane)

Scenario #5 details
• summary MME 1

Scenario #5 C2 SGW 1
NB IoT deployed yes
LTE-M deployed yes U2
Separate core for legacy broadband and IoT traffic yes
LTE EPC
Separate transport per legacy broadband and IoT traffic no LTE BTS PLMN ID = 1122
Multiple (two) operators no
Separate transport per each operator n/a C1 MBH C-SGN
Backhaul traffic encryption no U1

C3 MME 2
Features
LTE3071 NB-IoT Inband yes SGW 2
C4
LTE3128 LTE-M yes
LTE2 S1 Flex IoT EPC
yes U4
LTE4 RAN Sharing PLMN ID = 1133
LTE505 Transport Separation for RAN Sharing no
LTE689 LTE IPsec Support no

77 © Nokia 2017
Nokia internal use
 LTE-M CP
LTE C-plane
Deployment Aspects
LTE-M UP
LTE18 Transport IoT complex LTE U-plane
NB-IoT (C+U plane)

Scenario #5 details (continued)

• Single dedicated transport IP address for LTE C-Plane and MME 1

LTE U-Plane respectively at LTE BTS (C1, U1) C2 SGW 1

• MME 1 deployed for legacy broadband traffic, with (C2) IP U2

address LTE EPC

LTE BTS PLMN ID = 1122
• C-SGN deployed for NB-IoT traffic, with (C3) IP address C1 MBH C-SGN
• MME 2 deployed for LTE-M traffic, with (C4) IP address U1

C3 MME 2
• Separate PLMN ID used for legacy broadband (1122) and
IoT (1133) traffic C4 SGW 2

IoT EPC
• Single operator, no transport separation, no backhaul PLMN ID = 1133
U4

encryption

78 © Nokia 2017
Nokia internal use
 LTE-M CP
LTE C-plane
Deployment Aspects
LTE-M UP
LTE18 Transport IoT complex LTE U-plane
NB-IoT (C+U plane)

Scenario #5 main LTE BTS parameters highlighted

MME 1
LTE BTS LNMME-1 LNMME-2 (C- LNMME-3
C2 SGW 1
(MME 1) SGN) (MME 2)
mmeRatSupport 1:Wideband-LTE 2:NB-IoT 1:Wideband-LTE U2

ipAddrPrim [C2] [C3] [C4] LTE EPC

LTE BTS PLMN ID = 1122
accMmePlmnsList/mcc 11 11 11
C1 MBH C-SGN
accMmePlmnsList/mnc 22 33 33
U1
accMmePlmnsList/mncLength 2 2 2
C3 MME 2

C4 SGW 2
LTE BTS IPNO
IoT EPC
cPlaneIpAddress [C1] PLMN ID = 1133
U4

uPlaneIpAddress [U1]

79 © Nokia 2017
Nokia internal use
 LTE-M CP
LTE C-plane
LTE-M UP
Deployment Aspects LTE U-plane
NB-IoT (C+U plane)
LTE18 Transport IoT complex
MME 1
Scenario #7 details C-SGN 1
SGW 1
C2 MME 2
• summary C3
U2 SGW 2
Scenario #7 C4
NB IoT deployed yes LTE EPC
PLMN ID = 1122 U4
LTE-M deployed yes IoT EPC
Separate core for legacy broadband and IoT traffic PLMN ID = 1133
yes
Separate transport per legacy broadband and IoT traffic no
Multiple (two) operators MBH 1
yes
Separate transport per each operator yes CU1
Backhaul traffic encryption
Operator 1
no
LTE BTS
Features
Operator 2 CU2
LTE3071 NB-IoT Inband yes MME 4
LTE3128 LTE-M yes MME 3 MBH 2
LTE2 S1 Flex C7 SGW 4
yes SGW 3
LTE4 RAN Sharing
LTE505 Transport Separation for RAN Sharing C5
yes U7
LTE689 LTE IPsec Support no U5 C-SGN 2
IoT EPC
LTE EPC PLMN ID = 1155
PLMN ID = 1144 C6

80 © Nokia 2017
Nokia internal use
 LTE-M CP
LTE C-plane
LTE-M UP
Deployment Aspects LTE U-plane
NB-IoT (C+U plane)
LTE18 Transport IoT complex
MME 1
Scenario #7 details – Operator 1 C-SGN 1
SGW 1
C2 MME 2
• Single common transport IP address for LTE C-Plane C3

and LTE U-Plane at LTE BTS (CU1)

U2 SGW 2
C4
LTE EPC
• MME 1 deployed for legacy broadband traffic, with PLMN ID = 1122
IoT EPC
U4
PLMN ID = 1133
(C2) IP address
MBH 1
• C-SGN 1 deployed for NB-IoT traffic, with (C3) IP
CU1
address Operator 1
LTE BTS
• MME 2 deployed for LTE-M traffic, with (C4) IP Operator 2 CU2
address MME 4
MME 3 MBH 2
• Separate PLMN ID used for legacy broadband (1122) SGW 3
C7 SGW 4

and IoT (1133) traffic C5

U7
U5 C-SGN 2
IoT EPC
LTE EPC PLMN ID = 1155
PLMN ID = 1144 C6

81 © Nokia 2017
Nokia internal use
 LTE-M CP
LTE C-plane
LTE-M UP
Deployment Aspects LTE U-plane
NB-IoT (C+U plane)
LTE18 Transport IoT complex
MME 1
Scenario #7 details – Operator 2 C-SGN 1
SGW 1
C2 MME 2
• Single common transport IP address for LTE C-Plane C3

and LTE U-Plane at LTE BTS (CU2)

U2 SGW 2
C4
LTE EPC
• MME 3 deployed for legacy broadband traffic, with PLMN ID = 1122
IoT EPC
U4
PLMN ID = 1133
(C5) IP address
MBH 1
• C-SGN 2 deployed for NB-IoT traffic, with (C6) IP
CU1
address Operator 1
LTE BTS
• MME 4 deployed for LTE-M traffic, with (C7) IP Operator 2 CU2
address MME 4
MME 3 MBH 2
• Separate PLMN ID used for legacy broadband (1144) SGW 3
C7 SGW 4

and IoT (1155) traffic C5

U7
U5 C-SGN 2
IoT EPC
LTE EPC PLMN ID = 1155
PLMN ID = 1144 C6

82 © Nokia 2017
Nokia internal use
 LTE-M CP
LTE C-plane
LTE-M UP
Deployment Aspects LTE U-plane
NB-IoT (C+U plane)
LTE18 Transport IoT complex
MME 1
Scenario #7 main LTE BTS parameters highlighted C-SGN 1
SGW 1
Operator 1 C2
C3
MME 2

LTE BTS LNMME-1 (MME LNMME-2 (C- LNMME-3 (MME U2 SGW 2

C4
1) SGN 1) 2)
LTE EPC
mmeRatSupport 1:Wideband-LTE 2:NB-IoT 1:Wideband-LTE PLMN ID = 1122 U4
IoT EPC
PLMN ID = 1133
ipAddrPrim [C2] [C3] [C4]

accMmePlmnsList/mcc 11 11 11 MBH 1
accMmePlmnsList/mnc 22 33 33 CU1
Operator 1
accMmePlmnsList/mncLength 2 2 2
LTE BTS
transportNwId 0 0 0
Operator 2 CU2 MME 4
LTE BTS IPNO MBH 2
MME 3
C7 SGW 4
cPlaneIpAddress [CU1]
SGW 3
uPlaneIpAddress [CU1] C5
U7
U5 C-SGN 2
IoT EPC
LTE EPC PLMN ID = 1155
PLMN ID = 1144 C6

83 © Nokia 2017
Nokia internal use
 LTE-M CP
LTE C-plane
LTE-M UP
Deployment Aspects LTE U-plane
NB-IoT (C+U plane)
LTE18 Transport IoT complex
MME 1
Scenario #7 main LTE BTS parameters highlighted C-SGN 1
SGW 1
Operator 2 C2
C3
MME 2

LTE BTS LNMME-4 (MME LNMME-5 (C- LNMME-6 (MME U2 SGW 2

C4
3) SGN 2) 4)
LTE EPC
mmeRatSupport 1:Wideband-LTE 2:NB-IoT 1:Wideband-LTE PLMN ID = 1122 U4
IoT EPC
PLMN ID = 1133
ipAddrPrim [C5] [C6] [C7]

accMmePlmnsList/mcc 11 11 11 MBH 1
accMmePlmnsList/mnc 44 55 55 CU1
Operator 1
accMmePlmnsList/mncLength 2 2 2
LTE BTS
transportNwId 1 1 1
Operator 2 CU2 MME 4
LTE BTS IPNO MBH 2
MME 3
C7 SGW 4
addTransportNwIpAddrList/addCPlaneIpv4Address [CU2]
SGW 3
addTransportNwIpAddrList/addUPlaneIpv4Address [CU2] C5
U7
addTransportNwIpAddrList/transportNwId 1 U5 C-SGN 2
IoT EPC
LTE EPC PLMN ID = 1155
PLMN ID = 1144 C6

84 © Nokia 2017
Nokia internal use
LTE18 Transport IoT complex

Dimensioning Aspects

Table of contents

<chapter:dimensioning>

85 © Nokia 2017
Nokia internal use
Dimensioning
LTE18 Transport IoT complex

Detailed radio related dimensioning details are covered in relevant webNEI materials (focused on
air interface aspects):
• LTE3071 NB-IoT Inband (webNEI link: part 1, part 2)
• LTE3543 NB-IoT Standalone (webNEI link)
• LTE3128 LTE-M (webNEI link: part 1, part 2)

Following slides provide basic dimensioning assumptions for NB-IoT and LTE-M at transport
network level.

86 © Nokia 2017
Nokia internal use
Dimensioning
LTE18 Transport IoT complex

Detailed dimensioning process requires actual IoT traffic profile inputs, such as:
• Number of IoT devices per cell
• IoT devices activity (number of messages sent per given period)
• Average message length
• Transport protocols overhead
If such data is not available, dimensioning estimates can be based on sustained peak values per
IoT (NB-IoT or LTE-M respectively) values per cell. This simplified approach can be the preferred
option, since overall capacity demand (in terms of backhaul link bandwidth) for IoT traffic is
considered low.

87 © Nokia 2017
Nokia internal use
Dimensioning
NB-IoT

According to LTE3071 based NB-IoT implementation, assuming optimal radio conditions,

maximum NB-IoT traffic throughput per cell at RLC level is:
• 47.4 kbps in downlink
• 155.8 kbps in uplink

Stripping RLC OH and taking into consideration maximum TBS (Transport Block Size) available at
user (NB-IoT device) level of 680 bits, and maximum throughput, corresponding average packet
rate is:
• 64.5 pps in downlink
• 212.2 pps in uplink
…per NB-IoT cell.

88 © Nokia 2017
Nokia internal use
Dimensioning
NB-IoT

Taking into consideration protocol overheads at

TNL, resulting maximum throughput per cell (using NB-IoT CP+UP 85 bytes (680 bits max)

IPv4 and assuming no IPsec encryption) is: S1-AP 24 bytes

• DL: 1432 bits x 64.5 pps → 92.4 kbps SCTP 28 bytes
• UL: 1432 bits x 212.2 pps → 303.8 kbps
IPv4 20 bytes

Ethernet 22 bytes

S1-lite
TNL stack

89 © Nokia 2017
Nokia internal use
Dimensioning
LTE-M: LTE3128 LTE-M

According to LTE3128 based LTE-M implementation, assuming optimal radio conditions,

maximum LTE-M traffic throughput per cell at user level is:
• 262 kbps in downlink
• 561 kbps in uplink

Taking into consideration maximum TBS (Transport Block Size) available at user (LTE-M/Cat M
device) level of 936 bits, and maximum throughput, corresponding average packet rate is:
• 279.9 pps in downlink
• 599.6 pps in uplink
…per LTE-M cell.

90 © Nokia 2017
Nokia internal use
Dimensioning
LTE-M: LTE3128 LTE-M

Taking into consideration protocol overheads at TNL,

resulting maximum throughput per cell (using IPv4 LTE-M UP 117 bytes (936 bits max)

and assuming no IPsec encryption) for LTE-M UP GTP-U 8 bytes

according to LTE3128 implementation is:
UDP 8 bytes
• DL: 1400 bits x 279.9 pps → 391.9 kbps
IPv4 20 bytes
• UL: 1400 bits x 599.6 pps → 839.4 kbps
Ethernet 22 bytes

S1-U
TNL stack

91 © Nokia 2017
Nokia internal use
Dimensioning
LTE-M: LTE4222 Cat-M1 Improved Single-User Peak DL & UL Throughput with Multiple-HARQ

• Cell level maximum throughput values for LTE4222 are the same as for LTE3128.
• Only single UE peak values are improved in LTE4222 (comparing to LTE3128).

92 © Nokia 2017
Nokia internal use
Nokia internal use