No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.

Single RAN System, Rel. SRAN 21A,
Operating Documentation, Issue
06

SRAN 21A Changes

DN09158507
Issue 01D
Approved on 2021-12-17

© 2022 Nokia. Nokia Condential Information

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Nokia is committed to diversity and inclusion. We are continuously reviewing our customer
documentation and consulting with standards bodies to ensure that terminology is inclusive
and aligned with the industry. Our future customer documentation will be updated
accordingly.

This document includes Nokia proprietary and condential information, which may not be
distributed or disclosed to any third parties without the prior written consent of Nokia. This
document is intended for use by Nokia’s customers (“You”/”Your”) in connection with a
product purchased or licensed from any company within Nokia Group of Companies. Use this
document as agreed. You agree to notify Nokia of any errors you may nd in this document;
however, should you elect to use this document for any purpose(s) for which it is not
intended, You understand and warrant that any determinations You may make or actions
You may take will be based upon Your independent judgment and analysis of the content of
this document.

Nokia reserves the right to make changes to this document without notice. At all times, the
controlling version is the one available on Nokia’s site.

No part of this document may be modied.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES,
INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR
CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT,
REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE
FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF
ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.

Copyright and trademark: Nokia is a registered trademark of Nokia Corporation. Other

product names mentioned in this document may be trademarks of their respective owners.

© 2022 Nokia.

2 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Table of Contents

Summary of changes .................................................................................................................. 12

1 Changes introduced with new software release .................................................................... 13

1.1 Changes introduced with SRAN 21A release ............................................................... 13
1.1.1 LTE5567 changes to the system ....................................................................... 13
1.1.2 CB005932 changes to the SRAN 21A system ................................................. 14
1.1.3 CB006028 changes to the system .................................................................... 14
1.1.4 CB007258 changes to the SRAN 21A system ................................................. 15
1.1.5 Cell resource groups changes to the system in SRAN21A ............................. 16
1.2 Changes introduced with SRAN 20C release ............................................................... 17
1.2.1 LTE5226 changes to the SRAN20C system ..................................................... 17
1.2.2 TDD massive MIMO changes to the system in SRAN20C ............................... 17
1.3 Changes introduced with SRAN 20B release ............................................................... 18
1.3.1 LTE1320 changes to the system ....................................................................... 18
1.3.2 LTE5640 changes to the SRAN20B system ..................................................... 18
1.3.3 SR002488 changes to the system .................................................................... 18
1.3.4 SR002493 changes to the system .................................................................... 19
1.3.5 TDD massive MIMO changes to the system in SRAN20B ............................... 19
1.3.6 TDD remote interference changes to the system .......................................... 20
1.3.6.1 LTE5602 changes to the system in release SRAN 20B ....................... 20
1.3.7 Changes to the system brought by enhancements of actual EIRP control for
non-beamforming cells in SRAN 20B ................................................................... 21
1.4 Changes introduced with SRAN 20A release ............................................................... 21
1.4.1 TDD Massive MIMO changes to the system in SRAN20A ............................... 21
1.4.2 Plug and Play changes to the system ............................................................... 21
1.4.3 SR001865 changes to the system .................................................................... 22
1.4.4 SR002817 changes to the system .................................................................... 22
1.4.5 LTE5306 changes to the system ....................................................................... 23
1.4.6 LTE5620 changes to the system ....................................................................... 26
1.5 Changes introduced with LTE 19B release .................................................................. 27
1.5.1 LTE1118 changes to the system ....................................................................... 27
1.5.2 LTE2971 changes to the system ....................................................................... 27
1.5.3 LTE4549 changes to the LTE19B system ........................................................ 27
1.5.4 LTE5266 changes to the system ....................................................................... 27
1.5.5 LTE5510 changes to the LTE19B system ........................................................ 28
1.5.6 LTE5558 changes to the LTE19B system ........................................................ 28
1.5.7 LTE-M mobility changes to the system in LTE19B .......................................... 28
1.6 Changes introduced with LTE19A release ................................................................... 29
1.6.1 LTE652 changes to the system ......................................................................... 30
1.6.2 LTE1709 changes to the system ....................................................................... 30
1.6.3 LTE4034/SR001670 changes to the system ................................................... 30
1.6.4 LTE4531 changes to the LTE19A system ........................................................ 31

Issue 01D. © 2022 Nokia. Nokia Confidential Information 3

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
1.6.5 LTE4701 changes to the system ....................................................................... 31
1.6.6 LTE4875 changes to the system ....................................................................... 31
1.6.7 LTE5063 changes to the system ....................................................................... 32
1.6.8 LTE5135 changes to the system ....................................................................... 32
1.6.9 LTE5335 changes to the LTE19A system ........................................................ 33
1.7 Changes introduced with LTE 19 release .................................................................... 34
1.7.1 LTE3435 changes to the system ....................................................................... 34
1.7.2 LTE4575 changes to the LTE19 system ........................................................... 35
1.7.3 LTE4788 changes to the system ....................................................................... 36
1.7.4 LTE4504 changes to the system ....................................................................... 36
1.7.5 LTE5268 changes to the system ....................................................................... 37
1.7.6 LTE4088 changes to the LTE19 system ........................................................... 37
1.8 Changes introduced with LTE 18A release .................................................................. 38
1.8.1 LTE3571 changes to the system ....................................................................... 38
1.8.2 LTE2774 changes to the system ....................................................................... 38
1.8.3 LTE2617 changes to the system ....................................................................... 39
1.8.4 LTE4259 changes to the system ....................................................................... 40
1.8.5 LTE2179 changes to the system ....................................................................... 40
1.8.6 LTE4096 changes to the system ....................................................................... 41
1.8.7 LTE4117 changes to the system ....................................................................... 42
1.8.8 LTE4739 changes to the system ....................................................................... 42
1.8.9 LTE3974 changes to the system ....................................................................... 43
1.8.10 SR001933LTE3796 changes to the system .................................................. 43
1.8.11 LTE4066 changes to the system ..................................................................... 44
1.9 Changes introduced with LTE 18SP release ................................................................ 45
1.9.1 LTE3687 changes to the system ....................................................................... 45
1.9.2 LTE3870 changes to the system ....................................................................... 46
1.9.3 LTE4494 changes to the system ....................................................................... 46
1.9.4 LTE2647/SR001070 changes to the system ................................................... 47
1.9.5 New parameter for Coordinated Multipoint and CRAN features .................. 48
1.10 Changes introduced with LTE 18 release .................................................................. 49
1.10.1 LTE2839 changes to the system ..................................................................... 49
1.10.2 LTE2927 changes to the system ..................................................................... 50
1.10.3 LTE3225 changes to the system ..................................................................... 53
1.10.4 LTE3590 changes to the system ..................................................................... 53
1.10.5 UE selection algorithms modified by LTE3757 ............................................. 53
1.10.6 Preemption candidate selection algorithm modified by LTE3758 ............ 55
1.10.7 LTE3866 changes to the system ..................................................................... 56
1.10.8 New Model Object Chart (MOC) introduced by LTE4154 ............................ 56
1.10.9 LTE4222 changes to the system ..................................................................... 56
1.10.10 LTE4409 changes to the system .................................................................. 57
1.10.11 LTE3865 changes to the system .................................................................. 57
1.10.11.1 Counters improvement with the LTE3865 ...................................... 58

4 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
2 Algorithm changes ...................................................................................................................... 67
2.1 SRAN 21A algorithm changes ........................................................................................ 67
2.1.1 LTE UL 256QAM configuration for UEs with UL category 22 and above ..... 67
2.1.2 Updating radio quality counters (SINR/RSSI) when unreliable DTX
transmission from UEs occurs ............................................................................... 70
2.2 SRAN 20C algorithm changes ........................................................................................ 72
2.2.1 Improvement in UL SCell deconfiguration algorithm ..................................... 72
2.3 SRAN 20B algorithm changes ........................................................................................ 73
2.3.1 SCell channel quality estimation for UEs configured with LTE 256QAM in
downlink .................................................................................................................... 73
2.3.2 DSS dynamic sharing ratio changes .................................................................. 74
2.3.3 Improvements in counter aggregation algorithm when Real-Time
Performance Monitoring (RT PM) framework is activated ................................. 76
2.3.4 The correction of relative instantaneous channel quality calculation ......... 77
2.4 SRAN 20A algorithm changes ........................................................................................ 78
2.4.1 Calculation of load, Composite Available Capacity (CAC), and Normalized Load
Compare Value (NLCV) ............................................................................................ 78
2.4.2 Possible counter value changes for IP throughput and corresponding
time/net time .......................................................................................................... 79
2.4.3 Improper handling of the ring buffer wraparound ......................................... 81
2.4.4 HARQ release with default previous HARQ state in AM mode ...................... 84
2.4.5 Update of legacy fixed FDD UL CoMP solution ................................................ 85
2.5 LTE 19B algorithm changes ........................................................................................... 85
2.5.1 Potential cell load increase with the LTE5731: TCP Service Differentiation
feature activated .................................................................................................... 86
2.5.2 Prioritization of the optional power group over the mandatory power group
for baseband pool allocation ................................................................................. 86
2.5.3 Introduction of Resource Allocation Type (RAT) 1 .......................................... 87
2.5.4 Enabling Cyclic PUCCH Allocation algorithm will consider the setting of
maxNumCaConfUe3c or maxNum2CCUeWithPF3 ............................................. 88
2.6 LTE19A algorithm changes ............................................................................................ 89
2.6.1 LTE19A common algorithm changes ................................................................ 89
2.6.1.1 Improved SCell handling when moving from bad to good channel
conditions ......................................................................................................... 89
2.6.1.2 QCI-specific UL power control ................................................................ 90
2.6.1.3 Improved UL grant efficiency for TCP boosting ................................... 92
2.6.2 LTE19A FDD algorithm changes ........................................................................ 93
2.6.2.1 Correction of PUCCH RSSI and PUCCH SINR KPIs in inter-site CA
............................................................................................................................ 93
2.6.2.2 Modification of conditions triggering the step-wise secondary cell
(SCell) configuration ....................................................................................... 94
2.6.2.3 RIP interference measurement correction ........................................... 95
2.6.2.4 Change in handling the Radio Network Layer Cause: "Release due to E-

Issue 01D. © 2022 Nokia. Nokia Confidential Information 5

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
UTRAN Generated Reason" ............................................................................ 95
2.6.3 LTE19A TDD algorithm changes ........................................................................ 96
2.6.3.1 TDD mMIMO downlink PRB usage-based multiple users paring ........ 96
2.6.3.2 PDCCH CCE power limiting (TDD) ........................................................... 97
2.7 LTE 19 algorithm changes .............................................................................................. 98
2.7.1 QCI5 and QCI1 scheduling enhancement for CAT-M VoLTE Ues .................. 99
2.7.2 Counters for micro-DTX ................................................................................... 101
2.7.3 Average number of available PRBs when micro DTX extension is activated
.................................................................................................................................. 102
2.7.4 Direct reporting removal .................................................................................. 102
2.7.5 Changes in inter-site carrier aggregation (CA) .............................................. 103
2.7.6 Enhanced flow control ...................................................................................... 104
2.8 LTE 18A algorithm changes ......................................................................................... 106
2.8.1 The number of subframes adaptation for message 2 in DL ....................... 106
2.8.2 Legacy PUCCH region expansion steps calibrated for Cat-M ..................... 107
2.8.3 LTE2664 enhancements of minimal configuration handling ...................... 108
2.8.4 Support Cat-M CE ModeA Paging Optimization ............................................ 109
2.8.5 SCell activation for 256 QAM-capable UEs .................................................... 110
2.8.6 Dynamic UL resource units selection ............................................................. 113
2.8.7 Radio Link Failure (RLF) indication during the Initial Context Setup Procedure
.................................................................................................................................. 114
2.8.8 The SCell will not be deactivated when the ChannelStatus value equals
'undetected' .......................................................................................................... 114
2.9 LTE 18SP algorithm changes ....................................................................................... 115
2.9.1 Common algorithm changes ............................................................................ 116
2.9.1.1 Downlink cat-4 UEs supported in uplink 64QAM ............................... 116
2.9.1.2 Proactive grants for VoLTE robustness .............................................. 116
2.9.2 FDD-LTE 18SP algorithm changes .................................................................. 117
2.9.2.1 Support of MCS29/30/31 for retransmission ................................... 117
2.9.2.2 Interference Mitigation of the NB-IoT Receiver ................................. 119
2.9.2.3 Automatic calculation of the G-factor ................................................ 120
2.9.2.4 Impact of the Cat-M and eMBMS coexistence ................................... 121
2.9.2.5 Adjustment of the SIB-NB broadcast NRS power value in the 4TX mode
.......................................................................................................................... 122
2.9.3 TD-LTE 18SP algorithm changes ..................................................................... 123
2.9.3.1 Cell resource group support with TDD downlink 3CC carrier
aggregation ................................................................................................... 123
2.9.3.2 Single radio voice call continuity to GSM workaround ...................... 124
2.9.3.3 Extended timer ranges .......................................................................... 125
2.9.3.4 SCell combination selection mechanism by MIMO throughput check
.......................................................................................................................... 125
2.10 LTE 18 algorithm changes ......................................................................................... 126
2.10.1 Common algorithm changes ......................................................................... 126
2.10.1.1 PUCCH format '1bwsc' to use cyclic PUCCH allocation .................. 126

6 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
2.10.1.2 Non-HARQ, MAC-level automatic repeat requests for inter-site carrier
aggregation extension ................................................................................. 127
2.10.2 FDD-LTE 18 algorithm changes .................................................................... 128
2.10.2.1 ACK/NACK DTX detection on PUSCH ................................................ 128
2.10.2.2 SCell activation threshold based on average expected UE throughput
.......................................................................................................................... 129
2.10.2.3 Modified LTE-M scheduling priorities ............................................... 130
2.10.2.4 Increased value range for sFreqPrio ................................................. 131
2.10.2.5 Modified NB-IoT scheduling priorities .............................................. 131
2.10.2.6 Improvement of L2 HARQ ACK based NB-IoT RRC connection release.
.......................................................................................................................... 132
2.10.2.7 Improvement of NB-IoT cell deletion ............................................... 133
2.10.2.8 Subframe adaptation over NPDSCH in a NB-IoT cell ...................... 133
2.10.2.9 No preamble group B for 5MHz system with Cat-M ....................... 134
2.10.2.10 Throughput-check procedure enhancement ................................ 135
2.10.2.10.1 LTE3605 changes to the system ......................................... 136
2.10.2.11 Enhancement of counters related to PDCP SDU .......................... 137
2.10.2.12 Link adaptation for NB-IoT Inband ................................................. 138
2.10.2.13 Lower MCS and PRB allocation is allowed in Cat-M uplink ........... 138
2.10.2.14 Improvement of VoLTE IP scheduled throughput ........................ 139
2.10.2.15 Improvement of the average UL MCS ............................................ 141
2.10.2.16 Source rate based UL grant assignment for VoLTE (or any other
small packet transmission) .......................................................................... 142
2.10.3 TD-LTE 18 algorithm changes ....................................................................... 144
2.10.3.1 PRACH format4 guard window adjustment ..................................... 144

3 Performance changes .............................................................................................................. 145

3.1 SRAN21A performance changes ................................................................................. 145
3.1.1 HRL enforcement also for emergency calls ................................................... 145
3.2 SRAN20C performance changes ................................................................................. 146
3.2.1 TDD massive MIMO performance changes in SRAN20C .............................. 146
3.2.1.1 DL QoE-based scheduling enhancement for low load scenarios in TDD
massive MIMO ................................................................................................ 146
3.2.1.2 Selective HARQ scheduling in subframe 3 or 8 for TDD massive MIMO
.......................................................................................................................... 147
3.2.2 CAS Srel Noise Rise Improvement ................................................................... 148
3.3 SRAN20B performance changes ................................................................................. 149
3.3.1 Active Mode Load Equalization (AMLE) RSRP/RSRQ Source Thresholds .... 149
3.3.2 Update the filtering for the RxAntennaSignalLevelDifferenceTooHigh fault
and alarm ............................................................................................................... 151
3.3.3 TDD massive MIMO performance changes in SRAN20B .............................. 151
3.3.3.1 Configurable TDD mMIMO UE beam pattern ..................................... 151
3.3.3.2 Configurable options for OLLA handling for MIMO mode control and
OLLA initialization during rank switch ........................................................ 154

Issue 01D. © 2022 Nokia. Nokia Confidential Information 7

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
3.3.3.3 Extended BF weight using delay timer based on SRS quality .......... 154
3.3.3.4 Dynamic TDD mMIMO vertical sector beamforming adaptation .... 156
3.3.3.5 TDD massive MIMO MU-MIMO pairing enhancement ....................... 157
3.3.4 FDD massive MIMO performance changes in SRAN20B .............................. 159
3.3.4.1 Skipping periodic PMI reports and polling aperiodic PMI reports for LTE
FDD mMIMO ................................................................................................... 159
3.3.4.2 Support for supplemental downlink carrier for FDD mMIMO .......... 160
3.3.4.3 Support for TM4 in 4x4 mode when TM9 is configured in 8x2 mode
.......................................................................................................................... 160
3.4 SRAN20A performance changes ................................................................................. 161
3.4.1 MCS/PRB selection for poor RF ....................................................................... 161
3.4.2 QCI1, SRB, and power limits for PDCCH ......................................................... 165
3.4.3 CAS Noise Rise Reduction ................................................................................. 168
3.5 LTE19B performance changes .................................................................................... 169
3.5.1 Load Adaptive Uplink PF Scheduling ............................................................... 169
3.5.2 Enhanced CA Band Combination Selection ................................................... 172
3.5.3 Spectrally Efficient Scheduling ........................................................................ 174
3.6 LTE19A performance changes .................................................................................... 178
3.6.1 QCI Specific UL Power Control ......................................................................... 178
3.6.2 SCell configuration for high demand UEs ...................................................... 184
3.6.3 Improved SCell handling when moving from bad to good channel conditions
.................................................................................................................................. 186
3.7 LTE19 performance changes ...................................................................................... 188
3.7.1 UL TCP Power Boost .......................................................................................... 188
3.7.2 PDCCH CQI Shift for 4Tx .................................................................................. 189
3.7.3 Adaptive Vocoder PRB/TBS for TTIB ............................................................... 191
3.7.4 Load Adaptive PF Scheduling ........................................................................... 194
3.7.5 Data Split CA Selection ..................................................................................... 197
3.8 LTE18A performance changes .................................................................................... 199
3.8.1 LTE5731: TCP Service Differentiation ............................................................ 199
3.8.2 Advanced Step-wise SCell Addition for CA: Initial SCellAddition in One Step
.................................................................................................................................. 203
3.8.3 Fast Scheduling Flexible CA .............................................................................. 207
3.8.4 UL Dynamic BLER Adaptation .......................................................................... 207
3.8.5 Prolong Timer Override .................................................................................... 209

8 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
List of Figures
Figure 1 Updated 3GPP table for MCS/TBS index ................................................................ 163
Figure 2 PF scheduling formula ............................................................................................... 170
Figure 3 UL PF scheduling parameters ................................................................................... 171
Figure 4 Example of MCS upgrade (green - MCS increase by 1, orange - MCS increase by 2)
......................................................................................................................................... 176
Figure 5 Power control decision matrix .................................................................................. 179
Figure 6 Updated power control decision matrix ................................................................. 181
Figure 7 Algorithm of SCell addition ....................................................................................... 185
Figure 8 PF scheduling formula ............................................................................................... 194
Figure 9 DL PF scheduling parameters ................................................................................... 196
Figure 10 Algorithm of data flow boosting ............................................................................ 201
Figure 11 Exemplary result of data boosting (number of PRBs allocated vs time, for three
UE) .................................................................................................................................. 201
Figure 12 One-step advanced solution ................................................................................. 205
Figure 13 Buffer-based solution ............................................................................................. 206
Figure 14 PCFICH location in subframe .................................................................................. 209

Issue 01D. © 2022 Nokia. Nokia Confidential Information 9

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
List of Tables
Table 1 Changes in parameters during system upgrade to SRAN 21A ................................ 13
Table 2 Additional PCMD field .................................................................................................... 34
Table 3 List of counters impacted by the LTE4575 related to the SCell in CA .................. 35
Table 4 Parameters modified by the LTE3571 feature ......................................................... 38
Table 5 Parameters modified by the LTE2179 feature ......................................................... 41
Table 6 List of impacted counters and KPIs related to DL and UL IP scheduled throughput
........................................................................................................................................... 59
Table 7 Parameters introduced by HRL enforcement also for emergency calls .............. 146
Table 8 Parameters introduced by CAS Srel Noise Rise Improvement ............................. 149
Table 9 Parameters related to CAS Srel Noise Rise Improvement ..................................... 149
Table 10 Parameters related to the RSRP and RSRQ thresholds ....................................... 151
Table 11 Parameters related to configurable TDD mMIMO UE beam pattern ................. 153
Table 12 Counters related to MCS/PRB selection for poor RF ........................................... 164
Table 13 Key performance indicators related to MCS/PRB selection for poor RF
......................................................................................................................................... 164
Table 14 Parameters introduced by MCS/PRB selection for poor RF ................................ 165
Table 15 Parameters related to MCS/PRB selection for poor RF ....................................... 165
Table 16 Parameters introduced by QCI1, SRB, and power limits for PDCCH ................. 167
Table 17 Counters impacted by CAS Noise Rise Reduction ................................................ 169
Table 18 Parameters introduced by CAS Noise Rise Reduction ......................................... 169
Table 19 KPIs related to Load Adaptive Uplink PF Scheduling ............................................ 171
Table 20 Parameters introduced by Load Adaptive Uplink PF Scheduling ....................... 172
Table 21 KPIs related to Enhanced CA Band Combination Selection ................................ 174
Table 22 Parameters introduced by Enhanced CA Band Combination Selection ............ 174
Table 23 KPIs related to Spectrally Efficient Scheduling ..................................................... 177
Table 24 Parameters introduced by Spectrally Efficient Scheduling ................................. 178
Table 25 Parameters and scenarios for the decision matrix .............................................. 179
Table 26 Scenarios explanation for the decision matrix ..................................................... 180
Table 27 Parameters introduced by QCI Specific UL Power Control ................................. 181
Table 28 Parameters related to QCI Specific UL Power Control ........................................ 183
Table 29 Key performance indicators related to QCI Specific UL Power Control ............ 183
Table 30 Parameters introduced by SCell configuration for high demand UEs ............... 185
Table 31 Parameters related to SCell configuration for high demand UEs ...................... 185
Table 32 Parameters introduced by QCI Specific UL Power Control ................................. 187
Table 33 Counters introduced by UL TCP Power Boost ...................................................... 189
Table 34 Parameters introduced by UL TCP Power Boost .................................................. 189
Table 35 Parameters related to UL TCP Power Boost ......................................................... 189
Table 36 KPIs related to UL TCP Power Boost ...................................................................... 190
Table 37 Parameters introduced by UL TCP Power Boost .................................................. 190
Table 38 Parameters related to UL TCP Power Boost ......................................................... 191

10 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Table 39 Counters related to Adaptive Vocoder PRB/TBS for TTIB .................................. 193
Table 40 KPIs related to Adaptive Vocoder PRB/TBS for TTIB ........................................... 193
Table 41 Parameters introduced by Adaptive Vocoder PRB/TBS for TTIB ....................... 193
Table 42 Parameters related to Adaptive Vocoder PRB/TBS for TTIB .............................. 194
Table 43 KPIs related to Load Adaptive PF Scheduling ....................................................... 196
Table 44 Parameters introduced by Load Adaptive PF Scheduling ................................... 197
Table 45 KPIs related to Data Split CA Selection .................................................................. 199
Table 46 Parameters introduced by Data Split CA Selection ............................................. 199
Table 47 LTE5731 hardware and software requirements ................................................... 200
Table 48 Counters introduced by TCP Service Differentiation .......................................... 202
Table 49 Parameters introduced by TCP Service Differentiation ...................................... 203
Table 50 Parameters introduced by Advanced Step-wise SCell Addition for CA: Initial SCell
Addition in One Step ................................................................................................... 206
Table 51 Parameters related to Advanced Step-wise SCell Addition for CA: Initial SCell
Addition in One Step ................................................................................................... 206
Table 52 Parameters introduced by Fast Scheduling Flexible CA ...................................... 207
Table 53 Parameters introduced by UL Dynamic BLER Adaptation ................................... 208
Table 54 Parameters related by UL Dynamic BLER Adaptation ......................................... 208
Table 55 Key performance indicators related to UL Dynamic BLER Adaptation ............. 208
Table 56 Parameters introduced by Prolong Timer Override ............................................. 210
Table 57 Parameters related to Prolong Timer Override .................................................... 210
Table 58 Key performance indicators related to Prolong Timer Override ....................... 210

Issue 01D. © 2022 Nokia. Nokia Confidential Information 11

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Summary of changes
Changes between document issues are cumulative. Therefore, the latest document issue
contains all changes made to previous issues.

Changes between Issue 01C (SRAN 21A, 2021-10-13) and 01D (SRAN 21A,
2021-12-17)
The Enhanced flow control section has been updated. The M8011C57 Average UEs per DL
TTI counter has been removed and the LTE_6842aResidual Block Error Rate
(rBLER) in DL , LTE_5208aE-UTRAN RLC PDU Re-transmission Ratio
Downlink KPIs have been added.

The Buffering non-access stratum (NAS) messages during the Initial Context Setup (ICS)
section has been removed.

Changes between Issue 01B (SRAN 21A, 2021-05-12) and 01C (SRAN 21A,
2021-10-13)
The The correction of relative instantaneous channel quality calculation section has been
added.

The Improvement in UL SCell deconfiguration algorithm section has been added.

Changes between Issue 01A (SRAN 21A, 2021-03-08) and Issue 01B (SRAN
21A, 2021-05-12)
The section has been added.

Changes between Issue 01 (SRAN 21A, 2021-01-22) and Issue 01A (SRAN 21A,
2021-03-08)
The Changes introduced with SRAN 21A release section has been added.

The Updating radio quality counters (SINR/RSSI) when unreliable DTX transmission from UEs
occurs section has been added.

The Enhanced flow control section has been updated (more impacted counters added).

12 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
1. Changes introduced with new software release
Various changes impacting the system grouped per release and feature.

1.1 Changes introduced with SRAN 21A release

Impact on existing parameters (changed values, managed objects, or consistency checks),
counters, or existing functionalities (improvement or degradation of the functionality)
and algorithms

1.1.1 LTE5567 changes to the system

Some configuration changes can be observed in the BTSs after the system upgrade
process, due to implementation of new functionalities or due to enhancements of
existing functionalities, provided in the new release.

During the system upgrade to SRAN 21A, the following parameters get the following values:

Table 1: Changes in parameters during system upgrade to SRAN 21A

MO Parameter Value after

upgrade to
SRAN 21A

MRBTS/LNBTS/LNCEL Enable AMC for PDCCH link true

adaptation (enableAmcPdcch)

MRBTS/LNBTS/LNCEL Enable PDCCH power control true

(enablePcPdcch)

MRBTS/LNBTS/LNCEL Activate outer loop link true

adaptation (actOlLaPdcch)

MRBTS/LNBTS/LNCEL Enable OLQC (dlOlqcEnable) true

MRBTS/LNBTS/LNCEL Enable DL AMC (dlamcEnable) true

Depending on the values of other parameters, the following parameters are created and
configured or, if they existed before upgrade to SRAN 21A, they can get new values:
MRBTS/LNBTS/LNCEL PDCCH and HARQ response target BLER

Issue 01D. © 2022 Nokia. Nokia Confidential Information 13

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
(pdcchHarqTargetBler)
MRBTS/LNBTS/LNCEL PDCCH LA CQI shift (pdcchCqiShift)
MRBTS/LNBTS/LNCEL PDCCH CQI shift for 4Tx (pdcchCqiShift4Tx)
MRBTS/LNBTS/LNCEL Min PDCCH LA CQI shift for QCI1
(minPdcchCqiShiftQci1)
MRBTS/LNBTS/LNCEL Max PDCCH LA CQI shift for QCI1
(maxPdcchCqiShiftQci1)
MRBTS/LNBTS/LNCEL DL target BLER (dlTargetBler)

1.1.2 CB005932 changes to the SRAN 21A system

With the CB005932: SPID Forwarding in EN-DC Option 3x feature enabled, the number of
subscriber profile IDs (SPIDs) increases depending on how frequently the SgNB addition
and SgNB modification procedures take place. The SGNB ADDITION REQUEST and SGNB
MODIFICATION REQUEST messages are extended with the Subscriber Profile ID
for RAT/Frequency Priority information element (IE).

1.1.3 CB006028 changes to the system

The CB006028 feature brings changes to the faults.

With the CB006028: Independent Software Upgrade for Shared RU feature activated, also the
secondary BTS can raise the following faults:

23 Incompatible SW version detected

1850 SW corrupted

Fault 23 Incompatible SW version detected is triggered when there is a

misalignment between the RF and the BTS software. BTS checks if the fault 23 should be
raised in the following cases:
Shared radio is detected.
After the CB006028 feature is activated.
BTS recovers from temporary primary role as a secondary BTS.

Fault 1850 SW corrupted is triggered when the RF software is corrupted upon the shared
RU detection.

14 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
1.1.4 CB007258 changes to the SRAN 21A system
Modification of the NRDCDPR/NRDCPR NR DC measurement Configuration
(nrDcMeasConfig) parameter structure and introduction of the
ENDCDMEASCONF/ENDCMEASCONF managed object classes (MOCs). Parameters moved
from the NRDCDPR/NRDCPR MOCs to the ENDCDMEASCONF/ENDCMEASCONF MOCs.

The CB007258: NR MFBI Support in EN-DC feature introduces the following changes to
parameters and MOCs:
The NRDCDPR/NRDCPR NR DC measurement Configuration (nrDcMeasConfig)
parameter structure is removed, and it no longer holds the parameters for measurement
configuration of LTE-NR Dual Connectivity (DC) in a cell default profile (NRDCDPR MOC)
and cell dedicated profile (NRDCPR MOC).
The ENDCDMEASCONF MOC is added under the NRDCDPR MOC and holds all the
parameters for measurement configuration of LTE-NR DC on a single NR frequency in a
cell default profile.
The ENDCMEASCONF MOC is added under the NRDCPR MOC and holds all the parameters
for measurement configuration of LTE-NR DC on a single NR frequency in a cell dedicated
profile.

The changes described above affect the following parameters:

B1 NR DC RSRP Time to trigger (b1TimeToTriggerRsrp)
B1 NR DC RSRQ Time to trigger (b1TimeToTriggerRsrq)
B1 RSRP threshold for NR DC (b1ThresholdNrRsrp)
B1 RSRQ threshold for NR DC (b1ThresholdNrRsrq)
B1 Trigger Quantity for NR DC (b1TriggerQuantity)
B1-NR beam level report quantity (b1NrBeamReportQuantity)
B1-NR report amount (b1NrReportAmount)
B1-NR report interval (b1NrReportInterval)
Duration for blocking of B1-NR measurements (endcNrDropThreshTimer)
Duration for SS/PBCH blocks (ssbDuration)
Frequency Band Indicator NR (freqBandIndicatorNr)
Hysteresis RSRP for B1 NR DC (hysB1ThresholdRsrp)
Hysteresis RSRQ for B1 NR DC (hysB1ThresholdRsrq)
Maximum number of NR beams included in B1-NR measurement report
(b1NrMaxNumBeams)
NR carrier priority (nrCarPrio)
NR DC carrier frequency (carrierFreqNrCell)
NR PCI neighbor relation addition hysteresis (nrPciNbrRelAddHyst)

Issue 01D. © 2022 Nokia. Nokia Confidential Information 15

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
NR PCI neighbor relation addition threshold (nrPciNbrRelAddThresh)
NR PCI neighbor relation removal threshold (nrPciNbrRelRemThresh)
Offset for SS/PBCH blocks (ssbOffset)
Period for counting NR drops (endcNrDropWaitTimer)
Periodicity of SS/PBCH blocks (ssbPeriodicity)
Quantity configuration index for NR (quantityConfigId)
Subcarrier spacing of NR carrier (ssbSubcarrierSpacing)
Threshold of 5G drops before blocking of B1-NR measurements
(endcNrDropThresh)
Threshold RSRP for B1-NR beam level measurements
(b1NrBeamThreshRsrp)
Threshold RSRQ for B1-NR beam level measurements
(b1NrBeamThreshRsrq)

The following migration rules apply after system migration to the SRAN 21A release:
For each previously existing instance of the NRDCDPR/NRDCPR NR DC measurement
Configuration (nrDcMeasConfig) parameter, one instance of the
ENDCDMEASCONF/ENDCMEASCONF MOC is created. The parameters removed from the
nrDcMeasConfig parameter structure keep their previous values in the instance of the
ENDCDMEASCONF/ENDCMEASCONF MOC.
All the NRDCDPR/NRDCPR Frequency Band Indicator NR (freqBandIndicatorNr)
parameters from the nrDcMeasConfig parameter structure are migrated as a first
instance of the ENDCDMEASCONF/ENDCMEASCONF Frequency Band Indicator NR
list (freqBandIndicatorNrL) parameters, with the highest priority assigned. The
ENDCDMEASCONF/ENDCMEASCONF priority of NR frequency band (priority)
parameters are set to 0.

1.1.5 Cell resource groups changes to the system in

SRAN21A
Changes to the system introduced by cell resource groups features in release SRAN21A

The LNCEL Temporary activation flags #1 (tmpActFeat1) parameter is replaced

by the LNCEL Cell resource group SCell mode (cellResourceScellMode)
parameter.

16 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
1.2 Changes introduced with SRAN 20C release
Impact on existing parameters (changed values, managed objects, or consistency checks),
counters, or existing functionalities (improvement or degradation of the functionality)
and algorithms

1.2.1 LTE5226 changes to the SRAN20C system

The LTE5226: Increased Number of NR Carriers feature moves the LNBTS Wait for
high priority measurement report timer (mrWaitTimer) parameter to NRDCPR
and NRDCDPR managed object classes (MOCs) level. The ENDCMEASCONF and
ENDCDMEASCONF NR DC carrier frequency (carrierFreqNrCell) parameter
maximum range is reduced to 3279165.

1.2.2 TDD massive MIMO changes to the system in

SRAN20C
Changes to the system introduced by TDD massive MIMO features in SRAN20C

CB006432: Dynamic TDD mMIMO Sector Beamforming Weight Switching

The CB006432: Dynamic TDD mMIMO Sector Beamforming Weight Switching feature
introduces the LNCEL_TDD Activate Adaptive Sector BF Weight
(actAdptSectorBfWeight) parameter which is used to activate the feature. This
parameter replaces the LNCEL_TDD Activate Adaptive Vertical Sector BF
Weight (actAdptSectorBfWeightV) parameter which was introduced in the SRAN 20B
release to activate a performance enhancement for TDD massive MIMO.

CB006549: TDD Massive MIMO Beam Pre-grouping for Downlink MU-MIMO

Pairing
The CB006549: TDD Massive MIMO Beam Pre-grouping for Downlink MU-MIMO Pairing
feature introduces parameters to replace the temporary parameters used in the TDD
massive MIMO MU-MIMO pairing enhancement. The following parameters are introduced:
LNCEL_TDD Activate Downlink Pre-grouping for mMIMO MU
(actDlPreGrouping)
LNCEL_TDD Massive MIMO GoB(Grid of beam) TD metric factor for

Issue 01D. © 2022 Nokia. Nokia Confidential Information 17

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
downlink (mMimoGoBTdMetricFactorDl)
LNCEL_TDD Sector beam group weight (sectorBeamGrpWeight)
LNCEL_TDD Scaling factor for number of subgroup (scaleNumSubGrp)

1.3 Changes introduced with SRAN 20B release

Impact on existing parameters (changed values, managed objects, or consistency checks),
counters, or existing functionalities (improvement or degradation of the functionality)
and algorithms

1.3.1 LTE1320 changes to the system

The LTE1320: TDD ULDL Configuration 0(DSUUUDSUUU) feature's impact on parameters.

Introduction of the LTE1320 feature modifies ranges and consistency checks of the
following parameters:
LNCEL_TDD TDD subframe configuration (tddFrameConf)
LNCEL_TDD PRS configuration index (prsConfigurationIndex)

The LTE1320 also modifies consistency checks for additional parameters as required to
support the radio frame TDD ULDL configuration 0. For the full list see .

1.3.2 LTE5640 changes to the SRAN20B system

The LTE5640: Flexible ARP Ranges for EN-DC feature removes the LNBTS Starting ARP
for EN-DC eligible bearer (startArpEnDc) and LNBTS Stop ARP for EN-DC
eligible bearer (stopArpEnDc) parameters.

1.3.3 SR002488 changes to the system

The SR002488 feature modifies existing parameters.

The managed object class (MOC) NWSLICE (Network Slice) is introduced to LNBTS. It's
introduced to configure network slices based on the operator-specific QCI values.

The following parameters have been modified for the SR002488 feature:

18 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
FSTSCH First level scheduler identifier(fstSchId): This parameter has
been modified for SR002488. Product specific descriptors (PSD) field TNL -MO
MaxOccurs has been changed from 50 to 52.
IPIF IP interface object identifier(ipIfId): This parameter has been
modified for SR002488. PSD field TNL -MO MaxOccurs has been changed from 48 to
72.
IPADDRESSV4 IPv4 address object identifier(ipAddressV4Id): This
parameter has been modified for SR002488. PSD field TNL -MO MaxOccurs has been
changed from 32 to 64.
IPADDRESSV6 IPv6 address object identifier(ipAddressV6Id): This
parameter has been modified for SR002488. PSD field TNL -MO MaxOccurs has been
changed from 32 to 64.
IPRT IPv4 routing table object identifier(ipRtId): This parameter has
been modified for SR002488. PSD field TNL -MO MaxOccurs has been changed from
32 to 64.
VLANIF VLAN interface object identifier(vlanIfId): This parameter has
been modified for SR002488. PSD field TNL -MO MaxOccurs has been changed from
36 to 56.

For reference data descriptions, see Single RAN System/SRAN Reference Data.

1.3.4 SR002493 changes to the system

The SR002493 feature brings changes to the configuration migration mechanism.

Using the functionality introduced with the SR002493: SW Activation With Configured SCF
feature, the configuration file downloaded by the operator is saved by the system to the
BTS passive file partition. In this case:
1. The BTS does not migrate the running configuration.
2. The BTS converts the format of the downloaded target SCF (the configuration is
translated from RAML file to IMS2 file).
3. After startup, the BTS reads the IMS2 file containing the target configuration.

1.3.5 TDD massive MIMO changes to the system in

SRAN20B
Changes to the system introduced by TDD massive MIMO features in SRAN20B

Issue 01D. © 2022 Nokia. Nokia Confidential Information 19

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
LTE5404: TDD Massive MIMO PDCCH Spatial Multiplexing on ABIC
The LTE5404: TDD Massive MIMO PDCCH Spatial Multiplexing on ABIC feature brings
modifications to the physical downlink control channel (PDCCH) allocation algorithm. It
introduces PDCCH spatial multiplexing to enhance PDCCH capacity for TDD mMIMO on ABIC
hardware. Specifically:
32TRX on ABIC (top/bottom split mode from 64TRX radio) which is introduced through
the LTE5116: TDD Massive MIMO 32TRX on ABIC and LTE5400: TDD massive MIMO
ABIC remaining porting features.
64TRX on ABIC which is introduced by the LTE4671/SR002305: TDD Massive MIMO on
ABIC feature.

LTE5674: Downlink QoE-based Scheduling Enhancement for TDD Massive

MIMO
The LTE5674: Downlink QoE-based Scheduling Enhancement for TDD Massive MIMO feature
improves UE throughput by introducing enhancements to scheduling algorithms. These
include improvements to prioritized tail packet (PTP) scheduling algorithm as well as packet
aggregation scheduling (PAS) algorithm for non-GBR bearers.

1.3.6 TDD remote interference changes to the system

The LTE5602: TDD Remote Interference Avoidance Based on Downhill Trend feature
introduces a new parameter.

1.3.6.1 LTE5602 changes to the system in release SRAN

20B
The LNBTS Temporary activation flags #2 (tmpActFeat2) parameter is replaced
with the RIAPR Allowance of rollback DwPTS from SSP6/7 to SSP5(3:9:2)
for downhill trend of remote interference in a defined duration
(allowRollDwPtsByRI) parameter for activation of the LTE5602 feature.

20 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
1.3.7 Changes to the system brought by enhancements of
actual EIRP control for non-beamforming cells in SRAN
20B
The LTE5574: Enhancements of Actual EIRP Control for Non-Beamforming Cells feature
modifies specific parameters so that they no longer require object locking when modified.

The following LNCEL parameters are modified and no longer require object locking when
modified:
Activate EIRP Control (actEirpControl)
EIRP reduction (eirpReduction)
Antenna Gain for Non Beamforming (antGainNonBF)

1.4 Changes introduced with SRAN 20A release

Impact on existing parameters (changed values, managed objects, or consistency checks),
counters, or existing functionalities and algorithms

1.4.1 TDD Massive MIMO changes to the system in

SRAN20A
Changes to the system introduced by TDD massive MIMO features

LTE5462: TDD mMIMO Zero Forcing

The LTE5462: TDD mMIMO Zero Forcing feature enhances the existing TDD mMIMO
algorithm. Previously, the beam weights are calculated based on Eigen-based Beamforming
(EBB) algorithm. With the LTE5462 feature, the Zero Forcing (ZF) algorithm is introduced and
is applied only on beams within the vertical plane.

1.4.2 Plug and Play changes to the system

Changes to the system introduced by Plug and Play (PnP) features

The SR001670: BTS Support for New Plug and Play Services and SR001540: LTE Plug and
Play Feature Parity for Common OAM features replace the following legacy LTE PnP features:

Issue 01D. © 2022 Nokia. Nokia Confidential Information 21

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
LTE154: SON LTE BTS Auto Connectivity
LTE720: SON LTE BTS Auto Configuration
LTE1058: Plug & Play Extensions
LTE1448: VLAN Scan Optimization
LTE1992: Flexi HW Replacement - Detect and Restore

1.4.3 SR001865 changes to the system

The SR001865: Protection for Incompatible BTS SW Upgrade feature brings changes to
the BTS SW package and NetAct SW Manager functionalities.

Changes to the BTS SW package

A new file (sw_compatibility.xml) containing compatibility information related to SW
upgrade paths is created.

Changes to NetAct SW Manager functionalities

NetAct SW Manager uses the metadata in the sw_compatibility.xml file to check the
conversion compatibility for a selected BTS SW package. During SW operations, (for example,
SW download or SW provision), only the compatible SW packages are listed for selection and
execution.

1.4.4 SR002817 changes to the system

The SR002817: BTSMED Ramp Down feature removes BTS Mediator (BTSMED) along with
the associated features from the network.

BTSMED along with the following associated features are removed from Single RAN 20A
onwards:
LTE3435/SR001536: BTS Mediator
LTE3875/SR001756: BTS Mediator Resiliency (Active-Standby)
LTE3937/SR001796: BTSMED Operability and Maintenance
LTE3938/SR001841: BTSMED NTP Proxy and Syslog Server Support
LTE4172/SR001917: BTSMED Active-Active Resiliency
LTE4512/SR001985: BTSMED Capacity Extension
LTE4808/SR002051: BTSMED RHEL7

22 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
LTE4831/SR002121: BTSMED for Bare-Metal
LTE5022/SR002238: Multiple BTSMEDs

BTSMED is still supported for previous releases (SRAN 19, 19A, and 19B) and the BTSMED SW
is still used to support the BTS upgrade from SRAN 19 to SRAN 20A SW, before switching to
Direct Integration. Customers which have SRAN 19 need to upgrade their BTSMED first to
BTSMED 19B, before the upgrade to SRAN 20A.

1.4.5 LTE5306 changes to the system

The NB-IoT parameters, counters, and KPIs visible changes to the system caused by the
LTE5306: NB-IoT Release Assistance Indication and Inactivity Timer per Coverage Level
feature introduction.

Parameters
The inactivity timer related parameter has been modified to allow to set the signaling radio
bearer (SRB) timer for NB-IoT UEs in different coverage levels.

The NBIOTPR SRB inactivity timer (srbInactivityTimerNB) parameter is no

longer used for NB-IoT cell, and it is replaced by:
NBIOTPR schedProfNBNorCov/srbInactivityTimerNB parameter
NBIOTPR schedProfNBRobCov/srbInactivityTimerNB parameter
NBIOTPR schedProfNBExtCov/srbInactivityTimerNB parameter

The power control parameters have been modified to differentiate the default value of NB-
IoT cells and the host cell.

The two power control parameters are no longer used for NB-IoT cell:
The LNCEL Nominal power for UE PUSCH or NPUSCH TX power calculation
(p0NomPusch) parameter is replaced with NBIOT_FDD Nominal power for NB-IoT
UE NPUSCH TX power calculation (p0NomNpusch) parameter.
The LNCEL/SIB Preamble initial received target power (ulpcIniPrePwr)
parameter is replaced with NBIOT_FDD Preamble initial received target
power in NB-IoT cell (ulpcIniPrePwrNB) parameter.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 23

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Counters
The LTE5306: NB-IoT: Release Assistance Indication and Inactivity Timer per Coverage Level
feature with LTE4147: NB-IoT Performance Monitoring feature rearrange some of the NB-
IoT counters. The NB-IoT related counters were replaced either with a new counter in new
measurement type, or by more than one counter (with division per coverage enhancement
level).

When Release Assistance Indication (RAI) is in use, the following counter values decrease:
M8201C0 Accumulated time duration in RRC_CONNECTED for NB-IoT UEs,
which selected coverage enhancement level 0 during random access
M8201C1 Accumulated time duration in RRC_CONNECTED for NB-IoT UEs,
which selected coverage enhancement level 1 during random access
M8201C2 Accumulated time duration in RRC_CONNECTED for NB-IoT UEs,
which selected coverage enhancement level 2 during random access

The decrease in counter values depends on the number of prioritized RRC Connection
Release messages, the number of RRC-connected UEs, and a selected coverage level. The
decrease in counter values also depends on the setting for inactivity timer
(schedProfNBNorCov/srbInactivityTimerNB,
schedProfNBRobCov/srbInactivityTimerNB,
schedProfNBExtCov/srbInactivityTimerNB, and cpInactivityTimerNB
parameters).

When RAI is in use, the following counter values increase:

M8200C0 Accumulated time for RRC connection setup duration for NB-
IoT UEs, which selected coverage enhancement level 0 during random
access
M8200C1 Accumulated time for RRC connection setup duration for NB-
IoT UEs, which selected coverage enhancement level 1 during random
access
M8200C2 Accumulated time for RRC connection setup duration for NB-
IoT UEs, which selected coverage enhancement level 2 during random
access

The increase in counter values depends on the time spent by eNB on UE capability retrieval
from Mobility Management Entity (MME), the number of RRC-connected UEs, a selected
coverage level, and the difference between the RRCConnectionSetupComplete-NB
message and the corresponding RRCConnectionRequest-NB message.

When UE is released by RAI, but after that the data arrives, the NB-IoT UEs are experiencing

24 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
additional RRC connection setup attempts and NB-IoT RRC paging messages (paging is used
to inform the UE which is in idle mode that there is some data for it). With such situation, the
following counter values increase:
M8066C20 RRC paging requests (records) for NB-IoT UEs
The NB-IoT UEs random access-related counters per selected coverage enhancement
(CE) level (CE 0, CE 1, CE 2):
M8200C3/M8200C4/M8200C5 Attempted RRC Connection Establishments
with cause "mt-Access" for NB-IoT UEs
M8200C12/M8200C13/M8200C14 Successful RRC Connection
Establishments with cause "mt-Access"
M8201C0/M8201C1/M8201C2 Accumulated time duration in
RRC_CONNECTED for NB-IoT UEs
M8201C3/M8201C4/M8201C5 UE movement to ECM idle state (eNB
initiated) for NB-IoT UEs
M8201C6/M8201C7/M8201C8 UE movement to ECM idle state (MME
initiated) for NB-IoT UEs
M8201C15/M8201C16/M8201C17 UE movement to ECM idle state due to
user inactivity for NB-IoT UEs
M8204C23/M8204C24/M8204C25 NPRACH preambles for NB-IoT UEs
M8204C56/M8204C57/M8204C58 Accumulated delay for data
transmission on SRB1bis for NB-IoT UEs
The NB-IoT UEs connection-related counters per selected CE level (CE 0, CE 1, CE 2):
M8200C40/M8200C41/M8200C42 Successful RRC Connection
Establishment for NB-IoT UEs
M8200C43/M8200C44/M8200C45 Attempted RRC Connection Establishment
for NB-IoT UEs
M8200C46/M8200C47/M8200C48 Attempted UE-associated logical S1-
Connection Establishments for NB-IoT UEs
M8200C49/M8200C50/M8200C51 Successful UE-associated logical S1-
Connection Establishments for NB-IoT UEs
The narrowband physical downlink shared channel (NPDSCH) usage-related counter:
M8204C65/M8204C66/M8204C67 NB-IoT NPDSCH usage time

The increase in counter values depends on the number of NB-IoT UEs experiencing the
events of data arrival after RAI-based release.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 25

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
KPIs
KPIs are modified as a result of the existing counters being replaced with new ones.

When RAI is in use, the following KPI values decrease:

LTE_6876b E-UTRAN Average Session Duration for NB IoT UEs
LTE_6877b E-UTRAN Average Session Duration for NB IoT UEs per CE
Level 0
LTE_6878b E-UTRAN Average Session Duration for NB IoT UEs per CE
Level 1
LTE_6879b E-UTRAN Average Session Duration for NB IoT UEs per CE
Level 2

The decrease in KPI values depends on the ratio of the number of the NB-IoT UE releases
due to RAI-based user inactivity and total number of releases due to user inactivity and
selected coverage level. The higher the ratio is, the bigger decrease of selected coverage
level- related KPI may be. The ratio can be monitored via dedicated LTE_8026a E-UTRAN
Percentage UE Transitions to ECM-IDLE State Due to RAI Based User
Inactivity KPI.

1.4.6 LTE5620 changes to the system

New child parameters and changes in the full name of existing parameters are introduced
by the LTE5620: CAT-M1: Initial MCS per CELevel for CEModeA feature

The CATMPR Initial MCS in downlink of Cat-M CE Level 0

(iniMcsDlModeACatM) parameter full name is changed from Initial MCS in
downlink of Cat-M in CE modeA to Initial MCS in downlink of Cat-M CE
Level 0.

The CATMPR Initial MCS in uplink of Cat-M CE Level 0

(iniMcsUlModeACatM) parameter full name is changed from Initial MCS in uplink
of Cat-M in CE modeA to Initial MCS in uplink of Cat-M CE Level 0.

New child CATMPR Initial MCS in downlink of Cat-M in CE Level 1

(iniMcsDlModeACatM) and Initial MCS in uplink of Cat-M in CE Level 1
(iniMcsUlModeACatM) parameters are added to the CATMPR CE(Coverage
Enhancement) Level 1 Table for Cat-M (catMCELevel1) parameter.

26 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
1.5 Changes introduced with LTE 19B release
Impact on existing parameters (changed values, managed objects, or consistency checks),
counters, or existing functionalities and algorithms

1.5.1 LTE1118 changes to the system

Modified counter description

The counter M8011C51 has been modified to include PRBs allocated with RAT1.

1.5.2 LTE2971 changes to the system

The DRX profile 6 (drxProfile6) and DRX smart profile 6
(drxSmartProfile6) profiles are now configured for QCI1, QCI2, QCI3, QCI4, QCI65,
QCI66, QCI69, and operator specific QCIs (in the range from 128 to 254).

1.5.3 LTE4549 changes to the LTE19B system

Additional value added for the LNBTS Activation of CA in LTE-NR Dual
Connectivity (actCAggrLteNrDualConnectivity) parameter.

The enhanced_CA_LTE_NR value is added to the LNBTS Activation of CA in LTE-

NR Dual Connectivity (actCAggrLteNrDualConnectivity) parameter choice. This
value is used to activate the Flexible LTE CA with EN-DC functionality.

1.5.4 LTE5266 changes to the system

Parameter location changes.

The following parameters have been moved to another location:

The Inter Freq Load Balance A4 active limit (iFLBA4ActLim) parameter

has been moved from LNBTS to LNCEL.
The Activate active mode load equalization (actAmle) parameter has been
moved from LNBTS to LNCEL.
The Activation of inter-frequency load balancing (iFLB)
(actInterFreqLB) parameter has been moved from LNBTS to LNCEL.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 27

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Note:

The location change is part of the release software.

1.5.5 LTE5510 changes to the LTE19B system

Extension for the X2AP: SGNB MODIFICATION REQUEST message.

The X2 interface SGNB MODIFICATION REQUEST processed message is enhanced with the
E-RABs To Be Added information element (IE) related to the additional multiple bearers
for already existing EN-DC connection.

1.5.6 LTE5558 changes to the LTE19B system

The LTE5558: S1 Handover for LTE-NR DC Option 3x feature introduces the intra-LTE S1
handover for UEs with SN-terminated split bearer established.

1.5.7 LTE-M mobility changes to the system in LTE19B

Changes to the system introduced by LTE-M mobility features in release LTE19B

The LTE5303:Cat-M1: Separate HO Measurement Thresholds for VoLTE and Data feature,
introduces the following changes to the parameters:

Deleted parameters
A3 report interval for Cat-M (a3ReportIntervalCatM)
A3 report interval RSRP inter frequency for Cat-M
(a3ReportIntervalRsrpInterFreqCatM)

Replaced parameters

The Hysteresis of A2 threshold for Cat-M intra and inter frequency

handover measurement (hysThreshold2CatM) parameter replaces:
Hysteresis of A2 threshold for Cat-M intra and inter frequency
handover measurement (hysThreshold2CatM) and

28 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Threshold th2 RSRP inter frequency for Cat-M
(threshold2InterFreqCatM).
It takes the values from the hysThreshold2CatM parameter and the
threshold2InterFreqCatM parameter is no longer used.

The Hysteresis of A2 threshold for Cat-M intra and inter frequency

handover measurement (hysThreshold2CatM) parameter replaces:
Hysteresis of A2 threshold for Cat-M intra frequency handover
measurement (hysThreshold2IntraFreqCatM) and
Related hysteresis of threshold th2 interFreq for Cat-M
(hysThreshold2InterFreqCatM)
It takes the values from the hysThreshold2IntraFreqCatM parameter and the
hysThreshold2InterFreqCatM parameter is no longer used.

The Time to trigger for A1 measurement for Cat-M

(a1TimeToTriggerCatM) parameter replaces the Time to trigger for A1 inter
frequency measurement for Cat-M (a1TimeToTriggerRsrpInterFreqCatM)
parameter.

The Time to trigger for A2 event to activate Cat-M intra and inter
frequency handover measurement (a2TimeToTriggerCatM) parameter replaces:
Time to trigger for A2 event to activate Cat-M intra frequency
handover measurement (a2TimeToTriggerIntraFreqCatM) and
Time to trigger for A2 inter frequency measurement for Cat-M
(a2TimeToTriggerRsrpInterFreqCatM)
It takes the values from the a2TimeToTriggerIntraFreqCatM parameter and the
a2TimeToTriggerRsrpInterFreqCatM parameter is no longer used.

1.6 Changes introduced with LTE19A release

Impact on existing parameters (changed values, managed objects, or consistency checks),
counters, or existing functionalities and algorithms

Issue 01D. © 2022 Nokia. Nokia Confidential Information 29

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
1.6.1 LTE652 changes to the system
Description of alarm/parameter changes that are introduced with the LTE652: Intelligent
Flexi BTS Shutdown feature.

In case the main power outage takes place, and the battery backup is present, the intelligent
shutdown alarm starts. The BTS informs the operator about the fault (4395 Cells shutdown
due to mains break).

The fault is also reported when the BTS power supply is available again, but not all cells are
enabled yet. When all previously shutdown cells are enabled again, the alarm resulting from
this fault is cleared.

See

Parameter:

Following parameters are introduced with this feature:

Intelligent shutdown in use (intShutdownInUse)
The Intelligent shutdown in use parameter denotes if the intelligent shutdown
feature is enabled or disabled.
Intelligent shutdown timeout (intShutdownTimeout)
The Intelligent shutdown timeout parameter denotes the timeout for the
intelligent shutdown in minutes. The zero value means that the cell is immediately
shutdown with high priority. If the parameter is not present in the LNCELL object, it
means that the cell remains operational until the batteries run out.

See

1.6.2 LTE1709 changes to the system

Starting with the LTE19A release, the LTE1709: Liquid Cell feature is disabled and cannot
be activated anymore. The Activate liquid cell configuration
(actLiquidCell) LNCEL_FDD parameter must be set to false.

1.6.3 LTE4034/SR001670 changes to the system

The introduction of the LTE4034 feature replaces legacy Plug and Play features.

The LTE4034/SR001670: BTS support for new Plug and Play Services feature substitutes the
following features:

30 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
LTE154: SON LTE BTS Auto Connectivity
LTE720: SON LTE BTS Auto Configuration

1.6.4 LTE4531 changes to the LTE19A system

Logical channel identity (LCID) change procedure upgrade and QCI translation table
enlargement

With the LTE4531: LTE-NR DC Option 3X: Multiple non-GBR SCG Split Bearers feature
released in the LTE19A, the following changes are introduced:
The LCID change procedure works without data radio bearer identifier (DRB ID) release
during bearer change. Upgraded procedure uses Packet Data Convergence Protocol
(PDCP) and Radio Link Control (RLC) reestablishment procedures.
The QCI translation table QCI 5 (qciTab5), and QCI translation table
QCI 70 (qciTab70) parameters are available.

1.6.5 LTE4701 changes to the system

The feature introduces the Activate improvements to CA architecture
enhancements (actCaArchEnhImp) parameter replacing the Enable carr. aggr.
architecture enhancements (actCaArchEnh) parameter.

1.6.6 LTE4875 changes to the system

For Licensed Assisted Access (LAA), the Maximum output power, LAA mode
(pMaxLaa) parameter is introduced.

It replaces the Maximum output power (pMax) parameter that enables the operator to
set the maximum output power of the cell per antenna carrier.

The Maximum output power, LAA mode (pMaxLaa) parameter allows eNB to
automatically calculate maximum output power of the LAA cell per antenna carrier.

The value of calculated output power depends on:

used hardware
the country of operation
the number of configured LAA cells
which specific unlicensed sub-bands are enabled

Issue 01D. © 2022 Nokia. Nokia Confidential Information 31

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
1.6.7 LTE5063 changes to the system
Impact on physical uplink control channel (PUCCH) resources, and changes to the system.

LTE5063 inherits the below restrictions with the same consideration as LTE3230: UL
Interference Offsets and LTE3242: A-MPR:

Most of the restrictions, found in TS36.101, affect the borders of a cell's radio spectrum.
Usually this is where the cell's PUCCH resources are configured. To keep PUCCH unaffected
by restrictions, LTE3230/LTE3242 configures PUCCH resources so that they are relocated
towards the center of the cell's bandwidth. This means that there are two outer physical
uplink shared channel (PUSCH) regions with maximum UE power restriction in at least one of
them, and one central region between PUCCH resources.

Overall, the fragmentation of PUSCH reduces the peak throughput because:

The maximum allocation size is reduced to the number of physical resource blocks (PRB)
left between PUCCH resources, and
UEs can be scheduled in only one region (one of the outer PUSCH regions or the central
PUSCH region)
Multicluster UL scheduling for legacy/wideband LTE is not supported because it adds high
complexity, and the power backoff that is to be considered in multicluster allocations
restricts the gain that can be expected.

1.6.8 LTE5135 changes to the system

The LTE5135: Geofencing Information in CMAS Notification feature adds the Warning
area coordinates allowed (warnAreaCoAllowed) parameter and uses an optional
segment in the WRITE-REPLACE WARNING REQUEST message.

The LTE5135: Geofencing Information in CMAS Notification feature introduces a new

parameter, Warning area coordinates allowed (warnAreaCoAllowed), which is
used to activate and deactivate the feature.

When the LTE5135 feature is enabled, the optional segment

warningAreaCoordinatesSegment-r15 (which contains geofencing information) is used
in the WRITE-REPLACE WARNING REQUEST message.

32 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
1.6.9 LTE5335 changes to the LTE19A system
Mobility scenarios improved and inter-site Carrier Aggregation (CA) support with EN-DC
added.

With the LTE5335 feature, functions of the LTE4088: LTE-NR Dual Connectivity Option 3x
feature listed below are improved:
The error handling and safeguarding from contrary messaging on layer 2 (L2) /control
plane (C-plane) interface during the Secondary Node (SN)-terminated split bearer
takeback was added.
The resources management improvement in case of immediate UE Context Release when
the EN-DC release is initiated by the Mobility Management Entity (MME) or the eNB.
The UE context preemption for UEs with EN-DC established was added.

With the LTE5335 feature, functions of the LTE4193: Dynamic Trigger for LTE-NR DC Option
3x feature listed below are improved:
The Initial Context Setup (ICS) with EN-DC and coverage-based trigger update improves
the reconfiguration of physical uplink control channel (PUCCH) resources to position
compatible with EN-DC measurement gap offset. This update affects FDD cell only.
The bearer preemption of last eligible bearer was added.
Release of the last EN-DC eligible bearer when B1-NR measurements are activated
improves better resource management.
The sounding reference signal (SRS) resource handling and coverage-based trigger
improves allocation of the SRS to avoid collision with the measurement gap set up during
ICS procedure by the coverage-based trigger B1 NR measurements. This update affects
TDD cell only.

With the LTE5335 feature, functions of the LTE4575: Blind Carrier Aggregation with LTE-NR
DC Option 3x feature listed below are improved:
The support for inter-eNB and inter-site Carrier Aggregation (CA) were added. With this
functionality, the EN-DC partner gNB can be on different site.
The following per call measurement data (PCMD) is added:

Issue 01D. © 2022 Nokia. Nokia Confidential Information 33

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Table 2: Additional PCMD field

Measurement data Description

Carrier Aggregation This filed indicates the number of times CA de-

Deconfiguration Cause 5 configuration involving this secondary cell (SCell) (SCell
release) is attempted for the following cause:
- SCell de-configuration due to EN-DC setup or
Secondary Node (SN) change (LS byte 1)
- Not applicable (byte 2)
- Not applicable (byte 3)
- Not applicable (byte 4)
Other causes are defined in PCMD fields Carrier
Aggregation Deconfiguration Cause 1,
Carrier Aggregation Deconfiguration
Cause 2, Carrier Aggregation
Deconfiguration Cause 3 and Carrier
Aggregation Deconfiguration Cause 4.

The following PCMD are modified:

The list of other causes defined in PCMD fields for the Carrier Aggregation
Deconfiguration Cause 1, Carrier Aggregation Deconfiguration Cause
2,Carrier Aggregation Deconfiguration Cause 3 and Carrier
Aggregation Deconfiguration Cause 4 were extended by the Carrier
Aggregation Deconfiguration Cause 5.
The LTE4575 feature Activation of CA in LTE-NR Dual Connectivity
(actCAggrLteNrDualConnectivity) activation flag is online modifiable.

1.7 Changes introduced with LTE 19 release

Impact on existing parameters (changed values, managed objects, or consistency checks),
counters, or existing functionalities and algorithms

1.7.1 LTE3435 changes to the system

The LTE3435: BTS Mediator introduction to LTE feature introduces BTS Mediator into use
in LTE. The Open Fault Standard version 3.0.5 is adapted with the formatting changes
replacing separator <name> : <value> with <name> = <value>.

34 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
1.7.2 LTE4575 changes to the LTE19 system
Decrease of counters related to Carrier Aggregation (CA) secondary cell (SCell)

After the LTE4575: Blind Carrier Aggregation with LTE-NR DC Option 3x feature is activated,
and the UE enters the EN-DC mode, the SCell addition is not allowed anymore. The values of
counters related to the number of CA SCells will decrease in the event of EN-DC induced or
regular SCell release.

Table 3: List of counters impacted by the LTE4575 related to the SCell in CA

Type Counter ID Counter name Measurement

Existing M8011C67 Number of SCell LTE Cell Resource

configuration
attempts

Existing M8011C68 Number of LTE Cell Resource

successful
SCell
configurations

Existing M8011C165 Number of event LTE Cell Resource

A6 triggered
SCell swaps

Existing M8012C151 PCell RLC data LTE Cell Resource

volume in DL
via SCell

Existing M8051C116 Average number LTE UE Quantity

of UEs with one
activated SCell

Existing M8051C117 Average number LTE UE Quantity

of UEs with two
activated
SCells

Existing M8051C121 Average number LTE UE Quantity

of DL carrier
aggregated
capable UEs for
2 CCs

Existing M8051C122 Average number LTE UE Quantity

of DL carrier
aggregated
capable UEs for
3 CCs

Issue 01D. © 2022 Nokia. Nokia Confidential Information 35

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Type Counter ID Counter name Measurement

Existing M8051C123 Average number LTE UE Quantity

of UEs with one
configured
SCell

Existing M8051C124 Average number LTE UE Quantity

of UEs with two
configured
SCells

Existing M8011C213 Downlink CA LTE Cell Resource

Deconfiguration
Attemps

Existing M8011C214 Downlink CA LTE Cell Resource

Deconfiguration
Successes

1.7.3 LTE4788 changes to the system

Description of parameter changes that are introduced with the LTE4788: ETSI and IC DFS
Support for LAA feature.

The following parameters are changed by the LTE4788: ETSI and IC DFS Support for LAA
feature:

Wi-Fi Channel Selection List (uCellChannelSList), Transmit Power per

LAA cell (pMaxLaa) and ITU Region (lteUItuRegion) parameters
These parameters are configured and updated by the eNB software. Previously
configured by the operator.

1.7.4 LTE4504 changes to the system

The LTE4504: BTS Rx-Sniffing feature replaces the LTE1434: Flexi Multiradio BTS
antenna Rx RF-sniffing and LTE2556: Flexi Multiradio BTS Rx-Sniffing enhancements
features.

36 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
1.7.5 LTE5268 changes to the system
With the LTE5268: NB-IoT: Coexistence with UL CoMP feature, the ULCOMP Uplink CoMP
Cell ListUplink CoMP Cell List (ulCoMpCellList) parameter is modified, to
allow the coexistence of UL CoMP and NB-IoT technologies on the same hosting LTE cell.

1.7.6 LTE4088 changes to the LTE19 system

Description of changes that are introduced to the data model with the LTE4088: LTE-NR
Dual Connectivity Option 3x feature.

The following changes are introduced by the LTE4088: LTE-NR Dual Connectivity Option 3x
feature:

In LNBTS:
The existing LNBTS QCI translation table QCI 6 (qciTab6), QCI translation
table QCI 7 (qciTab7), QCI translation table QCI 8 (qciTab8), QCI
translation table QCI 9 (qciTab9) parameters are extended by three new
structure members:
LNBTS LTE-NR Dual connectivity support (from
qciTab6.lteNrDualConnectSupport to
qciTab9.lteNrDualConnectSupport) which allows to set the support for EN-DC.
The next new member in the same qciTab6, qciTab7, qciTab8, qciTab9 must be
configured.
LNBTS NR PDCP profile index (from qciTab6.nrPdcpProfIdx to
qciTab9.nrPdcpProfIdx) which is a pointer to the NR-PDCP profile.
The existing LNBTS QCI translation table operator specific QCIs
(qciTabOperator) parameter is extended by two new structure members:
LNBTS LTE-NR Dual connectivity support (lteNrDualConnectSupport)
which allows to set the support for EN-DC. The next new member in the same QCI
translation table (from qciTab6 to qciTab9) must be configured.
LNBTS NR PDCP profile index (qciTabOperator.nrPdcpProfIdx) which is a
pointer to the NR-PDCP profile.
In LTE-NR Dual Connectivity, the LNBTS Status report required
(pdcpProf1001.statusRepReq) parameter has only one supported value.
The existing LNBTS Sequence number size DL (snSizeDl) parameter is split into UL
(Sequence number size UL pdcpProf1001.snSizeUl) and DL (Sequence
number size DL pdcpProf1001.snSizeDl) where the limitation to 18-bit is
included.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 37

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
New managed object classes (MOCs) are added: LNRELGNBCELL, NRDCDPR, and NRDCPR
(dedicated profiles).

1.8 Changes introduced with LTE 18A release

Impact on existing parameters (changed values, managed objects, or consistency checks),
counters, or existing functionalities and algorithms

1.8.1 LTE3571 changes to the system

List of modified parameters

The following existing parameters are modified by the LTE3571: NB-IoT co-existence with
eICIC feature:

Table 4: Parameters modified by the LTE3571 feature

Full name Abbreviated name Change description

Activate enhanced inter- actEicic Parameter modified to allow the

cell interference co-existence of eICIC and inband
coordination
NB-IoT technologies on the same
hosting LTE cell.

Nb-IoT operation mode nbIoTMode Parameter modified to allow the

support of eICIC together with
inband NB-IoT on the same
hosting LTE cell.

1.8.2 LTE2774 changes to the system

The SID packet sizes, that are constant values for the relevant audio codecs (AMR, AMR-
WB and EVS) have been reduced to make UL allocations more adapted to the real packet
sizes.

38 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
1.8.3 LTE2617 changes to the system
The LTE2617: Increased Carrier Monitoring in Idle Mode feature introduces the following
changes.

Configuration Management
Introduced parameters, such as the incMonExSel and reducedMeasPerformance
parameters, are mandatory when SIB5 is configured, whereas the eutCelResSubPrio and
cellReSelSubPrio parameters are optional.

Note:

These new parameters are valid for both FDD and TDD cells. In case of NB-IoT FDD
cells, the value of these parameters is ignored by the eNB.

The following parameters are updated:

The multiplicity of the Inter frequency Idle Mode parameters (IRFIM)
managed object class (MOC) is extended from 8 to 16.
The multiplicity of the dlCarFrqEutL structure under the Mobility Idle Mode
Default Profile (MODIMP) and Mobility Idle Mode Profile (MOIMP) MOCs
is extended from 8 to 16.

When extendedFreqPriorities-r13 is supported by the UE,

cellReselectionSubPriority which includes fraction numbers is also supported. As a
result, the following parameter values are extended to support fraction numbers:
idleLBCellReSelPrio
idleLBCellReSelPrio2CC
idleLBCellReSelPrio3CC
idleLBCellReSelPrio4CC
idleLBCellReSelPrio5CC
idleLBEutCelResPrio
idleLBEutCelResPrio2CC
idleLBEutCelResPrio3CC
idleLBEutCelResPrio4CC
idleLBEutCelResPrio5CC

Issue 01D. © 2022 Nokia. Nokia Confidential Information 39

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Consistency Checks
A new SIB5 message cutting rule is introduced which changes the SIB5 consistency check.
When the configured content is larger than expected, some SIB5 content will be cut out as a
result. A warning will be raised and sent to operators when this occurs.

1.8.4 LTE4259 changes to the system

The LTE4259 feature changes the range of values for two parameters

The range of values for the following parameters is extended:

IFGPR Group Size in dedicated group profile (groupSize)

IFGDPR Group Size in default group profile (groupSize)

The new range is from 0 to 16.

1.8.5 LTE2179 changes to the system

List of modified parameters

The following existing parameters are modified by the LTE2179: TDD downlink carrier
aggregation 4CC - 80 MHz feature:

40 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Table 5: Parameters modified by the LTE2179 feature

Full name Abbreviated name Change description

Max. DL CA maxDlCaConfigForUlCa Added TDD applicability.

configuration for UL
CA

Max number of maxNumScells Parameter setting 2 changed

secondary cells for into 3 in the consistency check.
DL carrier aggr

Max number carrier maxNumCaConfUe3c Modification attribute changed

aggr configured UEs 3 from On-line to Requires
carriers
object locking.
Parameter name amended to
accommodate for increased
number of SCells.
Setting extended to 50.

Activate flexible actFlexScellSelect Parameters consistency check

SCell selection amended to allow inter-
operability with Cell Resource
Groups for 4 CC CA.

Activation of actDLCAggr Parameters consistency check

downlink carrier amended to allow inter-
aggregation
operability with Cell Resource
Groups for 4 CC CA.

Cell resource sharing cellResourceSharingMo Parameters consistency check

mode de amended to allow inter-
operability with Cell Resource
Groups for 4 CC CA.

Activation of actAutoPucchAlloc Parameters consistency check

automatic PUCCH amended to allow inter-
allocation
operability with Cell Resource
Groups for 4 CC CA.

1.8.6 LTE4096 changes to the system

At least one QCI translation table, that is the QCI translation table operator
specific (QCIsqciTabOperator) structure must be configured with the value of
the QCI (qci) parameter in the 98 to 100 range to activate the LTE4096 feature.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 41

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
1.8.7 LTE4117 changes to the system
The LTE4117: NB-IoT: Inter-frequency Idle mode Mobility feature introduces support of
SIB4-NB for intra-frequency enhancement and SIB5-NB allowing NB-IoT UEs for inter-
frequency cell reselection.

The LTE4117: NB-IoT: Inter-frequency Idle mode Mobility feature brings the following
changes:

The LTE4117 feature support system information blocks (SIBs) for Narrowband Internet
of Things (NB-IoT) devices with SIB4-NB and SIB5-NB. The SIB4-NB enhances intra-
frequency cell reselection with neighbouring and blacklist cell list. Usage of SIB5-NB with
addition of SIB3-NB allows the NB-IoT UE in RRC_IDLE mode to perform inter-frequency
reselection where neighbouring NB-IoT cells are set with different frequencies than the
active NB-IoT cell.
This feature allows encapsulation of system information (SI) messages to simplify and
reduce the traffic.

1.8.8 LTE4739 changes to the system

The LTE4739 feature changes the preemption algorithms and adds conditions to two
existing parameters.

Preemption algorithms
The LTE4739 feature changes the preemption algorithms to include Cat-M devices and
bearers and NB-IoT devices, providing the operator a configurable time limit for the
preemption duration.

Parameters
New conditions were added to existing parameters as follows:
LNBTS Activate RRC connection and SCell context preemption
(actContextPreemption)
If the LNBTS Supported LTE cell technology (supportedCellTechnology)
parameter is configured to FDD and if at least one LNCEL Cell technology
(cellTechnology) parameter is set to NB-IoT-FDD, the following condition must be
fulfilled:

42 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
The value of the LNBTS Preemption priority of pure NB-IoT RRC
connections (pureRrcPreempPrioNB) parameter is allowed to be configured to
true only if the LNBTS Activate RRC connection and SCell context
preemption (actContextPreemption) parameter value is set to true.
LNBTS Activate enhanced AC and GBR services (actEnhAcAndGbrServices)
If the LNBTS Supported LTE cell technology (supportedCellTechnology) is
configured to FDD and if at least one LNCEL_FDD Activate LTE-M feature
(actCatM) is set to true, the following condition must be fulfilled:
The value of the LNBTS Indicates if Cat-M preemption vulnerability
for DRB bearers and UE Contexts is disabled or not
(actPreempVulCatM) parameter is allowed to be configured to true only if the
LNBTS Activate enhanced AC and GBR services
(actEnhAcAndGbrServices) parameter value is set to true.

1.8.9 LTE3974 changes to the system

The LTE3974: AirScale CBRS: Support Enhanced Measurement feature introduces a new
parameter to the system.

Because the Received Signal Strength Indicator (RSSI) measurement with grant affects
service (throughput, link reputation/repetition, modulation and coding scheme (MCS)), a
parameter is introduced to allow online modification in order to perform the measurement
while an inquiry event occurs. If this parameter is enabled, at the end of one RSSI
measurement, including pre-TX, of a Citizens Broadband Radio Service Device (CBSD), the
BTS Operations and Maintenance (BTSOM) opens a timer. Before the timer expires, the
BTSOM does not perform the enhanced RSSI measurement on the CBSD, instead it uses the
latest measurement results if the CBSD needs to apply for a new grant.

The feature is activated using the newly introduced Activate the support for CBRS
Enhanced Measurement (actCbrsEnhMeas) parameter.

1.8.10 SR001933LTE3796 changes to the system

SR001933LTE3796 introduces new counters to calculate the degraded RRC success rate
and to check usage statistics of a particular recovery phase for each cell.

SR001933LTE3796 introduces the Number of Signaling Connection

Establishment Requests rejected due to OAM Intervention (M8013C122)

Issue 01D. © 2022 Nokia. Nokia Confidential Information 43

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
counter to calculate the degraded radio resource control (RRC) success rate.

SR001933LTE3796 introduces the following counters to check usage statistics of a

particular recovery phase for each cell:
Degraded RRC success rate recovery phase I (M8020C13) to determine
how many times the recovery action in Phase 1 is initiated.
Degraded RRC success rate recovery phase II (M8020C14) to determine
how many times the recovery action in Phase 2 is initiated.
Degraded RRC success rate recovery phase III (M8020C15) to determine
how many times the recovery action in Phase 3 is initiated.

1.8.11 LTE4066 changes to the system

Possible KPI changes due to the LTE4066: Low Latency Fast UL Grants feature
functionality

Enabling of R14 functionality, provided by the Activate low latency fast UL

grants(actUlTxSkip) parameter, may lead to change in UL/DL Discontinuous
Transmission (DTX) detection rate.

When Activate low latency fast UL grants(actUlTxSkip) parameter is

configured, the R14 UE may skip UL transmissions for an UL grant if no data is available for
transmission in the UE buffer. This functionality introduces some ambiguity where the eNB
shall detect the hybrid automatic repeat request (HARQ) response
(acknowledgment/negative acknowledgment(ACK/NACK)) from the UE (physical uplink shared
channel or physical uplink control channel (PUSCH or PUCCH)).

Since eNB scheduling is done with some advance, there might be cases when the evaluated
buffer state at an eNB differs from the actual buffer status report (BSR) sent over the air. As
a result, the eNB may decide to decode the signal on a different physical channel (for
example, PUSCH instead of PUCCH). The eNB housekeeping function has to deal with a
possible change in UL/DL DTX in case the eNB was not able to detect the HARQ response
(ACK/NACK) from the UE, or a PUSCH transmission was not detected.

Any lack of response for a proactive UL grant for R14 UE will have to be still treated as
“skippable” (since eNB is not aware of the real state of UE’s data buffer in a given subframe),
or it simply has an issue with a proper decoding of physical downlink control channel
(PDCCH).

The impact can be observed mainly on PDCCH allocations for PDSCH

transmissions with HARQ reporting for which eNB received no HARQ

44 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
response from UE (M8010C62) counter (PDCCH allocations for physical downlink shared
channel (PDSCH) transmissions with HARQ reporting for which eNB received no HARQ
response from the UE) and related counters.

List of impacted KPIs that might increase with the feature activated:

E-UTRAN MAC PDU Re-transmission Ratio Downlink LTE_5216a

Perc UL_SCH TB RTRANS LTE_140b
Block error ratio (BLER) in UL LTE_1553a
E-UTRAN Percentage of PUSCH transmissions using Low MCS Codes (MCS<=9)
LTE_6260a
E-UTRAN Percentage of PDSCH transmissions using Low MCS Codes (MCS<=9)
LTE_6262a
E-UTRAN Average RSSI for PUCCH LTE_5441b
E-UTRAN Average SINR for PUCCH LTE_5541b
E-UTRAN Average PRB usage per TTI UL LTE_5273b
Avg AGG PDCCH sched LTE_1084a
E-UTRAN average PRB usage per TTI DL LTE_5276b

List of impacted KPIs that might decrease with the feature activated:

Avg MCS PUSCH trans LTE_1075a

E-UTRAN Percentage of PUSCH transmissions using High MCS Codes (MCS>=20)
LTE_6261a
E-UTRAN Average SINR per Cell for PUCCH LTE_5370a
E-UTRAN Average SINR per Cell for PUSCH LTE_5371a
Average RSSI for PUSCH LTE_5444b
E-UTRAN Average SINR for PUSCH LTE_5544b
E-UTRAN Average RSSI per Cell for PUSCH LTE_5369a
E-UTRAN Average RSSI per Cell for PUCCH LTE_5368a

1.9 Changes introduced with LTE 18SP release

Impact on existing parameters (changed values, managed objects, or consistency checks),
counters, or existing functionalities and algorithms

1.9.1 LTE3687 changes to the system

Modification of UL and DL CA parameters

Issue 01D. © 2022 Nokia. Nokia Confidential Information 45

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
The following parameters are modified by the LTE3687: FDD Carrier Aggregation 2CC UL
with 4CC/5CC DL feature:
Activation of uplink carrier aggregation (actULCAggr) LNBTS
Max number of secondary cells for DL carrier aggr (maxNumScells)
LNCEL

Parameters have been modified by the change in a consistency checks to allow the support
of 4CC/5CC DL CA with 2CC UL CA.

1.9.2 LTE3870 changes to the system

LTE3870 modified several existing parameters.

LTE3870 introduces the possibility to modify several Cat-M1 related parameters online,
eliminating the need to lock/unlock the cell.

Note:

For a complete list of the parameters related to LTE3870, see LTE3870 reference
data section.

1.9.3 LTE4494 changes to the system

Description of parameters changed or introduced with the LTE4494: Cat-M1 Dynamic
Repetitions Support

Changes to existing parameters introduced with LTE4494

The existing parameter listed below is extended to a new value range n32:
CATMPR - numRepPerPreambAttemptCECatM
This parameter defines the number of PRACH repetitions per preamble attempts for Cat-
M UEs in Coverage Enhancement (CE) Level 0.

The existing parameter listed below is also extended to the new value of n32 if CATMPR
parameter numCELevelCatM is set to 2:
CATMPR - catMCELevel1/numRepPerPreambAttemptCECatM
This parameter defines the number of PRACH repetitions per preamble attempts for Cat-
M UEs in CE Level 1.

46 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
The number of MPUSCH repetitions can be configured to maximum 32 by setting the
puschMaxNumRepModeACatM parameter to r32 and the puschRepLevModeACatM
paramater to 4.

The number of MPUSCH repetitions for CE Level 1 can be configured to a maximum of 32 if

CATMPR the numCELevelCatM parameter is set to 2, by setting
puschMaxNumRepModeACatM to r32 and catMCELevel1/puschRepLevModeACatM to
n4.

Note:

If the dynamic repetition is activated on PUSCH, only the first PUSCH grant is set to
32 repetitions. The number of repetitions can vary to up to 32, depending on the
BLER or RF conditions.

1.9.4 LTE2647/SR001070 changes to the system

The LTE2647/SR001070 feature blocks the direct login access to the service account
called toor4nsn, provides a new service account called serviceuser (which is by default
visible instead), and changes the parameters used for storing the SSH keys for service
accounts. As a result, when upgrading to LTE/SRAN 18SP release, the operator must
reconfigure all credentials for service accounts, and configure a new service account
password.

Before the LTE/SRAN 18SP release, the credentials for a service account were configured
using the Service User Public Keys (serviceUserPublicKeys) parameter. The
SSH keys were applicable for the toor4nsn account. With LTE/SRAN 18SP, a new parameter
is introduced for toor4nsn: rootUserPublicKeys, while serviceUserPublicKeys
parameter is used for a new service account serviceuser. During the system upgrade, all
configured SSH keys are deleted (not migrated to a new parameter). After the upgrade, the
operator must reconfigure them manually. This can be done either using the Network
Element Manager for a particular BTS or NetAct Configurator plan file for more BTSs.

After upgrade to LTE/SRAN 18SP release, there is no default SSH key pre-configured by
Nokia. It means there is no possibility to escalate to root by default. In case Nokia Service
personnel needs to get root access for diagnosis tasks then the operator must first
configure at least one public SSH key (the access to the privileged account is possible only if
at least one key has been provisioned). The operator will not be notified by a warning of the
missing provisioning.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 47

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Additionally, after upgrade to LTE/SRAN 18SP, a new password for the serviceuser
account is added. Assuming that before the upgrade the credentials for service account
were configured as:

Login: toor4nsn

Password: operator_configured_password

then after the upgrade the credentials are changed as follows:

Login: toor4nsn

Password: operator_configured_password

(credentials configured at BTS, but not working)

Login: serviceuser

Password: default_Nokia_password

(new set of credentials)

Note:

It is an essential part of BTS hardening that the operator configures a new password
for the serviceuser account (after software upgrade or during BTS commissioning).

1.9.5 New parameter for Coordinated Multipoint and CRAN

features
In LTE18SP, a new parameter is introduced that is used to activate all Coordinated
Multipoint and CRAN features.

In releases up to LTE18SP, the Coordinated Multipoint features, that is

LTE1402: Uplink Intra-eNB CoMP
LTE1691: Uplink intra-eNB CoMP 4Rx
LTE2104: Uplink Intra eNodeB CoMP 4 RX with Softbit Combination
LTE2128: Uplink Intra eNodeB CoMP 8 RX with Softbit Combination

were activated with Active Uplink CoMP (actUlCoMp) parameter. Since release
LTE18SP, those features are activated with the new Activate CoMP (actCoMp)
parameter, which needs to be set to fixedULCoMp.

The same parameter is used with CRAN features. In CRAN deployment scenario, the

48 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
actCoMp parameter needs to be configured measBasedCoMp.

If Coordinated Multipoint and CRAN needs to be deactivated, the actCoMp parameter

needs to be configured to disabled.

1.10 Changes introduced with LTE 18 release

Impact on existing parameters (changed values, managed objects, or consistency checks),
counters, or existing functionalities and algorithms

1.10.1 LTE2839 changes to the system

LTE2839 modifies existing parameters and improves capacity and QoS

Modified parameters
Multicast channel info

mchInfo MBSFN_FDD
Multicast channel configuration per GBR QCI
Multiplicity is extended from 4 to 6
One list item for each qci value
mchInfo is a structure with multiplicity n comprising
dataMCS (0,25)
mchSchedulingPeriod
Multicast channel Scheduling period
Possible values (radioframes): 4:rf4; 8:rf8; 16:rf16; 32:rf32; 64:rf64;
128:rf128; 256:rf256; 512:rf512; 1024:rf1024
All configured mchSchedulingPeriod values must be less than or equal to
mcchRepetitionPeriod MBSFN_FDD
mbmsSyncPeriod M1SYNC must be at least twice the value of the longest
amongst all instances of mchInfo/mchSchedulingPeriod MBSFN_FDD
If mchInfo/qci is 1 or 2 or 3 or 4, the mchSchedulingPeriod cannot be set to
rf4
qci
QCI
Values added with LTE2839: 65 and 66
The qci value must be unique within all list items
Only following values are valid for qci: 1, 2, 3, 4, 65, 66

Issue 01D. © 2022 Nokia. Nokia Confidential Information 49

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Capacity improvements
With LTE2839, the maximum number of MBMS sessions per MBSFN is increased to 32 in
order to support multiple Mission Critical Push to Talk (MCPTT) group calls (using QCIs
65/66)
Maximum number of pmchs is increased to 7. In order to meet the capacity demands of
Public safety scenarios with different media, support of multiple pmchs carrying the
similar QCI type is required
Number of similar bearers of the same QCI type can be greater than 16 (current pmch
maximum), requiring additional pmch to be created to support similar bearers

Note:

Public Safety MBMS bearers and normal MBMS bearers such as QCI 1 are not
multiplexed within the same pmch

QoS improvements
Mission-Critical Push To Talk (MCPTT) Group Communication (using QCI 65/66) is
characterized by low packet delay budgets. Shorter MCH scheduling period values (<80
ms) have to be supported to ensure more frequent scheduling of related MBMS sessions
LTE2839 provides reduced minimum MCH scheduling period to rf4 (40 ms) in order to
meet the end-to-end delay and BLER for media transport for QCIs 65/66

1.10.2 LTE2927 changes to the system

The LTE2927: Changed Feature Restriction Policy for 1.4 and 3 MHz feature impacts
parameters, including their managed objects and consistency checks.

The following changes to the system have been introduced due to the The LTE2927:
Changed Feature Restriction Policy for 1.4 and 3 MHz feature:

Update of the actDLCAggr parameter consistency check

The actDLCAggr parameter can be configured to true, only if no LNCEL_FDD instance
exists with dlChBw set to 1.4 MHz or 3 MHz.

The consistency check for the actDLCAggr parameter is updated to allow downlink carrier

50 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
aggregation activation for eNBs which host the 3 MHz or 1.4 MHz bandwidth cells along with
other bandwidths. This change applies to intra-eNB and inter-eNB and inter-site carrier
aggregation scenarios, both for FDD-FDD and for FDD-TDD combinations.

Note:

1.4 MHz and 3 MHz cells cannot be used in DL CA combinations, neither as a PCell nor
as a SCell. Thus, invalid CA combinations involving 1.4 MHz and 3 MHz cells can lead to
erroneous eNB behavior

Related feature:
LTE1089: Downlink carrier aggregation - 20 MHz

Change of the actIntraFreqLoadBal parameter managed object

The LTE2927 feature moves the LTE1140 feature flag actIntraFreqLoadBal from
LNBTS to LNCEL instance. The LTE1140 feature can be activated in cells under an eNB with
mix-bandwidth (bandwidth both <5 MHz and >=5 MHz) cells. Nevertheless, it is still not
supported in 1.4 MHz/3 MHz cells.

Related feature:
LTE1140: Intra-frequency load balancing

Change of the actInterFreqLB parameter managed object

The LTE2927 feature moves the LTE1170 and the LTE1387 features flag
actInterFreqLB from LNBTS to LNCEL instance and adds support inter-frequency load
balance features in l3 MHz cell. The LTE1170 and the LTE1387 features remain restricted in
1.4 MHz cells.

Related features:
LTE1170: Inter eNode B IF Load Balancing
LTE1387: Intra-eNode B IF Load Balancing

Removed restriction of the 1.4/3 MHz cells for actDlIntShaping

The LTE2927 feature removes the restriction of 1.4/3 MHz cells for actDlIntShaping.
For 1.4/3 MHz cells, the actDlIsh parameter must be set to false and the

Issue 01D. © 2022 Nokia. Nokia Confidential Information 51

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
amountBlankedRes parameter must be set to 0.

Related feature:
LTE1800: Downlink interference shaping

Change of the actAmle parameter managed object

The LTE2927 feature moves the LTE1841 feature flag actAmle from LNBTS to LNCEL
instance. The LTE2927 feature causes the LTE1841 feature not to work in LTE1.4 MHz cells.

Related feature:
LTE1841: Inter-Frequency Load Equalization

Removed restriction of the 1.4/3 MHz cells for actCsgS1Mobility

The LTE2927 feature removes the bandwidth consistency check on the LTE2351 feature
flag actCsgS1Mobility. Previously, when the actCsgS1Mobility was set to true, the
dlChBw had to be set to: 5 MHz, 10 MHz, 15 MHz, or 20 MHz values. Now, the LTE2351
feature can be enabled in all kinds of bandwidth, including 1.4 MHz and 3 MHz cells.

Related feature:
LTE2351: S1 based handover towards CSG cells

Related parameter:
dlChBw

Changed consistency check of the act1xSrvcc parameter

The act1xSrvcc parameter can be configured to true if a CDFIM instance with the
configured csfbRegParam1xRtt parameter exists for all LNCEL instances. The LNCEL
instances cannot operate in one of the following bandwidth: 1.4 MHz and 3 MHz.
Additionally, the LTE738 feature does not work in 1.4 MHz and 3 MHz bandwidth cells.

Related feature:
LTE738: SRVCC to 1xRTT/CDMA

Related parameter:
csfbRegParam1xRtt

52 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
1.10.3 LTE3225 changes to the system
For Max. number of secondary cells for DL carrier aggr maxNumScells
parameter (maximum number of secondary cells for DL carrier aggregation) the range is set
from 1 to 4 with step value 1.

1.10.4 LTE3590 changes to the system

A new CA intra-cell handover mode (caIntraCellHoMode) parameter is
introduced.

A new MRBTS/LNBTS CA intra-cell handover mode (caIntraCellHoMode)

parameter is introduced by the LTE3590: CA and MFBI Interworking Extensions feature.

This parameter replaces, renames the MRBTS/LNBTS Activate CA steering intra-

cell handover (actCaIntraCellHo) parameter, and enhances its range.

The following intra-cell handover modes to MFBI mapped or native frequency with carrier
aggregation needs are supported:
disabled
Intra-cell handover to MFBI mapped or native frequency with CA needs is disabled.
nonCAtoCA
Intra-cell handover will be performed if there is no CA band combination supported both
by UE and eNB for current operating band of the PCell, while there are CA band
combinations supported both by UE and eNB for another operating band of the PCell.
moreDLCACapacity
This mode covers the nonCAtoCA mode. In addition to nonCAtoCA mode intra-cell
handover will be also performed if there are CA band combinations which have more
potential DL CA aggregation bandwidth supported both by UE and eNB for PCell on
another operating band than current operating band.

1.10.5 UE selection algorithms modified by LTE3757

The modifications of LB UE selection algorithms brought by LTE3757

Issue 01D. © 2022 Nokia. Nokia Confidential Information 53

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
LB UE Selection algorithm modification
This is the core functionality of LTE3757.

When a cell is overloaded the candidate UEs for offload are selected by the common UE
selection algorithm which is applied to inter frequency load balancing features. This
algorithm does not provide any option that will allow operator a prioritization in how the
eNB chooses a candidate for offload. LTE3757 covers this missing functionality.

UE selection for offload is prioritized per operator-defined SPID groups.

The mobility profiles are defined either by the SPID group or by the default profile. The
operator defines a new Mobility Profile parameter (iFLBCandPrio MOPR / MODPR). This
parameter indicates the selection priority for Connected Mode Load Balancing. The value of
the highest offload priority is the default value: 0.

When the already existing trigger for the Connected Mode Load Balancing offload is reached
then the eNB evaluates SPID groups available for UE candidate selection. The UEs belonging
to SPID groups with the highest offload priorities for Load Balancing are offloaded first and
UEs belonging to lower offload priority SPID groups are offloaded only if UEs from higher
offload priority SPID groups did not sufficiently reduce the load below the high load
threshold for LB offload.

The evaluation of SPID groups priority is done at the expiry of the operator defined timer
(iFLBCandSelUpdateTimer LNCEL). If the already existing threshold for the Connected
Mode Load Balancing (iFLBHighLoadThreshold) + operator defined cell level high-load
threshold step (iFLBHighLoadStep LNCEL) is exceeded, then the next lower offload
priority SPID group is selected. The UEs with all SPID groups selected so far are considered
for offload.

Additionally, if the load is reduced below the threshold mentioned above the SPID groups
are step-wise excluded from offload.

Active Mode Load Equalization (AMLE) UE Selection algorithm modification

There are situations when the LTE3757: SPID Based Offload UE Candidate Selection and
LTE1841: Inter-Frequency Load Equalization features are both enabled.

When a cell enters inter-frequency LB active state, the AMLE functionality is not applied.

When AMLE functionality is applied, iFLBCandPrio MOPR / MODPR of Mobility Profile

assigned to this UE = iFLBCandPrio. For AMLE, iFLBCandPrio is always set to the
highest priority for offload (that is 0). The UEs from profiles with iFLBCandPrio = 0 are
candidates for AMLE.

54 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
LB UTRAN UE selection algorithm modification
There are situations when the LTE3757: SPID Based Offload UE Candidate Selection and
LTE1357: LTE-UTRAN load balancing features are both enabled.

The UTRAN LB selection algorithm is affected in the same way as the one for LTE inter-
frequency LB. The UE is selected if UE belongs to a SPID group allowed by you to be
offloaded to UTRAN (allowLBHoToUtran MOPR / MODPR set to true)
If a UE does not belong to a SPID group allowed by you to be offloaded to UTRAN
(allowLBHoToUtran MOPR / MODPR set to false), the UE is not selected for UTRAN
offload.

Note:

This case is for FDD only as UTRAN LB is only for FDD.

1.10.6 Preemption candidate selection algorithm modified

by LTE3758
The modifications of pre-emption candidate selection algorithm brought by LTE3758

The pre-emption candidate selection algorithm is modified so that the selection is done
according to PLMN groups with certain selection order between each PLMN group.

The pre-emption candidate selection algorithm applies at cell level to E-RABs (if it was the
last E-RAB of an UE) and UE contexts (if LTE1898 is activated together with LTE3758).

This also applies at baseband level if

configured thresholds are reached

or

in case of AirScale hardware only, corresponding pool limits (see the LTE2733: Baseband
pooling feature for details) are reached.

In case of AirScale hardware the pool resources available for pre-emption are partitioned so
that only resources from cells with the same pre-emption profile as the request hosting cell
are considered valid for pre-emption. Bearers or UE contexts belonging to the same pool,
but having different cell level pre-emption profile assigned, are not subject to pre-emption

Issue 01D. © 2022 Nokia. Nokia Confidential Information 55

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
candidate selection.

1.10.7 LTE3866 changes to the system

Withdrawn band combination

With the LTE3866: Additional Carrier Aggregation Band Combinations 2CC – VI feature
released in LTE18, the support of band 5 + band 28 introduced by the release LTE17 in
LTE3047: Additional Carrier Aggregation Band Combinations 2CC – V feature is removed.

1.10.8 New Model Object Chart (MOC) introduced by

LTE4154
The modifications of Model Object Chart (MOC) brought by LTE4154

Model Object Chart (MOC) modification

The LTE4154: CA-aware Idle Mode Load Balancing II feature introduces two new Model
Object Chart (MOC) entries:

Carrier Aggregation-aware Idle Mode Load Balancing PCell

configuration (CAIMLBP)
The MOC CAIMLBP is introduced as subordinate to LNBTS-CAGENB. It is introduced to
hold PCell configuration with PCell EARFCN combination for the LTE4154: CA-aware Idle
Mode Load Balancing II feature.
The maximum number of CAIMLBP instances is 12.
Carrier Aggregation-aware Idle Mode Load Balancing SCell
configuration (CAIMLBS)
The MOC CAIMLBS is introduced as subordinate to LNBTS-CAGENB-CAIMLBP. It is
introduced to hold SCells' configurations as a structured list per number of component
carriers.
The maximum number of CAIMLBS instances per CAPLIMBP instance is 6.

1.10.9 LTE4222 changes to the system

Timer setting modification as a prevention of spurious retransmissions

Timer Reordering for DRB Cat-M (tReordDrb) parameter recommended value was

56 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
modified from 0 ms to 200 ms. This timer is used by the receiving side for data reordering,
protocol data unit (PDU) loss detection, and delay of the PDU transmission status.

Without activation of the LTE4222 feature, there is a single HARQ process, so there is no
potential spurious retransmission issue, and T-reordering (tReordDrb) timer can be
configured to 0 ms. With the LTE4222 feature activated, when the data radio bearer (DRB)
is operating under multiple HARQ processes, the mentioned T-reordering timer must be set
to a value other than 0 ms to prevent the risk of spurious retransmission.

By default, radio link control (RLC) layer initiates retransmission procedure whenever a
transmission detection gap occurs. Below the RLC, the HARQ also has its own retransmission
mechanism and when there are multiple HARQ processes, some
transmissions/retransmissions could be completed faster than the others. As a result, there
is a possibility of premature retransmission request at the RLC layer, so the T-reordering
timer is used to ensure all media access control (MAC) layer related HARQ processes have
been completed properly.

If the timer would be too short, the RLC may prematurely request a retransmission for a
PDU that is still in the HARQ retransmission process. Also the value of T-reordering timer
should not be too large because it may result in longer transmission, even in single-HARQ
transmission mode.

1.10.10 LTE4409 changes to the system

With the LTE4409: NB-IoT: Enhancements and Improved Feature Interactions (OTDOA,
FDD-TDD CA) feature introduction the LNBTS_FDD Attach without PDN
connectivity support (attachNoPDNConn) parameter range is enhanced to include
NB-IoT support.

1.10.11 LTE3865 changes to the system

Modified counter

A new description and meaning is introduced in the LTE3865 feature for the M8026C284
Number of bursts in UL counter originated from the LTE3778 feature.

Previous LTE3778 feature counter M8026C284 Number of burst in UL

implementation provided number of UL grants after SR.
Current LTE3865 feature counter M8026C284 Number of burst in UL
implementation provides the total number of data bursts in UL. The M8026C284 counter

Issue 01D. © 2022 Nokia. Nokia Confidential Information 57

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
has been modified with triggering done from received data when no previous
transmission was done for the buffered data.
In the LTE3865 feature a new M8026C286 Number of UL Grants after SR
reception counter has been created to replace previous M8026C284 counter
implementation from the LTE3778 feature.

Starting from FDD-LTE 18SP release the counters M8012C207, M8012C208, M8012C210,
M8012C211 are no longer supported. In FDD-LTE 18SP there are four new counters
introduced: M8012C216, M8012C218, M8047C17, M8047C18.

For counter descriptions, see LTE Measurements, Counters, and KPIs reference document.

1.10.11.1 Counters improvement with the LTE3865

Enhancements for all counters related to the IP scheduled throughput

With the LTE3865: Additional DL initial burst delay counters for overall traffic and CA feature,
DL and UL IP scheduled throughput related counters are improved as follows:
Maximum 10 s duration per burst is removed. The counter updates are triggered
continuously for already completed DRB data transmissions.
The DL burst data counting is triggered from the moment of reception of the HARQ
feedback for both RLC UM and RLC AM mode DRBs.
A new DL burst measurement is started in parallel with a previous burst that is still
waiting for its HARQ feedback to consider that previous burst as completed.
UL burst is detected and counted from the moment of data reception, taking into
account the HARQ retransmissions.

As a result there can be more samples which leads to a more accurate and increased value
of the data volume and transmission time counters in DL. Improved UL burst detection also
leads to a more accurate measurement data for the UL counter.

The DL data burst triggering from HARQ feedback can contribute to a higher throughput
value compared to previous releases when radio link control (RLC) retransmissions were
needed during data burst time. All RLC retransmissions which are successfully transmitted
on HARQ are counted, whereas in previous releases which used RLC triggering RLC negative
acknowledgement (NACK) transmissions were excluded from the data volume count. Parallel
DL data burst measurement can contribute to higher throughput value compared to
previous releases when more data bursts are counted in bursty data transmission for UEs in
good radio frequency conditions.

58 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Table 6: List of impacted counters and KPIs related to DL and UL IP scheduled throughput

Counter ID Counter name Corresponding KPI

M8001C135 Number of RLC SDUs on UL DTCH not used in KPI

calculation

M8001C142 UL RLC PDUs received LTE_5207b

M8006C183 ERAB_IN_SESSION_TIME_QCI3 LTE_5575a

LTE_5578a
LTE_5581a
LTE_5581b
LTE_5584a
LTE_5584b

M8006C184 ERAB_IN_SESSION_TIME_QCI4 LTE_5575a

LTE_5579a
LTE_5581a
LTE_5581b
LTE_5585a
LTE_5585b

M8006C185 ERAB_IN_SESSION_TIME_NON_GBR LTE_5575a

LTE_5580a
LTE_5581a
LTE_5581b
LTE_5586a
LTE_5586b

M8011C231 NUM_SUCC_CA_ACT_SCELL_DL not used in KPI

calculation

M8012C16 RLC_SDU_VOL_UL_DCCH not used in KPI

calculation

M8012C17 RLC PDU volume received LTE_5283a

LTE_5283b

M8012C70 MAC SDU volume on UL-DCCH not used in KPI

calculation

M8012C71 MAC SDU volume on UL-DTCH not used in KPI

calculation

M8012C79 Volume of RLC SDUs on UL-DTCH not used in KPI

calculation

M8012C117 IP Throughput volume in DL for QCI LTE_5350a

1 LTE_5503a

M8012C118 IP Throughput time in DL for QCI 1 LTE_5350a

Issue 01D. © 2022 Nokia. Nokia Confidential Information 59

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Counter ID Counter name Corresponding KPI

M8012C119 IP Throughput volume in DL for QCI LTE_5351a

2 LTE_5504a

M8012C120 IP Throughput time in DL for QCI 2 LTE_5351a

M8012C121 IP Throughput volume in DL for QCI LTE_5352a

3 LTE_5505a

M8012C122 IP Throughput time in DL for QCI 3 LTE_5352a

M8012C123 IP Throughput volume in DL for QCI LTE_5353a

4 LTE_5506a

M8012C124 IP Throughput time in DL for QCI 4 LTE_5353a

M8012C125 IP Throughput volume in DL for QCI LTE_5354a

5 LTE_5507a

M8012C126 IP Throughput time in DL for QCI 5 LTE_5354a

M8012C127 IP Throughput volume in DL for QCI LTE_5355a

6 LTE_5508a

M8012C128 IP Throughput time in DL for QCI 6 LTE_5355a

M8012C129 IP Throughput volume in DL for QCI LTE_5356a

7 LTE_5509a

M8012C130 IP Throughput time in DL for QCI 7 LTE_5356a

M8012C131 IP Throughput volume in DL for QCI LTE_5357a

8 LTE_5510a

M8012C132 IP Throughput time in DL for QCI 8 LTE_5357a

M8012C133 IP Throughput volume in DL for QCI LTE_5358a

9 LTE_5511a

M8012C134 IP Throughput time in DL for QCI 9 LTE_5358a

M8012C165 IP Throughput net time in DL for LTE_5503a

QCI 1

M8012C166 IP Throughput net time in DL for LTE_5504a

QCI 2

M8012C167 IP Throughput net time in DL for LTE_5505a

QCI 3

M8012C168 IP Throughput net time in DL for LTE_5506a

QCI 4

60 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Counter ID Counter name Corresponding KPI

M8012C169 IP Throughput net time in DL for LTE_5507a

QCI 5

M8012C170 IP Throughput net time in DL for LTE_5508a

QCI 6

M8012C171 IP Throughput net time in DL for LTE_5509a

QCI 7

M8012C172 IP Throughput net time in DL for LTE_5510a

QCI 8

M8012C173 IP Throughput net time in DL for LTE_5511a

QCI 9

M8012C187 DL nonGBR IP throughput Data Volume LTE_6178a

for UEs without CA LTE_6178a

M8012C191 DL nonGBR IP throughput time for LTE_6178a

UEs without CA LTE_6178a

M8012C209 Number of bursts with CA activity not used in KPI

in DL for nonGBR (QCIs6-9) calculation

M8012C212 Number of single TTI initialbursts not used in KPI

for nonGBR (QCIs 6-9) in DL calculation

M8012C213 Single TTI Burst Data Volume in DL not used in KPI

for nonGBR (QCIs 6-9) traffic calculation

M8012C216 Initial burst waiting for not used in KPI

scheduling applicability delay in calculation
DL PCell and one or more SCells for
nonGBR (QCIs 6-9)

M8012C218 Initial burst scheduling not used in KPI

applicability and scheduling delay calculation
in DL PCell and one or more SCells
for nonGBR (QCIs 6-9)

M8026C284 Number of Bursts in UL LTE_6285a

M8026C287 Number of Uplink Bursts for nonGBR not used in KPI

(QCIs 6-9) calculation

M8038C28 IP Throughput volume in DL for QCI1 LTE_5847a

per PLMN-ID

M8038C29 IP Throughput time in DL for QCI1 LTE_5847a

per PLMN-ID

Issue 01D. © 2022 Nokia. Nokia Confidential Information 61

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Counter ID Counter name Corresponding KPI

M8038C30 IP Throughput volume in DL for QCI2 LTE_5848a

per PLMN-ID

M8038C31 IP Throughput time in DL for QCI2 LTE_5848a

per PLMN-ID

M8038C32 IP Throughput volume in DL for QCI3 LTE_5849a

per PLMN-ID

M8038C33 IP Throughput time in DL for QCI3 LTE_5849a

per PLMN-ID

M8038C34 IP Throughput volume in DL for QCI4 LTE_5850a

per PLMN-ID

M8038C35 IP Throughput time in DL for QCI4 LTE_5850a

per PLMN-ID

M8038C36 IP Throughput volume in DL for QCI5 LTE_5851a

per PLMN-ID

M8038C37 IP Throughput time in DL for QCI5 LTE_5851a

per PLMN-ID

M8038C38 IP Throughput volume in DL for QCI6 LTE_5852a

per PLMN-ID

M8038C39 IP Throughput time in DL for QCI6 LTE_5852a

per PLMN-ID

M8038C40 IP Throughput volume in DL for QCI7 LTE_5853a

per PLMN-ID

M8038C41 IP Throughput time in DL for QCI7 LTE_5853a

per PLMN-ID

M8038C42 IP Throughput volume in DL for QCI8 LTE_5854a

per PLMN-ID

M8038C43 IP Throughput time in DL for QCI8 LTE_5854a

per PLMN-ID,

M8038C44 IP Throughput volume in DL for QCI9 LTE_5855a

per PLMN-ID

M8038C45 IP Throughput time in DL for QCI9 LTE_5855a

per PLMN-ID

M8047C0 IP Throughput volume in DL for not used in KPI

QCI/ARP dynamic profile calculation

62 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Counter ID Counter name Corresponding KPI

M8047C2 Throughput time in DL per Profile not used in KPI

calculation

M8012C91 IP Throughput volume in UL for QCI LTE_5359a

1 LTE_5512a

M8012C92 IP Throughput time in UL for QCI 1 LTE_5359a

M8012C93 IP Throughput volume in UL for QCI LTE_5360a

2 LTE_5513a

M8012C94 IP Throughput time in UL for QCI 2 LTE_5360a

M8012C95 IP Throughput volume in UL for QCI LTE_5361a

3 LTE_5514a

M8012C96 IP Throughput time in UL for QCI 3 LTE_5361a

M8012C97 IP Throughput volume in UL for QCI LTE_5362a

4 LTE_5515a

M8012C98 IP Throughput time in UL for QCI 4 LTE_5362a

M8012C99 IP Throughput volume in UL for QCI LTE_5363a

5 LTE_5516a

M8012C100 IP Throughput time in UL for QCI 5 LTE_5363a

M8012C101 IP Throughput volume in UL for QCI LTE5364a

6 LTE_5517a

M8012C102 IP Throughput time in UL for QCI 6 LTE_5364a

M8012C103 IP Throughput volume in UL for QCI LTE_5365a

7 LTE_5518a

M8012C104 IP Throughput time in UL for QCI 7 LTE_5365a

M8012C105 IP Throughput volume in UL for QCI LTE_5366a

8 LTE_5519a

M8012C106 IP Throughput time in UL for QCI 8 LTE_5366a

M8012C107 IP Throughput volume in UL for QCI LTE_5367a

9 LTE_5520a

M8012C108 IP Throughput time in UL for QCI 9 LTE_5367a

M8012C156 IP Throughput net time in UL for LTE_5512a

QCI 1

M8012C157 IP Throughput net time in UL for LTE_5513a

QCI 2

Issue 01D. © 2022 Nokia. Nokia Confidential Information 63

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Counter ID Counter name Corresponding KPI

M8012C158 IP Throughput net time in UL for LTE_5514a

QCI 3

M8012C159 IP Throughput net time in UL for LTE_5515a

QCI 4

M8012C160 IP Throughput net time in UL for LTE_5516a

QCI 5

M8012C161 IP Throughput net time in UL for LTE_5517a

QCI 6

M8012C162 IP Throughput net time in UL for LTE_5518a

QCI 7

M8012C163 IP Throughput net time in UL for LTE_5519a

QCI 8

M8012C164 IP Throughput net time in UL for LTE_5520a

QCI 9

M8026C286 Number of UL Grants after SR not used in KPI

reception calculation

M8038C10 IP Throughput volume in UL for QCI1 LTE_5856a

per PLMN-ID

M8038C11 IP Throughput time in UL for QCI1 LTE_5856a

per PLMN-ID

M8038C12 IP Throughput volume in UL for QCI2 LTE_5857a

per PLMN-ID

M8038C13 IP Throughput time in UL for QCI2 LTE_5857a

per PLMN-ID

M8038C14 IP Throughput volume in UL for QCI3 LTE_5858a

per PLMN-ID

M8038C15 IP Throughput time in UL for QCI3 LTE_5858a

per PLMN-ID

M8038C16 IP Throughput volume in UL for QCI4 LTE_5859a

per PLMN-ID

M8038C17 IP Throughput time in UL for QCI4 LTE_5859a

per PLMN-ID

M8038C18 IP Throughput volume in UL for QCI5 LTE_5860a

per PLMN-ID

M8038C19 IP Throughput time in UL for QCI5 LTE_5860a

per PLMN-ID

64 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Counter ID Counter name Corresponding KPI

M8038C20 IP Throughput volume in UL for QCI6 LTE_5861a

per PLMN-ID

M8038C21 IP Throughput time in UL for QCI6 LTE_5861a

per PLMN-ID

M8038C22 IP Throughput volume in UL for QCI7 LTE_5862a

per PLMN-ID

M8038C23 IP Throughput time in UL for QCI7 LTE_5862a

per PLMN-ID

M8038C24 IP Throughput volume in UL for QCI8 LTE_5863a

per PLMN-ID

M8038C25 IP Throughput time in UL for QCI8 LTE_5863a

per PLMN-ID

M8038C26 IP Throughput volume in UL for QCI9 LTE_5864a

per PLMN-ID

M8038C27 IP Throughput time in UL for QCI9 LTE_5864a

per PLMN-ID

M8047C1 IP Throughput data volume in UL per not used in KPI

Profile calculation

M8047C17 Number of single TTI initial bursts not used in KPI

for in DL per Profile calculation

M8047C18 Single TTI initial burst data not used in KPI

volume in DL per Profile calculation

M8047C3 IP Throughput time in UL per not used in KPI

Profile calculation

For counter descriptions, see LTE Measurements, Counters, and KPIs reference document.

Note:

The U-Plane counters are not supported with FZM one cell deployment.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 65

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Note:

Starting from FDD-LTE 18SP release the counters M8012C207, M8012C208,

M8012C210, M8012C211 are no longer supported. In FDD-LTE 18SP there are four
additional counters introduced: M8012C216, M8012C218, M8047C17, M8047C18.

66 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
2. Algorithm changes
Algorithm changes grouped per release

2.1 SRAN 21A algorithm changes

Algorithm changes for pre-SRAN 21A radio resource management features

2.1.1 LTE UL 256QAM configuration for UEs with UL

category 22 and above
Updated conditions for considering UEs for 256QAM UL

Short description
Before this change, when the actModulationSchemeUL parameter value was set to
256QAM or 256QAMand16QAMHighMCS, the UE was considered as LTE UL 256QAM capable
if the following conditions were fulfilled:
the UE has reported within its capability either the ul-256QAM-r14 IE or ul-256QAM-
perCC-r14 IE on a single component carrier within a band combination
UL UE category is within the range of 16 to 20

With this change, when the actModulationSchemeUL parameter value is set to 256QAM or
256QAMand16QAMHighMCS, the UL UE category is not checked while determining if the UE
is UL 256QAM-capable. The UE is considered as UL 256QAM-capable based on either the
ul-256QAM-r14 IE or ul-256QAM-perCC-r14 IE.

When the actModulationSchemeUL parameter value is set to 256QAM or

256QAMand16QAMHighMCS, the UL Category 22 UEs and higher can be configured with LTE
UL 256QAM.

Related features
LTE4581: 256 QAM in UL
CB006465: LTE UL 256 QAM for EN-DC-capable UEs

Issue 01D. © 2022 Nokia. Nokia Confidential Information 67

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related parameters
actModulationSchemeUL

Expected impact on performance counters

The following counter values might increase:
M8029C41…M8029C69: PUSCH transmission using MCS0…MCS28 for UE in 256QAM
Mode
M8029C70…M8029C98: PUSCH transmission nacks using MCS0…MCS28 for UE in
256QAM Mode
M8029C99…M8029C127: Number of failed PUSCH transmission using MCS0…MCS28 for
UE in 256QAM Mode
M8029C128…M8029C156: First PUSCH transmission using MCS0…MCS28 for UE in
256QAM Mode
M8029C157…M8029C185: First PUSCH transmission nacks using MCS0…MCS28 for UE in
256QAM Mode
M8012C226…M8012C254: MAC PDU volume on PUSCH using MCS0…MCS28 for UE in
256QAM Mode

The following counter values might decrease:

M8029C186…M8029C189: PUSCH transmission using MCS21…MCS24 64QAM for UE not
in 256QAM Mode
M8029C190…M8029C193: PUSCH transmission nacks using MCS21…MCS24 64QAM for
UE not in 256QAM Mode
M8029C194…M8029C197: Failed PUSCH transmission using MCS21…MCS24 64QAM for
UE not in 256QAM Mode
M8029C198…M8029C201: First transmissions on PUSCH using MCS21…MCS24 64QAM
for UE not in 256QAM Mode
M8029C202…M8029C205: First transmissions NACKs on PUSCH using MCS21…MCS24
64QAM for UE not in 256QAM Mode
M8012C255…M8012C258: MAC PDU volume PUSCH using MCS21…MCS24 64QAM for UE
not in 256QAM Mode

The following KPI values might increase:

LTE_6668a E-UTRAN RRC Connection Reconfiguration Success Ratio for downgrade from
256QAM table in UL based on channel quality monitoring
LTE_6669a E-UTRAN RRC Connection Reconfiguration Success Ratio for upgrade to

68 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
256QAM table in UL based on channel quality monitoring
LTE_6728a Total UL scheduled session duration of 256QAM-scheduled UEs

The following KPI values might change depending on the traffic model in a particular
network:
LTE_5207b E-UTRAN RLC PDU Re-transmission Ratio Uplink
LTE_5444b E-UTRAN Average RSSI for PUSCH
LTE_5544b E-UTRAN Average SINR for PUSCH
LTE_5369a E-UTRAN Average RSSI per Cell for PUSCH
LTE_5371a E-UTRAN Average SINR per Cell for PUSCH
LTE_5310b E-UTRAN PDCP SDU Loss Ratio in the UL
LTE_5311b…LTE_5314b, LTE_5455a…LTE_5459a E-UTRAN PDCP SDU Loss Ratio in the
UL, QCI1…QCI9
LTE_6268a E-UTRAN Percentage of UEs with available Uplink Power
LTE_6260a E-UTRAN Percentage of PUSCH transmissions using Low MCS Codes (MCS<=9)
LTE_6261a E-UTRAN Percentage of PUSCH transmissions using High MCS Codes
(MCS>=20)

The following KPI values might increase (the performance depends on the traffic model in
the particular network):
LTE_5289d E-UTRAN average PDCP Layer Active Cell Throughput UL
LTE_5283b E-UTRAN average RLC Layer Cell Throughput UL

The following KPI values might change (the performance depends on the traffic model in the
particular network):
LTE_5213a E-UTRAN PDCP SDU Volume UL
LTE_5810a E-UTRAN RLC PDU Volume UL
LTE_6015a E-UTRAN RLC PDU Volume UL via SCell
LTE_6183a E-UTRAN RLC PDU Volume UL via PCell
LTE_5846a E-UTRAN PDCP SDU User Volume UL per PLMN
LTE_7175a E-UTRAN PCell RLC data volume in UL via specific SCell per PCell-SCell relation

The following KPI values might increase (the performance depends on the traffic model in
the particular network):
LTE_5359a…LTE_5367a E-UTRAN Averaged IP scheduled Throughput in UL, QCI1…QCI9
LTE_5512a…LTE_5520a E-UTRAN Averaged IP Throughput in UL, QCI1…QCI9
LTE_5856a…LTE_5864a E-UTRAN Averaged IP scheduled Throughput in UL, QCI1…QCI9,
PLMN

Issue 01D. © 2022 Nokia. Nokia Confidential Information 69

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
The following KPI values might change (the performance depends on the traffic model in the
particular network):
LTE_5273b E-UTRAN average PRB usage per TTI UL
LTE_8075a E-UTRAN minimum PRB usage per TTI UL
LTE_8076a E-UTRAN maximum PRB usage per TTI UL
LTE_8077a E-UTRAN average PRB usage per TTI UL per PLMN
LTE_8078a E-UTRAN minimum PRB usage per TTI UL per PLMN
LTE_8079a E-UTRAN maximum PRB usage per TTI UL per PLMN
LTE_6353a E-UTRAN PRB usage ratio for CA related traffic of PCell UEs in UL
LTE_6354a E-UTRAN PRB usage ratio for CA related traffic of SCell UEs in UL
LTE_6355a E-UTRAN PRB usage ratio for nonCA related traffic in UL
LTE_5801e E-UTRAN Average Active UEs with data in the buffer UL
LTE_5807d E-UTRAN Average Active UEs with data in the buffer for QCI1 DRBs per cell UL
LTE_5808d E-UTRAN Average Active UEs with data in the buffer for non-GBR DRBs UL
LTE_6847a E-UTRAN Average Active UEs with data in the buffer UL for QCI1 DRBs per
PLMN
LTE_6848a E-UTRAN Average Active UEs with data in the buffer UL for non-GBR DRBs per
PLMN
LTE_5803b E-UTRAN Maximum Active UEs with data in the buffer per cell UL
LTE_5804c E-UTRAN Average Active Connected UEs
LTE_5214b E-UTRAN Maximum of Average Active Connected UEs
LTE_6020a E-UTRAN Maximum Number of Active UEs per eNB
LTE_6245a E-UTRAN Maximum Number of Active UEs per cell
LTE_6621a E-UTRAN Average Number of CA UEs with Configured SCell in SCell
LTE_6622a E-UTRAN Maximum Number of CA UEs with Configured SCell in SCell
LTE_5838b E-UTRAN Average UEs with Configured one SCell in UL
LTE_5837b E-UTRAN Average UEs with an Activated SCell in UL
LTE_7173a E-UTRAN Average number of CA UEs with configured UL CA per PCell-SCell
relation
LTE_5748a UL Spectral efficiency

The counter values used to calculate the KPIs listed above might change accordingly.

2.1.2 Updating radio quality counters (SINR/RSSI) when

unreliable DTX transmission from UEs occurs
Before the change, the counter values were updated during discontinuous transmission
(DTX). After the change, they are not updated in such scenario.

70 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related features

Note:

This change was introduced from the following software releases onwards:
SBTS20B_ENB_0000_002016_000000
SBTS20C_ENB_0000_001808_000000
SBTS21A_ENB_0000_000842_000000

So you might notice the change in 20B, 20C, or 21A release depending on what
software version is in use.

LTE798: Performance Counter Histogram Package I

LTE651: Performance Monitoring I

Related parameters
There are no related parameters.

Expected impact on performance counters

The following counters are no longer updated during DTX. The counter impact might not be
visible in good radio conditions. In other cases, the following counter value changes can be
observed:
Increase:
M8005C0: RSSI for PUCCH Min
M8005C2: RSSI for PUCCH Mean
M8005C3: RSSI for PUSCH Min
M8005C5: RSSI for PUSCH Mean
M8005C90: SINR for PUCCH Min
M8005C92: SINR for PUCCH Mean
M8005C93: SINR for PUSCH Min
M8005C95: SINR for PUSCH Mean
Depending on the traffic mix, the level counters distribution might move to higher levels:
M8005C6 - M8005C27: RSSI for PUCCH Level 01 - Level 22
M8005C28 - M8005C49: RSSI for PUSCH Level 01 - Level 22
M8005C96 - M8005C117: SINR for PUCCH Level 1 - Level 22
M8005C118 - M8005C139: SINR for PUSCH Level 1 - Level 22

Issue 01D. © 2022 Nokia. Nokia Confidential Information 71

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
The following counters should not change, or the change will be minimal:
M8005C1: RSSI for PUCCH Max
M8005C4: RSSI for PUSCH Max
M8005C91: SINR for PUCCH Max
M8005C94: SINR for PUSCH Max

2.2 SRAN 20C algorithm changes

Algorithm changes for pre-SRAN 20C radio resource management features

2.2.1 Improvement in UL SCell deconfiguration algorithm

Prior to this change, the eNB didn't give UL grants to UE after releasing a UL secondary
cell (SCell). The change fixes UL traffic resumption on the primary cell after a UL SCell has
been released.

Related features
LTE3303: Enhanced VoLTE, CA, and RF Quality Monitoring
LTE1092: Uplink Carrier Aggregation – 2CC

Related parameters
The LNBTS Activation of uplink carrier aggregation (actULCAggr)
parameter set to true

Expected impact on performance counters

.
The LTE_6126a E-UTRAN SCell Deconfiguration Success Ratio in DL key
performance indicator (KPI) value is increased.

The M8011C214 Downlink CA Deconfiguration Successes counter value is

increased.

The following KPI values might decrease:

LTE_6161a RRC Connection Re-establishment Attempts per type total

72 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
attempts
LTE_5142a RRC Connection Re-establishment Attempts, other fails

2.3 SRAN 20B algorithm changes

Algorithm changes for pre-SRAN 20B radio resource management features

2.3.1 SCell channel quality estimation for UEs configured

with LTE 256QAM in downlink
Improved algorithm for scellNotDetectableThr and scellBadChQualThr
parameters.

Short description
When the UE is configured with DL 256QAM, the scellNotDetectableThr and
scellBadChQualThr parameters are converted internally in the eNB to the modified
Modulation and Coding Scheme (MCS) table applied for 256QAM modulation.

Before this change, when both parameter values were set to 1, they were internally
converted to 0, which did not allow to release the SCell due to undetected or bad channel
quality respectively. Such system behavior was not fulfilling operators' requirements.

With this change, if both parameter values are set to 1, they remain unchanged for the UE
configured with DL 256QAM. Therefore, the SCell channel quality estimation algorithm may
still detect an ‘undetected SCell’ or a ‘SCell with bad channel quality’ for such UE.

If the actModulationSchemeDl parameter value is set to 256QAM, the UE is configured

with DL 256QAM, and the scellNotDetectableThr parameter value is set to 1, then it
should be possible to detect an ‘undetected SCell’ and release this SCell.

If the actModulationSchemeDl parameter value is set to 256QAM, the UE is configured

with DL 256QAM, the scellBadChQualThr parameter value is set to 1, and the
scellNotDetectableThr parameter value is set to 0, then it should be possible to detect
the SCell with bad channel quality and initiate the SCellReleaseTimer for ‘bad channel
quality’ (the SCellReleaseTimer is based on multScellReleaseTimer and
sCellDeactivationTimereNB parameter settings).

Issue 01D. © 2022 Nokia. Nokia Confidential Information 73

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related features
LTE2479: 256QAM in Downlink
LTE3073: 256 QAM Extensions
LTE1541: Advanced SCell Measurement Handling

Related parameters
Threshold for a not detectable Scell (scellNotDetectableThr)
Threshold for a SCell detected - bad channel quality
(scellBadChQualThr)

Expected impact on performance counters

If the scellNotDetectableThr or the scellBadChQualThr parameters are set to 1,
then for DL 256QAM configured UEs, the counter and KPI values might be impacted as
follows.

The following counter values might increase:

M8011C213: Downlink CA Deconfiguration Attempts
M8011C214: Downlink CA Deconfiguration Successes

The following KPI values can be impacted by the counters listed above:
LTE_6167a: E-UTRAN SCell Deconfiguration Attempts in DL might increase
LTE_6126a: E-UTRAN SCell Deconfiguration Success Ratio in DL might
change

The following KPI values might decrease (related counters might change accordingly):
LTE_6842a: Residual Block Error Rate (rBLER) in DL
LTE_6843b: Residual Block Error Rate (rBLER) in UL

DL BLER and UL BLER might decrease.

2.3.2 DSS dynamic sharing ratio changes

Protection of NR Discontinuous Reception (DRX), especially 6 or 10 ms duration values
(instead of 20 ms)

74 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Short description
This change impacts the DSS with low NR traffic and medium LTE traffic as follows:
The LTE gets fewer resources to protect NR DRX, especially to have the duration of the
DRX timer (drxOnDuratT) set for 6 or 10ms instead of 20 ms.
LTE gets less than 90% resources (for example, 70% but this can be dynamically changed
with load reported by each RAT) and with growing LTE traffic the LTE goes dynamically to
90% of all radio resources.

Without this change the behavior of DSS with low NR traffic and medium LTE traffic is as
follows:

LTE always gets approximately 90% of the resources (proportional assignment of the
current usage of both RATs).
With growing NR traffic, the LTE share is lowered (proportionally to the usage).
When there is no NR traffic, LTE share will dynamically go back to 90%.
With growing LTE traffic, LTE can't get more because it is already at 90% of possible
resources.

Related features
LTE5407: LTE-NR Dynamic Spectrum Sharing Phase I

Related parameters
DRX on duration timer (drxOnDuratT)

Expected impact on performance counters

Counters related to PRB usage can be impacted. When LTE load is low or medium, the
M8001C216: Average number of available PRBs per TTI on PDSCH counter
value can decrease. When LTE load is high, the value should be comparable with the value
before the introduction of this change.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 75

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
2.3.3 Improvements in counter aggregation algorithm
when Real-Time Performance Monitoring (RT PM)
framework is activated
Propagation of rounding errors during the additional aggregation necessary to obtain the
standard, non-real-time performance monitoring counter values is minimized.

Short description
In the RT PM framework, the standard counter values are recreated from their 60-second
intermediate values by additional aggregation. Improvements to the aggregation algorithm
have been introduced. These improvements might lead to small value changes of counters
with a logical type "average". When it is necessary to obtain counter values with
measurement periods smaller than 15 minutes, as for instance in case of sleeping cell
detection features, the RT PM is activated indirectly in the BTS.

Related features
LTE1053: Real-time KPI-monitoring with Traffica
LTE2054: Measurement Report addition with PDCP KPI counter subset
LTE3796/SR001933: Automatic Sleeping Cell Detection and Recovery
LTE4560/SR002240: RX Power and Traffic Based Sleeping LTE Cell Detection
LTE4972: Actual EIRP Control for Non-Beamforming Cells

Related parameters
There are no related parameters.

Expected impact on performance counters

Counters that have logical type "average" might show different values compared to values
shown when the RT PM framework was not activated. This deviation is expected to be small,
between (-1,+1).

76 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
2.3.4 The correction of relative instantaneous channel
quality calculation
Relative instantaneous channel quality (RICQ) calculation is corrected when channel
quality indicator reports are received with invalid resource block groups.

Short description
Calculated RICQ is used to calculate the modulation and coding scheme (MCS). Before the
correction of RICQ calculation, while calculating average relative RICQ, there was a variable
which was unsigned __int32 but kept getting assigned a negative value from the
calculation. Due to this, the variable was assigned a very large integer value. The variable was
then used to calculate average RICQ, eventually leading to MCS being calculated as a high
value. High RICQ average calculation could lead to too high MCS, and as a result it could
cause a negative Hybrid Automatic Repeat Request feedback.

With the correction of RICQ calculation, there might be a certain shift in the MCS distribution
from higher MCS levels towards lower MCS levels. Over time, the average MCS can decrease.

Related features
LTE651: Performance Monitoring I
LTE2479: 256 QAM in Downlink

Related parameters
There are no related parameters.

Expected impact on performance counters

The following changes in counter values can be observed (increase/decrease):
M8001C45 First transmissions on PUSCH using MCS21
M8001C73 PDSCH transmissions using MCS28
M8001C236 PDSCH transmissions using MCS29
M8001C238 PDSCH transmissions using MCS31
M8011C196 PDSCH transmission using QPSK of 256QAM-scheduled UE
M8011C199 PDSCH transmission using 256QAM of 256QAM-scheduled UE

The following changes in key performance indicators values can be observed

Issue 01D. © 2022 Nokia. Nokia Confidential Information 77

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
(increase/decrease):
LTE_6263b E-UTRAN Percentage of PDSCH transmissions using High MCS
Codes (MCS>=20)
LTE_6262a E-UTRAN Percentage of PDSCH transmissions using Low MCS
Codes (MCS<=9

2.4 SRAN 20A algorithm changes

Algorithm changes for SRAN 20A system

2.4.1 Calculation of load, Composite Available Capacity

(CAC), and Normalized Load Compare Value (NLCV)
The calculation method is changed with the activation of Effective Isotropic Radiated
Power (EIRP) control.

Short description
With the EIRP control activated, the Physical Resource Block (PRB) usage for Cat-M and NB-
IoT also adds to the calculation the number of used/available PRBs. There is a side effect for
the neighbor cells (for example, PCell/SCell candidates, load balancing handover targets, or
other recipients of load-related data) which are not under EIRP control and calculate the
load/CAC/NLCV with the legacy method.

EIRP is generated from all transmissions in the cell, including NB-IoT (inband, guardband) and
Cat-M, therefore it must be respectively considered. For other purposes, either NB-IoT/Cat-
M can be neglected, or it can be assumed that the target/recipient cell has the same feature
composition.

The handover levels are changed and the load metrics are calculated in a different way
compared to:
previous releases
target/recipient cells without the EIRP control

To ensure that the same load metrics are used:

activate the EIRP control in all relevant cells
set the eirpReduction parameter value to 0 if a cell shall use the new calculation
method but has no EIRP reduction

78 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related features
LTE4972: Actual EIRP control in LTE for non-beamforming cells

Related parameters
Activate EIRP Control (actEirpControl)
EIRP reduction (eirpReduction)

Expected impact on performance counters

There are no related counters.

2.4.2 Possible counter value changes for IP throughput

and corresponding time/net time
Algorithms for IP throughput, related time and net time calculation are more precise.

Short description
The current algorithms used for IP throughput counters, related time and net time
calculations were modified to give more precise values. Therefore, depending on the
configuration, the corresponding counter values might increase or decrease few percent.

Related features
There are no related features.

Related parameters
There are no related parameters.

Expected impact on performance counters

The following counter values might change:
M8012C91 IP Throughput volume in UL for QCI 1
M8012C92 IP Throughput time in UL for QCI 1

Issue 01D. © 2022 Nokia. Nokia Confidential Information 79

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
M8012C93 IP Throughput volume in UL for QCI 2
M8012C94 IP Throughput time in UL for QCI 2
M8012C95 IP Throughput volume in UL for QCI 3
M8012C96 IP Throughput time in UL for QCI 3
M8012C97 IP Throughput volume in UL for QCI 4
M8012C98 IP Throughput time in UL for QCI 4
M8012C99 IP Throughput volume in UL for QCI 5
M8012C100 IP Throughput time in UL for QCI 5
M8012C101 IP Throughput volume in UL for QCI 6
M8012C102 IP Throughput time in UL for QCI 6
M8012C103 IP Throughput volume in UL for QCI 7
M8012C104 IP Throughput time in UL for QCI 7
M8012C105 IP Throughput volume in UL for QCI 8
M8012C106 IP Throughput time in UL for QCI 8
M8012C107 IP Throughput volume in UL for QCI 9
M8012C108 IP Throughput time in UL for QCI 9
M8012C117 IP Throughput volume in DL for QCI 1
M8012C118 IP Throughput time in DL for QCI 1
M8012C119 IP Throughput volume in DL for QCI 2
M8012C120 IP Throughput time in DL for QCI 2
M8012C121 IP Throughput volume in DL for QCI 3
M8012C122 IP Throughput time in DL for QCI 3
M8012C123 IP Throughput volume in DL for QCI 4
M8012C124 IP Throughput time in DL for QCI 4
M8012C125 IP Throughput volume in DL for QCI 5
M8012C126 IP Throughput time in DL for QCI 5
M8012C127 IP Throughput volume in DL for QCI 6
M8012C128 IP Throughput time in DL for QCI 6
M8012C129 IP Throughput volume in DL for QCI 7
M8012C130 IP Throughput time in DL for QCI 7
M8012C131 IP Throughput volume in DL for QCI 8
M8012C132 IP Throughput time in DL for QCI 8
M8012C133 IP Throughput volume in DL for QCI 9
M8012C134 IP Throughput time in DL for QCI 9
M8012C156 IP Throughput net time in UL for QCI 1
M8012C157 IP Throughput net time in UL for QCI 2
M8012C158 IP Throughput net time in UL for QCI 3
M8012C159 IP Throughput net time in UL for QCI 4
M8012C160 IP Throughput net time in UL for QCI 5

80 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
M8012C161 IP Throughput net time in UL for QCI 6
M8012C162 IP Throughput net time in UL for QCI 7
M8012C163 IP Throughput net time in UL for QCI 8
M8012C164 IP Throughput net time in UL for QCI 9
M8012C165 IP Throughput net time in DL for QCI 1
M8012C166 IP Throughput net time in DL for QCI 2
M8012C167 IP Throughput net time in DL for QCI 3
M8012C168 IP Throughput net time in DL for QCI 4
M8012C169 IP Throughput net time in DL for QCI 5
M8012C170 IP Throughput net time in DL for QCI 6
M8012C171 IP Throughput net time in DL for QCI 7
M8012C172 IP Throughput net time in DL for QCI 8
M8012C173 IP Throughput net time in DL for QCI 9

2.4.3 Improper handling of the ring buffer wraparound

IP throughput related counters are more accurate in case of an RLC segmentation.

Short description
This change is fixing the problem related to 'CDlSegmentedSduInfoStorage' index
wraparound. In some scenarios the function responsible for setting the reference to a
segment improperly handled the ring buffer wraparound. This caused the segment
references to disappear.

Related features
There are no related features.

Related parameters
There are no related parameters.

Expected impact on performance counters

If the segmentation occurs, the following counter values might increase:
M8012C117 IP Throughput volume in DL for QCI 1

Issue 01D. © 2022 Nokia. Nokia Confidential Information 81

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
M8012C119 IP Throughput volume in DL for QCI 2
M8012C121 IP Throughput volume in DL for QCI 3
M8012C123 IP Throughput volume in DL for QCI 4
M8012C125 IP Throughput volume in DL for QCI 5
M8012C127 IP Throughput volume in DL for QCI 6
M8012C129 IP Throughput volume in DL for QCI 7
M8012C131 IP Throughput volume in DL for QCI 8
M8012C133 IP Throughput volume in DL for QCI 9
M8038C28 IP Throughput volume in DL for QCI1 per PLMN-ID
M8038C30 IP Throughput volume in DL for QCI2 per PLMN-ID
M8038C32 IP Throughput volume in DL for QCI3 per PLMN-ID
M8038C34 IP Throughput volume in DL for QCI4 per PLMN-ID
M8038C36 IP Throughput volume in DL for QCI5 per PLMN-ID
M8038C38 IP Throughput volume in DL for QCI6 per PLMN-ID
M8038C40 IP Throughput volume in DL for QCI7 per PLMN-ID
M8038C42 IP Throughput volume in DL for QCI8 per PLMN-ID
M8038C44 IP Throughput volume in DL for QCI9 per PLMN-ID
M8103C27 PDCP SDU data volume successfully transmitted on eUu
interface in downlink (LTE-M)
M8103C28 PDCP SDU data volume successfully transmitted on eUu
interface in downlink (LTE-M CE level 0)
M8103C29 PDCP SDU data volume successfully transmitted on eUu
interface in downlink (LTE-M CE level 1)
M8103C30 PDCP SDU data volume successfully transmitted on eUu
interface in downlink (LTE-M CE level 2)
M8103C31 PDCP SDU data volume successfully transmitted on eUu
interface in downlink (LTE-M CE level 3)
M8047C0 IP Throughput data volume in DL per Profile

The following counter values might increase, but only in specific scenarios that might occur
rarely:
M8012C118 IP Throughput time in DL for QCI 1
M8012C120 IP Throughput time in DL for QCI 2
M8012C122 IP Throughput time in DL for QCI 3
M8012C124 IP Throughput time in DL for QCI 4
M8012C126 IP Throughput time in DL for QCI 5
M8012C128 IP Throughput time in DL for QCI 6
M8012C130 IP Throughput time in DL for QCI 7
M8012C132 IP Throughput time in DL for QCI 8

82 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
M8012C134 IP Throughput time in DL for QCI 9
M8012C165 IP Throughput net time in DL for QCI 1
M8012C166 IP Throughput net time in DL for QCI 2
M8012C167 IP Throughput net time in DL for QCI 3
M8012C168 IP Throughput net time in DL for QCI 4
M8012C169 IP Throughput net time in DL for QCI 5
M8012C170 IP Throughput net time in DL for QCI 6
M8012C171 IP Throughput net time in DL for QCI 7
M8012C172 IP Throughput net time in DL for QCI 8
M8012C173 IP Throughput net time in DL for QCI 9
M8012C261 IP Throughput net time in DL for QCI 65
M8012C262 IP Throughput net time in DL for QCI 66
M8038C29 IP Throughput time in DL for QCI1 per PLMN-ID
M8038C31 IP Throughput time in DL for QCI2 per PLMN-ID
M8038C33 IP Throughput time in DL for QCI3 per PLMN-ID
M8038C35 IP Throughput time in DL for QCI4 per PLMN-ID
M8038C37 IP Throughput time in DL for QCI5 per PLMN-ID
M8038C39 IP Throughput time in DL for QCI6 per PLMN-ID
M8038C41 IP Throughput time in DL for QCI7 per PLMN-ID
M8038C43 IP Throughput time in DL for QCI8 per PLMN-ID
M8038C45 IP Throughput time in DL for QCI9 per PLMN-ID
M8047C2 IP Throughput time in DL per Profile
M8103C22 PDCP time for successful transmissions in downlink (LTE-
M)
M8103C23 PDCP time for successful transmissions in downlink (LTE-M
CE level 0)
M8103C24 PDCP time for successful transmissions in downlink (LTE-M
CE level 1)
M8103C25 PDCP time for successful transmissions in downlink (LTE-M
CE level 2)
M8103C26 PDCP time for successful transmissions in downlink (LTE-M
CE level 3)

If any of the M8103C27 - M8103C31 counter values increase, it results in bins counters
value change:
M8105C30...M8105C38 (User Throughput in DL bin 1 (LTE-M)...User
Throughput in DL bin 9 (LTE-M))

Issue 01D. © 2022 Nokia. Nokia Confidential Information 83

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
2.4.4 HARQ release with default previous HARQ state in
AM mode
HARQ related counters are more accurate as a result of proper handling of the HARQ
release with HARQ state NACK. Before this change, the state did not matter in the AM
mode.

Short description
The HARQ release performed via the 'TxCompletion' event requires information about the
previous HARQ state (final ACK/NACK). This information is passed to 'RlcCoreDl' from MAC PS
via 'SPduMuxDataCombReq' ('newDataIndicator' field) and next to RlcSupportDl. In the UM
mode the information about previous HARQ state is passed to RlcSupportDl properly but for
AM mode this info is not passed. This change aims to correct this problem.

Related features
There are no related features.

Related parameters
There are no related parameters.

Expected impact on performance counters

The following counter values might be impacted:
M8026C33 Average HARQ transmission time for TBs with QCI 4 data
M8026C34 Average HARQ transmission time for TBs with QCI 5 data
M8026C35 Average HARQ transmission time for TBs with QCI 6 data
M8026C36 Average HARQ transmission time for TBs with QCI 7 data
M8026C37 Average HARQ transmission time for TBs with QCI 8 data
M8026C38 Average HARQ transmission time for TBs with QCI 9 data

84 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
2.4.5 Update of legacy fixed FDD UL CoMP solution
The architecture of fixed FDD Co-ordinated Multipoint (CoMP) features (LTE1402,
LTE1691) is aligned with the flexible approach. This change might impact some counter
and KPI values for FDD cells.

Short description
For maintenance reasons, the fixed FDD UL CoMP solution is harmonized with flexible UL
CoMP. Fixed UL CoMP is used when the actCoMp parameter is set tofixedULCoMp value.
From 20A onwards, the implementation is updated and aligned with the actCoMp =
measBasedCoMp setting. Small impact on the amount of UL CoMP might be seen.

Related features
LTE1402: Uplink Intra-eNB CoMP
LTE1691: Uplink intra-eNB CoMP 4Rx

Related parameters
Activate CoMP (actCoMp)

Expected impact on performance counters

The following counter and KPI values might change (increase or decrease):
M8051C119 Average number of UEs using UL intra-eNB CoMP
LTE_5403c E-UTRAN Average number of UEs utilizing UL intra-eNB
CoMP
LTE_5749b Percentage of UEs using CoMP in the cell

2.5 LTE 19B algorithm changes

Algorithm changes for LTE 19B system

Issue 01D. © 2022 Nokia. Nokia Confidential Information 85

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
2.5.1 Potential cell load increase with the LTE5731: TCP
Service Differentiation feature activated
Configuration of dedicated non-GBR QCI and operator-specific QCI bias factors in UL and
DL allows prioritization of the UE transmission.

Short description
The LTE5731: TCP Service Differentiation feature improves the data transfer in DL and UL by
boosting the amount of resources assigned to data radio bearers (DRB) with the
Transmission Control Protocol (TCP) traffic.

Related features
LTE5731: TCP Service Differentiation

Related parameters
MRBTS/LNBTS/LNCEL Activate TCP Service Differentiation
(actTcpServiceDiff)

Related counters
In certain scenarios, the configured UL and DL bias factor might result in activating the cell
off-loading mechanisms. This situation results in the M8021C23 Number of load
balancing Handover attempts counter value increase.

2.5.2 Prioritization of the optional power group over the

mandatory power group for baseband pool allocation
With this change the baseband pool allocation is now prioritized on the optional group
(also known as second power group PG#2) instead of the mandatory one. This allows the
BTS to reserve mandatory power group for potential GSM deployment.

Related features
LTE2733: Baseband Pooling

86 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related parameters
There are no related parameters.

Expected impact on performance counters

There are no related counters.

2.5.3 Introduction of Resource Allocation Type (RAT) 1

Supporting RAT 1 results in a reduced inter-cell interference and an optimized downlink
Physical Resource Block (PRB) utilization for services with small transport block size
allocations.

Related features
LTE1118: Resource Allocation Type 1

Related parameters
There are no related parameters.

Expected impact on performance counters

The following counter values might increase:
M8011C311: Total number of PRBs used for Resource Allocation Type
1 (RAT1) scheduling
M8012C20: PDCP SDU data volume on eUu Interface downlink
M8012C179: Average achievable MAC PDU Throughput in Downlink per
Cell
M8012C80: RLC SDU DL-DTCH volume
M8012C181: Average achievable MAC PDU Throughput in Uplink per
Cell
M8012C183: Average achievable MAC PDU throughput in Downlink per
User
M8012C184: Maximum achievable MAC PDU throughput in Downlink per
User

Issue 01D. © 2022 Nokia. Nokia Confidential Information 87

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
2.5.4 Enabling Cyclic PUCCH Allocation algorithm will
consider the setting of maxNumCaConfUe3c or
maxNum2CCUeWithPF3
The enabling status of Cyclic PUCCH Allocation (CPA) algorithm checks if the
maxNum2CCUeWithPF3 or maxNumCaConfUe3c parameter value is greater than 20 or
not. If yes, CPA algorithm will be enabled, otherwise, CPA algorithm will not be enabled.

Description
Up to LTE/SRAN 18A, the M8011C167: blocking rate for SCell scheduling
with PUCCH format 3 counter isn't increased, if maxNumCaConfUe3c is set to a value
not larger than 20.

Since LTE/SRAN 19B, with the introduction of the LTE5194: TDD-FDD SDLC DL carrier
aggregation 4CC feature, 2CC UE can also be configured with PUCCH format 3 (PF3),
meaning, 2CC/3CC/4CC/5CC can share the same PF3 resource pool. Therefore, the enabling
status of CPA algorithm and the PF3 PRB allocation algorithm should also consider the
setting of maxNum2CCUeWithPF3.

The PF3 PRB number will be allocated as per the setting of the sum of
maxNum2CCUeWithPF3 and maxNumCaConfUe3c as follows:
If CPA algorithm is disabled:
1 PF3 PRB for "maxNum2CCUeWithPF3 + maxNumCaConfUe3c" [1,5]
2 PF3 PRB for "maxNum2CCUeWithPF3 + maxNumCaConfUe3c" [6,10]
3 PF3 PRB for "maxNum2CCUeWithPF3 + maxNumCaConfUe3c" [11,15]
4 PF3 PRB for "maxNum2CCUeWithPF3 + maxNumCaConfUe3c" [16,20]
If CPA algorithm is enabled:
1 PF3 PRB for "maxNum2CCUeWithPF3 + maxNumCaConfUe3c" [21,24]
2 PF3 PRB for "maxNum2CCUeWithPF3 + maxNumCaConfUe3c" [25,50]

Related features
LTE5194: TDD-FDD SDLC DL Carrier Aggregation 4CC
LTE2179: TDD Downlink Carrier Aggregation 4CC - 80Mhz

88 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related parameters
LNCEL_TDD Max. number of 2CC CA UEs with PUCCH format 3
(maxNum2CCUeWithPF3)
LNCEL_TDD Max number carrier aggr configured UEs 3 carriers
(maxNumCaConfUe3c)

Related counters
M8011C167: blocking rate for SCell scheduling with PUCCH format 3

2.6 LTE19A algorithm changes

Algorithm changes for LTE 19A system

2.6.1 LTE19A common algorithm changes

2.6.1.1 Improved SCell handling when moving from bad to

good channel conditions
This change aims at reducing the scheduling delay and the probability of unnecessary
secondary cell (SCell) releases.

Short description
When the channel status equals either 'bad' or 'undetected' (during the SCell channel quality
estimation), the eNB will gradually reduce (age) the delta CQI received from DL link
adaptation. This aging is performed in each consecutive SCell channel quality estimation
period during which the channel status is bad or undetected until a configurable target delta
CQI is reached.

When the signal quality improves and if a negative delta CQI is gradually reduced during the
channel quality estimation, the eNB will likely transition the SCell channel status to good
faster than in the original implementation (when the original delta CQI was used for the
entire period of channel quality estimation).

Issue 01D. © 2022 Nokia. Nokia Confidential Information 89

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related features
LTE1541 Advanced SCell measurement handling

Related parameters
Activate delta CQI aging in SCell channel estimation
(actDeltaCqiAgingScellChEst)
Activate advanced SCell measurement handling (actAdvScellMeas)
Activation of downlink carrier aggregation(actDLCAggr)
Delta CQI target value in SCell channel
estimation(deltaCqiTargetScellChEst)
Delta CQI aging window in SCell channel estimation
(deltaCqiAgingWinScellChEst)

Expected impact on performance counters

There are no related counters.

2.6.1.2 QCI-specific UL power control

This change might improve the UL throughput for specific target QCI bearers or for
64QAM UEs.

Short description
With this change enabled, the eNB creates QCI-specific UL power control settings that can
be applied to a selected QCI to define modulation-specific values for PUSCH target closed
loop power control settings. The selected QCI can be replaced in favor of all QCIs for
modulation 64QAM or higher.

The target QCI will have separate parameters for modulation values lower than 64QAM in UL
and modulation higher or equal to 64QAM.

Related features
LTE27 Open loop UL power control and DL power setting

90 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related parameters
Method for UL power control (actUlpcMethod)
Activate Differentiation for PUSCH closed loop power control
(actUlpcDiffPusch)
QCI for differentiated PUSCH closed loop power control
(ulpcDiffTgtQci)
TPC Direction for Quad 1 of differentiated PUSCH ULPC Decision
Matrix (ulpcDiffTpcDirQuad1)
TPC Direction for Quad 9 of differentiated PUSCH ULPC Decision
Matrix (ulpcDiffTpcDirQuad9)
Time interval for power command decisions with differentiated ULPC
(ulpcDiffReadPeriod)
PHR Threshold for Up TPC with differentiated ULPC
(ulpcDiffPhrThresh)
MCS Delta Threshold for Up TPC with differentiated ULPC
(ulpcDiffMcsThresh)
Lower RSSI threshold for differentiated TPC decision per QCI
(ulpcDiffLowLev)
Lower SINR threshold for differentiated TPC decision per QCI
(ulpcDiffLowQual)
Lower RSSI threshold for differentiated TPC decision with 64QAM
(ulpcDiffLowLev64)
Lower SINR threshold for differentiated TPC decision with 64QAM
(ulpcDiffLowQual64)
Upper RSSI threshold for differentiated TPC decision per QCI
(ulpcDiffUpLev)
Upper SINR threshold for differentiated TPC decision per QCI
(ulpcDiffUpQual)
Upper RSSI threshold for differentiated TPC decision with 64QAM
(ulpcDiffUpLev64)
Upper SINR threshold for differentiated TPC decision with 64QAM
(ulpcDiffUpQual64)
Configuration for differentiated PUSCH closed loop power control
(ulpcDiffSchConfig)
Control for differentiated PUSCH closed loop power control
(ulpcDiffSchControl)
Configuration of PUSCH closed loop power control for
differentiation with 64QAM (ulpcDiffConfig64)
Uplink power control PUSCH configuration (ulpcPuschConfig)

Issue 01D. © 2022 Nokia. Nokia Confidential Information 91

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Expected impact on performance counters
There are no related counters.

2.6.1.3 Improved UL grant efficiency for TCP boosting

New parameters are introduced to improve the grant efficiency used for Transmission
Control Protocol (TCP) boosting. The PDCCH and PUSCH usage ratio is expected to be
reduced. The Received Signal Strength Indicator (RSSI) noise increase should be reduced
when the LTE4066 feature is activated.

Short description
This change aims at improving the efficiency of TCP boost proactive UL grants and the
skippable TCP boost proactive UL grants by introducing the following enhancements:
Grants will only be triggered when the scheduled data size at a TTI is not lower than the
value of the ilMinDataTrigGrantTcpBoost parameter.
Grant can be sent only after the configured gap (ilGrantGapTcpBoost) TTIs elapsed
since the previous UL grant (regardless of the grant type).
A grant delay timer is introduced (ilGrantDelayTcpBoost) to avoid sending grants too
soon.
The grant period expiration accuracy is improved so that no grants are sent after the
grant timer expires.

Related features
LTE4066: Low Latency Fast UL Grants

Related parameters
Activate improve UL grant efficiency for TCP Boost
(actUlGrantEffTcpBoost)
Improved latency minimum DL data to trigger TCP Boost proactive UL
grants sending (ilMinDataTrigGrantTcpBoost)
Improved latency initial delay for proactive UL grants triggered
for TCP boosting (ilGrantDelayTcpBoost)
Improved latency gap for proactive UL grants triggered for TCP

92 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
boosting (ilGrantGapTcpBoost)

Expected impact on performance counters

There are no related counters.

2.6.2 LTE19A FDD algorithm changes

2.6.2.1 Correction of PUCCH RSSI and PUCCH SINR KPIs in

inter-site CA
The PUCCH Received Signal Strength Indicator (RSSI) and PUCCH Signal to Interference
and Noise Ratio (SINR) KPIs will show correct values in inter-site carrier aggregation (CA)
scenarios.

Short description
With this change, 'DTX-to-ACK' and 'DTX-to-NACK' (discontinuous transmission
acknowledgement or negative acknowledgement) errors caused by the PUCCH pre-
allocation based decoding of PUCCH format 3 and PUCCH format 1bwcs will not result in
fake PUCCH SINR samples and fake PUCCH RSSI samples that were taken into the calculation
of the PUCCH KPIs and counters.

Related features
LTE3022/SR001419: Inter-site Carrier Aggregation

Related parameters
Activate inter-eNB DL carrier aggregation (actInterEnbDLCAggr)

Expected impact on performance counters

If the actInterEnbDLCAggr parameter value is set to true and the CA deployment is
inter-site (there is an X2-connected SCell), then the following KPI values might increase:
LTE_5441b E-UTRAN Average RSSI for PUCCH

Issue 01D. © 2022 Nokia. Nokia Confidential Information 93

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
LTE_5541b E-UTRAN Average SINR for PUCCH

2.6.2.2 Modification of conditions triggering the step-wise

secondary cell (SCell) configuration
The SCell configuration will be triggered only when the UE is in 'in-sync' state.

Short description
With this change, the step-wise SCell configuration will not be triggered when the UE is in
'out-of-sync' state.

Related features
LTE1541: Advanced SCell Measurement Handling

Related parameters
PDCCH Order Configuration (pdcchOrderConfig)

Expected impact on performance counters

If the DL carrier aggregation is enabled, the numTxWithHighNonGbr parameter value is
bigger than 0, and the pdcchOrderConfig parameter value is either set to enabled or
not configured at all, then the following KPI values might decrease:
LTE_5319c E-UTRAN Average UEs with Configured one SCell in DL
LTE_5320b E-UTRAN Average UEs with an Activated SCell in DL
LTE_5672b E-UTRAN Average UEs with Configured two SCells in DL
LTE_5999a E-UTRAN Average UEs with Configured three SCells in DL
LTE_6003d E-UTRAN Average Number of CCCs in DL
LTE_6166a E-UTRAN SCell Configuration Attempts in DL and UL
LTE_6304a E-UTRAN Average UEs with Configured four SCells in DL
LTE_6615a E-UTRAN Average UEs with Configured five SCells in DL
LTE_6791a E-UTRAN Average UEs with Configured six SCells in DL
LTE_5246a E-UTRAN Average UEs with Activated Three SCells in DL
LTE_5674b E-UTRAN Average UEs with Activated Two SCells in DL
LTE_6302a E-UTRAN Average UEs with Activated Four SCells in DL

94 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
LTE_6614a E-UTRAN Average UEs with Activated Five SCells in DL
LTE_6792a E-UTRAN Average UEs with Activated Six SCells in DL

2.6.2.3 RIP interference measurement correction

The cell PUSCH Received Interference Power (RIP) fetch-type reports show correct results
for PRACH Physical Resource Blocks (PRBs) and PRACH subframe.

Short description
The RIP interference measurement for PRACH PRBs was calculated from both PRACH PRBs
and PUSCH PRBs. With this change, the PUSCH PRBs are excluded.

Related features
LTE1914: RIP (Received Interference Power) measurement report extension/Support RIP
initiated alarms

Related parameters
Activate RIP alarming (actRIPAlarming)

Expected impact on performance counters

There are no related counters.

2.6.2.4 Change in handling the Radio Network Layer

Cause: "Release due to E-UTRAN Generated Reason"
Introduction of a 3GPP-compliant mechanism for handling Radio Network Layer Cause
due to E-UTRAN Generated reason in case of receiving a E-RAB Release Command with
incorrect E-RAB IDs.

Short description
In case of unknown E-RAB ID, the original procedure of handling the Radio Network Layer

Issue 01D. © 2022 Nokia. Nokia Confidential Information 95

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Cause: "Release due to E-UTRAN Generated Reason" (sent within the S1AP: UE CONTEXT
RELEASE REQUEST message from eNB to MME) resulted in moving the “E-RAB to be
Released List” to “E-RAB Failed to Released List”. For bearers which the E-RAB ID was not
known, the cause was set to “Unknown E-RAB ID”. For others, the cause was set to "Release
due to E-UTRAN Generated Reason".

After the change, the UE context should not be released (the S1AP: UE CONTEXT
RELEASE REQUEST message is not sent) when the MME sends an E-RAB release command
with an incorrect E-RAB ID. As a result, other bearers are not released because of the "E-
UTRAN Generated Reason".

Related features
There are no related features.

Related parameters
There are no related parameters.

Expected impact on performance counters

The following counter impact is expected:
The M8013C60 eNB initiated UE Context releases with radio network
layer cause "Unspecified" counter value might decrease.
The M8006C259 eNB initiated E-RAB releases due to E-UTRAN Generated
Reason counter value might increase.

2.6.3 LTE19A TDD algorithm changes

2.6.3.1 TDD mMIMO downlink PRB usage-based multiple

users paring
This change improves the dynamic balancing of single user and multiple user
performance in different scenarios by controlling the maximum number of layers.

96 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Short description
In the original implementation:
The MU set is prioritized as long as UEs fulfill the pairing criterion.
The number of paired layers is always set by the dlMaxNumLayerPerMuRBG parameter.

With the change:

The number of Physical Resource Blocks (PRBs) is prioritized and once the PRB fulfills the
UEs requirement, single user is preferred.
The number of paired layers is decided by dlMaxNumLayerPerMuRBG and the number
of requested resource block groups (RBGs) for all the UEs

Related features
LTE2666: Massive MIMO
LTE3463: DL MU-MIMO for massive MIMO

Related parameters
The maximum multiplexing layers per MU RBG for downlink MU-MIMO of
TDD mMIMO (dlMaxNumLayerPerMuRBG)

Expected impact on performance counters

The cell and user throughput might be improved, thus the following counter values can be
impacted:
M8011C232 - M8011C238 (Number of RBGs for 2-8 paired UEs in DL MU-MIMO mode)
M8012C117 - M8012C134 (IP Throughput volume/time in DL for QCI 1-9)

2.6.3.2 PDCCH CCE power limiting (TDD)

Performance improvement for sites in dense urban areas.

Short description
In dense urban sites the AirScale BTS is dealing with high PDCCH utilization and blocking
because of UEs that are using a high number of Control Channel Elements (CCEs) and power

Issue 01D. © 2022 Nokia. Nokia Confidential Information 97

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
boosting together. This is reducing data scheduling and causing RLC retransmissions, thus
impacting data retainabililty. This change should prevent this behavior by setting PDCCH
resource limits:
Limit the maximum equivalent CCEs (link adaptation requests - CCEs + power boost). This
will be based on Control Format Indicator (CFI) link adaptation methods.
Limit the physical CCE aggregation level by restricting the use of aggregation level 8 with
power boosting (consumes a total number of 16 CCEs when this happens). Instead, the
AirScale BTS will allow power boosting only for aggregation level 1/2/4 (excluding 8). This
should double the PDCCH space and reduce blocking.
Limit the pdcchCqiShift range during the Open Loop Link Adaptation (range from -5
to +10 instead of -10 to +10).

Related features
LTE749: Link adaptation for PDCCH
LTE1035: Outer loop link adaptation for PDCCH

Related parameters
Max PDCCH Aggregation (maxPdcchAgg)
Max PDCCH Aggregation During High PDCCH Load (maxPdcchAggHighLoad)
Max PDCCH Physical CCEs (maxPhyCces)
PDCCH LA CQI shift (pdcchCqiShift)
Min PDCCH LA CQI shift (minPdcchCqiShift)
Max PDCCH LA CQI shift (maxPdcchCqiShift)
Activate outer loop link adaptation (actOlLaPdcch)

Expected impact on performance counters

The following counter values can be impacted:
M8011C39 - M8011C42 (AGG1/2/4/8 used PDCCH)
M8011C43 - M8011C46 (AGG1/2/4/8 blocked PDCCH)

2.7 LTE 19 algorithm changes

Algorithm changes for LTE 19 system

98 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
2.7.1 QCI5 and QCI1 scheduling enhancement for CAT-M
VoLTE Ues
This change aims at improving the CAT-M VoLTE UEs performance by reducing the Cat-M
VoLTE voice gap and radio link failure in parallel with QCI5 SIP transmission. It improves
the VoLTE performance (less voice gaps), quality (possibility of using higher codecs), and
capacity.

Short description
This change consists of two parts:
The first enhancement:
The common link adaptation concept for all bearers (no separate QCI1 semi-static link
adaptation)
The Cat-M scheduler will select the MCS just to fit the data in buffer for Cat-M UEs
(higher MCS for QCI5 and lower MCS for QCI1 with less data, similar as LTE4885 for
Rel-14 UL). Multiple HARQs (LTE4222 and LTE4442) are also possible for VoLTE bearer.
The Cat-M scheduler will use the VoLTE-specific link adaptation BLER target for link
adaptation, after first the DL QCI1 payload arrived.
The Cat-M scheduler will limit the maximum number of repetitions used for the QCI1
bearer.
The MPDCCH LA to follow the common concept as non-GBR.
The dynamic repetition must be enabled if Cat-M VoLTE is enabled.
New parameters are introduced for UL/DL VoLTE BLER target and UL/DL maximum
repetition for VoLTE
The second enhancement:
Boosting the QCI1 (re-)transmission when there are some QCI5 (re-) transmitted
When being boosted, the QCI1 UL/DL will still toggle as currently.
Initial transmission and re-transmissions are both counted as QCI1 or QCI5
transmissions.

Related features
There are no related features.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 99

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related parameters
New parameters:

CATMPR/amcCStepUpQci1CatM

CATMPR/dlTargetBlerQci1CatM

CATMPR/ulTargetBlerQci1CatM

CATMPR/catMVoLTETab/mpdschMaxNumRepQci1CatM

CATMPR/catMVoLTETab/mpuschMaxNumRepQci1CatM

Updated existing parameters (consistency checks, value range):

CATMPR/catMVoLTETab/dlMaxHarqTxQci1CatM

CATMPR/catMVoLTETab/ulMaxHarqTxQci1CatM

CATMPR/catMVoLTETab/maxGbrDlQci1CatM

CATMPR/catMVoLTETab/maxGbrUlQci1CatM

CATMCEL/actDynamicRepVoLTECatM

Expected impact on performance counters

The following counter and KPI values might decrease:
LTE_6381a E-UTRAN Average VoLTE PDCP SDU Delay in DL for Cat-M UEs
LTE_6382a E-UTRAN Average VoLTE Latency Uplink for Cat-M UEs
LTE_6383a E-UTRAN Average VoLTE Latency Downlink for Cat-M UEs
LTE_6384a E-UTRAN VoLTE PDCP SDU Discard Ratio in DL for Cat-M UEs
LTE_6385a E-UTRAN VoLTE PDCP SDU Loss Ratio in the DL for Cat-M
UEs
LTE_6386a E-UTRAN VoLTE PDCP SDU Loss Ratio in the UL for Cat-M
UEs
M8061C105 Mean PDCP SDU delay on DL DTCH for DRB for VoLTE (LTE-M)
M8061C106 Average HARQ transmission time for TBs for VoLTE (LTE-M)
M8061C107 PDCP SDU delay on UL DTCH Mean for VoLTE (LTE-M)
M8061C110 Number of lost PDCP SDUs in UL for VoLTE UEs (LTE-M)
M8061C111 Number of PDCP SDU UL for VoLTE (LTE-M)
M8061C112 Number of lost PDCP SDUs in DL for VoLTE UEs (LTE-M)
M8061C113 Number of PDCP SDU discarded in DL for VoLTE UEs (LTE-M)
M8061C114 Number of PDCP SDU DL for VoLTE UEs (LTE-M)

100 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
2.7.2 Counters for micro-DTX
The M8010C93 counter will not be provided for some radio units.

Short description
The new radio units (from release 5 onwards) do not support the reporting of suppressed
OFDM symbols with micro DTX ratio.

Before FL19 release, the M8010C93 Suppressed OFDM symbols with micro DTX
ratio in RF module counter was reported by the system module for rel. 5 radio units.
From FL19 onwards, the M8010C94 Suppressed OFDM symbols with micro DTX
ratio in FS module counter was added and the implementation of M8010C93 was
reverted. This leads to situation that for some radio units only the M8010C94 counter is
provided, while for others both M8010C93 and M8010C94 counters are available.

Related features
LTE3036: Micro DTX extension
LTE1891: eNodeB Power Saving – Micro-DTX

Related parameters
There are no related parameters.

Expected impact on performance counters

M8010C93 Suppressed OFDM symbols with micro DTX ratio in RF module
M8010C94 Suppressed OFDM symbols with micro DTX ratio in FS module
LTE_5789a E-UTRAN Percentage of Suppressed OFDM Symbols with Micro
DTX in RF Module

Issue 01D. © 2022 Nokia. Nokia Confidential Information 101

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
2.7.3 Average number of available PRBs when micro DTX
extension is activated
The LTE3036: Micro DTX extension feature activation impacts the M8001C216 counter.

Short description
The M8001C216 counter will not discard the muted Transmission Time Intervals (TTIs) when
the LTE3036 feature is activated. This is because the muted Physical Resource Blocks (PRBs)
are available in a very short time (almost immediately) whenever a larger amount of data
needs to be transmitted. A sudden drop of KPI values for estimation of spectral efficiency is
avoided.

Related features
LTE3036: Micro DTX extension

Related parameters
There are no related parameters.

Expected impact on performance counters

The M8001C216: Average number of available PRBs per TTI on PDSCH
counter value will increase when the LTE3036 feature is activated.

2.7.4 Direct reporting removal

The direct reporting of CSI/ACK/NACK from the uplink physical layer to each serving cell
(PCell and SCells) is removed.

Short description
All CSI/ACK/NACK reports are delivered to the serving cells by the DL scheduler of the PCell
or by the DL scheduler of the UL+DL SCell (in case of uplink control information (UCI) on the
SCell's PUSCH). The new reporting solution is scalable and it is an enabler of CA features with
number of CC equal or higher than 6.

102 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related features
LTE4753: Licensed Assisted Access 7CC

Related parameters
There are no related parameters.

Expected impact on performance counters

There are no related counters.

2.7.5 Changes in inter-site carrier aggregation (CA)

Changes aimed at improving the secondary cell (SCell) configuration success rate are now
applicable for UEs that are candidates for inter-site CA (UEs that can get an SCell
connected through the X2 interface). Before this change the improvements were
applicable only for UEs that are candidates for intra-site CA.

Short description
When one of the following conditions are fulfilled:
1. condition:
dlCaMinPcellCqi is bigger than 0 and/or ulCaMinPcellSinr is bigger than 0
and/or dlCaMinPcellCqiQci1 is bigger than 0 and/or ulCaMinPcellSinrQci1 is
bigger than 0
and
actInterEnbDLCAggr equals to true and the CA deployment is inter-site (there are
SCells connected via the X2 interface)
2. condition
actInterEnbDLCAggr equals to true and the CA deployment is inter-site (there are
SCells connected via the X2 interface

then this change will increase the SCell configuration success rate and decrease the SCell
configuration failures.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 103

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related features
LTE3022/SR001419: Inter-site Carrier Aggregation

Related parameters
SCell add DL CQI threshold (dlCaMinPcellCqi)
SCell add UL SINR threshold (ulCaMinPcellSinr)
SCell add DL CQI threshold for QCI1 (dlCaMinPcellCqiQci1)
SCell add UL SINR threshold for QCI1 (ulCaMinPcellSinrQci1)
Activate inter-eNB DL carrier aggregation (actInterEnbDLCAggr)

Expected impact on performance counters

The following KPI value might increase:
LTE_5323a E-UTRAN SCell Configuration Success Ratio

The following KPI and counter values might decrease:

LTE_6166a E-UTRAN SCell Configuration Attempts in DL
M8011C67 Number of SCell addition attempts

2.7.6 Enhanced flow control

With this change the enhanced flow control algorithms will be taken into use for all carrier
aggregation (CA) deployment. Also, the buffer monitoring of EN-DC eligible bearers for an
EN-DC setup becomes feasible.

Short description
The buffer monitoring of a secondary cell (SCell) addition and SCell activation is moved from
the downlink scheduler to the Radio Link Control (RLC) layer and the SCell addition buffer
threshold will be calculated differently.

The SCell addition buffer threshold calculated by RLC will be typically greater than the
threshold calculated by the downlink scheduler. The buffer monitoring for SCell activation is
moved from the downlink scheduler to the RLC layer and the SCell activation buffer
threshold will be calculated differently. The SCell activation buffer threshold calculated by
RLC will be typically greater than the threshold calculated by the downlink scheduler. The

104 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
new SCell activation algorithm will use one check instead of three checks.

The carrier aggregation data division algorithm is moved from the downlink scheduler to the
RLC layer. The CA data division algorithm will use new rules of controlling the data division to
serving cells (similar to inter-site CA rules). The new algorithm might result in a more
conservative data assignment to SCells compared to the legacy algorithm.

Related features
LTE4753: Licensed Assisted Access 7CC

Related parameters
Activate enhanced flow control (actFlowCtrlEnh)

Expected impact on performance counters

If intra-site DL CA is configured with the enhanced flow control mechanism enabled
(actFlowCtrlEnh parameter set to true), the following counter values might increase
(compared to actFlowCtrlEnh = false):
M8011C213: Downlink CA Deconfiguration Attempts (alternatively, depending
on the traffic and configuration, this counter value can decrease)
CA activated to CA configured ratio:
(M8051C116 + M8051C117 + M8051C21 + M8051C22 + M8051C168 + M8051C178) /
(M8051C123 + M8051C124 + M8051C19 + M8051C20 + M8051C167 + M8051C177) -
alternatively, depending on the traffic and configuration, this KPI value might decrease
M8012C20: PDCP SDU data volume on eUu Interface downlink
M8012C212: Number of single TTI initial bursts for nonGBR(QCIs
6-9) in DL
LTE_6842a Residual Block Error Rate (rBLER) in DL
LTE_5208a E-UTRAN RLC PDU Re-transmission Ratio Downlink

The following counter values might decrease:

CA volume (M8012C188, M8012C189, M8012C190, M8012C271: DL nonGBR IP
throughput Data Volume for UEs with 2CC/3CC/4CC/5CC CA
CA Transmission Time (M8012C192, M8012C193, M8012C194, M8012C273: DL
nonGBR IP throughput time for UEs with 2CC/3CC/4CC/5CC CA)
IP throughput volume (M8012C127, M8012C129, M8012C131, M8012C133: IP
Throughput volume in DL for QCI 6/7/8/9)

Issue 01D. © 2022 Nokia. Nokia Confidential Information 105

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
IP throughput time (M8012C128, M8012C130, M8012C132, M8012C134: IP
Throughput time in DL for QCI 6/7/8/9)
Average CA configured UEs (M8051C123, M8051C124, M8051C19, M8051C20:
Average number of UEs with one/two/three/four configured SCells)
M8011C67: Number of SCell addition attempts
M8011C213: Downlink CA Deconfiguration Attempts
Average CA activated UEs (M8051C116, M8051C117, M8051C21, M8051C22:
Average number of UEs with one/two/three/four activated SCells)
DL CA PRB ratio ((M8011C223 + M8011C225) / (M8011C223 + M8011C225 +
M8011C227))
DL CA traffic ratio ((M8012C201 + M8012C202) / (M8012C201 + M8012C202 +
M8012C205))
M8012C209: Number of bursts with CA activity in DL for nonGBR
(QCIs 6-9)
CA initial burst delay (M8012C218 / M8012C209)

For counters calculation customization, see the LTE5077: IP Throughput Counter Extension
for CA scenarios feature.

2.8 LTE 18A algorithm changes

Algorithm changes for LTE 18A system

2.8.1 The number of subframes adaptation for message 2

in DL
Multiple Random Access (RA) responses can be fit into one message 2. The eNB selects
the subframes for RA response Media Access Control (MAC) C-PDU based on the the
transport block size (TBS) size.

Short description
Before this change, only one RA response could be fit into one message 2 with a fixed
number of subframes. The change improves the scheduling efficiency for message 2 in the
DL and reduces the timeout of the RA response window size for NB-IoT
(raRespWinSizeNB) parameter.

106 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related features
There are no related features.

Related parameters
There are no related parameters.

Expected impact on performance counters

The following counter values might decrease:
M8066C15 MAC PDU volume in DL for NB-IoT UEs
M8066C18 Used NB-IoT DL resources

2.8.2 Legacy PUCCH region expansion steps calibrated for

Cat-M
More active UEs with a smaller physical uplink control channel (PUCCH) configuration in 5
MHz cells

Short description
This change calibrates the PUCCH configuration when the cell bandwidth is 5MHz and the
LTE3128: LTE-M feature is activated. It reduces the number of format1b with channel
selection (F1bCS) resources available for 2CC Carrier Aggregation (CA) to allow more
resources available for scheduling request and therefore to have more active UEs in the cell
by a smaller PUCCH configuration.

This change brings better coexistence of legacy PUCCH configuration with the strong
constraints of Cat-M configuration in a small bandwidth cell (5 MHz). 2CC CA-capable UEs
may experience increased blocking (the UE cannot be scheduled in the secondary cell (SCell)
because there are not enough 'F1bCS' resources for providing feedback).

Related features
LTE1130: Dynamic PUCCH Allocation
LTE2664: Load-based PUCCH Region

Issue 01D. © 2022 Nokia. Nokia Confidential Information 107

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related parameters
There are no related parameters.

Expected impact on performance counters

There are no related counters.

2.8.3 LTE2664 enhancements of minimal configuration

handling
Decreasing of the radio admission control (RAC) rejection at a minimal physical uplink
control channel (PUCCH) configuration

Short description
During the field trials of the LTE2664: Load-based PUCCH Region feature it was noticed that
usage of the minimal configurations causes frequent RAC rejections. Especially for Carrier
Aggregation (CA) and MIMO PUCCH configurations, the number of UEs supported in the
minimal configuration is near the real minimal limit (the eNB needs to consider the pre-
reservations for handover/TAU/emergency). Because the expansion includes the system
information block (SIB) reconfiguration, the time needed for such procedure is significant
(5~20s), and in such time the number of UEs kept for the additional connections might be
quickly exhausted, causing the RAC rejections.

At expansion from the minimal PUCCH configuration, the RAC is immediately informed of
the new target capacity. Therefore, the RAC will not block the incoming UEs above the
threshold given for the minimal PUCCH configuration. Free scheduling request (SR)
resources during the transition are allocated at 40 ms.

During the transition phase of the expansion, CA is temporary suspended. The 'F1bCS'
dedicated resources are used for SR allocation during this phase. In the transient phase
from the minimal PUCCH configuration, RAC does not guarantee pre-reservations for
handover and non-data radio bearer (non-DRB, like tracking area update) connections.

Finally the system ignores the expansion timer. This avoids any delay when expanding from
the minimal PUCCH configuration. As soon as the conditions for the expansion are fulfilled,
the expansion is triggered even if the Countdown timer SIB modification by
PUCCH expansion (countdownPucchExp) still has not expired.

108 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
At the compression to the minimal configuration, a method has been implemented to avoid
too early compressions that consequently may cause blocking issues with the next
consequent new expansion.

Related features
LTE2664: Load-based PUCCH Region

Related parameters
There are no related parameters.

Expected impact on performance counters

There are no related counters.

2.8.4 Support Cat-M CE ModeA Paging Optimization

Support of a per-CE level paging for CE ModeA UEs, which determines the
MPDCCH/MPDSCH paging repetition according to UE's RF conditions. This mechanism
saves the MPDCCH/MPDSCH paging resources.

Short description
Before the change, the eNB would page the Cat-M UE in a CE ModeA (that is, CE0 or CE1)
with common MPDCCH/MPDSCH paging repetition regardless of the "Coverage
Enhancement Level" information received from the MME paging.

This change optimizes the paging for ModeA, that is:

1. The eNB optimizes the MPDCCH paging repetition according to the "Coverage
Enhancement Level" information received from the MME paging. The eNB maps the
mpdcch-NumRepetition-r13 (taken from "Coverage Enhancement Level" IE from MME) up
to the nearest possible higher CE level and use mapped CE level's paging repetitions for
this paging record. The RRC paging message is sent with the highest CE level and with its
paging repetitions derived from all paging records included in the message.
2. The eNB implements the CE level paging MPDSCH repetition according to the selected
MPDCCH CE level.
3. The eNB implements the CE level ramp-up after unsuccessful paging attempts.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 109

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
4. The eNB supports the CE level threshold for the first paging attempt on E-UTRAN Cell
Global Identifier (ECGI) only (that is, only if the first mapped CE level is higher than the
threshold, the ECGI-only paging will be supported.).

Related features
There are no related features.

Related parameters
CATMPR/catMCELevel1: Repetition level of M-PDCCH(UE-SS) for Cat-M CE
Level 1 (mpdcchRepLevPagCatM)

CATMPR/catMCELevel1: Repetition level of PDSCH(Paging) for Cat-M CE

Level 1 (pdschRepLevPagCatM)

CATMPR: Maximum attempt number for paging message within current

coverage level for Cat-M CE ModeA (pagAttCeIncreaseModeACatM)

CATMCEL: Starting Coverage Level to support first paging attempt on

ECGI only for Cat-M (startingCovLevelPagingOptCatM)

Expected impact on performance counters

There are no related counters.

2.8.5 SCell activation for 256 QAM-capable UEs

Transition to 256 QAM tables and configuration of the secondary cells (SCells) are
modified with the introduction of LTE4064.

Short description
The algorithms for transition between 256 QAM and legacy tables and the SCell activation
and modification for 256 QAM-capable UEs (addition or swap) are modified with the
introduction of LTE4064:256 QAM enhancements. For details, refer to LTE4064 feature
description.

Before the change, the 256 QAM tables were used by default for initial admission of 256

110 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
QAM capable UEs. Many UEs which used 256 QAM tables according to the LTE3073: 256
QAM Extensions feature experienced throughput degradation. The degradation was caused
by lower granularity of 256 QAM tables around the QPSK area which triggered Carrier
Aggregation (CA) to get sufficient bandwidth to transmit data which is in the buffer.

With the introduction of LTE4064:256 QAM enhancements, the 256 QAM capable UEs are
initially admitted with legacy tables and the transition to 256 QAM tables happens only for
UEs in good radio conditions. Therefore, the total number of activated UEs in 256 QAM
mode is reduced in FL18A. Since 256 QAM tables are used only for UEs in good radio
conditions, there is no throughput degradation and the CA activation is used in an optimized
way.

Related features
LTE4064:256 QAM enhancements

Related parameters
There are no related parameters.

Expected impact on performance counters

The call drop rate of 256 QAM configured UEs might decrease:
LTE5090f: E-UTRAN E-RAB Drop Ratio per Cause, RNL due to loss of
connection to the UE, initiated by eNB

The following counter values might decrease:

M8011C196 PDSCH transmission using QPSK of 256QAM-scheduled UE
M8011C197 PDSCH transmission using 16QAM of 256QAM-scheduled UE
M8012C175 MAC PDU volume PDSCH using QPSK of 256QAM-scheduled UE
M8012C176 MAC PDU volume PDSCH using 16QAM of 256QAM-scheduled UE
M8011C200 PDSCH transmission nacks using QPSK of 256QAM-scheduled UE
M8011C201 PDSCH transmission nacks using 16QAM of 256QAM-scheduled UE
M8011C202 PDSCH transmission nacks using 64QAM of 256QAM-scheduled UE
M8011C203 PDSCH transmission nacks using 256QAM of 256QAM-scheduled UE
M8011C204 Failed PDSCH transmission using QPSK of 256QAM-scheduled UE
M8011C205 Failed PDSCH transmission using 16QAM of 256QAM-scheduled UE
M8011C206 Failed PDSCH transmission using 64QAM of 256QAM-scheduled UE
M8011C207 Failed PDSCH transmission using 256QAM of 256QAM-scheduled UE

Issue 01D. © 2022 Nokia. Nokia Confidential Information 111

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
M8010C116 - M8010C131 (UE Reported CQI Level 00 for 256QAM-configured UEs - UE
Reported CQI Level 15 for 256QAM-configured UEs)
M8010C132 - M8010C147 (CQI Level 0 for Codeword 1 Reported by 256QAM-configured
UEs - CQI Level 15 for Codeword 1 Reported by 256QAM-configured UEs)

The following counter and KPI values might decrease:

M8051C116 Average number of UEs with one activated SCell
M8051C117 Average number of UEs with two activated SCells
M8051C21 Average number of UEs with three activated SCells
M8051C22 Average number of UEs with four activated SCells
M8012C151 PCell RLC data volume in DL via SCell
LTE_5320b E-UTRAN Average UEs with an Activated SCell in DL
LTE_5674b E-UTRAN Average UEs with Activated Two SCells in DL
LTE_5246a E-UTRAN Average UEs with Activated Three SCells in DL
LTE_6302a E-UTRAN Average UEs with Activated Four SCells in DL
LTE_5324a E-UTRAN RLC PDU Volume DL via Scell

The following counter and KPI values might increase:

M8010C36 - M8010C51 (UE Reported CQI Level 00 - UE Reported CQI Level 15)
M8001C45 - M8001C73 (PDSCH transmissions using MCS0 - PDSCH transmissions using
MCS28)
M8001C236 - M8001C238 (PDSCH transmissions using MCS29 - PDSCH transmissions
using MCS31)
M8001C103 - M8001C131 (PDSCH transmission nacks using MCS0 - PDSCH transmission
nacks using MCS28)
M8001C239 - M8001C241 (PDSCH transmission nacks using MCS29 - PDSCH
transmission nacks using MCS31)
M8001C156 - M8001C209 (Failed Transmission PDSCH MCS0 - Failed Transmission
PDSCH MCS28)
M8001C242 - M8001C244 (Failed Transmission PDSCH MCS29 - Failed Transmission
PDSCH MCS31)
LTE_6119a E-UTRAN Average CQI of 256QAM configured UEs
LTE_6263a This KPI provides the percentage of PDSCH transmissions using High MCS
Codes (MCS>=20).

The following counter and KPI value changes depend on radio conditions:
M8011C198 PDSCH transmission using 64QAM of 256QAM-scheduled UE
M8011C199 PDSCH transmission using 256QAM of 256QAM-scheduled UE
M8012C177 MAC PDU volume PDSCH using 64QAM of 256QAM-scheduled UE

112 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
M8012C178 MAC PDU volume PDSCH using 256QAM of 256QAM-scheduled UE
LTE_6262a E-UTRAN Percentage of PDSCH transmissions using Low MCS Codes (MCS<=9)

Higher numbers of CCs might be used less frequently for 256 QAM UEs (depending on the
radio conditions), therefore the following counter values (with related KPIs) might be
impacted:
M8051C116 Average number of UEs with one activated SCell
M8051C117 Average number of UEs with two activated SCells
M8051C21 Average number of UEs with three activated SCells
M8051C22 Average number of UEs with four activated SCells
M8051C168 Average number of UEs with five activated Scells

2.8.6 Dynamic UL resource units selection

Potential throughput improvement with larger transport block size scheduled in worse
radio conditions

Short description
Before this change, the maximum UL transport block size (TBS) of 1000 bits was supported
for Cat-NB1 UEs using 4 resource units. From FL18A onwards, the maximum UL transport
block size is supported for Cat-NB1 UEs using 5/6/8/10 resource units. The efficiency is
higher when the resource units are fitting the payload. Larger TBS can be scheduled also
when the radio conditions become worse, therefore the UL throughput can be improved.

Related features
There are no related features

Related parameters
There are no related parameters.

Expected impact on performance counters

The following counter values might increase:
M8066C14: MAC PDU volume in UL for NB-IoT UEs

Issue 01D. © 2022 Nokia. Nokia Confidential Information 113

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
M8066C16: Number of used NB-IoT UL resources

2.8.7 Radio Link Failure (RLF) indication during the Initial

Context Setup Procedure
When there is and RLF indication, the internal resources are released sooner which leads
to better resource handling.

Short description
Before the change, when an RLF indication was received during an RRC Initial Context Setup
Procedure, it was ignored. After the change, when an RLF Indication is received it stops the
Initial Context Setup Procedure.

Related features
There are no related features

Related parameters
There are no related parameters.

Expected impact on performance counters

The failure counting is shifted from the M8006C247 Failed setup attempts for
initial E-RABs due to "Radio Network Layer Cause - Failure in the
Radio Interface Procedure" counter to M8006C246: Failed setup attempts
for initial E-RABs due to "Radio Network Layer Cause - Radio
Connection with UE lost", therefore the value of M8006C246 might increase.

Degradation of the initial context setup success rate KPIs might also occur.

2.8.8 The SCell will not be deactivated when the

ChannelStatus value equals 'undetected'
If the monitoring feature introduced with LTE1541 detects that an secondary cell (SCell)

114 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
is in 'ChannelStatus = undetected', then the SCell will not be deactivated (also this SCell
will not be scheduled in this state).

Short description
When the following conditions are met:
actAdvScellMeas = true
multScellReleaseTimer = 0

then this change helps to avoid an SCell activation-deactivation ping-pong and SCell
scheduling in very bad radio conditions.

Related features
LTE1541: Advanced SCell Measurement Handling

Related parameters
Activate advanced SCell measurement handling (actAdvScellMeas)
Mult. factor for SCell release timer (multScellReleaseTimer)
Threshold for a not detectable Scell (scellNotDetectableThr)

Expected impact on performance counters

The following counter and KPI values might increase:
LTE_5320b E-UTRAN Average UEs with an Activated SCell in DL
(M8051C116)
LTE_5674b E-UTRAN Average UEs with Activated Two SCells in DL
(M8051C117)
LTE_5246a E-UTRAN Average UEs with Activated Three SCells in DL
(M8051C21)
LTE_6302a E-UTRAN Average UEs with Activated Four SCells in DL
(M8051C22)

2.9 LTE 18SP algorithm changes

Algorithm changes for LTE 18SP system

Issue 01D. © 2022 Nokia. Nokia Confidential Information 115

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
2.9.1 Common algorithm changes
Common FDD and TD algorithm changes for pre-LTE 18SP features

2.9.1.1 Downlink cat-4 UEs supported in uplink 64QAM

Less expensive UEs support 64QAM UL, which improves the network throughput.

Related features
LTE44: 64 QAM in UL

Related parameters
There are no related parameters.

Expected impact on performance counters

The following counter values might increase:
M8001C41 PUSCH transmissions using MCS25
M8001C42 PUSCH transmissions using MCS26
M8001C43 PUSCH transmissions using MCS27
M8001C44 PUSCH transmissions using MCS28

2.9.1.2 Proactive grants for VoLTE robustness

Low priority proactive uplink grants are added for non-TTI bundling QCI1 traffic.
Proactive, forced SRI uplink grants are added for TTI bundling QCI1 traffic.

Related features
There are no related features.

116 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related parameters
There are no related parameters.

Expected impact on performance counters

The LTE_6243a Percentage of Average Uplink VoLTE Quality Break Period
Expected Time KPI value might decrease.

2.9.2 FDD-LTE 18SP algorithm changes

Algorithm changes for pre-LTE 18SP features

2.9.2.1 Support of MCS29/30/31 for retransmission

Non-256QAM-capable LTE UEs (modulation and coding scheme MCS 29/30/31) or
256QAM-capable LTE UEs (MCS28/29/30/31) are supported for hybrid automatic repeat
request (HARQ) retransmission in downlink (DL).

Short description
The solution is based on 3GPP TS36.213. It is beneficial for all cases (with or without Cat-M,
conflicting with legacy SIBs and Cat-M SIBs). With MCS29/30/31, the possibility of collisions
is reduced and the expected throughput related to the HARQ retransmission can be
scheduled in the available time frame.

With the LTE3128: LTE-M feature enabled, the possibility of collision between LTE
scheduling and Cat-M MIB/SIB/paging/data transmission increased. The gain of legacy peak
throughput with this improvement significantly increased (approximately 7%~8%).

Related features
LTE3128: LTE-M
LTE45: Fair Scheduler (UL/DL)

Issue 01D. © 2022 Nokia. Nokia Confidential Information 117

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related parameters
There are no related parameters.

Expected impact on performance counters

New counters are introduced in FDD-LTE 18SP:
M8001C236 PDSCH transmissions using MCS29
M8001C237 PDSCH transmissions using MCS30
M8001C238 PDSCH transmissions using MCS31
M8001C239 PDSCH transmission nacks using MCS29
M8001C240 PDSCH transmission nacks using MCS30
M8001C241 PDSCH transmission nacks using MCS31
M8001C242 Failed Transmission PDSCH MCS29
M8001C243 Failed Transmission PDSCH MCS30
M8001C244 Failed Transmission PDSCH MCS31
M8012C148 MAC PDU volume PDSCH MCS29
M8012C149 MAC PDU volume PDSCH MCS30
M8012C150 MAC PDU volume PDSCH MCS31

The following legacy counters and KPIs are impacted:

M8012C25 PDCP Throughput DL Max (increase)
M8012C175 MAC PDU volume PDSCH using QPSK of 256QAM-scheduled UE
M8012C176 MAC PDU volume PDSCH using 16QAM of 256QAM-scheduled UE
M8012C177 MAC PDU volume PDSCH using 64QAM of 256QAM-scheduled UE
M8012C178 MAC PDU volume PDSCH using 256QAM of 256QAM-scheduled UE
M8011C196 PDSCH transmission using QPSK of 256QAM-scheduled UE
M8011C197 PDSCH transmission using 16QAM of 256QAM-scheduled UE
M8011C198 PDSCH transmission using 64QAM of 256QAM-scheduled UE
M8011C199 PDSCH transmission using 256QAM of 256QAM-scheduled UE
M8011C200 PDSCH transmission nacks using QPSK of 256QAM-scheduled UE
M8011C201 PDSCH transmission nacks using 16QAM of 256QAM-scheduled UE
M8011C202 PDSCH transmission nacks using 64QAM of 256QAM-scheduled UE
M8011C203 PDSCH transmission nacks using 256QAM of 256QAM-scheduled UE
M8011C204 Failed PDSCH transmission using QPSK of 256QAM-scheduled UE
M8011C205 Failed PDSCH transmission using 16QAM of 256QAM-scheduled UE
M8011C206 Failed PDSCH transmission using 64QAM of 256QAM-scheduled UE
M8011C207 Failed PDSCH transmission using 256QAM of 256QAM-scheduled UE
LTE_5292d E-UTRAN average PDCP Layer Active Cell Throughput DL (increase)

118 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
LTE_5354a E-UTRAN Averaged IP scheduled Throughput in DL, QCI5
LTE_5356a E-UTRAN Averaged IP scheduled Throughput in DL, QCI7
LTE_5357a E-UTRAN Averaged IP scheduled Throughput in DL, QCI8
LTE_5358a E-UTRAN Averaged IP scheduled Throughput in DL, QCI9
E-UTRAN Percentage of PDSCH transmissions using Low MCS Codes (MCS<=9) - decrease
E-UTRAN Percentage of PDSCH transmissions using High MCS Codes (MCS>=20) -
increase

2.9.2.2 Interference Mitigation of the NB-IoT Receiver

The number of NB-PRACH false alarms is reduced by mitigating interference from
neighbouring LTE PRBs.

Short Description
The interference mitigation receiver for NB-IoT is mitigating interference from
PUSCH/PUCCH to NPRACH because different subcarrier spacing is used. PUSCH is using 15
kHz while NPRACH is using 3.75 kHz subcarrier spacing.

The number of NB-PRACH false alarms is reduced by mitigating interference from

neighboring LTE physical resource blocks (PRBs). Before LTE 18SP, the interference caused
by different subcarrier spacing increased the probability of ghost preambles. The higher the
power of the PUSCH/PUCCH PRBs next to NPRACH, the higher the probability of ghost
preambles. Based on the interference mitigation receiver, the probability of ghost preamble
detection is reduced. Less preambles to be processed by the receiver means less data
volume in UL to be scheduled and also less MSG2 to be scheduled in DL. Thanks to the new
algorithm, the number of false detections significantly decreased but a zero level of false
alarms cannot be guaranteed.

Related features
LTE3071: NB-IoT Inband
LTE3570: NB-IoT Guardband 15/20MHz
LTE3509: NB-IoT: Inband on Airscale without Baseband Pooling
LTE3667: NB-IoT Standalone with Baseband Pooling

Issue 01D. © 2022 Nokia. Nokia Confidential Information 119

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related parameters
There are no related parameters.

Expected impact on performance counters

The following counter values might decrease because of less NB-PRACH false alarms:
M8066C14 MAC PDU volume in UL for NB-IoT UEs
M8066C15 MAC PDU volume in DL for NB-IoT UEs
M8066C16 Number of used NB-IoT UL resources
M8066C18 Used NB-IoT DL resources
M8066C35 NB-IoT RACH Setup attempts without C-RNTI
M8066C36 NB-IoT RACH Setup attempts with valid C-RNTI
M8066C37 NB-IoT RACH Setup attempts with invalid C-RNTI
M8066C38 NB-IoT RACH Setup attempts without C-RNTI for NB-Iot UEs with coverage
enhancement level 1
M8066C39 NB-IoT RACH Setup attempts without C-RNTI for NB-Iot UEs with coverage
enhancement level 2
M8066C40 NB-IoT RACH Setup attempts with valid C-RNTI for NB-Iot UEs with coverage
enhancement level 1
M8066C41 NB-IoT RACH Setup attempts with valid C-RNTI for NB-Iot UEs with coverage
enhancement level 2
M8066C42 NB-IoT RACH Setup attempts with invalid C-RNTI for NB-Iot UEs with coverage
enhancement level 1
M8066C43 NB-IoT RACH Setup attempts with invalid C-RNTI for NB-Iot UEs with coverage
enhancement level 2

2.9.2.3 Automatic calculation of the G-factor

From LTE 18SP onwards, the mpdcchStartSfCssCatM and mpdcchStartSfUessCatM
parameter values are set by the system.

Short description
Before LTE 18SP the possibilities of setting up both parameters were wrongly limited by
consistency checks. With the LTE4495: Cat-M1: eMBMS Coexistence Support feature this
limitation is removed as it introduces the Localized Virtual Resource Blocks (LVRB) and
eMBMS coexistence. As a result, the parameter calculation is related to an invalid subframe

120 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
list (probably operator unknown) and the mpdcchMaxNumRepRaCatM or
mpdcchMaxNumRepCatM parameter. Because it is not feasible to let the operator calculate
the value and to avoid potentially wrong settings, an automatic calculation algorithm was
introduced and the parameters are calculated by the eNB. The value set is always the
smallest possible one.

Related features
LTE4495: Cat-M1: eMBMS Coexistence Support

Related parameters
MPDCCH Start SF for MPDCCH common search space for Cat-M
(mpdcchStartSfCssCatM)
MPDCCH Start SF for MPDCCH UE specific search space for Cat-M CE
Level 0 (mpdcchStartSfUessCatM)

Expected impact on performance counters

There are no related counters.

2.9.2.4 Impact of the Cat-M and eMBMS coexistence

The LTE4495 feature might impact call drop and handover failure rates.

Short description
Before the LTE4495: Cat-M1: eMBMS Coexistence Support feature introduction, eMBMS and
Cat-M had to be deployed on different bands. Both eMBMS and Cat-M have in common that
they consume resources which are not available for the legacy LTE traffic. When LTE4495 is
activated, both eMBMS and Cat-M consume resources in the same band leaving less
resources for legacy LTE traffic as compared to a scenario where eMBMS and Cat-M are in
different bands.

When eMBMS and Cat-M are deployed in the 10 MHz band, the total amount of consumed
PRBs is 42%: 15 PRBs for eMBMS plus 6 PRBs for Cat-M gives 21 PRBs out of 50 PRBs. So
the relative PRB occupancy of eMBMS and Cat-M in a 10 MHz band is significant. Therefore,
high traffic caused by legacy UEs in the 10 MHz band where operator is planning to deploy

Issue 01D. © 2022 Nokia. Nokia Confidential Information 121

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
eMBMS and Cat-M would have a potential KPI impact.

In a mobility scenario where individual UEs or groups of UEs (for example, multiple users
travelling with a bus) may experience bad radio conditions while moving away from the base
station. As a result, the number of HARQ transmissions and RRC reconfiguration messages
will increase. The amount of resources available to accommodate HARQ transmissions and
RRC reconfiguration messages on top of the traffic generated by the legacy UEs is much
lower when LTE4495 is activated. As a result, handover procedures might be delayed and
the probability of call drops might increase.

Note that in many situations the eMBMS traffic appears only at certain slots during the day.
In that case, the unused eMBMS resources are available for legacy UEs. Therefore, the KPI
degradation described above is observed only if the eMBMS traffic is permanently high.

Related features
LTE4495: Cat-M1: eMBMS Coexistence Support

Related parameters
There are no related parameters.

Expected impact on performance counters

The E-RAB drop rate and the context drop rate KPIs might be impacted (for example,
LTE_5025h E-UTRAN E-RAB Drop Ratio, RAN View). Also various handover failure
rates might be impacted (depending on the mobility configuration in use).

2.9.2.5 Adjustment of the SIB-NB broadcast NRS power

value in the 4TX mode
This update aligns the NRS power in SIB broadcasting with the actual averaged NRS power
used in 4TX mode.

Short description
With this change the narrowband (NB) SIB broadcast value of the NRS (Narrowband
Reference Signal) power in the 4TX mode will be 3dB higher. It reflects the actual NRS power

122 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
used for the 4TX mode. The accurate NRS power value results in a better downlink path loss
estimation by the UE. It might also improve the accuracy of uplink power control. The higher
NRS power results in a higher and more accurate UE uplink transmit power, that might lead
to an overall uplink performance improvement.

Related features
LTE4499: NB-IoT Guardband
LTE3570: NB-IoT Guardband 15/20MHz
LTE3722: NB-IoT: Additional configurations (4Rx, 4Tx or 1Tx eNB support)
LTE3071: NB-IoT Inband
LTE3543: NB-IoT Standalone

Related parameters
Downlink MIMO mode (dlMimoMode)

Expected impact on performance counters

There are no related counters.

2.9.3 TD-LTE 18SP algorithm changes

Algorithm changes for pre-LTE 18SP features

2.9.3.1 Cell resource group support with TDD downlink

3CC carrier aggregation
Improved admission control for TDD 3CC carrier aggregation

Related features
LTE1382: Cell resource groups
LTE1836: TDD downlink carrier aggregation - 60Mhz

Issue 01D. © 2022 Nokia. Nokia Confidential Information 123

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related parameters
Activation of downlink carrier aggregation (actDLCAggr)
Activation of automatic PUCCH allocation (actAutoPucchAlloc)
Max number of secondary cells for DL carrier aggr (maxNumScells)
Cell resource sharing mode (cellResourceSharingMode)

Expected impact on performance counters

There are no related counters.

2.9.3.2 Single radio voice call continuity to GSM

workaround
The GSM cell is temporary blacklisted when the SRVCC handover to this GSM cell fails for
consecutive number of times (defined with an internal parameter).

Related features
LTE873: SRVCC to GSM

Related parameters
There are no related parameters.

Expected impact on performance counters

The following counter values might decrease:
M8016C55 Failed Inter-System Handover preparations to GERAN with SRVCC due to
timer
M8016C56 Failed Inter-System Handover preparations to GERAN with SRVCC due to
target eNB admission control
M8016C57 Failed Inter-System Handover preparations to GERAN with SRVCC caused by
other reasons
M8016C64 Failed Inter-System Handover preparations to GERAN with VoLTE Quality
triggered SRVCC due to timer
M8016C65 Failed Inter-System Handover preparations to GERAN with VoLTE Quality

124 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
triggered SRVCC due to target eNB admission control
M8016C66 Failed Inter-System Handover preparations to GERAN with VoLTE Quality
triggered SRVCC caused by other reasons

2.9.3.3 Extended timer ranges

Certain timer parameters have extended value ranges for accurate KPI calculation.

Related features
There are no related features.

Related parameters
RRC guard timer radio bearer management (rrcGuardTimer)
T HO overall delta (tHoOverallD)
TX2 RELOC overall delta (tx2RelODelta)

Expected impact on performance counters

There are no related counters.

2.9.3.4 SCell combination selection mechanism by MIMO

throughput check
The existing carrier aggregation (CA) secondary cell (SCell) combination selection is
modified by performing a throughput check per each available SCell combination until the
eNB finds one that passes the check.

Short description
Before the LTE3879: TDD downlink carrier aggregation with MIMO – 12 layers feature
introduction, the radio admission control (RAC) did not consider any transmission gain when
selecting CA SCells. Now with LTE3879, the RAC admits only the SCell combinations where:
a MIMO transmission gain has been checked
the advantage of using these particular SCells combinations has been checked.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 125

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related features
LTE3879: TDD downlink carrier aggregation with MIMO – 12 layers

Related parameters
There are no related parameters.

Expected impact on performance counters

There are no related counters.

2.10 LTE 18 algorithm changes

Algorithm changes for LTE 18 system

2.10.1 Common algorithm changes

Common FDD and TD algorithm changes for pre-LTE 18 features

2.10.1.1 PUCCH format '1bwsc' to use cyclic PUCCH

allocation
Fair resource allocation of PUCCH format 1b with channel selection for 2CC UEs

Short description
With this change, the PUCCH format 1b with channel selection '1bwsc' will use cyclic PUCCH
allocation (semi-static allocation) when the LTE2006: Flexible Scell selection feature is
enabled (the actFlexScellSelect parameter value is set to true). The change should
reduce blocking of SCell activation for 2CC UEs.

126 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related features
LTE3022: Inter-site Carrier Aggregation
LTE2006: Flexible Scell selection

Related parameters
Activate flexible SCell selection (actFlexScellSelect)

Expected impact on performance counters

The following counter and KPI values might increase:
LTE_5320b E-UTRAN Average UEs with an Activated SCell in DL
M8051C116 Average number of UEs with one activated Scell
M8011C166 SCell scheduling blocking rate due to conflicts on PUCCH
format 1bwcs resources

2.10.1.2 Non-HARQ, MAC-level automatic repeat requests

for inter-site carrier aggregation extension
Improvement of single UE peak rate

Short description
This concerns long X2 backhaul delays in the SCells connected over X2. To optimize the peak
rate in case of small number of scheduled UEs (for long latency connection base carrier
aggregation), the blocking of hybrid automatic repeat request (HARQ) process would be pre-
emptioned by the newest transmission, and the blocked HARQ process would become an
RLC-level retransmission (if it is eventually committed as negative acknowledgement).

Related features
LTE3022: Inter-site Carrier Aggregation

Issue 01D. © 2022 Nokia. Nokia Confidential Information 127

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related parameters
There are no related parameters.

Expected impact on performance counters

There are no related counters.

2.10.2 FDD-LTE 18 algorithm changes

Algorithm changes for pre-LTE 18 features

2.10.2.1 ACK/NACK DTX detection on PUSCH

Improvement of PUSCH link level performance (block error ratio against signal-to-
interference-plus-noise ratio)

Short description
When the acknowledgement or negative acknowledgement (ACK/NACK) message is expected
on PUSCH (before the PUSCH decoding), the uplink receiver is initiating ACK/NACK
transmission/discontinuous transmission (TX/DTX) detection. Depending on the outcome of
such detection, the UL receiver will decode PUSCH assuming that ACK/NACK bits are either
punctured into PUSCH respectively or not. This change applies to inter-site carrier
aggregation (CA), inter-eNB CA, intra-eNB CA, and to single-carrier operation.

This change aims at improving the PUSCH link level performance. Especially in the inter-site
CA scenarios when ACK/NACK is expected on PUSCH not based on actual SCell downlink
transmission, but it is based on semi-static PUCCH resource allocation due to long X2 delay.
It might also impact scenarios when the eNB falsely assumes ACK/NACK on PUSCH due to
PDCCH miss-detection at the UE.

Related features
LTE3022: Inter-site Carrier Aggregation

128 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related parameters
There are no related parameters.

Expected impact on performance counters

There are no related counters.

2.10.2.2 SCell activation threshold based on average

expected UE throughput
More accurate UE throughput prediction to trigger the SCell activation

Short description
With this change, the SCell activation buffer threshold is based on the average expected UE
throughput. In the legacy implementation it was based on average UE throughput. The
change applies to inter-site carrier aggregation (CA), inter-eNB CA, and intra-eNB CA.

The expected UE throughput predicts the UE throughput more accurately compared to the
legacy calculation. Especially for transmission time intervals (TTIs) when all the UE data in a
buffer is drained. The SCell activation threshold calculated based on expected average
throughput might result in a more conservative SCell activation. If needed, this effect can be
compensated by setting the scellActivationLevel parameter to a lower value.

Related features
LTE3022: Inter-site Carrier Aggregation

Related parameters
Conservativeness level of SCell activation (scellActivationLevel)

Expected impact on performance counters

The following counter and KPI values might decrease:
LTE_5320b E-UTRAN Average UEs with an Activated SCell in DL
M8051C116 Average number of UEs with one activated SCell
LTE_5674b E-UTRAN Average UEs with Activated Two SCells in DL

Issue 01D. © 2022 Nokia. Nokia Confidential Information 129

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
M8051C117 Average number of UEs with two activated SCells
M8051C21 Average number of UEs with three activated SCells
LTE_5246a E-UTRAN Average UEs with Activated Three SCells in DL
M8051C22 Average number of UEs with four activated SCells
LTE_6302a E-UTRAN Average UEs with Activated Four SCells in DL
M8051C123 Average number of UEs with one configured SCell
LTE_5319c E-UTRAN Average UEs with Configured one SCell in DL
M8051C124 Average number of UEs with two configured SCells
LTE_5672b E-UTRAN Average UEs with Configured two SCells in DL
M8051C19 Average number of UEs with three configured SCells
LTE_5999a E-UTRAN Average UEs with Configured three SCells in DL
M8051C20 Average number of UEs with four configured SCells
LTE_6304a E-UTRAN Average UEs with Configured four SCells in DL

Note:

The change might be negligible.

2.10.2.3 Modified LTE-M scheduling priorities

Introduction of Cat-M VoLTE support is causing a change of priorities in scheduling.

Short description
From LTE 18 onwards, along with the support of Cat-M VoLTE, the scheduling priorities are
changed. It results in slightly different scheduling order in case of multiple UEs with pending
data and different traffic classes and/or pending HARQ retransmissions. The signaling radio
bearers (SRBs) are sent prior to the pending retransmissions (ReTx). There is also a bigger
differentiation of SRBs.

Related features
LTE4056: Cat-M1: VoLTE Support (Phase-I)
LTE3653: Cat-M1: TA Management for Improved Mobility Support

130 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related parameters
There are no related parameters.

Expected impact on performance counters

There are no related counters.

2.10.2.4 Increased value range for sFreqPrio

The sFreqPrio parameter's maximum value is extended to 10000.

Short description
The carriers for SCell addition are selected with a metric that considers both the downlink
load and the frequency priority. The previous implementation assumed that all frequencies
are in the licensed spectrum, with no further discrimination required. To add further
discrimination capability between licensed and unlicensed frequencies, the value range has
been extended to allow up to ~1000-fold (reached by using a new maximum value of
sFreqPrio parameter that is 10000) biasing between candidates.

Related features
LTE2233: N-out-of-M downlink carrier aggregation

Related parameters
There are no related parameters.

Expected impact on performance counters

There are no related counters.

2.10.2.5 Modified NB-IoT scheduling priorities

The priority for proactive UL scheduling is higher than for UL and DL retransmission.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 131

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Short description
The change aims at reducing the probability of NB-IoT UEs having to use RACH procedure in
order to get resources for UL data transmission assigned.

Related features
LTE4475: NB-IoT: Multiple Coverage Levels

Related parameters
There are no related parameters.

Expected impact on performance counters

There are no related counters.

2.10.2.6 Improvement of L2 HARQ ACK based NB-IoT RRC

connection release.
A new configurable timer is introduced.

Short description
This change enhances the layer 2 hybrid automatic repeat request (HARQ)
acknowledgement-based NB-IoT RRC connection release procedure. A new configurable
timer (tL2AckRrcRelNB) is introduced to control this function. This timer was fixed to 70s
with the introduction of the LTE3668: NB-IoT: Coverage enhancements feature. It can reduce
the release time when there are multiple UEs in coverage enhancement area.

Related features
LTE4475: NB-IoT: Multiple Coverage Levels

Related parameters
Timer missing L2 ack for NB-IoT RRC connection release

132 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
(tL2AckRrcRelNB)

Expected impact on performance counters

There are no related counters.

2.10.2.7 Improvement of NB-IoT cell deletion

A new guard timer is introduced.

Short description
A new guard timer (tCellDelNB) is introduced to force the release of UE context for the
NB-IoT cell deletion. The change aims at reducing the cell deletion time when there are
multiple UEs in a coverage enhancement area.

Related features
LTE4475: NB-IoT: Multiple Coverage Levels

Related parameters
Guard time to force the release of UE context(s) when NB-IoT cell
deletion (tCellDelNB)

Expected impact on performance counters

There are no related counters.

2.10.2.8 Subframe adaptation over NPDSCH in a NB-IoT

cell
The subframe number is adapted based on the transport block size (TBS).

Issue 01D. © 2022 Nokia. Nokia Confidential Information 133

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Short description
In the previous implementation, the subframe number over NPDSCH was fixed to 4. From
LTE 18 onwards (with LTE4475: NB-IoT: Multiple Coverage Levels introduction), it can be
adapted based on the TBS size. The change improves the scheduling efficiency and reduces
the packet delay.

Related features
LTE4475: NB-IoT: Multiple Coverage Levels

Related parameters
There are no related parameters.

Expected impact on performance counters

The M8066C15 MAC PDU volume in DL for NB-IoT Ues counter value might be
impacted.

2.10.2.9 No preamble group B for 5MHz system with Cat-

M
Additional configuration consistency check is introduced.

Short description
The configuration of random access preamble group B is prevented for systems with a 5MHz
system bandwidth and the Cat-M feature activated through an additional explicit check. This
configuration check should prevent increasing the volume of RRC re-establishments being
caused by random access failures. The failures were caused by the size of random access
response message being too large to fit in the available resources of a 5MHz system with
Cat-M feature activated.

Related features
LTE3128: LTE-M

134 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related parameters
Random access preambles group A size (raPreGrASize)
Activate LTE-M feature (actCatM)

Expected impact on performance counters

There are no related counters.

2.10.2.10 Throughput-check procedure enhancement

A throughput-check failure of any SCell candidate will not cause an SCell addition failure
as long as other SCell candidates for SCell addition remain.

Short description
With this change, the throughput-check procedure is now applied not only to the first
proposed SCell candidate but it is continued until there is any SCell candidate which can
pass the check, or there are no SCells remaining. This enhanced throughput procedure is
applicable also for one-step SCell addition. This functionality is available independently of
the feature activation status.

Related features
LTE3605: DL 4x4 MIMO with Carrier Aggregation - 12 layers

Related parameters
There are no related parameters.

Expected impact on performance counters

The following counter and KPI values might increase:
M8011C67 Number of SCell addition attempts
M8011C68 Number of successful SCell additions
LTE_6166a E-UTRAN SCell Configuration Attempts in DL
M8012C151 PCell RLC data volume in DL via SCell

Issue 01D. © 2022 Nokia. Nokia Confidential Information 135

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
LTE_5324a E-UTRAN RLC PDU Volume DL via Scell
M8011C224 PRBs used for SCell UEs' DL DRB traffic
M8011C54 PRB used PDSCH
LTE_6351a E-UTRAN PRB usage ratio for CA related traffic of SCell
UEs in DL
M8051C123 Average number of UEs with one configured SCell
LTE_5319c E-UTRAN Average UEs with Configured one SCell in DL
M8051C124 Average number of UEs with two configured SCells
LTE_5672b E-UTRAN Average UEs with Configured two SCells in DL
M8051C19 Average number of UEs with three configured SCells
LTE_5999a E-UTRAN Average UEs with Configured three SCells in DL
M8051C20 Average number of UEs with four configured SCells
LTE_6304a E-UTRAN Average UEs with Configured four SCells in DL
M8051C116 Average number of UEs with one activated SCell
LTE_5320b E-UTRAN Average UEs with an Activated SCell in DL
M8051C117 Average number of UEs with two activated SCells
LTE_5674b E-UTRAN Average UEs with Activated Two SCells in DL
M8051C21 Average number of UEs with three activated SCells
LTE_5246a E-UTRAN Average UEs with Activated Three SCells in DL
M8051C22 Average number of UEs with four activated SCells
LTE_6302a E-UTRAN Average UEs with Activated Four SCells in DL

2.10.2.10.1 LTE3605 changes to the system

Overview of the throughput check enhancement

The throughput check is based on the twoLayerMimoAvSpectralEff and

fourLayerMimoAvSpectralEff parameters which were introduced with the LTE2582:
DL 4x4 MIMO with Carrier Aggregation feature, and the channel bandwidths of particular
component carriers (CCs). In the context of the LTE2582 feature, the throughput check is
performed for step-wise secondary cell (SCell) addition (numTxWithHighNonGBR> 0).

Starting with LTE3605, the throughput check is performed also for one-step SCell addition
(numTxWithHighNonGBR = 0). Moreover, it has been improved to analize more band
combinations during the radio admission control (RAC) procedure, thus increasing the
chances of finding a suitable Carrier Aggregation (CA) and MIMO layer configuration.

136 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
2.10.2.11 Enhancement of counters related to PDCP SDU
Implementation of counters related to the Packet Data Convergence Protocol (PDCP)
service data unit SDU is moved to the RLC layer.

Short description
In the previous implementation, the monitoring of the eUu interface did not take into
account the Robust Header Compression (ROHC). From LTE 18 onwards, it is included by
moving the implementation to the RLC layer where the ROHC-compressed SDUs are
handled.

Related features
LTE518: Operator specific QCI

Related parameters
There are no related parameters.

Expected impact on performance counters

The following VoLTE bearers counter values should decrease significantly (in case of
activated Robust Header Compression):
M8023C6 PDCP SDU data volume on eUu Interface DL for UEs assigned to QCI Counter
Group 1
M8023C7 PDCP SDU data volume on eUu Interface DL for UEs assigned to QCI Counter
Group 2
M8023C8 PDCP SDU data volume on eUu Interface DL for UEs assigned to QCI Counter
Group 3
M8023C9 PDCP SDU data volume on eUu Interface DL for UEs assigned to QCI Counter
Group 4
M8023C10 PDCP SDU data volume on eUu Interface DL for UEs assigned to QCI Counter
Group 5
M8023C11 PDCP SDU data volume on eUu Interface DL for UEs assigned to QCI Counter
Group 6
M8038C2 PDCP SDU user data volume on eUu interface in DL per PLMN-ID
M8047C4 PDCP SDU data volume on eUu Interface downlink per Profile

Issue 01D. © 2022 Nokia. Nokia Confidential Information 137

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
2.10.2.12 Link adaptation for NB-IoT Inband
Link adaptation is dynamically optimizing data transmission to the radio conditions.

Short description
In FL17A, the transport block size was fixed, while in FL18 the transport block size is
dynamically selected according to the data volume to be transmitted. This change reduces
the PDU volume. This change is visible only when the LTE4475: NB-IoT: Multiple Coverage
Levels feature is activated. The NB-IoT link adaptation is enabled for uplink and downlink by
default.

Related features
LTE4475: NB-IoT: Multiple Coverage Levels

Related parameters
There are no related parameters.

Expected impact on performance counters

The following counter value might decrease:
M8066C15 MAC PDU volume in DL for NB-IoT UEs

2.10.2.13 Lower MCS and PRB allocation is allowed in Cat-

M uplink
The Cat-M UE uplink coverage is increased by enhancing the modulation and coding
scheme (MCS) range and allowing one physical resource block (PRB) allocation.

Short description
The coverage gain is achieved with the following two methods:
The link adaptation (LA) MCS range is increased from a fixed value (MCS 5) to lower values
(in case of two PRBs). This is possible if the operator defined limit (configured with the

138 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Minimum UL transport block size for Cat-M CE mode A
(ulsMinTbsModeACatM) parameter) is not exceeded.
Under certain conditions, it is allowed to switch from two PRBs to one PRB. This results in
higher available power (3 dB) for one PRB that is used to enhance the MCL (visible
especially in flat channels). A loss in a more disperse channel can be encountered.

Using lower values for the ulsMinTbsModeACatM parameter results in more coverage gain,
but on the other side it reduces available resources for all the other UEs in an RRC
connected state.

Related features
LTE3128: LTE-M
LTE3582: LTE-M Enhancements I
LTE3597: Cat-M1: 15 & 20 MHz Support

Related parameters
Minimum UL transport block size for Cat-M CE mode A
(ulsMinTbsModeACatM)

Expected impact on performance counters

There are no related counters.

2.10.2.14 Improvement of VoLTE IP scheduled throughput

The Buffer Status Report (BSR) estimation is performed earlier in the scheduling process.

Short description
At the reception of a scheduling request, the uplink packet scheduler needs to estimate the
BSR size for VoLTE UEs to avoid packet segmentation or to avoid scheduling all VoLTE
packets in a buffer at once.

In the previous implementation, for a UE waiting in scheduler, the uplink VoLTE BSR was
updated in the “post scheduling phase“ (every 10ms or every 40ms depending on the CPU
Load) on a regular basis. In the current implementation, the BSR estimation is done within

Issue 01D. © 2022 Nokia. Nokia Confidential Information 139

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
the frequency domain (FD) scheduler.

By making the BSR update in the FD scheduler (that is just before the scheduling), the
estimation of VoLTE packet number in the BSR is more precise (that is higher) if the UE with
pending scheduling request had to wait to get scheduled. As a result, it is expected that
more VoLTE UEs have the buffer completely empty by the first UL grant that follows the
scheduling request.

Related features
LTE496: Support of QCI 2, 3 and 4

Related parameters
There are no related parameters.

Expected impact on performance counters

The following counter values might decrease:
M8012C92 IP Throughput time in UL for QCI 1
M8012C94 IP Throughput time in UL for QCI 2
M8012C96 IP Throughput time in UL for QCI 3
M8012C98 IP Throughput time in UL for QCI 4
M8012C100 IP Throughput time in UL for QCI 5
M8012C156 IP Throughput net time in UL for QCI 1
M8012C157 IP Throughput net time in UL for QCI 2
M8012C158 IP Throughput net time in UL for QCI 3
M8012C159 IP Throughput net time in UL for QCI 4
M8012C160 IP Throughput net time in UL for QCI 5
M8018C0 Active UE per eNB average
M8018C1 Active UE per eNB max
M8018C8 Sum of Active UEs per eNB
M8018C9 Denominator for Active UEs per eNB
M8038C11 IP Throughput time in UL for QCI1 per PLMN-ID
M8038C13 IP Throughput time in UL for QCI2 per PLMN-ID
M8038C15 IP Throughput time in UL for QCI3 per PLMN-ID
M8038C17 IP Throughput time in UL for QCI4 per PLMN-ID
M8038C19 IP Throughput time in UL for QCI5 per PLMN-ID
M8047C3 IP Throughput time in UL per Profile

140 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
M8051C57 Active UE per Cell average
M8051C58 Active UE per Cell max
M8051C62 Sum of Active UEs per cell
M8051C97 UEs with buffered UL data for DRB with QCI 1
M8051C99 Sum of Active UEs with buffered data in UL per cell
M8051C103 Sum of active UEs per cell, which had data scheduled in UL
M8051C109 Average number of UEs with buffered data in UL
M8051C110 Max number of UEs with buffered data in UL

The following counter and KPI values might increase:

LTE_5359a E-UTRAN Averaged IP scheduled Throughput in UL, QCI1
LTE_5363a E-UTRAN Averaged IP scheduled Throughput in UL, QCI5
M8012C91 IP Throughput volume in UL for QCI 1
M8012C93 IP Throughput volume in UL for QCI 2
M8012C95 IP Throughput volume in UL for QCI 3
M8012C97 IP Throughput volume in UL for QCI 4
M8012C99 IP Throughput volume in UL for QCI 5
M8038C10 IP Throughput volume in UL for QCI1 per PLMN-ID
M8038C12 IP Throughput volume in UL for QCI2 per PLMN-ID
M8038C14 IP Throughput volume in UL for QCI3 per PLMN-ID
M8038C16 IP Throughput volume in UL for QCI4 per PLMN-ID
M8038C18 IP Throughput volume in UL for QCI5 per PLMN-ID
M8047C1 IP Throughput data volume in UL per Profile

2.10.2.15 Improvement of the average UL MCS

Higher UL modulation and coding scheme (MCS) to be used so that UL data can be
transferred with smaller number of data transmissions.

Short description
The change concerns the Extended Uplink Link Adaptation (eULA). If the scheduling inactivity
was higher than 200ms but smaller than 1s, the eULA considers an extra MCS downgrade
towards the initial MCS only if the last UL data transmission resulted with negative
acknowledgement. It is expected that most UEs in the field have stationary conditions and
therefore only few additional hybrid automatic repeat request (HARQ) retransmissions are
expected after this change.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 141

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related features
LTE1034: Extended Uplink Link Adaptation

Related parameters
There are no related parameters.

Expected impact on performance counters

The following counter and KPI values might decrease:
UL MCS2 - MCS11 Usage (M8001C18 PUSCH transmissions using MCS2 - M8001C27
PUSCH transmissions using MCS11)
M8012C89 Number of TTIs in UL with at least one UE scheduled to transmit user plane
data
LTE_6260a E-UTRAN Percentage of PUSCH transmissions using Low MCS Codes (MCS<=9)

The following counter and KPI values might increase:

UL MCS13~MCS28 Usage (M8001C29 PUSCH transmissions using MCS13 - M8001C44
PUSCH transmissions using MCS28)
LTE_6261a E-UTRAN Percentage of PUSCH transmissions using High MCS Codes
(MCS>=20)
LTE_5289d E-UTRAN average PDCP Layer Active Cell Throughput UL

Note:

The impact depends on the Initial MCS in uplink (iniMcsUl) parameter

setting.

2.10.2.16 Source rate based UL grant assignment for

VoLTE (or any other small packet transmission)
Improved algorithm to avoid aperiodic CQI causing segmentation of the PUSCH grants

142 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Short description
When aperiodic channel quality indicator (CQI) is in use it can cause the segmentation on
PUSCH grants. It concerns small packets like VoLTE, but can impact other kind of traffic as
well.

During the PUSCH code rate check (only for modulation and coding scheme (MCS) higher
than 15), the MCS is decreased (but limited to MCS11) until the uplink control information
(UCI) no longer violates the code rate. This can lead to segmentation because the amount of
data to be received no longer fits into the grant for data (because of aperiodic CQI grant
added).

The following change is proposed to deal with situation. If a grant is sufficiently large to
receive all data pending at the UE, then a minimum MCS is defined which is the smallest MCS
which still allows all data to be received without a segmentation. During the code rate check,
the MCS is not reduced below this minimal MCS if aperiodic CQI is requested in the grant. If
the code rate is still violated, the aperiodic CQI is dropped instead. With this evolution, the
dynamic MCS limit is more often reached and the aperiodic CQI is more often skipped and
replaced by a periodic CQI.

As a result, the average CQI decreases. For small allocations (1-3PRBs), the segmentation is
relevant and typically only UEs in good radio conditions can have small UL PRB allocation.
The aperiodic CQI value is skipped, thus the average CQI decreases.

It results in reduced PDCCH load and less UL PRB usage.

Related features
LTE2774: Source rate based UL grant assignment for VoLTE

Related parameters
There are no related parameters.

Expected impact on performance counters

The following counter and KPI values might decrease:
M8001C13 Correct non-duplicate UL-SCH TB with original reception
M8001C139 RLC PDU reception
M8001C142 UL RLC PDUs received
M8001C137 RLC PDU first transmissions

Issue 01D. © 2022 Nokia. Nokia Confidential Information 143

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
M8010C36-M8010C51 UE Reported CQI Level 00 - UE Reported CQI Level 15
M8010C116-8010C131 UE Reported CQI Level 00 for 256QAM-configured UEs - UE
Reported CQI Level 15 for 256QAM-configured UEs
LTE_5427c E-UTRAN Average CQI
LTE_6119a E-UTRAN Average CQI of 256QAM configured UEs

2.10.3 TD-LTE 18 algorithm changes

Algorithm changes for pre-LTE 18 features

2.10.3.1 PRACH format4 guard window adjustment

The guard band is increased, so the side-lobe is not considered in the detection window.

Short description
It was observed that the energy of the desired preamble (for example, preamble 8) might
leak to the detection window of the neighboring preamble, so the fake preamble (for
example, preamble 9) is detected. This change aims at decreasing the PRACH format4 false
alarm rate and improving the handover performance.

Related features
There are no related features.

Related parameters
There are no related parameters.

Expected impact on performance counters

There are no related counters.

144 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
3. Performance changes
Changes introduced to increase the performance of existing features or particular radio
network functions. Usually they introduce new parameters and might require activation.

3.1 SRAN21A performance changes

3.1.1 HRL enforcement also for emergency calls

This functionality allows you to configure the Handover Restriction List (HRL) on the BTS
to reject emergency calls handover.

Technical description
Each Handover Restriction List (HRL) has mobility restrictions that govern the behavior of
calls and handovers. The HRL enforcement also for emergency calls functionality is used to
block inter-Public Land Mobile Network (inter-PLMN) handover for VoIP emergency calls by
introducing additional checks to the mobility restrictions of the HRL. This behavior applies
despite the fact that the call is an emergency one.

The HRL enforcement also for emergency calls functionality is enabled with the LNBTS
Activate the enforced consideration of the HRL list (actEnforceHRL)
parameter. This functionality applies for both X2 and S1 intra-LTE handovers.

Note:

3GPP requests that no mobility restrictions are applied to emergency calls. This
means that inter-PLMN handover for VoIP emergency calls is always allowed. For more
information, see: 3GPP 23.401 (section 4.3.12.3).

Related parameters

Issue 01D. © 2022 Nokia. Nokia Confidential Information 145

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Table 7: Parameters introduced by HRL enforcement also for emergency calls

Path Full name Abbreviated name

MRBTS/LNBTS Activate the enforced actEnforceHRL

consideration of the
HRL list

3.2 SRAN20C performance changes

3.2.1 TDD massive MIMO performance changes in

SRAN20C
Changes introduced to enhance and improve the TDD massive MIMO functionality in
SRAN20C.

3.2.1.1 DL QoE-based scheduling enhancement for low

load scenarios in TDD massive MIMO
Additional enhancements to LTE5674: Downlink QoE-based Scheduling Enhancement for
TDD Massive MIMO, applicable to low load scenarios.

Technical description
This enhancement improves UE throughput by introducing modifications to packet
aggregation scheduling (PAS) and prioritized tail packet (PTP) scheduling algorithms for non-
GBR bearers.

The PTP and PAS enhancements, introduced by the LTE5674: Downlink QoE-based
Scheduling Enhancement for TDD Massive MIMO feature, were intended for medium and
high load scenarios. In order to work also for low load scenarios, since release SRAN 20C
onwards, the following modifications are introduced:

Workload-based scheduling (WBS) improves PTP by draining the data burst as soon as
possible, once it's scheduled. This occurs by increasing the frequency resource allocation
metric in weight-based round robin allocation algorithm. WBS applies to all non-GBR
bearers except for small first packet identification and aggregation candidates (SPA).

146 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Small first packet identification and aggregation (SPA) scheduling improves PAS by
providing additional resource allocation restrictions in the FD-scheduler for small packet
traffic. Small packet scheduling for a specific session is delayed if the session is still
waiting for the first transmission to occur, and hasn't exceeded the configured duration.
This delay occurs only when there are no resources in the FD-scheduler. A UE is
considered a candidate for SPA if its predicted remaining TTIs to drain the current
session burst is less than the configured threshold.

Related parameters
There are no related parameters.

Expected impact on performance counters

There are no related counters.

3.2.1.2 Selective HARQ scheduling in subframe 3 or 8 for

TDD massive MIMO
An enhancement to Hybrid Automatic Repeat Request (HARQ) scheduling which improves
PRB usage in subframe 3 or 8 for TDD massive MIMO (mMIMO).

Technical description
PRB usage in subframes 3 or 8 is observed to be low. This occurs due to either of the
following:
the physical downlink control channel (PDCCH) in subframe 3 or 8 is used for both DL and
UL grants,
the DL retransmission ratio is high in subframe 3 or 8, and
new transmission data volume is insufficient from the scheduled UEs.

This results in lower PRB usage because of limited PDCCH capacity.

The TDD mMIMO selective HARQ scheduling in subframe 3 or 8 enhancement is introduced

to improve PRB usage, specifically by:
limiting PDCCH usage for retransmissions in subframe 3 or 8,
prioritizing retransmissions whose aggregate level is relatively low, and
increasing the TD metric for new transmissions which have a relative high data volume.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 147

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
This enhancement is applicable for non-GBR bearers only.

Related parameters
The following parameters are introduced:
LNCEL_TDD Activate downlink retransmission schedule based on PDCCH
capacity (actDlRetxSchedBasedOnPdcchCap)
LNCEL_TDD PDCCH factor for downlink retransmission and PDCCH block
(pdcchFactorForDLReTxPdcBlk)
LNCEL_TDD PDCCH utility threshold for downlink retransmission
(pdcchUtilThForDlReTx)
LNCEL_TDD Activate downlink new transmission schedule based on
buffer (actDlNewtxSchedBasedOnBuffer)

Expected impact on performance counters

There are no related counters.

3.2.2 CAS Srel Noise Rise Improvement

CAS Srel Noise Rise Improvement allows a more uniform noise rise distribution for
channel aware scheduling and a better UL performance, including throughput, especially
for the VoLTE spectrum with small physical resource block (PRB) allocation.

Technical description
CAS Srel Noise Rise Improvement is build on top of the CAS Noise Rise Reduction
functionality. The CAS Noise Rise Reduction functionality distributes the physical uplink
shared channel (PUSCH) PRB resources randomly when the Interference Aware Scheduler
(IAS) or the Channel Aware Scheduler (CAS) is used. Randomly distributed PRB resource
allocation helps reduce the inter-cell interference spikes that occur due to PUSCH PRBs
always being allocated in the same location. The CAS Noise Rise Reduction functionality is
enabled with the LNCEL Activate PUSCH PRB Distribution
(actPuschPrbDistribution) parameter.

The purpose of CAS Srel Noise Rise Improvement is to enhance the PUSCH PRB distribution
algorithm by using the average relative signal-to-interference-plus-noise (SINR) metric in a
preferred PRB area. This functionality is enabled with the LNCELActivate PUSCH PRB

148 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
distribution enhancement (actPuschPrbDistributionEnh) parameter.

Note:

The SINR calculations are done on a PRB basis across all UEs, with the precision of 0.5
dB.

Related features
LTE46: Channel Aware Scheduler (UL)
LTE619: Interference Aware UL Scheduling
CAS Noise Rise Reduction

Related parameters

Table 8: Parameters introduced by CAS Srel Noise Rise Improvement

Path Full name Abbreviated Name

MRBTS/LNBTS/LNCEL Activate PUSCH PRB actPuschPrbDistribution

distribution Enh
enhancement

Table 9: Parameters related to CAS Srel Noise Rise Improvement

Path Full name Abbreviated Name

MRBTS/LNBTS/LNCEL Activate PUSCH PRB actPuschPrbDistributio

Distribution n

3.3 SRAN20B performance changes

3.3.1 Active Mode Load Equalization (AMLE) RSRP/RSRQ

Source Thresholds
This enhancement allows active mode load equalization (AMLE) inter-frequency handover
for the source cell edge users located in a low-frequency RF band.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 149

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Note:

The functionality introduced with this change becomes the CB006602: Source Cell
Quality-Based Active Mode Load Equalization feature in the next release.

Technical description
This change introduces source cell Reference Signal Received Power (RSRP) or serving cell
Reference Signal Received Quality (RSRQ) thresholds for AMLE inter-frequency handover,
which can be set for additional radio quality checks for the candidate UE selection.

The following LNCEL parameters are introduced:

Activate AMLE serving cell threshold filtering
(actAmleServCellFilter)
AMLE serving cell RSRP threshold filter (amleServCellThreshRsrp)
AMLE serving cell RSRQ threshold filter (amleServCellThreshRsrq)

When the LNCEL Activate AMLE serving cell threshold filtering

(actAmleServCellFilter) parameter value is set to true, you have the flexibility to
configure the serving cell RSRP (LNCEL AMLE serving cell RSRP threshold filter
(amleServCellThreshRsrp)) and RSRQ (LNCEL AMLE serving cell RSRQ
threshold filter (amleServCellThreshRsrq)) thresholds as follows:
Single-entry configuration, that is, either the serving cell RSRP or the serving cell RSRQ
threshold is configured. For this configuration, the UE AMLE handover is allowed if the
serving cell RSRP or RSRQ is equal to or higher than the corresponding threshold.
Dual-entry configuration, that is, both the serving cell RSRP and the serving cell RSRQ
thresholds are configured. For this configuration, the UE AMLE handover is allowed if the
serving cell RSRP and RSRQ are equal to or higher than the corresponding threshold.

Related features
LTE1841: Inter-Frequency Load Equalization

Related parameters

150 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Table 10: Parameters related to the RSRP and RSRQ thresholds

Path Full name Abbreviated name

LNCEL Activate active mode actAmle

load equalization

3.3.2 Update the filtering for the

RxAntennaSignalLevelDifferenceTooHigh fault and alarm
Filter configuration for alarm 7116 BASE STATION SERVICE PROBLEM, fault 134
EFaultId_RxAntennaSignalLevelDifferenceTooHighAl requires operator
environment adaptation.

Alarm 7116 BASE STATION SERVICE PROBLEM with fault 134

EFaultId_RxAntennaSignalLevelDifferenceTooHighAl indicates the difference
between the maximum and minimum power levels of all RX antennas in the same cell and
sector that exceeds the defined limit for a cell.

The current defined time limit for triggering the fault has been modified from the prior 600
s to 7200 s (two hours). The fault condition must be present for two hours without toggling
off in order for the alarm to be raised.

If the fault condition has been cleared after 600 s (ten minutes), the alarm is also cleared.

3.3.3 TDD massive MIMO performance changes in

SRAN20B
Changes introduced to enhance and improve the TDD massive MIMO functionality in
SRAN20B.

3.3.3.1 Configurable TDD mMIMO UE beam pattern

Beam management enhancements for massive MIMO (mMIMO) are introduced to improve
network performance.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 151

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Technical description
The following changes are introduced to improve network performance:
Eigenvalue Based Beamforming (EBB) beams (instead of taped beams) can be used on a
transmission time interval (TTI) basis while the UE is not paired. This provides
approximately 3 dB gain for single-user MIMO.
A 25 dB tapering setting is introduced (in addition to the existing 30 dB tapering setting)
for both horizontal and vertical beams. This allows for additional options for beam
selection.
New parameters that allow for TDD mMIMO beam pattern configuration.

Related parameters

152 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Table 11: Parameters related to configurable TDD mMIMO UE beam pattern

Path Full name Abbreviated name

LNCEL_TDD MU-MIMO beam interference dlMuBfIcMethodH

cancellation method selection
in horizontal direction for
downlink TDD mMIMO

LNCEL_TDD MU-MIMO beam interference dlMuBfIcMethodV

cancellation method selection
in vertical direction for
downlink TDD mMIMO

LNCEL_TDD MU-MIMO beam interference ulMuBfIcMethodH

cancellation method selection
in horizontal direction for
uplink TDD mMIMO

LNCEL_TDD MU-MIMO beam interference ulMuBfIcMethodV

cancellation method selection
in vertical direction for
uplink TDD mMIMO

LNCEL_TDD The maximum allowed value of dlMaxBfGain

downlink beamforming gain for
TDD mMIMO

LNCEL_TDD The coefficient for dlBfGainCoeff

restriction of downlink
beamforming gain for TDD
mMIMO

LNCEL_TDD The aging coefficient to bfWeightAgingCoeff

calculate beamforming weight

LNCEL_TDD The maximum multiplexing ulMaxNumLayerPerMuPRB

layers per MU PRB for uplink
MU-MIMO of TDD mMIMO

Expected impact on performance counters

There are no related counters.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 153

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
3.3.3.2 Configurable options for OLLA handling for MIMO
mode control and OLLA initialization during rank switch
The enhancement for Physical Downlink Shared Channel (PDSCH) outer loop link
adaptation (OLLA) introduced in a previous release can now be enabled or disabled
depending on the operator's needs.

Technical description
An enhancement for PDSCH OLLA was introduced in release LTE19, which caused some
observable degradation for DL throughput, block error rate (BLER) and call drop rate (CDR).

This enhancement can now be enabled or disabled, depending on the operator's needs,
using a new parameter, LNCEL_TDD The enhancement of OLLA initialization
for downlink rank switching activation in TM8
(actDlOllaInitEnhForTm8RankSwitch). The enhancement is disabled by default.

Other parameters are introduced to enable or disable, as well as restrict, the delta channel
quality indicator (CQI) initialization enhancements that occur during rank switching.

Related parameters
The following parameters are introduced:
LNCEL_TDD The maximum delta CQI for mode control of downlink
beamforming (dlMaxDeltaCqiForBfModeCtrl)
LNCEL_TDD The enhancement of DL OLLA for mode control of
beamforming activation (actDlOllaEnhForBfModeCtrl)
LNCEL_TDD The enhancement of OLLA initialization for downlink rank
switching activation in TM8 (actDlOllaInitEnhForTm8RankSwitch)

Expected impact on performance counters

There are no related counters.

3.3.3.3 Extended BF weight using delay timer based on

SRS quality
The timer that determines switching to a UE specific beamforming mode can be delayed

154 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
based on sounding reference signal (SRS) quality.

Technical description
The SRS strength is not always good enough for each UE, making beamforming unstable for
the impacted UEs.

Without this enhancement, the timer that dictates when the UE switches to a UE specific
beamforming mode from a sector beam mode has a fixed value across the cell. This does
not fit all possible situations.

With the enhancement, the timer can be delayed (based on SRS strength) before switching
to using beamforming weight in TDD massive MIMO (mMIMO). This improves beamforming
stability - if the SRS is worse, the timer becomes longer, which means that the UE will be in
the sector beam longer.

Note:

If this enhancement is enabled, and the LNCEL_TDD The timer to delay using
service beamforming weight (delayUseBfWeightTimer) parameter is set to
a value that is too short, then the call drop rate may increase.

Related parameters
The following parameters are introduced:
LNCEL_TDD Extended timer to delay to use beamforming weight
activation (actExtendedDelayToUseBfWeightTimer)
LNCEL_TDD Target Sounding reference signal power (targetSrsPower)
LNCEL_TDD Scaling factor of extended delay timer
(extendedDelayFactor)
LNCEL_TDD The timer to delay using service beamforming weight
(delayUseBfWeightTimer)

Expected impact on performance counters

There are no related counters.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 155

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
3.3.3.4 Dynamic TDD mMIMO vertical sector beamforming
adaptation
Dynamic TDD massive MIMO (mMIMO) sector beamforming adaptation based on time or
traffic is introduced.

Technical description
This change introduces dynamic TDD mMIMO vertical sector beamforming adaptation based
on time and traffic in the areas where TDD mMIMO is deployed. This reduces performance
issues related to user location, traffic distribution, and peak usage hours.
The dynamic switching of vertical sector beamforming profile adjusts the cell coverage and
load to optimize the critical mMIMO performance such as UE throughput. Two beamforming
profiles (one for busy-hour and one for non-busy-hour times) are introduced, each with
different electronic tilts (e-tilts). An e-tilt is a way to control the downtilt of a beam by
modifying antenna elements to adjust the beam tilt.

Switching between the sector beamforming profile depends on the newly defined policies
introduced by the enhancement:
Time-based policy - switching to sector beamforming profiles is done automatically
based on the time of day. This is suitable for cells with a stable busy-hour traffic pattern.
Traffic-based policy - switching to sector beamforming profiles is triggered based on UE
throughput, cell load, and the average number of active UEs.

This enhancement applies to ABIA and ABIC (32TRX and 64TRX antennas).

Note:

This enhancement is replaced by the CB006432: Dynamic TDD mMIMO Sector

Beamforming Weight Switching feature starting from the SRAN20C release. The
LNCEL_TDD Activate Adaptive Vertical Sector BF Weight
(actAdptSectorBfWeightV) parameter is removed and a new activation
parameter, LNCEL Activate Adaptive Sector BF Weight
(actAdptSectorBfWeight), is introduced.

Related parameters
The following parameters are introduced:
LNCEL_TDD Sector BF Weight Change Profile based on Traffic

156 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
(sectorBfWeightChgPrfTraffic)
LNCEL_TDD Downlink PRB usage threshold (dlPrbUsageThr)
LNCEL_TDD Downlink user throughput decrease rate threshold
(dlUserTputDcrRateThr)
LNCEL_TDD Downlink user trhoughput threshold (dlUserTputThr)
LNCEL_TDD RRC connected UEs increasing rate threshold
(numRrcConnUeIncRateThr)
LNCEL_TDD Start Monitor time hour (startMonitorHour)
LNCEL_TDD Sector BF Weight Change Profile (sectorBfWeightChgProf)
LNCEL_TDD Delta of electronic down tilt angle for high load
(deltaElecDownTiltHighLoad)
LNCEL_TDD Delta of electronic down tilt angle for low load
(deltaElecDownTiltLowLoad)
LNCEL_TDD Start switch time hour for high load
(startSwitchHourHighLoad)
LNCEL_TDD Start switch time hour for low load
(startSwitchHourLowLoad)
LNCEL_TDD Start switch time minute for high load
(startSwitchMinuteHighLoad)
LNCEL_TDD Start switch time minute for low load
(startSwitchMinuteLowLoad)

Expected impact on performance counters

The following counters are introduced:
M8010C194: Delta E-Tilt Angle for Sector Beamforming
M8010C195: Average Cell Thoughput for Sector Beamforming
M8010C196: Average Number of UEs Transmitting Data in parallel

3.3.3.5 TDD massive MIMO MU-MIMO pairing

enhancement
An enhancement to multi-user (MU)-MIMO pairing based on the grid-of-beam (GoB) pre-
grouping principle is introduced to TDD massive MIMO.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 157

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Technical description
The enhancement is based on the grid-of-beam (GoB) pre-grouping principle for UE pairing.
The scheduler divides UEs into beam groups and sub-groups, which increases cell
throughput.

The beam group is defined as separate beams where the users have a high possibility of
pairing. The scheduler prioritizes the UEs within the beam group with the highest TD metric.
It is defined by the combined metrics of all the users within that specific beam group.

The sub-groups are composed of each beam grid within a beam group. The scheduler
prioritizes the UEs from different sub-groups within its corresponding beam group.

The sector beam is classified as a special group in which UEs cannot be paired, and the
scheduler reserves resources for this beam group.

Related parameters
The enhancement is activated using bit #5 of the temporary parameter LNCEL Temporary
activation flags #1 (tmpActFeat1).

In addition, the following temporary parameters are used to configure this enhancement:
LNCEL Temporary parameter #7 (tmpParam7)
This parameter sets the number of the subgroup with user scaling factor.
LNCEL Temporary parameter #8 (tmpParam8)
This parameter sets the sector beam group weight.
LNCEL Temporary parameter #1 (tmpParam1)
This parameter sets the scaling factor for the scheduling metric.

The temporary parameters are replaced by the following in the SRAN20C release:
LNCEL_TDD Activate Downlink Pre-grouping for mMIMO MU
(actDlPreGrouping)
LNCEL_TDD Massive MIMO GoB(Grid of beam) TD metric factor for
downlink (mMimoGoBTdMetricFactorDl)
LNCEL_TDD Sector beam group weight (sectorBeamGrpWeight)
LNCEL_TDD Scaling factor for number of subgroup (scaleNumSubGrp)

Expected impact on performance counters

There are no related counters.

158 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
3.3.4 FDD massive MIMO performance changes in
SRAN20B
Changes to the system introduced by FDD massive MIMO features in SRAN20B

3.3.4.1 Skipping periodic PMI reports and polling aperiodic

PMI reports for LTE FDD mMIMO
This enhancement allows the operator to disable beamforming for TM9 downlink
transmissions based on periodic PMI reports to avoid misreporting of beamforming
feedback and corresponding channel state information for all TM9 UEs. Instead, aperiodic
reports are polled and used for beamforming, link adaptation, and rank selection.

Technical description
Test results for 8-port TM9 UEs that use a specific chipset and UE software versions deliver
non-optimum PMIs for beam selection depending on the channel conditions based on
periodic reports, leading to throughput degradations in case of TM9 transmissions
dominated by periodic reports compared to aperiodic reports.

This FDD mMIMO functionality introduces the capability to skip or discard data (PMIs and
corresponding channel state information such as CQI and RI) from periodic reports, and
allows the eNB to poll aperiodic reports to counteract the impact of the inaccurate periodic
reports.

Note:

It is recommended to activate this functionality only if a significant portion of TM9

data traffic is based on TM9 UEs with limited performance of periodic reports. All TM9
UEs will be affected by this functionality if activated.

Related parameters
The following parameters are introduced:
LNCEL_FDD Activate aperiodic PMI polling function
(actAperPmiPolling)

Issue 01D. © 2022 Nokia. Nokia Confidential Information 159

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Expected impact on performance counters
There are no related counters.

3.3.4.2 Support for supplemental downlink carrier for FDD

mMIMO
Interworking with the LTE2149: Supplemental Downlink Carrier feature is introduced for
FDD massive MIMO (mMIMO).

Technical description
With the LTE2149: Supplemental Downlink Carrier feature, it is possible to have carriers
configured on the FDD mMIMO radio LTE4529: AirScale Dual MAA 16T16R B25/66 200W
AAFIA as mMIMO adaptive antenna as suplemental DL carriers. When there is no RX
configured, the antenna can be configured as PHYANT TX-only.

Each cell with mMIMO activated and configured to either 4-way TXDiv, Closed Loop
MIMO (4x2), Closed Loop MIMO (4x4), Closed Loop MIMO (8x2), or Closed
Loop MIMO (8x4) can be mapped to a DL-only carrier, as specified in the LTE2149
feature. For more information, see LTE2149: Supplemental Downlink Carrier.

Related parameters
There are no updated or introduced parameters related to this enhancement.

Expected impact on performance counters

There are no related counters.

3.3.4.3 Support for TM4 in 4x4 mode when TM9 is

configured in 8x2 mode
The enhancement enables support of up to four layers for TM4 UEs in 4x4 mode, in
addition to support for up to two layers in 4x2 mode, when transmission mode 9 (TM9) is
configured with up to two layers in 8x2 mode.

160 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Technical description
Currently, if the LTE4300 feature is enabled in 8x2 mode (the LNCEL_FDD Downlink MIMO
mode (dlMimoMode) parameter is set to the Closed Loop MIMO (8x2) option), all TM4
UEs are configured in TM4 4x2 mode only, limiting the TM4 UEs to a maximum of two layers
only. This enhancement allows the operator to add back the four-layer capability of TM4 UEs
by configuring TM4 UEs in 4x4 mode.

With this enhancement, the operator has the option to use either 4x2 or 4x4 for TM4 UEs
when the dlMimoMode parameter is set to the Closed Loop MIMO (8x2) option.

Related parameters
The enhancement is activated by bit #3 of the temporary parameter LNCEL Temporary
activation flags #1 (tmpActFeat1).

In the SRAN20C release, the enhancement is enabled when the LNCEL_FDD Control of
maximum number of spatial MIMO layers for TM4 with downlink MIMO
mode 'Closed Loop MIMO (8x2)' (maxLayerTM4with2LayerTM9) is configured. If
the parameter value is set to 2, then up to two layers for TM4 are supported; if the
parameter value is set to 4, then up to four layers of TM4 are supported.

Expected impact on performance counters

Counters for rank3 and rank4 usage for TM4 are expected to measure higher layer
transmissions using 3 and 4 layers after activation of the functionality.

3.4 SRAN20A performance changes

3.4.1 MCS/PRB selection for poor RF

Functionality which improves the LTE1495: Fast UL Link Adaptation feature with an
algorithm reducing the number of physical resource blocks (PRBs) before reducing the
modulation and coding scheme (MCS) to zero. In poor RF the UE is able to achieve better
uplink coverage and throughput when the UE sends fewer PRBs at a higher MCS versus
sending more PRBs at MCS 0.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 161

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Technical details

Note:

Since SRAN20C release, this functionality is available as the CB006620: Fast Uplink
Link Adaptation Improvement feature.

Without the MCS/PRB selection for poor RF functionality, the UL scheduler reduces the
number of PRBs only after the MCS has reached the minimum value of 0. This causes
unnecessary wait times to reduce the number of PRBs, and suboptimal coverage in non-TTI-
bundling (TTIB). Additionally, MCS 0 consumes more PRBs than otherwise needed and
reduces UL capacity.

With the introduction of the MCS/PRB selection for poor RF functionality, when the MCS
reaches MCS 6 value, the eNB will start reducing the number of PRBs to 2 before reducing
MCS to lower level as follows:

MCS 6 - 2 PRBS
MCS 5 - 2 PRBs
MCS 4 - 2 PRBs
etc.

The MCS/PRB selection for poor RF functionality can be enabled using theActivate
Uplink Scheduling for Optimized PRB / MCS Allocations
(actUlsOptimizePrbMcs) parameter. You can then select the UL MCS value that when
reached, will cause the scheduler to reduce the number of PRBs using the Uplink
Scheduling Minimum MCS for Optimized PRB Allocations
(ulsOptimizePrbMinMcs) parameter.

Note:

It's recommended to switch off the LTE907: TTI Bundling and LTE2098 VoLTE Uplink
Coverage Boosting features, as this functionality changes working entry points for the
given features.

Considering that non-TTIB VoLTE is sensitive to segmentation size and the maximum
number of hybrid automatic repeat request (HARQ) attempts in order to achieve maximum
coverage, the MCS/PRB selection for poor RF functionality introduces new parameters for
VoLTE. It's possible to configure the minimum resource block, and transport block sizes

162 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
using the Minimum Resource Blocks for Non-TTI Bundling VoLTE UEs
(ulsMinRbNonTtibVolte), and Minimum TBS for Non-TTI Bundling VoLTE UEs
(ulsMinTbsNonTtibVolte) parameters respectively.

Additionally, with the LTE4581: 256 QAM in UL feature enabled, the 256QAM-capable UEs
are handled based on the new, dedicated 3GPP table for MCS/TBS index in UL link
adaptation. UE's that don't support 256QAM are handled according to the legacy MCS/TBS
index table.

Figure 1: Updated 3GPP table for MCS/TBS index

The LTE1092: Uplink Carrier Aggregation - 2CC and LTE4050: UL Traffic-driven UL CA SCell
Configuration uplink CA features can be enabled together with the MCS/PRB selection for
poor RF.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 163

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Related features
LTE1495: Fast Uplink Link Adaptation
LTE4581: 256 QAM in UL

Management data

Table 12: Counters related to MCS/PRB selection for poor RF

Counter ID Counter name Measurement

M8012C23 PDCP_DATA_RATE_MEAN_U 8012: LTE Cell Throughput

M8012C17 RLC_PDU_VOL_RECEIVED 8012: LTE Cell Throughput

M8012C91 - IP_TPUT_VOL_UL_QCI_(1-9) 8012: LTE Cell Throughput

M8012C134

Table 13: Key performance indicators related to MCS/PRB selection for poor RF

KPI ID KPI name

LTE_5289 E-UTRAN average PDCP Layer Active Cell Throughput UL

d

LTE_5283 E-UTRAN Average RLC Layer Cell Throughput UL

LTE_5359 E-UTRAN Averaged IP scheduled Throughput in UL (QCI1–QCI9)

a
LTE_5367
a

164 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Table 14: Parameters introduced by MCS/PRB selection for poor RF

Full name Abbreviated name Path

Activate Uplink actUlsOptimizePrbMcs MRBTS/LNBTS/LNCEL

Scheduling for
Optimized PRB / MCS
Allocations

Uplink Scheduling ulsOptimizePrbMinMcs MRBTS/LNBTS/LNCEL

Minimum MCS for
Optimized PRB
Allocations

Minimum Resource Blocks ulsMinRbNonTtibVolte MRBTS/LNBTS/LNCEL

for Non-TTI Bundling
VoLTE UEs

Minimum TBS for Non-TTI ulsMinTbsNonTtibVolt MRBTS/LNBTS/LNCEL

Bundling VoLTE UEs e

Table 15: Parameters related to MCS/PRB selection for poor RF

Full name Abbreviated name Path

Activate uplink link actUlLnkAdp MRBTS/LNBTS/LNCEL

adaptation

3.4.2 QCI1, SRB, and power limits for PDCCH

Functionality that solves the problem occurring during busy hours, when physical
downlink control channel (PDCCH) resources are depleting as a result of UEs using high
number of common control element (CCEs) and power boosting together. To overcome
this, new parameters are introduced to have more PDCCH link adaptation (LA)
configuration possibilities. The new configuration can improve PDCCH performance for
important traffic without to much decrease in PDCCH capacity.

Technical details
Up to SRAN20A release, the following limits for the PDDCH resource allocation to UEs can be
configured:
the maximum allowed aggregation per UE (LNCEL Max PDCCH Aggregation
(maxPdcchAgg))

Issue 01D. © 2022 Nokia. Nokia Confidential Information 165

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
the maximum allowed aggregation per UE during high PDDCH load1) (LNCEL Max PDCCH
Aggregation During High PDCCH Load (maxPdcchAggHighLoad))
limits of the dynamically adjusted Channel Quality Indicator (CQI) shift used in PDCCH
Outer Loop Link Adaptation (OLLA) (LNCEL Max PDCCH LA CQI shift
(maxPdcchCqiShift) and LNCEL Min PDCCH LA CQI shift (minPdcchCqiShift))
the initial value of PDCCH aggregation in case there are no CQI reports available, or
PDCCH link adaptation is disabled (LNCEL PDCCH LA UE default aggregation
(pdcchAggDefUe))

Since SRAN 20A release, if the LNCEL Activate PDCCH QCI1 and SRB based
control (actPdcchQci1SrbControl is set to true, the separate set of limits for QCI1
and SRB bearers can be configured. Separate limits allow you to apply more robust PDCCH
settings without severely impacting PDCCH capacity. PDDCH settings for other QCIs remain
under control of previous parameters. The following limits can be configured:
the maximum allowed aggregation per UE with QCI1 bearer (LNCEL Max PDCCH
Aggregation QCI1 (maxPdcchAggQci1))
maximum allowed aggregation per DL SRB (LNCEL Max PDCCH Aggregation SRB
(maxPdcchAggSrb))
the maximum allowed aggregation per UE with QCI1 during high PDDCH load (LNCEL Max
PDCCH Aggregation During High PDCCH Load for QCI1
(maxPdcchAggHighLoadQci1))
the maximum allowed aggregation per DL SRB during high PDDCH load (LNCEL Max
PDCCH Aggregation During High PDCCH Load for SRB
(maxPdcchAggHighLoadSrb))
CQI link adaptation offset applied to downlink transmissions containing SRB1 messages
(LNCEL Downlink SRB1 CQI offset (dlSrbCqiOffset))
CQI link adaptation offset applied to DL transmissions with QCI1 data (LNCEL PDCCH
CQI offset for QCI1 (pdcchCqiOffsetQci1))
limits of the dynamically adjusted CQI1 shift used in PDCCH Outer Loop Link Adaptation
(OLLA) (LNCEL Max PDCCH LA CQI shift for QCI1 (maxPdcchCqiShiftQci1)
and LNCEL Min PDCCH LA CQI shift for QCI1 (minPdcchCqiShiftQci1))
the initial value of PDCCH aggregation for QCI1 and SRB bearers (LNCEL PDCCH LA UE
default aggregation for QCI1 (pdcchAggDefUeQci1) and LNCEL PDCCH LA UE
default aggregation for SRB (pdcchAggDefUeSrb ))

Related features
LTE749: Link Adaptation for PDCCH

166 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
LTE1035: Outer Loop Link Adaptation for PDCCH

Management data

Table 16: Parameters introduced by QCI1, SRB, and power limits for PDCCH

Full name Abbreviated name Path

Max PDCCH Physical maxPhyCces MRBTS/LNBTS/LNCEL

CCEs

Max PDCCH Aggregation maxPdcchAgg MRBTS/LNBTS/LNCEL

Max PDCCH Aggregation maxPdcchAggQci1 MRBTS/LNBTS/LNCEL

QCI1

Max PDCCH Aggregation maxPdcchAggSrb MRBTS/LNBTS/LNCEL

SRB

Max PDCCH Aggregation maxPdcchAggHighLoad MRBTS/LNBTS/LNCEL

During High PDCCH Load

Max PDCCH Aggregation maxPdcchAggHighLoadQci MRBTS/LNBTS/LNCEL

During High PDCCH Load 1
for QCI1

Max PDCCH Aggregation maxPdcchAggHighLoadSrb MRBTS/LNBTS/LNCEL

During High PDCCH Load
for SRB

Max PDCCH LA CQI shift maxPdcchCqiShift MRBTS/LNBTS/LNCEL

Min PDCCH LA CQI shift minPdcchCqiShift MRBTS/LNBTS/LNCEL

Downlink SRB1 CQI dlSrbCqiOffset MRBTS/LNBTS/LNCEL

offset

PDCCH CQI offset for pdcchCqiOffsetQci1 MRBTS/LNBTS/LNCEL

QCI1

PDCCH LA UE default pdcchAggDefUe MRBTS/LNBTS/LNCEL

aggregation

Max PDCCH LA CQI shift maxPdcchCqiShiftQci1 MRBTS/LNBTS/LNCEL

for QCI1

Min PDCCH LA CQI shift minPdcchCqiShiftQci1 MRBTS/LNBTS/LNCEL

for QCI1

PDCCH LA UE default pdcchAggDefUeQci1 MRBTS/LNBTS/LNCEL

aggregation for QCI1

Issue 01D. © 2022 Nokia. Nokia Confidential Information 167

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Full name Abbreviated name Path

PDCCH LA UE default pdcchAggDefUeSrb MRBTS/LNBTS/LNCEL

aggregation for SRB

1)
When scheduler wants to increase number of PDCCH symbols but LNCEL_FDD/LNCEL_TDD
Maximum number of OFDM symbols for PDCCH (maxNrSymPdcch) is already reached,
high PDCCH load is declared.

3.4.3 CAS Noise Rise Reduction

Functionality which allows more uniform noise rise distribution in neighboring cells when
Interference Aware Scheduling (IAS) or Channel Aware Scheduling (CAS) is used. It results
in a better UL performance, especially for VoLTE with small physical resource block (PRB)
allocations.

Technical details
The purpose of CAS Noise Rise Reduction is to distribute the physical uplink shared channel
(PUSCH) PRB allocations more randomly when IAS or CAS is used. More randomly distributed
PRB allocations will help to reduce inter-cell interference spikes that are occurring due to
PUSCH PRBs always being allocated in the same location. This functionality is enabled with
LNCEL Activate PUSCH PRB Distribution (actPuschPrbDistribution)
parameter.

Related features
LTE46: Channel-aware Scheduler (UL)
LTE619: Interference-aware UL Scheduling

Management data

168 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Table 17: Counters impacted by CAS Noise Rise Reduction

Counter ID Counter name Measurement

M8056C0 - Mean Uplink RIP for PRB0 - PRB99 8056: LTE Received Interference
M8056C99 Power

M8056C100 Maximum Uplink RIP for PRB0 - PRB99 8056: LTE Received Interference
- Power
M8056C199

Table 18: Parameters introduced by CAS Noise Rise Reduction

Full name Abbreviated name Path

Activate PUSCH PRB actPuschPrbDistributi MRBTS/LNBTS/LNCEL

Distribution on

3.5 LTE19B performance changes

3.5.1 Load Adaptive Uplink PF Scheduling

Functionality that improves network efficiency by allowing the operator to configure
adaptive (depending on the UE radio conditions) proportional fair (PF) scheduling
algorithm for UL.

Technical details
PF scheduling ensures high cell throughput by favoring UEs in good radio conditions while
still providing fair amount of resources to UEs in worse condition. The formula for PF
scheduling is shown on the picture below.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 169

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Figure 2: PF scheduling formula

Numerator of the formula represents immediate throughput of the given UE. The UEs in
good conditions will have higher possible throughput per subframe and bigger chances of
being scheduled.

Denominator of the formula represents average throughput of the given UE. The UEs in bad
conditions will have lower average throughput due to UEs with better conditions being
prioritized, which increases chances of UE being scheduled.

Up to release LTE19, the alpha factor in the numerator of formula was equal to 1. Since
LTE19, the alpha factor can be modified, allowing to adjust the scheduling to required
purposes:
Increasing the value will favor UEs in good conditions leading to higher cell throughput in
congestion.
Lowering the value will favor UEs in worse conditions leading to more consistent user
experience.

In LTE19B, Load Adaptive Uplink PF Scheduling can be enabled for UL using LNCEL
Activate UL Load adaptive PF algorithm for TD and FD scheduling
steps (actUlsLdAdaptPf) parameter. If it is set to true, the following LNCEL parameters
must be configured:
Load threshold for turning on UL Adaptive Proportional Fair (PF)
Scheduler (ulAdaptPfLoadThresh)
PF alpha to be used when UL instantaneous spectral efficiency is
higher than rInstUlHigh (ulsPfAlphaHigh)
PF alpha to be used when UL instantaneous spectral efficiency is
lower than rInstUlLow (ulsPfAlphaLow)
PF alpha to be used when UL instantaneous spectral efficiency is
between rInstUlLow and rInstUlHigh (ulsPfAlphaMid)
High water mark to trigger use of different PF Alpha metric in UL
TD and FD scheduling steps (rInstUlHigh)

170 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Low water mark to trigger use of different PF Alpha metric in UL
TD and FD scheduling steps (rInstUlLow)

Also, LNCEL Cell resource sharing mode (cellResourceSharingMode) must be

set to none. The relationship between the parameters is shown in the figure below.

Figure 3: UL PF scheduling parameters

If UEs in good conditions will be favored by alpha parameter settings, then following key
performance indicator (KPI) is expected to show improvements in high load scenario:
LTE_5748a UL Spectral efficiency

Management data

Table 19: KPIs related to Load Adaptive Uplink PF Scheduling

KPI ID KPI name

LTE_5748a UL Spectral efficiency

Issue 01D. © 2022 Nokia. Nokia Confidential Information 171

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Table 20: Parameters introduced by Load Adaptive Uplink PF Scheduling

Full name Abbreviated name Path

Activate UL Load actUlsLdAdaptPf MRBTS/LNBTS/LNCEL

adaptive PF algorithm
for TD and FD
scheduling steps

Load threshold for ulAdaptPfLoadThresh MRBTS/LNBTS/LNCEL

turning on UL Adaptive
PF Scheduler

PF alpha to be used ulsPfAlphaHigh MRBTS/LNBTS/LNCEL

when UL instantaneous
spectral efficiency is
higher than rInstDlHigh

PF alpha to be used ulsPfAlphaLow MRBTS/LNBTS/LNCEL

when UL instantaneous
spectral efficiency is
lower than rInstDlLow

PF alpha to be used ulsPfAlphaMid MRBTS/LNBTS/LNCEL

when UL instantaneous
spectral efficiency is
between rInstDlLow and
rInstDlHigh

High water mark to rInstUlHigh MRBTS/LNBTS/LNCEL

trigger use of
different PF Alpha
metric in UL TD and FD
scheduling steps

Low water mark to rInstUlLow MRBTS/LNBTS/LNCEL

trigger use of
different PF Alpha
metric in UL TD and FD
scheduling steps

Related descriptions
Load Adaptive PF Scheduling

3.5.2 Enhanced CA Band Combination Selection

Functionality that improves Carrier Aggregation (CA) optimization by assigning to a UE
the best band combination that will provide the best estimated throughput.

172 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Technical details
The legacy CA band combination selection algorithm forms component carrier (CC)
combinations by sorting based on secondary cell (SCell) priority, biased normalized load
compare value (NLCV), UL load compare value (ULCV) (if UL CA is activated) and preferred
candidate status (if measurement-based SCell selection is activated). It doesn't consider
estimated throughput and spectral efficiency among all supported band combinations and
doesn't guarantee the best combination that will provide the highest estimated throughput.

NLCV a metric used in the Radio Admission Control (RAC) procedure to

determine the least loaded SCell candidate to be configured for
particular CA UE in the next step. NLCV biased metric value is based
on: average PDCCH load, average non-GBR PDSCH load, potential cell
resource group (CRG) shares, and value of the sFreqPrio
parameter.

The Enhanced CA Band Combination Selection introduces two new algorithms:

Throughput and Aggregate NLCV
This algorithm attempts to choose the CA candidate combination with the best
estimated throughput with the serving cells loading taken into account. A throughput and
loading factor is calculated for each candidate combination. The combination with the
highest throughput and loading factor is chosen.
Aggregate NLCV
This algorithm attempts to choose the CA candidate combination with the least
aggregate NLCV_extended_biased. The eNB first groups the CA candidate combinations by
number of CC and starting with the highest CC group. The eNB then searches for the
candidate combination that offers the least aggregate NLCV_extended_biased and the
most CCs.

Enhanced CA Band Combination Selection can be activated with CAGENB Activate

enhanced CA band combination selection (actEnhCaBandCombSel) parameter.
The enhanced algorithms are supported only when the following applies:
one-step CA addition is activated (see Advanced Step-wise SCell Addition for CA: Initial
SCellAddition in One Step)
networks supports the following 3GPP bands: 1, 3, 7, 28, and 40.
4CC CA band combinations or higher are supported by UE.

Enhanced CA Band Combination Selection can't be activated together with:

Issue 01D. © 2022 Nokia. Nokia Confidential Information 173

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
UL Carrier Aggregation features (for example LTE1092: Uplink Carrier Aggregation - 2CC
or LTE2105: TDD Uplink Intra-Band Carrier Aggregation-2CC)
LTE2276: Measurement-Based SCell Selection
LTE2275: PCell Swap
LTE3590: CA and MFBI Interworking Extensions

With activation of this functionality, the LTE_5292: E-UTRAN average PDCP Layer
Active Cell Throughput DL KPI should improve.

Management data

Table 21: KPIs related to Enhanced CA Band Combination Selection

KPI ID KPI name

LTE_5292d E-UTRAN average PDCP Layer Active Cell

Throughput DL

Table 22: Parameters introduced by Enhanced CA Band Combination Selection

Full name Abbreviated name Path

Activate enhanced CA actEnhCaBandCombSel MRBTS/LNBTS/CAGENB

band combination
selection

3.5.3 Spectrally Efficient Scheduling

Functionality that improves the spectral efficiency of the DL data transmitted on the
physical downlink shared channel (PDSCH) thanks to three new functions.

Technical details
The Spectrally Efficient Scheduling introduces the following functionalities:
Minimize DL non-GBR UEs scheduled per TTI
MCS Upgrade
Fast PDCCH Adaptation

174 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Minimize DL non-GBR UEs scheduled per TTI

With this functionality, the operator can configure the LNCEL Activate maximum
number of non-GBR UEs per TTI (actMaxNumUeDlNonGbr) parameter, which
specifies the maximum number of non-GBR UEs that can be scheduled per TTI.

Restricting the number of non-GBR UEs scheduled per TTI forces UEs to wait in the queue
until their proportional fair (PF) metric improves (see Load Adaptive PF Scheduling). When
the UE is scheduled, their RF conditions are typically better, and because the number of UEs
scheduled is low the UE will get a larger, more spectrally efficient allocation. However,
limiting the number of non-GBR UEs scheduled per TTI can increase latency. To fix the
latency issue, two parameters are introduced:
LNCEL Low latency additional non-GBR UE threshold
(lowLatencyAddlUeThreshold) specifies the number of non-GBR UEs in the scheduler
queue, that will trigger additional non-GBR UEs scheduling in the current TTI.
LNCEL Maximum number of additional non-GBR UEs to schedule
(maxNumUeDlNonGbrAddl) specifies the maximum additional non-GBR UEs that can be
scheduled per TTI when low latency threshold is exceeded.

This functionality can't be enabled together with:

LTE2666: Massive MIMO
LTE1382: Cell Resource Groups
LTE2462: Coordinate Scheduling for Beamforming Interference Avoidance

MCS Upgrade

When this functionality is configured (using LNCEL Activate MCS upgrade

(actMcsUpgrade) parameter), the DL scheduler increases the modulation and coding
scheme (MCS) index by one or two for DL non-GBR transmission, if the upgrade results in
the reduction of one resource block group (RGB) to transmit the same amount of data. The
following conditions must be fullfilled:
The UE transmission is an initial non-GBR transmission. MCS upgrades aren't applied to
SRB or GBR transmissions.
The UE’s non-upgraded MCS is greater than 0.
Two or three RBGs are being scheduled and the last RBG doesn't require all physical
resource blocks (PRBs).
Number of RBGs can be reduced by 1 due to MCS upgrade
UE’s DL buffer is drained.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 175

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Figure 4: Example of MCS upgrade (green - MCS increase by 1, orange - MCS increase by 2)

Fast PDCCH Adaptation

When this functionality is configured (using LNCEL Activate Fast PDCCH adaptation
(actFastPdcchAdapt) parameter), the PDCCH link adaptation will quickly adjust the
physical downlink control channel (PDCCH) symbols to be the smallest number required to
support the cell’s traffic. The fewer symbols used for PDCCH the more symbols are available
for PDSCH data transmissions which improves spectral efficiency. The number of PDCCH
symbols depends on the internal PDCCH fast adapt counter. The following parameters
that impact this counter are introduced:
LNCEL Fast PDCCH adaptation step up size (fastPdcchAdaptStepUpSize)
Specifies the amount that will be added to the PDCCH fast adapt counter when there
are insufficient PDCCH resources for the load in the current TTI. Once the PDCCH fast
adapt counter exceeds a threshold, the PDCCH will be increased by one symbol. The
maximum number of PDCCH symbols that can be expanded to is defined by
LNCEL_FDD/TDD Maximum number of OFDM symbols for PDCCH
(maxNrSymPdcch).
LNCEL Fast PDCCH adaptation step down size
(fastPdcchAdaptStepDownSize)
Specifies the amount that will be decremented from the PDCCH fast adapt counter when
there are more PDCCH resources than is required for the load in the current TTI. Once
the PDCCH fast adapt counter is less than a threshold, the PDCCH will be reduced by one
symbol.
LNCEL Fast PDCCH adaptation blocked UE threshold
(fastPdcchAdaptBlockedUeThreshold)
Specifies a threshold for number of UEs that could not be scheduled in current TTI due to
PDCCH hashing collisions. A step down cannot be performed if the number of blocked

176 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
UEs is above this threshold.

This functionality can't be enabled together with:

LTE616: Usage based PDCCH Adaptation
LTE939: Usage based PDCCH Adaptation

The Spectrally Efficient Scheduling can be verified by checking following KPIs:

LTE_5276b: E-UTRAN average PRB usage per TTI DL
LTE_535(4-8)a: E-UTRAN Averaged IP scheduled Throughput in DL,
QCI(5-9)
LTE_5747a: DL Spectral efficiency

Management data

Table 23: KPIs related to Spectrally Efficient Scheduling

KPI ID KPI name

LTE_5276b E-UTRAN average PRB usage per TTI DL

LTE_5354a E-UTRAN Averaged IP scheduled Throughput in DL,

QCI5

LTE_5355a E-UTRAN Averaged IP scheduled Throughput in DL,

QCI6

LTE_5356a E-UTRAN Averaged IP scheduled Throughput in DL,

QCI7

LTE_5357a E-UTRAN Averaged IP scheduled Throughput in DL,

QCI8

LTE_5358a E-UTRAN Averaged IP scheduled Throughput in DL,

QCI9

LTE_5747a DL Spectral efficiency

Issue 01D. © 2022 Nokia. Nokia Confidential Information 177

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Table 24: Parameters introduced by Spectrally Efficient Scheduling

Full name Abbreviated name Path

Activate maximum number of actMaxNumUeDlNonGbr MRBTS/LNBTS/LNCEL

non-GBR UEs per TTI

Low latency additional non- lowLatencyAddlUeThreshold MRBTS/LNBTS/LNCEL

GBR UE threshold

Maximum number of maxNumUeDlNonGbrAddl MRBTS/LNBTS/LNCEL

additional non-GBR UEs to
schedule

Activate MCS upgrade actMcsUpgrade MRBTS/LNBTS/LNCEL

Activate Fast PDCCH actFastPdcchAdapt MRBTS/LNBTS/LNCEL

adaptation

Fast PDCCH adaptation step fastPdcchAdaptStepUpSize MRBTS/LNBTS/LNCEL

up size

Fast PDCCH adaptation step fastPdcchAdaptStepDownSize MRBTS/LNBTS/LNCEL

down size

Fast PDCCH adaptation fastPdcchAdaptBlockedUeThr MRBTS/LNBTS/LNCEL

blocked UE threshold eshold

3.6 LTE19A performance changes

3.6.1 QCI Specific UL Power Control

Functionality that optimizes power control of physical uplink shared channel (PUSCH) by
allowing to use different UL power control threshold settings for different QoS QCIs and
modulations values.

Technical Details
The QCI Specific UL Power Control functionality enhances the LTE28: Closed Loop UL Power
Control feature. With this functionality, the thresholds and values in the power control
decision matrix for PUSCH can be configured.

178 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Figure 5: Power control decision matrix

The QCI Specific UL Power Control can be activated with LNBTS Activate
Differentiation for PUSCH closed loop power control (actUlpcDiffPusch)
parameter. When functionality is activated, the Differentiation for PUSCH Closed
Loop Power Control (DPCLPC) MO needs to be configured with all mandatory
parameters. This functionality is active only when the LNCEL Method for UL power
control (actUlpcMethod) is set to one of the following values: PuschCLPucchOL,
PuschCLPucchCL, PuschCLSrsPucchOL, or PuschCLSrsPucchCL. The functionality
activation should be considered by operators with premium subscription UEs using a specific
QCI and modulation.

With QCI Specific UL Power Control functionality, different threshold in the power control
decision matrix can be assigned depending on the bearer QCI or modulation values. See
tables below for more information.

Table 25: Parameters and scenarios for the decision matrix

Decision matrix Scenario 1, 5, 6 Scenario 2 Scenario 3,4

threshold

LOW_QUAL ulpcLowqualSch ulpcDiffLowQual ulpcDiffLowQual6

4

UP_QUAL ulpcUpqualSch ulpcDiffUpQual ulpcDiffUpQual64

LOW_LEV ulpcLowlevSch ulpcDiffLowLev ulpcDiffLowLev64

UP_LEV ulpcUplevSch ulpcDiffUpLev ulpcDiffUpLev64

FILTER_OUTPUT_PERIOD ulpcReadPeriod ulpcDiffReadPeriod

Issue 01D. © 2022 Nokia. Nokia Confidential Information 179

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Table 26: Scenarios explanation for the decision matrix

Scenario QCI Specific UL Power UE modulation ulpcDiffAllQci UE's bearer with

Control status 64Qam value QCI configured
using
ulpcDiffTgtQci

1 Disabled - - -

2 Enabled Lower than 64QAM - yes

3 Enabled Equal or higher than false or true yes

64QAM

4 Enabled Equal or higher than true no

64QAM

5 Enabled Equal or higher than false no

64QAM

6 Enabled Lower than 64QAM - no

Values in the power control decision matrix quadrant 1 and quadrant 9 are configurable with
DPCLPC TPC Direction for Quad 1 of differentiated PUSCH ULPC Decision
Matrix (ulpcDiffTpcDirQuad1) and TPC Direction for Quad 9 of
differentiated PUSCH ULPC Decision Matrix (ulpcDiffTpcDirQuad9) (changed
from a fixed Up to Up or Down). If a quadrant is set to Up, the change in PUSCH power (δPUSCH
) equals +1dB or + 3dB, like in solution known from the LTE28 feature. If a quadrant is Down,
the δPUSCH equals -1dB.

180 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Figure 6: Updated power control decision matrix

Two additional parameters introduced with this functionality: MCS Delta Threshold for
Up TPC with differentiated ULPC (ulpcDiffMcsThresh) and PHR Threshold
for Up TPC with differentiated ULPC (ulpcDiffPhrThresh) are disabled by
default and are recommended to not be used.

Thanks to thresholds dedicated for a QCI selected by the operator, a positive impact should
be observed in a KPI related to the average throughput for this QCI (for example
LTE_5512a-E-UTRAN Averaged IP Throughput in UL, QCI1, depending on which
QCI was selected by the operator as prioritized one using DPCLPC QCI for
differentiated PUSCH closed loop power control (ulpcDiffTgtQci)). Also,
higher UL throughput may be expected for UEs capable with 64QAM or 256QAM modulation
in UL (observed by LTE_5289d-E-UTRAN average PDCP Layer Active Cell
Throughput UL 18).

Related features
LTE28: Closed Loop UL Power Control

Management data

Table 27: Parameters introduced by QCI Specific UL Power Control

Issue 01D. © 2022 Nokia. Nokia Confidential Information 181

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Full name Abbreviated name Path

Activate Differentiation actUlpcDiffPusch MRBTS/LNBTS

for PUSCH closed loop power
control

Configuration of PUSCH ulpcDiffConfig64 MRBTS/LNBTS/DPCLPC

closed loop power control
for differentiation with
64QAM

Lower RSSI threshold for ulpcDiffLowLev64 MRBTS/LNBTS/DPCLPC/ulpcDiffC

differentiated TPC decision onfig64
with 64QAM

Lower SINR threshold for ulpcDiffLowQual64 MRBTS/LNBTS/DPCLPC/ulpcDiffC

differentiated TPC decision onfig64
with 64QAM

Upper RSSI threshold for ulpcDiffUpLev64 MRBTS/LNBTS/DPCLPC/ulpcDiffC

differentiated TPC decision onfig64
with 64QAM

Upper SINR threshold for ulpcDiffUpQual64 MRBTS/LNBTS/DPCLPC/ulpcDiffC

differentiated TPC decision onfig64
with 64QAM

Configuration for ulpcDiffSchConfig MRBTS/LNBTS/DPCLPC

differentiated PUSCH closed
loop power control

Lower RSSI threshold for ulpcDiffLowLev MRBTS/LNBTS/DPCLPC/ulpcDiffSc

differentiated TPC decision hConfig
per QCI

Lower SINR threshold for ulpcDiffLowQual MRBTS/LNBTS/DPCLPC/ulpcDiffSc

differentiated TPC decision hConfig
per QCI

Upper RSSI threshold for ulpcDiffUpLev MRBTS/LNBTS/DPCLPC/ulpcDiffSc

differentiated TPC decision hConfig
per QCI

Upper SINR threshold for ulpcDiffUpQual MRBTS/LNBTS/DPCLPC/ulpcDiffSc

differentiated TPC decision hConfig
per QCI

Control for differentiated ulpcDiffSchControl MRBTS/LNBTS/DPCLPC

PUSCH closed loop power
control

Differentiated 64QAM ULPC ulpcDiffAllQci64Qam MRBTS/LNBTS/DPCLPC/ulpcDiffSc

settings applied for all hControl
QCIs

MCS Delta Threshold for Up ulpcDiffMcsThresh MRBTS/LNBTS/DPCLPC/ulpcDiffSc

TPC with differentiated hControl
ULPC

PHR Threshold for Up TPC ulpcDiffPhrThresh MRBTS/LNBTS/DPCLPC/ulpcDiffSc

with differentiated ULPC hControl

182 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Full name Abbreviated name Path

Time interval for power ulpcDiffReadPeriod MRBTS/LNBTS/DPCLPC/ulpcDiffSc

command decisions with hControl
differentiated ULPC

QCI for differentiated ulpcDiffTgtQci MRBTS/LNBTS/DPCLPC/ulpcDiffSc

PUSCH closed loop power hControl
control

TPC Direction for Quad 1 of ulpcDiffTpcDirQuad1 MRBTS/LNBTS/DPCLPC/ulpcDiffSc

differentiated PUSCH ULPC hControl
Decision Matrix

TPC Direction for Quad 9 of ulpcDiffTpcDirQuad9 MRBTS/LNBTS/DPCLPC/ulpcDiffSc

differentiated PUSCH ULPC hControl
Decision Matrix

Table 28: Parameters related to QCI Specific UL Power Control

Full name Abbreviated name Path

Method for UL power actUlpcMethod MRBTS/LNBTS/LNCEL

control

Table 29: Key performance indicators related to QCI Specific UL Power Control

KPI ID KPI name

LTE_5512a E-UTRAN Averaged IP Throughput in UL, QCI

LTE_5513a E-UTRAN Averaged IP Throughput in UL, QC2

LTE_5514a E-UTRAN Averaged IP Throughput in UL, QC3

LTE_5515a E-UTRAN Averaged IP Throughput in UL, QC4

LTE_5516a E-UTRAN Averaged IP Throughput in UL, QC5

LTE_5517a E-UTRAN Averaged IP Throughput in UL, QC6

LTE_5518a UTRAN Averaged IP Throughput in UL, QC7

LTE_5519a E-UTRAN Averaged IP Throughput in UL, QC8

LTE_5519a E-UTRAN Averaged IP Throughput in UL, QC9

LTE_5289d E-UTRAN average PDCP Layer Active Cell Throughput UL 18

Issue 01D. © 2022 Nokia. Nokia Confidential Information 183

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
3.6.2 SCell configuration for high demand UEs
Functionality that improves Carrier Aggregation (CA) optimization by assigning maximum
number of component carriers (CC) only to the UEs that will benefit from it.

Technical Details
With Advanced Step-wise SCell Addition for CA: Initial SCellAddition in One Step activated, the
maximum number of CA CC is added in one-step secondary cells (SCells) addition procedure
for all UEs, and then eNB starts inactivity monitoring to allow SCells to be de-configured and
added back as needed. This is not optimal solution, as number of CC per UE should depend
on the actual needs of the UE (UE’s existing data buffer depth). This can result in higher RRC
messaging, which can be mitigated by increasing the LNBTS Number of sampled
subframes with High Non-GBR traffic (numTxWithHighNonGbr parameter value.
However, increasing numTxWithHighNonGbr will also increase CA configuration delay.

The SCell configuration for high demand UEs functionality allows the SCell addition to occur
only if sufficient throughput improvement will result (based on a configurable threshold that
is separate from the SCell activation threshold). Thanks to this functionality, the operator
can use larger throughput threshold for SCell addition, without impacting SCell activation.
With the larger throughput threshold, the operator can decrease the
numTxWithHighNonGbr parameter value to reduce the CA configuration delay while still
maintaining an acceptable level of RRC messaging.

The SCell configuration for high demand UEs can be activated with LNCEL Activate SCell
configuration for high demand UEs (actScellConfigForHiDemand) parameter.
It can be activated only if LNBTS Number of sampled subframes with High Non-
GBR traffic (numTxWithHighNonGbr) is higher than 0. When it is activated, the eNB
uses LNCEL Minimum TTI to empty buffer in DL to trigger SCell
configuration (dlScellConfigLevel) parameter for the SCell configuration purpose
instead of the LNBTS Conservativeness level of SCell activation
(scellActivationLevel) parameter.

The following algorithm of SCell addition is used since introduction of this functionality:

184 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Figure 7: Algorithm of SCell addition

Management data

Table 30: Parameters introduced by SCell configuration for high demand UEs

Full name Abbreviated name Path

Activate SCell actScellConfigForHiDema MRBTS/LNBTS/LNCEL

configuration for high nd
demand UEs

Minimum TTI to empty dlScellConfigLevel MRBTS/LNBTS/LNCEL

buffer in DL to trigger
SCell configuration

Table 31: Parameters related to SCell configuration for high demand UEs

Full name Abbreviated name Path

Number of sampled numTxWithHighNonGbr MRBTS/LNBTS

subframes with High
Non-GBR traffic

Conservativeness scellActivationLevel MRBTS/LNBTS

level of SCell
activation

Issue 01D. © 2022 Nokia. Nokia Confidential Information 185

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
3.6.3 Improved SCell handling when moving from bad to
good channel conditions
Functionality that improves Carrier Aggregation (CA) management, by fixing known error
occurring when cell conditions change from bad to good.

Technical Details
When the LTE1541: Advanced SCell Measurement Handling feature is activated, the eNB
classifies the secondary cells (SCells) channel status as good, undefined, bad, or
undetected. The classification is based on UE QCI measurements and the delta CQI used
by DL link adaptation. If bad or undetected channel status is detected, the DL SCell
scheduling is stopped but the SCell is kept active to receive the UE's CQI measurement. The
delta CQI is not updated while the UE is not scheduled. DL SCell scheduling is resumed in
case channel status is improved to good. If the CQI doesn't improve or improve not enough
to offset the delta CQI, then the SCell release timer expires and the SCell is released from
the UE. This applies to both licensed LAA SCells and unlicensed SCells.

Even if SCell channel quality had improved, the eNB does not always detect that due to the
delta CQI that was saved at the time the eNB stopped scheduling the UE. If the saved delta
CQI is large enough, even if the UE reported CQI improves, the eNB may not detect the
change in radio conditions, and the SCell may be released. With Improved SCell handling
when moving from bad to good channel conditions functionality activated (LNCEL Activate
delta CQI aging in SCell channel estimation
(actDeltaCqiAgingScellChEst) set to true), the unnecessary SCell releases can be
avoided and SCell scheduling may resume faster. With the functionality activated, when the
eNB detects bad or undetected channel status, if the delta CQI is lower than LNCEL
Delta CQI target value in SCell channel estimation
(deltaCqiTargetScellChEst), the eNB gradually reduces the delta CQI. The delta CQI is
calculated using following formula:

where α is smoothing factor, depending on number of channel status changes from good to
bad or undetected (called numberOfTransitions).If numberOfTransitions equal 0, then

If numberOfTransitions is higer than 0, then

186 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
N in above formulas is number of samples, calculated using

where
LNCELDelta CQI aging window in SCell channel
estimationdeltaCqiAgingWinScellChEst is a new parameter
MCS_Sampling_Interval equals to 20 ms or 40 ms in FDD (depending on CPU load) and 80
ms in TDD.

Related features
LTE1541: Advanced SCell Measurement Handling
LTE2860: Licensed – Assisted Access
LTE31: Link Adaptation by AMC (UL/DL)
LTE1803: Downlink Carrier Aggregation 3 CC - 40 MHz

Management data

Table 32: Parameters introduced by QCI Specific UL Power Control

Full name Abbreviated name Path

Activate delta CQI actDeltaCqiAgingScellChE MRBTS/LNBTS/LNCEL

aging in SCell channel st
estimation

Delta CQI target value deltaCqiTargetScellChEst MRBTS/LNBTS/LNCEL

in SCell channel
estimation

Delta CQI aging window deltaCqiAgingWinScellChE MRBTS/LNBTS/LNCEL

in SCell channel st
estimation

Issue 01D. © 2022 Nokia. Nokia Confidential Information 187

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
3.7 LTE19 performance changes

3.7.1 UL TCP Power Boost

Functionality which improves data transfer in UL, by boosting transmit power of the UE.
This functionality is based on TCP Service Differentiation.

Technical details
If the TCP Service Differentiation functionality is enabled (see LTE5731: TCP Service
Differentiation), the UL TCP data transfer can be additionally boosted to allow UEs to reach
the maximum modulation and coding scheme (MCS). The additional UL TCP boost is enabled
with the LNCEL Activate TCP UL Power Boost (actTcpUlPowerBoost) parameter.

The UL TCP Power Boost can occur only if:

the LNCEL Boost guard time (boostGuardTime timer is running (introduced with
the TCP Service Differentiation),
the UE Power Headroom Report (PHR) is higher than 6 dB,
(LTE 19 release only) the UL MCS is lower from maximum possible MCS by at least 0.6,
(LTE 19A release onwards) an averaged version of MCS is below a threshold controlled by
the DPCLPC MCS Delta Threshold for Up TPC with differentiated ULPC
(ulpcDiffMcsThresh) parameter,
number of UEs already in UL Power Boost state is lower than LNCEL Max Number of
UEs in TCP UL Power Boost (maxTcpUlPowerBoostUEs) parameter.

The number of UEs simultaneously in TCP Power Boost state is limited by the
maxTcpUlPowerBoostUEs parameter. If the limit is reached, the oldest UE is released
from TCP Power Boost state.

A new counter related with this functionality is introduced: M8006C345 - total TCP boosting
duration of all ERABs in UL with Power Boost.

Management data

188 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Table 33: Counters introduced by UL TCP Power Boost

Counter ID Counter name Measurement

M8006C345 TCP_BOOST_DUR_ERABS_UL_PB 8006: LTE EPS Bearer

Table 34: Parameters introduced by UL TCP Power Boost

Full name Abbreviated name Path

Activate TCP UL Power actTcpUlPowerBoost MRBTS/LNBTS/LNCEL

Boost

Max Number of UEs in maxTcpUlPowerBoostUE MRBTS/LNBTS/LNCEL

TCP UL Power Boost s

Table 35: Parameters related to UL TCP Power Boost

Full name Abbreviated name Path

Activate TCP Service actTcpServiceDiff MRBTS/LNBTS/LNCEL

Differentiation

Boost guard time boostGuardTime MRBTS/LNBTS/LNCEL/tcpServiceDi

ffConfig

Related descriptions
LTE5731: TCP Service Differentiation

3.7.2 PDCCH CQI Shift for 4Tx

Functionality that improves network performance in 4Tx deployment by introducing new
algorithm for Chanel Quality Indicator (CQI) mapping to aggregation level for physical
downlink control channel (PDCCH).

Technical details
Before the PDCCH CQI Shift for 4Tx functionality, there was a single algorithm that maps
CQI to aggregation level for PDCCH transmission. However, it was discovered that 4Tx
Transmit Diversity results in up to 1 dB performance penalty compared to 2Tx Transmit
Diversity. Therefore, an offset for mentioned algorithm is needed to allow a slightly more

Issue 01D. © 2022 Nokia. Nokia Confidential Information 189

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
conservative choice of aggregation level with 4Tx. A new LNCEL PDCCH CQI shift for
4Tx (pdcchCqiShift4Tx) parameter is introduced to specify the value of the offset. Nokia
recommends to set the value of PDCCH CQI shift for 4Tx to -1.5. Lowering the value
too much can lead to too conservative aggregation levels resulting in wasted resources.
Setting this parameter to 0 disables the PDCCH CQI Shift for 4Tx.

The LNCEL PDCCH CQI shift for 4Tx (pdcchCqiShift4Tx) must be configured if
LNCEL Enable AMC for PDCCH link adaptation (enableAmcPdcch) or LNCEL
Activate outer loop link adaptation (actOlLaPdcch) is set to true. It requires
the LNCEL_FDD/TDD Downlink MIMO mode (dlMimoMode) to be set to Closed Loop
MIMO (4x2) or Closed Loop MIMO (4x4).

The LTE_5208a: E-UTRAN RLC PDU Re-transmission Ratio Downlink key

performance indicator (KPI) should improve if the functionality is configured properly.

Related features
LTE749: Link Adaptation for PDCCH
LTE1035: Outer Loop Link Adaptation for PDCCH
LTE568: DL Adaptive Closed Loop MIMO (4x2)
LTE569: Downlink Adaptive Closed Loop SU MIMO 4x4 - TM 4
LTE1987: Downlink Adaptive Closed Loop SU MIMO (4x4)

Management data

Table 36: KPIs related to UL TCP Power Boost

KPI ID KPI name

LTE_5208a E-UTRAN RLC PDU Re-transmission Ratio Downlink

Table 37: Parameters introduced by UL TCP Power Boost

Full name Abbreviated name Path

PDCCH CQI shift for 4Tx pdcchCqiShift4Tx MRBTS/LNBTS/LNCEL

190 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Table 38: Parameters related to UL TCP Power Boost

Full name Abbreviated name Path

Enable AMC for PDCCH link enableAmcPdcch MRBTS/LNBTS/LNCEL

adaptation

Activate outer loop link actOlLaPdcch MRBTS/LNBTS/LNCEL

adaptation

Downlink MIMO mode dlMimoMode MRBTS/LNBTS/LNCEL/LNCEL_F

DD or LNCEL_TDD

3.7.3 Adaptive Vocoder PRB/TBS for TTIB

Functionality that improves network optimization by calculating the minimum transport
block size (TBS) for time interval bundling (TTIB) UEs, instead of using the fixed value set
by the operator. The minimum TBS is used by link adaptation to determine the transport
block size (TBS).

Technical details

vocoder A technology of voice coding, allowing to send voice over digital

medium. A vocoder also incorporates voice compression, a technique
that effectively minimizes the number of bits used to represent voice.
LTE uses the Adaptive Multi-Rate (AMR) vocoder, which has a variable
bit-rate capability from 1.8 to 12.2 kbits/s.

Without Adaptive Vocoder PRB/TBS for TTIB, the BTS use the same LNCEL Minimum UL
TBS for UEs for TTI bundled UEs (ttibUlsMinTbs) for all vocoder rate. This leads
to the following inefficiencies in UL resources:
If operator configures a value which is optimized for high data rate voice calls, then not
enough segmentation can be achieved for low data rate voice calls. Thus, a lower cell
edge gain due to segmentation for low data rate voice calls is seen.
If operator configures a value which is optimized for low data rate voice calls, then too
much segmentation occurs for high data rate voice calls. This can lead to 100% TTI
utilization just to send the voice packet.

Adaptive Vocoder PRB/TBS for TTIB utilizes the mechanism introduced in the LTE2774:

Issue 01D. © 2022 Nokia. Nokia Confidential Information 191

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Source Rate Based UL Grant Assignment for VoLTE, that is measurement-based UL TBS
adaptation. With this functionality enabled (the LNCEL Activate adaptive UL min TBS
for TTI Bundling (actTtibAdaptUlMinTbs) set to true), the BTS calculates the
minimum TBS, taking into account:
effective bit rate (EBR), based on the measurements of the voice data
the LNCEL Maximum number of packet segmentation in TTIB
(ttibUlsMaxPacketSeg) value which defines maximum number of packet
segmentation in TTIB mode

Note:

Parameter must be carefully planned as too high value may lead to high resource
utilization (that is, to send one voice packet high number of PRBs might be used).

If the LNCEL Activate adaptive UL min TBS for TTI Bundling

(actTtibAdaptUlMinTbs) parameter is set to true, the following parameters must be
configured:
LNCEL Activate TTI bundling (actTtiBundling) must be set to true (the
LTE904: TTI Bundling is activated)
LNCEL Activate VoLTE source rate based UL assignment
(actVoLteSrcRate) must be set to true (the LTE2774: Source Rate Based UL Grant
Assignment for VoLTE is activated)
LNCEL Activation of VoIP coverage boosting in UL scheduling
(actVoipCovBoost) must be set to false (the LTE2098: VoLTE Uplink Coverage
Boosting is deactivated)

This functionality is configured properly if the following counter and key performance
indicators (KPIs) improve:
M8011C215: Number of UL PRBs used for TTI Bundling
LTE_5572f E-UTRAN E-RAB QCI1 Drop Ratio, RAN View
LTE_5311b E-UTRAN PDCP SDU LossRatio in the UL, QCI1

Related features
LTE904: TTI Bundling
LTE2774: Source Rate Based UL Grant Assignment for VoLTE
LTE2098: VoLTE Uplink Coverage Boosting

192 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Management data

Table 39: Counters related to Adaptive Vocoder PRB/TBS for TTIB

Counter ID Counter name Measurement

M8011C215 Number of UL PRBs used for 8011: LTE Cell Resource

TTI Bundling

Table 40: KPIs related to Adaptive Vocoder PRB/TBS for TTIB

KPI ID KPI name

LTE_5572f E-UTRAN E-RAB QCI1 Drop Ratio, RAN View

LTE_5311b E-UTRAN PDCP SDU LossRatio in the UL, QCI1

Table 41: Parameters introduced by Adaptive Vocoder PRB/TBS for TTIB

Full name Abbreviated name Path

Activate adaptive UL actTtibAdaptUlMinTbs MRBTS/LNBTS/LNCEL

min TBS for TTI
Bundling

Maximum number of ttibUlsMaxPacketSeg MRBTS/LNBTS/LNCEL

packet segmentation in
TTIB

Issue 01D. © 2022 Nokia. Nokia Confidential Information 193

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Table 42: Parameters related to Adaptive Vocoder PRB/TBS for TTIB

Full name Abbreviated name Path

Activate TTI bundling actTtiBundling MRBTS/LNBTS/LNCEL

Activate VoLTE source actVoLteSrcRate MRBTS/LNBTS/LNCEL

rate based UL
assignment

Activation of VoIP actVoipCovBoost MRBTS/LNBTS/LNCEL

coverage boosting in UL
scheduling

Minimum UL TBS for UEs ttibUlsMinTbs MRBTS/LNBTS/LNCEL

for TTI bundled UEs

3.7.4 Load Adaptive PF Scheduling

Functionality that improves network efficiency by allowing the operator to configure
adaptive (depending on the UE radio conditions) proportional fair (PF) scheduling
algorithm for DL.

Technical details
PF scheduling ensures high cell throughput by favoring UEs in good radio conditions while
still providing fair amount of resources to UEs in worse condition. The formula for PF
scheduling is shown on the picture below.
Figure 8: PF scheduling formula

Numerator of the formula represents immediate throughput of the given UE. The UEs in
good conditions will have higher possible throughput per subframe and bigger chances of
being scheduled.

194 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Denominator of the formula represents average throughput of the given UE. The UEs in bad
conditions will have lower average throughput due to UEs with better conditions being
prioritized, which increases chances of UE being scheduled.

Up to release LTE19, the alpha factor in the numerator of formula was equal to 1. Since
LTE19, the alpha factor can be modified, allowing to adjust the scheduling to required
purposes:
Increasing the value will favor UEs in good conditions leading to higher cell throughput in
congestion.
Lowering the value will favor UEs in worse conditions leading to more consistent user
experience.

In LTE19, Load Adaptive PF Scheduling can be enabled for DL using LNCEL Activate DL
Load adaptive PF algorithm for TD and FD scheduling steps
(actDlsLdAdaptPf) parameter. If it's set to true, the following LNCEL parameters must
be configured:
Load threshold for turning on DL Adaptive PF Scheduler
(dlAdaptPfLoadThresh)
PF alpha to be used when DL instantaneous spectral efficiency is
higher than rInstDlHigh (dlsPfAlphaHigh)
PF alpha to be used when DL instantaneous spectral efficiency is
lower than rInstDlLow (dlsPfAlphaLow)
PF alpha to be used when DL instantaneous spectral efficiency is
between rInstDlLow and rInstDlHigh (dlsPfAlphaMid)
High water mark to trigger use of different PF Alpha metric in DL
TD and FD scheduling steps (rInstDlHigh)
Low water mark to trigger use of different PF Alpha metric in DL
TD and FD scheduling steps (rInstDlLow)

The relationship between the parameters is shown in the figure below.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 195

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Figure 9: DL PF scheduling parameters

If UEs in good conditions will be favored by alpha parameter settings, then following key
performance indicators (KPIs) are expected to show improvements in high load scenario:
LTE_5354a E-UTRAN Averaged IP scheduled Throughput in DL, QCI5
LTE_5355a E-UTRAN Averaged IP scheduled Throughput in DL, QCI6
LTE_5356a E-UTRAN Averaged IP scheduled Throughput in DL, QCI7
LTE_5357a E-UTRAN Averaged IP scheduled Throughput in DL, QCI8
LTE_5358a E-UTRAN Averaged IP scheduled Throughput in DL, QCI9
LTE_5747a DL Spectral efficiency

Management data

Table 43: KPIs related to Load Adaptive PF Scheduling

KPI ID KPI name

LTE_5354a E-UTRAN Averaged IP scheduled Throughput in DL,

QCI5

LTE_5355a E-UTRAN Averaged IP scheduled Throughput in DL,

QCI6

LTE_5356a E-UTRAN Averaged IP scheduled Throughput in DL,

QCI7

LTE_5357a E-UTRAN Averaged IP scheduled Throughput in DL,

QCI8

LTE_5358a E-UTRAN Averaged IP scheduled Throughput in DL,

QCI9

LTE_5747a DL Spectral efficiency

196 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Table 44: Parameters introduced by Load Adaptive PF Scheduling

Full name Abbreviated name Path

Activate DL Load actDlsLdAdaptPf MRBTS/LNBTS/LNCEL

adaptive PF algorithm
for TD and FD
scheduling steps

Load threshold for dlAdaptPfLoadThresh MRBTS/LNBTS/LNCEL

turning on DL Adaptive
PF Scheduler

PF alpha to be used dlsPfAlphaHigh MRBTS/LNBTS/LNCEL

when DL instantaneous
spectral efficiency is
higher than rInstDlHigh

PF alpha to be used dlsPfAlphaLow MRBTS/LNBTS/LNCEL

when DL instantaneous
spectral efficiency is
lower than rInstDlLow

PF alpha to be used dlsPfAlphaMid MRBTS/LNBTS/LNCEL

when DL instantaneous
spectral efficiency is
between rInstDlLow and
rInstDlHigh

High water mark to rInstDlHigh MRBTS/LNBTS/LNCEL

trigger use of
different PF Alpha
metric in DL TD and FD
scheduling steps

Low water mark to rInstDlLow MRBTS/LNBTS/LNCEL

trigger use of
different PF Alpha
metric in DL TD and FD
scheduling steps

Related descriptions
Load Adaptive Uplink PF Scheduling

3.7.5 Data Split CA Selection

Functionality that improves network optimization, by allowing the operator to prioritize
the selected secondary cell (SCell). This way, operator can configure BTS to schedule as

Issue 01D. © 2022 Nokia. Nokia Confidential Information 197

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
much non-GBR bearer traffic as possible on certain SCell (for example, Licensed Assisted
Access (LAA) SCell).

Technical details
Without Data Split CA Selection activated, all serving cells are assigned equal non-GBR
scheduler weights when the UE is in Carrier Aggregation (CA). It results in no differentiation
for LAA or other frequency bands in CA scheduling fairness factor. The Data Split CA
Selection allows the DL scheduler to favor chosen SCells (for example for LAA instances) over
others if the operator wants to schedule as much non-GBR bearer traffic as possible on
certain cells rather than equal balance.

The Data Split CA Selection is activated with the LNCEL Activate carrier
aggregation SCell scheduler weight factor
(actCaScellSchedWeightFactor) parameter set to true. It only needs to be activated
in the LNCEL instance of the primary cell (PCell). The CAREL SCell scheduler weight
factor for downlink (scellSchedWeightFactorDl) parameter controls SCell DL
scheduler weight in relation to the PCell and other activated SCell. Only SCells with Channel
Quality Indicator (CQI) that meets or exceeds the threshold set by CAGENB or CAREL
Carrier aggregration SCell scheduler weight factor minimum CQI
(caScellSchedWtFactMinCqi) parameter are impacted by this scheduling factor.If this
parameter is configured in both CAGENB and CAREL MOs, then the CAREL value will be used.

Up to SRAN20A, the BTS applies the Scheduler Weight Factor updates on a periodic basis
approximately every 100 ms. Since release SRAN20A, this time is configurable with the
LNCEL_FDD Data split CA SCell scheduler weight factor activation
timer (caScellSchedWeightFactorTimer) parameter. The PCell starts the timer when
one of the first of following events occurs after SCell activation:
reception of valid SCell CQI
expiration of 33 ms timer that starts upon successful SCell activation

Management data

198 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Table 45: KPIs related to Data Split CA Selection

KPI ID KPI name

LTE_5212a E-UTRAN PDCP SDU Volume DL

LTE_5276b E-UTRAN average PRB usage per TTI DL

Table 46: Parameters introduced by Data Split CA Selection

Full name Abbreviated name Path

Activate carrier actCaScellSchedWeightFac MRBTS/LNBTS/LNCEL

aggregation SCell scheduler tor
weight factor

SCell scheduler weight scellSchedWeightFactorDl MRBTS/LNBTS/LNCEL/CAREL

factor for downlink

Carrier aggregration SCell caScellSchedWtFactMinCqi MRBTS/LNBTS/CAGENB

scheduler weight factor
minimum CQI

Carrier aggregration SCell caScellSchedWtFactMinCqi MRBTS/LNBTS/LNCEL/CAREL

scheduler weight factor
minimum CQI

Data split CA SCell caScellSchedWeightFactor MRBTS/LNBTS/LNCEL/LNCEL_FDD

scheduler weight factor Timer
activation timer

3.8 LTE18A performance changes

3.8.1 LTE5731: TCP Service Differentiation

Functionality which improves data transfer in DL and UL, by boosting the amount of
resources assigned to data radio bearers (DRB) with Transmission Control Protocol (TCP)
traffic.

Hardware and software requirements

Issue 01D. © 2022 Nokia. Nokia Confidential Information 199

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Table 47: LTE5731 hardware and software requirements

FDD TDD

Flexi Multiradio 10 BTS FL19B TL19B

Flexi Multiradio 10 Indoor BTS Not supported TL19B

Nokia AirScale BTS FL19B TL19B

Flexi Zone BTS Not supported Not supported

Flexi Zone Access Point Not supported Not supported

Cloud Flexi Zone Controller Not supported Not supported

Technical details
With the TCP Service Differentiation enabled (LNCEL Activate TCP Service
Differentiation (actTcpServiceDiff) parameter set to true), the scheduling weight
is multiplied by configured bias factor during TCP data transfer. The bias factor is applicable
for:
QCIs 5 to 9,
QCI 70,
operator-specific QCI,

and for each QCI is configurable separately using the LNBTS Boosting factor for
downlink (boostFactorDl) and LNBTS Boosting factor for uplink
(boostFactorUl) parameters.

With this functionality enabled, Packet Data Convergence Protocol (PDCP) layer is monitored
for TCP traffic. From the moment it is detected, the BTS starts measuring volume of TCP
data (only TCP packet with size equal or bigger than the LNCEL Minimum TCP packet
size (minTcpPacketSize) parameter are considered for this measurement). Two
thresholds are defined:
lower threshold, which is the threshold between small and medium data transfer (LNCEL
Downlink minimum boosting bytes (dlMinBoostBytes) or LNCEL Uplink
minimum boosting bytes (ulMinBoostBytes) for UL)
upper threshold, which is the threshold between medium and big data transfer (LNCEL
Downlink maximum boosting bytes (dlMaxBoostBytes) or LNCEL Uplink
maximum boosting bytes (ulMaxBoostBytes) for UL)

200 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
After reaching lower threshold, the scheduling bias is applied, resulting in a boost of data
transfer. After reaching upper threshold, the bias application is stopped, and data transfer is
not boosted anymore.

Figure 10: Algorithm of data flow boosting

Figure 11: Exemplary result of data boosting (number of PRBs allocated vs time, for three UE)

Bias application can also be prematurely stopped if:

Time between any two consecutive TCP packets exceeds the LNCEL Time between
TCP packets (timeBetweenTcpPackets) parameter's value. Only TCP packet with
size equal or bigger than the LNCEL Minimum TCP packet size
(minTcpPacketSize) parameter are considered for this check.
Handover procedure was triggered.
Another bearer for the same UE is setup, modified, deleted or bias is applied.
Configurable timer expires (configured with the LNCEL Boost guard time
(boostGuardTime) parameter).

After bias application is stopped on certain DRB, it can only be started again after
configurable period of time (configured with the LNCEL Time until next boosting
round (timeNextBoostingRound) parameter).

Issue 01D. © 2022 Nokia. Nokia Confidential Information 201

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
There are two counters related with this functionality (incremented at TCP boost stop time
or at the end of the measurement period):
M8006C337 - total TCP boosting duration of all ERABs in DL
M8006C338 - total TCP boosting duration of all ERABs in UL

This functionality is enhanced with UL TCP Power Boost.

Management data

Table 48: Counters introduced by TCP Service Differentiation

Counter ID Counter name Measurement

M8006C337 TCP_BOOSTING_DUR_ERABS_DL 8006: LTE EPS Bearer

M8006C338 TCP_BOOSTING_DUR_ERABS_UL 8006: LTE EPS Bearer

202 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Table 49: Parameters introduced by TCP Service Differentiation

Full name Abbreviated name Path

Activate TCP Service actTcpServiceDiff MRBTS/LNBTS/LNCEL

Differentiation

Boosting factor for downlink boostFactorDl MRBTS/LNBTS/qciTab[x]

Boosting factor for uplink boostFactorUl MRBTS/LNBTS/qciTab[x]

TCP Service Differentiation tcpServiceDiffConfig MRBTS/LNBTS/LNCEL

Configuration

Downlink minimum boosting dlMinBoostBytes MRBTS/LNBTS/LNCEL/tcpServiceDi

bytes ffConfig

Uplink minimum boosting ulMinBoostBytes MRBTS/LNBTS/LNCEL/tcpServiceDi

bytes ffConfig

Downlink maximum boosting dlMaxBoostBytes MRBTS/LNBTS/LNCEL/tcpServiceDi

bytes ffConfig

Uplink maximum boosting ulMaxBoostBytes MRBTS/LNBTS/LNCEL/tcpServiceDi

bytes ffConfig

Time between TCP packets timeBetweenTcpPackets MRBTS/LNBTS/LNCEL/tcpServiceDi

ffConfig

Minimum TCP packet size minTcpPacketSize MRBTS/LNBTS/LNCEL/tcpServiceDi

ffConfig

Boost guard time boostGuardTime MRBTS/LNBTS/LNCEL/tcpServiceDi

ffConfig

Time until next boosting timeNextBoostingRound MRBTS/LNBTS/LNCEL/tcpServiceDi

round ffConfig

Related descriptions
UL TCP Power Boost

3.8.2 Advanced Step-wise SCell Addition for CA: Initial

SCellAddition in One Step
Functionality that improves network optimization by more efficient use of the secondary
cell (SCell) resources, and minimization of signaling messages. It is achieved by combining
two methods of SCell addition: one-step and step-wise.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 203

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Technical details
When Advanced Step-wise SCell Addition for CA is not activated, there are two independent
ways of SCell addition: one-step and step-wise.

If BTS is configured for one-step SCell addition, then all possible SCells are added when the
UE enters the cell. However, buffer measurement is not started, and if SCells are dropped,
then they cannot be added back.

If BTS is configured for step-wise SCell addition, then SCells are added only after
measurement criteria are fulfilled (for example, buffer based or UE measurements) and only
one SCell can be added at a time. It is performed depending on demand, using separate RRC
Connection Reconfiguration messages (this can lead to signaling message overload).

When the Advanced Step-wise SCell Addition for CA is activated, all SCells are configured in
one-step manner, but the BTS also starts inactivity monitoring to allow SCells to be de-
configured and added back as needed (based on UE throughput demand).

This functionality can be enabled with the LNBTS Activate advanced step-wise
SCell addition (actAdvStepwiseScellAdd) parameter, and requires the
LNBTS_FDD/TDD Number of sampled subframes with High Non-GBR traffic
(numTxWithHighNonGbr) to be configured to value higher than 0. The
actAdvStepwiseScellAdd parameter can be configured to either one-step advanced
or buffer-based.

With the actAdvStepwiseScellAdd parameter set to one-step advanced, upon the

UE entering the cell, the BTS selects all eligible candidate SCells (based on configuration and
UE capabilities), and then adds the SCells in one-step (a single RRC Connection
Reconfiguration message is sent). If the LTE2276: Measurement-based SCell Selection is
activated, SCells are filtered according to LTE2276 rules. After the initial one-step addition,
the BTS follows the step-wise behavior:
Channel quality and SCells activity are monitored (channel quality is monitored if
LTE1541: Advanced SCell Measurement Handling is activated).
Inactive SCells are de-configured if the LTE1541 is activated and the
multScellReleaseTimer parameter is higher than 0.
Non-GBR user data buffer measurements are performed, and released SCells are added
again in a step-wise manner (if the LTE2276 is activated, SCells are filtered according to
LTE2276 rules).
SCells unavailable due to channel quality measurements are de-configured and cannot be
added again unless the LTE2276 is activated.

204 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Figure 12: One-step advanced solution

With the actAdvStepwiseScellAdd parameter set to buffer-based, upon the UE

entering the cell, the BTS starts non-GBR user data buffer measurements. If no SCells are
configured when an SCell addition trigger occurs, the BTS selects all eligible candidate SCells
(based on configuration and UE capabilities), and then adds the SCells in one-step (a single
RRC Connection Reconfiguration message is sent). If the LTE2276: Measurement-based SCell
Selection is activated, SCells are filtered according to LTE2276 rules. After the initial one-
step addition, the BTS follows the step-wise behavior:
Channel quality and SCells activity are monitored (channel quality is monitored if the
LTE1541: Advanced SCell Measurement Handling is activated).
Inactive SCells are de-configured if the LTE1541 is activated and the
multScellReleaseTimer parameter is higher than 0.
Non-GBR user data buffer measurements are performed, and, if the SCell addition trigger
occurs, the SCells are added again:
In step-wise manner if at least one SCell is configured.
In one-step manner if all SCells are released.
If the LTE2276 is activated, SCells are filtered according to LTE2276 rules.
SCells unavailable due to channel quality measurements are de-configured and can't be
added again unless the LTE2276 is activated.

If Carrier Aggregation (CA) Steering intra-cell handover is triggered, and the functionality is
set to buffer-based, then upon the trigger for CA Steering intra-cell handover, the BTS
selects all eligible candidate SCells based on configuration and UE capabilities. If the
LTE2276 is activated, SCells are filtered according to LTE2276 rules.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 205

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Figure 13: Buffer-based solution

Related features
LTE1541: Advanced SCell Measurement Handling
LTE2276: Measurement-based SCell Selection

Management data

Table 50: Parameters introduced by Advanced Step-wise SCell Addition for CA: Initial SCell
Addition in One Step

Full name Abbreviated name Path

Activate advanced actAdvStepwiseScellAdd MRBTS/LNBTS

step-wise SCell
addition

Table 51: Parameters related to Advanced Step-wise SCell Addition for CA: Initial SCell Addition
in One Step

Full name Abbreviated name Path

Number of sampled numTxWithHighNonGbr MRBTS/LNBTS/LNBTS_FDD

subframes with High MRBTS/LNBTS/LNBTS_TDD
Non-GBR traffic

206 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
3.8.3 Fast Scheduling Flexible CA
Functionality which can reduce the amount of time before DL data transmission on a
newly added secondary cell (SCell) begins.

Technical details
The BTS sends DL data on SCell only if it has an indication that the UE is already monitoring
physical downlink control channel (PDCCH) on that SCell. Without activation of the Fast
Scheduling Flexible CA functionality, the BTS gets that indication in one of two ways:
Valid Channel Quality Indicator (CQI) report (different than 0/out of range) was
received for particular SCell.
At least 33 ms passed since particular SCell was activated (BTS waits enough time to
increase the chances that UE is already monitoring PDCCH on newly added SCell).

When the Fast Scheduling Flexible CA is activated (the LNCEL SCcell fast downlink
scheduling selection (scellFastSchedulingSelect) parameter set to true), the
BTS proactively requests aperiodic CQI (A-CQI) for the newly activated SCell, rather than wait
for a periodic CQI. The BTS makes a maximum of four such requests, in order to receive a
valid CQI for the SCell. In the case that no valid CQI is received, then the 33 ms wait criteria
is applied to trigger the start of scheduling on the SCell. Averagely, with this functionality
activated, the delay for the start of DL scheduling on newly activated SCells should be
shorter.

Management data

Table 52: Parameters introduced by Fast Scheduling Flexible CA

Full name Abbreviated name Path

SCcell fast downlink scellFastSchedulingSel MRBTS/LNBTS/LNCEL

scheduling selection ect

3.8.4 UL Dynamic BLER Adaptation

Functionality that improves UL throughput, due to dynamically adapted block error rate
(BLER) value for UL non-GBR traffic.

Issue 01D. © 2022 Nokia. Nokia Confidential Information 207

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Technical details
Without the UL Dynamic BLER Adaptation functionality, the target BLER for UL Adaptive
Modulation and Coding (AMC) is configurable statically by LNCEL UL AMC target BLER
(ulTargetBler) parameter, in range 1% to 50% (default 10%). If the UL Dynamic BLER
Adaptation functionality is enabled (LNCEL Activate uplink dynamic target BLER
(actUlDynamicTargetBler) set to true), the target BLER depends on UE channel
conditions (signal-to-interference-plus-noise-ratio (SINR), Power Headroom Report (PHR)).
The goal of dynamic target BLER change is to use a higher target BLER as SINR degrades (for
example 30% near cell edge). For very good SINR, the target BLER remains at 10%.

When this functionality is activated, the UL throughput for UEs nearing cell edge improves
compared to a fixed target BLER of 10% (the throughput improvements is much more
visible in FDD cells compared to TDD cells). This improvement can be visible at cell level key
performance indicators (KPIs) such as LTE5289d - E-UTRAN average PDCP Layer
Active Cell Throughput UL.

Management data

Table 53: Parameters introduced by UL Dynamic BLER Adaptation

Full name Abbreviated name Path

Activate uplink dynamic actUlDynamicTargetBle MRBTS/LNBTS/LNCEL

target BLER r

Table 54: Parameters related by UL Dynamic BLER Adaptation

Full name Abbreviated name Path

UL AMC target BLER ulTargetBler MRBTS/LNBTS/LNCEL

Table 55: Key performance indicators related to UL Dynamic BLER Adaptation

KPI ID KPI name

LTE5289d E-UTRAN average PDCP Layer Active Cell Throughput UL

208 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
3.8.5 Prolong Timer Override
Functionality that allows you to configure the time before Control Format Indicator (CFI)
is decreased.

Technical details
When the LNCEL Activate load adaptive PDCCH (actLdPdcch) parameter is set to
true, the eNB adapts the number of symbols used for the physical downlink control channel
(PDCCH) on a subframe basis. This number is transmitted using CFI inside the physical
control format indicator channel (PCFICH). CFI indicates how many OFDM symbols are used
for PDCCH transmission in each subframe. CFI can take value 1, 2, or 3. If CFI is set to 1 for a
subframe, it means one symbol at the subframe is used for PDCCH allocation; if it is set to 2,
two symbols are used; and if it is set to 3, three symbols are used. A bigger CFI value means
less space for physical downlink shared channel (PDSCH), which impacts downlink
throughput.
Figure 14: PCFICH location in subframe

Priori to the Prolong Timer Override functionality, the minimum time that had to pass before
the value of CFI was decreased was not configurable, and it was fixed at 100 ms. With this
functionality, this delay is configurable with the LNCEL Adaptive PDCCH symbol
decrease dwell time (adaptPdcchDwellTime) parameter. If it is set to a 100 ms
delay, a downlink throughput degradation can be observed (with the LTE5292:E-UTRAN
average PDCP Layer Active Cell Throughput DL KPI).

Issue 01D. © 2022 Nokia. Nokia Confidential Information 209

Use subject to agreed restrictions on disclosure and use.

SRAN 21A Changes

No further reproduction or networking is permitted. Distributed by Nokia.

Copyrighted material licensed to [email protected] on 29-09-2022.
Management data

Table 56: Parameters introduced by Prolong Timer Override

Full name Abbreviated name Path

Adaptive PDCCH symbol adaptPdcchDwellTime MRBTS/LNBTS/LNCEL

decrease dwell time

Table 57: Parameters related to Prolong Timer Override

Full name Abbreviated name Path

Activate load adaptive actLdPdcch MRBTS/LNBTS/LNCEL

PDCCH

Table 58: Key performance indicators related to Prolong Timer Override

KPI ID KPI name

LTE5289d E-UTRAN average PDCP Layer Active Cell Throughput UL

210 © 2022 Nokia. Nokia Confidential Information Issue 01D

Use subject to agreed restrictions on disclosure and use.