Extra High Value Feature

NETWORK
ENGINEERING
LTE2479 - 256 QAM in downlink
LTE3073 – 256 QAM extensions
LTE3502/LTE3020 – 256 QAM in Downlink for Flexi Zone BTS on FDD-LTE/TD-
LTE SR001921 - LTE 18A new feature
LTE4064 - 256 QAM enhancements implementation in SRAN
LTE4054 – Dynamic Power Back-off
Network Engineering Information
• Doc ID: 5a55f32747230100125247da
• Version: 1.8
• Wojciech Wascinski
• Status: Approved
• 06-09-2018

Please, always check the latest version of NEI slides.

1 © Nokia 2018 Nokia Internal Use
Disclaimer

• Please note that the NEI materials are for internal use only. If they shall be used as a source for
the customer presentation, it is mandatory to align the contents with the Product Management
and/or local sales teams at first!
• The results of simulations shown in this presentation are examples only. They demonstrate
trends (not absolute values) expected after feature activation. The presented simulations should
be analyzed with respect to the assumptions taken. They may differ from results achievable in
real networks.
• This NEI slide deck reflects the state of the feature/solution as it is at the moment of the NEI
slide deck release and is being updated up to C5 (release available) milestone.

2 © Nokia 2018 Nokia Internal Use

Revision history and metadata

Document ID: 5a55f32747230100125247da

Document location: https://webnei.emea.nsn-net.net/#/webnei/5a55f32747230100125247da/1
Organization: MN CS NetEng

Version Description of Changes Date Doc Owner Doc Status Reviewed by Approv Approval Date
er

0.9 New document created, ready for internal review. 17-10-2016 Krzysztof Draft
Golebiewski

1.0 Comments collected during internal and external review included 07-11-2016 Krzysztof Approved Mandatory internal and external reviewers Jacek 07-11-2016
Golebiewski Kotwinski

1.1 Some corrections done in e.g. Benefits and Gains section. Some minor 14-11-2016 Krzysztof
changes are included. Golebiewski

1.2 Some corrections have been done in line with comments collected 16-11-2016 Krzysztof
during trainings sessions. Golebiewski

1.3 Updated information about power back-offs (slides 24-26). Findings 18-11-2016 Krzysztof
from some email discussions are included. Golebiewski

1.4 Update of 256QAM slide set with LTE3502. 15-02-2017 Krzysztof LTE3502 reviewed by Mani Iyer and Konrad
Update of LTE3073 slides (correction done for parameters Golebiewski Liedtke
dl256QAMGoodChQualPerc and dl256QAMBadChQualPerc which
are vendor parameters)

1.5 Dimensioning Aspects section was added. 07-04-2017 Krzysztof LTE3020 reviewed by Mani Iyer and Konrad Jacek 10-04-2017
LTE3020 feature is covered Golebiewski Liedtke Kotwinski

1.6 Some corrections throughout the whole document. Update of 11-05-2017 Krzysztof Approved
counters/KPIs in line with FL17 changes. Golebiewski

1.7 LTE4064 from FL18A added 14-08-2018 Wojciech Wascinski Approved Katarzyna Rybianska, Prabhjinder Boparai,
Adam Pomianek

1.8 LTE4054 from FL18A added 06-09-2018

3 © Nokia 2018 Nokia Internal Use

 NETWORK
ENGINEERING

256 QAM in downlink

features view

4 © Nokia 2018 Nokia Internal Use

256 QAM in downlink features view
Roadmap overview LTE3020 & LTE3502 bring basic support
for 256QAM modulation in downlink for
FZM in TDD and FDD

LTE3073 enhances basic 256QAM concept

with possibility to switch between new and
legacy MCS/CQI tables. Also, internal
conversion of MCS/CQI provided for fair
xL16A UE treatment xL18A

LTE2479 brings basic support xL17A LTE4054 introduces dynamic power

back-off to be applied per TTI depending
for 256QAM modulation in
on share of 256QAM transmissions
downlink for Macro BTS
LTE4064 enhances LTE3073 so that UE is
initially configured with legacy MCS/CQI
tables, legacy parameter range is
extended and new one introduced for
faster initial transition to 256QAM (if
required)
5 © Nokia 2018 Nokia Internal Use
 Extra High Value Feature

NETWORK
ENGINEERING

LTE2479 - 256 QAM in

downlink
6 © Nokia 2018 Nokia Internal Use
LTE2479 - 256 QAM in downlink
Table of contents

Introduction Technical Inter – Benefits and Configuration Deployment

Details dependencies Gains Management Aspects
Motivation and Feature Detailed Functionality Simulation, Lab and Field Parameters and
Interdependencies with Activation, Configuration
Overview Description Findings Parameterization
other features and Examples, Fault Mgmt,
functions Scenarios Trial Area
1

Dimensioning fALU Performance Compliance

Aspects equivalents Aspects Aspects
Dimensioning Impacts and Nokia vs. ALU solution Counters and KPIs, 3GPP, IETF, ETSI
Examples comparison Feature Impact Analysis
and Verification

7 © Nokia 2018 Nokia Internal Use

LTE2479 - 256 QAM in downlink

Introduction

Table of contents

<chapter:introduction>

8 © Nokia 2018 Nokia Internal Use

Introduction
Background - modulation

Modulation is the process of

conveying a message, for
example a bit stream, inside Data stream (message) Modulated signal
signal that can be physically to be transmitted over (example of 16QAM)
transmitted. the air
symbol
Modulation
• Modulation order determines, … …
how many …0000110110010000…
bits per symbol are encoded 0000 1101 1001 0000
- QPSK – 2 bits per symbol
- 16QAM – 4 bits per symbol
- 64QAM – 6 bits per symbol
The higher the modulation order, the more bits are
- 256QAM – 8 bits per symbol
encoded by one modulation symbol

9 © Nokia 2018 Nokia Internal Use

Introduction
Background - modulation
TTI (DL)
In LTE, the smallest part of the
PDCCH PDSCH
Resource grid is the Resource
f Single Resource Element (RE)
Element – 1 RE, that is, 1 OFDM
symbol x 1 subcarrier Physical Resource Block (PRB)
Cell-specific RS (port 0)
• One modulation symbol is Cell-specific RS (port 1)
transmitted on one resource Resource Element Group (REG)

element = 4 REs

• The higher the modulation order, t

the more bits are transmitted over
one resource element, i.e. the
higher spectral efficiency is …
experienced
TTI

10 © Nokia 2018 Nokia Internal Use

Introduction
Background - modulation

Q
Each modulation symbol has its Q

representation on constellation diagram

ISD
• The higher the modulation order, the more I I

modulation symbols need to be reflected

on the constellation diagram
QPSK 16 QAM
• The more modulation symbols needClickto be to add text
reflected, the smaller inter-symbol distance
Q Q
(ISD) is experienced
- Smaller distance between adjacent
modulation symbols leads to higher I I
SINR requirement, as the risk of
incorrect symbol detection is higher
64 QAM 256 QAM

11 © Nokia 2018 Nokia Internal Use

Introduction
Before & after LTE2479

Before After
• No 256QAM possible for DL transmission • 256QAM can be used for DL transmission
• UDP DL peak rates up to: • Improved spectral efficiency
− FDD: ~561,6Mbps (4CC CA, 4x2MIMO, 4x20MHz, 64QAM)
• Gain numbers depend on 256QAM area probability and
− TDD: ~327Mbps (3CC CA, 2x2MIMO, 3x20MHz, TDD frame availability of 256QAM capable UEs
config 2, 64QAM)
• UDP DL peak rates up to:
− FDD: ~748Mbps (4CC CA, 4x2 MIMO, 4x20MHz, 256QAM)
− TDD: ~436Mbps (3CC CA, 2x2 MIMO, 3x20MHz, TDD
frame config 2, 256QAM)

64QAM 16QAM 256QA

M
16QAM
QPSK 64QAM
QPSK

Note: Theoretical peak DL TP with other assumptions can be found here.

12 © Nokia 2018 Nokia Internal Use

LTE2479 - 256 QAM in downlink

Technical Details

Table of contents

13 © Nokia 2018 Nokia Internal Use

Technical Details Sales information
Dependency Table (LTE) BSW/ASW ASW

Release information
Release/version RL release eNodeB NetAct
FDD LTE FDD-LTE 16A FL16A NetAct 16.8
TDD LTE TD-LTE 16A TL16A NetAct 16.8
Flexi Zone Micro (FZM/FZP) N/A N/A N/A
Flexi Zone Controller (FZC) N/A N/A N/A
Single RAN SRAN17 SBTS17 NetAct 17.2

Release information – general

HW & IOT HW requirements MME SAE GW UE Specified by 3GPP
• FSMF/FSIH System Module (from FDD/TD-LTE16A)
• FSMF System Module (from SRAN17) Cat. 11,12
• AirScale System Module (from DL Cat.≥11*
3GPP TS 36.213
FDD/TD-LTE/SRAN17)

Note: *Selected UE of listed categories support 256QAM. Support of 256QAM is mandatory for UEs of DL category 13-14.
Support of 256QAM is reported by UE itself. More details on slide #.
14 © Nokia 2018 Nokia Internal Use
Technical Details
256QAM requirements

Downlink transmission with 256QAM

modulation can happen provided that:
1) LTE2479 is activated in the cell
2) UE is 256QAM capable
2 5 6Q A
M
64QAM 16QAM
3) UE is in good radio conditions QPSK

(sufficient DL SINR)
SINR
256QAM capable UE

The higher the modulation order, the

higher SINR is required

15 © Nokia 2018 Nokia Internal Use

Technical Details
256QAM general requirements [1/2]

Downlink transmission with 256QAM

modulation can happen provided that:
1) LTE2479 is activated in the cell
• Parameter LNCEL:
actModulationSchemeDl is set to
’256QAM’

One has to select the highest allowed

DL modulation scheme in the cell

16 © Nokia 2018 Nokia Internal Use

Technical Details
256QAM general requirements

2) UE is 256QAM capable Initial context setup procedure

UE reports dl-256QAM-r12 as …
RRC:UECapabilityEnquiery

supported for the band(s), in which RRC:UECapabilityInformation

UE is currently being served …

- UE is of category 11 or 12
• UE of DL category 11 and onwards
- Note that support of 256QAM is mandatory
for UEs of DL category 13-14

17 © Nokia 2018 Nokia Internal Use

Technical Details
256QAM radio condition requirements [1/3]

UEs in good radio conditions (UE reports SINR=20dB

CQI that reflects sufficient DL SINR) can
benefit from 256QAM 16QAM 64QAM 256QAM
• Propagation channel distorts the amplitude
and the phase of initially transmitted signal
• The more modulation symbols (different
phase and amplitude combinations) the
smaller distance between adjacent modulation
symbols
• The smaller distance between adjacent
modulation symbols, the higher SINR is The more modulation symbols are possible
required to decode the signal correctly to be used by eNB, the higher SINR is
required for correct decoding

18 © Nokia 2018 Nokia Internal Use

Technical Details
256QAM radio condition requirements [2/3]

Good radio conditions give a 256QAM

chance of efficient 256QAM
usage SINR = 20dB SINR=30dB
The smaller the SINR, the
higher the probability of
modulation symbol
misdetection

19 © Nokia 2018 Nokia Internal Use

Technical Details
256QAM radio condition requirements [3/3]

Link Level simulation results Modulation order vs DL SINR

have proven high SINR
requirement MCS20-27:256QAM

Assuming 10% of BLER, eNB has a

MCS20 ~ 25dB
chance to use 256QAM, when DL
SINR is higher than ~25dB
− Achieved results strongly depend on
chosen simulation conditions

Source: 4GMax Link Level simulations

Simulation conditions: 10MHz, 4x2MIMO TM4, 2layers (RANK=2), EPA5, 10% BLER, EVM not considered

20 © Nokia 2018 Nokia Internal Use

Technical Details
256QAM capable UE handling [1/2]
Modulation Code rate x 1024 Efficiency
When LTE2479 is activated, 256QAM capable UEs CQI
index legacy* new** legacy* new** legacy* new**
are handled based on new, dedicated 3GPP table for 0 Out of range

CQI index in DL Link Adaptation 1 QPSK QPSK 78 78 0.1523 0.1523

2 QPSK QPSK 120 193 0.2344 0.3770
• New CQI index table reflects presence of 256QAM modulation 3 QPSK QPSK 193 449 0.3770 0.8770

• New CQI index table is characterized by coarser granularity due to 4 QPSK 16QAM 308 378 0.6016 1.4766
5 QPSK 16QAM 449 490 0.8770 1.9141
addition of 256QAM
6 QPSK 16QAM 602 616 1.1758 2.4063
− 256QAM capable UEs may experience smaller data rates and lower 7 16QAM 64QAM 378 466 1.4766 2.7305
transmission efficiency at the cell edge, when QPSK is used, 8 16QAM 64QAM 490 567 1.9141 3.3223
comparing to the case when legacy tables would be used 9 16QAM 64QAM 616 666 2.4063 3.9023

• Applicability of the new CQI index table is indicated by eNB 10 64QAM 64QAM 466 772 2.7305 4.5234
11 64QAM 64QAM 567 873 3.3223 5.1152
during initial access, SCell addition, Handover or RRC
12 64QAM 256QAM 666 711 3.9023 5.5547
reestablishment (via CQI-ReportConfig IE: CQI-ReportConfig- 13 64QAM 256QAM 772 797 4.5234 6.2266
v12x0:altCQI-Table-r12 = allSubframes) 14 64QAM 256QAM 873 885 5.1152 6.9141
• Note: UEs that do not support 256QAM are handled according to 15 64QAM 256QAM 948 948 5.5547 7.4063

the legacy CQI index table

New CQI index table, specified by 3GPP,
defines higher efficiency levels
Note: * 3GPP 36.213 Table 7.2.3-1 (non-256QAM relevant configuration)
** 3GPP 36.213 Table 7.2.3-2 (256QAM relevant configuration)

21 © Nokia 2018 Nokia Internal Use

Technical Details MCS index [IMCS]
Modulation Order [Qm] TBS Index [ITBS]

256QAM capable UE handling [2/2] 0

legacy*
2 (QPSK)
new**
2 (QPSK)
legacy*
0
new**
0
1 2 (QPSK) 2 (QPSK) 1 2
2 2 (QPSK) 2 (QPSK) 2 4
3 2 (QPSK) 2 (QPSK) 3 6
When LTE2479 is activated, 256QAM capable UEs 4 2 (QPSK) 2 (QPSK) 4 8
5 2 (QPSK) 4 (16QAM) 5 10
are handled based on new, dedicated 3GPP table for 6 2 (QPSK) 4 (16QAM) 6 11
7 2 (QPSK) 4 (16QAM) 7 12
MCS/TBS index in DL Link Adaptation 8 2 (QPSK) 4 (16QAM) 8 13
9 2 (QPSK) 4 (16QAM) 9 14
•New MCS/TBS index mapping table reflects presence of 256QAM 10 4 (16QAM) 4 (16QAM) 9 15
11 4 (16QAM) 6 (64QAM) 10 16
modulation 12 4 (16QAM) 6 (64QAM) 11 17
13 4 (16QAM) 6 (64QAM) 12 18
•New MCS/TBS index table is characterized by coarser granularity due 14 4 (16QAM) 6 (64QAM) 13 19
to addition of 256QAM 15 4 (16QAM) 6 (64QAM) 14 20
16 4 (16QAM) 6 (64QAM) 15 21
− 256QAM capable UEs may experience smaller data rates and lower 17 6 (64QAM) 6 (64QAM) 15 22
18 6 (64QAM) 6 (64QAM) 16 23
transmission efficiency at the cell edge, when QPSK is used, comparing 19 6 (64QAM) 6 (64QAM) 17 24
to the case when legacy tables would be used 20 6 (64QAM) 8 (256QAM) 18 25
21 6 (64QAM) 8 (256QAM) 19 27
•Applicability of the new MCS/TBS index table is indicated by eNB in 22 6 (64QAM) 8 (256QAM) 20 28
the same way as new CQI index table (via altCQI-Table-r12 IE = 23 6 (64QAM) 8 (256QAM) 21 29
24 6 (64QAM) 8 (256QAM) 22 30
allSubframes) 25 6 (64QAM) 8 (256QAM) 23 31
26 6 (64QAM) 8 (256QAM) 24 32
•Note: UEs that do not support 256QAM are handled according to the 27 6 (64QAM) 8 (256QAM) 25 33
28 6 (64QAM) 2 (QPSK) 26/26A
legacy MCS/TBS index table 29 2 (QPSK) 4 (16QAM)
reserved
•256QAM capable UE that uses new CQI & MCS-TBS index mapping 30 4 (16QAM) 6 (64QAM) reserved
31 6 (64QAM) 8 (256QAM)
tables is called 256QAM configured UE
Note: * 3GPP 36.213 Table 7.1.7.1-1 (non-256QAM relevant configuration)
** 3GPP 36.213 Table 7.1.7.1-1A (256QAM relevant configuration)
22 © Nokia 2018 Nokia Internal Use
Current Setting
dl256QamDeactChQualThr (McsNew)=13 dl256QamReactChQualThr (McsLegacy)= 22

SINR= 21 TBS = 20
SINR= 18, TBS = 18 dl256QamReactChQualThr
McsLegacy=20 McsLegacy= 22 (18 to 24)
dl256QamDeactChQualThr McsNew= 15
McsNew=13 (9 to 15)

23 © Nokia 2018 Nokia Internal Use

Recommended Setting perDl256QamChQualEst = from 60s to 10 (1 …240)
dl256QamDeactChQualThr (McsNew)=13 dl256QamReactChQualThr (McsLegacy)= 24

SINR= 25, TBS = 22

dl256QamReactChQualThr
McsLegacy= 24 (18 to 24)
SINR= 18, TBS = 18 McsNew= 17
McsLegacy=20
dl256QamDeactChQualThr
McsNew=13 (9 to 15)

24 © Nokia 2018 Nokia Internal Use

Technical Details
Throughput performance with the new and legacy CQI and MCS-TBS index tables [1/2]

256QAM capable UE is configured

with the new CQI index tables Efficiency 5.5547 (the highest
acc. to the legacy CQI tables)

According to the new CQI table, CQI 12-15 are

assumed for 256QAM. Those values correspond
to the highest CQI (15) according to the legacy
CQI table

For 256QAM 3GPP specified efficiency 5.5547

and higher. UE is able to handle this efficiency
level, when measured DL SINR corresponds to
CQI=15, according to the legacy CQI tables.

25 © Nokia 2018 Nokia Internal Use

Technical Details
Throughput performance with the new and legacy CQI and MCS-TBS index tables [2/2]
256QAM capable UE is configured with
the new MCS-TBS index tables
TBS index vs DL SINR
Table size is left the same - there is the New TBS index sizes for 256QAM capable
same number of 32 MCS indexes UE that is in good radio condition. Higher
data ratesare possible to be achieved
256QAM addition required replacement of
some of existing indexes with the new
No impact is expected
settings for 256QAM scheme
Coarser granularity of new tables (QPSK-
256QAM) may lead to worse cell edge Coarser MCS table may lead to worse performance
when 256QAM UE is at the cell edge (when QPSK is used)
performance
- lower DL TP will be experienced by
256QAM capable UE comparing to
the case in which legacy tables
would be used instead Note: Simulation conditions are the same as on slide #.

New 3GPP MCS-TBS mapping tables may affect cell

edge DL TP of 256QAM capable UEs*
*Improvement of cell edge performance is a subject of LTE3073 feature
26 © Nokia 2018 Nokia Internal Use
 Configuration Management
New/Related parameters

Abbreviated name Full name Description Range and step Default

LNCEL:iniDl256QamChQualEst Initial decision period for channel Initial decision period for channel quality estimation. 1,2,3,5,7,10,15, 1
w!

quality estimation 30,60,120,240

Ne

LNCEL:perDl256QamChQualEst Decision period for channel Decision period for channel quality estimation. 1,2,3,5,7,10,15, 60
quality estimation 30,60,120,240

LNCEL:actDl256QamChQualEst Activate channel quality This parameter activates the channel quality 0 (false), 1 (true) 0
monitoring for 256QAM usage monitoring for 256QAM usage.

MCS threshold for deactivating MCS threshold for deactivating 256QAM for the UE. from 9 to 15, step 1 13
256QAM for the UE. Value refers Value refers to legacy MCSs so it needs to be
LNCEL:dl256QamDeactChQualThr
to legacy MCSs so it needs to be converted eNB internally.
converted eNB internally.
MCS threshold for reactivating MCS threshold for reactivating 256QAM for the UE. from 18 to 24 step 1 22
LNCEL:dl256QamReactChQualThr 256QAM for the UE. Value refers Value refers to legacy MCSs.
to legacy MCSs.

All above-mentioned parmaeter are On-line modifiable

27 © Nokia 2018 Nokia Internal Use

Technical Details
Error Vector Magnitude and the power back-off

Error Vector Magnitude (EVM) is B

A Q
a measure that determines how far are the
transmitted modulation symbols from its ideal •
representation on the constellation diagram *
00001000 *
allowed EVM
Imperfections of the transmitter lead to the
deviations in modulated signal
B
* *
The higher the modulation order, the more I
stringent the EVM is
For 256QAM EVM, defined by 3GPP, should
not be higher than 3,5% A Error vector

Error Vector Magnitude

28 © Nokia 2018 Nokia Internal Use

Technical Details
Error Vector Magnitude and the power back-off

To comply with stringent 3GPP requirements regarding EVM,

usage of Power back-off is recommended*
The higher the transmitted power, the higher the EVM is
experienced
− Transmitted power is proportional to the load in the TTI
− EVM <= 3,5% might not be guaranteed when the Power
Amplifier (PA) works with the maximum supported output
power
•When the allowed EVM is exceeded, worse radio conditions Exceeded EVM value
are experienced, what in turn leads to the lower probability of
256QAM usage reduces the chance of
256QAM usage
Note: *Usage of power back-off is not mandatory. No checks are done by Nokia eNB, if recommended power back-off
value is configured. Nevertheless, if no or too low power back-off value is used, customer proceeds at own risk!

29 © Nokia 2018 Nokia Internal Use

Technical Details
Power back-off
The goal of the power back-off is to reduce the maximum
configured output power with the value that will guarantee the
PA power [W]
EVM not higher than 3,5% for 256QAM transmission Max PA power
Power back-off value depends on the PA characteristic as well as used Power back-off
configuration (it depends on, among others, number of carriers per PA)
Power back-off is applicable when PA that is handling the cell where 256QAM
is used, is allowed to use the maximum supported power (for LTE,
LNCEL:pMax is set to maximum supported PA power)
- When cell with 256QAM enabled is handled by PA that is shared between
multiple carriers and sum of all carriers powers is equal to maximum
supported power of the PA, the recommended power back-off value defined
for multiple carrier scenario should be used for each carrier handled by this
PA
Before power After power
back-off is used back-off is used

30 © Nokia 2018 Nokia Internal Use

Technical Details
Recommended power back-offs

Recommended values of power back-offs are results of tests that are performed with Nokia Radio
units. Power back-off value for already tested radios are always included in Customer
Documentation
Recommended power back-off value Recommended power back-off value
[dB] [dB]
Radio Radio
Module Module
Single Carrier Dual Carrier Single Carrier Dual Carrier

FRMD 1.0 1.5 FHCA 0.7 -

FXFB 0.1 - FRLB 0.9 1.5

FXDB 1.2 1.3 FRGQ 1.0 -

FRGS 0.9 0.8 FHDB 0.4 0.8

The most optimal value
FRHC 1.0 1.4 FHGB 0.2 -

FRMC 0.7 - FRBG 0.7 0.8

of power back-off is an
FRMF 0.7 1.2 FHFB 0.7 0.8 outcome of test
FXED 1.0 1.3

Note: New radios and new configurations are constantly being tested. The most up to date power back-off values are always
available in the Customer Documentation (see more details in backup).

31 © Nokia 2018 Nokia Internal Use

Technical Details
256QAM hardware support

256QAM feature support has been initially brought by

FL/TL16A and it was possible to be activated only on
FSMF/FSIH
Feature is possible to be run on AirScale starting from FL/TL/SRAN17
SRAN17 provided support for FSMF as well
Feature is possible to be used with all radio types (Metro RRH, RFM,
RRH)
− Whenever the cell with LTE2479 enabled is handled by PA that is
configured to run with the maximum supported power, a power back-off
should be used (if recommended) Depending on the Radio
type, different power back-
off might be needed

32 © Nokia 2018 Nokia Internal Use

Technical Details
256QAM UE support

256QAM feature is already supported by some UE

terminals, like for example:
Netgear Aircard 810S
Samsung Galaxy S7 edge
LG G5
Xiaomi Mi 5

There are already some commercial

UEs on market that could benefit
from 256QAM feature

33 © Nokia 2018 Nokia Internal Use

LTE2479 - 256 QAM in downlink

Interdependencies

Table of contents

<chapter:interdependencies>

34 © Nokia 2018 Nokia Internal Use

Interdependencies

prerequisites LTE793 - Support of 16 QAM (DL)

LTE43 - Support of 64 QAM in DL
From FL16A onwards, one has to select the highest allowed DL
modulation scheme. This is equal to activation of all lower
modulation schemes as well. When actDlModulationScheme =
'256QAM', 64QAM, 16QAM and QPSK will be used as well,
depending on the radio conditions

35 © Nokia 2018 Nokia Internal Use

Interdependencies

extensions Carrier Aggregation features

LTE1089, LTE1332, LTE1562, LTE1803, LTE1804,
LTE2531 and others
MIMO features
LTE568, LTE569, LTE1987 and others
In conjunction with Carrier Aggregation (4CC) and higher order MIMO
(4x2), when 256QAM is enabled on each carrier, the peak DL UDP TP
up to ~750Mbps is expected.

Note: The applicability of 256QAM is decided on a per-component-carrier (CC) basis

36 © Nokia 2018 Nokia Internal Use

Interdependencies

limitations LTE1117 LTE MBMS:

LTE1117 can be activated in parallel with LTE2479, however
no 256QAM support is provided for MBMS related signalling
(MCCH).
LTE819 DL inter-cell interference generation:
LTE819 can be activated in parallel with LTE2479.
Nevertheless DL interference generation using 256QAM is not
supported.

37 © Nokia 2018 Nokia Internal Use

LTE2479 - 256 QAM in downlink

Benefits and Gains

Table of contents

<chapter:benefits_and_gains>

38 © Nokia 2018 Nokia Internal Use

Benefits and Gains
Peak TP evaluation

LTE2479 is expected to significantly increase downlink peak UE throughput for

256QAM capable UEs that uses MCS20-MCS27
UDP peak throughput up to ~748Mbps (FDD)
Improved spectral efficiency

Before (64QAM) After (256QAM)

FDD TDD FDD TDD
562Mbps 327Mbps 748Mbps 436Mbps

33% higher DL
Assumptions: peak TP
FDD: 4CC CA, 4x2 MIMO, 4x20MHz
TDD: 3CC CA, 2x2 MIMO, 3x20MHz, TDD frame config 2

39 © Nokia 2018 Nokia Internal Use

Benefits and Gains
MoRSE Simulation scenarios parameterization

Parameter Value Description

Layout 3GPP Macro according to TR 25.814 (ISD=500m)
LTE2479 Duplex mode FDD
was Transmission modes TM4 - 2x2 MIMO, 4x4 MIMO

a subject of Operational band 2.1 GHz

Bandwidth 10 MHz
a Output power Macro eNB 46dBm, 256QAM power back-off 1.2dB; UE: 23dBm
simulations Modulation QPSK, 16QAM, 64QAM, 256QAM
that have Max # UEs per TTI 14
also proven Scheduler
Nokia Smart Scheduler
(Proportional Fair)
benefits Slow fading Std. dev = 8 dB; corr. distance = 50 m
brought by Fast fading SCME (Spatial Channel Extended Model) 3 kmph

activation of Traffic model Full Buffer

Number of users in the simulation 10UEs per cell (210 total)
256QAM
User placement Uniform distribution, random placement + movement, speed=3kmh
Penetration of 256QAM capable UEs 0%, 20%, 40%, 60%, 80%, 100%

40 © Nokia 2018 Nokia Internal Use

Benefits and Gains
MoRSE Simulation results (1/3)

Baseline scenario:
• MIMO scheme: 2x2,
• 0% of 256QAM-capable UEs
• no power back-off used
• max 64QAM

Peak UE DL TP(s): + ~12%

Note:
1) Power back-off value (1.2dB) was taken for simulation scenarios with 256QAM capable UEs (20%-100% of
256QAM UEs)
~53,5Mbps recorded for 64QAM vs 2) % values on charts express the % of gain in relation to baseline
3) Average SINR in the cell ~14dB
~60Mbps recorded for 256QAM
Gain from 256QAM strongly depends on number of 256QAM capable UEs in the cell
*Note: 100% of 64QAM UEs vs 100% of 256QAM UEs

41 © Nokia 2018 Nokia Internal Use

Benefits and Gains
MoRSE Simulation results (2/3)

Baseline scenario:
• MIMO scheme: 4x4,
• 0% of 256QAM-capable UEs
• no power back-off used
• max 64QAM

Peak UE DL TP(s): + ~12%

Note:
1) Power back-off value (1.2dB) was taken for simulation scenarios with 256QAM capable UEs (20%-100% of
256QAM UEs)
~89Mbps recorded for 64QAM vs 2) % values on charts express the % of gain in relation to baseline
3) Average SINR in the cell ~17.5dB
~100Mbps recorded for 256QAM
Gain from 256QAM strongly depends on number of 256QAM capable UEs in the cell
*Note: 100% of 64QAM UEs vs 100% of 256QAM UEs

42 © Nokia 2018 Nokia Internal Use

Benefits and Gains
MoRSE Simulation results (3/3)

Previous results (2x2) were achieved

with quite good radio conditions
(average SINR ~14dB).
As a result even on the cell edge, gain
was recorded

Cell edge loss at worse radio conditions: ~

13,5%
Radio conditions were intentially degraded (average
SINR ~3,2dB)
Cell edge throughput: ~88,2kbps for 100% of non-256QAM UEs
Cell edge loss proves the need of the LTE3073 vs ~76,4kbps for 100% of 256QAM configured UEs.
– 256 QAM extensions Note: In this example both scenarios 100% 64QAM UEs and 100% 256QAM UEs have the same power (power back-off
= 1.2dB). Thus ~13,5% of loss is caused by usage of different MCS-TBS index mapping tables only.

43 © Nokia 2018 Nokia Internal Use

Benefits and Gains
Acceptance testing results

Assumptions: Test results

• RAT: LTE TDD • Peak DL UE TP for single-CA UE:

• eNB HW: FSIH(A101) + 2*FBIH(A101) + • 64QAM ~111 Mbps with 0% BLER vs 256QAM ~145

2*FZHJ(X21) Mbps with 0% BLER

• Distance UE-antennas: ~300m
• eNB SW: TL16A_ENB_0000_000296_000000
• Peak DL UE TP on 256QAM 2CC: ~286Mbps
• eNB parameterization for LTE2479:
− LNCEL:actModulationSchemeDl = 256QAM
− LNCEL:dlCellPwrRed = 0.0 (no power back-off)
• UE: Qualcomm 9640
• TM mode: TM3
~30% of gain in DL peak TP
More details available under the following link

44 © Nokia 2018 Nokia Internal Use

Benefits and Gains
Field results (NPI)

Assumptions Test results

• RAT: LTE FDD • Peak UE DL TP improvement: up to 23,7%
• eNB HW: FSMF + 2xFBBA + FXCA(B5) + (3CC CA) in stationary test
FHEA(B3) + FRGT(B1) • The average downlink throughput of the
• eNB SW: FL16A PCD FL16A_ENB_0000_000692_000041 test UE increased by 8.3%!
• eNB parameterization for LTE2479: • Achieved DL peak TP depends on the UE
• LNCEL:actModulationSchemeDl = 256QAM as well as the configured power
• LNCEL:dlCellPwrRed = 0.0, 0.5, 1.0 back-off value
• UE: LG G5, Samsung Galaxy 7 edge

Up to 23,7% of gain in DL peak TP

More details available under the following link

45 © Nokia 2018 Nokia Internal Use

LTE2479 - 256 QAM in downlink

Configuration
Management
Table of contents

<chapter:configuration_management>

46 © Nokia 2018 Nokia Internal Use

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

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

47 © Nokia 2018 Nokia Internal Use

Configuration Management
New basic parameters

Abbreviated name Full name PKDB link

LNCEL:actModulationSchemeDl Activate modulation scheme DL

48 © Nokia 2018 Nokia Internal Use

Configuration Management
Related basic parameters

Abbreviated name Full name PKDB link

LNCEL:dlCellPwrRed Cell​power​reduce

49 © Nokia 2018 Nokia Internal Use

LTE2479 - 256 QAM in downlink

Deployment
Aspects
Network graphic boxes Network element boxes
Table of contents

<chapter:deployment_aspects>

50 © Nokia 2018 Nokia Internal Use

Deployment Aspects
256QAM best deployment candidates

High SINR requirements that have to be met, before

eNB decides to use 256QAM, limit the number of
scenarios for 256QAM feature enabling
Opportunity to satisfy SINR requirement can appear in:
- Indoor deployments (interference isolated scenario)
- Small cells
• Small cells built on Low Power Metro RRH
• Flexi Zone product – support provided by dedicated FDD/TDD
features in FL/TL17A: LTE3502/LTE3020 (256 QAM in Downlink
for Flexi Zone BTS on FDD/TD-LTE)

and these are the main candidates, where 256QAM is

worth being considered
Note: Please check slide # to find more details about where to use 256QAM.

51 © Nokia 2018 Nokia Internal Use

Deployment Aspects
Feature activation

Feature LTE2479 can be activated by proper

choice of Activate modulation scheme DL
option in BTS Site Manager (256QAM) or by
setting parameter
LNCEL:actModulationSchemeDL to 256QAM
One has to select the highest allowed modulation
scheme in a cell
- Note: activation of 256QAM leads to activation of all
lower modulation orders as well, that is, QPSK,
16QAM, 64QAM will also be used, depending on the
radio conditions
One has to select the highest allowed
DL modulation scheme in the cell

52 © Nokia 2018 Nokia Internal Use

Deployment Aspects
Feature configuration

When LTE2479 is activated and power

back-off is going to be used, one can
configure it as a component of
dlCellPwrRed parameter value

Power back-off, if going to be used, should

be contained in Cell power reduce option

53 © Nokia 2018 Nokia Internal Use

LTE2479 - 256 QAM in downlink

Dimensioning
Aspects
Table of contents

<chapter:dimensioning>

54 © Nokia 2018 Nokia Internal Use

Dimensioning
Feature configuration in RAN Dim

256QAM modulation is not available in the

RAN Dim tool
RAN Dim can still be used for the dimensioning purposes
when certain workaround is used
1) If investigated DL TP value is in range supported by
RAN Dim
Example: 68Mbps are possible to be handled with 64QAM
in 20MHz  MCS28-64QAM is used for that purpose
256QAM capable UE will be handled according to the new
MCS-TBS index mapping table. Equivalent MCS that will
be used by eNB for 256QAM configured UE can be evaluated
thanks to the MCS mapping tool
- Equivalent of MCS28-64QAM will be MCS23-256QAM,
according to the new MCS-TBS index mapping table

256QAM mapper

55 © Nokia 2018 Nokia Internal Use

Dimensioning
Feature configuration in RAN Dim

One should provide SINR offset to Additional gains

field
• Note that sometimes SINR offset can be negative (negative gain
is to be used then)

• Once done, RAN Dim can be used as usual

Please keep in mind that coverage calculation for 256QAM UE
is done in line with equivalent MCS (23 in this example)

Mapper output (to RAN Dim) Mapper input (from RAN Dim)

56 © Nokia 2018 Nokia Internal Use

Dimensioning
Feature configuration in RAN Dim

2) If investigated TP value is out of range supported by

RAN Dim
Example: 80Mbps are not possible to be handled
with 64QAM in 20MHz  no suitable MCS is found
As investigated DL TP can still be handled by
256QAM modulation, again 256QAM Mapper tool can help
you
in evaluations Inputs

Outputs

Note: If the output of 256QAM mapper is ‚not available’ (Required MCS for 256 QAM
UE = not available) it indicates that investigated DL TP cannot be handled by given
scenario even with 256QAM DL modulation

57 © Nokia 2018 Nokia Internal Use

Dimensioning
Feature configuration in RAN Dim

Outputs from the Mapper

should be entered to the
RAN Dim as shown on picture
Please keep in mind that
evaluation is now
being
done for equivalent
MCS
27 (27_256QAM),
as
shown in the Mapper
tool

58 © Nokia 2018 Nokia Internal Use

LTE2479 - 256 QAM in downlink

Performance
Aspects
Table of contents

<chapter:performance_aspects>

59 © Nokia 2018 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

UE_256QAM_CONF_CQI_LEVEL_{00-15} UE reported (wideband) Channel Quality Indicator (CQI) class for 256QAM-
(M8010C116 - M8010C131) configured UEs*.

Trigger event: Appropriate counter is updated when the associated CQI value is
received from the 256QAM-configured UEs.
Example: M8010C116 is incremented when 256QAM-configured UE reports CQI
class 00, M8010C117 is incremented when class 01 is received etc.
Note: only reports from UEs using the new CQI and MCS-TBS index mapping table are
considered
Use case: 256QAM capable UE CQI histogram

*Note: Counters M8010C116-M8010C131 are pegged for all Codewords (i.e. CW0 and CW1)

60 © Nokia 2018 Nokia Internal Use

 Performance Aspects
New counters

Counter name Description

SCHDL_256QAM_PDSCH_QPSK This counter provides the number of transmissions on PDSCH over the
(M8011C196) measurement period using corresponding modulation for 256QAM-scheduled
UEs.
SCHDL_256QAM_PDSCH_16QAM
(M8011C197) Trigger event: This counter is updated when corresponding modulation is used
for transmission of the 256QAM-scheduled UEs. SIB, Paging and RA response
are excluded (Note:DL transmissions to UEs using the new CQI and MCS-TBS
SCHDL_256QAM_PDSCH_64QAM index mapping table are counted only)
(M8011C198)
Use case: Ratio of QPSK (M8011C196) transmissions for 256QAM-scheduled
SCHDL_256QAM_PDSCH_256QAM UEs. For
(M8011C199) For ratio of other modulations, please use the appropriate counters [16QAM
(M8011C197), 64QAM(M8011C198), 256QAM(M8011C199)].
Ratio of QPSK transmissions for M8011C196
x 100%
256QAM-scheduled UEs = M8011C196 + M8011C197 + M8011C198 + M8011C199

61 © Nokia 2018 Nokia Internal Use

 Performance Aspects
New counters
Counter name Description
SCHDL_256QAM_PDSCH_NACK_QPSK The number of unacknowledged transmissions on PDSCH
(M8011C200) using one of corresponding DL modulations for 256QAM-
scheduled UEs.
SCHDL_256QAM_PDSCH_NACK_16QAM
(M8011C201) Trigger event: When QPSK/16QAM/64QAM/256QAM is
used respectively for transmission of 256QAM-scheduled UEs
SCHDL_256QAM_PDSCH_NACK_64QAM (Note:DL transmissions to UEs using the new CQI and MCS-
(M8011C202) TBS index mapping table are counted only)

SCHDL_256QAM_PDSCH_NACK_256QAM
(M8011C203)

62 © Nokia 2018 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

SCHDL_256QAM_PDSCH_FAIL_QPSK The number of unsuccessful transmissions on PDSCH using
(M8011C204) QPSK/16QAM/64QAM/256QAM for 256QAM-scheduled UE. Only not transmitted TBs
exceeding max HARQ retransmissions are considered.
SCHDL_256QAM_PDSCH_FAIL_16QA Trigger event: A corresponding counter is updated when the maximum number of HARQ
M retransmissions has been exceeded for the TB sent with QPSK/16QAM/64QAM/256QAM
(M8011C205) (Note: DL transmissions to UEs using the new CQI and MCS-TBS index mapping table are
counted only)
SCHDL_256QAM_PDSCH_FAIL_64QA
M Use cases:
(M8011C206)
Ratio of unsuccessful QPSK transmissions M8011C204
for 256QAM-scheduled UEs * x 100%
SCHDL_256QAM_PDSCH_FAIL_256QA M8011C196
=
M
(M8011C207) Ratio of unsuccessful transmissions M8011C204 + M8011C205 + M8011C206 + M8011C207
M8012C175
for 256QAM-scheduled UEs = x 100%
M8011C196 + M8011C197 + M8011C198 + M8011C199

*Note: For other modulations please use proper pair of counters: e.g. for 16QAM(M8011C205/M8011C197)

63 © Nokia 2018 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

SCHDL_256QAM_VOL_PDSCH_QPSK The size of transport blocks scheduled on PDSCH using

(M8012C175) QPSK/16QAM/64QAM/256QAM for 256QAM-scheduled UE. The volume of MAC
PDUs is considered (expressed in bytes)
SCHDL_256QAM_VOL_PDSCH_16QA
M Trigger event: This counter is updated when MAC PDU is scheduled for 256QAM-
(M8012C176) scheduled UE. Retransmissions are included (Note: only TB sizes used for UEs using
the new CQI and MCS-TBS index mapping table are considered)
SCHDL_256QAM_VOL_PDSCH_64QA
M Use case: Average TB size for 256QAM-scheduled UE
(M8012C177)
Average TB size in QPSK transmissions M8012C175
SCHDL_256QAM_VOL_PDSCH_256QA for 256QAM-scheduled UEs *
M = M8011C196
(M8012C178)

*Note: For other modulations please use proper pair of counters: e.g. for 16QAM(M8012C176/M8011C197)

64 © Nokia 2018 Nokia Internal Use

Performance Aspects
Where to use 256QAM?

Counter name Description

UE_REP_CQI_LEVEL_00 (M8010C36) UE reported (wideband) Channel Quality Indicator CQI class.
UE_REP_CQI_LEVEL_01 (M8010C37) Trigger event: The appropriate counter is updated when associated CQI is received from
UE_REP_CQI_LEVEL_02 (M8010C38) the UE..
UE_REP_CQI_LEVEL_03 (M8010C39) Example: M8010C36 is incremented when UE reports CQI class 00, M8010C37 is
UE_REP_CQI_LEVEL_04 (M8010C40) incremented when class 01 is received etc. (Note: only reports from UEs using legacy CQI
UE_REP_CQI_LEVEL_05 (M8010C41) and MCS-TBS index mapping table are counted, i.e. reports from 256QAM scheduled UEs, using
UE_REP_CQI_LEVEL_06 (M8010C42) the new CQI and MCS-TBS mapping tables are excluded).
UE_REP_CQI_LEVEL_07 (M8010C43)
UE_REP_CQI_LEVEL_08 (M8010C44) Use case: UE CQI histogram
UE_REP_CQI_LEVEL_09 (M8010C45) Note: These counters can be used for evaluation of the radio conditions in the cell
UE_REP_CQI_LEVEL_10 (M8010C46) where 256QAM is going to be used.
UE_REP_CQI_LEVEL_11 (M8010C47)
UE_REP_CQI_LEVEL_12 (M8010C48)
UE_REP_CQI_LEVEL_13 (M8010C49)
UE_REP_CQI_LEVEL_14 (M8010C50) The more frequently CQI=15 is
UE_REP_CQI_LEVEL_15 (M8010C51) reported by the UEs, comparing to
other CQIs, the higher chance of
#LTE Power and Quality DL
efficient 256QAM usage

65 © Nokia 2018 Nokia Internal Use

Performance Aspects
Network performance monitoring after 256QAM activation
Feature impact How to measure
Improved mean and instantaneous DL UE throughput E-UTRAN average PDCP Layer Active Cell
Gain depends mostly on the radio conditions – DL SINR that defines 256QAM area probability, as well as Throughput DL (LTE_5292d)
256QAM UE penetration. The higher the area probability is, the higher the chance of 256QAM usage that leads
to higher UE DL instantaneous TP. Maximum PDCP Throughput DL (LTE_291b)
Due to the high DL SINR requirements that have to be met before 256QAM is used, the 256QAM area
probability is relatively small.
Feature is expected to provide gain mainly in peak DL TP. Nevertheless some gains in average cell DL TP might Note: To verify peak UE throughput for the 256QAM capable UEs
be also recorded (gains depend strictly on the scenario) it is recommended to perform drive tests

Please note that 256QAM requires a power back-off for some radios. In case power back-off is used and
256QAM UE penetration is relatively small, a loss in mean/instantaneous DL TP may also be recorded. The
expected gain of 256QAM may not surpass a loss caused by a static power reduction.

Smaller average DL PRB usage DL_PRB_UTIL_TTI_MEAN (M8011C37)

It is possible that DL PRB utilization will decrease due to the usage of higher order modulation (256QAM). The
same amount of data can be sent with less PRBs (8 bits per one modulation symbol instead of 6 bits per one
modulation symbol for 64QAM)

66 © Nokia 2018 Nokia Internal Use

Performance Aspects
Network performance monitoring after 256QAM activation
Feature impact How to measure
Smaller average CQI* E-UTRAN Average CQI (LTE_5427b) [xL16A]
3GPP defined new CQI index table that is used for 256QAM capable UEs, when LTE2479 is activated. E-UTRAN Average CQI (LTE_5427c) [xL17]
New CQI index table is coarser. Some efficiency levels are removed and remaining levels are shifted to lower
CQI indexes. Some higher efficiency levels are added at the bottom (CQI indexes 12-15). As a result, lower CQI
E-UTRAN Average CQI of 256QAM configured
index for 256QAM UE means higher efficiency than the same CQI index for UEs (LTE_6119a)
non-256QAM UE. As a consequence, whenever LTE2479 is activated, 256 QAM capable UE, in the same radio E-UTRAN Average CQI for Code Word 1 of
conditions (when given efficiency level is achievable), will report smaller CQI.
256QAM configured UEs (LTE_6128a)
*Note: Effect will be visible only in FL/TL16A. Starting from x17, 256QAM configured UEs are excluded from LTE_5427c. Instead there E-UTRAN Average CQI for Code Word 0 of
are separate KPIs for monitoring of average CQI for 256QAM configured UEs.
Analogical impact in xL16A on average MCS KPI is not visible as 256QAM UEs are not counted by counters M8001C45-M8001C73 .
256QAM configured UEs (LTE_6129a)
What is more there are no separate counters, dedicated for counting PDSCH transmissions using MCS0-MCS27 for 256QAM configured
UEs.

Reduced cell coverage Cell range histogram*

In majority of cases, LTE cells are UL limited and power back-off addition (less than 2dB) does not change the Overall handover preparation attempts (LTE_1438b)
cell RF footprint at all. However in the scenarios where cell is DL limited, usage of recommended power back-off
may decrease coverage futhermore. Additional attention should be paid in scenarios where difference between DL
and UL MCL is relatively small  usage of a power back-off might change the case from UL to DL limited,
resulting in affected cell range.

When power back-off is used in a given cell, UEs can be handed over sooner what will result in change in Cell
range distribution as well as it can increase the number of attempted HO.

*Note: More details can be found under the following link

67 © Nokia 2018 Nokia Internal Use

LTE2479 - 256 QAM in downlink

Compliance
Aspects
Table of contents

<chapter:compliance_aspects>

68 © Nokia 2018 Nokia Internal Use

Compliance Aspects

LTE2479 introduces higher order modulation – 8

bits per modulation symbol, which is specified by
3GPP (for more details please check 3GPP TS
36.211)
Only UE of category 9, 11-15 has a possibility to support 256QAM
- UE reports potential 256QAM capability per each
supported band
According to 3GPP standarization, 256QAM capable UE can be
handled according to either the new (7.2.3-2 and 7.1.7.1-1A) or
legacy CQI and MCS/TBS index tables (7.2.3-1 and 7.1.7.1-1)
Legacy UEs are handled according to the legacy CQI and
Cooperation between eNB and
MCS/TBS index tables (7.2.3-1 and 7.1.7.1-1) UE, needed for proper 256QAM
handling, is standardized by 3GPP

69 © Nokia 2018 Nokia Internal Use

 Extra High Value Feature

NETWORK
ENGINEERING

LTE3073 - 256 QAM extensions

70 © Nokia 2018 Nokia Internal Use

LTE3073 - 256 QAM extensions
Table of contents

Introduction Technical Inter – Benefits and Configuration Deployment

Details dependencies Gains Management Aspects
Motivation and Feature Detailed Functionality Simulation, Lab and Field Parameters and
Interdependencies with Activation, Configuration
Overview Description Findings Parameterization
other features and Examples, Fault Mgmt,
functions Scenarios Trial Area
1

fALU Performance
equivalents Aspects
Nokia vs. ALU solution Counters and KPIs,
comparison Feature Impact Analysis
and Verification

71 © Nokia 2018 Nokia Internal Use

LTE3073 - 256 QAM extensions

Introduction

Table of contents

<chapter:introduction>

72 © Nokia 2018 Nokia Internal Use

Introduction
Background - motivation

Non-efficient 256QAM UE handling Worse DL TP of 256QAM capable

UEs at cell edge
Lack of CQI and MCS conversion functionality could
lead to non-effective 256QAM capable UE handling
256QAM feature support requires new
by algorithms other than Link adaptation that also
LTE3073 – make their decisions based on CQI/MCS. CQI index mapping table as well as new
256QAM MCS-TBS index mapping table to be
Rationale:
used. Coarser granularity of new tables
extensions New CQI index table as well as new MCS-TBS index
with introduction of LTE2479 can cause
mapping table have different mappings of CQI index to
is an efficiency and MCS index to TBS index. Even though 256QAM capable UE to experience
radio conditions are the same, in comparison to the non-
answer on 256QAM capable UE:
deterioration of DL TP on the cell edge
• 256QAM capable UEs will report smaller average
CQI index value
• smaller MCS value will be assigned for DL
transmissions of 256QAM capable UEs

73 © Nokia 2018 Nokia Internal Use

Introduction
256QAM extensions overview

Available from FL/TL17A

LTE3073 enhances the basic functionality
LTE3073 requires LTE2479 to be activated
introduced with LTE2479

CQI/MCS conversion 256QAM Performance monitor

LTE3073 – LTE3073 brings some basic functionalitites on top of LTE3073 introduces 256QAM performance monitoring
256QAM what was provided with LTE2479 (it does not require mechanism controlled by an activation flag. Operator
any additional feature activation) has a possibility to decide whether the performance
extensions monitor will check UE`s perceived channel quality and
1) MCS conversion based on that decide on the 256QAM capable UE
2) CQI conversion configuration.

that will guarantee fair 256QAM capable UE evaluation

by mechanisms that also base on the reported
CQI/assigned MCS for DL transmissions
More details can be found on slide #

74 © Nokia 2018 Nokia Internal Use

Introduction
Before & after LTE3073

Before After
• All mechanisms that make their decisions • CQI/MCS conversions are available. It will
based on reported CQI or assigned DL result in fair evaluation of 256QAM
MCS could cause inefficient 256QAM capable UEs by algorithms different than
capable UE handling LA that also relies on reported CQI or
• When 256QAM was enabled in the cell, assigned MCS
256QAM capable UE could achieve worse • If performance monitoring mechanism is
DL TP at the cell edge (in the area where enabled, DL TP of 256QAM capable UE at
QPSK is used) the cell edge will be improved (DL TP will
be closer to the DL TP before 256QAM
feature activation*)
*Note: When 256QAM is activated and power back-off is used, DL TP may still be affected

75 © Nokia 2018 Nokia Internal Use

LTE3073 - 256 QAM extensions

Technical Details

Table of contents

76 © Nokia 2018 Nokia Internal Use

Technical Details Sales information
Dependency Table (LTE) BSW/ASW ASW

Release information
Release/version RL release eNodeB NetAct
FDD LTE FDD-LTE 17A FL17A NetAct 17.2
TDD LTE TD-LTE 17A TL17A NetAct 17.2
Flexi Zone Micro (FZM/FZP) N/A N/A N/A
Flexi Zone Controller (FZC) N/A N/A N/A
Single RAN SRAN17 SBTS17 NetAct 17.2

Release information – general

HW & IOT HW requirements MME SAE GW UE Specified by 3GPP
• FSMF/FSIH System Module Cat. 11,12
• AirScale System Module DL Cat.≥11*

Note: *Selected UE of listed categories support 256QAM. Support of 256QAM is mandatory for UEs of DL category 13-14.
Support of 256QAM is reported by UE itself. More details on slide #.

77 © Nokia 2018 Nokia Internal Use

Technical Details
MCS conversion (1/2)

Carrier Aggregation algorithm relies on the assigned MCS value to estimate the radio
conditions perceived by the UE

Before FL/TL17A 256QAM capable UEs were not treated fair by

LTE3073 e.g. Advanced SCell measurement handling (LTE1541)
Lack of MCS conversion
introduces mechanism could lead to
For 256QAM UE, even though the
the same radio conditions are perceived,
biased decisions as CA
algorithm relies only on
algorithm the smaller MCS will be assigned by
the MCS index value and
eNB. This is a consequence of
for MCS different does not take into
consideration that
conversion …
MCS-TBS index mapping table
different mapping table is
Example: used by the 256QAM
MCS index assigned to non-256QAM capable UE, according to the legacy MCS-TBS index mapping table, is capable UE
8. As it is indicated by green color in the table, it corresponds to MCS index 4 for 256QAM capable UE that
uses new MCS-TBS index mapping table.
Note: Both MCS indexes point out the same TBS index for non-256QAM and 256QAM capable UE accordingly.

78 © Nokia 2018 Nokia Internal Use

Technical Details
MCS conversion (2/2)
Configured Converted
Mapping of equivalent MCS index values is
MCS conversion
parameter value parameter value for
(MCS index) 256QAM UE*
done according to the predefined table 2 1
4 2
Modulation and coding scheme (MCS) is For configured parameter values (CPV) that have 6 3
one of possible indicators reflecting the mapped value not assigned (like MCS=1), 8 4

LTE3073 channel quality conversion is done according to the conservative

approach.
11 5
12 6
introduces Some of parameter values are expressed in MCS 13 7
For ‚up’ threshold LNCEL:scellGoodChQualThr, the 14 8
the index (acc. to legacy MCS-TBS table). Thus eNB
needs to do an internal conversion of (DL) MCS
next higher value will be used. 15 9

algorithm index value, used in configuration of dedicated

thresholds, like:
Example:
CPV=9 (not available)  CPV=11 (next higher value) 
16
18
10
11
Converted parameter value for 256QAM configured UE: 5
for MCS • LNCEL:scellBadChQualThr For all ‚down’ thresholds (LNCEL:scellBadQualThr,
19
20
12
13

conversion •
•
LNCEL:scellGoodChQualThr
LNCEL:scellNotDetectableThr
LNCEL:scellNotDetectable, LNCEL:iniMcsDl) the
next lower value will be used.
21
22
14
15
• LNCEL:iniMcsDl 23 16
Example:
to the value being an equivalent for 256QAM CPV=5 (not available)  CPV=4 (the next lower value)  24 17

UEs which use different Converted parameter value for 256QAM configured UE: 2 25 18
26 19
MCS-TBS index mapping tables
27,28 20

*Note: MCS conversion is applicable for 256QAM configured UEs only (256QAM capable UE that uses 256QAM relevant configuration)

79 © Nokia 2018 Nokia Internal Use

Technical Details
CQI conversion (1/2)

There are mechanisms, RF based VoLTE DRX deactivaton or MIMO, that rely on the
reported CQI value to estimate the radio conditions perceived by the UE

Before FL/TL17A 256QAM capable UEs were not treated fair

LTE3073 by e.g. RF based VoLTE DRX deactivation algorithm Lack of CQI conversion
introduces mechanism could lead to
For 256QAM UE, even though the biased decisions as RF
the same radio conditions are perceived, based VoLTE DRX
algorithm the smaller CQI will be reported, deactivation algorithm
according to the new coarser CQI relies only on the CQI
for CQI index mapping table defined by index value and does not
conversion …
3GPP take into consideration
that different mapping
Example: table is used by the
Non-256QAM capable UE perceives radio conditions, for which CQI index 5 is reported according to the 256QAM capable UE
legacy CQI index table. 256QAM capable UE in the same radio conditions will report CQI index 3,
according to the new table defined by 3GPP (as indicated by green color in the table above).

80 © Nokia 2018 Nokia Internal Use

Technical Details
CQI conversion (2/2)
CQI reported by
Converted CQI*
CQI 256QAM UE

1 1

Channel Quality Indicator is one of the crucial information that eNB 2 3

3 5
receives from UEs. It is a base for many decisions done by eNB`s
LTE3073 algorithms. 4 7
5 8
introduces 6 9
Mapping of equivalent CQI index values from the new and legacy CQI
the index table is done according to the predefined table
7 10

algorithm 8 11
9 12
for CQI 10 13
Note: The table contains the main CQI indexes (as defined by 3GPP). As a result of
conversion OLQC – Outer Link Quality Control operation, a final CQI can be adjusted with the 11 14
calculated ∆CQI. All possible CQI values, including adjustments are available in the 12 15
attached excel file CQI mapping
13 15
14 15
More details about the Link Adaptation in the Link Adaptation NEI complex. 15 15
*Note: CQI conversion is applicable for 256QAM configured UEs only (256QAM capable UE that uses 256QAM relevant configuration)

81 © Nokia 2018 Nokia Internal Use

Technical Details
256QAM performance monitor (1/4)

Coarser MCS-TBS index as well as CQI index mapping tables for 256QAM capable UEs
have been a reason of possible worse performance at the cell edge – where only QPSK has
been allowed to be selected by eNB
Note: For more details, please refer to slide #

LTE3073
LTE3073 offers an optional performance
introduces the monitor that will control the channel quality for non-256QAM relevant 256QAM relevant
optional 256QAM UEs. This funtionality is controlled via configuration configuration
functionality activation flag (LNBTS:actDl256QamChQualEst).
256QAM capable UE is 256QAM capable UE is
Whenever activation flag is set to true and channel
of 256QAM quality is evaluated as ‚bad’, eNB will reconfigure
configured to use legacy configured to use new,
CQI index as well as coarser CQI index as well
performance 256QAM capable UE to use non-256QAM relevant
MCS-TBS index mapping as MCS-TBS index
monitoring configuration. This will result in better performance
table mapping table
of 256QAM capable UEs at the cell Edge
(QPSK-64QAM) (QPSK-256QAM), i.e. it is
256QAM configured UE
256QAM capable UE is always initially configured Note: For more details refer to slides
# and #
to use 256QAM relevant configuration (RRC Note: For more details refer to slides
# and #
Connection establishment and after Handover)

82 © Nokia 2018 Nokia Internal Use

Technical Details
256QAM performance monitor (2/4)

Performance monitor evaluates each MCS sample MCS sample evaluation

MCS

Good channel MCS sample considered as

Conditions threshold ‚bad’

MCS sample considered as

Performance Bad channel
conditions threshold
‚neutral’ – neither ‚good’
nor ‚bad’

monitor MCS sample considered as

‚good’

evaluates Decision period for

time
channel quality estimation
MCS samples Decision period

During the time window (so called

A MCS sample is considered as A MCS sample is considered as
‚Decision period for channel quality
‚bad’ whenever index of MCS ‚good’ whenever index of MCS
estimation’), controlled by the
sample is lower than ‚bad channel sample is above or equal to ‚good
configurable timer
(LNCEL:perDl256QamChQualEst), each conditions threshold’ channel conditions threshold’
(LNCEL:dl256QamDeactChQualThr) (LNCEL:dl256QamReactChQualThr)
MCS sample is being evaluated

83 © Nokia 2018 Nokia Internal Use

Technical Details
256QAM performance monitor (3/4)

Channel quality estimation for 256QAM UE

eNB is able to estimate channel quality provided that MCS
10 MCS samples have been collected within already
expired decision period
At the end of • Each decision period is independent. All MCS samples
each decision that have been collected before are wiped out …
• Whenever number of collected samples is not enough
period, UE`s or channel quality estimation result is neither
perceived GOOD nor BAD, channel quality is considered to be time
unchanged Decision period for
channel quality channel quality estimation

is estimated
Channel quality estimation result: GOOD Channel quality estimation result: BAD

Percentage of ‚good’ MCS samples is higher Percentage of ‚good’ samples is lower than 80%
than or equal to 80% while percentage of ‚bad’ MCS samples is higher
than 80%

84 © Nokia 2018 Nokia Internal Use

Technical Details
256QAM performance monitor (4/4)

Channel quality estimation for 256QAM UE At the end of each decision period, eNB can make a

MCS 6 … … N
decision about the 256QAM capable UE
reconfiguration

Performance If UE operates based on If UE operates based on

monitor can …4 5 10 non-256QAM configuration 256QAM configuration and

trigger 256QAM
1 2
… and channel quality is
estimated as good,
channel quality is estimated
as bad,
256QAM relevant non-256QAM relevant
capable UE configuration is provided configuration is provided
via RRC Connection via RRC Connection
reconfiguration Decision period for
time
Reconfiguration Reconfiguration
when estimated channel quality estimation

channel quality 1 256QAM UE was initially configured with 256-QAM relevant configuration. Channel conditions are estimated as ‚bad’. RRC Connection Reconfiguration with
non-256QAM relevant configuration is triggered
result is either 2 - 4 Channel conditions are still estimated as ‚bad’. UE is already configured with non-256QAM configuration thus RRC Connection Reconfiguration is not triggered.

‚good’ or ‚bad’ 5 & 10 Channel conditions are estimated as ‚neutral’ (neihter ‚good’ nor ‚bad’). No action is triggered by eNB.

6 Channel conditions are estimated as ‚good’. 256QAM capable UE uses non-256QAM relevant configuration. RRC Connection Reconfiguration with 256QAM relevant
configuration is triggered

6 - 10 & 10 - N Channel conditions are estimated as ‚good’. 256QAM capable UE operates based on 256QAM relevant configuration. No RRC Connection
Reconfiguration is triggered.

85 © Nokia 2018 Nokia Internal Use

LTE3073 - 256 QAM extensions

Interdependencies

Table of contents

<chapter:interdependencies>

86 © Nokia 2018 Nokia Internal Use

Interdependencies

prerequisites LTE2479 – 256QAM in downlink

LTE3073 is applicable only, if LTE2479 is activated.
Please note that LTE3073 brings some functionality already with
LNCEL:actModulationSchemeDl = 256QAM. Additionally, there is an
optional mechanism of 256QAM performance monitoring available that
depends on the separate activation flag as well
(LNBTS:actDl256QamChQualEst)

87 © Nokia 2018 Nokia Internal Use

LTE3073 - 256 QAM extensions

Benefits and Gains

Table of contents

<chapter:benefits_and_gains>

88 © Nokia 2018 Nokia Internal Use

Benefits and Gains

Handling of 256QAM capable UE is more 256QAM capable UE will not experience DL

efficient TP degradation at the cell edge

LTE3073 As a result of CQI and MCS transparent If performance monitoring is decided to be used,
conversion mechanisms, all functionalities 256QAM capable UE will be reconfigured by eNB to
feature will use legacy CQI index mapping table as well as
relying on the reported CQI or allocated MCS
increase have a chance for fair 256QAM capable UE legacy MCS-TBS index mapping table whenever
256QAM capable UE perceives ‚bad’ radio
gains treatment.
conditions. As a result of this, improved performance
On the other hand, there is no need for many
provided separate parameters describing settings (e.g.
(DL TP) at the cell edge is expected – closer to the
DL TP before LTE2479 activation*. Whenever
already by thresholds) relevant for 256QAM capable UEs ‚good’ radio conditions are perceived by 256QAM
LTE2479 only. It will make 256QAM configuration capable UE, it will be instructed to operate based on
easier. new tables that will make usage of 256QAM possible
*Note: When 256QAM is activated and power back-off is used, DL TP may still be
affected

89 © Nokia 2018 Nokia Internal Use

LTE3073 - 256 QAM extensions

Configuration
Management
Table of contents

<chapter:configuration_management>

90 © Nokia 2018 Nokia Internal Use

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

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

91 © Nokia 2018 Nokia Internal Use

Configuration Management
New advanced parameters

Abbreviated name Full name PKDB link

Activate channel quality monitoring for
LNBTS:actDl256QamChQualEst
256QAM usage
MCS threshold for deactivating 256QAM for
LNCEL:dl256QamDeactChQualThr
the UE
MCS threshold for reactivating 256QAM for
LNCEL:dl256QamReactChQualThr
the UE
Decision period for channel quality
LNCEL:perDl256QamChQualEst
estimation

92 © Nokia 2018 Nokia Internal Use

Configuration Management
Related basic parameters

Abbreviated name Full name PKDB link

LNCEL:actModulationSchemeDl Activate modulation scheme DL

LNCEL:dlCellPwrRed Cell​power​reduce

93 © Nokia 2018 Nokia Internal Use

LTE3073 - 256 QAM extensions

Deployment
Aspects
Network graphic boxes Network element boxes
Table of contents

<chapter:deployment_aspects>

94 © Nokia 2018 Nokia Internal Use

Deployment Aspects
LTE3073 best deployment candidates

LTE2479 provides initial 256QAM support and is recommended for scenarios

as pointed out on slide #. LTE3073 is an enhancement of the baseline feature
LTE2479
part of functionalities provided by LTE3073 in FL/TL17A are enabled always when
LTE2479 is activated
256QAM performance monitor, which can be activated optionally, is worth being
considered especially if we expect that there are many 256QAM capable UEs located at
the cell edge
- the higher the number of 256QAM capable UEs in the cell, the higher gain will be brought by LTE3073

95 © Nokia 2018 Nokia Internal Use

Deployment Aspects
Performance monitor activation and configuration

1) Activate Performance Monitor by setting value of parameter LNBTS:actDl256QamChQualEst to true

2) Change the value of thresholds defining the ‚bad’ (LNCEL:dl256QamDeactChQualThr*) and ‚good’
(LNCEL:dl256QamReactChQualThr*) MCS sample, if needed, or stay with defaults

*Note: Parameter value should be given acc. to legacy MCS-TBS index mapping table

3) If needed, change the length of the decision period (LNCEL:perDl256QamChQualEst) during which the channel quality
estimation is done, otherwise stay with the default value of 60s

96 © Nokia 2018 Nokia Internal Use

LTE3073 - 256 QAM extensions

Performance
Aspects
Table of contents

<chapter:performance_aspects>

97 © Nokia 2018 Nokia Internal Use

Performance Aspects
New counters

There arename
Counter no additional counters andDescription
KPIs
UE_256QAM_CONF_CQI_CW1_LEVEL{0-15} Wideband Channel Quality Indicator CQI class {00-15} for Codeword 1 reported by
(M8010C132 - M8010C147) 256QAM-configured UEs.

Trigger event: This counter is updated when the associated wideband CQI
value for Codeword 1 is received from the 256QAM-configured UE.
Example:
M8010C132 is incremented by the eNB when 256QAM-configured UE
reports CQI class 00 for codeword 1, M8010C133 is incremented when class
01 is received etc.
Note: Only UE reports based on 256QAM CQI table 3GPP 36.213 Table
7.2.3-2 are considered.
Use case: 256QAM capable UE CQI histogram

Note: All counters/KPIs mentioned by the occasion of LTE2479, i.e. starting from slide #, are applicable for LTE3073 as well.

98 © Nokia 2018 Nokia Internal Use

Performance Aspects
Network performance monitoring (LTE3073 in use)

Feature impact How to measure

Improved mean DL cell throughput E-UTRAN average PDCP Layer Active Cell Throughput
DL (LTE_5292d)
Gain depends mostly on the radio conditions and if performance monitor is activated
(LNBTS:actDl256QamChQualEst=true). Whenever UE experiences ‚bad’ channel Note: To verify peak UE throughput for the 256QAM capable
quality, it will be reconfigured according to the non-256QAM relevant configuration. As UEs it is recommended to perform drive tests
a result, no deterioration of DL UE TP for 256QAM capable UE at the cell edge is
expected. This should lead to even higher mean DL cell TP.

Improved performance of other features that make Counters/KPIs mentioned in the scope of outlined features can be
checked before and after feature activation.
decision based on the CQI/MCS
Note that the improvement is expected to be seen for 256QAM
Fair evaluation of reported CQI/allocated MCS for 256QAM capable UEs should bring capable UEs thus level of improvement depends directly on the
improvement in performance of features such as: LTE1541 – Advanced SCell number of 256QAM capable UEs in the cell.
measurement handling, LTE1496 – eICIC micro or LTERLCR-9668 - RF-based
disabling of DRX for VoLTE UEs.

99 © Nokia 2018 Nokia Internal Use

Performance Aspects
Network performance monitoring (LTE3073 in use)

Feature impact How to measure

CQI/MCS Counters M8010C36-M8010C51 for CQI and M8001C45-

M8010C73 for MCS are pegged for non-256QAM capable UE
When Performance monitor introduced by LTE3073 is activated, 256QAM capable UE and 256QAM capable UE using the non-256QAM relevant
reconfigurations between 256QAM relevant and not relevant configurations will lead to configuration
different set of counters pegged for 256QAM capable UE. Whenever 256QAM Counters M8010C116-M8010C131 and M8010C132-
capable UE is not 256QAM configured, a legacy set of counters is pegged. M8010C147 for CQI (CW0&CW1 and CW1 respectively) are
pegged for 256QAM configured UEs
Impact mentioned above will have the influence on CQI/MCS distribution and average Note: No MCS counters are provided for 256QAM configured UEs.
CQI/MCS. Changes in distributions as well as in average CQI/MCS value will depend
on the 256QAM capable UE penetration and 256QAM capable UE mobility. E-UTRAN Average CQI (all KPIs collected on single slide)
Average used MCS on PDSCH transmissions (LTE_1074a)
LTE_1074a together with LTE_5427b (xL16A) or LTE5427c
(xL17) can be impacted by change of number of UEs which these
counters are incremented for. This in turn will be a consequnence
of 256QAM performance monitor operation, if it is decided to be
used.

100 © Nokia 2018 Nokia Internal Use

 NETWORK
ENGINEERING

LTE3502/LTE3020 - 256 QAM in

Downlink for Flexi Zone BTS on FDD-
LTE/TD-LTE

101 © Nokia 2018 Nokia Internal Use

LTE3502/LTE3020 - 256 QAM in Downlink for Flexi Zone BTS on FDD-LTE/TD-
LTE

Introduction and
Technical Details
Table of contents

<chapter:introduction>

102 © Nokia 2018 Nokia Internal Use

Introduction and Technical Details

Features LTE3502 – 256QAM in Downlink for FZ BTS on FDD-LTE and

LTE3020 – 256QAM in Downlink for FZ BTS on FDD-LTE
• Give possibility to enable
Feature • 256QAM modulation in DL (as introduced by LTE2479), by introduction of ’256QAM’ option in
LTE3502 and LNCEL:actModulationSchemeDl
LTE3020 bring • Performance monitor (as introduced by LTE3073), by addition of a separate parameter
256QAM LNBTS:actDl256QamChQualEst
support on Flexi in the FZM software (FLF17A/TLF17A respectively)
Zone BTS • Do not bring any changes in existing LTE2479/LTE3073 RRM algorithm
• Are expected to provide similar level of gains (up to ~33% higher peak DL TP over
64QAM)

103 © Nokia 2018 Nokia Internal Use

Technical Details Sales information
LTE3502 dependency table BSW/ASW ASW

Release information
Release/version RL release eNodeB NetAct
FDD LTE N/A N/A N/A
TDD LTE N/A N/A N/A
Flexi Zone Micro (FZM/FZP) FL17A FLF17A NetAct 17.2
Flexi Zone Controller (FZC) FL17A FLF17A NetAct 17.2
Single RAN N/A N/A N/A

Release information – general

HW & IOT HW requirements MME SAE GW UE Specified by 3GPP
Cat. 11,12
All supported FZ hardware is listed starting from slide #
DL Cat.≥11*
3GPP TS 36.213

Note: *Selected UE of listed categories support 256QAM. Support of 256QAM is mandatory for UEs of DL category 13-14.
Support of 256QAM is reported by UE itself. More details on slide #.

104 © Nokia 2018 Nokia Internal Use

Technical Details Sales information
LTE3020 dependency table BSW/ASW ASW

Release information
Release/version RL release eNodeB NetAct
FDD LTE N/A N/A N/A
TDD LTE N/A N/A N/A
Flexi Zone Micro (FZM/FZP) TL17A TLF17A NetAct 17.2
Flexi Zone Controller (FZC) N/A N/A N/A
Single RAN N/A N/A N/A

Release information – general

HW & IOT HW requirements MME SAE GW UE Specified by 3GPP
Cat. 11,12
All supported FZ hardware is listed starting from slide #
DL Cat.≥11*
3GPP TS 36.213

Note: *Selected UE of listed categories support 256QAM. Support of 256QAM is mandatory for UEs of DL category 13-14.
Support of 256QAM is reported by UE itself. More details on slide #.

105 © Nokia 2018 Nokia Internal Use

 LTE3502
Introduction and Technical Details
[FDD] FZ Hardware supporting 256QAM in DL (1/5)

Outdoor Mini Macro

Feature 3GPP Max Output RX Band TX Band Max BW** Antenna
Variant Spectrum Description
ID Band power per TX* (MHz) (MHz) (MHz) config

FW2CA BC26 Flexi Zone G2 Outdoor Micro

LTE2914 FW2CA 26 850MHz 20W 817.6 – 824 862.6 – 869 5 2x2
FDD LTE 850 MHz High Power w/ PoE

FW2EA BC3 Flexi Zone G2 Outdoor Micro

LTE3493 FW2EA 3 1800MHz 20W 1710 – 1785 1805 – 1880 20 2x2
FDD LTE 1800 MHz High Power w/ PoE

FW2H FW2HA BC7 Flexi Zone G2 Outdoor Micro

LTE3492 7 2600MHz 20W 2500 – 2570 2620 - 2690 20 2x2
A FDD LTE 2600 MHz High Power w/ PoE

FW2PC BC28 Flexi Zone G2 Outdoor Micro

LTE3460 FW2PC 28 700Mhz 20W 703 – 748 758 – 803 20 2x2
FDD LTE 700 MHz High Power w/ PoE

Note:
* Max output power per TX per antenna connector
** Max bandwidth supported, e.g. if 20MHz is given, 5, 10, 15 and 20MHz are supported

106 © Nokia 2018 Nokia Internal Use

 LTE3502
Introduction and Technical Details
[FDD] FZ Hardware supporting 256QAM in DL (2/5)

G2 Dual Band Pico

Feature 3GPP Max Output RX Band TX Band Max BW Antenna
Variant Spectrum Description
ID Band power per TX (MHz) (MHz) (MHz) config
2 1900 MHz, 1850 – 1910 1930 – 1990 FW2FIA B2+B4/B66 Flexi Zone G2 Indoor Dual
FW2FIA 250mW 20 2x2
66 AWS 1710 - 1780 2110 - 2180 Band Pico
2 1900 MHz, 1850 – 1910 1930 – 1990 FW2FIWA B2+B4/B66 Flexi Zone G2 Indoor Dual
LTE2729 FW2FIWA 250mW 20 2x2
66 AWS 1710 - 1780 2110 - 2180 Band Pico + WiFi
2 1900 MHz 1850 – 1910 1930 – 1990 FW2FIWC B2+B4/B66 Flexi Zone G2 Indoor Dual
FW2FIWC 250mW 20 2x2
66 AWS 1710 - 1780 2110 - 2180 Band Pico + WiFi
66 AWS 2110 - 2180 20 FW2IRA B4/B66+LAA Flexi Zone G2 Indoor
FW2IRA 250mW 1710 - 1780 (5150-5250) + (5735- 2x2
LAA UNII-1 & 3 5835) 60 Multi Band Pico
66 AWS 2110 - 2180 20 FW2IRWA B4/B66+LAA Flexi Zone G2 Indoor
LTE2357 FW2IRWA 250mW 1710 - 1780 (5150-5250) + (5735- 2x2
LAA UNII-1 & 3 5835) 60 Dual Band Pico + WiFi
66 AWS 2110 - 2180 20 FW2IRWC B4/B66+LAA Flexi Zone G2 Indoor
FW2IRWC 250mW 1710 – 1780 (5150-5250) + (5735- 2x2
LAA UNII-1 & 3 5835) 60 Dual Band Pico + WiFi
3 1800MHz 1805 - 1880 20 FW2ERA B3+LAA Flexi Zone G2 Indoor Multi
FW2ERA 250mW 1710 – 1785 (5150-5250) + (5735- 2x2
LAA UNII-1 & 3 5835) 60 Band Pico
LTE2951
3 1800MHz 1805 - 1880 20 FW2ERWA B3+LAA Flexi Zone G2 Indoor Multi
FW2ERWA 250mW 1710 - 1785 (5150-5250) + (5735- 2x2
LAA UNII-1 & 3 5835) 60 Band Pico + WiFi

107 © Nokia 2018 Nokia Internal Use

 LTE3502
Introduction and Technical Details
[FDD] FZ Hardware supporting 256QAM in DL (3/5)

G2 Dual Band Pico

Feature 3GPP Max Output RX Band TX Band Max BW Antenna
Variant Spectrum Description
ID Band power per TX* (MHz) (MHz) (MHz) config
1 2100 MHz 1920 - 1980 2110 - 2170 FW2GEA B1+B3 Flexi Zone G2 Indoor MultiBand
FW2GEA 250mW 20 2x2
3 1800 MHz 1710 - 1785 1805 - 1880 Pico
LTE3014
1 2100 MHz 1920 - 1980 2110 - 2170 FW2GEWA B1+B3 Flexi Zone G2 Indoor
FW2GEWA 250mW 20 2x2
3 1800 MHz 1710 - 1785 1805 - 1880 MultiBand Pico + WiFi
1 2100 MHz 1920 - 1980 2110 - 2170 FW2GHA B1+B7 Flexi Zone G2 Indoor
FW2GHA 250mW 20 2x2
7 2600 MHz 2500 - 2570 2620 - 2690 MultiBand Pico
LTE3015
1 2100 MHz 1920 - 1980 2110 - 2170 FW2GHWA B1+B7 Flexi Zone G2 Indoor
FW2GHWA 250mW 20 2x2
7 2600 MHz 2500 - 2570 2620 - 2690 MultiBand Pico + WiFi
3 1800MHz 1710 - 1785 1805 - 1880 FW2EHA B3+B7 LB Flexi Zone G2 Indoor
FW2EHA 250mW 20 2x2
7 2600 MHz 2500 - 2570 2620 - 2690 MultiBand Pico
LTE2950
3 1800MHz 1710 - 1785 1805 - 1880 FW2EHWA B3+B7 LB Flexi Zone G2 Indoor
FW2EHWA 250mW 20 2x2
7 2600 MHz 2500 - 2570 2620 - 2690 MultiBand Pico + WiFi
7 2600MHz FW2HHA B7 + B7 Flexi Zone G2 Indoor
FW2HHA 250mW 2510 - 2550 2630 – 2670 20 2x2
7 2600MHz MultiBand Pico
LTE3177
7 2600MHz FW2HHWA B7 + B7 Flexi Zone G2 Indoor
FW2HHWA 250mW 2510 - 2550 2630 - 2670 20 2x2
7 2600MHz MultiBand Pico + WiFi
1 2100 MHz 1920 – 1980 2110 – 2170
40MHz FW2GEHA B1+B3+B7 Flexi Zone Indoor Multi+
LTE3382 FW2GEHA 3 1800 MHz 250mW 1710 – 1785 1805 - 1880 2x2
cummulative* Band Pico
7 2600 MHz 2500 - 2570 2620 - 2690

* e.g. 10/10/20Mhz, 15/15/10, any combination in any order as long as it adds up to 40MHz

108 © Nokia 2018 Nokia Internal Use

 LTE3502
Introduction and Technical Details
[FDD] FZ Hardware supporting 256QAM in DL (4/5)

G2 Dual Band Pico

Feature 3GPP Max Output RX Band TX Band Max BW Antenna
Variant Spectrum Description
ID Band power per TX (MHz) (MHz) (MHz) config
2 1900 MHz 1850 - 1910 1930 - 1990
40MHz FW2FPIA B2 + B13 + B66 Flexi Zone Indoor
LTE3383 FW2FPIA 13 700 MHz 250mW 777 – 787 746 - 756 2x2
cummulative* Multi Band Pico
66 AWS 1710 - 1780 2110 - 2180
2 1900 MHz 1850 - 1910 1930 - 1990 FW2FIB B2+B66 Flexi Zone G2 Outdoor
FW2FIB 5W 20 2x2
66 AWS 1710 - 1780 2110 - 2180 MultiBand Micro
2 1900 MHz 1850 - 1910 1930 - 1990 FW2FIWB B2+B66 Flexi Zone G2 Outdoor
LTE3171 FW2FIWB 5W 20 2x2
66 AWS 1710 - 1780 2110 - 2180 MultiBand Micro + WiFi
2 1900 MHz 1850 - 1910 1930 - 1990 FW2FIWD B2+B66 Flexi Zone G2 Outdoor
FW2FIWD 5W 20 2x2
66 AWS 1710 - 1780 2110 - 2180 MultiBand Micro + WiFi
3 1800 MHz, 1710 - 1785 1805 – 1880 FW2EHB B3+B7 Flexi Zone G2 Outdoor
FW2EHB 5W 20 2x2
7 2600 MHz 2500 - 2570 2620 - 2690 MultiBand Micro
LTE2600
3 1800 MHz, 1710 - 1785 1805 – 1880 FW2EHWB B3+B7 Flexi Zone G2 Outdoor
FW2EHWB 5W 20 2x2
7 2600 MHz 2500 - 2570 2620 - 2690 MultiBand Micro + WiFi (WW)
66 AWS 5W 2110 - 2180 20 FW2IRB B66+LAA Flexi Zone G2 Outdoor
FW2IRB 1710 - 1780 (5150-5250) + (5735- 2x2
LAA UNII-1 & 3 500mW 5835) 60 MultiBand Micro
66 AWS 5W 2110 - 2180 20 FW2IRWB B66+LAA Flexi Zone G2 Outdoor
LTE2654 FW2IRWB 1710 - 1780 (5150-5250) + (5735- 2x2
LAA UNII-1 & 3 500mW 5835) 60 MultiBand Micro + WiFi
66 AWS 5W 2110 - 2180 20 FW2IRWD B66+LAA Flexi Zone G2 Outdoor
FW2IRWD 1710 - 1780 (5150-5250) + (5735- 2x2
LAA UNII-1 & 3 500mW 5835) 60 MultiBand Micro + WiFi

* e.g. 10/10/20Mhz, 15/15/10, any combination in any order as long as it adds up to 40MHz

109 © Nokia 2018 Nokia Internal Use

 LTE3502
Introduction and Technical Details
[FDD] FZ Hardware supporting 256QAM in DL (5/5)

G2 Dual Band Pico

Feature 3GPP Max Output RX Band TX Band Max BW Antenna
Variant Spectrum Description
ID Band power per TX* (MHz) (MHz) (MHz) config
1 2100 MHz 1920 – 1980 2110 – 2170 FW2GEB B1+B3 Flexi Zone G2 Outdoor
FW2GEB 5W 20 2x2
3 1800 MHz 1710 - 1785 1805 - 1880 MultiBand Micro
LTE2476
1 2100 MHz 1850 - 1910 1930 - 1990 FW2GEWB B1+B3 Flexi Zone G2 Outdoor
FW2GEWB 5W 20 2x2
3 1800 MHz 1710 - 1780 2110 - 2180 MultiBand Micro + WiFi
1 2100 MHz, 1920 – 1980 2110 – 2170 FW2GHB B1+B7 Flexi Zone G2 Outdoor
FW2GHB 5W 20 2x2
7 2600 MHz 2500 - 2570 2620 - 2690 MultiBand Micro
LTE3170
FW2GHW 1 2100 MHz, 1920 – 1980 2110 – 2170 FW2GHWB B1+B7 Flexi Zone G2 Outdoor
5W 20 2x2
B 7 2600 MHz 2500 - 2570 2620 - 2690 MultiBand Micro + WiFi
2 1900 MHz 1850 – 1910 1930 – 1990
40MHz FW2FPIB B2 + B13 + B66 Flexi Zone Outdoor
LTE3426 FW2FPIB 13 700 MHz 5W 777 – 787 746 – 756 2x2
cummulative* Multi Band Micro
66 AWS 1710 - 1780 2110 - 2180

* e.g. 10/10/20Mhz, 15/15/10, any combination in any order as long as it adds up to 40MHz
Note: List of FZM HW given on slides concerns existing FZM HW that supports 256QAM. Newer HW is expected to support 256QAM as well.

110 © Nokia 2018 Nokia Internal Use

 LTE3020
Introduction and Technical Details
[TDD] FZ Hardware supporting 256QAM in DL (1/3)

Outdoor Mini Macro

Feature 3GPP Max Output RX Band TX Band Max BW** Antenna
Variant Spectrum Description
ID Band power per TX* (MHz) (MHz) (MHz) config

FWHX B41 Flexi Zone Outdoor Micro TDD

LTE3026 FWHX 41 2600MHz 20W 2575 – 2635 40MHz 2x2
LTE 2600 MHz Narrow Band High Power

FWHR 41 2600MHz 20W 2496 – 2690 40MHz 2x2 B41 MM FZ 2x20W (FWHR)

FWHRL B41 MM FZ 2x20W (FWHR)

41 2600MHz 20W 2496 – 2593 40MHz 2x2
LTE2825 B

FWHRH B41 MM FZ 2x20W (FWHR)

41 2600MHz 20W 2593 - 2690 40MHz 2x2
B

Note:
* Max output power per TX per antenna connector
** Max bandwidth supported, e.g. if 20MHz is given, 5, 10, 15 and 20MHz are supported

111 © Nokia 2018 Nokia Internal Use

 LTE3020
Introduction and Technical Details
[TDD] FZ Hardware supporting 256QAM in DL (2/3)

Outdoor Micro
Feature 3GPP Max Output RX Band TX Band Max BW Antenna
Variant Spectrum Description
ID Band power per TX (MHz) (MHz) (MHz) config
FWHE BC41 Flexi Zone Micro/Pico BTS TDD
LTE1729 FWHE 41 2600MHz 5W 2575 - 2635 40MHz 2x2
LTE 2600 MHz Narrow Band
FWND BC40 Flexi Zone Micro/Pico BTS TDD
LTE2290 FWND 40 2300MHz 5W 2300 - 2400 40MHz 2x2
LTE 2300 MHz
FWHT 41 2600MHz 5W 2496 - 2690 40MHz 2x2 FWHT FZ BTS 2600 TDD B41 w/PoE
LTE2821 FWHTLB 41 2600MHz 5W 2496 – 2593 40MHz 2x2 FWHT FZ BTS 2600 TDD B41 w/PoE
FWHTHB 41 2600MHz 5W 2593 - 2690 40MHz 2x2 FWHT FZ BTS 2600 TDD B41 w/PoE

112 © Nokia 2018 Nokia Internal Use

 LTE3020
Introduction and Technical Details
[TDD] FZ Hardware supporting 256QAM in DL (3/3)

Indoor Pico
Feature 3GPP Max Output RX Band TX Band Max BW Antenna
Variant Spectrum Description
ID Band power per TX (MHz) (MHz) (MHz) config
FWNA BC40 Flexi Zone Indoor Pico BTS TDD
LTE2092 FWNA 40 2600MHz 250mW 2300 – 2400 40MHz 2x2
LTE 2300 MHz + WiFi
FWNB BC40 Flexi Zone Indoor Pico BTS TDD
LTE2092 FWNB 40 2300MHz 250mW 2300 – 2400 40MHz 2x2
LTE 2300 MHz
FWNC BC40 Flexi Zone Indoor Pico BTS TDD
LTE2092 FWNC 40 2300MHz 250mW 2300 - 2400 40MHz 2x2
LTE 2300 MHz w/ Ext Ant
250
LTE3168 FW2QD 3500MHz 250mW 3550-3700 40MHz 2x2 B250 MBI FZ BTS (FW2QD)
(CBRS)
40 2300MHz 250mW 2320 – 2370 B40+B41 MBI FZ Multiband Indoor Pico
LTE3169 FW2NHA 40MHz 2x2
41 2600MHz 250MW 2575 - 2635 (FW2NHA)

Note: List of FZM HW given on slides concerns existing FZM HW that supports 256QAM. Newer HW is expected to support 256QAM as well.

113 © Nokia 2018 Nokia Internal Use

 NETWORK
ENGINEERING

LTE4064
256 QAM enhancements

114 © Nokia 2018 Nokia Internal Use

LTE4064 256 QAM enhancements
Table of contents

Introduction Technical Inter – Benefits and Configuration

Details dependencies Gains Management
Motivation and Feature Detailed Functionality Simulation, Lab and Field Parameters and
Interdependencies with
Overview Description Findings Parameterization
other features and
functions Scenarios
1

Deployment Performance
Aspects Aspects
Activation, Configuration Counters and KPIs,
Examples, Fault Mgmt, Feature Impact Analysis
Trial Area and Verification

115 © Nokia 2018 Nokia Internal Use

LTE4064 256 QAM enhancements

Introduction

Table of contents

<chapter:introduction>

116 © Nokia 2018 Nokia Internal Use

Introduction
Feature motivation

• Currently (pre-FL18A), 256QAM capable UE is

Initial context setup
configured with 256QAM configuration (MCS/CQI
tables suited for UE in good radio conditions)
256QAM related config.

Period to change MCS/CQI tables

Throughput eNB with
• As a consequence, UE in bad radio conditions (~QPSK degradation enabled
256QAM in
256QAM in DL
experienced due
related area in MCS/CQI tables) needs to wait for capable UE to lower
DL

granularity of
configured period to be downgraded to use legacy on cell edge
256QAM tables
tables (introduced via LTE3073 in FL17A) around QPSK
area
- Table change (via RRC Connection Reconfiguration) can occur the
earliest after 15 seconds (lowest possible configuration before
FL18A) and in addition there is higher probability of failure due to RRC Connection reconfiguration
bad radio conditions (switch to 64QAM tables)

117 © Nokia 2018 Nokia Internal Use

Introduction
Feature in brief
Feature is an enhancement of LTE3073 introduced in xL17A
• With this feature, UE that is capable of 256QAM in DL is initially configured
with legacy MCS/CQI tables (64QAM related) 64QAM in
DL capable UE
• Also, new parameter is introduced to allow earlier switch of 64QAM In i t i a
l cont
MCS/CQI tables right after initial context setup to 256QAM MCS/CQI tables ext se
t up
(if UE is in very good radio conditions)
- Algorithm (logic) known from LTE3073 is unchanged, new parameter 64QA
M rel
ated c
to additionally supervise just initial transition is introduced o nfig.

• Timer range of legacy parameter (from LTE3073) is extended to be aligned setu

p eNB with
text enabled
with new one (from LTE4064) i al con
In it 256QAM in
- Minimum value is 1 sec (compared to 15 sec from LTE3073) . DL
co nfig
ted
• LTE4064 doesn’t introduce separate activation flag, it reuses activation flag from rela
AM
LTE3073 64Q
256QAM in
- Functionality of LTE3073 is overwritten by enhancements coming from LTE4064 just DL capable UE
after SW upgrade to FL18A
• New counters are introduced to monitor transitions between
64QAM  256QAM tables and total time with 256QAM tables
118 © Nokia 2018 Nokia Internal Use
Introduction
Before & after LTE4064

Before After
• After Initial context setup UE is configured with • After Initial context setup UE is configured with
256QAM related configuration 64QAM related configuration
• Configuration can be changed after configured • Configuration can be changed after configured
period (minimum 15 sec) (if UE is in bad radio period
conditions) • New parameter to potentially perform initial transition to
256QAM tables earlier (e.g. initial change after 1 sec but any
subsequent every 7 sec)
• Range for period extended with even 1 sec
Initial context setup
Initial context setup

256QAM in 256QAM related config.

eNB with
DL capable UE 256QAM in 64QAM related config. eNB with
enabled
DL capable UE enabled
256QAM in
256QAM in
DL
DL

119 © Nokia 2018 Nokia Internal Use

LTE4064 256 QAM enhancements

Technical Details

Table of contents

120 © Nokia 2018 Nokia Internal Use

Technical Details
In LTE4064, legacy tables
Algorithm for radio conditions evaluation – LTE3073 vs LTE4064
are used at the beginning
• Algorithm from LTE3073 used to determine
Good/Bad/Neutral radio conditions is unchanged

1. Each MCS sample within evaluation period is marked as Good, Bad

or Neutral (based on configurable thresholds)
2. With expiration of evaluation period (initial or any subsequent) it is
checked whether CQI/MCS tables upgrade or downgrade is needed
• Upgrade if 64QAM tables are used and from at least 10 MCS
samples 80% is Good
• Downgrade if 256QAM are used and from at least 10 MCS
samples 80% is Bad Legacy
• New
In any other case do not change tables tables
used configurable
timer

LTE3073 reference:
https://webnei.emea.nsn-net.net/#/webnei/5a55f32747230100125247db/6
7
121 © Nokia 2018 Nokia Internal Use
Technical Details
Default configuration change (1/3)

There are two cases to be studied where default configuration change

brings different behavior compared to pre-FL18A

256QAM UE in bad radio conditions 256QAM UE in very good radio conditions

during initial access during initial access
• In such scenario introduced change brings • The only negative impact (THP) could be seen if radio
the highest gain conditions are that good that UE could benefit purely
• UE doesn’t need to perform Reconfiguration from 256QAM modulation from very beginning of
(being in poor radio conditions) as 64QAM data transmission
config is being used • Above is however mitigated with new parameter
(initial decision period) that can be much shorter than
in previous releases
• If UE is in good enough conditions within initial
decision period, it can be quickly reconfigured to use
256QAM config.

122 © Nokia 2018 Nokia Internal Use

 Technical Details
Default configuration change – 256QAM UE in bad radio conditions during initial access (2/3)
• Pre FL18A:
- In this scenario, UE from the beginning is using not optimal in this case 256QAM related MCS/CQI tables
- Need for RRC Connection Reconfig. after 1 st decision period (minimum 15sec long) due to bad radio conditions
• FL18A onwards (LTE4064):
- UE from the beginning is using 64QAM related MCS/CQI tables. MCS/TBS can be better suited for such a UE
- Initial decision period (LNCEL:iniDl256QamChQualEst  that can be shorter than following ones) verifies whether switch to 256QAM
is required
- This new timer is used only once, each subsequent period is controlled with legacy timer known form LTE3073

Pre FL18A (start with 256QAM tables) FL18A onwards (start with 64QAM tables)
Switch to 64QAM config Switch to 256QAM config Switch to 256QAM config

MCS MCS

Good channel Good channel

Conditions threshold Conditions threshold

Bad channel Bad channel

conditions threshold conditions threshold

time time

Decision period for channel quality estimarion Decision period for 1st Decision period for 2nd and further
(15sec as minimum value). The same value for all periods channel quality channel quality estimations (new
estimation can be shorter values available: 1, 2, 3, 5, 7, 10 … sec)
(e.g. 1sec)
123 © Nokia 2018 Nokia Internal Use
 Technical Details
Default configuration change – 256QAM UE in very good radio conditions during initial access
(3/3)
• Pre FL18A:
- In this scenario, UE from the beginning is using 256QAM related MCS/CQI tables
- No need for RRC Connection Reconfig. as it is already in use. Decision period with at minimum 15 sec interval
• FL18A onwards (LTE4064):
- UE from the beginning is using not optimal in this case 64QAM related MCS/CQI tables
- Upon Initial decision period expiration (LNCEL:iniDl256QamChQualEst  that can be shorter than following ones) tables can be
changed to 256QAM ones with RRC Connection Reconfiguration even 1 sec after initial setup
- This new timer is used only once, each subsequent period is controlled with legacy timer known form LTE3073

Pre FL18A (start with 256QAM tables) FL18A onwards (start with 64QAM tables)
Switch to 64QAM config Switch to 256QAM config

MCS MCS

Good channel Good channel

Conditions threshold Conditions threshold

Bad channel Bad channel

conditions conditions
threshold threshold

time time

Decision period for channel quality estimarion Decision period for 1st Decision period for 2nd and further channel
(15sec as minimum value). The same value for all periods channel quality quality estimations (new values available: 1,
estimation can be shorter 2, 3, 5, 7, 10 … sec)
(e.g. 1sec)
124 © Nokia 2018 Nokia Internal Use
LTE4064 256 QAM enhancements

Interdependencies

Table of contents

<chapter:interdependencies>

125 © Nokia 2018 Nokia Internal Use

Interdependencies

prerequisites LTE2479 – 256QAM in downlink

LTE3073 – 256QAM extensions
LTE4064 is applicable only, if both LTE2479 and LTE3073 are
activated.
If LTE3073 is disabled (and LTE2479 enabled) , UE is
initially configured with 256QAM configuration as before
with no possibility to switch to 64QAM config.

126 © Nokia 2018 Nokia Internal Use

LTE4064 256 QAM enhancements

Benefits and Gains

Table of contents

<chapter:benefits_and_gains>

127 © Nokia 2018 Nokia Internal Use

Benefits and Gains
Executive summary

• LTE4064 aims to improve CDR (Call Drop Rate) that could happen for 256QAM capable
UEs accessing the network in bad radio conditions (cell edge)
- Risk that RRC Connection Reconfiguration (triggered to downgrade CQI/MCS tables to 64QAM related) for such a
UE will end up with drop
• To avoid keeping 256QAM UE being in very good radio conditions with 64QAM related
tables, new parameter to allow faster initial switching to 256QAM tables is introduced
- Extended parameter range gives more freedom in optimization to find best configuration not only for initial
transition but also for any subsequent one

128 © Nokia 2018 Nokia Internal Use

LTE4064 256 QAM enhancements

Configuration
Management
Table of contents

<chapter:configuration_management>

129 © Nokia 2018 Nokia Internal Use

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

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

130 © Nokia 2018 Nokia Internal Use

 Configuration Management
New/Related parameters

Abbreviated name Full name Description Range and step Default

LNCEL:iniDl256QamChQualEst Initial decision period for channel Initial decision period for channel quality estimation. 1,2,3,5,7,10,15, 1
w!

quality estimation 30,60,120,240

Ne

LNCEL:perDl256QamChQualEst Decision period for channel Decision period for channel quality estimation. 1,2,3,5,7,10,15, 60
quality estimation 30,60,120,240

LNCEL:actDl256QamChQualEst Activate channel quality This parameter activates the channel quality 0 (false), 1 (true) 0
monitoring for 256QAM usage monitoring for 256QAM usage.

MCS threshold for deactivating MCS threshold for deactivating 256QAM for the UE. from 9 to 15, step 1 13
256QAM for the UE. Value refers Value refers to legacy MCSs so it needs to be
LNCEL:dl256QamDeactChQualThr
to legacy MCSs so it needs to be converted eNB internally.
converted eNB internally.
MCS threshold for reactivating MCS threshold for reactivating 256QAM for the UE. from 18 to 24 step 1 22
LNCEL:dl256QamReactChQualThr 256QAM for the UE. Value refers Value refers to legacy MCSs.
to legacy MCSs.

All above-mentioned parmaeter are On-line modifiable

131 © Nokia 2018 Nokia Internal Use

LTE4064 256 QAM enhancements

Deployment
Aspects
Network graphic boxes Network element boxes
Table of contents

<chapter:deployment_aspects>

132 © Nokia 2018 Nokia Internal Use

Deployment Aspects
Feature activation Tests & Pilots

• LTE4064 is extension of 256QAM feature, thus basic LTE2479 needs to be activated first:
- LNCEL:actModulationSchemeDl = 256QAM
• Feature doesn’t introduce new
activation flag, LTE3073 activation
flag is reused from FL18A onwards
- LNCEL:actDl256QamChQualEst = True

• „Good” and „Bad” switch thresholds configuration (defaults shown):

- LNCEL:dl256QamDeactChQualThr
- LNCEL:dl256QamReactChQualThr

• Monitoring periods (initial and all the others) configuration (defaults shown):
- LNCEL:iniDl256QamChQualEst (xL18A BTS SM not available yet to show this parameter) – 1 sec default value
- LNCEL:perDl256QamChQualEst

133 © Nokia 2018 Nokia Internal Use

Deployment Aspects
Feature activation Tests & Pilots

Selection of proper trial area is critical to show feature gains

• Proper area in terms of this feature means decent share of 256QAM capable UEs
vs.
being in conditions that favor legacy CQI/MCS tables
(e.g. cell edge UEs)
KPIs/counters for area verification
• UE capabilities check:
- UEs of Categories 11, 12 or DL UE Categories 11 onwards are the ones potentially LTE_5985a Active UEs with UE Category
11 Distribution Ratio
considered to support 256QAM LTE_5696a Active UEs with UE Category
• DL UE category 13, 14 and 17 must support 256QAM, for remaining categories mentioned above it is 12 Distribution Ratio
optional KPIs: Active UEs with DL UE Category
11-19 Distribution Ratio
• Share of UEs at the cell edge can be verified using MCS histogram counters
PDSCH_TRANS_USING_MCS0 -
- The more histogram is shifted towards lower MCSs, more likely UEs are on the cell edge PDSCH_TRANS_USING_MCS28

134 © Nokia 2018 Nokia Internal Use

Deployment Aspects
Feature activation Tests & Pilots

• Feature also introduces new counters to monitor switches between 64  256 QAM related tables
(M8007C20 - M8007C24):
- DWGRADE_256QAM_ATT & DWGRADE_256QAM_SUCC  RRC Conn. Reconfig. Att./Succ. for downgrade from
256QAM
- UPGRADE_256QAM_ATT & UPGRADE_256QAM_SUCC  RRC Conn. Reconfig. Att./Succ. for upgrade to 256QAM
- UE_ACTIVE_TIME_256QAM  Total active time of 256QAM scheduled UEs
• Looking at above counters it can be said what is the quantity and quality of performed reconfigurations
(attempts & success ratio)
- As 64QAM tables are default ones, expected could be to see more „upgrades” than „downgrades” (opposite to pure
LTE3073 however due to lack of counters at that time it is hard to compare it directly)
- Upgrades happen for UEs that are in very good radio conditions. Once UE becomes 256QAM configured, it needs very bad
radio conditions to be downgraded (80% of MCSs below configured threshold – default 13 – within evaluation period)
- UE won’t be upgraded until 80% of MCSs are above configured threshold – default 22 – within evaluation period
- From time related counter average duration of session with 256QAM related tables can be derived
• Positive impact can be seen on KPI related to drop ratio (gain depends on share of 256QAM capable UEs):
- Drop Ratio due to RNL due to loss of connection to the UE cause initiated by eNB (LTE_5090)

135 © Nokia 2018 Nokia Internal Use

LTE4064 256 QAM enhancements

Performance
Aspects
Table of contents

<chapter:performance_aspects>

136 © Nokia 2018 Nokia Internal Use

Performance Aspects
Executive summary
With this feature 5 counters are introduced that
ease monitoring of upgrading/downgrading functionality

• From 4 new counters it is possible to get KPIs for

Success Ratio of upgrading and downgrading procedure
(RRC Connection Reconfiguration) RRC Connection Reconfiguration DWGRADE_256QAM_ATT

• Respective counters are pegged together with transmission UPGRADE_256QAM_AT

T
of Reconfiguration messages, if the messages are send due
to upgrade/downgrade: DWGRADE_256QAM_SUCC
RRC Connection Reconfiguration
- RRC Connection Reconfiguration  attempts Complete UPGRADE_256QAM_SUC
- RRC Connection Reconfiguration Complete  successes C

UE_ACTIVE_TIME_256QA
M • One additional counter counts time
when UEs are scheduled using
Initial setup
t 256QAM related CQI/MCS tables
Reconfiguration Reconfiguration UE goes to IDLE
(64QAM tables) to 256QAM tables to 64QAM tables
137 © Nokia 2018 Nokia Internal Use
Performance Aspects
New counters

Counter name Description

DWGRADE_256QAM_ATT This counter provides the total number of RRC Connection Reconfiguration attempts for
(M8007C20) downgrade from the 256QAM table (according to 3GPP TS36.213).
#LTE Radio Bearer Trigger event: This counter is updated only on the PCell when the RRC Connection
Reconfiguration message is sent from the eNB to the UE due to the downgrade from the
256QAM table.
Use case: Performance monitoring of switches between new legacy CQI/MCS tables

RRC Connection
DWGRADE_256QAM_SUCC
Reconfiguration Success Ratio ×100%
(LTE_6600a) =
for downgrade from 256QAM DWGRADE_256QAM_ATT
table

138 © Nokia 2018 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

DWGRADE_256QAM_SUCC This counter provides the total number of successful RRC Connection Reconfiguration
(M8007C21) downgrades from the 256QAM table (according to 3GPP TS36.213).
#LTE Radio Bearer Trigger event: This counter is updated only on the PCell when the RRC Connection
Reconfiguration Complete message is received by the eNB from the UE due to the
downgrade from the 256QAM table.
Use case: Performance monitoring of switches between new legacy CQI/MCS tables

RRC Connection
DWGRADE_256QAM_SUCC
Reconfiguration Success Ratio ×100%
(LTE_6600a) =
for downgrade from 256QAM DWGRADE_256QAM_ATT
table

139 © Nokia 2018 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

UPGRADE_256QAM_ATT This counter provides the total number of RRC Connection Reconfiguration attempts for
(M8007C22) upgrade to the 256QAM table (according to 3GPP TS36.213).
#LTE Radio Bearer Trigger event: This counter is updated only on the PCell when the RRC Connection
Reconfiguration message is sent from the eNB to the UE due to the upgrade to the
256QAM table.
Use case: Performance monitoring of switches between new legacy CQI/MCS tables

RRC Connection
UPGRADE_256QAM_SUCC
Reconfiguration Success Ratio ×100%
(LTE_6601a) =
for upgrade to UPGRADE_256QAM_ATT
256QAM table

140 © Nokia 2018 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

UPGRADE_256QAM_SUCC This counter provides the total number of successful RRC Connection Reconfiguration
(M8007C23) upgrades to the 256QAM table (according to 3GPP TS36.213).
#LTE Radio Bearer Trigger event: This counter is updated only on the PCell when the RRC Connection
Reconfiguration Complete message is received by the eNB from the UE due to the
upgrade to the 256QAM table.
Use case: Performance monitoring of switches between new legacy CQI/MCS tables

RRC Connection
UPGRADE_256QAM_SUCC
Reconfiguration Success Ratio ×100%
(LTE_6601a) =
for upgrade to UPGRADE_256QAM_ATT
256QAM table

141 © Nokia 2018 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

UE_ACTIVE_TIME_256QAM This counter provides the total amount of active time spent by UEs using the 256QAM table.
(M8007C20)
Trigger event: This counter is updated only on the PCell based on the time between:
#LTE Radio Bearer 1. RRC Connection Reconfiguration Complete (upgrade to 256QAM table) and RRC Connection Release
2. RRC Connection Reconfiguration Complete (upgrade to 256QAM table) and RRC Connection Reconfiguration
Complete (downgrade from 256QAM table)
3. 3) RRC Connection Reconfiguration Complete (upgrade to 256QAM table) and RRC Connection
Reconfiguration (HO Command)
4. RRC Connection Reconfiguration Complete (upgrade to 256QAM table) and RRC Connection Re-establishment
(legacy CQI table)
Use case: Showing average 256QAM scheduled session duration

Average scheduled session UE_ACTIVE_TIME_256QAM

duration of 256QAM-scheduled (LTE_6602a) =
UEs UPGRADE_256QAM_SUCC

142 © Nokia 2018 Nokia Internal Use

Performance Aspects
Feature impact
Feature impact How to measure?
Drop ratio due to RNL (loss of connection to the UE cause) KPIs:
can improve - LTE_5090f E-RAB drop ratio due to radio network layer (RNL) due
As with LTE4064 all UEs are initially configured with legacy to loss of connection to the UE cause initiated by eNB
CQI/MCS tables there is lower possibility that UE is dropped
(256QAM tables are suited for UEs in good radio conditions)
Imact proportional to amount of 256QAM capable Ues on the
cell edge

143 © Nokia 2018 Nokia Internal Use

 Extra High Value Feature

NETWORK
ENGINEERING

LTE4054
Dynamic Power Back-off

144 © Nokia 2018 Nokia Internal Use

LTE4054 Dynamic Power Back-off
Table of contents

Introduction Technical Inter – Benefits and Configuration

Details dependencies Gains Management
Motivation and Feature Detailed Functionality Simulation, Lab and Field Parameters and
Interdependencies with
Overview Description Findings Parameterization
other features and
functions Scenarios
1

Deployment Performance
Aspects Aspects
Activation, Configuration Counters and KPIs,
Examples, Fault Mgmt, Feature Impact Analysis
Trial Area and Verification

145 © Nokia 2018 Nokia Internal Use

LTE4054 Dynamic Power Back-off

Introduction

Table of contents

<chapter:introduction>

146 © Nokia 2018 Nokia Internal Use

Introduction
Error Vector Magnitude recap

Error Vector Magnitude (EVM) is B

A Q
a measure that determines how far are the
transmitted modulation symbols from its ideal •
representation on the constellation diagram *
00001000 *
allowed EVM
Imperfections of the transmitter lead to the
deviations in modulated signal
B
* *
The higher the modulation order, the more I
stringent the EVM is
For 256QAM, EVM defined by 3GPP, should
not be higher than 3.5% A Error vector

Error Vector Magnitude

147 © Nokia 2018 Nokia Internal Use

Introduction
Power back-off recap

The goal of the power back-off is to reduce the maximum

configured output power with the value that will guarantee the PA power [W]
EVM not higher than 3.5% for 256QAM transmission Max PA power
Power back-off
Power back-off value depends on the PA (Power Amplifier) characteristic as
well as used configuration (it depends on, among others, number of carriers per
PA)
Power back-off is applicable when PA that is handling the cell where 256QAM
is used, is allowed to use the maximum supported power (for LTE,
LNCEL:pMax is set to maximum supported PA power)
- When cell with 256QAM enabled is handled by PA that is shared between
multiple carriers and sum of all carriers powers is equal to maximum
supported power of the PA, the recommended power back-off value defined
for multiple carrier scenario should be used for each carrier handled by this
Before power After power
PA back-off is used back-off is used

148 © Nokia 2018 Nokia Internal Use

Introduction
Feature motivation
To comply with stringent 3GPP requirements regarding EVM
(Error Vector Magnitude) usage of Power back-off is recommended*
• The higher transmitted power, the higher EVM is experienced
− The transmitted power is proportional to the load in the TTI
− The EVM <= 3.5% can not be guaranteed when the Power Amplifier (PA) works with
3GPP 36.104
the maximum supported output power
• Exceeded allowed EVM leads to the lower probability of 256QAM usage
(worse performance than possible) Exceeded EVM
value reduces the
• Up to xL18A, it was possible to manually set back-off value, accordingly to chance of 256QAM
used Radio Module usage, thus also
• Drawback of this is that reduction applies for all channels and modulation peak throughout is
schemes all the time, no matter if required or not reduced
Note: *Usage of power back-off is not mandatory. No checks are done by Nokia eNB, if recommended power back-off value is configured.

149 © Nokia 2018 Nokia Internal Use

Introduction
LTE4054 in brief
Dynamic power back-off is introduced to be applied only if needed

• To achieve limit of 3.5% EVM, power back-off will be calculated and applied per
TTI basis (if needed)
- Upper threshold for power back-off is configurable TTI1 Back-off: 0.6dB

• TTIs with decent number of used PRBs and EVM critical modulation and TX TTI2 Back-off: 1.0dB
schemes are subject of dynamic power back-off application
TTI3 NO back-off (0dB)
- With small load there is no need to use power back-off even for 256QAM scheduled UE (PA
doesn’t work with its max power) TTI4 Back-off: 1.4dB
• Out of 7 new parameters, 5 are strictly related to configuration of this feature TTI5 NO back-off (0dB)
behaviour (they are put into new structure):
- … …
Maximum possible power back-off that can be applied (two values/levels)
- Preference of using second (higher) value/level for power back-off TTIn Back-off: 2.0dB
- Threshold for applying power back-off
- Applicability of power back-off (in terms of modulation)
• Feature has its dedicated activation flag
150 © Nokia 2018 Nokia Internal Use
Introduction
Before & after LTE4054

Before After
• Static power back-off applied for all UEs in the cell • Power back-off applied only in TTIs where it is
(even if UE doesn’t need it) required due to:
• Power of all channels is reduced • High load, and
• High number of UEs with EVM critical modulation
and TX scheme
• Not on all channels power is reduced

Static back-off value

Configured max. back-off
Back-off
value

Back-off
value
Applied back-off varies
based on current need
t
t

151 © Nokia 2018 Nokia Internal Use

LTE4054 Dynamic Power Back-off

Technical Details

Table of contents

152 © Nokia 2018 Nokia Internal Use

Technical Details
Intro information / dual carrier case

Dynamic power back-off is evaluated and applied on cell level only

• It means that, in case of dual carrier operation

(LTE-LTE or LTE-WCDMA/GSM), the power Even though one out of 2
consumption or PRB allocation of other carriers under PA is not
carrier is not considered loaded at all, back-off still
can be applied if second
• Above can lead to situations when power
carrier decides (based on
back-off is unnecessarily applied
LTE4054 algorithm) to apply
dynamic back-off

153 © Nokia 2018 Nokia Internal Use

Technical Details
Intro information / dual carrier case

Even though back-off can be unnecessarily applied in dual carrier case,

still advantage over legacy static back-off can be noticed
LTE Freq. 1 (low load)
43dBm (20W) • In case that Freq. 1 is very little loaded and
Freq. 2 is highly loaded (with EVM critical
modulation and TX scheme), back-off will be
applied to LTE Freq. 2
• It wouldn’t be required as on Freq. 1 max
power of 20W is not utilized, thus any
RF with compensation on Freq. 2 is also not
single PA needed
(max P=40W) LTE Freq. 2 (high load)
43dBm (20W) • Nonetheless, such behavior is still better than
legacy as lower value can be applied
compared to static value and
154 © Nokia 2018 Nokia Internal Use only to 1 carrier
Technical Details
Power back-off applicability

It can be configured (LNCEL/dlPwBackoffStructure/dlPwBackoffApp) whether power reduction applies to:

• All PRBs within given TTI (including PRBs scheduled with QPSK*), or
• Only PRBs using QAM modulation (16QAM, 64QAM, 256QAM)

If power reduction is used, it applies for: Power reduction does’t apply for:
- PDSCH data symbols depending on their modulation - PDCCH
scheme (see above) - PCFICH
- CRS and CSI-RS within the whole TTI - PHICH
(even if located in control channel area)
- PBCH / PSS and SSS
- NB-IoT / LTE-M PRBs

NOTE: in case of multiple layers (MIMO) or MU-MIMO (shared PRBs), worst case is taken, meaning if EVM critical modulation is used for one
codeword or part of shared PRB, whole codeword/PRB is considered as EVM critical
(even if other layer on that codeword or other PRB part use non EVM critical modulation, back-off will be applied to it)
*If power reduction is applied to PRBs using QPSK modulation, this applies also to SI, MSG2, MSG4, Paging etc. and thus the cell coverage is
reduced
155 © Nokia 2018 Nokia Internal Use
Technical details
Algorithm highlevel view PER TTI
1
Back-off necessity
verification (via
configurable threshold)

4 2
Back-off application Max. Back-off value
Configuration (considering PRBs to
which back-off don’t
selection (2 values
possible depending on
provisioning apply) config.)

3
PRB based effective
back-off calculation
(considering static back-
off)

156 © Nokia 2018 Nokia Internal Use

Technical Details
Dynamic back-off algorithm overview
• EVM Critical Modulations and TX schemes are Structure for new power back-off related parameters:
assumed to be: LNCEL/dlPwBackoffStructure/
- 256QAM with any Rank (1,2,3,4)
usageOfMaxDlPw
maxDlPwBackoffValue1 maxDlPwBackoffValue2
- 64QAM with Ranks 3 or 4 BackoffValue2

• In each TTI it is checked how many PRBs are

scheduled as EVM critical None NOT USED
- If percentage of PRBs with EVM critical is higher than configured
threshold, back-off is calculated and applied to that TTI Apply if:
Apply if: • 256QAM (Rank 3, 4)
• Depending on configuration, one or two maximum QAM256r3r4 • 64QAM (Rank 3, 4) is used in more PRBs than
back-off thresholds can be set • 256QAM (any Rank) threshold
is used in more PRBs
- First one always exists and is applicable if share of transmissions than threshold
Apply if:
with 256QAM or 64QAM with ranks 3,4 is above configured • 256QAM (any Rank)
threshold QAM256r2r3r4 is used in more PRBs than
- threshold
Second is optional and applies if share of transmissions with
256QAM only (if configured) is above configured threshold.
If configured, must be higher than first threshold

157 © Nokia 2018 Nokia Internal Use

Technical Details
Back-off value calculation (1-2/4)
• Let’s say usageOfMaxDlPwBackoffValue2 is Structure for new power back-off related parameters:
configured with value „QAM256r3r4” LNCEL/dlPwBackoffStructure/
- In that case both Max back-off values (VALUE 1 and VALUE usageOfMaxDlPw
maxDlPwBackoffValue1 maxDlPwBackoffValue2
2) must be configured where VALUE 2 > VALUE 1 BackoffValue2
(VALUE 1) (VALUE 2)
(CONFIG.)
Per each TTI, it is checked if percentage of EVM critical
PRBs crosses configured threshold:
None NOT USED
• LNCEL/dlPwBackoffStructure/dlPwBackoffThreshold

If above threshold is crossed, decision which Apply if:

Apply if:
• 256QAM (Rank 3, 4)
maximum value to choose is taken: QAM256r3r4 • 64QAM (Rank 3, 4)
• 256QAM (any Rank)
is used in more PRBs than
threshold
is used in more PRBs
a) Verified is rule for applicability of VALUE 2. If it than threshold
match: Apply if:
• 256QAM (any Rank)
- maximum back-off VALUE 2 is used QAM256r2r3r4 is used in more PRBs than
threshold
b) If threshold doesn’t match with rule for VALUE 2
application:
- Maximum back-off VALUE 1 is used
158 © Nokia 2018 Nokia Internal Use
 Technical Details
Used PRBs
Back-off value calculation (3/4) (20MHz)
100 0.00
96 0.18
92 0.36
Once maximum back-off value is decided, 88 0.56
PRB based effective value can be calculated 84 0.76
80 0.97
• Effective power back-off (PRB based) is approximation of final 76 1.19
72 1.43
back-off to be applied and is selected taking into account: 68 1.67
- Maximum back-off value (Value 1 or Value 2 from previous slides) 64 1.94
60 2.22
- PDSCH utilization (considering LTE-M / NB-IoT) 56 2.52
52 2.84
and is expressed as: 48 3.19
44 3.57

[
𝑑𝑙𝑃𝑤𝐵𝑎𝑐𝑘𝑜𝑓𝑓 𝑃𝑅𝐵=𝑚𝑎𝑥 𝑑𝑙𝑃𝑤𝐵𝑎𝑐𝑘𝑜𝑓𝑓 𝑢𝑠𝑒𝑑𝑚𝑎𝑥 −10 𝑙𝑜𝑔 [ 𝑑𝑙𝐶h𝐵𝑤 [ 𝑃𝑅𝐵𝑠 ] +¿ 𝑔𝑢𝑎𝑟𝑑𝑏𝑎𝑛𝑑 𝑐𝑎𝑟𝑟𝑖𝑒𝑟𝑠
𝑛𝑢𝑚𝑈𝑠𝑒𝑑𝑃𝑟𝑏𝑠 ] ]
;0
40
36
3.98
4.44
Calculated dynamic Max. possible back-off PRB utilization 32 4.95
back-off that can be applied ratio in TTI 28 5.53
24 6.20
dlChBw  each configured guardband NB-IoT carrier is added to total number of PRBs 20 6.99
numUsedPrbs  LTE-M and NB-IoT reserved PRBs are always treated as „used”. Empty legacy PDSCH 16 7.96
PRBs used for NB-IoT boosting are also considered as „used” PRBs 12 9.21
Guardband carriers  Each guardband carrier is added as 1 PRB 8 10.97
159 © Nokia 2018 Nokia Internal Use
4 13.98
 Technical Details
Back-off value calculation (3/4)

Static back-off can still exists and needs to be considered

by LTE4054 in algorithm
• Static value is considered within maximum DL power back-off values as follows:

𝑓𝑖𝑛𝑎𝑙max ⁡𝑣𝑎𝑙𝑢𝑒 1= 𝑚𝑎𝑥 [ 𝑚𝑎𝑥𝐷𝑙𝑃𝑤𝐵𝑎𝑐𝑘𝑜𝑓𝑓𝑉𝑎𝑙𝑢𝑒 1 − 𝑠𝑡𝑎𝑡𝑖𝑐 𝑏𝑎𝑐𝑘𝑜𝑓𝑓 ; 0 ] If static back-off is

higher than or equal
𝑓𝑖𝑛𝑎𝑙max ⁡𝑣𝑎𝑙𝑢𝑒 2=𝑚𝑎𝑥 [ 𝑚𝑎𝑥𝐷𝑙𝑃𝑤𝐵𝑎𝑐𝑘𝑜𝑓𝑓𝑉𝑎𝑙𝑢𝑒 2 − 𝑠𝑡𝑎𝑡𝑖𝑐 𝑏𝑎𝑐𝑘𝑜𝑓𝑓 ; 0 ]
to configured max
value (1 or 2
depending on config.),
[
𝑑𝑙𝑃𝑤𝐵𝑎𝑐𝑘𝑜𝑓𝑓 𝑃𝑅𝐵=𝑚𝑎𝑥 𝑑𝑙𝑃𝑤𝐵𝑎𝑐𝑘𝑜𝑓𝑓 𝑢𝑠𝑒𝑑𝑚𝑎𝑥 −10 𝑙𝑜𝑔 [ 𝑑𝑙𝐶h𝐵𝑤 [ 𝑃𝑅𝐵𝑠 ] +¿ 𝑔𝑢𝑎𝑟𝑑𝑏𝑎𝑛𝑑 𝑐𝑎𝑟𝑟𝑖𝑒𝑟𝑠
𝑛𝑢𝑚𝑈𝑠𝑒𝑑𝑃𝑟𝑏𝑠 ] ]
;0
calculation of
dynamic back-off is
skipped
If Value 1 and/or Value 2 are set to 0, above calculation is omitted

160 © Nokia 2018 Nokia Internal Use

Technical Details
Back-off value calculation (4/4)

Final back-off value (to be applied) includes correction considering

PRBs/symbols to which back-off is not applied
• Following list contains PRBs for which power is NOT reduced: PRB
24 PDSC
- PRBs used by inband NB-IoT cells 23 H
- Empty PRBs used by inband/guardband NB-IoT cells for power boosting …
of NB-IoT carriers 15
14

PD
- PRBs used by LTE-M

PSS/
H
13

CC
- PRBs with PDSCH transmission using QPSK in case 12 PBCH

S
dlPwBackoffApp =”QAMonly„ 11

SS
10
• Additionally, for following signals power is NOT reduced PBCH 9
 occupies 4 symbols across 6 PRBs …
- PSS/SSS  occupies 2 symbols across 6 PRBs 1
0
Sym. 1 2 … 6 7 8 9 10 11 … 14

161 © Nokia 2018 Nokia Internal Use

Technical Details
Back-off value calculation / examples Used PRBs
(20MHz)
100 0.00
96 0.18
Back-off calculation examples (No NB-IoT/LTE-M or static back-off): 92
88
0.36
0.56
1. BW=20MHz, configured max. back-off=1.5dB, PRB util.=96% 84 0.76
80 0.97
• At least 72% PRB utilization required to apply any back-off 76 1.19
𝑑𝑙𝑃𝑤𝐵𝑎𝑐𝑘𝑜𝑓𝑓 𝑃𝑅𝐵=𝑚𝑎𝑥 [ 1.5 𝑑𝐵 −0.18 ; 0 ] =𝟏 . 𝟑𝟐 𝒅𝑩 72 1.43
68 1.67
2. BW=20MHz, configured max. back-off=2dB, PRB util.=84% 64 1.94
• At least 64% PRB utilization required to apply any back-off 60 2.22
56 2.52
𝑑𝑙𝑃𝑤𝐵𝑎𝑐𝑘𝑜𝑓𝑓 𝑃𝑅𝐵=𝑚𝑎𝑥 [ 2 𝑑𝐵− 0.76 ; 0 ] =𝟏 . 𝟐𝟒 𝒅𝑩 52 2.84
48 3.19
3. BW=20MHz, configured max. back-off=1.7dB, PRB util.=64% 44 3.57
• At least 68% PRB utilization required to apply any back-off 40 3.98
𝑑𝑙𝑃𝑤𝐵𝑎𝑐𝑘𝑜𝑓𝑓 𝑃𝑅𝐵=𝑚𝑎𝑥 [ 1.7 𝑑𝐵 −1.94 ; 0 ] =𝟎 𝒅𝑩 36 4.44
32 4.95
4. BW=20MHz, configured max. back-off=3dB, PRB util.=52% 28 5.53
24 6.20
• At least 52% PRB utilization required to apply any back-off 20 6.99
𝑑𝑙𝑃𝑤𝐵𝑎𝑐𝑘𝑜𝑓𝑓 𝑃𝑅𝐵=𝑚𝑎𝑥 [ 3 𝑑𝐵 −2.84 ; 0 ] =𝟎 . 𝟏𝟔 𝒅𝑩 16 7.96
12 9.21
8 10.97
4 13.98

162 © Nokia 2018 [

𝑑𝑙𝑃𝑤𝐵𝑎𝑐𝑘𝑜𝑓𝑓 𝑃𝑅𝐵=𝑚𝑎𝑥 𝑑𝑙𝑃𝑤𝐵𝑎𝑐𝑘𝑜𝑓𝑓 𝑢𝑠𝑒𝑑𝑚𝑎𝑥 −10 𝑙𝑜𝑔
Nokia Internal Use [ 𝑑𝑙𝐶h𝐵𝑤 [ 𝑃𝑅𝐵𝑠 ]
𝑢𝑠𝑒𝑑 𝑃𝑅𝐵𝑠 ] ]
;0
Technical Details
Prevention from feature working

There are few possible cases in which feature won’t work even with feature
activation flag set to „True” (no consisteny check)

eNB can consider LTE4054 disabled

(even if enabled via flag: LNCEL/actDlPwBackoff=True) Rationale: In any of
provided that: presented case there
LNCEL/actModulationSchemeDl won’t be any PRBs
is set to 2:64QAM considered as EVM
LNCEL/actModulationSchemeDl OR and critical from
is set to 0:QPSK or 1:16QAM LNCEL/dlMimoMode
modulation and TX
is to ('0:SingleTx' or '10:TXDiv' or scheme perspective (i.e.
'11:4-way TXDiv' 64QAM with Rank 3,4 or
256QAM)

163 © Nokia 2018 Nokia Internal Use

LTE4054 Dynamic Power Back-off

Interdependencies

Table of contents

<chapter:interdependencies>

164 © Nokia 2018 Nokia Internal Use

Interdependencies

Interworking NB-IoT/LTE-M
with PRBs reserved for Inband NB-IoT as well as LTE-M are considered by LTE4054
NB-IoT/LTE-M threshold (are treated as „used” PRBs)
features Number of NB-IoT guardbands is added to total numer of PRBs [dlChBw + #
(except standalone NB-IoT)
guardband carriers)

If power is reduced due to LTE4054, NB-IoT/LTE-M channels are NOT affected

(only power for legacy LTE is reduced)

165 © Nokia 2018 Nokia Internal Use

Interdependencies

Interworking DL Power Boosting

with Boosted control channels are not affected by power reduction
DL power from LTE4054
boosting
Reference symbols power is reduced to the same extent as
PDSCH symbols

166 © Nokia 2018 Nokia Internal Use

Interdependencies

prerequisites LTE2479 – 256QAM in downlink

LTE4054 is intended to cope with EVM related mainly to
256QAM modulation, thus LTE2479 can be seen as obvious
prerequisite; however, it is not mandatory to have it
activated as back-off could be also applied based only on
64QAM modulation with high ranks (3 & 4)

167 © Nokia 2018 Nokia Internal Use

Interdependencies

limitations LTE819 DL inter-cell interference generation

As LTE819 is a testing feature it can’t be activated together
with LTE4054

168 © Nokia 2018 Nokia Internal Use

LTE4054 Dynamic Power Back-off

Benefits and Gains

Table of contents

<chapter:benefits_and_gains>

169 © Nokia 2018 Nokia Internal Use

Benefits and Gains
Executive summary

• LTE4054 brings great improvement over legacy methodology

with static power back-off
• With this feature, power is reduced only in TTIs that require it
to the extent of provided configuration
• Such mechanism controls in real-time EVM required to achieve high
throughput performance for demanding users
• Negative impact (due to reduced power) on users in the cell is
assumed to be low/negligible
- highest power reduction will happen only in case of really heavy PRB utilization
(>90%) and with UEs using EVM critical modulation and TX schemes
- Gain over static back-off solution expected

170 © Nokia 2018 Nokia Internal Use

LTE4054 Dynamic Power Back-off

Configuration
Management
Table of contents

<chapter:configuration_management>

171 © Nokia 2018 Nokia Internal Use

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

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

172 © Nokia 2018 Nokia Internal Use

Configuration Management
New parameters

Abbreviated name Full name Description Range and step Default

LNCEL/actDlPwBackoff Activate dynamic DL power This parameter is the activation flag of the feature DL 0 (false), 1 (true) 0
backoff dynamic power back-off.

LNCEL/dlPwBackoffStructure/… Structure for DL dynamic power Structure for hosting the configuration parameter for - -
back-off feature DL dynamic power back-off

…/dlPwBackoffApp Applicability of DL power back- This parameter value determines to which PRBs with 0: ALL; 1: QAMonly 1:
off modulation (QPSK and QAM) that back-off is applied. QAMonly
If dynamic DL power back-off is applied in case of
paired UEs in MU-MIMO scenarios it shall be applied
for the paired UEs disregard to the used modulation.
Same principle is uses for the single UE multi layers
case with different modulation schemes for the two
layers.
If sum of all PRBs per TTI with EVM limited higher from 0 to 100 step 1 50
order modulation schemes is above this defined
threshold parameter (calculated in % of the DL system
bandwidth), then a dynamic power back-off shall be
Threshold for applying DL power
…/dlPwBackoffThreshold applied . A PRB is considered as a PRB with EMV
backoff
limited higher order modulation scheme as soon as one
layer for multi-layer cases or as soon as one UE for
MU-MIMO cases is using an EVM limited higher
order modulation scheme.

173 © Nokia 2018 Nokia Internal Use

Configuration Management
New parameters

Abbreviated name Full name Description Range and step Default

This parameter defines the preference of the usage of 0: None 0: None
Usage Of maxdlPwBackoffValue2.
…/usageOfMaxDlPwBackoffValue2 1: QAM256r3r4
maxdlPwBackoffValue2
2: QAM256r1r2r3r4
This parameter defines the maximum DL power back- from 0 to 10.0 step 0.1 0
Maximum DL power backoff
…/maxDlPwBackoffValue1 off for 64QAM and/or 256 transmissions depending
value 1
on configuration.
This parameter defines the maximum DL power back- from 0 to 10.0 step 0.1 0
Maximum DL power backoff
…/maxDlPwBackoffValue2 off for 64QAM and/or 256 transmissions depending
value 2
on configuration.

usageOfMaxDlPwBackoffValue2 maxDlPwBackoffValue1 maxDlPwBackoffValue2

None NOT USED

Apply if:
Apply if: • 256QAM (Rank 3, 4)
QAM256r3r4
• 64QAM (Rank 3, 4) is used in more PRBs than threshold
• 256QAM (any Rank)
is used in more PRBs than threshold
Apply if:
• 256QAM (any Rank)
QAM256r2r3r4
is used in more PRBs than threshold

174 © Nokia 2018 Nokia Internal Use

LTE4054 Dynamic Power Back-off

Deployment
Aspects
Network graphic boxes Network element boxes
Table of contents

<chapter:deployment_aspects>

175 © Nokia 2018 Nokia Internal Use

Deployment Aspects
Feature Activation

To activate feature, its activation flag needs to be set to „True”

as well as configuration needs to be provided

Dedicated structure containing new parameters needs to be defined first:

New structure

• LNCEL/dlPwBackoffStructure/
• /usageOfMaxDlPwBackoffValue2 = None (Default)
• /maxDlPwBackoffValue1 = 0 (Default) Defaults prevent from
• /maxDlPwBackoffValue2 = 0 (Default) back-off calculation
• /dlPwBackoffThreshold = 50 (Default)
• /dlPwBackoffApp = QAMonly (Default)

Once strcuture exsists, Feature Activation flag can be set to „True”:

• LNCEL/actDlPwBackoff = True

176 © Nokia 2018 Nokia Internal Use

Deployment Aspects
Tests & Pilots

Selection of proper trial area is critical to show feature gains

• Proper area in terms of this feature means decent share of UEs using EVM critical modulation
vs.
and TX scheme (256QAM modulation and/or 64QAM modulation with ranks 3,4) generating
high load
• UE capabilities check: KPIs/counters for area verification

- UEs of Categories 11, 12 or DL UE Categories 11 onwards are the ones potentially considered to LTE_5985a Active UEs with UE Category
support 256QAM 11 Distribution Ratio
LTE_5696a Active UEs with UE Category
• DL UE category 13, 14 and 17 must support 256QAM, for remaining categories mentioned above it is 12 Distribution Ratio
optional
KPIs: Active UEs with DL UE Category
• Share of UEs using high RIs (>2) can be checked using dedicated KPIs 11-19 Distribution Ratio
- The more high RIs the better (it means many transmissions with high TX scheme) LTE_1669a % of MIMO Rank Indication
with value 3 reported by the UE
• High percentage of traffic using 256QAM modulation is also good indication for trial LTE_1520b % of MIMO Rank Indication
area selection with value 4 reported by the UE

• On top of that, PRB utilization needs to be high to see benefit from reduced power LTE_6263a % of PDSCH transmissions
using High MCS Codes (MCS>=20)
- Only average PRB utilization can be checked from PM counters perspesctive, thus lowest aggregation level should be used to
determine really loaded cells (time_aggregation=15min) LTE_5276b Avg. PRB usage per TTI DL

177 © Nokia 2018 Nokia Internal Use

Deployment Aspects
Tests & Pilots

Configuration of power back-off max threshold(s)

• Using dynamic power back-off it is possible to configure up to 2 thresholds (if usageOfMaxDlPwBackoffValue2 != 0)
• First threshold (maxDlPwBackoffValue1) is Table: Recommended FXDA power back-off in 256 QAM mode
always in use and its value should be aligned Single carrier [dB] Dual carrier [dB]
with value provided in CuDo per Radio Module 0.1 0.2
(approach known from static back-off)
• Decision whether second threshold should be used or not depends, among others, whether 4x4 MIMO is
in use (thus RI 3 and 4 are being reported)
- Second threshold considers only 256QAM configured UEs (with Ranks 3,4 or irrespectively of Rank)
• Second threshold (maxDlPwBackoffValue2 – must be higher than first one) can be used to apply even higher back-
offs in some special cases when PRBs in TTI are consumed by very demanding UEs (in terms of EVM critical
modulations and TX schemes)
- It can be configured if using first threshold is not enough under specific conditions (many 256QAM UEs scheduled in TTI) and
its exact value is subject of optimization (no explicit value given)

178 © Nokia 2018 Nokia Internal Use

Deployment Aspects
Tests & Pilots

Check for trial area selection corectness with feature enabled

• Using dedicated dynamic-back-off-related counters (and KPIs) it can be verified if
selected cells were good candidates (in terms of quantity of power back-off There is no „golden
applicability)
configuration” for
- LTE_6630a E-UTRAN Averaged Reduced Power per TTI
-
dynamic back-off,
LTE_6629a E-UTRAN Percentage of the Power Reduced TTIs
many factors need to
• Values of above KPIs strongly depends on applied back-off configuration and load
in the cell be taken into
- The lower threshold to activate dynamic power back-off the higher percentage of TTIs using consideration for
it, but at the same time possibly lower average applied back-off value final decision
- Even if high load is experienced in the cell, KPIs can show no TTIs with reduced power in
situation when threshold to activate dynamic back-off is too high (and vice versa: with small
threshold value majority of TTIs can have reduced power even in low load)

179 © Nokia 2018 Nokia Internal Use

Deployment Aspects
Tests & Pilots – various scenarios

We can think of plenty of different scenarios depending on existing site configuration

• There are many variables that differentiate sites in terms of this feature. To
mention few of them:
- Existence of any NB-IoT/LTE-M combination
- Single/Dual carrier configuration (LTE-LTE, LTE-otherRAT)
- …
• Following scenarios are discussed on next slides to give better view on
expectations in different deployments
- Scenario 1a: Single carrier without NB-IoT/LTE-M features
- Scenario 1b: Single carrier with NB-IoT (guardband)
- Scenario 1c: Single carrier with LTE-M (very similar as inband NB-IoT)
- Scenario 2a: Dual carrier LTE-LTE without NB-IoT/LTE-M features
- Scenario 2b: Dual carrier LTE-otherRAT without NB-IoT/LTE-M features

180 © Nokia 2018 Nokia Internal Use

Deployment Aspects
Tests & Pilots – Scenario 1a: Single carrier without NB-IoT/LTE-M features

Scenario 1a: Single carrier without NB-IoT/LTE-M features

Parameterization 1. In each TTI it is checked if percentage of PRBs using
usageOfMaxDlPwBackoffValue2 = QAM256r3r4 64QAM with Ranks 3,4 and 256QAM exceeds configured,
maxDlPwBackoffValue1 = 1 50% threshold
maxDlPwBackoffValue2 = 1.5
- If the same threshold is crossed just by PRBs scheduled using
dlPwBackoffThreshold = 50
256QAM with Ranks 3 and 4, threshold with value 2 is taken (1.2dB)
dlPwBackoffApp = QAMonly
- Otherwise, threshold with value 1 is taken (1dB)
2. Dynamic power back-off is calculated,
considering max value from previous step and
PBCH/PSS/SSS (for some TTIs only)
3. Calculated dynamic back-off is applied only to
Monitoring of two new counters indicates how
PDSCH scheduled with at least 16QAM
often back-off is used and with what average
- Power by which QPSK PRBs were not power reduction
reduced is equally distributed through PRBs • NUM_TTI_DYN_PWR_BACKOFF
with QAM modulation • SUM_RED_DYN_PWR_BACKOFF

181 © Nokia 2018

Nokia Internal Use
 Deployment Aspects
Tests & Pilots – Scenario 1b: Single carrier with NB-IoT (guardband)

Scenario 1b: Single carrier with NB-IoT (guardband)

Parameterization 1. In each TTI it is checked if percentage of PRBs using
usageOfMaxDlPwBackoffValue2 = QAM256r3r4 64QAM with Ranks 3,4 and 256QAM exceeds configured,
maxDlPwBackoffValue1 = 0.8 maxDlPwBackoffValue2 60% threshold
= 1.2
- If the same threshold is crossed just by PRBs scheduled using
dlPwBackoffThreshold = 60
256QAM with Ranks 3 and 4, threshold with value 2 is taken (1.2dB)
dlPwBackoffApp = All*
- Otherwise, threshold with value 1 is taken (1dB)
2. Dynamic power back-off is calculated, - For each guardband 1 PRB is added to total numer of PRBs for
considering max value from previous step, utilization calculation as well as to used PRBs
PBCH/PSS/SSS (for relevant TTIs) and
guardband NB-IoT reserved resources
Monitoring of two new counters indicates how
3. Calculated dynamic back-off is applied to
often back-off is used and with what average
PDSCH irrespectively of modulation - also to
power reduction
QPSK (excluding guardband NB-IoT) • NUM_TTI_DYN_PWR_BACKOFF
*If power reduction is applied to PRBs using QPSK modulation, this applies
also to SI, MSG2, MSG4, Paging etc. and thus the cell coverage is reduced
• SUM_RED_DYN_PWR_BACKOFF

182 © Nokia 2018 Nokia Internal Use

Deployment Aspects
Tests & Pilots – Scenario 1c: Single carrier with LTE-M (very similar as inband NB-IoT)

Scenario 1c: Single carrier with LTE-M (very similar as inband NB-IoT)
Parameterization 1. In each TTI it is checked if percentage of PRBs using
usageOfMaxDlPwBackoffValue2 = QAM256r1r2r3r4 64QAM with Ranks 3,4 and 256QAM exceeds configured,
maxDlPwBackoffValue1 = 0.9 maxDlPwBackoffValue2 70% threshold
= 1.4
- If the same threshold is crossed just by PRBs scheduled using
dlPwBackoffThreshold = 70
256QAM with Ranks 1,2, 3 and 4, threshold with value 2 is taken
dlPwBackoffApp = QAMonly
(1.2dB)
2. Dynamic power back-off is calculated, - Otherwise, threshold with value 1 is taken (1dB)
considering max value from previous step,
PBCH/PSS/SSS (for some TTIs only), LTE-
M / NB-IoT reserved resources
Monitoring of two new counters indicates how
3. Calculated dynamic back-off is applied only to
often back-off is used and with what average
PDSCH scheduled with at least 16QAM
power reduction
(excluding LTE-M / inband NB-IoT) • NUM_TTI_DYN_PWR_BACKOFF
- Power by which QPSK PRBs were not reduced • SUM_RED_DYN_PWR_BACKOFF
is equally distributed through PRBs with QAM
183 modulation
© Nokia 2018
Nokia Internal Use
 Deployment Aspects
Tests & Pilots – Scenario 2a: Dual carrier LTE-LTE without NB-IoT/LTE-M features

Scenario 2a: Dual carrier LTE-LTE without NB-IoT/LTE-M features

Parameterization (on both carriers) 1. In each TTI per carrier it is checked if percentage of PRBs
usageOfMaxDlPwBackoffValue2 = QAM256r1r2r3r4 using 64QAM with Ranks 3,4 and 256QAM exceeds
maxDlPwBackoffValue1 = 0.9 maxDlPwBackoffValue2 configured, 65% threshold
= 1.4
- If the same threshold is crossed just by PRBs scheduled using
dlPwBackoffThreshold = 65
256QAM with Ranks 1,2, 3 and 4, threshold with value 2 is taken
dlPwBackoffApp = All*
(1.2dB)
2. Dynamic power back-off is calculated, - Otherwise, threshold with value 1 is taken (1dB)
considering max value from previous step and - LTE-M / NB-IoT reserved PRBs are treated as used PRBs
PBCH/PSS/SSS (for some TTIs only) - Dynamicback-off is decided on cell basis – no interaction between
3. Calculated dynamic back-off is applied to carriers in that matter
PDSCH irrespectively of modulation - also to
Monitoring of two new counters indicates how
QPSK
often back-off is used and with what average
*If power reduction is applied to PRBs using QPSK modulation, this applies power reduction
also to SI, MSG2, MSG4, Paging etc. and thus the cell coverage is reduced • NUM_TTI_DYN_PWR_BACKOFF
• SUM_RED_DYN_PWR_BACKOFF
184 © Nokia 2018 Nokia Internal Use
Deployment Aspects
Tests & Pilots – Scenario 2b: Dual carrier LTE-otherRAT without NB-IoT/LTE-M
features
Scenario 2b: Dual carrier LTE-otherRAT without NB-IoT/LTE-M features
Parameterization (on both carriers) 1. In each TTI per carrier it is checked if percentage of PRBs
usageOfMaxDlPwBackoffValue2 = QAM256r3r4 using 64QAM with Ranks 3,4 and 256QAM exceeds
maxDlPwBackoffValue1 = 0.9 maxDlPwBackoffValue2 configured, 55% threshold
= 1.4
- If the same threshold is crossed just by PRBs scheduled using
dlPwBackoffThreshold = 55
256QAM with Ranks 3 and 4, threshold with value 2 is taken (1.2dB)
dlPwBackoffApp = QAMonly
- Otherwise, threshold with value 1 is taken (1dB)
2. Dynamic power back-off is calculated, - LTE-M / NB-IoT reserved PRBs are treated as used PRBs
considering max value from previous step and
- otherRAT carrier load is not considered, thus sometimes back-off can
PBCH/PSS/SSS (for some TTIs only) be unnecesarily applied on LTE carrier (which is still better than static
3. Calculated dynamic back-off is applied only to back-off)
PDSCH scheduled with at least 16QAM
- Power by which QPSK PRBs were not reduced Monitoring of two new counters indicates how
is equally distributed through PRBs with QAM often back-off is used and with what average
modulation power reduction
• NUM_TTI_DYN_PWR_BACKOFF
• SUM_RED_DYN_PWR_BACKOFF
185 © Nokia 2018
Nokia Internal Use
LTE4054 Dynamic Power Back-off

Performance
Aspects
Table of contents

<chapter:performance_aspects>

186 © Nokia 2018 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

NUM_TTI_DYN_PWR_BACKOFF This counter provides the number of TTIs for which the dynamic power backoff
(M8010C148) algorithm has been applied.
#LTE Power and Quality DL Trigger event: This counter is updated for every TTI for which the dynamic power
backoff algorithm has been applied.
Use case: Monitoring of average applied power back-off. Percentage of TTIs where
back-off was applied (among all active TTIs) can be also monitored

SUM_RED_DYN_PWR_BACKOFF
E-UTRAN Averaged (LTE_6630a) =
Reduced Power per TTI NUM_TTI_DYN_PWR_BACKOFF

NUM_TTI_DYN_PWR_BACKOFF
E-UTRAN Percentage of the (LTE_6629a) = ×100%
Power Reduced TTIs ACTIVE_TTI_DL

187 © Nokia 2018 Nokia Internal Use

Performance Aspects
New counters

Counter name Description

SUM_RED_DYN_PWR_BACKOFF This counter provides the sum of the transmission power reduction due to dynamic
(M8010C149) power backoff.
#LTE Power and Quality DL Trigger event: his counter accumulates the values of power reduction occuring due to
dynamic power backoff.
Use case: Monitoring of average applied power back-off

SUM_RED_DYN_PWR_BACKOFF
E-UTRAN Averaged Reduced (LTE_6630a) =
Power per TTI NUM_TTI_DYN_PWR_BACKOFF

188 © Nokia 2018 Nokia Internal Use

Performance Aspects
Feature impact
Feature impact How to measure?
Peak UE throughput increase (see assumptions below) No direct KPI to show Peak UE Throughput. DT needs to be
To observe this gain, decent share of EVM critical modulations performed
and TX schemes needs to be in the cell (so that dynamic back-off
is applied). Gain will be visible on UEs that require power
reduction in order to achieve high modulation and TX scheme.

Higher share of high Rank Indicators (assumptions as above) LTE_1518b Percentage of MIMO Rank Indication with value 1
reported by the UE
As a result of reduced power, certain UEs are eligible to utilize
higher TX schemes (RI histogram shift towards higher values) LTE_1519b Percentage of MIMO Rank Indication with value 2
reported by the UE
LTE_1669a Percentage of MIMO Rank Indication with value 3
reported by the UE
LTE_1520b Percentage of MIMO Rank Indication with value 4
reported by the UE
Higher share of high MCSs (assumptions as above) LTE_174b – LTE_202b Percentage of PDSCH transmissions using
As a result of reduced power, certain UEs are eligible to utilize MCS{0-28}
higher MCSs (MCS histogram shift towards higher values) LTE_6263a E-UTRAN Percentage of PDSCH transmissions using
High MCS Codes (MCS>=20)

189 © Nokia 2018 Nokia Internal Use

References and acknowledgments

References
Ioannis Maniatis and CFAM team – CFAM for LTE2479

Ioannis Maniatis and CFAM team – CFAM for LTE3073

Mani Iyer and CFAM team – CFAM for LTE3502

Flexi Zone Product Variant Summary

3GPP TS 36.211 - Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation (v 12.8.0)

Pawel Gorzelewski – NEI for LTE44 – 64QAM in UL

Prabhjinder Boparai – CFAM for LTE4064

191 © Nokia 2018 Nokia Internal Use

Copyright and confidentiality

The contents of this document are proprietary and be used in Nokia Solutions and Networks products and implied warranties of merchantability and fitness for a
confidential property of Nokia Solutions and Networks. This related specifications or other documentation. Accordingly, particular purpose, are made in relation to the accuracy,
document is provided subject to confidentiality obligations if the user of this document gives Nokia Solutions and reliability or contents of this document. NOKIA
of the applicable agreement(s). Networks Feedback on the contents of this document, Nokia SOLUTIONS AND NETWORKS SHALL NOT BE
Solutions and Networks may freely use, disclose, reproduce, RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS
This document is intended for use of Nokia Solutions and license, distribute and otherwise commercialize the feedback DOCUMENT or for any loss of data or income or any
Networks customers and collaborators only for the purpose in any Nokia Solutions and Networks product, technology, special, incidental, consequential, indirect or direct damages
for which this document is submitted by Nokia Solution and service, specification or howsoever caused, that might arise from the use of this
Networks. No part of this document may be reproduced or other documentation. document or any contents of this document.
made available to the public or to any third party in any
form or means without the prior written permission of Nokia Nokia Solutions and Networks operates a policy of ongoing This document and the product(s) it describes are protected
Solutions and Networks. This document is to be used by development. Nokia Solutions and Networks reserves the by copyright according to the
properly trained professional personnel. Any use of the right to make changes and improvements to any of the applicable laws.
contents in this document is limited strictly to the use(s) products and/or services described in this document or
specifically created in the applicable agreement(s) under withdraw this document at any time without prior notice. Nokia is a registered trademark of Nokia Corporation. Other
which the document is submitted. The user of this document product and company names mentioned herein may be
may voluntarily provide suggestions, comments or other The contents of this document are provided "as is". Except trademarks or trade names of their respective owners.
feedback to Nokia Solutions and Networks in respect of the as required by applicable law, no warranties of any kind,
contents of this document ("Feedback"). Such Feedback may either express or implied, including, but not limited to, the © Nokia Solutions and Networks 2014

192 © Nokia 2018 Nokia Internal Use