3GPP TS 38.214

3GPP TS 38.214 V16.1.
0 (2020-03)
Technical Specification
3rd Generation Partnership Project;

Technical Specification Group Radio Access Network;
NR;
Physical layer procedures for data
(Release 16)
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP..
The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
Specifications and Reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.
Release 16 2 3GPP TS 38.214 V16.1.0 (2020-03)
Keywords
3GPP, New Radio, Layer 1
3GPP
Postal address
3GPP support office address

650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://www.3gpp.org
Copyright Notification
No part may be reproduced except as authorized by written permission.

The copyright and the foregoing restriction extend to reproduction in all media.
© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
All rights reserved.
UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
GSM® and the GSM logo are registered and owned by the GSM Association
3GPP
Release 16 3 3GPP TS 38.214 V16.1.0 (2020-03)
Contents
Foreword............................................................................................................................................................. 6
1 Scope ........................................................................................................................................................ 7
2 References ................................................................................................................................................ 7
3 Definitions, symbols and abbreviations ................................................................................................... 8
3.1 Definitions ......................................................................................................................................................... 8
3.2 Symbols ............................................................................................................................................................. 8
3.3 Abbreviations..................................................................................................................................................... 8
4 Power control ........................................................................................................................................... 9
4.1 Power allocation for downlink ........................................................................................................................... 9
5 Physical downlink shared channel related procedures ........................................................................... 10
5.1 UE procedure for receiving the physical downlink shared channel ................................................................. 10
5.1.1 Transmission schemes ................................................................................................................................ 12
5.1.1.1 Transmission scheme 1 ......................................................................................................................... 12
5.1.2 Resource allocation .................................................................................................................................... 13
5.1.2.1 Resource allocation in time domain ..................................................................................................... 13
5.1.2.1.1 Determination of the resource allocation table to be used for PDSCH ........................................... 16
5.1.2.2 Resource allocation in frequency domain ............................................................................................. 20
5.1.2.2.1 Downlink resource allocation type 0............................................................................................... 20
5.1.2.2.2 Downlink resource allocation type 1............................................................................................... 21
5.1.2.3 Physical resource block (PRB) bundling .............................................................................................. 22
5.1.3 Modulation order, target code rate, redundancy version and transport block size determination .............. 23
5.1.3.1 Modulation order and target code rate determination ........................................................................... 25
5.1.3.2 Transport block size determination ...................................................................................................... 29
5.1.4 PDSCH resource mapping ......................................................................................................................... 32
5.1.4.1 PDSCH resource mapping with RB symbol level granularity .............................................................. 32
5.1.4.2 PDSCH resource mapping with RE level granularity ........................................................................... 33
5.1.5 Antenna ports quasi co-location ................................................................................................................. 35
5.1.6 UE procedure for receiving reference signals ............................................................................................ 37
5.1.6.1 CSI-RS reception procedure ................................................................................................................. 37
5.1.6.1.1 CSI-RS for tracking ........................................................................................................................ 38
5.1.6.1.2 CSI-RS for L1-RSRP and L1-SINR computation........................................................................... 39
5.1.6.1.3 CSI-RS for mobility ........................................................................................................................ 39
5.1.6.2 DM-RS reception procedure ................................................................................................................. 40
5.1.6.3 PT-RS reception procedure .................................................................................................................. 42
5.1.6.4 SRS reception procedure for CLI ......................................................................................................... 44
5.1.6.5 PRS reception procedure ...................................................................................................................... 44
5.1.7 Code block group based PDSCH transmission .......................................................................................... 47
5.1.7.1 UE procedure for grouping of code blocks to code block groups......................................................... 47
5.1.7.2 UE procedure for receiving code block group based transmissions ..................................................... 47
5.2 UE procedure for reporting channel state information (CSI) ........................................................................... 48
5.2.1 Channel state information framework ........................................................................................................ 48
5.2.1.1 Reporting settings ................................................................................................................................. 48
5.2.1.2 Resource settings .................................................................................................................................. 48
5.2.1.3 (void) .................................................................................................................................................... 49
5.2.1.4 Reporting configurations ...................................................................................................................... 49
5.2.1.4.1 Resource Setting configuration ....................................................................................................... 52
5.2.1.4.2 Report Quantity Configurations ...................................................................................................... 53
5.2.1.4.3 L1-RSRP Reporting ........................................................................................................................ 54
5.2.1.4.4 L1-SINR Reporting ......................................................................................................................... 55
5.2.1.5 Triggering/activation of CSI Reports and CSI-RS ............................................................................... 55
5.2.1.5.1 Aperiodic CSI Reporting/Aperiodic CSI-RS when the triggering PDCCH and the CSI-RS
have the same numerology .............................................................................................................. 55
5.2.1.5.1a Aperiodic CSI Reporting/Aperiodic CSI-RS when the triggering PDCCH and the CSI-RS
have different numerologies............................................................................................................ 57
5.2.1.5.2 Semi-persistent CSI/Semi-persistent CSI-RS ................................................................................. 58
3GPP
Release 16 4 3GPP TS 38.214 V16.1.0 (2020-03)
5.2.1.6 CSI processing criteria.......................................................................................................................... 59

5.2.2 Channel state information .......................................................................................................................... 61
5.2.2.1 Channel quality indicator (CQI) ........................................................................................................... 61
5.2.2.1.1 (void)............................................................................................................................................... 63
5.2.2.2 Precoding matrix indicator (PMI) ......................................................................................................... 63
5.2.2.2.1 Type I Single-Panel Codebook ....................................................................................................... 63
5.2.2.2.2 Type I Multi-Panel Codebook......................................................................................................... 69
5.2.2.2.3 Type II Codebook ........................................................................................................................... 73
5.2.2.2.4 Type II Port Selection Codebook .................................................................................................... 80
5.2.2.2.5 Enhanced Type II Codebook........................................................................................................... 82
5.2.2.2.6 Enhanced Type II Port Selection Codebook ................................................................................... 89
5.2.2.3 Reference signal (CSI-RS) ................................................................................................................... 91
5.2.2.3.1 NZP CSI-RS ................................................................................................................................... 91
5.2.2.4 Channel State Information – Interference Measurement (CSI-IM) ...................................................... 92
5.2.2.5 CSI reference resource definition ......................................................................................................... 93
5.2.3 CSI reporting using PUSCH ...................................................................................................................... 94
5.2.4 CSI reporting using PUCCH ...................................................................................................................... 97
5.2.5 Priority rules for CSI reports ...................................................................................................................... 98
5.3 UE PDSCH processing procedure time ........................................................................................................... 99
5.3.1 Application delay of the minimum scheduling offset restriction ............................................................. 100
5.4 UE CSI computation time .............................................................................................................................. 101
5.5 UE PDSCH reception preparation time with cross carrier scheduling with different subcarrier spacings
for PDCCH and PDSCH ................................................................................................................................ 102
6 Physical uplink shared channel related procedure ............................................................................... 102
6.1 UE procedure for transmitting the physical uplink shared channel ............................................................... 102
6.1.1 Transmission schemes .............................................................................................................................. 104
6.1.1.1 Codebook based UL transmission ...................................................................................................... 105
6.1.1.2 Non-Codebook based UL transmission .............................................................................................. 106
6.1.2 Resource allocation .................................................................................................................................. 107
6.1.2.1 Resource allocation in time domain ................................................................................................... 107
6.1.2.1.1 Determination of the resource allocation table to be used for PUSCH ......................................... 110
6.1.2.2 Resource allocation in frequency domain ........................................................................................... 113
6.1.2.2.1 Uplink resource allocation type 0 ................................................................................................. 113
6.1.2.3 Resource allocation for uplink transmission with configured grant ................................................... 116
6.1.3 UE procedure for applying transform precoding on PUSCH ................................................................... 119
6.1.4 Modulation order, redundancy version and transport block size determination ....................................... 119
6.1.4.1 Modulation order and target code rate determination ......................................................................... 121
6.1.4.2 Transport block size determination .................................................................................................... 124
6.1.5 Code block group based PUSCH transmission ........................................................................................ 125
6.1.5.1 UE procedure for grouping of code blocks to code block groups....................................................... 125
6.1.5.2 UE procedure for transmitting code block group based transmissions ............................................... 126
6.2 UE reference signal (RS) procedure .............................................................................................................. 126
6.2.1 UE sounding procedure ............................................................................................................................ 126
6.2.1.1 UE SRS frequency hopping procedure ............................................................................................... 130
6.2.1.2 UE sounding procedure for DL CSI acquisition ................................................................................. 131
6.2.1.3 UE sounding procedure between component carriers......................................................................... 132
6.2.1.4 UE sounding procedure for positioning purposes ............................................................................... 133
6.2.2 UE DM-RS transmission procedure ......................................................................................................... 134
6.2.3 UE PT-RS transmission procedure........................................................................................................... 135
6.2.3.1 UE PT-RS transmission procedure when transform precoding is not enabled ................................... 135
6.2.3.2 UE PT-RS transmission procedure when transform precoding is enabled ......................................... 137
6.3 UE PUSCH frequency hopping procedure .................................................................................................... 138
6.3.1 Frequency hopping for PUSCH repetition Type A .................................................................................. 138
6.3.2 Frequency hopping for PUSCH repetition Type B .................................................................................. 139
6.4 UE PUSCH preparation procedure time ........................................................................................................ 140
7 UE procedures for transmitting and receiving on a carrier with intra-cell guard bands....................... 141
8 Physical sidelink shared channel related procedures............................................................................ 141
8.1 UE procedure for transmitting the physical sidelink shared channel ............................................................. 141
3GPP
Release 16 5 3GPP TS 38.214 V16.1.0 (2020-03)
8.1.1 Transmission schemes .............................................................................................................................. 142

8.1.2 Resource allocation .................................................................................................................................. 142
8.1.2.1 Resource allocation in time domain ................................................................................................... 142
8.1.2.2 Resource allocation in frequency domain ........................................................................................... 143
8.1.3 Modulation order, target code rate, redundancy version and transport block size determination ............ 143
8.1.3.1 Modulation order and target code rate determination ......................................................................... 143
8.1.3.2 Transport block size determination .................................................................................................... 143
8.1.4 UE procedure for determining the subset of resources to be reported to higher layers in PSSCH
resource selection in sidelink resource allocation mode 2 ........................................................................ 143
8.1.5 UE procedure for determining slots and resource blocks for PSSCH transmission associated with an
SCI format 0-1.......................................................................................................................................... 145
8.1.6 Sidelink congestion control in sidelink resource allocation mode 2 ........................................................ 145
8.2 UE procedure for transmitting sidelink reference signals .............................................................................. 146
8.2.1 CSI-RS transmission procedure ............................................................................................................... 146
8.2.2 PSSCH DM-RS transmission procedure .................................................................................................. 146
8.2.3 PT-RS transmission procedure ................................................................................................................. 146
8.3 UE procedure for receiving the physical sidelink shared channel ................................................................. 146
8.4 UE procedure for receiving reference signals ................................................................................................ 147
8.4.1 CSI-RS reception procedure..................................................................................................................... 147
8.4.2 DM-RS reception procedure for RSRP computation ............................................................................... 147
8.4.3 PT-RS reception procedure ...................................................................................................................... 147
8.5 UE procedure for reporting channel state information (CSI) ......................................................................... 147
8.5.1 Channel state information framework ...................................................................................................... 147
8.5.1.1 Reporting configurations .................................................................................................................... 147
8.5.1.2 Triggering of CSI reports ................................................................................................................... 147
8.5.2 Channel state information ........................................................................................................................ 148
8.5.2.1 CSI reporting quantities ...................................................................................................................... 148
8.5.2.1.1 Channel quality indicator (CQI) ......................................................................................................... 148
8.5.2.2 Reference signal (CSI-RS) ................................................................................................................. 148
8.5.2.3 CSI reference resource definition ....................................................................................................... 148
8.5.3 CSI reporting ............................................................................................................................................ 148
Annex A (informative): Change history ..................................................................................................... 149
3GPP
Release 16 6 3GPP TS 38.214 V16.1.0 (2020-03)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
3GPP
Release 16 7 3GPP TS 38.214 V16.1.0 (2020-03)
1 Scope
The present document specifies and establishes the characteristics of the physicals layer procedures of data channels for
5G-NR.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications"
[2] 3GPP TS 38.201: " NR; Physical Layer – General Description"
[3] 3GPP TS 38.202: "NR; Services provided by the physical layer"
[4] 3GPP TS 38.211: "NR; Physical channels and modulation"
[5] 3GPP TS 38.212: "NR; Multiplexing and channel coding"
[6] 3GPP TS 38.213: "NR; Physical layer procedures for control"
[7] 3GPP TS 38.215: "NR; Physical layer measurements"
[8] 3GPP TS 38.101: "NR; User Equipment (UE) radio transmission and reception"
[9] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception"
[10] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification"
[11] 3GPP TS 38.133: "NR; Requirements for support of radio resource management"
[12] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification"
[13] 3GPP TS 38.306: "NR; User Equipment (UE) radio access capabilities"
[14] 3GPP TS 38.423: "NG-RAN; Xn signalling transport"
[15] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and
modulation"
[16] 3GPP TS 37.213: "Physical layer procedures for shared spectrum channel access"
3GPP
Release 16 8 3GPP TS 38.214 V16.1.0 (2020-03)
3 Definitions, symbols and abbreviations

3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A
term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
3.2 Symbols
For the purposes of the present document, the following symbols apply:
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
TR 21.905 [1].
BWP Bandwidth part

CBG Code block group
CLI Cross Link Interference
CP Cyclic prefix
CQI Channel quality indicator
CPU CSI processing unit
CRB Common resource block
CRC Cyclic redundancy check
CRI CSI-RS Resource Indicator
CSI Channel state information
CSI-RS Channel state information reference signal
CSI-RSRP CSI reference signal received power
CSI-RSRQ CSI reference signal received quality
CSI-SINR CSI signal-to-noise and interference ratio
CW Codeword
DCI Downlink control information
DL Downlink
DM-RS Dedicated demodulation reference signals
EPRE Energy per resource element
IAB-MT Integrated Access and Backhaul – Mobile Terminal
L1-RSRP Layer 1 reference signal received power
LI Layer Indicator
MCS Modulation and coding scheme
PDCCH Physical downlink control channel
PDSCH Physical downlink shared channel
PSS Primary Synchronisation signal
PUCCH Physical uplink control channel
QCL Quasi co-location
PMI Precoding Matrix Indicator
PRB Physical resource block
PRG Precoding resource block group
PRS Positioning reference signal
PT-RS Phase-tracking reference signal
RB Resource block
RBG Resource block group
RI Rank Indicator
RIV Resource indicator value
RS Reference signal
SLIV Start and length indicator value
SR Scheduling Request
SRS Sounding reference signal
SS Synchronisation signal
SSS Secondary Synchronisation signal
3GPP
Release 16 9 3GPP TS 38.214 V16.1.0 (2020-03)
SS-RSRP SS reference signal received power

SS-RSRQ SS reference signal received quality
SS-SINR SS signal-to-noise and interference ratio
TB Transport Block
TCI Transmission Configuration Indicator
TDM Time division multiplexing
UE User equipment
UL Uplink
4 Power control
Throughout this specification, unless otherwise noted, statements using the term "UE" in clauses 4, 5, or 6 are equally
applicable to the IAB-MT part of an IAB node.
4.1 Power allocation for downlink

The gNB determines the downlink transmit EPRE.
For the purpose of SS-RSRP, SS-RSRQ and SS-SINR measurements, the UE may assume downlink EPRE is constant
across the bandwidth. For the purpose of SS-RSRP, SS-RSRQ and SS-SINR measurements, the UE may assume
downlink EPRE is constant over SSS carried in different SS/PBCH blocks. For the purpose of SS-RSRP, SS-RSRQ and
SS-SINR measurements, the UE may assume that the ratio of SSS EPRE to PBCH DM-RS EPRE is 0 dB.
For the purpose of CSI-RSRP, CSI-RSRQ and CSI-SINR measurements, the UE may assume downlink EPRE of a port
of CSI-RS resource configuration is constant across the configured downlink bandwidth and constant across all
configured OFDM symbols.
The downlink SS/PBCH SSS EPRE can be derived from the SS/PBCH downlink transmit power given by the parameter
ss-PBCH-BlockPower provided by higher layers. The downlink SSS transmit power is defined as the linear average
over the power contributions (in [W]) of all resource elements that carry the SSS within the operating system
bandwidth.
The downlink CSI-RS EPRE can be derived from the SS/PBCH block downlink transmit power given by the parameter
ss-PBCH-BlockPower and CSI-RS power offset given by the parameter powerControlOffsetSS provided by higher
layers. The downlink reference-signal transmit power is defined as the linear average over the power contributions (in
[W]) of the resource elements that carry the configured CSI-RS within the operating system bandwidth.
For downlink DM-RS associated with PDSCH, the UE may assume the ratio of PDSCH EPRE to DM-RS EPRE (
 DMRS [dB]) is given by Table 4.1-1 according to the number of DM-RS CDM groups without data as described in
Clause 5.1.6.2. The DM-RS scaling factor  PDSCH

DMRS
specified in Clause 7.4.1.1.2 of [4, TS 38.211] is given by
 DMRS
−
 PDSCH
DMRS
= 10 20
.
Table 4.1-1: The ratio of PDSCH EPRE to DM-RS EPRE
Number of DM-RS CDM DM-RS configuration type 1 DM-RS configuration type 2

groups without data
1 0 dB 0 dB
2 -3 dB -3 dB
3 - -4.77 dB
When the UE is scheduled with a PT-RS port associated with the PDSCH,
- if the UE is configured with the higher layer parameter epre-Ratio, the ratio of PT-RS EPRE to PDSCH EPRE
per layer per RE for PT-RS port (  PTRS ) is given by Table 4.1-2 according to the epre-Ratio, the PT-RS scaling
PTRS
factor  PTRS specified in clause 7.4.1.2.2 of [4, TS 38.211] is given by  PTRS = 10 20 .
- otherwise, the UE shall assume epre-Ratio is set to state '0' in Table 4.1-2 if not configured.
3GPP
Release 16 10 3GPP TS 38.214 V16.1.0 (2020-03)
Table 4.1-2: PT-RS EPRE to PDSCH EPRE per layer per RE (  PTRS )
The number of PDSCH layers

epre-Ratio
1 2 3 4 5 6
0 0 3 4.77 6 7 7.78
1 0 0 0 0 0 0
2 reserved
3 reserved
For link recovery, as described in clause 6 of [6, TS 38.213] the ratio of the PDCCH EPRE to NZP CSI-RS EPRE is
assumed as 0 dB.
5 Physical downlink shared channel related procedures

5.1 UE procedure for receiving the physical downlink shared
channel
For downlink, a maximum of 16 HARQ processes per cell is supported by the UE. The number of processes the UE
may assume will at most be used for the downlink is configured to the UE for each cell separately by higher layer
parameter nrofHARQ-ProcessesForPDSCH, and when no configuration is provided the UE may assume a default
number of 8 processes.
A UE shall upon detection of a PDCCH with a configured DCI format 1_0, 1_1 or 1_2 decode the corresponding
PDSCHs as indicated by that DCI. For any HARQ process ID(s) in a given scheduled cell, the UE is not expected to
receive a PDSCH that overlaps in time with another PDSCH. The UE is not expected to receive another PDSCH for a
given HARQ process until after the end of the expected transmission of HARQ-ACK for that HARQ process, where the
timing is given by Clause 9.2.3 of [6]. In a given scheduled cell, the UE is not expected to receive a first PDSCH in slot
i, with the corresponding HARQ-ACK assigned to be transmitted in slot j, and a second PDSCH starting later than the
first PDSCH with its corresponding HARQ-ACK assigned to be transmitted in a slot before slot j. For any two HARQ
process IDs in a given scheduled cell, if the UE is scheduled to start receiving a first PDSCH starting in symbol j by a
PDCCH ending in symbol i, the UE is not expected to be scheduled to receive a PDSCH starting earlier than the end of
the first PDSCH with a PDCCH that ends later than symbol i. In a given scheduled cell, for any PDSCH corresponding
to SI-RNTI, the UE is not expected to decode a re-transmission of an earlier PDSCH with a starting symbol less than N
symbols after the last symbol of that PDSCH, where the value of N depends on the PDSCH subcarrier spacing
configuration , with N=13 for =0, N=13 for =1, N=20 for =2, and N=24 for =3.
When receiving PDSCH scheduled with SI-RNTI or P-RNTI, the UE may assume that the DM-RS port of PDSCH is
quasi co-located with the associated SS/PBCH block with respect to Doppler shift, Doppler spread, average delay, delay
spread, spatial RX parameters when applicable.
When receiving PDSCH scheduled with RA-RNTI, or MsgB-RNTI, the UE may assume that the DM-RS port of
PDSCH is quasi co-located with the SS/PBCH block or the CSI-RS resource the UE used for RACH association as
applicable, and transmission with respect to Doppler shift, Doppler spread, average delay, delay spread, spatial RX
parameters when applicable. When receiving a PDSCH scheduled with RA-RNTI in response to a random access
procedure triggered by a PDCCH order which triggers contention-free random access procedure for the SpCell [10, TS
38.321], the UE may assume that the DM-RS port of the received PDCCH order and the DM-RS ports of the
corresponding PDSCH scheduled with RA-RNTI are quasi co-located with the same SS/PBCH block or CSI-RS with
respect to Doppler shift, Doppler spread, average delay, delay spread, spatial RX parameters when applicable.
When receiving PDSCH in response to a PUSCH transmission scheduled by a RAR UL grant or corresponding PUSCH
retransmission, or when receiving PDSCH in response to a PUSCH for Type-2 random access procedure, or a PUSCH
scheduled by a fallbackRAR UL grant or corresponding PUSCH retransmission, the UE may assume that the DM-RS
port of PDSCH is quasi co-located with the SS/PBCH block the UE selected for RACH association and transmission
with respect to Doppler shift, Doppler spread, average delay, delay spread, spatial RX parameters when applicable.
If the UE is not configured for PUSCH/PUCCH transmission for at least one serving cell configured with slot formats
comprised of DL and UL symbols, and if the UE is not capable of simultaneous reception and transmission on serving
cell c1 and serving cell c2, the UE is not expected to receive PDSCH on serving cell c1 if the PDSCH overlaps in time
3GPP
Release 16 11 3GPP TS 38.214 V16.1.0 (2020-03)
with SRS transmission (including any interruption due to uplink or downlink RF retuning time [10]) on serving cell c2
not configured for PUSCH/PUCCH transmission.
The UE is not expected to decode a PDSCH scheduled in a serving cell with C-RNTI or MCS-C-RNTI and another
PDSCH scheduled in the same serving cell with CS-RNTI if the PDSCHs partially or fully overlap in time except if the
PDCCH scheduling the PDSCH with C-RNTI or MCS-C-RNTI ends at least 14 symbols before the start of the PDSCH
with CS-RNTI without the corresponding DCI, in which case the UE shall decode the PDSCH scheduled with C-RNTI
or MCS-C-RNTI.
The UE is not expected to decode a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI if another PDSCH in
the same cell scheduled with RA-RNTI or MsgB-RNTI partially or fully overlap in time.
The UE in RRC_IDLE and RRC_INACTIVE modes shall be able to decode two PDSCHs each scheduled with SI-
RNTI, P-RNTI, RA-RNTI or TC-RNTI, with the two PDSCHs partially or fully overlapping in time in non-overlapping
PRBs.
On a frequency range 1 cell, the UE shall be able to decode a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-
RNTI and, during a process of P-RNTI triggered SI acquisition, another PDSCH scheduled with SI-RNTI that partially
or fully overlap in time in non-overlapping PRBs, unless the PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-
RNTI requires Capability 2 processing time according to clause 5.3 in which case the UE may skip decoding of the
scheduled PDSCH with C-RNTI, MCS-C-RNTI, or CS-RNTI.
On a frequency range 2 cell, the UE is not expected to decode a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-
RNTI if in the same cell, during a process of P-RNTI triggered SI acquisition, another PDSCH scheduled with SI-RNTI
partially or fully overlap in time.
The UE is expected to decode a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI during a process of
autonomous SI acquisition.
If the UE is configured by higher layers to decode a PDCCH with its CRC scrambled by a CS-RNTI, the UE shall
receive PDSCH transmissions without corresponding PDCCH transmissions using the higher-layer-provided PDSCH
configuration for those PDSCHs.
If a UE is configured by higher layer parameter PDCCH-Config that contains two different values of
CORESETPoolIndex in ControlResourceSet, the UE may expect to receive multiple PDCCHs scheduling
fully/partially/non-overlapped PDSCHs in time and frequency domain. The UE may expect the reception of
full/partially-overlapped PDSCHs in time only when PDCCHs that schedule two PDSCHs are associated to different
ControlResourceSets having different values of CORESETPoolIndex. For a ControlResourceSet without
CORESETPoolIndex, the UE may assume that the ControlResourceSet is assigned with CORESETPoolIndex as 0.
When the UE is scheduled with full/partially/non-overlapped PDSCHs in time and frequency domain, the full
scheduling information for receiving a PDSCH is indicated and carried only by the corresponding PDCCH, the UE is
expected to be scheduled with the same active BWP and the same SCS. When the UE is scheduled with full/partially-
overlapped PDSCHs in time and frequency domain, the UE can be scheduled with at most two codewords
simultaneously. When PDCCHs that schedule two PDSCHs are associated to different ControlResourceSets having
different values of CORESETPoolIndex, the following operations are allowed:
- For any two HARQ process IDs in a given scheduled cell, if the UE is scheduled to start receiving a first PDSCH
starting in symbol j by a PDCCH associated with a value of CORESETpoolIndex ending in symbol i, the UE can
be scheduled to receive a PDSCH starting earlier than the end of the first PDSCH with a PDCCH associated with
a different value of CORESETpoolIndex that ends later than symbol i.
- In a given scheduled cell, the UE can receive a first PDSCH in slot i, with the corresponding HARQ-ACK
assigned to be transmitted in slot j, and a second PDSCH associated with a value of CORESETpoolindex
different from that of the first PDSCH starting later than the first PDSCH with its corresponding HARQ-ACK
assigned to be transmitted in a slot before slot j.
If PDCCHs that schedule corresponding PDSCHs are associated to the same or different ControlResourceSets having
the same value of CORESETPoolIndex, the UE procedure for receiving the PDSCH upon detection of a PDCCH
follows Clause 5.1.
When a UE is configured by higher layer parameter RepSchemeEnabler set to one of 'FDMSchemeA', 'FDMSchemeB',
'TDMSchemeA', if the UE is indicated with two TCI states in a codepoint of the DCI field 'Transmission Configuration
Indication' and DM-RS port(s) within one CDM group in the DCI field "Antenna Port(s)".
3GPP
Release 16 12 3GPP TS 38.214 V16.1.0 (2020-03)
- When two TCI states are indicated in a DCI and the UE is set to 'FDMSchemeA', the UE shall receive a single
PDSCH transmission occasion of the TB with each TCI state associated to a non-overlapping frequency domain
resource allocation as described in Clause 5.1.2.3.
- When two TCI states are indicated in a DCI and the UE is set to 'FDMSchemeB', the UE shall receive two
PDSCH transmission occasions of the same TB with each TCI state associated to a PDSCH transmission
occasion which has non-overlapping frequency domain resource allocation with respect to the other PDSCH
transmission occasion as described in Clause 5.1.2.3.
- When two TCI states are indicated in a DCI and the UE is set to 'TDMSchemeA', the UE shall receive two
PDSCH transmission occasions of the same TB with each TCI state associated to a PDSCH transmission
occasion which has non-overlapping time domain resource allocation with respect to the other PDSCH
transmission occasion and both PDSCH transmission occasions shall be received within a given slot as described
in Clause 5.1.2.1.
When a UE is configured by the higher layer parameter PDSCH-config that indicates at least one entry in pdsch-
TimeDomainAllocationList containing RepNumR16 in PDSCH-TimeDomainResourceAllocation, the UE may expect to
be indicated with one or two TCI states in a codepoint of the DCI field 'Transmission Configuration Indication' together
with the DCI field "Time domain resource assignment' indicating an entry in pdsch-TimeDomainAllocationList which
contain RepNum16 in PDSCH-TimeDomainResourceAllocation and DM-RS port(s) within one CDM group in the DCI
field "Antenna Port(s)".
- When two TCI states are indicated in a DCI with 'Transmission Configuration Indication' field, the UE may
expect to receive multiple slot level PDSCH transmission occasions of the same TB with two TCI states used
across multiple PDSCH transmission occasions as defined in Clause 5.1.2.1.
- When one TCI state is indicated in a DCI with 'Transmission Configuration Indication' field, the UE may expect
to receive multiple slot level PDSCH transmission occasions of the same TB with one TCI state used across
multiple PDSCH transmission occasions as defined in Clause 5.1.2.1.
When a UE is not indicated with a DCI that DCI field "Time domain resource assignment' indicating an entry in pdsch-
TimeDomainAllocationList which contain RepNumR16 in PDSCH-TimeDomainResourceAllocation, and it is indicated
with two TCI states in a codepoint of the DCI field 'Transmission Configuration Indication' and DM-RS port(s) within
two CDM group in the DCI field "Antenna Port(s)", the UE may expect to receive a single PDSCH where the
association between the DM-RS ports and the TCI states are as defined in Clause 5.1.6.2.
TimeDomainAllocationList which contain RepNumR16 in PDSCH-TimeDomainResourceAllocation, and it is indicated
with one TCI states in a codepoint of the DCI field 'Transmission Configuration Indication', the UE procedure for
receiving the PDSCH upon detection of a PDCCH follows Clause 5.1.
If more than one PDSCH on a serving cell each without a corresponding PDCCH transmission are partially or fully
overlapping in time, a UE is not required to receive a PDSCH among these PDSCHs other than one with the lowest
configured sps-ConfigIndex.
If a UE does not indicate a capability to receive more than one unicast PDSCH per slot, and if there is more than one
PDSCH on a serving cell each without a corresponding PDCCH transmission in a slot, the UE is not required to receive
a PDSCH among these PDSCHs other than one with the lowest configured sps-ConfigIndex on the serving cell.
5.1.1 Transmission schemes

Only one transmission scheme is defined for the PDSCH, and is used for all PDSCH transmissions.
5.1.1.1 Transmission scheme 1

For transmission scheme 1 of the PDSCH, the UE may assume that a gNB transmission on the PDSCH would be
performed with up to 8 transmission layers on antenna ports 1000-1011 as defined in Clause 7.3.1.4 of [4, TS 38.211],
subject to the DM-RS reception procedures in Clause 5.1.6.2.
3GPP
Release 16 13 3GPP TS 38.214 V16.1.0 (2020-03)
5.1.2 Resource allocation

5.1.2.1 Resource allocation in time domain
When the UE is scheduled to receive PDSCH by a DCI, the Time domain resource assignment field value m of the DCI
provides a row index m + 1 to an allocation table. The determination of the used resource allocation table is defined in
Clause 5.1.2.1.1. The indexed row defines the slot offset K0, the start and length indicator SLIV, or directly the start symbol
S and the allocation length L, and the PDSCH mapping type to be assumed in the PDSCH reception.
Given the parameter values of the indexed row:
- The slot allocated for the PDSCH is Ks, where

 2 PDSCH   N CA CA
N slot  
 + K 0 +   , if UE is configured with CA-slot-
  2 PDSCH
slot ,offset , PDCCH ,offset , PDSCH
K S = n  −
 2 PDCCH   2 offset ,PDCCH offset ,PDSCH  

 2 
 2 PDSCH 
offset for at least one of the scheduled and scheduling cell, and Ks =  n   + K0 , otherwise, and where n is
 2 PDCCH 
the slot with the scheduling DCI, and K0 is based on the numerology of PDSCH, and PDSCH and  PDCCH are the
subcarrier spacing configurations for PDSCH and PDCCH, respectively, and
offset, PDCCH and 𝜇offset,PDCCH are the 𝑁slot, offset and the  offset , respectively, which are determined by higher-
CA CA
- 𝑁slot,
CA
layer configured CA-slot-offset, for the cell receiving the PDCCH respectively, 𝑁slot, offset, PDSCH and 𝜇offset,PDSCH
are the 𝑁slot, offset and the  offset , respectively,which are determined by higher-layer configured CA-slot-offset for
CA
the cell receiving the PDSCH, as defined in clause 4.5 of [4, TS 38.211].
- The reference point S0 for starting symbol S is defined as:
- if configured with ReferenceofSLIV-ForDCIFormat1_2, and when receiving PDSCH scheduled by DCI

format 1_2 with CRC scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI with K0=0, and PDSCH mapping
Type B, the starting symbol S is relative to the starting symbol S0 of the PDCCH monitoring occasion where
DCI format 1_2 is detected;
- otherwise, the starting symbol S is relative to the start of the slot using S0=0, and the starting symbol S
relative to the start of the slot, and the number of consecutive symbols L counting from the symbol S
allocated for the PDSCH are determined from the start and length indicator SLIV:
if ( L − 1)  7 then
SLIV = 14  ( L − 1) + S
else
SLIV = 14  (14 − L + 1) + (14 − 1 − S )
where 0  L  14 − S , and
- the PDSCH mapping type is set to Type A or Type B as defined in Clause 7.4.1.1.2 of [4, TS 38.211].
The UE shall consider the S and L combinations defined in table 5.1.2.1-1 satisfying S0 + S + L  14 for normal
cyclic prefix and S0 + S + L  12 for extended cyclic prefix as valid PDSCH allocations:
3GPP
Release 16 14 3GPP TS 38.214 V16.1.0 (2020-03)
Table 5.1.2.1-1: Valid S and L combinations
PDSCH Normal cyclic prefix Extended cyclic prefix

mapping type S L S+L S L S+L
Type A {0,1,2,3} {3,…,14} {3,…,14} {0,1,2,3} {3,…,12} {3,…,12}
(Note 1) (Note 1)
Type B {0,…,12} {2,…,13} {2,…,14} {0,…,10} {2,4,6} {2,…,12}
Note 1: S = 3 is applicable only if dmrs-TypeA-Position = 3
When receiving PDSCH scheduled by DCI format 1_1 or 1_2 in PDCCH with CRC scrambled by C-RNTI, MCS-C-
RNTI, or CS-RNTI with NDI=1, if the UE is configured with pdsch-AggregationFactor in pdsch-config, the same
symbol allocation is applied across the pdsch-AggregationFactor consecutive slots. When receiving PDSCH scheduled
by DCI format 1_1 or 1_2 in PDCCH with CRC scrambled by CS-RNTI with NDI=0, or PDSCH scheduled without
corresponding PDCCH transmission using sps-Config and activated by DCI format 1_1 or 1_2, the same symbol
allocation is applied across the pdsch-AggregationFactor, in sps-Config if configured or in pdsch-config otherwise,
consecutive slots. The UE may expect that the TB is repeated within each symbol allocation among each of the pdsch-
AggregationFactor consecutive slots and the PDSCH is limited to a single transmission layer. For PDSCH scheduled by
DCI format 1_1 or 1_2 in PDCCH with CRC scrambled by CS-RNTI with NDI=0, or PDSCH scheduled without
corresponding PDCCH transmission using sps-Config and activated by DCI format 1_1 or 1_2, the UE is not expected
to be configured with the time duration for the reception of pdsch-AggregationFactor repetitions, in sps-Config if
configured or in pdsch-config otherwise, larger than the time duration derived by the periodicity P obtained from the
corresponding sps-Config. The redundancy version to be applied on the nth transmission occasion of the TB, where n =
0, 1, …pdsch-AggregationFactor -1, is determined according to table 5.1.2.1-2 and "rvid indicated by the DCI
scheduling the PDSCH" in table 5.1.2.1-2 is assumed to be 0 for PDSCH scheduled without corresponding PDCCH
transmission using sps-Config and activated by DCI format 1_1 or 1_2.
Table 5.1.2.1-2: Applied redundancy version when pdsch-AggregationFactor is present
rvid indicated by the DCI rvid to be applied to nth transmission occasion

scheduling the PDSCH n mod 4 = 0 n mod 4 = 1 n mod 4 = 2 n mod 4 = 3
0 0 2 3 1
2 2 3 1 0
3 3 1 0 2
1 1 0 2 3
A PDSCH reception in a slot of a multi-slot PDSCH reception is omitted according to the conditions in Clause 11.1 of
[6, TS38.213].
The UE is not expected to receive a PDSCH with mapping type A in a slot, if the PDCCH scheduling the PDSCH was
received in the same slot and was not contained within the first three symbols of the slot.
The UE is not expected to receive a PDSCH with mapping type B in a slot, if the first symbol of the PDCCH scheduling
the PDSCH was received in a later symbol than the first symbol indicated in the PDSCH time domain resource
allocation.
When the UE configured with [minimumSchedulingOffset] in an active DL BWP it applies a minimum scheduling
offset restriction indicated by the ['Minimum applicable scheduling offset indicator'] field in DCI format 0_1 or 1_1.
When the UE configured with [minimumSchedulingOffset] in active DL BWP and it has not received ['Minimum
applicable scheduling offset indicator'] field in DCI format 0_1 or 1_1, UE shall apply a minimum scheduling offset
restriction indicated based on ['Minimum applicable scheduling offset indicator'] value '0'. When the minimum
scheduling offset restriction is applied the UE is not expected to be scheduled with a DCI in slot n to receive a PDSCH
scheduled with C-RNTI, CS-RNTI or MCS-C-RNTI with K0 smaller than the applicable minimum scheduling offset
restriction K0min. The minimum scheduling offset restriction is not applied when PDSCH transmission is scheduled with
C-RNTI, CS-RNTI or MCS-C-RNTI in common search space associated with CORESET0 and default PDSCH time
domain resource allocation is used or when PDSCH transmission is scheduled with SI-RNTI or RA-RNTI. The
application delay of the change of the minimum scheduling offset restriction is determined in Clause 5.3.1.
The UE is not expected to be configured with ReferenceofSLIV-ForDCIFormat1_2 for serving cells configured for
cross-carrier scheduling with a scheduling cell of a different downlink SCS configuration.
When a UE is configured by the higher layer parameter RepSchemeEnabler set to 'TDMSchemeA' and indicated DM-RS
port(s) within one CDM group in the DCI field "Antenna Port(s)", the number of PDSCH transmission occasions is
3GPP
Release 16 15 3GPP TS 38.214 V16.1.0 (2020-03)
derived by the number of TCI states indicated by the DCI field 'Transmission Configuration Indication' of the
scheduling DCI.
- If two TCI states are indicated by the DCI field 'Transmission Configuration Indication', the UE is expected to
receive two PDSCH transmission occasions, where the first TCI state is applied to the first PDSCH transmission
occasion and resource allocation in time domain for the first PDSCH transmission occasion follows Clause
5.1.2.1. The second TCI state is applied to the second PDSCH transmission occasion, and the second PDSCH
transmission occasion shall have the same number of symbols as the first PDSCH transmission occasion. If the
UE is configured by the higher layers with a value 𝐾̅ in StartingSymbolOffsetK, it shall determine that the first
symbol of the second PDSCH transmission occasion starts after 𝐾 ̅ symbols from the last symbol of the first
̅
PDSCH transmission occasion. If the value 𝐾 is not configured via the higher layer parameter
StartingSymbolOffsetK, 𝐾 ̅ = 0 shall be assumed by the UE. The UE is not expected to receive more than two
PDSCH transmission layers for each PDSCH transmission occasion. For two PDSCH transmission occasions,
the redundancy version to be applied is derived according to Table 5.1.2.1-2, where 𝑛 = 0, 1 applied respectively
to the first and second TCI state.
- Otherwise, the UE is expected to receive a single PDSCH transmission occasion, and the resource allocation in
the time domain follows Clause 5.1.2.1.
When a UE configured by the higher layer parameter PDSCH-config that indicates at least one entry in pdsch-
TimeDomainAllocationList contain RepNumR16 in PDSCH-TimeDomainResourceAllocation,
- If two TCI states are indicated by the DCI field 'Transmission Configuration Indication' together with the DCI
field "Time domain resource assignment' indicating an entry in pdsch-TimeDomainAllocationList which contain
RepNumR16 in PDSCH-TimeDomainResourceAllocation and DM-RS port(s) within one CDM group in the
DCI field "Antenna Port(s)", the same SLIV is applied for all PDSCH transmission occasions, the first TCI state
is applied to the first PDSCH transmission occasion and resource allocation in time domain for the first PDSCH
transmission occasion follows Clause 5.1.2.1.
When the value indicated by RepNumR16 in PDSCH-TimeDomainResourceAllocation equals to two, the

second TCI state is applied to the second PDSCH transmission occasion. When the value indicated by
RepNumR16 in PDSCH-TimeDomainResourceAllocation is larger than two, the UE may be further configured
to enable CycMapping or SeqMapping in RepTCIMapping.
- When CycMapping is enabled, the first and second TCI states are applied to the first and second PDSCH
transmission occasions, respectively, and the same TCI mapping pattern continues to the remaining PDSCH
transmission occasions.
- When SeqMapping is enabled, first TCI state is applied to the first and second PDSCH transmissions, and the
second TCI state is applied to the third and fourth PDSCH transmissions, and the same TCI mapping pattern
continues to the remaining PDSCH transmission occasions.
The UE may expect that each PDSCH transmission occasion is limited to two transmission layers. For all PDSCH
transmission occasions associated with the first TCI state, the redundancy version to be applied is derived according to
Table 5.1.2.1-2, where 𝑛 is counted only considering PDSCH transmission occasions associated with the first TCI state.
The redundancy version for PDSCH transmission occasions associated with the second TCI state is derived according
to Table 5.1.2.1-3, where additional shifting operation for each redundancy version 𝑟𝑣𝑠 is configured by higher layer
parameter RVSeqOffset and 𝑛 is counted only considering PDSCH transmission occasions associated with the second
TCI state.
Table 5.1.2.1-3: Applied redundancy version for the second TCI state when RVSeqOffset is present
rvid indicated by the DCI rvid to be applied to nth transmission occasion with second TCI state
scheduling the PDSCH n mod 4 = 0 n mod 4 = 1 n mod 4 = 2 n mod 4 = 3
0 (0 + 𝑟𝑣𝑠 ) mod 4 (2 + 𝑟𝑣𝑠 ) mod 4 (3 + 𝑟𝑣𝑠 ) mod 4 (1 + 𝑟𝑣𝑠 ) mod 4
- If one TCI state is indicated by the DCI field 'Transmission Configuration Indication' together with the DCI field
"Time domain resource assignment' indicating an entry in pdsch-TimeDomainAllocationList which contain
RepNumR16 in PDSCH-TimeDomainResourceAllocation and DM-RS port(s) within one CDM group in the
3GPP
Release 16 16 3GPP TS 38.214 V16.1.0 (2020-03)
DCI field "Antenna Port(s)", the same SLIV is applied for all PDSCH transmission occasions, the first PDSCH
transmission occasion follows Clause 5.1.2.1, the same TCI state is applied to all PDSCH transmission
occasions. The UE may expect that each PDSCH transmission occasion is limited to two transmission layers. For
all PDSCH transmission occasions, the redundancy version to be applied is derived according to Table 5.1.2.1-2,
where 𝑛 is counted considering PDSCH transmission occasions.
- Otherwise, the UE is expected to receive a single PDSCH transmission occasion, and the resource allocation in
the time domain follows Clause 5.1.2.1.
5.1.2.1.1 Determination of the resource allocation table to be used for PDSCH

Table 5.1.2.1.1-1 and Table 5.1.2.1.1-1A define which PDSCH time domain resource allocation configuration to apply.
Either a default PDSCH time domain allocation A, B or C according to tables 5.1.2.1.1-2, 5.1.2.1.1-3, 5.1.2.1.1-4 and
5.1.2.1.1-5 is applied, or the higher layer configured pdsch-TimeDomainAllocationList or pdsch-
TimeDomainAllocationList-ForDCIFormat1_2 is applied. For operation with shared spectrum channel access, as
described in [16, TS 37.213], UE reinterprets S and L in row 9 of Table 5.1.2.1.1-2 as S=6 and L=7.
3GPP
Release 16 17 3GPP TS 38.214 V16.1.0 (2020-03)
Table 5.1.2.1.1-1: Applicable PDSCH time domain resource allocation for DCI formats 1_0 and 1_1
RNTI PDCCH SS/PBCH pdsch- pdsch-Config PDSCH time

search block and ConfigCommon includes pdsch- domain resource
space CORESET includes pdsch- TimeDomainAllocati allocation to apply
multiplexin TimeDomainAlloca onList
g pattern tionList
SI-RNTI Type0 1 - - Default A for normal
common CP
2 - - Default B
3 - - Default C
SI-RNTI Type0A 1 No - Default A
common 2 No - Default B
3 No - Default C
1,2,3 Yes - pdsch-
TimeDomainAllocati
onList provided in
pdsch-
ConfigCommon
RA-RNTI, Type1 1, 2, 3 No - Default A
MsgB-RNTI, common 1, 2, 3 Yes - pdsch-
TC-RNTI TimeDomainAllocati
onList provided in
pdsch-
ConfigCommon
P-RNTI Type2 1 No - Default A
common 2 No - Default B
3 No - Default C
1,2,3 Yes - pdsch-
TimeDomainAllocati
onList provided in
pdsch-
ConfigCommon
C-RNTI, Any common 1, 2, 3 No - Default A
MCS-C- search 1, 2, 3 Yes - pdsch-
RNTI, CS- space TimeDomainAllocati
RNTI associated onList provided in
with pdsch-
CORESET 0 ConfigCommon
C-RNTI, Any common 1,2,3 No No Default A
MCS-C- search 1,2,3 Yes No pdsch-
RNTI, CS- space not TimeDomainAllocati
RNTI associated onList provided in
with pdsch-
CORESET 0 ConfigCommon
1,2,3 No/Yes Yes pdsch-
UE specific TimeDomainAllocati
search onList provided in
space pdsch-Config
3GPP
Release 16 18 3GPP TS 38.214 V16.1.0 (2020-03)
Table 5.1.2.1.1-1A: Applicable PDSCH time domain resource allocation for DCI format 1_2
pdsch-ConfigCommon pdsch-Config includes pdsch-Config includes PDSCH time domain

includes pdsch- pdsch- pdsch- resource allocation to apply
TimeDomainAllocationList TimeDomainAllocationList TimeDomainAllocationList
-ForDCIformat1_2
No No No Default A
Yes No No pdsch-
TimeDomainAllocationList
provided in pdsch-
ConfigCommon
No/Yes Yes No pdsch-
provided in pdsch-Config
No/Yes No/Yes Yes pdsch-
TimeDomainAllocationList-
ForDCIformat1_2 provided in
pdsch-Config
Table 5.1.2.1.1-2: Default PDSCH time domain resource allocation A for normal CP
Row index dmrs-TypeA- PDSCH K0 S L

Position mapping type
1 2 Type A 0 2 12
3 Type A 0 3 11
2 2 Type A 0 2 10
3 Type A 0 3 9
3 2 Type A 0 2 9
3 Type A 0 3 8
4 2 Type A 0 2 7
3 Type A 0 3 6
5 2 Type A 0 2 5
3 Type A 0 3 4
6 2 Type B 0 9 4
3 Type B 0 10 4
7 2 Type B 0 4 4
3 Type B 0 6 4
8 2,3 Type B 0 5 7
9 2,3 Type B 0 5 2
10 2,3 Type B 0 9 2
11 2,3 Type B 0 12 2
12 2,3 Type A 0 1 13
13 2,3 Type A 0 1 6
14 2,3 Type A 0 2 4
15 2,3 Type B 0 4 7
16 2,3 Type B 0 8 4
3GPP
Release 16 19 3GPP TS 38.214 V16.1.0 (2020-03)
Table 5.1.2.1.1-3: Default PDSCH time domain resource allocation A for extended CP

1 2 Type A 0 2 6
3 Type A 0 3 5
2 2 Type A 0 2 10
3 Type A 0 3 9
3 2 Type A 0 2 9
3 Type A 0 3 8
4 2 Type A 0 2 7
3 Type A 0 3 6
5 2 Type A 0 2 5
3 Type A 0 3 4
6 2 Type B 0 6 4
3 Type B 0 8 2
7 2 Type B 0 4 4
3 Type B 0 6 4
8 2,3 Type B 0 5 6
9 2,3 Type B 0 5 2
10 2,3 Type B 0 9 2
11 2,3 Type B 0 10 2
12 2,3 Type A 0 1 11
13 2,3 Type A 0 1 6
14 2,3 Type A 0 2 4
15 2,3 Type B 0 4 6
16 2,3 Type B 0 8 4
Table 5.1.2.1.1-4: Default PDSCH time domain resource allocation B

1 2,3 Type B 0 2 2
2 2,3 Type B 0 4 2
3 2,3 Type B 0 6 2
4 2,3 Type B 0 8 2
5 2,3 Type B 0 10 2
6 2,3 Type B 1 2 2
7 2,3 Type B 1 4 2
8 2,3 Type B 0 2 4
9 2,3 Type B 0 4 4
10 2,3 Type B 0 6 4
11 2,3 Type B 0 8 4
12 (Note 1) 2,3 Type B 0 10 4
13 (Note 1) 2,3 Type B 0 2 7
14 (Note 1) 2 Type A 0 2 12
3 Type A 0 3 11
15 2,3 Type B 1 2 4
16 Reserved
Note 1: If the PDSCH was scheduled with SI-RNTI in PDCCH Type0 common search space, the UE may
assume that this PDSCH resource allocation is not applied
3GPP
Release 16 20 3GPP TS 38.214 V16.1.0 (2020-03)
Table 5.1.2.1.1-5: Default PDSCH time domain resource allocation C

1 (Note 1) 2,3 Type B 0 2 2
2 2,3 Type B 0 4 2
3 2,3 Type B 0 6 2
4 2,3 Type B 0 8 2
5 2,3 Type B 0 10 2
6 Reserved
7 Reserved
8 2,3 Type B 0 2 4
9 2,3 Type B 0 4 4
10 2,3 Type B 0 6 4
11 2,3 Type B 0 8 4
12 2,3 Type B 0 10 4
13 (Note 1) 2,3 Type B 0 2 7
14 (Note 1) 2 Type A 0 2 12
3 Type A 0 3 11
15 (Note 1) 2,3 Type A 0 0 6
16 (Note 1) 2,3 Type A 0 2 6
Note 1: The UE may assume that this PDSCH resource allocation is not used, if the PDSCH was scheduled
with SI-RNTI in PDCCH Type0 common search space
5.1.2.2 Resource allocation in frequency domain

Two downlink resource allocation schemes, type 0 and type 1, are supported. The UE shall assume that when the
scheduling grant is received with DCI format 1_0, then downlink resource allocation type 1 is used.
If the scheduling DCI is configured to indicate the downlink resource allocation type as part of the Frequency domain
resource assignment field by setting a higher layer parameter resourceAllocation in pdsch-Config to 'dynamicswitch',
for DCI format 1_1 or setting a higher layer parameter resourceAllocation-ForDCIFormat1_2 in pdsch-Config to
'dynamicswitch' for DCI format 1_2, the UE shall use downlink resource allocation type 0 or type 1 as defined by this
DCI field. Otherwise the UE shall use the downlink frequency resource allocation type as defined by the higher layer
parameter resourceAllocation for DCI format 1_1 or by the higher layer parameter resourceAllocation-
ForDCIFormat1_2 for DCI format 1_2.
If a bandwidth part indicator field is not configured in the scheduling DCI or the UE does not support active BWP
change via DCI, the RB indexing for downlink type 0 and type 1 resource allocation is determined within the UE's
active bandwidth part. If a bandwidth part indicator field is configured in the scheduling DCI and the UE supports
active BWP change via DCI, the RB indexing for downlink type 0 and type 1 resource allocation is determined within
the UE's bandwidth part indicated by bandwidth part indicator field value in the DCI. The UE shall upon detection of
PDCCH intended for the UE determine first the downlink bandwidth part and then the resource allocation within the
bandwidth part.
For a PDSCH scheduled with a DCI format 1_0 in any type of PDCCH common search space, regardless of which
bandwidth part is the active bandwidth part, RB numbering starts from the lowest RB of the CORESET in which the
DCI was received; otherwise RB numbering starts from the lowest RB in the determined downlink bandwidth part.
5.1.2.2.1 Downlink resource allocation type 0

In downlink resource allocation of type 0, the resource block assignment information includes a bitmap indicating the
Resource Block Groups (RBGs) that are allocated to the scheduled UE where a RBG is a set of consecutive virtual
resource blocks defined by higher layer parameter rbg-Size configured by PDSCH-Config and the size of the bandwidth
part as defined in Table 5.1.2.2.1-1.
Table 5.1.2.2.1-1: Nominal RBG size P
Bandwidth Part Size Configuration 1 Configuration 2

1 – 36 2 4
37 – 72 4 8
73 – 144 8 16
145 – 275 16 16
3GPP
Release 16 21 3GPP TS 38.214 V16.1.0 (2020-03)
size
The total number of RBGs ( N RBG ) for a downlink bandwidth part i of size N BWP, i PRBs is given by
 (
N RBG =  N BWP
size
,i + ( N BWP ,i mod P ) / P , where
start 
 )
- the size of the first RBG is RBG0size = P − N BW
start
P,i mod P ,
- the size of last RBG is RBGlast

size
(
= N BW
start size
) ( start
)
P,i + N BW P,i mod P if N BW P,i + N BW P,i mod P  0 and P otherwise,
size
- the size of all other RBGs is P.
The bitmap is of size N RBG bits with one bitmap bit per RBG such that each RBG is addressable. The RBGs shall be
indexed in the order of increasing frequency and starting at the lowest frequency of the bandwidth part. The order of
RBG bitmap is such that RBG 0 to RBG N RBG − 1 are mapped from MSB to LSB. The RBG is allocated to the UE if
the corresponding bit value in the bitmap is 1, the RBG is not allocated to the UE otherwise.
5.1.2.2.2 Downlink resource allocation type 1

In downlink resource allocation of type 1, the resource block assignment information indicates to a scheduled UE a set
of contiguously allocated non-interleaved or interleaved virtual resource blocks within the active bandwidth part of size
size PRBs except for the case when DCI format 1_0 is decoded in any common search space in which case the size
N BWP
of CORESET 0 shall be used if CORESET 0 is configured for the cell and the size of initial DL bandwidth part shall be
used if CORESET 0 is not configured for the cell.
A downlink type 1 resource allocation field consists of a resource indication value (RIV) corresponding to a starting
virtual resource block ( RB start ) and a length in terms of contiguously allocated resource blocks L RBs . The resource
indication value is defined by

if ( LRBs − 1)  N BW P / 2
size
 then
RIV = N BW
size
P( LRBs − 1) + RBstart
else
RIV = N BW
size
P( N BW P − LRBs + 1) + ( N BW P − 1 − RBstart )
size size
P − RBstart .
size
where L RBs  1 and shall not exceed N BW
When the DCI size for DCI format 1_0 in USS is derived from the size of DCI format 1_0 in CSS but applied to an
active
active BWP with size of NBWP , a downlink type 1 resource block assignment field consists of a resource indication
value (RIV) corresponding to a starting resource block RBstart = 0, K , 2  K , ,( NBWP
initial
−1)  K and a length in terms of
virtually contiguously allocated resource blocks LRBs = K , 2  K , , NBWP  K , where NBWP
initial initial
is given by
- the size of CORESET 0 if CORESET 0 is configured for the cell;
- the size of initial DL bandwidth part if CORESET 0 is not configured for the cell.
The resource indication value is defined by:
if ( L 'RBs − 1)   N BWP / 2 then

initial
RIV = NBWP
initial
( L 'RBs −1) + RB 'start
else
RIV = NBWP
initial initial
( NBWP − L 'RBs + 1) + ( NBWP
initial
−1 − RB 'start )
3GPP
Release 16 22 3GPP TS 38.214 V16.1.0 (2020-03)
where L 'RBs = LRBs K , RB 'start = RBstart K and where L 'RBs shall not exceed NBWP
initial
− RB 'start .
active
If NBWP  NBWP
initial
, K is the maximum value from set {1, 2, 4, 8} which satisfies K   N BWP
active initial
/ N BWP  ; otherwise K = 1.
When the scheduling grant is received with DCI format 1_2, a downlink type 1 resource allocation field consists of a
resource indication value (RIV) corresponding to a starting resource block group RBGstart=0, 1, …, NRBG-1 and a length
in terms of virtually contiguously allocated resource block groups LRBGs=1, …, NRBG, where the resource block groups
are defined as in 5.1.2.2.1 with P defined by ResourceAllocationType1-granularity-ForDCIFormat1_2 if the UE is
configured with higher layer parameter ResourceAllocationType1-granularity-ForDCIFormat1_2, and P=1 otherwise.
The resource indication value is defined by
if ( LRBGs − 1)   N RBG / 2  then
RIV = N RBG ( LRBGs − 1) + RBGstart
else
RIV = N RBG ( N RBG − LRBGs + 1) + ( N RBG − 1 − RBGstart )
where LRBGs  1 and shall not exceed N RBG − RBGstart .
5.1.2.3 Physical resource block (PRB) bundling

The PRB bundling procedures for PDSCH scheduled by PDCCH with DCI format 1_1 described in this clause equally
apply to PDSCH scheduled by PDCCH with DCI format 1_2, by applying the parameters of prb-BundlingType-
ForDCIFormat1_2 instead of prb-BundlingType as well as vrb-ToPRB-Interleaver-ForDCIFormat1_2 instead of vrb-
ToPRB-Interleaver.
A UE may assume that precoding granularity is PBW  P.i can

 P.i consecutive resource blocks in the frequency domain. PBW
be equal to one of the values among {2, 4, wideband}.
 P.i is determined as "wideband", the UE is not expected to be scheduled with non-contiguous PRBs and the UE
If PBW
may assume that the same precoding is applied to the allocated resource.
 P.i is determined as one of the values among {2, 4}, Precoding Resource Block Group (PRGs) partitions the
If PBW
 P.i consecutive PRBs. Actual number of consecutive PRBs in each PRG could be one or more.
bandwidth part i with PBW
The first PRG size is given by PBW P,i − N BWP,i mod PBW P and the last PRG size given by P,i + N BW P,i ) mod PBW P,i
' start ' start size '
( N BW
P,i + N BW P,i ) mod PBW P,i  0 , and the last PRG size is PBW P,i if ( N BW P,i + N BW P,i ) mod PBW P,i = 0 .
start size ' ' start size '
if ( N BW
The UE may assume the same precoding is applied for any downlink contiguous allocation of PRBs in a PRG.
For PDSCH carrying SIB1 scheduled by PDCCH with CRC scrambled by SI-RNTI, a PRG is partitioned from the
lowest numbered resource block of CORESET 0 if the corresponding PDCCH is associated with CORESET 0 and
Type0-PDCCH common search space and is addressed to SI-RNTI; otherwise, a PRG is partitioned from common
resource block 0.
 P.i is equal to 2 PRBs.

If a UE is scheduled a PDSCH with DCI format 1_0, the UE shall assume that PBW
When receiving PDSCH scheduled by PDCCH with DCI format 1_1 with CRC scrambled by C-RNTI, MCS-C-RNTI,
 P.i for bandwidth part is equal to 2 PRBs unless configured by the higher layer parameter prb-
or CS-RNTI, PBW
BundlingType given by PDSCH-Config.
or CS-RNTI, if the higher layer parameter prb-BundlingType is set to 'dynamicBundling', the higher layer parameters
 P.i values, the first set can take one or two PBW
bundleSizeSet1 and bundleSizeSet2 configure two sets of PBW  P.i values
 P.i value among {2, 4, wideband}.
among {2, 4, wideband}, and the second set can take one PBW
If the PRB bundling size indicator signalled in DCI format 1_1 as defined in Clause 7.3.1.2.2 of [5, TS 38.212]
3GPP
Release 16 23 3GPP TS 38.214 V16.1.0 (2020-03)
-  P.i value from the second set of PBW

is set to '0', the UE shall use the PBW  P.i values when receiving PDSCH
scheduled by the same DCI.
- is set to '1' and one value is configured for the first set of PBW  P.i value when
 P.i values, the UE shall use this PBW
receiving PDSCH scheduled by the same DCI
-  P.i values as 'n2-wideband' (corresponding to

is set to '1' and two values are configured for the first set of PBW
two PBW  P.i values 2 and wideband) or 'n4-wideband' (corresponding to two PBW  P.i values 4 and wideband), the
UE shall use the value when receiving PDSCH scheduled by the same DCI as follows:
size
- If the scheduled PRBs are contiguous and the size of the scheduled PRBs is larger than N BW P,i / 2 ,  P.i is
PBW
 P.i is set to the remaining configured value of 2 or 4,
the same as the scheduled bandwidth, otherwise PBW
respectively.
 P.i value is configured
or CS-RNTI, if the higher layer parameter prb-BundlingType is set to 'staticBundling', the PBW
with the single value indicated by the higher layer parameter bundleSize.
When a UE is configured with nominal RBG size 𝑃 = 2 for bandwidth part i according to Clause 5.1.2.2.1, or when a
UE is configured with interleaving unit of 2 for VRB to PRB mapping provided by the higher layer parameter vrb-
ToPRB-Interleaver given by PDSCH-Config for bandwidth part i, the UE is not expected to be configured with PBW P.i =
4.
For a UE configured by the higher layer parameter RepSchemeEnabler set to 'FDMSchemeA' or 'FDMSchemeB', and
when the UE is indicated with two TCI states in a codepoint of the DCI field 'Transmission Configuration Indication
and DM-RS port(s) within one CDM group in the DCI field "Antenna Port(s)",
𝑛𝑃𝑅𝐵
-  P.i is determined as "wideband", the first ⌈
If PBW ⌉ PRBs are assigned to the first TCI state and the remaining
2
𝑛𝑃𝑅𝐵
⌊ ⌋ PRBs are assigned to the second TCI state, where 𝑛𝑃𝑅𝐵 is the total number of allocated PRBs for the UE.
2
-  P.i is determined as one of the values among {2, 4}, even PRGs within the allocated frequency domain
If PBW
resources are assigned to the first TCI state and odd PRGs within the allocated frequency domain resources are
assigned to the second TCI state.
- The UE is not expected to receive more than two PDSCH transmission layers for each PDSCH transmission
occasion.
For a UE configured by the higher layer parameter RepSchemeEnabler set to 'FDMSchemeB', and when the UE is
indicated with two TCI states in a codepoint of the DCI field 'Transmission Configuration Indication and DM-RS
port(s) within one CDM group in the DCI field "Antenna Port(s)", each PDSCH transmission occasion shall follow the
Clause 7.3.1 of [4, TS 38.211] with the mapping to resource elements determined by the assigned PRBs for
corresponding TCI state of the PDSCH transmission occasion, and the UE shall only expect at most two code blocks
per PDSCH transmission occasion when a single transmission layer is scheduled and a single code block per PDSCH
transmission occasion when two transmission layers are scheduled. For two PDSCH transmission occasions, the
redundancy version to be applied is derived according to Table 5.1.2.1-2, where 𝑛 = 0, 1 are applied to the first and
second TCI state, respectively.
5.1.3 Modulation order, target code rate, redundancy version and

transport block size determination
To determine the modulation order, target code rate, and transport block size(s) in the physical downlink shared
channel, the UE shall first
- read the 5-bit modulation and coding scheme field (IMCS) in the DCI to determine the modulation order (Qm) and
target code rate (R) based on the procedure defined in Clause 5.1.3.1, and
- read redundancy version field (rv) in the DCI to determine the redundancy version.
and second
3GPP
Release 16 24 3GPP TS 38.214 V16.1.0 (2020-03)
- the UE shall use the number of layers (ʋ), the total number of allocated PRBs before rate matching (nPRB) to
determine to the transport block size based on the procedure defined in Clause 5.1.3.2.
The UE may skip decoding a transport block in an initial transmission if the effective channel code rate is higher than
0.95, where the effective channel code rate is defined as the number of downlink information bits (including CRC bits)
divided by the number of physical channel bits on PDSCH.
The UE is not expected to handle any transport blocks (TBs) in a 14 consecutive-symbol duration for normal CP (or 12
for extended CP) ending at the last symbol of the latest PDSCH transmission within an active BWP on a serving cell
whenever
′ 𝐶𝑖′ X 1
2max (0,𝜇−𝜇 ) . ∑ ⌊ ⌋ 𝑥𝑖 . 𝐹𝑖 > ⌈ ⌉ . . 𝑇𝐵𝑆𝐿𝐵𝑅𝑀
𝐿𝑖 4 𝑅𝐿𝐵𝑅𝑀
𝑖∈𝑆
where, for the serving cell,
- S is the set of TBs belonging to PDSCH(s) that are partially or fully contained in the consecutive-symbol
duration
- for the ith TB
- Ci' is the number of scheduled code blocks for as defined in [5, 38.212].
- Li is the number of OFDM symbols assigned to the PDSCH
- xi is the number of OFDM symbols of the PDSCH contained in the consecutive-symbol duration
𝑗 𝑗
- 𝐹𝑖 = max (min(𝑘0,𝑖 + 𝐸𝑖 , 𝑁𝑐𝑏,𝑖 )) based on the values defined in Clause 5.4.2.1 [5, TS 38.212]
𝑗=0,...,𝐽−1
𝑗
- 𝑘0,𝑖 is the starting location of RV for the 𝑗th transmission
𝑗
- 𝐸𝑖 = min(𝐸𝑟 ) of the scheduled code blocks for the 𝑗th transmission
- 𝑁𝑐𝑏,𝑖 is the circular buffer length
- 𝐽 − 1 is the current (re)transmission for the ith TB
- 𝜇′ corresponds to the subcarrier spacing of the BWP (across all configured BWPs of a carrier) that has the
largest configured number of PRBs
- in case there is more than one BWP corresponding to the largest configured number of PRBs, µ' follows
the BWP with the largest subcarrier spacing.
- 𝜇 corresponds to the subcarrier spacing of the active BWP
- RLBRM = 2/3 as defined in Clause 5.4.2.1 [5, TS 38.212]
- TBSLBRM as defined in Clause 5.4.2.1 [5, TS 38.212]
- X as defined for downlink in Clause 5.4.2.1 [5, TS 38.212].
If the UE skips decoding, the physical layer indicates to higher layer that the transport block is not successfully
decoded.
Within a cell group, a UE is not required to handle PDSCH(s) transmissions in slot sj in serving cell-j, and for j = 0,1,2..
J-1, slot sj overlapping with any given point in time, if the following condition is not satisfied at that point in time:
𝐽−1
∑𝑀−1
𝑚=0 𝑉𝑗,𝑚
∑ 𝜇(𝑗)
≤ 𝐷𝑎𝑡𝑎𝑅𝑎𝑡𝑒
𝑗=0
𝑇𝑠𝑙𝑜𝑡
where,
- J is the number of configured serving cells belonging to a frequency range
3GPP
Release 16 25 3GPP TS 38.214 V16.1.0 (2020-03)
- for the j-th serving cell,
- M is the number of TB(s) transmitted in slot sj.
- Tslot(j) =10-3/2(j), where (j) is the numerology for PDSCH(s) in slot sj of the j-th serving cell.
𝐴
- for the m-th TB, 𝑉𝑗,𝑚 = 𝐶′ ∙ ⌊ ⌋
𝐶
- A is the number of bits in the transport block as defined in Clause 7.2.1 [5, TS 38.212]
- C is the total number of code blocks for the transport block defined in Clause 5.2.2 [5, TS 38.212].
- 𝐶′ is the number of scheduled code blocks for the transport block as defined in Clause 5.4.2.1 [5, TS
38.212]
- 𝐷𝑎𝑡𝑎𝑅𝑎𝑡𝑒 [Mbps] is computed as the maximum data rate summed over all the carriers in the frequency range
for any signaled band combination and feature set consistent with the configured servings cells, where the data
rate value is given by the formula in Clause 4.1.2 in [13, TS 38.306], including the scaling factor f(i).
For a j-th serving cell, if higher layer parameter processingType2Enabled of PDSCH-ServingCellConfig is configured
for the serving cell and set to enable, or if at least one IMCS > W for a PDSCH, where W = 28 for MCS tables 5.1.3.1-1
and 5.1.3.1-3, and W = 27 for MCS table 5.1.3.1-2, the UE is not required to handle PDSCH transmissions, if the
following condition is not satisfied:
∑𝑀−1
𝜇 ≤ 𝐷𝑎𝑡𝑎𝑅𝑎𝑡𝑒𝐶𝐶
𝐿 × 𝑇𝑠
where
- 𝐿 is the number of symbols assigned to the PDSCH
- M is the number of TB(s) in the PDSCH

10−3
where  is the numerology of the PDSCH
𝜇
- 𝑇𝑠 = 𝑠𝑙𝑜𝑡
2𝜇 ∙𝑁𝑠𝑦𝑚𝑏
𝐴
𝐶
- C is the total number of code blocks for the transport block defined in Clause 5.2.2 [5, TS 38.212]
- 𝐶′ is the number of scheduled code blocks for the transport block as defined in Clause 5.4.2.1 [5, TS 38.212]
- 𝐷𝑎𝑡𝑎𝑅𝑎𝑡𝑒𝐶𝐶 [Mbps] is computed as the maximum data rate for a carrier in the frequency band of the serving
cell for any signaled band combination and feature set consistent with the serving cell, where the data rate value
is given by the formula in Clause 4.1.2 in [13, TS 38.306], including the scaling factor f(i).
5.1.3.1 Modulation order and target code rate determination

For the PDSCH scheduled by a PDCCH with DCI format 1_0, format 1_1 or format 1_2 with CRC scrambled by C-
RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI, SI-RNTI, RA-RNTI, MsgB-RNTI, or P-RNTI, or for the PDSCH
scheduled without corresponding PDCCH transmissions using the higher-layer-provided PDSCH configuration SPS-
Config,
if the higher layer parameter mcs-Table-ForDCIFormat1_2 given by PDSCH-Config is set to 'qam256', and the PDSCH
is scheduled by a PDCCH with DCI format 1_2 with CRC scrambled by C-RNTI
- the UE shall use IMCS and Table 5.1.3.1-2 to determine the modulation order (Qm) and Target code rate (R) used
in the physical downlink shared channel.
elseif the UE is not configured with MCS-C-RNTI, the higher layer parameter mcs-Table-ForDCIFormat1_2 given by
PDSCH-Config is set to 'qam64LowSE', and the PDSCH is scheduled by a PDCCH with DCI format 1_2 scrambled by
C-RNTI
3GPP
Release 16 26 3GPP TS 38.214 V16.1.0 (2020-03)
elseif the higher layer parameter mcs-Table given by PDSCH-Config is set to 'qam256', and the PDSCH is scheduled by
a PDCCH with DCI format 1_1 with CRC scrambled by C-RNTI
elseif the UE is not configured with MCS-C-RNTI, the higher layer parameter mcs-Table given by PDSCH-Config is
set to 'qam64LowSE', and the PDSCH is scheduled by a PDCCH with a DCI format other than DCI format 1_2 in a
UE-specific search space with CRC scrambled by C-RNTI
elseif the UE is configured with MCS-C-RNTI, and the PDSCH is scheduled by a PDCCH with CRC scrambled by
MCS-C-RNTI
elseif the UE is not configured with the higher layer parameter mcs-Table given by SPS-config, the higher layer
parameter mcs-Table-ForDCIFormat1_2 given by PDSCH-Config is set to 'qam256', and the PDSCH is scheduled by a
PDCCH with DCI format 1_2 with CRC scrambled by CS-RNTI
elseif the UE is not configured with the higher layer parameter mcs-Table given by SPS-Config, the higher layer
parameter mcs-Table given by PDSCH-Config is set to 'qam256',
- if the PDSCH is scheduled by a PDCCH with DCI format 1_1 with CRC scrambled by CS-RNTI or
- if the PDSCH is scheduled without corresponding PDCCH transmission using SPS-Config,
- the UE shall use IMCS and Table 5.1.3.1-2 to determine the modulation order (Qm) and Target code rate (R)
used in the physical downlink shared channel.
elseif the UE is configured with the higher layer parameter mcs-Table given by SPS-Config set to 'qam64LowSE'
- if the PDSCH is scheduled by a PDCCH with CRC scrambled by CS-RNTI or
- if the PDSCH is scheduled without corresponding PDCCH transmission using SPS-Config,
used in the physical downlink shared channel.
else
end
The UE is not expected to decode a PDSCH scheduled with P-RNTI, RA-RNTI, SI-RNTI and Qm > 2
For a UE configured with FDMSchemeB, and when the UE is indicated with two TCI states in a codepoint of the DCI
field 'Transmission Configuration Indication and DM-RS port(s) within one CDM group in the DCI field "Antenna
Port(s)", the determined modulation order of PDSCH transmission occasion associated with the first TCI state is
applied to the PDSCH transmission occasion associated with the second TCI state.
3GPP
Release 16 27 3GPP TS 38.214 V16.1.0 (2020-03)
Table 5.1.3.1-1: MCS index table 1 for PDSCH
MCS Index Modulation Order Spectral

Target code Rate R x [1024]
IMCS Qm efficiency
0 2 120 0.2344
1 2 157 0.3066
2 2 193 0.3770
3 2 251 0.4902
4 2 308 0.6016
5 2 379 0.7402
6 2 449 0.8770
7 2 526 1.0273
8 2 602 1.1758
9 2 679 1.3262
10 4 340 1.3281
11 4 378 1.4766
12 4 434 1.6953
13 4 490 1.9141
14 4 553 2.1602
15 4 616 2.4063
16 4 658 2.5703
17 6 438 2.5664
18 6 466 2.7305
19 6 517 3.0293
20 6 567 3.3223
21 6 616 3.6094
22 6 666 3.9023
23 6 719 4.2129
24 6 772 4.5234
25 6 822 4.8164
26 6 873 5.1152
27 6 910 5.3320
28 6 948 5.5547
29 2 reserved
30 4 reserved
31 6 reserved
3GPP
Release 16 28 3GPP TS 38.214 V16.1.0 (2020-03)

IMCS Qm efficiency
0 2 120 0.2344
1 2 193 0.3770
2 2 308 0.6016
3 2 449 0.8770
4 2 602 1.1758
5 4 378 1.4766
6 4 434 1.6953
7 4 490 1.9141
8 4 553 2.1602
9 4 616 2.4063
10 4 658 2.5703
11 6 466 2.7305
12 6 517 3.0293
13 6 567 3.3223
14 6 616 3.6094
15 6 666 3.9023
16 6 719 4.2129
17 6 772 4.5234
18 6 822 4.8164
19 6 873 5.1152
20 8 682.5 5.3320
21 8 711 5.5547
22 8 754 5.8906
23 8 797 6.2266
24 8 841 6.5703
25 8 885 6.9141
26 8 916.5 7.1602
27 8 948 7.4063
28 2 reserved
29 4 reserved
30 6 reserved
31 8 reserved
3GPP
Release 16 29 3GPP TS 38.214 V16.1.0 (2020-03)

IMCS Qm efficiency
0 2 30 0.0586
1 2 40 0.0781
2 2 50 0.0977
3 2 64 0.1250
4 2 78 0.1523
5 2 99 0.1934
6 2 120 0.2344
7 2 157 0.3066
8 2 193 0.3770
9 2 251 0.4902
10 2 308 0.6016
11 2 379 0.7402
12 2 449 0.8770
13 2 526 1.0273
14 2 602 1.1758
15 4 340 1.3281
16 4 378 1.4766
17 4 434 1.6953
18 4 490 1.9141
19 4 553 2.1602
20 4 616 2.4063
21 6 438 2.5664
22 6 466 2.7305
23 6 517 3.0293
24 6 567 3.3223
25 6 616 3.6094
26 6 666 3.9023
27 6 719 4.2129
28 6 772 4.5234
29 2 reserved
30 4 reserved
31 6 reserved
5.1.3.2 Transport block size determination

In case the higher layer parameter maxNrofCodeWordsScheduledByDCI indicates that two codeword transmission is
enabled, then one of the two transport blocks is disabled by DCI format 1_1 if IMCS = 26 and if rvid = 1 for the
corresponding transport block. If both transport blocks are enabled, transport block 1 and 2 are mapped to codeword 0
and 1 respectively. If only one transport block is enabled, then the enabled transport block is always mapped to the first
codeword.
For the PDSCH assigned by a PDCCH with DCI format 1_0, format 1_1 or format 1_2 with CRC scrambled by C-
RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI, or SI-RNTI, if Table 5.1.3.1-2 is used and 0  I MCS  27 , or a table other
than Table 5.1.3.1-2 is used and 0  I MCS  28 , the UE shall, except if the transport block is disabled in DCI format
1_1, first determine the TBS as specified below:
1) The UE shall first determine the number of REs (NRE) within the slot.
- '
A UE first determines the number of REs allocated for PDSCH within a PRB ( N RE ) by
'
N RE = N scRB  N symb
sh
− N DMRS
PRB
− N oh
PRB RB
, where N sc = 12 is the number of subcarriers in a physical resource
sh
block, N symb is the number of symbols of the PDSCH allocation within the slot, N DMRS
PRB is the number of
REs for DM-RS per PRB in the scheduled duration including the overhead of the DM-RS CDM groups
without data, as indicated by DCI format 1_1 or format 1_2 or as described for format 1_0 in Clause 5.1.6.2,
PRB is the overhead configured by higher layer parameter xOverhead in PDSCH-ServingCellConfig.
and N oh
PRB
If the xOverhead in PDSCH-ServingCellconfig is not configured (a value from 0, 6, 12, or 18), the N oh is
3GPP
Release 16 30 3GPP TS 38.214 V16.1.0 (2020-03)
set to 0. If the PDSCH is scheduled by PDCCH with a CRC scrambled by SI-RNTI, RA-RNTI, MsgB-RNTI
PRB
or P-RNTI, N oh is assumed to be 0.
- (
A UE determines the total number of REs allocated for PDSCH ( N RE ) by N RE = min 156, N RE  nPRB ,
'
)
where nPRB is the total number of allocated PRBs for the UE.
2) Intermediate number of information bits (Ninfo) is obtained by N inf o = N RE ·R·Qm · .
If N inf o  3824
Use step 3 as the next step of the TBS determination
else
Use step 4 as the next step of the TBS determination
end if
3) When N inf o  3824 , TBS is determined as follows
  N inf o  
quantized intermediate number of information bits N inf o = max  24,2 · 
' n
- n   , where
  2 
n = max (3, log 2 (N inf o ) − 6) .
- '
use Table 5.1.3.2-1 find the closest TBS that is not less than N inf .
o
Table 5.1.3.2-1: TBS for N inf o  3824
Index TBS Index TBS Index TBS Index TBS

1 24 31 336 61 1288 91 3624
2 32 32 352 62 1320 92 3752
3 40 33 368 63 1352 93 3824
4 48 34 384 64 1416
5 56 35 408 65 1480
6 64 36 432 66 1544
7 72 37 456 67 1608
8 80 38 480 68 1672
9 88 39 504 69 1736
10 96 40 528 70 1800
11 104 41 552 71 1864
12 112 42 576 72 1928
13 120 43 608 73 2024
14 128 44 640 74 2088
15 136 45 672 75 2152
16 144 46 704 76 2216
17 152 47 736 77 2280
18 160 48 768 78 2408
19 168 49 808 79 2472
20 176 50 848 80 2536
21 184 51 888 81 2600
22 192 52 928 82 2664
23 208 53 984 83 2728
24 224 54 1032 84 2792
25 240 55 1064 85 2856
26 256 56 1128 86 2976
27 272 57 1160 87 3104
28 288 58 1192 88 3240
29 304 59 1224 89 3368
30 320 60 1256 90 3496
3GPP
Release 16 31 3GPP TS 38.214 V16.1.0 (2020-03)
4) When N inf o  3824 , TBS is determined as follows.
  Ninf o − 24  
quantized intermediate number of information bits Ninf o = max  3840, 2  round
' n
-    , where
  2 
n
n = log 2 (N inf o − 24 ) − 5 and ties in the round function are broken towards the next largest integer.
- if R  1 / 4
 N ' + 24   N inf
'
o + 24

TBS = 8· C·  inf o  − 24 , where C =  
 8· C   3816 
else
o  8424
'
if N inf
 N ' + 24   N inf
'
o + 24

TBS = 8· C·  inf o  − 24 , where C =  
 8· C   8424 
else
 N ' + 24 
TBS = 8·  inf o  − 24
 8 
end if
end if
else if Table 5.1.3.1-2 is used and 28  I MCS  31 ,
- the TBS is assumed to be as determined from the DCI transported in the latest PDCCH for the same transport
block using 0  I MCS  27 . If there is no PDCCH for the same transport block using 0  I MCS  27 , and if
the initial PDSCH for the same transport block is semi-persistently scheduled, the TBS shall be determined
from the most recent semi-persistent scheduling assignment PDCCH.
else
block using 0  I MCS  28 . If there is no PDCCH for the same transport block using 0  I MCS  28 , and if the
initial PDSCH for the same transport block is semi-persistently scheduled, the TBS shall be determined from
the most recent semi-persistent scheduling assignment PDCCH.
The UE is not expected to receive a PDSCH assigned by a PDCCH with CRC scrambled by SI-RNTI with a TBS
exceeding 2976 bits.
For a UE configured with FDMSchemeB and indicated with two TCI states in a codepoint of the DCI field
'Transmission Configuration Indication and DM-RS port(s) within one CDM group in the DCI field "Antenna Port(s)",
the TBS determination follows the steps 1-4 with the following modification in step 1: a UE determines the total
( '
)
number of REs allocated for PDSCH ( N RE ) by N RE = min 156, N RE  nPRB , where nPRB is the total number of
allocated PRBs corresponding to the first TCI state. and the determined TBS of PDSCH transmission occasion
associated with the first TCI state is also applied to the PDSCH transmission occasion associated with the second TCI
state.
For the PDSCH assigned by a PDCCH with DCI format 1_0 with CRC scrambled by P-RNTI, or RA-RNTI, MsgB-
RNTI, TBS determination follows the steps 1-4 with the following modification in step 2: a scaling
N inf o = S  N RE  R  Qm  is applied in the calculation of Ninfo, where the scaling factor is determined based on the TB
scaling field in the DCI as in Table 5.1.3.2-2.
3GPP
Release 16 32 3GPP TS 38.214 V16.1.0 (2020-03)
Table 5.1.3.2-2: Scaling factor of Ninfo for P-RNTI, RA-RNTI and MsgB-RNTI
TB scaling field Scaling factor S

00 1
01 0.5
10 0.25
11
The NDI and HARQ process ID, as signalled on PDCCH, and the TBS, as determined above, shall be reported to higher
layers.
5.1.4 PDSCH resource mapping

When receiving the PDSCH scheduled with SI-RNTI and the system information indicator in DCI is set to 0, the UE
shall assume that no SS/PBCH block is transmitted in REs used by the UE for a reception of the PDSCH.
When receiving the PDSCH scheduled with SI-RNTI and the system information indicator in DCI is set to 1, RA-
RNTI, MsgB-RNTI, P-RNTI or TC-RNTI, the UE assumes SS/PBCH block transmission according to ssb-
PositionsInBurst, and if the PDSCH resource allocation overlaps with PRBs containing SS/PBCH block transmission
resources the UE shall assume that the PRBs containing SS/PBCH block transmission resources are not available for
PDSCH in the OFDM symbols where SS/PBCH block is transmitted.
A UE expects a configuration provided by ssb-PositionsInBurst in ServingCellConfigCommon to be same as a

configuration provided by ssb-PositionsInBurst in SIB1.
When receiving PDSCH scheduled by PDCCH with CRC scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI, or
PDSCHs with SPS, the REs corresponding to the configured or dynamically indicated resources in Clauses 5.1.4.1,
5.1.4.2 are not available for PDSCH. Furthermore, the UE assumes SS/PBCH block transmission according to ssb-
PositionsInBurst if the PDSCH resource allocation overlaps with PRBs containing SS/PBCH block transmission
resources, the UE shall assume that the PRBs containing SS/PBCH block transmission resources are not available for
PDSCH in the OFDM symbols where SS/PBCH block is transmitted.
A UE is not expected to handle the case where PDSCH DM-RS REs are overlapping, even partially, with any RE(s) not
available for PDSCH.
5.1.4.1 PDSCH resource mapping with RB symbol level granularity

The procedures for PDSCH scheduled by PDCCH with DCI format 1_1 described in this clause equally apply to
PDSCH scheduled by PDCCH with DCI format 1_2, by applying the parameters of rateMatchPatternGroup1-
ForDCIFormat1_2, rateMatchPatternGroup2-ForDCIFormat1_2 instead of rateMatchPatternGroup1 and
rateMatchPatternGroup2.
A UE may be configured with any of the following higher layer parameters indicating REs declared as not available for
PDSCH:
- rateMatchPatternToAddModList given by PDSCH-Config, by ServingCellConfig or by

ServingCellConfigCommon and configuring up to 4 RateMatchPattern(s) per BWP and up to 4
RateMatchPattern(s) per serving-cell. A RateMatchPattern may contain:
- within a BWP, when provided by PDSCH-Config or within a serving cell when provided by
ServingCellConfig or ServingCellConfigCommon, a pair of reserved resources with numerology provided by
higher layer parameter subcarrierSpacing given by RateMatchPattern when configured per serving cell or by
numerology of associated BWP when configured per BWP .The pair of reserved resources are respectively
indicated by an RB level bitmap (higher layer parameter resourceBlocks given by RateMatchPattern ) with
1RB granularity and a symbol level bitmap spanning one or two slots (higher layer parameters
symbolsInResourceBlock given by RateMatchPattern ) for which the reserved RBs apply. A bit value equal
to 1 in the RB and symbol level bitmaps indicates that the corresponding resource is not available for
PDSCH. For each pair of RB and symbol level bitmaps, a UE may be configured with a time-domain pattern
(higher layer parameter periodicityAndPattern given by RateMatchPattern ), where each bit of
periodicityAndPattern corresponds to a unit equal to a duration of the symbol level bitmap, and a bit value
equal to 1 indicates that the pair is present in the unit. The periodicityAndPattern can be {1, 2, 4, 5, 8, 10, 20
or 40} units long, but maximum of 40ms. The first symbol of periodicityAndPattern every 40ms/P periods is
a first symbol in frame 𝑛𝑓 mod 4 = 0, where P is the duration of periodicityAndPattern in units of ms. When
3GPP
Release 16 33 3GPP TS 38.214 V16.1.0 (2020-03)
periodicityAndPattern is not configured for a pair, for a symbol level bitmap spanning two slots, the bits of
the first and second slots correspond respectively to even and odd slots of a radio frame, and for a symbol
level bitmap spanning one slot, the bits of the slot correspond to every slot of a radio frame. The pair can be
included in one or two groups of resource sets (higher layer parameters rateMatchPatternGroup1and
rateMatchPatternGroup2). The rateMatchPatternToAddModList given by ServingCellConfig or
ServingCellConfigCommon configuration in numerology µ applies only to PDSCH of the same numerology
µ.
- within a BWP, a frequency domain resource of a CORESET configured by ControlResourceSet with

controlResourceSetId or ControlResourceSetZero and time domain resource determined by the higher layer
parameters monitoringSlotPeriodicityAndOffset, duration and monitoringSymbolsWithinSlot of all search-
space-sets configured by SearchSpace and time domain resource of search-space-set zero configured by
searchSpaceZero associated with the CORESET as well as CORESET duration configured by
ControlResourceSet with controlResourceSetId or ControlResourceSetZero. This resource not available for
PDSCH can be included in one or two groups of resource sets (higher layer parameters
rateMatchPatternGroup1 and rateMatchPatternGroup2).
A configured group rateMatchPatternGroup1 or rateMatchPatternGroup2 contains a list of RB and symbol level

resource set indices forming a union of resource-sets not available for PDSCH dynamically if a corresponding bit of the
Rate matching indicator field of DCI format 1_1 scheduling the PDSCH is equal to 1. The REs corresponding to the
union of configured RB-symbol level resource-sets that are not included in either of the two groups are not available for
PDSCH scheduled by DCI format 1_1. When receiving PDSCH scheduled by DCI format 1_0 or PDSCHs with SPS
activated by DCI format 1_0, the REs corresponding to configured resources in rateMatchPatternGroup1 or
rateMatchPatternGroup2 are not available for PDSCH.
For a bitmap pair included in one or two groups of resource sets, the dynamic indication of availability for PDSCH
applies to a set of slot(s) where the rateMatchPatternToAddModList is present among the slots of scheduled PDSCH.
If a UE monitors PDCCH candidates of aggregation levels 8 and 16 with the same starting CCE index in non-
interleaved CORESET spanning one OFDM symbol and if a detected PDCCH scheduling the PDSCH has aggregation
level 8, the resources corresponding to the aggregation level 16 PDCCH candidate are not available for the PDSCH.
If a PDSCH scheduled by a PDCCH would overlap with resources in the CORESET containing the PDCCH, the
resources corresponding to a union of the detected PDCCH that scheduled the PDSCH and associated PDCCH DM-RS
are not available for the PDSCH. When precoderGranularity configured in a CORESET where the PDCCH was
detected is equal to allContiguousRBs, the associated PDCCH DM-RS are DM-RS in all REGs of the CORESET.
Otherwise, the associated DM-RS are the DM-RS in REGs of the PDCCH.
5.1.4.2 PDSCH resource mapping with RE level granularity

The procedures for PDSCH scheduled by PDCCH with DCI format 1_1 described in this clause equally apply to
PDSCH scheduled by PDCCH with DCI format 1_2, by applying the parameters of aperiodic-ZP-CSI-RS-
ResourceSetsToAddModList-ForDCIFormat1_2 instead of aperiodic-ZP-CSI-RS-ResourceSetsToAddModList.
A UE may be configured with any of the following higher layer parameters:
- REs indicated by the RateMatchingPatternLTE-CRS in lte-CRS-ToMatchAround in ServingCellConfig or

ServingCellConfigCommon configuring common RS, in 15 kHz subcarrier spacing applicable only to 15 kHz
subcarrier spacing PDSCH, of one LTE carrier in a serving cell are declared as not available for PDSCH.
- REs indicated by RateMatchingPatternLTE-CRS in lte-CRS-PatternList-r16 in ServingCellConfig configuring

common RS, in 15 kHz subcarrier spacing applicable only to 15 kHz subcarrier spacing PDSCH, of one LTE
carrier in a serving cell are declared as not available for PDSCH.
- Each RateMatchingPatternLTE-CRS configuration contains v-Shift consisting of LTE-CRS-vshift(s), nrofCRS-

Ports consisting of LTE-CRS antenna ports 1, 2 or 4 ports, carrierFreqDL representing the offset in units of 15
kHz subcarriers from (reference) point A to the LTE carrier centre subcarrier location, carrierBandwidthDL
representing the LTE carrier bandwidth, and may also configure mbsfn-SubframeConfigList representing
MBSFN subframe configuration. A UE determines the CRS position within the slot according to Clause 6.10.1.2
in [15, TS 36.211], where slot corresponds to LTE subframe.
- If the UE configured by higher layer parameter PDCCH-Config with two different values of
CORESETPoolIndex in ControlResourceSet and also configured by the higher layer parameter LTE-CRS-
PatternList-r16 in ServingCellConfig, the following REs are declared as not available for PDSCH:
3GPP
Release 16 34 3GPP TS 38.214 V16.1.0 (2020-03)
- REs indicated by CRSPatternList-CORESETPoolIndex for a UE supporting the capability of [separate-lte-

CRS-ToMatchAround];
- REs indicated by CRS-PatternList-r16 in ServingCellConfig for a UE not supporting the capability of

[separate-lte-CRS-ToMatchAround].
- Within a BWP, the UE can be configured with one or more ZP CSI-RS resource set configuration(s) for
aperiodic, semi-persistent and periodic time-domain behaviours (higher layer parameters aperiodic-ZP-CSI-RS-
ResourceSetsToAddModList, sp-ZP-CSI-RS-ResourceSetsToAddModList and p-ZP-CSI-RS-ResourceSet
respectively comprised in PDSCH-Config), with each ZP-CSI-RS resource set consisting of at most 16 ZP CSI-
RS resources (higher layer parameter ZP-CSI-RS-Resource) in numerology of the BWP. The REs indicated by p-
ZP-CSI-RS-ResourceSet are declared as not available for PDSCH. The REs indicated by sp-ZP-CSI-RS-
ResourceSetsToAddModList and aperiodic-ZP-CSI-RS-ResourceSetsToAddModList are declared as not
available for PDSCH when their triggering and activation are applied, respectively. The following parameters
are configured via higher layer signaling for each ZP CSI-RS resource configuration:
- zp-CSI-RS-ResourceId in ZP-CSI-RS-Resource determines ZP CSI-RS resource configuration identity.
- nrofPorts defines the number of CSI-RS ports, where the allowable values are given in Clause 7.4.1.5 of [4,
TS 38.211].
- cdm-Type defines CDM values and pattern, where the allowable values are given in Clause 7.4.1.5 of [4, TS
38.211].
- resourceMapping given by ZP-CSI-RS-Resource defines the OFDM symbol and subcarrier occupancy of the
ZP-CSI-RS resource within a slot that are given in Clause 7.4.1.5 of [4, TS 38.211].
- periodicityAndOffset in ZP-CSI-RS-Resource defines the ZP-CSI-RS periodicity and slot offset for
periodic/semi-persistent ZP-CSI-RS.
The UE may be configured with a DCI field for triggering the aperiodic ZP-CSI-RS. A list of ZP-CSI-RS-
ResourceSet(s), provided by higher layer parameter aperiodic-ZP-CSI-RS-ResourceSetsToAddModList in PDSCH-
Config , is configured for aperiodic triggering. The maximum number of aperiodic ZP-CSI-RS-ResourceSet(s)
configured per BWP is 3. The bit-length of DCI field ZP CSI-RS trigger depends on the number of aperiodic ZP-CSI-
RS-ResourceSet(s)configured (up to 2 bits). Each non-zero codepoint of ZP CSI-RS trigger in DCI format 1_1 triggers
one aperiodic ZP-CSI-RS-ResourceSet in the list aperiodic-ZP-CSI-RS-ResourceSetsToAddModList by indicating the
aperiodic ZP CSI-RS resource set ID. The DCI codepoint '01' triggers the resource set with ZP-CSI-RS-ResourceSetIds
= 1, the DCI codepoint '10' triggers the resource set with ZP-CSI-RS-ResourceSetIds = 2, and the DCI codepoint '11'
triggers the resource set with ZP-CSI-RS-ResourceSetIds = 3. Codepoint '00' is reserved for not triggering aperiodic ZP
CSI-RS. When receiving PDSCH scheduled by DCI format 1_0 or PDSCHs with SPS activated by DCI format 1_0, the
REs corresponding to configured resources in aperiodic-ZP-CSI-RS-ResourceSetsToAddModList are available for
PDSCH.
When the UE is configured with multi-slot and single-slot PDSCH scheduling, the triggered aperiodic ZP CSI-RS is
applied to all the slot(s) of the PDSCH scheduled by the PDCCH containing the trigger.
For a UE configured with a list of ZP-CSI-RS-ResourceSet(s) provided by higher layer parameter sp-ZP-CSI-RS-
ResourceSetsToAddModList:
- when the UE would transmit a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH
carrying the activation command, as described in clause 6.1.3.19 of [10, TS 38.321], for ZP CSI-RS resource(s),
the corresponding action in [10, TS 38.321] and the UE assumption on the PDSCH RE mapping corresponding
to the activated ZP CSI-RS resource(s) shall be applied starting from the first slot that is after slot 𝑛 +
where  is the SCS configuration for the PUCCH.
𝑠𝑢𝑏𝑓𝑟𝑎𝑚𝑒,µ
3𝑁𝑠𝑙𝑜𝑡
- when the UE would transmit a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH
carrying the deactivation command, as described in clause 6.1.3.19 of [10, TS 38.321], for activated ZP CSI-RS
resource(s), the corresponding action in [10, TS 38.321] and the UE assumption on cessation of the PDSCH RE
mapping corresponding to the de-activated ZP CSI-RS resource(s) shall be applied starting from the first slot that
is after slot 𝑛 + 3𝑁𝑠𝑙𝑜𝑡
3GPP
Release 16 35 3GPP TS 38.214 V16.1.0 (2020-03)
5.1.5 Antenna ports quasi co-location

The UE can be configured with a list of up to M TCI-State configurations within the higher layer parameter PDSCH-
Config to decode PDSCH according to a detected PDCCH with DCI intended for the UE and the given serving cell,
where M depends on the UE capability maxNumberConfiguredTCIstatesPerCC. Each TCI-State contains parameters for
configuring a quasi co-location relationship between one or two downlink reference signals and the DM-RS ports of the
PDSCH, the DM-RS port of PDCCH or the CSI-RS port(s) of a CSI-RS resource. The quasi co-location relationship is
configured by the higher layer parameter qcl-Type1 for the first DL RS, and qcl-Type2 for the second DL RS (if
configured). For the case of two DL RSs, the QCL types shall not be the same, regardless of whether the references are
to the same DL RS or different DL RSs. The quasi co-location types corresponding to each DL RS are given by the
higher layer parameter qcl-Type in QCL-Info and may take one of the following values:
- 'QCL-TypeA': {Doppler shift, Doppler spread, average delay, delay spread}
- 'QCL-TypeB': {Doppler shift, Doppler spread}
- 'QCL-TypeC': {Doppler shift, average delay}
- 'QCL-TypeD': {Spatial Rx parameter}
The UE receives an activation command, as described in clause 6.1.3.14 of [10, TS 38.321] or in clause [6.1.3.x] of [10,
TS 38.321], used to map up to 8 TCI states to the codepoints of the DCI field 'Transmission Configuration Indication'
in one CC/DL BWP or in a set of CCs/DL BWPs, respectively. When a set of TCI state IDs are activated for a set of
CCs/DL BWPs, where the applicable list of CCs is determined by indicated CC in the activation command, the same set
of TCI state IDs are applied for all DL BWPs in the indicated CCs.
When a UE supports two TCI states in a codepoint of the DCI field 'Transmission Configuration Indication' the UE
may receive an activation command, as described in clause [6.1.3.X] of [10, TS 38.321], the activation command is
used to map up to 8 combinations of one or two TCI states to the codepoints of the DCI field 'Transmission
Configuration Indication'. The UE is not expected to receive more than 8 TCI states in the activation command.
When the UE would transmit a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH carrying
the activation command, the indicated mapping between TCI states and codepoints of the DCI field 'Transmission
where  is the
Configuration Indication' should be applied starting from the first slot that is after slot 𝑛 + 3𝑁𝑠𝑙𝑜𝑡
SCS configuration for the PUCCH. If tci-PresentInDCI is set to "enabled" or tci-PresentInDCI-ForFormat1_2 is
configured for the CORESET scheduling the PDSCH, and the time offset between the reception of the DL DCI and the
corresponding PDSCH is equal to or greater than timeDurationForQCL if applicable, after a UE receives an initial
higher layer configuration of TCI states and before reception of the activation command, the UE may assume that the
DM-RS ports of PDSCH of a serving cell are quasi co-located with the SS/PBCH block determined in the initial access
procedure with respect to 'QCL-TypeA', and when applicable, also with respect to'QCL-TypeD'.
If a UE is configured with the higher layer parameter tci-PresentInDCI that is set as 'enabled' for the CORESET
scheduling the PDSCH, the UE assumes that the TCI field is present in the DCI format 1_1 of the PDCCH transmitted
on the CORESET. If a UE is configured with the higher layer parameter tci-PresentInDCI-ForFormat1_2 for the
CORESET scheduling the PDSCH, the UE assumes that the TCI field with a DCI field size indicated by tci-
PresentInDCI-ForFormat1_2 is present in the DCI format 1_2 of the PDCCH transmitted on the CORESET. If the
PDSCH is scheduled by a DCI format not having the TCI field present, and the time offset between the reception of the
DL DCI and the corresponding PDSCH is equal to or greater than a threshold timeDurationForQCL if applicable,
where the threshold is based on reported UE capability [13, TS 38.306], for determining PDSCH antenna port quasi co-
location, the UE assumes that the TCI state or the QCL assumption for the PDSCH is identical to the TCI state or QCL
assumption whichever is applied for the CORESET used for the PDCCH transmission.
If the PDSCH is scheduled by a DCI format having the TCI field present, the TCI field in DCI in the scheduling
component carrier points to the activated TCI states in the scheduled component carrier or DL BWP, the UE shall use
the TCI-State according to the value of the 'Transmission Configuration Indication' field in the detected PDCCH with
DCI for determining PDSCH antenna port quasi co-location. The UE may assume that the DM-RS ports of PDSCH of a
serving cell are quasi co-located with the RS(s) in the TCI state with respect to the QCL type parameter(s) given by the
indicated TCI state if the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or
greater than a threshold timeDurationForQCL, where the threshold is based on reported UE capability [13, TS 38.306].
When the UE is configured with a single slot PDSCH, the indicated TCI state should be based on the activated TCI
states in the slot with the scheduled PDSCH. When the UE is configured with a multi-slot PDSCH, the indicated TCI
state should be based on the activated TCI states in the first slot with the scheduled PDSCH, and UE shall expect the
activated TCI states are the same across the slots with the scheduled PDSCH. When the UE is configured with
3GPP
Release 16 36 3GPP TS 38.214 V16.1.0 (2020-03)
CORESET associated with a search space set for cross-carrier scheduling and the UE is not configured with
[enableDefaultBeamForCSS], the UE expects tci-PresentInDCI is set as 'enabled' or tci-PresentInDCI-ForFormat1_2 is
configured for the CORESET, and if one or more of the TCI states configured for the serving cell scheduled by the
search space set contains 'QCL-TypeD', the UE expects the time offset between the reception of the detected PDCCH in
the search space set and the corresponding PDSCH is larger than or equal to the threshold timeDurationForQCL.
Independent of the configuration of tci-PresentInDCI and tci-PresentInDCI-ForFormat1_2 in RRC connected mode, if

no TCI codepoints are mapped to two different TCI states and the offset between the reception of the DL DCI and the
corresponding PDSCH is less than the threshold timeDurationForQCL, the UE may assume that the DM-RS ports of
PDSCH of a serving cell are quasi co-located with the RS(s) with respect to the QCL parameter(s) used for PDCCH
quasi co-location indication of the CORESET associated with a monitored search space with the lowest
controlResourceSetId in the latest slot in which one or more CORESETs within the active BWP of the serving cell are
monitored by the UE. In this case, if the 'QCL-TypeD' of the PDSCH DM-RS is different from that of the PDCCH DM-
RS with which they overlap in at least one symbol, the UE is expected to prioritize the reception of PDCCH associated
with that CORESET. This also applies to the intra-band CA case (when PDSCH and the CORESET are in different
component carriers). If none of configured TCI states for the serving cell of scheduled PDSCH contains 'QCL-TypeD',
the UE shall obtain the other QCL assumptions from the indicated TCI states for its scheduled PDSCH irrespective of
the time offset between the reception of the DL DCI and the corresponding PDSCH. If a UE configured by higher layer
parameter PDCCH-Config that contains two different values of CORESETPoolIndex in ControlResourceSet, for both
cases, when tci-PresentInDCI is set to 'enabled' and tci-PresentInDCI is not configured in RRC connected mode, if the
offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold
timeDurationForQCL, the UE may assume that the DM-RS ports of PDSCH associated with a value of
CORESETPoolIndex of a serving cell are quasi co-located with the RS(s) with respect to the QCL parameter(s) used for
PDCCH quasi co-location indication of the CORESET associated with a monitored search space with the lowest
CORESET-ID among CORESETs, which are configured with the same value of CORESETPoolIndex as the PDCCH
scheduling that PDSCH, in the latest slot in which one or more CORESETs associated with the same value of
CORESETPoolIndex as the PDCCH scheduling that PDSCH within the active BWP of the serving cell are monitored by
the UE. If the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold
timeDurationForQCL and at least one configured TCI states for the serving cell of scheduled PDSCH contains the
'QCL-TypeD', and at least one TCI codepoint indicates two TCI states, the UE may assume that the DM-RS ports of
PDSCH of a serving cell are quasi co-located with the RS(s) with respect to the QCL parameter(s) associated with the
TCI states corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states.
If the PDCCH carrying the scheduling DCI is received on one component carrier, and the PDSCH scheduled by that
DCI is on another component carrier and the UE is configured with [enabledDefaultBeamForCCS]:
- The timeDurationForQCL is determined based on the subcarrier spacing of the scheduled PDSCH. If µPDCCH <
2𝜇𝑃𝐷𝑆𝐶𝐻
µPDSCH an additional timing delay 𝑑 𝜇𝑃𝐷𝐶𝐶𝐻 is added to the timeDurationForQCL, where d is defined in
2
5.2.1.5.1a-1;
- For both the cases, when the offset between the reception of the DL DCI and the corresponding PDSCH is less
than the threshold timeDurationForQCL, and when the DL DCI does not have the TCI field present, the UE
obtains its QCL assumption for the scheduled PDSCH from the activated TCI state with the lowest ID applicable
to PDSCH in the active BWP of the scheduled cell.
For a periodic CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info, the UE
shall expect that a TCI-State indicates one of the following quasi co-location type(s):
- 'QCL-TypeC' with an SS/PBCH block and, when applicable, 'QCL-TypeD' with the same SS/PBCH block, or
- 'QCL-TypeC' with an SS/PBCH block and, when applicable,'QCL-TypeD' with a CSI-RS resource in an NZP-
CSI-RS-ResourceSet configured with higher layer parameter repetition, or
For an aperiodic CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-Info, the
UE shall expect that a TCI-State indicates 'QCL-TypeA' with a periodic CSI-RS resource in a NZP-CSI-RS-ResourceSet
configured with higher layer parameter trs-Info and, when applicable,'QCL-TypeD' with the same periodic CSI-RS
resource.
For a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured without higher layer parameter trs-Info and without
the higher layer parameter repetition, the UE shall expect that a TCI-State indicates one of the following quasi co-
location type(s):
3GPP
Release 16 37 3GPP TS 38.214 V16.1.0 (2020-03)
- 'QCL-TypeA' with a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-
Info and, when applicable, 'QCL-TypeD' with the same CSI-RS resource, or
Info and, when applicable, 'QCL-TypeD' with an SS/PBCH block , or
Info and, when applicable, 'QCL-TypeD' with a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with
higher layer parameter repetition, or
- 'QCL-TypeB' with a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with higher layer parameter trs-
Info when 'QCL-TypeD' is not applicable.
For a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with higher layer parameter repetition, the UE shall
expect that a TCI-State indicates one of the following quasi co-location type(s):
Info and, when applicable, 'QCL-TypeD' with a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured with
higher layer parameter repetition, or
- 'QCL-TypeC' with an SS/PBCH block and, when applicable, 'QCL-TypeD' with the same SS/PBCH block.
For the DM-RS of PDCCH, the UE shall expect that a TCI-State indicates one of the following quasi co-location
type(s):
Info and, when applicable, 'QCL-TypeD' with a CSI-RS resource in an NZP-CSI-RS-ResourceSet configured
with higher layer parameter repetition, or
- 'QCL-TypeA' with a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured without higher layer parameter
trs-Info and without higher layer parameter repetition and, when applicable, 'QCL-TypeD' with the same CSI-RS
resource.
For the DM-RS of PDSCH, the UE shall expect that a TCI-State indicates one of the following quasi co-location
type(s):
Info and, when applicable, 'QCL-TypeD' with a CSI-RS resource in an NZP-CSI-RS-ResourceSet configured
with higher layer parameter repetition,or
- QCL-TypeA' with a CSI-RS resource in a NZP-CSI-RS-ResourceSet configured without higher layer parameter
trs-Info and without higher layer parameter repetition and, when applicable, 'QCL-TypeD' with the same CSI-RS
resource.
5.1.6 UE procedure for receiving reference signals

5.1.6.1 CSI-RS reception procedure
The CSI-RS defined in Clause 7.4.1.5 of [4, TS 38.211], may be used for time/frequency tracking, CSI computation,
L1-RSRP computation and mobility.
For a CSI-RS resource associated with a NZP-CSI-RS-ResourceSet with the higher layer parameter repetition set to 'on',
the UE shall not expect to be configured with CSI-RS over the symbols during which the UE is also configured to
monitor the CORESET, while for other NZP-CSI-RS-ResourceSet configurations, if the UE is configured with a CSI-RS
resource and a search space set associated with a CORESET in the same OFDM symbol(s), the UE may assume that the
CSI-RS and a PDCCH DM-RS transmitted in all the search space sets associated with CORESET are quasi co-located
3GPP
Release 16 38 3GPP TS 38.214 V16.1.0 (2020-03)
with 'QCL-TypeD', if 'QCL-TypeD' is applicable. This also applies to the case when CSI-RS and the CORESET are in
different intra-band component carriers, if 'QCL-TypeD' is applicable. Furthermore, the UE shall not expect to be
configured with the CSI-RS in PRBs that overlap those of the CORESET in the OFDM symbols occupied by the search
space set(s).
The UE is not expected to receive CSI-RS and SIB1 message in the overlapping PRBs in the OFDM symbols where
SIB1 is transmitted.
If the UE is configured with DRX,
- if the UE is configured to monitor DCI format 2_6 and configured by higher layer parameter [PS-
Periodic_CSI_TransmitOrNot] to report CSI with the higher layer parameter reportConfigType set to 'periodic'
when drx-onDurationTimer is not started, the most recent CSI measurement occasion occurs in DRX active time
or during the time duration indicated by drx-onDurationTimer also outside DRX active time for CSI to be
reported;
- if the UE is configured to monitor DCI format 2_6 and configured by higher layer parameter[PS_Periodic_L1-
RSRP_TransmitOrNot] to report L1-RSRP with the higher layer parameter reportConfigType set to 'periodic'
and reportQuantity set to cri-RSRP when drx-onDurationTimer is not started, the most recent CSI measurement
occasion occurs in DRX active time or during the time duration indicated by drx-onDurationTimer also outside
DRX active time for CSI to be reported;
- otherwise, the most recent CSI measurement occasion occurs in DRX active time for CSI to be reported.
5.1.6.1.1 CSI-RS for tracking

A UE in RRC connected mode is expected to receive the higher layer UE specific configuration of a NZP-CSI-RS-
ResourceSet configured with higher layer parameter trs-Info.
For a NZP-CSI-RS-ResourceSet configured with the higher layer parameter trs-Info, the UE shall assume the antenna
port with the same port index of the configured NZP CSI-RS resources in the NZP-CSI-RS-ResourceSet is the same.
- For frequency range 1, the UE may be configured with one or more NZP CSI-RS set(s), where a NZP-CSI-RS-
ResourceSet consists of four periodic NZP CSI-RS resources in two consecutive slots with two periodic NZP
CSI-RS resources in each slot. If no two consecutive slots are indicated as downlink slots by tdd-UL-DL-
ConfigurationCommon or tdd-UL-DL-ConfigDedicated, then the UE may be configured with one or more NZP
CSI-RS set(s), where a NZP-CSI-RS-ResourceSet consists of two periodic NZP CSI-RS resources in one slot.
- For frequency range 2 the UE may be configured with one or more NZP CSI-RS set(s), where a NZP-CSI-RS-
ResourceSet consists of two periodic CSI-RS resources in one slot or with a NZP-CSI-RS-ResourceSet of four
periodic NZP CSI-RS resources in two consecutive slots with two periodic NZP CSI-RS resources in each slot.
A UE configured with NZP-CSI-RS-ResourceSet(s) configured with higher layer parameter trs-Info may have the CSI-
RS resources configured as:
- Periodic, with the CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with same periodicity,
bandwidth and subcarrier location
- Periodic CSI-RS resource in one set and aperiodic CSI-RS resources in a second set, with the aperiodic CSI-RS
and periodic CSI-RS resource having the same bandwidth (with same RB location) and the aperiodic CSI-RS
being 'QCL-Type-A' and 'QCL-TypeD', where applicable, with the periodic CSI-RS resources. For frequency
range 2, the UE does not expect that the scheduling offset between the last symbol of the PDCCH carrying the
triggering DCI and the first symbol of the aperiodic CSI-RS resources is smaller than the UE reported
ThresholdSched-Offset. The UE shall expect that the periodic CSI-RS resource set and aperiodic CSI-RS
resource set are configured with the same number of CSI-RS resources and with the same number of CSI-RS
resources in a slot. For the aperiodic CSI-RS resource set if triggered, and if the associated periodic CSI-RS
resource set is configured with four periodic CSI-RS resources with two consecutive slots with two periodic
CSI-RS resources in each slot, the higher layer parameter aperiodicTriggeringOffset indicates the triggering
offset for the first slot for the first two CSI-RS resources in the set.
A UE does not expect to be configured with a CSI-ReportConfig that is linked to a CSI-ResourceConfig containing an
NZP-CSI-RS-ResourceSet configured with trs-Info and with the CSI-ReportConfig configured with the higher layer
parameter timeRestrictionForChannelMeasurements set to 'configured'.
3GPP
Release 16 39 3GPP TS 38.214 V16.1.0 (2020-03)
A UE does not expect to be configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to
other than 'none' for aperiodic NZP CSI-RS resource set configured with trs-Info.
A UE does not expect to be configured with a CSI-ReportConfig for periodic NZP CSI-RS resource set configured with
trs-Info.
A UE does not expect to be configured with a NZP-CSI-RS-ResourceSet configured both with trs-Info and repetition.
Each CSI-RS resource, defined in Clause 7.4.1.5.3 of [4, TS 38.211], is configured by the higher layer parameter NZP-
CSI-RS-Resource with the following restrictions:
- the time-domain locations of the two CSI-RS resources in a slot, or of the four CSI-RS resources in two
consecutive slots (which are the same across two consecutive slots), as defined by higher layer parameter CSI-
RS-resourceMapping, is given by one of
- l  4,8 , l  5,9 , or l  6,10 for frequency range 1 and frequency range 2,
- l  0,4 , l  1,5 , l  2,6 , l  3,7 , l  7,11 , l  8,12 or l  9,13 for frequency range 2.
- a single port CSI-RS resource with density  = 3 given by Table 7.4.1.5.3-1 from [4, TS 38.211] and higher
layer parameter density configured by CSI-RS-ResourceMapping.
- the bandwidth of the CSI-RS resource, as given by the higher layer parameter freqBand configured by CSI-RS-
size size
ResourceMapping, is the minimum of 52 and NBWP,i resource blocks, or is equal to NBWP,i resource blocks. For
operation with shared spectrum channel access, freqBand configured by CSI-RS-ResourceMapping, is the
size size
minimum of 48 and NBWP,i resource blocks, or is equal to NBWP,i resource blocks.
- the UE is not expected to be configured with the periodicity of 2   10 slots if the bandwidth of CSI-RS
resource is larger than 52 resource blocks.
- the periodicity and slot offset for periodic NZP CSI-RS resources, as given by the higher layer parameter

periodicityAndOffset configured by NZP-CSI-RS-Resource, is one of 2 X p slots where X p = 10, 20, 40, or 80
and where µ is defined in Clause 4.3 of [4, TS 38.211].
- same powerControlOffset and powerControlOffsetSS given by NZP-CSI-RS-Resource value across all resources.
5.1.6.1.2 CSI-RS for L1-RSRP and L1-SINR computation

If a UE is configured with a NZP-CSI-RS-ResourceSet configured with the higher layer parameter repetition set to 'on',
the UE may assume that the CSI-RS resources, described in Clause 5.2.2.3.1, within the NZP-CSI-RS-ResourceSet are
transmitted with the same downlink spatial domain transmission filter, where the CSI-RS resources in the NZP-CSI-RS-
ResourceSet are transmitted in different OFDM symbols. If repetition is set to 'off', the UE shall not assume that the
CSI-RS resources within the NZP-CSI-RS-ResourceSet are transmitted with the same downlink spatial domain
transmission filter.
If the UE is configured with a CSI-ReportConfig with reportQuantity set to "cri-RSRP", "cri-SINR" or "none" and if the
CSI-ResourceConfig for channel measurement (higher layer parameter resourcesForChannelMeasurement) contains a
NZP-CSI-RS-ResourceSet that is configured with the higher layer parameter repetition and without the higher layer
parameter trs-Info, the UE can only be configured with the same number (1 or 2) of ports with the higher layer
parameter nrofPorts for all CSI-RS resources within the set. If the UE is configured with the CSI-RS resource in the
same OFDM symbol(s) as an SS/PBCH block, the UE may assume that the CSI-RS and the SS/PBCH block are quasi
co-located with 'QCL-TypeD' if 'QCL-TypeD' is applicable. Furthermore, the UE shall not expect to be configured with
the CSI-RS in PRBs that overlap with those of the SS/PBCH block, and the UE shall expect that the same subcarrier
spacing is used for both the CSI-RS and the SS/PBCH block.
5.1.6.1.3 CSI-RS for mobility

If a UE is configured with the higher layer parameter CSI-RS-Resource-Mobility and the higher layer parameter
associatedSSB is not configured, the UE shall perform measurements based on CSI-RS-Resource-Mobility and the UE
may base the timing of the CSI-RS resource on the timing of the serving cell.
If a UE is configured with the higher layer parameters CSI-RS-Resource-Mobility and associatedSSB, the UE may base
the timing of the CSI-RS resource on the timing of the cell given by the cellId of the CSI-RS resource configuration.
3GPP
Release 16 40 3GPP TS 38.214 V16.1.0 (2020-03)
Additionally, for a given CSI-RS resource, if the associated SS/PBCH block is configured but not detected by the UE,
the UE is not required to monitor the corresponding CSI-RS resource. The higher layer parameter isQuasiColocated
indicates whether the associated SS/PBCH block given by the associatedSSB and the CSI-RS resource(s) are quasi co-
located with respect to ['QCL-TypeD'].
If a UE is configured with the higher layer parameter CSI-RS-Resource-Mobility and with periodicity greater than 10 ms
in paired spectrum, the UE may assume the absolute value of the time difference between radio frame i between any
two cells, listed in the configuration with the higher layer parameter CSI-RS-CellMobility and with same refFreqCSI-
RS, is less than 153600 Ts.
If the UE is configured with DRX, the UE is not required to perform measurement of CSI-RS resources other than
during the active time for measurements based on CSI-RS-Resource-Mobility. When the UE is configured to monitor
DCI format 2_6, the UE is not required to perform measurements other than during the active time and during the timer
duration indicated by drx-onDurationTimer based on CSI-RS-Resource-Mobility.
If the UE is configured with DRX and DRX cycle in use is larger than 80 ms, the UE may not expect CSI-RS resources
are available other than during the active time for measurements based on CSI-RS-Resource-Mobility. If the UE is
configured with DRX and configured to monitor DCI format 2_6 and DRX cycle in use is larger than 80ms, the UE
may not expect that the CSI-RS resources are available other than during the active time and during the time duration
indicated by drx-onDurationTimer for measurements based on CSI-RS-Resource-Mobility. Otherwise, the UE may
assume CSI-RS are available for measurements based on CSI-RS-Resource-Mobility.
A UE configured with the higher layer parameters CSI-RS-Resource-Mobility may expect to be configured
- with no more than 96 CSI-RS resources per higher layer parameter MeasObjectNR when all CSI-RS resources
configured by the same higher layer parameter MeasObjectNR have been configured with associatedSSB, or,
- with no more than 64 CSI-RS resources per higher layer parameter MeasObjectNR when all CSI-RS resources
have been configured without associatedSSB or when only some of the CSI-RS resources have been configured
with associatedSSB by the same higher layer parameter MeasObjectNR
- For frequency range 1 the associatedSSB is optionally present for each CSI-RS resource
- For frequency range 2 the associatedSSB is either present for all configured CSI-RS resources or not present
for any configured CSI-RS resource per higher layer parameter MeasObjectNR.
For any CSI-RS resource configuration, the UE shall assume that the value for parameter cdm-Type is 'noCDM', and
there is only one antenna port.
5.1.6.2 DM-RS reception procedure

The DM-RS reception procedures for PDSCH scheduled by PDCCH with DCI format 1_1 described in this clause
equally apply to PDSCH scheduled by PDCCH with DCI format 1_2, by applying the parameters of dmrs-
DownlinkForPDSCH-MappingTypeA-ForDCIFormat1_2 and dmrs-DownlinkForPDSCH-MappingTypeB-
ForDCIFormat1_2 instead of dmrs-DownlinkForPDSCH-MappingTypeA and dmrs-DownlinkForPDSCH-
MappingTypeB.
When receiving PDSCH scheduled by DCI format 1_0 or receiving PDSCH before dedicated higher layer configuration
of any of the parameters dmrs-AdditionalPosition, maxLength and dmrs-Type, the UE shall assume that the PDSCH is
not present in any symbol carrying DM-RS except for PDSCH with allocation duration of 2 symbols with PDSCH
mapping type B (described in clause 7.4.1.1.2 of [4, TS 38.211]), and a single symbol front-loaded DM-RS of
configuration type 1 on DM-RS port 1000 is transmitted, and that all the remaining orthogonal antenna ports are not
associated with transmission of PDSCH to another UE and in addition
- For PDSCH with mapping type A, the UE shall assume dmrs-AdditionalPosition='pos2' and up to two additional
single-symbol DM-RS present in a slot according to the PDSCH duration indicated in the DCI as defined in
Clause 7.4.1.1 of [4, TS 38.211], and
- For PDSCH with allocation duration of 7 symbols for normal CP or 6 symbols for extended CP with mapping
type B, the UE shall assume one additional single-symbol DM-RS present in the 5th or 6th symbol when the
front-loaded DM-RS symbol is in the 1st or 2nd symbol respectively of the PDSCH allocation duration, otherwise
the UE shall assume that the additional DM-RS symbol is not present, and
3GPP
Release 16 41 3GPP TS 38.214 V16.1.0 (2020-03)
- For PDSCH with allocation duration of 4 symbols with mapping type B, the UE shall assume that no additional
DM-RS are present, and
- For PDSCH with allocation duration of 2 symbols with mapping type B, the UE shall assume that no additional
DM-RS are present, and the UE shall assume that the PDSCH is present in the symbol carrying DM-RS.
When receiving PDSCH scheduled by DCI format 1_1 by PDCCH with CRC scrambled by C-RNTI, MCS-C-RNTI, or
CS-RNTI,
- the UE may be configured with the higher layer parameter dmrs-Type, and the configured DM-RS configuration
type is used for receiving PDSCH in as defined in Clause 7.4.1.1 of [4, TS 38.211].
- the UE may be configured with the maximum number of front-loaded DM-RS symbols for PDSCH by higher
layer parameter maxLength given by DMRS-DownlinkConfig..
- if maxLength is set to 'len1', single-symbol DM-RS can be scheduled for the UE by DCI, and the UE can be
configured with a number of additional DM-RS for PDSCH by higher layer parameter dmrs-
AdditionalPosition, which can be set to 'pos0', 'pos1', 'pos2' or 'pos3'.
- if maxLength is set to 'len2', both single-symbol DM-RS and double symbol DM-RS can be scheduled for the
UE by DCI, and the UE can be configured with a number of additional DM-RS for PDSCH by higher layer
parameter dmrs-AdditionalPosition, which can be set to 'pos0' or 'pos1'.
- and the UE shall assume to receive additional DM-RS as specified in Table 7.4.1.1.2-3 and Table 7.4.1.1.2-4
as described in Clause 7.4.1.1.2 of [4, TS 38.211].
For the UE-specific reference signals generation as defined in Clause 7.4.1.1 of [4, TS 38.211], a UE can be configured
𝐷𝑀𝑅𝑆,𝑖
by higher layers with one or two scrambling identity(s), 𝑛𝐼𝐷 i = 0,1 which are the same for both PDSCH mapping
Type A and Type B.
A UE may be scheduled with a number of DM-RS ports by the antenna port index in DCI format 1_1 as described in
Clause 7.3.1.2 of [5, TS 38.212].
For DM-RS configuration type 1,
- if a UE is scheduled with one codeword and assigned with the antenna port mapping with indices of {2, 9, 10, 11
or 30} in Table 7.3.1.2.2-1 and Table 7.3.1.2.2-2 of Clause 7.3.1.2 of [5, TS 38.212], or
- if a UE is scheduled with two codewords,
the UE may assume that all the remaining orthogonal antenna ports are not associated with transmission of PDSCH to
another UE.
For DM-RS configuration type 2,
- if a UE is scheduled with one codeword and assigned with the antenna port mapping with indices of {2, 10 or
23} in Table 7.3.1.2.2-3 and Table 7.3.1.2.2-4 of Clause 7.3.1.2 of [5, TS38.212], or
- if a UE is scheduled with two codewords,
the UE may assume that all the remaining orthogonal antenna ports are not associated with transmission of PDSCH to
another UE.
If a UE receiving PDSCH is configured with the higher layer parameter phaseTrackingRS in DMRS-DownlinkConfig,
the UE may assume that the following configurations are not occurring simultaneously for the received PDSCH:
- any DM-RS ports among 1004-1007 or 1006-1011 for DM-RS configurations type 1 and type 2, respectively are
scheduled for the UE and the other UE(s) sharing the DM-RS REs on the same CDM group(s), and
- PT-RS is transmitted to the UE.
The UE is not expected to simultaneously be configured with the maximum number of front-loaded DM-RS symbols
for PDSCH by higher layer parameter maxLength being set equal to 'len2' and more than one additional DM-RS symbol
as given by the higher layer parameter dmrs-AdditionalPosition.
3GPP
Release 16 42 3GPP TS 38.214 V16.1.0 (2020-03)
The UE is not expected to assume co-scheduled UE(s) with different DM-RS configuration with respect to the actual
number of front-loaded DM-RS symbol(s), the actual number of additional DM-RS, the DM-RS symbol location, and
DM-RS configuration type as described in Clause 7.4.1.1 of [4, TS 38.211].
The UE does not expect the precoding of the potential co-scheduled UE(s) in other DM-RS ports of the same CDM
group to be different in the PRG-level grid configured to this UE with PRG =2 or 4.
The UE does not expect the resource allocation of the potential co-scheduled UE(s) in other DM-RS ports of the same
CDM group to be misaligned in the PRG-level grid to this UE with PRG=2 or 4.
When receiving PDSCH scheduled by DCI format 1_1, the UE shall assume that the CDM groups indicated in the
configured index from Tables 7.3.1.2.2-1, 7.3.1.2.2-2, 7.3.1.2.2-3, 7.3.1.2.2-4 of [5, TS. 38.212] contain potential co-
scheduled downlink DM-RS and are not used for data transmission, where "1", "2" and "3" for the number of DM-RS
CDM group(s) in Tables 7.3.1.2.2-1, 7.3.1.2.2-2, 7.3.1.2.2-3, 7.3.1.2.2-4 of [5, TS. 38.212] correspond to CDM group 0,
{0,1}, {0,1,2}, respectively.
When receiving PDSCH scheduled by DCI format 1_0, the UE shall assume the number of DM-RS CDM groups
without data is 1 which corresponds to CDM group 0 for the case of PDSCH with allocation duration of 2 symbols, and
the UE shall assume that the number of DM-RS CDM groups without data is 2 which corresponds to CDM group {0,1}
for all other cases.
The UE is not expected to receive PDSCH scheduling DCI which indicates CDM group(s) with potential DM-RS ports
which overlap with any configured CSI-RS resource(s) for that UE.
If the UE receives the DM-RS for PDSCH and an SS/PBCH block in the same OFDM symbol(s), then the UE may
assume that the DM-RS and SS/PBCH block are quasi co-located with 'QCL-TypeD', if 'QCL-TypeD' is applicable.
Furthermore, the UE shall not expect to receive DM-RS in resource elements that overlap with those of the SS/PBCH
block, and the UE can expect that the same or different subcarrier spacing is configured for the DM-RS and SS/PBCH
block in a CC except for the case of 240 kHz where only different subcarrier spacing is supported.
If a UE is configured by the higher layer parameter PDCCH-Config that contains two different values of
CORESETPoolIndex in ControlResourceSet, the UE may be scheduled with fully or partially overlapping PDSCHs in
the time and frequency domain by multiple PDCCHs with the following restrictions,
- the UE is not expected to assume different DM-RS configuration with respect to the actual number of front-
loaded DM-RS symbol(s), the actual number of additional DM-RS symbol(s), the actual DM-RS symbol
location, and DM-RS configuration type.
- the UE is not expected to assume DM-RS ports in a CDM group indicated by two TCI states.
TimeDomainAllocationList which contain RepNumR16 in PDSCH-TimeDomainResourceAllocation and it is indicated
with two TCI states in a codepoint of the DCI field 'Transmission Configuration Indication' and DM-RS port(s) within
two CDM group in the DCI field "Antenna Port(s)",
- the first TCI state corresponds to the CDM group of the first antenna port indicated by the antenna port
indication table, and the second TCI state corresponds to the other CDM group.
5.1.6.3 PT-RS reception procedure

A UE shall report the preferred MCS and bandwidth thresholds based on the UE capability at a given carrier frequency,
for each subcarrier spacing applicable to data channel at this carrier frequency, assuming the MCS table with the
maximum Modulation Order as it reported to support.
If a UE is configured with the higher layer parameter phaseTrackingRS in DMRS-DownlinkConfig,
- the higher layer parameters timeDensity and frequencyDensity in PTRS-DownlinkConfig indicate the threshold
values ptrs-MCSi, i=1,2,3 and NRB,i , i=0,1, as shown in Table 5.1.6.3-1 and Table 5.1.6.3-2, respectively.
- if either or both of the additional higher layer parameters timeDensity and frequencyDensity are configured, and
the RNTI equals MCS-C-RNTI, C-RNTI or CS-RNTI, the UE shall assume the PT-RS antenna port' presence
and pattern is a function of the corresponding scheduled MCS of the corresponding codeword and scheduled
bandwidth in corresponding bandwidth part as shown in Table 5.1.6.3-1 and Table 5.1.6.3-2,
- if the higher layer parameter timeDensity given by PTRS-DownlinkConfig is not configured, the UE shall
assume LPT-RS = 1.
3GPP
Release 16 43 3GPP TS 38.214 V16.1.0 (2020-03)
- if the higher layer parameter frequencyDensity given by PTRS-DownlinkConfig is not configured, the UE
shall assume KPT-RS = 2.
- otherwise, if neither of the additional higher layer parameters timeDensity and frequencyDensity are configured
and the RNTI equals MCS-C-RNTI, C-RNTI or CS-RNTI, the UE shall assume the PT-RS is present with LPT-RS
= 1, KPT-RS = 2, and the UE shall assume PT-RS is not present when
- the scheduled MCS from Table 5.1.3.1-1 is smaller than 10, or
- the number of scheduled RBs is smaller than 3, or
- otherwise, if the RNTI equals RA-RNTI, [MsgB-RNTI], SI-RNTI, or P-RNTI, the UE shall assume PT-RS is not
present
Table 5.1.6.3-1: Time density of PT-RS as a function of scheduled MCS
Scheduled MCS Time density ( L PT − RS )
IMCS < ptrs-MCS1 PT-RS is not present

ptrs-MCS1  IMCS < ptrs-MCS2 4
Table 5.1.6.3-2: Frequency density of PT-RS as a function of scheduled bandwidth
Scheduled bandwidth Frequency density ( K PT − RS )

NRB < NRB0 PT-RS is not present
NRB0  NRB < NRB1 2
NRB1  NRB 4
If a UE is not configured with the higher layer parameter phaseTrackingRS in DMRS-DownlinkConfig, the UE assumes
PT-RS is not present.
The higher layer parameter PTRS-DownlinkConfig provides the parameters ptrs-MCSi, i=1,2,3 and with values in range
0-29 when MCS Table 5.1.3.1-1 or MCS Table 5.1.3.1-3 is used and 0-28 when MCS Table 5.1.3.1-2 is used,
respectively. ptrs-MCS4 is not explicitly configured by higher layers but assumed 29 when MCS Table 5.1.3.1-1 or
MCS Table 5.1.3.1-3 is used and 28 when MCS Table 5.1.3.1-2 is used, respectively. The higher layer parameter
frequencyDensity in PTRS-DownlinkConfig provides the parameters NRBi i=0,1 with values in range 1-276.
If the higher layer parameter PTRS-DownlinkConfig indicates that the time density thresholds ptrs-MCSi = ptrs-MCSi+1,
then the time density LPT-RS of the associated row where both these thresholds appear in Table 5.1.6.3-1 is disabled. If
the higher layer parameter PTRS-DownlinkConfig indicates that the frequency density thresholds NRBi = NRBi +1, then the
frequency density KPTRS of the associated row where both these thresholds appear in Table 5.1.6.3-2 is disabled.
If either or both of the parameters PT-RS time density (LPT-RS) and PT-RS frequency density (KPT-RS), shown in Table
5.1.6.3-1 and Table 5.1.6.3-2, indicates that 'PT-RS not present', the UE shall assume that PT-RS is not present.
When the UE is receiving a PDSCH with allocation duration of 2 symbols as defined in Clause 7.4.1.1.2 of [4, TS
38.211] and if LPT-RS is set to 2 or 4, the UE shall assume PT-RS is not transmitted.
When the UE is receiving a PDSCH with allocation duration of 4 symbols and if LPT-RS is set to 4, the UE shall assume
PT-RS is not transmitted.
When a UE is receiving PDSCH for retransmission, if the UE is scheduled with an MCS index greater than V, where
V=28 for MCS Table 5.1.3.1-1 and Table 5.1.3.1-3, and V=27 for MCS Table 5.1.3.1-2 respectively, the MCS for the
3GPP
Release 16 44 3GPP TS 38.214 V16.1.0 (2020-03)
PT-RS time-density determination is obtained from the DCI received for the same transport block in the initial
transmission, which is smaller than or equal to V.
The DL DM-RS port(s) associated with a PT-RS port are assumed to be quasi co-located with respect to {'QCL-TypeA'
and 'QCL-TypeD'}.If a UE is scheduled with one codeword, the PT-RS antenna port is associated with the lowest
indexed DM-RS antenna port among the DM-RS antenna ports assigned for the PDSCH.
If a UE is scheduled with two codewords, the PT-RS antenna port is associated with the lowest indexed DM-RS
antenna port among the DM-RS antenna ports assigned for the codeword with the higher MCS. If the MCS indices of
the two codewords are the same, the PT-RS antenna port is associated with the lowest indexed DM-RS antenna port
assigned for codeword 0.
TimeDomainAllocationList which contain RepNumR16 in PDSCH-TimeDomainResourceAllocation, and if the UE is
configured with the higher layer parameter maxNrofPorts equal to n2, and if the UE is indicated with two TCI states by
the codepoints of the DCI field 'Transmission Configuration Indication' and DM-RS port(s) within two CDM group in
the DCI field "Antenna Port(s)", the UE shall receive two PT-RS ports which are associated to the lowest indexed DM-
RS port among the DM-RS ports corresponding to the first/second indicated TCI state, respectively.
When a UE configured by the higher layer parameter RepSchemeEnabler set to 'FDMSchemeA' or 'FDMSchemeB', and
the UE is indicated with two TCI states in a codepoint of the DCI field 'Transmission Configuration Indication and
DM-RS port(s) within one CDM group in the DCI field "Antenna Port(s)", the UE shall receive a single PT-RS port
which is associated with the lowest indexed DM-RS antenna port among the DM-RS antenna ports assigned for the
PDSCH, a PT-RS frequency density is determined by the number of PRBs associated to each TCI state, and a PT-RS
resource element mapping is associated to the allocated PRBs for each TCI state.
5.1.6.4 SRS reception procedure for CLI

The SRS resources defined in Clause 6.4.1.4 of [4, TS 38.211] may be configured for SRS-RSRP measurement for CLI,
as defined in Clause 5.1.19 of [7, TS 38.215]. The UE is not expected to measure SRS-RSRP with a subcarrier spacing
other than the one configured for the active BWP confining the SRS resource. The UE is not expected to measure more
than 32 SRS resources, and the UE is not expected to receive more than 8 SRS resources in a slot.
5.1.6.5 PRS reception procedure

The UE can be configured with one or more DL PRS resource set configuration(s) as indicated by the higher layer
parameters DL-PRS-ResourceSet and DL-PRS-Resource. Each DL PRS resource set consists of K≥1 DL PRS
resource(s) where each has an associated spatial transmission filter. The UE can be configured with one or more DL
PRS Positioning Frequency Layer configuration(s) as indicated by the higher layer parameter DL-PRS-
PositioningFrequencyLayer. A DL PRS Positioning Frequency Layer is defined as a collection of DL PRS Resource
Sets which have common parameters configured by DL-PRS-PositioningFrequencyLayer.
The UE assumes that the following parameters for each DL PRS resource(s) are configured via higher layer parameters
DL-PRS-PositioningFrequencyLayer, DL-PRS-ResourceSet and DL-PRS-Resource.
A positioning frequency layer consists of one or more PRS resource sets and it is defined by:
- DL-PRS-SubcarrierSpacing defines the subcarrier spacing for the DL PRS resource. All DL PRS Resources and
DL PRS Resource sets in the same DL-PRS-PositioningFrequencyLayer have the same value of DL-PRS-
SubcarrierSpacing. The supported values of DL-PRS-SubcarrierSpacing are given in Table 4.2-1 of [4,
TS38.211].
- DL-PRS-CyclicPrefix defines the cyclic prefix for the DL PRS resource. All DL PRS Resources and DL PRS
Resource sets in the same DL-PRS-PositioningFrequencyLayer have the same value of DL-PRS-CyclicPrefix.
The supported values of DL-PRS-CyclicPrefix are given in Table 4.2-1 of [4, TS38.211].
- DL-PRS-PointA defines the absolute frequency of the reference resource block. Its lowest subcarrier is also
known as Point A. All DL PRS resources belonging to the same DL PRS Resource Set have common Point A
and all DL PRS Resources sets belonging to the same DL-PRS-PositioningFrequencyLayer have a common
Point A.
The UE expects that it will be configured with [IDs] each of which is defined such that it is associated with multiple DL
PRS Resource Sets from the same cell. The UE expects that one of these [IDs] along with a DL-PRS-ResourceSetId and
a DL-PRS-ResourceId can be used to uniquely identify a DL PRS Resource.
3GPP
Release 16 45 3GPP TS 38.214 V16.1.0 (2020-03)
A DL PRS resource set consists of one or more DL PRS resources and it is defined by:
- DL-PRS-ResourceSetId defines the identity of the DL PRS resource set configuration.
- DL-PRS-Periodicity defines the DL PRS resource periodicity and takes values 𝑇PRS
per ∈
2𝜇 {4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240} slots, where 𝜇 = 0, 1, 2, 3 for
DL-PRS-SubcarrierSpacing=15, 30, 60 and 120kHz respectively. All the DL PRS resources within one DL PRS
resource set are configured with the same DL PRS periodicity.
- DL-PRS-ResourceRepetitionFactor defines how many times each DL-PRS resource is repeated for a single
PRS
instance of the DL-PRS resource set and takes values 𝑇rep ∈ {1,2,4,6,8,16,32},. All the DL PRS resources
within one resource set have the same ResourceRepetitionFactor
- DL-PRS-ResourceTimeGap defines the offset in number of slots between two repeated instances of a DL PRS
resource with the same DL-PRS-ResourceID within a single instance of the DL PRS resource set and takes
PRS
values 𝑇gap ∈ {1,2,4,8,16,32}. The UE only expects to be configured with DL-PRS-ResourceTimeGap if DL-
PRS-ResourceRepetitionFactor is configured with value greater than 1. The time duration spanned by one
instance of a DL-PRS-ResourceSet is not expected to exceed the configured value of DL-PRS-Periodicity. All
the DL PRS resources within one resource set have the same DL-PRS-ResourceTimeGap.
- DL-PRS-MutingPattern defines a bitmap of the time locations where the DL PRS resource is expected to not be
transmitted for a DL PRS resource set. The bitmap size can be {2, 4, 6, 8, 16, 32} bits long. The bitmap has two
options for applicability. In the first option each bit in the bitmap corresponds to a configurable number provided
by higher layer parameter DL-PRS.MutingBitRepetitionFactor of consecutive instances of a DL-PRS-
ResourceSet where all the DL-PRS-Resources within the set are muted for the instance that is indicated to be
muted. In the second option each bit in the bitmap corresponds to a single repetition index for each of the DL-
PRS-Resources within each instance of a DL-PRS-ResourceSet and the length of the bitmap is equal to DL-PRS-
ResourceRepetitionFactor. Both options may be configured at the same time in which case the logical AND
operation is applied to the bit maps as described in clause 7.4.1.7.4 of [4, TS 38.211].
- DL-PRS-SFN0-Offset defines the time offset of the SFN0 slot 0 for the transmitting cell with respect to SFN0
slot 0 of [FFS in RAN2].
PRS
- DL-PRS-ResourceSetSlotOffset defines the slot offset with respect to SFN0 slot 0 and takes values 𝑇offset ∈
PRS
{0,1, … , 𝑇per − 1}.
- DL-PRS-CombSizeN defines the comb size of a DL PRS resource where the allowable values are given in Clause
7.4.1.7.1 of [TS38.211]. All DL PRS resource sets belonging to the same positioning frequency layer have the
same value of DL-PRS-combSizeN.
- DL-PRS-ResourceBandwidth defines the number of resource blocks configured for PRS transmission. The
parameter has a granularity of 4 PRBs with a minimum of 24 PRBs and a maximum of 272 PRBs. All DL PRS
resources sets within a positioning frequency layer have the same value of DL-PRS-ResourceBandwidth.
- DL-PRS-StartPRB defines the starting PRB index of the DL PRS resource with respect to reference Point A,
where reference Point A is given by the higher-layer parameter DL-PRS-PointA. The starting PRB index has a
granularity of one PRB with a minimum value of 0 and a maximum value of 2176 PRBs. All DL PRS Resource
Sets belonging to the same Positioning Frequency Layer have the same value of Start PRB.
A DL PRS resource is defined by:
- DL-PRS-ResourceList determines the DL PRS resources that are contained within one DL PRS resource set.
- DL-PRS-ResourceId determines the DL PRS resource configuration identity. All DL PRS resource IDs are
locally defined within a DL PRS resource set.
- DL-PRS-SequenceId is used to initialize cinit value used in pseudo random generator [4, TS38.211, 7.4.1.7.2] for
generation of DL PRS sequence for a given DL PRS resource.
- DL-PRS-ReOffset defines the starting RE offset of the first symbol within a DL PRS resource in frequency. The
relative RE offsets of the remaining symbols within a DL PRS resource are defined based on the initial offset
and the rule described in Clause 7.4.1.7.3 of [4, TS38.211].
3GPP
Release 16 46 3GPP TS 38.214 V16.1.0 (2020-03)
- DL-PRS-ResourceSlotOffset determines the starting slot of the DL PRS resource with respect to corresponding
DL-PRS-ResourceSetSlotOffset
- DL-PRS-ResourceSymbolOffset determines the starting symbol of the DL PRS resource within the starting slot.
- DL-PRS-NumSymbols defines the number of symbols of the DL PRS resource within a slot where the allowable
values are given in Clause 7.4.1.7.1 of [4, TS38.211].
- DL-PRS-QCL-Info defines any quasi-colocation information of the DL PRS resource with other reference
signals. The DL PRS may be configured to be 'QCL-Type-D' with a DL PRS or SS/PBCH Block from a serving
cell or a non-serving cell. The DL PRS may be configured to be 'QCL-Type-C' with a SS/PBCH Block from a
serving or non-serving cell. If the DL PRS is configured as both 'QCL-Type-C' and 'QCL-Type-D' with a
SS/PBCH Block then the SSB index indicated should be the same.
The UE assumes constant EPRE is used for all REs of a given DL PRS resource.
The UE may be indicated by the network that a DL PRS resources can be used as the reference for the DL RSTD, DL
PRS-RSRP, and UE Rx-Tx time difference measurements in a higher layer parameter DL-PRS-RstdReferenceInfo. The
reference time indicated by the network to the UE can also be used by the UE to determine how to apply higher layer
parameters DL-PRS-expectedRSTD and DL-PRS-expectedRSTD-uncertainty. The UE expects the reference time to be
indicated whenever it is expected to receive the DL PRS. This reference time provided by DL-PRS-RstdReferenceInfo
may include an [ID], a PRS resource set ID, and optionally a single PRS resource ID or a list of PRS resource IDs. The
UE may use different DL PRS resources or a different DL PRS resource set to determine the reference time for the
RSTD measurement as long as the condition that the DL PRS resources used belong to a single DL PRS resource set is
met. If the UE chooses to use a different reference time than indicated by the network, then it is expected to report the
[ID], the DL PRS resource ID(s) or the DL PRS resource set ID used to determine the reference.
The UE may be configured to report quality metrics corresponding to the RSTD and UE Rx-Tx time difference
measurements which include the following fields:
- TimingMeasQuality-Value which provides the best estimate of the uncertainty of the measurement
- TimingMeasQuality-Resolution which specifies the resolution levels used in the Value field
The UE expects to be configured with higher layer parameter DL-PRS-expectedRSTD, which defines the time difference
with respect to the received DL subframe timing the UE is expected to receive DL PRS, and DL-PRS-expectedRSTD-
uncertainty, which defines a search window around the expectedRSTD.
For DL UE positioning measurement reporting in higher layer parameters DL-PRS-RstdMeasurementInfo or DL-PRS-

UE-Rx-Tx-MeasurementInfo the UE can be configured to report the DL PRS resource ID(s) or the DL PRS resource set
ID(s) associated with the DL PRS resource(s) or the DL PRS resource set(s) which are used in determining the UE
measurements DL RSTD, UE Tx-Rx time difference or the DL PRS-RSRP.
The UE can be configured in higher layer parameter UE Rx-Tx Time-MeasRequestInfo to report multiple UE Rx-Tx
time difference measurements corresponding to a single configured SRS resource or resource set for positioning. Each
measurement corresponds to a single received DL PRS resource or resource set which can be in difference positioning
frequency layers.
For the DL RSTD, DL PRS-RSRP, and UE Rx-Tx time difference measurements the UE can report an associated
higher layer parameter Timestamp. The Timestamp can include the SFN and the slot number for a subcarrier spacing.
These values correspond to the reference which is provided by DL-PRS-RSTDReferenceInfo.
The UE is expected to measure the DL PRS resource outside the active DL BWP or with a numerology different from
the numerology of the active DL BWP if the measurement is made during a configured measurement gap. When not
configured with a measurement gap, the UE is only required to measure DL PRS within the active DL BWP and with
the same numerology as the active DL BWP. When the UE is expected to measure the DL PRS resource outside the
active DL BWP it may request a measurement gap in higher layer parameter [XYZ].
The UE assumes that the DL PRS from the serving cell is not mapped to any symbol that contains SS/PBCH block from
the serving cell. If the time frequency location of the SS/PBCH block transmissions from non-serving cells are provided
to the UE then the UE also assumes that the DL PRS from a non-serving cell is not mapped to any symbol that contains
the SS/PBCH block of the same non-serving cell.
The UE may be configured to report, subject to UE capability, up to 4 DL RSTD measurements per pair of cells with
each measurement between a different pair of DL PRS resources or DL PRS resource sets within the DL PRS
3GPP
Release 16 47 3GPP TS 38.214 V16.1.0 (2020-03)
configured for those cells. The up to 4 measurements being performed on the same pair of cells and all DL RSTD
measurements in the same report use a single reference timing.
The UE may be configured to measure and report up to 8 DL PRS RSRP measurements on different DL PRS resources
from the same cell. When the UE reports DL PRS RSRP measurements from one DL PRS resource set, the UE may
indicate which DL PRS RSRP measurements have been performed using the same spatial domain filter for reception.
If the UE is configured with DL-PRS-QCL-Info and the QCL relation is between two DL PRS resources, then the UE
assumes those DL PRS resources are from the same cell. If DL-PRS-QCL-Info is configured to the UE with 'QCL-Type-
D' with a source DL-PRS-Resource then the DL-PRS-ResourceSetId and the DL-PRS-ResrouceId of the source DL-
PRS-Resource are expected to be indicated to the UE.
The UE does not expect to process the DL PRS in the same symbol where other DL signals and channels are
transmitted to the UE when there is no measurement gap configured to the UE.
5.1.7 Code block group based PDSCH transmission

5.1.7.1 UE procedure for grouping of code blocks to code block groups
If a UE is configured to receive code block group (CBG) based transmissions by receiving the higher layer parameter
codeBlockGroupTransmission for PDSCH, the UE shall determine the number of CBGs for atransport block reception
as
M = min (N , C ) ,
where N is the maximum number of CBGs per transport block as configured by

maxCodeBlockGroupsPerTransportBlock for PDSCH, and C is the number of code blocks in the transport block
according to the procedure defined in Clause 7.2.3 of [5, TS 38.212].
Define M 1 = mod (C , M ) , K1 =  C  , and K 2 =  C  .

M  M 
If M 1  0 , CBG m, m = 0,1,..., M 1 − 1 , consists of code blocks with indices m  K 1 + k , k = 0,1,..., K 1 − 1 . CBG m,

m = M 1 , M 1 + 1,..., M − 1 , consists of code blocks with indices M 1  K 1 + (m − M 1 )  K 2 + k , k = 0,1,..., K 2 − 1 .
5.1.7.2 UE procedure for receiving code block group based transmissions

If a UE is configured to receive code block group based transmissions by receiving the higher layer parameter
codeBlockGroupTransmission for PDSCH,
- The CBG transmission information (CBGTI) field of DCI format 1_1 is of length 𝑁𝑇𝐵 ∙ 𝑁 bits, where 𝑁𝑇𝐵 is the
value of the higher layer parameter maxNrofCodeWordsScheduledByDCI. If 𝑁𝑇𝐵 = 2 the CBGTI field bits are
mapped such that the first set of 𝑁 bits starting from the MSB corresponds to the first TB while the second set of
𝑁 bits corresponds to a second TB, if scheduled. The first M bits of each set of 𝑁 bits in the CBGTI field have
an in-order one-to-one mapping with the M CBGs of the TB, with the MSB mapped to CBG#0.
- For initial transmission of a TB as indicated by the New Data Indicator field of the scheduling DCI, the UE may
assume that all the code block groups of the TB are present.
- For a retransmission of a TB as indicated by the New Data Indicator field of the scheduling DCI, the UE may
assume that
- The CBGTI field of the scheduling DCI indicates which CBGs of the TB are present in the transmission. A
bit value of 0' in the CBGTI field indicates that the corresponding CBG is not transmitted and 1' indicates that
it is transmitted.
- If the CBG flushing out information (CBGFI) field of the scheduling DCI is present, CBGFI set to 0'
indicates that the earlier received instances of the same CBGs being transmitted may be corrupted, and
CBGFI set to 1' indicates that the CBGs being retransmitted are combinable with the earlier received
instances of the same CBGs.
- A CBG contains the same CBs as in the initial transmission of the TB.
3GPP
Release 16 48 3GPP TS 38.214 V16.1.0 (2020-03)
5.2 UE procedure for reporting channel state information (CSI)

5.2.1 Channel state information framework
The procedures on aperiodic CSI reporting described in this clause assume that the CSI reporting is triggered by DCI
format 0_1, but they equally apply to CSI reporting triggered by DCI format 0_2, by applying the higher layer
parameter reportTriggerSize-ForDCIFormat0_2 instead of reportTriggerSize.
The time and frequency resources that can be used by the UE to report CSI are controlled by the gNB. CSI may consist
of Channel Quality Indicator (CQI), precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), SS/PBCH
Block Resource indicator (SSBRI), layer indicator (LI), rank indicator (RI), L1-RSRP or L1-SINR.
For CQI, PMI, CRI, SSBRI, LI, RI, L1-RSRP, L1-SINR a UE is configured by higher layers with N≥1 CSI-
ReportConfig Reporting Settings, M≥1 CSI-ResourceConfig Resource Settings, and one or two list(s) of trigger states
(given by the higher layer parameters CSI-AperiodicTriggerStateList and CSI-SemiPersistentOnPUSCH-
TriggerStateList). Each trigger state in CSI-AperiodicTriggerStateList contains a list of associated CSI-ReportConfigs
indicating the Resource Set IDs for channel and optionally for interference. Each trigger state in CSI-
SemiPersistentOnPUSCH-TriggerStateList contains one associated CSI-ReportConfig.
5.2.1.1 Reporting settings

Each Reporting Setting CSI-ReportConfig is associated with a single downlink BWP (indicated by higher layer
parameter BWP-Id) given in the associated CSI-ResourceConfig for channel measurement and contains the parameter(s)
for one CSI reporting band:codebook configuration including codebook subset restriction, time-domain behavior,
frequency granularity for CQI and PMI, measurement restriction configurations, and the CSI-related quantities to be
reported by the UE such as the layer indicator (LI), L1-RSRP, L1-SINR, CRI, and SSBRI (SSB Resource Indicator).
The time domain behavior of the CSI-ReportConfig is indicated by the higher layer parameter reportConfigType and
can be set to 'aperiodic', 'semiPersistentOnPUCCH', 'semiPersistentOnPUSCH', or 'periodic'. For periodic and
semiPersistentOnPUCCH/semiPersistentOnPUSCH CSI reporting, the configured periodicity and slot offset applies in
the numerology of the UL BWP in which the CSI report is configured to be transmitted on. The higher layer parameter
reportQuantity indicates the CSI-related, L1-RSRP-related or L1-SINR-related quantities to report. The
reportFreqConfiguration indicates the reporting granularity in the frequency domain, including the CSI reporting band
and if PMI/CQI reporting is wideband or sub-band. The timeRestrictionForChannelMeasurements parameter in CSI-
ReportConfig can be configured to enable time domain restriction for channel measurements and
timeRestrictionForInterferenceMeasurements can be configured to enable time domain restriction for interference
measurements. The CSI-ReportConfig can also contain CodebookConfig, which contains configuration parameters for
Type-I, Type II or Enhanced Type II CSI including codebook subset restriction, and configurations of group based
reporting.
For operation with shared spectrum channel access, the UE should not average CSI-RS measurements for channel
estimation from occasions of an NZP CSI-RS (defined in [4, TS 38.211]) located in different DL transmissions burst
(defined in [X, TS 37.213]).
5.2.1.2 Resource settings

Each CSI Resource Setting CSI-ResourceConfig contains a configuration of a list of S≥1 CSI Resource Sets (given by
higher layer parameter csi-RS-ResourceSetList), where the list is comprised of references to either or both of NZP CSI-
RS resource set(s) and SS/PBCH block set(s) or the list is comprised of references to CSI-IM resource set(s). Each CSI
Resource Setting is located in the DL BWP identified by the higher layer parameter BWP-id, and all CSI Resource
Settings linked to a CSI Report Setting have the same DL BWP.
The time domain behavior of the CSI-RS resources within a CSI Resource Setting are indicated by the higher layer
parameter resourceType and can be set to aperiodic, periodic, or semi-persistent. For periodic and semi-persistent CSI
Resource Settings, the number of CSI-RS Resource Sets configured is limited to S=1. For periodic and semi-persistent
CSI Resource Settings, the configured periodicity and slot offset is given in the numerology of its associated DL BWP,
as given by BWP-id. When a UE is configured with multiple CSI-ResourceConfigs consisting the same NZP CSI-RS
resource ID, the same time domain behavior shall be configured for the CSI-ResourceConfigs. When a UE is configured
with multiple CSI-ResourceConfigs consisting the same CSI-IM resource ID, the same time-domain behavior shall be
configured for the CSI-ResourceConfigs. All CSI Resource Settings linked to a CSI Report Setting shall have the same
time domain behavior.
3GPP
Release 16 49 3GPP TS 38.214 V16.1.0 (2020-03)
The following are configured via higher layer signaling for one or more CSI Resource Settings for channel and
interference measurement:
- CSI-IM resource for interference measurement as described in Clause 5.2.2.4.
- NZP CSI-RS resource for interference measurement as described in Clause 5.2.2.3.1.
- NZP CSI-RS resource for channel measurement as described in Clause 5.2.2.3.1.
The UE may assume that the NZP CSI-RS resource(s) for channel measurement and the CSI-IM resource(s) for
interference measurement configured for one CSI reporting are resource-wise QCLed with respect to 'QCL-TypeD'.
When NZP CSI-RS resource(s) is used for interference measurement, the UE may assume that the NZP CSI-RS
resource for channel measurement and the CSI- IM resource or NZP CSI-RS resource(s) for interference measurement
configured for one CSI reporting are QCLed with respect to 'QCL-TypeD'.
For L1-SINR measurement:
- When one Resource Setting is configured, the Resource Setting (given by higher layer parameter
resourcesForChannelMeasurement) is for channel and interference measurement for L1-SINR computation. UE
may assume that same 1 port NZP CSI-RS resource(s) with density 3 REs/RB is used for both channel and
interference measurements.
- When two Resource Settings are configured, the first one Resource Setting (given by higher layer parameter
resourcesForChannelMeasurement) is for channel measurement on SSB or NZP CSI-RS and the second one
(given by either higher layer parameter csi-IM-ResourcesForInterference or higher layer parameter nzp-CSI-RS-
ResourcesForInterference) is for interference measurement performed on CSI-IM or on 1 port NZP CSI-RS with
density 3 REs/RB, where each SSB or NZP CSI-RS resource for channel measurement is associated with one
CSI-IM resource or one NZP CSI-RS resource for interference measurement by the ordering of the SSB or NZP
CSI-RS resource for channel measurement and CSI-IM resource or NZP CSI-RS resource for interference
measurement in the corresponding resource sets. The number of SSB(s) or CSI-RS resources for channel
measurement equals to the number of CSI-IM resources or the number of NZP CSI-RS resource for interference
measurement.
- UE may apply 'QCL-TypeD' assumption of the SSB or 'QCL-TypeD' configured to the NZP CSI-RS resource
for channel measurement to measure the associated CSI- IM resource or associated NZP CSI-RS resource for
interference measurement configured for one CSI reporting
- UE may expect that the NZP CSI-RS resource set for channel measurement and the NZP-CSI-RS resource
set for interference measurement, if any, are configured with the higher layer parameter repetition.
- [When three Resource Settings are configured, the first one Resource Setting (given by higher layer
parameterresourcesForChannelMeasurement) is for channel measurement on SSB or NZP CSI-RS. The second
one (given by either higher layer parameter csi-IM-ResourcesForInterference) is for interference measurement
performed on CSI-IM, where each NZP CSI-RS resource set for channel measurement is associated with one
CSI-IM resource for interference measurement. The Third one (given by higher layer parameter nzp-CSI-RS-
ResourcesForInterference) is for interference measurement performed on 1 port NZP CSI-RS with density 3
REs/RB.]
5.2.1.3 (void)
5.2.1.4 Reporting configurations
The UE shall calculate CSI parameters (if reported) assuming the following dependencies between CSI parameters (if
reported)
- LI shall be calculated conditioned on the reported CQI, PMI, RI and CRI
- CQI shall be calculated conditioned on the reported PMI, RI and CRI
- PMI shall be calculated conditioned on the reported RI and CRI
- RI shall be calculated conditioned on the reported CRI.
The Reporting configuration for CSI can be aperiodic (using PUSCH), periodic (using PUCCH) or semi-persistent
(using PUCCH, and DCI activated PUSCH). The CSI-RS Resources can be periodic, semi-persistent, or aperiodic.
3GPP
Release 16 50 3GPP TS 38.214 V16.1.0 (2020-03)
Table 5.2.1.4-1 shows the supported combinations of CSI Reporting configurations and CSI-RS Resource
configurations and how the CSI Reporting is triggered for each CSI-RS Resource configuration. Periodic CSI-RS is
configured by higher layers. Semi-persistent CSI-RS is activated and deactivated as described in Clause 5.2.1.5.2.
Aperiodic CSI-RS is configured and triggered/activated as described in Clause 5.2.1.5.1.
Table 5.2.1.4-1: Triggering/Activation of CSI Reporting for the possible CSI-RS Configurations.
CSI-RS Configuration Periodic CSI Reporting Semi-Persistent CSI Aperiodic CSI Reporting
Reporting
Periodic CSI-RS No dynamic For reporting on PUCCH, Triggered by DCI;
triggering/activation the UE receives an additionally, subselection
activation command, as indication as described in
described in clause clause 6.1.3.13 of [10, TS
6.1.3.16 of [10, TS 38.321] possible as
38.321]; for reporting on defined in Clause
PUSCH, the UE receives 5.2.1.5.1.
triggering on DCI
Semi-Persistent CSI-RS Not Supported For reporting on PUCCH, Triggered by DCI;
the UE receives an additionally, subselection
activation command, as indication as described in
described in clause clause 6.1.3.13 of [10, TS
6.1.3.16 of [10, TS 38.321] possible as
38.321]; for reporting on defined in Clause
PUSCH, the UE receives 5.2.1.5.1.
triggering on DCI
Aperiodic CSI-RS Not Supported Not Supported Triggered by DCI;
additionally, subselection
indication as described in
clause 6.1.3.13 of [10, TS
38.321] possible as
defined in Clause
5.2.1.5.1.
When the UE is configured with higher layer parameter NZP-CSI-RS-ResourceSet and when the higher layer parameter
repetition is set to 'off', the UE shall determine a CRI from the supported set of CRI values as defined in Clause
6.3.1.1.2 of [5, TS 38.212] and report the number in each CRI report. When the higher layer parameter repetition is set
to 'on', CRI is not reported. CRI reporting is not supported when the higher layer parameter codebookType is set to
either 'typeII', 'typeII-PortSelection', 'typeII-r16' or to 'typeII-PortSelection-r16'.
For a periodic or semi-persistent CSI report on PUCCH, the periodicity 𝑇𝐶𝑆𝐼 (measured in slots) and the slot offset
𝑇𝑜𝑓𝑓𝑠𝑒𝑡 are configured by the higher layer parameter reportSlotConfig. Unless specified otherwise, the UE shall transmit
𝜇
the CSI report in frames with SFN 𝑛𝑓 and slot number within the frame 𝑛𝑠,𝑓 satisfying
frame,𝜇 𝜇
(𝑁slot 𝑛𝑓 + 𝑛𝑠,𝑓 − 𝑇𝑜𝑓𝑓𝑠𝑒𝑡 )mod TCSI = 0
where 𝜇 is the SCS configuration of the UL BWP the CSI report is transmitted on.
For a semi-persistent CSI report on PUSCH, the periodicity 𝑇𝐶𝑆𝐼 (measured in slots) is configured by the higher layer
parameter reportSlotConfig. Unless specified otherwise, the UE shall transmit the CSI report in frames with SFN 𝑛𝑓 and
𝜇
slot number within the frame 𝑛𝑠,𝑓 satisfying
frame,𝜇 𝜇
(𝑁slot (𝑛𝑓 − 𝑛𝑓𝑠𝑡𝑎𝑟𝑡 ) + 𝑛𝑠,𝑓 − 𝑛𝑠,𝑓
𝑠𝑡𝑎𝑟𝑡
)mod TCSI = 0
where 𝑛𝑓𝑠𝑡𝑎𝑟𝑡 and 𝑛𝑠,𝑓

are the SFN and slot number within the frame respectively of the initial semi-persistent PUSCH
transmission according to the activating DCI.
For a semi-persistent or aperiodic CSI report on PUSCH, the allowed slot offsets are configured by the following higher
layer parameters:
- if triggered/activated by DCI format 0_2 and the higher layer parameter reportSlotOffsetListForDCI-Format0-2
is configured, the allowed slot offsets are configured by reportSlotOffsetListForDCI-Format0-2, and
- if triggered/activated by DCI format 0_1 and the higher layer parameter reportSlotOffsetListForDCI-Format0-1
is configured, the allowed slot offsets are configured by reportSlotOffsetListForDCI-Format0-1, and
3GPP
Release 16 51 3GPP TS 38.214 V16.1.0 (2020-03)
- otherwise, the allowed slot offsets are configured by the higher layer parameter reportSlotOffsetList.
The offset is selected in the activating/triggering DCI.
For CSI reporting, a UE can be configured via higher layer signaling with one out of two possible subband sizes, where
SB contiguous PRBs and depends on the total number of PRBs in the bandwidth part
a subband is defined as NPRB
according to Table 5.2.1.4-2.
Table 5.2.1.4-2: Configurable subband sizes
Bandwidth part (PRBs) Subband size (PRBs)

< 24 N/A
24 – 72 4, 8
73 – 144 8, 16
145 – 275 16, 32
The reportFreqConfiguration contained in a CSI-ReportConfig indicates the frequency granularity of the CSI Report. A
CSI Reporting Setting configuration defines a CSI reporting band as a subset of subbands of the bandwidth part, where
the reportFreqConfiguration indicates:
- the csi-ReportingBand as a contiguous or non-contiguous subset of subbands in the bandwidth part for which
CSI shall be reported.
- A UE is not expected to be configured with csi-ReportingBand which contains a subband where a CSI-RS
resource linked to the CSI Report setting has the frequency density of each CSI-RS port per PRB in the
subband less than the configured density of the CSI-RS resource.
- If a CSI-IM resource is linked to the CSI Report Setting, a UE is not expected to be configured with csi-
ReportingBand which contains a subband where not all PRBs in the subband have the CSI-IM REs present.
- wideband CQI or subband CQI reporting, as configured by the higher layer parameter cqi-FormatIndicator.
When wideband CQI reporting is configured, a wideband CQI is reported for each codeword for the entire CSI
reporting band. When subband CQI reporting is configured, one CQI for each codeword is reported for each
subband in the CSI reporting band.
- wideband PMI or subband PMI reporting as configured by the higher layer parameter pmi-FormatIndicator.
When wideband PMI reporting is configured, a wideband PMI is reported for the entire CSI reporting band.
When subband PMI reporting is configured, except with 2 antenna ports, a single wideband indication (i1 in
Clause 5.2.2.2) is reported for the entire CSI reporting band and one subband indication (i2 in clause 5.2.2.2) is
reported for each subband in the CSI reporting band. When subband PMIs are configured with 2 antenna ports, a
PMI is reported for each subband in the CSI reporting band.
- a UE is not expected to be configured with pmi-FormatIndicator if codebookConfig is set to 'typeII-r16' or

'typeII-PortSelection-r16'.
A CSI Reporting Setting is said to have a wideband frequency-granularity if
- reportQuantity is set to 'cri-RI-PMI-CQI', or 'cri-RI-LI-PMI-CQI', cqi-FormatIndicator is set to 'widebandCQI'

and pmi-FormatIndicator is set to 'widebandPMI', or
- reportQuantity is set to 'cri-RI-i1' or
- reportQuantity is set to 'cri-RI-CQI' or 'cri-RI-i1-CQI' and cqi-FormatIndicator is set to 'widebandCQI', or
- reportQuantity is set to 'cri-RSRP' or 'ssb-Index-RSRP'
otherwise, the CSI Reporting Setting is said to have a subband frequency-granularity.
The first subband size is given by

SB
N PRB (
− N BW
start SB
)
P,i mod N PRB and the last subband size given by
(N start
BW P,i + N BW
size
) SB
( start
)
P,i mod N PRB if N BW P,i + N BW P,i mod N PRB  0 and
size SB SB if
N PRB (N start
BW P,i + N BW
size
)
P,i mod N PRB = 0
SB
3GPP
Release 16 52 3GPP TS 38.214 V16.1.0 (2020-03)
If a UE is configured with semi-persistent CSI reporting, the UE shall report CSI when both CSI-IM and NZP CSI-RS
resources are configured as periodic or semi-persistent. If a UE is configured with aperiodic CSI reporting, the UE shall
report CSI when both CSI-IM and NZP CSI-RS resources are configured as periodic, semi-persistent or aperiodic.
A UE configured with DCI format 0_1 or 0_2 does not expect to be triggered with multiple CSI reports with the same
CSI-ReportConfigId.
5.2.1.4.1 Resource Setting configuration

For aperiodic CSI, each trigger state configured using the higher layer parameter CSI-AperiodicTriggerState is
associated with one or multiple CSI-ReportConfig where each CSI-ReportConfig is linked to periodic, or semi-
persistent, or aperiodic resource setting(s):
- When one Resource Setting is configured, the Resource Setting (given by higher layer parameter
resourcesForChannelMeasurement) is for channel measurement for L1-RSRP or L1-SINR computation.
- When two Resource Settings are configured, the first one Resource Setting (given by higher layer parameter
resourcesForChannelMeasurement) is for channel measurement and the second one (given by either higher layer
parameter csi-IM-ResourcesForInterference or higher layer parameter nzp-CSI-RS-ResourcesForInterference) is
for interference measurement performed on CSI-IM or on NZP CSI-RS.
- When three Resource Settings are configured, the first Resource Setting (higher layer parameter
resourcesForChannelMeasurement) is for channel measurement, the second one (given by higher layer
parameter csi-IM-ResourcesForInterference) is for CSI-IM based interference measurement and the third one
(given by higher layer parameter nzp-CSI-RS-ResourcesForInterference) is for NZP CSI-RS based interference
measurement.
For semi-persistent or periodic CSI, each CSI-ReportConfig is linked to periodic or semi-persistent Resource Setting(s):
- When one Resource Setting (given by higher layer parameter resourcesForChannelMeasurement) is configured,
the Resource Setting is for channel measurement for L1-RSRP computation.
- When two Resource Settings are configured, the first Resource Setting (given by higher layer parameter
resourcesForChannelMeasurement) is for channel measurement and the second Resource Setting (given by
higher layer parameter csi-IM-ResourcesForInterference) is used for interference measurement performed on
CSI-IM.
A UE is not expected to be configured with more than one CSI-RS resource in resource set for channel measurement for
a CSI-ReportConfig with the higher layer parameter codebookType set to either 'typeII', 'typeII-PortSelection', 'typeII-
r16' or to 'typeII-PortSelection-r16'. A UE is not expected to be configured with more than 64 NZP CSI-RS resources in
resource setting for channel measurement for a CSI-ReportConfig with the higher layer parameter reportQuantity set to
'none', 'cri-RI-CQI', 'cri-RSRP' or 'ssb-Index-RSRP'. If interference measurement is performed on CSI-IM, each CSI-RS
resource for channel measurement is resource-wise associated with a CSI-IM resource by the ordering of the CSI-RS
resource and CSI-IM resource in the corresponding resource sets. The number of CSI-RS resources for channel
measurement equals to the number of CSI-IM resources.
If interference measurement is performed on NZP CSI-RS, a UE does not expect to be configured with more than one
NZP CSI-RS resource in the associated resource set within the resource setting for channel measurement. The UE
configured with the higher layer parameter nzp-CSI-RS-ResourcesForInterference may expect no more than 18 NZP
CSI-RS ports configured in a NZP CSI-RS resource set.
For CSI measurement(s) other than L1-SINR, a UE assumes:
- each NZP CSI-RS port configured for interference measurement corresponds to an interference transmission
layer.
- all interference transmission layers on NZP CSI-RS ports for interference measurement take into account the
associated EPRE ratios configured in 5.2.2.3.1;
- other interference signal on REs of NZP CSI-RS resource for channel measurement, NZP CSI-RS resource for
interference measurement, or CSI-IM resource for interference measurement.
For L1-SINR measurement with dedicated interference measurement resources, a UE assumes:
3GPP
Release 16 53 3GPP TS 38.214 V16.1.0 (2020-03)
- the total received power on dedicated NZP CSI-RS resource for interference measurement [and/] or dedicated
CSI-IM resource for interference measurement corresponds to interference and noise.
5.2.1.4.2 Report Quantity Configurations

A UE may be configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to either 'none',
'cri-RI-PMI-CQI ', 'cri-RI-i1', 'cri-RI-i1-CQI', 'cri-RI-CQI', 'cri-RSRP', 'cri-SINR', 'ssb-Index-RSRP', 'ssb-Index-SINR'
or 'cri-RI-LI-PMI-CQI'.
If the UE is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'none', then the
UE shall not report any quantity for the CSI-ReportConfig.
If the UE is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'cri-RI-PMI-
CQI', or 'cri-RI-LI-PMI-CQI', the UE shall report a preferred precoder matrix for the entire reporting band, or a
preferred precoder matrix per subband, according to Clause 5.2.2.2.
If the UE is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'cri-RI-i1',
- the UE expects, for that CSI-ReportConfig, to be configured with higher layer parameter codebookType set to
'typeI-SinglePanel' and pmi-FormatIndicator set to 'widebandPMI' and,
- the UE shall report a PMI consisting of a single wideband indication ( i1 in Clause 5.2.2.2.1) for the entire CSI
reporting band.
If the UE is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'cri-RI-i1-CQI',
- the UE expects, for that CSI-ReportConfig, to be configured with higher layer parameter codebookType set to
'typeI-SinglePanel' and pmi-FormatIndicator set to 'widebandPMI' and,
- the UE shall report a PMI consisting of a single wideband indication ( i1 in Clause 5.2.2.2.1) for the entire CSI
reporting band. The CQI is calculated conditioned on the reported i1 assuming PDSCH transmission with N p  1
precoders (corresponding to the same i1 but different i2 in Clause 5.2.2.2.1), where the UE assumes that one
precoder is randomly selected from the set of N p precoders for each PRG on PDSCH, where the PRG size for
CQI calculation is configured by the higher layer parameter pdsch-BundleSizeForCSI.
If the UE is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'cri-RI-CQI',
- if the UE is configured with higher layer parameter non-PMI-PortIndication contained in a CSI-ReportConfig, r

ports are indicated in the order of layer ordering for rank r and each CSI-RS resource in the CSI resource setting
is linked to the CSI-ReportConfig based on the order of the associated NZP-CSI-RS-ResourceId in the linked CSI
resource setting for channel measurement given by higher layer parameter resourcesForChannelMeasurement.
The configured higher layer parameter non-PMI-PortIndication contains a sequence
p 0(1) , p 0( 2) , p1( 2) , p 0(3) , p1(3) , p 2(3) ,..., p 0( R ) , p1( R ) ,..., p R( R−)1 of port indices, where p0( ) ,..., p(−)1 are the CSI-RS port
indices associated with rank ν and R  1, 2,..., P where P  1,2,4,8 is the number of ports in the CSI-RS
resource. The UE shall only report RI corresponding to the configured fields of PortIndexFor8Ranks.
- if the UE is not configured with higher layer parameter non-PMI-PortIndication, the UE assumes, for each CSI-
RS resource in the CSI resource setting linked to the CSI-ReportConfig, that the CSI-RS port indices
p0( ) ,..., p(−)1 = 0,..., − 1 are associated with ranks  = 1,2,..., P where P  1,2,4,8 is the number of ports in
the CSI-RS resource.
- When calculating the CQI for a rank, the UE shall use the ports indicated for that rank for the selected CSI-RS
1
resource. The precoder for the indicated ports shall be assumed to be the identity matrix scaled by .

If the UE is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'cri-RSRP' or
'ssb-Index-RSRP',
- if the UE is configured with the higher layer parameter groupBasedBeamReporting set to 'disabled', the UE is
not required to update measurements for more than 64 CSI-RS and/or SSB resources, and the UE shall report in
a single report nrofReportedRS (higher layer configured) different CRI or SSBRI for each report setting.
3GPP
Release 16 54 3GPP TS 38.214 V16.1.0 (2020-03)
- if the UE is configured with the higher layer parameter groupBasedBeamReporting set to 'enabled', the UE is not
required to update measurements for more than 64 CSI-RS and/or SSB resources, and the UE shall report in a
single reporting instance two different CRI or SSBRI for each report setting, where CSI-RS and/or SSB
resources can be received simultaneously by the UE either with a single spatial domain receive filter, or with
multiple simultaneous spatial domain receive filters.
If the UE is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'cri-SINR' or
'ssb-Index-SINR',
- if the UE is configured with the higher layer parameter groupBasedBeamReporting set to 'disabled', the UE shall
report [in a single report] nrofReportedRSForSINR (higher layer configured) different CRI or SSBRI for each
report setting.
- if the UE is configured with the higher layer parameter groupBasedBeamReporting set to 'enabled', the UE shall
report in a single reporting instance two different CRI or SSBRI for each report setting, [where CSI-RS and/or
SSB resources can be received simultaneously by the UE either with a single spatial domain receive filter, or
with multiple simultaneous spatial domain receive filters.]
If the UE is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'cri-RSRP', 'cri-
RI-PMI-CQI ', 'cri-RI-i1', 'cri-RI-i1-CQI', 'cri-RI-CQI' or 'cri-RI-LI-PMI-CQI', and 𝐾𝑠 > 1 resources are configured in
the corresponding resource set for channel measurement, then the UE shall derive the CSI parameters other than CRI
conditioned on the reported CRI, where CRI k (k ≥ 0) corresponds to the configured (k+1)-th entry of associated nzp-
CSI-RSResource in the corresponding nzp-CSI-RS-ResourceSet for channel measurement, and (k+1)-th entry of
associated csi-IM-Resource in the corresponding csi-IM-ResourceSet (if configured) If 𝐾𝑠 = 2 CSI-RS resources are
configured, each resource shall contain at most 16 CSI-RS ports. If 2 < 𝐾𝑠 ≤ 8 CSI-RS resources are configured, each
resource shall contain at most 8 CSI-RS ports.
If the UE is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'ssb-Index-
RSRP', the UE shall report SSBRI, where SSBRI k (k ≥ 0) corresponds to the configured (k+1)-th entry of the
associated csi-SSB-ResourceList in the corresponding CSI-SSB-ResourceSet.
If the UE is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'cri-RI-PMI-
CQI', ' cri-RI-i1', 'cri-RI-i1-CQI', 'cri-RI-CQI' or 'cri-RI-LI-PMI-CQI', then the UE is not expected to be configured with
more than 8 CSI-RS resources in a CSI-RS resource set contained within a resource setting that is linked to the CSI-
ReportConfig.
If the UE is configured with a CSI-ReportConfig with higher layer parameter reportQuantity set to 'cri-RSRP' or 'none'
and the CSI-ReportConfig is linked to a resource setting configured with the higher layer parameter resourceType set to
'aperiodic', then the UE is not expected to be configured with more than 16 CSI-RS resources in a CSI-RS resource set
contained within the resource setting.
The LI indicates which column of the precoder matrix of the reported PMI corresponds to the strongest layer of the
codeword corresponding to the largest reported wideband CQI. If two wideband CQIs are reported and have equal
value, the LI corresponds to strongest layer of the first codeword.
5.2.1.4.3 L1-RSRP Reporting

For L1-RSRP computation
- the UE may be configured with CSI-RS resources, SS/PBCH Block resources or both CSI-RS and SS/PBCH
block resources, when resource-wise quasi co-located with 'QCL-Type C' and 'QCL-TypeD' when applicable.
- the UE may be configured with CSI-RS resource setting up to 16 CSI-RS resource sets having up to 64 resources
within each set. The total number of different CSI-RS resources over all resource sets is no more than 128.
For L1-RSRP reporting, if the higher layer parameter nrofReportedRS in CSI-ReportConfig is configured to be one, the
reported L1-RSRP value is defined by a 7-bit value in the range [-140, -44] dBm with 1dB step size, if the higher layer
parameter nrofReportedRS is configured to be larger than one, or if the higher layer parameter
groupBasedBeamReporting is configured as 'enabled', the UE shall use differential L1-RSRP based reporting, where the
largest measured value of L1-RSRP is quantized to a 7-bit value in the range [-140, -44] dBm with 1dB step size, and
the differential L1-RSRP is quantized to a 4-bit value. The differential L1-RSRP value is computed with 2 dB step size
with a reference to the largest measured L1-RSRP value which is part of the same L1-RSRP reporting instance. The
mapping between the reported L1-RSRP value and the measured quantity is described in [11, TS 38.133].
3GPP
Release 16 55 3GPP TS 38.214 V16.1.0 (2020-03)
5.2.1.4.4 L1-SINR Reporting

For L1-SINR computation, for channel measurement the UE may be configured with NZP CSI-RS resources and/or
SS/PBCH Block resources, for interference measurement the UE may be configured with NZP CSI-RS or CSI-IM
resources.
- for channel measurement, the UE may be configured with CSI-RS resource setting up to 64 CSI-RS resources or
up to 64 SS/PBCH Block resources.
For L1-SINR reporting, if the higher layer parameter nrofReportedRSForSINR in CSI-ReportConfig is configured to be
one, the reported L1-SINR value is defined by a 7-bit value in the range [-23, 40] dB with 0.5 dB step size, and if the
higher layer parameter nrofReportedRSForSINR is configured to be larger than one, the UE shall use differential L1-
SINR based reporting, where the largest measured value of L1-SINR is quantized to a 7-bit value in the range [-23, 40]
dB with 0.5 dB step size, and the differential L1-SINR is quantized to a 4-bit value. The differential L1-SINR is
computed with 1 dB step size with a reference to the largest measured L1-SINR value which is part of the same L1-
SINR reporting instance. When NZP CSI-RS is configured for channel measurement and/or interference measurement,
the reported L1-SINR values should not be compensated by the power offset(s) given by higher layer parameter
powerControOffsetSS or powerControlOffset.
5.2.1.5 Triggering/activation of CSI Reports and CSI-RS

5.2.1.5.1 Aperiodic CSI Reporting/Aperiodic CSI-RS when the triggering PDCCH and the
CSI-RS have the same numerology
For CSI-RS resource sets associated with Resource Settings configured with the higher layer parameter resourceType set
to 'aperiodic', 'periodic', or 'semi-persistent', trigger states for Reporting Setting(s) (configured with the higher layer
parameter reportConfigType set to 'aperiodic') and/or Resource Setting for channel and/or interference measurement on
one or more component carriers are configured using the higher layer parameter CSI-AperiodicTriggerStateList. For
aperiodic CSI report triggering, a single set of CSI triggering states are higher layer configured, wherein the CSI triggering
states can be associated with any candidate DL BWP. A UE is not expected to receive more than one DCI with non-zero
CSI request per slot. A UE is not expected to be configured with different TCI-StateId's for the same aperiodic CSI-RS
resource ID configured in multiple aperiodic CSI-RS resource sets with the same triggering offset in the same aperiodic
trigger state. A UE is not expected to receive more than one aperiodic CSI report request for transmission in a given slot.
When a UE is triggered with a CSI report for a DL BWP that is non-active when expecting to receive the most recent
occasion, no later than the CSI reference resource, of the associated NZP CSI-RS, the UE is not expected to report the
CSI for the non-active DL BWP and the CSI report associated with that BWP is omitted. When a UE is triggered with
aperiodic NZP CSI-RS in a DL BWP that is non-active when expecting to receive the NZP CSI-RS, the UE is not expected
to measure the aperiodic CSI-RS. In the carrier of the serving cell expecting to receive that associated NZP CSI-RS, if
the active DL BWP when receiving the NZP CSI-RS is different from the active DL BWP when receiving the triggering
DCI,
- the last symbol of the PDCCH span of the DCI carrying the BWP switching shall be no later than the last symbol
of the PDCCH span of the DCI carrying the CSI trigger, irrespective of whether they are in the same carrier of a
serving cell or not and irrespective of whether they are in the same SCS or not;
- the UE is not expected to have any other BWP switching in that carrier after the last symbol of the PDCCH span
covering the DCI carrying the CSI trigger and before the first symbol of the triggered NZP CSI-RS or CSI-IM.
A trigger state is initiated using the CSI request field in DCI.
- When all the bits of CSI request field in DCI are set to zero, no CSI is requested.
- When the number of configured CSI triggering states in CSI-AperiodicTriggerStateList is greater than 2 NTS − 1 ,
where N TS is the number of bits in the DCI CSI request field, the UE receives a subselection indication, as
described in clause 6.1.3.13 of [10, TS 38.321], used to map up to 2 NTS − 1 trigger states to the codepoints of the
CSI request field in DCI. N TS is configured by the higher layer parameter reportTriggerSize where
N TS  0,1, 2, 3, 4, 5, 6 . When the UE would transmit a PUCCH with HARQ-ACK information in slot n
corresponding to the PDSCH carrying the subselection indication, the corresponding action in [10, TS 38.321]
and UE assumption on the mapping of the selected CSI trigger state(s) to the codepoint(s) of DCI CSI request
where  is the SCS
field shall be applied starting from the first slot that is after slot 𝑛 + 3𝑁𝑠𝑙𝑜𝑡
configuration for the PUCCH.
3GPP
Release 16 56 3GPP TS 38.214 V16.1.0 (2020-03)
- When the number of CSI triggering states in CSI-AperiodicTriggerStateList is less than or equal to 2 NTS − 1 , the
CSI request field in DCI directly indicates the triggering state.
- For each aperiodic CSI-RS resource in a CSI-RS resource set associated with each CSI triggering state, the UE is
indicated the quasi co-location configuration of quasi co-location RS source(s) and quasi co-location type(s), as
described in Clause 5.1.5, through higher layer signaling of qcl-info which contains a list of references to TCI-
State's for the aperiodic CSI-RS resources associated with the CSI triggering state. If a State referred to in the list
is configured with a reference to an RS associated with 'QCL-TypeD', that RS may be an SS/PBCH block located
in the same or different CC/DL BWP or a CSI-RS resource configured as periodic or semi-persistent located in
the same or different CC/DL BWP.
- If the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI and the first
symbol of the aperiodic CSI-RS resources in a NZP-CSI-RS-ResourceSet configured without higher layer
parameter trs-Info is smaller than the UE reported threshold beamSwitchTiming, as defined in [13, TS
38.306], when the reported value is one of the values of {14, 28, 48}, or is smaller than 48 when the reported
value of beamSwitchTiming is one of the values of {224, 336}.
- if there is any other DL signal with an indicated TCI state in the same symbols as the CSI-RS, the UE
applies the QCL assumption of the other DL signal also when receiving the aperiodic CSI-RS. The other
DL signal refers to PDSCH scheduled with offset larger than or equal to the threshold
timeDurationForQCL, as defined in [13, TS 38.306], aperiodic CSI-RS scheduled with offset larger than
or equal to the UE reported threshold beamSwitchTiming when the reported value is one of the values
{14,28,48}, aperiodic CSI-RS scheduled with offset larger than or equal to 48 when the reported value of
beamSwitchTiming is one of the values {224, 336}, periodic CSI-RS, semi-persistent CSI-RS;
- else, when receiving the aperiodic CSI-RS, the UE applies the QCL assumption used for the CORESET
associated with a monitored search space with the lowest controlResourceSetId in the latest slot in which
one or more CORESETs within the active BWP of the serving cell are monitored.
- If the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI and the first
symbol of the aperiodic CSI-RS resources is equal to or greater than the UE reported threshold
beamSwitchTiming when the reported value is one of the values of {14,28,48}, or is equal to or greater than
48 when the reported value of beamSwitchTiming is one of the values of {224, 336}, the UE is expected to
apply the QCL assumptions in the indicated TCI states for the aperiodic CSI-RS resources in the CSI
triggering state indicated by the CSI trigger field in DCI.
- A non-zero codepoint of the CSI request field in the DCI is mapped to a CSI triggering state according to the
order of the associated positions of the up to 2𝑁𝑇𝑆 − 1 trigger states in CSI-AperiodicTriggerStateList with
codepoint '1' mapped to the triggering state in the first position.
For a UE configured with the higher layer parameter CSI-AperiodicTriggerStateList, if a Resource Setting linked to a
CSI-ReportConfig has multiple aperiodic resource sets, only one of the aperiodic CSI-RS resource sets from the
Resource Setting is associated with the trigger state, and the UE is higher layer configured per trigger state per Resource
Setting to select the one CSI-IM/NZP CSI-RS resource set from the Resource Setting.
When aperiodic CSI-RS is used with aperiodic reporting, the CSI-RS offset is configured per resource set by the higher
layer parameter aperiodicTriggeringOffset, including the case that the UE is not configured with
[minimumSchedulingOffset] for any DL or UL BWP and all the associated trigger states do not have the higher layer
parameter qcl-Type set to 'QCL-TypeD' in the corresponding TCI states. The CSI-RS triggering offset has the values of
{0, 1, 2, 3, 4, 16, 24} slots. If the UE is not configured with [minimumSchedulingOffset] for any DL or UL BWP and if
all the associated trigger states do not have the higher layer parameter qcl-Type set to 'QCL-TypeD' in the
corresponding TCI states , the CSI-RS triggering offset is fixed to zero. The aperiodic triggering offset of the CSI-IM
follows offset of the associated NZP CSI-RS for channel measurement.
The UE does not expect that aperiodic CSI-RS is transmitted before the OFDM symbol(s) carrying its triggering DCI.
When the minimum scheduling offset restriction is applied, UE is not expected to be triggered by CSI triggering state
indicated by the CSI request field in DCI in which CSI-RS triggering offset is smaller than the currently applicable
minimum scheduling offset restriction K0min.
If interference measurement is performed on aperiodic NZP CSI-RS, a UE is not expected to be configured with a
different aperiodic triggering offset of the NZP CSI-RS for interference measurement from the associated NZP CSI-RS
for channel measurement.
3GPP
Release 16 57 3GPP TS 38.214 V16.1.0 (2020-03)
If the UE is configured with a single carrier for uplink, the UE is not expected to transmit more than one aperiodic CSI
report triggered by different DCIs on overlapping OFDM symbols.
5.2.1.5.1a Aperiodic CSI Reporting/Aperiodic CSI-RS when the triggering PDCCH and the
CSI-RS have different numerologies
When the triggering PDCCH and the triggered aperiodic CSI-RS are of different numerologies, the behavior defined in
5.2.1.5.1 for the case where the numerologies are the same applies with the following exceptions:
Beam switch timing:
- If the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol
of the aperiodic CSI-RS resources in a NZP-CSI-RS-ResourceSet configured without higher layer parameter trs-
Info is smaller than the UE reported threshold beamSwitchTiming + d in CSI-RS symbols, as
defined in [13, TS 38.306], when the reported value is one of the values of {14, 28, 48}, or is smaller than 48+ d
when the reported value of beamSwitchTiming is one of the values of {224, 336} and where if the µPDCCH <
µCSIRS, the beam switching timing delay d is defined in Table 5.2.1.5.1a-1, else d is zero
- if one of the associated trigger states has the higher layer parameter qcl-Type set to 'QCL-TypeD',
- if there is any other DL signal with an indicated TCI state in the same symbols as the CSI-RS, the UE
applies the QCL assumption of the other DL signal also when receiving the aperiodic CSI-RS. The other
DL signal refers to PDSCH scheduled with offset larger than or equal to the threshold
timeDurationForQCL, as defined in [13, TS 38.306], aperiodic CSI-RS scheduled with offset larger than
or equal to the UE reported threshold beamSwitchTiming + d in CSI-RS symbols
when the reported value is one of the values {14,28,48}, aperiodic CSI-RS scheduled with offset larger
than or equal to 48+ d when the reported value of beamSwitchTiming is one of the values {224, 336},
periodic CSI-RS, semi-persistent CSI-RS;
- else,
- if at least one CORESET is configured for the BWP in which the aperiodic CSI-RS is to be received,
when receiving the aperiodic CSI-RS, the UE applies the QCL assumption used for the CORESET
associated with a monitored search space with the lowest CORESET-ID in the latest slot in which one or
more CORESETs within the active BWP of the serving cell are monitored.
- else, when receiving the aperiodic CSI-RS, the UE applies the QCL assumption of the lowest-ID
activated TCI state applicable to the PDSCH within the active BWP of the cell in which the CSI-RS is to
be received.
- If the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol
of the aperiodic CSI-RS resources is equal to or greater than the UE reported threshold beamSwitchTiming + d
in CSI-RS symbols, when the reported value is one of the values of {14,28,48}, or is equal
to or greater than 48+d when the reported value of beamSwitchTiming is one of the values of {224, 336}, the UE
is expected to apply the QCL assumptions in the indicated TCI states for the aperiodic CSI-RS resources in the
CSI triggering state indicated by the CSI trigger field in DCI.
Table 5.2.1.5.1a-1: Additional beam switching timing delay d
µPDCCH d [PDCCH symbols]

0 8
1 8
2 14
Aperiodic CSI-RS timing:
- When the aperiodic CSI-RS is used with aperiodic CSI reporting, the CSI-RS triggering offset X is configured
per resource set by the higher layer parameter aperiodicTriggeringOffset. The CSI-RS triggering offset has the
values of {0, 1,…31} slots when the µPDCCH < µCSIRS and {0, 1, 2, 3, 4, 16, 24} when the µ PDCCH > µCSIRS.. The
3GPP
Release 16 58 3GPP TS 38.214 V16.1.0 (2020-03)
 2 CSIRS   N CA CA
N slot  
 + X +    2 CSIRS  , if
slot ,offset , PDCCH ,offset ,CSIRS
aperiodic CSI-RS is transmitted in a slot  n  −
 2  PDCCH
   offset , PDCCH offset ,CSIRS  
 2 2  
UE is configured with CA-slot-offset for at least one of the triggered and triggering cell, and Ks =
 2 CSIRS 
n   + X , otherwise, and where
 2 PDCCH 
- n is the slot containing the triggering DCI, X is the CSI-RS triggering offset in the numerology of CSI-RS
according to the higher layer parameter aperiodicTriggeringOffset,
- 𝜇𝐶𝑆𝐼𝑅𝑆 and 𝜇𝑃𝐷𝐶𝐶𝐻 are the subcarrier spacing configurations for CSI-RS and PDCCH, respectively,
offset, PDCCH and 𝜇offset,PDCCH are the 𝑁slot, offset and the  offset , respectively, which are determined by
CA CA
- 𝑁slot,
higher-layer configured CA-slot-offset for the cell receiving the PDCCH
offset, CSIRS and 𝜇offset,CSIRS are the 𝑁slot, offset and the  offset , respectively, which are
CA CA
respectively, 𝑁slot,
determined by higher-layer configured CA-slot-offset for the cell transmitting the CSI-RS respectively, as
defined in [4, TS 38.211] clause 4.5
- If the µPDCCH < µCSIRS, the UE is expected to be able to measure the aperiodic CSI RS, if the CSI-RS starts no
earlier than the first symbol of the CSI-RS carrier's slot that starts at least Ncsirs PDCCH symbols after the end
of the PDCCH triggering the aperiodic CSI-RS.
- If the µPDCCH > µCSIRS, the UE is expected to be able to measure the aperiodic CSI RS, if the CSI-RS starts no
earlier than at least Ncsirs PDCCH symbols after the end of the PDCCH triggering the aperiodic CSI-RS.
Table 5.2.1.5.1a: Ncsirs as a function of the subcarrier spacing of the triggering PDCCH
µPDCCH Ncsirs [symbols]

0 4
1 5
2 10
3 [14]
5.2.1.5.2 Semi-persistent CSI/Semi-persistent CSI-RS

For semi-persistent reporting on PUSCH, a set of trigger states are higher layer configured by CSI-
SemiPersistentOnPUSCH-TriggerStateList, where the CSI request field in DCI scrambled with SP-CSI-RNTI activates
one of the trigger states. A UE is not expected to receive a DCI scrambled with SP-CSI-RNTI activating one semi-
persistent CSI report with the same CSI-ReportConfigId as in a semi-persistent CSI report which is activated by a
previously received DCI scrambled with SP-CSI-RNTI.
For semi-persistent reporting on PUCCH, the PUCCH resource used for transmitting the CSI report are configured by
reportConfigType. Semi-persistent reporting on PUCCH is activated by an activation command as described in clause
6.1.3.16 of [10, TS 38.321], which selects one of the semi-persistent Reporting Settings for use by the UE on the
PUCCH. When the UE would transmit a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH
carrying the activation command, the indicated semi-persistent Reporting Setting should be applied starting from the
first slot that is after slot 𝑛 + 3𝑁𝑠𝑙𝑜𝑡
For a UE configured with CSI resource setting(s) where the higher layer parameter resourceType set to 'semiPersistent'.
- when a UE receives an activation command, as described in clause 6.1.3.12 of [10, TS 38.321], for CSI-RS
resource set(s) for channel measurement and CSI-IM/NZP CSI-RS resource set(s) for interference measurement
associated with configured CSI resource setting(s), and when the UE would transmit a PUCCH with HARQ-
ACK information in slot n corresponding to the PDSCH carrying the selection command, the corresponding
actions in [10, TS 38.321] and the UE assumptions (including QCL assumptions provided by a list of reference
to TCI-State's, one per activated resource) on CSI-RS/CSI-IM transmission corresponding to the configured CSI-
RS/CSI-IM resource configuration(s) shall be applied starting from the first slot that is after slot 𝑛 +
where  is the SCS configuration for the PUCCH. If a TCI-State referred to in the list is
3𝑁𝑠𝑙𝑜𝑡
configured with a reference to an RS associated with 'QCL-TypeD', that RS can be an SS/PBCH block, periodic
or semi-persistent CSI-RS located in same or different CC/DL BWP.
3GPP
Release 16 59 3GPP TS 38.214 V16.1.0 (2020-03)
- when a UE receives a deactivation command, as described in clause 6.1.3.12 of [10, TS 38.321], for activated
CSI-RS/CSI-IM resource set(s) associated with configured CSI resource setting(s), and when the UE would
transmit a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH carrying the
deactivation command, the corresponding actions in [10, TS 38.321] and UE assumption on cessation of CSI-
RS/CSI-IM transmission corresponding to the deactivated CSI-RS/CSI-IM resource set(s) shall apply starting
from the first slot that is after slot 𝑛 + 3𝑁𝑠𝑙𝑜𝑡
A codepoint of the CSI request field in the DCI is mapped to a SP-CSI triggering state according to the order of the
positions of the configured trigger states in CSI-SemiPersistentOnPUSCH-TriggerStateList, with codepoint '0' mapped
to the triggering state in the first position. A UE validates, for semi-persistent CSI activation or release, a DL semi-
persistent assignment PDCCH on a DCI only if the following conditions are met:
- the CRC parity bits of the DCI format are scrambled with a SP-CSI-RNTI provided by higher layer parameter
sp-CSI-RNTI
- Special fields for the DCI format are set according to Table 5.2.1.5.2-1 or Table 5.2.1.5.2-2.
If validation is achieved, the UE considers the information in the DCI format as a valid activation or valid release of
semi-persistent CSI transmission on PUSCH, and the UE activates or deactivates a CSI Reporting Setting indicated by
CSI request field in the DCI. If validation is not achieved, the UE considers the DCI format as having been detected
with a non-matching CRC.
Table 5.2.1.5.2-1: Special fields for semi-persistent CSI activation PDCCH validation
DCI format 0_1/0_2

HARQ process number set to all '0's
Redundancy version set to all '0's
Table 5.2.1.5.2-2: Special fields for semi-persistent CSI deactivation PDCCH validation
DCI format 0_1/0_2

HARQ process number set to all '0's
Modulation and coding scheme set to all '1's
If higher layer configures RA type 0 only, set to all '0's;
If higher layer configures RA type 1 only, set to all '1's;
Resource block assignment
If higher layer configures dynamic switch between RA type 0 and 1,
then if MSB is'0', set to all '0's; else, set to all '1's
Redundancy version set to all '0's
If the UE has an active semi-persistent CSI-RS/CSI-IM resource configuration, or an active semi-persistent ZP CSI-RS
resource set configuration, and has not received a deactivation command, the activated semi-persistent CSI-RS/CSI-IM
resource set or the activated semi-persistent ZP CSI-RS resource set configurations are considered to be active when the
corresponding DL BWP is active, otherwise they are considered suspended.
If the UE is configured with carrier deactivation, the following configurations in the carrier in activated state would also
be deactivated and need re-activation configuration(s): semi-persistent CSI-RS/CSI- IM resource, semi-persistent CSI
reporting on PUCCH, semi-persistent SRS, semi-persistent ZP CSI-RS resource set.
5.2.1.6 CSI processing criteria

The UE indicates the number of supported simultaneous CSI calculations 𝑁𝐶𝑃𝑈 . If a UE supports 𝑁𝐶𝑃𝑈 simultaneous
CSI calculations it is said to have 𝑁𝐶𝑃𝑈 CSI processing units for processing CSI reports across all configured cells. If L
CPUs are occupied for calculation of CSI reports in a given OFDM symbol, the UE has 𝑁𝐶𝑃𝑈 − 𝐿 unoccupied CPUs. If
N CSI reports start occupying their respective CPUs on the same OFDM symbol on which 𝑁𝐶𝑃𝑈 − 𝐿 CPUs are
(𝑛)
unoccupied, where each CSI report 𝑛 = 0, … , 𝑁 − 1 corresponds to 𝑂𝐶𝑃𝑈 , the UE is not required to update the 𝑁 − 𝑀
requested CSI reports with lowest priority (according to Clause 5.2.5), where 0 ≤ 𝑀 ≤ 𝑁 is the largest value such that
(𝑛)
∑𝑀−1
𝑛=0 𝑂𝐶𝑃𝑈 ≤ 𝑁𝐶𝑃𝑈 − 𝐿 holds.
A UE is not expected to be configured with an aperiodic CSI trigger state containing more than 𝑁𝐶𝑃𝑈 Reporting
Settings.Processing of a CSI report occupies a number of CPUs for a number of symbols as follows:
3GPP
Release 16 60 3GPP TS 38.214 V16.1.0 (2020-03)
- 𝑂𝐶𝑃𝑈 = 0 for a CSI report with CSI-ReportConfig with higher layer parameter reportQuantity set to 'none' and
CSI-RS-ResourceSet with higher layer parameter trs-Info configured
- 𝑂𝐶𝑃𝑈 = 1 for a CSI report with CSI-ReportConfig with higher layer parameter reportQuantity set to 'cri-RSRP',
'ssb-Index-RSRP', 'cri-SINR', 'ssb-Index-SINR' or 'none' (and CSI-RS-ResourceSet with higher layer parameter
trs-Info not configured)
- for a CSI report with CSI-ReportConfig with higher layer parameter reportQuantity set to 'cri-RI-PMI-CQI', 'cri-
RI-i1', 'cri-RI-i1-CQI', 'cri-RI-CQI', or 'cri-RI-LI-PMI-CQI',
- if a CSI report is aperiodically triggered without transmitting a PUSCH with either transport block or HARQ-
ACK or both when L = 0 CPUs are occupied, where the CSI corresponds to a single CSI with wideband
frequency-granularity and to at most 4 CSI-RS ports in a single resource without CRI report and where
codebookType is set to 'typeI-SinglePanel' or where reportQuantity is set to 'cri-RI-CQI', 𝑂𝐶𝑃𝑈 = 𝑁𝐶𝑃𝑈 ,
- otherwise, 𝑂𝐶𝑃𝑈 = 𝐾𝑠 , where 𝐾𝑠 is the number of CSI-RS resources in the CSI-RS resource set for channel
measurement.
For a CSI report with CSI-ReportConfig with higher layer parameter reportQuantity not set to 'none', the CPU(s) are
occupied for a number of OFDM symbols as follows:
- A periodic or semi-persistent CSI report (excluding an initial semi-persistent CSI report on PUSCH after the
PDCCH triggering the report) occupies CPU(s) from the first symbol of the earliest one of each CSI-RS/CSI-
IM/SSB resource for channel or interference measurement, respective latest CSI-RS/CSI-IM/SSB occasion no
later than the corresponding CSI reference resource, until the last symbol of the PUSCH/PUCCH carrying the
report.
- An aperiodic CSI report occupies CPU(s) from the first symbol after the PDCCH triggering the CSI report until
the last symbol of the PUSCH carrying the report.
- An initial semi-persistent CSI report on PUSCH after the PDCCH trigger occupies CPU(s) from the first symbol
after the PDCCH until the last symbol of the PUSCH carrying the report.
For a CSI report with CSI-ReportConfig with higher layer parameter reportQuantity set to 'none' and CSI-RS-
ResourceSet with higher layer parameter trs-Info is not configured, the CPU(s) are occupied for a number of OFDM
symbols as follows:
- A semi-persistent CSI report (excluding an initial semi-persistent CSI report on PUSCH after the PDCCH
triggering the report) occupies CPU(s) from the first symbol of the earliest one of each transmission occasion of
periodic or semi-persistent CSI-RS/SSB resource for channel measurement for L1-RSRP computation, until 𝑍3′
symbols after the last symbol of the latest one of the CSI-RS/SSB resource for channel measurement for L1-
RSRP computation in each transmission occasion.
- An aperiodic CSI report occupies CPU(s) from the first symbol after the PDCCH triggering the CSI report until
the last symbol between 𝑍3 symbols after the first symbol after the PDCCH triggering the CSI report and 𝑍3′
symbols after the last symbol of the latest one of each CSI-RS/SSB resource for channel measurement for L1-
RSRP computation.
where (𝑍3 , 𝑍3′ ) are defined in the table 5.4-2.
In any slot, the UE is not expected to have more active CSI-RS ports or active CSI-RS resources than reported as
capability. NZP CSI-RS resource is active in a duration of time defined as follows. For aperiodic CSI-RS, starting from
the end of the PDCCH containing the request and ending at the end of the PUSCH containing the report associated with
this aperiodic CSI-RS. For semi-persistent CSI-RS, starting from the end of when the activation command is applied,
and ending at the end of when the deactivation command is applied. For periodic CSI-RS, starting when the periodic
CSI-RS is configured by higher layer signalling, and ending when the periodic CSI-RS configuration is released. If a
CSI-RS resource is referred by N CSI reporting settings, the CSI-RS resource and the CSI-RS ports within the CSI-RS
resource are counted N times.
3GPP
Release 16 61 3GPP TS 38.214 V16.1.0 (2020-03)
5.2.2 Channel state information

5.2.2.1 Channel quality indicator (CQI)
The CQI indices and their interpretations are given in Table 5.2.2.1-2 or Table 5.2.2.1-4 for reporting CQI based on
QPSK, 16QAM and 64QAM. The CQI indices and their interpretations are given in Table 5.2.2.1-3 for reporting CQI
based on QPSK, 16QAM, 64QAM and 256QAM.
Based on an unrestricted observation interval in time unless specified otherwise in this Clause, and an unrestricted
observation interval in frequency, the UE shall derive for each CQI value reported in uplink slot n the highest CQI
index which satisfies the following condition:
- A single PDSCH transport block with a combination of modulation scheme, target code rate and transport block
size corresponding to the CQI index, and occupying a group of downlink physical resource blocks termed the
CSI reference resource, could be received with a transport block error probability not exceeding:
- 0.1, if the higher layer parameter cqi-Table in CSI-ReportConfig configures 'table1' (corresponding to Table
5.2.2.1-2), or 'table2' (corresponding to Table 5.2.2.1-3), or
- 0.00001, if the higher layer parameter cqi-Table in CSI-ReportConfig configures 'table3' (corresponding to
Table 5.2.2.1-4).
If a UE is not configured with higher layer parameter timeRestrictionForChannelMeasurements, the UE shall derive the
channel measurements for computing CSI value reported in uplink slot n based on only the NZP CSI-RS, no later than
the CSI reference resource, (defined in TS 38.211[4]) associated with the CSI resource setting.
If a UE is configured with higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig, the

UE shall derive the channel measurements for computing CSI reported in uplink slot n based on only the most recent,
no later than the CSI reference resource, occasion of NZP CSI-RS (defined in [4, TS 38.211]) associated with the CSI
resource setting.
If a UE is not configured with higher layer parameter timeRestrictionForInterferenceMeasurements, the UE shall derive
the interference measurements for computing CSI value reported in uplink slot n based on only the CSI-IM and/or NZP
CSI-RS for interference measurement no later than the CSI reference resource associated with the CSI resource setting.
If a UE is configured with higher layer parameter timeRestrictionForInterferenceMeasurements in CSI-ReportConfig,

the UE shall derive the interference measurements for computing the CSI value reported in uplink slot n based on the
most recent, no later than the CSI reference resource, occasion of CSI-IM and/or NZP CSI-RS for interference
measurement (defined in [4, TS 38.211]) associated with the CSI resource setting.
For each sub-band index s, a 2-bit sub-band differential CQI is defined as:
- Sub-band Offset level (s) = sub-band CQI index (s) - wideband CQI index.
The mapping from the 2-bit sub-band differential CQI values to the offset level is shown in Table 5.2.2.1-1
Table 5.2.2.1-1: Mapping sub-band differential CQI value to offset level
Sub-band differential CQI value Offset level

0 0
1 1
2 ≥2
3 ≤-1
A combination of modulation scheme and transport block size corresponds to a CQI index if:
- the combination could be signaled for transmission on the PDSCH in the CSI reference resource according to the
Transport Block Size determination described in Clause 5.1.3.2, and
- the modulation scheme is indicated by the CQI index, and
- the combination of transport block size and modulation scheme when applied to the reference resource results in
the effective channel code rate which is the closest possible to the code rate indicated by the CQI index. If more
than one combination of transport block size and modulation scheme results in an effective channel code rate
3GPP
Release 16 62 3GPP TS 38.214 V16.1.0 (2020-03)
equally close to the code rate indicated by the CQI index, only the combination with the smallest of such
transport block sizes is relevant.
Table 5.2.2.1-2: 4-bit CQI Table
CQI index modulation code rate x 1024 efficiency

0 out of range
1 QPSK 78 0.1523
2 QPSK 120 0.2344
3 QPSK 193 0.3770
4 QPSK 308 0.6016
5 QPSK 449 0.8770
6 QPSK 602 1.1758
7 16QAM 378 1.4766
8 16QAM 490 1.9141
9 16QAM 616 2.4063
10 64QAM 466 2.7305
11 64QAM 567 3.3223
12 64QAM 666 3.9023
13 64QAM 772 4.5234
14 64QAM 873 5.1152
15 64QAM 948 5.5547
Table 5.2.2.1-3: 4-bit CQI Table 2

0 out of range
1 QPSK 78 0.1523
2 QPSK 193 0.3770
3 QPSK 449 0.8770
4 16QAM 378 1.4766
5 16QAM 490 1.9141
6 16QAM 616 2.4063
7 64QAM 466 2.7305
8 64QAM 567 3.3223
9 64QAM 666 3.9023
10 64QAM 772 4.5234
11 64QAM 873 5.1152
12 256QAM 711 5.5547
13 256QAM 797 6.2266
14 256QAM 885 6.9141
15 256QAM 948 7.4063
3GPP
Release 16 63 3GPP TS 38.214 V16.1.0 (2020-03)
Table 5.2.2.1-4: 4-bit CQI Table 3

0 out of range
1 QPSK 30 0.0586
2 QPSK 50 0.0977
3 QPSK 78 0.1523
4 QPSK 120 0.2344
5 QPSK 193 0.3770
6 QPSK 308 0.6016
7 QPSK 449 0.8770
8 QPSK 602 1.1758
9 16QAM 378 1.4766
10 16QAM 490 1.9141
11 16QAM 616 2.4063
12 64QAM 466 2.7305
13 64QAM 567 3.3223
14 64QAM 666 3.9023
15 64QAM 772 4.5234
5.2.2.1.1 (void)
5.2.2.2 Precoding matrix indicator (PMI)

5.2.2.2.1 Type I Single-Panel Codebook
For 2 antenna ports {3000, 3001} and the UE configured with higher layer parameter codebookType set to 'typeI-
SinglePanel' each PMI value corresponds to a codebook index given in Table 5.2.2.2.1-1. The UE is configured with the
higher layer parameter twoTX-CodebookSubsetRestriction. The bitmap parameter twoTX-CodebookSubsetRestriction
forms the bit sequence a5 ,..., a1 , a0 where a0 is the LSB and a5 is the MSB and where a bit value of zero indicates
that PMI reporting is not allowed to correspond to the precoder associated with the bit. Bits 0 to 3 are associated
respectively with the codebook indices 0 to 3 for  = 1 layer, and bits 4 and 5 are associated respectively with the
codebook indices 0 and 1 for  = 2 layers.
Table 5.2.2.2.1-1: Codebooks for 1-layer and 2-layer CSI reporting using antenna ports 3000 to 3001
Codebook Number of layers 

index 1 2
1 1 1 1 1 
0   
2 1 2 1 −1
1 1  1 1 1 
1    − j 
2  j 2j
1 1
2   -
2  −1
1  1 
3   -
2 − j 
For 4 antenna ports {3000, 3001, 3002, 3003}, 8 antenna ports {3000, 3001, …, 3007}, 12 antenna ports {3000, 3001,
…, 3011}, 16 antenna ports {3000, 3001, …, 3015}, 24 antenna ports {3000, 3001, …, 3023}, and 32 antenna ports
{3000, 3001, …, 3031}, and the UE configured with higher layer parameter codebookType set to 'typeI-SinglePanel',
except when the number of layers   2,3, 4 (where  is the associated RI value), each PMI value corresponds to
three codebook indices i1,1 , i1,2 , i2 . When the number of layers   2,3, 4 , each PMI value corresponds to four
codebook indices i1,1 , i1,2 , i1,3 , i2 . The composite codebook index i1 is defined by
3GPP
Release 16 64 3GPP TS 38.214 V16.1.0 (2020-03)
 i1,1 i1,2    2,3, 4

i1 = 
 i1,1 i1,2 i1,3    2,3, 4
The codebooks for 1-8 layers are given respectively in Tables 5.2.2.2.1-5, 5.2.2.2.1-6, 5.2.2.2.1-7, 5.2.2.2.1-8, 5.2.2.2.1-
9, 5.2.2.2.1-10, 5.2.2.2.1-11, and 5.2.2.2.1-12. The mapping from i1,3 to k1 and k2 for 2-layer reporting is given in
Table 5.2.2.2.1-3. The mapping from i1,3 to k1 and k2 for 3-layer and 4-layer reporting when PCSI-RS  16 is given in
Table 5.2.2.2.1-4. The quantities  n ,  p , um , vl , m , and vl ,m are given by
n = e j n 2
 p = e j p 4
 j
2 m
j
2 m ( N 2 −1) 
 1 e O2 N 2 e O2 N 2  N2 1
um =   
 
 1 N2 =1
2 l 2 l ( N1 −1) T
 j j 
vl ,m =  um e O1 N1
um e O1 N1
um 
 
 
4 l 4 l ( N1 2 −1) T
 j j 
vl ,m =  um e O1 N1
um e O1 N1
um 
 
 
- The values of N 1 and N 2 are configured with the higher layer parameter n1-n2, respectively. The supported
configurations of (N1 , N 2 ) for a given number of CSI-RS ports and the corresponding values of ( O1 , O2 ) are
given in Table 5.2.2.2.1-2. The number of CSI-RS ports, PCSI-RS , is 2 N1 N 2 .
- UE shall only use i1,2 = 0 and shall not report i1,2 if the value of N2 is 1.
The bitmap parameter n1-n2 forms the bit sequence a A −1 ,..., a1 , a0 where a0 is the LSB and a A −1 is the MSB and
c c
where a bit value of zero indicates that PMI reporting is not allowed to correspond to any precoder associated with the
bit. The number of bits is given by Ac = N1O1 N 2O2 . Except when the number of layers   3, 4 and the number of
antenna ports is 16, 24, or 32, bit aN O l + m is associated with all precoders based on the quantity vl ,m ,
2 2
l = 0, , N1O1 − 1 , m = 0, , N 2O2 − 1 . When the number of layers   3, 4 and the number of antenna ports is 16,
24, or 32,
- bits a( N 2O2 ( 2l −1) + m ) mod N1O1 N 2O2 , aN2O2 ( 2l )+ m , and aN2O2 ( 2l +1)+ m are each associated with all precoders based on the
quantity vl ,m , l = 0, , N1O1 2 − 1 , m = 0, , N 2O2 − 1 ;
- if one or more of the associated bits is zero, then PMI reporting is not allowed to correspond to any precoder
based on vl ,m .
For UE configured with higher layer parameter codebookType set to 'typeI-SinglePanel', the bitmap parameter typeI-
SinglePanel-ri‑Restriction forms the bit sequence r7 ,..., r1 , r0 where r0 is the LSB and r7 is the MSB. When ri is zero,
i  0,1, , 7 , PMI and RI reporting are not allowed to correspond to any precoder associated with  = i + 1 layers.
For UE configured with higher layer parameter reportQuantity set to 'cri-RI-i1-CQI', the bitmap parameter typeI-
SinglePanel-codebookSubsetRestriction-i2 forms the bit sequence 𝑏15 , …,𝑏1 , 𝑏0 where 𝑏0 is the LSB and 𝑏15 is the
MSB. The bit 𝑏𝑖 is associated with precoders corresponding to codebook index 𝑖2 = 𝑖. When 𝑏𝑖 is zero, the randomly
selected precoder for CQI calculation is not allowed to correspond to any precoder associated with the bit 𝑏𝑖 .
3GPP
Release 16 65 3GPP TS 38.214 V16.1.0 (2020-03)
Table 5.2.2.2.1-2: Supported configurations of (N1 , N 2 ) and (O1 ,O2 )
Number of
CSI-RS antenna ports, PCSI-RS
(N1, N 2 ) (O1,O2 )
4 (2,1) (4,1)
(2,2) (4,4)
8
(4,1) (4,1)
(3,2) (4,4)
12
(6,1) (4,1)
(4,2) (4,4)
16
(8,1) (4,1)
(4,3) (4,4)
24 (6,2) (4,4)
(12,1) (4,1)
(4,4) (4,4)
32 (8,2) (4,4)
(16,1) (4,1)
Table 5.2.2.2.1-3: Mapping of i1,3 to k1 and k2 for 2-layer CSI reporting
N1  N 2  1 N1 = N 2 N1 = 2, N 2 = 1 N1  2, N 2 = 1
i1,3
k1 k2 k1 k2 k1 k2 k1 k2
0 0 0 0 0 0 0 0 0
1 O1 0 O1 0 O1 0 O1 0
2 0 O2 0 O2 2O1 0
3 2O1 0 O1 O2 3O1 0
Table 5.2.2.2.1-4: Mapping of i1,3 to k1 and k2 for 3-layer and 4-layer CSI reporting when PCSI-RS  16
N1 = 2, N 2 = 1 N1 = 4, N 2 = 1 N1 = 6, N 2 = 1 N1 = 2, N 2 = 2 N1 = 3, N 2 = 2
i1,3
k1 k2 k1 k2 k1 k2 k1 k2 k1 k2
0 O1 0 O1 0 O1 0 O1 0 O1 0
1 2O1 0 2O1 0 0 O2 0 O2
2 3O1 0 3O1 0 O1 O2 O1 O2
3 4O1 0 2O1 0
Table 5.2.2.2.1-5: Codebook for 1-layer CSI reporting using antenna ports 3000 to 2999+PCSI-RS
codebookMode = 1
i1,1 i1,2 i2
0,1, , N1O1 − 1 0, , N 2O2 − 1 0,1,2,3 Wi(1),i ,i2
1,1 1,2
1  vl ,m 
where Wl ,m,n =
(1)
 v  .
PCSI-RS  n l ,m 
3GPP
Release 16 66 3GPP TS 38.214 V16.1.0 (2020-03)
codebookMode = 2, N 2  1
i2
i1,1 i1,2
0 1 2 3
NO N O
0,1,..., 1 1 − 1 0,1,..., 2 2 − 1 W2(i1) ,2i ,0 W2(i1) ,2i ,1 W2(i1) ,2i ,2 W2(i1) ,2i ,3
2 2 1,1 1, 2 1,1 1, 2 1,1 1, 2 1,1 1, 2
i2
i1,1 i1,2
4 5 6 7
NO N O
0,1,..., 1 1 − 1 0,1,..., 2 2 − 1 W2(i1) +1,2i ,0 W2(i1) +1,2i ,1 W2(i1) +1,2i ,2 W2(i1) +1,2i ,3
2 2 1,1 1, 2 1,1 1, 2 1,1 1, 2 1,1 1, 2
i2
i1,1 i1,2
8 9 10 11
NO N O
0,1,..., 1 1 − 1 0,1,..., 2 2 − 1 W2(i1) ,2i +1,0 W2(i1) ,2i +1,1 W2(i1) ,2i +1,2 W2(i1) ,2i +1,3
2 2 1,1 1, 2 1,1 1, 2 1,1 1, 2 1,1 1, 2
i2
i1,1 i1,2
12 13 14 15
NO N O
0,1,..., 1 1 − 1 0,1,..., 2 2 − 1 W2(i1) +1,2i +1,0 W2(i1) +1,2i +1,1 W2(i1) +1,2i +1,2 W2(i1) +1,2i +1,3
2 2 1,1 1, 2 1,1 1, 2 1,1 1, 2 1,1 1, 2
1  vl ,m 
where Wl ,m,n =
(1)
 v  .
codebookMode = 2, N 2 = 1
i2
i1,1 i1,2
0 1 2 3
NO
0,1,..., 1 1 − 1 0 W2(1)i ,0,0 W2(1)i ,0,1 W2(1)i ,0,2 W2(1)i ,0,3
2 1,1 1,1 1,1 1,1
i2
i1,1 i1,2
4 5 6 7
NO
0,1,..., 1 1 − 1 0 W2(1)
i1,1 +1,0,0 W2(1)
i1,1 +1,0,1 W2(1)
i1,1 +1,0,2 W2(1)i +1,0,3
2 1,1
i2
i1,1 i1,2
8 9 10 11
NO
0,1,..., 1 1 − 1 0 W2(1)
i1,1 + 2,0,0 W2(1)
i1,1 + 2,0,1 W2(1)
i1,1 + 2,0,2 W2(1)
i1,1 + 2,0,3
2
i2
i1,1 i1,2
12 13 14 15
NO
0,1,..., 1 1 − 1 0 W2(1)
i1,1 +3,0,0 W2(1)i +3,0,1 W2(1)
i1,1 +3,0,2 W2(1)
i1,1 +3,0,3
2 1,1
1  vl ,m 
where Wl ,m,n =
(1)
 v  .
codebookMode = 1
i1,1 i1,2 i2
0,1, , N1O1 − 1 0, , N 2O2 − 1 0,1 Wi(2),i + k1 ,i1,2 ,i1,2 + k2 ,i2
1,1 1,1
1  vl ,m vl  ,m 
where Wl ,l ' ,m,m' ,n =
(2)
 .
2 PCSI-RS n vl ,m −n vl  ,m 
and the mapping from i1,3 to k1 and k2 is given in Table 5.2.2.2.1-3.
3GPP
Release 16 67 3GPP TS 38.214 V16.1.0 (2020-03)
codebookMode = 2, N 2  1
i2
i1,1 i1,2
0 1
NO N O
0, , 1 1 − 1 0, , 2 2 −1 W2(2)
i1,1 ,2i1,1 + k1 ,2i1,2 ,2i1,2 + k2 ,0 W2(2)
i1,1 ,2i1,1 + k1 ,2i1,2 ,2i1,2 + k2 ,1
2 2
i2
i1,1 i1,2
2 3
NO N O
0, , 1 1 − 1 0, , 2 2 −1 W2(2)
i1,1 +1,2i1,1 +1+ k1 ,2i1,2 ,2i1,2 + k2 ,0 W2(2)
i1,1 +1,2i1,1 +1+ k1 ,2i1,2 ,2i1,2 + k2 ,1
2 2
i2
i1,1 i1,2
4 5
NO N O
0, , 1 1 − 1 0, , 2 2 −1 W2(2)
i1,1 ,2i1,1 + k1 ,2i1,2 +1,2i1,2 +1+ k2 ,0 W2(2)
i1,1 ,2i1,1 + k1 ,2i1,2 +1,2i1,2 +1+ k2 ,1
2 2
i2
i1,1 i1,2
6 7
NO N O
0, , 1 1 − 1 0, , 2 2 −1 W2(2)
i1,1 +1,2i1,1 +1+ k1 ,2i1,2 +1,2i1,2 +1+ k2 ,0 W2(2)
i1,1 +1,2i1,1 +1+ k1 ,2i1,2 +1,2i1,2 +1+ k2 ,1
2 2
 vl ,m
1 vl  ,m 
(2)
 .
2 PCSI-RS n vl ,m −n vl  ,m 
codebookMode = 2, N 2 = 1
i2
i1,1 i1,2
0 1 2 3
N1O1
0, , −1 0 W2(2)
i ,2i + k1 ,0,0,0 W2(2)
i ,2i + k1 ,0,0,1 W2(2)
i +1,2i +1+ k1 ,0,0,0 W2(2)
i +1,2i +1+ k1 ,0,0,1
2 1,1 1,1 1,1 1,1 1,1 1,1 1,1 1,1
i2
i1,1 i1,2
4 5 6 7
NO
0, , 1 1 − 1 0 W2(2)
i + 2,2i
1,1 1,1 + 2+ k1 ,0,0,0 W2(2)
i + 2,2i + 2+ k1 ,0,0,1 W2(2)
i +3,2i +3+ k1 ,0,0,0 W2(2)
i +3,2i +3+ k1 ,0,0,1
2 1,1 1,1 1,1 1,1 1,1 1,1
1  vl ,m vl  ,m 
(2)
 .
2 PCSI-RS n vl ,m −n vl  ,m 
and the mapping from i1,3 to k1 is given in Table 5.2.2.2.1-3.
codebookMode = 1-2, PCSI-RS  16

i1,1 i1,2 i2
0, , N1O1 − 1 0,1, , N 2O2 − 1 0,1 Wi(3),i + k1 ,i1,2 ,i1,2 + k2 ,i2
1,1 1,1
1  vl ,m vl ,m vl ,m 
where Wl ,l ,m,m.n =
(3)
 .
3PCSI-RS n vl ,m n vl ,m −n vl ,m 
3GPP
Release 16 68 3GPP TS 38.214 V16.1.0 (2020-03)
codebookMode = 1-2, PCSI-RS  16

i1,1 i1,2 i1,3 i2
N1O1
0, , −1 0, , N 2O2 − 1 0,1,2,3 0,1 Wi(3),i ,i ,i
2 1,1 1,2 1,3 2
 vl ,m vl ,m vl ,m
 
1   p vl ,m − p vl ,m  p vl ,m 
where Wl ,m, p, n =
(3)
  v n vl ,m −n vl ,m 
.
3PCSI-RS  n l ,m 
n p vl ,m −n p vl ,m −n p vl ,m 

codebookMode = 1-2, PCSI-RS  16

i1,1 i1,2 i2
0, , N1O1 − 1 0,1, , N 2O2 − 1 0,1 Wi(4),i + k1 ,i1,2 ,i1,2 + k2 ,i2
1,1 1,1
 vl ,m 1vl ,m vl ,m vl ,m 

where Wl ,l ,m,m.n =
(4)
 .
4 PCSI-RS n vl ,m n vl ,m −n vl ,m −n vl ,m 
codebookMode = 1-2, PCSI-RS  16

i1,1 i1,2 i1,3 i2
N1O1
0, , −1 0, , N 2O2 − 1 0,1,2,3 0,1 Wi(4),i ,i ,i
2 1,1 1,2 1,3 2
 vl ,m vl ,m vl ,m vl ,m 
 
1   p vl ,m − p vl ,m  p vl ,m − p vl ,m 
where Wl ,m, p, n =
(4)
  v n vl ,m −n vl ,m −n vl ,m 
.
4 PCSI-RS  n l ,m 
n p vl ,m −n p vl ,m −n p vl ,m n p vl ,m 

codebookMode = 1-2
i1,1 i1,2 i2
N2  1 0, , N1O1 − 1 0, , N 2O2 − 1 0,1 Wi(5),i +O1 ,i1,1 +O1 ,i1,2 ,i1,2 ,i1,2 +O2 ,i2
1,1 1,1
N1  2, N 2 = 1 0, , N1O1 − 1 0 0,1 Wi(5),i +O ,i +2O ,0,0,0,i

1,1 1,1 1 1,1 1 2
1  vl ,m vl ,m vl ,m vl ,m vl ,m 

where Wl ,l ,l ,m,m.m, n =
(5)
 .
5PCSI-RS n vl ,m −n vl ,m vl ,m −vl ,m vl ,m 
3GPP
Release 16 69 3GPP TS 38.214 V16.1.0 (2020-03)
codebookMode = 1-2
i1,1 i1,2 i2
N2  1 0, , N1O1 − 1 0, , N 2O2 − 1 0,1 Wi(6),i +O1 ,i1,1 +O1 ,i1,2 ,i1,2 ,i1,2 +O2 ,i2
1,1 1,1
N1  2, N 2 = 1 0, , N1O1 − 1 0 0,1 Wi(6),i +O ,i +2O ,0,0,0,i

1,1 1,1 1 1,1 1 2
1  vl ,m vl ,m vl ,m vl ,m vl ,m vl ,m 

where Wl ,l ,l ,m,m.m,n =
(6)
 .
6 PCSI-RS n vl ,m −n vl ,m n vl ,m −n vl ,m vl ,m −vl ,m 
codebookMode = 1-2
i1,1 i1,2 i2
N1O1
N1 = 4, N 2 = 1 0, , −1 0 0,1 Wi(7),i +O1 ,i1,1 + 2O1 ,i1,1 +3O1 ,0,0,0,0,i2
2 1,1 1,1
N1  4, N 2 = 1 0, , N1O1 − 1 0 0,1 Wi(7),i +O1 ,i1,1 + 2O1 ,i1,1 +3O1 ,0,0,0,0,i2

1,1 1,1
N1 = 2, N 2 = 2 0, , N1O1 − 1 0, , N 2O2 − 1 0,1 Wi(7),i +O ,i ,i +O ,i ,i ,i +O ,i +O ,i

1,1 1,1 1 1,1 1,1 1 1,2 1,2 1,2 2 1,2 2 2
N 2O2
N1  2, N 2 = 2 0, , N1O1 − 1 0, , −1 0,1 Wi(7),i +O1 ,i1,1 ,i1,1 +O1 ,i1,2 ,i1,2 ,i1,2 +O2 ,i1,2 +O2 ,i2
2 1,1 1,1
N1  2, N 2  2 0, , N1O1 − 1 0, , N 2O2 − 1 0,1 Wi(7),i +O1 ,i1,1 ,i1,1 +O1 ,i1,2 ,i1,2 ,i1,2 +O2 ,i1,2 +O2 ,i2
1,1 1,1
1  vl ,m vl ,m vl ,m vl ,m vl ,m vl ,m vl ,m 

where Wl ,l ,l ,l ,m,m.m,m,n =
(7)
 .
7 PCSI-RS n vl ,m −n vl ,m n vl ,m vl ,m −vl ,m vl ,m −vl ,m 
codebookMode = 1-2
i1,1 i1,2 i2
N1O1
N1 = 4, N 2 = 1 0, , −1 0 0,1 Wi(8),i +O1 ,i1,1 + 2O1 ,i1,1 +3O1 ,0,0,0,0,i2
2 1,1 1,1
N1  4, N 2 = 1 0, , N1O1 − 1 0 0,1 Wi(8),i +O1 ,i1,1 + 2O1 ,i1,1 +3O1 ,0,0,0,0,i2

1,1 1,1
N1 = 2, N 2 = 2 0, , N1O1 − 1 0, , N 2O2 − 1 0,1 Wi(8),i +O1 ,i1,1 ,i1,1 +O1 ,i1,2 ,i1,2 ,i1,2 +O2 ,i1,2 +O2 ,i2
1,1 1,1
N 2O2
N1  2, N 2 = 2 0, , N1O1 − 1 0, , −1 0,1 Wi(8),i +O1 ,i1,1 ,i1,1 +O1 ,i1,2 ,i1,2 ,i1,2 +O2 ,i1,2 +O2 ,i2
2 1,1 1,1
N1  2, N 2  2 0, , N1O1 − 1 0, , N 2O2 − 1 0,1 Wi(8),i +O1 ,i1,1 ,i1,1 +O1 ,i1,2 ,i1,2 ,i1,2 +O2 ,i1,2 +O2 ,i2
1,1 1,1
1  vl ,m vl , m vl , m vl ,m vl ,m vl ,m vl ,m vl ,m 

where Wl ,l ,l ,l ,m,m.m,m,n =
(8)
 .
8PCSI-RS n vl ,m −n vl ,m n vl ,m −n vl ,m vl ,m −vl ,m vl ,m −vl ,m 
5.2.2.2.2 Type I Multi-Panel Codebook

For 8 antenna ports {3000, 3001, …, 3007}, 16 antenna ports {3000, 3001, …, 3015}, and 32 antenna ports {3000,
3001, …, 3031}, and the UE configured with higher layer parameter codebookType set to 'typeI-MultiPanel',
3GPP
Release 16 70 3GPP TS 38.214 V16.1.0 (2020-03)
- The values of N g , N 1 and N 2 are configured with the higher layer parameters ng-n1-n2. The supported
( )
configurations of N g , N1 , N2 for a given number of CSI-RS ports and the corresponding values of ( O1 , O2 )
are given in Table 5.2.2.2.2-1. The number of CSI-RS ports, PCSI-RS , is 2 N g N1 N2 .
- When N g = 2 , codebookMode shall be set to either '1' or '2'. When N g = 4 , codebookMode shall be set to '1'.
The bitmap parameter ng-n1-n2 forms the bit sequence a A −1 ,..., a1 , a0 where a0 is the LSB and a A −1 is the MSB and
c c
where a bit value of zero indicates that PMI reporting is not allowed to correspond to any precoder associated with the
bit. The number of bits is given by Ac = N1O1 N 2O2 . Bit aN O l + m is associated with all precoders based on the quantity
2 2
vl ,m , l = 0, , N1O1 − 1 , m = 0, , N 2O2 − 1 , as defined below. The bitmap parameter ri‑Restriction forms the bit
sequence r3 ,..., r1 , r0 where r0 is the LSB and r3 is the MSB. When ri is zero, i  0,1, ,3 , PMI and RI reporting are
not allowed to correspond to any precoder associated with  = i + 1 layers.
(
Table 5.2.2.2.2-1: Supported configurations of N g , N1 , N2 and (O1 ,O2 ) )
Number of
CSI-RS antenna ports, PCSI-RS ( N g , N1, N2 ) (O1,O2 )
8 (2,2,1) (4,1)
(2,4,1) (4,1)
16 (4,2,1) (4,1)
(2,2,2) (4,4)
(2,8,1) (4,1)
(4,4,1) (4,1)
32
(2,4,2) (4,4)
(4,2,2) (4,4)
Each PMI value corresponds to the codebook indices i1 and i2 , where i1 is the vector
i1,1 i1,2 i1,4   =1

i1 = 
 i1,1 i1,2 i1,3 i1,4    2,3, 4
and  is the associated RI value. When codebookMode is set to '1', i1,4 is

 i1,4,1 Ng = 2
i1,4 =  .
i1,4,1 i1,4,2 i1,4,3 
 Ng = 4
When codebookMode is set to '2', i1,4 and i2 are
i1,4 = i1,4,1 i1,4,2 

.
i2 = i2,0 i2,1 i2,2 
The mapping from i1,3 to k1 and k2 for 2-layer reporting is given in Table 5.2.2.2.1-3. The mapping from i1,3 to k1
and k2 for 3-layer and 4-layer reporting is given in Table 5.2.2.2.2-2.
- UE shall only use i1,2 = 0 and shall not report i1,2 if the value of N2 is 1.
3GPP
Release 16 71 3GPP TS 38.214 V16.1.0 (2020-03)
Table 5.2.2.2.2-2: Mapping of i1,3 to k1 and k2 for 3-layer and 4-layer CSI reporting
N1 = 2, N 2 = 1 N1 = 4, N 2 = 1 N1 = 8, N 2 = 1 N1 = 2, N 2 = 2 N1 = 4, N 2 = 2
i1,3
k1 k2 k1 k2 k1 k2 k1 k2 k1 k2
0 O1 0 O1 0 O1 0 O1 0 O1 0
1 2O1 0 2O1 0 0 O2 0 O2
2 3O1 0 3O1 0 O1 O2 O1 O2
3 4O1 0 2O1 0
Several quantities are used to define the codebook elements. The quantities  n , a p , bn , um , and vl , m are given by
n = e j n 2
a p = e j 4 e j p 2
bn = e− j 4 e j n 2
 j
2 m
j
2 m ( N 2 −1) 
 
1 e
O2 N 2
e O2 N 2  N2 1
um =   
 

 1 N2 =1
2 l 2 l ( N1 −1) T
 j j 
vl , m =  um e O1 N1
um e O1 N1
um 
 
 
1, N ,1
Furthermore, the quantities Wl ,m, gp,n and Wl ,m, pg ,n ( N g
2, N ,1
 2, 4 ) are given by
 vl , m   vl ,m 
  v   − v 
1  n l ,m  1  n l ,m 
, m, p , n =
Wl1,2,1   p vl , m  Wl , m, p , n =
2,2,1
PCSI-RS PCSI-RS   p1 vl ,m 
 1
  
 n p1 vl ,m   −n p1 vl ,m 
 vl , m   vl , m 
  v   − v 
 n l ,m   n l ,m 
  p vl , m    p1 vl ,m 
 1
  
1   n p1 vl , m  1  − n p1 vl ,m 
, m, p , n =
Wl1,4,1   Wl 2,4,1
, m, p , n =
 
PCSI-RS   p2 vl , m  PCSI-RS   p2 vl ,m 
  v   −  v 
 n p2 l , m   n p2 l ,m 
  v    p3 vl ,m 
 p3 l , m
  
n p3 vl , m   −n p3 vl ,m 
   
where
 p1 Ng = 2
p= ,
 p1 p2 p3  N g = 4
1, N ,2 2, N ,2
and the quantities Wl ,m, gp,n and Wl ,m, pg ,n ( N g = 2 ) are given by
3GPP
Release 16 72 3GPP TS 38.214 V16.1.0 (2020-03)
 vl , m   vl ,m 
  v   − v 
1  n0 l , m  1  n0 l , m 
,m, p ,n =
Wl1,2,2  a b v  Wl ,m, p ,n =
2,2,2
 a b v 
PCSI-RS  p1 n1 l ,m  PCSI-RS  p1 n1 l ,m 
 a p bn vl ,m   −a p bn vl ,m 
 2 2   2 2 
where
p =  p1 p2 
.
n =  n0 n1 n2 
The codebooks for 1-4 layers are given respectively in Tables 5.2.2.2.2-3, 5.2.2.2.2-4, 5.2.2.2.2-5, and 5.2.2.2.2-6.
codebookMode = 1, N g  2, 4
i1,1 i1,2 i1,4,q , q = 1, , Ng −1 i2
0, , N1O1 − 1 0, , N 2O2 − 1 0,1,2,3 0,1,2,3 Wi(1),i , i ,i

1,1 1,2 1,4 2
1, N g ,1
where , m, p , n = Wl , m, p , n
Wl(1) .
codebookMode = 2, N g = 2
i1,1 i1,2 i1,4,q , q = 1, 2 i2,0 i2,q , q = 1, 2
0, , N1O1 − 1 0, , N 2O2 − 1 0,1,2,3 0,1,2,3 0,1 Wi(1),i , i ,i

1,1 1,2 1,4 2
1, N g ,2
where , m, p , n = Wl , m, p , n
Wl(1) .
i1,1 i1,2 i1,4,q , q = 1, , Ng −1 i2
0, , N1O1 − 1 0, , N 2O2 − 1 0,1,2,3 0,1 Wi(2),i + k1 ,i1,2 ,i1,2 + k2 ,i1,4 ,i2

1,1 1,1
1  1, N g ,1
Wl ,m, p ,n Wl , m,g p , n 
2, N ,1
, l , m , m , p , n =
where Wl(2)
 
2
i1,1 i1,2 i1,4,q , q = 1, 2 i2,q , q = 0,1, 2
0, , N1O1 − 1 0, , N 2O2 − 1 0,1,2,3 0,1 Wi(2),i + k1 ,i1,2 ,i1,2 + k2 ,i1,4 ,i2

1,1 1,1
1  1, N g ,2
Wl ,m, p ,n Wl , m,g p , n 
2, N ,2
, l , m , m , p , n =
where Wl(2)
 
2
3GPP
Release 16 73 3GPP TS 38.214 V16.1.0 (2020-03)
i1,1 i1,2 i1,4,q , q = 1, , Ng −1 i2
0, , N1O1 − 1 0, , N 2O2 − 1 0,1,2,3 0,1 Wi(3),i + k1 ,i1,2 ,i1,2 + k2 ,i1,4 ,i2

1,1 1,1
1  1, N g ,1
Wl ,m, p ,n Wl , mg, p ,n Wl ,m, pg ,n 
1, N ,1 2, N ,1
, l  , m , m , p , n =
where Wl(3)
 
3
i1,1 i1,2 i1,4,q , q = 1, 2 i2,q , q = 0,1, 2
0, , N1O1 − 1 0, , N 2O2 − 1 0,1,2,3 0,1 Wi(3),i + k1 ,i1,2 ,i1,2 + k2 ,i1,4 ,i2

1,1 1,1
1  1, N g ,2
Wl ,m, p ,n Wl , mg, p, n Wl ,m, pg ,n 
1, N ,2 2, N ,2
, l  , m , m , p , n =
where Wl(3)
3 
i1,1 i1,2 i1,4,q , q = 1, , Ng −1 i2
0, , N1O1 − 1 0, , N 2O2 − 1 0,1,2,3 0,1 Wi(4),i + k1 ,i1,2 ,i1,2 + k2 ,i1,4 ,i2

1,1 1,1
1  1, N g ,1
Wl ,m, p ,n Wl ,mg, p ,n Wl ,m, pg ,n Wl ,m,g p ,n 
1, N ,1 2, N ,1 2, N ,1
, l  , m , m , p , n =
where Wl(4)
 
4
i1,1 i1,2 i1,4,q , q = 1, 2 i2,q , q = 0,1, 2
0, , N1O1 − 1 0, , N 2O2 − 1 0,1,2,3 0,1 Wi(4),i + k1 ,i1,2 ,i1,2 + k2 ,i1,4 ,i2

1,1 1,1
1  1, N g ,2
Wl ,m, p ,n Wl ,mg, p ,n Wl ,m, pg ,n Wl ,m,g p ,n 
1, N ,2 2, N ,2 2, N ,2
, l  , m , m , p , n =
where Wl(4)
4 
5.2.2.2.3 Type II Codebook

For 4 antenna ports {3000, 3001, …, 3003}, 8 antenna ports {3000, 3001, …, 3007}, 12 antenna ports {3000, 3001, …,
3011}, 16 antenna ports {3000, 3001, …, 3015}, 24 antenna ports {3000, 3001, …, 3023}, and 32 antenna ports {3000,
3001, …, 3031}, and the UE configured with higher layer parameter codebookType set to 'typeII'
- The values of N 1 and N 2 are configured with the higher layer parameter n1-n2-codebookSubsetRestriction. The
supported configurations of (N1 , N 2 ) for a given number of CSI-RS ports and the corresponding values of
( O1 , O2 ) are given in Table 5.2.2.2.1-2. The number of CSI-RS ports, PCSI-RS , is 2 N1 N 2 .
- The value of L is configured with the higher layer parameter numberOfBeams, where L=2 when PCSI-RS = 4
and L  2,3, 4 when PCSI-RS  4 .
3GPP
Release 16 74 3GPP TS 38.214 V16.1.0 (2020-03)
- The value of N PSK is configured with the higher layer parameter phaseAlphabetSize, where NPSK  4,8 .
- The UE is configured with the higher layer parameter subbandAmplitude set to 'true' or 'false'.
- The UE shall not report RI > 2.
When   2 , where  is the associated RI value, each PMI value corresponds to the codebook indices i1 and i2 where

 i1,1 i1,4,1   =1
i1 =  
i1,2 i1,3,1
 i1,1
 i1,2 i1,3,1 i1,4,1 i1,3,2 i1,4,2   = 2
 i2,1,1  subbandAmplitude = 'false',  = 1 ..


 i2,1,1 i2,1,2  subbandAmplitude = 'false',  = 2
i2 =  
 i2,1,1 i2,2,1  subbandAmplitude = 'true',  = 1
 i2,1,1 i2,2,1 i2,1,2 i2,2,2  subbandAmplitude = 'true',  = 2

The L vectors combined by the codebook are identified by the indices i1,1 and i1,2 , where
i1,1 =  q1 q2 
q1  0,1, , O1 − 1
q2  0,1, , O2 − 1
  N N  
i1, 2  0,1,  ,  1 2  − 1 .
  L  
Let
n1 =  n1(0) , , n1( L −1) 
n2 =  n2(0) , , n2( L −1) 
n1(i )  0,1, , N1 − 1
n2(i )  0,1, , N 2 − 1
and
 x 
  x  y
C ( x, y ) =  y  .
 0 x y

where the values of C ( x, y ) are given in Table 5.2.2.2.3-1.
Then the elements of n1 and n2 are found from i1,2 using the algorithm:
s −1 = 0
for i = 0, , L −1
Find the largest x*  L − 1 − i, , N1 N 2 − 1 − i in Table 5.2.2.2.3-1 such that i1,2 − si −1  C ( x* , L − i )
(
ei = C x* , L − i )
si = si −1 + ei
n( ) = N1 N 2 − 1 − x*
i
n1( ) = n( ) mod N1
i i
3GPP
Release 16 75 3GPP TS 38.214 V16.1.0 (2020-03)
( n( ) − n( ) )
i i
(i ) 1
n2 =
N1
When n1 and n2 are known, i1,2 is found using:
n( ) = N1n2( ) + n1( ) where the indices i = 0,1, , L −1 are assigned such that n(i ) increases as i increases
i i i
( )
L −1
i1,2 =  C N1 N 2 − 1 − n( ) , L − i , where C ( x, y ) is given in Table 5.2.2.2.3-1.
i
i =0
- If N 2 = 1 , q2 = 0 and n2(i ) = 0 for i = 0,1, , L −1 , and q2 is not reported.
- When ( N1 , N2 ) = (2,1) , n1 = 0,1 and n2 = 0, 0 , and i1,2 is not reported.
- When ( N1 , N2 ) = (4,1) and L = 4, n1 = 0,1, 2,3 and n2 = 0, 0, 0, 0 , and i1,2 is not reported.
- When ( N1 , N2 ) = (2, 2) and L = 4, n1 = 0,1, 0,1 and n2 = 0, 0,1,1 , and i1,2 is not reported.
Table 5.2.2.2.3-1: Combinatorial coefficients C ( x, y )
y
1 2 3 4
x
0 0 0 0 0
1 1 0 0 0
2 2 1 0 0
3 3 3 1 0
4 4 6 4 1
5 5 10 10 5
6 6 15 20 15
7 7 21 35 35
8 8 28 56 70
9 9 36 84 126
10 10 45 120 210
11 11 55 165 330
12 12 66 220 495
13 13 78 286 715
14 14 91 364 1001
15 15 105 455 1365
The strongest coefficient on layer l , l = 1, , is identified by i1,3,l 0,1, , 2L − 1 .
The amplitude coefficient indicators i1,4,l and i2,2,l are
i1,4,l =  kl(1) (1)

,0 , kl ,1 , , kl(1) 
,2 L −1 
i2,2,l =  kl(2) (2)

,0 , kl ,1 , , kl(2) 
,2 L −1 
,i  0,1,
kl(1) , 7
,i  0,1
kl(2)
3GPP
Release 16 76 3GPP TS 38.214 V16.1.0 (2020-03)
(1) (1)
for l = 1, , . The mapping from kl ,i to the amplitude coefficient pl ,i is given in Table 5.2.2.2.3-2 and the
(2) (2)
mapping from kl ,i to the amplitude coefficient pl ,i is given in Table 5.2.2.2.3-3. The amplitude coefficients are
represented by
pl(1) =  pl(1) (1)

,0 , pl ,1 , , pl(1) 
,2 L −1 
pl(2) =  pl(2) (2)

,0 , pl ,1 , , pl(2) 
,2 L −1 
for l = 1, , .
(1) (1)
Table 5.2.2.2.3-2: Mapping of elements of i1,4,l : kl ,i to pl ,i
kl(1)
,i pl(1)
,i
0 0
1 1 64
2 1 32
3 1 16
4 18
5 14
6 12
7 1
(2) (2)
Table 5.2.2.2.3-3: Mapping of elements of i2,2,l : kl ,i to pl ,i
kl(2)
,i pl(2)
,i
0 12
1 1
The phase coefficient indicators are
i2,1,l = cl ,0 , cl ,1 , , cl ,2 L −1 
for l = 1, , .
The amplitude and phase coefficient indicators are reported as follows:
- The indicators kl ,i
(1)
,i1,3,l = 1 , and l ,i 1,3,l
= 7 , kl(2) c = 0 ( l = 1, , ). kl(1) (2)
c
,i1,3,l , kl ,i1,3,l , and l ,i1,3,l are not reported for
1,3,l
l = 1, , .
2 L − 1 elements of , ) are reported, where kl ,i  0,1, , 7 . Let M l (

(1)
- The remaining i1,4,l ( l = 1,
, ) be the number of elements of i1,4,l that satisfy kl ,i  0 .

(1)
l = 1,
- The remaining 2 L − 1 elements of i2,1,l and i2,2,l ( l = 1, , ) are reported as follows:
3GPP
Release 16 77 3GPP TS 38.214 V16.1.0 (2020-03)
- When subbandAmplitude is set to 'false',
- ,i = 1 for l = 1, , , and i = 0,1, ,2L −1 . i2,2,l is not reported for l = 1, , .

kl(2)
, , the elements of i2,1,l corresponding to the coefficients that satisfy kl ,i  0 , i  i1,3,l , as

(1)
- For l = 1,
determined by the reported elements of i1,4,l , are reported, where cl ,i 0,1, , NPSK − 1 and the
remaining 2 L − M l elements of i2,1,l are not reported and are set to cl ,i = 0 .
- When subbandAmplitude is set to 'true',
- For l = 1, ( )
, , the elements of i2,2,l and i2,1,l corresponding to the min M l , K (2) − 1 strongest
coefficients (excluding the strongest coefficient indicated by i1,3,l ), as determined by the corresponding
reported elements of i1,4,l , are reported, where kl ,i  0,1 and cl ,i 0,1,

(2)
, NPSK − 1 . The values of
( )
K (2) are given in Table 5.2.2.2.3-4. The remaining 2 L − min M l , K (2) elements of i2,2,l are not
reported and are set to kl(2)

,i ( )
= 1 . The elements of i2,1,l corresponding to the M l − min M l , K (2) weakest
non-zero coefficients are reported, where cl ,i  0,1, 2, 3 . The remaining 2 L − M l elements of i2,1,l are
not reported and are set to cl ,i = 0 .
When two elements, kl , x and kl , y , of the reported elements of i1,4,l are identical ( kl , x = kl , y ), then
(1) (1) (1) (1)
-
( )
element min ( x, y ) is prioritized to be included in the set of the min M l , K (2) − 1 strongest coefficients
for i2,1,l and i2,2,l ( l = 1, , ) reporting.
Table 5.2.2.2.3-4: Full resolution subband coefficients when subbandAmplitude is set to 'true'
L K (2)
2 4
3 4
4 6
The codebooks for 1-2 layers are given in Table 5.2.2.2.3-5, where the indices m1(i ) and m2(i ) are given by
m1(i ) = O1n1(i ) + q1
m2(i ) = O2 n2(i ) + q2
for i = 0,1, , L −1 , and the quantities  l ,i , u m , and vl , m are given by
3GPP
Release 16 78 3GPP TS 38.214 V16.1.0 (2020-03)
e j 2 cl ,i NPSK subbandAmplitude = 'false'


e j 2 cl ,i NPSK
 ( )
,i  0
subbandAmplitude = 'true', min M l , K (2) strongest coefficients (including i1,3,l ) with kl(1)
l ,i =  j 2 c 4
e

l ,i
subbandAmplitude = 'true', M l − min M l , K (2) weakest coefficients with kl(1)
,i  0( )

1 subbandAmplitude = 'true', 2 L − M l coefficients with kl(1)
,i = 0
 j
2 m
j
2 m ( N 2 −1) 
 
1 e
O2 N 2
e O2 N 2  N2 1
um =    .
 

 1 N2 =1
2 l 2 l ( N1 −1) T
 j j 
vl ,m = um e O1 N1
um e O1 N1
um 
 
 
Table 5.2.2.2.3-5: Codebook for 1-layer and 2-layer CSI reporting using antenna ports 3000 to
2999+PCSI‑RS
Layers
 =1 Wq(1,)q (1) (2) = Wq1 , q (1) (2)

1 2 , n1 , n2 , p1 , p1 , i2,1,1 1 2 , n1 , n2 , p1 , p1 , i2,1,1
1  1 
=2 Wq(2),q = W Wq2,q
2  q1 ,q2 ,n1 ,n2 , p1 , p1 ,i2,1,1 
(1) (2) (1) (2) (1) (2) (1) (2)
1 2 , n1 , n2 , p1 , p1 ,i2,1,1 , p2 , p2 ,i2,1,2 1 2 , n1 , n2 , p2 , p2 ,i2,1,2
 L −1 
  vm1( i ) , m2( i ) pl ,i pl ,i l ,i 
(1) (2)
1  i =0  , l = 1, 2 ,
where W l =
 L −1 
(1) (2)
q ,q 2 , n1 , n2 , pl , pl , cl 2 L −1
N1 N 2  ( pl(1)
,i pl ,i )   vm1( i ) , m2( i ) pl ,i + L pl ,i + Ll ,i + L 
1
(2) 2 (1) (2)
i =0  i =0 
and the mappings from i1 to q1 , q2 , n1 , n2 , p1(1) , and p 2(1) , and from i2 to i2,1,1 , i2,1,2 , p1(2) and p2(2) are as described
above, including the ranges of the constituent indices of i1 and i2 .
When the UE is configured with higher layer parameter codebookType set to 'typeII', thebitmap parameter typeII-
RI‑Restriction forms the bit sequence r1 , r0 where r0 is the LSB and r1 is the MSB. When ri is zero, i  0,1 , PMI and
RI reporting are not allowed to correspond to any precoder associated with  = i + 1 layers. The bitmap parameter n1-
n2‑codebookSubsetRestriction forms the bit sequence B = B1 B2 where bit sequences B1 , and B2 are concatenated to
form B . To define B1 and B2 , first define the O1O2 vector groups G ( r1 , r2 ) as

G ( r1 , r2 ) = vN1r1 + x1 , N2r2 + x2 : x1 = 0,1, , N1 − 1; x2 = 0,1, , N2 − 1 
for
r1  0,1, , O1 − 1
.
r2  0,1, , O2 − 1
The UE shall be configured with restrictions for 4 vector groups indicated by r1( k ) , r2( k ) for k = 0,1, 2,3 and identified ( )
by the group indices
g ( ) = O1r2( ) + r1( )
k k k
3GPP
Release 16 79 3GPP TS 38.214 V16.1.0 (2020-03)
g ( ) increases as k increases. The remaining vector groups

k
for k = 0,1, ,3 , where the indices are assigned such that
are not restricted.
g ( ) = k for k = 0,1, ,3 , and

k
- If N 2 = 1 , B1 is empty.
(10 )
b1( ) is the binary representation of the integer 1 where b1( ) is the MSB and b1( ) is
0 10 0
- If N 2  1 , B1 = b1
the LSB. 1 is found using:
( )
3
1 =  C O1O2 − 1 − g ( k ) , 4 − k ,
k =0
g ( ) and indicators ( r( ) , r( ) ) for

k
where C ( x, y ) is defined in Table 5.2.2.2.3-1. The group indices 1
k
2
k
k = 0,1, 2,3 may be found from 1 using the algorithm:
s −1 = 0
for k = 0, ,3
Find the largest x*  3 − k , , O1O2 − 1 − k such that 1 − sk −1  C ( x* , 4 − k )
(
ek = C x* , 4 − k )
sk = sk −1 + ek
g ( ) = O1O2 − 1 − x*
k
r1( ) = g ( ) mod O1
k k
( g( ) − r( ) )
k k
(k ) 1
r2 =
O1
( 0 ) (1) ( 2 ) ( 3) (k )
The bit sequence B2 = B2 B2 B2 B2 is the concatenation of the bit sequences B2 for k = 0,1, ,3 , corresponding
(k ) (k )
to the group indices g . The bit sequence B2 is defined as
B2( ) = b2( 1 2 ) b2( )

k k ,2 N N −1 k ,0
( k ,2( N1x2 + x1 )+1) ( k ,2( N1x2 + x1 )) (1) (k )

Bits b2 b2 indicate the maximum allowed amplitude coefficient pl ,i for the vector in group g
indexed by x1 , x2 , where the maximum amplitude coefficients are given in Table 5.2.2.2.3-6. A UE that does not report
parameter amplitudeSubsetRestriction = 'supported' in its capability signaling is not expected to be configured with
( k ,2( N1x2 + x1 )+1) ( k ,2( N1x2 + x1 ))
b2 b2 = 01 or 10.
Table 5.2.2.2.3-6: Maximum allowed amplitude coefficients for restricted vectors
Maximum
Bits Amplitude
( k ,2( N1x2 + x1 )+1) ( k ,2( N1x2 + x1 )) Coefficient
b2 b2
pl(1)
,i
00 0
01 14
10 12
11 1
3GPP
Release 16 80 3GPP TS 38.214 V16.1.0 (2020-03)
5.2.2.2.4 Type II Port Selection Codebook

3001, …, 3031}, and the UE configured with higher layer parameter codebookType set to 'typeII-PortSelection'
- The number of CSI-RS ports is given by PCSI-RS 4,8,12,16, 24,32 as configured by higher layer parameter
nrofPorts.
- The value of L is configured with the higher layer parameter numberOfBeams , where L=2 when PCSI-RS = 4
and L  2,3, 4 when PCSI-RS  4 .
- The value of d is configured with the higher layer parameter portSelectionSamplingSize, where d  1, 2, 3, 4
and d  min 
PCSI-RS 
, L .
 2 
- The value of N PSK is configured with the higher layer parameter phaseAlphabetSize, where NPSK  4,8 .
- The UE is configured with the higher layer parameter subbandAmplitude set to 'true' or 'false'.
- The UE shall not report RI > 2.
The UE is also configured with the higher layer parameter typeII-PortSelectionRI‑Restriction. The bitmap parameter
typeII-PortSelectionRI‑Restriction forms the bit sequence r1 , r0 where r0 is the LSB and r1 is the MSB. When ri is zero,
i  0,1 , PMI and RI reporting are not allowed to correspond to any precoder associated with  = i + 1 layers.
When   2 , where  is the associated RI value, each PMI value corresponds to the codebook indices i1 and i2 where
i1,1 i1,3,1 i1,4,1   =1

i1 = 
 i1,1 i1,3,1 i1,4,1 i1,3,2 i1,4,2   = 2
 i2,1,1  subbandAmplitude = 'false',  = 1
 .
 i2,1,1 i2,1,2  subbandAmplitude = 'false',  = 2
 
i2 = 

  2,1,1 2,2,1 
i i subbandAmplitude = 'true',  = 1

 i2,1,1 i2,2,1 i2,1,2 i2,2,2  subbandAmplitude = 'true',  = 2
The L antenna ports per polarization are selected by the index i1,1 , where
 P  
i1,1  0,1, ,  CSI-RS  − 1 .
  2d  
The strongest coefficient on layer l , l = 1, , is identified by i1,3,l 0,1, , 2L − 1 .
The amplitude coefficient indicators i1,4,l and i2,2,l are
i1,4,l =  kl(1) (1)

,0 , kl ,1 , , kl(1) 
,2 L −1 
i2,2,l =  kl(2) (2)

,0 , kl ,1 , , kl(2) 
,2 L −1 
,i  0,1,
kl(1) , 7
,i  0,1
kl(2)
3GPP
Release 16 81 3GPP TS 38.214 V16.1.0 (2020-03)
(1) (1)
for l = 1, , . The mapping from kl ,i to the amplitude coefficient pl ,i is given in Table 5.2.2.2.3-2 and the
(2) (2)
mapping from kl ,i to the amplitude coefficient pl ,i is given in Table 5.2.2.2.3-3. The amplitude coefficients are
represented by
pl(1) =  pl(1) (1)

,0 , pl ,1 , , pl(1) 
,2 L −1 
pl(2) =  pl(2) (2)

,0 , pl ,1 , , pl(2) 
,2 L −1 
for l = 1, , .
The phase coefficient indicators are
i2,1,l = cl ,0 , cl ,1 , , cl ,2 L −1 
for l = 1, , .
- The indicators kl ,i
(1)
= 7 , kl(2)
,i1,3,l = 1 , and l ,i 1,3,l
c = 0 ( l = 1, , ). kl(1) (2)
c
,i1,3,l , kl ,i1,3,l , and l ,i1,3,l are not reported for
1,3,l
l = 1, , .
2 L − 1 elements of , ) are reported, where kl ,i  0,1, , 7 . Let M l (

(1)
- The remaining i1,4,l ( l = 1,
, ) be the number of elements of i1,4,l that satisfy kl ,i  0 .

(1)
l = 1,
- The remaining 2 L − 1 elements of i2,1,l and i2,2,l ( l = 1, , ) are reported as follows:
- When subbandAmplitude is set to 'false',
- ,i = 1 for l = 1, , , and i = 0,1, ,2L −1 . i2,2,l is not reported for l = 1, , .

kl(2)
, , the M l − 1 elements of i2,1,l corresponding to the coefficients that satisfy kl ,i  0 ,

(1)
- For l = 1,
i  i1,3,l , as determined by the reported elements of i1,4,l , are reported, where cl ,i  0,1, , NPSK − 1 and
the remaining 2 L − M l elements of i2,1,l are not reported and are set to cl ,i = 0 .
- When subbandAmplitude is set to 'true',
- For l = 1, , , the elements of i2,2,l and i2,1,l corresponding to the min M l , K (2) − 1 strongest ( )
coefficients (excluding the strongest coefficient indicated by i1,3,l ), as determined by the corresponding
reported elements of i1,4,l , are reported, where kl ,i  0,1 and cl ,i 0,1,

(2)
, NPSK − 1 . The values of
(
K (2) are given in Table 5.2.2.2.3-4. The remaining 2 L − min M l , K (2) elements of i2,2,l are not )
reported and are set to kl(2)
,i = 1 . The elements of i2,1,l corresponding to the M l − min M l , K (2) weakest ( )
non-zero coefficients are reported, where cl ,i  0,1, 2, 3 . The remaining 2 L − M l elements of i2,1,l are
not reported and are set to cl ,i = 0 .
When two elements, kl , x and kl , y , of the reported elements of i1,4,l are identical ( kl , x = kl , y ), then
(1) (1) (1) (1)
-
(
element min ( x, y ) is prioritized to be included in the set of the min M l , K (2) − 1 strongest coefficients )
for i2,1,l and i2,2,l ( l = 1, , ) reporting.
3GPP
Release 16 82 3GPP TS 38.214 V16.1.0 (2020-03)
The codebooks for 1-2 layers are given in Table 5.2.2.2.4-1, where the quantity  l ,i is given by
e j 2 cl ,i N PSK
subbandAmplitude = 'false'

e j 2 cl ,i

N PSK
( ) ,i  0
subbandAmplitude = 'true', min M l , K (2) strongest coefficients (including i1,3,l ) with kl(1)
l , i =  j 2 c
e

l ,i 4
(
subbandAmplitude = 'true', M l − min M l , K (2) weakest coefficients with kl(1)
,i  0 )

1 subbandAmplitude = 'true', 2 L − M l coefficients with kl(1)
,i = 0
and vm is a PCSI-RS 2 -element column vector containing a value of 1 in element ( m mod PCSI-RS 2 ) and zeros
elsewhere (where the first element is element 0).
Table 5.2.2.2.4-1: Codebook for 1-layer and 2-layer CSI reporting using antenna ports 3000 to
2999+PCSI‑RS
Layers
 =1 Wi (1), p(1) , p(2) ,i = Wi1 , p(1) , p(2) ,i

1,1 1 1 2,1,1 1,1 1 1 2,1,1
1  1 
=2 Wi (2), p(1) , p(2) ,i = W (1) (2) Wi 2 , p(1) , p(2) ,i
2  i1,1 , p1 , p1 ,i2,1,1 
(1) (2)
1,1 1 1 2,1,1 , p2 , p2 , i2,1,2 1,1 2 2 2,1,2
 L −1 
  vi1,1d +i pl ,i pl ,i l ,i 
(1) (2)
1  i =0  , l = 1, 2 ,
where W l =
 L −1 
(1) (2)
i 1,1 , pl , pl , i2,1,l 2 L −1
(p ,i )   vi1,1d +i pl ,i + L pl ,i + Ll ,i + L 

(1) 2 (1) (2)
pl(2)
 i =0 
l ,i
i =0
and the mappings from i1 to i1,1 , p1(1) , and p2(1) and from i2 to i2,1,1 , i2,1,2 , p1(2) , and p2(2) are as described above,
including the ranges of the constituent indices of i1 and i2 .
5.2.2.2.5 Enhanced Type II Codebook

3001, …, 3031}, and UE configured with higher layer parameter codebookType set to ' typeII-r16'
- The values of 𝑁1 and 𝑁2 are configured with the higher layer parameter n1-n2-codebookSubsetRestriction-r16.
The supported configurations of (𝑁1 , 𝑁2 ) for a given number of CSI-RS ports and the corresponding values of
(𝑂1 , 𝑂2 ) are given in Table 5.2.2.2.1-2. The number of CSI-RS ports, 𝑃CSI−RS , is 2𝑁1 𝑁2 .
- The values of 𝐿, 𝛽 and 𝑝𝜐 are determined by the higher layer parameter paramCombination-r16, where the
mapping is given in Table 5.2.2.2.5-1.
- The UE is not expected to be configured with paramCombination-r16 equal to
- 3, 4, 5, 6, 7, or 8 when 𝑃CSI−RS = 4,
- 7 or 8 when 𝑃CSI−RS < 32
- 7 or 8 when higher layer parameter typeII-RI-Restriction-r16 is configured with 𝑟𝑖 = 1 for any 𝑖 > 1.
- 7 or 8 when 𝑅 = 2.
- The parameter 𝑅 is configured with the higher-layer parameter numberOfPMISubbandsPerCQISubband. This

parameter controls the total number of precoding matrices 𝑁3 indicated by the PMI as a function of the number
of subbands in csi-ReportingBand, the subband size configured by the higher-level parameter subbandSize and
of the total number of PRBs in the bandwidth part according to Table 5.2.1.4-2, as follows:
- When 𝑅 = 1:
- One precoding matrix is indicated by the PMI for each subband in csi-ReportingBand.
3GPP
Release 16 83 3GPP TS 38.214 V16.1.0 (2020-03)
- When 𝑅 = 2:
- For each subband in csi-ReportingBand that is not the first or last subband of a BWP, two precoding
𝑆𝐵
matrices are indicated by the PMI: the first precoding matrix corresponds to the first 𝑁𝑃𝑅𝐵 /2 PRBs of the
𝑆𝐵
subband and the second precoding matrix corresponds to the last 𝑁𝑃𝑅𝐵 /2 PRBs of the subband.
- For each subband in csi-ReportingBand that is the first or last subband of a BWP
𝑆𝐵
𝑠𝑡𝑎𝑟𝑡 𝑆𝐵 𝑁𝑃𝑅𝐵
- If (𝑁𝐵𝑊𝑃,𝑖 mod 𝑁𝑃𝑅𝐵 )≥ , one precoding matrix is indicated by the PMI corresponding to the
2
𝑆𝐵
𝑠𝑡𝑎𝑟𝑡 𝑆𝐵 𝑁𝑃𝑅𝐵
first subband. If (𝑁𝐵𝑊𝑃,𝑖 mod 𝑁𝑃𝑅𝐵 )< , two precoding matrices are indicated by the PMI
2
𝑆𝐵
𝑁𝑃𝑅𝐵
corresponding to the first subband: the first precoding matrix corresponds to the first −
2
𝑠𝑡𝑎𝑟𝑡 𝑆𝐵
(𝑁𝐵𝑊𝑃,𝑖 mod 𝑁𝑃𝑅𝐵 ) PRBs of the first subband and the second precoding matrix corresponds to the
𝑆𝐵
𝑁𝑃𝑅𝐵
last PRBs of the first subband.
2
𝑆𝐵
𝑠𝑡𝑎𝑟𝑡 𝑠𝑖𝑧𝑒 𝑆𝐵 𝑁𝑃𝑅𝐵
- If (𝑁𝐵𝑊𝑃,𝑖 + 𝑁𝐵𝑊𝑃,𝑖 )mod 𝑁𝑃𝑅𝐵 ≤ , one precoding matrix is indicated by the PMI corresponding
2
𝑆𝐵
to the last subband. If (𝑁𝐵𝑊𝑃,𝑖 + 𝑁𝐵𝑊𝑃,𝑖 )mod 𝑁𝑃𝑅𝐵 > , two precoding matrices are indicated by
2
𝑆𝐵
𝑁𝑃𝑅𝐵
the PMI corresponding to the last subband: the first precoding matrix corresponds to the first
2
PRBs of the last subband and the second precoding matrix corresponds to the last
𝑆𝐵
(𝑁𝐵𝑊𝑃,𝑖 + 𝑁𝐵𝑊𝑃,𝑖 )mod 𝑁𝑃𝑅𝐵 − PRBs of the last subband.
2
Table 5.2.2.2.5-1: Codebook parameter configurations for 𝑳, 𝛃 and 𝒑𝝊
paramCombination- 𝑝𝜐
𝐿 𝛽
r16 𝜐 ∈ {1,2} 𝜐 ∈ {3,4}
1 2 ¼ 1/8 ¼
2 2 ¼ 1/8 ½
3 4 ¼ 1/8 ¼
4 4 ¼ 1/8 ½
5 4 ¼ ¼ ¾
6 4 ½ ¼ ½
7 6 ¼ - ½
8 6 ¼ - ¾
- The UE shall report the RI value 𝜐 according to the configured higher layer parameter typeII-RI-Restriction-r16.
The UE shall not report 𝜐 > 4.
The PMI value corresponds to the codebook indices of i1 and i2 where
[𝑖1,1 𝑖1,2 𝑖1,5 𝑖1,6,1 𝑖1,7,1 𝑖1,8,1 ] 𝜐=1

[𝑖1,1 𝑖1,2 𝑖1,5 𝑖1,6,1 𝑖1,7,1 𝑖1,8,1 𝑖1,6,2 𝑖1,7,2 𝑖1,8,2 ] 𝜐=2
𝑖1 = 𝑖 𝑖1,2 𝑖1,5 𝑖1,6,1 𝑖1,7,1 𝑖1,8,1 𝑖1,6,2 𝑖1,7,2 𝑖1,8,2 𝑖1,6,3
[ 1,1 𝑖1,7,3 𝑖1,8,3 ] 𝜐=3
{[𝑖1,1 𝑖1,2 𝑖1,5 𝑖1,6,1 𝑖1,7,1 𝑖1,8,1 𝑖1,6,2 𝑖1,7,2 𝑖1,8,2 𝑖1,6,3 𝑖1,7,3 𝑖1,8,3 𝑖1,6,4 𝑖1,7,4 𝑖1,8,4 ] 𝜐=4
[𝑖2,3,1 𝑖2,4,1 𝑖2,5,1 ] 𝜐=1
[𝑖2,3,1 𝑖2,4,1 𝑖2,5,1 𝑖2,3,2 𝑖2,4,2 𝑖2,5,2 ] 𝜐=2
𝑖2 =
[𝑖2,3,1 𝑖2,4,1 𝑖2,5,1 𝑖2,3,2 𝑖2,4,2 𝑖2,5,2 𝑖2,3,3 𝑖2,4,3 𝑖2,5,3 ] 𝜐=3
{[𝑖2,3,1 𝑖2,4,1 𝑖2,5,1 𝑖2,3,2 𝑖2,4,2 𝑖2,5,2 𝑖2,3,3 𝑖2,4,3 𝑖2,5,3 𝑖2,3,4 𝑖2,4,4 𝑖2,5,4 ] 𝜐=4
The precoding matrices indicated by the PMI are determined from 𝐿 + 𝑀𝜐 vectors.
𝐿 vectors, 𝑣𝑚(𝑖),𝑚(𝑖) , 𝑖 = 0,1, … , 𝐿 − 1, are indentified by the indices 𝑞1 , 𝑞2 , 𝑛1 , 𝑛2 , indicated by 𝑖1,1 , 𝑖1,2, obtained as in
1 2
5.2.2.2.3, where the values of 𝐶(𝑥, 𝑦) are given in Table 5.2.2.2.5-4.
3GPP
Release 16 84 3GPP TS 38.214 V16.1.0 (2020-03)
𝑁3 (𝑓) (𝑓) (𝑓) 𝑇

𝑀𝜐 = ⌈𝑝𝜐 ⌉ vectors, [𝑦0,𝑙 , 𝑦1,𝑙 , … , 𝑦𝑁3−1,𝑙 ] , 𝑓 = 0,1, … , 𝑀𝜐 − 1, are identified by 𝑀𝑖𝑛𝑖𝑡𝑖𝑎𝑙 (for 𝑁3 > 19) and
𝑅
𝑛3,𝑙 (𝑙 = 1, … , 𝜐) where
𝑀𝑖𝑛𝑖𝑡𝑖𝑎𝑙 ∈ {−2𝑀𝜐 + 1, −2𝑀𝜐 + 2, … ,0}

(0) (𝑀 −1)
𝑛3,𝑙 = [𝑛3,𝑙 , … , 𝑛3,𝑙 𝜐 ]
(𝑓)
𝑛3,𝑙 ∈ {0,1, … , 𝑁3 − 1}
which are indicated by means of the indices 𝑖1,5 (for 𝑁3 > 19) and 𝑖1,6,𝑙 (𝑙 = 1, … , 𝜐), where
𝑖1,5 ∈ {0,1, … ,2𝑀𝜐 − 1}
𝑁 −1
{0,1, … , ( 3 ) − 1} 𝑁3 ≤ 19
𝑀𝜐 − 1
𝑖1,6,𝑙 ∈{
2𝑀 − 1
{0,1, … , ( 𝜐 ) − 1} 𝑁3 > 19
𝑀𝜐 − 1
The amplitude coefficient indicators 𝑖2,3,𝑙 and 𝑖2,4,𝑙 are

(1) (1)
𝑖2,3,𝑙 = [𝑘𝑙,0 𝑘𝑙,1 ]
(2) (2)
𝑖2,4,𝑙 = [𝑘𝑙,0 … 𝑘𝑙,𝑀𝜐 −1 ]
(2) (2) (2)

𝑘𝑙,𝑓 = [𝑘𝑙,0,𝑓 … 𝑘𝑙,2𝐿−1,𝑓 ]
(1)
𝑘𝑙,𝑝 ∈ {1, … ,15}
(2)
𝑘𝑙,𝑖,𝑓 ∈ {0, … ,7}
for 𝑙 = 1, … , 𝜐.
The phase coefficient indicator 𝑖2,5,𝑙 is
𝑖2,5,𝑙 = [𝑐𝑙,0 … 𝑐𝑙,𝑀𝜐 −1 ]
𝑐𝑙,𝑓 = [𝑐𝑙,0,𝑓 … 𝑐𝑙,2𝐿−1,𝑓 ]
𝑐𝑙,𝑖,𝑓 ∈ {0, … ,15}
for 𝑙 = 1, … , 𝜐.
Let 𝐾0 = ⌈𝛽2𝐿𝑀1 ⌉. The bitmap whose nonzero bits identify which coefficients in 𝑖2,4,𝑙 and 𝑖2,5,𝑙 are reported, is
indicated by 𝑖1,7,𝑙
(3) (3)
𝑖1,7,𝑙 = [𝑘𝑙,0 … 𝑘𝑙,𝑀𝜐 −1 ]
(3) (3) (3)
𝑘𝑙,𝑓 = [𝑘𝑙,0,𝑓 … 𝑘𝑙,2𝐿−1,𝑓 ]
(3)
𝑘𝑙,𝑖,𝑓 ∈ {0,1}
𝑀𝜐 −1 (3)
for 𝑙 = 1, … , 𝜐, such that 𝐾𝑙𝑁𝑍 = ∑2𝐿−1
𝑖=0 ∑𝑓=0 𝑘𝑙,𝑖,𝑓 ≤ 𝐾0 is the number of nonzero coefficients for layer 𝑙 = 1, … , 𝜐 and
𝐾 𝑁𝑍 = ∑𝜐𝑙=1 𝐾𝑙𝑁𝑍 ≤ 2𝐾0 is the total number of nonzero coefficients.
The indices of 𝑖2,4,𝑙 , 𝑖2,5,𝑙 and 𝑖1,7,𝑙 are associated to the 𝑀𝜐 codebook indices in 𝑛3,𝑙 .
(1) (1) (2)
The mapping from 𝑘𝑙,𝑝 to the amplitude coefficient 𝑝𝑙,𝑝 is given in Table 5.2.2.2.5-2 and the mapping from 𝑘𝑙,𝑖,𝑓 to the
(2)
amplitude coefficient 𝑝𝑙,𝑖,𝑓 is given in Table 5.2.2.2.5-3. The amplitude coefficients are represented by
3GPP
Release 16 85 3GPP TS 38.214 V16.1.0 (2020-03)
(1) (1) (1)

𝑝𝑙 = [𝑝𝑙,0 𝑝𝑙,1 ]
(2) (2) (2)

𝑝𝑙 = [𝑝𝑙,0 … 𝑝𝑙,𝑀𝜐 −1 ]
(2) (2) (2)

𝑝𝑙,𝑓 = [𝑝𝑙,0,𝑓 … 𝑝𝑙,2𝐿−1,𝑓 ]
for 𝑙 = 1, … , 𝜐.
(2)
Let 𝑓𝑙∗ ∈ {0,1, … , 𝑀𝜐 − 1} be the index of 𝑖2,4,𝑙 and 𝑖𝑙∗ ∈ {0,1, … ,2𝐿 − 1} be the index of 𝑘𝑙,𝑓∗ which identify the
𝑙
(2)
strongest coefficient of layer 𝑙, i.e., the element 𝑘𝑙,𝑖 ∗,𝑓∗ of 𝑖2,4,𝑙 , for 𝑙 = 1, … , 𝜐. The codebook indices of 𝑛3,𝑙 are
𝑙 𝑙
(𝑓∗𝑙 ) (𝑓) (𝑓) (𝑓∗𝑙 ) (𝑓∗ )
remapped with respect to 𝑛3,𝑙 as 𝑛3,𝑙 = ( 𝑛3,𝑙 − 𝑛3,𝑙 ) mod 𝑁3 , such that 𝑛3,𝑙𝑙 = 0, after remapping. The index 𝑓 is
remapped with respect to 𝑓∗𝑙 as 𝑓 = (𝑓 − 𝑓𝑙∗ )mod 𝑀𝜐 , such that the index of the strongest coefficient is 𝑓∗𝑙 = 0 (𝑙 =
1, … , 𝜐), after remapping. The indices of 𝑖2,4,𝑙 , 𝑖2,5,𝑙 and 𝑖1,7,𝑙 indicate amplitude coefficients, phase coefficients and
bitmap after remapping.
The strongest coefficient of layer 𝑙 is identified by 𝑖1,8,𝑙 ∈ {0,1, … ,2𝐿 − 1}, which is obtained as follows
𝑖∗
∑ 1 𝑘 (3) − 1 𝜐=1
𝑖1,8,𝑙 = { 𝑖=0 1,𝑖,0
𝑖𝑙∗ 1<𝜐≤4
for 𝑙 = 1, … , 𝜐.
(𝟏) (𝟏)
Table 5.2.2.2.5-2: Mapping of elements of 𝒊𝟐,𝟑,𝒍 : 𝒌𝒍,𝒑 to 𝒑𝒍,𝒑
(𝟏) (𝟏) (𝟏) (𝟏) (𝟏) (𝟏) (𝟏) (𝟏)

𝒌𝒍,𝒑 𝒑𝒍,𝒑 𝒌𝒍,𝒑 𝒑𝒍,𝒑 𝒌𝒍,𝒑 𝒑𝒍,𝒑 𝒌𝒍,𝒑 𝒑𝒍,𝒑
0 Reserved 4 1 1/4 8 1 1/4 12 1 1/4

( ) ( ) ( )
2048 128 8
1 1 1 1
1 5 9 13
√128 2√8 √8 √2
2 1 1/4 6 1 1/4 10 1 1/4 14 1 1/4

( ) ( ) ( ) ( )
8192 512 32 2
1 1 1
3 7 11 15 1
8 4 2

(1) (2) (3) (1) (2)
- 𝑘 𝑖∗ = 15, 𝑘𝑙,𝑖 ∗ ,0 = 7, 𝑘𝑙,𝑖 ∗ ,0 = 1 and 𝑐𝑙,𝑖𝑙∗ ,0 = 0 (𝑙 = 1, … , 𝜐). The indicators 𝑘 𝑖∗ , 𝑘𝑙,𝑖 ∗ ,0 and 𝑐𝑙,𝑖𝑙∗ ,0 are not
𝑙,⌊ 𝑙 ⌋ 𝑙 𝑙 𝑙,⌊ 𝑙 ⌋ 𝑙
𝐿 𝐿
reported for 𝑙 = 1, … , 𝜐.
(1)
- The indicator 𝑘 𝑖 ∗ is reported for 𝑙 = 1, … , 𝜐.
𝑙,(⌊ 𝑙 ⌋+1) 𝑚𝑜𝑑 2
𝐿
(2) (3)
- The 𝐾 𝑁𝑍 − 𝜐 indicators 𝑘𝑙,𝑖,𝑓 for which 𝑘𝑙,𝑖,𝑓 = 1, 𝑖 ≠ 𝑖𝑙∗ , 𝑓 ≠ 0 are reported.
(3)
- The 𝐾 𝑁𝑍 − 𝜐 indicators 𝑐𝑙,𝑖,𝑓 for which 𝑘𝑙,𝑖,𝑓 = 1, 𝑖 ≠ 𝑖𝑙∗ , 𝑓 ≠ 0 are reported.
(2)
- The remaining 2𝐿 ⋅ 𝑀ν ⋅ 𝜈 − 𝐾 𝑁𝑍 indicators 𝑘𝑙,𝑖,𝑓 are not reported.
3GPP
Release 16 86 3GPP TS 38.214 V16.1.0 (2020-03)
- The remaining 2𝐿 ⋅ 𝑀ν ⋅ 𝜈 − 𝐾 𝑁𝑍 indicators 𝑐𝑙,𝑖,𝑓 are not reported.

(𝟐) (𝟐)
Table 5.2.2.2.5-3: Mapping of elements of 𝒊𝟐,𝟒,𝒍 : 𝒌𝒍,𝒊,𝒇 to 𝒑𝒍,𝒊,𝒇
(𝟐) (𝟐)
𝒌𝒍,𝒊,𝒇 𝒑𝒍,𝒊,𝒇
1
0
8√2
1
1
8
1
2
4√2
1
3
4
1
4
2√2
1
5
2
1
6
√2
7 1
The elements of 𝑛1 and 𝑛2 are found from 𝑖1,2 using the algorithm described in 5.2.2.2.3, where the values of 𝐶(𝑥, 𝑦)
are given in Table 5.2.2.2.5-4.
For 𝑁3 > 19, 𝑀𝑖𝑛𝑖𝑡𝑖𝑎𝑙 is identified by 𝑖1,5 .

(0) (1) (𝑀 −1)
For all values of 𝑁3 , 𝑛3,𝑙 = 0 for 𝑙 = 1, … , 𝜐. The nonzero elements of 𝑛3,𝑙 , identified by 𝑛3,𝑙 , … , 𝑛3,𝑙 𝜐 , are found
from 𝑖1,6,𝑙 (𝑙 = 1, … , 𝜐), for 𝑁3 ≤ 19, and from 𝑖1,6,𝑙 (𝑙 = 1, … , 𝜐) and 𝑀𝑖𝑛𝑖𝑡𝑖𝑎𝑙 , for 𝑁3 > 19, using 𝐶(𝑥, 𝑦) as defined
in Table 5.2.2.2.5-4 and the algorithm:
𝑠0 = 0
for 𝑓 = 1, … , 𝑀𝜐 − 1
Find the largest 𝑥 ∗ ∈ {𝑀𝜐 − 1 − 𝑓, … , 𝑁3 − 1 − 𝑓} in Table 5.2.2.2.5-4 such that
𝑖1,6,𝑙 − 𝑠𝑓−1 ≥ 𝐶(𝑥 ∗ , 𝑀𝜐 − 𝑓)
𝑒𝑓 = 𝐶(𝑥∗ , 𝑀𝜐 − 𝑓)
𝑠𝑓 = 𝑠𝑓−1 + 𝑒𝑓
if 𝑁3 ≤ 19
(𝑓)
𝑛3,𝑙 = 𝑁3 − 1 − 𝑥 ∗
else
(𝑓)
𝑛𝑙 = 2𝑀𝜐 − 1 − 𝑥 ∗
(𝑓)
if 𝑛𝑙 ≤ 𝑀𝑖𝑛𝑖𝑡𝑖𝑎𝑙 + 2𝑀𝜐 − 1
3GPP
Release 16 87 3GPP TS 38.214 V16.1.0 (2020-03)
(𝑓) (𝑓)
𝑛3,𝑙 = 𝑛𝑙
else
(𝑓) (𝑓)
𝑛3,𝑙 = 𝑛𝑙 + (𝑁3 − 2𝑀𝜐 )
end if
end if
Table 5.2.2.2.5-4: Combinatorial coefficients 𝑪(𝒙, 𝒚)
y
1 2 3 4 5 6 7 8 9
x
0 0 0 0 0 0 0 0 0 0
1 1 0 0 0 0 0 0 0 0
2 2 1 0 0 0 0 0 0 0
3 3 3 1 0 0 0 0 0 0
4 4 6 4 1 0 0 0 0 0
5 5 10 10 5 1 0 0 0 0
6 6 15 20 15 6 1 0 0 0
7 7 21 35 35 21 7 1 0 0
8 8 28 56 70 56 28 8 1 0
9 9 36 84 126 126 84 36 9 1
10 10 45 120 210 252 210 120 45 10
11 11 55 165 330 462 462 330 165 55
12 12 66 220 495 792 924 792 495 220
13 13 78 286 715 1287 1716 1716 1287 715
14 14 91 364 1001 2002 4004 3432 3003 2002
15 15 105 455 1365 3003 5005 6435 6435 5005
16 16 120 560 1820 4368 8008 11440 12870 11440
17 17 136 680 2380 6188 12376 19448 24310 24310
18 18 153 816 3060 8568 18564 31824 43758 48620
When 𝑛3,𝑙 and 𝑀𝑖𝑛𝑖𝑡𝑖𝑎𝑙 are known, 𝑖1,5 and 𝑖1,6,𝑙 (𝑙 = 1, … , 𝜐) are found as follows:
𝜐 𝑀 −1 (𝑓)
- If 𝑁3 ≤ 19, 𝑖1,5 = 0 and is not reported. 𝑖1,6,𝑙 = ∑𝑓=1 𝐶 (𝑁3 − 1 − 𝑛3,𝑙 , 𝑀𝜐 − 𝑓), where 𝐶(𝑥, 𝑦) is given in
(𝑓)
Table 5.2.2.2.5-4 and where the indices 𝑓 = 1, … , 𝑀𝜐 − 1 are assigned such that 𝑛3,𝑙 increases as 𝑓 increases.
- If 𝑁3 > 19, 𝑀𝑖𝑛𝑖𝑡𝑖𝑎𝑙 is indicated by 𝑖1,5 , which is reported and given by
𝑀𝑖𝑛𝑖𝑡𝑖𝑎𝑙 𝑀𝑖𝑛𝑖𝑡𝑖𝑎𝑙 = 0
𝑖1,5 = {
𝑀𝑖𝑛𝑖𝑡𝑖𝑎𝑙 + 2𝑀𝜐 𝑀𝑖𝑛𝑖𝑡𝑖𝑎𝑙 < 0
(𝑓)
Only the nonzero indices 𝑛3,𝑙 ∈ 𝐼𝑛𝑡𝑆, where 𝐼𝑛𝑡𝑆 = {(𝑀𝑖𝑛𝑖𝑡𝑖𝑎𝑙 + 𝑖) mod 𝑁3 , 𝑖 = 0,1, … ,2𝑀𝜐 − 1}, are reported,
(𝑓)
where the indices 𝑓 = 1, … , 𝑀𝜐 − 1 are assigned such that 𝑛3,𝑙 increases as 𝑓 increases. Let
(𝑓) (𝑓)
(𝑓) 𝑛3,𝑙 𝑛3,𝑙 ≤ 𝑀𝑖𝑛𝑖𝑡𝑖𝑎𝑙 + 2𝑀𝜐 − 1
𝑛𝑙 ={ (𝑓) (𝑓)
,
𝑛3,𝑙 − (𝑁3 − 2𝑀𝜐 ) 𝑛3,𝑙 > 𝑀𝑖𝑛𝑖𝑡𝑖𝑎𝑙 + 𝑁3 − 1
𝜐 𝑀 −1 (𝑓)
then 𝑖1,6,𝑙 = ∑𝑓=1 𝐶 (2𝑀𝜐 − 1 − 𝑛𝑙 , 𝑀𝜐 − 𝑓), where 𝐶(𝑥, 𝑦) is given in Table 5.2.2.2.5-4.
3GPP
Release 16 88 3GPP TS 38.214 V16.1.0 (2020-03)
(𝑖) (𝑖)
The codebooks for 1-4 layers are given in Table 5.2.2.2.5-5, where 𝑚1 , 𝑚2 , for 𝑖 = 0,1, … , 𝐿 − 1, 𝑢𝑛 and 𝑣𝑚,𝑛 are
obtained as in clause 5.2.2.2.3, and the quantities 𝜑𝑙,𝑖,𝑓 and 𝑦𝑡,𝑙 are given by
2𝜋𝑐𝑙,𝑖,𝑓
𝜑𝑙,𝑖,𝑓 = 𝑒 𝑗 16
(0) (1) (𝑀 −1)

𝑦𝑡,𝑙 = [𝑦𝑡,𝑙 𝑦𝑡,𝑙 … 𝑦𝑡,𝑙 𝜐 ]
where 𝑡 = {0,1, … , 𝑁3 − 1}, is the index associated with the precoding matrix, 𝑙 = {1, … , 𝜐}, and with
(𝑓)
2𝜋𝑡𝑛
3,𝑙
(𝑓) 𝑗
𝑦𝑡,𝑙 =𝑒 𝑁3
for 𝑓 = 0,1, … , 𝑀𝜐 − 1.
Table 5.2.2.2.5-5: Codebook for 1-layer. 2-layer, 3-layer and 4-layer CSI reporting using antenna ports
3000 to 2999+PCSI-RS
Layers
(1)
𝑊 (1) (2) = 𝑊𝑞1 ,𝑞 (1) (2)
𝜐=1 𝑞1 ,𝑞2 ,𝑛1 ,𝑛2 ,𝑛3,1 ,𝑝1 ,𝑝1 ,𝑖2,5,1,𝑡 1 2 ,𝑛1 ,𝑛2 ,𝑛3,1 ,𝑝1 ,𝑝1 ,𝑖2,5,1,𝑡
(2) 1
𝑊 (1) (2) (1) (2) = [𝑊𝑞1 ,𝑞 (1) (2) 𝑊𝑞2 ,𝑞 (1) (2) ]
𝜐=2 𝑞1 ,𝑞2 ,𝑛1 ,𝑛2 ,𝑛3,1 ,𝑝1 ,𝑝1 ,𝑖2,5,1 ,𝑛3,2 ,𝑝2 ,𝑝2 ,𝑖2,5,2 ,𝑡 √2 1 2 ,𝑛1 ,𝑛2 ,𝑛3,1 ,𝑝1 ,𝑝1 ,𝑖2,5,1 ,𝑡 1 2 ,𝑛1 ,𝑛2 ,𝑛3,2 ,𝑝2 ,𝑝2 ,𝑖2,5,2 ,𝑡
(3)
𝑊 (1) (2) (1) (2) (1) (2)
𝑞1 ,𝑞2 ,𝑛1 ,𝑛2 ,𝑛3,1 ,𝑝1 ,𝑝1 ,𝑖2,5,1 ,𝑛3,2 ,𝑝2 ,𝑝2 ,𝑖2,5,2,𝑛3,3 ,𝑝3 ,𝑝3 ,𝑖2,5,3 ,𝑡
𝜐=3 1
= [𝑊𝑞1 ,𝑞 (1) (2) 𝑊𝑞2 ,𝑞 (1) (2) 𝑊𝑞3 ,𝑞 (1) (2) ]
√3 1 2 ,𝑛1 ,𝑛2 ,𝑛3,1 ,𝑝1 ,𝑝1 ,𝑖2,5,1 ,𝑡 1 2 ,𝑛1 ,𝑛2 ,𝑛3,2 ,𝑝2 ,𝑝2 ,𝑖2,5,2 ,𝑡 1 2 ,𝑛1 ,𝑛2 ,𝑛3,3 ,𝑝3 ,𝑝3 ,𝑖2,5,3 ,𝑡
(4)
𝑊 (1) (2) (1) (2) (1) (2) (1) (2)
𝑞1 ,𝑞2 ,𝑛1 ,𝑛2 ,𝑛3,1 ,𝑝1 ,𝑝1 ,𝑖2,5,1 ,𝑛3,2 ,𝑝2 ,𝑝2 ,𝑖2,5,2 ,𝑛3,3 ,𝑝3 ,𝑝3 ,𝑖2,5,3,𝑛3,4 ,𝑝4 ,𝑝4 ,𝑖2,5,4 ,𝑡
𝜐=4 1
= [𝑊𝑞1 ,𝑞 ,𝑛 ,𝑛 ,𝑛 ,𝑝(1),𝑝(2),𝑖 ,𝑡 𝑊𝑞2 ,𝑞 ,𝑛 ,𝑛 ,𝑛 ,𝑝(1),𝑝(2) ,𝑖 ,𝑡 𝑊𝑞3 ,𝑞 ,𝑛 ,𝑛 ,𝑛 ,𝑝(1),𝑝(2),𝑖 ,𝑡 𝑊𝑞4 ,𝑞 ,𝑛 ,𝑛 ,𝑛 ,𝑝(1),𝑝(2),𝑖 ,𝑡 ]
2 1 2 1 2 3,1 1 1 2,5,1 1 2 1 2 3,2 2 2 2,5,2 1 2 1 2 3,3 3 3 2,5,3 1 2 1 2 3,4 4 4 2,5,4
(1) 𝑀𝜐−1 (𝑓) (2)
∑𝐿−1
𝑖=0 𝑣𝑚(𝑖),𝑚(𝑖) 𝑝𝑙,0 ∑𝑓=0 𝑦𝑡,𝑙 𝑝𝑙,𝑖,𝑓 𝜑𝑙,𝑖,𝑓
1
Where 𝑊𝑞𝑙 (1) (2) = [ 1 2
] , 𝑙 = 1,2,3,4,
1 ,𝑞2 ,𝑛1 ,𝑛2 ,𝑛3 ,𝑝𝑙 ,𝑝𝑙 ,𝑖2,5,𝑙 ,𝑡 √𝑁1 𝑁2 𝛾𝑡,𝑙 ∑𝐿−1 𝑣 (𝑖) (𝑖) 𝑝 (1) ∑𝑀𝜐 −1 𝑦 (𝑓) 𝑝 (2)
𝑖=0 𝑚 ,𝑚 𝑙,1 𝑓=01
𝑡,𝑙 𝑙,𝑖+𝐿,𝑓 𝜑𝑙,𝑖+𝐿,𝑓
2
2
2𝐿−1 2 𝑀𝜐−1
(1) (𝑓) (2)
𝛾𝑡,𝑙 = ∑ (𝑝 𝑖 ) | ∑ 𝑦𝑡,𝑙 𝑝𝑙,𝑖,𝑓 𝜑𝑙,𝑖,𝑓 |
𝑙,⌊ ⌋
𝑖=0 𝐿 𝑓=0
(1) (1) (1) (1)

and the mappings from 𝑖1 to 𝑞1 , 𝑞2 , 𝑛1 , 𝑛2 , 𝑛3,1 , 𝑛3,2 , 𝑛3,3 , 𝑛3,4 , 𝑝1 , 𝑝2 , 𝑝3 and 𝑝4 , and from 𝑖2 to 𝑖2,5,1 , 𝑖2,5,2 , 𝑖2,5,3 , 𝑖2,5,4 ,
(2) (2) (2) (2)
𝑝1 , 𝑝2 , 𝑝3 and 𝑝4 are as described above, including the ranges of the constituent indices of 𝑖1 and 𝑖2 .
(3)
For coefficients with 𝑘𝑙,𝑖,𝑓 = 0, amplitude and phase are set to zero, i.e., 𝑝(2)
𝑙,𝑖,𝑓
= 0 and 𝜑𝑙,𝑖,𝑓 = 0.
The bitmap parameter typeII-RI-Restriction-r16 forms the bit sequence 𝑟3 , 𝑟2 , 𝑟1 , 𝑟0 where 𝑟0 is the LSB and 𝑟3 is the
MSB. When 𝑟𝑖 is zero, 𝑖 ∈ {0,1, … ,3}, PMI and RI reporting are not allowed to correspond to any precoder associated
with 𝜐 = 𝑖 + 1 layers.
The bitmap parameter n1-n2-codebookSubsetRestriction-r16 forms the bit sequence 𝐵 = 𝐵1 𝐵2 and configures the
(𝑘,2(𝑁1 𝑥2 +𝑥1 )+1) (𝑘,2(𝑁1 𝑥2 +𝑥1 ))
vector group indices 𝑔(𝑘) as in clause 5.2.2.2.3. Bits 𝑏2 𝑏2 indicate the maximum allowed
average amplitude, 𝛾𝑖+𝑝𝐿 (𝑝 = 0,1), with 𝑖 ∈ {0,1, … , 𝐿 − 1}, of the coefficients associated with the vector in group 𝑔(𝑘)
indexed by 𝑥1 , 𝑥2 , where the maximum amplitudes are given in Table 5.2.2.2.5-6 and the average coefficient amplitude
is restricted as follows
1 2
𝜐 −1 (3) (1) (2)
√∑𝑀𝜐−1 𝑘 (3) ∑𝑀
𝑓=0 𝑘𝑙,𝑖+𝑝𝐿,𝑓 (𝑝𝑙,𝑝 𝑝𝑙,𝑖+𝑝𝐿,𝑓 ) ≤ 𝛾𝑖+𝑝𝐿
𝑓=0 𝑙,𝑖+𝑝𝐿,𝑓
3GPP
Release 16 89 3GPP TS 38.214 V16.1.0 (2020-03)
for 𝑙 = 1, … , 𝜐, and 𝑝 = 0,1. A UE that does not report the parameter amplitudeSubsetRestriction='supported' in its
(𝑘,2(𝑁1 𝑥2 +𝑥1 )+1) (𝑘,2(𝑁1 𝑥2 +𝑥1 ))
capability signaling is not expected to be configured with 𝑏2 𝑏2 = 01 or 10.
Table 5.2.2.2.5-6: Maximum allowed average coefficient amplitudes for restricted vectors
Maximum
Bit Average
(𝒌,𝟐(𝑵𝟏 𝒙𝟐 +𝒙𝟏 )+𝟏) (𝒌,𝟐(𝑵𝟏 𝒙𝟐 +𝒙𝟏 )) Coefficient
𝒃𝟐 𝒃𝟐 Amplitude
𝜸𝒊+𝒑𝑳
00 0
01 √1/4
10 √1/2
11 1
5.2.2.2.6 Enhanced Type II Port Selection Codebook

3001, …, 3031}, and the UE configured with higher layer parameter codebookType set to ' typeII-PortSelection-r16 '
- The number of CSI-RS ports is configured as in Clause 5.2.2.2.4
- The value of 𝑑 is configured with the higher layer parameter portSelectionSamplingSize-r16, where 𝑑 ∈
{1,2,3,4} and 𝑑 ≤ 𝐿.
- The values 𝐿, 𝛽 and 𝑝𝜐 are configured as in Clause 5.2.2.2.5, where the supported configurations are given in
Table 5.2.2.2.6-1.
Table 5.2.2.2.6-1: Codebook parameter configurations for 𝑳, 𝜷 and𝒑𝝊
paramCombination- 𝑝𝜐
𝐿 𝛽
r16 𝜐 ∈ {1,2} 𝜐 ∈ {3,4}
1 2 ¼ 1/8 ¼
2 2 ¼ 1/8 ½
3 4 ¼ 1/8 ¼
4 4 ¼ 1/8 ½
5 4 ¼ ¼ ¾
6 4 ½ ¼ ½
- The UE shall report the RI value 𝜐 according to the configured higher layer parameter typeII-PortSelectionRI-
Restriction-r16. The UE shall not report 𝜐 > 4.
- The values of 𝑅 is configured as in Clause 5.2.2.2.5.
The UE is also configured with the higher layer bitmap parameter typeII-PortSelectionRI-Restriction-r16, which forms
the bit sequence 𝑟3 , 𝑟2 , 𝑟1 , 𝑟0 , where 𝑟0 is the LSB and 𝑟3 is the MSB. When 𝑟𝑖 is zero, 𝑖 ∈ {0,1, … , 3}, PMI and RI
reporting are not allowed to correspond to any precoder associated with 𝜐 = 𝑖 + 1 layers.
The PMI value corresponds to the codebook indices 𝑖1 and 𝑖2 where
3GPP
Release 16 90 3GPP TS 38.214 V16.1.0 (2020-03)
[𝑖1,1 𝑖1,5 𝑖1,6,1 𝑖1,7,1 𝑖1,8,1 ] 𝜐=1

[𝑖1,1 𝑖1,5 𝑖1,6,1 𝑖1,7,1 𝑖1,8,1 𝑖1,6,2 𝑖1,7,2 𝑖1,8,2 ] 𝜐=2
𝑖1 =
[𝑖1,1 𝑖1,5 𝑖1,6,1 𝑖1,7,1 𝑖1,8,1 𝑖1,6,2 𝑖1,7,2 𝑖1,8,2 𝑖1,6,3 𝑖1,7,3 𝑖1,8,3 ] 𝜐=3
{[𝑖1,1 𝑖1,5 𝑖1,6,1 𝑖1,7,1 𝑖1,8,1 𝑖1,6,2 𝑖1,7,2 𝑖1,8,2 𝑖1,6,3 𝑖1,7,3 𝑖1,8,3 𝑖1,6,4 𝑖1,7,4 𝑖1,8,4 ] 𝜐=4
[𝑖2,3,1 𝑖2,4,1 𝑖2,5,1 ] 𝜐=1
[𝑖2,3,1 𝑖2,4,1 𝑖2,5,1 𝑖2,3,2 𝑖2,4,2 𝑖2,5,2 ] 𝜐=2
𝑖2 =
[𝑖2,3,1 𝑖2,4,1 𝑖2,5,1 𝑖2,3,2 𝑖2,4,2 𝑖2,5,2 𝑖2,3,3 𝑖2,4,3 𝑖2,5,3 ] 𝜐=3
{[𝑖2,3,1 𝑖2,4,1 𝑖2,5,1 𝑖2,3,2 𝑖2,4,2 𝑖2,5,2 𝑖2,3,3 𝑖2,4,3 𝑖2,5,3 𝑖2,3,4 𝑖2,4,4 𝑖2,5,4 ] 𝜐=4
The 2𝐿 antenna ports are selected by the index 𝑖1,1 as in clause 5.2.2.2.4.
Parameters 𝑁3 , 𝑀𝜐 , 𝑀𝑖𝑛𝑖𝑡𝑖𝑎𝑙 (for 𝑁3 > 19) and 𝐾0 are defined as in clause 5.2.2.2.5.
For layer 𝑙, 𝑙 = 1, … , 𝜐, the strongest coefficient 𝑖1,8,𝑙 , the amplitude coefficient indicators 𝑖2,3,𝑙 and 𝑖2,4,𝑙 , the phase
coefficient indicator 𝑖2,5,𝑙 and the bitmap indicator 𝑖1,7,𝑙 are defined and indicated as in clause 5.2.2.2.5, where the
(1) (1) (2)
mapping from 𝑘𝑙,𝑝 to the amplitude coefficient 𝑝𝑙,𝑝 is given in Table 5.2.2.2.5-2 and the mapping from 𝑘𝑙,𝑖,𝑓 to the
(2)
amplitude coefficient 𝑝𝑙,𝑖,𝑓 is given inTable 5.2.2.2.5-3.
The number of nonzero coefficients for layer 𝑙, 𝐾𝑙𝑁𝑍 , and the total number of nonzero coefficients 𝐾 𝑁𝑍 are defined as in
Clause 5.2.2.2.5.
(1) (2)
The amplitude coefficients 𝑝𝑙 and 𝑝𝑙 (𝑙 = 1, … , 𝜐 ) are represented as in clause 5.2.2.2.5.
The amplitude and phase coefficient indicators are reported as in clause 5.2.2.2.5.
Codebook indicators 𝑖1,5 and 𝑖1,6,𝑙 (𝑙 = 1, … , 𝜐) are found as in clause 5.2.2.2.5.
The codebooks for 1-4 layers are given in Table 5.2.2.2.6-2, where 𝑣𝑚 is a 𝑃𝐶𝑆𝐼−𝑅𝑆 /2 -element column vector
containing a value of 1 in element (𝑚 mod 𝑃𝐶𝑆𝐼−𝑅𝑆 /2 ) and zeros elsewhere (where the first element is element 0), and
the quantities 𝜑𝑙,𝑖,𝑓 and 𝑦𝑡,𝑙 are defined as in clause 5.2.2.2.5.
Table 5.2.2.2.6-2: Codebook for 1-layer. 2-layer, 3-layer and 4-layer CSI reporting using antenna ports
3000 to 2999+PCSI-RS
Layers
3GPP
Release 16 91 3GPP TS 38.214 V16.1.0 (2020-03)
(1)
𝑊 (1) (2) = 𝑊𝑖1 (1) (2)
𝜐=1 𝑖1,1 ,𝑛3,1 ,𝑝1 ,𝑝1 ,𝑖2,5,1,𝑡 1,1 ,𝑛3,1 ,𝑝1 ,𝑝1 ,𝑖2,5,1 ,𝑡
(2) 1
𝑊 (1) (2) (1) (2) = [𝑊𝑖1 (1) (2) 𝑊𝑖2 (1) (2) ]
𝜐=2 𝑖1,1 ,𝑛3,1 ,𝑝1 ,𝑝1 ,𝑖2,5,1,𝑛3,2 ,𝑝2 ,𝑝2 ,𝑖2,5,2 ,𝑡 √2 1,1 ,𝑛3,1 ,𝑝1 ,𝑝1 ,𝑖2,5,1 ,𝑡 1,1 ,𝑛3,2,𝑝2 ,𝑝2 ,𝑖2,5,2 ,𝑡
(3)
𝑊 (1) (2) (1) (2) (1) (2)
𝑖1,1 ,𝑛3,1 ,𝑝1 ,𝑝1 ,𝑖2,5,1 ,𝑛3,2 ,𝑝2 ,𝑝2 ,𝑖2,5,2,𝑛3,3 ,𝑝3 ,𝑝3 ,𝑖2,5,3 ,𝑡
𝜐=3 1
= [𝑊𝑖1 (1) (2) 𝑊𝑖2 (1) (2) 𝑊𝑖3 (1) (2) ]
√3 1,1 ,𝑛3,1 ,𝑝1 ,𝑝1 ,𝑖2,5,1 ,𝑡 1,1 ,𝑛3,2,𝑝2 ,𝑝2 ,𝑖2,5,2 ,𝑡 1,1 ,𝑛3,3 ,𝑝3 ,𝑝3 ,𝑖2,5,3 ,𝑡
(4)
𝑊 (1) (2) (1) (2) (1) (2) (1) (2)
𝑖1,1 ,𝑛3,1 ,𝑝1 ,𝑝1 ,𝑖2,5,1,𝑛3,2 ,𝑝2 ,𝑝2 ,𝑖2,5,2 ,𝑛3,3,𝑝3 ,𝑝3 ,𝑖2,5,3 ,𝑛3,4 ,𝑝4 ,𝑝4 ,𝑖2,5,4,𝑡
𝜐=4 1
= [𝑊𝑖1 ,𝑛 ,𝑝(1),𝑝(2),𝑖 ,𝑡 𝑊𝑖2 ,𝑛 ,𝑝(1),𝑝(2) ,𝑖 ,𝑡 𝑊𝑖3 ,𝑛 ,𝑝(1),𝑝(2),𝑖 ,𝑡 𝑊𝑖4 ,𝑛 ,𝑝(1),𝑝(2),𝑖 ,𝑡 ]
2 1,1 3,1 1 1 2,5,1 1,1 3,2 2 2 2,5,2 1,1 3,3 3 3 2,5,3 1,1 3,4 4 4 2,5,4
(1) 𝑀𝜐−1 (𝑓) (2)
1
∑𝐿−1
𝑖=0 𝑣𝑖1,1 𝑑+𝑖 𝑝𝑙,0 ∑𝑓=0 𝑦𝑡,𝑙 𝑝𝑙,𝑖,𝑓 𝜑𝑙,𝑖,𝑓
𝑙
Where 𝑊𝑖 ,𝑛 ,𝑝(1),𝑝(2),𝑖 ,𝑡 [ (1) 𝑀𝜐−1 (𝑓) (2)
], 𝑙 = 1,2,3,4,
2,5,𝑙 √𝑁1 𝑁2 𝛾𝑡,𝑙 ∑𝐿−1 𝑣
𝑖=0 𝑖1,1 𝑑+𝑖 𝑝𝑙,1 ∑𝑓=0 𝑦𝑡,𝑙 𝑝𝑙,𝑖+𝐿,𝑓 𝜑𝑙,𝑖+𝐿,𝑓
1,1 3 𝑙 𝑙
2
2𝐿−1 2 𝑀𝜐−1
(1) (𝑓) (2)
𝛾𝑡,𝑙 = ∑ (𝑝 𝑖 ) | ∑ 𝑦𝑡,𝑙 𝑝𝑙,𝑖,𝑓 𝜑𝑙,𝑖,𝑓 |
𝑙,⌊ ⌋
𝑖=0 𝐿 𝑓=0
(1) (1) (1) (1) (2) (2)

and the mappings from 𝑖1 to 𝑖1,1 , 𝑛3,1 , 𝑛3,2 , 𝑛3,3 , 𝑛3,4 , 𝑝1 , 𝑝2 , 𝑝3 and 𝑝4 , and from 𝑖2 to 𝑖2,5,1 , 𝑖2,5,2 , 𝑖2,5,3 , 𝑖2,5,4 , 𝑝1 , 𝑝2 ,
(2) (2)
𝑝3 and 𝑝4 are as described above, including the ranges of the constituent indices of 𝑖1 and 𝑖2 .
(3)
For coefficients with 𝑘𝑙,𝑖,𝑓 = 0, amplitude and phase are set to zero, i.e., 𝑝(2)
𝑙,𝑖,𝑓
= 0 and 𝜑𝑙,𝑖,𝑓 = 0.
5.2.2.3 Reference signal (CSI-RS)

5.2.2.3.1 NZP CSI-RS
The UE can be configured with one or more NZP CSI-RS resource set configuration(s) as indicated by the higher layer
parameters CSI-ResourceConfig, and NZP-CSI-RS-ResourceSet. Each NZP CSI-RS resource set consists of K≥1 NZP
CSI-RS resource(s).
The following parameters for which the UE shall assume non-zero transmission power for CSI-RS resource are
configured via the higher layer parameter NZP-CSI-RS-Resource, CSI-ResourceConfig and NZP-CSI-RS-ResourceSet
for each CSI-RS resource configuration:
- nzp-CSI-RS-ResourceId determines CSI-RS resource configuration identity.
- periodicityAndOffset defines the CSI-RS periodicity and slot offset for periodic/semi-persistent CSI-RS. All the
CSI-RS resources within one set are configured with the same periodicity, while the slot offset can be same or
different for different CSI-RS resources.
- resourceMapping defines the number of ports, CDM-type, and OFDM symbol and subcarrier occupancy of the
CSI-RS resource within a slot that are given in Clause 7.4.1.5 of [4, TS 38.211].
- nrofPorts in resourceMapping defines the number of CSI-RS ports, where the allowable values are given in
Clause 7.4.1.5 of [4, TS 38.211].
- density in resourceMapping defines CSI-RS frequency density of each CSI-RS port per PRB, and CSI-RS PRB
offset in case of the density value of 1/2, where the allowable values are given in Clause 7.4.1.5 of [4, TS
38.211]. For density 1/2, the odd/even PRB allocation indicated in density is with respect to the common
resource block grid.
- cdm-Type in resourceMapping defines CDM values and pattern, where the allowable values are given in Clause
7.4.1.5 of [4, TS 38.211].
- powerControlOffset: which is the assumed ratio of PDSCH EPRE to NZP CSI-RS EPRE when UE derives CSI
feedback and takes values in the range of [-8, 15] dB with 1 dB step size.
- powerControlOffsetSS: which is the assumed ratio of NZP CSI-RS EPRE to SS/PBCH block EPRE.
- scramblingID defines scrambling ID of CSI-RS with length of 10 bits.
3GPP
Release 16 92 3GPP TS 38.214 V16.1.0 (2020-03)
- BWP-Id in CSI-ResourceConfig defines which bandwidth part the configured CSI-RS is located in.
- repetition in NZP-CSI-RS-ResourceSet is associated with a CSI-RS resource set and defines whether UE can
assume the CSI-RS resources within the NZP CSI-RS Resource Set are transmitted with the same downlink
spatial domain transmission filter or not as described in Clause 5.1.6.1.2. and can be configured only when the
higher layer parameter reportQuantity associated with all the reporting settings linked with the CSI-RS resource
set is set to 'cri-RSRP', 'cri-SINR' or 'none'.
- qcl-InfoPeriodicCSI-RS contains a reference to a TCI-State indicating QCL source RS(s) and QCL type(s). If the
TCI-State is configured with a reference to an RS with 'QCL-TypeD' association, that RS may be an SS/PBCH
block located in the same or different CC/DL BWP or a CSI-RS resource configured as periodic located in the
same or different CC/DL BWP.
- trs-Info in NZP-CSI-RS-ResourceSet is associated with a CSI-RS resource set and for which the UE can assume
that the antenna port with the same port index of the configured NZP CSI-RS resources in the NZP-CSI-RS-
ResourceSet is the same as described in Clause 5.1.6.1.1 and can be configured when reporting setting is not
configured or when the higher layer parameter reportQuantity associated with all the reporting settings linked
with the CSI-RS resource set is set to 'none'.
All CSI-RS resources within one set are configured with same density and same nrofPorts, except for the NZP CSI-RS
resources used for interference measurement.
The UE expects that all the CSI-RS resources of a resource set are configured with the same starting RB and number of
RBs and the same cdm-type.
The bandwidth and initial common resource block (CRB) index of a CSI-RS resource within a BWP, as defined in
Clause 7.4.1.5 of [4, TS 38.211], are determined based on the higher layer parameters nrofRBs and startingRB,
respectively, within the CSI-FrequencyOccupation IE configured by the higher layer parameter freqBand within the
CSI-RS-ResourceMapping IE. Both nrofRBs and startingRB are configured as integer multiples of 4 RBs, and the
reference point for startingRB is CRB 0 on the common resource block grid. If 𝑠𝑡𝑎𝑟𝑡𝑖𝑛𝑔𝑅𝐵 < 𝑁𝐵𝑊𝑃 , the UE shall
assume that the initial CRB index of the CSI-RS resource is 𝑁𝑖𝑛𝑖𝑡𝑖𝑎𝑙 𝑅𝐵 = 𝑁𝐵𝑊𝑃 , otherwise 𝑁𝑖𝑛𝑖𝑡𝑖𝑎𝑙 𝑅𝐵 = 𝑠𝑡𝑎𝑟𝑡𝑖𝑛𝑔𝑅𝐵.
𝑠𝑖𝑧𝑒 𝑠𝑡𝑎𝑟𝑡
If 𝑛𝑟𝑜𝑓𝑅𝐵𝑠 > 𝑁𝐵𝑊𝑃 + 𝑁𝐵𝑊𝑃 − 𝑁𝑖𝑛𝑖𝑡𝑖𝑎𝑙 𝑅𝐵 , the UE shall assume that the bandwidth of the CSI-RS resource is
𝐵𝑊 𝑠𝑖𝑧𝑒 𝑠𝑡𝑎𝑟𝑡 𝐵𝑊
𝑁𝐶𝑆𝐼−𝑅𝑆 = 𝑁𝐵𝑊𝑃 + 𝑁𝐵𝑊𝑃 − 𝑁𝑖𝑛𝑖𝑡𝑖𝑎𝑙 𝑅𝐵 , otherwise 𝑁𝐶𝑆𝐼−𝑅𝑆 = 𝑛𝑟𝑜𝑓𝑅𝐵𝑠. In all cases, the UE shall expect that
𝐵𝑊 𝑠𝑖𝑧𝑒
𝑁𝐶𝑆𝐼−𝑅𝑆 ≥ min (24, 𝑁𝐵𝑊𝑃 ).
5.2.2.4 Channel State Information – Interference Measurement (CSI-IM)

The UE can be configured with one or more CSI-IM resource set configuration(s) as indicated by the higher layer
parameter CSI-IM-ResourceSet. Each CSI-IM resource set consists of K≥1 CSI-IM resource(s).
The following parameters are configured via higher layer parameter CSI-IM-Resource for each CSI-IM resource
configuration:
- csi-IM-ResourceId determines CSI-IM resource configuration identity
- subcarrierLocation-p0 or subcarrierLocation-p1 defines subcarrier occupancy of the CSI-IM resource within a

slot for csi-IM-ResourceElementPattern set to 'pattern0' or 'pattern1', respectively.
- symbolLocation-p0 or symbolLocation-p1 defines OFDM symbol location of the CSI-IM resource within a slot
for csi-IM-ResourceElementPattern set to 'pattern0' or 'pattern1', respectively.
- periodicityAndOffset defines the CSI-IM periodicity and slot offset for periodic/semi-persistent CSI-IM.
- freqBand includes parameters to enable configuration of frequency-occupancy of CSI-IM
In each of the PRBs configured by freqBand, the UE shall assume each CSI-IM resource is located in,
- resource elements (k CSI − IM , l CSI − IM ) , (k CSI − IM , l CSI − IM + 1) , (k CSI − IM + 1, l CSI − IM ) and

(k CSI − IM + 1, l CSI − IM + 1) , if csi-IM-ResourceElementPattern is set to 'pattern0',
- resource elements (k CSI − IM , l CSI − IM ) , (k CSI − IM + 1, l CSI − IM ) , (k CSI − IM + 2, l CSI − IM ) and (k CSI − IM + 3, l CSI − IM )
if csi-IM-ResourceElementPattern is set to 'pattern1',
3GPP
Release 16 93 3GPP TS 38.214 V16.1.0 (2020-03)
where k CSI − IM and l CSI − IM are the configured frequency-domain location and time-domain location, respectively, given
by the higher layer parameters in the above list.
5.2.2.5 CSI reference resource definition

The CSI reference resource for a serving cell is defined as follows:
- In the frequency domain, the CSI reference resource is defined by the group of downlink physical resource
blocks corresponding to the band to which the derived CSI relates.
- In the time domain, the CSI reference resource for a CSI reporting in uplink slot n' is defined by a single
downlink slot n-nCSI_ref,
 2  DL 
- where n =  n '  and  DL and UL are the subcarrier spacing configurations for DL and UL, respectively
 2 UL 
- where for periodic and semi-persistent CSI reporting
- if a single CSI-RS/SSB resource is configured for channel measurement nCSI_ref is the smallest value
greater than or equal to 4 ⋅ 2µ𝐷𝐿 , such that it corresponds to a valid downlink slot, or
- if multiple CSI-RS/SSB resources are configured for channel measurement nCSI_ref is the smallest value
greater than or equal to 5  2DL , such that it corresponds to a valid downlink slot.
- where for aperiodic CSI reporting, if the UE is indicated by the DCI to report CSI in the same slot as the CSI
request, nCSI_ref is such that the reference resource is in the same valid downlink slot as the corresponding CSI
 ' slot

request, otherwise nCSI_ref is the smallest value greater than or equal to Z / N symb , such that slot n- nCSI_ref
corresponds to a valid downlink slot, where Z' corresponds to the delay requirement as defined in Clause 5.4.
- when periodic or semi-persistent CSI-RS/CSI-IM or SSB is used for channel/interference measurements, the
UE is not expected to measure channel/interference on the CSI-RS/CSI-IM/SSB whose last OFDM symbol is
received up to Z' symbols before transmission time of the first OFDM symbol of the aperiodic CSI reporting.
A slot in a serving cell shall be considered to be a valid downlink slot if:
- it comprises at least one higher layer configured downlink or flexible symbol, and
- it does not fall within a configured measurement gap for that UE
If there is no valid downlink slot for the CSI reference resource corresponding to a CSI Report Setting in a serving cell,
CSI reporting is omitted for the serving cell in uplink slot n'.
After the CSI report (re)configuration, serving cell activation, BWP change, or activation of SP-CSI, the UE reports a
CSI report only after receiving at least one CSI-RS transmission occasion for channel measurement and CSI-RS and/or
CSI-IM occasion for interference measurement no later than CSI reference resource and drops the report otherwise.
When DRX is configured, the UE reports a CSI report only if receiving at least one CSI-RS transmission occasion for
channel measurement and CSI-RS and/or CSI-IM occasion for interference measurement in DRX Active Time no later
than CSI reference resource and drops the report otherwise. When the UE is configured to monitor DCI format 2_6 and
if the UE configured by higher layer parameter [PS-Periodic_CSI_TransmitOrNot] to report CSI with the higher layer
parameter reportConfigType set to 'periodic' when drx-onDurationTimer is not started, the UE shall report CSI during
the time duration indicated by drx-onDurationTimer also outside active time according to the procedure described in
Clause 5.2.1.4 if receiving at least one CSI-RS transmission occasion for channel measurement and CSI-RS and/or CSI-
IM occasion for interference measurement during the time duration indicated by drx-onDurationTimer outside DRX
active time or in DRX Active Time no later than CSI reference resource and drops the report otherwise. When the UE is
configured to monitor DCI format 2_6 and if the UE configured by higher layer parameter [PS_Periodic_L1-
RSRP_TransmitOrNot] to report L1-RSRP with the higher layer parameter reportConfigType set to 'periodic' and
reportQuantity set to 'cri-RSRP' or 'ssb-Index-RSRP' when drx-onDurationTimer is not started, the UE shall report L1-
RSRP during the time duration indicated by drx-onDurationTimer also outside active time according to the procedure
described in clause 5.2.1.4 and when reportQuantity set to 'cri-RSRP' if receiving at least one CSI-RS transmission
occasion for channel measurement and CSI-RS and/or CSI-IM occasion for interference measurement during the time
3GPP
Release 16 94 3GPP TS 38.214 V16.1.0 (2020-03)
duration indicated by drx-onDurationTimer outside DRX active time or in DRX Active Time no later than CSI
reference resource and drops the report otherwise.
When deriving CSI feedback, the UE is not expected that a NZP CSI -RS resource for channel measurement overlaps
with CSI-IM resource for interference measurement or NZP CSI -RS resource for interference measurement.
If configured to report CQI index, in the CSI reference resource, the UE shall assume the following for the purpose of
deriving the CQI index, and if also configured, for deriving PMI and RI:
- The first 2 OFDM symbols are occupied by control signaling.
- The number of PDSCH and DM-RS symbols is equal to 12.
- The same bandwidth part subcarrier spacing configured as for the PDSCH reception
- The bandwidth as configured for the corresponding CQI report.
- The reference resource uses the CP length and subcarrier spacing configured for PDSCH reception
- No resource elements used by primary or secondary synchronization signals or PBCH.
- Redundancy Version 0.
- The ratio of PDSCH EPRE to CSI-RS EPRE is as given in Clause 4.1.
- Assume no REs allocated for NZP CSI-RS and ZP CSI-RS.
- Assume the same number of front loaded DM-RS symbols as the maximum front-loaded symbols configured by
the higher layer parameter maxLength in DMRS-DownlinkConfig.
- Assume the same number of additional DM-RS symbols as the additional symbols configured by the higher
layer parameter dmrs-AdditionalPosition.
- Assume the PDSCH symbols are not containing DM-RS.
- Assume PRB bundling size of 2 PRBs.
- The PDSCH transmission scheme where the UE may assume that PDSCH transmission would be performed
with up to 8 transmission layers as defined in Clause 7.3.1.4 of [4, TS 38.211]. For CQI calculation, the UE
should assume that PDSCH signals on antenna ports in the set [1000,…, 1000+ν-1] for ν layers would result in
signals equivalent to corresponding symbols transmitted on antenna ports [3000,…, 3000+P-1], as given by
𝑦 (3000) (𝑖) 𝑥 (0) (𝑖)

[ ⋯ ] = 𝑊(𝑖) [ ⋯ ]
𝑦 (3000+𝑃−1) (𝑖) 𝑥 (𝜈−1) (𝑖)

where x(i) = x (i)... x
( 0) ( −1)
(i) 
T
is a vector of PDSCH symbols from the layer mapping defined in Clause 7.3.1.4
of [4, TS 38.211], P  1,2,4,8,12,16,24,32 is the number of CSI-RS ports. If only one CSI-RS port is
configured, W(i) is 1. If the higher layer parameter reportQuantity in CSI-ReportConfig for which the CQI is
reported is set to either 'cri-RI-PMI-CQI' or 'cri-RI-LI-PMI-CQI', W(i) is the precoding matrix corresponding to
the reported PMI applicable to x(i). If the higher layer parameter reportQuantity in CSI-ReportConfig for which
the CQI is reported is set to 'cri-RI-CQI', W(i) is the precoding matrix corresponding to the procedure described
in Clause 5.2.1.4.2. If the higher layer parameter reportQuantity in CSI-ReportConfig for which the CQI is
reported is set to 'cri-RI-i1-CQI', W(i) is the precoding matrix corresponding to the reported i1 according to the
procedure described in Clause 5.2.1.4.2.The corresponding PDSCH signals transmitted on antenna ports
[3000,…,3000 + P - 1] would have a ratio of EPRE to CSI-RS EPRE equal to the ratio given in Clause 5.2.2.3.1.
5.2.3 CSI reporting using PUSCH

A UE shall perform aperiodic CSI reporting using PUSCH on serving cell c upon successful decoding of a DCI format
0_1 or DCI format 0_2 which triggers an aperiodic CSI trigger state.
3GPP
Release 16 95 3GPP TS 38.214 V16.1.0 (2020-03)
When a DCI format 0_1 schedules two PUSCH allocations, the aperiodic CSI report is carried on the second scheduled
PUSCH. When a DCI format 0_1 schedules more than two PUSCH allocations, the aperiodic CSI report is carried on
the penultimate scheduled PUSCH.
An aperiodic CSI report carried on the PUSCH supports wideband, and sub-band frequency granularities. An aperiodic
CSI report carried on the PUSCH supports Type I, Type II and Enhanced Type II CSI.
A UE shall perform semi-persistent CSI reporting on the PUSCH upon successful decoding of a DCI format 0_1 or DCI
format 0_2 which activates a semi-persistent CSI trigger state. DCI format 0_1 and DCI format 0_2 contains a CSI
request field which indicates the semi-persistent CSI trigger state to activate or deactivate. Semi-persistent CSI
reporting on the PUSCH supports Type I, Type II with wideband, and sub-band frequency granularities and Enhanced
Type II CSI. The PUSCH resources and MCS shall be allocated semi-persistently by an uplink DCI.
CSI reporting on PUSCH can be multiplexed with uplink data on PUSCH. CSI reporting on PUSCH can also be
performed without any multiplexing with uplink data from the UE.
Type I CSI feedback is supported for CSI Reporting on PUSCH. Type I wideband and sub-band CSI is supported for
CSI Reporting on the PUSCH. Type II CSI is supported for CSI Reporting on the PUSCH.
For Type I, Type II and Enhanced Type II CSI feedback on PUSCH, a CSI report comprises of two parts. Part 1 has a
fixed payload size and is used to identify the number of information bits in Part 2. Part 1 shall be transmitted in its
entirety before Part 2.
- For Type I CSI feedback, Part 1 contains RI (if reported), CRI (if reported), CQI for the first codeword (if
reported). Part 2 contains PMI (if reported) and contains the CQI for the second codeword (if reported) when RI
(if reported) is larger than 4.
- For Type II CSI feedback, Part 1 contains RI (if reported), CQI, and an indication of the number of non-zero
wideband amplitude coefficients per layer for the Type II CSI (see Clause 5.2.2.2.3). The fields of Part 1 – RI (if
reported), CQI, and the indication of the number of non-zero wideband amplitude coefficients for each layer –
are separately encoded. Part 2 contains the PMI of the Type II CSI. Part 1 and 2 are separately encoded.
- For Enhanced Type II CSI feedback, Part 1 contains RI, CQI, and an indication of the overall number of non-
zero amplitude coefficients across layers for the Enhanced Type II CSI (see Clause 5.2.2.2.5). The fields of Part
1 – RI, CQI, and the indication of the overall number of non-zero amplitude coefficients across layers – are
separately encoded. Part 2 contains the PMI of the Enhanced Type II CSI. Part 1 and 2 are separately encoded.
A Type II CSI report that is carried on the PUSCH shall be computed independently from any Type II CSI report that is
carried on the PUCCH formats 3 or 4 (see Clause 5.2.4 and 5.2.2).
When the higher layer parameter reportQuantity is configured with one of the values 'cri-RSRP' or 'ssb-Index-RSRP',
the CSI feedback consists of a single part.
For both Type I and Type II reports configured for PUCCH but transmitted on PUSCH, the determination of the
payload for CSI part 1 and CSI part 2 follows that of PUCCH as described in Clause 5.2.4.
When CSI reporting on PUSCH comprises two parts, the UE may omit a portion of the Part 2 CSI. Omission of Part 2
CSI is according to the priority order shown in Table 5.2.3-1, where N Rep is the number of CSI reports configured to be
carried on the PUSCH. Priority 0 is the highest priority and priority 2N Rep is the lowest priority and the CSI report n
corresponds to the CSI report with the nth smallest Prii,CSI(y,k,c,s) value among the N Rep CSI reports as defined in
Clause 5.2.5. The subbands for a given CSI report n indicated by the higher layer parameter csi-ReportingBand are
numbered continuously in increasing order with the lowest subband of csi-ReportingBand as subband 0. When omitting
Part 2 CSI information for a particular priority level, the UE shall omit all of the information at that priority level.
- For Enhanced Type II reports, for a given CSI report 𝑛, each reported element of indices 𝑖2,4,𝑙 𝑖2,5,𝑙 and 𝑖1,7,𝑙 ,
indexed by 𝑙, 𝑖 and 𝑓, is associated with a priority value Pri(𝑙, 𝑖, 𝑓) = 2 ⋅ 𝐿 ⋅ 𝜐 ⋅ 𝜋(𝑓) + 𝜐 ⋅ 𝑖 + 𝑙, with 𝜋(𝑓) =
(𝑓) (𝑓)
min (2 ⋅ 𝑛3,𝑙 , 2 ⋅ (𝑁3 − 𝑛3,𝑙 ) − 1) with 𝑙 = 1,2, … , 𝜐, 𝑖 = 0,1, … ,2𝐿 − 1, and 𝑓 = 0,1, … , 𝑀𝜐 − 1, and where
(𝑓)
𝑛3,𝑙 is defined in Clause 5.2.2.2.5. The element with the highest priority has the lowest associated value
Pri(𝑙, 𝑖, 𝑓). Omission of Part 2 CSI is according to the priority order shown in Table 5.2.3-1, where
- Group 0 includes indices 𝑖1,1, 𝑖1,2 and 𝑖1,8,𝑙 (𝑙 = 1, … , 𝜐).
3GPP
Release 16 96 3GPP TS 38.214 V16.1.0 (2020-03)
- Group 1 includes indices 𝑖1,5 (if reported), 𝑖1,6,𝑙 , the 𝜐2𝐿𝑀𝜐 − ⌊𝐾 𝑁𝑍 /2⌋ highest priority elements of 𝑖1,7,𝑙 ,
𝑖2,3,𝑙 , the ⌈𝐾 𝑁𝑍 /2⌉ − 𝜐 highest priority elements of 𝑖2,4,𝑙 and the ⌈𝐾 𝑁𝑍 /2⌉ − 𝜐 highest priority elements of
𝑖2,5,𝑙 (𝑙 = 1, … , 𝜐).
- Group 2 includes the ⌊𝐾 𝑁𝑍 /2⌋ lowest priority elements of 𝑖1,7,𝑙 , the ⌊𝐾 𝑁𝑍 /2⌋ lowest priority elements of 𝑖2,4,𝑙
and the ⌊𝐾 𝑁𝑍 /2⌋ lowest priority elements of 𝑖2,5,𝑙 (𝑙 = 1, … , 𝜐).
Table 5.2.3-1: Priority reporting levels for Part 2 CSI
Priority 0:
For CSI reports 1 to 𝑁𝑅𝑒𝑝 , Group 0 CSI for CSI reports

configured as 'typeII-r16' or 'typeII-PortSelection-r16'; Part 2
wideband CSI for CSI reports configured otherwise
Priority 1:
Group 1 CSI for CSI report 1, if configured as 'typeII-r16' or

'typeII-PortSelection-r16'; Part 2 subband CSI of even
subbands for CSI report 1, if configured otherwise
Priority 2:

'typeII-PortSelection-r16'; Part 2 subband CSI of odd
Priority 3:

'typeII-PortSelection-r16'; Part 2 subband CSI of even
Priority 4:

'typeII-PortSelection-r16'. Part 2 subband CSI of odd
Priority 2𝑁𝑅𝑒𝑝 − 1:
Group 1 CSI for CSI report 𝑁𝑅𝑒𝑝 , if configured as 'typeII-r16'

or 'typeII-PortSelection-r16'; Part 2 subband CSI of even
subbands for CSI report 𝑁𝑅𝑒𝑝 , if configured otherwise
Priority 2𝑁𝑅𝑒𝑝 :
Group 2 CSI for CSI report 𝑁𝑅𝑒𝑝 , if configured as 'typeII-r16'

or 'typeII-PortSelection-r16'; Part 2 subband CSI of odd
subbands for CSI report 𝑁𝑅𝑒𝑝 , if configured otherwise
When the UE is scheduled to transmit a transport block on PUSCH multiplexed with a CSI report(s), Part 2 CSI is
 −1 
PUSCH
Nsymb,all CUL−SCH −1
omitted only when ( O
CSI-2 + LCSI-2 )   PUSCH
offset   M scUCI ( l )  K r  is larger than
 l =0 r =0

3GPP
Release 16 97 3GPP TS 38.214 V16.1.0 (2020-03)
 Nsymb ,all −1 UCI 

PUSCH
   M SC (l )  − QACK all M sc ( l )
'
− QCSI
'
−1
, where parameters OCSI-2 , LCSI-2 ,  offset
PUSCH PUSCH
, N symb, , UCI , CUL-SCH , K r ,
 l =0 
Q 'CSI-1 , Q 'ACK and  are defined in Clause 6.3.2.4 of [5, TS 38.212].
Part 2 CSI is omitted level by level, beginning with the lowest priority level until the lowest priority level is reached
 −1 
PUSCH
Nsymb,all CUL−SCH −1
which causes the ( O
CSI-2 + LCSI-2 )   PUSCH
offset   M scUCI ( l )  K r  to be less than or equal to
 l =0 r =0 
 − 
PUSCH
N symb ,all 1
   M SC UCI
(l )  − QACK'
− QCSI
'
−1
.
 l = 0 
When part 2 CSI is transmitted on PUSCH with no transport block, lower priority bits are omitted until Part 2 CSI code
rate, which is given by (𝑂CSI‑2 + 𝐿CSI‑2 )/(𝑁𝐿 ⋅ 𝑄′CSI,2 ⋅ 𝑄𝑚 ) where 𝑂CSI‑2 , 𝐿CSI‑2 , 𝑁𝐿 , 𝑄′CSI,2 , 𝑄𝑚 are given in clause
6.3.2.4 of [5, 38.212] before HARQ-ACK puncturing part 2 CSI if any, is below a threshold code rate cT lower than
one, where
R
cT =
 CSI-part2
offset
CSI − part2
-  offset is the CSI offset value from Table 9.3-2 of [6, TS 38.213]
- R is signaled code rate in DCI
If the UE is in an active semi-persistent CSI reporting configuration on PUSCH, the CSI reporting is deactivated when
either the downlink BWP or the uplink BWP is changed. Another activation command is required to enable the semi-
persistent CSI reporting.
5.2.4 CSI reporting using PUCCH

A UE is semi-statically configured by higher layers to perform periodic CSI Reporting on the PUCCH. A UE can be
configured by higher layers for multiple periodic CSI Reports corresponding to multiple higher layer configured CSI
Reporting Settings, where the associated CSI Resource Settings are higher layer configured. Periodic CSI reporting on
PUCCH formats 2, 3, 4 supports Type I CSI with wideband granularity.
A UE shall perform semi-persistent CSI reporting on the PUCCH applied starting from the first slot that is after slot 𝑛 +
3𝑁𝑠𝑙𝑜𝑡 when the UE would transmit a PUCCH with HARQ-ACK information in slot n corresponding to the
PDSCH carrying the activation command described in clause 6.1.3.16 of [10, TS 38.321] where  is the SCS
configuration for the PUCCH. The activation command will contain one or more Reporting Settings where the
associated CSI Resource Settings are configured. Semi-persistent CSI reporting on the PUCCH supports Type I CSI.
Semi-persistent CSI reporting on the PUCCH format 2 supports Type I CSI with wideband frequency granularity. Semi-
persistent CSI reporting on PUCCH formats 3 or 4 supports Type I CSI with wideband and sub-band frequency
granularities and Type II CSI Part 1.
When the PUCCH carry Type I CSI with wideband frequency granularity, the CSI payload carried by the PUCCH
format 2 and PUCCH formats 3, or 4 are identical and the same irrespective of RI (if reported), CRI (if reported). For
type I CSI sub-band reporting on PUCCH formats 3, or 4, the payload is split into two parts. The first part contains RI
(if reported), CRI (if reported), CQI for the first codeword. The second part contains PMI and contains the CQI for the
second codeword when RI > 4.
A semi-persistent report carried on the PUCCH formats 3 or 4 supports Type II CSI feedback, but only Part 1 of Type II
CSI feedback (See Clause 5.2.2 and 5.2.3). Supporting Type II CSI reporting on the PUCCH formats 3 or 4 is a UE
capability type2-SP-CSI-Feedback-LongPUCCH. A Type II CSI report (Part 1 only) carried on PUCCH formats 3 or 4
shall be calculated independently of any Type II CSI reports carried on the PUSCH (see Clause 5.2.3).
When the UE is configured with CSI Reporting on PUCCH formats 2, 3 or 4, each PUCCH resource is configured for
each candidate UL BWP.
3GPP
Release 16 98 3GPP TS 38.214 V16.1.0 (2020-03)
If the UE is in an active semi-persistent CSI reporting configuration on PUCCH and has not received a deactivation
command, the CSI reporting takes place when the BWP in which the reporting is configured to take place is the active
BWP, otherwise the CSI reporting is suspended.
A UE is not expected to report CSI with a total number of UCI bits and CRC bits larger than 115 bits when configured
with PUCCH format 4. For CSI reports transmitted on a PUCCH, if all CSI reports consist of one part, the UE may omit
a portion of CSI reports. Omission of CSI is according to the priority order determined from the Pri i,CSI(y,k,c,s) value as
defined in Clause 5.2.5. CSI report is omitted beginning with the lowest priority level until the CSI report code rate is
less or equal to the one configured by the higher layer parameter maxCodeRate.
If any of the CSI reports consist of two parts, the UE may omit a portion of Part 2 CSI. Omission of Part 2 CSI is
according to the priority order shown in Table 5.2.3-1. Part 2 CSI is omitted beginning with the lowest priority level
until the Part 2 CSI code rate is less or equal to the one configured by higher layer parameter maxCodeRate.
5.2.5 Priority rules for CSI reports

CSI reports are associated with a priority value Pri𝑖𝐶𝑆𝐼 (𝑦, 𝑘, 𝑐, 𝑠) = 2 ∙ 𝑁𝑐𝑒𝑙𝑙𝑠 ∙ 𝑀𝑠 ∙ 𝑦 + 𝑁𝑐𝑒𝑙𝑙𝑠 ∙ 𝑀𝑠 ∙ 𝑘 + 𝑀𝑠 ∙ 𝑐 + 𝑠
where
- y = 0 for aperiodic CSI reports to be carried on PUSCH y = 1 for semi-persistent CSI reports to be carried on
PUSCH, y = 2 for semi-persistent CSI reports to be carried on PUCCH and y = 3 for periodic CSI reports to be
carried on PUCCH;
- k = 0 for CSI reports carrying L1-RSRP or L1-SINR and k = 1 for CSI reports not carrying L1-RSRP or L1-
SINR;
- c is the serving cell index and 𝑁𝑐𝑒𝑙𝑙𝑠 is the value of the higher layer parameter maxNrofServingCells;
- s is the reportConfigID and M s is the value of the higher layer parameter maxNrofCSI-ReportConfigurations.
A first CSI report is said to have priority over second CSI report if the associated Pri iCSI ( y, k , c, s ) value is lower for the
first report than for the second report.
Two CSI reports are said to collide if the time occupancy of the physical channels scheduled to carry the CSI reports
overlap in at least one OFDM symbol and are transmitted on the same carrier. When a UE is configured to transmit two
colliding CSI reports,
- if y values are different between the two CSI reports, the following rules apply except for the case when one of
the y value is 2 and the other y value is 3 (for CSI reports transmitted on PUSCH, as described in Clause 5.2.3;
for CSI reports transmitted on PUCCH, as described in Clause 5.2.4):
- The CSI report with higher Pri iCSI ( y, k , c, s ) value shall not be sent by the UE.
- otherwise, the two CSI reports are multiplexed or either is dropped based on the priority values, as described in
Clause 9.2.5.2 in [6, TS 38.213].
If a semi-persistent CSI report to be carried on PUSCH overlaps in time with PUSCH data transmission in one or more
symbols on the same carrier, and if the earliest symbol of these PUSCH channels starts no earlier than N 2+d2,1 symbols
after the last symbol of the DCI scheduling the PUSCH where d2,1 is the maximum of the d2,1 associated with the
PUSCH carrying semi-persistent CSI report and the PUSCH with data transmission, the CSI report shall not be
transmitted by the UE. Otherwise, if the timeline requirement is not satisfied this is an error case.
If a UE would transmit a first PUSCH that includes semi-persistent CSI reports and a second PUSCH that includes an
UL-SCH and the first PUSCH transmission would overlap in time with the second PUSCH transmission, the UE does
not transmit the first PUSCH and transmits the second PUSCH. The UE expects that the first and second PUSCH
transmissions satisfy the above timing conditions for PUSCH transmissions that overlap in time when at least one of the
first or second PUSCH transmissions is in response to a DCI format detection by the UE.
3GPP
Release 16 99 3GPP TS 38.214 V16.1.0 (2020-03)
5.3 UE PDSCH processing procedure time

If the first uplink symbol of the PUCCH which carries the HARQ-ACK information, as defined by the assigned HARQ-
ACK timing K1 and the PUCCH resource to be used and including the effect of the timing advance, starts no earlier than
at symbol L1, where L1 is defined as the next uplink symbol with its CP starting after
−
Tproc ,1 = ( N1 + d1,1 )(2048 + 144)   2  TC after the end of the last symbol of the PDSCH carrying the TB being
acknowledged, then the UE shall provide a valid HARQ-ACK message.
- N1 is based on µ of table 5.3-1 and table 5.3-2 for UE processing capability 1 and 2 respectively, where µ
corresponds to the one of (µPDCCH, µPDSCH, µUL) resulting with the largest Tproc,1, where the µPDCCH corresponds to
the subcarrier spacing of the PDCCH scheduling the PDSCH, the µPDSCH corresponds to the subcarrier spacing of
the scheduled PDSCH, and µUL corresponds to the subcarrier spacing of the uplink channel with which the
HARQ-ACK is to be transmitted, and κ is defined in clause 4.1 of [4, TS 38.211].
- If the PDSCH DM-RS position 𝑙1 for the additional DM-RS in Table 7.4.1.1.2-3 in clause 7.4.1.1.2 of [4, TS
38.211] is 𝑙1 = 12 then N1,0=14 in Table 5.3-1, otherwise N1,0=13.
- If the UE is configured with multiple active component carriers, the first uplink symbol which carries the
HARQ-ACK information further includes the effect of timing difference between the component carriers as
given in [11, TS 38.133].
- For the PDSCH mapping type A as given in clause 7.4.1.1 of [4, TS 38.211]: if the last symbol of PDSCH is on
the i-th symbol of the slot where i < 7, then d1,1 = 7 - i, otherwise d1,1 = 0
- For UE processing capability 1: If the PDSCH is mapping type B as given in clause 7.4.1.1 of [4, TS 38.211],
and
- if the number of PDSCH symbols allocated is L ≥ 7, then d1,1 = 0,
- if the number of PDSCH symbols allocated is L ≥ 4 and L ≤ 6, then d1,1 = 7- L.
- if the number of PDSCH symbols allocated is L = 3 then d1,1 = 3 + min (d,1), where d is the number of
overlapping symbols of the scheduling PDCCH and the scheduled PDSCH.
- if the number of PDSCH symbols allocated is 2, then d1,1 = 3+d, where d is the number of overlapping
symbols of the scheduling PDCCH and the scheduled PDSCH.
- For UE processing capability 2: If the PDSCH is mapping type B as given in clause 7.4.1.1 of [4, TS 38.211],
- if the number of PDSCH symbols allocated is L ≥ 7, then d1,1 = 0,
- if the number of PDSCH symbols allocated is L ≥ 3 and L ≤ 6, then d1,1 is the number of overlapping symbols
of the scheduling PDCCH and the scheduled PDSCH,
- if the number of PDSCH symbols allocated is 2,
- if the scheduling PDCCH was in a 3-symbol CORESET and the CORESET and the PDSCH had the same
starting symbol, then d1,1 = 3,
- otherwise d1,1 is the number of overlapping symbols of the scheduling PDCCH and the scheduled
PDSCH.
- For UE processing capability 2 with scheduling limitation when µPDSCH = 1, if the scheduled RB allocation
exceeds 136 RBs, the UE defaults to capability 1 processing time. The UE may skip decoding a number of
PDSCHs with last symbol within 10 symbols before the start of a PDSCH that is scheduled to follow Capability
2, if any of those PDSCHs are scheduled with more than 136 RBs with 30kHz SCS and following Capability 1
processing time.
- For a UE that supports capability 2 on a given cell, the processing time according to UE processing capability 2
is applied if the high layer parameter processingType2Enabled in PDSCH-ServingCellConfig is configured for
the cell and set to enable.
3GPP
Release 16 100 3GPP TS 38.214 V16.1.0 (2020-03)
- If this PUCCH resource is overlapping with another PUCCH or PUSCH resource, then HARQ-ACK is
multiplexed following the procedure in clause 9.2.5 of [6, TS 38.213], otherwise the HARQ-ACK message is
transmitted on PUCCH.
Otherwise the UE may not provide a valid HARQ-ACK corresponding to the scheduled PDSCH. The value of Tproc,1 is
used both in the case of normal and extended cyclic prefix.
Table 5.3-1: PDSCH processing time for PDSCH processing capability 1
PDSCH decoding time N1 [symbols]

dmrs-AdditionalPosition = pos0 in dmrs-AdditionalPosition ≠ pos0 in
DMRS-DownlinkConfig in both of DMRS-DownlinkConfig in either of
 dmrs-DownlinkForPDSCH-
MappingTypeA, dmrs-
dmrs-DownlinkForPDSCH-
MappingTypeA, dmrs-
DownlinkForPDSCH-MappingTypeB DownlinkForPDSCH-MappingTypeB
or if the higher layer parameter is not
configured
0 8 N1,0
1 10 13
2 17 20
3 20 24
Table 5.3-2: PDSCH processing time for PDSCH processing capability 2
PDSCH decoding time N1 [symbols]

 dmrs-AdditionalPosition = pos0 in
DMRS-DownlinkConfig in both of
dmrs-DownlinkForPDSCH-MappingTypeA, dmrs-DownlinkForPDSCH-MappingTypeB
0 3
1 4.5
2 9 for frequency range 1
5.3.1 Application delay of the minimum scheduling offset restriction

When the UE is scheduled with DCI format 0_1 or 1_1 with a ['Minimum applicable scheduling offset indicator'] field,
it shall determine the K0min and K2min values to be applied, while the previously applied K0min and K2min values are
applied until the new values take effect after application delay. Change of applied minimum scheduling offset
restriction indication carried by DCI in slot n, shall be applied in slot n+X of the scheduling cell. The UE does not
expect to be scheduled with DCI format 0_1 or 1_1 with ['Minimum applicable scheduling offset indicator'] field
indicating another change to the applied K0min or K2min for the same active BWP before slot n+X of the scheduling
cell.
When the DCI format 0_1 or 1_1 with ['Minimum applicable scheduling offset indicator'] field indicating a change to
the applied K0min or K2min is contained within the first three symbols of the slot, the value of application delay X is
2𝜇𝑃𝐷𝐶𝐶𝐻
determined by, 𝑋 = 𝑚𝑎𝑥 (⌈𝐾0𝑚𝑖𝑛𝑂𝑙𝑑 ∙ 𝜇𝑃𝐷𝑆𝐶𝐻 ⌉ , 𝑍𝜇 ) where K0minOld is the currently applied K0min value of the active DL
2
BWP in the scheduled cell, and Zµ is determined by the subcarrier spacing of the active DL BWP in the scheduling cell,
and given in Table 5.3.1-1 and µPDCCH and µPDSCH are the sub-carrier spacing configurations for PDCCH and PDSCH,
respectively
When the DCI format 0_1 or 1_1 with ['Minimum applicable scheduling offset indicator'] field is received outside the
first [three] symbols of the slot, value of Zµ from Table 5.3.1-1 is incremented by one before determining the application
delay X.
Table 5.3.1-1: Definition of Zµ
µ Zµ
0 1
1 1
2 2
3 2
3GPP
Release 16 101 3GPP TS 38.214 V16.1.0 (2020-03)
5.4 UE CSI computation time

When the CSI request field on a DCI triggers a CSI report(s) on PUSCH, the UE shall provide a valid CSI report for the
n-th triggered report,
- if the first uplink symbol to carry the corresponding CSI report(s) including the effect of the timing advance,
starts no earlier than at symbol Zref , and
- if the first uplink symbol to carry the n-th CSI report including the effect of the timing advance, starts no earlier
than at symbol Z'ref(n),
−
where Zref is defined as the next uplink symbol with its CP starting Tproc ,CSI = (Z )(2048 + 144)   2  TC after the end
of the last symbol of the PDCCH triggering the CSI report(s), and where Z'ref(n), is defined as the next uplink symbol
−
with its CP starting T ' proc ,CSI = (Z ')(2048 + 144)   2  TC after the end of the last symbol in time of the latest of:
aperiodic CSI-RS resource for channel measurements, aperiodic CSI-IM used for interference measurements, and
aperiodic NZP CSI-RS for interference measurement, when aperiodic CSI-RS is used for channel measurement for the
n-th triggered CSI report.
If the PUSCH indicated by the DCI is overlapping with another PUCCH or PUSCH, then the CSI report(s) are
multiplexed following the procedure in clause 9.2.5 of [6, TS 38.213] and clause 5.2.5 when applicable, otherwise the
CSI report(s) are transmitted on the PUSCH indicated by the DCI.
When the CSI request field on a DCI triggers a CSI report(s) on PUSCH, if the first uplink symbol to carry the
corresponding CSI report(s) including the effect of the timing advance, starts earlier than at symbol Zref,
- the UE may ignore the scheduling DCI if no HARQ-ACK or transport block is multiplexed on the PUSCH.
When the CSI request field on a DCI triggers a CSI report(s) on PUSCH, if the first uplink symbol to carry the n-th CSI
report including the effect of the timing advance, starts earlier than at symbol Z'ref(n),
- the UE may ignore the scheduling DCI if the number of triggered reports is one and no HARQ-ACK or transport
block is multiplexed on the PUSCH
- Otherwise, the UE is not required to update the CSI for the n-th triggered CSI report.
Z, Z' and µ are defined as:
𝑍= max (𝑍(𝑚)) and 𝑍′ = max (𝑍′(𝑚)), where M is the number of updated CSI report(s) according to
𝑚=0,…,𝑀−1 𝑚=0,…,𝑀−1
Clause 5.2.1.6, (𝑍(𝑚), 𝑍′(𝑚)) corresponds to the m-th updated CSI report and is defined as
- (𝑍1 , 𝑍1′ ) of the table 5.4-1 if the CSI is triggered without a PUSCH with either transport block or HARQ-ACK or
both when L = 0 CPUs are occupied (according to Clause 5.2.1.6) and the CSI to be transmitted is a single CSI
and corresponds to wideband frequency-granularity where the CSI corresponds to at most 4 CSI-RS ports in a
single resource without CRI report and where CodebookType is set to 'typeI-SinglePanel' or where
reportQuantity is set to 'cri-RI-CQI', or
- (𝑍1 , 𝑍1′ ) of the table 5.4-2 if the CSI to be transmitted corresponds to wideband frequency-granularity where the
CSI corresponds to at most 4 CSI-RS ports in a single resource without CRI report and where CodebookType is
set to 'typeI-SinglePanel' or where reportQuantity is set to 'cri-RI-CQI', or
- (𝑍1 , 𝑍1′ ) of the table 5.4-2 if the CSI to be transmitted corresponds to wideband frequency-granularity where the
reportQuantity is set to 'ssb-Index-SINR', or reportQuantity is set to 'cri-SINR', or
- (𝑍3 , 𝑍3′ ) of the table 5.4-2 if reportQuantity is set to 'cri-RSRP' or 'ssb-Index-RSRP', where 𝑋µ is according to
UE reported capability beamReportTiming and KBl is according to UE reported capability beamSwitchTiming as
defined in [13, TS 38.306], or
- (𝑍2 , 𝑍2′ ) of table 5.4-2 otherwise.
- µ of table 5.4-1 and table 5.4-2 corresponds to the min (µPDCCH, µCSI-RS, µUL) where the µPDCCH corresponds to the
subcarrier spacing of the PDCCH with which the DCI was transmitted and µUL corresponds to the subcarrier
3GPP
Release 16 102 3GPP TS 38.214 V16.1.0 (2020-03)
spacing of the PUSCH with which the CSI report is to be transmitted and µCSI-RS corresponds to the minimum
subcarrier spacing of the aperiodic CSI-RS triggered by the DCI
Table 5.4-1: CSI computation delay requirement 1
 Z1 [symbols]
Z1 Z'1
0 10 8
1 13 11
2 25 21
3 43 36
Table 5.4-2: CSI computation delay requirement 2
 Z1 [symbols] Z2 [symbols] Z3 [symbols]

Z1 Z'1 Z2 Z'2 Z3 Z'3
0 22 16 40 37 22 X0
1 33 30 72 69 33 X1
2 44 42 141 140 min(44,X2+ KB1) X2
3 97 85 152 140 min(97, X3+ KB2) X3
5.5 UE PDSCH reception preparation time with cross carrier

scheduling with different subcarrier spacings for PDCCH
and PDSCH
This clause applies only if the PDCCH carrying the scheduling DCI is received on one carrier with one OFDM
subcarrier spacing, and the PDSCH scheduled to be received by the DCI is on another carrier with another OFDM
subcarrier spacing.
If the µPDCCH < µPDSCH, the UE is expected to receive the scheduled PDSCH, if the first symbol in the PDSCH
allocation, including the DM-RS, as defined by the slot offset K0 and the start and length indicator SLIV of the
scheduling DCI starts no earlier than the first symbol of the PDSCH slot starting at least Npdsch PDCCH symbols after
the end of the PDCCH scheduling the PDSCH, not taking into account the effect of receive timing difference between
the scheduling cell and the scheduled cell.
If the µPDCCH > µPDSCH, the UE is expected to receive the scheduled PDSCH, if the first symbol in the PDSCH
allocation, including the DM-RS, as defined by the slot offset K0 and the start and length indicator SLIV of the
scheduling DCI starts no earlier than Npdsch PDCCH symbols after the end of the PDCCH scheduling the PDSCH, not
taking into account the effect of receive timing difference between the scheduling cell and the scheduled cell.
Table 5.5-1: Npdsch as a function of the subcarrier spacing of the scheduling PDCCH
µPDCCH Npdsch [symbols]

0 4
1 5
2 10
3 14
6 Physical uplink shared channel related procedure

6.1 UE procedure for transmitting the physical uplink shared
channel
PUSCH transmission(s) can be dynamically scheduled by an UL grant in a DCI, or the transmission can correspond to a
configured grant Type 1 or Type 2. The configured grant Type 1 PUSCH transmission is semi-statically configured to
operate upon the reception of higher layer parameter of configuredGrantConfig including rrc-ConfiguredUplinkGrant
without the detection of an UL grant in a DCI. The configured grant Type 2 PUSCH transmission is semi-persistently
scheduled by an UL grant in a valid activation DCI according to Clause 10.2 of [6, TS 38.213] after the reception of
3GPP
Release 16 103 3GPP TS 38.214 V16.1.0 (2020-03)
higher layer parameter configuredGrantConfig not including rrc-ConfiguredUplinkGrant. If Configuredgrantconfig-

ToAddModList-r16 is configured, more than one configured grant configuration of configured grant Type 1 and/or
configured grant Type 2 may be active at the same time on an active BWP of a serving cell.
For the PUSCH transmission corresponding to a Type 1 configured grant or a Type 2 configured grant activated by DCI
format 0_0 or 0_1, the parameters applied for the transmission are provided by configuredGrantConfig except for
dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, scaling of UCI-OnPUSCH, which are provided
by pusch-Config. For the PUSCH transmission corresponding to a Type 2 configured grant activated by DCI format
0_2, the parameters applied for the transmission are provided by configuredGrantConfig except for
dataScramblingIdentityPUSCH, txConfig, codebookSubset-ForDCIFormat0_2, maxRank-ForDCIFormat0_2, scaling
of UCI-OnPUSCH, ResourceAllocationType1-granularity-ForDCIFormat0_2 provided by pusch-Config. If the UE is
provided with transformPrecoder in configuredGrantConfig, the UE applies the higher layer parameter tp-pi2BPSK, if
provided in pusch-Config, according to the procedure described in Clause 6.1.4 for the PUSCH transmission
corresponding to a configured grant.
For the PUSCH retransmission scheduled by a PDCCH with CRC scrambled by CS-RNTI with NDI=1, the parameters
in pusch-Config are applied for the PUSCH transmission except for p0-NominalWithoutGrant, p0-PUSCH-Alpha,
powerControlLoopToUse, pathlossReferenceIndex described in Clause 7.1 of [6, TS 38.213], mcs-Table, mcs-
TableTransformPrecoder described in Clause 6.1.4.1 and transformPrecoder described in Clause 6.1.3.
For a UE configured with two uplinks in a serving cell, PUSCH retransmission for a TB on the serving cell is not expected
to be on a different uplink than the uplink used for the PUSCH initial transmission of that TB.
A UE shall upon detection of a PDCCH with a configured DCI format 0_0, 0_1 or 0_2 transmit the corresponding PUSCH
as indicated by that DCI. Upon detection of a DCI format 0_1 or 0_2 with "UL-SCH indicator" set to "0" and with a non-
zero "CSI request" where the associated "reportQuantity" in CSI-ReportConfig set to "none" for all CSI report(s) triggered
by "CSI request" in this DCI format 0_1 or 0_2, the UE ignores all fields in this DCI except the "CSI request" and the UE
shall not transmit the corresponding PUSCH as indicated by this DCI format 0_1 or 0_2. When the UE is scheduled with
multiple PUSCHs by a DCI, HARQ process ID indicated by this DCI applies to the first PUSCH, as described in clause
6.1.2.1, HARQ process ID is then incremented by 1 for each subsequent PUSCH(s) in the scheduled order, with modulo
16 operation applied. For any HARQ process ID(s) in a given scheduled cell, the UE is not expected to transmit a PUSCH
that overlaps in time with another PUSCH. For any two HARQ process IDs in a given scheduled cell, if the UE is
scheduled to start a first PUSCH transmission starting in symbol j by a PDCCH ending in symbol i, the UE is not expected
to be scheduled to transmit a PUSCH starting earlier than the end of the first PUSCH by a PDCCH that ends later than
symbol i. The UE is not expected to be scheduled to transmit another PUSCH by DCI format 0_0, 0_1 or 0_2 scrambled
by C-RNTI or MCS-C-RNTI for a given HARQ process until after the end of the expected transmission of the last PUSCH
for that HARQ process.
If a UE is configured by higher layer parameter PDCCH-Config that contains two different values of
CORESETPoolIndex in ControlResourceSet for the active BWP of a serving cell and PDCCHs that schedule two non-
overlapping in time domain PUSCHs are associated to different ControlResourceSets having different values of
CORESETPoolIndex, for any two HARQ process IDs in a given scheduled cell, if the UE is scheduled to start a first
PUSCH transmission starting in symbol j by a PDCCH associated with a value of CORESETpoolIndex ending in
symbol i, the UE can be scheduled to transmit a PUSCH starting earlier than the end of the first PUSCH by a PDCCH
associated with a different value of CORESETpoolIndex that ends later than symbol i.
A UE is not expected to be scheduled by a PDCCH ending in symbol 𝑖 to transmit a PUSCH on a given serving cell
overlapping in time with a transmission occasion, where the UE is allowed to transmit a PUSCH with configured grant
according to [10, TS38.321], starting in a symbol 𝑗 on the same serving cell if the end of symbol 𝑖 is not at least 𝑁2
symbols before the beginning of symbol 𝑗. The value 𝑁2 in symbols is determined according to the UE processing
capability defined in Clause 6.4, and 𝑁2 and the symbol duration are based on the minimum of the subcarrier spacing
corresponding to the PUSCH with configured grant and the subcarrier spacing of the PDCCH scheduling the PUSCH.
If a UE receives an ACK for a given HARQ process in CG-DFI in a PDCCH ending in symbol i to terminate a transport
block repetition in a PUSCH transmission on a given serving cell with the same HARQ process after symbol i, the UE
is expected to terminate the repetition of the transport block in a PUSCH transmission starting from a symbol j if the
gap between the end of PDCCH of symbol i and the start of the PUSCH transmission in symbol j is equal to or more
than N2 symbols. The value N2 in symbols is determined according to the UE processing capability defined in Clause
6.4, and N2 and the symbol duration are based on the minimum of the subcarrier spacing corresponding to the PUSCH
and the subcarrier spacing of the PDCCH indicating CG-DFI.
3GPP
Release 16 104 3GPP TS 38.214 V16.1.0 (2020-03)
[If [a UE reports the capability of intra-UE prioritization], and if a PUSCH corresponding to a configured grant and a
PUSCH scheduled by a PDCCH on a serving cell are partially or fully overlapping in time,
- If the PUSCH corresponding to the configured grant has priority in configuredGrantConfig set to 1 (i.e., high
priority), and the PUSCH scheduled by the PDCCH is indicated as low priority by having the [priority indicator]
field in the scheduling DCI set to 0 or by not having the [priority indicator] field present in the scheduling DCI,
the UE is expected to transmit the PUSCH corresponding to the configured grant, and cancel the PUSCH
transmission scheduled by the PDCCH at latest starting at the first symbol of the PUSCH corresponding to the
configured grant.
- Otherwise, the UE shall cancel the PUSCH transmission corresponding to the configured grant at latest starting
M symbols after the end of the last symbol of the PDCCH carrying the DCI scheduling the PUSCH, and transmit
the PUSCH scheduled by the PDCCH, where
- M = Tproc,2 +d1, where Tproc,2 is given by clause 6.4 for the corresponding PUSCH timing capability assuming
d2,1 = 0 and d1 is determined by the reported UE capability [XXXXX],
- In this case, the UE is not expected to be scheduled for the PUSCH by the PDCCH where the PUSCH starts
earlier than N symbols after the end of the last symbol of the PDCCH, where
- N = Tproc,2 + d2, where Tproc,2 is the PUSCH preparation time of the PUSCH scheduled by the PDCCH
using the associated PUSCH timing capability according to clause 6.4 and d2 is determined by the
reported UE capability [YYYYY].
- In case of PUSCH repetitions, the overlapping handling is performed for each PUSCH repetition separately.
- The UE is not expected to be scheduled for another PUSCH by a PDCCH where this PUSCH starts no earlier
than the end of the prioritized transmitted PUSCH and before the end of the time domain allocation of the
cancelled PUSCH.]
A UE is not expected to be scheduled by a PDCCH ending in symbol 𝑖 to transmit a PUSCH on a given serving cell for
a given HARQ process, if there is a transmission occasion where the UE is allowed to transmit a PUSCH with
configured grant according to [10, TS38.321] with the same HARQ process on the same serving cell starting in a
symbol 𝑗 after symbol 𝑖, and if the gap between the end of PDCCH and the beginning of symbol 𝑗 is less than 𝑁2
symbols. The value 𝑁2 in symbols is determined according to the UE processing capability defined in Clause 6.4, and
𝑁2 and the symbol duration are based on the minimum of the subcarrier spacing corresponding to the PUSCH with
configured grant and the subcarrier spacing of the PDCCH scheduling the PUSCH.
For PUSCH scheduled by DCI format 0_0 on a cell, the UE shall transmit PUSCH according to the spatial relation, if
applicable, corresponding to the dedicated PUCCH resource with the lowest ID within the active UL BWP of the cell,
as described in Clause 9.2.1 of [6, TS 38.213].
For PUSCH scheduled by DCI format 0_0 on a cell and if the higher layer parameter
enableDefaultBeamPlForPUSCH0_0 is set 'enabled', the UE is not configured with PUCCH resources on the active UL
BWP and the UE is in RRC connected mode, the UE shall transmit PUSCH according to the spatial relation, if
applicable, with a reference to the RS with 'QCL-Type-D' corresponding to the QCL assumption of the CORESET with
the lowest ID.
For PUSCH scheduled by DCI format 0_0 on a cell and if the higher layer parameter
enableDefaultBeamPlForPUSCH0_0 is set 'enabled', the UE is configured with PUCCH resources on the active UL
BWP where all the PUCCH resource(s) are not configured with any spatial relation and the UE is in RRC connected
mode, the UE shall transmit PUSCH according to the spatial relation, if applicable, with a reference to the RS with
'QCL-Type-D' corresponding to the QCL assumption of the CORESET with the lowest ID in case CORESET(s) are
configured on the CC.
For uplink, 16 HARQ processes per cell is supported by the UE.

Two transmission schemes are supported for PUSCH: codebook based transmission and non-codebook based
transmission. The UE is configured with codebook based transmission when the higher layer parameter txConfig in
pusch-Config is set to 'codebook', the UE is configured non-codebook based transmission when the higher layer
parameter txConfig is set to 'nonCodebook'. If the higher layer parameter txConfig is not configured, the UE is not
expected to be scheduled by DCI format 0_1 or 0_2. If PUSCH is scheduled by DCI format 0_0, the PUSCH
3GPP
Release 16 105 3GPP TS 38.214 V16.1.0 (2020-03)
transmission is based on a single antenna port. Except if the higher layer parameter
enableDefaultBeamPlForPUSCH0_0 is set 'enabled', the UE shall not expect PUSCH scheduled by DCI format 0_0 in
a BWP without configured PUCCH resource with PUCCH-SpatialRelationInfo in frequency range 2 in RRC connected
mode.
6.1.1.1 Codebook based UL transmission

For codebook based transmission, PUSCH can be scheduled by DCI format 0_0, DCI format 0_1, DCI format 0_2 or
semi-statically configured to operate according to Clause 6.1.2.3. If this PUSCH is scheduled by DCI format 0_1, DCI
format 0_2, or semi-statically configured to operate according to Clause 6.1.2.3, the UE determines its PUSCH
transmission precoder based on SRI, TPMI and the transmission rank, where the SRI, TPMI and the transmission rank
are given by DCI fields of SRS resource indicator and Precoding information and number of layers in clause 7.3.1.1.2
and 7.3.1.1.3 of [5, TS 38.212] for DCI format 0_1 and 0_2 or given by srs-ResourceIndicator and
precodingAndNumberOfLayers according to clause 6.1.2.3. The SRS-ResourceSet(s) applicable for PUSCH scheduled
by DCI format 0_1 and DCI format 0_2 are defined by the entries of the higher layer parameter srs-
ResourceSetToAddModList and srs-ResourceSetToAddModList-ForDCIFormat0_2 in SRS-config, respectively. The
TPMI is used to indicate the precoder to be applied over the layers {0…ν-1} and that corresponds to the SRS resource
selected by the SRI when multiple SRS resources are configured, or if a single SRS resource is configured TPMI is used
to indicate the precoder to be applied over the layers {0…ν-1} and that corresponds to the SRS resource. The
transmission precoder is selected from the uplink codebook that has a number of antenna ports equal to higher layer
parameter nrofSRS-Ports in SRS-Config, as defined in Clause 6.3.1.5 of [4, TS 38.211]. When the UE is configured
with the higher layer parameter txConfig set to 'codebook', the UE is configured with at least one SRS resource. The
indicated SRI in slot n is associated with the most recent transmission of SRS resource identified by the SRI, where the
SRS resource is prior to the PDCCH carrying the SRI.
For codebook based transmission, the UE determines its codebook subsets based on TPMI and upon the reception of
higher layer parameter codebookSubset in pusch-Config for PUSCH associated with DCI format 0_1 and
codebookSubset-ForDCIFormat0_2 in pusch-Config for PUSCH associated with DCI format 0_2 which may be
configured with 'fullyAndPartialAndNonCoherent', or 'partialAndNonCoherent', or 'nonCoherent' depending on the UE
capability. The maximum transmission rank may be configured by the higher layer parameter maxRank in pusch-Config
for PUSCH scheduled with DCI format 0_1 and maxRank-ForDCIFormat0_2 for PUSCH scheduled with DCI format
0_2.
A UE reporting its UE capability of 'partialAndNonCoherent' transmission shall not expect to be configured by either
codebookSubset or codebookSubset-ForDCIFormat0_2 with 'fullyAndPartialAndNonCoherent'.
A UE reporting its UE capability of 'nonCoherent' transmission shall not expect to be configured by either
codebookSubset or codebookSubset-ForDCIFormat0_2 with 'fullyAndPartialAndNonCoherent' or with
'partialAndNonCoherent'.
A UE shall not expect to be configured with the higher layer parameter codebookSubset or the higher layer parameter
codebookSubset-ForDCIFormat0_2 set to 'partialAndNonCoherent' when higher layer parameter nrofSRS-Ports in an
SRS-ResourceSet with usage set to 'codebook' indicates that the maximum number of the configured SRS antenna ports
in the SRS-ResourceSet is two.
For codebook based transmission, the UE may be configured with a single SRS-ResourceSet with usage set to
'codebook' and only one SRS resource can be indicated based on the SRI from within the SRS resource set. Except
when higher layer parameter ULFPTxModes is set to 'Mode 2', the maximum number of configured SRS resources for
codebook based transmission is 2. If aperiodic SRS is configured for a UE, the SRS request field in DCI triggers the
transmission of aperiodic SRS resources.
The UE shall transmit PUSCH using the same antenna port(s) as the SRS port(s) in the SRS resource indicated by the
DCI format 0_1 or 0_2 or by configuredGrantConfig according to clause 6.1.2.3.
The DM-RS antenna ports ~ p −1 in Clause 6.4.1.1.3 of [4, TS38.211] are determined according to the ordering of
p0,..., ~
DM-RS port(s) given by Tables 7.3.1.1.2-6 to 7.3.1.1.2-23 in Clause 7.3.1.1.2 of [5, TS 38.212].
Except when higher layer parameter ULFPTxModes is set to 'Mode 2', when multiple SRS resources are configured by
SRS-ResourceSet with usage set to 'codebook', the UE shall expect that higher layer parameters nrofSRS-Ports in SRS-
Resource in SRS-ResourceSet shall be configured with the same value for all these SRS resources.
When higher layer parameter ULFPTxModes is set to 'Mode 2',
3GPP
Release 16 106 3GPP TS 38.214 V16.1.0 (2020-03)
- the UE can be configured with one SRS resource or multiple SRS resources with same or different number of
SRS ports within an SRS resource set with usage set to 'codebook'.
- up to 2 different spatial relations (maxNumberConfiguredSpatialRelations) can be configured for all SRS

resources with usage set to 'codebook'.
- subject to UE capability, a maximum of 2 or 4 SRS resources are supported in an SRS resource set with
usage set to 'codebook'
6.1.1.2 Non-Codebook based UL transmission

For non-codebook based transmission, PUSCH can be scheduled by DCI format 0_0, DCI format 0_1, DCI format 0_2
or semi-statically configured to operate according to Clause 6.1.2.3. If this PUSCH is scheduled by DCI format 0_1,
DCI format 0_2, or semi-statically configured to operate according to Clause 6.1.2.3, the UE can determine its PUSCH
precoder and transmission rank based on the SRI when multiple SRS resources are configured, where the SRI is given
by the SRS resource indicator in DCI according to clause 7.3.1.1.2 and 7.3.1.1.3 of [5, 38.212] for DCI format 0_1 and
DCI format 0_2, or the SRI is given by srs-ResourceIndicator according to clause 6.1.2.3. The SRS-ResourceSet(s)
applicable for PUSCH scheduled by DCI format 0_1 and DCI format 0_2 are defined by the entries of the higher layer
parameter srs-ResourceSetToAddModList and srs-ResourceSetToAddModList-ForDCIFormat0_2 in SRS-config,
respectively. The UE shall use one or multiple SRS resources for SRS transmission, where, in a SRS resource set, the
maximum number of SRS resources which can be configured to the UE for simultaneous transmission in the same
symbol and the maximum number of SRS resources are UE capabilities. The SRS resources transmitted simultaneously
occupy the same RBs. Only one SRS port for each SRS resource is configured. Only one SRS resource set can be
configured with higher layer parameter usage in SRS-ResourceSet set to 'nonCodebook'. The maximum number of SRS
resources that can be configured for non-codebook based uplink transmission is 4. The indicated SRI in slot n is
associated with the most recent transmission of SRS resource(s) identified by the SRI, where the SRS transmission is
prior to the PDCCH carrying the SRI.
For non-codebook based transmission, the UE can calculate the precoder used for the transmission of SRS based on
measurement of an associated NZP CSI-RS resource. A UE can be configured with only one NZP CSI-RS resource for
the SRS resource set with higher layer parameter usage in SRS-ResourceSet set to 'nonCodebook' if configured.
- If aperiodic SRS resource set is configured, the associated NZP-CSI-RS is indicated via SRS request field in
DCI format 0_1 and 1_1, as well as DCI format 0_2 (if SRS request field is present) and DCI format 1_2 (if SRS
request field is present), where AperiodicSRS-ResourceTrigger and AperiodicSRS-ResourceTriggerList
(indicating the association between aperiodic SRS triggering state(s) and SRS resource sets), triggered SRS
resource(s) srs-ResourceSetId, csi-RS (indicating the associated NZP-CSI-RS-ResourceId) are higher layer
configured in SRS-ResourceSet. The SRS-ResourceSet(s) associated with the SRS request by DCI format 0_1 and
1_1 are defined by the entries of the higher layer parameter srs-ResourceSetToAddModList and the SRS-
ResourceSet(s) associated with the SRS request by DCI format 0_2 and 1_2 are defined by the entries of the
higher layer parameter srs-ResourceSetToAddModList-ForDCIFormat0_2. A UE is not expected to update the
SRS precoding information if the gap from the last symbol of the reception of the aperiodic NZP-CSI-RS
resource and the first symbol of the aperiodic SRS transmission is less than 42 OFDM symbols.
- If the UE configured with aperiodic SRS associated with aperiodic NZP CSI-RS resource, the presence of the
associated CSI-RS is indicated by the SRS request field if the value of the SRS request field is not '00' as in
Table 7.3.1.1.2-24 of [5, TS 38.212] and if the scheduling DCI is not used for cross carrier or cross bandwidth
part scheduling. The CSI-RS is located in the same slot as the SRS request field. If the UE configured with
aperiodic SRS associated with aperiodic NZP CSI-RS resource, any of the TCI states configured in the
scheduled CC shall not be configured with 'QCL-TypeD'.
- If periodic or semi-persistent SRS resource set is configured, the NZP-CSI-RS-ResourceId for measurement is
indicated via higher layer parameter associatedCSI-RS in SRS-ResourceSet.
The UE shall perform one-to-one mapping from the indicated SRI(s) to the indicated DM-RS ports(s) and their
corresponding PUSCH layers {0 … ν-1} given by DCI format 0_1 or by configuredGrantConfig according to clause
6.1.2.3 in increasing order.
The UE shall transmit PUSCH using the same antenna ports as the SRS port(s) in the SRS resource(s) indicated by
SRI(s) given by DCI format 0_1 or by configuredGrantConfig according to clause 6.1.2.3, where the SRS port in (i+1)-
th SRS resource in the SRS resource set is indexed as pi = 1000 + i .
3GPP
Release 16 107 3GPP TS 38.214 V16.1.0 (2020-03)
The DM-RS antenna ports ~ p −1 in Clause 6.4.1.1.3 of [4, TS 38.211] are determined according to the ordering of
p0,..., ~
DM-RS port(s) given by Tables 7.3.1.1.2-6 to 7.3.1.1.2-23 in Clause 7.3.1.1.2 of [5, TS 38.212].
For non-codebook based transmission, the UE does not expect to be configured with both spatialRelationInfo for SRS
resource and associatedCSI-RS in SRS-ResourceSet for SRS resource set.
For non-codebook based transmission, the UE can be scheduled with DCI format 0_1 when at least one SRS resource is
configured in SRS-ResourceSet with usage set to 'nonCodebook'.

When the UE is scheduled to transmit a transport block and no CSI report, or the UE is scheduled to transmit a transport
block and a CSI report(s) on PUSCH by a DCI, the Time domain resource assignment field value m of the DCI provides
a row index m + 1 to an allocated table. The determination of the used resource allocation table is defined in Clause
6.1.2.1.1. The indexed row defines the slot offset K2, the start and length indicator SLIV, or directly the start symbol S
and the allocation length L, the PUSCH mapping type, and the number of repetitions (if numberofrepetitions is present
in the resource allocation table) to be applied in the PUSCH transmission.
When the UE is scheduled to transmit a PUSCH with no transport block and with a CSI report(s) by a CSI request field
on a DCI, the Time domain resource assignment field value m of the DCI provides a row index m + 1 to the allocated
table as defined in Clause 6.1.2.1.1. The indexed row defines the start and length indicator SLIV, and the PUSCH
mapping type to be applied in the PUSCH transmission and the K2 value is determined as K 2 = max Y j ( m + 1) , where
j
Y j , j = 0,..., N Rep − 1 are the corresponding list entries of the higher layer parameter
- reportSlotOffsetListForDCI-Format0-2, if PUSCH is scheduled by DCI format 0_2 and

reportSlotOffsetListForDCI-Format0-2 is configured;
- reportSlotOffsetListForDCI-Format0-1, if PUSCH is scheduled by DCI format 0_1 and

reportSlotOffsetListForDCI-Format0-1 is configured;
- reportSlotOffsetList, otherwise;
in CSI-ReportConfig for the N Rep triggered CSI Reporting Settings and Y j ( m + 1) is the (m+1)th entry of Y j .
- The slot Ks where the UE shall transmit the PUSCH is determined by K2 as Ks =

 2 PUSCH   N CA CA
N slot  
n   + K2 +   slot ,offset , PDCCH
−
,offset , PUSCH
  2 PUSCH  , if UE is configured with CA-slot-offset for
 2 PDCCH   2 offset ,PDCCH 
2 offset ,PUSCH 
 
 
 2 PUSCH 

at least one of the scheduled and scheduling cell, Ks =  n   + K 2 , otherwise, and where n is the slot with
 2 PDCCH 
the scheduling DCI, K2 is based on the numerology of PUSCH, and PUSCH and  PDCCH are the subcarrier
spacing configurations for PUSCH and PDCCH, respectively,
offset, PDCCH and 𝜇offset,PDCCH are the 𝑁slot, offset and the  offset , respectively, which are determined by higher-
CA CA
- 𝑁slot,
CA
layer configured CA-slot-offset for the cell receiving the PDCCH, 𝑁slot, offset, PUSCH and 𝜇offset,PUSCH are the
𝑁slot, offset and the  offset ,respectively, which are determined by higher-layer configured CA-slot-offset for the cell
CA
transmitting the PUSCH, as defined in clause 4.5 of [4, TS 38.211], and
- for PUSCH scheduled by DCI format 0_1, if PUSCHRepTypeIndicator-ForDCIFormat0_1 is set to 'pusch-

RepTypeB', the UE applies PUSCH repetition Type B procedure when determining the time domain resource
allocation. For PUSCH scheduled by DCI format 0_2, if PUSCHRepTypeIndicator-ForDCIFormat0_2 is set to
'pusch-RepTypeB', the UE applies PUSCH repetition Type B procedure when determining the time domain
resource allocation. Otherwise, the UE applies PUSCH repetition Type A procedure when determining the time
domain resource allocation for PUSCH scheduled by PDCCH.
3GPP
Release 16 108 3GPP TS 38.214 V16.1.0 (2020-03)
- For PUSCH repetition Type A, the starting symbol S relative to the start of the slot, and the number of
consecutive symbols L counting from the symbol S allocated for the PUSCH are determined from the start and
length indicator SLIV of the indexed row:
if ( L − 1)  7 then
SLIV = 14  ( L − 1) + S
else
SLIV = 14  (14 − L + 1) + (14 − 1 − S )
where 0  L  14 − S , and
- For PUSCH repetition Type B, the starting symbol S relative to the start of the slot, and the number of
consecutive symbols L counting from the symbol S allocated for the PUSCH are provided by startSymbol and
length of the indexed row of the resource allocation table, respectively.
- For PUSCH repetition Type A, the PUSCH mapping type is set to Type A or Type B as defined in Clause
6.4.1.1.3 of [4, TS 38.211] as given by the indexed row.
- For PUSCH repetition Type B, the PUSCH mapping type is set to Type B.
The UE shall consider the S and L combinations defined in table 6.1.2.1-1 as valid PUSCH allocations
Table 6.1.2.1-1: Valid S and L combinations
PUSCH Normal cyclic prefix Extended cyclic prefix

mapping type S L S+L S L S+L
Type A 0 {4,…,14} {4,…,14} 0 {4,…,12} {4,…,12}
(repetitionType A
only)
Type B {0,…,13} {1,…,14} {1,…,14} for {0,…, 11} {1,…,12} {1,…,12}
repetition Type A,
{1,…,27} for
repetition Type B
For PUSCH repetition Type A, when transmitting PUSCH scheduled by DCI format 0_1 or 0_2 in PDCCH with CRC
scrambled with C-RNTI, MCS-C-RNTI, or CS-RNTI with NDI=1, the number of repetitions K is determined as
- if numberofrepetitions is present in the resource allocation table, the number of repetitions K is equal to
numberofrepetitions;
- elseif the UE is configured with pusch-AggregationFactor, the number of repetitions K is equal to pusch-
AggregationFactor;
- otherwise K=1.
For PUSCH repetition Type A, in case K>1, the same symbol allocation is applied across the K consecutive slots and
the PUSCH is limited to a single transmission layer. The UE shall repeat the TB across the K consecutive slots applying
the same symbol allocation in each slot. The redundancy version to be applied on the nth transmission occasion of the
TB, where n = 0, 1, … K-1, is determined according to table 6.1.2.1-2.
Table 6.1.2.1-2: Redundancy version for PUSCH transmission
rvid indicated by the DCI rvid to be applied to nth transmission occasion (repetition Type A) or nth
scheduling the PUSCH actual repetition (repetition Type B)
n mod 4 = 0 n mod 4 = 1 n mod 4 = 2 n mod 4 = 3
0 0 2 3 1
2 2 3 1 0
3 3 1 0 2
1 1 0 2 3
3GPP
Release 16 109 3GPP TS 38.214 V16.1.0 (2020-03)
When transmitting MsgA PUSCH on a non-initial UL BWP, if the UE is configured with

startSymbolAndLengthMsgAPO, the UE shall determine the S and L from startSymbolAndLengthMsgAPO.
When transmitting MsgA PUSCH, if the UE is not configured with startSymbolAndLengthMsgAPO, and if the TDRA
list PUSCH-TimeDomainResourceAllocationList is provided in PUSCH-ConfigCommon, the UE shall use msgA-
timeDomainAllocation to indicate which values are used in the list. If PUSCH-TimeDomainResourceAllocationList is
not provided in PUSCH-ConfigCommon, the UE shall use parameters S and L from table 6.1.2.1.1-2 where msgA-
timeDomainAllocation indicates which values are used in the list. The time offset for PUSCH transmission is described
in [6, TS38.213].
For PUSCH repetition Type A, a PUSCH transmission in a slot of a multi-slot PUSCH transmission is omitted
according to the conditions in Clause 11.1 of [6, TS38.213].
For PUSCH repetition Type B, the number of nominal repetitions is given by numberofrepetitions. For the n-th nominal
repetition, n = 0, …, numberofrepetitions - 1,
S + nL
- The slot where the nominal repetition starts is given by K s +  slot  , and the starting symbol relative to the
 N symb 
(
start of the slot is given by mod S + n  L, N symb .
slot
)
 S + ( n + 1)  L − 1 
- The slot where the nominal repetition ends is given by K s +  slot  , and the ending symbol relative
 N symb 
(
to the start of the slot is given by mod S + ( n + 1)  L − 1, N symb .
slot
)
Here K s is the slot where the PUSCH transmission starts, and N symb
slot
is the number of symbols per slot as defined in
Clause 4.3.2 of [4, TS38.211].
For PUSCH repetition Type B, the UE determines invalid symbol(s) for PUSCH repetition Type B transmission as
follows:
- A symbol that is indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-

ConfigurationDedicated is considered as an invalid symbol for PUSCH repetition Type B transmission.
- The UE may be configured with the higher layer parameter InvalidSymbolPattern, which provides a symbol
level bitmap spanning one or two slots (higher layer parameter symbols given by InvalidSymbolPattern). A bit
value equal to 1 in the symbol level bitmap symbols indicates that the corresponding symbol is an invalid symbol
for PUSCH repetition Type B transmission. The UE may be additionally configured with a time-domain pattern
(higher layer parameter periodicityAndPattern given by InvalidSymbolPattern), where each bit of
periodicityAndPattern corresponds to a unit equal to a duration of the symbol level bitmap symbols, and a bit
value equal to 1 indicates that the symbol level bitmap symbols is present in the unit. The periodicityAndPattern
can be {1, 2, 4, 5, 8, 10, 20 or 40} units long, but maximum of 40ms. The first symbol of periodicityAndPattern
every 40ms/P periods is a first symbol in frame 𝑛𝑓 mod 4 = 0, where P is the duration of periodicityAndPattern
in units of ms. When periodicityAndPattern is not configured, for a symbol level bitmap spanning two slots, the
bits of the first and second slots correspond respectively to even and odd slots of a radio frame, and for a symbol
level bitmap spanning one slot, the bits of the slot correspond to every slot of a radio frame. If
InvalidSymbolPattern is configured, when the UE applies the invalid symbol pattern is determined as follows:
- if the PUSCH is scheduled by DCI format 0_1, or corresponds to a Type 2 configured grant activated by DCI
format 0_1, and if InvalidSymbolPatternIndicator-ForDCIFormat0_1 is configured,
- if invalid symbol pattern indicator field is set 1, the UE applies the invalid symbol pattern;
- otherwise, the UE does not apply the invalid symbol pattern;
- if the PUSCH is scheduled by DCI format 0_2, or corresponds to a Type 2 configured grant activated by DCI
format 0_2, and if InvalidSymbolPatternIndicator-ForDCIFormat0_2 is configured,
- if invalid symbol pattern indicator field is set 1, the UE applies the invalid symbol pattern;
- otherwise, the UE does not apply the invalid symbol pattern;
3GPP
Release 16 110 3GPP TS 38.214 V16.1.0 (2020-03)
- otherwise, the UE applies the invalid symbol pattern.
For PUSCH repetition Type B, after determining the invalid symbol(s) for PUSCH repetition type B transmission for
each of the K nominal repetitions, the remaining symbols are considered as potentially valid symbols for PUSCH
repetition Type B transmission. If the number of potentially valid symbols for PUSCH repetition type B transmission is
greater than zero for a nominal repetition, the nominal repetition consists of one or more actual repetitions, where each
actual repetition consists of a consecutive set of potentially valid symbols that can be used for PUSCH repetition Type
B transmission within a slot. An actual repetition with a single symbol is omitted except for the case of L=1. An actual
repetition is omitted according to the conditions in Clause 11.1 of [6, TS38.213]. The redundancy version to be applied
on the nth actual repetition (with the counting including the actual repetitions that are omitted) is determined according
to table 6.1.2.1-2.
If pusch-TimeDomainAllocationList in pusch-Config contains row indicating resource allocation for two to eight
contiguous PUSCHs, K2 indicates the slot where UE shall transmit the first PUSCH of the multiple PUSCHs. Each
PUSCH has a separate SLIV and mapping type. The number of scheduled PUSCHs is signalled by the number of
indicated valid SLIVs in the row of the pusch-TimeDomainAllocationList signalled in DCI format 0_1.
When the UE configured with [minimumSchedulingOffset] in active UL BWP it applies a minimum scheduling offset
restriction indicated by the ['Minimum applicable scheduling offset indicator'] field in DCI format 0_1 or 1_1. When the
UE configured with [minimumSchedulingOffset] in active UL BWP and it has not received ['Minimum applicable
scheduling offset indicator'] field in DCI format 0_1 or 1_1, the UE shall apply a minimum scheduling offset restriction
indicated based on ['Minimum applicable scheduling offset indicator'] value '0'. When the minimum scheduling offset
restriction is applied the UE is not expected to be scheduled with a DCI in slot n to transmit a PUSCH scheduled with
C-RNTI, CS-RNTI or MCS-C-RNTI with K2 smaller than the applicable minimum scheduling offset restriction K2min in
slot n. The minimum scheduling restriction is not applied when PUSCH transmission is scheduled by RAR UL grant for
RACH procedure, or when PUSCH is scheduled with TC-RNTI. The application delay of the change of the minimum
scheduling offset restriction is determined in Clause 5.3.1.
6.1.2.1.1 Determination of the resource allocation table to be used for PUSCH

Table 6.1.2.1.1-1, Table 6.1.2.1.1-1A and Table 6.1.2.1.1-1B define which PUSCH time domain resource allocation
configuration to apply.
Table 6.1.2.1.1-4 defines the subcarrier spacing specific values j. j is used in determination of 𝐾2 in conjunction to
table 6.1.2.1.1-2, for normal CP or table 6.1.2.1.1.-3 for extended CP, where µ𝑃𝑈𝑆𝐶𝐻 is the subcarrier spacing
configurations for PUSCH.
Table 6.1.2.1.1-5 defines the additional subcarrier spacing specific slot delay value for the first transmission of PUSCH
scheduled by the RAR or by the fallback RAR. When the UE transmits a PUSCH scheduled by RAR or by the fallback
RAR, the Δ value specific to the PUSCH subcarrier spacing µPUSCH is applied in addition to the K2 value.
3GPP
Release 16 111 3GPP TS 38.214 V16.1.0 (2020-03)
Table 6.1.2.1.1-1: Applicable PUSCH time domain resource allocation for common search space and
DCI format 0_0 in UE specific search space
RNTI PDCCH pusch-ConfigCommon pusch-Config includes PUSCH time domain

search includes pusch- pusch- resource allocation to apply
space TimeDomainAllocationList TimeDomainAllocationList
PUSCH scheduled by No - Default A
MAC RAR as described Yes pusch-
in clause 8.2 of [6, TS TimeDomainAllocationList
38.213] or MAC fallback provided in pusch-
RAR as described in ConfigCommon
clause X.Y of [6, 38.213]
or for MsgA PUSCH
transmission
C-RNTI, Any common No - Default A
MCS-C- search space Yes pusch-
RNTI, associated TimeDomainAllocationList
TC- with provided in pusch-
RNTI, CORESET 0 ConfigCommon
CS-RNTI
C-RNTI, Any common No No Default A
MCS-C- search space Yes No pusch-
RNTI, not TimeDomainAllocationList
TC- associated provided in pusch-
RNTI, with ConfigCommon
CS- CORESET 0, No/Yes Yes pusch-
RNTI, DCI format TimeDomainAllocationList
SP-CSI- 0_0 in provided in pusch-Config
RNTI UE specific
search space
Table 6.1.2.1.1-1A: Applicable PUSCH time domain resource allocation for DCI format 0_1 in UE
specific search space scrambled with C-RNTI, MCS-C-RNTI, CS-RNTI or SP-CSI-RNTI
pusch-ConfigCommon pusch-Config includes pusch-Config includes PUSCH time domain

includes pusch- pusch- pusch- resource allocation to apply
-ForDCIformat0_1
No No No Default A
Yes No No pusch-
provided in pusch-
ConfigCommon
No/Yes Yes No pusch-
provided in pusch-Config
No/Yes No/Yes Yes pusch-
pusch-Config
3GPP
Release 16 112 3GPP TS 38.214 V16.1.0 (2020-03)
Table 6.1.2.1.1-1B: Applicable PUSCH time domain resource allocation for DCI format 0_2 in UE
specific search space scrambled with C-RNTI, MCS-C-RNTI, CS-RNTI or SP-CSI-RNTI
pusch-ConfigCommon pusch-Config includes pusch-Config includes PUSCH time domain

includes pusch- pusch- pusch- resource allocation to apply
-ForDCIformat0_2
No No No Default A
Yes No No pusch-
provided in pusch-
ConfigCommon
No/Yes Yes No pusch-
provided in pusch-Config
No/Yes No/Yes Yes pusch-
pusch-Config
Table 6.1.2.1.1-2: Default PUSCH time domain resource allocation A for normal CP
Row index PUSCH 𝑲𝟐 S L

mapping type
1 Type A j 0 14
2 Type A j 0 12
3 Type A j 0 10
4 Type B j 2 10
5 Type B j 4 10
6 Type B j 4 8
7 Type B j 4 6
8 Type A j+1 0 14
9 Type A j+1 0 12
10 Type A j+1 0 10
11 Type A j+2 0 14
12 Type A j+2 0 12
13 Type A j+2 0 10
14 Type B j 8 6
15 Type A j+3 0 14
16 Type A j+3 0 10
Table 6.1.2.1.1-3: Default PUSCH time domain resource allocation A for extended CP
Row index PUSCH K2 S L

mapping type
1 Type A j 0 8
2 Type A j 0 12
3 Type A j 0 10
4 Type B j 2 10
5 Type B j 4 4
6 Type B j 4 8
7 Type B j 4 6
8 Type A j+1 0 8
9 Type A j+1 0 12
10 Type A j+1 0 10
11 Type A j+2 0 6
12 Type A j+2 0 12
13 Type A j+2 0 10
14 Type B j 8 4
15 Type A j+3 0 8
16 Type A j+3 0 10
3GPP
Release 16 113 3GPP TS 38.214 V16.1.0 (2020-03)
Table 6.1.2.1.1-4: Definition of value j
µPUSCH j
0 1
1 1
2 2
3 3
Table 6.1.2.1.1-5: Definition of value Δ
µPUSCH Δ
0 2
1 3
2 4
3 6

The UE shall determine the resource block assignment in frequency domain using the resource allocation field in the
detected PDCCH DCI except for a PUSCH transmission scheduled by a RAR UL grant or fallbackRAR UL grant, in
which case the frequency domain resource allocation is determined according to clause 8.3 of [6, 38.213] or clause X.Y
of [6, 38.213] respectively. Three uplink resource allocation schemes type 0, type 1 and type 2 are supported. Uplink
resource allocation scheme type 0 is supported for PUSCH only when transform precoding is disabled. Uplink resource
allocation scheme type 1 and type 2 are supported for PUSCH for both cases when transform precoding is enabled or
disabled.
If the scheduling DCI is configured to indicate the uplink resource allocation type as part of the Frequency domain
resource assignment field by setting a higher layer parameter resourceAllocation in pusch-Config to 'dynamicSwitch',
for DCI format 0_1 or setting a higher layer parameter resourceAllocation-ForDCIFormat0_2 in pusch-Config to
'dynamicswitch' for DCI format 0_2, the UE shall use uplink resource allocation type 0 or type 1 as defined by this DCI
field. Otherwise the UE shall use the uplink frequency resource allocation type as defined by the higher layer parameter
resourceAllocation for DCI format 0_1 or the higher layer parameter resourceAllocation-ForDCIFormat0_2 for DCI
format 0_2. The UE shall assume that when the scheduling PDCCH is received with DCI format 0_1 and
useInterlacePUSCH-Dedicated is set to 'enabled', uplink type 2 resource allocation is used.
The UE shall assume that when the scheduling PDCCH is received with DCI format 0_0, then uplink resource
allocation type 1 is used, except when any of the higher layer parameters useInterlacePUSCH-Common or
useInterlacePUSCH-Dedicated are set to 'enabled' in which case uplink resource allocation type 2 is used.
The UE expects that either none or both of useInterlacePUSCH-Common and useInterlacePUSCH-Dedicated is set to
'enabled'.
The UE expects that either none or both of useInterlacePUSCH-Common and useInterlacePUCCH-Common is set to
'enabled'.
If a bandwidth part indicator field is not configured in the scheduling DCI or the UE does not support active bandwidth
part change via DCI, the RB indexing for uplink type 0, type 1 and type 2 resource allocation is determined within the
UE's active bandwidth part. If a bandwidth part indicator field is configured in the scheduling DCI and the UE supports
active bandwidh part change via DCI, the RB indexing for uplink type 0, type 1, type 2 resource allocation is
determined within the UE's bandwidth part indicated by bandwidth part indicator field value in the DCI. The UE shall
upon detection of PDCCH intended for the UE determine first the uplink bandwidth part and then the resource
allocation within the bandwidth part. RB numbering starts from the lowest RB in the determined uplink bandwidth part.
6.1.2.2.1 Uplink resource allocation type 0

In uplink resource allocation of type 0, the resource block assignment information includes a bitmap indicating the
Resource Block Groups (RBGs) that are allocated to the scheduled UE where a RBG is a set of consecutive virtual
resource blocks defined by higher layer parameter rbg-Size configured in pusch-Config and the size of the bandwidth
part as defined in Table 6.1.2.2.1-1.
3GPP
Release 16 114 3GPP TS 38.214 V16.1.0 (2020-03)
Table 6.1.2.2.1-1: Nominal RBG size P
Bandwidth Part Size Configuration 1 Configuration 2

1 – 36 2 4
37 – 72 4 8
73 – 144 8 16
145 – 275 16 16
size
The total number of RBGs ( N RBG ) for a uplink bandwidth part i of size N BWP,i PRBs is given by
 (
N RBG =  N BWP
size
,i + ( N BWP ,i mod P ) / P
start 
 ) where
- the size of the first RBG is RBG0size = P − N BW

start
P,i mod P ,
- the size of the last RBG is

size
RBGlast (
= N BW
start size
) ( start
)
P,i + N BW P,i mod P if N BW P,i + N BW P,i mod P  0 and P otherwise.
size
- the size of all other RBG is P.
The bitmap is of size N RBG bits with one bitmap bit per RBG such that each RBG is addressable. The RBGs shall be
indexed in the order of increasing frequency of the bandwidth part and starting at the lowest frequency. The order of
RBG bitmap is such that RBG 0 to RBG N RBG − 1 are mapped from MSB to LSB of the bitmap. The RBG is allocated
to the UE if the corresponding bit value in the bitmap is 1, the RBG is not allocated to the UE otherwise.
In frequency range 1, only 'almost contiguous allocation' defined in [8, TS 38.101-1] is allowed as non-contiguous allocation per
component carrier for UL RB allocation for CP-OFDM.
In frequency range 2, non-contiguous allocation per component carrier for UL RB allocation for CP-OFDM is not supported.

In uplink resource allocation of type 1, the resource block assignment information indicates to a scheduled UE a set of
size
contiguously allocated non-interleaved virtual resource blocks within the active bandwidth part of size N BWP PRBs
except for the case when DCI format 0_0 is decoded in any common search space in which case the size of the initial
size
UL bandwidth part NBWP,0 shall be used.
An uplink type 1 resource allocation field consists of a resource indication value (RIV) corresponding to a starting
virtual resource block ( RBstart ) and a length in terms of contiguously allocated resource blocks L RBs . The resource
indication value is defined by

if ( LRBs − 1)  N BW P / 2
size
 then
RIV = N BW
size
P( LRBs − 1) + RBstart
else
RIV = N BW
size
P( N BW P − LRBs + 1) + ( N BW P − 1 − RBstart )
size size
where L RBs  1 and shall not exceed N BW P − RBstart .

size
initial
When the DCI size for DCI format 0_0 in USS is derived from the initial UL BWP with size NBWP but applied to
active
another active BWP with size of NBWP , an uplink type 1 resource block assignment field consists of a resource
indication value (RIV) corresponding to a starting resource block RBstart = 0, K , 2  K , ,( NBWP
initial
−1)  K and a length in
terms of virtually contiguously allocated resource blocks LRBs = K , 2  K , , NBWP  K .
initial
3GPP
Release 16 115 3GPP TS 38.214 V16.1.0 (2020-03)
if ( L 'RBs − 1)   N BWP
initial
/ 2 then
RIV = NBWP
initial
( L 'RBs −1) + RB 'start
else
RIV = NBWP
initial initial
( NBWP − L 'RBs + 1) + ( NBWP
initial
−1 − RB 'start )
where L 'RBs = LRBs K , RB 'start = RBstart K and where L 'RBs shall not exceed NBWP
initial
− RB 'start .
active
If NBWP  NBWP
initial
, K is the maximum value from set {1, 2, 4, 8} which satisfies K   N BWP
active initial
/ N BWP  ; otherwise K = 1.
When the scheduling grant is received with DCI format 0_2, an uplink type 1 resource allocation field consists of a
resource indication value (RIV) corresponding to a starting resource block group RBGstart=0, 1, …, NRBG-1 and a length
in terms of virtually contiguously allocated resource block groups LRBGs=1, …, NRBG, where the resource block groups
are defined as in 6.1.2.2.1 with P defined by ResourceAllocationType1-granularity-ForDCIFormat0_2 if the UE is
configured with higher layer parameter ResourceAllocationType1-granularity-ForDCIFormat0_2, and P=1 otherwise.
if ( LRBGs − 1)   N RBG / 2  then
RIV = N RBG ( LRBGs − 1) + RBGstart
else
RIV = N RBG ( N RBG − LRBGs + 1) + ( N RBG − 1 − RBGstart )
where LRBGs  1 and shall not exceed N RBG − RBGstart .

In uplink resource allocation of type 2, the resource block assignment information defined in [5, TS 38.212] indicates to
𝐵𝑊𝑃
a UE a set of up to M interlace indices, and for DCI 0_1 a set of up to 𝑁𝑅𝐵−𝑠𝑒𝑡 contiguous RB sets, where M and
interlace indexing are defined in Clause 4.4.4.6 in [4, TS 38.211]. The UE shall determine the resource allocation in
frequency domain as an intersection of the resource blocks of the indicated interlaces and the indicated set of RB sets
and intra-cell guard bands defined in Clause 7 between the indicated RB sets, if any.
For µ=0, the X MSBs of the resource block assignment information indicates to a UE a set of allocated interlace indices
𝑚 0 + 𝑙, where the indication consists of a resource indication value (RIV). For 0 ≤ 𝑅𝐼𝑉 < 𝑀(𝑀 + 1)/2 , 𝑙 =
0,1, ⋯ 𝐿 − 1 the resource indication value corresponds to the starting interlace index m0 and the number of contiguous
interlace indices L ( L  1 ). The resource indication value is defined by:
if (𝐿 − 1) ≤ ⌊𝑀/2⌋ then
𝑅𝐼𝑉 = 𝑀(𝐿 − 1) + 𝑚0
else
𝑅𝐼𝑉 = 𝑀(𝑀 − 𝐿 + 1) + (𝑀 − 1 − 𝑚0 )
For 𝑅𝐼𝑉 ≥ 𝑀(𝑀 + 1)/2 , the resource indication value corresponds to the starting interlace index m0 and the set of
values l according to Table 6.1.2.2.3-1.
3GPP
Release 16 116 3GPP TS 38.214 V16.1.0 (2020-03)
Table 6.1.2.2.3-1: m0 and l for 𝑹𝑰𝑽 ≥ 𝑴(𝑴 + 𝟏)/𝟐.
𝑹𝑰𝑽 − 𝑴(𝑴 + 𝟏)/𝟐 m0 l

0 0 {0, 5}
1 0 {0, 1, 5, 6}
2 1 {0, 5}
3 1 {0, 1, 2, 3, 5, 6, 7, 8}
4 2 {0, 5}
5 2 {0, 1, 2, 5, 6, 7}
6 3 {0, 5}
7 4 {0, 5}
For µ=1, the X MSBs of the resource block assignment information comprise a bitmap indicating the interlaces that are
allocated to the scheduled UE. The bitmap is of size M bits with one bitmap bit per interlace such that each interlace is
addressable, where M and interlace indexing is defined in Clause 4.4.4.6 in [4, TS 38.211]. The order of interlace
bitmap is such that interlace 0 to interlace 𝑀 − 1 are mapped from MSB to LSB of the bitmap. An interlace is allocated
to the UE if the corresponding bit value in the bitmap is 1; otherwise the interlace is not allocated to the UE.
𝐵𝑊𝑃 𝐵𝑊𝑃
𝑁𝑅𝐵−𝑠𝑒𝑡 (𝑁𝑅𝐵−𝑠𝑒𝑡 +1)
For both µ=0 and µ=1, the 𝑌 = ⌈𝑙𝑜𝑔2 ⌉ LSBs of the resource block assignment information indicate to
2
a UE a set of contiguously allocated RB sets for PUSCH scheduled by DCI 0_1 and Type 1 and Type 2 configured
grant. The resource allocation field consists of a resource indication value (RIVRBset). For 0 ≤ 𝑅𝐼𝑉𝑅𝐵𝑠𝑒𝑡 <
𝐵𝑊𝑃 𝐵𝑊𝑃
𝑁𝑅𝐵−𝑠𝑒𝑡 (𝑁𝑅𝐵−𝑠𝑒𝑡 + 1)/2 , 𝑙 = 0,1, ⋯ 𝐿𝑅𝐵𝑠𝑒𝑡 − 1 the resource indication value corresponds to the starting RB set
(𝑅𝐵𝑠𝑒𝑡START ) and the number of contiguous RB sets 𝐿𝑅𝐵𝑠𝑒𝑡 (𝐿𝑅𝐵𝑠𝑒𝑡 ≥ 1). The resource indication value is defined by;
𝐵𝑊𝑃
if (𝐿𝑅𝐵𝑠𝑒𝑡 − 1) ≤ ⌊𝑁𝑅𝐵−𝑠𝑒𝑡 /2⌋ then
𝐵𝑊𝑃
𝑅𝐼𝑉𝑅𝐵𝑠𝑒𝑡 = 𝑁𝑅𝐵−𝑠𝑒𝑡 (𝐿𝑅𝐵𝑠𝑒𝑡 − 1) + 𝑅𝐵𝑠𝑒𝑡START
else
𝐵𝑊𝑃 𝐵𝑊𝑃 𝐵𝑊𝑃
𝑅𝐼𝑉𝑅𝐵𝑠𝑒𝑡 = 𝑁𝑅𝐵−𝑠𝑒𝑡 (𝑁𝑅𝐵−𝑠𝑒𝑡 − 𝐿𝑅𝐵𝑠𝑒𝑡 + 1) + (𝑁𝑅𝐵−𝑠𝑒𝑡 − 1 − 𝑅𝐵𝑠𝑒𝑡START )
If transform precoding is enabled according to the procedure in Clause 6.1.3, then the UE transmits PUSCH on the
PUSCH PUSCH
lowest-indexed 𝑀RB PRBs indicated by the frequency domain resource assignment information. 𝑀RB is the
largest integer not greater than the number of RBs indicated by the frequency domain resource assignment information
that fulfils the conditions in [4, TS 38.211 Clause 6.3.1.4].
6.1.2.3 Resource allocation for uplink transmission with configured grant

When PUSCH resource allocation is semi-statically configured by higher layer parameter configuredGrantConfig in
BWP-UplinkDedicated information element, and the PUSCH transmission corresponding to a configured grant, the
following higher layer parameters are applied in the transmission:
- For Type 1 PUSCH transmissions with a configured grant, the following parameters are given in
configuredGrantConfig unless mentioned otherwise:
- For the determination of the PUSCH repetition type, if the higher layer parameter PUSCHRepTypeIndicator-
ForType1Configuredgrant is configured and set to 'pusch-RepTypeB', PUSCH repetition type B is applied;
otherwise, PUSCH repetition type A is applied;
- For PUSCH repetition type A, the selection of the time domain resource allocation table follows the rules for
DCI format 0_0 on UE specific search space, as defined in Clause 6.1.2.1.1.
- For PUSCH repetition type B, the selection of the time domain resource allocation table is as follows:
- If PUSCHRepTypeIndicator-ForDCIFormat0_1 in pusch-Config is configured and set to 'pusch-

RepTypeB', PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_1 in pusch-Config is used;
- Otherwise, PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_2 in pusch-Config is used.
- It is not expected that PUSCHRepTypeIndicator-ForType1Configuredgrant is configured with 'pusch-

RepTypeB' when none of PUSCHRepTypeIndicator-ForDCIFormat0_1 and PUSCHRepTypeIndicator-
ForDCIFormat0_2 in pusch-Config is set to 'pusch-RepTypeB'.
3GPP
Release 16 117 3GPP TS 38.214 V16.1.0 (2020-03)
- The higher layer parameter timeDomainAllocation value m provides a row index m+1 pointing to the
determined time domain resource allocation table, where the start symbol and length are determined
following the procedure defined in Clause 6.1.2.1;
- Frequency domain resource allocation is determined by the N LSB bits in the higher layer parameter
frequencyDomainAllocation, forming a bit sequence 𝑓17 , … , 𝑓1 , 𝑓0 , where 𝑓0 is the LSB, according to the
procedure in Clause 6.1.2.2 and N is determined as the size of frequency domain resource assignment field in
DCI format 0_1 for a given resource allocation type indicated by resourceAllocation, except if
useInterlacePUSCH-Dedicated is set to 'enabled', in which case uplink type 2 resource allocation is used
wherein the UE interprets the LSB bits in the higher layer parameter frequencyDomainAllocation as for the
frequency domain resource assignment field of DCI 0_1 according to the procedure in Clause 6.1.2.2.3;
- The IMCS is provided by higher layer parameter mcsAndTBS;
- Number of DM-RS CDM groups, DM-RS ports, SRS resource indication and DM-RS sequence initialization
are determined as in Clause 7.3.1.1 of [5, TS 38.212], and the antenna port value, the bit value for DM-RS
sequence initialization, precoding information and number of layers, SRS resource indicator are provided by
antennaPort, dmrs-SeqInitialization, precodingAndNumberOfLayers, and srs-ResourceIndicator
respectively;
- When frequency hopping is enabled, the frequency offset between two frequency hops can be configured by
higher layer parameter frequencyHoppingOffset.
- For Type 2 PUSCH transmissions with a configured grant: the resource allocation follows the higher layer
configuration according to [10, TS 38.321], and UL grant received on the DCI.
- The PUSCH repetition type and the time domain resource allocation table are determined by the PUSCH
repetition type and the time domain resource allocation table associated with the UL grant received on the
DCI, respectively, as defined in Clause 6.1.2.1.
For PUSCH transmissions with a Type 1 or Type 2 configured grant, the number of (nominal) repetitions K to be
applied to the transmitted transport block is provided by the indexed row in the time domain resource allocation table if
numberofrepetitions is present in the table; otherwise K is provided by the higher layer configured parameters repK.
The UE shall not transmit anything on the resources configured by configuredGrantConfig if the higher layers did not
deliver a transport block to transmit on the resources allocated for uplink transmission without grant.
A set of allowed periodicities P are defined in [12, TS 38.331]. The higher layer parameter cg-nrofSlots-r16, provides
the number of consecutive slots allocated within a configured grant period. The higher layer parameter cg-nrofPUSCH-
InSlot-r16 provides the number of consecutive PUSCH allocations within a slot, where the first PUSCH allocation
follows the higher layer parameter timeDomainAllocation, and the remaining PUSCH allocations have the same length
and PUSCH mapping type, and are appended following the previous allocations without any gaps. The same
combination of start symbol and length and PUSCH mapping type repeats over the consecutively allocated slots.
For operation with shared spectrum channel access where a UE is performing uplink transmission with configured
grants in contiguous OFDM symbols on all resource blocks of an RB set, for the first such UL transmission the UE
randomly determines a duration of a cyclic prefix extension Text to be applied for transmission according to [4, TS
38.211] from a set of values configured by higher layers according to the following rule:
- If the first such UL transmission is within a channel occupancy initiated by the gNB (defined in Clause 4 of [16,
TS 37.213]), the set of values is determined by cg-StartingFullBW-InsideCOT-r16;
- otherwise, the set of values is determined by cg-StartingFullBW-OutsideCOT-r16.
For operation with shared spectrum channel access where a UE is performing uplink transmission with configured
grants in contiguous OFDM symbols on fewer than all resource blocks of an RB set, for the first such UL transmission
the UE determines a duration of a cyclic prefix extension Text to be applied for transmission according to [4, TS 38.211]
according to the following rule:
- If the first such UL transmission is within a channel occupancy initiated by the gNB (defined in Clause 4 of [16,
TS 37.213]), the Text is equal to cg-StartingPartialBW-InsideCOT-r16;
- otherwise, the Text is equal to cg-StartingPartialBW-OutsideCOT-r16.
3GPP
Release 16 118 3GPP TS 38.214 V16.1.0 (2020-03)
6.1.2.3.1 Transport Block repetition for uplink transmissions of PUSCH repetition Type A with a
configured grant
The procedures described in this clause apply to PUSCH transmissions of PUSCH repetition Type A with a Type 1 or
Type 2 configured grant.
The higher layer parameter repK-RV defines the redundancy version pattern to be applied to the repetitions. If the
parameter repK-RV is not provided in the configuredGrantConfig, the redundancy version for uplink transmissions with
a configured grant shall be set to 0. Otherwise, for the nth transmission occasion among K repetitions, n=1, 2, …, K, it is
associated with (mod(n-1,4)+1)th value in the configured RV sequence. If a configured grant configuration is configured
with Configuredgrantconfig-StartingfromRV0 set to 'off', the initial transmission of a transport block may only start at
the first transmission occasion of the K repetitions. Otherwise, the initial transmission of a transport block may start at
- the first transmission occasion of the K repetitions if the configured RV sequence is {0,2,3,1},
- any of the transmission occasions of the K repetitions that are associated with RV=0 if the configured RV
sequence is {0,3,0,3},
- any of the transmission occasions of the K repetitions if the configured RV sequence is {0,0,0,0}, except the last
transmission occasion when K≥8.
For any RV sequence, the repetitions shall be terminated after transmitting K repetitions, or at the last transmission
occasion among the K repetitions within the period P, or from the starting symbol of the repetition that overlaps with a
PUSCH with the same HARQ process scheduled by DCI format 0_0, 0_1 or 0_2, whichever is reached first. In
addition, the UE shall terminate the repetition of a transport block in a PUSCH transmission if the UE receives a DCI
format 0_1 with DFI flag provided and set to '1', and if in this DCI the UE detects ACK for the HARQ process
corresponding to that transport block.
The UE is not expected to be configured with the time duration for the transmission of K repetitions larger than the time
duration derived by the periodicity P. If the UE determines that, for a transmission occasion, the number of symbols
available for the PUSCH transmission in a slot is smaller than transmission duration L, the UE does not transmit the
PUSCH in the transmission occasion.
For both Type 1 and Type 2 PUSCH transmissions with a configured grant, when K > 1, the UE shall repeat the TB
across the K consecutive slots applying the same symbol allocation in each slot, except if the UE is provided with
higher layer parameters cg-nrofSlots-r16 and cg-nrofPUSCH-InSlot-r16, in which case the UE repeats the TB in the
repK earliest consecutive transmission occasion candidates within the same configuration. A Type 1 or Type 2 PUSCH
transmission with a configured grant in a slot is omitted according to the conditions in Clause 11.1 of [6, TS38.213].
6.1.2.3.2 Transport Block repetition for uplink transmissions of PUSCH repetition Type B with a
configured grant
The procedures described in this Clause apply to PUSCH transmissions of PUSCH repetition type B with a Type 1 or
Type 2 configured grant.
For PUSCH transmissions with a Type 1 or Type 2 configured grant, the nominal repetitions and the actual repetitions
are determined according to the procedures for PUSCH repetition Type B defined in Clause 6.1.2.1. The higher layer
configured parameters repK-RV defines the redundancy version pattern to be applied to the repetitions. If the parameter
repK-RV is not provided in the configuredGrantConfig, the redundancy version for each actual repetition with a
configured grant shall be set to 0. Otherwise, for the nth transmission occasion among all the actual repetitions
(including the actual repetitions that are omitted) of the K nominal repetitions, it is associated with (mod(n-1,4)+1)th
value in the configured RV sequence. If a configured grant configuration is configured with Configuredgrantconfig-
StartingfromRV0 set to 'off', the initial transmission of a transport block may only start at the first transmission occasion
of the actual repetitions. Otherwise, the initial transmission of a transport block may start at
- the first transmission occasion of the actual repetitions if the configured RV sequence is {0,2,3,1},
- any of the transmission occasions of the actual repetitions that are associated with RV=0 if the configured RV
sequence is {0,3,0,3},
- any of the transmission occasions of the actual repetitions if the configured RV sequence is {0,0,0,0}, except the
actual repetitions within the last nominal repetition when K≥8.
3GPP
Release 16 119 3GPP TS 38.214 V16.1.0 (2020-03)
For any RV sequence, the repetitions shall be terminated after transmitting K nominal repetitions, or at the last
transmission occasion among the K nominal repetitions within the period P, or from the starting symbol of a repetition
that overlaps with a PUSCH with the same HARQ process scheduled by DCI format 0_0, 0_1 or 0_2, whichever is
reached first. The UE is not expected to be configured with the time duration for the transmission of K nominal
repetitions larger than the time duration derived by the periodicity P.
6.1.3 UE procedure for applying transform precoding on PUSCH

For a PUSCH scheduled by RAR UL grant, or for a PUSCH scheduled by fallbackRAR UL grant, or for a PUSCH
scheduled by DCI format 0_0 with CRC scrambled by TC-RNTI, the UE shall consider the transform precoding either
'enabled' or 'disabled' according to the higher layer configured parameter msg3-transformPrecoder.
For a MsgA PUSCH, the UE shall consider the transform precoding either 'enabled' or 'disabled' according to the higher
layer configured parameter msgA-transformPrecoder. If higher layer parameter msgA-transformPrecoder is not
configured, the UE shall consider the transform precoding either 'enabled' or 'disabled' according to the higher layer
configured parameter msg3-transformPrecoder.
For PUSCH transmission scheduled by a PDCCH with CRC scrambled by CS-RNTI with NDI=1, C-RNTI, or MCS-C-
RNTI or SP-CSI-RNTI:
- If the DCI with the scheduling grant was received with DCI format 0_0, the UE shall, for this PUSCH
transmission, consider the transform precoding either enabled or disabled according to the higher layer
configured parameter msg3-transformPrecoder.
- If the DCI with the scheduling grant was not received with DCI format 0_0
- If the UE is configured with the higher layer parameter transformPrecoder in pusch-Config, the UE shall, for
this PUSCH transmission, consider the transform precoding either enabled or disabled according to this
parameter.
- If the UE is not configured with the higher layer parameter transformPrecoder in pusch-Config, the UE shall,
for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the
higher layer configured parameter msg3-transformPrecoder.
For PUSCH transmission with a configured grant
- If the UE is configured with the higher layer parameter transformPrecoder in configuredGrantConfig, the UE
shall, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this
parameter.
- If the UE is not configured with the higher layer parameter transformPrecoder in configuredGrantConfig, the
UE shall, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to
the higher layer configured parameter msg3-transformPrecoder.
6.1.4 Modulation order, redundancy version and transport block size

determination
To determine the modulation order, target code rate, redundancy version and transport block size for the physical uplink
shared channel, the UE shall first
- read the 5-bit modulation and coding scheme field (I MCS ) in the DCI scheduling PUSCH or provided in a DCI
activating a configured grant Type 2 PUSCH, or as provided by mcsAndTBS as described in Clause 6.1.2.3 for a
configured grant Type 1 PUSCH to determine the modulation order (O m ) and target code rate (R) based on the
procedure defined in Clause 6.1.4.1
- read redundancy version field (rv) in the DCI to determine the redundancy version for PUSCH scheduled by
DCI, or determine the redundancy version according to Clause 6.1.2.3.1 for configured grant Type 1 and Type 2
PUSCH,
and second
- use the number of layers ( ) , the total number of allocated PRBs (n PRB ) to determine the transport block size
based on the procedure defined in Clause 6.1.4.2.
3GPP
Release 16 120 3GPP TS 38.214 V16.1.0 (2020-03)
When the UE is scheduled with multiple PUSCHs by a DCI, as described in clause 6.1.2.1, the bits of rv field and NDI
field, respectively, in the DCI are one to one mapped to the scheduled PUSCH(s) with the corresponding transport
block(s) in the scheduled order where the LSB bits of the rv field and NDI field, respectively, correspond to the last
scheduled PUSCH.
Within a cell group, a UE is not required to handle PUSCH(s) transmissions in slot sj in serving cell-j, and for j = 0,1,2..
J-1, slot sj overlapping with any given point in time, if the following condition is not satisfied at that point in time:
∑𝑀−1
∑𝐽−1
𝑗=0 𝜇(𝑗) ≤ 𝐷𝑎𝑡𝑎𝑅𝑎𝑡𝑒,
𝑇𝑠𝑙𝑜𝑡
where
- J is the number of configured serving cells belong to a frequency range
- for the j-th serving cell,
- M is the number of TB(s) transmitted in slot-sj.
- Tslot(j) =10-3/2(j), where (j) is the numerology for PUSCH(s) in slot sj of the j-th serving cell.
𝐴
𝐶
- C is the total number of code blocks for the transport block defined in Clause 5.2.2 [5, TS 38.212].
- 𝐶′is the number of scheduled code blocks for the transport block as defined in Clause 5.4.2.1
[5,38.212]
- 𝐷𝑎𝑡𝑎𝑅𝑎𝑡𝑒 [Mbps] is computed as the maximum data rate summed over all the carriers in the frequency range
for any signaled band combination and feature set consistent with the configured servings cells, where the data
rate value is given by the formula in Clause 4.1.2 in [13, TS 38.306], including the scaling factor f(i).
For a j-th serving cell, if higher layer parameter processingType2Enabled of PUSCH-ServingCellConfig is configured
for the serving cell and set to enable, or if at least one IMCS > W for a PUSCH, where W = 28 for MCS tables 5.1.3.1-1
and 5.1.3.1-3, and W = 27 for MCS tables 5.1.3.1-2, 6.1.4.1-1, and 6.1.4.1-2, the UE is not required to handle PUSCH
transmissions, if the following condition is not satisfied:
∑𝑀−1
𝜇 ≤ 𝐷𝑎𝑡𝑎𝑅𝑎𝑡𝑒𝐶𝐶
𝐿 × 𝑇𝑠
where
- 𝐿 is the number of symbols assigned to the PUSCH
- M is the number of TB in the PUSCH

𝜇 10−3
- 𝑇𝑠 = 𝑠𝑙𝑜𝑡 where  is the numerology of the PUSCH
2𝜇 ∙𝑁𝑠𝑦𝑚𝑏
𝐴
𝐶
- C is the total number of code blocks for the transport block defined in Clause 5.2.2 [5, TS 38.212]
- 𝐶′ is the number of scheduled code blocks for the transport block as defined in Clause 5.4.2.1 [5, TS 38.212]
- 𝐷𝑎𝑡𝑎𝑅𝑎𝑡𝑒𝐶𝐶 [Mbps] is computed as the maximum data rate for a carrier in the frequency band of the serving
cell for any signaled band combination and feature set consistent with the serving cell, where the data rate value
is given by the formula in Clause 4.1.2 in [13, TS 38.306], including the scaling factor f(i).
3GPP
Release 16 121 3GPP TS 38.214 V16.1.0 (2020-03)

For a PUSCH scheduled by RAR UL grant or
for a PUSCH scheduled by a fallbackRAR UL grant or
for a MsgA PUSCH transmission, or
for a PUSCH scheduled by a DCI format 0_0 with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI, or
for a PUSCH scheduled by a DCI format 0_1 for DCI format 0_2 with CRC scrambled by C-RNTI, MCS-C-RNTI, CS-
RNTI, SP-CSI-RNTI, or
for a PUSCH with configured grant using CS-RNTI, and
if transform precoding is disabled for this PUSCH transmission according to Clause 6.1.3
- if mcs-Table-ForDCIFormat0_2 in pusch-Config is set to 'qam256', and PUSCH is scheduled by a PDCCH with

DCI format 0_2 with CRC scrambled by C-RNTI or SP-CSI-RNTI,
used in the physical uplink shared channel;
- elseif the UE is not configured with MCS-C-RNTI, mcs-Table-ForDCIFormat0_2 in pusch-Config is set to

'qam64LowSE', and the PUSCH is scheduled by a PDCCH by a PDCCH with DCI format 0_2 with CRC
scrambled by C-RNTI or SP-CSI-RNTI,
used in the physical uplink shared channel.
- elseif mcs-Table in pusch-Config is set to 'qam256', and PUSCH is scheduled by a PDCCH with DCI format 0_1
with CRC scrambled by C-RNTI or SP-CSI-RNTI,
- elseif the UE is not configured with MCS-C-RNTI, mcs-Table in pusch-Config is set to 'qam64LowSE', and the
PUSCH is scheduled by a PDCCH with a DCI format other than DCI format 0_2 in a UE-specific search space
with CRC scrambled by C-RNTI or SP-CSI-RNTI,
- elseif the UE is configured with MCS-C-RNTI, and the PUSCH is scheduled by a PDCCH with CRC scrambled
by MCS-C-RNTI,
- elseif mcs-Table in configuredGrantConfig is set to 'qam256',
- if PUSCH is scheduled by a PDCCH with CRC scrambled by CS-RNTI or
- if PUSCH is transmitted with configured grant
- elseif mcs-Table in configuredGrantConfig is set to 'qam64LowSE',
- if PUSCH is transmitted with configured grant,
3GPP
Release 16 122 3GPP TS 38.214 V16.1.0 (2020-03)
- elseif for a MsgA PUSCH transmission,
- the UE shall use higher layer parameter MsgA-MCS for IMCS and Table 5.1.3.1-1 to determine the Target code
rate (R) used in the physical uplink shared channel.
- the UE shall use q=2 for determining modulation order Qm in Table 5.1.3.1-1.
- else
else
- if mcs-TableTransformPrecoder-ForDCIFormat0_2 in pusch-Config is set to 'qam256', and PUSCH is

scheduled by a PDCCH with DCI format 0_2 with CRC scrambled by C-RNTI or SP-CSI-RNTI,
- the UE shall use IMCS and Table 5.1.3.1.-2 to determine the modulation order (Qm) and Target code rate (R)
- elseif the UE is not configured with MCS-C-RNTI, mcs-Table-ForDCIFormat0_2 in pusch-Config is set to

'qam64LowSE', and the PUSCH is scheduled by a PDCCH with DCI format 0_2 with CRC scrambled by C-
RNTI or SP-CSI-RNTI,
- elseif mcs-TableTransformPrecoder in pusch-Config is set to 'qam256', and PUSCH is scheduled by a PDCCH

with DCI format 0_1 with CRC scrambled by C-RNTI or SP-CSI-RNTI,
- the UE shall use IMCS and Table 5.1.3.1.-2 to determine the modulation order (Qm) and Target code rate (R)
- elseif the UE is not configured with MCS-C-RNTI, mcs-TableTransformPrecoder in pusch-Config is set to

'qam64LowSE', and the PUSCH is scheduled by a PDCCH with a DCI format other than DCI format 0_2 in a
UE-specific search space with CRC scrambled by C-RNTI or SP-CSI-RNTI,
- elseif the UE is configured with MCS-C-RNTI, and the PUSCH is scheduled by a PDCCH with CRC scrambled
by MCS-C-RNTI,
- elseif mcs-TableTransformPrecoder in configuredGrantConfig is set to 'qam256',
- elseif mcs-TableTransformPrecoder in configuredGrantConfig is set to 'qam64LowSE',
- elseif for a MsgA PUSCH transmission,
3GPP
Release 16 123 3GPP TS 38.214 V16.1.0 (2020-03)
- the UE shall use higher layer parameter MsgA-MCS for IMCS and Table 6.1.4.1-1 to determine the Target code
rate (R) used in the physical uplink shared channel.
- the UE shall use q=2 for determining modulation order Qm in Table 6.1.4.1-1.
- else
- the UE shall use IMCS and Table 6.1.4.1-1to determine the modulation order (Qm) and Target code rate (R)
end
For Table 6.1.4.1-1 and Table 6.1.4.1-2, if higher layer parameter tp-pi2BPSK is configured, q = 1 otherwise q=2.
Table 6.1.4.1-1: MCS index table for PUSCH with transform precoding and 64QAM

Target code Rate R x 1024
IMCS Qm efficiency
0 q 240/ q 0.2344
1 q 314/ q 0.3066
2 2 193 0.3770
3 2 251 0.4902
4 2 308 0.6016
5 2 379 0.7402
6 2 449 0.8770
7 2 526 1.0273
8 2 602 1.1758
9 2 679 1.3262
10 4 340 1.3281
11 4 378 1.4766
12 4 434 1.6953
13 4 490 1.9141
14 4 553 2.1602
15 4 616 2.4063
16 4 658 2.5703
17 6 466 2.7305
18 6 517 3.0293
19 6 567 3.3223
20 6 616 3.6094
21 6 666 3.9023
22 6 719 4.2129
23 6 772 4.5234
24 6 822 4.8164
25 6 873 5.1152
26 6 910 5.3320
27 6 948 5.5547
28 q reserved
29 2 reserved
30 4 reserved
31 6 reserved
3GPP
Release 16 124 3GPP TS 38.214 V16.1.0 (2020-03)
Table 6.1.4.1-2: MCS index table 2 for PUSCH with transform precoding and 64QAM

Target code Rate R x 1024
IMCS Qm efficiency
0 q 60/q 0.0586
1 q 80/q 0.0781
2 q 100/q 0.0977
3 q 128/q 0.1250
4 q 156/q 0.1523
5 q 198/q 0.1934
6 2 120 0.2344
7 2 157 0.3066
8 2 193 0.3770
9 2 251 0.4902
10 2 308 0.6016
11 2 379 0.7402
12 2 449 0.8770
13 2 526 1.0273
14 2 602 1.1758
15 2 679 1.3262
16 4 378 1.4766
17 4 434 1.6953
18 4 490 1.9141
19 4 553 2.1602
20 4 616 2.4063
21 4 658 2.5703
22 4 699 2.7305
23 4 772 3.0156
24 6 567 3.3223
25 6 616 3.6094
26 6 666 3.9023
27 6 772 4.5234
28 q reserved
29 2 reserved
30 4 reserved
31 6 reserved

For a PUSCH scheduled by RAR UL grant or
for a PUSCH scheduled by fallbackRAR UL grant or
for a PUSCH scheduled by a DCI format 0_0 with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI, or
for a PUSCH scheduled by a DCI format 0_1 or DCI format 0_2 with CRC scrambled by C-RNTI, MCS-C-RNTI, CS-
RNTI, SP-CSI-RNTI, or
for a PUSCH transmission with configured grant, or
for a MsgA PUSCH transmission,
if
- 0  I MCS  27 and transform precoding is disabled and Table 5.1.3.1-2 is used, or
- 0  I MCS  28 and transform precoding is disabled and a table other than Table 5.1.3.1-2 is used, or
- 0  I MCS  27 and transform precoding is enabled, the UE shall first determine the TBS as specified below:
3GPP
Release 16 125 3GPP TS 38.214 V16.1.0 (2020-03)
The UE shall first determine the number of REs (NRE) within the slot:
- A UE first determines the number of REs allocated for PUSCH within a PRB (N RE
'
) by
-
'
N RE = N scRB · N symb
sh
− N DMRS
PRB
− N oh
PRB RB
, where N sc = 12 is the number of subcarriers in the frequency domain
sh
in a physical resource block, N symb is the number of symbols L of the PUSCH allocation according to
Clause 6.1.2.1 for scheduled PUSCH or Clause 6.1.2.3 for configured PUSCH, N DMRS PRB is the number of REs
for DM-RS per PRB in the allocated duration including the overhead of the DM-RS CDM groups without
data, as described for PUSCH with a configured grant in Clause 6.1.2.3 or as indicated by DCI format 0_1 or
DCI format 0_2 or as described for DCI format 0_0 in Clause 6.2.2, and N ohPRB is the overhead configured
PRB
by higher layer parameter xOverhead in PUSCH-ServingCellConfig. If the N oh is not configured (a value
PRB PRB
from 6, 12, or 18), the N oh is assumed to be 0. For Msg3 transmission the N oh is always set to 0.
- A UE determines the total number of REs allocated for PUSCH (N ) by N

RE RE ( '
)
= min 156, N RE  nPRB
where n PRB is the total number of allocated PRBs for the UE.
- Next, proceed with steps 2-4 as defined in Clause 5.1.3.2
else if
- 28  I MCS  31 and transform precoding is disabled and Table 5.1.3.1-2 is used, or
- 28  I MCS  31 and transform precoding is enabled,
initial PUSCH for the same transport block is transmitted with configured grant,
- the TBS shall be determined from configuredGrantConfig for a configured grant Type 1 PUSCH.
- the TBS shall be determined from the most recent PDCCH scheduling a configured grant Type 2 PUSCH.
else
initial PUSCH for the same transport block is transmitted with configured grant,
- the TBS shall be determined from configuredGrantConfig for a configured grant Type 1 PUSCH.
- the TBS shall be determined from the most recent PDCCH scheduling a configured grant Type 2 PUSCH.
6.1.5 Code block group based PUSCH transmission

6.1.5.1 UE procedure for grouping of code blocks to code block groups
If a UE is configured to transmit code block group (CBG) based transmissions by receiving the higher layer parameter
codeBlockGroupTransmission in PUSCH-ServingCellConfig, the UE shall determine the number of CBGs for a
PUSCH transmission as
M = min (N , C ) ,
where N is the maximum number of CBGs per transport block as configured by

maxCodeBlockGroupsPerTransportBlock in PUSCH-ServingCellConfig, and C is the number of code blocks in the
PUSCH according to the procedure defined in Clause 6.2.3 of [5, TS 38.212].
Define M 1 = mod (C , M ) , K1 =  C  , and K 2 =  C  .

M  M 
3GPP
Release 16 126 3GPP TS 38.214 V16.1.0 (2020-03)
If M 1  0 , CBG m, m = 0,1,..., M 1 − 1 , consists of code blocks with indices m  K 1 + k , k = 0,1,..., K 1 − 1 . CBG m,

m = M 1 , M 1 + 1,..., M − 1 , consists of code blocks with indices M 1  K 1 + (m − M 1 )  K 2 + k , k = 0,1,..., K 2 − 1 .
6.1.5.2 UE procedure for transmitting code block group based transmissions

If a UE is configured to transmit code block group based transmissions by receiving the higher layer parameter
codeBlockGroupTransmission in PUSCH-ServingCellConfig,
- For an initial transmission of a TB as indicated by the New Data Indicator field of the scheduling DCI, the UE
may expect that the CBGTI field indicates all the CBGs of the TB are to be transmitted, and the UE shall include
all the code block groups of the TB.
- For a retransmission of a TB as indicated by the New Data Indicator field of the scheduling DCI, the UE shall
include only the CBGs indicated by the CBGTI field of the scheduling DCI.
A bit value of 0' in the CBGTI field indicates that the corresponding CBG is not to be transmitted and 1' indicates that it
is to be transmitted. The order of CBGTI field bits is such that the CBGs are mapped in order from CBG#0 onwards
starting from the MSB.
6.2 UE reference signal (RS) procedure

6.2.1 UE sounding procedure
The UE may be configured with one or more Sounding Reference Signal (SRS) resource sets as configured by the
higher layer parameter SRS-ResourceSet. For each SRS resource set, a UE may be configured with K  1 SRS
resources (higher layer parameter SRS-Resource), where the maximum value of K is indicated by UE capability [13,
38.306] except when SRS is configured with the higher layer parameter [SRS-for-positioning] in which case the
maximum value of K is 16. The SRS resource set applicability is configured by the higher layer parameter usage in
SRS-ResourceSet. When the higher layer parameter usage is set to 'beamManagement', only one SRS resource in each
of multiple SRS sets may be transmitted at a given time instant, but the SRS resources in different SRS resource sets
with the same time domain behaviour in the same BWP may be transmitted simultaneously.
For aperiodic SRS at least one state of the DCI field is used to select at least one out of the configured SRS resource
set(s).
The following SRS parameters are semi-statically configurable by higher layer parameter SRS-Resource.
- srs-ResourceId determines SRS resource configuration identity.
- Number of SRS ports as defined by the higher layer parameter nrofSRS-Ports and described in Clause 6.4.1.4 of
[4, TS 38.211]. If not configured, nrofSRS-Ports is 1.
- Time domain behaviour of SRS resource configuration as indicated by the higher layer parameter resourceType,
which may be periodic, semi-persistent, aperiodic SRS transmission as defined in Clause 6.4.1.4 of [4, TS
38.211].
- Slot level periodicity and slot level offset as defined by the higher layer parameters periodicityAndOffset-p or
periodicityAndOffset-sp for an SRS resource of type periodic or semi-persistent. The UE is not expected to be
configured with SRS resources in the same SRS resource set SRS-ResourceSet with different slot level
periodicities. For an SRS-ResourceSet configured with higher layer parameter resourceType set to 'aperiodic', a
slot level offset is defined by the higher layer parameter slotOffset except when SRS is configured with the
higher layer parameter [SRS-for-positioning] in which case the slot level offset is defined by the higher layer
parameter slotOffset for each SRS resource.
- Number of OFDM symbols in the SRS resource, starting OFDM symbol of the SRS resource within a slot
including repetition factor R as defined by the higher layer parameter resourceMapping and described in Clause
6.4.1.4 of [4, TS 38.211]. If R is not configured, then R is equal to the number of OFDM symbols in the SRS
resource.
- SRS bandwidth B SRS and C SRS , as defined by the higher layer parameter freqHopping and described in Clause
6.4.1.4 of [4, TS 38.211]. If not configured, then B SRS = 0.
3GPP
Release 16 127 3GPP TS 38.214 V16.1.0 (2020-03)
- Frequency hopping bandwidth, bhop , as defined by the higher layer parameter freqHopping and described in
Clause 6.4.1.4 of [4, TS 38.211]. If not configured, then bhop = 0.
- Defining frequency domain position and configurable shift, as defined by the higher layer parameters
freqDomainPosition and freqDomainShift, respectively, and described in Clause 6.4.1.4 of [4, TS 38.211]. If
freqDomainPosition is not configured, freqDomainPosition is zero.
- Cyclic shift, as defined by the higher layer parameter cyclicShift-n2, cyclicShift-n4, or cyclicShift-n8 for
transmission comb value 2, 4 and 8, respectively, and described in Clause 6.4.1.4 of [4, TS 38.211].
- Transmission comb value as defined by the higher layer parameter transmissionComb described in Clause
6.4.1.4 of [4, TS 38.211].
- Transmission comb offset as defined by the higher layer parameter combOffset-n2, combOffset-n4, or
combOffset-n8 for transmission comb value 2, 4, or 8 respectively, and described in Clause 6.4.1.4 of [4, TS
38.211].
- SRS sequence ID as defined by the higher layer parameter sequenceId in Clause 6.4.1.4 of [4].
- The configuration of the spatial relation between a reference RS and the target SRS, where the higher layer
parameter spatialRelationInfo, if configured, contains the ID of the reference RS. The reference RS may be an
SS/PBCH block, CSI-RS configured on serving cell indicated by higher layer parameter servingCellId if present,
same serving cell as the target SRS otherwise, or an SRS configured on uplink BWP indicated by the higher
layer parameter uplinkBWP, and serving cell indicated by the higher layer parameter servingCellId if present,
same serving cell as the target SRS otherwise. When SRS is configured by the higher layer parameter [SRS-for-
positioning] the reference RS may also be a DL PRS configured on a serving cell, an SS/PBCH block or a DL
PRS of a non-serving cell indicated by a higher layer parameter.
The UE may be configured by the higher layer parameter resourceMapping in SRS-Resource with an SRS resource
occupying N S  1, 2, 4 adjacent symbols within the last 6 symbols of the slot, where all antenna ports of the SRS
resources are mapped to each symbol of the resource. When the SRS is configured with the higher layer parameter
[SRS-for-positioning] the higher layer parameter resourceMapping in SRS-Resource with an SRS resource occupying
𝑁𝑆 ∈ {1,2,4,8,12} adjacent symbols anywhere within the slot.
If a UE is not configured with [intraUEPrioritization] and PUSCH and SRS configured by SRS-Resource are
transmitted in the same slot on a serving cell, the UE may only be configured to transmit SRS after the transmission of
the PUSCH and the corresponding DM-RS.
If a UE is configured with [intraUEPrioritization] and a PUSCH transmission would overlap in time with an SRS
transmission on a serving cell, the UE does not transmit the SRS in the overlapping symbol(s).
For a UE configured with one or more SRS resource configuration(s), and when the higher layer parameter
resourceType in SRS-Resource is set to 'periodic':
- if the UE is configured with the higher layer parameter spatialRelationInfo containing the ID of a reference 'ssb-
Index', the UE shall transmit the target SRS resource with the same spatial domain transmission filter used for
the reception of the reference SS/PBCH block, if the higher layer parameter spatialRelationInfo contains the ID
of a reference 'csi-RS-Index', the UE shall transmit the target SRS resource with the same spatial domain
transmission filter used for the reception of the reference periodic CSI-RS or of the reference semi-persistent
CSI-RS, if the higher layer parameter spatialRelationInfo containing the ID of a reference 'srs', the UE shall
transmit the target SRS resource with the same spatial domain transmission filter used for the transmission of the
reference periodic SRS. When the SRS is configured by the higher layer parameter [SRS-for-positioning] and if
the higher layer parameter spatialRelationInfo contains the ID of a reference 'DL-PRS-ResourceId', the UE shall
transmit the target SRS resource with the same spatial domain transmission filter used for the reception of the
reference DL PRS.
resourceType in SRS-Resource is set to 'semi-persistent':
- when a UE receives an activation command, as described in clause 6.1.3.17 of [10, TS 38.321], for an SRS
resource, and when the UE would transmit a PUCCH with HARQ-ACK information in slot n corresponding to
the PDSCH carrying the activation command is transmitted in slot n, the corresponding actions in [10, TS
38.321] and the UE assumptions on SRS transmission corresponding to the configured SRS resource set shall be
3GPP
Release 16 128 3GPP TS 38.214 V16.1.0 (2020-03)
where  is the SCS configuration for the

applied starting from the first slot that is after slot 𝑛 + 3𝑁𝑠𝑙𝑜𝑡
PUCCH. The activation command also contains spatial relation assumptions provided by a list of references to
reference signal IDs, one per element of the activated SRS resource set. Each ID in the list refers to a reference
SS/PBCH block, NZP CSI-RS resource configured on serving cell indicated by Resource Serving Cell ID field in
the activation command if present, same serving cell as the SRS resource set otherwise, or SRS resource
configured on serving cell and uplink bandwidth part indicated by Resource Serving Cell ID field and Resource
BWP ID field in the activation command if present, same serving cell and bandwidth part as the SRS resource set
otherwise. When the SRS is configured with the higher layer parameter [SRS-for-positioning], each ID in the list
of reference signal IDs may also refer to a reference SS/PBCH block of a non-serving cell or DL PRS of a
serving or non-serving cell indicated by a higher layer parameter.
- if an SRS resource in the activated resource set is configured with the higher layer parameter spatialRelationInfo,
the UE shall assume that the ID of the reference signal in the activation command overrides the one configured
in spatialRelationInfo.
- when a UE receives a deactivation command [10, TS 38.321] for an activated SRS resource set, and when the
UE would transmit a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH carrying the
deactivation command, the corresponding actions in [10, TS 38.321] and UE assumption on cessation of SRS
transmission corresponding to the deactivated SRS resource set shall apply starting from the first slot that is after
slot 𝑛 + 3𝑁𝑠𝑙𝑜𝑡
CSI-RS, if the higher layer parameter spatialRelationInfo contains the ID of a reference 'srs', the UE shall
transmit the target SRS resource with the same spatial domain transmission filter used for the transmission of the
reference periodic SRS or of the reference semi-persistent SRS. When the SRS is configured by the higher layer
parameter [SRS-for-positioning] and if the higher layer parameter spatialRelationInfo contains the ID of a
reference 'DL-PRS-ResourceId', the UE shall transmit the target SRS resource with the same spatial domain
transmission filter used for the reception of the reference DL PRS.
If the UE has an active semi-persistent SRS resource configuration and has not received a deactivation command, the
semi-persistent SRS configuration is considered to be active in the UL BWP which is active, otherwise it is considered
suspended.
resourceType in SRS-Resource is set to 'aperiodic':
- the UE receives a configuration of SRS resource sets,
- the UE receives a downlink DCI, a group common DCI, or an uplink DCI based command where a codepoint of
the DCI may trigger one or more SRS resource set(s). For SRS in a resource set with usage set to 'codebook' or
'antennaSwitching', the minimal time interval between the last symbol of the PDCCH triggering the aperiodic
SRS transmission and the first symbol of SRS resource is N2. Otherwise, the minimal time interval between the
last symbol of the PDCCH triggering the aperiodic SRS transmission and the first symbol of SRS resource is N2
+ 14. The minimal time interval in units of OFDM symbols is counted based on the minimum subcarrier spacing
between the PDCCH and the aperiodic SRS.
- If the UE receives the DCI triggering aperiodic SRS in slot n and except when SRS is configured with the higher
layer parameter [SRS-for-positioning], the UE transmits aperiodic SRS in each of the triggered SRS resource
 2 SRS   N CA CA
N slot  
 + k +    2 SRS  , if UE is configured with CA-slot-
slot ,offset , PDCCH ,offset , SRS
set(s) in slot  n  −
 2 PDCCH   2 offset ,PDCCH 2 offset ,SRS 
 
 
 2 SRS 

offset for at least one of the triggered and triggering cell, Ks = n   + k , otherwise, and where
 2 
PDCCH
- k is configured via higher layer parameter slotOffset for each triggered SRS resources set and is based on the
subcarrier spacing of the triggered SRS transmission, µSRS and µPDCCH are the subcarrier spacing
configurations for triggered SRS and PDCCH carrying the triggering command respectively;
3GPP
Release 16 129 3GPP TS 38.214 V16.1.0 (2020-03)
offset, PDCCH and 𝜇offset,PDCCH are the 𝑁slot, offset and the  offset , respectively, which are determined by
CA CA
- 𝑁slot,
higher-layer configured CA-slot-offset for the cell receiving the PDCCH, 𝑁𝐶𝐴
𝑠𝑙𝑜𝑡,𝑜𝑓𝑓𝑠𝑒𝑡,𝑆𝑅𝑆 and 𝜇𝑜𝑓𝑓𝑠𝑒𝑡,𝑆𝑅𝑆 are the
CA
N slot ,offset and the
 offset , respectively, which are determined by higher-layer configured CA-slot-offset for the
cell transmitting the SRS, as defined in [4, TS 38.211] clause 4.5.
- If the UE receives the DCI triggering aperiodic SRS in slot n and when SRS is configured with the higher layer
parameter [SRS-for-positioning], the UE transmits every aperiodic SRS resource in each of the triggered SRS
 2 SRS   N CA CA
N slot  
 + k +    2 SRS  where
slot ,offset , PDCCH ,offset , SRS
resource set(s) in slot  n  −
 2 PDCCH   2 offset ,PDCCH 2 offset ,SRS 
 
 
- k is configured via higher layer parameter slotOffset for each aperiodic SRS resource in each triggered SRS
resources set and is based on the subcarrier spacing of the triggered SRS transmission, µSRS and µPDCCH are
the subcarrier spacing configurations for triggered SRS and PDCCH carrying the triggering command
respectively;
offset and the  offset for the {scheduling, scheduled} carrier pair is defined in [4, TS 38.211] clause 4.5.
CA
- 𝑁slot,
CSI-RS, or of the latest reference aperiodic CSI-RS. If the higher layer parameter spatialRelationInfo contains
the ID of a reference 'srs', the UE shall transmit the target SRS resource with the same spatial domain
transmission filter used for the transmission of the reference periodic SRS or of the reference semi-persistent
SRS or of the reference aperiodic SRS. When the SRS is configured by the higher layer parameter [SRS-for-
positioning] and if the higher layer parameter spatialRelationInfo contains the ID of a reference 'DL-PRS-
ResourceId', the UE shall transmit the target SRS resource with the same spatial domain transmission filter used
for the reception of the reference DL PRS.
- when a UE receives an spatial relation update command, as described in clause 6.1.3.xx of [10, TS 38.321], for
an SRS resource, and when the HARQ-ACK corresponding to the PDSCH carrying the update command is
transmitted in slot n, the corresponding actions in [10, TS 38.321] and the UE assumptions on updating spatial
relation for the SRS resource shall be applied for SRS transmission starting from the first slot that is after slot
𝑛 + 3𝑁𝑠𝑙𝑜𝑡 . [The update command contains spatial relation assumptions provided by a list of references to
reference signal IDs, one per element of the updated SRS resource set. Each ID in the list refers to a reference
SS/PBCH block, NZP CSI-RS resource configured on serving cell indicated by Resource Serving Cell ID field in
the update command if present, same serving cell as the SRS resource set otherwise, or SRS resource configured
on serving cell and uplink bandwidth part indicated by Resource Serving Cell ID field and Resource BWP ID
field in the update command if present, same serving cell and bandwidth part as the SRS resource set otherwise.]
When the UE is configured with the higher layer parameter usage in SRS-ResourceSet set to 'antennaSwitching',
the UE shall not expect to be configured with different spatial relations for SRS resources in the same SRS
resource set.
The UE is not expected to be configured with different time domain behavior for SRS resources in the same SRS
resource set. The UE is also not expected to be configured with different time domain behavior between SRS resource
and associated SRS resources set.
For single carrier operations, the UE does not expect to be configured on overlapping symbols with a SRS resource
configured by the higher layer parameter [SRS-for-positioning] and a SRS resource configured by the higher layer
parameter SRS-Resource with resourceType of both SRS resources as 'periodic'.
For single carrier operations, the UE does not expect to be triggered to transmit SRS on overlapping symbols with a
SRS resource configured by the higher layer parameter [SRS-for-positioning] and a SRS resource configured by the
higher layer parameter SRS-Resource with resourceType of both SRS resources as 'semi-persistent' or 'aperiodic'.
The SRS request field [5, TS38.212] in DCI format 0_1, 1_1, 0_2 (if SRS request field is present), 1_2 (if SRS request
field is present) indicates the triggered SRS resource set given in Table 7.3.1.1.2-24 of [5, TS 38.212]. The 2-bit SRS
request field [5, TS38.212] in DCI format 2_3 indicates the triggered SRS resource set given in Clause 7.3 of [5, TS
38.212] if the UE is configured with higher layer parameter srs-TPC-PDCCH-Group set to 'typeB', or indicates the SRS
3GPP
Release 16 130 3GPP TS 38.214 V16.1.0 (2020-03)
transmission on a set of serving cells configured by higher layers if the UE is configured with higher layer parameter
srs-TPC-PDCCH-Group set to 'typeA'.
For PUCCH and SRS on the same carrier, a UE shall not transmit SRS when semi-persistent and periodic SRS are
configured in the same symbol(s) with PUCCH carrying only CSI report(s), or only L1-RSRP report(s), or only L1-
SINR report(s). A UE shall not transmit SRS when semi-persistent or periodic SRS is configured or aperiodic SRS is
triggered to be transmitted in the same symbol(s) with PUCCH carrying HARQ-ACK, link recovery request (as defined
in clause 9.2.4 of [6, 38.213]) and/or SR. In the case that SRS is not transmitted due to overlap with PUCCH, only the
SRS symbol(s) that overlap with PUCCH symbol(s) are dropped. PUCCH shall not be transmitted when aperiodic SRS
is triggered to be transmitted to overlap in the same symbol with PUCCH carrying semi-persistent/periodic CSI
report(s) or semi-persistent/periodic L1-RSRP report(s) only, or only L1-SINR report(s).
In case of intra-band carrier aggregation or in inter-band CA band-band combination where simultaneous SRS and
PUCCH/PUSCH transmissions are not allowed, a UE is not expected to be configured with SRS from a carrier and
PUSCH/UL DM-RS/UL PT-RS/PUCCH formats from a different carrier in the same symbol.
In case of intra-band carrier aggregation or in inter-band CA band-band combination where simultaneous SRS and
PRACH transmissions are not allowed, a UE shall not transmit simultaneously SRS resource(s) from a carrier and
PRACH from a different carrier.
In case a SRS resource with resourceType set as 'aperiodic' is triggered on the OFDM symbol(s) configured with
periodic/semi-persistent SRS transmission, the UE shall transmit the aperiodic SRS resource and only the
periodic/semi-persistent SRS symbol(s) overlapping within the symbol(s) are dropped, while the periodic/semi-
persistent SRS symbol(s) that are not overlapped with the aperiodic SRS resource are transmitted. In case a SRS
resource with resourceType set as 'semi-persistent' is triggered on the OFDM symbol(s) configured with periodic SRS
transmission, the UE shall transmit the semi-persistent SRS resource and only the periodic SRS symbol(s) overlapping
within the symbol(s) are dropped, while the periodic SRS symbol(s) that are not overlapped with the semi-persistent
SRS resource are transmitted.
When the UE is configured with the higher layer parameter usage in SRS-ResourceSet set to 'antennaSwitching', and a
guard period of Y symbols is configured according to Clause 6.2.1.2, the UE shall use the same priority rules as defined
above during the guard period as if SRS was configured.
When a spatialRelationInfo is activated/updated for a semi-persistent or aperiodic SRS resource configured by the
higher layer parameter SRS-Resource by a MAC CE for a set of CCs/BWPs, where the applicable list of CCs is
indicated by higher layer parameter [applicableCellList], the spatialRelationInfo is applied for the semi-persistent or
aperiodic SRS resource(s) with the same SRS resource ID for all the BWPs in the indicated CCs.
When the higher layer parameter enableDefaultBeamPlForSRS is set 'enabled', and if the higher layer parameter
spatialRelationInfo for the SRS resource, except for the SRS resource with the higher layer parameter usage in SRS-
ResourceSet set to 'beamManagement' or for the SRS resource with the higher layer parameter usage in SRS-
ResourceSet set to 'nonCodebook' with configuration of associatedCSI-RS or for the SRS resource configured by the
higher layer parameter [SRS-for-positioning], is not configured in FR2 and if the UE is not configured with higher layer
parameter(s) pathlossReferenceRS, the UE shall transmit the target SRS resource
- with the same spatial domain transmission filter used for the reception of the CORESET with the lowest
controlResourceSetId in the active DL BWP in the CC.
- with the same spatial domain transmission filter used for the reception of the activated TCI state with the lowest
ID applicable to PDSCH in the active DL BWP of the CC if the UE is not configured with any CORESET in the
CC
6.2.1.1 UE SRS frequency hopping procedure

For a given SRS resource, the UE is configured with repetition factor R∈{1,2,4} by higher layer parameter
resourceMapping in SRS-Resource where R≤Ns. When frequency hopping within an SRS resource in each slot is not
configured (R=Ns), each of the antenna ports of the SRS resource in each slot is mapped in all the N s symbols to the
same set of subcarriers in the same set of PRBs. When frequency hopping within an SRS resource in each slot is
configured without repetition (R=1), according to the SRS hopping parameters B SRS , C SRS and bhop defined in Clause
6.4.1.4 of [4, TS 38.211], each of the antenna ports of the SRS resource in each slot is mapped to different sets of
subcarriers in each OFDM symbol, where the same transmission comb value is assumed for different sets of subcarriers.
When both frequency hopping and repetition within an SRS resource in each slot are configured (Ns=4, R=2), each of
the antenna ports of the SRS resource in each slot is mapped to the same set of subcarriers within each pair of R
3GPP
Release 16 131 3GPP TS 38.214 V16.1.0 (2020-03)
adjacent OFDM symbols, and frequency hopping across the two pairs is according to the SRS hopping parameters B SRS
, C SRS and bhop .
A UE may be configured N s = 2 or 4 adjacent symbol aperiodic SRS resource with intra-slot frequency hopping
within a bandwidth part, where the full hopping bandwidth is sounded with an equal-size subband across N s symbols
when frequency hopping is configured with R=1. A UE may be configured N s = 4 adjacent symbols aperiodic SRS
resource with intra-slot frequency hopping within a bandwidth part, where the full hopping bandwidth is sounded with
an equal-size subband across two pairs of R adjacent OFDM symbols, when frequency hopping is configured with R=2.
Each of the antenna ports of the SRS resource is mapped to the same set of subcarriers within each pair of R adjacent
OFDM symbols of the resource.
A UE may be configured N s = 1 symbol periodic or semi-persistent SRS resource with inter-slot hopping within a
bandwidth part, where the SRS resource occupies the same symbol location in each slot. A UE may be configured
N s = 2 or 4 symbol periodic or semi-persistent SRS resource with intra-slot and inter-slot hopping within a bandwidth
part, where the N-symbol SRS resource occupies the same symbol location(s) in each slot. For Ns=4, when frequency
hopping is configured with R=2, intra-slot and inter-slot hopping is supported with each of the antenna ports of the SRS
resource mapped to different sets of subcarriers across two pairs of R adjacent OFDM symbol(s) of the resource in each
slot. Each of the antenna ports of the SRS resource is mapped to the same set of subcarriers within each pair of R
adjacent OFDM symbols of the resource in each slot. For Ns= R, when frequency hopping is configured, inter-slot
frequency hopping is supported with each of the antenna ports of the SRS resource mapped to the same set of
subcarriers in R adjacent OFDM symbol(s) of the resource in each slot.
6.2.1.2 UE sounding procedure for DL CSI acquisition

When the UE is configured with the higher layer parameter usage in SRS-ResourceSet set as 'antennaSwitching', the UE
may be configured with only one of the following configurations depending on the indicated UE capability
supportedSRS-TxPortSwitch ('t1r2' for 1T2R, 't1r1-t1r2' for 1T=1R/1T2R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't1r1-t1r2-
t1r4' for 1T=1R/1T2R/1T4R, 't1r4-t2r4' for 1T4R/2T4R, 't1r1-t1r2-t2r2-t2r4' for 1T=1R/1T2R/2T=2R/2T4R, 't1r1-t1r2-
t2r2-t1r4-t2r4' for 1T=1R/1T2R/2T=2R/1T4R/2T4R, 't1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r1-t2r2' for 1T=1R/2T=2R,
't4r4' for 4T=4R, or 't1r1-t2r2-t4r4' for 1T=1R/2T=2R/4T=4R):
- For 1T2R, up to two SRS resource sets configured with a different value for the higher layer parameter
resourceType in SRS-ResourceSet set, where each set has two SRS resources transmitted in different symbols,
each SRS resource in a given set consisting of a single SRS port, and the SRS port of the second resource in the
set is associated with a different UE antenna port than the SRS port of the first resource in the same set, or
- For 2T4R, up to two SRS resource sets configured with a different value for the higher layer parameter
resourceType in SRS-ResourceSet set, where each SRS resource set has two SRS resources transmitted in
different symbols, each SRS resource in a given set consisting of two SRS ports, and the SRS port pair of the
second resource is associated with a different UE antenna port pair than the SRS port pair of the first resource, or
- For 1T4R, zero or one SRS resource set configured with higher layer parameter resourceType in SRS-
ResourceSet set to 'periodic' or 'semi-persistent' with four SRS resources transmitted in different symbols, each
SRS resource in a given set consisting of a single SRS port, and the SRS port of each resource is associated with
a different UE antenna port, and
- For 1T4R, zero or two SRS resource sets each configured with higher layer parameter resourceType in SRS-
ResourceSet set to 'aperiodic' and with a total of four SRS resources transmitted in different symbols of two
different slots, and where the SRS port of each SRS resource in the given two sets is associated with a different
UE antenna port. The two sets are each configured with two SRS resources, or one set is configured with one
SRS resource and the other set is configured with three SRS resources. The UE shall expect that the two sets are
both configured with the same values of the higher layer parameters alpha, p0, pathlossReferenceRS, and srs-
PowerControlAdjustmentStates in SRS-ResourceSet. The UE shall expect that the value of the higher layer
parameter aperiodicSRS-ResourceTrigger or the value of an entry in AperiodicSRS-ResourceTriggerList in each
SRS-ResourceSet is the same, and the value of the higher layer parameter slotOffset in each SRS-ResourceSet is
different. Or,
- For 1T=1R, or 2T=2R, or 4T=4R, up to two SRS resource sets each with one SRS resource, where the number of
SRS ports for each resource is equal to 1, 2, or 4.
3GPP
Release 16 132 3GPP TS 38.214 V16.1.0 (2020-03)
The UE is configured with a guard period of Y symbols, in which the UE does not transmit any other signal, in the case
the SRS resources of a set are transmitted in the same slot. The guard period is in-between the SRS resources of the set.
The UE shall expect to be configured with the same number of SRS ports for all SRS resources in the SRS resource
set(s) with higher layer parameter usage set as 'antennaSwitching'.
For 1T2R, 1T4R or 2T4R, the UE shall not expect to be configured or triggered with more than one SRS resource set
with higher layer parameter usage set as 'antennaSwitching' in the same slot. For 1T=1R, 2T=2R or 4T=4R, the UE
shall not expect to be configured or triggered with more than one SRS resource set with higher layer parameter usage
set as 'antennaSwitching' in the same symbol.
The value of Y is defined by Table 6.2.1.2-1.
Table 6.2.1.2-1: The minimum guard period between two SRS resources of an SRS resource set for
antenna switching
 f = 2  15 [kHz] Y [symbol]
0 15 1
1 30 1
2 60 1
3 120 2
6.2.1.3 UE sounding procedure between component carriers

For a carrier of a serving cell with slot formats comprised of DL and UL symbols, not configured for PUSCH/PUCCH
transmission, the UE shall not transmit SRS whenever SRS transmission (including any interruption due to uplink or
downlink RF retuning time [11, TS 38.133] as defined by higher layer parameters switchingTimeUL and
switchingTimeDL of srs-SwitchingTimeNR) on the carrier of the serving cell and PUSCH/PUCCH transmission carrying
HARQ-ACK/positive SR/RI/CRI and/or PRACH happen to overlap in the same symbol and that can result in uplink
transmissions beyond the UE's indicated uplink carrier aggregation capability included in [13, TS 38.306].
transmission, the UE shall not transmit a periodic/semi-persistent SRS whenever periodic/semi-persistent SRS
transmission (including any interruption due to uplink or downlink RF retuning time [11, TS 38.133] as defined by
higher layer parameters switchingTimeUL and switchingTimeDL of srs-SwitchingTimeNR) on the carrier of the serving
cell and PUSCH transmission carrying aperiodic CSI happen to overlap in the same symbol and that can result in uplink
transmission, the UE shall drop PUCCH/PUSCH transmission carrying periodic CSI comprising only CQI/PMI, and/or
SRS transmission on another serving cell configured for PUSCH/PUCCH transmission whenever the transmission and
SRS transmission (including any interruption due to uplink or downlink RF retuning time [11, TS 38.133] as defined by
higher layer parameters switchingTimeUL and switchingTimeDL of srs-SwitchingTimeNR) on the serving cell happen to
overlap in the same symbol and that can result in uplink transmissions beyond the UE's indicated uplink carrier
aggregation capability included in [13, TS 38.306].
transmission, the UE shall drop PUSCH transmission carrying aperiodic CSI comprising only CQI/PMI whenever the
transmission and aperiodic SRS transmission (including any interruption due to uplink or downlink RF retuning time
[11, TS 38.133]) as defined by higher layer parameters switchingTimeUL and switchingTimeDL of srs-
SwitchingTimeNR) on the carrier of the serving cell happen to overlap in the same symbol and that can result in uplink
For an aperiodic SRS triggered in DCI format 2_3 and if the UE is configured with higher layer parameter srs-TPC-
PDCCH-Group set to 'typeA', and given by SRS-CarrierSwitching, without PUSCH/PUCCH transmission, the order of
the triggered SRS transmission on the serving cells follow the order of the serving cells in the indicated set of serving
cells configured by higher layers, where the UE in each serving cell transmits the configured one or two SRS resource
set(s) with higher layer parameter usage set to 'antennaSwitching' and higher layer parameter resourceType in SRS-
ResourceSet set to 'aperiodic'.
For an aperiodic SRS triggered in DCI format 2_3 and if the UE is configured with higher layer parameter srs-TPC-
PDCCH-Group set to 'typeB' without PUSCH/PUCCH transmission, the order of the triggered SRS transmission on the
serving cells follow the order of the serving cells with aperiodic SRS triggered in the DCI, and the UE in each serving
3GPP
Release 16 133 3GPP TS 38.214 V16.1.0 (2020-03)
cell transmits the configured one or two SRS resource set(s) with higher layer parameter usage set to 'antennaSwitching'
and higher layer parameter resourceType in SRS-ResourceSet set to 'aperiodic'.
A UE can be configured with SRS resource(s) on a carrier c1 with slot formats comprised of DL and UL symbols and
not configured for PUSCH/PUCCH transmission. For carrier c1, the UE is configured with higher layer parameter srs-
SwitchFromServCellIndex and srs-SwitchFromCarrier the switching from carrier c2 which is configured for
PUSCH/PUCCH transmission. During SRS transmission on carrier c1 (including any interruption due to uplink or
downlink RF retuning time [11, TS 38.133] as defined by higher layer parameters switchingTimeUL and
switchingTimeDL of srs-SwitchingTimeNR), the UE temporarily suspends the uplink transmission on carrier c2.
If the UE is not configured for PUSCH/PUCCH transmission on carrier c1 with slot formats comprised of DL and UL
symbols, and if the UE is not capable of simultaneous reception and transmission on carrier c1 and serving cell c2, the
UE is not expected to be configured or indicated with SRS resource(s) such that SRS transmission on carrier c1
(including any interruption due to uplink or downlink RF retuning time [11, TS 38.133] as defined by higher layer
parameters switchingTimeUL and switchingTimeDL of srs-SwitchingTimeNR) would collide with the REs
corresponding to the SS/PBCH blocks configured for the UE or the slots belonging to a control resource set indicated
by MIB or SIB1 on serving cell c2.
For n-th (n ≥ 1) aperiodic SRS transmission on a cell c, upon detection of a positive SRS request on a grant, the UE shall commence
this SRS transmission on the configured symbol and slot provided
- it is no earlier than the summation of
- the maximum time duration between the two durations spanned by N OFDM symbols of the numerology of
cell c and the cell carrying the grant respectively, and
- the UL or DL RF retuning time [11, TS 38.133] as defined by higher layer parameters switchingTimeUL and
switchingTimeDL of srs-SwitchingTimeNR,
- it does not collide with any previous SRS transmissions, or interruption due to UL or DL RF retuning time.
otherwise, n-th SRS transmission is dropped, where N is the reported capability as the minimum time interval in unit
of symbols, between the DCI triggering and aperiodic SRS transmission.
In case of inter-band carrier aggregation, a UE can simultaneously transmit SRS and PUCCH/PUSCH across
component carriers in different bands subject to the UE's capability.
In case of inter-band carrier aggregation, a UE can simultaneously transmit PRACH and SRS across component carriers
in different bands subject to UE's capability.
6.2.1.4 UE sounding procedure for positioning purposes
When the SRS is configured by the higher layer parameter [SRS-for-positioning] and if the higher layer parameter
spatialRelationInfo is configured, it contains the ID of the configuration fields of a reference RS according to Clause
6.3.2 of [TS 38.331]. The reference RS can be an SRS configured by the higher layer parameter SRS-Config or [SRS-
for-positioning], CSI-RS, SS/PBCH block, or a DL PRS configured on a serving cell or a SS/PBCH block or a DL PRS
configured on a non-serving cell.
The UE is not expected to transmit multiple SRS resources with different spatial relations in the same OFDM symbol.
If the UE is not configured with the higher layer parameter spatialRelationInfo the UE may use a fixed spatial domain
transmission filter for transmissions of the SRS configured by the higher layer parameter [SRS-for-positioning] across
multiple SRS resources or it may use a different spatial domain transmission filter across multiple SRS resources.
The UE is only expected to transmit an SRS configured the by the higher layer parameter [SRS-for-positioning] within
the active UL BWP of the UE.
When the configuration of SRS is done by the higher layer parameter [SRS-for-positioning], the UE can only be
provided with a single RS source in spatialRelationInfo per SRS resource.
If an SRS configured by the higher parameter [SRS-for-positioning] collides with a scheduled PUSCH, the SRS is
dropped in the symbols where the collision occurs.
3GPP
Release 16 134 3GPP TS 38.214 V16.1.0 (2020-03)
6.2.2 UE DM-RS transmission procedure

When transmitted PUSCH is neither scheduled by DCI format 0_1 with CRC scrambled by C-RNTI, CS-RNTI, SP-
CSI-RNTI or MCS-C-RNTI, nor corresponding to a configured grant, nor being a PUSCH for Type-2 random access
procedure. the UE shall use single symbol front-loaded DM-RS of configuration type 1 on DM-RS port 0 and the
remaining REs not used for DM-RS in the symbols are not used for any PUSCH transmission except for PUSCH with
allocation duration of 2 or less OFDM symbols with transform precoding disabled, additional DM-RS can be
transmitted according to the scheduling type and the PUSCH duration as specified in Table 6.4.1.1.3-3 of [4, TS38.211]
for frequency hopping disabled and as specified in Table 6.4.1.1.3-6 of [4, TS38.211] for frequency hopping enabled,
and
If frequency hopping is disabled:
- The UE shall assume dmrs-AdditionalPosition equals to 'pos2' and up to two additional DM-RS can be
transmitted according to PUSCH duration, or
If frequency hopping is enabled:
- The UE shall assume dmrs-AdditionalPosition equals to 'pos1' and up to one additional DM-RS can be
transmitted according to PUSCH duration.
When transmitted PUSCH is scheduled by activation DCI format 0_0 with CRC scrambled by CS-RNTI, the UE shall
use single symbol front-loaded DM-RS of configuration type provided by higher layer parameter dmrs-Type in
configuredGrantConfig on DM-RS port 0 and the remaining REs not used for DM-RS in the symbols are not used for
any PUSCH transmission except for PUSCH with allocation duration of 2 or less OFDM symbols with transform
precoding disabled, and additional DM-RS with dmrs-AdditionalPosition from configuredGrantConfig can be
transmitted according to the scheduling type and the PUSCH duration as specified in Table 6.4.1.1.3-3 of [4, TS38.211]
for frequency hopping disabled and as specified in Table 6.4.1.1.3-6 of [4, TS38.211] for frequency hopping enabled.
For the UE-specific reference signals generation as defined in Clause 6.4.1.1 of [4, TS 38.211], a UE can be configured
𝐷𝑀𝑅𝑆,𝑖
by higher layers with one or two scrambling identity(s), 𝑛𝐼𝐷 i = 0,1 which are the same for both PUSCH mapping
Type A and Type B.
When transmitted PUSCH is scheduled by DCI format 0_1 with CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI
or MCS-C-RNTI, or corresponding to a configured grant, or being a PUSCH for Type-2 random access procedure,
- the UE may be configured with higher layer parameter dmrs-Type in DMRS-UplinkConfig, and the configured
DM-RS configuration type is used for transmitting PUSCH in as defined in Clause 6.4.1.1 of [4, TS 38.211]. For
MsgA PUSCH transmissions, dmrs-Type is type 1.
- the UE may be configured with the maximum number of front-loaded DM-RS symbols for PUSCH by higher
layer parameter maxLength in DMRS-UplinkConfig, or by higher layer parameter msgA-MaxLength in msgA-
DMRS-Configuration,
- if maxLength is not configured, single-symbol DM-RS can be scheduled for the UE by DCI or configured by
the configured grant configuration, and the UE can be configured with a number of additional DM-RS for
PUSCH by higher layer parameter dmrs-AdditionalPosition, which can be 'pos0', 'pos1', 'pos2', 'pos3'.
- if maxLength is configured, either single-symbol DM-RS or double symbol DM-RS can be scheduled for the
UE by DCI or configured by the configured grant configuration, and the UE can be configured with a number
of additional DM-RS for PUSCH by higher layer parameter dmrs-AdditionalPosition, which can be 'pos0' or
'pos1'.
- for msgA PUSCH for Type-2 random access procedure the UE can be configured with a number of
additional DM-RS for PUSCH by higher layer parameter msgA-DMRS-AdditionalPosition, which can be
'pos0', 'pos1', 'pos2', 'pos3' for single-symbol DM-RS or 'pos0', 'pos1' for double-symbol DM-RS.
- and, the UE shall transmit a number of additional DM-RS as specified in Table 6.4.1.1.3-3 and Table
6.4.1.1.3-4 in -Clause 6.4.1.1.3 of [4, TS 38.211].
If a UE transmitting PUSCH is configured with the higher layer parameter phaseTrackingRS in DMRS-UplinkConfig,
the UE may assume that the following configurations are not occurring simultaneously for the transmitted PUSCH
3GPP
Release 16 135 3GPP TS 38.214 V16.1.0 (2020-03)
- any DM-RS ports among 4-7 or 6-11 for DM-RS configurations type 1 and type 2, respectively are scheduled for
the UE and PT-RS is transmitted from the UE.
For PUSCH scheduled by DCI format 0_1, by activation DCI format 0_1 with CRC scrambled by CS-RNTI, or
configured by configured grant Type 1 configuration, the UE shall assume the DM-RS CDM groups indicated in Tables
7.3.1.1.2-6 to 7.3.1.1.2-23 of Clause 7.3.1.1 of [5, TS38.212] are not used for data transmission, where "1", "2" and "3"
for the number of DM-RS CDM group(s) correspond to CDM group 0, {0,1}, {0,1,2}, respectively.
For PUSCH scheduled by DCI format 0_0 or by activation DCI format 0_0 with CRC scrambled by CS-RNTI, the UE
shall assume the number of DM-RS CDM groups without data is 1 which corresponds to CDM group 0 for the case of
PUSCH with allocation duration of 2 or less OFDM symbols with transform precoding disabled, the UE shall assume
that the number of DM-RS CDM groups without data is 3 which corresponds to CDM group {0,1,2} for the case of
PUSCH scheduled by activation DCI format 0_0 and the dmrs-Type in cg-DMRS-Configuration equal to 'type2' and the
PUSCH allocation duration being more than 2 OFDM symbols, and the UE shall assume that the number of DM-RS
CDM groups without data is 2 which corresponds to CDM group {0,1} for all other cases.
For MsgA PUSCH transmission, if the UE is not configured with msgAPUSCHDMRSCDMgroup, the UE shall assume
that 2 DM-RS CDM groups are configured. Otherwise, msgAPUSCHDMRSCDMgroup indicates which DM-RS CDM
group to use from the set of {0,1}.
For MsgA PUSCH transmission, if the UE is not configured with msgAPUSCHNrOfPort, the UE shall assume that 4
ports are configured per DM-RS CDM groups. Otherwise, msgAPUSCHNrOfPort with value of 0 indicates the first port
per DM-RS CDM group, while a value of 1 indicates the first two ports per DM-RS CDM group.
For uplink DM-RS with PUSCH, the UE may assume the ratio of PUSCH EPRE to DM-RS EPRE (  DMRS [dB]) is
given by Table 6.2.2-1 according to the number of DM-RS CDM groups without data. The DM-RS scaling factor
 DMRS
−
 DMRS
PUSCH specified in clause 6.4.1.1.3 of [4, TS 38.211] is given by  DMRS
PUSCH
= 10 20
.
Table 6.2.2-1: The ratio of PUSCH EPRE to DM-RS EPRE
Number of DM-RS CDM DM-RS configuration type 1 DM-RS configuration type 2

groups without data
1 0 dB 0 dB
2 -3 dB -3 dB
3 - -4.77 dB
For PUSCH repetition Type B, the DM-RS transmission procedure is applied for each actual repetition separately based
on the allocation duration of the actual repetition. A UE is not expected to be indicated with an antenna port
configuration that is invalid for the allocated duration of any actual repetition.
6.2.3 UE PT-RS transmission procedure

If a UE is not configured with the higher layer parameter phaseTrackingRS in DMRS-UplinkConfig, the UE shall not
transmit PT-RS. The PTRS is only present on PUSCH scheduled by PDCCH with CRC scrambled by MCS-C-RNTI,
C-RNTI, CS-RNTI, SP-CSI-RNTI and on PUSCH corresponding to a configured grant. For PUSCH repetition Type B,
the PT-RS transmission procedure is applied for each actual repetition separately based on the allocation duration of the
actual repetition.
6.2.3.1 UE PT-RS transmission procedure when transform precoding is not enabled

When transform precoding is not enabled and if a UE is configured with the higher layer parameter phaseTrackingRS in
DMRS-UplinkConfig,
- the higher layer parameters timeDensity and frequencyDensity in PTRS-UplinkConfig indicate the threshold
values ptrs-MCSi, i=1,2,3 and NRB,i , i=0,1, as shown in Table 6.2.3.1-1 and Table 6.2.3.1-2, respectively.
- if either or both higher layer parameters timeDensity and/or frequencyDensity in PTRS-UplinkConfig are
configured, the UE shall assume the PT-RS antenna ports' presence and pattern are a function of the
corresponding scheduled MCS and scheduled bandwidth in a corresponding bandwidth part as shown in Table
6.2.3.1-1 and Table 6.2.3.1-2, respectively,
- if the higher layer parameter timeDensity is not configured, the UE shall assume LPT-RS = 1.
3GPP
Release 16 136 3GPP TS 38.214 V16.1.0 (2020-03)
- if the higher layer parameter frequencyDensity is not configured, the UE shall assume KPT-RS = 2.
- if none of the higher layer parameters timeDensity and frequencyDensity in PTRS-UplinkConfig are configured,
the UE shall assume LPT-RS = 1 and KPT-RS = 2.
Table 6.2.3.1-1: Time density of PT-RS as a function of scheduled MCS
Scheduled MCS Time density( L PT − RS )

IMCS < ptrs-MCS1 PT-RS is not present
Table 6.2.3.1-2: Frequency density of PT-RS as a function of scheduled bandwidth
Scheduled bandwidth Frequency density ( K PT − RS )

NRB < NRB0 PT-RS is not present
NRB0  NRB < NRB1 2
NRB1  NRB 4
The higher layer parameter PTRS-UplinkConfig provides the parameters ptrs-MCSi, i=1,2,3 and with values in 0-29
when MCS Table 5.1.3.1-1 is used and 0-28 when MCS Table 5.1.3.1-2 is used, respectively. ptrs-MCS4 is not
explicitly configured by higher layers but assumed 29 when MCS Table 5.1.3.1-1 is used and 28 when MCS Table
5.1.3.1-2 is used. The higher layer parameter PTRS-UplinkConfig provides the parameters NRBi i=0,1 with values in
range 1-276.
If the higher layer parameter PTRS-UplinkConfig indicates that the time density thresholds ptrs-MCSi = ptrs-MCSi+1,
then the time density LPTRS of the associated row where both these thresholds appear in Table 6.2.3.1-1 is disabled. If the
higher layer parameter frequencyDensity in PTRS-UplinkConfig indicates that the frequency density thresholds NRB,i =
NRB,i+1, then the frequency density KPTRS of the associated row where both these thresholds appear in Table 6.2.3.1-2 is
disabled.
If either or both of the parameters PT-RS time density (LPT-RS) and PT-RS frequency density (KPT-RS), shown in Table
6.2.3.1-1 and Table 6.2.3.1-2, indicates that are configured as 'PT-RS not present', the UE shall assume that PT-RS is
not present.
When a UE is scheduled to transmit PUSCH with allocation duration of 2 symbols or less, and if LPT-RS is set to 2 or 4,
the UE shall not transmit PT-RS. When a UE is scheduled to transmit PUSCH with allocation duration of 4 symbols or
less, and if LPT-RS is set to 4, the UE shall not transmit PT-RS.
When a UE is scheduled to transmit PUSCH for retransmission, if the UE is scheduled with IMCS > V, where V = 28 for
MCS Table 5.1.3.1-1 and MCS Table 5.1.3.1-3 and V = 27 for MCS Table 5.1.3.1-2, respectively, the MCS for PT-RS
time-density determination is obtained from the DCI for the same transport block in the initial transmission, which is
smaller than or equal to V.
The maximum number of configured PT-RS ports is given by the higher layer parameter maxNrofPorts in PTRS-
UplinkConfig. The UE is not expected to be configured with a larger number of UL PT-RS ports than it has reported
need for.
If a UE has reported the capability of supporting full-coherent UL transmission, the UE shall expect the number of UL
PT-RS ports to be configured as one if UL-PTRS is configured.
For codebook or non-codebook based UL transmission, the association between UL PT-RS port(s) and DM-RS port(s)
is signalled by PTRS-DMRS association field in DCI format 0_1. For a PUSCH corresponding to a configured grant
Type 1 transmission, the UE may assume the association between UL PT-RS port(s) and DM-RS port(s) defined by
value 0 in Table 7.3.1.1.2-25 or value "00" in Table 7.3.1.1.1.2-26 described in Clause 7.3.1 of [5, TS38.212].
For PUSCH scheduled by DCI format 0_0 or by activation DCI format 0_0, the UL PT-RS port is associated to DM-RS
port 0.
3GPP
Release 16 137 3GPP TS 38.214 V16.1.0 (2020-03)
For non-codebook based UL transmission, the actual number of UL PT-RS port(s) to transmit is determined based on
SRI(s) in DCI format 0_1 or higher layer parameter sri-ResourceIndicator in rrc-ConfiguredUplinkGrant. A UE is
configured with the PT-RS port index for each configured SRS resource by the higher layer parameter ptrs-PortIndex
configured by SRS-Config if the UE is configured with the higher layer parameter phaseTrackingRS in DMRS-
UplinkConfig. If the PT-RS port index associated with different SRIs are the same, the corresponding UL DM-RS ports
are associated to the one UL PT-RS port.
For partial-coherent and non-coherent codebook based UL transmission, the actual number of UL PT-RS port(s) is
determined based on TPMI and/or number of layers which are indicated by Precoding information and number of
layers field in DCI format 0_1 or configured by higher layer parameter precodingAndNnumberOfLayers:
- if the UE is configured with the higher layer parameter maxNrofPorts in PTRS-UplinkConfig set to 'n2', the
actual UL PT-RS port(s) and the associated transmission layer(s) are derived from indicated TPMI as:
- PUSCH antenna port 1000 and 1002 in indicated TPMI share PT-RS port 0, and PUSCH antenna port 1001 and
1003 in indicated TPMI share PT-RS port 1.
- UL PT-RS port 0 is associated with the UL layer [x] of layers which are transmitted with PUSCH antenna
port 1000 and PUSCH antenna port 1002 in indicated TPMI, and UL PT-RS port 1 is associated with the
UL layer [y] of layers which are transmitted with PUSCH antenna port 1001 and PUSCH antenna port
1003 in indicated TPMI, where [x] and/or [y] are given by DCI parameter PTRS-DMRS association as
shown in DCI format 0_1 described in Clause 7.3.1 of [5, TS38.212].
PUSCH
When the UE is scheduled with Qp={1,2} PT-RS port(s) in uplink and the number of scheduled layers is n layer ,
- If the UE is configured with higher layer parameter ptrs-Power, the PUSCH to PT-RS power ratio per layer per
RE  PTRS
PUSCH is given by
 PTRS
PUSCH
= − PTRS
PUSCH
dB , where  PTRS
PUSCH is shown in the Table 6.2.3.1-3 according to
the higher layer parameter ptrs-Power, the PT-RS scaling factor  PTRS specified in clause 6.4.1.2.2.1 of [4, TS
PUSCH

− PTRS
38.211] is given by  PTRS = 10 20
and also on the Precoding Information and Number of Layers field in
DCI.
- The UE shall assume ptrs-Power in PTRS-UplinkConfig is set to state "00" in Table 6.2.3.1-3 if not configured
or in case of non-codebook based PUSCH.
Table 6.2.3.1-3: Factor related to PUSCH to PT-RS power ratio per layer per RE  PTRS
PUSCH
PUSCH
The number of PUSCH layers ( nlayer )
UL- 1 2 3 4
PTRS- All Full Partial and Full Partial and Full Partial Non-
power / cases coherent noncoherent noncoherent coherent coherent
 PTRS
PUSCH coherent
and non-
coherent and
non-
and non-
codebook
codebook codebook based
based based
00 0 3 3Qp-3 4.77 3Qp-3 6 3Qp 3Qp-3
01 0 3 3 4.77 4.77 6 6 6
10 Reserved
11 Reserved
6.2.3.2 UE PT-RS transmission procedure when transform precoding is enabled

When transform precoding is enabled and if a UE is configured with the higher layer parameter
transformPrecoderEnabled in PTRS-UplinkConfig,
- the UE shall be configured with the higher layer parameters sampleDensity and the UE shall assume the PT-RS
antenna ports' presence and PT-RS group pattern are a function of the corresponding scheduled bandwidth in a
corresponding bandwidth part, as shown in Table 6.2.3.2-1. The UE shall assume no PT-RS is present when the
number of scheduled RBs is less than NRB0 if NRB0 > 1 or if the RNTI equals TC-RNTI.
3GPP
Release 16 138 3GPP TS 38.214 V16.1.0 (2020-03)
- and the UE may be configured PT-RS time density LPT-RS = 2 with the higher layer parameter
timeDensityTransformPrecoding. Otherwise, the UE shall assume LPT-RS = 1.
- if the higher layer parameter sampleDensity indicates that the sample density thresholds NRB,i = NRB,i+1, then the
associated row where both these thresholds appear in Table 6.2.3.2-1 is disabled.
Table 6.2.3.2-1: PT-RS group pattern as a function of scheduled bandwidth
Number of samples
Scheduled bandwidth Number of PT-RS groups
per PT-RS group
NRB0  NRB < NRB1 2 2
NRB4  NRB 8 4
When transform precoding is enabled and if a UE is configured with the higher layer parameter
transformPrecoderEnabled in PTRS-UplinkConfig, the PT-RS scaling factor β' specified in Clause 6.4.1.2.2.2 of [4, TS
38.211] is determined by the scheduled modulation order as shown in table 6.2.3.2-2.
Table 6.2.3.2-2: PT-RS scaling factor (β') when transform precoding enabled.
Scheduled modulation PT-RS scaling factor (β')

π/2-BPSK 1
QPSK 1
16QAM 3 5
64QAM 7 21
256QAM 15 85
6.3 UE PUSCH frequency hopping procedure

6.3.1 Frequency hopping for PUSCH repetition Type A
For PUSCH repetition Type A (as determined according to procedures defined in Clause 6.1.2.1 for scheduled PUSCH,
or Clause 6.1.2.3 for configured PUSCH), a UE is configured for frequency hopping by the higher layer parameter
frequencyHopping-ForDCIFormat0_2 in pusch-Config for PUSCH transmission scheduled by DCI format 0_2, and by
frequencyHopping provided in pusch-Config for PUSCH transmission scheduled by a DCI format other than 0_2, and
by frequencyHopping provided in configuredGrantConfig for configured PUSCH transmission. One of two frequency
hopping modes can be configured:
- Intra-slot frequency hopping, applicable to single slot and multi-slot PUSCH transmission.
- Inter-slot frequency hopping, applicable to multi-slot PUSCH transmission.
In case of resource allocation type 2, the UE transmits PUSCH without frequency hopping.
In case of resource allocation type 1, whether or not transform precoding is enabled for PUSCH transmission, the UE
may perform PUSCH frequency hopping, if the frequency hopping field in a corresponding detected DCI format or in a
random access response UL grant is set to 1, or if for a Type 1 PUSCH transmission with a configured grant the higher
layer parameter frequencyHoppingOffset is provided, otherwise no PUSCH frequency hopping is performed. When
frequency hopping is enabled for PUSCH, the RE mapping is defined in clause 6.3.1.6 of [4, TS 38.211].
For a PUSCH scheduled by RAR UL grant, fallbackRAR UL grant, or by DCI format 0_0 with CRC scrambled by TC-
RNTI, frequency offsets are obtained as described in clause 8.3 of [6, TS 38.213]. For a PUSCH scheduled by DCI
format 0_0/0_1 or a PUSCH based on a Type2 configured UL grant activated by DCI format 0_0/0_1 and for resource
allocation type 1, frequency offsets are configured by higher layer parameter frequencyHoppingOffsetLists in pusch-
Config. For a PUSCH scheduled by DCI format 0_2 or a PUSCH based on a Type2 configured UL grant activated by
3GPP
Release 16 139 3GPP TS 38.214 V16.1.0 (2020-03)
DCI format 0_2 and for resource allocation type 1, frequency offsets are configured by higher layer parameter
frequencyHoppingOffsetLists-ForDCIFormat0_2 in pusch-Config.
- When the size of the active BWP is less than 50 PRBs, one of two higher layer configured offsets is indicated in
the UL grant.
- When the size of the active BWP is equal to or greater than 50 PRBs, one of four higher layer configured offsets
is indicated in the UL grant.
For PUSCH based on a Type1 configured UL grant the frequency offset is provided by the higher layer parameter
frequencyHoppingOffset in rrc-ConfiguredUplinkGrant.
For a MsgA PUSCH the frequency offset is provided by the higher layer parameter as described in [6, TS 38.213 .
In case of intra-slot frequency hopping, the starting RB in each hop is given by:
 RBstart i=0
RBstart = 
( RBstart + RBoffset ) mod N BWP i = 1
size ,
where i=0 and i=1 are the first hop and the second hop respectively, and RB start is the starting RB within the UL BWP,
as calculated from the resource block assignment information of resource allocation type 1 (described in Clause 6.1.2.2.2)
and RB offset is the frequency offset in RBs between the two frequency hops. The number of symbols in the first hop is
 PUSCH,s
given by N symb  PUSCH,s
/ 2 , the number of symbols in the second hop is given by N symb − N symb 
PUSCH,s
 𝑃𝑈𝑆𝐶𝐻,𝑠
/ 2 , where 𝑁𝑠𝑦𝑚𝑏
is the length of the PUSCH transmission in OFDM symbols in one slot.
In case of inter-slot frequency hopping, the starting RB during slot ns is given by:
( ) 
RB start ns = 
RB start
(RB start + RB offset ) mod N BW
ns mod 2 = 0
 ,
P ns mod 2 = 1
size
where ns is the current slot number within a radio frame, where a multi-slot PUSCH transmission can take place,
RB start is the starting RB within the UL BWP, as calculated from the resource block assignment information of resource
allocation type 1 (described in Clause 6.1.2.2.2) and RB offset is the frequency offset in RBs between the two frequency
hops.
6.3.2 Frequency hopping for PUSCH repetition Type B

For PUSCH repetition Type B (as determined according to procedures defined in Clause 6.1.2.1 for scheduled PUSCH,
or Clause 6.1.2.3 for configured PUSCH), a UE is configured for frequency hopping by the higher layer parameter
frequencyHopping-ForDCIFormat0_2 in pusch-Config for PUSCH transmission scheduled by DCI format 0_2, by
frequencyHopping-ForDCIFormat0_1 provided in pusch-Config for PUSCH transmission scheduled by DCI format
0_1, and by frequencyHopping-PUSCHRepTypeB provided in rrc-ConfiguredUplinkGrant for Type 1 configured
PUSCH transmission. The frequency hopping mode for Type 2 configured PUSCH transmission follows the
configuration of the activating DCI format. One of two frequency hopping modes can be configured:
- Inter-repetition frequency hopping
- Inter-slot frequency hopping
In case of resource allocation type 1, whether or not transform precoding is enabled for PUSCH transmission, the UE
may perform PUSCH frequency hopping, if the frequency hopping field in a corresponding detected DCI format is set
to 1, or if for a Type 1 PUSCH transmission with a configured grant the higher layer parameter frequencyHopping-
PUSCHRepTypeB is provided, otherwise no PUSCH frequency hopping is performed. When frequency hopping is
enabled for PUSCH, the RE mapping is defined in clause 6.3.1.6 of [4, TS 38.211].
For a PUSCH scheduled by DCI format 0_1 or a PUSCH based on a Type 2 configured UL grant activated by DCI
format 0_1 and for resource allocation type 1, frequency offsets are configured by higher layer parameter
frequencyHoppingOffsetLists in pusch-Config. For a PUSCH scheduled by DCI format 0_2 or a PUSCH based on a
Type 2 configured UL grant activated by DCI format 0_2 and for resource allocation type 1, frequency offsets are
configured by higher layer parameter frequencyHoppingOffsetLists-ForDCIFormat0_2 in pusch-Config.
3GPP
Release 16 140 3GPP TS 38.214 V16.1.0 (2020-03)
- When the size of the active BWP is less than 50 PRBs, one of two higher layer configured offsets is indicated in
the UL grant.
- When the size of the active BWP is equal to or greater than 50 PRBs, one of four higher layer configured offsets
is indicated in the UL grant.
For PUSCH based on a Type1 configured UL grant the frequency offset is provided by the higher layer parameter
frequencyHoppingOffset in rrc-ConfiguredUplinkGrant.
In case of inter-repetition frequency hopping, the starting RB for an actual repetition within the n-th nominal repetition
(as defined in Clause 6.1.2.1) is given by:
where RBstart is the starting RB within the UL BWP, as calculated from the resource block assignment information of
resource allocation type 1 (described in Clause 6.1.2.2.2) and RBoffset is the frequency offset in RBs between the two
frequency hops.
In case of inter-slot frequency hopping, the starting RB during slot ns follows that of inter-slot frequency hopping for
PUSCH Repetition Type A in Clause 6.3.1.
6.4 UE PUSCH preparation procedure time

If the first uplink symbol in the PUSCH allocation for a transport block, including the DM-RS, as defined by the slot
offset K2 and the start and length indicator SLIV of the scheduling DCI and including the effect of the timing advance, is
no earlier than at symbol L2, where L2 is defined as the next uplink symbol with its CP starting
Tproc ,2 = max ((N 2 + d 2,1 )(2048 + 144)   2−   TC , d 2,2 ) after the end of the reception of the last symbol of the
PDCCH carrying the DCI scheduling the PUSCH, then the UE shall transmit the transport block.
- N2 is based on µ of Table 6.4-1 and Table 6.4-2 for UE processing capability 1 and 2 respectively, where µ
corresponds to the one of (µDL, µUL) resulting with the largest Tproc,2, where the µDL corresponds to the subcarrier
spacing of the downlink with which the PDCCH carrying the DCI scheduling the PUSCH was transmitted and
µUL corresponds to the subcarrier spacing of the uplink channel with which the PUSCH is to be transmitted, and
κ is defined in clause 4.1 of [4, TS 38.211].
- If the first symbol of the PUSCH allocation consists of DM-RS only, then d2,1 = 0, otherwise d2,1 = 1.
- If the UE is configured with multiple active component carriers, the first uplink symbol in the PUSCH allocation
further includes the effect of timing difference between component carriers as given in [11, TS 38.133].
- If the scheduling DCI triggered a switch of BWP, d2,2 equals to the switching time as defined in [11, TS 38.133],
otherwise d2,2=0.
- For a UE that supports capability 2 on a given cell, the processing time according to UE processing capability 2
is applied if the high layer parameter processingType2Enabled in PUSCH-ServingCellConfig is configured for
the cell and set to enable,
- If the PUSCH indicated by the DCI is overlapping with one or more PUCCH channels, then the transport block
is multiplexed following the procedure in clause 9.2.5 of [6, TS 38.213], otherwise the transport block is
transmitted on the PUSCH indicated by the DCI.
Otherwise the UE may ignore the scheduling DCI.
The value of T proc,2 is used both in the case of normal and extended cyclic prefix.
3GPP
Release 16 141 3GPP TS 38.214 V16.1.0 (2020-03)
Table 6.4-1: PUSCH preparation time for PUSCH timing capability 1
 PUSCH preparation time N2 [symbols]

0 10
1 12
2 23
3 36
Table 6.4-2: PUSCH preparation time for PUSCH timing capability 2
 PUSCH preparation time N2 [symbols]

0 5
1 5.5
2 11 for frequency range 1
7 UE procedures for transmitting and receiving on a

carrier with intra-cell guard bands
For operation with shared spectrum channel access, when the UE is configured with any of intraCellGuardBandUL-r16
for UL carrier and intraCellGuardBandDL-r16 for DL carrier, the UE is provided with 𝑁𝑅𝐵−𝑠𝑒𝑡 − 1 intra-cell guard
𝑠𝑡𝑎𝑟𝑡,𝜇 𝑒𝑛𝑑,𝜇
bands on a carrier, each defined by start and end CRB, 𝐺𝐵 𝑠 and 𝐺𝐵 𝑠 , respectively. The intra-cell guard bands
𝑠𝑡𝑎𝑟𝑡,𝜇 𝑒𝑛𝑑,𝜇
separate 𝑁𝑅𝐵−𝑠𝑒𝑡 RB-sets, each defined by start and end CRB, 𝑅𝐵 𝑠 and 𝑅𝐵 𝑠 , respectively. UE determines
𝑠𝑡𝑎𝑟𝑡,𝜇 start,𝜇 𝑒𝑛𝑑,𝜇 start,𝜇 size,𝜇 𝑒𝑛𝑑,𝜇
𝑅𝐵 0 = 𝑁grid , 𝑅𝐵𝑁𝑅𝐵−𝑠𝑒𝑡−1 = 𝑁grid + 𝑁grid , and the remaining start and end CRBs as 𝑅𝐵 𝑠 =
𝑠𝑡𝑎𝑟𝑡,𝜇 𝑠𝑡𝑎𝑟𝑡,𝜇 𝑒𝑛𝑑,𝜇
𝐺𝐵 𝑠 − 1 and 𝑅𝐵 𝑠+1 = 𝐺𝐵 𝑠 + 1. When the UE is not configured with intraCellGuardBandUL-r16, the UE
determines intra-cell guard band and corresponding RB-set according to the [default intra-cell GB pattern from 38.101
size,𝜇
corresponding to 𝜇 and carrier size 𝑁grid ]. When the UE is not configured with intraCellGuardBandDL-r16, the UE
determines intra-cell guard band and corresponding RB-set according to the [default intra-cell GB pattern from 38.101
size,𝜇
corresponding to 𝜇 and carrier size 𝑁grid ].
For a carrier with intra-carrier guard bands, the UE does not expect to receive a BWP configuration by BWP-Downlink
𝐵𝑊𝑃
or BWP-Uplink partially overlapping with a RB-set. RB-sets within BWP form a set 𝑆𝑅𝐵−𝑠𝑒𝑡𝑠 of cardinality 𝑁𝑅𝐵−𝑠𝑒𝑡 .
[The configuration of intraCellGuardBandDL-r16 and intraCellGuardBandUL-r16 can indicate to the UE that no intra-
cell guard-bands are configured.]
8 Physical sidelink shared channel related procedures

A UE can be configured by higher layers with one or more sidelink resource pools. A sidelink resource pool can be for
transmission of PSSCH, as described in Clause 8.1, or for reception of PSSCH, as described in Clause 8.3 and can be
associated with either sidelink resource allocation mode 1 or sidelink resource allocation mode 2.
In the frequency domain, a sidelink resource pool consists of numSubchannel contiguous sub-channels. A sub-channel
consists of subchannelsize contiguous PRBs, where numSubchannel and subchannelsize are higher layer parameters.
8.1 UE procedure for transmitting the physical sidelink shared

channel
Each PSSCH transmission is associated with an PSCCH transmission.
That PSCCH transmission carries the 1st stage of the SCI associated with the PSSCH transmission; the 2 nd stage of the
associated SCI is carried within the resource of the PSSCH.
If the UE transmits SCI format 0-1 on PSCCH according to a PSCCH resource configuration in slot n and PSCCH
resource m, then for the associated PSSCH transmission in the same slot
3GPP
Release 16 142 3GPP TS 38.214 V16.1.0 (2020-03)
- one transport block is transmitted with up to two layers;
- The number of layers (ʋ) is determined according to the "Number of DMRS port" field in the SCI
- The set of consecutive symbols within the slot for transmission of the PSSCH is determined according to clause
8.1.2.1;
- The set of contiguous resource blocks for transmission of the PSSCH is determined according to clause 8.1.2.2;
Transform precoding is not supported for PSSCH transmission.
Only wideband precoding is supported for PSSCH transmission.
The DM-RS antenna ports in Clause 8.4.1.1.1 of [4, TS38.211] are determined according to the ordering of
DM-RS port(s) given by Tables 8.3.1.1-1 in Clause 8.3.1.1 of [5, TS 38.212].
The UE shall set the contents of the SCI format 0_2 as follows:
- the UE shall determine "Zone ID" field as indicated by higher layers.
- the UE shall set the "Communication range requirement" field as indicated by higher layers.

Only one transmission scheme is defined for the PSSCH and is used for all PSSCH transmissions.
PSSCH transmission is performed with up to two antenna ports, with antenna ports 1000-1001 as defined in clause 8.2.4
of [4, TS 38.211].

In sidelink resource allocation mode 1:
- for PSSCH and PSCCH transmission, dynamic grant, configured grant type 1 and configured grant type 2 are
supported.

The UE shall transmit the PSSCH in the same slot as the associated PSCCH.
The minimum resource allocation unit in the time domain is a slot.
The UE shall transmit the PSSCH in consecutive symbols within the slot, subject to the following restrictions:
- The UE shall not transmit PSSCH in symbols which are not configured for sidelink. A symbol is configured for
sidelink, according to higher layer parameters startSLsymbols and lengthSLsymbols, where startSLsymbols is the
symbol index of the first symbol of lengthSLsymbols consecutive symbols configured for sidelink.
- Within the slot, PSSCH resource allocation starts at symbol startSLsymbols+1.
- The UE shall not transmit PSSCH in symbols which are configured for use by PSFCH, if PSFCH is configured
in this slot.
- The UE shall not transmit PSSCH in the last symbol configured for sidelink.
- The UE shall not transmit PSSCH in the symbol immediately preceding the symbols which are configured for
use by PSFCH, if PSFCH is configured in this slot.
In sidelink resource allocation mode 1:
- For sidelink dynamic grant, the PSSCH transmission is scheduled by a DCI format 3_0.
- For sidelink configured grant type 2, the configured grant is activated by a DCI format 3_0.
- For sidelink dynamic grant and sidelink configured grant type 2:
3GPP
Release 16 143 3GPP TS 38.214 V16.1.0 (2020-03)
- The "Time gap" field value m of the DCI format 3_0 provides an index m + 1 into a slot offset table. That
table is given by higher layer parameter timeGapFirstSidelinkTransmission and the table value at index m + 1
will be referred to as slot offset 𝐾𝑆𝐿 .
- The slot of the first sidelink transmission scheduled by the DCI is the first SL slot of the corresponding
𝑇
resource pool that starts not earlier than 𝑇DL − TA + 𝐾𝑆𝐿 × 𝑇slot where 𝑇DL is starting time of the downlink
2
slot carrying the corresponding DCI, 𝑇TA is the timing advance value and 𝐾𝑆𝐿 is the slot offset between the
slot DCI and the first sidelink transmission scheduled by DCI, 𝑇c is as defined in 38.211, and 𝑇slot t is the SL
slot duration.
- For sidelink configured grant type 1:
- The slot of the first sidelink transmissions follows the higher layer configuration according to [10, TS
38.321].

The resource allocation unit in the frequency domain is the sub-channel.
The sub-channel assignment for sidelink transmission is determined using the "Frequency resource assignment" field in
the associated SCI.
The lowest sub-channel for sidelink transmission is the sub-channel on which the lowest PRB of the associated PSCCH
is transmitted.
If a PSSCH scheduled by a PSCCH would overlap with resources containing the PSCCH, the resources corresponding
to a union of the PSCCH that scheduled the PSSCH and associated PSCCH DM-RS are not available for the PSSCH.
8.1.3 Modulation order, target code rate, redundancy version and

transport block size determination
IMCS is given by the "Modulation and coding scheme" field in SCI format 0-1.
The MCS table is determined as follows: one out of Table 5.1.3.1-1, Table 5.1.3.1-2, Table 5.1.3.1-3 according to
higher layer parameter mcs-Table-SL in resource pool configuration [ or field [TBD] in the SCI or higher layer
indication].
The UE shall use IMCS and the MCS table determined according to the previous step to determine the modulation order
(Qm) and Target code rate (R) used in the physical sidelink shared channel.

The UE shall first determine the number of REs (NRE) within the slot.
8.1.4 UE procedure for determining the subset of resources to be reported

to higher layers in PSSCH resource selection in sidelink resource
allocation mode 2
In resource allocation mode 2, the higher layer can request the UE to determine a subset of resources from which the
higher layer will select resources for PSSCH/PSCCH transmission. To trigger this procedure, in slot n, the higher layer
provides the following parameters for this PSSCH/PSCCH transmission:
- the resource pool from which the resources are to be reported;
- L1 priority, 𝑝𝑟𝑖𝑜𝑇𝑋 ;
- the remaining packet delay budget;
- the number of sub-channels to be used for the PSSCH/PSCCH transmission in a slot, 𝐿subCH ;
- optionally, the resource reservation interval, 𝑃rsvp_TX , in units of ms.
3GPP
Release 16 144 3GPP TS 38.214 V16.1.0 (2020-03)
The following higher layer parameters affect this procedure:
- t2min_SelectionWindow: internal parameter 𝑇2𝑚𝑖𝑛 is set to the corresponding value from higher layer parameter
t2min_SelectionWindow for the given value of 𝑝𝑟𝑖𝑜𝑇𝑋 .
- SL-ThresRSRP_pi_pj: this higher layer parameter provides an RSRP threshold for each combination (𝑝𝑖 , 𝑝𝑗 ),
where 𝑝𝑖 is the value of the priority field in a received SCI format 0-1 and 𝑝j is the priority of the transmission of
the UE selecting resources; for a given invocation of this procedure, 𝑝j = 𝑝𝑟𝑖𝑜𝑇𝑋 .
- RSforSensing selects if the UE uses the PSSCH-RSRP or PSCCH-RSRP measurement, as defined in clause
8.4.2.1.
- reservationPeriodAllowed
- t0_SensingWindow: internal parameter 𝑇0 is defined as the number of slots corresponding to t0_SensingWindow

ms.
The resource reservation interval, 𝑃rsvp_TX , if provided, is converted from units of ms to units of logical slots, resulting in
′
𝑃rsvp_TX .
Notation:
(𝑡0𝑆𝐿 , 𝑡1𝑆𝐿 , 𝑡2𝑆𝐿 , . . . ) denotes the set of slots which can belong to a sidelink resource pool and is defined in [TBD].
The following steps are used:
1) A candidate single-slot resource for transmission 𝑅x,y is defined as a set of 𝐿subCH contiguous sub-channels with
sub-channel x+j in slot 𝑡𝑦𝑆𝐿 where 𝑗 = 0, . . . , 𝐿subCH − 1. The UE shall assume that any set of 𝐿subCH contiguous
sub-channels included in the corresponding resource pool within the time interval [𝑛 + 𝑇1 , 𝑛 + 𝑇2 ] correspond to
one candidate single-slot resource, where
- selection of 𝑇1 is up to UE implementation under 0 ≤ 𝑇1 ≤ 𝑇𝑝𝑟𝑜𝑐,1 , where 𝑇𝑝𝑟𝑜𝑐,1 is TBD;
- if 𝑇2𝑚𝑖𝑛 is shorter than the remaining packet delay budget (in slots) then 𝑇2 is up to UE implementation
subject to 𝑇2𝑚𝑖𝑛 ≤ 𝑇2 ≤ remaining packet budget (in slots); otherwise 𝑇2 is set to the remaining packet
delay budget (in slots).
The total number of candidate single-slot resources is denoted by 𝑀total .
2) The sensing window is defined by the range of slots [𝑛 – 𝑇0 , 𝑛– 𝑇𝑝𝑟𝑜𝑐,0 ) where 𝑇0 is defined above and 𝑇𝑝𝑟𝑜𝑐,1 is
TBD. The UE shall monitor slots which can belong to a sidelink resource pool within the sensing window except
for those in which its own transmissions occur. The UE shall perform the behaviour in the following steps based
on PSCCH decoded and RSRP measured in these slots.
3) The internal parameter 𝑇ℎ(𝑝𝑖 ) is set to the corresponding value from higher layer parameter SL-
ThresRSRP_pi_pj for 𝑝𝑗 equal to the given value of 𝑝𝑟𝑖𝑜𝑇𝑋 and each priority value 𝑝𝑖 .
4) The set 𝑆𝐴 is initialized to the set of all the candidate single-slot resources.
5) The UE shall exclude any candidate single-slot resource 𝑅x,y from the set 𝑆𝐴 if it meets all the following
conditions:
𝑆𝐿
- the UE has not monitored slot 𝑡𝑚 in Step 2.
- for any periodicity value allowed by the higher layer parameter reservationPeriodAllowed and a hypothetical
𝑆𝐿
SCI format 0-1 received in slot 𝑡𝑚 with "Resource reservation period" field set to that periodicity value and
indicating all subchannels of the resource pool in this slot, condition c in step 6 would be met.
6) The UE shall exclude any candidate single-slot resource 𝑅x,y from the set 𝑆𝐴 if it meets all the following
conditions:
𝑆𝐿
a) the UE receives an SCI format 0-1 in slot 𝑡𝑚 , and "Resource reservation period" field, if present, and
"Priority" field in the received SCI format 0-1 indicate the values 𝑃rsvp_RX and 𝑝𝑟𝑖𝑜𝑅𝑋 , respectively according
to Clause [TBD] in [6, TS 38.213];
3GPP
Release 16 145 3GPP TS 38.214 V16.1.0 (2020-03)
b) the RSRP measurement performed, according to clause 8.4.2.1 for the received SCI format 0-1, is higher than
𝑇ℎ(𝑝𝑟𝑖𝑜𝑅𝑋 );
𝑆𝐿
c) the SCI format received in slot 𝑡𝑚 or the same SCI format which, if and only if the "Resource reservation
𝑆𝐿
period" field is present in the received SCI format 0-1, is assumed to be received in slot(s) 𝑡𝑚+𝑞×𝑃 ′
𝑟𝑠𝑣𝑝_𝑅𝑋
determines according to clause [TBD] in [6, TS 38.213] the set of resource blocks and slots which overlaps
′
with 𝑅𝑥,𝑦+𝑗×𝑃𝑟𝑠𝑣𝑝_𝑇𝑋
′ for q=1, 2, …, Q and j=0, 1, …, 𝐶𝑟𝑒𝑠𝑒𝑙 − 1. Here, 𝑃𝑟𝑠𝑣𝑝_𝑅𝑋 is 𝑃rsvp_RX converted to units
𝑇𝑠𝑐𝑎𝑙
of logical slots, 𝑄 = ⌈ ⌉ if 𝑃𝑟𝑠𝑣𝑝_𝑅𝑋 < 𝑇𝑠𝑐𝑎𝑙 and 𝑛′ − 𝑚 ≤ 𝑃𝑟𝑠𝑣𝑝_𝑅𝑋 ′
, where 𝑡𝑛𝑆𝐿′ = 𝑛 if slot n belongs
𝑃𝑟𝑠𝑣𝑝_𝑅𝑋
to the set (𝑡0𝑆𝐿 , 𝑡1𝑆𝐿 , . . . , 𝑡𝑇𝑆𝐿𝑚𝑎𝑥 ), otherwise slot 𝑡𝑛𝑆𝐿′ is the first slot after slot n belonging to the set
(𝑡0𝑆𝐿 , 𝑡1𝑆𝐿 , . . . , 𝑡𝑇𝑆𝐿𝑚𝑎𝑥 ); otherwise 𝑄 = 1. 𝑇𝑠𝑐𝑎𝑙 is FFS.
7) If the number of candidate single-slot resources remaining in the set 𝑆𝐴 is smaller than 0.2 ⋅ 𝑀total , then 𝑇ℎ(𝑝𝑖 ) is
increased by 3 dB for each priority value 𝑇ℎ(𝑝𝑖 ) and the procedure continues with step 4.
The UE shall report set 𝑆𝐴 to higher layers.
8.1.5 UE procedure for determining slots and resource blocks for PSSCH
transmission associated with an SCI format 0-1
The set of slots and resource blocks for PSSCH transmission is determined by the resource used for the PSCCH
transmission containing the associated SCI format 0-1, and fields "Frequency resource assignment", "Time resource
assignment" of the associated SCI format 1 as described below.
[TBD]
8.1.6 Sidelink congestion control in sidelink resource allocation mode 2

If a UE is configured with higher layer parameter sl-CR-Limit and transmits PSSCH in slot n, the UE shall ensure the
following limits for any priority value k;
∑𝑖≥𝑘 𝐶𝑅(𝑖) ≤ 𝐶𝑅𝐿𝑖𝑚𝑖𝑡 (𝑘)
where 𝐶𝑅(𝑖) is the CR evaluated in slot n-N for the PSSCH transmissions with "Priority" field in the SCI set to i, and
𝐶𝑅𝐿𝑖𝑚𝑖𝑡 (𝑘) corresponds to the high layer parameter sl-CR-Limit that is associated with the priority value k and the CBR
range which includes the CBR measured in slot n-N, where N is the congestion control processing time.
The congestion control processing time N is based on µ of Table 8.1.6-1 and Table 8.1.6-2 for UE processing capability
1 and 2 respectively, where µ corresponds to the subcarrier spacing of the sidelink channel with which the PSSCH is to
be transmitted. A UE shall only apply a single processing time capability in sidelink congestion control.
Table 8.1.6-1: Congestion control processing time for processing timing capability 1
µ Congestion control processing time N [slots]

0 2
1 2
2 4
3 8
Table 8.1.6-2: Congestion control processing time for processing timing capability 2
µ Congestion control processing time N [slots]

0 2
1 4
2 8
3 16
[ It is up to UE implementation how to meet the above limits, including dropping the transmissions in slot n. ]
3GPP
Release 16 146 3GPP TS 38.214 V16.1.0 (2020-03)
8.2 UE procedure for transmitting sidelink reference signals

8.2.1 CSI-RS transmission procedure
A UE transmits sidelink CSI-RS within a unicast PSSCH transmission if the following conditions hold:
- CSI reporting is enabled by higher layer parameter [CSIsiReporting]; and
- the "CSI request" field in the corresponding SCI format 0-2 is set to 1.
The following parameters for CSI-RS transmission are configured via the higher layer parameter [TBD] for each CSI-
RS configuration:
- nrofPortsCSIRS-SL indicates the number of ports for SL CSI-RS.
- firstSymbolInTimeDomainCSIRS-SL indicates the first OFDM symbol in a PRB used for SL CSI-RS
- frequDomainAllocationCSIRS-SL indicates the frequency domain allocation for SL CSI-RS.

𝑃𝑆𝑆𝐶𝐻
When the UE is configured with Qp={1,2} CSI-RS port(s) in sidelink and the number of scheduled layers is 𝑛𝑙𝑎𝑦𝑒𝑟 ,
PSSCH
- The CSI-RS scaling factor 𝛽CSIRS specified in clause 8.4.1.5.3 of [4, TS 38.211] is given by 𝛽CSIRS = 𝛽DM−RS ∙
𝑃𝑆𝑆𝐶𝐻
𝑛𝑙𝑎𝑦𝑒𝑟
√ PSSCH
where 𝛽DM−RS is the scaling factor for the corresponding PSSCH specified in clause 8.3.1.5 of [4, TS
𝑄𝑝
38.211].
8.2.2 PSSCH DM-RS transmission procedure

The UE selects the DM-RS time domain pattern out of the patterns configured using the higher layer parameter
TimePatternPsschDmrs for the resource pool on which the PSSCH is to be transmitted. If more than one DM-RS time
domain pattern is configured, the selected pattern is indicated by the "DMRS pattern" field in the SCI format 0-1
associated with the PSSCH transmission.
[ If PSSCH DMRS and PSCCH are mapped to the same OFDM symbol, then this mapping within a single sub-channel
is only supported if higher layer parameter subchannelsize >= 20, i.e. the sub-channel size is at least 20 PRBs. ]
8.2.3 PT-RS transmission procedure

Transmission of PT-RS is only supported in FR2.
The UE PT-RS transmission procedure specified in clause 6.2.3.1 applies for derivation of the PT-RS parameters LPT-RS
and, KPT-RS and for determination of PT-RS presence, with the following changes:
- timeDensity and frequencyDensity in PTRS-UplinkConfig are replaced by timeDensity-SL and

frequencyDensity-SL respectively;
- the number of antenna ports is the same as the number of DMRS antenna ports and the association between a
PT-RS antenna port and a DMRS antenna port is fixed.
8.3 UE procedure for receiving the physical sidelink shared

channel
For sidelink resource allocation mode 1, a UE upon detection of SCI format 0-1 on PSCCH can decode PSSCH
according to the detected SCI format 0-2, and associated PSSCH resource configuration configured by higher layers.
For sidelink resource allocation mode 2, a UE upon detection of SCI format 0-1 on PSCCH can decode PSSCH
according to the detected SCI format 0-2, and associated PSSCH resource configuration configured by higher layers.
3GPP
Release 16 147 3GPP TS 38.214 V16.1.0 (2020-03)
8.4 UE procedure for receiving reference signals

8.4.1 CSI-RS reception procedure
The CSI-RS defined in Clause 8.4.1.5 of [4, TS 38.211] may be used for CSI computation.
8.4.2 DM-RS reception procedure for RSRP computation

8.4.2.1 RSRP for resource selection in sidelink resource allocation mode 2
In sidelink resource allocation mode 2, the UE measures RSRP for resource selection as follows:
- PSSCH-RSRP over the DM-RS resource elements for the PSCCH carrying the received SCI format 0-1 if higher
layer parameter RSforSensing is set to "PSSCH DM RS", and
- PSCCH-RSRP over the DM-RS resource elements for the PSSCH according to the received SCI format 0-1 if
higher layer parameter RSforSensing is set to "PSCCH DM RS".
8.4.3 PT-RS reception procedure

Reception of PT-RS is only supported in FR2.
The UE PT-RS reception procedure specified in clause 5.1.6.3 applies for derivation of the PT-RS parameters LPT-RS and
KPT-RS and for determination of PT-RS presence, with the following changes:
- timeDensity and frequencyDensity in PTRS-DownlinkConfig are replaced by timeDensity-SL and

frequencyDensity-SL in [TBD] respectively, and [TBD] is (pre)configured per resource pool;
- the number of antenna ports is the same as the number of PSSCH DMRS antenna ports and the association
between a PT-RS antenna port and a PSSCH DMRS antenna port is fixed.
8.5 UE procedure for reporting channel state information (CSI)

8.5.1 Channel state information framework
CSI consists of Channel Quality Indicator (CQI) and Rank Indicator (RI). The CQI and RI are always reported together.
8.5.1.1 Reporting configurations

The UE shall calculate CSI parameters (if reported) assuming the following dependencies between CSI parameters (if
reported)
- CQI shall be calculated conditioned on the reported RI
The CSI reporting can be aperiodic (using [10, TS 38.321]). Table 8.5.1.1-1 shows the supported combinations of CSI
reporting configurations and CSI-RS configurations and how the CSI reporting is triggered for CSI-RS configuration.
Aperiodic CSI-RS is configured and triggered/activated as described in Clause 8.5.1.2.
Table 8.5.1.1-1 Triggering/Activation of CSI reporting for the possible CSI-RS Configurations.
CSI-RS Configuration Aperiodic CSI Reporting

For CSI reporting, Aperiodic CSI-RS Triggered by SCI. wideband CQI reporting is
supported. A wideband CQI is reported [for each
codeword] for the entire CSI reporting band.
8.5.1.2 Triggering of CSI reports

An aperiodic CSI report is triggered by an SCI format 0-2 with the "CSI request" field set to 1.
3GPP
Release 16 148 3GPP TS 38.214 V16.1.0 (2020-03)
8.5.2 Channel state information

8.5.2.1 CSI reporting quantities
8.5.2.1.1 Channel quality indicator (CQI)
The UE shall derive CQI as specified in clause 5.2.2.1, with the following changes
- PDSCH replaced by PSSCH
- uplink slot replaced by sidelink slot
- downlink physical resource blocks replaced by sidelink physical resource blocks
- Transport Block Size determination according to Clause 8.1.3.2
- CSI reference resource according to TODO
- interference measurements are not supported
- sub-band differential CQI is not supported
8.5.2.2 Reference signal (CSI-RS)

The UE can be configured with one CSI-RS pattern as indicated by the higher layer parameters TBD.
Parameters for which the UE shall assume non-zero transmission power for CSI-RS are configured according to clause
8.2.1.
8.5.2.3 CSI reference resource definition

TBD
8.5.3 CSI reporting

CSI reporting is aperiodic and is described in [10, TS 38.321].
3GPP
Release 16 149 3GPP TS 38.214 V16.1.0 (2020-03)
Annex A (informative):
Change history
3GPP
Release 16 150 3GPP TS 38.214 V16.1.0 (2020-03)
Change history
New
Date Meeting TDoc CR Rev Cat Subject/Comment
version
2017-05 RAN1#89 R1-1708892 - - - Draft skeleton 0.0.0
2017-07 AH_1706 R1-1712016 Inclusion of agreements up to and including RAN1#AH2 0.0.1
2017-08 RAN1#90 R1-1714596 Updated editor's version 0.0.3
2017-08 RAN1#90 R1-1715077 Endorsed version by RAN1#90 0.1.0
2017-08 RAN1#90 R1-1715324 Inclusion of agreements up to and including RAN1#90 0.1.1
2017-09 RAN#77 RP-172001 For information to plenary 1.0.0
bis
2017-10 RAN1#90 R1-1718819 Endorsed version by RAN1#90bis 1.1.0
bis
2017-10 RAN1#90 R1-1719227 Inclusion of agreements up to and including RAN1#90bis 1.1.1
bis
bis
bis
2017-11 RAN1#90 R1-1721051 Endorsed version 1.2.0
bis
2017-12 RAN1#91 R1-1721344 Inclusion of agreements up to and including RAN1#91 1.3.0
2017-12 RAN#78 RP-172416 Endorsed version for approval by plenary 2.0.0
2017-12 RAN#78 Approved by plenary – Rel-15 spec under change control 15.0.0
2018-03 RAN#79 RP-180200 0001 F CR capturing the Jan18 ad-hoc and RAN1#92 meeting agreements 15.1.0
2018-06 RAN#80 RP-181172 0002 1 F CR to 38.214 capturing the RAN1#92bis and RAN1#93 meeting 15.2.0
agreements
2018-06 RAN#80 RP-181257 0003 - B CR to 38.214 capturing the RAN1#92bis and RAN1#93 meeting 15.2.0
agreements related to URLLC
2018-06 RAN#80 RP-181172 0004 - F CR to 38.214: maintenance according to agreed Rel 15 features 15.2.0
2018-09 RAN#81 RP-181789 0005 - F CR to 38.214 capturing the RAN1#94 meeting agreements 15.3.0
2018-12 RAN#82 RP-182523 0006 2 F Combined CR of all essential corrections to 38.214 from 15.4.0
RAN1#94bis and RAN1#95
2019-03 RAN#83 RP-190632 0007 3 F Correction to aperiodic CSI-RS triggering with different numerology 15.5.0
between PDCCH and CSI-RS
2019-03 RAN#83 RP-190450 0009 - F Correction on CSI-RS configuration in 38.214 15.5.0
2019-03 RAN#83 RP-190450 0010 - F Correction on uplink resource allocation type 1 15.5.0
2019-03 RAN#83 RP-190450 0011 - F Correction on determination of the resource allocation table for 15.5.0
PUSCH with SP CSI
2019-03 RAN#83 RP-190450 0012 - F Correction on PUSCH resource allocation 15.5.0
2019-03 RAN#83 RP-190450 0013 - F Change Request for alignment of frequency domain resource 15.5.0
allocation with 38.213 for a PUSCH transmission scheduled by a
RAR UL grant
2019-03 RAN#83 RP-190450 0014 - F CR on sequential PDSCH and PUSCH scheduling 15.5.0
2019-03 RAN#83 RP-190450 0015 - F CR on out of HARQ order with multiple PDSCHs within one slot 15.5.0
2019-03 RAN#83 RP-190450 0016 - F Correction to LBRM restriction 15.5.0
2019-03 RAN#83 RP-190450 0017 - F CR on PDSCH beam indication 15.5.0
2019-03 RAN#83 RP-190450 0018 - F Correction on TCI indication for multi-slot PDSCH 15.5.0
2019-03 RAN#83 RP-190450 0019 - F Clarifications on CSI reporting on PUSCH 15.5.0
2019-03 RAN#83 RP-190450 0020 - F QCL properties of Msg4 in CONNECTED Mode 15.5.0
2019-03 RAN#83 RP-190450 0022 1 F CR on dynamic grant overriding configured grant 15.5.0
2019-03 RAN#83 RP-190450 0023 - F Correction on PUSCH with configured grant 15.5.0
2019-03 RAN#83 RP-190450 0024 - F Corrections to 38.214 15.5.0
2019-03 RAN#83 RP-190425 0025 1 F CR on QCL assumption for receiving PDSCH for RAR 15.5.0
2019-06 RAN#84 RP-191552 0035 - F Removal of "Correction to aperiodic CSI-RS triggering with different 15.6.0
numerology between PDCCH and CSI-RS"
2019-06 RAN#84 RP-191284 0026 - F Corrections on non-codebook based UL transmission to TS 38.214 15.6.0
2019-06 RAN#84 RP-191284 0027 - F CR on UE procedure for PDSCH and PUSCH 15.6.0
2019-06 RAN#84 RP-191284 0028 - F Correction on configured scheduling PUSCH repetition with dynamic 15.6.0
SFI
2019-06 RAN#84 RP-191284 0029 - F CR on rate matching for PDSCH scheduled by DCI format 1_0 15.6.0
2019-06 RAN#84 RP-191284 0030 - F Clarification on CG transmission opportunities 15.6.0
2019-06 RAN#84 RP-191284 0031 5 F Corrections to 38.214 including alignment of terminology across 15.6.0
specifications
2019-06 RAN#84 RP-191284 0032 - F CR to 38.214 clarifying calculation of DataRate and DataRateCC 15.6.0
2019-06 RAN#84 RP-191284 0033 - F Correction on PUSCH retransmission for a serving cell configured 15.6.0
with two uplinks
3GPP
Release 16 151 3GPP TS 38.214 V16.1.0 (2020-03)
2019-06 RAN#84 RP-191284 0034 - F Corrections to 38.214 regarding the MAC CE activation/deactivation 15.6.0
timing in mixed numerology scenario
2019-09 RAN#85 RP-191943 0037 - F Correction on UE receiving PDSCH procedure in FR2 15.7.0
2019-09 RAN#85 RP-191943 0038 - F Correction on slot aggregation 15.7.0
2019-09 RAN#85 RP-191943 0039 - F CR on grant-based PDSCH overlapping with SPS PDSCH 15.7.0
2019-09 RAN#85 RP-191943 0040 - F Correction on the resource mapping of PDSCH in TS 38.214 15.7.0
2019-09 RAN#85 RP-191943 0041 1 F Corrections to 38.214 including alignment of terminology across 15.7.0
specifications in RAN1#98
2019-09 RAN#85 RP-191943 0042 - F Clarification of PUSCH with SP-CSI overlapping with PUSCH with 15.7.0
data
2019-12 RAN#86 RP-192627 0045 - F Correction on resource allocation for uplink transmission with 15.8.0
configured grant Type 1
2019-12 RAN#86 RP-192627 0046 - F Clarification to the dynamically scheduled PDSCH collision with 15.8.0
SPS-PDSCH
2019-12 RAN#86 RP-192627 0047 - F Correction on rate-matching for LTE-CRS-toMatchAround 15.8.0
2019-12 RAN#86 RP-192627 0048 - F Correction on timing for MAC CE applicability in 38.214 15.8.0
2019-12 RAN#86 RP-192627 0049 - F Corrections to 38.214 including alignment of terminology across 15.8.0
specifications in RAN1#98bis and RAN1#99
2019-12 RAN#86 RP-192634 0043 1 B Introduction of UE behaviour for SRS measurements for CLI 16.0.0
2019-12 RAN#86 RP-192635 0050 - B Introduction of two-step RACH 16.0.0
2019-12 RAN#86 RP-192636 0051 - B Introduction of NR - U 16.0.0
2019-12 RAN#86 RP-192637 0052 - B Introduction of integrated access and backhaul for NR 16.0.0
2019-12 RAN#86 RP-192638 0053 - B Introduction of NR V2X 16.0.0
2019-12 RAN#86 RP-192639 0054 - B Introduction of NR URLLC support 16.0.0
2019-12 RAN#86 RP-192641 0055 - B Introduction of NR enhanced MIMO 16.0.0
2019-12 RAN#86 RP-192642 0056 - B Introduction of cross-slot scheduling restriction 16.0.0
2019-12 RAN#86 RP-192643 0057 - B Introduction of NR positioning support 16.0.0
2019-12 RAN#86 RP-192645 0058 - B Introduction of Cross-carrier Scheduling with Different Numerologies 16.0.0
2019-12 RAN#86 RP-192646 0059 - B Introduction of multiple LTE CRS rate matching patterns 16.0.0
2019-12 RAN#86 RP-192646 0060 - B Aperiodic CSI-RS Triggering for UE reporting beamSwitchTiming 16.0.0
values of 224 and 336
2019-12 RAN#86 RP-192646 0061 - B Behaviour for triggered with a CSI report for non-active BWP 16.0.0
2019-12 RAN#86 RP-192646 0062 - B Introduction of downgraded configurations for SRS antenna 16.0.0
switching
2019-12 RAN#86 RP-192646 0063 - B Introduction of one-slot periodic TRS configuration for FR1 under a 16.0.0
certain condition
2019-12 RAN#86 RP-192640 0064 - B Introduction of Industrial IoT 16.0.0
2020-03 RAN#87-e RP-200185 0068 - F Corrections on NR - U 16.1.0
2020-03 RAN#87-e RP-200187 0069 - F Corrections on NR V2X 16.1.0
2020-03 RAN#87-e RP-200483 0070 1 F Corrections on Cross-carrier Scheduling with Different Numerologies 16.1.0
2020-03 RAN#87-e RP-200188 0071 - F Corrections on NR URLLC support 16.1.0
2020-03 RAN#87-e RP-200190 0072 - F Corrections on NR enhanced MIMO 16.1.0
2020-03 RAN#87-e RP-200189 0073 - F Corrections on Industrial IoT 16.1.0
2020-03 RAN#87-e RP-200191 0074 - F Corrections of cross-slot scheduling restriction and CSI/L1-RSRP 16.1.0
measurement outside active time
2020-03 RAN#87-e RP-200184 0075 - F Corrections on two-step RACH after RAN1#100-e 16.1.0
2020-03 RAN#87-e RP-200192 0076 - F Corrections of NR positioning support 16.1.0
2020-03 RAN#87-e RP-200448 0078 - A CR on UL PTRS density selection 16.1.0
3GPP

3GPP TS 38.214

Uploaded by

Copyright:

Available Formats

3GPP TS 38.214

Uploaded by

Document Information

Original Title

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

3GPP TS 38.214

Uploaded by

Copyright:

Available Formats

What is the purpose and scope of this document?

What is the purpose and scope of this document?

What topics are covered in this document?

What topics are covered in this document?

3GPP TS 38.214 V16.1.

3rd Generation Partnership Project;

3GPP support office address

No part may be reproduced except as authorized by written permission.

5.2.1.6 CSI processing criteria.......................................................................................................................... 59

8.1.1 Transmission schemes .............................................................................................................................. 142

Annex A (informative): Change history ..................................................................................................... 149

x the first digit:

1 presented to TSG for information;

2 presented to TSG for approval;

3 or greater indicates TSG approved document under change control.

[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications"

[2] 3GPP TS 38.201: " NR; Physical Layer – General Description"

[3] 3GPP TS 38.202: "NR; Services provided by the physical layer"

[4] 3GPP TS 38.211: "NR; Physical channels and modulation"

[5] 3GPP TS 38.212: "NR; Multiplexing and channel coding"

[6] 3GPP TS 38.213: "NR; Physical layer procedures for control"

[7] 3GPP TS 38.215: "NR; Physical layer measurements"

[14] 3GPP TS 38.423: "NG-RAN; Xn signalling transport"

3 Definitions, symbols and abbreviations

BWP Bandwidth part

SS-RSRP SS reference signal received power

4.1 Power allocation for downlink

Clause 5.1.6.2. The DM-RS scaling factor  PDSCH

Table 4.1-1: The ratio of PDSCH EPRE to DM-RS EPRE

Number of DM-RS CDM DM-RS configuration type 1 DM-RS configuration type 2

The number of PDSCH layers

5 Physical downlink shared channel related procedures

5.1.1 Transmission schemes

5.1.1.1 Transmission scheme 1

5.1.2 Resource allocation

Given the parameter values of the indexed row:

- The slot allocated for the PDSCH is Ks, where

- The reference point S0 for starting symbol S is defined as:

- if configured with ReferenceofSLIV-ForDCIFormat1_2, and when receiving PDSCH scheduled by DCI

SLIV = 14  (14 − L + 1) + (14 − 1 − S )

Table 5.1.2.1-1: Valid S and L combinations

PDSCH Normal cyclic prefix Extended cyclic prefix

Table 5.1.2.1-2: Applied redundancy version when pdsch-AggregationFactor is present

rvid indicated by the DCI rvid to be applied to nth transmission occasion

When the value indicated by RepNumR16 in PDSCH-TimeDomainResourceAllocation equals to two, the

5.1.2.1.1 Determination of the resource allocation table to be used for PDSCH

RNTI PDCCH SS/PBCH pdsch- pdsch-Config PDSCH time

pdsch-ConfigCommon pdsch-Config includes pdsch-Config includes PDSCH time domain

Row index dmrs-TypeA- PDSCH K0 S L

Row index dmrs-TypeA- PDSCH K0 S L

Table 5.1.2.1.1-4: Default PDSCH time domain resource allocation B

Row index dmrs-TypeA- PDSCH K0 S L

Table 5.1.2.1.1-5: Default PDSCH time domain resource allocation C

Row index dmrs-TypeA- PDSCH K0 S L

5.1.2.2 Resource allocation in frequency domain

5.1.2.2.1 Downlink resource allocation type 0

Table 5.1.2.2.1-1: Nominal RBG size P

Bandwidth Part Size Configuration 1 Configuration 2

- the size of last RBG is RBGlast