SFR LTE-M WS

Woonhee Hwang
Business Development Manager
MN Product Sales
March 26st 2018
1 © Nokia 2016
Content
1. LTE3128 LTE-M

2. LTE3582 LTE-M Enhancements I

3. LTE3597 Cat-M1: 15 & 20 MHz Support

4. LTE3819 IoT: Cat-M and NB-IoT on Same Frequency Carrier

5. LTE3672 Cat-M1: 4T eNB Support

6. Field Test Result – LTE3128,LTE3582

2 © Nokia 2016
LTE3128: Introduction
LTE-M in a nutshell

With LTE-M feature, support for CAT-M UEs is provided to Nokia product

LTE-M, which Aspect 3GPP LTE3128 – LTE-M

stands for LTE-
Coverage +15dB over legacy LTE +5dB of Coverage Enhancement - CE
MTC (Machine
Type Module cost $3-5 Mainly depends on UE vendor

Communication), Battery life +10 years Mainly depends on UE vendor

is an answer for Scalability +50k/cell ~52k CAT-M UEs per cell (3GPP 45.820 TM assumed)
the recent market
UL/DL Bit rate (peak TP) <1Mbit/s ~1Mbit/s
needs
Network upgrade Software upgrade Software upgrade

Spectrum 1.4 MHz (standalone or shared) 1.4 MHz (shared within 10MHz of legacy LTE)

3 © Nokia 2017 Nokia Internal Use

LTE3128: Introduction
LTE-M in a nutshell (CAT-M UE)

CAT-M UE complexity reduction may be achieved due to half duplex, single antenna
usage and smaller bandwidth. At the same time it implies smaller data rates,
leading to smaller energy consumption as well as the lower device price
CAT-M device is
characterized by Release 8 Release 8 Release 12 Release 13 Release 13
lower: Category 4 Category 1 Category 0 Cat-M1 Cat-NB1
complexity, Downlink peak rate 150 Mbps 10 Mbps 1 Mbps 1 Mbps <26 kbps
power Uplink peak rate 50 Mbps 5 Mbps 1 Mbps 1 Mbps <56 kbps
consumption and Number of antennas 2 2 1 1 1
the price Duplex mode Full duplex Full duplex Half duplex Full/Half duplex Half duplex
UE receive bandwidth 20 MHz 20 MHz 20 MHz 1.4 MHz 200 kHz
UE transmit power 23 dBm 23 dBm 23 dBm 20/23 dBm 23 dBm
Modem complexity 100% 80% 40% 20% 15%

4 © Nokia 2017 Nokia Internal Use

LTE3128: Technical Details
Narrowband concept (1/3)

2 slots (1TTI)
F [MHz] …
PRB
… …
6PRBs in frequency dimension (1.4MHz)
Narrowband …
(NB) is new Time [ms]

logical entity Power

LTE-M LTE

In band location, within existing LTE carrier*

introduced
by LTE-M
Shared with legacy LTE, meaning that PRBs can be reused for
legacy, non CAT-M UEs
*Note: For LTE3128, 1.4MHz within 10MHz is possible

5 © Nokia 2017
LTE3128: Technical Details
Narrowband concept (2/3)

1xTTI
At one time only one NB is used by CAT-M UE in DL

NB index for DL transmissions

50PRBs
(10MHz)* are 3GPP allows for different NB for MTC DL control and data
divided by PRB0 and channels (including different NB for Paging/SIB transmission).
PRB49 do
3GPP into not belong LTE3128 supports only one NB in DL  NB7 for both MTC
8 possible
to any NB
data and control channel
narrowbands
(NB0-NB7) CAT-M UE is instructed which NB should be used in SIBs
(information about the NB index of MTC control channel)
PRB
index as well as in DCI - Downlink Control Information (NB
used for UL and DL data transmission)
*Note: LTE3128 is possible to be activated only in cells operating with 10MHz of bandwidth

6 © Nokia 2017
LTE3128: Technical Details
Narrowband concept (3/3)

1xTTI
At one time only one NB is used by CAT-M UE in UL

NB index for UL transmissions

50PRBs
NB6 selection
(10MHz)* are results in no LTE3128 supports only one NB in UL  NB6 for UL
divided by collision with other data transmissions
3GPP into channels

8 possible
narrowbands
(NB0-NB7)
CAT-M UE is instructed which NB should be
used in UL via DCI that carries UL grant

*Note: LTE3128 is possible to be activated only in cells operating with 10MHz of bandwidth

7 © Nokia 2017
LTE3128: Technical Details
Coverage enhancement (CE)

Many MTC devices Coverage enhancement techniques are expected

are expected to to improve the signal penetration into buildings LTE
LTE-M: +≥5dB
be located
indoors LTE-M feature offers the possibility of enabling NoR*=1 1ms
of multi subframe repetitions, resulting in higher
NoR*=2
energy per information bit

CE modes defined by 3GPP

CE mode A (supported by LTE3128)
CE mode A provides relatively modest coverage
enhancement. Maximum Coupling Loss (MCL) is
expected to be improved about at least 5dB. Smaller,
comparing to CE mode B, number of repetitions is
allowed to be used.
CE mode B (not supported)
CE mode B is expected to improve the
MCL about ~15dB, as a result of much
more extensive repetition (up to 2048
repetitions)

Note. LTE3128 supports only static repetitions (single Coverage Enhancement level).

*Note: NoR stands for Number of Repetitions

8 © Nokia 2017
LTE3128: Technical Details
What the repetition is?

The major difference between repetition and HARQ retransmission is related

to the necessity of sending

Repetition HARQ Retransmission

Idea of
Configured number of HARQ retransmission is done only when needed.
repetition is repetitions are always Whenever the latest (re)transmission is not
similar to mandatorily sent acknowledged, HARQ retransmission will take place
(provided that maximum number of HARQ
HARQ Note: Repetitions can be retransmitted as well retransmissions is not reached)
retransmission Both HARQ retransmissions and repetitions are characterized by different RV (Redundancy
Versions). RV sequence {0,2,3,1} defined by 3GPP for LTE is kept for LTE-M as well

Please note that preserving 3GPP wording, repetition means both the initial transmission (1st repetition) as well as
additional ’copies’. When single repetition is to be used, only an initial transmission is sent. In turn, when 4 repetitions
are configured, initial transmission + 3 ’copies’ are sent.

9 © Nokia 2017
LTE3128: Benefits and Gains

LTE-M is a cost-optimized
technology developed to -80% lower module Easy and fast deployment
serve massive number of cost
via SW upgrade
IoT devices (CAT-M)
LTE-M • Support of massive number of simple LTE-M
and cheap CAT-M devices is provided
enables by single feature available after
software upgrade (OPEX/CAPEX savings) Longer battery lifecycle
support of Extended coverage up to

CAT-M
• Provides extended coverage needed +15dB over legacy LTE (more than 10 years)
for reaching of CAT-M devices inside
devices in the buildings and in basements
• Optimized for low volume, infrequent
LTE network transmissions coming from tracking
and controlling IoT devices that do not
require high data rates
• Ensures longer battery lifecycle (>10 years)
Standardized for global
• Provides protection against (malicious)
interference by use of licensed spectrum
use in 3GPP Rel.13

10 © Nokia 2017
LTE3128: Benefits and Gains

LTE-M as introduced by LTE3128

• Support of massive number of simple CAT-M -80% lower module Easy and fast deployment
devices is provided by single feature available cost
after software upgrade (OPEX/CAPEX savings) via SW upgrade
• Provides extended coverage needed for
LTE3128 is the reaching of CAT-M devices inside buildings LTE3128
baseline and in basements
• ~+5dB over legacy LTE at the first stage
feature that • Optimized for low volume, infrequent Extended coverage up to Longer battery lifecycle
ensures transmissions coming from tracking and +15dB over legacy LTE (more than 10 years)
controlling IoT devices that do not require
foundations high data rates
for futher • Ensures longer battery lifecycle (>10 years) Not available Partially available Already available

enhancements • Power saving mode (eDRX Idle) is planned

for FL18 in LTE3125
• Provides protection against (malicious)
interference by use of licensed spectrum Standardized for global
use in 3GPP Rel.13

11 © Nokia 2017
LTE3582: Introduction
LTE-M Enhancements I feature overview

LTE3128 (inband LTE-M) provides support for Cat-M UEs

with 10 MHz legacy LTE host cell with 2Tx2Rx or 2Tx4Rx configuration.

LTE3582 extends LTE3128 functionality by the following features:

• Support of 5MHz legacy host cell,
• Long cell ranges support (up to 107 or 77 km) with
RACH formats 1 and 3. LTE3128 supports only RACH format 0, up to 14.5 km.
• Control Plane optimization with LTE-M data transfer by SRB1 only
• Cat-M support for Distributed Antenna System DAS
• eICIC coexistence with LTE-M
• Validated RRC connected users with LTE3582 is 100
• PUCCH Blanking support for Cat-M host cell

As the basic LTE-M functionality is introduced with LTE3128, this is a prerequisite for LTE3582

12 © Nokia 2017
LTE3582: Technical Details
Location of Narrowbands (NB) in downlink 5 MHz
1xTTI
24

23
At one time only one NB is used by CAT-M UE in DL
NB3
22

NB index for DL transmissions

21

20

25PRBs
19

18

(5MHz) are 17

16
NB2
3GPP allows for different NB for MTC DL control and data
divided by 15

14
channels (including different NB for Paging/SIB transmission).
3GPP into 13
PRB12 does LTE3582 supports only one NB in DL  NB0 for both MTC
data and control channel.
12
not belong
4 possible 11

10
to any NB

narrowbands 9

8
NB1

(NB0-NB3) 7

6 CAT-M UE is instructed which NB should be used in SIBs

5

4
(information about the NB index of MTC control channel)
PRB
3

2
NB0 as well as in DCI - Downlink Control Information (NB
used for UL and DL data transmission)
index
1

Note: Legacy scheduler allocates resources in the RBG (Resource Block Group), with size depending on the LTE BW (2 PRBs for 5 MHz). RBG occupied LTE-M carrier are excluded
from the legacy traffic allocation. NB0 was selected since RGB and NB boundaries are aligned.

13 © Nokia 2017
LTE3582: Technical Details
Location of Narrowbands in uplink 5 MHz
24 PUCCH
23
22
PUCCH
PUCCH
At one time only one NB is used by CAT-M UE in UL

NB3
21 MPUCCH
20

19 NB index for UL transmissions

25PRBs 18 MPUSCH
17 MPUSCH
(5MHz) are 16 MPUSCH
LTE3582 supports only one NB in UL  NB2 for
NB2
15 MPUSCH
divided by 14 MPUSCH
UL data transmissions.
MPUSCH
3GPP into
13
12

4 possible 11

narrowbands
10
NB1

9 PRACH
PRACH
(NB0-NB3)
8
7 PRACH CAT-M UE is instructed which NB should be used in
6 PRACH
5 PRACH UL via DCI that carries UL grant
4 PRACH
Example of
3 MPUCCH
NB0

6PRB PUCCH
2 PUCCH allocation.
1 PUCCH
0 PUCCH

14 © Nokia 2017
LTE3582: Benefits and Gains
LTE-M Enhancements I

New deployments opportunities with introduction of 5MHz BW support for Cat-M

Extended Cat-M cell ranges owing to new PRACH formats 1 and 3

Indoor environment support for Cat-M thanks to DAS support introduction

Extended configuration ranges by support of PUCCH blanking and eICIC

Optimization of core network resources by LTE-M data transfer by SRB1

2.4 W
2.40 W

15 © Nokia 2017
LTE3597: Introduction
Cat-M1: 15 & 20 MHz Support
• LTE3128 feature introduced LTE-M standard in Nokia
networks for 10 MHz BW and the LTE3582: LTE-M
Enhancemenets I extends it with 5 MHz.
• LTE3597 Cat-M1 15 & 20 MHz Support feature enhances
LTE3128 and LTE3582 functionality with additional (15

LTE-M
and 20 MHz) bandwidth support.
• Allocation of Cat-M resources (narrowband – NB) for
LTE3128 / LTE3582 was fixed (depends on the bandwidth
option)
• In LTE3597 it depends on the PCI settings
• LTE3597 introduced new timers to guard Scheduling LTE carrier
Requests, RACH and RRC procedures

16 © Nokia 2017
LTE3597: Technical Details
Location of Narrowbands in downlink 15 MHz
1xTTI
37
36
74

73
At one time only one NB is used by CAT-M UE in DL
35 72
34
NB5 71

NB11
33
32
70

69
NB index for DL transmissions
31 68
30
29
67
NB index is determined based on the parameter
75 PRBs
66
28
27 NB4 65

64 NB10 (actDlPciBasedNarBandCatM) which is set by default to

26
„false” and in such a case NB11 will be selected for the DL
(15MHz) are
63
25
62
24

This parameter was introduced to avoid collisions between

61
23

divided by
60
22
NB3 PRB0, PRB37 and
21
PRB74 do
59

58 NB9 paging (including MPDCCH paging and paging message in

20

3GPP into not belong PDSCH) and when is set to „true” then NB index is selected
57
19
56

based on the table below

18
to any NB 55

12 possible
17
54

NB2
phyCELLID NB index
16

NB8
53
15
52

narrowbands
14
51

phyCELLID mod 10 ≠ 9 𝑵𝑩𝟏𝟏

13
50
12

(NB0-NB11)
49
11
10
NB1
48
phyCELLID mod 10 = 9 𝑵𝑩𝟎
9
8
47

46
NB7
45

CAT-M UE is instructed which NB should be used in SIBs

7
6 44

(information about the NB index of MTC control channel) as

5 43

NB0
4 42

PRB
NB6 well as in DCI - Downlink Control Information (NB used for
3 41

index 2 40

1
0
39

38
UL and DL data transmission)

17 © Nokia 2017
LTE3597: Technical Details
Location of Narrowbands in downlink 20 MHz
1xTTI
49 99
48
47
46 NB7
98
97
96
At one time only one NB is used by CAT-M UE in DL
45
44
95
94
NB15
NB index for DL transmissions
43 93
42 92
41
40 NB6 91
90
39
38
89
88 NB14 NB index is determined based on the parameter
100PRBs
37 87
36 86
(actDlPciBasedNarBandCatM) which is set by default to
35
NB5 85

„false” and in such a case NB15 will be selected for the DL

34 84

(20MHz) are NB13

33 83
32 82
31 81
30 80
This parameter was introduced to avoid collisions between
divided by 29
28
27
NB4
PRBs {0,1,98,99)
79
78
77
NB12 paging (including MPDCCH paging and paging message in
3GPP into
26 76
25
24
do not belong
to any NB
75
74
PDSCH) and when is set to „true” then NB index is selected
23
NB3 73
based on the table below
16 possible
22 72
21 71
NB11
20
19
70
69 phyCELLID NB index
narrowbands
18 68
17
16 NB2 67
66 phyCELLID mod 14 ≠ 13 𝑵𝑩𝟏𝟓
15 65
NB10
(NB0-NB15) phyCELLID mod 14 = 13 𝑵𝑩𝟎
14 64
13 63
12 62
11
10 NB1 61
60
9
8
59
58 NB9 CAT-M UE is instructed which NB should be used in SIBs
(information about the NB index of MTC control channel) as
7 57
6 56
5
4 NB0 55
54
well as in DCI - Downlink Control Information (NB used for
3 53
NB8
UL and DL data transmission)
2 52
1 51
0 50

18 © Nokia 2017
LTE3597: Technical Details
Location of Narrowbands (NB) in downlink 5 MHz
1xTTI
24
23
At one time only one NB is used by CAT-M UE in DL
22
NB3
21 NB index for DL transmissions
20
19 NB index is determined based on the parameter
25PRBs 18
17
(actDlPciBasedNarBandCatM) which is set by default to
„false” and in such a case NB0 will be selected for the DL
(5MHz) are 16
15
NB2
This parameter was introduced to avoid collisions between
divided by 14
13
paging (including MPDCCH paging and paging message in
PRB12 does not
3GPP into 12
11
belong
PDSCH) and when is set to „true” then NB index is selected
based on the table below
to any NB
4 possible 10
9 phyCELLID NB index
NB1
narrowbands 8
7 phyCELLID mod 2 ≠ 0 𝑵𝑩𝟎
(NB0-NB3) 6
5
phyCELLID mod 2 = 0 𝑵𝑩𝟑
4
3 CAT-M UE is instructed which NB should be used in SIBs
PRB 2
NB0 (information about the NB index of MTC control channel) as
index
1
well as in DCI - Downlink Control Information (NB used for
0
UL and DL data transmission)

19 © Nokia 2017
LTE3597: Technical Details
Location of Narrowbands in downlink 10 MHz
1xTTI

At one time only one NB is used by CAT-M UE in DL

49
48
47
46
45 NB7
44
43
42
41
NB index for DL transmissions
40
NB6
39
38 NB index is determined based on the parameter
50PRBs
37
36
35
(actDlPciBasedNarBandCatM) which is set by default to
34
NB5 „false” and in such a case NB7 will be selected for the DL
(10MHz) are 33
32
31

This parameter was introduced to avoid collisions between

divided by
30
29
28
27 NB4 paging (including MPDCCH paging and paging message in
3GPP into
26
25
24 PDSCH) and when is set to „true” then NB index is selected
based on the table below
23

8 possible NB3
22
21 PRB0 and PRB 49 do
phyCELLID NB index
20
19 not belong

narrowbands to any NB
18
17
16
15 NB2 phyCELLID mod 6 ≠ 5 𝑵𝑩𝟕
(NB0-NB7)
14
13
12
11
phyCELLID mod 6 = 5 𝑵𝑩𝟎
10
NB1
9
8
7
CAT-M UE is instructed which NB should be used in SIBs
6
5
(information about the NB index of MTC control channel) as
4
3 NB0 well as in DCI - Downlink Control Information (NB used for
2
1
0
UL and DL data transmission)

20 © Nokia 2017
LTE3597: Technical Details
Location of Narrowbands in downlink for 5, 10, 15 and 20 MHz

The determination of NB for downlink transmission also affects 10MHz

(LTE3128) and 5MHz (LTE3582) channels bandwidth.

NB index for DL transmissions Channel NB

phyCELLID
bandwidth index
When actDlPciBasedNarBandCatM is set to
phyCELLID mod 2 ≠ 0 𝑵𝑩𝟎
„true” then NB index is selected based on 5
phyCELLID mod 2 = 0 𝑵𝑩𝟑
phyCellID.
phyCELLID mod 6 ≠ 5 𝑵𝑩𝟕
Different configurations are possible 10
phyCELLID mod 6 = 5 𝑵𝑩𝟎
depending on the selected bandwidth phyCELLID mod 10 ≠ 9 𝑵𝑩𝟏𝟏
15
channel. phyCELLID mod 10 = 9 𝑵𝑩𝟎
phyCELLID mod 14 ≠ 13 𝑵𝑩𝟏𝟓
20
phyCELLID mod 14 = 13 𝑵𝑩𝟎

21 © Nokia 2017
LTE3597: Technical Details
Location of Narrowbands in uplink 15 MHz

13
Blank PUCCH

halfMaxPucchResourceSize > 13*

74 PUCCH Blank PUCCH
Blank PUCCH

NB index for UL transmissions

73 PUCCH Blank PUCCH
Blank PUCCH

0< halfMaxPucchResourceSize
Blank PUCCH

7 < halfMaxPucchResourceSize
72 PUCCH

NB11
PUCCH Blank PUCCH

NB11
NB11
71 PUCCH Blank PUCCH
PUCCH
70 PUCCH PUCCH
PUCCH
69
68
67
MPUCCH

MPUSCH
PUCCH
PUCCH
PUCCH
PUCCH Allocation of NB in UL depends on the utilization
PUCCH resource which are calculated by
PUCCH
66 MPUSCH MPUCCH
PUCCH

NB10
NB10

NB10
65 MPUSCH
PUCCH
halfMaxPucchResourceSize = roundup (PUCCH +
75PRBs
64 MPUSCH
63 MPUSCH
PUCCH
MPUCCH
MPUCCH + Blank PUCCH)/2.
62 MPUSCH
61 MPUSCH
MPUSCH

(15MHz) are 60 MPUSCH

MPUSCH
MPUSCH

NB9
59 NB9
MPUSCH
Depending on their size NB index is selected based

NB9
58 MPUSCH
MPUSCH

divided by
57 MPUSCH
MPUSCH
MPUSCH
on the table below
56
MPUSCH

3GPP into

NB3-NB8
NB3-

NB3-NB8
NB8

19-55

12 possible 18
17 PRACH
PRACH
Half of PUCCH resource size:
NB index for
MPUSCH
NB2

16

narrowbands PRACH
15

NB2
14 NB2 PRACH
13
PRACH PRACH 0 < halfMaxPucchResourceSize ≤ 7 𝑵𝑩𝟏𝟎
(NB0-NB11)
12 PRACH
PRACH
11 PRACH
PRACH MPUCCH
7 < halfMaxPucchResourceSize ≤ 13 𝑵𝑩𝟗
NB1

10 PRACH
PRACH PUCCH
9 PRACH
PRACH PUCCH

NB1
halfMaxPucchResourceSize > 13 𝑵𝑩𝟗
NB1

8 PRACH
7 PRACH PRACH PUCCH
6 PRACH MPUCCH PUCCH
5 MPUCCH PUCCH PUCCH
Example of PUCCH PUCCH
NB0

4 PUCCH
3 PUCCH
10 PRB PUCCH
PUCCH
NB0 PUCCH
Blank PUCCH CAT-M UE is instructed which NB should be used in
NB0

2 PUCCH
PUCCH Blank PUCCH

UL via DCI that carries UL grant

1 PUCCH PUCCH Blank PUCCH
0 PUCCH allocation. Blank PUCCH Blank PUCCH
Blank PUCCH Blank PUCCH
Blank PUCCH

22 © Nokia 2017
LTE3597: Technical Details
Location of Narrowbands in uplink 20 MHz

8
Blank PUCCH

14
Blank PUCCH

halfMaxPucchResourceSize > 14*

99 PUCCH
Blank PUCCH

NB index for UL transmissions

Blank PUCCH
98 PUCCH

0< halfMaxPucchResourceSize
Blank PUCCH Blank PUCCH

8 < halfMaxPucchResourceSize
97 PUCCH PUCCH Blank PUCCH

NB15
96 PUCCH Blank PUCCH
PUCCH

NB15
Blank PUCCH

NB15
95 PUCCH
PUCCH
94
93
MPUCCH
PUCCH
PUCCH
PUCCH
PUCCH Allocation of NB in UL depends on the utilization
PUCCH
PUCCH resource which are calculated by
92
91 MPUSCH MPUCCH PUCCH
90 MPUSCH PUCCH

NB14
halfMaxPucchResourceSize = roundup (PUCCH +

NB14
NB14
100PRBs
89 MPUSCH
PUCCH
88 MPUSCH
PUCCH
87 MPUSCH
86 MPUSCH
MPUCCH
MPUCCH + Blank PUCCH)/2.
(20MHz) are
MPUSCH
85 MPUSCH
84 MPUSCH
MPUSCH
Depending on their size NB index is selected based
MPUSCH

NB13
83 NB13
MPUSCH

NB13
divided by
82 MPUSCH
MPUSCH
81 MPUSCH
80 MPUSCH
MPUSCH
MPUSCH on the table below
3GPP into
NB12
NB3-

NB3-NB12
NB3-NB12
20-79

16 possible 19
18 PRACH Half of PUCCH resource size:
NB index for
MPUSCH
PRACH

narrowbands
17
NB2

16 PRACH
NB2

NB2
15
14
PRACH
PRACH 0 < halfMaxPucchResourceSize ≤ 8 𝑵𝑩𝟏𝟒
(NB0-NB15)
13 PRACH
PRACH
8 < halfMaxPucchResourceSize ≤ 14 𝑵𝑩𝟏𝟑
12 PRACH
11 PRACH MPUCCH
NB1

PRACH
10 PRACH PRACH
PUCCH
NB1

9 PRACH PUCCH
halfMaxPucchResourceSize > 14 𝑵𝑩𝟏𝟑

NB1
PRACH
8 PRACH PRACH PUCCH
7 PRACH MPUCCH PUCCH
6 PRACH
PUCCH
5 MPUCCH Example of PUCCH
NB0

PUCCH PUCCH
10 PRB
CAT-M UE is instructed which NB should be used in
4 PUCCH
NB0

PUCCH
3 PUCCH
PUCCH
2 PUCCH PUCCH PUCCH
PUCCH NB0 Blank PUCCH

UL via DCI that carries UL grant

Blank PUCCH
1 PUCCH allocation. Blank PUCCH Blank PUCCH
0 PUCCH Blank PUCCH Blank PUCCH
Blank PUCCH Blank PUCCH
Blank PUCCH

23 © Nokia 2017
LTE3597: Technical Details
Location of Narrowbands in uplink 5 MHz
24 PUCCH 24 PUCCH

halfMaxPucchResourceSize > 5*
23 PUCCH 23 PUCCH NB index for UL transmissions

0< halfMaxPucchResourceSize
22 PUCCH 22 PUCCH

NB3
NB3
21 MPUCCH 21 PUCCH Allocation of NB in UL depends on the utilization
20 20 PUCCH
19 MPUCCH
PUCCH resource which are calculated by
19
halfMaxPucchResourceSize = roundup (PUCCH +
25PRBs 18
17
MPUSCH
MPUSCH
18
17
MPUSCH
MPUSCH MPUCCH + Blank PUCCH)/2.
(5MHz) are MPUSCH 16 MPUSCH

NB2
16
NB2
15 MPUSCH 15 MPUSCH Depending on their size NB index is selected based
divided by 14 MPUSCH 14
13
MPUSCH
MPUSCH on the table below
13 MPUSCH
3GPP into 12 12

4 possible 11 11

10
PRACH
PRACH
10 NB index for
narrowbands Half of PUCCH resource size:

NB1
9 PRACH
NB1

9 PRACH MPUSCH
8 PRACH
8 PRACH
(NB0-NB3) 7 PRACH
7
6
PRACH
PRACH
0 < halfMaxPucchResourceSize ≤ 5 𝑵𝑩𝟐
6 PRACH
5 PRACH
5 MPUCCH halfMaxPucchResourceSize> 5 𝑵𝑩𝟐
4 PRACH Example of
4 PUCCH
3 MPUCCH 6PRB PUCCH
3 NB0 PUCCH
CAT-M UE is instructed which NB should be used in
NB0

allocation. 2 PUCCH
2 PUCCH
1 PUCCH
1 PUCCH UL via DCI that carries UL grant
0 PUCCH
0 PUCCH

24 © Nokia 2017
LTE3597: Technical Details
Location of Narrowbands in uplink 10 MHz

halfMaxPucchResourceSize > 13*

7

13
49 PUCCH Blank PUCCH Blank PUCCH
Blank PUCCH Blank PUCCH
48 PUCCH

NB index for UL transmissions

Blank PUCCH Blank PUCCH

0< halfMaxPucchResourceSize
47 PUCCH PUCCH Blank PUCCH

7 < halfMaxPucchResourceSize

NB7
NB7
46 PUCCH Blank PUCCH

NB7
PUCCH
45 PUCCH PUCCH
PUCCH
44 MPUCCH PUCCH
PUCCH

Allocation of NB in UL depends on the utilization

43 PUCCH
PUCCH
42 MPUSCH PUCCH
MPUCCH
41 MPUSCH PUCCH

NB6
PUCCH resource which are calculated by
PUCCH

NB6
40 MPUSCH

NB6
39 MPUSCH PUCCH
38 MPUSCH MPUCCH

halfMaxPucchResourceSize = roundup (PUCCH +

MPUSCH

50PRBs
37 MPUSCH
36 MPUSCH MPUSCH
MPUSCH MPUSCH

NB5
35
34 MPUSCH MPUSCH
MPUCCH + Blank PUCCH)/2.

NB5
NB5
MPUSCH

(10MHz) are
33 MPUSCH
MPUSCH MPUSCH
32
MPUSCH

Depending on their size NB index is selected based

31
30

divided by 29

NB5
on the table below
28

NB4
NB4

27

3GPP into
26
25
24
23

8 possible Half of PUCCH resource size:

NB index for
22
NB3

NB3
21

NB4
20
MPUSCH
narrowbands
19
18

0 < halfMaxPucchResourceSize ≤ 7 𝑵𝑩𝟔

17
PRACH
16
NB2

PRACH
NB2

(NB0-NB7)
15
PRACH

NB2
7 < halfMaxPucchResourceSize ≤ 13 𝑵𝑩𝟓
14
PRACH PRACH
13 PRACH
PRACH
12 PRACH
PRACH

halfMaxPucchResourceSize > 13 𝑵𝑩𝟓

11 PRACH MPUCCH
PRACH
10 PRACH PUCCH
NB1

PRACH
NB1

9 PRACH PUCCH

NB1
PRACH
8 PRACH PUCCH
MPUCCH
7 PRACH PUCCH
PUCCH
6 PRACH Example of PUCCH
PUCCH

CAT-M UE is instructed which NB should be used in

5 MPUCCH PUCCH
4 PUCCH 10 PRB PUCCH
PUCCH
NB0

PUCCH
NB0

NB0
3 PUCCH
PUCCH
Blank PUCCH

UL via DCI that carries UL grant

2 PUCCH PUCCH Blank PUCCH
Blank PUCCH
allocation.
Blank PUCCH
1 PUCCH Blank PUCCH Blank PUCCH
0 PUCCH Blank PUCCH Blank PUCCH

25 © Nokia 2017
LTE3597: Benefits and Gains
Cat-M1: 15 & 20 MHz Support

New deployments opportunities with introduction of 15 and 20MHz BW

support for Cat-M

Flexible downlink narrowband allocation depends on PCI settings

Extended Cat-M support for PUCCH blanking in UL (with LTE1130 feature)

Safer operations with timers guarding RACH and RRC reconfiguration

procedures, which helps to avoid a state mismatch between the UE and
the eNodeB.

26 © Nokia 2016
LTE3819: Introduction
LTE Cat-M and NB-IoT by 3GPP Release 13

There are two different standardized solutions used for low-cost and IoT communication. The 3GPP Release 13
introduces two types of LTE IoT devices Cat-1 and Cat NB1

Cat-M NB-IoT
Technical info
LTE3128: LTE-M LTE3071: NB-IoT In-band

UE receive bandwidth 1.4 MHz 200 kHz

Number of UE antennas 1 1

Duplex mode Half duplex Half duplex

UE transmit power 20/23 dBm 23 dBm

Better for a larger amount of data (hundreds of kb). Usage More suitable for devices requiring very little data (tens of kb).
Data rate
example: healthcare wearables Usage example: temperature sensors
Preferred for non-time-critical devices (delay-tolerant Good when bigger latency (few seconds) is not an issue.
Latency
applications). Usage example: wearables Usage example: metering devices
Network resource
6 PRB 1 PRB
utilization

Table: 3GPP Release 13 LTE IoT technologies shows technical parameters of Cat-M and NB-IoT solutions

27 © Nokia 2017
LTE3819: Introduction
LTE-M and NB-IoT on same frequency carrier
• As the services brought by NB-IoT are complementary to those one of
LTE-M, coexistence of both LTE-M and NB-IoT on the same carrier in NB-IoT
eNB enriches the variety of IoT applications within the same cell.
‒ LTE3819 introduces support of LTE-M and NB-IoT coexistence on same host LTE
cell.

NB-IoT
LTE-M
• Before this feature, the inband NB-IoT and LTE-M are mutually exclusive
in one cell, although they can be enabled in different cells in one eNB.
• Feature is applicable over 10 MHz LTE carrier BW with FSMF and FZM
deployment LTE carrier
Inband
‒ LTE-M and NB-IoT coexistence for 10 MHz over AirScale comes with LTE4040 LTE-M and NB-IoT on same cell
• No new feature activation flag is introduced for LTE3819.
When LTE-M & NB-IoT are activated by the respective feature activation
flags, LTE3819 is activated.
• Configuration of NB-IoT PRB cannot overlap with LTE-M PRBs.

28 © Nokia 2017 Nokia Internal Use

LTE3819: Technical Details
Simplification of this feature

• 10MHz cell only (other bandwidths (5, 15 and 20 MHz) will be covered by LTE4040
Cat-M1 and NB-IoT on same LTE cell – Phase II comes with FL18)
• Downlink NB-IoT PRB position (PRB #19 and PRB #30)
• The narrowband #7 (PRB 43-48) will be used for Cat-M PDSCH regarding DL PRB
allocation
• FSMr3 and FZM are supported for the first phase with LTE3819, AirScale support will
come also with LTE4040 Cat-M1 and NB-IoT on same LTE cell – Phase II)
• UL NB-IoT PRB configurations
• FSMr3, 10MHz, with PUCCH blanking (1-4 PRBs on each side)
• FSMr3, 10MHz, w/o PUCCH blanking

29 © Nokia 2017 Nokia Internal Use

LTE3819: Technical Details
Uplink PRB allocation for Cat-M and NB-IoT coexistence within the same cell – case 1

• Uplink NB-IoT PRB selected to avoid collision with PRACH, PUCCH and Cat-M narrowband in host cell
• PUCCH blanking is not supported  (blankedPucch = 0)
• Supported configuration:
• NB-IoT UL RB is allocated in the inner PUSCH area
• Cat-M UL PUSCH is NarrowBand #6 (PRB 37-42) set by LTE3128 feature
• MPUCCH is adjacent to legacy PUCCH

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
NPRACH Inner PUSCH Cat-M Uplink
PUCCH and MPUCCH PUCCH and MPUCCH
AreaArea
for NB-IoT UL PRB Inner.
for NB-IoT UL PRBPUSCH

LTE system Eligible setting of inbandPRBIndexUL

blankedPucch setting Cat-M UL PRB index
bandwidth NB-IoT inband UL PRB index
10 MHz blankedPucch = 0 [13, .., 36] NarrowBand #6 (PRB 37-42)

30 © Nokia 2017 Nokia Internal Use

LTE3819: Technical Details
Uplink PRB allocation for Cat-M and NB-IoT coexistence within the same cell – case 2

• Uplink NB-IoT PRB selected to avoid collision with PRACH, PUCCH and Cat-M narrowband in host cell
• Normal PUCCH and PUCCH blanking will be supported, PUCCH blanking (1-3 PRBs in each side)
• Supported configuration:
• 1/2/3 upper and 1/2/3 lower PRBs are blanked (blankedPucch = 2/4/6)
• NB-IoT UL RB is allocated in the lower or upper blanked PUCCH area
• Cat-M uplink PUSCH is Narrowband #5 (PRB 31-36) set by LTE3128 feature
• MPUCCH is adjacent to legacy PUCCH
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
Out. PUSCH NPRACH Inner
Inner PUSCH
PUSCH Cat-M Uplink Out. PUSCH
PUCCH and MPUCCH PUCCH and MPUCCH

Area for NB-IoT Area for NB-IoT

UL PRB Out. Eligible setting of inbandPRBIndexUL UL PRB Out.
blankedPucch setting Cat-M UL PRB index
PUSCH LTE system NB-IoT inband UL PRB index PUSCH
bandwidth
blankedPucch = 2 [0, 49]
10 MHz NarrowBand #5
blankedPucch = 4 [0, 1, 48, 49]
(PRB 31-36)
blankedPucch = 6 [0, 1, 2, 47, 48, 49]

31 © Nokia 2017
Please note: picture shows example for blankedPucch = 4
Nokia Internal Use
LTE3819: Technical Details
Uplink PRB allocation for Cat-M and NB-IoT coexistence within the same cell – case 3

• Uplink NB-IoT PRB selected to avoid collision with PRACH, PUCCH and Cat-M narrowband in host cell
• Normal PUCCH and PUCCH blanking will be supported, PUCCH blanking (4 PRBs in each side)
• Supported configuration:
• 4 upper and 4 lower PRBs are blanked (blankedPucch = 8)
• NB-IoT UL RB is allocated in the part of lower or upper blanked PUCCH area
• Cat-M uplink PUSCH is Narrowband #5 (PRB 31-36) set by LTE3128 feature
• MPUCCH is adjacent to legacy PUCCH

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
Out. PUSCH NPRACH Inner PUSCH Cat-M Uplink Out. PUSCH
PUCCH and MPUCCH PUCCH and MPUCCH

Area for NB-IoT Area for NB-IoT

UL PRB Out. Eligible setting of UL PRB Out.
blankedPucch
PUSCH LTE system inbandPRBIndexUL Cat-M UL PRB index PUSCH
setting
bandwidth NB-IoT inband UL PRB index
10 MHz
blankedPucch = 8 [0, 1, 2, 3, 46, 47, 48, 49] NarrowBand #5 (PRB 31-36)
32 © Nokia 2017
 LTE3819: Technical Details
Downlink PRB allocation for Cat-M and NB-IoT coexistence within the same cell

• The selection of NB-IoT anchor PRB location in downlink needs to avoid conflict with:
• Cat-M narrowband resources for downlink MPDSCH and MPDCCH
• SIB1-BR hopping and MPDCCH Paging PCI
Mod 6
NBA NBB

(depends on Cat-M configuration, PCI mod 6) 0

1
NB0
NB1
NB5
NB6
2 NB2 NB7
3 NB5 NB0
4 NB6 NB1
• NB-IoT PRB position without conflict: 5 NB7 NB2

• Only PRB 19 or PRB 30 is employed for inband NB-IoT downlink PRB when coexisting with Cat-M.
• The Narrowband #7 (PRB 43 - 48) will be used for Cat-M MPDSCH as Cat-M LTE3128.

NB-IoT anchor PRB (candidate) SIB1-BR / MPDCCH Paging narrowband PBCH Cat-M reserved narrowband

PCI 0,3 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
PCI 1,4 PRB # 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
PCI 2,5 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
Narrowband # NB0 NB1 NB2 NB3 NB4 NB5 NB6 NB7
LTE system
3 MHz 5 MHz 10 MHz 15 MHz 20 MHz
bandwidth
4, 9, 14, 19, 24, 29,
PRB indices for 2, 7, 12, 17, 22, 27,
33 © Nokia 2017 4, 9, 14, 19, 30, 35 34, 39, 44, 55, 60,
NPSS/NSSS 2, 12 2, 7, 17, 22 32, 42, 47, 52, 57,
40, 45 65, 70, 75, 80, 85,
transmission 62, 67, 72
90, 95
 LTE3819: Technical Details
Downlink PRB allocation for Cat-M and NB-IoT coexistence within the same cell

• Legacy LTE scheduler allocates resources in the RBG (Resource Block Group), with size depending
on the LTE BW. The whole RBG with NB-IoT carrier is excluded from the legacy traffic allocation.
RBG size for 10MHz is 3 PRB (2 for anchor PRB48/49).
• Power of the non-used PRBs in the RBG can be used for NB-IoT carrier boosting.
• NB-IoT on PRB 19 is preferred for cells with PCI modulo 6 equal to (0,3,1,4) to avoid NB-IoT RBG
overlapping with LTE-M SIB1-BR
• NB-IoT on PRB 30 is preferred for cells with PCI modulo 6 equal to (1,4,2,5)

NB-IoT anchor PRB (candidate) SIB1-BR / MPDCCH Paging narrowband PBCH Cat-M reserved narrowband

PCI 0,3 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
PCI 1,4 PRB # 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
PCI 2,5 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
Narrowband # NB0 NB1 NB2 NB3 NB4 NB5 NB6 NB7
RBG

34 © Nokia 2017
LTE3819: Technical Details
NB-IoT Downlink power boosting

• Legacy NB-IoT solution uses power of unused PRB within RBG for power boosting.
NB-IoT
10MHz example Power boost

NB-IoT
RBG=3

• In some conditions (PRB 19 and PCI modulo 6 equal to (2,5) or PRB 30 and PCI modulo 6 equal to
(0,3)) NB-IoT RBG overlaps with LTE-M SIB1-BR, what means that only part of the power from
unused PRB can be used for power boosting.
• Remaining power deficit to reach desired NB-IoT boosting will be solved by reduction of the wide
band host cell power.(mostly it concerns 6dB boost)
NB-IoT anchor PRB (candidate) SIB1-BR / MPDCCH Paging narrowband PBCH Cat-M reserved narrowband

PCI 0,3 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
PRB #
PCI 2,5 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
Narrowband # NB0 NB1 NB2 NB3 NB4 NB5 NB6 NB7
RBG

35 © Nokia 2017
LTE3819: Technical Details
Active users and Radio Admission Control (RAC)

LTE3819 LTE-M and NB-IoT coexistence

Existing rules The total number of Cat-M and wideband LTE active UEs is limited to 600 per LTE host 10
remains MHz cell. The total number of NB-IoT UEs is limited to 280 per NB-IoT cell.
unchanged. In case NB-IoT UEs request admission, the sum of all UE types (Cat-M, legacy, CA guest,
NB-IoT) may not exceed 840 as specified for LTE3071.

Legacy and
LTE-M users
share the
same pool,
while NB-IoT
users are
defined in a
separate
pool.

36 © Nokia 2017
LTE3819: Benefits and Gains
Cat-M and NB-IoT on Same Frequency Carrier

• Feature LTE3819 allows to deploy both CAT-M and NB-IoT on same frequency carrier
– Coexistence causes simplified network configuration  one cell 10 MHz instead of two
overlapping cells serves both Cat-M and NB-IoT devices
– HW savings – less RF modules and antennas are required
– NB-IoT and CAT-M coexistence enables use of the variety IoT applications within the same cell

Legacy LTE UE

CAT-M UE  same frequency carrier

NB-IoT UE

37 © Nokia 2017
 LTE3672: Introduction
Cat-M1 4Tx eNB support

• This feature enables support of Cat-M on hosting cell with 4TX

antennas (4T4R).
Main benefit will be expected for existing 4Tx sites, where Cat-M
deployment was not possible before. Additionally 2Tx sites with Cat-M
can be extended to 4Tx, if needed.

Cat-M UE

Legacy LTE UE
Nokia Internal Use
38 © Nokia 2017
LTE3672: Technical Details
h1
Cat-M1 4Tx eNB support

• Since Cat-M UEs are equipped with just

h2
1 antenna, there is no MIMO (spatial multiplexing)
support.
LTE3128: 2x1 transmission mode
• For the host cell equipped with 4Tx only 4way TX
diversity with Transmission Mode 2 is possible for h1
Cat-M UE (4x1 transmission scheme).
• Host cell can operate in 4Tx diversity, 4x2 Closed h2
loop MIMO or 4x4 Closed loop MIMO
h3
• 4Tx with TM9 is not supported in the legacy cell
with Cat-M activated.
h4

LTE3672: 4x1 transmission mode

39 © Nokia 2017
LTE3672: Technical Details
Cat-M1 4Tx eNB support

• 4Tx transmission scheme yields increased amount number

antenna reduced
CRS of CRS
of REs reserved for CRS comparing to 2Tx solution port
number reserved
bits in
number QPSK
• It means that less REs available for actual data RE

(MPDSCH, MPDCCH). 1 1 8 32
2 2 16 64
• This effect counteracts gains which are brought by
4Tx 4 4 24 96
SUPPORTED
2Tx MPDSCH 4Tx MPDSCH

RE carrying the PDCCH

RE carrying the Cell specific Reference Signal (RS)
RE carrying the PDSCH

40 © Nokia 2017
LTE3672: Benefits and Gains
Cat-M1 4Tx eNB support

• Primary benefit of LTE3672 is to allow Cat-M deployment for legacy host cell
working in 4 Tx mode.
• Gain from Cat-M operating in 4Tx diversity mode is side effect.
- Tx diversity gain of 4Tx over 2Tx is small, additionally reduced by overhead of CRS for 4Tx transmission.
- Main component of the improved performance comes from the doubled transmission power
of 4 Tx scheme comparing to the 2Tx reference*.

Cat-M UE Cat-M UE

Note: Improved performance can be observe assuming same power of TXs before and after.

41 © Nokia 2017
Field Results: LTE- M (LTE3128, LTE3582)

Test cluster (customer field test):

• 3 sites, Airscale / BW 10Mhz / Band 13 (700MHz)
• LTE-M activated and tested during maintenance window (24.00 – 06.00
o’clock)
• LTE-M stationary testing were performed in the following locations
(CC,MC, and CB) :
• cell-center ( RSRP <= -60 dBm, SINR >= 20)
• middle-cell ( RSRP -80…-86 dBm, SINR 14..16 )
• cell border ( RSRP <= -100 dBm, SINR <= 10)

42 © Nokia 2017
 LTE3128 / LTE3582
Field test results: TP Stationary Performance Tests with Legacy UE with/without CATM feature
activated

• The DL and UL FTP results of each UE at different test

locations are shown, respectively. Results is average over 3
min per run.
• All runs are performed during MT windows where low number
of traffic users are observed. Based on UL / DL t-put results,
no impact on Legacy UEs is observed when CAT-M feature is
activated.
Achieved t-put results on Legacy LTE UE in the field (in CC, MC, CB RF) are
O.K. However, maximum t-put could not be achieved by the test UE as there
were more than 10 commercial UEs present in the same cell.
43 27/03/2018 © Nokia
Confidential
 LTE3128 / LTE3582
Single CAT-M UE Peak DL&UL throughput with RL=1, 2, 8 and mixed2 repetitions performance Tests

• The DL and UL FTP results is based on UE best RF possible location. Results is average over 3 min per run.
• Measured UL/DL results are aligned with the expected results (*)

Note(*): only RL=1 (i.e.Rep0), RL=2 and RL=8 were tested in the lab. Field UL/DL results are O.K.
Approx. 15% deviation is originated from measurement methodology. E2E application layer UDP t-put measured in the lab.
Field test is done FTP and measurement figures are obtained using QXDM /QCAT PDCP level t-put which contains also overhead.

44 27/03/2018 © Nokia
Confidential
 LTE3128 / LTE3582
CAT-M UEs in different RF conditions - (CC, MC, CB) DL t-put with 0, 2, 8, mixed2 repetitions performance tests

• The DL FTP results of each UE at different test locations are shown, respectively.
• Results is average over 3 min per run.
• DL results are aligned with the expected results (* see remarks in slide#10)

45 27/03/2018 © Nokia
Confidential
 LTE3128 / LTE3582
CAT-M UEs in different RF conditions - (CC, MC, CB) UL t-put with 0, 2, 8, mixed2 repetitions performance tests

• The UL FTP results of each UE at different test locations are shown, respectively.
• Results is average over 3 min per run.
UL results are aligned with the expected results. Note(*): only RL=1 (i.e.Rep0), RL=2 and RL=8 were tested in the lab. Field UL/DL results are O.K.
Approx. 15% deviation is originated from measurement methodology. E2E application layer UDP t-put measured in the lab.
Field test is done FTP and measurement figures are obtained using QXDM /QCAT PDCP level t-put which contains also overhead.

46 27/03/2018 © Nokia
Confidential
 LTE3128 / LTE3582
CAT-M UE DL t-put, simultaneous single carrier legacy DL t-put, measure CAT-M impact on legacy DL t-put

• The purpose of this test is check is to measure DL legacy throughput while a CAT-M users is doing DL data transfer at the same time.
• All runs are performed during Maintenance windows where low number of traffic users are observed.
• Based on DL results, measured t-put on Cat-M1 UE is aligned with expected results. However, impact of active Cat-M1 Call to t-put of
Legacy UE is not visible due to the fact that maximum Legacy t-put could not be achieved by the test UE in the field as there were 8
commercial UEs present in the same cell and sharing DL resources. However, impact of active Cat-M1 call to Legacy UE is validated in
the lab tests.

Conclusion: Based on DL results, measured t-put on Cat-M1 UE is aligned with expected results. However, impact of active Cat-M1 Call to
t-put of Legacy UE is not visible due to the fact that maximum Legacy t-put could not be achieved by the test UE in the field as there
were 8 commercial UEs present in the same cell and sharing DL resources. However, impact of active Cat-M1 call to Legacy UE is
validated in the lab tests.

47 27/03/2018 © Nokia
Confidential
 LTE3128 / LTE3582
Summary of CAT-M multiple UEs in different RF conditions - (CC, MC, CB) DL and UL t-put with RL=1 (no
repetitions) Performance Tests

• UL / DL FTP t-put results of each UE at different test locations are shown above, respectively. Results is average over 3 min per run.
• Measured UL/DL results are aligned with the expected results.

48 27/03/2018 © Nokia
Confidential
CAT-M cell coverage drive, DL t-put mobility CC to CB DL FTP with Repetition 0, mixed 2, 2, and 8
The purpose of this test is to verify the CAT-M UE coverage with different repetitions.
For Rep8 repetition, data drop at path loss of 140dB or RSRP of -117 dBm at vehicle speed traveling constantly at 35
mile/hr. All other Reps drop around path loss of 138 dB or -115 dBm

NOTE: Coverage Enhancement target value MCL ~ 149-150 dB could not be achieved in the field due to interference caused by neighbor sites.
As permission of powering neighbor sites OFF was not given by customer, single CAT-M cell without interference could not be tested !

49 27/03/2018 © Nokia
Confidential
Test result summary
- Field test results
• Activation of LTE-M feature was successful.
• Various single test steps performed for LTE-M feature in 1-3 sites
Paging of CAT-M1 could not be tested due to missing EPC support.
Coverage Enhancement target value MCL ~ 149-150 dB could not be achieved in the field due to interference caused by
neighbor sites.
• CAT-M related KPIs were evaluated in the test cluster. CAT-M related counters / KPIs are
successfully tested and several KPI formulas are changed. 2x t-put related KPIs ( Cat-M cell
tput) cannot reflect measured t-put on the UE due to 15 min granularity period if call session
time < 15 min.

• 4 x different repetition profiles used : RL1, RL2, RL8 and combination of RL1 and RL2 (i.e.
mixed2)

50 27/03/2018 © Nokia
Confidential