Extra High Value Feature

NETWORK
ENGINEERING
TDD Massive MIMO
LTE2666 Massive MIMO
LTE4566 TDD Massive MIMO 10MHz Support
LTE5671 15MHz carrier support for CPRI based TDD massive MIMO

Network Engineering Information

• Doc ID: 5bacece5092dda00183dcaf7
• Version 5.5
• Krzysztof Wisniowski, Adam Pomianek
• Status: Approved
• 11-03-2021

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: 5bacece5092dda00183dcaf7

Document location:
Organization:

Version Description of Changes Date Doc Owner Doc Status Reviewed Approver Approval Date
by
Krzysztof
0.1 Draft 09-03-2018 DD-MM-YYYY
Wisniowski

Krzysztof
1.0 Reviewed first version 15-03-2018
Wisniowski

2.0 NEI complex draft: LTE2666 & LTE4566 23-04-2018 Adam Pomianek

2.1 NEI Complex 27-09-2018 Adam Pomianek

2.2 TD-LTE19 features added 14-01-2019 Adam Pomianek

LTERLCR-25434 added in Deployment Aspects

3.0 LTERLCR-27092 and LTERLCR-25482 added in mMIMO 04-03-2019 Adam Pomianek
features structure

4.0 TD-LTE19A features added to the Roadmap 25-04-2019 Adam Pomianek

4.1 LTERLCR-25482 and LTERLCR-29581 to the Roadmap 10-05-2019 Adam Pomianek

4.2 LTERLCR-27155 added to the Roadmap 13-05-2019 Adam Pomianek

3 © Nokia 2018 Nokia Internal Use

Revision history and metadata

Document ID: 5bacece5092dda00183dcaf7

Document location:
Organization:

Version Description of Changes Date Doc Owner Doc Status Reviewed Approver Approval Date
by

5.0 LTE5671 Added, LTE2666 faults added 10-03-2020 Adam Pomianek

5.1 LTERLCR-32395 added 14-09-2020 Adam Pomianek

5.2 LTERLCR-29794 added 19-11-2020 Adam Pomianek

Fault 1938 modified to provide reference

5.3 2-12-2020 Adam Pomianek
to CNI-54058

5.4 CNI-56063 & CNI-63336 01-03-2021 Adam Pomianek

5.5 LTERLCR-32396 added 11-03-2021 Adam Pomianek

4 © Nokia 2018 Nokia Internal Use

TDD Massive MIMO
Table of contents

Introduction Technical Benefits and Inter –

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

Configuration Deployment Dimensioning Performance

Management Aspects Aspects Aspects
Parameters and Activation, Configuration Dimensioning Impacts and Counters and KPIs,
Parameterization Examples, Fault Mgmt, Examples Feature Impact Analysis
Scenarios Trial Area and Verification

5 © Nokia 2018 Nokia Internal Use

TDD Massive MIMO

Introduction

Table of contents

<chapter:introduction>

6 © Nokia 2018 Nokia Internal Use

 * each extension of
Introduction BASIC LTE2666 feature
applies to
TDD Massive MIMO features structure (1/11 and still growing) all mMIMO features

- LTE2666 Massive MIMO (subject of current NEI) BASIC feature*

- LTE3463 DL MU-MIMO for massive MIMO, up to 8 streams (webNEI) Basic Multi User in DL

- LTE3469 AirScale site configuration for Massive MIMO (webNEI) Configuration

- LTE3953 AirScale MAA 64T64R 128AE B38 80W AAHD

- LTE3809 AirScale MAA 64T64R 128AE B40 80W AANA
- LTE4084 AirScale MAA 64T64R 128AE B40 120W AANB Hardware
- LTE3452 AirScale MAA 64T64R 128AE B41 120W AAHB
- LTE3738 AirScale MAA 64T64R 128AE B41 120W AAHC

TD-LTE18 T D D M a s s i v e M I M O
7 © Nokia 2018 Nokia Internal Use
 * each extension of
Introduction BASIC LTE2666 feature
applies to
TDD Massive MIMO features structure (2/11 and still growing) all mMIMO features

- LTE4566 TDD Massive MIMO 10MHz Support (subject of current NEI) Extension of BASIC LTE2666*

- LTE4427 DL MU-MIMO for massive MIMO, up to 16 streams (webNEI) Extension of Multi User in DL,
- LTE3464 UL MU-MIMO for massive MIMO, up to 8 streams (webNEI) Multi User in UL
- LTE3690 DL CA for massive MIMO (webNEI)
- LTE3691 UL CA for massive MIMO (webNEI) UL/DL CA for mMIMO

- LTE4630 10MHz configuration for TD-LTE mMIMO (webNEI)

Configuration
- LTE4298 3 carrier or 3 sector configuration for mMIMO (webNEI)

- LTE4576 AirScale MAA 64T64R 128AE B41 120W AAHE

- LTE4590 AirScale MAA 64T64R 128AE B43 200W AEQD Hardware
- LTE4672 AirScale MAA 64T64R 128AE B41 120W AAHF

TD-LTE18SP T D D M a s s i v e M I M O
8 © Nokia 2018 Nokia Internal Use
 * each extension of
Introduction BASIC LTE2666 feature
applies to
TDD Massive MIMO features structure (3/11 and still growing) all mMIMO features

- LTE4573 TDD massive MIMO DL 256QAM and UL64QAM (webNEI) Extension of BASIC LTE2666*
TD-LTE18A mMP - LTE4655 TDD 32TRX massive MIMO (webNEI)
(commercial)
LTERLCR-27092
same branch as - LTE4557-A TDD TM9 support for massive MIMO (webNEI)
TD-LTE18A

BF improvement
on R&D level - LTE3463 DL MU-MIMO for massive MIMO, up to 8 streams LTERLCR-25822

CR regarding SRS in SCell - LTE3691 TDD uplink carrier aggregation with massive MIMO LTERLCR-26224

- LTE4659 32Tx32Rx configuration with split mode for TDD mMIMO (webNEI) Configuration

- LTE4845 AirScale MAA 64T64R 128AE B41 120W AAHJ Hardware

TD-LTE18A T D D M a s s i v e M I M O
9 © Nokia 2018 Nokia Internal Use
 * each extension of
** Hardware
Introduction license
BASIC LTE2666 feature
applies to
activation
TDD Massive MIMO features structure (4/11 and still growing) all mMIMO features

- LTE4567 TDD Massive MIMO Capacity boost (webNEI) Extension of BASIC LTE2666*
Second 32TRx for LTE - LTE4655 TDD 32TRX massive MIMO LTERLCR-25482

TD-LTE19 PT1 - LTE4557-B TDD TM9 support for massive MIMO (webNEI) LTERLCR-27092

- LTE2666/LTE4566 Massive MIMO 20MHz/10MHz LTERLCR-27155

R&D parameters converted (in case of LTE3463 R&D parameters from
into new OAM parameters - LTE3463 DL MU-MIMO for massive MIMO, up to 8 streams LTERLCR-25822 in TD-LTE18A are made
OAM and list of parameters is extended)
- LTE3464 UL MU-MIMO for massive MIMO
delayUseBfWeightTimer
modification for Sprint LTERLCR-30353
- LTE4655 TDD 32TRX massive MIMO

Calibration Alarms - LTE2666 Massive MIMO

LTERLCR-28015
workaround
- LTE4655 TDD 32TRX massive MIMO

- LTE4659 32Tx32Rx configuration with split

Second 32TRx for LTE
mode for TDD mMIMO (webNEI)
LTERLCR-25482 Config.

removed from
- LTE4759 HW activation (HWA) licenses for mMIMO LTERLCR-28767 **HWA License
TD-LTE19

TD-LTE19 T D D M a s s i v e M I M O
10 © Nokia 2018 Nokia Internal Use
 Introduction
TDD Massive MIMO features structure (5/11 and still growing)
Change of PRB LTERLCR-28577
allocation policy - LTE3463 DL MU-MIMO for massive MIMO, up to 8 streams (CR execution postponed to
during UE pairing TD-LTE19B, content valid)

- LTE2666/LTE4566 Massive MIMO 20MHz/10MHz

LTERLCR-29317
delayToUseBfWeightTimer - LTE3463 DL MU-MIMO for massive MIMO, up to 8 streams
OAM parameter update (CR execution postponed to
- LTE3464 UL MU-MIMO for massive MIMO TD-LTE19B, content valid)

- LTE4655 TDD 32TRX massive MIMO

Calibration Alarms - LTE2666/LTE4566 Massive MIMO 20MHz/10MHz

LTERLCR-26249
severity downgrade
- LTE4655 TDD 32TRX massive MIMO

Power per carrier - AAHC/AAHF/AANB LTERLCR-29794 Hardware

TD-LTE19A T D D M a s s i v e M I M O
11 © Nokia 2018 Nokia Internal Use
 Introduction
TDD Massive MIMO features structure (6/11 and still growing)
- LTE5107 TDD TM9 MU-MIMO support for massive MIMO (webNEI)
Ported back to 19A MP - LTE5141 TDD massive MIMO calibration enhancement (webNEI) LTERLCR-29749

- LTE4032 AirScale Capacity ABIC (webNEI)

- LTE4671 TDD massive MIMO on ABIC (webNEI)
- LTE5116 TDD massive MIMO 32TRX on ABIC (webNEI)
- LTE5400 TDD massive MIMO ABIC remaining porting (webNEI)

- LTE5238 TDD mMIMO configuration with 32TxRx split mode on ABIC (webNEI)
- SR002305 LTE-TDD massive MIMO on ABIC in SBTS (webNEI) Configuration
- LTE4719 CPRI based TDD mMIMO Configurations on ABIC (webNEI)

TD-LTE19B T D D M a s s i v e M I M O
12 © Nokia 2018 Nokia Internal Use
 Introduction
TDD Massive MIMO features structure (7/11 and still growing)

vertical beamforming - LTE4557 TDD TM9 support for massive MIMO LTERLCR-29581
profiles
- LTE5107A-h TDD TM9 MU-MIMO support for massive MIMO LTERLCR-30384

- LTE2666/LTE4566 Massive MIMO 20MHz/10MHz LTERLCR-29914

- LTE3463 DL MU-MIMO for massive MIMO, up to 8 streams executes postponed CRs:
CRs postponed
In TD-LTE19A LTERLCR-28577
- LTE3464 UL MU-MIMO for massive MIMO
LTERLCR-29317
- LTE4655 TDD 32TRX massive MIMO

LTERLCR-29317 was initially further postponed by

LTERLCR-30967 but finally shifted back to
TD-LTE19B by LTERLCR-31397

Power per carrier - AANB LTERLCR-30522 Hardware

TD-LTE19B T D D M a s s i v e M I M O
13 © Nokia 2018 Nokia Internal Use
 Introduction
TDD Massive MIMO features structure (8/11 and still growing)

dynamic TDD
mMIMO sector
beamforming (BF)
- LTE2666/LTE4566 Massive MIMO 20MHz/10MHz LTERLCR-31705
adaption

- LTE2666/LTE4566 Massive MIMO 20MHz/10MHz

Improved packet
scheduling for India LTERLCR-31487
- LTE4655 TDD 32TRX massive MIMO
market
- LTE4671 TDD massive MIMO on ABIC
delayUseBfWeightTimer - LTE5116 TDD massive MIMO 32TRx on ABIC LTERLCR-30540 it corrects
OAM parameter changes introduced by
LTERLCR-30353 from TD-LTE19
modification - LTE3463 DL MU-MIMO for massive MIMO, up to 8 streams

LTE2810/3329/3549/3550/3736
Power step 3737/3961/LTE3452/LTE3738/ LTERLCR-31080 Hardware
3953/4576/4672/4845/3809/4084

SRAN20A T D D M a s s i v e M I M O
14 © Nokia 2018 Nokia Internal Use
 ** Hardware
Introduction license
activation
TDD Massive MIMO features structure (9/11 and still growing)

- LTE5578 TDD massive MIMO ABIC remaining porting II (WebNEI)

- LTE5372 MAC PS core extension for TDD massive MIMO (WebNEI)
Support on ABIA - LTE5462 TDD mMIMO Zero Forcing (WebNEI) LTERLCR-31598

- LTE4592 FDD-TDD downlink carrier aggregateon with mMIMO (WebNEI)

- LTE4759 HW activation (HWA) licenses for mMIMO (WebNEI) **HWA License

Two sector BF
profiles
- LTE2666/LTE4566 Massive MIMO 20MHz/10MHz LTERLCR-31705

SRAN20A T D D M a s s i v e M I M O
15 © Nokia 2018 Nokia Internal Use
 * each extension of
Introduction BASIC LTE2666 feature
applies to
TDD Massive MIMO features structure (10/11 and still growing) all mMIMO features

- LTE5671 15MHz carrier support for CPRI based TDD massive MIMO (WebNEI) Extension of BASIC LTE2666*

- LTE5736 TDD massive MIMO two carriers per ABIC with 16 layer (WebNEI)
- LTE5674 Downlink QoE based scheduling enhancement for TDD massive MIMO (WebNEI)
- LTE5404 TDD massive MIMO PDCCH spatial multiplexing on ABIC (WebNEI)

Pipe overheating
handling - LTE5578 TDD massive MIMO ABIC remaining porting II LTERLCR-32302
porting to ABIC

- LTE4655 TDD 32TRX massive MIMO

Two sector BF LTERLCR-31860
profiles
- LTE4671 TDD massive MIMO on ABIC
LTERLCR-32395
- LTE5116 TDD massive MIMO 32TRx on ABIC

SRAN20B T D D M a s s i v e M I M O
16 © Nokia 2018 Nokia Internal Use
 Introduction
TDD Massive MIMO features structure (11/11 and still growing)

Support on AEQA - LTE5141 TDD massive MIMO calibration enhancement LTERLCR-31657

R&D parameter - LTE3463 DL MU-MIMO for massive MIMO, up to 8 streams LTERLCR-32396
made OAM

SRAN20B T D D M a s s i v e M I M O
17 © Nokia 2018 Nokia Internal Use
 Introduction
TDD Massive MIMO features structure (11/11 and still growing)

- CB006432 Dynamic TDD mMIMO sector beamforming weight switching (WebNEI)

- LTE5110 LTE eCPRI fronthaul interface (WebNEI)

SU MIMO with TM7 - LTE3949 eCPRI/LLS based TDD massive MIMO (WebNEI) LTERLCR-32140

- LTE3950 eCPRI/LLS based TDD massive MIMO MU-MIMO (WebNEI)

- LTE5111 NR-TDLTE concurrent operation for eCPRI radios (WebNEI)

Configuration
- LTE4248 eCPRI mMIMO TDD initial configuration (WebNEI)

TDD mMIMO on eCPRI

SPA/WBS - LTE5674 Downlink QoE based scheduling enhancement for TDD massive MIMO (WebNEI) CNI-56063

SRAN20C T D D M a s s i v e M I M O
18 © Nokia 2018 Nokia Internal Use
 Introduction
TDD Massive MIMO features structure (11/11 and still growing)
No SU MIMO
with TM7
- LTE5657 eCPRI/LLS based TDD massive MIMO MU-MIMO II (WebNEI) LTERLCR-32140

- LTE5716 15MHz carrier support for eCPRI based TDD massive MIMO (WebNEI)

Support for 15MHz

- CB005962 TDD eCPRI mMIMO configuration extension on ABIC (WebNEI) Configuration
CNI-63336
excluded
- CB006490 LTE-TDD eCPRI mMIMO four carriers configurations on ABIC (WebNEI)

TDD mMIMO on eCPRI

SRAN21A T D D M a s s i v e M I M O
19 © Nokia 2018 Nokia Internal Use
Introduction
Considered features in brief

THIS NEI complex covers following features:

• LTE2666 Massive MIMO (TDD-LTE18)

basic feature introducing support for Single User (SU) Massive MIMO (mMIMO)
for 20MHz cell deployment

• LTE4566 TDD Massive MIMO 10MHz Support (TDD-LTE18SP)

extension of mMIMO platform introducing support
for 10MHz deployment

• LTE5671 15MHz carrier support for CPRI based TDD massive MIMO (SRAN20B)
extension of mMIMO platform introducing support
for 15MHz deployment

20 © Nokia 2018 Nokia Internal Use

 Symbol received
Introduction
1.5

1
by RX antenna 1
MIMO Principle 0.5

Symbol received
0

by RX antenna 2
-0.5

-1

MIMO = Multiple Input Multiple Output -1.5

• different symbols are sent by transmit antennas in the same

time and frequency
• as symbols propagate over the wireless channel, their phase and
amplitude changes according to the channel coefficients

B
eN
• channel between each pair of the TX and RX antennas is
different due to different propagation conditions

x1 h11
TX y1 • channel coefficients are obtained from
antenna
port 0 h21
RX1
DL reference symbols (FDD) or uplink
x1 sounding in reciprocal channels (TDD)
h12 y1  h11 x1  h12 x2
y2  h21 x1  h22 x2 x2 • receiver needs to solve a set of linear
h22 equations to obtain the transmitted
x2 TX
antenna
RX2 symbols
port 1
y2
Wireless channel coefficients
21 © Nokia 2018 (known from Reference
NokiaSignal)
Internal Use
Introduction
Multiuser MIMO Principle …having a large
number of
antennas on UE is
not practical
• in theory, maximum number of spatial multiplexing layers is defined
by the smaller number of RX or TX antennas in the link:

• in reality having large number of antennas on UE is not practical –

increased cost of device, energy consumption, limited antenna
packing space, favorable channel condition less frequent

• multiuser MIMO (MU-MIMO) allows scheduling UEs on

same time and frequency resources
• favorable channel conditions always met since close
antenna packing is no longer an issue with multiple UEs
• better spectral efficiency (bit/s/Hz) than Single User MIMO
(SU-MIMO)
B
eN

22 © Nokia 2018 Nokia Internal Use

Introduction
What is massive MIMO technology (1/2)?
AAS*

• Massive MIMO (mMIMO) is the extension of traditional

MIMO technology to antenna arrays having a large
number (>>8) of controllable antenna elements higher energy
concentration

• utilization of larger number of antenna elements for signal

transmission toward only one UE enables high degree of lower level of
interference
energy concentration in space as narrower beam is possible
to be created
legacy antenna system
• higher energy concentration (narrower beam) brings SINR
improvement as:
- increased signal strength is provided to the UE location
lower energy
- less power is spread in other directions causing lower level concentration
of interference
higher level of
interference

23 © Nokia 2018 Nokia Internal Use

* Adaptive Antenna System
Introduction
individually
What is massive MIMO technology (2/2)? controlled downtilt
AAS

• moreover utilization of larger number of antenna elements

for signal transmission toward only one UE enables beam’s
position to be controlled in 3D
(mMIMO enables 3D beamforming)
• 3D beamforming enables downtilt of a beam to be
received signal strength
controlled individually (no more fixed downtilts) improvement due to tuned reduced level of inter-cell-interference
downtilt
• individually controlled downtilt enables
fixed downtilt
- substantial reduction of inter-cell-interference legacy antenna system

- improvement of received signal strength

• 3D beamforming is controlled through so called Beam
Forming vector (BF vector)

NO improvement of high level of inter-cell-interference

received signal strength

24 © Nokia 2018 Nokia Internal Use

Introduction
What is MU-MIMO for mMIMO technology (1/2)?
LTE2666

• mMIMO antenna (MAA, AAS) is capable to produce

more then just one narrow beam
• moreover, each beam can be independently controlled in
3D (a dedicated Beam Forming vector is associated with
each beam)
• as one beam can potentially serve one UE, that means more only one beam/UE is supported

UEs can be simultaneously served by mMIMO antenna

• the exact number of served UEs depends on: AAS capabilities

- the size of an AAS antenna array (number of UEs

should be smaller than number of elements in an antenna
array – usually an order of magnitude)
- the signal processing capabilities of hardware just
behind mMIMO antenna array
mMIMO AAS is capable to produce more
than just one beam
each beam can potentially serve one UE
25 © Nokia 2018 Nokia Internal Use
Introduction
What is MU-MIMO for mMIMO technology (2/2)?

• when all UEs are placed in distinct locations (are spatially

separated) and each UE is served by dedicated narrow MU-MIMO for mMIMO
beam, AAS antenna array can distinguish them (UEs are technology
considered to be spatially orthogonal)
• under such circumstances UEs no longer have to be
allocated with different (orthogonal) time and frequency
resources (PRBs), UEs can reuse same PRBs
• that in general means that PRBs are not distributed among
UEs but simultaneously reused instead – as a result each UE
can be (at least potentially) allocated with all available
PRBs
• from that point of view number of available PRBs is
multiplied by the number of UEs – this is how mMIMO can
provide Multiuser Gain

26 © Nokia 2018 Nokia Internal Use

Introduction
Channel Hardening in Massive MIMO

Is Massive MIMO just MU-MIMO with extra antennas?

What is fundamentally different?
• with more transmit antennas, fast fading gradually disappears. This effect
is called channel hardening in mMIMO literature
• this effect, plus favorable propagation conditions made available by
massive antenna array take MU-MIMO to the ultimate performance
level in practical radio conditions

• radio channel becomes flat in frequency domain -> less gain from
frequency scheduling
• system design could be simplified resulting in lower latencies

27 © Nokia 2018 Nokia Internal Use

Introduction

Number of terminals (K)

TDD/FDD Aspects of Massive MIMO TDD

FD
• as in traditional closed loop MIMO, in mMIMO D
channel knowledge is needed at the transmitter as well:
− TDD can use channel reciprocity
− FDD uses improved 3GPP Release 13/14 feedback Number of antennas (M)

• TDD is better suitable for Massive MIMO than FDD *Illustrative only.
*Assuming same % of pilot overhead.

1 5 UL SRS
1 5 CSI-RS
In TDD, radio pilot In FDD overhead depends both on
2 6 overhead depends on the the number of the antennas and the
number of spatially 2 6 number of spatially multiplexed
3 7 multiplexed UEs. It does UEs.
not depend on the number 3 7
Reciprocity
Therefore spectral efficiency of FDD
4 8 of the antennas. mMIMO is limited compared to that
granted in
TDD 4 8 of TDD.
PM
I

28 © Nokia 2018 Nokia Internal Use

Introduction
Before & after LTE2666

Before After
• Network uses 8T8R beamforming in horizontal domain only • mMIMO Active Antenna (AAS) in place
• Extended capacity and coverage due to 3D beamforming
• More mMIMO features possible with SW upgrade

29 © Nokia 2018 Nokia Internal Use

Introduction
Before & after LTE4566

Before After
• mMIMO Active Antenna (AAS) in place • mMIMO Active Antenna (AAS) in place
• Extended capacity and coverage due to 3D beamforming • Extended capacity and coverage due to 3D beamforming
• More mMIMO features possible with SW upgrade • More mMIMO features possible with SW upgrade
• only 20MHz bandwidth supported by LTE2666 • 10MHz bandwidth supported

30 © Nokia 2018 Nokia Internal Use

LTE2666 Massive MIMO, LTE4566 TDD Massive MIMO 10MHz support

Technical Details

Table of contents

<chapter:technical_details>

31 © Nokia 2018 Nokia Internal Use

 <feature:LTE4566>

Technical Details
LTE2666 Massive MIMO

LTE2666

32 © Nokia 2018 Nokia Internal Use

Technical Details
LTE2666 Massive MIMO Active Antenna Array
• LTE2666 works with Adaptive Antenna Systems (AAS) provided in Introduction part
• first AAS supported by LTE2666 was LTE3452 AirScale MAA 64T64R 128AE B41 120W AAHB
• basic configuration is as per LTE3469 AirScale site configuration for Massive MIMO
LTE2763
Fronthaul
Passive WDM
64T
• LTE3452 features: RX
− Integrated antenna
Q
− 120W total output power at 2.6GHz Band (3GPP TDD B41) S
F
− 64 TRXs driving 128 antenna elements, transmitting 1.875W per TRX 9.8G P
w/IQC ID CWDM
− Instantaneous bandwidth 60MHz at 2.6GHz Band (up to 3xLTE20) 1 +
2 MUX/
3
ABIA#1 4 DEMUX
5 Q
6 (1830 VWM)
S carrier1
1 AAHB
2 F
• LTE3469 features: ASIA ABIA#2 3
4 P
64T64R
5
6 +
− one 20 MHz carrier requires 2x ABIA cards
Q
− 4 CPRI links required per carrier S
Optical F
− physical layer from 64TXRX fully processed in baseband module P
interface, +
supporting 4x
9.8Gbps
CPRI link
33 © Nokia 2018 Nokia Internal Use
Technical Details
PDSCH beamforming

• LTE2666/LTE4566 is based on Rel.9 UEs. Transmission to the

UE in the DL is done using 3GPP Transmission Mode 8 (TM8)

• long term beamforming weights per UE are calculated based on H

PDSC
the Sounding Reference Signal (SRS) symbols sent by the UE UL S

B
SURL

eN
periodically in the UL. They are then used to transmit up to 2
SRS
beamformed spatially multiplexed streams to the UE UL SRS
UL SRS
• broadcast and common control channels are not beamformed

• LTE2666/LTE4566 bases on beamforming algorithm that was

introduced by the legacy feature LTE541 Dual Stream
Beamforming (webNEI) Reciprocity granted in TDD

34 © Nokia 2018 Nokia Internal Use

Technical Details
Broadcast (sector) beam
User beam

• broadcast, common control channels and cell reference symbols

are transmitted via sector beam. Sector beam radiation pattern is
made wide enough (e.g.900 beam width) to provide coverage in
the cell for the radio channels that cannot or must not be
beamformed User beam
• sector beam will also be used for non-beamformed UE dedicated
PDSCH transmissions (e.g. TM2, TM3)

• sector beam weights are stored in the sector beamforming weight

profiles, defined in both vertical and horizontal plane

• there are 20 predefined beamforming profiles defined for Broadcast beam

LTE2666/LTE4566

• in LTE2666/LTE4566 electrical tilt of the sector beam is realized

also by means of beamforming profile selection

35 © Nokia 2018 Nokia Internal Use

Technical Details
Broadcast beam: 64T64R antenna deployment

• according to the antenna deployment picture on the right,

antenna Id #0 and #1 belong to a same
sub-array and they will have a same Sector Beamforming
Weight. Antenna IDs table is
shown below:

48, 49 50, 51 52, 53 54, 55 56, 57 58, 59 60, 61 62, 63

32, 33 34, 35 36, 37 38, 39 40, 41 42, 43 44, 45 46, 47
16, 17 18, 19 20, 21 22, 23 24, 25 26, 27 28, 29 30, 31
0, 1 2, 3 4, 5 6, 7 8, 9 10, 11 12, 13 14, 15

• the two antennas that are in the same antenna group have
different polarizations

36 © Nokia 2018 Nokia Internal Use

Technical Details
Broadcast beam: how sector beams are made

• sector beam weights are complex numbers, that are defined in terms of modulus and phase for each of 8 horizontal and 4
vertical antenna group.

• individual antenna group weight is obtained by multiplying vertical and horizontal modules of an antenna element and
adding their respective phases:
modulusOfAntGrp6H
phaseOfAntGrp6H

48, 49 50, 51 52, 53 54, 55 56, 57 58, 59 60, 61 62, 63

modulusOfAntGrp2V 32, 33 34, 35 36, 37 38, 39 40, 41 42, 43 44, 45 46, 47
phaseOfAntGrp2V 16, 17 18, 19 20, 21 22, 23 24, 25 26, 27 28, 29 30, 31
0, 1 2, 3 4, 5 6, 7 8, 9 10, 11 12, 13 14, 15

FinalModulusForAntGrp[i*8 + j] = ModulusOfVerticalForAntGrp[i] * ModulusOfHorizontalForAntGrp[j];

FinalPhaseForAntGrp[i*8 + j] = PhaseOfVerticalForAntGrp[i] + PhaseOfHorizontalForAntGrp[j];

37 © Nokia 2018 Nokia Internal Use

Technical Details
Broadcast beam: how to configure broadcast beam

• sector beamforming profiles are either predefined or

customized Predefined sector beam profiles:
Macro-0 Electrical Tilt-(0)
• they are selected by setting Macro-0 Electrical Tilt-(1)
LNCEL_TDD:mMimoSectorBFProfName parameter to a Macro-0 Electrical Tilt-(2)
specific sector beam profile name Macro-0 Electrical Tilt-(3)
• vertical sector beam tilt adjustment is based on selecting Macro-0 Electrical Tilt-(4)
one of the predefined profiles. In LTE2666 vertical tilt is Macro-0 Electrical Tilt-(5)
processed by the baseband, there is no additional Remote Macro-0 Electrical Tilt-(6)
Electrical Tilt (RET) function. Macro-0 Electrical Tilt-(7)
Macro-0 Electrical Tilt-(8)
• additionally to the predefined profiles, customer can
Macro-0 Electrical Tilt-(-1)
configure up to 20 additional sector beam profiles.
Macro-0 Electrical Tilt-(-2)
High Building-0

38 © Nokia 2018 Nokia Internal Use

Technical Details
Broadcast beam based on LTERLCR-31705 and LTERLCR-31860

• since SRAN20A LTERLCR-31705 starts to support dynamic TDD mMIMO sector beamforming (BF) adaption
• two sector BF profiles with different E-tilts are pre-defined
• two policies are defined for E-tilt change:
‑ time based: switching between sector BF profiles is done each day, based on time of a day to adjust E-tilt either to the
busy hours specific traffic or to non-busy hours specific traffic
‑ traffic based: switching between sector BF profiles is done based on user throughput, cell load and average number of
active UEs
• functionality introduced by LTERLCR-31705 is supported on:
‑ ABIA based TDD mMIMO configurations with 64TRx only (as per SRAN20A)
• in SRAN20B functionality introduced by LTERLCR-31705 is extended by LTERLCR-31860 to:
‑ ABIA based TDD mMIMO configurations with 32TRx
‑ ABIC based TDD mMIMO configurations with 32TRx or 64TRx

• in both cases i.e. LTERLCR-31705 and LTERLCR-31860 all settings are handled by R&D parameters

39 © Nokia 2018 Nokia Internal Use

Technical Details
Broadcast beam based on LTERLCR-32395

• in SRAN20B functionality introduced by LTERLCR-31860 was further improved by LTERLCR-32395:

‑ dynamic/automatic switching of sector beam profile back from Busy Hour (BH) to non-Busy Hour (NBH) profile
‑ executed once the PRB usage ratio is below a threshold
‑ the enhancement is available on both ABIA and ABIC HW platforms
‑ all settings are handled by R&D parameters
‑ LTERLCR-32395 reuses parameters
from LTECRL-31860

• in SRAN20C all functionalities introduced by:

‑ LTERLCR-31705 (SRAN20A)
‑ LTERLCR-31860 (SRAN20B)
‑ LTERLCR-32395 (SRAN20B)
are converted into the regular OAM feature (for more technical details, please refer to the OAM feature)
CB006432 Dynamic TDD mMIMO sector beamforming weight switching (WebNEI)
40 © Nokia 2018 Nokia Internal Use
Technical Details
Uplink Receiver

• Uplink receiver structure is optimized for complexity caused by large scale of antennas
• Uplink PUSCH algorithm is based on 4RX IRC receiver as specified in LTE936 considering balance between
performance and complexity
• a large scale antenna data is split to 4 virtual antennas. Pre-combined data from these virtual antennas is the input
of traditional type receiver
• Pre-combining is done based on the long term beamforming weights obtained from SRS

DL long term beamforming Beamforming weight

weights calculation calculation based on SRS

IQ samples from
64 RX antennas
SRS, Pre- 4RX IRC
FFT channel combiner receiver
estimation (LTE936)

mMIMO AAS AirScale system module IQ samples from 4

virtual RX antennas
41 © Nokia 2018 Nokia Internal Use
 Technical Details
PUSCH Receiver: Internal Structure

FFT, Pre- FFT, Pre-

-45

AxC
AxC
+45

16
16 combiner combiner
4RX IRC
Receiver

4 AxC
ABIA #1 Pool 1 ABIA #1 Pool 2

ABIA #2 Pool 1 ABIA #2 Pool 2

FFT, Pre- FFT, Pre-

+45
AxC

AxC
-45
16

combiner

16
combiner

- Get one 16x1 pre-coding vector in each DSP pool for each user based on covariance matrix
- 1 AxC output for each user from each pre-combiner
- Extra processing power will be used in later release for UL MU-MIMO for Massive MIMO (LTE3464)

42 © Nokia 2018
 <feature:LTE4566>

Technical Details
LTE4566 TDD Massive MIMO 10MHz Support

LTE4566

43 © Nokia 2018 Nokia Internal Use

Technical Details
LTE4566 TDD Massive MIMO 10MHz Support
• LTE4566 works with Adaptive Antenna Systems (AAS) provided in Introduction part
• first AAS supported by LTE4566 was LTE3452 AirScale MAA 64T64R 128AE B41 120W AAHB
• basic configuration is as per LTE4630 10MHz configuration for TD-LTE mMIMO

64T
• LTE3452 features: RX
− Integrated antenna
− 120W total output power at 2.6GHz Band (3GPP TDD B41)
− 64 TRXs driving 128 antenna elements, transmitting 1.875W per TRX
− Instantaneous bandwidth 60MHz at 2.6GHz Band (up to 3xLTE20)

LTE2763
• LTE4630 features: Fronthaul
Optical
Passive WDM
− one 10 MHz carrier requires 2x ABIA cards (same as for 20MHz) interface,
supporting 4x
− 4 CPRI links required per carrier
9.8Gbps
− physical layer from 64TXRX fully processed in baseband module CPRI link

44 © Nokia 2018 Nokia Internal Use

Technical Details
LTE4566 TDD Massive MIMO 10MHz Support
• in opposition to LTE2666, LTE4566 is supposed to cover not only SU-MIMO use cases
• LTE4566 deployment took place after deployment of features already extending LTE2666 capabilities
• thus despite the aim of LTE4566 is modification of basic LTE2666 feature only, LTE4566 affects all features that bases on LTE2666 and were released before
TD-LTE18SP
• that allows to avoid necessity of updating a large number of other mMIMO features, the update is included in the LTE4566
• that is why MU-MIMO functionality is in the LTE4566 scope as well
• that means that LTE4566 covers:
- DL MU-MIMO for mMIMO (LTE3463 in case of 20MHz bandwidth)
- DL MU-MIMO for mMIMO 16 layers (LTE4427 in case of 20MHz bandwidth)
- UL MU-MIMO for mMIMO (LTE3464 in case of 20MHz bandwidth)

• however, the range in which LTE4566 covers MU-MIMO functionality is limited only to the bandwidth
• in order to activate 20MHz specific TDD mMIMO functionality in a network with 10MHz cell deployment, relevant 20MHz feature has to be
activated prior to LTE4566 activation
• in newer SW releases (beyond TD-LTE18SP) LTE4566 will only narrow the bandwidth to 10MHz

45 © Nokia 2018 Nokia Internal Use

Technical Details
LTE4566 TDD Massive MIMO 10MHz Support

• in newer SW releases (beyond TD-LTE18SP) LTE4566 will only narrow the bandwidth to 10MHz
• thus activation of LTE4566 is limited to:
− TDD mMIMO activation by setting LNCEL_TDD.actMMimo to ‘True’
in fact mMIMO is activated automatically after Baseband (BB) module discovers TDD mMIMO antenna AAS connected to it
− bandwidth setting LNCEL_TDD.chBw to ‘10MHz’

46 © Nokia 2018 Nokia Internal Use

 <feature:LTE5671>

Technical Details
LTE5671 15MHz carrier support for CPRI based TDD massive MIMO

LTE5671

47 © Nokia 2018 Nokia Internal Use

Technical Details
LTE5671 15MHz carrier support for CPRI based TDD massive MIMO
• in SRAN20B Software (SW) release, the feature LTE5671 15MHz carrier support for CPRI based TDD massive MIMO ports non-mMIMO 15MHz
carrier feature LTE113 Cell Bandwidth - 15 MHz (No WebNEI) to CPRI based TDD mMIMO
• status of LTE5671 is similar to status of LTE4566
• LTE5671 is released after a set of features extending basic LTE2666 capabilities thus despite the main goal of LTE5671 is to support 15MHz cell deployment,
LTE5671 affects all prior SRAN20B TDD mMIMO features
• thus LTE5671 supports:
− 15MHz cell deployment
i de
− 2 CRS port (each polarization mapped to one CRS port) t sl
nex
− frame configuration 2, special sub-frame configuration 5,6,7 on
a il s
− downlink TM2/TM3/TM7/TM8/TM9 with mode switch, 256QAM
re det
− uplink TM1, 64QAM mo
− MU-MIMO downlink 16 and uplink 8 layers
− 2CC TDD CA
− TDD mMIMO capacity boost
− TDD mMIMO on ABIC (16 layers PRB limit apply)

• EXLUSION: LTE5671 does NOT support any of features applicable to 32TRx TDD mMIMO (64TRx split mode not supported)
• in order to activate 20MHz specific TDD mMIMO functionality in a network with 15MHz cell deployment, relevant 20MHz feature has to be
activated prior to LTE5671 activation

48 © Nokia 2018 Nokia Internal Use

Technical Details
Features upgraded by LTE5671 to support 15MHz bandwidth

• LTE5671 inherits following massive MIMO features in 15MHz cell:

− LTE4672 TD-LTE massive MIMO AAS 64T64R 120W B41 AAHF
− LTE4084 TD-LTE massive MIMO AAS 64T64R 120W B40 AANB
− LTE2666 Massive MIMO (WebNEI) • feature that is not supported by LTE5671:
− LTE3463 DL MU-MIMO for massive MIMO (WebNEI) − LTE4655 TDD 32TRX massive MIMO (WebNEI)
− LTE3464 UL MU-MIMO for massive MIMO (WebNEI)
− LTE4427 TDD Massive MIMO Downlink MU-MIMO 16 layers (WebNEI)
− LTE4557 TDD TM9 support for massive MIMO (WebNEI)
− LTE5107 TDD TM9 MU-MIMO support for massive MIMO (WebNEI) despite LTE5671 inherits all mentioned features,
− LTE4567 TDD Massive MIMO Capacity boost (WebNEI) to activate some particular functionality (e.g.
MU-MIMO) with 15MHz cell deployment,
− LTE4573 TDD massive MIMO DL 256QAM and UL 64QAM (WebNEI)
activation of legacy 20MHz specific feature in
− LTE4671 TDD massive MIMO on ABIC (WebNEI) parallel to LTE5671 is still necessary!
− LTE3690 TDD downlink carrier aggregation with massive MIMO (WebNEI)
− LTE3691 TDD uplink carrier aggregation with massive MIMO (WebNEI)
− LTE5141 TDD massive MIMO calibration enhancement (WebNEI)
− LTE4759 HW activation (HWA) licenses for mMIMO (WebNEI)
49 © Nokia 2018 Nokia Internal Use
Technical Details
LTE5671 capacity targets for LTE4567 TDD Massive MIMO Capacity boost (1/2)
• in TD-LTE19 SW release the feature LTE4567 TDD Massive MIMO Capacity boost (WebNEI) was introduced
• the LTE4567 feature increased the number of RRC connected UE served by TDD mMIMO as well as number of UEs
served per TTI for 20MHz as well as for 10MHz cell deployment

• new figures for 15MHz ABIA based deployment are introduced by LTE5671

50 © Nokia 2018 Nokia Internal Use

Technical Details
LTE5671 capacity targets for LTE4567 TDD Massive MIMO Capacity boost (2/2)
• in TD-LTE19 SW release the feature LTE4567 TDD Massive MIMO Capacity boost (WebNEI) was introduced
• the LTE4567 feature increased the number of RRC connected UE served by TDD mMIMO as well as number of UEs
served per TTI for 20MHz as well as for 10MHz cell deployment

• new figures for 15MHz ABIC based deployment are introduced by LTE5671

51 © Nokia 2018 Nokia Internal Use

Technical Details
LTE5671 DL throughput targets

Downlink
BB PiU TM Bandwidth Modulation MU-MIMO
peak L1 target

ABIA/ABIC TM8 64QAM 1UE, 2 layers 70.74 Mbps

ABIA/ABIC TM8 256QAM 1UE, 2 layers 87.67 Mbps

ABIA/ABIC TM8 64QAM 8 layers 281.42 Mbps

ABIA/ABIC TM8 256QAM 8 layers 337.52 Mbps

15MHz
ABIA TM8 64QAM 16 layers 562.84 Mbps

ABIA TM8 256QAM 16 layers 675.03 Mbps

ABIC* TM8 64QAM 16 layers 326.21 Mbps

ABIC* TM8 256QAM 16 layers 398.23 Mbps

* - in LTE4671 TDD massive MIMO on ABIC (WebNEI) there is a limitation against max. supported PRB∙layer
(total number of PRBs multiplicated by number of MU-MIMO layers)

52 © Nokia 2018 Nokia Internal Use

Technical Details
LTE5671 – feature activation and supported configurations

• in newer SW releases (beyond SRAN20B) LTE5671 will only narrow the bandwidth to 15MHz
• thus activation of LTE5671 is limited to:
− TDD mMIMO activation by setting LNCEL_TDD.actMMimo to ‘True’
in fact mMIMO is activated automatically after Baseband (BB) module discovers TDD mMIMO antenna AAS connected to it
− bandwidth setting LNCEL_TDD.chBw to ‘15MHz’

• LTE5671 supports only 64TRx related configurations

• LTE5671 follows selected configurations from:
− LTE3469 AirScale TDD-LTE site configuration for Massive MIMO (WebNEI)
− LTE4298 Triple carrier or three sectors configuration for TDD massive MIMO (WebNEI)
− LTE4719 64Tx64Rx configuration for TDD mMIMO (WebNEI)

53 © Nokia 2018 Nokia Internal Use

Technical Details
Overview of configurations supported by LTE5671
Number of

Sector Max

LTE2866
needed
sectors

configuration number of Cell

Carrier layout Fronthaul
type / number of carriers set
RF family cable solution CFID
TXs/RXs per sector type

Z type:
1 2 2 Z (15+15MHz) Vb CWDM #3469-5BCL1-T2-Z-76 No
64Tx/64Rx
Z type: Break-out
1 2 2 Z (15+15MHz) Vb #3469-5BCL1-T2-Z-76 No
64Tx/64Rx cable
Z type: FRMTDr3.4_AAS_64T64R,
3 1 1+1+1 Z (15MHz) VII cMAA_Gen3.14_64T64R CWDM #4298-7CL3-T111-Z-97 Yes
64Tx/64Rx
Z type: AAHF or AANB Break-out
3 1 1+1+1 Z (15MHz) VII #4298-7CL3-T111-Z-97 Yes
64Tx/64Rx is required cable
Z type:
1 2 2 Z (15+15MHz) II CWDM #4719-2CL1-T2-Z-197 Yes
64Tx/64Rx
Z type: Break-out
1 2 2 Z (15+15MHz) II #4719-2CL1-T2-Z-197 Yes
64Tx/64Rx cable

• all sub-configurations are supported

54 © Nokia 2018
 LTE5671 ABIA based example configuration #1
Technical Details
LTE3469 AirScale TDD-LTE site configuration for Massive MIMO
One sector configuration
CFID: #3469-5BCL1-T2-Z-76 More details
HERE and 15MHz
• One sector, dual carrier configuration HERE
AAHF or AANB
• CWDM solution 15MHz is required
• One RRU connected to the ports of two CWDM
components (one cable between RRU and each CWDM)
QSFP+
• Two CWDM components connected to the eight ports of
four ABIAs (two optical cables between CWDM and any CWDM CWDM
two ABIA ports which supports IQC (RF1,RF2,RF3)) #1 #2
• Links between ABIA and CWDM are configured as CPRI
9.8Gbps link rate
• Each link between system module and radio module
Nokia CPRI 9.8G
requires IQC and down-sampling enabled IQC&DS Enabled
• Two ABIAs support single carrier. Each carrier is
processed in one half sub-rack
• Two ABIAs from one half sub-rack have to be connected to SFP+
same CWDM component

55 © Nokia 2018 Nokia Internal Use

 LTE5671 ABIA based example configuration #2
Technical Details
LTE4298 Triple carrier or three sectors configuration for TDD massive MIMO

Three sector configuration

CFID: #4298-7CL3-T111-Z-97 More details
HERE and LTE2866 is mandatory prerequisite
• Three sector, single carrier configuration HERE
Sector 1 Sector 2 Sector 3
• Break-out cable solution
15MHz 15MHz 15MHz
• Three RRUs connected to the six ABIAs by three break-
out cables
• Each break-out cable connects one RRU port and four
ABIA ports (two ports (RF1,RF2,RF3) on each ABIA can
QSFP+ QSFP+ QSFP+
be used)
3xAAHF or
• Links between ABIAs and RRU are configured as CPRI 3xAANB
9.8Gbps link rate is required
• IQC and down-sampling are enabled
• Two ABIAs support single carrier: Nokia CPRI 9.8G
IQC&DS Enabled
• Two ABIAs in left half sub-rack support single carrier, and
• Two ABIAs in right half sub-rack support single carrier, and
• Two ABIAs (one in the right and one in the left half sub-rack)
support single carrier
SFP+

56 © Nokia 2018 Nokia Internal Use

 LTE5671 ABIC based example configuration #1
Technical Details
LTE4719 64Tx64Rx configuration for TDD mMIMO One sector configuration

CFID: #4719-2CL1-T2-Z-197 More details

HERE and
One sector, dual carrier configuration, 64T64R HERE 15MHz 15MHz
• Break-out cable solution
• One RRU connected to the one ABIC by two break-out
cables
• One break-out cable connects one RRU port and four ABIC QSFP+ AAHF or AANB
ports is required
Nokia CPRI 9.8G
IQC&DS Enabled
• Links between ABIC and RRU are configured as CPRI
9.8Gbps
• Each link between system module and radio module requires
IQC and down-sampling are enabled

57 © Nokia 2018
Technical Details
TDD massive MIMO

CR based
improvements

58 © Nokia 2018 Nokia Internal Use

Technical Details
Scheduler

• LTE2666/LTE4566/LTE5671 reuses legacy LTE Scheduler

• legacy LTE Scheduler is modified for the needs of MU-MIMO in LTE3463 and LTE3464
(from TD-LTE18 and TD-LTE18SP respectively)
• in SRAN 20A support for packet aggregation scheduling (PAS) and prioritized tail packet (PTP) scheduling algorithms is
introduced in DL by LTERLCR-31487
• LTERLCR-31487:
‑ its goal is to improve DL UE throughput
‑ is controlled by R&D parameters and valid for India customers ONLY (controlled by PLMN-ID restriction)
‑ is valid for both ABIA and ABIC, 32TRX and 64TRX carriers, for CPRI based TDD massive MIMO only

• in SRAN20B based on LTERLCR-31487 the regular feature

LTE5674 Downlink QoE based scheduling enhancement for TDD massive MIMO has been released
• PAS & PTP description is available in
LTE5674 Downlink QoE based scheduling enhancement for TDD massive MIMO (WebNEI)

59 © Nokia 2018
Technical Details
Beamforming - new parameters introduced by LTERLCR-27155 in TD-LTE19 (1/2)

• to save lots of service effort for the network optimization, in TD-LTE19 a set of R&D parameters was converted into OAM
parameters, thus enabling their change via SEM/Netact (i.e. remotely instead manually on site)

Name Description
The maximum allowed value for beamforming gain for downlink is in order to balance between performance and robustness. It is
dlMaxBfGain (mMimoParaSet) configured together with dlBfGainCoeff. The beamforming gain of UE beam shall be restricted via maximum allowed value and
coefficient because it is evaluted too optimistic in some scenario.

The coefficient for restriction of beamforming gain for downlink is in order to balance between performance and robustness. It is
dlBfGainCoeff (mMimoParaSet) configured together with dlMaxBfGain.The beamforming gain of UE beam shall be restricted via maximum allowed value and
coefficient because it is evaluated too optimistic in some scenario.

The timer to delay to use service beamforming weight (milli-scecond) calculated from SRS is to avoid performance loss. The
delayUseBfWeightTimer (mMimoParaSet) initial name of this parameter was delayToUseBfWeightTimer

The threshold of beamforming gain (linear scale) for downlink. The beamforming weight should not be applied when the
bfGainThd (mMimoParaSet) beamforming gain is low than the threshold.

bfWeightAgingCoeff The aging coefficient to calculate beamforming weight.

60 © Nokia 2018
Technical Details
Beamforming - new parameters introduced by LTERLCR-27155 in TD-LTE19 (2/2)

• to save lots of service effort for the network optimization, in TD-LTE19 a set of R&D parameters was converted into OAM
parameters, thus enabling their change via SEM/Netact (i.e. remotely instead manually on site)

Name Description

actDlBfUeHighBlerMitigation The activation of mitigating higher DL BLER for certain sorts of UE chipset while using beamforming.

MU-MIMO beam interference cancellation method selection in horizontal direction for downlink.
dlMuBfIcMethodH More in LTE3463 NEI material (WebNEI)

MU-MIMO beam interference cancellation method selection in vertical direction for downlink.
dlMuBfIcMethodV More in LTE3463 NEI material (WebNEI)

MU-MIMO beam interference cancellation method selection in horizontal direction for uplink.
ulMuBfIcMethodH More in LTE3464 NEI material (WebNEI)

MU-MIMO beam interference cancellation method selection in vertical direction for uplink.
ulMuBfIcMethodV More in LTE3464 NEI material (WebNEI)

61 © Nokia 2018
Technical Details
Beamforming – parameter overloading by LTERLCR-30353 in TD-LTE19 (1/2)

• in TD-LTE19 an overloaded definition of delayUseBfWeightTimer was introduced by LTERLCR-30353

• the change was valid through: TD-LTE19, TD-LTE19A & TD-LTE19B and available ONLY for Sprint U.S. PLMN IDs
• the purpose of new overloaded definition was to:
‑ enable handling of at least discrete control over the HARQ feedback 'ANY' type. This allowed adjustment of the
proportion of control given to this type of feedback in the OLLA control
‑ enable discrete on/off control over forward long term beamforming weights to be conveyed from PCell to Scell. This
allowed for use of UL CA's SCell SRS for beamforming vector generation if there is UL CA's SCell SRS - if enabled (else
no use of UL CA's SCell SRS for beamforming vector generation - if disabled)

• initially delayUseBfWeightTimer was a 10 bit number

• after LTERLCR-30353 number of bits that were dedicated to report delayUseBfWeightTimer only was decreased to 4 bits
(details on the next slide) – therefore step was changed to 200ms
• remaining 6 bits were used to report several different R&D parameters (details on the next slide)
• available ONLY for Sprint U.S. PLMN IDs (TDD only)

62 © Nokia 2018
Technical Details
Beamforming – parameter overloading by LTERLCR-30353 in TD-LTE19 (2/2)
• available ONLY for Sprint U.S. PLMN IDs

Bit 9 8 7 6 5 4 3 2 1 0

Parameter delayUseBfWeightTimer TRdOllaForANY EnableScellSrs DiffCwForTM8

Controls the forwarding of long

Controls the downgrade step of Controls the alignment of TM8
term weights from Pcell to Scell.
PDSCH OLLA for feedback type with other Tx Modes for deltaCQI
Controls delayBfWeightTimer If enabled then use UL CA's Scell
ANY. 0 means rrmDeltaCqi not handling. If enabled then TM8
[bits 6-9] Range 2^4 = 16 steps SRS for bfWeight generation if
affected by ANY. 10 means maintain rrmdeltaCqi for each
Description 16 steps x [200ms] = [0..3000ms]
100% downgrade step of NACK
there is UL CA's Scell SRS. If
codeword independently. If
disabled then UL CA's Scell SRS
is used for ANY. Use values disabled, align TM8 with other
e.g. 2000ms = b0101 is not used and UL CA's SCELL
[0..10]. Example shown = b0011 TM which maintain same
will use the one forwarded from
= 3 (30%) rrmDeltaCqi for all codewords
PCELL

Bits reported as part of delayUseBfWeightTimer

delayUseBfWeightTimer x x x x but not used for delayUseBfWeightTimer (overloaded meaning)

OFF disable 0 disable 0

ON enable 1 enable 1

63 © Nokia 2018
Technical Details
Beamforming - parameter overloading removal by LTERLCR-30540

• in TD-LTE19 an overloaded definition of delayUseBfWeightTimer was introduced by LTERLCR-30353

• the change was valid through: TD-LTE19, TD-LTE19A & TD-LTE19B and available ONLY for Sprint U.S. PLMN IDs
• in TD-LTE20A/SRAN20A delayUseBfWeightTimer is set back by LTERLCR-30540 to the initial definition introduced
prior to LTERLCR-30353
• that means that overloaded meaning of delayUseBfWeightTimer has been withdrawn
• in parallel to that, a new OAM parameter TDD_LNCELL.mMimoParaSet.actDualOllaForTM8 is introduced

• in LTERLCR-30540:
‑ Bit 0 value (DiffCwForTM8) of delayUseBfWeight following LTERLCR-30353 meaning is translated to
actDualOllaForTM8
‑ delayUseBfWeightTimer range changes from “0-3000 ms step 200” to “0-3000 ms step 1”
‑ delayUseBfWeightTimer default value changes from 500 to 2000
‑ migrates delayUseBfWeightTimer Bits 6-9 from TD-LTE19B (LTERLCR-30353) meaning to TD-LTE20A (
LTERLCR-30540) meaning

64 © Nokia 2018
Technical Details
Beamforming - new parameters introduced by LTERLCR-29317 in TD-LTE19A
(1/2)
• to save lots of service effort for the network optimization, in TD-LTE19 a set of R&D parameters was converted into OAM
parameters by LTERLCR-27155
• in TD-LTE19A LTERLCR-29317 a set of OAM settings has been extended by addition of new OAM parameters
• improvements introduced by LTERLCR-29317 from TD-LTE19A were however postponed to TD-LTE19B, where
implementation of LTERLCR-29317 was executed by LTERLCR-29914
• parameters introduced by LTERLCR-29317 are as follows:

Name Description

actExtendedDelayToUseBfWeightTimer This parameter activates extended timer to delay to use beamforming weight in TDD Massive MIMO

The parameter specifies the target power per PRB per pipe of SRS to calculate extended timer to delay to use beamforming weight
mMimoParaSet.targetSrsPower in TDD Massive MIMO

mMimoParaSet.extendedDelayFactor The parameter specifies the scaling factor of extended timer to delay to use beamforming weight in TDD Massive MIMO

Please refer also to CB006549 (WebNEI) as it has converted LTERLCR-29317 R&D parameter into OAM parameter

65 © Nokia 2018
Technical Details
Beamforming - new parameters introduced by LTERLCR-29317 in TD-LTE19A
(2/2)
• purpose of LTERLCR-29317 is to extend delay introduced by LTERLCR-27155 in TD-LTE19
• in LTERLCR-29317 additional, SRS quality based delay can be activated
• as a result delay introduced by LTERLCR-27155 and controlled by delayUseBfWeightTimer can be further extended
• the goal is to improve overall system performance

• improvements introduced by LTERLCR-29317 from TD-LTE19A were however postponed to TD-LTE19B, where
implementation of LTERLCR-29317 was executed by LTERLCR-29914

• LTERLCR-29317 was initially postponed by LTERLCR-30967 but finally

shifted back to TD-LTE19B by LTERLCR-31397 and executed in TD-LTE19B by LTERLCR-29914

66 © Nokia 2018
LTE2666 Massive MIMO, LTE4566 TDD Massive MIMO 10MHz support

Benefits and Gains

Table of contents

<chapter:benefits_and_gains>

67 © Nokia 2018 Nokia Internal Use

Benefits and Gains
LTE2666 System Level Simulations Single User DL MIMO

Mobile Users within 3D-UMa Cells (Macro Downlink cell throughput

scenario) with Buildings 60000

• Full Buffer traffic +115%

50000
+113%
• TM8

Throughput [kbps]
40000
+40% +136%
+59%
• SU-MIMO, MU-MIMO (8 users) 30000 +56%

• Reference scenario: 8TX 20000

10000

Source: Network Engineering system level simulations 0

UMa (no buildings) UMa UMi

8Tx SU 64Tx SU 64Tx MU

There is about 40% - 59% gain (depending on
scenario) in downlink cell throughput after
switching from 8Tx to 64Tx.

68 © Nokia 2018 Nokia Internal Use

Benefits and Gains
LTE2666 Static User Locations within 3D-UMi-LoS (microcell, line of sight)

Downlink • stationary users experience more stable channel and

therefore channel estimates are more reliable. This is
25 16 reflected in spectral efficiency gain, and eventually to
14 higher DL cell throughput
20 • please note, that simulations shown here are for massive
Spectrum efficiency (bit/s/Hz)

12
MU-MIMO case, gain for single user is not shown,
10

# layers per PRB

15 however similar quantitative impact is expected also for
8 SU-MIMO case
10 20.2 20.6
9%

6
2
+4

13.6 4
5
2
2.57
0 0
8Tx 64Tx 64Tx 128Tx
single user 4 users 8 users 8 users

Spectrum efficiency (bit/s/Hz) # layers per PRB

Source: https://sharenet-ims.int.net.nokia.com/livelink/livelink/overview/D550070418

69 © Nokia 2018
Benefits and Gains
LTE2666 Mobile Users, uplink

• single user UL throughput gain is about 30% compared

to 8T8R.
• in case of 8T8R the receiver is 8RX IRC, which should
outperform 4RX IRC used by LTE2666, all other things
considered equal. However in case of 8T8R there are
+30% only 8 active antenna elements. In case of 64T64R pre-
combining over four groups of 16 antennas in the
mMIMO AAS is able to compensate for lower IRC
receiver complexity, and bring an additional gain.
• please see Technical Details section for more
information on the uplink receiver in LTE2666.

Source: https://sharenet-ims.int.net.nokia.com/Overview/D551644206

70 © Nokia 2018 Nokia Internal Use

Benefits and Gains
Peak cell throughput comparison for 10MHz, 15MHz and 20MHz massive MIMO

Uplink Downlink
Feature Bandwidth/PiU
peak L1 target peak L1 target
LTE2666 20MHz/ABIA 9.996 Mbps 92.0 Mbps

LTE5671 15MHz/ABIA 6.802 Mbps 70.7 Mbps

LTE4566 10MHz/ABIA 4.680 Mbps 46.13 Mbps

UL settings DL settings
transmission mode – TM1 transmission mode - TM8
MCS - MCS24 MCS - MCS28
SSF config – any SSF config – 7
Frame Config – 2 Frame Config – 2
Rank – 1 Rank – 2, Layer – 2
16QAMHighMCS 64QAM

71 © Nokia 2018 Nokia Internal Use

LTE2666 Massive MIMO, LTE4566 TDD Massive MIMO 10MHz support

Interdependencies

Table of contents

<chapter:interdependencies>

72 © Nokia 2018 Nokia Internal Use

Interdependencies

LTE2666
LTE4566

73 © Nokia 2018 Nokia Internal Use

Interdependencies
LTE2666 & LTE4566

Following features are prerequisites for LTE2666 and LTE4566

prerequisites
• LTE3452 AAU TD-LTE massive MIMO AAS 64T64R B41 120W AAHB
• LTE3469 AirScale TDD-LTE site configuration for Massive MIMO
These features cover 64T64R Massive MIMO AAS and baseband configuration
• LTE541 Dual Stream Beamforming
LTE2666 bases on the hybrid DL beamforming algorithm introduced by LTE541

74 © Nokia 2018 Nokia Internal Use

Interdependencies
LTE2666 & LTE4566

Following features are not supported with LTE2666 and LTE4566

limitations
LTE1089: Downlink carrier LTE1987: Downlink Adaptive Closed
aggregation - 20 MHz Loop SU MIMO (4x4)
LTE1103: Load based Power Saving LTE2733: Baseband pooling
for multi-layer networks LTE48: Support of High Speed Users
LTE1130: Dynamic PUCCH allocation LTE495: OTDOA
LTE1203: Load based Power Saving LTE73: UL MU MIMO 4RX
with Tx path switching off
LTE993: Cell Combination (Super cell)
LTE1709: Liquid Cell

75 © Nokia 2018 Nokia Internal Use

Interdependencies
LTE2666 & LTE4566

Following functionalities are not supported with LTE2666 and LTE4566

limitations
LTE2479 256 QAM in downlink
this constraint was removed by LTE4573
LTE1691 UL CoMP for 4RX
LTE2462 Coordinate Scheduling for Beamforming Interference Avoidance
LTE1929 UL SPS Scheduler
LTE1117 LTE eMBMS
LTE1113 eICIC
LTE180 Large cell radius
PRACH format 4

76 © Nokia 2018 Nokia Internal Use

Interdependencies
LTE2666 & LTE4566

Following functionalities extends capabilities of LTE2666 and LTE4566

extensions
LTE3463 DL MU-MIMO for Massive MIMO
LTE3464 UL MU-MIMO for Massive MIMO (in TL18SP)
These features introduce multiuser MIMO functionalities for LTE2666 and
LTE4566

LTE1013 Dynamic transmission Mode Switch

This feature allows for switching between transmission modes resulting in higher
peak and average throughput

77 © Nokia 2018 Nokia Internal Use

Interdependencies

LTE5671

78 © Nokia 2018 Nokia Internal Use

Interdependencies
LTE5671
Exact set of features that are prerequisites for LTE5671 depends on the desired TDD
mMIMO configuration
prerequisites
• LTE4672 TD-LTE massive MIMO AAS 64T64R 120W B41 AAHF
• LTE4084 TD-LTE massive MIMO AAS 64T64R 120W B40 AANB
• LTE2666 Massive MIMO
• LTE3463 DL MU-MIMO for massive MIMO
• LTE3464 UL MU-MIMO for massive MIMO
• LTE4427 TDD Massive MIMO Downlink MU-MIMO 16 layers
• LTE4557 TDD TM9 support for massive MIMO
• LTE5107 TDD TM9 MU-MIMO support for massive MIMO
• LTE4567 TDD Massive MIMO Capacity boost
• LTE4573 TDD massive MIMO DL 256QAM and UL 64QAM

79 © Nokia 2018 Nokia Internal Use

Interdependencies
LTE5671
Exact set of features that are prerequisites for LTE5671 depends on the desired TDD
mMIMO configuration
prerequisites
• LTE4671 TDD massive MIMO on ABIC
• LTE5400 TDD massive MIMO ABIC remaining porting
• LTE5578 TDD massive MIMO ABIC remaining porting II
• LTE5736 TDD massive MIMO two carriers per ABIC with 16 layer
• LTE3690 TDD downlink carrier aggregation with massive MIMO
• LTE3691 TDD uplink carrier aggregation with massive MIMO
• LTE5141 TDD massive MIMO calibration enhancement

80 © Nokia 2018 Nokia Internal Use

Interdependencies
LTE5671
Set of features that are not supported by LTE5671 contains the set of features that
are not supported by all underlaying prerequisite features
limitations with addition of:
• LTE5723 Inter site TDD - FDD DL carrier aggregation 5CC with TDD ABIC
mMIMO
• LTE4655 TDD 32TRX massive MIMO

81 © Nokia 2018 Nokia Internal Use

LTE2666 Massive MIMO, LTE4566 TDD Massive MIMO 10MHz support

Configuration
Management
Table of contents

<chapter:configuration_management>

82 © 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

83 © Nokia 2018 Nokia Internal Use

Configuration Management
New parameters LTE2666 Massive MIMO

Abbreviated name Full name MIND link

LNCEL_TDD:actMMimo Massive MIMO activation (read only)

LNCEL_TDD:mMimoSectorBFProfName Massive MIMO profile name

LNBTS:MMIMOCPR:mMimoDlSBFWeig Massive MIMO DL sector beamforming

htProfName weight profile name
MMIMOCPR:modulusOfAntGrp0H.. Modulus of weight for horizontal antenna
modulusOfAntGrp7H group 0..7

MMIMOCPR:modulusOfAntGrp0V..
modulusOfAntGrp3V Modulus of weight for vertical antenna
group 0..3

REQUIRES BTS REQUIRES CELL LOCKING ONLINE MODIFIABLE

84 RESTART
© Nokia 2018 Nokia Internal Use
Configuration Management
New parameters LTE2666 Massive

Abbreviated name Full name MIND link

MMIMOCPR:phaseOfAntGrp0H.. Phase of weight for horizontal antenna
phaseOfAntGrp7H group 0..7
MMIMOCPR:phaseOfAntGrp0V.. Phase of weight for vertical antenna group
phaseOfAntGrp3V 0..3

REQUIRES BTS REQUIRES CELL LOCKING ONLINE MODIFIABLE

85 RESTART
© Nokia 2018 Nokia Internal Use
Configuration Management
New parameters LTERLCR-27155 from TD-LTE19

Abbreviated name Full name MIND link

The maximum allowed value of downlink
LNCEL_TDD.mMimoParaSet.dlMaxBfGain
beamforming gain for TDD mMIMO
The coefficient for restriction of downlink
LNCEL_TDD.mMimoParaSet.dlBfGainCoeff
beamforming gain for TDD mMIMO
LNCEL_TDD.mMimoParaSet.delayToUseBf The timer to delay using service beamforming Initial name, parameter’s name changed
WeightTimer weight
LNCEL_TDD.mMimoParaSet.delayUseBfWe The timer to delay using service beamforming
ightTimer weight
The threshold of beamforming gain for TDD
LNCEL_TDD.mMimoParaSet.bfGainThd
mMIMO
The aging coefficient to calculate beamforming
LNCEL_TDD.bfWeightAgingCoeff
weight

LNCEL_TDD.actDlBfUeHighBlerMitigation The activation of mitigating higher DL BLER

REQUIRES BTS REQUIRES CELL LOCKING ONLINE MODIFIABLE

86 RESTART
© Nokia 2018 Nokia Internal Use
Configuration Management
New parameters LTERLCR-29317 from TD-LTE19B

Abbreviated name Full name MIND link

LNCEL_TDD.actExtendedDelayToUseBfWeigh Extended timer to delay to use beamforming
tTimer weight activation

LNCEL_TDD.mMimoParaSet.targetSrsPower Target Sounding reference signal power

LNCEL_TDD.mMimoParaSet.extendedDelayFa
Scaling factor of extended delay timer
ctor

• improvements introduced by LTERLCR-29317 from TD-LTE19A were postponed to TD-LTE19B, where implementation
of LTERLCR-29317 was executed by LTERLCR-29914

REQUIRES BTS REQUIRES CELL LOCKING ONLINE MODIFIABLE

87 RESTART
© Nokia 2018 Nokia Internal Use
Configuration Management
Parameter overloading by LTERLCR-30353 in TD-LTE19 (1/2)

• in TD-LTE19 an overloaded definition of delayUseBfWeightTimer was introduced by LTERLCR-30353

• the change was valid through: TD-LTE19, TD-LTE19A & TD-LTE19B and available ONLY for Sprint U.S. PLMN IDs
• the purpose of new overloaded definition was to:
‑ enable handling of at least discrete control over the HARQ feedback 'ANY' type. This allowed adjustment of the
proportion of control given to this type of feedback in the OLLA control
‑ enable discrete on/off control over forward long term beamforming weights to be conveyed from PCell to Scell. This
allowed for use of UL CA's SCell SRS for beamforming vector generation if there is UL CA's SCell SRS - if enabled (else
no use of UL CA's SCell SRS for beamforming vector generation - if disabled)

• initially delayUseBfWeightTimer was a 10 bit number

• after LTERLCR-30353 number of bits that were dedicated to report delayUseBfWeightTimer only was decreased to 4 bits
(details on the next slide) – therefore step was changed to 200ms
• remaining 6 bits were used to report several different R&D parameters (details on the next slide)
• available ONLY for Sprint U.S. PLMN IDs (TDD only)

88 © Nokia 2018
Configuration Management
Parameter overloading by LTERLCR-30353 in TD-LTE19 (2/2)
• available ONLY for Sprint U.S. PLMN IDs

Bit 9 8 7 6 5 4 3 2 1 0

Parameter delayUseBfWeightTimer TRdOllaForANY EnableScellSrs DiffCwForTM8

Controls the forwarding of long

Controls the downgrade step of Controls the alignment of TM8
term weights from Pcell to Scell.
PDSCH OLLA for feedback type with other Tx Modes for deltaCQI
Controls delayBfWeightTimer If enabled then use UL CA's Scell
ANY. 0 means rrmDeltaCqi not handling. If enabled then TM8
[bits 6-9] Range 2^4 = 16 steps SRS for bfWeight generation if
affected by ANY. 10 means maintain rrmdeltaCqi for each
Description 16 steps x [200ms] = [0..3000ms]
100% downgrade step of NACK
there is UL CA's Scell SRS. If
codeword independently. If
disabled then UL CA's Scell SRS
is used for ANY. Use values disabled, align TM8 with other
e.g. 2000ms = b0101 is not used and UL CA's SCELL
[0..10]. Example shown = b0011 TM which maintain same
will use the one forwarded from
= 3 (30%) rrmDeltaCqi for all codewords
PCELL

Bits reported as part of delayUseBfWeightTimer

delayUseBfWeightTimer x x x x but not used for delayUseBfWeightTimer (overloaded meaning)

OFF disable 0 disable 0

ON enable 1 enable 1

89 © Nokia 2018
Configuration Management
Parameter overloading by LTERLCR-30353 and change by LTERLCR-30540

• in TD-LTE19 an overloaded definition of delayUseBfWeightTimer was introduced by LTERLCR-30353

• the change was valid through: TD-LTE19, TD-LTE19A & TD-LTE19B and available ONLY for Sprint U.S. PLMN IDs
• in TD-LTE20A/SRAN20A delayUseBfWeightTimer is set back by LTERLCR-30540 to the initial definition introduced
prior to LTERLCR-30353
• that means that overloaded meaning of delayUseBfWeightTimer has been withdrawn
• in parallel to that, a new OAM parameter TDD_LNCELL.mMimoParaSet.actDualOllaForTM8 is introduced

• in LTERLCR-30540:
‑ Bit 0 value (DiffCwForTM8) of delayUseBfWeight following LTERLCR-30353 meaning is translated to
actDualOllaForTM8
‑ delayUseBfWeightTimer range changes from “0-3000 ms step 200” to “0-3000 ms step 1”
‑ delayUseBfWeightTimer default value changes from 500 to 2000
‑ migrates delayUseBfWeightTimer Bits 6-9 from TD-LTE19B (LTERLCR-30353) meaning to TD-LTE20A (
LTERLCR-30540) meaning

90 © Nokia 2018
Configuration Management
New parameters LTERLCR-30540 from SRAN20A

Abbreviated name Full name MIND link

LNCEL.LNCEL_TDD.actDualOllaForTM8 Activate Dual OLLA for TM8

REQUIRES BTS REQUIRES CELL LOCKING ONLINE MODIFIABLE

91 RESTART
© Nokia 2018 Nokia Internal Use
Configuration Management
New parameters CRL-23564

Abbreviated name Full name MIND link

LNBTS_TDD.mMimoSectorBFProf.mMi
unmodifable
moSectorBfProfRFMGroupId

REQUIRES BTS REQUIRES CELL LOCKING ONLINE MODIFIABLE

92 RESTART
© Nokia 2018 Nokia Internal Use
Configuration Management
New parameters LTE4566 and LTE5671

New parameters LTE4566 TDD Massive MIMO 10Mhz Support

• LTE4566 reuses all LTE2666 parameters and does not introduce any new parameters

New parameters LTE5671 15MHz carrier support for CPRI based

TDD massive MIMO
• LTE5671 reuses all LTE2666 parameters and does not introduce any new parameters

93 © Nokia 2018 Nokia Internal Use

LTE2666 Massive MIMO, LTE4566 TDD Massive MIMO 10MHz support

Deployment
Aspects
Network graphic boxes Network element boxes
Table of contents

<chapter:deployment_aspects>

94 © Nokia 2018 Nokia Internal Use

Deployment Aspects
LTE2666 Massive MIMO, LTE4566 TDD Massive MIMO 10MHz support

• Based on LTERLCR-25434

• TDD mMIMO originally restricted the cell maximum total power to 40W per 20MHz for 64TRX due to radio emission
performance limitation
• after HW internal test it is confirmed that the performance of 60W shall be acceptable for AAHC
• as all TDD mMIMO official AASs 64TRX in TD-LTE18A or earlier release follow the same platform, it is reasonable to
believe more radios shall follow the new limitation

• after this CR Nokia support cell maximum total power as below for designated TDD mMIMO official AASs 64TRX in
TD-LTE18A or earlier release (B41,B40,B38):
− 20MHz 64TRX 60W
− 10MHz 64TRX 40W (legacy rule)

95 © Nokia 2018 Nokia Internal Use

Deployment Aspects
LTE2666 Massive MIMO, LTE4566 TDD Massive MIMO 10MHz support

• Based on LTERLCR-25434
• for special areas there may be specific governance rules, e.x. U.S.A FCC
• this CR does not cover these specific market radios (AAHJ, AAHE)
• for these specific markets eNB will check:
− maximum power limitation per carrier (20MHz or 10MHz)
− total AAS maximum power limitation (this CR has no intention to increase total AAS power)

• NOTE: AAS requires multi-carrier flat power spectrum density(20MHz+10MHz configuration example: 20MHz 60W,
then 10MHz 30W), operators should follow this rule for configuration
• NOTE: the same family AASs beyond TD-LTE18A shall follow the same limitation
• NOTE: 32TRx split mode maximum cell power is defined in TD-LTE18A LTE4655 TDD 32TRX massive MIMO
(WebNEI) and shall follow the similar principle (e.x. half cell maximum total power of 64TRx)

96 © Nokia 2018 Nokia Internal Use

Deployment Aspects
80W/LTE20 support to Compass MAA, AAHC/AAHF/AANB

• Based on LTERLCR-29794 from SRAN19A

• India operators demand higher power density per 20MHz LTE carrier
• LTERLCR-29794 is created to update the maximum supported carrier power from 60 to 80W for Compass platform MAA in
the India market (with 3GPP compliance only. FCC compliance not supported), AAHC/AAHF/AANB principle (e.x. half cell
maximum total power of 64TRx)

• Based on LTERLCR-30522 from SRAN19B part of LTERLCR-29794 that is related to LTE4084 AANB has been moved to
SRAN20A

• Based on LTERLCR-31080 from SRAN20A, Power step has been changed from 0.5 to 0.1 for the following RUs: AAHB,
AAHC, AAHD, AAHE, AAHF, AAHJ, AANA, AANB, AEHB, AZHA, AZHE, AZNA, AZNB, AZNC, AZND, AZNE,
AZQD, AZQF, AZQR, FZQJ-1, FZQJ-2

97 © Nokia 2018 Nokia Internal Use

Deployment Aspects
LTE2666 Massive MIMO, LTE4566 TDD Massive MIMO 10MHz support

• due to improved antenna gain and capability of vertical beamforming DL coverage and capacity is
increased as well when compared to the legacy 8-column beamforming antennas.
• another purpose of the feature is to increase site capacity in dense urban environments with high rise
buildings owing to 3D beamforming.

• please keep in mind that LTE2666 will usually not be deployed “as is” but also with combination of other
features, especially LTE3463 DL MU-MIMO for Massive MIMO. Therefore feature potential of increasing
the capacity should be considered in the first place.

• as supported bandwidth is the main and only factor by which LTE4566 differ from LTE2666, same
conclusion apply for LTE4566.

98 © Nokia 2018 Nokia Internal Use

Deployment Aspects
LTE2666 Feature activation/deactivation (1/3)

• feature activation flag (LNCEL_TDD:actMMimo) is a read-only parameter. It is automatically set to true

whenever a 64T64R radio is commissioned.
• it is possible to force feature to work in a sector beam mode, when user beamforming will be deactivated.
This can be used to show the true benefits of the feature in field trial conditions.
• use combination of LNCEL_TDD:dlMimoMode and LNCEL_TDD:actTmSwitch for the desired effect.

dlMimoMode = Dynamic Open Loop MIMO

actTmSwitch = true TM3/8 switch activated

actTmSwitch = false TM3 only, only sector

beam in use

99 © Nokia 2018 Nokia Internal Use

Deployment Aspects
LTE2666 Feature activation/deactivation (2/3)

Open Loop
MIMO.
Interworking with
TM switching is AAHB and 2
supported. ABIAs are
configured

100 © Nokia 2018 Nokia Internal Use

Deployment Aspects
LTE2666 Feature activation/deactivation (3/3)

actmMimo flag
set to true if
64T64R radio is
detected

101 © Nokia 2018 Nokia Internal Use

Deployment Aspects
Macro-0 Electrical Tilt-(0)
LTE2666 Sector Beam Configuration (1/3) Macro-0 Electrical Tilt-(1)
Macro-0 Electrical Tilt-(2)
Macro-0 Electrical Tilt-(3)
Macro-0 Electrical Tilt-(4)
• Massive MIMO AAS that is used with LTE2666 does not provide a remote electrical Macro-0 Electrical Tilt-(5)
Macro-0 Electrical Tilt-(6)
tilt (RET) function. Instead, vertical sector beam tilt is controlled entirely by the Macro-0 Electrical Tilt-(7)
baseband and is selected from 12 predefined sector beamforming profiles. The tilts Macro-0 Electrical Tilt-(8)
Macro-0 Electrical Tilt-(-1)
of the predefined profiles range from +8 to -2 degrees, and are indicated in the profile Macro-0 Electrical Tilt-(-2)
name. High Building-0
customized profile 1
• in addition to the tilted profiles, there is an additional predefined sector beam profile for customized profile 2
customized profile 3
the high rise building use case. customized profile 4
customized profile 5
• operator may define additional 20 customized sector beam profiles in MMIMOCPR customized profile 6
customized profile 7
managed object class. customized profile 8
customized profile 9
• sector beam profile selection is done by setting parameter customized profile 10
LNCEL_TDD:mMimoSectorBFProfName customized profile 11
customized profile 12
to a corresponding predefined or customized profile name customized profile 13
customized profile 14
customized profile 15
customized profile 16
• selection of the sector beam should be done following radio network planning, as it customized profile 17
involves deployment of a new antenna system with new radiation pattern. customized profile 18
customized profile 19
customized profile 20

102 © Nokia 2018 Nokia Internal Use

Deployment Aspects
LTE2666 Sector Beam Configuration (2/3)

Sector beam
profile
selection
103 © Nokia 2018 Nokia Internal Use
Deployment Aspects
LTE2666 Sector Beam Configuration (3/3)

Customized sector
beamforming profile
may be added in
MMIMOCPR.
MMIMOCPR object Sector beam profile
can be created in selection
LNBTS

Horizontal and
vertical beamforming
weights to be defined
in customized profile

104 © Nokia 2018 Nokia Internal Use

Deployment Aspects
LTE2666 Massive MIMO

Additional parameters, recommended/required settings

Parameter name Abbreviation Description Range and Step Required/ MOC
recommended
value
Channel chBw Channel Bandwidth defines the 10 MHz (100), 15 20MHz (200) LNCEL_TDD
bandwidth TDD Downlink and Uplink bandwidth MHz (150), 20
for the eNode-B transmission. MHz (200)
TDD subframe tddFrameConf Indicates the uplink-downlink 1...2, step 1 2 LNCEL_TDD
configuration subframe configuration in TDD.
TDD special tddSpecSubfCo The TDD Special Subframe 0...9, step 1 7 LNCEL_TDD
subframe nf Configuration parameter is used for
configuration the configuration of DwPTS, GP
and UpPTS in the special subframe
Activate actModulationS Selects the highest modulation QPSK (0), 64QAM (2) LNCEL
modulation chemeDl scheme for link adaptation use in 16QAM (1),
scheme DL PDSCH 64QAM (2),
256QAM (3)

105 © Nokia 2018 Nokia Internal Use

Deployment Aspects
LTE2666 Massive MIMO

Additional parameters, recommended/required settings

Parameter name Abbreviation Description Range and Step Required/ MOC
recommended
value
Active actTmSwitch Activate or deactivate the dynamic True, false True/false LNCEL_TDD
transmission mode transmission mode switch function
switch
Prohibit timer for prohibitTimerT Defines the period of time between infinite (0), 100ms 1200ms (5) LNCEL_TDD
dynamic TM mSwitch to transmission mode switches for (1), 200ms (2),
mode switch the same UE 400ms (3), 800ms
(4), 1200ms (5),
1600ms (6),
2000ms (7)

106 © Nokia 2018 Nokia Internal Use

Deployment Aspects
NEW LTERLCR-27155 (TD-LTE19) based parameters, recommended/required settings

Parameter name Abbreviation Description Range and Step Required/ MOC

recommended
value
The maximum Enables to set the maximum allowed
allowed value of value for beamforming gain for
downlink downlink. Can be used to mitigate 1,…,12 LNCEL_TDD
dlMaxBfGain 4.0
beamforming gain gain of UE beam because it is Step 1 (mMimoParaSet)
for TDD mMIMO evaluated too optimistic in some
scenarios
The coefficient for restriction of
beamforming gain for downlink is in
The coefficient for order to balance between performance
restriction of and robustness. It is configured
LNCEL_TDD
downlink together with dlMaxBfGain. The 0.5,...,10
dlBfGainCoeff 4.0 (mMimoParaSet)
beamforming gain beamforming gain of UE beam shall Step 0.5
for TDD mMIMO be restricted via maximum allowed
value and coefficient because it is
evaluated too optimistic in some
scenario.

107 © Nokia 2018 Nokia Internal Use

Deployment Aspects
NEW LTERLCR-27155 (TD-LTE19) based parameters, recommended/required settings

Parameter name Abbreviation Description Range and Step Required/ MOC

recommended
value

delayUseBfWeight 0,...,2000ms 500

Extended timer to Timer The timer to delay to use service Step 1 ms
delay to use beamforming weight (milli-scecond) LNCEL_TDD
beamforming Subject calculated from SRS is to avoid Subject Subject (mMimoParaSet)
weight activation to change by performance loss to change by to change by
LTERLCR-30540 LTERLCR-30540 LTERLCR-30540
and and and
LTERLCR-30353 LTERLCR-30353 LTERLCR-30353

The threshold of beamforming gain

The threshold of (linear scale) for downlink. The
0,...,40
beamforming gain BfGainThd beamforming weight should not be 3 LNCEL_TDD
Step 1
for TDD mMIMO applied when the beamforming gain is
low than the threshold

108 © Nokia 2018 Nokia Internal Use

Deployment Aspects
NEW LTERLCR-27155 (TD-LTE19) based parameters, recommended/required settings

Parameter name Abbreviation Description Range and Step Required/ MOC

recommended
value

The aging
coefficient to
The aging coefficient to calculate 0,...,1
calculate bfWeightAgingCoeff 0.01 LNCEL_TDD
beamforming weight Step 0.01
beamforming
weight

The activation of The activation of mitigating higher

actDlBfUeHighBler 0: disable
mitigating higher DL BLER for certain sorts of UE 0 LNCEL_TDD
Mitigation 1: enable
DL BLER chipset while using beamforming

• bfWeightAgingCoeff and actDlBfUeHighBlerMitigation are valid for both 8T8R and mMIMO while other parameters
introduced by LTERLCR-27155 are valid for mMIMO only
• all new parameters introduced by LTERLCR-27155 are TDD specific

109 © Nokia 2018 Nokia Internal Use

Deployment Aspects
NEW LTERLCR-29317 (TD-LTE19B) based parameters, recommended/required
settings
Parameter name Abbreviation Description Range and Step Required/ MOC
recommended
value

actExtendedDelayT This parameter activates extended

Activates delay
oUseBfWeightTime timer to delay to use beamforming True, False True/False LNCEL_TDD
timer
r weight in TDD Massive MIMO

The parameter specifies the target

Extended timer to
power per PRB per pipe of SRS to
delay to use mMimoParaSet.targ Range n.a. dBm LNCEL_TDD
calculate extended timer to delay to n.a.
beamforming etSrsPower Step 0.1 dBm (mMimoParaSet)
use beamforming weight in TDD
weight activation
Massive MIMO

The parameter specifies the scaling

The threshold of
mMimoParaSet.exte factor of extended timer to delay to use Range 0.1,...,5 LNCEL_TDD
beamforming gain 1
ndedDelayFactor beamforming weight in TDD Massive Step 0.1 (mMimoParaSet)
for TDD mMIMO
MIMO

• improvements introduced by LTERLCR-29317 from TD-LTE19A were postponed to TD-LTE19B, where implementation
of LTERLCR-29317 was executed by LTERLCR-29914
110 © Nokia 2018 Nokia Internal Use
Deployment Aspects
Parameter overloading by LTERLCR-30353 in TD-LTE19 (1/2)

• in TD-LTE19 an overloaded definition of delayUseBfWeightTimer was introduced by LTERLCR-30353

• the change was valid through: TD-LTE19, TD-LTE19A & TD-LTE19B and available ONLY for Sprint U.S. PLMN IDs
• the purpose of new overloaded definition was to:
‑ enable handling of at least discrete control over the HARQ feedback 'ANY' type. This allowed adjustment of the
proportion of control given to this type of feedback in the OLLA control
‑ enable discrete on/off control over forward long term beamforming weights to be conveyed from PCell to Scell. This
allowed for use of UL CA's SCell SRS for beamforming vector generation if there is UL CA's SCell SRS - if enabled (else
no use of UL CA's SCell SRS for beamforming vector generation - if disabled)

• initially delayUseBfWeightTimer was a 10 bit number

• after LTERLCR-30353 number of bits that were dedicated to report delayUseBfWeightTimer only was decreased to 4 bits
(details on the next slide) – therefore step was changed to 200ms
• remaining 6 bits were used to report several different R&D parameters (details on the next slide)
• available ONLY for Sprint U.S. PLMN IDs (TDD only)

111 © Nokia 2018

Deployment Aspects
Parameter overloading by LTERLCR-30353 in TD-LTE19 (2/2)
• available ONLY for Sprint U.S. PLMN IDs

Bit 9 8 7 6 5 4 3 2 1 0

Parameter delayUseBfWeightTimer TRdOllaForANY EnableScellSrs DiffCwForTM8

Controls the forwarding of long

Controls the downgrade step of Controls the alignment of TM8
term weights from Pcell to Scell.
PDSCH OLLA for feedback type with other Tx Modes for deltaCQI
Controls delayBfWeightTimer If enabled then use UL CA's Scell
ANY. 0 means rrmDeltaCqi not handling. If enabled then TM8
[bits 6-9] Range 2^4 = 16 steps SRS for bfWeight generation if
affected by ANY. 10 means maintain rrmdeltaCqi for each
16 steps x [200ms] = [0..3000ms] there is UL CA's Scell SRS. If
100% downgrade step of NACK codeword independently. If
disabled then UL CA's Scell SRS
is used for ANY. Use values disabled, align TM8 with other
e.g. 2000ms = b0101 is not used and UL CA's SCELL
[0..10]. Example shown = b0011 TM which maintain same
will use the one forwarded from
= 3 (30%) rrmDeltaCqi for all codewords
PCELL

Description
Bits reported as part of delayUseBfWeightTimer
delayUseBfWeightTimer x x x x but not used for delayUseBfWeightTimer (overloaded meaning)

OFF disable 0 disable 0

ON enable 1 enable 1

112 © Nokia 2018

Deployment Aspects
Parameter overloading by LTERLCR-30353 and change by LTERLCR-30540

• in TD-LTE19 an overloaded definition of delayUseBfWeightTimer was introduced by LTERLCR-30353

• the change was valid through: TD-LTE19, TD-LTE19A & TD-LTE19B and available ONLY for Sprint U.S. PLMN IDs
• in TD-LTE20A/SRAN20A delayUseBfWeightTimer is set back by LTERLCR-30540 to the initial definition introduced
prior to LTERLCR-30353
• that means that overloaded meaning of delayUseBfWeightTimer has been withdrawn
• in parallel to that, a new OAM parameter TDD_LNCELL.mMimoParaSet.actDualOllaForTM8 is introduced

• in LTERLCR-30540:
‑ Bit 0 value (DiffCwForTM8) of delayUseBfWeight following LTERLCR-30353 meaning is translated to
actDualOllaForTM8
‑ delayUseBfWeightTimer range changes from “0-3000 ms step 200” to “0-3000 ms step 1”
‑ delayUseBfWeightTimer default value changes from 500 to 2000
‑ migrates delayUseBfWeightTimer Bits 6-9 from TD-LTE19B (LTERLCR-30353) meaning to TD-LTE20A (
LTERLCR-30540) meaning

113 © Nokia 2018

Deployment Aspects
NEW LTERLCR-30540 (SRAN20A) based parameters, recommended/required settings

Parameter name Abbreviation Description Range and Step Required/ MOC

recommended
value

Value Name
This parameter configures 0 Single OLLA for
the codeword TM8
Activate Dual
actDualOllaForTM8 methodology to be 1 Dual OLLA for 1 LNCEL_TDD
OLLA for TM8 TM8
applied for dual layer
2 Auto configure
beamforming TM8 OLLA for TM8

114 © Nokia 2018 Nokia Internal Use

 <feature:LTE4566>

Deployment Aspects
LTE4566 TDD Massive MIMO 10MHz Support

LTE4566

115 © Nokia 2018 Nokia Internal Use

Deployment Aspects
LTE4566 Feature activation/deactivation

LTE4566 TDD massive MIMO 10MHz support is activated in the same way as LTE2666. The main and only difference is the cell
bandwidth which in the case of LTE4566 needs to be set to 10MHz.

10 MHz

chBw parameter
set to ’10MHz’

116 © Nokia 2018 Nokia Internal Use

Deployment Aspects
LTE4566 Feature activation/deactivation

chBw flag indicates

channel bandwidth of
10MHz

10 MHz

117 © Nokia 2018 Nokia Internal Use

Deployment Aspects
LTE4566 TDD Massive MIMO 10MHz support

Additional parameters, recommended/required settings

Parameter name Abbreviation Description Range and Step Required/ MOC
recommended
value
Channel chBw Channel Bandwidth defines the 10 MHz (100), 15 10MHz (100) LNCEL_TDD
bandwidth TDD Downlink and Uplink bandwidth MHz (150), 20
for the eNode-B transmission. MHz (200)

chBw parameter
set to ’10MHz’

118 © Nokia 2018 Nokia Internal Use

 <feature:LTE5671>

Deployment Aspects
LTE5671 15MHz carrier support for CPRI based TDD massive MIMO

LTE5671

119 © Nokia 2018 Nokia Internal Use

Deployment Aspects
LTE5671 Feature activation/deactivation

LTE5671 LTE5671 15MHz carrier support for CPRI based TDD massive MIMO is activated in the same way as LTE2666.
The main and only difference is the cell bandwidth which in the case of LTE5671 needs to be set to 15MHz.

15 MHz

chBw parameter
set to ’15MHz’

120 © Nokia 2018 Nokia Internal Use

Deployment Aspects
LTE5671 Feature activation/deactivation

chBw flag indicates

channel bandwidth of
15MHz

15 MHz

121 © Nokia 2018 Nokia Internal Use

Deployment Aspects
LTE5671 Feature activation/deactivation

Additional parameters, recommended/required settings

Parameter name Abbreviation Description Range and Step Required/ MOC
recommended
value
Channel chBw Channel Bandwidth defines the 10 MHz (100), 15 15MHz (150) LNCEL_TDD
bandwidth TDD Downlink and Uplink bandwidth MHz (150), 20
for the eNode-B transmission. MHz (200)

chBw parameter
set to ’15MHz’

122 © Nokia 2018 Nokia Internal Use

Deployment Aspects

Alarms
Faults
&
Malfunctions
Management

123 © Nokia 2018 Nokia Internal Use

Deployment Aspects Fault ID Fault ID Name

LTE2666 NEW Faults (1/2) 1938 EFaultId_FrPipeOverheat

LTE4655 modifies the working flow of fault 1938. Alarm 7653 is no

• Fault Name: Pipe dangerously overheating longer raised for only one faulty TRx board (pipe). Further
modifications are introduced in CNI-54058 (from SRAN21A).
• Meaning of the Fault:
− the validated temperature of any TRx board or FPGA sensor in the RF module is greater than or equal to the pre-defined value
in the unit property file
• Reported Alarm Name: depends on FMCADM:actCategoryAlarms
Reported alarm
FMCADM:
actCategoryAlarms
Alarm ID Alarm Name Comment

true 7115 BASE STATION INFORMATION when fault does not affect basic services of the base station

true 7116 BASE STATION SERVICE PROBLEM when fault affects basic services of the base station

false 7652 BASE STATION NOTIFICATION uncommissioned source

the cell cannot operate because of not enough available and needed
false 7653 CELL FAULTY
resources: Tx or Rx

the cell can still operate because it still has enough available and needed
false 7654 CELL OPERATION DEGRADED
resources: both Tx and Rx

124 © Nokia 2018

Deployment Aspects Fault ID Fault ID Name

LTE2666 NEW Faults (2/2) 1938 EFaultId_FrPipeOverheat

• Fault Name: Pipe dangerously overheating

• Meaning of the Fault:
− unit is set to degraded state (when any TX/RX resources are available on alarming FRM) if any TRX board or FPGA sensor
temp is greater than or equal to the pre-defined value in the unit property file
− carriers on the affected pipe are deactivated (and FR state set Out of order, when no RX/TX resources are available on
alarming FRM) when dangerously high temperature occurs for longer than a pre-defined HW specific value for reasonably
long filtering time
− Note: alarm is always raised for predefined 32 pipes no matter which TRX board or FPGA sensor measure temperature is
greater than or equal to the pre-defined value in the unit property file
• Fault Clearance Conditions:
− check if the ambient temperature or environmental conditions are within the design limits of the radio module
− check if the air flow is not blocked by some objects. Ensure the minimum thermal clearances are followed
− check if excessive sunlight is causing an overheat. Install sunshield and follow the mounting instructions and
recommendations

125 © Nokia 2018

Deployment Aspects Fault ID Fault ID Name

Reused Fault 6051 (1/3) 6051 EFaultId_PhyRxBfCalibrationDetectContinuousExceptionAl

Redefined by introduction of the LTE5141 feature in the LTE19B release!

• Fault Name: Beamforming calibration failure in RF data path due to critical fault
• Meaning of the Fault:
− while beamforming calibration measurement detects specific pattern related to continuous failure in transmission path (a
continuous failure due to abnormal performance in transmission path). The failure has impact on beamforming calibration
operation
LTE5141 modifies the working flow of fault 6051. It
− the cell is kept as enabled i.e. LNCEL:operationalState is ‘enabled’ is no longer enabled by default for
the LTE2666 feature.
• Reported Alarm Name: depends on FMCADM:actCategoryAlarms
• Fault Clearance Conditions:
− while beamforming calibration measurement detects disappearance due to NO abnormal performance in transmission path
during beamforming operation

Reported alarm
FMCADM:
actCategoryAlarms
Alarm ID Alarm Name

true 7114 CELL SERVICE PROBLEM

false 7654 CELL OPERATION DEGRADED

126 © Nokia 2018
Deployment Aspects Fault ID Fault ID Name

Reused Fault 6051 (2/3) 6051 EFaultId_PhyRxBfCalibrationDetectContinuousExceptionAl

Redefined by introduction of the LTE5141 feature in the LTE19B release!

• Fault Name: Beamforming calibration failure in RF data path due to critical fault
• Meaning of the Fault:
− the fault indicate that there are more than 4 antenna paths (64TRx) or 3 antenna path(32TRx) being detected as path failure or
reference antenna is detected as path failure by BBU
− the path failure means that there are continuous exception on SINR and/or InitPhase and/or TimeOffset for one antenna path,
the detection time period is hardcoded as 10 min, when exception count ratio in one period is bigger than one threshold, it
will be taken as path failure, the threshold can be changed by R&D parameter and set as 100% by default.
• Fault Clearance Conditions:
− in one fault detection period (10 min), if there are no more than 4 antenna paths (64TRx) or 3 antenna paths (32TRx) being
detected as path failure and reference antenna path is not detected as path failure for Tx and Rx direction, the fault recovery
will be triggered

• LTE5141 removes fault 6052 (the fault was initially introduced by LTE2666)

127 © Nokia 2018

Deployment Aspects Fault ID Fault ID Name

Reused Fault 6051 (3/3) 6051 EFaultId_PhyRxBfCalibrationDetectContinuousExceptionAl

Redefined by introduction of the LTE5141 feature in the LTE19B release!

• the ULPHY will save the failed channel information

rma tion
• the following table defines the thresholds based on the engineering experience ictly in ternal info
str
TxC RxC
R&D
parameter
Bandwidth 20MHz 10MHz 20MHz 10MHz

Ep/No threshold (mMIMO only) 25 20 30 26 YES

TO jitter (max. 5°) 0.77ns 1.54ns 0.77ns 1.54ns YES

Phase jitter 10° 10° 10° 10° YES

AmpRatio 0.707 0.707 0.707 0.707 YES

DeltaOffset* +4.5 +7 -4.5 -1.5 YES

* - due to the offset between Ep/No and SNR, Ep/No has to be corrected for the final SNR:

OrigCaliSignalLen
SNR [dB] = EpN0 [dB] + L2 [dB] + DeltaOffset
(ZcSeqLen)2
128 © Nokia 2018
Deployment Aspects Fault ID Fault ID Name

Reused Fault 4254 (1/2) 4254 EFaultId_BfCellParaMismatchAl

• Fault Name: Beamforming cell parameter mismatch

• Meaning of the Fault:
− during BTS startup or BTS recomissioning, the BTSOAM has detected that there are wrong combination of values for the
beam-forming cell parameters ‘tddSpecSubfConf’, ‘rxCalibrationConfiguration’, ‘actReduceWimaxInterference’ for the
used beamforming radio module
− the cell cannot be set up and remains faulty (Out of order)

• Reported Alarm Name: depends on FMCADM:actCategoryAlarms

Reported alarm
FMCADM:
actCategoryAlarms
Alarm ID Alarm Name

true 7112 BASE STATION CONFIGURATION PROBLEM

false 7653 CELL FAULTY

129 © Nokia 2018
Deployment Aspects Fault ID Fault ID Name

Reused Fault 4254 (2/2) 4254 EFaultId_BfCellParaMismatchAl

• Fault Name: Beamforming cell parameter mismatch

• Fault Clearance Conditions:
− check values of the parameters ‘tddSpecSubfConf’, ‘rxCalibrationConfiguration’, ‘actReduceWimaxInterference’ and the
used beam-forming radio module type.
− commission different combination for the mentioned values, or change to a different beam-forming radio module type for the
configuration

130 © Nokia 2018

Deployment Aspects Fault ID Fault ID Name

Reused Fault 6253 (1/2) 6253 EFaultId_CellSetupFailed

• Fault Name: Cell configuration data distribution failed

• Meaning of the Fault:
− a BTS raises this fault if it experiences a problem in the internal configuration data distribution (cell setup) to the C-Plane and
U-Plane SW components. The root cause of the fault might be an incorrect cell configuration in the site configuration file
(scf).the cell cannot be set up and remains faulty
− the cell cannot be set up and remains faulty (Out of order)

• Reported Alarm Name: depends on FMCADM:actCategoryAlarms

Reported alarm
FMCADM:
actCategoryAlarms
Alarm ID Alarm Name

true 7114 CELL SERVICE PROBLEM

false 7653 CELL FAULTY

131 © Nokia 2018
Deployment Aspects Fault ID Fault ID Name

Reused Fault 6253 (2/2) 6253 EFaultId_CellSetupFailed

• Fault Name: Cell configuration data distribution failed

• Fault Clearance Conditions:
− check and update the configuration parameters related to the cells.
− load the correct commissioning file to the BTS.
− block and unblock the BTS.

132 © Nokia 2018

Deployment Aspects Fault ID Fault ID Name

Reused Fault 1900 (1/2) 1900 EFaultId_FrConfiguringFailed

• Fault Name: Cell configuration data distribution failed

• Meaning of the Fault:
− RFSW rejected carrier or antenna calibration parameters. The cell remains faulty (Out of order)
• Reported Alarm Name: depends on FMCADM:actCategoryAlarms
Reported alarm
FMCADM:
actCategoryAlarms Alarm ID Alarm Name Comment

true 7115 BASE STATION INFORMATION when fault does not affect basic services of the base station

true 7116 BASE STATION SERVICE PROBLEM when fault affects basic services of the base station

BASE STATION/UNIT
true 7101 AUTONOMOUS RESET when autonomous recovery reset is being performed due to the fault
NOTIFICATION

false 7652 BASE STATION NOTIFICATION uncommissioned source

the cell cannot operate because of not enough available and needed resources: Tx
false 7653 CELL FAULTY
or Rx

the cell can still operate because it still has enough available and needed
false 7654 CELL OPERATION DEGRADED
resources: both Tx and Rx

133 ©false
Nokia 2018 7655 CELL NOTIFICATION the cell is not impacted
Deployment Aspects Fault ID Fault ID Name

Reused Fault 1900 (2/2) 1900 EFaultId_FrConfiguringFailed

• Fault Name: Cell configuration data distribution failed

• Fault appears as an exception during processing:
− BTS calculates antenna calibration parameters by selection of one LNBTS_TDD:mMimoCalibrationParameters analysing
RRU type (Radio Resource Unit), SSP (special subframe configuration, LNCEL_TDD:tddSpecSubfConf),
LNCEL_TDD:rxCalibrationConfiguration and LNCEL_TDD:actReduceWimaxInterference, and prepares data to be send
to RFSW in LteTddCarrier and LteTddCalibration MOs
− BTS calculates sector beamforming weights for each channel basing on defined LNCEL_TDD:mMimoSectorBFProfName
for mMIMO cell
− BTS sends antenna carriers’ and calibration’s information to RFSW
− BTS proceeds with mMIMO cell setup applying calculated providing among others sector beamforming weights and
calibration compensation parameters (received from RFSW) to RROM
− BTS proceeds with antenna carrier’s activation on mMIMO radio
− as a result: mMIMO cell is enabled meaning that operationalStatus of LNCELL is ‘enabled’
− in case of any exception fault 1900:EFaultId_FrConfiguringFailed is raised

134 © Nokia 2018

 <feature:LTE5671>

Deployment Aspects
TDD mMIMO

Feature impact
monitoring

135 © Nokia 2018 Nokia Internal Use

Deployment Aspects
Where to deploy the feature?
To monitor number of active
• please keep in mind that LTE2666/LTE4566 will usually not be deployed “as is” but also with UEs, LTE_1734a Effective
combination of other features, especially LTE3463 DL MU-MIMO for Massive MIMO. Therefore connected users ratio
feature potential of increasing the capacity should be considered in the first place. can be used

• feature should be activated in clusters with high number of UEs and high average DL
throughput. To monitor average DL
throughput, LTE_5292d
• one of the use cases of the feature is providing indoor coverage for the high-rise buildings. E-UTRAN average PDCP
Layer Active Cell Throughput
Other factors to consider: DL can be used
• UE support
- Feature should be deployed in clusters with high penetration of 3GPP Rel.9 compliant UEs supporting TM8 To monitor penetration of
• Low to moderate mobility 3GPP Rel.9 compliant UEs ,
LTE_6093a UEs Supporting
- Feature does not support High Speed receiver, moreover simulations predict much more significant gains for stationary UEs Rel 9 Access Stratum Release
• Subframe configuration and cell BW Distribution Ratio can be used

- LTE2666/LTE4566 supports only TDD 7/2 configuration and 20MHz bandwidth

Please refer to the Interdependencies section for other limiting features.

136 © Nokia 2018 Nokia Internal Use

Deployment Aspects
How to verify if the feature works

LTE2666/LTE4566 does not introduce any new counters or KPIs. Feature activation should bring benefit in
terms of the increased DL and UL cell throughput.

KPI ID KPI Name Description / Role in evaluating LTE2666/LTE4566

LTE_5292d E-UTRAN average PDCP Layer This KPI shows the active average PDCP layer throughput per cell in a downlink
Active Cell Throughput DL direction.
LTE_5289d E-UTRAN average PDCP Layer This KPI shows the active average PDCP layer throughput per cell in an uplink
Active Cell Throughput UL direction.

Drive test, or stationary test before and after feature activation can also be used to prove that the feature is
working.

137 © Nokia 2018 Nokia Internal Use

LTE2666 Massive MIMO, LTE4566 TDD Massive MIMO 10MHz support

Dimensioning
Aspects
Table of contents

<chapter:dimensioning>

138 © Nokia 2018 Nokia Internal Use

Dimensioning Aspects
LTE2666 Massive MIMO, LTE4566 TDD Massive MIMO 10MHz support

• Massive MIMO functionality is not available in RAN Configure Dual Stream BF (TM8) feature
Dim tool, however it can be easily modeled using certain
workaround:
1. Activate Dual Stream BF (TM8) feature on Features
configuration tab and make sure corresponding Antenna
configuration and Tx/Rx Algorithm at eNB on Coverage
calculation tab are set:
• 8Tx-8Rx SS-HBF in DL
• 1Tx-8Rx in UL
2. Tune DL Antenna gain [dB] parameter to 15.0 dB to
compensate for performance of 64Tx-64Rx mMIMO antenna
and channel model difference. Tune DL Antenna gain to model 64Tx-64Rx antenna

3. Perform all calculations as usual tuning other parameters like

output power cell edge user throughput, propagation
environment specifics, etc. according to the scenario
requirements

139 © Nokia 2018 Nokia Internal Use

Dimensioning Aspects
LTE2666 Massive MIMO, LTE4566 TDD Massive MIMO 10MHz support

4. Provide additional gain introduced by mMIMO solution using Model mMIMO impact using additional gain values
Additional gains [dB] parameter on Coverage calculation tab
• 8.44 dB in DL
• 8.30 dB in UL
5. Finally, calculated cell range will reflect usage of mMIMO solution

• introduction of the mMIMO functionality significantly improves network coverage in both DL and UL
direction

mMIMO Legacy 8Tx-8Rx

Visible coverage improvement in

both DL and UL

140 © Nokia 2018 Nokia Internal Use

Dimensioning Aspects
LTE2666 Massive MIMO

• impact of LTE2666 massive MIMO solution on the

average cell capacity calculations can be modeled
using Additional capacity gain [%] parameter on Model mMIMO impact using additional gain values
Air Interface Capacity tab
- There should be provided gain value corresponding to
the required mMIMO deployment:

mMIMO mMIMO
20MHz
Single User (SU) Multi User (MU)

Downlink 59% 125%

Uplink 31% 99%

LTE2666
141 © Nokia 2018 Nokia Internal Use
Dimensioning Aspects
LTE4566 TDD Massive MIMO 10MHz support

• impact of LTE4566 Massive MIMO 10MHz

support solution on the average cell capacity
calculations can be modeled using Additional Model mMIMO impact using additional gain values
capacity gain [%] parameter on Air Interface
Capacity tab
- There should be provided gain value corresponding to the
required mMIMO deployment:

mMIMO mMIMO
10MHz 30% 15%
Single User (SU) Multi User (MU)

Downlink 30% 63%

Uplink 15% 50%

in opposition to LTE2666, LTE4566 is supposed to cover

MU-MIMO features as well (already discussed)
LTE4566
142 © Nokia 2018 Nokia Internal Use
Dimensioning Aspects
LTE5671 15MHz carrier support for CPRI based TDD massive MIMO

• impact of LTE5671 LTE5671 15MHz carrier

support for CPRI based TDD massive MIMO
solution on the average cell capacity calculations Model mMIMO impact using additional gain values
can be modeled using Additional capacity gain
[%] parameter on Air Interface Capacity tab
- There should be provided gain value corresponding to the
required mMIMO deployment:

mMIMO mMIMO
15MHz 44% 23%
Single User (SU) Multi User (MU)

Downlink 44% 94%

Uplink 23% 75%

LTE5671 is supposed to cover MU-MIMO features as

well (already discussed)
LTE5671
143 © Nokia 2018 Nokia Internal Use
LTE2666 Massive MIMO, LTE4566 TDD Massive MIMO 10MHz support

Performance
Aspects
Table of contents

<chapter:performance_aspects>

144 © Nokia 2018 Nokia Internal Use

Performance Aspects
Feature impact

• LTE2666 does not introduce any new performance measurement counters nor KPIs. Feature
impact can be measured using the existing counters (shown on next slides)

• LTE4566 does not introduce any new performance measurement counters nor KPIs. Feature
impact can be measured using the existing counters (shown on next slides)

• LTE5671 does not introduce any new performance measurement counters nor KPIs. Feature
impact can be measured using the existing counters (shown on next slides)

145 © Nokia 2018 Nokia Internal Use

Performance Aspects
Feature impact
Feature impact How to measure?
Downlink throughput KPIs:
Downlink cell throughput should increase for UEs scheduled - DL RLC PDU volume transmitted (LTE_284a)
with TM8. Therefore it is important to activate feature with - Average PDCP Layer Active Cell Throughput DL (LTE_5292b)
adequate Rel.9 compliant UE penetration
Counters:
- RLC_PDU_VOL_TRANSMITTED (M8012C18)
- PDCP_DATA_RATE_MEAN_DL (M8012C26)

MCS distribution Counters:

DL MCS will increase due to improved DL conditions - PDSCH_TRANS_USING_MCS0 (M8001C45)…
- PDSCH_TRANS_USING_MCS28 (M8001C73)

146 © Nokia 2018 Nokia Internal Use

References and acknowledgments

References
Massive MIMO system level simulations, https://sharenet-ims.int.net.nokia.com/Open/546444656

LTE2666 CFAM

LTE4566 CFAM

LTE5671 CFAM

147 © 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

148 © Nokia 2018 Nokia Internal Use