Channel Configuration

NokiaEDU
Channel Configuration
5G RRM and PM Features Delta from 5G21B to 22R1 for NSA

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

Module Objectives
After completing this learning element, the participant should be able to:
• Describe DFT-S-OFDM for FDD cells on ABIL
• Describe 256 QAM for PUSCH for FDD cells on ABIL
• Describe PUSCH DMRS FDM & PUSCH Mapping Type A for FR1 cells on ABIL
• Describe Extended FR2 Cell range
• Describe the new “Aperiodic CSI reporting on PUSCH” features in 22R1
• Configure Management of UE Bandwidth Capabilities
• Analyse UE power saving: Dynamic bandwidth part adaptation for TDD FR1
• Recall Uplink closed loop power control
3 RA50090-V-22R1 © 2022 Nokia

Index
• CB007781 DFT-S-OFDM for FDD cells on ABIL
• CB007797 256 QAM for PUSCH (FDD cells on ABIL)
• CB007782 PUSCH DMRS FDM & PUSCH Mapping Type A
for FR1 cells on ABIL
• CB007462 Extended FR2 Cell Range
• Aperiodic CSI reporting on PUSCH – New 22R1 features
• CB007552: Management of UE Bandwidth Capabilities
• 5GC000937: UE power saving: Dynamic BWP adaptation
for TDD FR1
• 5GC000884 Uplink closed loop power control
4 © Nokia
4 RA50090-V-22R1 © 2022 Nokia
Index
for TDD FR1
5 © Nokia
5 RA50090-V-22R1 © 2022 Nokia
Introduction
Comparison of CP-OFDM and DFT-S-OFDM (1/2)
CP-OFDM
Cyclic Prefix OFDM
• CP-OFDM waveform
• is used in downlink and uplink chains in physical layer of 5G NR system
• is used for high throughput scenario
• is intended for MIMO (Multiple Input Multiple Output)
• offers very high spectral efficiency in RBs (Resource blocks)
• is employed when operators need to maximize network capacity in dense urban environments.
6 RA50090-V-22R1 © 2022 Nokia

• For DFT-S-OFDM waveform Transform Precoding is
Introduction added to the chain of processing blocks
Comparison of CP-OFDM and DFT-S-OFDM (2/2) • Therefore, PUSCH transmission with DFT-S-OFDM is
called also transmission with Transform Precoder
DFT-S-OFDM
Discrete Fourier Transform – Spread - OFDM
• DFT-S-OFDM waveform
• is used in uplink chain only in physical layer of 5G NR system
• is used for power limited scenario
• is only used in single layer transmission
• offers lower spectral efficient, improving at the same time cell coverage
7 RA50090-V-22R1 © 2022 Nokia
Introduction
Recap on 5G21B 5GC000545 DFT-s-OFDM For PUSCH
Before After
• UL PUSCH transmission is supported by • For PUSCH transmission 5GC000545 enables
waveform CP-OFDM (Cyclic Prefix-Orthogonal waveform DFT-S-OFDM (Discrete Fourier
Frequency-Division Multiplexing) only Transform-Spread-Orthogonal Frequency-
Division Multiplexing) as an alternative to CP-
OFDM, providing better link budget
• DFT-S-OFDM for PUSCH is activated at operator
defined UL SINR level measured by gNB
• Feature is supported for ABIO only for 5G NSA
and 5G SA deployment for FR1 TDD and FR1
FDD
8 RA50090-V-22R1 © 2022 Nokia

Introduction
Recap on 5G21B 5GC000545 DFT-s-OFDM For PUSCH
• With 5GC000545 in the Nokia solution:
• RACH Msg3 and DCI 0_0 related PUSCH transmissions are never executed with Transform
Precoding (no DFT-S-OFDM)
• PUSCH transmission requested by DCI 0_1 can be either with Transform Precoding enabled or
disabled (CP OFDM or DFT-S-OFDM)
• gNB decides to use CP-OFDM or DFT-S-OFDM for PUSCH transmission requested by DCI 0_1 based on
UL SINR measurements:
• If the UL SINR level goes below certain threshold, UE is informed to use DFT-S-OFDM waveform
• When the UL SINR level becomes high enough, above another operator defined UL SINR level, UE
is commanded to use CP-OFDM waveform for PUSCH transmission requested by DCI 0_1
• The switch between CP-OFDM and DFT-S-OFDM and vice versa is signaled to the UE terminal by RRC
Reconfiguration procedure
9 RA50090-V-22R1 © 2022 Nokia

Introduction
Switching between CP OFDM and DFT-S-OFDM
UL SINR becomes high enough above certain level;
UL SINR RRC Reconfiguration procedure is started to command the UE to use CP-OFDM;
During transition phase DCI 0_0 is used which always uses CP-OFDM
DCI 0_1 DCI 0_0 DCI 0_1 DCI 0_0 DCI 0_1
High level of UL SINR
Low level of UL SINR

After completion of RRC
PUSCH transmission signaled via DCI Reconfiguration procedure,
0_1 with high UL SINR; After completion of RRC Reconfiguration PUSCH transmission is signaled
Selected waveform is CP-OFDM procedure, PUSCH transmission is signaled again via DCI 0_1; for high UL
again via DCI 0_1; for low UL SINR selected SINR selected waveform is CP-
CP-OFDM waveform is DFT-S-OFDM CP-OFDM OFDM
t
Starting point: UL SINR goes below certain level;
PUSCH transmission is RRC Reconfiguration procedure is started to command the UE to use DFT-S-OFDM;
scheduled via DCI 0_1 During transition phase DCI 0_0 is used which always uses CP-OFDM
10 RA50090-V-22R1 © 2022 Nokia

Technical Details
π/2 BPSK modulation
• 3GPP allows for following PUSCH modulations:

• For CP-OFDM waveform:
• QPSK, 16QAM, 64QAM, 256QAM
• For DFT-S-OFDM waveform:
• π/2 BPSK, QPSK, 16QAM, 64QAM, 256QAM
• current Nokia implementation does not support 256QAM for DFT-S-OFDM
• π/2 BPSK modulation is a new kind of modulation supported by gNB, introduced also by 5GC000545 DFT-S-OFDM for
PUSCH transmission
• *π/2-BPSK is generated from the standard BPSK signal by multiplying the symbol sequence with a rotating phasor
with phase increments per symbol period of π/2.
• π/2-BPSK has the same bit error rate performance as BPSK over a linear channel, however, it exhibits less envelope
variation, and less peak-to-average power ratio (PAPR), making it more suitable for transmission with nonlinear
channels
• This improves the power-amplifier efficiency cost in the mobile terminal at lower data rates.
• BPSK has two modulation states which differ by 180 degrees phase and each state reflects single bit
• π/2 BPSK modulation has four modulation states (the same number as QPSK has); however, for π/2 BPSK each state still
reflects single bit; every state can reflect logical 0 or 1
* Whitepaper: 5G new radio architecture and challenges Link
11 RA50090-V-22R1 © 2022 Nokia

Coverage aspects
• With DFT-S-OFDM it is expected that PUSCH coverage is improved by about 1.5-2dB; as result
retainability of ongoing call can be improved from UE UL coverage POV
• On the other side to fulfill a given UL SINR requirements by UEs located at the cell edge, less
transmitting power is needed what has positive impact on battery life
• At cell edge, UEs transmitting with DFT-S-OFDM are using π/2 BPSK modulation for MCS0 and MCS1,
instead of QPSK modulation; the cost of improved PUSCH coverage can be UL throughput degradation
for UEs at the cell edge due to less efficient modulation used
• 1 symbol of π/2 BPSK modulation reflects 1 bit
• 1 symbol of QPSK modulation reflects 2 bits
12 RA50090-V-22R1 © 2022 Nokia

Introduction
CB007781 DFT-s-OFDM for FDD cells on ABIL
Before After
• Support of DFT-S-OFDM for PUSCH, introduced • The feature CB007781 is porting feature
by 5GC000545 applies for: 5GC000545 to ABIL for FR1 FDD for both 5G
• ABIO NSA and 5G SA
• 5G NSA and 5G SA
• FR1 TDD and FR1 FDD
13 RA50090-V-22R1 © 2022 Nokia

Appendix:
5GC000545: DFT-s-OFDM for PUSCH (5G21B)
14 RA50090-V-22R1 © 2022 Nokia

Technical Details
3GPP requirements for usage of DFT-S-OFDM for PUSCH
• According to 3GPP 38.331 specification, DFT-S-OFDM

waveform (also called transmission with Transform
Precoding) can be configured for PUSCH:
• during UL initial access (Random Access) for Msg3
• during transfer of UL user plane data scheduled by DCI
formats of type DCI 0_0 and DCI 0_1 applicable for
scheduling of PUSCH
NOTE: DCI formats are defined in 3GPP 38.212, 38.213, 38.314
15 RA50090-V-22R1 © 2022 Nokia

Technical Details
RRC Reconfiguration for switching between CP OFDM and DFT-S-OFDM
5G NSA with indirect signaling over MeNB
• For 5G NSA deployment RRC
Reconfiguration procedure
UE gNB-DU
initiated by gNB can be executed RU gNB-CU-UP gNB-CU-CP MeNB
• indirectly over MeNB using

UE in RRC Connected (LTE)
LTE RRC signaling to reach
the UE
• directly via SRB3 to reach
the UE when 5GC000578 gNB-DU detects low OR high UL SINR
feature is activated and the need for RRC Reconfiguration
F1AP: UE CONTEXT MODIFICATION REQUIRED

• For 5G SA deployment RRC X2AP: SGNB MODIFICATION REQUIRED
Reconfiguration procedure (RRC: RRCReconfiguration)
initiated by gNB is executed RRC: RRCConnectionReconfiguration (RRC: RRCReconfiguration)
• directly via SRB2 to reach RRC: RRCConnectionReconfigurationComplete (RRC: RRCReconfigurationComplete)

the UE
X2AP: SGNB MODIFICATION CONFIRM
(RRC: RRCReconfigurationComplete)
F1AP: UE CONTEXT MODIFICATION CONFRIM
16 RA50090-V-22R1 © 2022 Nokia

Technical Details
UE requirements for support of DFT-S-OFDM for PUSCH (1/2)
• There is no dedicated IE in UE-NR-Capability which directly indicates

support of DFT-S-OFDM for PUSCH by a given UE
• Based on recommendations provided by Qualcomm (QC) and

implemented in 5GC000545, Nokia gNB determines whether a UE
terminal supports Transform Precoding or not looking at the following
UE-NR-Capability attributes:
• ss-SINR-Meas
• absoluteTPC-Command
• pucch-F3-4-HalfPi-BPSK
• channelBWs-DL
• twoFL-DMRS-TwoAdditionalDMRS-UL
17 RA50090-V-22R1 © 2022 Nokia

Technical Details
UE requirements for support of DFT-S-OFDM for PUSCH (2/2)
• IF the UE reported capabilities are:
• ss-SINR-Meas = supported
• absoluteTPC-Command = not supported
• pucch-F3-4-HalfPi-BPSK = not supported
• channelBWs-DL include all bitmaps = ( scs-15kHz , scs-30kHz, scs-
60kHz for FR1 and scs-60kHz, scs-120kHz for FR2)
• twoFL-DMRS-TwoAdditionalDMRS-UL = not supported
Then Nokia gNB considers the UE as not eligible for PUSCH Transform
Precoding
In practice UE terminals not supporting DFT-S-OFDM are those with QC software release
SDX50 1.0 or 1.1 and SDX55 1.0 or 1.1
18 RA50090-V-22R1 © 2022 Nokia

Technical Details
gNB-DU decision for changing Transform Precoder from Disabled to Enabled
Transform Precoding is DISABLED
Valid UL SINR measurement +
UE supports DFT-S-OFDM
No RRC Reconfiguration procedure for

Counter=0
Transform Precoder is ongoing
rdTransPrecodeHystCounter
No
Measured SINR < TP On SiNR Thr
The switch to TP enabled state is possible if there is NRBTS.NRCELL.ulTransPrecode

number of consecutive SINR measurements indicating Yes Ctl.ulTransPrecodeOnSinrThres
low level of SINR h
Counter=Counter + 1
Transform
Precoding Yes Counter > 100
ENABLED
(Hardcoded) No
19 RA50090-V-22R1 © 2022 Nokia
Technical Details
gNB-DU decision for changing Transform Precoder from Enabled to Disabled
Transform Precoding is ENABLED
Valid UL SINR measurement +
UE supports DFT-S-OFDM
No RRC Reconfiguration procedure for

Counter=0
Transform Precoder is ongoing
rdTransPrecodeHystCounter NRBTS.NRCELL.ulTransPre
codeCtl.ulTransPrecodeOff
No SinrThresh
Measured SINR >= TP OFF SiNR Thr
The switch to TP disabled state is possible if there is Yes

number of consecutive SINR measurements indicating
high level of SINR Counter=Counter + 1
Transform Yes
Counter > 100
Precoding
(Hardcoded) No
20
DISABLED © 2022 Nokia
RA50090-V-22R1
Configuration Management
Feature activation
• Feature is activated on NRCELL level by parameter NRBTS.NRCELL.actUlDftSOfdm
• For UE in RRC Connected mode, after initial access phase, if DFT-s-OFDM is activated and the UL SINR
of the UE measured by the gNB is below the level defined by parameter value
NRBTS.NRCELL.ulTransPrecodeCtl.ulTransPrecodeOnSinrThresh, then the UE is reconfigured with uplink
transform precoding enabled
• Waveform for UL transfer is reconfigured from CP-OFDM to DFT-S-OFDM
• For UE in RRC Connected mode, if DFT-s-OFDM is activated and the UL SINR of the UE measured by
gNB is greater than or equal to the level defined by parameter value
NRBTS.NRCELL.ulTransPrecodeCtl.ulTransPrecodeOffSinrThresh, then the UE is configured with uplink
transform precoding disabled
• Waveform for UL transfer is reconfigured from DFT-S-OFDM to CP-OFDM
• Reconfiguration between waveform types is executed via RRC Reconfiguration procedure
21 RA50090-V-22R1 © 2022 Nokia

Activation of π/2 BPSK modulation for PUSCH with DFT-S-OFDM
• Parameter NRBTS.NRCELL.ulTransPrecodeCtl.ulTransPrecodePi2Bpsk indicates possible usage of π/2

BPSK modulation by the UE
• If set to true and UE capabilities support π/2 BPSK modulation, then π/2 BPSK modulation is
selected for MCS0 and MCS1 for PUSCH transfer
• If set to true but UE capabilities do not support π/2 BPSK modulation, then QPSK modulation is
selected for MCS0 and MCS1 for PUSCH transfer
• If set to false, any kind of UE uses QPSK modulation for MCS0 and MCS1 for PUSCH transfer
22 RA50090-V-22R1 © 2022 Nokia

Feature configuration
Activation of power boosting for π/2 BPSK modulation for PUSCH with DFT-S-OFDM
• Parameter NRBTS.NRCELL.ulTransPrecodeCtl.ulTransPrePi2BpskPwrBoost indicates if the use of power

boost for π/2 BPSK modulation is enabled for UEs
• If NRBTS.NRCELL.ulTransPrecodeCtl.ulTransPrePi2BpskPwrBoost is set to true and the UE capabilities

indicate:
• Support of π/2 BPSK modulation power boost
• Support of TDD with power boost bands per 3GPP
UE determines the maximum output power for PUCCH/PUSCH transmissions that use π/2 BPSK
modulation according to TS 38.101-1, clause 6.2.4.
• Power Boost on π/2 BPSK only works on selected TDD FR1 bands defined by 3GPP; as result this
function is 5GC000545 specific and not aplicable to CB007781
23 RA50090-V-22R1 © 2022 Nokia

Scenario Activation of DFT-S-OFDM for PUSCH
Parameter name Parameter value Explanation

NRBTS.NRCELL.actUlDftSOfdm activation flag which allows gNB for reconfiguration the UE for usage of
true
DFT-S-OFDM for PUSCH transmission
NRBTS.NRCELL.ulTransPrecodeCtl.ulT Default value; SINR level below which PUSCH is transmitted with DFT-
1.5dB
ransPrecodeOnSinrThresh OFDM
NRBTS.NRCELL.ulTransPrecodeCtl.ulT Default value; SINR level above which PUSCH is transmitted with CP-
3.5dB
ransPrecodeOffSinrThresh OFDM
24 RA50090-V-22R1 © 2022 Nokia

Scenario Usage of π/2 BPSK modulation for DFT-S-OFDM for PUSCH
Scenario provides parameter settings to enhance operation of DFT-S-OFDM waveform for
PUSCH transmission by using π/2 BPSK modulation when MCSO/MCS1 is used
Description
Keep in mind that UE terminal capability need to support π/2 BPSK modulation for DFT-S-
OFDM for PUSCH
NRBTS.NRCELL.ulTransPrecodeCtl.ulTra Recommended value to get most benefits from using DFT-S-OFDM for
true
nsPrecodePi2Bpsk PUSCH coverage improvement
25 RA50090-V-22R1 © 2022 Nokia

Scenario Power boosting for π/2 BPSK modulation for DFT-S-OFDM for PUSCH
Scenario provides parameter settings to enhance operation of DFT-S-OFDM waveform for
PUSCH transmission with π/2 BPSK modulation for MCSO/MCS1 by additional power
boosting
Description
Keep in mind that UE terminal capability need to support power boosting for π/2 BPSK
modulation for DFT-S-OFDM for PUSCH; this option is only possible for selected FR1 TDD
bands
Default value; Recommended value is false because there is a risk to
NRBTS.NRCELL.ulTransPrecodeCtl.ulTra insert increased level of interferences by UEs with power boosting;
false
nsPrePi2BpskPwrBoost value true should be set carefully first on few sites and the impact
should be observed by operator
26 RA50090-V-22R1 © 2022 Nokia

KPIs & Counters
New Counters
5GC000545 introduces counters which control the efficiency of PUSCH
transmission with DFT-S-OFDM
Areas which are populated:
1) Number of PUSCH transmission per waveform, per MCS table, per MCS (112 new counters)
2) Volume of PUSCH transmission per waveform, per MCS table, per MCS (56 new counters)
3) Number of PUSCH transmission in Rank 1 with DFT-S-OFDM using PMI 0…5 (6 new counters)
Total: 174 new counters
27 RA50090-V-22R1 © 2022 Nokia

Performance Management
New counters & KPIs
New counters:
1) M55302C06000…27 PUSCH_DFT_INI_64TBL_MCS_xx
2) M55302C08000…27 PUSCH_DFT_SUCC_INI_64TBL_MCS_xx 4 x 28 =112 new counters per CELL
3) M55302C09000…27 PUSCH_DFT_SUCC_ANY_64TBL_MCS_xx
4) M55302C07000…27 PUSCH_DFT_UNSUCC_64TBL_MCS_xx
5) M55304C07000…27 PUSCH_DFT_INI_VOL_64TBL_MCS_xx
2 x 28=56 new counters per CELL
6) M55304C08000…27 PUSCH_DFT_INRE_VOL_64TBL_MC_xx
7) M55303C21000…05 PUSCH_DFT_RANK1_PMI_xx 6 new counters per CELL
28 RA50090-V-22R1 © 2022 Nokia

Index
for TDD FR1
29 © Nokia
29 RA50090-V-22R1 © 2022 Nokia
Introduction
Recap on 5G21B 5GC001118 256 QAM for PUSCH
• The feature extends the supported modulation schemes
in UL to include support of 256QAM for PUSCH.
• The modulation scheme is supported for UEs with
required capabilities.
SINR
• The functionality is supported NSA and SA, FDD (FR1)
and TDD deployments (FR1) at classic deployment.
• Only ABIO card supports the feature (ABIL support
planned for the future).
256QAM in UL
• Both CPRI (FDD) and eCPRI (TDD) radio units are capable UE
supported
• The feature can be enabled/ disabled per cell by an
operator configurable parameter NRCELL.actUl256Qam.
30 RA50090-V-22R1 © 2022 Nokia

Introduction
Recap on 5G21B 5GC001118 256 QAM for PUSCH
Before After
5GC001118: 5GC001118:
• UE 256QAM capable could transfer data with • UE 256QAM capable can use 256QAM
64QAM max in UL direction modulation in UL direction
• Higher UE peak throughput achieved
31 RA50090-V-22R1 © 2022 Nokia

<feature:CB007797>
CB007797 256 QAM for PUSCH (FDD-ABIL)

Feature in nutshell
• This feature extends the legacy 5GC001118 and introduces the
256 QAM modulation scheme for the UL of FDD deployments
on the ABIL board.
• CB007797 is porting feature 5GC001118 to ABIL for FDD only.
SINR
• CB007797 applies the functionality introduced by 5GC001118
for the ABIL card:
• All requirements and conclusions are the same as in 5GC001118.
• 5GC001118 and CB007797 use the same activation flag

NRCELL.actUl256Qam. 256QAM in UL
capable UE
• Expected gains for CB007797 are the same as for 5GC001118 in
5G21B for FDD.
32 RA50090-V-22R1 © 2022 Nokia

CB007797 256 QAM for PUSCH (FDD-ABIL)
Before & after
Before After
CB007797: CB007797:
• UE 256QAM capable could transfer data with • UE 256QAM capable could transfer data with
256QAM in UL direction on ABIO only 256QAM in UL direction on ABIO and ABIL (FDD
variant only)
33 RA50090-V-22R1 © 2022 Nokia

Appendix:
5GC001118: 256QAM for PUSCH (5G21B)
34 RA50090-V-22R1 © 2022 Nokia

Technical details
5GC001118 256 QAM for PUSCH – UE Capability
Feature can be activated only for 256QAM capable UEs in UL SA Example

direction. UE gNB
UE reports its capability:

• SA: during registration (via RRCSetupComplete (1)) or,
optionally, might be requested by network to provide its RRCSetupComplete
1
capabilities (2)
• NSA: via LTE leg RRC_UECapabilityEnquiry/Information
UECapabilityEnquiry
procedure; information is later pass to gNB during
X2AP_SgNBAddition procedure UECapabilityInformation 2
35 RA50090-V-22R1 © 2022 Nokia

Technical details
5GC001118 256 QAM for PUSCH - UE capabilities
• UE capabilities from several manufacturers UE Capabilites

were checked for UL 256QAM support
(status on 05.2021) 12
• Majority of the UEs support 256QAM in

UL direction
48
256QAM UL supported 256QAM UL not supported
36 RA50090-V-22R1 © 2022 Nokia

Technical details
64QAM 256QAM
MCS tables Modulation Target Modulation Target
Efficiency Efficiency
MCS Index Order code rate MCS Index Order code rate x
• Each 256QAM capable UE is (Q_m) x 1024
[bits/RE]
(Q_m) 1024
[bits/RE]
reconfigured to use 256QAM MCS table

0_QPSK 2 120 0.2344 0_QPSK 2 120 0.2344
1_QPSK 2 157 0.3066 1_QPSK 2 193 0.3770
via RRCConnectionReconfiguration
2_QPSK 2 193 0.3770 2_QPSK 2 308 0.6016
3_QPSK 2 251 0.4902 3_QPSK 2 449 0.8770
message
4_QPSK 2 308 0.6016 4_QPSK 2 602 1.1758
5_QPSK 2 379 0.7402 5_16QAM 4 378 1.4766
6_QPSK 2 449 0.8770 6_16QAM 4 434 1.6953
7_QPSK 2 526 1.0273 7_16QAM 4 490 1.9141
• Dynamic reconfiguration procedure 8_QPSK
9_QPSK
2
2
602
679
1.1758
1.3262
8_16QAM
9_16QAM
4
4
553
616
2.1602
2.4063
(256QAM table <-> 64QAM table) is not 10_16QAM
11_16QAM
4
4
340
378
1.3281
1.4766
10_16QAM
11_64QAM
4
6
658
466
2.5703
2.7305
a scope of this feature. 12_16QAM
13_16QAM
4
4
434
490
1.6953
1.9141
12_64QAM
13_64QAM
6
6
517
567
3.0293
3.3223
14_16QAM 4 553 2.1602 14_64QAM 6 616 3.6094
• 256QAM table is punctured comparing 15_16QAM
16_16QAM
4
4
616
658
2.4063
2.5703
15_64QAM
16_64QAM
6
6
666
719
3.9023
4.2129
to 64QAM to leave a space for a higher 17_64QAM
18_64QAM
6
6
438
466
2.5664
2.7305
17_64QAM
18_64QAM
6
6
772
822
4.5234
4.8164
modulation order. 19_64QAM
20_64QAM
6
6
517
567
3.0293
3.3223
19_64QAM
20_256QAM
6
8
873
683
5.1152
5.3320
21_64QAM 6 616 3.6094 21_256QAM 8 711 5.5547
• 256QAM brings more efficient MCS 22_64QAM
23_64QAM
6
6
666
719
3.9023
4.2129
22_256QAM
23_256QAM
8
8
754
797
5.8906
6.2266
24_64QAM 6 772 4.5234 24_256QAM 8 841 6.5703
25_64QAM 6 822 4.8164 25_256QAM 8 885 6.9141
26_64QAM 6 873 5.1152 26_256QAM 8 917 7.1602
27_64QAM 6 910 5.3320 27_256QAM 8 948 7.4063
28_64QAM 6 948 5.5547 28_QPSK 2 reserved
29_QPSK 2 reserved 29_16QAM 4 reserved
30_16QAM 4 reserved 30_64QAM 6 reserved
31_64QAM 6 reserved 31_256QAM 8 reserved
3GPP 38.214
37 RA50090-V-22R1 © 2022 Nokia

Interdependencies
5GC001118 interaction with 5GC000545 DFT-S-OFDM for PUSCH
• 5GC001118 256 QAM for PUSCH interacts with 5GC000545 DFT-s-OFDM for PUSCH
• Whenever UE is 256 QAM eligible and 5GC001118 is activated, UE will be configured with 256 MCS table
• Since 5GC000545 is mainly coverage enhancement, there is no need to use the 256QAM MCS table for
Transform Precoding
• When both features are activated, and radio conditions get worse, 5GC001118 follows 5GC000545 and
thus continues to use only the Transform Precoding specific 64QAM MCS table
– SINR value is used as a criteria
• When radio condition are better, system switches back to CP OFDM (256 QAM MCS table)
38 RA50090-V-22R1 © 2022 Nokia

5GC001118 - parameters
Default
Abbreviated name Full name Description Range and step
value
NRBTS.NRCELL. Activate 256QAM in

This parameter activates/deactivates the support of 256QAM in UL 0: False, 1 :True 0
actul256qam UL
This parameter indicates the default MCS for UL transmissions

Initial MCS for UL
NRBTS.NRCELL. ullainimcs The default MCS is applied as long as SINR reports are missing or [0…28] 0
Transmission
when the SINR reports are outdated.
REQUIRES BTS RESTART REQUIRES CELL LOCKING ONLINE MODIFIABLE NON-MODIFIABLE
39 RA50090-V-22R1 © 2022 Nokia

New counters & KPIs
New counters:
Measurement name
1) M55302C11000…27 PUSCH_CP_INI_256TBL_MCS_xx
2) M55302C12000…27 PUSCH_CP_UNSUCC_256TBL_MCS_xx NR UL HARQ (4 x 28 new counters per CELL)
3) M55302C13000…27 PUSCH_CP_SUCC_INI_256TBL_MCSxx
4) M55302C14000…27 PUSCH_CP_SUCC_ANY_256TBL_MCSxx
5) M55303C22000…27 PUSCH_CP_RANK1_256TBL_MCS_xx
NR UL Signal Quality (2 x 28 new counters per CELL)
6) M55303C23000…27 PUSCH_CP_Rank2_256TBL_MCS_xx
7) M55304C09000…27 PUSCH_CP_INI_VOL_256TBL_MCSxx
NR MAC PDU Throughput (2 x 28 new counters per CELL)
8) M55304C10000…27 PUSCH_CP_INRE_VOL_256TBL_MCSxx
Currently no new KPIs were defined for 5GC01118
40 RA50090-V-22R1 © 2022 Nokia

Index
• CB007782 PUSCH DMRS FDM & PUSCH Mapping Type
A for FR1 cells on ABIL
for TDD FR1
41 © Nokia
41 RA50090-V-22R1 © 2022 Nokia
Introduction
Refresher: Demodulation Reference Signal DMRS
• DMRS refers to demodulation reference signal and it is

used by a receiver for radio channel estimation for
demodulation of associated physical channel.
• DMRS design and mapping is specific to each
Downlink and Uplink NR channel, e.g., PDCCH, PDSCH,
PUSCH.
• DMRS is unique for specific UE and antenna port. Uplink Control (PUCCH)
Uplink Data (PUSCH)
Sounding Reference Signal
Uplink DMRS
42 RA50090-V-22R1 © 2022 Nokia

Introduction
Refresher: DMRS Frequency Domain Allocations
DMRS Type 1 DMRS Type 2
Mandatory from 3GPP; applied to all common channels Optional; not supported yet
Type 1 is denser in the frequency domain, while type 2 Higher number of orthogonal DMRS ports but lower DMRS density (less
trades the frequency-domain density for a larger sensitivity) and less accurate estimation in case of highly frequency
multiplexing capacity. selective channel
43 *OCC: Orthogonal Covering Code

RA50090-V-22R1 © 2022 Nokia
Introduction
Refresher: Additional DMRS DMRS channel estimate
cross correlation
• 5GC001347 Additional DMRS Configuration (5G19A)

• Additional DMRSs shortens the distance between data and
DMRS and allows for better channel estimation especially for
UEs under varying RF conditions.
• It stabilizes demodulation performance
(and therefore throughput) in mobility scenarios.
• With one additional DMRS symbol, UEs moving up to a speed
of 120km/h can be served.
• If UE is not moving and clock error is not significant, the 0 1 2 3 4 5 6 7 8 9 10 11 12 13
additional DMRS might reduce throughput (for the same

reference MCS) due to higher reference signal overhead.
PUSCH DMRS
PUSCH dat a
44 RA50090-V-22R1 © 2022 Nokia

FL DMRS Additional DMRS
Introduction
Refresher: DMRS Time Domain Allocation 0 1 2 3 4 5 6 7 8 9 10 11 12 13
Mapping type A
• DMRS is mapped relative to the start of the slot boundary
(slot-based allocation), regardless of where in the slot the actual data
transmission starts. Uplink Data (PUSCH)
• Front loaded (FL) DMRS is located in symbol number 2 or 3 SRS/ GP
of the slot. Uplink DMRS
* Note that first symbol refers to symbol number 0

Mapping type B
• The front loaded DMRS is located in the first symbol 0 1 2 3 4 5 6 7 8 9 10 11 12 13
of the data allocation (non-slot based).

• The DMRS location is given relative to where the data is located
Before CB007782: DMRS support for PDSCH Mapping type A and PUSCH
Mapping type B was provided.
45 RA50090-V-22R1 © 2022 Nokia

Introduction
Refresher: Motivation for DMRS multiplexing with data
• DMRS patterns are unique for each antenna

Even 0
port / layer in use. comb
• 2 layers uses the same resources (symbol column of odd
or even subcarriers) which are further orthogonalized in 1
the code domain OCC (CDM multiplexing).

• For 2 layers transmission, either odd or even subcarriers Odd 2
remains unused in the DMRS symbol row. comb
• Please note that currently (22R1) for UL only up to 2x2
MIMO transmission is available (5GC000532), 4x4 is being 3
specified under 5GC000606 framework.
Example:
Uplink DMRS: Even subcarriers, OCC 1
UL slot configuration 69/39
Uplink DMRS: Even subcarriers, OCC 2
Uplink DMRS: Odd subcarriers, OCC 3
Uplink DMRS: Odd subcarriers, OCC 4
Uplink Control (PUCCH)
Uplink Data (PUSCH)
46 RA50090-V-22R1 © 2022 Nokia

Introduction
Motivation for PUSCH mapping type A
PUSCH mapping type B
• For higher speed scenarios, channel estimation performance is 13 symbols
restricted by the data symbol with max. distance to a DMRS symbol. Um Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud
Um Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud
• Higher number of DMRS symbols reduce the max. distance of a data
symbol to the closest DMRS symbol. 5 symbols 4 symbols
Um Ud Ud Ud Ud Ud Ud Ud Ud Ud Um Ud Ud Ud
• For PUSCH Mapping Type B, first DMRS symbol is located at slot

Um Ud Ud Ud Ud Ud Ud Ud Ud Ud Um Ud Ud Ud
start.
PUSCH mapping type A

• For Mapping Type A, first DMRS symbol is located at symbol 2 or 3. 11 symbols
For this reason, max. DMRS symbol distance is typically smaller for Ud Ud Um Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud
Type A compared to Type B. Ud Ud Um Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud
10 symbols
• FL DMRS allocated at pos3 can further reduce the max. distance Ud Ud Ud Um Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud
compared to pos2. Ud Ud Ud Um Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud
47 RA50090-V-22R1 © 2022 Nokia

CB007782: PUSCH DMRS FDM & PUSCH Mapping Type A for FR1 cells on ABIL
Before & after
Before After
• In case of 2 antenna ports in use, half of • 22R1 CB007782 introduces PUSCH DMRS FDM
subcarriers in DMRS symbol row remains unused. functionality for UL TDD and FDD FR1 with ABIL
• It applies to both, single Front Loaded (FL) DMRS HW.
and additional DMRS case (5GC001347). • PUSCH mapping type A is introduced, together
with mixed estimation algorithm.
• Only mapping type B was supported for PUSCH • UL throughput gain due to FDM can be achieved,
• PUSCH DMRS FDM was allowed for ABIO only now also for ABIL
• Mapping type A allows for better performance at
high speeds due to shorter DMRS – data distance
and better channel estimation. Also, SRS handling
with Long PUCCH and aperiodic CSI are also
optimized with mapping type A.
48 RA50090-V-22R1 © 2022 Nokia

List of features
High level feature scope (please note that future releases assignments are subject to change):
5G21B CB006062 PUSCH DMRS FDM for FR1 cells on ABIO-> ABIO only, for TDD FR1 and FDD
22R1 CB007782 PUSCH DMRS FDM & PUSCH mapping Type A for FR1 cells on ABIL -> ABIL only, for TDD FR1 and FDD
22R2 CB008072 PUSCH mapping Type A support on FR1 -> introduced for TDD FR1 and FDD
Later than 22R2: CB007783 PUSCH DMRS FDM & PUSCH mapping Type A for FR2 cells -> ABIO only, for TDD FR2
Note: there’s no feature to support PUSCH & DMRS FDM for TDD FR2 on ABIL.
49 RA50090-V-22R1 © 2022 Nokia

Feature in brief (1/2)
PUSCH data and DMRS FDM for FR1 cells on ABIL PUSCH mapping type A FDM
• The feature extends the PUSCH DMRS FDM for ABIL. Basically, the feature is a
spillover of CB006062 for ABIL card
• Additionally, FDM support for PUSCH mapping type A was introduced.
• PUSCH DMRS FDM allows to improve UL PUSCH throughput, the
functionality is restricted to up to 2 layers transmission per UE (2x2 SU MIMO)
PUSCH mapping type B FDM
Uplink Data (PUSCH)
Uplink DMRS
50 RA50090-V-22R1 © 2022 Nokia

Feature in brief (2/2)
PUSCH mapping type A for FR1 cells on ABIL PUSCH mapping type A FDM
• Mapping type A shortens the distance between the Data and DMRS symbols
what improves SINR and Demodulation capability and in-turn UL throughput,
especially for higher speed scenarios.
• SRS handling with Long PUCCH and aperiodic CSI are also optimized with
mapping Type A.
PUSCH mapping type B FDM
Uplink Data (PUSCH)
Uplink DMRS
51 RA50090-V-22R1 © 2022 Nokia

Supported configurations
CB007782 is supported for TDD and FDD FR1 for ABIL, both SA and NSA, available configurations :
• PUSCH DMRS type 1,
• Single symbol length DMRS,
• Up to 2 consecutive symbols are standardized by 3GPP (> ant ports), 1 symbol supported currently
• PUSCH and DMRS FDM for both PUSCH mapping type A and mapping type B
• 0 or 1 additional DMRS for data PUSCH scheduled by DCI 0_1,
and 2 additional DMRS for PUSCH scheduled by DCI 0_0 (msg3)
• dmrs-TypeA-Position equals 2 or 3 (configuration is common for PUSCH & PDSCH mapping type A )
• Phase Tracking Reference signals PTRS on or off,
• PTRSs are optionally used for phase estimation to compensate clock error.
• Both short PUCCH and long PUCCH configurations,

• Mixed interpolation algorithm for channel estimation with PUSCH mapping type A only,
• CPRI/eCPRI based TDD FR1 and CPRI based FDD.
52 RA50090-V-22R1 © 2022 Nokia

CB007782 Feature activation - DMRS Mapping type A
• DMRS Mapping type A for UL PUSCH transmission can be activated by

NRCELL.puschMappingType=TypeA
• Then Front Loaded DMRS position can be selected by NRCELL.dmrsTypeAPosition, either
pos2 or pos3.
• Please note that mapping type A is available for PDSCH by default.
• Mapping type A brings benefits only for moving mobiles, by reducing of distance of max
distant PUSCH symbol to DMRS.
53 RA50090-V-22R1 © 2022 Nokia

Technical Details
PUSCH DMRS configuration for Mapping type A
Source: 38.211, table 6.4.1.1.3-3
• Front loaded DMRS symbol location for PUSCH mapping type A
is defined by NRCELL: dmrsTypeAPosition (l0). equal to ‘pos3’ or ‘pos2’ DMRS positions
PUSCH mapping type A
(symbol number 3 or 2 of the slot, respectively) ld (in symbols)
• “pos3” would bring much more performance gain than “pos2”. dmrs-AdditionalPosition
pos0 pos1
• Additional DMRS symbol location for PUSCH mapping type A is defined by ld .
4 l0 l0
• Id is the duration between the first OFDM symbol of the slot and last OFDM 5 l0 l0
symbol of the scheduled PUSCH resources in the slot. 6 l0 l0
• E.g. slot type 69/39 -> (S, L) = (0, 11) corresponds to ld =11 7 l0 l0
dmrsAdditionalPosition =(3, 9) 8 l0 l0 , 7
9 l0 l0 , 7
10 l0 l0 , 9
11 symbols
11 l0 l0 , 9
0 1 2 3 4 5 6 7 8 9 10 11 12 13
12 l0 l0 , 9
Ud Ud Ud Um Ud Ud Ud Ud Ud Um Ud Sr Uc Uc Uplink DMRS
13 l0 l0 , 11
14 l0 l0 , 11
Uplink Data (PUSCH)
(S, L) = ( 0 , 11) Sounding Reference Signal
54 RA50090-V-22R1 © 2022 Nokia

NRCELL: dmrsTypeAPosition=‘pos3’
Technical Details
TDD FR1 0 1 2 3 4 5 6 7 8 9 10 11 12 13
69/ 39 -> (S, L) = (0, 11) Ud Ud Ud Um Ud Ud Ud Ud Ud Um Ud Sr Uc Uc
DMRS configuration for PUSCH Mapping type A 55/ 32/ C5 -> (S, L) = (0, 12) Ud Ud Ud Um Ud Ud Ud Ud Ud Um Ud Ud Sr Uc
27 -> (S, L) = (0, 14) Ud Ud Ud Um Ud Ud Ud Ud Ud Ud Ud Um Ud Ud

• Front loaded DMRS symbol location 41 -> (S, L) = (0, 13) Ud Ud Ud Um Ud Ud Ud Ud Ud Ud Ud Um Ud Sr
NRCELL: dmrsTypeAPosition = ‘pos3’ or pos2’
• Additional DMRS according to 3GPP 38.211, FDD FR1 0 1 2 3 4 5 6 7 8 9 10 11 12 13
table 7.4.1.1.3-3: 55/ 32/ C5 -> (S, L) = (0, 12) Ud Ud Ud Um Ud Ud Ud Ud Ud Um Ud Ud Sr Uc
DMRS postitions 27 -> (S, L) = (0, 14) Ud Ud Ud Um Ud Ud Ud Ud Ud Ud Ud Um Ud Ud

PDSCH mapping type A
dmrs-AdditionalPosition 41 -> (S, L) = (0, 13) Ud Ud Ud Um Ud Ud Ud Ud Ud Ud Ud Um Ud Sr
ld (in symbols)
First DMRS Additional DMRS TDD FR1 0 1 2 3 4 5 6 7 8 9 10 11 12 13
dmrsTypeAPosition
69/ 39 -> (S, L) = (0, 11) Ud Ud Ud Um Ud Ud Ud Ud Ud Ud Ud Sr Uc Uc
11 2 or 3 9 55/ 32/ C5 -> (S, L) = (0, 12) Ud Ud Ud Um Ud Ud Ud Ud Ud Ud Ud Ud Sr Uc

12 2 or 3 9
27 -> (S, L) = (0, 14) Ud Ud Ud Um Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud
13 2 or 3 11
14 2 or 3 11 41 -> (S, L) = (0, 13) Ud Ud Ud Um Ud Ud Ud Ud Ud Ud Ud Ud Ud Sr
• Single symbol length DMRS for PUSCH FDD FR1 0 1 2 3 4 5 6 7 8 9 10 11 12 13
Uplink DMRS
55/ 32/ C5 -> (S, L) = (0, 12) Ud Ud Ud Um Ud Ud Ud Ud Ud Ud Ud Ud Sr Uc
Uplink Data (PUSCH) 27 -> (S, L) = (0, 14) Ud Ud Ud Um Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud

41 -> (S, L) = (0, 13) Ud Ud Ud Um Ud Ud Ud Ud Ud Ud Ud Ud Ud Sr

S – PUSCH slot starting position
L – PDSCH duration from the frame start
55 RA50090-V-22R1 © 2022 Nokia

Technical Details
DMRS Additional position
DMRS Additional position for PUSCH Mapping type A is controlled with parameter
NRCELL:ulDMRSAdditionalPosition
Possible values for this parameter:
• No additional DMRS - all UEs would be configured as single DMRS
• One additional DMRS - all UEs would be configured with one additional DMRS, irrespective the
existence of PTRS.
• Automatic - In this case:
• one additional DMRS would be configured for the UEs without PTRS capability.
• PTRS capable UEs would be configured as single DMRS. PTRS Mapping type A would
significantly improve PUSCH performance for such UEs hence reduce the performance gap
with 2 DMRS, making "Automatic" mode a more valuable configuration for customer.
56 RA50090-V-22R1 © 2022 Nokia

Appendix:
CB006062: FDM of DMRS and PUSCH Data in UL
(5G21B)
57 RA50090-V-22R1 © 2022 Nokia

FDM of DMRS and PUSCH
DMRS FDM
• FDM of DMRS and PUSCH means that PUSCH coded symbols
can be allocated in symbol columns used for DMRS OFDM
symbols.
• FDM of DMRS and PUSCH increases available data REs for
transmission, then increases the throughput.
• FDM selection is a dynamic process, decided by gNB,
indicated to UE with appropriate antenna port in DCI.
Counterpart feature for DL: 5GC002015 for TDD FR1 & FR2 and
5GC002535 for FDD FR1 (5G20B)
Uplink Data (PUSCH)
Uplink DMRS
58 RA50090-V-22R1 © 2022 Nokia
CB006062 FDM of DMRS and PUSCH Data in UL
Feature in brief
• The feature introduces the frequency domain multiplexing (FDM)
for DMRS and PUSCH data in one OFDM symbol for all 5G FR1 cells
(FDD & TDD).
• It allows to improve UL PUSCH throughput.
• The functionality is restricted to up to 2 layers transmission
per UE i.e., 2x2 SU MIMO.
• DMRS FDM is dynamically decided by gNB, depending on current rank and
MCS,
• When MCS is below the MCS threshold (bad coverage, cell edge users),
FDM is not activated and since every second OFDM subcarrier in DMRS symbols
column does not carry any data, the DMRS can be power boosted by 3dB (by
default, even before the feature) assuring better demodulation performance,
• Above the MCS threshold, i.e., when UE is closer to the gNB with better SINR, then
the 3dB power boost for the DMRS can be omitted in order to achieve higher
throughput gains with FDM. Uplink Control (PUCCH)
Uplink Data (PUSCH)
Uplink DMRS
59 RA50090-V-22R1 © 2022 Nokia
Power allocation for PUSCH and DMRS
• The drawback of the data and DMRS FDM is the PUSCH DMRS power reduction - all
the resources in the DMRS symbol row are used for PUSCH and DMRS FDM, hence
there is no power left for DMRS power boosting.
• The DMRS power reduction leads to a higher required SINR for same MCS compared
to no-FDM case.
• To avoid the negative impact, FDM of DMRS and PUSCH should be applied only for
higher MCS expected to work in good SINR conditions.
• FDM of DMRS and PUSCH will be decided by gNB based on the MCS thresholds,
defined separately for 64 and 256QAM tables, (providing that feature activation flag is
set).
• This approach assumes that the 3dB power boosting without FDM is more useful for coverage
hence to be limited to low MCS.
• For high MCS, demodulation performance is not any more sensitive to the DMRS power but
more for coding rate and modulation order.
60 RA50090-V-22R1 © 2022 Nokia

Supported configurations
• CB006062 is supported for TDD and FDD FR1 for ABIO
• Supported configurations:
• PUSCH DMRS type 1,
• PUSCH mapping type B,
• Mapping type B assumes that DMRS starts in the first symbol of data allocation, while in mapping type A
this is fixed to 2 or 3rd symbol, relative to the start of the slot boundary. Currently only type B is supported
for PUSCH, while type A is planned for 22R1 with CB007782.
• Single symbol length DMRS,

• Up to 2 consecutive symbols are standardized by 3GPP (> ant ports), 1 symbol supported currently
• 0 or 1 additional DMRS for data PUSCH scheduled by DCI 0_1,

• Up to 2 additional DMRS are standardized by 3GPP, planned for future releases
• Phase Tracking Reference signals PTRS on or off,

• PTRSs are optionally used for phase estimation to compensate clock error.
• Both short PUCCH and long PUCCH configurations,

• CPRI_N and eCPRI are both supported.
61 RA50090-V-22R1 © 2022 Nokia

PUSCH DMRS FDM relations with PUCCH configuration
• According to 3GPP rule (38.214, chapter 6.1.4.2), the maximum number of RE per PRB should
not be higher than 156:
• For single DMRS configuration with 14 PUSCH symbols (including DMRS) and long PUCCH
the 156 RE limit is already reached without FDM (i.e. 13 * 12), hence same TBS with and without
PUSCH DMRS FDM can be allocated. It means that there will be no gain in peak TP with FDM
for such a case. PUSCH allocations with 13, 12 or 11 symbols, e.g., with additional DMRS or SRS would benefit
from DMRS FDM.
(S, L) = (0, 14), 1DMRS (S, L) = (0, 14), 2DMRS (S, L) = (0, 13), 1DMRS, SRS
noFDM:12x12=144 RE noFDM:12x12=144 RE
12x13=156 RE
FDM:(12x12) +12=156 RE FDM:(12x12) +6=150 RE PUSCH DMRS
PUSCH data
SRS
0 1 2 3 4 5 6 7 8 9 10 11 12 13 0 1 2 3 4 5 6 7 8 9 10 11 12 13
0 1 2 3 4 5 6 7 8 9 10 11 12 13
62 RA50090-V-22R1 © 2022 Nokia

• NRCELL:ulDataDmrsFdm structure needs to be defined, gathering parameters for PUSCH
and DMRS FDM
• The feature is activated by NRCELL:ulDataDmrsFdm.actUlDataDmrsFdm activation flag
• UL MCS Index thresholds to apply PUSCH and DMRS FDM for 64QAM and 256QAM MCS tables needs to be
set then:
NRCELL:ulDataDmrsFdm.ulDataDmrsFdmThres64QamMcs
NRCELL:ulDataDmrsFdm.ulDataDmrsFdmThres256QamMcs
• Uplink data and DMRS FDM could be enabled if the MCS used in PUSCH is higher or equal to this parameter.
Please note that the threshold is only a precondition to use data and DMRS FDM since it depends also on the
number of used layers.
• Parameters above activate the feature, however since it depends on the rank and configured number of
layers, the gNB has the flexibility to decide whether data and DMRS FDM need to be used when MCS is
higher or equal to the threshold.
• Data & DMRS FDM automatically disabled when transform precoding DFT-s-OFDM is configured by gNB
(dynamically, based on SINR threshold)
63 RA50090-V-22R1 © 2022 Nokia

Gain and Benefits
• When DMRS FDM is selected, unused symbols in the DMRS symbol column turned into data symbols can
contribute to the UL throughput gain.
• Higher UL throughput when MCS > activation threshold. Note that there will be no gain for 1 DMRS case and
14 symbols PUSCH allocation due to 3GPP restrictions to 156 RE (only in case when Long PUCCH is selected).
• The feature is applicable to up to 2 antenna ports (up to 2x2 MIMO) in use.
• FDM allows for better resources utilization, especially for scenarios suffering from additional DMRS overhead.
Uplink Data (PUSCH)
Uplink DMRS
64 RA50090-V-22R1 © 2022 Nokia

Gain impacting factors
• Achievable feature gains depend on many factors:

• Activation of additional DMRS – with more DMRS signals in baseline, more PUSCH resources can
be used again for data scheduling, also 3GPP TBS size limitation can have impact here.
• Deployment type (FDD/TDD) and frame structure – with different frame structures there is
different number of UL slots in the pattern, therefore different number of PUSCH resources.
• Settings of MCS threshold – setting of MCS threshold will impact the amount of PUSCH resources
from DMRS symbols which can be used for data scheduling as those resources could be only used
when UE has certain radio conditions.
• PUCCH type – long and short PUCCH have different placement and size in UL slots, therefore this
setting can impact final number of PUSCH RE from DMRS symbols which will be used for data
scheduling.
• Activation of beamforming – with enabled beamforming, it is easier for more UEs to get better
channel conditions (due to higher antenna gain), therefore more of them could multiplex PUSCH
with DMRS
65 RA50090-V-22R1 © 2022 Nokia

UL Throughput improvement – frame/cell level
Maximum cell average throughput gain in UL due to PUSCH and DMRS FDM • FDM of PUSCH and DMRS can improve maximum
Additional DMRS UL cell throughput and peak UE throughput for
Frame configuration
up to 2 layers transmission.
PUCCH configuration
no yes
4.1% 11.4%
Effective throughput gain on the cell/UE level
short PUCCH
Source: NRdim tool
TDD 5GC001208
long PUCCH 0.0% 9.5%
•
short PUCCH 4.1% 11.4%
depends on the frame configuration.
TDD 5GC001070
short PUCCH 4.1% 11.5%
TDD 5GC001116
Note: presented gains are given for illustrative purposes
5.2% 11.8%
only, since dynamic effects of the real network are not
short PUCCH
FDD 5GC00836/1095
0.0% 9.8%
considered here, e.g., MCS variation or dynamic selection
long PUCCH
Calculations based on NR Dim tool reference configurations (status of of FDM by gNB. They should be rather treated as an upper
22.06.2021), short PUCCH with 2 symbols, 64QAM, PTRS disabled bound.
66 RA50090-V-22R1 © 2022 Nokia

Index
for TDD FR1
67 © Nokia
67 RA50090-V-22R1 © 2022 Nokia
Introduction
CB007462 Extended FR2 cell range
• Feature CB007462 is extending cell coverage of

PRACH from maximum of 1.16 km up to 2.3 km
• It is designed for Fixed Wireless Access (FWA)
deployments, however mobile devices are not
precluded from accessing the site
• By extending PRACH coverage, overall cell
range might be improved.Overall cell range
depends on the link budget of the other
channels
68 RA50090-V-22R1 © 2022 Nokia

Introduction
• FR2 cell has to use PRACH format C2 and 120kHz SCS. The cell range
extension is achieved by adjusting the RACH receiver window processing
• The zeroCorrelationZoneConfig must be configured to value „0”, when

CB007462 is activated. It means only one preamble can be obtained out of a
root sequence of Zadoff-Chu sequence.
Feature is supported for:

• TDD FR2 deployments
• FR2 radios with eCPRI fronthaul support
• Only NSA architecture is tested, however no implementation changes expected for SA support
• Both ABIO and ABIL based HWs are supported
69 RA50090-V-22R1 © 2022 Nokia

PRACH configuration Index (FR2 unpaired (TDD), format C2)
• Several PRACH configuration Indices are currently supported by Nokia (FR2) with format C2 (TDD)
• These indices differ in terms of frequency of appearance and starting symbol in slot
• Different PRACH capacity can be obtained with each of them or can be suited to different frame formats
Number of PRACH Number of time-domain Max #

PRACH configuration Preamble Slot number (converted to Starting PRACH
Frame (SFN) slots within a PRACH occasions within a occasions
index (FR1 unpaired) format SCS=120kHz) symbol duration
subframe RACH slot within 20ms
175 C2 2nd every 8th (1, 9 …) 9,19,29,39,49,59,69,79 0 2 2 6 32 (every 80ms)
2nd & 3rd every 8th (1,2 19,39,59,79

177 C2 0 2 2 6 32 (every 80ms)
9,10 …)
178 C2 2nd every 4th (1, 5 …) 9,19,29,39,49,59,69,79 0 1 2 6 32 (every 80ms)
182 C2 Odd 9,19,29,39,49,59,69,79 0 1 2 6 16
185 C2 Every 39,79 2 1 2 6 8

187 C2 Every 49,59,69,79 7 1 1 6 8
196 C2 Every 9,19,29,39,49,59,69,79 2 1 2 6 32
38.211 Table 6.3.3.2-4: Random access configurations for FR2 and unpaired spectrum
70 RA50090-V-22R1 © 2022 Nokia

Introduction
Before & after
Before After
• Range of PRACH format C2 with TDD FR2 • After CB007462 feature is activated, range
deployments was limited to ~1.16km of PRACH format C2 with TDD FR2
deployments can be extended up to
~2.3km
71 RA50090-V-22R1 © 2022 Nokia

Technical Details
• FR2 extended cell range beyond 1.16km up to 2.3km with preamble format C2 and 120kHz SCS
• This can be achieved by shifting the PRACH detection window, allow farther UEs to attach to the cell
PRACH Slot with 14 Symbols
SCS 120kHz
14 Symbols 0 1 2 3 4 5 6 7 8 9 10 11 12 13
CP Seq Seq Seq Seq GT CP Seq Seq Seq Seq GT
1 symbol shift CP Seq Seq Seq Seq GT 1st opportunity

(for users from ~1.16 to 2.3km)
1 symbol shift CP Seq Seq Seq Seq GT 2nd opportunity
(for users from ~1.16 to 2.3km) (different SSB)
NOTE: The final range of the cell strongly depends on the deployment area (propagation model) and
UE/FWA user link budget as well as the maximum transmission power of a used carrier. This feature
assumes cell range is not restricted by these items.
72 RA50090-V-22R1 © 2022 Nokia

Technical Details
PRACH detection window shift
• New implementation enhances mechanisms of the RACH handling:

• If extended mode of work is configured in the cell, two sliding windows over each PRACH occasion
within the PRACH slot will be processed:
• In first window PRACH symbols are processed as in the regular (not extended) cell.
• In second window it will process symbols starting from the second symbol occupied by PRACH
in this occasion, but it will include additional symbol (effectively extending the occasion by one
symbol).
PRACH Slot with 14 Symbols

SCS 120kHz
14 Symbols 0 1 2 3 4 5 6 7 8 9 10 11 12 13
CP Seq Seq Seq Seq GT CP Seq Seq Seq Seq GT
1 symbol shift CP Seq Seq Seq Seq GT 1st opportunity

(for users from ~1.16 to 2.3km)
1 symbol shift CP Seq Seq Seq Seq GT 2nd opportunity
(for users from ~1.16 to 2.3km) (different SSB)
73 RA50090-V-22R1 © 2022 Nokia

New and Related Parameters
New Parameters: Related Parameters:
• NRCELL.rangeExtension • NRCELL.zeroCorrelationZoneConfig
• NRBTS.actGeneralConnectivitySilver • NRCELL.tddFrameStructure.guardPeriodLength
• NRCELL.prachConfigurationIndex
This parameter indicates the extension of the cell range. If it is equal to 10

NRCELL: rangeExtension
23 (0-2.3km) (corresponding to 1x_range), then regular range is applied.
Value 23 (corresponding to 0-2.3km) are allowed only to FR2 cells.
NRCELL: tddFrameStructure.guardPeriodLength This parameter defines the length in the OFDM symbols of the guard
2 (2 symbols)
period.
175, 177, 178, 182, 185, One of following values for PRACH Configuration Index should be
NRCELL: prachConfigurationIndex
187, 196 configured.
NRCELL:zeroCorrelationZoneConfig is enforced to be 0, as a result of
NRCELL: zeroCorrelationZoneConfig 0 that root sequence re-use factor is low, what shall be taken into
consideration during network planning.
Activation of this feature is required to change NRCELL.rangeExtension

NRBTS. actGeneralConnectivitySilver True
parameter.
74 RA50090-V-22R1 © 2022 Nokia

KPIs & Counters
Related counters
CB007462 is not introducing new KPIs, but reusing RACH KPIs:
• 5G Contention free RACH setup attempts (NR_5010)
• 5G Contention free RACH setup success ratio (NR_5011)
• 5G Contention based RACH setup attempts (NR_5012)
• 5G Contention based RACH setup success ratio (NR_5013)
Following counters are related to this functionality:

1) RA_ATT_CONT_A_PRMBL_SSB_00 (M55306C00001)
Separate counter for RA setup attempts for contention based group A
each SSB beam. preambles corresponding to SSB beam ID from 0 to 63
RA_ATT_CONT_A_PRMBL_SSB_63 (M55306C00064)
2) RA_ATT_DED_PRMBL_SSB_00 (M55306C02001)
Separate counter for RA setup attempts for dedicated preambles corresponding
each SSB beam. to SSB beam from 0 to 63
RA_ATT_DED_PRMBL_SSB_63 (M55306C02064)
75 RA50090-V-22R1 © 2022 Nokia
CB007462 Performance Executive Summary
Capacity and Performance impact
DL UL
User Peak Rate NO NO
Cell Throughput ▲▼ YES(S) ▲▼ YES(S)
Cell Edge User Throughput NO NO
Maximum Cell Range ▲ YES(I) ▲ YES(I)
Maximum # of RRC Conn
▲▼ YES(S)
users/cell
E2E Delay NO NO
Accessibility ▲▼ YES(S)
Retainability ▲▼ YES(S)
Power Consumption ▼ YES(S)
Others NO
GREEN - positive; RED - negative; ORANGE - depends on scenario; GRAY - no impact

YES (I) (▲) - there is intended positive impact of the feature (by design)
YES (I) (▲▼) - impact of the feature depends on the scenario and is intended (by design)
YES (S) (▲) - there is positive impact of the feature which is a side effect (not intended)
YES (S) (▼) - there is negative impact of the feature which is a side effect (not intended)
YES (S) (▲▼) - impact of the feature depends on the scenario and is a side effect (not intended)
NO - there is no impact
76 RA50090-V-22R1 © 2022 Nokia
Index
• CB007782 PUSCH DMRS FDM & PUSCH Mapping Type A for
FR1 cells on ABIL
• 5GC000937: UE power saving: Dynamic BWP adaptation for
TDD FR1
77 © Nokia
77 RA50090-V-22R1 © 2022 Nokia
Aperiodic CSI reporting on PUSCH evolution
5G21B 22R1-5G
5GC001817 CB008131
Aperiodic CSI reporting on Aperiodic CSI reporting for FR1
PUSCH for non-beamforming CA deployments with FDD as
FDD cells PCell
CB007220 CB007798
Aperiodic CSI reporting on Aperiodic CSI reporting on
PUSCH for beamforming FR1 PUSCH for non-beamforming
TDD cells FDD cells - ABIL
78 RA50090-V-22R1 © 2022 Nokia

Refresher
Periodic CSI Reporting
• Up to 5G21A UEs could only report CSI (Channel Status Information) periodically
– controlled by NRCELLGRP.csiReportPeriodicity parameter
• Each RRC Connected UE requires PUCCH resources assigned for Periodic CSI
– For this reason, to maximize the number of supported RRC Connected UEs it is beneficial to set
the periodicity to high values
– The downside of this is gNB may hold less accurate measurements for UEs in fast changing radio
conditions reducing effectiveness of Link Adaptation algorithms
20 ms CSI-
CSI-
RS RS
Measurement
Periodic CSI
CSI-RS
Report
NRCELLGRP.csiReportPeriodicity = 160 ms
79 RA50090-V-22R1 © 2022 Nokia

Refresher
Aperiodic CSI Reporting
• In 5G21B Aperiodic CSI (A-CSI) reporting functionality on PUSCH channel is

introduced for FDD (5GC001817) and FR1 TDD with beamforming
(5GC007220)
– UE can be aperiodically requested to report CSI multiplexed with PUSCH data
or alone as UCI only
– Higher reporting volume improves CSI measurement accuracy on gNB side
and therefore improves Link Adaptation and MCS selection
– No impact on PUCCH resources, thus no reduction in number of RRC
Connected UEs
• Instead impact of increased reporting on UL resources is shifted to
PUSCH
– gNB will not admit more UEs than it can be handled with PUCCH capacity
– Long PUCCH is required, as it brings functionality to send CSI reports on
PUSCH
– A-CSI reporting functionality is running complementary to the Periodic CSI
(P-CSI) reporting
80 RA50090-V-22R1 © 2022 Nokia

Refresher
Supported deployments
• NSA and SA (or SA+NSA) modes • In 5G21B functionality is available only on ABIO
• FR1 FDD (no beamforming) and FR1 TDD with • From 22R1 functionality is also available for FDD
beamforming (i.e., when 5GC002200 is no beamforming deployments on ABIL
activated) (CB007798)
• Up to 8 SSB beams are supported in FR1 TDD
mode • TDD non-beamforming and beamforming
• Semi-static frame pattern (only applicable to deployments without cell specific CSI-RS are not
TDD): covered with this features
- as given by the 5GC001116 / 5GC1208 / 5GC1070 • FR2 deployments are not in the scope of this
feature bundle feature
• All supported FDD/TDD bandwidths in 5G21A • CB007220 (A-CSI reporting on PUSCH for TDD
can have A-CSI enabled FR1 Beamforming cells) is supported only in
configurations with eCPRI
81 RA50090-V-22R1 © 2022 Nokia

Introduction
CB008131 Aperiodic CSI reporting for FR1 CA deployments with FDD as PCell
• CB008131 is a spillover feature to 5GC001817 and CB007220.

• It is introduced in order to handle the Carrier Aggregation (CA)
content.
P(S)Cell
• Feature provides A-CSI reporting support for configurations with CA SCell
and with FDD as P(S)Cell.
82 RA50090-V-22R1 © 2022 Nokia

Introduction
Before & after
Before After
• Aperiodic CSI supported on ABIO capacity • A-CSI reporting on PUSCH available on

card only ABIL capacity card for FDD cells
(CB007798)
• Aperiodic-CSI can not be enabled together
with CA • A-CSI reporting for FR1 CA deployments
with FDD as Pcell (CB008131)
83 RA50090-V-22R1 © 2022 Nokia

Technical Details
• A-CSI reports are triggered for the PCell only.

• No aperiodic report related to any SCell is provided. SCell’s CQI/RI/PMI report is based on Periodic
report only, for both FDD and TDD SCell.
SCell
P(S)Cell SCell
Periodic CSI
Periodic CSI
Aperiodic CSI
84 RA50090-V-22R1 © 2022 Nokia

Technical Details
• Aperiodic CSI reporting is supported for following CA deployments:

• FDD as P(S)Cell and SCell(s)
• FDD as P(S)Cell and TDD as Scell(s)
• A-CSI support for configurations with CA and FDD SCell(s) is provided in SA mode
• A-CSI support for configurations with CA and TDD as SCell(s) is provided in SA/NSA mode
FDD FDD FDD TDD

P(S)Cell SCells P(S)Cell SCells
SA SA/NSA
85 RA50090-V-22R1 © 2022 Nokia

Technical Details
CB008131 Aperiodic CSI reporting for FR1 CA deployments with FDD as P(S)Cell
• Aperiodic CSI reporting process is attempted on P(S)Cell if:

• the UE is scheduled in UL
• UE has received a new CSI-RS to measure in the P(s)Cell since the last
CSI reporting for the P(s)Cell CSI.
• A-CSI report continues to be received for the P(S)Cell independently from SCell
SCell activation status. P(S)Cell SCell
• Aperiodic CSI reports with UCI information are multiplexed with data in Periodic CSI
PUSCH of the P(s)Cell or are transmitted in UCI-Only mode.
Periodic CSI
• Periodic CSI reports are received for both P(S)Cell and SCells
Aperiodic CSI
86 RA50090-V-22R1 © 2022 Nokia

Technical Details
CB008131 Aperiodic CSI reporting for FR1 CA deployments with FDD as P(S)Cell
• In 5G21B A-CSI cannot be enabled together with Carrier Aggregation

• In 22R1 release feature CB008131 allows to enable A-CSI together with CA, but A-CSI cannot be
requested for SCells
• In future releases A-CSI reporting will be supported for SCells
87 RA50090-V-22R1 © 2022 Nokia

Related Parameters
Range and
Abbreviated name Full name Description Default
step
Activate aperiodic This parameter activates/deactivates Aperiodic CSI 1: true /

NRBTS.NRCELL.actapercsi 0
CSI reporting reporting. 0: false
REQUIRES BTS RESTART REQUIRES CELL LOCKING ONLINE MODIFIABLE
88 RA50090-V-22R1 © 2022 Nokia

Feature Configuration & Performance Evaluation
Feature activation
Scenario Activation of aCSI functionality
Aperiodic CSI functionality is enabled by single activation flag and there is no

Description additional configurable parameters. Long PUCCH is a prerequisite in both FDD and
TDD cells. Additionally, in TDD deployments feature 5GC002200 is a prerequisite.
Parameter name Explanation
NRCELL.actAperCsi 1 (true) Feature activation flag
Long PUCCH is required to enable the

NRCELL.pucchModeSelect 1 (Long PUCCH)
aCSI functionality
NRCELL.dlMimoMode Feature 5GC002200 is required to enable

70
aCSI functionality (FR1 TDD only)
89 RA50090-V-22R1 © 2022 Nokia

The feature provides the same impact like 5GC001817 and CB007220 (utilizes PUSCH for CSI reporting, increasing CSI accuracy,
without impacting PUCCH) in comparison to situation where CA is on without ACSI. That is because ACSI can only be measured on
PCell.
DL UL
User Peak Rate NO ▼ YES(S) (I): Intended
Cell Throughput ▲ YES(I) ▼ YES(S) (S): Side Effect
Cell Edge User
▲ YES(I) NO
Throughput
Maximum Cell Range NO NO
NO
users/cell
E2E Delay NO NO
Accessibility NO
Retainability NO
Power Consumption NO
Others NO
90 RA50090-V-22R1 © 2022 Nokia

Feature utilizes PUSCH for CSI reporting, increasing CSI accuracy, without impacting PUCCH. Feature valid for ABIL (ABIO
support is introduced with 5GC001817 in 5G21B) / with CPRI / SA and NSA

DL UL
User Peak Rate NO ▼ YES(S) (I): Intended
Cell Throughput ▲ YES(I) ▼ YES(S) (S): Side Effect
Cell Edge User
▲ YES(I) NO
Throughput
Maximum Cell Range NO NO
NO
users/cell
E2E Delay NO NO
Accessibility NO
Retainability NO
Power Consumption NO
Others NO
91 RA50090-V-22R1 © 2022 Nokia

Index
for TDD FR1
92 © Nokia
92 RA50090-V-22R1 © 2022 Nokia
SA + NSA
CB007552: Management of UE Bandwidth Capabilities
Before After
• Only one Dedicated BWP for the cell can • Two Dedicated BWPs may be
be configured configured – one Small and one Large
• Accordingly UEs with limited BW size • This solution provides better
capabilities, cannot connect to cell accessibility to cell, for UEs who’s
capability does not allow operation at
full cell BW
93 RA50090-V-22R1 © 2022 Nokia

SA + NSA
BWP overview (before CB007552)
• As per 3GPP, BWP is a contiguous set of PRBs, selected

from a contiguous subset of the common RBs for a given Cell BW
numerology on a given carrier Initial BWP
• Prior to 22R1, it was only possible to configure the Initial Dedicated BWP = NR Cell size
and Dedicated BWP profiles
Full Channel Bandwidth of the cell
– Initial BWP is used as first active BWP until UE
capabilities are known to assure entered UE can be
For SA,
served* (For NSA, the Initial BWP must be
configured, but it is not used) • Initial access is always performed using initial BWP
– UE switches to Dedicated BWP when it is known that • Initial DL BWP, UL BWP is defined in SIB1 (SA only)
it supports full cell BW size. • Random access resources are defined in initial UL BWP (SA only)
• Initial BWP and Dedicated BWP overlap and Dedicated • Dedicated signalling is used to provide the CONNECTED mode BWP
BWP is equal to the cell bandwidth size configuration to UE
• UE can be configured only with a one active BWP at a given • For NR SA, RRCSetup - message is sent to UE with the MCG
configuration
time
• UE switches to using the Dedicated BWP after random access
• BWP is a core functionality of NR and plays a role in several
completion (SA only)
important procedures such as:
For NSA:
– Initial access uses selected part of BW (initial BWP)
• Initial BWP gets configured but never used in the Nokia
to access the cell
implementation
– HO require performing RA in the BWP indicated by
• UE directly uses the dedicated BWP (BWP 1) as this gets activated
network immediately with the configuration of both BWPs. (Signalled via RRC)
94 RA50090-V-22R1 © 2022 Nokia

SA + NSA
Feature CB007552 overview
• Large Dedicated BWP has same bandwidth as spectrum carrier (recommended in Nokia)
• Small Dedicated BWP overlaps the Large Dedicated BWP

• Initial and Dedicated (Small and Large) BWP sizes are configurable by instances of BWP_profile
• UE is configured with the maximum size of dedicated BWP that UE supports (based on UE capabilities), either Small or Large Dedicated
BWP
• Note that this feature supports only FR1 BWs (FR2 is not supported)
NR Cell Previously, in Legacy solution

Initial BWP Dedicated BWP is configured as
full BW of the cell (disabled PRB
Large Dedicated BWP = NR Cell
blanking case), and it is
(legacy Dedicated BWP)
recommended in Nokia product,
Small Dedicated BWP = Size of Initial BWP but please note that using NOT
full BW of the cell for Legacy
Full Bandwidth of the NR Cell Dedicated BWP is also allowed.
95 RA50090-V-22R1 © 2022 Nokia

SA + NSA
All the BWPs have common CRB0 and PRB0. Small
BWP is contained within large BWP. The same SSB
block resources lies in all BWPs including the initial
Max Cell DL
NR-arfcn
• Introduced with CB007552 all BWPs are aligned at bottom of CRBx
cell BW in order to enable reuse of common PRB0 and
CRB0
absoluteFrequencySSB
• For all BWPs, common components are; SSB, CSI-RS,
CORESET0, PRACH, PDCCH to support UE with different
GSCN/
BW capabilities Cell Large dedicated
Chann
NR-arfcn
…
DL = Full
• For UE not supporting Large Dedicated BWP, the small d- el BW
Bandwidth
BWP is configurable same as in legacy solution (large BWP)
CoreSet#0
CoreSet#0
CoreSet#0
SSB/PBCH
• Feature is not compatible with DSS, PRB Blanking and
Short PUCCH (Long PUCCH needs to be enabled) in same
cell offsetTo
PointA
• CB007552 applies to FR1, TDD and FDD* CRB0
Min Cell Small dedicated

NR-arfcn Initial BWP
BWP
Please note that after activation CB007552, if parameter

NRCELL.gscnOrSsPbchArfcn is set with on of the special value
NRBTS:actMultipleDedicatedBWPs (0, 1 or 2) the position of SS Block is rescaled to size of Small
Activate multiple dedicated bandwidth parts Dedicated BWP
False, True
Default: false
96 RA50090-V-22R1 © 2022 Nokia

SA + NSA
DL-BWPs Dedicated BWP
• CoreSet#0 is common for all DL-BWPs
• Dedicated PDCCH are overlapping

• The Dedicated DL BWP should have one
common dedicated PDCCH configuration
• The same SSB (Synchronization Signal
Block) resources lies in all DL-BWPs
including the Initial BWP Dedicated BWP Initial BWP
• CoreSet#0 is in all DL-BWPs

• Dedicated PDCCH are overlapping (in Coreset #0
context of allocation in physical frequency) CSI-RS
• CSI-RS resources transmission are SSB
common for all dedicated BWP TRS
– Different dedicated BWP use a

different share of the CSI-RS
resource
PRB
OFDM-Symbols Figure: example RSs and PDCCH in

20MHz and 30MHz dedicated and initial
DL-BWP
97 RA50090-V-22R1 © 2022 Nokia
SA + NSA
CB007552: Management of UE Bandwidth Capabilities Large
UL-BWPs Dedicated
BWP
Scheduling request
HARQ
• Same PUCCH configuration used by all dedicated
BWP pCSI
– One dedicated long PUCCH configuration PUSCH

Small
for all dedicated UL BWPs Initial Dedicated SRS
• Same PRACH resources are used by all UL BWPs BWP BWP Initial PUCCH (Msg 4 AN)
• The PUCCH areas are aggregated and placed at the PUSCH (Msg3)
bottom edge of the carrier BW and are included in Reserved
the small BWP
- PRACH/PUSCH are in the other PRB, above As the Initial BWP is the same
size as Small d-BWP (same
PUCCH in frequency domain number of PRBs) the PUSCH
in initial BWP for Msg3 needs
- UL scheduler uses PUSCH resources from both cannot be reserved for PUCCH
in d-BWP.
Small and Large BWPs Hence, PRBs that cannot be
used are described in the
- UL scheduler assigns UL resources to UE diagram as Reserved
according to their configured BWP in a manner
maximizing resource utilization and maximizing
peak throughput for both Dedicated BWPs - small PRB
and large
OFDM-Symbols
Figure: simplified example long PUCCH of 20MHz and 30MHz

Dedicated UL-BWP
98 RA50090-V-22R1 © 2022 Nokia

SA + NSA
Handover in context of BWP
• For Handover, the UE performs Random Access directly to d-BWP, (and doesn’t switch BWP from Initial to Dedicated after
Random Access as happens from idle to connected mode)
– During handover when UEs capabilities are known there is no switching from small dedicated BWP to large dedicated
BWP for capable UE – the supported BWP is configured
– It is assumed that the UE does BWP switching at the beginning of the handover (i.e. before performing RA towards the
target cell) and there will be NO data interruption after RA)
– After enabling CB007552, mobility procedures will be possible as in below presented scenarios:
Source cell Target cell
Reconfigure Small BWP during NRcell1 (source cell) NRcell2 (target cell)
BWP 1 BWP 4 Introduced with CB007552
HO to Large BWP
Reconfigure Small BWP during NRcell1 (source cell) NRcell2 (target cell)
BWP 1 BWP 1
Introduced with CB007552
HO to Small BWP
Reconfigure Large BWP during NRcell1 (source cell) NRcell2 (target cell)
BWP 4 BWP 1
Introduced with CB007552
HO to Small BWP
Reconfigure Large BWP during NRcell1 (source cell) NRcell2 (target cell)
BWP 4 BWP 4
Legacy behaviour
HO to Large BWP
NR band
99 RA50090-V-22R1 © 2022 Nokia

SA + NSA
Carrier Aggregation with CB007552
• When Carrier Aggregation is configured on UE and UE doesn’t support the full size BW of the cell Pcell, the Small
BWP may be used in the cell
• When UE is configured with CA, the UE CA bandwidth capabilities are analyzed with consideration of contiguous
carriers in case of smaller BWP usage
NRcell1 (PCell) NRcell2 (SCell)

Large BWP Large BWP
Example with legacy configuration
NRcell1 (PCell) NRcell2 (SCell) NRcell3 (SCell)

Small BWP Large BWP Large BWP
• Please note that, the Small BWP cannot
be used for the SCell
NRcell1 (PCell) NRcell2 (SCell)
Large
Small BWP Large BWP
Examples after enabling CB007552
• Depending on position of small BWP, the contiguous CA may not be possible due to nominal channel spacing
requirements and limitation of CB007552 for intra-band contiguous CA (3GPP 38.104 5.4.1.1)
100 RA50090-V-22R1 © 2022 Nokia

KPI & Counters
New counters - NR Dynamic BWP
Counter ID Network element name NetAct name
M55115C02001 number of admission successes due to BWP1 selected for NSA SGNB_NSA_DU_ADM_SUCC_BWP1
M55115C02002 number of admission successes due to BWP2 selected for NSA SGNB_NSA_DU_ADM_SUCC_BWP2
M55139C02501 number of admission successes due to BWP1 selected for SA GNB_SA_DU_ADM_SUCC_BWP1
M55139C02502 number of admission successes due to BWP2 selected for SA GNB_SA_DU_ADM_SUCC_BWP2
M55166C00001 number of RRC RECONFIGURATION sent with BWP1 in P(S)Cell NRRC_RRC_RECONF_BWP1_SENT
M55166C00002 The number of RRC RECONFIGURATION sent with BWP2 in P(S)Cell NRRC_RRC_RECONF_BWP2_SENT
M55166C00003 number of RRC RECONFIGURATION COMPLETE received due to NRRC_RCFG_CMP_BWP1_RCVD
BWP1 configured in P(S)Cell
M55166C00004 number of RRC RECONFIGURATION COMPLETE received due to NRRC_RCFG_CMP_BWP2_RCVD
BWP2 configured in P(S)Cell
101 RA50090-V-22R1 © 2022 Nokia

KPI & Counters
Counter ID Network element name NetAct name
M55308C28001 Accumulated number of UEs scheduled in DL per slot per BWP1 ACC_UE_DL_SCH_SLOT_BWP1
M55308C28002 Maximum number of UEs scheduled in DL per slot per BWP1 MAX_UE_DL_SCH_SLOT_BWP1
M55308C28003 Accumulated number of UEs scheduled in UL per slot per BWP1 ACC_UE_UL_SCH_SLOT_BWP1
M55308C28004 Maximum number of UEs scheduled in UL per slot per BWP1 MAX_UE_UL_SCH_SLOT_BWP1
M55308C28005 Accumulated number of UEs scheduled in DL per slot per BWP2 ACC_UE_DL_SCH_SLOT_BWP2
M55308C28006 Maximum number of UEs scheduled in DL per slot per BWP2 MAX_UE_DL_SCH_SLOT_BWP2
M55308C28007 Accumulated number of UEs scheduled in UL per slot per BWP2 ACC_UE_UL_SCH_SLOT_BWP2
M55308C28008 Maximum number of UEs scheduled in UL per slot per BWP2 MAX_UE_UL_SCH_SLOT_BWP2
M55308C29001 PRBs used for PDSCH for BWP1 PRB_USED_PDSCH_BWP1
M55308C29002 PRBs used for PUSCH for BWP1 PRB_USED_PUSCH_BWP1
M55308C29003 PRBs used for PDSCH for BWP2 PRB_USED_PDSCH_BWP2
M55308C29004 PRBs used for PUSCH for BWP2 PRB_USED_PUSCH_BWP2
102 RA50090-V-22R1 © 2022 Nokia

Counters, KPIs
KPI ID KPI Name Formula
NR_5086a 5G SA BWP1 Configuration Success Ratio (100 * Sum([NRRC_RCFG_CMP_BWP1_RCVD]) /
Sum([NRRC_RRC_RECONF_BWP1_SENT]))
NR_5087a 5G SA BWP2 Configuration Success Ratio (100 *Sum([NRRC_RCFG_CMP_BWP2_RCVD]) /
Sum([NRRC_RRC_RECONF_BWP2_SENT]))
NR_5303a 5G Average number of scheduled UEs in UL (Sum([ACC_UE_UL_SCH_SLOT_BWP1])/Sum([UL_DATA_
per BWP1 SLOTS] + [PRACH_SLOTS_PUSCH]))
NR_5304a 5G Average number of scheduled UEs in UL (Sum([ACC_UE_UL_SCH_SLOT_BWP2])/Sum([UL_DATA_
per BWP2 SLOTS] +[PRACH_SLOTS_PUSCH]))
NR_5305a 5G Maximum number of scheduled UEs in (max([MAX_UE_DL_SCH_SLOT_BWP1]))
DL per BWP1
NR_5306a 5G Maximum number of scheduled UEs in (Max([MAX_UE_DL_SCH_SLOT_BWP2]))
DL per BWP2
NR_5307a 5G Maximum number of scheduled UEs in (Max([MAX_UE_UL_SCH_SLOT_BWP1]))
UL per BWP1
NR_5308a 5G Maximum number of scheduled UEs in (Max([MAX_UE_UL_SCH_SLOT_BWP2]))
UL per BWP2
103 RA50090-V-22R1 © 2022 Nokia

Index
• 5GC000937: UE power saving: Dynamic BWP
adaptation for TDD FR1
104 © Nokia
104 RA50090-V-22R1 © 2022 Nokia
SA
5GC000937: UE power saving: Dynamic BWP adaptation for TDD FR1
Before After
• UE must always use dedicated • Support for additional dedicated

bandwidth part which spans over bandwidth part
configured frequency resources • UE with low data needs can use
• Higher UE battery consumption due to dedicated bandwidth part which spans
using full bandwidth even in case of low over limited amount of frequency
data demand resources
• Feature allows to save UE Battery
105 RA50090-V-22R1 © 2022 Nokia

SA
Feature in a nutshell (1/2) NRCELL:actPowerSavingBWP
Activate power saving bandwidth part
True, False
• Allow power savings for UE with small throughput Default: False
traffic. Simplified view
Max Cell X e.g.= 272 (FR1)
NR-arfcn
• Limited to FR1 TDD for UEs in SA mode. CRBx
Dedicated
BWP
• The strategy for UE power savings is based on the
possibility of dynamic switch between a BWP with
UE carrier bandwidth
large bandwidth size (often configured with full carrier
bandwidth size) and a “power saving BWP” with a
narrow bandwidth size.
Cell
NR-arfcn
• BWP switching from full Cell BW to Power saving Channel
BW
BWP is entirely based on DCI (not using BWP
inactivityTimer)
Dedicated
• Full BWP and Power saving BWP have the same
FrequencySSB
BWP
SSB/PBCH
Type=
Absolute
values of K0, and PDDCH periodicity
offsetToPointA
GSCN
Power
Saving
Min Cell CRB0

NR-arfcn
Point A or absoluteFrequencypointA:
27 July 2022 subcarrier 0 of Common Resource Block 0 (CRB0)
106 RA50090-V-22R1 © 2022 Nokia
SA
Feature in a nutshell (2/2)
• Switching between full BWP and power saving BWP
happens simultaneously in both DL and UL directions
• Operator can configure UL and DL data thresholds and DL
buffer space to switch between BWPs:
• Data volume below threshold (UL and DL) to switch to
power saving BWP
Data in buffer Data in buffer
• Data volume above threshold (UL and DL) to switch below threshold above threshold
100 100
to wide BWP MHz MHz
• DL/UL Buffer status (emptiness) above threshold to BWP BWP
switch to power saving BWP

• DL/UL Buffer status (emptiness) above threshold to
switch to power saving BWP
• In UL there are seperate throughput thresholds for
VoNR users 20 MHz
BWP
DCI DCI
• If UE is in Carrier Aggregation, SCell(s) are deactivated
switch switch
first and then Power Saving BWP is applied to P(S)Cell
107 RA50090-V-22R1 © 2022 Nokia

SA
Bandwidth part (BWP)
Simplified view
• As per 3GPP, BWP = contiguous set of PRBs, selected from a
contiguous subset of the common RBs for a given numerology on
a given carrier.
• In 22R1- up to 2 (+1 initial) BWPs are supported
Dedicated BWP
• 3GPP allows support of up to 4 BWPs
Carrier PDSCH
BW /
PUSCH
PRB0 of
the BWP
offsetToCarrier
Point A :
110 RA50090-V-22R1 © 2022 Nokia

SA
Power saving BWP Simplified view
Max Cell X e.g.= 272 (FR1)
• 5GC000937 supports new dedicated BWP – called power NR-arfcn
CRBx Dedicated
saving BWP BWP
• Power saving BWP size, < carrier BW

• System then supports 3 BWP profiles (initial and 2
UE carrier bandwidth
dedicated), where 1 dedicated BWP is power saving.
• SSB/PBCH needs to be inside Power Saving BWP
• Manual reconfiguration of NRCELL.gscnOrSsPbchArfcn Cell
NR-arfcn Channel
may be required to fit it into power saving BWP if values BW
other than 0,1 or 2 are used
• Otherwise gNB will automatically adapt GSCN to fit
SSB/PBCH block in power saving BWP Dedicated
PbchArfcn
BWP
gscnOrSs
SSB/PBCH
offsetToPointA
Type=
• It also required that starting CRB of power saving BWP must Power
Saving
be set to CRB0 (cRbStartDl/Ul == crb0) due to change in
PUCCH resource allocation Min Cell CRB0
NR-arfcn
Point A or absoluteFrequencypointA:
subcarrier 0 of Common Resource Block 0 (CRB0)
111 RA50090-V-22R1 © 2022 Nokia

SA
Power saving BWP – impact on UL
• In UL with 5GC000937 enabled, all long PUCCH PRBs are reserved at bottom edge of the spectrum
• Due to such PUCCH allocation - starting CRB must be set to CRB0 (cRbStartDl/Ul == crb0)
• Number of reserved PRBs for PUCCH is not affected by switching between BWPs
SR
HARQ ACK/NACK
pCSI
After enabling 5GC000937 all PUSCH

PUCCH PRBs are allocated at PUCCH PRBs are moved to
the edges of the spectrum, PUSCH the lower edge
when 5GC000937 is disabled
SR
HARQ ACK/NACK
pCSI
pCSI pCSI
HARQ ACK/NACK HARQ ACK/NACK
SR SR
CB006064 5GC000937
112 RA50090-V-22R1 © 2022 Nokia

SA
UE Capability (1/3)
• BWP switch is performed according to the DCI- IE/Group Name Presence Range/Type
Phy-ParametersCommon SEQUENCE
based BWP switch procedure > semiStaticHARQ-ACK-Codebook O supported
• Feature only applies to UEs with sufficient > spatialBundlingHARQ-ACK O supported
…….
capabilities for performing this procedure (whether > dynamicHARQ-ACK-CodeB-CBG- O supported
the UE supports the DCI-based BWP switch) Retx-DL
• Following UE-NR Capability information elements > rateMatchingResrcSetSemi-Static O supported
> rateMatchingResrcSetDynamic O supported
(IE) are used by the 5GC000937 : > bwp-SwitchingDelay O type1, type2
• Phy-ParametersCommon - is used to convey > ... O
> dummy O supported
the physical layer capabilities
> maxNumberSearchSpaces O n10
• bwp-SwitchingDelay - defines whether the > rateMatchingCtrlResrcSetDynamic O supported
UE supports DCI and timer based active > maxLayersMIMO-Indication O Supported
………
BWP switching delay type1 or type2
specified in clause 8.6.2 of TS 38.133. It is
mandatory to report type 1 or type 2.
113 RA50090-V-22R1 © 2022 Nokia

SA
UE Capability (2/3)
IE/Group Name Presence Range/Type
• Another capability within Phy-ParametersCommon SEQUENCE
Phy-ParametersCommon is > semiStaticHARQ-ACK-Codebook O supported
dl-SchedulingOffset-PDSCH-TypeA > spatialBundlingHARQ-ACK O supported
…….
• This field indicates whether the UE supports > dynamicHARQ-ACK-CodeB-CBG- O supported
Retx-DL
DL scheduling slot offset (k0 value) greater > rateMatchingResrcSetSemi-Static O supported
than 0 for PDSCH mapping type > rateMatchingResrcSetDynamic O supported
> bwp-SwitchingDelay O type1, type2
> ... O
> dummy O supported
> maxNumberSearchSpaces O n10
> rateMatchingCtrlResrcSetDynamic O supported
> maxLayersMIMO-Indication O supported
dl-SchedulingOffset-PDSCH-TypeA O supported
114 RA50090-V-22R1 © 2022 Nokia

SA
UE Capability (3/3)
IE/Group Name Presence Range/Type
• Following UE-NR Capability information BandNR SEQUENCE
elements (IE) are used by the 5GC000937: > bandNR M 1..1024 (FreqBandIndicatorNR)
• BandNR - which is part of rf-Parameters > modifiedMPR-Behaviour O BIT STRING (SIZE(8))

group, provides information about UE > bwp-SameNumerology O upto2, upto4
capabilities for NR Band …. …. ….
> crossCarrierScheduling- O supported
• bwp-SameNumerology - indicates whether SameSCS
UE supports BWP adaptation (up to 2/4 > pdsch-256QAM-FR2 O supported
BWPs) with the same numerology, via DCI > pusch-256QAM O supported
and timer. For the UE capable of this feature,

> ue-PowerClass O pc1, pc2, pc3, pc4
the bandwidth of a UE-specific RRC > rateMatchingLTE-CRS O supported
configured DL BWP includes the bandwidth … … …
of the CORESET#0 (if CORESET#0 is
present) and SSB for PCell and PSCell (if
configured). For SCell(s), the bandwidth of
the UE-specific RRC configured DL BWP
includes SSB, if there is SSB on SCell(s)..
115 RA50090-V-22R1 © 2022 Nokia

SA
Thresholds
• UL and DL data / DL buffer emptiness thresholds and measurement period are configured via following
parameters under NRBTS.powerSavingBwpSwitching parameter structure:
Parameters Defaults
dlRateThresholdToPsBwp /dlRateThresholdFromPsBwp - 30kbits/s ,35 kbits/s
DL thresholds for switching into/from power saving BWP
ulRateThresholdVoNRToPsBwp /ulRateThresholdVoNRFromPsBwp – 30kbits/s ,35 kbits/s
UL thresholds for switching into/from power saving BWP for VoNR users
ulRateThresholdNoVoNRToPsBwp /ulRateThresholdNoVoNRFromPsBwp – 5kbits/s, 10kits/s
UL thresholds for switching into/from power saving BWP for non-VoNR users
dlBufferEmptyRatioToPsBwp /dlBufferEmptyRatioFromPsBwp - DL buffer emptiness 90% , 40%
thresholds for switching into/from power saving BWP
ulBufferEmptyRatioToPsBwp /ulBufferEmptyRatioFromPsBwp - UL buffer emptiness 90%, 40%
thresholds for switching into/from power saving BWP
measurementDurationToPsBwp / measurementDurationFromPsBwp – averaging period 160ms, 40ms
for switching into/from power saving BWP
116 RA50090-V-22R1 © 2022 Nokia

SA
Power saving BWP application checks
• Following conditions need to be fulfilled by UE to to switch from large dedicated BWP to power saving BWP:
• UE indicates BWP switching support

• #UEs using power saving BWP is below the threshold maxNumberUesPowerSaving
• For VoNR users (i.e. with at least one VoNR bearer) thresholds is maxNumberVoNRPowerSaving
• Average DL and UL throughput for given UE are below the threshold and buffer emptiness is above threshold
during measurement averaging period
• Measurement averaging period for switching a UE to power saving BWP is controlled

measurementDurationToPsBwp (parameter is common for DL and UL) and measurementDurationFromPsBwp,
when power saving BWP is in use
NRCELL: maxNumberUesPowerSaving NRCELL:maxNumberVoNRPowerSaving

Max # of UEs in power saving BWP Max # of VoNR UEs in power saving BWP
1…1000 0…400
Default:400 Default:250
117 RA50090-V-22R1 © 2022 Nokia

SA
Average throughput and buffer status checks - overview (1/3)
• Average throughput and buffer emptiness are checked every slot during
averaging period
• Average throughput is the one achieved by the UE including slots in

which it was not scheduled but
present in Pre-scheduler Candidate Set
• By buffer emptiness it is meant how much time during averaging

period data buffer was empty
NRBTS: measurementDurationToPsBwp NRBTS: measurementDurationfromPsBwp

Structure: powerSavingBwpSwitching Structure: powerSavingBwpSwitching
averaging period for switching into power saving BWP averaging period for switching from power saving BWP
160…640ms 20…160ms
Default: 160ms Default: 40ms
118 RA50090-V-22R1 © 2022 Nokia

SA
Average throughput and buffer status checks – switching to power saving BWP (2/3)
In this example it is assumed, that similiar conditions
are also applied for UL
1. Average throughput is above the Average
DL throughput Power saving
dlRateThresholdToPsBwp, and DL buffer level is Wide BWP Wide BWP BWP
below dlBufferEmptyRatioToPsBwp, so no BWP dlRateThreshold
FromPsBwp
switch is triggered dlRateThreshold
ToPsBwp
2. Switching to power saving BWP is not triggered, as
buffer emptiness is still below the threshold
Time
3. Both throughput and buffer status conditions are met, DL buffer
emptiness
so from the next measurement period power saving Measurement
Period
BWP is applied
dlBufferEmpty
RatioToPsBwp dlBufferEmpty
RatioTFromPsBwp
Time
1 2 3
NRBTS: measurementDurationToPsBwp
Average DL throughput (after averaging)
Structure: powerSavingBwpSwitching
averaging period for switching into power saving BWP Average DL throughput (current value)
160…640ms Buffer emptiness (after averaging)
Default: 160ms
Threshold values
119 RA50090-V-22R1 © 2022 Nokia

SA
Average throughput and buffer status checks – switching to wide BWP (3/3)
In this example it is assumed, that similiar conditions
are also applied for UL
1. Both averaged throughput and buffer emptiness Average
DL throughput Power saving
conditions are not met, so power saving BWP is still BWP Wide BWP Wide BWP
applied
dlRateThreshold
2. Averaged throughput is still below the wide BWP FromPsBwp dlRateThreshold
ToPsBwp
switching trigger threshold, however
buffer emptiness is low enough to consider UE as
Time
eligible for using wide BWP DL buffer
emptiness
3. As wide BWP is in use, dlRateThresholdFromPsBwp Averaging
Period
and dlBufferEmptyRatioFromPsBwp
parameters are not applicable until power saving BWP dlBufferEmpty
RatioFromPsBwp dlBufferEmpty
will be applied again RatioToPsBwp
Time
1 2 3
Average DL throughput (after averaging)

NRBTS: measurementDurationfromPsBwp
Average DL throughput (current value)
Structure: powerSavingBwpSwitching
averaging period for switching from power saving BWP Buffer emptiness (after averaging)
20…160ms Threshold values

Default: 40ms
120 RA50090-V-22R1 © 2022 Nokia

Parameter Name Structure MO
actPowerSavingBWP Activate power saving bandwidth part NRCELL
cellBwpList Cell bandwidth part list NRCELL
dlRateThresholdToPsBwp Downlink data rate threshold for switching to power powerSavingBwpSwitching NRBTS
saving bandwidth part
dlRateThresholdFromPsBwp Downlink data rate threshold for switching from power powerSavingBwpSwitching NRBTS
saving bandwidth part
maxNumberUesPowerSaving Maximum number of UEs in power saving bandwidth NRCELL
Part
maxNumberVoNRPowerSaving Max number of VoNR UEs in power saving bandwidth NRCELL
Part
ulRateThresholdVoNRFromPsBwp Uplink data rate threshold for switching from power powerSavingBwpSwitching NRBTS
saving bandwidth part for VoNR users
ulRateThresholdNoVoNRToPsBwp Uplink data rate threshold for switching to power saving powerSavingBwpSwitching NRBTS
bandwidth part for VoNR users
ulRateThresholdNoVoNRFromPsBwp Uplink data rate threshold for switching from power powerSavingBwpSwitching NRBTS
saving bandwidth part for Non VoNR users
ulRateThresholdNoVoNRToPsBwp Uplink data rate threshold for switching to power saving powerSavingBwpSwitching NRBTS
bandwidth part for Non VoNR users
121 RA50090-V-22R1 © 2022 Nokia

Parameter Name Structure MO
dlBufferEmptyRatioToPsBwp DL buffer emptiness thresholds for switching into power NRBTS
powerSavingBwpSwitching
saving BWP
dlBufferEmptyRatioFromPsBwp DL buffer emptiness thresholds for switching from power powerSavingBwpSwitching NRBTS
saving BWP
ulBufferEmptyRatioToPsBwp UL buffer emptiness thresholds for switching into/from powerSavingBwpSwitching NRBTS
power saving BWP
ulBufferEmptyRatioFromPsBwp UL buffer emptiness thresholds for switching into/from powerSavingBwpSwitching NRBTS
power saving BWP
measurementDurationToPsBwp averaging period for switching into power saving BWP powerSavingBwpSwitching NRBTS
measurementDurationFromPsBwp averaging period for switching from power saving BWP powerSavingBwpSwitching NRBTS
122 RA50090-V-22R1 © 2022 Nokia

KPI & Counters
New counters - measurement groups with enabling parameters
• New counters found under measurement group:

• NR Dynamic BWP
Counter groups per measurement

Measurement Measurement ID Parameter Default value
NR Dynamic BWP 55351 NRPMRNL. miNrPowerSavingBwp 0 (disabled)
123 RA50090-V-22R1 © 2022 Nokia

KPI & Counters
Counter ID Network element name NetAct name Description

M55351C00001 Maximum number of UEs MAX_UE_ACTIVE_PWR_SAVING_ Maximum number of UEs with Power Saving BWP as
with active Power Saving BWP active BWP. The value is updated when the number of
BWP UEs with active Power Saving BWP over the sampling
period exceeds the previous recorded value.
M55351C00002 Average number of UEs AVG_UE_ACTIVE_PWR_SAVING_ Average number of UEs with Power Saving BWP as
with active Power Saving BWP active BWP. The counter determines the number of UEs
BWP with active Power Saving BWP every sampling period and
averages the values at the end of collection interval.
M55351C01001 Maximum number of UEs MAX_UE_CONFIG_2BWP Maximum number of UEs configured with 2 BWPs (both
configured with 2 BWPs large and Power Saving BWP).The value is updated when
the number of UEs configured with Power Saving over the
sampling period exceeds the previous recorded value.
M55351C01002 Average number of UEs AVG_UE_CONFIG_2BWP Average number of UEs configured with 2 BWPs (both
configured with 2 BWPs large and Power Saving BWP). The counter determines
the number of UEs configured with Power Saving every
sampling period and averages the values at the end of
collection interval.
124 RA50090-V-22R1 © 2022 Nokia

Counters, KPIs
• There are no new KPIs introduced by the feature.
125 RA50090-V-22R1 © 2022 Nokia

Index
for TDD FR1
126 © Nokia
126 RA50090-V-22R1 © 2022 Nokia
5GC000884 Uplink closed loop power control
Introduction - OLPC
• Power Control is a mechanism designed in order Too high Tx power
to adjust UE Tx to the current radio conditions
and network configuration. Optimal Tx power
• Before 22R1 only Open Loop Power Control was
available in 5G. Too low Tx power
• OLPC is a cell-oriented mechanism, which
means that gNB shares the same power control
settings with all UEs and leaves to them their
own power control without focusing on each of
them.
• With OLPC, power level adjustment is calculated
by the UE based on downlink path loss
estimation.
• This type of power control can compensate for
long-term channel variations (such as path
losses) but it typically suffers from errors in UE
specific path loss measurements which may
cause incorrect power adjustment.
• With OLPC, all UEs in the cell try to adjust their transmission power according to
the current radio conditions and OLPC network parameter settings but without
receiving any feedback from gNB.
127 RA50090-V-22R1 © 2022 Nokia

Open Loop Power Control Example
128 RA50090-V-22R1 © 2022 Nokia

Introduction - CLPC
• Feature 5GC000884 introduces a new power Optimal Tx power
control method in 5G which is Closed Loop
power control.
• Closed Loop power control is a UE oriented
mechanism, which means that gNB is trying
to optimize the UE Tx power for each UE
individually.
• With CLPC, power level adjustments are
calculated by the gNB based on
measurements of uplink interference and
pathloss for each UE separately.
• This type of power control is less sensitive to
errors in measurement and transmit power
settings but also allows to reach optimum
reception points under varying propagation
and interference conditions.
• With CLPC, each UE in the cell receives the instructions from the gNB if the
transmission power needs to be increased, decreased or is on optimal level.
• This type of power control, solves the problem of unoptimized (too low or too
high) UL power which may have positive impact for transmission robustness and
reduced interference level and thus increases UL T-put.
129 RA50090-V-22R1 © 2022 Nokia

Overview
• Closed loop power control uses uplink interference and pathloss measurements to select proper SINR (Signal to Interference ratio)
targets for individual UEs.
• The difference between the calculated UL SINR target and current measured UL SINR is compared with configurable TPC
thresholds to check if UL Tx power modification is needed.
• Tx power level adjustments are sent to each UE separately via TPC commands which are simple instructions for UE how much the
power needs to be increased or decreased.
• TPC commands are part of DCI sent via the PDCCH channel. 2
• gNB process the data to compute
the SINR target for UE
1 • gNB compares received SINR to
SINR target and prepares the
gNB receives UE’s transmission and measures UE's UL Rx
power corresponding TPC command
4 UE UL Transmission
UE adjusts the UL transmit power
based on network configuration
and received TPC command 3
TPC command is send to UE via DCI
130 RA50090-V-22R1 © 2022 Nokia

5GC000884 Uplink closed loop power control UL pathloss and
Introduction interference
• Feature 5GC000884 introduces new power control functionality, which is measurements
Closed Loop power control (CLPC).
• With CLPC, UL transmission power is adjusted by the gNB based on UL
Rx power measurements.
INPUT
• UL Tx power modification instructions are sent to individual UE via TPC
commands as part of DCI messages.
• Functionality applies to classical gNB and FR1.
CLPC
• This feature is applicable for:
• Both CPRI and eCPRI
• Both BF and non-BF
• Both SA and NSA mode
• FR1-TDD and FR1-FDD
• ASIL, ABIL, ABIO and small cell.
• No specific (optional) UE capability is required
OUTPUT
• High power UEs are supported.
• 5GC000884 feature activation has the following benefits:
• UL Tx power optimization
• Interference control
• UL throughput improvement Dedicated TPC
commands for
individual UE
131 RA50090-V-22R1 © 2022 Nokia
Introduction
• 5G UL closed loop power control is applied on the following: NRCELL: actUlClosedLoopPwrCtrl
• Physical Uplink Control Channel (PUCCH) Activate UL closed loop power control
• Physical Uplink Shared Channel (PUSCH) 0:disabled;
1:pucch;
• Sounding reference signal (SRS) 23:puschSrs;
123:pucchPuschSrs
Default: 0
• CLPC functionality activation is performed via parameter
NRBTS.NRCELL.actUlClosedLoopPwrCtrl which can
be set to:
• 0 – CLPC disabled
• 1 – CLPC for PUCCH only
• 23 – CLPC for PUSCH and SRS
• 123 – CLPC for PUCCH, PUSCH and SRS
• For SRS CLPC, gNB uses the same TPC command calculated for
PUSCH
• Feature can be activated only if the OLPC is activated in the cell:
NRCELL.ulPowerControlCommon.actUlOpenLoopPwrCtrl
132 RA50090-V-22R1 © 2022 Nokia

New MOC and parameters
CLPC Profile with dedicated
set of CLPC parameters for Measurement
CLPC Profile PUSCH and PUCCH NRBTS activation
ID
Structure with all

NRULCLPC_PROFILE NRPMRNL
parameters related to nrUlClpcProfileId miNrUlSignalQuality2
PUSCH CLPC NRULCLPC_PROFILE: clpcPucch
Closed loop power control for PUCCH
clpcPusch clpcPucch NRCELL

interferAveMeasPeriod sinrAveMeasSamples actUlClosedLoopPwrCtrl
maxTargSinr sinrThresholdIndex nrUlClpcProfileDN
minTargSinr tIntervalSinrUpd
refPathloss tTpcPenalty
sinrAveMeasSamples targetSinr
sinrThresholdIndex 5GC000884 feature
tIntervalSinrUpd activation flag
tTpcPenalty
The ID of the CLPC Profile
targetSinrOffset Structure with all
which will be used in the cell
parameters related to
if CLPC is active
NRULCLPC_PROFILE: clpcPusch PUCCH CLPC
Closed loop power control for PUSCH
133 RA50090-V-22R1 © 2022 Nokia

CLPC Profile Ids and Measurement Settings
NRCELL: nrUlClpcProfileDN NRULCLPC_PROFILE: nrUlClpcProfileId NRPMRNL:

New Radio UpLink Closed Loop Power New Radio UpLink Closed Loop Power Control miNrUlSignalQuality2
Control Profile distinguished name Profile instance identifier Measurement interval for NR
1...400 characters 0...255, step 1 UL Signal Quality Level 2
0:disabled;
5:5min;
15:15min;
30:30min;
60:60min;
360:360min;
720:720min;
1440:1440min
Default: 0
134 RA50090-V-22R1 © 2022 Nokia

PUCCH Parametrization
NRULCLPC_PROFILE: clpcPucch
Closed loop power control for PUCCH
NRULCLPC_PROFILE: NRULCLPC_PROFILE: NRULCLPC_PROFILE: NRULCLPC_PROFILE:

sinrThresholdIndex tIntervalSinrUpd tTpcPenalty sinrAveMeasSamples
SINR threshold index for Timer of SINR update TPC penalty timer for Number of PUCCH data samples when
PUCCH for PUCCH PUCCH averaging S in SINR calculation for
parent: clpcPucch parent: clpcPucch parent: clpcPucch PUCCH
1:triplet 1 (-2, 0, +1); 0:infinity; 30...100, step 1 parent: clpcPucch
2:triplet 2 (-2, 0.5, +1); 10:10ms; Default: 50 3...1000, step 1
3:triplet 3 (-2, 0.5, +2); 20:20ms; Default: 10
4:triplet 4 (-2, 1, +2); 40:40ms;
5:triplet 5 (-1, 0, +2); 60:60ms; NRULCLPC_PROFILE:
6:triplet 6 (-1, 0.5, +2); 80:80ms; targetSinr
7:triplet 7 (-1, 1, +2); 100:100ms; Target SINR for
8:triplet 8 (-1, +2, +2); 200:200ms; PUCCH
9:triplet 9 (-0.5, 0.5, +2); 300:300ms; parent: clpcPucch
10:triplet 10 (-0.5, 1, +2) 500:500ms; -18.5...19, step 0.5
Default: 1 800:800ms; Default: 4
1000:1000ms;
2000:2000ms;
3000:3000ms;
4000:4000ms;
5000:5000ms
Default: 100
PUSCH Parametrization: see below

135 RA50090-V-22R1 © 2022 Nokia
Details
• PUSCH power depends on several static and dynamic factors like OLPC parameters P0 and alpha configuration or pathloss
measurements.
136 RA50090-V-22R1 © 2022 Nokia

Details
• UE determines the Tx power of PUSCH on UL BW part b of carrier f in the primary cell c using PUSCH power control
adjustment state with index l in PUSCH transmission period i as follows:
• PUSCH power equation defined by the 3GPP is divided into two parts – Open Loop and Closed Loop part.
• Before 22R1-5G, Closed loop part was unused. It means that 𝑓𝑓𝑓𝑓,𝑐𝑐 (𝑖𝑖, 𝑙𝑙) was always equal to 0.
• With 5GC000884, 𝑓𝑓𝑓𝑓,𝑐𝑐 (𝑖𝑖, 𝑙𝑙) will be modified according to the received TPC command.
𝑃𝑃𝐶𝐶𝐶𝐶𝐶𝐶𝑋𝑋𝑓𝑓,𝑐𝑐 𝑖𝑖 ,
𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝐻𝐻𝑓𝑓,𝑐𝑐 𝑖𝑖, 𝑗𝑗, 𝑞𝑞𝑑𝑑 , 𝑙𝑙 = 𝑚𝑚𝑚𝑚𝑚𝑚 � 𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃
𝑃𝑃0𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝐻𝐻 𝑗𝑗 + 10 log10 2𝜇𝜇 ∗ 𝑀𝑀𝑅𝑅𝐵𝐵𝑓𝑓,𝑐𝑐
𝑖𝑖 + 𝛼𝛼𝑓𝑓,𝑐𝑐 𝑗𝑗 ∗ 𝑃𝑃𝐿𝐿𝑓𝑓,𝑐𝑐 𝑞𝑞𝑑𝑑 + ∆ 𝑇𝑇𝐹𝐹𝑓𝑓,𝑐𝑐 𝑖𝑖 + 𝑓𝑓𝑓𝑓,𝑐𝑐 (𝑖𝑖, 𝑙𝑙)
𝑓𝑓,𝑐𝑐
Open Loop When UL CLPC is active Closed Loop

part then ΔTF f,c(i) =0 part
137 RA50090-V-22R1 © 2022 Nokia

Workflow
1 Pathloss calculation
When the 5GC000884 feature is activated for PUSCH

(NRBTS.NRCELL.actUlClosedLoopPwrCtrl is set to 23 or 123) , gNB 2 Interference and noise
determination
prepares Closed Loop PUSCH power adjustment for individual UE
based on procedure shown on the scheme.
• Procedure consists of a few steps.
• gNB picks the most appropriate value for TPC command for each
UE based on:
3 SINR target update
• UL pathloss
• Interference and noise level
• Calculated SINR target for the given UE
• Actual measured SINR for the given UE 4 PUSCH SINR
• Selected TPC commands will be sent to the UE via DCI. determination
UL CLPC
5 TPC preparation
138 RA50090-V-22R1 © 2022 Nokia

1 2 3 4 5
5GC000884 Uplink closed loop power control d
UE Pathloss Determination PUSCH CLPC procedure
• First step in the PUSCH CLPC procedure is to calculate the PUSCH pathloss.
• UL pathloss is a difference between the current UE’s PUSCH transmission power and the UL receive power
detected by the gNB.
• With 5GC000884, the UE’s PUSCH transmission is evaluated based on the type 1 PHR received
continuously with the data stream in UL.
• Periodicity of PHR depends on parameter configuration: MRBTS.NRBTS.phrConfig.tPeriodicPhr
• UL pathloss for individual UE is calculated as follows: NRULCLPC_PROFILE: refPathloss
• In the case of no PHR received during the expected period, the UL pathloss is defined by configurable
Reference pathloss
parameter NRBTS.NRULCLPC_PROFILE.clpcPusch.refPathloss. parent: clpcPusch
38...162, step 1
Default: 134
𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃
𝑈𝑈𝑈𝑈 𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 𝑖𝑖 = 𝑃𝑃𝐶𝐶𝐶𝐶𝐶𝐶𝐶𝐶,𝑓𝑓,𝑐𝑐 − max 0, 𝑃𝑃𝑃𝑃𝑡𝑡𝑡𝑡𝑡𝑡𝑡𝑡𝑡,𝑓𝑓,𝑐𝑐 𝑖𝑖, 𝑗𝑗, 𝑞𝑞𝑑𝑑 , 𝑙𝑙 − 10𝑙𝑙𝑙𝑙𝑙𝑙10 𝑀𝑀𝑅𝑅𝑅𝑅,𝑓𝑓,𝑐𝑐 𝑖𝑖 − 𝑟𝑟𝑟𝑟𝑟𝑟𝑟𝑟𝑟𝑟𝑟𝑟𝑟𝑟 𝑖𝑖
Maximum UL Tx power which can Power Headroom calculated on Number of RBs for PUSCH PUSCH received power provided at
be transmitted on carrier f of the carrier f of the serving cell c. In case transmission on carrier f of the each slot where UE has sent data in
serving cell c when received PH is <=0, TPC serving cell c. UL.
command will be forced to 0.
139 RA50090-V-22R1 © 2022 Nokia

PHR Configuraton
• Configuration of PHR. Periodicity parameter: MRBTS.NRBTS.phrConfig.tPeriodicPhr Power Headroom (PH)
value which indicates how
much UE transmission
power left to use in addition
to the power being used in
NRBTS: tPeriodicPhr
current transmission.
Periodic PHR timer
parent: phrConfig
0:10sf; 1:20sf; 2:50sf; 3:100sf; PHR type 1 has been
4:200sf; 5:500sf; 6:1000sf; 7:infinity described in 3GPP 38.213
Default: 20sf chapter 7.7.1
• PHR Config - Signalled to UE:
140 RA50090-V-22R1 © 2022 Nokia

5GC000884 Uplink closed loop power control 1 2 3 4 5
Interference and Noise PUSCH CLPC procedure
• In order to adjust UE PUSCH power correctly, gNB needs to take interference and noise level into consideration.
• Interference and noise (I+N) power is estimated using DMRS associated with each UE.
• I+N power for a certain scheduled UE is reported only for allocated PRBs in each slot.
• For CLPC Interference and noise level is reported for each slot and averaged over a configurable period as follows:
NRULCLPC_PROFILE:
Term “i” is the slot index. interferAveMeasPeriod
Averaging period of interference level
parent: clpcPusch
1:0dot1s;2:0dot2s;4:0dot4s;
𝑥𝑥=𝑖𝑖 5:0dot5s;8:0dot8s;10:1s;20:2s; 50:5s;
1 100:10s; 150:15s; 200:20s; 300:30s;
𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝑒𝑒𝑎𝑎𝑎𝑎𝑒𝑒𝑃𝑃𝑃𝑃𝑃𝑃 𝑖𝑖 = ∗ � 𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝑒𝑒𝑃𝑃𝑃𝑃𝑃𝑃 𝑥𝑥 [𝑑𝑑𝑑𝑑𝑑𝑑] 600:60s; 1200:120s; 1800:180s;
𝑆𝑆 3000:300s; 6000:600s; 12000:1200s;
𝑥𝑥=𝑖𝑖−𝑆𝑆 18000:1800s; 36000:3600s
Default: 1
Operator defines the averaging time (ms) of interference and noise

measurements with a dedicated parameter: Interference plus noise level measured for
NRBTS.NRULCLPC_PROFILE.clpcPusch.interferAveMeasPeriod each UE per slot and normalized per PRB
Value S indicates the number of slots in configured measurement time. but only for allocated PRBs.
Higher parameter values provides less fluctuant measurements.
141 RA50090-V-22R1 © 2022 Nokia

PUSCH SINR Target Computation PUSCH CLPC procedure
• Whenever UE pathloss or interference for PUSCH is updated, gNB calculates corresponding SINR target:
Values introduced with 5GC000510 Uplink open loop power control, defined by configurable UL pathloss value,
Interference, determined
parameters: NRBTS.NRCELL.ulPowerControlCommon.p0NominalPusch determined on the
on the previous step
NRBTS.NRCELL.ulPowerControlCommon.alpha previous step
𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑆𝑆𝑆𝑆𝑆𝑆𝑆𝑆−𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 = 𝑃𝑃0_𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 + 𝑆𝑆𝑆𝑆𝑆𝑆𝐹𝐹𝐹𝐹𝐹𝐹𝐹𝐹𝐹𝐹𝐹𝐹 + 𝐴𝐴𝐴𝐴𝐴𝐴𝐴𝐴𝐴𝐴𝐴𝐴𝑎𝑎𝐹𝐹𝐹𝐹𝐹𝐹𝐹𝐹𝐹𝐹𝐹𝐹 − 1 − 𝛼𝛼 ∗ 𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 − 𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝐼𝑒𝑒𝑎𝑎𝑎𝑎𝑒𝑒𝑃𝑃𝑃𝑃𝑃𝑃 + 𝑂𝑂𝑂𝑂𝑂𝑂𝑂𝑂𝑂𝑂𝑂𝑂𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃
Factor related to SCS and effective Factor related to the number of 𝑂𝑂𝑂𝑂𝑂𝑂𝑂𝑂𝑂𝑂𝑂𝑂𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 can be configured by NIDD parameter
BW of single PRB. antennas in the cell. NRBTS.NRULCLPC_PROFILE.clpcPusch.targetSinrOffset
Value corresponds to Where 𝑂𝑂𝑂𝑂𝑂𝑂𝑂𝑂𝑂𝑂𝑂𝑂𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 can be set to a larger value for better cell throughput in
Value corresponds to 10log10( 15 )
𝑆𝑆𝑆𝑆𝑆𝑆
10log10(# 𝑜𝑜𝑜𝑜 𝑅𝑅𝑅𝑅 𝑎𝑎𝑎𝑎𝑎𝑎𝑎𝑎𝑎𝑎𝑎𝑎𝑎𝑎𝑎𝑎) cell center. But it may introduce a higher interference for neighbor cell.
NRULCLPC_PROFILE: targetSinrOffset
Target SINR offset for PUSCH
parent: clpcPusch
-15...15, step 0.1
Default: 0
142 RA50090-V-22R1 © 2022 Nokia

PUSCH SINR Target Limits PUSCH CLPC procedure
• Maximum and minimum 𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑆𝑆𝑆𝑆𝑆𝑆𝑆𝑆−𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 is limited via a dedicated parameter as below:
𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑆𝑆𝑆𝑆𝑆𝑆𝑆𝑆−𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 = max(min(𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑆𝑆𝑆𝑆𝑆𝑆𝑆𝑆−𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 , 𝑇𝑇𝑆𝑆𝑆𝑆𝑆𝑆𝑆𝑆 𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃_𝑚𝑚𝑚𝑚𝑚𝑚 ), 𝑇𝑇𝑆𝑆𝑆𝑆𝑆𝑆𝑆𝑆 𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃_𝑚𝑚𝑚𝑚𝑚𝑚 )
Maximum SINR value defined with configurable Minimum SINR value defined with configurable
parameter: parameter:
NRBTS.NRULCLPC_PROFILE.clpcPusch.maxTargSinr NRBTS.NRULCLPC_PROFILE.clpcPusch.minTargSinr
This parameter allows to avoid situation where CLPC This parameter allows to avoid situation where CLPC
drives Target SINR−PUSCH above acceptable value. drives Target SINR−PUSCH below acceptable value.
NRULCLPC_PROFILE: maxTargSinr NRULCLPC_PROFILE: minTargSinr

Maximum value of target SINR for Minimum value of target SINR for
PUSCH PUSCH
parent: clpcPusch parent: clpcPusch
-15...30, step 1 -15...30, step 1
Default: 15 Default: -10
143 RA50090-V-22R1 © 2022 Nokia

1 2 3 4 5
Example Received signal
PUSCH CLPC procedure
• Measured and computed rxpower and interference levels are compared
to determine the received SINR level. Higher signal level
Amplitude
comparing to noise
• In CLPC, the calculated SINR level is averaged over a sliding window level means better
with a period defined with the parameter SINR
Noise
NRBTS.NRULCLPC_PROFILE.clpcPusch.sinrAveMeasSamples
• With higher window duration of averaging window, received SINR will
be less fluctuant. NRULCLPC_PROFILE: sinrAveMeasSamples Frequency
Number of PUSCH data samples when averaging S in SINR
calculation for PUSCH
parent: clpcPusch
3...1000, step 1
Default: 10
NRULCLPC_PROFILE: tIntervalSinrUpd
• The 𝑆𝑆𝑆𝑆𝑆𝑆𝑅𝑅𝑈𝑈𝐸𝐸𝐴𝐴𝐴𝐴𝐴𝐴,𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 value, will be passed to the TPC calculation only if Timer of SINR update for PUSCH
parent: clpcPusch
minimum 3 samples are available and the time interval between this 0:infinity; 10:10ms; 20:20ms;40:40ms;
60:60ms; 80:80ms; 100:100ms;
calculation and the second one is smaller than a given time threshold 200:200ms; 300:300ms; 500:500ms;
NRBTS.NRULCLPC_PROFILE.clpcPusch.tIntervalSinrUpd. 800:800ms; 1000:1000ms;
2000:2000ms; 3000:3000ms;
• Otherwise, TPC command is forced to 0dB. 4000:4000ms; 5000:5000ms
Default: 100
144 RA50090-V-22R1 © 2022 Nokia

PUSCH TPC Determination (1) PUSCH CLPC procedure
• When a PUSCH channel is already scheduled for UE, gNB determines the difference between an expected SINR
(𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑡𝑡𝑆𝑆𝑆𝑆𝑆𝑆𝑆𝑆−𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 ) and a reached SINR in UL Tx (𝑆𝑆𝑆𝑆𝑆𝑆𝑅𝑅𝑈𝑈𝐸𝐸𝐴𝐴𝐴𝐴𝐴𝐴 ) as follows:
𝑆𝑆𝑆𝑆𝑆𝑆𝑅𝑅𝑈𝑈𝐸𝐸𝐴𝐴𝐴𝐴𝐴𝐴
SINR target value, determined in the previous step
𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑡𝑡𝑆𝑆𝑆𝑆𝑆𝑆𝑆𝑆 ∆𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 = 𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑇𝑡𝑡𝑆𝑆𝑆𝑆𝑆𝑆𝑆𝑆−𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 − 𝑆𝑆𝑆𝑆𝑆𝑆𝑅𝑅𝑈𝑈𝐸𝐸𝐴𝐴𝐴𝐴𝐴𝐴
UE reached SINR value, determined in the previous step
• Depending on the calculated ∆𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 value, gNB determines the PUSCH TPC command by comparing ∆𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 with 𝐷𝐷𝐷𝐷𝐷𝐷𝐷𝐷𝑎𝑎𝑆𝑆𝑆𝑆𝑆𝑆𝑆𝑆𝑆𝑆
thresholds.
145 RA50090-V-22R1 © 2022 Nokia

PUSCH TPC Determination (2)
NRULCLPC_PROFILE: sinrThresholdIndex
SINR threshold index for PUSCH
parent: clpcPusch
1:triplet 1 (-2, 0, +1);
2:triplet 2 (-2, 0.5, +1);
• 𝑫𝑫𝑫𝑫𝑫𝑫𝑫𝑫𝒂𝒂𝑺𝑺𝑺𝑺𝑺𝑺𝑺𝑺𝑺𝑺 set of thresholds is defined by configurable parameter 3:triplet 3 (-2, 0.5, +2);
NRBTS.NRULCLPC_PROFILE.clpcPusch.sinrThresholdIndex 4:triplet 4 (-2, 1, +2);
• gNB locates the calculated ∆𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 value with respect to predefined thresholds 5:triplet 5 (-1, 0, +2);
6:triplet 6 (-1, 0.5, +2);
as it is shown on the example below. 7:triplet 7 (-1, 1, +2);
8:triplet 8 (-1, +2, +2);
9:triplet 9 (-0.5, 0.5, +2);
10:triplet 10 (-0.5, 1, +2)
Default: 1
𝑫𝑫𝑫𝑫𝑫𝑫𝑫𝑫𝒂𝒂𝑺𝑺𝑺𝑺𝑺𝑺𝑺𝑺𝑺𝑺 𝑫𝑫𝑫𝑫𝑫𝑫𝑫𝑫𝒂𝒂𝑺𝑺𝑺𝑺𝑺𝑺𝑺𝑺𝑺𝑺 𝑫𝑫𝑫𝑫𝑫𝑫𝑫𝑫𝒂𝒂𝑺𝑺𝑺𝑺𝑺𝑺𝑺𝑺𝑺𝑺

∆𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 ≥ 𝐷𝐷𝐷𝐷𝐷𝐷𝐷𝐷𝑎𝑎𝑆𝑆𝑆𝑆𝑆𝑆𝑆𝑆1
and
∆𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 < 𝐷𝐷𝐷𝐷𝐷𝐷𝐷𝐷𝑎𝑎𝑆𝑆𝑆𝑆𝑆𝑆𝑆𝑆𝑆 TPC=-1dB TPC=0dB TPC=1dB TPC=3dB
Then
TPC=0dB Calculated value ∆𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃
∆𝑷𝑷𝑷𝑷𝑷𝑷𝑷𝑷𝑷𝑷
146 RA50090-V-22R1 © 2022 Nokia

TPC Signalling
DCI format 0_1 - content
• TPC commands are transferred to the UEs via DCI in PDCCH.
• For PUSCH power adjustments, gNB uses DCI format 0_1 Identifier for DCI formats
which is used for PUSCH scheduling. Carrier indication
• TPC field can be set to: DFI Flag
• value 0 corresponds to -1dB used in CLPC
●●●
• value 1 corresponds to 0dB, which means no power
control 1st downlink assignment index
• value 2 corresponds to +1dB used in CLPC 2nd downlink assignment index
• value 3 corresponds to +3dB used in CLPC TPC command
• In order to avoid the situation that the TPC reacts too quickly
SRS resource indicator
for each received SINR change, two consecutive TPC
commands are separated by a dedicated, configurable Precoding information and number of layers
penalty timer: ●●●
NRBTS.NRULCLPC_PROFILE.clpcPusch.tTpcPenalty
• TPC commands different than 0 will be sent only if the
penalty timer is expired. NRULCLPC_PROFILE: DCI content
tTpcPenalty compliant with
TPC penalty timer for PUSCH
parent: clpcPusch 38.212
7.3.1.1
30...100, step 1
Default: 50
147 RA50090-V-22R1 © 2022 Nokia

Abbrev Description MO Structure
actUlClosedLoopPwrCtrl Activate UL closed loop power control NRCELL
nrUlClpcProfileDN New Radio UpLink Closed Loop Power Control Profile distinguished name NRCELL
miNrUlSignalQuality2 Measurement interval for NR UL Signal Quality Level 2 NRPMRNL
clpcPucch Closed loop power control for PUCCH NRULCLPC_PROFILE
Number of PUCCH data samples when averaging S in SINR calculation for
sinrAveMeasSamples PUCCH NRULCLPC_PROFILE clpcPucch
sinrThresholdIndex SINR threshold index for PUCCH NRULCLPC_PROFILE clpcPucch
tIntervalSinrUpd Timer of SINR update for PUCCH NRULCLPC_PROFILE clpcPucch
tTpcPenalty TPC penalty timer for PUCCH NRULCLPC_PROFILE clpcPucch
targetSinr Target SINR for PUCCH NRULCLPC_PROFILE clpcPucch
clpcPusch Closed loop power control for PUSCH NRULCLPC_PROFILE
interferAveMeasPeriod Averaging period of interference level NRULCLPC_PROFILE clpcPusch
maxTargSinr Maximum value of target SINR for PUSCH NRULCLPC_PROFILE clpcPusch
minTargSinr Minimum value of target SINR for PUSCH NRULCLPC_PROFILE clpcPusch
refPathloss Reference pathloss NRULCLPC_PROFILE clpcPusch
Number of PUSCH data samples when averaging S in SINR calculation for
sinrAveMeasSamples PUSCH NRULCLPC_PROFILE clpcPusch
sinrThresholdIndex SINR threshold index for PUSCH NRULCLPC_PROFILE clpcPusch
148 RA50090-V-22R1 © 2022 Nokia

Abbrev Description MO Structure
tIntervalSinrUpd Timer of SINR update for PUSCH NRULCLPC_PROFILE clpcPusch
tTpcPenalty TPC penalty timer for PUSCH NRULCLPC_PROFILE clpcPusch
targetSinrOffset Target SINR offset for PUSCH NRULCLPC_PROFILE clpcPusch
nrUlClpcProfileId New Radio UpLink Closed Loop Power Control Profile instance identifier NRULCLPC_PROFILE
149 RA50090-V-22R1 © 2022 Nokia

Performance Management - related Counters
Counter ID NetAct Name Network Element Name
M55340C00001..25 UE_PATHLOSS_PUSCH_SSB0_LEV_1..25 UE pathloss for PUSCH for SSB0 level 1..25
M55340C08001..37 UE_PWR_HEADROOM_PUSCH_LEV_1..37 UE power headroom for PUSCH for level 1..37
150 RA50090-V-22R1 © 2022 Nokia

Channel Configuration

Uploaded by

Copyright:

Available Formats

You might also like

Channel Configuration

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Channel Configuration

Uploaded by

Copyright:

Available Formats

NokiaEDU

5G RRM and PM Features Delta from 5G21B to 22R1 for NSA

2 RA50090-V-22R1 © 2022 Nokia

3 RA50090-V-22R1 © 2022 Nokia

6 RA50090-V-22R1 © 2022 Nokia

8 RA50090-V-22R1 © 2022 Nokia

9 RA50090-V-22R1 © 2022 Nokia

High level of UL SINR

Low level of UL SINR

10 RA50090-V-22R1 © 2022 Nokia

• 3GPP allows for following PUSCH modulations:

* Whitepaper: 5G new radio architecture and challenges Link

11 RA50090-V-22R1 © 2022 Nokia

12 RA50090-V-22R1 © 2022 Nokia

13 RA50090-V-22R1 © 2022 Nokia

14 RA50090-V-22R1 © 2022 Nokia

• According to 3GPP 38.331 specification, DFT-S-OFDM

NOTE: DCI formats are defined in 3GPP 38.212, 38.213, 38.314

15 RA50090-V-22R1 © 2022 Nokia

• indirectly over MeNB using

F1AP: UE CONTEXT MODIFICATION REQUIRED

• directly via SRB2 to reach RRC: RRCConnectionReconfigurationComplete (RRC: RRCReconfigurationComplete)

16 RA50090-V-22R1 © 2022 Nokia

• There is no dedicated IE in UE-NR-Capability which directly indicates

• Based on recommendations provided by Qualcomm (QC) and

17 RA50090-V-22R1 © 2022 Nokia

18 RA50090-V-22R1 © 2022 Nokia

No RRC Reconfiguration procedure for

The switch to TP enabled state is possible if there is NRBTS.NRCELL.ulTransPrecode

No RRC Reconfiguration procedure for

Measured SINR >= TP OFF SiNR Thr

The switch to TP disabled state is possible if there is Yes

• Feature is activated on NRCELL level by parameter NRBTS.NRCELL.actUlDftSOfdm

• Reconfiguration between waveform types is executed via RRC Reconfiguration procedure

21 RA50090-V-22R1 © 2022 Nokia

• Parameter NRBTS.NRCELL.ulTransPrecodeCtl.ulTransPrecodePi2Bpsk indicates possible usage of π/2

22 RA50090-V-22R1 © 2022 Nokia

• Parameter NRBTS.NRCELL.ulTransPrecodeCtl.ulTransPrePi2BpskPwrBoost indicates if the use of power

• If NRBTS.NRCELL.ulTransPrecodeCtl.ulTransPrePi2BpskPwrBoost is set to true and the UE capabilities

23 RA50090-V-22R1 © 2022 Nokia

Scenario Activation of DFT-S-OFDM for PUSCH

Parameter name Parameter value Explanation

24 RA50090-V-22R1 © 2022 Nokia

25 RA50090-V-22R1 © 2022 Nokia

26 RA50090-V-22R1 © 2022 Nokia

Areas which are populated:

Total: 174 new counters

27 RA50090-V-22R1 © 2022 Nokia

2) M55302C08000…27 PUSCH_DFT_SUCC_INI_64TBL_MCS_xx 4 x 28 =112 new counters per CELL

7) M55303C21000…05 PUSCH_DFT_RANK1_PMI_xx 6 new counters per CELL

Total: 174 new counters

28 RA50090-V-22R1 © 2022 Nokia

30 RA50090-V-22R1 © 2022 Nokia

31 RA50090-V-22R1 © 2022 Nokia

CB007797 256 QAM for PUSCH (FDD-ABIL)

• 5GC001118 and CB007797 use the same activation flag

32 RA50090-V-22R1 © 2022 Nokia

33 RA50090-V-22R1 © 2022 Nokia

34 RA50090-V-22R1 © 2022 Nokia