0% found this document useful (0 votes)

155 views213 pages

3GPP TS 38.212

Uploaded by

sumitstop2

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

155 views213 pages

3GPP TS 38.212

Uploaded by

sumitstop2

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

3GPP TS 38.212 V17.5.

0 (2023-03)
Technical Specification
3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
NR;
Multiplexing and channel coding
(Release 17)

The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP..
The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this
Specification.
Specifications and Reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.
Release 17 2 3GPP TS 38.212 V17.5.0 (2023-03)

Keywords
3GPP, New Radio, Layer 1

3GPP

Postal address

3GPP support office address

650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Internet
[Link]

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

The copyright and the foregoing restriction extend to reproduction in all media.

UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
GSM® and the GSM logo are registered and owned by the GSM Association

3GPP
Release 17 3 3GPP TS 38.212 V17.5.0 (2023-03)

Contents
Foreword.............................................................................................................................................................
1 Scope.........................................................................................................................................................
2 References.................................................................................................................................................
3 Definitions, symbols and abbreviations....................................................................................................
3.1 Definitions...........................................................................................................................................................
3.2 Symbols...............................................................................................................................................................
3.3 Abbreviations.......................................................................................................................................................
4 Mapping to physical channels...................................................................................................................
4.1 Uplink..................................................................................................................................................................
4.2 Downlink.............................................................................................................................................................
4.3 Sidelink................................................................................................................................................................
5 General procedures.................................................................................................................................
5.1 CRC calculation.................................................................................................................................................
5.2 Code block segmentation and code block CRC attachment..............................................................................
5.2.1 Polar coding.................................................................................................................................................10
5.2.2 Low density parity check coding.................................................................................................................11
5.3 Channel coding..................................................................................................................................................
5.3.1 Polar coding.................................................................................................................................................13
[Link] Interleaving.............................................................................................................................................14
[Link] Polar encoding........................................................................................................................................15
5.3.2 Low density parity check coding.................................................................................................................19
5.3.3 Channel coding of small block lengths........................................................................................................26
[Link] Encoding of 1-bit information................................................................................................................26
[Link] Encoding of 2-bit information................................................................................................................26
[Link] Encoding of other small block lengths...................................................................................................27
5.4 Rate matching....................................................................................................................................................
5.4.1 Rate matching for Polar code.......................................................................................................................27
[Link] Sub-block interleaving...........................................................................................................................27
[Link] Bit selection............................................................................................................................................29
[Link] Interleaving of coded bits.......................................................................................................................29
5.4.2 Rate matching for LDPC code.....................................................................................................................30
[Link] Bit selection............................................................................................................................................30
[Link] Bit interleaving.......................................................................................................................................33
5.4.3 Rate matching for channel coding of small block lengths...........................................................................34
5.5 Code block concatenation..................................................................................................................................
6 Uplink transport channels and control information................................................................................
6.1 Random access channel.....................................................................................................................................
6.2 Uplink shared channel.......................................................................................................................................
6.2.1 Transport block CRC attachment.................................................................................................................34
6.2.2 LDPC base graph selection..........................................................................................................................35
6.2.3 Code block segmentation and code block CRC attachment........................................................................35
6.2.4 Channel coding of UL-SCH.........................................................................................................................35
6.2.5 Rate matching..............................................................................................................................................35
6.2.6 Code block concatenation............................................................................................................................36
6.2.7 Data and control multiplexing......................................................................................................................36
6.3 Uplink control information................................................................................................................................
6.3.1 Uplink control information on PUCCH.......................................................................................................48
[Link] UCI bit sequence generation..................................................................................................................48
[Link].1 HARQ-ACK/SR only.......................................................................................................................48
[Link].2 CSI only............................................................................................................................................48
[Link].3 HARQ-ACK/SR and CSI.................................................................................................................65
[Link].4 UCI with different priority indexes..................................................................................................66
[Link] Code block segmentation and CRC attachment.....................................................................................66
[Link].1 UCI encoded by Polar code..............................................................................................................66

3GPP
Release 17 4 3GPP TS 38.212 V17.5.0 (2023-03)

[Link].2 UCI encoded by channel coding of small block lengths..................................................................67

[Link] Channel coding of UCI..........................................................................................................................67
[Link].1 UCI encoded by Polar code..............................................................................................................67
[Link].2 UCI encoded by channel coding of small block lengths..................................................................67
[Link] Rate matching.........................................................................................................................................67
[Link].1 UCI encoded by Polar code..............................................................................................................67
[Link].2 UCI encoded by channel coding of small block lengths..................................................................68
[Link].3 UCI with different priority indexes encoded by Polar code.............................................................69
[Link].4 UCI with different priority indexes encoded by channel coding of small block lengths.................69
[Link] Code block concatenation......................................................................................................................69
[Link] Multiplexing of coded UCI bits to PUCCH...........................................................................................70
6.3.2 Uplink control information on PUSCH.......................................................................................................72
[Link] UCI bit sequence generation..................................................................................................................72
[Link].1 HARQ-ACK.....................................................................................................................................72
[Link].2 CSI....................................................................................................................................................73
[Link].3 CG-UCI............................................................................................................................................87
[Link].4 HARQ-ACK and CG-UCI................................................................................................................88
[Link].5 UCI with different priority indexes..................................................................................................88
[Link] Code block segmentation and CRC attachment.....................................................................................90
[Link].1 UCI encoded by Polar code..............................................................................................................90
[Link].2 UCI encoded by channel coding of small block lengths..................................................................90
[Link] Channel coding of UCI..........................................................................................................................91
[Link].1 UCI encoded by Polar code..............................................................................................................91
[Link].2 UCI encoded by channel coding of small block lengths..................................................................91
[Link] Rate matching.........................................................................................................................................91
[Link].1 UCI encoded by Polar code..............................................................................................................91
[Link].1.1 HARQ-ACK...............................................................................................................................91
[Link].1.2 CSI part 1....................................................................................................................................94
[Link].1.3 CSI part 2....................................................................................................................................97
[Link].1.4 CG-UCI.....................................................................................................................................101
[Link].1.5 HARQ-ACK and CG-UCI........................................................................................................102
[Link].1.6 UCI with different priority indexes...........................................................................................103
[Link].2 UCI encoded by channel coding of small block lengths................................................................105
[Link].2.1 HARQ-ACK.............................................................................................................................105
[Link].2.2 CSI part 1..................................................................................................................................105
[Link].2.3 CSI part 2..................................................................................................................................106
[Link].2.4 CG-UCI.....................................................................................................................................106
[Link].2.5 HARQ-ACK and CG-UCI........................................................................................................106
[Link].2.6 UCI with different priority indexes...........................................................................................106
[Link] Code block concatenation....................................................................................................................108
[Link] Multiplexing of coded UCI bits to PUSCH.........................................................................................108
[Link] Multiplexing of coded UCI bits with different priority indexes to PUSCH........................................108
7 Downlink transport channels and control information.........................................................................
7.1 Broadcast channel............................................................................................................................................
7.1.1 PBCH payload generation..........................................................................................................................109
7.1.2 Scrambling.................................................................................................................................................110
7.1.3 Transport block CRC attachment...............................................................................................................111
7.1.4 Channel coding..........................................................................................................................................111
7.1.5 Rate matching............................................................................................................................................111
7.2 Downlink shared channel and paging channel................................................................................................
7.2.1 Transport block CRC attachment...............................................................................................................112
7.2.2 LDPC base graph selection........................................................................................................................112
7.2.3 Code block segmentation and code block CRC attachment......................................................................112
7.2.4 Channel coding..........................................................................................................................................112
7.2.5 Rate matching............................................................................................................................................112
7.2.6 Code block concatenation..........................................................................................................................113
7.3 Downlink control information.........................................................................................................................
7.3.1 DCI formats...............................................................................................................................................113
[Link] DCI size alignment...............................................................................................................................114
[Link].1 DCI size alignment for DCI formats for scheduling of sidelink....................................................117
[Link] DCI formats for scheduling of PUSCH................................................................................................117

3GPP
Release 17 5 3GPP TS 38.212 V17.5.0 (2023-03)

[Link].1 Format 0_0......................................................................................................................................117

[Link].2 Format 0_1......................................................................................................................................121
[Link].3 Format 0_2......................................................................................................................................149
[Link] DCI formats for scheduling of PDSCH................................................................................................158
[Link].1 Format 1_0......................................................................................................................................158
[Link].2 Format 1_1......................................................................................................................................162
[Link].3 Format 1_2......................................................................................................................................179
[Link] DCI formats for other purposes............................................................................................................184
[Link].1 Format 2_0......................................................................................................................................184
[Link].2 Format 2_1......................................................................................................................................185
[Link].3 Format 2_2......................................................................................................................................185
[Link].4 Format 2_3......................................................................................................................................185
[Link].5 Format 2_4......................................................................................................................................186
[Link].6 Format 2_5......................................................................................................................................186
[Link].7 Format 2_6......................................................................................................................................186
[Link].8 Format 2_7......................................................................................................................................187
[Link] DCI formats for scheduling of sidelink................................................................................................187
[Link].1 Format 3_0......................................................................................................................................187
[Link].2 Format 3_1......................................................................................................................................188
[Link] DCI formats for scheduling of MBS....................................................................................................188
[Link].1 Format 4_0......................................................................................................................................188
[Link].2 Format 4_1......................................................................................................................................189
[Link].3 Format 4_2......................................................................................................................................189
7.3.2 CRC attachment.........................................................................................................................................191
7.3.3 Channel coding..........................................................................................................................................192
7.3.4 Rate matching............................................................................................................................................192
8 Sidelink transport channels and control information............................................................................
8.1 Sidelink broadcast channel..............................................................................................................................
8.1.1 (void)..........................................................................................................................................................192
8.2 Sidelink shared channel...................................................................................................................................
8.2.1 Data and control multiplexing....................................................................................................................192
8.3 Sidelink control information on PSCCH.........................................................................................................
8.3.1 1st-stage SCI formats..................................................................................................................................193
[Link] SCI format 1-A.....................................................................................................................................194
8.3.2 CRC attachment.........................................................................................................................................195
8.3.3 Channel coding..........................................................................................................................................195
8.3.4 Rate Matching............................................................................................................................................195
8.4 Sidelink control information on PSSCH.........................................................................................................
8.4.1 2nd-stage SCI formats.................................................................................................................................195
[Link] SCI format 2-A.....................................................................................................................................195
[Link] SCI format 2-B.....................................................................................................................................196
[Link] SCI format 2-C.....................................................................................................................................196
8.4.2 CRC attachment.........................................................................................................................................197
8.4.3 Channel coding..........................................................................................................................................197
8.4.4 Rate Matching............................................................................................................................................198
8.4.5 Multiplexing of coded 2nd-stage SCI bits to PSSCH..................................................................................198

Annex <A> (informative): Change history.................................................................................................199

3GPP
Release 17 6 3GPP TS 38.212 V17.5.0 (2023-03)

Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).

The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:

Version x.y.z

where:

x the first digit:

1 presented to TSG for information;

2 presented to TSG for approval;

3 or greater indicates TSG approved document under change control.

y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.

z the third digit is incremented when editorial only changes have been incorporated in the document.

3GPP
Release 17 7 3GPP TS 38.212 V17.5.0 (2023-03)

1 Scope
The present document specifies the coding, multiplexing and mapping to physical channels for 5G NR.

2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.

- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.

- For a specific reference, subsequent revisions do not apply.

- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as 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.213: "NR; Physical layer procedures for control"

[6] 3GPP TS 38.214: "NR; Physical layer procedures for data"

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

[8] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification"

[9] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification"

[10] 3GPP TS 38.473: "NG-RAN; F1 Application Protocol (F1AP)"

[11] 3GPP TS 36.212: "Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and
channel coding"

[12] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-
Everything (V2X) services"

3 Definitions, symbols and abbreviations

3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A
term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].

3.2 Symbols
For the purposes of the present document, the following symbols apply:

3GPP
Release 17 8 3GPP TS 38.212 V17.5.0 (2023-03)

3.3 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
TR 21.905 [1].

3GPP
Release 17 9 3GPP TS 38.212 V17.5.0 (2023-03)

UE User equipment
UL Uplink
UL-SCH Uplink shared channel
VRB Virtual resource block
ZP CSI-RS Zero power CSI-RS

4 Mapping to physical channels

4.1 Uplink
Table 4.1-1 specifies the mapping of the uplink transport channels to their corresponding physical channels. Table 4.1-2
specifies the mapping of the uplink control channel information to its corresponding physical channel.

Table 4.1-1

TrCH Physical Channel

UL-SCH PUSCH
RACH PRACH

Table 4.1-2

Control information Physical Channel

UCI PUCCH, PUSCH

4.2 Downlink
Table 4.2-1 specifies the mapping of the downlink transport channels to their corresponding physical channels. Table
4.2-2 specifies the mapping of the downlink control channel information to its corresponding physical channel.

Table 4.2-1

TrCH Physical Channel

DL-SCH PDSCH
BCH PBCH
PCH PDSCH

Table 4.2-2

Control information Physical Channel

DCI PDCCH

4.3 Sidelink
Table 4.3-1 specifies the mapping of the sidelink transport channels to their corresponding physical channels. Table 4.3-
2 specifies the mapping of the sidelink control information and sidelink feedback control information to their
corresponding physical channels.

Table 4.3-1

TrCH Physical Channel

SL-SCH PSSCH
SL-BCH PSBCH

3GPP
Release 17 10 3GPP TS 38.212 V17.5.0 (2023-03)

Table 4.3-2

Control information Physical Channel

1st-stage SCI PSCCH
2nd-stage SCI PSSCH
SFCI PSFCH

5 General procedures
Data and control streams from/to MAC layer are encoded /decoded to offer transport and control services over the radio
transmission link. Channel coding scheme is a combination of error detection, error correcting, rate matching,
interleaving and transport channel or control information mapping onto/splitting from physical channels.

5.1 CRC calculation

Denote the input bits to the CRC computation by 0 1 2 3
a , a , a , a , . .. , a
A −1 , and the parity bits by 0 1 2 3 L−1 , p , p , p , p , . .. , p
where A L
is the size of the input sequence and is the number of parity bits. The parity bits are generated by one of
the following cyclic generator polynomials:

- gCRC24A ( D )=[ D 24 + D23+ D18+ D17+ D14 + D11 + D10 + D7 + D6 + D5 + D4 + D3 + D+1 ] for a CRC length
L=24 ;

- gCRC24B ( D )=[ D 24 + D23+ D6 + D5 + D+1 ] for a CRC length L=24 ;

- gCRC24C ( D )=[ D 24+ D 23+ D 21+ D 20+ D 17 + D 15 + D 13 + D 12 + D 8 + D 4 + D 2 + D+1 ] for a CRC length L=24 ;

- gCRC16 ( D ) =[ D16+ D12+ D5 +1 ] for a CRC length L=16 ;

- gCRC11 ( D )=[ D 11 + D 10 + D 9 + D 5 +1 ] for a CRC length L=11 ;

- gCRC6 ( D )=[ D6 + D5 +1 ] for a CRC length L=6 .

The encoding is performed in a systematic form, which means that in GF(2), the polynomial:

a 0 D A +L−1 +a1 D A +L−2 +. . .+a A −1 D L + p0 D L−1 + p1 D L−2 +. ..+ p L−2 D1 + p L−1

.
yields a remainder equal to 0 when divided by the corresponding CRC generator polynomial

The bits after CRC attachment are denoted by

b 0 , b1 , b 2 ,b 3 , .. . , bB−1 , where B= A+ L . The relation between a k and b k
is:

b k =ak for k=0,1,2,..., A−1

b k =p k −A for k= A , A +1, A+2,..., A +L−1 .

5.2 Code block segmentation and code block CRC attachment

5.2.1 Polar coding
The input bit sequence to the code block segmentation is denoted by
a 0 , a1 , a 2 , a3 , . .. , a A −1 , where A> 0 .

if
I seg =1

Number of code blocks: C=2 ;

3GPP
Release 17 11 3GPP TS 38.212 V17.5.0 (2023-03)

else

Number of code blocks:

end if

A '=⌈ A/C ⌉⋅C ;

for i=0 to A '−A−1

a ' i=0 ;

end for

for i= A '− A to A '−1

a ' i=ai−( A '− A )

;

end for

s=0 ;

for r =0 to C−1

for k =0 to A '/ C−1

c rk =a ' s ;

s=s+ 1 ;

end for

c ,c ,c ,c ,...,c
r ( A '/ C−1 ) is used to calculate the CRC parity bits pr 0 , pr 1 , pr 2 , .. . , p r ( L−1 )
The sequence r 0 r 1 r 2 r 3 according to
Clause 5.1 with a generator polynomial of length L .

for k = A '/ C to A '/ C+L−1

c rk = pr ( k − A '/C )
;

end for

The value of A is no larger than 1706.

5.2.2 Low density parity check coding

The input bit sequence to the code block segmentation is denoted by
b 0 , b1 , b 2 ,b 3 , .. . , bB−1 , where B>0 . If B is larger
K
than the maximum code block size cb , segmentation of the input bit sequence is performed and an additional CRC
sequence of L=24 bits is attached to each code block.

For LDPC base graph 1, the maximum code block size is:

-
K cb =8448 .

For LDPC base graph 2, the maximum code block size is:

-
K cb =3840 .

3GPP
Release 17 12 3GPP TS 38.212 V17.5.0 (2023-03)

Total number of code blocks C is determined by:

if
B≤K cb

L=0

Number of code blocks: C=1

B' =B
else

L=24

C=⌈ B/ ( K cb−L ) ⌉
Number of code blocks: .
'
B =B+C⋅L
end if

c r 0 , c r 1 , c r 2 , c r 3 , .. . , cr ( K −1 )
The bits output from code block segmentation are denoted by r , where 0≤r <C is the code
block number, and K r = K is the number of bits for the code block number r .

The number of bits in each code block is calculated as:

K ' =B '/ C ;

For LDPC base graph 1,

K b =22 .

For LDPC base graph 2,

if B>640

K b =10 ;

elseif B>560

K b =9 ;

elseif B>192

K b =8 ;

else

K b =6 ;

end if

Z K ⋅Z ≥K ' , and
find the minimum value of Z in all sets of lifting sizes in Table 5.3.2-1, denoted as c , such that b c
set
K=22 Z c for LDPC base graph 1 and K=10 Z c for LDPC base graph 2;

The bit sequence is calculated as:

s=0 ;

3GPP
Release 17 13 3GPP TS 38.212 V17.5.0 (2023-03)

for r =0 to C−1

for k =0 to K '−L−1

c rk =b s ;

s=s+ 1 ;

end for

if C> 1

c ,c ,c ,c ,...,cr ( K '−L−1 ) p , p , p , .. . , p r ( L−1 )

The sequence r 0 r 1 r 2 r 3 is used to calculate the CRC parity bits r 0 r 1 r 2
according to Clause 5.1 with the generator polynomial gCRC24B ( D ) .

for k =K '−L to K '−1

c rk = pr ( k +L−K ' )
;

end for

end if

for k =K ' to K−1 -- Insertion of filler bits

c rk =< NULL>¿ ¿;

end for

5.3 Channel coding

Usage of coding scheme for the different types of TrCH is shown in table 5.3-1. Usage of coding scheme for the
different control information types is shown in table 5.3-2.

Table 5.3-1: Usage of channel coding scheme for TrCHs

TrCH Coding scheme

UL-SCH
DL-SCH LDPC
PCH
BCH Polar code

Table 5.3-2: Usage of channel coding scheme for control information

Control Information Coding scheme

DCI Polar code
Block code
UCI
Polar code

5.3.1 Polar coding

The bit sequence input for a given code block to channel coding is denoted by
c 0 , c 1 , c 2 , c 3 , .. . , c K −1 , where K is the
d ,d ,d ,...,d N−1 , where N=2n and the value of n is
number of bits to encode. After encoding the bits are denoted by 0 1 2
determined by the following:

Denote by E the rate matching output sequence length as given in Clause 5.4.1;

3GPP
Release 17 14 3GPP TS 38.212 V17.5.0 (2023-03)

( ⌈ log 2 E ⌉−1 )
If E≤( 9/ 8 )⋅2 and K / E< 9/ 16

n1 =⌈log 2 E⌉−1 ;

else

n1 =⌈log 2 E⌉ ;

end if

R min=1/8 ;

n2 =⌈ log 2 ( K / R min ) ⌉
;

n=max { min { n1 , n2 , nmax } , n min }

where
n min=5 .

UE is not expected to be configured with , where

n PC is the number of parity check bits defined in Clause
[Link].

[Link] Interleaving

The bit sequence

c 0 , c 1 , c 2 , c 3 , .. . , c K −1 is interleaved into bit sequence c '0 ,c '1 , c '2 , c '3 , . .. , c' K −1 as follows:
'
c k =c Π (k ) , k=0,1,..., K−1

where the interleaving pattern Π ( k ) is given by the following:

if I IL =0

Π ( k ) =k , k=0,1,..., K−1

else

k =0 ;
max
for m=0 to K IL −1
max max
if Π IL ( m )≥K IL −K

IL ( m ) −( K IL −K )
Π ( k ) =Π max max
;

k =k +1 ;

end if

end for

end if
max max
where Π IL ( m ) is given by Table [Link]-1 and K IL =164 .

3GPP
Release 17 15 3GPP TS 38.212 V17.5.0 (2023-03)

max
Table [Link]-1: Interleaving pattern Π IL ( m )
m Π max
IL ( m )
m Π max
IL ( m )
m Π max
IL ( m )
m Π max
IL ( m )
m Π max
IL ( m )
m Π max
IL ( m )
11 14
0 0 28 67 56 122 84 68 33 38
2 0
11 14
1 2 29 69 57 123 85 73 36 144
3 1
11 14
2 4 30 70 58 126 86 78 44 39
4 2
11 14
3 7 31 71 59 127 87 84 47 145
5 3
11 14
4 9 32 72 60 129 88 90 64 40
6 4
11 14
5 14 33 76 61 132 89 92 74 146
7 5
11 14
6 19 34 77 62 134 90 94 79 41
8 6
11 14
7 20 35 81 63 138 91 96 85 147
9 7
12 14
8 24 36 82 64 139 92 99 97 148
0 8
12 14
9 25 37 83 65 140 93 102 100 149
1 9
12 15
10 26 38 87 66 1 94 105 103 150
2 0
12 15
11 28 39 88 67 3 95 107 117 151
3 1
12 15
12 31 40 89 68 5 96 109 125 152
4 2
12 15
13 34 41 91 69 8 97 112 131 153
5 3
12 15
14 42 42 93 70 10 98 114 136 154
6 4
12 15
15 45 43 95 71 15 99 116 142 155
7 5
10 12 15
16 49 44 98 72 21 121 12 156
0 8 6
10 12 15
17 50 45 101 73 27 124 17 157
1 9 7
10 13 15
18 51 46 104 74 29 128 23 158
2 0 8
10 13 15
19 53 47 106 75 32 130 37 159
3 1 9
10 13 16
20 54 48 108 76 35 133 48 160
4 2 0
10 13 16
21 56 49 110 77 43 135 75 161
5 3 1
10 13 16
22 58 50 111 78 46 141 80 162
6 4 2
10 13 16
23 59 51 113 79 52 6 86 163
7 5 3
10 13
24 61 52 115 80 55 11 137
8 6
10 13
25 62 53 118 81 57 16 143
9 7
11 13
26 65 54 119 82 60 22 13
0 8
11 13
27 66 55 120 83 63 30 18
1 9

[Link] Polar encoding

{ } is given by Table [Link]-1, where 0≤QNi

N −1 N N N
Q 0 max = Q 0 max ,Q 1 max ,. .. , Q N max−1 max
≤N max −1 denotes a
The Polar sequence max

bit index before Polar encoding for

i=0 , 1,. . ., N max −1 and N max =1024 . The Polar sequence N −1
Q0 max is in ascending
order of reliability
W(
N
Q 0 max ) <W (Q N max
1 ) ¿ .. .<W (Q N max
N max −1 ) , where W ( N
Qi max ) denotes the reliability of bit index QiN max
.
N−1
= {Q0N ,Q1N , QN2 , . .. , QNN −1 }
For any code block encoded to N bits, a same Polar sequence Q0 is used. The Polar
N−1 N −1 N max
sequence Q 0 is a subset of Polar sequence Q0 with all elements Qi of values less than N , ordered in
max

ascending order of reliability W ( Q N0 ) <W ( Q1N ) <W ( Q2N )< .. .<W ( Q NN−1 ).
N N−1 N
Denote Q̄ I as a set of bit indices in Polar sequence Q 0 , and Q̄ F as the set of other bit indices in Polar sequence
N N N
Q0N−1 , where Q̄ NI and Q̄ NF are given in Clause [Link], |Q̄ I |=K +n PC , |Q̄ F |=N−|Q̄ I |, and n PC is the number of
parity check bits.

3GPP
Release 17 16 3GPP TS 38.212 V17.5.0 (2023-03)

Denote
G N =( G 2 ) ⊗n
as the n -th Kronecker power of matrix
G 2 , where [ ]
G2=
1 0
1 1 .

For a bit index j with j=0,1,..., N−1 , denote g j as the j -th row of G N and w ( g j ) as the row weight of g j , where
w (gj) g N
|Q N |=n PC . A
is the number of ones in j . Denote the set of bit indices for parity check bits as Q PC , where PC
number of ( PC ) parity check bits are placed in the ( PC )
n PC −n wm n PC −n wm N
least reliable bit indices in Q̄ I . A number of
~N ~N
n wm
PC other parity check bits are placed in the bit indices of minimum row weight in Q I , where Q I denotes the
(|Q̄IN|−n PC ) most reliable bit indices in Q̄ N
I ;
wm
if there are more than n PC bit indices of the same minimum row weight
~N wm wm
in Q I , the n PC other parity check bits are placed in the n PC bit indices of the highest reliability and the minimum row
~N
weight in Q I .

u=[ u0 u1 u 2 . . .u N−1 ]
Generate according to the following:

k =0 ;

if
n PC > 0

y 0 =0 ; y 1 =0 ; y 2 =0 ; y 3 =0 ; y 4 =0 ;

for n=0 to N−1

y t = y 0 ; y 0= y 1 ; y 1= y 2 ; y 2= y 3 ; y 3= y 4 ; y 4= y t ;
N
if n ∈ Q̄ I
N
if n ∈Q PC

un = y 0 ;

else

un =c 'k ;

k =k +1 ;

y 0 = y 0 ⊕u n ;

end if

else

un =0 ;

end if

end for

else

for n=0 to N−1

N
if n ∈ Q̄ I

3GPP
Release 17 17 3GPP TS 38.212 V17.5.0 (2023-03)

un =c 'k ;

k =k +1 ;

else

un =0 ;

end if

end for

end if

d= [ d 0 d 1 d 2 . .. d N−1 ] d=uG N . The encoding is performed in GF(2).

The output after encoding is obtained by

3GPP
Release 17 18 3GPP TS 38.212 V17.5.0 (2023-03)

and its corresponding reliability W ( Qi )

N max−1 N max
Table [Link]-1: Polar sequence Q0

3GPP
Release 17 19 3GPP TS 38.212 V17.5.0 (2023-03)

W ( Qi ) QiN W ( Qi ) QiN W ( Qi ) QiN W ( Qi ) QiN W ( Qi ) QiN W ( Qi ) QiN W ( Qi ) QiN W ( Qi ) QiN

N max max N max max N max max N max max N max max N max max N max max N max max

0 0 128 518 256 94 384 214 512 364 640 414 768 819 896 966
1 1 129 54 257 204 385 309 513 654 641 223 769 814 897 755
2 2 130 83 258 298 386 188 514 659 642 663 770 439 898 859
3 4 131 57 259 400 387 449 515 335 643 692 771 929 899 940
4 8 132 521 260 608 388 217 516 480 644 835 772 490 900 830
5 16 133 112 261 352 389 408 517 315 645 619 773 623 901 911
6 32 134 135 262 325 390 609 518 221 646 472 774 671 902 871
7 3 135 78 263 533 391 596 519 370 647 455 775 739 903 639
8 5 136 289 264 155 392 551 520 613 648 796 776 916 904 888
9 64 137 194 265 210 393 650 521 422 649 809 777 463 905 479
10 9 138 85 266 305 394 229 522 425 650 714 778 843 906 946
11 6 139 276 267 547 395 159 523 451 651 721 779 381 907 750
12 17 140 522 268 300 396 420 524 614 652 837 780 497 908 969
13 10 141 58 269 109 397 310 525 543 653 716 781 930 909 508
14 18 142 168 270 184 398 541 526 235 654 864 782 821 910 861
15 128 143 139 271 534 399 773 527 412 655 810 783 726 911 757
16 12 144 99 272 537 400 610 528 343 656 606 784 961 912 970
17 33 145 86 273 115 401 657 529 372 657 912 785 872 913 919
18 65 146 60 274 167 402 333 530 775 658 722 786 492 914 875
19 20 147 280 275 225 403 119 531 317 659 696 787 631 915 862
20 256 148 89 276 326 404 600 532 222 660 377 788 729 916 758
21 34 149 290 277 306 405 339 533 426 661 435 789 700 917 948
22 24 150 529 278 772 406 218 534 453 662 817 790 443 918 977
23 36 151 524 279 157 407 368 535 237 663 319 791 741 919 923
24 7 152 196 280 656 408 652 536 559 664 621 792 845 920 972
25 129 153 141 281 329 409 230 537 833 665 812 793 920 921 761
26 66 154 101 282 110 410 391 538 804 666 484 794 382 922 877
27 512 155 147 283 117 411 313 539 712 667 430 795 822 923 952
28 11 156 176 284 212 412 450 540 834 668 838 796 851 924 495
29 40 157 142 285 171 413 542 541 661 669 667 797 730 925 703
30 68 158 530 286 776 414 334 542 808 670 488 798 498 926 935
31 130 159 321 287 330 415 233 543 779 671 239 799 880 927 978
32 19 160 31 288 226 416 555 544 617 672 378 800 742 928 883
33 13 161 200 289 549 417 774 545 604 673 459 801 445 929 762
34 48 162 90 290 538 418 175 546 433 674 622 802 471 930 503
35 14 163 545 291 387 419 123 547 720 675 627 803 635 931 925
36 72 164 292 292 308 420 658 548 816 676 437 804 932 932 878
37 257 165 322 293 216 421 612 549 836 677 380 805 687 933 735
38 21 166 532 294 416 422 341 550 347 678 818 806 903 934 993
39 132 167 263 295 271 423 777 551 897 679 461 807 825 935 885
40 35 168 149 296 279 424 220 552 243 680 496 808 500 936 939
41 258 169 102 297 158 425 314 553 662 681 669 809 846 937 994
42 26 170 105 298 337 426 424 554 454 682 679 810 745 938 980
43 513 171 304 299 550 427 395 555 318 683 724 811 826 939 926
44 80 172 296 300 672 428 673 556 675 684 841 812 732 940 764
45 37 173 163 301 118 429 583 557 618 685 629 813 446 941 941
46 25 174 92 302 332 430 355 558 898 686 351 814 962 942 967
47 22 175 47 303 579 431 287 559 781 687 467 815 936 943 886
48 136 176 267 304 540 432 183 560 376 688 438 816 475 944 831
49 260 177 385 305 389 433 234 561 428 689 737 817 853 945 947
50 264 178 546 306 173 434 125 562 665 690 251 818 867 946 507
51 38 179 324 307 121 435 557 563 736 691 462 819 637 947 889
52 514 180 208 308 553 436 660 564 567 692 442 820 907 948 984
53 96 181 386 309 199 437 616 565 840 693 441 821 487 949 751
54 67 182 150 310 784 438 342 566 625 694 469 822 695 950 942
55 41 183 153 311 179 439 316 567 238 695 247 823 746 951 996
56 144 184 165 312 228 440 241 568 359 696 683 824 828 952 971
57 28 185 106 313 338 441 778 569 457 697 842 825 753 953 890
58 69 186 55 314 312 442 563 570 399 698 738 826 854 954 509
59 42 187 328 315 704 443 345 571 787 699 899 827 857 955 949
60 516 188 536 316 390 444 452 572 591 700 670 828 504 956 973
100
61 49 189 577 317 174 445 397 573 678 701 783 829 799 957
0
62 74 190 548 318 554 446 403 574 434 702 849 830 255 958 892
63 272 191 113 319 581 447 207 575 677 703 820 831 964 959 950
64 160 192 154 320 393 448 674 576 349 704 728 832 909 960 863
65 520 193 79 321 283 449 558 577 245 705 928 833 719 961 759
100
66 288 194 269 322 122 450 785 578 458 706 791 834 477 962
8
67 528 195 108 323 448 451 432 579 666 707 367 835 915 963 510
68 192 196 578 324 353 452 357 580 620 708 901 836 638 964 979
69 544 197 224 325 561 453 187 581 363 709 630 837 748 965 953
70 70 198 166 326 203 454 236 582 127 710 685 838 944 966 763
71 44 199 519 327 63 455 664 583 191 711 844 839 869 967 974
72 131 200 552 328 340 456 624 584 782 712 633 840 491 968 954
73 81 201 195 329 394 457 587 585 407 713 711 841 699 969 879
74 50 202 270 330 527 458 780 586 436 714 253 842 754 970 981
75 73 203 641 331 582 459 705 587 626 715 691 843 858 971 982
76 15 204 523 332 556 460 126 588 571 716 824 844 478 972 927
77 320 205 275 333 181 461 242 589 465 717 902 845 968 973 995
78 133 206 580 334 295 462 565 590 681 718 686 846 383 974 765
79 52 207 291 335 285 463 398 591 246 719 740 847 910 975 956
80 23 208 59 336 232 464 346 592 707 720 850 848 815 976 887
81 134 209 169 337 124 465 456 593 350 721 375 849 976 977 985
82 384 210 560 338 205 466 358 594 599 722 444 850 870 978 997
83 76 211 114 339 182 467 405 595 668 723 470 851 917 979 986
84 137 212 277 340 643 468 303 596 790 724 483 852 727 980 943
85 82 213 156 341 562 469 569 597 460 725 415 853 493 981 891

3GPP
Release 17 20 3GPP TS 38.212 V17.5.0 (2023-03)

86 56 214 87 342 286 470 244 598 249 726 485 854 873 982 998
87 27 215 197 343 585 471 595 599 682 727 905 855 701 983 766
88 97 216 116 344 299 472 189 600 573 728 795 856 931 984 511
89 39 217 170 345 354 473 566 601 411 729 473 857 756 985 988
100
90 259 218 61 346 211 474 676 602 803 730 634 858 860 986
1
91 84 219 531 347 401 475 361 603 789 731 744 859 499 987 951
100
92 138 220 525 348 185 476 706 604 709 732 852 860 731 988
2
93 145 221 642 349 396 477 589 605 365 733 960 861 823 989 893
94 261 222 281 350 344 478 215 606 440 734 865 862 922 990 975
95 29 223 278 351 586 479 786 607 628 735 693 863 874 991 894
100
96 43 224 526 352 645 480 647 608 689 736 797 864 918 992
9
97 98 225 177 353 593 481 348 609 374 737 906 865 502 993 955
100
98 515 226 293 354 535 482 419 610 423 738 715 866 933 994
4
101
99 88 227 388 355 240 483 406 611 466 739 807 867 743 995
0
100 140 228 91 356 206 484 464 612 793 740 474 868 760 996 957
101 30 229 584 357 95 485 680 613 250 741 636 869 881 997 983
102 146 230 769 358 327 486 801 614 371 742 694 870 494 998 958
103 71 231 198 359 564 487 362 615 481 743 254 871 702 999 987
101
104 262 232 172 360 800 488 590 616 574 744 717 872 921 1000
2
105 265 233 120 361 402 489 409 617 413 745 575 873 501 1001 999
101
106 161 234 201 362 356 490 570 618 603 746 913 874 876 1002
6
107 576 235 336 363 307 491 788 619 366 747 798 875 847 1003 767
108 45 236 62 364 301 492 597 620 468 748 811 876 992 1004 989
100
109 100 237 282 365 417 493 572 621 655 749 379 877 447 1005
3
110 640 238 143 366 213 494 219 622 900 750 697 878 733 1006 990
100
111 51 239 103 367 568 495 311 623 805 751 431 879 827 1007
5
112 148 240 178 368 832 496 708 624 615 752 607 880 934 1008 959
101
113 46 241 294 369 588 497 598 625 684 753 489 881 882 1009
1
101
114 75 242 93 370 186 498 601 626 710 754 866 882 937 1010
3
115 266 243 644 371 646 499 651 627 429 755 723 883 963 1011 895
100
116 273 244 202 372 404 500 421 628 794 756 486 884 747 1012
6
101
117 517 245 592 373 227 501 792 629 252 757 908 885 505 1013
4
101
118 104 246 323 374 896 502 802 630 373 758 718 886 855 1014
7
101
119 162 247 392 375 594 503 611 631 605 759 813 887 924 1015
8
120 53 248 297 376 418 504 602 632 848 760 476 888 734 1016 991
102
121 193 249 770 377 302 505 410 633 690 761 856 889 829 1017
0
100
122 152 250 107 378 649 506 231 634 713 762 839 890 965 1018
7
101
123 77 251 180 379 771 507 688 635 632 763 725 891 938 1019
5
101
124 164 252 151 380 360 508 653 636 482 764 698 892 884 1020
9
102
125 768 253 209 381 539 509 248 637 806 765 914 893 506 1021
1
102
126 268 254 284 382 111 510 369 638 427 766 752 894 749 1022
2
102
127 274 255 648 383 331 511 190 639 904 767 868 895 945 1023
3

5.3.2 Low density parity check coding

The bit sequence input for a given code block to channel coding is denoted by
c 0 , c 1 , c 2 , c 3 , .. . , c K −1 , where K is the
number of bits to encode as defined in Clause 5.2.2. After encoding the bits are denoted by 0 1 2
d ,d ,d ,...,d N−1 , where
N=66 Z c for LDPC base graph 1 and N=50 Z c for LDPC base graph 2, and the value of Z c is given in Clause 5.2.2.

For a code block encoded by LDPC, the following encoding procedure applies:

1) Find the set with index

i LS in Table 5.3.2-1 which contains Z c .

2) for
k =2 Z c to K−1

if
c k ≠¿ NULL>¿ ¿

3GPP
Release 17 21 3GPP TS 38.212 V17.5.0 (2023-03)

d k −2 Z =c k
c ;

else

c k =0 ;

d k −2 Z =< NULL>¿ ¿
c ;

end if

end for

3) Generate
N +2 Z c −K parity bits [
w= w0 , w1 , w 2 , .. . , w N+2 Z −K−1
c ]
T

such that
H×
[ wc ]=0 , where
c= [ c 0 , c 1 , c 2 ,. .. , c K−1 ]T 0
; is a column vector of all elements equal to 0. The encoding is performed in GF(2).

For LDPC base graph 1, a matrix of

H BG has 46 rows with row indices i=0,1,2,...,45 and 68 columns with
H
column indices j=0,1,2,...,67 . For LDPC base graph 2, a matrix of BG has 42 rows with row indices
i=0,1,2,...,41 and 52 columns with column indices j=0,1,2,...,51 . The elements in H BG with row and
column indices given in Table 5.3.2-2 (for LDPC base graph 1) and Table 5.3.2-3 (for LDPC base graph 2) are
of value 1, and all other elements in
H BG are of value 0.

H Z ×Z c matrix, according to the following:

The matrix H is obtained by replacing each element of BG with a c

- Each element of value 0 in

H BG is replaced by an all zero matrix 0 of size Z c×Z c ;

- Each element of value 1 in

H BG is replaced by a circular permutation matrix I ( P i, j ) of size Z c×Z c , where i
and j are the row and column indices of the element, and ( i, j ) is obtained by circularly shifting the
I P
Z ×Z c to the right Pi , j times. The value of Pi , j is given by Pi , j =mod ( V i , j , Z c ) . The
identity matrix I of size c
value of
V i , j is given by Tables 5.3.2-2 and 5.3.2-3 according to the set index i LS and LDPC base graph.

4) for k =K to
N +2 Z c −1

d k −2 Z =w k−K
c ;

end for

Table 5.3.2-1: Sets of LDPC lifting size Z

i
Set index ( LS ) Set of lifting sizes ( Z )
0 {2, 4, 8, 16, 32, 64, 128, 256}
1 {3, 6, 12, 24, 48, 96, 192, 384}
2 {5, 10, 20, 40, 80, 160, 320}
3 {7, 14, 28, 56, 112, 224}
4 {9, 18, 36, 72, 144, 288}
5 {11, 22, 44, 88, 176, 352}
6 {13, 26, 52, 104, 208}
7 {15, 30, 60, 120, 240}

3GPP
Release 17 22 3GPP TS 38.212 V17.5.0 (2023-03)

Table 5.3.2-2: LDPC base graph 1 (

H BG ) and its parity check matrices (V i , j )

3GPP
Release 17 23 3GPP TS 38.212 V17.5.0 (2023-03)

H BG Vi,j H BG Vi,j
Row
inde
Column
Set index LS
i Row
inde
Column
Set index LS
i
index index
x x
i j 0 1 2 3 4 5 6 7
i j 0 1 2 3 4 5 6 7

0 250 307 73 223 211 294 0 135 1 96 2 290 120 0 348 6 138
1 69 19 15 16 198 118 0 227 10 65 210 60 131 183 15 81 220
2 226 50 103 94 188 167 0 126 13 63 318 130 209 108 81 182 173
15
3 159 369 49 91 186 330 0 134 18 75 55 184 209 68 176 53 142
5 100 181 240 74 219 207 0 84 25 179 269 51 81 64 113 46 49
6 10 216 39 10 4 165 0 83 37 0 0 0 0 0 0 0 0
9 59 317 15 0 29 243 0 53 1 64 13 69 154 270 190 88 78
10 229 288 162 205 144 250 0 225 3 49 338 140 164 13 293 198 152
11 110 109 215 216 116 1 0 205 11 49 57 45 43 99 332 160 84
16
0 12 191 17 164 21 216 339 0 128 20 51 289 115 189 54 331 122 5
13 9 357 133 215 115 201 0 75 22 154 57 300 101 0 114 182 205
15 195 215 298 14 233 53 0 135 38 0 0 0 0 0 0 0 0
16 23 106 110 70 144 347 0 217 0 7 260 257 56 153 110 91 183
18 190 242 113 141 95 304 0 220 14 164 303 147 110 137 228 184 112
19 35 180 16 198 216 167 0 90 16 59 81 128 200 0 247 30 106
17
20 239 330 189 104 73 47 0 105 17 1 358 51 63 0 116 3 219
21 31 346 32 81 261 188 0 137 21 144 375 228 4 162 190 155 129
22 1 1 1 1 1 1 0 1 39 0 0 0 0 0 0 0 0
23 0 0 0 0 0 0 0 0 1 42 130 260 199 161 47 1 183
0 2 76 303 141 179 77 22 96 12 233 163 294 110 151 286 41 215
2 239 76 294 45 162 225 11 236 13 8 280 291 200 0 246 167 180
18
3 117 73 27 151 223 96 124 136 18 155 132 141 143 241 181 68 143
4 124 288 261 46 256 338 0 221 19 147 4 295 186 144 73 148 14
5 71 144 161 119 160 268 10 128 40 0 0 0 0 0 0 0 0
7 222 331 133 157 76 112 0 92 0 60 145 64 8 0 87 12 179
8 104 331 4 133 202 302 0 172 1 73 213 181 6 0 110 6 108
9 173 178 80 87 117 50 2 56 7 72 344 101 103 118 147 166 159
19
11 220 295 129 206 109 167 16 11 8 127 242 270 198 144 258 184 138
1 12 102 342 300 93 15 253 60 189 10 224 197 41 8 0 204 191 196
14 109 217 76 79 72 334 0 95 41 0 0 0 0 0 0 0 0
15 132 99 266 9 152 242 6 85 0 151 187 301 105 265 89 6 77
16 142 354 72 118 158 257 30 153 3 186 206 162 210 81 65 12 187
17 155 114 83 194 147 133 0 87 9 217 264 40 121 90 155 15 203
20
19 255 331 260 31 156 9 168 163 11 47 341 130 214 144 244 5 167
21 28 112 301 187 119 302 31 216 22 160 59 10 183 228 30 30 130
22 0 0 0 0 0 0 105 0 42 0 0 0 0 0 0 0 0
23 0 0 0 0 0 0 0 0 1 249 205 79 192 64 162 6 197
24 0 0 0 0 0 0 0 0 5 121 102 175 131 46 264 86 122
0 106 205 68 207 258 226 132 189 16 109 328 132 220 266 346 96 215
21
1 111 250 7 203 167 35 37 4 20 131 213 283 50 9 143 42 65
2 185 328 80 31 220 213 21 225 21 171 97 103 106 18 109 199 216
4 63 332 280 176 133 302 180 151 43 0 0 0 0 0 0 0 0
5 117 256 38 180 243 111 4 236 0 64 30 177 53 72 280 44 25
6 93 161 227 186 202 265 149 117 12 142 11 20 0 189 157 58 47
7 229 267 202 95 218 128 48 179 22 13 188 233 55 3 72 236 130 126
8 177 160 200 153 63 237 38 92 17 158 22 316 148 257 113 131 178
9 95 63 71 177 0 294 122 24 44 0 0 0 0 0 0 0 0
2 10 39 129 106 70 3 127 195 68 1 156 24 249 88 180 18 45 185
13 142 200 295 77 74 110 155 6 2 147 89 50 203 0 6 18 127
14 225 88 283 214 229 286 28 101 23 10 170 61 133 168 0 181 132 117
15 225 53 301 77 0 125 85 33 18 152 27 105 122 165 304 100 199
17 245 131 184 198 216 131 47 96 45 0 0 0 0 0 0 0 0
18 205 240 246 117 269 163 179 125 0 112 298 289 49 236 38 9 32
19 251 205 230 223 200 210 42 67 3 86 158 280 157 199 170 125 178
20 117 13 276 90 234 7 66 230 4 236 235 110 64 0 249 191 2
24
24 0 0 0 0 0 0 0 0 11 116 339 187 193 266 288 28 156
25 0 0 0 0 0 0 0 0 22 222 234 281 124 0 194 6 58
0 121 276 220 201 187 97 4 128 46 0 0 0 0 0 0 0 0
1 89 87 208 18 145 94 6 23 1 23 72 172 1 205 279 4 27
3 84 0 30 165 166 49 33 162 6 136 17 295 166 0 255 74 141
4 20 275 197 5 108 279 113 220 25 7 116 383 96 65 0 111 16 11
6 150 199 61 45 82 139 49 43 14 182 312 46 81 183 54 28 181
7 131 153 175 142 132 166 21 186 47 0 0 0 0 0 0 0 0
8 243 56 79 16 197 91 6 96 0 195 71 270 107 0 325 21 163
10 136 132 281 34 41 106 151 1 2 243 81 110 176 0 326 142 131
11 86 305 303 155 162 246 83 216 26 4 215 76 318 212 0 226 192 169
3 12 246 231 253 213 57 345 154 22 15 61 136 67 127 277 99 197 98
13 219 341 164 147 36 269 87 24 48 0 0 0 0 0 0 0 0
14 211 212 53 69 115 185 5 167 1 25 194 210 208 45 91 98 165
16 240 304 44 96 242 249 92 200 6 104 194 29 141 36 326 140 232
27
17 76 300 28 74 165 215 173 32 8 194 101 304 174 72 268 22 9
18 244 271 77 99 0 143 120 235 49 0 0 0 0 0 0 0 0
20 144 39 319 30 113 121 2 172 0 128 222 11 146 275 102 4 32
21 12 357 68 158 108 121 142 219 4 165 19 293 153 0 1 1 43
22 1 1 1 1 1 1 0 1 28 19 181 244 50 217 155 40 40 200
25 0 0 0 0 0 0 0 0 21 63 274 234 114 62 167 93 205
0 157 332 233 170 246 42 24 64 50 0 0 0 0 0 0 0 0
4 1 102 181 205 10 235 256 204 211 1 86 252 27 150 0 273 92 232
26 0 0 0 0 0 0 0 0 14 236 5 308 11 180 104 136 32
5 0 205 195 83 164 261 219 185 2 29 18 84 147 117 53 0 243 106 118
1 236 14 292 59 181 130 100 171 25 6 78 29 68 42 107 6 103
3 194 115 50 86 72 251 24 47 51 0 0 0 0 0 0 0 0
12 231 166 318 80 283 322 65 143 30 0 216 159 91 34 0 171 2 170

3GPP
Release 17 24 3GPP TS 38.212 V17.5.0 (2023-03)

16 28 241 201 182 254 295 207 210 10 73 229 23 130 90 16 88 199
21 123 51 267 130 79 258 161 180 13 120 260 105 210 252 95 112 26
22 115 157 279 153 144 283 72 180 24 9 90 135 123 173 212 20 105
27 0 0 0 0 0 0 0 0 52 0 0 0 0 0 0 0 0
0 183 278 289 158 80 294 6 199 1 95 100 222 175 144 101 4 73
6 22 257 21 119 144 73 27 22 7 177 215 308 49 144 297 49 149
10 28 1 293 113 169 330 163 23 31 22 172 258 66 177 166 279 125 175
11 67 351 13 21 90 99 50 100 25 61 256 162 128 19 222 194 108
6 13 244 92 232 63 59 172 48 92 53 0 0 0 0 0 0 0 0
17 11 253 302 51 177 150 24 207 0 221 102 210 192 0 351 6 103
18 157 18 138 136 151 284 38 52 12 112 201 22 209 211 265 126 110
20 211 225 235 116 108 305 91 13 32 14 199 175 271 58 36 338 63 151
28 0 0 0 0 0 0 0 0 24 121 287 217 30 162 83 20 211
0 220 9 12 17 169 3 145 77 54 0 0 0 0 0 0 0 0
1 44 62 88 76 189 103 88 146 1 2 323 170 114 0 56 10 199
4 159 316 207 104 154 224 112 209 2 187 8 20 49 0 304 30 132
7 7 31 333 50 100 184 297 153 32 33 11 41 361 140 161 76 141 6 172
8 167 290 25 150 104 215 159 166 21 211 105 33 137 18 101 92 65
14 104 114 76 158 164 39 76 18 55 0 0 0 0 0 0 0 0
29 0 0 0 0 0 0 0 0 0 127 230 187 82 197 60 4 161
0 112 307 295 33 54 348 172 181 7 167 148 296 186 0 320 153 237
1 4 179 133 95 0 75 2 105 34 15 164 202 5 68 108 112 197 142
3 7 165 130 4 252 22 131 141 17 159 312 44 150 0 54 155 180
12 211 18 231 217 41 312 141 223 56 0 0 0 0 0 0 0 0
16 102 39 296 204 98 224 96 177 1 161 320 207 192 199 100 4 231
8
19 164 224 110 39 46 17 99 145 6 197 335 158 173 278 210 45 174
21 109 368 269 58 15 59 101 199 35 12 207 2 55 26 0 195 168 145
22 241 67 245 44 230 314 35 153 22 103 266 285 187 205 268 185 100
24 90 170 154 201 54 244 116 38 57 0 0 0 0 0 0 0 0
30 0 0 0 0 0 0 0 0 0 37 210 259 222 216 135 6 11
0 103 366 189 9 162 156 6 169 14 105 313 179 157 16 15 200 207
1 182 232 244 37 159 88 10 12 36 15 51 297 178 0 0 35 177 42
10 109 321 36 213 93 293 145 206 18 120 21 160 6 0 188 43 100
11 21 133 286 105 134 111 53 221 58 0 0 0 0 0 0 0 0
9 13 142 57 151 89 45 92 201 17 1 198 269 298 81 72 319 82 59
17 14 303 267 185 132 152 4 212 13 220 82 15 195 144 236 2 204
37
18 61 63 135 109 76 23 164 92 23 122 115 115 138 0 85 135 161
20 216 82 209 218 209 337 173 205 59 0 0 0 0 0 0 0 0
31 0 0 0 0 0 0 0 0 0 167 185 151 123 190 164 91 121
1 98 101 14 82 178 175 126 116 9 151 177 179 90 0 196 64 90
2 149 339 80 165 1 253 77 151 38 10 157 289 64 73 0 209 198 26
4 167 274 211 174 28 27 156 70 12 163 214 181 10 0 246 100 140
10 7 160 111 75 19 267 231 16 230 60 0 0 0 0 0 0 0 0
8 49 383 161 194 234 49 12 115 1 173 258 102 12 153 236 4 115
14 58 354 311 103 201 267 70 84 3 139 93 77 77 0 264 28 188
32 0 0 0 0 0 0 0 0 39 7 149 346 192 49 165 37 109 168
0 77 48 16 52 55 25 184 45 19 0 297 208 114 117 272 188 52
1 41 102 147 11 23 322 194 115 61 0 0 0 0 0 0 0 0
12 83 8 290 2 274 200 123 134 0 157 175 32 67 216 304 10 4
16 182 47 289 35 181 351 16 1 8 137 37 80 45 144 237 84 103
11 40
21 78 188 177 32 273 166 104 152 17 149 312 197 96 2 135 12 30
22 252 334 43 84 39 338 109 165 62 0 0 0 0 0 0 0 0
23 22 115 280 201 26 192 124 107 1 167 52 154 23 0 123 2 53
33 0 0 0 0 0 0 0 0 3 173 314 47 215 0 77 75 189
0 160 77 229 142 225 123 6 186 41 9 139 139 124 60 0 25 142 215
1 42 186 235 175 162 217 20 215 18 151 288 207 167 183 272 128 24
10 21 174 169 136 244 142 203 124 63 0 0 0 0 0 0 0 0
12 11 32 232 48 3 151 110 153 180 0 149 113 226 114 27 288 163 222
13 234 50 105 28 238 176 104 98 4 157 14 65 91 0 83 10 170
42
18 7 74 52 182 243 76 207 80 24 137 218 126 78 35 17 162 71
34 0 0 0 0 0 0 0 0 64 0 0 0 0 0 0 0 0
0 177 313 39 81 231 311 52 220 1 151 113 228 206 52 210 1 22
3 248 177 302 56 0 251 147 185 16 163 132 69 22 243 3 163 127
7 151 266 303 72 216 265 1 154 43 18 173 114 176 134 0 53 99 49
13
20 185 115 160 217 47 94 16 178 25 139 168 102 161 270 167 98 125
23 62 370 37 78 36 81 46 150 65 0 0 0 0 0 0 0 0
35 0 0 0 0 0 0 0 0 0 139 80 234 84 18 79 4 191
0 206 142 78 14 0 22 1 124 7 157 78 227 4 0 244 6 211
12 55 248 299 175 186 322 202 144 44 9 163 163 259 9 0 293 142 187
15 206 137 54 211 253 277 118 182 22 173 274 260 12 57 272 3 148
14 16 127 89 61 191 16 156 130 95 66 0 0 0 0 0 0 0 0
17 16 347 179 51 0 66 1 72 1 149 135 101 184 168 82 181 177
21 229 12 258 43 79 78 2 76 6 151 149 228 121 0 67 45 114
45
36 0 0 0 0 0 0 0 0 10 167 15 126 29 144 235 153 93
15 0 40 241 229 90 170 176 173 39 67 0 0 0 0 0 0 0 0

3GPP
Release 17 25 3GPP TS 38.212 V17.5.0 (2023-03)

Table 5.3.2-3: LDPC base graph 2 (

H BG ) and its parity check matrices (V i , j )

3GPP
Release 17 26 3GPP TS 38.212 V17.5.0 (2023-03)

H BG Vi,j H BG Vi,j
Row
inde
Column
Set index LS
i Row
inde
Column
Set index LS
i
index index
x x
i j 0 1 2 3 4 5 6 7
i j 0 1 2 3 4 5 6 7

0 9 174 0 72 3 156 143 145 16 26 0 0 0 0 0 0 0 0

1 117 97 0 110 26 143 19 131 1 254 158 0 48 120 134 57 196
2 204 166 0 23 53 14 176 71 5 124 23 24 132 43 23 201 173
3 26 66 0 181 35 3 165 21 17 11 114 9 109 206 65 62 142 195
0
6 189 71 0 95 115 40 196 23 12 64 6 18 2 42 163 35 218
9 205 172 0 8 127 123 13 112 27 0 0 0 0 0 0 0 0
10 0 0 0 1 0 0 0 1 0 220 186 0 68 17 173 129 128
11 0 0 0 0 0 0 0 0 6 194 6 18 16 106 31 203 211
18
0 167 27 137 53 19 17 18 142 7 50 46 86 156 142 22 140 210
3 166 36 124 156 94 65 27 174 28 0 0 0 0 0 0 0 0
4 253 48 0 115 104 63 3 183 0 87 58 0 35 79 13 110 39
5 125 92 0 156 66 1 102 27 1 20 42 158 138 28 135 124 84
19
6 226 31 88 115 84 55 185 96 10 185 156 154 86 41 145 52 88
1
7 156 187 0 200 98 37 17 23 29 0 0 0 0 0 0 0 0
8 224 185 0 29 69 171 14 9 1 26 76 0 6 2 128 196 117
9 252 3 55 31 50 133 180 167 4 105 61 148 20 103 52 35 227
20
11 0 0 0 0 0 0 0 0 11 29 153 104 141 78 173 114 6
12 0 0 0 0 0 0 0 0 30 0 0 0 0 0 0 0 0
0 81 25 20 152 95 98 126 74 0 76 157 0 80 91 156 10 238
1 114 114 94 131 106 168 163 31 8 42 175 17 43 75 166 122 13
21
3 44 117 99 46 92 107 47 3 13 210 67 33 81 81 40 23 11
4 52 110 9 191 110 82 183 53 31 0 0 0 0 0 0 0 0
2
8 240 114 108 91 111 142 132 155 1 222 20 0 49 54 18 202 195
10 1 1 1 0 1 1 1 0 22 2 63 52 4 1 132 163 126 44
12 0 0 0 0 0 0 0 0 32 0 0 0 0 0 0 0 0
13 0 0 0 0 0 0 0 0 0 23 106 0 156 68 110 52 5
1 8 136 38 185 120 53 36 239 3 235 86 75 54 115 132 170 94
23
2 58 175 15 6 121 174 48 171 5 238 95 158 134 56 150 13 111
4 158 113 102 36 22 174 18 95 33 0 0 0 0 0 0 0 0
5 104 72 146 124 4 127 111 110 1 46 182 0 153 30 113 113 81
6 209 123 12 124 73 17 203 159 2 139 153 69 88 42 108 161 19
3 24
7 54 118 57 110 49 89 3 199 9 8 64 87 63 101 61 88 130
8 18 28 53 156 128 17 191 43 34 0 0 0 0 0 0 0 0
9 128 186 46 133 79 105 160 75 0 228 45 0 211 128 72 197 66
10 0 0 0 1 0 0 0 1 25 5 156 21 65 94 63 136 194 95
13 0 0 0 0 0 0 0 0 35 0 0 0 0 0 0 0 0
0 179 72 0 200 42 86 43 29 2 29 67 0 90 142 36 164 146
1 214 74 136 16 24 67 27 140 7 143 137 100 6 28 38 172 66
4
11 71 29 157 101 51 83 117 180 26 12 160 55 13 221 100 53 49 190
14 0 0 0 0 0 0 0 0 13 122 85 7 6 133 145 161 86
0 231 10 0 185 40 79 136 121 36 0 0 0 0 0 0 0 0
1 41 44 131 138 140 84 49 41 0 8 103 0 27 13 42 168 64
5 194 121 142 170 84 35 36 169 27 6 151 50 32 118 10 104 193 181
5
7 159 80 141 219 137 103 132 88 37 0 0 0 0 0 0 0 0
11 103 48 64 193 71 60 62 207 1 98 70 0 216 106 64 14 7
15 0 0 0 0 0 0 0 0 2 101 111 126 212 77 24 186 144
28
0 155 129 0 123 109 47 7 137 5 135 168 110 193 43 149 46 16
5 228 92 124 55 87 154 34 72 38 0 0 0 0 0 0 0 0
7 45 100 99 31 107 10 198 172 0 18 110 0 108 133 139 50 25
6
9 28 49 45 222 133 155 168 124 29 4 28 17 154 61 25 161 27 57
11 158 184 148 209 139 29 12 56 39 0 0 0 0 0 0 0 0
16 0 0 0 0 0 0 0 0 2 71 120 0 106 87 84 70 37
1 129 80 0 103 97 48 163 86 5 240 154 35 44 56 173 17 139
5 147 186 45 13 135 125 78 186 30 7 9 52 51 185 104 93 50 221
7 140 16 148 105 35 24 143 87 9 84 56 134 176 70 29 6 17
7
11 3 102 96 150 108 47 107 172 40 0 0 0 0 0 0 0 0
13 116 143 78 181 65 55 58 154 1 106 3 0 147 80 117 115 201
17 0 0 0 0 0 0 0 0 31 13 1 170 20 182 139 148 189 46
0 142 118 0 147 70 53 101 176 41 0 0 0 0 0 0 0 0
1 94 70 65 43 69 31 177 169 0 242 84 0 108 32 116 110 179
8
12 230 152 87 152 88 161 22 225 5 44 8 20 21 89 73 0 14
32
18 0 0 0 0 0 0 0 0 12 166 17 122 110 71 142 163 116
1 203 28 0 2 97 104 186 167 42 0 0 0 0 0 0 0 0
8 205 132 97 30 40 142 27 238 2 132 165 0 71 135 105 163 46
9 10 61 185 51 184 24 99 205 48 7 164 179 88 12 6 137 173 2
33
11 247 178 85 83 49 64 81 68 10 235 124 13 109 2 29 179 106
19 0 0 0 0 0 0 0 0 43 0 0 0 0 0 0 0 0
0 11 59 0 174 46 111 125 38 0 147 173 0 29 37 11 197 184
1 185 104 17 150 41 25 60 217 12 85 177 19 201 25 41 191 135
34
10 6 0 22 156 8 101 174 177 208 13 36 12 78 69 114 162 193 141
7 117 52 20 56 96 23 51 232 44 0 0 0 0 0 0 0 0
20 0 0 0 0 0 0 0 0 1 57 77 0 91 60 126 157 85
0 11 32 0 99 28 91 39 178 5 40 184 157 165 137 152 167 225
35
7 236 92 7 138 30 175 29 214 11 63 18 6 55 93 172 181 175
11 9 210 174 4 110 116 24 35 168 45 0 0 0 0 0 0 0 0
13 56 154 2 99 64 141 8 51 0 140 25 0 1 121 73 197 178
21 0 0 0 0 0 0 0 0 2 38 151 63 175 129 154 167 112
36
1 63 39 0 46 33 122 18 124 7 154 170 82 83 26 129 179 106
3 111 93 113 217 122 11 155 122 46 0 0 0 0 0 0 0 0
12
11 14 11 48 109 131 4 49 72 10 219 37 0 40 97 167 181 154
22 0 0 0 0 0 0 0 0 37 13 151 31 144 12 56 38 193 114
13 0 83 49 0 37 76 29 32 48 47 0 0 0 0 0 0 0 0
1 2 125 112 113 37 91 53 57 38 1 31 84 0 37 1 112 157 42

3GPP
Release 17 27 3GPP TS 38.212 V17.5.0 (2023-03)

8 38 35 102 143 62 27 95 167 5 66 151 93 97 70 7 173 41

13 222 166 26 140 47 127 186 219 11 38 190 19 46 1 19 191 105
23 0 0 0 0 0 0 0 0 48 0 0 0 0 0 0 0 0
1 115 19 0 36 143 11 91 82 0 239 93 0 106 119 109 181 167
6 145 118 138 95 51 145 20 232 7 172 132 24 181 32 6 157 45
39
14 11 3 21 57 40 130 8 52 204 12 34 57 138 154 142 105 173 189
13 232 163 27 116 97 166 109 162 49 0 0 0 0 0 0 0 0
24 0 0 0 0 0 0 0 0 2 0 103 0 98 6 160 193 78
0 51 68 0 116 139 137 174 38 10 75 107 36 35 73 156 163 67
40
10 175 63 73 200 96 103 108 217 13 120 163 143 36 102 82 179 180
15
11 213 81 99 110 128 40 102 157 50 0 0 0 0 0 0 0 0
25 0 0 0 0 0 0 0 0 1 129 147 0 120 48 132 191 53
1 203 87 0 75 48 78 125 170 5 229 7 2 101 47 6 197 215
41
9 142 177 79 158 9 158 31 23 11 118 60 55 81 19 8 167 230
16
11 8 135 111 134 28 17 54 175 51 0 0 0 0 0 0 0 0
12 242 64 143 97 8 165 176 202

5.3.3 Channel coding of small block lengths

The bit sequence input for a given code block to channel coding is denoted by
c 0 , c 1 , c 2 , c 3 , .. . , c K −1 , where K is the
number of bits to encode. After encoding the bits are denoted by
d 0 ,d1 ,d 2 ,...,d N−1 .

[Link] Encoding of 1-bit information

For K=1 , the code block is encoded according to Table [Link]-1, where
N=Q m and Qm is the modulation order for
the code block.

[Link] Encoding of 2-bit information

For K = 2 , the code block is encoded according to Table [Link]-1, where c 2 =(c 0 +c 1 )mod2 ,
N=3Q m , and Qm is the
modulation order for the code block.

Table [Link]-1: Encoding of 2-bit information

Qm d ,d ,d ,...,d N−1
Encoded bits 0 1 2
1 [ c0 c1 c2 ]
2 [ c0 c1 c2 c0 c1 c2 ]
4 [ c0 c1 x x c2 c0 x x c1 c2 x x ]
6 [ c0 c1 x x x x c2 c0 x x x x c1 c2 x x x x ]
8 [ c 0 c 1 x x x x x x c2 c0 x x x x x x c 1 c 2 x x x x x x]
The "x" in Table [Link]-1 are placeholders for Clause [Link] of [4, TS 38.211] to scramble the information bits in a
way that maximizes the Euclidean distance of the modulation symbols carrying the information bits.

3GPP
Release 17 28 3GPP TS 38.212 V17.5.0 (2023-03)

[Link] Encoding of other small block lengths

(∑ )
K−1
di= c k⋅M i , k mod 2
For 3≤K≤11 , the code block is encoded by k =0 M
, where i=0 , 1 ,⋯, N−1 , N=32 , and i, k
represents the basis sequences as defined in Table [Link]-1.

3GPP
Release 17 29 3GPP TS 38.212 V17.5.0 (2023-03)

5.4 Rate matching

5.4.1 Rate matching for Polar code
The rate matching for Polar code is defined per coded block and consists of sub-block interleaving, bit collection, and
bit interleaving. The input bit sequence to rate matching is d 0 ,d1 ,d 2 ,...,d N−1 . The output bit sequence after rate matching
is denoted as f 0 , f 1 , f 2 , .. . , f E−1 .

[Link] Sub-block interleaving

The bits input to the sub-block interleaver are the coded bits d 0 ,d1 ,d 2 ,...,d N−1 . The coded bits d 0 ,d1 ,d 2 ,...,d N−1 are
divided into 32 sub-blocks. The bits output from the sub-block interleaver are denoted as y 0 , y 1 , y 2 ,..., y N −1 , generated as
follows:

for n=0 to N−1

i=⌊ 32 n/ N ⌋ ;

J ( n )=P ( i )×( N /32 ) +mod (n , N /32) ;

y n =d J ( n )
;

end for

where the sub-block interleaver pattern P ( i ) is given by Table [Link]-1.

Table [Link]-1: Sub-block interleaver pattern P ( i )

i P (i) i P (i) i P (i) i P (i) i P (i) i P (i) i P (i) i P (i)
0 0 4 3 8 8 12 10 16 12 20 14 24 24 28 27
1 1 5 5 9 16 13 18 17 20 21 22 25 25 29 29
2 2 6 6 10 9 14 11 18 13 22 15 26 26 30 30
3 4 7 7 11 17 15 19 19 21 23 23 27 28 31 31

N N n
The sets of bit indices Q̄ I and Q̄ F are determined as follows, where K , PC , and Q 0
N−1
are defined in Clause 5.3.1

Q̄ NF , tmp=∅

if E< N

if K / E≤7/ 16 -- puncturing

for n=0 to N−E−1

Q̄ NF , tmp= Q̄NF ,tmp ∪ { J ( n ) } ;

end for

if E≥3 N / 4

Q̄ NF , tmp= Q̄NF ,tmp ∪ {0 , 1 ,…, ⌈3 N /4−E /2⌉−1 } ;

else

Q̄ NF , tmp= Q̄NF ,tmp ∪ {0 , 1 ,…, ⌈9 N /16−E/ 4⌉−1 } ;

end if

3GPP
Release 17 30 3GPP TS 38.212 V17.5.0 (2023-03)

else -- shortening

for n=E to N−1

Q̄ NF , tmp= Q̄ NF ,tmp ∪ { J ( n ) } ;

end for

end if

Q̄ NI , tmp =Q0N−1 {Q̄ NF , tmp ¿ ;

I comprises (
Q̄ N K + nPC ) N
most reliable bit indices in Q̄ I , tmp ;

Q̄ NF =Q0N−1 {Q̄ NI ¿ ;

[Link] Bit selection

The bit sequence after the sub-block interleaver y 0 , y 1 , y 2 ,..., y N −1 from Clause [Link] is written into a circular buffer of
length N .

Denoting by E the rate matching output sequence length, the bit selection output bit sequence
e k , k=0,1,2,...,E−1 , is
generated as follows:

if E≥N -- repetition

for k =0 to E−1

e k = y mod( k , N )
;

end for

else

if K / E≤7/ 16 -- puncturing

for k =0 to E−1

e k = y k + N−E ;
end for

else -- shortening

for k =0 to E−1

ek = yk ;
end for

end if

[Link] Interleaving of coded bits

The bit sequence e 0 ,e 1 ,e2 ,...,e E −1 is interleaved into bit sequence f 0 , f 1 , f 2 , .. . , f E−1 , as follows:

3GPP
Release 17 31 3GPP TS 38.212 V17.5.0 (2023-03)

If I BIL=1

Denote T as the smallest integer such that T ( T +1 ) /2≥E ;

k =0 ;

for i=0 to T −1

for j =0 to T −1−i

if k < E

v i, j =e k ;

else

v i, j =< NULL>¿ ¿;

end if

k =k +1 ;

end for

k =0 ;

for j =0 to T −1

for i=0 to T −1− j

if
v i, j ≠¿ NULL>¿ ¿

f k =v i , j ;

k =k +1
end if

end for

else

for i=0 to E−1

f i=ei ;

end for

end if

The value of E is no larger than 8192.

3GPP
Release 17 32 3GPP TS 38.212 V17.5.0 (2023-03)

5.4.2 Rate matching for LDPC code

The rate matching for LDPC code is defined per coded block and consists of bit selection and bit interleaving. The input
bit sequence to rate matching is d 0 ,d1 ,d 2 ,...,d N−1 . The output bit sequence after rate matching is denoted as
f 0 , f 1 , f 2 , .. . , f E−1 .

[Link] Bit selection

The bit sequence after encoding d 0 ,d1 ,d 2 ,...,d N−1 from Clause 5.3.2 is written into a circular buffer of length
N cb for the
r -th coded block, where N is defined in Clause 5.3.2.

For the r -th code block, let cb

N =N
if LBRM and
I =0 N cb =min ( N , N ref )
otherwise, where
N ref =
,
⌊ TBS LBRM
C⋅R LBRM ⌋
RLBRM =2 /3 , TBS LBRM is determined according to Clause [Link] in [6, TS 38.214] for UL-SCH and Clause [Link] in
[6, TS 38.214] for DL-SCH/PCH, assuming the following:

For one TB for DL-SCH with PDSCH scheduled by DCI format 4_0/4_1/4_2,

- if the PDSCH is scheduled by DCI format 4_1/4_2,

- maximum number of layers is given by X, where

- if the higher layer parameter maxMIMO-Layers of pdsch-ConfigMulticast is configured, X is given by

that parameter;

- otherwise, X equals to 1;

- if the higher layer parameter mcs-Table given by a pdsch-ConfigMulticast for at least one common frequency
resource (CFR) is set to 'qam256', maximum modulation order Q m =8 is assumed for DL-SCH; otherwise a
maximum modulation order Q m =6 is assumed for DL-SCH;

- if the PDSCH is scheduled by DCI format 4_0,

- maximum number of layers is 1;

- if the higher layer parameter mcs-Table given by a pdsch-ConfigMCCH is set to 'qam256', maximum
modulation order Q m =8 is assumed for DL-SCH; otherwise a maximum modulation order Q m =6 is
assumed for DL-SCH;

- if the higher layer parameter mcs-Table given by a pdsch-ConfigMTCH is set to 'qam256', maximum
modulation order Q m =8 is assumed for DL-SCH; otherwise a maximum modulation order Q m =6 is
assumed for DL-SCH;

- n PRB=n PRB , LBRM is given by Table [Link]-1, where the value of n PRB , LBRM for DL-SCH is determined
according to the size of the CFR if only one CFR is configured to the UE;

- maximum coding rate of 948/1024;

- N ℜ=156∙ n PRB;
- C is the number of code blocks of the transport block determined according to Clause 5.2.2.
For one TB for UL-SCH, or for one TB for DL-SCH/PCH except for DL-SCH with PDSCH scheduled by DCI format
4_0/4_1/4_2,

- maximum number of layers for one TB for UL-SCH is given by X, where

- if the higher layer parameter maxMIMO-Layers of PUSCH-ServingCellConfig of the serving cell is

configured, X is given by that parameter

3GPP
Release 17 33 3GPP TS 38.212 V17.5.0 (2023-03)

- elseif the higher layer parameter maxRank of pusch-Config of the serving cell is configured, X is given by the
maximum value of maxRank across all BWPs of the serving cell

- otherwise, X is given by the maximum number of layers for PUSCH supported by the UE for the serving cell

- maximum number of layers for one TB for DL-SCH/PCH is given by the minimum of X and 4, where

- if the higher layer parameter maxMIMO-Layers of PDSCH-ServingCellConfig of the serving cell is

configured, X is given by that parameter

- otherwise, X is given by the maximum number of layers for PDSCH supported by the UE for the serving cell

- if the higher layer parameter mcs-Table-r17 or mcs-TableDCI-1-2-r17 given by a pdsch-Config for at least one
DL BWP of the serving cell is set to 'qam1024', maximum modulation order Q m =10 is assumed for DL-SCH,
else if the higher layer parameter mcs-Table or mcs-TableDCI-1-2 given by a pdsch-Config for at least one DL
BWP of the serving cell is set to 'qam256', maximum modulation order is assumed for DL-SCH;
Q =6 is assumed for DL-SCH;
otherwise a maximum modulation order m

- if the higher layer parameter mcs-Table or mcs-TableTransformPrecoder or mcs-TableDCI-0-2 or mcs-

TableTransformPrecoderDCI-0-2 given by a pusch-Config or the higher layer parameter mcs-Table or
mcs-TableTransformPrecoder given by configuredGrantConfig for at least one UL BWP of the serving cell
is set to 'qam256', maximum modulation order is assumed for UL-SCH; otherwise a maximum
Q =6 is assumed for UL-SCH
modulation order m

- maximum coding rate of 948/1024;

-
n PRB=n PRB , LBRM is given by Table [Link]-1, where the value of n PRB , LBRM for DL-SCH is determined
according to the initial downlink bandwidth part if there is no other downlink bandwidth part configured to the
UE;

- ;

- C is the number of code blocks of the transport block determined according to Clause 5.2.2.

n
Table [Link]-1: Value of PRB , LBRM

Maximum number of PRBs across all configured DL BWPs and UL BWPs of a carrier for DL-
SCH and UL-SCH, respectively,
or n PRB , LBRM
Maximum number of PRBs across all CFRs of a carrier for DL-SCH with PDSCH scheduled by DCI
format 4_0/4_1/4_2
Less than 33 32
33 to 66 66
67 to 107 107
108 to 135 135
136 to 162 162
163 to 217 217
Larger than 217 273

Denoting by Er the rate matching output sequence length for the r -th coded block, where the value of Er is
determined as follows:

Set j=0

for r =0 to C−1

3GPP
Release 17 34 3GPP TS 38.212 V17.5.0 (2023-03)

if the r -th coded block is not scheduled for transmission as indicated by CBGTI according to Clause [Link] for
DL-SCH and [Link] for UL-SCH in [6, TS 38.214]
Er =0 ;

else

if j ≤C ' −mod (G / ( N L⋅Qm ) ,C ' )−1

Er =N L⋅Q m⋅
⌊ G
N L⋅Q m⋅C ' ⌋ ;

else

G
Er =N L⋅Q m⋅⌈ ⌉
N L⋅Q m⋅C ' ;

end if

j= j+1 ;
end if

end for

where

- N L is the number of transmission layers that the transport block is mapped onto;

- Q m is the modulation order;

- G is the total number of coded bits available for transmission of the transport block;

- C '=C if CBGTI is not present in the DCI scheduling the transport block and C ' is the number of scheduled code
blocks of the transport block if CBGTI is present in the DCI scheduling the transport block.

Denote by
rv id the redundancy version number for this transmission (rv id = 0, 1, 2 or 3), the rate matching output bit
e k
sequence k , k=0,1,2,...,E−1 , is generated as follows, where 0 is given by Table [Link]-2 according to the value of
rv id and LDPC base graph:

k =0 ;

j=0 ;

while k < E
d ≠¿ NULL>¿ ¿
if ( k 0 + j ) mod N cb
e k =d k
( 0
+ j ) mod N cb
;

k =k +1 ;

end if

j= j+1 ;
end while

3GPP
Release 17 35 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link]-2: Starting position of different redundancy versions,

k0
rv id
LDPC base graph 1 LDPC base graph 2
0 0 0

1
⌊ ⌋
17 N cb
66 Z c
Zc
⌊ ⌋
13 N cb
50 Z c
Zc

2
⌊ ⌋
33 N cb
66 Z c
Zc
⌊ ⌋
25 N cb
50 Z c
Zc

3
⌊ ⌋
56 N cb
66 Z c
Zc
⌊ ⌋
43 N cb
50 Z c
Zc

[Link] Bit interleaving

The bit sequence e 0 ,e 1 ,e2 ,...,e E −1 is interleaved to bit sequence f 0 , f 1 , f 2 , .. . , f E−1 , according to the following, where the
value of
Q m is the modulation order.

for j=0 to
E /Q m−1

for i=0 to
Q m−1

f i+ j⋅Q =e i⋅E / Q +j
m m ;

end for

5.4.3 Rate matching for channel coding of small block lengths

The input bit sequence to rate matching is d 0 ,d1 ,d 2 ,...,d N−1 . The output bit sequence after rate matching is denoted as
f 0 , f 1 , f 2 , .. . , f E−1 , where E is the rate matching output sequence length. The bit sequence f 0 , f 1 , f 2 , .. . , f E−1 is obtained by
the following:

for k =0 to E−1

f k =d k mod N ;
end for

5.5 Code block concatenation

The input bit sequence for the code block concatenation block are the sequences
f rk , for r=0 ,. . ., C−1 and
k =0 , .. . , E r −1 , where Er is the number of rate matched bits for the r -th code block. The output bit sequence from

the code block concatenation block is the sequence

gk for k=0,...,G−1 .

The code block concatenation consists of sequentially concatenating the rate matching outputs for the different code
blocks. Therefore,

Set k =0 and r =0

3GPP
Release 17 36 3GPP TS 38.212 V17.5.0 (2023-03)

while r <C

Set j=0

while
j< Er

gk =f rj

k =k +1

j= j+1
end while

r =r +1

end while

6 Uplink transport channels and control information

6.1 Random access channel
The sequence index for the random access channel is received from higher layers and is processed according to [4, TS
38.211].

6.2 Uplink shared channel

6.2.1 Transport block CRC attachment
Error detection is provided on each UL-SCH transport block through a Cyclic Redundancy Check (CRC).

The entire transport block is used to calculate the CRC parity bits. Denote the bits in a transport block delivered to layer
1 by
a 0 , a1 , a 2 , a3 , . .. , a A −1 , and the parity bits by p0 , p1 , p2 , p3 , . .. , p L−1 , where A is the payload size and L is the

number of parity bits. The lowest order information bit

a 0 is mapped to the most significant bit of the transport block
as defined in Clause 6.1.1 of [TS38.321].

The parity bits are computed and attached to the UL-SCH transport block according to Clause 5.1, by setting L to 24
bits and using the generator polynomial gCRC24A ( D ) if A>3824 ; and by setting L to 16 bits and using the generator
polynomial gCRC16 ( D ) otherwise.

The bits after CRC attachment are denoted by

b 0 , b1 , b 2 ,b 3 , .. . , bB−1 , where B= A+ L .

6.2.2 LDPC base graph selection

For initial transmission of a transport block with coding rate R indicated by the MCS index according to Clause
[Link] in [6, TS 38.214] and subsequent re-transmission of the same transport block, each code block of the transport
block is encoded with either LDPC base graph 1 or 2 according to the following:

- if A≤292 , or if A≤3824 and R≤0 .67 , or if R≤0 .25 , LDPC base graph 2 is used;

- otherwise, LDPC base graph 1 is used,

where A is the payload size as described in Clause 6.2.1.

3GPP
Release 17 37 3GPP TS 38.212 V17.5.0 (2023-03)

6.2.3 Code block segmentation and code block CRC attachment

The bits input to the code block segmentation are denoted by
b 0 , b1 , b 2 ,b 3 , .. . , bB−1 where B is the number of bits in the
transport block (including CRC).

Code block segmentation and code block CRC attachment are performed according to Clause 5.2.2.

c r 0 , c r 1 , c r 2 , c r 3 , .. . , cr
The bits after code block segmentation are denoted by ( K r −1 ) , where r is the code block number

and K r is the number of bits for code block number r according to Clause 5.2.2.

When the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI is
larger than 1, the value of B is no larger than 3840 if R ≤ 0.25 and no larger than 8448 otherwise, where coding rate R
is indicated by the MCS index according to Clause [Link] in [6, TS 38.214].

6.2.4 Channel coding of UL-SCH

Code blocks are delivered to the channel coding block. The bits in a code block are denoted by
c r 0 , c r 1 , c r 2 , c r 3 , .. . , cr K −1
( r ) , where r is the code block number, and K r is the number of bits in code block number r .
The total number of code blocks is denoted by C and each code block is individually LDPC encoded according to
Clause 5.3.2.
d r 0 ,d r 1 , d r 2 , d r 3 ,. .. , d r N −1 N r is given in Clause 5.3.2.
After encoding the bits are denoted by ( r ) , where the values of

6.2.5 Rate matching

d r 0 ,d r 1 , d r 2 , d r 3 ,. .. , d r N
Coded bits for each code block, denoted as ( −1 )
r , are delivered to the rate match block, where r is
the code block number, and N r is the number of encoded bits in code block number r . The total number of code
blocks is denoted by C and each code block is individually rate matched according to Clause 5.4.2 by setting
I LBRM =1 if higher layer parameter rateMatching is set to limitedBufferRM and by setting I LBRM =0 otherwise, if
numberOfSlotsTBoMS is not present in the resource allocation table, or if numberOfSlotsTBoMS is present in the
resource allocation table and the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource
assignment field in DCI is equal to 1. When the value of numberOfSlotsTBoMS in the row indicated by the Time
domain resource assignment field in DCI is larger than 1, each code block is individually rate matched per slot
according to Clause 5.4.2 by setting

- I LBRM =1 if higher layer parameter rateMatching is set to limitedBufferRM and by setting I LBRM =0otherwise;
- G as the total number of coded bits available for transmission of the transport block in the slot;
- k 0 as given by Table [Link]-2 according to the value of rv id and LDPC base graph if the slot is the first slot
within the N s slots allocated for the transmission of TB processing over multiple slots, and setting
k 0=( k '0 + H +τ ) mod N cbif the slot is a slot except for the first one within the N s slots, where N s is the value
'
of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI, k 0 denotes
the index of starting coded bit in the previous slot within the N s slots, H is the total number of coded bits
available for transmission of the transport block in the previous slot within the N s slots assuming no UCI
multiplexing, and τ denotes the number of skipped filler bits if any in the previous slot within the N s slots
according to Clause [Link] by assuming no UCI multiplexing.
f r 0 , f r1 , f r 2 , f r 3 ,. .. , f r ( E −1 ) Er is the number of rate matched bits for
After rate matching, the bits are denoted by r , where
code block number r .

3GPP
Release 17 38 3GPP TS 38.212 V17.5.0 (2023-03)

6.2.6 Code block concatenation

f r 0 , f r1 , f r 2 , f r 3 ,. .. , f r ( E −1 )
The input bit sequence for the code block concatenation block are the sequences r , for
r=0 ,. . ., C−1 and where Er is the number of rate matched bits for the r -th code block.

Code block concatenation is performed according to Clause 5.5.

g ,g ,g ,g ,..., gG−1 , where G is the total number of coded bits

The bits after code block concatenation are denoted by 0 1 2 3
for transmission.

6.2.7 Data and control multiplexing

gUL−SCH
0 , gUL−SCH
1 , gUL−SCH
2 , gUL−SCH
3 , . .. , g UL−SCH
GUL−SCH −1
Denote the coded bits for UL-SCH as .

Denote the coded bits for HARQ-ACK or jointly coded bits for HARQ-ACK and CG-UCI when the high layer
ACK
g0ACK , g1ACK , g2ACK , g3ACK , . .. , g GACK −1
parameter cg-UCI-Multiplexing is configured, if any, as .

gCSI-part1 , gCSI-part1 , g CSI-part1 , gCSI-part1

CSI-part1
0 1 2 3 , . .. , g GCSI-part1−1
Denote the coded bits for CSI part 1, if any, as .

gCSI-part2
0 , gCSI-part2
1 , g CSI-part2
2 , gCSI-part2
3 , . .. , g CSI-part2
GCSI-part2−1
Denote the coded bits for CSI part 2, if any, as .

Denote the coded bits for CG-UCI without HARQ-ACK, if any, as

CG−UCI CG−UCI CG−UCI CG−UCI CG−UCI
g0 , g1 , g2 , g3 , … , gGCG −UCI −1.

g ,g ,g ,g ,..., gG−1 .
Denote the multiplexed data and control coded bit sequence as 0 1 2 3
PUSCH PUSCH
Denote l as the OFDM symbol index of the scheduled PUSCH, starting from 0 to N symb,all −1 , where N symb,all is the
total number of OFDM symbols of the PUSCH, including all OFDM symbols used for DMRS.
PUSCH PUSCH
Denote k as the subcarrier index of the scheduled PUSCH, starting from 0 to M sc −1 , where M sc is expressed as
a number of subcarriers.

Denote as the set of resource elements, in ascending order of indices k , available for transmission of data in
PUSCH
OFDM symbol l , for l=0 , 1, 2, . .. , N symb,all −1 .

Denote as the number of elements in set . Denote as the j -th element in

Denote as the set of resource elements, in ascending order of indices k , available for transmission of UCI in
PUSCH
OFDM symbol l , for l=0 , 1, 2, . .. , N symb,all −1 . Denote as the number of elements in set . Denote
as the j -th element in . For any OFDM symbol that carriers DMRS of the PUSCH, . For any
OFDM symbol that does not carry DMRS of the PUSCH, .

If frequency hopping is configured for the PUSCH,

(1)
- denote l as the OFDM symbol index of the first OFDM symbol after the first set of consecutive OFDM
symbol(s) carrying DMRS in the first hop;
(2)
- denote l as the OFDM symbol index of the first OFDM symbol after the first set of consecutive OFDM
symbol(s) carrying DMRS in the second hop.

3GPP
Release 17 39 3GPP TS 38.212 V17.5.0 (2023-03)

(1)
- denote l CSI as the OFDM symbol index of the first OFDM symbol that does not carry DMRS in the first hop;
(2)
- denote l CSI as the OFDM symbol index of the first OFDM symbol that does not carry DMRS in the second hop;

- if HARQ-ACK is present for transmission on the PUSCH with UL-SCH or if both HARQ-ACK and CG-UCI
are present on the same PUSCH with UL-SCH, let

- ⌊
G ACK (1 )=N L⋅Q m⋅ G ACK / ( 2⋅N L⋅Q m ) ⌋ and G
ACK
(2 )=N L⋅Qm⋅⌈GACK / ( 2⋅N L⋅Q m) ⌉ ;

- if CSI is present for transmission on the PUSCH with UL-SCH, let

- ⌊
G CSI-part1 ( 1 )=N L⋅Q m⋅ G CSI-part1 / ( 2⋅N L⋅Q m ) ⌋;

-
GCSI-part1 (2 )=N L⋅Qm⋅⌈GCSI-part1 /( 2⋅N L⋅Qm ) ⌉ ;

- ⌊
G CSI-part2 ( 1 )=N L⋅Q m⋅ G CSI-part2 / ( 2⋅N L⋅Q m ) ⌋ ; and

-
GCSI-part2 (2 )=N L⋅Qm⋅⌈GCSI-part2 / ( 2⋅N L⋅Qm ) ⌉ ;

- if CG-UCI is present for transmission on the PUSCH with UL-SCH and without HARQ-ACK, let
CG−UCI
- G ( 1 )=N L ∙Qm ∙ ⌊ GCG−UCI / ( 2 ∙ N L ∙ Qm ) ⌋ and GCG−UCI ( 2 )=N L ∙Qm ∙ ⌈ GCG−UCI / ( 2 ∙ N L ∙ Qm ) ⌉
- if only HARQ-ACK and CSI part 1 are present for transmission on the PUSCH without UL-SCH, let

- ;

- GACK (2 )=G ACK−GACK (1 ) ;

- GCSI-part1 (1 )=M 1⋅N L⋅Q m−GACK (1 ) ; and

- GCSI-part1 (2)=GCSI-part1−G CSI-part1 (1) ;

- if HARQ-ACK, CSI part 1 and CSI part 2 are present for transmission on the PUSCH without UL-SCH, let

- ;

- GACK (2 )=G ACK−GACK (1 ) ;

- if the number of HARQ-ACK information bits is more than 2,

( ⌊ ⌋
G CSI-part1 ( 1 )=min N L⋅Q m⋅ G CSI-part1 / ( 2⋅N L⋅Q m) , M 1⋅N L⋅Q m−G ACK ( 1) ) ; otherwise,

- GCSI-part1 (2)=GCSI-part1−G CSI-part1 (1) ;

- GCSI-part2 (1 )=M 1⋅N L⋅Q m−GCSI-part1 (1) if the number of HARQ-ACK information bits is no more than 2, and
GCSI-part2 (1 )=M 1⋅N L⋅Q m−GACK (1 )−GCSI-part1 (1) otherwise; and

- GCSI-part2 (2 )=M 2⋅N L⋅Q m−GCSI-part1 (2 ) if the number of HARQ-ACK information bits is no more than 2, and
GCSI-part2 (2 )=M 2⋅N L⋅Q m−GACK (2 )−GCSI-part1 (2 ) otherwise;

- if only CSI part 1 and CSI part 2 are present for transmission on the PUSCH without UL-SCH, let

3GPP
Release 17 40 3GPP TS 38.212 V17.5.0 (2023-03)

- ;

- GCSI-part1 (2)=GCSI-part1−G CSI-part1 (1) ;

- GCSI-part2 (1 )=M 1⋅N L⋅Q m−GCSI-part1 (1) ; and

- GCSI-part2 (2 )=M 2⋅N L⋅Q m−GCSI-part1 (2 ) ;

PUSCH PUSCH PUSCH

- let N hop =2 , and denote N symb,hop (1) , N symb,hop (2 ) as the number of OFDM symbols of the PUSCH in the first
and second hop, respectively;

- N L is the number of transmission layers of the PUSCH;

-
Qm is the modulation order of the PUSCH;
N PUSCH
symb,hop (1 )−1

M 1= ∑ UCI
M SC (l)
- l=0 ;
PUSCH PUSCH
N symb,hop ( 1 ) +N symb,hop ( 2 ) −1

M 2= ∑ UCI
M SC (l )
- l= N PUSCH ( )
symb,hop 1

- .

If frequency hopping is not configured for the PUSCH,

(1)
- denote l as the OFDM symbol index of the first OFDM symbol after the first set of consecutive OFDM
symbol(s) carrying DMRS;
(1)
- denote l CSI as the OFDM symbol index of the first OFDM symbol that does not carry DMRS;

- if HARQ-ACK is present for transmission on the PUSCH or if both HARQ-ACK and CG-UCI are present on the
ACK
same PUSCH with UL-SCH, let G (1)=G ACK ;
CSI-part1
- if CSI is present for transmission on the PUSCH, let G (1)=GCSI-part1 and GCSI-part2 (1)=GCSI-part2 ;

- if CG-UCI is present for transmission on the PUSCH without HARQ-ACK, let G CG−UCI ( 1 )=G CG−UCI ;

PUSCH
- let N hop =1 and N PUSCH PUSCH
symb,hop (1 )=N symb,all .

g ,g ,g ,g ,..., gG−1 is obtained according to the following:

The multiplexed data and control coded bit sequence 0 1 2 3

Step 1:
PUSCH
Set for l=0 , 1, 2, . .. , N symb,all −1 ;

PUSCH
Set for l=0 , 1 , 2, . .. , N symb,all −1 ;
PUSCH
Set for l=0 , 1, 2, . .. , N symb,all −1 ;

PUSCH
Set for l=0 , 1 , 2, . .. , N symb,all −1 ;

3GPP
Release 17 41 3GPP TS 38.212 V17.5.0 (2023-03)

if the number of HARQ-ACK information bits to be transmitted on PUSCH is 0, 1 or 2 bits and without CG-UCI

the number of reserved resource elements for potential HARQ-ACK transmission is calculated according to Clause

[Link].2.1, by setting ;

denote as the number of coded bits for potential HARQ-ACK transmission using the reserved resource
elements;

if frequency hopping is configured for the PUSCH, let and

if frequency hopping is not configured for the PUSCH, let ;

rvd
denote Φ̄ l as the set of reserved resource elements for potential HARQ-ACK transmission, in OFDM symbol l ,
PUSCH
for l=0 , 1, 2, . .. , N symb,all −1 ;
ACK
Set m count (1 )=0 ;
ACK
Set mcount (2 )=0 ;
PUSCH
l =∅ for l=0 , 1 , 2, . .. , N symb,all −1 ;
Φ̄ rvd

PUSCH
for i=1 to N hop

l=l (i ) ;

while

d=1 ;

end if

end if
RE
for j =0 to m count −1

3GPP
Release 17 42 3GPP TS 38.212 V17.5.0 (2023-03)

mACK ACK
count (i)=m count (i)+N L⋅Q m ;

end for

end if

l=l +1 ;

end while

end for

else
PUSCH
l =∅ for l=0 , 1 , 2, . .. , N symb,all −1 ;
Φ̄ rvd

end if

Denote
M̄ Φ̄sc, rvd (l ) =|Φ̄lrvd| as the number of elements in Φ̄ rvd
l .

Step 2:

if HARQ-ACK is present for transmission on the PUSCH and the number of HARQ-ACK information bits is more than
2 or if both HARQ-ACK and CG-UCI are present on the same PUSCH with UL-SCH,
ACK
Set m count (1 )=0 ;
ACK
Set mcount (2 )=0 ;

Set
mACK
count,all =0 ;

PUSCH
for i=1 to N hop

l=l (i ) ;

while
mACK
count (i)<G
ACK
(i)

d=1 ;

end if

count =⌈ ( G
mRE (i )) / ( N L⋅Qm ) ⌉
ACK ACK
(i)−mcount
;

3GPP
Release 17 43 3GPP TS 38.212 V17.5.0 (2023-03)

end if
RE
for j =0 to m count −1

for v=0 to
N L⋅Qm−1
ACK
ḡl , k , v =gm ACK
count, all ;

mACK ACK
count,all =m count,all +1 ;

mACK ACK
count (i)=m count (i)+1 ;

end for

;
RE
for j =0 to m count −1

end for

end if

l=l +1 ;

end while

end for

end if

Step 2A:

If CG-UCI is present for transmission on the PUSCH without HARQ-ACK,

CG−UCI
Set m count (1 )=0;
CG−UCI
Set m count ( 2 )=0;
CG−UCI
Set m count , all =0 ;

3GPP
Release 17 44 3GPP TS 38.212 V17.5.0 (2023-03)

PUSCH
for i=1 to N hop

(i )
l=l ;
CG−UCI
while m count (i ) <GCG−UCI (i )
UCI
if M sc ( l ) >0
CG−UCI CG−UCI
if G (i)−mcount ( 1 ) ≥ M UCI
sc ( l ) . N L .Q m

d=1;
ℜ UCI
mcount =M sc ( l ) ;
end if
CG−UCI CG−UCI
if G (i)−mcount ( 1 ) < M UCI
sc ( l ) . N L . Q m

d=⌊ M UCI
sc
( l ) . N L . Qm / ( GCG−UCI (i)−mCG−UCI
count
(i ) ) ⌋ ;

mℜcount =⌈ ( GCG−UCI (i)−mCG−UCI

count
( i )) / ( N L .Q m ) ⌉ ;
end if
ℜ
for j=0 to m count −1
UCI
k =Φl ( j . d) ;

for v=0 to N L .Q m−1

CG−UCI
gl , k ,v =g m CG−UCI
count ,all
;

CG−UCI CG−UCI
mcount , all =mcount , all +1;
CG−UCI
mcount (i ) =mCG−UCI
count ( i ) +1;
end for

end for
UCI
Φ l ,tmp =∅ ;
ℜ
for j=0 to m count −1
UCI UCI UCI
Φ l ,tmp =Φl ,tmp ∪Φ l ( j. d );
end for
UCI UCI UCI
Φ l =Φ l {Φ ¿ l ,tmp;
UL−SCH UL−SCH UCI
Φl =Φl {Φ ¿l , tmp;

sc ( l ) =|Φ l |;
M UCI UCI

M UL−
sc
SCH
( l )=|ΦUL−SCH
l |;
end if

3GPP
Release 17 45 3GPP TS 38.212 V17.5.0 (2023-03)

l=l+1;
end while

end for

end if

Step 3:

if CSI is present for transmission on the PUSCH,

CSI-part1
Set mcount (1)=0 ;
CSI-part1
Set m count (2 )=0 ;

Set
mCSI-part1
count,all =0 ;

PUSCH
for i=1 to N hop

l=l (iCSI
)
;

while

l=l +1 ;

end while

while
mCSI-part1
count (i)<G
CSI-part1
(i )

d=1 ;

end if

count =⌈ ( G
mRE (i) ) / ( N L⋅Qm ) ⌉
CSI-part1
(i )−mCSI-part1
count ;

end if

;
RE
for j =0 to m count −1

3GPP
Release 17 46 3GPP TS 38.212 V17.5.0 (2023-03)

for v=0 to
N L⋅Qm−1
CSI-part1
ḡl , k , v =gmCSI-part1
count, all ;

mCSI-part1 CSI-part1
count,all =mcount,all +1 ;

mCSI-part1
count (i)=mCSI-part1
count (i)+1 ;

end for

;
RE
for j =0 to m count −1

end for

end if

l=l +1 ;

end while

end for

CSI-part2
Set mcount (1)=0 ;
CSI-part2
Set m count (2 )=0 ;

Set
mCSI-part2
count,all =0 ;

PUSCH
for i=1 to N hop

l=l (iCSI
)
;

while

l=l +1 ;

3GPP
Release 17 47 3GPP TS 38.212 V17.5.0 (2023-03)

end while

while
mCSI-part2
count (i)<G
CSI-part2
(i )

d=1 ;

end if

count =⌈ ( G
m RE (i) ) / ( N L⋅Q m ) ⌉
CSI-part2
(i )−mCSI-part2
count ;

end if
RE
for j =0 to m count −1

for v=0 to
N L⋅Qm−1

ḡl , k , v =gCSI-part2
mCSI-part2
count, all ;

mCSI-part2 CSI-part2
count,all =mcount,all +1 ;

mCSI-part2
count (i)=mCSI-part2
count (i)+1 ;

end for

;
RE
for j =0 to m count −1

end for

3GPP
Release 17 48 3GPP TS 38.212 V17.5.0 (2023-03)

end if

l=l +1 ;

end while

end for

end if

Step 4:

if UL-SCH is present for transmission on the PUSCH,

UL−SCH
Set m count =0 ;

PUSCH
for l=0 to N symb,all −1

for j =0 to

for v=0 to
N L⋅Qm−1

ḡl , k , v =gmUL−SCH
UL−SCH
count ;

mUL−SCH
count =mUL−SCH
count +1 ;

end for

end if

end for

end if

Step 5:

if HARQ-ACK is present for transmission on the PUSCH without CG-UCI and the number of HARQ-ACK information
bits is no more than 2,
ACK
Set mcount (1 )=0 ;
ACK
Set m count (2 )=0 ;

Set
mACK
count,all =0 ;

PUSCH
for i=1 to N hop

3GPP
Release 17 49 3GPP TS 38.212 V17.5.0 (2023-03)

l=l (i ) ;

while
mACK
count (i)<G
ACK
(i)

d=1 ;

end if

count =⌈ ( G
mRE (i )) / ( N L⋅Qm ) ⌉
ACK ACK
(i)−mcount
;

end if
RE
for j =0 to m count −1

for v=0 to
N L⋅Qm−1
ACK
ḡl , k , v =gm ACK
count, all ;

mACK ACK
count,all =m count,all +1 ;

mACK ACK
count (i)=m count (i)+1 ;

end for

end if

l=l +1 ;

end while

end for

end if

Step 6:

Set t =0 ;

3GPP
Release 17 50 3GPP TS 38.212 V17.5.0 (2023-03)

PUSCH
for l=0 to N symb,all −1

for j =0 to

for v=0 to
N L⋅Qm−1

gt = ḡl , k , v ;

t =t + 1 ;

end for

6.3 Uplink control information

6.3.1 Uplink control information on PUCCH
The procedure in this clause applies to PUCCH formats 2/3/4.

The following clauses [Link], [Link] and [Link] apply regardless of whether the higher layer parameter uci-
MuxWithDiffPrio is configured or not. The following clauses [Link], [Link] and [Link] apply by assuming uci-
MuxWithDiffPrio is not configured, or uci-MuxWithDiffPrio is configured and the UCIs for transmission on a PUCCH
are of the same priority index, unless stated otherwise.

If the UE is configured with a PUCCH-SCell, uci-MuxWithDiffPrio is replaced by uci-

MuxWithDiffPrioSecondaryPUCCHgroup for the secondary PUCCH group in this clause.

[Link] UCI bit sequence generation

[Link].1 HARQ-ACK/SR only
a 0 , a1 , a 2 , a 3 ,..., a A1
If only HARQ-ACK bits are transmitted on a PUCCH, the UCI bit sequence is determined by
ai  o~i ACK o~0ACK , o~1ACK ,..., o~OACK
for i  0, 1, ..., O  1 and A  O ACK ACK ACK
setting , where the HARQ-ACK bit sequence 1

is given by Clause 9.1 of [5, TS38.213].

a 0 , a1 , a 2 , a 3 ,..., a A1
If only HARQ-ACK and SR bits are transmitted on a PUCCH, the UCI bit sequence is
ai  o~i ACK
  ~ SR
    1 , and
, a i=oi −O ACK for
ACK ACK ACK ACK SR
determined by setting for i 0, 1, ..., O 1 i O , O 1,..., O O
~ ACK ~ ACK ~ ACK
A  O ACK  O SR , where the HARQ-ACK bit sequence o0 , o1 ,..., oO ACK 1 is given by Clause 9.1 of [5, TS 38.213],
o~0SR , o~1SR ,..., o~OSRSR 1
and the SR bit sequence is given by Clause [Link] of [5, TS 38.213].

[Link].2 CSI only

If cqi-BitsPerSubband is configured, this Clause [Link].2 applies by taking Subband CQI as Subband differential CQI
and replacing the corresponding number of bits 2 by 4.

The bitwidth for PMI of codebookType=typeI-SinglePanel with 2 CSI-RS ports is 2 for Rank=1 and 1 for Rank=2,
according to Clause [Link].1 in [6, TS 38.214].

The bitwidth for PMI of codebookType=typeI-SinglePanel with more than 2 CSI-RS ports is provided in Tables
N , N  O ,O 
[Link].2-1, where the values of 1 2 and 1 2 are given by Clause [Link].1 in [6, TS 38.214].

3GPP
Release 17 51 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-1: PMI of codebookType=typeI-SinglePanel

X
Information field 2 for wideband
X
Information field 1 for wideband PMI PMI
or per subband PMI

i
( 1, 1 ,
i 1, 2 )

codebookMode=1 codebookMode=2 codebookMode=1 codebookMode=2

Rank = 1 with >2

CSI-RS ports, ( , ( ,
N/A 2 4
N 2> 1
)
)

Rank = 1 with >2

CSI-RS ports,
N 2 =1
( ,

) (
⌈log 2 ( )
N 1 O1
2
⌉
, 0)
N/A 2 4

Rank=2 with 4
CSI-RS ports,
N 2 =1
(

)
,
(
⌈log 2 ( )
N 1 O1
2
⌉
, 0)
1 1 3

Rank=2 with >4

CSI-RS ports, ( , ( ,
2 1 3
N 2> 1
)
)

Rank=2 with >4

CSI-RS ports,
N 2 =1
( ,

) (
⌈log 2 ( )
N 1 O1
2
⌉
, 0)
2 1 3

Rank=3 or 4,
with 4 CSI-RS 0 1
( , )
ports

Rank=3 or 4,
with 8 or 12 CSI- 2 1
( , )
RS ports

Rank=3 or 4 ,
with >=16 CSI- 2 1
RS ports ( , )

Rank=5 or 6 N/A 1
( , )

Rank=7 or 8,
N/A 1
( , )

3GPP
Release 17 52 3GPP TS 38.212 V17.5.0 (2023-03)

Rank=7 or 8,
with

or N/A 1
( , )
or

The bitwidth for PMI of codebookType= typeI-MultiPanel is provided in Tables [Link].2-2, where the values of

and (
O1 ,O2 )
are given by Clause [Link].2 in [6, TS 38.214].

Table [Link].2-2: PMI of codebookType= typeI-MultiPanel

Information fields
X2
X
Information fields 1 for wideband for wideband
or per subband

i i 1, 2 )
( 1, 1 , i1,3 i1,4 ,1 i1,4 ,2 i1,4 ,3 i2,0 i2,1 i2,2

Rank=1 with g
N =2 ( ,
N/A 2 N/A N/A 2 N/A N/A N/A
codebookMode=1
)

Rank=1 with g
N =4 ( ,
N/A 2 2 2 2 N/A N/A N/A
codebookMode=1
)

Rank=2 with
N g =2 ,
( ,
1 2 N/A N/A 1 N/A N/A N/A

codebookMode=1 )

Rank=3 or 4 with
N g =2 ,
( ,
0 2 N/A N/A 1 N/A N/A N/A

codebookMode=1 )

Rank=2 or 3 or 4 with
N g =2 ,
( ,
2 2 N/A N/A 1 N/A N/A N/A

codebookMode=1 )

Rank=2 with
N g =4 ,
( ,
1 2 2 2 1 N/A N/A N/A

codebookMode=1 )

Rank=3 or 4 with
N g =4 ,
( ,
0 2 2 2 1 N/A N/A N/A

codebookMode=1 )

Rank=2 or 3 or 4 with
N g =4 , ( ,
2 2 2 2 1 N/A N/A N/A

3GPP
Release 17 53 3GPP TS 38.212 V17.5.0 (2023-03)

codebookMode=1 )

Rank=1 with g
N =2 ( ,
N/A 2 2 N/A N/A 2 1 1
codebookMode=2
)

Rank=2 with
N g =2 ,
( ,
1 2 2 N/A N/A 1 1 1

codebookMode=2 )

Rank=3 or 4 with
N g =2 ,
( ,
0 2 2 N/A N/A 1 1 1

codebookMode=2 )

Rank=2 or 3 or 4 with
N g =2 ,
( ,
2 2 2 N/A N/A 1 1 1

codebookMode=2 )

The bitwidth for PMI with 1 CSI-RS port is 0.

The bitwidth for RI/LI/CQI/CRI of codebookType=typeI-SinglePanel or reportQuantity set to 'cri-RI-CQI' is provided

in Tables [Link].2-3.

Table [Link].2-3: RI, LI, CQI, and CRI of codebookType=typeI-SinglePanel, or reportQuantity set to
'cri-RI-CQI'

Bitwidth
Field 2 antenna >4 antenna ports
1 antenna port 4 antenna ports
ports Rank1~4 Rank5~8
Rank Indicator when ⌈log 2 n RI ⌉ ⌈log 2 n RI ⌉
codebookType=typeI- 0 min ( 1 ,⌈log 2 n RI⌉ ) min ( 2 ,⌈log 2 n RI⌉ )
SinglePanel
Rank Indicator when
reportQuantity set to 0 1 2 3 3
'cri-RI-CQI'
Layer Indicator 0
Wide-band CQI for the
4 4 4 4 4
first TB
Wideband CQI for the
0 0 0 0 4
second TB
Subband differential CQI
2 2 2 2 2
for the first TB
Subband differential CQI
0 0 0 0 2
for the second TB
CRI (
⌈log 2 K CSI−RS
s )⌉ (
⌈log 2 K CSI−RS
s )⌉ (
⌈log 2 K CSI−RS
s )⌉ (
⌈log2 K CSI−RS
s )⌉ ⌈log 2 ( K CSI−RS
s )⌉
n RI in Table [Link].2-3 is the number of allowed rank indicator values according to Clause [Link].1 [6, TS 38.214].

is the value of the rank. The value of s

K CSI−RS is the number of CSI-RS resources in the corresponding resource set.
The values of the rank indicator field are mapped to allowed rank indicator values with increasing order, where '0' is
mapped to the smallest allowed rank indicator value. For higher layer parameter reportQuantity set to 'cri-RI-CQI', the
values of the rank indicator field are mapped to rank indicator values with increasing order, where '0' is mapped to rank-
1.

3GPP
Release 17 54 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-3A: RI, LI, CQI, and CRI associated with one CSI-RS resource pair and csi-
ReportMode= Mode 1 or Mode 2

Bitwidth
Field 1 antenna port per >1 antenna ports
Resource per Resource
Rank Combination Indicator 0 min(2, ⌈ log 2 nRI , NCJT ⌉ )
The first Layer Indicator 0 ⌈ log 2 ( v 1 ) ⌉
The second Layer Indicator 0 ⌈ log 2 ( v 2 ) ⌉
Wide-band CQI for the first TB 4 4
Subband differential CQI for the first TB 2 2
CRI if csi-ReportMode= Mode 1 ⌈ log 2 N ⌉ ⌈ log 2 N ⌉
CRI if csi-ReportMode= Mode 2 ⌈ log 2 ( M 1+ M 2 + N ) ⌉ ⌈ log 2 ( M 1+ M 2 + N ) ⌉

Table [Link].2-3B: RI, LI, CQI, and CRI associated with one CSI-RS resource and csi-ReportMode=
Mode 1 or Mode 2

Bitwidth
Field >4 antenna ports
1 antenna port 2 antenna ports 4 antenna ports
Rank1~4 Rank5~8
Rank Indicator 0 min( 1, ⌈ log 2 nRI ,min(
sTRP ⌉) ⌈ log⌉)2 nRI , sTRP ⌉ ⌈ log 2 nRI , sTRP ⌉
2, ⌈ log 2 nRI , sTRP
Layer Indicator 0 ⌈ log 2 ( v ) ⌉ min ⁡(2 , ⌈ log 2 ( v ) ⌉min
) ⁡(2 , ⌈ log 2 ( v ) ⌉min
) ⁡(2 , ⌈ log 2 ( v ) ⌉ )
Wide-band CQI
4 4 4 4 4
for the first TB
Wideband CQI for
0 0 0 0 4
the second TB
Subband
differential CQI for 2 2 2 2 2
the first TB
Subband
differential CQI for 0 0 0 0 2
the second TB
CRI if csi-
ReportMode=
Mode 1 and
numberOfSingleT
⌈ log 2 ( M 1+ M 2 ) ⌉⌈ log 2 ( M 1+ M 2 ) ⌉⌈ log 2 ( M 1+ M 2 ) ⌉⌈ log 2 ( M 1+ M 2 ) ⌉⌈ log 2 ( M 1+ M 2 ) ⌉
RP-CSI-Mode1 =
1
CRI if csi- ⌈ log 2 ( M 1) ⌉ ⌈ log 2 ( M 1) ⌉ ⌈ log 2 ( M 1) ⌉ ⌈ log 2 ( M 1) ⌉ ⌈ log 2 ( M 1) ⌉ for
ReportMode=
for the first CRI; for the first CRI; for the first CRI; for the first CRI;
Mode 1 and the first CRI;
numberOfSingleT ⌈ log 2 ( M 2) ⌉ ⌈ log 2 ( M 2) ⌉ ⌈ log 2 ( M 2) ⌉ ⌈ log 2 ( M 2) ⌉ ⌈ log 2 ( M 2) ⌉ for
RP-CSI-Mode1 = for the second for the second for the second for the second
2 the second CRI
CRI CRI CRI CRI
CRI if csi-
ReportMode= ⌈ log 2 ( M 1+ M 2 + N ) ⌉ 2 ( M 1+ M 2 + N⌈ log
⌈ log ) ⌉ 2 ( M 1+ M 2 + N⌈ log
) ⌉ 2 ( M 1+ M 2 + N⌈ log
) ⌉ 2 ( M 1+ M 2 + N ) ⌉
Mode 2

n RI , NCJT in Table [Link].2-3A is the number of allowed rank combination indicator values associated with one CSI-RS
resource pair according to Clause [Link].1X [6, TS 38.214]. The values of the rank combination indicator field are
mapped to allowed rank combinations in the following order: {1,1}, {1,2}, {2,1},{2,2}, where '0' is mapped to {1,1}.
v 1 and v 2 are the values of the first and the second rank associated with two CSI-RS resources of the CSI-RS resource
pair respectively.

n RI , sTRP in Table [Link].2-3B is the number of allowed rank indicator values associated with one CSI-RS resource
according to Clause [Link].1X [6, TS 38.214]. v is the value of the rank associated with the CSI-RS resource. The

3GPP
Release 17 55 3GPP TS 38.212 V17.5.0 (2023-03)

values of the rank indicator field are mapped to allowed rank indicator values with increasing order, where '0' is mapped
to the smallest allowed rank indicator value.

The value of N in Table [Link].2-3A and Table [Link].2-3B is the number of CSI-RS resource pairs configured within
a CSI-RS resource set. The values of M1 and M2 in Table [Link].2-3A and Table [Link].2-3B are given by

- If sharedCMR = "Enabled", M1 = K1 and M2 = K2

- If sharedCMR is absent and N = 1, M1 = K1 - 1 and M2 = K2 – 1

- If sharedCMR is absent and N = 2,

- M1 = K1 - 2 and M2 = K2 – 2, if the two resource pairs do not share any CSI-RS resource

- M1 = K1 - 1 and M2 = K2 – 2, if the two resource pairs share the same CSI-RS resource from the first CSI-RS
resource group

- M1 = K1 - 2 and M2 = K2 – 1, if the two resource pairs share the same CSI-RS resource from the second CSI-
RS resource group

where the values of K1 and K2 are the numbers of CSI-RS resources in the first and second CSI-RS resource groups
within the CSI-RS resource set respectively.

The bitwidth for RI/LI/CQI/CRI of codebookType= typeI-MultiPanel is provided in Table [Link].2-4.

Table [Link].2-4: RI, LI, CQI, and CRI of codebookType=typeI-MultiPanel

Field Bitwidth

Rank Indicator min ( 2 ,⌈log 2 n RI⌉ )

Layer Indicator
Wide-band CQI 4
Subband differential
2
CQI
CRI ⌈log 2 ( K CSI−RS
s )⌉
where n RI is the number of allowed rank indicator values according to Clause [Link].2 [6, TS 38.214], is the value
K CSI−RS is the number of CSI-RS resources in the corresponding resource set. The values of the rank
of the rank, and s
indicator field are mapped to allowed rank indicator values with increasing order, where '0' is mapped to the smallest
allowed rank indicator value.

The bitwidth for RI/LI/CQI of codebookType= typeII or codebookType=typeII-PortSelection is provided in Table

[Link].2-5.

Table [Link].2-5: RI, LI, and CQI of codebookType=typeII or typeII-PortSelection

Field Bitwidth

Rank Indicator min ( 1 ,⌈log2 n RI⌉ )

Layer Indicator
Wide-band CQI 4
Subband differential CQI 2
Indicator of the number of non-zero
M l for layer l ⌈log 2 ( 2 L−1 ) ⌉
wideband amplitude coefficients

3GPP
Release 17 56 3GPP TS 38.212 V17.5.0 (2023-03)

where n RI is the number of allowed rank indicator values according to Clauses [Link].3 and [Link].4 [6, TS 38.214]
and is the value of the rank. The values of the rank indicator field are mapped to allowed rank indicator values with
increasing order, where '0' is mapped to the smallest allowed rank indicator value.

The bitwidth for CRI, SSBRI, RSRP, differential RSRP, and CapabilityIndex are provided in Table [Link].2-6.

Table [Link].2-6: CRI, SSBRI, RSRP, and CapabilityIndex

Field Bitwidth

CRI ⌈log 2 ( K CSI−RS

s )⌉
SSBRI ⌈log 2 ( K SSB
s )⌉
RSRP 7
Differential RSRP 4
CapabilityIndex 2

where s
K CSI−RSis the number of CSI-RS resources in the corresponding resource set, and
K SSB
s is the configured
number of SS/PBCH blocks in the corresponding resource set for reporting 'ssb-Index-RSRP'.

The bitwidth for CRI, SSBRI, SINR, differential SINR, and CapabilityIndex are provided in Table [Link].2-6A.

Table [Link].2-6A: CRI, SSBRI, SINR, and CapabilityIndex

Field Bitwidth

CRI ⌈ log 2 ( K CSI−

s
RS
)⌉
SSBRI ⌈ log 2 ( K SSB
s )⌉
SINR 7
Differential SINR 4
CapabilityIndex 2
CSI −RS SSB
where K s is the number of CSI-RS resources in the corresponding resource set, and K s is the configured
number of SS/PBCH blocks in the corresponding resource set for reporting 'ssb-Index-SINR'.

Table [Link].2-7: Mapping order of CSI fields of one CSI report, pmi-FormatIndicator=widebandPMI
and cqi-FormatIndicator=widebandCQI or reportQuantity set to 'cri-RI-CQI' and cqi-
FormatIndicator=widebandCQI

CSI report
CSI fields
number
CRI as in Tables [Link].2-3/4, if reported
Rank Indicator as in Tables [Link].2-3/4, if reported
Layer Indicator as in Tables [Link].2-3/4, if reported

Zero padding bits

O P , if needed
CSI report #n
PMI wideband information fields
X 1 , from left to right as in Tables [Link].2-1/2, if reported
PMI wideband information fields
X
2 , from left to right as in Tables [Link].2-1/2, or codebook
index for 2 antenna ports according to Clause [Link].1 in [6, TS38.214], if reported
Wideband CQI for the first TB as in Tables [Link].2-3/4, if reported
Wideband CQI for the second TB as in Tables [Link].2-3/4, if reported

3GPP
Release 17 57 3GPP TS 38.212 V17.5.0 (2023-03)

The number of zero padding bits O P in Table [Link].2-7 is 0 for 1 CSI-RS port and
O P=N max −N reported for more than
1 CSI-RS port, where
N max = max B ( r )
- r ∈ S Rank
and
SRank is the set of rank values r that are allowed to be reported;

-
N reported =B ( R ) , where R is the reported rank;

- For 2 CSI-RS ports,

B ( r )=N PMI ( r )+N CQI ( r ) +N LI ( r ) ;

- For more than 2 CSI-RS ports,

B ( r )=N PMI,i1 ( r ) +N PMI,i2 ( r ) +N CQI ( r ) +N LI ( r ) ;

- if PMI is reported, N PMI ( 1 )=2 and N PMI ( 2 ) =1 ; otherwise, N PMI ( r )=0 ;

- if PMI i1 is reported,
N PMI,i1 ( r ) is obtained according to Tables [Link].2-1/2; otherwise, N PMI,i1 ( r )=0 ;

- if PMI i 2 is reported,
N PMI,i2 ( r ) is obtained according to Tables [Link].2-1/2; otherwise, N PMI,i2 ( r )=0 ;

- if CQI is reported,
N CQI ( r ) is obtained according to Tables [Link].2-3/4; otherwise, N CQI ( r )=0 ;

- if LI is reported, N LI ( r ) is obtained according to Tables [Link].2-3/4; otherwise, N LI ( r )=0 .

Table [Link].2-7A: Mapping order of CSI fields of one CSI report, pmi-FormatIndicator=widebandPMI,
cqi-FormatIndicator=widebandCQI, csi-ReportMode= Mode 1 and numberOfSingleTRP-CSI-Mode1=0

CSI report
CSI fields
number
CRI as in Tables [Link].2-3A, if reported
Rank Combination Indicator as in Tables [Link].2-3A, if reported
Two Layer Indicators as in Table [Link].2-3A, where the first Layer Indicator and the second
Layer Indicator are associated with the first resource and the second resource within the
resource pair respectively and if reported;
Zero padding bits O P, if needed
PMI wideband information fields X1, from left to right as in Tables [Link].2-1 associated with
the first resource within the CSI-RS resource pair, if reported
CSI report #n PMI wideband information fields X2, from left to right as in Tables [Link].2-1, or codebook
index for 2 antenna ports according to Clause [Link].1 in [6, TS38.214] associated with the
first CSI-RS resource within the CSI-RS resource pair, if reported
PMI wideband information fields X1, from left to right as in Tables [Link].2-1 associated with
the second resource within the CSI-RS resource pair, if reported
PMI wideband information fields X2, from left to right as in Tables [Link].2-1, or codebook
index for 2 antenna ports according to Clause [Link].1 in [6, TS38.214] associated with the
second CSI-RS resource within the CSI-RS resource pair, if reported
Wideband CQI for the first TB as in Tables [Link].2-3A, if reported

The number of zero padding bits O P in Table [Link].2-7A is 0 for 1 CSI-RS port and O P=N max −N reported for more
than 1 CSI-RS port, where

- N max = max B (r ) and S is the set of rank combination values of r ={r 1 , r 2 } that are allowed to be
r ∈ SRank Rank

reported;

- N reported =B (R) where R is the reported rank combination;

- For 2 CSI-RS ports, B ( r )=N PMI (r 1)+ N PMI (r 2 )+ N CQI ( r ) + N LI (r 1 )+ N LI (r 2 );

3GPP
Release 17 58 3GPP TS 38.212 V17.5.0 (2023-03)

- For more than 2 CSI-RS ports,

B ( r )=N PMI ,i (r 1 )+ N PMI ,i (r 2)+ N PMI ,i (r 1)+ N PMI ,i (r 2)+ N CQI ( r ) + N LI ( r 1)+ N LI (r 2) ;
1 1 2 2

- if PMI is reported, N PMI ( 1 )=2 and N PMI ( 2 ) =1; otherwise, N PMI =0;

- if PMI i 1 is reported, N PMI ,i1 (r 1 ) and N PMI ,i1 (r 2 ) are obtained according to Tables [Link].2-1; otherwise,
N PMI ,i =0 ;
1

- if PMI i 2 is reported, N PMI ,i2 (r 1 ) and N PMI ,i2 (r 2 ) are obtained according to Tables [Link].2-1; otherwise,
N PMI ,i =0 ;
2

- if CQI is reported, N CQI ( r ) is obtained according to Tables [Link].2-3A; otherwise, N CQI ( r ) =0;

- if LI is reported, N LI (r 1 ) and N LI (r 2) are obtained according to Tables [Link].2-3A; otherwise , N LI =0.

Table [Link].2-8: Mapping order of CSI fields of one report for CRI/RSRP or SSBRI/RSRP or
CRI/RSRP/CapabilityIndex or SSBRI/RSRP/CapabilityIndex reporting, or mapping order of CSI fields
of one report for inter-cell SSBRI/RSRP reporting

CSI report
CSI fields
number
CRI or SSBRI #1 as in Table [Link].2-6, if reported
CRI or SSBRI #2 as in Table [Link].2-6, if reported
CRI or SSBRI #3 as in Table [Link].2-6, if reported
CRI or SSBRI #4 as in Table [Link].2-6, if reported
RSRP #1 as in Table [Link].2-6, if reported
Differential RSRP #2 as in Table [Link].2-6, if reported
CSI report #n
Differential RSRP #3 as in Table [Link].2-6, if reported
Differential RSRP #4 as in Table [Link].2-6, if reported
CapabilityIndex #1 as in Table [Link].2-6, if reported
CapabilityIndex #2 as in Table [Link].2-6, if reported
CapabilityIndex #3 as in Table [Link].2-6, if reported
CapabilityIndex #4 as in Table [Link].2-6, if reported

Table [Link].2-8A: Mapping order of CSI fields of one report for CRI/SINR or SSBRI/SINR or
CRI/SINR/CapabilityIndex or SSBRI/SINR/CapabilityIndex reporting

CSI report
CSI fields
number
CRI or SSBRI #1 as in Table [Link].2-6A, if reported
CRI or SSBRI #2 as in Table [Link].2-6A, if reported
CRI or SSBRI #3 as in Table [Link].2-6A, if reported
CRI or SSBRI #4 as in Table [Link].2-6A, if reported
SINR #1 as in Table [Link].2-6A, if reported
Differential SINR #2 as in Table [Link].2-6A, if reported
CSI report #n
Differential SINR #3 as in Table [Link].2-6A, if reported
Differential SINR #4 as in Table [Link].2-6A, if reported
CapabilityIndex #1 as in Table [Link].2-6, if reported
CapabilityIndex #2 as in Table [Link].2-6, if reported
CapabilityIndex #3 as in Table [Link].2-6, if reported
CapabilityIndex #4 as in Table [Link].2-6, if reported

3GPP
Release 17 59 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-8B: Mapping order of CSI fields of one report for group-based CRI/RSRP or
SSBRI/RSRP reporting

CSI report
CSI fields
number
Resource set indicator
CRI or SSBRI #1 of 1st resource group as in Table [Link].2-6, if reported
CRI or SSBRI #2 of 1st resource group as in Table [Link].2-6, if reported
CRI or SSBRI #1 of 2nd resource group as in Table [Link].2-6, if reported
CRI or SSBRI #2 of 2nd resource group as in Table [Link].2-6, if reported
CRI or SSBRI #1 of 3rd resource group as in Table [Link].2-6, if reported
CRI or SSBRI #2 of 3rd resource group as in Table [Link].2-6, if reported
CRI or SSBRI #1 of 4th resource group as in Table [Link].2-6, if reported
CSI report #n CRI or SSBRI #2 of 4th resource group as in Table [Link].2-6, if reported
RSRP of CRI or SSBRI #1 of 1st resource group as in Table [Link].2-6
Differential RSRP of CRI or SSBRI #2 of 1st resource group as in Table [Link].2-6
Differential RSRP of CRI or SSBRI #1 of 2nd resource group as in Table [Link].2-6, if reported
Differential RSRP of CRI or SSBRI #2 of 2nd resource group as in Table [Link].2-6, if reported
Differential RSRP of CRI or SSBRI #1 of 3rd resource group as in Table [Link].2-6, if reported
Differential RSRP of CRI or SSBRI #2 of 3rd resource group as in Table [Link].2-6, if reported
Differential RSRP of CRI or SSBRI #1 of 4th resource group as in Table [Link].2-6, if reported
Differential RSRP of CRI or SSBRI #2 of 4th resource group as in Table [Link].2-6, if reported
where the 1-bit resource set indicator, with value of 0 or 1, indicates the 1 st or the 2nd channel measurement resource set
respectively, from which CRI or SSBRI #1 of 1st resource group is reported from; and all remaining resource groups, if
reported, follow the same mapping order as the 1st resource group where CRI or SSBRI #1 of all remaining resource
groups is reported from the indicated channel measurement resource set. For all reported resource groups, CRI or
SSBRI #1 and CRI or SSBRI #2 are reported from different channel measurement resource sets.

Table [Link].2-9: Mapping order of CSI fields of one CSI report, CSI part 1, pmi-FormatIndicator=
subbandPMI or cqi-FormatIndicator=subbandCQI

CSI report number CSI fields

CRI as in Tables [Link].2-3/4, if reported

Rank Indicator as in Tables [Link].2-3/4/5, if reported
Wideband CQI for the first TB as in Tables [Link].2-3/4/5, if reported
Subband differential CQI for the first TB with increasing order of subband number as in
Tables [Link].2-3/4/5, if reported
CSI report #n Indicator of the number of non-zero wideband amplitude coefficients M 0 for layer 0 as in
CSI part 1
Table [Link].2-5, if reported
Indicator of the number of non-zero wideband amplitude coefficients M 1 for layer 1 as in
Table [Link].2-5 (if the rank according to the reported RI is equal to one, this field is set to all
zeros), if 2-layer PMI reporting is allowed according to the rank restriction in Clauses [Link].3
and [Link].4 [6, TS 38.214] and if reported
Note: Subbands for given CSI report n indicated by the higher layer parameter csi-ReportingBand with value set
to '1' are numbered continuously in the increasing order with the lowest subband of csi-ReportingBand with
value set to '1' as subband 0.

3GPP
Release 17 60 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-9A: Mapping order of CSI fields of one CSI report, CSI part 1, csi-ReportMode= Mode 1

CSI report number CSI fields

CRI as in Tables [Link].2-3A, if associated with one CSI-RS resource pair and if reported
Rank Combination Indicator as in Tables [Link].2-3A, if reported
Wideband CQI for the first TB as in Tables [Link].2-3A, if reported
Subband differential CQI for the first TB with increasing order of subband number as in
Tables [Link].2-3A, if reported
CRI as in Tables [Link].2-3B, if associated with one CSI-RS resource, numberOfSingleTRP-
CSI-Mode1 = 1 and if reported;
First CRI as in Tables [Link].2-3B, if associated with one CSI-RS resource,
numberOfSingleTRP-CSI-Mode1 = 2 and if reported
Rank Indicator associated with CRI as in Tables [Link].2-3B, if numberOfSingleTRP-CSI-
Mode1 = 1 and if reported;
Rank Indicator associated with the first CRI as in Tables [Link].2-3B, if
numberOfSingleTRP-CSI-Mode1 = 2 and if reported
Wideband CQI associated with CRI for the first TB as in Tables [Link].2-3B, if
numberOfSingleTRP-CSI-Mode1 = 1 and if reported;
CSI report #n
Wideband CQI associated with the first CRI for the first TB as in Tables [Link].2-3B, if
CSI part 1
numberOfSingleTRP-CSI-Mode1 = 2 and if reported
Subband differential CQI associated with CRI for the first TB with increasing order of subband
number as in Tables [Link].2-3B, if numberOfSingleTRP-CSI-Mode1 = 1 if reported;
Subband differential CQI associated with the first CRI for the first TB with increasing order of
subband number as in Tables [Link].2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if
reported
Second CRI as in Tables [Link].2-3B, if associated with one CSI-RS resource,
numberOfSingleTRP-CSI-Mode1 = 2 and if reported
Rank Indicator associated with the second CRI as in Tables [Link].2-3B, if
numberOfSingleTRP-CSI-Mode1 = 2 and if reported
Wideband CQI associated with the second CRI for the first TB as in Tables [Link].2-3B, if
numberOfSingleTRP-CSI-Mode1 = 2 and if reported
Subband differential CQI associated with the second CRI for the first TB with increasing order
of subband number as in Tables [Link].2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if
reported
Note: Subbands for given CSI report n indicated by the higher layer parameter csi-ReportingBand with value set
to '1' are numbered continuously in the increasing order with the lowest subband of csi-ReportingBand with
value set to '1' as subband 0.

Table [Link].2-9B: Mapping order of CSI fields of one CSI report, CSI part 1, csi-ReportMode= Mode 2

CSI report number CSI fields

CRI as in Tables [Link].2-3A, if associated with one CSI-RS resource pair and if reported;
CRI as in Tables [Link].2-3B, if associated with one CSI-RS resource and if reported
Rank Combination Indicator as in Tables [Link].2-3A, if associated with one CSI-RS
resource pair and if reported;
Rank Indicator as in Tables [Link].2-3B, if associated with one CSI-RS resource and if
reported;
CSI report #n Zero padding bits O P, if needed
CSI part 1 Wideband CQI for the first TB as in Tables [Link].2-3A, if associated with one CSI-RS
resource pair and if reported;
Wideband CQI for the first TB as in Tables [Link].2-3B, if associated with one CSI-RS
resource and if reported
Subband differential CQI for the first TB with increasing order of subband number as in
Tables [Link].2-3A, if associated with one CSI-RS resource pair and if reported;
Subband differential CQI for the first TB with increasing order of subband number as in
Tables [Link].2-3B, if associated with one CSI-RS resource and if reported
Note: Subbands for given CSI report n indicated by the higher layer parameter csi-ReportingBand with value set
to '1' are numbered continuously in the increasing order with the lowest subband of csi-ReportingBand with
value set to '1' as subband 0.

3GPP
Release 17 61 3GPP TS 38.212 V17.5.0 (2023-03)

The number of zero padding bits O P in Table [Link].2-9B is 0 for 1 CSI-RS port and O P=N max −N reported (R) for
more than 1 CSI-RS port, where

- N max = max N (r ). S the set of rank and rank combination values r that are allowed to be reported. N ( r )
r ∈ SRank Rank is

is obtained according to Tables [Link].2-3A/3B for rank combination indicator and rank indicator respectively.

- N reported ( R ) is obtained according to Tables [Link].2-3A for rank combination indicator and R is the reported
rank combination.

- N reported (R) is obtained according to Tables [Link].2-3B for rank indicator and R is the reported rank.

Table [Link].2-10: Mapping order of CSI fields of one CSI report, CSI part 2 wideband, pmi-
FormatIndicator= subbandPMI or cqi-FormatIndicator=subbandCQI

CSI report
CSI fields
number
Wideband CQI for the second TB as in Tables [Link].2-3/4/5, if present and reported
Layer Indicator as in Tables [Link].2-3/4/5, if reported
CSI report #n
PMI wideband information fields
X 1 , from left to right as in Tables [Link].2-1/2, if reported
CSI part 2
wideband PMI wideband information fields
X 2 , from left to right as in Tables [Link].2-1/2, or codebook
index for 2 antenna ports according to Clause [Link].1 in [6, TS38.214], if pmi-
FormatIndicator= widebandPMI and if reported

3GPP
Release 17 62 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-10A: Mapping order of CSI fields of one CSI report, CSI part 2 wideband, csi-
ReportMode= Mode 1

CSI report
CSI fields
number
Two Layer Indicators as in Table [Link].2-3A, where the first Layer Indicator and the
second Layer Indicator are associated with the first resource and the second resource
within the resource pair respectively and if reported;

PMI wideband information fields

X 1 , from left to right as in Tables [Link].2-1
associated with the first resource within the CSI-RS resource pair, if reported

PMI wideband information fields

X 1 , from left to right as in Tables [Link].2-1
associated with the second resource within the CSI-RS resource pair, if reported

PMI wideband information fields

X 2 , from left to right as in Tables [Link].2-1, or
codebook index for 2 antenna ports according to Clause [Link].1 in [6, TS38.214]
associated with the second CSI-RS resource within the CSI-RS resource pair, if pmi-
FormatIndicator= widebandPMI and if reported
Wideband CQI for the second TB as in Tables [Link].2-3B, if associated with CRI in CSI
part 1, numberOfSingleTRP-CSI-Mode1 = 1 and if reported;
Wideband CQI for the second TB as in Tables [Link].2-3B, if associated with the first
CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if reported
Layer Indicator as in Table [Link].2-3B, if associated with CRI in CSI part 1,
numberOfSingleTRP-CSI-Mode1 = 1 and if reported;
Layer Indicator as in Table [Link].2-3B, if associated with the first CRI in CSI part 1,
numberOfSingleTRP-CSI-Mode1 = 2 and if reported
CSI report #n
PMI wideband information fields
X 1 , from left to right as in Tables [Link].2-1, if
CSI part 2
associated with CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 1 and if reported;
wideband
PMI wideband information fields
X 1 , from left to right as in Tables [Link].2-1, if
associated with the first CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if
reported

PMI wideband information fields

X 2 , from left to right as in Tables [Link].2-1, or
codebook index for 2 antenna ports according to Clause [Link].1 in [6, TS38.214], if
associated with CRI in CSI part 1, pmi-FormatIndicator= widebandPMI,
numberOfSingleTRP-CSI-Mode1 = 1 and if reported;

PMI wideband information fields

X 2 , from left to right as in Tables [Link].2-1, or
codebook index for 2 antenna ports according to Clause [Link].1 in [6, TS38.214], if
associated with the first CRI in CSI part 1, pmi-FormatIndicator= widebandPMI,
numberOfSingleTRP-CSI-Mode1 = 2 and if reported
Wideband CQI for the second TB as in Tables [Link].2-3B, if associated with the second
CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if reported
Layer Indicator as in Table [Link].2-3B, if associated with the second CRI in CSI part 1,
numberOfSingleTRP-CSI-Mode1 = 2 and if reported

PMI wideband information fields

X 1 , from left to right as in Tables [Link].2-1, if
associated with the second CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if
reported

PMI wideband information fields

X 2 , from left to right as in Tables [Link].2-1, or
codebook index for 2 antenna ports according to Clause [Link].1 in [6, TS38.214], if
associated with the second CRI in CSI part 1, pmi-FormatIndicator= widebandPMI,
numberOfSingleTRP-CSI-Mode1 = 2 and if reported

3GPP
Release 17 63 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-10B: Mapping order of CSI fields of one CSI report, CSI part 2 wideband, csi-
ReportMode= Mode 2

CSI report
CSI fields
number
Wideband CQI for the second TB as in Tables [Link].2-3B, if reported part 1 is
associated with one CSI-RS resource and if reported
Two Layer Indicators as in Table [Link].2-3A, if reported part 1 is associated with one
CSI-RS resource pair, where the first Layer Indicator and the second Layer Indicator are
associated with the first resource and the second resource within the resource pair
respectively and if reported;
Layer Indicator as in Table [Link].2-3B, if reported part 1 is associated with one CSI-RS
resource and if reported

PMI wideband information fields

X 1 , from left to right as in Tables [Link].2-1
associated with the first resource within the CSI-RS resource pair, if reported part 1 is
associated with one CSI-RS resource pair and if reported

PMI wideband information fields

X 2 , from left to right as in Tables [Link].2-1, or
codebook index for 2 antenna ports according to Clause [Link].1 in [6, TS38.214]
associated with the first CSI-RS resource within the CSI-RS resource pair, if pmi-
FormatIndicator= widebandPMI and reported part 1 is associated with one CSI-RS
CSI report #n
resource pair and if reported
CSI part 2
wideband
PMI wideband information fields
X 1 , from left to right as in Tables [Link].2-1
associated with the second CSI-RS resource within the CSI-RS resource pair, if reported
part 1 is associated with one CSI-RS resource pair and if reported

PMI wideband information fields

X 1 , from left to right as in Tables [Link].2-1, if
reported part 1 is associated with one CSI-RS resource and if reported

PMI wideband information fields

X 2 , from left to right as in Tables [Link].2-1, or
codebook index for 2 antenna ports according to Clause [Link].1 in [6, TS38.214], if
pmi-FormatIndicator= widebandPMI and reported part 1 is associated with one CSI-RS
resource and if reported

Table [Link].2-11: Mapping order of CSI fields of one CSI report, CSI part 2 subband, pmi-
FormatIndicator= subbandPMI or cqi-FormatIndicator=subbandCQI

Subband differential CQI for the second TB of all even subbands with increasing order of
subband number, as in Tables [Link].2-3/4/5, if cqi-FormatIndicator=subbandCQI and if reported

PMI subband information fields

X 2 of all even subbands with increasing order of subband
number, from left to right as in Tables [Link].2-1/2, or codebook index for 2 antenna ports
according to Clause [Link].1 in [6, TS38.214] of all even subbands with increasing order of
CSI report #n subband number, if pmi-FormatIndicator= subbandPMI and if reported
Part 2 subband Subband differential CQI for the second TB of all odd subbands with increasing order of subband
number, as in Tables [Link].2-3/4/5, if cqi-FormatIndicator=subbandCQI and if reported

PMI subband information fields

X 2 of all odd subbands with increasing order of subband
number, from left to right as in Tables [Link].2-1/2, or codebook index for 2 antenna ports
according to Clause [Link].1 in [6, TS38.214] of all odd subbands with increasing order of
subband number, if pmi-FormatIndicator= subbandPMI and if reported
Note: Subbands for given CSI report n indicated by the higher layer parameter csi-ReportingBand with value set
to '1' are numbered continuously in the increasing order with the lowest subband of csi-ReportingBand
with value set to '1' as subband 0.

3GPP
Release 17 64 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-11A: Mapping order of CSI fields of one CSI report, CSI part 2 subband, csi-
ReportMode= Mode 1

3GPP
Release 17 65 3GPP TS 38.212 V17.5.0 (2023-03)

CSI report #n
Part 2 subband PMI subband information fields
X 2 of all even subbands with increasing order of subband
number, from left to right as in Tables [Link].2-1, or codebook index for 2 antenna ports
associated with the first resource within the CSI-RS resource pair, according to Clause [Link].1
in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-
FormatIndicator= subbandPMI and if reported

PMI subband information fields

X 2 of all even subbands with increasing order of subband
number, from left to right as in Tables [Link].2-1, or codebook index for 2 antenna ports
associated with the second resource within the CSI-RS resource pair, according to Clause
[Link].1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-
FormatIndicator= subbandPMI and if reported
Subband differential CQI for the second TB of all even subbands with increasing order of
subband number associated with CRI in CSI part 1, as in Tables [Link].2-3B, if cqi-
FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 1 and if reported;
Subband differential CQI for the second TB of all even subbands with increasing order of
subband number associated with the first CRI in CSI part 1, as in Tables [Link].2-3B, if cqi-
FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported

PMI subband information fields

X 2 of all even subbands with increasing order of subband
number, from left to right as in Tables [Link].2-1, or codebook index for 2 antenna ports
associated with CRI in CSI part 1 according to Clause [Link].1 in [6, TS38.214] of all even
subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI,
numberOfSingleTRP-CSI-Mode1 = 1 and if reported;

PMI subband information fields

X 2 of all even subbands with increasing order of subband
number, from left to right as in Tables [Link].2-1, or codebook index for 2 antenna ports
associated with the first CRI in CSI part 1 according to Clause [Link].1 in [6, TS38.214] of all
even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI,
numberOfSingleTRP-CSI-Mode1 = 2 and if reported
Subband differential CQI for the second TB of all even subbands with increasing order of
subband number associated with the second CRI in CSI part 1, as in Tables [Link].2-3B, if cqi-
FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported

PMI subband information fields

X 2 of all even subbands with increasing order of subband
number, from left to right as in Tables [Link].2-1, or codebook index for 2 antenna ports
associated with the second CRI in CSI part 1 according to Clause [Link].1 in [6, TS38.214] of all
even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI,
numberOfSingleTRP-CSI-Mode1 = 2 and if reported

PMI subband information fields

X 2 of all odd subbands with increasing order of subband
number, from left to right as in Tables [Link].2-1, or codebook index for 2 antenna ports
associated with the first resource within the CSI-RS resource pair, according to Clause [Link].1
in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-
FormatIndicator= subbandPMI and if reported

PMI subband information fields

X 2 of all odd subbands with increasing order of subband
number, from left to right as in Tables [Link].2-1, or codebook index for 2 antenna ports
associated with the second resource within the CSI-RS resource pair, according to Clause
[Link].1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-
FormatIndicator= subbandPMI and if reported
Subband differential CQI for the second TB of all odd subbands with increasing order of subband
number associated with CRI in CSI part 1, as in Tables [Link].2-3B, if cqi-
FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 1 and if reported;
Subband differential CQI for the second TB of all odd subbands with increasing order of subband
number associated with the first CRI in CSI part 1, as in Tables [Link].2-3B, if cqi-
FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported

PMI subband information fields

X 2 of all odd subbands with increasing order of subband
number, from left to right as in Tables [Link].2-1, or codebook index for 2 antenna ports
associated with CRI in CSI part 1 according to Clause [Link].1 in [6, TS38.214] of all odd
subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI,
numberOfSingleTRP-CSI-Mode1 = 1 and if reported;

PMI subband information fields

X 2 of all odd subbands with increasing order of subband
number, from left to right as in Tables [Link].2-1, or codebook index for 2 antenna ports
associated with the first CRI in CSI part 1 according to Clause [Link].1 in [6, TS38.214] of all
odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI,

3GPP
Release 17 66 3GPP TS 38.212 V17.5.0 (2023-03)

numberOfSingleTRP-CSI-Mode1 = 2 and if reported

Subband differential CQI for the second TB of all odd subbands with increasing order of subband
number associated with the second CRI in CSI part 1, as in Tables [Link].2-3B, if cqi-
FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported

PMI subband information fields

X 2 of all odd subbands with increasing order of subband
number, from left to right as in Tables [Link].2-1, or codebook index for 2 antenna ports
associated with the second CRI in CSI part 1 according to Clause [Link].1 in [6, TS38.214] of all
odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI,
numberOfSingleTRP-CSI-Mode1 = 2 and if reported

Table [Link].2-11B: Mapping order of CSI fields of one CSI report, CSI part 2 subband, csi-
ReportMode= Mode 2

PMI subband information fields

X 2 of all even subbands with increasing order of subband
number, from left to right as in Tables [Link].2-1, or codebook index for 2 antenna ports
associated with the first resource within the CSI-RS resource pair, according to Clause [Link].1
in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-
FormatIndicator= subbandPMI and reported part 1 is associated with one CSI-RS resource pair
and if reported

PMI subband information fields

X 2 of all odd subbands with increasing order of subband
CSI report #n number, from left to right as in Tables [Link].2-1, or codebook index for 2 antenna ports
Part 2 subband associated with the second resource within the CSI-RS resource pair, according to Clause
[Link].1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-
FormatIndicator= subbandPMI and reported part 1 is associated with one CSI-RS resource pair
and if reported
Subband differential CQI for the second TB of all even subbands with increasing order of
subband number associated with one CSI-RS resource, as in Tables [Link].2-3B, if cqi-
FormatIndicator=subbandCQI and reported part 1 is associated with one CSI-RS resource and if
reported

PMI subband information fields

X 2 of all even subbands with increasing order of subband
number, from left to right as in Tables [Link].2-1, or codebook index for 2 antenna ports
associated with one CSI-RS resource according to Clause [Link].1 in [6, TS38.214] of all even
subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and
reported part 1 is associated with one CSI-RS resource and if reported
Subband differential CQI for the second TB of all odd subbands with increasing order of subband
number associated with one CSI-RS resource, as in Tables [Link].2-3B, if cqi-
FormatIndicator=subbandCQI and reported part 1 is associated with one CSI-RS resource and if
reported

PMI subband information fields

X 2 of all odd subbands with increasing order of subband
number, from left to right as in Tables [Link].2-1/2, or codebook index for 2 antenna ports
associated with one CSI-RS resource according to Clause [Link].1 in [6, TS38.214] of all odd
subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and
reported part 1 is associated with one CSI-RS resource and if reported

If none of the CSI reports for transmission on a PUCCH is of two parts, the CSI fields of all CSI reports, in the order
from upper part to lower part in Table [Link].2-12, are mapped to the UCI bit sequence
a 0 , a1 , a 2 , a3 , . .. , a A −1 starting

3GPP
Release 17 67 3GPP TS 38.212 V17.5.0 (2023-03)

a
with 0 . The most significant bit of each field is mapped to the lowest order information bit for that field, e.g. the most
a
significant bit of the first field is mapped to 0 .

Table [Link].2-12: Mapping order of CSI reports to UCI bit sequence

a 0 , a1 , a 2 , a3 , . .. , a A −1 , without two-
part CSI report(s)

UCI bit sequence CSI report number

CSI report #1
a0 as in Table [Link].2-
7/7A/8/8B
a1 CSI report #2
as in Table [Link].2-
a2 7/7A/8/8B
a3 …
⋮ CSI report #n
a A−1 as in Table [Link].2-
7/7A/8/8B

If at least one of the CSI reports for transmission on a PUCCH is of two parts, two UCI bit sequences are generated,
a(01) , a(11) , a(1
) (1 )
a( 2) , a( 2) , a( 2) , a( 2) , .. . , a( 2)(2 )
(1 )
2 , a3 ,. .. , a A( 1 )−1
and 0 1 2 3 A −1 . The CSI fields of all CSI reports, in the order from upper

a( 1) , a( 1) , a(1 ) , a(1 ) ,. .. , a(1A()1 )−1

part to lower part in Table [Link].2-13, are mapped to the UCI bit sequence 0 1 2 3 starting with
( 1)
a 0 . The most significant bit of each field is mapped to the lowest order information bit for that field, e.g. the most
( 1)
significant bit of the first field is mapped toa 0 . The CSI fields of all CSI reports, in the order from upper part to lower
a( 2) , a( 2) , a( 2) , a( 2) , .. . , a( 2)(2 ) ( 2)
part in Table [Link].2-14, are mapped to the UCI bit sequence 0 1 2 3 A −1 starting with a 0 . The most
significant bit of each field is mapped to the lowest order information bit for that field, e.g. the most significant bit of
( 2) ( 2) ( 2) ( 2) ( 2)
( 2) a , a , a , a , .. . , a A(2 )−1
the first field is mapped to a 0 . If the length of UCI bit sequence 0 1 2 3 is less than 3 bits, zeros
shall be appended to the UCI bit sequence until its length equals 3.

a(01) , a(11) , a(1

) (1 ) (1 )
2 , a3 ,. .. , a ( 1 )
Table [Link].2-13: Mapping order of CSI reports to UCI bit sequence A −1 ,
with two-part CSI report(s)

UCI bit sequence CSI report number

CSI report #1 if CSI report #1 is not of two parts, or

a(01) CSI report #1, CSI part 1, if CSI report #1 is of two parts,
as in Table [Link].2-7/7A/8/8B/9/9A/9B
( 1)
a1 CSI report #2 if CSI report #2 is not of two parts, or
CSI report #2, CSI part 1, if CSI report #2 is of two parts,
a(21) as in Table [Link].2-7/7A/8/8B/9/9A/9B
( 1)
a3 …
⋮
(1 ) CSI report #n if CSI report #n is not of two parts, or
a A(1 )−1 CSI report #n, CSI part 1, if CSI report #n is of two parts,
as in Table [Link].2-7/7A/8/8B/9/9A/9B

where CSI report #1, CSI report #2, …, CSI report #n in Table [Link].2-13 correspond to the CSI reports in increasing
order of CSI report priority values according to Clause 5.2.5 of [6, TS38.214].

3GPP
Release 17 68 3GPP TS 38.212 V17.5.0 (2023-03)

( 2) ( 2) ( 2) ( 2) ( 2)
a 0 , a1 , a2 , a3 , .. . , a (2 )
Table [Link].2-14: Mapping order of CSI reports to UCI bit sequence A −1 ,
with two-part CSI report(s)

UCI bit sequence CSI report number

CSI report #1, CSI part 2 wideband, as in Table [Link].2-

10/10A/10B
if CSI part 2 exists for CSI report #1
CSI report #2, CSI part 2 wideband, as in Table [Link].2-
10/10A/10B
if CSI part 2 exists for CSI report #2

a(02) …
( 2) CSI report #n, CSI part 2 wideband, as in Table [Link].2-
a1
10/10A/10B
a(22) if CSI part 2 exists for CSI report #n
( 2) CSI report #1, CSI part 2 subband, as in Table [Link].2-
a3 11/11A/11B
⋮ if CSI part 2 exists for CSI report #1
(2 ) CSI report #2, CSI part 2 subband, as in Table [Link].2-
a A(2 )−1
11/11A/11B
if CSI part 2 exists for CSI report #2

CSI report #n, CSI part 2 subband, as in Table [Link].2-

11/11A/11B
if CSI part 2 exists for CSI report #n

where CSI report #1, CSI report #2, …, CSI report #n in Table [Link].2-14 correspond to the CSI reports in increasing
order of CSI report priority values according to Clause 5.2.5 of [6, TS38.214].

[Link].3 HARQ-ACK/SR and CSI

If none of the CSI reports for transmission on a PUCCH is of two parts, the UCI bit sequence
a 0 , a1 , a 2 , a3 , . .. , a A −1 is
ACK
generated according to the following, where A=O +OSR + OCSI :

- if there is HARQ-ACK for transmission on the PUCCH, the HARQ-ACK bits are mapped to the UCI bit
a , a , a , a , . .. , a ACK ~ACK ACK
sequence 0 1 2 3 O −1 , where a i= o i for i=0,1,...,O −1 , the HARQ-ACK bit sequence
~o ACK , { ~o ACK ,..., ~o ACK ¿ ACK
0 1 O ACK −1 is given by Clause 9.1 of [5, TS38.213], and O is number of HARQ-ACK bits; if there
ACK
is no HARQ-ACK for transmission on the PUCCH, set O =0 ;

- if there is SR for transmission on the PUCCH, set a i=oi −O ACK for i=O
~SR ACK
, OACK +1 , .. . ,O ACK +OSR −1 , where
~o SR , { ~o SR ,...,~o SRSR ¿
the SR bit sequence 0 1 O −1 is given by Clause [Link] of [5, TS 38.213]; if there is no SR for
SR
transmission on the PUCCH, set O =0 ;

- the CSI fields of all CSI reports, in the order from upper part to lower part in Table [Link].2-12, are mapped to
a , a OACK +OSR +1 , . .. , aO ACK+O SR+O CSI−1 a CSI
the UCI bit sequence OACK +OSR starting with OACK +OSR , where O is the
number of CSI bits.

If at least one of the CSI reports for transmission on a PUCCH is of two parts, two UCI bit sequences are generated,
a(01) , a(11) , a(1
) (1 )
a( 2) , a( 2) , a( 2) , a( 2) , .. . , a( 2)(2 )
(1 )
2 , a3 ,. .. , a A( 1 )−1
and 0 1 2 3 A −1 , according to the following, where
( 1) ACK SR CSI-part1 ( 2) CSI-part2
A =O +O +O and A =O :

- if there is HARQ-ACK for transmission on the PUCCH, the HARQ-ACK bits are mapped to the UCI bit
( 1) ~ACK
a( 1) , a( 1) , a(1 ) , a(1 ) ,. .. , a(1OACK
)
−1 , where a i = o i
ACK
−1 , the HARQ-ACK bit sequence
sequence 0 1 2 3 for i=0,1,...,O

3GPP
Release 17 69 3GPP TS 38.212 V17.5.0 (2023-03)

~o ACK , { ~o ACK ,..., ~o ACK ¿ ACK

0 1 O ACK −1 is given by Clause 9.1 of [5, TS38.213], and O is number of HARQ-ACK bits; if there
ACK
is no HARQ-ACK for transmission on the PUCCH, set O =0 ;

- the CSI fields of all CSI reports, in the order from upper part to lower part in Table [Link].2-13, are mapped to
(1 ) (1 ) (1 ) (1 )
a ,a , . .. , aO ACK+O SR+O CSI-part1−1 a CSI-part1
the UCI bit sequence OACK +OSR OACK +OSR +1 starting with OACK +OSR , where O is the
number of CSI bits in CSI part 1 of all CSI reports;

- the CSI fields of all CSI reports, in the order from upper part to lower part in Table [Link].2-14, are mapped to
a( 2) , a( 2) , a( 2) , a( 2) , .. . , a( 2)(2 ) ( 2) CSI-part2
the UCI bit sequence 0 1 2 3 A −1 starting with a 0 , where O is the number of CSI bits in
a( 2) , a( 2) , a( 2) , a(32) , .. . , a( 2)(2 )
CSI part 2 of all CSI reports. If the length of UCI bit sequence 0 1 2 A −1 is less than 3 bits,
zeros shall be appended to the UCI bit sequence until its length equals 3.

[Link].4 UCI with different priority indexes

If uci-MuxWithDiffPrio is configured, and HARQ-ACK bits associated with priority index 0, HARQ-ACK bits
associated with priority index 1, and SR associated with priority index 1 if any are transmitted on a PUCCH, two UCI
(1) (1) (1) (1) (1 ) (2) (2) (2) (2) ( 2)
bit sequences are generated, a 0 , a1 , a2 , a3 , … , a A(1)−1 and a 0 , a1 , a2 , a3 , … , a A( 2)−1 , according to the
following, where A(1)=O ACK −HP +O SR −HP and A(2)=O ACK −LP :

- the HARQ-ACK bits associated with priority index 1 are mapped to the UCI bit sequence
, where a i =~
(1) (1) (1) (1) (1 ) (1) ACK −HP
a 0 , a 1 , a 2 , a 3 , … , aO −1
ACK −HP oi for i=0 , 1 , … ,O ACK −HP −1, the HARQ-ACK bit
sequence ~
ACK −HP ~ ACK −HP
, … , ~o
ACK −HP
o 0 ,o 1 is given by Clause 9.1 of [5, TS 38.213], and O ACK −HP is the
O
ACK −HP
−1
number of HARQ-ACK bits associated with priority index 1;

if there is SR associated with priority index 1 for transmission on the PUCCH, set a i =~
(1) SR− HP
- oi−O ACK−HP for
ACK −HP ACK− HP ACK −HP SR−HP
i=O ,O +1 ,… ,O +O −1, where the SR bit sequence
~
o0
SR− HP ~SR− HP
, o1 ~ SR− HP
,… , o O −1 is given by Clause [Link] of [5, TS 38.213]; if there is no SR associated with
SR −HP

priority index 1 for transmission on the PUCCH, set O SR −HP=0 ;

- the HARQ-ACK bits associated with priority index 0 are mapped to the UCI bit sequence
(2) (2) (2) (2) ( 2)
a 0 , a1 , a2 , a3 , … , aO ACK −L P −1, where a(2) ~ ACK −L P for i=0 , 1 , … ,O ACK −LP −1, the HARQ-ACK bit
i = oi
sequence ~ ,~ , … , ~oO ACK −L P−1 is given by Clause 9.1 of [5, TS 38.213], and O ACK −L P is the
ACK −L P ACK −L P ACK −L P
o0 o1
number of HARQ-ACK bits associated with priority index 0.

[Link] Code block segmentation and CRC attachment

The UCI bit sequence from clause [Link] is denoted by 0 1 2 3

a , a , a , a , . .. , a
A −1 , where A is the payload size. The

procedure in [Link].1 applies for A≥12 and the procedure in Clause [Link].2 applies for A≤11 .

[Link].1 UCI encoded by Polar code

If the payload size A≥12 , code block segmentation and CRC attachment is performed according to Clause 5.2.1. If (
A≥360 and E≥1088 ) or if , seg
I =1
; otherwise
I seg =0 , where E is the rate matching output sequence
length as given in Clauses [Link].1 and [Link].3.

3GPP
Release 17 70 3GPP TS 38.212 V17.5.0 (2023-03)

pr 0 , pr 1 , pr 2 , .. . , p r ( L−1 )
If 12≤ A≤19 , the parity bits in Clause 5.2.1 are computed by setting L to 6 bits and using the
c , c , c , c , .. . , cr K −1
generator polynomial gCRC6 ( D ) in Clause 5.1, resulting in the sequence r 0 r 1 r 2 r 3 ( r ) where r is the

code block number and K r is the number of bits for code block number r .

p , p , p , .. . , p r ( L−1 )
If A≥20 , the parity bits r 0 r 1 r 2 in Clause 5.2.1 are computed by setting L to 11 bits and using the
c , c , c , c , .. . , cr K −1
generator polynomial gCRC11 ( D ) in Clause 5.1, resulting in the sequence r 0 r 1 r 2 r 3 ( r ) where r is the

code block number and K r is the number of bits for code block number r .

[Link].2 UCI encoded by channel coding of small block lengths

If the payload size A≤11 , CRC bits are not attached.

The output bit sequence is denoted by

c 0 , c 1 , c 2 , c 3 , .. . , c K −1 , where c i =ai for i=0,1,..., A−1 and K= A .

[Link] Channel coding of UCI

[Link].1 UCI encoded by Polar code
c r 0 , c r 1 , c r 2 , c r 3 , .. . , cr
Information bits are delivered to the channel coding block. They are denoted by ( K r −1 ) , where r

is the code block number, and K r is the number of bits in code block number r . The total number of code blocks is
denoted by C and each code block is individually encoded by the following:

If
18≤K r ≤25 , the information bits are encoded via Polar coding according to Clause 5.3.1, by setting n max =10 ,
I IL =0 , n PC =3 , n wm wm
PC =1 if Er −K r + 3>192 and n PC =0 if Er −K r + 3≤192 , where E r is the rate matching
output sequence length as given in Clauses [Link].1 and [Link].3.

If
K r >30 , the information bits are encoded via Polar coding according to Clause 5.3.1, by setting n max =10 , I IL=0 ,
n PC =0 , and n wm
PC =0 .

d r 0 ,d r 1 , d r 2 , d r 3 ,. .. , d r( N −1 )
After encoding the bits are denoted by r , where N r is the number of coded bits in code block
number r .

[Link].2 UCI encoded by channel coding of small block lengths

Information bits are delivered to the channel coding block. They are denoted by
c 0 , c 1 , c 2 , c 3 , .. . , c K −1 , where K is the
number of bits.

The information bits are encoded according to Clause 5.3.3.

After encoding the bits are denoted by

d 0 ,d1 ,d 2 ,d3 ,...,d N−1 , where N is the number of coded bits.

[Link] Rate matching

For PUCCH formats 2/3/4, the total rate matching output sequence length
E tot is given by Table [Link]-1, where
N PUCCH, 2
symb, UCI , N PUCCH, 3
symb, UCI , and N PUCCH, 4
symb, UCI are the number of symbols carrying UCI for PUCCH formats 2/3/4 respectively;
N PUCCH,
PRB
2 PUCCH, 3
, N PRB
PUCCH , 4
and N PRB are the number of PRBs that are determined by the UE for PUCCH formats 2/3/4
PUCCH, 4
, and N SF
PUCCH ,2 PUCCH ,3
transmission respectively according to Clause 9.2 of [5, TS38.213]; and N SF , N SF are the
spreading factors for PUCCH format 2, PUCCH format 3, and PUCCH format 4, respectively.

3GPP
Release 17 71 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link]-1: Total rate matching output sequence length

E tot

Modulation order
PUCCH format
QPSK π/2-BPSK
PUCCH ,2 PUCCH ,2 PUCCH , 2
PUCCH format 2 16 ∙ N symb ,UCI ∙N PRB /N SF N/A
PUCCH ,3 PUCCH , 3 PUCCH ,3 PUCCH , 3 PUCCH ,3 PUCCH ,3
PUCCH format 3 24 ∙ N symb , UCI ∙N PRB /N SF 12 ∙ N symb ,UCI ∙ N PRB / N SF
PUCCH , 4 PUCCH , 4 PUCCH ,4 PUCCH , 4 PUCCH , 4 PUCCH , 4
PUCCH format 4 24 ∙ N symb , UCI ∙N PRB /N SF 12 ∙ N symb ,UCI ∙ N PRB / N SF

[Link].1 UCI encoded by Polar code

d ,d , d , d ,. .. , d r( N −1 )
The input bit sequence to rate matching is r 0 r 1 r 2 r 3 r where r is the code block number, and N r is the
number of coded bits in code block number r .

Table [Link].1-1: Rate matching output sequence length

E UCI

UCI(s) for
transmission on a UCI for encoding Value of
E UCI
PUCCH
HARQ-ACK HARQ-ACK E UCI =Etot
HARQ-ACK, SR HARQ-ACK, SR E UCI =Etot
CSI E UCI =Etot
CSI
(CSI not of two parts)
HARQ-ACK, CSI E UCI =Etot
HARQ-ACK, CSI
(CSI not of two parts)
HARQ-ACK, SR, CSI HARQ-ACK, SR, E UCI =Etot
(CSI not of two parts) CSI

CSI CSI part 1 E UCI =min ( Etot ,⌈ ( O CSI-part1 + L ) / R max

UCI /Q m ⌉⋅Q m )
(CSI of two parts) CSI part 2 E UCI =Etot −min ( E tot ,⌈ ( O CSI-part1 + L ) / R max
UCI /Q m ⌉⋅Q m )
HARQ-ACK, CSI
HARQ-ACK, CSI E UCI =min ( Etot ,⌈ ( O ACK +O CSI-part1+ L ) / R max
UCI / Q m ⌉⋅Q m )
part 1
(CSI of two parts)
CSI part 2 E UCI =Etot −min ( E tot ,⌈ ( O ACK +O CSI-part1 + L ) / R max
UCI / Q m ⌉⋅Q m )
HARQ-ACK, SR,
HARQ-ACK, SR, CSI E UCI =min ( Etot ,⌈ ( O ACK +O SR +O CSI-part1 + L ) / R max
UCI /Q m⌉⋅Q m )
CSI part 1
(CSI of two parts)
CSI part 2 E UCI =Etot −min ( E tot ,⌈ ( O ACK +O SR +O CSI-part1 + L ) / R max
UCI / Q m ⌉⋅Q m )

Rate matching is performed according to Clause 5.4.1 by setting I BIL=1 and the rate matching output sequence length
to r ⌊ UCI UCI ⌋ , where UCI is the number of code blocks for UCI determined according to Clause [Link].1 and
E = E /C C
the value of
E UCI is given by Table [Link].1-1:

- O ACK is the number of bits for HARQ-ACK for transmission on the current PUCCH;

- O SR is the number of bits for SR for transmission on the current PUCCH;

- OCSI-part1 is the number of bits for CSI part 1 for transmission on the current PUCCH;

- OCSI-part2 is the number of bits for CSI part 2 for transmission on the current PUCCH;

- if , ; otherwise, L is the number of CRC bits determined according to clause [Link].1, where
CSI-part1
equals O for "CSI (CSI of two parts)", equals for "HARQ-ACK, CSI (CSI of two parts)",
and equals for "HARQ-ACK, SR, CSI (CSI of two parts)" respectively in Table [Link].1-
1;;

3GPP
Release 17 72 3GPP TS 38.212 V17.5.0 (2023-03)

- R max
UCI is the configured maximum PUCCH coding rate;

-
E tot is given by Table [Link]-1.

f r 0 , f r1 , f r 2 , .. . , f r ( E −1)
The output bit sequence after rate matching is denoted as r where Er is the length of rate matching
output sequence in code block number r .

[Link].2 UCI encoded by channel coding of small block lengths

The input bit sequence to rate matching is d 0 ,d1 ,d 2 ,...,d N−1 .

The value of
E UCI is determined according to Table [Link].1-1 by setting L=0 .

Rate matching is performed according to Clause 5.4.3 by setting the rate matching output sequence length
E=EUCI .

The output bit sequence after rate matching is denoted as f 0 , f 1 , f 2 , .. . , f E−1 .

[Link].3 UCI with different priority indexes encoded by Polar code

The following procedure in this clause [Link].3 applies if uci-MuxWithDiffPrio is configured, and HARQ-ACK bits
associated with priority index 0, HARQ-ACK bits associated with priority index 1 and SR associated with priority
index 1 if any are transmitted on a PUCCH.

The input bit sequence to rate matching is d r 0 , d r 1 , d r 2 , d r 3 ,… , d r (N r−1) where r is the code block number, and N r
is the number of coded bits in code block numberr .

Table [Link].3-1: Rate matching output sequence length EUCI for UCIs with different priority indexes

UCIs for transmission

on a PUCCH
UCI for encoding Value of EUCI
EUCI =min ( E tot , ⌈ ( O /Qm ⌉ ∙Qm )
HARQ-ACK of priority
+ L ) / RUCI
ACK −HP max −HP
HARQ-ACK of priority
index 1
index 1, HARQ-ACK of
EUCI =Etot −min ( Etot , ⌈ ( O /Qm ⌉ ∙ Qm )
HARQ-ACK of priority
+ L ) /R UCI
ACK −HP max− HP
priority index 0
index 0
HARQ-ACK of priority
EUCI =min ( E tot , ⌈ ( O /Qm ⌉ ∙Qm )
HARQ-ACK of priority
+ L ) / RUCI
ACK −HP SR− HP max −HP
index 1, SR of priority
index 1, SR of priority +O
index 1
index 1, HARQ-ACK of
EUCI =Etot −min ( Etot , ⌈ ( O /Qm ⌉ ∙ Qm )
HARQ-ACK of priority
+ L ) /R UCI
ACK −HP SR−HP max− HP
priority index 0
index 0 +O

Rate matching is performed according to Clause 5.4.1 by setting I BIL =1 and the rate matching output sequence length
to Er =⌊ EUCI /C UCI ⌋ , where C UCI is the number of code blocks for UCI determined according to Clause [Link].1
and the value of EUCI is given by Table [Link].3-1:
ACK −HP
- O is the number of bits for HARQ-ACK associated with priority index 1 for transmission on the current
PUCCH;
SR −HP
- O is the number of bits for SR associated with priority index 1 for transmission on the current PUCCH;

- if A ≥ 360, L=11; otherwise, L is the number of CRC bits determined according to clause [Link].1, where A
equals O ACK −HP for the case of "HARQ-ACK of priority index 1, HARQ-ACK of priority index 0", and equals
ACK −HP SR −HP
O +O for the case of "HARQ-ACK of priority index 1, SR of priority index 1, HARQ-ACK of
priority index 0" respectively in Table [Link].3-1;
max −HP
- RUCI is the configured maximum PUCCH coding rate of priority index 1;

3GPP
Release 17 73 3GPP TS 38.212 V17.5.0 (2023-03)

- Etot is given by Table [Link]-1.

The output bit sequence after rate matching is denoted as f r 0 , f r 1 , f r 2 , … , f r( Er −1 ) where Er is the length of rate
matching output sequence in code block numberr .

[Link].4 UCI with different priority indexes encoded by channel coding of small block
lengths
The following procedure in this clause [Link].4 applies if uci-MuxWithDiffPrio is configured, and HARQ-ACK bits
associated with priority index 0, HARQ-ACK bits associated with priority index 1 and SR associated with priority
index 1 if any are transmitted on a PUCCH.

The input bit sequence to rate matching is d 0 , d 1 , d 2 , … , d N −1.

The value of EUCI is determined according to Table [Link].3-1 by setting L=0.

Rate matching is performed according to Clause 5.4.3 by setting the rate matching output sequence length E=EUCI .

The output bit sequence after rate matching is denoted as f 0 , f 1 , f 2 ,… , f E −1.

[Link] Code block concatenation

f r 0 , f r1 , f r 2 , .. . , f r ( E −1)
The input bit sequence for the code block concatenation block are the sequences r , for r=0 ,. . ., C−1
and where
Er is the number of rate matched bits for the r -th code block.

Code block concatenation is performed according to Clause 5.5.

g ,g ,g ,g ,..., gG '−1 , where G '= ⌊ EUCI /C UCI ⌋⋅C UCI with the
The bits after code block concatenation are denoted by 0 1 2 3
E C
values of UCI and UCI given in Clauses [Link].1 and [Link].3. Let G be the total number of coded bits for
transmission and
G=G '+ mod ( E UCI , CUCI ) g =0 for i=G ',G '+1,...,G−1 .
. Set i

[Link] Multiplexing of coded UCI bits to PUCCH

If CSI of two parts or UCIs with different priority indexes are transmitted on a PUCCH, the coded bits corresponding to
a( 1) , a( 1) , a(1 ) , a(1 ) ,. .. , a(1()1 ) g(1 ) , g(11) , g(1) ( 1) (1 )
2 , g3 , .. . , gG( 1)−1
UCI bit sequence 0 1 2 3 A −1 is denoted by 0 and the coded bits corresponding
( 2) ( 2) ( 2) ( 2) ( 2) (2 ) ( 2) (2 ) ( 2) (2 )
a , a , a , a , .. . , a (2 ) g , g 1 , g2 , g 3 , .. . , g ( 2 )
to UCI bit sequence 0 1 2 3 A −1 is denoted by 0 G −1 .

For PUCCH format 2 when uci-MuxWithDiffPrio is configured, the coded bit sequence g0 , g 1 , g2 , g 3 , … , gG−1 is
(1) (2)
generated for UCIs with different priority indexes by setting gi=g i for i=0 , 1 , … ,G ( 1) −1, and setting gi=g i−G (1)
for i=G ( 1) ,G ( 1) + 1, … , G ( 1 ) + G ( 2) −1 .

g ,g ,g ,g ,..., gG−1 , where G=G( 1)+G( 2) , is generated according to

For PUCCH format 3/4, the coded bit sequence 0 1 2 3
the following.

3GPP
Release 17 74 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link]-1: PUCCH DMRS and UCI symbols

PUCCH Number of UCI

PUCCH DMRS 1st UCI symbol 2nd UCI symbol 3rd UCI symbol
duration symbol indices
(symbols)
symbol indices
N set S(1 )
indices set UCI
S(2 )
indices set UCI
S (3 )
indices set UCI
sets UCI
4 {1} 2 {0,2} {3} -
4 {0,2} 1 {1,3} - -
5 {0, 3} 1 {1, 2, 4} - -
6 {1, 4} 1 {0, 2, 3, 5} - -
7 {1, 4} 2 {0, 2, 3, 5} {6} -
8 {1, 5} 2 {0, 2, 4, 6} {3, 7} -
9 {1, 6} 2 {0, 2, 5, 7} {3, 4, 8} -
10 {2, 7} 2 {1, 3, 6, 8} {0, 4, 5, 9} -
10 {1, 3, 6, 8} 1 {0,2,4,5,7,9} - -
11 {2, 7} 3 {1,3,6,8} {0,4,5,9} {10}
11 {1,3,6,9} 1 {0,2,4,5,7,8,10} - -
12 {2, 8} 3 {1,3,7,9} {0,4,6,10} {5, 11}
12 {1,4,7,10} 1 {0,2,3,5,6,8,9,11} - -
13 {2, 9} 3 {1,3,8,10} {0,4,7,11} {5,6,12}
13 {1,4,7,11} 2 {0,2,3,5,6,8,10,12} {9} -
14 {3, 10} 3 {2,4,9,11} {1,5,8,12} {0,6,7,13}
14 {1,5,8,12} 2 {0,2,4,6,7,9,11,13} {3, 10} -

(i ) (i )
s
Denote l as UCI OFDM symbol index. Denote N UCI as the number of elements in UCI symbol indices set SUCI for
(i )
i=1 , .. ., N set set
UCI , where SUCI and N UCI are given by Table [Link]-1 according to the PUCCH duration and the PUCCH
N set
UCI

N PUCCH,
symb, UCI = ∑ N(UCI
i)

DMRS configuration. Denote i=1 as the number of OFDM symbols carrying UCI in the PUCCH.
Q
Denote m as the modulation order of the PUCCH.
symbol PUCCH,s PUCCH, s PUCCH, s
For PUCCH formats 3/4, set N UCI =12 ⋅ N PRB / N SF , where N PRB is the number of PRBs that is
determined by the UE for the corresponding PUCCH format transmission according to Clause 9.2 of [5, TS 38.213],
is the spreading factor for the corresponding PUCCH format [4, TS 38.211], where s ∈ {3 , 4 }.
PUCCH, s
and N SF

(∑ )
j
N (UCI
i)
⋅N symbol
UCI ⋅Q m ≥G
( 1)

Find the smallest j > 0 such that i =1 .

Set
n1 =0 ;

Set
n2 =0 ;

⌊( ( ) ) ⌋
j−1
N̄ symbol
UCI = G
( 1)
− ∑ N (UCI
i)
UCI ⋅Q m / ( N UCI⋅Q m )
⋅N symbol
( j)

i=1
Set ;

(( ( ∑ ) ) )
j −1
( 1) (i ) ( j)
M = mod G − N UCI ⋅N symbol
UCI ⋅Q m /Q m , N UCI
i =1
Set ;

for l=0 to
N PUCCH,
symb, UCI −1

j−1
( i)
sl ∈ ¿ S UCI
if i=1

symbol
for k =0 to N UCI −1

3GPP
Release 17 75 3GPP TS 38.212 V17.5.0 (2023-03)

for v=0 to Q m−1

(1 )
ḡl , k , v =gn 1
;

n1 =n1 +1 ;

end for

end for
( j)
elseif sl ∈ S UCI

if M >0

γ =1 ;
else

γ =0 ;
end if

M =M −1 ;
symbol
for k =0 to N̄ UCI +γ −1

for v=0 to Q m−1

(1 )
ḡl , k , v =gn 1
;

n1 =n1 +1 ;

end for

end for
symbol
for k = N̄ UCI +γ to N symbol
UCI −1

for v=0 to Q m−1

ḡl , k , v =g(2
n2
)
;

n2 =n 2 +1 ;

end for

else
symbol
for k =0 to N UCI −1

for v=0 to Q m−1

ḡl , k , v =g(2
n2
)
;

3GPP
Release 17 76 3GPP TS 38.212 V17.5.0 (2023-03)

n2 =n 2 +1 ;

end for

end if

end for

Set n=0

for l=0 to
N PUCCH,
symb, UCI −1

symbol
for k =0 to N UCI −1

for v=0 to Q m−1

gn = ḡl , k , v ;

n=n+1 ;

end for

6.3.2 Uplink control information on PUSCH

The following clauses [Link], [Link], and [Link] apply regardless of whether the higher layer parameter uci-
MuxWithDiffPrio is configured or not. The following clauses [Link], [Link], and [Link] apply by assuming uci-
MuxWithDiffPrio is not configured, or uci-MuxWithDiffPrio is configured and the UCIs for transmission on a PUSCH
are of the same priority index, unless stated otherwise.

If the UE is configured with a PUCCH-SCell, uci-MuxWithDiffPrio is replaced by uci-

MuxWithDiffPrioSecondaryPUCCHgroup for the secondary PUCCH group in this clause.

[Link] UCI bit sequence generation

[Link].1 HARQ-ACK

If HARQ-ACK bits are transmitted on a PUSCH, the UCI bit sequence

a 0 , a1 , a 2 , a3 , . .. , a A −1 is determined as follows:

- If UCI is transmitted on PUSCH without UL-SCH and the UCI includes CSI part 1 without CSI part 2,

- if there is no HARQ-ACK bit given by Clause 9.1 of [5, TS 38.213], set

a 0=0 , a 1=0 , and A=2 ;
~
o 0ACK a = o0 ~ACK a =0
- if there is only one HARQ-ACK bit given by Clause 9.1 of [5, TS 38.213], set 0 , 1 ,
and A=2 ;

a = oi ~ACK ACK
- otherwise, set i for i=0,1,...,O −1 and A=OACK , where the HARQ-ACK bit sequence
~o ACK , { ~o ACK ,..., ~o ACK ¿
0 1 O ACK −1 is given by Clause 9.1 of [5, TS 38.213].

[Link].2 CSI
If cqi-BitsPerSubband is configured, this Clause [Link].2 applies by taking Subband CQI as Subband differential CQI
and replacing the corresponding number of bits 2 by 4.

3GPP
Release 17 77 3GPP TS 38.212 V17.5.0 (2023-03)

The bitwidth for PMI of codebookType=typeI-SinglePanel and codebookType=typeI-MultiPanel is specified in Clause

[Link].2.

The bitwidth for RI/LI/CQI/CRI of codebookType=typeI-SinglePanel and codebookType=typeI-MultiPanel is specified

in Clause [Link].2.

The bitwidth for PMI of codebookType=typeII is provided in Tables [Link].2-1, where the values of (
N1 , N2)
,
( O1 ,O2 ) , L , N PSK , M 1 , M 2 , and K ( 2 ) are given by Clause [Link].3 in [6, TS 38.214].
Table [Link].2-1: PMI of codebookType= typeII

X1 Information fields
X 2 for wideband PMI or per subband
Information fields for wideband PMI
PMI

i1, 1 i 1, 2 i1,3 ,1 i1,4 ,1 i1,3 ,2 i1,4 ,2 i2,1 ,1 i2,1 ,2 i2,2 ,1 i2,2 ,2

Rank=1

SBAmp
⌈log 2 ( O1 O2 ) ⌉ ⌈log 2
( N LN )⌉ ⌈log ( 2 L ) ⌉ 3 ( 2L−1)
1 2
2 N/A N/A ( M 1 −1 )⋅log2 N PSK N/A N/A N/A
off

Rank=2

SBAmp
⌈log 2 ( O1 O2 ) ⌉ ⌈log 2
( N LN )⌉ ⌈log ( 2 L ) ⌉ 3 ( 2L−1) ⌈log ( 2 L ) ⌉ 3 ( 2L−1)
1 2
2 2 ( M 1−1 )⋅log2 N PSK ( M 2−1 )⋅log2 N PSK N/A N/A
off

Rank=1 min ( M 1 , K( 2) )⋅log 2 N PSK

SBAmp
⌈log 2 ( O1 O2 ) ⌉ ⌈log 2
( )
N1 N2
L
⌉ ⌈log 2 ( 2 L ) ⌉ 3 ( 2L−1 ) N/A N/A −log 2 N PSK
(
+2⋅ M 1 −min ( M 1 , K ( 2)
))
N/A min ( M 1 , K (2 ))−1 N/A
on

Rank=2 min ( M , K( 2) )⋅log N min ( M , K (2 ))⋅log N

( )
1 2 PSK 2 2 PSK
N N
⌈log 2 ( O1 O2 ) ⌉ ⌈log 2 1 2 ⌉ ⌈log 2 ( 2 L ) ⌉ 3 ( 2L−1 ) ⌈log 2 ( 2 L ) ⌉ 3 ( 2L−1 ) −log 2 N PSK −log 2 N PSK min ( M 1 , K )−1
(2 )
min ( M 2 , K
(2 )
)−1
SBAmp L +2⋅( M 1 −min ( M 1 , K ) ) +2⋅( M 2 −min ( M 2 , K ))
( 2) ( 2)

The bitwidth for PMI of codebookType=typeII-r16 is provided in Tables [Link].2-1A, where the values of (N 1 , N 2),
(O1 ,O2 ), L, K NZ , N 3, and { M l }l=1 , …, υ are given by Clause [Link].5 in [6, TS 38.214].
Table [Link].2-1A: PMI of codebookType= typeII-r16

Information fields X1

i 1 ,1 i 1 ,2 i 1 ,8 ,1 i 1 ,8 , 2 i 1 ,8 ,3 i 1 ,8 , 4

( )
Rank=1 ⌈ log 2 (O1 O 2)⌉ N 1 N 2 ⌈ log 2 K NZ ⌉ N/A N/A N/A
⌈ log 2 ⌉
N 3 ≤19 L

⌈ log 2 (O1 O 2)⌉

( )
N 1 N 2 ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉
Rank=2 N/A N/A
⌈ log 2 ⌉
N 3 ≤19 L

( )
Rank=3 ⌈ log 2 (O1 O 2)⌉ N 1 N 2 ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉ N/A
⌈ log 2 ⌉
N 3 ≤19 L

⌈ log 2 (O1 O 2)⌉

( )
N 1 N 2 ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉
Rank=4
⌈ log 2 ⌉
N 3 ≤19 L

3GPP
Release 17 78 3GPP TS 38.212 V17.5.0 (2023-03)

⌈ log 2 (O1 O 2)⌉

( )
N 1 N 2 ⌈ log 2 K NZ ⌉
Rank=1 N/A N/A N/A
⌈ log 2 ⌉
N 3 >19 L

( )
Rank=2 ⌈ log 2 (O1 O 2)⌉ N 1 N 2 ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉ N/A N/A
⌈ log 2 ⌉
N 3 >19 L

⌈ log 2 (O1 O 2)⌉

( )
N 1 N 2 ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉
Rank=3 N/A
⌈ log 2 ⌉
N 3 >19 L

( )
Rank=4 ⌈ log 2 (O1 O 2)⌉ N 1 N 2 ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉
⌈ log 2 ⌉
N 3 >19 L

Information fields X2

i 2 ,3 ,1i 2 ,3 ,2 i 2 ,3 ,3i 2 ,3 , 4 i 1 ,5 i 1 ,6 ,1 i 1 ,6 , 2 i 1 ,6 ,3 i 1 ,6 , 4 {i 2 , 4 ,l }l=1,{i…2 ,5,υ, l }l=1{i,…1,υ,7 , l }l=1 ,… ,υ

( )
Rank=
1
4 N/A N/
A
N/
A
N/A N/A
N 3−1 N/A N/A NZ
3(K −1)
NZ
2 LM1
4 (K −1)
⌈ log 2 ⌉
N 3 ≤19 M 1−1

( )( )
Rank=
2
4 4 N/
A
N/
A
N/A
N 3−1 N/A
N 3−1 N/A NZ
3(K −2)
NZ
4 LM2
4 (K −2)
⌈ log 2 ⌈ log
⌉ ⌉
M 2−1 2 M 2−1
N 3 ≤19

( )( )( )
Rank=
3
4 4 4 N/
A
N/A
N 3−1 N 3−1 N/A
N 3−1 NZ
3(K −3)
NZ
6 L M3
4 (K −3)
⌈ log 2 ⌈ log
⌉ ⌈ log⌉ ⌉
N 3 ≤19 M 3−1 2 M 3−1 2 M 3−1

( )( )( )( )
Rank=
4
4 4 4 4 N/A
N 3−1 N −1 N −1 N −1 NZ
3(K −4)
NZ
8 LM4
4 (K −4)
⌈ log 2 ⌈ log⌉ 2 3 ⌈ log⌉2 3 ⌈ log⌉ 2 3 ⌉
M 4 −1 M 4 −1 M 4 −1 M 4 −1
N 3 ≤19

( )
Rank=
1
4 N/A N/
A
N/
A ⌈ log 2 (2 M 1)⌉ 2 M 1N/A
−1 N/A N/A NZ
3(K −1)
NZ
2 LM1
4 (K −1)
⌈ log 2 ⌉
N 3 >19 M 1−1

( )( )
Rank=
2
4 4 N/
A
N/
A ⌈ log 2 (2 M 2)⌉ 2 M 2−1 2 M N/A 2−1
N/A NZ
3(K −2)
NZ
4 LM2
4 (K −2)
⌈ log 2 ⌈ log 2⌉ ⌉
M 2−1 M 2−1
N 3 >19

( )( )( )
Rank=
3
4 4 4 N/
A ⌈ log 2 (2 M 3)⌉ 2 M 3−1 2 M 3−1 2 M 3N/A −1 NZ
3(K −3)
NZ
6 L M3
4 (K −3)
⌈ log 2 ⌈ log 2⌉ ⌈ log 2⌉ ⌉
N 3 >19 M 3−1 M 3−1 M 3−1

( )( )( )( )
Rank=
4
4 4 4 4
⌈ log 2 (2 M 4 )⌉ 2 M 4−1 2 M 4−1 2 M 4−1 2 M 43(K −1 NZ −4) NZ
8 LM4
4 (K −4)
⌈ log 2 ⌈ log 2⌉ ⌈ log 2⌉ ⌈ log 2⌉ ⌉
M 4 −1 M 4 −1 M 4 −1 M 4 −1
N 3 >19

Note: the bitwidth for {i 1 ,7 , l }l=1 ,… ,υ , {i 2 , 4 ,l }l=1, … ,υ and {i 2 ,5 , l }l=1 ,… ,υ shown in Table [Link].2-1A is the total
bitwidth of {i 1 ,7 , l } , {i 2 , 4 ,l } and {i 2 ,5 , l } up to Rank = υ , respectively, and the corresponding per layer
bitwidths are 2 L M υ , 3 ( K l −1 ), and 4( K l −1 ), (i.e., 1, 3, and 4 bits for each respective indicator
NZ NZ

(3) (2) NZ
elements k l ,i , f , k l ,i , f , and c l ,i , f , respectively), where K l as defined in Clause [Link].5 in [6, TS
υ
38.214] is the number of nonzero coefficients for layer l such that K
NZ
=∑ K NZ
l .
l =1

3GPP
Release 17 79 3GPP TS 38.212 V17.5.0 (2023-03)

The bitwidth for PMI of codebookType= typeII-PortSelection is provided in Tables [Link].2-2, where the values of
PCSI− RS , d , L , N PSK , M 1 , M 2 , and K ( 2 ) are given by Clause [Link].4 in [6, TS 38.214].
Table [Link].2-2: PMI of codebookType= typeII-PortSelection

X1 Information fields
X 2 for wideband PMI or per subband
Information fields for wideband PMI
PMI

i1,1 i1,3 ,1 i1,4 ,1 i1,3 ,2 i1,4 ,2 i2,1 ,1 i2,1 ,2 i2,2 ,1 i2,2 ,2

Rank=1
PCSI−RS
SBAmp ⌈log2 ⌈ ⌉⌉ ⌈log 2 ( 2 L ) ⌉ 3 ( 2L−1 ) N/A N/A ( M 1−1 )⋅log2 N PSK N/A N/A N/A
2d
off

Rank=2
PCSI−RS
SBAmp ⌈log2 ⌈ ⌉⌉ ⌈log 2 ( 2 L ) ⌉ 3 ( 2L−1 ) ⌈log 2 ( 2 L ) ⌉ 3 ( 2L−1 ) ( M 1 −1 )⋅log2 N PSK ( M 2 −1 )⋅log2 N PSK N/A N/A
2d
off

Rank=1 min ( M 1 , K( 2) )⋅log 2 N PSK

PCSI−RS
SBAmp ⌈log2 ⌈ ⌉⌉ ⌈log 2 ( 2 L ) ⌉ 3 ( 2L−1 ) N/A N/A N/A min ( M 1 , K )−1
(2 )
−log 2 N PSK N/A
2d (
+2⋅ M 1 −min ( M 1 , K ( 2)) )
on

Rank=2 min ( M 1 , K( 2) )⋅log 2 N PSK min ( M 2 , K (2 ))⋅log 2 N PSK

PCSI−RS
SBAmp ⌈log2 ⌈ ⌉⌉ ⌈log 2 ( 2 L ) ⌉ 3 ( 2L−1 ) ⌈log 2 ( 2 L ) ⌉ 3 ( 2L−1 ) −log 2 N PSK −log 2 N PSK min ( M 1 , K (2 ))−1 min ( M 2 , K (2 ))−1
2d (
+2⋅ M 1 −min ( M 1 , K ( 2)) ) (
+2⋅ M 2 −min ( M 2 , K( 2) ) )
on

The bitwidth for PMI of codebookType=typeII-PortSelection-r16 is provided in Tables [Link].2-2A, where the values
of PCSI− RS,d , L, K NZ, N 3, and { M l }l=1 , …, υ are given by Clause [Link].6 in [6, TS 38.214].

Table [Link].2-2A: PMI of codebookType= typeII-PortSelection-r16

Information fields X1

i 1 ,1 i 1 ,8 ,1 i 1 ,8 , 2 i 1 ,8 ,3 i 1 ,8 , 4
Rank=1 PCSI−RS NZ
⌈ log 2 K ⌉ N/A N/A N/A
⌈ log 2 ⌈ ⌉⌉
N 3 ≤19 2d

Rank=2 PCSI−RS ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉ N/A N/A

⌈ log 2 ⌈ ⌉⌉
N 3 ≤19 2d

Rank=3 PCSI−RS ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉ N/A

⌈ log 2 ⌈ ⌉⌉
N 3 ≤19 2d

Rank=4 PCSI−RS ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉
⌈ log 2 ⌈ ⌉⌉
N 3 ≤19 2d

Rank=1 PCSI−RS NZ
⌈ log 2 K ⌉ N/A N/A N/A
⌈ log 2 ⌈ ⌉⌉
N 3 >19 2d

3GPP
Release 17 80 3GPP TS 38.212 V17.5.0 (2023-03)

Rank=2 PCSI−RS ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉ N/A N/A

⌈ log 2 ⌈ ⌉⌉
N 3 >19 2d

Rank=3 PCSI−RS ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉ N/A

⌈ log 2 ⌈ ⌉⌉
N 3 >19 2d

Rank=4 PCSI−RS ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉ ⌈ log 2 (2 L)⌉
⌈ log 2 ⌈ ⌉⌉
N 3 >19 2d

Information fields X2

i 2 ,3 ,1i 2 ,3 ,2i 2 ,3 ,3 i 2 ,3 , 4 i 1 ,5 i 1 ,6 ,1 i 1 ,6 , 2 i 1 ,6 ,3 i 1 ,6 , 4 {i 2 , 4 ,l }l=1,{i…2 ,υ,5 , l }l=1{i,…1 ,7,υ , l }l=1 ,… ,υ

( )
Rank=
1
4 N/
A
N/A N/
A
N/A N/A
N 3−1 N/A N/A NZ
3( K −1)
NZ
2 LM1
4 ( K −1)
⌈ log 2 ⌉
M 1−1
N 3 ≤19

( )( )
Rank=
2
4 4 N/A N/
A
N/A
N 3−1 N/A
N 3−1 N/A NZ
3( K −2)
NZ
4 LM2
4 (K −2)
⌈ log 2 ⌈ log
⌉ ⌉
M 2−1 2 M 2−1
N 3 ≤19

( )( ) ( )
Rank=
3
4 4 4 N/
A
N/A
N 3−1 N 3−1 N/A
N 3−1 NZ
3(K −3)
NZ
6 L M3
4 ( K −3)
⌈ log 2 ⌈ log
⌉ ⌈ log
⌉ ⌉
M 3−1 2 M 3−1 2 M 3−1
N 3 ≤19

( )( ) ( )( )
Rank=
4
4 4 4 4 N/A
N 3−1 N −1 N −1 N −1 NZ
3( K −4)
NZ
8 LM4
4 ( K −4)
⌈ log 2 ⌈ log⌉ 2 3 ⌈ log
⌉ 2 3 ⌈ log⌉2 3 ⌉
M 4 −1 M 4 −1 M 4 −1 M 4 −1
N 3 ≤19

( )
Rank=
1
4 N/
A
N/A N/
A ⌈ log 2 (2 M 1)⌉ 2 M 1−1N/A N/A N/A NZ
3( K −1)
NZ
2 LM1
4 ( K −1)
⌈ log 2 ⌉
M 1−1
N 3 >19

( )( )
Rank=
2
4 4 N/A N/
A ⌈ log 2 (2 M 2)⌉ 2 M 2−1 2 M 2−1N/A N/A NZ
3( K −2)
NZ
4 LM2
4 (K −2)
⌈ log 2 ⌈ log ⌉ ⌉
M 2−1 2 M 2−1
N 3 >19

( )( )( )
Rank=
3
4 4 4 N/
A ⌈ log 2 (2 M 3)⌉ 2 M 3−1 2 M 3−1 2 M 3−1N/A NZ
3(K −3)
NZ
6 L M3
4 ( K −3)
⌈ log 2 ⌈ log ⌉ ⌈ log ⌉ ⌉
M 3−1 2 M 3−1 2 M 3−1
N 3 >19

( )( )( )( )
Rank=
4
4 4 4 4
⌈ log 2 (2 M 4 )⌉ 2 M 4−1 2 M 4−1 2 M 4−1 2 M 43( −1 NZ
K −4)
NZ
8 LM4
4 ( K −4)
⌈ log 2 ⌈ log 2⌉ ⌈ log 2⌉ ⌈ log2⌉ ⌉
M 4 −1 M 4 −1 M 4 −1 M 4 −1
N 3 >19

Note: the bitwidth for {i 1 ,7 , l }l=1 ,… ,υ , {i 2 , 4 ,l }l=1, … ,υ and {i 2 ,5 , l }l=1 ,… ,υ shown in Table [Link].2-2A is the total
bitwidth of {i 1 ,7 , l } , {i 2 , 4 ,l } and {i 2 ,5 , l } up to Rank = υ , respectively, and the corresponding per layer
bitwidths are 2 L M υ , 3 ( K l −1 ), and 4( K l −1 ), (i.e., 1, 3, and 4 bits for each respective indicator
NZ NZ

The bitwidth for PMI of codebookType=typeII-PortSelection-r17 is provided in Tables [Link].2-2B, where the values
of PCSI− RS, K 1, K NZ, N 3, N and M are given by Clause [Link].7 in [6, TS 38.214].

3GPP
Release 17 81 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-2B: PMI of codebookType= typeII-PortSelection-r17

Information fields X1

i 1 ,2 i 1 ,6 i 1 ,8 ,1 i 1 ,8 , 2 i 1 ,8 ,3 i 1 ,8 , 4

( )
PCSI −RS /2⌈ log 2 (N −1)⌉ ⌈ log 2 (K ¿¿ 1 M )⌉ ¿ N/A
Rank=1 N/A N/A
⌈ log 2 N⌉ > M=2,
K 1 /2 ifN/A otherwise

( )
PCSI −RS /2⌈ log 2 (N −1)⌉ ⌈ log 2 (K ¿¿ 1 M⌈)⌉log
Rank=2 ¿ 2 (K ¿¿ 1 M )⌉ ¿ N/A N/A
⌈ log 2 ⌉
K 1 /2 ifN/A
N > M=2,
otherwise

( )
PCSI −RS /2⌈ log 2 (N −1)⌉ ⌈ log 2 (K ¿¿ 1 M⌈)⌉log
Rank=3 ¿ 2 (K ¿¿ 1 M⌈)⌉log
¿ 2 (K ¿¿ 1 M )⌉ ¿ N/A
⌈ log 2 if N⌉ > M=2,
K 1 /2 N/A otherwise

( )
PCSI −RS /2⌈ log 2 (N −1)⌉ ⌈ log 2 (K 1 M )⌉ ⌈ log 2 (K 1 M )⌉ ⌈ log 2 (K 1 M )⌉ ⌈ log 2 (K ¿¿ 1 M )⌉ ¿
Rank=4
⌈ log 2 N⌉ > M=2,
K 1 /2 ifN/A otherwise

Information fields X2

i 2 ,3 ,1 i 2 ,3 ,2 i 2 ,3 ,3 i 2 ,3 , 4 {i 2 , 4 ,l }l=1, … ,υ{i 2 ,5 , l }l=1 ,… ,υ {i 1 ,7 , l }l=1 ,… ,υ

Rank=1 4 N/A N/A N/A NZ NZ NZ
3(K −1) 4 (K −1) N/A if K =K 1 M ;
K 1 M otherwise

Rank=2 4 4 N/A N/A NZ NZ N/A if

3(K −2) 4 (K −2) NZ
K =2 K 1 M ;
2 K1 M otherwise

Rank=3 4 4 4 N/A NZ
3( K −3) 4 ( K −3)
NZ
3 K1 M

Rank=4 4 4 4 4 NZ
3(K −4) 4 (K −4)
NZ
4 K1 M

Note: the bitwidth for {i 1 ,7 , l }l=1 ,… ,υ , {i 2 , 4 ,l }l=1, … ,υ and {i 2 ,5 , l }l=1 ,… ,υ shown in Table [Link].2-2B is the total
bitwidth of {i 1 ,7 , l } , {i 2 , 4 ,l } and {i 2 ,5 , l } up to Rank = υ , respectively, and the corresponding per layer
bitwidths are K 1 M , 3 ( K l −1 ), and 4( K l −1 ), (i.e., 1, 3, and 4 bits for each respective indicator
NZ NZ

(3) (2) NZ
elements k l ,i , f , k l ,i , f , and c l ,i , f , respectively), where K l as defined in Clause [Link].7 in [6, TS
υ
38.214] is the number of nonzero coefficients for layer l such that K
NZ
=∑ K NZ
l .
l =1

a( 1) , a( 1) , a(1 ) , a(1 ) ,. .. , a(1()1 ) a( 2) , a(12) , a(22) , a(32) , .. . , a( 2)(2 )

For CSI on PUSCH, two UCI bit sequences are generated, 0 1 2 3 A −1 and 0 A −1 .
The CSI fields of all CSI reports, in the order from upper part to lower part in Table [Link].2-6, are mapped to the UCI

3GPP
Release 17 82 3GPP TS 38.212 V17.5.0 (2023-03)

( 1) ( 1) (1 ) (1 ) (1 ) ( 1)
a 0 , a1 , a2 , a3 ,. .. , a
bit sequence starting with a 0 . The CSI fields of all CSI reports, in the order from upper part
(1)
A −1

a( 2) , a( 2) , a( 2) , a( 2) , .. . , a(A2)(2 )−1 ( 2)
to lower part in Table [Link].2-7, are mapped to the UCI bit sequence 0 1 2 3 starting with a 0 .

The mapping order of CSI fields of one report for CRI/RSRP or SSBRI/RSRP or CRI/RSRP/CapabilityIndex or
SSBRI/RSRP/CapabilityIndex reporting is provided in Table [Link].2-8. The mapping order of CSI fields of one report
for inter-cell SSBRI/RSRP reporting is provided in Table [Link].2-8. The mapping order of CSI fields of one report for
CRI/SINR or SSBRI/SINR or CRI/SINR/CapabilityIndex or SSBRI/SINR/CapabilityIndex reporting is provided in
Table [Link].2-8A. The mapping order of CSI fields of one report for group-based CRI/RSRP or SSBRI/RSRP
reporting is provided in Table [Link].2-8B. The procedure in clause 6.3.2 described for CSI part 1 is also applicable for
one report for CRI/RSRP, SSBRI/RSRP, CRI/SINR, or SSBRI/SINR reporting.

Table [Link].2-3: Mapping order of CSI fields of one CSI report, CSI part 1

CSI report number CSI fields

CRI as in Tables [Link].2-3/4/6, if reported

Rank Indicator as in Tables [Link].2-3/4/5 or [Link].2-8/9, if reported
Wideband CQI for the first TB as in Tables [Link].2-3/4/5 or [Link].2-8/9, if reported
Subband differential CQI for the first TB with increasing order of subband number as in
Tables [Link].2-3/4/5 or [Link].2-8/9, if reported
Indicator of the number of non-zero wideband amplitude coefficients M 0 for layer 0 as in
CSI report #n Table [Link].2-5, if reported
CSI part 1
Indicator of the number of non-zero wideband amplitude coefficients M 1 for layer 1 as in
Table [Link].2-5 (if the rank according to the reported RI is equal to one, this field is set to all
zeros), if 2-layer PMI reporting is allowed according to the rank restriction in Clauses [Link].3
and [Link].4 [6, TS 38.214] and if reported
Indicator of the total number of non-zero coefficients summed across all layers K NZ as in
Table [Link].2-8/9, if reported
Note: Subbands for given CSI report n indicated by the higher layer parameter csi-ReportingBand are numbered
continuously in the increasing order with the lowest subband of csi-ReportingBand as subband 0.

3GPP
Release 17 83 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-3A: Mapping order of CSI fields of one CSI report, CSI part 1, csi-ReportMode= Mode 1

CSI report number CSI fields

CRI as in Tables [Link].2-3A, if associated with one CSI-RS resource pair and if reported
Rank Combination Indicator as in Tables [Link].2-3A, if reported
Wideband CQI for the first TB as in Tables [Link].2-3A, if reported
Subband differential CQI for the first TB with increasing order of subband number as in
Tables [Link].2-3A, if reported
CRI as in Tables [Link].2-3B, if associated with one CSI-RS resource, numberOfSingleTRP-
CSI-Mode1 = 1 and if reported;
First CRI as in Tables [Link].2-3B, if associated with one CSI-RS resource,
numberOfSingleTRP-CSI-Mode1 = 2 and if reported
Rank Indicator associated with CRI as in Tables [Link].2-3B, if numberOfSingleTRP-CSI-
Mode1 = 1 and if reported;
Rank Indicator associated with the first CRI as in Tables [Link].2-3B, if
numberOfSingleTRP-CSI-Mode1 = 2 and if reported
Wideband CQI associated with CRI for the first TB as in Tables [Link].2-3B, if
numberOfSingleTRP-CSI-Mode1 = 1 and if reported;
CSI report #n
Wideband CQI associated with the first CRI for the first TB as in Tables [Link].2-3B, if
CSI part 1
numberOfSingleTRP-CSI-Mode1 = 2 and if reported
Subband differential CQI associated with CRI for the first TB with increasing order of subband
number as in Tables [Link].2-3B, if numberOfSingleTRP-CSI-Mode1 = 1 if reported;
Subband differential CQI associated with the first CRI for the first TB with increasing order of
subband number as in Tables [Link].2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if
reported
Second CRI as in Tables [Link].2-3B, if associated with one CSI-RS resource,
numberOfSingleTRP-CSI-Mode1 = 2 and if reported
Rank Indicator associated with the second CRI as in Tables [Link].2-3B, if
numberOfSingleTRP-CSI-Mode1 = 2 and if reported
Wideband CQI associated with the second CRI for the first TB as in Tables [Link].2-3B, if
numberOfSingleTRP-CSI-Mode1 = 2 and if reported
Subband differential CQI associated with the second CRI for the first TB with increasing order
of subband number as in Tables [Link].2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if
reported
Note: Subbands for given CSI report n indicated by the higher layer parameter csi-ReportingBand are numbered
continuously in the increasing order with the lowest subband of csi-ReportingBand as subband 0.

Table [Link].2-3B: Mapping order of CSI fields of one CSI report, CSI part 1, csi-ReportMode= Mode 2

CSI report number CSI fields

CRI as in Tables [Link].2-3A, if associated with one CSI-RS resource pair and if reported;
CRI as in Tables [Link].2-3B, if associated with one CSI-RS resource and if reported
Rank Combination Indicator as in Tables [Link].2-3A, if associated with one CSI-RS resource
pair and if reported;
Rank Indicator as in Tables [Link].2-3B, if associated with one CSI-RS resource and if
reported;
CSI report #n Zero padding bits O P, if needed
CSI part 1 Wideband CQI for the first TB as in Tables [Link].2-3A, if associated with one CSI-RS
resource pair and if reported;
Wideband CQI for the first TB as in Tables [Link].2-3B, if associated with one CSI-RS
resource and if reported
Subband differential CQI for the first TB with increasing order of subband number as in Tables
[Link].2-3A, if associated with one CSI-RS resource pair and if reported;
Subband differential CQI for the first TB with increasing order of subband number as in Tables
[Link].2-3B, if associated with one CSI-RS resource and if reported
Note: Subbands for given CSI report n indicated by the higher layer parameter csi-ReportingBand are numbered
continuously in the increasing order with the lowest subband of csi-ReportingBand as subband 0.

3GPP
Release 17 84 3GPP TS 38.212 V17.5.0 (2023-03)

The number of zero padding bits O P in Table [Link].2-9B is 0 for 1 CSI-RS port and O P=N max −N reported (R) for
more than 1 CSI-RS port, where

- N max = max N (r ). S the set of rank and rank combination values r that are allowed to be reported. N ( r )
r ∈ SRank Rank is

is obtained according to Tables [Link].2-3A/3B for rank combination indicator and rank indicator respectively.

- N reported (R)is obtained according to Tables [Link].2-3A for rank combination indicator and R is the reported
rank combination

- N reported (R) is obtained according to Tables [Link].2-3B for rank indicator and R is the reported rank

Table [Link].2-4: Mapping order of CSI fields of one CSI report, CSI part 2 wideband

CSI report
CSI fields
number
Wideband CQI for the second TB as in Tables [Link].2-3/4/5, if present and reported
Layer Indicator as in Tables [Link].2-3/4/5, if reported

CSI report #n PMI wideband information fields

X 1 , from left to right as in Tables [Link].2-1/2 or [Link].2-
CSI part 2 1/2, if reported
wideband X 2 , from left to right as in Tables [Link].2-1/2 or [Link].2-
PMI wideband information fields
1/2, or codebook index for 2 antenna ports according to Clause [Link].1 in [6, TS38.214], if
pmi-FormatIndicator= widebandPMI and if reported

3GPP
Release 17 85 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-4A: Mapping order of CSI fields of one CSI report, CSI part 2 wideband, csi-
ReportMode= Mode 1

PMI wideband information fields

X 1 , from left to right as in Tables [Link].2-1
associated with the first resource within the CSI-RS resource pair, if reported

PMI wideband information fields

X 1 , from left to right as in Tables [Link].2-1
associated with the second resource within the CSI-RS resource pair, if reported

PMI wideband information fields

X
2 , from left to right as in Tables [Link].2-1, or
codebook index for 2 antenna ports according to Clause [Link].1 in [6, TS38.214]
associated with the second CSI-RS resource within the CSI-RS resource pair, if pmi-
FormatIndicator= widebandPMI and if reported
Wideband CQI for the second TB as in Tables [Link].2-3B, if associated with CRI in CSI
part 1, numberOfSingleTRP-CSI-Mode1 = 1 and if reported;
Wideband CQI for the second TB as in Tables [Link].2-3B, if associated with the first
CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if reported
Layer Indicator as in Table [Link].2-3B, if associated with CRI in CSI part 1,
numberOfSingleTRP-CSI-Mode1 = 1 and if reported;
Layer Indicator as in Table [Link].2-3B, if associated with the first CRI in CSI part 1,
numberOfSingleTRP-CSI-Mode1 = 2 and if reported
CSI report #n
CSI part 2 PMI wideband information fields
X
1 , from left to right as in Tables [Link].2-1, if
wideband associated with CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 1 and if reported;

PMI wideband information fields

X1 , from left to right as in Tables [Link].2-1, if
associated with the first CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if
reported

PMI wideband information fields

X
2 , from left to right as in Tables [Link].2-1, or
codebook index for 2 antenna ports according to Clause [Link].1 in [6, TS38.214], if
associated with CRI in CSI part 1, pmi-FormatIndicator= widebandPMI,
numberOfSingleTRP-CSI-Mode1 = 1 and if reported;

PMI wideband information fields

X2 , from left to right as in Tables [Link].2-1, or
codebook index for 2 antenna ports according to Clause [Link].1 in [6, TS38.214], if
associated with the first CRI in CSI part 1, pmi-FormatIndicator= widebandPMI,
numberOfSingleTRP-CSI-Mode1 = 2 and if reported
Wideband CQI for the second TB as in Tables [Link].2-3B, if associated with the second
CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if reported
Layer Indicator as in Table [Link].2-3B, if associated with the second CRI in CSI part 1,
numberOfSingleTRP-CSI-Mode1 = 2 and if reported

PMI wideband information fields

X
1 , from left to right as in Tables [Link].2-1, if
associated with the second CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if
reported

PMI wideband information fields

X
2 , from left to right as in Tables [Link].2-1, or
codebook index for 2 antenna ports according to Clause [Link].1 in [6, TS38.214], if
associated with the second CRI in CSI part 1, pmi-FormatIndicator= widebandPMI,
numberOfSingleTRP-CSI-Mode1 = 2 and if reported

3GPP
Release 17 86 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-4B: Mapping order of CSI fields of one CSI report, CSI part 2 wideband, csi-
ReportMode= Mode 2

CSI report
CSI fields
number
Wideband CQI for the second TB as in Tables [Link].2-3B, if reported part 1 is associated
with one CSI-RS resource and if reported
Two Layer Indicators as in Table [Link].2-3A, if reported part 1 is associated with one CSI-
RS resource pair, where the first Layer Indicator and the second Layer Indicator are
associated with the first resource and the second resource within the resource pair
respectively and if reported;
Layer Indicator as in Table [Link].2-3B, if reported part 1 is associated with one CSI-RS
resource and if reported
X
PMI wideband information fields 1 , from left to right as in Tables [Link].2-1 associated with
the first resource within the CSI-RS resource pair, if reported part 1 is associated with one
CSI-RS resource pair and if reported

PMI wideband information fields

X 2 , from left to right as in Tables [Link].2-1, or codebook
index for 2 antenna ports according to Clause [Link].1 in [6, TS38.214] associated with the
first CSI-RS resource within the CSI-RS resource pair, if pmi-FormatIndicator= widebandPMI
CSI report #n
and reported part 1 is associated with one CSI-RS resource pair and if reported
CSI part 2
wideband X
PMI wideband information fields 1 , from left to right as in Tables [Link].2-1 associated with
the second CSI-RS resource within the CSI-RS resource pair, if reported part 1 is associated
with one CSI-RS resource pair and if reported

PMI wideband information fields

X 2 , from left to right as in Tables [Link].2-1, or codebook
index for 2 antenna ports according to Clause [Link].1 in [6, TS38.214], if pmi-
FormatIndicator= widebandPMI and reported part 1 is associated with one CSI-RS resource
and if reported

Table [Link].2-5: Mapping order of CSI fields of one CSI report, CSI part 2 subband

Subband differential CQI for the second TB of all even subbands with increasing order of
subband number, as in Tables [Link].2-3/4/5, if cqi-FormatIndicator=subbandCQI and if reported

PMI subband information fields

X 2 of all even subbands with increasing order of subband
number, from left to right as in Tables [Link].2-1/2 or [Link].2-1/2, or codebook index for 2
antenna ports according to Clause [Link].1 in [6, TS38.214] of all even subbands with increasing
CSI report #n order of subband number, if pmi-FormatIndicator= subbandPMI and if reported
Part 2 subband Subband differential CQI for the second TB of all odd subbands with increasing order of subband
number, as in Tables [Link].2-3/4/5, if cqi-FormatIndicator=subbandCQI and if reported

PMI subband information fields

X 2 of all odd subbands with increasing order of subband
number, from left to right as in Tables [Link].2-1/2 or [Link].2-1/2, or codebook index for 2
antenna ports according to Clause [Link].1 in [6, TS38.214] of all odd subbands with increasing
order of subband number, if pmi-FormatIndicator= subbandPMI and if reported
Note: Subbands for given CSI report n indicated by the higher layer parameter csi-ReportingBand are numbered
continuously in the increasing order with the lowest subband of csi-ReportingBand as subband 0.

3GPP
Release 17 87 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-5A: Mapping order of CSI fields of one CSI report, CSI part 2 of codebookType=typeII-
r16 or typeII-PortSelection-r16

CSI report
CSI fields
number

CSI report #n
CSI part 2, group 0
PMI fields X 1, from left to right as in Tables [Link].2-1A/2A, if reported

The following PMI fields X 2 , from left to right, as in Tables [Link].2-1A/2A:

NZ
{ i2 ,3 , l :l=1 , … , υ }, i1 ,5, { i1 ,6 , l :l=1, … , υ } and max ⁡(0 , ⌈ K ⌉ −υ)× 3 highest
2
priority bits of
CSI report #n NZ
K
CSI part 2, group 1 {i2 , 4 ,l :l=1 , … ,υ } , max ⁡(0 , ⌈ ⌉−υ )× 4 highest priority bits of {i 2 ,5 , l :l=1, … , υ }
2
and ν∗2 L M υ −⌊ K /2 ⌋ highest priority bits of{ i 1 ,7 , l :l=1 , … , υ }, in decreasing order of
NZ

priority based on the corresponding function Pri ( l , i, f ) defined in clause 5.2.3 of TS38.214,
if reported
The following PMI fields X 2 , from left to right, as in Tables [Link].2-1A/2A:

( )
NZ
K
NZ
min K −v , ⌊ ⌋ × 3 lowest priority bits of
2

:l=1 , … ,υ } , min ( K ⌋ )× 4
CSI report #n NZ
K lowest priority bits of { i 2 ,5 , l :l=1 , … , υ }
CSI part 2, group 2 {i2 , 4 ,l NZ
−v , ⌊
2
and ⌊ K NZ /2 ⌋ lowest priority bits of { i 1 ,7 , l :l=1 , … , υ }, in decreasing order of priority
based on the corresponding function Pri ( l , i, f ) defined in clause 5.2.3 of TS38.214, if
reported

Table [Link].2-5B: Mapping order of CSI fields of one CSI report, CSI part 2 of codebookType=typeII-
PortSelection-r17

CSI report
CSI fields
number

CSI report #n
CSI part 2, group 0
PMI fields X 1 , from left to right as in Tables [Link].2-2B, if reported

The following PMI fields X 2 , from left to right, as in Tables [Link].2-2B:{ i 2 ,3 , l :l=1 , … , υ }
NZ
K
(max ⁡(0 , ⌈ ⌉ −υ))×3 highest priority bits of
2
NZ
CSI report #n K
CSI part 2, group 1 {i2 , 4 ,l :l=1 , … ,υ } ,(max ⁡(0 , ⌈ ⌉ −υ))× 4 highest priority bits of
2
{i 2 ,5 , l :l=1, … , υ } and ν∗K 1 M −⌊ K NZ /2 ⌋ highest priority bits of{ i 1 ,7 , l :l=1 , … , υ },
in decreasing order of priority based on the corresponding function Pri ( l , i, f ) defined in
clause 5.2.3 of TS38.214, if reported
The following PMI fields X 2 , from left to right, as in Tables [Link].2-2B:

( )
NZ
NZ K
(min K −v , ⌊ ⌋ )× 3 lowest priority bits of
2

( )
CSI report #n NZ
K
CSI part 2, group 2 {i2 , 4 ,l :l=1 , … ,υ } ,(min K NZ−v , ⌊ ⌋ )× 4 lowest priority bits of
2
{i2 ,5 , l :l=1 , … , υ } and ⌊ K NZ /2 ⌋ lowest priority bits of {i1 ,7 , l :l=1 , … , υ }, in decreasing
order of priority based on the corresponding function Pri ( l , i, f ) defined in clause 5.2.3 of
TS38.214, if reported

3GPP
Release 17 88 3GPP TS 38.212 V17.5.0 (2023-03)

3GPP
Release 17 89 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-5C: Mapping order of CSI fields of one CSI report, CSI part 2 subband, ReportMode=
Mode 1

3GPP
Release 17 90 3GPP TS 38.212 V17.5.0 (2023-03)

PMI subband information fields

3GPP
Release 17 91 3GPP TS 38.212 V17.5.0 (2023-03)

numberOfSingleTRP-CSI-Mode1 = 2 and if reported

PMI subband information fields

Table [Link].2-5D: Mapping order of CSI fields of one CSI report, CSI part 2 subband, ReportMode=
Mode 2

PMI subband information fields

3GPP
Release 17 92 3GPP TS 38.212 V17.5.0 (2023-03)

( 1) ( 1) (1 ) (1 ) (1 )
a 0 , a1 , a2 , a3 ,. .. , a (1)
Table [Link].2-6: Mapping order of CSI reports to UCI bit sequence A −1 ,
with two-part CSI report(s)

UCI bit sequence CSI report number

where CSI report #1, CSI report #2, …, CSI report #n in Table [Link].2-6 correspond to the CSI reports in increasing
order of CSI report priority values according to Clause 5.2.5 of [6, TS38.214].

a(02) , a(12) , a(22) , a(32) , .. . , a( 2)(2 )

Table [Link].2-7: Mapping order of CSI reports to UCI bit sequence A −1 ,
with two-part CSI report(s)

UCI bit sequence CSI report number

CSI report #1, CSI part 2 wideband, as in Table [Link].2-

4/4A/4B,
or CSI part 2 with group 0, as in Table [Link].2-5A/5B,
if CSI part 2 exists for CSI report #1
CSI report #2, CSI part 2 wideband, as in Table [Link].2-
4/4A/4B,
or CSI part 2 with group 0, as in Table [Link].2-5A/5B,
if CSI part 2 exists for CSI report #2

…
a(02) CSI report #n, CSI part 2 wideband, as in Table [Link].2-
( 2) 4/4A/4B,
a1
or CSI part 2 with group 0, as in Table [Link].2-5A/5B,
a(22) if CSI part 2 exists for CSI report #n
( 2) CSI report #1, CSI part 2 subband, as in Table [Link].2-
a3 5/5C/5D,
⋮ or CSI part 2 with group 1 and 2, as in Table [Link].2-5A/5B,
(2 )
a A(2 )−1 if CSI part 2 exists for CSI report #1
CSI report #2, CSI part 2 subband, as in Table [Link].2-
5/5C/5D,
or CSI part 2 with group 1 and 2, as in Table [Link].2-5A/5B,
if CSI part 2 exists for CSI report #2

CSI report #n, CSI part 2 subband, as in Table [Link].2-

5/5C/5D,
or CSI part 2 with group 1 and 2, as in Table [Link].2-5A/5B,
if CSI part 2 exists for CSI report #n

where CSI report #1, CSI report #2, …, CSI report #n in Table [Link].2-7 correspond to the CSI reports in increasing
order of CSI report priority values according to Clause 5.2.5 of [6, TS38.214].

The bitwidth for RI/CQI of codebookType= typeII-r16 or codebookType=typeII-PortSelection-r16 is provided in Table

[Link].2-8.

3GPP
Release 17 93 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-8: RI and CQI of codebookType=typeII-r16 or typeII-PortSelection-r16

Field Bitwidth

Rank Indicator min ( 2 , ⌈ log 2 n RI ⌉ )

where n RI is the number of allowed rank indicator values according to Clauses [Link].5 and [Link].6 [6, TS 38.214],
N3
K 0=⌈ 2 L ⌈ p1 × ⌉ β ⌉ , where p1, N 3, R , and β are given by Clause [Link].5 and [Link].6 in [6, TS 38.214].
R
The values of the rank indicator field are mapped to allowed rank indicator values with increasing order, where '0' is
mapped to the smallest allowed rank indicator value. The values of the K NZ indicator field are mapped to the allowed
values of K NZ , according to Clauses [Link].5 and [Link].6 [6, TS 38.214], with increasing order, where '0' is mapped
to K NZ=1.

The bitwidth for RI/CQI of codebookType=typeII-PortSelection-r17 is provided in Table [Link].2-9.

Table [Link].2-9: RI and CQI of codebookType=typeII-PortSelection-r17

Field Bitwidth

Rank Indicator min ( 2 , ⌈ log 2 n RI ⌉ )

Wide-band CQI 4
Subband differential CQI 2
⌈ log 2 (K 0 )⌉ if max
Indicator of the total number of non-zero coefficients allowed rank is 1;
summed across all layers K NZ ⌈ log 2 (2 K 0 )⌉
otherwise
where n RI is the number of allowed rank indicator values according to Clauses [Link].7 [6, TS 38.214],
K 0=⌈ K 1 Mβ ⌉ , where K 1, M , and β are given by Clause [Link].7 in [6, TS 38.214]. The values of the rank
indicator field are mapped to allowed rank indicator values with increasing order, where '0' is mapped to the smallest
allowed rank indicator value. The values of the K NZ indicator field are mapped to the allowed values of K NZ,
according to Clauses [Link].7 [6, TS 38.214], with increasing order, where '0' is mapped to K NZ=1 .

[Link].3 CG-UCI
For CG-UCI bits transmitted on a CG PUSCH when the higher layer parameter cg-RetransmissionTimer is configured,
the CG-UCI bit sequence a 0 , a 1 , a2 , a3 , … , a A −1 is determined as follows:

set a i=~
CG−UCI
- oi for i=0 , 1 , … ,O CG−UCI −1 and A=O CG−UCI , where the CG-UCI bit sequence
~oCG−UCI , ~oCG−UCI , … , ~
oO
CG−UCI
is given by Table [Link].3-1, mapped in the order from upper part to lower
0 1 CG−UCI
−1
part.

3GPP
Release 17 94 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].3-1: Mapping order of CG-UCI fields

Field Bitwidth
5 if nrofHARQ-Processes-v1700 in ConfiguredGrantConfig is
HARQ process number configured;
4 otherwise.
Redundancy version 2
New data indicator 1
⌈ log 2 C ⌉ if both higher layer parameter ul-toDL-COT-
SharingED-Threshold and higher layer parameter cg-COT-
SharingList are configured, or if both higher layer parameter
semiStaticChannelAccessConfigUE and higher layer
parameter cg-COT-SharingList are configured, or if higher
layer parameter cg-COT-SharingList is configured in frequency
range 2-2, where C is the number of combinations configured
in cg-COT-SharingList;

1 if higher layer parameter ul-toDL-COT-SharingED-Threshold

Channel Occupancy Time (COT) sharing is not configured, and if higher layer parameter
information semiStaticChannelAccessConfigUE is not configured, and if
higher layer parameter cg-COT-SharingOffset is configured;

0 otherwise.

If a UE indicates COT sharing other than "no sharing" in a CG

PUSCH within the UE's initiated COT, the UE should provide
consistent COT sharing information in all the subsequent CG
PUSCHs, if any, occurring within the same UE's initiated COT
such that the same DL starting point and duration are
maintained.

[Link].4 HARQ-ACK and CG-UCI

When higher layer parameter cg-UCI-Multiplexing is configured, the UCI bit sequence a 0 , a 1 , a2 , a3 , … , a A −1 is
determined as follows, where A=O CG−UCI + O ACK .

The CG-UCI bits are mapped to the UCI bit sequencea 0 , a 1 , a2 , a3 , … , aOCG −UCI −1, where a i=~
CG−UCI
- oi for
−1. The CG-UCI bit sequence ~
CG−UCI ~CG−UCI
, … ,~
CG−UCI CG−UCI
i=0 , 1 , … ,O o0 , o1 oO −1
is given by Table
CG−UCI

CG−UCI
[Link].3-1 mapped in the order from upper part to lower part, and O is number of CG-UCI bits;

- The HARQ-ACK bits are mapped to the UCI bit sequence a OCG−UCI , aOCG−UCI +1 , … , aOCG−UCI +O ACK−1, where
=~ for i=0 , 1 , … ,O ACK −1. The HARQ-ACK bit sequence ~ ,~ , … ,~
ACK ACK ACK ACK
a i+O CG−UCI oi o0 o1 oO −1 is given
ACK

ACK
by Clause 9.1 of [5, TS38.213], and O is number of HARQ-ACK bits.

[Link].5 UCI with different priority indexes

If uci-MuxWithDiffPrio is configured, and HARQ-ACK bits associated with priority index 0, and CSI part 1 if any are
transmitted on a PUSCH associated with priority index 1, the following UCI bit sequences are generated,
(1) (1) (1) (1) (1 ) (2) (2) (2) (2) ( 2)
a 0 , a1 , a2 , a3 , … , a A(1)−1, and a 0 , a1 , a2 , a3 , … , a A( 2)−1 if any, according to the following:
- If CSI part 1 is also transmitted on the PUSCH,
(1)
- Set a i for i=0 , 1 , … , A(1)−1 as the bit sequence of CSI part 1, where the CSI fields of all CSI reports, in
the order from upper part to lower part in Table [Link].2-6, are mapped to the UCI bit sequence
(1) (1) (1) (1) (1 )
a 0 , a1 , a2 , a3 , … , a A(1)−1 starting with a(1)
0
.

3GPP
Release 17 95 3GPP TS 38.212 V17.5.0 (2023-03)

Set a i =~
(2) ACK −LP
- oi for i=0 , 1 , … ,O ACK −LP −1 and A(2)=O ACK −LP , where the HARQ-ACK bit
sequence ~ , ~o1 , … , ~oO
ACK −L P ACK −L P ACK −L P
o0 associated with priority index 0 is given by Clause 9.1 of [5,
ACK −L P
−1
TS 38.213].

Otherwise, set a i =~
(1) ACK −LP
- oi for i=0 , 1 , … ,O ACK −LP −1 and A(1)=O ACK −LP , where the HARQ-ACK bit
sequence ~ ,~ , … , ~oO
ACK −L P ACK −L P ACK −L P
o0 o1 associated with priority index 0 is given by Clause 9.1 of [5, TS
ACK −L P
−1
38.213].

If uci-MuxWithDiffPrio is configured, and HARQ-ACK bits associated with priority index 1, and CSI if any are
transmitted on a PUSCH associated with priority index 0, the following UCI bit sequences are generated,
(1 ) ( 2)
a 0 , a 1 , a2 , a3 , … , a A −1, a(1) (1) (1) (1) (2) (2) (2) (2)
0 , a1 , a2 , a3 , … , a A(1)−1 if any, and a 0 , a1 , a2 , a3 , … , a A( 2)−1 if any, according
to the following:

- If HARQ-ACK bits associated with priority index 1 and CSI are transmitted on the PUSCH without UL-SCH
and the CSI includes CSI part 1 without CSI part 2, and there is only one HARQ-ACK bit associated with
priority index 1 given by Clause 9.1 of [5, TS 38.213], set a 0=~ , a 1=0, and A=2; otherwise, set
ACK− HP
o0
a i =~
ACK − HP
oi for i=0 , 1 , … ,O ACK −HP −1 and A=O ACK− HP, where the HARQ-ACK bit sequence
~
o0
ACK −HP ~ ACK −HP
, o1 , … , ~oO
ACK −HP
associated with priority index 1 is given by Clause 9.1 of [5, TS 38.213];
ACK −HP
−1

(1)
- Set a i for i=0 , 1 , … , A(1)−1 as the bit sequence of CSI part 1, if CSI part 1 is also transmitted on the
PUSCH, where the CSI fields of all CSI reports, in the order from upper part to lower part in Table [Link].2-6,
(1) (1) (1) (1) (1 ) (1)
are mapped to the UCI bit sequence a 0 , a1 , a2 , a3 , … , a A(1)−1 starting with a 0 ;

(2)
- Set a i for i=0 , 1 , … , A(2)−1 as the bit sequence of CSI part 2, if CSI part 2 is also transmitted on the
PUSCH, where the CSI fields of all CSI reports, in the order from upper part to lower part in Table [Link].2-7,
(2) (2) (2) (2) ( 2) (2)
are mapped to the UCI bit sequence a 0 , a1 , a2 , a3 , … , a A( 1)−1 starting with a 0 .

If uci-MuxWithDiffPrio is configured, and HARQ-ACK bits associated with priority index 0, HARQ-ACK bits
associated with priority index 1 and/or CG-UCI associated with priority index 1, and CSI part 1 if any are transmitted
(1) (1) (1) (1) (1 )
on a PUSCH, the following UCI bit sequences are generated,a 0 , a 1 , a2 , a3 , … , a A −1, a 0 , a1 , a2 , a3 , … , a A(1)−1,
(2) (2) (2) (2) ( 2)
and a 0 , a1 , a2 , a3 , … , a A( 2)−1 if any, according to the following:

Set a i=~
ACK − HP
- oi for i=0 , 1 , … ,O ACK −HP −1 and A=O ACK− HP if HARQ-ACK bits associated with
priority index 1 are transmitted without CG-UCI associated with priority index 1, where the HARQ-ACK bit
sequence ~
ACK −HP ~ ACK −HP
, … , ~oO ACK −HP−1 associated with priority index 1 is given by Clause 9.1 of [5, TS
ACK −HP
o0 , o1
38.213];

Set a i=~
CG−UCI
- oi for i=0 , 1 , … ,O CG−UCI −1 and A=O CG−UCI if CG-UCI associated with priority index 1
is transmitted without HARQ-ACK bits associated with priority index 1, where the CG-UCI bit sequence
~oCG−UCI , ~oCG−UCI , … , ~ CG−UCI
oOCG−UCI −1 associated with priority index 1 is given by Table [Link].3-1, mapped in the
0 1
order from upper part to lower part;

- Set a 0 , a 1 , a2 , a3 , … , a A −1 as follows, if both CG-UCI associated with priority index 1 and HARQ-ACK bits
associated with priority index 1 are transmitted, where A=O CG−UCI + O ACK− HP

The CG-UCI bits are mapped to the UCI bit sequence a 0 , a 1 , a2 , a3 , … , aOCG −UCI −1, where a i=~
CG−UCI
- oi for
−1. The CG-UCI bit sequence ~o0
CG−UCI ~CG−UCI
, … ,~
CG−UCI CG−UCI
i=0 , 1 , … ,O , o1 oO −1
is given by Table CG−UCI

CG−UCI
[Link].3-1 mapped in the order from upper part to lower part, and O is number of CG-UCI bits

3GPP
Release 17 96 3GPP TS 38.212 V17.5.0 (2023-03)

- The HARQ-ACK bits are mapped to the UCI bit sequence a OCG−UCI , aOCG−UCI +1 , … , aOCG−UCI +O ACK−HP−1, where
=~
ACK − H P
a i+O oi
CG−UCI for i=0 , 1 , … ,O ACK −HP −1. The HARQ-ACK bit sequence
~
o0
ACK −HP ~ ACK −HP
, o1 , … , ~oO
ACK −HP
associated with priority index 1 is given by Clause 9.1 of [5, TS 38.213].
ACK −HP
−1

- If CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 1,
(1)
- Set a i for i=0 , 1 , … , A(1)−1 as the bit sequence of CSI part 1, where the CSI fields of all CSI reports, in
the order from upper part to lower part in Table [Link].2-6, are mapped to the UCI bit sequence
(1) (1) (1) (1) (1 )
a 0 , a1 , a2 , a3 , … , a A(1)−1 starting with a(1)
0
.

- Otherwise,

Set a i =~
(1) ACK −LP
- oi for i=0 , 1 , … ,O ACK −LP −1 and A(1)=O ACK −LP , where the HARQ-ACK bit
sequence ~ , ~o1 , … , ~oO
ACK −L P ACK −L P ACK −L P
o0 associated with priority index 0 is given by Clause 9.1 of [5,
ACK −L P
−1
TS 38.213].

Set a i =~ ai for i=0 , 1 , … , ~ (2) ~(1)

(2) (1) ( 1)
- A −1and A = A , if CSI part 1 is also transmitted on the PUSCH and
the PUSCH is associated with priority index 0, where the CSI part 1 sequence
~
a 0 , ~a1 , ~
(1) (1 )
a 2 , ~a3 , … , ~
(1) (1) (1) (1) (1) (1) (1) (1 )
a~A( 1)−1 is given by Table [Link].2-6 by replacing a 0 , a1 , a2 , a3 , … , a A(1)−1,
and the CSI fields of all CSI reports, in the order from upper part to lower part in Table [Link].2-6, are
mapped to the CSI part 1 sequence ~ a 0 , ~a1 , ~a 2 , ~a3 , … , ~
a~A( 1)−1 starting with ~
(1) (1 ) (1) (1) (1) (1)
a0 .
If uci-MuxWithDiffPrio is configured, and CG-UCI associated with priority index 0 and HARQ-ACK bits associated
with priority index 0 if any, HARQ-ACK bits associated with priority index 1, and CSI part 1 if any are transmitted on a
PUSCH associated with priority index 0, the following UCI bit sequences are generated,a 0 , a 1 , a2 , a3 , … , a A −1,
(1) (1) (1) (1) (1 ) (2) (2) (2) (2) ( 2)
a 0 , a1 , a2 , a3 , … , a A (1)
−1
, and a 0 , a1 , a2 , a3 , … , a A( 2)−1 if any, according to the following:

Set a i=~
ACK − HP
- oi for i=0 , 1 , … ,O ACK −HP −1 and A=O ACK− HP, where the HARQ-ACK bit sequence
~
o0
ACK −HP ~ ACK −HP
, o1 , … , ~oO
ACK −HP
associated with priority index 1 is given by Clause 9.1 of [5, TS 38.213];
ACK −HP
−1

Set a i =~
(1) CG−UCI
- oi for i=0 , 1 , … ,O CG−UCI −1 and A(1)=O CG−UCI if CG-UCI associated with priority
index 0 is transmitted without HARQ-ACK bits associated with priority index 0, where the CG-UCI bit sequence
~oCG−UCI , ~oCG−UCI , … , ~ CG−UCI
oOCG−UCI −1 associated with priority index 0 is given by Table [Link].3-1, mapped in the
0 1
order from upper part to lower part;
(1) (1) (1) (1) (1 )
- Set a 0 , a1 , a2 , a3 , … , a A(1)−1 as follows if both CG-UCI associated with priority index 0 and HARQ-ACK
bits associated with priority index 0 are transmitted, where A(1)=O CG−UCI +O ACK −LP
(1) (1) (1) (1) (1 )
- The CG-UCI bits are mapped to the UCI bit sequence a 0 , a1 , a2 , a3 , … , aOCG −UCI −1, where
a i =~oi for i=0 , 1 , … ,O CG−UCI −1. The CG-UCI bit sequence ~ , ~o1 , … ,~
(1) CG−UCI CG−UCI CG−UCI CG−UCI
o0 oO −1
CG−UCI

is given by Table [Link].3-1 mapped in the order from upper part to lower part, and O CG−UCI is number of
CG-UCI bits
(1) (1) (1 )
- The HARQ-ACK bits are mapped to the UCI bit sequence a OCG−UCI , aOCG−UCI +1 , … , aOCG−UCI +O ACK−LP−1, where
(1)
a i+O ~ACK − LP for i=0 , 1 , … ,O ACK −LP −1. The HARQ-ACK bit sequence
=o
CG−UCI
i
~
o
ACK −L P ~ ACK −L P
,o , … , ~o
ACK −L P
associated with priority index 0 is given by Clause 9.1 of [5, TS 38.213].
0 1 O
ACK −L P
−1

3GPP
Release 17 97 3GPP TS 38.212 V17.5.0 (2023-03)

Set a i =~ for i=0 , 1 , … , ~ (2) ~(1)

(2) (1) ( 1)
- ai A −1and A = A , if CSI part 1 is also transmitted on the PUSCH and the
PUSCH is associated with priority index 0, where the CSI part 1 sequence ~
a 0 , ~a1 , ~a 2 , ~a3 , … , ~
(1) (1 ) (1) (1) (1)
a~A( 1)−1 is
(1) (1) (1) (1) (1 )
given by Table [Link].2-6 by replacing a 0 , a1 , a2 , a3 , … , a A(1)−1 , and the CSI fields of all CSI reports, in
the order from upper part to lower part in Table [Link].2-6, are mapped to the CSI part 1 sequence
~
a 0 , ~a1 , ~
(1) (1 )
a 2 , ~a3 , … , ~
(1) (1)
a~A( 1)−1 starting with ~
(1) (1)
a0 .

[Link] Code block segmentation and CRC attachment

Denote the bits of the payload by 0 1 2 3

a , a , a , a , . .. , a
A −1 , where A is the payload size. The procedure in [Link].1

applies for A≥12 and the procedure in Clause [Link].2 applies for A≤11 .

[Link].1 UCI encoded by Polar code

Code block segmentation and CRC attachment is performed according to Clause [Link].1.

[Link].2 UCI encoded by channel coding of small block lengths

The procedure in Clause [Link].2 applies.

[Link] Channel coding of UCI

[Link].1 UCI encoded by Polar code

Channel coding is performed according to Clause [Link].1, except that the rate matching output sequence length
Er is
given in Clause [Link].1.

[Link].2 UCI encoded by channel coding of small block lengths

Information bits are delivered to the channel coding block. They are denoted by
c 0 , c 1 , c 2 , c 3 , .. . , c K −1 , where K is the
number of bits.

The information bits are encoded according to Clause 5.3.3.

After encoding the bits are denoted by

d 0 ,d1 ,d 2 ,d3 ,...,d N−1 , where N is the number of coded bits.

[Link] Rate matching

[Link].1 UCI encoded by Polar code
[Link].1.1 HARQ-ACK

For HARQ-ACK transmission on PUSCH not using repetition type B with UL-SCH and if numberOfSlotsTBoMS is not
present in the resource allocation table, or if numberOfSlotsTBoMS is present in the resource allocation table and the
value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI is equal to 1,

the number of coded modulation symbols per layer for HARQ-ACK transmission, denoted as
Q'ACK , is determined as
follows:

{ }
N PUSCH
symb,all
−1

( PUSCH
)
O ACK + L ACK ⋅β offset ⋅ ∑ M UCI
sc ( l )
PUSCH
N symb,all −1
'
Q ACK =min ⌈ C
UL−SCH
l=0
−1
⌉,⌈α⋅ ∑ M UCI
sc ( l ) ⌉
l =l
∑ Kr
0

r=0

where

-
OACK is the number of HARQ-ACK bits;

3GPP
Release 17 98 3GPP TS 38.212 V17.5.0 (2023-03)

- if , ; otherwise is the number of CRC bits for HARQ-ACK determined according to

Clause [Link].1;

-
β PUSCH HARQ−ACK
offset =β offset ;

-
C UL−SCH is the number of code blocks for UL-SCH of the PUSCH transmission;
- if the DCI format scheduling the PUSCH transmission includes a CBGTI field indicating that the UE shall not
transmit the r -th code block,
K r =0; otherwise, K r is the r -th code block size for UL-SCH of the PUSCH
transmission;

-
M PUSCH
sc is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

- is the number of subcarriers in OFDM symbol l that carries PTRS, in the PUSCH transmission;

- is the number of resource elements that can be used for transmission of UCI in OFDM symbol l , for
l=0 , 1, 2, . .. , N PUSCH PUSCH
symb,all −1 , in the PUSCH transmission and N symb,all is the total number of OFDM symbols of the
PUSCH, including all OFDM symbols used for DMRS;

- for any OFDM symbol that carries DMRS of the PUSCH, ;

- for any OFDM symbol that does not carry DMRS of the PUSCH, ;

- is configured by higher layer parameter scaling;

- is the symbol index of the first OFDM symbol that does not carry DMRS of the PUSCH, after the first DMRS
symbol(s), in the PUSCH transmission.

For HARQ-ACK transmission on PUSCH not using repetition type B with UL-SCH, and if numberOfSlotsTBoMS is
present in the resource allocation table and the value of numberOfSlotsTBoMS in the row indicated by the Time domain
resource assignment field in DCI is larger than 1, the number of coded modulation symbols per layer for HARQ-ACK
'
transmission, denoted as Q ACK , is determined as follows:

{ }
PUSCH
N symb , all−1

( O ACK + L ACK ) ∙ β
PUSCH
offset ∙ ∑ UCI
M sc ( l ) PUSCH
N symb , all−1
Q
'
ACK =min ⌈ C UL −SCH−1
l=0
⌉,⌈α∙ ∑ UCI
M sc ( l ) ⌉
1
∑
l=l 0
Kr
Ns r=0

where

- N s is the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in
DCI;
PT −RS
- M sc ( l )is the number of subcarriers in OFDM symbol l that carries PTRS, in the PUSCH transmission of TB
processing over multiple slots in the slot with the HARQ-ACK transmission;
UCI
- M sc ( l ) is the number of resource elements that can be used for transmission of UCI in OFDM symbol l , for
PUSCH
l=0 , 1 , 2, … , N symb , all −1, in the PUSCH transmission of TB processing over multiple slots in the slot with
PUSCH
the HARQ-ACK transmission and N symb , allis the total number of OFDM symbols of the PUSCH in the slot,
including all OFDM symbols used for DMRS;

3GPP
Release 17 99 3GPP TS 38.212 V17.5.0 (2023-03)

- l 0is the symbol index of the first OFDM symbol that does not carry DMRS of the PUSCH, after the first DMRS
symbol(s), in the PUSCH transmission of TB processing over multiple slots in the slot with the HARQ-ACK
transmission;

- and all the other notations in the formula are defined the same as for PUSCH not using repetition type B and if
numberOfSlotsTBoMS is not present in the resource allocation table.

For HARQ-ACK transmission on an actual repetition of a PUSCH with repetition Type B with UL-SCH, the number of
'
coded modulation symbols per layer for HARQ-ACK transmission, denoted as Q ACK , is determined as follows:

{ }
PUSCH
N symb,nominal −1

( O ACK + L ACK ) ∙ β
PUSCH
offset ∙ ∑ UCI
M sc,nominal ( l ) N PUSCH
symb,nominal
−1 N PUSCH
symb,actual
−1

Q
'
ACK =min ⌈ C UL-SCH −1
l=0
⌉ ,⌈ α ∙ ∑ M
UCI
sc,nominal (l) ⌉ , ∑ UCI
M sc,actual ( l )
∑
l=0 l=0
Kr
r =0

where
UCI
- M sc,nominal ( l ) is the number of resource elements that can be used for transmission of UCI in OFDM symbol l ,
PUSCH
for l=0 , 1 , 2, ⋯ , N symb,nominal −1, in the PUSCH transmission assuming a nominal repetition without
PUSCH
segmentation, and N symb,nominal is the total number of OFDM symbols in a nominal repetition of the PUSCH,
including all OFDM symbols used for DMRS;

- for any OFDM symbol that carries DMRS of the PUSCH assuming a nominal repetition without
UCI
segmentation, M sc,nominal ( l )=0;

- for any OFDM symbol that does not carry DMRS of the PUSCH assuming a nominal repetition without
UCI PUSCH PT-RS PT-RS
segmentation, M sc,nominal ( l )=M sc −M sc,nominal ( l ) where M sc,nominal ( l ) is the number of subcarriers in
OFDM symbol l that carries PTRS, in the PUSCH transmission assuming a nominal repetition without
segmentation;
UCI
- M sc,actual ( l ) is the number of resource elements that can be used for transmission of UCI in OFDM symbol l , for
PUSCH PUSCH
l=0 , 1 , 2, ⋯ , N symb,actual−1, in the actual repetition of the PUSCH transmission, and N symb,actual is the total
number of OFDM symbols in the actual repetition of the PUSCH transmission, including all OFDM symbols
used for DMRS;

- for any OFDM symbol that carries DMRS of the actual repetition of the PUSCH transmission,
UCI
M sc,actual ( l )=0 ;
- for any OFDM symbol that does not carry DMRS of the actual repetition of the PUSCH transmission,
UCI PUSCH PT-RS PT-RS
M sc,actual ( l )=M sc −M sc,actual ( l ) where M sc,actual ( l ) is the number of subcarriers in OFDM symbol l
that carries PTRS, in the actual repetition of the PUSCH transmission;

- and all the other notations in the formula are defined the same as for PUSCH not using repetition type B and if
numberOfSlotsTBoMS is not present in the resource allocation table.

For HARQ-ACK transmission on PUSCH without UL-SCH, the number of coded modulation symbols per layer for
'
HARQ-ACK transmission, denoted as
Q ACK , is determined as follows:

3GPP
Release 17 100 3GPP TS 38.212 V17.5.0 (2023-03)

where

-
OACK is the number of HARQ-ACK bits;

- if , ; otherwise is the number of CRC bits for HARQ-ACK defined according to

Clause [Link].1;;

- ;

-
M PUSCH
sc is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

- is the number of subcarriers in OFDM symbol l that carries PTRS, in the PUSCH transmission;

- for any OFDM symbol that carries DMRS of the PUSCH, ;

- for any OFDM symbol that does not carry DMRS of the PUSCH, ;

- is the symbol index of the first OFDM symbol that does not carry DMRS of the PUSCH, after the first DMRS
symbol(s), in the PUSCH transmission;

- is the code rate of the PUSCH, determined according to Clause [Link] of [6, TS38.214];

-
Qm is the modulation order of the PUSCH;

- is configured by higher layer parameter scaling.

d ,d , d , d ,. .. , d r( N −1 )
The input bit sequence to rate matching is r 0 r 1 r 2 r 3 r where r is the code block number, and N r is the
number of coded bits in code block number r .

Rate matching is performed according to Clause 5.4.1 by setting I BIL=1 and the rate matching output sequence length
to r ⌊ UCI UCI ⌋ , where
E = E /C

-
C UCI is the number of code blocks for UCI determined according to Clause 5.2.1;

- N L is the number of transmission layers of the PUSCH;

-
Qm is the modulation order of the PUSCH;

-
E UCI =N L⋅Q ' ACK⋅Qm .

f r 0 , f r1 , f r 2 , .. . , f r ( E −1)
The output bit sequence after rate matching is denoted as r where Er is the length of rate matching
output sequence in code block number r .

3GPP
Release 17 101 3GPP TS 38.212 V17.5.0 (2023-03)

[Link].1.2 CSI part 1

For CSI part 1 transmission on PUSCH not using repetition type B with UL-SCH and if numberOfSlotsTBoMS is not
present in the resource allocation table, or if numberOfSlotsTBoMS is present in the resource allocation table and the
value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI is equal to 1,
'
the number of coded modulation symbols per layer for CSI part 1 transmission, denoted as
QCSI-part1 , is determined as
follows:

{ }
PUSCH
N symb ,all−1

( OCSI −1+ LCSI −1 ) ∙ β

PUSCH
offset ∙ ∑ UCI
M sc ( l ) N PUSCH
symb ,all
−1

Q
'
CSI −1 =min ⌈ C UL −SCH−1
l=0
⌉ ,⌈ α ∙ ∑ UCI '
M sc ( l ) ⌉ −Q ACK /CG−UCI
∑
l=0
Kr
r=0

where

- is the number of bits for CSI part 1;

- if , ; otherwise is the number of CRC bits for CSI part 1 determined according to
Clause [Link].1;

-
β PUSCH CSI-part1
offset =β offset ;

-
M PUSCH
sc is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

- is the number of subcarriers in OFDM symbol l that carries PTRS, in the PUSCH transmission;
' '
- Q ACK / CG−UCI =Q ACK if HARQ-ACK is present for transmission on the same PUSCH with UL-SCH and
'
without CG-UCI, where Q ACK is the number of coded modulation symbols per layer for HARQ-ACK
transmitted on the PUSCH as defined in clause [Link].1.1 if number of HARQ-ACK information bits is more

than 2, and if the number of HARQ-ACK information bits is no more than 2 bits,

where is the number of reserved resource elements for potential HARQ-ACK transmission in
PUSCH
OFDM symbol l , for l=0 , 1 , 2, . .. , N symb,all −1 , in the PUSCH transmission, defined in Clause 6.2.7; or
' '
- Q ACK / CG−UCI =Q ACK if both HARQ-ACK and CG-UCI are present on the same PUSCH with UL-SCH, where
'
Q ACK is the number of coded modulation symbols per layer for HARQ-ACK and CG-UCI transmitted on the
PUSCH as defined in clause [Link].1.5; or
' '
- Q ACK / CG−UCI =QCG−UCI if CG-UCI is present on the same PUSCH with UL-SCH and without HARQ-ACK,
'
where Q CG−UCI is the number of coded modulation symbols per layer for CG-UCI transmitted on the PUSCH as
defined in clause [Link].1.4;

3GPP
Release 17 102 3GPP TS 38.212 V17.5.0 (2023-03)

- is the number of resource elements that can be used for transmission of UCI in OFDM symbol l , for
l=0 , 1 , 2, . .. , N PUSCH PUSCH
symb,all −1 , in the PUSCH transmission and N symb,all is the total number of OFDM symbols of the
PUSCH, including all OFDM symbols used for DMRS;

- for any OFDM symbol that carries DMRS of the PUSCH, ;

- for any OFDM symbol that does not carry DMRS of the PUSCH, ;

- is configured by higher layer parameter scaling.

For CSI part 1 transmission on PUSCH not using repetition type B with UL-SCH, and if numberOfSlotsTBoMS is
present in the resource allocation table and the value of numberOfSlotsTBoMS in the row indicated by the Time domain
resource assignment field in DCI is larger than 1, the number of coded modulation symbols per layer for CSI part 1
'
transmission, denoted as Q CSI −part 1, is determined as follows:

{ }
PUSCH
N symb , all−1

( OCSI −1+ LCSI −1 ) ∙ β

PUSCH
offset ∙ ∑ UCI
M sc ( l ) PUSCH
N symb , all−1
Q
'
CSI −1 =min ⌈ CUL −SCH−1
l=0
⌉ ,⌈ α ∙ ∑ UCI '
M sc ( l ) ⌉ −Q ACK /CG−UCI
1
∑
l=0
Kr
Ns r=0

where

- N s is the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in
DCI;
PT −RC
- M sc (l ) is the number of subcarriers in OFDM symbol l that carries PTRS, in the PUSCH transmission of
TB processing over multiple slots in the slot with the CSI part 1 transmission;
UCI
- M sc ( l )is the number of resource elements that can be used for transmission of UCI in OFDM symbol l , for
PUSCH
l=0 , 1 , 2, … , N symb , all −1, in the PUSCH transmission of TB processing over multiple slots in the slot with
PUSCH
the CSI part 1 transmission and N symb , allis the total number of OFDM symbols of the PUSCH in the slot,
including all OFDM symbols used for DMRS;

- and all the other notations in the formula are defined the same as for PUSCH not using repetition type B and if
numberOfSlotsTBoMS is not present in the resource allocation table.

For CSI part 1 transmission on an actual repetition of a PUSCH with repetition Type B with UL-SCH, the number of
'
coded modulation symbols per layer for CSI part 1 transmission, denoted as Q CSI- part 1, is determined as follows:

{
PUSCH
N symb,nominal −1

( OCSI-1 + LCSI-1 ) ∙ β
PUSCH
offset ∙ ∑ UCI
M sc,nominal ( l ) N PUSCH
symb,nominal
−1 N PUSCH
symb,actual
−1

Q
'
CSI-1 =min ⌈ C UL-SCH −1
l=0
⌉ ,⌈ α ∙ ∑ M
UCI
sc,nominal (l ) ⌉−Q '
ACK /CG−UCI , ∑ UC
M sc,
∑
l=0 l=0
Kr
r =0

3GPP
Release 17 103 3GPP TS 38.212 V17.5.0 (2023-03)

PUSCH
segmentation, and N symb,nominal is the total number of OFDM symbols in a nominal repetition of the PUSCH,
including all OFDM symbols used for DMRS;

- for any OFDM symbol that carries DMRS of the PUSCH assuming a nominal repetition without
UCI
segmentation, M sc,nominal ( l )=0;

- and all the other notations in the formula are defined the same as for PUSCH not using repetition type B and if
numberOfSlotsTBoMS is not present in the resource allocation table.

For CSI part 1 transmission on PUSCH without UL-SCH, the number of coded modulation symbols per layer for CSI
'
part 1 transmission, denoted as
QCSI-part1 , is determined as follows:
if there is CSI part 2 to be transmitted on the PUSCH,

else

end if

where

- is the number of bits for CSI part 1;

- if , ; otherwise is the number of CRC bits for CSI part 1 determined according to
Clause [Link].1;

-
β PUSCH CSI-part1
offset =β offset ;

-
M PUSCH
sc is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

3GPP
Release 17 104 3GPP TS 38.212 V17.5.0 (2023-03)

- is the number of subcarriers in OFDM symbol l that carries PTRS, in the PUSCH transmission;

-
Q ' ACK is the number of coded modulation symbols per layer for HARQ-ACK transmitted on the PUSCH if

number of HARQ-ACK information bits is more than 2, and if the number of

HARQ-ACK information bits is no more than 2 bits, where is the number of reserved resource
PUSCH
elements for potential HARQ-ACK transmission in OFDM symbol l , for l=0 , 1 , 2, . .. , N symb,all −1 , in the
PUSCH transmission, defined in Clause 6.2.7;

- is the number of resource elements that can be used for transmission of UCI in OFDM symbol l , for
l=0 , 1 , 2, . .. , N PUSCH PUSCH
symb,all −1 , in the PUSCH transmission and N symb,all is the total number of OFDM symbols of the
PUSCH, including all OFDM symbols used for DMRS;

- for any OFDM symbol that carries DMRS of the PUSCH, ;

- for any OFDM symbol that does not carry DMRS of the PUSCH, ;

- is the code rate of the PUSCH, determined according to Clause [Link] of [6, TS38.214];

-
Qm is the modulation order of the PUSCH.

d ,d , d , d ,. .. , d r( N −1 )
The input bit sequence to rate matching is r 0 r 1 r 2 r 3 r where r is the code block number, and N r is the
number of coded bits in code block number . r

Rate matching is performed according to Clause 5.4.1 by setting I BIL=1 and the rate matching output sequence length
to r ⌊ UCI UCI ⌋ , where
E = E /C

-
C UCI is the number of code blocks for UCI determined according to Clause 5.2.1;

- N L is the number of transmission layers of the PUSCH;

-
Qm is the modulation order of the PUSCH;

-
E UCI=N L⋅Q ' CSI,1⋅Q m .

f r 0 , f r1 , f r 2 , .. . , f r ( E −1)
The output bit sequence after rate matching is denoted as r where Er is the length of rate matching
output sequence in code block number r .

[Link].1.3 CSI part 2

For CSI part 2 transmission on PUSCH not using repetition type B with UL-SCH and if numberOfSlotsTBoMS is not
present in the resource allocation table, or if numberOfSlotsTBoMS is present in the resource allocation table and the
value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI is equal to 1,
'
the number of coded modulation symbols per layer for CSI part 2 transmission, denoted as
QCSI-part2 , is determined as
follows:

3GPP
Release 17 105 3GPP TS 38.212 V17.5.0 (2023-03)

{ }
PUSCH
N symb ,all−1

( O CSI−2+ LCSI −2 ) ∙ β
PUSCH
offset ∙ ∑ UCI
M sc ( l ) N PUSCH
symb ,all
−1

Q
'
CSI −2 =min ⌈ CUL −SCH−1
l=0
⌉ ,⌈ α ∙ ∑ UCI ' '
M sc ( l ) ⌉ −Q ACK / CG−UCI −QCSI−1
∑
l=0
Kr
r=0

where

- is the number of bits for CSI part 2;

- if , ; otherwise is the number of CRC bits for CSI part 2 determined according to
Clause [Link].1;

-
β PUSCH CSI-part2
offset =β offset ;

-
M PUSCH
sc is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

than 2, and
Q ' ACK=0 if the number of HARQ-ACK information bits is 1 or 2 bits; or
' '
- Q ACK / CG−UCI =Q ACK if both HARQ-ACK and CG-UCI are present on the same PUSCH with UL-SCH, where
'
Q ACK is the number of coded modulation symbols per layer for HARQ-ACK and CG-UCI transmitted on the
PUSCH as defined in clause [Link].1.5; or
' '
- Q ACK / CG−UCI =QCG−UCI if CG-UCI is present on the same PUSCH with UL-SCH and without HARQ-ACK,
'
where Q CG−UCI is the number of coded modulation symbols per layer for CG-UCI transmitted on the PUSCH as
defined in clause [Link].1.4;

- is the number of coded modulation symbols per layer for CSI part 1 transmitted on the PUSCH;

- is the number of resource elements that can be used for transmission of UCI in OFDM symbol l , for
l=0 , 1 , 2, . .. , N PUSCH PUSCH
symb,all −1 , in the PUSCH transmission and N symb,all is the total number of OFDM symbols of the
PUSCH, including all OFDM symbols used for DMRS;

- for any OFDM symbol that carries DMRS of the PUSCH, ;

- for any OFDM symbol that does not carry DMRS of the PUSCH, .

- is configured by higher layer parameter scaling.

3GPP
Release 17 106 3GPP TS 38.212 V17.5.0 (2023-03)

For CSI part 2 transmission on PUSCH not using repetition type B with UL-SCH, and if numberOfSlotsTBoMS is
present in the resource allocation table and the value of numberOfSlotsTBoMS in the row indicated by the Time domain
resource assignment field in DCI is larger than 1, the number of coded modulation symbols per layer for CSI part 2
'
transmission, denoted as Q CSI −part 2, is determined as follows:

{ }
PUSCH
N symb ,all−1

( O CSI−2+ LCSI −2 ) ∙ β
PUSCH
offset ∙ ∑ UCI
M sc ( l ) PUSCH
N symb ,all−1
Q
'
CSI −2 =min ⌈ C UL−SCH−1
l=0
⌉ ,⌈ α ∙ ∑ UCI '
M sc ( l ) ⌉ −Q ACK / CG−UCI −QCSI−1
'

1
∑
l=0
Kr
Ns r=0

where

- N s is the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in
DCI;
PT −RS
- M sc ( l )is the number of subcarriers in OFDM symbol l that carries PTRS, in the PUSCH transmission of TB
processing over multiple slots in the slot with the CSI part 2 transmission;
UCI
- M sc ( l )is the number of resource elements that can be used for transmission of UCI in OFDM symbol l , for
PUSCH
l=0 , 1 , 2, … , N symb , all −1, in the PUSCH transmission of TB processing over multiple slots in the slot with
PUSCH
the CSI part 2 transmission and N symb , allis the total number of OFDM symbols of the PUSCH in the slot,
including all OFDM symbols used for DMRS;

- and all the other notations in the formula are defined the same as for PUSCH not using repetition type B and if
numberOfSlotsTBoMS is not present in the resource allocation table.

For CSI part 2 transmission on an actual repetition of a PUSCH with repetition Type B with UL-SCH, the number of
'
coded modulation symbols per layer for CSI part 2 transmission, denoted as Q CSI- part 2, is determined as follows:

{
PUSCH
N symb,nominal −1

( OCSI-2 + LCSI-2 ) ∙ β
PUSCH
offset ∙ ∑ UCI
M sc,nominal ( l ) N PUSCH
symb,nominal
−1 N PUSCH
symb,act

Q
'
CSI-2 =min ⌈ C UL-SCH −1
l=0
⌉ ,⌈ α ∙ ∑ M
UCI
sc,nominal (l ) ⌉−Q '
ACK /CG−UCI −Q
'
CSI-1 , ∑
∑
l=0 l=0
Kr
r =0

- for any OFDM symbol that carries DMRS of the PUSCH assuming a nominal repetition without
UCI
segmentation, M sc,nominal ( l )=0;

3GPP
Release 17 107 3GPP TS 38.212 V17.5.0 (2023-03)

number of OFDM symbols in the actual repetition of the PUSCH transmission, including all OFDM symbols
used for DMRS;

- and all the other notations in the formula are defined the same as for PUSCH not using repetition type B and if
numberOfSlotsTBoMS is not present in the resource allocation table.

For CSI part 2 transmission on PUSCH without UL-SCH, the number of coded modulation symbols per layer for CSI
'
part 2 transmission, denoted as
QCSI-part2 , is determined as follows:

where

-
M PUSCH
sc is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

- is the number of subcarriers in OFDM symbol l that carries PTRS, in the PUSCH transmission;

-
Q ' ACK is the number of coded modulation symbols per layer for HARQ-ACK transmitted on the PUSCH if
number of HARQ-ACK information bits is more than 2, and
Q ' ACK=0 if the number of HARQ-ACK
information bits is 1 or 2 bits;

- is the number of coded modulation symbols per layer for CSI part 1 transmitted on the PUSCH;

- is the number of resource elements that can be used for transmission of UCI in OFDM symbol l , for
l=0 , 1 , 2, . .. , N PUSCH PUSCH
symb,all −1 , in the PUSCH transmission and N symb,all is the total number of OFDM symbols of the
PUSCH, including all OFDM symbols used for DMRS;

- for any OFDM symbol that carries DMRS of the PUSCH, ;

- for any OFDM symbol that does not carry DMRS of the PUSCH, .

d ,d , d , d ,. .. , d r( N −1 )
The input bit sequence to rate matching is r 0 r 1 r 2 r 3 r where r is the code block number, and N r is the
number of coded bits in code block number . r

Rate matching is performed according to Clause 5.4.1 by setting I BIL=1 and the rate matching output sequence length
to r ⌊ UCI UCI ⌋ , where
E = E /C

-
C UCI is the number of code blocks for UCI determined according to Clause 5.2.1;

- N L is the number of transmission layers of the PUSCH;

3GPP
Release 17 108 3GPP TS 38.212 V17.5.0 (2023-03)

-
Qm is the modulation order of the PUSCH;

-
E UCI=N L⋅Q ' CSI,2⋅Q m .

f r 0 , f r1 , f r 2 , .. . , f r ( E −1)
The output bit sequence after rate matching is denoted as r where Er is the length of rate matching
output sequence in code block number r .

[Link].1.4 CG-UCI

For CG-UCI transmission on PUSCH with UL-SCH and if numberOfSlotsTBoMS is not present in the resource
allocation table, or if numberOfSlotsTBoMS is present in the resource allocation table and the value of
numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI is equal to 1, the
'
number of coded modulation symbols per layer for CG-UCI transmission, denoted as Q CG−UCI , is determined as
follows:

{ }
PUSCH
N symb,all −1

( OCG−UCI + LCG−UCI ) ∙ β
PUSCH
offset ∙ ∑ UCI
M sc (l ) N PUSCH
symb,all
−1

Q
'
CG−UCI =min ⌈ C UL −SCH −1
l=0
⌉, ⌈ α ∙ ∑ UCI
M sc (l ) ⌉
∑
l=l 0
Kr
r =0

where

- OCG−UCI is the number of CG-UCI bits;

- LCG−UCI is the number of CRC bits for CG-UCI determined according to Clause [Link].1;
PUSCH CG−UCI
- β offset =β offset ;

- C UL−SCH is the number of code blocks for UL-SCH of the PUSCH transmission;

- K r is the r-th code block size for UL-SCH of the PUSCH transmission;
PUSCH
- M sc is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

PT −RS
- M sc ( l ) is the number of subcarriers in OFDM symbol l that carries PTRS, in the PUSCH transmission;
UCI
- M sc ( l ) is the number of resource elements that can be used for transmission of UCI in OFDM symbol l, for l
PUSCH PUSCH
=0,1,2,…, N symb , all −1, in the PUSCH transmission and N symb , all is the total number of OFDM symbols of the
PUSCH, including all OFDM symbols used for DMRS;
UCI
- for any OFDM symbol that carries DMRS of the PUSCH, M sc ( l )=0 ;
UCI
- for any OFDM symbol that does not carry DMRS of the PUSCH, M sc ( l )=M PUSCH
sc
PT− RS
− M sc ( l );
- α is configured by higher layer parameter scaling;
- l 0 is the symbol index of the first OFDM symbol that does not carry DMRS of the PUSCH, after the first DMRS
symbol(s), in the PUSCH transmission.

For CG-UCI transmission on PUSCH with UL-SCH, and if numberOfSlotsTBoMS is present in the resource allocation
table and the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI
'
is larger than 1, the number of coded modulation symbols per layer for CG-UCI transmission, denoted as Q CG−UCI , is
determined as follows:

3GPP
Release 17 109 3GPP TS 38.212 V17.5.0 (2023-03)

{ }
PUSCH
N symb, all −1

( OCG−UCI + LCG−UCI ) ∙ β
PUSCH
offset ∙ ∑ UCI
M sc (l ) PUSCH
N symb, all −1
Q
'
CG−UCI =min ⌈ C UL −SCH−1
l=0
⌉, ⌈ α ∙ ∑ UCI
M sc (l ) ⌉
1
∑
l=l 0
Kr
Ns r =0

where

- N s is the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in
DCI;
PT −RS
- M sc ( l )is the number of subcarriers in OFDM symboll that carries PTRS, in the PUSCH transmission of TB
processing over multiple slots in the slot with the CG-UCI transmission;
UCI
- M sc ( l )is the number of resource elements that can be used for transmission of UCI in OFDM symbol l , for
PUSCH
l=0 , 1 , 2, … , N symb , all −1, in the PUSCH transmission of TB processing over multiple slots in the slot with
PUSCH
the CG-UCI transmission and N symb , all is the total number of OFDM symbols of the PUSCH in the slot,
including all OFDM symbols used for DMRS;

- and all the other notations in the formula are defined the same as for PUSCH with UL-SCH and if
numberOfSlotsTBoMS is not present in the resource allocation table.

The input bit sequence to rate matching is d r 0 , d r 1 , d r 2 , d r 3 ,… , d r ( N r −1 ) where r is the code block number, and N r is
the number of coded bits in code block number r.

Rate matching is performed according to Clause 5.4.1 by setting I BIL =1 and the rate matching output sequence length
to Er =⌊ EUCI /C UCI ⌋ , where

- C UCI is the number of code blocks for UCI determined according to Clause 5.2.1;

- N L is the number of transmission layers of the PUSCH;

- Qm is the modulation order of the PUSCH;

'
- EUCI =N L ∙QCG−UCI ∙ Qm.

The output bit sequence after rate matching is denoted as f r 0 , f r 1 , f r 2 , … , f r ( Er −1) where Er is the length of rate
matching output sequence in code block number r.

[Link].1.5 HARQ-ACK and CG-UCI

For HARQ-ACK and CG-UCI transmission on PUSCH with UL-SCH and if numberOfSlotsTBoMS is not present in the
resource allocation table, or if numberOfSlotsTBoMS is present in the resource allocation table and the value of
numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in DCI is equal to 1, the
'
number of coded modulation symbols per layer for HARQ-ACK and CG-UCI transmission, denoted as Q ACK , is
determined as follows:

3GPP
Release 17 110 3GPP TS 38.212 V17.5.0 (2023-03)

{ }
PUSCH
N symb ,all−1

( O ACK +OCG−UCI + L ACK ) ∙ β

PUSCH
offset ∙ ∑ UCI
M sc ( l ) N PUSCH
symb ,all
−1

Q
'
ACK =min ⌈ C UL −SCH−1
l=0
⌉ ,⌈ α ∙ ∑ UCI
M sc ( l ) ⌉
∑
l=l 0
Kr
r =0

where

- O ACK is the number of HARQ-ACK bits;

- OCG−UCI is the number of CG-UCI bits;

- if O ACK +O CG−UCI >360 , L ACK =11; otherwise L ACK is the number of CRC bits for HARQ-ACK and CG-
UCI determined according to Clause [Link].1;
PUSCH HARQ− ACK
- β offset =β offset ;

- C UL−SCH is the number of code blocks for UL-SCH of the PUSCH transmission;

- K r is the r-th code block size for UL-SCH of the PUSCH transmission;
PUSCH
- M sc is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

For HARQ-ACK and CG-UCI transmission on PUSCH with UL-SCH, and if numberOfSlotsTBoMS is present in the
resource allocation table and the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource
assignment field in DCI is larger than 1, the number of coded modulation symbols per layer for HARQ-ACK and CG-
'
UCI transmission, denoted as Q ACK , is determined as follows:

{ }
PUSCH
N symb , all−1

( O ACK +OCG−UCI + L ACK ) ∙ β

PUSCH
offset ∙ ∑ UCI
M sc ( l ) PUSCH
N symb , all−1
Q
'
ACK =min ⌈ C UL −SCH−1
l=0
⌉ ,⌈ α ∙ ∑ UCI
M sc ( l ) ⌉
1
∑
l=l 0
Kr
Ns r =0

where

- N s is the value of numberOfSlotsTBoMS in the row indicated by the Time domain resource assignment field in
DCI;

3GPP
Release 17 111 3GPP TS 38.212 V17.5.0 (2023-03)

PT −RS
- M sc ( l )is the number of subcarriers in OFDM symbol l that carries PTRS, in the PUSCH transmission of TB
processing over multiple slots in the slot with the HARQ-ACK and CG-UCI transmission;
UCI
- M sc ( l )is the number of resource elements that can be used for transmission of UCI in OFDM symbol l , for
PUSCH
l=0 , 1 , 2, … , N symb , all −1, in the PUSCH transmission of TB processing over multiple slots in the slot with
PUSCH
the HARQ-ACK and CG-UCI transmission and N symb , all is the total number of OFDM symbols of the PUSCH
in the slot, including all OFDM symbols used for DMRS;

- and all the other notations in the formula are defined the same as for PUSCH with UL-SCH and if
numberOfSlotsTBoMS is not present in the resource allocation table.

The input bit sequence to rate matching is d r 0 , d r 1 , d r 2 , d r 3 ,… , d r ( N r −1 ) where r is the code block number, and N r is
the number of coded bits in code block number r.

Rate matching is performed according to Clause 5.4.1 by setting I BIL =1 and the rate matching output sequence length
to Er =⌊ EUCI /C UCI ⌋ , where

- C UCI is the number of code blocks for UCI determined according to Clause 5.2.1;

- N L is the number of transmission layers of the PUSCH;

- Qm is the modulation order of the PUSCH;

'
- EUCI =N L ∙Q ACK ∙ Qm.

The output bit sequence after rate matching is denoted as f r 0 , f r 1 , f r 2 , … , f r ( Er −1) where Er is the length of rate
matching output sequence in code block number r.

[Link].1.6 UCI with different priority indexes

HARQ− ACK −LP HARQ− ACK ,0
In this clause, β offset is equal to β offset defined in [5, TS38.213] in case of PUSCH associated with
HARQ− ACK
priority index 1, and equal β
to offset defined in [5, TS38.213] in case of PUSCH associated with priority index 0.
HARQ− ACK −HP HARQ− ACK ,1
β offset is equal to β offset defined in [5, TS38.213] in case of PUSCH associated with priority index 0,
HARQ− ACK
β
and equal to offset defined in [5, TS38.213] in case of PUSCH associated with priority index 1.

If uci-MuxWithDiffPrio is configured, and HARQ-ACK bits associated with priority index 0, and CSI part 1 if any are
transmitted on a PUSCH associated with priority index 1:

- If CSI part 1 is also transmitted on the PUSCH,

- Perform rate matching for CSI part 1 according to clause [Link].1.2, by assuming the number of HARQ-
ACK information bits to be transmitted on PUSCH in clause [Link].1.2 is 0 bit.

- Perform rate matching for HARQ-ACK with priority index 0 according to clause [Link].1.3, by taking
PUSCH HARQ− ACK −LP
HARQ-ACK with priority index 0 as CSI part 2 and replacing β offset by β offset , and assuming the
number of HARQ-ACK information bits to be transmitted on PUSCH in clause [Link].1.3 is 0 bit.

- Otherwise, perform rate matching for HARQ-ACK with priority index 0 according to clause [Link].1.2, by
PUSCH HARQ− ACK −LP
taking HARQ-ACK with priority index 0 as CSI-part 1 and replacing β offset by β offset , and assuming
the number of HARQ-ACK information bits to be transmitted on PUSCH in clause [Link].1.2 is 0 bit.

3GPP
Release 17 112 3GPP TS 38.212 V17.5.0 (2023-03)

If uci-MuxWithDiffPrio is configured, and HARQ-ACK bits associated with priority index 1, and CSI if any are
transmitted on a PUSCH associated with priority index 0:

- Perform rate matching for CSI part 1 according to clause [Link].1.2, by taking HARQ-ACK with priority index
1 as HARQ-ACK, if CSI part 1 is also transmitted on the PUSCH.

- Perform rate matching for CSI part 2 according to clause [Link].1.3, by taking HARQ-ACK with priority index
1 as HARQ-ACK, if CSI part 2 is also transmitted on the PUSCH.

- Perform rate matching for HARQ-ACK with priority index 1 according to clause [Link].1.1, by taking HARQ-
PUSCH HARQ− ACK −HP
ACK with priority index 1 as HARQ-ACK and replacing β offset by β offset , if HARQ-ACK bits
associated with priority index 1 are transmitted without CG-UCI associated with priority index 1.

- Perform rate matching for CG-UCI with priority index 1 according to clause [Link].1.4, if CG-UCI associated
with priority index 1 is transmitted without HARQ-ACK bits associated with priority index 1.

- Perform rate matching for CG-UCI with priority index 1 and HARQ-ACK with priority index 1 according to
clause [Link].1.5, if both CG-UCI associated with priority index 1 and HARQ-ACK bits associated with priority
PUSCH
index 1 are transmitted, by taking HARQ-ACK with priority index 1 as HARQ-ACK and replacing β offset by
HARQ− ACK −HP
β offset .

- If CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 1,

- Perform rate matching for CSI part 1 according to clause [Link].1.2, by taking HARQ-ACK with priority
index 1 if any as HARQ-ACK, and taking CG-UCI associated with priority index 1 if any as CG-UCI.

- Perform rate matching for HARQ-ACK with priority index 0 according to clause [Link].1.3, by taking
PUSCH HARQ− ACK −LP
HARQ-ACK with priority index 0 as CSI part 2 and replacing β offset by β offset , and taking
HARQ-ACK with priority index 1 if any as HARQ-ACK, and taking CG-UCI associated with priority index
1 if any as CG-UCI.

- Otherwise,

- Perform rate matching for HARQ-ACK with priority index 0 according to clause [Link].1.2, by taking
PUSCH HARQ− ACK −LP
HARQ-ACK with priority index 0 as CSI-part 1 and replacing β offset by β offset , and taking
HARQ-ACK with priority index 1 if any as HARQ-ACK, and taking CG-UCI associated with priority index
1 if any as CG-UCI.

- Perform rate matching for CSI part 1 according to clause [Link].1.3, by taking CSI part 1 as CSI part 2 and
PUSCH CSI− part 1
replacing β offset by β offset , taking HARQ-ACK with priority index 0 as CSI-part 1 and taking HARQ-
ACK with priority index 1 as HARQ-ACK, if CSI part 1 is also transmitted on the PUSCH and the PUSCH
is associated with priority index 0.

- Perform rate matching for CG-UCI associated with priority index 0 according to clause [Link].1.2, if CG-UCI
associated with priority index 0 is transmitted without HARQ-ACK bits associated with priority index 0, by
PUSCH CG−UCI
taking CG-UCI associated with priority index 0 as CSI-part 1 and replacing β offset by β offset , and taking
HARQ-ACK with priority index 1 as HARQ-ACK.

3GPP
Release 17 113 3GPP TS 38.212 V17.5.0 (2023-03)

- Perform rate matching for CG-UCI associated with priority index 0 and HARQ-ACK bits associated with
priority index 0 according to clause [Link].1.2, if both CG-UCI associated with priority index 0 and HARQ-
ACK bits associated with priority index 0 are transmitted, by taking CG-UCI associated with priority index 0
PUSCH HARQ− ACK −L P
and HARQ-ACK bits associated with priority index 0 as CSI-part 1 and replacing β offset by β offset ,
and taking HARQ-ACK with priority index 1 as HARQ-ACK.

- Perform rate matching for CSI part 1 according to clause [Link].1.3, by taking CSI part 1 as CSI part 2 and
PUSCH CSI− part 1
replacing β offset by β offset , taking CG-UCI associated with priority index 0 and HARQ-ACK bits
associated with priority index 0 if any as CSI-part 1 and taking HARQ-ACK with priority index 1 as HARQ-
ACK, if CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 0.

[Link].2 UCI encoded by channel coding of small block lengths

[Link].2.1 HARQ-ACK

For HARQ-ACK transmission on PUSCH, the number of coded modulation symbols per layer for HARQ-ACK
'
transmission, denoted as
Q ACK , is determined according to Clause [Link].1.1, by setting the number of CRC bits
L=0 .

The input bit sequence to rate matching is d 0 ,d1 ,d 2 ,...,d N−1 .

Rate matching is performed according to Clause 5.4.3, by setting the rate matching output sequence length
E=N L⋅Q' ACK⋅Q m , where

- N L is the number of transmission layers of the PUSCH;

-
Qm is the modulation order of the PUSCH.

The output bit sequence after rate matching is denoted as f 0 , f 1 , f 2 , .. . , f E−1 .

[Link].2.2 CSI part 1

For CSI part 1 transmission on PUSCH, the number of coded modulation symbols per layer for CSI part 1 transmission,
'
denoted as
QCSI,1 , is determined according to Clause [Link].1.2, by setting the number of CRC bits L=0 .
Rate matching is performed according to Clause 5.4.3, by setting the rate matching output sequence length
E=N L⋅Q' CSI,1⋅Qm , where

- N L is the number of transmission layers of the PUSCH;

-
Qm is the modulation order of the PUSCH.

The output bit sequence after rate matching is denoted as f 0 , f 1 , f 2 , .. . , f E−1 .

[Link].2.3 CSI part 2

For CSI part 2 transmission on PUSCH, the number of coded modulation symbols per layer for CSI part 2 transmission,
'
denoted as
QCSI,2 , is determined according to Clause [Link].1.3, by setting the number of CRC bits L=0 .
Rate matching is performed according to Clause 5.4.3, by setting the rate matching output sequence length
E=N L⋅Q' CSI,2⋅Qm , where

- N L is the number of transmission layers of the PUSCH;

-
Qm is the modulation order of the PUSCH.

3GPP
Release 17 114 3GPP TS 38.212 V17.5.0 (2023-03)

The output bit sequence after rate matching is denoted as f 0 , f 1 , f 2 , .. . , f E−1 .

[Link].2.4 CG-UCI

For CG-UCI transmission on PUSCH, the number of coded modulation symbols per layer for CG-UCI transmission,
denoted as Q CG−UCI , is determined according to Clause [Link].1.4, by setting the number of CRC bits LCG−UCI =0 .
'

The input bit sequence to rate matching is d 0 , d 1 , d 2 , … , d N −1.

Rate matching is performed according to Clause 5.4.3, by setting the rate matching output sequence length
'
E=N L ∙ QCG−UCI ∙Qm , where

- N L is the number of transmission layers of the PUSCH;

- Qm is the modulation order of the PUSCH.

The output bit sequence after rate matching is denoted as f 0 , f 1 , f 2 ,… , f E −1.

[Link].2.5 HARQ-ACK and CG-UCI

For HARQ-ACK and CG-UCI transmission on PUSCH, the number of coded modulation symbols per layer for HARQ-
'
ACK and CG-UCI transmission, denoted as Q ACK , is determined according to Clause [Link].1.5, by setting the number
of CRC bits L ACK =0.

The input bit sequence to rate matching is d 0 , d 1 , d 2 , … , d N −1.

Rate matching is performed according to Clause 5.4.3, by setting the rate matching output sequence length
'
E=N L ∙ Q ACK ∙ Qm, where

- N L is the number of transmission layers of the PUSCH;

- Qm is the modulation order of the PUSCH.

The output bit sequence after rate matching is denoted as f 0 , f 1 , f 2 ,… , f E −1.

[Link].2.6 UCI with different priority indexes

HARQ− ACK −LP HARQ− ACK ,0
In this clause, β offset is equal to β offset defined in [5, TS38.213] in case of PUSCH associated with
HARQ− ACK
priority index 1, and equal β
to offset defined in [5, TS38.213] in case of PUSCH associated with priority index 0.
HARQ− ACK −HP HARQ− ACK ,1
β offset is equal to βoffset defined in [5, TS38.213] in case of PUSCH associated with priority index 0,
HARQ− ACK
β
and equal to offset defined in [5, TS38.213] in case of PUSCH associated with priority index 1.

If uci-MuxWithDiffPrio is configured, and HARQ-ACK bits associated with priority index 0, and CSI part 1 if any are
transmitted on a PUSCH associated with priority index 1:

- If CSI part 1 is also transmitted on the PUSCH,

- Perform rate matching for CSI part 1 according to clause [Link].2.2, by assuming the number of HARQ-
ACK information bits to be transmitted on PUSCH in clause [Link].2.2 is 0 bit.

- Perform rate matching for HARQ-ACK with priority index 0 according to clause [Link].2.3, by taking
PUSCH HARQ− ACK −LP
HARQ-ACK with priority index 0 as CSI part 2 and replacing β offset by β offset , and assuming the
number of HARQ-ACK information bits to be transmitted on PUSCH in clause [Link].2.3 is 0 bit.

- Otherwise, perform rate matching for HARQ-ACK with priority index 0 according to clause [Link].2.2, by
PUSCH HARQ− ACK −LP
taking HARQ-ACK with priority index 0 as CSI-part 1 and replacing β offset by β offset , and assuming
the number of HARQ-ACK information bits to be transmitted on PUSCH in clause [Link].2.2 is 0 bit.

3GPP
Release 17 115 3GPP TS 38.212 V17.5.0 (2023-03)

If uci-MuxWithDiffPrio is configured, and HARQ-ACK bits associated with priority index 1, and CSI if any are
transmitted on a PUSCH associated with priority index 0:

- Perform rate matching for CSI part 1 according to clause [Link].2.2, by taking HARQ-ACK with priority index
1 as HARQ-ACK, if CSI part 1 is also transmitted on the PUSCH.

- Perform rate matching for CSI part 2 according to clause [Link].2.3, by taking HARQ-ACK with priority index
1 as HARQ-ACK, if CSI part 2 is also transmitted on the PUSCH.

- Perform rate matching for HARQ-ACK with priority index 1 according to clause [Link].2.1, by taking HARQ-
PUSCH HARQ− ACK −HP
ACK with priority index 1 as HARQ-ACK and replacing β offset by β offset , if HARQ-ACK bits
associated with priority index 1 are transmitted without CG-UCI associated with priority index 1.

- Perform rate matching for CG-UCI with priority index 1 according to clause [Link].2.4, if CG-UCI associated
with priority index 1 is transmitted without HARQ-ACK bits associated with priority index 1.

- Perform rate matching for CG-UCI with priority index 1 and HARQ-ACK with priority index 1 according to
clause [Link].2.5, if both CG-UCI associated with priority index 1 and HARQ-ACK bits associated with priority
PUSCH
index 1 are transmitted, by taking HARQ-ACK with priority index 1 as HARQ-ACK and replacing β offset by
HARQ− ACK −HP
β offset .

- If CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 1,

- Perform rate matching for CSI part 1 according to clause [Link].2.2, by taking HARQ-ACK with priority
index 1 if any as HARQ-ACK, and taking CG-UCI associated with priority index 1 if any as CG-UCI.

- Perform rate matching for HARQ-ACK with priority index 0 according to clause [Link].2.3, by taking
PUSCH HARQ− ACK −LP
HARQ-ACK with priority index 0 as CSI part 2 and replacing β offset by β offset , and taking
HARQ-ACK with priority index 1 if any as HARQ-ACK, and taking CG-UCI associated with priority index
1 if any as CG-UCI.

- Otherwise,

- Perform rate matching for HARQ-ACK with priority index 0 according to clause [Link].2.2, by taking
PUSCH HARQ− ACK −LP
HARQ-ACK with priority index 0 as CSI-part 1 and replacing β offset by β offset , and taking
HARQ-ACK with priority index 1 if any as HARQ-ACK, and taking CG-UCI associated with priority index
1 if any as CG-UCI.

- Perform rate matching for CSI part 1 according to clause [Link].2.3, by taking CSI part 1 as CSI part 2 and
PUSCH CSI− part 1
replacing β offset by β offset , taking HARQ-ACK with priority index 0 as CSI-part 1 and taking HARQ-
ACK with priority index 1 as HARQ-ACK, if CSI part 1 is also transmitted on the PUSCH and the PUSCH
is associated with priority index 0.

- Perform rate matching for CG-UCI associated with priority index 0 according to clause [Link].2.2, if CG-UCI
associated with priority index 0 is transmitted without HARQ-ACK bits associated with priority index 0, by
PUSCH CG−UCI
taking CG-UCI associated with priority index 0 as CSI-part 1 and replacing β offset by β offset , and taking
HARQ-ACK with priority index 1 as HARQ-ACK.

3GPP
Release 17 116 3GPP TS 38.212 V17.5.0 (2023-03)

- Perform rate matching for CG-UCI associated with priority index 0 and HARQ-ACK bits associated with
priority index 0 according to clause [Link].2.2, if both CG-UCI associated with priority index 0 and HARQ-
ACK bits associated with priority index 0 are transmitted, by taking CG-UCI associated with priority index 0
PUSCH HARQ− ACK −L P
and HARQ-ACK bits associated with priority index 0 as CSI-part 1 and replacing β offset by β offset ,
and taking HARQ-ACK with priority index 1 as HARQ-ACK.

- Perform rate matching for CSI part 1 according to clause [Link].2.3, by taking CSI part 1 as CSI part 2 and
PUSCH CSI− part 1
replacing β offset by β offset , taking CG-UCI associated with priority index 0 and HARQ-ACK bits
associated with priority index 0 if any as CSI-part 1 and taking HARQ-ACK with priority index 1 as HARQ-
ACK, if CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 0.

[Link] Code block concatenation

E UCI C UCI
Code block concatenation is performed according to Clause [Link], except that the values of and given in
Clause [Link].1.

[Link] Multiplexing of coded UCI bits to PUSCH

The coded UCI bits are multiplexed onto PUSCH according to the procedures in Clause 6.2.7.

[Link] Multiplexing of coded UCI bits with different priority indexes to PUSCH
If uci-MuxWithDiffPrio is configured, and HARQ-ACK bits associated with priority index 0, and CSI part 1 if any are
transmitted on a PUSCH associated with priority index 1,

- If CSI part 1 is also transmitted on the PUSCH, the coded UCI bits are multiplexed onto PUSCH according to
the procedures in Clause 6.2.7 by taking HARQ-ACK with priority index 0 as CSI part 2, and assuming the
number of HARQ-ACK information in Clause 6.2.7 is 0 bit;

- Otherwise, the coded UCI bits are multiplexed onto PUSCH according to the procedures in Clause 6.2.7 by
taking HARQ-ACK with priority index 0 as CSI-part 1, and assuming the number of HARQ-ACK information
in Clause 6.2.7 is 0 bit.

If uci-MuxWithDiffPrio is configured, and HARQ-ACK bits associated with priority index 1, and CSI if any are
transmitted on a PUSCH associated with priority index 0, the coded UCI bits are multiplexed onto PUSCH according to
the procedures in Clause 6.2.7 by taking HARQ-ACK with priority index 1 as HARQ-ACK.

- if CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 1, the coded
UCI bits are multiplexed onto PUSCH according to the procedures in Clause 6.2.7 by taking HARQ-ACK with
priority index 1 as HARQ-ACK, and taking HARQ-ACK with priority index 0 as CSI part 2;

- otherwise, the coded UCI bits are multiplexed onto PUSCH according to the procedures in Clause 6.2.7 by
taking HARQ-ACK with priority index 1 if any as HARQ-ACK, taking CG-UCI associated with priority index 1
if any as CG-UCI, taking HARQ-ACK with priority index 0 as CSI part 1, and taking CSI part 1 as CSI part 2 if
CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 0.

If uci-MuxWithDiffPrio is configured, and CG-UCI associated with priority index 0 and HARQ-ACK bits associated
with priority index 0 if any, HARQ-ACK bits associated with priority index 1, and CSI part 1 if any are transmitted on a
PUSCH associated with priority index 0, the coded UCI bits are multiplexed onto PUSCH according to the procedures
in Clause 6.2.7 by taking HARQ-ACK with priority index 1 as HARQ-ACK, taking CG-UCI associated with priority
index 0 and HARQ-ACK bits associated with priority index 0 if any as CSI part 1, and taking CSI part 1 as CSI part 2 if
CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 0.

3GPP
Release 17 117 3GPP TS 38.212 V17.5.0 (2023-03)

7 Downlink transport channels and control information

7.1 Broadcast channel
Data arrives to the coding unit in the form of a maximum of one transport block every 80ms. The following coding
steps can be identified:

- Payload generation

- Scrambling

- Transport block CRC attachment

- Channel coding

- Rate matching

7.1.1 PBCH payload generation

ā , ā , ā , ā ,..., ā Ā −1 , where
Denote the bits in a transport block delivered to layer 1 by 0 1 2 3 Ā is the payload size
ā
generated by higher layers. The lowest order information bit 0 is mapped to the most significant bit of the transport
block as defined in Clause 6.1.1 of [8, TS 38.321].

ā , ā , ā , ā ,..., ā Ā+7 , where:

Generate the following additional timing related PBCH payload bits Ā Ā +1 Ā +2 Ā +3

-
ā Ā , ā Ā +1 , ā Ā +2 , ā Ā +3 are the 4th, 3rd, 2nd, and 1st LSB of SFN, respectively;

-
ā Ā+4 ā
is the half frame bit HRF ;

- if Lmax =10 as defined in Clause 4.1 of [5, TS38.213],

a A+5 is the MSB of k SSB as defined in Clause [Link] of [4, TS 38.211].

a A+ 6 is reserved.

a A+7 is the MSB of candidate SS/PBCH block index.

- else if Lmax =20 as defined in Clause 4.1 of [5, TS38.213],

a A+5 is the MSB of k SSB as defined in Clause [Link] of [4, TS 38.211].

a A+ 6, a A+7 are the 5th and 4th bits of the candidate SS/PBCH block index, respectively.

- else if Lmax =64 as defined in Clause 4.1 of [5, TS38.213],

a A+5 , a A+ 6, a A+7 are the 6th, 5th, and 4th bits of the candidate SS/PBCH block index, respectively.
- else

a A+5 is the MSB of k SSB as defined in Clause [Link] of [4, TS 38.211].

a A+ 6, a A+7 are reserved.

- end if

3GPP
Release 17 118 3GPP TS 38.212 V17.5.0 (2023-03)

Let A= Ā +8 ; j SFN =0 ; j HRF=10 ; j SSB =11 ; jother =14 ;

for i=0 to A−1

if
ā i is an SFN bit

a G( j )= āi
SFN ;

j SFN = j SFN +1 ;

elseif
ā i is the half radio frame bit

a G( j
HRF
)= āi

elseif Ā+5≤i≤ Ā+7

a G( j ) =āi
SSB ;

j SSB = j SSB +1 ;

else

aG = āi
( j Other ) ;

j Other = j Other +1 ;

end if

end for

where Lmax is the number of candidate SS/PBCH blocks in a half frame according to Clause 4.1 of [5, TS38.213], and
the value of G( j ) is given by Table 7.1.1-1.

Table 7.1.1-1: Value of PBCH payload interleaver pattern G( j )

j G ( j) j G ( j) j G ( j) j G ( j) j G ( j) j G ( j) j G ( j) j G ( j)
0 16 4 8 8 24 12 3 16 9 20 14 24 21 28 27
1 23 5 30 9 7 13 2 17 11 21 15 25 22 29 28
2 18 6 10 10 0 14 1 18 12 22 19 26 25 30 29
3 17 7 6 11 5 15 4 19 13 23 20 27 26 31 31

7.1.2 Scrambling
For PBCH transmission in a frame, the bit sequence
a 0 , a1 , a 2 , a3 , . .. , a A −1 is scrambled into a bit sequence
a' 0 ,a'1 ,a' 2 ,a'3 ,...,a' A−1 , where a ' i=( ai + si ) mod 2 for i=0,1,..., A−1 and s0 ,s1 ,s2 ,s3 ,..., s A −1 is generated according
to the following:

i=0 ;

j=0 ;

while i < A

3GPP
Release 17 119 3GPP TS 38.212 V17.5.0 (2023-03)

if
a i corresponds to any one of the bits belonging to the candidate SS/PBCH block index, the half frame index, and
2nd and 3rd least significant bits of the system frame number

si =0 ;

else

si =c ( j+ vM ) ;

j= j+1 ;
end if

i=i +1 ;

end while
cell
c =N ID at the start of
The scrambling sequence c(i) is given by Clause 5.2.1of [4, TS38.211] and initialized with init
each SFN satisfying mod ( SFN ,8 )=0 ; M = A−3 for Lmax =4 or Lmax =8, M = A−4 for Lmax =10, M = A−5
for Lmax =20, and M = A−6 for Lmax =64 , where Lmax is the number of candidate SS/PBCH blocks in a half frame
according to Clause 4.1 of [5, TS38.213]; and v is determined according to Table 7.1.2-1 using the 3rd and 2nd LSB of
the SFN in which the PBCH is transmitted.

Table 7.1.2-1: Value of v for PBCH scrambling

(3rd LSB of SFN, 2nd LSB of SFN) Value of v

(0, 0) 0
(0, 1) 1
(1, 0) 2
(1, 1) 3

7.1.3 Transport block CRC attachment

Error detection is provided on BCH transport blocks through a Cyclic Redundancy Check (CRC).

The entire transport block is used to calculate the CRC parity bits. The input bit sequence is denoted by
a' 0 ,a'1 ,a' 2 ,a'3 ,...,a' A−1 , and the parity bits by p0 , p1 , p2 , p3 , . .. , p L−1 , where A is the payload size and L is the
number of parity bits.

The parity bits are computed and attached to the BCH transport block according to Clause 5.1 by setting L to 24 bits
and using the generator polynomial gCRC24C ( D ) , resulting in the sequence 0 1 2 3
b , b , b ,b , .. . , bB−1 , where B= A+ L .

The bit sequence

b 0 , b1 , b 2 ,b 3 , .. . , bB−1 is the input bit sequence c 0 , c 1 , c 2 , c 3 , .. . , c K −1 to the channel encoder, where
c i =bi for i=0,1,..., B−1 and K=B .

7.1.4 Channel coding

Information bits are delivered to the channel coding block. They are denoted by
c 0 , c 1 , c 2 , c 3 , .. . , c K −1 , where K is the

number of bits, and they are encoded via Polar coding according to Clause 5.3.1, by setting max
n =9 , I IL =1 , n PC =0 ,
wm
and n PC =0 .

After encoding the bits are denoted by

d 0 ,d1 ,d 2 ,d3 ,...,d N−1 , where N is the number of coded bits.

3GPP
Release 17 120 3GPP TS 38.212 V17.5.0 (2023-03)

7.1.5 Rate matching

The input bit sequence to rate matching is d 0 ,d1 ,d 2 ,...,d N−1 .

The rate matching output sequence length E=864 .

Rate matching is performed according to Clause 5.4.1 by setting I BIL=0 .

The output bit sequence after rate matching is denoted as f 0 , f 1 , f 2 , .. . , f E−1 .

7.2 Downlink shared channel and paging channel

7.2.1 Transport block CRC attachment
Error detection is provided on each transport block through a Cyclic Redundancy Check (CRC).

number of parity bits. The lowest order information bit

a 0 is mapped to the most significant bit of the transport block
as defined in Clause 6.1.1 of [TS38.321].

The parity bits are computed and attached to the DL-SCH transport block according to Clause 5.1, by setting L to 24
bits and using the generator polynomial gCRC24A ( D ) if A>3824 ; and by setting L to 16 bits and using the generator
polynomial gCRC16 ( D ) otherwise.

The bits after CRC attachment are denoted by

b 0 , b1 , b 2 ,b 3 , .. . , bB−1 , where B= A+ L .

7.2.2 LDPC base graph selection

- if A≤292 , or if A≤3824 and R≤0 .67 , or if R≤0 .25 , LDPC base graph 2 is used;

- otherwise, LDPC base graph 1 is used,

where A is the payload size in Clause 7.2.1.

7.2.3 Code block segmentation and code block CRC attachment

The bits input to the code block segmentation are denoted by
b 0 , b1 , b 2 ,b 3 , .. . , bB−1 where B is the number of bits in the
transport block (including CRC).

Code block segmentation and code block CRC attachment are performed according to Clause 5.2.2.

c r 0 , c r 1 , c r 2 , c r 3 , .. . , cr
The bits after code block segmentation are denoted by ( K r −1 ) , where r is the code block number

and K r is the number of bits for code block number r according to Clause 5.2.2.

7.2.4 Channel coding

3GPP
Release 17 121 3GPP TS 38.212 V17.5.0 (2023-03)

d r 0 ,d r 1 , d r 2 , d r 3 ,. .. , d r ( N −1 )
After encoding the bits are denoted by r , where the values of N r is given in Clause 5.3.2.

7.2.5 Rate matching

f r 0 , f r1 , f r 2 , f r 3 ,. .. , f r ( E −1 ) Er is the number of rate matched bits for

After rate matching, the bits are denoted by r , where
code block number r .

7.2.6 Code block concatenation

f r 0 , f r1 , f r 2 , f r 3 ,. .. , f r E −1
The input bit sequence for the code block concatenation block are the sequences ( r ) , for
r=0 ,. . ., C−1 and where Er is the number of rate matched bits for the r -th code block.

Code block concatenation is performed according to Clause 5.5.

g ,g ,g ,g ,..., gG−1 , where G is the total number of coded bits

The bits after code block concatenation are denoted by 0 1 2 3
for transmission.

7.3 Downlink control information

A DCI transports downlink control information for one or more cells with one RNTI.

The following coding steps can be identified:

- Information element multiplexing

- CRC attachment

- Channel coding

- Rate matching

7.3.1 DCI formats

The DCI formats defined in table 7.3.1-1 are supported.

3GPP
Release 17 122 3GPP TS 38.212 V17.5.0 (2023-03)

Table 7.3.1-1: DCI formats

DCI format Usage

0_0 Scheduling of PUSCH in one cell
Scheduling of one or multiple PUSCH in one cell, or
0_1 indicating downlink feedback information for configured
grant PUSCH (CG-DFI)
0_2 Scheduling of PUSCH in one cell
1_0 Scheduling of PDSCH in one cell
Scheduling of one or multiple PDSCH in one cell, and/or
1_1
triggering one shot HARQ-ACK codebook feedback
1_2 Scheduling of PDSCH in one cell
Notifying a group of UEs of the slot format, available RB
2_0
sets, COT duration and search space set group switching
Notifying a group of UEs of the PRB(s) and OFDM
2_1 symbol(s) where UE may assume no transmission is
intended for the UE
2_2 Transmission of TPC commands for PUCCH and PUSCH
Transmission of a group of TPC commands for SRS
2_3
transmissions by one or more UEs
Notifying a group of UEs of the PRB(s) and OFDM
2_4 symbol(s) where UE cancels the corresponding UL
transmission from the UE
Notifying the availability of soft resources as defined in
2_5
Clause 9.3.1 of [10, TS 38.473]
Notifying the power saving information outside DRX Active
2_6
Time for one or more UEs
Notifying paging early indication and TRS availability
2_7
indication for one or more UEs.
3_0 Scheduling of NR sidelink in one cell
3_1 Scheduling of LTE sidelink in one cell
Schedulng of PDSCH with CRC scrambled by MCCH-
4_0
RNTI/G-RNTI for broadcast
Schedulng of PDSCH with CRC scrambled by G-RNTI/G-
4_1
CS-RNTI for multicast
Schedulng of PDSCH with CRC scrambled by G-RNTI/G-
4_2
CS-RNTI for multicast

The fields defined in the DCI formats below are mapped to the information bits
a 0 to a A−1 as follows.
Each field is mapped in the order in which it appears in the description, including the zero-padding bit(s), if any, with
a
the first field mapped to the lowest order information bit 0 and each successive field mapped to higher order
information bits. The most significant bit of each field is mapped to the lowest order information bit for that field, e.g.
a
the most significant bit of the first field is mapped to 0 .

If the number of information bits in a DCI format is less than 12 bits, zeros shall be appended to the DCI format until
the payload size equals 12.

The size of each DCI format is determined by the configuration of the corresponding active bandwidth part of the
scheduled cell and shall be adjusted as described in clause [Link] if necessary.

If a UE is configured with pdsch-HARQ-ACK-CodebookList-r16, pdsch-HARQ-ACK-Codebook is replaced by the

relevant entry in pdsch-HARQ-ACK-CodebookList-r16 in this clause.

If a UE is configured with pdsch-HARQ-ACK-CodebookListMulticast-r17, pdsch-HARQ-ACK-Codebook is replaced by

the relevant entry in pdsch-HARQ-ACK-CodebookListMulticast-r17 in this clause.

[Link] DCI size alignment

If necessary, padding or truncation shall be applied to the DCI formats according to the following steps executed in the
order below:

3GPP
Release 17 123 3GPP TS 38.212 V17.5.0 (2023-03)

Step 0:
UL,BWP
- Determine DCI format 0_0 monitored in a common search space according to clause [Link].1 where N RB is
the size of the initial UL bandwidth part.
DL,BWP
- Determine DCI format 1_0 monitored in a common search space according to clause [Link].1 where N RB is
given by

- the size of CORESET 0 if CORESET 0 is configured for the cell; and

- the size of initial DL bandwidth part if CORESET 0 is not configured for the cell.

- If DCI format 0_0 is monitored in common search space and if the number of information bits in the DCI format
0_0 prior to padding is less than the payload size of the DCI format 1_0 monitored in common search space for
scheduling the same serving cell, a number of zero padding bits are generated for the DCI format 0_0 until the
payload size equals that of the DCI format 1_0.

- If DCI format 0_0 is monitored in common search space and if the number of information bits in the DCI format
0_0 prior to truncation is larger than the payload size of the DCI format 1_0 monitored in common search space
for scheduling the same serving cell, the bitwidth of the frequency domain resource assignment field in the DCI
format 0_0 is reduced by truncating the first few most significant bits such that the size of DCI format 0_0
equals the size of the DCI format 1_0.

Step 1:
UL,BWP
- Determine DCI format 0_0 monitored in a UE-specific search space according to clause [Link].1 where N RB
is the size of the active UL bandwidth part.
DL,BWP
- Determine DCI format 1_0 monitored in a UE-specific search space according to clause [Link].1 where N RB
is the size of the active DL bandwidth part.

- For a UE configured with supplementaryUplink in ServingCellConfig in a cell, if PUSCH is configured to be

transmitted on both the SUL and the non-SUL of the cell and if the number of information bits in DCI format
0_0 in UE-specific search space for the SUL is not equal to the number of information bits in DCI format 0_0 in
UE-specific search space for the non-SUL, a number of zero padding bits are generated for the smaller DCI
format 0_0 until the payload size equals that of the larger DCI format 0_0.

- If DCI format 0_0 is monitored in UE-specific search space and if the number of information bits in the DCI
format 0_0 prior to padding is less than the payload size of the DCI format 1_0 monitored in UE-specific search
space for scheduling the same serving cell, a number of zero padding bits are generated for the DCI format 0_0
until the payload size equals that of the DCI format 1_0.

- If DCI format 1_0 is monitored in UE-specific search space and if the number of information bits in the DCI
format 1_0 prior to padding is less than the payload size of the DCI format 0_0 monitored in UE-specific search
space for scheduling the same serving cell, zeros shall be appended to the DCI format 1_0 until the payload size
equals that of the DCI format 0_0

Step 2:

- Determine DCI format 0_1 monitored in a UE-specific search space according to clause [Link].2.

- Determine DCI format 1_1 monitored in a UE-specific search space according to clause [Link].2.

- For a UE configured with supplementaryUplink in ServingCellConfig in a cell, if PUSCH is configured to be

transmitted on both the SUL and the non-SUL of the cell and if the number of information bits in format 0_1 for
the SUL is not equal to the number of information bits in format 0_1 for the non-SUL, zeros shall be appended
to smaller format 0_1 until the payload size equals that of the larger format 0_1.

- If the size of DCI format 0_1 monitored in a UE-specific search space equals that of a DCI format 0_0/1_0
monitored in another UE-specific search space, one bit of zero padding shall be appended to DCI format 0_1.

- If the size of DCI format 1_1 monitored in a UE-specific search space equals that of a DCI format 0_0/1_0
monitored in another UE-specific search space, one bit of zero padding shall be appended to DCI format 1_1.

3GPP
Release 17 124 3GPP TS 38.212 V17.5.0 (2023-03)

Step 2A:

- Determine DCI format 0_2 monitored in a UE-specific search space according to clause [Link].3.

- Determine DCI format 1_2 monitored in a UE-specific search space according to clause [Link].3.

- For a UE configured with supplementaryUplink in ServingCellConfig in a cell, if PUSCH is configured to be

transmitted on both the SUL and the non-SUL of the cell and if the number of information bits in format 0_2 for
the SUL is not equal to the number of information bits in format 0_2 for the non-SUL, zeros shall be appended
to smaller format 0_2 until the payload size equals that of the larger format 0_2.

Step 3:

- If both of the following conditions are fulfilled the size alignment procedure is complete

- the total number of different DCI sizes configured to monitor is no more than 4 for the cell

- the total number of different DCI sizes with C-RNTI configured to monitor is no more than 3 for the cell

Step 4:

- Otherwise

Step 4A:

- Remove the padding bit (if any) introduced in step 2 above.

- Determine DCI format 1_0 monitored in a UE-specific search space according to clause [Link].1 where
N DL,BWP
RB is given by

- the size of CORESET 0 if CORESET 0 is configured for the cell; and

- the size of initial DL bandwidth part if CORESET 0 is not configured for the cell.

- Determine DCI format 0_0 monitored in a UE-specific search space according to clause [Link].1 where
N UL,BWP
RB is the size of the initial UL bandwidth part.

- If the number of information bits in the DCI format 0_0 monitored in a UE-specific search space prior to
padding is less than the payload size of the DCI format 1_0 monitored in UE-specific search space for
scheduling the same serving cell, a number of zero padding bits are generated for the DCI format 0_0
monitored in a UE-specific search space until the payload size equals that of the DCI format 1_0 monitored
in a UE-specific search space.

- If the number of information bits in the DCI format 0_0 monitored in a UE-specific search space prior to
truncation is larger than the payload size of the DCI format 1_0 monitored in UE-specific search space for
scheduling the same serving cell, the bitwidth of the frequency domain resource assignment field in the DCI
format 0_0 is reduced by truncating the first few most significant bits such that the size of DCI format 0_0
monitored in a UE-specific search space equals the size of the DCI format 1_0 monitored in a UE-specific
search space.

Step 4B:

- If the total number of different DCI sizes configured to monitor is more than 4 for the cell after applying the
above steps, or if the total number of different DCI sizes with C-RNTI configured to monitor is more than 3
for the cell after applying the above steps

- If the number of information bits in the DCI format 0_2 prior to padding is less than the payload size of
the DCI format 1_2 for scheduling the same serving cell, a number of zero padding bits are generated for
the DCI format 0_2 until the payload size equals that of the DCI format 1_2.

- If the number of information bits in the DCI format 1_2 prior to padding is less than the payload size of
the DCI format 0_2 for scheduling the same serving cell, zeros shall be appended to the DCI format 1_2
until the payload size equals that of the DCI format 0_2.

Step 4C:

3GPP
Release 17 125 3GPP TS 38.212 V17.5.0 (2023-03)

- If the number of information bits in the DCI format 0_1 prior to padding is less than the payload size of
the DCI format 1_1 for scheduling the same serving cell, a number of zero padding bits are generated for
the DCI format 0_1 until the payload size equals that of the DCI format 1_1.

- If the number of information bits in the DCI format 1_1 prior to padding is less than the payload size of
the DCI format 0_1 for scheduling the same serving cell, zeros shall be appended to the DCI format 1_1
until the payload size equals that of the DCI format 0_1.

The UE is not expected to handle a configuration that, after applying the above steps, results in

- the total number of different DCI sizes configured to monitor is more than 4 for the cell; or

- the total number of different DCI sizes with C-RNTI configured to monitor is more than 3 for the cell; or

- the size of DCI format 0_0 in a UE-specific search space is equal to DCI format 0_1 in another UE-specific
search space; or

- the size of DCI format 1_0 in a UE-specific search space is equal to DCI format 1_1 in another UE-specific
search space; or

- the size of DCI format 0_0 in a UE-specific search space is equal to DCI format 0_2 in another UE-specific
search space when at least one pair of the corresponding PDCCH candidates of DCI formats 0_0 and 0_2 are
mapped to the same resource; or

- the size of DCI format 1_0 in a UE-specific search space is equal to DCI format 1_2 in another UE-specific
search space when at least one pair of the corresponding PDCCH candidates of DCI formats 1_0 and 1_2 are
mapped to the same resource; or

- the size of DCI format 0_1 in a UE-specific search space is equal to DCI format 0_2 in the same or another UE-
specific search space when at least one pair of the corresponding PDCCH candidates of DCI formats 0_1 and
0_2 are mapped to the same resource; or

- the size of DCI format 1_1 in a UE-specific search space is equal to DCI format 1_2 in the same or another UE-
specific search space when at least one pair of the corresponding PDCCH candidates of DCI formats 1_1 and
1_2 are mapped to the same resource.

[Link].1 DCI size alignment for DCI formats for scheduling of sidelink
If DCI format 3_0 or DCI format 3_1 is monitored on a cell, DCI size alignment for DCI format 3_0 and DCI format
3_1 is performed as described in this clause after performing the DCI size alignment described in Clause [Link]. The
size(s) of the DCI formats configured to monitor for a cell in this clause refers to that after performing the DCI size
alignment described in Clause [Link].

If DCI format 3_0 or DCI format 3_1 is monitored on a cell and the total number of DCI sizes of the DCI formats
configured to monitor for the cell and DCI format 3_0 or DCI format 3_1 is more than 4, zeros shall be appended to
DCI format 3_0 if configured and DCI format 3_1 if configured, until the payload size of DCI format 3_0 or DCI
format 3_1 equals that of the smallest DCI format configured to monitor for the cell that is larger than DCI format 3_0
or DCI format 3_1.

The UE is not expected to handle a configuration that results in:

- the total number of different DCI sizes configured to monitor for the cell and DCI format 3_0 or DCI format 3_1
is more than 4; and

- the payload size of DCI format 3_0 or DCI format 3_1 is larger than the payload size of all other DCI formats
configured to monitor for the cell.

3GPP
Release 17 126 3GPP TS 38.212 V17.5.0 (2023-03)

[Link] DCI formats for scheduling of PUSCH

[Link].1 Format 0_0
DCI format 0_0 is used for the scheduling of PUSCH in one cell.

The following information is transmitted by means of the DCI format 0_0 with CRC scrambled by C-RNTI or CS-
RNTI or MCS-C-RNTI:

- Identifier for DCI formats – 1 bit

- The value of this bit field is always set to 0, indicating an UL DCI format

- Frequency domain resource assignment – number of bits determined by the following:

-
⌈log2 ( N UL,BWP
RB ( N UL,BWP
RB +1 )/2)⌉ bits if neither of the higher layer parameters useInterlacePUCCH-PUSCH
in BWP-UplinkCommon and useInterlacePUCCH-PUSCH in BWP-UplinkDedicated is configured, where
N UL,BWP
RB is defined in clause [Link]

- For PUSCH hopping with resource allocation type 1:

-
N UL_hop MSB bits are used to indicate the frequency offset according to Clause 6.3 of [6, TS 38.214],
N
where UL_hop
=1 if the higher layer parameter frequencyHoppingOffsetLists contains two offset
values and
N UL_hop =2 if the higher layer parameter frequencyHoppingOffsetLists contains four offset
values

-
⌈log2 ( N UL,BWP
RB ( N UL,BWP
RB +1)/2)⌉−N UL_hop bits provide the frequency domain resource allocation
according to Clause [Link].2 of [6, TS 38.214]

- For non-PUSCH hopping with resource allocation type 1:

-
⌈log2 ( N UL,BWP
RB ( N UL,BWP
RB +1 )/2)⌉ bits provide the frequency domain resource allocation according to
Clause [Link].2 of [6, TS 38.214]

- If any of the higher layer parameters useInterlacePUCCH-PUSCH in BWP-UplinkCommon and

useInterlacePUCCH-PUSCH in BWP-UplinkDedicated is configured

- 5+Y bits provide the frequency domain resource allocation according to Clause [Link].3 of [6, TS
38.214] if the subcarrier spacing for the active UL bandwidth part is 30 kHz.

- 6+Y bits provide the frequency domain resource allocation according to Clause [Link].3 of [6, TS
38.214] if the subcarrier spacing for the active UL bandwidth part is 15 kHz.

If the DCI format 0_0 is monitored in a UE-specific search space, the value of Y is determined by

( RB-set,UL ( N RB- set,UL +1 )

N BWP
)
BWP
BWP
⌈ log 2 ⌉ where N RB-set,UL is the number of RB sets contained in the active UL
2
BWP as defined in clause 7 of [6, TS38.214]. If the DCI 0_0 is monitored in a common search space Y = 0.

- Time domain resource assignment – 4 bits as defined in Clause [Link] of [6, TS 38.214]

- Frequency hopping flag – 1 bit according to Table [Link].1-3, as defined in Clause 6.3 of [6, TS 38.214]

- Modulation and coding scheme – 5 bits as defined in Clause [Link] of [6, TS 38.214]

- New data indicator – 1 bit

- Redundancy version – 2 bits as defined in Table [Link].1-2

- HARQ process number – 4 bits

3GPP
Release 17 127 3GPP TS 38.212 V17.5.0 (2023-03)

- TPC command for scheduled PUSCH – 2 bits as defined in Clause 7.1.1 of [5, TS 38.213]

- ChannelAccess-CPext – 2 bits indicating combinations of channel access type and CP extension as defined in
Table [Link].1-4, or Table [Link].1-4A if channelAccessMode-r16 = "semiStatic" is provided, for operation in a
cell with shared spectrum channel access in frequency range 1; 2 bits indicating channel access type as defined
in Table [Link].1-4B if ChannelAccessMode2-r17 is provided for operation in a cell in frequency range 2-2; 0
bit otherwise.

- Padding bits, if required.

- UL/SUL indicator – 1 bit for UEs configured with supplementaryUplink in ServingCellConfig in the cell as
defined in Table [Link].1-1 and the number of bits for DCI format 1_0 before padding is larger than the number
of bits for DCI format 0_0 before padding; 0 bit otherwise. The UL/SUL indicator, if present, locates in the last
bit position of DCI format 0_0, after the padding bit(s).

- If the UL/SUL indicator is present in DCI format 0_0 and the higher layer parameter pusch-Config is not
configured on both UL and SUL the UE ignores the UL/SUL indicator field in DCI format 0_0, and the
corresponding PUSCH scheduled by the DCI format 0_0 is for the UL or SUL for which high layer
parameter pucch-Config is configured;

- If the UL/SUL indicator is not present in DCI format 0_0 and pucch-Config is configured, the corresponding
PUSCH scheduled by the DCI format 0_0 is for the UL or SUL for which high layer parameter pucch-Config
is configured.

- If the UL/SUL indicator is not present in DCI format 0_0 and pucch-Config is not configured, the
corresponding PUSCH scheduled by the DCI format 0_0 is for the uplink on which the latest PRACH is
transmitted.

The following information is transmitted by means of the DCI format 0_0 with CRC scrambled by TC-RNTI:

- Identifier for DCI formats – 1 bit

- The value of this bit field is always set to 0, indicating an UL DCI format

- Frequency domain resource assignment – number of bits determined by the following:

-
⌈log2 ( N UL,BWP
RB ( N UL,BWP
RB +1 )/2)⌉ bits if the higher layer parameter useInterlacePUCCH-PUSCH in BWP-
UplinkCommon is not configured, where

- N UL,BWP
RB is the size of the initial UL bandwidth part.

- For PUSCH hopping with resource allocation type 1:

-
N UL_hop MSB bits are used to indicate the frequency offset according to Table 8.3-1 in Clause 8.3 of
N
[5, TS 38.213], where UL_hop
=1 if N UL,BWP
RB < 50 and N UL_hop =2 otherwise

-
⌈log2 ( N UL,BWP
RB ( N UL,BWP
RB +1)/2)⌉−N UL_hop bits provide the frequency domain resource allocation
according to Clause [Link].2 of [6, TS 38.214]

- For non-PUSCH hopping with resource allocation type 1:

-
⌈log 2 ( N UL,BWP
RB ( N UL,BWP
RB +1)/2)⌉ bits provide the frequency domain resource allocation according to
Clause [Link].2 of [6, TS 38.214]

- If the higher layer parameter useInterlacePUCCH-PUSCH in BWP-UplinkCommon is configured

- 5 bits provide the frequency domain resource allocation according to Clause [Link].3 of [6, TS 38.214] if
the subcarrier spacing for the active UL bandwidth part is 30 kHz

- 6 bits provide the frequency domain resource allocation according to Clause [Link].3 of [6, TS 38.214] if
the subcarrier spacing for the active UL bandwidth part is 15 kHz

3GPP
Release 17 128 3GPP TS 38.212 V17.5.0 (2023-03)

- Time domain resource assignment – 4 bits as defined in Clause [Link] of [6, TS 38.214]

- Frequency hopping flag – 1 bit according to Table [Link].1-3, as defined in Clause 6.3 of [6, TS 38.214]

- Modulation and coding scheme – 5 bits

- If the UE requests repetition of PUSCH scheduled by RAR UL grant [8, TS 38.321], 5 bits as defined in
Clause [Link] and Clause [Link] of [6, TS 38.214];

- otherwise 5 bits as defined in Clause [Link] of [6, TS 38.214].

- New data indicator – 1 bit, reserved

- Redundancy version – 2 bits as defined in Table [Link].1-2

- HARQ process number – 4 bits, reserved

- TPC command for scheduled PUSCH – 2 bits as defined in Clause 7.1.1 of [5, TS 38.213]

- Padding bits, if required.

- UL/SUL indicator – 1 bit if the cell has two ULs and the number of bits for DCI format 1_0 before padding is
larger than the number of bits for DCI format 0_0 before padding; 0 bit otherwise. The UL/SUL indicator, if
present, locates in the last bit position of DCI format 0_0, after the padding bit(s).

- If 1 bit, reserved, and the corresponding PUSCH is always on the same UL carrier as the previous
transmission of the same TB

Table [Link].1-1: UL/SUL indicator

Value of UL/SUL indicator Uplink

0 The non-supplementary uplink
1 The supplementary uplink

Table [Link].1-2: Redundancy version

Value of the Redundancy rv id

version field Value of to be applied
00 0
01 1
10 2
11 3

Table [Link].1-3: Frequency hopping indication

Bit field mapped to index PUSCH frequency hopping

0 Disabled
1 Enabled

3GPP
Release 17 129 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].1-4: Channel access type & CP extension for DCI format 0_0 and DCI format 1_0 for
frequency range 1

The CP extension T_"ext" index

Bit field mapped to index Channel Access Type defined in Clause 5.3.1 of [4, TS
38.211]
0 Type2C-ULChannelAccess 2
defined in [clause [Link].3 in
37.213]
1 Type2A-ULChannelAccess 3
defined in [clause [Link].1 in
37.213]
2 Type2A-ULChannelAccess 1
defined in [clause [Link].1 in
37.213]
3 Type1-ULChannelAccess defined 0
in [clause [Link] in 37.213]

Table [Link].1-4A: Channel access type & CP extension if channelAccessMode-r16 = "semiStatic" is

provided

Table [Link].1-4B: Channel access type for DCI format 0_0 and DCI format 1_0 for frequency range 2-
2

Bit field mapped to index Channel Access Type

0 Type 1 channel access defined in clause 4.4.1 of 37.213

1 Type 2 channel access defined in clause 4.4.2 of 37.213

2 Type 3 channel access defined in clause 4.4.3 of 37.213

3 Reserved

[Link].2 Format 0_1

DCI format 0_1 is used for the scheduling of one or multiple PUSCH in one cell, or indicating CG downlink feedback
information (CG-DFI) to a UE.

The following information is transmitted by means of the DCI format 0_1 with CRC scrambled by C-RNTI or CS-
RNTI or SP-CSI-RNTI or MCS-C-RNTI:

- Identifier for DCI formats – 1 bit

- The value of this bit field is always set to 0, indicating an UL DCI format

3GPP
Release 17 130 3GPP TS 38.212 V17.5.0 (2023-03)

- Carrier indicator – 0 or 3 bits, as defined in Clause 10.1 of [5, TS38.213]. This field is reserved when this format
is carried by PDCCH on the primary cell and the UE is configured for scheduling on the primary cell from an
SCell, with the same number of bits as that in this format carried by PDCCH on the SCell for scheduling on the
primary cell.

- DFI flag – 0 or 1 bit

- 1 bit if the UE is configured to monitor DCI format 0_1 with CRC scrambled by CS-RNTI and for operation
in a cell with shared spectrum channel access when the higher layer parameter cg-RetransmissionTimer is
configured. For a DCI format 0_1 with CRC scrambled by CS-RNTI, the bit value of 0 indicates activating or
releasing type 2 CG transmission and the bit value of 1 indicates CG-DFI. For a DCI format 0_1 with CRC
scrambled by C-RNTI/SP-CSI-RNTI/MCS-C-RNTI and for operation in a cell with shared spectrum channel
access, the bit is reserved.

- 0 bit otherwise;

If DCI format 0_1 is used for indicating CG-DFI, all the remaining fields are set as follows:

- HARQ-ACK bitmap – 16 bits if nrofHARQ-Processes-v1700 in ConfiguredGrantConfig is not configured or 32

bits if nrofHARQ-Processes-v1700 in ConfiguredGrantConfig is configured, where the order of the bitmap to
HARQ process index mapping is such that HARQ process indices are mapped in ascending order from MSB to
LSB of the bitmap. For each bit of the bitmap, value 1 indicates ACK, and value 0 indicates NACK.

- TPC command for scheduled PUSCH – 2 bits as defined in Clause 7.1.1 of [5, TS38.213]

- All the remaining bits in format 0_1 are set to zero.

Otherwise, all the remaining fields are set as follows:

- UL/SUL indicator – 0 bit for UEs not configured with supplementaryUplink in ServingCellConfig in the cell or
UEs configured with supplementaryUplink in ServingCellConfig in the cell but only one carrier in the cell is
configured for PUSCH transmission; otherwise, 1 bit as defined in Table [Link].1-1.

- Bandwidth part indicator – 0, 1 or 2 bits as determined by the number of UL BWPs configured by

higher layers, excluding the initial UL bandwidth part. The bitwidth for this field is determined as ⌈log 2 ( nBWP )⌉
bits, where

-
n BWP=n BWP,RRC +1 if , in which case the bandwidth part indicator is equivalent to the ascending
order of the higher layer parameter BWP-Id;

- otherwise
n BWP=n BWP,RRC , in which case the bandwidth part indicator is defined in Table [Link].2-1;

If a UE does not support active BWP change via DCI, the UE ignores this bit field.
UL,BWP
- Frequency domain resource assignment – number of bits determined by the following, where N RB is the size
of the active UL bandwidth part:

- If higher layer parameter useInterlacePUCCH-PUSCH in BWP-UplinkDedicated is not configured

-
N RBG bits if only resource allocation type 0 is configured, where N RBG is defined in Clause [Link].1 of
[6, TS 38.214],

-
⌈log2 ( N UL,BWP
RB ( N UL,BWP
RB +1 )/2)⌉ bits if only resource allocation type 1 is configured, or
max ( ⌈ log 2 ( N UL,BWP ( N UL,BWP +1)/ 2 )⌉, N RBG )+1
RB RB bits if resourceAllocation is configured as
'dynamicSwitch'.

- If resourceAllocation is configured as 'dynamicSwitch', the MSB bit is used to indicate resource

allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type
0 and the bit value of 1 indicates resource allocation type 1.

3GPP
Release 17 131 3GPP TS 38.212 V17.5.0 (2023-03)

- For resource allocation type 0, the

N RBG LSBs provide the resource allocation as defined in Clause
[Link].1 of [6, TS 38.214].

- For resource allocation type 1, the

⌈log2 ( N UL,BWP
RB ( N UL,BWP
RB +1 )/2)⌉ LSBs provide the resource allocation
as follows:

- For PUSCH hopping with resource allocation type 1:

-
N UL_hop MSB bits are used to indicate the frequency offset according to Clause 6.3 of [6, TS
N
38.214], where UL_hop
=1 if the higher layer parameter frequencyHoppingOffsetLists contains
N
two offset values and UL_hop
=2 if the higher layer parameter frequencyHoppingOffsetLists
contains four offset values

-
⌈log2 ( N UL,BWP
RB ( N UL,BWP
RB +1)/2)⌉−N UL_hop bits provide the frequency domain resource allocation
according to Clause [Link].2 of [6, TS 38.214]

- For non-PUSCH hopping with resource allocation type 1:

-
⌈log 2 ( N UL,BWP
RB ( N UL,BWP
RB +1)/2)⌉ bits provide the frequency domain resource allocation according
to Clause [Link].2 of [6, TS 38.214]

If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and if
resourceAllocation is configured as 'dynamicSwitch' for the indicated bandwidth part, the UE assumes
resource allocation type 0 for the indicated bandwidth part if the bitwidth of the "Frequency domain resource
assignment" field of the active bandwidth part is smaller than the bitwidth of the "Frequency domain resource
assignment" field of the indicated bandwidth part.

- If the higher layer parameter useInterlacePUCCH-PUSCH in BWP-UplinkDedicated is configured

- 5 + Y bits provide the frequency domain resource allocation according to Clause [Link].3 of [6, TS
38.214] if the subcarrier spacing for the active UL bandwidth part is 30 kHz. The 5 MSBs provide the
interlace allocation and the Y LSBs provide the RB set allocation.

- 6 + Y bits provide the frequency domain resource allocation according to Clause [Link].3 of [6, TS
38.214] if the subcarrier spacing for the active UL bandwidth part is 15 kHz. The 6 MSBs provide the
interlace allocation and the Y LSBs provide the RB set allocation.

( N RB −set ,UL ( N RB− set ,UL + 1 )

)
BWP BWP
BWP
The value of Y is determined by ⌈ log
2 ⌉ where N RB-set,UL is the number of
2
RB sets contained in the active UL BWP as defined in clause 7 of [6, TS38.214].

- Time domain resource assignment – 0, 1, 2, 3, 4, 5, or 6 bits

- If the higher layer parameter pusch-TimeDomainAllocationListDCI-0-1 is not configured and if the higher
layer parameter pusch-TimeDomainAllocationListForMultiPUSCH is not configured and if the higher layer
parameter pusch-TimeDomainAllocationList is configured, 0, 1, 2, 3, or 4 bits as defined in Clause [Link] of
[6, TS38.214]. The bitwidth for this field is determined as
⌈log 2 ( I )⌉ bits, where I is the number of entries in
the higher layer parameter pusch-TimeDomainAllocationList;

- If the higher layer parameter pusch-TimeDomainAllocationListDCI-0-1 is configured or if the higher layer

parameter pusch-TimeDomainAllocationListForMultiPUSCH is configured, 0, 1, 2, 3, 4, 5 or 6 bits as
defined in Clause [Link] of [6, TS38.214]. The bitwidth for this field is determined as ⌈ log 2 (I ) ⌉ bits,
where I is the number of entries in the higher layer parameter pusch-TimeDomainAllocationListDCI-0-1 or
pusch-TimeDomainAllocationListForMultiPUSCH;

- otherwise the bitwidth for this field is determined as ⌈ log 2 (I )⌉ bits, where I is the number of entries in the
default table.

3GPP
Release 17 132 3GPP TS 38.212 V17.5.0 (2023-03)

- Frequency hopping flag – 0 or 1 bit:

- 0 bit if only resource allocation type 0 is configured, or if the higher layer parameter frequencyHopping is not
configured and the higher layer parameter pusch-RepTypeIndicatorDCI-0-1 is not configured to pusch-
RepTypeB, or if the higher layer parameter frequencyHoppingDCI-0-1 is not configured and pusch-
RepTypeIndicatorDCI-0-1 is configured to pusch-RepTypeB, or if only resource allocation type 2 is
configured;

- 1 bit according to Table [Link].1-3 otherwise, only applicable to resource allocation type 1, as defined in
Clause 6.3 of [6, TS 38.214].

- Modulation and coding scheme – 5 bits as defined in Clause [Link] of [6, TS 38.214]

- New data indicator – 1 bit if the number of scheduled PUSCH indicated by the Time domain resource
assignment field is 1; otherwise 2, 3, 4, 5, 6, 7 or 8 bits determined based on the maximum number of
schedulable PUSCH among all entries in the higher layer parameter pusch-
TimeDomainAllocationListForMultiPUSCH, where each bit corresponds to one scheduled PUSCH as defined in
clause 6.1.4 in [6, TS 38.214].

- Redundancy version – – number of bits determined by the following:

- 2 bits as defined in Table [Link].1-2 if the number of scheduled PUSCH indicated by the Time domain
resource assignment field is 1;

- otherwise 2, 3, 4, 5, 6, 7 or 8 bits determined by the maximum number of schedulable PUSCHs among all
entries in the higher layer parameter pusch-TimeDomainAllocationListForMultiPUSCH, where each bit
corresponds to one scheduled PUSCH as defined in clause 6.1.4 in [6, TS 38.214] and redundancy version is
determined according to Table [Link].2-34.

- HARQ process number – 5 bits if higher layer parameter harq-ProcessNumberSizeDCI-0-1 is configured;

otherwise 4 bits

- 1st downlink assignment index – 1, 2 or 4 bits:

- 1 bit for semi-static HARQ-ACK codebook for unicast and multicast if pdsch-HARQ-ACK-Codebook =
semiStatic is configured for both unicast and multicast and the higher layer parameter fdmed-
ReceptionMulticast is not configured; otherwise for semi-static HARQ-ACK codebook for unicast;

- 2 bits for dynamic HARQ-ACK codebook for unicast, or for enhanced dynamic HARQ-ACK codebook
without UL-TotalDAI-Included configured;

- 4 bits for enhanced dynamic HARQ-ACK codebook and with UL-TotalDAI-Included = true.

When two HARQ-ACK codebooks are configured by pdsch-HARQ-ACK-CodebookList for the same serving
cell and if higher layer parameter priorityIndicatorDCI-0-1 is configured, if the bit width of the 1st downlink
assignment index in DCI format 0_1 for one HARQ-ACK codebook is not equal to that of the 1st downlink
assignment index in DCI format 0_1 for the other HARQ-ACK codebook, a number of most significant bits
with value set to '0' are inserted to smaller 1st downlink assignment index until the bit width of the 1st
downlink assignment index in DCI format 0_1 for the two HARQ-ACK codebooks are the same.

- 2nd downlink assignment index – 0, 2 or 4 bits:

- 2 bits for dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks for unicast, or for enhanced
dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks and without UL-TotalDAI-Included
configured;

- 4 bits for enhanced dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks and with UL-
TotalDAI-Included = true;

- 0 bit otherwise.

3GPP
Release 17 133 3GPP TS 38.212 V17.5.0 (2023-03)

with value set to '0' are inserted to smaller 2nd downlink assignment index until the bit width of the 2nd
downlink assignment index in DCI format 0_1 for the two HARQ-ACK codebooks are the same.

- 3rd downlink assignment index – 0, 1 or 2 bits:

- 1 bit for semi-static HARQ-ACK codebook for multicast if the higher layer parameter fdmed-
ReceptionMulticast is configured;

- 2 bits for the dynamic HARQ-ACK codebook for multicast;

- 0 bit otherwise.

When two HARQ-ACK codebooks are configured by pdsch-HARQ-ACK-CodebookListMulticast for the

same serving cell and if higher layer parameter priorityIndicatorDCI-0-1 is configured, if the bit width of the
3rd downlink assignment index in DCI format 0_1 for one HARQ-ACK codebook is not equal to that of the
3rd downlink assignment index in DCI format 0_1 for the other HARQ-ACK codebook, a number of most
significant bits with value set to '0' are inserted to smaller 3rd downlink assignment index until the bit width of
the 3rd downlink assignment index in DCI format 0_1 for the two HARQ-ACK codebooks are the same.

- TPC command for scheduled PUSCH – 2 bits as defined in Clause 7.1.1 of [5, TS38.213]

- Second TPC command for scheduled PUSCH – 2 bits as defined in Clause 7.1.1 of [5, TS38.213] if higher layer
parameter SecondTPCFieldDCI-0-1 is configured; 0 bit otherwise.

- SRS resource set indicator – 0 or 2 bits

- 2 bits according to Table [Link].2-36 if

- txConfig = nonCodeBook, and there are two SRS resource sets configured by srs-
ResourceSetToAddModList and associated with the usage of value 'nonCodeBook', or

- txConfig=codebook, and there are two SRS resource sets configured by srs-ResourceSetToAddModList
and associated with usage of value 'codebook';

- 0 bit otherwise.

( ( ))
min { Lmax , N SRS }
N SRS
⌈ log 2 ∑ k
⌉
⌈log 2 ( N SRS ) ⌉ N
k =1
- SRS resource indicator – or bits, where SRS is the number of
configured SRS resources in the SRS resource set indicated by SRS resource set indicator field if present;
otherwise N SRS is the number of configured SRS resources in the SRS resource set configured by higher layer
parameter srs-ResourceSetToAddModList and associated with the higher layer parameter usage of value
'codeBook' or 'nonCodeBook',

( ( N k ))⌉
min { Lmax , N SRS }

⌈log 2 ∑ SRS
k =1
- bits according to Tables [Link].2-28/29/30/31 if the higher layer parameter
N
txConfig = nonCodebook, where SRS is the number of configured SRS resources in the SRS resource set
indicated by SRS resource set indicator field if present, otherwise N SRS is the number of configured SRS
resources in the SRS resource set configured by higher layer parameter srs-ResourceSetToAddModList and
associated with the higher layer parameter usage of value 'nonCodeBook', and

- if UE supports operation with maxMIMO-Layers and the higher layer parameter maxMIMO-Layers of
PUSCH-ServingCellConfig of the serving cell is configured, Lmax is given by that parameter

- otherwise, Lmax is given by the maximum number of layers for PUSCH supported by the UE for the
serving cell for non-codebook based operation.

⌈log 2 ( N SRS ) ⌉
- bits according to Tables [Link].2-32, [Link].2-32A and [Link].2-32B if the higher layer
N
parameter txConfig = codebook, where SRS is the number of configured SRS resources in the SRS resource
set indicated by SRS resource set indicator field if present, otherwise N SRS is the number of configured SRS

3GPP
Release 17 134 3GPP TS 38.212 V17.5.0 (2023-03)

resources in the SRS resource set configured by higher layer parameter srs-ResourceSetToAddModList and
associated with the higher layer parameter usage of value 'codeBook'.

- Second SRS resource indicator – 0, ⌈ log 2 ( max

k ∈{1 ,2 ,… , min⁡{L max , N SRS }} ( Nk ))⌉
SRS
or ⌈ log 2 (N SRS )⌉ bits,

- ⌈ log 2 ( max
k ∈ {1 ,2 ,… , min⁡{L max , N SRS }} ( )
N SRS )⌉
k
bits according to Tables [Link].2-28/29A/30A/31A with the same

number of layers indicated by SRS resource indicator field if the higher layer parameter txConfig =
nonCodebook and SRS resource set indicator field is present, where N SRS is the number of configured SRS
resources in the second SRS resource set, and

- if UE supports operation with maxMIMO-Layers and the higher layer parameter maxMIMO-Layers of
PUSCH-ServingCellConfig of the serving cell is configured, Lmax is given by that parameter

- otherwise, Lmax is given by the maximum number of layers for PUSCH supported by the UE for the
serving cell for non-codebook based operation.

- ⌈ log 2 (N SRS )⌉ bits according to Tables [Link].2-32, [Link].2-32A and [Link].2-32B if the higher layer
parameter txConfig = codebook and SRS resource set indicator field is present, where N SRS is the number of
configured SRS resources in the second SRS resource set.

- 0 bit otherwise.

- Precoding information and number of layers – number of bits determined by the following:

- 0 bits if the higher layer parameter txConfig = nonCodeBook;

- 0 bits for 1 antenna port and if the higher layer parameter txConfig = codebook;

- 4, 5, or 6 bits according to Table [Link].2-2 for 4 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower,
transform precoder is disabled, and according to the values of higher layer parameters maxRank, and
codebookSubset;

- 4 or 5 bits according to Table [Link].2-2A for 4 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission = fullpowerMode1, maxRank=2, transform precoder is disabled, and according to
the values of higher layer parameter codebookSubset;

- 4 or 6 bits according to Table [Link].2-2B for 4 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission = fullpowerMode1, maxRank=3 or 4, transform precoder is disabled, and according
to the values of higher layer parameter codebookSubset;

- 2, 4, or 5 bits according to Table [Link].2-3 for 4 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower, and
according to whether transform precoder is enabled or disabled, and the values of higher layer parameters
maxRank, and codebookSubset;

- 3 or 4 bits according to Table [Link].2-3A for 4 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission = fullpowerMode1, maxRank=1, and according to whether transform precoder is
enabled or disabled, and the values of higher layer parameter codebookSubset;

- 2 or 4 bits according to Table7.[Link]-4 for 2 antenna ports, if txConfig = codebook, ul-

FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower,
transform precoder is disabled, and according to the values of higher layer parameters maxRank and
codebookSubset;

- 2 bits according to Table [Link].2-4A for 2 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission = fullpowerMode1, transform precoder is disabled, maxRank=2, and
codebookSubset=nonCoherent;

- 1 or 3 bits according to Table7.[Link]-5 for 2 antenna ports, if txConfig = codebook, ul-

FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower, and

3GPP
Release 17 135 3GPP TS 38.212 V17.5.0 (2023-03)

according to whether transform precoder is enabled or disabled, and the values of higher layer parameters
maxRank and codebookSubset;

- 2 bits according to Table [Link].2-5A for 2 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission = fullpowerMode1, maxRank=1, and according to whether transform precoder is
enabled or disabled, and the values of higher layer parameter codebookSubset;

For the higher layer parameter txConfig=codebook, if ul-FullPowerTransmission is configured to

fullpowerMode2, maxRank is configured to be larger than 2, and at least one SRS resource with 4 antenna ports
is configured in the SRS resource set indicated by SRS resource set indicator field if present, otherwise in an
SRS resource set with usage set to 'codebook', and an SRS resource with 2 antenna ports is indicated via SRI in
the same SRS resource set, then Table [Link].2-4 is used.

For the higher layer parameter txConfig = codebook, if different SRS resources with different number of antenna
ports are configured, the bitwidth is determined according to the maximum number of ports in an SRS resource
among the configured SRS resources in all SRS resource set(s) with usage set to 'codebook'. If the number of
ports for a configured SRS resource in the set is less than the maximum number of ports in an SRS resource
among the configured SRS resources, a number of most significant bits with value set to '0' are inserted to the
field.

- Second Precoding information – number of bits determined by the following:

- 0 bits if SRS resource set indicator field is not present;

- 0 bits if the higher layer parameter txConfig = nonCodeBook;

- 0 bits for 1 antenna port and if the higher layer parameter txConfig = codebook;

- 3, 4, or 5 bits according to Table [Link].2-2C with the same number of layers indicated by Precoding
information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present,
txConfig = codebook, ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or
configured to fullpower, transform precoder is disabled, and according to the values of higher layer
parameters maxRank, and codebookSubset;

- 3 or 4 bits according to Table [Link].2-2D with the same number of layers indicated by Precoding
information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present,
txConfig = codebook, ul-FullPowerTransmission = fullpowerMode1, maxRank=2, transform precoder is
disabled, and according to the values of higher layer parameter codebookSubset;

- 3 or 4 bits according to Table [Link].2-2E with the same number of layers indicated by Precoding
information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present,
txConfig = codebook, ul-FullPowerTransmission = fullpowerMode1, maxRank=3 or 4, transform precoder is
disabled, and according to the values of higher layer parameter codebookSubset;

- 2, 4, or 5 bits according to Table [Link].2-3 with the same number of layers indicated by Precoding
information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present,
txConfig = codebook, ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or
configured to fullpower, and according to whether transform precoder is enabled or disabled, and the values
of higher layer parameters maxRank, and codebookSubset;

- 3 or 4 bits according to Table [Link].2-3A with the same number of layers indicated by Precoding
information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present,
txConfig = codebook, ul-FullPowerTransmission = fullpowerMode1, maxRank=1, and according to whether
transform precoder is enabled or disabled, and the values of higher layer parameter codebookSubset;

- 1 or 3 bits according to Table7.[Link]-4B with the same number of layers indicated by Precoding
information and number of layers field for 2 antenna ports, if SRS resource set indicator field is present,
txConfig = codebook, ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or
configured to fullpower, transform precoder is disabled, and according to the values of higher layer
parameters maxRank and codebookSubset;

3GPP
Release 17 136 3GPP TS 38.212 V17.5.0 (2023-03)

codebook, ul-FullPowerTransmission = fullpowerMode1, transform precoder is disabled, maxRank=2, and

codebookSubset=nonCoherent;

- 1 or 3 bits according to Table7.[Link]-5 with the same number of layers indicated by Precoding information
and number of layers field for 2 antenna ports, if SRS resource set indicator field is present, txConfig =
codebook, ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to
fullpower, and according to whether transform precoder is enabled or disabled, and the values of higher layer
parameters maxRank and codebookSubset;

- 2 bits according to Table [Link].2-5A with the same number of layers indicated by Precoding information
and number of layers field for 2 antenna ports, if SRS resource set indicator field is present, txConfig =
codebook, ul-FullPowerTransmission = fullpowerMode1, maxRank=1, and according to whether transform
precoder is enabled or disabled, and the values of higher layer parameter codebookSubset;

For the higher layer parameter txConfig=codebook, if ul-FullPowerTransmission is configured to

fullpowerMode2, maxRank is configured to be larger than 2, and at least one SRS resource with 4 antenna ports
is configured in the SRS resource set indicated by SRS resource set indicator field, and an SRS resource with 2
antenna ports is indicated via Second SRS resource indicator field in the same SRS resource set, then Table
[Link].2-4B is used.

For the higher layer parameter txConfig = codebook, if different SRS resources with different number of antenna
ports are configured, the bitwidth is determined according to the maximum number of ports in an SRS resource
among the configured SRS resources in the second SRS resource set with usage set to 'codebook' as defined in
Table [Link].2-36. If the number of ports for a configured SRS resource in the set is less than the maximum
number of ports in an SRS resource among the configured SRS resources, a number of most significant bits with
value set to '0' are inserted to the field.

- Antenna ports – number of bits determined by the following

- 2 bits as defined by Tables [Link].2-6, if transform precoder is enabled, dmrs-Type=1, and maxLength=1,
except that dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured and π/2 BPSK modulation
is used;

- 2 bits as defined by Tables [Link].2-6A, if transform precoder is enabled and dmrs-

UplinkTransformPrecoding and tp-pi2BPSK are both configured, π/2 BPSK modulation is used, dmrs-
Type=1, and maxLength=1, where nSCID is the scrambling identity for antenna ports defined in [Clause
[Link].1.2, TS38.211];

- 4 bits as defined by Tables [Link].2-7, if transform precoder is enabled, dmrs-Type=1, and maxLength=2,
except that dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured and π/2 BPSK modulation
is used;

- 4 bits as defined by Tables [Link].2-7A, if transform precoder is enabled and dmrs-

UplinkTransformPrecoding and tp-pi2BPSK are both configured, π/2 BPSK modulation is used, dmrs-
Type=1, and maxLength=2, where nSCID is the scrambling identity for antenna ports defined in [Clause
[Link].1.2, TS38.211];

- 3 bits as defined by Tables [Link].2-8/9/10/11, if transform precoder is disabled, dmrs-Type=1, and

maxLength=1, and the value of rank is determined according to the SRS resource indicator field if the higher
layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers
field if the higher layer parameter txConfig = codebook;

- 4 bits as defined by Tables [Link].2-12/13/14/15, if transform precoder is disabled, dmrs-Type=1, and

maxLength=2, and the value of rank is determined according to the SRS resource indicator field if the higher
layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers
field if the higher layer parameter txConfig = codebook;

- 4 bits as defined by Tables [Link].2-16/17/18/19, if transform precoder is disabled, dmrs-Type=2, and

- 5 bits as defined by Tables [Link].2-20/21/22/23, if transform precoder is disabled, dmrs-Type=2, and

maxLength=2, and the value of rank is determined according to the SRS resource indicator field if the higher

3GPP
Release 17 137 3GPP TS 38.212 V17.5.0 (2023-03)

layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers
field if the higher layer parameter txConfig = codebook.

where the number of CDM groups without data of values 1, 2, and 3 in Tables [Link].2-6 to [Link].2-23 refers
to CDM groups {0}, {0,1}, and {0, 1,2} respectively.

If a UE is configured with both dmrs-UplinkForPUSCH-MappingTypeA and dmrs-UplinkForPUSCH-

MappingTypeB, the bitwidth of this field equals , where is the "Antenna ports" bitwidth
derived according to dmrs-UplinkForPUSCH-MappingTypeA and is the "Antenna ports" bitwidth derived

according to dmrs-UplinkForPUSCH-MappingTypeB. A number of zeros are padded in the MSB of

this field, if the mapping type of the PUSCH corresponds to the smaller value of and .

- SRS request – 2 bits as defined by Table [Link].2-24 for UEs not configured with supplementaryUplink in
ServingCellConfig in the cell; 3 bits for UEs configured with supplementaryUplink in ServingCellConfig in the
cell where the first bit is the non-SUL/SUL indicator as defined in Table [Link].1-1 and the second and third bits
are defined by Table [Link].2-24. This bit field may also indicate the associated CSI-RS according to Clause
[Link] of [6, TS 38.214].

- SRS offset indicator – 0, 1 or 2 bits.

- 0 bit if higher layer parameter AvailableSlotOffset is not configured for any aperiodic SRS resource set in the
scheduled cell, or if higher layer parameter AvailableSlotOffset is configured for at least one aperiodic SRS
resource set in the scheduled cell and the maximum number of entries of availableSlotOffsetList configured
for all aperiodic SRS resource set(s) is 1;

- otherwise, ⌈ log 2 (K )⌉ bits are used to indicate available slot offset according to Table [Link].2-37 and
Clause 6.2.1 of [6, TS 38.214], where K is the maximum number of entries of availableSlotOffsetList
configured for all aperiodic SRS resource set(s) in the scheduled cell;

- CSI request – 0, 1, 2, 3, 4, 5, or 6 bits determined by higher layer parameter reportTriggerSize.

- CBG transmission information (CBGTI) – 0 bit if higher layer parameter codeBlockGroupTransmission for
PUSCH is not configured or if the number of scheduled PUSCH indicated by the Time domain resource
assignment field is larger than 1; otherwise, 2, 4, 6, or 8 bits determined by higher layer parameter
maxCodeBlockGroupsPerTransportBlock for PUSCH.

- PTRS-DMRS association – number of bits determined as follows

- 0 bit if PTRS-UplinkConfig is not configured in either dmrs-UplinkForPUSCH-MappingTypeA or dmrs-

UplinkForPUSCH-MappingTypeB and transform precoder is disabled, or if transform precoder is enabled, or
if maxRank=1;

- 2 bits otherwise, where Table [Link].2-25/[Link].2-25A and [Link].2-26 are used to indicate the association
between PTRS port(s) and DMRS port(s) when one PT-RS port and two PT-RS ports are configured by
maxNrofPorts in PTRS-UplinkConfig respectively, and the DMRS ports are indicated by the Antenna ports
field. When the SRS resource set indicator field is present and maxRank>2, this field indicates the
association between PTRS port(s) and DMRS port(s) corresponding to SRS resource indicator field and/or
Precoding information and number of layers field according to Table [Link].2-25 and [Link].2-26. When the
SRS resource set indicator field is present and equals "10" and "11" and maxRank=2, the MSB of this field
indicates the association between PTRS port(s) and DMRS port(s) corresponding to SRS resource indicator
and/or Precoding information and number of layers field, and the LSB of this field indicates the association
between PTRS port(s) and DMRS port(s) corresponding to Second SRS resource indicator field and/or
Second Precoding information field, according to Table [Link].2-25A.

If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and the
"PTRS-DMRS association" field is present for the indicated bandwidth part but not present for the active
bandwidth part, the UE assumes the "PTRS-DMRS association" field is not present for the indicated bandwidth
part.

- Second PTRS-DMRS association – 2 bits if PTRS-DMRS association field and SRS resource set indicator field
are present and maxRank>2; 0 bit otherwise. Table [Link].2-25 and [Link].2-26 are used to indicate the

3GPP
Release 17 138 3GPP TS 38.212 V17.5.0 (2023-03)

association between PTRS port(s) and DMRS port(s) corresponding to Second SRS resource indicator field
and/or Second precoding information field when one PT-RS port and two PT-RS ports are configured by
maxNrofPorts in PTRS-UplinkConfig respectively, and the DMRS ports are indicated by the Antenna ports
field.

- beta_offset indicator – 0 if the higher layer parameter betaOffsets = semiStatic; otherwise 2 bits as defined by
Table 9.3-3 in [5, TS 38.213].

When two HARQ-ACK codebooks are configured by pdsch-HARQ-ACK-CodebookList or by pdsch-HARQ-

ACK-CodebookListMulticast for the same serving cell and if higher layer parameter priorityIndicatorDCI-0-1 is
configured, if the bit width of the beta_offset indicator in DCI format 0_1 for one HARQ-ACK codebook is not
equal to that of the beta_offset indicator in DCI format 0_1 for the other HARQ-ACK codebook, a number of
most significant bits with value set to '0' are inserted to smaller beta_offset indicator until the bit width of the
beta_offset indicator in DCI format 0_1 for the two HARQ-ACK codebooks are the same.

- DMRS sequence initialization – 0 bit if transform precoder is enabled; 1 bit if transform precoder is disabled.

- UL-SCH indicator – 0 or 1 bit as follows

- 0 bit if the number of scheduled PUSCH indicated by the Time domain resource assignment field is larger
than 1;

- 1 bit otherwise. A value of "1" indicates UL-SCH shall be transmitted on the PUSCH and a value of "0"
indicates UL-SCH shall not be transmitted on the PUSCH. If a UE does not support triggering SRS only in
DCI, except for DCI format 0_1 with CRC scrambled by SP-CSI-RNTI, the UE is not expected to receive a
DCI format 0_1 with UL-SCH indicator of "0" and CSI request of all zero(s). If a UE supports triggering
SRS only in DCI, except for DCI format 0_1 with CRC scrambled by SP-CSI-RNTI, the UE is not expected
to receive a DCI format 0_1 with UL-SCH indicator of "0", CSI request of all zero(s) and SRS request of all
zero(s).

- ChannelAccess-CPext-CAPC – 0, 1, 2, 3, 4, 5 or 6 bits. The bitwidth for this field is determined as ⌈ log 2 (I ) ⌉

bits, where I is the number of entries in the higher layer parameter ul-AccessConfigListDCI-0-1 or in Table
[Link].1-4A if channelAccessMode-r16 = "semiStatic" is provided, for operation in a cell with shared spectrum
channel access in frequency range 1, or for operation in frequency range 2-2 if ChannelAccessMode2-r17 is
provided; otherwise 0 bit. One or more entries from Table [Link].2-35 or Table [Link].2-35A are configured by
the higher layer parameter ul-AccessConfigListDCI-0-1.

- Open-loop power control parameter set indication – 0 or 1 or 2 bits.

- 0 bit if the higher layer parameter p0-PUSCH-SetList is not configured;

- 1 or 2 bits otherwise,

- 1 bit if SRS resource indicator is present in the DCI format 0_1;

- 1 or 2 bits as determined by higher layer parameter olpc-ParameterSetDCI-0-1 if SRS resource indicator

is not present in the DCI format 0_1.

- Priority indicator – 0 bit if higher layer parameter priorityIndicatorDCI-0-1 is not configured; otherwise 1 bit as
defined in Clause 9 in [5, TS 38.213].

- Invalid symbol pattern indicator – 0 bit if higher layer parameter invalidSymbolPatternIndicatorDCI-0-1 is not
configured; otherwise 1 bit as defined in Clause [Link] in [6, TS 38.214].

- Minimum applicable scheduling offset indicator – 0 or 1 bit

- 0 bit if higher layer parameter minimumSchedulingOffsetK2 is not configured;

- 1 bit if higher layer parameter minimumSchedulingOffsetK2 is configured. The 1 bit indication is used to
determine the minimum applicable K2 for the active UL BWP and the minimum applicable K0 value for the
active DL BWP, if configured respectively, according to Table [Link].2-33. If the minimum applicable K0 is
indicated, the minimum applicable value of the aperiodic CSI-RS triggering offset for an active DL BWP
shall be the same as the minimum applicable K0 value.

3GPP
Release 17 139 3GPP TS 38.212 V17.5.0 (2023-03)

- SCell dormancy indication – 0 bit if higher layer parameter dormancyGroupWithinActiveTime is not configured;
otherwise 1, 2, 3, 4 or 5 bits bitmap determined according to the number of different DormancyGroupID(s)
provided by higher layer parameter dormancyGroupWithinActiveTime, where each bit corresponds to one of the
SCell group(s) configured by higher layers parameter dormancyGroupWithinActiveTime, with MSB to LSB of
the bitmap corresponding to the first to last configured SCell group in ascending order of DormancyGroupID.
The field is only present when this format is carried by PDCCH on the primary cell within DRX Active Time
and the UE is configured with at least two DL BWPs for an SCell.

- Sidelink assignment index – 0, 1 or 2 bits:

- 1 bit if the UE is configured with pdsch-HARQ-ACK-Codebook = semi-static and, in addition, the UE is

configured with a SL configured grant type 1 or to monitor DCI format 3_0 with CRC scrambled by SL-
RNTI or SL-CS-RNTI;

- 2 bits if the UE is configured with pdsch-HARQ-ACK-Codebook = dynamic and, in addition, the UE is

configured with a SL configured grant type 1 or to monitor DCI format 3_0 with CRC scrambled by SL-
RNTI or SL-CS-RNTI;

- 0 bit otherwise.

- PDCCH monitoring adaptation indication – 0, 1 or 2 bits

- 1 or 2 bits, if searchSpaceGroupIdList-r17 is not configured and if pdcch-SkippingDurationList is configured

- 1 bit if the UE is configured with only one duration by pdcch-SkippingDurationList;

- 2 bits if the UE is configured with more than one duration by pdcch-SkippingDurationList.

- 1 or 2 bits, if pdcch-SkippingDurationList is not configured and if searchSpaceGroupIdList-r17 is configured

- 1 bit if the UE is configured by searchSpaceGroupIdList-r17 with search space set(s) with group index 0
and search space set(s) with group index 1, and if the UE is not configured by searchSpaceGroupIdList-
r17 with any search space set with group index 2;

- 2 bits if the UE is configured by searchSpaceGroupIdList-r17 with search space set(s) with group index
0, search space set(s) with group index 1 and search space set(s) with group index 2;

- 2 bits, if pdcch-SkippingDurationList is configured and if searchSpaceGroupIdList-r17 is configured

- 0 bit, otherwise

A UE does not expect that the bit width of a field in DCI format 0_1 with CRC scrambled by CS-RNTI is larger than
corresponding bit width of same field in DCI format 0_1 with CRC scrambled by C-RNTI for the same serving cell. If
the bit width of a field in the DCI format 0_1 with CRC scrambled by CS-RNTI is not equal to that of the
corresponding field in the DCI format 0_1 with CRC scrambled by C-RNTI for the same serving cell, a number of most
significant bits with value set to '0' are inserted to the field in DCI format 0_1 with CRC scrambled by CS-RNTI until
the bit width equals that of the corresponding field in the DCI format 0_1 with CRC scrambled by C-RNTI for the same
serving cell.

If the number of information bits in DCI format 0_1 scheduling a single PUSCH prior to padding is not equal to the
number of information bits in DCI format 0_1 scheduling multiple PUSCHs for the same serving cell, zeros shall be
appended to the DCI format 0_1 with smaller size until the payload size is the same for scheduling a single PUSCH and
multiple PUSCHs.

For a UE configured with scheduling on the primary cell from an SCell, if prior to padding the number of information
bits in DCI format 0_1 carried by PDCCH on the primary cell is not equal to the number of information bits in DCI
format 0_1 carried by PDCCH on the SCell for scheduling on the primary cell, zeros shall be appended to the DCI
format 0_1 with smaller size until the payload size is the same.

- If application of step 4C in clause [Link] results in additional zero padding for DCI format 0_1 for scheduling
on the primary cell, corresponding zeros shall be appended to both DCI format 0_1 monitored on the primary
cell and DCI format 0_1 monitored on the SCell for scheduling on the primary cell.

- If the SCell is deactivated and firstActiveDownlinkBWP-Id is not set to dormant BWP, the UE determines the
number of information bits in DCI format 0_1 carried by PDCCH on the primary cell based on a DL BWP

3GPP
Release 17 140 3GPP TS 38.212 V17.5.0 (2023-03)

provided by firstActiveDownlinkBWP-Id for the SCell. If the active DL BWP of the SCell is a dormant DL
BWP, or if the SCell is deactivated and firstActiveDownlinkBWP-Id is set to dormant BWP, the UE determines
the number of information bits in DCI format 0_1 carried by PDCCH on the primary cell based on a DL BWP
provided by firstWithinActiveTimeBWP-Id for the SCell if provided; otherwise, based on a DL BWP provided by
firstOutsideActiveTimeBWP-Id for the SCell.

Table [Link].2-1: Bandwidth part indicator

Value of BWP indicator field

Bandwidth part
2 bits
00 Configured BWP with BWP-Id = 1
01 Configured BWP with BWP-Id = 2
10 Configured BWP with BWP-Id = 3
11 Configured BWP with BWP-Id = 4

Table [Link].2-2: Precoding information and number of layers, for 4 antenna ports, if transform
precoder is disabled, maxRank = 2 or 3 or 4, and ul-FullPowerTransmission is not configured or
configured to fullpowerMode2 or configured to fullpower

Bit field codebookSubset = Bit field codebookSubset = Bit field

codebookSubset=
mapped fullyAndPartialAndNonCoheren mapped partialAndNonCoheren mapped
nonCoherent
to index t to index t to index
0 1 layer: TPMI=0 0 1 layer: TPMI=0 0 1 layer: TPMI=0
1 1 layer: TPMI=1 1 1 layer: TPMI=1 1 1 layer: TPMI=1
… … … … … …
3 1 layer: TPMI=3 3 1 layer: TPMI=3 3 1 layer: TPMI=3
4 2 layers: TPMI=0 4 2 layers: TPMI=0 4 2 layers: TPMI=0
… … … … … …
9 2 layers: TPMI=5 9 2 layers: TPMI=5 9 2 layers: TPMI=5
10 3 layers: TPMI=0 10 3 layers: TPMI=0 10 3 layers: TPMI=0
11 4 layers: TPMI=0 11 4 layers: TPMI=0 11 4 layers: TPMI=0
12 1 layer: TPMI=4 12 1 layer: TPMI=4 12-15 reserved
… … … …
19 1 layer: TPMI=11 19 1 layer: TPMI=11
20 2 layers: TPMI=6 20 2 layers: TPMI=6
… … … …
27 2 layers: TPMI=13 27 2 layers: TPMI=13
28 3 layers: TPMI=1 28 3 layers: TPMI=1
29 3 layers: TPMI=2 29 3 layers: TPMI=2
30 4 layers: TPMI=1 30 4 layers: TPMI=1
31 4 layers: TPMI=2 31 4 layers: TPMI=2
32 1 layers: TPMI=12
… …
47 1 layers: TPMI=27
48 2 layers: TPMI=14
… …
55 2 layers: TPMI=21
56 3 layers: TPMI=3
… …
59 3 layers: TPMI=6
60 4 layers: TPMI=3
61 4 layers: TPMI=4
62-63 reserved

3GPP
Release 17 141 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-2A: Precoding information and number of layers for 4 antenna ports, if transform
precoder is disabled, maxRank = 2, and ul-FullPowerTransmission = fullpowerMode1

Bit field codebookSubset = Bit field

codebookSubset=
mapped partialAndNonCoheren mapped
nonCoherent
to index t to index
0 1 layer: TPMI=0 0 1 layer: TPMI=0
1 1 layer: TPMI=1 1 1 layer: TPMI=1
… … … …
3 1 layer: TPMI=3 3 1 layer: TPMI=3
4 2 layers: TPMI=0 4 2 layers: TPMI=0
… … … …
9 2 layers: TPMI=5 9 2 layers: TPMI=5
10 1 layer: TPMI=13 10 1 layer: TPMI=13
11 2 layer: TPMI=6 11 2 layer: TPMI=6
12 1 layer: TPMI=4 12-15 Reserved
… …
20 1 layer: TPMI=12
21 1 layer: TPMI=14
22 1 layer: TPMI=15
23 2 layers: TPMI=7
… …
29 2 layers: TPMI=13
30-31 Reserved

Table [Link].2-2B: Precoding information and number of layers for 4 antenna ports, if transform
precoder is disabled, maxRank = 3 or 4, and ul-FullPowerTransmission = fullpowerMode1

Bit field codebookSubset = Bit field

codebookSubset=
mapped partialAndNonCoheren mapped
nonCoherent
to index t to index
0 1 layer: TPMI=0 0 1 layer: TPMI=0
1 1 layer: TPMI=1 1 1 layer: TPMI=1
… … … …
3 1 layer: TPMI=3 3 1 layer: TPMI=3
4 2 layers: TPMI=0 4 2 layers: TPMI=0
… … … …
9 2 layers: TPMI=5 9 2 layers: TPMI=5
10 3 layers: TPMI=0 10 3 layers: TPMI=0
11 4 layers: TPMI=0 11 4 layers: TPMI=0
12 1 layer: TPMI=13 12 1 layer: TPMI=13
13 2 layer: TPMI=6 13 2 layer: TPMI=6
14 3 layer: TPMI=1 14 3 layer: TPMI=1
15 1 layer: TPMI=4 15 Reserved
… …
23 1 layer: TPMI=12
24 1 layer: TPMI=14
25 1 layer: TPMI=15
26 2 layers: TPMI=7
… …
32 2 layers: TPMI=13
33 3 layers: TPMI=2
34 4 layers: TPMI=1
35 4 layers: TPMI=2
36-63 Reserved

3GPP
Release 17 142 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-2C: Second precoding information, for 4 antenna ports, if transform precoder is
disabled, maxRank = 2 or 3 or 4, and ul-FullPowerTransmission is not configured or configured to
fullpowerMode2 or configured to fullpower

Bit field codebookSubset = Bit field codebookSubset = Bit field

codebookSubset=
mapped fullyAndPartialAndNonCoheren mapped partialAndNonCoheren mapped
nonCoherent
to index t to index t to index
0 1 layer: TPMI=0 0 1 layer: TPMI=0 0 1 layer: TPMI=0
… … … … … …
27 1 layer: TPMI=27 11 1 layer: TPMI=11 3 1 layer: TPMI=3
28-31 1 layer: reserved 12-15 1 layer: reserved 4-7 1 layer: reserved
0 2 layers: TPMI=0 0 2 layers: TPMI=0 0 2 layers: TPMI=0
… … … … … …
21 2 layers: TPMI=21 13 2 layers: TPMI=13 5 2 layers: TPMI=5
22-31 2 layers: reserved 14-15 2 layers: reserved 6-7 2 layers: reserved
0 3 layers: TPMI=0 0 3 layers: TPMI=0 0 3 layers: TPMI=0
… … … … 1-7 3 layers: reserved
6 3 layers: TPMI=6 2 3 layers: TPMI=2 0 4 layers: TPMI=0
7-31 3 layers: reserved 3-15 3 layers: reserved 1-7 4 layers: reserved
0 4 layers: TPMI=0 0 4 layers: TPMI=0
… … … …
4 4 layers: TPMI=4 2 4 layers: TPMI=2
5-31 4 layers: reserved 3-15 4 layers: reserved

Table [Link].2-2D: Second precoding information for 4 antenna ports, if transform precoder is
disabled, maxRank = 2, and ul-FullPowerTransmission = fullpowerMode1

Bit field codebookSubset = Bit field

Table [Link].2-2E: Second precoding information for 4 antenna ports, if transform precoder is
disabled, maxRank = 3 or 4, and ul-FullPowerTransmission = fullpowerMode1

Bit field codebookSubset = Bit field

codebookSubset=
mapped partialAndNonCoheren mapped
nonCoherent
to index t to index
0 1 layer: TPMI=0 0 1 layer: TPMI=0
… … … …
14 1 layer: TPMI=14 3 1 layer: TPMI=3
15 1 layer: TPMI=15 4 1 layer: TPMI=13
0 2 layers: TPMI=0 5-7 1 layer: reserved
… … 0 2 layers: TPMI=0
13 2 layers: TPMI=13 … …
14-15 2 layers: reserved 6 2 layers: TPMI=6
0 3 layers: TPMI=0 7 2 layers: reserved
… … 0 3 layers: TPMI=0
2 3 layers: TPMI=2 1 3 layer: TPMI=1
3-15 3 layers: reserved 2-7 3 layers: reserved
0 4 layers: TPMI=0 0 4 layers: TPMI=0
… … 1-7 4 layers: reserved
2 4 layers: TPMI=2
3-15 4 layers: reserved

3GPP
Release 17 143 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-3: Precoding information and number of layers or Second Precoding information, for 4
antenna ports, if transform precoder is enabled and ul-FullPowerTransmission is either not
configured or configured to fullpowerMode2 or configured to fullpower, or if transform precoder is
disabled, maxRank = 1, and ul-FullPowerTransmission is not configured or configured to
fullpowerMode2 or configured to fullpower

Bit field codebookSubset = Bit field codebookSubset= Bit field

Table [Link].2-3A: Precoding information and number of layers or Second Precoding information, for
4 antenna ports, if transform precoder is enabled and ul-FullPowerTransmission = fullpowerMode1,
or if transform precoder is disabled, maxRank = 1, and ul-FullPowerTransmission = fullpowerMode1

Bit field codebookSubset= Bit field

Table [Link].2-4: Precoding information and number of layers, for 2 antenna ports, if transform
precoder is disabled, maxRank = 2, and ul-FullPowerTransmission is not configured or configured to
fullpowerMode2 or configured to fullpower

Bit field
codebookSubset = Bit field
mappe
fullyAndPartialAndNonCoheren mapped codebookSubset = nonCoherent
d to
t to index
index
0 1 layer: TPMI=0 0 1 layer: TPMI=0
1 1 layer: TPMI=1 1 1 layer: TPMI=1
2 2 layers: TPMI=0 2 2 layers: TPMI=0
3 1 layer: TPMI=2 3 reserved
4 1 layer: TPMI=3
5 1 layer: TPMI=4
6 1 layer: TPMI=5
7 2 layers: TPMI=1
8 2 layers: TPMI=2
9-15 reserved

3GPP
Release 17 144 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-4A: Precoding information and number of layers, for 2 antenna ports, if transform
precoder is disabled, maxRank = 2, and ul-FullPowerTransmission = fullpowerMode1

Bit field mapped to

codebookSubset= nonCoherent
index
0 1 layer: TPMI=0
1 1 layer: TPMI=1
2 2 layers: TPMI=0
3 1 layer: TPMI=2

Table [Link].2-4B: Second precoding information, for 2 antenna ports, if transform precoder is
disabled, maxRank = 2, and ul-FullPowerTransmission is not configured or configured to
fullpowerMode2 or configured to fullpower

Bit field
codebookSubset = Bit field
mappe
fullyAndPartialAndNonCoheren mapped codebookSubset = nonCoherent
d to
t to index
index
0 1 layer: TPMI=0 0 1 layer: TPMI=0
1 1 layer: TPMI=1 1 1 layer: TPMI=1
… … 0 2 layers: TPMI=0
5 1 layer: TPMI=5 1 2 layers: reserved
6-7 1 layer: reserved
0 2 layers: TPMI=0
… …
2 2 layers: TPMI=2
3-7 2 layers: reserved

Table [Link].2-4C: Second precoding information, for 2 antenna ports, if transform precoder is
disabled, maxRank = 2, and ul-FullPowerTransmission = fullpowerMode1

Bit field mapped to

codebookSubset= nonCoherent
index
0 1 layer: TPMI=0
… …
2 1 layer: TPMI=2
3 1 layer: reserved
0 2 layers: TPMI=0
1-3 2 layers: reserved

Table [Link].2-5: Precoding information and number of layers or Second Precoding information, for 2
antenna ports, if transform precoder is enabled and ul-FullPowerTransmission is not configured or
configured to fullpowerMode2 or configured to fullpower, or if transform precoder is disabled,
maxRank = 1, and and ul-FullPowerTransmission is not configured or configured to fullpowerMode2
or configured to fullpower

Bit field codebookSubset = Bit field

codebookSubset =
mapped fullyAndPartialAndNonCoheren mapped
nonCoherent
to index t to index
0 1 layer: TPMI=0 0 1 layer: TPMI=0
1 1 layer: TPMI=1 1 1 layer: TPMI=1
2 1 layer: TPMI=2
3 1 layer: TPMI=3
4 1 layer: TPMI=4
5 1 layer: TPMI=5
6-7 reserved

3GPP
Release 17 145 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-5A: Precoding information and number of layers, for 2 antenna ports or Second
Precoding information, if transform precoder is enabled and ul-FullPowerTransmission =
fullpowerMode1, or if transform precoder is disabled, maxRank = 1, and ul-FullPowerTransmission =
fullpowerMode1

Bit field mapped to

codebookSubset= nonCoherent
index
0 1 layer: TPMI=0
1 1 layer: TPMI=1
2 1 layer: TPMI=2
3 Reserved

Table [Link].2-6: Antenna port(s), transform precoder is enabled, dmrs-Type=1, maxLength=1,

except that dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured and π/2-BPSK
modulation is used
Number of DMRS
DMRS
Value CDM group(s)
port(s)
without data
0 2 0
1 2 1
2 2 2
3 2 3

Table [Link].2-6A: Antenna port(s), transform precoder is enabled, dmrs-UplinkTransformPrecoding

and tp-pi2BPSK are both configured, π/2-BPSK modulation is used, dmrs-Type=1, maxLength=1
Number of DMRS
DMRS
Value CDM group(s)
port(s)
without data
0 2 0, nSCID= 0
1 2 0, nSCID= 1
2 2 2, nSCID= 0
3 2 2, nSCID= 1

Table [Link].2-7: Antenna port(s), transform precoder is enabled, dmrs-Type=1, maxLength=2,

except that dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured and π/2-BPSK
modulation is used
Valu Number of DMRS CDM group(s) without
DMRS port(s) Number of front-load symbols
e data
0 2 0 1
1 2 1 1
2 2 2 1
3 2 3 1
4 2 0 2
5 2 1 2
6 2 2 2
7 2 3 2
8 2 4 2
9 2 5 2
10 2 6 2
11 2 7 2
12-15 Reserved Reserved Reserved

3GPP
Release 17 146 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-7A: Antenna port(s), transform precoder is enabled, dmrs-UplinkTransformPrecoding

and tp-pi2BPSK are both configured, π/2-BPSK modulation is used, dmrs-Type=1, maxLength=2
Valu Number of DMRS CDM group(s) without
DMRS port(s) Number of front-load symbols
e data
0 2 0, nSCID= 0 1
1 2 0, nSCID= 1 1
2 2 2, nSCID= 0 1
3 2 2, nSCID= 1 1
4 2 0, nSCID= 0 2
5 2 0, nSCID= 1 2
6 2 2, nSCID= 0 2
7 2 2, nSCID= 1 2
8 2 4, nSCID= 0 2
9 2 4, nSCID= 1 2
10 2 6, nSCID= 0 2
11 2 6, nSCID= 1 2
12-15 Reserved Reserved Reserved

Table [Link].2-8: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=1, rank
=1
Valu
Number of DMRS CDM group(s) without data DMRS port(s)
e
0 1 0
1 1 1
2 2 0
3 2 1
4 2 2
5 2 3
6-7 Reserved Reserved

Table [Link].2-9: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=1, rank
=2
Valu
Number of DMRS CDM group(s) without data DMRS port(s)
e
0 1 0,1
1 2 0,1
2 2 2,3
3 2 0,2
4-7 Reserved Reserved

Table [Link].2-10: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=1, rank
=3
Valu
Number of DMRS CDM group(s) without data DMRS port(s)
e
0 2 0-2
1-7 Reserved Reserved

Table [Link].2-11: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=1, rank
=4
Valu
Number of DMRS CDM group(s) without data DMRS port(s)
e
0 2 0-3
1-7 Reserved Reserved

3GPP
Release 17 147 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-12: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=2, rank
=1
Valu Number of DMRS CDM group(s) without
DMRS port(s) Number of front-load symbols
e data
0 1 0 1
1 1 1 1
2 2 0 1
3 2 1 1
4 2 2 1
5 2 3 1
6 2 0 2
7 2 1 2
8 2 2 2
9 2 3 2
10 2 4 2
11 2 5 2
12 2 6 2
13 2 7 2
14-15 Reserved Reserved Reserved

Table [Link].2-13: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=2, rank
=2
Valu Number of DMRS CDM group(s) without
DMRS port(s) Number of front-load symbols
e data
0 1 0,1 1
1 2 0,1 1
2 2 2,3 1
3 2 0,2 1
4 2 0,1 2
5 2 2,3 2
6 2 4,5 2
7 2 6,7 2
8 2 0,4 2
9 2 2,6 2
10-15 Reserved Reserved Reserved

Table [Link].2-14: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=2, rank
=3
Valu Number of DMRS CDM group(s) without
DMRS port(s) Number of front-load symbols
e data
0 2 0-2 1
1 2 0,1,4 2
2 2 2,3,6 2
3-15 Reserved Reserved Reserved

Table [Link].2-15: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=2, rank
=4
Valu Number of DMRS CDM group(s) without
DMRS port(s) Number of front-load symbols
e data
0 2 0-3 1
1 2 0,1,4,5 2
2 2 2,3,6,7 2
3 2 0,2,4,6 2
4-15 Reserved Reserved Reserved

3GPP
Release 17 148 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-16: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=1,

rank=1
Valu
Number of DMRS CDM group(s) without data DMRS port(s)
e
0 1 0
1 1 1
2 2 0
3 2 1
4 2 2
5 2 3
6 3 0
7 3 1
8 3 2
9 3 3
10 3 4
11 3 5
12-15 Reserved Reserved

Table [Link].2-17: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=1,

rank=2
Valu
Number of DMRS CDM group(s) without data DMRS port(s)
e
0 1 0,1
1 2 0,1
2 2 2,3
3 3 0,1
4 3 2,3
5 3 4,5
6 2 0,2
7-15 Reserved Reserved

Table [Link].2-18: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=1, rank
=3
Valu
Number of DMRS CDM group(s) without data DMRS port(s)
e
0 2 0-2
1 3 0-2
2 3 3-5
3-15 Reserved Reserved

Table [Link].2-19: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=1, rank
=4
Valu
Number of DMRS CDM group(s) without data DMRS port(s)
e
0 2 0-3
1 3 0-3
2-15 Reserved Reserved

3GPP
Release 17 149 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-20: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=2,

rank=1
Valu Number of DMRS CDM group(s) without
DMRS port(s) Number of front-load symbols
e data
0 1 0 1
1 1 1 1
2 2 0 1
3 2 1 1
4 2 2 1
5 2 3 1
6 3 0 1
7 3 1 1
8 3 2 1
9 3 3 1
10 3 4 1
11 3 5 1
12 3 0 2
13 3 1 2
14 3 2 2
15 3 3 2
16 3 4 2
17 3 5 2
18 3 6 2
19 3 7 2
20 3 8 2
21 3 9 2
22 3 10 2
23 3 11 2
24 1 0 2
25 1 1 2
26 1 6 2
27 1 7 2
28-31 Reserved Reserved Reserved

Table [Link].2-21: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=2,

rank=2
Valu Number of DMRS CDM group(s) without
DMRS port(s) Number of front-load symbols
e data
0 1 0,1 1
1 2 0,1 1
2 2 2,3 1
3 3 0,1 1
4 3 2,3 1
5 3 4,5 1
6 2 0,2 1
7 3 0,1 2
8 3 2,3 2
9 3 4,5 2
10 3 6,7 2
11 3 8,9 2
12 3 10,11 2
13 1 0,1 2
14 1 6,7 2
15 2 0,1 2
16 2 2,3 2
17 2 6,7 2
18 2 8,9 2
19-31 Reserved Reserved Reserved

3GPP
Release 17 150 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-22: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=2,

rank=3
Valu Number of DMRS CDM group(s) without
DMRS port(s) Number of front-load symbols
e data
0 2 0-2 1
1 3 0-2 1
2 3 3-5 1
3 3 0,1,6 2
4 3 2,3,8 2
5 3 4,5,10 2
6-31 Reserved Reserved Reserved

Table [Link].2-23: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=2,

rank=4
Valu Number of DMRS CDM group(s) without
DMRS port(s) Number of front-load symbols
e data
0 2 0-3 1
1 3 0-3 1
2 3 0,1,6,7 2
3 3 2,3,8,9 2
4 3 4,5,10,11 2
5-31 Reserved Reserved Reserved

3GPP
Release 17 151 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-24: SRS request

Triggered aperiodic SRS resource Triggered aperiodic SRS resource set(s) for DCI
set(s) for DCI format 0_1, 0_2, 1_1, format 2_3 configured with higher layer
Value of SRS request
1_2, and 2_3 configured with higher parameter srs-TPC-PDCCH-Group set to 'typeA'
field
layer parameter srs-TPC-PDCCH-
Group set to 'typeB'
No aperiodic SRS resource set No aperiodic SRS resource set triggered
00
triggered
SRS resource set(s) configured by SRS resource set(s) configured with higher layer
SRS-ResourceSet with higher layer parameter usage in SRS-ResourceSet set to
parameter aperiodicSRS- 'antennaSwitching' and resourceType in SRS-
ResourceTrigger set to 1 or an entry in ResourceSet set to 'aperiodic' for a 1st set of serving
aperiodicSRS-ResourceTriggerList set cells configured by higher layers
to 1
01
SRS resource set(s) configured by
SRS-PosResourceSet with an entry in
aperiodicSRS-ResourceTriggerList set
to 1 when triggered by DCI formats 0_1,
0_2, 1_1, and 1_2
SRS resource set(s) configured by SRS resource set(s) configured with higher layer
SRS-ResourceSet with higher layer parameter usage in SRS-ResourceSet set to
parameter aperiodicSRS- 'antennaSwitching' and resourceType in SRS-
ResourceTrigger set to 2 or an entry in ResourceSet set to 'aperiodic' for a 2nd set of
aperiodicSRS-ResourceTriggerList set serving cells configured by higher layers
to 2
10
SRS resource set(s) configured by
SRS-PosResourceSet with an entry in
aperiodicSRS-ResourceTriggerList set
to 2 when triggered by DCI formats 0_1,
0_2, 1_1, and 1_2
SRS resource set(s) configured by SRS resource set(s) configured with higher layer
SRS-ResourceSet with higher layer parameter usage in SRS-ResourceSet set to
parameter aperiodicSRS- 'antennaSwitching' and resourceType in SRS-
ResourceTrigger set to 3 or an entry in ResourceSet set to 'aperiodic' for a 3rd set of
aperiodicSRS-ResourceTriggerList set serving cells configured by higher layers
to 3
11
SRS resource set(s) configured by
SRS-PosResourceSet with an entry in
aperiodicSRS-ResourceTriggerList set
to 3 when triggered by DCI formats 0_1,
0_2, 1_1, and 1_2

Table [Link].2-25: PTRS-DMRS association or Second PTRS-DMRS association for UL PTRS port 0

Value DMRS port

st
0 1 scheduled DMRS port
1 2nd scheduled DMRS port
2 3rd scheduled DMRS port
3 4th scheduled DMRS port

Table [Link].2-25A: PTRS-DMRS association for UL PTRS port 0 or for the actual UL PT-RS port

Value of MSB DMRS port Value of LSB DMRS port

st
1 scheduled DMRS port corresponding
1st scheduled DMRS port corresponding to
to SRS resource indicator field and/or
0 0 Second SRS resource indicator field and/or
Precoding information and number of
Second Precoding information field
layers field
2nd scheduled DMRS port
2nd scheduled DMRS port corresponding
corresponding to SRS resource indicator
1 1 to Second SRS resource indicator field
field and/or Precoding information and
and/or Second Precoding information field
number of layers field

3GPP
Release 17 152 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-26: PTRS-DMRS association or Second PTRS-DMRS association for UL PTRS ports 0
and 1

Value of MSB DMRS port Value of LSB DMRS port

1st DMRS port which shares 1st DMRS port which shares
0 0
PTRS port 0 PTRS port 1
2nd DMRS port which shares 2nd DMRS port which shares
1 1
PTRS port 0 PTRS port 1

Table [Link].2-27: void

Table [Link].2-28: SRI indication or Second SRI indication, for non-codebook based PUSCH
transmission,
Lmax =1

Bit field Bit field Bit field

mapped to N =2
SRI(s), SRS mapped to N =3
SRI(s), SRS mapped to SRI(s),
N SRS=4
index index index
0 0 0 0 0 0
1 1 1 1 1 1
2 2 2 2
3 reserved 3 3

Table [Link].2-29: SRI indication for non-codebook based PUSCH transmission,

Lmax =2

Bit field Bit field Bit field

mapped to N =2
SRI(s), SRS mapped to N =3
SRI(s), SRS mapped to SRI(s),
N SRS=4
index index index
0 0 0 0 0 0
1 1 1 1 1 1
2 0,1 2 2 2 2
3 reserved 3 0,1 3 3
4 0,2 4 0,1
5 1,2 5 0,2
6-7 reserved 6 0,3
7 1,2
8 1,3
9 2,3
10-15 reserved

Table [Link].2-29A: Second SRI indication for non-codebook based PUSCH transmission, Lmax =2

Bit field Bit field Bit field

mapped to N =2
SRI(s), SRS mapped to N =3
SRI(s), SRS mapped to SRI(s),
N SRS=4
index index index
0 0 0 0 0 0
1 1 1 1 1 1
0 0,1 2 2 2 2
1 2 layers: reserved 3 1 layer: reserved 3 3
0 0,1 4-7 1 layer: reserved
1 0,2 0 0,1
2 1,2 1 0,2
3 2 layers: reserved 2 0,3
3 1,2
4 1,3
5 2,3
6-7 2 layers: reserved

3GPP
Release 17 153 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-30: SRI indication for non-codebook based PUSCH transmission,

Lmax =3

Bit field Bit field Bit field

mapped to N =2
SRI(s), SRS mapped to N =3
SRI(s), SRS mapped to SRI(s),
N SRS=4
index index index
0 0 0 0 0 0
1 1 1 1 1 1
2 0,1 2 2 2 2
3 reserved 3 0,1 3 3
4 0,2 4 0,1
5 1,2 5 0,2
6 0,1,2 6 0,3
7 reserved 7 1,2
8 1,3
9 2,3
10 0,1,2
11 0,1,3
12 0,2,3
13 1,2,3
14-15 reserved

Table [Link].2-30A: Second SRI indication for non-codebook based PUSCH transmission, Lmax =3

Bit field Bit field Bit field

3GPP
Release 17 154 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-31: SRI indication for non-codebook based PUSCH transmission,

Lmax =4

Bit field Bit field Bit field

Table [Link].2-31A: Second SRI indication for non-codebook based PUSCH transmission, Lmax =4

Bit field Bit field Bit field

mapped to SRI(s),
N SRS=2 mapped to SRI(s),
N SRS=3 mapped to SRI(s),
N SRS=4
index index index
0 0 0 0 0 0
1 1 1 1 1 1
0 0,1 2 2 2 2
1 2 layers: reserved 3 1 layer: reserved 3 3
0 0,1 4-7 1 layer: reserved
1 0,2 0 0,1
2 1,2 1 0,2
3 2 layers: reserved 2 0,3
0 0,1,2 3 1,2
1-3 3 layers: reserved 4 1,3
5 2,3
6-7 2 layers: reserved
0 0,1,2
1 0,1,3
2 0,2,3
3 1,2,3
4-7 3 layer: reserved
0 0,1,2,3
1-7 4 layers: reserved

Table [Link].2-32: SRI indication or Second SRI indication, for codebook based PUSCH
transmission, if ul-FullPowerTransmission is not configured, or ul-FullPowerTransmission =
fullpowerMode1, or ul-FullPowerTransmission = fullpowerMode2, or ul-FullPowerTransmission =
fullpower and N SRS =2

Bit field mapped to index SRI(s),

N SRS=2
0 0
1 1

3GPP
Release 17 155 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-32A: SRI indication or Second SRI indication, for codebook based PUSCH
transmission, if ul-FullPowerTransmission = fullpowerMode2 and N SRS =3

Bit field mapped to index SRI(s), N SRS =3

0 0
1 1
2 2
3 Reserved

Table [Link].2-32B: SRI indication or Second SRI indication, for codebook based PUSCH
transmission, if ul-FullPowerTransmission = fullpowerMode2 and N SRS =4

Bit field mapped to index SRI(s), N SRS =4

0 0
1 1
2 2
3 3

Table [Link].2-33: Joint indication of minimum applicable scheduling offset K0/K2

Minimum applicable K0 for the Minimum applicable K2 for the

active DL BWP, if active UL BWP, if
Bit field mapped to index
minimumSchedulingOffsetK0 is minimumSchedulingOffsetK2 is
configured for the DL BWP configured for the UL BWP
0 The first value configured by The first value configured by
minimumSchedulingOffsetK0 for the minimumSchedulingOffsetK2 for the
active DL BWP active UL BWP
1 The second value configured by The second value configured by
minimumSchedulingOffsetK0 for the minimumSchedulingOffsetK2 for the
active DL BWP if the second value is active UL BWP if the second value is
configured; 0 otherwise configured; 0 otherwise

Table [Link].2-34: Redundancy version

Value of the Redundancy rv id to be applied

version field Value of
0 0
1 2

3GPP
Release 17 156 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-35: Allowed entries for DCI format 0_1 and DCI format 0_2, configured by higher layer
parameter ul-AccessConfigListDCI-0-1 and ul-AccessConfigListDCI-0-2, respectively, in frequency
range 1
The CP extension T_"ext"
Entry
Channel Access Type index defined in Clause CAPC
index
5.3.1 of [4, 38.211]
0 Type2C-ULChannelAccess defined in [clause [Link].3 in 37.213] 0 1
1 Type2C-ULChannelAccess defined in [clause [Link].3 in 37.213] 0 2
2 Type2C-ULChannelAccess defined in [clause [Link].3 in 37.213] 0 3
3 Type2C-ULChannelAccess defined in [clause [Link].3 in 37.213] 0 4
4 Type2C-ULChannelAccess defined in [clause [Link].3 in 37.213] 2 1
5 Type2C-ULChannelAccess defined in [clause [Link].3 in 37.213] 2 2
6 Type2C-ULChannelAccess defined in [clause [Link].3 in 37.213] 2 3
7 Type2C-ULChannelAccess defined in [clause [Link].3 in 37.213] 2 4
8 Type2B-ULChannelAccess defined in [clause [Link].2 in 37.213] 0 1
9 Type2B-ULChannelAccess defined in [clause [Link].2 in 37.213] 0 2
10 Type2B-ULChannelAccess defined in [clause [Link].2 in 37.213] 0 3
11 Type2B-ULChannelAccess defined in [clause [Link].2 in 37.213] 0 4
12 Type2B-ULChannelAccess defined in [clause [Link].2 in 37.213] 2 1
13 Type2B-ULChannelAccess defined in [clause [Link].2 in 37.213] 2 2
14 Type2B-ULChannelAccess defined in [clause [Link].2 in 37.213] 2 3
15 Type2B-ULChannelAccess defined in [clause [Link].2 in 37.213] 2 4
16 Type2A-ULChannelAccess defined in [clause [Link].1 in 37.213] 0 1
17 Type2A-ULChannelAccess defined in [clause [Link].1 in 37.213] 0 2
18 Type2A-ULChannelAccess defined in [clause [Link].1 in 37.213] 0 3
19 Type2A-ULChannelAccess defined in [clause [Link].1 in 37.213] 0 4
20 Type2A-ULChannelAccess defined in [clause [Link].1 in 37.213] 1 1
21 Type2A-ULChannelAccess defined in [clause [Link].1 in 37.213] 1 2
22 Type2A-ULChannelAccess defined in [clause [Link].1 in 37.213] 1 3
23 Type2A-ULChannelAccess defined in [clause [Link].1 in 37.213] 1 4
24 Type2A-ULChannelAccess defined in [clause [Link].1 in 37.213] 3 1
25 Type2A-ULChannelAccess defined in [clause [Link].1 in 37.213] 3 2
26 Type2A-ULChannelAccess defined in [clause [Link].1 in 37.213] 3 3
27 Type2A-ULChannelAccess defined in [clause [Link].1 in 37.213] 3 4
28 Type1-ULChannelAccess defined in [clause [Link] in 37.213] 0 1
29 Type1-ULChannelAccess defined in [clause [Link] in 37.213] 0 2
30 Type1-ULChannelAccess defined in [clause [Link] in 37.213] 0 3
31 Type1-ULChannelAccess defined in [clause [Link] in 37.213] 0 4
32 Type1-ULChannelAccess defined in [clause [Link] in 37.213] 1 1
33 Type1-ULChannelAccess defined in [clause [Link] in 37.213] 1 2
34 Type1-ULChannelAccess defined in [clause [Link] in 37.213] 1 3
35 Type1-ULChannelAccess defined in [clause [Link] in 37.213] 1 4
36 Type1-ULChannelAccess defined in [clause [Link] in 37.213] 2 1
37 Type1-ULChannelAccess defined in [clause [Link] in 37.213] 2 2
38 Type1-ULChannelAccess defined in [clause [Link] in 37.213] 2 3
39 Type1-ULChannelAccess defined in [clause [Link] in 37.213] 2 4
40 Type1-ULChannelAccess defined in [clause [Link] in 37.213] 3 1
41 Type1-ULChannelAccess defined in [clause [Link] in 37.213] 3 2
42 Type1-ULChannelAccess defined in [clause [Link] in 37.213] 3 3
43 Type1-ULChannelAccess defined in [clause [Link] in 37.213] 3 4

Table [Link].2-35A: Allowed entries for DCI format 0_1 and DCI format 0_2, configured by higher
layer parameter ul-AccessConfigListDCI-0-1 in frequency range 2-2

Entry
Channel Access Type
index
0 Type 1 channel access defined in clause 4.4.1 of 37.213
1 Type 2 channel access defined in clause 4.4.2 of 37.213
2 Type 3 channel access defined in clause 4.4.3 of 37.213

3GPP
Release 17 157 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-36: SRS resource set indication

Bit field mapped to

SRS resource set indication
index
0 SRS resource indicator field and Precoding information and number of layers
field are associated with the first SRS resource set;
Second SRS resource indicator field and Second Precoding information field are
reserved.
SRS resource indicator field and Precoding information and number of layers
field are associated with the second SRS resource set;
1
Second SRS resource indicator field and Second Precoding information field are
reserved.
SRS resource indicator field and Precoding information and number of layers
field are associated with the first SRS resource set;
2
Second SRS resource indicator field and Second Precoding information field are
associated with the second SRS resource set.
SRS resource indicator field and Precoding information and number of layers
field are associated with the first SRS resource set;
3
Second SRS resource indicator field and Second Precoding information field are
associated with the second SRS resource set.
NOTE 1: The first and the second SRS resource sets are respectively the ones with lower and higher srs-
ResourceSetId of the two SRS resources sets configured by higher layer parameter srs-
ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, and associated with the higher
layer parameter usage of value 'nonCodeBook' if txConfig=nonCodebook or 'codebook' if
txConfig=codebook. When only one SRS resource set is configured by higher layer parameter srs-
ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, and associated with the higher
layer parameter usage of value 'codebook' or 'nonCodeBook' respectively, the first SRS resource set is
the SRS resource set. The association of the first and second SRS resource sets to PUSCH repetitions
for each bit field index value is as defined in Clause [Link] of [6, TS 38.214].
NOTE 2: For DCI format 0_2, the first and second SRS resource sets configured by higher layer
parameter srs-ResourceSetToAddModListDCI-0-2 are composed of the first N SRS , 02 SRS resources
together with other configurations in the first and second SRS resource sets configured by higher layer
parameter srs-ResourceSetToAddModList, if any, and associated with the higher layer parameter usage
of value 'codebook' or 'nonCodeBook', respectively, except for the higher layer parameters 'srs-
ResourceSetId' and 'srs-ResourceIdList'.

Table [Link].2-37: SRS offset indicator

Bit field Bit field Bit field

Available slot offset, Available slot offset, Available slot offset,
mapped mapped mapped
K=2 K=3 K=4
to index to index to index
0 The 1st entry in 0 The 1st entry in 0 The 1st entry in
availableSlotOffsetList availableSlotOffsetList, availableSlotOffsetList,
, if configured for the if configured for the if configured for the
aperiodic SRS aperiodic SRS aperiodic SRS
resource set; resource set; resource set;
0, otherwise 0, otherwise 0, otherwise
1 The 2nd entry in 1 The 2nd entry in 1 The 2nd entry in
availableSlotOffsetList availableSlotOffsetList, availableSlotOffsetList,
, if configured for the if configured for the if configured for the
aperiodic SRS aperiodic SRS aperiodic SRS
resource set; resource set; resource set;
0, otherwise 0, otherwise 0, otherwise
2 The 3rd entry in 2 The 3rd entry in
availableSlotOffsetList, availableSlotOffsetList,
if configured for the if configured for the
aperiodic SRS aperiodic SRS
resource set; resource set;
0, otherwise 0, otherwise
3 Reserved 3 The 4th entry in
availableSlotOffsetList,
if configured for the
aperiodic SRS
resource set;
0, otherwise

3GPP
Release 17 158 3GPP TS 38.212 V17.5.0 (2023-03)

[Link].3 Format 0_2

DCI format 0_2 is used for the scheduling of PUSCH in one cell.

The following information is transmitted by means of the DCI format 0_2 with CRC scrambled by C-RNTI or CS-
RNTI or SP-CSI-RNTI or MCS-C-RNTI:

- Identifier for DCI formats – 1 bit

- The value of this bit field is always set to 0, indicating an UL DCI format

- Carrier indicator – 0, 1, 2 or 3 bits determined by higher layer parameter carrierIndicatorSizeDCI-0-2, as defined

in Clause 10.1 of [5, TS38.213]. This field is reserved when this format is carried by PDCCH on the primary cell
and the UE is configured for scheduling on the primary cell from an SCell, with the same number of bits as that
in this format carried by PDCCH on the SCell for scheduling on the primary cell.

- Bandwidth part indicator – 0, 1 or 2 bits as determined by the number of UL BWPs n BWP , RRC configured by
higher layers, excluding the initial UL bandwidth part. The bitwidth for this field is determined as
⌈ log 2 (n BWP)⌉ bits, where

- n BWP=n BWP , RRC +1if n BWP , RRC ≤ 3, in which case the bandwidth part indicator is equivalent to the
ascending order of the higher layer parameter BWP-Id;

- otherwise n BWP =n BWP , RRC , in which case the bandwidth part indicator is defined in Table [Link].2-1;

If a UE does not support active BWP change via DCI, the UE ignores this bit field.

- Frequency domain resource assignment – number of bits determined by the following:

- N RBG bits if only resource allocation type 0 is configured, where N RBG is defined in Clause [Link].1 of [6,
TS 38.214]

- ⌈ log 2 ( N RBG ,K 1 ( N RBG , K 1 +1 ) /2 ) ⌉ bits if only resource allocation type 1 is configured, or

max ( ⌈ log 2 ( N RBG , K 1 ( N RBG , K 1+ 1 ) /2 ) ⌉ , N RBG )+1 bits if resourceAllocationDCI-0-2-r16 is configured
as 'dynamicSwitch', where N RBG , K 1=⌈ N RB ( UL ,BWP
+ ( N UL, BWP mod K 1 ) ) /K 1 ⌉ , N UL
start
RB
,BWP
is the size of
start
the active UL bandwidth part, N UL ,BWP is defined as in clause [Link] of [4, TS 38.211] and K 1 is given by
higher layer parameter resourceAllocationType1GranularityDCI-0-2. If the higher layer parameter
resourceAllocationType1GranularityDCI-0-2 is not configured, K 1 is equal to 1.

- If resourceAllocationDCI-0-2-r16 is configured as 'dynamicSwitch', the MSB bit is used to indicate resource

allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0
and the bit value of 1 indicates resource allocation type 1.

- For resource allocation type 0, the N RBG LSBs provide the resource allocation as defined in Clause [Link].1
of [6, TS 38.214].

- For resource allocation type 1, the ⌈ log 2 ( N RBG ,K 1 ( N RBG , K 1 +1 ) /2 ) ⌉ LSBs provide the resource
allocation as follows:

- For PUSCH hopping with resource allocation type 1:

- N UL MSB bits are used to indicate the frequency offset according to Clause 6.3 of [6, TS 38.214],
hop

where N UL =1 if the higher layer parameter frequencyHoppingOffsetListsDCI-0-2 contains two

hop

3GPP
Release 17 159 3GPP TS 38.212 V17.5.0 (2023-03)

offset values and N UL hop =2if the higher layer parameter frequencyHoppingOffsetListsDCI-0-2
contains four offset values

- ⌈ log 2 ( N RBG ,K 1 ( N RBG , K 1 +1 ) /2 ) ⌉−N UL bits provide the frequency domain resource allocation
hop

according to Clause [Link].2 of [6, TS 38.214]

- For non-PUSCH hopping with resource allocation type 1:

- ⌈ log 2 ( N RBG ,K 1 ( N RBG , K 1 +1 ) /2 ) ⌉ bits provide the frequency domain resource allocation according
to Clause [Link].2 of [6, TS 38.214]

If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and if
resourceAllocationDCI-0-2-r16 is configured as 'dynamicSwitch' for the indicated bandwidth part, the UE
assumes resource allocation type 0 for the indicated bandwidth part if the bitwidth of the "Frequency domain
resource assignment" field of the active bandwidth part is smaller than the bitwidth of the "Frequency domain
resource assignment" field of the indicated bandwidth part.

- Time domain resource assignment – 0, 1, 2, 3, 4, 5 or 6 bits as defined in Clause [Link] of [6, TS38.214]. The
bitwidth for this field is determined as ⌈ log 2 (I ) ⌉ bits, where I is the number of entries in the higher layer
parameter pusch-TimeDomainAllocationListDCI-0-2 if the higher layer parameter is configured, or I is the
number of entries in the higher layer parameter PUSCH-TimeDomainResourceAllocationList if the higher layer
parameter PUSCH-TimeDomainResourceAllocationList is configured and the higher layer parameter pusch-
TimeDomainAllocationListDCI-0-2 is not configured; otherwise I is the number of entries in the default table.

- Frequency hopping flag – 0 or 1 bit:

- 0 bit if the higher layer parameter frequencyHoppingDCI-0-2 is not configured;

- 1 bit according to Table [Link].1-3 otherwise, only applicable to resource allocation type 1, as defined in
Clause 6.3 of [6, TS 38.214].

- Modulation and coding scheme –5 bits as defined in Clause [Link] of [6, TS 38.214]

- New data indicator – 1 bit

- Redundancy version – 0, 1 or 2 bits determined by higher layer parameter numberOfBitsForRV-DCI-0-2

- If 0 bit is configured, rvid to be applied is 0;

- 1 bit according to Table [Link].3-1;

- 2 bits according to Table [Link].1-2.

- HARQ process number – number of bits determined by the following:

- 5 bits determined by higher layer parameter harq-ProcessNumberSizeDCI-0-2-v1700 if configured;

- otherwise 0, 1, 2, 3 or 4 bits determined by higher layer parameter harq-ProcessNumberSizeDCI-0-2

- Downlink assignment index – 0, 1, 2 or 4 bits

- 0 bit if the higher layer parameter downlinkAssignmentIndexDCI-0-2 is not configured;

- 1, 2, 3, 4, 5 or 6 bits otherwise,

- 1st downlink assignment index – 1 or 2 bits:

- 1 bit for semi-static HARQ-ACK codebook for unicast and multicast if pdsch-HARQ-ACK-Codebook
= semiStatic is configured for both unicast and multicast and the higher layer parameter fdmed-
ReceptionMulticast is not configured; otherwise for semi-static HARQ-ACK codebook for unicast;

- 2 bits for dynamic HARQ-ACK codebook for unicast.

- 2nd downlink assignment index – 0 or 2 bits

3GPP
Release 17 160 3GPP TS 38.212 V17.5.0 (2023-03)

- 2 bits for dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks for unicast;

- 0 bit otherwise.

- 3rd downlink assignment index – 0, 1 or 2 bits

- 1 bit for semi-static HARQ-ACK codebook for multicast if the higher layer parameter fdmed-
ReceptionMulticast is configured;

- 2 bits for the dynamic HARQ-ACK codebook for multicast;

- 0 bit otherwise.

When two HARQ-ACK codebooks are configured by pdsch-HARQ-ACK-CodebookList for the same serving cell
and if higher layer parameter priorityIndicatorDCI-0-2 is configured, if the bit width of the 1st or 2 nd Downlink
assignment index in DCI format 0_2 for one HARQ-ACK codebook is not equal to that of the 1st or 2 nd
Downlink assignment index in DCI format 0_2 for the other HARQ-ACK codebook, a number of most
significant bits with value set to '0' are inserted to smaller 1st or 2 nd Downlink assignment index until the bit
width of the 1st or 2 nd Downlink assignment index in DCI format 0_2 for the two HARQ-ACK codebooks are the
same.

When two HARQ-ACK codebooks are configured by pdsch-HARQ-ACK-CodebookListMulticast for the same
serving cell and if higher layer parameter priorityIndicatorDCI-0-2 is configured, if the bit width of the 3rd
downlink assignment index in DCI format 0_2 for one HARQ-ACK codebook is not equal to that of the 3rd
downlink assignment index in DCI format 0_2 for the other HARQ-ACK codebook, a number of most
significant bits with value set to '0' are inserted to smaller 3rd downlink assignment index until the bit width of
the 3rd downlink assignment index in DCI format 0_2 for the two HARQ-ACK codebooks are the same.

- TPC command for scheduled PUSCH – 2 bits as defined in Clause 7.1.1 of [5, TS38.213]

- Second TPC command for scheduled PUSCH – 2 bits as defined in Clause 7.1.1 of [5, TS38.213] if higher layer
parameter SecondTPCFieldDCI-0-2 is configured; 0 bit otherwise.

- SRS resource set indicator – 0 or 2 bits

- 2 bits according to Table [Link].2-36 if

- txConfig = nonCodeBook, and there are two SRS resource sets configured by srs-
ResourceSetToAddModListDCI-0-2 and associated with the usage of value 'nonCodeBook', or

- txConfig=codebook, and there are two SRS resource sets configured by srs-
ResourceSetToAddModListDCI-0-2 and associated with usage of value 'codebook';

- 0 bit otherwise.

( ( N k )) ⌉
min { Lmax , N SRS , 0 }
2

- SRS resource indicator – ⌈ log 2 ∑ SRS ,02 or ⌈ log 2 N SRS ,02 ⌉ bits, where N SRS , 02 is the number
k=1

of configured SRS resources in the SRS resource set indicated by SRS resource set indicator field if present;
otherwise N SRS , 02 is the number of configured SRS resources in the SRS resource set configured by higher layer
parameter srs-ResourceSetToAddModListDCI-0-2 and associated with the higher layer parameter usage of value
'codeBook' or 'nonCodeBook', where the SRS resource set is composed of the first N SRS , 02 SRS resources
together with other configurations in the SRS resource set, or in the SRS resource set with lower srs-
ResourceSetId of two SRS resources sets, configured by higher layer parameter srs-ResourceSetToAddModList,
if any, and associated with the higher layer parameter usage of value 'codeBook' or 'nonCodeBook', respectively,
except for the higher layer parameters 'srs-ResourceSetId' and 'srs-ResourceIdList'

( ( N k )) ⌉
min { Lmax , N SRS , 0 }
2

- ⌈ log 2 ∑ SRS ,02 bits according to Tables [Link].2-28/29/30/31 if the higher layer parameter
k=1

txConfig = nonCodebook, where N SRS , 0 is the number of configured SRS resources in the SRS resource set
2

indicated by SRS resource set indicator field if present, otherwise N SRS , 0 is the number of configured SRS 2

3GPP
Release 17 161 3GPP TS 38.212 V17.5.0 (2023-03)

resources in the SRS resource set configured by higher layer parameter srs-ResourceSetToAddModListDCI-
0-2 and associated with the higher layer parameter usage of value 'nonCodeBook', where the SRS resource
set is composed of the first N SRS , 02 SRS resources together with other configurations in the SRS resource set,
or in the SRS resource set with lower srs-ResourceSetId of two SRS resources sets, configured by higher
layer parameter srs-ResourceSetToAddModList, if any, and associated with the higher layer parameter usage
of value 'nonCodeBook', except for the higher layer parameters 'srs-ResourceSetId' and 'srs-ResourceIdList',
and

- if UE supports operation with maxMIMO-LayersDCI-0-2 and the higher layer parameter maxMIMO-
LayersDCI-0-2 of PUSCH-ServingCellConfig of the serving cell is configured, Lmax is given by that
parameter

- otherwise, Lmax is given by the maximum number of layers for PUSCH supported by the UE for the
serving cell for non-codebook based operation.

- ⌈ log2 N SRS ,0 ⌉ bits according to Tables [Link].2-32 if the higher layer parameter txConfig = codebook,
2

where N SRS , 0 is the number of configured SRS resources in the SRS resource set indicated by SRS resource
2

set indicator field if present, otherwise N SRS , 0 is the number of configured SRS resources in the SRS
2

resource set configured by higher layer parameter srs-ResourceSetToAddModListDCI-0-2 and associated

with the higher layer parameter usage of value 'codeBook', where the SRS resource set is composed of the
first N SRS , 02 SRS resources together with other configurations in the SRS resource set configured by higher
layer parameter srs-ResourceSetToAddModList, if any, and associated with the higher layer parameter usage
of value 'codeBook', except for the higher layer parameters 'srs-ResourceSetId' and 'srs-ResourceIdList'.

- Second SRS resource indicator – 0, ⌈ log 2 ( max

k ∈{1 ,2 ,… , min⁡{L max , N SRS ,0 }}
2
( N k )) ⌉
SRS ,02
or ⌈ log2 N SRS ,0 ⌉ bits,
2

- ⌈ log 2 ( max
k ∈{1 ,2 ,… , min⁡{L max , N SRS ,0 }}
2
( N SRS ,0
k
2

)
) ⌉ bits according to Tables [Link].2-28/29A/30A/31A with the
same number of layers indicated by SRS resource indicator field if the higher layer parameter txConfig =
nonCodebook and SRS resource set indicator field is present, where N SRS , 02 is the number of configured SRS
resources in the second SRS resource set, and

- otherwise, Lmax is given by the maximum number of layers for PUSCH supported by the UE for the
serving cell for non-codebook based operation.

- ⌈ log2 N SRS ,0 ⌉ bits according to Tables [Link].2-32 if the higher layer parameter txConfig = codebook and
2

SRS resource set indicator field is present, where N SRS , 0 is the number of configured SRS resources in the
2

second SRS resource set.

- 0 bit otherwise.

- Precoding information and number of layers – number of bits determined by the following:

- 0 bits if the higher layer parameter txConfig = nonCodeBook;

- 0 bits for 1 antenna port and if the higher layer parameter txConfig = codebook;

- 4 or 5 bits according to Table [Link].2-2A for 4 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission =fullpowerMode1, the values of higher layer parameters maxRankDCI-0-2=2,
transform precoder is disabled, and according to the value of higher layer parameter codebookSubsetDCI-0-2;

3GPP
Release 17 162 3GPP TS 38.212 V17.5.0 (2023-03)

- 4 or 6 bits according to Table [Link].2-2B for 4 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission =fullpowerMode1, the values of higher layer parameters maxRankDCI-0-2=3 or 4,
transform precoder is disabled, and according to the value of higher layer parameter codebookSubsetDCI-0-2;

- 3 or 4 bits according to Table [Link].2-3A for 4 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission =fullpowerMode1, maxRankDCI-0-2=1, and according to whether transform
precoder is enabled or disabled, and the value of higher layer parameter codebookSubsetDCI-0-2;

- 2 or 4 bits according to Table7.[Link]-4 for 2 antenna ports, if txConfig = codebook, ul-

- 2 bits according to Table [Link].2-4A for 2 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission =fullpowerMode1, transform precoder is disabled, the maxRankDCI-0-2=2, and
codebookSubsetDCI-0-2=nonCoherent;

- 1 or 3 bits according to Table7.[Link]-5 for 2 antenna ports, if txConfig = codebook, ul-

FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower, and
according to whether transform precoder is enabled or disabled, and the values of higher layer parameters
maxRankDCI-0-2 and codebookSubsetDCI-0-2;

- 2 bits according to Table [Link].2-5A for 2 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission =fullpowerMode1, maxRankDCI-0-2=1, and according to whether transform
precoder is enabled or disabled, and the value of higher layer parameter codebookSubsetDCI-0-2.

For the higher layer parameter txConfig=codebook, if ul-FullPowerTransmission is configured to fullpowerMode2,

the values of higher layer parameters maxRankDCI-0-2 is configured to be larger than 2, and at least one SRS
resource with 4 antenna ports is configured in the SRS resource set indicated by SRS resource set indicator field if
present, otherwise in an SRS resource set with usage set to 'codebook', and an SRS resource with 2 antenna ports is
indicated via SRI in the same SRS resource set, then Table [Link].2-4 is used.

For the higher layer parameter txConfig = codebook, if different SRS resources with different number of antenna
ports are configured, the bitwidth is determined according to the maximum number of ports in an SRS resource
among the configured SRS resources in all SRS resource set(s) with usage set to 'codebook'. If the number of ports
for a configured SRS resource in the set is less than the maximum number of ports in an SRS resource among the
configured SRS resources, a number of most significant bits with value set to '0' are inserted to the field.

- Second Precoding information – number of bits determined by the following:

- 0 bits if SRS resource set indicator field is not present;

- 0 bits if the higher layer parameter txConfig = nonCodeBook;

- 0 bits for 1 antenna port and if the higher layer parameter txConfig = codebook;

- 3 or 4 bits according to Table [Link].2-2D with the same number of layers indicated by Precoding
information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present,
txConfig = codebook, ul-FullPowerTransmission =fullpowerMode1, the values of higher layer parameters
maxRankDCI-0-2=2, transform precoder is disabled, and according to the value of higher layer parameter
codebookSubsetDCI-0-2;

3GPP
Release 17 163 3GPP TS 38.212 V17.5.0 (2023-03)

txConfig = codebook, ul-FullPowerTransmission =fullpowerMode1, the values of higher layer parameters

maxRankDCI-0-2=3 or 4, transform precoder is disabled, and according to the value of higher layer
parameter codebookSubsetDCI-0-2;

- 2, 4, or 5 bits according to Table [Link].2-3 with the same number of layers indicated by Precoding
information and number of layers field for 4 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower, and
according to whether transform precoder is enabled or disabled, and the values of higher layer parameters
maxRankDCI-0-2 and codebookSubsetDCI-0-2;

- 3 or 4 bits according to Table [Link].2-3A with the same number of layers indicated by Precoding
information and number of layers field for 4 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission =fullpowerMode1, maxRankDCI-0-2=1, and according to whether transform
precoder is enabled or disabled, and the value of higher layer parameter codebookSubsetDCI-0-2;

- 2 bits according to Table [Link].2-4C with the same number of layers indicated by Precoding information
and number of layers field for 2 antenna ports, if SRS resource set indicator field is present, txConfig =
codebook, ul-FullPowerTransmission =fullpowerMode1, transform precoder is disabled, the maxRankDCI-
0-2=2, and codebookSubsetDCI-0-2=nonCoherent;

- 2 bits according to Table [Link].2-5A with the same number of layers indicated by Precoding information
and number of layers field for 2 antenna ports, if SRS resource set indicator field is present, txConfig =
codebook, ul-FullPowerTransmission =fullpowerMode1, maxRankDCI-0-2=1, and according to whether
transform precoder is enabled or disabled, and the value of higher layer parameter codebookSubsetDCI-0-2.

For the higher layer parameter txConfig=codebook, if ul-FullPowerTransmission is configured to fullpowerMode2,

the values of higher layer parameters maxRankDCI-0-2 is configured to be larger than 2, and at least one SRS
resource with 4 antenna ports is configured in the SRS resource set indicated by SRS resource set indicator field,
and an SRS resource with 2 antenna ports is indicated via Second SRS resource indicator field in the same SRS
resource set, then Table [Link].2-4B is used.

For the higher layer parameter txConfig = codebook, if different SRS resources with different number of antenna
ports are configured, the bitwidth is determined according to the maximum number of ports in an SRS resource
among the configured SRS resources in the second SRS resource set with usage set to 'codebook' as defined in
Table [Link].2-36. If the number of ports for a configured SRS resource in the set is less than the maximum
number of ports in an SRS resource among the configured SRS resources, a number of most significant bits with
value set to '0' are inserted to the field.

- Antenna ports – number of bits determined by the following:

- 0 bit if higher layer parameter antennaPortsFieldPresenceDCI-0-2 is not configured;

- 2, 3, 4, or 5 bits otherwise,

- 2 bits as defined by [Link].2-6A, if transform precoder is enabled, and dmrs-UplinkTransformPrecoding

and tp-pi2BPSK are both configured, π/2 BPSK modulation is used, dmrs-Type=1, and maxLength=1,
where nSCID is the scrambling identity for antenna ports defined in Clause [Link].1.2, in [4, TS38.211];

3GPP
Release 17 164 3GPP TS 38.212 V17.5.0 (2023-03)

- 4 bits as defined by Tables [Link].2-7A, if transform precoder is enabled, and dmrs-

- 3 bits as defined by Tables [Link].2-8/9/10/11, if transform precoder is disabled, dmrs-Type=1, and

maxLength=1, and the value of rank is determined according to the SRS resource indicator field if the
higher layer parameter txConfig = nonCodebook and according to the Precoding information and number
of layers field if the higher layer parameter txConfig = codebook;

- 4 bits as defined by Tables [Link].2-12/13/14/15, if transform precoder is disabled, dmrs-Type=1, and

maxLength=2, and the value of rank is determined according to the SRS resource indicator field if the
higher layer parameter txConfig = nonCodebook and according to the Precoding information and number
of layers field if the higher layer parameter txConfig = codebook;

- 4 bits as defined by Tables [Link].2-16/17/18/19, if transform precoder is disabled, dmrs-Type=2, and

maxLength=1, and the value of rank is determined according to the SRS resource indicator field if the
higher layer parameter txConfig = nonCodebook and according to the Precoding information and number
of layers field if the higher layer parameter txConfig = codebook;

- 5 bits as defined by Tables [Link].2-20/21/22/23, if transform precoder is disabled, dmrs-Type=2, and

maxLength=2, and the value of rank is determined according to the SRS resource indicator field if the
higher layer parameter txConfig = nonCodebook and according to the Precoding information and number
of layers field if the higher layer parameter txConfig = codebook.

where the number of CDM groups without data of values 1, 2, and 3 in Tables [Link].2-6 to [Link].2-23 refers
to CDM groups {0}, {0,1}, and {0, 1,2} respectively.

If a UE is configured with both dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 and dmrs-UplinkForPUSCH-

MappingTypeB-DCI-0-2 and is configured with antennaPortsFieldPresenceDCI-0-2, the bitwidth of this field
equals max { x A , x B } , where x A is the "Antenna ports" bitwidth derived according to dmrs-UplinkForPUSCH-
MappingTypeA-DCI-0-2 and x B is the "Antenna ports" bitwidth derived according to dmrs-UplinkForPUSCH-
MappingTypeB-DCI-0-2. A number of |x A −x B|zeros are padded in the MSB of this field, if the mapping type
of the PUSCH corresponds to the smaller value of x A and x B .

If a UE is not configured with higher layer parameter antennaPortsFieldPresenceDCI-0-2, antenna port(s) are
defined assuming bit field index value 0 in Tables [Link].2-6 to [Link].2-23.

- SRS request – 0, 1, 2 or 3 bits

- 0 bit if the higher layer parameter srs-RequestDCI-0-2 is not configured;

- 1 bit as defined by Table [Link].3-1 if higher layer parameter srs-RequestDCI-0-2 = 1 and for UEs not
configured with supplementaryUplink in ServingCellConfig in the cell;

- 2 bits if higher layer parameter srs-RequestDCI-0-2 = 1 and for UEs configured with supplementaryUplink in
ServingCellConfig in the cell, where the first bit is the non-SUL/SUL indicator as defined in Table [Link].1-
1 and the second bit is defined by Table [Link].3-1;

- 2 bits as defined by Table [Link].2-24 if higher layer parameter srs-RequestDCI-0-2 = 2 and for UEs not
configured with supplementaryUplink in ServingCellConfig in the cell;

- 3 bits if higher layer parameter srs-RequestDCI-0-2 = 2 and for UEs configured with supplementaryUplink in
ServingCellConfig in the cell, where the first bit is the non-SUL/SUL indicator as defined in Table [Link].1-
1 and the second and third bits are defined by Table [Link].2-24;

- SRS offset indicator – 0, 1 or 2 bits.

3GPP
Release 17 165 3GPP TS 38.212 V17.5.0 (2023-03)

- CSI request – 0, 1, 2, 3, 4, 5, or 6 bits determined by higher layer parameter reportTriggerSizeDCI-0-2.

- PTRS-DMRS association – number of bits determined as follows

- 0 bit if PTRS-UplinkConfig is not configured in either dmrs-UplinkForPUSCH-MappingTypeA or dmrs-

UplinkForPUSCH-MappingTypeB and transform precoder is disabled, or if transform precoder is enabled, or
if maxRankDCI-0-2=1;

- 2 bits otherwise, where Table [Link].2-25/[Link].2-25A and [Link].2-26 are used to indicate the association
between PTRS port(s) and DMRS port(s) when one PT-RS port and two PT-RS ports are configured by
maxNrofPorts in PTRS-UplinkConfig respectively, and the DMRS ports are indicated by the Antenna ports
field. When the SRS resource set indicator field is present and maxRankDCI-0-2>2, this field indicates the
association between PTRS port(s) and DMRS port(s) corresponding to SRS resource indicator field and/or
Precoding information and number of layers field according to Table [Link].2-25 and [Link].2-26 field
according to Table [Link].2-25 and [Link].2-26. When the SRS resource set indicator field is present and
equals "10" and "11" and maxRankDCI-0-2=2, the MSB of this field indicates the association between PTRS
port(s) and DMRS port(s) corresponding to SRS resource indicator field and/or Precoding information and
number of layers field, and the LSB of this field indicates the association between PTRS port(s) and DMRS
port(s) corresponding to Second SRS resource indicator field and/or Second Precoding information field,
according to Table [Link].2-25A.

- Second PTRS-DMRS association – 2 bits if PTRS-DMRS association field and SRS resource set indicator field
are present and maxRankDCI-0-2>2; 0 bit otherwise. Table [Link].2-25 and [Link].2-26 are used to indicate the
association between PTRS port(s) and DMRS port(s) corresponding to Second SRS resource indicator field
and/or Second precoding information field when one PT-RS port and two PT-RS ports are configured by
maxNrofPorts in PTRS-UplinkConfig respectively, and the DMRS ports are indicated by the Antenna ports
field.

- beta_offset indicator – 0 bit if the higher layer parameter betaOffsetsDCI-0-2 = semiStaticDCI-0-2; otherwise 1
bit if 2 offset indexes are configured by higher layer parameter dynamicDCI-0-2 as defined by Table 9.3-3A in
[5, TS 38.213], and 2 bits if 4 offset indexes are configured by higher layer parameter dynamicDCI-0-2 as
defined by Table 9.3-3 in [5, TS 38.213].

When two HARQ-ACK codebooks are configured by pdsch-HARQ-ACK-CodebookList or by pdsch-HARQ-

ACK-CodebookListMulticast for the same serving cell and if higher layer parameter priorityIndicatorDCI-0-2 is
configured, if the bit width of the beta_offset indicator in DCI format 0_2 for one HARQ-ACK codebook is not
equal to that of the beta_offset indicator in DCI format 0_2 for the other HARQ-ACK codebook, a number of
most significant bits with value set to '0' are inserted to smaller beta_offset indicator until the bit width of the
beta_offset indicator in DCI format 0_2 for the two HARQ-ACK codebooks are the same.

- DMRS sequence initialization – 0 or 1 bit

- 0 bit if the higher layer parameter dmrs-SequenceInitializationDCI-0-2 is not configured or if transform

precoder is enabled;

- 1 bit if transform precoder is disabled and the higher layer parameter dmrs-SequenceInitializationDCI-0-2 is
configured.

- UL-SCH indicator – 1 bit. A value of "1" indicates UL-SCH shall be transmitted on the PUSCH and a value of
"0" indicates UL-SCH shall not be transmitted on the PUSCH. If a UE does not support triggering SRS only in

3GPP
Release 17 166 3GPP TS 38.212 V17.5.0 (2023-03)

DCI, except for DCI format 0_2 with CRC scrambled by SP-CSI-RNTI, the UE is not expected to receive a DCI
format 0_2 with UL-SCH indicator of "0" and CSI request of all zero(s). If a UE supports triggering SRS only in
DCI, except for DCI format 0_2 with CRC scrambled by SP-CSI-RNTI, the UE is not expected to recerive a
DCI format 0_2 with UL-SCH indicator of "0", CSI request of all zero(s) and SRS request of all zero(s).

- ChannelAccess-CPext-CAPC – 0, 1, 2, 3, 4, 5 or 6 bits. The bitwidth for this field is determined as ⌈ log 2 (I )⌉

bits, where I is the number of entries in the higher layer parameter ul-AccessConfigListDCI-0-2 or in Table
[Link].1-4A if channelAccessMode-r16 = "semiStatic" is provided, for operation in a cell with shared spectrum
channel access in frequency range 1, or the number of entries in the high layer parameter ul-
AccessConfigListDCI-0-1 for operation in frequency range 2-2 if ChannelAccessMode2-r17 is provided;
otherwise 0 bit. One or more entries from Table [Link].2-35 are configured by the higher layer parameter ul-
AccessConfigListDCI-0-2 in frequency range 1. One or more entries from Table [Link].2-35A are configured by
the higher layer parameter ul-AccessConfigListDCI-0-1 in frequency range 2-2.

- Open-loop power control parameter set indication – 0 or 1 or 2 bits.

- 0 bit if the higher layer parameter p0-PUSCH-SetList is not configured;

- 1 or 2 bits otherwise,

- 1 bit if SRS resource indicator is present in the DCI format 0_2;

- 1 or 2 bits as determined by higher layer parameter olpc-ParameterSetDCI-0-2 if SRS resource indicator

is not present in the DCI format 0_2;

- Priority indicator – 0 bit if higher layer parameter priorityIndicatorDCI-0-2 is not configured; otherwise 1 bit as
defined in Clause 9 in [5, TS 38.213].

- Invalid symbol pattern indicator – 0 bit if higher layer parameter invalidSymbolPatternIndicatorDCI-0-2 is not
configured; otherwise 1 bit as defined in Clause [Link] in [6, TS 38.214].

- PDCCH monitoring adaptation indication – 0, 1 or 2 bits

- 1 or 2 bits, if searchSpaceGroupIdList-r17 is not configured and if pdcch-SkippingDurationList is configured

- 1 bit if the UE is configured with only one duration by pdcch-SkippingDurationList;

- 2 bits if the UE is configured with more than one duration by pdcch-SkippingDurationList.

- 1 or 2 bits, if pdcch-SkippingDurationList is not configured and if searchSpaceGroupIdList-r17 is configured

- 2 bits if the UE is configured by searchSpaceGroupIdList-r17 with search space set(s) with group index
0, search space set(s) with group index 1 and search space set(s) with group index 2;

- 2 bits, if pdcch-SkippingDurationList is configured and if searchSpaceGroupIdList-r17 is configured

- 0 bit, otherwise

A UE does not expect that the bit width of a field in DCI format 0_2 with CRC scrambled by CS-RNTI is larger than
corresponding bit width of same field in DCI format 0_2 with CRC scrambled by C-RNTI for the same serving cell. If
the bit width of a field in the DCI format 0_2 with CRC scrambled by CS-RNTI is not equal to that of the
corresponding field in the DCI format 0_2 with CRC scrambled by C-RNTI for the same serving cell, a number of most
significant bits with value set to '0' are inserted to the field in DCI format 0_2 with CRC scrambled by CS-RNTI until
the bit width equals that of the corresponding field in the DCI format 0_2 with CRC scrambled by C-RNTI for the same
serving cell.

For a UE configured with scheduling on the primary cell from an SCell, if prior to padding the number of information
bits in DCI format 0_2 carried by PDCCH on the primary cell is not equal to the number of information bits in DCI
format 0_2 carried by PDCCH on the SCell for scheduling on the primary cell, zeros shall be appended to the DCI
format 0_2 with smaller size until the payload size is the same.

3GPP
Release 17 167 3GPP TS 38.212 V17.5.0 (2023-03)

- If application of step 4B in clause [Link] results in additional zero padding for DCI format 0_2 for scheduling
on the primary cell, corresponding zeros shall be appended to both DCI format 0_2 monitored on the primary
cell and DCI format 0_2 monitored on the SCell for scheduling on the primary cell.

- If the SCell is deactivated and firstActiveDownlinkBWP-Id is not set to dormant BWP, the UE determines the
number of information bits in DCI format 0_2 carried by PDCCH on the primary cell based on a DL BWP
provided by firstActiveDownlinkBWP-Id for the SCell. If the active DL BWP of the SCell is a dormant DL
BWP, or if the SCell is deactivated and firstActiveDownlinkBWP-Id is set to dormant BWP, the UE determines
the number of information bits in DCI format 0_2 carried by PDCCH on the primary cell based on a DL BWP
provided by firstWithinActiveTimeBWP-Id for the SCell if provided; otherwise, based on a DL BWP provided by
firstOutsideActiveTimeBWP-Id for the SCell.

Table [Link].3-1: 1 bit SRS request in DCI format 0_2 and DCI format 1_2

Value of SRS request Triggered aperiodic SRS resource

field set(s) for DCI format 0_2 and 1_2
No aperiodic SRS resource set
0
triggered
SRS resource set(s) configured with
higher layer parameter aperiodicSRS-
1 ResourceTrigger set to 1 or an entry in
aperiodicSRS-ResourceTriggerList set
to 1

[Link] DCI formats for scheduling of PDSCH

[Link].1 Format 1_0
DCI format 1_0 is used for the scheduling of PDSCH in one DL cell.

The following information is transmitted by means of the DCI format 1_0 with CRC scrambled by C-RNTI or CS-
RNTI or MCS-C-RNTI:

- Identifier for DCI formats – 1 bits

- The value of this bit field is always set to 1, indicating a DL DCI format

- Frequency domain resource assignment –

⌈log 2 ( N DL,BWP
RB ( N DL,BWP
RB +1 )/2)⌉ bits where N DL,BWP
RB is given by
clause [Link]

If the CRC of the DCI format 1_0 is scrambled by C-RNTI and the "Frequency domain resource assignment" field
are of all ones, the DCI format 1_0 is for random access procedure initiated by a PDCCH order, with all remaining
fields set as follows:

- Random Access Preamble index – 6 bits according to ra-PreambleIndex in Clause 5.1.2 of [8, TS38.321]

- UL/SUL indicator – 1 bit. If the value of the "Random Access Preamble index" is not all zeros and if the UE is
configured with supplementaryUplink in ServingCellConfig in the cell, this field indicates which UL carrier in
the cell to transmit the PRACH according to Table [Link].1-1; otherwise, this field is reserved

- SS/PBCH index – 6 bits. If the value of the "Random Access Preamble index" is not all zeros, this field indicates
the SS/PBCH that shall be used to determine the RACH occasion for the PRACH transmission; otherwise, this
field is reserved.

- PRACH Mask index – 4 bits. If the value of the "Random Access Preamble index" is not all zeros, this field
indicates the RACH occasion associated with the SS/PBCH indicated by "SS/PBCH index" for the PRACH
transmission, according to Clause 5.1.1 of [8, TS38.321]; otherwise, this field is reserved

- Reserved bits – 12 bits for operation in a cell with shared spectrum channel access in frequency range 1 or when
the DCI format is monitored in common search space for operation in a cell in frequency range 2-2; otherwise 10
bits

3GPP
Release 17 168 3GPP TS 38.212 V17.5.0 (2023-03)

Otherwise, all remaining fields are set as follows:

- Time domain resource assignment – 4 bits as defined in Clause [Link] of [6, TS 38.214]

- VRB-to-PRB mapping – 1 bit according to Table [Link].2-5

- Modulation and coding scheme – 5 bits as defined in Clause 5.1.3 of [6, TS 38.214]

- New data indicator – 1 bit

- Redundancy version – 2 bits as defined in Table [Link].1-2

- HARQ process number – 4 bits

- Downlink assignment index – 2 bits as defined in Clause 9.1.3 of [5, TS 38.213], as counter DAI

- TPC command for scheduled PUCCH – 2 bits as defined in Clause 7.2.1 of [5, TS 38.213]

- PUCCH resource indicator – 3 bits as defined in Clause 9.2.3 of [5, TS 38.213]

- PDSCH-to-HARQ_feedback timing indicator – 3 bits as defined in Clause 9.2.3 of [5, TS38.213]

- Reserved bits – 2 bits when the DCI format is monitored in common search space for operation in a cell in
frequency range 2-2 and the number of bits for the field of 'ChannelAccess-CPext' is 0; 0 bits otherwise

The following information is transmitted by means of the DCI format 1_0 with CRC scrambled by P-RNTI:

- Short Messages Indicator – 2 bits according to Table [Link].1-1.

- Short Messages – 8 bits, according to Clause 6.5 of [9, TS38.331]. If only the scheduling information for Paging,
and TRS availability indication if trs-ResourceSetConfig is configured, are carried, this bit field is reserved.

- Frequency domain resource assignment –

⌈log ( N DL,BWP ( N DL,BWP +1 )/2)⌉
2 RB RB bits. If only the short message, and
TRS availability indication if trs-ResourceSetConfig is configured, are carried, this bit field is reserved.

- N DL,BWP
RB is the size of CORESET 0

- Time domain resource assignment – 4 bits as defined in Clause [Link] of [6, TS38.214]. If only the short
message, and TRS availability indication if trs-ResourceSetConfig is configured, are carried, this bit field is
reserved.

- VRB-to-PRB mapping – 1 bit according to Table [Link].2-5. If only the short message, and TRS availability
indication if trs-ResourceSetConfig is configured, are carried, this bit field is reserved.

- Modulation and coding scheme – 5 bits as defined in Clause 5.1.3 of [6, TS38.214], using Table [Link]-1. If
only the short message, and TRS availability indication if trs-ResourceSetConfig is configured, are carried, this
bit field is reserved.

- TB scaling – 2 bits as defined in Clause [Link] of [6, TS38.214]. If only the short message, and TRS availability
indication if trs-ResourceSetConfig is configured, are carried, this bit field is reserved.

- TRS availability indication – 1, 2, 3, 4, 5, or 6 bits, where the number of bits is equal to one plus the highest
value of all the indBitID(s) provided by the trs-ResourceSetConfig if configured; 0 bits otherwise.

- Reserved bits – (8 – M) bits for operation in a cell with shared spectrum channel access in frequency range 1 or
for operation in a cell in frequency range 2-2; (6 – M) bits for operation in a cell without shared spectrum

3GPP
Release 17 169 3GPP TS 38.212 V17.5.0 (2023-03)

channel access, where the value of M is the number of bits for the field of 'TRS availability indication' as defined
above.

The following information is transmitted by means of the DCI format 1_0 with CRC scrambled by SI-RNTI:

- Frequency domain resource assignment –

⌈log 2 ( N DL,BWP
RB ( N DL,BWP
RB +1 )/2)⌉ bits

- N DL,BWP
RB is the size of CORESET 0

- Time domain resource assignment – 4 bits as defined in Clause [Link] of [6, TS38.214]

- VRB-to-PRB mapping – 1 bit according to Table [Link].2-5

- Modulation and coding scheme – 5 bits as defined in Clause 5.1.3 of [6, TS38.214], using Table [Link]-1

- Redundancy version – 2 bits as defined in Table [Link].1-2

- System information indicator – 1 bit as defined in Table [Link].1-2

- Reserved bits – 17 bits for operation in a cell with shared spectrum channel access in frequency range 1 or for
operation in a cell in frequency range 2-2; otherwise 15 bits

The following information is transmitted by means of the DCI format 1_0 with CRC scrambled by RA-RNTI or MsgB-
RNTI:

- Frequency domain resource assignment –

⌈log 2 ( N DL,BWP
RB ( N DL,BWP
RB +1 )/2)⌉ bits

- N DL,BWP
RB is the size of CORESET 0 if CORESET 0 is configured for the cell and is the size of initial
DL bandwidth part if CORESET 0 is not configured for the cell

- Time domain resource assignment – 4 bits as defined in Clause [Link] of [6, TS38.214]

- VRB-to-PRB mapping – 1 bit according to Table [Link].2-5

- Modulation and coding scheme – 5 bits as defined in Clause 5.1.3 of [6, TS38.214], using Table [Link]-1

- TB scaling – 2 bits as defined in Clause [Link] of [6, TS38.214]

- LSBs of SFN – 2 bits for the DCI format 1_0 with CRC scrambled by MsgB-RNTI as defined in Clause 8.2A of
[5, TS 38.213] if msgB-responseWindow is configured to be larger than 10 ms; or 2 bits for the DCI format 1_0
with CRC scrambled by RA-RNTI as defined in Clause 8.2 of [5, TS 38.213] for operation in a cell with shared
spectrum channel access if ra-ResponseWindow or ra-ResponseWindow-v1610 is configured to be larger than 10
ms; 0 bit otherwise

- Reserved bits – (16 – A) bits for operation in a cell without shared spectrum access in frequency range 1 and
frequency range 2-1, (18 – A) for operation in a cell with shared spectrum access in frequency range 1 or for
operation in a cell in frequency range 2-2, where the value of A is the number of bits for the field of 'LSBs of
SFN' as defined above

The following information is transmitted by means of the DCI format 1_0 with CRC scrambled by TC-RNTI:

- Identifier for DCI formats – 1 bit

- The value of this bit field is always set to 1, indicating a DL DCI format

- Frequency domain resource assignment –

⌈log 2 ( N DL,BWP
RB ( N DL,BWP
RB +1 )/2)⌉ bits

- N DL,BWP
RB is the size of CORESET 0

3GPP
Release 17 170 3GPP TS 38.212 V17.5.0 (2023-03)

- Time domain resource assignment – 4 bits as defined in Clause [Link] of [6, TS38.214]

- VRB-to-PRB mapping – 1 bit according to Table [Link].2-5

- Modulation and coding scheme – 5 bits as defined in Clause 5.1.3 of [6, TS38.214], using Table [Link]-1

- New data indicator – 1 bit

- Redundancy version – 2 bits as defined in Table [Link].1-2

- HARQ process number – 4 bits

- Downlink assignment index – 2 bits, reserved

- TPC command for scheduled PUCCH – 2 bits as defined in Clause 7.2.1 of [5, TS38.213]

- PUCCH resource indicator – 3 bits as defined in Clause 9.2.3 of [5, TS38.213]

- PDSCH-to-HARQ_feedback timing indicator – 3 bits as defined in Clause 9.2.3 of [5, TS38.213]

Table [Link].1-1: Short Message indicator

Bit field Short Message indicator

00 Reserved
01 Only scheduling information for Paging, and TRS availability indication if trs-
ResourceSetConfig is configured, are present in the DCI
10 Only short message, and TRS availability indication if trs-ResourceSetConfig is
configured, are present in the DCI
11 Both scheduling information for Paging, TRS availability indication if trs-
ResourceSetConfig is configured and short message are present in the DCI

Table [Link].1-2: System information indicator

Bit field System information indicator

0 SIB1 [9, TS38.331, Clause 5.2.1]
1 SI message [9, TS38.331, Clause 5.2.1]

[Link].2 Format 1_1

DCI format 1_1 is used for the scheduling of one or multiple PDSCH in one cell.

The following information is transmitted by means of the DCI format 1_1 with CRC scrambled by C-RNTI or CS-
RNTI or MCS-C-RNTI:

- Identifier for DCI formats – 1 bits

- The value of this bit field is always set to 1, indicating a DL DCI format

- Carrier indicator – 0 or 3 bits as defined in Clause 10.1 of [5, TS 38.213]. This field is reserved when this format
is carried by PDCCH on the primary cell and the UE is configured for scheduling on the primary cell from an
SCell, with the same number of bits as that in this format carried by PDCCH on the SCell for scheduling on the
primary cell.

3GPP
Release 17 171 3GPP TS 38.212 V17.5.0 (2023-03)

- Bandwidth part indicator – 0, 1 or 2 bits as determined by the number of DL BWPs configured by

higher layers, excluding the initial DL bandwidth part. The bitwidth for this field is determined as
⌈log2 ( nBWP )⌉
bits, where

-
n BWP=n BWP,RRC +1 if , in which case the bandwidth part indicator is equivalent to the ascending
order of the higher layer parameter BWP-Id;

- otherwise
n BWP=n BWP,RRC , in which case the bandwidth part indicator is defined in Table [Link].2-1;

If a UE does not support active BWP change via DCI, the UE ignores this bit field.
DL,BWP
- Frequency domain resource assignment – number of bits determined by the following, where N RB is the size
of the active DL bandwidth part:

-
N RBG bits if only resource allocation type 0 is configured, where N RBG is defined in Clause [Link].1 of [6,
TS38.214],

-
⌈log 2 ( N DL,BWP
RB ( N DL,BWP
RB +1 )/2)⌉ bits if only resource allocation type 1 is configured, or

max ( ⌈ log 2 ( N DL,BWP ( N DL,BWP +1)/ 2 )⌉, N RBG )+1

- RB RB bits if resourceAllocation is configured as
'dynamicSwitch'.

- If resourceAllocation is configured as 'dynamicSwitch', the MSB bit is used to indicate resource allocation
type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0 and the bit
value of 1 indicates resource allocation type 1.

- For resource allocation type 0, the

N RBG LSBs provide the resource allocation as defined in Clause [Link].1
of [6, TS 38.214].

- For resource allocation type 1, the

⌈log ( N DL,BWP ( N DL,BWP
2 RB RB +1 )/2)⌉ LSBs provide the resource allocation as
defined in Clause [Link].2 of [6, TS 38.214]

If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and if
resourceAllocation is configured as 'dynamicSwitch' for the indicated bandwidth part, the UE assumes resource
allocation type 0 for the indicated bandwidth part if the bitwidth of the "Frequency domain resource assignment"
field of the active bandwidth part is smaller than the bitwidth of the "Frequency domain resource assignment"
field of the indicated bandwidth part.

- Time domain resource assignment – 0, 1, 2, 3, 4, 5 or 6 bits

- If the higher layer parameter pdsch-TimeDomainAllocationListForMultiPDSCH is not configured and if the

higher layer parameter pdsch-TimeDomainAllocationList is configured, 0, 1, 2, 3 or 4 bits as defined in
Clause [Link] of [6, TS 38.214]. The bitwidth for this field is determined as ⌈log 2 ( I )⌉ bits, where I is the
number of entries in the higher layer parameter pdsch-TimeDomainAllocationList if the higher layer
parameter is configured;

- if the higher layer parameter pdsch-TimeDomainAllocationListForMultiPDSCH is configured, 0, 1, 2, 3, 4, 5

or 6 bits as defined in Clause [Link] of [6, TS38.214]. The bitwidth for this field is determined as
⌈ log 2 (I ) ⌉ bits, where I is the number of entries in the higher layer parameter pdsch-
TimeDomainAllocationListForMultiPDSCH;

- otherwise I is the number of entries in the default table.

- VRB-to-PRB mapping – 0 or 1 bit:

- 0 bit if only resource allocation type 0 is configured or if interleaved VRB-to-PRB mapping is not configured
by high layers;

3GPP
Release 17 172 3GPP TS 38.212 V17.5.0 (2023-03)

- 1 bit according to Table [Link].2-5 otherwise, only applicable to resource allocation type 1, as defined in
Clause [Link] of [4, TS 38.211].

- PRB bundling size indicator – 0 bit if the higher layer parameter prb-BundlingType is not configured or is set to
'staticBundling', or 1 bit if the higher layer parameter prb-BundlingType is set to 'dynamicBundling' according to
Clause [Link] of [6, TS 38.214].

- Rate matching indicator – 0, 1, or 2 bits according to higher layer parameters rateMatchPatternGroup1 and
rateMatchPatternGroup2, where the MSB is used to indicate rateMatchPatternGroup1 and the LSB is used to
indicate rateMatchPatternGroup2 when there are two groups.

- ZP CSI-RS trigger – 0, 1, or 2 bits as defined in Clause [Link] of [6, TS 38.214]. The bitwidth for this field is
determined as ⌈log 2 ( nZP +1)⌉ bits, where n ZP is the number of aperiodic ZP CSI-RS resource sets configured by
higher layer.

For transport block 1:

- Modulation and coding scheme – 5 bits as defined in Clause [Link] of [6, TS 38.214]

- New data indicator – 1 bit if the number of scheduled PDSCH indicated by the Time domain resource
assignment field is 1; otherwise 2, 3, 4, 5, 6, 7 or 8 bits determined based on the maximum number of
schedulable PDSCH among all entries in the higher layer parameter pdsch-
TimeDomainResourceAllocationListForMultiPDSCH, where each bit corresponds to one scheduled PDSCH
as defined in clause 5.1.3 in [6, TS 38.214].

- Redundancy version – number of bits determined by the following:

- 2 bits as defined in Table [Link].1-2 if the number of scheduled PDSCH indicated by the Time domain
resource assignment field is 1;

- otherwise 2, 3, 4, 5, 6, 7 or 8 bits determined by the maximum number of schedulable PDSCHs among all
entries in the higher layer parameter pdsch-TimeDomainResourceAllocationListForMultiPDSCH, where
each bit corresponds to one scheduled PDSCH as defined in clause 5.1.3 in [6, TS 38.214] and
redundancy version is determined according to Table [Link].2-34.

For transport block 2 (only present if maxNrofCodeWordsScheduledByDCI equals 2):

- Modulation and coding scheme – 5 bits as defined in Clause [Link] of [6, TS 38.214]

- Redundancy version – number of bits determined by the following:

- 2 bits as defined in Table [Link].1-2 if the number of scheduled PDSCH indicated by the Time domain
resource assignment field is 1;

If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and the value
of maxNrofCodeWordsScheduledByDCI for the indicated bandwidth part equals 2 and the value of
maxNrofCodeWordsScheduledByDCI for the active bandwidth part equals 1, the UE assumes zeros are padded
when interpreting the "Modulation and coding scheme", "New data indicator", and "Redundancy version" fields
of transport block 2 according to Clause 12 of [5, TS38.213], and the UE ignores the "Modulation and coding
scheme", "New data indicator", and "Redundancy version" fields of transport block 2 for the indicated
bandwidth part.

3GPP
Release 17 173 3GPP TS 38.212 V17.5.0 (2023-03)

- HARQ process number – 5 bits if higher layer parameter harq-ProcessNumberSizeDCI-1-1 is configured;

otherwise 4 bits

- Downlink assignment index – number of bits as defined in the following

- 6 bits if more than one serving cell are configured in the DL and the higher layer parameter nfi-TotalDAI-
Included is configured. The 4 MSB bits are the counter DAI and the total DAI for the scheduled PDSCH
group, and the 2 LSB bits are the total DAI for the non-scheduled PDSCH group.

- 4 bits if only one serving cell is configured in the DL and the higher layer parameter nfi-TotalDAI-Included is
configured. The 2 MSB bits are the counter DAI for the scheduled PDSCH group, and the 2 LSB bits are the
total DAI for the non-scheduled PDSCH group;

- 4 bits if more than one serving cell are configured in the DL, the higher layer parameter pdsch-HARQ-ACK-
Codebook=dynamic or pdsch-HARQ-ACK-Codebook-r16= enhancedDynamic, and nfi-TotalDAI-Included is
not configured, where the 2 MSB bits are the counter DAI and the 2 LSB bits are the total DAI;

- 4 bits if one serving cell is configured in the DL, and the higher layer parameter pdsch-HARQ-ACK-
Codebook=dynamic, and 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, where the 2 MSB bits are the counter
DAI and the 2 LSB bits are the total DAI;

- 2 bits if only one serving cell is configured in the DL, the higher layer parameter pdsch-HARQ-ACK-
Codebook=dynamic or pdsch-HARQ-ACK-Codebook-r16=enhancedDynamic, and nfi-TotalDAI-Included is
not configured, when the UE is not configured with coresetPoolIndex or the value of coresetPoolIndex is the
same for all CORESETs if coresetPoolIndex is provided or the UE is not configured with
ackNackFeedbackMode = joint, where the 2 bits are the counter DAI;

- 0 bits otherwise.

If the UE is configured with a PUCCH-SCell, the number of serving cells is determined within a PUCCH group.

If the UE is configured with a PUCCH-SCell, pdsch-HARQ-ACK-Codebook is replaced by pdsch-HARQ-ACK-

Codebook-secondaryPUCCHgroup-r16 if present for the secondary PUCCH group.

If higher layer parameter priorityIndicatorDCI-1-1 is configured, if the bit width of the Downlink assignment
index in DCI format 1_1 for one HARQ-ACK codebook is not equal to that of the Downlink assignment index in
DCI format 1_1 for the other HARQ-ACK codebook, a number of most significant bits with value set to '0' are
inserted to smaller Downlink assignment index until the bit width of the Downlink assignment index in DCI
format 1_1 for the two HARQ-ACK codebooks are the same.

- TPC command for scheduled PUCCH – 2 bits as defined in Clause 7.2.1 of [5, TS 38.213]

- Second TPC command for scheduled PUCCH – 2 bits as defined in Clause 7.2.1 of [5, TS 38.213] if higher layer
parameter SecondTPCFieldDCI-1-1 is configured; 0 bit otherwise.

- PUCCH resource indicator – 3 bits as defined in Clause 9.2.3 of [5, TS 38.213]

If higher layer parameter priorityIndicatorDCI-1-1 is configured, if the bit width of the PDSCH-to-
HARQ_feedback timing indicator in DCI format 1_1 for one HARQ-ACK codebook is not equal to that of the
PDSCH-to-HARQ_feedback timing indicator in DCI format 1_1 for the other HARQ-ACK codebook on the
same cell for PUCCH transmission, a number of most significant bits with value set to '0' are inserted to smaller
PDSCH-to-HARQ_feedback timing indicator until the bit width of the PDSCH-to-HARQ_feedback timing
indicator in DCI format 1_1 for the two HARQ-ACK codebooks are the same.

If higher layer parameter pucch-sSCellDyn is configured, if the bit width of the PDSCH-to-HARQ_feedback
timing indicator in DCI format 1_1 associated with one cell for PUCCH transmission is not equal to that of the
PDSCH-to-HARQ_feedback timing indicator in DCI format 1_1 associated with the other cell for PUCCH
transmision, a number of most significant bits with value set to '0' are inserted to smaller PDSCH-to-

3GPP
Release 17 174 3GPP TS 38.212 V17.5.0 (2023-03)

HARQ_feedback timing indicator until the bit width of the PDSCH-to-HARQ_feedback timing indicator in DCI
format 1_1 associated with the two cells are the same.

If the UE is configured with a PUCCH-SCell, pucch-sSCellDyn is replaced by pucch-

sSCellDynSecondaryPUCCHgroup for the secondary PUCCH group.

- One-shot HARQ-ACK request – 0 or 1 bit.

- 1 bit if higher layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 or pdsch-HARQ-ACK-

EnhType3ToAddModList is configured;

- 0 bit otherwise.

If the UE is configured with a PUCCH-SCell, pdsch-HARQ-ACK-EnhType3ToAddModList is replaced by

pdsch-HARQ-ACK-EnhType3SecondaryToAddModList for the secondary PUCCH group.

- Enhanced Type 3 codebook indicator - 0, 1, 2, or 3 bits.

- 0 bit if pdsch-HARQ-ACK-EnhType3DCI-Field is not configured;

- ⌈ log2 (nCB )⌉ bits otherwise, where nCB is the number of entries in the higher layer parameter pdsch-
HARQ-ACK-EnhType3ToAddModList.

If the UE is configured with a PUCCH-SCell, pdsch-HARQ-ACK-EnhType3DCI-Field is replaced by pdsch-

HARQ-ACK-EnhType3DCI-FieldSecondaryPUCCHgroup for the secondary PUCCH group, and pdsch-HARQ-
ACK-EnhType3ToAddModList is replaced by pdsch-HARQ-ACK-EnhType3SecondaryList for the secondary
PUCCH group.

- PDSCH group index – 0 or 1 bit.

- 1 bit if the higher layer parameter pdsch-HARQ-ACK-Codebook-r16= enhancedDynamic;

- 0 bit otherwise.

- New feedback indicator – 0, 1 or 2 bits.

- 1 bit if the higher layer parameter pdsch-HARQ-ACK-Codebook-r16= enhancedDynamic and the higher
layer parameter nfi-TotalDAI-Included is not configured;

- 2 bits if the higher layer parameter pdsch-HARQ-ACK-Codebook-r16= enhancedDynamic and the higher
layer parameter nfi-TotalDAI-Included=true; the MSB corresponds to the scheduled PDSCH group, and the
LSB corresponds to the non-scheduled PDSCH group, as defined in [TS38.213] clause [Link]

- 0 bit otherwise.

- Number of requested PDSCH group(s) – 0 or 1 bit.

- 1 bit if the higher layer parameter pdsch-HARQ-ACK-Codebook-r16= enhancedDynamic;

- 0 bit otherwise.

- HARQ-ACK retransmission indicator – 0 or 1 bit.

- 1 bit if higher layer parameter pdsch-HARQ-ACK-Retx is configured.

- 0 bit otherwise.

If the UE is configured with a PUCCH-SCell, pdsch-HARQ-ACK-Retx is replaced by pdsch-HARQ-ACK-

RetxSecondaryPUCCHgroup for the secondary PUCCH group.

- Antenna port(s) – 4, 5, or 6 bits as defined by Tables [Link].2-1/2/3/4 and Tables [Link].2-1A/2A/3A/4A,

where the number of CDM groups without data of values 1, 2, and 3 refers to CDM groups {0}, {0,1}, and {0,
1,2} respectively. The antenna ports { 0, . .. , υ−1 } shall be determined according to the ordering of DMRS port(s)
p p
given by Tables [Link].2-1/2/3/4 or Tables [Link].2-1A/2A/3A/4A. When a UE receives an activation
command that maps at least one codepoint of DCI field 'Transmission Configuration Indication' to two TCI
states, the UE shall use Table [Link].2-1A/2A/3A/4A; otherwise, it shall use Tables [Link].2-1/2/3/4. The UE

3GPP
Release 17 175 3GPP TS 38.212 V17.5.0 (2023-03)

can receive an entry with DMRS ports equals to 1000, 1002, 1003 when two TCI states are indicated in a
codepoint of DCI field 'Transmission Configuration Indication'.

If a UE is configured with both dmrs-DownlinkForPDSCH-MappingTypeA and dmrs-DownlinkForPDSCH-

MappingTypeB, the bitwidth of this field equals , where is the "Antenna ports" bitwidth
derived according to dmrs-DownlinkForPDSCH-MappingTypeA and is the "Antenna ports" bitwidth derived

according to dmrs-DownlinkForPDSCH-MappingTypeB. A number of zeros are padded in the MSB of

this field, if the mapping type of the PDSCH corresponds to the smaller value of and .

- Transmission configuration indication – 0 bit if higher layer parameter tci-PresentInDCI is not enabled;
otherwise 3 bits as defined in Clause 5.1.5 of [6, TS38.214].

If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part,

- if the higher layer parameter tci-PresentInDCI is not enabled for the CORESET used for the PDCCH
carrying the DCI format 1_1,

- the UE assumes tci-PresentInDCI is not enabled for all CORESETs in the indicated bandwidth part;

- otherwise,

- the UE assumes tci-PresentInDCI is enabled for all CORESETs in the indicated bandwidth part.

- SRS offset indicator – 0, 1 or 2 bits.

- CBG transmission information (CBGTI) – 0 bit if higher layer parameter codeBlockGroupTransmission for
PDSCH is not configured, otherwise, 2, 4, 6, or 8 bits as defined in Clause 5.1.7 of [6, TS38.214], determined by
the higher layer parameters maxCodeBlockGroupsPerTransportBlock and maxNrofCodeWordsScheduledByDCI
for the PDSCH.

If higher layer parameter priorityIndicatorDCI-1-1 is configured, if the bit width of the CBG transmission
information in DCI format 1_1 for one HARQ-ACK codebook is not equal to that of the CBG transmission
information in DCI format 1_1 for the other HARQ-ACK codebook, a number of most significant bits with
value set to '0' are inserted to smaller CBG transmission information until the bit width of the CBG transmission
information in DCI format 1_1 for the two HARQ-ACK codebooks are the same.

- CBG flushing out information (CBGFI) – 1 bit if higher layer parameter codeBlockGroupFlushIndicator is
configured as "TRUE", 0 bit otherwise.

If higher layer parameter priorityIndicatorDCI-1-1 is configured, if the bit width of the CBG flushing out
information in DCI format 1_1 for one HARQ-ACK codebook is not equal to that of the CBG flushing out
information in DCI format 1_1 for the other HARQ-ACK codebook, a number of most significant bits with
value set to '0' are inserted to smaller CBG flushing out information until the bit width of the CBG flushing out
information in DCI format 1_1 for the two HARQ-ACK codebooks are the same.

- DMRS sequence initialization – 1 bit.

3GPP
Release 17 176 3GPP TS 38.212 V17.5.0 (2023-03)

- Priority indicator – 0 bit if higher layer parameter priorityIndicatorDCI-1-1 is not configured; otherwise 1 bit as
defined in Clause 9 in [5, TS 38.213].

- ChannelAccess-CPext – 0, 1, 2, 3 or 4 bits. The bitwidth for this field is determined as ⌈ log 2 (I )⌉ bits, where I
is the number of entries in the higher layer parameter ul-AccessConfigListDCI-1-1 or in Table [Link].1-4A if
channelAccessMode-r16 = "semiStatic" is provided, for operation in a cell with shared spectrum channel access
in frequency range 1, or for operation in frequency range 2-2 if ChannelAccessMode2-r17 is provided; otherwise
0 bit. One or more entries from Table [Link].2-6 or Table [Link].2-6A are configured by the higher layer
parameter ul-AccessConfigListDCI-1-1.

- Minimum applicable scheduling offset indicator – 0 or 1 bit

- 0 bit if higher layer parameter minimumSchedulingOffsetK0 is not configured;

- 1 bit if higher layer parameter minimumSchedulingOffsetK0 is configured. The 1 bit indication is used to
determine the minimum applicable K0 for the active DL BWP and the minimum applicable K2 value for the
active UL BWP, if configured respectively, according to Table [Link].2-33. If the minimum applicable K0 is
indicated, the minimum applicable value of the aperiodic CSI-RS triggering offset for an active DL BWP
shall be the same as the minimum applicable K0 value.

If one-shot HARQ-ACK request is not present or set to '0', and all bits of frequency domain resource assignment
are set to 0 for resource allocation type 0 or set to 1 for resource allocation type 1 or set to 0 or 1 for dynamic
switch resource allocation type, this field is reserved and the following fields among the fields above are used for
SCell dormancy indication, where each bit corresponds to one of the configured SCell(s), with MSB to LSB of
the following fields concatenated in the order below corresponding to the SCell with lowest to highest SCell
index

- Modulation and coding scheme of transport block 1

- New data indicator of transport block 1

- Redundancy version of transport block 1

- HARQ process number

- Antenna port(s)

- DMRS sequence initialization

- PDCCH monitoring adaptation indication – 0, 1 or 2 bits

- 1 or 2 bits, if searchSpaceGroupIdList-r17 is not configured and if pdcch-SkippingDurationList is configured

- 1 bit if the UE is configured with only one duration by pdcch-SkippingDurationList;

- 2 bits if the UE is configured with more than one duration by pdcch-SkippingDurationList.

- 1 or 2 bits, if pdcch-SkippingDurationList is not configured and if searchSpaceGroupIdList-r17 is configured

- 2 bits if the UE is configured by searchSpaceGroupIdList-r17 with search space set(s) with group index
0, search space set(s) with group index 1 and search space set(s) with group index 2;

- 2 bits, if pdcch-SkippingDurationList is configured and if searchSpaceGroupIdList-r17 is configured

3GPP
Release 17 177 3GPP TS 38.212 V17.5.0 (2023-03)

- 0 bit, otherwise

- PUCCH Cell indicator – 0 or 1 bit.

- 1 bit if higher layer parameter pucch-sSCellDyn is configured.

- 0 bit otherwise.

If the UE is configured with a PUCCH-SCell, pucch-sSCellDyn is replaced by pucch-

sSCellDynSecondaryPUCCHgroup for the secondary PUCCH group.

If DCI formats 1_1 are monitored in multiple search spaces associated with multiple CORESETs in a BWP for
scheduling the same serving cell, zeros shall be appended until the payload size of the DCI formats 1_1 monitored in
the multiple search spaces equal to the maximum payload size of the DCI format 1_1 monitored in the multiple search
spaces.

If the number of information bits in DCI format 1_1 scheduling a single PDSCH prior to padding is not equal to the
number of information bits in DCI format 1_1 scheduling multiple PDSCHs for the same serving cell, zeros shall be
appended to the DCI format 1_1 with smaller size until the payload size is the same for scheduling a single PDSCH and
multiple PDSCHs.

For a UE configured with scheduling on the primary cell from an SCell, if prior to padding the number of information
bits in DCI format 1_1 carried by PDCCH on the primary cell is not equal to the number of information bits in DCI
format 1_1 carried by PDCCH on the SCell for scheduling on the primary cell, zeros shall be appended to the DCI
format 1_1 with smaller size until the payload size is the same.

- If application of step 4C in clause [Link] results in additional zero padding for DCI format 1_1 for scheduling
on the primary cell, corresponding zeros shall be appended to both DCI format 1_1 monitored on the primary
cell and DCI format 1_1 monitored on the SCell for scheduling on the primary cell.

- If the SCell is deactivated and firstActiveDownlinkBWP-Id is not set to dormant BWP, the UE determines the
number of information bits in DCI format 1_1 carried by PDCCH on the primary cell based on a DL BWP
provided by firstActiveDownlinkBWP-Id for the SCell. If the active DL BWP of the SCell is a dormant DL
BWP, or if the SCell is deactivated and firstActiveDownlinkBWP-Id is set to dormant BWP, the UE determines
the number of information bits in DCI format 1_1 carried by PDCCH on the primary cell based on a DL BWP
provided by firstWithinActiveTimeBWP-Id for the SCell if provided; otherwise, based on a DL BWP provided by
firstOutsideActiveTimeBWP-Id for the SCell.

Table [Link].2-1: Antenna port(s) (1000 + DMRS port), dmrs-Type=1, maxLength=1

One Codeword:
Codeword 0 enabled,
Codeword 1 disabled
Number of DMRS
DMRS
Value CDM group(s)
port(s)
without data
0 1 0
1 1 1
2 1 0,1
3 2 0
4 2 1
5 2 2
6 2 3
7 2 0,1
8 2 2,3
9 2 0-2
10 2 0-3
11 2 0,2
12-15 Reserved Reserved

3GPP
Release 17 178 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-1A: Antenna port(s) (1000 + DMRS port), dmrs-Type=1, maxLength=1

One Codeword:
Codeword 0 enabled,
Codeword 1 disabled
Number of DMRS
DMRS
Value CDM group(s)
port(s)
without data
0 1 0
1 1 1
2 1 0,1
3 2 0
4 2 1
5 2 2
6 2 3
7 2 0,1
8 2 2,3
9 2 0-2
10 2 0-3
11 2 0,2
12 2 0,2,3
13-15 Reserved Reserved

Table [Link].2-2: Antenna port(s) (1000 + DMRS port), dmrs-Type=1, maxLength=2

One Codeword: Two Codewords:
Codeword 0 enabled, Codeword 0 enabled,
Codeword 1 disabled Codeword 1 enabled
Number of Number of
Number of Number of
DMRS CDM DMRS DMRS CDM
Value front-load Value DMRS port(s) front-load
group(s) port(s) group(s)
symbols symbols
without data without data
0 1 0 1 0 2 0-4 2
1 1 1 1 1 2 0,1,2,3,4,6 2
2 1 0,1 1 2 2 0,1,2,3,4,5,6 2
3 2 0 1 3 2 0,1,2,3,4,5,6,7 2
4 2 1 1 4-31 reserved reserved reserved
5 2 2 1
6 2 3 1
7 2 0,1 1
8 2 2,3 1
9 2 0-2 1
10 2 0-3 1
11 2 0,2 1
12 2 0 2
13 2 1 2
14 2 2 2
15 2 3 2
16 2 4 2
17 2 5 2
18 2 6 2
19 2 7 2
20 2 0,1 2
21 2 2,3 2
22 2 4,5 2
23 2 6,7 2
24 2 0,4 2
25 2 2,6 2
26 2 0,1,4 2
27 2 2,3,6 2
28 2 0,1,4,5 2
29 2 2,3,6,7 2
30 2 0,2,4,6 2
31 Reserved Reserved Reserved

3GPP
Release 17 179 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-2A: Antenna port(s) (1000 + DMRS port), dmrs-Type=1, maxLength=2

One Codeword: Two Codewords:
Codeword 0 enabled, Codeword 0 enabled,
Codeword 1 disabled Codeword 1 enabled
Number of Number of
Number of Number of
Valu DMRS CDM DMRS DMRS CDM
front-load Value DMRS port(s) front-load
e group(s) port(s) group(s)
symbols symbols
without data without data
0 1 0 1 0 2 0-4 2
1 1 1 1 1 2 0,1,2,3,4,6 2
2 1 0,1 1 2 2 0,1,2,3,4,5,6 2
3 2 0 1 3 2 0,1,2,3,4,5,6,7 2
4 2 1 1 4-31 reserved reserved reserved
5 2 2 1
6 2 3 1
7 2 0,1 1
8 2 2,3 1
9 2 0-2 1
10 2 0-3 1
11 2 0,2 1
12 2 0 2
13 2 1 2
14 2 2 2
15 2 3 2
16 2 4 2
17 2 5 2
18 2 6 2
19 2 7 2
20 2 0,1 2
21 2 2,3 2
22 2 4,5 2
23 2 6,7 2
24 2 0,4 2
25 2 2,6 2
26 2 0,1,4 2
27 2 2,3,6 2
28 2 0,1,4,5 2
29 2 2,3,6,7 2
30 2 0,2,4,6 2
31 2 0,2,3 1

3GPP
Release 17 180 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-3: Antenna port(s) (1000 + DMRS port), dmrs-Type=2, maxLength=1

One codeword: Two codewords:
Codeword 0 enabled, Codeword 0 enabled,
Codeword 1 disabled Codeword 1 enabled
Number of Number of
DMRS CDM DMRS DMRS CDM
Value Value DMRS port(s)
group(s) port(s) group(s)
without data without data
0 1 0 0 3 0-4
1 1 1 1 3 0-5
2 1 0,1 2-31 reserved reserved
3 2 0
4 2 1
5 2 2
6 2 3
7 2 0,1
8 2 2,3
9 2 0-2
10 2 0-3
11 3 0
12 3 1
13 3 2
14 3 3
15 3 4
16 3 5
17 3 0,1
18 3 2,3
19 3 4,5
20 3 0-2
21 3 3-5
22 3 0-3
23 2 0,2
24-31 Reserved Reserved

3GPP
Release 17 181 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-3A: Antenna port(s) (1000 + DMRS port), dmrs-Type=2, maxLength=1

3GPP
Release 17 182 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-4: Antenna port(s) (1000 + DMRS port), dmrs-Type=2, maxLength=2

3GPP
Release 17 183 3GPP TS 38.212 V17.5.0 (2023-03)

One codeword: Two Codewords:

Codeword 0 enabled, Codeword 0 enabled,
Codeword 1 disabled Codeword 1 enabled
Number of Number of
Number of Number of
Valu DMRS CDM DMRS DMRS CDM
front-load Value DMRS port(s) front-load
e group(s) port(s) group(s)
symbols symbols
without data without data
0 1 0 1 0 3 0-4 1
1 1 1 1 1 3 0-5 1
2 1 0,1 1 2 2 0,1,2,3,6 2
3 2 0 1 3 2 0,1,2,3,6,8 2
4 2 1 1 4 2 0,1,2,3,6,7,8 2
5 2 2 1 5 2 0,1,2,3,6,7,8,9 2
6 2 3 1 6-63 Reserved Reserved Reserved
7 2 0,1 1
8 2 2,3 1
9 2 0-2 1
10 2 0-3 1
11 3 0 1
12 3 1 1
13 3 2 1
14 3 3 1
15 3 4 1
16 3 5 1
17 3 0,1 1
18 3 2,3 1
19 3 4,5 1
20 3 0-2 1
21 3 3-5 1
22 3 0-3 1
23 2 0,2 1
24 3 0 2
25 3 1 2
26 3 2 2
27 3 3 2
28 3 4 2
29 3 5 2
30 3 6 2
31 3 7 2
32 3 8 2
33 3 9 2
34 3 10 2
35 3 11 2
36 3 0,1 2
37 3 2,3 2
38 3 4,5 2
39 3 6,7 2
40 3 8,9 2
41 3 10,11 2
42 3 0,1,6 2
43 3 2,3,8 2
44 3 4,5,10 2
45 3 0,1,6,7 2
46 3 2,3,8,9 2
47 3 4,5,10,11 2
48 1 0 2
49 1 1 2
50 1 6 2
51 1 7 2
52 1 0,1 2
53 1 6,7 2
54 2 0,1 2
55 2 2,3 2
56 2 6,7 2
57 2 8,9 2
58-63 Reserved Reserved Reserved

3GPP
Release 17 184 3GPP TS 38.212 V17.5.0 (2023-03)

3GPP
Release 17 185 3GPP TS 38.212 V17.5.0 (2023-03)

Table [Link].2-4A: Antenna port(s) (1000 + DMRS port), dmrs-Type=2, maxLength=2

3GPP
Release 17 186 3GPP TS 38.212 V17.5.0 (2023-03)

One codeword: Two Codewords:

3GPP
Release 17 187 3GPP TS 38.212 V17.5.0 (2023-03)

59-63 Reserved Reserved Reserved

Table [Link].2-5: VRB-to-PRB mapping

Bit field mapped to index VRB-to-PRB mapping

0 Non-interleaved
1 Interleaved

Table [Link].2-6: Allowed entries for DCI format 1_1 and DCI format 1_2, configured by higher layer
parameter ul-AccessConfigListDCI-1-1 and ul-AccessConfigListDCI-1-2, respectively, in frequency
range 1

The CP extension Text index

Entry
Channel Access Type defined in Clause 5.3.1 of [4, TS
index
38.211]
0 Type2C-ULChannelAccess defined in [clause [Link].3 in 37.213] 0
1 Type2C-ULChannelAccess defined in [clause [Link].3 in 37.213] 2
2 Type2B-ULChannelAccess defined in [clause [Link].2 in 37.213] 0
3 Type2B-ULChannelAccess defined in [clause [Link].2 in 37.213] 2
4 Type2A-ULChannelAccess defined in [clause [Link].1 in 37.213] 0
5 Type2A-ULChannelAccess defined in [clause [Link].1 in 37.213] 1
6 Type2A-ULChannelAccess defined in [clause [Link].1 in 37.213] 3
7 Type1-ULChannelAccess defined in [clause [Link] in 37.213] 0
8 Type1-ULChannelAccess defined in [clause [Link] in 37.213] 1
9 Type1-ULChannelAccess defined in [clause [Link] in 37.213] 2
10 Type1-ULChannelAccess defined in [clause [Link] in 37.213] 3

Table [Link].2-6A: Allowed entries for DCI format 1_1 and DCI format 1_2, configured by higher layer
parameter ul-AccessConfigListDCI-1-1 in frequency range 2-2

[Link].3 Format 1_2

DCI format 1_2 is used for the scheduling of PDSCH in one cell.

The following information is transmitted by means of the DCI format 1_2 with CRC scrambled by C-RNTI or CS-
RNTI or MCS-C-RNTI:

- Identifier for DCI formats – 1 bits

- The value of this bit field is always set to 1, indicating a DL DCI format.

- Carrier indicator – 0, 1, 2 or 3 bits determined by higher layer parameter carrierIndicatorSizeDCI-1-2, as defined

- Bandwidth part indicator – 0, 1 or 2 bits as determined by the number of DL BWPs n BWP , RRC configured by
higher layers, excluding the initial DL bandwidth part. The bitwidth for this field is determined as
⌈ log 2 (n BWP)⌉ bits, where

- n BWP=n BWP , RRC +1if n BWP , RRC ≤ 3, in which case the bandwidth part indicator is equivalent to the
ascending order of the higher layer parameter BWP-Id;

- otherwise n BWP =n BWP , RRC , in which case the bandwidth part indicator is defined in Table [Link].2-1;

3GPP
Release 17 188 3GPP TS 38.212 V17.5.0 (2023-03)

If a UE does not support active BWP change via DCI, the UE ignores this bit field.

- Frequency domain resource assignment – number of bits determined by the following:

- N RBG bits if only resource allocation type 0 is configured, where N RBG is defined in Clause [Link].1 of [6,
TS 38.214];

- ⌈ log 2 ( N RBG ,K 2 ( N RBG , K 2 +1 ) /2 ) ⌉ bits if only resource allocation type 1 is configured, or

max ( ⌈ log 2 ( N RBG , K 2 ( N RBG , K 2+ 1 ) /2 ) ⌉ , N RBG )+1 bits if resourceAllocationDCI-1-2-r16 is configured
as 'dynamicSwitch', where N RBG , K 2=⌈ N RB ( DL, BWP
+ ( N DL, BWP mod K 2 ) ) / K 2 ⌉ , N DL,
start
RB
BWP
is the size of the
start
active DL bandwidth part, N DL, BWPis defined as in clause [Link] of [4, TS 38.211] and K 2 is determined
by higher layer parameter resourceAllocationType1GranularityDCI-1-2. If the higher layer parameter
resourceAllocationType1GranularityDCI-1-2 is not configured, K 2 is equal to 1.

- If resourceAllocationDCI-1-2-r16 is configured as 'dynamicSwitch', the MSB bit is used to indicate resource

allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0
and the bit value of 1 indicates resource allocation type 1.

- For resource allocation type 0, the N RBG LSBs provide the resource allocation as defined in Clause [Link].1
of [6, TS 38.214].

- For resource allocation type 1, the ⌈ log 2 ( N RBG ,K 2 ( N RBG , K 2 +1 ) /2 ) ⌉ LSBs provide the resource
allocation as defined in Clause [Link].2 of [6, TS 38.214]

If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and if
resourceAllocationDCI-1-2-r16 is configured as 'dynamicSwitch' for the indicated bandwidth part, the UE
assumes resource allocation type 0 for the indicated bandwidth part if the bitwidth of the "Frequency domain
resource assignment" field of the active bandwidth part is smaller than the bitwidth of the "Frequency domain
resource assignment" field of the indicated bandwidth part.

- Time domain resource assignment – 0, 1, 2, 3, or 4 bits as defined in Clause [Link] of [6, TS 38.214]. The
bitwidth for this field is determined as ⌈ log 2 (I )⌉ bits, where I is the number of entries in the higher layer
parameter pdsch-TimeDomainAllocationListDCI-1-2 if the higher layer parameter is configured, or I is the
number of entries in the higher layer parameter pdsch-TimeDomainAllocationList if the higher layer parameter
pdsch-TimeDomainAllocationList is configured when the higher layer parameter pdsch-
TimeDomainAllocationListDCI-1-2 is not configured; otherwise I is the number of entries in the default table.

- VRB-to-PRB mapping – 0 or 1 bit:

- 0 bit if the higher layer parameter vrb-ToPRB-InterleaverDCI-1-2 is not configured;

- 1 bit according to Table [Link].2-5 otherwise, only applicable to resource allocation type 1, as defined in
Clause [Link] of [4, TS 38.211].

- PRB bundling size indicator – 0 bit if the higher layer parameter prb-BundlingTypeDCI-1-2 is not configured or
is set to 'static', or 1 bit if the higher layer parameter prb-BundlingTypeDCI-1-2 is set to 'dynamic' according to
Clause [Link] of [6, TS 38.214].

- Rate matching indicator – 0, 1, or 2 bits according to higher layer parameters rateMatchPatternGroup1DCI-1-2

and rateMatchPatternGroup2DCI-1-2, where the MSB is used to indicate rateMatchPatternGroup1DCI-1-2 and
the LSB is used to indicate rateMatchPatternGroup2DCI-1-2 when there are two groups.

- ZP CSI-RS trigger – 0, 1, or 2 bits as defined in Clause [Link] of [6, TS 38.214]. The bitwidth for this field is
determined as ⌈ log 2 (n ZP +1)⌉ bits, where n ZP is the number of aperiodic ZP CSI-RS resource sets configured
by higher layer parameter aperiodicZP-CSI-RS-ResourceSetsToAddModListDCI-1-2.

- Modulation and coding scheme – 5 bits as defined in Clause [Link] of [6, TS 38.214]

- New data indicator – 1 bit

3GPP
Release 17 189 3GPP TS 38.212 V17.5.0 (2023-03)

- Redundancy version – 0, 1 or 2 bits determined by higher layer parameter numberOfBitsForRV-DCI-1-2

- If 0 bit is configured, rvid to be applied is 0;

- 1 bit according to Table [Link].3-1;

- 2 bits according to Table [Link].1-2.

- HARQ process number – number of bits determined by the following:

- 0, 1, 2, 3, 4 or 5 bits determined by higher layer parameter harq-ProcessNumberSizeDCI-1-2-v1700 if

configured;

- otherwise 0, 1, 2, 3 or 4 bits determined by higher layer parameter harq-ProcessNumberSizeDCI-1-2

- Downlink assignment index – 0, 1, 2 or 4 bits

- 0 bit if the higher layer parameter downlinkAssignmentIndexDCI-1-2 is not configured;

- 1, 2 or 4 bits determined by higher layer parameter downlinkAssignmentIndexDCI-1-2 otherwise,

- 4 bits if more than one serving cell are configured in the DL and the higher layer parameter pdsch-
HARQ-ACK-Codebook=dynamic, where the 2 MSB bits are the counter DAI and the 2 LSB bits are the
total DAI

- 4 bits if only one serving cell is configured in the DL and the higher layer parameter pdsch-HARQ-ACK-
Codebook=dynamic, and 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, where the 2 MSB bits are the
counter DAI and the 2 LSB bits are the total DAI.

- 1 or 2 bits if only one serving cell is configured in the DL and the higher layer parameter pdsch-HARQ-
ACK-Codebook=dynamic, when the UE is not configured with coresetPoolIndex or the value of
coresetPoolIndex is the same for all CORESETs if coresetPoolIndex is provided or the UE is not
configured with ackNackFeedbackMode = joint, where the 1 bit or 2 bits are the counter DAI.

If the UE is configured with a PUCCH-SCell, the number of serving cells is determined within a PUCCH group.

If the UE is configured with a PUCCH-SCell, pdsch-HARQ-ACK-Codebook is replaced by pdsch-HARQ-ACK-

Codebook-secondaryPUCCHgroup-r16 if present for the secondary PUCCH group.

If higher layer parameter priorityIndicatorDCI-1-2 is configured, if the bit width of the Downlink assignment
index in DCI format 1_2 for one HARQ-ACK codebook is not equal to that of the Downlink assignment index in
DCI format 1_2 for the other HARQ-ACK codebook, a number of most significant bits with value set to '0' are
inserted to smaller Downlink assignment index until the bit width of the Downlink assignment index in DCI
format 1_2 for the two HARQ-ACK codebooks are the same.

- TPC command for scheduled PUCCH – 2 bits as defined in Clause 7.2.1 of [5, TS 38.213]

- Second TPC command for scheduled PUCCH – 2 bits as defined in Clause 7.2.1 of [5, TS 38.213] if higher layer
parameter SecondTPCFieldDCI-1-2 is configured; 0 bit otherwise.

- PUCCH resource indicator – 0 or 1 or 2 or 3 bits determined by higher layer parameter

numberOfBitsForPUCCH-ResourceIndicatorDCI-1-2

If higher layer parameter pucch-sSCellPattern or pucch-sSCellDynDCI-1-2 is configured, if the bit width of the
PUCCH resource indicator in DCI format 1_2 associated with one cell for PUCCH transmission is not equal to
that of the PUCCH resource indicator in DCI format 1_2 associated with the other cell for PUCCH transmission,
a number of most significant bits with value set to '0' are inserted to smaller PUCCH resource indicator until the
bit width of the PUCCH resource indicator in DCI format 1_2 associated with the two cells for PUCCH
transmissions are the same.

If the UE is configured with a PUCCH-SCell, pucch-sSCellPattern is replaced by pucch-

sSCellPatternSecondaryPUCCHgroup for the secondary PUCCH group.

3GPP
Release 17 190 3GPP TS 38.212 V17.5.0 (2023-03)

If higher layer parameter priorityIndicatorDCI-1-2 is configured, if the bit width of the PDSCH-to-
HARQ_feedback timing indicator in DCI format 1_2 for one HARQ-ACK codebook is not equal to that of the
PDSCH-to-HARQ_feedback timing indicator in DCI format 1_2 for the other HARQ-ACK codebook on the
same cell for PUCCH transmission, a number of most significant bits with value set to '0' are inserted to smaller
PDSCH-to-HARQ_feedback timing indicator until the bit width of the PDSCH-to-HARQ_feedback timing
indicator in DCI format 1_2 for the two HARQ-ACK codebooks are the same.

If higher layer parameter pucch-sSCellDynDCI-1-2 is configured, if the bit width of the PDSCH-to-
HARQ_feedback timing indicator in DCI format 1_2 associated with one cell for PUCCH transmission is not
equal to that of the PDSCH-to-HARQ_feedback timing indicator in DCI format 1_2 associated with the other
cell for PUCCH transmision, a number of most significant bits with value set to '0' are inserted to smaller
PDSCH-to-HARQ_feedback timing indicator until the bit width of the PDSCH-to-HARQ_feedback timing
indicator in DCI format 1_2 associated with the two cells are the same.

- One-shot HARQ-ACK request –0 or 1 bit.

- 1 bit if higher layer parameter pdsch-HARQ-ACK-OneShotFeedbackDCI-1-2 or pdsch-HARQ-ACK-

EnhType3DCI-1-2 is configured;

- 0 bit otherwise.

- Enhanced Type 3 codebook indicator - 0, 1, 2, or 3 bits.

- 0 bit if pdsch-HARQ-ACK-EnhType3DCI-Field-1-2 is not configured;

- ⌈ log 2 (nCB )⌉ bits otherwise, where nCB is the number of entries in the higher layer parameter pdsch-
HARQ-ACK-EnhType3ToAddModList.

If the UE is configured with a PUCCH-SCell, pdsch-HARQ-ACK-EnhType3ToAddModList is replaced by

pdsch-HARQ-ACK-EnhType3SecondaryToAddModList for the secondary PUCCH group.

- HARQ-ACK retransmission indicator – 0 or 1 bit.

- 1 bit if higher layer parameter pdsch-HARQ-ACK-retxDCI-1-2 is configured.

- 0 bit otherwise.

- Antenna port(s) – 0, 4, 5, or 6 bits

- 0 bit if higher layer parameter antennaPortsFieldPresenceDCI-1-2 is not configured;

- Otherwise 4, 5 or 6 bits as defined by Tables [Link].2-1/2/3/4 and Tables [Link].2-1A/2A/3A/4A, where the
number of CDM groups without data of values 1, 2, and 3 refers to CDM groups {0}, {0,1}, and {0, 1,2}
respectively. The antenna ports { p0 , … , p v−1 }shall be determined according to the ordering of DMRS
port(s) given by Tables [Link].2-1/2/3/4 or Tables [Link].2-1A/2A/3A/4A. When a UE receives an
activation command that maps at least one codepoint of DCI field 'Transmission Configuration Indication' to
two TCI states, the UE shall use Table [Link].2-1A/2A/3A/4A; otherwise, it shall use Tables [Link].2-
1/2/3/4.

- If a UE is configured with both dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 and dmrs-

DownlinkForPDSCH-MappingTypeB-DCI-1-2 and is configured with higher layer parameter
antennaPortsFieldPresenceDCI-1-2, the bitwidth of this field equalsmax { x A , x B } , where x A is the
"Antenna ports" bitwidth derived according to dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 and x B is
the "Antenna ports" bitwidth derived according to dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2. A
number of |x A −x B| zeros are padded in the MSB of this field, if the mapping type of the PDSCH
corresponds to the smaller value of x A and x B .

If a UE is not configured with higher layer parameter antennaPortsFieldPresenceDCI-1-2, antenna port(s) are
defined assuming bit field index value 0 in Tables [Link].2-1/2/3/4.

3GPP
Release 17 191 3GPP TS 38.212 V17.5.0 (2023-03)

- Transmission configuration indication – 0 bit if higher layer parameter tci-PresentDCI-1-2 is not configured;
otherwise 1 or 2 or 3 bits determined by higher layer parameter tci-PresentDCI-1-2 as defined in Clause 5.1.5 of
[6, TS38.214].

If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part,

- if the higher layer parameter tci-PresentDCI-1-2 is not configured for the CORESET used for the PDCCH
carrying the DCI format 1_2,

- the UE assumes tci-PresentDCI-1-2 is not configured for all CORESETs in the indicated bandwidth part;

- otherwise,

- the UE assumes tci-PresentDCI-1-2 is configured for all CORESETs in the indicated bandwidth part with
the same value configured for the CORESET used for the PDCCH carrying the DCI format 1_2.

- SRS request – 0, 1, 2 or 3 bits

- 0 bit if the higher layer parameter srs-RequestDCI-1-2 is not configured;

- 1 bit as defined by Table [Link].3-1 if the higher layer parameter srs-RequestDCI-1-2 = 1 and for UEs not
configured with supplementaryUplink in ServingCellConfig in the cell;

- 2 bits if the higher layer parameter srs-RequestDCI-1-2 = 1 and for UEs configured with
supplementaryUplink in ServingCellConfig in the cell, where the first bit is the non-SUL/SUL indicator as
defined in Table [Link].1-1 and the second bit is defined by Table [Link].3-1;

- 2 bits as defined by Table [Link].2-24 if the higher layer parameter srs-RequestDCI-1-2 = 2 and for UEs not
configured with supplementaryUplink in ServingCellConfig in the cell;

- 3 bits if the higher layer parameter srs-RequestDCI-1-2 = 2 and for UEs configured with
supplementaryUplink in ServingCellConfig in the cell, where the first bit is the non-SUL/SUL indicator as
defined in Table [Link].1-1 and the second and third bits are defined by Table [Link].2-24;

- SRS offset indicator – 0, 1 or 2 bits.

- DMRS sequence initialization – 0 or 1 bit

- 0 bit if the higher layer parameter dmrs-SequenceInitializationDCI-1-2 is not configured;

- 1 bit otherwise.

- Priority indicator – 0 bit if higher layer parameter priorityIndicatorDCI-1-2 is not configured; otherwise 1 bit as
defined in Clause 9 in [5, TS 38.213].

- PDCCH monitoring adaptation indication – 0, 1 or 2 bits

- 1 or 2 bits, if searchSpaceGroupIdList-r17 is not configured and if pdcch-SkippingDurationList is configured

- 1 bit if the UE is configured with only one duration by pdcch-SkippingDurationList;

- 2 bits if the UE is configured with more than one duration by pdcch-SkippingDurationList.

- 1 or 2 bits, if pdcch-SkippingDurationList is not configured and if searchSpaceGroupIdList-r17 is configured

3GPP
Release 17 192 3GPP TS 38.212 V17.5.0 (2023-03)

- 2 bits if the UE is configured by searchSpaceGroupIdList-r17 with search space set(s) with group index
0, search space set(s) with group index 1 and search space set(s) with group index 2;

- 2 bits, if pdcch-SkippingDurationList is configured and if searchSpaceGroupIdList-r17 is configured

- 0 bit, otherwise

- ChannelAccess-CPext – 0, 1, 2, 3 or 4 bits. The bitwidth for this field is determined as ⌈ log 2 (I ) ⌉ bits, where I
is the number of entries in the higher layer parameter ul-AccessConfigListDCI-1-2 or in Table [Link].1-4A if
channelAccessMode-r16 = "semiStatic" is provided, for operation in a cell with shared spectrum channel access
in frequency range 1, or the number of entries in the high layer parameter ul-AccessConfigListDCI-1-1 for
operation in frequency range 2-2 if ChannelAccessMode2-r17 is provided; otherwise 0 bit. One or more entries
from Table [Link].2-6 are configured by the higher layer parameter ul-AccessConfigListDCI-1-2 in frequency
range 1. One or more entries from Table [Link].2-6A are configured by the higher layer parameter ul-
AccessConfigListDCI-1-1 in frequency range 2-2.

- PUCCH Cell indicator – 0 or 1 bit.

- 1 bit if higher layer parameter pucch-sSCellDynDCI-1-2 is configured.

- 0 bit otherwise.

If DCI formats 1_2 are monitored in multiple search spaces associated with multiple CORESETs in a BWP for
scheduling the same serving cell, zeros shall be appended until the payload size of the DCI formats 1_2 monitored in
the multiple search spaces equal to the maximum payload size of the DCI format 1_2 monitored in the multiple search
spaces.

For a UE configured with scheduling on the primary cell from an SCell, if prior to padding the number of information
bits in DCI format 1_2 carried by PDCCH on the primary cell is not equal to the number of information bits in DCI
format 1_2 carried by PDCCH on the SCell for scheduling on the primary cell, zeros shall be appended to the DCI
format 1_2 with smaller size until the payload size is the same.

- If application of step 4B in clause [Link] results in additional zero padding for DCI format 1_2 for scheduling
on the primary cell, corresponding zeros shall be appended to both DCI format 1_2 monitored on the primary
cell and DCI format 1_2 monitored on the SCell for scheduling on the primary cell.

- If the SCell is deactivated and firstActiveDownlinkBWP-Id is not set to dormant BWP, the UE determines the
number of information bits in DCI format 1_2 carried by PDCCH on the primary cell based on a DL BWP
provided by firstActiveDownlinkBWP-Id for the SCell. If the active DL BWP of the SCell is a dormant DL
BWP, or if the SCell is deactivated and firstActiveDownlinkBWP-Id is set to dormant BWP, the UE determines
the number of information bits in DCI format 1_2 carried by PDCCH on the primary cell based on a DL BWP
provided by firstWithinActiveTimeBWP-Id for the SCell if provided; otherwise, based on a DL BWP provided by
firstOutsideActiveTimeBWP-Id for the SCell.

Table [Link].3-1: Redundancy version

Value of the Redundancy rv id

version field Value of to be applied
0 0
1 3

[Link] DCI formats for other purposes

[Link].1 Format 2_0
DCI format 2_0 is used for notifying the slot format, COT duration, available RB set, and search space set group
switching.

3GPP
Release 17 193 3GPP TS 38.212 V17.5.0 (2023-03)

The following information is transmitted by means of the DCI format 2_0 with CRC scrambled by SFI-RNTI:

- If the higher layer parameter slotFormatCombToAddModList is configured,

- Slot format indicator 1, Slot format indicator 2, …, Slot format indicator N,

- If the higher layer parameter availableRB-SetsToAddModList is configured,

- Available RB set Indicator 1, Available RB set Indicator 2, …, Available RB set Indicator N1,

- If the higher layer parameter co-DurationsPerCellToAddModList is configured

- COT duration indicator 1, COT duration indicator 2, …, COT duration indicator N2.

- If the higher layer parameter switchTriggerToAddModList is configured

- Search space set group switching flag 1, Search space set group switching flag 2, …, Search space set group
switching flag M.

The size of DCI format 2_0 is configurable by higher layers up to 128 bits, according to Clause 11.1.1 of [5, TS
38.213].

[Link].2 Format 2_1

DCI format 2_1 is used for notifying the PRB(s) and OFDM symbol(s) where UE may assume no transmission is
intended for the UE.

The following information is transmitted by means of the DCI format 2_1 with CRC scrambled by INT-RNTI:

- Pre-emption indication 1, Pre-emption indication 2, …, Pre-emption indication N.

The size of DCI format 2_1 is configurable by higher layers up to 126 bits, according to Clause 11.2 of [5, TS 38.213].
Each pre-emption indication is 14 bits.

[Link].3 Format 2_2

DCI format 2_2 is used for the transmission of TPC commands for PUCCH and PUSCH.

The following information is transmitted by means of the DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI
or TPC-PUCCH-RNTI:

- block number 1, block number 2,…, block number N

The parameter tpc-PUSCH or tpc-PUCCH provided by higher layers determines the index to the block number for an
UL of a cell, with the following fields defined for each block:

- Closed loop indicator – 0 or 1 bit.

- For DCI format 2_2 with TPC-PUSCH-RNTI, 0 bit if the UE is not configured with high layer parameter
twoPUSCH-PC-AdjustmentStates, in which case UE assumes each block in the DCI format 2_2 is of 2 bits; 1
bit otherwise, in which case UE assumes each block in the DCI format 2_2 is of 3 bits;

- For DCI format 2_2 with TPC-PUCCH-RNTI, 0 bit if the UE is not configured with high layer parameter
twoPUCCH-PC-AdjustmentStates, in which case UE assumes each block in the DCI format 2_2 is of 2 bits; 1
bit otherwise, in which case UE assumes each block in the DCI format 2_2 is of 3 bits;

- TPC command –2 bits

The number of information bits in format 2_2 shall be equal to or less than the payload size of format 1_0 monitored in
common search space in the same serving cell. If the number of information bits in format 2_2 is less than the payload
size of format 1_0 monitored in common search space in the same serving cell, zeros shall be appended to format 2_2
until the payload size equals that of format 1_0 monitored in common search space in the same serving cell.

[Link].4 Format 2_3

DCI format 2_3 is used for the transmission of a group of TPC commands for SRS transmissions by one or more UEs.
Along with a TPC command, a SRS request may also be transmitted.

3GPP
Release 17 194 3GPP TS 38.212 V17.5.0 (2023-03)

The following information is transmitted by means of the DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI:

- block number 1, block number 2, …, block number B

where the starting position of a block is determined by the parameter startingBitOfFormat2-3 or

startingBitOfFormat2-3SUL-v1530 provided by higher layers for the UE configured with the block.

If the UE is configured with higher layer parameter srs-TPC-PDCCH-Group = typeA for an UL without PUCCH and
PUSCH or an UL on which the SRS power control is not tied with PUSCH power control, one block is configured for
the UE by higher layers, with the following fields defined for the block:

- SRS request – 0 or 2 bits. The presence of this field is according to the definition in Clause 11.4 of [5,
TS38.213]. If present, this field is interpreted as defined by Table [Link].2-24.

- TPC command number 1, TPC command number 2, ..., TPC command number N, where each TPC command
applies to a respective UL carrier provided by higher layer parameter cc-IndexInOneCC-Set

If the UE is configured with higher layer parameter srs-TPC-PDCCH-Group = typeB for an UL without PUCCH and
PUSCH or an UL on which the SRS power control is not tied with PUSCH power control, one block or more blocks is
configured for the UE by higher layers where each block applies to an UL carrier, with the following fields defined for
each block:

- SRS request – 0 or 2 bits. The presence of this field is according to the definition in Clause 11.4 of [5,
TS38.213]. If present, this field is interpreted as defined by Table [Link].2-24.

- TPC command –2 bits

The number of information bits in format 2_3 shall be equal to or less than the payload size of format 1_0 monitored in
common search space in the same serving cell. If the number of information bits in format 2_3 is less than the payload
size of format 1_0 monitored in common search space in the same serving cell, zeros shall be appended to format 2_3
until the payload size equals that of format 1_0 monitored in common search space in the same serving cell.

[Link].5 Format 2_4

DCI format 2_4 is used for notifying the PRB(s) and OFDM symbol(s) where UE cancels the corresponding UL
transmission from the UE according to Clause 11.2A of [5, TS 38.213].

The following information is transmitted by means of the DCI format 2_4 with CRC scrambled by CI-RNTI:

- Cancellation indication 1, Cancellation indication 2, …, Cancellation indication indication N.

The size of DCI format 2_4 is configurable by higher layers parameter dci-PayloadSizeForCI up to 126 bits, according
to Clause 11.2A of [5, TS 38.213]. The number of bits for each cancellation indication is configurable by higher layer
parameter ci-PayloadSize. For a UE, there is at most one cancellation indication for an UL carrier.

[Link].6 Format 2_5

DCI format 2_5 is used for notifying the availability of soft resources as defined in Clause 9.3.1 of [10, TS 38.473]

The following information is transmitted by means of the DCI format 2_5 with CRC scrambled by AI-RNTI:

- Availability indicator 1, Availability indicator 2, …, Availability indicator N.

The size of DCI format 2_5 is configurable by higher layers up to 128 bits, according to Clause 14 of [5, TS 38.213].

[Link].7 Format 2_6

DCI format 2_6 is used for notifying the power saving information outside DRX Active Time for one or more UEs.

The following information is transmitted by means of the DCI format 2_6 with CRC scrambled by PS-RNTI:

- block number 1, block number 2,…, block number N

where the starting position of a block is determined by the parameter ps-PositionDCI-2-6 provided by higher
layers for the UE configured with the block.

3GPP
Release 17 195 3GPP TS 38.212 V17.5.0 (2023-03)

If the UE is configured with higher layer parameter ps-RNTI and dci-Format2-6, one block is configured for the UE by
higher layers, with the following fields defined for the block:

- Wake-up indication - 1 bit

- SCell dormancy indication – 0 bit if higher layer parameter dormancyGroupOutsideActiveTime is not

configured; otherwise 1, 2, 3, 4 or 5 bits bitmap determined according to the number of different
DormancyGroupID(s) provided by higher layer parameter dormancyGroupOutsideActiveTime, where each bit
corresponds to one of the SCell group(s) configured by higher layers parameter
dormancyGroupOutsideActiveTime, with MSB to LSB of the bitmap corresponding to the first to last configured
SCell group in ascending order of DormancyGroupID.

The size of DCI format 2_6 is indicated by the higher layer parameter sizeDCI-2-6, according to Clause 10.3 of [5, TS
38.213].

[Link].8 Format 2_7

DCI format 2_7 is used for notifying the paging early indication and TRS availability indication for one or more UEs.

The following information is transmitted by means of the DCI format 2_7 with CRC scrambled by PEI-RNTI:
PEI PO
- Paging indication field – N PO N SG bit(s), where

PEI
- N PO is the number of paging occasions configured by higher layer parameter po-NumPerPEI as defined in
Clause 10.4A in [5, TS 38.213];
PO
- N SG is the number of sub-groups of a paging occasion configured by higher layer parameter
subgroupsNumPerPO.

- Each bit in the field indicates one UE subgroup of a paging occasion.

The size of DCI format 2_7 is indicated by the higher layer parameter payloadSizeDCI-2-7, according to Clause 10.4A
of [5, TS 38.213]. The number of information bits in format 2_7 shall be equal to or less than the payload size of format
2_7. If the number of information bits in format 2_7 is less than the size of format 2_7, the remaining bits are reserved.

[Link] DCI formats for scheduling of sidelink

[Link].1 Format 3_0
DCI format 3_0 is used for scheduling of NR PSCCH and NR PSSCH in one cell.

The following information is transmitted by means of the DCI format 3_0 with CRC scrambled by SL-RNTI or SL-CS-
RNTI:

- Resource pool index – ⌈ log 2 I ⌉ bits, where I is the total number of resource pools for transmission configured
by the higher layer parameter sl-TxPoolScheduling, if configured, and sl-DiscTxPoolScheduling, if configured.

- Time gap – 3 bits determined by higher layer parameter sl-DCI-ToSL-Trans, as defined in clause [Link] of [6,
TS 38.214]

- HARQ process number – 4 bits.

- New data indicator – 1 bit.

SL
- Lowest index of the subchannel allocation to the initial transmission – ⌈ log 2 ( N subChannel ) ⌉ bits as defined in
clause [Link] of [6, TS 38.214]

- SCI format 1-A fields according to clause [Link]:

- Frequency resource assignment.

3GPP
Release 17 196 3GPP TS 38.212 V17.5.0 (2023-03)

- Time resource assignment.

- PSFCH-to-HARQ feedback timing indicator – ⌈ log 2 N fb timing ⌉ bits, where N fb timing is the number of entries in the
higher layer parameter sl-PSFCH-ToPUCCH, as defined in clause 16.5 of [5, TS 38.213]

- PUCCH resource indicator – 3 bits as defined in clause 16.5 of [5, TS 38.213].

- Configuration index – 0 bit if the UE is not configured to monitor DCI format 3_0 with CRC scrambled by SL-
CS-RNTI; otherwise 3 bits as defined in clause 8.1.2 of [6, TS 38.214]. If the UE is configured to monitor DCI
format 3_0 with CRC scrambled by SL-CS-RNTI, this field is reserved for DCI format 3_0 with CRC scrambled
by SL-RNTI.

- Counter sidelink assignment index – 2 bits

- 2 bits as defined in clause 16.5.2 of [5, TS 38.213] if the UE is configured with pdsch-HARQ-ACK-
Codebook = dynamic

- 2 bits as defined in clause 16.5.1 of [5, TS 38.213] if the UE is configured with pdsch-HARQ-ACK-
Codebook = semi-static

- Padding bits, if required

If the total number of transmit resource pools provided in sl-TxPoolScheduling, if configured, and sl-
DiscTxPoolScheduling, if configured, is larger than one, zeros shall be appended to the DCI format 3_0 until the
payload size is equal to the size of a DCI format 3_0 given by a configuration of the transmit resource pool resulting in
the largest number of information bits for DCI format 3_0.

If the UE is configured to monitor DCI format 3_1 and the number of information bits in DCI format 3_0 is less than
the payload of DCI format 3_1, zeros shall be appended to DCI format 3_0 until the payload size equals that of DCI
format 3_1.

[Link].2 Format 3_1

DCI format 3_1 is used for scheduling of LTE PSCCH and LTE PSSCH in one cell.

The following information is transmitted by means of the DCI format 3_1 with CRC scrambled by SL Semi-Persistent
Scheduling V-RNTI:

- Timing offset – 3 bits determined by higher layer parameter sl-TimeOffsetEUTRA-List, as defined in clause 16.6
of [5, TS 38.213]

- Carrier indicator –3 bits as defined in [Link].9A of [11, TS 36.212].

-  SL
Lowest index of the subchannel allocation to the initial transmission - log2 ( N subchannel)  bits as defined in
[Link].9A of [11, TS 36.212].

- Frequency resource location of initial transmission and retransmission, as defined in [Link].9A of [11, TS
36.212]

- Time gap between initial transmission and retransmission, as defined in [Link].9A of [11, TS 36.212]

- SL index – 2 bits as defined in [Link].9A of [11, TS 36.212]

- SL SPS configuration index – 3 bits as defined in clause [Link].9A of [11, TS 36.212].

- Activation/release indication – 1 bit as defined in clause [Link].9A of [11, TS 36.212].

If the UE is configured to monitor DCI format 3_0 and the number of information bits in DCI format 3_1 is less than
the payload of DCI format 3_0, zeros shall be appended to DCI format 3_1 until the payload size equals that of DCI
format 3_0.

3GPP
Release 17 197 3GPP TS 38.212 V17.5.0 (2023-03)

[Link] DCI formats for scheduling of MBS

[Link].1 Format 4_0
DCI format 4_0 is used for the scheduling of PDSCH for broadcast in DL cell.

The following information is transmitted by means of the DCI format 4_0 with CRC scrambled by MCCH-RNTI or G-
RNTI for broadcast configured by MBS-SessionInfo:

Frequency domain resource assignment – ⌈ log 2 ¿ ¿ bits where N RB

DL,CFR
- equals to

- the size of CORESET 0 if CORESET 0 is configured for the cell; and

- the size of initial DL bandwidth part if CORESET 0 is not configured for the cell.

- Time domain resource assignment – 4 bits as defined in Clause [Link] of [6, TS38.214]

- VRB-to-PRB mapping – 1 bit according to Table [Link].2-5

- Modulation and coding scheme – 5 bits as defined in Clause 5.1.3 of [6, TS38.214]

- Redundancy version – 2 bits as defined in Table [Link].1-2

- MCCH change notification – 2 bits as defined in Clause [Link] of [9, TS38.331] if the CRC of the DCI format
4_0 is scrambled by MCCH-RNTI. Otherwise, this bit field is reserved.

- Reserved bits – 14bits

[Link].2 Format 4_1

DCI format 4_1 is used for the scheduling of PDSCH for multicast in DL cell.

The following information is transmitted by means of the DCI format 4_1 with CRC scrambled by G-RNTI for
multicast or G-CS-RNTI configured by MBS-RNTI-SpecificConfig:

Frequency domain resource assignment – ⌈ log 2 ¿ ¿ bits where N RB

DL,CFR
- equals to

- the size of CORESET 0 if CORESET 0 is configured for the cell; and

- the size of initial DL bandwidth part if CORESET 0 is not configured for the cell.

- Time domain resource assignment – 4 bits as defined in Clause [Link] of [6, TS38.214]

- VRB-to-PRB mapping – 1 bit according to Table [Link].2-5

- Modulation and coding scheme – 5 bits as defined in Clause 5.1.3 of [6, TS38.214]

- New data indicator – 1 bit

- Redundancy version – 2 bits as defined in Table [Link].1-2

- HARQ process number – 4 bits

- Downlink assignment index – 2 bits as defined in Clause 9.1.3 of [5, TS 38.213], as counter DAI

- PUCCH resource indicator – 3 bits as defined in Clause 9.2.3 of [5, TS38.213]

- PDSCH-to-HARQ_feedback timing indicator – 3 bits as defined in Clause 9.2.3 of [5, TS38.213]

- Reserved bits – 3 bits

[Link].3 Format 4_2

DCI format 4_2 is used for the scheduling of PDSCH for multicast in DL cell.

The following information is transmitted by means of the DCI format 4_2 with CRC scrambled by G-RNTI for
multicast or G-CS-RNTI configured by MBS-RNTI-SpecificConfig:

3GPP
Release 17 198 3GPP TS 38.212 V17.5.0 (2023-03)

DL,CFR
- Frequency domain resource assignment – number of bits determined by the following, where N RB is the size
of the common frequency resource as configured by higher layer parameter locationAndBandwidthMulticast:

- N RBG bits if only resource allocation type 0 is configured, where N RBG is defined in Clause [Link].1 of [6,
TS38.214],

- ⌈ log 2 ¿ ¿ bits if only resource allocation type 1 is configured, or

- max ¿ ¿ bits if resourceAllocation in pdsch-ConfigMulticast is configured as 'dynamicSwitch'.
- If resourceAllocation in pdsch-ConfigMulticast is configured as 'dynamicSwitch', the MSB bit is used to
indicate resource allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource
allocation type 0 and the bit value of 1 indicates resource allocation type 1.

- For resource allocation type 0, the N RBG LSBs provide the resource allocation as defined in Clause [Link].1
of [6, TS 38.214].

- For resource allocation type 1, the ⌈ log 2 ¿ ¿ LSBs provide the resource allocation as defined in Clause
[Link].2 of [6, TS 38.214]

- VRB-to-PRB mapping – 0 or 1 bit:

- 0 bit if only resource allocation type 0 is configured or if vrb-ToPRB-Interleaver in pdsch-ConfigMulticast is

not configured;

- 1 bit according to Table [Link].2-5 otherwise, only applicable to resource allocation type 1, as defined in
Clause [Link] of [4, TS 38.211].

- PRB bundling size indicator – 0 bit if the higher layer parameter prb-BundlingType is not configured in pdsch-
ConfigMulticast or is set to 'staticBundling', or 1 bit if the higher layer parameter prb-BundlingType in pdsch-
ConfigMulticast is set to 'dynamicBundling' according to Clause [Link] of [6, TS 38.214].

- Rate matching indicator – 0, 1, or 2 bits according to higher layer parameters rateMatchPatternGroup1 and
rateMatchPatternGroup2 in pdsch-ConfigMulticast, where the MSB is used to indicate
rateMatchPatternGroup1 and the LSB is used to indicate rateMatchPatternGroup2 when there are two groups.

- ZP CSI-RS trigger – 0, 1, or 2 bits as defined in Clause [Link] of [6, TS 38.214]. The bitwidth for this field is
determined as ⌈ log 2 (n ZP +1)⌉ bits, where n ZP is the number of aperiodic ZP CSI-RS resource sets configured
in pdsch-ConfigMulticast.

For transport block 1:

- Modulation and coding scheme – 5 bits as defined in Clause [Link] of [6, TS 38.214]

- New data indicator – 1 bit

- Redundancy version – 2 bits as defined in Table [Link].1-2

For transport block 2 (only present if maxNrofCodeWordsScheduledByDCI configured in pdsch-ConfigMulticast

equals 2):

- Modulation and coding scheme – 5 bits as defined in Clause [Link] of [6, TS 38.214]

- New data indicator – 1 bit

- Redundancy version – 2 bits as defined in Table [Link].1-2

- HARQ process number – 4 bits

3GPP
Release 17 199 3GPP TS 38.212 V17.5.0 (2023-03)

- Downlink assignment index – number of bits as defined in the following

- 2 bits if the higher layer parameter pdsch-HARQ-ACK-Codebook =dynamic is configured for multicast,
where the 2 bits are the counter DAI;

- 0 bits otherwise.

If higher layer parameter priorityIndicatorDCI-4-2 is configured in pdsch-ConfigMulticast, if the bit width of the
Downlink assignment index in DCI format 4_2 for one HARQ-ACK codebook is not equal to that of the
Downlink assignment index in DCI format 4_2 for the other HARQ-ACK codebook, a number of most
significant bits with value set to '0' are inserted to smaller Downlink assignment index until the bit width of the
Downlink assignment index in DCI format 4_2 for the two HARQ-ACK codebooks are the same.

- PUCCH resource indicator – 3 bits as defined in Clause 9.2.3 of [5, TS 38.213]

- PDSCH-to-HARQ_feedback timing indicator – 0, 1, 2, or 3 bits as defined in Clause 9.2.3 of [5, TS 38.213]. The
bitwidth for this field is determined as ⌈ log 2 (I ) ⌉ bits, where I is the number of entries in the higher layer
parameter dl-DataToUL-ACK in pucch-ConfigMulticast1 if configured or pucch-ConfigMulticast2 if configured;
otherwise, I is the number of entries in the higher layer parameter dl-DataToUL-ACK in PUCCH-Config.

If higher layer parameter priorityIndicatorDCI-4-2 is configured in pdsch-ConfigMulticast, if the bit width of the
PDSCH-to-HARQ_feedback timing indicator in DCI format 4_2 for one HARQ-ACK codebook is not equal to
that of the PDSCH-to-HARQ_feedback timing indicator in DCI format 4_2 for the other HARQ-ACK codebook,
a number of most significant bits with value set to '0' are inserted to smaller PDSCH-to-HARQ_feedback timing
indicator until the bit width of the PDSCH-to-HARQ_feedback timing indicator in DCI format 4_2 for the two
HARQ-ACK codebooks are the same.

- Antenna port(s) – 4, 5, or 6 bits as defined by Tables [Link].2-1/2/3/4, where the number of CDM groups
without data of values 1, 2, and 3 refers to CDM groups {0}, {0,1}, and {0, 1,2} respectively. The antenna ports
{ p 0 , … , pv−1 } shall be determined according to the ordering of DMRS port(s) given by Tables [Link].2-
1/2/3/4.

If a UE is configured with both dmrs-DownlinkForPDSCH-MappingTypeA and dmrs-DownlinkForPDSCH-

MappingTypeB, the bitwidth of this field equals max ⁡{ x A , x B } , where x A is the "Antenna ports" bitwidth
derived according to dmrs-DownlinkForPDSCH-MappingTypeA and x B is the "Antenna ports" bitwidth derived
according to dmrs-DownlinkForPDSCH-MappingTypeB. A number of |x A −x B| zeros are padded in the MSB
of this field, if the mapping type of the PDSCH corresponds to the smaller value of x A and x B .

- Transmission configuration indication – 0 bit if higher layer parameter tci-PresentInDCI in pdcch-

ConfigMulticast is not enabled; otherwise 3 bits as defined in Clause 5.1.5 of [6, TS38.214].

- DMRS sequence initialization – 1 bit.

- Priority indicator – 0 bit if higher layer parameter priorityIndicatorDCI-4-2 is not configured in pdsch-
ConfigMulticast; otherwise 1 bit as defined in Clause 9 in [5, TS 38.213].

- Enabling/disabling HARQ-ACK feedback indication –1 bit if higher layer parameter harq-

FeedbackEnablerMulticast indicates dci-enabler, where value 1 indicates enabling HARQ-ACK feedback and
value 0 indicates disabling HARQ-ACK feedback; 0 bit, otherwise.

The size of DCI format 4_2 is configurable by higher layer parameter sizeDCI-4-2 from 20 bits and up to 140 bits.

7.3.2 CRC attachment

Error detection is provided on DCI transmissions through a Cyclic Redundancy Check (CRC).

The entire payload is used to calculate the CRC parity bits. Denote the bits of the payload by
a 0 , a1 , a 2 , a3 , . .. , a A −1 , and
the parity bits by
p0 , p1 , p2 , p3 , . .. , p L−1 , where A is the payload size and L is the number of parity bits. Let
a' 0 ,a'1 ,a' 2 ,a'3 ,...,a' A+ L−1 be a bit sequence such that a ' i=1 for i=0,1,..., L−1 and a ' i=ai− L for
i=L , L+1, .. . , A +L−1 . The parity bits are computed with input bit sequence a' 0 ,a'1 ,a' 2 ,a'3 ,...,a' A+ L−1 and attached

3GPP
Release 17 200 3GPP TS 38.212 V17.5.0 (2023-03)

according to Clause 5.1 by setting L to 24 bits and using the generator polynomial gCRC24C ( D ) . The output bit
is

b k =ak for k=0,1,2,..., A−1

b k =p k −A for k= A , A +1, A+2,..., A +L−1 ,

where K= A + L .

After attachment, the CRC parity bits are scrambled with the corresponding RNTI
x rnti , 0 , x rnti, 1 , . .. , xrnti , 15 , where x rnti ,0
c ,c ,c ,c ,...,c K −1 . The relation between c and b
corresponds to the MSB of the RNTI, to form the sequence of bits 0 1 2 3 k k
is:

c k =b k for k = 0, 1, 2, …, A+7

c k =( bk + xrnti , k − A−8 ) mod 2

for k = A+8 , A+ 9 , A+10 ,..., A+23 .

7.3.3 Channel coding

Information bits are delivered to the channel coding block. They are denoted by
c 0 , c 1 , c 2 , c 3 , .. . , c K −1 , where K is the

number of bits, and they are encoded via Polar coding according to Clause 5.3.1, by setting
n max =9 , I IL =1 , n PC =0 ,
wm
and n PC =0 .

After encoding the bits are denoted by

d 0 ,d1 ,d 2 ,d3 ,...,d N−1 , where N is the number of coded bits.

7.3.4 Rate matching

The input bit sequence to rate matching is d 0 ,d1 ,d 2 ,...,d N−1 .

Rate matching is performed according to Clause 5.4.1 by setting I BIL=0 .

The output bit sequence after rate matching is denoted as f 0 , f 1 , f 2 , .. . , f E−1 .

8 Sidelink transport channels and control information

8.1 Sidelink broadcast channel
The processing for SL-BCH transport channel follows the BCH according to clause 7.1, with the following changes:

- In Clause 7.1, 'maximum of one transport block every 80ms' is replaced with 'maximum of one transport block'.

- Clause 7.1.1 for PBCH payload generation is not performed.

- Clause 7.1.2 for scrambling is not performed.

- In clause 7.1.5, the rate matching output sequence length E = 1386 when higher layer parameter cyclicPrefix is
configured, otherwise, E = 1782.

8.1.1 (void)
8.2 Sidelink shared channel
The processing for SL-SCH transport channel follows the UL-SCH according to clause 6.2, with the following changes:

3GPP
Release 17 201 3GPP TS 38.212 V17.5.0 (2023-03)

- Rate matching of SL-SCH follows the rate matching according to clause 6.2.5 by setting I LBRM =0

- Clause 6.2.7 is replaced by clause 8.2.1

8.2.1 Data and control multiplexing

SL−SCH SL−SCH SL−SCH SL−SCH SL−SCH
Denote the coded bits for SL-SCH as g0 , g1 , g2 , g3 , ⋯ , gG SL−SCH
−1
.

SCI 2 SCI 2 SCI 2 SCI 2 SCI 2

Denote the coded bits for the 2nd-stage SCI, as g0 , g1 , g2 , g3 , ⋯ , gGSCI2
−1
.

Denote the multiplexed data and control coded bit sequence as g0 , g 1 , ⋯ , gG −1, where G is the total number of coded
bits for transmission.

Assuming that N L is the number of layers onto which the SL-SCH transport block is mapped, the multiplexed data and
control coded bit sequence g0 , g 1 , ⋯ , gG −1 is obtained as follows:
SCI 2
Denote Q m is modulation order of the 2nd-stage SCI.

if N L=1 ,

for i=0 to G SCI 2+G SL−SCH −1

if 0 ≤ i<G SCI 2
SCI 2
gi=g i
end if

if G SCI 2 ≤ i≤ G SCI 2 +G SL−SCH −1

SL−SCH
gi=g i−G SCI 2

end if

end for

end if

if N L=2,
ℜ SCI 2 SCI 2
let M count , SCI 2=G /Q m
ℜ
set m count =0
ℜ
for i=0 to M count , SCI 2−1

for v=0 to N L−1

SCI 2
for q=0 to Q m −1
if v=0
SCI 2
gm =gi ∙Q
ℜ
count
SCI2
m +q

else

gm =x // placeholder bit
ℜ
count

end if

3GPP
Release 17 202 3GPP TS 38.212 V17.5.0 (2023-03)

ℜ ℜ
mcount =mcount +1
end for

end for

for i=0 to G SL−SCH −1

SL−SCH
gm =gi
ℜ
count

ℜ ℜ
mcount =mcount +1
end for

end if

8.3 Sidelink control information on PSCCH

SCI carried on PSCCH is a 1st-stage SCI, which transports sidelink scheduling information.

8.3.1 1st-stage SCI formats

The fields defined in each of the 1st-stage SCI formats below are mapped to the information bits a 0 to a A−1as follows:

Each field is mapped in the order in which it appears in the description, with the first field mapped to the lowest order
information bit a 0and each successive field mapped to higher order information bits. The most significant bit of each
field is mapped to the lowest order information bit for that field, e.g. the most significant bit of the first field is mapped
to a 0.

[Link] SCI format 1-A

SCI format 1-A is used for the scheduling of PSSCH and 2nd-stage-SCI on PSSCH

The following information is transmitted by means of the SCI format 1-A:

subChannel ( N subChannel + 1 )
N SL
SL
- Frequency resource assignment – ⌈ log ( ) ⌉ bits when the value of the higher
2
2
layer parameter sl-MaxNumPerReserve is configured to 2; otherwise
subChannel ( N subChannel + 1 )( 2 N subChannel + 1 )
N SL
SL SL

⌈ log 2 ( ) ⌉ bits when the value of the higher layer

6
parameter sl-MaxNumPerReserve is configured to 3, as defined in clause 8.1.5 of [6, TS 38.214].

- Time resource assignment – 5 bits when the value of the higher layer parameter sl-MaxNumPerReserve is
configured to 2; otherwise 9 bits when the value of the higher layer parameter sl-MaxNumPerReserve is
configured to 3, as defined in clause 8.1.5 of [6, TS 38.214].

- Resource reservation period – ⌈ log 2 N rsv period ⌉ bits as defined in clause 16.4 of [5, TS 38.213], where N rsv period is
the number of entries in the higher layer parameter sl-ResourceReservePeriodList, if higher layer parameter sl-
MultiReserveResource is configured; 0 bit otherwise.

- DMRS pattern – ⌈ log 2 N pattern ⌉ bits as defined in clause [Link].2 of [4, TS 38.211], where N pattern is the
number of DMRS patterns configured by higher layer parameter sl-PSSCH-DMRS-TimePatternList.

- 2nd-stage SCI format – 2 bits as defined in Table [Link]-1.

3GPP
Release 17 203 3GPP TS 38.212 V17.5.0 (2023-03)

- Beta_offset indicator – 2 bits as provided by higher layer parameter sl-BetaOffsets2ndSCI and Table [Link]-2.

- Number of DMRS port – 1 bit as defined in Table [Link]-3.

- Modulation and coding scheme – 5 bits as defined in clause 8.1.3 of [6, TS 38.214].

- Additional MCS table indicator – as defined in clause [Link] of [6, TS 38.214]: 1 bit if one MCS table is
configured by higher layer parameter sl-Additional-MCS-Table; 2 bits if two MCS tables are configured by
higher layer parameter sl-Additional-MCS-Table; 0 bit otherwise.

- PSFCH overhead indication – 1 bit as defined clause [Link] of [6, TS 38.214] if higher layer parameter sl-
PSFCH-Period = 2 or 4; 0 bit otherwise.

- Reserved – a number of bits as determined by the following:

- N reserved bits as configured by higher layer parameter sl-NumReservedBits, with value set to zero, if higher
layer parameter sl-IndicationUE-B is not configured, or if higher layer parameter sl-IndicationUE-B is
configured to 'disabled';

- (N reserved −1) bits otherwise, with value set to zero.

- Conflict information receiver flag – 0 or 1 bit

- 1 bit if higher layer parameter sl-IndicationUE-B is configured to 'enabled', where the bit value of 0 indicates
that the UE cannot be a UE to receive conflict information and the bit value of 1 indicates that the UE can be
a UE to receive conflict information as defined in Clause 16.3.0 of [5, TS 38.213];

- 0 bit otherwise.

Table [Link]-1: 2nd-stage SCI formats

Value of 2nd-stage SCI

2nd-stage SCI format
format field
00 SCI format 2-A
01 SCI format 2-B
10 SCI format 2-C
11 Reserved

Table [Link]-2: Mapping of Beta_offset indicator values to indexes in Table 9.3-2 of [5, TS38.213]

Value of Beta_offset
Beta_offset index in Table 9.3-2 of [5, TS38.213]
indicator
1st index provided by higher layer parameter sl-
00
BetaOffsets2ndSCI
2nd index provided by higher layer parameter sl-
01
BetaOffsets2ndSCI
3rd index provided by higher layer parameter sl-
10
BetaOffsets2ndSCI
4th index provided by higher layer parameter sl-
11
BetaOffsets2ndSCI

Table [Link]-3: Number of DMRS port(s)

Value of the Number of

Antenna ports
DMRS port field
0 1000
1 1000 and 1001

8.3.2 CRC attachment

CRC attachment is performed according to clause 7.3.2 except that scrambling is not performed.

3GPP
Release 17 204 3GPP TS 38.212 V17.5.0 (2023-03)

8.3.3 Channel coding

Channel coding is performed according to clause 7.3.3.

8.3.4 Rate Matching

Rate matching is performed according to clause 7.3.4.

8.4 Sidelink control information on PSSCH

SCI carried on PSSCH is a 2nd-stage SCI, which transports sidelink scheduling information, and/or inter-UE
coordination related information.

8.4.1 2nd-stage SCI formats

The fields defined in each of the 2nd-stage SCI formats below are mapped to the information bits a 0 to a A−1 as follows:

[Link] SCI format 2-A

SCI format 2-A is used for the decoding of PSSCH, with HARQ operation when HARQ-ACK information includes
ACK or NACK, when HARQ-ACK information includes only NACK, or when there is no feedback of HARQ-ACK
information.

The following information is transmitted by means of the SCI format 2-A:

- HARQ process number – 4 bits.

- New data indicator – 1 bit.

- Redundancy version – 2 bits as defined in Table [Link].1-2.

- Source ID – 8 bits as defined in clause 8.1 of [6, TS 38.214].

- Destination ID – 16 bits as defined in clause 8.1 of [6, TS 38.214].

- HARQ feedback enabled/disabled indicator – 1 bit as defined in clause 16.3 of [5, TS 38.213].

- Cast type indicator – 2 bits as defined in Table [Link]-1 and in clause 8.1 of [6, TS 38.214].

- CSI request – 1 bit as defined in clause 8.2.1 of [6, TS 38.214] and in clause 8.1 of [6, TS 38.214].

Table [Link]-1: Cast type indicator

Value of Cast type

Cast type
indicator
00 Broadcast
Groupcast
01
when HARQ-ACK information includes ACK or NACK
10 Unicast
Groupcast
11
when HARQ-ACK information includes only NACK

[Link] SCI format 2-B

SCI format 2-B is used for the decoding of PSSCH, with HARQ operation when HARQ-ACK information includes
only NACK, or when there is no feedback of HARQ-ACK information.

The following information is transmitted by means of the SCI format 2-B:

3GPP
Release 17 205 3GPP TS 38.212 V17.5.0 (2023-03)

- HARQ process number – 4 bits.

- New data indicator – 1 bit.

- Redundancy version – 2 bits as defined in Table [Link].1-2.

- Source ID – 8 bits as defined in clause 8.1 of [6, TS 38.214].

- Destination ID – 16 bits as defined in clause 8.1 of [6, TS 38.214].

- HARQ feedback enabled/disabled indicator – 1 bit as defined in clause 16.3 of [5, TS 38.213].

- Zone ID – 12 bits as defined in clause 5.8.11 of [9, TS 38.331].

- Communication range requirement – 4 bits determined by higher layer parameter sl-ZoneConfigMCR-Index.

[Link] SCI format 2-C

SCI format 2-C is used for the decoding of PSSCH, and providing inter-UE coordination information or requesting
inter-UE coordination information. SCI format 2-C can be used only for unicast.

The following information is transmitted by means of the SCI format 2-C:

- HARQ process number – 4 bits

- New data indicator – 1 bit

- Redundancy version – 2 bits as defined in Table [Link].1-2

- Source ID – 8 bits as defined in clause 8.1 of [6, TS 38.214]

- Destination ID – 16 bits as defined in clause 8.1 of [6, TS 38.214]

- HARQ feedback enabled/disabled indicator – 1 bit as defined in clause 16.3 of [5, TS 38.213]

- CSI request – 1 bit as defined in clause 8.2.1 of [6, TS 38.214] and in clause 8.1 of [6, TS 38.214]

- Providing/Requesting indicator – 1 bit, where value 0 indicates SCI format 2-C is used for providing inter-UE
coordination information and value 1 indicates SCI format 2-C is used for requesting inter-UE coordination
information

If the 'Providing/Requesting indicator' field is set to 0, all the remaining fields are set as follows:

( subChannel ( N subChannel + 1 )( 2 N subChannel + 1 )

N SL
)
SL SL
- Resource combinations –2 ∙ ⌈ log ( ) ⌉ + 9+Y bits as
2
6
defined in Clause 8.1.5A of [6, TS 38.214], where

- Y =⌈ log 2 N rsv period

⌉ and N rsv
is the number of entries in the higher layer parameter sl-
period

ResourceReservePeriodList, if higher layer parameter sl-MultiReserveResource is configured;Y =0

otherwise
SL
- N subChannel is the number of subchannels in a resource pool provided by the higher layer parameter sl-
NumSubchannel

- First resource location – 8 bits as defined in Clause 8.1.5A of [6, TS 38.214].

μ
- Reference slot location – (10+ ⌈ log 2 (10∙ 2 ) ⌉ ¿ bits as defined in Clause 8.1.5A of [6, TS 38.214], where μ is
defined in Table 4.2-1 of Clause 4.2 of [4, TS 38.211].

- Resource set type – 1 bit, where value 0 indicates preferred resource set and value 1 indicates non-preferred
resource set.
SL
- Lowest subChannel indices – 2 ∙ ⌈ log 2 N subChannel ⌉ bits as defined in Clause 8.1.5A of [6, TS 38.214].

3GPP
Release 17 206 3GPP TS 38.212 V17.5.0 (2023-03)

If the 'Providing/Requesting indicator' field is set to 1, all the remaining fields are set as follows:

- Priority – 3 bits as specified in clause [Link] of [12, TS 23.287] and clause [Link].1 of [8, TS 38.321]. Value
'000' of Priority field corresponds to priority value '1', value '001' of Priority field corresponds to priority value
'2', and so on.
SL
- Number of subchannels – ⌈ log 2 N subChannel ⌉ bits as defined in Clause 8.1.4A of [6, TS 38.214].

- Resource reservation period – ⌈ log 2 N rsv period ⌉ bits as defined in Clause 8.1.4A of [6, TS 38.214], where N rsv period
is the number of entries in the higher layer parameter sl-ResourceReservePeriodList, if higher layer parameter
sl-MultiReserveResource is configured; 0 bit otherwise.

Resource selection window location – 2 ∙ ( 10+ ⌈ log 2 (10∙ 2 ) ⌉ ) bits as defined in Clause 8.1.4A of [6, TS
μ
-
38.214], where μ is defined in Table 4.2-1 of Clause 4.2 of [4, TS 38.211].

- Resource set type – 1 bit, where value 0 indicates a request for inter-UE coordination information providing
preferred resource set and value 1 indicates a request for inter-UE coordination information providing non-
preferred resource set, if higher layer parameter sl-DetermineResourceType is configured to 'ueb'; otherwise, 0
bit.

- Padding bits.

For operation in a same resource pool, zeros shall be appended to SCI format 2-C of which 'Providing/Requesting
indicator' field is set to 1 until the payload size equals that of SCI format 2-C of which 'Providing/Requesting indicator'
field is set to 0.

8.4.2 CRC attachment

CRC attachment is performed according to clause 7.3.2 except that scrambling is not performed.

8.4.3 Channel coding

Channel coding is performed according to clause 7.3.3.

8.4.4 Rate Matching

For 2nd-stage SCI transmission on PSSCH with SL-SCH, the number of coded modulation symbols generated for 2 nd-
'
stage SCI transmission prior to duplication for the 2nd layer if present, denoted as Q SCI 2, is determined as follows:

{ }
SCI 2 N PSSCH −1
( O SCI 2+ LSCI 2 ) ∙ β offset symbol

Q
'
SCI 2 =min ⌈
Q
SCI 2
∙R
⌉ ,⌈ α ∑ SCI 2
M sc (l)⌉ + γ
m l=0

where

- OSCI 2 is the number of the 2nd-stage SCI bits

- LSCI 2 is the number of CRC bits for the 2nd-stage SCI, which is 24 bits.
SCI 2
- β offset is indicated in the corresponding 1st-stage SCI.
PSSCH
- M sc (l) is the scheduled bandwidth of PSSCH transmission, expressed as a number of subcarriers.
PSCCH
- M sc (l) is the number of subcarriers in OFDM symbol l that carry PSCCH and PSCCH DMRS associated
with the PSSCH transmission.
SCI 2
- M sc (l) is the number of resource elements that can be used for transmission of the 2nd-stage SCI in OFDM
PSSCH PSSCH sh PSFCH
symbol l , for l=0 , 1 , 2 ⋯ , N symbol −1 and for N symbol =N symb−N symb , in PSSCH transmission, where
sh
N symb = sl-lengthSymbols - 2, where sl-lengthSymbols is the number of sidelink symbols within the slot provided

3GPP
Release 17 207 3GPP TS 38.212 V17.5.0 (2023-03)

PSFCH
by higher layers as defined in [6, TS 38.214]. If higher layer parameter sl-PSFCH-Period = 2 or 4, N symb =3
PSFCH
if "PSFCH overhead indication" field of SCI format 1-A indicates "1", and N symb = 0 otherwise. If higher
PSFCH
layer parameter sl-PSFCH-Period = 0, N symb =0. If higher layer parameter sl-PSFCH-Period is 1,
PSFCH
N symb =3.
SCI 2 PSSCH PSCCH
- M sc (l) = M sc (l) - M sc (l)
- γ is the number of vacant resource elements in the resource block to which the last coded symbol of the 2nd-stage
SCI belongs.

- R is the coding rate as indicated by "Modulation and coding scheme" field in SCI format 1-A.
- α is configured by higher layer parameter sl-Scaling.

The input bit sequence to rate matching is d 0 , d 1 , d 2 , d 3 , ⋯ , d N −1 , where N is the number of coded bits.

Rate matching is performed according to Clause 5.4.1 by setting I BIL =1.

SCI 2 SCI 2 SCI 2 SCI 2 SCI 2
The output bit sequence after rate matching is denoted as g0 , g1 , g2 , g3 , ⋯ , gGSCI2
−1
, where
SCI 2 ' SCI 2 SCI 2
G =Q SCI 2 ∙Q m and Q m is modulation order of the 2 -stage SCI. A UE is not expected to haveG SCI 2> 4096 .
nd

8.4.5 Multiplexing of coded 2nd-stage SCI bits to PSSCH

The coded 2nd-stage SCI bits are multiplexed onto PSSCH according to the procedures in Clause 8.2.1.

3GPP
Release 17 208 3GPP TS 38.212 V17.5.0 (2023-03)

Annex <A> (informative):

Change history

3GPP
Release 17 209 3GPP TS 38.212 V17.5.0 (2023-03)

Change history
Date Meeting TDoc CR Rev Cat Subject/Comment New
version
2017-05 RAN1#89 R1-1707082 Draft skeleton 0.0.0
2017-07 AH_NR2 R1-1712014 Inclusion of LDPC related agreements 0.0.1
2017-08 RAN1#90 R1-1714564 Inclusion of Polar coding related agreements 0.0.2
2017-08 RAN1#90 R1-1714659 Endorsed version by RAN1#90 as basis for further updates 0.1.0
2017-09 RAN1#90 R1-1715322 Capturing additional agreements on LDPC and Polar code from 0.1.1
RAN1 #90
2017-09 RAN#77 RP-171991 For information to plenary 1.0.0
2017-09 RAN1#90b R1-1716928 Capturing additional agreements on LDPC and Polar code from 1.0.1
RAN1 NR AH#3
2017-10 RAN1#90b R1-1719106 Endorsed as v1.1.0 1.1.0
2017-11 RAN1#91 R1-1719225 Capturing additional agreements on channel coding, etc. 1.1.1
2017-11 RAN1#91 R1-1719245 Capturing additional agreements on DCI format, channel coding, 1.1.2
etc.
2017-11 RAN1#91 R1-1721049 Endorsed as v1.2.0 1.2.0
2017-12 RAN1#91 R1-1721342 Capturing additional agreements on UCI, DCI, channel coding, etc. 1.2.1
2017-12 RAN#78 RP-172668 Endorsed version for approval by plenary. 2.0.0
2017-12 RAN#78 Approved by plenary – Rel-15 spec under change control 15.0.0
2018-03 RAN#79 RP-180200 0001 - F CR capturing the Jan18 ad-hoc and RAN1#92 meeting 15.1.0
agreements
2018-04 RAN#79 MCC: correction of typo in DCI format 0_1 (time domain resource 15.1.1
assignment) – higher layer parameter should be pusch-
AllocationList
2018-06 RAN#80 RP-181172 0002 1 F CR to 38.212 capturing the RAN1#92bis and RAN1#93 meeting 15.2.0
agreements
2018-06 RAN#80 RP-181257 0003 - B CR to 38.212 capturing the RAN1#92bis and RAN1#93 meeting 15.2.0
agreements related to URLLC
2018-09 RAN#81 RP-181789 0004 - F CR to 38.212 capturing the RAN1#94 meeting agreements 15.3.0
2018-12 RAN#82 RP-182523 0005 3 F Combined CR of all essential corrections to 38.212 from 15.4.0
RAN1#94bis and RAN1#95
2019-03 RAN#83 RP-190448 0006 - F Correction of wrong implementation on frequency domain resource 15.5.0
assignment bitwidth
2019-03 RAN#83 RP-190448 0008 - F Correction to UCI multiplexing 15.5.0
2019-03 RAN#83 RP-190448 0009 - F Correction on DCI format 2_3 for SUL cell in TS 38.212 15.5.0
2019-03 RAN#83 RP-190448 0010 - F Corrections to TS38.212 15.5.0
2019-03 RAN#83 RP-190448 0011 - F On bitwidth calculation for DCI fields using RRC parameter 15.5.0
indicating maximum number of MIMO layers per serving cell
2019-03 RAN#83 RP-190448 0012 - F CR on zero-padding of DCI 1_1 in cross-carrier scheduling case 15.5.0
2019-03 RAN#83 RP-190448 0013 - F Clarification on UL_SUL indicator field and SRS request field 15.5.0
2019-06 RAN#84 RP-191282 0014 - F CR on correction to bitwidth of NNZC indicator 15.6.0
2019-06 RAN#84 RP-191282 0015 - F Correction on DCI size alignment in TS 38.212 15.6.0
2019-06 RAN#84 RP-191282 0016 - F Correction on UL/SUL indicator in DCI format 0_0 15.6.0
2019-06 RAN#84 RP-191282 0017 - F Corrections to 38.212 including alignment of terminology across 15.6.0
specifications
2019-06 RAN#84 RP-191282 0018 - F CR on maximum modulation order configured for serving cell 15.6.0
2019-06 RAN#84 RP-191282 0019 1 F Corrections to 38.212 including alignment of terminology across 15.6.0
specifications from RAN1#97
2019-09 RAN#85 RP-191941 0020 - F Corrections to 38.212 including alignment of terminology across 15.7.0
specifications in RAN1#98
2019-12 RAN#86 RP-192625 0021 - F CR on UL/SUL indicator in DCI format 0_1 15.8.0
2019-12 RAN#86 RP-192625 0022 - F Corrections to 38.212 including alignment of terminology across 15.8.0
specifications in RAN1#98bis and RAN1#99
2019-12 RAN#86 RP-192636 0023 - B Introduction of NR based access to unlicensed spectrum into 16.0.0
38.212
2019-12 RAN#86 RP-192637 0024 - B Introduction of IAB into 38.212 16.0.0
2019-12 RAN#86 RP-192638 0025 - B Introduction of 5G V2X sidelink features into TS 38.212 16.0.0

2019-12 RAN#86 RP-192639 0026 - B Introduction of Physical Layer Enhancements for NR URLLC 16.0.0

2019-12 RAN#86 RP-192641 0027 - B Introduction of Enhancements on NR MIMO 16.0.0

2019-12 RAN#86 RP-192642 0028 - B Introduction of power saving in 38.212 16.0.0

2019-12 RAN#86 RP-192645 0029 - B Introduction of MR DC/CA 16.0.0

2019-12 RAN#86 RP-192643 0030 - B Introduction of NR positioning support 16.0.0

2019-12 RAN#86 RP-192635 0031 - B Introduction of two-step RACH 16.0.0

2020-03 RAN#87-e RP-200185 0032 - F Corrections for Rel-16 NR-U after RAN1#100-e 16.1.0

3GPP
Release 17 210 3GPP TS 38.212 V17.5.0 (2023-03)

2020-03 RAN#87-e RP-200190 0033 - F Corrections for NR MIMO after RAN1#100-e 16.1.0

2020-03 RAN#87-e RP-200188 0034 - F Corrections for URLLC after RAN1#100-e 16.1.0

2020-03 RAN#87-e RP-200191 0035 - F Corrections for power saving after RAN1#100-e 16.1.0

2020-03 RAN#87-e RP-200187 0036 - F Corrections on 5G V2X sidelink features after RAN1#100-e 16.1.0

2020-06 RAN#88-e RP-200683 0038 - A CR on L1-RSRP report on PUSCH 16.2.0

2020-06 RAN#88-e RP-200693 0039 1 F Corrections for power saving 16.2.0

2020-06 RAN#88-e RP-200689 0040 1 F Corrections on 5G V2X sidelink features after RAN1#100bis-e and 16.2.0
RAN1#101-e

2020-06 RAN#88-e RP-200694 0041 1 F Corrections in TS 38.212 for NR positioning 16.2.0

2020-06 RAN#88-e RP-200692 0042 1 F Corrections in TS 38.212 for NR MIMO 16.2.0

2020-06 RAN#88-e RP-200696 0043 - F Corrections for Rel-16 MR-DC/CA after RAN1#100bis-e 16.2.0

2020-06 RAN#88-e RP-200690 0044 1 F Corrections on NR eURLLC 16.2.0

2020-06 RAN#88-e RP-200687 0045 1 F Corrections for Rel-16 NR-U 16.2.0

2020-06 RAN#88-e RP-200688 0046 - F Corrections for NR IAB 16.2.0

2020-09 RAN#89-e RP-201814 0047 - F Correction on UCI bit sequence generation 16.3.0

2020-09 RAN#89-e RP-201803 0049 - A CR on PTRS for TS 38.212 16.3.0

2020-09 RAN#89-e RP-201810 0050 - F Alignment of RRC parameter ps-RNTI 16.3.0

2020-09 RAN#89-e RP-201813 0051 - F CR to 38.212 on RRC parameter alignment for SCell dormancy 16.3.0

2020-09 RAN#89-e RP-201807 0052 - F Corrections on 5G V2X sidelink features 16.3.0

2020-09 RAN#89-e RP-201809 0053 - F Corrections to MIMO enhancements 16.3.0

2020-09 RAN#89-e RP-201805 0054 - F Corrections to MIMO enhancements 16.3.0

2020-09 RAN#89-e RP-201808 0055 - F Corrections on NR eURLLC 16.3.0

2020-12 RAN#90-e RP-202390 0056 - F RRC IE name fix to dynamic frequency domain resource allocation 16.4.0
type selection (Rel-15 origin)

2020-12 RAN#90-e RP-202384 0057 - F Correction on Transmission configuration indication in DCI format 16.4.0
1_2

2020-12 RAN#90-e RP-202398 0058 - F Alignment CR for TS 38.212 16.4.0

2021-03 RAN#91-e RP-210052 0059 - F CR on DMRS 16.5.0

2021-03 RAN#91-e RP-210049 0060 - F Correction to description of FDRA field size in DCI 0_0 16.5.0

2021-03 RAN#91-e RP-210049 0061 - F Correction to description of FDRA field interpretation in DCI 0_1 16.5.0

2021-03 RAN#91-e RP-210050 0062 - F Correction on Sidelink Broadcast channel 16.5.0

2021-03 RAN#91-e RP-210049 0063 - F Correction on LBT Type and CP Extension Indication for Semi- 16.5.0
Static Channel Occupancy

2021-03 RAN#91-e RP-210059 0064 - F Alignment CR for TS 38.212 16.5.0

2021-06 RAN#92-e RP-211252 0066 - F 38.212 CR on DAI size determination for DCI format 1_1/1-2 in CA 16.6.0

2021-06 RAN#92-e RP-211236 0067 - F Corrections on parameter of MCS table set to qam256 16.6.0

2021-06 RAN#92-e RP-211234 0068 - D Alignment CR for TS 38.212 (post RAN1#104bis-e) 16.6.0

2021-06 RAN#92-e RP-211234 0069 - F Correction on HARQ-ACK codebook RRC parameter 16.6.0

2021-06 RAN#92-e RP-211236 0070 - F Correction on SRS resource set configuration in TS 38.212 16.6.0

2021-06 RAN#92-e RP-211243 0071 - F Alignment CR for TS 38.212 (post RAN1#105-e) 16.6.0

3GPP
Release 17 211 3GPP TS 38.212 V17.5.0 (2023-03)

3GPP
Release 17 212 3GPP TS 38.212 V17.5.0 (2023-03)

2021-09 RAN#93-e RP-211843 0072 - F Correction on SRS resource set configuration for DCI format 0_2 16.7.0
in TS 38.212

2021-09 RAN#93-e RP-211841 0074 - A Rel-15 editorial corrections for TS 38.212 (mirrored to Rel-16) 16.7.0

2021-09 RAN#93-e RP-211850 0075 - F Alignment CR for TS 38.212 16.7.0

2021-12 RAN#94-e RP-212959 0076 - F Correction on mapping between priority field value and priority 16.8.0
value in SCI format 1-A

2021-12 RAN#94-e RP-212961 0077 - F Changes of channel access types tables in TS 38.212 16.8.0

2021-12 RAN#94-e RP-212961 0078 - F Corrections on CG-UCI multiplexing in TS38.212 16.8.0

2021-12 RAN#94-e RP-212958 0080 - A Clarify UCI bitwidth and UCI mapping order for non-PMI based 16.8.0
CSI feedback

2021-12 RAN#94-e RP-213238 0081 - F Clarification on KNZ to codepoint mapping for eType II CSI 16.8.0

2021-12 RAN#94-e RP-212958 0083 - A Rel-15 editorial corrections for TS 38.212 (mirrored to Rel-16) 16.8.0

2021-12 RAN#94-e RP-212964 0084 - F Alignment CR for TS 38.212 16.8.0

2021-12 RAN#94-e RP-212967 0085 - B Introduction of features to extend current NR operation to 71 GHz 17.0.0

2021-12 RAN#94-e RP-212982 0086 - B Introduction of NR DL 1024QAM for FR1 17.0.0

2021-12 RAN#94-e RP-212973 0087 - B Introduction of Coverage Enhancements 17.0.0

2021-12 RAN#94-e RP-212979 0088 - B Introduction of NR Multicast and Broadcast Services 17.0.0

2021-12 RAN#94-e RP-212966 0089 - B Introduction of Further enhancements on MIMO for NR 17.0.0

2021-12 RAN#94-e RP-212969 0090 - B Introduction of NR non-terrestrial networks (NTN) 17.0.0

2021-12 RAN#94-e RP-212972 0091 - B Introduction of Rel-17 UE power saving enhancements 17.0.0

2021-12 RAN#94-e RP-212968 0092 - B Introduction of Rel-17 enhanced IIoT and URLLC 17.0.0

2021-12 RAN#94-e RP-212980 0093 - B Introduction of NR dynamic spectrum sharing enhancements 17.0.0

2021-12 RAN#94-e RP-212978 0094 - B Introduction of NR sidelink enhancement 17.0.0

2022-03 RAN#95-e RP-220269 0096 - A Correction of NZC partitioning in eType II CSI 17.1.0

2022-03 RAN#95-e RP-220248 0098 - A Correction on Rel-16 UE dormancy adaptation 17.1.0

2022-03 RAN#95-e RP-220252 0099 - F Corrections on enhanced IIoT and URLLC in 38.212 17.1.0

2022-03 RAN#95-e RP-220262 0100 - F Corrections on NR sidelink enhancement in 38.212 17.1.0

2022-03 RAN#95-e RP-220257 0101 - F Corrections on coverage enhancements in 38.212 17.1.0

2022-03 RAN#95-e RP-220263 0102 - F Corrections on NR Multicast and Broadcast Services in 38.212 17.1.0

2022-03 RAN#95-e RP-220256 0103 - F Corrections on UE power saving enhancements in 38.212 17.1.0

2022-03 RAN#95-e RP-220251 0104 - F Correction on extension of current NR operation to 71 GHz in 17.1.0
38.212

2022-03 RAN#95-e RP-220264 0105 - F Corrections on NR dynamic spectrum sharing enhancements in 17.1.0
38.212

2022-03 RAN#95-e RP-220250 0106 - F Corrections on Further enhancements on MIMO for NR in TS 17.1.0
38.212

2022-06 RAN#96 RP-221617 0108 - A Clarification of TPMI indication for UL full power transmission 17.2.0

2022-06 RAN#96 RP-221602 0109 - F Corrections on enhanced IIoT and URLLC in 38.212 17.2.0

2022-06 RAN#96 RP-221612 0110 - F Corrections on NR Multicast and Broadcast Services in 38.212 17.2.0

2022-06 RAN#96 RP-221606 0111 - F Corrections on UE power saving enhancements in 38.212 17.2.0

2022-06 RAN#96 RP-221601 0112 - F Correction on extension of current NR operation to 71 GHz in 17.2.0

3GPP
Release 17 213 3GPP TS 38.212 V17.5.0 (2023-03)

38.212

2022-06 RAN#96 RP-221600 0113 - F Corrections on Further enhancements on MIMO for NR in TS 17.2.0
38.212

2022-06 RAN#96 RP-221599 0115 - A Rel-16 editorial corrections for TS 38.212 (mirrored to Rel-17) 17.2.0

2022-09 RAN#97-e RP-222403 0116 1 F CR on DCI size for Rel-17 NTN HARQ in 38.212 17.3.0

2022-09 RAN#97-e RP-222400 0117 - F CR on the description of the SRS resource set indication for 17.3.0
PUSCH repetition

2022-09 RAN#97-e RP-222401 0118 - F CR on ChannelAccess-Cpext in Fallback DCI 17.3.0

2022-09 RAN#97-e RP-222413 0119 - F CR on DCI size alignment for Cross-carrier scheduling from SCell 17.3.0
to PCell

2022-09 RAN#97-e RP-222406 0120 - F Corrections on UE Power Saving Enhancements for NR in TS 17.3.0
38.212

2022-09 RAN#97-e RP-222412 0121 - F Corrections on NR Multicast and Broadcast Services in 38.212 17.3.0

2022-09 RAN#97-e RP-222411 0122 - F Correction on NR sidelink enhancement 17.3.0

2022-09 RAN#97-e RP-222422 0123 - F Rel-17 editorial corrections for TS 38.212 17.3.0

2022-12 RAN#98-e RP-222863 0124 - F Corrections on resource pool index 17.4.0

2022-12 RAN#98-e RP-222853 0125 - F CR on channel access type indication in non-fallback DCI 17.4.0

2022-12 RAN#98-e RP-222853 0126 - F Correction to support up to 32 HARQ process numbers for FR2-2 17.4.0

2022-12 RAN#98-e RP-222853 0127 - F Correction on TDRA for multiple PUSCH scheduling in TS 38.212 17.4.0

2022-12 RAN#98-e RP-222854 0128 - F CR on priority of CG-UCI 17.4.0

2022-12 RAN#98-e RP-222864 0129 - F CR on number of HARQ-ACK codebooks configurable for 17.4.0
multicast

2022-12 RAN#98-e RP-222865 0130 - F CR on DCI size alignment for Cross-carrier schduling from SCell to 17.4.0
PCell

2022-12 RAN#98-e RP-222868 0131 1 F Rel-17 editorial corrections for TS 38.212 17.4.0

2022-12 RAN#98-e RP-222858 0132 - F Correction on the short message indicator when TRS availability 17.4.0
indication is present

2022-12 RAN#98-e RP-222864 0133 - F CR on format 4_0 DCI size alignment in SCell 17.4.0

2022-12 RAN#98-e RP-222870 0134 - F CR on CSI reporting 17.4.0

2023-03 RAN#99 RP-230451 0135 - F CR on aligning DCI sizes when configuring two HARQ-ACK 17.5.0
codebooks for multicast

2023-03 RAN#99 RP-230443 0136 - F Corrections on intra-UE multiplexing and semi-static channel 17.5.0
occupancy

2023-03 RAN#99 RP-230442 0137 - F CR on DCI field sizes for multiple PDSCHs scheduled by single 17.5.0
DCI

2023-03 RAN#99 RP-230442 0138 - F Corrections to ChanneAccess-CPext field in DCI formats x_2 in 17.5.0
TS38.212

2023-03 RAN#99 RP-230440 0140 - A Rel-16 editorial corrections for TS 38.212 (mirrored to Rel-17) 17.5.0

2023-03 RAN#99 RP-230453 0141 - F Rel-17 editorial corrections for TS 38.212 17.5.0

3GPP

3GPP TS 38.211
No ratings yet
3GPP TS 38.211
143 pages
f00
No ratings yet
f00
83 pages
3GPP TS 38.214
No ratings yet
3GPP TS 38.214
240 pages
3GPP TS 38.211
No ratings yet
3GPP TS 38.211
103 pages
3GPP TS 29.525
No ratings yet
3GPP TS 29.525
62 pages
3gpp 29512-h10
No ratings yet
3gpp 29512-h10
219 pages
1 h80 - Cover
No ratings yet
1 h80 - Cover
18 pages
3GPP TS 38.213
No ratings yet
3GPP TS 38.213
278 pages
1 h60 - Cover
No ratings yet
1 h60 - Cover
17 pages
1 h40 - Cover
No ratings yet
1 h40 - Cover
16 pages
3GPP TS 38.306
No ratings yet
3GPP TS 38.306
266 pages
NR - Physical Channels and Modulation
No ratings yet
NR - Physical Channels and Modulation
130 pages
3GPP TS 38.331
No ratings yet
3GPP TS 38.331
1,328 pages
3GPP TS 38.215
No ratings yet
3GPP TS 38.215
27 pages
3GPP TS 38.214
No ratings yet
3GPP TS 38.214
109 pages
3GPP TS 38.306
No ratings yet
3GPP TS 38.306
174 pages
3GPP TS 38.306
No ratings yet
3GPP TS 38.306
266 pages
3GPP TS 29.507
No ratings yet
3GPP TS 29.507
61 pages
3GPP TS 38.300
No ratings yet
3GPP TS 38.300
211 pages
3 h70 - Cover
No ratings yet
3 h70 - Cover
12 pages
38174-g70 Integrated Access and Backhaul Radio Transmission and Reception
No ratings yet
38174-g70 Integrated Access and Backhaul Radio Transmission and Reception
316 pages
3GPP TS 38.214
No ratings yet
3GPP TS 38.214
106 pages
3GPP TS 23.501
No ratings yet
3GPP TS 23.501
694 pages
3GPP TS 38.211
No ratings yet
3GPP TS 38.211
97 pages
3GPP TS 38.214
No ratings yet
3GPP TS 38.214
315 pages
3GPP TS 37.483
No ratings yet
3GPP TS 37.483
489 pages
3GPP TS 36.101: Technical Specification
No ratings yet
3GPP TS 36.101: Technical Specification
31 pages
3gpp Pathloss
No ratings yet
3gpp Pathloss
98 pages
f00
No ratings yet
f00
71 pages
3GPP TS 38.413
No ratings yet
3GPP TS 38.413
928 pages
3GPP TS 23.204: Technical Specification
No ratings yet
3GPP TS 23.204: Technical Specification
59 pages
3GPP TS 38.202
No ratings yet
3GPP TS 38.202
14 pages
3GPP TS 23.501
No ratings yet
3GPP TS 23.501
14 pages
3GPP TS 38.331
No ratings yet
3GPP TS 38.331
13 pages
3GPP TS 29.571
No ratings yet
3GPP TS 29.571
191 pages
38176-1-g40 Integrated Access and Backhaul (IAB) Part 1 Conformance Testing
No ratings yet
38176-1-g40 Integrated Access and Backhaul (IAB) Part 1 Conformance Testing
219 pages
23247-I60 - Architectural Enhancements For 5G Multicast-Broadcast Services - Stage 2
No ratings yet
23247-I60 - Architectural Enhancements For 5G Multicast-Broadcast Services - Stage 2
138 pages
3GPP TS 38.201
No ratings yet
3GPP TS 38.201
12 pages
3GPP TS 36.413
No ratings yet
3GPP TS 36.413
669 pages
3GPP TS 38.211
No ratings yet
3GPP TS 38.211
97 pages
3GPP TS 36.211
No ratings yet
3GPP TS 36.211
107 pages
38176-2-g40 Integrated Access and Backhaul (IAB) Part 2 Conformance Testing
No ratings yet
38176-2-g40 Integrated Access and Backhaul (IAB) Part 2 Conformance Testing
318 pages
3GPP TS 38.201
No ratings yet
3GPP TS 38.201
12 pages
3GPP TS 21.101
No ratings yet
3GPP TS 21.101
8 pages
38413-h40 v1 Rapp1
No ratings yet
38413-h40 v1 Rapp1
924 pages
3GPP TS 36.212
No ratings yet
3GPP TS 36.212
63 pages
38141-1-I20 Base Station (BS) Conformance Testing Part 1 - Conducted Conformance Testing
No ratings yet
38141-1-I20 Base Station (BS) Conformance Testing Part 1 - Conducted Conformance Testing
351 pages
38104-I20 - Base Station (BS) Radio Transmission and Reception
No ratings yet
38104-I20 - Base Station (BS) Radio Transmission and Reception
377 pages
36211-E40 Cover
No ratings yet
36211-E40 Cover
7 pages
3GPP TS 38.508-1
No ratings yet
3GPP TS 38.508-1
1,317 pages
3GPP TS 38.101-4
No ratings yet
3GPP TS 38.101-4
662 pages
38874-g00 Study On Integrated Access and Backhaul
No ratings yet
38874-g00 Study On Integrated Access and Backhaul
111 pages
3GPP TS 23.289
No ratings yet
3GPP TS 23.289
113 pages
38113-h40 - Base Station (BS) ElectroMagnetic Compatibility (EMC)
No ratings yet
38113-h40 - Base Station (BS) ElectroMagnetic Compatibility (EMC)
34 pages
36212-900 PHYmultiplexing Coding
No ratings yet
36212-900 PHYmultiplexing Coding
63 pages
3GPP TS 23.501
No ratings yet
3GPP TS 23.501
430 pages
3GPP TS 36.300: Technical Specification
No ratings yet
3GPP TS 36.300: Technical Specification
403 pages
3GPP TS 36.423
No ratings yet
3GPP TS 36.423
438 pages
3GPP TR 23.737
No ratings yet
3GPP TR 23.737
96 pages
3GPP TR 21.917
No ratings yet
3GPP TR 21.917
148 pages
HARQ Enhancements for NTN
No ratings yet
HARQ Enhancements for NTN
22 pages
SIMD Extensions and AVX Overview
No ratings yet
SIMD Extensions and AVX Overview
41 pages
Publi-7036 1
No ratings yet
Publi-7036 1
7 pages
Low-Cost SDR for Electro-Smog Monitoring
No ratings yet
Low-Cost SDR for Electro-Smog Monitoring
10 pages
RFIC Noise Testing in Wireless Systems
No ratings yet
RFIC Noise Testing in Wireless Systems
23 pages
Conspicuous Consumption in A Recession - Toning It Down or Turning It Up
No ratings yet
Conspicuous Consumption in A Recession - Toning It Down or Turning It Up
8 pages
International A Level Pure Maths Exam
No ratings yet
International A Level Pure Maths Exam
36 pages
2022 Mechanics Exam Paper
No ratings yet
2022 Mechanics Exam Paper
7 pages
Post-Arrival Quiz - International Student Orientation
No ratings yet
Post-Arrival Quiz - International Student Orientation
3 pages
Nonconformity Management with CARA Tool
No ratings yet
Nonconformity Management with CARA Tool
19 pages
Steps For The Interpretation of The KABC-II
No ratings yet
Steps For The Interpretation of The KABC-II
9 pages
CBS Guide for Cooperative Banks
100% (2)
CBS Guide for Cooperative Banks
55 pages
A Review On Developing Critical Thinking Skills Through Literary Texts
No ratings yet
A Review On Developing Critical Thinking Skills Through Literary Texts
6 pages
Tempco Finned Tubular Heaters
No ratings yet
Tempco Finned Tubular Heaters
15 pages
Mech Sol
No ratings yet
Mech Sol
5 pages
CV Jan 2021 AP Arasinah Kamis
No ratings yet
CV Jan 2021 AP Arasinah Kamis
48 pages
习近平宗教中国化
No ratings yet
习近平宗教中国化
26 pages
History of Cooperative Learning
No ratings yet
History of Cooperative Learning
5 pages
CVT Transmission Wiring Diagram
No ratings yet
CVT Transmission Wiring Diagram
2 pages
Sanako Lab 100 Multi MSU Technical Guide
No ratings yet
Sanako Lab 100 Multi MSU Technical Guide
27 pages
Tvs Wego Projects
100% (1)
Tvs Wego Projects
32 pages
Ajv DPW 00 TMS53 in R03 2972 - 00
No ratings yet
Ajv DPW 00 TMS53 in R03 2972 - 00
2 pages
Rule 130 Evidence 21 Questions
No ratings yet
Rule 130 Evidence 21 Questions
4 pages
En 1426 2024
No ratings yet
En 1426 2024
18 pages
Chemical Formulas of Common Substances
No ratings yet
Chemical Formulas of Common Substances
7 pages
The Role of Technology in Shaping Business Communication
No ratings yet
The Role of Technology in Shaping Business Communication
6 pages
Imapct of Working Capital Management On Profitability of The Select Commercial Vehicle Manufacturers in India
No ratings yet
Imapct of Working Capital Management On Profitability of The Select Commercial Vehicle Manufacturers in India
11 pages
Annotated Bibliography
0% (1)
Annotated Bibliography
4 pages
Mygov 10000000001887797823
No ratings yet
Mygov 10000000001887797823
3 pages
CH 13: Secondary Metabolism and Plant Defense
No ratings yet
CH 13: Secondary Metabolism and Plant Defense
48 pages
Hertha Ayrton: Pioneer Scientist and Inventor
No ratings yet
Hertha Ayrton: Pioneer Scientist and Inventor
6 pages
A Complete Tetris 99 Guide - From Beginner To Expert
No ratings yet
A Complete Tetris 99 Guide - From Beginner To Expert
21 pages
Chapter 7 Commercial Bank
No ratings yet
Chapter 7 Commercial Bank
43 pages
CO2's Role in Scale Formation
No ratings yet
CO2's Role in Scale Formation
11 pages
January 2022 (IAL) QP
No ratings yet
January 2022 (IAL) QP
28 pages

3GPP TS 38.212

Uploaded by

3GPP TS 38.212

Uploaded by

3GPP TS 38.212 V17.5.

3GPP support office address

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

[Link].2 UCI encoded by channel coding of small block lengths..................................................................67

[Link].1 Format 0_0......................................................................................................................................117

Annex <A> (informative): Change history.................................................................................................199

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.

- For a specific reference, subsequent revisions do not apply.

[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.213: "NR; Physical layer procedures for control"

[6] 3GPP TS 38.214: "NR; Physical layer procedures for data"

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

[10] 3GPP TS 38.473: "NG-RAN; F1 Application Protocol (F1AP)"

3 Definitions, symbols and abbreviations

BCH Broadcast channel

4 Mapping to physical channels

TrCH Physical Channel

Control information Physical Channel

TrCH Physical Channel

Control information Physical Channel

TrCH Physical Channel

Control information Physical Channel

5.1 CRC calculation

- gCRC24B ( D )=[ D 24 + D23+ D6 + D5 + D+1 ] for a CRC length L=24 ;

- gCRC16 ( D ) =[ D16+ D12+ D5 +1 ] for a CRC length L=16 ;

- gCRC11 ( D )=[ D 11 + D 10 + D 9 + D 5 +1 ] for a CRC length L=11 ;

- gCRC6 ( D )=[ D6 + D5 +1 ] for a CRC length L=6 .

a 0 D A +L−1 +a1 D A +L−2 +. . .+a A −1 D L + p0 D L−1 + p1 D L−2 +. ..+ p L−2 D1 + p L−1

The bits after CRC attachment are denoted by

b k =ak for k=0,1,2,..., A−1

b k =p k −A for k= A , A +1, A+2,..., A +L−1 .

5.2 Code block segmentation and code block CRC attachment

Number of code blocks: C=2 ;

Number of code blocks:

A '=⌈ A/C ⌉⋅C ;

for i=0 to A '−A−1

for i= A '− A to A '−1

a ' i=ai−( A '− A )

for k =0 to A '/ C−1

for k = A '/ C to A '/ C+L−1

The value of A is no larger than 1706.

5.2.2 Low density parity check coding

Total number of code blocks C is determined by:

Number of code blocks: C=1

The number of bits in each code block is calculated as:

For LDPC base graph 1,

For LDPC base graph 2,

The bit sequence is calculated as:

c ,c ,c ,c ,...,cr ( K '−L−1 ) p , p , p , .. . , p r ( L−1 )

for k =K '−L to K '−1

for k =K ' to K−1 -- Insertion of filler bits

5.3 Channel coding

Table 5.3-1: Usage of channel coding scheme for TrCHs

TrCH Coding scheme

Table 5.3-2: Usage of channel coding scheme for control information

Control Information Coding scheme

5.3.1 Polar coding

n=max { min { n1 , n2 , nmax } , n min }

UE is not expected to be configured with , where

The bit sequence

where the interleaving pattern Π ( k ) is given by the following:

[Link] Polar encoding

{ } is given by Table [Link]-1, where 0≤QNi

bit index before Polar encoding for

for n=0 to N−1

for n=0 to N−1

d= [ d 0 d 1 d 2 . .. d N−1 ] d=uG N . The encoding is performed in GF(2).

and its corresponding reliability W ( Qi )

W ( Qi ) QiN W ( Qi ) QiN W ( Qi ) QiN W ( Qi ) QiN W ( Qi ) QiN W ( Qi ) QiN W ( Qi ) QiN W ( Qi ) QiN

5.3.2 Low density parity check coding