ETSI TS 138 213: 5G NR Physical Layer Procedures For Control (3GPP TS 38.213 Version 16.6.0 Release 16)

ETSI TS 138 213 V16.6.
0 (2021-08)
TECHNICAL SPECIFICATION
5G;
NR;
Physical layer procedures for control
(3GPP TS 38.213 version 16.6.0 Release 16)
3GPP TS 38.213 version 16.6.0 Release 16 1 ETSI TS 138 213 V16.6.0 (2021-08)
Reference
RTS/TSGR-0138213vg60
Keywords
5G
ETSI
650 Route des Lucioles

F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C

Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:

http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2021.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
GSM® and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
Intellectual Property Rights

Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology

In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
Contents
Intellectual Property Rights ................................................................................................................................2
Legal Notice .......................................................................................................................................................2
Modal verbs terminology....................................................................................................................................2
Foreword.............................................................................................................................................................5
1 Scope ........................................................................................................................................................6
2 References ................................................................................................................................................6
3 Definitions, symbols and abbreviations ...................................................................................................6
3.1 Definitions .......................................................................................................................................................... 6
3.2 Symbols .............................................................................................................................................................. 7
3.3 Abbreviations ..................................................................................................................................................... 7
4 Synchronization procedures .....................................................................................................................9
4.1 Cell search .......................................................................................................................................................... 9
4.2 Transmission timing adjustments ..................................................................................................................... 11
4.3 Timing for secondary cell activation / deactivation.......................................................................................... 12
5 Radio link monitoring ............................................................................................................................13
6 Link recovery procedures .......................................................................................................................14
7 Uplink Power control .............................................................................................................................16
7.1 Physical uplink shared channel ........................................................................................................................ 17
7.1.1 UE behaviour .............................................................................................................................................. 17
7.2 Physical uplink control channel........................................................................................................................ 24
7.2.1 UE behaviour .............................................................................................................................................. 24
7.3 Sounding reference signals ............................................................................................................................... 29
7.3.1 UE behaviour .............................................................................................................................................. 29
7.4 Physical random access channel ....................................................................................................................... 32
7.5 Prioritizations for transmission power reductions ............................................................................................ 33
7.6 Dual connectivity ............................................................................................................................................. 34
7.6.1 EN-DC ........................................................................................................................................................ 34
7.6.1A NE-DC ........................................................................................................................................................ 34
7.6.2 NR-DC ........................................................................................................................................................ 35
7.7 Power headroom report .................................................................................................................................... 37
7.7.1 Type 1 PH report ........................................................................................................................................ 38
7.7.2 Type 2 PH report ........................................................................................................................................ 39
7.7.3 Type 3 PH report ........................................................................................................................................ 39
8 Random access procedure ......................................................................................................................40
8.1 Random access preamble ................................................................................................................................. 40
8.1A PUSCH for Type-2 random access procedure .................................................................................................. 43
8.2 Random access response - Type-1 random access procedure .......................................................................... 45
8.2A Random access response - Type-2 random access procedure .......................................................................... 47
8.3 PUSCH scheduled by RAR UL grant............................................................................................................... 48
8.4 PDSCH with UE contention resolution identity ............................................................................................... 50
9 UE procedure for reporting control information ....................................................................................51
9.1 HARQ-ACK codebook determination ............................................................................................................. 55
9.1.1 CBG-based HARQ-ACK codebook determination .................................................................................... 56
9.1.2 Type-1 HARQ-ACK codebook determination ........................................................................................... 57
9.1.2.1 Type-1 HARQ-ACK codebook in physical uplink control channel ...................................................... 58
9.1.2.2 Type-1 HARQ-ACK codebook in physical uplink shared channel....................................................... 65
9.1.3.1 Type-2 HARQ-ACK codebook in physical uplink control channel ...................................................... 67
9.1.3.2 Type-2 HARQ-ACK codebook in physical uplink shared channel....................................................... 72
9.1.3.3 Type-2 HARQ-ACK codebook grouping and HARQ-ACK retransmission......................................... 73
ETSI
9.2 UCI reporting in physical uplink control channel ............................................................................................ 79

9.2.1 PUCCH Resource Sets................................................................................................................................ 79
9.2.2 PUCCH Formats for UCI transmission ...................................................................................................... 83
9.2.3 UE procedure for reporting HARQ-ACK ................................................................................................... 84
9.2.4 UE procedure for reporting SR ................................................................................................................... 87
9.2.5 UE procedure for reporting multiple UCI types ......................................................................................... 88
9.2.5.0 UE procedure for prioritization between SL HARQ-ACK information in a PUCCH and UCI in a
PUCCH ................................................................................................................................................. 93
9.2.5.1 UE procedure for multiplexing HARQ-ACK or CSI and SR in a PUCCH .......................................... 93
9.2.5.2 UE procedure for multiplexing HARQ-ACK/SR/CSI in a PUCCH ..................................................... 95
9.2.6 PUCCH repetition procedure ...................................................................................................................... 99
9.3 UCI reporting in physical uplink shared channel ........................................................................................... 100
10 UE procedure for receiving control information ..................................................................................104
10.1 UE procedure for determining physical downlink control channel assignment ............................................. 109
10.2 PDCCH validation for DL SPS and UL grant Type 2 .................................................................................... 121
10.2A PDCCH validation for SL configured grant Type 2 ....................................................................................... 123
10.3 PDCCH monitoring indication and dormancy/non-dormancy behaviour for SCells ..................................... 123
10.4 Search space set group switching ................................................................................................................... 126
10.5 HARQ-ACK information for PUSCH transmissions ..................................................................................... 127
11 UE-group common signalling ..............................................................................................................128
11.1 Slot configuration ........................................................................................................................................... 128
11.1.1 UE procedure for determining slot format ................................................................................................ 133
11.2 Interrupted transmission indication ................................................................................................................ 140
11.2A Cancellation indication ................................................................................................................................... 141
11.3 Group TPC commands for PUCCH/PUSCH ................................................................................................. 142
11.4 SRS switching ................................................................................................................................................ 143
12 Bandwidth part operation .....................................................................................................................143
13 UE procedure for monitoring Type0-PDCCH CSS sets ......................................................................146
14 Integrated access-backhaul operation ...................................................................................................157
15 Dual active protocol stack based handover ..........................................................................................161
16 UE procedures for sidelink ...................................................................................................................162
16.1 Synchronization procedures ........................................................................................................................... 162
16.2 Power control ................................................................................................................................................. 165
16.2.0 S-SS/PSBCH blocks ................................................................................................................................. 165
16.2.1 PSSCH ...................................................................................................................................................... 165
16.2.2 PSCCH...................................................................................................................................................... 166
16.2.3 PSFCH ...................................................................................................................................................... 167
16.2.4 Prioritization of transmissions/receptions ................................................................................................. 168
16.2.4.1 Simultaneous NR and E-UTRA transmission/reception ..................................................................... 168
16.2.4.2 Simultaneous PSFCH transmission/reception ..................................................................................... 169
16.2.4.3 Simultaneous SL and UL transmissions/receptions ............................................................................ 169
16.2.4.3.1 Prioritizations for sidelink and uplink transmissions/receptions ................................................... 169
16.3 UE procedure for reporting HARQ-ACK on sidelink .................................................................................... 171
16.3.1 UE procedure for receiving HARQ-ACK on sidelink .............................................................................. 172
16.4 UE procedure for transmitting PSCCH .......................................................................................................... 172
16.5 UE procedure for reporting HARQ-ACK on uplink ...................................................................................... 173
16.5.1 Type-1 HARQ-ACK codebook determination ......................................................................................... 175
16.5.1.1 Type-1 HARQ-ACK codebook in physical uplink control channel .................................................... 176
16.5.1.2 Type-1 HARQ-ACK codebook in physical uplink shared channel..................................................... 177
16.5.2 Type-2 HARQ-ACK codebook determination ......................................................................................... 178
16.5.2.1 Type-2 HARQ-ACK codebook in physical uplink control channel .................................................... 178
16.5.2.2 Type-2 HARQ-ACK codebook in physical uplink shared channel..................................................... 180
16.6 UE procedure for LTE sidelink transmission ................................................................................................. 181
16.7 Operation for in-device coexistence ............................................................................................................... 181
Annex A: Change history ....................................................................................................................182

History ............................................................................................................................................................189
ETSI
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.
ETSI
1 Scope
The present document specifies and establishes the characteristics of the physical layer procedures for control
operations in 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.214: "NR; Physical layer procedures for data"
[7] 3GPP TS 38.215: "NR; Physical layer measurements"
[8-1] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1
Standalone"
Standalone"
and Range 2 Interworking operation with other radios"
[9] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception"
[10] 3GPP TS 38.133: "NR; Requirements for support of radio resource management"
[11] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification"
[12] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification"
[13] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer
procedures"
[14] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access
Control (MAC) protocol specification"
[15] 3GPP TS 37.213: "Physical layer procedures for shared spectrum channel access"
[16] 3GPP TS 38.473: "F1 application protocol (F1AP)"
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in [1, TR 21.905] and the following apply. A
term defined in the present document takes precedence over the definition of the same term, if any, in [1, TR 21.905]. A
parameter referenced in italics is provided by higher layers.
ETSI
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 [1, TR 21.905].
BPRE Bits per resource element

BWP Bandwidth part
CB Code block
CBG Code block group
CBR Channel busy ratio
CCE Control channel element
CORESET Control resource set
CP Cyclic prefix
CRC Cyclic redundancy check
CSI Channel state information
CSS Common search space
DAI Downlink assignment index
DAPS Dual active protocol stack
DC Dual connectivity
DCI Downlink control information
DL Downlink
DL-SCH Downlink shared channel
EPRE Energy per resource element
EN-DC E-UTRA NR dual connectivity with MCG using E-UTRA and SCG using NR
FR1 Frequency range 1
FR2 Frequency range 2
GSCN Global synchronization channel number
HARQ-ACK Hybrid automatic repeat request acknowledgement
MCG Master cell group
MCS Modulation and coding scheme
NDI New Data Indicator
NE-DC E-UTRA NR dual connectivity with MCG using NR and SCG using E-UTRA
NR-DC NR NR dual connectivity
PBCH Physical broadcast channel
PCell Primary cell
PDCCH Physical downlink control channel
PDSCH Physical downlink shared channel
PRACH Physical random access channel
PRB Physical resource block
PRG Physical resource block group
PSCell Primary secondary cell
PSBCH Physical sidelink broadcast channel
PSCCH Physical sidelink control channel
PSFCH Physical sidelink feedback channel
PSS Primary synchronization signal
PSSCH Physical sidelink shared channel
PUCCH Physical uplink control channel
PUCCH-SCell PUCCH SCell
PUSCH Physical uplink shared channel
QCL Quasi co-location
RB Resource block
RE Resource element
RLM Radio link monitoring
RRM Radio resource management
RS Reference signal
RSRP Reference signal received power
ETSI
SCG Secondary cell group

SCI Sidelink control information
SCS Subcarrier spacing
SFCI Sidelink feedback control information
SFN System frame number
SL Sidelink
SLIV Start and length indicator value
SPS Semi-persistent scheduling
SR Scheduling request
SRI SRS resource indicator
SRS Sounding reference signal
SSS Secondary synchronization signal
TA Timing advance
TAG Timing advance group
TCI Transmission Configuration Indicator
UCI Uplink control information
UE User equipment
UL Uplink
UL-SCH Uplink shared channel
USS UE-specific search space
ETSI
4 Synchronization procedures
4.1 Cell search

Cell search is the procedure for a UE to acquire time and frequency synchronization with a cell and to detect the
physical layer Cell ID of the cell.
A UE receives the following synchronization signals (SS) in order to perform cell search: the primary synchronization
signal (PSS) and secondary synchronization signal (SSS) as defined in [4, TS 38.211].
A UE assumes that reception occasions of a physical broadcast channel (PBCH), PSS, and SSS are in consecutive
symbols, as defined in [4, TS 38.211], and form a SS/PBCH block. The UE assumes that SSS, PBCH DM-RS, and
PBCH data have same EPRE. The UE may assume that the ratio of PSS EPRE to SSS EPRE in a SS/PBCH block is
either 0 dB or 3 dB. If the UE has not been provided dedicated higher layer parameters, the UE may assume that the
ratio of PDCCH DMRS EPRE to SSS EPRE is within -8 dB and 8 dB when the UE monitors PDCCHs for a DCI
format 1_0 with CRC scrambled by SI-RNTI, P-RNTI, or RA-RNTI.
For a half frame with SS/PBCH blocks, the first symbol indexes for candidate SS/PBCH blocks are determined
according to the SCS of SS/PBCH blocks as follows, where index 0 corresponds to the first symbol of the first slot in a
half-frame.
- Case A - 15 kHz SCS: the first symbols of the candidate SS/PBCH blocks have indexes of {2, 8} +14 ⋅ n .
- For operation without shared spectrum channel access:
- For carrier frequencies smaller than or equal to 3 GHz, n = 0, 1.
- For carrier frequencies within FR1 larger than 3 GHz, n = 0, 1, 2, 3 .
- For operation with shared spectrum channel access, as described in [15, TS 37.213], = 0, 1, 2, 3, 4.
- Case B - 30 kHz SCS: the first symbols of the candidate SS/PBCH blocks have indexes {4, 8, 16, 20} + 28 ⋅ n . For
carrier frequencies smaller than or equal to 3 GHz, n = 0 . For carrier frequencies within FR1 larger than 3 GHz,
n = 0, 1.
- Case C - 30 kHz SCS: the first symbols of the candidate SS/PBCH blocks have indexes {2, 8} +14 ⋅ n .
- For operation without shared spectrum channel access
- For paired spectrum operation
- For carrier frequencies smaller than or equal to 3 GHz, n = 0, 1. For carrier frequencies within FR1
larger than 3 GHz, n = 0, 1, 2, 3 .
- For unpaired spectrum operation
- For carrier frequencies smaller than 1.88 GHz, n = 0, 1. For carrier frequencies within FR1 equal to or
larger than 1.88 GHz, n = 0, 1, 2, 3 .
- For operation with shared spectrum channel access, = 0, 1, 2, 3, 4, 5, 6, 7, 8, 9.

- Case D - 120 kHz SCS: the first symbols of the candidate SS/PBCH blocks have indexes {4, 8, 16, 20} + 28 ⋅ n .
For carrier frequencies within FR2, = 0, 1, 2, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, 18.
- Case E - 240 kHz SCS: the first symbols of the candidate SS/PBCH blocks have indexes
{8, 12, 16, 20, 32, 36, 40, 44} + 56 ⋅ n . For carrier frequencies within FR2, = 0, 1, 2, 3, 5, 6, 7, 8.
From the above cases, if the SCS of SS/PBCH blocks is not provided by ssbSubcarrierSpacing, the applicable cases for
a cell depend on a respective frequency band, as provided in [8-1, TS 38.101-1] and [8-2, TS 38.101-2]. A same case
applies for all SS/PBCH blocks on the cell. If a 30 kHz SS/PBCH block SCS is indicated by ssbSubcarrierSpacing,
ETSI
Case B applies for frequency bands with only 15 kHz SS/PBCH block SCS as specified in [8-1, TS 38.101-1], and the
case specified for 30 kHz SS/PBCH block SCS in [8-1, TS 38.101-1] applies for frequency bands with 30 kHz
SS/PBCH block SCS or both 15 kHz and 30 kHz SS/PBCH block SCS as specified in [8-1, TS 38.101-1]. For a UE
configured to operate with carrier aggregation over a set of cells in a frequency band of FR2 or with frequency-
contiguous carrier aggregation over a set of cells in a frequency band of FR1, if the UE is provided SCS values by
ssbSubcarrierSpacing for receptions of SS/PBCH blocks on any cells from the set of cells, the UE expects the SCS
values to be same.
The candidate SS/PBCH blocks in a half frame are indexed in an ascending order in time from 0 to ௠௔௫ − 1, where
݉ܽ‫ ݔ‬is determined according to SS/PBCH block patterns for Cases A through E. ݉ܽ‫ ݔ‬is a maximum number of
SS/PBCH block indexes in a cell, and the maximum number of transmitted SS/PBCH blocks within a half frame is
௠௔௫ .
- For operation without shared spectrum channel access, ௠௔௫ = ௠௔௫
- For operation with shared spectrum channel access, ௠௔௫ = 8 for ௠௔௫ = 10 and 15 kHz SCS of SS/PBCH
blocks and for ௠௔௫ = 20 and 30 kHz SCS of SS/PBCH blocks
For ௠௔௫ = 4, a UE determines the 2 LSB bits of a candidate SS/PBCH block index per half frame from a one-to-one
mapping with an index of the DM-RS sequence transmitted in the PBCH as described in [4, TS 38.211].
For ௠௔௫ > 4, a UE determines the 3 LSB bits of a candidate SS/PBCH block index per half frame from a one-to-one
mapping with an index of the DM-RS sequence transmitted in the PBCH as described in [4, TS 38.211]
- for ௠௔௫ = 10, the UE determines the 1 MSB bit of the candidate SS/PBCH block index from PBCH payload
bit ̄ ஺ሜା଻ as described in [5, TS 38.212]
- for ௠௔௫ = 20, the UE determines the 2 MSB bits of the candidate SS/PBCH block index from PBCH payload
bits ̄஺ሜା଺ , ̄ ஺ሜା଻ as described in [5, TS 38.212]
- for ௠௔௫ = 64, the UE determines the 3 MSB bits of the candidate SS/PBCH block index from PBCH payload
bits ̄஺ሜାହ , ̄ ஺ሜା଺ , ̄ ஺ሜା଻ as described in [5, TS 38.212]
A UE can be provided per serving cell by ssb-periodicityServingCell a periodicity of the half frames for reception of the
SS/PBCH blocks for the serving cell. If the UE is not configured a periodicity of the half frames for receptions of the
SS/PBCH blocks, the UE assumes a periodicity of a half frame. A UE assumes that the periodicity is same for all
SS/PBCH blocks in the serving cell.
For initial cell selection, a UE may assume that half frames with SS/PBCH blocks occur with a periodicity of 2 frames.
For operation without shared spectrum channel access, an SS/PBCH block index is same as a candidate SS/PBCH block
index.
For operation with shared spectrum channel access, a UE assumes that transmission of SS/PBCH blocks in a half frame
is within a discovery burst transmission window that starts from the first symbol of the first slot in a half-frame. The UE
can be provided per serving cell by DiscoveryBurst-WindowLength a duration of the discovery burst transmission
window. If DiscoveryBurst-WindowLength is not provided, the UE assumes that the duration of the discovery burst
transmission window is a half frame. For a serving cell, the UE assumes that a periodicity of the discovery burst
transmission window is same as a periodicity of half frames for receptions of SS/PBCH blocks in the serving cell. The
UE assumes that one or more SS/PBCH blocks indicated by ssb-PositionsInBurst may be transmitted within the
discovery burst transmission window and have candidate SS/PBCH blocks indexes corresponding to SS/PBCH block
indexes provided by ssb-PositionsInBurst. If MSB , ≥ 1, of ssb-PositionsInBurst is set to 1, the UE assumes that
SS/PBCH block(s) within the discovery burst transmission window with candidate SS/PBCH block index(es)
corresponding to SS/PBCH block index equal to − 1 may be transmitted; if MSB is set to 0, the UE assumes that
the SS/PBCH block(s) are not transmitted.
For operation with shared spectrum channel access, a UE assumes that SS/PBCH blocks in a serving cell that are within
a same discovery burst transmission window or across discovery burst transmission windows are quasi co-located with
respect to average gain, quasi co-location 'typeA' and 'typeD' properties, when applicable [6, TS 38.214], if a value of
௉஻஼ு mod ொ஼௅ is same among the SS/PBCH blocks. ஽ெିோௌ
஽ெିோௌ ௉஻஼ு is an index of a DM-RS sequence transmitted in a
ௌௌ஻
ETSI
PBCH of a corresponding SS/PBCH block, and ௌௌ஻ ொ஼௅ is either provided by ssb-PositionQCL or, if ssb-PositionQCL is
not provided, obtained from a MIB provided by a SS/PBCH block according to Table 4.1-1 with ௌௌ஻ < 24 [4, TS
38.211]. subCarrierSpacingCommon indicates SCS of RMSI only for the case of operation without shared spectrum
௉஻஼ு mod ொ஼௅ , or according to
channel access. The UE can determine an SS/PBCH block index according to ஽ெିோௌ ௌௌ஻
̅ ொ஼௅ where ̅ is the candidate SS/PBCH block index. The UE assumes that within a discovery burst
mod ௌௌ஻
ܳ‫ܮܥ‬
transmission window, a number of transmitted SS/PBCH blocks on a serving cell is not larger than ܵܵ‫ ܤ‬and a number
of transmitted SS/PBCH blocks with a same SS/PBCH block index is not larger than one.
Table 4.1-1: Mapping between the combination of subCarrierSpacingCommon and LSB of ssb-
ࡽ࡯ࡸ
SubcarrierOffset to ࡿࡿ࡮
subCarrierSpacingCommon LSB of ssb-SubcarrierOffset ࡺࡽ࡯ࡸ

ࡿࡿ࡮
scs15or60 0 1
scs15or60 1 2
scs30or120 0 4
scs30or120 1 8
Upon detection of a SS/PBCH block, the UE determines from MIB that a CORESET for Type0-PDCCH CSS set, as
described in clause 13, is present if ௌௌ஻ < 24 [4, TS 38.211] for FR1 or if ௌௌ஻ < 12 for FR2. The UE determines
from MIB that a CORESET for Type0-PDCCH CSS set is not present if ௌௌ஻ > 23 for FR1 or if ௌௌ஻ > 11 for FR2;
the CORESET for Type0-PDCCH CSS set may be provided by PDCCH-ConfigCommon.
For a serving cell without transmission of SS/PBCH blocks, a UE acquires time and frequency synchronization with the
serving cell based on receptions of SS/PBCH blocks on the PCell, or on the PSCell, or on an SCell if applicable as
described in [10, TS 38.133], of the cell group for the serving cell.
4.2 Transmission timing adjustments

A UE can be provided a value N TA, offset of a timing advance offset for a serving cell by n-TimingAdvanceOffset for the
serving cell. If the UE is not provided n-TimingAdvanceOffset for a serving cell, the UE determines a default value
N TA, offset of the timing advance offset for the serving cell as described in [10, TS 38.133].
If a UE is configured with two UL carriers for a serving cell, a same timing advance offset value N TA, offset applies to
both carriers.
Upon reception of a timing advance command for a TAG, the UE adjusts uplink timing for PUSCH/SRS/PUCCH
transmission on all the serving cells in the TAG based on a value N TA, offset that the UE expects to be same for all the
serving cells in the TAG and based on the received timing advance command where the uplink timing for
PUSCH/SRS/PUCCH transmissions is the same for all the serving cells in the TAG.
For a band with synchronous contiguous intra-band EN-DC in a band combination with non-applicable maximum
transmit timing difference requirements as described in Note 1 of Table 7.5.3-1 of [10, TS 38.133], if the UE indicates
ul-TimingAlignmentEUTRA-NR as 'required' and uplink transmission timing based on timing adjustment indication for a
TAG from MCG and a TAG from SCG are determined to be different by the UE, the UE adjusts the transmission
timing for PUSCH/SRS/PUCCH transmission on all serving cells part of the band with the synchronous contiguous
intra-band EN-DC based on timing adjustment indication for a TAG from a serving cell in MCG in the band. The UE is
not expected to transmit a PUSCH/SRS/PUCCH in one CG when the PUSCH/SRS/PUCCH is overlapping in time,
even partially, with random access preamble transmitted in another CG.
For a SCS of 2 μ ⋅ 15 kHz, the timing advance command for a TAG indicates the change of the uplink timing relative to
the current uplink timing for the TAG in multiples of 16 ⋅ 64 ⋅ Tc 2 μ . The start timing of the random access preamble is
described in [4, TS 38.211].
A timing advance command [11, TS 38.321] in case of random access response or in an absolute timing advance
command MAC CE, T A , for a TAG indicates N TA values by index values of T A = 0, 1, 2, ..., 3846, where an amount
of the time alignment for the TAG with SCS of 2 μ ⋅15 kHz is N TA = TA ⋅ 16 ⋅ 64 2 μ . N TA is defined in [4, TS 38.211]
ETSI
and is relative to the SCS of the first uplink transmission from the UE after the reception of the random access response
or absolute timing advance command MAC CE.
In other cases, a timing advance command [11, TS 38.321], T A , for a TAG indicates adjustment of a current N TA
value, N TA_old , to the new N TA value, N TA_new , by index values of T A = 0, 1, 2,..., 63, where for a SCS of 2 μ ⋅15 kHz,
NTA_new = NTA_old + (TA − 31) ⋅16 ⋅ 64 2μ .
If a UE has multiple active UL BWPs, as described in clause 12, in a same TAG, including UL BWPs in two UL
carriers of a serving cell, the timing advance command value is relative to the largest SCS of the multiple active UL
BWPs. The applicable N TA_new value for an UL BWP with lower SCS may be rounded to align with the timing
advance granularity for the UL BWP with the lower SCS while satisfying the timing advance accuracy requirements in
[10, TS 38.133].
Adjustment of an N TA value by a positive or a negative amount indicates advancing or delaying the uplink
transmission timing for the TAG by a corresponding amount, respectively.
For a timing advance command received on uplink slot n and for a transmission other than a PUSCH scheduled by a
RAR UL grant or a fallbackRAR UL grant as described in clause 8.2A or 8.3, or a PUCCH with HARQ-ACK
information in response to a successRAR as described in clause 8.2A, the corresponding adjustment of the uplink
transmission timing applies from the beginning of uplink slot n + k + 1 where
k = Nslot
subframe,μ
⋅ (NT,1 + NT,2 + NTA,max + 0.5) Tsf  , N T,1 is a time duration in msec of N 1 symbols corresponding to a
PDSCH processing time for UE processing capability 1 when additional PDSCH DM-RS is configured, N T,2 is a time
duration in msec of N 2 symbols corresponding to a PUSCH preparation time for UE processing capability 1 [6, TS
38.214], N TA,max is the maximum timing advance value in msec that can be provided by a TA command field of 12 bits,
subframe,μ
N slot is the number of slots per subframe, and Tsf is the subframe duration of 1 msec. N 1 and N 2 are determined
with respect to the minimum SCS among the SCSs of all configured UL BWPs for all uplink carriers in the TAG and of
all configured DL BWPs for the corresponding downlink carriers. For μ = 0 , the UE assumes N 1,0 = 14 [6, TS
subframe,μ
38.214]. Slot n and N slot are determined with respect to the minimum SCS among the SCSs of all configured UL
BWPs for all uplink carriers in the TAG. NTA,max is determined with respect to the minimum SCS among the SCSs of all
configured UL BWPs for all uplink carriers in the TAG and for all configured initial UL BWPs provided by
initialUplinkBWP. The uplink slot n is the last slot among uplink slot(s) overlapping with the slot(s) of PDSCH
reception assuming ்஺ = 0, where the PDSCH provides the timing advance command and ்஺ is defined in [4, TS
38.211].
If a UE changes an active UL BWP between a time of a timing advance command reception and a time of applying a
corresponding adjustment for the uplink transmission timing, the UE determines the timing advance command value
based on the SCS of the new active UL BWP. If the UE changes an active UL BWP after applying an adjustment for
the uplink transmission timing, the UE assumes a same absolute timing advance command value before and after the
active UL BWP change.
If the received downlink timing changes and is not compensated or is only partly compensated by the uplink timing
adjustment without timing advance command as described in [10, TS 38.133], the UE changes N TA accordingly.
If two adjacent slots overlap due to a TA command, the latter slot is reduced in duration relative to the former slot.
4.3 Timing for secondary cell activation / deactivation

With reference to slots for PUCCH transmissions each consisting of symb
slot
symbols as defined in [4, TS 38.211], when a
UE receives in a PDSCH an activation command [11, TS 38.321] for a secondary cell ending in slot n, the UE applies
the corresponding actions in [11, TS 38.321] no later than the minimum requirement defined in [10, TS 38.133] and no
earlier than slot n + k , except for the following:
- the actions related to CSI reporting on a serving cell that is active in slot n + k
- the actions related to the sCellDeactivationTimer associated with the secondary cell [11, TS 38.321] that the UE
applies in slot n + k
ETSI
- the actions related to CSI reporting on a serving cell which is not active in slot n + k that the UE applies in the
earliest slot after n + k in which the serving cell is active.
subframe,ఓ
The value of k is + 3 slot + 1 where slot n+m is a slot indicated for PUCCH transmission with HARQ-ACK
subframe,μ
information for the PDSCH reception as described in clause 9.2.3 and Nslot is a number of slots per subframe for
the SCS configuration μ of the PUCCH transmission as defined in [4, TS 38.211].
With reference to slots for PUCCH transmissions each consisting of symbslot

symbols as defined in [4, TS 38.211], if a
UE receives a deactivation command [11, TS 38.321] for a secondary cell ending in slot n , the UE applies the
corresponding actions in [11, TS 38.321] no later than the minimum requirement defined in [10, TS 38.133], except for
the actions related to CSI reporting on an activated serving cell which the UE applies in slot n + k .
If the sCellDeactivationTimer associated with the secondary cell expires in slot n , the UE applies the corresponding
actions in [11, TS 38.321] no later than the minimum requirement defined in [10, TS 38.133], except for the actions
related to CSI reporting on an activated serving cell which the UE applies in the first slot that is after slot
subframe, μ
n + 3 ⋅ N slot where μ is the SCS configuration for PDSCH reception on the secondary cell.
5 Radio link monitoring

The downlink radio link quality of the primary cell is monitored by a UE for the purpose of indicating out-of-sync/in-
sync status to higher layers. The UE is not required to monitor the downlink radio link quality in DL BWPs other than
the active DL BWP, as described in clause 12, on the primary cell. If the active DL BWP is the initial DL BWP and for
SS/PBCH block and CORESET multiplexing pattern 2 or 3, as described in clause 13, the UE is expected to perform
RLM using the associated SS/PBCH block when the associated SS/PBCH block index is provided by
RadioLinkMonitoringRS.
If the UE is configured with a SCG, as described in [12, TS 38.331], and the parameter rlf-TimersAndConstants is
provided by higher layers and is not set to release, the downlink radio link quality of the PSCell of the SCG is
monitored by the UE for the purpose of indicating out-of-sync/in-sync status to higher layers. The UE is not required to
monitor the downlink radio link quality in DL BWPs other than the active DL BWP on the PSCell.
A UE can be configured for each DL BWP of a SpCell [11, TS 38.321] with a set of resource indexes, through a
corresponding set of RadioLinkMonitoringRS, for radio link monitoring by failureDetectionResources. The UE is
provided either a CSI-RS resource configuration index, by csi-RS-Index, or a SS/PBCH block index, by ssb-Index. The
UE can be configured with up to N LR − RLM RadioLinkMonitoringRS for link recovery procedures, as described in clause
6, and for radio link monitoring. From the N LR − RLM RadioLinkMonitoringRS, up to NRLM RadioLinkMonitoringRS can
be used for radio link monitoring depending on ௠௔௫ as described in Table 5-1, wherein ௠௔௫ is as defined in clause
4.1, and up to two RadioLinkMonitoringRS can be used for link recovery procedures.
For operation with shared spectrum channel access, when a UE is provided a SS/PBCH block index by ssb-Index, the
UE is expected to perform radio link monitoring using SS/PBCH block(s) in the discovery burst transmission window
as described in clause 4.1, where the SS/PBCH block(s) have candidate SS/PBCH block index(es) corresponding to
SS/PBCH block index provided by ssb-Index.
If the UE is not provided RadioLinkMonitoringRS and the UE is provided for PDCCH receptions TCI states that include
one or more of a CSI-RS
- the UE uses for radio link monitoring the RS provided for the active TCI state for PDCCH reception if the active
TCI state for PDCCH reception includes only one RS
- if the active TCI state for PDCCH reception includes two RS, the UE expects that one RS is configured with qcl-
Type set to 'typeD' [6, TS 38.214] and the UE uses the RS configured with qcl-Type set to 'typeD' for radio link
monitoring; the UE does not expect both RS to be configured with qcl-Type set to 'typeD'
- the UE is not required to use for radio link monitoring an aperiodic or semi-persistent RS
- For Lmax = 4 , the UE selects the NRLM RS provided for active TCI states for PDCCH receptions in CORESETs
associated with the search space sets in an order from the shortest monitoring periodicity. If more than one
ETSI
CORESETs are associated with search space sets having same monitoring periodicity, the UE determines the
order of the CORESET from the highest CORESET index as described in clause 10.1.
A UE does not expect to use more than NRLM RadioLinkMonitoringRS for radio link monitoring when the UE is not
provided RadioLinkMonitoringRS.
Values of N LR − RLM and NRLM for different values of L max are given in Table 5-1.
Table 5-1: N LR − RLM and NRLM as a function of maximum number L max of SS/PBCH blocks per half
frame
L max N LR − RLM NRLM

4 2 2
8 6 4
64 8 8
For a CSI-RS resource configuration, powerControlOffsetSS is not applicable and a UE expects to be provided only
'noCDM' from cdm-Type, only 'one' and 'three' from density, and only '1 port' from nrofPorts [6, TS 38.214].
If a UE is configured with multiple DL BWPs for a serving cell, the UE performs RLM using the RS(s) corresponding
to resource indexes provided by RadioLinkMonitoringRS for the active DL BWP or, if RadioLinkMonitoringRS is not
provided for the active DL BWP, using the RS(s) provided for the active TCI state for PDCCH receptions in
CORESETs on the active DL BWP.
In non-DRX mode operation, the physical layer in the UE assesses once per indication period the radio link quality,
evaluated over the previous time period defined in [10, TS 38.133] against thresholds (Qout and Qin) configured by
rlmInSyncOutOfSyncThreshold. The UE determines the indication period as the maximum between the shortest
periodicity for radio link monitoring resources and 10 msec.
In DRX mode operation, the physical layer in the UE assesses once per indication period the radio link quality,
evaluated over the previous time period defined in [10, TS 38.133], against thresholds (Qout and Qin) provided by
rlmInSyncOutOfSyncThreshold. The UE determines the indication period as the maximum between the shortest
periodicity for radio link monitoring resources and the DRX period.
The physical layer in the UE indicates, in frames where the radio link quality is assessed, out-of-sync to higher layers
when the radio link quality is worse than the threshold Qout for all resources in the set of resources for radio link
monitoring. When the radio link quality is better than the threshold Qin for any resource in the set of resources for radio
link monitoring, the physical layer in the UE indicates, in frames where the radio link quality is assessed, in-sync to
higher layers.
6 Link recovery procedures

A UE can be provided, for each BWP of a serving cell, a set q 0 of periodic CSI-RS resource configuration indexes by
failureDetectionResourcesToAddModList and a set q 1 of periodic CSI-RS resource configuration indexes and/or
SS/PBCH block indexes by candidateBeamRSList or candidateBeamRSListExt or candidateBeamRSSCellList for radio
link quality measurements on the BWP of the serving cell. If the UE is not provided q 0 by
failureDetectionResourcesToAddModList for a BWP of the serving cell, the UE determines the set q 0 to include
periodic CSI-RS resource configuration indexes with same values as the RS indexes in the RS sets indicated by TCI-
State for respective CORESETs that the UE uses for monitoring PDCCH and, if there are two RS indexes in a TCI
state, the set q 0 includes RS indexes configured with qcl-Type set to 'typeD' for the corresponding TCI states. The UE
expects the set q 0 to include up to two RS indexes. The UE expects single port RS in the set q 0 . The UE expects
single-port or two-port CSI-RS with frequency density equal to 1 or 3 REs per RB in the set q 1 .
The thresholds Qout,LR and Qin,LR correspond to the default value of rlmInSyncOutOfSyncThreshold, as described in [10,
TS 38.133] for Qout, and to the value provided by rsrp-ThresholdSSB or rsrp-ThresholdBFR, respectively.
ETSI
The physical layer in the UE assesses the radio link quality according to the set q 0 of resource configurations against
the threshold Qout,LR. For the set q 0 , the UE assesses the radio link quality only according to SS/PBCH blocks on the
PCell or the PSCell or periodic CSI-RS resource configurations that are quasi co-located, as described in [6, TS
38.214], with the DM-RS of PDCCH receptions monitored by the UE. The UE applies the Qin,LR threshold to the L1-
RSRP measurement obtained from a SS/PBCH block. The UE applies the Qin,LR threshold to the L1-RSRP measurement
obtained for a CSI-RS resource after scaling a respective CSI-RS reception power with a value provided by
powerControlOffsetSS.
In non-DRX mode operation, the physical layer in the UE provides an indication to higher layers when the radio link
quality for all corresponding resource configurations in the set q 0 that the UE uses to assess the radio link quality is
worse than the threshold Qout,LR. The physical layer informs the higher layers when the radio link quality is worse than
the threshold Qout,LR with a periodicity determined by the maximum between the shortest periodicity among the
SS/PBCH blocks on the PCell or the PSCell and/or the periodic CSI-RS configurations in the set q 0 that the UE uses
to assess the radio link quality and 2 msec. In DRX mode operation, the physical layer provides an indication to higher
layers when the radio link quality is worse than the threshold Qout,LR with a periodicity determined as described in [10,
TS 38.133].
For the PCell or the PSCell, upon request from higher layers, the UE provides to higher layers the periodic CSI-RS
configuration indexes and/or SS/PBCH block indexes from the set q 1 and the corresponding L1-RSRP measurements
that are larger than or equal to the Qin,LR threshold.
For the SCell, upon request from higher layers, the UE indicates to higher layers whether there is at least one periodic
CSI-RS configuration index and/or SS/PBCH block index from the set q 1 with corresponding L1-RSRP measurements
that are larger than or equal to the Qin,LR threshold, and provides the periodic CSI-RS configuration indexes and/or
SS/PBCH block indexes from the set q 1 and the corresponding L1-RSRP measurements that are larger than or equal to
the Qin,LR threshold, if any.
For the PCell or the PSCell, a UE can be provided a CORESET through a link to a search space set provided by
recoverySearchSpaceId, as described in clause 10.1, for monitoring PDCCH in the CORESET. If the UE is provided
recoverySearchSpaceId, the UE does not expect to be provided another search space set for monitoring PDCCH in the
CORESET associated with the search space set provided by recoverySearchSpaceId.
For the PCell or the PSCell, the UE can be provided, by PRACH-ResourceDedicatedBFR, a configuration for PRACH
transmission as described in clause 8.1. For PRACH transmission in slot n and according to antenna port quasi co-
location parameters associated with periodic CSI-RS resource configuration or with SS/PBCH block associated with
index qnew provided by higher layers [11, TS 38.321], the UE monitors PDCCH in a search space set provided by
recoverySearchSpaceId for detection of a DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI starting from
slot n + 4 within a window configured by BeamFailureRecoveryConfig. For PDCCH monitoring in a search space set
provided by recoverySearchSpaceId and for corresponding PDSCH reception, the UE assumes the same antenna port
quasi-collocation parameters as the ones associated with index qnew until the UE receives by higher layers an
activation for a TCI state or any of the parameters tci-StatesPDCCH-ToAddList and/or tci-StatesPDCCH-
ToReleaseList. After the UE detects a DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI in the search
space set provided by recoverySearchSpaceId, the UE continues to monitor PDCCH candidates in the search space set
provided by recoverySearchSpaceId until the UE receives a MAC CE activation command for a TCI state or tci-
StatesPDCCH-ToAddList and/or tci-StatesPDCCH-ToReleaseList.
For the PCell or the PSCell, after 28 symbols from a last symbol of a first PDCCH reception in a search space set
provided by recoverySearchSpaceId for which the UE detects a DCI format with CRC scrambled by C-RNTI or MCS-
C-RNTI and until the UE receives an activation command for PUCCH-SpatialRelationInfo [11, TS 38.321] or is
provided PUCCH-SpatialRelationInfo for PUCCH resource(s), the UE transmits a PUCCH on a same cell as the
PRACH transmission using
- a same spatial filter as for the last PRACH transmission
- a power determined as described in clause 7.2.1 with qu = 0 , q d = q new , and l = 0
For the PCell or the PSCell, after 28 symbols from a last symbol of a first PDCCH reception in a search space set
provided by recoverySearchSpaceId where a UE detects a DCI format with CRC scrambled by C-RNTI or MCS-C-
ETSI
RNTI, the UE assumes same antenna port quasi-collocation parameters as the ones associated with index qnew for
PDCCH monitoring in a CORESET with index 0.
For the PCell or the PSCell, if BFR MAC CE [11, TS38.321] is transmitted in Msg3 or MsgA of contention based
random access procedure, and if a PUCCH resource is provided with PUCCH-SpatialRelationInfo, after 28 symbols
from the last symbol of the PDCCH reception that determines the completion of the contention based random access
procedure as described in clause 5.1.5 of [11, TS38.321], the UE transmits the PUCCH on a same cell as the PRACH
transmission using
- a same spatial filter as for the last PRACH transmission
- a power determined as described in clause 7.2.1 with qu = 0 , qd = qnew , and l = 0 , where qnew is the SS/PBCH
block index selected for the last PRACH transmission.
A UE can be provided, by schedulingRequestID-BFR-SCell, a configuration for PUCCH transmission with a link

recovery request (LRR) as described in clause 9.2.4. The UE can transmit in a first PUSCH MAC CE providing
index(es) for at least corresponding SCell(s) with radio link quality worse than Qout,LR, indication(s) of presence of new
for corresponding SCell(s), and index(es) new for a periodic CSI-RS configuration or for a SS/PBCH block provided
by higher layers, as described in [11, TS 38.321], if any, for corresponding SCell(s). After 28 symbols from a last
symbol of a PDCCH reception with a DCI format scheduling a PUSCH transmission with a same HARQ process
number as for the transmission of the first PUSCH and having a toggled NDI field value, the UE
- monitors PDCCH in all CORESETs on the SCell(s) indicated by the MAC CE using the same antenna port quasi
co-location parameters as the ones associated with the corresponding index(es) new , if any
- transmits PUCCH on a PUCCH-SCell using a same spatial domain filter as the one corresponding to new , if
any, for periodic CSI-RS or SS/PBCH block reception, as described in clause 9.2.2, and using a power
determined as described in clause 7.2.1 with u = 0, d = new , and = 0, if
- the UE is provided PUCCH-SpatialRelationInfo for the PUCCH,
- a PUCCH with the LRR was either not transmitted or was transmitted on the PCell or the PSCell, and
- the PUCCH-SCell is included in the SCell(s) indicated by the MAC-CE
where the SCS configuration for the 28 symbols is the smallest of the SCS configurations of the active DL BWP for the
PDCCH reception and of the active DL BWP(s) of the at least one SCell.
7 Uplink Power control

Uplink power control determines a power for PUSCH, PUCCH, SRS, and PRACH transmissions.
A UE does not expect to simultaneously maintain more than four pathloss estimates per serving cell for all
PUSCH/PUCCH/SRS transmissions as described in clauses 7.1.1, 7.2.1, and 7.3.1, except for SRS transmissions
configured by SRS-PosResourceSet as described in clause 7.3.1. If the UE is provided a number of RS resources for
pathloss estimation for PUSCH/PUCCH/SRS transmissions that is larger than 4, the UE maintains for pathloss
estimation RS resources corresponding to RS resource indexes ௗ as described in clauses 7.1.1, 7.2.1, and 7.3.1. If an
RS resource updated by MAC CE, as described in clauses 7.1.1, 7.2.1 and 7.3.1, is one from the RS resources the UE
maintains for pathloss estimation for PUSCH/PUCCH/SRS transmissions, the UE applies the pathloss estimation based
on the RS resources starting from the first slot that is after slot + 3 ∙ ܰslot
subframe,ߤ
where is the slot where the UE would
transmit a PUCCH or PUSCH with HARQ-ACK information for the PDSCH providing the MAC CE and is the SCS
configuration for the PUCCH or PUSCH, respectively.
ఓ
A PUSCH/PUCCH/SRS/PRACH transmission occasion is defined by a slot index ௦,௙ within a frame with system
frame number , a first symbol within the slot, and a number of consecutive symbols . For a PUSCH
transmission with repetition Type B, a PUSCH transmission occasion is a nominal repetition [6, TS 38.214].
ETSI
7.1 Physical uplink shared channel

For a PUSCH transmission on active UL BWP , as described in clause 12, of carrier of serving cell , a UE first
calculates a linear value PUSCH,௕,௙,௖ ( , , ௗ , ) of the transmit power PUSCH,௕,௙,௖ ( , , ௗ , ), with parameters as defined in
clause 7.1.1. For a PUSCH transmission scheduled by a DCI format other than DCI format 0_0, or configured by
ConfiguredGrantConfig or semiPersistentOnPUSCH, if txConfig in PUSCH-Config is set to 'codebook',
- if ul-FullPowerTransmission in PUSCH-Config is provided, the UE scales PUSCH,௕,௙,௖ ( , , ௗ , ) by where:
- if ul-FullPowerTransmission in PUSCH-Config is set to fullpowerMode1, and each SRS resource in the SRS-
ResourceSet with usage set to 'codebook' has more than one SRS port, is the ratio of a number of antenna
ports with non-zero PUSCH transmission power over the maximum number of SRS ports supported by the
UE in one SRS resource
- if ul-FullPowerTransmission in PUSCH-Config is set to fullpowerMode2,
- = 1 for full power TPMIs reported by the UE [16, TS 38.306], and is the ratio of a number of antenna
ports with non-zero PUSCH transmission power over a number of SRS ports for remaining TPMIs, where
the number of SRS ports is associated with an SRS resource indicated by an SRI field in a DCI format
scheduling the PUSCH transmission if more than one SRS resource is configured in the SRS-ResourceSet
with usage set to 'codebook', or indicated by Type 1 configured grant, or the number of SRS ports is
associated with the SRS resource if only one SRS resource is configured in the SRS-ResourceSet with
usage set to 'codebook',
- = 1, if an SRS resource with a single port is indicated by an SRI field in a DCI format scheduling the
PUSCH transmission when more than one SRS resource is provided in the SRS-ResourceSet with usage
set to 'codebook', or indicated by Type 1 configured grant, or if only one SRS resource with a single port
is provided in the SRS-ResourceSet with usage set to 'codebook', and
- if ul-FullPowerTransmission in PUSCH-Config is set to fullpower, =1

- else, if each SRS resource in the SRS-ResourceSet with usage set to 'codebook' has more than one SRS port, the
UE scales the linear value by the ratio of the number of antenna ports with a non-zero PUSCH transmission
power to the maximum number of SRS ports supported by the UE in one SRS resource.
The UE splits the power equally across the antenna ports on which the UE transmits the PUSCH with non-zero power.
7.1.1 UE behaviour
If a UE transmits a PUSCH on active UL BWP b of carrier f of serving cell c using parameter set configuration
with index j and PUSCH power control adjustment state with index l , the UE determines the PUSCH transmission
power PPUSCH ,b , f , c (i, j , qd , l ) in PUSCH transmission occasion i as
 PCMAX, f ,c (i ), 
PPUSCH,b, f,c (i, j, qd , l ) = min  μ 
 PO_PUSCH,b, f,c ( j ) + 10 log10 (2 ⋅ M RB,b, f,c (i )) + α b, f ,c ( j ) ⋅ PLb, f ,c (qd ) + Δ TF,b, f,c (i ) + f b, f ,c (i, l )
PUSCH
[dBm]
where,
- PCMAX,f ,c (i) is the UE configured maximum output power defined in [8-1, TS 38.101-1], [8-2, TS38.101-2] and
[8-3, TS38.101-3] for carrier f of serving cell c in PUSCH transmission occasion i .
- PO_PUSCH,b, f ,c ( j) is a parameter composed of the sum of a component PO_NOMINAL_PUSCH,f,c ( j) and a component

PO_UE_PUSCH,b, f ,c ( j) where j ∈ {0, 1, ..., J − 1} .
- If a UE established dedicated RRC connection using a Type-1 random access procedure, as described in
clause 8, and is not provided P0-PUSCH-AlphaSet or for a PUSCH (re)transmission corresponding to a RAR
UL grant as described in clause 8.3,
ETSI
PO_UE_PUSCH ,b , f , c (0) = 0 PO_NOMINAL_ PUSCH, f ,c (0) = PO_PRE + Δ PREAMBLE _ Msg 3

j =0, , and ,
where O_PRE is provided by preambleReceivedTargetPower [11, TS 38.321] and ௉ோா஺ெ஻௅ா _ெ௦௚ଷ is

provided by msg3-DeltaPreamble, or ΔPREAMBLE_ Msg3 = 0 dB if msg3-DeltaPreamble is not provided, for
carrier f of serving cell c
- If a UE established dedicated RRC connection using a Type-2 random access procedure, as described in
clause 8, and is not provided P0-PUSCH-AlphaSet, or for a PUSCH transmission for Type-2 random access
procedure as described in clause 8.1A,
= 0, O_UE_PUSCH,௕,௙,௖ (0) = 0, and O_NOMINAL_PUSCH,௙,௖ (0) = O_PRE + ெ௦௚஺_௉௎ௌ஼ு ,

where O_PRE is provided by msgA-preambleReceivedTargetPower, or by preambleReceivedTargetPower if
msgA-preambleReceivedTargetPower is not provided and ெ௦௚஺_௉௎ௌ஼ு is provided by msgA-DeltaPreamble,
or ெ௦௚஺ _௉௎ௌ஼ு = ௉ோா஺ெ஻௅ா _ெ௦௚ଷ dB if msgA-DeltaPreamble is not provided, for carrier of serving cell
- For a PUSCH (re)transmission configured by ConfiguredGrantConfig, j = 1 , PO_NOMINAL_PUSCH, f ,c (1) is
PUSCH,f ,c (1) = PO_NOMINAL_

provided by p0-NominalWithoutGrant, or PO_NOMINAL_ PUSCH,f ,c (0) if p0-
NominalWithoutGrant is not provided, and PO_UE_PUSCH , b , f , c (1) is provided by p0 obtained from p0-PUSCH-
Alpha in ConfiguredGrantConfig that provides an index P0-PUSCH-AlphaSetId to a set of P0-PUSCH-
AlphaSet for active UL BWP b of carrier f of serving cell c
- For j ∈ {2, ..., J − 1} = S J , a PO_NOMINAL_PUSCH, f ,c ( j ) value, applicable for all j ∈ S J , is provided by p0-
NominalWithGrant, or PO_NOMINAL_PUSCH, f ,c ( j ) = PO_NOMINAL_PUSCH, f ,c (0) if p0-NominalWithGrant is not
provided, for each carrier f of serving cell c and a set of PO_UE_PUSCH ,b , f , c ( j ) values are provided by a set
of p0 in P0-PUSCH-AlphaSet indicated by a respective set of p0-PUSCH-AlphaSetId for active UL BWP b
of carrier f of serving cell c
- If the UE is provided by SRI-PUSCH-PowerControl more than one values of p0-PUSCH-AlphaSetId and

if a DCI format scheduling the PUSCH transmission includes an SRI field, the UE obtains a mapping
from sri-PUSCH-PowerControlId in SRI-PUSCH-PowerControl between a set of values for the SRI field
in the DCI format [5, TS 38.212] and a set of indexes provided by p0-PUSCH-AlphaSetId that map to a
set of P0-PUSCH-AlphaSet values and determines the value of PO_UE_PUSCH , b , f , c ( j ) from the p0-PUSCH-
AlphaSetId value that is mapped to the SRI field value. If the DCI format also includes an open-loop
power control parameter set indication field and a value of the open-loop power control parameter set
indication field is '1', the UE determines a value of PO_UE_PUSCH , b , f , c ( j ) from a first value in P0-PUSCH-
Set with a p0-PUSCH-SetId value mapped to the SRI field value.
- If the PUSCH transmission except for the PUSCH retransmission corresponding to a RAR UL grant is
scheduled by a DCI format that does not include an SRI field, or if SRI-PUSCH-PowerControl is not
provided to the UE, j = 2 ,
- If P0-PUSCH-Set is provided to the UE and the DCI format includes an open-loop power control
parameter set indication field, the UE determines a value of PO_UE_PUSCH , b , f , c ( j ) from
- a first P0-PUSCH-AlphaSet in p0-AlphaSets if a value of the open-loop power control parameter

set indication field is '0' or '00'
- a first value in P0-PUSCH-Set with the lowest p0-PUSCH-SetID value if a value of the open-loop
power control parameter set indication field is '1' or '01'
- a second value in P0-PUSCH-Set with the lowest p0-PUSCH-SetID value if a value of the open-
loop power control parameter set indication field is '10'
- else, the UE determines PO_UE_PUSCH ,b , f , c ( j ) from the value of the first P0-PUSCH-AlphaSet in p0-
AlphaSets
ETSI
- For α b , f ,c ( j )
- For j = 0 ,
- if O_NOMINAL_PUSCH,௙,௖ (0) = O_PRE + ெ௦௚஺_௉௎ௌ஼ு and msgA-Alpha is provided, ௕,௙,௖ (0) is the value
of msgA-Alpha
- elseif O_NOMINAL_PUSCH,௙,௖ (0) = O_PRE + ௉ோா஺ெ஻௅ா _ெ௦௚ଷ or msgA-Alpha is not provided, and msg3-
Alpha is provided, α b , f ,c (0) is the value of msg3-Alpha
- else, α b , f , c (0) = 1
- For j = 1 , α b , f ,c (1) is provided by alpha obtained from p0-PUSCH-Alpha in ConfiguredGrantConfig

providing an index P0-PUSCH-AlphaSetId to a set of P0-PUSCH-AlphaSet for active UL BWP b of carrier
f of serving cell c
- For j ∈ S J , a set of αb, f ,c ( j) values are provided by a set of alpha in P0-PUSCH-AlphaSet indicated by a
respective set of p0-PUSCH-AlphaSetId for active UL BWP b of carrier f of serving cell c
- If the UE is provided SRI-PUSCH-PowerControl and more than one values of p0-PUSCH-AlphaSetId,
and if a DCI format scheduling the PUSCH transmission includes an SRI field, the UE obtains a mapping
from sri-PUSCH-PowerControlId in SRI-PUSCH-PowerControl between a set of values for the SRI field
in the DCI format [5, TS 38.212] and a set of indexes provided by p0-PUSCH-AlphaSetId that map to a
set of P0-PUSCH-AlphaSet values and determines the values of α b, f ,c ( j ) from the p0-PUSCH-
AlphaSetId value that is mapped to the SRI field value
- If the PUSCH transmission except for the PUSCH retransmission corresponding to a RAR UL grant is
scheduled by a DCI format that does not include an SRI field, or if SRI-PUSCH-PowerControl is not
provided to the UE, j = 2 , and the UE determines α b, f ,c ( j ) from the value of the first P0-PUSCH-
AlphaSet in p0-AlphaSets
PUSCH
- M RB, b , f , c ( i ) is the bandwidth of the PUSCH resource assignment expressed in number of resource blocks for
PUSCH transmission occasion i on active UL BWP b of carrier f of serving cell c and μ is a SCS
configuration defined in [4, TS 38.211]
- PLb , f ,c (q d ) is a downlink pathloss estimate in dB calculated by the UE using reference signal (RS) index ௗ for
the active DL BWP, as described in clause 12, of carrier of serving cell
- If the UE is not provided PUSCH-PathlossReferenceRS and enableDefaultBeamPL-ForSRS, or before the

UE is provided dedicated higher layer parameters, the UE calculates PLb , f ,c (q d ) using a RS resource from
an SS/PBCH block with same SS/PBCH block index as the one the UE uses to obtain MIB
- If the UE is configured with a number of RS resource indexes, up to the value of maxNrofPUSCH-

PathlossReferenceRSs, and a respective set of RS configurations for the number of RS resource indexes by
PUSCH-PathlossReferenceRS, the set of RS resource indexes can include one or both of a set of SS/PBCH
block indexes, each provided by ssb-Index when a value of a corresponding pusch-PathlossReferenceRS-Id
maps to a SS/PBCH block index, and a set of CSI-RS resource indexes, each provided by csi-RS-Index when
a value of a corresponding pusch-PathlossReferenceRS-Id maps to a CSI-RS resource index. The UE
identifies a RS resource index ௗ in the set of RS resource indexes to correspond either to a SS/PBCH block
index or to a CSI-RS resource index as provided by pusch-PathlossReferenceRS-Id in PUSCH-
PathlossReferenceRS
- If the PUSCH transmission is scheduled by a RAR UL grant as described in clause 8.3, or for a PUSCH
transmission for Type-2 random access procedure as described in clause 8.1A, the UE uses the same RS
resource index ௗ as for a corresponding PRACH transmission
- If the UE is provided SRI-PUSCH-PowerControl and more than one values of PUSCH-

PathlossReferenceRS-Id, the UE obtains a mapping from sri-PUSCH-PowerControlId in SRI-PUSCH-
ETSI
PowerControl between a set of values for the SRI field in a DCI format scheduling the PUSCH transmission
and a set of PUSCH-PathlossReferenceRS-Id values and determines the RS resource index ௗ from the value
of PUSCH-PathlossReferenceRS-Id that is mapped to the SRI field value where the RS resource is either on
serving cell or, if provided, on a serving cell indicated by a value of pathlossReferenceLinking
- If the PUSCH transmission is scheduled by DCI format 0_0, and if the UE is provided a spatial setting by
PUCCH-SpatialRelationInfo for a PUCCH resource with a lowest index for active UL BWP of each carrier
and serving cell , as described in clause 9.2.2, the UE uses the same RS resource index ௗ as for a
PUCCH transmission in the PUCCH resource with the lowest index
- If the PUSCH transmission is not scheduled by DCI format 0_0, and if the UE is provided
enableDefaultBeamPL-ForSRS and is not provided PUSCH-PathlossReferenceRS and PUSCH-
PathlossReferenceRS-r16, the UE uses the same RS resource index ௗ as for an SRS resource set with an
SRS resource associated with the PUSCH transmission
- If
- the PUSCH transmission is scheduled by DCI format 0_0 and the UE is not provided a spatial setting for
a PUCCH transmission, or
- the PUSCH transmission is scheduled by DCI format 0_1 or DCI format 0_2 that does not include an SRI
field, or
- SRI-PUSCH-PowerControl is not provided to the UE,
the UE determines a RS resource index ௗ with a respective PUSCH-PathlossReferenceRS-Id value being

equal to zero where the RS resource is either on serving cell or, if provided, on a serving cell indicated by a
value of pathlossReferenceLinking
- If
- the PUSCH transmission is scheduled by DCI format 0_0 on serving cell ,
- the UE is not provided PUCCH resources for the active UL BWP of serving cell , and
- the UE is provided enableDefaultBeamPL-ForPUSCH0-0
the UE determines a RS resource index ௗ providing a periodic RS resource configured with qcl-Type set to
'typeD' in the TCI state or the QCL assumption of a CORESET with the lowest index in the active DL BWP
of the serving cell
- If
- the PUSCH transmission is scheduled by DCI format 0_0 on serving cell ,
- the UE is not provided a spatial setting for PUCCH resources on the active UL BWP of the primary cell
[11, TS 38.321], and
- the UE is provided enableDefaultBeamPL-ForPUSCH0-0
the UE determines a RS resource index ௗ providing a periodic RS resource configured with qcl-Type set to
'typeD' in the TCI state or the QCL assumption of a CORESET with the lowest index in the active DL BWP
of the serving cell
- For a PUSCH transmission configured by ConfiguredGrantConfig, if rrc-ConfiguredUplinkGrant is included

in ConfiguredGrantConfig, a RS resource index q d is provided by a value of pathlossReferenceIndex
included in rrc-ConfiguredUplinkGrant where the RS resource is either on serving cell c or, if provided, on
a serving cell indicated by a value of pathlossReferenceLinking
- For a PUSCH transmission configured by ConfiguredGrantConfig that does not include rrc-
ConfiguredUplinkGrant, the UE determines a RS resource index q d from a value of PUSCH-
PathlossReferenceRS-Id that is mapped to a SRI field value in a DCI format activating the PUSCH
transmission. If the DCI format activating the PUSCH transmission does not include an SRI field, the UE
determines a RS resource index q d with a respective PUSCH-PathlossReferenceRS-Id value being equal to
ETSI
zero where the RS resource is either on serving cell c or, if provided, on a serving cell indicated by a value
of pathlossReferenceLinking
- If the UE is provided enablePL-RS-UpdateForPUSCH-SRS, a mapping between sri-PUSCH-PowerControlId

and PUSCH-PathlossReferenceRS-Id values can be updated by a MAC CE as described in [11, TS38.321]
- For a PUSCH transmission scheduled by a DCI format that does not include an SRI field, or for a PUSCH
transmission configured by ConfiguredGrantConfig and activated, as described in clause 10.2, by a DCI
format that does not include an SRI field, a RS resource index q d is determined from the PUSCH-
PathlossReferenceRS-Id mapped to sri-PUSCH-PowerControlId = 0
PLb , f ,c (q d ) = referenceSignalPower – higher layer filtered RSRP, where referenceSignalPower is provided by

higher layers and RSRP is defined in [7, TS 38.215] for the reference serving cell and the higher layer filter
configuration provided by QuantityConfig is defined in [12, TS 38.331] for the reference serving cell
If the UE is not configured periodic CSI-RS reception, referenceSignalPower is provided by ss-PBCH-

BlockPower. If the UE is configured periodic CSI-RS reception, referenceSignalPower is provided either by ss-
PBCH-BlockPower or by powerControlOffsetSS providing an offset of the CSI-RS transmission power relative
to the SS/PBCH block transmission power [6, TS 38.214]. If powerControlOffsetSS is not provided to the UE,
the UE assumes an offset of 0 dB.
- (( s
)
ΔTF,b, f ,c (i) = 10log10 2BPRE⋅K − 1 ⋅ βoffset
PUSCH
)
for K S = 1.25 and Δ TF,b, f ,c (i) = 0 for KS = 0 where K S is provided
by deltaMCS for each UL BWP b of each carrier f and serving cell c . If the PUSCH transmission is over
more than one layer [6, TS 38.214], Δ TF,b, f ,c (i) = 0 . BPRE and β offset
PUSCH
, for active UL BWP b of each carrier
f and each serving cell c , are computed as below
C −1
BPRE =  K r N RE for PUSCH with UL-SCH data and BPRE = Qm ⋅ R β offset
PUSCH
- for CSI transmission in a
r =0
PUSCH without UL-SCH data, where
- C is a number of transmitted code blocks, K r is a size for code block r , and N RE is a number of
b , f ,c ( i ) −1
PUSCH
N symb,
resource elements determined as N RE = M

PUSCH
RB,b , f ,c (i) ⋅ N
j =0
RB
sc,data
PUSCH
(i, j ) , where Nsymb,b, f , c (i ) is a number
of symbols for PUSCH transmission occasion i on active UL BWP b of carrier f of serving cell c,
RB
N sc, data (i, j ) is a number of subcarriers excluding DM-RS subcarriers and phase-tracking RS samples [4,
TS 38.211] in PUSCH symbol j and assuming no segmentation for a nominal repetition in case the
PUSCH transmission is with repetition Type B, 0 ≤ j < Nsymb,b, f , c (i) , and C , K r are defined in [5, TS
PUSCH
38.212]
- β offset
PUSCH
= 1 when the PUSCH includes UL-SCH data and β offset
PUSCH
= β offset
CSI,1
, as described in clause 9.3, when
the PUSCH includes CSI and does not include UL-SCH data
- Qm is the modulation order and R is the target code rate, as described in [6, TS 38.214], provided by the DCI
format scheduling the PUSCH transmission that includes CSI and does not include UL-SCH data
- For the PUSCH power control adjustment state f b , f , c ( i , l ) for active UL BWP b of carrier f of serving cell
c in PUSCH transmission occasion i
- δ PUSCH, b , f ,c (i, l ) is a TPC command value included in a DCI format that schedules the PUSCH transmission
occasion i on active UL BWP b of carrier f of serving cell c or jointly coded with other TPC commands
in a DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, as described in clause 11.3
- l ∈ { 0, 1} if the UE is configured with twoPUSCH-PC-AdjustmentStates and l = 0 if the UE is not

configured with twoPUSCH-PC-AdjustmentStates or if the PUSCH transmission is scheduled by a RAR
UL grant as described in clause 8.3
ETSI
- For a PUSCH (re)transmission configured by ConfiguredGrantConfig, the value of l ∈ { 0, 1} is

provided to the UE by powerControlLoopToUse
- If the UE is provided SRI-PUSCH-PowerControl, the UE obtains a mapping between a set of values

for the SRI field in a DCI format scheduling the PUSCH transmission and the l value(s) provided by
sri-PUSCH-ClosedLoopIndex and determines the l value that is mapped to the SRI field value
- If the PUSCH transmission is scheduled by a DCI format that does not include an SRI field, or if an
SRI-PUSCH-PowerControl is not provided to the UE, l = 0
- If the UE obtains one TPC command from a DCI format 2_2 with CRC scrambled by a TPC-PUSCH-
RNTI, the l value is provided by the closed loop indicator field in DCI format 2_2
( )
C Di −1
- f b , f , c (i , l ) = f b , f , c (i − i 0 , l ) +  δ PUSCH,b, f ,c (m, l )
m =0
is the PUSCH power control adjustment state l for active
UL BWP b of carrier f of serving cell c and PUSCH transmission occasion i if the UE is not provided
tpc-Accumulation, where
- The δ PUSCH,b, f ,c values are given in Table 7.1.1-1
C ( D i )−1
- δ
m=0
PUSCH, b , f ,c ( m , l ) is a sum of TPC command values in a set D i of TPC command values with
cardinality C (Di ) that the UE receives between K PUSCH (i − i0 ) − 1 symbols before PUSCH transmission
occasion i − i 0 and K PUSCH (i ) symbols before PUSCH transmission occasion i on active UL BWP b of
carrier f of serving cell c for PUSCH power control adjustment state l , where i0 > 0 is the smallest
integer for which K PUSCH (i − i0 ) symbols before PUSCH transmission occasion i − i0 is earlier than
K PUSCH (i ) symbols before PUSCH transmission occasion i
- If a PUSCH transmission is scheduled by a DCI format, K PUSCH (i ) is a number of symbols for active UL
BWP b of carrier f of serving cell c after a last symbol of a corresponding PDCCH reception and
before a first symbol of the PUSCH transmission
- If a PUSCH transmission is configured by ConfiguredGrantConfig, K PUSCH (i ) is a number of K PUSCH, min

slot
symbols equal to the product of a number of symbols per slot, Nsymb, and the minimum of the values
provided by k2 in PUSCH-ConfigCommon for active UL BWP b of carrier f of serving cell c
- If the UE has reached maximum power for active UL BWP b of carrier f of serving cell c at PUSCH
C ( D i )−1
transmission occasion i − i 0 and δ
m=0
PUSCH, b , f , c ( m, l ) ≥ 0 , then f b , f , c (i, l ) = f b , f , c (i − i0 , l )
- If UE has reached minimum power for active UL BWP b of carrier f of serving cell c at PUSCH
( )
C Di −1
transmission occasion i − i 0 and  δ PUSCH, b, f ,c (m, l ) ≤ 0 , then

m=0
f b, f ,c (i, l ) = f b, f ,c (i − i0 , l )
- A UE resets accumulation of a PUSCH power control adjustment state l for active UL BWP b of carrier
f of serving cell c to f b, f ,c (k, l) = 0, k = 0,1,...,i
- If a configuration for a corresponding PO_UE_PUSCH ,b , f ,c ( j ) value is provided by higher layers
- If a configuration for a corresponding α b, f ,c ( j ) value is provided by higher layers
where l is determined from the value of j as
ETSI
- If j > 1 and the UE is provided higher SRI-PUSCH-PowerControl, l is the sri-PUSCH-

ClosedLoopIndex value(s) configured in any SRI-PUSCH-PowerControl with the sri-P0-PUSCH-
AlphaSetId value corresponding to j
- If j > 1 and the UE is not provided SRI-PUSCH-PowerControl or ݆ = 0, l = 0

- If j = 1 , l is provided by the value of powerControlLoopToUse
- fb, f ,c (i, l) = δPUSCH,b, f ,c (i,l) is the PUSCH power control adjustment state for active UL BWP b of carrier
f of serving cell c and PUSCH transmission occasion i if the UE is provided tpc-Accumulation, where
- δ PUSCH, b , f ,c absolute values are given in Table 7.1.1-1
- If the UE receives a random access response message in response to a PRACH transmission or a MsgA
transmission on active UL BWP b of carrier f of serving cell c as described in clause 8
- f b , f ,c (0, l ) = ΔPrampup ,b , f ,c + δ msg 2,b , f ,c , where l = 0 and
- δ msg 2 , b , f , c is a TPC command value indicated in a random access response grant of the random
access response message corresponding to a PRACH transmission according to Type-1 random access
procedure, or in a random access response grant of the random access response message
corresponding to a MsgA transmission according to Type-2 random access procedure with RAR
message(s) for fallbackRAR, on active UL BWP b of carrier f in the serving cell c , and
   10 log10 (2 μ ⋅ M RB, PUSCH

b , f , c (0))    
     
- ΔPrampup,b, f , c = min max 0 , PCMAX, f , c −  + PO_PUSCH,b, f , c (0) + α b, f ,c (0) ⋅ PLc   , ΔP rampuprequested ,b, f ,c 
     
 


+ Δ TF,b, f , c (0) + δ msg 2,b, f ,c    


and ΔPrampuprequ ested ,b , f ,c is provided by higher layers and corresponds to the total power ramp-up
requested by higher layers from the first to the last random access preamble for carrier f in the
serving cell c, PUSCH
M RB,b, f , c (0) is the bandwidth of the PUSCH resource assignment expressed in number
of resource blocks for the first PUSCH transmission on active UL BWP b of carrier f of serving
cell c , and Δ TF ,b , f ,c ( 0 ) is the power adjustment of first PUSCH transmission on active UL BWP b
of carrier f of serving cell c.
- If the UE transmits the PUSCH in PUSCH transmission occasion ݅ on active UL BWP ܾ of carrier ݂ of
serving cell ܿ as described in clause 8.1A, ݂௕ ௙ ௖ (0, ݈ ) = ߂ܲ௥௔௠௣௨௣ ௕ ௙ ௖ , where
, , , , ,
- ݈ = 0, and
   10 log10 (2 μ ⋅ M RB, PUSCH
b , f , c (i ))    
     
- ΔPrampup,b, f ,c = min max 0 , PCMAX, f ,c −  + PO_PUSCH,b, f ,c (0) + α b, f ,c (0) ⋅ PLc (i)   , ΔP rampuprequested ,b, f ,c 
  
   
  
+ Δ TF,b, f ,c (i)    


and ߂ܲ௥௔௠௣௨௣௥௘௤௨௘௦௧௘ௗ ௕ ௙ ௖ is provided by higher layers and corresponds to the total power ramp-up
, , ,
requested by higher layers, ‫ ܯ‬௕ ௙ ௖ (݅ ) is the bandwidth of the PUSCH resource assignment expressed in
PUSCH
number of resource blocks, and ߂ ௕ ௙ ௖ (݅ ) is the power adjustment of the PUSCH transmission in
RB, , ,
TF, , ,
PUSCH transmission occasion ݅ .
ETSI
Table 7.1.1-1: Mapping of TPC Command Field in a DCI format scheduling a PUSCH transmission, or
in DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, or in DCI format 2_3, to absolute and
accumulated δ PUSCH, b , f , c values or δ SRS, b , f , c values
TPC Command Field Accumulated δ PUSCH, b , f , c or δ SRS, b , f ,c [dB] Absolute δ PUSCH, b , f ,c or δ SRS, b , f ,c [dB]
0 -1 -4
1 0 -1
2 1 1
3 3 4
7.2 Physical uplink control channel

If the UE is configured with a SCG, the UE shall apply the procedures described in this clause for both MCG and SCG.
- When the procedures are applied for MCG, the term 'serving cell' in this clause refers to serving cell belonging to
the MCG.
- When the procedures are applied for SCG, the term 'serving cell' in this clause refers to serving cell belonging to
the SCG. The term 'primary cell' in this clause refers to the PSCell of the SCG.
If the UE is configured with a PUCCH-SCell, the UE shall apply the procedures described in this clause for both
primary PUCCH group and secondary PUCCH group.
- When the procedures are applied for the primary PUCCH group, the term 'serving cell' in this clause refers to
serving cell belonging to the primary PUCCH group.
- When the procedures are applied for the secondary PUCCH group, the term 'serving cell' in this clause refers to
serving cell belonging to the secondary PUCCH group. The term 'primary cell' in this clause refers to the
PUCCH-SCell of the secondary PUCCH group. If pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup-r16 is
provided, pdsch-HARQ-ACK-Codebook is replaced by pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup-
r16.
7.2.1 UE behaviour
If a UE transmits a PUCCH on active UL BWP b of carrier f in the primary cell c using PUCCH power control
adjustment state with index l , the UE determines the PUCCH transmission power PPUCCH,b, f ,c (i, qu , qd , l ) in PUCCH
transmission occasion i as
PCMAX, f , c (i), 
PPUCCH,b, f , c (i, qu , qd , l ) = min 
PO_PUCCH,b, f , c (qu ) + 10 log10 (2 ⋅ M RB,b, f , c (i)) + PLb, f , c (qd ) + Δ F_PUCCH(F ) + ΔTF,b, f , c (i) + gb, f , c (i, l )
μ PUCCH
[dBm]
where
- PCMAX, f ,c ( i ) is the UE configured maximum output power defined in [8-1, TS 38.101-1], [8-2, TS38.101-2] and
[8-3, TS38.101-3] for carrier f of primary cell c in PUCCH transmission occasion i
- PO_PUCCH,b, f ,c (qu ) is a parameter composed of the sum of a component PO_NOMINAL_PUCCH , provided by p0-
nominal, or PO_NOMINAL_ PUCCH = 0 dBm if p0-nominal is not provided, for carrier f of primary cell c and, if
provided, a component PO_UE_PUCCH (qu ) provided by p0-PUCCH-Value in P0-PUCCH for active UL BWP b of
carrier f of primary cell c , where 0 ≤ q u < Q u . Qu is a size for a set of PO_UE_PUCCH values provided by
maxNrofPUCCH-P0-PerSet. The set of PO_UE_PUCCH values is provided by p0-Set. If p0-Set is not provided to
the UE, PO_UE_PUCCH (qu ) = 0 , 0 ≤ qu < Qu
ETSI
- If the UE is provided PUCCH-SpatialRelationInfo, the UE obtains a mapping, by an index provided by p0-

PUCCH-Id, between a set of pucch-SpatialRelationInfoId values and a set of p0-PUCCH-Value values. If the
UE is provided more than one values for pucch-SpatialRelationInfoId and the UE receives an activation
command [11, TS 38.321] indicating a value of pucch-SpatialRelationInfoId, the UE determines the p0-
PUCCH-Value value through the link to a corresponding p0-PUCCH-Id index. The UE applies the activation
subframe,μ
command in the first slot that is after slot k + 3 ⋅ Nslot where k is the slot where the UE would transmit a
PUCCH with HARQ-ACK information for the PDSCH providing the activation command and μ is the SCS
configuration for the PUCCH
- If the UE is not provided PUCCH-SpatialRelationInfo, the UE obtains the p0-PUCCH-Value value from the
P0-PUCCH with p0-PUCCH-Id value equal to the minimum p0-PUCCH-Id value in p0-Set
PUCCH
- M RB,b , f , c (i ) is a bandwidth of the PUCCH resource assignment expressed in number of resource blocks for
PUCCH transmission occasion i on active UL BWP b of carrier f of primary cell c and μ is a SCS
configuration defined in [4, TS 38.211]
- PL b , f , c ( q d ) is a downlink pathloss estimate in dB calculated by the UE using RS resource index q d as

described in clause 7.1.1 for the active DL BWP b of carrier f of the primary cell c as described in clause 12
- If the UE is not provided pathlossReferenceRSs or before the UE is provided dedicated higher layer
parameters, the UE calculates PL b , f , c ( q d ) using a RS resource obtained from an SS/PBCH block with same
SS/PBCH block index as the one the UE uses to obtain MIB
- If the UE is provided a number of RS resource indexes, the UE calculates PL b , f , c ( q d ) using RS resource

with index q d , where 0 ≤ qd < Qd . Qd is a size for a set of RS resources provided by maxNrofPUCCH-
PathlossReferenceRSs. The set of RS resources is provided by pathlossReferenceRSs. The set of RS
resources can include one or both of a set of SS/PBCH block indexes, each provided by ssb-Index in
PUCCH-PathlossReferenceRS when a value of a corresponding pucch-PathlossReferenceRS-Id maps to a
SS/PBCH block index, and a set of CSI-RS resource indexes, each provided by csi-RS-Index when a value of
a corresponding pucch-PathlossReferenceRS-Id maps to a CSI-RS resource index. The UE identifies a RS
resource in the set of RS resources to correspond either to a SS/PBCH block index or to a CSI-RS resource
index as provided by pucch-PathlossReferenceRS-Id in PUCCH-PathlossReferenceRS
- If the UE is provided pathlossReferenceRSs and PUCCH-SpatialRelationInfo, the UE obtains a mapping, by

indexes provided by corresponding values of pucch-PathlossReferenceRS-Id, between a set of pucch-
SpatialRelationInfoId values and a set of referenceSignal values provided by PUCCH-PathlossReferenceRS.
If the UE is provided more than one values for pucch-SpatialRelationInfoId and the UE receives an activation
command [11, TS 38.321] indicating a value of pucch-SpatialRelationInfoId, the UE determines the
referenceSignal value in PUCCH-PathlossReferenceRS through the link to a corresponding pucch-
PathlossReferenceRS-Id index. The UE applies the activation command in the first slot that is after slot
subframe,μ
k + 3⋅ Nslot where k is the slot where the UE would transmit a PUCCH with HARQ-ACK information
for the PDSCH providing the activation command and μ is the SCS configuration for the PUCCH
- If PUCCH-SpatialRelationInfo includes servingCellId indicating a serving cell, the UE receives the RS for
resource index q d on the active DL BWP of the serving cell
- If the UE is provided pathlossReferenceRSs and is not provided PUCCH-SpatialRelationInfo, the UE obtains

the referenceSignal value in PUCCH-PathlossReferenceRS from the pucch-PathlossReferenceRS-Id with
index 0 in PUCCH-PathlossReferenceRS where the RS resource is either on the primary cell or, if provided,
on a serving cell indicated by a value of pathlossReferenceLinking
- If the UE
- is not provided pathlossReferenceRSs, and
- is not provided PUCCH-SpatialRelationInfo, and
- is provided enableDefaultBeamPL-ForPUCCH, and
ETSI
- is not provided coresetPoolIndex value of 1 for any CORESET, or is provided coresetPoolIndex value of
1 for all CORESETs, in ControlResourceSet and no codepoint of a TCI field, if any, in a DCI format of
any search space set maps to two TCI states [5, TS 38.212]
the UE determines a RS resource index ‫ݍ‬ௗ providing a periodic RS resource configured with qcl-Type set
to 'typeD' in the TCI state or the QCL assumption of a CORESET with the lowest index in the active DL
BWP of the primary cell. For a PUCCH transmission over multiple slots, a same ‫ݍ‬ௗ applies to the
PUCCH transmission in each of the multiple slots.
- The parameter Δ F_PUCCH( F ) is a value of deltaF-PUCCH-f0 for PUCCH format 0, deltaF-PUCCH-f1 for
PUCCH format 1, deltaF-PUCCH-f2 for PUCCH format 2, deltaF-PUCCH-f3 for PUCCH format 3, and
deltaF-PUCCH-f4 for PUCCH format 4, if provided; otherwise Δ ሺ‫ܨ‬ሻ = 0. F_PUCCH
- Δ TF,b, f ,c (i) is a PUCCH transmission power adjustment component on active UL BWP b of carrier f of
primary cell c
- For a PUCCH transmission using PUCCH format 0 or PUCCH format 1,
 PUCCH 
N ref
ΔTF,b, f ,c (i) = 10log10   + Δ (i) where
 N PUCCH(i)  UCI
 symb 
PUCCH
- N symb (i ) is a number of PUCCH format 0 symbols or PUCCH format 1 symbols for the PUCCH
transmission as described in clause 9.2.
-
PUCCH
Nref = 2 for PUCCH format 0
-
PUCCH
Nref = Nsymb
slot
for PUCCH format 1
- Δ UCI (i) = 0 for PUCCH format 0
- Δ UCI (i) = 10 log10 (OUCI (i)) for PUCCH format 1, where OUCI (i) is a number of UCI bits in PUCCH
transmission occasion i
- For a PUCCH transmission using PUCCH format 2 or PUCCH format 3 or PUCCH format 4 and for a
number of UCI bits smaller than or equal to 11,
( ( ) )
Δ TF,b, f ,c (i) = 10 log10 K1 ⋅ nHARQ- ACK (i) + OSR (i) + OCSI (i) N RE (i) , where
- K1 = 6
- n HARQ - ACK (i ) is a number of HARQ-ACK information bits that the UE determines as described in clause
9.1.2.1 for Type-1 HARQ-ACK codebook and as described in clause 9.1.3.1 or 9.1.3.3 for Type-2
HARQ-ACK codebook. n HARQ - ACK (i ) is the same as O ACK (i ) as described in clause 9.1.4 for Type-3
HARQ-ACK codebook. If the UE is not provided any of pdsch-HARQ-ACK-Codebook, pdsch-HARQ-
ACK-Codebook-r16, or pdsch-HARQ-ACK-OneShotFeedback, n HARQ - ACK (i ) = 1 if the UE includes a
HARQ-ACK information bit in the PUCCH transmission; otherwise, n HARQ - ACK (i ) = 0
- OSR (i ) is a number of SR information bits that the UE determines as described in clause 9.2.5.1
- OCSI (i) is a number of CSI information bits that the UE determines as described in clause 9.2.5.2
N RE (i) is a number of resource elements determined as NRE(i) = MRB,b, f ,c (i) ⋅ Nsc,ctrl(i) ⋅ Nsymb-UCI,b, f ,c (i) , where
PUCCH RB PUCCH
-
RB
Nsc,ctrl (i) is a number of subcarriers per resource block excluding subcarriers used for DM-RS
PUCCH
transmission, and Nsymb-UCI,b, f ,c (i) is a number of symbols excluding symbols used for DM-RS
transmission, as defined in clause 9.2.5.2, for PUCCH transmission occasion i on active UL BWP b of
carrier f of primary cell c
ETSI
- For a PUCCH transmission using PUCCH format 2 or PUCCH format 3 or PUCCH format 4 and for a
K ⋅BPRE(i )
number of UCI bits larger than 11, Δ TF,b, f ,c (i) = 10log10 2 2 − 1 , where ( )
- K 2 = 2.4
- BPRE( i ) = (O ACK (i ) + OSR (i ) + OCSI (i ) + OCRC (i ) ) N RE (i )
- O ACK (i ) is a number of HARQ-ACK information bits that the UE determines as described in clause
9.1.2.1 for Type-1 HARQ-ACK codebook and as described in clause 9.1.3.1 or 9.1.3.3 for Type-2
HARQ-ACK codebook, or as described in clause 9.1.4 for Type-3 HARQ-ACK codebook. If the UE is
not provided any of pdsch-HARQ-ACK-Codebook, pdsch-HARQ-ACK-Codebook-r16, or pdsch-HARQ-
ACK-OneShotFeedback, OACK = 1 if the UE includes a HARQ-ACK information bit in the PUCCH
transmission; otherwise, OACK = 0
- OSR (i ) is a number of SR information bits that the UE determines as described in clause 9.2.5.1
- OCSI (i) is a number of CSI information bits that the UE determines as described in clause 9.2.5.2
- O CRC ( i ) is a number of CRC bits that the UE determines as described in clause 9.2
- N RE (i) is a number of resource elements that the UE determines as

NRE(i) = MRB,
b, f , c (i) ⋅ Nsc,ctrl(i) ⋅ Nsymb- UCI,b, f ,c (i) , where N sc, ctrl ( i ) is a number of subcarriers per resource block
PUCCH RB PUCCH RB
PUCCH
excluding subcarriers used for DM-RS transmission, and N symb - UCI,b , f , c (i ) is a number of symbols
excluding symbols used for DM-RS transmission, as defined in clause 9.2.5.2, for PUCCH transmission
occasion i on active UL BWP b of carrier f of primary cell c .
- For the PUCCH power control adjustment state g b , f ,c (i, l ) for active UL BWP b of carrier f of primary cell c
and PUCCH transmission occasion i
- δ PUCCH,b , f ,c (i, l ) is a TPC command value included in a DCI format scheduling a PDSCH reception for active
UL BWP b of carrier f of the primary cell c that the UE detects for PUCCH transmission occasion i , or is
jointly coded with other TPC commands in a DCI format 2_2 with CRC scrambled by TPC-PUCCH-RNTI
[5, TS 38.212], as described in clause 11.3
- l ∈ { 0, 1} if the UE is provided twoPUCCH-PC-AdjustmentStates and PUCCH-SpatialRelationInfo and

l = 0 if the UE is not provided twoPUCCH-PC-AdjustmentStates or PUCCH-SpatialRelationInfo
- If the UE obtains a TPC command value from a DCI format scheduling a PDSCH reception and if the UE
is provided PUCCH-SpatialRelationInfo, the UE obtains a mapping, by an index provided by p0-
PUCCH-Id, between a set of pucch-SpatialRelationInfoId values and a set of values for closedLoopIndex
that provide the l value(s). If the UE receives an activation command indicating a value of pucch-
SpatialRelationInfoId, the UE determines the value closedLoopIndex that provides the value of l through
the link to a corresponding p0-PUCCH-Id index
- If the UE obtains one TPC command from a DCI format 2_2 with CRC scrambled by a TPC-PUCCH-
RNTI, the l value is provided by the closed loop indicator field in DCI format 2_2
C (Ci )−1
- g b, f ,c (i, l ) = g b, f ,c (i − i0 , l ) + δ
m= 0
PUCCH,b, f , c (m, l ) is the current PUCCH power control adjustment state l for
active UL BWP b of carrier f of primary cell c and PUCCH transmission occasion i , where
- The δ PUCCH,b, f ,c values are given in Table 7.1.2-1
ETSI
( )
C Ci −1
-  δ PUCCH, b , f ,c ( m, l )
m=0
is a sum of TPC command values in a set C i of TPC command values with
cardinality C (Ci ) that the UE receives between K PUCCH (i − i0 ) − 1 symbols before PUCCH transmission
occasion i − i0 and K PUCCH (i ) symbols before PUCCH transmission occasion i on active UL BWP b of
carrier f of primary cell c for PUCCH power control adjustment state, where i0 > 0 is the smallest
integer for which K PUCCH (i − i0 ) symbols before PUCCH transmission occasion i − i0 is earlier than
K PUCCH (i ) symbols before PUCCH transmission occasion i
- If the PUCCH transmission is in response to a detection by the UE of a DCI format, K PUCCH (i ) is a
number of symbols for active UL BWP b of carrier f of primary cell c after a last symbol of a
corresponding PDCCH reception and before a first symbol of the PUCCH transmission
- If the PUCCH transmission is not in response to a detection by the UE of a DCI format, K PUCCH (i ) is a
slot
number of K PUCCH, min
symbols equal to the product of a number of symbols per slot, Nsymb, and the
minimum of the values provided by k2 in PUSCH-ConfigCommon for active UL BWP b of carrier f of
primary cell c
- If the UE has reached maximum power for active UL BWP b of carrier f of primary cell c at PUCCH
C (C i )− 1
transmission occasion i − i 0 and  δ PUCCH, b , f , c ( m , l ) ≥ 0 , then
m =0
g b , f ,c (i, l ) = g b, f ,c (i − i0 , l )
- If UE has reached minimum power for active UL BWP b of carrier f of primary cell c at PUCCH
C (C i )−1
transmission occasion i − i0 and  δ PUCCH, ,
m=0
b f ,c (m, l ) ≤ 0 , then gb, f , c (i, l ) = gb, f , c (i − i0 , l )
- If a configuration of a PO_PUCCH, b , f , c (qu ) value for a corresponding PUCCH power control adjustment
state l for active UL BWP b of carrier f of primary cell c is provided by higher layers,
- gb, f ,c (k, l ) = 0, k = 0,1,...,i
If the UE is provided PUCCH-SpatialRelationInfo, the UE determines the value of l from the value
of q u based on a pucch-SpatialRelationInfoId value associated with the p0-PUCCH-Id value
corresponding to q u and with the closedLoopIndex value corresponding to l ; otherwise, l = 0
- Else,
- gb, f ,c (0, l ) = ΔPrampup,b, f ,c + δb, f ,c , where l = 0 , and δb, f ,c is
- the TPC command value indicated in a random access response grant corresponding to a PRACH
transmission according to Type-1 random access procedure, or in a random access response grant
corresponding to MsgA transmissions according to Type-2 random access procedure with RAR
message(s) for fallbackRAR, or
- the TPC command value indicated in a successRAR corresponding to MsgA transmissions for
Type-2 random access procedure, or
- the TPC command value in a DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI that
the UE detects in a first PDCCH reception in a search space set provided by
recoverySearchSpaceId if the PUCCH transmission is a first PUCCH transmission after 28
symbols from a last symbol of the first PDCCH reception,
and, if the UE transmits PUCCH on active UL BWP b of carrier f of primary cell c,
ETSI
  0, 
max  
ΔPrampup,b, f ,c =min   PCMAX , f ,c − (PO _ PUCCH ,b, f ,c + PLb, f ,c (qd ) + ΔF _ PUCCH (F ) + ΔTF ,b, f ,c + δb, f ,c )  ;
ΔP 
 rampuprequested ,b, f ,c 
otherwise,
  0,  
max  , 
ΔPrampup ,b, f ,c = min  P
 CMAX , f ,c
(
− PO_PUCCH,b, f ,c + PLb, f ,c ( qd ) )

  where ΔP rampuprequested ,b, f ,c is
 

ΔP rampuprequested ,b , f ,c 
provided by higher layers and corresponds to the total power ramp-up requested by higher layers from
the first to the last preamble for active UL BWP b of carrier f of primary cell c , and
Δ F_PUCCH (F ) corresponds to PUCCH format 0 or PUCCH format 1
Table 7.2.1-1: Mapping of TPC Command Field in a DCI format to accumulated δ PUCCH,b, f ,c values
TPC Command Field Accumulated δ PUCCH,b, f , c [dB]

0 -1
1 0
2 1
3 3
7.3 Sounding reference signals

For SRS, a UE splits a linear value PˆSRS,b, f ,c (i, qs , l ) of the transmit power PSRS,b, f ,c (i, qs , l ) on active UL BWP b of
carrier f of serving cell c equally across the configured antenna ports for SRS.
7.3.1 UE behaviour
If a UE transmits SRS based on a configuration by SRS-ResourceSet on active UL BWP b of carrier f of serving
cell c using SRS power control adjustment state with index l , the UE determines the SRS transmission power
PSRS,b, f ,c (i, qs , l ) in SRS transmission occasion i as
 PCMAX , f ,c (i ), 
PSRS,b , f,c (i, q s , l ) = min  μ  [dBm]
 PO_SRS,b , f ,c (qs ) + 10 log10 (2 ⋅ M SRS,b , f ,c (i )) + α SRS,b , f ,c (qs ) ⋅ PLb , f , c (qd ) + hb , f ,c (i, l )
where,
- PCMAX, f ,c ( i ) is the UE configured maximum output power defined in [8, TS 38.101-1], [8-2, TS38.101-2] and
[TS 38.101-3] for carrier f of serving cell c in SRS transmission occasion i
- PO_SRS,b, f ,c (qs ) is provided by p0 for active UL BWP b of carrier f of serving cell c and SRS resource set
qs provided by SRS-ResourceSet and SRS-ResourceSetId
- MSRS,b, f ,c (i) is a SRS bandwidth expressed in number of resource blocks for SRS transmission occasion i on
active UL BWP b of carrier f of serving cell c and μ is a SCS configuration defined in [4, TS 38.211]
- αSRS,b, f ,c (qs ) is provided by alpha for active UL BWP b of carrier f of serving cell c and SRS resource set
qs
ETSI
- PLb , f ,c ( qd ) is a downlink pathloss estimate in dB calculated by the UE using RS resource index ‫ݍ‬ௗ as
described in clause 7.1.1 for the active DL BWP of serving cell ܿ and SRS resource set ‫ݍ‬௦ [6, TS 38.214]. The
RS resource index ‫ݍ‬ௗ is provided by pathlossReferenceRS associated with the SRS resource set ‫ݍ‬௦ and is either
an ssb-Index providing a SS/PBCH block index or a csi-RS-Index providing a CSI-RS resource index If the UE
is provided enablePL-RS-UpdateForPUSCH-SRS, a MAC CE [11, TS 38.321] can provide by SRS-
PathlossReferenceRS-Id a corresponding RS resource index ‫ݍ‬ௗ for aperiodic or semi-persistent SRS resource set
‫ݍ‬௦
- If the UE is not provided pathlossReferenceRS or SRS-PathlossReferenceRS-Id, or before the UE is provided
dedicated higher layer parameters, the UE calculates PL b , f , c ( q d ) using a RS resource obtained from an
SS/PBCH block with same SS/PBCH block index as the one the UE uses to obtain MIB
- If the UE is provided pathlossReferenceLinking, the RS resource is on a serving cell indicated by a value of

pathlossReferenceLinking
- If the UE
- is not provided pathlossReferenceRS or SRS-PathlossReferenceRS-Id,
- is not provided spatialRelationInfo, and
- is provided enableDefaultBeamPL-ForSRS, and
- is not provided coresetPoolIndex value of 1 for any CORESET, or is provided coresetPoolIndex value of
1 for all CORESETs, in ControlResourceSet and no codepoint of a TCI field, if any, in a DCI format of
any search space set maps to two TCI states [5, TS 38.212]
the UE determines a RS resource index q d providing a periodic RS resource configured with qcl-Type set to
'typeD' in
- the TCI state or the QCL assumption of a CORESET with the lowest index in the active DL BWP, if
CORESETs are provided in the active DL BWP of serving cell ܿ
- the active PDSCH TCI state with lowest ID [6, TS 38.214] in the active DL BWP, if CORESETs are not
provided in the active DL BWP of serving cell ܿ
- For the SRS power control adjustment state for active UL BWP b of carrier f of serving cell c and SRS
transmission occasion i
- hb , f , c ( i , l ) = f b , f , c ( i , l ) , where f b , f ,c (i , l ) is the current PUSCH power control adjustment state as described
in clause 7.1.1, if srs-PowerControlAdjustmentStates indicates a same power control adjustment state for
SRS transmissions and PUSCH transmissions; or
C ( S i )−1
- hb , f , c (i ) = hb , f , c (i − i0 ) + δ
m=0
SRS, b , f , c ( m ) if the UE is not configured for PUSCH transmissions on active UL
BWP b of carrier f of serving cell c, or if srs-PowerControlAdjustmentStates indicates separate power

control adjustment states between SRS transmissions and PUSCH transmissions, and if tpc-Accumulation is
not provided, where
- The δSRS,b, f ,c values are given in Table 7.1.1-1
- δ SRS,b , f ,c ( m) is jointly coded with other TPC commands in a PDCCH with DCI format 2_3, as
described in clause 11.4
C ( S i )− 1
- δ
m=0
SRS, b , f , c (m ) is a sum of TPC command values in a set S i of TPC command values with cardinality
C (S i ) that the UE receives between KSRS(i −i0 ) −1 symbols before SRS transmission occasion i − i 0 and
KSRS(i) symbols before SRS transmission occasion i on active UL BWP b of carrier f of serving cell
c for SRS power control adjustment state, where i 0 > 0 is the smallest integer for which KSRS (i − i0 )
ETSI
symbols before SRS transmission occasion i − i 0 is earlier than KSRS(i) symbols before SRS transmission
occasion i
- if the SRS transmission is aperiodic, KSRS(i) is a number of symbols for active UL BWP b of carrier f
of serving cell c after a last symbol of a corresponding PDCCH triggering the SRS transmission and
before a first symbol of the SRS transmission
- if the SRS transmission is semi-persistent or periodic, KSRS(i) is a number of K SRS, min symbols equal to
the product of a number of symbols per slot, N symb
slot
, and the minimum of the values provided by k2 in
PUSCH-ConfigCommon for active UL BWP b of carrier f of serving cell c
- If the UE has reached maximum power for active UL BWP b of carrier f of serving cell c at SRS
C ( S i )− 1
m=0
SRS, b , f , c ( m ) ≥ 0 , then h b , f , c ( i ) = hb , f , c ( i − i 0 )
- If UE has reached minimum power for active UL BWP b of carrier f of serving cell c at SRS
C ( S i )− 1
m=0
SRS, b , f , c ( m ) ≤ 0 , then h b , f , c ( i ) = hb , f , c ( i − i 0 )
- If a configuration for a PO_SRS, b , f ,c ( q s ) value or for a α SRS , b , f , c ( q s ) value for a corresponding SRS
power control adjustment state l for active UL BWP b of carrier f of serving cell c is provided by
higher layers
- hb, f ,c (k ) = 0, k = 0,1,..., i
- Else
- hb , f , c (0) = ΔPrampup ,b , f , c + δmsg 2,b , f , c
where
δmsg2,b, f ,c is the TPC command value indicated in the random access response grant corresponding
to the random access preamble that the UE transmitted on active UL BWP b of carrier f of the
serving cell c, and
  0,  
max , 
ΔPrampup,b, f ,c = min P
 CMAX, f , c
(
− PO_SRS,b, f ,c (qs ) + 10log10 (2μ ⋅ M SRS,b, f ,c (i)) + αSRS,b, f ,c (qs ) ⋅ PLb, f ,c (qd ) )

 
;
 
ΔPrampuprequested,b, f , c 
where Δ P rampuprequ ested , b , f , c

is provided by higher layers and corresponds to the total power ramp-up
requested by higher layers from the first to the last preamble for active UL BWP b of carrier f of
serving cell c.
- hb, f ,c (i) = δSRS,b, f ,c (i) if the UE is not configured for PUSCH transmissions on active UL BWP b of carrier f
of serving cell c, or if srs-PowerControlAdjustmentStates indicates separate power control adjustment states
between SRS transmissions and PUSCH transmissions, and tpc-Accumulation is provided, and the UE
detects a DCI format 2_3 K SRS, min symbols before a first symbol of SRS transmission occasion i , where
absolute values of δ SRS, b , f ,c
are provided in Table 7.1.1-1
- if srs-PowerControlAdjustmentStates indicates a same power control adjustment state for SRS transmissions
and PUSCH transmissions, the update of the power control adjustment state for SRS transmission occasion i
ETSI
occurs at the beginning of each SRS resource in the SRS resource set q s ; otherwise, the update of the power
control adjustment state SRS transmission occasion i occurs at the beginning of the first transmitted SRS
resource in the SRS resource set q s .
If a UE transmits SRS based on a configuration by SRS-PosResourceSet on active UL BWP ܾ of carrier ݂ of serving

cell ܿ , the UE determines the SRS transmission power ܲௌோௌ ௕ ௙ ௖ ሺ݅ , ‫ݍ‬௦ ሻ in SRS transmission occasion ݅ as
, , ,
 PCMAX , f , c (i ), 
PSRS, b, f,c (i, qs ) = min  μ  [dBm]
 PO_SRS,b , f , c (qs ) + 10 log10 (2 ⋅ M SRS, b, f , c (i )) + α SRS, b, f , c (qs ) ⋅ PLb, f , c (qd )
where,
- ܲ୓ ୗୖୗ ௕ ௙ ௖ ሺ‫ݍ‬௦ ሻ and ߙୗୖୗ ௕ ௙ ௖ ሺ‫ݍ‬௦ ሻ are provided by p0-r16 and alpha-r16 respectively, for active UL BWP ܾ of
_ , , , , , ,
carrier ݂ of serving cell ܿ , and SRS resource set ‫ݍ‬௦ is indicated by SRS-PosResourceSetId from SRS-
PosResourceSet, and
- ܲ‫ܮ‬௕ ௙ ௖ ሺ‫ݍ‬ௗ ሻ is a downlink pathloss estimate in dB calculated by the UE, as described in clause 7.1.1 in case of an
, ,
active DL BWP of a serving cell ܿ , using RS resource indexed ‫ݍ‬ௗ in a serving or non-serving cell for SRS
resource set ‫ݍ‬௦ [6, TS 38.214]. A configuration for RS resource index ‫ݍ‬ௗ associated with SRS resource set ‫ݍ‬௦ is
provided by pathlossReferenceRS-Pos
- if a ssb-IndexNcell is provided, referenceSignalPower is provided by ss-PBCH-BlockPower-r16
- if a dl-PRS-ResourceId is provided, referenceSignalPower is provided by dl-PRS-ResourcePower
If the UE determines that the UE is not able to accurately measure ܲ‫ܮ‬௕ ௙ ௖ ሺ‫ݍ‬ௗ ሻ, or the UE is not provided with
, ,
pathlossReferenceRS-Pos, the UE calculates ܲ‫ܮ‬௕ ௙ ௖ ሺ‫ݍ‬ௗ ሻ using a RS resource obtained from the SS/PBCH block
, ,
of the serving cell that the UE uses to obtain MIB
The UE may indicate a capability for a number of pathloss estimates that the UE can simultaneously maintain for
all SRS resource sets provided by SRS-PosResourceSet in addition to the up to four pathloss estimates that the
UE maintains per serving cell for PUSCH/PUCCH transmissions and for SRS transmissions configured by SRS-
Resource.
7.4 Physical random access channel

A UE determines a transmission power for a physical random access channel (PRACH), PPRACH, b, f ,c ( i ) , on active UL
BWP b of carrier f of serving cell c based on DL RS for serving cell c in transmission occasion i as
{
PPRACH,b, f ,c (i) = min PCMAX, f ,c (i), PPRACH,target,f,c + PLb, f ,c [dBm], }
where PCMAX, f,c (i ) is the UE configured maximum output power defined in [8-1, TS 38.101-1], [8-2, TS 38.101-2] and
[8-3, TS 38.101-3] for carrier f of serving cell c within transmission occasion i , PPRACH, target, f,c is the PRACH target
reception power PREAMBLE_RECEIVED_TARGET_POWER provided by higher layers [11, TS 38.321] for the active
UL BWP b of carrier f of serving cell c, and PLb , f ,c is a pathloss for the active UL BWP b of carrier f based on
the DL RS associated with the PRACH transmission on the active DL BWP of serving cell c and calculated by the UE
in dB as referenceSignalPower – higher layer filtered RSRP in dBm, where RSRP is defined in [7, TS 38.215] and the
higher layer filter configuration is defined in [12, TS 38.331]. If the active DL BWP is the initial DL BWP and for
SS/PBCH block and CORESET multiplexing pattern 2 or 3, as described in clause 13, the UE determines PLb , f ,c based
on the SS/PBCH block associated with the PRACH transmission.
If a PRACH transmission from a UE is not in response to a detection of a PDCCH order by the UE, or is in response to
a detection of a PDCCH order by the UE that triggers a contention based random access procedure, or is associated with
a link recovery procedure where a corresponding index q new is associated with a SS/PBCH block, as described in
clause 6, referenceSignalPower is provided by ss-PBCH-BlockPower.
ETSI
If a PRACH transmission from a UE is in response to a detection of a PDCCH order by the UE that triggers a
contention-free random access procedure and depending on the DL RS that the DM-RS of the PDCCH order is quasi-
collocated with as described in clause 10.1, referenceSignalPower is provided by ss-PBCH-BlockPower or, if the UE is
configured resources for a periodic CSI-RS reception or the PRACH transmission is associated with a link recovery
procedure where a corresponding index q new is associated with a periodic CSI-RS configuration as described in clause
6, referenceSignalPower is obtained by ss-PBCH-BlockPower and powerControlOffsetSS where powerControlOffsetSS
provides an offset of CSI-RS transmission power relative to SS/PBCH block transmission power [6, TS 38.214]. If
powerControlOffsetSS is not provided to the UE, the UE assumes an offset of 0 dB. If the active TCI state for the
PDCCH that provides the PDCCH order includes two RS, the UE expects that one RS is configured with qcl-Type set to
'typeD' and the UE uses the one RS when applying a value provided by powerControlOffsetSS.
If within a random access response window, as described in clause 8.2, the UE does not receive a random access
response that contains a preamble identifier corresponding to the preamble sequence transmitted by the UE, the UE
determines a transmission power for a subsequent PRACH transmission, if any, as described in [11, TS 38.321].
If prior to a PRACH retransmission, a UE changes the spatial domain transmission filter, Layer 1 notifies higher layers
to suspend the power ramping counter as described in [11, TS 38.321].
If due to power allocation to PUSCH/PUCCH/PRACH/SRS transmissions as described in clause 7.5, or due to power
allocation in EN-DC or NE-DC or NR-DC operation, or due to slot format determination as described in clause 11.1, or
due to the PUSCH/PUCCH/PRACH/SRS transmission occasions are in the same slot or the gap between a PRACH
transmission and PUSCH/PUCCH/SRS transmission is small as described in clause 8.1, the UE does not transmit a
PRACH in a transmission occasion, Layer 1 notifies higher layers to suspend the corresponding power ramping counter.
If due to power allocation to PUSCH/PUCCH/PRACH/SRS transmissions as described in clause 7.5, or due to power
allocation in EN-DC or NE-DC or NR-DC operation, the UE transmits a PRACH with reduced power in a transmission
occasion, Layer 1 may notify higher layers to suspend the corresponding power ramping counter.
7.5 Prioritizations for transmission power reductions

For single cell operation with two uplink carriers or for operation with carrier aggregation, if a total UE transmit power
for PUSCH or PUCCH or PRACH or SRS transmissions on serving cells in a frequency range in a respective
transmission occasion i would exceed PˆCMAX (i ) , where PˆCMAX (i ) is the linear value of PCMAX (i ) in transmission
occasion i as defined in [8-1, TS 38.101-1] for FR1 and [8-2, TS38.101-2] for FR2, the UE allocates power to
PUSCH/PUCCH/PRACH/SRS transmissions according to the following priority order (in descending order) so that the
total UE transmit power for transmissions on serving cells in the frequency range is smaller than or equal to PˆCMAX (i )
for that frequency range in every symbol of transmission occasion i . When determining a total transmit power for
serving cells in a frequency range in a symbol of transmission occasion i , the UE does not include power for
transmissions starting after the symbol of transmission occasion i . The total UE transmit power in a symbol of a slot is
defined as the sum of the linear values of UE transmit powers for PUSCH, PUCCH, PRACH, and SRS in the symbol of
the slot.
- PRACH transmission on the PCell
- PUCCH or PUSCH transmissions with higher priority index according to clause 9
- For PUCCH or PUSCH transmissions with same priority index
- PUCCH transmission with HARQ-ACK information, and/or SR, and/or LRR, or PUSCH transmission with
HARQ-ACK information
- PUCCH transmission with CSI or PUSCH transmission with CSI
- PUSCH transmission without HARQ-ACK information or CSI and, for Type-2 random access procedure,
PUSCH transmission on the PCell
- SRS transmission, with aperiodic SRS having higher priority than semi-persistent and/or periodic SRS, or
PRACH transmission on a serving cell other than the PCell
In case of same priority order and for operation with carrier aggregation, the UE prioritizes power allocation for
transmissions on the primary cell of the MCG or the SCG over transmissions on a secondary cell. In case of same
priority order and for operation with two UL carriers, the UE prioritizes power allocation for transmissions on the
ETSI
carrier where the UE is configured to transmit PUCCH. If PUCCH is not configured for any of the two UL carriers, the
UE prioritizes power allocation for transmissions on the non-supplementary UL carrier.
7.6 Dual connectivity

7.6.1 EN-DC
If a UE is configured with a MCG using E-UTRA radio access and with a SCG using NR radio access, the UE is
configured a maximum power PLTE for transmissions on the MCG by p-MaxEUTRA and a maximum power PNR for
transmissions in FR1 on the SCG by p-NR-FR1.
The UE determines a transmission power for the MCG as described in [13, TS 36.213] using PLTE as the maximum
transmission power. The UE determines transmission power for the SCG in FR1 as described in clauses 7.1 through 7.5
using PNR as the maximum transmission power. The UE determines transmission power for the SCG in FR2 as
described in clauses 7.1 through 7.5.
A UE does not expect to be configured for operation with shortened TTI and/or processing time [13, TS 36.213] on a
cell that is included in an EN-DC configuration.
If a UE is configured with PˆLTE + PˆNR > PˆTotal

EN - DC
, where P̂LTE is the linear value of PLTE , P̂NR is the linear value of PNR ,
and P̂Total is the linear value of a configured maximum transmission power for EN-DC operation as defined in [8-3,
EN - DC
TS 38.101-3] for FR1, the UE determines a transmission power for the SCG as follows.
- If the UE is configured with reference TDD configuration for E-UTRA (by tdm-PatternConfig or by tdm-
PatternConfig2 in [13, TS 36.213])
- If the UE does not indicate a capability for dynamic power sharing between E-UTRA and NR for EN-DC,
the UE does not transmit in a slot on the SCG in FR1 when a corresponding subframe on the MCG is an UL
subframe in the reference TDD configuration.
- If the UE indicates a capability for dynamic power sharing between E-UTRA and NR for EN-DC, and does
not indicate a capability tdm-restrictionDualTX-FDD-endc-r16 in [16, TS 38.306], and is configured with
tdm-PatternConfig2, the UE does not transmit on the SCG in FR1 when the UE has overlapped transmission
on a subframe on the MCG.
- If the UE indicates a capability for dynamic power sharing between E-UTRA and NR for EN-DC and
- if UE transmission(s) in subframe i1 of the MCG overlap in time with UE transmission(s) in slot i2 of the
SCG in FR1, and
- if PˆMCG (i1 ) + PˆSCG (i 2 ) > PˆTotal

EN - DC
in any portion of slot i2 of the SCG,
the UE reduces transmission power in any portion of slot i2 of the SCG so that PˆMCG (i1 ) + PˆSCG (i2 ) ≤ PˆTotal EN - DC
in
any portion of slot i2 , where PMCG(i1 ) and PSCG (i 2 ) are the linear values of the total UE transmission powers in
ˆ ˆ
subframe i1 of the MCG and in slot i2 of the SCG in FR1, respectively. The UE is not required to transmit in
any portion of slot i2 of the SCG if PˆSCG (i 2 ) would need to be reduced by more than the value provided by
XSCALE in order for PˆMCG (i1 ) + PˆSCG (i2 ) ≤ PˆTotal
EN - DC
in any portion of slot i2 of the SCG. The UE is required to
transmit in slot i2 of the SCG if PˆSCG (i2 ) would not need to be reduced by more than the value provided by
XSCALE in order for PˆMCG (i1 ) + PˆSCG (i2 ) ≤ PˆTotal
EN - DC
in all portions of slot i2 .
- If the UE does not indicate a capability for dynamic power sharing between E-UTRA and NR for EN-DC, the
UE expects to be configured with reference TDD configuration for E-UTRA by tdm-PatternConfig in [13, TS
36.213].
ETSI
7.6.1A NE-DC
If a UE is configured with an MCG using NR radio access and with a SCG using E-UTRA radio access, the UE is
configured a maximum power PNR for transmissions in FR1 on the MCG by p-NR-FR1 and a maximum power PLTE for
transmissions on the SCG by p-MaxEUTRA.
The UE determines transmission power for the MCG in FR1 as described in clauses 7.1 through 7.5 using PNR as the
maximum transmission power for PCMAX ≤ PNR . The UE determines transmission power for the MCG in FR2 as
described in clauses 7.1 through 7.5.
If the UE is not provided tdd-UL-DL-ConfigurationCommon for the MCG, the UE determines a transmission power for
the SCG as described in [13, TS 36.213] using PLTE as the maximum transmission power.
If at least one symbol of slot i1 of the MCG that is indicated as uplink or flexible by tdd-UL-DL-ConfigurationCommon
or tdd-UL-DL-ConfigurationDedicated overlaps with subframe i2 of the SCG
- for subframe i2 , the UE determines a transmission power for the SCG as described in [13, TS 36.213] using
PLTE as the maximum transmission power
otherwise
- the UE determines a transmission power for the SCG as described in [13, TS 36.213] without considering PLTE
as the maximum transmission power
If a UE is configured with PˆLT E + PˆN R > PˆTNotal

E -D C , where
P̂LTE is the linear value of PLTE , P̂ NR is the linear value of
NE-DC
PNR , and P̂Total is the linear value of a configured maximum transmission power for NE-DC operation as defined in
[8-3, TS 38.101-3] for FR1, the UE determines a transmission power for the MCG as follows
- If the UE is configured with reference TDD configuration for E-UTRA (by tdm-PatternConfigNE-DC-r15 in
[13, TS 36.213])
- If the UE does not indicate a capability for dynamic power sharing between E-UTRA and NR for NE-DC,
the UE does not expect to transmit in a slot on the MCG in FR1 when a corresponding subframe on the SCG
is an UL subframe in the reference TDD configuration.
- If the UE indicates a capability for dynamic power sharing between E-UTRA and NR for NE-DC and
- if the UE transmission(s) in slot i1 of the MCG in FR1 overlap in time with UE transmission(s) in subframe
i2 of the SCG, and
- if PˆMCG ( i1 ) + PˆSCG ( i2 ) > PˆTotal

NE-DC
in any portion of slot i1 of the MCG,
the UE reduces transmission power in any portion of slot i1 of the MCG so that PˆMCG ( i1 ) + PˆSCG ( i2 ) ≤ PˆTotal
NE-DC
in all portions of slot i1 , where PˆMCG (i1 ) and PˆSCG (i2 ) are the linear values of the total UE transmission powers
in slot i1 of the MCG in FR1 and in subframe i2 of the SCG, respectively.
- If the UE does not indicate a capability for dynamic power sharing between E-UTRA and NR for NE-DC, the
UE expects to be configured with reference TDD configuration for E-UTRA (by tdm-PatternConfigNE-DC-r15
in [13, TS 36.213]).
7.6.2 NR-DC
If a UE is configured with an MCG using NR radio access in FR1 or in FR2 and with a SCG using NR radio access in
FR2 or in FR1, respectively, the UE performs transmission power control independently per cell group as described in
clauses 7.1 through 7.5.
If a UE is configured with an MCG and a SCG using NR radio access in FR1 and/or in FR2, the UE is configured a
maximum power ܲMCG for transmissions on the MCG by p-NR-FR1 and/or by p-NR-FR2 and a maximum power ܲSCG
for transmissions on the SCG by p-NR-FR1 and/or by p-NR-FR2 and with an inter-CG power sharing mode by nrdc-
ETSI
PCmode-FR1 for FR1 and/or by nrdc-PCmode-FR2 for FR2. The UE determines a transmission power on the MCG
and a transmission power on the SCG per frequency range.
If a UE is provided semi-static-mode1 for nrdc-PCmode-FR1 or for nrdc-PCmode-FR2, or semi-static-mode2 for nrdc-

PCmode-FR1 or for nrdc-PCmode-FR2, the UE does not expect ܲMCG and SCG to be configured such that MCG +
ௌ஼ீ > ்௢௧௔௟
ேோି஽஼
, where MCG is the linear value of MCG , ௌ஼ீ is the linear value of SCG , and ்௢௧௔௟
ேோି஽஼
is the linear value
of a configured maximum transmission power for NR-DC operation in FR1 or FR2 as defined in [8-3, TS 38.101-3].
If a UE is provided semi-static-mode1 for nrdc-PCmode-FR1 or for nrdc-PCmode-FR2, the UE determines a

transmission power for the MCG or for the SCG as described in clauses 7.1 through 7.5 using MCG or SCG as the
maximum transmission power, respectively.
If a UE is provided semi-static-mode2 for nrdc-PCmode-FR1 or for nrdc-PCmode-FR2
- if the UE is not provided tdd-UL-DL-ConfigurationCommon for the MCG or SCG, the UE determines a
transmission power for the MCG or for the SCG as described in clauses 7.1 through 7.5 using MCG or SCG as the
maximum transmission power, respectively
- if at least one symbol of slot ଵ of the MCG or of the SCG that is indicated as uplink or flexible to a UE by tdd-
UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated, if provided, overlaps with a symbol for
any ongoing transmission overlapping with slot ଶ of the SCG or of the MCG, respectively, the UE determines a
power for the transmission on the SCG or the MCG overlapping with slot ଶ as described in clauses 7.1 through
7.5 using SCG or MCG , respectively, as the maximum transmission power
- otherwise, the UE determines a power for the transmission on SCG or the MCG overlapping with slot ଶ , as
described in [8-3, TS 38.101-3] and in clauses 7.1 through 7.5 without considering SCG or MCG respectively
The UE expects to be provided semi-static-mode2 for nrdc-PCmode-FR1 or for nrdc-PCmode-FR2 only for
synchronous NR-DC operation [10, TS 38.133].
If a UE
- is provided dynamic for nrdc-PCmode-FR1 or for nrdc-PCmode-FR2, and
- indicates a capability to support dynamic power sharing for intra-FR NR DC,
the UE determines a maximum transmission power on the SCG at a first symbol of a transmission occasion on the SCG
by determining transmissions on the MCG that
- are scheduled by DCI formats in PDCCH receptions with a last symbol that is earlier by at least offset from the
first symbol of the transmission occasion on the SCG, or are configured by higher layers, and
- overlap with the transmission occasion on the SCG
the maximum transmission power on the SCG is determined as

NR-DC − ୟୡ୲୳ୟ୪ , if the UE determines transmissions on the MCG with a ୟୡ୲୳ୟ୪ total power
SCG , Total
- MCG MCG
- NR-DC , if the UE does not determine any transmissions on the MCG
Total
where
- offset = max{௣௥௢௖
௠௔௫
,ெ஼ீ , ௣௥௢௖ ,ௌ஼ீ },
௠௔௫
- ௣௥௢௖
௠௔௫
,ெ஼ீ and ௣௥௢௖ ,ௌ஼ீ is the maximum of ௣௥௢௖ ,ଶ , ௣௥௢௖ ,஼ௌூ , ௣௥௢௖ ,௥௘௟௘௔௦௘ , ௣௥௢௖ ,ଶ , and ௣௥௢௖,஼ௌூ based on the
௠௔௫ ௠௨௫ ௠௨௫ ௠௨௫
configurations on the MCG and the SCG, respectively, when the UE indicates the value of 'long' for the
capability,
- ௣௥௢௖
௠௔௫
,ெ஼ீ and ௣௥௢௖ ,ௌ஼ீ is the maximum of ௣௥௢௖ ,ଶ , ௣௥௢௖ ,௥௘௟௘௔௦௘ , ௣௥௢௖ ,ଶ based on the configurations on the MCG
௠௔௫ ௠௨௫ ௠௨௫
and the SCG, respectively, when the UE indicates the value of 'short' for the capability, and
- MCG
ୟୡ୲୳ୟ୪
is the total power for the transmissions on the MCG that overlap with the transmission occasion on the
SCG where MCG ୟୡ୲୳ୟ୪
is determined based on transmissions configured by higher layers and on transmissions
scheduled by DCI formats in PDCCH receptions with a last symbol that is at least offset before the first symbol
of the transmission occasion on the SCG.
ETSI
The UE does not expect to have PUSCH, PUCCH, PRACH, or SRS transmissions on the MCG that
- are scheduled/triggered by DCI formats in PDCCH receptions with a last symbol that is earlier by less than offset
from the first symbol of the transmission occasion on the SCG, and
- overlap with the transmission occasion on the SCG
The UE does not expect to receive a positive TPC command value in a DCI format 2_2 or a DCI format 2_3 in a
PDCCH reception with a last symbol that is less than offset before the first symbol of the transmission occasion on the
SCG, if the transmission on the MCG overlaps with the transmission occasion on the SCG.
The UE is not required to apply a TPC command the UE receives in a DCI format 2_2 or a DCI format 2_3 in a
PDCCH reception with a last symbol that is less than offset before the first symbol of the transmission occasion on the
SCG, if the transmission on the MCG overlaps with the transmission occasion on the SCG.
7.7 Power headroom report

The types of UE power headroom reports are the following. A Type 1 UE power headroom PH that is valid for
PUSCH transmission occasion i on active UL BWP b of carrier f of serving cell c . A Type 3 UE power headroom
PH that is valid for SRS transmission occasion i on active UL BWP b of carrier f of serving cell c.
A UE determines whether a power headroom report for an activated serving cell [11, TS 38.321] is based on an actual
transmission or a reference format based on the higher layer signalling of configured grant and periodic/semi-persistent
sounding reference signal transmissions and downlink control information the UE received until and including the
PDCCH monitoring occasion where the UE detects the first DCI format scheduling an initial transmission of a transport
block since a power headroom report was triggered if the power headroom report is reported on a PUSCH triggered by
the first DCI format. Otherwise, a UE determines whether a power headroom report is based on an actual transmission
or a reference format based on the higher layer signalling of configured grant and periodic/semi-persistent sounding
reference signal transmissions and downlink control information the UE received until the first uplink symbol of a
configured PUSCH transmission minus T'proc,2=Tproc,2 where Tproc,2 is determined according to [6, TS 38.214] assuming
d2,1 = 1, d2,2=0, and with µ DL corresponding to the subcarrier spacing of the active downlink BWP of the scheduling cell
for a configured grant if the power headroom report is reported on the PUSCH using the configured grant.
If a UE
- is configured with two UL carriers for a serving cell, and
- determines a Type 1 power headroom report and a Type 3 power headroom report for the serving cell
the UE
- provides the Type 1 power headroom report if both the Type 1 and Type 3 power headroom reports are based on
respective actual transmissions or on respective reference transmissions
- provides the power headroom report that is based on a respective actual transmission if either the Type 1 report
or the Type 3 report is based on a respective reference transmission
If a UE is configured with a SCG and if phr-ModeOtherCG for a CG indicates 'virtual' then, for power headroom
reports transmitted on the CG, the UE computes PH assuming that the UE does not transmit PUSCH/PUCCH on any
serving cell of the other CG. For NR-DC when both the MCG and the SCG operate either in FR1 or in FR2 and for a
power headroom report transmitted on the MCG or the SCG, the UE computes PH assuming that the UE does not
transmit PUSCH/PUCCH on any serving cell of the SCG or the MCG, respectively.
If the UE is configured with a SCG,
- For computing power headroom for cells belonging to MCG, the term 'serving cell' in this clause refers to
serving cell belonging to the MCG.
- For computing power headroom for cells belonging to SCG, the term 'serving cell' in this clause refers to serving
cell belonging to the SCG. The term 'primary cell' in this clause refers to the PSCell of the SCG.
If the UE is configured with a PUCCH-SCell,
ETSI
- For computing power headroom for cells belonging to primary PUCCH group, the term 'serving cell' in this
clause refers to serving cell belonging to the primary PUCCH group.
- For computing power headroom for cells belonging to secondary PUCCH group, the term 'serving cell' in this
clause refers to serving cell belonging to the secondary PUCCH group. The term 'primary cell' in this clause
refers to the PUCCH-SCell of the secondary PUCCH group.
For a UE configured with EN-DC/NE-DC and capable of dynamic power sharing, if E-UTRA Dual Connectivity PHR
[14, TS 36.321] is triggered and,
- if the duration of NR slot on active UL BWP is different from that of E-UTRA subframe carrying the Dual
Connectivity PHR, the UE provides power headroom of the first NR slot that fully overlaps with the E-UTRA
subframe;
- if the duration of NR slot on active UL BWP is the same as that of E-UTRA subframe carrying the Dual
Connectivity PHR for asynchronous EN-DC/NE-DC [10, TS 38.133], the UE provides power headroom of the
first NR slot that overlaps with the E-UTRA subframe.
7.7.1 Type 1 PH report

If a UE determines that a Type 1 power headroom report for an activated serving cell is based on an actual PUSCH
transmission then, for PUSCH transmission occasion i on active UL BWP b of carrier f of serving cell c , the UE
computes the Type 1 power headroom report as
{
PHtype1,b, f ,c (i, j, qd , l ) = PCMAX, f ,c (i)− PO_PUSCH,b, f ,c ( j ) + 10log10 (2μ ⋅ M RB,b, f ,c (i )) + α b, f ,c ( j ) ⋅ PLb, f ,c (qd ) + Δ TF,b , f ,c (i) + f b, f ,c (i, l )
PUSCH
} [dB]
where PCMAX, f ,c (i ) , PO_PUSCH,b, f , c ( j ) , M RB,b, f , c (i ) ,

PUSCH
αb, f ,c ( j) , PLb, f ,c (qd ) , Δ TF, b, f , c (i ) and f b , f , c (i , l ) are defined in
clause 7.1.1.
If a UE is configured with multiple cells for PUSCH transmissions, where a SCS configuration μ1 on active UL BWP
b 1 of carrier f 1 of serving cell c1 is smaller than a SCS configuration μ 2 on active UL BWP b 2 of carrier f 2 of
serving cell c 2 , and if the UE provides a Type 1 power headroom report in a PUSCH transmission in a slot on active
UL BWP b 1 that overlaps with multiple slots on active UL BWP b 2 , the UE provides a Type 1 power headroom
report for the first PUSCH, if any, on the first slot of the multiple slots on active UL BWP b 2 that fully overlaps with
the slot on active UL BWP b 1 . If a UE is configured with multiple cells for PUSCH transmissions, where a same SCS
configuration on active UL BWP b 1 of carrier f 1 of serving cell c1 and active UL BWP b 2 of carrier f 2 of
serving cell c 2 , and if the UE provides a Type 1 power headroom report in a PUSCH transmission in a slot on active
UL BWP b 1 , the UE provides a Type 1 power headroom report for the first PUSCH, if any, on the slot on active UL
BWP b 2 that overlaps with the slot on active UL BWP b 1 .
If a UE is configured with multiple cells for PUSCH transmissions and provides a Type 1 power headroom report in a
PUSCH transmission with PUSCH repetition Type B having a nominal repetition that spans multiple slots on active UL
BWP b 1 and overlaps with one or more slots on active UL BWP b 2 , the UE provides a Type 1 power headroom
report for the first PUSCH, if any, on the first slot of the one or more slots on active UL BWP b 2 that overlaps with the
multiple slots of the nominal repetition on active UL BWP b 1 .
For a UE configured with EN-DC/NE-DC and capable of dynamic power sharing, if E-UTRA Dual Connectivity PHR
[14, TS 36.321] is triggered, the UE provides power headroom of the first PUSCH, if any, on the determined NR slot as
described in clause 7.7.
If a UE is configured with multiple cells for PUSCH transmissions, the UE does not consider for computation of a Type
1 power headroom report in a first PUSCH transmission that includes an initial transmission of transport block on active
UL BWP b 1 of carrier f 1 of serving cell c1 , a second PUSCH transmission on active UL BWP b 2 of carrier f 2 of
serving cell c2 that overlaps with the first PUSCH transmission if
ETSI
- the second PUSCH transmission is scheduled by a DCI format in a PDCCH received in a second PDCCH
monitoring occasion, and
- the second PDCCH monitoring occasion is after a first PDCCH monitoring occasion where the UE detects the
earliest DCI format scheduling an initial transmission of a transport block after a power headroom report was
triggered
or
- the second PUSCH transmission is after the first uplink symbol of the first PUSCH transmission minus
T'proc,2=Tproc,2 where Tproc,2 is determined according to [6, TS 38.214] assuming d2,1 =1, d2,2=0, and with µ DL
corresponding to the subcarrier spacing of the active downlink BWP of the scheduling cell for a configured grant
if the first PUSCH transmission is on a configured grant after a power headroom report was triggered.
If the UE determines that a Type 1 power headroom report for an activated serving cell is based on a reference PUSCH
transmission then, for PUSCH transmission occasion i on active UL BWP b of carrier f of serving cell c , the UE
computes the Type 1 power headroom report as
~
{
PHtype1,b, f ,c (i, j, qd , l ) = PCMAX, f ,c (i) − PO_PUSCH,b, f ,c ( j) + αb, f ,c ( j ) ⋅ PLb, f ,c (qd ) + fb, f ,c (i, l ) } [dB]
~
where PCMAX, f ,c (i) is computed assuming MPR=0 dB, A-MPR=0 dB, P-MPR=0 dB. ΔTC = 0 dB. MPR, A-MPR, P-MPR
and ΔTC are defined in [8-1, TS 38.101-1], [8-2, TS38.101-2] and [8-3, TS 38.101-3]. The remaining parameters are
defined in clause 7.1.1 where PO_PUSCH,b , f ,c ( j ) and αb, f ,c ( j) are obtained using PO_NOMINAL_ PUSCH, f,c (0) and p0-
PUSCH-AlphaSetId = 0, PL b , f , c ( q d ) is obtained using pusch-PathlossReferenceRS-Id = 0, and l = 0 .
If a UE is configured with two UL carriers for a serving cell and the UE determines a Type 1 power headroom report
for the serving cell based on a reference PUSCH transmission, the UE computes a Type 1 power headroom report for
the serving cell assuming a reference PUSCH transmission on the UL carrier provided by pusch-Config. If the UE is
provided pusch-Config for both UL carriers, the UE computes a Type 1 power headroom report for the serving cell
assuming a reference PUSCH transmission on the UL carrier provided by pucch-Config. If pucch-Config is not
provided to the UE for any of the two UL carriers, the UE computes a Type 1 power headroom report for the serving
cell assuming a reference PUSCH transmission on the non-supplementary UL carrier.

This clause is reserved.

If a UE determines that a Type 3 power headroom report for an activated serving cell is based on an actual SRS
transmission then, for SRS transmission occasion i on active UL BWP b of carrier f of serving cell and if the
UE is not configured for PUSCH transmissions on carrier f of serving cell and the resource for the SRS
transmission is provided by SRS-Resource, the UE computes a Type 3 power headroom report as
PH type3,b , f ,c (i, q s ) = PCMAX , f ,c (i )− {P O_SRS, b , f ,c ( q s ) + 10 log10 (2 μ ⋅ M SRS,b , f ,c (i )) + α SRS,b , f ,c ( q s ) ⋅ PLb , f ,c (qd ) + hb , f ,c (i ) }

[dB]
where PCMAX , f , c ( i ) , PO_SRS, b , f ,c ( q s ) , M SRS, b , f , c (i ) , αSRS,b, f ,c (qs ) , PL b , f , c ( q d ) and hb , f , c ( i ) are defined in clause
7.3.1 with corresponding values provided by SRS-ResourceSet.
If the UE determines that a Type 3 power headroom report for an activated serving cell is based on a reference SRS
transmission then, for SRS transmission occasion i on UL BWP b of carrier f of serving cell , and if the UE is
not configured for PUSCH transmissions on UL BWP b of carrier f of serving cell and a resource for the
reference SRS transmission is provided by SRS-Resource, the UE computes a Type 3 power headroom report as
~
{
PHtype3,b, f ,c (i, qs ) = PCMAX, f ,c (i) − PO_SRS,b, f ,c (qs ) + αSRS,b, f ,c (qs ) ⋅ PLb, f ,c (qd ) + hb, f ,c (i) } [dB]
ETSI
where qs is an SRS resource set corresponding to SRS-ResourceSetId = 0 for UL BWP b and PO_SRS,b, f ,c (qs ) ,
α SRS, f ,c (qs ) , PLb, f ,c (qd ) and hb, f , c (i) are defined in clause 7.3.1 with corresponding values obtained from SRS-
~
ResourceSetId = 0 for UL BWP b . PCMAX , f ,c ( i ) is computed assuming MPR=0 dB, A-MPR=0 dB, P-MPR=0 dB
and ΔTC =0 dB. MPR, A-MPR, P-MPR and ΔTC are defined in [8-1, TS 38.101-1], [8-2, TS38.101-2] and [8-3, TS
38.101-3].
If a UE is configured with two UL carriers for a serving cell and the UE determines a Type 3 power headroom report
for the serving cell based on a reference SRS transmission and a resource for the reference SRS is provided by SRS-
Resource, the UE computes a Type 3 power headroom report for the serving cell assuming a reference SRS
transmission on the UL carrier provided by pucch-Config. If pucch-Config is not provided to the UE for any of the two
UL carriers, the UE computes a Type 3 power headroom report for the serving cell assuming a reference SRS
transmission on the non-supplementary UL carrier.
8 Random access procedure

Prior to initiation of the physical random access procedure, Layer 1 receives from higher layers a set of SS/PBCH block
indexes and provides to higher layers a corresponding set of RSRP measurements.
Prior to initiation of the physical random access procedure, Layer 1 may receive from higher layers an indication to
perform a Type-1 random access procedure, as described in clauses 8.1 through 8.4, or a Type-2 random access
procedure as described in clauses 8.1 through 8.2A.
Prior to initiation of the physical random access procedure, Layer 1 receives the following information from the higher
layers:
- Configuration of physical random access channel (PRACH) transmission parameters (PRACH preamble format,
time resources, and frequency resources for PRACH transmission).
- Parameters for determining the root sequences and their cyclic shifts in the PRACH preamble sequence set
(index to logical root sequence table, cyclic shift ( N CS ), and set type (unrestricted, restricted set A, or restricted
set B)).
From the physical layer perspective, the Type-1 L1 random access procedure includes the transmission of random
access preamble (Msg1) in a PRACH, random access response (RAR) message with a PDCCH/PDSCH (Msg2), and
when applicable, the transmission of a PUSCH scheduled by a RAR UL grant, and PDSCH for contention resolution.
From the physical layer perspective, the Type-2 L1 random access procedure includes the transmission of random
access preamble in a PRACH and of a PUSCH (MsgA) and the reception of a RAR message with a PDCCH/PDSCH
(MsgB), and when applicable, the transmission of a PUSCH scheduled by a fallback RAR UL grant, and PDSCH for
contention resolution.
If a random access procedure is initiated by a PDCCH order to the UE, a PRACH transmission is with a same SCS as a
PRACH transmission initiated by higher layers.
If a UE is configured with two UL carriers for a serving cell and the UE detects a PDCCH order, the UE uses the
UL/SUL indicator field value from the detected PDCCH order to determine the UL carrier for the corresponding
PRACH transmission.
8.1 Random access preamble

Physical random access procedure is triggered upon request of a PRACH transmission by higher layers or by a PDCCH
order. A configuration by higher layers for a PRACH transmission includes the following:
- A configuration for PRACH transmission [4, TS 38.211].
- A preamble index, a preamble SCS, PPRACH,target , a corresponding RA-RNTI, and a PRACH resource.
ETSI
A PRACH is transmitted using the selected PRACH format with transmission power PPRACH,b , f , c (i ) , as described in
clause 7.4, on the indicated PRACH resource.
For Type-1 random access procedure, a UE is provided a number

of SS/PBCH block indexes associated with one
PRACH occasion and a number of contention based preambles per SS/PBCH block index per valid PRACH occasion
by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.
For Type-2 random access procedure with common configuration of PRACH occasions with Type-1 random access
procedure, a UE is provided a number
of SS/PBCH block indexes associated with one PRACH occasion by ssb-
perRACH-OccasionAndCB-PreamblesPerSSB and a number of contention based preambles per SS/PBCH block
index per valid PRACH occasion by msgA-CB-PreamblesPerSSB-PerSharedRO. The PRACH transmission can be on a
subset of PRACH occasions associated with a same SS/PBCH block index within an SSB-RO mapping cycle for a UE
provided with a PRACH mask index by msgA-SSB-SharedRO-MaskIndex according to [11, TS 38.321].
For Type-2 random access procedure with separate configuration of PRACH occasions with Type-1 random access
procedure, a UE is provided a number
of SS/PBCH block indexes associated with one PRACH occasion and a
number of contention based preambles per SS/PBCH block index per valid PRACH occasion by msgA-SSB-
PerRACH-OccasionAndCB-PreamblesPerSSB when provided; otherwise, by ssb-perRACH-OccasionAndCB-
PreamblesPerSSB.
For Type-1 random access procedure, or for Type-2 random access procedure with separate configuration of PRACH
occasions from Type 1 random access procedure, if
< 1, one SS/PBCH block index is mapped to 1⁄
consecutive
valid PRACH occasions and contention based preambles with consecutive indexes associated with the SS/PBCH
block index per valid PRACH occasion start from preamble index 0. If
≥ 1, contention based preambles with
consecutive indexes associated with SS/PBCH block index , 0 ≤ ≤
− 1, per valid PRACH occasion start from
preamble index ⋅
୮୰ୣୟ୫ୠ୪ୣ
୲୭୲ୟ୪ ୲୭୲ୟ୪
⁄
where
୮୰ୣୟ୫ୠ୪ୣ is provided by totalNumberOfRA-Preambles for Type-1 random
access procedure, or by msgA-TotalNumberOfRA-Preambles for Type-2 random access procedure with separate
configuration of PRACH occasions from a Type 1 random access procedure, and is an integer multiple of
.
For Type-2 random access procedure with common configuration of PRACH occasions with Type-1 random access
procedure, if
consecutive valid PRACH occasions and
contention based preambles with consecutive indexes associated with the SS/PBCH block index per valid PRACH
occasion start from preamble index . If
≥ 1, contention based preambles with consecutive indexes associated
with SS/PBCH block index , 0 ≤ ≤
− 1, per valid PRACH occasion start from preamble index
⋅
୲୭୲ୟ୪ ⁄
+ , where
୲୭୲ୟ୪ is provided by totalNumberOfRA-Preambles for Type-1 random access
procedure.
For link recovery, a UE is provided

SS/PBCH block indexes associated with one PRACH occasion by ssb-perRACH-
Occasion in BeamFailureRecoveryConfig. For a dedicated RACH configuration provided by RACH-ConfigDedicated,
if cfra is provided, a UE is provided
SS/PBCH block indexes associated with one PRACH occasion by ssb-
perRACH-Occasion in occasions. If
consecutive valid PRACH
occasions. If
≥ 1, all consecutive
SS/PBCH block indexes are associated with one PRACH occasion.
SS/PBCH block indexes provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon are mapped to

valid PRACH occasions in the following order where the parameters are described in [4, TS 38.211].
- First, in increasing order of preamble indexes within a single PRACH occasion
- Second, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions
- Third, in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot
- Fourth, in increasing order of indexes for PRACH slots
An association period, starting from frame 0, for mapping SS/PBCH block indexes to PRACH occasions is the smallest
SSB
value in the set determined by the PRACH configuration period according Table 8.1-1 such that NTx SS/PBCH block
SSB
indexes are mapped at least once to the PRACH occasions within the association period, where a UE obtains NTx from
the value of ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon. If after an integer number of SS/PBCH
block indexes to PRACH occasions mapping cycles within the association period there is a set of PRACH occasions or
ETSI
SSB
PRACH preambles that are not mapped to NTx SS/PBCH block indexes, no SS/PBCH block indexes are mapped to
the set of PRACH occasions or PRACH preambles. An association pattern period includes one or more association
periods and is determined so that a pattern between PRACH occasions and SS/PBCH block indexes repeats at most
every 160 msec. PRACH occasions not associated with SS/PBCH block indexes after an integer number of association
periods, if any, are not used for PRACH transmissions.
For a PRACH transmission triggered by a PDCCH order, the PRACH mask index field [5, TS 38.212], if the value of
the random access preamble index field is not zero, indicates the PRACH occasion for the PRACH transmission where
the PRACH occasions are associated with the SS/PBCH block index indicated by the SS/PBCH block index field of the
PDCCH order.
For a PRACH transmission triggered by higher layers, if ssb-ResourceList is provided, the PRACH mask index is
indicated by ra-ssb-OccasionMaskIndex which indicates the PRACH occasions for the PRACH transmission where the
PRACH occasions are associated with the selected SS/PBCH block index.
The PRACH occasions are mapped consecutively per corresponding SS/PBCH block index. The indexing of the
PRACH occasion indicated by the mask index value is reset per mapping cycle of consecutive PRACH occasions per
SS/PBCH block index. The UE selects for a PRACH transmission the PRACH occasion indicated by PRACH mask
index value for the indicated SS/PBCH block index in the first available mapping cycle.
For the indicated preamble index, the ordering of the PRACH occasions is
- First, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions
- Second, in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH
slot
- Third, in increasing order of indexes for PRACH slots
For a PRACH transmission triggered upon request by higher layers, a value of ra-OccasionList [12, TS 38.331], if
csirs-ResourceList is provided, indicates a list of PRACH occasions for the PRACH transmission where the PRACH
occasions are associated with the selected CSI-RS index indicated by csi-RS. The indexing of the PRACH occasions
indicated by ra-OccasionList is reset per association pattern period.
Table 8.1-1: Mapping between PRACH configuration period and SS/PBCH block to PRACH occasion
association period
Association period (number of PRACH
PRACH configuration period (msec)
configuration periods)
10 {1, 2, 4, 8, 16}
20 {1, 2, 4, 8}
40 {1, 2, 4}
80 {1, 2}
160 {1}
For paired spectrum or supplementary uplink band all PRACH occasions are valid.
For unpaired spectrum,
- if a UE is not provided tdd-UL-DL-ConfigurationCommon, a PRACH occasion in a PRACH slot is valid if it

does not precede a SS/PBCH block in the PRACH slot and starts at least
୥ୟ୮ symbols after a last SS/PBCH
block reception symbol, where
୥ୟ୮ is provided in Table 8.1-2 and, if channelAccessMode = semistatic is
provided, does not overlap with a set of consecutive symbols before the start of a next channel occupancy time
where the UE does not transmit [15, TS 37.213].
- the candidate SS/PBCH block index of the SS/PBCH block corresponds to the SS/PBCH block index
provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon , as described in clause 4.1
- If a UE is provided tdd-UL-DL-ConfigurationCommon, a PRACH occasion in a PRACH slot is valid if
- it is within UL symbols, or
ETSI
- it does not precede a SS/PBCH block in the PRACH slot and starts at least
୥ୟ୮ symbols after a last
downlink symbol and at least
୥ୟ୮ symbols after a last SS/PBCH block symbol, where
୥ୟ୮ is provided in
Table 8.1-2, and if channelAccessMode = semistatic is provided, does not overlap with a set of consecutive
symbols before the start of a next channel occupancy time where there shall not be any transmissions, as
described in [15, TS 37.213]
- the candidate SS/PBCH block index of the SS/PBCH block corresponds to the SS/PBCH block index
provided by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon, as described in clause 4.1.
For preamble format B4 [4, TS 38.211],

୥ୟ୮ =0N gap =0.
Table 8.1-2: ܏‫ ܘ܉‬values for different preamble SCS
Preamble SCS ࡺ܏‫ܘ܉‬

1.25 kHz or 5 kHz 0
15 kHz or 30 kHz or 60 kHz or 120 kHz 2
If a random access procedure is initiated by a PDCCH order, the UE, if requested by higher layers, transmits a PRACH
in the selected PRACH occasion, as described in [11, TS 38.321], for which a time between the last symbol of the
PDCCH order reception and the first symbol of the PRACH transmission is larger than or equal to
் ଶ +
∆୆୛୔ୗ୵୧୲ୡ୦୧୬୥ + ∆ୈୣ୪ୟ୷ + ୱ୵୧୲ୡ୦ msec, where
,
-
் ଶ is a time duration of
ଶ symbols corresponding to a PUSCH preparation time for UE processing capability
,
1 [6, TS 38.214] assuming corresponds to the smallest SCS configuration between the SCS configuration of
the PDCCH order and the SCS configuration of the corresponding PRACH transmission
- ∆୆୛୔ୗ୵୧୲ୡ୦୧୬୥ = 0 if the active UL BWP does not change and ∆୆୛୔ୗ୵୧୲ୡ୦୧୬୥ is defined in [10, TS 38.133]
otherwise
- ∆ୈୣ୪ୟ୷ = 0.5 msec for FR1 and ∆ୈୣ୪ୟ୷ = 0.25 msec for FR2
- ୱ୵୧୲ୡ୦ is a switching gap duration as defined in [6, TS 38.214]
For a PRACH transmission using 1.25 kHz or 5 kHz SCS, the UE determines
ଶ assuming SCS configuration = 0.
For single cell operation or for operation with carrier aggregation in a same frequency band, a UE does not transmit
PRACH and PUSCH/PUCCH/SRS in a same slot or when a gap between the first or last symbol of a PRACH
transmission in a first slot is separated by less than
symbols from the last or first symbol, respectively, of a
PUSCH/PUCCH/SRS transmission in a second slot where
= 2 for = 0 or =1,
= 4 for = 2 or = 3, and
is the SCS configuration for the active UL BWP. For a PUSCH transmission with repetition Type B, this applies to each
actual repetition for PUSCH transmission [6, TS 38.214].
8.1A PUSCH for Type-2 random access procedure

For a Type-2 random access procedure, a UE transmits a PUSCH, when applicable, after transmitting a PRACH. The
UE encodes a transport block provided for the PUSCH transmission using redundancy version number 0. The PUSCH
transmission is after the PRACH transmission by at least
symbols where
= 2 for = 0 or = 1,
= 4 for = 2
or = 3, and is the SCS configuration for the active UL BWP.
A UE does not transmit a PUSCH in a PUSCH occasion if the PUSCH occasion associated with a DMRS resource is
not mapped to a preamble of valid PRACH occasions or if the associated PRACH preamble is not transmitted as
described in clause 7.5 or clause 11.1. A UE can transmit a PRACH preamble in a valid PRACH occasion if the
PRACH preamble is not mapped to a valid PUSCH occasion.
A mapping between one or multiple PRACH preambles and a PUSCH occasion associated with a DMRS resource is
per PUSCH configuration.
A UE determines time resources and frequency resources for PUSCH occasions in an active UL BWP from msgA-
PUSCH-Config for the active UL BWP. If the active UL BWP is not the initial UL BWP and msgA-PUSCH-Config is
not provided for the active UL BWP, the UE uses the msgA-PUSCH-Config provided for the initial UL BWP.
ETSI
A UE determines a first interlace or first RB for a first PUSCH occasion in an active UL BWP respectively from
interlaceIndexFirstPO-MsgA-PUSCH or from frequencyStartMsgA-PUSCH that provides an offset, in number of RBs
in the active UL BWP, from a first RB of the active UL BWP. A PUSCH occasion includes a number of interlaces or a
number of RBs provided by nrofInterlacesPerMsgA-PO or by nrofPRBs-perMsgA-PO, respectively. Consecutive
PUSCH occasions in the frequency domain of an UL BWP are separated by a number of RBs provided by
guardBandMsgA-PUSCH. A number
݂ of PUSCH occasions in the frequency domain of an UL BWP is provided by
nrofMsgA-PO-FDM.
For operation with shared spectrum channel access, if the PUSCH occasion is provided by higher layer parameters
frequencyStartMsgA-PUSCH and nrofPRBs-perMsgA-PO, the UE expects a PUSCH occasion to be confined within the
same RB set as the corresponding PRACH transmission.
For operation with shared spectrum channel access, if the PUSCH occasion is provided by higher layer parameters
interlaceIndexFirstPO-MsgA-PUSCH and nrofInterlacesPerMsgA-PO, the RB set for the PUSCH occasion in the
active UL BWP is the same RB set as the corresponding PRACH transmission. The UE assumes that the RB set is
defined as when the UE is not provided intraCellGuardBandsPerSCS for an UL carrier as described in clause 7 of [6,
TS 38.214].
If a UE does not have dedicated RRC configuration, or has an initial UL BWP as an active UL BWP, or is not provided
startSymbolAndLengthMsgA-PO, msgA-PUSCH-timeDomainAllocation provides a SLIV and a PUSCH mapping type
for a PUSCH transmission by indicating
- one of the first maxNrofUL-Allocations values from PUSCH-TimeDomainResourceAllocationList, if PUSCH-

TimeDomainResourceAllocationList is provided in PUSCH-ConfigCommon
- one of the entries from table 6.1.2.1.1-2 or table 6.1.2.1.1-3 in [6, TS 38.214], if PUSCH-
TimeDomainResourceAllocationList is not provided in PUSCH-ConfigCommon
else, the UE is provided a SLIV by startSymbolAndLengthMsgA-PO, and a PUSCH mapping type by

mappingTypeMsgA-PUSCH for a PUSCH transmission.
For mapping one or multiple preambles of a PRACH slot to a PUSCH occasion associated with a DMRS resource, a UE
determines a first slot for a first PUSCH occasion in an active UL BWP from msgA-PUSCH-TimeDomainOffset that
provides an offset, in number of slots in the active UL BWP, relative to the start of a PUSCH slot including the start of
each PRACH slot. The UE does not expect to have a PRACH preamble transmission and a PUSCH transmission with a
msgA in a PRACH slot or in a PUSCH slot, or to have overlapping msgA PUSCH occasions for a MsgA PUSCH
configuration. The UE expects that a first PUSCH occasion in each slot has a same SLIV for a PUSCH transmission
that is provided by startSymbolAndLengthMsgA-PO or msgA-PUSCH-timeDomainAllocation [6, TS 38.214].
Consecutive PUSCH occasions within each slot are separated by guardPeriodMsgA-PUSCH symbols and have same
duration. A number
‫ ݐ‬of time domain PUSCH occasions in each slot is provided by nrofMsgA-PO-perSlot and a
number
‫ ݏ‬of consecutive slots that include PUSCH occasions is provided by nrofSlotsMsgA-PUSCH.
A UE is provided a DMRS configuration for a PUSCH transmission in a PUSCH occasion in an active UL BWP by
msgA-DMRS-Config.
A UE is provided an MCS for data information in a PUSCH transmission for a PUSCH occasion by msgA-MCS.
For a PUSCH transmission with frequency hopping in a slot, when indicated by msgA-intraSlotFrequencyHopping for
the active UL BWP, the frequency offset for the second hop [6, TS 38.214] is determined as described in clause 8.3,
Table 8.3-1 using msgA-HoppingBits instead of
୙୐ ୦୭୮ . If guardPeriodMsgA-PUSCH is provided, a first symbol of the
,
second hop is separated by guardPeriodMsgA-PUSCH symbols from the end of a last symbol of the first hop;
otherwise, there is no time separation of the PUSCH transmission before and after frequency hopping. If a UE is
provided with useInterlacePUCCH-PUSCH in BWP-UplinkCommon, the UE shall transmit PUSCH without frequency
hopping. A PUSCH transmission uses a same spatial filter as an associated PRACH transmission.
A UE determines whether or not to apply transform precoding for a PUSCH transmission as described in [6, TS
38.214].
A PUSCH occasion for PUSCH transmission is defined by a frequency resource and a time resource, and is associated
with a DMRS resource. The DMRS resources are provided by msgA-DMRS-Config.
Each consecutive number of

preamble preamble indexes from valid PRACH occasions in a PRACH slot
ETSI
- first, in increasing order of preamble indexes within a single PRACH occasion
- second, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions
- third, in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot
are mapped to a valid PUSCH occasion and the associated DMRS resource
- first, in increasing order of frequency resource indexes ௜ௗ for frequency multiplexed PUSCH occasions
- second, in increasing order of DMRS resource indexes within a PUSCH occasion, where a DMRS resource
index ௜ௗ is determined first in an ascending order of a DMRS port index and second in an ascending order
of a DMRS sequence index [4, TS 38.211]
- third, in increasing order of time resource indexes ௜ௗ for time multiplexed PUSCH occasions within a PUSCH
slot
- fourth, in increasing order of indexes for

‫ ݏ‬PUSCH slots
where
preamble = preamble ⁄PUSCH , preamble is a total number of valid PRACH occasions per association pattern
period multiplied by the number of preambles per valid PRACH occasion provided by rach-
ConfigCommonTwoStepRA, and PUSCH is a total number of valid PUSCH occasions per PUSCH configuration per
association pattern period multiplied by the number of DMRS resource indexes per valid PUSCH occasion provided by
msgA-DMRS-Config.
A PUSCH occasion is valid if it does not overlap in time and frequency with any valid PRACH occasion associated
with either a Type-1 random access procedure or a Type-2 random access procedure. Additionally, for unpaired
spectrum and for SS/PBCH blocks with indexes provided by ssb-PositionsInBurst in SIB1 or by
ServingCellConfigCommon
- if a UE is not provided tdd-UL-DL-ConfigurationCommon, a PUSCH occasion is valid if the PUSCH occasion
- does not precede a SS/PBCH block in the PUSCH slot, and
- starts at least
gap symbols after a last SS/PBCH block symbol, where
gap is provided in Table 8.1-2 and, if
channelAccessMode = semistatic is provided, does not overlap with a set of consecutive symbols before the
start of a next channel occupancy time where the UE does not transmit [15, TS 37.213].
- if a UE is provided tdd-UL-DL-ConfigurationCommon, a PUSCH occasion is valid if the PUSCH occasion
- is within UL symbols, or
- does not precede a SS/PBCH block in the PUSCH slot, and
- starts at least
gap symbols after a last downlink symbol and at least
gap symbols after a last SS/PBCH block
symbol, where
gap is provided in Table 8.1-2 and, if channelAccessMode = semistatic is provided, does not
overlap with a set of consecutive symbols before the start of a next channel occupancy time where the UE
does not transmit [15, TS 37.213].
8.2 Random access response - Type-1 random access procedure

In response to a PRACH transmission, a UE attempts to detect a DCI format 1_0 with CRC scrambled by a
corresponding RA-RNTI during a window controlled by higher layers [11, TS 38.321]. The window starts at the first
symbol of the earliest CORESET the UE is configured to receive PDCCH for Type1-PDCCH CSS set, as defined in
clause 10.1, that is at least one symbol, after the last symbol of the PRACH occasion corresponding to the PRACH
transmission, where the symbol duration corresponds to the SCS for Type1-PDCCH CSS set as defined in clause 10.1.
The length of the window in number of slots, based on the SCS for Type1-PDCCH CSS set, is provided by ra-
ResponseWindow.
If the UE detects the DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI and LSBs of a SFN field in
the DCI format 1_0, if included and applicable, are same as corresponding LSBs of the SFN where the UE transmitted
ETSI
PRACH, and the UE receives a transport block in a corresponding PDSCH within the window, the UE passes the
transport block to higher layers. The higher layers parse the transport block for a random access preamble identity
(RAPID) associated with the PRACH transmission. If the higher layers identify the RAPID in RAR message(s) of the
transport block, the higher layers indicate an uplink grant to the physical layer. This is referred to as random access
response (RAR) UL grant in the physical layer.
If the UE does not detect the DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI within the window,
or if the UE detects the DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI within the window and
LSBs of a SFN field in the DCI format 1_0, if included and applicable, are not same as corresponding LSBs of the SFN
where the UE transmitted PRACH, or if the UE does not correctly receive the transport block in the corresponding
PDSCH within the window, or if the higher layers do not identify the RAPID associated with the PRACH transmission
from the UE, the higher layers can indicate to the physical layer to transmit a PRACH. If requested by higher layers, the
UE is expected to transmit a PRACH no later than NT,1 + 0.75 msec after the last symbol of the window, or the last
symbol of the PDSCH reception, where NT,1 is a time duration of N1 symbols corresponding to a PDSCH processing
time for UE processing capability 1 assuming μ corresponds to the smallest SCS configuration among the SCS
configurations for the PDCCH carrying the DCI format 1_0, the corresponding PDSCH when additional PDSCH DM-
RS is configured, and the corresponding PRACH. For μ = 0 , the UE assumes N 1,0 = 14 [6, TS 38.214]. For a PRACH
transmission using 1.25 kHz or 5 kHz SCS, the UE determines N1 assuming SCS configuration μ = 0 .
If the UE detects a DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI and LSBs of a SFN field in
the DCI format 1_0, if included and applicable, are same as corresponding LSBs of the SFN where the UE transmitted
the PRACH, and the UE receives a transport block in a corresponding PDSCH, the UE may assume same DM-RS
antenna port quasi co-location properties, as described in [6, TS 38.214], as for a SS/PBCH block or a CSI-RS resource
the UE used for PRACH association, as described in clause 8.1, regardless of whether or not the UE is provided TCI-
State for the CORESET where the UE receives the PDCCH with the DCI format 1_0.
If the UE attempts to detect the DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI in response to a
PRACH transmission initiated by a PDCCH order that triggers a contention-free random access procedure for the
SpCell [11, TS 38.321], the UE may assume that the PDCCH that includes the DCI format 1_0 and the PDCCH order
have same DM-RS antenna port quasi co-location properties. If the UE attempts to detect the DCI format 1_0 with CRC
scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order that
triggers a contention-free random access procedure for a secondary cell, the UE may assume the DM-RS antenna port
quasi co-location properties of the CORESET associated with the Type1-PDCCH CSS set for receiving the PDCCH
that includes the DCI format 1_0.
A RAR UL grant schedules a PUSCH transmission from the UE. The contents of the RAR UL grant, starting with the
MSB and ending with the LSB, are given in Table 8.2-1.
If the value of the frequency hopping flag is 0, the UE transmits the PUSCH without frequency hopping; otherwise, the
UE transmits the PUSCH with frequency hopping.
The UE determines the MCS of the PUSCH transmission from the first sixteen indexes of the applicable MCS index
table for PUSCH as described in [6, TS 38.214].
The TPC command value δ msg 2,b, f ,c is used for setting the power of the PUSCH transmission, as described in clause
7.1.1, and is interpreted according to Table 8.2-2.
The CSI request field is reserved.
The ChannelAccess-CPext field indicates a channel access type and CP extension for operation with shared spectrum
channel access [15, TS 37.213] as defined in Table 7.3.1.1.1-4 in TS 38.212 or Table 7.3.1.1.1-4A in TS 38.212 if
ChannelAccessMode-r16 = "semistatic" is provided.as defined in Table 7.3.1.1.1-4 in TS 38.212.
ETSI
Table 8.2-1: Random Access Response Grant Content field size

RAR grant field Number of bits
Frequency hopping flag 1
14, for operation without shared spectrum channel access
PUSCH frequency resource allocation
12, for operation with shared spectrum channel access
PUSCH time resource allocation 4
MCS 4
TPC command for PUSCH 3
CSI request 1
0, for operation without shared spectrum channel access
ChannelAccess-CPext
2, for operation with shared spectrum channel access
Table 8.2-2: TPC Command δ msg 2,b, f ,c for PUSCH
TPC Command Value (in dB)

0 -6
1 -4
2 -2
3 0
4 2
5 4
6 6
7 8
Unless the UE is configured a SCS, the UE receives subsequent PDSCH using same SCS as for the PDSCH reception
providing the RAR message.
If the UE does not detect the DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI within the window,
or if the UE detects the DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI within the window and
the LSBs of a SFN field in the DCI format 1_0, if included and applicable, are not same as corresponding LSBs of the
SFN where the UE transmitted the PRACH, or the UE does not correctly receive a corresponding transport block within
the window, the UE procedure is as described in [11, TS 38.321].
8.2A Random access response - Type-2 random access procedure

In response to a transmission of a PRACH and a PUSCH, or to a transmission of only a PRACH if the PRACH
preamble is mapped to a valid PUSCH occasion, a UE attempts to detect a DCI format 1_0 with CRC scrambled by a
corresponding MsgB-RNTI during a window controlled by higher layers [11, TS 38.321]. The window starts at the first
symbol of the earliest CORESET the UE is configured to receive PDCCH for Type1-PDCCH CSS set, as defined in
clause 10.1, that is at least one symbol, after the last symbol of the PUSCH occasion corresponding to the PRACH
transmission, where the symbol duration corresponds to the SCS for Type1-PDCCH CSS set. The length of the window
in number of slots, based on the SCS for Type1-PDCCH CSS set, is provided by msgB-ResponseWindow.
In response to a transmission of a PRACH, if the PRACH preamble is not mapped to a valid PUSCH occasion, a UE
attempts to detect a DCI format 1_0 with CRC scrambled by a corresponding MsgB-RNTI during a window controlled
by higher layers [11, TS 38.321]. The window starts at the first symbol of the earliest CORESET the UE is configured to
receive PDCCH for Type1-PDCCH CSS set, as defined in clause 10.1, that is at least one symbol, after the last symbol
of the PRACH occasion corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS
for Type1-PDCCH CSS set. The length of the window in number of slots, based on the SCS for Type1-PDCCH CSS set,
is provided by msgB-ResponseWindow.
If the UE detects the DCI format 1_0, with CRC scrambled by the corresponding MsgB-RNTI and LSBs of a SFN field
in the DCI format 1_0, if applicable, are same as corresponding LSBs of the SFN where the UE transmitted PRACH,
and the UE receives a transport block in a corresponding PDSCH within the window, the UE passes the transport block
to higher layers. The higher layers indicate to the physical layer
- an uplink grant if the RAR message(s) is for fallbackRAR and a random access preamble identity (RAPID)
associated with the PRACH transmission is identified, and the UE procedure continues as described in clauses
8.2, 8.3, and 8.4 when the UE detects a RAR UL grant, or
ETSI
- transmission of a PUCCH with HARQ-ACK information having ACK value if the RAR message(s) is for
successRAR, where
- a PUCCH resource for the transmission of the PUCCH is indicated by PUCCH resource indicator field of 4
bits in the successRAR from a PUCCH resource set that is provided by pucch-ResourceCommon
- a slot for the PUCCH transmission is indicated by a HARQ Feedback Timing Indicator field of 3 bits in the
successRAR having a value from {1, 2, 3, 4, 5, 6, 7, 8} and, with reference to slots for PUCCH
transmission having duration ௦௟௢௧ , the slot is determined as + + ∆, where is a slot of the PDSCH
reception and ∆ is as defined for PUSCH transmission in Table 6.1.2.1.1-5 of [6, TS 38.214]
- the UE does not expect the first symbol of the PUCCH transmission to be after the last symbol of the
PDSCH reception by a time smaller than
் ଵ + 0.5 msec where
் ଵ is the PDSCH processing time for
, ,
UE processing capability 1 [6, TS 38.214]
- for operation with shared spectrum channel access, a channel access type and CP extension [15, TS 37.213]
for a PUCCH transmission is indicated by a ChannelAccess-CPext field in the successRAR as defined in
Table 7.3.1.1.1-4 in TS 38.212 as defined in Table 7.3.1.1.1-4 in TS 38.212 or Table 7.3.1.1.1-4A in TS
38.212 if ChannelAccessMode-r16 = "semistatic" is provided
- the PUCCH transmission is with a same spatial domain transmission filter and in a same active UL BWP as a
last PUSCH transmission
If the UE detects the DCI format 1_0 with CRC scrambled by a C-RNTI and a transport block in a corresponding
PDSCH within the window, the UE transmits a PUCCH with HARQ-ACK information having ACK value if the UE
correctly detects the transport block or NACK value if the UE incorrectly detects the transport block and the time
alignment timer is running [11, TS 38.321].
If the UE detects a DCI format 1_0 with CRC scrambled by the corresponding MsgB-RNTI and receives a transport
block within the window in a corresponding PDSCH, the UE may assume same DM-RS antenna port quasi co-location
properties, as described in [6, TS 38.214], as for a SS/PBCH block the UE used for PRACH association, as described in
clause 8.1, regardless of whether or not the UE is provided TCI-State for the CORESET where the UE receives the
PDCCH with the DCI format 1_0.
The UE does not expect to be indicated to transmit the PUCCH with the HARQ-ACK information at a time that is prior
to a time when the UE applies a TA command that is provided by the transport block. If the UE does not detect the DCI
format 1_0 with CRC scrambled by the corresponding MsgB-RNTI within the window, or if the UE detects the DCI
format 1_0 with CRC scrambled by the corresponding MsgB-RNTI within the window and LSBs of a SFN field in the
DCI format 1_0, if applicable, are not same as corresponding LSBs of the SFN where the UE transmitted the PRACH,
or if the UE does not correctly receive the transport block in the corresponding PDSCH within the window, or if the
higher layers do not identify the RAPID associated with the PRACH transmission from the UE, the higher layers can
indicate to the physical layer to transmit only PRACH according to Type-1 random access procedure or to transmit both
PRACH and PUSCH according to Type-2 random access procedure [11, TS 38.321]. If requested by higher layers, the
UE is expected to transmit a PRACH no later than
+ 0.75 msec after the last symbol of the window, or the last
T,1
symbol of the PDSCH reception, where

is a time duration of
ଵ symbols corresponding to a PDSCH processing
time for UE processing capability 1 when additional PDSCH DM-RS is configured. For = 0, the UE assumes
=
T,1
14 [6, TS 38.214].
1,0
Unless the UE is configured a SCS, the UE receives subsequent PDSCH using same SCS as for the PDSCH reception
providing the RAR message.
If the UE does not detect the DCI format 1_0 with CRC scrambled by the corresponding MsgB-RNTI within the
window, or if the UE detects the 1_0 with CRC scrambled by the corresponding MsgB-RNTI within the window and
LSBs of a SFN field in the DCI format 1_0, if applicable, are not same as corresponding LSBs of the SFN where the
UE transmitted the PRACH, or the UE does not correctly receive a corresponding transport block within the window,
the UE procedure is as described in [11, TS 38.321].
8.3 PUSCH scheduled by RAR UL grant

An active UL BWP, as described in clause 12 and in [4, TS 38.211], for a PUSCH transmission scheduled by a RAR
UL grant is indicated by higher layers.
ETSI
If useInterlacePUCCH-PUSCH is not provided by BWP-UplinkCommon and BWP-UplinkDedicated, for determining

the frequency domain resource allocation for the PUSCH transmission within the active UL BWP
- if the active UL BWP and the initial UL BWP have same SCS and same CP length and the active UL BWP
includes all RBs of the initial UL BWP, or the active UL BWP is the initial UL BWP, the initial UL BWP is
used
- else, the RB numbering starts from the first RB of the active UL BWP and the maximum number of RBs for
frequency domain resource allocation equals the number of RBs in the initial UL BWP
The frequency domain resource allocation is by uplink resource allocation type 1 [6, TS 38.214]. For an initial UL BWP
size of
RBs, a UE processes the frequency domain resource assignment field as follows
size
BWP
- if
size
BWP
≤ 180, or for operation with shared spectrum channel access if
≤ 90
size
BWP
- truncate the frequency domain resource assignment field to its log ଶ

∙
+ 1⁄2 least significant
size
BWP
size
BWP
bits and interpret the truncated frequency resource assignment field as for the frequency resource assignment
field in DCI format 0_0 as described in [5, TS 38.212]
- else
- insert log ଶ
size
∙
+ 1⁄2 − 14 most significant bits, or for operation with shared spectrum
size
channel access insert log ଶ

∙
+ 1⁄2 − 12 most significant bits, with value set to '0' after the
BWP BWP
size size

୙୐ ୦୭୮ bits to the frequency domain resource assignment field, where
୙୐ ୦୭୮ = 0 if the frequency hopping
BWP BWP
, ,
flag is set to '0' and

୙୐ ୦୭୮ is provided in Table 8.3-1 if the hopping flag bit is set to '1', and interpret the
,
expanded frequency resource assignment field as for the frequency resource assignment field in DCI format
0_0 as described in [5, TS 38.212]
- end if
If useInterlacePUCCH-PUSCH is provided by BWP-UplinkCommon or BWP-UplinkDedicated, the frequency domain

resource allocation is by uplink resource allocation type 2 [6, TS 38.214]. A UE processes the frequency domain
resource assignment field as follows
- truncate the frequency domain resource assignment field to the = 6 LSBs if = 0, or to the = 5 LSBs if
=1
- for interlace allocation of a PUSCH transmission, interpret the MSBs of the truncated frequency domain
resource assignment field for the active UL BWP as for the MSBs of the frequency domain resource
assignment field in DCI format 0_0 [6, TS 38.214]
- for RB set allocation of a PUSCH transmission, the RB set of the active UL BWP is the RB set of the PRACH
transmission associated with the RAR UL grant. The UE assumes that the RB set is defined as when the UE is
not provided intraCellGuardBandsUL-List [6, TS 38.214].
A UE determines whether or not to apply transform precoding as described in [6, TS 38.214].
For a PUSCH transmission with frequency hopping scheduled by RAR UL grant or for a Msg3 PUSCH retransmission,
the frequency offset for the second hop [6, TS 38.214] is given in Table 8.3-1.
ETSI
Table 8.3-1: Frequency offset for second hop of PUSCH transmission with frequency hopping
scheduled by RAR UL grant or of Msg3 PUSCH retransmission
Number of PRBs in initial UL BWP Value of ࡺ‫ ܘܗܐ ۺ܃‬Hopping Bits

,
Frequency offset for 2nd hop
0 ⌊ܰsize
⁄ 2⌋
ܰ < 50
BWP
size
⌊ܰ ⁄ 4⌋
BWP
1 size
BWP
00 ⌊ܰsize
BWP
⁄ 2⌋
01 ⌊ܰsize
⁄ 4⌋
ܰ ≥ 50
BWP
size
BWP
10 − ⌊ܰ size
BWP
⁄ 4⌋
11 Reserved
A SCS for the PUSCH transmission is provided by subcarrierSpacing in BWP-UplinkCommon. A UE transmits

PRACH and the PUSCH on a same uplink carrier of a same serving cell.
A UE transmits a transport block in a PUSCH scheduled by a RAR UL grant in a corresponding RAR message using
redundancy version number 0. If a TC-RNTI is provided by higher layers, the scrambling initialization of the PUSCH
corresponding to the RAR UL grant in clause 8.2 is by TC-RNTI. Otherwise, the scrambling initialization of the
PUSCH corresponding to the RAR UL grant in clause 8.2 is by C-RNTI. Msg3 PUSCH retransmissions, if any, of the
transport block, are scheduled by a DCI format 0_0 with CRC scrambled by a TC-RNTI provided in the corresponding
RAR message [11, TS 38.321]. The UE always transmits the PUSCH scheduled by a RAR UL grant without
repetitions.
With reference to slots for a PUSCH transmission scheduled by a RAR UL grant, if a UE receives a PDSCH with a
RAR message ending in slot for a corresponding PRACH transmission from the UE, the UE transmits the PUSCH in
slot + ଶ + ∆, where ଶ and ∆ are provided in [6, TS 38.214].
The UE may assume a minimum time between the last symbol of a PDSCH reception conveying a RAR message with a
RAR UL grant and the first symbol of a corresponding PUSCH transmission scheduled by the RAR UL grant is equal
to
் ଵ +
் ଶ + 0.5 msec, where
் ଵ is a time duration of
ଵ symbols corresponding to a PDSCH processing time for
, , ,
UE processing capability 1 when additional PDSCH DM-RS is configured,

் ଶ is a time duration of
ଶ symbols
,
corresponding to a PUSCH preparation time for UE processing capability 1 [6, TS 38.214] and, for determining the
minimum time, the UE considers that
ଵ and
ଶ correspond to the smaller of the SCS configurations for the PDSCH
and the PUSCH. For = 0, the UE assumes
ଵ ଴ = 14 [6, TS 38.214].
,
8.4 PDSCH with UE contention resolution identity

In response to a PUSCH transmission scheduled by a RAR UL grant when a UE has not been provided a C-RNTI, the
UE attempts to detect a DCI format 1_0 with CRC scrambled by a corresponding TC-RNTI scheduling a PDSCH that
includes a UE contention resolution identity [11, TS 38.321]. In response to the PDSCH reception with the UE
contention resolution identity, the UE transmits HARQ-ACK information in a PUCCH. The PUCCH transmission is
within a same active UL BWP as the PUSCH transmission. A minimum time between the last symbol of the PDSCH
reception and the first symbol of the corresponding PUCCH transmission with the HARQ-ACK information is equal to
N T,1 + 0 .5 msec. N T,1 is a time duration of N1 symbols corresponding to a PDSCH processing time for UE
processing capability 1 when additional PDSCH DM-RS is configured. For μ = 0 , the UE assumes N 1,0 = 14 [6, TS
38.214].
When detecting a DCI format in response to a PUSCH transmission scheduled by a RAR UL grant, as described in [11,
TS 38.321], or corresponding PUSCH retransmission scheduled by a DCI format 0_0 with CRC scrambled by a TC-
RNTI provided in the corresponding RAR message [11, TS 38.321], the UE may assume the PDCCH carrying the DCI
format has the same DM-RS antenna port quasi co-location properties, as described in [6, TS 38.214], as for a
SS/PBCH block the UE used for PRACH association, as described in clause 8.1, regardless of whether or not the UE is
provided TCI-State for the CORESET where the UE receives the PDCCH with the DCI format.
ETSI
9 UE procedure for reporting control information

If a UE is configured with a SCG, the UE shall apply the procedures described in this clause for both MCG and SCG.
- When the procedures are applied for MCG, the terms 'secondary cell', 'secondary cells' , 'serving cell', 'serving
cells' in this clause refer to secondary cell, secondary cells, serving cell, serving cells belonging to the MCG
respectively.
- When the procedures are applied for SCG, the terms 'secondary cell', 'secondary cells', 'serving cell', 'serving
cells' in this clause refer to secondary cell, secondary cells (not including PSCell), serving cell, serving cells
belonging to the SCG respectively. The term 'primary cell' in this clause refers to the PSCell of the SCG.
If a UE is configured with a PUCCH-SCell, the UE shall apply the procedures described in this clause for both primary
PUCCH group and secondary PUCCH group
- When the procedures are applied for the primary PUCCH group, the terms 'secondary cell', 'secondary cells' ,
'serving cell', 'serving cells' in this clause refer to secondary cell, secondary cells, serving cell, serving cells
belonging to the primary PUCCH group respectively.
- When the procedures are applied for secondary PUCCH group, the terms 'secondary cell', 'secondary cells',
'serving cell', 'serving cells' in this clause refer to secondary cell, secondary cells (not including the PUCCH-
SCell), serving cell, serving cells belonging to the secondary PUCCH group respectively. The term 'primary cell'
in this clause refers to the PUCCH-SCell of the secondary PUCCH group. If pdsch-HARQ-ACK-Codebook-
secondaryPUCCHgroup-r16 is provided, pdsch-HARQ-ACK-Codebook is replaced by pdsch-HARQ-ACK-
Codebook-secondaryPUCCHgroup-r16. If harq-ACK-SpatialBundlingPUCCH-secondaryPUCCHgroup is
provided, harq-ACK-SpatialBundlingPUCCH is replaced by harq-ACK-SpatialBundlingPUCCH-
secondaryPUCCHgroup. If harq-ACK-SpatialBundlingPUSCH-secondaryPUCCHgroup is provided, harq-
ACK-SpatialBundlingPUSCH is replaced by harq-ACK-SpatialBundlingPUSCH-secondaryPUCCHgroup.
If a UE is provided pdsch-HARQ-ACK-CodebookList-r16, pdsch-HARQ-ACK-Codebook is replaced by the relevant

entry in pdsch-HARQ-ACK-CodebookList-r16.
If a UE
- is not provided coresetPoolIndex or is provided coresetPoolIndex with a value of 0 for first CORESETs on
active DL BWPs of serving cells, and
- is provided coresetPoolIndex with a value of 1 for second CORESETs on active DL BWPs of the serving cells,
and
- is provided ackNackFeedbackMode = separate
the UE shall separately apply the procedures described in clauses 9.1 and 9.2.3 for reporting HARQ-ACK information
associated with the first CORESETs on active DL BWP of the serving cells and for reporting HARQ-ACK information
associated with the second CORESETs on active DL BWP of the serving cells, and the UE does not expect to be
provided with subslotLengthForPUCCH or to be indicated by pdsch-HARQ-ACK-CodebookList to generate two
HARQ-ACK codebooks on active DL BWP of the serving cells. HARQ-ACK information reporting is associated
with a CORESET through a reception of a PDCCH with a DCI format triggering the reporting of the HARQ-ACK
information by the UE.
For NR-DC when both the MCG and the SCG operate either in FR1 or in FR2 and for a power headroom report
transmitted on the MCG or the SCG, the UE computes PH assuming that the UE does not transmit PUSCH/PUCCH on
any serving cell of the SCG or the MCG, respectively.
If a UE is configured for NR-DC operation, the UE does not expect to be configured with a PUCCH-SCell.
A PUSCH or a PUCCH transmission other than PUCCH transmissions with SL HARQ-ACK reports, including
repetitions if any, can be of priority index 0 or of priority index 1. For a configured grant PUSCH transmission, a UE
determines a priority index from phy-PriorityIndex, if provided. For a PUCCH transmission with HARQ-ACK
information corresponding to a SPS PDSCH reception or a SPS PDSCH release, a UE determines a priority index from
harq-CodebookID, if provided. For a PUCCH transmission with SR, a UE determines the corresponding priority as
described in clause 9.2.4. For a PUSCH transmission with semi-persistent CSI report, a UE determines a priority index
from a priority indicator field, if provided, in a DCI format that activates the semi-persistent CSI report. If a priority
ETSI
index is not provided to a UE for a PUSCH or a PUCCH transmission other than PUCCH transmissions with SL
HARQ-ACK reports, the priority index is 0.
If a UE is provided one PUCCH-Config

- if the UE is provided subslotLengthForPUCCH in the PUCCH-Config, the PUCCH resource for any SR
configuration with priority index 0 or any CSI report configuration in the PUCCH-Config is within the
subslotLengthForPUCCH symbols in the PUCCH-Config
If a UE is provided two PUCCH-Config
- if the UE is provided subslotLengthForPUCCH in the first PUCCH-Config, the PUCCH resource for any SR
configuration with priority index 0 or any CSI report configuration in any PUCCH-Config is within the
subslotLengthForPUCCH symbols in the first PUCCH-Config
- if the UE is provided subslotLengthForPUCCH in the second PUCCH-Config, the PUCCH resource for any SR
configuration with priority index 1 in any PUCCH-Config is within the subslotLengthForPUCCH symbols in the
second PUCCH-Config
If in an active DL BWP a UE monitors PDCCH either for detection of DCI format 0_1 and DCI format 1_1 or for
detection of DCI format 0_2 and DCI format 1_2, a priority index can be provided by a priority indicator field. If a UE
indicates a capability to monitor, in an active DL BWP, PDCCH for detection of DCI format 0_1 and DCI format 1_1
and for detection of DCI format 0_2 and DCI format 1_2, a DCI format 0_1 or a DCI format 0_2 can schedule a
PUSCH transmission of any priority, a DCI format 1_1 or a DCI format 1_2 can schedule a PDSCH reception and
trigger a PUCCH transmission with corresponding HARQ-ACK information of any priority and a DCI format 1_1 can
indicate SCell dormancy and trigger a PUCCH transmission with corresponding HARQ-ACK information of any
priority.
When a UE determines overlapping for PUCCH transmissions with SL HARQ-ACK reports and PUCCH of larger
and/or smaller priority index, the UE resolves the overlapping for PUCCH transmissions with SL HARQ-ACK reports
and PUCCH of each priority index as described in clause 9.2.5 and 9.2.6 before resolving the overlapping for PUCCH
transmissions without SL HARQ-ACK or the overlapping for PUCCH transmissions and PUSCH transmissions.
When a UE determines overlapping for PUCCH and/or PUSCH transmissions of different priority indexes other than
PUCCH transmissions with SL HARQ-ACK reports before considering limitations for UE transmission as described in
clause 11.1, including repetitions if any, the UE first resolves the overlapping for PUCCH and/or PUSCH transmissions
of smaller priority index as described in clauses 9.2.5 and 9.2.6. Then,
- if a transmission of a first PUCCH of larger priority index scheduled by a DCI format in a PDCCH reception
would overlap in time with a repetition of a transmission of a second PUSCH or a second PUCCH of smaller
priority index, the UE cancels the repetition of a transmission of the second PUSCH or the second PUCCH
before the first symbol that would overlap with the first PUCCH transmission
- if a transmission of a first PUSCH of larger priority index scheduled by a DCI format in a PDCCH reception
would overlap in time with a repetition of the transmission of a second PUCCH of smaller priority index, the UE
cancels the repetition of the transmission of the second PUCCH before the first symbol that would overlap with
the first PUSCH transmission
where
- the overlapping is applicable before or after resolving overlapping among channels of larger priority index, if
any, as described in clauses 9.2.5 and 9.2.6
- any remaining PUCCH and/or PUSCH transmission after overlapping resolution is subjected to the limitations
for UE transmission as described in clause 11.1
- the UE expects that the transmission of the first PUCCH or the first PUSCH, respectively, would not start before
௣௥௢௖ ଶ after a last symbol of the corresponding PDCCH reception
,
- ௣௥௢௖ ଶ is the PUSCH preparation time for a corresponding UE processing capability assuming ଶ ଵ = ଵ [6, TS
, ,
38.214], based on and

ଶ as subsequently defined in this clause, and ଵ is determined by a reported UE
capability
ETSI
If a UE is scheduled by a DCI format in a first PDCCH reception to transmit a first PUCCH or a first PUSCH of larger
priority index that overlaps with a second PUCCH or a second PUSCH transmission of smaller priority index that, if
any, is scheduled by a DCI format in a second PDCCH
- ௣௥௢௖ ଶ is based on a value of corresponding to the smallest SCS configuration of the first PDCCH, the second
,
PDCCHs, the first PUCCH or the first PUSCH, and the second PUCCHs or the second PUSCHs
- if the overlapping group includes the first PUCCH
- if processingType2Enabled of PDSCH-ServingCellConfig is set to enable for the serving cell where the
UE receives the first PDCCH and for all serving cells where the UE receives the PDSCHs corresponding
to the second PUCCHs, and if processingType2Enabled of PUSCH-ServingCellConfig is set to enable for
the serving cells with the second PUSCHs,
ଶ is 5 for = 0, 5.5 for = 1 and 11 for = 2
- else,
ଶ is 10 for =0, 12 for = 1, 23 for = 2, and 36 for = 3;
- if the overlapping group includes the first PUSCH
- if processingType2Enabled of PUSCH-ServingCellConfig is set to enable for the serving cells with the
first PUSCH and the second PUSCHs and if processingType2Enabled of PDSCH-ServingCellConfig is
set to enable for all serving cells where the UE receives the PDSCHs corresponding to the second
PUCCHs,
ଶ is 5 for = 0, 5.5 for = 1 and 11 for = 2
- else,
ଶ is 10 for =0, 12 for = 1, 23 for = 2, and 36 for = 3;
If a UE would transmit the following channels, including repetitions if any, that would overlap in time
- a first PUCCH of larger priority index with SR and a second PUCCH or PUSCH of smaller priority index, or
- a configured grant PUSCH of larger priority index and a PUCCH of smaller priority index, or
- a first PUCCH of larger priority index with HARQ-ACK information only in response to a PDSCH reception
without a corresponding PDCCH and a second PUCCH of smaller priority index with SR and/or CSI, or a
configured grant PUSCH with smaller priority index, or a PUSCH of smaller priority index with SP-CSI
report(s) without a corresponding PDCCH, or
- a PUSCH of larger priority index with SP-CSI reports(s) without a corresponding PDCCH and a PUCCH of
smaller priority index with SR, or CSI, or HARQ-ACK information only in response to a PDSCH reception
without a corresponding PDCCH, or
- a configured grant PUSCH of larger priority index and a configured PUSCH of lower priority index on a same
serving cell
the UE is expected to cancel a repetition of the PUCCH/PUSCH transmissions of smaller priority index before the first
symbol overlapping with the PUCCH/PUSCH transmission of larger priority index if the repetition of the
PUCCH/PUSCH transmissions of smaller priority index overlaps in time with the PUCCH/PUSCH transmissions of
larger priority index.
When a UE determines overlapping for PUCCH transmissions with SL HARQ-ACK reports and PUSCH of smaller
priority index, including repetitions if any, after resolving the overlapping PUCCH other than PUCCH transmissions
with SL HARQ-ACK reports and/or PUSCH transmissions, if the PUSCH includes no UCI, the UE resolves the
overlapping for PUCCH transmissions with SL HARQ-ACK reports and PUSCH of smaller priority index as described
in clauses 9.2.5 and 9.2.6.
When a UE determines overlapping for PUCCH transmissions with SL HARQ-ACK reports and PUSCH of larger
priority index only, including repetitions if any, after resolving the overlapping PUCCH other than PUCCH
transmissions with SL HARQ-ACK reports and/or PUSCH transmissions, the UE does not transmit the PUCCH with
SL HARQ-ACK reports
where
- the UE expects that the transmission of the PUSCH would not start before ௣௥௢௖ ଶ + ଵ after a last symbol of the
,
corresponding PDCCH reception;
ETSI
- ௣௥௢௖ ଶ is the PUSCH preparation time for a corresponding UE processing capability assuming ଶ ଵ = 0 [6, TS
, ,
38.214], based on and

ଶ as subsequently defined in this clause, and ଵ is determined by a reported UE
capability.
The UE expects the PUCCH and PUSCH transmissions fulfill the conditions in clause 9 and clause 9.2.5 for UCI
multiplexing replacing the reference time of "end of PDSCH" with "end of the last symbol of a last PSFCH reception
occasion" as described in 16.5 and Tproc,1 with Tprep.
A UE does not expect that a PUCCH carrying SL HARQ-ACK reports overlaps with PUSCH with aperiodic or semi-
persistent CSI reports.
A UE does not expect to be scheduled to transmit a PUCCH or a PUSCH with smaller priority index that would overlap
in time with a PUCCH of larger priority index with HARQ-ACK information only in response to a PDSCH reception
without a corresponding PDCCH. A UE does not expect to be scheduled to transmit a PUCCH of smaller priority index
that would overlap in time with a PUSCH of larger priority index with SP-CSI report(s) without a corresponding
PDCCH.
In the remaining of this clause, a UE multiplexes UCIs with same priority index in a PUCCH or a PUSCH before
considering limitations for UE transmission as described in clause 11.1. A PUCCH or a PUSCH is assumed to have a
same priority index as a priority index of UCIs a UE multiplexes in the PUCCH or the PUSCH.
In the remaining of this clause, the multiplexing or prioritization for overlapping channels are for overlapping channels
with same priority index or for overlapping channels with a PUCCH carrying SL HARQ-ACK information..
In the remaining of this clause, if a UE is provided subslotLengthForPUCCH, a slot for an associated PUCCH resource
of a PUCCH transmission with HARQ-ACK information includes a number of symbols indicated by
subslotLengthForPUCCH.
If a UE would transmit on a serving cell a PUSCH without UL-SCH that overlaps with a PUCCH transmission on a
serving cell that includes positive SR information, the UE does not transmit the PUSCH.
If a UE would transmit CSI reports on overlapping physical channels, the UE applies the priority rules described in [6,
TS 38.214] for the multiplexing of CSI reports.
If a UE has overlapping resources for PUCCH transmissions in a slot and at least one of the PUCCH transmissions is
with repetitions over multiple slots, the UE first follows the procedures described in clause 9.2.6 for resolving the
overlapping among the resources for the PUCCH transmissions.
If a UE
- would multiplex UCI in a PUCCH transmission that overlaps with a PUSCH transmission, and
- the PUSCH and PUCCH transmissions fulfill the conditions in clause 9.2.5 for UCI multiplexing,
the UE
- multiplexes only HARQ-ACK information, if any, from the UCI in the PUSCH transmission and does not
transmit the PUCCH if the UE multiplexes aperiodic or semi-persistent CSI reports in the PUSCH;
- multiplexes only HARQ-ACK information and CSI reports, if any, from the UCI in the PUSCH transmission
and does not transmit the PUCCH if the UE does not multiplex aperiodic or semi-persistent CSI reports in the
PUSCH.
A UE does not expect to multiplex in a PUSCH transmission in one slot with SCS configuration ଵ UCI of same type
that the UE would transmit in PUCCHs in different slots with SCS configuration ଶ if ଵ < ଶ .
A UE does not expect to multiplex in a PUSCH transmission or in a PUCCH transmission HARQ-ACK information
that the UE would transmit in different PUCCHs.
A UE does not expect a PUCCH resource that results from multiplexing overlapped PUCCH resources, if applicable, to
overlap with more than one PUSCHs if each of the more than one PUSCHs includes aperiodic CSI reports.
A UE does not expect to detect a DCI format scheduling a PDSCH reception or a SPS PDSCH release, a DCI format
1_1 indicating SCell dormancy, or a DCI format including a One-shot HARQ-ACK request field with value 1, and
indicating a resource for a PUCCH transmission with corresponding HARQ-ACK information in a slot if the UE
ETSI
previously detects a DCI format scheduling a PUSCH transmission in the slot and if the UE multiplexes HARQ-ACK
information in the PUSCH transmission.
If a UE multiplexes aperiodic CSI in a PUSCH and the UE would multiplex UCI that includes HARQ-ACK
information in a PUCCH that overlaps with the PUSCH and the timing conditions for overlapping PUCCHs and
PUSCHs in clause 9.2.5 are fulfilled, the UE multiplexes only the HARQ-ACK information in the PUSCH and does not
transmit the PUCCH.
If a UE transmits multiple PUSCHs in a slot on respective serving cells that include first PUSCHs that are scheduled by
DCI formats and second PUSCHs configured by respective ConfiguredGrantConfig or semiPersistentOnPUSCH, and
the UE would multiplex UCI in one of the multiple PUSCHs, and the multiple PUSCHs fulfil the conditions in clause
9.2.5 for UCI multiplexing, the UE multiplexes the UCI in a PUSCH from the first PUSCHs.
If a UE transmits multiple PUSCHs in a slot on respective serving cells and the UE would multiplex UCI in one of the
multiple PUSCHs and the UE does not multiplex aperiodic CSI in any of the multiple PUSCHs, the UE multiplexes the
UCI in a PUSCH of the serving cell with the smallest ServCellIndex subject to the conditions in clause 9.2.5 for UCI
multiplexing being fulfilled. If the UE transmits more than one PUSCHs in the slot on the serving cell with the smallest
ServCellIndex that fulfil the conditions in clause 9.2.5 for UCI multiplexing, the UE multiplexes the UCI in the earliest
PUSCH that the UE transmits in the slot.
If a UE transmits a PUSCH over multiple slots and the UE would transmit a PUCCH with HARQ-ACK and/or CSI
information over a single slot that overlaps with the PUSCH transmission in one or more slots of the multiple slots, and
the PUSCH transmission in the one or more slots fulfills the conditions in clause 9.2.5 for multiplexing the HARQ-
ACK and/or CSI information, the UE multiplexes the HARQ-ACK and/or CSI information in the PUSCH transmission
in the one or more slots. The UE does not multiplex HARQ-ACK and/or CSI information in the PUSCH transmission in
a slot from the multiple slots if the UE would not transmit a single-slot PUCCH with HARQ-ACK and/or CSI
information in the slot in case the PUSCH transmission was absent.
If a UE transmits a PUSCH with repetition Type B and the UE would transmit a PUCCH with HARQ-ACK and/or CSI
information over a single slot that overlaps with the PUSCH transmission in one or more slots, the UE expects all actual
repetitions of the PUSCH transmission [6, TS 38.214] that would overlap with the PUCCH transmission to fulfill the
conditions in clause 9.2.5 for multiplexing the HARQ-ACK and/or CSI information, and the UE multiplexes the
HARQ-ACK and/or CSI information in the earliest actual PUSCH repetition of the PUSCH transmission that would
overlap with the PUCCH transmission and includes more than one symbol. The UE does not expect that all actual
repetitions that would overlap with the PUCCH transmission do not include more than one symbol.
If the PUSCH transmission over the multiple slots is scheduled by a DCI format that includes a DAI field, the value of
the DAI field is applicable for multiplexing HARQ-ACK information in the PUSCH transmission in any slot from the
multiple slots where the UE multiplexes HARQ-ACK information.
When a UE would multiplex HARQ-ACK information in a PUSCH transmission that is configured by a

ConfiguredGrantConfig, and includes CG-UCI [5, TS 38.212], the UE multiplexes the HARQ-ACK information in the
PUSCH transmission if the UE is provided cg-UCI-Multiplexing; otherwise, the UE does not transmit the PUSCH and
multiplexes the HARQ-ACK information in a PUCCH transmission or in another PUSCH transmission.
9.1 HARQ-ACK codebook determination

If a UE is provided pdsch-HARQ-ACK-CodebookList, the UE can be indicated by pdsch-HARQ-ACK-CodebookList to
generate one or two HARQ-ACK codebooks. If the UE is indicated to generate one HARQ-ACK codebook, the HARQ-
ACK codebook is associated with a PUCCH of priority index 0. If a UE is provided pdsch-HARQ-ACK-CodebookList,
the UE multiplexes in a same HARQ-ACK codebook only HARQ-ACK information associated with a same priority
index. If the UE is indicated to generate two HARQ-ACK codebooks
- a first HARQ-ACK codebook is associated with a PUCCH of priority index 0 and a second HARQ-ACK
codebook is associated with a PUCCH of priority index 1
- the UE is provided first and second for each of {PUCCH-Config, UCI-OnPUSCH, PDSCH-
codeBlockGroupTransmission} by {PUCCH-ConfigurationList, UCI-OnPUSCH-ListDCI-0-1, PDSCH-
CodeBlockGroupTransmissionList} or {PUCCH-ConfigurationList, UCI-OnPUSCH-ListDCI-0-2, PDSCH-
CodeBlockGroupTransmissionList}, respectively, for use with the first and second HARQ-ACK codebooks,
respectively
ETSI
If a UE receives a PDSCH without receiving a corresponding PDCCH, or if the UE receives a PDCCH indicating a SPS
PDSCH release, the UE generates one corresponding HARQ-ACK information bit. If the UE generates two HARQ-
ACK codebooks, the UE is indicated by harq-CodebookID, per SPS PDSCH configuration, a HARQ-ACK codebook
index for multiplexing the corresponding HARQ-ACK information bit.
If a UE is provided pdsch-HARQ-ACK-OneShotFeedback and the UE detects a DCI format in any PDCCH monitoring
occasion that includes a One-shot HARQ-ACK request field with value 1
- the UE includes the HARQ-ACK information in a Type-3 HARQ-ACK codebook, as described in clause 9.1.4
- the UE does not expect that the PDSCH-to-HARQ_feedback timing indicator field of the DCI format provides
an inapplicable value from dl-DataToUL-ACK-r16
In the remaining of this clause, reference is to one HARQ-ACK codebook and to DCI formats that schedule PDSCH
reception, or indicate SPS PDSCH release, or indicate SCell dormancy without scheduling a PDSCH reception and are
associated with the HARQ-ACK codebook.
If a UE is configured to receive SPS PDSCHs in a slot for SPS configurations that are indicated to be released by a DCI
format, and if the UE receives the PDCCH providing the DCI format in the slot where the end of a last symbol of the
PDCCH reception is not after the end of a last symbol of any of the SPS PDSCH receptions, and if HARQ-ACK
information for the SPS PDSCH release and the SPS PDSCH receptions would be multiplexed in a same PUCCH, the
UE does not expect to receive the SPS PDSCHs, does not generate HARQ-ACK information for the SPS PDSCH
receptions, and generates a HARQ-ACK information bit for the SPS PDSCH release.
If a UE detects a DCI format 1_1 indicating
- SCell dormancy without scheduling a PDSCH reception, as described in clause 10.3, and
- is provided pdsch-HARQ-ACK-Codebook = dynamic or pdsch-HARQ-ACK-Codebook-r16
the UE generates a HARQ-ACK information bit as described in clause 9.1.3 for a DCI format 1_1 indicating SCell
dormancy and the HARQ-ACK information bit value is ACK.
If a UE is not provided PDSCH-CodeBlockGroupTransmission, the UE generates one HARQ-ACK information bit per
transport block.
For a HARQ-ACK information bit, a UE generates a positive acknowledgement (ACK) if the UE detects a DCI format
that provides a SPS PDSCH release or correctly decodes a transport block, and generates a negative acknowledgement
(NACK) if the UE does not correctly decode the transport block. A HARQ-ACK information bit value of 0 represents a
NACK while a HARQ-ACK information bit value of 1 represents an ACK.
In the following, the CRC for a DCI format is scrambled with a C-RNTI, an MCS-C-RNTI, or a CS-RNTI.
9.1.1 CBG-based HARQ-ACK codebook determination

If a UE is provided PDSCH-CodeBlockGroupTransmission for a serving cell, the UE receives a PDSCH scheduled by
DCI format 1_1, that includes code block groups (CBGs) of a transport block. The UE is also provided
CBG/TB,max
maxCodeBlockGroupsPerTransportBlock indicating a maximum number N HARQ− ACK of CBGs for generating
respective HARQ-ACK information bits for a transport block reception for the serving cell.
For a number of C code blocks (CBs) in a transport block, the UE determines a number of CBGs M according to
clause 5.1.7.1 of [6, TS 38.214] and determines a number of HARQ-ACK bits for the transport block as
− ACK = M .
CBG/TB
N HARQ
The UE generates an ACK for the HARQ-ACK information bit of a CBG if the UE correctly received all code blocks of
the CBG and generates a NACK for the HARQ-ACK information bit of a CBG if the UE incorrectly received at least
one code block of the CBG. If the UE receives two transport blocks, the UE concatenates the HARQ-ACK information
bits for CBGs of the second transport block after the HARQ-ACK information bits for CBGs of the first transport
block.
ETSI
The HARQ-ACK codebook includes the NHARQ− ACK HARQ-ACK information bits and, if N HARQ−ACK < N HARQ−ACK for
CBG/TB,max CBG/TB CBG/TB,max
a transport block, the UE generates a NACK value for the last N HARQ −ACK − N HARQ −ACK HARQ-ACK information bits
CBG/TB,max CBG/TB
for the transport block in the HARQ-ACK codebook.
If the UE generates a HARQ-ACK codebook in response to a retransmission of a transport block, corresponding to a

same HARQ process as a previous transmission of the transport block, the UE generates an ACK for each CBG that the
UE correctly decoded in a previous transmission of the transport block.
CBG/TB
If a UE correctly detects each of the N HARQ−ACK CBGs and does not correctly detect the transport block for the
CBG/TB CBG/TB
N HARQ − ACK CBGs, the UE generates a NACK value for each of the N HARQ−ACK CBGs.
9.1.2 Type-1 HARQ-ACK codebook determination

This clause applies if the UE is configured with pdsch-HARQ-ACK-Codebook = semi-static.
A UE does not expect to be configured with pdsch-HARQ-ACK-Codebook = semi-static for a codebook if a UE is

provided subslotLength-ForPUCCH for the codebook.
A UE reports HARQ-ACK information for a corresponding PDSCH reception or SPS PDSCH release only in a HARQ-
ACK codebook that the UE transmits in a slot indicated by a value of a PDSCH-to-HARQ_feedback timing indicator
field in a corresponding DCI format. The UE reports NACK value(s) for HARQ-ACK information bit(s) in a HARQ-
ACK codebook that the UE transmits in a slot not indicated by a value of a PDSCH-to-HARQ_feedback timing
indicator field in a corresponding DCI format.
If a UE is not provided pdsch-HARQ-ACK-OneShotFeedback, the UE does not expect to receive a PDSCH scheduled
by a DCI format that the UE detects in any PDCCH monitoring occasion and includes a PDSCH-to-HARQ_feedback
timing indicator field providing an inapplicable value from dl-DataToUL-ACK-r16.
If the UE is provided pdsch-AggregationFactor-r16 in SPS-Config or pdsch-AggregationFactor in PDSCH-Config and

no entry in pdsch-TimeDomainAllocationList and pdsch-TimeDomainAllocationListDCI-1-2 includes repetitionNumber
୰ୣ୮ୣୟ୲ ୫ୟ୶
in PDSCH-TimeDomainResourceAllocation-r16,
୔ୈୗେୌ
,
is a maximum value of pdsch-AggregationFactor-r16 in
SPS-Config or pdsch-AggregationFactor in PDSCH-Config; otherwise
୔ୈୗେୌ
,
= 1. The UE reports HARQ-ACK
information for a PDSCH reception
from DL slot ஽ −
୔ୈୗେୌ + 1 to DL slot ஽ , if
୔ୈୗେୌ is provided by pdsch-AggregationFactor or pdsch-
୰ୣ୮ୣୟ୲ ୰ୣ୮ୣୟ୲
-
AggregationFactor-r16 [6, TS 38.214], or
- from DL slot ஽ − !

"# + 1 to DL slot ஽ , if the time domain resource assignment field in the
DCI format scheduling the PDSCH reception indicates an entry containing repetitionNumber, or
- in DL slot ஽ , otherwise
only in a HARQ-ACK codebook that the UE includes in a PUCCH or PUSCH transmission in slot + , where is a
UL slot overlapping with the end of the PDSCH reception in DL slot ஽ and is a number of slots indicated by the
PDSCH-to-HARQ_feedback timing indicator field in a corresponding DCI format or provided by dl-DataToUL-ACK if
the PDSCH-to-HARQ_feedback timing indicator field is not present in the DCI format. If the UE reports HARQ-ACK
information for the PDSCH reception in a slot other than slot + , the UE sets a value for each corresponding HARQ-
ACK information bit to NACK.
If a UE reports HARQ-ACK information in a PUCCH only for
- a SPS PDSCH release indicated by DCI format 1_0 with counter DAI field value of 1, or
- a PDSCH reception scheduled by DCI format 1_0 with counter DAI field value of 1 on the PCell, or
- SPS PDSCH reception(s)
within the M A, c occasions for candidate PDSCH receptions as determined in clause 9.1.2.1, the UE determines a
HARQ-ACK codebook only for the SPS PDSCH release or only for the PDSCH reception or only for one SPS PDSCH
reception according to corresponding M A, c occasion(s) on respective serving cell(s), where the value of counter DAI in
DCI format 1_0 is according to Table 9.1.3-1 and HARQ-ACK information bits in response to more than one SPS
ETSI
PDSCH receptions that the UE is configured to receive are ordered according to the following pseudo-code; otherwise,
the procedures in clause 9.1.2.1 and clause 9.1.2.2 for a HARQ-ACK codebook determination apply.
ୈ୐ to the number of serving cells configured to the UE
Set
ୡୣ୪୪ୱ
Set
ୡୗ୔ୗ to the number of SPS PDSCH configuration configured to the UE for serving cell
Set
ୡୈ୐ to the number of DL slots for SPS PDSCH reception on serving cell with HARQ-ACK information multiplexed
on the PUCCH
Set $ = 0 – HARQ-ACK information bit index

Set = 0 – serving cell index: lower indexes correspond to lower RRC indexes of corresponding cell
while <
ୡୣ୪୪ୱ
ୈ୐
Set % = 0 – SPS PDSCH configuration index: lower indexes correspond to lower RRC indexes of corresponding
SPS configurations
while % <
ୡୗ୔ୗ
Set ஽ = 0 – slot index
while ஽ <
ୡୈ୐
if {
a UE is configured to receive SPS PDSCHs from slot ஽ −

௉஽ௌ஼ு + 1 to slot ஽ for SPS
௥௘௣௘௔௧
PDSCH configuration % on serving cell , excluding SPS PDSCHs that are not required to be
received in any slot among overlapping SPS PDSCHs, if any according to [6, TS 38.214], or based
on a UE capability for a number of PDSCH receptions in a slot according to [6, TS 38.214], or due
to overlapping with a set of symbols indicated as uplink by tdd-UL-DL-ConfigurationCommon or
௥௘௣௘௔௧
by tdd-UL-DL-ConfigurationDedicated where
௉஽ௌ஼ு is provided by pdsch-AggregationFactor-
r16 in sps-Config or, if pdsch-AggregationFactor-r16 is not included in sps-Config, by pdsch-
AggregationFactor in pdsch-config, and
HARQ-ACK information for the SPS PDSCH is associated with the PUCCH
!&௝஺஼௄ = HARQ-ACK information bit for this SPS PDSCH reception

$ = $ + 1;
end if
஽ = ஽ + 1;
end while
% = % + 1;
end while
= + 1;
end while
9.1.2.1 Type-1 HARQ-ACK codebook in physical uplink control channel

For a serving cell , an active DL BWP, and an active UL BWP, as described in clause 12, the UE determines a set of
஺ ௖ occasions for candidate PDSCH receptions for which the UE can transmit corresponding HARQ-ACK information
,
in a PUCCH in slot ௎ . If serving cell is deactivated, the UE uses as the active DL BWP for determining the set of
஺ ௖ occasions for candidate PDSCH receptions a DL BWP provided by firstActiveDownlinkBWP-Id. The
,
determination is based:
ETSI
a) on a set of slot timing values 'ଵ associated with the active UL BWP
a) If the UE is configured to monitor PDCCH for DCI format 1_0 and is not configured to monitor PDCCH for
either DCI format 1_1 or DCI format 1_2 on serving cell , 'ଵ is provided by the slot timing values {1, 2, 3,
4, 5, 6, 7, 8}
b) If the UE is configured to monitor PDCCH for DCI format 1_1 and is not configured to monitor PDCCH for
DCI format 1_2 for serving cell , 'ଵ is provided by dl-DataToUL-ACK
c) If the UE is configured to monitor PDCCH for DCI format 1_2 and is not configured to monitor PDCCH for
DCI format 1_1 for serving cell , 'ଵ is provided by dl-DataToUL-ACK-ForDCIFormat1_2
d) If the UE is configured to monitor PDCCH for DCI format 1_1 and DCI format 1_2 for serving cell , 'ଵ is
provided by the union of dl-DataToUL-ACK and dl-DataToUL-ACK-ForDCIFormat1_2
b) on a set of row indexes of a table that is associated with the active DL BWP and defining respective sets of
slot offsets '଴ , start and length indicators SLIV, and PDSCH mapping types for PDSCH reception as described
in [6, TS 38.214], where the row indexes of the table are provided by the union of row indexes of time domain
resource allocation tables for DCI formats the UE is configured to monitor PDCCH for serving cell
a) if the UE is provided referenceOfSLIVDCI-1-2, for each row index with slot offset '଴ = 0 and PDSCH
mapping Type B in a set of row indexes of a table for DCI format 1_2 [6, TS 38.214], for any PDCCH
monitoring occasion in any slot where the UE monitors PDCCH for DCI format 1_2 and with starting
symbol ଴ > 0, if + ଴ + ( ≤ 14 for normal cyclic prefix and + ଴ + ( ≤ 12 for extended cyclic prefix,
add a new row index in the set of row indexes of the table by replacing the starting symbol of the row index
by + ଴
c) on the ratio 2ఓDLିఓUL between the downlink SCS configuration and the uplink SCS configuration
DL UL
provided by subcarrierSpacing in BWP-Downlink and BWP-Uplink for the active DL BWP and the active UL
BWP, respectively
d) if provided, on tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated as described in

clause 11.1
e) if ca-SlotOffset is provided, on
DL
and
slot,offset,c
provided by ca-SlotOffset for serving cell , or on
offset,DL,c

UL
and
slot,offset U provided
offset, L
by ca-SlotOffset for the primary cell, as described in [4, TS 38.211].
If a UE
and
- is provided ackNackFeedbackMode = joint
where
- a serving cell is placed in a first set 0 of

DL,0
cells
serving cells if the serving cell includes a first CORESET, and
- a serving cell is placed in a second set 1 of

DL,1
cells
serving cells if the serving cell includes a second CORESET,
and
- serving cells are placed in a set according to an ascending order of a serving cell index
the UE generates a Type-1 HARQ-ACK codebook for the set 0 and the set ଵ of serving cells separately by setting
DL
cells
=
and
=
in the following pseudo-code. The UE concatenates the HARQ-ACK codebook
DL,0
cells
DL
cells
DL,1
cells
generated for the set 0 followed by the HARQ-ACK codebook generated for the set ଵ to obtain a total number of
OACK HARQ-ACK information bits.
For the set of slot timing values K 1 , the UE determines a set of M A,c occasions for candidate PDSCH receptions or
SPS PDSCH releases according to the following pseudo-code. A location in the Type-1 HARQ-ACK codebook for
HARQ-ACK information corresponding to a single SPS PDSCH release is same as for a corresponding SPS PDSCH
ETSI
reception. A location in the Type-1 HARQ-ACK codebook for HARQ-ACK information corresponding to multiple SPS
PDSCH releases by a single DCI format is same as for a corresponding SPS PDSCH reception with the lowest SPS
configuration index among the multiple SPS PDSCH releases.
Set j = 0 - index of occasion for candidate PDSCH reception or SPS PDSCH release
Set B = ∅
Set M A, c = ∅
Set C (K1 ) to the cardinality of set K 1
Set k =0 – index of slot timing values K1,k , in descending order of the slot timing values, in set K 1 for serving cell c
If a UE is not provided ca-SlotOffset for any serving cell of PDSCH receptions and for the serving cell of corresponding
PUCCH transmission with HARQ-ACK information
while k < C (K 1 )
( μ -μ
if mod nU - K1,k + 1, max 2 UL DL ,1 = 0( ))
Set nD = 0 – index of a DL slot within an UL slot
while nD < max 2 μ ( DL - μ UL

)
,1
Set R to the set of rows
Set C (R ) to the cardinality of R
Set r = 0 – index of row in set R

if slot n U starts at a same time as or after a slot for an active DL BWP change on serving cell c or an active
UL BWP change on the PCell and slot (n U − K1, k )⋅ 2 μ DL - μ UL
+ n D is before the slot for the active DL BWP
change on serving cell c or the active UL BWP change on the PCell
஽ = ஽ + 1;
else
while r < C (R )
if the UE is provided tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated and,

for each slot from slot උ൫݊௎ − ‫ܭ‬ଵ ௞ ൯ ⋅ 2ఓವಽିఓೆಽ ඏ + ݊஽ − ܰ୔ୈୗେୌ + 1 to slot උ൫݊௎ − ‫ܭ‬ଵ ௞ ൯ ⋅
,
, ,
2 ఓ ವಽ ିఓ ೆಽ ඏ + ݊஽ , at least one symbol of the PDSCH time resource derived by row r is configured as
UL where K1,k is the k-th slot timing value in set K 1 ,
R = R\ r ;
else
r = r +1 ;
end if
end while
if the UE does not indicate a capability to receive more than one unicast PDSCH per slot and R ≠ ∅ ,
M A, c = M A, c U j ;
ETSI
j = j +1 ;
else
Set m to the smallest last OFDM symbol index, as determined by the SLIV, among all rows of R
while R≠∅
Set r =0
while r < C (R)
if S ≤ m for start OFDM symbol index S for row r
br ,k ,n = j ; - index of occasion for candidate PDSCH reception or SPS PDSCH release

D
associated with row r
R= R\r ;
B = B U br ,k ,n ; D
else
r = r +1;
end if
end while
M A,c = M A,c U j;
j = j +1 ;
Set m to the smallest last OFDM symbol index among all rows of R ;
end while
end if
݊‫ܦ‬ = ݊‫ ܦ‬+ 1;
end if
end while
end if
k = k +1 ;
end while
else
while k < C (K 1 )
ೆಽ ವಽ
if mod ൬݊௎ − ‫ܭ‬ଵ ௞ + ඌ(ଶேഋೞ೗೚೟
,
೚೑೑ೞ೐೟ ேೞ೗೚೟ ೚೑೑ೞ೐೟ ೎
೚೑೑ೞ೐೟ ೆಽ − ଶഋ೚೑೑ೞ೐೟ ವಽ ೎ ) ∙ 2 ඐ + 1, max(2
, ఓೆಽ
,
, ఓೆಽ ିఓವಽ , 1)൰ = 0
,
,
Set nD = 0 – index of a DL slot within an UL slot
while nD < max 2 μ ( DL - μ UL

,1 )
ETSI
Set R to the set of rows
Set r = 0 – index of row in set R

if slot n U starts at a same time as or after a slot for an active DL BWP change on serving cell c or an active UL
ேೆಽ ೚೑೑ೞ೐೟ ேೞ೗೚೟
ವಽ
BWP change on the PCell and slot උ൫݊୙ − ‫ܭ‬ଵ ௞ ൯ ∙ 2ఓವಽିఓೆಽ ඏ + ඌ൬ ഋೞ೗೚೟
೚೑೑ೞ೐೟ ೆಽ − ഋ
,೚೑೑ೞ೐೟ ೎
൰ ∙ 2 ವಽ ඐ + ݊஽
ఓ , ,
,
ଶ ଶ ೚೑೑ೞ೐೟ ವಽ ೎ , , ,
is before the slot for the active DL BWP change on serving cell c or the active UL BWP change on the
PCell
݊஽ = ݊ ஽ + 1;
else
while r < C (R )
if the UE is provided tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated and,

ேೆಽ ೚೑೑ೞ೐೟ ேೞ೗೚೟ ವಽ
for each slot from slot උ൫݊୙ − ‫ܭ‬ଵ ௞ ൯ ∙ 2ఓವಽିఓೆಽ ඏ + ඌ൬ ഋೞ೗೚೟ ,
೚೑೑ೞ೐೟ ೆಽ − ഋ
೚೑೑ೞ೐೟ ೎
൰ ∙ 2 ವಽ ඐ + ݊஽ −
, ఓ ,
,
ଶ ଶ ೚೑೑ೞ೐೟ ವಽ ೎
, , ,
ೆಽ ವಽ
௥௘௣௘௔௧ ௠௔௫
ܰ௉஽ௌ஼ு
,
+ 1 to slot උ൫݊୙ − ‫ܭ‬ଵ ௞ ൯ ∙ 2ఓವಽିఓೆಽ ඏ + ඌ൬ଶேഋೞ೗೚೟
,
೚೑೑ೞ೐೟ ேೞ೗೚೟ ೚೑೑ೞ೐೟ ೎
೚೑೑ೞ೐೟ ೆಽ ଶ ೚೑೑ೞ೐೟ ವಽ ೎ ൰ ∙ 2 ඐ + ݊஽ , at least
,
− ഋ ,
ఓವಽ
,
,
,
one symbol of the PDSCH time resource derived by row r is configured as UL where K1,k is the k-th
slot timing value in set K 1 ,
R = R\ r ;
else
r = r +1 ;
end if
end while
if the UE does not indicate a capability to receive more than one unicast PDSCH per slot and R ≠ ∅ ,
M A, c = M A, c U j ;
j = j +1 ;
else
Set m to the smallest last OFDM symbol index, as determined by the SLIV, among all rows of R
while R ≠∅
Set r =0
while r < C (R)
if S ≤ m for start OFDM symbol index S for row r
br ,k ,n = j ; - index of occasion for candidate PDSCH reception or SPS PDSCH release

D
associated with row r
R=R\ r ;
ETSI
B = B U br ,k ,n ;
D
else
r = r + 1;
end if
end while
M A,c = M A,c U j;
j = j +1 ;
Set m to the smallest last OFDM symbol index among all rows of R ;
end while
end if
݊஽ = ݊ ஽ + 1;
end if
end while
end if
k = k +1 ;
end while
end if
If the UE indicates a capability to receive more than one PDSCH per slot, for occasions of candidate PDSCH receptions
corresponding to rows of ܴ associated with a same value of br ,k,nD , where br , k ,n D ∈ B , the UE does not expect to receive
more than one PDSCH in a same DL slot.
If a UE receives a SPS PDSCH, or a SPS PDSCH release, or a PDSCH that is scheduled by a DCI format that does not
support CBG-based PDSCH receptions and if
- the UE is configured with one serving cell, and
- C (M ) = 1 , and
A, c
- PDSCH-CodeBlockGroupTransmission is provided to the UE
the UE generates HARQ-ACK information only for the transport block in the PDSCH or only for the SPS PDSCH
release.
If a UE receives a SPS PDSCH, or a SPS PDSCH release, or a PDSCH that is scheduled by a DCI format that does not
support CBG-based PDSCH receptions and if
- the UE is configured with more than one serving cells, or
- ( )
C M A,c > 1 , and
- PDSCH-CodeBlockGroupTransmission is provided to the UE

CBG/TB, max
the UE repeats N HARQ − ACK times the HARQ-ACK information for the transport block in the PDSCH or for the SPS
PDSCH release.
A UE does not expect to detect a DCI format switching a DL BWP within N 3 symbols prior to a first symbol of a
PUCCH transmission where the UE multiplexes HARQ-ACK information, where N 3 is defined in clause 9.2.3.
ETSI
If a UE is provided dl-DataToUL-ACK or dl-DataToUL-ACK-ForDCIFormat1_2, the UE does not expect to be

indicated by DCI format 1_0 a slot timing value for transmission of HARQ-ACK information that does not belong to
the intersection of the set of slot timing values {1, 2, 3, 4, 5, 6, 7, 8} and the set of slot timing values provided by ଵ for
the active DL BWP of a corresponding serving cell.
If maxNrofCodeWordsScheduledByDCI indicates reception of two transport blocks, when the UE receives a PDSCH
with one transport block or a SPS PDSCH release, the HARQ-ACK information is associated with the first transport
block and the UE generates a NACK for the second transport block if harq-ACK-SpatialBundlingPUCCH is not
provided and generates HARQ-ACK information with value of ACK for the second transport block if harq-ACK-
SpatialBundlingPUCCH is provided.
A UE determines ଴஺஼௄ , ଵ஺஼௄ ,...,ை஺஼௄

ಲ಴಼ ିଵ HARQ-ACK information bits, for a total number of OACK HARQ-ACK
information bits, of a HARQ-ACK codebook for transmission in a PUCCH according to the following pseudo-code. In
the following pseudo-code, if the UE does not receive a transport block or a CBG, due to the UE not detecting a
corresponding DCI format, the UE generates a NACK value for the transport block or the CBG. The cardinality of the
set M A,c defines a total number M c of occasions for PDSCH reception or SPS PDSCH release for serving cell c
corresponding to the HARQ-ACK information bits.
Set c = 0 – serving cell index: lower indexes correspond to lower RRC indexes of corresponding cells including, when
applicable, cells in the set 0 and the set ଵ
Set j = 0 - HARQ-ACK information bit index
DL
Set Ncells to the number of serving cells configured by higher layers for the UE
while c < Ncells

DL
Set m = 0 – index of occasion for candidate PDSCH reception or SPS PDSCH release
while m < M c
if harq-ACK-SpatialBundlingPUCCH is not provided, PDSCH-CodeBlockGroupTransmission is not

provided, and the UE is configured by maxNrofCodeWordsScheduledByDCI with reception of two
transport blocks for the active DL BWP of serving cell c ,
o~jACK = HARQ-ACK information bit corresponding to a first transport block of this cell;
j = j +1 ;
o~jACK = HARQ-ACK information bit corresponding to a second transport block of this cell;
j = j +1 ;
elseif harq-ACK-SpatialBundlingPUCCH is provided, and the UE is configured by

maxNrofCodeWordsScheduledByDCI with reception of two transport blocks for the active DL BWP of
serving cell c ,
o~jACK = binary AND operation of the HARQ-ACK information bits corresponding to first and second
transport blocks of this cell - if the UE receives one transport block, the UE assumes ACK for the
second transport block;
j = j +1 ;
CBG/TB, max
elseif PDSCH-CodeBlockGroupTransmission is provided, and N HARQ −ACK, c CBGs are indicated by
maxCodeBlockGroupsPerTransportBlock for serving cell c ,
Set nCBG = 0 - CBG index
ETSI
while nCBG < N HARQ −ACK, c

CBG/TB, max
o~jACK
+ nCBG = HARQ-ACK information bit corresponding to CBG
nCBG of the first transport block;
if the UE is configured by maxNrofCodeWordsScheduledByDCI with reception of two transport

blocks for the active DL BWP of serving cell c
o~jACK
+n CBG/TB,max = HARQ-ACK information bit corresponding to CBG nCBG of the second
CBG + N HARQ−ACK,c
transport block;
end if
nCBG = nCBG +1 ;
end while
j = j + NTB,
DL
c ⋅ N HARQ − ACK , c , where NTB,c is the value of maxNrofCodeWordsScheduledByDCI for the
CBG/TB,max DL
active DL BWP of serving cell c ;
else
o~jACK = HARQ-ACK information bit of serving cell c ;
j = j +1 ;
end if
m = m +1 ;
end while
c = c +1 ;
end while
If OACK + OSR + OCSI ≤ 11 , the UE determines a number of HARQ-ACK information bits n HARQ - ACK for obtaining a
DL
N cells −1 M c −1 DL
N cells −1 M c −1
transmission power for a PUCCH, as described in clause 7.2.1, as nHARQ-ACK =  N
c =0 m=0
received
m ,c +  N
c =0 m=0
received,CBG
m ,c
where
- N mreceived
,c is the number of transport blocks the UE receives in PDSCH reception occasion m for serving cell c if
harq-ACK-SpatialBundlingPUCCH and PDSCH-CodeBlockGroupTransmission are not provided, or the number
of transport blocks the UE receives in PDSCH reception occasion m for serving cell c if PDSCH-
CodeBlockGroupTransmission is provided and the PDSCH reception is scheduled by a DCI format that does not
support CBG-based PDSCH receptions, or the number of PDSCH receptions if harq-ACK-
SpatialBundlingPUCCH is provided or SPS PDSCH release in PDSCH reception occasion m for serving cell c
and the UE reports corresponding HARQ-ACK information in the PUCCH.
- N mreceived,
,c
CBG
is the number of CBGs the UE receives in a PDSCH reception occasion m for serving cell c if
PDSCH-CodeBlockGroupTransmission is provided and the PDSCH reception is scheduled by a DCI format that
supports CBG-based PDSCH receptions and the UE reports corresponding HARQ-ACK information in the
PUCCH.
9.1.2.2 Type-1 HARQ-ACK codebook in physical uplink shared channel

If a UE would multiplex HARQ-ACK information in a PUSCH transmission that is not scheduled by a DCI format or is
scheduled by a DCI format that does not include a DAI field, then
ETSI
- if the UE has not received any PDSCH or SPS PDSCH release that the UE transmits corresponding HARQ-ACK
information in the PUSCH, based on a value of a respective PDSCH-to-HARQ_feedback timing indicator field
in a DCI format scheduling the PDSCH reception or the SPS PDSCH release or on the value of dl-DataToUL-
ACK if the PDSCH-to-HARQ_feedback timing indicator field is not present in DCI format 1_1 or on the value
of dl-DataToUL-ACK-ForDCI-Format1-2 if the PDSCH-to-HARQ_feedback timing indicator field is not
present in DCI format 1_2, in any of the ௖ occasions for candidate PDSCH receptions by a DCI format or SPS
PDSCH on any serving cell , as described in clause 9.1.2.1, the UE does not multiplex HARQ-ACK
information in the PUSCH transmission;
- else the UE generates the HARQ-ACK codebook as described in clause 9.1.2.1, except that harq-ACK-
SpatialBundlingPUCCH is replaced by harq-ACK-SpatialBundlingPUSCH, unless the UE receives only a SPS
PDSCH release, or only SPS PDSCH reception, or only a PDSCH that is scheduled by DCI format 1_0 with a
counter DAI field value of 1 on the PCell in the ௖ occasions for candidate PDSCH receptions in which case the
UE generates HARQ-ACK information only for the SPS PDSCH release or only for the PDSCH reception as
described in clause 9.1.2.
A UE sets to NACK value in the HARQ-ACK codebook any HARQ-ACK information corresponding to PDSCH
reception or SPS PDSCH release that the UE detects in a PDCCH monitoring occasion that starts after a PDCCH
monitoring occasion where the UE detects a DCI format scheduling the PUSCH transmission.
A UE does not expect to detect a DCI format switching a DL BWP within ଶ symbols prior to a first symbol of a
PUSCH transmission where the UE multiplexes HARQ-ACK information, where ଶ is defined in [6, TS 38.214].
If a UE multiplexes HARQ-ACK information in a PUSCH transmission that is scheduled by DCI format that includes a
DAI field, the UE generates the HARQ-ACK codebook as described in clause 9.1.2.1 when a value of the DAI field is
T-DAI
UL = 1 except that harq-ACK-SpatialBundlingPUCCH is replaced by harq-ACK-SpatialBundlingPUSCH. The UE
does not generate a HARQ-ACK codebook for multiplexing in the PUSCH transmission when T-DAI UL = 0 unless the UE
receives only a SPS PDSCH release, or only SPS PDSCH(s), or only a PDSCH that is scheduled by DCI format 1_0
with a counter DAI field value of 1 on the PCell in the ௖ occasions for candidate PDSCH receptions in which case the
UE generates HARQ-ACK information only for the SPS PDSCH release or only for the PDSCH reception as described
in clause 9.1.2. T-DAI
UL = 0 if the PUSCH is scheduled by a DCI format that includes a DAI field and the DAI field is set
to '0'; otherwise, T-DAI
UL = 1.

This clause applies if the UE is configured with pdsch-HARQ-ACK-Codebook = dynamic or with pdsch-HARQ-ACK-
Codebook-r16. Unless stated otherwise, a PDSCH-to-HARQ_feedback timing indicator field provides an applicable
value.
A UE does not expect to multiplex in a Type-2 HARQ-ACK codebook HARQ-ACK information that is in response to a
detection of a DCI format that does not include a counter DAI field.
If a UE receives a first DCI format that the UE detects in a first PDCCH monitoring occasion and includes a PDSCH-
to-HARQ_feedback timing indicator field providing an inapplicable value from dl-DataToUL-ACK-r16,
- if the UE detects a second DCI format, the UE multiplexes the corresponding HARQ-ACK information in a
PUCCH or PUSCH transmission in a slot that is indicated by a value of a PDSCH-to-HARQ_feedback timing
indicator field in the second DCI format, where
- if the UE is not provided pdsch-HARQ-ACK-Codebook-r16, the UE detects the second DCI format in any
PDCCH monitoring occasion after the first one, and where the slot indicated by the value of the PDSCH-to-
HARQ_feedback timing indicator field in the second DCI format is no later than a slot for HARQ-ACK
information in response to a SPS PDSCH reception, if any, received after the PDSCH scheduled by the first
DCI format.
- if the UE is provided pdsch-HARQ-ACK-Codebook-r16, the UE detects the second DCI format in any
PDCCH monitoring occasion after the first one, and the second DCI format indicates a HARQ-ACK
information report for a same PDSCH group index as indicated by the first DCI format as described in clause
9.1.3.3, and where the slot indicated by the value of the PDSCH-to-HARQ_feedback timing indicator field in
the second DCI format is no later than a slot for HARQ-ACK information in response to a SPS PDSCH
reception, if any, received after the PDSCH scheduled by the first DCI format.
ETSI
- if the UE is provided pdsch-HARQ-ACK-Codebook-r16, the UE receives the second DCI format later than
the slot for HARQ-ACK information in response to a SPS PDSCH reception received after the PDSCH
scheduled by the first DCI format, and the second DCI format indicates a HARQ-ACK information report for
a same PDSCH group index as indicated by the first DCI format as described in clause 9.1.3.3.
- if the UE is provided pdsch-HARQ-ACK-OneShotFeedback, the first DCI format does not indicate SPS
PDSCH release or SCell dormancy, the UE detects the second DCI format in any PDCCH monitoring
occasion after the first one, and the second DCI format includes a One-shot HARQ-ACK request field with
value 1, the UE includes the HARQ-ACK information in a Type-3 HARQ-ACK codebook, as described in
clause 9.1.4, and where the slot indicated by the value of the PDSCH-to-HARQ_feedback timing indicator
field in the second DCI format is no later than a slot for HARQ-ACK information in response to a SPS
PDSCH reception, if any, received after the PDSCH scheduled by the first DCI format.
- if the UE is provided pdsch-HARQ-ACK-OneShotFeedback-r16, the first DCI format does not indicate SPS
PDSCH release or SCell dormancy, and the UE receives the second DCI format later than the slot for
HARQ-ACK information in response to a SPS PDSCH reception received after the PDSCH scheduled by the
first DCI format, and the second DCI format includes a One-shot HARQ-ACK request field with value 1, the
UE includes the HARQ-ACK information in a Type-3 HARQ-ACK codebook, as described in clause 9.1.4.
- otherwise, the UE does not multiplex the corresponding HARQ-ACK information in a PUCCH or PUSCH
transmission.

A UE determines monitoring occasions for PDCCH with DCI format scheduling PDSCH receptions or SPS PDSCH
release or indicating SCell dormancy on an active DL BWP of a serving cell , as described in clause 10.1, and for
which the UE transmits HARQ-ACK information in a same PUCCH in slot based on
- PDSCH-to-HARQ_feedback timing indicator field values for PUCCH transmission with HARQ-ACK
information in slot in response to PDSCH receptions, SPS PDSCH release or SCell dormancy indication
- slot offsets ଴ [6, TS 38.214] provided by time domain resource assignment field in a DCI format scheduling
PDSCH receptions and by pdsch-AggregationFactor, or pdsch-AggregationFactor-r16, or repetitionNumber,
when provided.
The set of PDCCH monitoring occasions for a DCI format scheduling PDSCH receptions or SPS PDSCH release or
indicating SCell dormancy is defined as the union of PDCCH monitoring occasions across active DL BWPs of
configured serving cells. PDCCH monitoring occasions are indexed in an ascending order of their start times. The
cardinality of the set of PDCCH monitoring occasions defines a total number of PDCCH monitoring occasions.
A value of the counter downlink assignment indicator (DAI) field in DCI formats denotes the accumulative number of
{serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH reception(s), SPS PDSCH release or SCell
dormancy indication associated with the DCI formats is present up to the current serving cell and current PDCCH
monitoring occasion,
- first, if the UE indicates by type2-HARQ-ACK-Codebook support for more than one PDSCH reception on a
serving cell that are scheduled from a same PDCCH monitoring occasion, in increasing order of the PDSCH
reception starting time for the same {serving cell, PDCCH monitoring occasion} pair,
- second in ascending order of serving cell index, and
- third in ascending order of PDCCH monitoring occasion index

, where 0 ≤
< .
If, for an active DL BWP of a serving cell, the UE is not provided coresetPoolIndex or is provided coresetPoolIndex
with value 0 for one or more first CORESETs and is provided coresetPoolIndex with value 1 for one or more second
CORESETs, and is provided ackNackFeedbackMode = joint, the value of the counter DAI is in the order of the first
CORESETs and then the second CORESETs for a same serving cell index and a same PDCCH monitoring occasion
index.
The value of the total DAI, when present [5, TS 38.212], in a DCI format denotes the total number of {serving cell,
PDCCH monitoring occasion}-pair(s) in which PDSCH reception(s), SPS PDSCH release or SCell dormancy indication
associated with DCI formats is present, up to the current PDCCH monitoring occasion
and is updated from PDCCH
monitoring occasion to PDCCH monitoring occasion. If, for an active DL BWP of a serving cell, the UE is not provided
coresetPoolIndex or is provided coresetPoolIndex with value 0 for one or more first CORESETs and is provided
ETSI
coresetPoolIndex with value 1 for one or more second CORESETs, and is provided ackNackFeedbackMode = joint,
the total DAI value counts the {serving cell, PDCCH monitoring occasion}-pair(s) for both the first CORESETs and the
second CORESETs.
DL
Denote by ஼ିDAI
DL the number of bits for the counter DAI and set ஽ = 2ே಴షDAI . Denote by େିDAI,
DL
c,m the value of the
counter DAI in a DCI format scheduling PDSCH reception, SPS PDSCH release or SCell dormancy indication on
serving cell in PDCCH monitoring occasion
according to Table 9.1.3-1 or Table 9.1.3-1A. Denote by ୘ିDAI, DL
m the
value of the total DAI in a DCI format in PDCCH monitoring occasion
according to Table 9.1.3-1. The UE assumes
a same value of total DAI in all DCI formats that include a total DAI field in PDCCH monitoring occasion
. A UE
does not expect to multiplex, in a same Type-2 HARQ-ACK codebook, HARQ-ACK information that is in response to
detection of DCI formats with different number of bits for the counter DAI field.
If the UE transmits HARQ-ACK information in a PUCCH in slot and for any PUCCH format, the UE determines the
଴஺஼௄ ଵ஺஼௄
, ,⋯,ை஺஼௄
ఽిే ିଵ , for a total number of ୅େ୏ HARQ-ACK information bits, according to the following pseudo-
code:
Set
= 0 – PDCCH with DCI format scheduling PDSCH reception, SPS PDSCH release or SCell dormancy
indication monitoring occasion index: lower index corresponds to earlier PDCCH monitoring occasion
Set = 0
Set ௧௘௠௣ = 0
Set ௧௘௠௣ଶ = 0
Set ௦ = ∅
Set ୡୣ୪୪ୱ
DL to the number of serving cells configured by higher layers for the UE
- if, for an active DL BWP of a serving cell, the UE is not provided coresetPoolIndex or is provided
coresetPoolIndex with value 0 for one or more first CORESETs and is provided coresetPoolIndex with value 1
for one or more second CORESETs, and is provided ACKNackFeedbackMode = JointFeedback, the serving cell
is counted two times where the first time corresponds to the first CORESETs and the second time corresponds to
the second CORESETs
- if the UE indicates type2-HARQ-ACK-Codebook, a serving cell is counted ୔ୈୗେୌ

MO times where ୔ୈୗେୌ
MO is the
number of PDSCH receptions that can be scheduled for the serving cell by DCI formats in PDCCH receptions at
a same PDCCH monitoring occasion based on the reported value of type2-HARQ-ACK-Codebook
Set to the number of PDCCH monitoring occasion(s)
while
<
Set = 0 – serving cell index: lower indexes correspond to lower RRC indexes of corresponding cell
while < ୡୣ୪୪ୱ

DL
if PDCCH monitoring occasion

is before an active DL BWP change on serving cell or an active UL
BWP change on the PCell and an active DL BWP change is not triggered in PDCCH monitoring occasion

= + 1 ;
else
if there is a PDSCH on serving cell associated with PDCCH in PDCCH monitoring occasion
, or
there is a PDCCH indicating SPS PDSCH release or SCell dormancy on serving cell
if ஼ି
DL
DAI,௖,௠ ≤ ௧௘௠௣
j = j + 1
end if
௧௘௠௣ ஼ି
DL
=
DAI,௖,௠
ETSI
if T-D
DL
AI,௠ = ∅
௧௘௠௣,ଶ ஼ି
DL
=
DAI,௖,௠
else
௧௘௠௣,ଶ ்ି
DL
=
DAI,௠
end if
if harq-ACK-SpatialBundlingPUCCH is not provided and the UE is configured by

maxNrofCodeWordsScheduledByDCI with reception of two transport blocks for at least one
configured DL BWP of at least one serving cell,
ଶ⋅்
஺஼௄
ವಽ
ವ⋅௝ାଶ൫௏಴షವಲ಺,೎,೘ ିଵ൯
= HARQ-ACK information bit corresponding to the first transport block of
this cell
ଶ⋅்
஺஼௄
ವಽ
ವ⋅௝ାଶ൫௏಴షವಲ಺,೎,೘ ିଵ൯ାଵ
= HARQ-ACK information bit corresponding to the second transport
block of this cell
௦ ௦ ஽
= ∪ 2 ⋅ ⋅ + 2 ஼ି
DL
DAI,௖,௠ − 1 , 2 ⋅ ஽
⋅ + 2 ஼ି
DL
DAI,௖,௠ − 1 + 1
elseif harq-ACK-SpatialBundlingPUCCH is provided to the UE and
is a monitoring occasion for
PDCCH with a DCI format that supports PDSCH reception with two transport blocks and the UE is
configured by maxNrofCodeWordsScheduledByDCI with reception of two transport blocks in at least
one configured DL BWP of a serving cell,
்஺஼௄ DL
ವ⋅௝ା௏಴షDAI,೎,೘ ିଵ
= binary AND operation of the HARQ-ACK information bits corresponding to
the first and second transport blocks of this cell
௦ ௦ ஽ ஼ି
= ∪
DL
DAI,௖,௠
⋅ + − 1
else
்஺஼௄ ವಽ
ವ⋅௝ା௏಴షವಲ಺,೎,೘ ିଵ
= HARQ-ACK information bit of this cell
௦ ௦ ஽ ஼ି
= ∪
DL
DAI,௖,௠
⋅ + − 1
end if
end if
= + 1
end if
end while

= + 1
end while
௧௘௠௣
்ସವ ்ସವ ௧௘௠௣
= × +
if UE does not set ‫݌݉݁ݐ‬2 = ܷ‫ܮ‬

T−‫ ܫܣܦ‬and ‫ܦ‬ = 2
‫݌݉݁ݐ‬2 = ‫݌݉݁ݐ‬
end if
஽

×
=
4
ETSI
if ௧௘௠௣ଶ < ௧௘௠௣

= + 1
end if
if harq-ACK-SpatialBundlingPUCCH is not provided to the UE and the UE is configured by

maxNrofCodeWordsScheduledByDCI with reception of two transport blocks for at least one configured DL BWP of
a serving cell,
‫ܭܥܣ‬ = 2 ⋅ ൫4 ⋅ + ‫݌݉݁ݐ‬2 ൯
else
‫ܭܥܣ‬ = 4 ⋅ ‫݌݉݁ݐ‬2
+
end if
௜஺஼௄ = NACK for any ∈ 0,1, ⋯ , ஺஼௄ − 1 \ ௦

If a UE is configured to receive SPS PDSCH and the UE multiplexes HARQ-ACK information for one activated SPS
PDSCH reception in the PUCCH in slot , the UE generates one HARQ-ACK information bit associated with the SPS
PDSCH reception and appends it to the ஺஼௄ HARQ-ACK information bits.
If a UE is configured to receive SPS PDSCH and the UE multiplexes HARQ-ACK information for multiple activated
SPS PDSCH receptions in the PUCCH in slot , the UE generates the HARQ-ACK information as described in clause
9.1.2 and appends it to the ஺஼௄ HARQ-ACK information bits.
For a PDCCH monitoring occasion with DCI format scheduling PDSCH reception or SPS PDSCH release or indicating
SCell dormancy in the active DL BWP of a serving cell, when a UE receives a PDSCH with one transport block or a
SPS PDSCH release or indicating SCell dormancy and the value of maxNrofCodeWordsScheduledByDCI is 2, the
HARQ-ACK information is associated with the first transport block and the UE generates a NACK for the second
transport block if harq-ACK-SpatialBundlingPUCCH is not provided and generates HARQ-ACK information with
value of ACK for the second transport block if harq-ACK-SpatialBundlingPUCCH is provided.
If a UE is not provided PDSCH-CodeBlockGroupTransmission for each of the ୡୣ୪୪ୱDL serving cells, or for PDSCH
receptions scheduled by a DCI format that does not support CBG-based PDSCH receptions, or for SPS PDSCH
reception, or for SPS PDSCH release, or for SCell dormancy indication, and if ACK + SR + CSI ≤ 11, the UE
determines a number of HARQ-ACK information bits HARQ-ACK for obtaining a transmission power for a PUCCH, as
described in clause 7.2.1, as
DL DL
HARQ-ACK HARQ-ACK,TB DAI,௠
=
DL =
last
∑ே௖ୀ଴
cells ିଵ
DAI,௖
஽ ! TB,௠௔௫
−
DL ேcellsିଵ ெିଵ received
∑௖ୀ଴ +∑௠ୀ଴ ௠,௖ SPS,௖ +
where
- if ୡୣ୪୪ୱ
DL = 1, DL
ୈ୅୍,௠ౢ౗౩౪ is the value of the counter DAI in the last DCI format scheduling PDSCH reception or
indicating SPS PDSCH release or indicating SCell dormancy, for any serving cell that the UE detects within
the PDCCH monitoring occasions.
DL > 1
- if the UE does not detect any DCI format that includes a total DAI field in a last PDCCH monitoring
occasion within the PDCCH monitoring occasions where the UE detects at least one DCI format
scheduling PDSCH reception, indicating SPS PDSCH release or indicating SCell dormancy for any serving
cell , ୈ୅୍,௠
DL
ౢ౗౩౪ is the value of the counter DAI in a last DCI format the UE detects in the last PDCCH
monitoring occasion
- if the UE detects at least one DCI format that includes a total DAI field in a last PDCCH monitoring occasion
within the PDCCH monitoring occasions where the UE detects at least one DCI format scheduling
PDSCH reception, indicating SPS PDSCH release or indicating SCell dormancy for any serving cell ,
ୈ୅୍,௠
DL
ౢ౗౩౪ is the value of the total DAI in the at least one DCI format that includes a total DAI field
ETSI
- ୈ୅୍,௠
DL
ౢ౗౩౪= 0 if the UE does not detect any DCI format scheduling PDSCH reception, indicating SPS PDSCH
release or indicating SCell dormancy for any serving cell in any of the PDCCH monitoring occasions.
- DAI,c is the total number of a DCI format scheduling PDSCH reception, indicating SPS PDSCH release or
indicating SCell dormancy that the UE detects within the PDCCH monitoring occasions for serving cell .
DAI,c = 0 if the UE does not detect any DCI format scheduling PDSCH reception, indicating SPS PDSCH
release or indicating SCell dormancy for serving cell in any of the PDCCH monitoring occasions.
- ୘୆,୫ୟ୶
DL = 2 if the value of maxNrofCodeWordsScheduledByDCI is 2 for any serving cell and harq-ACK-
SpatialBundlingPUCCH is not provided; otherwise, ୘୆,୫ୟ୶

DL = 1.
- ௠,௖
received is the number of transport blocks the UE receives in a PDSCH scheduled by a DCI format that the UE
detects in PDCCH monitoring occasion
for serving cell if harq-ACK-SpatialBundlingPUCCH is not
provided, or the number of PDSCH scheduled by a DCI format that the UE detects in PDCCH monitoring
occasion
for serving cell if harq-ACK-SpatialBundlingPUCCH is provided, or the number of DCI format
that the UE detects and indicate SPS PDSCH release in PDCCH monitoring occasion
for serving cell , or the
number of DCI format that the UE detects and indicate SCell dormancy in PDCCH monitoring occasion
for
serving cell .
- SPS,c is the number of SPS PDSCH receptions by the UE on serving cell for which the UE transmits
corresponding HARQ-ACK information in the same PUCCH as for HARQ-ACK information corresponding to
PDSCH receptions within the PDCCH monitoring occasions.
If a UE
- is provided PDSCH-CodeBlockGroupTransmission for ୡୣ୪୪ୱ

DL,CBG
serving cells; and
- is not provided PDSCH-CodeBlockGroupTransmission, for ୡୣ୪୪ୱ

DL,TB
serving cells where ୡୣ୪୪ୱ
DL,TB
+
DL,CBG
ୡୣ୪୪ୱ =
ୡୣ୪୪ୱ
DL
the UE determines the ଴஺஼௄ , ଵ஺஼௄ , ⋯ , ை஺஼௄

ఽిేିଵ according to the previous pseudo-code with the following modifications
- ୡୣ୪୪ୱ
DL is used for the determination of a first HARQ-ACK sub-codebook for
- SPS PDSCH release,
- SPS PDSCH reception,
- DCI format 1_1 indicating SCell dormancy, and
- for TB-based PDSCH receptions on the ୡୣ୪୪ୱ

DL,CBG
serving cells and on the ୡୣ୪୪ୱ
DL,TB
serving cells,
- ୡୣ୪୪ୱ
DL is replaced by DL,CBG for the determination of a second HARQ-ACK sub-codebook corresponding to the
ୡୣ୪୪ୱ
ୡୣ୪୪ୱ
DL,CBG
serving cells for CBG-based PDSCH receptions, and
- if, for an active DL BWP of a serving cell, the UE is not provided coresetPoolIndex or is provided
coresetPoolIndex with value 0 for one or more first CORESETs and is provided coresetPoolIndex with value 1
for one or more second CORESETs, and is provided ackNackFeedbackMode = joint, the serving cell is counted
as two times where the first time corresponds to the first CORESETs and the second time corresponds to the
second CORESETs, and
- instead of generating one HARQ-ACK information bit per transport block for a serving cell from the ୡୣ୪୪ୱ
DL,CBG
serving cells, the UE generates HARQିACK,max HARQ-ACK information bits, where N HARQ−
CBG/TB,max CBG/TB,max
ACK,max is the
maximum value of ୘୆,௖

DL ⋅ CBG/TB,max across all DL,CBG serving cells and N DL is the value of
HARQିACK,c ୡୣ୪୪ୱ TB,c
maxNrofCodeWordsScheduledByDCI for serving cell . If for a serving cell it is ୘୆,௖

DL ⋅ CBG/TB,max
ୌ୅ୖ୕ି୅େ୏,௖ <
CBG/TB,max
ୌ୅ୖ୕ି୅େ୏,୫ୟ୶ , the UE generates NACK for the last HARQିACK,max − ୘୆,௖
CBG/TB,max DL ⋅ CBG/TB,max
HARQିACK,c HARQ-ACK
information bits for serving cell
- the pseudo-code operation when harq-ACK-SpatialBundlingPUCCH is provided is not applicable
- The counter DAI value and the total DAI value apply separately for each HARQ-ACK sub-codebook
ETSI
- The UE generates the HARQ-ACK codebook by appending the second HARQ-ACK sub-codebook to the first
HARQ-ACK sub-codebook
If ACK + SR + CSI ≤ 11, the UE also determines HARQ-ACK = HARQ-ACK,TB HARQ-ACK,CBG for obtaining a
+
PUCCH transmission power, as described in clause 7.2.1, with
∑ே௖ୀ଴ ିଵ
DL,CBG
ேcells ିଵ ெିଵ received,CBG
HARQ-ACK,CBG DAI DAI, ௖
஽ ! HARQିACK,max ∑௖ୀ଴ ∑௠ୀ଴ ௠,௖
DL
DL cells CBG CBG/TB,max
=
,௠last − +
where
DL = 1, DL
ୈ୅୍,௠ౢ౗౩౪ is the value of the counter DAI in the last DCI format scheduling CBG-based PDSCH
reception for any serving cell that the UE detects within the PDCCH monitoring occasions
DL > 1,, DL
ୈ୅୍,௠ౢ౗౩౪ is the value of the total DAI in the last DCI format scheduling CBG-based PDSCH
reception for any serving cell that the UE detects within the PDCCH monitoring occasions
- ୈ୅୍,௠
DL = 0, if the UE does not detect any DCI format scheduling CBG-based PDSCH reception for any
ౢ౗౩౪
serving cell in any of the PDCCH monitoring occasions
- ୈ୅୍,௖
CBG is the total number of DCI formats scheduling CBG-based PDSCH receptions that the UE detects
within the PDCCH monitoring occasions for serving cell . ୈ୅୍,௖

CBG if the UE does not detect any DCI
= 0
format scheduling CBG-based PDSCH reception for serving cell in any of the PDCCH monitoring
occasions
- ௠,௖
received,CBG
is the number of CBGs the UE receives in a PDSCH scheduled by a DCI format that supports
CBG-based PDSCH reception that the UE detects in PDCCH monitoring occasion
for serving cell and
the UE reports corresponding HARQ-ACK information in the PUCCH
Table 9.1.3-1: Value of counter DAI for "DL

࡯ିDAI = # and of total DAI
Number of {serving cell, PDCCH monitoring occasion}-pair(s) in which

DAI
MSB, LSB $ DL
C-DAI or $ DL
T-DAI
PDSCH transmission(s) associated with PDCCH or PDCCH indicating
SPS PDSCH release or DCI format 1_1 indicating SCell dormancy is
present, denoted as ࢅ and ࢅ ≥ ૚
0,0 1 ሺܻ − 1ሻ ݉‫ܶ ݀݋‬஽ + 1 = 1
0,1 2 ሺܻ − 1ሻ ݉‫ܶ ݀݋‬஽ + 1 = 2
1,0 3 ሺܻ − 1ሻ ݉‫ܶ ݀݋‬஽ + 1 = 3
1,1 4 ሺܻ − 1ሻ ݉‫ܶ ݀݋‬஽ + 1 = 4
Table 9.1.3-1A: Value of counter DAI for "DL

࡯ିDAI = %

DAI
C-DAI
DL PDSCH transmission(s) associated with PDCCH or PDCCH indicating
SPS PDSCH release is present, denoted as & and & ≥ 1
0 1 ሺܻ − 1ሻ ݉‫ܶ ݀݋‬஽ + 1 = 1
1 2 ሺܻ − 1ሻ ݉‫ܶ ݀݋‬஽ + 1 = 2

scheduled by a DCI format that does not include a DAI field, then
- if the UE has not received any PDCCH within the monitoring occasions for DCI formats scheduling PDSCH
receptions, or SPS PDSCH release, or DCI format 1_1 indicating SCell dormancy on any serving cell and the
UE does not have HARQ-ACK information in response to a SPS PDSCH reception, or in response to a detection
of a DCI format 1_1 indicating SCell dormancy, to multiplex in the PUSCH, as described in clause 9.1.3.1, the
UE does not multiplex HARQ-ACK information in the PUSCH transmission;
ETSI
- else, the UE generates the HARQ-ACK codebook as described in clause 9.1.3.1, except that harq-ACK-
SpatialBundlingPUCCH is replaced by harq-ACK-SpatialBundlingPUSCH.
If a UE multiplexes HARQ-ACK information in a PUSCH transmission that is scheduled by a DCI format that includes
a DAI field, the UE generates the HARQ-ACK codebook as described in clause 9.1.3.1, with the following
modifications:
- For the pseudo-code for the HARQ-ACK codebook generation in clause 9.1.3.1, after the completion of the
and
loops, the UE sets ௧௘௠௣ଶ = ୘ିDAI
UL where ୘ିDAI
UL is the value of the DAI field according to Table 9.1.3-2
- For the case of first and second HARQ-ACK sub-codebooks, the DCI format includes a first DAI field
corresponding to the first HARQ-ACK sub-codebook and a second DAI field corresponding to the second
HARQ-ACK sub-codebook
- harq-ACK-SpatialBundlingPUCCH is replaced by harq-ACK-SpatialBundlingPUSCH.
If a UE is not provided PDSCH-CodeBlockGroupTransmission and the UE is scheduled for a PUSCH transmission by

DCI format that includes a DAI field with value T-DAI
UL = 4 and the UE has not received any PDCCH within the
monitoring occasions for PDCCH with DCI format scheduling PDSCH receptions or SPS PDSCH release or indicating
SCell dormancy on any serving cell and the UE does not have HARQ-ACK information in response to a SPS PDSCH
reception to multiplex in the PUSCH, as described in clause 9.1.3.1, the UE does not multiplex HARQ-ACK
information in the PUSCH transmission.
If a UE is provided PDSCH-CodeBlockGroupTransmission and the UE is scheduled for a PUSCH transmission by DCI

format that includes a DAI field with first value T-DAI
UL = 4 or with second value UL = 4 and the UE has not received
T-DAI
any PDCCH within the monitoring occasions for PDCCH with DCI format scheduling PDSCH receptions or SPS
PDSCH release, or DCI format 1_1 indicating SCell dormancy, on any serving cell and the UE does not have HARQ-
ACK information in response to a SPS PDSCH reception to multiplex in the PUSCH, as described in clause 9.1.3.1, the
UE does not multiplex HARQ-ACK information for the first sub-codebook or for the second sub-codebook,
respectively, in the PUSCH transmission.
Table 9.1.3-2: Value of DAI

DAI
MSB, LSB $ UL
T-DAI
PDSCH transmission(s) associated with PDCCH or PDCCH indicating
SPS PDSCH release or DCI format 1_1 indicating SCell dormancy is
present, denoted as ࢄ and ࢄ ≥ ૚
0,0 1 ሺܺ − 1ሻ ݉‫ ݀݋‬4 + 1 = 1
0,1 2 ሺܺ − 1ሻ ݉‫ ݀݋‬4 + 1 = 2
1,0 3 ሺܺ − 1ሻ ݉‫ ݀݋‬4 + 1 = 3
1,1 4 ሺܺ − 1ሻ ݉‫ ݀݋‬4 + 1 = 4
9.1.3.3 Type-2 HARQ-ACK codebook grouping and HARQ-ACK retransmission

If a UE is provided pdsch-HARQ-ACK-Codebook, the UE determines HARQ-ACK information for multiplexing in a
PUCCH transmission occasion according to the following procedure.
Set ' to the value of a PDSCH group index field in a last DCI format that provides a value of ' and indicates a PUCCH
transmission occasion.
Set (') to denote a PUCCH transmission occasion for multiplexing HARQ-ACK information
Set ( to the value of a PDSCH-to-HARQ_feedback timing field, if any, in a DCI format providing a value of '
- If the DCI format does not include a PDSCH-to-HARQ_feedback timing field, set ( to the value provided by dl-
DataToUL-ACK
Set ℎ(') to the value of a first New feedback indicator field in the last DCI format providing the value of '
Set ℎሺ௚ାଵሻ௠௢ௗଶ (') to a value of a second New feedback indicator field in the last DCI format providing the value of '
Set ஽஺ூ
ሺ௚ାଵሻ௠௢ௗଶ
to the value of a total DAI field for group ' + 1 !
2 in the last DCI format providing the value of '
ETSI
- If ' = 1 and the UE detects a DCI format that does not include a PDSCH group index field in a PDCCH
reception that is after the PDCCH reception for the last DCI format detection providing the value of ' and
indicating a same slot for a PUCCH transmission occasion, set ୈ୅୍
= ∅
Set ) to the value of a number of requested PDSCH group(s) field in the last DCI format providing the value of g
A UE does not expect to detect DCI formats with respective
- Number of requested PDSCH group(s) field values of 0, and
- PDSCH-to-HARQ_feedback timing field values that indicate a same PUCCH transmission occasion, and
- PDSCH group index field values that are different
Generate first HARQ-ACK information for PUCCH transmission occasion (') in a slot, as described in clause 9.1.3.1,
where
- the first HARQ-ACK information corresponds only to detections of DCI formats each providing a same value of
', of ℎ('), and to detections of DCI formats that do not provide a value of ' and ℎ(') and are associated with a
same value of ', of ℎ('), and at least one of the DCI formats providing a value of ( indicating the slot
- at least one of the DCI formats provides a ℎ(') value
-
= 0 corresponds to a PDCCH monitoring occasion, where the UE detects a DCI format that provides a value
of ' or is associated with a value of ', that is the first PDCCH monitoring occasion after a PDCCH monitoring
occasion where the UE detects another DCI format that provides a value different than ℎ(')
The generation of the first HARQ-ACK information for PUCCH transmission occasion '! in a slot, as described in
clause 9.1.3.1, excludes the generation of HARQ-ACK information for SPS PDSCH receptions.
If ℎሺ௚ାଵሻ௠௢ௗଶ '! = ∅ or ℎሺ௚ାଵሻ௠௢ௗଶ '! = ℎ( ' + 1!

2), generate second HARQ-ACK information for PUCCH
transmission occasion ( ' + 1!
2) in a slot, as described in clause 9.1.3.1, where
- the second HARQ-ACK information corresponds to detections of DCI formats each providing a same value of
' + 1!
2, of ℎ( ' + 1!
2) and to detections of DCI formats that do not provide a value of
' + 1!
2, of ℎ( ' + 1!
2), but are associated with a same value of ' + 1!
2, of ℎ( ' + 1!
2)
- at least one of the DCI formats provides a ℎ( ' + 1 !
2) value
-
= 0 corresponds to a PDCCH monitoring occasion, where the UE detects a DCI format that provides a value
of ' + 1!
2 or that is associated with a value of ' + 1!
2, that is the first PDCCH monitoring
occasion after a PDCCH monitoring occasion where the UE detects another DCI format that provides a value
different than ℎ( ' + 1!
2)
- the PUCCH transmission occasion ( ' + 1!

2) is a last one for multiplexing second HARQ-ACK
information and it is not after PUCCH transmission occasion (')
if ୈ୅୍ ≠ ∅, after the completion of the and

loops for the pseudo-code for the second HARQ-ACK
-
codebook generation in clause 9.1.3.1, set ௧௘௠௣ଶ = ஽஺ூ
. If the UE is provided PDSCH-
CodeBlockGroupTransmission for ୡୣ୪୪ୱ serving cells, set ௧௘௠௣ଶ = ஽஺ூ
ୈ୐,େ୆ୋ ሺ௚ାଵሻ௠௢ௗଶ
for both sub-codebooks
before appending the second sub-codebook to the first sub-codebook.
If ℎሺ௚ାଵሻ௠௢ௗଶ '! ≠ ∅ and ℎሺ௚ାଵሻ௠௢ௗଶ '! ≠ ℎ( ' + 1!

2), generate second HARQ-ACK information as described
in clause 9.1.3.1 by setting = 0 and, after the completion of the and
loops for the pseudo-code for the second
HARQ-ACK codebook generation in clause 9.1.3.1, setting ௧௘௠௣ଶ = ஽஺ூ
.
The generation of the second HARQ-ACK information for PUCCH transmission occasion ( ' + 1!
2) in a slot, as
described in clause 9.1.3.1, excludes the generation of HARQ-ACK information for SPS PDSCH receptions.
If ) = 0 , the UE
includes only the first HARQ-ACK information for multiplexing in PUCCH transmission occasion (')
elseif ) = 1
ETSI
if g = 1
appends the first HARQ-ACK information to the second HARQ-ACK information for multiplexing in PUCCH
transmission occasion (')
else
append the second HARQ-ACK information to the first HARQ-ACK information for multiplexing in PUCCH
transmission occasion (')
end if
end if
The UE appends the HARQ-ACK information corresponding to SPS PDSCH receptions, if any, as described in clause
9.1.3.1, after the first and second, if any, HARQ-ACK information.
If the HARQ-ACK information is multiplexed in a PUSCH transmission, the HARQ-ACK information is determined as
- for multiplexing in PUCCH transmission occasion ('), if the PUSCH transmission is not scheduled by a DCI
format or is scheduled by a DCI format that does not include a DCI field with value ୈ୅୍
୙୐
- for multiplexing in PUCCH transmission occasion ('), if the PUSCH transmission is scheduled by a DCI
format without ul-TotalDAI-Included configured except that for PDSCH group ', the DCI field with value ୈ୅୍
୙୐
in the DCI format is used after the completion of the and
loops for the pseudo-code for the HARQ-ACK
codebook generation in clause 9.1.3.1, and when the HARQ-ACK information multiplexed in the PUCCH
transmission occasion '! does not include HARQ-ACK information for PDSCH group ' + 1!
2
format without ul-TotalDAI-Included configured except that for PDSCH group ' = 0, the DCI field with value
ୈ୅୍
୙୐ in the DCI format is used after the completion of the and
loops for the pseudo-code for the HARQ-
ACK codebook generation in clause 9.1.3.1, and when the HARQ-ACK information multiplexed in the PUCCH
transmission occasion '! includes HARQ-ACK information for PDSCH groups ' and ' + 1!
2
format without ul-TotalDAI-Included configured except that for PDSCH group ' = 0, the DCI field with value
in the DCI format is used after the completion of the and
loops for the pseudo-code for the HARQ-
UL
VDAI
ACK codebook generation in clause 9.1.3.1, and when the UE has not detected any DCI format scheduling
PDSCH receptions, and the UE has not detected any DCI format with a request for HARQ-ACK information for
any PDSCH group
format with ul-TotalDAI-Included configured except that MSBs of the DCI field with value ୈ୅୍
୙୐ in the DCI
format are used for PDSCH group ' = 0, and LSBs of DCI field with value ୈ୅୍ in the DCI format are used for
୙୐
PDSCH group ' = 1, after the completion of the and
loops for the pseudo-code for the HARQ-ACK
codebook generation in clause 9.1.3.1.
If a UE is scheduled a PUSCH transmission by DCI format 0_1 having a DAI field value ୈ୅୍
୙୐ = 4 for a PDSCH group
index, and the UE has not detected any DCI format scheduling PDSCH receptions for the PDSCH group index, and the
UE has not detected any DCI format with a request for HARQ-ACK information for the PDSCH group index, the UE
does not multiplex HARQ-ACK information in the PUSCH transmission for the PDSCH group index.
If a UE detects DCI formats with respective PDSCH-to-HARQ_feedback timing field values indicating a same PUCCH
transmission occasion and none of the DCI formats that the UE detects after a last PUCCH transmission occasion for
' = 0 includes a New feedback indicator field for ' = 0, and at least one of the DCI formats is DCI format 1_0, the UE
generates HARQ-ACK information only for PDSCH receptions scheduled by detections of DCI format 1_0 and SPS
PDSCH releases indicated by detections of DCI format 1_0, as described in clause 9.1.3.1 or 9.1.3.2 for multiplexing in
the PUCCH transmission occasion.
If a DCI format indicating a slot for a PUCCH transmission occasion does not include a New feedback indicator field, a
PDSCH reception scheduled by the DCI format or a SPS PDSCH release indicated by the DCI format is associated with
PDSCH group 0 and a value of h(g) associated with the DCI format is set only if h(g) is provided by another DCI
format that provides a value of h(g) for PDSCH group 0 and indicates the slot for the PUCCH transmission occasion.
ETSI
For PUCCH transmission occasion ('), the UE determines a PUCCH or a PUSCH transmission to multiplex the
HARQ-ACK information according to the procedures in clauses 9.2.3 and 9.2.5.
If ୅େ୏ ୗୖ ୌ୍
+ + , the UE determines a number of HARQ-ACK information bits ୌ୅ୖ୕ି୅େ୏,௚ for group
≤ 11
' and a number of HARQ-ACK information bits ୌ୅ୖ୕ି୅େ୏,(௚ାଵ)௠௢ௗଶ for group ' !
as described in clause
+ 1 2
9.1.3.1 where SPS,௖ is included in ୌ୅ୖ୕ି୅େ୏,௚ and, if ) and ୈ୅୍

= 1 , the UE determines
≠ ∅
ୌ୅ୖ୕ି୅େ୏,(௚ାଵ)௠௢ௗଶ by setting ୈ୅୍,୫ౢ౗౩౪ ஽஺ூ

ୈ୐ ሺ௚ାଵሻ௠௢ௗଶ
= . For obtaining a PUCCH transmission power, if ) ,= 0
ୌ୅ୖ୕ି୅େ୏ ୌ୅ୖ୕ି୅େ୏,௚ ; else, ୌ୅ୖ୕ି୅େ୏ ୌ୅ୖ୕ି୅େ୏,௚ ୌ୅ୖ୕ି୅େ୏,(௚ାଵ)୫୭ୢଶ .

= = +

If a UE is provided pdsch-HARQ-ACK-OneShotFeedback, the UE determines ଴஺஼௄ , ଵ஺஼௄ , … , ை஺஼௄
ಲ಴಼ ିଵ HARQ-ACK
information bits, for a total number of ஺஼௄ HARQ-ACK information bits, of a Type-3 HARQ-ACK codebook
according to the following procedure.
Set ୡୣ୪୪ୱ
ୈ୐ to the number of configured serving cells
Set ୌ୅ୖ୕,௖
ୈ୐ to the value of nrofHARQ-ProcessesForPDSCH for serving cell , if provided; else, set ୌ୅ୖ୕,௖
ୈ୐ = 8
Set ୘୆,௖
ୈ୐ to the value of maxNrofCodeWordsScheduledByDCI for serving cell if harq-ACK-SpatialBundlingPUCCH
is provided and *+ୌ୅ୖ୕ = 0, or if harq-ACK-SpatialBundlingPUCCH is not provided, or if

maxCodeBlockGroupsPerTransportBlock is provided for serving cell ; else, set ୘୆,௖
ୈ୐ = 1
Set ୌ୅ୖ୕ି୅େ୏,௖ to the number of HARQ-ACK information bits per TB for PDSCH receptions on serving cell as
େ୆ୋ/୘୆,୫ୟ୶
described in clause 9.1.1 if maxCodeBlockGroupsPerTransportBlock is provided for serving cell and pdsch-HARQ-
ACK-OneShotFeedbackCBG is provided; else, set ୌ୅ୖ୕ି୅େ୏,௖ = 0
େ୆ୋ/୘୆,୫ୟ୶
Set *+ୌ୅ୖ୕ = 0 if pdsch-HARQ-ACK-OneShotFeedbackNDI is provided; else set *+ୌ୅ୖ୕ = 1
Set = 0 – serving cell index
Set ℎ = 0 – HARQ process number
Set , = 0 – TB index
Set ' = 0 – CBG index
Set = 0
while < ୡୣ୪୪ୱ

ୈ୐
while ℎ < ୌ୅ୖ୕,௖

ୈ୐
if *+ୌ୅ୖ୕ = 0
if ୌ୅ୖ୕ି୅େ୏,௖
େ୆ୋ/୘୆,୫ୟ୶
> 0
while , < ୘୆,௖

ୈ୐
while ' < ୌ୅ୖ୕ି୅େ୏,௖

େ୆ୋ/୘୆,୫ୟ୶
o~jACK = HARQ-ACK information bit for CBG ' of TB , for HARQ process number of
ℎ
serving cell , if any; else, o

~ ACK = 0
j
= + 1
' ' = + 1
end while
ETSI
o~jACK = NDI value indicated in the DCI format corresponding to the HARQ-ACK information
~ ACK = 0
bit(s) for TB , for HARQ process number on serving cell , if any; else, o
ℎ j
' = 0

= + 1
, ,
= + 1
end while
else
while , < ୘୆,௖

ୈ୐
o~jACK = HARQ-ACK information bit for TB , for HARQ process of serving cell , if any; else,
ℎ
o~ ACK = 0
j

= + 1
o~jACK = NDI value indicated in the DCI format corresponding to the HARQ-ACK information
~ ACK = 0
bit(s) for TB , for HARQ process number on serving cell , if any; else, o
ℎ j

= + 1
, ,
= + 1
end while
end if
, = 0
else
if ୌ୅ୖ୕ି୅େ୏,௖
େ୆ୋ/୘୆,୫ୟ୶
> 0
while , < ୘୆,௖

ୈ୐
if UE has obtained HARQ-ACK information for TB , for HARQ process number ℎ on serving cell
corresponding to a PDSCH reception and has not reported the HARQ-ACK information
corresponding to the PDSCH reception

େ୆ୋ/୘୆,୫ୟ୶
o~jACK = HARQ-ACK information bit for CBG ' of TB , for HARQ process number ℎ of
serving cell

= + 1
' '
= + 1
end while
else
େ୆ୋ/୘୆,୫ୟ୶
o~ jACK = NACK
ETSI

= + 1
' '
= + 1
end while
end if
' = 0
, ,
= + 1
end while
else
while , < ୘୆,௖

ୈ୐
if UE has obtained HARQ-ACK information for TB , for HARQ process number ℎ on serving cell
corresponding to a PDSCH reception and has not reported the HARQ-ACK information
corresponding to the PDSCH reception
if harq-ACK-SpatialBundlingPUCCH is not provided
o~jACK = HARQ-ACK information bit for TB , for HARQ process ℎ of serving cell
else
o~jACK = binary AND operation of the HARQ-ACK information bits corresponding to first and
second transport blocks for HARQ process ℎ of serving cell . If the UE receives one
transport block, the UE assumes ACK for the second transport block
end if
= + 1
, , = + 1
else
o~jACK = NACK
= + 1
, , = + 1
end if
end while
end if
, = 0
end if
ℎ = ℎ + 1
end while
ℎ = 0

= + 1
end while
ETSI
If DL
TB,ܿ > 1, when a UE receives a PDSCH with one transport block, the HARQ-ACK information is associated with
the first transport block.
If a UE receives a SPS PDSCH, or a PDSCH that is scheduled by a DCI format that does not support CBG-based
PDSCH receptions for a serving cell and if maxCodeBlockGroupsPerTransportBlock is provided for serving cell ,
and pdsch-HARQ-ACK-OneShotFeedbackCBG is provided, the UE repeats ୌ୅ୖ୕ି୅େ୏,௖ times the HARQ-ACK
େ୆ୋ/୘୆,୫ୟ୶
information for the transport block in the PDSCH.
If a UE detects a DCI format that includes a One-shot HARQ-ACK request field with value 1, the UE determines a
PUCCH or a PUSCH to multiplex a Type-3 HARQ-ACK codebook for transmission in a slot as described in clauses
9.2.3 and 9.2.5. The UE multiplexes only the Type-3 HARQ-ACK codebook in the PUCCH or the PUSCH for
transmission in the slot.
If
- a UE detects a DCI format that includes a One-shot HARQ-ACK request field with value 1, and
- the CRC of the DCI is scrambled by a C-RNTI or an MCS-C-RNTI, and
- resourceAllocation = resourceAllocationType0 and all bits of the frequency domain resource assignment field in
the DCI format are equal to 0, or
the DCI format are equal to 1, or
- resourceAllocation = dynamicSwitch and all bits of the frequency domain resource assignment field in the DCI
format are equal to 0 or 1
the DCI format provides a request for a Type-3 HARQ-ACK codebook report and does not schedule a PDSCH
reception. The UE is expected to provide HARQ-ACK information in response to the request for the Type-3 HARQ-
ACK codebook after symbols from the last symbol of a PDCCH providing the DCI format, where the value of for
- = 0,1,2 is provided in clause 10.2 by replacing "SPS PDSCH release" with "DCI format".
If a UE multiplexes HARQ-ACK information in a PUSCH transmission, the UE generates the HARQ-ACK codebook
as described in this clause except that harq-ACK-SpatialBundlingPUCCH is replaced by harq-ACK-
SpatialBundlingPUSCH.
9.2 UCI reporting in physical uplink control channel

UCI types reported in a PUCCH include HARQ-ACK information, SR, LRR, and CSI. UCI bits include HARQ-ACK
information bits, if any, SR information bits, if any, LRR information bit, if any, and CSI bits, if any. The HARQ-ACK
information bits correspond to a HARQ-ACK codebook as described in clause 9.1. For the remaining of this clause, any
reference to SR is applicable for SR and/or for LRR.
A UE may transmit one or two PUCCHs on a serving cell in different symbols within a slot. When the UE transmits
two PUCCHs in a slot and the UE is not provided ackNackFeedbackMode = separate, at least one of the two PUCCHs
uses PUCCH format 0 or PUCCH format 2.
If a UE is provided ackNackFeedbackMode = separate, the UE may transmit up to two PUCCHs with HARQ-ACK
information in different symbols within a slot.
In clauses 9.2.3, 9.2.5.1 and 9.2.5.2, a UE assumes 11 CRC bits if a number of respective UCI bits is larger than or
equal to 360; otherwise, the UE determines a number of CRC bits based on the number of respective UCI bits as
described in [5, TS 38.212].
9.2.1 PUCCH Resource Sets

If a UE does not have dedicated PUCCH resource configuration, provided by PUCCH-ResourceSet in PUCCH-Config,
a PUCCH resource set is provided by pucch-ResourceCommon through an index to a row of Table 9.2.1-1 for
transmission of HARQ-ACK information on PUCCH in an initial UL BWP of BWP size
PRBs.
ETSI
The PUCCH resource set includes sixteen resources, each corresponding to a PUCCH format, a first symbol, a duration,
a PRB offset ./BWP
offset
, and a cyclic shift index set for a PUCCH transmission.
The UE transmits a PUCCH using frequency hopping if not provided useInterlacePUCCH-PUSCH in BWP-
UplinkCommon; otherwise, the UE transmits a PUCCH without frequency hopping.
An orthogonal cover code with index 0 is used for a PUCCH resource with PUCCH format 1 in Table 9.2.1-1.
The UE transmits the PUCCH using the same spatial domain transmission filter as for a PUSCH transmission scheduled
by a RAR UL grant as described in clause 8.3.
If a UE is not provided any of pdsch-HARQ-ACK-Codebook, pdsch-HARQ-ACK-Codebook-r16, or pdsch-HARQ-ACK-

OneShotFeedback, the UE generates at most one HARQ-ACK information bit.
If the UE provides HARQ-ACK information in a PUCCH transmission in response to detecting a DCI format
scheduling a PDSCH reception or a SPS PDSCH release, the UE determines a PUCCH resource with index 0୔୙େେୌ ,
ଶ⋅௡ిిు,బ
0 ≤ 0୔୙େେୌ ≤ 15, as 0୔୙େେୌ = 1 2 + 2 ⋅ ∆୔ୖ୍ , where େେ୉ is a number of CCEs in a CORESET of a PDCCH
ேిిు
reception with the DCI format, as described in clause 10.1, େେ୉,଴ is the index of a first CCE for the PDCCH reception,
and ∆୔ୖ୍ is a value of the PUCCH resource indicator field in the DCI format.
If ⌊0PUCCH ⁄8⌋ = 0 and a UE is provided a PUCCH resource by pucch-ResourceCommon and is not provided
useInterlacePUCCH-PUSCH in BWP-UplinkCommon
the UE determines the PRB index of the PUCCH transmission in the first hop as ./BWP + ⌊0PUCCH ⁄ୌ ⌋ and the
offset
-
PRB index of the PUCCH transmission in the second hop as BWP − 1 − ./BWP − ⌊0PUCCH ⁄ୌ ⌋, where ୌ is
size offset
the total number of initial cyclic shift indexes in the set of initial cyclic shift indexes
- the UE determines the initial cyclic shift index in the set of initial cyclic shift indexes as 0PUCCH mod ୌ
8 =1
If ⌊PUCCH ⁄ ⌋ and a UE is provided a PUCCH resource by pucch-ResourceCommon and is not provided
useInterlacePUCCH-PUSCH in BWP-UplinkCommon
- size
the UE determines the PRB index of the PUCCH transmission in the first hop as BWP BWP −1−
offset
−
−8
⌊PUCCH ⁄ ୌ⌋ and the PRB index of the PUCCH transmission in the second hop as BWP
offset
+
⌊PUCCH − 8 ⁄ ୌ⌋
- the UE determines the initial cyclic shift index in the set of initial cyclic shift indexes as (rPUCCH − 8) modNCS
If a UE is provided a PUCCH resource by pucch-ResourceCommon and is provided useInterlacePUCCH-PUSCH in

BWP-UplinkCommon
- = +
the UE determines for the PUCCH resource an interlace index
as

଴ ⌊PUCCH ⁄ CS ⌋ mod
where
=
is a number of interlaces [4, TS 38.211] and
଴ BWP
offset is an interlace index offset and offset is as given in
BWP
Table 9.2.1-1
- the UE determines an initial cyclic shift index in a set of initial cyclic shift indexes as PUCCH mod CS , where CS
is the total number of initial cyclic shifts indexes in the set of initial cyclic shift indexes in Table 9.2.1-1
- if pucch-ResourceCommon indicates
- index 0: the first symbol is 9 for a PUCCH resource with PUCCH format 0 if PUCCH ≥ 10
- index 1 or 2: the first symbol is 9 for a PUCCH resource with PUCCH format 0 if PUCCH = 15
- index 3, 7, or 11: an orthogonal cover code with index 1 is used for a PUCCH resource with PUCCH format
1 if PUCCH≥ 10
- the UE does not expect pucch-ResourceCommon to indicate index 15
ETSI
Table 9.2.1-1: PUCCH resource sets before dedicated PUCCH resource configuration
PRB offset Set of initial
Index PUCCH format First symbol Number of symbols offset
RBBWP CS indexes
0 0 12 2 0 {0, 3}
1 0 12 2 0 {0, 4, 8}
2 0 12 2 3 {0, 4, 8}
3 1 10 4 0 {0, 6}
4 1 10 4 0 {0, 3, 6, 9}
5 1 10 4 2 {0, 3, 6, 9}
6 1 10 4 4 {0, 3, 6, 9}
7 1 4 10 0 {0, 6}
8 1 4 10 0 {0, 3, 6, 9}
9 1 4 10 2 {0, 3, 6, 9}
10 1 4 10 4 {0, 3, 6, 9}
11 1 0 14 0 {0, 6}
12 1 0 14 0 {0, 3, 6, 9}
13 1 0 14 2 {0, 3, 6, 9}
14 1 0 14 4 {0, 3, 6, 9}
15 1 0 14 N size
BWP 4 {0, 3, 6, 9}
If a UE has dedicated PUCCH resource configuration, the UE is provided by higher layers with one or more PUCCH
resources.
A PUCCH resource includes the following parameters:
- a PUCCH resource index provided by pucch-ResourceId
- an index of the first PRB prior to frequency hopping or for no frequency hopping by startingPRB, if a UE is not
provided useInterlacePUCCH-PUSCH in BWP-UplinkDedicated
- an index of the first PRB after frequency hopping by secondHopPRB, if a UE is not provided
useInterlacePUCCH-PUSCH in BWP-UplinkDedicated
- an indication for intra-slot frequency hopping by intraSlotFrequencyHopping, if a UE is not provided

useInterlacePUCCH-PUSCH in BWP-UplinkDedicated
- an index of a first interlace by interlace0, if a UE is provided useInterlacePUCCH-PUSCH in BWP-

UplinkDedicated
- if provided, an index of a second interlace by interlace1, if a UE is provided useInterlacePUCCH-PUSCH in

BWP-UplinkDedicated
- an index of an RB set by rb-SetIndex, if a UE is provided useInterlacePUCCH-PUSCH in BWP-

UplinkDedicated
- a configuration for a PUCCH format provided by format
The UE expects that useInterlacePUCCH-PUSCH in BWP-UplinkCommon and useInterlacePUCCH-PUSCH in BWP-

UplinkDedicated are provided either in all UL BWPs or in none of the UL BWPs for a serving cell.
If a UE is provided useInterlacePUCCH-PUSCH in BWP-UplinkDedicated, the UE determines available RBs for

PUCCH transmissions within the active UL BWP as the intersection of RBs corresponding to an interlace index
provided by interlace0 and, if provided, interlace1, and RBs of an RB set provided by rb-SetIndex. The intersection
results in interlace,0
PUCCH RBs in the first interlace and the UE expects that PUCCH is either 10 or 11. If interlace1 is
interlace,0
provided, the intersection results in interlace,1
PUCCH RBs in the second interlace and the UE expects that PUCCH is either
interlace,1
10 or 11.
If the format indicates PUCCH-format0, the PUCCH format configured for a PUCCH resource is PUCCH format 0,
where the PUCCH resource also includes an index for an initial cyclic shift provided by initialCyclicShift, a number of
symbols for a PUCCH transmission provided by nrofSymbols, a first symbol for the PUCCH transmission provided by
startingSymbolIndex.
ETSI
where the PUCCH resource also includes an index for an initial cyclic shift provided by initialCyclicShift, a number of
symbols for a PUCCH transmission provided by nrofSymbols, a first symbol for the PUCCH transmission provided by
startingSymbolIndex, and an index for an orthogonal cover code by timeDomainOCC.
If the format indicates PUCCH-format2 or PUCCH-format3, the PUCCH format configured for a PUCCH resource is
PUCCH format 2 or PUCCH format 3, respectively, where the PUCCH resource also includes a number of PRBs
provided by nrofPRBs, a number of symbols for a PUCCH transmission provided by nrofSymbols, and a first symbol
for the PUCCH transmission provided by startingSymbolIndex. If a UE is provided by useInterlacePUCCH-PUSCH in
BWP-UplinkDedicated, and the format indicates PUCCH-format2 or PUCCH-format3 and PUCCH-ResourceExt is
provided, the PUCCH resource also includes an index of a second interlace by interlace1, if provided; otherwise, if
interlace1 is not provided, the PUCCH resource also includes, if provided, an orthogonal cover code length by occ-
Length and an orthogonal cover code index by occ-Index. If the format indicates PUCCH-format3 and PUCCH-
ResourceExt is provided, the UE assumes that the RB PUCCH,ଷ
[4, TS38.211] PRBs with the lowest indexes within the
first, and if configured, second interlace are used for PUCCH transmission.
where the PUCCH resource also includes a number of symbols for a PUCCH transmission provided by nrofSymbols, an
orthogonal cover code length by occ-Length, an orthogonal cover code index by occ-Index, and a first symbol for the
PUCCH transmission provided by startingSymbolIndex.
If a UE is provided subslotLengthForPUCCH in a PUCCH-Config, the first symbol of a PUCCH resource provided by

PUCCH-ResourceSet or SPS-PUCCH-AN-List in PUCCH-Config or by n1PUCCH-AN in SPS-Config for multiplexing
HARQ-ACK in a PUCCH transmission is relative to the first symbol of the subslotLengthForPUCCH symbols [12, TS
38.331]. For the remaining cases, the first symbol of a PUCCH resource is relative to the first symbol of a slot with
slot
sym symbols [4, TS 38.211].
A UE can be configured up to four sets of PUCCH resources in a PUCCH-Config. A PUCCH resource set is provided
by PUCCH-ResourceSet and is associated with a PUCCH resource set index provided by pucch-ResourceSetId, with a
set of PUCCH resource indexes provided by resourceList that provides a set of pucch-ResourceId used in the PUCCH
resource set, and with a maximum number of UCI information bits the UE can transmit using a PUCCH resource in the
PUCCH resource set provided by maxPayloadSize. For the first PUCCH resource set, the maximum number of UCI
information bits is 2. A maximum number of PUCCH resource indexes for a set of PUCCH resources is provided by
maxNrofPUCCH-ResourcesPerSet. The maximum number of PUCCH resources in the first PUCCH resource set is 32
and the maximum number of PUCCH resources in the other PUCCH resource sets is 8.
If the UE transmits UCI UCI information bits, that include HARQ-ACK information bits, the UE determines a PUCCH
resource set to be
- a first set of PUCCH resources with pucch-ResourceSetId = 0 if UCI ≤2 including 1 or 2 HARQ-ACK

information bits and a positive or negative SR on one SR transmission occasion if transmission of HARQ-ACK
information and SR occurs simultaneously, or
- a second set of PUCCH resources with pucch-ResourceSetId = 1, if provided by higher layers, if 2<
UCI ଶ ≤
where ଶ is equal to maxPayloadSize if maxPayloadSize is provided for the PUCCH resource set with pucch-
ResourceSetId = 1; otherwise ଶ is equal to 1706, or
- <
a third set of PUCCH resources with pucch-ResourceSetId = 2, if provided by higher layers, if ଶ UCI ଷ ≤
where ଷ is equal to maxPayloadSize if maxPayloadSize is provided for the PUCCH resource set with pucch-
ResourceSetId = 2; otherwise ଷ is equal to 1706, or
- a fourth set of PUCCH resources with pucch-ResourceSetId = 3, if provided by higher layers, if ଷ < UCI ≤
1706.
If the UE is provided SPS-PUCCH-AN-List and transmits UCI UCI information bits that include only HARQ-ACK
information bits in response to one or more SPS PDSCH receptions and SR, if any, the UE determines a PUCCH
resource to be
- a PUCCH resource provided by sps-PUCCH-AN-ResourceID obtained from the first entry in sps-PUCCH-AN-
≤2
List if UCI including 1 or 2 HARQ-ACK information bits and a positive or negative SR on one SR
transmission occasion if transmission of HARQ-ACK information and SR occurs simultaneously, or
ETSI
- a PUCCH resource provided by sps-PUCCH-AN-ResourceID obtained from the second entry in sps-PUCCH-
2<
AN-List, if provided, if ≤
UCI ଵ,ௌ௉ௌ where ଵ,ௌ௉ௌ is either provided by maxPayloadSize obtained from the
second entry in sps-PUCCH-AN-List or is otherwise equal to 1706, or
- a PUCCH resource provided by sps-PUCCH-AN-ResourceID obtained from the third entry in sps-PUCCH-AN-
<
List, if provided, if ଵ,ௌ௉ௌ UCI ≤ ଶ,ௌ௉ௌ where ଶ,ௌ௉ௌ is either provided by maxPayloadSize obtained from the
third entry in sps-PUCCH-AN-List or is otherwise equal to 1706, or
- a PUCCH resource provided by sps-PUCCH-AN-ResourceID obtained from the fourth entry in sps-PUCCH-AN-
<
List, if provided, if 2,ܵܲܵ UCI ≤3,ܵܲܵ where 3,ܵܲܵ is equal to 1706.
9.2.2 PUCCH Formats for UCI transmission

If a UE is not transmitting PUSCH, and the UE is transmitting UCI, the UE transmits UCI in a PUCCH using
- PUCCH format 0 if
- the transmission is over 1 symbol or 2 symbols,
- the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK/SR bits) is 1 or 2
- PUCCH format 1 if
- the transmission is over 4 or more symbols,
- the number of HARQ-ACK/SR bits is 1 or 2
- PUCCH format 2 if
- the transmission is over 1 symbol or 2 symbols,
- the number of UCI bits is more than 2
- PUCCH format 3 if
- the number of UCI bits is more than 2,
- the PUCCH resource does not include an orthogonal cover code, or the UE is provided useInterlacePUCCH-
PUSCH in BWP-UplinkDedicated
- PUCCH format 4 if
- the number of UCI bits is more than 2,
- the PUCCH resource includes an orthogonal cover code and the UE is not provided useInterlacePUCCH-
PUSCH in BWP-UplinkDedicated
A spatial setting for a PUCCH transmission is provided by PUCCH-SpatialRelationInfo if the UE is configured with a
single value for pucch-SpatialRelationInfoId; otherwise, if the UE is provided multiple values for PUCCH-
SpatialRelationInfo, the UE determines a spatial setting for the PUCCH transmission as described in [11, TS 38.321].
The UE applies corresponding actions in [11, TS 38.321] and a corresponding setting for a spatial domain filter to
subframe,μ
transmit PUCCH in the first slot that is after slot k + 3 ⋅ Nslot where k is the slot where the UE would transmit a
PUCCH with HARQ-ACK information with ACK value corresponding to a PDSCH reception providing the PUCCH-
SpatialRelationInfo and μ is the SCS configuration for the PUCCH
- If PUCCH-SpatialRelationInfo provides ssb-Index, the UE transmits the PUCCH using a same spatial domain
filter as for a reception of a SS/PBCH block with index provided by ssb-Index for a same serving cell or, if
servingCellId is provided, for a serving cell indicated by servingCellId
ETSI
- else if PUCCH-SpatialRelationInfo provides csi-RS-Index, the UE transmits the PUCCH using a same spatial
domain filter as for a reception of a CSI-RS with resource index provided by csi-RS-Index for a same serving cell
or, if servingCellId is provided, for a serving cell indicated by servingCellId
- else PUCCH-SpatialRelationInfo provides srs, the UE transmits the PUCCH using a same spatial domain filter
as for a transmission of a SRS with resource index provided by resource for a same serving cell and/or active UL
BWP or, if servingCellId and/or uplinkBWP are provided, for a serving cell indicated by servingCellId and/or for
an UL BWP indicated by uplinkBWP
If a UE
- is not provided pathlossReferenceRSs in PUCCH-PowerControl,
- is provided enableDefaultBeamPL-ForPUCCH, and
- is not provided PUCCH-SpatialRelationInfo, and
- is not provided coresetPoolIndex value of 1 for any CORESET, or is provided coresetPoolIndex value of 1 for
all CORESETs, in ControlResourceSet and no codepoint of a TCI field, if any, in a DCI format of any search
space set maps to two TCI states [5, TS 38.212]
a spatial setting for a PUCCH transmission from the UE is same as a spatial setting for PDCCH receptions by the UE in
the CORESET with the lowest ID on the active DL BWP of the PCell. For a PUCCH transmission over multiple slots, a
same spatial setting applies to the PUCCH transmission in each of the multiple slots.
A number of DMRS symbols for a PUCCH transmission using PUCCH format 3 or 4 is provided by additionalDMRS.
Use of π/2-BPSK, instead of QPSK, for a PUCCH transmission using PUCCH format 3 or 4 is indicated by pi2BPSK.
9.2.3 UE procedure for reporting HARQ-ACK

A UE does not expect to transmit more than one PUCCH with HARQ-ACK information in a slot per priority index, if
the UE is not provided ackNackFeedbackMode = separate.
For DCI format 1_0, the PDSCH-to-HARQ_feedback timing indicator field values map to {1, 2, 3, 4, 5, 6, 7, 8}. For a
DCI format, other than DCI format 1_0, scheduling a PDSCH reception or a SPS PDSCH release, the PDSCH-to-
HARQ_feedback timing indicator field values, if present, map to values for a set of number of slots provided by dl-
DataToUL-ACK, dl-DataToUL-ACK-r16, or dl-DataToUL-ACKForDCIFormat1_2, as defined in Table 9.2.3-1.
+
For a SPS PDSCH reception ending in slot n , the UE transmits the PUCCH in slot where is provided by the
PDSCH-to-HARQ_feedback timing indicator field, if present, in a DCI format activating the SPS PDSCH reception.
If the UE detects a DCI format that does not include a PDSCH-to-HARQ_feedback timing indicator field and schedules
a PDSCH reception or activates a SPS PDSCH reception ending in slot , the UE provides corresponding HARQ-ACK
+
information in a PUCCH transmission within slot where is provided by dl-DataToUL-ACK, or dl-DataToUL-
ACK-r16, or dl-DataToUL-ACKForDCIFormat1_2.
With reference to slots for PUCCH transmissions, if the UE detects a DCI format scheduling a PDSCH reception
ending in slot or if the UE detects a DCI format indicating a SPS PDSCH release or indicating SCell dormancy
through a PDCCH reception ending in slot , or if the UE detects a DCI format that requests Type-3 HARQ-ACK
codebook report and does not schedule a PDSCH reception through a PDCCH reception ending in slot , as described
in clause 9.1.4, the UE provides corresponding HARQ-ACK information in a PUCCH transmission within slot , +
where is a number of slots and is indicated by the PDSCH-to-HARQ_feedback timing indicator field in the DCI
format, if present, or provided by dl-DataToUL-ACK, dl-DataToUL-ACK-r16, or dl-DataToUL-
ACKForDCIFormat1_2. =0 corresponds to the last slot of the PUCCH transmission that overlaps with the PDSCH
reception or with the PDCCH reception in case of SPS PDSCH release or in case of SCell dormancy indication or in
case of the DCI format that requests Type-3 HARQ-ACK codebook report and does not schedule a PDSCH reception.
A PUCCH transmission with HARQ-ACK information is subject to the limitations for UE transmissions described in
clause 11.1 and clause 11.1.1.
ETSI
Table 9.2.3-1: Mapping of PDSCH-to-HARQ_feedback timing indicator field values to numbers of

slots
PDSCH-to-HARQ_feedback timing indicator Number of slots k

1 bit 2 bits 3 bits
'0' '00' 1st value provided by dl-DataToUL-ACK, dl-DataToUL-ACK-r16,
'000'
or dl-DataToUL-ACKForDCIFormat1_2
'1' '01' 2nd value provided by dl-DataToUL-ACK, dl-DataToUL-ACK-r16,
'001'
'10' 3rd value provided by dl-DataToUL-ACK, dl-DataToUL-ACK-r16,
'010'
'11' 4th value provided by dl-DataToUL-ACK, dl-DataToUL-ACK-r16,
'011'
5th value provided by dl-DataToUL-ACK, dl-DataToUL-ACK-r16,
'100'
'101'
'110'
'111'
For a PUCCH transmission with HARQ-ACK information, a UE determines a PUCCH resource after determining a set
of PUCCH resources for O UCI HARQ-ACK information bits, as described in clause 9.2.1. The PUCCH resource
determination is based on a PUCCH resource indicator field [5, TS 38.212], if present, in a last DCI format, among the
DCI formats that have a value of a PDSCH-to-HARQ_feedback timing indicator field, if present, or a value of dl-
DataToUL-ACK, or dl-DataToUL-ACK-r16, or dl-DataToUL-ACKForDCIFormat1_2, indicating a same slot for the
PUCCH transmission, that the UE detects and for which the UE transmits corresponding HARQ-ACK information in
the PUCCH where, for PUCCH resource determination, detected DCI formats are first indexed in an ascending order
across serving cells indexes for a same PDCCH monitoring occasion and are then indexed in an ascending order across
PDCCH monitoring occasion indexes. For indexing DCI formats within a serving cell for a same PDCCH monitoring
occasion, if the UE is not provided coresetPoolIndex or is provided coresetPoolIndex with value 0 for one or more first
CORESETs and is provided coresetPoolIndex with value 1 for one or more second CORESETs on an active DL BWP
of a serving cell, and with ackNackFeedbackMode = joint for the active UL BWP, detected DCI formats from PDCCH
receptions in the first CORESETs are indexed prior to detected DCI formats from PDCCH receptions in the second
CORESETs.
The PUCCH resource indicator field values map to values of a set of PUCCH resource indexes, as defined in Table
9.2.3-2 for a PUCCH resource indicator field of 3 bits, provided by resourceList for PUCCH resources from a set of
PUCCH resources provided by PUCCH-ResourceSet with a maximum of eight PUCCH resources. If the PUCCH
resource indicator field includes 1 bit or 2 bits, the values map to the first two values or the first four values,
respectively, of Table 9.2.3-2. If the last DCI format does not include a PUCCH resource indicator field, the first value
of Table 9.2.3-2 is used.
For the first set of PUCCH resources and when the size RPUCCH of resourceList is larger than eight, when a UE provides
HARQ-ACK information in a PUCCH transmission in response to detecting a last DCI format in a PDCCH reception,
among DCI formats with a value of the PDSCH-to-HARQ_feedback timing indicator field, if present, or a value of dl-
DataToUL-ACK, or dl-DataToUL-ACK-r16, or dl-DataToUL-ACKForDCIFormat1_2, indicating a same slot for the
PUCCH transmission, the UE determines a PUCCH resource with index rPUCCH , 0 ≤ rPUCCH≤ RPUCCH−1 , as
 nCCE, p ⋅ RPUCCH 8 R  

  + Δ PRI ⋅  PUCCH  if Δ PRI < RPUCCH mod 8 
  N CCE , p   8  
rPUCCH = 
  nCCE, p ⋅ RPUCCH 8 R  
  + Δ PRI ⋅  PUCCH  + RPUCCH mod 8 if Δ PRI ≥ RPUCCH mod 8
 N CCE , p   8  
where N CCE , p is a number of CCEs in CORESET p of the PDCCH reception for the DCI format as described in
∆
clause 10.1, nCCE, p is the index of a first CCE for the PDCCH reception, and PRI is a value of the PUCCH resource
indicator field in the DCI format. If the DCI format does not include a PUCCH resource indicator field, PRI ∆ = 0.
ETSI
Table 9.2.3-2: Mapping of PUCCH resource indication field values to a PUCCH resource in a PUCCH
resource set with maximum 8 PUCCH resources
PUCCH resource indicator PUCCH resource

1 bit 2 bits 3 bits
'0' '00' 1st PUCCH resource provided by pucch-ResourceId obtained from the
'000'
1st value of resourceList
'1' '01' nd PUCCH resource provided by pucch-ResourceId obtained from the
2
'001'
2nd value of resourceList
'10' rd PUCCH resource provided by pucch-ResourceId obtained from the
3
'010'
3rd value of resourceList
'11' th PUCCH resource provided by pucch-ResourceId obtained from the
4
'011'
4th value of resourceList
5th PUCCH resource provided by pucch-ResourceId obtained from the
'100'
th PUCCH resource provided by pucch-ResourceId obtained from the
6
'101'
th
7 PUCCH resource provided by pucch-ResourceId obtained from the
'110'
8th PUCCH resource provided by pucch-ResourceId obtained from the
'111'
If a UE determines a first resource for a PUCCH transmission with HARQ-ACK information corresponding only to a
PDSCH reception without a corresponding PDCCH or detects a first DCI format indicating a first resource for a
PUCCH transmission with corresponding HARQ-ACK information in a slot and also detects at a later time a second
DCI format indicating a second resource for a PUCCH transmission with corresponding HARQ-ACK information in
the slot, the UE does not expect to multiplex HARQ-ACK information corresponding to the second DCI format in a
PUCCH resource in the slot if the PDCCH reception that includes the second DCI format is not earlier than
N 3 ⋅ ( 2048 + 144 ) ⋅ κ ⋅ 2 − μ ⋅ TC from the beginning of a first symbol of the first resource for PUCCH transmission in
the slot where, and ௖ are defined in clause 4.1 of [4, TS 38.211] and μ corresponds to the smallest SCS
configuration among the SCS configurations of the PDCCHs providing the DCI formats and the SCS configuration of
the PUCCH. If processingType2Enabled of PDSCH-ServingCellConfig is set to enable for the serving cell with the
second DCI format and for all serving cells with corresponding HARQ-ACK information multiplexed in the PUCCH
transmission in the slot, N3 = 3 for μ = 0 , N 3 = 4.5 for μ = 1 , N3 = 9 for μ = 2 ; otherwise , N3 = 8 for μ = 0 ,
N 3 = 10 for μ = 1 , N 3 = 17 for μ = 2 , N 3 = 20 for μ = 3 .
If a UE is not provided SPS-PUCCH-AN-List and transmits HARQ-ACK information corresponding only to a PDSCH
reception without a corresponding PDCCH, a PUCCH resource for corresponding PUCCH transmission with HARQ-
ACK information is provided by n1PUCCH-AN.
If a UE transmits a PUCCH with HARQ-ACK information using PUCCH format 0, the UE determines values m0 and
mCS for computing a value of cyclic shift α [4, TS 38.211] where m0 is provided by initialCyclicShift of PUCCH-
format0 or, if initialCyclicShift is not provided, by the initial cyclic shift index as described in clause 9.2.1 and mCS is
determined from the value of one HARQ-ACK information bit or from the values of two HARQ-ACK information bits
as in Table 9.2.3-3 and Table 9.2.3-4, respectively.
Table 9.2.3-3: Mapping of values for one HARQ-ACK information bit to sequences for PUCCH format
0
HARQ-ACK Value 0 1
Sequence cyclic shift m CS = 0 m CS = 6
ETSI
Table 9.2.3-4: Mapping of values for two HARQ-ACK information bits to sequences for PUCCH format
0
HARQ-ACK Value {0, 0} {0, 1} {1, 1} {1, 0}

Sequence cyclic shift m CS = 0 m CS = 3 m CS = 6 m CS = 9
If a UE transmits a PUCCH with HARQ-ACK information using PUCCH format 1, the UE is provided a value for m0
by initialCyclicShift of PUCCH-format1 or, if initialCyclicShift is not provided, by the initial cyclic shift index as
If a UE transmits a PUCCH with OACK HARQ-ACK information bits and OCRC bits using PUCCH format 2 or PUCCH
PUCCH PUCCH
format 3 in a PUCCH resource that includes M RB PRBs, the UE determines a number of PRBs M RB,min for the
PUCCH
PUCCH transmission to be the minimum number of PRBs, that is smaller than or equal to a number of PRBs M RB
provided respectively by nrofPRBs of PUCCH-format2 or nrofPRBs of PUCCH-format3 and start from the first PRB
from the number of PRBs, that results to (OACK + OCRC ) ≤ M RB,min ⋅ Nsc,ctrl ⋅ Nsymb- UCI ⋅ Qm ⋅ r and, if M RB > 1,
PUCCH RB PUCCH PUCCH
(OACK + OCRC ) > (M RB, min − 1)⋅ Nsc,ctrl ⋅ N symb- UCI ⋅ Qm ⋅ r , where
PUCCH RB PUCCH RB
Nsc,ctrl , Nsymb- UCI , Qm , and
PUCCH
r are defined in clause
α2
9.2.5.2. For PUCCH format 3, if
PUCCH
M RB, min is not equal 2 ⋅ 3α 3 ⋅ 5α 5 according to [4, TS 38.211], M RB,
PUCCH
min is
increased to the nearest allowed value of nrofPRBs for PUCCH-format3 [12, TS 38.331]. If
(OACK + OCRC ) > (M RB
PUCCH
−1)⋅ Nsc,
RB
ctrl ⋅ Nsymb- UCI ⋅ Qm ⋅ r , the UE transmits the PUCCH over
PUCCH PUCCH
M RB PRBs.
If a UE is provided a first interlace of Interlace,0

PUCCH PRBs by interlace0 in InterlaceAllocation and transmits a PUCCH
with ACK HARQ-ACK information bits and CRC bits using PUCCH format 2 or PUCCH format 3, the UE transmits
+ ≤
the PUCCH over the first interlace if ACK CRC Interlace,0
PUCCH RB ⋅
sc,ctrl ⋅ ⋅ ⋅
symb-UCI ௠ ; otherwise, if the UE is
PUCCH
provided a second interlace by interlace1 in PUCCH-format2 or PUCCH-format3, the UE transmits the PUCCH over
the first and second interlaces.
9.2.4 UE procedure for reporting SR

A UE can be configured by SchedulingRequestResourceConfig a set of configurations for SR in a PUCCH transmission
using either PUCCH format 0 or PUCCH format 1. A UE can be configured by schedulingRequestID-BFR-SCell a
configuration for LRR in a PUCCH transmission using either PUCCH format 0 or PUCCH format 1. A UE can be
configured by schedulingRequestID-LBT-SCell a configuration for consistent LBT failure recovery, as described in [11,
TS 38.321], in a PUCCH transmission using either PUCCH format 0 or PUCCH format 1. The UE can be provided, by
phy-PriorityIndex in SchedulingRequestResourceConfig, a priority index 0 or a priority index 1 for the SR. If the UE is
not provided a priority index for SR, the priority index is 0.
The UE is configured a PUCCH resource by SchedulingRequestResourceId, or by schedulingRequestID-BFR-SCell, or

by schedulingRequestID-LBT-SCell, providing a PUCCH format 0 resource or a PUCCH format 1 resource as described
in clause 9.2.1. The UE is also configured a periodicity SRPERIODICITY in symbols or slots and an offset SROFFSET in slots
by periodicityAndOffset for a PUCCH transmission conveying SR. If SRPERIODICITY is larger than one slot, the UE
μ
determines a SR transmission occasion in a PUCCH to be in a slot with number n s,f [4, TS 38.211] in a frame with
( frame, μ
number n f if n f ⋅ N slot )
+ ns,fμ − SROFFSET mod SRPERIODICITY = 0 .
If SRPERIODICITY is one slot, the UE expects that SROFFSET = 0 and every slot is a SR transmission occasion in a PUCCH.
If SRPERIODICITY is smaller than one slot, the UE determines a SR transmission occasion in a PUCCH to start in a symbol
with index l [4, TS 38.211] if (l − l0 mod SRPERIODICITY ) mod SRPERIODICITY = 0 where l0 is the value of
startingSymbolIndex.
If the UE determines that, for a SR transmission occasion in a PUCCH, the number of symbols available for the
PUCCH transmission in a slot is smaller than the value provided by nrofSymbols, the UE does not transmit the PUCCH
in the slot.
ETSI
SR transmission occasions in a PUCCH are subject to the limitations for UE transmissions described in clause 11.1 and
clause 11.1.1.
The UE transmits a PUCCH in the PUCCH resource for the corresponding SR configuration only when the UE
transmits a positive SR. For a positive SR transmission using PUCCH format 0, the UE transmits the PUCCH as
described in [4, TS 38.211] by obtaining m0 as described for HARQ-ACK information in clause 9.2.3 and by setting
mcs = 0 . For a positive SR transmission using PUCCH format 1, the UE transmits the PUCCH as described in [4, TS
38.211] by setting b ( 0 ) = 0 .
9.2.5 UE procedure for reporting multiple UCI types

This clause is applicable to the case that a UE has resources for PUCCH transmissions or for PUCCH and PUSCH
transmissions that overlap in time and each PUCCH transmission is over a single slot without repetitions. Any case that
a PUCCH transmission is with repetitions over multiple slots is described in clause 9.2.6. If a UE is configured with
multiple PUCCH resources in a slot to transmit CSI reports
- if the UE is not provided multi-CSI-PUCCH-ResourceList or if PUCCH resources for transmissions of CSI

reports do not overlap in the slot, the UE determines a first resource corresponding to a CSI report with the
highest priority [6, TS 38.214]
- if the first resource includes PUCCH format 2, and if there are remaining resources in the slot that do not
overlap with the first resource, the UE determines a CSI report with the highest priority, among the CSI
reports with corresponding resources from the remaining resources, and a corresponding second resource as
an additional resource for CSI reporting
- if the first resource includes PUCCH format 3 or PUCCH format 4, and if there are remaining resources in
the slot that include PUCCH format 2 and do not overlap with the first resource, the UE determines a CSI
report with the highest priority, among the CSI reports with corresponding resources from the remaining
resources, and a corresponding second resource as an additional resource for CSI reporting
- if the UE is provided multi-CSI-PUCCH-ResourceList and if any of the multiple PUCCH resources overlap, the
UE multiplexes all CSI reports in a resource from the resources provided by multi-CSI-PUCCH-ResourceList, as
described in clause 9.2.5.2.
A UE multiplexes DL HARQ-ACK information, with or without SR, and CSI report(s) in a same PUCCH if the UE is
provided simultaneousHARQ-ACK-CSI; otherwise, the UE drops the CSI report(s) and includes only DL HARQ-ACK
information, with or without SR, in the PUCCH. If the UE would transmit multiple PUCCHs in a slot that include DL
HARQ-ACK information and CSI report(s), the UE expects to be provided a same configuration for
simultaneousHARQ-ACK-CSI each of PUCCH formats 2, 3, and 4.
If a UE would multiplex CSI reports that include Part 2 CSI reports in a PUCCH resource, the UE determines the
PUCCH resource and a number of PRBs for the PUCCH resource or a number of Part 2 CSI reports assuming that each
of the CSI reports indicates rank 1.
If a UE would transmit multiple overlapping PUCCHs in a slot or overlapping PUCCH(s) and PUSCH(s) in a slot and,
when applicable as described in clauses 9.2.5.1 and 9.2.5.2, the UE is configured to multiplex different UCI types in
one PUCCH, and at least one of the multiple overlapping PUCCHs or PUSCHs is in response to a DCI format detection
by the UE, the UE multiplexes all corresponding UCI types if the following conditions are met. If one of the PUCCH
transmissions or PUSCH transmissions is in response to a DCI format detection by the UE, the UE expects that the first
symbol 0 of the earliest PUCCH or PUSCH, among a group overlapping PUCCHs and PUSCHs in the slot, satisfies
the following timeline conditions
- 0 is not before a symbol with CP starting after ݉‫ݔݑ‬

‫ܿ݋ݎ݌‬,1 after a last symbol of any corresponding PDSCH, ‫ܿ݋ݎ݌‬,1
݉‫ݔݑ‬
is given by maximum of ൛‫ܿ݋ݎ݌‬,1 , ⋯ , ‫ܿ݋ݎ݌‬,1 , ⋯ ൟ where for the i-th PDSCH with corresponding HARQ-ACK
݉‫ݔݑ‬,1 ݉‫ݔݑ‬,݅
transmission on a PUCCH which is in the group of overlapping PUCCHs and PUSCHs, ‫ܿ݋ݎ݌‬,1 =
݉‫ݔݑ‬,݅
൫ 1 + 1,1 + 1൯ ⋅ ሺ2048 + 144ሻ ⋅ ⋅ 2−ߤ ⋅ ‫ ܥ‬, 1,1 is selected for the i-th PDSCH following [6, TS 38.214],
1 is selected based on the UE PDSCH processing capability of the i-th PDSCH and SCS configuration ,
where corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH
scheduling the i-th PDSCH, the i-th PDSCH, the PUCCH with corresponding HARQ-ACK transmission for the
i-th PDSCH, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs.
ETSI
- 0 is not before a symbol with CP starting after ݉‫ݔݑ‬

‫ܿ݋ݎ݌‬,‫ ݁ݏ݈ܽ݁݁ݎ‬after a last symbol of any corresponding SPS
PDSCH release or of a DCI format 1_1 indicating SCell dormancy as described in clause 10.3, or of a DCI
format 1_1 indicating a request for a Type-3 HARQ-ACK codebook report without scheduling PDSCH.
݉‫ݔݑ‬ ݉‫ݔݑ‬,1
,⋯,
‫ܿ݋ݎ݌‬,‫ ݁ݏ݈ܽ݁݁ݎ‬is given by maximum of ൛‫ܿ݋ݎ݌‬,‫݁ݏ݈ܽ݁݁ݎ‬ ݉‫ݔݑ‬ ,݅
‫ܿ݋ݎ݌‬,‫݁ݏ݈ܽ݁݁ݎ‬,⋯
ൟ where for the i-th PDCCH providing the
SPS PDSCH release or the DCI format 1_1 with corresponding HARQ-ACK transmission on a PUCCH which is
in the group of overlapping PUCCHs and PUSCHs, ‫ܿ݋ݎ݌‬,‫ ݁ݏ݈ܽ݁݁ݎ‬ሺ
݉‫ݔݑ‬,݅
= + 1 ⋅ 2048 + 144 ⋅ ⋅ 2 ⋅
ሻ ሺ ሻ −ߤ ‫ ܥ‬, as
described in clause 10.2, or DCI format 1_1 that requests Type-3 HARQ-ACK codebook report as described in
clause 10.2, or the DCI format 1_1 indicating SCell dormancy without scheduling a PDSCH reception as
described in clause 10.3, where corresponds to the smallest SCS configuration among the SCS configurations
used for the PDCCH providing the i-th SPS PDSCH release or the DCI format 1_1, the PUCCH with
corresponding HARQ-ACK transmission for the i-th SPS PDSCH release or the DCI format 1_1, and all
PUSCHs in the group of overlapping PUCCHs and PUSCHs.
- if there is no aperiodic CSI report multiplexed in a PUSCH in the group of overlapping PUCCHs and PUSCHs,
0 is not before a symbol with CP starting after ݉‫ݔݑ‬
‫ܿ݋ݎ݌‬,2 after a last symbol of
- any PDCCH with the DCI format scheduling an overlapping PUSCH, and
- any PDCCH scheduling a PDSCH or SPS PDSCH release, or a DCI format 1_1 indicating SCell dormancy,
or a DCI format 1_1 indicating a request for a Type-3 HARQ-ACK codebook report without scheduling
PDSCH, with corresponding HARQ-ACK information in an overlapping PUCCH in the slot
If there is at least one PUSCH in the group of overlapping PUCCHs and PUSCHs, ௣௥௢௖ ௠௨௫ is given by maximum
,ଶ
,⋯,
of ௣௥௢௖,ଶ
௠௨௫,ଵ
,⋯
௣௥௢௖,ଶ where for the i-th PUSCH which is in the group of overlapping PUCCHs and
௠௨௫,௜

௠௨௫ ,௜
PUSCHs, ௣௥௢௖ ,ଶ =
ଶ + ଶ,ଵ + 1 ⋅ 2048 + 144 ⋅ ⋅ 2ିఓ ⋅ ஼ + ୱ୵୧୲ୡ୦, ଶ,ଶ, ଶ,ଵ, ଶ,ଶ and ୱ୵୧୲ୡ୦
are selected for the i-th PUSCH following [6, TS 38.214], ଶ is selected based on the UE PUSCH processing
capability of the i-th PUSCH and SCS configuration , where corresponds to the smallest SCS configuration
among the SCS configurations used for the PDCCH scheduling the i-th PUSCH, the PDCCHs scheduling the
PDSCHs or providing the SPS PDSCH releases or providing the SCell dormancy indication or providing the
indication of a request for a Type-3 HARQ-ACK codebook report without scheduling PDSCH with
corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs/PUSCHs,
and all PUSCHs in the group of overlapping PUCCHs and PUSCHs.
If there is no PUSCH in the group of overlapping PUCCHs and PUSCHs, ௣௥௢௖ ௠௨௫ is given by maximum of
,ଶ
,⋯, ,⋯
௣௥௢௖,ଶ ௣௥௢௖,ଶ where for the i-th PDSCH or the i-th SPS PDSCH release or the i-th SCell dormancy
௠௨௫,ଵ ௠௨௫ ,௜
indication or the i-th indication of a request for a Type-3 HARQ-ACK codebook report without scheduling
PDSCH with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping
PUCCHs, ௣௥௢௖ =
௠௨௫ ,௜
,ଶ + 1 ⋅ 2048 + 144 ⋅ ⋅ 2 ⋅
ଶ ିఓ ஼ , ଶis selected based on the UE PUSCH processing
capability of the PUCCH serving cell if configured. 2 is selected based on the UE PUSCH processing
capability 1, if PUSCH processing capability is not configured for the PUCCH serving cell. is selected based
on the smallest SCS configuration between the SCS configuration used for the PDCCH scheduling the i-th
PDSCH or providing the i-th SPS PDSCH release or providing the i-th SCell dormancy indication or providing
the i-th indication of a request for a Type-3 HARQ-ACK codebook report without scheduling PDSCH with
corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs, and the
SCS configuration for the PUCCH serving cell.
- if there is an aperiodic CSI report multiplexed in a PUSCH in the group of overlapping PUCCHs and PUSCHs,
0 is not before a symbol with CP starting after ௣௥௢௖ ,஼ௌூ =
+ ⋅ 2048 + 144 ⋅ ⋅ 2 ⋅ ஼ +
௠௨௫ ିఓ
ୱ୵୧୲ୡ୦ , ଶ,ଶ after a last symbol of

- any PDCCH with the DCI format scheduling an overlapping PUSCH, and
- any PDCCH scheduling a PDSCH, or SPS PDSCH release, or providing a DCI format 1_1 indicating SCell
dormancy, or a DCI format 1_1 indicating a request for a Type-3 HARQ-ACK codebook report without
scheduling PDSCH, with corresponding HARQ-ACK information in an overlapping PUCCH in the slot
where corresponds to the smallest SCS configuration among the SCS configuration of the PDCCHs, the
smallest SCS configuration for the group of the overlapping PUSCHs, and the smallest SCS configuration of
CSI-RS associated with the DCI format scheduling the PUSCH with the multiplexed aperiodic CSI report, and
ETSI
= 2 for = 0,1 , = 3 for = 2 and = 4 for = 3. ୱ୵୧୲ୡ୦ is defined in [6, TS 38.214] and it is applied
only if ଵ of table 5.4-1 in [6, TS 38.214] is applied to the determination of .
- ଵ , ଶ , ଵ,ଵ , ଶ,ଵ , ଶ,ଶ , and are defined in [6, TS 38.214] and and ஼ are defined in [4, TS 38.211].
If a UE would transmit multiple overlapping PUCCHs in a slot or overlapping PUCCH(s) and PUSCH(s) in a slot, one
of the PUCCHs includes HARQ-ACK information in response to an SPS PDSCH reception, and any PUSCH is not in
response to a DCI format detection, the UE expects that the first symbol S 0 of the earliest PUCCH or PUSCH satisfies
the first of the previous timeline conditions with the exception that components associated to a SCS configuration for a
PDCCH scheduling a PDSCH or a PUSCH are absent from the timeline conditions.
A UE does not expect a PUCCH or a PUSCH that is in response to a DCI format detection to overlap with any other
PUCCH or PUSCH that does not satisfy the above timing conditions.
A UE that
and
- is provided ackNackFeedbackMode = separate
does not expect a PUCCH or a PUSCH transmission triggered by a detection of a DCI format in a PDCCH received in a
CORESET from the first CORESETs to overlap in time with a PUCCH or a PUSCH transmission triggered by a
detection of a DCI format in a PDCCH received in a CORESET from the second CORESETs.
If there is one or more aperiodic CSI reports multiplexed on a PUSCH in the group of overlapping PUCCHs and
mux
PUSCHs and if symbol S 0 is before symbol Z'ref that is a next uplink symbol with CP starting after
CSI = (Z '+ d ) ⋅ (2048 + 144) ⋅ κ ⋅ 2

−μ
mux
Z'proc, ⋅ TC after the end of the last symbol of
- the last symbol of aperiodic CSI-RS resource for channel measurements, and
- the last symbol of aperiodic CSI-IM used for interference measurements, and
- the last symbol of aperiodic NZP CSI-RS for interference measurements, when aperiodic CSI-RS is used for
channel measurement for triggered CSI report n
the UE is not required to update the CSI report for the triggered CSI report n . Z' is defined in [6, TS 38.214] and μ
corresponds to the smallest SCS configuration among the SCS configurations of the PDCCHs scheduling the PUSCHs,
the smallest SCS configuration of aperiodic CSI-RSs associated with DCI formats provided by the PDCCHs triggering
the aperiodic CSI reports, and the smallest SCS configuration of the overlapping PUCCHs and PUSCHs and d = 2 for
μ = 0 ,1 , d = 3 for μ = 2 and d = 4 for μ = 3 .
If a UE would transmit multiple PUCCHs in a slot that include HARQ-ACK information, and/or SR, and/or CSI reports
and any PUCCH with HARQ-ACK information in the slot satisfies the above timing conditions and does not overlap
with any other PUCCH or PUSCH in the slot that does not satisfy the above timing conditions, the UE multiplexes the
HARQ-ACK information, and/or SR, and/or CSI reports and determines corresponding PUCCH(s) for transmission in
the slot according to the following pseudo-code. If the multiple PUCCHs do not include HARQ-ACK information and
do not overlap with any PUSCH transmission by the UE in response to a DCI format detection by the UE, the timing
conditions do not apply.
If
- a UE is not provided multi-CSI-PUCCH-ResourceList, and
- a resource for a PUCCH transmission with HARQ-ACK information in response to SPS PDSCH reception
and/or a resource for a PUCCH associated with a SR occasion overlap in time with two resources for respective
PUCCH transmissions with two CSI reports, and
- there is no resource for a PUCCH transmission with HARQ-ACK information in response to a DCI format
detection that overlaps in time with any of the previous resources, and
ETSI
- the following pseudo code results to the UE attempting to determine a single PUCCH resource from the HARQ-
ACK and/or the SR resource and the two PUCCH resources with CSI reports
the UE
- multiplexes the HARQ-ACK information and/or the SR in the resource for the PUCCH transmission with the
CSI report having the higher priority, and
- does not transmit the PUCCH with the CSI report having the lower priority
Set Q to the set of resources for transmission of corresponding PUCCHs in a single slot without repetitions where
- a resource with earlier first symbol is placed before a resource with later first symbol
- for two resources with same first symbol, the resource with longer duration is placed before the resource with
shorter duration
- for two resources with same first symbol and same duration, the placement is arbitrary
- the above three steps for the set Q are according to a subsequent pseudo-code for a function order(Q )
- a resource for negative SR transmission that does not overlap with a resource for HARQ-ACK or CSI
transmission is excluded from set Q
- if the UE is not provided simultaneousHARQ-ACK-CSI and resources for transmission of HARQ-ACK

information include PUCCH format 0 or PUCCH format 2, resources that include PUCCH format 2, or PUCCH
format 3, or PUCCH format 4 for transmission of CSI reports are excluded from the set Q if they overlap with
any resource from the resources for transmission of HARQ-ACK information
- if the UE is not provided simultaneousHARQ-ACK-CSI and at least one of the resources for transmission of
HARQ-ACK information includes PUCCH format 1, PUCCH format 3, or PUCCH format 4
- resources that include PUCCH format 3 or PUCCH format 4 for transmission of CSI reports are excluded
from the set Q
- resources that include PUCCH format 2 for transmission of CSI reports are excluded from the set Q if they
overlap with any resource from the resources for transmission of HARQ-ACK information
Set C (Q ) to the cardinality of Q
Set Q( j,0) to be the first symbol of resource Q( j ) in the slot
Set L (Q ( j ) ) to be the number of symbols of resource Q( j ) in the slot
Set j = 0 - index of first resource in set Q
Set o =0 - counter of overlapped resources

while j ≤ C (Q ) − 1
if j < C (Q ) − 1 and resource Q ( j − o ) overlaps with resource Q ( j + 1)
o = o +1
j = j +1
else
if o >0
determine a single resource for multiplexing UCI associated with resources {Q ( j − o), Q ( j − o + 1),..., Q ( j )} as
described in clauses 9.2.5.0, 9.2.5.1 and 9.2.5.2
ETSI
set the index of the single resource to j
Q = Q \ {Q ( j − o ), Q ( j − o + 1),..., Q ( j − 1)}
j = 0 % start from the beginning after reordering unmerged resources at next step
o =0
order(Q ) % function that re-orders resources in current set Q
Set C (Q ) to the cardinality of Q
else
j = j +1
end if
end if
end while
The function order(Q ) performs the following pseudo-code
k =0
while k < C (Q) − 1 % the next two while loops are to re-order the unmerged resources
l =0
while l < C (Q ) − 1 − k
if Q(l ,0) > Q(l + 1,0) OR (Q(l ,0) = Q(l + 1,0) & L(Q(l )) < L(Q(l + 1)))
temp = Q(l )
Q(l ) = Q(l + 1)
Q (l + 1) = temp
end if
l =l +1
end while
k =k +1
end while
For each PUCCH resource in the set Q that satisfies the aforementioned timing conditions, when applicable,
- the UE transmits a PUCCH using the PUCCH resource if the PUCCH resource does not overlap in time with a
PUSCH transmission after multiplexing UCI following the procedures described in clauses 9.2.5.1 and 9.2.5.2
- the UE multiplexes HARQ-ACK information and/or CSI reports in a PUSCH if the PUCCH resource overlaps in
time with a PUSCH transmission, as described in clause 9.3, and does not transmit SR. In case the PUCCH
resource overlaps in time with multiple PUSCH transmissions, the PUSCH for multiplexing HARQ-ACK
information and/or CSI is selected as described in clause 9. If the PUSCH transmission by the UE is not in
ETSI
response to a DCI format detection and the UE multiplexes only CSI reports, the timing conditions are not
applicable
- the UE does not expect the resource to overlap with a second resource of a PUCCH transmission over multiple
slots if the resource is obtained from a group of resources that do not overlap with the second resource.
clauses 9.2.5.0, 9.2.5.1 and 9.2.5.2 assume the following
- resources for transmissions of UCI types, prior to multiplexing or dropping, overlap in a slot
- multiplexing conditions of corresponding UCI types in a single PUCCH are satisfied, and
- the UE does not transmit any PUSCH time-overlapping with PUCCH in the slot.
9.2.5.0 UE procedure for prioritization between SL HARQ-ACK information in a

PUCCH and UCI in a PUCCH
The priority value of a PUCCH transmission is as described in clause 16.2.4.3.1.
For prioritization between SL HARQ-ACK information in a first PUCCH and UCI in a second PUCCH
- if the second PUCCH has priority index 1,
- if sl-PriorityThreshold-UL-URLLC is provided
- the UE transmits the first PUCCH if a smallest priority value of the first PUCCH is smaller than sl-
PriorityThreshold-UL-URLLC; otherwise, the UE transmits the second PUCCH
- else
- the UE transmits the second PUCCH
- else
- the UE transmits the first PUCCH if the smallest priority value of the first PUCCH is smaller than sl-
PriorityThreshold; otherwise, the UE transmits the second PUCCH
When the UE determines to transmit the second PUCCH, the UE determines a single resource for multiplexing UCI in
the second PUCCH as described in clauses 9.2.5.1 and 9.2.5.2.
9.2.5.1 UE procedure for multiplexing HARQ-ACK or CSI and SR in a PUCCH

In the following, a UE is configured to transmit PUCCHs for respective SRs in a slot, as determined by a set of
schedulingRequestResourceId, a schedulingRequestResourceId associated with schedulingRequestID-BFR-SCell, and a
schedulingRequestResourceId associated with schedulingRequestID-LBT-SCell, with SR transmission occasions that
would overlap with a transmission of a PUCCH with HARQ-ACK information from the UE in the slot or with a
transmission of a PUCCH with CSI report(s) from the UE in the slot.
If a UE would transmit a PUCCH with positive SR and at most two HARQ-ACK information bits in a resource using
PUCCH format 0, the UE transmits the PUCCH in the resource using PUCCH format 0 in PRB(s) for HARQ-ACK
information as described in clause 9.2.3. The UE determines a value of m0 and m CS for computing a value of cyclic
shift α [4, TS 38.211] where m0 is provided by initialCyclicShift of PUCCH-format0, and m CS is determined from
the value of one HARQ-ACK information bit or from the values of two HARQ-ACK information bits as in Table 9.2.5-
1 and Table 9.2.5-2, respectively.
If the UE would transmit negative SR and a PUCCH with at most two HARQ-ACK information bits in a resource using
PUCCH format 0, the UE transmits the PUCCH in the resource using PUCCH format 0 for HARQ-ACK information as
ETSI
Table 9.2.5-1: Mapping of values for one HARQ-ACK information bit and positive SR to sequences for
PUCCH format 0
HARQ-ACK Value 0 1
Sequence cyclic shift m CS = 3 m CS = 9
Table 9.2.5-2: Mapping of values for two HARQ-ACK information bits and positive SR to sequences
for PUCCH format 0
HARQ-ACK Value {0, 0} {0, 1} {1, 1} {1, 0}

Sequence cyclic shift mCS = 1 m CS = 4 m CS = 7 mCS = 10
If a UE would transmit SR in a resource using PUCCH format 0 and HARQ-ACK information bits in a resource using
PUCCH format 1 in a slot, the UE transmits only a PUCCH with the HARQ-ACK information bits in the resource using
PUCCH format 1.
If the UE would transmit positive SR in a first resource using PUCCH format 1 and at most two HARQ-ACK
information bits in a second resource using PUCCH format 1 in a slot, the UE transmits a PUCCH with HARQ-ACK
information bits in the first resource using PUCCH format 1 as described in clause 9.2.3. If a UE would not transmit a
positive SR in a resource using PUCCH format 1 and would transmit at most two HARQ-ACK information bits in a
resource using PUCCH format 1 in a slot, the UE transmits a PUCCH in the resource using PUCCH format 1 for
HARQ-ACK information as described in clause 9.2.3.
If a UE would transmit a PUCCH with OACK HARQ-ACK information bits in a resource using PUCCH format 2 or
PUCCH format 3 or PUCCH format 4 in a slot, as described in clauses 9.2.1 and 9.2.3, log 2 (K + 1) bits representing
a negative or positive SR, in ascending order of the values of schedulingRequestResourceId, a
schedulingRequestResourceId associated with schedulingRequestID-BFR-SCell, and a schedulingRequestResourceId
associated with schedulingRequestID-LBT-SCell, are appended to the HARQ-ACK information bits and the UE
transmits the combined OUCI = OACK+ log2(K +1) UCI bits in a PUCCH using a resource with PUCCH format 2 or
PUCCH format 3 or PUCCH format 4 that the UE determines as described in clauses 9.2.1 and 9.2.3. If one of the SRs
is a positive LRR, the value of the log 2 (K + 1) bits indicates the positive LRR. An all-zero value for the
log 2 (K + 1) bits represents a negative SR value across all SRs.
If a UE would transmit a PUCCH with OCSI CSI report bits in a resource using PUCCH format 2 or PUCCH format 3 or
PUCCH format 4 in a slot, log 2 (K + 1) bits representing corresponding negative or positive SR, in ascending order of
the values of schedulingRequestResourceId, a schedulingRequestResourceId associated with schedulingRequestID-
BFR-SCell, and a schedulingRequestResourceId associated with schedulingRequestID-LBT-SCell, are prepended to the
CSI information bits as described in clause 9.2.5.2 and the UE transmits a PUCCH with the combined
OUCI = log2 (K + 1) + OCSI UCI bits in a resource using the PUCCH format 2 or PUCCH format 3 or PUCCH format 4
for CSI reporting. If one of the SRs is a positive LRR, the value of the log 2 (K + 1) bits indicates the positive LRR.
An all-zero value for the log2 (K + 1) bits represents a negative SR value across all SRs.
If a UE transmits a PUCCH with OACK HARQ-ACK information bits, OSR = log 2 (K + 1) SR bits, and OCRC CRC bits
PUCCH
using PUCCH format 2 or PUCCH format 3 in a PUCCH resource that includes M RB PRBs, the UE determines a
PUCCH
number of PRBs M RB,min for the PUCCH transmission to be the minimum number of PRBs, that is smaller than or
equal to a number of PRBs provided respectively by nrofPRBs in PUCCH-format2 or nrofPRBs in PUCCH-format3
and starts from the first PRB from the number of PRBs, that results to
(OACK + OSR + OCRC ) ≤ M RB,min ⋅ N sc,ctrl ⋅ N symb- UCI ⋅ Qm ⋅ r and, if M RB
PUCCH RB PUCCH PUCCH
> 1,
(OACK + OSR + OCRC ) > (M RB,min −1)⋅ Nsc,ctrl ⋅ Nsymb- UCI ⋅ Qm ⋅ r , where N sc,ctrl , Nsymb
PUCCH RB PUCCH RB PUCCH
- UCI ,
Qm , and r are defined in
α2 α3 α5
clause 9.2.5.2. For PUCCH format 3, if M PUCCH
RB,min is not equal 2 ⋅3 ⋅5 according to [4, TS 38.211],
PUCCH
M RB, min
is increased to the nearest allowed value of nrofPRBs for PUCCH-format3 [12, TS 38.331]. If
(OACK + OSR + OCRC ) > (M RB
PUCCH
− 1)⋅ Nsc,
RB
ctrl ⋅ Nsymb- UCI ⋅ Qm ⋅ r , the UE transmits the PUCCH over the
PUCCH PUCCH
M RB PRBs.
ETSI
If a UE is provided a first interlace of Interlace,0

PUCCH
PRBs by interlace0 in InterlaceAllocation and transmits a PUCCH
with ACK HARQ-ACK information bits, SR = ⌈ଶ + 1 ⌉ SR bits, and CRC CRC bits using PUCCH format 2 or
PUCCH format 3, the UE transmits the PUCCH over the first interlace if ACK + SR + CRC ≤ Interlace,0
PUCCH
⋅ sc,ctrl
RB
⋅
symb-UCI ⋅ ௠ ⋅ ; otherwise, if the UE is provided a second interlace by interlace1 in PUCCH-format2 or PUCCH-
PUCCH
format3, the UE transmits the PUCCH over the first and second interlaces.
9.2.5.2 UE procedure for multiplexing HARQ-ACK/SR/CSI in a PUCCH

For a transmission occasion of a single CSI report, a PUCCH resource is provided by pucch-CSI-ResourceList. For a
transmission occasion of multiple CSI reports, corresponding PUCCH resources can be provided by multi-CSI-PUCCH-
ResourceList. If a UE is provided first and second PUCCH-Config, multi-CSI-PUCCH-ResourceList is provided by the
first PUCCH-Config, and PUCCH-ResourceId in pucch-CSI-ResourceList or multi-CSI-PUCCH-ResourceList indicates
a corresponding PUCCH resource in PUCCH-Resource provided by the first PUCCH-Config.
If a UE is provided only one PUCCH resource set for transmission of HARQ-ACK information in response to PDSCH
reception scheduled by a DCI format or in response to a SPS PDSCH release or in response to a SCell dormancy
indication, the UE does not expect to be provided simultaneousHARQ-ACK-CSI.
A UE is configured by maxCodeRate a code rate for multiplexing HARQ-ACK, SR, and CSI report(s) in a PUCCH
transmission using PUCCH format 2, PUCCH format 3, or PUCCH format 4.
If a UE transmits CSI reports using PUCCH format 2, the UE transmits only wideband CSI for each CSI report [6, TS
38.214]. In the following, a Part 1 CSI report refers either to a CSI report with only wideband CSI or to a Part 1 CSI
report with wideband CSI and sub-band CSI.
Denote as
- OACK a total number of HARQ-ACK information bits, if any
- O SR a total number of SR bits. O SR = 0 if there is no scheduling request bit; otherwise, OSR = log 2 (K + 1) as
described in clause 9.2.5.1
total
 (O )
N CSI
- O CSI = CSI - part1 , n + O CSI - part2 , n , where OCSI-part1,n is a number of Part 1 CSI report bits for CSI report with
n =1
priority value n , OCSI - part2 , n is a number of Part 2 CSI report bits, if any, for CSI report with priority value n [6,
total
TS 38.214], and NCSI is a number of CSI reports that include overlapping CSI reports
- OCRC = OCRC,CSI-part1 + OCRC,CSI-part2, where OCRC, CSI-part1 is a number of CRC bits, if any, for encoding HARQ-
ACK, SR and Part 1 CSI report bits and OCRC, CSI -part2 is a number of CRC bits, if any, for encoding Part 2 CSI
report bits
In the following
- r is a code rate given by maxCodeRate as in Table 9.2.5.2-1.

PUCCH
- M RB is a number of PRBs for PUCCH format 2, or PUCCH format 3, or PUCCH format 4, respectively,
PUCCH
where M RB is provided by nrofPRBs in PUCCH-format2 for PUCCH format 2 or by nrofPRBs in PUCCH-
PUCCH
format3 for PUCCH format 3, and M RB = 1 for PUCCH format 4
-
RB
N sc,ctrl = N scRB − 4 for PUCCH format 2 or, if the PUCCH resource with PUCCH format 2 includes an
orthogonal cover code with length NSF
PUCCH,2 RB
(RB
)
provided by occ-Length, Nsc,ctrl = Nsc − 4 NSF
PUCCH,2
,
ctrl = N sc for PUCCH format 3 or, if the PUCCH resource with PUCCH format 3 includes an orthogonal
RB RB
N sc,
provided by occ-Length, Nsc,ctrl = Nsc NSF , and Nsc,ctrl = Nsc NSF
PUCCH,3 RB RB PUCCH,3 RB RB PUCCH,4
cover code with length NSF
RB
for PUCCH format 4, where Nsc is a number of subcarriers per resource block [4, TS 38.211]
ETSI
PUCCH PUCCH,2
- N symb - UCI is equal to a number of PUCCH symbols N symb for PUCCH format 2 provided by nrofSymbols in
PUCCH
PUCCH-format2. For PUCCH format 3 or for PUCCH format 4, N symb - UCI is equal to a number of PUCCH
PUCCH,3 PUCCH,4
symbols Nsymb for PUCCH format 3 or equal to a number of PUCCH symbols N symb for PUCCH format
4 provided by nrofSymbols in PUCCH-format3 or nrofSymbols in PUCCH-format4, respectively, after excluding
a number of symbols used for DM-RS transmission for PUCCH format 3 or for PUCCH format 4, respectively
[4, TS 38.211]
- Qm =1 if pi/2-BPSK is the modulation scheme and Qm = 2 if QPSK is the modulation scheme as indicated by
pi2BPSK for PUCCH format 3 or PUCCH format 4. For PUCCH format 2, Qm = 2
If a UE has one or more CSI reports and zero or more HARQ-ACK/SR information bits to transmit in a PUCCH where
the HARQ-ACK, if any, is in response to a PDSCH reception without a corresponding PDCCH
- if any of the CSI reports are overlapping and the UE is provided by multi-CSI-PUCCH-ResourceList with J ≤ 2
PUCCH resources in a slot, for PUCCH format 2 and/or PUCCH format 3 and/or PUCCH format 4, as described
in clause 9.2.1, where the resources are indexed according to an ascending order for the product of a number of
corresponding REs, modulation order Qm , and configured code rate r ;
- if (OACK + OSR + OCSI + OCRC ) ≤ M RB (

PUCCH
⋅ N sc,
RB
)
ctrl ⋅ N symb - UCI ⋅ Qm ⋅ r 0 , the UE uses PUCCH format 2 resource
PUCCH
0 , or the PUCCH format 3 resource 0 , or the PUCCH format 4 resource 0
- else if (OACK + OSR + OCSI + OCRC ) > M RB

PUCCH
(
⋅ Nsc,
RB
ctrl ⋅ N symb - UCI ⋅ Qm ⋅ r
PUCCH
) j
and
(OACK + OSR + OCSI + OCRC ) ≤ (M RB

PUCCH
⋅ N sc,
RB
ctrl ⋅ N symb- UCI ⋅ Qm ⋅ r ) j +1 ,
PUCCH
0 ≤ j < J − 1 , the UE transmits a
PUCCH conveying HARQ-ACK information, SR and CSI report(s) in a respective PUCCH where the UE
uses the PUCCH format 2 resource j + 1 , or the PUCCH format 3 resource j + 1 , or the PUCCH format 4
resource j + 1
- else the UE uses the PUCCH format 2 resource J −1 , or the PUCCH format 3 resource J −1 , or the PUCCH
format 4 resource J −1 and the UE selects N CSI
reported
CSI report(s) for transmission together with HARQ-
ACK information and SR, when any, in ascending priority value as described in [6, TS 38.214]
- else, the UE transmits the OACK + OSR + OCSI + OCRC bits in a PUCCH resource provided by pucch-CSI-
ResourceList and determined as described in clause 9.2.5
If a UE has HARQ-ACK, SR and wideband or sub-band CSI reports to transmit and the UE determines a PUCCH
resource with PUCCH format 2, or the UE has HARQ-ACK, SR and wideband CSI reports [6, TS 38.214] to transmit
and the UE determines a PUCCH resource with PUCCH format 3 or PUCCH format 4, where
- the UE determines the PUCCH resource using the PUCCH resource indicator field [5, TS 38.212] in a last of a
number of DCI formats with a value of a PDSCH-to-HARQ_feedback timing indicator field, if present, or a
value of dl-DataToUL-ACK, or dl-DataToUL-ACK-r16, or dl-DataToUL-ACKForDCIFormat1_2, indicating a
same slot for the PUCCH transmission, from a PUCCH resource set provided to the UE for HARQ-ACK
transmission, and
- the UE determines the PUCCH resource set as described in clause 9.2.1 and clause 9.2.3 for OUCI UCI bits
and
- (
if OACK + OSR + OCSI−part1 + OCRC,CSI-part1 ≤ M RB )
PUCCH
⋅ Nsc,
RB
ctrl ⋅ Nsymb-UCI ⋅ Qm ⋅ r , the UE transmits the HARQ-ACK,
PUCCH
PUCCH PUCCH
SR, and CSI reports bits by selecting the minimum number M RB,min of the M RB PRBs satisfying
(O ACK )
+ OSR + OCSI-part1 + OCRC,CSI-part1 ≤ M PUCCH
RB,min ⋅N RB
sc,ctrl ⋅N PUCCH
symb- UCI ⋅ Qm ⋅ r as described in clauses 9.2.3 and 9.2.5.1;
ETSI
reported total
- else, the UE selects N CSI CSI report(s), from the NCSI CSI reports, for transmission together with HARQ-
reported
ACK and SR in ascending priority value [6, TS 38.214], where the value of N CSI satisfies
reported
 N CSI 
O
 ACK
+ OSR + O
n =1
CSI - part1, n + OCRC,CSI-part1,N  ≤ M RB

PUCCH
⋅ N sc,
RB
ctrl ⋅ N symb- UCI ⋅ Qm ⋅ r and
PUCCH
 

reported
N CSI +1 
O
 ACK
+ OSR +  OCSI-part1,n + OCRC,CSI-part1,N +1  > M RBPUCCH ⋅ Nsc,RBctrl ⋅ Nsymb
n =1
- UCI ⋅ Qm ⋅ r , where OCRC, CSI -part1, N is a
PUCCH
 
reported
N CSI
number of CRC bits corresponding to OACK + OSR + 

n =1
OCSI - part1,n UCI bits, and OCRC, CSI -part1, N +1 is a number
reported
N CSI +1
of CRC bits corresponding to OACK + OSR + 

n =1
OCSI-part1,n UCI bits.
PUCCH
If a UE is provided a first interlace of Interlace,0 ‫ܯ‬
PRBs by interlace0 in InterlaceAllocation, the UE has HARQ-ACK,
SR and wideband or sub-band CSI reports to transmit, and the UE determines a PUCCH resource with PUCCH format
2, or the UE has HARQ-ACK, SR and wideband CSI reports to transmit and the UE determines a PUCCH resource
with PUCCH format 3, where
- the UE determines the PUCCH resource using the PUCCH resource indicator field in a last of a number of DCI
formats with a value of a PDSCH-to-HARQ_feedback timing indicator field indicating a same slot for the
PUCCH transmission, from a PUCCH resource set provided to the UE for HARQ-ACK transmission, and
- the UE determines the PUCCH resource set as described in clauses 9.2.1 and 9.2.3 for ܱUCI UCI bits
and
- ൫ܱ ܱ ܱ ܱ
if ACK + SR + CSIିpart1 + CRC,CSI-part1 ≤ Interlace,0
PUCCH
⋅ sc,ctrl
RB
൯ ‫ܯ‬
⋅ symb-UCI
PUCCH
ܰ
⋅ ௠ ⋅ , the UE transmits the ܰ ܳ ‫ݎ‬
HARQ-ACK, SR, and CSI reports bits in a PUCCH over the first interlace
- else, if the UE is provided a second interlace of ‫ܯ‬Interlace,1

PUCCH
PRBs by interlace1 and if ൫ܱACK + ܱSR + ܱCSIିpart1 +
ܱCRC,CSI-part1൯ ≤ ൫‫ܯ‬Interlace,0 + ‫ܯ‬Interlace,1൯ ⋅ ܰsc,ctrl ⋅ ܰsymb-UCI ⋅ ܳ௠ ⋅ ‫ݎ‬, the UE transmits the HARQ-ACK, SR,
PUCCH PUCCH RB PUCCH
and CSI reports bits in a PUCCH over both the first and second interlaces
- else, the procedure is same as the corresponding one when the UE is provided PUCCH-ResourceSet by replacing
‫ܯ‬ PUCCH
RB ‫ܯ‬
PUCCH
with Interlace,0 PUCCH
, or, if the UE is provided interlace1, by Interlace,0 + Interlace,1
PUCCH
. ‫ܯ‬ ‫ܯ‬
If a UE has HARQ-ACK, SR and sub-band CSI reports to transmit and the UE determines a PUCCH resource with
PUCCH format 3 or PUCCH format 4, where
- the UE determines the PUCCH resource using the PUCCH resource indicator field [5, TS 38.212] in a last of a
number of DCI formats with a value of a PDSCH-to-HARQ_feedback timing indicator field indicating a same
slot for the PUCCH transmission, from a PUCCH resource set provided to the UE for HARQ-ACK transmission,
and
- the UE determines the PUCCH resource set as described in clause 9.2.1 and clause 9.2.3 for OUCI UCI bits
and
- if (OACK + OSR + OCSI + OCRC ) ≤ M RB

PUCCH
⋅ N sc,
RB
ctrl ⋅ N symb -UCI ⋅ Qm ⋅ r , the UE transmits the HARQ-ACK, SR and the
PUCCH
total PUCCH PUCCH

N CSI CSI report bits by selecting the minimum number M RB,min of PRBs from the M RB PRBs satisfying
(OACK + OSR + OCSI + OCRC ) ≤ M RB,min ⋅ Nsc,ctrl ⋅ Nsymb- UCI ⋅ Qm ⋅ r
PUCCH RB PUCCH
as described in clauses 9.2.3 and 9.2.5.1
- else,
if for N CSI-part2 > 0 Part 2 CSI report priority value(s), it is

reported
-
ETSI
 
reported

NCSI total
NCSI 
(Qm ⋅ r )  ⋅ Qm ⋅ r
- part2
 OCSI-part2,n + OCRC,CSI-part2,N ≤  M RBPUCCH ⋅ Nsc,RBctrl ⋅ Nsymb

 -UCI −  OACK + OSR +
PUCCH 
 O CSI-part1,n + OCRC,CSI-part1 

n=1
  n=1  
 
and
-part2 +1  
reported

N CSI total
N CSI 
 (Q ⋅ r )  ⋅ Q ⋅ r
O
n =1
CSI- part2, n + OCRC,CSI-part2,N+1 >  M RB
PUCCH
⋅ Nsc,
RB
 ctrl ⋅ Nsymb- UCI −  OACK + OSR +  OCSI- part1, n + OCRC,CSI- part1
PUCCH 

 n =1
m m



  
,
reported
the UE selects the first N CSI-part2 Part 2 CSI reports, according to respective priority value(s) [6, TS 38.214],
total
for transmission together with the HARQ-ACK, SR and NCSI Part 1 CSI reports , where O CSI - part1 , n is the
number of Part 1 CSI report bits for the nth CSI report and OCSI - part2 , n is the number of Part 2 CSI report bits
reported
NCSI-part2
for the nth CSI report priority value, OCRC,CSI - part2, N is a number of CRC bits corresponding to O
n=1
CSI- part2, n ,
-part2 +1
reported
N CSI
and OCRC,CSI- part2,N +1 is a number of CRC bits corresponding to O
n =1
CSI - part2, n
reported total
- else, the UE drops all Part 2 CSI reports and selects N CSI-part1 Part 1 CSI report(s), from the NCSI CSI reports
in ascending priority value [6, TS 38.214], for transmission together with the HARQ-ACK and SR
reported
information bits where the value of N CSI-part1 satisfies
reported
 N CSI-part1 



OACK + OSR + OCSI-part1,n + OCRC,CSI-part1,N  ≤ M RBPUCCH ⋅ Nsc,RBctrl ⋅ Nsymb
n =1 
- UCI ⋅ Qm ⋅ r and
PUCCH
 

reported
N CSI-part1
+1 

O + OSR
 ACK
+ O
n =1
CSI- part1, n + OCRC,CSI-part1,N +1  > M RB

PUCCH
⋅ Nsc,
RB
ctrl ⋅ N symb- UCI ⋅ Qm ⋅ r , where OCRC,CSI-part1,N is
PUCCH
 
reported
N CSI-part1
a number of CRC bits corresponding to OACK + OSR + O

n =1
CSI- part1, n UCI bits, and OCRC, CSI -part1, N +1 is a
reported
N CSI-part1
+1
number of CRC bits corresponding to OACK + OSR + O

n=1
CSI-part1,n UCI bits.
PUCCH
If a UE is provided a first interlace of Interlace,0 PRBs by interlace0 in InterlaceAllocation, the UE has HARQ-ACK,
SR and sub-band CSI reports to transmit, and the UE determines a PUCCH resource with PUCCH format 3, where
- the UE determines the PUCCH resource using the PUCCH resource indicator field in a last of a number of DCI
formats that have a value of a PDSCH-to-HARQ_feedback timing indicator field indicating a same slot for the
PUCCH transmission, from a PUCCH resource set provided to the UE for HARQ-ACK transmission, and
- the UE determines the PUCCH resource set as described in clauses 9.2.1 and 9.2.3 for UCI UCI bits
and
-
if ACK + SR + CSI + CRC ≤ Interlace,0
PUCCH
⋅ sc,ctrl
RB

⋅ symb-UCI
PUCCH
⋅ ௠ ⋅ , the UE transmits the HARQ-ACK, SR
total

and the CSI CSI report bits in a PUCCH over the first interlace
- else if the UE is provided a second interlace of PRBs by interlace1 and if ACK + SR + CSI +
PUCCH

Interlace,1
CRC ≤ + PUCCH
⋅
Interlace,0 ⋅ PUCCH
Interlace,1 RB
sc,ctrl PUCCH
symb-UCI
⋅ ௠ ⋅ , the UE transmits the HARQ-ACK, SR, and CSI
reports bits in a PUCCH over both the first and second interlaces
- else, the procedure is same as the corresponding one when the UE is provided PUCCH-ResourceSet by replacing
PUCCH
RB
PUCCH
with Interlace,0 PUCCH
, or, if the UE is provided interlace1, with Interlace,0 + Interlace,1
PUCCH
.
ETSI
Table 9.2.5.2-1: Code rate r corresponding to value of maxCodeRate
maxCodeRate Code rate r

0 0.08
1 0.15
2 0.25
3 0.35
4 0.45
5 0.60
6 0.80
7 Reserved
9.2.6 PUCCH repetition procedure

repeat
For PUCCH formats 1, 3, or 4, a UE can be configured a number of slots, PUCCH , for repetitions of a PUCCH
transmission by respective nrofSlots. If a UE is provided a PUCCH-config that includes subslotLengthForPUCCH, the
UE does not expect the PUCCH-config to include nrofSlots.
For repeat > 1,

PUCCH
- the UE repeats the PUCCH transmission with the UCI over repeat
PUCCH
slots
- repeat
a PUCCH transmission in each of the PUCCH slots has a same number of consecutive symbols, as provided by
nrofSymbols in PUCCH-format1, nrofSymbols in PUCCH-format3, or nrofSymbols in PUCCH-format4
- repeat
a PUCCH transmission in each of the PUCCH slots has a same first symbol, as provided by startingSymbolIndex
in PUCCH-format1, startingSymbolIndex in PUCCH-format3, or startingSymbolIndex in PUCCH-format4
- the UE is configured by interslotFrequencyHopping whether or not to perform frequency hopping for PUCCH
transmissions in different slots
- if the UE is configured to perform frequency hopping for PUCCH transmissions across different slots
- the UE performs frequency hopping per slot
- the UE transmits the PUCCH starting from a first PRB, provided by startingPRB, in slots with even
number and starting from the second PRB, provided by secondHopPRB, in slots with odd number. The
slot indicated to the UE for the first PUCCH transmission has number 0 and each subsequent slot until the
repeat
UE transmits the PUCCH in PUCCH slots is counted regardless of whether or not the UE transmits the
PUCCH in the slot
- the UE does not expect to be configured to perform frequency hopping for a PUCCH transmission within
a slot
- If the UE is not configured to perform frequency hopping for PUCCH transmissions across different slots and
if the UE is configured to perform frequency hopping for a PUCCH transmission within a slot, the frequency
hopping pattern between the first PRB and the second PRB is same within each slot
If the UE determines that, for a PUCCH transmission in a slot, the number of symbols available for the PUCCH
transmission is smaller than the value provided by nrofSymbols for the corresponding PUCCH format, the UE does not
transmit the PUCCH in the slot.
A SS/PBCH block symbol is a symbol of an SS/PBCH block with candidate SS/PBCH block index corresponding to
the SS/PBCH block index indicated to a UE by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in
ServingCellConfigCommon, as described in clause 4.1.
repeat
For unpaired spectrum, the UE determines the PUCCH slots for a PUCCH transmission starting from a slot indicated to
the UE as described in clause 9.2.3 for HARQ-ACK reporting, or a slot determined as described in clause 9.2.4 for SR
reporting or in clause 5.2.1.4 of [6, TS 38.214] for CSI reporting and having
ETSI
- an UL symbol, as described in clause 11.1, or flexible symbol that is not SS/PBCH block symbol provided by
startingSymbolIndex in PUCCH-format1, or in PUCCH-format3, or in PUCCH-format4 as a first symbol, and
- consecutive UL symbols, as described in clause 11.1, or flexible symbols that are not SS/PBCH block symbols,
starting from the first symbol, equal to or larger than a number of symbols provided by nrofsymbols in PUCCH-
format1, or in PUCCH-format3, or in PUCCH-format4
repeat
For paired spectrum or supplementary uplink band, the UE determines the PUCCH slots for a PUCCH transmission as
repeat
the PUCCH consecutive slots starting from a slot indicated to the UE as described in clause 9.2.3 for HARQ-ACK
reporting, or a slot determined as described in clause 9.2.4 for SR reporting or in clause 5.2.1.4 of [6, TS 38.214] for
CSI reporting.
repeat
If a UE would transmit a PUCCH over a first number PUCCH > 1 of slots and the UE would transmit a PUSCH with
repetition Type A over a second number of slots, and the PUCCH transmission would overlap with the PUSCH
transmission in one or more slots, and the conditions in clause 9.2.5 for multiplexing the UCI in the PUSCH are
satisfied in the overlapping slots, the UE transmits the PUCCH and does not transmit the PUSCH in the overlapping
slots.
repeat
If a UE would transmit a PUCCH over a first number PUCCH > 1 of slots and the UE would transmit a PUSCH with
repetition Type B over a second number of slots, and the PUCCH transmission would overlap with actual PUSCH
repetitions in one or more slots, and the conditions in clause 9.2.5 for multiplexing the UCI in the PUSCH are satisfied
for the overlapping actual PUSCH repetitions, the UE transmits the PUCCH and does not transmit the overlapping
actual PUSCH repetitions.
repeat
A UE does not multiplex different UCI types in a PUCCH transmission with repetitions over PUCCH > 1 slots. If a UE
would transmit a first PUCCH over more than one slot and at least a second PUCCH over one or more slots, and the
transmissions of the first PUCCH and the second PUCCH would overlap in a number of slots then, for each slot of the
number of slots and with UCI type priority of HARQ-ACK > SR > CSI with higher priority > CSI with lower priority
- the UE does not expect the first PUCCH and any of the second PUCCHs to start at a same slot and include a UCI
type with same priority
- if the first PUCCH and any of the second PUCCHs include a UCI type with same priority, the UE transmits the
PUCCH starting at an earlier slot and does not transmit the PUCCH starting at a later slot
- if the first PUCCH and any of the second PUCCHs do not include a UCI type with same priority, the UE
transmits the PUCCH that includes the UCI type with higher priority and does not transmit the PUCCH that
include the UCI type with lower priority
A UE does not expect a PUCCH that is in response to a DCI format detection to overlap with any other PUCCH that
does not satisfy the corresponding timing conditions in clause 9.2.5.
repeat
If a UE would transmit a PUCCH over PUCCH slots and the UE does not transmit the PUCCH in a slot from the repeat
repeat
PUCCH
slots due to overlapping with another PUCCH transmission in the slot, the UE counts the slot in the number of PUCCH
slots.
repeat
For DAPS operation, if a UE would transmit a PUCCH over PUCCH slots on the source MCG and the UE does not
௥௘௣௘௔௧
transmit the PUCCH in a slot from the ௉௎஼஼ு slots due to overlapping in time with UE transmission on the target
௥௘௣௘௔௧

MCG in the slot, the UE counts the slot in the number of ௉௎஼஼ு slots.
9.3 UCI reporting in physical uplink shared channel

Offset values are defined for a UE to determine a number of resources for multiplexing HARQ-ACK information and
for multiplexing CSI reports in a PUSCH. Offset values are also defined for multiplexing CG-UCI [5, TS 38.212] in a
CG-PUSCH. The offset values are signalled to a UE either by a DCI format scheduling the PUSCH transmission or by
higher layers.
If a DCI format that does not include a beta_offset indicator field schedules the PUSCH transmission from the UE and
, β offset , and β offset values that are
HARQ − ACK CSI-1 CSI-2
the UE is provided betaOffsets = 'semiStatic', the UE applies the β offset
provided by betaOffsets = 'semiStatic' for the corresponding HARQ-ACK information, Part 1 CSI reports and Part 2
CSI reports.
ETSI
If the PUSCH transmission is with a configured grant and the UE is provided CG-UCI-OnPUSCH= 'semiStatic', the UE
, β offset , and β offset values that are provided by CG-UCI-OnPUSCH = 'semiStatic' for the
HARQ − ACK CSI-1 CSI-2
applies the β offset
corresponding HARQ-ACK information, Part 1 CSI reports and Part 2 CSI reports.
If the PUSCH is scheduled by DCI format 0_0 and the UE is provided betaOffsets = 'dynamic', the UE applies the
HARQ − ACK
β offset , β offset
CSI -1
, and β offset
CSI - 2
values that are determined from the first value of betaOffsets = 'dynamic'.
If the PUSCH is a configured grant Type 2 PUSCH activated by DCI format 0_0 and the UE is provided CG-UCI-
HARQ − ACK
OnPUSCH ='dynamic', the UE applies the β offset , β offset
CSI -1
, and β offset
CSI - 2
values that are determined from the first
value of CG-UCI-OnPUSCH = 'dynamic'.
HARQ − ACK
HARQ-ACK information offsets β offset are configured to values according to Table 9.3-1. The betaOffsetACK-
HARQ −ACK HARQ −ACK
Index1, betaOffsetACK-Index2, and betaOffsetACK-Index3 respectively provide indexes I offset,0 , I offset,1 , and
HARQ −ACK
I offset,2 for the UE to use if the UE multiplexes up to 2 HARQ-ACK information bits, more than 2 and up to 11
HARQ-ACK information bits, and more than 11 bits in the PUSCH, respectively.
Part 1 CSI report and Part 2 CSI report offsets β offset and β offset , respectively, are configured to values according to
CSI-1 CSI-2
CSI-1
Table 9.3-2. The betaOffsetCSI-Part1-Index1 and betaOffsetCSI-Part2-Index1 respectively provide indexes I offset,0 and
CSI- 2
I offset,0 for the UE to use if the UE multiplexes up to 11 bits for Part 1 CSI reports or Part 2 CSI reports in the PUSCH.
CSI -1 CSI- 2
The betaOffsetCSI-Part1-Index2 and betaOffsetCSI-Part2-Index2 respectively provide indexes I offset,1 or I offset,1 for the
UE to use if the UE multiplexes more than 11 bits for Part 1 CSI reports or Part 2 CSI reports in the PUSCH.
If a DCI format that includes a beta_offset indicator field with one bit or two bits, as configured by uci-OnPUSCH,
schedules the PUSCH transmission from the UE, the UE is provided by each of {betaOffsetACK-Index1,
HARQ−ACK
betaOffsetACK-Index2, betaOffsetACK-Index3} a set of two or four I offset indexes, by each of {betaOffsetCSI-
CSI -1
Part1-Index1, betaOffsetCSI-Part1-Index2} a set of two or four I offset indexes, and by each of {betaOffsetCSI-Part2-
CSI-2
Index1, betaOffsetCSI-Part2-Index2} a set of two or four I indexes from Tables 9.3-1 and 9.3-2, respectively, for
offset
multiplexing HARQ-ACK information, Part 1 CSI reports, and Part 2 CSI reports, respectively, in the PUSCH
HARQ−ACK CSI -1 CSI-2
transmission. The beta_offset indicator field indicates a I offset value, a I offset value and a I offset value from the
respective sets of values, with the mapping defined in Table 9.3-3 and in Table 9.3-3A.
For a PUSCH transmission that is configured by a ConfiguredGrantConfig, and includes CG-UCI, the UE multiplexes
CG-UCI in the PUSCH transmission if the UE is provided by betaOffsetCG-UCI a offset CG-UCI

value, from a set of values,

with the mapping defined in Table 9.3-1. If the UE multiplexes HARQ-ACK information in the PUSCH transmission,
as described in clause 9.2.5, the UE jointly encodes the HARQ-ACK information and the CG-UCI [5, TS 38.212] and
determines a number of resources for multiplexing the combined information in a PUSCH using ୭୤୤ୱୣ୲
ୌ୅ୖ୕ି୅େ୏ which

ୌ୅ୖ୕ି୅େ୏
provides indexes ୭୤୤ୱୣ୲,ଵ
ୌ୅ୖ୕ି୅େ୏

and ୭୤୤ୱୣ୲,ଶ for the UE to use if the UE multiplexes up to 11, and more than 11
combined information bits, respectively.
ETSI
Table 9.3-1: Mapping of beta_offset values for HARQ-ACK information and/or for CG-UCI and the
index signalled by higher layers
HARQ −ACK
I offset,0 HARQ −ACK
or I offset,1
HARQ −ACK
or I offset,2 or ࡵCG-UCI
offset
۶‫ۯିۿ܀ۯ‬۱۹
ࢼ‫ܜ܍ܛ܎܎ܗ‬ or ۱۵ି‫܃‬۱۷
‫ܜ܍ܛ܎܎ܗ‬
0 1.000
1 2.000
2 2.500
3 3.125
4 4.000
5 5.000
6 6.250
7 8.000
8 10.000
9 12.625
10 15.875
11 20.000
12 31.000
13 50.000
14 80.000
15 126.000
16 Reserved
17 Reserved
18 Reserved
19 Reserved
20 Reserved
21 Reserved
22 Reserved
23 Reserved
24 Reserved
25 Reserved
26 Reserved
27 Reserved
28 Reserved
29 Reserved
30 Reserved
31 Reserved
ETSI
Table 9.3-2: Mapping of beta_offset values for CSI and the index signalled by higher layers
CSI -1
I offset,0 CSI -1
or I offset,1 β offset
CSI -1
CSI- 2
I offset,0 CSI - 2
or I offset,1 β offset
CSI-2
0 1.125
1 1.250
2 1.375
3 1.625
4 1.750
5 2.000
6 2.250
7 2.500
8 2.875
9 3.125
10 3.500
11 4.000
12 5.000
13 6.250
14 8.000
15 10.000
16 12.625
17 15.875
18 20.000
19 Reserved
20 Reserved
21 Reserved
22 Reserved
23 Reserved
24 Reserved
25 Reserved
26 Reserved
27 Reserved
28 Reserved
29 Reserved
30 Reserved
31 Reserved
ETSI
Table 9.3-3: Mapping of four beta_offset indicator values to offset indexes
HARQ −ACK HARQ − ACK HARQ −ACK CSI -1 CSI- 2 CSI -1 CSI - 2
beta_offset indicator ( I offset,0 or I offset,1 or I offset,2 ), ( I offset,0 or I offset,0 ), ( I offset,1 or I offset,1 )
'00' 1st offset index provided by higher layers
'01' 2nd offset index provided by higher layers
'10' 3rd offset index provided by higher layers
'11' 4th offset index provided by higher layers
Table 9.3-3A: Mapping of two beta_offset indicator values to offset indexes
HARQ −ACK HARQ − ACK HARQ −ACK CSI -1 CSI- 2 CSI -1 CSI - 2
beta_offset indicator ( I offset,0 or I offset,1 or I offset,2 ), ( I offset,0 or I offset,0 ), ( I offset,1 or I offset,1 )
'0' 1st offset index provided by higher layers
'1' 2nd offset index provided by higher layers
10 UE procedure for receiving control information

If the UE is configured with a SCG, the UE shall apply the procedures described in this clause for both MCG and SCG
except for PDCCH monitoring in Type0/0A/2-PDCCH CSS sets where the UE is not required to apply the procedures
in this clause for the SCG
respectively.
A UE monitors a set of PDCCH candidates in one or more CORESETs on the active DL BWP on each activated
serving cell configured with PDCCH monitoring according to corresponding search space sets where monitoring
implies decoding each PDCCH candidate according to the monitored DCI formats.
If a UE is provided monitoringCapabilityConfig for a serving cell, the UE obtains an indication to monitor PDCCH on
the serving cell for a maximum number of PDCCH candidates and non-overlapping CCEs
- per slot, as in Tables 10.1-2 and 10.1-3, if monitoringCapabilityConfig = r15monitoringcapability, or
- per span, as in Tables 10.1-2A and 10.1-3A, if monitoringCapabilityConfig = r16monitoringcapability
If the UE is not provided monitoringCapabilityConfig, the UE monitors PDCCH on the serving cell for a maximum
number of PDCCH candidates and non-overlapping CCEs per slot.
A UE can indicate a capability to monitor PDCCH according to one or more of the combinations X, Y = (2, 2), (4, 3),

and (7, 3) per SCS configuration of = 0 and = 1. A span is a number of consecutive symbols in a slot where the
UE is configured to monitor PDCCH. Each PDCCH monitoring occasion is within one span. If a UE monitors PDCCH

on a cell according to combination X, Y , the UE supports PDCCH monitoring occasions in any symbol of a slot with

minimum time separation of symbols between the first symbol of two consecutive spans, including across slots. A
span starts at a first symbol where a PDCCH monitoring occasion starts and ends at a last symbol where a PDCCH
monitoring occasion ends, where the number of symbols of the span is up to .
If a UE indicates a capability to monitor PDCCH according to multiple X, Y combinations and a configuration of
search space sets to the UE for PDCCH monitoring on a cell results to a separation of every two consecutive PDCCH
monitoring spans that is equal to or larger than the value of for one or more of the multiple combinations X, Y, the
UE monitors PDCCH on the cell according to the combination X, Y, from the one or more combinations X, Y, that is
associated with the largest maximum number of ୔ୈେେୌ
௠௔௫ ሺ௑ ௒ሻ ఓ and ௠௔௫ ሺ௑ ௒ሻ ఓ defined in Table 10.1-2A and Table 10.1-
୔ୈେେୌ
, , , , , ,
3A. The UE expects to monitor PDCCH according to the same combination X, Y in every slot on the active DL BWP
of a cell.
ETSI
A UE capability for PDCCH monitoring per slot or per span on an active DL BWP of a serving cell is defined by a
maximum number of PDCCH candidates and non-overlapped CCEs the UE can monitor per slot or per span,
respectively, on the active DL BWP of the serving cell.
For monitoring of a PDCCH candidate by a UE, if the UE
- has received ssb-PositionsInBurst in SIB1 and has not received ssb-PositionsInBurst in

ServingCellConfigCommon for a serving cell, and
- does not monitor PDCCH candidates in a Type0-PDCCH CSS set, and
- at least one RE for a PDCCH candidate overlaps with at least one RE of a candidate SS/PBCH block
corresponding to a SS/PBCH block index provided by ssb-PositionsInBurst in SIB1,
the UE is not required to monitor the PDCCH candidate.
For monitoring of a PDCCH candidate by a UE, if the UE
- has received ssb-PositionsInBurst in ServingCellConfigCommon for a serving cell, and
- does not monitor PDCCH candidates in a Type0-PDCCH CSS set, and
- at least one RE for a PDCCH candidate overlaps with at least one RE of a candidate SS/PBCH block
corresponding to a SS/PBCH block index provided by ssb-PositionsInBurst in ServingCellConfigCommon,
the UE is not required to monitor the PDCCH candidate.
If a UE monitors the PDCCH candidate for a Type0-PDCCH CSS set on the serving cell according to the procedure
described in clause 13, the UE may assume that no SS/PBCH block is transmitted in REs used for monitoring the
PDCCH candidate on the serving cell.
If at least one RE of a PDCCH candidate for a UE on the serving cell overlaps with at least one RE of lte-CRS-
ToMatchAround, or of LTE-CRS-PatternList, the UE is not required to monitor the PDCCH candidate.
If a UE is provided availableRB-SetsPerCell, the UE is not required to monitor PDCCH candidates that overlap with
any RB from RB sets that are indicated as unavailable for receptions by an available RB set indicator field in DCI
format 2_0 as described in clause 11.1.1. If the UE does not obtain the available RB set indicator for a symbol, the UE
monitors PDCCH candidates on all RB sets in the symbol.
If a UE can support
-
DL
a first set of cells,0 serving cells where the UE is either not provided coresetPoolIndex or is provided
coresetPoolIndex with a single value for all CORESETs on all DL BWPs of each scheduling cell from the first
set of serving cells, and
- DL
a second set of cells,1
serving cells where the UE is not provided coresetPoolIndex or is provided
coresetPoolIndex with a value 0 for a first CORESET, and with a value 1 for a second CORESET on any DL
BWP of each scheduling cell from the second set of serving cells
the UE determines, for the purpose of reporting pdcch-BlindDetectionCA, a number of serving cells as DL
+⋅

cells,0
DL
cells,1
where is a value reported by the UE.
If a UE indicates in UE-NR-Capability a carrier aggregation capability larger than 4 serving cells and the UE is not
provided monitoringCapabilityConfig for any downlink cell or if the UE is provided monitoringCapabilityConfig =
r15monitoringcapability for all downlink cells where the UE monitors PDCCH, the UE includes in UE-NR-Capability
an indication for a maximum number of PDCCH candidates and for a maximum number of non-overlapped CCEs the
UE can monitor per slot when the UE is configured for carrier aggregation operation over more than 4 cells. When a UE
is not configured for NR-DC operation, the UE determines a capability to monitor a maximum number of PDCCH
cap
candidates and a maximum number of non-overlapped CCEs per slot that corresponds to cells downlink cells, where
- cap DL

is cells,0
cells
+ ⋅ cells,1
DL

if the UE does not provide pdcch-BlindDetectionCA where
DL
cells,0
+ DL
cells,1
is the
number of configured downlink serving cells
- otherwise, cap
cells
is the value of pdcch-BlindDetectionCA
ETSI
When a UE is configured for NR-DC operation, the UE determines a capability to monitor a maximum number of
PDCCH candidates and a maximum number of non-overlapped CCEs per slot that corresponds to cells = MCG
cap
cells

downlink cells for the MCG where MCG cells
is provided by pdcch-BlindDetection for the MCG and determines a capability
to monitor a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs per slot that

corresponds to cells = SCG
cap

cells
downlink cells for the SCG where SCG
cells
is provided by pdcch-BlindDetection for the
SCG. When the UE is configured for carrier aggregation operation over more than 4 cells, or for a cell group when the
UE is configured for NR-DC operation, the UE does not expect to monitor per slot a number of PDCCH candidates or a
number of non-overlapped CCEs that is larger than the maximum number as derived from the corresponding value of
cap
cells
.
DL,cells
When a UE is configured for NR-DC operation with a total of NR−DC downlink cells on both the MCG and the SCG,
the UE expects to be provided pdcch-BlindDetection for the MCG and pdcch-BlindDetection for the SCG with values
that satisfy
- pdcch-BlindDetection for the MCG + pdcch-BlindDetection for the SCG <= pdcch-BlindDetectionCA, if the UE
reports pdcch-BlindDetectionCA, or
- pdcch-BlindDetection for the MCG + pdcch-BlindDetection for the SCG <= DL,cells
NR−DC
, if the UE does not report
pdcch-BlindDetectionCA.
For NR-DC operation, the UE may indicate, through pdcch-BlindDetectionMCG-UE and pdcch-BlindDetectionSCG-
UE, respective maximum values for pdcch-BlindDetection for the MCG and pdcch-BlindDetection for the SCG.
If the UE reports pdcch-BlindDetectionCA,
- the value range of pdcch-BlindDetectionMCG-UE or of pdcch-BlindDetectionSCG-UE is [1, …, pdcch-

BlindDetectionCA-1], and
- pdcch-BlindDetectionMCG-UE + pdcch-BlindDetectionSCG-UE >= pdcch-BlindDetectionCA.
DL,cells
Otherwise, if NR−DC,max is a maximum total number of downlink cells that the UE can be configured on both the MCG
and the SCG for NR-DC as indicated in UE-NR-Capability,
- the value range of pdcch-BlindDetectionMCG-UE or of pdcch-BlindDetectionSCG-UE is [1, 2, 3], and
- pdcch-BlindDetectionMCG-UE + pdcch-BlindDetectionSCG-UE >= DL,cells

NR−DC,max
.
If a UE indicates in UE-NR-Capability a carrier aggregation capability larger than two downlink cells, the UE includes
in UE-NR-Capability an indication for a maximum number of PDCCH candidates and a maximum number of non-
overlapped CCEs that the UE can monitor per span when the UE is configured for carrier aggregation operation over
more than two downlink cells with monitoringCapabilityConfig = r16monitoringcapability. When a UE is not
configured for NR-DC operation and the UE is provided monitoringCapabilityConfig = r16monitoringcapability for all
downlink cell where the UE monitors PDCCH, the UE determines a capability to monitor a maximum number of
PDCCH candidates and a maximum number of non-overlapped CCEs per span that corresponds to ௖௘௟௟௦
௖௔௣ି௥ଵ଺ downlink
cells, where
-
௖௔௣ି௥ଵ଺ is the number of configured downlink cells if the UE does not provide pdcch-MonitoringCA
௖௘௟௟௦
-
௖௔௣ି௥ଵ଺ is the value of pdcch-MonitoringCA
otherwise, ௖௘௟௟௦
When a UE is configured for NR-DC operation and the UE is provided monitoringCapabilityConfig =

r16monitoringcapability for all downlink cells where the UE monitors PDCCH, the UE determines a capability to
monitor a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs per span that
corresponds to
ୡୟ୮ି୰ଵ଺ = ୑େୋ downlink cells for the MCG where ୑େୋ is provided by pdcch-BlindDetection2 for the
ୡୣ୪୪ୱ
- ୡୣ୪୪ୱ ୰ଵ଺, ୡୣ୪୪ୱ ୰ଵ଺ ,
MCG, and
ୡୟ୮ି୰ଵ଺ = ୗେୋ downlink cells for the SCG where ୗେୋ is provided by pdcch-BlindDetection2 for the
ୡୣ୪୪ୱ
- ୡୣ୪୪ୱ ୰ଵ଺, ୡୣ୪୪ୱ ୰ଵ଺ ,
SCG
ETSI
When the UE is configured for carrier aggregation operation over more than 2 cells, or for a cell group when the UE is
configured for NR-DC operation, the UE does not expect to monitor per span a number of PDCCH candidates or a
number of non-overlapped CCEs that is larger than the maximum number as derived from the corresponding value of
ୡୟ୮ି୰ଵ଺
ୡୣ୪୪ୱ .
ୈ୐,ୡୣ୪୪ୱ downlink cells on both the MCG and the SCG

When a UE is configured for NR-DC operation with a total of ୒ୖିୈେ
and the UE is provided monitoringCapabilityConfig = r16monitoringcapability for all downlink cells where the UE
monitors PDCCH, the UE expects to be provided pdcch-BlindDetection for the MCG and pdcch-BlindDetection for the
SCG with values that satisfy
- pdcch-BlindDetection2 for the MCG + pdcch-BlindDetection2 for the SCG <= pdcch-MonitoringCA, if the UE
reports pdcch-MonitoringCA, or
- pdcch-BlindDetection2 for the MCG + pdcch-BlindDetection2 for the SCG <= ୈ୐ ୡୣ୪୪ୱ , if the UE does not
୒ୖିୈେ,
report pdcch-MonitoringCA
When a UE is configured for NR-DC operation and the UE is provided monitoringCapabilityConfig =

r16monitoringcapability for all downlink cells where the UE monitors PDCCH, the UE may indicate, through pdcch-
BlindDetectionMCG-UE-r16 and pdcch-BlindDetectionSCG-UE-r16, respective maximum values for pdcch-
BlindDetection for the MCG and pdcch-BlindDetection for the SCG.
If the UE reports pdcch-MonitoringCA,
- the value range of pdcch-BlindDetectionMCG-UE-r16 or of pdcch-BlindDetectionSCG-UE-r16 is [1, …, pdcch-

MonitoringCA-1], and
- pdcch-BlindDetectionMCG-UE-r16 + pdcch-BlindDetectionSCG-UE-r16 >= pdcch-MonitoringCA.

ୈ୐,ୡୣ୪୪ୱ

Otherwise, if ୒ୖିୈେ ,୫ୟ୶,୰ଵ଺
is a maximum total number of downlink cells for which the UE is provided
monitoringCapabilityConfig = r16monitoringcapability and the UE is configured on both the MCG and the SCG for
NR-DC as indicated in UE-NR-Capability
- the value of pdcch-BlindDetectionMCG-UE-r16 or of pdcch-BlindDetectionSCG-UE-r16 is 1,

ୈ୐ ୡୣ୪୪ୱ
୒ୖିୈେ ୫ୟ୶ ୰ଵ଺.
,
- pdcch-BlindDetectionMCG-UE-r16 + pdcch-BlindDetectionSCG-UE-r16 >= , ,
If a UE indicates in UE-NR-Capability a carrier aggregation capability larger than one downlink cell with
monitoringCapabilityConfig = r15monitoringcapability or larger than one downlink cell with
monitoringCapabilityConfig = r16monitoringcapability, the UE includes in UE-NR-Capability an indication for a
maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs the UE can monitor for
downlink cells with monitoringCapabilityConfig = r15monitoringcapability or for downlink cells with
monitoringCapabilityConfig = r16monitoringcapability when the UE is configured for carrier aggregation operation
over more than two downlink cells with at least one downlink cell with monitoringCapabilityConfig =
r15monitoringcapability and at least one downlink cell with monitoringCapabilityConfig = r16monitoringcapability.
When a UE is not configured for NR-DC operation, the UE determines a capability to monitor a maximum number of
௖௔௣ି௥ଵ଺
PDCCH candidates and a maximum number of non-overlapped CCEs per slot or per span that corresponds to ௖௘௟௟௦,௥ଵହ
௖௔௣ି௥ଵ଺

downlink cells or to ௖௘௟௟௦ ,௥ଵ଺ downlink cells, respectively, where
௖௔௣ି௥ଵ଺ is the number of configured downlink cells if the UE does not provide pdcch-BlindDetectionCA1
௖௘௟௟௦
- , ௥ଵହ
- otherwise,
௖௔௣ି௥ଵ଺
௖௘௟௟௦
- if the UE reports only one combination of (pdcch-BlindDetectionCA1, pdcch-BlindDetectionCA2), ௥ଵହ
,
is the value of pdcch-BlindDetectionCA1
- ୡୟ୮ି୰ଵ଺
else, ୡୣ୪୪ୱ,୰ଵହ is the value of pdcch-BlindDetectionCA1 from a combination of (pdcch-BlindDetectionCA1,
pdcch-BlindDetectionCA2) that is provided by pdcch-BlindDetectionCA-CombIndicator
and
௖௔௣ି௥ଵ଺ is the number of configured downlink cells if the UE does not provide pdcch-BlindDetectionCA2
௖௘௟௟௦
- , ௥ଵ଺
- otherwise,
ETSI
௖௔௣ି௥ଵ଺
௖௘௟௟௦
- if the UE reports only one combination of (pdcch-BlindDetectionCA1, pdcch-BlindDetectionCA2), , ௥ଵ଺
is the value of pdcch-BlindDetectionCA2
- ୡୟ୮ି୰ଵ଺
else, ୡୣ୪୪ୱ,୰ଵ଺ is the value of pdcch-BlindDetectionCA2 from a combination of (pdcch-BlindDetectionCA1,
pdcch-BlindDetectionCA2) that is provided by pdcch-BlindDetectionCA-CombIndicator
When a UE is configured for NR-DC operation and is provided monitoringCapabilityConfig = r15monitoringcapability

for at least one downlink cell and monitoringCapabilityConfig = r16monitoringcapability for at least one downlink cell
where the UE monitors PDCCH, the UE determines a capability to monitor a maximum number of PDCCH candidates
and a maximum number of non-overlapped CCEs that corresponds to
ୡୣ୪୪ୱ
- ,୰ଵହ ୡୣ୪୪ୱ ୰ଵହ , ୡୣ୪୪ୱ ୰ଵହ ,
MCG,
ୡୣ୪୪ୱ
- ,୰ଵହ ୡୣ୪୪ୱ ୰ଵହ , ୡୣ୪୪ୱ ୰ଵହ ,
SCG, and
ୡୣ୪୪ୱ
- ,୰ଵ଺ ୡୣ୪୪ୱ ୰ଵ଺ , ୡୣ୪୪ୱ ୰ଵ଺ ,
MCG,
ୡୣ୪୪ୱ
- ,୰ଵ଺ ୡୣ୪୪ୱ ୰ଵ଺ , ୡୣ୪୪ୱ ୰ଵ଺ ,
SCG
When the UE is configured for carrier aggregation operation over more than two downlink cells with at least one
downlink cell with monitoringCapabilityConfig = r15monitoringcapability and at least one downlink cell with
monitoringCapabilityConfig = r16monitoringcapability, or for a cell group when the UE is configured for NR-DC
operation, the UE does not expect to
- monitor per slot a number of PDCCH candidates or a number of non-overlapped CCEs that is larger than the

maximum number as derived from the corresponding value of ୡୣ୪୪ୱ,୰ଵହ , and
- monitor per span a number of PDCCH candidates or a number of non-overlapped CCEs that is larger than the

maximum number as derived from the corresponding value of ୡୣ୪୪ୱ,୰ଵ଺
ୈ୐,ୡୣ୪୪ୱ downlink cells on both the MCG and the SCG

When a UE is configured for NR-DC operation with a total of ୒ୖିୈେ
ୈ୐,ୡୣ୪୪ୱ downlink cells and
and the UE is provided monitoringCapabilityConfig = r15monitoringcapability for ୒ୖିୈେ ,୰ଵହ
ୈ୐,ୡୣ୪୪ୱ downlink cells where the UE monitors PDCCH,

monitoringCapabilityConfig = r16monitoringcapability for ୒ୖିୈେ ,୰ଵ଺
the UE expects to be provided pdcch-BlindDetection3 and pdcch-BlindDetection2 for the MCG, and pdcch-
BlindDetection3 and pdcch-BlindDetection2 for the SCG with values that satisfy
- pdcch-BlindDetection3 for the MCG + pdcch-BlindDetection3 for the SCG <= pdcch-BlindDetectionCA, if the
UE reports pdcch-BlindDetectionCA1, or
ୈ୐ ୡୣ୪୪ୱ , if the UE does not
୒ୖିୈେ ୰ଵହ
,
- pdcch-BlindDetection3 for the MCG + pdcch-BlindDetection3 for the SCG <= ,
report pdcch-BlindDetectionCA1
and
- pdcch-BlindDetection2 for the MCG + pdcch-BlindDetection2 for the SCG <= pdcch-BlindDetectionCA2, if the
UE reports pdcch-BlindDetectionCA2, or
ୈ୐,ୡୣ୪୪ୱ , if the UE does not
pdcch-BlindDetection2 for the MCG + pdcch-BlindDetection2 for the SCG <= N୒ୖିୈେ ,୰ଵ଺
-
report pdcch-BlindDetectionCA2
When a UE is configured for NR-DC operation and is provided monitoringCapabilityConfig = r15monitoringcapability

for at least one downlink cell and monitoringCapabilityConfig = r16monitoringcapability for at least one downlink cell
where the UE monitors PDCCH, the UE may indicate, through pdcch-BlindDetectionMCG-UE1 and pdcch-
BlindDetectionSCG-UE1, respective maximum values for pdcch-BlindDetection3 for the MCG and pdcch-
BlindDetection3 for the SCG, and through pdcch-BlindDetectionMCG-UE2 and pdcch-BlindDetectionSCG-UE2
respective maximum values for pdcch-BlindDetection2 for the MCG and pdcch-BlindDetection2 for the SCG.
ETSI
If the UE reports pdcch-BlindDetectionCA1,
- the value range of pdcch-BlindDetectionMCG-UE1 or of pdcch-BlindDetectionSCG-UE1 is [0, 1, …, pdcch-

BlindDetectionCA1], and
- pdcch-BlindDetectionMCG-UE1 + pdcch-BlindDetectionSCG-UE1 >= pdcch-BlindDetectionCA1.
Otherwise, if ୒ୖିୈେ ,୫ୟ୶,୰ଵହ
- the value range of pdcch-BlindDetectionMCG-UE1 or of pdcch-BlindDetectionSCG-UE1 is [0, 1, 2],

୒ୖିୈେ ୫ୟ୶ ୰ଵହ.
,
- pdcch-BlindDetectionMCG-UE1 + pdcch-BlindDetectionSCG-UE1 >= , ,
If the UE reports pdcch-BlindDetectionCA2
- the value range of pdcch-BlindDetectionMCG-UE2 or of pdcch-BlindDetectionSCG-UE2 is [0, 1, …, pdcch-

BlindDetectionCA2], and
- pdcch-BlindDetectionMCG-UE2 + pdcch-BlindDetectionSCG-UE2 >= pdcch-BlindDetectionCA2.
Otherwise, if ୒ୖିୈେ ,୫ୟ୶,୰ଵ଺
- the value range of pdcch-BlindDetectionMCG-UE2 or of pdcch-BlindDetectionSCG-UE2 is [0, 1],

୒ୖିୈେ ୫ୟ୶ ୰ଵ଺.
,
- pdcch-BlindDetectionMCG-UE2 + pdcch-BlindDetectionSCG-UE2 >= , ,
10.1 UE procedure for determining physical downlink control

channel assignment
A set of PDCCH candidates for a UE to monitor is defined in terms of PDCCH search space sets. A search space set
can be a CSS set or a USS set. A UE monitors PDCCH candidates in one or more of the following search spaces sets
- a Type0-PDCCH CSS set configured by pdcch-ConfigSIB1 in MIB or by searchSpaceSIB1 in PDCCH-

ConfigCommon or by searchSpaceZero in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a
SI-RNTI on the primary cell of the MCG
- a Type0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for

a DCI format with CRC scrambled by a SI-RNTI on the primary cell of the MCG
- a Type1-PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommon for a DCI format with
CRC scrambled by a RA-RNTI, a MsgB-RNTI, or a TC-RNTI on the primary cell
- a Type2-PDCCH CSS set configured by pagingSearchSpace in PDCCH-ConfigCommon for a DCI format with
CRC scrambled by a P-RNTI on the primary cell of the MCG
- a Type3-PDCCH CSS set configured by SearchSpace in PDCCH-Config with searchSpaceType = common for
DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-
SRS-RNTI, or CI-RNTI and, only for the primary cell, C-RNTI, MCS-C-RNTI, CS-RNTI(s), or PS-RNTI and
- a USS set configured by SearchSpace in PDCCH-Config with searchSpaceType = ue-Specific for DCI formats
with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI(s), SL-RNTI, SL-CS-RNTI, or SL
Semi-Persistent Scheduling V-RNTI.
For a DL BWP, if a UE is not provided searchSpaceSIB1 for Type0-PDCCH CSS set by PDCCH-ConfigCommon, the
UE does not monitor PDCCH candidates for a Type0-PDCCH CSS set on the DL BWP. The Type0-PDCCH CSS set is
defined by the CCE aggregation levels and the number of PDCCH candidates per CCE aggregation level given in Table
10.1-1. If the active DL BWP and the initial DL BWP have same SCS and same CP length and the active DL BWP
includes all RBs of the CORESET with index 0, or the active DL BWP is the initial DL BWP, the CORESET
ETSI
configured for Type0-PDCCH CSS set has CORESET index 0 and the Type0-PDCCH CSS set has search space set
index 0.
For a DL BWP, if a UE is not provided searchSpaceOtherSystemInformation for Type0A-PDCCH CSS set, the UE
does not monitor PDCCH for Type0A-PDCCH CSS set on the DL BWP. The CCE aggregation levels and the number
of PDCCH candidates per CCE aggregation level for Type0A-PDCCH CSS set are given in Table 10.1-1.
For a DL BWP, if a UE is not provided ra-SearchSpace for Type1-PDCCH CSS set, the UE does not monitor PDCCH
for Type1-PDCCH CSS set on the DL BWP. If the UE has not been provided a Type3-PDCCH CSS set or a USS set
and the UE has received a C-RNTI and has been provided a Type1-PDCCH CSS set, the UE monitors PDCCH
candidates for DCI format 0_0 and DCI format 1_0 with CRC scrambled by the C-RNTI in the Type1-PDCCH CSS set.
If a UE is not provided pagingSearchSpace for Type2-PDCCH CSS set, the UE does not monitor PDCCH for Type2-
PDCCH CSS set on the DL BWP. The CCE aggregation levels and the number of PDCCH candidates per CCE
aggregation level for Type2-PDCCH CSS set are given in Table 10.1-1.
If a UE is provided a zero value for searchSpaceID in PDCCH-ConfigCommon for a Type0/0A/2-PDCCH CSS set, the
UE determines monitoring occasions for PDCCH candidates of the Type0/0A/2-PDCCH CSS set as described in clause
13, and the UE is provided a C-RNTI, the UE monitors PDCCH candidates only at monitoring occasions associated
with a SS/PBCH block, where the SS/PBCH block is determined by the most recent of
- a MAC CE activation command indicating a TCI state of the active BWP that includes a CORESET with index
0, as described in [6, TS 38.214], where the TCI-state includes a CSI-RS which is quasi-co-located with the
SS/PBCH block, or
- a random access procedure that is not initiated by a PDCCH order that triggers a contention-free random access
procedure
If a UE monitors PDCCH candidates for DCI formats with CRC scrambled by a C-RNTI and the UE is provided a non-
zero value for searchSpaceID in PDCCH-ConfigCommon for a Type0/0A/2-PDCCH CSS set, the UE determines
monitoring occasions for PDCCH candidates of the Type0/0A/2-PDCCH CSS set based on the search space set
associated with the value of searchSpaceID.
The UE may assume that the DM-RS antenna port associated with PDCCH receptions in the CORESET configured by
pdcch-ConfigSIB1 in MIB, the DM-RS antenna port associated with corresponding PDSCH receptions, and the
corresponding SS/PBCH block are quasi co-located with respect to average gain, quasi co-location 'typeA' and 'typeD'
properties, when applicable [6, TS 38.214], if the UE is not provided a TCI state indicating quasi co-location
information of the DM-RS antenna port for PDCCH reception in the CORESET. The value for the DM-RS scrambling
sequence initialization is the cell ID. A SCS is provided by subCarrierSpacingCommon in MIB.
For single cell operation or for operation with carrier aggregation in a same frequency band, a UE does not expect to
monitor a PDCCH in a Type0/0A/2/3-PDCCH CSS set or in a USS set if a DM-RS for monitoring a PDCCH in a
Type1-PDCCH CSS set is not configured with same qcl-Type set to 'typeD' properties [6, TS 38.214] with a DM-RS for
monitoring the PDCCH in the Type0/0A/2/3-PDCCH CSS set or in the USS set, and if the PDCCH or an associated
PDSCH overlaps in at least one symbol with a PDCCH the UE monitors in a Type1-PDCCH CSS set or with an
associated PDSCH.
If a UE is provided
- one or more search space sets by corresponding one or more of searchSpaceZero, searchSpaceSIB1,
searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, and
- a C-RNTI, an MCS-C-RNTI, or a CS-RNTI
the UE monitors PDCCH candidates for DCI format 0_0 and DCI format 1_0 with CRC scrambled by the C-RNTI, the
MCS-C-RNTI, or the CS-RNTI in the one or more search space sets in a slot where the UE monitors PDCCH
candidates for at least a DCI format 0_0 or a DCI format 1_0 with CRC scrambled by SI-RNTI, RA-RNTI, MsgB-
RNTI, or P-RNTI.
If a UE is provided
- one or more search space sets by corresponding one or more of searchSpaceZero, searchSpaceSIB1,
searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, or a CSS set by PDCCH-Config,
and
ETSI
- a SI-RNTI, a P-RNTI, a RA-RNTI, a MsgB-RNTI, a SFI-RNTI, an INT-RNTI, a TPC-PUSCH-RNTI, a TPC-

PUCCH-RNTI, or a TPC-SRS-RNTI
then, for a RNTI from any of these RNTIs, the UE does not expect to process information from more than one DCI
format with CRC scrambled with the RNTI per slot.
Table 10.1-1: CCE aggregation levels and maximum number of PDCCH candidates per CCE
aggregation level for CSS sets configured by searchSpaceSIB1
CCE Aggregation Level Number of Candidates
4 4
8 2
16 1
For each DL BWP configured to a UE in a serving cell, the UE can be provided by higher layer signalling with
- ≤ 3 CORESETs if coresetPoolIndex is not provided, or if a value of coresetPoolIndex is same for all

CORESETs if coresetPoolIndex is provided
- ≤ 5 CORESETs if coresetPoolIndex is not provided for a first CORESET, or is provided and has a value 0 for
a first CORESET, and is provided and has a value 1 for a second CORESET
For each CORESET, the UE is provided the following by ControlResourceSet:
-
a CORESET index , by controlResourceSetId or by controlResourceSetId-v1610, where
-
0 < < 12 if coresetPoolIndex is not provided, or if a value of coresetPoolIndex is same for all CORESETs
if coresetPoolIndex is provided;
-
0 < < 16 if coresetPoolIndex is not provided for a first CORESET, or is provided and has a value 0 for a
first CORESET, and is provided and has a value 1 for a second CORESET;
- a DM-RS scrambling sequence initialization value by pdcch-DMRS-ScramblingID;
- a precoder granularity for a number of REGs in the frequency domain where the UE can assume use of a same
DM-RS precoder by precoderGranularity;
- a number of consecutive symbols provided by duration;
- a set of resource blocks provided by frequencyDomainResources;
- CCE-to-REG mapping parameters provided by cce-REG-MappingType;
- an antenna port quasi co-location, from a set of antenna port quasi co-locations provided by TCI-State, indicating
quasi co-location information of the DM-RS antenna port for PDCCH reception in a respective CORESET;
- an indication for a presence or absence of a transmission configuration indication (TCI) field for a DCI format,
other than DCI format 1_0, that schedules PDSCH receptions or indicates SPS PDSCH release or indicates SCell
dormancy or indicates a request for a Type-3 HARQ-ACK codebook report without scheduling PDSCH and is

transmitted by a PDCCH in CORESET , by tci-PresentInDCI or tci-PresentDCI-1-2.
When precoderGranularity = allContiguousRBs, a UE does not expect
- to be configured a set of resource blocks of a CORESET that includes more than four sub-sets of resource blocks
that are not contiguous in frequency
- any RE of a CORESET to overlap with any RE determined from lte-CRS-ToMatchAround, or from LTE-CRS-
PatternList, or with any RE of a SS/PBCH block.
For each CORESET in a DL BWP of a serving cell, a respective frequencyDomainResources provides a bitmap
- if a CORESET is not associated with any search space set configured with freqMonitorLocations, the bits of the
bitmap have a one-to-one mapping with non-overlapping groups of 6 consecutive PRBs, in ascending order of
the PRB index in the DL BWP bandwidth of ୖ୆
୆୛୔ PRBs with starting common RB position ୆୛୔ ୱ୲ୟ୰୲ , where the

⌈
ୱ୲ୟ୰୲ ⌉
first common RB of the first group of 6 PRBs has common RB index 6 ⋅ ୆୛୔ /6 if rb-Offset is not provided,
ETSI
or the first common RB of the first group of 6 PRBs has common RB index ୱ୲ୟ୰୲ + ୖ୆
୆୛୔ ୭୤୤ୱୣ୲ where ୖ୆
୭୤୤ୱୣ୲ is
provided by rb-Offset.
- if a CORESET is associated with at least one search space set configured with freqMonitorLocations, the first
ୱ୧୸ୣ,ୱୣ୲଴ bits of the bitmap have a one-to-one mapping with non-overlapping groups of 6 consecutive PRBs, in
ୖ୆ୋ

ascending order of the PRB index in each RB set in the DL BWP bandwidth of ୖ୆
ୱ୲ୟ୰୲ ,ఓ
୆୛୔ PRBs with starting
common RB position ௦଴ା௞,ୈ୐ [6, TS 38.214], where the first common RB of the first group of 6 PRBs has
ୱ୲ୟ୰୲,ఓ
common RB index ௦଴ା௞,ୈ୐ + ୖ୆ ୭୤୤ୱୣ୲ and k is indicated by freqMonitorLocations if provided for a search space
ୱ୧୸ୣ ୱ୧୸ୣ ୭୤୤ୱୣ୲ ୱ୧୸ୣ
set; otherwise, = 0. ୖ୆ୋ,ୱୣ୲଴ = ( ୖ୆,ୱୣ୲଴ − ୖ୆ )/6 , ୖ୆,ୱୣ୲଴ is a number of available PRBs in the RB set
୭୤୤ୱୣ୲ ୭୤୤ୱୣ୲
0 for the DL BWP, and ୖ୆ is provided by rb-Offset or ୖ୆ = 0 if rb-Offset is not provided. If a UE is
provided RB sets in the DL BWP, the UE expects that the RBs of the CORESET are within the union of the
PRBs in the RB sets of the DL BWP.
For a CORESET other than a CORESET with index 0,
- if a UE has not been provided a configuration of TCI state(s) by tci-StatesPDCCH-ToAddList and tci-
StatesPDCCH-ToReleaseList for the CORESET, or has been provided initial configuration of more than one TCI
states for the CORESET by tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList but has not
received a MAC CE activation command for one of the TCI states as described in [11, TS 38.321], the UE
assumes that the DM-RS antenna port associated with PDCCH receptions is quasi co-located with the SS/PBCH
block the UE identified during the initial access procedure;
- if a UE has been provided a configuration of more than one TCI states by tci-StatesPDCCH-ToAddList and tci-
StatesPDCCH-ToReleaseList for the CORESET as part of Reconfiguration with sync procedure as described in
[12, TS 38.331] but has not received a MAC CE activation command for one of the TCI states as described in
[11, TS 38.321], the UE assumes that the DM-RS antenna port associated with PDCCH receptions is quasi co-
located with the SS/PBCH block or the CSI-RS resource the UE identified during the random access procedure
initiated by the Reconfiguration with sync procedure as described in [12, TS 38.331].
For a CORESET with index 0, the UE assumes that a DM-RS antenna port for PDCCH receptions in the CORESET is
quasi co-located with
- the one or more DL RS configured by a TCI state, where the TCI state is indicated by a MAC CE activation
command for the CORESET, if any, or
- a SS/PBCH block the UE identified during a most recent random access procedure not initiated by a PDCCH
order that triggers a contention-free random access procedure, if no MAC CE activation command indicating a
TCI state for the CORESET is received after the most recent random access procedure.
For a CORESET other than a CORESET with index 0, if a UE is provided a single TCI state for a CORESET, or if the
UE receives a MAC CE activation command for one of the provided TCI states for a CORESET, the UE assumes that
the DM-RS antenna port associated with PDCCH receptions in the CORESET is quasi co-located with the one or more
DL RS configured by the TCI state. For a CORESET with index 0, the UE expects that a CSI-RS configured with qcl-
Type set to 'typeD' in a TCI state indicated by a MAC CE activation command for the CORESET is provided by a
SS/PBCH block
- if the UE receives a MAC CE activation command for one of the TCI states, the UE applies the activation
ୱ୳ୠ୤୰ୟ୫ୣ,ఓ where is the slot where the UE would transmit a

command in the first slot that is after slot + 3 ୱ୪୭୲
PUCCH with HARQ-ACK information for the PDSCH providing the activation command and is the SCS
configuration for the PUCCH. The active BWP is defined as the active BWP in the slot when the activation
command is applied.
If the UE is provided by simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2 up to two lists of cells for

simultaneous TCI state activation, the UE applies the antenna port quasi co-location provided by TCI-States with same
activated tci-StateID value to CORESETs with a same index in all configured DL BWPs of all configured cells in a list
determined from a serving cell index, where tci-StateID, the CORESET index and the serving cell index are provided
by a MAC CE command.

For each DL BWP configured to a UE in a serving cell, the UE is provided by higher layers with ≤ 10 search space

sets where, for each search space set from the search space sets, the UE is provided the following by SearchSpace:
-
a search space set index , 0 < < 40 , by searchSpaceId
ETSI
- an association between the search space set and a CORESET by controlResourceSetId or by

controlResourceSetId-v1610
- a PDCCH monitoring periodicity of ௦ slots and a PDCCH monitoring offset of ௦ slots, by

monitoringSlotPeriodicityAndOffset
- a PDCCH monitoring pattern within a slot, indicating first symbol(s) of the CORESET within a slot for PDCCH
monitoring, by monitoringSymbolsWithinSlot
- a duration of௦ < ௦ slots indicating a number of slots that the search space set exists by duration
-
௅
a number of PDCCH candidates ௦ per CCE aggregation level by aggregationLevel1, aggregationLevel2,
( )
aggregationLevel4, aggregationLevel8, and aggregationLevel16, for CCE aggregation level 1, CCE aggregation
level 2, CCE aggregation level 4, CCE aggregation level 8, and CCE aggregation level 16, respectively
-
an indication that search space set is either a CSS set or a USS set by searchSpaceType
- if search space set is a CSS set

- an indication by dci-Format0-0-AndFormat1-0 to monitor PDCCH candidates for DCI format 0_0 and DCI
format 1_0
- an indication by dci-Format2-0 to monitor one or two PDCCH candidates, or to monitor one PDCCH
candidate per RB set if the UE is provided freqMonitorLocations for the search space set, for DCI format 2_0
and a corresponding CCE aggregation level
- an indication by dci-Format2-1 to monitor PDCCH candidates for DCI format 2_1
-
if search space set is a USS set, an indication by dci-Formats to monitor PDCCH candidates either for DCI
format 0_0 and DCI format 1_0, or for DCI format 0_1 and DCI format 1_1, or an indication by dci-FormatsExt
to monitor PDCCH candidates for DCI format 0_2 and DCI format 1_2, or for DCI format 0_1, DCI format 1_1,
DCI format 0_2, and DCI format 1_2, or an indication by dci-FormatsSL to monitor PDCCH candidates for DCI
format 0_0 and DCI format 1_0, or for DCI format 0_1 and DCI format 1_1, or for DCI format 3_0, or for DCI
format 3_1, or for DCI format 3_0 and DCI format 3_1
- a bitmap by freqMonitorLocations, if provided, to indicate an index of one or more RB sets for the search space

set , where the MSB in the bitmap corresponds to RB set − 1 in the DL BWP. For RB set indicated in the
bitmap, the first PRB of the frequency domain monitoring location confined within the RB set is given by
ୱ୲ୟ୰୲,ఓ ୭୤୤ୱୣ୲
ୱ୲ୟ୰୲,ఓ
௦଴ା௞,ୈ୐ + ୖ୆ , where ௦଴ା௞,ୈ୐ is the index of first common RB of the RB set [6, TS 38.214], and
୭୤୤ୱୣ୲
ୖ୆ is provided by rb-Offset or ୖ୆ ୭୤୤ୱୣ୲ = 0 if rb-Offset is not provided. For each RB set with a corresponding
value of 1 in the bitmap, the frequency domain resource allocation pattern for the monitoring location is
determined based on the first ୖ୆ୋୱ୧୸ୣ,ୱୣ୲ ଴ bits in frequencyDomainResources provided by the associated
CORESET configuration.
If the monitoringSymbolsWithinSlot indicates to a UE to monitor PDCCH in a subset of up to three consecutive symbols

that are same in every slot where the UE monitors PDCCH for all search space sets, the UE does not expect to be
configured with a PDCCH SCS other than 15 kHz if the subset includes at least one symbol after the third symbol.
A UE does not expect to be provided a first symbol and a number of consecutive symbols for a CORESET that results
to a PDCCH candidate mapping to symbols of different slots.
A UE does not expect any two PDCCH monitoring occasions on an active DL BWP, for a same search space set or for
different search space sets, in a same CORESET to be separated by a non-zero number of symbols that is smaller than
the CORESET duration.
A UE determines a PDCCH monitoring occasion on an active DL BWP from the PDCCH monitoring periodicity, the

PDCCH monitoring offset, and the PDCCH monitoring pattern within a slot. For search space set , the UE determines
ETSI
that a PDCCH monitoring occasion(s) exists in a slot with number ௦ఓ௙ [4, TS 38.211] in a frame with number ௙ if (௙ .
௙௥௔௠௘ ఓ + ఓ - ) mod
,
௦௟௢௧ ௦ ௙ ௦ఓ
,
௦ =0
. The UE monitors PDCCH candidates for search space set for ௦ consecutive slots,
−
,
starting from slot ௦ ௙ , and does not monitor PDCCH candidates for search space set for the next ௦ ௦ consecutive
,
slots.
A USS at CCE aggregation level ∈ 1, 2, 4, 8, 16 is defined by a set of PDCCH candidates for CCE aggregation level
.
If a UE is configured with CrossCarrierSchedulingConfig for a serving cell the carrier indicator field value corresponds
to the value indicated by CrossCarrierSchedulingConfig.
For an active DL BWP of a serving cell on which a UE monitors PDCCH candidates in a USS, if the UE is not
configured with a carrier indicator field, the UE monitors the PDCCH candidates without carrier indicator field. For an
active DL BWP of a serving cell on which a UE monitors PDCCH candidates in a USS, if a UE is configured with a
carrier indicator field, the UE monitors the PDCCH candidates with carrier indicator field.
A UE does not expect to monitor PDCCH candidates on an active DL BWP of a secondary cell if the UE is configured
to monitor PDCCH candidates with carrier indicator field corresponding to that secondary cell in another serving cell.
For the active DL BWP of a serving cell on which the UE monitors PDCCH candidates, the UE monitors PDCCH
candidates at least for the same serving cell.
For a search space set associated with CORESET , the CCE indexes for aggregation level corresponding to
ఓ
PDCCH candidate ௦ ௡಴಺ of the search space set in slot ௦ ௙ for an active DL BWP of a serving cell corresponding to
, ,
carrier indicator field value ஼ூ are given by
௦ ௡಴಺ ⋅ େେ୉ ௣
⋅
௣ ௡ഋ + + ஼ூ େେ୉ ௣ ⁄ +
, ,
ೞ೑ ⋅ ௦ሺ௅ሻ
, ,
,
୫ୟ୶
,
where
for any CSS, ௣ ௡ഋ ,

ೞ೑
,
= 0;
for a USS, ௣ ௡ഋ = ௣ ⋅ ௣ ௡ೞഋ೑ିଵ , ௣ ିଵ = ୖ୒୘୍ ≠ 0, ௣ = 39827 for 3 = 0, ௣ = 39829 for
,
ೞ೑ , ,
3 = 1, ௣ = 39839 for 3 = 2, and = 65537;

, ,
= 0, ⋯ , − 1;
େେ୉ ௣ is the number of CCEs, numbered from 0 to େେ୉ ௣ − 1, in CORESET and, if any, per RB set;
, ,
஼ூ is the carrier indicator field value if the UE is configured with a carrier indicator field by
CrossCarrierSchedulingConfig for the serving cell on which PDCCH is monitored; otherwise, including for any CSS,
஼ூ =0 ;
௦ ௡಴಺ = 0, ⋯ , ௦ሺ௅ሻ
, ௡಴಺ − 1, where ௦ ௡಴಺ is the number of PDCCH candidates the UE is configured to monitor for
ሺ௅ሻ
, ,
aggregation level of a search space set for a serving cell corresponding to ஼ூ ;
for any CSS, ௦ ୫ୟ୶

ሺ௅ሻ
,
= ௦ሺ௅ሻ଴ ;
,
ሺ௅ሻ ሺ௅ሻ
for a USS, ௦ ୫ୟ୶ is the maximum of ௦ ௡಴಺ over all configured ஼ூ values for a CCE aggregation level of search
, ,
space set ;
the RNTI value used for ୖ୒୘୍ is the C-RNTI.
A UE does not expect to be provided freqMonitorLocations for a search space set in a serving cell if
intraCellGuardBandsDL-List indicates that no intra-cell guard-bands are configured for the serving cell.
A UE that
- is configured for operation with carrier aggregation, and
ETSI
- indicates support of search space sharing through searchSpaceSharingCA-UL or through

searchSpaceSharingCA-DL, and
- has a PDCCH candidate with CCE aggregation level in CORESET for a first DCI format scheduling PUSCH
transmission or UL grant Type 2 PUSCH release, other than DCI format 0_0, or for a second DCI format
scheduling PDSCH reception or SPS PDSCH release or indicating SCell dormancy or indicating a request for a
Type-3 HARQ-ACK codebook report without scheduling PDSCH, other than DCI format 1_0, having a first size
and associated with serving cell ஼ூ ଶ ,
,
can receive a corresponding PDCCH through a PDCCH candidate with CCE aggregation level in CORESET for a
first DCI format or for a second DCI format, respectively, having a second size and associated with serving cell ஼ூ ଵ if ,
the first size and the second size are same.
A UE expects to monitor PDCCH candidates for up to 4 sizes of DCI formats that include up to 3 sizes of DCI formats
with CRC scrambled by C-RNTI per serving cell. The UE counts a number of sizes for DCI formats per serving cell
based on a number of configured PDCCH candidates in respective search space sets for the corresponding active DL
BWP.
A UE does not expect to detect, in a same PDCCH monitoring occasion, a DCI format with CRC scrambled by a SI-
RNTI, RA-RNTI, MsgB-RNTI, TC-RNTI, P-RNTI, C-RNTI, CS-RNTI, or MCS-RNTI and a DCI format with CRC
scrambled by a SL-RNTI or a SL-CS-RNTI for scheduling respective PDSCH reception and PSSCH transmission on a
same serving cell.
A PDCCH candidate with index ௦ೕ ௡಴಺ for a search space set ௝ using a set of CCEs in a CORESET on the active DL
,
BWP for serving cell ஼ூ is not counted for monitoring if there is a PDCCH candidate with index ௦೔ ௡಴಺ for a search
< <
,
space set ௜ ௝ , or if there is a PDCCH candidate with index ௦ೕ ௡಴಺ and ௦ೕ ௡಴಺ ௦ೕ ௡಴಺ , in the CORESET on the
, , ,
active DL BWP for serving cell ஼ூ using a same set of CCEs, the PDCCH candidates have identical scrambling, and
the corresponding DCI formats for the PDCCH candidates have a same size; otherwise, the PDCCH candidate with
index ௦ೕ ௡಴಺ is counted for monitoring.
,
݉ܽ‫ݔ‬,‫ݐ݋݈ݏ‬,ߤ
Table 10.1-2 provides the maximum number of monitored PDCCH candidates, PDCCH , per slot for a UE in a DL
BWP with SCS configuration for operation with a single serving cell.
࢓ࢇ࢞,࢙࢒࢕࢚,ࣆ
Table 10.1-2: Maximum number ‫۾‬۲۱۱۶ of monitored PDCCH candidates per slot for a DL BWP
∈ , , ,
with SCS configuration ! " # for a single serving cell
࢓ࢇ࢞ ࢙࢒࢕࢚ ࣆ
ࣆ Maximum number of monitored PDCCH candidates per slot and per serving cell ࡹ‫۾‬۲۱۱۶
, ,
0 44
1 36
2 22
3 20
݉ܽ‫ݔ‬,ሺܺ ,ܻሻ,ߤ
Table 10.1-2A provides the maximum number of monitored PDCCH candidates, PDCCH , per span for a UE in a DL
BWP with SCS configuration for operation with a single serving cell.
࢓ࢇ࢞,ሺࢄ,ࢅሻ,ࣆ
Table 10.1-2A: Maximum number ‫۾‬۲۱۱۶ of monitored PDCCH candidates in a span for
∈ ,
combination (X, Y) for a DL BWP with SCS configuration ! for a single serving cell
࢓ࢇ࢞ ሺࢄ ࢅሻ ࣆ
Maximum number ࡹ‫۾‬۲۱۱۶
, , ,
of monitored PDCCH
candidates per span for combination ሺࢄ ࢅሻ and per,
serving cell
ࣆ (2, 2) (4, 3) (7, 3)
0 14 28 44
1 12 24 36
݉ܽ‫ݔ‬,‫ݐ݋݈ݏ‬,ߤ
Table 10.1-3 provides the maximum number of non-overlapped CCEs, $PDCCH , for a DL BWP with SCS
configuration that a UE is expected to monitor corresponding PDCCH candidates per slot for operation with a single
serving cell.
ETSI
CCEs for PDCCH candidates are non-overlapped if they correspond to
- different CORESET indexes, or
- different first symbols for the reception of the respective PDCCH candidates.
࢓ࢇ࢞,࢙࢒࢕࢚,ࣆ
Table 10.1-3: Maximum number %‫۾‬۲۱۱۶ of non-overlapped CCEs per slot for a DL BWP with SCS
configuration ∈ , !, ", # for a single serving cell
࢓ࢇ࢞ ࢙࢒࢕࢚ ࣆ
ࣆ Maximum number of non-overlapped CCEs per slot and per serving cell ࡯‫۾‬۲۱۱۶
, ,
0 56
1 56
2 48
3 32
݉ܽ‫ݔ‬,ሺܺ,ܻሻ,ߤ
Table 10.1-3A provides the maximum number of non-overlapped CCEs, $PDCCH , for a DL BWP with SCS
configuration that a UE is expected to monitor corresponding PDCCH candidates per span for operation with a single
serving cell.
࢓ࢇ࢞ ,ሺࢄ,ࢅሻ,ࣆ
Table 10.1-3A: Maximum number %‫۾‬۲۱۱۶ of non-overlapped CCEs in a span for combination (X, Y)
for a DL BWP with SCS configuration ! for a single serving cell ∈ ,
࢓ࢇ࢞ ሺࢄ ࢅሻ ࣆ
Maximum number ࡯‫۾‬۲۱۱۶
, , ,
of non-overlapped
CCEs per span for combination ሺࢄ ࢅሻ and per ,
serving cell
ߤ (2, 2) (4, 3) (7, 3)
0 18 36 56
1 18 36 56
If a UE
- does not report pdcch-BlindDetectionCA or is not provided BDFactorR, & ='

- reports pdcch-BlindDetectionCA, the UE can be indicated by BDFactorR either & = 1 or & = '
DL,ఓ
+ DL,ఓ
If a UE is configured with cells,0 cells,1 downlink cells for which the UE is not provided
monitoringCapabilityConfig-r16, or is provided monitoringCapabilityConfig-r16 = r15monitoringcapability but not
provided CORESETPoolIndex, with associated PDCCH candidates monitored in the active DL BWPs of the scheduling
DL,ఓ DL,ఓ
+ ∙
cap
≤
cells using SCS configuration where ∑ଷఓୀ଴)cells,0 & cells,1 * cells , the UE is not required to monitor, on the
active DL BWPs of the scheduling cells,
-
total,slot,ఓ
more than PDCCH = max,slot,ఓ
PDCCH PDCCH candidates or more than $PDCCH total,slot,ఓ
$PDCCH non-overlapped = max,slot,ఓ
DL,ఓ
CCEs per slot for each scheduled cell when the scheduling cell is from the cells,0 downlink cells, or
-
total,slot,ఓ
more than PDCCH = ∙ max,slot,ఓ
& PDCCH PDCCH candidates or more than $PDCCH & $PDCCH non- total,slot,ఓ
= ∙ max,slot,ఓ
DL,ఓ
overlapped CCEs per slot for each scheduled cell when the scheduling cell is from the cells,1 downlink cells
max,slot,ఓ max,slot,ఓ
- more than PDCCH PDCCH candidates or more than $PDCCH non-overlapped CCEs per slot for CORESETs
DL,ఓ
with same coresetPoolIndex value for each scheduled cell when the scheduling cell is from the cells,1 downlink
cells
cells
cap
is replaced by cells,r15 , if a UE is configured with downlink cells for which the UE is provided both
cap-r16
monitoringCapabilityConfig-r16 = r15monitoringcapability and monitoringCapabilityConfig-r16 =

r16monitoringcapability.
If a UE
-
DL,ఓ
+ DL,ఓ
is configured with cells,0 cells,1 downlink cells for which the UE is not provided monitoringCapabilityConfig,
or is provided monitoringCapabilityConfig-r16 = r15monitoringcapability but not provided coresetPoolIndex,
ETSI
- with associated PDCCH candidates monitored in the active DL BWPs of the scheduling cell(s) using SCS
DL,ఓ DL,ఓ cap
+ ∙
configuration , where ∑ଷఓୀ଴)cells,0 & cells,1 * cells , and >
- a DL BWP of an activated cell is the active DL BWP of the activated cell, and a DL BWP of a deactivated cell is
the DL BWP with index provided by firstActiveDownlinkBWP-Id for the deactivated cell,
total,slot,ఓ
the UE is not required to monitor more than PDCCH
cap
cells
max,slot,ఓ
PDCCH = ⋅ ⋅
DL,+ ∙
ߤ
cells,0 & DL, ߤ
cells,1∑ + ∙
ଷ DL,݆ DL,݆ total,slot,ఓ
௝ୀ଴ cells,0 & cells,1 PDCCH candidates or more than PDCCH =
⋅
cap
cells
max,slot,ఓ
PDCCH ⋅
DL,+ ∙
ߤ
cells,0 ∑
& DL, ߤ
cells,1
ଷ DL,݆ DL,݆
+ ∙
௝ୀ଴ cells,0 & cells,1 non-overlapped CCEs per slot on the active
DL BWP(s) of scheduling cell(s) from the
DL,ఓ
cells,0 + DL,ఓ
cells,1
downlink cells. cells is replaced by cells,r15 if a UE is
cap cap-r16
configured with downlink cells for which the UE is provided both monitoringCapabilityConfig-r16 =
r15monitoringcapability and monitoringCapabilityConfig-r16 = r16monitoringcapability.
DL,ఓ
For each scheduled cell from the cells,0 downlink cells, the UE is not required to monitor on the active DL BWP with
SCS configuration of the scheduling cell more than )PDCCH
max,slot,ఓ
, PDCCH
total,slot,ఓ
* PDCCH candidates or more than
max,slot,ఓ
)$PDCCH ,
total,slot,ఓ
$PDCCH * non-overlapped CCEs per slot.
DL,ఓ
For each scheduled cell from the cells,1 downlink cells, the UE is not required to monitor on the active DL BWP with
SCS configuration of the scheduling cell
- more than )& PDCCH ∙ max,slot,ఓ

, PDCCH
total,slot,ఓ
* PDCCH candidates or more than )& ∙ $PDCCH
max,slot,ఓ
, $PDCCH
total,slot,ఓ
* non-
overlapped CCEs per slot
-
max,slot,ఓ
, total,slot,ఓ
more than )PDCCH PDCCH * PDCCH candidates or more than )$PDCCH
max,slot,ఓ
, $PDCCH
total,slot,ఓ
* non-
overlapped CCEs per slot for CORESETs with same coresetPoolIndex value
ୈ୐,μ
If a UE is configured with ୡୣ୪୪ୱ,୰ଵ଺ downlink cells for which the UE is provided monitoringCapabilityConfig =
r16monitoringcapability and with associated PDCCH candidates monitored in the active DL BWPs of the scheduling
cells using SCS configuration , and with ܰୡୣ୪୪ୱ ୰ଵ଺ of the downlink cells using combination X, Y for
ୈ୐,(ଡ଼,ଢ଼),ஜ ୈ୐,μ
, ୡୣ୪୪ୱ,୰ଵ଺
PDCCH monitoring, where ∑
ୈ୐,ஜ cap-r16
ଵ
ஜୀ଴ ୡୣ୪୪ୱ ,୰ଵ଺ ≤ cells
, the UE is not required to monitor, on the active DL BWP of the
scheduling cell, more than
total,(X,Y),ఓ
PDCCH = max,(X,Y),ఓ
PDCCH
total,(X,Y),ఓ
PDCCH candidates or more than PDCCH max,(X,Y),ఓ
= PDCCH
non-overlapped CCEs per span for each scheduled cell when the scheduling cell is from the ܰ
ୈ୐,(ଡ଼,ଢ଼),ஜ
downlink cells. ୡୣ୪୪ୱ,୰ଵ଺
If a UE is configured with downlink cells for which the UE is provided both monitoringCapabilityConfig =
cap-r16 cap-r16
r15monitoringcapability and monitoringCapabilityConfig = r16monitoringcapability, cells is replaced by cells,r16 .
ୈ୐,μ
If a UE is configured only with ୡୣ୪୪ୱ,୰ଵ଺ downlink cells for which the UE is provided monitoringCapabilityConfig =
r16monitoringcapability and with associated PDCCH candidates monitored in the active DL BWPs of the scheduling
cells using SCS configuration , and with ܰୡୣ୪୪ୱ ୰ଵ଺ of the ୡୣ୪୪ୱ,୰ଵ଺ downlink cells using combination X, Y for
ୈ୐ ଡ଼ ଢ଼ ஜ ୈ୐, ,( , ), μ
PDCCH monitoring, where ∑ଵஜୀ଴ ୡୣ୪୪ୱ,୰ଵ଺ > cells , a DL BWP of an activated cell is the active DL BWP of the
ୈ୐,ஜ cap-r16
activated cell, and a DL BWP of a deactivated cell is the DL BWP with index provided by firstActiveDownlinkBWP-Id
total,(X,Y),ఓ
for the deactivated cell, the UE is not required to monitor more than PDCCH
cap-r16
cells
max,(X,Y),ఓ
PDCCH = ⋅ ⋅
DL,(X,Y),μ
cells,r16
∑
ଵ DL,j

௝ୀ଴ cells,r16 PDCCH candidates or more than PDCCH
total,(X,Y),ఓ cap-r16
cells PDCCH
max,(X,Y),ఓ
= ⋅ ⋅
DL,(X,Y),μ
cells,r16
∑ଵ௝ୀ଴ DL,j
cells,r16 non-overlapped CCEs
- per set of spans on the active DL BWP(s) of all scheduling cell(s) from the ୡୣ୪୪ୱ,୰ଵ଺ downlink cells within
every X symbols, if the union of PDCCH monitoring occasions on all scheduling cells from the ୡୣ୪୪ୱ,୰ଵ଺
downlink cells results to PDCCH monitoring according to the combination X, Y and any pair of spans in the set
is within symbols, where first X symbols start at a first symbol with a PDCCH monitoring occasion and next X
symbols start at a first symbol with a PDCCH monitoring occasion that is not included in the first X symbols
- per set of spans across the active DL BWP(s) of all scheduling cells from the ୡୣ୪୪ୱ ,୰ଵ଺ downlink cells, with at
most one span per scheduling cell for each set of spans, otherwise
ETSI
ୈ୐,୨
where ୡୣ୪୪ୱ,୰ଵ଺ is a number of configured cells with associated PDCCH candidates monitored in the active DL BWPs
of the scheduling cells using SCS configuration . If a UE is configured with downlink cells for which the UE is
provided both monitoringCapabilityConfig = r15monitoringcapability and monitoringCapabilityConfig =
cap-r16 cap-r16
r16monitoringcapability, cells is replaced by cells,r16 .
downlink cells using combination X, Y, the UE is not required to monitor
For each scheduled cell from the ୡୣ୪୪ୱ ,୰ଵ଺
on the active DL BWP with SCS configuration of the scheduling cell, more than
୔ୈେେୌ , ୔ୈେେୌ
୫ୟ୶,(ଡ଼,ଢ଼),ఓ ୲୭୲ୟ୪,(ଡ଼,ଢ଼),ఓ
PDCCH candidates or more than

୔ୈେେୌ , ୔ୈେେୌ non-overlapped CCEs per span.
୫ୟ୶,(ଡ଼,ଢ଼),ఓ ୲୭୲ୟ୪,(ଡ଼,ଢ଼),ఓ
A UE does not expect to be configured CSS sets that result to corresponding total, or per scheduled cell, numbers of
monitored PDCCH candidates and non-overlapped CCEs per slot or per span that exceed the corresponding maximum
numbers per slot or per span, respectively.
For same cell scheduling or for cross-carrier scheduling, a UE does not expect a number of PDCCH candidates, and a
number of corresponding non-overlapped CCEs per slot or per span on a secondary cell to be larger than the
corresponding numbers that the UE is capable of monitoring on the secondary cell per slot or per span, respectively. If a
UE is provided monitoringCapabilityConfig = r16monitoringcapability for the primary cell, except the first span of
each slot, the UE does not expect a number of PDCCH candidates and a number of corresponding non-overlapped
CCEs per span on the primary cell to be larger than the corresponding numbers that the UE is capable of monitoring on
the primary cell per span.
For cross-carrier scheduling, the number of PDCCH candidates for monitoring and the number of non-overlapped CCEs
per span or per slot are separately counted for each scheduled cell.
For all search space sets within a slot

or within a span in slot
, denote by Scss a set of CSS sets with cardinality of
I css and by Suss a set of USS sets with cardinality of Juss . The location of USS sets s j , 0 ≤ j < J uss , in Suss is according
to an ascending order of the search space set index.
Denote by M S(Lcss)(i) , 0 ≤ i < I css , the number of counted PDCCH candidates for monitoring for CSS set S css (i ) and by
MS(L) ( j) , 0 ≤ j < J uss , the number of counted PDCCH candidates for monitoring for USS set Suss ( j ) .
uss
I css −1
 M
CSS
CSS
For the CSS sets, a UE monitors M PDCCH = (L)
S css ( i )
PDCCH candidates requiring a total of CPDCCH non-
i =0 L
overlapping CCEs in a slot or in a span.
The UE allocates PDCCH candidates for monitoring to USS sets for the primary cell having an active DL BWP with
SCS configuration in a slot if the UE is not provided monitoringCapabilityConfig for the primary cell or if the UE is
provided monitoringCapabilityConfig = r15monitoringcapability for the primary cell, or in the first span of each slot if
the UE is provided monitoringCapabilityConfig = r16monitoringcapability for the primary cell, according to the
following pseudocode. If for the USS sets for scheduling on the primary cell the UE is not provided coresetPoolIndex
for first CORESETs, or is provided coresetPoolIndex with value 0 for first CORESETs, and is provided
coresetPoolIndex with value 1 for second CORESETs, and if
∙ PDCCH , PDCCH >
max,slot,ఓ total,slot,ఓ

PDCCH , PDCCH or
∙ PDCCH , PDCCH >
PDCCH , PDCCH , the following pseudocode
max,slot,ఓ total,slot,ఓ max,slot,ఓ total,slot,ఓ max,slot,ఓ total,slot,ఓ
applies only to USS sets associated with the first CORESETs. A UE does not expect to monitor PDCCH in a USS set
without allocated PDCCH candidates for monitoring. In the following pseudocode, if the UE is provided
monitoringCapabilityConfig = r16monitoringcapability for the primary cell, PDCCH and PDCCH
max,slot,μ max,slot,μ
are replaced by
PDCCH and
max,(X,Y),μ max,(X,Y),μ
PDCCH respectively, and
total,slot,μ
PDCCH and
total,slot,μ
PDCCH are replaced by
total,(X,Y),μ
PDCCH and PDCCH
total,(X,Y),μ
respectively.
Denote by VCCE (Suss ( j)) the set of non-overlapping CCEs for search space set Suss ( j ) and by C VCCE(Suss( j)) the ( )
cardinality of VCCE (Suss ( j)) where the non-overlapping CCEs for search space set Suss ( j ) are determined considering
the allocated PDCCH candidates for monitoring for the CSS sets and the allocated PDCCH candidates for monitoring
for all search space sets Suss (k ) , 0 ≤ k ≤ j .
uss
( max,slot,μ total,slot,μ
Set MPDCCH = min MPDCCH , MPDCCH − MPDCCH ) css
ETSI
(
Set CPDCCH = min CPDCCH , CPDCCH
uss max,slot,μ total,slot,μ
)− Ccss
PDCCH
Set j = 0
while M ( L)
S uss ( j ) ≤ M PDCCH
uss
(
AND C VCCE(Suss( j)) ≤ CPDCCH
uss
)
L
allocate L M S( L) ( j )
uss
PDCCH candidates for monitoring to USS set Suss( j)
uss
MPDCCH = MPDCCH
uss
− MS( L) ( j ) ; uss
L
uss
CPDCCH = CPDCCH
uss
− C VCCE (Suss ( j)) ; ( )
j = j +1 ;
end while
If a UE
- is configured for single cell operation or for operation with carrier aggregation in a same frequency band, and
- monitors PDCCH candidates in overlapping PDCCH monitoring occasions in multiple CORESETs that have
been configured with same or different qcl-Type set to 'typeD' properties on active DL BWP(s) of one or more
cells
the UE monitors PDCCHs only in a CORESET, and in any other CORESET from the multiple CORESETs that have
been configured with qcl-Type set to same 'typeD' properties as the CORESET, on the active DL BWP of a cell from
the one or more cells
- the CORESET corresponds to the CSS set with the lowest index in the cell with the lowest index containing
CSS, if any; otherwise, to the USS set with the lowest index in the cell with lowest index
- the lowest USS set index is determined over all USS sets with at least one PDCCH candidate in overlapping
PDCCH monitoring occasions
- for the purpose of determining the CORESET, a SS/PBCH block is considered to have different QCL 'typeD'
properties than a CSI-RS
- for the purpose of determining the CORESET, a first CSI-RS associated with a SS/PBCH block in a first cell and
a second CSI-RS in a second cell that is also associated with the SS/PBCH block are assumed to have same QCL
'typeD' properties
- the allocation of non-overlapping CCEs and of PDCCH candidates for PDCCH monitoring is according to all
search space sets associated with the multiple CORESETs on the active DL BWP(s) of the one or more cells
- the number of active TCI states is determined from the multiple CORESETs
If a UE
- is configured for single cell operation or for operation with carrier aggregation in a same frequency band, and
- monitors PDCCH candidates in overlapping PDCCH monitoring occasions in multiple CORESETs where none
of the CORESETs has TCI-states configured with qcl-Type set to 'typeD',
the UE is required to monitor PDCCH candidates in overlapping PDCCH monitoring occasions for search space sets
associated with different CORESETs.
ETSI
For a scheduled cell and at any time, a UE expects to have received at most 16 PDCCHs for DCI formats with CRC
scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI scheduling 16 PDSCH receptions for which the UE has not
received any corresponding PDSCH symbol and at most 16 PDCCHs for DCI formats with CRC scrambled by C-
RNTI, CS-RNTI, or MCS-C-RNTI scheduling 16 PUSCH transmissions for which the UE has not transmitted any
corresponding PUSCH symbol.
If a UE is not provided monitoringCapabilityConfig = r16monitoringcapability for any serving cell, and
- is not configured for NR-DC operation and indicates through pdcch-BlindDetectionCA a capability to monitor
ୡୟ୮
PDCCH candidates for ୡୣ୪୪ୱ ≥ 4 downlink cells and the UE is configured with ୡୣ୪୪ୱ
ୈ୐
> 4 downlink cells or
ୡୣ୪୪ୱ > 4 uplink cells, or
୙୐
ୈ୐ ୙୐
- is configured with NR-DC operation and for a cell group with ୡୣ୪୪ୱ downlink cells or ୡୣ୪୪ୱ uplink cells
ୡୟ୮
the UE expects to have respectively received at most 16 ∙ ୡୣ୪୪ୱ PDCCHs for
ୡୟ୮
- DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI scheduling 16 ∙ ୡୣ୪୪ୱ
ୈ୐
PDSCH receptions for which the UE has not received any corresponding PDSCH symbol over all ୡୣ୪୪ୱ
downlink cells
ୡୟ୮
- DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI scheduling 16 ∙ ୡୣ୪୪ୱ
୙୐
PUSCH transmissions for which the UE has not transmitted any corresponding PUSCH symbol over all ୡୣ୪୪ୱ
uplink cells
If a UE is provided monitoringCapabilityConfig = r16monitoringcapability for all serving cells, and
- is not configured for NR-DC operation and indicates through pdcch-MonitoringCA a capability to monitor
௖௔௣ି௥ଵ଺ ୈ୐
PDCCH candidates for ௖௘௟௟௦ ≥ 2 downlink cells and the UE is configured with ୡୣ୪୪ୱ > 2 downlink cells or
୙୐
ୡୣ୪୪ୱ > 2 uplink cells, or
ୈ୐ ୙୐
௖௔௣ି௥ଵ଺
the UE expects to have respectively received at most 16 ∙ ௖௘௟௟௦ PDCCHs for
௖௔௣ି௥ଵ଺
- DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI scheduling 16 ∙ ௖௘௟௟௦
ୈ୐
PDSCH receptions for which the UE has not received any corresponding PDSCH symbol over all ୡୣ୪୪ୱ
downlink cells
௖௔௣ି௥ଵ଺
- DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI scheduling 16 ∙ ௖௘௟௟௦
୙୐
PUSCH transmissions for which the UE has not transmitted any corresponding PUSCH symbol over all ୡୣ୪୪ୱ
uplink cells.
If a UE is provided monitoringCapabilityConfig = r16monitoringcapability for at least one serving cell and is not
provided monitoringCapabilityConfig = r16monitoringcapability for at least one serving cell, and
௖௔௣ି௥ଵ଺
- is not configured for NR-DC operation, and indicates a capability to monitor PDCCH candidates for ௖௘௟௟௦ ௥ଵହ ≥ ,
௖௔௣ି௥ଵ଺ ୈ୐
1 downlink cells and ௖௘௟௟௦ , ௥ଵ଺ ≥ 1 downlink cells, and the UE is configured with ୡୣ୪୪ୱ > 1 downlink cell or
୙୐
ୡୣ୪୪ୱ > 1 uplink cell, or
ୈ୐ ୙୐
the UE expects to have respectively received

௖௔௣ି௥ଵ଺
- at most 16 ∙ ௖௘௟௟௦ ௥ଵହ PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-
,
௖௔௣ି௥ଵ଺
C-RNTI scheduling 16 ∙ ௖௘௟௟௦ ௥ଵହ PDSCH receptions for which the UE has not received any corresponding
,
PDSCH symbol over all serving cells that are not provided monitoringCapabilityConfig =
r16monitoringcapability
௖௔௣ି௥ଵ଺
- at most 16 ∙ ௖௘௟௟௦ ௥ଵହ PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-
,
௖௔௣ି௥ଵ଺
C-RNTI scheduling 16 ∙ ௖௘௟௟௦ ௥ଵହ PUSCH transmissions for which the UE has not transmitted any
,
ETSI
corresponding PUSCH symbol over all serving cells that are not provided monitoringCapabilityConfig =
௖௔௣ି௥ଵ଺
- at most 16 ∙ ௖௘௟௟௦ ௥ଵ଺ PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-
,
௖௔௣ି௥ଵ଺
C-RNTI scheduling 16 ∙ ௖௘௟௟௦ ௥ଵ଺ PDSCH receptions for which the UE has not received any corresponding
,
PDSCH symbol over all serving cells that are provided monitoringCapabilityConfig = r16monitoringcapability
௖௔௣ି௥ଵ଺
- at most 16 ∙ ௖௘௟௟௦ ௥ଵ଺ PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-
,
௖௔௣ି௥ଵ଺
C-RNTI scheduling 16 ∙ ௖௘௟௟௦ ௥ଵ଺ PUSCH transmissions for which the UE has not transmitted any
,
corresponding PUSCH symbol over all serving cells that are provided monitoringCapabilityConfig =
If a UE
- is configured to monitor a first PDCCH candidate for a DCI format 0_0 and a DCI format 1_0 from a CSS set
and a second PDCCH candidate for a DCI format 0_0 and a DCI format 1_0 from a USS set in a CORESET
with index zero on an active DL BWP, and
- the DCI formats 0_0/1_0 associated with the first PDCCH candidate and the DCI formats 0_0/1_0 associated
with the second PDCCH candidate have same size, and
- the UE receives the first PDCCH candidate and the second PDCCH candidate over a same set of CCEs, and
- the first PDCCH candidate and the second PDCCH candidate have identical scrambling, and
- the DCI formats 0_0/1_0 for the first PDCCH candidate and the DCI formats 0_0/1_0 for the second PDCCH
candidate have CRC scrambled by either C-RNTI, or MCS-C-RNTI, or CS-RNTI
the UE decodes only the DCI formats 0_0/1_0 associated with the first PDCCH candidate.
If a UE detects a DCI format with inconsistent information, the UE discards all the information in the DCI format.
A UE configured with a bandwidth part indicator in a DCI format determines, in case of an active DL BWP or of an
active UL BWP change, that the information in the DCI format is applicable to the new active DL BWP or UL BWP,
respectively, as described in clause 12.
For unpaired spectrum operation, if a UE is not configured for PUSCH/PUCCH transmission on serving cell ଶ , the UE
does not expect to monitor PDCCH on serving cell ଵ if the PDCCH overlaps in time with SRS transmission (including
any interruption due to uplink or downlink RF retuning time [10, TS 38.133]) on serving cell ଶ and if the UE is not
capable of simultaneous reception and transmission on serving cell ଵ and serving cell ଶ .
If a UE is provided resourceBlocks and symbolsInResourceBlock in RateMatchPattern, or if the UE is additionally

provided periodicityAndPattern in RateMatchPattern, the UE can determine a set of RBs in symbols of a slot that are
not available for PDSCH reception as described in [6, TS 38.214]. If a PDCCH candidate in a slot is mapped to one or
more REs that overlap with REs of any RB in the set of RBs in symbols of the slot, the UE does not expect to monitor
the PDCCH candidate.
A UE does not expect to be configured with dci-FormatsSL and dci-FormatsExt in a same USS.
10.2 PDCCH validation for DL SPS and UL grant Type 2

A UE validates, for scheduling activation or scheduling release, a DL SPS assignment PDCCH or a configured UL
grant Type 2 PDCCH if
- the CRC of a corresponding DCI format is scrambled with a CS-RNTI provided by cs-RNTI, and
- the new data indicator field in the DCI format for the enabled transport block is set to '0', and
- the DFI flag field, if present, in the DCI format is set to '0', and
- if validation is for scheduling activation and if the PDSCH-to-HARQ_feedback timing indicator field in the DCI
format is present, the PDSCH-to-HARQ_feedback timing indicator field does not provide an inapplicable value
from dl-DataToUL-ACK-r16.
ETSI
If a UE is provided a single configuration for UL grant Type 2 PUSCH or for SPS PDSCH, validation of the DCI
format is achieved if all fields for the DCI format are set according to Table 10.2-1 or Table 10.2-2.
If a UE is provided more than one configurations for UL grant Type 2 PUSCH or for SPS PDSCH, a value of the
HARQ process number field in a DCI format indicates an activation for a corresponding UL grant Type 2 PUSCH or
for a SPS PDSCH configuration with a same value as provided by ConfiguredGrantConfigIndex or by sps-ConfigIndex,
respectively. Validation of the DCI format is achieved if the RV field for the DCI format is set as in Table 10.2-3.
If a UE is provided more than one configuration for UL grant Type 2 PUSCH or for SPS PDSCH
- if the UE is provided ConfiguredGrantConfigType2DeactivationStateList or sps-ConfigDeactivationStateList, a

value of the HARQ process number field in a DCI format indicates a corresponding entry for scheduling release
of one or more UL grant Type 2 PUSCH or SPS PDSCH configurations
- if the UE is not provided ConfiguredGrantConfigType2DeactivationStateList or sps-

ConfigDeactivationStateList, a value of the HARQ process number field in a DCI format indicates a release for a
corresponding UL grant Type 2 PUSCH or for a SPS PDSCH configuration with a same value as provided by
ConfiguredGrantConfigIndex or by sps-ConfigIndex, respectively
Validation of the DCI format is achieved if all fields for the DCI format are set according to Table 10.2-4.
If validation is achieved, the UE considers the information in the DCI format as a valid activation or valid release of DL
SPS or configured UL grant Type 2. If validation is not achieved, the UE discards all the information in the DCI format.
Table 10.2-1: Special fields for single DL SPS or single UL grant Type 2 scheduling activation PDCCH
validation when a UE is provided a single SPS PDSCH or UL grant Type 2 configuration in the active
DL/UL BWP of the scheduled cell
DCI format 0_0/0_1/0_2 DCI format 1_0/1_2 DCI format 1_1
HARQ process number set to all '0's set to all '0's set to all '0's
For the enabled transport block:
Redundancy version set to all '0's set to all '0's
set to all '0's
Table 10.2-2: Special fields for single DL SPS or single UL grant Type 2 scheduling release PDCCH
validation when a UE is provided a single SPS PDSCH or UL grant Type 2 configuration in the active
DL/UL BWP of the scheduled cell
DCI format 0_0/0_1/0_2 DCI format 1_0/1_1/1_2
HARQ process number set to all '0's set to all '0's
Modulation and coding scheme set to all '1's set to all '1's
set to all '0's for FDRA set to all '0's for FDRA
Type 2 with ߤ = 1 Type 0 or for
Frequency domain resource dynamicSwitch
assignment
set to all '1's for FDRA
set to all '1's, otherwise Type 1
Table 10.2-3: Special fields for a single DL SPS or single UL grant Type 2 scheduling activation
PDCCH validation when a UE is provided multiple DL SPS or UL grant Type 2 configurations in the
active DL/UL BWP of the scheduled cell
DCI format 0_0/0_1/0_2 DCI format 1_0/1_2 DCI format 1_1
For the enabled transport block:
set to all '0's
ETSI
Table 10.2-4: Special fields for a single or multiple DL SPS and UL grant Type 2 scheduling release
PDCCH validation when a UE is provided multiple DL SPS or UL grant Type 2 configurations in the
active DL/UL BWP of the scheduled cell
DCI format 0_0/0_1/0_2 DCI format 1_0/1_1/1_2
Modulation and coding scheme set to all '1's set to all '1's
set to all '0's for FDRA set to all '0's for FDRA Type 0 or
Type 2 with ߤ = 1 for dynamicSwitch
Frequency domain resource assignment
set to all '1's, otherwise set to all '1's for FDRA Type 1
A UE is expected to provide HARQ-ACK information in response to a SPS PDSCH release after symbols from the
last symbol of a PDCCH providing the SPS PDSCH release. If processingType2Enabled of PDSCH-ServingCellConfig
is set to enable for the serving cell with the PDCCH providing the SPS PDSCH release, = 5 for = 0, = 5.5 for
= 1, and = 11 for = 2, otherwise, = 10 for = 0, = 12 for = 1, = 22 for = 2, and = 25 for
= 3, wherein corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH
providing the SPS PDSCH release and the SCS configuration of a PUCCH carrying the HARQ-ACK information in
response to a SPS PDSCH release.
10.2A PDCCH validation for SL configured grant Type 2

A UE validates, for scheduling activation or scheduling release, a SL configured grant Type 2 PDCCH if
- the CRC of a corresponding DCI format 3_0 is scrambled with a SL-CS-RNTI provided by sl-CS-RNTI, and
- the new data indicator field in the DCI format 3_0 for the enabled transport block is set to '0'
Validation of the DCI format 3_0 is achieved if all fields for the DCI format 3_0 are set according to Table 10.2A-1 or
Table 10.2A-2.
If validation is achieved, the UE considers the information in the DCI format 3_0 as a valid activation or valid release
of SL configured grant Type 2. If validation is not achieved, the UE discards all the information in the DCI format 3_0.
Table 10.2A-1: Special fields for SL configured grant Type 2 scheduling activation PDCCH validation
DCI format 3_0

HARQ process number set to all '0's
Table 10.2A-2: Special fields for SL configured grant Type 2 scheduling release PDCCH validation
DCI format 3_0

HARQ process number set to all '1's
Frequency resource assignment
set to all '1's
(if present)
10.3 PDCCH monitoring indication and dormancy/non-dormancy

behaviour for SCells
A UE configured with DRX mode operation [11, TS 38.321] can be provided the following for detection of a DCI
format 2_6 in a PDCCH reception on the PCell or on the SpCell [12, TS 38.331]
- a PS-RNTI for DCI format 2_6 by ps-RNTI
- a number of search space sets, by dci-Format2-6, to monitor PDCCH for detection of DCI format 2_6 on the
active DL BWP of the PCell or of the SpCell according to a common search space as described in clause 10.1
- a payload size for DCI format 2_6 by size-DCI-2-6
ETSI
- a location in DCI format 2_6 of a Wake-up indication bit by ps-PositionDCI-2-6
- a '0' value for the Wake-up indication bit, when reported to higher layers, indicates to not start the drx-
onDurationTimer for the next long DRX cycle [11, TS 38.321]
- a '1' value for the Wake-up indication bit, when reported to higher layers, indicates to start the drx-
onDurationTimer for the next long DRX cycle [11, TS 38.321]
- a bitmap, when the UE is provided a number of groups of configured SCells by

dormancyGroupOutsideActiveTime, where
- the bitmap location is immediately after the Wake-up indication bit location
- the bitmap size is equal to the number of groups of configured SCells where each bit of the bitmap
corresponds to a group of configured SCells from the number of groups of configured SCells
- a '0' value for a bit of the bitmap indicates an active DL BWP, provided by dormantBWP-Id, for the UE [11,
TS38.321] for each activated SCell in the corresponding group of configured SCells
- a '1' value for a bit of the bitmap indicates
- an active DL BWP, provided by firstOutsideActiveTimeBWP-Id, for the UE for each activated SCell in
the corresponding group of configured SCells, if a current active DL BWP is the dormant DL BWP
- a current active DL BWP, for the UE for each activated SCell in the corresponding group of configured
SCells, if the current active DL BWP is not the dormant DL BWP
- the UE sets the active DL BWP to the indicated active DL BWP
- an offset by ps-Offset indicating a time, where the UE starts monitoring PDCCH for detection of DCI format 2_6
according to the number of search space sets, prior to a slot where the drx-onDurationTimer would start on the
PCell or on the SpCell [11, TS 38.321]
- for each search space set, the PDCCH monitoring occasions are the ones in the first s slots indicated by
duration, or s = 1 slot if duration is not provided, starting from the first slot of the first s slots and ending
prior to the start of drx-onDurationTimer.
On PDCCH monitoring occasions associated with a same long DRX Cycle, a UE does not expect to detect more than
one DCI format 2_6 with different values of the Wake-up indication bit for the UE or with different values of the
bitmap for the UE.
The UE does not monitor PDCCH for detecting DCI format 2_6 during Active Time [11, TS 38.321].
If a UE reports for an active DL BWP a MinTimeGap value that is X slots prior to the beginning of a slot where the UE
would start the drx-onDurationTimer, the UE is not required to monitor PDCCH for detection of DCI format 2_6 during
the X slots, where X corresponds to the MinTimeGap value of the SCS of the active DL BWP in Table 10.3-1.
Table 10.3-1 Minimum time gap value X

Minimum Time Gap X (slots)
SCS (kHz)
Value 1 Value 2
15 1 3
30 1 6
60 1 12
120 2 24
If a UE is provided search space sets to monitor PDCCH for detection of DCI format 2_6 in the active DL BWP of the
PCell or of the SpCell and the UE detects DCI format 2_6, the physical layer of a UE reports the value of the Wake-up
indication bit for the UE to higher layers [11, TS 38.321] for the next long DRX cycle.
PCell or of the SpCell and the UE does not detect DCI format 2_6, the physical layer of the UE does not report a value
of the Wake-up indication bit to higher layers for the next long DRX cycle.
PCell or of the SpCell and the UE
ETSI
- is not required to monitor PDCCH for detection of DCI format 2_6, as described in clauses 10, 11.1, 12, and in
clause 5.7 of [11, TS 38.321] for all corresponding PDCCH monitoring occasions outside Active Time prior to a
next long DRX cycle, or
- does not have any PDCCH monitoring occasions for detection of DCI format 2_6 outside Active Time of a next
long DRX cycle
the physical layer of the UE reports a value of 1 for the Wake-up indication bit to higher layers for the next long DRX
cycle.
If a UE is provided search space sets to monitor PDCCH for detection of DCI format 0_1 and DCI format 1_1 and if
one or both of DCI format 0_1 and DCI format 1_1 include a SCell dormancy indication field,
- the SCell dormancy indication field is a bitmap with size equal to a number of groups of configured SCells,
provided by dormancyGroupWithinActiveTime,
- each bit of the bitmap corresponds to a group of configured SCells from the number of groups of configured
Scells
- if the UE detects a DCI format 0_1 or a DCI format 1_1 that does not include a carrier indicator field, or detects
a DCI format 0_1 or DCI format 1_1 that includes a carrier indicator field with value equal to 0
- a '0' value for a bit of the bitmap indicates an active DL BWP, provided by dormantBWP-Id, for the UE for each
activated SCell in the corresponding group of configured SCells
- an active DL BWP, provided by firstWithinActiveTimeBWP-Id, for the UE for each activated SCell in the
corresponding group of configured SCells, if a current active DL BWP is the dormant DL BWP
- a current active DL BWP, for the UE for each activated SCell in the corresponding group of configured
SCells, if the current active DL BWP is not the dormant DL BWP
If a UE is provided search space sets to monitor PDCCH for detection of DCI format 1_1, and if
- the CRC of DCI format 1_1 is scrambled by a C-RNTI or a MCS-C-RNTI, and if
- a one-shot HARQ-ACK request field is not present or has a '0' value, and if
- the UE detects a DCI format 1_1 on the primary cell that does not include a carrier indicator field, or detects a
DCI format 1_1 on the primary cell that includes a carrier indicator field with value equal to 0, and if
DCI format 1_1 are equal to 0, or
DCI format 1_1 are equal to 1, or
- resourceAllocation = dynamicSwitch and all bits of the frequency domain resource assignment field in DCI
format 1_1 are equal to 0 or 1
the UE considers the DCI format 1_1 as indicating SCell dormancy, not scheduling a PDSCH reception or indicating a
SPS PDSCH release, and for transport block 1 interprets the sequence of fields of
- modulation and coding scheme
- new data indicator
- redundancy version
and of
- HARQ process number
- antenna port(s)
ETSI
- DMRS sequence initialization
as providing a bitmap to each configured SCell, in an ascending order of the SCell index, where
- a '0' value for a bit of the bitmap indicates an active DL BWP, provided by dormantBWP-Id, for the UE for a
corresponding activated SCell
- an active DL BWP, provided by firstWithinActiveTimeBWP-Id, for the UE for a corresponding activated

SCell, if a current active DL BWP is the dormant DL BWP
- a current active DL BWP, for the UE for a corresponding activated SCell, if the current active DL BWP is
not the dormant DL BWP
If an active DL BWP provided by dormantBWP-Id for a UE on an activated SCell is not a default DL BWP for the UE
on the activated SCell, as described in clause 12, the BWP inactivity timer is not used for transitioning from the active
DL BWP provided by dormantBWP-Id to the default DL BWP on the activated SCell.
A UE is expected to provide HARQ-ACK information in response to a detection of a DCI format 1_1 indicating SCell
dormancy after symbols from the last symbol of a PDCCH providing the DCI format 1_1. If
processingType2Enabled of PDSCH-ServingCellConfig is set to enable for the serving cell with the PDCCH providing
the DCI format 1_1, = 7 for = 0, = 7.5 for = 1, and = 15 for = 2; otherwise, = 14 for = 0, =
16 for = 1, = 27 for = 2, and = 31 for = 3, where is the smallest SCS configuration between the SCS
configuration of the PDCCH providing the DCI format 1_1 and the SCS configuration of a PUCCH with the HARQ-
ACK information in response to the detection of the DCI format 1_1.
10.4 Search space set group switching

A UE can be provided a group index for a respective Type3-PDCCH CSS set or USS set by searchSpaceGroupIdList
for PDCCH monitoring on a serving cell. If the UE is not provided searchSpaceGroupIdList for a search space set, the
following procedures are not applicable for PDCCH monitoring according to the search space set.
If a UE is provided cellGroupsForSwitchList, indicating one or more groups of serving cells, the following procedures
apply to all serving cells within each group; otherwise, the following procedures apply only to a serving cell for which
the UE is provided searchSpaceGroupIdList.
When a UE is provided searchSpaceGroupIdList, the UE resets PDCCH monitoring according to search space sets with
group index 0, if provided by searchSpaceGroupIdList.
A UE can be provided by searchSpaceSwitchDelay a number of symbols ௦௪௜௧௖௛ where a minimum value of ௦௪௜௧௖௛ is
provided in Table 10.4-1 for UE processing capability 1 and UE processing capability 2 and SCS configuration . UE
processing capability 1 for SCS configuration applies unless the UE indicates support for UE processing capability 2.
Table 10.4-1: Minimum value of ࢙࢝࢏࢚ࢉࢎ [symbols]
Minimum ‫ ܐ܋ܜܑܟܛ۾‬value for Minimum ‫ ܐ܋ܜܑܟܛ۾‬value for

ࣆ
UE processing capability 1 [symbols] UE processing capability 2 [symbols]
0 25 10
1 25 12
2 25 22
A UE can be provided, by searchSpaceSwitchTimer, a timer value for a serving cell that the UE is provided
searchSpaceGroupIdList or, if provided, for a set of serving cells provided by cellGroupsForSwitchList. The UE
decrements the timer value by one after each slot based on a reference SCS configuration that is the smallest SCS
configuration among all configured DL BWPs in the serving cell, or in the set of serving cells. The UE maintains the
reference SCS configuration during the timer decrement procedure.
If a UE is provided by SearchSpaceSwitchTrigger a location of a search space set group switching flag field for a
serving cell in a DCI format 2_0, as described in clause 11.1.1;
ETSI
- if the UE detects a DCI format 2_0 and a value of the search space set group switching flag field in the DCI
format 2_0 is 0, the UE starts monitoring PDCCH according to search space sets with group index 0, and stops
monitoring PDCCH according to search space sets with group index 1, for the serving cell at a first slot that is at
least ௦௪௜௧௖௛ symbols after the last symbol of the PDCCH with the DCI format 2_0
- if the UE detects a DCI format 2_0 and a value of the search space set group switching flag field in the DCI
format 2_0 is 1, the UE starts monitoring PDCCH according to search space sets with group index 1, and stops
monitoring PDCCH according to search space sets with group index 0, for the serving cell at a first slot that is at
least ௦௪௜௧௖௛ symbols after the last symbol of the PDCCH with the DCI format 2_0, and the UE sets the timer
value to the value provided by searchSpaceSwitchTimer
- if the UE monitors PDCCH for a serving cell according to search space sets with group index 1, the UE starts
monitoring PDCCH for the serving cell according to search space sets with group index 0, and stops monitoring
PDCCH according to search space sets with group index 1, for the serving cell at the beginning of the first slot
that is at least ௦௪௜௧௖௛ symbols after a slot where the timer expires or after a last symbol of a remaining channel
occupancy duration for the serving cell if indicated by DCI format 2_0
If a UE is not provided SearchSpaceSwitchTrigger for a serving cell,
- if the UE detects a DCI format by monitoring PDCCH according to a search space set with group index 0, the
UE starts monitoring PDCCH according to search space sets with group index 1, and stops monitoring PDCCH
according to search space sets with group index 0, for the serving cell at a first slot that is at least ௦௪௜௧௖௛
symbols after the last symbol of the PDCCH with the DCI format, the UE sets the timer value to the value
provided by searchSpaceSwitchTimer if the UE detects a DCI format by monitoring PDCCH in any search space
set
- if the UE monitors PDCCH for a serving cell according to search space sets with group index 1, the UE starts
monitoring PDCCH for the serving cell according to search space sets with group index 0, and stops monitoring
PDCCH according to search space sets with group index 1, for the serving cell at the beginning of the first slot
that is at least ௦௪௜௧௖௛ symbols after a slot where the timer expires or, if the UE is provided a search space set to
monitor PDCCH for detecting a DCI format 2_0, after a last symbol of a remaining channel occupancy duration
for the serving cell if indicated by DCI format 2_0
A UE determines a slot and a symbol in the slot to start or stop PDCCH monitoring according to search space sets for a
serving cell that the UE is provided searchSpaceGroupIdList or, if cellGroupsForSwitchList is provided, for a set of
serving cells, based on the smallest SCS configuration among all configured DL BWPs in the serving cell or in the set
of serving cells and, if any, in the serving cell where the UE receives a PDCCH and detects a corresponding DCI format
2_0 triggering the start or stop of PDCCH monitoring according to search space sets.
10.5 HARQ-ACK information for PUSCH transmissions

A UE can be configured a number of search space sets to monitor PDCCH for detecting a DCI format 0_1 with a DFI
flag field and CRC scrambled with a CS-RNTI provided by cs-RNTI. The UE determines that the DCI format provides
HARQ-ACK information for PUSCH transmissions based on when a DFI flag field value is set to '1', if a PUSCH
transmission is configured by ConfiguredGrantConfig.
The HARQ-ACK information corresponds to transport blocks in PUSCH transmissions for all HARQ processes for a
serving cell of a PDCCH reception that provides DCI format 0_1 or, if DCI format 0_1 includes a carrier indicator field,
for a serving cell indicated by a value of the carrier indicator field.
For a PUSCH transmission configured by ConfiguredGrantConfig, HARQ-ACK information for a transport block of a
corresponding HARQ process number is valid if a first symbol of the PDCCH reception is after a last symbol of the
PUSCH transmission, or of any repetition of the PUSCH transmission, by a number of symbols provided by cg-
minDFI-Delay.
For an initial transmission by a UE of a transport block in a PUSCH configured by ConfiguredGrantConfig, if the UE

receives a CG-DFI that provides HARQ-ACK information for the transport block, the UE assumes that the transport
block was correctly decoded if the HARQ-ACK information value is ACK; otherwise, the UE assumes that the
transport block was not correctly decoded.
For a PUSCH transmission scheduled by a DCI format, if the UE receives a CG-DFI that provides HARQ-ACK
information for the transport block, the UE assumes that the transport block was correctly decoded if the HARQ-ACK
information value is ACK; otherwise, the UE assumes that the transport block was not correctly decoded.
ETSI
For a PUSCH transmission scheduled by a DCI format, HARQ-ACK information for a transport block of a
corresponding HARQ process number is valid if a first symbol of the PDCCH reception is after a last symbol of the
PUSCH transmission by a number of symbols provided by cg-minDFI-Delay or, if the PUSCH transmission is over
multiple slots,
- after a last symbol of the PUSCH transmission in a first slot from the multiple slots by a number of symbols
provided by cg-minDFI-Delay, if a value of the HARQ-ACK information is ACK.
- after a last symbol of the PUSCH transmission in a last slot from the multiple slots by a number of symbols
provided by cg-minDFI-Delay, if a value of the HARQ-ACK information is NACK.
UE does not expect to be configured with different cg-minDFI-Delay-r16 among multiple ConfiguredGrantConfig in
one BWP.
11 UE-group common signalling

respectively.
11.1 Slot configuration

A slot format includes downlink symbols, uplink symbols, and flexible symbols.
The following are applicable for each serving cell.
If a UE is provided tdd-UL-DL-ConfigurationCommon, the UE sets the slot format per slot over a number of slots as
indicated by tdd-UL-DL-ConfigurationCommon.
The tdd-UL-DL-ConfigurationCommon provides
- a reference SCS configuration μ ref by referenceSubcarrierSpacing
- a pattern1.
The pattern1 provides
- a slot configuration period of P msec by dl-UL-TransmissionPeriodicity
- a number of slots d slots with only downlink symbols by nrofDownlinkSlots
- a number of downlink symbols d sym by nrofDownlinkSymbols
- a number of slots uslots with only uplink symbols by nrofUplinkSlots
- a number of uplink symbols usym by nrofUplinkSymbols
A value P = 0.625 msec is valid only for μref = 3 . A value P = 1.25 msec is valid only for μref = 2 or μref = 3 . A value
P = 2.5 msec is valid only for μref = 1 , or μref = 2 , or μref = 3 .
A slot configuration period of P msec includes S = P ⋅ 2μref slots with SCS configuration μ ref . From the S slots, a
first dslots slots include only downlink symbols and a last uslots slots include only uplink symbols. The dsym symbols
ETSI
after the first dslots slots are downlink symbols. The usym symbols before the last uslots slots are uplink symbols. The
remaining (S − dslots − uslots ) ⋅ Nsymb − dsym − usym are flexible symbols.
slot
The first symbol every 20 P periods is a first symbol in an even frame.
If tdd-UL-DL-ConfigurationCommon provides both pattern1 and pattern2, the UE sets the slot format per slot over a
first number of slots as indicated by pattern1 and the UE sets the slot format per slot over a second number of slots as
indicated by pattern2.
The pattern2 provides
- a slot configuration period of P2 msec by dl-UL-TransmissionPeriodicity
- a number of slots dslots,2 with only downlink symbols by nrofDownlinkSlots
- a number of downlink symbols dsym,2 by nrofDownlinkSymbols
- a number of slots uslots,2 with only uplink symbols by nrofUplinkSlots
- a number of uplink symbols usym,2 by nrofUplinkSymbols
The applicable values of P2 are same as the applicable values for P .
A slot configuration period of P + P2 msec includes first S = P ⋅ 2 μ ref

slots and second S 2 = P2 ⋅ 2 μ ref
slots.
From the S2 slots, a first dslots,2 slots include only downlink symbols and a last uslots,2 include only uplink symbols.
The dsym,2 symbols after the first dslots,2 slots are downlink symbols. The usym,2 symbols before the last uslots,2 slots are
( )
uplink symbols. The remaining S2 − dslots,2 − uslots,2 ⋅ Nsymb − dsym,2 − usym,2 are flexible symbols.
slot
A UE expects that P + P2 divides 20 msec.
The first symbol every 20 (P + P2 ) periods is a first symbol in an even frame.
A UE expects that the reference SCS configuration μ ref is smaller than or equal to a SCS configuration μ for any
configured DL BWP or UL BWP. Each slot provided by pattern1 or pattern2 is applicable to 2(μ−μref ) consecutive slots
in the active DL BWP or the active UL BWP where the first slot starts at a same time as a first slot for the reference
SCS configuration μ ref and each downlink or flexible or uplink symbol for the reference SCS configuration μ ref
corresponds to 2(μ−μref ) consecutive downlink or flexible or uplink symbols for the SCS configuration μ .
If the UE is additionally provided tdd-UL-DL-ConfigurationDedicated, the parameter tdd-UL-DL-

ConfigurationDedicated overrides only flexible symbols per slot over the number of slots as provided by tdd-UL-DL-
ConfigurationCommon.
The tdd-UL-DL-ConfigurationDedicated provides
- a set of slot configurations by slotSpecificConfigurationsToAddModList
- for each slot configuration from the set of slot configurations
- a slot index for a slot provided by slotIndex
- a set of symbols for a slot by symbols where
- if symbols = allDownlink, all symbols in the slot are downlink
- if symbols = allUplink, all symbols in the slot are uplink
ETSI
- if symbols = explicit, nrofDownlinkSymbols provides a number of downlink first symbols in the slot and
nrofUplinkSymbols provides a number of uplink last symbols in the slot. If nrofDownlinkSymbols is not
provided, there are no downlink first symbols in the slot and if nrofUplinkSymbols is not provided, there are
no uplink last symbols in the slot. The remaining symbols in the slot are flexible
For each slot having a corresponding index provided by slotIndex, the UE applies a format provided by a corresponding
symbols. The UE does not expect tdd-UL-DL-ConfigurationDedicated to indicate as uplink or as downlink a symbol
that tdd-UL-DL-ConfigurationCommon indicates as a downlink or as an uplink symbol, respectively.
For each slot configuration provided by tdd-UL-DL-ConfigurationDedicated, a reference SCS configuration is the
reference SCS configuration μref provided by tdd-UL-DL-ConfigurationCommon.
A slot configuration period and a number of downlink symbols, uplink symbols, and flexible symbols in each slot of the
slot configuration period are determined from tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-
ConfigurationDedicated and are common to each configured BWP.
A UE considers symbols in a slot indicated as downlink by tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-

ConfigurationDedicated to be available for receptions and considers symbols in a slot indicated as uplink by tdd-UL-
DL-ConfigurationCommon, or by tdd-UL-DL-ConfigurationDedicated to be available for transmissions.
If a UE is not configured to monitor PDCCH for DCI format 2_0, for a set of symbols of a slot that are indicated as
flexible by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated if provided, or when tdd-UL-
DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided to the UE
- the UE receives PDSCH or CSI-RS in the set of symbols of the slot if the UE receives a corresponding
indication by a DCI format
- the UE transmits PUSCH, PUCCH, PRACH, or SRS in the set of symbols of the slot if the UE receives a
corresponding indication by a DCI format, a RAR UL grant, fallbackRAR UL grant, or successRAR
For operation on a single carrier in unpaired spectrum, if a UE is configured by higher layers to receive a PDCCH, or a
PDSCH, or a CSI-RS, or a DL PRS in a set of symbols of a slot, the UE receives the PDCCH, the PDSCH, the CSI-RS,
or the DL PRS if the UE does not detect a DCI format that indicates to the UE to transmit a PUSCH, a PUCCH, a
PRACH, or a SRS in at least one symbol of the set of symbols of the slot; otherwise, the UE does not receive the
PDCCH, or the PDSCH, or the CSI-RS, or the DL PRS in the set of symbols of the slot.
For operation with shared spectrum channel access, if a UE is provided csi-RS-ValidationWith-DCI, is not provided
CO-DurationsPerCell, and is not provided SlotFormatCombinationsPerCell, and if the UE is configured by higher
layers to receive a CSI-RS in a set of symbols of a slot, the UE cancels the CSI-RS reception in the set of symbols of
the slot if the UE does not detect a DCI format indicating an aperiodic CSI-RS reception or scheduling a PDSCH
reception in the set of symbols of the slot.
If a UE is provided channelAccessMode ='dynamic' and is provided availableRB-SetsToAddModList and availableRB-

SetsToRelease, the UE expects to be provided co-DurationsPerCellToAddModList and co-
DurationsPerCellToReleaseList and/or slotFormatCombToAddModList and slotFormatCombToReleaseList.
For operation on a single carrier in unpaired spectrum, if a UE is configured by higher layers to transmit SRS, or
PUCCH, or PUSCH, or PRACH in a set of symbols of a slot and the UE detects a DCI format indicating to the UE to
receive CSI-RS or PDSCH in a subset of symbols from the set of symbols, then
- If the UE does not indicate the capability of [partialCancellation], the UE does not expect to cancel the
transmission of the PUCCH or PUSCH or PRACH in the set of symbols if the first symbol in the set occurs
within ௣௥௢௖ ଶ relative to a last symbol of a CORESET where the UE detects the DCI format; otherwise, the UE
,
cancels the PUCCH, or the PUSCH, or an actual repetition of the PUSCH [6, TS38.214], determined from
clauses 9 and 9.2.5 or clause 6.1 of [6, TS38.214], or the PRACH transmission in the set of symbols.
- If the UE indicates the capability of [partialCancellation], the UE does not expect to cancel the transmission of
the PUCCH or PUSCH or PRACH in symbols from the set of symbols that occur within ௣௥௢௖ ଶ relative to a last
,
symbol of a CORESET where the UE detects the DCI format. The UE cancels the PUCCH, or the PUSCH, or an
actual repetition of the PUSCH [6, TS 38.214], determined from clauses 9 and 9.2.5 or clause 6.1 of [6, TS
38.214], or the PRACH transmission in remaining symbols from the set of symbols.
ETSI
- The UE does not expect to cancel the transmission of SRS in symbols from the subset of symbols that occur
within ௣௥௢௖ ଶ relative to a last symbol of a CORESET where the UE detects the DCI format. The UE cancels the
,
SRS transmission in remaining symbols from the subset of symbols.
୮୰୭ୡ ଶ is the PUSCH preparation time for the corresponding UE processing capability [6, TS 38.214] assuming
,
ଶ ଵ = 1 and corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH
carrying the DCI format and the SCS configuration of the SRS, PUCCH, PUSCH or ௥ , where ௥ corresponds to
,
the SCS configuration of the PRACH if it is 15kHz or higher; otherwise ௥ = 0.
For a set of symbols of a slot that are indicated to a UE as uplink by tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-
ConfigurationDedicated, the UE does not receive PDCCH, PDSCH, or CSI-RS when the PDCCH, PDSCH, or CSI-RS
overlaps, even partially, with the set of symbols of the slot.
For a set of symbols of a slot that are indicated to a UE as uplink by tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-
ConfigurationDedicated, the UE does not receive DL PRS in the set of symbols of the slot, if the UE is not provided
with a measurement gap.
For a set of symbols of a slot that are indicated to a UE as downlink by tdd-UL-DL-ConfigurationCommon, or tdd-UL-
DL-ConfigurationDedicated, the UE does not transmit PUSCH, PUCCH, PRACH, or SRS when the PUSCH, PUCCH,
PRACH, or SRS overlaps, even partially, with the set of symbols of the slot.
For a set of symbols of a slot that are indicated to a UE as flexible by tdd-UL-DL-ConfigurationCommon, and tdd-UL-
DL-ConfigurationDedicated if provided, the UE does not expect to receive both dedicated higher layer parameters
configuring transmission from the UE in the set of symbols of the slot and dedicated higher layer parameters
configuring reception by the UE in the set of symbols of the slot.
For operation on a single carrier in unpaired spectrum, for a set of symbols of a slot indicated to a UE by ssb-
PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon, for reception of SS/PBCH blocks, the
UE does not transmit PUSCH, PUCCH, PRACH in the slot if a transmission would overlap with any symbol from the
set of symbols and the UE does not transmit SRS in the set of symbols of the slot. The UE does not expect the set of
symbols of the slot to be indicated as uplink by tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-
ConfigurationDedicated, when provided to the UE.
If a UE
- is configured with multiple serving cells and is provided with directionalCollisionHandling-r16 = 'enabled' for a
set of serving cell(s) among the multiple serving cells, and
- indicates support of half-DuplexTDD-CA-SameSCS-r16 capability, and
- is not configured to monitor PDCCH for detection of DCI format 2_0 on any of the multiple serving cells,
for a set of symbols of a slot that are indicated to the UE for reception of SS/PBCH blocks in a first cell of the multiple
serving cells by ssb-PositionsInBurst in SystemInformationBlockType1 or by ssb-PositionsInBurst in
ServingCellConfigCommon, when provided to the UE, the UE does not transmit PUSCH, PUCCH, or PRACH in the
slot if a transmission would overlap with any symbol from the set of symbols, and the UE does not transmit SRS in the
set of symbols of the slot in
- any of the multiple serving cells if the UE is not capable of simultaneous transmission and reception as indicated
by simultaneousRxTxInterBandCA among the multiple serving cells, and
- any one of the cells corresponding to the same band as the first cell, irrespective of any capability indicated by
simultaneousRxTxInterBandCA.
For a set of symbols of a slot corresponding to a valid PRACH occasion and N gap symbols before the valid PRACH
occasion, as described in clause 8.1, the UE does not receive PDCCH, PDSCH, or CSI-RS in the slot if a reception
would overlap with any symbol from the set of symbols. The UE does not expect the set of symbols of the slot to be
indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.
For a set of symbols of a slot indicated to a UE by pdcch-ConfigSIB1 in MIB for a CORESET for Type0-PDCCH CSS
set, the UE does not expect the set of symbols to be indicated as uplink by tdd-UL-DL-ConfigurationCommon, or tdd-
UL-DL-ConfigurationDedicated.
ETSI
If a UE is scheduled by a DCI format to receive PDSCH over multiple slots, and if tdd-UL-DL-ConfigurationCommon,
or tdd-UL-DL-ConfigurationDedicated, indicate that, for a slot from the multiple slots, at least one symbol from a set of
symbols where the UE is scheduled PDSCH reception in the slot is an uplink symbol, the UE does not receive the
PDSCH in the slot.
If a UE is scheduled by a DCI format to transmit PUSCH over multiple slots, and if tdd-UL-DL-ConfigurationCommon,
or tdd-UL-DL-ConfigurationDedicated, indicates that, for a slot from the multiple slots, at least one symbol from a set
of symbols where the UE is scheduled PUSCH transmission in the slot is a downlink symbol, the UE does not transmit
the PUSCH in the slot.
If a UE
- is configured with multiple serving cells and is provided with directionalCollisionHandling-r16 = 'enabled' for a
set of serving cell(s) among the configured multiple serving cells, and
- indicates support of half-DuplexTDD-CA-SameSCS-r16 capability, and
- is not configured to monitor PDCCH for detection of DCI format 2_0 on any of the multiple serving cells,
the UE determines a reference cell for a symbol as an active cell with the smallest cell index among
- the configured multiple serving cells if the UE is not capable of simultaneous transmission and reception as
indicated by simultaneousRxTxInterBandCA among the multiple serving cells, and
- the cells of each band respectively if the UE is capable of simultaneous transmission and reception by
simultaneousRxTxInterBandCA for the configured multiple serving cells,
where the symbol is configured as
- downlink, or uplink, as indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated
- uplink, if the symbol is flexible and the UE is configured to transmit SRS, PUCCH, PUSCH, or PRACH on the
symbol
- downlink, if the symbol is flexible and the UE is configured to receive PDCCH, PDSCH or CSI-RS on the
symbol.
And if another cell among the cells configured with directionalCollisionHandling-r16 operates in the same frequency
band as the reference cell, the UE does not expect
- a symbol to be indicated as downlink or uplink on the reference cell and as uplink or downlink on another cell,
respectively, by tdd-UL-DL-ConfigurationCommon or by tdd-UL-DL-ConfigurationDedicated,
- tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigDedicated to indicate a symbol as downlink on the

reference cell and to detect a DCI format scheduling a transmission on the symbol on another cell, and
- to be configured by higher layers to receive PDCCH, PDSCH, or CSI-RS on a flexible symbol on the reference
cell and to detect a DCI format scheduling a transmission on the symbol on another cell,
if the reference cell and another cell among the cells configured with directionalCollisionHandling-r16 operate in
different frequency bands,
the UE
- assumes symbol as flexible, is not required to receive higher layer configured PDCCH, PDSCH, or CSI-RS and
not expected to transmit higher layer configured SRS, PUCCH, PUSCH, or PRACH, when tdd-UL-DL-
ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated indicates symbol as downlink or uplink on
another cell and as uplink or downlink for the reference cell, respectively,
- transmits a signal/channel scheduled by a DCI format on a symbol of another cell when the symbol is indicated
as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigDedicated for the reference cell,
- is not required to receive a higher layer configured PDCCH, PDSCH, or CSI-RS on flexible symbols on the
reference cell in a set of symbols, if the UE detects a DCI format scheduling a transmission on one or more
symbols in the set of symbols on another cell,
ETSI
and regardless of whether the reference cell and another cell operate in same or different frequency bands,
the UE
- does not expect tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for the reference cell

to indicate a symbol as uplink and to detect a DCI format scheduling a reception on the symbol on another cell
- does not expect to be configured by higher layers to transmit SRS, PUCCH, PUSCH, or PRACH on a flexible
symbol on the reference cell and to detect a DCI format scheduling a reception on the symbol on another cell
- does not transmit a PUCCH, PUSCH or PRACH that is configured by higher layers on a set of symbols on
another cell if at least one symbol from the set of symbols is indicated as downlink by tdd-UL-DL-
ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or is a symbol corresponding to a PDCCH,
PDSCH, or CSI-RS reception that is configured by higher layers on the reference cell
- does not transmit a SRS that is configured by higher layers on a set of symbols on another cell if the set of
symbols is indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated
or corresponds to a PDCCH, PDSCH or CSI-RS reception that is configured by higher layers on the reference
cell
- does not receive a PDCCH, PDSCH or CSI-RS that is configured by higher layers on a set of symbols on another
cell if at least one symbol from the set of symbols is indicated as uplink by tdd-UL-DL-ConfigurationCommon
or tdd-UL-DL-ConfigurationDedicated or is a symbol corresponding to a SRS, PUCCH, PUSCH, or PRACH
transmission that is configured by higher layers on the reference cell
- assumes a symbol indicated as downlink or uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-

ConfigurationDedicated on another cell to be flexible, if the UE is respectively configured by higher layers to
transmit SRS, PUCCH, PUSCH, or PRACH or to receive PDCCH, PDSCH, or CSI-RS on the reference cell
- does not expect to detect a first DCI format scheduling a transmission or reception on a symbol on a first cell and
a second DCI format scheduling a reception or transmission on the symbol on a second cell, respectively.
After the UE applies the procedures described above for directional collision handling within the set of cells that have
been configured with directionalCollisionHandling-r16, the UE does not expect any directional collision among the
serving cells that the UE is not capable of simultaneous transmission and reception.
11.1.1 UE procedure for determining slot format

This clause applies for a serving cell that is included in a set of serving cells configured to a UE by
slotFormatCombToAddModList and slotFormatCombToReleaseList, availableRB-SetsToAddModList and availableRB-
SetsToRelease, switchTriggerToAddModList and switchTriggerToReleaseList, or co-DurationsPerCellToAddModList
and co-DurationsPerCellToReleaseList.
If a UE is configured by higher layers with parameter SlotFormatIndicator, the UE is provided an SFI-RNTI by sfi-
RNTI and with a payload size of DCI format 2_0 by dci-PayloadSize.
The UE is also provided in one or more serving cells with a configuration for a search space set s and a corresponding
CORESET for monitoring ௣ ௦౏ూ౅ PDCCH candidates for DCI format 2_0 with a CCE aggregation level of
ୗ୊୍
ሺ௅ ሻ
,
CCEs as described in clause 10.1. The ௣ ௦౏ూ౅ PDCCH candidates are the first ௣ ௦౏ూ౅ PDCCH candidates for CCE
ሺ௅ ሻ ሺ௅ ሻ
aggregation level
ୗ୊୍ for search space set in CORESET .
, ,
For each serving cell in the set of serving cells, the UE can be provided:
- an identity of the serving cell by servingCellId
- a location of a SFI-index field in DCI format 2_0 by positionInDCI
- a set of slot format combinations by slotFormatCombinations, where each slot format combination in the set of
slot format combinations includes
- one or more slot formats indicated by a respective slotFormats for the slot format combination, and
- a mapping for the slot format combination provided by slotFormats to a corresponding SFI-index field value
in DCI format 2_0 provided by slotFormatCombinationId
ETSI
- for unpaired spectrum operation, a reference SCS configuration ୗ୊୍ by subcarrierSpacing and, when a
supplementary UL carrier is configured for the serving cell, a reference SCS configuration ୗ୊୍ ୗ୙୐ by
,
subcarrierSpacing2 for the supplementary UL carrier
- for paired spectrum operation, a reference SCS configuration ୗ୊୍ ୈ୐ for a DL BWP by subcarrierSpacing and a
reference SCS configuration ୗ୊୍ ୙୐ for an UL BWP by subcarrierSpacing2
,
- a location of an available RB set indicator field in DCI format 2_0 that is
- one bit, if intraCellGuardBandsDL-List for the serving cell indicates no intra-cell guard-bands are
configured, where a value of '1' indicates that the serving cell is available for receptions, a value of '0'
indicates that the serving cell is not available for receptions, by availableRB-SetsPerCell, and the serving cell
remains available or unavailable for reception until the end of the remaining channel occupancy duration
- a bitmap having a one-to-one mapping with the RB sets [6, TS 38.214] of the serving cell, if
intraCellGuardBandsDL-List for the serving cell indicates intra-cell guard-bands are configured, where the
bitmap includes ୖ୆ ୱୣ୲ ୈ୐ bits and ୖ୆ ୱୣ୲ ୈ୐ is the number of RB sets in the serving cell, a value of '1'
, , , ,
indicates that an RB set is available for receptions, a value of '0' indicates that an RB set is not available for
receptions, by availableRB-SetsPerCell and a RB set remains available or unavailable for receptions until the
end of the remaining channel occupancy duration
- a location of a channel occupancy duration field in DCI format 2_0, by CO-DurationsPerCell, that indicates a
remaining channel occupancy duration for the serving cell starting from a first symbol of a slot where the UE
detects the DCI format 2_0 by providing a value from co-DurationList. The channel occupancy duration field
includes max⌈log ଶ COdurationListSize ⌉, 1 bits, where COdurationListSize is the number of values provided
by co-DurationList. If CO-DurationsPerCell is not provided, the remaining channel occupancy duration for the
serving cell is a number of slots, starting from the slot where the UE detects the DCI format 2_0, that the SFI-
index field value provides corresponding slot formats
- a reference SCS configuration for co-DurationList, by subcarrierSpacing-r16
- a location of a search space set group switching flag field in DCI format 2_0, by SearchSpaceSwitchTrigger, that
indicates a group from two groups of search space sets for PDCCH monitoring for scheduling for the serving cell
or the set of serving cells, provided by CellGroupsForSwitching, as described in clause 10.4.
If neither CO-DurationPerCell-r16 nor SlotFormatCombinationsPerCell are provided and if ChannelAccessMode-

r16 = 'semistatic' is provided, the procedures in this clause apply with assuming a channel occupancy time defined in
clause 4.3 of [15, TS 37.213] is the remaining channel occupancy duration if a DL transmission burst(s) is detected
within the channel occupancy time.
A SFI-index field value in a DCI format 2_0 indicates to a UE a slot format for each slot in a number of slots for each
DL BWP or each UL BWP starting from a slot where the UE detects the DCI format 2_0. The number of slots is equal
to or larger than a PDCCH monitoring periodicity for DCI format 2_0. The SFI-index field includes
max{ log 2 (maxSFIindex + 1), 1} bits where maxSFIindex is the maximum value of the values provided by
corresponding slotFormatCombinationId. A slot format is identified by a corresponding format index as provided in
Table 11.1.1-1 where 'D' denotes a downlink symbol, 'U' denotes an uplink symbol, and 'F' denotes a flexible symbol.
If a PDCCH monitoring periodicity for DCI format 2_0, provided to a UE for the search space set s by
monitoringSlotPeriodicityAndOffset, is smaller than a duration of a slot format combination the UE obtains at a PDCCH
monitoring occasion for DCI format 2_0 by a corresponding SFI-index field value, and the UE detects more than one
DCI formats 2_0 indicating a slot format for a slot, the UE expects each of the more than one DCI formats 2_0 to
indicate a same format for the slot.
A UE does not expect to be configured to monitor PDCCH for DCI format 2_0 on a second serving cell that uses larger
SCS than the serving cell.
ETSI
Table 11.1.1-1: Slot formats for normal cyclic prefix

Format Symbol number in a slot
0 1 2 3 4 5 6 7 8 9 10 11 12 13
0 D D D D D D D D D D D D D D
1 U U U U U U U U U U U U U U
2 F F F F F F F F F F F F F F
3 D D D D D D D D D D D D D F
4 D D D D D D D D D D D D F F
5 D D D D D D D D D D D F F F
6 D D D D D D D D D D F F F F
7 D D D D D D D D D F F F F F
8 F F F F F F F F F F F F F U
9 F F F F F F F F F F F F U U
10 F U U U U U U U U U U U U U
11 F F U U U U U U U U U U U U
12 F F F U U U U U U U U U U U
13 F F F F U U U U U U U U U U
14 F F F F F U U U U U U U U U
15 F F F F F F U U U U U U U U
16 D F F F F F F F F F F F F F
17 D D F F F F F F F F F F F F
18 D D D F F F F F F F F F F F
19 D F F F F F F F F F F F F U
20 D D F F F F F F F F F F F U
21 D D D F F F F F F F F F F U
22 D F F F F F F F F F F F U U
23 D D F F F F F F F F F F U U
24 D D D F F F F F F F F F U U
25 D F F F F F F F F F F U U U
26 D D F F F F F F F F F U U U
27 D D D F F F F F F F F U U U
28 D D D D D D D D D D D D F U
29 D D D D D D D D D D D F F U
30 D D D D D D D D D D F F F U
31 D D D D D D D D D D D F U U
32 D D D D D D D D D D F F U U
33 D D D D D D D D D F F F U U
34 D F U U U U U U U U U U U U
35 D D F U U U U U U U U U U U
36 D D D F U U U U U U U U U U
37 D F F U U U U U U U U U U U
38 D D F F U U U U U U U U U U
39 D D D F F U U U U U U U U U
40 D F F F U U U U U U U U U U
41 D D F F F U U U U U U U U U
42 D D D F F F U U U U U U U U
43 D D D D D D D D D F F F F U
44 D D D D D D F F F F F F U U
45 D D D D D D F F U U U U U U
46 D D D D D F U D D D D D F U
47 D D F U U U U D D F U U U U
48 D F U U U U U D F U U U U U
49 D D D D F F U D D D D F F U
50 D D F F U U U D D F F U U U
51 D F F U U U U D F F U U U U
52 D F F F F F U D F F F F F U
53 D D F F F F U D D F F F F U
54 F F F F F F F D D D D D D D
55 D D F F F U U U D D D D D D
56 – 254 Reserved
UE determines the slot format for the slot based on tdd-UL-DL-ConfigurationCommon, or tdd-UL-
255
DL-ConfigurationDedicated and, if any, on detected DCI formats
ETSI
For unpaired spectrum operation for a UE on a serving cell, the UE is provided by subcarrierSpacing a reference SCS
configuration ୗ୊୍ for each slot format in a combination of slot formats indicated by an SFI-index field value in DCI
format 2_0. The UE expects that for a reference SCS configuration ୗ୊୍ and for an active DL BWP or an active UL
BWP with SCS configuration , it is ≥ ୗ୊୍ . Each slot format in the combination of slot formats indicated by the SFI-
index field value in DCI format 2_0 is applicable to 2ሺఓିఓ౏ూ౅ሻ consecutive slots in the active DL BWP or the active UL
BWP where the first slot starts at a same time as a first slot for the reference SCS configuration ୗ୊୍ and each downlink
( μ − μ SFI )
or flexible or uplink symbol for the reference SCS configuration ୗ୊୍ corresponds to 2 consecutive downlink or
flexible or uplink symbols for the SCS configuration .
For paired spectrum operation for a UE on a serving cell, the SFI-index field in DCI format 2_0 indicates a combination
of slot formats that includes a combination of slot formats for a reference DL BWP and a combination of slot formats
for a reference UL BWP of the serving cell. The UE is provided by subcarrierSpacing a reference SCS configuration
ୗ୊୍ ୈ୐ for the combination of slot formats indicated by the SFI-index field value in DCI format 2_0 for the reference
,
DL BWP of the serving cell. The UE is provided by subcarrierSpacing2 a reference SCS configuration ୗ୊୍ ୙୐ for the ,
combination of slot formats indicated by the SFI-index field value in DCI format 2_0 for the reference UL BWP of the
serving cell. If ୗ୊୍ ୈ୐ ≥ ୗ୊୍ ୙୐ and for each 2൫ఓ౏ూ౅ ీైିఓ౏ూ౅ ౑ై൯ + 1 values provided by a value of slotFormats, where the
, ,
, ,
value of slotFormats is determined by a value of slotFormatCombinationId in slotFormatCombination and the value of

slotFormatCombinationId is set by the value of the SFI-index field value in DCI format 2_0, the first 2൫ఓ౏ూ౅ ీైିఓ౏ూ౅ ౑ై൯ , ,
values for the combination of slot formats are applicable to the reference DL BWP and the next value is applicable to
the reference UL BWP. If ୗ୊୍ ୈ୐ < ୗ୊୍ ୙୐ and for each 2൫ఓ౏ూ౅ ౑ైିఓ౏ూ౅ ీై൯ + 1 values provided by slotFormats, the first
, ,
, ,
value for the combination of slot formats is applicable to the reference DL BWP and the next 2൫ఓ౏ూ౅ ౑ైିఓ౏ూ౅ ీై൯ values
, ,
are applicable to the reference UL BWP.
The UE is provided a reference SCS configuration ୗ୊୍ ୈ୐ so that for an active DL BWP with SCS configuration ୈ୐ , it
,
is ୈ୐ ≥ ୗ୊୍ ୈ୐ . The UE is provided a reference SCS configuration ୗ୊୍ ୙୐ so that for an active UL BWP with SCS
, ,
configuration ୙୐ , it is ୙୐ ≥ ୗ୊୍ ୙୐ . Each slot format for a combination of slot formats indicated by the SFI-index
,
field value in DCI format 2_0 for the reference DL BWP, by indicating a value for slotFormatCombinationId that is
mapped to a value of slotFormats in slotFormatCombination, is applicable to 2൫ఓీైିఓ౏ూ౅ ీై൯ consecutive slots for the
,
active DL BWP where the first slot starts at a same time as a first slot in the reference DL BWP and each downlink or
flexible symbol for the reference SCS configuration ୗ୊୍ ୈ୐ corresponds to 2൫ఓీై ିఓ౏ూ౅ ీై൯ consecutive downlink or
,
,
flexible symbols for the SCS configuration ୈ୐ . Each slot format for the combination of slot formats for the reference
UL BWP is applicable to 2൫ఓ౑ైିఓ౏ూ౅ ౑ై൯ consecutive slots for the active UL BWP where the first slot starts at a same
,
time as a first slot in the reference UL BWP and each uplink or flexible symbol for the reference SCS configuration
ୗ୊୍ ୙୐ corresponds to 2൫ఓ౑ైିఓ౏ూ౅ ౑ై൯ consecutive uplink or flexible symbols for the SCS configuration ୙୐ .
,
,
For unpaired spectrum operation with a second UL carrier for a UE on a serving cell, the SFI-index field value in DCI
format 2_0 indicates a combination of slot formats that includes a combination of slot formats for a reference first UL
carrier of the serving cell and a combination of slot formats for a reference second UL carrier of the serving cell. The
UE is provided by subcarrierSpacing a reference SCS configuration ୗ୊୍ for the combination of slot formats indicated
by the SFI-index field in DCI format 2_0 for the reference first UL carrier of the serving cell. The UE is provided by
subcarrierSpacing2 a reference SCS configuration ୗ୊୍ ୗ୙୐ for the combination of slot formats indicated by the SFI-
,
index field value in DCI format 2_0 for the reference second UL carrier of the serving cell. For each 2൫ఓ౏ూ౅ିఓ౏ూ౅ ౏౑ై൯ + 1 ,
values of slotFormats, the first 2൫ఓ౏ూ౅ିఓ౏ూ౅ ౏౑ై൯ values for the combination of slot formats are applicable to the reference
,
first UL carrier and the next value is applicable to the reference second UL carrier.
The UE expects to be provided a reference SCS configuration ୗ୊୍ ୗ୙୐ so that for an active UL BWP in the second UL
,
carrier with SCS configuration ୗ୙୐ , it is ୗ୙୐ ≥ ୗ୊୍ ୗ୙୐ . Each slot format for a combination of slot formats indicated
,
by the SFI-index field in DCI format 2_0 for the reference first UL carrier is applicable to 2ሺఓିఓ౏ూ౅ሻ consecutive slots
for the active DL BWP and the active UL BWP in the first UL carrier where the first slot starts at a same time as a first
slot in the reference first UL carrier. Each slot format for the combination of slot formats for the reference second UL
carrier is applicable to 2൫ఓ౏౑ైିఓ౏ూ౅ ౏౑ై൯ consecutive slots for the active UL BWP in the second UL carrier where the first
,
slot starts at a same time as a first slot in the reference second UL carrier.
If a BWP in the serving cell is configured with = 2 and with extended CP, the UE expects ୗ୊୍ = 0, ୗ୊୍ = 1, or
ୗ୊୍ = 2. A format for a slot with extended CP is determined from a format for a slot with normal CP. A UE determines
an extended CP symbol to be a downlink/uplink/flexible symbol if the overlapping normal CP symbols that are
downlink/uplink/flexible symbols, respectively. A UE determines an extended CP symbol to be a flexible symbol if one
of the overlapping normal CP symbols is flexible. A UE determines an extended CP symbol to be a flexible symbol if
the pair of the overlapping normal CP symbols includes a downlink and an uplink symbol.
ETSI
A reference SCS configuration ୗ୊୍ , or ୗ୊୍ ୈ୐ , or ୗ୊୍ ୙୐ , or ୗ୊୍ ୗ୙୐ is either 0, or 1, or 2 for FR1 and is either 2 or 3
, , ,
for FR2.
For a set of symbols of a slot, a UE does not expect to detect a DCI format 2_0 with an SFI-index field value indicating
the set of symbols of the slot as uplink and to detect a DCI format indicating to the UE to receive PDSCH or CSI-RS in
the set of symbols of the slot.
For a set of symbols of a slot, a UE does not expect to detect a DCI format 2_0 with an SFI-index field value indicating
the set of symbols in the slot as downlink and to detect a DCI format, a RAR UL grant, fallbackRAR UL grant, or
successRAR indicating to the UE to transmit PUSCH, PUCCH, PRACH, or SRS in the set of symbols of the slot.
For a set of symbols of a slot that are indicated by a DCI format 2_0 as being within a remaining channel occupancy
duration either by a channel occupancy duration field or by an SFI-index field, a UE does not expect to detect at a later
time a DCI format 2_0 indicating, either by a channel occupancy duration field or by an SFI-index field, that any
symbol from the set of symbols is not within a remaining channel occupancy duration.
For a set of symbols of a slot that are indicated as downlink/uplink by tdd-UL-DL-ConfigurationCommon, or tdd-UL-
DL-ConfigurationDedicated, the UE does not expect to detect a DCI format 2_0 with an SFI-index field value
indicating the set of symbols of the slot as uplink/downlink, respectively, or as flexible.
For a set of symbols of a slot corresponding to SS/PBCH blocks with candidate SS/PBCH block indices corresponding
to the SS/PBCH block indexes indicated to a UE by ssb-PositionsInBurst in SIB1, or by ssb-PositionsInBurst in
ServingCellConfigCommon, as described in clause 4.1, the UE does not expect to detect a DCI format 2_0 with an SFI-
index field value indicating the set of symbols of the slot as uplink.
For a set of symbols of a slot corresponding to a valid PRACH occasion and ୥ୟ୮ symbols before the valid PRACH
occasion, as described in clause 8.1, the UE does not expect to detect a DCI format 2_0 with an SFI-index field value
indicating the set of symbols of the slot as downlink.
For a set of symbols of a slot indicated to a UE by pdcch-ConfigSIB1 in MIB for a CORESET for Type0-PDCCH CSS
set, the UE does not expect to detect a DCI format 2_0 with an SFI-index field value indicating the set of symbols of the
slot as uplink.
For a set of symbols of a slot indicated to a UE as flexible by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-

ConfigurationDedicated if provided, or when tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-
ConfigurationDedicated are not provided to the UE, and if the UE detects a DCI format 2_0 providing a format for the
slot using a slot format value other than 255
- if one or more symbols from the set of symbols are symbols in a CORESET configured to the UE for PDCCH
monitoring, the UE receives PDCCH in the CORESET only if an SFI-index field value in DCI format 2_0
indicates that the one or more symbols are downlink symbols
- if an SFI-index field value in DCI format 2_0 indicates the set of symbols of the slot as flexible and the UE
detects a DCI format indicating to the UE to receive PDSCH or CSI-RS in the set of symbols of the slot, the UE
receives PDSCH or CSI-RS in the set of symbols of the slot
- if an SFI-index field value in DCI format 2_0 indicates the set of symbols of the slot as flexible and the UE
detects a DCI format, a RAR UL grant, fallbackRAR UL grant, or successRAR indicating to the UE to transmit
PUSCH, PUCCH, PRACH, or SRS in the set of symbols of the slot the UE transmits the PUSCH, PUCCH,
PRACH, or SRS in the set of symbols of the slot
- if an SFI-index field value in DCI format 2_0 indicates the set of symbols of the slot as flexible, and the UE does
not detect a DCI format indicating to the UE to receive PDSCH or CSI-RS, or the UE does not detect a DCI
format, a RAR UL, fallbackRAR UL grant, or successRAR grant indicating to the UE to transmit PUSCH,
PUCCH, PRACH, or SRS in the set of symbols of the slot, the UE does not transmit or receive in the set of
symbols of the slot
- if the UE is configured by higher layers to receive PDSCH or CSI-RS in the set of symbols of the slot, the UE
receives the PDSCH or the CSI-RS in the set of symbols of the slot only if an SFI-index field value in DCI
format 2_0 indicates the set of symbols of the slot as downlink and, if applicable, the set of symbols is within
remaining channel occupancy duration
ETSI
- if the UE is configured by higher layers to receive DL PRS in the set of symbols of the slot, the UE receives the
DL PRS in the set of symbols of the slot only if an SFI-index field value in DCI format 2_0 indicates the set of
symbols of the slot as downlink or flexible.
- if the UE is configured by higher layers to transmit PUCCH, or PUSCH, or PRACH in the set of symbols of the
slot, the UE transmits the PUCCH, or the PUSCH, or the PRACH in the slot only if an SFI-index field value in
DCI format 2_0 indicates the set of symbols of the slot as uplink
- if the UE is configured by higher layers to transmit SRS in the set of symbols of the slot, the UE transmits the
SRS only in a subset of symbols from the set of symbols of the slot indicated as uplink symbols by an SFI-index
field value in DCI format 2_0
- a UE does not expect to detect an SFI-index field value in DCI format 2_0 indicating the set of symbols of the
slot as downlink and also detect a DCI format, a RAR UL grant, fallbackRAR UL grant, or successRAR
indicating to the UE to transmit SRS, PUSCH, PUCCH, or PRACH, in one or more symbols from the set of
symbols of the slot
slot as downlink or flexible if the set of symbols of the slot includes symbols corresponding to any repetition of a
PUSCH transmission activated by an UL Type 2 grant PDCCH as described in clause 10.2
slot as uplink and also detect a DCI format indicating to the UE to receive PDSCH or CSI-RS in one or more
symbols from the set of symbols of the slot
If a UE is configured by higher layers to receive a CSI-RS or a PDSCH in a set of symbols of a slot and the UE detects
a DCI format 2_0 with a slot format value other than 255 that indicates a slot format with a subset of symbols from the
set of symbols as uplink or flexible, or the UE detects a DCI format indicating to the UE to transmit PUSCH, PUCCH,
SRS, or PRACH in at least one symbol in the set of the symbols, the UE cancels the CSI-RS reception in the set of
symbols of the slot or cancels the PDSCH reception in the slot.
For operation with shared spectrum channel access, if a UE is configured by higher layers to receive a CSI-RS and the
UE is provided CO-DurationsPerCell, for a set of symbols of a slot that are indicated as downlink or flexible by tdd-
UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, or when tdd-UL-DL-ConfigurationCommon
and tdd-UL-DL-ConfigurationDedicated are not provided, the UE cancels the CSI-RS reception in the set of symbols of
the slot that are not within the remaining channel occupancy duration.
If a UE is configured by higher layers to receive a DL PRS in a set of symbols of a slot and the UE detects a DCI format
2_0 with a slot format value other than 255 that indicates a slot format with a subset of symbols from the set of symbols
as uplink, or the UE detects a DCI format indicating to the UE to transmit PUSCH, PUCCH, SRS, or PRACH in at least
one symbol in the set of the symbols, the UE cancels the DL PRS reception in the set of symbols of the slot.
If a UE is configured by higher layers to transmit SRS, or PUCCH, or PUSCH, or PRACH in a set of symbols of a slot
and the UE detects a DCI format 2_0 with a slot format value other than 255 that indicates a slot format with a subset of
symbols from the set of symbols as downlink or flexible, or the UE detects a DCI format indicating to the UE to receive
CSI-RS or PDSCH in a subset of symbols from the set of symbols, then
- If the UE does not indicate the capability of [partialCancellation], the UE does not expect to cancel the
transmission of the PUCCH or PUSCH or PRACH in the set of symbols if the first symbol in the set occurs
within ௣௥௢௖ ଶ relative to a last symbol of a CORESET where the UE detects the DCI format; otherwise, the UE
,
cancels the PUCCH, or the PUSCH, or an actual repetition of the PUSCH [6, TS38.214], determined from
clauses 9 and 9.2.5 or clause 6.1 of [6, TS38.214], or the PRACH transmission in the set of symbols.
- If the UE indicates the capability of [partialCancellation], the UE does not expect to cancel the transmission of
the PUCCH or PUSCH or PRACH in symbols from the set of symbols that occur within ௣௥௢௖ ଶ relative to a last
,
symbol of a CORESET where the UE detects the DCI format. The UE cancels the PUCCH, or the PUSCH, or an
actual repetition of the PUSCH [6, TS 38.214], determined from clauses 9 and 9.2.5 or clause 6.1 of [6, TS
38.214], or the PRACH transmission in remaining symbols from the set of symbols.
- The UE does not expect to cancel the transmission of SRS in symbols from the subset of symbols that occur
within ௣௥௢௖ ଶ relative to a last symbol of a CORESET where the UE detects the DCI format. The UE cancels the
,
SRS transmission in remaining symbols from the subset of symbols.
ETSI
୮୰୭ୡ ଶis the PUSCH preparation time for the corresponding UE processing capability [6, TS 38.214] assuming
,
ଶ ଵ =
,
1 and corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH
carrying the DCI format and the SCS configuration of the SRS, PUCCH, PUSCH or ௥ , where ௥ corresponds to
the SCS configuration of the PRACH if it is 15kHz or higher; otherwise ௥ = 0.
If a UE is configured by higher layers to receive a CSI-RS or detects a DCI format 0_1 indicating to the UE to receive a
CSI-RS in one or more RB sets and a set of symbols of a slot, and the UE detects a DCI format 2_0 with bitmap
indicating that any RB set from the one or more RB sets is not available for reception, the UE cancels the CSI-RS
reception in the set of symbols of the slot.
A UE assumes that flexible symbols in a CORESET configured to the UE for PDCCH monitoring are downlink
symbols if the UE does not detect an SFI-index field value in DCI format 2_0 indicating the set of symbols of the slot as
flexible or uplink and the UE does not detect a DCI format indicating to the UE to transmit SRS, PUSCH, PUCCH, or
PRACH in the set of symbols.
For a set of symbols of a slot that are indicated as flexible by tdd-UL-DL-ConfigurationCommon, and tdd-UL-DL-
ConfigurationDedicated if provided, or when tdd-UL-DL-ConfigurationCommon, and tdd-UL-DL-
ConfigurationDedicated are not provided to the UE, and if the UE does not detect a DCI format 2_0 providing a slot
format for the slot
- the UE receives PDSCH or CSI-RS in the set of symbols of the slot if the UE receives a corresponding
indication by a DCI format
- the UE transmits PUSCH, PUCCH, PRACH, or SRS in the set of symbols of the slot if the UE receives a
corresponding indication by a DCI format, a RAR UL grant, fallbackRAR UL grant, or successRAR
- the UE receives PDCCH as described in clause 10.1
- if the UE is configured by higher layers to receive PDSCH in the set of symbols of the slot, the UE does not
receive the PDSCH in the set of symbols of the slot
- if the UE is configured by higher layers to receive CSI-RS in the set of symbols of the slot, the UE does not
receive the CSI-RS in the set of symbols of the slot, except when UE is provided CO-DurationsPerCell and the
set of symbols of the slot are within the remaining channel occupancy duration.
- if the UE is configured by higher layers to receive DL PRS in the set of symbols of the slot, the UE receives the
DL PRS
- if the UE is configured by higher layers to transmit SRS, or PUCCH, or PUSCH, or PRACH in the set of
symbols of the slot and the UE is not provided enableConfiguredUL, then
- if the UE does not indicate the capability of [partialCancellation], the UE does not expect to cancel the
transmission of the PUCCH, or the PUSCH, or an actual repetition of the PUSCH [6, TS 38.214], as
determined in clauses 9 and 9.2.5 or in clause 6.1 of [6. TS 38.214], or the PRACH in the slot if the first
symbol of the PUCCH or the PUSCH or actual repetition of the PUSCH or the PRACH in the slot occurs
within ୮୰୭ୡ ଶ relative to a last symbol of a CORESET where the UE is configured to monitor PDCCH for
,
DCI format 2_0; otherwise, the UE cancels the PUCCH, or the PUSCH, or an actual repetition of the PUSCH
[6, TS 38.214], as determined in clauses 9 and 9.2.5 or in clause 6.1 of [6. TS 38.214], or the PRACH in the
slot;
- if the UE indicates the capability of [partialCancellation], the UE does not expect to cancel the transmission
of the PUCCH, or the PUSCH, or an actual repetition of the PUSCH [6, TS 38.214], as determined in clauses
9 and 9.2.5 or in clause 6.1 of [6. TS 38.214], or the PRACH in symbols from the set of symbols that occur
within ௣௥௢௖ ଶ relative to a last symbol of a CORESET where the UE is configured to monitor PDCCH for
,
DCI format 2_0. The UE cancels the PUCCH, or the PUSCH, or an actual repetition of the PUSCH [6, TS
38.214], as determined in clauses 9 and 9.2.5 or in clause 6.1 of [6. TS 38.214], or the PRACH transmission
in remaining symbols from the set of symbols;
- the UE does not expect to cancel the transmission of SRS in symbols from the set of symbols that occur
within ௣௥௢௖ ଶ relative to a last symbol of a CORESET where the UE is configured to monitor PDCCH for
,
DCI format 2_0. The UE cancels the SRS transmission in remaining symbols from the set of symbols;
- ୮୰୭ୡ ଶ
,
is the PUSCH preparation time for the corresponding UE processing capability [6, TS 38.214]
assuming ଶ ଵ = 1 and corresponds to the smallest SCS configuration between the SCS configuration of
,
ETSI
the PDCCH carrying the DCI format 2_0 and the SCS configuration of the SRS, PUCCH, PUSCH or ௥ ,
where ௥ corresponds to the SCS configuration of the PRACH if it is 15kHz or higher; otherwise ௥ = 0;
- if the UE is configured by higher layers to transmit SRS, or PUCCH, or PUSCH, or PRACH in the set of
symbols of the slot and the UE is provided enableConfiguredUL, the UE can transmit the SRS, or PUCCH, or
PUSCH, or PRACH, respectively.
For unpaired spectrum operation for a UE on a cell in a frequency band of FR1, and when the scheduling restrictions
due to RRM measurements [10, TS 38.133] are not applicable, if the UE detects a DCI format indicating to the UE to
transmit in a set of symbols, the UE is not required to perform RRM measurements [10, TS 38.133] based on a
SS/PBCH block or CSI-RS reception on a different cell in the frequency band if the SS/PBCH block or CSI-RS
reception includes at least one symbol from the set of symbols.
11.2 Interrupted transmission indication

If a UE is provided DownlinkPreemption, the UE is configured with an INT-RNTI provided by int-RNTI for monitoring
PDCCH conveying DCI format 2_1 [5, TS 38.212]. The UE is additionally configured with
- a set of serving cells by int-ConfigurationPerServingCell that includes a set of serving cell indexes provided by
corresponding servingCellId and a corresponding set of locations for fields in DCI format 2_1 by positionInDCI
- an information payload size for DCI format 2_1 by dci-PayloadSize
- an indication granularity for time-frequency resources by timeFrequencySet
If a UE detects a DCI format 2_1 for a serving cell from the configured set of serving cells, the UE may assume that no
transmission to the UE is present in PRBs and in symbols that are indicated by the DCI format 2_1, from a set of PRBs
and a set of symbols of the last monitoring period. The indication by the DCI format 2_1 is not applicable to receptions
of SS/PBCH blocks.
The set of PRBs is equal to the active DL BWP as defined in clause 12 and includes B INT PRBs.
If a UE detects a DCI format 2_1 in a PDCCH transmitted in a CORESET in a slot, the set of symbols is the last
μ − μ INT
slot
N symb ⋅TINT ⋅ 2 symbols prior to the first symbol of the CORESET in the slot where T INT is the PDCCH
monitoring periodicity provided by the value of monitoringSlotPeriodicityAndOffset, as described in clause 10.1,
is the number of symbols per slot, μ is the SCS configuration for a serving cell with mapping to a respective
slot
N symb
field in the DCI format 2_1, μ INT is the SCS configuration of the DL BWP where the UE receives the PDCCH with the
DCI format 2_1. If the UE is provided tdd-UL-DL-ConfigurationCommon, symbols indicated as uplink by tdd-UL-DL-
μ − μ INT
slot
ConfigurationCommon are excluded from the last N symb ⋅TINT ⋅ 2 symbols prior to the first symbol of the
CORESET in the slot. The resulting set of symbols includes a number of symbols that is denoted as N INT .
μ −μ
The UE does not expect to be provided values of μ , μ INT , and T INT resulting to a value of N symb
slot
⋅TINT ⋅ 2 INT
that is
not an integer. The UE does not expect to be configured by monitoringSymbolsWithinSlot with more than one PDCCH
monitoring occasion for DCI format 2_1 in a slot.
A UE is provided the indication granularity for the set of PRBs and for the set of symbols by timeFrequencySet.
If the value of timeFrequencySet is 'set0', 14 bits from MSB of a field in DCI format 2_1 have a one-to-one mapping
with 14 groups of consecutive symbols from the set of symbols where each of the first N INT − N INT 14  ⋅ 14 symbol
groups includes N INT 14  symbols, each of the last 14 − N INT + N INT 14  ⋅ 14 symbol groups includes N INT 14 
symbols, a bit value of 0 indicates transmission to the UE in the corresponding symbol group and a bit value of 1
indicates no transmission to the UE in the corresponding symbol group.
If the value of timeFrequencySet is 'set1', 7 pairs of bits from MSB of a field in the DCI format 2_1 have a one-to-one
mapping with 7 groups of consecutive symbols where each of the first N INT − N INT 7  ⋅ 7 symbol groups includes
N INT 7  symbols, each of the last 7 − N INT + N INT 7  ⋅ 7 symbol groups includes N INT 7  symbols, a first bit in a
pair of bits for a symbol group is applicable to the subset of first B INT 2  PRBs from the set of B INT PRBs, a second
bit in the pair of bits for the symbol group is applicable to the subset of last BINT 2  PRBs from the set of B INT PRBs,
ETSI
a bit value of 0 indicates transmission to the UE in the corresponding symbol group and subset of PRBs, and a bit value
of 1 indicates no transmission to the UE in the corresponding symbol group and subset of PRBs.
11.2A Cancellation indication

If a UE is provided UplinkCancellation, the UE is provided, in one or more serving cells, a search space set for
monitoring the first PDCCH candidate with a CCE aggregation level of ‫ ܫܥ‬CCEs of the search space set for detection
of a DCI format 2_4 [5, TS 38.212] with a CI-RNTI provided by ci-RNTI as described in clause 10.1.
UplinkCancellation additionally provides to the UE
- a set of serving cells, by ci-ConfigurationPerServingCell, that includes a set of serving cell indexes and a
corresponding set of locations for fields in DCI format 2_4 by positionInDCI
- a number of fields in DCI format 2_4, by positionInDCI-forSUL, for each serving cell for a SUL carrier, if the
serving cell is configured with a SUL carrier
- an information payload size for DCI format 2_4 by dci-PayloadSize-ForCI
- an indication for time-frequency resources by timeFrequencyRegion
For a serving cell having an associated field in a DCI format 2_4, for the field denote by
- CI a number of bits provided by ci-PayloadSize
- CI a number of PRBs provided by frequencyRegionforCI in timeFrequencyRegion
- CI a number of symbols, excluding symbols for reception of SS/PBCH blocks and DL symbols indicated by tdd-
UL-DL-ConfigurationCommon, from a number of symbols that
- is provided by timeDurationforCI in timeFrequencyRegion, if the PDCCH monitoring periodicity for the

search space set with the DCI format 2_4 is one slot and there are more than one PDCCH monitoring
occasions in a slot, or
- is equal to the PDCCH monitoring periodicity, otherwise.
-
CI a number of partitions for the CI symbols provided by timeGranularityforCI in timeFrequencyRegion
CI sets of bits from the MSB of the CI bits have a one-to-one mapping with
CI groups of symbols where each of the
first
CI − CI + ⌊CI ⁄
CI ⌋ ⋅
CI groups includes ⌊େ୍ ⁄
CI ⌋ symbols and each of the remaining CI − ⌊CI ⁄
CI ⌋ ⋅
CI
groups includes ⌈CI ⁄
CI ⌉ symbols. A UE determines a symbol duration with respect to a SCS configuration of an active
DL BWP where the UE monitors PDCCH for DCI format 2_4 detection.
For a group of symbols, BI = CI ⁄

‫ ܫܥ‬bits from MSB of each set of bits have a one-to-one mapping with BI groups
of PRBs where each of the first BI − CI + ⌊ CI ⁄BI ⌋ ⋅ BI groups includes ⌊ CI ⁄BI ⌋ PRBs and each of the remaining
CI − ⌊ CI ⁄BI ⌋ ⋅ BI groups includes ⌈ CI ⁄BI ⌉ PRBs. A UE determines a first PRB index as ோிோ
௦௧௔௥௧
= carrier +
௦௧௔௥௧ and a number of contiguous RBs as CI = RB from frequencyRegionforCI that indicates an offset ௦௧௔௥௧ and
a length RB as RIV according to [6, TS 38.214], and from offsetToCarrier in FrequencyInfoUL-SIB or
FrequencyInfoUL that indicates carrier for a SCS configuration of an active DL BWP where the UE monitors PDCCH
for DCI format 2_4 detection.
An indication by a DCI format 2_4 for a serving cell is applicable to a PUSCH transmission or an SRS transmission on
the serving cell. If the PUSCH transmission or the SRS transmission is scheduled by a DCI format, the indication by the
DCI format 2_4 is applicable to the PUSCH transmission or SRS transmission only if the last symbol of the PDCCH
reception providing the DCI format is earlier than the first symbol of the PDCCH reception providing the DCI format
2_4. For the serving cell, the UE determines the first symbol of the େ୍ symbols to be the first symbol that is after
′୮୰୭ୡ,ଶ from the end of a PDCCH reception where the UE detects the DCI format 2_4, where ′୮୰୭ୡ,ଶ is obtained from
୮୰୭ୡ,ଶ for PUSCH processing capability 2 [6, TS 38.214] assuming ଶ,ଵ = ୭୤୤ୱୣ୲ ⋅ 2ିఓೆಽ ⁄2ିఓ where ୭୤୤ୱୣ୲ is
provided by delta_Offset, being the smallest SCS configuration between the SCS configuration of the PDCCH and the
smallest SCS configuration ୙୐ provided in scs-SpecificCarrierList of FrequencyInfoUL or FrequencyInfoUL-SIB. The
UE does not expect to cancel the PUSCH transmission or the SRS transmission before a corresponding symbol that is
୮୰୭ୡ,ଶ assuming that ଶ,ଵ = 0 after a last symbol of a CORESET where the UE detects the DCI format 2_4.
ETSI
A UE that detects a DCI format 2_4 for a serving cell cancels a PUSCH transmission or an actual repetition of a
PUSCH transmission [6, TS 38.214] if the PUSCH transmission is with repetition Type B, as determined in clauses 9
and 9.2.5 or in clause 6.1 of [6, TS 38.214], or an SRS transmission on the serving cell if, respectively,
- the transmission is PUSCH with priority 0, if the UE is provided uplinkCancellationPriority,
- a group of symbols, from the CI symbols, has at least one bit value of '1' in the corresponding set of BI bits in
the DCI format 2_4 and includes a symbol of the (repetition of the) PUSCH transmission or of the SRS
transmission, and
- a group of PRBs, from the CI PRBs, has a corresponding bit value of '1' in the set of bits corresponding to the
group of symbols in the DCI format 2_4 and includes a PRB of the (repetition of the) PUSCH transmission or of
the SRS transmission,
where
- the cancellation of the (repetition of the) PUSCH transmission includes all symbols from the earliest symbol of
the (repetition of the) PUSCH transmission that is in a group of symbols having corresponding bit values of '1' in
the DCI format 2_4;
- the cancellation of the SRS transmission includes only symbols that are in one or more groups of symbols having
corresponding bit values of '1' in the DCI format 2_4.
If, based on an indication by a DCI format 2_4, a UE cancels a PUSCH transmission or an SRS transmission, the UE
does not expect to be scheduled by a second DCI format to transmit a PUSCH or an SRS over symbols that include
symbols of the cancelled PUSCH transmission or SRS transmission, where the last symbol of the PDCCH reception
providing the second DCI format is later than the first symbol of the PDCCH reception providing the DCI format 2_4.
11.3 Group TPC commands for PUCCH/PUSCH

For PUCCH transmission on a serving cell, a UE can be provided
- a TPC-PUCCH-RNTI for a DCI format 2_2 by tpc-PUCCH-RNTI
- a field in DCI format 2_2 is a TPC command of 2 bits mapping to δ P U C C H , b , f , c values as described in
clause 7.2.1
- an index for a location in DCI format 2_2 of a first bit for a TPC command field for the PCell, or for a carrier of
the PCell by tpc-IndexPCell
- an index for a location in DCI format 2_2 of a first bit for a TPC command field for the PUCCH-SCell or for a
carrier for the PUCCH-SCell by tpc-IndexPUCCH-Scell
- a mapping for the PUCCH power control adjustment state l ∈{ 0, 1}, by a corresponding {0, 1} value of a closed
loop index field that is appended to the TPC command field in DCI format 2_2 if the UE indicates a capability to
support two PUCCH power control adjustment states by twoDifferentTPC-Loop-PUCCH, and if the UE is
configured for two PUCCH power control adjustment states by twoPUCCH-PC-AdjustmentStates
The UE is also provided on a serving cell with a configuration for a search space set s and a corresponding CORESET
p for monitoring PDCCH candidates for DCI format 2_2 with CRC scrambled by a TPC-PUCCH-RNTI as described
in clause 10.1.
For PUSCH transmission on a serving cell, a UE can be provided
- a TPC-PUSCH-RNTI for a DCI format 2_2 by tpc-PUSCH-RNTI
- a field in DCI format 2_2 is a TPC command of 2 bits mapping to δ PUSCH, b, f ,c values as described in clause
7.1.1
- an index for a location in DCI format 2_2 of a first bit for a TPC command field for an uplink carrier of the
serving cell by tpc-Index
ETSI
- an index for a location in DCI format 2_2 of a first bit for a TPC command field for a supplementary uplink
carrier of the serving cell by tpc-IndexSUL
- an index of the serving cell by targetCell. If targetCell is not provided, the serving cell is the cell of the PDCCH
reception for DCI format 2_2
- a mapping for the PUSCH power control adjustment state l ∈ { 0, 1} , by a corresponding {0, 1} value of a closed
loop index field that is appended to the TPC command field for the uplink carrier or for the supplementary
uplink carrier of the serving cell in DCI format 2_2 if the UE indicates a capability to support two PUSCH
power control adjustment states, by twoDifferentTPC-Loop-PUSCH, and if the UE is configured for two PUSCH
power control adjustment states by twoPUSCH-PC-AdjustmentStates
The UE is also provided for the serving cell of the PDCCH reception for DCI format 2_2 with a configuration for a
search space set s and a corresponding CORESET p for monitoring PDCCH candidates for DCI format 2_2 with
CRC scrambled by a TPC-PUSCH-RNTI as described in clause 10.1.
11.4 SRS switching

DCI format 2_3 is applicable for uplink carrier(s) of serving cells where a UE is not configured for PUSCH/PUCCH
transmission or for uplink carrier(s) of a serving cell where srs-PowerControlAdjustmentStates indicates a separate
power control adjustment state between SRS transmissions and PUSCH transmissions.
A UE configured by higher layers with parameter carrierSwitching is provided
- a TPC-SRS-RNTI for a DCI format 2_3 by tpc-SRS-RNTI
- an index of a serving cell where the UE interrupts transmission in order to transmit SRS on one or more other
serving cells by srs-SwitchFromServCellIndex
- an indication of an uplink carrier where the UE interrupts transmission in order to transmit SRS on one or more
other serving cells by srs-SwitchFromCarrier
- a DCI format 2_3 field configuration type by typeA or typeB
- for typeA, an index for a set of serving cells is provided by cc-SetIndex, indexes of serving cells in the set of
serving cells are provided by cc-IndexInOneCC-Set, and a DCI format 2_3 field includes a TPC command
for each serving cell from the set of serving cells and can also include a SRS request for SRS transmission on
the set of serving cells
- for typeB, DCI format 2_3 field includes a TPC command for a serving cell index and can also include a SRS
request for SRS transmission on the serving cell
- an indication for a serving cell for whether or not a field in DCI format 2_3 includes a SRS request by
fieldTypeFormat2-3 where a value of 0/1 indicates absence/presence of the SRS request – a mapping for a 2 bit
SRS request to SRS resource sets is as provided in [6, TS 38.214]
- an index for a location in DCI format 2_3 of a first bit for a field for a non-supplementary uplink carrier of the
serving cell by startingBitOfFormat2-3
- an index for a location in DCI format 2_3 of a first bit for a field for a supplementary uplink carrier of the
serving cell by startingBitOfFormat2-3SUL-v1530
12 Bandwidth part operation

respectively.
ETSI
A UE configured for operation in bandwidth parts (BWPs) of a serving cell, is configured by higher layers for the
serving cell a set of at most four bandwidth parts (BWPs) for receptions by the UE (DL BWP set) in a DL bandwidth by
parameter BWP-Downlink or by parameter initialDownlinkBWP with a set of parameters configured by BWP-
DownlinkCommon and BWP-DownlinkDedicated, and a set of at most four BWPs for transmissions by the UE (UL
BWP set) in an UL bandwidth by parameter BWP-Uplink or by parameter initialUplinkBWP with a set of parameters
configured by BWP-UplinkCommon and BWP-UplinkDedicated.
For operation with shared spectrum channel access, a UE expects that the BWP configured by the parameter
initialUplinkBWP provided in UplinkConfigCommonSIB is mapped to only a single RB set.
If a UE is not provided initialDownlinkBWP, an initial DL BWP is defined by a location and number of contiguous
PRBs, starting from a PRB with the lowest index and ending at a PRB with the highest index among PRBs of a
CORESET for Type0-PDCCH CSS set, and a SCS and a cyclic prefix for PDCCH reception in the CORESET for
Type0-PDCCH CSS set; otherwise, the initial DL BWP is provided by initialDownlinkBWP. For operation on the
primary cell or on a secondary cell, a UE is provided an initial UL BWP by initialUplinkBWP. If the UE is configured
with a supplementary UL carrier, the UE can be provided an initial UL BWP on the supplementary UL carrier by
initialUplinkBWP.
If a UE has dedicated BWP configuration, the UE can be provided by firstActiveDownlinkBWP-Id a first active DL
BWP for receptions and by firstActiveUplinkBWP-Id a first active UL BWP for transmissions on a carrier of the
primary cell.
For each DL BWP or UL BWP in a set of DL BWPs or UL BWPs, respectively, the UE is provided the following
parameters for the serving cell as defined in [4, TS 38.211] or [6, TS 38.214]:
- a SCS by subcarrierSpacing
- a cyclic prefix by cyclicPrefix
a common RB NBWP = Ocarrier + RBstart and a number of contiguous RBs N BWP

start
- size
= LRB provided by
locationAndBandwidth that indicates an offset RBstart and a length LRB as RIV according to [6, TS 38.214],
setting NBWP = 275 , and a value Ocarrier provided by offsetToCarrier for the subcarrierSpacing
size
- an index in the set of DL BWPs or UL BWPs by respective BWP-Id
- a set of BWP-common and a set of BWP-dedicated parameters by BWP-DownlinkCommon and BWP-

DownlinkDedicated for the DL BWP, or BWP-UplinkCommon and BWP-UplinkDedicated for the UL BWP [12,
TS 38.331]
For unpaired spectrum operation, a DL BWP from the set of configured DL BWPs with index provided by BWP-Id is
linked with an UL BWP from the set of configured UL BWPs with index provided by BWP-Id when the DL BWP index
and the UL BWP index are same. For unpaired spectrum operation, a UE does not expect to receive a configuration
where the center frequency for a DL BWP is different than the center frequency for an UL BWP when the BWP-Id of
the DL BWP is same as the BWP-Id of the UL BWP.
For each DL BWP in a set of DL BWPs of the PCell, a UE can be configured CORESETs for every type of CSS sets
and for USS as described in clause 10.1. The UE does not expect to be configured without a CSS set on the PCell in the
active DL BWP.
If a UE is provided controlResourceSetZero and searchSpaceZero in PDCCH-ConfigSIB1 or PDCCH-ConfigCommon,

the UE determines a CORESET for a search space set from controlResourcesetZero as described in clause 13 and for
Tables 13-1 through 13-10, and determines corresponding PDCCH monitoring occasions as described in clause 13 and
for Tables 13-11 through 13-15. If the active DL BWP is not the initial DL BWP, the UE determines PDCCH
monitoring occasions for the search space set only if the CORESET bandwidth is within the active DL BWP and the
active DL BWP has same SCS configuration and same cyclic prefix as the initial DL BWP.
For each UL BWP in a set of UL BWPs of the PCell or of the PUCCH-SCell, the UE is configured resource sets for
PUCCH transmissions as described in clause 9.2.1.
ETSI
A UE receives PDCCH and PDSCH in a DL BWP according to a configured SCS and CP length for the DL BWP. A
UE transmits PUCCH and PUSCH in an UL BWP according to a configured SCS and CP length for the UL BWP.
If a bandwidth part indicator field is configured in a DCI format, the bandwidth part indicator field value indicates the
active DL BWP, from the configured DL BWP set, for DL receptions as described in [5, TS 38.212]. If a bandwidth
part indicator field is configured in a DCI format, the bandwidth part indicator field value indicates the active UL BWP,
from the configured UL BWP set, for UL transmissions as described in [5, TS 38.212]. If a bandwidth part indicator
field is configured in a DCI format and indicates an UL BWP or a DL BWP different from the active UL BWP or DL
BWP, respectively, the UE shall
- for each information field in the DCI format
- if the size of the information field is smaller than the one required for the DCI format interpretation for the
UL BWP or DL BWP that is indicated by the bandwidth part indicator, the UE prepends zeros to the
information field until its size is the one required for the interpretation of the information field for the UL
BWP or DL BWP prior to interpreting the DCI format information fields, respectively
- if the size of the information field is larger than the one required for the DCI format interpretation for the UL
BWP or DL BWP that is indicated by the bandwidth part indicator, the UE uses a number of least significant
bits of the DCI format equal to the one required for the UL BWP or DL BWP indicated by bandwidth part
indicator prior to interpreting the DCI format information fields, respectively
- set the active UL BWP or DL BWP to the UL BWP or DL BWP indicated by the bandwidth part indicator in the
DCI format
If a bandwidth part indicator field is configured in a DCI format 0_1 and indicates an active UL BWP with different
SCS configuration ߤ , or with different number BWP RB−set,UL of RB sets, than a current active UL BWP, the UE determines
an uplink frequency domain resource allocation Type 2 based on
′ bits and ′ bits that are generated by independently
truncating or padding the
MSBs and the LSBs [6, TS 38.214] of the frequency domain resource assignment field of
DCI format 0_1, where truncation starts from the MSBs of the X bits or the Y bits, zero-padding prepends zeros to the
X bits or the Y bits, and
- if the indicated active UL BWP has SCS configuration ߤ =1and the current active BWP has SCS
configuration ߤ =0 , the
MSBs are truncated to
′ =
− 1 bits, or
- if the indicated active UL BWP has SCS configuration ߤ = 0 and the current active BWP has SCS
configuration ߤ =1 , the
MSBs are zero-padded to
′ =
+ 1 bits
- otherwise, the
MSBs are unchanged
and
ా౓ౌ ా౓ౌ
- the LSBs are truncated or zero-padded to ′ = logଶ ே౎ాష౩౛౪ ౑ై൫ேଶ౎ాష౩౛౪ ౑ైାଵ൯ bits where BWP
, ,
RB−set,UL is a
number of RB sets configured for the indicated active UL BWP
A UE does not expect to detect a DCI format with a BWP indicator field that indicates an active DL BWP or an active
UL BWP change with the corresponding time domain resource assignment field providing a slot offset value for a
PDSCH reception or PUSCH transmission that is smaller than a delay required by the UE for an active DL BWP
change or UL BWP change, respectively [10, TS 38.133].
If a UE detects a DCI format with a BWP indicator field that indicates an active DL BWP change for a cell, the UE is
not required to receive or transmit in the cell during a time duration from the end of the third symbol of a slot where the
UE receives the PDCCH that includes the DCI format in a scheduling cell until the beginning of a slot indicated by the
slot offset value of the time domain resource assignment field in the DCI format.
If a UE detects a DCI format with SCell dormancy indication that indicates an active DL BWP change for an Scell in
slot n of primary cell, the UE is not required to receive or transmit in the SCell during a time duration specified in [10,
TS 38.133].
If a UE detects a DCI format indicating an active UL BWP change for a cell, the UE is not required to receive or
transmit in the cell during a time duration from the end of the third symbol of a slot where the UE receives the PDCCH
that includes the DCI format in the scheduling cell until the beginning of a slot indicated by the slot offset value of the
time domain resource assignment field in the DCI format.
ETSI
A UE does not expect to detect a DCI format indicating an active DL BWP change or an active UL BWP change for a
scheduled cell within FR1 (or FR2) in a slot other than the first slot of a set of slots for the DL SCS of the scheduling
cell that overlaps with a time duration where the UE is not required to receive or transmit, respectively, for an active
BWP change in a different cell from the scheduled cell within FR1 (or FR2).
A UE expects to detect a DCI format with a BWP indicator field that indicates an active UL BWP change or an active
DL BWP change only if a corresponding PDCCH is received within the first 3 symbols of a slot.
For a serving cell, a UE can be provided by defaultDownlinkBWP-Id a default DL BWP among the configured DL
BWPs. If a UE is not provided a default DL BWP by defaultDownlinkBWP-Id, the default DL BWP is the initial DL
BWP.
If a UE is provided by bwp-InactivityTimer a timer value for the serving cell [11, TS 38.321] and the timer is running,
the UE decrements the timer at the end of a subframe for FR1 or at the end of a half subframe for FR2 if the restarting
conditions in [11, TS 38.321] are not met during the interval of the subframe for FR1 or of the half subframe for FR2.
For a cell where a UE changes an active DL BWP due to a BWP inactivity timer expiration and for accommodating a
delay in the active DL BWP change or the active UL BWP change required by the UE [10, TS 38.133], the UE is not
required to receive or transmit in the cell during a time duration from the beginning of a subframe for FR1, or of half of
a subframe for FR2, that is immediately after the BWP inactivity timer expires until the beginning of a slot where the
UE can receive or transmit.
When a UE's BWP inactivity timer for a cell within FR1 (or FR2) expires within a time duration where the UE is not
required to receive or transmit for an active UL/DL BWP change in the cell or in a different cell within FR1 (or FR2),
the UE delays the active UL/DL BWP change triggered by the BWP inactivity timer expiration until a subframe for
FR1 or half a subframe for FR2 that is immediately after the UE completes the active UL/DL BWP change in the cell or
in the different cell within FR1 (or FR2).
If a UE is provided by firstActiveDownlinkBWP-Id a first active DL BWP and by firstActiveUplinkBWP-Id a first active

UL BWP on a carrier of a secondary cell, the UE uses the indicated DL BWP and the indicated UL BWP as the
respective first active DL BWP on the secondary cell and first active UL BWP on the carrier of the secondary cell.
A UE does not expect to monitor PDCCH when the UE performs RRM measurements [10, TS 38.133] over a
bandwidth that is not within the active DL BWP for the UE.
13 UE procedure for monitoring Type0-PDCCH CSS

sets
If during cell search a UE determines from MIB that a CORESET for Type0-PDCCH CSS set is present, as described in
clause 4.1, the UE determines a number of consecutive resource blocks and a number of consecutive symbols for the
CORESET of the Type0-PDCCH CSS set from controlResourceSetZero in pdcch-ConfigSIB1, as described in Tables
13-1 through 13-10, for operation without shared spectrum channel access, or as described in Tables 13-1A and 13-4A
for operation with shared spectrum channel access, and determines PDCCH monitoring occasions from
searchSpaceZero in pdcch-ConfigSIB1, included in MIB, as described in Tables 13-11 through 13-15. SFNC and nC
are the SFN and slot index within a frame of the CORESET based on SCS of the CORESET and SFNSSB,i and nSSB, i
are the SFN and slot index based on SCS of the CORESET, respectively, where the SS/PBCH block with index i
overlaps in time with system frame SFN SSB, i and slot nSSB, i . The symbols of the CORESET associated with pdcch-
ConfigSIB1 in MIB or with searchSpaceSIB1 in PDCCH-ConfigCommon have normal cyclic prefix.
For operation without shared spectrum channel access, a UE assumes that the offset in Tables 13-1 through 13-10 is
defined with respect to the SCS of the CORESET for Type0-PDCCH CSS set, provided by
subCarrierSpacingCommon, from the smallest RB index of the CORESET for Type0-PDCCH CSS set to the smallest
RB index of the common RB overlapping with the first RB of the corresponding SS/PBCH block. In Tables 13-7, 13-8,
and 13-10 kSSB is defined in [4, TS 38.211].
For operation with shared spectrum channel access, a UE determines an offset from a smallest RB index of the
CORESET for Type0-PDCCH CSS set to a smallest RB index of the common RB overlapping with a first RB of the
corresponding SS/PBCH block
ETSI
- according to the offset in Table 13-1A or Table 13-4A, if the frequency position of the SS/PBCH block
corresponds to the GSCN of a synchronization raster entry as defined in [8-1, TS 38.101-1], and
- according to a sum of a first offset and a second offset if the frequency position of the SS/PBCH block is
provided by ssbFrequency in a measurement configuration associated with a reporting configuration providing
reportCGI and does not correspond to the GSCN of a synchronization raster entry as defined in [8-1, TS 38.101-
1], where
- the first offset is provided in Table 13-1A or Table 13-4A, and
- the second offset is determined as the offset from a smallest RB index of the common RB overlapping with
the first RB of the SS/PBCH block indicated in the measurement configuration to a smallest RB index of the
common RB overlapping with the first RB of a SS/PBCH block hypothetically located at the GSCN of a
synchronization raster entry, where the single synchronization raster entry is located in the same channel as
the SS/PBCH block used for the shared spectrum channel access procedure, as described in [15, TS 37.213]
where the offsets are defined with respect to the SCS of the CORESET for Type0-PDCCH CSS set that is same as the
SCS of the corresponding SS/PBCH block.
For operation without shared spectrum channel access and for the SS/PBCH block and CORESET multiplexing pattern
1, a UE monitors PDCCH in the Type0-PDCCH CSS set over two consecutive slots starting from slot n 0 . For
SS/PBCH block with index i , the UE determines an index of slot n 0 as n0 = (O ⋅ 2μ + i ⋅ M )modNslot
frame,μ
that is in a
( μ
frame with system frame number (SFN) SFNC satisfying SFNC mod 2 = 0 if O ⋅ 2 + i ⋅ M  Nslot ) frame, μ
 mod2 = 0 , or
(
in a frame with SFN satisfying SFNC mod2 = 1 if  O ⋅ 2 + i ⋅ M  N
μ
)  mod 2 = 1 . M and O are provided by
frame , μ
slot
Tables 13-11 and 13-12, and μ ∈ {0,1,2,3} based on the SCS for PDCCH receptions in the CORESET [4, TS 38.211].
The index for the first symbol of the CORESET in slots n 0 and n 0 + 1 is the first symbol index provided by Tables
13-11 and 13-12.
For operation with shared spectrum channel access and for the SS/PBCH block and CORESET multiplexing pattern 1, a
UE monitors PDCCH in the Type0-PDCCH CSS set over slots that include Type0-PDCCH monitoring occasions
associated with SS/PBCH blocks that are quasi co-located with the SS/PBCH block that provides a CORESET for
Type0-PDCCH CSS set with respect to average gain, quasi co-location 'typeA' and 'typeD' properties, when applicable
[6, TS 38.214]. For a candidate SS/PBCH block index ̅, where 0 ≤ ̅ ≤ ௠௔௫ − 1, two consecutive slots starting from
slot ଴ include the associated Type0-PDCCH monitoring occasions. The UE determines an index of slot ଴ as ଴ =
⋅ 2ఓ + ⌊̅ ⋅ ⌋ mod ୱ୪୭୲୤୰ୟ୫ୣ,ஜ
that is in a frame with system frame number (SFN) SFN஼ satisfying SFN஼ 2 = 0
if ⋅ 2 + ⌊̅ ⋅ ⌋/ ୱ୪୭୲ 2 = 0, or in a frame with SFN satisfying SFN஼ 2 = 1 if
ఓ ୤୰ୟ୫ୣ ,ஜ
⋅ 2ఓ + ⌊̅ ⋅ ⌋/ ୱ୪୭୲

୤୰ୟ୫ୣ,ஜ
2 = 1. and are provided by Table 13-11, and ∈ {0, 1} based on the SCS for
PDCCH receptions in the CORESET [4, TS 38.211]. The index for the first symbol of the CORESET in slots ଴ and
଴ + 1 is the first symbol index provided by Table 13-11. The UE does not expect to be configured with = 1/2, or
with = 2, when ௌௌ஻ ொ஼௅
= 1.
For the SS/PBCH block and CORESET multiplexing patterns 2 and 3, a UE monitors PDCCH in the Type0-PDCCH
CSS set over one slot with Type0-PDCCH CSS set periodicity equal to the periodicity of SS/PBCH block. For the
SS/PBCH block and CORESET multiplexing patterns 2 and 3, if the active DL BWP is the initial DL BWP, the UE is
expected to be able to perform radio link monitoring, as described in clause 5, and measurements for radio resource
management [10, TS 38.133] using a SS/PBCH block that provides a CORESET for Type0-PDCCH CSS set. For a
SS/PBCH block with index i , the UE determines the slot index n C and SFNC based on parameters provided by Tables
13-13 through 13-15.
ETSI
Table 13-1: Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set
when {SS/PBCH block, PDCCH} SCS is {15, 15} kHz for frequency bands with minimum channel
bandwidth 5 MHz or 10 MHz
Number of RBs Number of Symbols

SS/PBCH block and CORESET
Index CORESET CORESET Offset (RBs)
multiplexing pattern N RB Nsymb
0 1 24 2 0
1 1 24 2 2
2 1 24 2 4
3 1 24 3 0
4 1 24 3 2
5 1 24 3 4
6 1 48 1 12
7 1 48 1 16
8 1 48 2 12
9 1 48 2 16
10 1 48 3 12
11 1 48 3 16
12 1 96 1 38
13 1 96 2 38
14 1 96 3 38
15 Reserved
Table 13-1A: Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space
set when {SS/PBCH block, PDCCH} SCS is {15, 15} kHz for frequency bands operated with shared
spectrum channel access
SS/PBCH block and CORESET Number of RBs Number of

ࡺCORESET Symbols ࡺCORESET
Index Offset (RBs)
multiplexing pattern RB symb
0 1 96 1 10
1 1 96 1 12
2 1 96 1 14
3 1 96 1 16
4 1 96 2 10
5 1 96 2 12
6 1 96 2 14
7 1 96 2 16
8 Reserved
9 Reserved
10 Reserved
11 Reserved
12 Reserved
13 Reserved
14 Reserved
15 Reserved
ETSI
SS/PBCH block and CORESET Number of RBs Number of Symbols

multiplexing pattern N RB N symb
0 1 24 2 5
1 1 24 2 6
2 1 24 2 7
3 1 24 2 8
4 1 24 3 5
5 1 24 3 6
6 1 24 3 7
7 1 24 3 8
8 1 48 1 18
9 1 48 1 20
10 1 48 2 18
11 1 48 2 20
12 1 48 3 18
13 1 48 3 20
14 Reserved
15 Reserved

0 1 48 1 2
1 1 48 1 6
2 1 48 2 2
3 1 48 2 6
4 1 48 3 2
5 1 48 3 6
6 1 96 1 28
7 1 96 2 28
8 1 96 3 28
9 Reserved
10 Reserved
11 Reserved
12 Reserved
13 Reserved
14 Reserved
15 Reserved
ETSI

0 1 24 2 0
1 1 24 2 1
2 1 24 2 2
3 1 24 2 3
4 1 24 2 4
5 1 24 3 0
6 1 24 3 1
7 1 24 3 2
8 1 24 3 3
9 1 24 3 4
10 1 48 1 12
11 1 48 1 14
12 1 48 1 16
13 1 48 2 12
14 1 48 2 14
15 1 48 2 16
Table 13-4A: Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space
set when {SS/PBCH block, PDCCH} SCS is {30, 30} kHz for frequency bands operated with shared
spectrum channel access

ࡺCORESET Symbols ࡺCORESET
Index Offset (RBs)
multiplexing pattern RB symb
0 1 48 1 0
1 1 48 1 1
2 1 48 1 2
3 1 48 1 3
4 1 48 2 0
5 1 48 2 1
6 1 48 2 2
7 1 48 2 3
8 Reserved
9 Reserved
10 Reserved
11 Reserved
12 Reserved
13 Reserved
14 Reserved
15 Reserved
ETSI
bandwidth 40MHz
Number of RBs Number of Symbols

SS/PBCH block and CORESET
multiplexing pattern N RB Nsymb
0 1 48 1 4
1 1 48 2 4
2 1 48 3 4
3 1 96 1 0
4 1 96 1 56
5 1 96 2 0
6 1 96 2 56
7 1 96 3 0
8 1 96 3 56
9 Reserved
10 Reserved
11 Reserved
12 Reserved
13 Reserved
14 Reserved
15 Reserved
bandwidth 40MHz

0 1 24 2 0
1 1 24 2 4
2 1 24 3 0
3 1 24 3 4
4 1 48 1 0
5 1 48 1 28
6 1 48 2 0
7 1 48 2 28
8 1 48 3 0
9 1 48 3 28
10 Reserved
11 Reserved
12 Reserved
13 Reserved
14 Reserved
15 Reserved
ETSI
when {SS/PBCH block, PDCCH} SCS is {120, 60} kHz

Index CORESET Symbols N symb
CORESET Offset (RBs)
multiplexing pattern N RB
0 1 48 1 0
1 1 48 1 8
2 1 48 2 0
3 1 48 2 8
4 1 48 3 0
5 1 48 3 8
6 1 96 1 28
7 1 96 2 28
-41 if k SSB = 0
8 2 48 1
-42 if k SSB > 0
9 2 48 1 49
-41 if k SSB = 0
10 2 96 1
-42 if kSSB>0
11 2 96 1 97
12 Reserved
13 Reserved
14 Reserved
15 Reserved

0 1 24 2 0
1 1 24 2 4
2 1 48 1 14
3 1 48 2 14
4 3 24 2
-20 if kSSB=0
-21 if k SSB > 0
5 3 24 2 24
-20 if kSSB=0
6 3 48 2
-21 if kSSB>0
7 3 48 2 48
8 Reserved
9 Reserved
10 Reserved
11 Reserved
12 Reserved
13 Reserved
14 Reserved
15 Reserved
ETSI

0 1 96 1 0
1 1 96 1 16
2 1 96 2 0
3 1 96 2 16
4 Reserved
5 Reserved
6 Reserved
7 Reserved
8 Reserved
9 Reserved
10 Reserved
11 Reserved
12 Reserved
13 Reserved
14 Reserved
15 Reserved
Table 13-10: Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space
set when {SS/PBCH block, PDCCH} SCS is {240, 120} kHz

0 1 48 1 0
1 1 48 1 8
2 1 48 2 0
3 1 48 2 8
-41 if k SSB = 0
4 2 24 1
-42 if kSSB>0
5 2 24 1 25
6 2 48 1
-41 if kSSB=0
-42 if k SSB > 0
7 2 48 1 49
8 Reserved
9 Reserved
10 Reserved
11 Reserved
12 Reserved
13 Reserved
14 Reserved
15 Reserved
ETSI
Table 13-11: Parameters for PDCCH monitoring occasions for Type0-PDCCH CSS set - SS/PBCH
block and CORESET multiplexing pattern 1 and FR1
Number of search space sets per
Index O slot M First symbol index
0 0 1 1 0
1 0 2 1/2 {0, if i is even}, { N symb
CORESET
, if i is odd}
2 2 1 1 0
3 2 2 1/2 {0, if i is even}, { N symb
CORESET
, if i is odd}
4 5 1 1 0
5 5 2 1/2 {0, if i is even}, { N symb
CORESET
, if i is odd}
6 7 1 1 0
7 7 2 1/2 {0, if i is even}, { N symb
CORESET
, if i is odd}
8 0 1 2 0
9 5 1 2 0
10 0 1 1 1
11 0 1 1 2
12 2 1 1 1
13 2 1 1 2
14 5 1 1 1
15 5 1 1 2
Table 13-12: Parameters for PDCCH monitoring occasions for Type0-PDCCH CSS set - SS/PBCH
block and CORESET multiplexing pattern 1 and FR2
Number of search space sets per

Index O slot M First symbol index
0 0 1 1 0
1 0 2 1/2 {0, if i is even}, {7, if i is odd}
2 2.5 1 1 0
3 2.5 2 1/2 {0, if i is even}, {7, if i is odd}
4 5 1 1 0
5 5 2 1/2 {0, if i is even}, {7, if i is odd}
6 0 2 1/2 {0, if i is even}, { N symb
CORESET
, if i is odd}
7 2.5 2 1/2 {0, if i is even}, { N symb

CORESET
, if i is odd}
8 5 2 1/2 {0, if i is even}, { N symb

CORESET
, if i is odd}
9 7.5 1 1 0
10 7.5 2 1/2 {0, if i is even}, {7, if i is odd}
11 7.5 2 1/2 {0, if i is even}, { N symb
CORESET
, if i is odd}
12 0 1 2 0
13 5 1 2 0
14 Reserved
15 Reserved
ETSI
Table 13-13: PDCCH monitoring occasions for Type0-PDCCH CSS set - SS/PBCH block and
CORESET multiplexing pattern 2 and {SS/PBCH block, PDCCH} SCS {120, 60} kHz
First symbol index
Index PDCCH monitoring occasions (SFN and slot number)
(k = 0, 1, … 15)
0, 1, 6, 7 for
SFN C = SFN SSB,i
0
n C = n SSB, i i = 4k , i = 4k + 1 , i = 4k + 2 ,
i = 4k + 3
1 Reserved
2 Reserved
3 Reserved
4 Reserved
5 Reserved
6 Reserved
7 Reserved
8 Reserved
9 Reserved
10 Reserved
11 Reserved
12 Reserved
13 Reserved
14 Reserved
15 Reserved
PDCCH monitoring occasions First symbol index
Index
(SFN and slot number) (k = 0, 1, …, 7)
0, 1, 2, 3, 0, 1 in i = 8k , i = 8k + 1 , i = 8k + 2 , i = 8k + 3 ,
SFN C = SFN SSB,i i = 8k + 6 , i = 8k + 7 ( nC = nSSB,i )
0
n C = n SSB, i or n C = nSSB, i − 1
12, 13 in i = 8k + 4 , i = 8k + 5 ( n C = nSSB, i − 1 )
1 Reserved
2 Reserved
3 Reserved
4 Reserved
5 Reserved
6 Reserved
7 Reserved
8 Reserved
9 Reserved
10 Reserved
11 Reserved
12 Reserved
13 Reserved
14 Reserved
15 Reserved
ETSI
First symbol index
Index PDCCH monitoring occasions (SFN and slot number)
(k = 0, 1, … 15)
4, 8, 2, 6 in
SFN C = SFN SSB,i
0
n C = n SSB, i i = 4k , i = 4k + 1 , i = 4k + 2 ,
i = 4k + 3
1 Reserved
2 Reserved
3 Reserved
4 Reserved
5 Reserved
6 Reserved
7 Reserved
8 Reserved
9 Reserved
10 Reserved
11 Reserved
12 Reserved
13 Reserved
14 Reserved
15 Reserved
If a UE detects a first SS/PBCH block and determines that a CORESET for Type0-PDCCH CSS set is not present, and
for 24 ≤ kSSB ≤ 29 for FR1 or for 12 ≤ k SSB ≤ 13 for FR2, the UE may determine the nearest (in the corresponding
frequency direction) global synchronization channel number (GSCN) of a second SS/PBCH block having a CORESET
for an associated Type0-PDCCH CSS set as NGSCN + NGSCN
Reference Offset
. Reference
N GSCN is the GSCN of the first SS/PBCH block and
N Offset
GSCN
is a GSCN offset provided by Table 13-16 for FR1 and Table 13-17 for FR2. If the UE detects the second
SS/PBCH block and the second SS/PBCH block does not provide a CORESET for Type0-PDCCH CSS set, as
described in clause 4.1, the UE may ignore the information related to GSCN of SS/PBCH block locations for
performing cell search.
If a UE detects a SS/PBCH block and determines that a CORESET for Type0-PDCCH CSS set is not present, and for
kSSB = 31 for FR1 or for kSSB = 15 for FR2, the UE determines that there is no SS/PBCH block having an associated
Type0-PDCCH CSS set within a GSCN range [ N GSCN Reference
− N GSCN
Start Reference
, N GSCN + N GSCN
End
] . N GSCN
Start
and N GSCN
End
are
respectively determined by controlResourceSetZero and searchSpaceZero in pdcch-ConfigSIB1. If the GSCN range is
Reference Reference
[NGSCN , NGSCN ] , the UE determines that there is no information for a second SS/PBCH block with a CORESET
for an associated Type0-PDCCH CSS set on the detected SS/PBCH block.
If a UE does not detect any SS/PBCH block providing a CORESET for Type0-PDCCH CSS set, as described in clause
4.1, within a time period determined by the UE, the UE may ignore the information related to GSCN of SS/PBCH
locations in performing cell search.
ETSI
Table 13-16: Mapping between the combination of k SSB and controlResourceSetZero and
Offset
searchSpaceZero in pdcch-ConfigSIB1 to NGSCN for FR1
16×controlResourceSetZero Offset
k SSB
+searchSpaceZero NGSCN
24 0, 1, …, 255 1, 2, …, 256
25 0, 1, …, 255 257, 258, …, 512
26 0, 1, …, 255 513, 514, …., 768
27 0, 1, …, 255 -1, -2, …, -256
28 0, 1, …, 255 -257, -258, …, -512
29 0, 1, …, 255 -513, -514, …., -768
30 0, 1, …, 255 Reserved, Reserved, …, Reserved
Table 13-17: Mapping between the combination of k SSB and controlResourceSetZero and
Offset
searchSpaceZero in pdcch-ConfigSIB1 to NGSCN for FR2
16×controlResourceSetZero Offset
k SSB
+searchSpaceZero NGSCN
12 0, 1, …, 255 1, 2, …, 256
13 0, 1, …, 255 -1, -2, …, -256
14 0, 1, …, 255 Reserved, Reserved, …, Reserved
14 Integrated access-backhaul operation

Throughout this specification, unless otherwise noted, statements using the term "UE" in clauses 4 through 13 are
equally applicable to the IAB-MT of an IAB node.
A procedure for an IAB-MT to perform cell search, system information acquisition, or random access procedure is same
as a corresponding one for a UE except for the following.
For initial cell selection, an IAB-MT may assume that half frames with SS/PBCH blocks occur with a periodicity of 16
frames.
For PRACH transmission, an IAB-MT determines frames and subframes/slots within the frames containing PRACH
occasions as described in [4, TS 38.211].
The IAB-MT determines an association period for mapping SS/PBCH blocks to PRACH occasions based on a PRACH
configuration period as described in clause 8.1 and according to Table 14-1 instead of Table 8.1-1. An association
pattern period includes one or more association periods and is determined so that a pattern between PRACH occasions
and SS/PBCH blocks repeats at most every 640 msec. A PRACH occasion in a PRACH slot is valid according to the
conditions in clause 8.1.
ETSI
Table 14-1: Mapping between PRACH configuration period and SS/PBCH block to PRACH occasion
association period for an IAB-MT
Association period (number of PRACH
PRACH configuration period (msec)
configuration periods)
10 {1, 2, 4, 8, 16, 32, 64}
20 {1, 2, 4, 8, 16, 32}
40 {1, 2, 4, 8, 16}
80 {1, 2, 4, 8}
160 {1, 2, 4}
320 {1, 2}
640 {1}
If an IAB-node is provided an index Tdelta in a Timing Delta MAC CE [11, TS 38.321] from a serving cell, the IAB-node
may assume that NTA /2 + delta + delta ⋅ Gstep ⋅ Tc is a time difference between a DU transmission of a signal from the
serving cell and a reception of the signal by the IAB-MT when NTA /2 + delta + delta ⋅ Gstep > 0, where NTA is obtained
as for a "UE" in clause 4.2 for the TAG containing the serving cell and delta and Gstep are determined as
- delta = −70528 and ௦௧௘௣ = 64, if the serving cell providing the Timing Delta MAC CE operates in FR1,
- delta = −17664 and ௦௧௘௣ = 32, if the serving cell providing the Timing Delta MAC CE operates in FR2
The IAB-node may use the time difference to determine a DU transmission time.
A slot format for an IAB-DU or an IAB-MT includes downlink symbols, uplink symbols, and flexible symbols.
For each cell of an IAB-DU, the IAB-DU can be provided an indication for a slot format over a number of slots by
gNB-DU Cell Resource Configuration [16, TS 38.473].
For each serving cell, an IAB-MT can be provided an indication for a slot format over a number of slots by tdd-UL-DL-
ConfigurationDedicated-IAB-MT. If the IAB-MT is provided tdd-UL-DL-ConfigurationDedicated-IAB-MT, the
statements in clause 11.1 that include "tdd-UL-DL-ConfigurationDedicated" apply to the IAB-MT of an IAB node by
replacing "tdd-UL-DL-ConfigurationDedicated" with "tdd-UL-DL-ConfigurationDedicated-IAB-MT" for the IAB-MT,
except that the tdd-UL-DL-ConfigurationDedicated-IAB-MT provides
- a set of slot configurations by slotSpecificConfigurationsToAddModList-IAB-MT
- for each slot configuration from the set of slot configurations
- a slot index for a slot provided by slotIndex
- a set of symbols for a slot by symbols-IAB-MT where
- if symbols-IAB-MT = allDownlink, all symbols in the slot are downlink
- if symbols-IAB-MT = allUplink, all symbols in the slot are uplink
- if symbols-IAB-MT = explicit, nrofDownlinkSymbols provides a number of downlink first symbols in the slot
and nrofUplinkSymbols provides a number of uplink last symbols in the slot. If nrofDownlinkSymbols is not
provided, there are no downlink first symbols in the slot and if nrofUplinkSymbols is not provided, there are
no uplink last symbols in the slot. The remaining symbols in the slot are flexible.
- if symbols-IAB-MT = explicit-IAB-MT, nrofUplinkSymbols provides a number of uplink first symbols in the

slot and nrofDownlinkSymbols provides a number of downlink last symbols in the slot. If nrofUplinkSymbols
is not provided, there are no uplink first symbols in the slot and if nrofDownlinkSymbols is not provided,
there are no downlink last symbols in the slot. The remaining symbols in the slot are flexible.
An IAB-MT can be provided, by SlotFormatCombinationsPerCell, a list of slot format combinations applicable for one
serving cell and, by SlotFormatIndicator, a configuration for monitor a DCI format 2_0 indicating a slot format
combination, from the list of slot format combinations, over a number of slots as described in clause 11.1.1. In addition
to the slot formats in Table 11.1.1-1, an SFI field for an IAB-MT in DCI format 2_0 can indicate to the IAB-MT a slot
format from the slot formats in Table 14-2.
ETSI
Table 14-2: Slot formats for normal cyclic prefix

Slot Symbol number in a slot
Format 0 1 2 3 4 5 6 7 8 9 10 11 12 13
56 U U U U U U U U U U U U U F
57 U U U U U U U U U U U U F F
58 U U U U U U U U U U U F F F
59 U U U U U U U U U U F F F F
60 U U U U U U U U U F F F F F
61 U U U U U U U U F F F F F F
62 U U U U U U U F F F F F F F
63 U U U U U U F F F F F F F F
64 U U U U U F F F F F F F F F
65 U U U U F F F F F F F F F F
66 U U U F F F F F F F F F F F
67 U U F F F F F F F F F F F F
68 U F F F F F F F F F F F F F
69 U F F F F F F F F F F F F D
70 U U F F F F F F F F F F F D
71 U U U F F F F F F F F F F D
72 U F F F F F F F F F F F D D
73 U U F F F F F F F F F F D D
74 U U U F F F F F F F F F D D
75 U F F F F F F F F F F D D D
76 U U F F F F F F F F F D D D
77 U U U F F F F F F F F D D D
78 U U U U U U U U U U U U F D
79 U U U U U U U U U U U F F D
80 U U U U U U U U U U F F F D
81 U U U U U U U U U U U F D D
82 U U U U U U U U U U F F D D
83 U U U U U U U U U F F F D D
84 U F D D D D D D D D D D D D
85 U U F D D D D D D D D D D D
86 U U U F D D D D D D D D D D
87 U F F D D D D D D D D D D D
88 U U F F D D D D D D D D D D
89 U U U F F D D D D D D D D D
90 U F F F D D D D D D D D D D
91 U U F F F D D D D D D D D D
92 U U U F F F D D D D D D D D
93 U U U U U U U U U F F F F D
94 U U U U U U F F F F F F D D
95 U U U U U U F F D D D D D D
96 U U U U U U U D D D D D D D
For a serving cell of an IAB-MT, the IAB-MT can be provided by Provided Guard Symbols MAC CE a number of
symbols that will not be used for the IAB-MT in slots where the IAB-node transitions between IAB-MT and IAB-node
DU and a SCS configuration for the number of symbols [11, TS 38.321].
With reference to slots of an IAB-DU cell, a symbol in a slot of an IAB-DU cell can be configured to be of hard, soft, or
unavailable type. When a downlink, uplink, or flexible symbol is configured as hard, the IAB-DU cell can respectively
transmit, receive, or either transmit or receive in the symbol.
When a downlink, uplink, or flexible symbol is configured as soft, the IAB-DU cell can respectively transmit, receive
or either transmit or receive in the symbol only if
- the IAB-MT does not transmit or receive during the symbol of the IAB-DU cell, or
- the IAB-MT would transmit or receive during the symbol of the IAB-DU cell, and the transmission or reception
during the symbol of the IAB-DU cell is not changed due to a use of the symbol by the IAB-DU, or
ETSI
- the IAB-MT detects a DCI format 2_5 with an AI index field value indicating the soft symbol as available
When a symbol is configured as unavailable, the IAB-DU neither transmits nor receives in the symbol.
A symbol of a slot is equivalent to being configured as hard if an IAB-DU would transmit a SS/PBCH block, PDCCH
for Type0-PDCCH CSS sets configured by pdcchConfigSIB1, or a periodic CSI-RS in the symbol of the slot, or would
receive a PRACH or a SR in the symbol of the slot.
If an IAB-node is provided an AvailabilityIndicator, the IAB-node is provided an AI-RNTI by ai-RNTI and a payload
size of a DCI format 2_5 by dci-PayloadSizeAI. The IAB-node is also provided a search space set configuration, by
SearchSpace, for monitoring PDCCH.
For each cell of an IAB-DU in a set of cells of the IAB-DU, the IAB-DU can be provided:
- an identity of the IAB-DU cell by iab-DU-CellIdentity
- a location of an availability indicator (AI) index field in DCI format 2_5 by positionInDCI-AI
- a set of availability combinations by availabilityCombinations, where each availability combination in the set of
availability combinations includes
- resourceAvailability indicating availability of soft symbols in one or more slots for the IAB-DU cell, and
- a mapping for the soft symbol availability combinations provided by resourceAvailability to a corresponding
AI index field value in DCI format 2_5 provided by availabilityCombinationId
The IAB-DU can assume a same SCS configuration for availabilityCombinations for a cell as an SCS configuration
provided by gNB-DU Cell Resource Configuration for the cell.
An AI index field value in a DCI format 2_5 indicates to an IAB-DU a soft symbol availability in each slot for a
number of slots starting from the earliest slot of the IAB-DU which overlaps in time with the slot of the IAB-MT where
the IAB-MT detects the DCI format 2_5. The number of slots is equal to or larger than a PDCCH monitoring
periodicity for DCI format 2_5 as provided by SearchSpace. The AI index field includes
max { log 2 (maxAIindex + 1), 1} bits where maxAIindex is the maximum of the values provided by corresponding
availabilityCombinationId. An availability for a soft symbol in a slot is identified by a corresponding value
resourceAvailability as provided in Table 14-3.
Table 14-3: Mapping between values of resourceAvailability elements and types of soft symbol
availability in a slot
Value Indication
0 No indication of availability for soft symbols
DL soft symbols are indicated available
1
No indication of availability for UL and Flexible soft symbols
UL soft symbols are indicated available
2
No indication of availability for DL and Flexible soft symbols
DL and UL soft symbols are indicated available
3
No indication of availability for Flexible soft symbols
Flexible soft symbols are indicated available
4
No indication of availability for DL and UL soft symbols
DL and Flexible soft symbols are indicated available
5
No indication of availability for UL soft symbols
UL and Flexible soft symbols are indicated available
6
No indication of availability for DL soft symbols
7 DL, UL, and Flexible soft symbols are indicated available
If a PDCCH monitoring periodicity for DCI format 2_5 is smaller than a duration of an availability combination of soft
symbols over a number of slots that the IAB-MT obtains at a PDCCH monitoring occasion for DCI format 2_5 by a
corresponding AI index field value, and the IAB-MT detects more than one DCI formats 2_5 indicating an availability
combination of soft symbols in a slot, the IAB-MT expects that each of the more than one DCI formats 2_5 indicates a
same value for the availability combination of the soft symbols in the slot. An IAB-MT monitors PDCCH candidates
for a DCI format 2_5 with CRC scrambled by AI-RNTI in one or both of the following search space sets:
- a Type3-PDCCH CSS set configured by SearchSpace in PDCCH-Config with searchSpaceType = common;
- a USS set configured by SearchSpace in PDCCH-Config with searchSpaceType = ue-Specific.
ETSI
15 Dual active protocol stack based handover

If a UE indicates a capability for dual active protocol stack based handover (DAPS HO), the UE can be provided with a
source MCG and a target MCG.
If a UE is configured with a target MCG using NR radio access in FR1 or in FR2 and with a source MCG using NR
radio access in FR2 or in FR1, respectively, the UE performs transmission power control independently per cell group
as described in clauses 7.1 through 7.5.
If a UE is configured with a target MCG using NR radio access in FR1 and a source MCG using NR radio access in
FR1, the UE is configured a maximum power MCG for transmissions on the target MCG by p-DAPS-Target and a
maximum power SCG for transmissions on the source MCG by p-DAPS-Source and with an inter-CG power sharing
mode by uplinkPowerSharingDAPS-Mode. The UE determines a transmission power on the target MCG and a
transmission power on the source MCG per frequency range.
If the UE indicates support for semi-static power sharing mode1 and is provided uplinkPowerSharingDAPS-Mode =
Semi-static-mode1, the UE determines a transmission power for the target MCG or for the source MCG as described in
clause 7.6.2 for nrdc-PCmode-FR1 = Semi-static-mode1 by considering the target MCG as the MCG and the source
MCG as the SCG.
If the UE indicates support for semi-static power sharing mode2 and is provided uplinkPowerSharingDAPS-Mode =
Semi-static-mode2, the UE determines a transmission power for the target MCG or for the source SCG as described in
clause 7.6.2 for nrdc-PCmode-FR1 = Semi-static-mode2 by considering the target MCG as the MCG and the source
MCG as the SCG. The UE expects to be provided uplinkPowerSharingDAPS-Mode = Semi-static-mode2 only for
synchronous DAPS HO operation [10, TS 38.133].
If the UE indicates support for dynamic power sharing and is provided uplinkPowerSharingDAPS-Mode = Dynamic,
the UE determines a transmission power for the target MCG or for the source MCG as described in clause 7.6.2 for
nrdc-PCmode-FR1 = Dynamic by considering the target MCG as the MCG and the source MCG as the SCG.
Intra-frequency DAPS handover is described in clause 6.1.3.2 of [10, TS38.133].
For DAPS handover that is not intra-frequency, if
- the UE does not indicate support of interFreqUL-TransCancellationDAPS-r16, and
- UE does not indicate a capability for power sharing between source and target MCG in DAPS handover or the
UE is not provided with uplinkPowerSharingDAPS-Mode,
the UE does not expect transmissions on the target and source cell in overlapping time resources.
For DAPS handover that is not intra-frequency, if
- the UE indicates support of interFreqUL-TransCancellationDAPS-r16, and
- UE does not indicate a capability for power sharing between source and target MCG in DAPS handover or the
UE is not provided with uplinkPowerSharingDAPS-Mode, and
- UE transmissions on the target cell and the source cell are in overlapping time resources,
the UE transmits only on the target cell, and cancels the transmission to source cell.
For intra-frequency DAPS handover, if
- UE transmissions on the target cell and the source cell are in overlapping time resources,
the UE transmits only on the target cell and cancels the transmission on the source cell.
The UE does not expect to cancel a transmission on the source cell if a first symbol of the transmission on the source
cell is less than proc,2 + after a last symbol of a CORESET where the UE receives a PDCCH providing a DCI format
scheduling a transmission on the target cell. proc,2 is the PUSCH preparation time for the corresponding PUSCH
processing capability [6, TS 38.214] assuming 2,1 = 1, is a time duration corresponding to 2 symbols for SCS
configuration , and is the smallest SCS configuration between the SCS configuration of the PDCCH providing the
ETSI
DCI format and the SCS configuration for the transmission on the source cell. If the UE transmits PRACH using 1.25
kHz or 5 kHz SCS on the source cell, the UE determines proc,2 assuming SCS configuration = 0.
A UE does not expect to cancel a transmission on the source cell if the first symbol of the source cell transmission
occurs, relative to a last symbol of a PDSCH reception conveying a RAR message with a RAR UL grant on the target
cell, after a number of symbols that is smaller than T,1 + T,2 + 0.5 msec, where T,1 is a time duration of 1 symbols
corresponding to a PDSCH processing time for UE processing capability 1 when additional PDSCH DM-RS is
configured, T,2 is a time duration of 2 symbols corresponding to a PUSCH preparation time for UE processing
capability 1 [6, TS 38.214] and the UE considers that 1 and ଶ correspond to the smaller of the SCS configurations for
the PDSCH on the target cell and the transmission on the source cell. For = 0, the UE assumes 1,0 = 14 [6, TS
38.214].
For intra-frequency DAPS handover operation, the UE expects that an active DL BWP and an active UL BWP on the
target cell are within an active DL BWP and an active UL BWP on the source cell, respectively.
If a UE is provided search space sets on both the target MCG and the source MCG, in any slot the UE does not expect
to have USS sets on both the target MCG and the source MCG that result in the number of monitored PDCCH
candidates and the total number of non-overlapped CCEs in both cells that each exceed the corresponding maximum
numbers per slot defined in Table 10.1-2 and Table 10.1-3.
For DAPS operation in a same frequency band, a UE does not transmit PUSCH/PUCCH/SRS to the source MCG in a
slot overlapping in time with a PRACH transmission to the target MCG or when a gap between a first or last symbol of
a PRACH transmission to the target MCG in a first slot would be separated by less than symbols from a last or first
symbol, respectively, of the PUSCH/PUCCH/SRS transmission to the source MCG in a second slot. For DAPS
operation in a same frequency band, a UE does not transmit PRACH on the source MCG in a slot overlapping in time
with a PUSCH/PUCCH/SRS transmission on the target MCG or when a gap between the first or last symbol of a
PUSCH/PUCCH/SRS transmission on the target MCG is separated by less than symbols from a last or a first symbol,
respectively, of a PRACH transmission on the source MCG. = 2 for = 0 or = 1, = 4 for = 2 or = 3, and
is the SCS configuration of the active UL BWP for the PUSCH/PUCCH/SRS transmission. The PUSCH processing
capability is the processing capability of source cell.
16 UE procedures for sidelink

A UE is provided by SL-BWP-Config a BWP for SL transmissions (SL BWP) with numerology and resource grid
determined as described in [4, TS 38.211]. For a resource pool within the SL BWP, the UE is provided by sl-
NumSubchannel a number of sub-channels where each sub-channel includes a number of contiguous RBs provided by
sl-SubchannelSize. The first RB of the first sub-channel in the SL BWP is indicated by sl-StartRB-Subchannel.
Available slots for a resource pool are provided by timeresourcepool and occur with a periodicity of 10240 ms. For an
available slot without S-SS/PSBCH blocks, SL transmissions can start from a first symbol indicated by sl-StartSymbol
and be within a number of consecutive symbols indicated by sl-LengthSymbols. For an available slot with S-SS/PSBCH
blocks, the first symbol and the number of consecutive symbols is predetermined.
The UE expects to use a same numerology in the SL BWP and in an active UL BWP in a same carrier of a same cell. If
the active UL BWP numerology is different than the SL BWP numerology, the SL BWP is deactivated.
A priority of a PSSCH according to NR radio access or according to E-UTRA radio access is indicated by a priority
field in a respective scheduling SCI format. A priority of a PSSS/SSSS/PSBCH according to E-UTRA radio access is
provided by sl-SSB-PriorityEUTRA [13, TS 36.213]. A priority of an S-SS/PSBCH block is provided by sl-SSB-
PriorityNR. A priority of a PSFCH is same as the priority of a corresponding PSSCH.
A UE does not expect to be provided search space sets associated with CORESETs on more than one cell to monitor
PDCCH for detection of DCI format 3_0 or DCI format 3_1.
16.1 Synchronization procedures

A UE receives the following SL synchronization signals in order to perform synchronization procedures based on S-
SS/PSBCH blocks: SL primary synchronization signals (S-PSS) and SL secondary synchronization signals (S-SSS) [4,
TS 38.211].
ETSI
A UE assumes that reception occasions of a physical sidelink broadcast channel (PSBCH), S-PSS, and S-SSS are in
consecutive symbols [4, TS 38.211] and form a S-SS/PSBCH block.
For reception of a S-SS/PSBCH block, a UE assumes a frequency location corresponding to the subcarrier with index
66 in the S-SS/PSBCH block [4, TS 38.211], is provided by sl-AbsoluteFrequencySSB. The UE assumes that a S-PSS
symbol, a S-SSS symbol, and a PSBCH symbol have a same transmission power. The UE assumes a same numerology
of the S-SS/PSBCH as for a SL BWP of the S-SS/PSBCH block reception, and that a bandwidth of the S-SS/PSBCH is
within a bandwidth of the SL BWP. The UE assumes the subcarrier with index 0 in the S-SS/PSBCH block is aligned
with a subcarrier with index 0 in an RB of the SL BWP.
A UE is provided, by sl-NumSSB-WithinPeriod, a number ୮ୣ୰୧୭ୢ

ୗିୗୗ୆
of S-SS/PSBCH blocks in a period of 16 frames. The
UE assumes that a transmission of the S-SS/PSBCH blocks in the period is with a periodicity of 16 frames. The UE
determines indexes of slots that include S-SS/PSBCH block as ୭୤୤ୱୣ୲
ୗିୗୗ୆
+ ୧୬୲ୣ୰୴ୟ୪
ୗିୗୗ୆
+ 1 ⋅ !ୗିୗୗ୆, where
- index 0 corresponds to a first slot in a frame with SFN satisfying (SFN mod 16) = 0
- !ୗିୗୗ୆ is a S-SS/PSBCH block index within the number of S-SS/PSBCH blocks in the period, with 0 ≤ !ୗିୗୗ୆ ≤
୮ୣ୰୧୭ୢ
ୗିୗୗ୆
−1
- ୭୤୤ୱୣ୲
ୗିୗୗ୆
is a slot offset from a start of the period to the first slot including S-SS/PSBCH block, provided by sl-
TimeOffsetSSB
- ୧୬୲ୣ୰୴ୟ୪
ୗିୗୗ୆
is a slot interval between S-SS/PSBCH blocks, provided by sl-timeInterval
For paired spectrum, an S-SS/PSBCH block can be transmitted/received only in a slot of an UL carrier. For unpaired
spectrum, an S-SS/PSBCH block can be transmitted/received only in a slot of which all OFDM symbols are semi-
statically configured as UL as per the higher layer parameter tdd-UL-DL-ConfigurationCommon of the serving cell if
provided or sl-TDD-Configuration-r16 if provided or sl-TDD-Config-r16 of the received PSBCH if provided. Or if tdd-
UL-DL-ConfigurationCommon and sl-TDD-Configuration are not provided for a spectrum indicated with only PC5
interface in Table 5.2E.1-1 in [TS 38.101-1], an S-SS/PSBCH block can be transmitted/received in any slot of the
spectrum.
For transmission of an S-SS/PSBCH block, a UE includes a bit sequence "଴ , "ଵ , "ଶ , "ଷ , … , "ଵଵ in the PSBCH payload to
indicate sl-TDD-Config and provide a slot format over a number of slots.
For paired spectrum, or if tdd-UL-DL-ConfigurationCommon and sl-TDD-Configuration are not provided for a spectrum
indicated with only PC5 interface in Table 5.2E.1-1 in [TS 38.101-1],
- "଴, "ଵ , "ଶ , "ଷ, "ସ , "ହ , "଺, "଻ , "଼, "ଽ , "ଵ଴ , "ଵଵ are set to '1';
else
- "଴ = 0 if pattern1 is provided by sl-TDD-Configuration-r16 or tdd-UL-DL-ConfigurationCommon; "଴ = 1 if

both pattern1 and pattern2 are provided by sl-TDD-Configuration-r16 or tdd-UL-DL-ConfigurationCommon
as described in clause 11.1
- "ଵ, "ଶ , "ଷ , "ସ are determined based on

- in pattern1 as described in Table 16.1-1 for "଴ =0
- in pattern1 and ଶ in pattern2 as described in Table 16.1-2 for "଴ =1
where and ଶ are as described in clause 11.1
- "ହ, "଺ , "଻ , "଼, "ଽ , "ଵ଴ , "ଵଵ are the 7th to 1st LSBs of #ୱ୪୭୲ୱ
ୗ୐
, respectively
ഋషഋ౨౛౜
- for "଴ = 0, #ୱ୪୭୲ୱ
ୗ୐
= #ୱ୪୭୲ୱ ∗ 2ఓିఓ౨౛౜ + $௨౩౯ౣ∗ଶ௅ % + &ଵ
ೠ౩౯ౣ మ ∗మഋషഋ౨౛౜ ೠ౩౯ౣ ∗మഋషഋ౨౛౜
௨౩ౢ౥౪౩ మ ∗ଶഋషഋ౨౛౜ ା቞ ቟ାூమ ௨౩ౢ౥౪౩∗ଶഋషഋ౨౛౜ ା቞ ቟ାூభ
,
௉∗ଶഋାଵ
for "଴ = 1, #ୱ୪୭୲ୱ =' ಽ ಽ
,
ୗ୐
- ∗ +
௪ ௪ ௪
where
ETSI
- is the number of symbols in a slot: = 12 if cyclicPrefix = "ECP"; else, = 14
- ଵ is 1 if ୱ୷୫ ∗ 2ఓିఓ౨౛౜
≥ − , else ଵ is 0
- ଶ is 1 if ୱ୷୫,ଶ ∗ 2ఓିఓ౨౛౜
≥ − , else ଶ is 0
- is the sidelink starting symbol index provided by sl-StartSymbol
- is the granularity of slots indication as described in Table 16.1-2
- ୰ୣ୤ , ୱ୪୭୲ୱ , ୱ୷୫ , ୱ୪୭୲ୱ,ଶ , ୱ୷୫,ଶ

are the parameters of TDD-UL-ConfigurationCommon as described in
clause 11.1, or the parameters of sl-TDD-Configuration-r16 as defined in [9.3, TS 38.331]
- = 0, 1, 2, 3 corresponds to SL SCS as defined in [4, TS 38.211]
Table 16.1-1: Slot configuration period when one pattern is indicated
Slot configuration period of pattern1

ࢇ૚ ࢇ ૛ ࢇ ૜ ࢇ ૝
, , ,
ࡼ (msec)
0, 0, 0, 0 0.5
0, 0, 0, 1 0.625
0, 0, 1, 0 1
0, 0, 1, 1 1.25
0, 1, 0, 0 2
0, 1, 0, 1 2.5
0, 1, 1, 0 4
0, 1, 1, 1 5
1, 0, 0, 0 10
Reserved Reserved
Table 16.1-2: Slot configuration period and granularity when two patterns are indicated
Slot configuration Slot configuration period Granularity ࢝ in slots with different SCS
ࢇ૚ ࢇ૛ ࢇ૜ ࢇ૝
, , , period of pattern1 of pattern2 15kHz 30 kHz 60 kHz 120 kHz
ࡼ (msec) ࡼ૛ (msec)
0, 0, 0, 0 0.5 0.5
0, 0, 0, 1 0.625 0.625
0, 0, 1, 0 1 1
1
0, 0, 1, 1 0.5 2
0, 1, 0, 0 1.25 1.25
0, 1, 0, 1 2 0.5
0, 1, 1, 0 1 3
0, 1, 1, 1 2 2
1, 0, 0, 0 3 1
1, 0, 0, 1 1 4
1 2
1, 0, 1, 0 2 3
1, 0, 1, 1 2.5 2.5
1, 1, 0, 0 3 2
1, 1, 0, 1 4 1
1, 1, 1, 0 5 5 1 2 4
1, 1, 1, 1 10 10 1 2 4 8
If a UE would transmit or receive an S-SS/PSBCH block, and the transmission or reception would overlap in time with
transmissions or receptions on the sidelink using E-UTRA radio access, the UE transmits or receives the signal/channel
with the higher priority.
If a UE would transmit or receive sidelink synchronization signals for E-UTRA radio access, and the transmission or
reception would overlap in time with sidelink transmissions or receptions using NR radio access, the UE transmits or
receives the signal/channel with the higher priority.
ETSI
16.2 Power control

16.2.0 S-SS/PSBCH blocks
A UE determines a power S-SSB ( ) for an S-SS/PSBCH block transmission occasion in slot on active SL BWP of
carrier of serving cell as
ୗିୗୗ୆ +
S-SSB ( ) = CMAX , O,ୗିୗୗ୆ + 10 ଵ଴ 2ఓ ∙ ୖ୆ ୗିୗୗ୆ ⋅ [dBm]
where
- CMAX is defined in [8-1, TS 38.101-1]
- O,ୗିୗୗ୆ is a value of dl-P0-PSBCH if provided; else, S-SSB ( ) = CMAX
- ୗିୗୗ୆ is a value of dl-Alpha-PSBCH, if provided; else, ୗିୗୗ୆ = 1
- = ௕,௙ ,௖ (ௗ ) as described in clause 7.1.1 except that
- the RS resource is the one the UE uses for determining a power of a PUSCH transmission scheduled by a
DCI format 0_0 in serving cell when the UE is configured to monitor PDCCH for detection of DCI format
0_0 in serving cell
- the RS resource is the one corresponding to the SS/PBCH block the UE uses to obtain MIB when the UE is
not configured to monitor PDCCH for detection of DCI format 0_0 in serving cell
S−SSB
- RB = 11 is a number of resource blocks for a S-SS/PSBCH block transmission with SCS configuration
16.2.1 PSSCH
A UE determines a power PSSCH,௕,௖ ( ) for a PSSCH transmission on a resource pool in symbols where a corresponding
PSCCH is not transmitted in PSCCH-PSSCH transmission occasion on active SL BWP of carrier of serving cell
as:
PSSCH ( ) = CMAX , MAX ,େ୆ୖ , PSSCH,஽ , PSSCH,ௌ௅ ( ) [dBm]
where
- CMAX is defined in [8-1, TS 38.101-1]
- MAX ,େ୆ୖ is determined by a value of sl-MaxTransPower based on a priority level of the PSSCH transmission
and a CBR range that includes a CBR measured in slot − [6, TS 38.214]; if sl-MaxTransPower-r16 is not
provided, then MAX,େ୆ୖ = CMAX ;
- if dl-P0-PSSCH-PSCCH is provided
- PSSCH,஽ ( ) = O,஽ + 10 ଵ଴ 2ఓ ⋅ RB

PSSCH
+ ஽ ⋅ ஽ [dBm]
- else
- PSSCH,஽ ( ) = CMAX , MAX,େ୆ୖ [dBm]
where
- O,஽ is a value of dl-P0-PSSCH-PSCCH if provided
- ஽ is a value of dl-Alpha-PSSCH-PSCCH, if provided; else, ஽ = 1
- ஽ = ௕ ,௙,௖ (ௗ ) as described in clause 7.1.1 except that
- the RS resource is the one the UE uses for determining a power of a PUSCH transmission scheduled
by a DCI format 0_0 in serving cell when the UE is configured to monitor PDCCH for detection of
DCI format 0_0 in serving cell
ETSI
- the RS resource is the one corresponding to the SS/PBCH block the UE uses to obtain MIB when the
UE is not configured to monitor PDCCH for detection of DCI format 0_0 in serving cell
PSSCH
- RB ( )is a number of resource blocks for the PSSCH transmission occasion and is a SCS
configuration
- if sl-P0-PSSCH-PSCCH is provided and if a SCI format scheduling the PSSCH transmission includes a cast type
indicator field indicating unicast
- PSSCH,ௌ௅ ( ) = O,ௌ௅ + 10 ଵ଴ 2ఓ ⋅ RB

PSSCH
+ ௌ௅ ⋅ ௌ௅ [dBm]
- else
- PSSCH,SL ( ) = CMAX , PSSCH,஽ ( ) [dBm]
where
- O,ௌ௅ is a value of sl-P0-PSSCH-PSCCH, if provided
- ௌ௅ is a value of sl-Alpha-PSSCH-PSCCH, if provided; else, ௌ௅ = 1
- ௌ௅ = !! !!"# ! – ℎℎ! #$! %! !

&"& , where
- !! !!"# ! is obtained from a PSSCH transmit power per RE summed over the antenna
ports of the UE, higher layer filtered across PSSCH transmission occasions using a filter configuration
provided by sl-filterCoefficient, and
- ℎℎ! #$! %! !

&"& is a RSRP, as defined in [7, TS 38.215], that is reported to the UE from
a UE receiving the PSCCH-PSSCH transmission and is obtained from a PSSCH DM-RS using a filter
configuration provided by sl-filterCoefficient
PSSCH
- RB ( )is a number of resource blocks for PSCCH-PSSCH transmission occasion and is a SCS
configuration
The UE splits the power PSSCH ( ) equally across the antenna ports on which the UE transmits the PSSCH with non-
zero power.
A UE determines a power PSSCH2,௕,௖ ( ) for a PSSCH transmission on a resource pool in the symbols where a
corresponding PSCCH is transmitted in PSCCH-PSSCH transmission occasion on active SL BWP of carrier of
serving cell as
ெౌ౏౏ిౄሺ௜ሻିெౌ౏ిిౄሺ௜ሻ
୔ୗୗେୌଶ ( ) = 10 ଵ଴ ' ౎ా ౌ౏౏ిౄ౎ా ( + ୔ୗୗେୌ ( ) [dBm]
ெ౎ా ሺ௜ሻ
PSCCH
where RB ( ) is a number of resource blocks for the corresponding PSCCH transmission in PSCCH-PSSCH
transmission occasion .
The UE splits the power ୔ୗୗେୌଶ ( ) equally across the antenna ports on which the UE transmits the PSSCH with non-
zero power.
16.2.2 PSCCH
A UE determines a power ୔ୗେେୌ,௕,௖ ( ) for a PSCCH transmission on a resource pool in PSCCH-PSSCH transmission
occasion as
ெౌ౏ిిౄሺ௜ሻ
୔ୗେେୌ ( ) = 10 ଵ଴ ' ౎ా ( + ୔ୗୗେୌ ( ) [dBm]
ெౌ౏౏ిౄሺ௜ሻ
౎ా
where
- ୔ୗୗେୌ ( ) is specified in clause 16.2.1
- PSCCH
RB ( ) is a number of resource blocks for the PSCCH transmission in PSCCH-PSSCH transmission occasion

ETSI
- ୔ୗୗେୌ ( )
ୖ୆ is a number of resource blocks for PSCCH-PSSCH transmission occasion i
16.2.3 PSFCH
A UE with ୱୡ୦,୘୶,୔ୗ୊େୌ scheduled PSFCH transmissions, and capable of transmitting a maximum of ୫ୟ୶,୔ୗ୊େୌ
PSFCHs, determines a number ୘୶,୔ୗ୊େୌ of simultaneous PSFCH transmissions and a power PSFCH,k ( ) for a PSFCH
transmission ), 1 ≤ ) ≤ ୘୶,୔ୗ୊େୌ , on a resource pool in PSFCH transmission occasion on active SL BWP of
carrier of serving cell as
- if dl-P0-PSFCH is provided,
PSFCH,one = O,௉ௌி஼ு + 10 ଵ଴ 2ఓ + ௉ௌி஼ு ⋅ [dBm]
where
- O,௉ௌி஼ு is a value of dl-P0-PSFCH
- ௉ிௌ஼ு is a value of dl-Alpha-PSFCH, if provided; else, ௉ிௌ஼ு = 1
- = ௕ ,௙,௖ (ௗ ) as described in clause 7.1.1 except that
- the RS resource is the one the UE uses for determining a power of a PUSCH transmission scheduled
by a DCI format 0_0 in serving cell when the UE is configured to monitor PDCCH for detection of
DCI format 0_0 in serving cell
- the RS resource is the one corresponding to the SS/PBCH block the UE uses to obtain MIB when the
UE is not configured to monitor PDCCH for detection of DCI format 0_0 in serving cell
- if ୱୡ୦,୘୶,୔ୗ୊େୌ ≤ ୫ୟ୶,୔ୗ୊େୌ
- if PSFCH,one + 10 ଵ଴ ୱୡ୦,୘୶,୔ୗ୊େୌ ≤ CMAX , where CMAX is determined for ୱୡ୦,୘୶,୔ୗ୊େୌ PSFCH
transmissions according to [8-1, TS 38.101-1]
- ୘୶,୔ୗ୊େୌ = ୱୡ୦,୘୶,୔ୗ୊େୌ and PSFCH,k ( ) = PSFCH,one [dBm]
- else
- UE autonomously determines ୘୶,୔ୗ୊େୌ PSFCH transmissions with ascending priority order as

described in clause 16.2.4.2 such that ୘୶,୔ୗ୊େୌ ≥ max1, ∑௄
௜ୀଵ ௜ where ௜ is a number of PSFCHs
with priority value and + is defined as
- the largest value satisfying PSFCH,one + 10 ଵ଴ max1, ∑௄

௜ୀଵ ௜ ≤ CMAX where CMAX is
determined according to [8-1, TS 38.101-1] for transmission of all PSFCHs assigned with priority
values 1, 2, …, + , if any
- zero, otherwise
and
PSFCH,k ( ) = CMAX − 10 ଵ଴ (୘୶,୔ୗ୊େୌ ), PSFCH,one [dBm]
where CMAX is defined in [8-1, TS 38.101-1] and is determined for the ୘୶,୔ୗ୊େୌ PSFCH
transmissions
- else
- the UE autonomously selects ୫ୟ୶,୔ୗ୊େୌ PSFCH transmissions with ascending priority order as described
in clause 16.2.4.2
- if PSFCH,one + 10 ଵ଴ ୫ୟ୶,୔ୗ୊େୌ ≤ CMAX , where CMAX is determined for the ୫ୟ୶,୔ୗ୊େୌ PSFCH
- ୘୶,୔ୗ୊େୌ = ୫ୟ୶,୔ୗ୊େୌ and PSFCH,k ( ) = PSFCH,one [dBm]
- else
ETSI
- the UE autonomously selects ୘୶,୔ୗ୊େୌ PSFCH transmissions in ascending order of corresponding

priority field values as described in clause 16.2.4.2 such that ୘୶,୔ୗ୊େୌ ≥ max1, ∑௄
௜ୀଵ ௜ where
௜ is a number of PSFCHs with priority value and + is defined as
- the largest value satisfying PSFCH,one + 10 ଵ଴ max1, ∑௄

௜ୀଵ ௜ ≤ CMAX where CMAX is
determined according to [8-1, TS 38.101-1] for transmission of all PSFCHs assigned with
priority values 1, 2, …, + , if any
- zero, otherwise
and
PSFCH,k ( ) = CMAX − 10 ଵ଴ (୘୶,୔ୗ୊େୌ ), PSFCH,one [dBm]
where CMAX is determined for the ୘୶,୔ୗ୊େୌ simultaneous PSFCH transmissions according to [8-
1, TS 38.101-1]
- else
PSFCH,k ( ) = CMAX − 10 ଵ଴ (୘୶,୔ୗ୊େୌ ) [dBm]
where the UE autonomously determines ୘୶,୔ୗ୊େୌ PSFCH transmissions with ascending priority order as
described in clause 16.2.4.2 such that ୘୶,୔ୗ୊େୌ ≥ 1 and where CMAX is determined for the ୘୶,୔ୗ୊େୌ PSFCH
16.2.4 Prioritization of transmissions/receptions
16.2.4.1 Simultaneous NR and E-UTRA transmission/reception

If a UE
- would transmit a first channel/signal using E-UTRA radio access and second channels/signals using NR radio
access, and
- a transmission of the first channel/signal would overlap in time with a transmission of the second
channels/signals, and
- the priorities of the channels/signals are known to both E-UTRA radio access and NR radio access at the UE ,
msec prior to the start of the earliest of the two transmissions, where , ≤ 4 and is based on UE implementation,
the UE transmits only the channels/signals of the radio access technology with the highest priority as determined by the
SCI formats scheduling the transmissions or, in case of a S-SS/PSBCH block or a sidelink synchronization signal using
E-UTRA radio access, as indicated by higher layers or, in case of PSFCH, equal to the priority of the corresponding
PSSCH.
If a UE
- would respectively transmit or receive a first channel/signal using E-UTRA radio access and receive a second
channel/signal or transmit second channels/signals using NR radio access, and
- a transmission or reception of the first channel/signal would respectively overlap in time with a reception of the
second channel/signal or transmission of the second channels/signals, and
- the priorities of the channels/signals are known to both E-UTRA radio access and NR radio access at the UE ,
msec prior to the start of the earliest transmission or reception, where , ≤ 4 and is based on UE implementation,
the UE transmits or receives only the channels/signals of the radio access technology with the highest priority as
determined by the SCI formats scheduling the transmissions or, in case of a S-SS/PSBCH block or a sidelink
synchronization signal using E-UTRA radio access, as indicated by higher layers or, in case of PSFCH, equal to the
priority of the corresponding PSSCH.
ETSI
16.2.4.2 Simultaneous PSFCH transmission/reception

If a UE
- would transmit ୱୡ୦,୘୶,୔ୗ୊େୌ PSFCHs and receive ୱୡ୦,ୖ୶,୔ୗ୊େୌ PSFCHs, and
- transmissions of the ୱୡ୦,୘୶,୔ୗ୊େୌ PSFCHs would overlap in time with receptions of the ୱୡ୦,ୖ୶,୔ୗ୊େୌ PSFCHs
the UE transmits or receives only a set of PSFCHs corresponding to the smallest priority field value, as determined by a
first set of SCI format 1-A and a second set of SCI format 1-A [5, TS 38.212] that are respectively associated with the
ୱୡ୦,୘୶,୔ୗ୊େୌ PSFCHs and the ୱୡ୦,ୖ୶,୔ୗ୊େୌ PSFCHs.
If a UE would transmit ୱୡ୦,୘୶,୔ୗ୊େୌ PSFCHs in a PSFCH transmission occasion, the UE transmits ୘୶,୔ୗ୊େୌ PSFCHs
corresponding to the smallest ୘୶,୔ୗ୊େୌ priority field values indicated in all SCI formats 1-A associated with the
PSFCH transmission occasion.
16.2.4.3 Simultaneous SL and UL transmissions/receptions

If a UE
- would simultaneously transmit on the UL and on the SL in a carrier or in two respective carriers, and
- the UE is not capable of simultaneous transmissions on the UL and on the SL in the carrier or in the two
respective carriers
the UE transmits only on the link, UL or SL, with the higher priority.
If a UE
- would simultaneously transmit on the UL and receive on the SL in a carrier, or
- would simultaneously transmit on the UL and receive on the SL in two respective carriers and the UE is not
capable of simultaneous transmission on the UL and reception on the SL in the two respective carriers
the UE transmits on UL or receives on SL, with the higher priority.
If a UE
- is capable of simultaneous transmissions on the UL and on the SL in two respective carriers,
- would transmit on the UL and on the SL in the two respective carriers,
- the transmission on the UL would overlap with the transmission on the SL over a time period, and
- the total UE transmission power over the time period would exceed CMAX
the UE
- reduces the power for the UL transmission prior to the start of the UL transmission, if the SL transmission has
higher priority than the UL transmission as determined in clause 16.2.4.3.1, so that the total UE transmission
power would not exceed CMAX
- reduces the power for the SL transmission prior to the start of the SL transmission, if the UL transmission has
higher priority than the SL transmission as determined in clause 16.2.4.3.1, so that the total UE transmission
power would not exceed CMAX
16.2.4.3.1 Prioritizations for sidelink and uplink transmissions/receptions

A UE performs prioritization between SL transmissions/receptions and UL transmissions after performing the
procedures described in clause 9, clause 9.2.5, and clause 9.2.6, and in clause 6.1 of [6, TS 38.214].
PSFCH transmissions in a slot have a same priority value as the smallest priority value among PSSCH receptions with
corresponding HARQ-ACK information provided by the PSFCH transmissions in the slot.
ETSI
PSFCH receptions in a slot have a same priority value as the smallest priority value among PSSCH transmissions with
corresponding HARQ-ACK information provided by the PSFCH receptions in the slot.
A priority of S-SS/PSBCH block transmission or reception is provided by sl-SSB-PriorityNR.
For prioritization between SL transmission or PSFCH/S-SS/PSBCH block reception and UL transmission other than a
PRACH, or a PUSCH scheduled by an UL grant in a RAR and its retransmission, or a PUSCH corresponding to Type-2
random access procedure and its retransmission, or a PUCCH with sidelink HARQ-ACK information report
- if the UL transmission is for a PUSCH or for a PUCCH with priority index 1,
- if sl-PriorityThreshold-UL-URLLC is provided
- the SL transmission or reception has higher priority than the UL transmission if the priority value of the
SL transmission(s) is smaller than sl-PriorityThreshold-UL-URLLC; otherwise, the UL transmission has
higher priority than the SL transmission or reception
- else
- the UL transmission has higher priority than the SL transmission or reception
- else
- the SL transmission or reception has higher priority than the UL transmission if the priority value of the SL
transmission(s) or reception is smaller than sl-PriorityThreshold; otherwise, the UL transmission has higher
priority than the SL transmission or reception
A PRACH transmission, or a PUSCH scheduled by an UL grant in a RAR and its retransmission, or a PUSCH for
Type-2 random access procedure and its retransmission, or a PUCCH with HARQ-ACK information in response to
successRAR, or a PUCCH indicated by a DCI format 1_0 with CRC scrambled by a corresponding TC-RNTI has
higher priority than a SL transmission or reception.
A PUCCH transmission with a sidelink HARQ-ACK information report has higher priority than a SL transmission if a
priority value of the PUCCH is smaller than a priority value of the SL transmission. The priority value of the PUCCH
transmission is as described in clause 16.5. If the priority value of the PUCCH transmission is larger than the priority
value of the SL transmission, the SL transmission has higher priority.
A PUCCH transmission with a sidelink HARQ-ACK information report has higher priority than a PSFCH/S-
SS/PSBCH block reception if a priority value of the PUCCH is smaller than a priority value of the SL reception. If the
priority value of the PUCCH transmission is larger than the priority value of the PSFCH/S-SS/PSBCH block reception,
the SL reception has higher priority.
When one or more SL transmissions from a UE overlap in time with multiple non-overlapping UL transmissions from
the UE, the UE performs the SL transmissions if at least one SL transmission is prioritized over all UL transmissions
subject to the UE processing timeline with respect to the first SL transmission and the first UL transmission.
When one or more UL transmissions from a UE overlap in time with multiple non-overlapping SL transmissions, the
UE performs the UL transmissions if at least one UL transmission is prioritized over all SL transmissions subject to the
UE processing timeline with respect to the first SL transmission and the first UL transmission.
When one SL transmission overlaps in time with one or more overlapping UL transmissions, the UE performs the SL
transmission if the SL transmission is prioritized over all UL transmissions subject to both the UE multiplexing and
processing timelines with respect to the first SL transmission and the first UL transmission, where the UE processing
timeline with respect to the first SL transmission and the first UL transmission is same as when one or more SL
transmissions overlap in time with multiple non-overlapping UL transmissions.
When one SL transmission overlaps in time with one or more overlapping UL transmissions, the UE performs the UL
transmission if at least one UL transmission is prioritized over the SL transmission subject to both the UE multiplexing
and processing timelines with respect to the first SL transmission and the first UL transmission, where the UE
processing timeline with respect to the first SL transmission and the first UL transmission is same as when one or more
SL transmissions overlap in time with multiple non-overlapping UL transmissions.
ETSI
16.3 UE procedure for reporting HARQ-ACK on sidelink

A UE can be indicated by an SCI format scheduling a PSSCH reception, in one or more sub-channels from a number of
PSSCH
subch sub-channels, to transmit a PSFCH with HARQ-ACK information in response to the PSSCH reception. The UE
provides HARQ-ACK information that includes ACK or NACK, or only NACK.
A UE can be provided, by sl-PSFCH-Period, a number of slots in a resource pool for a period of PSFCH transmission
occasion resources. If the number is zero, PSFCH transmissions from the UE in the resource pool are disabled.
A UE expects that a slot %′௞ௌ௅ (0 ≤ ) < ,′௠௔௫ ) has a PSFCH transmission occasion resource if ) mod PSSCH
PSFCH
= 0,
ௌ௅
where %′௞ is defined in [6, TS 38.214], and ,′௠௔௫ is a number of slots that belong to the resource pool within 10240
PSFCH
msec according to [6, TS 38.214], and PSSCH is provided by sl-PSFCH-Period.
A UE may be indicated by higher layers to not transmit a PSFCH in response to a PSSCH reception [11, TS 38.321].
If a UE receives a PSSCH in a resource pool and the HARQ feedback enabled/disabled indicator field in an associated
SCI format 2-A or a SCI format 2-B has value 1 [5, TS 38.212], the UE provides the HARQ-ACK information in a
PSFCH transmission in the resource pool. The UE transmits the PSFCH in a first slot that includes PSFCH resources
and is at least a number of slots, provided by sl-MinTimeGapPSFCH, of the resource pool after a last slot of the PSSCH
reception.
PSFCH
A UE is provided by sl-PSFCH-RB-Set a set of PRB, set PRBs in a resource pool for PSFCH transmission in a PRB of
the resource pool. For a number of subch sub-channels for the resource pool, provided by sl-NumSubchannel, and a
PSFCH
number of PSSCH slots associated with a PSFCH slot that is less than or equal to PSSCH , the UE allocates the
PSFCH PSFCH PSFCH PSFCH PSFCH
- + . ⋅ PSSCH ⋅ subch, slot , + 1 + . ⋅ PSSCH ⋅ subch, slot − 1/ PRBs from the PRB, set PRBs to slot among the
PSFCH PSFCH PSFCH
PSSCH slots associated with the PSFCH slot and sub-channel ., where subch, slot = PRB, set 0subch ⋅ PSSCH , 0 ≤
PSFCH
< PSSCH , 0 ≤ . < subch , and the allocation starts in an ascending order of and continues in an ascending order of ..
PSFCH PSFCH
The UE expects that PRB, set is a multiple of subch ∙ PSSCH .
The second OFDM symbol ′of PSFCH transmission in a slot is defined as = startSLsymbols+ lengthSLsymbols - 2.
′
A UE determines a number of PSFCH resources available for multiplexing HARQ-ACK information in a PSFCH
PSFCH PSFCH PSFCH PSFCH PSFCH
transmission as &PRB, CS = type ⋅ subch, slot ⋅ CS where CS is a number of cyclic shift pairs for the resource
pool provided by sl-NumMuxCS-Pair and, based on an indication by sl-PSFCH-CandidateResourceType,
PSFCH PSFCH
- if sl-PSFCH-CandidateResourceType is configured as startSubCH, type = 1 and the subch, slot PRBs are
associated with the starting sub-channel of the corresponding PSSCH;
PSFCH PSSCH PSSCH PSFCH
- if sl-PSFCH-CandidateResourceType is configured as allocSubCH, type = subch and the subch ⋅ subch, slot
PSSCH
PRBs are associated with one or more sub-channels from the subch sub-channels of the corresponding PSSCH.
PSFCH PSFCH
The PSFCH resources are first indexed according to an ascending order of the PRB index, from the type ⋅ subch, slot
PSFCH
PRBs, and then according to an ascending order of the cyclic shift pair index from the CS cyclic shift pairs.
A UE determines an index of a PSFCH resource for a PSFCH transmission in response to a PSSCH reception as
PSFCH
ID + ୍ୈ
&PRB, CS where ID is a physical layer source ID provided by SCI format 2-A or 2-B [5, TS 38.212]
scheduling the PSSCH reception, and ID is the identity of the UE receiving the PSSCH as indicated by higher layers
if the UE detects a SCI format 2-A with Cast type indicator field value of "01"; otherwise, ID is zero.
A UE determines a 0 value, for computing a value of cyclic shift [4, TS 38.211], from a cyclic shift pair index
PSFCH
corresponding to a PSFCH resource index and from CS using Table 16.3-1.
Table 16.3-1: Set of cyclic shift pairs
20
1PSFCH
CS Cyclic Shift Cyclic Shift Cyclic Shift Cyclic Shift Cyclic Shift Cyclic Shift
Pair Index 0 Pair Index 1 Pair Index 2 Pair Index 3 Pair Index 4 Pair Index 5
1 0 - - - - -
ETSI
2 0 3 - - - -
3 0 2 4 - - -
6 0 1 2 3 4 5
A UE determines a cs value, for computing a value of cyclic shift [4, TS 38.211], as in Table 16.3-2 if the UE
detects a SCI format 2-A with Cast type indicator field value of "01" or "10", or as in Table 16.3-3 if the UE detects a
SCI format 2-B or a SCI format 2-A with Cast type indicator field value of "11". The UE applies one cyclic shift from a
cyclic shift pair to a sequence used for the PSFCH transmission [4, TS 38.211].
Table 16.3-2: Mapping of HARQ-ACK information bit values to a cyclic shift, from a cyclic shift pair,
of a sequence for a PSFCH transmission when HARQ-ACK information includes ACK or NACK
HARQ-ACK Value 0 (NACK) 1 (ACK)

Sequence cyclic shift 0 6
Table 16.3-3: Mapping of HARQ-ACK information bit values to a cyclic shift, from a cyclic shift pair,
of a sequence for a PSFCH transmission when HARQ-ACK information includes only NACK
HARQ-ACK Value 0 (NACK) 1 (ACK)

Sequence cyclic shift 0 N/A
16.3.1 UE procedure for receiving HARQ-ACK on sidelink

A UE that transmitted a PSSCH scheduled by a SCI format 2-A or a SCI format 2-B that indicates HARQ feedback
enabled, attempts to receive associated PSFCHs according to PSFCH resources determined as described in clause 16.3.
The UE determines an ACK or a NACK value for HARQ-ACK information provided in each PSFCH resource as
described in [10, TS 38.133]. The UE does not determine both an ACK value and a NACK value at a same time for a
PSFCH resource.
For each PSFCH reception occasion, from a number of PSFCH reception occasions, the UE generates HARQ-ACK
information to report to higher layers. For generating the HARQ-ACK information, the UE can be indicated by a SCI
format to perform one of the following
- if the UE receives a PSFCH associated with a SCI format 2-A with Cast type indicator field value of "10"
- report to higher layers HARQ-ACK information with same value as a value of HARQ-ACK information that
the UE determines from the PSFCH reception
- report an ACK value to higher layers if the UE determines an ACK value from at least one PSFCH reception
occasion from the number of PSFCH reception occasions in PSFCH resources corresponding to every
identity ID of UEs that the UE expects to receive corresponding PSSCHs as described in clause 16.3;
otherwise, report a NACK value to higher layers
- if the UE receives a PSFCH associated with a SCI format 2-B or a SCI format 2-A with Cast type indicator field
value of "11"
- report to higher layers an ACK value if the UE determines absence of PSFCH reception for the PSFCH
reception occasion; otherwise, report a NACK value to higher layers
16.4 UE procedure for transmitting PSCCH

A UE can be provided a number of symbols in a resource pool, by sl-TimeResourcePSCCH, starting from a second
symbol that is available for SL transmissions in a slot, and a number of PRBs in the resource pool, by sl-
ETSI
FreqResourcePSCCH, starting from the lowest PRB of the lowest sub-channel of the associated PSSCH, for a PSCCH
transmission with a SCI format 1-A.
A UE that transmits a PSCCH with SCI format 1-A using sidelink resource allocation mode 2 [6, TS 38.214] sets
- "Resource reservation period" as an index in sl-ResourceReservePeriodList corresponding to a reservation

period provided by higher layers [11, TS 38.321], if the UE is provided sl-MultiReserveResource
- the values of the frequency resource assignment field and the time resource assignment field as described in [6,
TS 38.214] to indicate resources from a set ൛&y ൟ of resources selected by higher layers as described in [11, TS
38.321] with smallest slot indices $݅ for 0 ≤ ≤ − 1 such that $0 < $1 < ⋯ < $ܰ−1 ≤ $0 + 31, where:
- = minୱୣ୪ୣୡ୲ୣୢ , ୫ୟ୶_୰ୣୱୣ୰୴ୣ , where selected is a number of resources in the set ൛&y ൟ with slot indices
$௝ , 0 ≤ . ≤ ୱୣ୪ୣୡ୲ୣୢ − 1, such that $0 < $1 < ⋯ < $ܰ ≤ $0 + 31, and ୫ୟ୶_୰ୣୱୣ୰୴ୣ is provided by
selected −1
sl-MaxNumPerReserve
- each resource, from the set of 3&y 4 resources, corresponds to subCH contiguous sub-channels and a slot in a
set of slots {%′௬ௌ௅ }, where subCH is the number of sub-channels available for PSSCH/PSCCH transmission in a
slot
ܵ‫ܮ‬ ܵ‫ܮ‬ ܵ‫ܮ‬
- ൫%′0 , %′1 , %′2 , . . . ൯ is a set of slots in a sidelink resource pool [6, TS 38.214]
- $0 is an index of a slot where the PSCCH with SCI format 1-A is transmitted.
A UE that transmits a PSCCH with SCI format 1-A using sidelink resource allocation mode 1 [6, TS 38.214] sets
- the values of the frequency resource assignment field and the time resource assignment field for the SCI format
1-A transmitted in the -th resource for PSCCH/PSSCH transmission provided by a dynamic grant or by a SL
configured grant, where = 51, … , 6 and M is the total number of resources for PSCCH/PSSCH transmission
provided by a dynamic grant or the number of resources for PSCCH/PSSCH transmission in a period provided
by a SL configured grant type 1 or SL configured grant type 2, as follows:
- the frequency resource assignment field and time resource assignment field indicate the -th to -th
resources as described in [6, TS 38.214].
For decoding of a SCI format 1-A, a UE may assume that a number of bits provided by sl-NumReservedBits can have
any value.
16.5 UE procedure for reporting HARQ-ACK on uplink

A UE can be provided PUCCH resources or PUSCH resources [12, TS 38.331] to report HARQ-ACK information that
the UE generates based on HARQ-ACK information that the UE obtains from PSFCH receptions, or from absence of
PSFCH receptions. The UE reports HARQ-ACK information on the primary cell of the PUCCH group, as described in
clause 9, of the cell where the UE monitors PDCCH for detection of DCI format 3_0.
For SL configured grant Type 1 or Type 2 PSSCH transmissions by a UE within a time period provided by sl-
PeriodCG, the UE generates one HARQ-ACK information bit in response to the PSFCH receptions to multiplex in a
PUCCH transmission occasion that is after a last time resource, in a set of time resources.
For PSSCH transmissions scheduled by a DCI format 3_0, a UE generates HARQ-ACK information in response to
PSFCH receptions to multiplex in a PUCCH transmission occasion that is after a last time resource in a set of time
resources provided by the DCI format 3_0.
For each PSFCH reception occasion, from a number of PSFCH reception occasions, the UE generates HARQ-ACK
information to report in a PUCCH or PUSCH transmission. The UE can be indicated by a SCI format to perform one of
the following and the UE constructs a HARQ-ACK codeword with HARQ-ACK information, when applicable
- generate HARQ-ACK information with same value as a value of HARQ-ACK information the UE
determines from a PSFCH reception in the PSFCH reception occasion and, if the UE determines that a
PSFCH is not received at the PSFCH reception occasion, generate NACK
ETSI
- generate ACK if the UE determines ACK from at least one PSFCH reception occasion, from the number of
PSFCH reception occasions, in PSFCH resources corresponding to every identity ID of the UEs that the UE
expects to receive the PSSCH, as described in clause 16.3; otherwise, generate NACK
- if the UE receives a PSFCH associated with a SCI format 2-B or a SCI format 2-A with Cast type indicator field
value of "11"
- generate ACK when the UE determines absence of PSFCH reception for each PSFCH reception occasion
from the number of PSFCH reception occasions; otherwise, generate NACK
After a UE transmits PSSCHs and receives PSFCHs in corresponding PSFCH resource occasions, the priority value of
HARQ-ACK information is same as the priority value of the PSSCH transmissions that is associated with the PSFCH
reception occasions providing the HARQ-ACK information.
The UE generates a NACK when, due to prioritization, as described in clause 16.2.4, the UE does not receive PSFCH in
any PSFCH reception occasion associated with a PSSCH transmission in a resource provided by a DCI format 3_0 or,
for a configured grant, in a resource provided in a single period and for which the UE is provided a PUCCH resource to
report HARQ-ACK information. The priority value of the NACK is same as the priority value of the PSSCH
transmission.
The UE generates a NACK when, due to prioritization as described in clause 16.2.4, the UE does not transmit a PSSCH
in any of the resources provided by a DCI format 3_0 or, for a configured grant, in any of the resources provided in a
single period and for which the UE is provided a PUCCH resource to report HARQ-ACK information. The priority
value of the NACK is same as the priority value of the PSSCH that was not transmitted due to prioritization.
The UE generates an ACK if the UE does not transmit a PSCCH with a SCI format 1-A scheduling a PSSCH in any of
the resources provided by a configured grant in a single period and for which the UE is provided a PUCCH resource to
report HARQ-ACK information. The priority value of the ACK is same as the largest priority value among the possible
priority values for the configured grant.
For reporting HARQ-ACK information on uplink corresponding to one or multiple PSSCH transmissions with a
corresponding SCI format with the field 'HARQ feedback enabled/disabled indicator' set to disabled, the UE generates
HARQ-ACK information with the contents instructed by higher layer. The priority value of the HARQ-ACK
information is same as the priority value of the PSSCH transmission.
A UE does not expect to be provided PUCCH resources or PUSCH resources to report HARQ-ACK information that
start earlier than ,௣௥௘௣ = + 1 ∙ 2048 + 144 ∙ 7 ∙ 2ିఓ ∙ ,௖ after the end of a last symbol of a last PSFCH reception
occasion, from a number of PSFCH reception occasions that the UE generates HARQ-ACK information to report in a
PUCCH or PUSCH transmission, where
- 7 and ,௖ are defined in [4, TS 38.211]
- = min( ௌ௅ , ௎௅ ), where ௌ௅ is the SCS configuration of the SL BWP and ௎௅ is the SCS configuration of the
active UL BWP on the primary cell
- is determined from according to Table 16.5-1
Table 16.5-1: Values of 1
ࣆ ࡺ
0 14
1 18
2 28
3 32
For DCI format 3_0, if present, the PSFCH-to-HARQ_feedback timing indicator field values map to values for a set of
number of slots provided by sl-PSFCH-ToPUCCH-r16 as defined in Table 16.5-2.
ETSI
Table 16.5-2: Mapping of PSFCH-to-HARQ_feedback timing indicator field values to numbers of slots
PSFCH-to-HARQ_feedback timing indicator Number of slots k

1 bit 2 bits 3 bits
'0' '00' '000' 1st value provided by sl-PSFCH-ToPUCCH-r16
'1' '01' '001' 2nd value provided by sl-PSFCH-ToPUCCH-r16
'10' '010' 3rd value provided by sl-PSFCH-ToPUCCH-r16
'11' '011' 4th value provided by sl-PSFCH-ToPUCCH-r16
'100' 5th value provided by sl-PSFCH-ToPUCCH-r16
With reference to slots for PUCCH transmissions and for a number of PSFCH reception occasions ending in slot , the
UE provides the generated HARQ-ACK information in a PUCCH transmission within slot + ), subject to the
overlapping conditions in clause 9.2.5, where ) is a number of slots indicated by a PSFCH-to-HARQ_feedback timing
indicator field, if present, in a DCI format indicating a slot for PUCCH transmission to report the HARQ-ACK
information, or ) is provided by sl-PSFCH-ToPUCCH-r16 for a transmission scheduled by a DCI format or for a SL
configured grant type 2, or by sl-PSFCH-ToPUCCH-CG-Type1 for a SL configured grant type 1. ) = 0 corresponds to
a last slot for a PUCCH transmission that would overlap with the last PSFCH reception occasion assuming that the start
of the sidelink frame is same as the start of the downlink frame [4, TS 38.211].
For a PSSCH transmission by a UE that is scheduled by a DCI format, or for a SL configured grant Type 2 PSSCH
transmission activated by a DCI format, the DCI format indicates to the UE that a PUCCH resource is not provided
when a value of the PUCCH resource indicator field is zero and a value of PSFCH-to-HARQ feedback timing indicator
field, if present, is zero. For a SL configured grant Type 2 PSSCH transmission without a corresponding PDCCH, the
DCI format activating the SL configured grant Type 2 indicates to the UE that a PUCCH resource is not provided when
a value of the PUCCH resource indicator field is zero and a value of PSFCH-to-HARQ feedback timing indicator field,
if present, is zero. For a SL configured grant Type 1 PSSCH transmission, a PUCCH resource can be provided by sl-
N1PUCCH-AN and sl-PSFCH-ToPUCCH-CG-Type1. For transmission of HARQ-ACK information corresponding
only to a SL configured grant Type 2 PSSCH transmission without a corresponding PDCCH, a UE can be provided a
PUCCH resource by sl-N1PUCCH-AN-Type2. If a PUCCH resource is not provided, the UE does not transmit a
PUCCH with generated HARQ-ACK information from PSFCH reception occasions.
For a PUCCH transmission with HARQ-ACK information, a UE determines a PUCCH resource after determining a set
of PUCCH resources from up to four PUCCH resource sets provided by sl-PUCCH-Config-r16, for 8௎஼ூ HARQ-ACK
information bits, as described in clause 9.2.1. The PUCCH resource determination is based on a PUCCH resource
indicator field [5, TS 38.212] in a last DCI format 3_0, among the DCI formats 3_0 that have a value of a PSFCH-to-
HARQ_feedback timing indicator field indicating a same slot for the PUCCH transmission, that the UE detects and for
which the UE transmits corresponding HARQ-ACK information in the PUCCH where, for PUCCH resource
determination, detected DCI formats are indexed in an ascending order across PDCCH monitoring occasion indexes.
The PUCCH resource indicator field values map to values of a set of PUCCH resource indexes, as described in clause
9.2.3.
A UE transmits a PUCCH with HARQ-ACK information using PUCCH format 0 or PUCCH format 1 or PUCCH
format 2 or PUCCH format 3 or PUCCH format 4 as described in clause 9.2.3.
A UE does not expect to multiplex HARQ-ACK information for more than one SL configured grants in a same
PUCCH.
A priority value of a PUCCH transmission with one or more sidelink HARQ-ACK information bits is the smallest
priority value for the one or more HARQ-ACK information bits.
In the following, the CRC for DCI format 3_0 is scrambled with a SL-RNTI or a SL-CS-RNTI.

This clause applies if the UE is configured with pdsch-HARQ-ACK-Codebook = semi-static.
ETSI
If a UE is configured a SL configured grant Type 1, and the UE is configured a SL configured grant Type 2 or to
monitor PDCCH for detection of DCI format 3_0 with CRC scrambled by SL-RNTI or SL-CS-RNTI, and the UE is
provided a set of slot timing values +ଵ associated with a SL BWP by sl-PSFCH-ToPUCCH and sl-PSFCH-ToPUCCH-
CG-Type1, the sl-PSFCH-ToPUCCH-CG-Type1 is one of sl-PSFCH-ToPUCCH.
A UE reports HARQ-ACK information for PSSCH transmissions with corresponding PSFCH reception occasions in
slot only in a HARQ-ACK codebook that the UE includes in a PUCCH or PUSCH transmission in slot + ), where
) is a number of slots indicated by the PSFCH-to-HARQ_feedback timing indicator field in a DCI format 3_0
scheduling the PSSCH transmissions, or by a value of PSFCH-to-HARQ feedback timing indicator field in a DCI
format 3_0 activating a SL configured grant Type-2 transmission, or by a value of sl-PSFCH-ToPUCCH for a SL
configured grant Type-1. If the UE reports HARQ-ACK information for the PSSCH transmissions with corresponding
PSFCH reception occasions in a slot other than slot + ) , the UE sets a value for each corresponding HARQ-ACK
information bit to NACK.
If a UE reports HARQ-ACK information in a PUCCH only for
- PSFCH reception occasions associated with PSSCH transmissions scheduled by a DCI format 3_0 with counter
SAI field value of 1, or
- PSFCH reception occasions associated with PSSCH transmissions corresponding to a SL configured grant
within a set ஺ of occasions for candidate PSSCH transmissions with corresponding PSFCH reception occasions as
determined in clause 16.5.1.1, the UE determines a HARQ-ACK codebook only for the PSFCH reception occasion
associated with PSSCH transmissions scheduled by DCI format 3_0 or only for the PSFCH reception occasion
associated with PSSCH transmissions corresponding to a SL configured grant according to corresponding set ஺ of
occasions, where a value of a counter SAI in DCI format 3_0 is according to Table 16.5.2.1-1. Otherwise, the
procedures in clause 16.5.1.1 and in clause 16.5.1.2 for a HARQ-ACK codebook determination apply.

For a SL BWP on a serving cell and an active UL BWP on the primary cell, as described in clause 12, a UE
determines a set ஺ of occasions for candidate PSSCH transmissions with corresponding PSFCH reception occasions
for which the UE can multiplex corresponding HARQ-ACK information in a PUCCH transmission in slot ௎ . The
determination is based on:
a) a set of slot timing values +ଵ associated with the SL BWP where +ଵ is provided by sl-PSFCH-ToPUCCH for
DCI format 3_0 or by sl-PSFCH-ToPUCCH-CG-Type1
b) the ratio 2ఓSLିఓUL between the sidelink SCS configuration SL and the uplink SCS configuration ୙୐ provided by
subcarrierSpacing in BWP-Sidelink and BWP-Uplink for the SL BWP and the active UL BWP, respectively
c) a set of sidelink resource pool bitmaps
d) a value of a period of PSFCH transmission occasion resources for each sidelink resource pool provided by a
respective sl-PSFCH-Period
For the set of slot timing values +ଵ , the UE determines a set ஺ of occasions for candidate PSSCH transmissions with
corresponding PSFCH reception occasions according to the following pseudo-code.
Set . = 0 - index of occasion for candidate PSSCH transmissions with corresponding PSFCH reception occasions
Set ஺ = ∅
Set C ଵ to the cardinality of set ଵ
Set = 0 – index of slot timing values ଵ ௞ , in descending order of the slot timing values, in set ଵ
,
Set ௉ௌி஼ு to the value of the period of PSFCH transmission occasion resources for the sidelink resource pool
while < C ଵ
if
௎ − ଵ ௞ + 1,
,
2ఓULିఓSL , 1 = 0
Set
ௌ = 0 – index of a SL slot within an UL slot
ETSI
while
ௌ < 2ఓSLିఓUL , 1
if slot
௎ starts at a same time as or after a slot for an active UL BWP change on the PCell and slot

௎ − ଵ ௞ ⋅ 2ఓSLିఓUL +
ௌ is before the slot for the active UL BWP change on the PCell
,

ௌ =
ௌ + 1;
else
if slot
௎ − ଵ ௞ ⋅ 2ఓSLିఓUL +
ௌ belongs to the sidelink resource pool and includes PSFCH resources
,
as indicated by a sidelink resource pool bitmap and sl-PSFCH-Period, where ଵ ௞ is the k-th slot timing
,
value in set ଵ
Set
ி = 0 – index of a SL slot within an PSFCH period
while
ி < ௉ௌி஼ு
஺ = ஺ ∪ ;
= + 1;

ி =
ி + 1 ;
end while
end if

ܵ =
ܵ + 1;
end if
end while
end if
= + 1;
end while
The cardinality of the set ஺ defines a total number of occasions for candidate PSSCH transmissions with
corresponding PSFCH reception occasions corresponding to the HARQ-ACK information bits. A UE determines
଴஺஼௄ , ଵ஺஼௄ , … , ைಲ಴಼ ିଵ HARQ-ACK information bits, for a total number of ACK HARQ-ACK information bits as
஺஼௄
௝஺஼௄ = HARQ-ACK information bit for candidate PSSCH transmission with index with corresponding PSFCH
reception, for 0 ≤ < , as described in clause 16.5. If the UE does not transmit a PSSCH in an occasion for
candidate PSSCH transmission with corresponding PSFCH reception occasion, due to the UE not detecting a
corresponding DCI format 3_0, the UE generates a NACK value for the occasion for candidate PSSCH transmission
with corresponding PSFCH reception occasion.
If ACK ≤ 11, the UE determines a number of HARQ-ACK information bits

ୌ୅ୖ୕ି୅େ୏ for obtaining a transmission
power for a PUCCH, as described in clause 7.2.1, as
HARQ-ACK = ∑୑ିଵ ୰ୣୡୣ୧୴ୣୢ where received is a number of
୫ୀ଴ ୫ ௠
HARQ-ACK information bits determined for corresponding PSSCH transmissions with corresponding PSFCH
reception occasions in PSFCH reception occasion .

scheduled by a DCI format without an SAI field, then
- if the UE
- has not received any PDCCH with a DCI format 3_0 scheduling PSSCH transmissions with corresponding
PSFCH reception occasions that the UE transmits corresponding HARQ-ACK information in the PUSCH,
based on a value of a respective PSFCH-to-HARQ_feedback timing indicator field in a DCI format
ETSI
scheduling the PSSCH transmissions or on the value of PSFCH-to-HARQ feedback timing indicator field in
a DCI format 3_0 activating a SL configured grant Type 2 transmission, or
- has not been provided PSSCH resources with corresponding PSFCH reception occasions that the UE
transmits corresponding HARQ-ACK information based on the value of sl-PSFCH-ToPUCCH-CG-Type1 for
a SL configured grant Type 1, in any of the set ஺ of occasions for candidate PSSCH transmissions with
corresponding PSFCH reception occasions, as described in clause 16.5.1.1,
the UE does not multiplex HARQ-ACK information in the PUSCH transmission;
- else the UE generates the HARQ-ACK codebook as described in clause 16.5.1.1, unless the UE generates
HARQ-ACK information only for
- PSFCH reception occasions associated with PSSCH transmissions corresponding to a SL configured grant, or
- PSFCH reception occasions associated with PSSCH transmissions that are scheduled by DCI format 3_0 with
a counter SAI field value of 1 in the set ஺ of occasions for candidate PSSCH transmissions with
corresponding PSFCH reception occasions,
in which case the UE generates HARQ-ACK information only for the PSFCH reception occasions as described
in clause 16.5.1.
A UE sets to NACK value in the HARQ-ACK codebook any HARQ-ACK information corresponding to PSFCH
reception occasions associated with PSSCH transmissions scheduled by a DCI format 3_0 that the UE detects in a
PDCCH monitoring occasion that starts after a PDCCH monitoring occasion where the UE detects a DCI format
scheduling the PUSCH transmission.
a SAI field, the UE generates the HARQ-ACK codebook as described in clause 16.5.1.1 when a value of the SAI field
SAI = 1. The UE does not generate a HARQ-ACK codebook for multiplexing in the PUSCH
UL
in the DCI format is ்ି
transmission when ்ିSAI = 0 unless the UE generates HARQ-ACK information only for
UL
- PSFCH reception occasions associated with PSSCH transmissions corresponding to a SL configured grant, or
- PSFCH reception occasions associated with PSSCH transmissions that are scheduled by a DCI format 3_0 with a
counter SAI field value of 1 in the set ஺ of occasions for candidate PSSCH transmissions with corresponding
PSFCH reception occasions as described in clause 16.5.1.
UL
்ି SAI = 0 if the SAI field in the DCI format is set to '0'; otherwise, ்ି
UL
SAI = 1.

This clause applies if the UE is configured with pdsch-HARQ-ACK-Codebook = dynamic.

A UE determines monitoring occasions for PDCCH with DCI format 3_0 for scheduling PSSCH transmissions with
associated PSFCH reception occasions on an active DL BWP of a serving cell , as described in clause 10.1, and for
which the UE transmits HARQ-ACK information in a same PUCCH in slot
based on
- PSFCH-to-HARQ_feedback timing indicator field values, or a value provided by sl-PSFCH-ToPUCCH-CG-

Type1, for PUCCH transmission with HARQ-ACK information in slot
in response to PSFCH receptions;
- time gap field in DCI format 3_0 for scheduling PSSCH transmissions with associated PSFCH receptions;
- time resource assignment in DCI format 3_0 for scheduling PSSCH transmissions with associated PSFCH
receptions;
- a set of configured sidelink resource pool bitmaps;
- a value of a period of PSFCH resources provided in sl-PSFCH-Period;
- a value of a minimum time gap provided in sl-MinTimeGapPSFCH.
ETSI
The set of PDCCH monitoring occasions for DCI format 3_0 for scheduling PSSCH transmissions with associated
PSFCH reception occasions is defined as the PDCCH monitoring occasions in the active DL BWP of the configured
serving cell, indexed in ascending order of start time of the associated search space sets. The cardinality of the set of
PDCCH monitoring occasions defines a total number of PDCCH monitoring occasions.
A value of a counter sidelink assignment indicator (SAI) field in DCI format 3_0 denotes an accumulative number of
PDCCH monitoring occasions where PSSCH transmissions with associated PSFCH receptions are scheduled, up to a
current PDCCH monitoring occasion, in ascending order of PDCCH monitoring occasion index , where 0 ≤ < .
SL
Denote by ஼ି SAI,௠ the value of the counter SAI in DCI format 3_0 in PDCCH monitoring occasion according to
Table 16.5.2.1-1.
If the UE transmits HARQ-ACK information in a PUCCH in slot

, the UE determines the ଴஺஼௄ , ଵ஺஼௄ , … , ை஺஼௄
ಲ಴಼ ିଵ , for
a total number of ୅େ୏ HARQ-ACK information bits, according to the following pseudo-code:
Set = 0 – PDCCH with DCI format 3_0 monitoring occasion index: lower index corresponds to earlier PDCCH
with DCI format 3_0 monitoring occasion
Set = 0
Set ௧௘௠௣ =0
Set ௦ = ∅
Set to the number of PDCCH monitoring occasions
while <
if PDCCH monitoring occasion is before an active UL BWP change on the PCell
= ;
else
if there is a PSFCH reception occasion associated with a PSSCH transmission scheduled by a DCI format
in PDCCH monitoring occasion
SL
if ஼ି SAI,௠≤ ௧௘௠௣
= + 1;
end if
௧௘௠௣ = ஼ି
SL
SAI,௠
஺஼௄
ೄಽ = HARQ-ACK information bit
ସ௝ା௏಴షೄಲ಺ ,೘ ିଵ
௦ = ௦ ∪ 4 + ஼ି
SL
SAI,௠ − 1
end if
end if
= + 1;
end while
஺஼௄ = 4 ⋅ + ௧௘௠௣
௜஺஼௄ = for any ∈ 0,1, … , ஺஼௄ − 1\௦
if a SL configured grant Type 1 is configured for a UE, or a SL configured grant Type 2 is configured and activated
for a UE, and the SL configured grant provides a grant for PSSCH transmissions with PSFCH reception occasions in
a slot
− ଵ , where ଵ is the PSFCH-to-HARQ-feedback timing value for the SL configured grant
ETSI
஺஼௄ = ஺஼௄ + 1;
஺஼௄
ைಲ಴಼ ିଵ =
HARQ-ACK information bit associated with the PSFCH reception occasions associated with the
PSSCH transmissions scheduled by the SL configured grant
end if
If ACK ≤ 11, the UE determines a number of HARQ-ACK information bits

ୌ୅ୖ୕ି୅େ୏ for obtaining a transmission
power for a PUCCH, as described in clause 7.2.1, as
୑ିଵ
nHARQ-ACK = SL
SAI ,୫last − SAI mod 4 + ୫୰ୣୡୣ୧୴ୣୢ + େୋ
୫ୀ଴
where
- SL
SAI, is a value of a counter SAI field in a last DCI format 3_0 scheduling PSSCH transmissions associated
௠last
with PSFCH reception occasions that the UE detects within the PDCCH monitoring occasions
- SL
SAI, = 0 if the UE does not detect any DCI format 3_0 scheduling PSSCH transmissions associated with
௠last
PSFCH reception occasions in any of the PDCCH monitoring occasions
- SAI is a total number of DCI format 3_0, scheduling PSSCH transmissions associated with PSFCH reception
occasions, that the UE detects within the PDCCH monitoring occasions. SAI = 0 if the UE does not detect
any DCI format 3_0 scheduling PSSCH transmissions with associated PSFCH reception occasions in any of the
- received
௠ is a number of DCI format 3_0 scheduling PSSCH transmissions with associated PSFCH reception
occasions that the UE detects in PDCCH monitoring occasion
- CG is a number of SL configured grants for which the UE transmits corresponding HARQ-ACK information in
a same PUCCH as for HARQ-ACK information corresponding to PSFCH reception occasions within the
Table 16.5.2.1-1: Value of counter SAI in DCI format 3_0

Number of PDCCH monitoring occasions in which DCI format 3_0
SAI
ࢂSL
࡯ିࡿAI scheduling PSSCH transmissions with corresponding PSFCH reception
occasions is present, denoted as ࢅ and ࢅ ≥ ૚
MSB, LSB
0,0 1 ܻ − 1݉‫݀݋‬4 + 1 = 1
0,1 2 ܻ − 1݉‫݀݋‬4 + 1 = 2
1,0 3 ܻ − 1݉‫݀݋‬4 + 1 = 3
1,1 4 ܻ − 1݉‫݀݋‬4 + 1 = 4

scheduled by a DCI format without an SAI field, then
- if the UE
- has not received any PDCCH within the monitoring occasions for DCI format 3_0 for scheduling PSSCH
with corresponding PSFCH reception occasions on any serving cell, and
- does not have HARQ-ACK information in response to a PSSCH transmission with corresponding PSFCH
reception occasions associated with a SL configured grant to multiplex in the PUSCH, as described in clause
16.5.2.1,
the UE does not multiplex HARQ-ACK information in the PUSCH transmission;
- else, the UE generates and multiplexes in the PUSCH transmission the HARQ-ACK codebook as described in
clause 16.5.2.1.
ETSI
a SAI field, the UE generates the HARQ-ACK codebook as described in clause 16.5.2.1, with the following
modifications:
- For the pseudo-code for the HARQ-ACK codebook generation in clause 16.5.2.1, after the completion of the
loop, the UE sets ௧௘௠௣ = SAI
UL where UL is the value of the SAI field in the DCI format according to Table
SAI
16.5.2.2-1.
If a UE
- UL
is scheduled for a PUSCH transmission by a DCI format that includes a SAI field with value T-SAI = 4, and
- has not received any PDCCH within the monitoring occasions for PDCCH with DCI format 3_0 for scheduling
PSSCH with corresponding PSFCH reception occasions on a serving cell, and
- does not have HARQ-ACK information in response to PSFCH reception occasions associated with a SL
configured grant to multiplex in the PUSCH, as described in clause 16.5.2.1,
the UE does not multiplex HARQ-ACK information in the PUSCH transmission.
Table 16.5.2.2-1: Value of SAI

Number of PDCCH monitoring occasions in which DCI format 3_0
SAI
ࢂUL
T-SAI scheduling PSSCH transmissions with corresponding PSFCH reception
occasions is present, denoted as ࢄ and ࢄ ≥ ૚
MSB, LSB
0,0 1 ܺ − 1݉‫݀݋‬4 + 1 = 1
0,1 2 ܺ − 1݉‫݀݋‬4 + 1 = 2
1,0 3 ܺ − 1݉‫݀݋‬4 + 1 = 3
1,1 4 ܺ − 1݉‫݀݋‬4 + 1 = 4
16.6 UE procedure for LTE sidelink transmission

If the UE detects a DCI format 3_1 with CRC scrambled by SL Semi-Persistent Scheduling V-RNTI in slot
, the DCI
format 3_1 activates or releases an LTE sidelink SPS configuration that is indicated by a SL SPS configuration index
field [5, TS 38.212]. If the DCI format 3_1 activates an SL SPS configuration, the UE procedure for transmitting a
PSCCH and a PSSCH is as described in [13, TS 36.213] except that a transmission starts no earlier than ஽஼ூ − ౐ఽ ×
ே
ଶ
େ × 10 + ! + 4 + ms, where ஽஼ூ is a start time of slot
, ்஺ and ஼ are defined in [4, TS 38.211], ! is a value
ଷ
indicated by a Timing offset field in DCI format 3_1, and is a value indicated by SL index field in DCI format 3_1 if
the SL index field is present; otherwise, = 0.
16.7 Operation for in-device coexistence

If a UE would transmit or receive a first channel/signal using E-UTRA radio access and a second channel/signal using
NR radio access, when
- the first channel/signal and the second channel/signal are time-division multiplexed, and
- the UE knows the frame indexes of the first channel/signal and the frame indexes of the second channel/signal,
the UE transmits or receives each channel/signal so that the subframe boundary of the second channel/signal is aligned
with the subframe boundary of the first channel/signal where the subframe boundary alignment is achieved by UE
implementation means.
ETSI
Annex A:
Change history
Date TSG # TSG Doc. CR Rev Cat Subject/Comment New

version
2017-04 RAN1#89 R1-1707925 Draft skeleton 0.0.0
2017-07 AH_NR2 R1-1712015 Inclusion of agreements until RAN1-adhoc#2 0.0.1
2017-08 RAN1#90 R1-1714553 Inclusion of agreements on CA and first revisions 0.0.2
2017-08 RAN1#90 R1-1714565 Second revisions 0.0.3
2017-08 RAN1#90 R1-1714658 Endorsed by RAN1#90 0.1.0
2017-08 RAN1#90 R1-1715323 Inclusion of agreements from RAN1#90 0.1.1
2017-08 RAN1#90 R1-1715330 Updated editor's version 0.1.2
2017-09 RAN#77 RP-171995 For information to plenary 1.0.0
2017-09 RAN1#90bi R1-1716929 1.0.1
Inclusion of agreements until RAN1-adhoc#3
s
2017-10 RAN1#90bi R1-1719107 Endorsed by RAN1#90bis 1.1.0
s
2017-11 RAN1#90bi R1-1719226 1.1.1
Inclusion of agreements from RAN1#90bis
s
2017-11 RAN1#90bi R1-1719243 1.1.2
Updated editor's version
s
2017-11 RAN1#90bi R1-1721050 Endorsed by RAN1#90bis 1.2.0
s
2017-12 RAN1#91 R1-1721343 Inclusion of agreements from RAN1#91 1.3.0
2017-12 RAN#78 RP-172703 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 NR ad-hoc 1801 and RAN1#92 meeting 15.1.0
agreements
2018-06 RAN#80 RP-181172 0002 1 F CR to TS 38.213 capturing the RAN1#92bis and RAN1#93 15.2.0
meeting agreements and aligning higher layer parameters with
TS 38.331
2018-09 RAN#81 RP-181789 0005 - F CR to 38.213 capturing the RAN1#94 meeting agreements 15.3.0
2018-09 RAN#81 RP-182071 0006 - C Support maximum 8 SS/PBCH blocks for unpaired spectrum 15.3.0
beyond 2.4GHz
2018-12 RAN#82 RP-182523 0007 2 F Combined CR of all essential corrections to 38.213 from 15.4.0
RAN1#94bis and RAN1#95.
2019-03 RAN#83 RP-190449 0009 - F Correction on search space sharing 15.5.0
2019-03 RAN#83 RP-190449 0010 - F CR on timing adjustment indicator 15.5.0
2019-03 RAN#83 RP-190449 0011 - F CR on SSB-RO association 15.5.0
2019-03 RAN#83 RP-190449 0012 - F Removal of CSI request in RAR grant 15.5.0
2019-03 RAN#83 RP-190449 0014 - F Correction to dynamic HARQ codebook in NR 15.5.0
2019-03 RAN#83 RP-190449 0015 1 F Correcttions to TS 38.213 15.5.0
2019-03 RAN#83 RP-190449 0016 - F CR on simultaneous active BWP switching across carriers 15.5.0
2019-03 RAN#83 RP-190449 0017 - F CR on using CORESET#0 in dedicated DL BWP 15.5.0
2019-03 RAN#83 RP-190449 0018 - F PDCCH monitoring for overlapped CORESETs 15.5.0
2019-03 RAN#83 RP-190449 0019 - F Correction to last PUCCH resource set configuration 15.5.0
2019-03 RAN#83 RP-190449 0020 - F Correction on physical downlink control channel 15.5.0
2019-03 RAN#83 RP-190449 0021 - F Correction to align RAN1 and RAN4 specifications for EN-DC 15.5.0
power control
2019-03 RAN#83 RP-190449 0022 - F (Late Drop) CR on PRACH Power Ramping Counter 15.5.0
Suspension
2019-03 RAN#83 RP-190449 0023 - F QCL properties of Msg4 in CONNECTED Mode 15.5.0
2019-03 RAN#83 RP-190449 0024 - F CR on latency after gNB response for recovery 15.5.0
2019-03 RAN#83 RP-190449 0025 - F Clarifying DL reception and UL transmision related restrictions 15.5.0
2019-03 RAN#83 RP-190449 0026 - F CR on QCL assumption for receiving PDCCH for RAR 15.5.0
2019-03 RAN#83 RP-190449 0027 - F CR on identifying transmission occasion after resetting a PC 15.5.0
closed loop
2019-03 RAN#83 RP-190449 0028 - F CR on overlapping of CSI and PUSCH with slot aggregation 15.5.0
2019-03 RAN#83 RP-190449 0029 - F Correction on PHR timing for configured grant 15.5.0
2019-03 RAN#83 RP-190449 0030 - F CR on QCL assumption for a CORESET other than 0 15.5.0
2019-03 RAN#83 RP-190449 0031 - F Correction on DCI format 2_3 for SUL cell in TS 38.213 15.5.0
2019-03 RAN#83 RP-190449 0032 - F Correction to support FR1 extension to 7.125 GHz 15.5.0
2019-03 RAN#83 RP-190449 0033 - F CR on UE procedure for reporting multiple UCI types 15.5.0
2019-03 RAN#83 RP-190449 0034 - F Correction to transmission timing adjustments in TS 38.213 15.5.0
2019-06 RAN#84 RP-191283 0035 - F CR on missing case for DCI format 1_1 with CS-RNTI 15.6.0
2019-06 RAN#84 RP-191283 0036 1 F CR on the determination of the minimum number of PRBs for 15.6.0
PUCCH transmission
ETSI
2019-06 RAN#84 RP-191283 0037 - F CR on PHR determination and transmission 15.6.0

2019-06 RAN#84 RP-191283 0038 4 F Corrections to 38.213 including alignment of terminology 15.6.0
across specifications
2019-06 RAN#84 RP-191283 0039 1 F Correction on PUSCH power scaling 15.6.0
2019-06 RAN#84 RP-191283 0040 - F Correction on PDCCH monitoring 15.6.0
2019-06 RAN#84 RP-191283 0041 - F Correction on CRC assumption for multi-CSI resource 15.6.0
selection and CSI report(s) selection
2019-06 RAN#84 RP-191283 0042 - F Clarification of reference to PDSCH processing capability 1 in 15.6.0
TS 38.213
2019-06 RAN#84 RP-191283 0043 - F Correction on the timeline condition of multiplexing two HARQ- 15.6.0
ACK information in one slot
2019-06 RAN#84 RP-191283 0044 - F CR on Type-1 HARQ-ACK codebook determination 15.6.0
2019-06 RAN#84 RP-191283 0045 - F Correction on PHR in EN-DC 15.6.0
2019-06 RAN#84 RP-191283 0046 - F CR to 38.213 on deactivation timing for ScellDeactivationTimer 15.6.0
2019-06 RAN#84 RP-191283 0047 - F CR on single transmission timing for synchronous intra-band 15.6.0
EN-DC
2019-06 RAN#84 RP-191283 0048 - F CR on PDCCH Monitoring for NR-DC 15.6.0
2019-06 RAN#84 RP-191283 0049 - F CR on Timing for MAC CE Applicability 15.6.0
2019-09 RAN#85 RP-191942 0051 - F Correction on RA procedure triggered by higher layers 15.7.0
2019-09 RAN#85 RP-191942 0052 1 F CR on UE procedure for reporting multiple UCI types 15.7.0
2019-09 RAN#85 RP-191942 0053 - F CR to 38.213 fix to HARQ-ACK Type-1 codebook pseudo- 15.7.0
code
2019-09 RAN#85 RP-191942 0054 - F CR to 38.213 on clarification of the RNTI used for scrambling a 15.7.0
PUSCH transmission scheduled by RAR UL grant
across specifications in RAN1#98
2019-09 RAN#85 RP-191942 0056 - F Correction on intra-band EN-DC with single TAG 15.7.0
2019-09 RAN#85 RP-191942 0057 - F Correction on PHR in EN-DC/NE-DC/NR-CA 15.7.0
2019-09 RAN#85 RP-191942 0058 - F Correction on the time gap definition 15.7.0
2019-09 RAN#85 RP-191942 0059 - F Correction on slot configuration 15.7.0
2019-09 RAN#85 RP-191942 0060 - F CR to 38.213 on PUCCH configuration for NR-DC 15.7.0
2019-09 RAN#85 RP-191942 0061 - F Correction on PUCCH power control 15.7.0
2019-12 RAN#86 RP-192626 0062 1 F CR on beta_offset values for UCI reporting in PUSCH 15.8.0
2019-12 RAN#86 RP-192626 0063 - F Correction on RACH occasion 15.8.0
2019-12 RAN#86 RP-192626 0064 - F Correction on HARQ-ACK transmission with BWP change 15.8.0
2019-12 RAN#86 RP-192626 0065 - F CR on slot configuration regarding PUSCH scheduled by RAR 15.8.0
2019-12 RAN#86 RP-192626 0066 - F Correction on power control for NE-DC 15.8.0
2019-12 RAN#86 RP-192626 0067 - F Correction on time gap definition for HARQ-ACK transmission 15.8.0
2019-12 RAN#86 RP-192626 0068 - F Correction on time gap definition for random access procedure 15.8.0
across specifications in RAN1#98bis and RAN1#99
2019-12 RAN#86 RP-193121 0070 1 B Introduction of two-step RACH in NR 16.0.0
2019-12 RAN#86 RP-193221 0071 2 B Introduction of shared spectrum channel access 16.0.0
2019-12 RAN#86 RP-193123 0072 1 B Introduction of integrated access and backhaul in NR 16.0.0
2019-12 RAN#86 RP-193222 0073 2 B Introduction of Industrial IoT 16.0.0
2019-12 RAN#86 RP-193125 0074 1 B Introduction of Ultra Reliable Low Latency Communications 16.0.0
Enhancements
2019-12 RAN#86 RP-193127 0075 1 B Introduction of MIMO enhancements in NR 16.0.0
2019-12 RAN#86 RP-193128 0076 1 B Introduction of UE power savings 16.0.0
2019-12 RAN#86 RP-193131 0077 1 B Introduction of NR-DC in same Frequency Range and of 16.0.0
Cross-carrier Scheduling with Different Numerologies
2019-12 RAN#86 RP-193132 0078 1 B Introduction of multiple LTE CRS rate matching patterns 16.0.0
2019-12 RAN#86 RP-193124 0079 1 B Introduction of V2X in NR 16.0.0
2019-12 RAN#86 RP-193129 0080 1 B Introduction of positioning support in NR 16.0.0
ETSI
2019-12 RAN#86 RP-193223 0081 2 B Introduction of mobility enhancements in NR 16.0.0
2020-03 RAN#87-e RP-200184 0085 - F Corrections on two-step RACH 16.1.0
2020-03 RAN#87-e RP-200194 0086 - F Corrections on NR-DC and on Cross-carrier Scheduling with 16.1.0
Different Numerologies
2020-03 RAN#87-e RP-200186 0087 - F Corrections on integrated access and backhaul 16.1.0
2020-03 RAN#87-e RP-200189 0088 - F Corrections on Industrial IoT 16.1.0
2020-03 RAN#87-e RP-200190 0089 - F Corrections on MIMO enhancements 16.1.0
2020-03 RAN#87-e RP-200193 0090 - F Corrections on Mobility Enhancements 16.1.0
2020-03 RAN#87-e RP-200185 0091 - F Corrections on shared spectrum channel access 16.1.0
2020-03 RAN#87-e RP-200192 0092 - F Corrections on Positioning 16.1.0
2020-03 RAN#87-e RP-200187 0093 - F Corrections on Sidelink 16.1.0
2020-03 RAN#87-e RP-200191 0094 - F Corrections on UE power savings 16.1.0
2020-03 RAN#87-e RP-200188 0095 - F Corrections on Ultra Reliable Low Latency Communications 16.1.0
Enhancements
2020-03 RAN#87-e RP-200195 0097 - F Introduction of half-duplex operation in CA with unpaired 16.1.0
spectrum
2020-03 RAN#87-e RP-200447 0098 - A Corrections to 38.213 including alignment of terminology 16.1.0
across specifications in RAN1#100-e
2020-06 RAN#88-e RP-200683 0102 - A Correction on PDCCH Blind Detection for NR-DC 16.2.0
2020-06 RAN#88-e RP-200688 0103 1 F Corrections on integrated access and backhaul 16.2.0
2020-06 RAN#88-e RP-200690 0104 1 F Corrections on Ultra Reliable Low Latency Communications 16.2.0
Enhancements
2020-06 RAN#88-e RP-200693 0105 1 F Corrections on UE power savings 16.2.0
2020-06 RAN#88-e RP-200689 0106 1 F Corrections on Sidelink 16.2.0
2020-06 RAN#88-e RP-200694 0107 1 F Corrections on Positioning 16.2.0
2020-06 RAN#88-e RP-200687 0108 1 F Corrections on shared spectrum channel access 16.2.0
2020-06 RAN#88-e RP-200692 0109 1 F Corrections on MIMO enhancements 16.2.0
2020-06 RAN#88-e RP-200691 0110 1 F Corrections on Industrial IoT 16.2.0
2020-06 RAN#88-e RP-200696 0111 1 F Corrections on NR-DC and on Cross-carrier Scheduling with 16.2.0
Different Numerologies
2020-06 RAN#88-e RP-200686 0112 1 F Corrections on two-step RACH 16.2.0
2020-06 RAN#88-e RP-200697 0113 1 F Corrections on half-duplex operation in CA with unpaired 16.2.0
spectrum
2020-06 RAN#88-e RP-200705 0114 - B Introduction of UL transmission switching 16.2.0
2020-06 RAN#88-e RP-200695 0115 - F Corrections on Mobility Enhancements 16.2.0
2020-06 RAN#88-e RP-201349 0117 1 A Extending 8 SSB support to the newly introduced 30 kHz Case 16.2.0
C SSB pattern on band n40
2020-09 RAN#89-e RP-201803 0119 - A Correction on the definition for timeline condition 16.3.0
2020-09 RAN#89-e RP-201803 0120 - F Correction for PUCCH repetition transmission 16.3.0
2020-09 RAN#89-e RP-201814 0121 - F CR on determination of the number of RS for RLM 16.3.0
2020-09 RAN#89-e RP-201803 0123 - A CR on determining P0 for a PUSCH retransmission 16.3.0

corresponding to a RAR UL grant in TS 38.213
ETSI
2020-09 RAN#89-e RP-201803 0125 - F PRACH power ramping suspension 16.3.0
2020-09 RAN#89-e RP-201806 0126 - F Clarify starting slot within DCI 2_5 indication 16.3.0
2020-09 RAN#89-e RP-201804 0127 - F CR on 2-step RACH for 38.213 16.3.0
2020-09 RAN#89-e RP-201813 0128 - F CR on Power Control for NR-DC 16.3.0
2020-09 RAN#89-e RP-201810 0129 - F Type-3 CSS monitoring with PS-RNTI on primary cell 16.3.0
2020-09 RAN#89-e RP-201812 0131 - F CR on correction on uplink power sharing for DAPS HO 16.3.0
2020-09 RAN#89-e RP-201812 0132 - F CR on correction on PDCCH monitoring for DAPS HO 16.3.0
2020-09 RAN#89-e RP-201813 0133 - F CR to 38.213 on RRC parameter alignment for SCell 16.3.0
dormancy
2020-09 RAN#89-e RP-201813 0134 - F CR to 38.213 on BWP triggering via SCell dormancy indication 16.3.0
2020-09 RAN#89-e RP-201813 0135 - F CR to 38.213 on HARQ-ACK processing timeline for DCI 16.3.0
format 1_1 with Scell dormancy indication without scheduling
PDSCH
2020-09 RAN#89-e RP-201807 0136 - F Corrections on Sidelink 16.3.0
2020-09 RAN#89-e RP-201809 0137 - F Corrections on MIMO enhancements 16.3.0
2020-09 RAN#89-e RP-201805 0138 - F Corrections on shared spectrum channel access 16.3.0
2020-09 RAN#89-e RP-201808 0139 - F Corrections on Ultra Reliable Low Latency Communications 16.3.0
Enhancements
2020-09 RAN#89-e RP-202015 0141 1 A Extending 8 SSB support to the TDD bands with newly 16.3.0
introduced 30 kHz Case C SSB pattern
2020-09 RAN#89-e RP-201847 0142 - A Correction on supplementary uplink in Rel-16 TS 38.213 16.3.0
2020-12 RAN#90-e RP-202379 0144 - A CR on HARQ-ACK Determination for SPS Release 16.4.0
2020-12 RAN#90-e RP-202383 0145 - F Corrections related to sidelink physical layer procedures 16.4.0
2020-12 RAN#90-e RP-202382 0146 - F Clarify DCI Format 2_5 search space sets 16.4.0
2020-12 RAN#90-e RP-202380 0147 - F CR on 2-step RACH for 38.213 16.4.0
2020-12 RAN#90-e RP-202385 0148 - F Correction on UL power control 16.4.0
2020-12 RAN#90-e RP-202388 0149 1 F Correction on uplink transmission cancellation for DAPS 16.4.0
handover
2020-12 RAN#90-e RP-202388 0150 1 F Correction on PUSCH processing capability for DAPS 16.4.0
handover
2020-12 RAN#90-e RP-202388 0151 1 F Correction on intra-frequency DAPS handover 16.4.0
2020-12 RAN#90-e RP-202383 0152 - F Corrections on the use of TDRA and FDRA fields SCI for 16.4.0
Mode 1
2020-12 RAN#90-e RP-202383 0153 - F Corrections for the prioritization between uplink transmission 16.4.0
and sidelink transmission/reception
2020-12 RAN#90-e RP-202383 0154 - F Corrections related to the sidelink slot index 16.4.0
2020-12 RAN#90-e RP-202383 0155 - F Correction on sidelink pathloss calculation for S-SSB power 16.4.0
control
2020-12 RAN#90-e RP-202383 0156 1 F Correction on sidelink TDD configuration for OoC UEs 16.4.0
2020-12 RAN#90-e RP-202379 0158 - A Correction on HARQ-ACK generation for DL transmission with 16.4.0
single TB when multi-TB is configured
2020-12 RAN#90-e RP-202381 0159 - F Miscellaneous corrections on NR unlicensed configured grant 16.4.0
ETSI
2020-12 RAN#90-e RP-202383 0160 - F Introduction of the preparation time for SL retransmissions in 16.4.0
Mode 1
2020-12 RAN#90-e RP-202395 0161 - F Correction on uplink Tx switching 16.4.0
2020-12 RAN#90-e RP-202381 0163 - F Correction of NRU HARQ procedure in the presence of SPS 16.4.0
PDSCH
2020-12 RAN#90-e RP-202381 0165 - F CR to 38.213 on NR-U 2-step RACH PO configuration 16.4.0
2020-12 RAN#90-e RP-202389 0166 - F 38.213 CR for NR-DC power control 16.4.0
2020-12 RAN#90-e RP-202389 0167 - F 38.213 CR Correction on HARQ-ACK codebook for secondary 16.4.0
PUCCH group
2020-12 RAN#90-e RP-202384 0168 - F Correction on Type2 HARQ-ACK codebook construction 16.4.0
2020-12 RAN#90-e RP-202384 0169 - F Correction on UL grant Type 2 PUSCH release for search 16.4.0
space sharing
2020-12 RAN#90-e RP-202384 0170 - F Correction on PDCCH monitoring on cell(s) configured with 16.4.0
Rel-15 PDCCH monitoring capability
2020-12 RAN#90-e RP-202383 0171 - F Correction on periodicity of resource pool bitmap 16.4.0
2020-12 RAN#90-e RP-202383 0172 - F Correction on PSFCH and PSCCH mapping 16.4.0
2020-12 RAN#90-e RP-202385 0173 - F CR on CBRA based BFR 16.4.0
2020-12 RAN#90-e RP-202381 0174 - F CR to 38.213 to correct references to 38.212 for RACH 16.4.0
procedure
2020-12 RAN#90-e RP-202381 0175 - F Correction on remaining channel occupancy assumption 16.4.0
2020-12 RAN#90-e RP-202398 0176 - F Alignment CR for TS 38.213 16.4.0
2020-12 RAN#90-e RP-202389 0177 - F Corrections for SCell dormancy indication 16.4.0
2020-12 RAN#90-e RP-202384 0178 - F CR on handling overlapping PUCCH/PUSCH transmissions 16.4.0

with repetitions and with different priorities
2021-03 RAN#91-e RP-210055 0180 - F Type-1 HARQ-ACK for PDSCH repetition with different SCSs 16.5.0
in DL and UL
2021-03 RAN#91-e RP-210047 0182 - A Correction on the search space configuration of PUCCH-SCell 16.5.0
2021-03 RAN#91-e RP-210055 0183 - F Correction on UCI multiplexing with PUCCH overriding 16.5.0
2021-03 RAN#91-e RP-210048 0184 - F CR on transmission timing adjustment procedure in 38.213 16.5.0
2021-03 RAN#91-e RP-210055 0186 - F Correction for cancellation due to PDSCH/CSI-RS/SFI 16.5.0
2021-03 RAN#91-e RP-210049 0187 - F Correction of Type-3 HARQ-ACK codebook generation for a 16.5.0
PDSCH with one transport block for a configuration with a
maximum number of two TBs
2021-03 RAN#91-e RP-210049 0188 - F Correction of UE reception of DL control when a DCI indicates 16.5.0
a request for a Type-3 HARQ-ACK codebook report without
scheduling PDSCH
2021-03 RAN#91-e RP-210049 0189 - D Correction on PUCCH power control for enhanced Type-2 16.5.0
HARQ-ACK codebook and for Type-3 HARQ-ACK codebook
2021-03 RAN#91-e RP-210052 0190 - F CR on HARQ-ACK 16.5.0
2021-03 RAN#91-e RP-210049 0191 - F Correction on search space set group switching without 16.5.0
channel occupancy duration field
2021-03 RAN#91-e RP-210052 0192 - F Corrections on Scell BFR in Rel-16 16.5.0
2021-03 RAN#91-e RP-210058 0193 - F Correction on uplink Tx switching 16.5.0
2021-03 RAN#91-e RP-210050 0194 - F Corrections related to prioritization between uplink and sidelink 16.5.0
ETSI
2021-03 RAN#91-e RP-210050 0195 - F Determination of indexes for slots for S-SS/PSBCH block 16.5.0
transmission(s)
2021-03 RAN#91-e RP-210050 0196 - F Restrictions of the slots for S-SSB transmission/reception 16.5.0
2021-03 RAN#91-e RP-210051 0197 - F CR on Timing for secondary cell activation / deactivation with 16.5.0
sub-slot PUCCH
2021-03 RAN#91-e RP-210051 0198 - F CR on number of PUCCHs with HARQ-ACK in a slot 16.5.0
2021-03 RAN#91-e RP-210050 0199 1 F Correction of SL HARQ-ACK information reporting to the gNB 16.5.0
in Mode 1
2021-03 RAN#91-e RP-210049 0200 - F Correction on LBT Type and CP Extension Indication for Semi- 16.5.0
Static Channel Occupancy in RAR
2021-03 RAN#91-e RP-210054 0201 - F CR to 38.213 on PRACH handling for NR-DC power control 16.5.0
2021-03 RAN#91-e RP-210054 0202 - F CR to 38.213 on HARQ-ACK priority determination for SCell 16.5.0
dormancy indication
2021-03 RAN#91-e RP-210055 0203 - F 38.213 CR on DCI ordering in a search space set 16.5.0
2021-03 RAN#91-e RP-210051 0204 - F Correction on dci-FormatsExt in section 10.1 in TS 38.213 16.5.0
2021-03 RAN#91-e RP-210051 0205 - F Resolving collision with semi-static DL and SSB symbols 16.5.0
2021-03 RAN#91-e RP-210051 0206 - F Correction on PUCCH resource determination in section 9.2.1 16.5.0
in TS 38.213
2021-03 RAN#91-e RP-210059 0207 - F Editorial corrections for 38.213 16.5.0
2021-03 RAN#91-e RP-210126 0208 - A Resubmission of CR179r1 on Correction on supplementary 16.5.0

uplink in 38.213
2021-06 RAN#92-e RP-211234 0209 - F Correction on multiplexing timeline definition for Type-3 16.6.0
HARQ-ACK codebook
2021-06 RAN#92-e RP-211234 0210 - F Correction on Type-3 HARQ-ACK codebook size ambiguity 16.6.0
2021-06 RAN#92-e RP-211250 0211 - F CR to TS 38.213 on clarifying DAPS HO impact on PUCCH 16.6.0
repetition counting
2021-06 RAN#92-e RP-211235 0212 - F Corrections for the reference signal used for sidelink power 16.6.0
control
2021-06 RAN#92-e RP-211237 0214 - F Corrections for separate HARQ-ACK feedback of multi-TRP 16.6.0
transmission
2021-06 RAN#92-e RP-211240 0215 - F Correction on half-duplex operation in CA with unpaired 16.6.0
spectrum
2021-06 RAN#92-e RP-211239 0216 - F Correction on MR-DC Uplink Power Control in 38.213 16.6.0
2021-06 RAN#92-e RP-211234 0217 - F Correction on MsgA PUSCH validation for semistatic channel 16.6.0
access
2021-06 RAN#92-e RP-211238 0218 - F CR on the number of pathloss estimates maintained by the UE 16.6.0
for SRS for positioning.
2021-06 RAN#92-e RP-211249 0219 - F Conditions for IAB-DU soft resource availability 16.6.0
2021-06 RAN#92-e RP-211235 0220 - F Correction of search space configuration for DCI formats 3_0 16.6.0
and 3_1
2021-06 RAN#92-e RP-211234 0221 - F Correction on SR reporting due to consistent LBT failure 16.6.0
recovery
2021-06 RAN#92-e RP-211236 0222 - F Correction on Prioritization Timeline 16.6.0
2021-06 RAN#92-e RP-211236 0223 - F CR on the configuration for one PUCCH-Config with 16.6.0
subslotLengthForPUCCH-r16
ETSI
2021-06 RAN#92-e RP-211236 0224 - F CR on not supporting Type 1 HARQ-ACK codebook for sub- 16.6.0
slot HARQ-ACK in R16
2021-06 RAN#92-e RP-211236 0225 - F CR on Number of PUCCH resource sets per PUCCH-config 16.6.0
2021-06 RAN#92-e RP-211236 0226 - F Correction on UL cancellation due to dynamic SFI 16.6.0
2021-06 RAN#92-e RP-211233 0228 1 A Rel-15 editorial corrections for TS 38.213 (mirrored to Rel-16) 16.6.0
2021-06 RAN#92-e RP-211243 0229 1 F Rel-16 editorial corrections for TS 38.213 16.6.0
2021-06 RAN#92-e RP-211236 0230 - F Correction on UE procedure for determining physical downlink 16.6.0
control channel assignment for Rel-16 PDCCH monitoring
capability
2021-06 RAN#92-e RP-211235 0232 - F Corrections for the multiplexing SL HARQ-ACK information on 16.6.0
a PUSCH
2021-06 RAN#92-e RP-211237 0233 - F Correction on simultaneous multi-CC TCI indication for 16.6.0
CORESET
2021-06 RAN#92-e RP-211234 0234 - F Correction on HARQ-ACK codebook RRC parameter 16.6.0
2021-06 RAN#92-e RP-211234 0235 - F Initial UL BWP size restriction for NR-U 16.6.0
2021-06 RAN#92-e RP-211235 0236 - F Correction of SL HARQ-ACK reporting when SL feedback is 16.6.0
not used
2021-06 RAN#92-e RP-211235 0237 - F Correction of SL HARQ-ACK reporting on UL for SL CG type 2 16.6.0
2021-06 RAN#92-e RP-211240 0239 - F Correction on UL cancellation due to DCI format 2_0 16.6.0
2021-06 RAN#92-e RP-211240 0240 - F Correction on half-duplex operation in CA with unpaired 16.6.0
spectrum
2021-06 RAN#92-e RP-211236 0241 - F Handling collision between PUCCH/PUSCH and semi-static 16.6.0
DL symbols and SSBs
2021-06 RAN#92-e RP-211236 0242 - F Correction on Type-1 HARQ-ACK codebook 16.6.0
2021-06 RAN#92-e RP-211252 0243 - F Correction on value of 1-bit counter DAI 16.6.0
2021-06 RAN#92-e RP-211236 0244 - F CR on correction for sub-slot based PUCCH 16.6.0
2021-06 RAN#92-e RP-211236 0245 - F CR on clarification for reference point of sub-slot based 16.6.0
PUCCH resource
ETSI
History
Document history
V16.2.0 July 2020 Publication
V16.3.0 November 2020 Publication
V16.4.0 January 2021 Publication
V16.5.0 April 2021 Publication
V16.6.0 August 2021 Publication
ETSI

ETSI TS 138 213: 5G NR Physical Layer Procedures For Control (3GPP TS 38.213 Version 16.6.0 Release 16)

Uploaded by

Copyright:

Available Formats

ETSI TS 138 213: 5G NR Physical Layer Procedures For Control (3GPP TS 38.213 Version 16.6.0 Release 16)

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

ETSI TS 138 213: 5G NR Physical Layer Procedures For Control (3GPP TS 38.213 Version 16.6.0 Release 16)

Uploaded by

Copyright:

Available Formats

ETSI TS 138 213 V16.6.

650 Route des Lucioles

Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C

The present document can be downloaded from:

Intellectual Property Rights

Modal verbs terminology

9.2 UCI reporting in physical uplink control channel ............................................................................................ 79

Annex A: Change history ....................................................................................................................182

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.214: "NR; Physical layer procedures for data"

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

[16] 3GPP TS 38.473: "F1 application protocol (F1AP)"

3 Definitions, symbols and abbreviations

BPRE Bits per resource element

SCG Secondary cell group

4.1 Cell search

- For operation without shared spectrum channel access:

- For carrier frequencies smaller than or equal to 3 GHz, n = 0, 1.

- For carrier frequencies within FR1 larger than 3 GHz, n = 0, 1, 2, 3 .

- For operation without shared spectrum channel access

- For paired spectrum operation

- For unpaired spectrum operation

- For operation with shared spectrum channel access, = 0, 1, 2, 3, 4, 5, 6, 7, 8, 9.

subCarrierSpacingCommon LSB of ssb-SubcarrierOffset ࡺࡽ࡯ࡸ

4.2 Transmission timing adjustments

4.3 Timing for secondary cell activation / deactivation

With reference to slots for PUCCH transmissions each consisting of symbslot

5 Radio link monitoring

L max N LR − RLM NRLM

6 Link recovery procedures

- a same spatial filter as for the last PRACH transmission

- a power determined as described in clause 7.2.1 with qu = 0 , q d = q new , and l = 0

- a same spatial filter as for the last PRACH transmission

A UE can be provided, by schedulingRequestID-BFR-SCell, a configuration for PUCCH transmission with a link

- the UE is provided PUCCH-SpatialRelationInfo for the PUCCH,

- the PUCCH-SCell is included in the SCell(s) indicated by the MAC-CE

7 Uplink Power control

7.1 Physical uplink shared channel

- if ul-FullPowerTransmission in PUSCH-Config is provided, the UE scales PUSCH,௕,௙,௖ ( , , ௗ ,  ) by  where:

- if ul-FullPowerTransmission in PUSCH-Config is set to fullpowerMode2,

- if ul-FullPowerTransmission in PUSCH-Config is set to fullpower,  =1

- PO_PUSCH,b, f ,c ( j) is a parameter composed of the sum of a component PO_NOMINAL_PUSCH,f,c ( j) and a component

PO_UE_PUSCH ,b , f , c (0) = 0 PO_NOMINAL_ PUSCH, f ,c (0) = PO_PRE + Δ PREAMBLE _ Msg 3

where O_PRE is provided by preambleReceivedTargetPower [11, TS 38.321] and ௉ோா஺ெ஻௅ா _ெ௦௚ଷ is

 = 0, O_UE_PUSCH,௕,௙,௖ (0) = 0, and O_NOMINAL_PUSCH,௙,௖ (0) = O_PRE + ெ௦௚஺_௉௎ௌ஼ு ,

- For a PUSCH (re)transmission configured by ConfiguredGrantConfig, j = 1 , PO_NOMINAL_PUSCH, f ,c (1) is

PUSCH,f ,c (1) = PO_NOMINAL_

- If the UE is provided by SRI-PUSCH-PowerControl more than one values of p0-PUSCH-AlphaSetId and

- a first P0-PUSCH-AlphaSet in p0-AlphaSets if a value of the open-loop power control parameter

- For j = 1 , α b , f ,c (1) is provided by alpha obtained from p0-PUSCH-Alpha in ConfiguredGrantConfig

With reference to slots for PUCCH transmissions each consisting of symbslot

- if ul-FullPowerTransmission in PUSCH-Config is provided, the UE scales PUSCH,௕,௙,௖ ( , , ௗ , ) by where:

- if ul-FullPowerTransmission in PUSCH-Config is set to fullpower, =1

where O_PRE is provided by preambleReceivedTargetPower [11, TS 38.321] and ௉ோா஺ெ஻௅ா _ெ௦௚ଷ is

= 0, O_UE_PUSCH,௕,௙,௖ (0) = 0, and O_NOMINAL_PUSCH,௙,௖ (0) = O_PRE + ெ௦௚஺_௉௎ௌ஼ு ,

the UE determines a RS resource index ௗ with a respective PUSCH-PathlossReferenceRS-Id value being

- the PUSCH transmission is scheduled by DCI format 0_0 on serving cell ,

- the PUSCH transmission is scheduled by DCI format 0_0 on serving cell ,