0% found this document useful (0 votes)

815 views153 pages

3GPP TS 38.212

Uploaded by

vikram_908116002

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

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

815 views153 pages

3GPP TS 38.212

Uploaded by

vikram_908116002

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

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 153

3GPP TS 38.212 V16.6.

0 (2021-06)
Technical Specification

3rd Generation Partnership Project;

Technical Specification Group Radio Access Network;
NR;
Multiplexing and channel coding
(Release 16)

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

Keywords
3GPP, New Radio, Layer 1

3GPP

Postal address

3GPP support office address

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

Internet
http://www.3gpp.org

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 16156T 3 3GPP TS 38.212 V16.6.0 (2021-06)

Contents
Foreword ............................................................................................................................................................ 6
1 Scope ........................................................................................................................................................ 7
2 References ................................................................................................................................................ 7
3 Definitions, symbols and abbreviations ................................................................................................... 7
3.1 Definitions ......................................................................................................................................................... 7
3.2 Symbols ............................................................................................................................................................. 7
3.3 Abbreviations ..................................................................................................................................................... 8
4 Mapping to physical channels .................................................................................................................. 9
4.1 Uplink ................................................................................................................................................................ 9
4.2 Downlink ........................................................................................................................................................... 9
4.3 Sidelink .............................................................................................................................................................. 9
5 General procedures................................................................................................................................. 10
5.1 CRC calculation ............................................................................................................................................... 10
5.2 Code block segmentation and code block CRC attachment ............................................................................ 10
5.2.1 Polar coding ............................................................................................................................................... 10
5.2.2 Low density parity check coding................................................................................................................ 11
5.3 Channel coding ................................................................................................................................................ 13
5.3.1 Polar coding ............................................................................................................................................... 13
5.3.1.1 Interleaving ........................................................................................................................................... 14
5.3.1.2 Polar encoding ...................................................................................................................................... 15
5.3.2 Low density parity check coding................................................................................................................ 19
5.3.3 Channel coding of small block lengths ...................................................................................................... 26
5.3.3.1 Encoding of 1-bit information .............................................................................................................. 26
5.3.3.2 Encoding of 2-bit information .............................................................................................................. 26
5.3.3.3 Encoding of other small block lengths ................................................................................................. 26
5.4 Rate matching .................................................................................................................................................. 27
5.4.1 Rate matching for Polar code ..................................................................................................................... 27
5.4.1.1 Sub-block interleaving.......................................................................................................................... 27
5.4.1.2 Bit selection .......................................................................................................................................... 28
5.4.1.3 Interleaving of coded bits ..................................................................................................................... 29
5.4.2 Rate matching for LDPC code ................................................................................................................... 30
5.4.2.1 Bit selection .......................................................................................................................................... 30
5.4.2.2 Bit interleaving ..................................................................................................................................... 32
5.4.3 Rate matching for channel coding of small block lengths.......................................................................... 33
5.5 Code block concatenation ................................................................................................................................ 33
6 Uplink transport channels and control information ................................................................................ 33
6.1 Random access channel ................................................................................................................................... 33
6.2 Uplink shared channel ..................................................................................................................................... 34
6.2.1 Transport block CRC attachment ............................................................................................................... 34
6.2.2 LDPC base graph selection ........................................................................................................................ 34
6.2.3 Code block segmentation and code block CRC attachment ....................................................................... 34
6.2.4 Channel coding of UL-SCH ....................................................................................................................... 34
6.2.5 Rate matching............................................................................................................................................. 34
6.2.6 Code block concatenation .......................................................................................................................... 35
6.2.7 Data and control multiplexing .................................................................................................................... 35
6.3 Uplink control information .............................................................................................................................. 46
6.3.1 Uplink control information on PUCCH ..................................................................................................... 46
6.3.1.1 UCI bit sequence generation................................................................................................................. 46
6.3.1.1.1 HARQ-ACK/SR only ..................................................................................................................... 46
6.3.1.1.2 CSI only .......................................................................................................................................... 47
6.3.1.1.3 HARQ-ACK/SR and CSI ............................................................................................................... 54
6.3.1.2 Code block segmentation and CRC attachment.................................................................................... 55
6.3.1.2.1 UCI encoded by Polar code ............................................................................................................ 55
6.3.1.2.2 UCI encoded by channel coding of small block lengths ................................................................. 55
6.3.1.3 Channel coding of UCI ......................................................................................................................... 56

3GPP
Release 16156T 4 3GPP TS 38.212 V16.6.0 (2021-06)

6.3.1.3.1 UCI encoded by Polar code ............................................................................................................ 56

6.3.1.3.2 UCI encoded by channel coding of small block lengths ................................................................. 56
6.3.1.4 Rate matching ....................................................................................................................................... 56
6.3.1.4.1 UCI encoded by Polar code ............................................................................................................ 56
6.3.1.4.2 UCI encoded by channel coding of small block lengths ................................................................. 57
6.3.1.5 Code block concatenation ..................................................................................................................... 58
6.3.1.6 Multiplexing of coded UCI bits to PUCCH.......................................................................................... 58
6.3.2 Uplink control information on PUSCH ...................................................................................................... 60
6.3.2.1 UCI bit sequence generation................................................................................................................. 60
6.3.2.1.1 HARQ-ACK ................................................................................................................................... 60
6.3.2.1.2 CSI .................................................................................................................................................. 61
6.3.2.1.3 CG-UCI........................................................................................................................................... 67
6.3.2.1.4 HARQ-ACK and CG-UCI .............................................................................................................. 68
6.3.2.2 Code block segmentation and CRC attachment.................................................................................... 68
6.3.2.2.1 UCI encoded by Polar code ............................................................................................................ 68
6.3.2.2.2 UCI encoded by channel coding of small block lengths ................................................................. 68
6.3.2.3 Channel coding of UCI ......................................................................................................................... 68
6.3.2.3.1 UCI encoded by Polar code ............................................................................................................ 68
6.3.2.3.2 UCI encoded by channel coding of small block lengths ................................................................. 68
6.3.2.4 Rate matching ....................................................................................................................................... 69
6.3.2.4.1 UCI encoded by Polar code ............................................................................................................ 69
6.3.2.4.1.1 HARQ-ACK .............................................................................................................................. 69
6.3.2.4.1.2 CSI part 1 .................................................................................................................................. 71
6.3.2.4.1.3 CSI part 2 .................................................................................................................................. 74
6.3.2.4.1.4 CG-UCI ..................................................................................................................................... 77
6.3.2.4.1.5 HARQ-ACK and CG-UCI ........................................................................................................ 78
6.3.2.4.2 UCI encoded by channel coding of small block lengths ................................................................. 78
6.3.2.4.2.1 HARQ-ACK .............................................................................................................................. 78
6.3.2.4.2.2 CSI part 1 .................................................................................................................................. 79
6.3.2.4.2.3 CSI part 2 .................................................................................................................................. 79
6.3.2.4.2.4 CG-UCI ..................................................................................................................................... 79
6.3.2.4.2.5 HARQ-ACK and CG-UCI ........................................................................................................ 79
6.3.2.5 Code block concatenation ..................................................................................................................... 80
6.3.2.6 Multiplexing of coded UCI bits to PUSCH .......................................................................................... 80
7 Downlink transport channels and control information ........................................................................... 80
7.1 Broadcast channel ............................................................................................................................................ 80
7.1.1 PBCH payload generation .......................................................................................................................... 80
7.1.2 Scrambling ................................................................................................................................................. 82
7.1.3 Transport block CRC attachment ............................................................................................................... 82
7.1.4 Channel coding........................................................................................................................................... 83
7.1.5 Rate matching............................................................................................................................................. 83
7.2 Downlink shared channel and paging channel ................................................................................................. 83
7.2.1 Transport block CRC attachment ............................................................................................................... 83
7.2.2 LDPC base graph selection ........................................................................................................................ 83
7.2.3 Code block segmentation and code block CRC attachment ....................................................................... 83
7.2.4 Channel coding........................................................................................................................................... 84
7.2.5 Rate matching............................................................................................................................................. 84
7.2.6 Code block concatenation .......................................................................................................................... 84
7.3 Downlink control information ......................................................................................................................... 84
7.3.1 DCI formats................................................................................................................................................ 84
7.3.1.0 DCI size alignment ............................................................................................................................... 85
7.3.1.0.1 DCI size alignment for DCI formats for scheduling of sidelink ..................................................... 88
7.3.1.1 DCI formats for scheduling of PUSCH ................................................................................................ 88
7.3.1.1.1 Format 0_0 ...................................................................................................................................... 88
7.3.1.1.2 Format 0_1 ...................................................................................................................................... 92
7.3.1.1.3 Format 0_2 .................................................................................................................................... 112
7.3.1.2 DCI formats for scheduling of PDSCH .............................................................................................. 118
7.3.1.2.1 Format 1_0 .................................................................................................................................... 118
7.3.1.2.2 Format 1_1 .................................................................................................................................... 121
7.3.1.2.3 Format 1_2 .................................................................................................................................... 136
7.3.1.3 DCI formats for other purposes .......................................................................................................... 139

3GPP
Release 16156T 5 3GPP TS 38.212 V16.6.0 (2021-06)

7.3.1.3.1 Format 2_0 .................................................................................................................................... 139

7.3.1.3.2 Format 2_1 .................................................................................................................................... 140
7.3.1.3.3 Format 2_2 .................................................................................................................................... 140
7.3.1.3.4 Format 2_3 .................................................................................................................................... 140
7.3.1.3.5 Format 2_4 .................................................................................................................................... 141
7.3.1.3.7 Format 2_6 .................................................................................................................................... 141
7.3.1.4 DCI formats for scheduling of sidelink .............................................................................................. 142
7.3.1.4.1 Format 3_0 .................................................................................................................................... 142
7.3.1.4.2 Format 3_1 .................................................................................................................................... 142
7.3.2 CRC attachment ....................................................................................................................................... 143
7.3.3 Channel coding......................................................................................................................................... 143
7.3.4 Rate matching........................................................................................................................................... 144
8 Sidelink transport channels and control information ........................................................................... 144
8.1 Sidelink broadcast channel ............................................................................................................................ 144
8.1.1 (void) ........................................................................................................................................................ 144
8.2 Sidelink shared channel ................................................................................................................................. 144
8.2.1 Data and control multiplexing .................................................................................................................. 144
8.3 Sidelink control information on PSCCH ....................................................................................................... 145
8.3.1 1st-stage SCI formats ................................................................................................................................ 145
8.3.1.1 SCI format 1-A ................................................................................................................................... 145
8.3.2 CRC attachment ....................................................................................................................................... 147
8.3.3 Channel coding......................................................................................................................................... 147
8.3.4 Rate Matching .......................................................................................................................................... 147
8.4 Sidelink control information on PSSCH ........................................................................................................ 147
8.4.1 2nd-stage SCI formats ............................................................................................................................... 147
8.4.1.1 SCI format 2-A ................................................................................................................................... 147
8.4.1.2 SCI format 2-B ................................................................................................................................... 148
8.4.2 CRC attachment ....................................................................................................................................... 148
8.4.3 Channel coding......................................................................................................................................... 148
8.4.4 Rate Matching .......................................................................................................................................... 148
8.4.5 Multiplexing of coded 2nd-stage SCI bits to PSSCH ................................................................................ 149

Annex A: Change history .................................................................................................................... 150

3GPP
Release 16156T 6 3GPP TS 38.212 V16.6.0 (2021-06)

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 16156T 7 3GPP TS 38.212 V16.6.0 (2021-06)

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 16156T 8 3GPP TS 38.212 V16.6.0 (2021-06)

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 16156T 9 3GPP TS 38.212 V16.6.0 (2021-06)

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 16156T 10 3GPP TS 38.212 V16.6.0 (2021-06)

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 a 0 , a1 , a 2 , a 3 ,..., a A−1 , and the parity bits by p 0 , p1 , p 2 , p 3 ,..., p L −1 ,
where A is the size of the input sequence and L is the number of parity bits. The parity bits are generated by one of
the following cyclic generator polynomials:

- g CRC24A (D ) = [ D 24 + D 23 + D18 + D17 + D14 + D11 + D10 + D 7 + D 6 + D 5 + D 4 + D 3 + D + 1] for a CRC length

L = 24 ;

- g CRC24B (D ) = [ D 24 + D 23 + D 6 + D 5 + D + 1] for a CRC length L = 24 ;

- g CRC24C (D ) = [ D 24 + D 23 + D 21 + D 20 + D17 + D15 + D13 + D12 + D 8 + D 4 + D 2 + D + 1] for a CRC length L = 24 ;

- g CRC16 (D ) = [ D16 + D12 + D 5 + 1] for a CRC length L = 16 ;

- g CRC11 (D ) = [ D11 + D10 + D 9 + D 5 + 1] for a CRC length L = 11 ;

- g CRC6 (D ) = [ D 6 + D 5 + 1] for a CRC length L = 6 .

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

a0 D A+ L−1 + a1 D A+ L−2 + ... + a A−1 D L + p0 DL−1 + p1 D L−2 + ... + pL−2 D1 + pL−1

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

The bits after CRC attachment are denoted by b0 , b1 , b2 , b3 ,..., b B −1 , where B = A + L . The relation between ak and
bk is:

bk = a k for k = 0,1,2,..., A − 1

bk = 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 , a 3 ,..., a A−1 , where A > 0 .

if I seg = 1

Number of code blocks: C = 2 ;

else

Number of code blocks: C = 1

3GPP
Release 16156T 11 3GPP TS 38.212 V16.6.0 (2021-06)

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

crk = a ' s ;

s = s +1;
end for

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

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

crk = 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 b0 , b1 , b2 , b3 ,..., b B −1 , where B > 0 . If B is
larger than the maximum code block size K 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 .

Total number of code blocks C is determined by:

if B ≤ K cb

L=0
Number of code blocks: C = 1

3GPP
Release 16156T 12 3GPP TS 38.212 V16.6.0 (2021-06)

B′ = B
else

L = 24
Number of code blocks: C = B / (K cb − L ) .

B′ = B + C ⋅ L

end if

The bits output from code block segmentation are denoted by c r 0 , c r1 , c r 2 , c r 3 ,..., c r (K r −1) , 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 K 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

Kb = 9 ;

elseif B > 192

Kb = 8 ;

else

Kb = 6 ;

end if

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

The bit sequence crk is calculated as:

s =0;

for r = 0 to C − 1

for k = 0 to K '−L − 1

crk = bs ;

s = s +1;

end for

3GPP
Release 16156T 13 3GPP TS 38.212 V16.6.0 (2021-06)

if C > 1

The sequence cr 0 , cr1 , cr 2 , cr 3 ,..., cr ( K '− L−1) is used to calculate the CRC parity bits p r 0 , p r1 , p r 2 ,..., p r (L −1)
according to Clause 5.1 with the generator polynomial g CRC24B (D ) .

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

crk = pr (k + L− K ' )
;

end for

end if

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

crk =< 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 , c1 , 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 , where N = 2 n and the value of n
is determined by the following:

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

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

n1 = log 2 E  − 1 ;

else

n1 = log 2 E  ;

end if

3GPP
Release 16156T 14 3GPP TS 38.212 V16.6.0 (2021-06)

Rmin = 1 / 8 ;

n2 = log 2 (K / Rmin ) ;

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

where nmin = 5 .

UE is not expected to be configured with K + nPC > E , where nPC is the number of parity check bits defined in
Clause 5.3.1.2.

5.3.1.1 Interleaving
The bit sequence c 0 , c1 , 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:

ck′ = 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;
for m = 0 to K ILmax − 1

IL (m ) ≥ K IL − K
if Π max max

Π (k ) = Π max (
IL (m ) − K IL − K
max
; )
k = k +1 ;
end if

end for

end if

IL (m )
where Π max is given by Table 5.3.1.1-1 and K ILmax = 164 .

3GPP
Release 16156T 15 3GPP TS 38.212 V16.6.0 (2021-06)

IL (m )
Table 5.3.1.1-1: Interleaving pattern Π max

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

5.3.1.2 Polar encoding

{ }
The Polar sequence Q 0N max −1 = Q0N max , Q1N max ,..., QNN max−1 is given by Table 5.3.1.2-1, where 0 ≤ QiN max ≤ N max − 1 denotes
max

a bit index before Polar encoding for i = 0,1,..., N max − 1 and N max = 1024 . The Polar sequence Q 0N max −1 is in
( ) ( ) ( )
ascending order of reliability W Q0N max < W Q1N max < ... < W QNN max−1 , where W QiN max denotes the reliability of bit
max
( )
N max
index Q i
.

{
For any code block encoded to N bits, a same Polar sequence Q 0N −1 = Q0N , Q1N , Q2N ,..., QNN−1 is used. The Polar }
sequence Q 0N −1 is a subset of Polar sequence Q 0N max −1 with all elements QiN max of values less than N , ordered in
( ) ( )
ascending order of reliability W Q0N < W Q1N < W Q2N < ... < W QNN−1 . ( ) ( )
Denote Q IN as a set of bit indices in Polar sequence Q 0N −1 , and Q FN as the set of other bit indices in Polar sequence
Q 0N −1 , where Q IN and Q FN are given in Clause 5.4.1.1, Q IN = K + nPC , Q FN = N − Q IN , and nPC is the
number of parity check bits.

1 0
Denote G N = (G 2 )
⊗n
as the n -th Kronecker power of matrix G 2 , where G 2 =  .
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(g j ) is the number of ones in g j . Denote the set of bit indices for parity check bits as Q PC
N
, where
N
Q PC = nPC . A number of nPC − nPC
wm
( ) parity check bits are placed in the (n PC − nPC
wm
)
least reliable bit indices in
wm ~
Q IN . A number of nPC other parity check bits are placed in the bit indices of minimum row weight in Q IN , where
~
( )
Q IN denotes the QIN − nPC most reliable bit indices in Q IN ; if there are more than nPC bit indices of the same
wm

~N wm wm
minimum row weight in Q I
, the nPC other parity check bits are placed in the nPC bit indices of the highest
~N
reliability and the minimum row weight in Q I .

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

k = 0;

3GPP
Release 16156T 16 3GPP TS 38.212 V16.6.0 (2021-06)

if nPC > 0

y0 = 0 ; y1 = 0 ; y2 = 0 ; y3 = 0 ; y4 = 0 ;

for n = 0 to N − 1

yt = y0 ; y0 = y1 ; y1 = y2 ; y2 = y3 ; y3 = y4 ; y4 = yt ;

if n ∈ Q IN

if n ∈ Q PC
N

u n = y0 ;

else

u n = ck' ;

k = k +1;

y0 = y0 ⊕ u n ;

end if

else

un = 0 ;

end if

end for

else

for n = 0 to N − 1

if n ∈ Q IN

u n = ck' ;

k = k +1;
else

un = 0 ;

end if

end for

end if

The output after encoding d = [d 0 d1 d 2 ... d N −1 ] is obtained by d = uG N . The encoding is performed in GF(2).

3GPP
Release 16156T 17 3GPP TS 38.212 V16.6.0 (2021-06)

(
Table 5.3.1.2-1: Polar sequence Q 0N max −1 and its corresponding reliability W QiN max )

3GPP
Release 16156T 18 3GPP TS 38.212 V16.6.0 (2021-06)

(
W QiNmax ) QiN max (
W QiNmax ) QiN max (
W QiNmax ) QiN max (
W QiNmax ) QiN max (
W QiNmax ) QiN max (
W QiNmax ) QiN max (
W QiNmax ) QiN max (
W QiNmax ) QiN 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
61 49 189 577 317 174 445 397 573 678 701 783 829 799 957 1000
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
66 288 194 269 322 122 450 785 578 458 706 791 834 477 962 1008
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
86 56 214 87 342 286 470 244 598 249 726 485 854 873 982 998

3GPP
Release 16156T 19 3GPP TS 38.212 V16.6.0 (2021-06)

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
90 259 218 61 346 211 474 676 602 803 730 634 858 860 986 1001
91 84 219 531 347 401 475 361 603 789 731 744 859 499 987 951
92 138 220 525 348 185 476 706 604 709 732 852 860 731 988 1002
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
96 43 224 526 352 645 480 647 608 689 736 797 864 918 992 1009
97 98 225 177 353 593 481 348 609 374 737 906 865 502 993 955
98 515 226 293 354 535 482 419 610 423 738 715 866 933 994 1004
99 88 227 388 355 240 483 406 611 466 739 807 867 743 995 1010
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
104 262 232 172 360 800 488 590 616 574 744 717 872 921 1000 1012
105 265 233 120 361 402 489 409 617 413 745 575 873 501 1001 999
106 161 234 201 362 356 490 570 618 603 746 913 874 876 1002 1016
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
109 100 237 282 365 417 493 572 621 655 749 379 877 447 1005 1003
110 640 238 143 366 213 494 219 622 900 750 697 878 733 1006 990
111 51 239 103 367 568 495 311 623 805 751 431 879 827 1007 1005
112 148 240 178 368 832 496 708 624 615 752 607 880 934 1008 959
113 46 241 294 369 588 497 598 625 684 753 489 881 882 1009 1011
114 75 242 93 370 186 498 601 626 710 754 866 882 937 1010 1013
115 266 243 644 371 646 499 651 627 429 755 723 883 963 1011 895
116 273 244 202 372 404 500 421 628 794 756 486 884 747 1012 1006
117 517 245 592 373 227 501 792 629 252 757 908 885 505 1013 1014
118 104 246 323 374 896 502 802 630 373 758 718 886 855 1014 1017
119 162 247 392 375 594 503 611 631 605 759 813 887 924 1015 1018
120 53 248 297 376 418 504 602 632 848 760 476 888 734 1016 991
121 193 249 770 377 302 505 410 633 690 761 856 889 829 1017 1020
122 152 250 107 378 649 506 231 634 713 762 839 890 965 1018 1007
123 77 251 180 379 771 507 688 635 632 763 725 891 938 1019 1015
124 164 252 151 380 360 508 653 636 482 764 698 892 884 1020 1019
125 768 253 209 381 539 509 248 637 806 765 914 893 506 1021 1021
126 268 254 284 382 111 510 369 638 427 766 752 894 749 1022 1022
127 274 255 648 383 331 511 190 639 904 767 868 895 945 1023 1023

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 , c1 , 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 d 0 , d1 , d 2 ,..., 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 iLS in Table 5.3.2-1 which contains Z c .

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

if ck ≠< NULL >

d k −2 Zc = ck ;

else

ck = 0 ;

d k −2 Zc =< NULL > ;

end if

end for

3GPP
Release 16156T 20 3GPP TS 38.212 V16.6.0 (2021-06)

[
3) Generate N + 2 Z c − K parity bits w = w0 , w1 , w2 ,..., wN + 2 Z − K −1
c
]
such that H ×   = 0 , where
T c
w 
 
c = [c0 , c1 , c2 ,..., cK −1 ] ; 0 is a column vector of all elements equal to 0. The encoding is performed in GF(2).
T

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
column indices j = 0,1,2,...,67 . For LDPC base graph 2, a matrix of H 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.

The matrix H is obtained by replacing each element of H BG with a Z c × Z c matrix, according to the
following:

- 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 (Pi , j ) of size Z c × Z c , where
i and j are the row and column indices of the element, and I(Pi , j ) is obtained by circularly shifting the
identity matrix I of size Z c × Z c to the right Pi , j times. The value of Pi , j is given by Pi , j = mod(Vi , j , Z c ) .
The value of Vi , j is given by Tables 5.3.2-2 and 5.3.2-3 according to the set index iLS and LDPC base
graph.

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

d k −2 Zc = wk − K ;

end for

Table 5.3.2-1: Sets of LDPC lifting size Z

Set index ( iLS ) 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 16156T 21 3GPP TS 38.212 V16.6.0 (2021-06)

Table 5.3.2-2: LDPC base graph 1 ( H BG ) and its parity check matrices ( Vi , j )

3GPP
Release 16156T 22 3GPP TS 38.212 V16.6.0 (2021-06)

H BG Vi , j H BG Vi , j
Row Column Row Column
index index
Set index iLS index index
Set index iLS
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
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
5
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 16156T 23 3GPP TS 38.212 V16.6.0 (2021-06)

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 16156T 24 3GPP TS 38.212 V16.6.0 (2021-06)

Table 5.3.2-3: LDPC base graph 2 ( H BG ) and its parity check matrices ( Vi , j )

3GPP
Release 16156T 25 3GPP TS 38.212 V16.6.0 (2021-06)

H BG Vi , j H BG Vi , j
Row Column Row Column
index index
Set index iLS index index
Set index iLS
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
0 83 49 0 37 76 29 32 48 47 0 0 0 0 0 0 0 0
13
1 2 125 112 113 37 91 53 57 38 1 31 84 0 37 1 112 157 42

3GPP
Release 16156T 26 3GPP TS 38.212 V16.6.0 (2021-06)

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

5.3.3.1 Encoding of 1-bit information

For K = 1 , the code block is encoded according to Table 5.3.3.1-1, where N = Qm and Qm is the modulation order
for the code block.

Table 5.3.3.1-1: Encoding of 1-bit information

Qm Encoded bits d 0 , d1 , d 2 ,..., d N −1

1 [c0 ]
2 [c0 y]
4 [c0 y x x]
6 [ c0 y x x x x ]
8 [ c0 y x x x x x x ]
The "x" and "y" in Table 5.3.3.1-1 are placeholders for Clause 6.3.1.1 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.

5.3.3.2 Encoding of 2-bit information

For K = 2 , the code block is encoded according to Table 5.3.3-2, where c2 = (c0 + c1 ) mod 2 , N = 3Qm , and Qm is
the modulation order for the code block.

Table 5.3.3.2-1: Encoding of 2-bit information

Qm Encoded bits d 0 , d1 , d 2 ,..., d N −1

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 [c0 c1 x x x x x x c2 c0 x x x x x x c1 c2 x x x x x x]
The "x" in Table 5.3.3.2-1 are placeholders for Clause 6.3.1.1 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.

5.3.3.3 Encoding of other small block lengths

For 3 ≤ K ≤ 11 , the code block is encoded by d i =  ∑ ck ⋅ M i ,k  mod 2 , where i = 0, 1, , N − 1 , N = 32 , and M i ,k

K −1

 k =0 
represents the basis sequences as defined in Table 5.3.3.3-1.

3GPP
Release 16156T 27 3GPP TS 38.212 V16.6.0 (2021-06)

Table 5.3.3.3-1: Basis sequences for (32, K ) code

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

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 , f1 , f 2 ,..., f E −1 .

5.4.1.1 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 y0 , y1 , y2 ,..., y N −1 , generated as
follows:

for n = 0 to N − 1

i = 32n / N  ;

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

y n = d J (n ) ;

3GPP
Release 16156T 28 3GPP TS 38.212 V16.6.0 (2021-06)

end for

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

Table 5.4.1.1-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

The sets of bit indices Q IN and Q FN are determined as follows, where K , nPC , and Q 0N −1 are defined in Clause
5.3.1

Q FN,tmp = ∅

if E < N

if K / E ≤ 7 / 16 -- puncturing

for n = 0 to N − E − 1

QFN,tmp = QFN,tmp  {J (n )} ;

end for

if E ≥ 3N / 4

Q FN,tmp = Q FN,tmp  {0,1,, 3 N / 4 − E / 2 − 1};

else

Q FN,tmp = Q FN,tmp  {0,1,, 9 N / 16 − E / 4 − 1};

end if

else -- shortening

for n = E to N − 1

QFN,tmp = QFN,tmp  {J (n )} ;

end for

end if

Q IN,tmp = Q 0N −1 \ Q FN,tmp ;

Q IN comprises (K + nPC ) most reliable bit indices in Q IN,tmp ;

Q FN = Q 0N −1 \ Q IN ;

5.4.1.2 Bit selection

The bit sequence after the sub-block interleaver y0 , y1 , y2 ,..., y N −1 from Clause 5.4.1.1 is written into a circular buffer of
length N .

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

3GPP
Release 16156T 29 3GPP TS 38.212 V16.6.0 (2021-06)

if E ≥ N -- repetition

for k = 0 to E − 1

ek = ymod( k , N ) ;

end for

else

if K / E ≤ 7 / 16 -- puncturing

for k = 0 to E − 1

ek = yk + N − E ;
end for

else -- shortening

for k = 0 to E − 1

ek = yk ;
end for

end if

5.4.1.3 Interleaving of coded bits

The bit sequence e0 , e1 , e2 ,..., eE −1 is interleaved into bit sequence f 0 , f1 , f 2 ,..., f E −1 , as follows:

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

vi , j = ek ;

else

vi, j =< NULL > ;

end if

k = k +1;
end for

end for

k = 0;
for j = 0 to T − 1

3GPP
Release 16156T 30 3GPP TS 38.212 V16.6.0 (2021-06)

for i = 0 to T −1 − j

if vi, j ≠< NULL >

f k = vi , 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.

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 , f1 , f 2 ,..., f E −1 .

5.4.2.1 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 N cb = N if I LBRM = 0 and N cb = min (N , N ref ) =
 TBS LBRM  ,
otherwise, where N

 C ⋅ RLBRM 
ref

RLBRM = 2 / 3 , TBS LBRM is determined according to Clause 6.1.4.2 in [6, TS 38.214] for UL-SCH and Clause 5.1.3.2 in
[6, TS 38.214] for DL-SCH/PCH, assuming the following:

- 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

- 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 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 Qm = 8 is assumed for DL-SCH;
otherwise a maximum modulation order Qm = 6 is assumed for DL-SCH;

3GPP
Release 16156T 31 3GPP TS 38.212 V16.6.0 (2021-06)

- 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 Qm = 8 is assumed for UL-SCH; otherwise a maximum
modulation order Qm = 6 is assumed for UL-SCH

- maximum coding rate of 948/1024;

- nPRB = nPRB , LBRM is given by Table 5.4.2.1-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;

- N=
RE 156 ⋅ nPRB ;

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

Table 5.4.2.1-1: Value of nPRB , LBRM

Maximum number of PRBs across all configured DL BWPs and UL BWPs of a carrier for DL- nPRB , LBRM
SCH and UL-SCH, respectively
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 E r the rate matching output sequence length for the r -th coded block, where the value of E r is
determined as follows:

Set j = 0

for r = 0 to C − 1

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

Er = 0 ;

else

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

 G ;
E r = N L ⋅ Qm ⋅  
 N L ⋅ Qm ⋅ C ' 

else

 G ;
E r = N L ⋅ Qm ⋅  
N ⋅
 L m Q ⋅ C ' 

end if

j = j + 1;

end if

3GPP
Release 16156T 32 3GPP TS 38.212 V16.6.0 (2021-06)

end for

where

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

- Qm 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 rvid the redundancy version number for this transmission ( rvid = 0, 1, 2 or 3), the rate matching output bit
sequence ek , k = 0,1,2,..., E − 1 , is generated as follows, where k 0 is given by Table 5.4.2.1-2 according to the value of
rvid and LDPC base graph:

k =0;

j = 0;

while k < E

if d (k + j ) mod N ≠< NULL >

0 cb

ek = d (k0 + j )mod Ncb ;

k = k +1 ;
end if

j = j + 1;

end while

Table 5.4.2.1-2: Starting position of different redundancy versions, k 0

k0
rvid
LDPC base graph 1 LDPC base graph 2
0 0 0
17 N cb  13 N cb 
1  Zc  Zc
 66 Z c   50 Z c 
 33 N cb   25 N cb 
2  Zc  Zc
 66 Z c   50 Z c 
 56 N cb   43 N cb 
3  Zc  Zc
 66 Z c   50 Z c 

5.4.2.2 Bit interleaving

The bit sequence e0 , e1 , e2 ,..., eE −1 is interleaved to bit sequence f 0 , f1 , f 2 ,..., f E −1 , according to the following, where the
value of Qm is the modulation order.

for j = 0 to E / Qm − 1

for i = 0 to Qm − 1

3GPP
Release 16156T 33 3GPP TS 38.212 V16.6.0 (2021-06)

f i + j⋅Qm = ei⋅E / Qm + j ;

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 , f1 , f 2 ,..., f E −1 , where E is the rate matching output sequence length. The bit sequence f 0 , f1 , 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 E r 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 g k 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

while r < C

Set j = 0

while j < E r

g k = 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].

3GPP
Release 16156T 34 3GPP TS 38.212 V16.6.0 (2021-06)

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 , a 3 ,..., a A−1 , and the parity bits by p 0 , p1 , p 2 , p 3 ,..., p L −1 , where A is the payload size and L is the
number of parity bits. The lowest order information bit a0 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 g CRC24A (D ) if A > 3824 ; and by setting L to 16 bits and using the generator
polynomial g CRC16 (D ) otherwise.

The bits after CRC attachment are denoted by b0 , b1 , b2 , b3 ,..., b B −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
6.1.4.1 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.

6.2.3 Code block segmentation and code block CRC attachment

The bits input to the code block segmentation are denoted by b0 , b1 , b2 , b3 ,..., b B −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.

The bits after code block segmentation are denoted by c r 0 , c r1 , c r 2 , c r 3 ,..., c r (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.

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 r1 , c r 2 , c r 3 ,..., c r (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 LDPC encoded according to
Clause 5.3.2.

After encoding the bits are denoted by d r 0 , d r1 , d r 2 , d r 3 ,..., d r ( N −1) , where the values of N r is given in Clause 5.3.2.
r

6.2.5 Rate matching

Coded bits for each code block, denoted as d r 0 , d r1 , d r 2 , d r 3 ,..., d r ( N −1) , are delivered to the rate match block, where
r
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.

After rate matching, the bits are denoted by f r 0 , f r1 , f r 2 , f r 3 ,..., f r ( E −1) , where E r is the number of rate matched bits for
r

code block number r.

3GPP
Release 16156T 35 3GPP TS 38.212 V16.6.0 (2021-06)

6.2.6 Code block concatenation

The input bit sequence for the code block concatenation block are the sequences f r 0 , f r1 , f r 2 , f r 3 ,..., f r ( E −1) , for
r

r = 0,..., C − 1 and where E r is the number of rate matched bits for the r -th code block.
Code block concatenation is performed according to Clause 5.5.

The bits after code block concatenation are denoted by g 0 , g1 , g 2 , g 3 ,..., g G −1 , where G is the total number of coded
bits for transmission.

6.2.7 Data and control multiplexing

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

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

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

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

Denote the coded bits for CG-UCI without HARQ-ACK, if any, as g CG−UCI
0 , g1CG−UCI ,
CG−UCI CG−UCI CG−UCI
g2 , g3 , … , g 𝐺𝐺𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 −1 .

Denote the multiplexed data and control coded bit sequence as g 0 , g1 , g 2 , g 3 ,..., g G −1 .

all − 1
PUSCH PUSCH
Denote l as the OFDM symbol index of the scheduled PUSCH, starting from 0 to N symb, , where N symb,all
is the
total number of OFDM symbols of the PUSCH, including all OFDM symbols used for DMRS.

Denote k as the subcarrier index of the scheduled PUSCH, starting from 0 to M scPUSCH − 1 , where M scPUSCH is expressed
as a number of subcarriers.

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

Denote M scUL-SCH ( l ) = Φ lUL-SCH as the number of elements in set Φ lUL-SCH . Denote Φ lUL-SCH ( j ) as the j -th element in
Φ lUL-SCH .

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

If frequency hopping is configured for the PUSCH,

- denote l (1) 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;

- denote l ( 2 ) 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.
(1)
- denote lCSI as the OFDM symbol index of the first OFDM symbol that does not carry DMRS in the first hop;

3GPP
Release 16156T 36 3GPP TS 38.212 V16.6.0 (2021-06)

(2)
- denote lCSI 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 ⋅ Qm ⋅ G ACK / (2 ⋅ N L ⋅ Qm ) and G ACK (2) = N L ⋅ Qm ⋅ G ACK / (2 ⋅ N L ⋅ Qm ) ;

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

- G CSI-part1 (1) = N L ⋅ Qm ⋅ G CSI-part1 / (2 ⋅ N L ⋅ Qm ) ;

- G CSI-part1 (2) = N L ⋅ Qm ⋅ G CSI-part1 / (2 ⋅ N L ⋅ Qm ) ;

- G CSI-part2 (1) = N L ⋅ Qm ⋅ G CSI-part2 / (2 ⋅ N L ⋅ Qm ) ; and

- G CSI-part2 (2) = N L ⋅ Qm ⋅ G CSI-part2 / (2 ⋅ N L ⋅ Qm ) ;

- if CG-UCI is present for transmission on the PUSCH with UL-SCH and without HARQ-ACK, let

- 𝐺𝐺 𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 (1) = 𝑁𝑁𝐿𝐿 ∙ 𝑄𝑄𝑚𝑚 ∙ ⌊𝐺𝐺 𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 ⁄(2 ∙ 𝑁𝑁𝐿𝐿 ∙ 𝑄𝑄𝑚𝑚 )⌋ and 𝐺𝐺 𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 (2) = 𝑁𝑁𝐿𝐿 ∙ 𝑄𝑄𝑚𝑚 ∙ ⌈𝐺𝐺 𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 ⁄(2 ∙ 𝑁𝑁𝐿𝐿 ∙ 𝑄𝑄𝑚𝑚 )⌉

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

- (
(1) min N L ⋅ Qm ⋅ G ACK / ( 2 ⋅ N L ⋅ Qm )  , M 3 ⋅ N L ⋅ Qm ;
G ACK= )
- G ACK (2) = G ACK − G ACK (1) ;

- G CSI-part1 (1) = M 1⋅ N L ⋅ Qm − G ACK (1) ; and

- G CSI-part1 (2) = G CSI-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

- (
(1) min N L ⋅ Qm ⋅ G ACK / ( 2 ⋅ N L ⋅ Qm )  , M 3 ⋅ N L ⋅ Qm ;
G ACK= )
- G ACK (2) = G ACK − G ACK (1) ;

- if 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, G CSI-part1 (1) = min (N L ⋅ Qm ⋅ G CSI-part1 / (2 ⋅ N L ⋅ Qm ) , M 1⋅N L ⋅ Qm − G ACK (1) );
otherwise, G CSI-part1= (
(1) min N L ⋅ Qm ⋅ G CSI-part1 / ( 2 ⋅ N L ⋅ Qm )  , M 1⋅ N L ⋅ Qm − Grvd
ACK
(1) )
- G CSI-part1 (2) = G CSI-part1 − G CSI-part1 (1) ;

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

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

- if CG-UCI is present for transmission on the PUSCH with UL-SCH and without HARQ-ACK, let

- 𝐺𝐺 𝐶𝐶𝐶𝐶𝐶𝐶−𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝1 (1) = min(𝑁𝑁𝐿𝐿 ∙ 𝑄𝑄𝑚𝑚 ∙ ⌊𝐺𝐺 𝐶𝐶𝐶𝐶𝐶𝐶−𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝1 ⁄(2 ∙ 𝑁𝑁𝐿𝐿 ∙ 𝑄𝑄𝑚𝑚 )⌋, 𝑀𝑀1 ∙ 𝑁𝑁𝐿𝐿 ∙ 𝑄𝑄𝑚𝑚 − 𝐺𝐺 𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 (1) );

- 𝐺𝐺 𝐶𝐶𝐶𝐶𝐶𝐶−𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝1 (2) = 𝐺𝐺 𝐶𝐶𝐶𝐶𝐶𝐶−𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝1 − 𝐺𝐺 𝐶𝐶𝐶𝐶𝐶𝐶−𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝1 (1);

- 𝐺𝐺 𝐶𝐶𝐶𝐶𝐶𝐶−𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝2 (1) = 𝑀𝑀1 ∙ 𝑁𝑁𝐿𝐿 ∙ 𝑄𝑄𝑚𝑚 − 𝐺𝐺 𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 (1) − 𝐺𝐺 𝐶𝐶𝐶𝐶𝐶𝐶−𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝1 (1); and

3GPP
Release 16156T 37 3GPP TS 38.212 V16.6.0 (2021-06)

- 𝐺𝐺 𝐶𝐶𝐶𝐶𝐶𝐶−𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝2 (2) = 𝑀𝑀2 ∙ 𝑁𝑁𝐿𝐿 ∙ 𝑄𝑄𝑚𝑚 − 𝐺𝐺 𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 (2) − 𝐺𝐺 𝐶𝐶𝐶𝐶𝐶𝐶−𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝1 (2);

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

-
=
G CSI-part1 (
(1) min N L ⋅ Qm ⋅ G CSI-part1 / ( 2 ⋅ N L ⋅ Qm )  , M 1⋅ N L ⋅ Qm − Grvd
ACK
(1) );
- G CSI-part1 (2) = G CSI-part1 − G CSI-part1 (1) ;

- G CSI-part2 (1) = M 1⋅ N L ⋅ Qm − G CSI-part1 (1) ; and

- G CSI-part2 (2) = M 2⋅ N L ⋅ Qm − G CSI-part1 (2) ;

- PUSCH
let N hop = 2 , and denote N symb,
PUSCH
hop (1)
PUSCH
, 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;

hop (1)−1
PUSCH
N symb,

- M1 = ∑ UCI
M SC (l ) ;
l =0

hop (1)+ N symb,hop ( 2 )−1

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

PUSCH
Nsymb,hop (1) −1
M3 = ∑ UCI
M SC (l )
- l =l (1) .

If frequency hopping is not configured for the PUSCH,

- denote l (1) as the OFDM symbol index of the first OFDM symbol after the first set of consecutive OFDM
symbol(s) carrying DMRS;
(1)
- denote lCSI 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
same PUSCH with UL-SCH, let G ACK (1) = G ACK ;

- if CSI is present for transmission on the PUSCH, let G CSI-part1 (1) = G CSI-part1 and G CSI-part2 (1) = G CSI-part2 ;

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

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

The multiplexed data and control coded bit sequence g 0 , g1 , g 2 , g 3 ,..., g G −1 is obtained according to the following:

Step 1:

Φ lUL-SCH for l = 0, 1, 2, ..., N symb,

Set Φ lUL-SCH = PUSCH
all − 1
;

Set M scUL-SCH ( l ) = Φ lUL-SCH for l = 0, 1, 2, ..., N symb,

PUSCH
all − 1
;

Φ lUCI for l = 0, 1, 2, ..., N symb,

Set Φ lUCI = PUSCH
all − 1
;

Set M scUCI ( l ) = Φ lUCI for l = 0, 1, 2, ..., N symb,

PUSCH
all − 1
;

3GPP
Release 16156T 38 3GPP TS 38.212 V16.6.0 (2021-06)

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
6.3.2.4.2.1, by setting OACK = 2 ;

denote Grvd
ACK
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 Grvd

ACK
(1) = N L ⋅ Qm ⋅ Grvd
ACK
/ ( 2 ⋅ N L ⋅ Qm )  and
ACK
Grvd (2) = N L ⋅ Qm ⋅ Grvd
ACK
/ ( 2 ⋅ N L ⋅ Qm )  ;

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

ACK
(1) = Grvd
ACK
;

denote Φlrvd as the set of reserved resource elements for potential HARQ-ACK transmission, in OFDM symbol l ,
for l = 0, 1, 2, ..., N symb,
PUSCH
all − 1
;

ACK
Set mcount (1) = 0 ;
ACK
Set mcount (2) = 0 ;

Φlrvd = ∅ for l = 0, 1, 2, ..., N symb,

PUSCH
all − 1
;

for i = 1 to N hop
PUSCH

l = l (i ) ;
ACK
while mcount (i ) < Grvd
ACK
(i )

if M scUCI ( l ) > 0

ACK
if Grvd (i ) − mcount
ACK
(i ) ≥ M scUCI ( l ) ⋅ N L ⋅ Qm

d = 1;
RE
mcount = M scUL-SCH ( l ) ;

end if
ACK
if Grvd (i ) − mcount
ACK
(i ) < M scUCI ( l ) ⋅ N L ⋅ Qm

=d  M scUCI ( l ) ⋅ N L ⋅ Qm ( Grvd
ACK
(i ) − mcount
ACK
(i ) )  ;

RE
mcount ( Grvd
= ACK
(i ) − mcount
ACK
(i ) ) / ( N L ⋅ Qm )  ;


end if

for j = 0 to
RE
mcount −1

Φ lrvd =Φ lrvd  {Φ lUL-SCH ( j ⋅ d )}

ACK
mcount (i ) = mcount
ACK
(i ) + N L ⋅ Qm ;

end for

end if

3GPP
Release 16156T 39 3GPP TS 38.212 V16.6.0 (2021-06)

l = l +1;
end while

end for

else

Φlrvd = ∅ for l = 0, 1, 2, ..., N symb,

PUSCH
all − 1
;

end if

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

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 mcount (1) = 0 ;
ACK
Set mcount (2) = 0 ;

all = 0
ACK
Set mcount, ;

for i = 1 to N hop
PUSCH

l = l (i ) ;
ACK
while mcount (i ) < G ACK (i )

if M scUCI ( l ) > 0

if G ACK (i ) − mcount
ACK
(i ) ≥ M scUCI ( l ) ⋅ N L ⋅ Qm

d = 1;
RE
mcount = M scUCI ( l ) ;

end if

if G ACK (i ) − mcount
ACK
(i ) < M scUCI ( l ) ⋅ N L ⋅ Qm

=d  M scUCI ( l ) ⋅ N L ⋅ Qm ( G ACK (i ) − mcount

ACK
(i ) )  ;

RE
mcount (
=  G ACK (i ) − mcount
ACK
)
(i ) / (N L ⋅ Qm ) ;

end if

for j = 0 to
RE
mcount −1

Φ lUCI ( j ⋅ d ) ;
k=

for v = 0 to N L ⋅ Qm − 1

3GPP
Release 16156T 40 3GPP TS 38.212 V16.6.0 (2021-06)

g l ,k ,v = g mACK
ACK ;
count, all

ACK
mcount,all = mcount,all
ACK
+ 1;

ACK
mcount (i ) = mcount
ACK
(i ) + 1 ;

end for

Φ lUCI
,tmp =
∅;

for j = 0 to
RE
mcount −1

Φ lUCI
,tmp =
Φ lUCI
,tmp  Φ l
UCI
( j⋅d);
end for

Φ lUCI =
Φ lUCI \ Φ lUCI
,tmp
;

Φ lUL-SCH =
Φ lUL-SCH \ Φ lUCI
,tmp
;

M scUCI ( l ) = Φ lUCI ;

M scUL-SCH ( l ) = Φ lUL-SCH ;

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,

𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 (1)
Set 𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐 = 0;
𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 (2)
Set 𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐 = 0;
𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈
Set 𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐,𝑎𝑎𝑎𝑎𝑎𝑎 = 0;
𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃
for 𝑖𝑖 = 1 to 𝑁𝑁ℎ𝑜𝑜𝑜𝑜

𝑙𝑙 = 𝑙𝑙 (𝑖𝑖) ;
𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 (𝑖𝑖)
while 𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐 < 𝐺𝐺 𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 (𝑖𝑖)
�𝑠𝑠𝑠𝑠
if 𝑀𝑀 𝑈𝑈𝑈𝑈𝑈𝑈 (𝑙𝑙)
>0
𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 (1)
if 𝐺𝐺 𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 (𝑖𝑖) − 𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐 �𝑠𝑠𝑠𝑠
≥ 𝑀𝑀 𝑈𝑈𝑈𝑈𝑈𝑈 (𝑙𝑙).
𝑁𝑁𝐿𝐿 . 𝑄𝑄𝑚𝑚

𝑑𝑑 = 1;
𝑅𝑅𝑅𝑅
𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐 �𝑠𝑠𝑠𝑠
= 𝑀𝑀 𝑈𝑈𝑈𝑈𝑈𝑈 (𝑙𝑙);

3GPP
Release 16156T 41 3GPP TS 38.212 V16.6.0 (2021-06)

end if
𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 (1)
if 𝐺𝐺 𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 (𝑖𝑖) − 𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐 �𝑠𝑠𝑠𝑠
< 𝑀𝑀 𝑈𝑈𝑈𝑈𝑈𝑈 (𝑙𝑙).
𝑁𝑁𝐿𝐿 . 𝑄𝑄𝑚𝑚
�𝑠𝑠𝑠𝑠
𝑑𝑑 = �𝑀𝑀 𝑈𝑈𝑈𝑈𝑈𝑈 (𝑙𝑙). 𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 (𝑖𝑖)�
𝑁𝑁𝐿𝐿 . 𝑄𝑄𝑚𝑚 ��𝐺𝐺 𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 (𝑖𝑖) − 𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐 �;
𝑅𝑅𝑅𝑅 𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 (𝑖𝑖)�⁄(𝑁𝑁
𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐 = ��𝐺𝐺 𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 (𝑖𝑖) − 𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐 𝐿𝐿 . 𝑄𝑄𝑚𝑚 )�;

end if
𝑅𝑅𝑅𝑅
for 𝑗𝑗 = 0 to 𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐 −1
� 𝑙𝑙𝑈𝑈𝑈𝑈𝑈𝑈 (𝑗𝑗. 𝑑𝑑);
𝑘𝑘 = Φ

for 𝑣𝑣 = 0 to 𝑁𝑁𝐿𝐿 . 𝑄𝑄𝑚𝑚 − 1

g� 𝑙𝑙,𝑘𝑘,𝑣𝑣 = g 𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈
𝑚𝑚𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈
;
𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐,𝑎𝑎𝑎𝑎𝑎𝑎

𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈
𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐,𝑎𝑎𝑎𝑎𝑎𝑎 = 𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐,𝑎𝑎𝑎𝑎𝑎𝑎 + 1;
𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 (𝑖𝑖) 𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 (𝑖𝑖)
𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐 = 𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐 + 1;

end for

end for
� 𝑙𝑙,𝑡𝑡𝑡𝑡𝑡𝑡
Φ 𝑈𝑈𝑈𝑈𝑈𝑈
= ∅;
𝑅𝑅𝑅𝑅
for 𝑗𝑗 = 0 to 𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐 −1
� 𝑙𝑙,𝑡𝑡𝑡𝑡𝑡𝑡
Φ 𝑈𝑈𝑈𝑈𝑈𝑈 � 𝑙𝑙,𝑡𝑡𝑡𝑡𝑡𝑡
=Φ 𝑈𝑈𝑈𝑈𝑈𝑈 � 𝑙𝑙𝑈𝑈𝑈𝑈𝑈𝑈 (𝑗𝑗. 𝑑𝑑);
∪Φ

end for

Φ � 𝑙𝑙𝑈𝑈𝑈𝑈𝑈𝑈 \Φ
� 𝑙𝑙𝑈𝑈𝑈𝑈𝑈𝑈 = Φ � 𝑙𝑙,𝑡𝑡𝑡𝑡𝑡𝑡
𝑈𝑈𝑈𝑈𝑈𝑈
;

Φ � 𝑙𝑙𝑈𝑈𝑈𝑈−𝑆𝑆𝑆𝑆𝑆𝑆 \Φ
� 𝑙𝑙𝑈𝑈𝑈𝑈−𝑆𝑆𝑆𝑆𝑆𝑆 = Φ � 𝑙𝑙,𝑡𝑡𝑡𝑡𝑡𝑡
𝑈𝑈𝑈𝑈𝑈𝑈
;

�𝑠𝑠𝑠𝑠
𝑀𝑀 𝑈𝑈𝑈𝑈𝑈𝑈 (𝑙𝑙) � 𝑙𝑙𝑈𝑈𝑈𝑈𝑈𝑈 �;
= �Φ

�𝑠𝑠𝑠𝑠
𝑀𝑀 𝑈𝑈𝑈𝑈−𝑆𝑆𝑆𝑆𝑆𝑆 (𝑙𝑙) � 𝑙𝑙𝑈𝑈𝑈𝑈−𝑆𝑆𝑆𝑆𝑆𝑆 �;
= �Φ

end if

𝑙𝑙 = 𝑙𝑙 + 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 mcount (2) = 0 ;
CSI-part1
Set mcount,all = 0;

3GPP
Release 16156T 42 3GPP TS 38.212 V16.6.0 (2021-06)

for i = 1 to N hop
PUSCH

l = lCSI
(i)
;

while M scUCI ( l ) − M sc,

Φ
rvd ( l ) ≤ 0

l = l +1;
end while
CSI-part1
while mcount (i ) < G CSI-part1 (i )

if M scUCI ( l ) − M sc,
Φ
rvd ( l ) > 0

if G CSI-part1 (i ) − mcount
CSI-part1
(
(i ) ≥ M scUCI ( l ) − M sc,
Φ
)
rvd ( l ) ⋅ N L ⋅ Qm

d = 1;

=RE
mcount M scUCI ( l ) − M sc,
Φ
rvd ( l )
;

end if

if G CSI-part1 (i ) − mcount
CSI-part1
(
(i ) < M scUCI ( l ) − M sc,
Φ
)
rvd ( l ) ⋅ N L ⋅ Qm

=
 (
d  M scUCI ( l ) − M sc,
Φ
)
rvd ( l ) ⋅ N L ⋅ Qm (G CSI-part1
(i ) − mcount
CSI-part1
(i ) )  ;


RE
mcount (
=  G CSI-part1 (i ) − mcount
CSI - part1
)
(i ) / ( N L ⋅ Qm ) ;

end if

Φ ltemp =
Φ lUCI \ Φ lrvd ;

for j = 0 to
RE
mcount −1

Φ ltemp ( j ⋅ d ) ;
k=

for v = 0 to N L ⋅ Qm − 1

g l ,k ,v = g mCSICSI--part1
part1 ;
count, all

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

CSI-part1
mcount (i ) = mcount
CSI-part1
(i ) + 1 ;

end for

Φ lUCI
,tmp =
∅;

for j = 0 to
RE
mcount −1

Φ lUCI
,tmp =
Φ lUCI
,tmp  Φ l
temp
( j⋅d);

3GPP
Release 16156T 43 3GPP TS 38.212 V16.6.0 (2021-06)

end for

Φ lUCI =
Φ lUCI \ Φ lUCI
,tmp
;

Φ lUL-SCH =
Φ lUL-SCH \ Φ lUCI
,tmp
;

M scUCI ( l ) = Φ lUCI ;

M scUL-SCH ( l ) = Φ lUL-SCH ;

end if

l = l +1;
end while

end for

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

all = 0
CSI-part2
Set mcount, ;

for i = 1 to N hop
PUSCH

l = lCSI
(i)
;

while M scUCI ( l ) ≤ 0

l = l +1;
end while
CSI-part2
while mcount (i ) < G CSI-part2 (i )

if M scUCI ( l ) > 0

if G CSI-part2 (i ) − mcount
CSI-part2
(i ) ≥ M scUCI ( l ) ⋅ N L ⋅ Qm

d = 1;
RE
mcount = M scUCI ( l ) ;

end if

if G CSI-part2 (i ) − mcount
CSI-part2
(i ) < M scUCI ( l ) ⋅ N L ⋅ Qm

=d  M scUCI ( l ) ⋅ N L ⋅ Qm ( G CSI-part2 (i ) − mcount

CSI-part2
(i ) )  ;

RE
mcount (
=  G CSI-part2 (i ) − mcount
CSI - part2
)
(i ) / ( N L ⋅ Qm ) ;

end if

3GPP
Release 16156T 44 3GPP TS 38.212 V16.6.0 (2021-06)

for j = 0 to
RE
mcount −1

Φ lUCI ( j ⋅ d ) ;
k=

for v = 0 to N L ⋅ Qm − 1

g l ,k ,v = g mCSICSI--part2
part2 ;
count, all

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

CSI-part2
mcount (i ) = mcount
CSI-part2
(i ) + 1 ;

end for

Φ lUCI
,tmp =
∅;

for j = 0 to
RE
mcount −1

Φ lUCI
,tmp =
Φ lUCI
,tmp  Φ l
UCI
( j⋅d);
end for

Φ lUCI =
Φ lUCI \ Φ lUCI
,tmp
;

Φ lUL-SCH =
Φ lUL-SCH \ Φ lUCI
,tmp
;

M scUCI ( l ) = Φ lUCI ;

M scUL-SCH ( l ) = Φ lUL-SCH ;

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 mcount = 0;

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

if M scUL-SCH ( l ) > 0

for j = 0 to M scUL-SCH ( l ) − 1

k = Φ lUL-SCH ( j ) ;

3GPP
Release 16156T 45 3GPP TS 38.212 V16.6.0 (2021-06)

for v = 0 to N L ⋅ Qm − 1

g l ,k ,v = g mULUL−−SCH
SCH
;
count

UL−SCH UL−SCH
mcount = mcount +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 mcount ( 2) = 0 ;

all = 0
ACK
Set mcount, ;

for i = 1 to N hop
PUSCH

l = l (i ) ;
ACK
while mcount (i ) < G ACK (i )

rvd ( l ) > 0
Φ
if M sc,

rvd ( l ) ⋅ N L ⋅ Qm
Φ
if G ACK (i ) − mcount
ACK
(i ) ≥ M sc,

d = 1;

rvd ( l )
Φ
RE
mcount = M sc, ;

end if

rvd ( l ) ⋅ N L ⋅ Qm
Φ
if G ACK (i ) − mcount
ACK
(i ) < M sc,

=d  M sc,Φ rvd ( l ) ⋅ N L ⋅ Qm ( G ACK (i ) − mcount

ACK
(i ) )  ;

RE
mcount (
=  G ACK (i ) − mcount
ACK
)
(i ) / (N L ⋅ Qm ) ;

end if

for j = 0 to
RE
mcount −1

Φ lrvd ( j ⋅ d ) ;
k=

3GPP
Release 16156T 46 3GPP TS 38.212 V16.6.0 (2021-06)

for v = 0 to N L ⋅ Qm − 1

g l ,k ,v = g mACK
ACK ;
count, all

ACK
mcount,all = mcount,all
ACK
+ 1;

ACK
mcount (i ) = mcount
ACK
(i ) + 1 ;

end for

end if

l = l +1;
end while

end for

end if

Step 6:

Set t = 0 ;

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

for j = 0 to M scUL-SCH ( l ) − 1

k = Φ lUL-SCH ( j ) ;

for v = 0 to N L ⋅ Qm − 1

g t = g l , k ,v ;

t = t +1;
end for

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.

6.3.1.1 UCI bit sequence generation

6.3.1.1.1 HARQ-ACK/SR only
If only HARQ-ACK bits are transmitted on a PUCCH, the UCI bit sequence a 0 , a1 , a 2 , a 3 ,..., a A−1 is determined by
setting ai = o~i ACK for i = 0, 1, ..., O ACK − 1 and A = O ACK , where the HARQ-ACK bit sequence
o~ ACK , o~ ACK ,..., o~ ACK
0 1 is given by Clause 9.1 of [5, TS38.213].
O ACK −1

3GPP
Release 16156T 47 3GPP TS 38.212 V16.6.0 (2021-06)

If only HARQ-ACK and SR bits are transmitted on a PUCCH, the UCI bit sequence a 0 , a1 , a 2 , a 3 ,..., a A−1 is
𝑆𝑆𝑆𝑆
determined by setting ai = o~i ACK for i = 0, 1, ..., O ACK − 1 , 𝑎𝑎𝑖𝑖 = 𝑜𝑜
�𝑖𝑖−𝑂𝑂𝐴𝐴𝐴𝐴𝐴𝐴 for i = O ACK , O ACK + 1,..., O ACK + O SR − 1 ,
and A = O ACK + O SR , where the HARQ-ACK bit sequence o~ ACK , o~ ACK ,..., o~ ACK
0 1 is given by Clause 9.1 of [5, TS
O ACK −1

38.213], and the SR bit sequence o~ , o~ ,..., o~

0
SR
1
SR SR
OSR −1
is given by Clause 9.2.5.1 of [5, TS 38.213].

6.3.1.1.2 CSI only

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 5.2.2.2.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
6.3.1.1.2-1, where the values of (N1, N 2 ) and (O1 ,O2 ) are given by Clause 5.2.2.2.1 in [6, TS 38.214].

Table 6.3.1.1.2-1: PMI of codebookType=typeI-SinglePanel

Information field X 2 for wideband

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

( i1,1 , i1,2 ) i2
i1,3
codebookMode=1 codebookMode=2 codebookMode=1 codebookMode=2

 N1O1 
(  log 2
2 
,
Rank = 1 with >2 (  log 2 N1O1  , 
CSI-RS ports, N/A 2 4
N2 > 1 log 2 N 2O2  )  N 2O2 
log 2 2  )

Rank = 1 with >2 (  log 2 N1O1  ,

CSI-RS ports, ( log 2  N1O1  , 0)
  N/A 2 4
N2 = 1 log 2 N 2O2  )   2 

Rank=2 with 4 (  log 2 N1O1  ,

CSI-RS ports, ( log 2  N1O1  , 0)
  1 1 3
N2 = 1 log 2 N 2O2  )   2 

 N1O1 
( log 2
Rank=2 with >4 (  log 2 N1O1  ,   2 
,
CSI-RS ports, 2 1 3
N2 > 1 log 2 N 2O2  )  N 2O2 
log 2 2  )

Rank=2 with >4 (  log 2 N1O1  ,

CSI-RS ports, ( log 2  N1O1  , 0)
  2 1 3
N2 = 1 log 2 N 2O2  )   2 

Rank=3 or 4,
with 4 CSI-RS (  log 2 N1O1  ,  log 2 N 2O2  ) 0 1
ports

Rank=3 or 4,
with 8 or 12 CSI- (  log 2 N1O1  ,  log 2 N 2O2  ) 2 1
RS ports

3GPP
Release 16156T 48 3GPP TS 38.212 V16.6.0 (2021-06)

Rank=3 or 4 ,  N1O1 
(  log 2 ,  log 2 N 2O2  )
2 
with >=16 CSI- 2 1
RS ports 

Rank=5 or 6 (  log 2 N1O1  ,  log 2 N 2O2  ) N/A 1

Rank=7 or 8,  N1O1 
(  log 2 ,  log 2 N 2O2  )
2 
=
N1 4,=
N2 1 N/A 1


Rank=7 or 8,  N 2O2 
(  log 2 N1O1  ,  log 2
2 
) N/A 1
N1 > 2, N 2 =
2

Rank=7 or 8,
with
N1 > 4, N 2 =
1
or (  log 2 N1O1  ,  log 2 N 2O2  ) N/A 1
=
N1 2,= N 2 2 or
N1 > 2, N 2 > 2

The bitwidth for PMI of codebookType= typeI-MultiPanel is provided in Tables 6.3.1.1.2-2, where the values of
( N g , N1 , N2 ) and (O1,O2 ) are given by Clause 5.2.2.2.2 in [6, TS 38.214].

Table 6.3.1.1.2-2: PMI of codebookType= typeI-MultiPanel

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

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

Rank=1 with Ng = 2 (  log 2 N1O1  ,

N/A 2 N/A N/A 2 N/A N/A N/A
codebookMode=1 log 2 N 2O2  )

Rank=1 with Ng = 4 (  log 2 N1O1  ,

N/A 2 2 2 2 N/A N/A N/A
codebookMode=1 log 2 N 2O2  )

Rank=2 with Ng = 2 , (  log 2 N1O1  ,

N1 N 2 = 2 1 2 N/A N/A 1 N/A N/A N/A
log 2 N 2O2  )
codebookMode=1

Rank=3 or 4 with Ng = 2 , (  log 2 N1O1  ,

N1 N 2 = 2 0 2 N/A N/A 1 N/A N/A N/A
log 2 N 2O2  )
codebookMode=1

Rank=2 or 3 or 4 with Ng = 2 , (  log 2 N1O1  ,

N1 N 2 > 2 2 2 N/A N/A 1 N/A N/A N/A
log 2 N 2O2  )
codebookMode=1

3GPP
Release 16156T 49 3GPP TS 38.212 V16.6.0 (2021-06)

Rank=2 with Ng = 4 , (  log 2 N1O1  ,

N1 N 2 = 2 1 2 2 2 1 N/A N/A N/A
log 2 N 2O2  )
codebookMode=1

Rank=3 or 4 with Ng = 4 , (  log 2 N1O1  ,

N1 N 2 = 2 0 2 2 2 1 N/A N/A N/A
log 2 N 2O2  )
codebookMode=1

Rank=2 or 3 or 4 with Ng = 4 , (  log 2 N1O1  ,

N1 N 2 > 2 2 2 2 2 1 N/A N/A N/A
log 2 N 2O2  )
codebookMode=1

Rank=1 with Ng = 2 (  log 2 N1O1  ,

N/A 2 2 N/A N/A 2 1 1
codebookMode=2 log 2 N 2O2  )

Rank=2 with Ng = 2 , (  log 2 N1O1  ,

N1 N 2 = 2 1 2 2 N/A N/A 1 1 1
log 2 N 2O2  )
codebookMode=2

Rank=3 or 4 with Ng = 2 , (  log 2 N1O1  ,

N1 N 2 = 2 0 2 2 N/A N/A 1 1 1
log 2 N 2O2  )
codebookMode=2

Rank=2 or 3 or 4 with Ng = 2 , (  log 2 N1O1  ,

N1 N 2 > 2 2 2 2 N/A N/A 1 1 1
log 2 N 2O2  )
codebookMode=2

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

The bitwidth for RI/LI/CQI/CRI of codebookType=typeI-SinglePanel is provided in Tables 6.3.1.1.2-3.

Table 6.3.1.1.2-3: RI, LI, CQI, and CRI of codebookType=typeI-SinglePanel

Bitwidth
Field 2 antenna 4 antenna >4 antenna ports
1 antenna port
ports ports Rank1~4 Rank5~8
Rank Indicator 0 min (1, log 2 nRI ) min (2, log 2 nRI )  2 RI 
log n log 2 nRI 
Layer Indicator 0 log 2 υ  min ( 2, log 2 υ  ) min ( 2, log 2 υ  ) min ( 2, log 2 υ  )
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 sCSI−RS ) log 2 (K sCSI−RS ) log 2 (K sCSI−RS ) log 2 (K sCSI−RS ) log 2 (K sCSI−RS )
nRI in Table 6.3.1.1.2-3 is the number of allowed rank indicator values according to Clause 5.2.2.2.1 [6, TS 38.214].
υ is the value of the rank. The value of K sCSI−RS is the number of CSI-RS resources in the corresponding resource

3GPP
Release 16156T 50 3GPP TS 38.212 V16.6.0 (2021-06)

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.

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

Table 6.3.1.1.2-4: RI, LI, CQI, and CRI of codebookType=typeI-MultiPanel

Field Bitwidth

Rank Indicator min (2, log 2 nRI )

Layer Indicator min ( 2, log 2 υ  )
Wide-band CQI 4
Subband differential CQI 2
CRI log 2 (K sCSI−RS )
where nRI is the number of allowed rank indicator values according to Clause 5.2.2.2.2 [6, TS 38.214], υ is the value
of the rank, and K sCSI−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.

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

6.3.1.1.2-5.

Table 6.3.1.1.2-5: RI, LI, and CQI of codebookType=typeII or typeII-PortSelection

Field Bitwidth

Rank Indicator min (1, log 2 nRI )

Layer Indicator min ( 2, log 2 υ  )
Wide-band CQI 4
Subband differential CQI 2
Indicator of the number of non-zero
wideband amplitude coefficients M l for layer l log 2 (2 L − 1)

where nRI is the number of allowed rank indicator values according to Clauses 5.2.2.2.3 and 5.2.2.2.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, and differential RSRP are provided in Table 6.3.1.1.2-6.

Table 6.3.1.1.2-6: CRI, SSBRI, and RSRP

Field Bitwidth

CRI log 2 (K sCSI−RS )

SSBRI log 2 (K sSSB )
RSRP 7
Differential RSRP 4
where K sCSI−RS is the number of CSI-RS resources in the corresponding resource set, and K sSSB is the configured
number of SS/PBCH blocks in the corresponding resource set for reporting 'ssb-Index-RSRP'.

3GPP
Release 16156T 51 3GPP TS 38.212 V16.6.0 (2021-06)

The bitwidth for CRI, SSBRI, SINR, and differential SINR are provided in Table 6.3.1.1.2-6A.

Table 6.3.1.1.2-6A: CRI, SSBRI, and SINR

Field Bitwidth

CRI ⌈log 2 (𝐾𝐾𝑠𝑠𝐶𝐶𝐶𝐶𝐶𝐶−𝑅𝑅𝑅𝑅 )⌉

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

Table 6.3.1.1.2-7: Mapping order of CSI fields of one CSI report, pmi-FormatIndicator=widebandPMI
and cqi-FormatIndicator=widebandCQI

CSI report
CSI fields
number
CRI as in Tables 6.3.1.1.2-3/4, if reported
Rank Indicator as in Tables 6.3.1.1.2-3/4, if reported
Layer Indicator as in Tables 6.3.1.1.2-3/4, if reported
Zero padding bits OP , if needed
CSI report #n PMI wideband information fields X 1 , from left to right as in Tables 6.3.1.1.2-1/2, if reported
PMI wideband information fields X 2 , from left to right as in Tables 6.3.1.1.2-1/2, or
codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214], if reported
Wideband CQI for the first TB as in Tables 6.3.1.1.2-3/4, if reported
Wideband CQI for the second TB as in Tables 6.3.1.1.2-3/4, if reported

The number of zero padding bits OP in Table 6.3.1.1.2-7 is 0 for 1 CSI-RS port and OP = N max − N reported for more
than 1 CSI-RS port, where

- N max = max B(r ) and S

r∈S Rank Rank 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 6.3.1.1.2-1/2; otherwise, N PMI,i1 (r ) = 0 ;

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

- if CQI is reported, N CQI (r ) is obtained according to Tables 6.3.1.1.2-3/4; otherwise, N CQI (r ) = 0 ;

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

3GPP
Release 16156T 52 3GPP TS 38.212 V16.6.0 (2021-06)

Table 6.3.1.1.2-8: Mapping order of CSI fields of one report for CRI/RSRP or SSBRI/RSRP reporting
CSI report
CSI fields
number
CRI or SSBRI #1 as in Table 6.3.1.1.2-6, if reported
CRI or SSBRI #2 as in Table 6.3.1.1.2-6, if reported
CRI or SSBRI #3 as in Table 6.3.1.1.2-6, if reported
CRI or SSBRI #4 as in Table 6.3.1.1.2-6, if reported
CSI report #n
RSRP #1 as in Table 6.3.1.1.2-6, if reported
Differential RSRP #2 as in Table 6.3.1.1.2-6, if reported
Differential RSRP #3 as in Table 6.3.1.1.2-6, if reported
Differential RSRP #4 as in Table 6.3.1.1.2-6, if reported

Table 6.3.1.1.2-8A: Mapping order of CSI fields of one report for CRI/SINR or SSBRI/SINR reporting

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

Table 6.3.1.1.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 6.3.1.1.2-3/4, if reported

Rank Indicator as in Tables 6.3.1.1.2-3/4/5, if reported
Wideband CQI for the first TB as in Tables 6.3.1.1.2-3/4/5, if reported
Subband differential CQI for the first TB with increasing order of subband number as in
Tables 6.3.1.1.2-3/4/5, if reported
CSI report #n
CSI part 1 Indicator of the number of non-zero wideband amplitude coefficients 𝑀𝑀0 for layer 0 as in
Table 6.3.1.1.2-5, if reported
Indicator of the number of non-zero wideband amplitude coefficients 𝑀𝑀1 for layer 1 as in
Table 6.3.1.1.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 5.2.2.2.3
and 5.2.2.2.4 [6, TS 38.214] 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 6.3.1.1.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 6.3.1.1.2-3/4/5, if present and reported
Layer Indicator as in Tables 6.3.1.1.2-3/4/5, if reported
CSI report #n PMI wideband information fields X 1 , from left to right as in Tables 6.3.1.1.2-1/2, if reported
CSI part 2
wideband PMI wideband information fields X 2 , from left to right as in Tables 6.3.1.1.2-1/2, or
codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214], if pmi-
FormatIndicator= widebandPMI and if reported

3GPP
Release 16156T 53 3GPP TS 38.212 V16.6.0 (2021-06)

Table 6.3.1.1.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 6.3.1.1.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 6.3.1.1.2-1/2, or codebook index for 2 antenna ports
according to Clause 5.2.2.2.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 6.3.1.1.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 6.3.1.1.2-1/2, or codebook index for 2 antenna ports
according to Clause 5.2.2.2.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.

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 6.3.1.1.2-12, are mapped to the UCI bit sequence a 0 , a1 , a 2 , a 3 ,..., a A−1 starting
with a0 . 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 a0 .

Table 6.3.1.1.2-12: Mapping order of CSI reports to UCI bit sequence a 0 , a1 , a 2 , a 3 ,..., a A−1 , without two-
part CSI report(s)

UCI bit sequence CSI report number

a0 CSI report #1
as in Table 6.3.1.1.2-7/8
a1
CSI report #2
a2 as in Table 6.3.1.1.2-7/8

a3 …

CSI report #n
a A −1 as in Table 6.3.1.1.2-7/8

If at least one of the CSI reports for transmission on a PUCCH is of two parts, two UCI bit sequences are generated,
a0(1) , a1(1) , a2(1) , a3(1) ,..., a A(1()1) −1 and a0( 2 ) , a1( 2 ) , a2( 2 ) , a3( 2 ) ,..., a A( 2( 2) ) −1 . The CSI fields of all CSI reports, in the order from upper
part to lower part in Table 6.3.1.1.2-13, are mapped to the UCI bit sequence a0(1) , a1(1) , a2(1) , a3(1) ,..., a A(1()1) −1 starting with
a0(1) . 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 a0(1) . The CSI fields of all CSI reports, in the order from upper part to lower
part in Table 6.3.1.1.2-14, are mapped to the UCI bit sequence a0( 2 ) , a1( 2 ) , a2( 2 ) , a3( 2 ) ,..., a A( 2( 2) ) −1 starting with a0( 2 ) . 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 a0( 2 ) . If the length of UCI bit sequence a0( 2 ) , a1( 2 ) , a2( 2 ) , a3( 2 ) ,..., a A( 2( 2) ) −1 is less than 3 bits,
zeros shall be appended to the UCI bit sequence until its length equals 3.

3GPP
Release 16156T 54 3GPP TS 38.212 V16.6.0 (2021-06)

Table 6.3.1.1.2-13: Mapping order of CSI reports to UCI bit sequence a0(1) , a1(1) , a2(1) , a3(1) ,..., a A(1()1) −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 (1) CSI report #1, CSI part 1, if CSI report #1 is of two parts,
0
as in Table 6.3.1.1.2-7/8/9
a1(1) 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,
a2(1) as in Table 6.3.1.1.2-7/8/9
a3(1)
…

CSI report #n if CSI report #n is not of two parts, or
a A(1()1) −1 CSI report #n, CSI part 1, if CSI report #n is of two parts,
as in Table 6.3.1.1.2-7/8/9

where CSI report #1, CSI report #2, …, CSI report #n in Table 6.3.1.1.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].

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

UCI bit sequence CSI report number

CSI report #1, CSI part 2 wideband, as in Table 6.3.1.1.2-10

if CSI part 2 exists for CSI report #1
CSI report #2, CSI part 2 wideband, as in Table 6.3.1.1.2-10
if CSI part 2 exists for CSI report #2

a0( 2 ) …
( 2)
a 1
CSI report #n, CSI part 2 wideband, as in Table 6.3.1.1.2-10
a2( 2 ) if CSI part 2 exists for CSI report #n
a3( 2 ) CSI report #1, CSI part 2 subband, as in Table 6.3.1.1.2-11
if CSI part 2 exists for CSI report #1

a A( 2( 2) ) −1 CSI report #2, CSI part 2 subband, as in Table 6.3.1.1.2-11
if CSI part 2 exists for CSI report #2

CSI report #n, CSI part 2 subband, as in Table 6.3.1.1.2-11

if CSI part 2 exists for CSI report #n

where CSI report #1, CSI report #2, …, CSI report #n in Table 6.3.1.1.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].

6.3.1.1.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 , a 3 ,..., a A−1 is
generated according to the following, where A = O ACK + OSR + O CSI :

- if there is HARQ-ACK for transmission on the PUCCH, the HARQ-ACK bits are mapped to the UCI bit
sequence a0 , a1 , a2 , a3 ,..., a ACK , where ai = o~i ACK for i = 0, 1, ..., O ACK − 1 , the HARQ-ACK bit sequence
O −1

o~ ACK , o~ ACK ,..., o~ ACK

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

3GPP
Release 16156T 55 3GPP TS 38.212 V16.6.0 (2021-06)

𝑆𝑆𝑆𝑆
- �𝑖𝑖−𝑂𝑂𝐴𝐴𝐴𝐴𝐴𝐴 for i = O ACK , O ACK + 1,..., O ACK + O SR − 1 ,
if there is SR for transmission on the PUCCH, set 𝑎𝑎𝑖𝑖 = 𝑜𝑜
where the SR bit sequence o~0SR , o~1SR ,..., o~OSRSR −1 is given by Clause 9.2.5.1 of [5, TS 38.213]; if there is no SR
for transmission on the PUCCH, set O SR
= 0;
- the CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.1.1.2-12, are mapped to
the UCI bit sequence aO ACK + O SR , aO ACK + O SR +1 ,..., aO ACK + O SR + O CSI −1 starting with aO ACK + O SR , where O CSI is the
number of CSI bits.

- if there is HARQ-ACK for transmission on the PUCCH, the HARQ-ACK bits are mapped to the UCI bit
sequence a0(1) , a1(1) , a2(1) , a3(1) ,..., aO(1ACK
)
−1
, where ai(1) = o~i ACK for i = 0, 1, ..., O ACK − 1 , the HARQ-ACK bit
sequence o~ ACK , o~ ACK ,..., o~ ACK
0 1 O ACK −1
is given by Clause 9.1 of [5, TS38.213], and O ACK is number of HARQ-ACK
bits; if there is no HARQ-ACK for transmission on the PUCCH, set O ACK = 0 ;

𝑆𝑆𝑆𝑆
- �𝑖𝑖−𝑂𝑂𝐴𝐴𝐴𝐴𝐴𝐴 for i = O ACK , O ACK + 1,..., O ACK + O SR − 1 ,
if there is SR for transmission on the PUCCH, set 𝑎𝑎𝑖𝑖 = 𝑜𝑜
where the SR bit sequence o~0SR , o~1SR ,..., o~OSRSR −1 is given by Clause 9.2.5.1 of [5, TS 38.213]; if there is no SR
for transmission on the PUCCH, set O SR
= 0;
- the CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.1.1.2-13, are mapped to
the UCI bit sequence aO(1ACK
)
+OSR
, aO(1ACK
)
+OSR +1
,..., aO(1ACK
)
+OSR +O CSI - part1 −1
starting with aO(1ACK
)
+OSR
, where O CSI-part1 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 6.3.1.1.2-14, are mapped to
the UCI bit sequence a0( 2 ) , a1( 2 ) , a2( 2 ) , a3( 2 ) ,..., a A( 2( 2) ) −1 starting with a0( 2 ) , where O CSI-part2 is the number of CSI bits
in CSI part 2 of all CSI reports. If the length of UCI bit sequence a0( 2 ) , a1( 2 ) , a2( 2 ) , a3( 2 ) ,..., a A( 2( 2) ) −1 is less than 3 bits,
zeros shall be appended to the UCI bit sequence until its length equals 3.

6.3.1.2 Code block segmentation and CRC attachment

The UCI bit sequence from clause 6.3.1.1 is denoted by a 0 , a1 , a 2 , a 3 ,..., a A−1 , where A is the payload size. The
procedure in 6.3.1.2.1 applies for A ≥ 12 and the procedure in Clause 6.3.1.2.2 applies for A ≤ 11 .

6.3.1.2.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 A ≥ 1013 , I seg = 1 ; otherwise I seg = 0 , where E is the rate matching output
sequence length as given in Clause 6.3.1.4.1.

If 12 ≤ A ≤ 19 , the parity bits p r 0 , p r1 , p r 2 ,..., p r (L −1) in Clause 5.2.1 are computed by setting L to 6 bits and using
the generator polynomial g CRC6 (D ) in Clause 5.1, resulting in the sequence c r 0 , c r1 , c r 2 , c r 3 ,..., c r (K r −1) where r is
the code block number and K r is the number of bits for code block number r.

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

6.3.1.2.2 UCI encoded by channel coding of small block lengths

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

3GPP
Release 16156T 56 3GPP TS 38.212 V16.6.0 (2021-06)

The output bit sequence is denoted by c0 , c1 , c 2 , c3 ,..., c K −1 , where ci = ai for i = 0, 1, ..., A − 1 and K = A .

6.3.1.3 Channel coding of UCI

6.3.1.3.1 UCI encoded by Polar code
Information bits are delivered to the channel coding block. They are denoted by c r 0 , c r1 , c r 2 , c r 3 ,..., c r (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 nmax = 10 ,
I IL = 0 , nPC = 3 , nPC = 1 if E r − K r + 3 > 192 and nPC = 0 if Er − K r + 3 ≤ 192 , where Er is the rate
wm wm

matching output sequence length as given in Clause 6.3.1.4.1.

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

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

number r.
6.3.1.3.2 UCI encoded by channel coding of small block lengths
Information bits are delivered to the channel coding block. They are denoted by c0 , c1 , c 2 , c3 ,..., 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 , d 3 ,..., d N −1 , where N is the number of coded bits.

6.3.1.4 Rate matching

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

Table 6.3.1.4-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 ∙ 𝑁𝑁symb,UCI ∙ 𝑁𝑁PRB /𝑁𝑁SF N/A
PUCCH,3 PUCCH,3 PUCCH,3 PUCCH,3 PUCCH,3 PUCCH,3
PUCCH format 3 24 ∙ 𝑁𝑁symb,UCI ∙ 𝑁𝑁PRB /𝑁𝑁SF 12 ∙ 𝑁𝑁symb,UCI ∙ 𝑁𝑁PRB /𝑁𝑁SF
PUCCH format 4 24 ⋅ N symb,
PUCCH, 4 PUCCH, 4
UCI / N SF 12 ⋅ N symb,
PUCCH, 4 PUCCH, 4
UCI / N SF

6.3.1.4.1 UCI encoded by Polar code

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

3GPP
Release 16156T 57 3GPP TS 38.212 V16.6.0 (2021-06)

Table 6.3.1.4.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 = E tot
HARQ-ACK, SR HARQ-ACK, SR E UCI = E tot
CSI E UCI = E tot
CSI
(CSI not of two parts)
HARQ-ACK, CSI E UCI = E tot
HARQ-ACK, CSI
(CSI not of two parts)
HARQ-ACK, SR, CSI HARQ-ACK, SR, E UCI = E tot
(CSI not of two parts) CSI

CSI CSI part 1 ( (

E UCI = min E tot ,  O CSI-part1 + L / RUCI
max
/ Qm  ⋅ Qm ) )
(CSI of two parts) CSI part 2 ) ( ) (
E UCI = E tot − min E tot ,  O CSI-part1 + L / RUCI
max
/ Qm  ⋅ Qm
E = min (E , (O + L )/ R / Q  ⋅ Q )
HARQ-ACK, CSI
HARQ-ACK, CSI part 1 UCI +O tot
ACK CSI - part1 max
UCI m m

E = E − min (E , (O + L )/ R / Q  ⋅ Q )
(CSI of two parts)
CSI part 2 UCI tot +O tot
ACK CSI - part1 max
UCI m m

E = min (E , (O + L )/ R / Q  ⋅ Q )
HARQ-ACK, SR,
HARQ-ACK, SR, CSI CSI part 1 UCI +O +O
tot
ACK SR CSI - part1 max
UCI m m

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

Rate matching is performed according to Clause 5.4.1 by setting I BIL = 1 and the rate matching output sequence length
to E r = E UCI / C UCI  , where C UCI is the number of code blocks for UCI determined according to Clause 6.3.1.2.1
and the value of E UCI is given by Table 6.3.1.4.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;

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

- O CSI-part2 is the number of bits for CSI part 2 for transmission on the current PUCCH;
- if A ≥ 360 , L = 11 ; otherwise, L is the number of CRC bits determined according to clause 6.3.1.2.1, where
A equals O CSI-part1 for "CSI (CSI of two parts)", equals O ACK + O CSI-part1 for "HARQ-ACK, CSI (CSI of two
parts)", and equals O ACK + OSR + O CSI-part1 for "HARQ-ACK, SR, CSI (CSI of two parts)" respectively in Table
6.3.1.4.1-1;;
max
- RUCI is the configured maximum PUCCH coding rate;

- E tot is given by Table 6.3.1.4-1.

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

matching output sequence in code block number r .

6.3.1.4.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 6.3.1.4.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 = E UCI .

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

3GPP
Release 16156T 58 3GPP TS 38.212 V16.6.0 (2021-06)

6.3.1.5 Code block concatenation

The input bit sequence for the code block concatenation block are the sequences f r 0 , f r1 , f r 2 ,..., f r ( E −1) , for
r

r = 0,..., C − 1 and where E r is the number of rate matched bits for the r -th code block.
Code block concatenation is performed according to Clause 5.5.

The bits after code block concatenation are denoted by g 0 , g1 , g 2 , g 3 ,..., g G '−1 , where G ' = E UCI / C UCI  ⋅ C UCI with the
values of E UCI and C UCI given in Clause 6.3.1.4.1. Let G be the total number of coded bits for transmission and
G = G '+ mod(E UCI , C UCI ) . Set g i = 0 for i = G ' , G '+1,..., G − 1 .

6.3.1.6 Multiplexing of coded UCI bits to PUCCH

If CSI of two parts are transmitted on a PUCCH, the coded bits corresponding to UCI bit sequence
a0(1) , a1(1) , a2(1) , a3(1) ,..., a A(1()1) −1 is denoted by g 0(1) , g1(1) , g 2(1) , g 3(1) ,..., g G(1()1) −1 and the coded bits corresponding to UCI bit
sequence a0( 2 ) , a1( 2 ) , a2( 2 ) , a3( 2 ) ,..., a A( 2( 2) ) −1 is denoted by g 0( 2 ) , g1( 2 ) , g 2( 2 ) , g 3( 2 ) ,..., g G( 2( )2 ) −1 . The coded bit sequence
g 0 , g1 , g 2 , g 3 ,..., g G −1 , where G = G (1) + G ( 2) , is generated according to the following.

Table 6.3.1.6-1: PUCCH DMRS and UCI symbols

PUCCH Number of UCI 3rd UCI symbol

PUCCH DMRS 1st UCI symbol 2nd UCI symbol
duration symbol indices (1) ( 2)
indices set
symbol indices set indices set S UCI indices set S UCI ( 3)
(symbols) sets N UCI S 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 )
Denote sl as UCI OFDM symbol index. Denote N UCI as the number of elements in UCI symbol indices set S UCI
for i = 1,..., N UCI
set (i )
, where S UCI set
and N UCI are given by Table 6.3.1.6-1 according to the PUCCH duration and the
set
N UCI
PUCCH DMRS configuration. Denote N PUCCH,
symb, UCI = ∑N
i =1
(i )
UCI
as the number of OFDM symbols carrying UCI in the

PUCCH. Denote Qm as the modulation order of the PUCCH.

symbol PUCCH,3 PUCCH,3
For PUCCH format 3, set 𝑁𝑁UCI = 12 ⋅ 𝑁𝑁PRB /𝑁𝑁SF PUCCH,3
, where N PRB is the number of PRBs that is
PUCCH,3
determined by the UE for PUCCH format 3 transmission according to Clause 9.2 of [5, TS 38.213], and 𝑁𝑁SF is
the spreading factor for PUCCH format 3 [4, TS 38.211].
symbol
For PUCCH format 4, set N UCI = 12 / N SF
PUCCH, 4 PUCCH, 4
, where N SF is the spreading factor for PUCCH format 4.

 j
 symbol
Find the smallest j > 0 such that 
 ∑N (i)
UCI  ⋅ N UCI ⋅ Qm ≥ G (1) .
 i =1 

3GPP
Release 16156T 59 3GPP TS 38.212 V16.6.0 (2021-06)

Set n1 = 0 ;

Set n2 = 0 ;

  j −1
 symbol  
symbol
Set N UCI =  G (1) −  ∑N (i)
UCI  ⋅ N UCI ⋅ Qm  (N ( j)
UCI )
⋅ Qm  ;
  i =1   

  j −1
 symbol  
Set M = mod  G (1) − 
  ∑N (i)
UCI
( j) 
 ⋅ N UCI ⋅ Qm  Qm , N UCI

;
  i =1   

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

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

for k = 0 to N UCI
symbol
−1

for v = 0 to Qm − 1

g l ,k ,v = g n(11 ) ;

n1 = n1 + 1 ;

end for

elseif sl ∈ S UCI
( j)

if M > 0

γ = 1;

else

γ = 0;

end if

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

for v = 0 to Qm − 1

g l ,k ,v = g n(11 ) ;

n1 = n1 + 1 ;

end for

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

for v = 0 to Qm − 1

3GPP
Release 16156T 60 3GPP TS 38.212 V16.6.0 (2021-06)

g l ,k ,v = g n( 22 ) ;

n2 = n2 + 1 ;

end for

else

for k = 0 to N UCI
symbol
−1

for v = 0 to Qm − 1

g l ,k ,v = g n( 22 ) ;

n2 = n2 + 1 ;

end for

end if

end for

Set n = 0

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

for k = 0 to N UCI
symbol
−1

for v = 0 to Qm − 1

g n = g l , k ,v ;

n = n +1;
end for

end for

6.3.2 Uplink control information on PUSCH

6.3.2.1 UCI bit sequence generation
6.3.2.1.1 HARQ-ACK
If HARQ-ACK bits are transmitted on a PUSCH, the UCI bit sequence a 0 , a1 , a 2 , a 3 ,..., 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 a0 = 0 , a1 = 0 , and A = 2 ;

o~0ACK given by Clause 9.1 of [5, TS 38.213], set a0 = o~0 ,

ACK
- if there is only one HARQ-ACK bit
a1 = 0 , and A = 2 ;

3GPP
Release 16156T 61 3GPP TS 38.212 V16.6.0 (2021-06)

- otherwise, set ai = o~ for i = 0, 1, ..., O

ACK
− 1 and A = O ACK ACK
, where the HARQ-ACK bit sequence
i
~ ACK ~ ACK
o , o ,..., o ~ ACK
is given by Clause 9.1 of [5, TS 38.213].
0 1 O ACK −1

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

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

in Clause 6.3.1.1.2.

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

Table 6.3.2.1.2-1: PMI of codebookType= typeII

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

i1,1 i1,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
  N1 N 2 
log (O O )
SBAmp  2 1 2  log 2   log 2 (2 L ) 3(2 L − 1) N/A N/A (M1 − 1) ⋅ log2 N PSK N/A N/A N/A
  L 
off

Rank=2
  N1 N 2 
log (O O )
SBAmp  2 1 2  log 2   log 2 (2 L ) 3(2 L − 1) log 2 (2 L ) 3(2 L − 1) (M1 − 1) ⋅ log 2 N PSK (M 2 − 1) ⋅ log2 N PSK N/A N/A
  L 
off

Rank=1

( )
min M 1 , K ( 2 ) ⋅ log 2 N PSK
 N N 
log (O O ) log  1 2  log (2 L ) 3(2 L − 1) ( )
SBAmp  2 1 2   2  L   2 N/A N/A − log 2 N PSK N/A min M 1 , K ( 2 ) − 1 N/A
on
( (
+ 2 ⋅ M 1 − min M 1 , K ( 2 ) ))

Rank=2

( ) ( )
min M 1 , K ( 2 ) ⋅ log 2 N PSK min M 2 , K ( 2 ) ⋅ log 2 N PSK
 N1 N 2 
log (O O )
SBAmp  2 1 2  log 2   log 2 (2 L ) 3(2 L − 1) log 2 (2 L ) 3(2 L − 1) − log 2 N PSK − log 2 N PSK ( ) (
min M 1 , K ( 2 ) − 1 min M 2 , K ( 2 ) − 1 )
 L 
on

( (
+ 2 ⋅ M 1 − min M 1 , K ( 2 ) )) ( (
+ 2 ⋅ M 2 − min M 2 , K ( 2 ) ))

The bitwidth for PMI of codebookType=typeII-r16 is provided in Tables 6.3.2.1.2-1A, where the values of (𝑁𝑁1 , 𝑁𝑁2 ),
(𝑂𝑂1 , 𝑂𝑂2 ), 𝐿𝐿, 𝐾𝐾 𝑁𝑁𝑁𝑁 , 𝑁𝑁3 , and {𝑀𝑀𝑙𝑙 }𝑙𝑙=1,…,𝜐𝜐 are given by Clause 5.2.2.2.5 in [6, TS 38.214].

Table 6.3.2.1.2-1A: PMI of codebookType= typeII-r16

Information fields 𝑋𝑋1

𝑖𝑖1,1 𝑖𝑖1,2 𝑖𝑖1,8,1 𝑖𝑖1,8,2 𝑖𝑖1,8,3 𝑖𝑖1,8,4

Rank=1 ⌈log 2 (𝑂𝑂1 𝑂𝑂2 )⌉ 𝑁𝑁1 𝑁𝑁2 ⌈log 2 𝐾𝐾 𝑁𝑁𝑁𝑁 ⌉ N/A N/A N/A
�log 2 � ��
𝐿𝐿
𝑁𝑁3 ≤ 19

Rank=2 ⌈log 2 (𝑂𝑂1 𝑂𝑂2 )⌉ 𝑁𝑁1 𝑁𝑁2 ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉ N/A N/A
�log 2 � ��
𝐿𝐿
𝑁𝑁3 ≤ 19

Rank=3 ⌈log 2 (𝑂𝑂1 𝑂𝑂2 )⌉ 𝑁𝑁1 𝑁𝑁2 ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉ N/A
�log 2 � ��
𝐿𝐿
𝑁𝑁3 ≤ 19

3GPP
Release 16156T 62 3GPP TS 38.212 V16.6.0 (2021-06)

Rank=4 ⌈log 2 (𝑂𝑂1 𝑂𝑂2 )⌉ 𝑁𝑁1 𝑁𝑁2 ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉
�log 2 � ��
𝐿𝐿
𝑁𝑁3 ≤ 19

Rank=1 ⌈log 2 (𝑂𝑂1 𝑂𝑂2 )⌉ 𝑁𝑁1 𝑁𝑁2 ⌈log 2 𝐾𝐾 𝑁𝑁𝑁𝑁 ⌉ N/A N/A N/A
�log 2 � ��
𝐿𝐿
𝑁𝑁3 > 19

Rank=2 ⌈log 2 (𝑂𝑂1 𝑂𝑂2 )⌉ 𝑁𝑁1 𝑁𝑁2 ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉ N/A N/A
�log 2 � ��
𝐿𝐿
𝑁𝑁3 > 19

Rank=3 ⌈log 2 (𝑂𝑂1 𝑂𝑂2 )⌉ 𝑁𝑁1 𝑁𝑁2 ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉ N/A
�log 2 � ��
𝐿𝐿
𝑁𝑁3 > 19

Rank=4 ⌈log 2 (𝑂𝑂1 𝑂𝑂2 )⌉ 𝑁𝑁1 𝑁𝑁2 ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉
�log 2 � ��
𝐿𝐿
𝑁𝑁3 > 19

Information fields 𝑋𝑋2

𝑖𝑖2,3,1 𝑖𝑖2,3,2 𝑖𝑖2,3,3 𝑖𝑖2,3,4 𝑖𝑖1,5 𝑖𝑖1,6,1 𝑖𝑖1,6,2 𝑖𝑖1,6,3 𝑖𝑖1,6,4 {𝑖𝑖2,4,𝑙𝑙 }𝑙𝑙=1,…,𝜐𝜐 {𝑖𝑖2,5,𝑙𝑙 }𝑙𝑙=1,…,𝜐𝜐 {𝑖𝑖1,7,𝑙𝑙 }𝑙𝑙=1,…,𝜐𝜐

Rank= 4 N/A N/ N/ N/A 𝑁𝑁 − 1 N/A N/A N/A 3(𝐾𝐾 𝑁𝑁𝑁𝑁 4(𝐾𝐾 𝑁𝑁𝑁𝑁 2𝐿𝐿𝑀𝑀1
�log 2 � 3 ��
1 A A 𝑀𝑀1 − 1 − 1) − 1)

𝑁𝑁3
≤ 19

Rank= 4 4 N/ N/ N/A 𝑁𝑁 − 1 𝑁𝑁 − 1 N/A N/A 3(𝐾𝐾 𝑁𝑁𝑁𝑁 4(𝐾𝐾 𝑁𝑁𝑁𝑁 4𝐿𝐿𝑀𝑀2

�log 2 � 3 �� log 2 � 3 ��
2 A A 𝑀𝑀2 − 1 𝑀𝑀2 − 1 − 2) − 2)

𝑁𝑁3
≤ 19

Rank= 4 4 4 N/ N/A 𝑁𝑁 − 1 𝑁𝑁 − 1 𝑁𝑁 − 1 N/A 3(𝐾𝐾 𝑁𝑁𝑁𝑁 4(𝐾𝐾 𝑁𝑁𝑁𝑁 6𝐿𝐿𝑀𝑀3

�log 2 � 3 �� log 2 � 3 �� log 2 � 3 ��
3 A 𝑀𝑀3 − 1 𝑀𝑀3 − 1 𝑀𝑀3 − 1 − 3) − 3)

𝑁𝑁3
≤ 19

Rank= 4 4 4 4 N/A 𝑁𝑁 − 1 𝑁𝑁 − 1 𝑁𝑁 − 1 𝑁𝑁 − 1 3(𝐾𝐾 𝑁𝑁𝑁𝑁 4(𝐾𝐾 𝑁𝑁𝑁𝑁 8𝐿𝐿𝑀𝑀4

�log 2 � 3 �� log 2 � 3 �� log 2 � 3 �� log 2 � 3 ��
4 𝑀𝑀4 − 1 𝑀𝑀4 − 1 𝑀𝑀4 − 1 𝑀𝑀4 − 1 − 4) − 4)

𝑁𝑁3
≤ 19

Rank= 4 N/A N/ N/ ⌈log 2 (2𝑀𝑀1 )⌉ 2𝑀𝑀 − 1 N/A N/A N/A 3(𝐾𝐾 𝑁𝑁𝑁𝑁 4(𝐾𝐾 𝑁𝑁𝑁𝑁 2𝐿𝐿𝑀𝑀1
�log 2 � 1 ��
1 A A 𝑀𝑀1 − 1 − 1) − 1)

𝑁𝑁3
> 19

Rank= 4 4 N/ N/ ⌈log 2 (2𝑀𝑀2 )⌉ 2𝑀𝑀 − 1 2𝑀𝑀 − 1 N/A N/A 3(𝐾𝐾 𝑁𝑁𝑁𝑁 4(𝐾𝐾 𝑁𝑁𝑁𝑁 4𝐿𝐿𝑀𝑀2
�log 2 � 2 �� log 2 � 2 ��
2 A A 𝑀𝑀2 − 1 𝑀𝑀2 − 1 − 2) − 2)

𝑁𝑁3
> 19

Rank= 4 4 4 N/ ⌈log 2 (2𝑀𝑀3 )⌉ 2𝑀𝑀 − 1 2𝑀𝑀 − 1 2𝑀𝑀 − 1 N/A 3(𝐾𝐾 𝑁𝑁𝑁𝑁 4(𝐾𝐾 𝑁𝑁𝑁𝑁 6𝐿𝐿𝑀𝑀3
�log 2 � 3 �� log 2 � 3 �� log 2 � 3 ��
3 A 𝑀𝑀3 − 1 𝑀𝑀3 − 1 𝑀𝑀3 − 1 − 3) − 3)

𝑁𝑁3
> 19

Rank= 4 4 4 4 ⌈log 2 (2𝑀𝑀4 )⌉ 2𝑀𝑀 − 1 2𝑀𝑀 − 1 2𝑀𝑀 − 1 2𝑀𝑀 − 1 3(𝐾𝐾 𝑁𝑁𝑁𝑁 4(𝐾𝐾 𝑁𝑁𝑁𝑁 8𝐿𝐿𝑀𝑀4
�log 2 � 4 �� log 2 � 4 �� log 2 � 4 �� log 2 � 4 ��
4 𝑀𝑀4 − 1 𝑀𝑀4 − 1 𝑀𝑀4 − 1 𝑀𝑀4 − 1 − 4) − 4)

𝑁𝑁3
> 19

Note: the bitwidth for {𝑖𝑖1,7,𝑙𝑙 }𝑙𝑙=1,…,𝜐𝜐 , {𝑖𝑖2,4,𝑙𝑙 }𝑙𝑙=1,…,𝜐𝜐 and {𝑖𝑖2,5,𝑙𝑙 }𝑙𝑙=1,…,𝜐𝜐 shown in Table 6.3.2.1.2-1A is the total
bitwidth of {𝑖𝑖1,7,𝑙𝑙 }, {𝑖𝑖2,4,𝑙𝑙 } and {𝑖𝑖2,5,𝑙𝑙 } up to Rank = 𝜐𝜐, respectively, and the corresponding per layer
bitwidths are 2𝐿𝐿𝑀𝑀𝜐𝜐 , 3(𝐾𝐾𝑙𝑙𝑁𝑁𝑁𝑁 − 1), and 4(𝐾𝐾𝑙𝑙𝑁𝑁𝑁𝑁 − 1), (i.e., 1, 3, and 4 bits for each respective indicator
(3) (2)
elements 𝑘𝑘𝑙𝑙,𝑖𝑖,𝑓𝑓 , 𝑘𝑘𝑙𝑙,𝑖𝑖,𝑓𝑓 , and 𝑐𝑐𝑙𝑙,𝑖𝑖,𝑓𝑓 , respectively), where 𝐾𝐾𝑙𝑙𝑁𝑁𝑁𝑁 as defined in Clause 5.2.2.2.5 in [6, TS
38.214] is the number of nonzero coefficients for layer 𝑙𝑙 such that 𝐾𝐾 𝑁𝑁𝑁𝑁 = ∑𝜐𝜐𝑙𝑙=1 𝐾𝐾𝑙𝑙𝑁𝑁𝑁𝑁 .

3GPP
Release 16156T 63 3GPP TS 38.212 V16.6.0 (2021-06)

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

Table 6.3.2.1.2-2: PMI of codebookType= typeII-PortSelection

Information fields X 1 for wideband PMI Information fields X 2 for wideband PMI or per subband
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  
log (2 L ) 3(2 L − 1) (M1 − 1) ⋅ log2 N PSK
SBAmp  2  2d    2
log N/A N/A N/A N/A N/A
off

Rank=2
  PCSI − RS  
log (2 L ) 3(2 L − 1) log 2 (2 L ) 3(2 L − 1) (M1 − 1) ⋅ log2 N PSK (M 2 − 1) ⋅ log2 N PSK
SBAmp  2  2d    2
log N/A N/A
off

Rank=1

( )
min M 1 , K ( 2 ) ⋅ log 2 N PSK
 PCSI − RS  
log (2 L ) 3(2 L − 1) ( )
SBAmp  2  2d    2
log N/A N/A − log 2 N PSK N/A min M 1 , K ( 2 ) − 1 N/A
on
( (
+ 2 ⋅ M 1 − min M 1 , K ( 2 ) ))

Rank=2

( ) ( )
min M 1 , K ( 2 ) ⋅ log 2 N PSK min M 2 , K ( 2 ) ⋅ log 2 N PSK
 PCSI − RS  
log (2 L ) 3(2 L − 1) log 2 (2 L ) 3(2 L − 1) − log2 N PSK ( ) ( )
SBAmp  2  2d    2
log − log 2 N PSK min M 1 , K ( 2 ) − 1 min M 2 , K ( 2 ) − 1

on
( (
+ 2 ⋅ M 1 − min M 1 , K ( 2 ) )) ( (
+ 2 ⋅ M 2 − min M 2 , K ( 2 ) ))

The bitwidth for PMI of codebookType=typeII-PortSelection-r16 is provided in Tables 6.3.2.1.2-2A, where the values
of 𝑃𝑃𝐶𝐶𝐶𝐶𝐶𝐶−𝑅𝑅𝑅𝑅 , 𝑑𝑑, 𝐿𝐿, 𝐾𝐾 𝑁𝑁𝑁𝑁 , 𝑁𝑁3 , and {𝑀𝑀𝑙𝑙 }𝑙𝑙=1,…,𝜐𝜐 are given by Clause 5.2.2.2.6 in [6, TS 38.214].

Table 6.3.2.1.2-2A: PMI of codebookType= typeII-PortSelection-r16

Information fields 𝑋𝑋1

𝑖𝑖1,1 𝑖𝑖1,8,1 𝑖𝑖1,8,2 𝑖𝑖1,8,3 𝑖𝑖1,8,4

Rank=1 𝑃𝑃𝐶𝐶𝐶𝐶𝐶𝐶−𝑅𝑅𝑅𝑅 ⌈log 2 𝐾𝐾 𝑁𝑁𝑁𝑁 ⌉ N/A N/A N/A

�log 2 � ��
2𝑑𝑑
𝑁𝑁3 ≤ 19

Rank=2 𝑃𝑃𝐶𝐶𝐶𝐶𝐶𝐶−𝑅𝑅𝑅𝑅 ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉ N/A N/A

�log 2 � ��
2𝑑𝑑
𝑁𝑁3 ≤ 19

Rank=3 𝑃𝑃𝐶𝐶𝐶𝐶𝐶𝐶−𝑅𝑅𝑅𝑅 ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉ N/A

�log 2 � ��
2𝑑𝑑
𝑁𝑁3 ≤ 19

Rank=4 𝑃𝑃𝐶𝐶𝐶𝐶𝐶𝐶−𝑅𝑅𝑅𝑅 ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉
�log 2 � ��
2𝑑𝑑
𝑁𝑁3 ≤ 19

Rank=1 𝑃𝑃𝐶𝐶𝐶𝐶𝐶𝐶−𝑅𝑅𝑅𝑅 ⌈log 2 𝐾𝐾 𝑁𝑁𝑁𝑁 ⌉ N/A N/A N/A

�log 2 � ��
2𝑑𝑑
𝑁𝑁3 > 19

Rank=2 𝑃𝑃𝐶𝐶𝐶𝐶𝐶𝐶−𝑅𝑅𝑅𝑅 ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉ N/A N/A

�log 2 � ��
2𝑑𝑑
𝑁𝑁3 > 19

Rank=3 𝑃𝑃𝐶𝐶𝐶𝐶𝐶𝐶−𝑅𝑅𝑅𝑅 ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉ N/A

�log 2 � ��
2𝑑𝑑

3GPP
Release 16156T 64 3GPP TS 38.212 V16.6.0 (2021-06)

𝑁𝑁3 > 19

Rank=4 𝑃𝑃𝐶𝐶𝐶𝐶𝐶𝐶−𝑅𝑅𝑅𝑅 ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉ ⌈log 2 (2𝐿𝐿)⌉
�log 2 � ��
2𝑑𝑑
𝑁𝑁3 > 19

Information fields 𝑋𝑋2

Rank= 4 N/ N/A N/ N/A 𝑁𝑁 − 1 N/A N/A N/A 3(𝐾𝐾 𝑁𝑁𝑁𝑁 4(𝐾𝐾 𝑁𝑁𝑁𝑁 2𝐿𝐿𝑀𝑀1
�log 2 � 3 ��
1 A A 𝑀𝑀1 − 1 − 1) − 1)

𝑁𝑁3
≤ 19

Rank= 4 4 N/A N/ N/A 𝑁𝑁 − 1 𝑁𝑁 − 1 N/A N/A 3(𝐾𝐾 𝑁𝑁𝑁𝑁 4(𝐾𝐾 𝑁𝑁𝑁𝑁 4𝐿𝐿𝑀𝑀2
�log 2 � 3 �� log 2 � 3 ��
2 A 𝑀𝑀2 − 1 𝑀𝑀2 − 1 − 2) − 2)

𝑁𝑁3
≤ 19

Rank= 4 4 4 N/ N/A 𝑁𝑁 − 1 𝑁𝑁 − 1 𝑁𝑁 − 1 N/A 3(𝐾𝐾 𝑁𝑁𝑁𝑁 4(𝐾𝐾 𝑁𝑁𝑁𝑁 6𝐿𝐿𝑀𝑀3

�log 2 � 3 �� log 2 � 3 �� log 2 � 3 ��
3 A 𝑀𝑀3 − 1 𝑀𝑀3 − 1 𝑀𝑀3 − 1 − 3) − 3)

𝑁𝑁3
≤ 19

Rank= 4 4 4 4 N/A 𝑁𝑁 − 1 𝑁𝑁 − 1 𝑁𝑁 − 1 𝑁𝑁 − 1 3(𝐾𝐾 𝑁𝑁𝑁𝑁 4(𝐾𝐾 𝑁𝑁𝑁𝑁 8𝐿𝐿𝑀𝑀4

�log 2 � 3 �� log 2 � 3 �� log 2 � 3 �� log 2 � 3 ��
4 𝑀𝑀4 − 1 𝑀𝑀4 − 1 𝑀𝑀4 − 1 𝑀𝑀4 − 1 − 4) − 4)

𝑁𝑁3
≤ 19

Rank= 4 N/ N/A N/ ⌈log 2 (2𝑀𝑀1 )⌉ 2𝑀𝑀 − 1 N/A N/A N/A 3(𝐾𝐾 𝑁𝑁𝑁𝑁 4(𝐾𝐾 𝑁𝑁𝑁𝑁 2𝐿𝐿𝑀𝑀1
�log 2 � 1 ��
1 A A 𝑀𝑀1 − 1 − 1) − 1)

𝑁𝑁3
> 19

Rank= 4 4 N/A N/ ⌈log 2 (2𝑀𝑀2 )⌉ 2𝑀𝑀 − 1 2𝑀𝑀 − 1 N/A N/A 3(𝐾𝐾 𝑁𝑁𝑁𝑁 4(𝐾𝐾 𝑁𝑁𝑁𝑁 4𝐿𝐿𝑀𝑀2
�log 2 � 2 �� log 2 � 2 ��
2 A 𝑀𝑀2 − 1 𝑀𝑀2 − 1 − 2) − 2)

𝑁𝑁3
> 19

Note: the bitwidth for {𝑖𝑖1,7,𝑙𝑙 }𝑙𝑙=1,…,𝜐𝜐 , {𝑖𝑖2,4,𝑙𝑙 }𝑙𝑙=1,…,𝜐𝜐 and {𝑖𝑖2,5,𝑙𝑙 }𝑙𝑙=1,…,𝜐𝜐 shown in Table 6.3.2.1.2-2A is the total
bitwidth of {𝑖𝑖1,7,𝑙𝑙 }, {𝑖𝑖2,4,𝑙𝑙 } and {𝑖𝑖2,5,𝑙𝑙 } up to Rank = 𝜐𝜐, respectively, and the corresponding per layer
bitwidths are 2𝐿𝐿𝑀𝑀𝜐𝜐 , 3(𝐾𝐾𝑙𝑙𝑁𝑁𝑁𝑁 − 1), and 4(𝐾𝐾𝑙𝑙𝑁𝑁𝑁𝑁 − 1), (i.e., 1, 3, and 4 bits for each respective indicator
(3) (2)
elements 𝑘𝑘𝑙𝑙,𝑖𝑖,𝑓𝑓 , 𝑘𝑘𝑙𝑙,𝑖𝑖,𝑓𝑓 , and 𝑐𝑐𝑙𝑙,𝑖𝑖,𝑓𝑓 , respectively), where 𝐾𝐾𝑙𝑙𝑁𝑁𝑁𝑁 as defined in Clause 5.2.2.2.5 in [6, TS
38.214] is the number of nonzero coefficients for layer 𝑙𝑙 such that 𝐾𝐾 𝑁𝑁𝑁𝑁 = ∑𝜐𝜐𝑙𝑙=1 𝐾𝐾𝑙𝑙𝑁𝑁𝑁𝑁 .

For CSI on PUSCH, two UCI bit sequences are generated, a0(1) , a1(1) , a2(1) , a3(1) ,..., a A(1()1) −1 and a0( 2 ) , a1( 2 ) , a2( 2 ) , a3( 2 ) ,..., a A( 2( 2) ) −1 .
The CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.2.1.2-6, are mapped to the UCI
bit sequence a0(1) , a1(1) , a2(1) , a3(1) ,..., a A(1()1) −1 starting with a0(1) . The CSI fields of all CSI reports, in the order from upper
part to lower part in Table 6.3.2.1.2-7, are mapped to the UCI bit sequence a0( 2 ) , a1( 2 ) , a2( 2 ) , a3( 2 ) ,..., a A( 2( 2) ) −1 starting with
a0( 2 ) .

The mapping order of CSI fields of one report for CRI/RSRP or SSBRI/RSRP reporting is provided in Table 6.3.1.1.2-
8. The mapping order of CSI fields of one report for CRI/SINR or SSBRI/SINR reporting is provided in Table
6.3.1.1.2-8A. 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.

3GPP
Release 16156T 65 3GPP TS 38.212 V16.6.0 (2021-06)

Table 6.3.2.1.2-3: Mapping order of CSI fields of one CSI report, CSI part 1

CSI report number CSI fields

CRI as in Tables 6.3.1.1.2-3/4/6, if reported

Rank Indicator as in Tables 6.3.1.1.2-3/4/5 or 6.3.2.1.2-8, if reported
Wideband CQI for the first TB as in Tables 6.3.1.1.2-3/4/5 or 6.3.2.1.2-8, if reported
Subband differential CQI for the first TB with increasing order of subband number as in
Tables 6.3.1.1.2-3/4/5 or 6.3.2.1.2-8, if reported
CSI report #n Indicator of the number of non-zero wideband amplitude coefficients 𝑀𝑀0 for layer 0 as in
CSI part 1 Table 6.3.1.1.2-5, if reported
Indicator of the number of non-zero wideband amplitude coefficients 𝑀𝑀1 for layer 1 as in
Table 6.3.1.1.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 5.2.2.2.3
and 5.2.2.2.4 [6, TS 38.214] and if reported
Indicator of the total number of non-zero coefficients summed across all layers 𝐾𝐾 𝑁𝑁𝑁𝑁 as in
Table 6.3.2.1.2-8, 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 6.3.2.1.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 6.3.1.1.2-3/4/5, if present and reported
Layer Indicator as in Tables 6.3.1.1.2-3/4/5, if reported
CSI report #n PMI wideband information fields X 1 , from left to right as in Tables 6.3.1.1.2-1/2 or 6.3.2.1.2-
CSI part 2 1/2, if reported
wideband
PMI wideband information fields X 2 , from left to right as in Tables 6.3.1.1.2-1/2 or 6.3.2.1.2-
1/2, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214], if
pmi-FormatIndicator= widebandPMI and if reported

Table 6.3.2.1.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 6.3.1.1.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 6.3.1.1.2-1/2 or 6.3.2.1.2-1/2, or codebook index for 2
antenna ports according to Clause 5.2.2.2.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 6.3.1.1.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 6.3.1.1.2-1/2 or 6.3.2.1.2-1/2, or codebook index for 2
antenna ports according to Clause 5.2.2.2.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 16156T 66 3GPP TS 38.212 V16.6.0 (2021-06)

Table 6.3.2.1.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
PMI fields 𝑋𝑋1 , from left to right as in Tables 6.3.2.1.2-1A/2A, if reported
CSI part 2, group 0
The following PMI fields 𝑋𝑋2 , from left to right, as in Tables 6.3.2.1.2-1A/2A: �𝑖𝑖2,3,𝑙𝑙 : 𝑙𝑙 = 1, … , 𝜐𝜐�,
𝐾𝐾 𝑁𝑁𝑁𝑁
𝑖𝑖1,5 , �𝑖𝑖1,6,𝑙𝑙 : 𝑙𝑙 = 1, … , 𝜐𝜐� and (� � − 𝜐𝜐) × 3 highest priority bits of
CSI report #n 2
𝑁𝑁𝑁𝑁
CSI part 2, group 1 �𝑖𝑖2,4,𝑙𝑙 : 𝑙𝑙 = 1, … , 𝜐𝜐�, (⌈𝐾𝐾 /2⌉ − 𝜐𝜐) × 4 highest priority bits of {𝑖𝑖2,5,𝑙𝑙 : 𝑙𝑙 = 1, … , 𝜐𝜐} and 𝜈𝜈 ∗ 2𝐿𝐿𝑀𝑀𝜐𝜐 −
⌊𝐾𝐾 𝑁𝑁𝑁𝑁 /2⌋ highest priority bits of�𝑖𝑖1,7,𝑙𝑙 : 𝑙𝑙 = 1, … , 𝜐𝜐�, in decreasing order of priority based on
function Pri(𝑙𝑙, 𝑖𝑖, 𝑓𝑓) defined in clause 5.2.3 of TS38.214, if reported
The following PMI fields 𝑋𝑋2 , from left to right, as in Tables 6.3.2.1.2-1A/2A: ⌊𝐾𝐾 𝑁𝑁𝑁𝑁 /2⌋ × 3
CSI report #n lowest priority bits of �𝑖𝑖2,4,𝑙𝑙 : 𝑙𝑙 = 1, … , 𝜐𝜐�, ⌊𝐾𝐾 𝑁𝑁𝑁𝑁 /2⌋ × 4 lowest priority bits of �𝑖𝑖2,5,𝑙𝑙 : 𝑙𝑙 = 1, … , 𝜐𝜐�
CSI part 2, group 2 and ⌊𝐾𝐾 𝑁𝑁𝑁𝑁 /2⌋ lowest priority bits of �𝑖𝑖1,7,𝑙𝑙 : 𝑙𝑙 = 1, … , 𝜐𝜐�, in decreasing order of priority based on
function Pri(𝑙𝑙, 𝑖𝑖, 𝑓𝑓) defined in clause 5.2.3 of TS38.214, if reported

Table 6.3.2.1.2-6: Mapping order of CSI reports to UCI bit sequence a0(1) , a1(1) , a2(1) , a3(1) ,..., a A(1()1) −1 ,
with two-part CSI report(s)

UCI bit sequence CSI report number

CSI part 1 of CSI report #1 as in Table 6.3.2.1.2-3 or Table

a0(1) 6.3.1.1.2-8 or Table 6.3.1.1.2-8A
a1(1)
CSI part 1 of CSI report #2 as in Table 6.3.2.1.2-3 or Table
a2(1) 6.3.1.1.2-8 or Table 6.3.1.1.2-8A
a3(1)
…

a A(1()1) −1 CSI part 1 of CSI report #n as in Table 6.3.2.1.2-3 or Table
6.3.1.1.2-8 or Table 6.3.1.1.2-8A

where CSI report #1, CSI report #2, …, CSI report #n in Table 6.3.2.1.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].

3GPP
Release 16156T 67 3GPP TS 38.212 V16.6.0 (2021-06)

Table 6.3.2.1.2-7: Mapping order of CSI reports to UCI bit sequence a0( 2 ) , a1( 2 ) , a2( 2 ) , a3( 2 ) ,..., a A( 2( 2) ) −1 ,
with two-part CSI report(s)

UCI bit sequence CSI report number

CSI report #1, CSI part 2 wideband, as in Table 6.3.2.1.2-4,

or CSI part 2 with group 0, as in Table 6.3.2.1.2-5A,
if CSI part 2 exists for CSI report #1
CSI report #2, CSI part 2 wideband, as in Table 6.3.2.1.2-4,
or CSI part 2 with group 0, as in Table 6.3.2.1.2-5A,
if CSI part 2 exists for CSI report #2

a0( 2 ) …

a1( 2 ) CSI report #n, CSI part 2 wideband, as in Table 6.3.2.1.2-4,

( 2) or CSI part 2 with group 0, as in Table 6.3.2.1.2-5A,
a 2 if CSI part 2 exists for CSI report #n
a3( 2 ) CSI report #1, CSI part 2 subband, as in Table 6.3.2.1.2-5,
or CSI part 2 with group 1 and 2, as in Table 6.3.2.1.2-5A,
 if CSI part 2 exists for CSI report #1
a A( 2( 2) ) −1 CSI report #2, CSI part 2 subband, as in Table 6.3.2.1.2-5,
or CSI part 2 with group 1 and 2, as in Table 6.3.2.1.2-5A,
if CSI part 2 exists for CSI report #2

CSI report #n, CSI part 2 subband, as in Table 6.3.2.1.2-5,

or CSI part 2 with group 1 and 2, as in Table 6.3.2.1.2-5A,
if CSI part 2 exists for CSI report #n

where CSI report #1, CSI report #2, …, CSI report #n in Table 6.3.2.1.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

6.3.2.1.2-8.

Table 6.3.2.1.2-8: RI and CQI of codebookType=typeII-r16 or typeII-PortSelection-r16

Field Bitwidth

Rank Indicator 𝑚𝑚𝑚𝑚𝑚𝑚(2, ⌈𝑙𝑙𝑙𝑙𝑙𝑙2 𝑛𝑛𝑅𝑅𝑅𝑅 ⌉)

Wide-band CQI 4
Subband differential CQI 2
⌈log 2 (𝐾𝐾0 )⌉ if max allowed
Indicator of the total number of non-zero coefficients
rank is 1;
summed across all layers 𝐾𝐾 𝑁𝑁𝑁𝑁
⌈log 2 (2𝐾𝐾0 )⌉ otherwise

where 𝑛𝑛𝑅𝑅𝑅𝑅 is the number of allowed rank indicator values according to Clauses 5.2.2.2.5 and 5.2.2.2.6 [6, TS
N
38.214], 𝐾𝐾0 = �2𝐿𝐿 �𝑝𝑝1 × 3 � 𝛽𝛽�, where 𝑝𝑝1 , 𝑁𝑁3 , 𝑅𝑅, and 𝛽𝛽 are given by Clause 5.2.2.2.5 and 5.2.2.2.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.

6.3.2.1.3 CG-UCI
For CG-UCI bits transmitted on a CG PUSCH, the CG-UCI bit sequence 𝑎𝑎0 , 𝑎𝑎1 , 𝑎𝑎2 , 𝑎𝑎3 , … , 𝑎𝑎𝐴𝐴−1 is determined as
follows:

- set 𝑎𝑎𝑖𝑖 = 𝑜𝑜�𝑖𝑖𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 for 𝑖𝑖 = 0,1, … , 𝑂𝑂𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 − 1 and 𝐴𝐴 = 𝑂𝑂𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 , where the CG-UCI bit sequence
𝑜𝑜�0𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 , 𝑜𝑜�1𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 , … , 𝑜𝑜�𝑂𝑂𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈
𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 −1 is given by Table 6.3.2.1.3-1, mapped in the order from upper part to lower
part.

3GPP
Release 16156T 68 3GPP TS 38.212 V16.6.0 (2021-06)

Table 6.3.2.1.3-1: Mapping order of CG-UCI fields

Field Bitwidth
HARQ process number 4
Redundancy version 2
New data indicator 1
⌈log 2 𝐶𝐶⌉ if both higher layer parameter ul-toDL-COT-SharingED-
Threshold and higher layer parameter cg-COT-SharingList are
configured, where C is the number of combinations configured in
cg-COT-SharingList;

1 if higher layer parameter ul-toDL-COT-SharingED-Threshold is

not configured and higher layer parameter cg-COT-SharingOffset is
Channel Occupancy Time (COT) sharing configured;
information
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.

6.3.2.1.4 HARQ-ACK and CG-UCI

When higher layer parameter cg-UCI-Multiplexing is configured, the UCI bit sequence 𝑎𝑎0 , 𝑎𝑎1 , 𝑎𝑎2 , 𝑎𝑎3 , … , 𝑎𝑎𝐴𝐴−1 is
determined as follows, where 𝐴𝐴 = 𝑂𝑂𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 + 𝑂𝑂 𝐴𝐴𝐴𝐴𝐴𝐴 .

- The CG-UCI bits are mapped to the UCI bit sequence𝑎𝑎0 , 𝑎𝑎1 , 𝑎𝑎2 , 𝑎𝑎3 , … , 𝑎𝑎𝑂𝑂CG−UCI−1 , where 𝑎𝑎𝑖𝑖 = 𝑜𝑜�𝑖𝑖𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 for 𝑖𝑖 =
0,1, … , 𝑂𝑂𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 − 1. The CG-UCI bit sequence 𝑜𝑜�0CG−UCI , 𝑜𝑜�1CG−UCI , … , 𝑜𝑜�𝑂𝑂CG−UCI
𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 −1 is given by Table 6.3.2.1.3-1

mapped in the order from upper part to lower part, and 𝑂𝑂CG−UCI is number of CG-UCI bits;

- The HARQ-ACK bits are mapped to the UCI bit sequence 𝑎𝑎𝑂𝑂𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 , 𝑎𝑎𝑂𝑂𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈+1 , … , 𝑎𝑎𝑂𝑂𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈+𝑂𝑂𝐴𝐴𝐴𝐴𝐴𝐴 −1 , where
𝑎𝑎𝑖𝑖+𝑂𝑂𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 = 𝑜𝑜�𝑖𝑖ACK for 𝑖𝑖 = 0,1, … , 𝑂𝑂ACK − 1. The HARQ-ACK bit sequence 𝑜𝑜�0ACK , 𝑜𝑜�1ACK , … , 𝑜𝑜�𝑂𝑂ACK
𝐴𝐴𝐴𝐴𝐴𝐴 −1 is given

by Clause 9.1 of [5, TS38.213], and 𝑂𝑂ACK is number of HARQ-ACK bits.

6.3.2.2 Code block segmentation and CRC attachment

Denote the bits of the payload by a 0 , a1 , a 2 , a 3 ,..., a A−1 , where A is the payload size. The procedure in 6.3.2.2.1
applies for A ≥ 12 and the procedure in Clause 6.3.2.2.2 applies for A ≤ 11 .

6.3.2.2.1 UCI encoded by Polar code

Code block segmentation and CRC attachment is performed according to Clause 6.3.1.2.1.

6.3.2.2.2 UCI encoded by channel coding of small block lengths

The procedure in Clause 6.3.1.2.2 applies.

6.3.2.3 Channel coding of UCI

6.3.2.3.1 UCI encoded by Polar code
Channel coding is performed according to Clause 6.3.1.3.1, except that the rate matching output sequence length Er
is given in Clause 6.3.2.4.1.

6.3.2.3.2 UCI encoded by channel coding of small block lengths

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

The information bits are encoded according to Clause 5.3.3.

3GPP
Release 16156T 69 3GPP TS 38.212 V16.6.0 (2021-06)

After encoding the bits are denoted by d 0 , d1 , d 2 , d 3 ,..., d N −1 , where N is the number of coded bits.

6.3.2.4 Rate matching

6.3.2.4.1 UCI encoded by Polar code
6.3.2.4.1.1 HARQ-ACK

For HARQ-ACK transmission on PUSCH not using repetition type B with UL-SCH, the number of coded modulation
′ , is determined as follows:
symbols per layer for HARQ-ACK transmission, denoted as QACK

 PUSCH
N symb, all −1  
 (OACK + LACK ) ⋅ β offset ⋅ ∑ M scUCI (l )   Nsymb,
PUSCH
PUSCH
− 

1
= min  , α ⋅ ( )
all

′
QACK
 C UL −SCH −1
l =0
 ∑ M UCI
sc l  
  
 ∑ Kr 
l = l0


 r =0  
where

- OACK is the number of HARQ-ACK bits;

- if OACK ≥ 360 , LACK = 11 ; otherwise LACK is the number of CRC bits for HARQ-ACK determined according
to Clause 6.3.1.2.1;

- β offset
PUSCH
= β offset
HARQ− ACK
;

- 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 scPUSCH is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

- M scPT-RS ( l ) is the number of subcarriers in OFDM symbol l that carries PTRS, in the PUSCH transmission;

- M scUCI ( l ) is the number of resource elements that can be used for transmission of UCI in OFDM symbol l , for
l = 0, 1, 2, ..., N symb,
PUSCH
all − 1
PUSCH
, 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, M scUCI ( l ) = 0 ;

sc ( l ) M scPUSCH − M scPT-RS ( l ) ;
- for any OFDM symbol that does not carry DMRS of the PUSCH, M=UCI

- α is configured by higher layer parameter scaling;

- l0 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 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 𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴 , is determined as follows:

3GPP
Release 16156T 70 3GPP TS 38.212 V16.6.0 (2021-06)

PUSCH
𝑁𝑁PUSCH −1 𝑁𝑁symb,nominal −1

′
(𝑂𝑂𝐴𝐴𝐴𝐴𝐴𝐴 + 𝐿𝐿𝐴𝐴𝐴𝐴𝐴𝐴 ) ∙ 𝛽𝛽offset
PUSCH
∙ ∑𝑙𝑙=0
symb,nominal
𝑀𝑀sc,nominal
UCI
(𝑙𝑙)
𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴 = min �� 𝐶𝐶UL-SCH −1 �, �𝛼𝛼 ∙ � 𝑀𝑀sc,nominal
UCI
(𝑙𝑙)� ,
∑𝑟𝑟=0 𝐾𝐾𝑟𝑟 𝑙𝑙=0
PUSCH
𝑁𝑁symb,actual −1

� 𝑀𝑀sc,actual
UCI
(𝑙𝑙)�
𝑙𝑙=0

where
UCI
- 𝑀𝑀sc,nominal (𝑙𝑙) is the number of resource elements that can be used for transmission of UCI in OFDM symbol 𝑙𝑙,
PUSCH
for 𝑙𝑙 = 0, 1, 2, ⋯ , 𝑁𝑁symb,nominal − 1, in the PUSCH transmission assuming a nominal repetition without
PUSCH
segmentation, and 𝑁𝑁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, 𝑀𝑀sc,nominal (𝑙𝑙) = 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, 𝑀𝑀sc,nominal (𝑙𝑙) = 𝑀𝑀sc − 𝑀𝑀sc,nominal (𝑙𝑙) where 𝑀𝑀sc,nominal (𝑙𝑙) is the number of subcarriers in
OFDM symbol 𝑙𝑙 that carries PTRS, in the PUSCH transmission assuming a nominal repetition without
segmentation;
UCI
- 𝑀𝑀sc,actual (𝑙𝑙) is the number of resource elements that can be used for transmission of UCI in OFDM symbol 𝑙𝑙 ,
PUSCH PUSCH
for 𝑙𝑙 = 0, 1, 2, ⋯ , 𝑁𝑁symb,actual − 1, in the actual repetition of the PUSCH transmission, and 𝑁𝑁symb,actual is the
total number of OFDM symbols in the actual repetition of the PUSCH transmission, including all OFDM
symbols used for DMRS;
UCI
- for any OFDM symbol that carries DMRS of the actual repetition of the PUSCH transmission, 𝑀𝑀sc,actual (𝑙𝑙) =
0;

- for any OFDM symbol that does not carry DMRS of the actual repetition of the PUSCH transmission,
UCI PUSCH PT-RS PT-RS
𝑀𝑀sc,actual (𝑙𝑙) = 𝑀𝑀sc − 𝑀𝑀sc,actual (𝑙𝑙) where 𝑀𝑀sc,actual (𝑙𝑙) is the number of subcarriers in OFDM symbol 𝑙𝑙
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.

For HARQ-ACK transmission on PUSCH without UL-SCH, the number of coded modulation symbols per layer for
′ , is determined as follows:
HARQ-ACK transmission, denoted as QACK

  ( OACK + LACK ) ⋅ β offset    

PUSCH PUSCH
Nsymb,all −1

= ′  , α ⋅ ∑ M sc ( l )  
UCI
QACK min  
  R ⋅ Qm   l =l0  

where

- OACK is the number of HARQ-ACK bits;

- if OACK ≥ 360 , LACK = 11 ; otherwise LACK is the number of CRC bits for HARQ-ACK defined according to
Clause 6.3.1.2.1;;

-
β offset
PUSCH
= β offset
HARQ − ACK
;

- M scPUSCH is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

- M scPT-RS ( l ) is the number of subcarriers in OFDM symbol l that carries PTRS, in the PUSCH transmission;

3GPP
Release 16156T 71 3GPP TS 38.212 V16.6.0 (2021-06)

- for any OFDM symbol that carries DMRS of the PUSCH, M scUCI ( l ) = 0 ;

sc ( l ) M scPUSCH − M scPT-RS ( l ) ;
- for any OFDM symbol that does not carry DMRS of the PUSCH, M=UCI

- l0 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;

- R is the code rate of the PUSCH, determined according to Clause 6.1.4.1 of [6, TS38.214];

- Qm is the modulation order of the PUSCH;

- α is configured by higher layer parameter scaling.

The input bit sequence to rate matching is d r 0 , d r1 , d r 2 , d r 3 ,..., d r ( N −1) where

r
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 E r = E UCI / 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 r1 , f r 2 ,..., f r ( E −1) where E r is the length of rate
r

matching output sequence in code block number r .

6.3.2.4.1.2 CSI part 1

For CSI part 1 transmission on PUSCH not using repetition type B with UL-SCH, the number of coded modulation
′ -part1 , is determined as follows:
symbols per layer for CSI part 1 transmission, denoted as QCSI

𝑁𝑁PUSCH
symb,all −1
′
PUSCH
(𝑂𝑂CSI−1 +𝐿𝐿CSI−1 )∙𝛽𝛽offset ∙∑𝑙𝑙=0 UCI (𝑙𝑙)
𝑀𝑀sc 𝑁𝑁PUSCH −1
symb,all ′
UCI (𝑙𝑙)
𝑄𝑄CSI−1 = min �� 𝐶𝐶𝑈𝑈𝑈𝑈−𝑆𝑆𝑆𝑆𝑆𝑆 −1 � , �𝛼𝛼 ∙ ∑𝑙𝑙=0 𝑀𝑀sc � − 𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴/𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 �
∑𝑟𝑟=0 𝐾𝐾𝑟𝑟

where

- OCSI-1 is the number of bits for CSI part 1;

- if OCSI-1 ≥ 360 , LCSI-1 = 11 ; otherwise LCSI-1 is the number of CRC bits for CSI part 1 determined according to
Clause 6.3.1.2.1;

- β offset
PUSCH
= β offset
CSI -part1
;

- C UL−SCH is the number of code blocks for UL-SCH of the PUSCH transmission;

3GPP
Release 16156T 72 3GPP TS 38.212 V16.6.0 (2021-06)

- 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 scPUSCH is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

Q 'ACK = ∑
l =0
ACK
M sc, rvd ( l ) if the number of HARQ-ACK information bits is no more than 2 bits, where

M ACK
sc, rvd (l ) is the number of reserved resource elements for potential HARQ-ACK transmission in OFDM
symbol l , for l = 0, 1, 2, ..., N symb,
PUSCH
all − 1
, in the PUSCH transmission, defined in Clause 6.2.7; or

′ ′
- 𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴/𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 = 𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴 if both HARQ-ACK and CG-UCI are present on the same PUSCH with UL-SCH, where
′
𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴 is the number of coded modulation symbols per layer for HARQ-ACK and CG-UCI transmitted on the
PUSCH as defined in clause 6.3.2.4.1.5; or
′ ′
- 𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴/𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 = 𝑄𝑄𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 if CG-UCI is present on the same PUSCH with UL-SCH and without HARQ-ACK,
′
where 𝑄𝑄𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 is the number of coded modulation symbols per layer for CG-UCI transmitted on the PUSCH as
defined in clause 6.3.2.4.1.4;

- for any OFDM symbol that carries DMRS of the PUSCH, M scUCI ( l ) = 0 ;

sc ( l ) M scPUSCH − M scPT-RS ( l ) ;
- for any OFDM symbol that does not carry DMRS of the PUSCH, M=
UCI

- α is configured by higher layer parameter scaling.

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 𝑄𝑄CSI-part1 , is determined as follows:
PUSCH
𝑁𝑁PUSCH −1 𝑁𝑁symb,nominal −1

′
(𝑂𝑂CSI-1 + 𝐿𝐿CSI-1 ) ∙ 𝛽𝛽offset
PUSCH
∙ ∑𝑙𝑙=0
symb,nominal
𝑀𝑀sc,nominal
UCI
(𝑙𝑙)
𝑄𝑄CSI-1 = min �� 𝐶𝐶UL-SCH −1 �, �𝛼𝛼 ∙ � 𝑀𝑀sc,nominal
UCI
(𝑙𝑙)�
∑𝑟𝑟=0 𝐾𝐾𝑟𝑟 𝑙𝑙=0
PUSCH
𝑁𝑁symb,actual −1

′ ′
− 𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴/𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 , � 𝑀𝑀sc,actual
UCI
(𝑙𝑙) − 𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴/𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 �
𝑙𝑙=0

where

- 𝑀𝑀sc,nominal
UCI
(𝑙𝑙) is the number of resource elements that can be used for transmission of UCI in OFDM symbol 𝑙𝑙,
for 𝑙𝑙 = 0, 1, 2, ⋯ , 𝑁𝑁symb,nominal
PUSCH
− 1, in the PUSCH transmission assuming a nominal repetition without
segmentation, and 𝑁𝑁symb,nominal is the total number of OFDM symbols in a nominal repetition of the PUSCH,
PUSCH

including all OFDM symbols used for DMRS;

- for any OFDM symbol that carries DMRS of the PUSCH assuming a nominal repetition without
segmentation, 𝑀𝑀sc,nominal
UCI
(𝑙𝑙) = 0;

3GPP
Release 16156T 73 3GPP TS 38.212 V16.6.0 (2021-06)

- for any OFDM symbol that does not carry DMRS of the PUSCH assuming a nominal repetition without
segmentation, 𝑀𝑀sc,nominal
UCI
(𝑙𝑙) = 𝑀𝑀sc
PUSCH
− 𝑀𝑀sc,nominal
PT-RS
(𝑙𝑙) where 𝑀𝑀sc,nominal
PT-RS
(𝑙𝑙) is the number of subcarriers in
OFDM symbol 𝑙𝑙 that carries PTRS, in the PUSCH transmission assuming a nominal repetition without
segmentation;

- 𝑀𝑀sc,actual
UCI
(𝑙𝑙) is the number of resource elements that can be used for transmission of UCI in OFDM symbol 𝑙𝑙, for
𝑙𝑙 = 0, 1, 2, ⋯ , 𝑁𝑁symb,actual
PUSCH
− 1, in the actual repetition of the PUSCH transmission, and 𝑁𝑁symb,actual
PUSCH
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, 𝑀𝑀sc,actual
UCI
(𝑙𝑙) =
0;

- for any OFDM symbol that does not carry DMRS of the actual repetition of the PUSCH transmission,
𝑀𝑀sc,actual
UCI
(𝑙𝑙) = 𝑀𝑀sc
PUSCH
− 𝑀𝑀sc,actual
PT-RS
(𝑙𝑙) where 𝑀𝑀sc,actual
PT-RS
(𝑙𝑙) is the number of subcarriers in OFDM symbol 𝑙𝑙
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.

For CSI part 1 transmission on PUSCH without UL-SCH, the number of coded modulation symbols per layer for CSI
′ -part1 , is determined as follows:
part 1 transmission, denoted as QCSI

if there is CSI part 2 to be transmitted on the PUSCH,

  ( OCSI-1 + LCSI-1 ) ⋅ β offset  symb,all

 
−1
PUSCH


PUSCH N
′  , ∑ M sc ( l ) − QACK
′ 
UCI
QCSI-1 min  

 R ⋅ Qm  l =0 

else
PUSCH
Nsymb,all −1

= ′
QCSI-1 ∑
l =0
M scUCI ( l ) − QACK
′

end if

where

- OCSI-1 is the number of bits for CSI part 1;

- if OCSI-1 ≥ 360 , LCSI-1 = 11 ; otherwise LCSI-1 is the number of CRC bits for CSI part 1 determined according to
Clause 6.3.1.2.1;

- β offset
PUSCH
= β offset
CSI -part1
;

- M scPUSCH is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

- M scPT-RS ( l ) 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
PUSCH
Nsymb,all −1

number of HARQ-ACK information bits is more than 2, and Q 'ACK = ∑

l =0
rvd ( l ) if the number of
M sc,ACK

HARQ-ACK information bits is no more than 2 bits, where M ACK

sc, rvd (l ) is the number of reserved resource

3GPP
Release 16156T 74 3GPP TS 38.212 V16.6.0 (2021-06)

elements for potential HARQ-ACK transmission in OFDM symbol l , for l = 0, 1, 2, ..., N symb,
PUSCH
all − 1
, in the
PUSCH transmission, defined in Clause 6.2.7;

- for any OFDM symbol that carries DMRS of the PUSCH, M scUCI ( l ) = 0 ;

sc ( l ) M scPUSCH − M scPT-RS ( l ) ;
- for any OFDM symbol that does not carry DMRS of the PUSCH, M=
UCI

- R is the code rate of the PUSCH, determined according to Clause 6.1.4.1 of [6, TS38.214];
- Qm is the modulation order of the PUSCH.

The input bit sequence to rate matching is d r 0 , d r1 , d r 2 , d r 3 ,..., d r ( N −1) 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'CSI,1 ⋅Qm .

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

matching output sequence in code block number r .

6.3.2.4.1.3 CSI part 2

For CSI part 2 transmission on PUSCH not using repetition type B with UL-SCH, the number of coded modulation
′ -part2 , is determined as follows:
symbols per layer for CSI part 2 transmission, denoted as QCSI

𝑁𝑁PUSCH
symb,all −1
′
PUSCH
(𝑂𝑂CSI−2 +𝐿𝐿CSI−2 )∙𝛽𝛽offset ∙∑𝑙𝑙=0 UCI (𝑙𝑙)
𝑀𝑀sc 𝑁𝑁PUSCH −1
symb,all ′ ′
UCI (𝑙𝑙)
𝑄𝑄CSI−2 = min �� 𝐶𝐶𝑈𝑈𝑈𝑈−𝑆𝑆𝑆𝑆𝑆𝑆 −1 � , �𝛼𝛼 ∙ ∑𝑙𝑙=0 𝑀𝑀sc � − 𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴/𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 − 𝑄𝑄CSI−1 �
∑𝑟𝑟=0 𝐾𝐾𝑟𝑟

where

- OCSI-2 is the number of bits for CSI part 2;

- if OCSI-2 ≥ 360 , LCSI-2 = 11 ; otherwise LCSI-2 is the number of CRC bits for CSI part 2 determined according to
Clause 6.3.1.2.1;

- β offset
PUSCH
= β offset
CSI-part2
;

- C UL−SCH is the number of code blocks for UL-SCH of the PUSCH transmission;

3GPP
Release 16156T 75 3GPP TS 38.212 V16.6.0 (2021-06)

- M scPUSCH is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

- M scPT-RS ( l ) is the number of subcarriers in OFDM symbol l that carries PTRS, in the PUSCH transmission;
′ ′
- 𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴/𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 = 𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴 if HARQ-ACK is present for transmission on the same PUSCH with UL-SCH and without
′
CG-UCI, where 𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴 is the number of coded modulation symbols per layer for HARQ-ACK transmitted on the
PUSCH as defined in clause 6.3.2.4.1.1 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; or
′ ′
- 𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴/𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 = 𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴 if both HARQ-ACK and CG-UCI are present on the same PUSCH with UL-SCH, where
′
𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴 is the number of coded modulation symbols per layer for HARQ-ACK and CG-UCI transmitted on the
PUSCH as defined in clause 6.3.2.4.1.5; or
′ ′
- 𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴/𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 = 𝑄𝑄𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 if CG-UCI is present on the same PUSCH with UL-SCH and without HARQ-ACK,
′
where 𝑄𝑄𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 is the number of coded modulation symbols per layer for CG-UCI transmitted on the PUSCH as
defined in clause 6.3.2.4.1.4;

- Q 'CSI-1 is the number of coded modulation symbols per layer for CSI part 1 transmitted on the PUSCH;

- for any OFDM symbol that carries DMRS of the PUSCH, M scUCI ( l ) = 0 ;

sc ( l ) M scPUSCH − M scPT-RS ( l ) .
- for any OFDM symbol that does not carry DMRS of the PUSCH, M=UCI

- α is configured by higher layer parameter scaling.

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 𝑄𝑄CSI-part2 , is determined as follows:
PUSCH
𝑁𝑁PUSCH −1 𝑁𝑁symb,nominal −1

′
(𝑂𝑂CSI-2 + 𝐿𝐿CSI-2 ) ∙ 𝛽𝛽offset
PUSCH
∙ ∑𝑙𝑙=0
symb,nominal
𝑀𝑀sc,nominal
UCI
(𝑙𝑙)
𝑄𝑄CSI-2 = min �� 𝐶𝐶UL-SCH −1 �, �𝛼𝛼 ∙ � 𝑀𝑀sc,nominal
UCI
(𝑙𝑙)�
∑𝑟𝑟=0 𝐾𝐾𝑟𝑟 𝑙𝑙=0
PUSCH
𝑁𝑁symb,actual −1

′ ′ ′ ′
− 𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴/𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 − 𝑄𝑄CSI-1 , � 𝑀𝑀sc,actual
UCI
(𝑙𝑙) − 𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴/𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 − 𝑄𝑄CSI-1 �
𝑙𝑙=0

where

- 𝑀𝑀sc,nominal
UCI
(𝑙𝑙) is the number of resource elements that can be used for transmission of UCI in OFDM symbol 𝑙𝑙,
for 𝑙𝑙 = 0, 1, 2, ⋯ , 𝑁𝑁symb,nominal
PUSCH
− 1, in the PUSCH transmission assuming a nominal repetition without
segmentation, and 𝑁𝑁symb,nominal
PUSCH
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
segmentation, 𝑀𝑀sc,nominal
UCI
(𝑙𝑙) = 0;

3GPP
Release 16156T 76 3GPP TS 38.212 V16.6.0 (2021-06)

- for any OFDM symbol that carries DMRS of the actual repetition of the PUSCH transmission, 𝑀𝑀sc,actual
UCI
(𝑙𝑙) =
0;

- and all the other notations in the formula are defined the same as for PUSCH not using repetition type B.

For CSI part 2 transmission on PUSCH without UL-SCH, the number of coded modulation symbols per layer for CSI
′ -part2 , is determined as follows:
part 2 transmission, denoted as QCSI

PUSCH
Nsymb,all −1

=′
QCSI-2 ∑
l =0
M scUCI ( l ) − QACK
′ − QCSI-1
′

where

- M scPUSCH is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;

- M scPT-RS ( l ) 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;

- Q 'CSI-1 is the number of coded modulation symbols per layer for CSI part 1 transmitted on the PUSCH;

- for any OFDM symbol that carries DMRS of the PUSCH, M scUCI ( l ) = 0 ;

sc ( l ) M scPUSCH − M scPT-RS ( l ) .
- for any OFDM symbol that does not carry DMRS of the PUSCH, M=
UCI

The input bit sequence to rate matching is d r 0 , d r1 , d r 2 , d r 3 ,..., d r ( N −1) where

- C UCI is the number of code blocks for UCI determined according to Clause 5.2.1;

3GPP
Release 16156T 77 3GPP TS 38.212 V16.6.0 (2021-06)

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

- Qm is the modulation order of the PUSCH;

- EUCI = N L ⋅ Q'CSI,2 ⋅Qm .

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

matching output sequence in code block number r .

6.3.2.4.1.4 CG-UCI

For CG-UCI transmission on PUSCH with UL-SCH, the number of coded modulation symbols per layer for CG-UCI
′
transmission, denoted as 𝑄𝑄CG−UCI , is determined as follows:

𝑁𝑁PUSCH
symb,all −1
′
PUSCH
(𝑂𝑂CG−UCI +𝐿𝐿CG−UCI )∙𝛽𝛽offset ∙∑𝑙𝑙=0 UCI (𝑙𝑙)
𝑀𝑀sc 𝑁𝑁PUSCH −1
symb,all UCI (𝑙𝑙)
𝑄𝑄CG−UCI = min �� 𝐶𝐶𝑈𝑈𝑈𝑈−𝑆𝑆𝑆𝑆𝑆𝑆 −1 � , �𝛼𝛼 ∙ ∑𝑙𝑙=𝑙𝑙0
𝑀𝑀sc ��
∑𝑟𝑟=0 𝐾𝐾𝑟𝑟

where

- 𝑂𝑂𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 is the number of CG-UCI bits;

- 𝐿𝐿CG−UCI is the number of CRC bits for CG-UCI determined according to Clause 6.3.1.2.1;
PUSCH CG−UCI
- 𝛽𝛽offset = 𝛽𝛽offset ;

- 𝐶𝐶𝑈𝑈𝑈𝑈−𝑆𝑆𝑆𝑆𝑆𝑆 is the number of code blocks for UL-SCH of the PUSCH transmission;

- 𝐾𝐾𝑟𝑟 is the r-th code block size for UL-SCH of the PUSCH transmission;
PUSCH
- 𝑀𝑀sc is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers;
PT−RS (𝑙𝑙)
- 𝑀𝑀sc is the number of subcarriers in OFDM symbol l that carries PTRS, in the PUSCH transmission;
UCI (𝑙𝑙)
- 𝑀𝑀sc is the number of resource elements that can be used for transmission of UCI in OFDM symbol l, for
PUSCH PUSCH
𝑙𝑙=0,1,2,…, 𝑁𝑁symb,all − 1, in the PUSCH transmission and 𝑁𝑁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, 𝑀𝑀sc = 0;
UCI (𝑙𝑙) PUSCH PT−RS (𝑙𝑙);
- for any OFDM symbol that does not carry DMRS of the PUSCH, 𝑀𝑀sc = 𝑀𝑀sc − 𝑀𝑀sc

- 𝛼𝛼 is configured by higher layer parameter scaling;

- 𝑙𝑙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.

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

Rate matching is performed according to Clause 5.4.1 by setting 𝐼𝐼𝐵𝐵𝐵𝐵𝐵𝐵 = 1 and the rate matching output sequence
length to 𝐸𝐸𝑟𝑟 = ⌊𝐸𝐸UCI ⁄𝐶𝐶UCI ⌋, where

- 𝐶𝐶UCI is the number of code blocks for UCI determined according to Clause 5.2.1;

- 𝑁𝑁𝐿𝐿 is the number of transmission layers of the PUSCH;

- 𝑄𝑄𝑚𝑚 is the modulation order of the PUSCH;

′
- 𝐸𝐸𝑈𝑈𝑈𝑈𝑈𝑈 = 𝑁𝑁𝐿𝐿 ∙ 𝑄𝑄𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 ∙ 𝑄𝑄𝑚𝑚 .

The output bit sequence after rate matching is denoted as 𝑓𝑓𝑟𝑟0 , 𝑓𝑓𝑟𝑟1 , 𝑓𝑓𝑟𝑟2 , … , 𝑓𝑓𝑟𝑟(𝐸𝐸𝑟𝑟 −1) where 𝐸𝐸𝑟𝑟 is the length of rate
matching output sequence in code block number r.

3GPP
Release 16156T 78 3GPP TS 38.212 V16.6.0 (2021-06)

6.3.2.4.1.5 HARQ-ACK and CG-UCI

For HARQ-ACK and CG-UCI transmission on PUSCH with UL-SCH, the number of coded modulation symbols per
′
layer for HARQ-ACK and CG-UCI transmission, denoted as 𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴 , is determined as follows:

𝑁𝑁PUSCH
symb,all −1
′
PUSCH
(𝑂𝑂ACK +𝑂𝑂𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 +𝐿𝐿ACK )∙𝛽𝛽offset ∙∑𝑙𝑙=0 UCI (𝑙𝑙)
𝑀𝑀sc 𝑁𝑁PUSCH −1
symb,all UCI (𝑙𝑙)
𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴 = min �� 𝐶𝐶
𝑈𝑈𝑈𝑈−𝑆𝑆𝑆𝑆𝑆𝑆 −1 � , �𝛼𝛼 ∙ ∑𝑙𝑙=𝑙𝑙0
𝑀𝑀sc ��
∑𝑟𝑟=0 𝐾𝐾𝑟𝑟

where

- 𝑂𝑂ACK is the number of HARQ-ACK bits;

- 𝑂𝑂𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 is the number of CG-UCI bits;

- if 𝑂𝑂ACK + 𝑂𝑂CG−UCI > 360, 𝐿𝐿ACK = 11; otherwise 𝐿𝐿ACK is the number of CRC bits for HARQ-ACK and CG-
UCI determined according to Clause 6.3.1.2.1;
PUSCH HARQ−ACK
- 𝛽𝛽offset = 𝛽𝛽offset ;

- 𝐶𝐶𝑈𝑈𝑈𝑈−𝑆𝑆𝑆𝑆𝑆𝑆 is the number of code blocks for UL-SCH of the PUSCH transmission;

- 𝛼𝛼 is configured by higher layer parameter scaling;

- 𝑙𝑙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.

- 𝐶𝐶UCI is the number of code blocks for UCI determined according to Clause 5.2.1;

- 𝑁𝑁𝐿𝐿 is the number of transmission layers of the PUSCH;

- 𝑄𝑄𝑚𝑚 is the modulation order of the PUSCH;

′
- 𝐸𝐸𝑈𝑈𝑈𝑈𝑈𝑈 = 𝑁𝑁𝐿𝐿 ∙ 𝑄𝑄𝐴𝐴𝐴𝐴𝐴𝐴 ∙ 𝑄𝑄𝑚𝑚 .

6.3.2.4.2 UCI encoded by channel coding of small block lengths

6.3.2.4.2.1 HARQ-ACK

For HARQ-ACK transmission on PUSCH, the number of coded modulation symbols per layer for HARQ-ACK
′ , is determined according to Clause 6.3.2.4.1.1, by setting the number of CRC bits
transmission, denoted as QACK
L =0.

3GPP
Release 16156T 79 3GPP TS 38.212 V16.6.0 (2021-06)

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 ⋅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 , f1 , f 2 ,..., f E −1 .

6.3.2.4.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,
′ , is determined according to Clause 6.3.2.4.1.2, by setting the number of CRC bits L = 0 .
denoted as QCSI,1

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 , f1 , f 2 ,..., f E −1 .

6.3.2.4.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,
′ , is determined according to Clause 6.3.2.4.1.3, by setting the number of CRC bits L = 0 .
denoted as QCSI,2

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.

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

6.3.2.4.2.4 CG-UCI

For CG-UCI transmission on PUSCH, the number of coded modulation symbols per layer for CG-UCI transmission,
′
denoted as 𝑄𝑄𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 , is determined according to Clause 6.3.2.4.1.4, by setting the number of CRC bits 𝐿𝐿CG−UCI = 0.

The input bit sequence to rate matching is 𝑑𝑑0 , 𝑑𝑑1 , 𝑑𝑑2 , … , 𝑑𝑑𝑁𝑁−1 .

Rate matching is performed according to Clause 5.4.3, by setting the rate matching output sequence length
′
𝐸𝐸 = 𝑁𝑁𝐿𝐿 ∙ 𝑄𝑄𝐶𝐶𝐶𝐶−𝑈𝑈𝑈𝑈𝑈𝑈 ∙ 𝑄𝑄𝑚𝑚 , where

- 𝑁𝑁𝐿𝐿 is the number of transmission layers of the PUSCH;

- 𝑄𝑄𝑚𝑚 is the modulation order of the PUSCH.

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

6.3.2.4.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 𝑄𝑄ACK , is determined according to Clause 6.3.2.4.1.5, by setting the number
of CRC bits 𝐿𝐿ACK = 0.

3GPP
Release 16156T 80 3GPP TS 38.212 V16.6.0 (2021-06)

The input bit sequence to rate matching is 𝑑𝑑0 , 𝑑𝑑1 , 𝑑𝑑2 , … , 𝑑𝑑𝑁𝑁−1 .

Rate matching is performed according to Clause 5.4.3, by setting the rate matching output sequence length 𝐸𝐸 = 𝑁𝑁𝐿𝐿 ∙
′
𝑄𝑄ACK ∙ 𝑄𝑄𝑚𝑚 , where

- 𝑁𝑁𝐿𝐿 is the number of transmission layers of the PUSCH;

- 𝑄𝑄𝑚𝑚 is the modulation order of the PUSCH.

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

6.3.2.5 Code block concatenation

Code block concatenation is performed according to Clause 6.3.1.5, except that the values of E UCI and C UCI given in
Clause 6.3.2.4.1.

6.3.2.6 Multiplexing of coded UCI bits to PUSCH

The coded UCI bits are multiplexed onto PUSCH according to the procedures in Clause 6.2.7.

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

a0 , a1 , a2 , a3 ,..., a A −1 , where A is the payload size
Denote the bits in a transport block delivered to layer 1 by
generated by higher layers. The lowest order information bit a0 is mapped to the most significant bit of the transport
block as defined in Clause 6.1.1 of [8, TS 38.321].

Generate the following additional timing related PBCH payload bits a A , a A +1 , a A +2 , a A +3 ,..., a A +7 , where:

- 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 is the half frame bit aHRF ;

- if 𝐿𝐿𝑚𝑚𝑚𝑚𝑚𝑚 = 10 as defined in Clause 4.1 of [5, TS38.213],

𝑎𝑎�𝐴𝐴̅+5 is the MSB of 𝑘𝑘SSB as defined in Clause 7.4.3.1 of [4, TS 38.211].

𝑎𝑎�𝐴𝐴̅+6 is reserved.

𝑎𝑎�𝐴𝐴̅+7 is the MSB of candidate SS/PBCH block index.

- else if 𝐿𝐿𝑚𝑚𝑚𝑚𝑚𝑚 = 20 as defined in Clause 4.1 of [5, TS38.213],

𝑎𝑎�𝐴𝐴̅+5 is the MSB of 𝑘𝑘SSB as defined in Clause 7.4.3.1 of [4, TS 38.211].

3GPP
Release 16156T 81 3GPP TS 38.212 V16.6.0 (2021-06)

𝑎𝑎�𝐴𝐴̅+6 , 𝑎𝑎�𝐴𝐴̅+7 are the 5th and 4th bits of the candidate SS/PBCH block index, respectively.

- else if 𝐿𝐿𝑚𝑚𝑚𝑚𝑚𝑚 = 64 as defined in Clause 4.1 of [5, TS38.213],

𝑎𝑎�𝐴𝐴̅+5 , 𝑎𝑎�𝐴𝐴̅+6 , 𝑎𝑎�𝐴𝐴̅+7 are the 6th, 5th, and 4th bits of the candidate SS/PBCH block index, respectively.

- else

𝑎𝑎�𝐴𝐴̅+5 is the MSB of 𝑘𝑘SSB as defined in Clause 7.4.3.1 of [4, TS 38.211].

𝑎𝑎�𝐴𝐴̅+6 , 𝑎𝑎�𝐴𝐴̅+7 are reserved.

- end if

Let A = A + 8 ; jSFN = 0 ; jHRF = 10 ; jSSB = 11 ; jother = 14 ;

for i = 0 to A − 1

if ai is an SFN bit

aG ( jSFN ) = ai ;

jSFN = jSFN + 1 ;

elseif ai is the half radio frame bit

aG ( jHRF ) = ai

elseif A + 5 ≤ i ≤ A + 7

aG ( jSSB ) = ai ;

jSSB = jSSB + 1 ;

else

aG ( jOther ) = ai ;

jOther = jOther + 1 ;

end if

end for

where 𝐿𝐿𝑚𝑚𝑚𝑚𝑚𝑚 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

3GPP
Release 16156T 82 3GPP TS 38.212 V16.6.0 (2021-06)

7.1.2 Scrambling
For PBCH transmission in a frame, the bit sequence a 0 , a1 , a 2 , a 3 ,..., 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

if ai 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

The scrambling sequence c(i ) is given by Clause 5.2.1of [4, TS38.211] and initialized with cinit = N ID
cell
at the start
of each SFN satisfying mod(SFN ,8) = 0 ; M = A − 3 for 𝐿𝐿𝑚𝑚𝑚𝑚𝑚𝑚 = 4 or 𝐿𝐿𝑚𝑚𝑚𝑚𝑚𝑚 = 8, 𝑀𝑀 = 𝐴𝐴 − 4 for 𝐿𝐿𝑚𝑚𝑚𝑚𝑚𝑚 = 10,
𝑀𝑀 = 𝐴𝐴 − 5 for 𝐿𝐿𝑚𝑚𝑚𝑚𝑚𝑚 = 20, and M = A − 6 for 𝐿𝐿𝑚𝑚𝑚𝑚𝑚𝑚 = 64, where 𝐿𝐿𝑚𝑚𝑚𝑚𝑚𝑚 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 p 0 , p1 , p 2 , p 3 ,..., 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 g CRC24C (D ) , resulting in the sequence b0 , b1 , b2 , b3 ,..., b B −1 , where B = A + L .

The bit sequence b0 , b1 , b2 , b3 ,..., b B −1 is the input bit sequence c0 , c1 , c 2 , c3 ,..., c K −1 to the channel encoder, where
ci = bi for i = 0, 1, ..., B − 1 and K = B .

3GPP
Release 16156T 83 3GPP TS 38.212 V16.6.0 (2021-06)

7.1.4 Channel coding

Information bits are delivered to the channel coding block. They are denoted by c0 , c1 , c 2 , c3 ,..., 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 nmax = 9 , I IL = 1 ,
nPC = 0 , and nPC
wm
= 0.

After encoding the bits are denoted by d 0 , d1 , d 2 , d 3 ,..., d N −1 , where N is the number of coded bits.

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 , f1 , 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).

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 g CRC24A (D ) if A > 3824 ; and by setting L to 16 bits and using the generator
polynomial g CRC16 (D ) otherwise.

The bits after CRC attachment are denoted by b0 , b1 , b2 , b3 ,..., b B −1 , where B = A + L .

7.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
5.1.3.1 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 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 b0 , b1 , b2 , b3 ,..., b B −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.

3GPP
Release 16156T 84 3GPP TS 38.212 V16.6.0 (2021-06)

7.2.4 Channel coding

After encoding the bits are denoted by d r 0 , d r1 , d r 2 , d r 3 ,..., d r ( N −1) , where the values of N r is given in Clause 5.3.2.
r

7.2.5 Rate matching

After rate matching, the bits are denoted by f r 0 , f r1 , f r 2 , f r 3 ,..., f r ( E −1) , where E r is the number of rate matched bits for
r

code block number r.

7.2.6 Code block concatenation

The input bit sequence for the code block concatenation block are the sequences f r 0 , f r1 , f r 2 , f r 3 ,..., f r ( E −1) , for
r

r = 0,..., C − 1 and where E r is the number of rate matched bits for the r -th code block.
Code block concatenation is performed according to Clause 5.5.

The bits after code block concatenation are denoted by g 0 , g1 , g 2 , g 3 ,..., g G −1 , where G is the total number of coded
bits 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 16156T 85 3GPP TS 38.212 V16.6.0 (2021-06)

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 PDSCH in one cell, and/or triggering one
1_1
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
3_0 Scheduling of NR sidelink in one cell
3_1 Scheduling of LTE sidelink in one cell

The fields defined in the DCI formats below are mapped to the information bits a0 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
the first field mapped to the lowest order information bit a0 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.
the most significant bit of the first field is mapped to a0 .

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 7.3.1.0 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.

7.3.1.0 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:

Step 0:
UL,BWP
- Determine DCI format 0_0 monitored in a common search space according to clause 7.3.1.1.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 7.3.1.2.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.

3GPP
Release 16156T 86 3GPP TS 38.212 V16.6.0 (2021-06)

- 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:

- Determine DCI format 0_0 monitored in a UE-specific search space according to clause 7.3.1.1.1 where
UL,BWP
N RB is the size of the active UL bandwidth part.

- Determine DCI format 1_0 monitored in a UE-specific search space according to clause 7.3.1.2.1 where
DL,BWP
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 7.3.1.1.2.

- Determine DCI format 1_1 monitored in a UE-specific search space according to clause 7.3.1.2.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.

Step 2A:

- Determine DCI format 0_2 monitored in a UE-specific search space according to clause 7.3.1.1.3.

- Determine DCI format 1_2 monitored in a UE-specific search space according to clause 7.3.1.2.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:

3GPP
Release 16156T 87 3GPP TS 38.212 V16.6.0 (2021-06)

- 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 7.3.1.2.1 where
DL,BWP
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.

- Determine DCI format 0_0 monitored in a UE-specific search space according to clause 7.3.1.1.1 where
UL,BWP
N 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:

- 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

3GPP
Release 16156T 88 3GPP TS 38.212 V16.6.0 (2021-06)

- 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.

7.3.1.0.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 7.3.1.0. 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 7.3.1.0.

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.

7.3.1.1 DCI formats for scheduling of PUSCH

7.3.1.1.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:

- log 2 ( N RBUL,BWP ( N RBUL,BWP + 1) / 2) bits if neither of the higher layer parameters useInterlacePUCCH-PUSCH
in BWP-UplinkCommon and useInterlacePUCCH-PUSCH in BWP-UplinkDedicated is configured, where
UL,BWP
N RB is defined in clause 7.3.1.0

3GPP
Release 16156T 89 3GPP TS 38.212 V16.6.0 (2021-06)

- 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],
where N 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

- log 2 ( N RBUL,BWP ( N RBUL,BWP + 1) / 2) − N UL_hop bits provide the frequency domain resource allocation
according to Clause 6.1.2.2.2 of [6, TS 38.214]

- For non-PUSCH hopping with resource allocation type 1:

- log 2 ( N RBUL,BWP ( N RBUL,BWP + 1) / 2) bits provide the frequency domain resource allocation according to
Clause 6.1.2.2.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 6.1.2.2.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 6.1.2.2.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
BWP BWP
𝑁𝑁RB-set,UL �𝑁𝑁RB-set,UL +1� BWP
�log 2 � �� where 𝑁𝑁RB-set,UL is the number of RB sets contained in the active UL BWP as
2
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 6.1.2.1 of [6, TS 38.214]

- Frequency hopping flag – 1 bit according to Table 7.3.1.1.1-3, as defined in Clause 6.3 of [6, TS 38.214]

- Modulation and coding scheme – 5 bits as defined in Clause 6.1.4.1 of [6, TS 38.214]

- New data indicator – 1 bit

- Redundancy version – 2 bits as defined in Table 7.3.1.1.1-2

- HARQ process number – 4 bits

- 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 7.3.1.1.1-4, or Table 7.3.1.1.1.4A, if ChannelAccessMode-r16 = "semistatic" is provided for operation in a
cell with shared spectrum channel access; 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 7.3.1.1.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.

3GPP
Release 16156T 90 3GPP TS 38.212 V16.6.0 (2021-06)

- 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:

- log 2 ( N RBUL,BWP ( N RBUL,BWP + 1) / 2) bits if the higher layer parameter useInterlacePUCCH-PUSCH in BWP-
UplinkCommon is not configured, where
UL,BWP
- N 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
[5, TS 38.213], where N UL_hop = 1 if N RBUL, BWP
< 50 and N UL_hop = 2 otherwise

- log 2 ( N RBUL,BWP ( N RBUL,BWP + 1) / 2) − N UL_hop bits provide the frequency domain resource allocation
according to Clause 6.1.2.2.2 of [6, TS 38.214]

- For non-PUSCH hopping with resource allocation type 1:

- log 2 ( N RBUL,BWP ( N RBUL,BWP + 1) / 2) bits provide the frequency domain resource allocation according to
Clause 6.1.2.2.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 6.1.2.2.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 6.1.2.2.3 of [6, TS 38.214] if
the subcarrier spacing for the active UL bandwidth part is 15 kHz

- Time domain resource assignment – 4 bits as defined in Clause 6.1.2.1 of [6, TS 38.214]

- Frequency hopping flag – 1 bit according to Table 7.3.1.1.1-3, as defined in Clause 6.3 of [6, TS 38.214]

- Modulation and coding scheme – 5 bits as defined in Clause 6.1.4.1 of [6, TS 38.214]

- New data indicator – 1 bit, reserved

- Redundancy version – 2 bits as defined in Table 7.3.1.1.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).

3GPP
Release 16156T 91 3GPP TS 38.212 V16.6.0 (2021-06)

- If 1 bit, reserved, and the corresponding PUSCH is always on the same UL carrier as the previous
transmission of the same TB

Table 7.3.1.1.1-1: UL/SUL indicator

Value of UL/SUL indicator Uplink

0 The non-supplementary uplink
1 The supplementary uplink

Table 7.3.1.1.1-2: Redundancy version

Value of the Redundancy Value of rvid to be applied

version field
00 0
01 1
10 2
11 3

Table 7.3.1.1.1-3: Frequency hopping indication

Bit field mapped to index PUSCH frequency hopping

0 Disabled
1 Enabled

Table 7.3.1.1.1-4: Channel access type & CP extension for DCI format 0_0 and DCI format 1_0
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 4.2.1.2.3 in
37.213]
1 Type2A-ULChannelAccess 3
defined in [clause 4.2.1.2.1 in
37.213]
2 Type2A-ULChannelAccess 1
defined in [clause 4.2.1.2.1 in
37.213]
3 Type1-ULChannelAccess defined 0
in [clause 4.2.1.1 in 37.213]

Table 7.3.1.1.1-4A: Channel access type & CP extension if ChannelAccessMode-r16 = "semistatic" is

provided
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 No sensing as defined in Clause 0
4.3 in TS 37.213
1 No sensing as defined in Clause 2
4.3 in TS 37.213
2 9us sensing within a 25us interval 0
as defined in Clause 4.3 in TS
37.213
3 - -

3GPP
Release 16156T 92 3GPP TS 38.212 V16.6.0 (2021-06)

7.3.1.1.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

- Carrier indicator – 0 or 3 bits, as defined in Clause 10.1 of [5, TS38.213].

- 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. For a DCI format 0_1 with CRC scrambled by CS-RNTI, the
bit value of 0 indicates activating 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 , 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 7.3.1.1.1-1.

- Bandwidth part indicator – 0, 1 or 2 bits as determined by the number of UL BWPs nBWP,RRC configured by
higher layers, excluding the initial UL bandwidth part. The bitwidth for this field is determined as log 2 (nBWP )
bits, where

- nBWP = nBWP,RRC + 1 if nBWP,RRC ≤ 3 , in which case the bandwidth part indicator is equivalent to the ascending
order of the higher layer parameter BWP-Id;

- otherwise nBWP = nBWP,RRC , in which case the bandwidth part indicator is defined in Table 7.3.1.1.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 6.1.2.2.1 of
[6, TS 38.214],

- log 2 ( N RBUL,BWP ( N RBUL,BWP + 1) / 2) bits if only resource allocation type 1 is configured, or
max ( log ( N
2
UL,BWP
RB
UL,BWP
RB (N + 1) / 2)  , N
RBG )+ 1 bits if resourceAllocation is configured as
'dynamicSwitch'.

3GPP
Release 16156T 93 3GPP TS 38.212 V16.6.0 (2021-06)

- 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
6.1.2.2.1 of [6, TS 38.214].

- For resource allocation type 1, the log 2 ( N RB

UL,BWP UL,BWP
( N 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
38.214], where N 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

- log 2 ( N RBUL,BWP ( N RBUL,BWP + 1) / 2) − N UL_hop bits provide the frequency domain resource allocation
according to Clause 6.1.2.2.2 of [6, TS 38.214]

- For non-PUSCH hopping with resource allocation type 1:

- log 2 ( N RBUL,BWP ( N RBUL,BWP + 1) / 2) bits provide the frequency domain resource allocation according
to Clause 6.1.2.2.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 6.1.2.2.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 6.1.2.2.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.
BWP BWP
𝑁𝑁RB−set,UL �𝑁𝑁RB−set,UL +1� BWP
The value of Y is determined by �log 2 � �� where 𝑁𝑁RB-set,UL is the number of RB
2
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 6.1.2.1 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 6.1.2.1 of [6, TS38.214]. The bitwidth for this field is determined as ⌈log 2 (𝐼𝐼)⌉ 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 (𝐼𝐼)⌉ bits, where I is the number of entries in the
default table.

3GPP
Release 16156T 94 3GPP TS 38.212 V16.6.0 (2021-06)

- 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 7.3.1.1.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 6.1.4.1 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 7.3.1.1.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 7.3.1.1.2-34.

- HARQ process number – 4 bits

- 1st downlink assignment index – 1, 2 or 4 bits:

- 1 bit for semi-static HARQ-ACK codebook;

- 2 bits for dynamic HARQ-ACK codebook, 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 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, 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.

When two HARQ-ACK codebooks are configured for the same serving cell and if higher layer parameter
priorityIndicatorDCI-0-1 is configured, if the bit width of the 2nd downlink assignment index in DCI format
0_1 for one HARQ-ACK codebook is not equal to that of the 2nd 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 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.

- TPC command for scheduled PUSCH – 2 bits as defined in Clause 7.1.1 of [5, TS38.213]

3GPP
Release 16156T 95 3GPP TS 38.212 V16.6.0 (2021-06)

  min{Lmax , N SRS } NSRS  

- SRS resource indicator – log 2 
 ∑    or log 2 (N SRS ) bits, where N SRS is the number of
  k =1  k  
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',

  min{Lmax , N SRS } NSRS  

- log 2  ∑    bits according to Tables 7.3.1.1.2-28/29/30/31 if the higher layer parameter
  k =1  k  
txConfig = nonCodebook, where 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, L max is given by that parameter

- otherwise, L max 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 7.3.1.1.2-32, 7.3.1.1.2-32A and 7.3.1.1.2-32B if the higher layer
parameter txConfig = codebook, where 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'.

- 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 7.3.1.1.2-2 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;

- 4 or 5 bits according to Table 7.3.1.1.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 7.3.1.1.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 7.3.1.1.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 7.3.1.1.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.3.1.1.2-4 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
maxRank and codebookSubset;

- 2 bits according to Table 7.3.1.1.2-4A for 2 antenna ports, if txConfig = codebook, ul-
FullPowerTransmission = fullpowerMode1, transform precoder is disabled, maxRank=2, and
codebookSubset=nonCoherent;

3GPP
Release 16156T 96 3GPP TS 38.212 V16.6.0 (2021-06)

- 1 or 3 bits according to Table7.3.1.1.2-5 for 2 antenna ports, if txConfig = codebook, ul-

- 2 bits according to Table 7.3.1.1.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 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 7.3.1.1.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 an SRS resource set 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.

- Antenna ports – number of bits determined by the following

- 2 bits as defined by Tables 7.3.1.1.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 7.3.1.1.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 n SCID is the scrambling identity for antenna ports defined in [Clause
6.4.1.1.1.2, TS38.211];

- 4 bits as defined by Tables 7.3.1.1.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 7.3.1.1.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 n SCID is the scrambling identity for antenna ports defined in [Clause
6.4.1.1.1.2, TS38.211];

- 3 bits as defined by Tables 7.3.1.1.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 7.3.1.1.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 7.3.1.1.2-16/17/18/19, if transform precoder is disabled, dmrs-Type=2, and

- 5 bits as defined by Tables 7.3.1.1.2-20/21/22/23, if transform precoder is disabled, dmrs-Type=2, and

where the number of CDM groups without data of values 1, 2, and 3 in Tables 7.3.1.1.2-6 to 7.3.1.1.2-23 refers
to CDM groups {0}, {0,1}, and {0, 1,2} respectively.

3GPP
Release 16156T 97 3GPP TS 38.212 V16.6.0 (2021-06)

If a UE is configured with both dmrs-UplinkForPUSCH-MappingTypeA and dmrs-UplinkForPUSCH-

MappingTypeB, the bitwidth of this field equals max { x A , xB } , where x A is the "Antenna ports" bitwidth
derived according to dmrs-UplinkForPUSCH-MappingTypeA and xB is the "Antenna ports" bitwidth derived
according to dmrs-UplinkForPUSCH-MappingTypeB. A number of x A − xB 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 xB .

- SRS request – 2 bits as defined by Table 7.3.1.1.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 7.3.1.1.1-1 and the second and third bits
are defined by Table 7.3.1.1.2-24. This bit field may also indicate the associated CSI-RS according to Clause
6.1.1.2 of [6, TS 38.214].

- 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 7.3.1.1.2-25 and 7.3.1.1.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.

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.

- 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 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. Except for DCI format 0_1 with CRC scrambled
by SP-CSI-RNTI, a UE is not expected to receive a DCI format 0_1 with UL-SCH indicator of "0" and CSI
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 (𝐼𝐼)⌉
bits, where I is the number of entries in the higher layer parameter ul-AccessConfigListDCI-0-1 or in Table
7.3.1.1.1-4A if ChannelAccessMode-r16 = "semistatic" is provided for operation in a cell with shared spectrum
channel access; otherwise 0 bit. One or more entries from Table 7.3.1.1.2-35 are configured by the higher layer
parameter ul-AccessConfigListDCI-0-1.

3GPP
Release 16156T 98 3GPP TS 38.212 V16.6.0 (2021-06)

- 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 6.1.2.1 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 7.3.1.1.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.

- 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 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. 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.

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.

3GPP
Release 16156T 99 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.1.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 7.3.1.1.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 Bit field Bit field
codebookSubset = codebookSubset = codebookSubset=
mapped mapped mapped
fullyAndPartialAndNonCoherent partialAndNonCoherent nonCoherent
to index to index 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 16156T 100 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.1.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 Bit field
codebookSubset = codebookSubset=
mapped mapped
partialAndNonCoherent nonCoherent
to index 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 7.3.1.1.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 Bit field
codebookSubset = codebookSubset=
mapped mapped
partialAndNonCoherent nonCoherent
to index 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 16156T 101 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.1.2-3: Precoding information and number of layers for 4 antenna ports, if transform
precoder is enabled and ul-FullPowerTransmission is either not configured or configured to
fullpowerMode2, or if transform precoder is disabled, maxRank = 1, and ul-FullPowerTransmission is
not configured or configured to fullpowerMode2 or configured to fullpower
Bit field Bit field Bit field
codebookSubset = codebookSubset= codebookSubset=
mapped mapped mapped
fullyAndPartialAndNonCoherent partialAndNonCoherent nonCoherent
to index to index 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 1 layer: TPMI=4 4 1 layer: TPMI=4
… … … …
11 1 layer: TPMI=11 11 1 layer: TPMI=11
12 1 layers: TPMI=12 12-15 reserved
… …
27 1 layers: TPMI=27
28-31 reserved

Table 7.3.1.1.2-3A: Precoding information and number of layers 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 Bit field
codebookSubset= codebookSubset=
mapped mapped
partialAndNonCoherent nonCoherent
to index 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 1 layer: TPMI=13 4 1 layer: TPMI=13
5 1 layer: TPMI=4 5-7 Reserved
… …
13 1 layer: TPMI=12
14 1 layer: TPMI=14
15 1 layer: TPMI=15

Table 7.3.1.1.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 Bit field
codebookSubset =
mapped mapped codebookSubset = nonCoherent
fullyAndPartialAndNonCoherent
to index to 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 16156T 102 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.1.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 7.3.1.1.2-5: Precoding information and number of layers, 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 Bit field
codebookSubset = codebookSubset =
mapped mapped
fullyAndPartialAndNonCoherent nonCoherent
to index 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

Table 7.3.1.1.2-5A: Precoding information and number of layers, for 2 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 mapped to

codebookSubset= nonCoherent
index
0 1 layer: TPMI=0
1 1 layer: TPMI=1
2 1 layer: TPMI=2
3 Reserved

Table 7.3.1.1.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 7.3.1.1.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, n SCID = 0
1 2 0, n SCID = 1
2 2 2, n SCID = 0
3 2 2, n SCID = 1

3GPP
Release 16156T 103 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.1.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
Value Number of DMRS CDM group(s) without data DMRS port(s) Number of front-load symbols
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

Table 7.3.1.1.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
Value Number of DMRS CDM group(s) without data DMRS port(s) Number of front-load symbols
0 2 0, n SCID = 0 1
1 2 0, n SCID = 1 1
2 2 2, n SCID = 0 1
3 2 2, n SCID = 1 1
4 2 0, n SCID = 0 2
5 2 0, n SCID = 1 2
6 2 2, n SCID = 0 2
7 2 2, n SCID = 1 2
8 2 4, n SCID = 0 2
9 2 4, n SCID = 1 2
10 2 6, n SCID = 0 2
11 2 6, n SCID = 1 2
12-15 Reserved Reserved Reserved

Table 7.3.1.1.2-8: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=1, rank
=1
Value Number of DMRS CDM group(s) without data DMRS port(s)
0 1 0
1 1 1
2 2 0
3 2 1
4 2 2
5 2 3
6-7 Reserved Reserved

Table 7.3.1.1.2-9: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=1, rank
=2
Value Number of DMRS CDM group(s) without data DMRS port(s)
0 1 0,1
1 2 0,1
2 2 2,3
3 2 0,2
4-7 Reserved Reserved

3GPP
Release 16156T 104 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.1.2-10: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=1, rank
=3
Value Number of DMRS CDM group(s) without data DMRS port(s)
0 2 0-2
2-7 Reserved Reserved

Table 7.3.1.1.2-11: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=1, rank
=4
Value Number of DMRS CDM group(s) without data DMRS port(s)
0 2 0-3
2-7 Reserved Reserved

Table 7.3.1.1.2-12: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=2, rank
=1
Value Number of DMRS CDM group(s) without data DMRS port(s) Number of front-load symbols
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 7.3.1.1.2-13: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=2, rank
=2
Value Number of DMRS CDM group(s) without data DMRS port(s) Number of front-load symbols
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 7.3.1.1.2-14: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=2, rank
=3
Value Number of DMRS CDM group(s) without data DMRS port(s) Number of front-load symbols
0 2 0-2 1
1 2 0,1,4 2
2 2 2,3,6 2
3-15 Reserved Reserved Reserved

3GPP
Release 16156T 105 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.1.2-15: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=2, rank
=4
Value Number of DMRS CDM group(s) without data DMRS port(s) Number of front-load symbols
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

Table 7.3.1.1.2-16: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=1,

rank=1
Value Number of DMRS CDM group(s) without data DMRS port(s)
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 7.3.1.1.2-17: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=1,

rank=2
Value Number of DMRS CDM group(s) without data DMRS port(s)
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 7.3.1.1.2-18: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=1, rank
=3
Value Number of DMRS CDM group(s) without data DMRS port(s)
0 2 0-2
1 3 0-2
2 3 3-5
3-15 Reserved Reserved

Table 7.3.1.1.2-19: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=1, rank
=4
Value Number of DMRS CDM group(s) without data DMRS port(s)
0 2 0-3
1 3 0-3
2-15 Reserved Reserved

3GPP
Release 16156T 106 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.1.2-20: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=2,

rank=1
Value Number of DMRS CDM group(s) without data DMRS port(s) Number of front-load symbols
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 7.3.1.1.2-21: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=2,

rank=2
Value Number of DMRS CDM group(s) without data DMRS port(s) Number of front-load symbols
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 16156T 107 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.1.2-22: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=2,

rank=3
Value Number of DMRS CDM group(s) without data DMRS port(s) Number of front-load symbols
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 7.3.1.1.2-23: Antenna port(s), transform precoder is disabled, dmrs-Type=2, maxLength=2,

rank=4
Value Number of DMRS CDM group(s) without data DMRS port(s) Number of front-load symbols
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 16156T 108 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.1.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
aperiodicSRS-ResourceTriggerList set serving 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 7.3.1.1.2-25: 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 7.3.1.1.2-26: PTRS-DMRS association for UL PTRS ports 0 and 1

Value of MSB DMRS port Value of LSB DMRS port

st st
1 DMRS port which shares 1 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

3GPP
Release 16156T 109 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.1.2-27: void

Table 7.3.1.1.2-28: SRI indication for non-codebook based PUSCH transmission, Lmax = 1

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
2 2 2 2
3 reserved 3 3

Table 7.3.1.1.2-29: SRI indication for non-codebook based PUSCH transmission, Lmax = 2

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
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 7.3.1.1.2-30: SRI indication for non-codebook based PUSCH transmission, Lmax = 3

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
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

3GPP
Release 16156T 110 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.1.2-31: SRI indication for non-codebook based PUSCH transmission, Lmax = 4

Bit field Bit field Bit field

Table 7.3.1.1.2-32: 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 𝑵𝑵𝑺𝑺𝑺𝑺𝑺𝑺 = 𝟐𝟐

Bit field mapped to index SRI(s), N SRS = 2

0 0
1 1

Table 7.3.1.1.2-32A: SRI indication for codebook based PUSCH transmission, if ul-
FullPowerTransmission = fullpowerMode2 and 𝑵𝑵𝑺𝑺𝑺𝑺𝑺𝑺 = 𝟑𝟑

Bit field mapped to index SRI(s), 𝑁𝑁𝑆𝑆𝑆𝑆𝑆𝑆 = 3

0 0
1 1
2 2
3 Reserved

Table 7.3.1.1.2-32B: SRI indication for codebook based PUSCH transmission, if ul-
FullPowerTransmission = fullpowerMode2 and 𝑵𝑵𝑺𝑺𝑺𝑺𝑺𝑺 = 𝟒𝟒

Bit field mapped to index SRI(s), 𝑁𝑁𝑆𝑆𝑆𝑆𝑆𝑆 = 4

0 0
1 1
2 2
3 3

3GPP
Release 16156T 111 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.1.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 7.3.1.1.2-34: Redundancy version

Value of the Redundancy Value of rvid to be applied

version field
0 0
1 2

3GPP
Release 16156T 112 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.1.2-35: Allowed entries for DCI format 0_1, configured by higher layer parameter ul-
AccessConfigListDCI-0-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 4.2.1.2.3 in 37.213] 0 1
1 Type2C-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213] 0 2
2 Type2C-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213] 0 3
3 Type2C-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213] 0 4
4 Type2C-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213] 2 1
5 Type2C-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213] 2 2
6 Type2C-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213] 2 3
7 Type2C-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213] 2 4
8 Type2B-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213] 0 1
9 Type2B-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213] 0 2
10 Type2B-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213] 0 3
11 Type2B-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213] 0 4
12 Type2B-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213] 2 1
13 Type2B-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213] 2 2
14 Type2B-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213] 2 3
15 Type2B-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213] 2 4
16 Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213] 0 1
17 Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213] 0 2
18 Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213] 0 3
19 Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213] 0 4
20 Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213] 1 1
21 Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213] 1 2
22 Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213] 1 3
23 Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213] 1 4
24 Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213] 3 1
25 Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213] 3 2
26 Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213] 3 3
27 Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213] 3 4
28 Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213] 0 1
29 Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213] 0 2
30 Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213] 0 3
31 Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213] 0 4
32 Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213] 1 1
33 Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213] 1 2
34 Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213] 1 3
35 Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213] 1 4
36 Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213] 2 1
37 Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213] 2 2
38 Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213] 2 3
39 Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213] 2 4
40 Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213] 3 1
41 Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213] 3 2
42 Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213] 3 3
43 Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213] 3 4

7.3.1.1.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].

3GPP
Release 16156T 113 3GPP TS 38.212 V16.6.0 (2021-06)

- 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 (𝑛𝑛𝐵𝐵𝐵𝐵𝐵𝐵 )⌉ bits, where

- 𝑛𝑛𝐵𝐵𝐵𝐵𝐵𝐵 = 𝑛𝑛𝐵𝐵𝐵𝐵𝐵𝐵,𝑅𝑅𝑅𝑅𝑅𝑅 + 1 if 𝑛𝑛𝐵𝐵𝐵𝐵𝐵𝐵,𝑅𝑅𝑅𝑅𝑅𝑅 ≤ 3, in which case the bandwidth part indicator is equivalent to the
ascending order of the higher layer parameter BWP-Id;

- otherwise 𝑛𝑛𝐵𝐵𝐵𝐵𝐵𝐵 = 𝑛𝑛𝐵𝐵𝐵𝐵𝐵𝐵,𝑅𝑅𝑅𝑅𝑅𝑅 , in which case the bandwidth part indicator is defined in Table 7.3.1.1.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:

- 𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅 bits if only resource allocation type 0 is configured, where 𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅 is defined in Clause 6.1.2.2.1 of [6,
TS 38.214]

- �log 2 �𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅,𝐾𝐾1 �𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅,𝐾𝐾1 + 1�/2�� bits if only resource allocation type 1 is configured, or
max� �log 2 �𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅,𝐾𝐾1 �𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅,𝐾𝐾1 + 1�/2��, 𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅 � + 1 bits if resourceAllocationDCI-0-2-r16 is configured as
𝑈𝑈𝑈𝑈,𝐵𝐵𝐵𝐵𝐵𝐵 𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠 𝑈𝑈𝑈𝑈,𝐵𝐵𝐵𝐵𝐵𝐵
'dynamicSwitch', where 𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅,𝐾𝐾1 = ��𝑁𝑁𝑅𝑅𝑅𝑅 + �𝑁𝑁𝑈𝑈𝑈𝑈,𝐵𝐵𝐵𝐵𝐵𝐵 𝑚𝑚𝑚𝑚𝑚𝑚 𝐾𝐾1�� /𝐾𝐾1�, 𝑁𝑁𝑅𝑅𝑅𝑅 is the size of the
𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠
active UL bandwidth part, 𝑁𝑁𝑈𝑈𝑈𝑈,𝐵𝐵𝐵𝐵𝐵𝐵 is defined as in clause 4.4.4.4 of [4, TS 38.211] and 𝐾𝐾1 is given by
higher layer parameter resourceAllocationType1GranularityDCI-0-2. If the higher layer parameter
resourceAllocationType1GranularityDCI-0-2 is not configured, 𝐾𝐾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 𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅 LSBs provide the resource allocation as defined in Clause 6.1.2.2.1
of [6, TS 38.214].

- For resource allocation type 1, the �log 2 �𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅,𝐾𝐾1 �𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅,𝐾𝐾1 + 1�/2�� LSBs provide the resource allocation
as follows:

- For PUSCH hopping with resource allocation type 1:

- 𝑁𝑁𝑈𝑈𝑈𝑈_ℎ𝑜𝑜𝑜𝑜 MSB bits are used to indicate the frequency offset according to Clause 6.3 of [6, TS 38.214],
where 𝑁𝑁𝑈𝑈𝑈𝑈_ℎ𝑜𝑜𝑜𝑜 = 1 if the higher layer parameter frequencyHoppingOffsetListsDCI-0-2 contains two
offset values and 𝑁𝑁𝑈𝑈𝑈𝑈_ℎ𝑜𝑜𝑜𝑜 = 2 if the higher layer parameter frequencyHoppingOffsetListsDCI-0-2
contains four offset values

- �log 2 �𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅,𝐾𝐾1 �𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅,𝐾𝐾1 + 1�/2�� − 𝑁𝑁𝑈𝑈𝑈𝑈_ℎ𝑜𝑜𝑜𝑜 bits provide the frequency domain resource allocation
according to Clause 6.1.2.2.2 of [6, TS 38.214]

- For non-PUSCH hopping with resource allocation type 1:

- �log 2 �𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅,𝐾𝐾1 �𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅,𝐾𝐾1 + 1�/2�� bits provide the frequency domain resource allocation according to
Clause 6.1.2.2.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 6.1.2.1 of [6, TS38.214]. The
bitwidth for this field is determined as ⌈log 2 (𝐼𝐼)⌉ 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:

3GPP
Release 16156T 114 3GPP TS 38.212 V16.6.0 (2021-06)

- 0 bit if the higher layer parameter frequencyHoppingDCI-0-2 is not configured;

- 1 bit according to Table 7.3.1.1.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 6.1.4.1 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, rv id to be applied is 0;

- 1 bit according to Table 7.3.1.2.3-1;

- 2 bits according to Table 7.3.1.1.1-2.

- HARQ process number – 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 or 4 bits otherwise,

- 1st downlink assignment index – 1 or 2 bits:

- 1 bit for semi-static HARQ-ACK codebook;

- 2 bits for dynamic HARQ-ACK codebook.

- 2nd downlink assignment index – 0 or 2 bits

- 2 bits for dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks;

- 0 bit otherwise.

When two HARQ-ACK codebooks are configured for the same serving cell and if higher layer parameter
priorityIndicatorDCI-0-2 is configured, if the bit width of the Downlink assignment index in DCI format 0_2 for
one HARQ-ACK codebook is not equal to that of the 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
Downlink assignment index until the bit width of the 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]
𝑚𝑚𝑚𝑚𝑚𝑚�𝐿𝐿𝑚𝑚𝑚𝑚𝑚𝑚 ,𝑁𝑁𝑆𝑆𝑆𝑆𝑆𝑆,0_2 � 𝑁𝑁𝑆𝑆𝑆𝑆𝑆𝑆,0_2
- SRS resource indicator – �log2 �∑𝑘𝑘=1 � �� or �log 2 𝑁𝑁𝑆𝑆𝑆𝑆𝑆𝑆,0_2 � bits, where 𝑁𝑁𝑆𝑆𝑆𝑆𝑆𝑆,0_2 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 𝑁𝑁𝑆𝑆𝑆𝑆𝑆𝑆,0_2 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' or 'nonCodeBook', respectively
𝑚𝑚𝑚𝑚𝑚𝑚�𝐿𝐿𝑚𝑚𝑚𝑚𝑚𝑚 ,𝑁𝑁𝑆𝑆𝑆𝑆𝑆𝑆,0_2 � 𝑁𝑁𝑆𝑆𝑆𝑆𝑆𝑆,0_2
- �log 2 �∑𝑘𝑘=1 � �� bits according to Tables 7.3.1.1.2-28/29/30/31 if the higher layer
𝑘𝑘
parameter txConfig = nonCodebook, where 𝑁𝑁𝑆𝑆𝑆𝑆𝑆𝑆,0_2 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 'nonCodeBook', where the SRS resource set is composed of
the first 𝑁𝑁𝑆𝑆𝑆𝑆𝑆𝑆,0_2 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 'nonCodeBook', 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, L max is given by that
parameter

3GPP
Release 16156T 115 3GPP TS 38.212 V16.6.0 (2021-06)

- otherwise, L max 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 𝑁𝑁𝑆𝑆𝑆𝑆𝑆𝑆,0_2 � bits according to Tables 7.3.1.1.2-32 if the higher layer parameter txConfig = codebook,
where 𝑁𝑁𝑆𝑆𝑆𝑆𝑆𝑆,0_2 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', where the SRS resource set is composed of the first 𝑁𝑁𝑆𝑆𝑆𝑆𝑆𝑆,0_2 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'.

- 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 7.3.1.1.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;

- 4 or 6 bits according to Table 7.3.1.1.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 7.3.1.1.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.3.1.1.2-4 for 2 antenna ports, if txConfig = codebook, ul-

- 2 bits according to Table 7.3.1.1.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.3.1.1.2-5 for 2 antenna ports, if txConfig = codebook, ul-

- 2 bits according to Table 7.3.1.1.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 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 7.3.1.1.2-4 is used.

3GPP
Release 16156T 116 3GPP TS 38.212 V16.6.0 (2021-06)

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 7.3.1.1.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 n SCID is the scrambling identity for antenna ports defined in Clause 6.4.1.1.1.2, in [4, TS38.211];

- 4 bits as defined by Tables 7.3.1.1.2-7A, if transform precoder is enabled, and dmrs-

- 3 bits as defined by Tables 7.3.1.1.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 7.3.1.1.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 7.3.1.1.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 7.3.1.1.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 7.3.1.1.2-6 to 7.3.1.1.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{𝑥𝑥𝐴𝐴 , 𝑥𝑥𝐵𝐵 }, where 𝑥𝑥𝐴𝐴 is the "Antenna ports" bitwidth derived according to
dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 and 𝑥𝑥𝐵𝐵 is the "Antenna ports" bitwidth derived according to
dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2. 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 𝑥𝑥𝐵𝐵 .

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 7.3.1.1.2-6 to 7.3.1.1.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 7.3.1.1.3-1 if higher layer parameter srs-RequestDCI-0-2 = 1 and for UEs not
configured with supplementaryUplink in ServingCellConfig in the cell;

3GPP
Release 16156T 117 3GPP TS 38.212 V16.6.0 (2021-06)

- 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 7.3.1.1.1-
1 and the second bit is defined by Table 7.3.1.1.3-1;

- 2 bits as defined by Table 7.3.1.1.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 7.3.1.1.1-
1 and the second and third bits are defined by Table 7.3.1.1.2-24;

- 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;

- beta_offset indicator – 0 bit if the higher layer parameter betaOffsets = semiStatic; 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 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. Except for DCI format 0_2 with CRC scrambled
by SP-CSI-RNTI, a UE is not expected to receive a DCI format 0_2 with UL-SCH indicator of "0" and CSI
request of all zero(s).

- 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;

3GPP
Release 16156T 118 3GPP TS 38.212 V16.6.0 (2021-06)

- 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 6.1.2.1 in [6, TS 38.214].

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.

Table 7.3.1.1.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

7.3.1.2 DCI formats for scheduling of PDSCH

7.3.1.2.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 RB

DL,BWP DL,BWP
( N RB + 1) / 2)  bits where N RB
DL,BWP
is given by
clause 7.3.1.0

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 7.3.1.1.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; otherwise 10 bits

Otherwise, all remaining fields are set as follows:

3GPP
Release 16156T 119 3GPP TS 38.212 V16.6.0 (2021-06)

- Time domain resource assignment – 4 bits as defined in Clause 5.1.2.1 of [6, TS 38.214]

- VRB-to-PRB mapping – 1 bit according to Table 7.3.1.2.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 7.3.1.1.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]

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 7.3.1.2.1-1.

- Short Messages – 8 bits, according to Clause 6.5 of [9, TS38.331]. If only the scheduling information for Paging
is carried, this bit field is reserved.

- Frequency domain resource assignment – log 2 ( N RB

DL,BWP DL,BWP
( N RB + 1) / 2)  bits. If only the short message is
carried, this bit field is reserved.
DL,BWP
- N RB is the size of CORESET 0

- Time domain resource assignment – 4 bits as defined in Clause 5.1.2.1 of [6, TS38.214]. If only the short
message is carried, this bit field is reserved.

- VRB-to-PRB mapping – 1 bit according to Table 7.3.1.2.2-5. If only the short message is 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 5.1.3.1-1. If
only the short message is carried, this bit field is reserved.

- TB scaling – 2 bits as defined in Clause 5.1.3.2 of [6, TS38.214]. If only the short message is carried, this bit
field is reserved.

- Reserved bits – 8 bits for operation in a cell with shared spectrum channel access; otherwise 6 bits

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 RB

DL,BWP DL,BWP
( N RB + 1) / 2)  bits
DL,BWP
- N RB is the size of CORESET 0

- Time domain resource assignment – 4 bits as defined in Clause 5.1.2.1 of [6, TS38.214]

- VRB-to-PRB mapping – 1 bit according to Table 7.3.1.2.2-5

- Modulation and coding scheme – 5 bits as defined in Clause 5.1.3 of [6, TS38.214], using Table 5.1.3.1-1

3GPP
Release 16156T 120 3GPP TS 38.212 V16.6.0 (2021-06)

- Redundancy version – 2 bits as defined in Table 7.3.1.1.1-2

- System information indicator – 1 bit as defined in Table 7.3.1.2.1-2

- Reserved bits – 17 bits for operation in a cell with shared spectrum channel access; 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 RB

DL,BWP DL,BWP
( N RB + 1) / 2)  bits

DL,BWP DL,BWP
- N RB is the size of CORESET 0 if CORESET 0 is configured for the cell and N RB 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 5.1.2.1 of [6, TS38.214]

- VRB-to-PRB mapping – 1 bit according to Table 7.3.1.2.2-5

- Modulation and coding scheme – 5 bits as defined in Clause 5.1.3 of [6, TS38.214], using Table 5.1.3.1-1

- TB scaling – 2 bits as defined in Clause 5.1.3.2 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, (18 – A) for operation in a
cell with shared spectrum access, 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 RB

DL,BWP DL,BWP
( N RB + 1) / 2)  bits

DL,BWP
- N RB is the size of CORESET 0

- Time domain resource assignment – 4 bits as defined in Clause 5.1.2.1 of [6, TS38.214]

- VRB-to-PRB mapping – 1 bit according to Table 7.3.1.2.2-5

- Modulation and coding scheme – 5 bits as defined in Clause 5.1.3 of [6, TS38.214], using Table 5.1.3.1-1

- New data indicator – 1 bit

- Redundancy version – 2 bits as defined in Table 7.3.1.1.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]

3GPP
Release 16156T 121 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.2.1-1: Short Message indicator

Bit field Short Message indicator

00 Reserved
01 Only scheduling information for Paging is present in the DCI
10 Only short message is present in the DCI
11 Both scheduling information for Paging and short message are present in the DCI

Table 7.3.1.2.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]

7.3.1.2.2 Format 1_1

DCI format 1_1 is used for the scheduling of 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].

- Bandwidth part indicator – 0, 1 or 2 bits as determined by the number of DL BWPs nBWP,RRC configured by
higher layers, excluding the initial DL bandwidth part. The bitwidth for this field is determined as log 2 (nBWP )
bits, where

- nBWP = nBWP,RRC + 1 if nBWP,RRC ≤ 3 , in which case the bandwidth part indicator is equivalent to the ascending
order of the higher layer parameter BWP-Id;

- otherwise nBWP = nBWP,RRC , in which case the bandwidth part indicator is defined in Table 7.3.1.1.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 5.1.2.2.1 of [6,
TS38.214],

- log 2 ( N RBDL,BWP ( N RBDL,BWP + 1) / 2) bits if only resource allocation type 1 is configured, or
- (
max log 2 ( N RB
DL,BWP DL,BWP
( N RB )
+ 1) / 2)  , N RBG + 1 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 16156T 122 3GPP TS 38.212 V16.6.0 (2021-06)

- For resource allocation type 0, the N RBG LSBs provide the resource allocation as defined in Clause 5.1.2.2.1
of [6, TS 38.214].

- For resource allocation type 1, the log 2 ( N RB

DL,BWP DL,BWP
( N RB + 1) / 2)  LSBs provide the resource allocation
as defined in Clause 5.1.2.2.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, or 4 bits as defined in Clause 5.1.2.1 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; 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;

- 1 bit according to Table 7.3.1.2.2-5 otherwise, only applicable to resource allocation type 1, as defined in
Clause 7.3.1.6 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 5.1.2.3 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 5.1.4.2 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.

For transport block 1:

- Modulation and coding scheme – 5 bits as defined in Clause 5.1.3.1 of [6, TS 38.214]

- New data indicator – 1 bit

- Redundancy version – 2 bits as defined in Table 7.3.1.1.1-2

For transport block 2 (only present if maxNrofCodeWordsScheduledByDCI equals 2):

- Modulation and coding scheme – 5 bits as defined in Clause 5.1.3.1 of [6, TS 38.214]

- New data indicator – 1 bit

- Redundancy version – 2 bits as defined in Table 7.3.1.1.1-2

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.

- HARQ process number – 4 bits

- Downlink assignment index – number of bits as defined in the following

3GPP
Release 16156T 123 3GPP TS 38.212 V16.6.0 (2021-06)

- 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]

- 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.

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, 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.

- One-shot HARQ-ACK request – 0 or 1 bit.

- 1 bit if higher layer parameter pdsch-HARQ-ACK-OneShotFeedback-r16 is configured;

- 0 bit otherwise.

- 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.

3GPP
Release 16156T 124 3GPP TS 38.212 V16.6.0 (2021-06)

- 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 9.1.3.3

- 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.

- Antenna port(s) – 4, 5, or 6 bits as defined by Tables 7.3.1.2.2-1/2/3/4 and Tables 7.3.1.2.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υ −1 shall be determined according to the ordering of DMRS port(s)
given by Tables 7.3.1.2.2-1/2/3/4 or Tables 7.3.1.2.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 7.3.1.2.2-1A/2A/3A/4A; otherwise, it shall use Tables 7.3.1.2.2-1/2/3/4. The UE
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 max { x A , xB } , where x A is the "Antenna ports" bitwidth
derived according to dmrs-DownlinkForPDSCH-MappingTypeA and xB is the "Antenna ports" bitwidth
derived according to dmrs-DownlinkForPDSCH-MappingTypeB. A number of x A − xB 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 xB .

- 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.

- 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.

3GPP
Release 16156T 125 3GPP TS 38.212 V16.6.0 (2021-06)

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.

- 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 (𝐼𝐼)⌉ bits, where I is
the number of entries in the higher layer parameter ul-AccessConfigListDCI-1-1 or in Table 7.3.1.1.1-4A if
ChannelAccessMode-r16 = "semistatic" is provided for operation in a cell with shared spectrum channel access;
otherwise 0 bit. One or more entries from Table 7.3.1.2.2-6 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 7.3.1.1.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

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.

3GPP
Release 16156T 126 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.2.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

Table 7.3.1.2.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

3GPP
Release 16156T 127 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.2.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 16156T 128 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.2.2-2A: Antenna port(s) (1000 + DMRS port), dmrs-Type=1, maxLength=2

3GPP
Release 16156T 129 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.2.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 16156T 130 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.2.2-3A: Antenna port(s) (1000 + DMRS port), dmrs-Type=2, maxLength=1

3GPP
Release 16156T 131 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.2.2-4: Antenna port(s) (1000 + DMRS port), dmrs-Type=2, maxLength=2

3GPP
Release 16156T 132 3GPP TS 38.212 V16.6.0 (2021-06)

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 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

3GPP
Release 16156T 133 3GPP TS 38.212 V16.6.0 (2021-06)

57 2 8,9 2
58-63 Reserved Reserved Reserved

3GPP
Release 16156T 134 3GPP TS 38.212 V16.6.0 (2021-06)

Table 7.3.1.2.2-4A: Antenna port(s) (1000 + DMRS port), dmrs-Type=2, maxLength=2

3GPP
Release 16156T 135 3GPP TS 38.212 V16.6.0 (2021-06)

One codeword: Two Codewords:

3GPP
Release 16156T 136 3GPP TS 38.212 V16.6.0 (2021-06)

57 2 8,9 2
58 2 0,2,3 1
59-63 Reserved Reserved Reserved

Table 7.3.1.2.2-5: VRB-to-PRB mapping

Bit field mapped to index VRB-to-PRB mapping

0 Non-interleaved
1 Interleaved

Table 7.3.1.2.2-6: Allowed entries for DCI format 1_1, configured by higher layer parameter ul-
AccessConfigListDCI-1-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 4.2.1.2.3 in 37.213] 0
1 Type2C-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213] 2
2 Type2B-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213] 0
3 Type2B-ULChannelAccess defined in [clause 4.2.1.2.3 in 37.213] 2
4 Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213] 0
5 Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213] 1
6 Type2A-ULChannelAccess defined in [clause 4.2.1.2.1 in 37.213] 3
7 Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213] 0
8 Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213] 1
9 Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213] 2
10 Type1-ULChannelAccess defined in [clause 4.2.1.1 in 37.213] 3

7.3.1.2.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

in Clause 10.1 of [5, TS38.213].

- 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 ⌈log 2 (𝑛𝑛𝐵𝐵𝐵𝐵𝐵𝐵 )⌉
bits, where

- otherwise 𝑛𝑛𝐵𝐵𝐵𝐵𝐵𝐵 = 𝑛𝑛𝐵𝐵𝐵𝐵𝐵𝐵,𝑅𝑅𝑅𝑅𝑅𝑅 , in which case the bandwidth part indicator is defined in Table 7.3.1.1.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:

- 𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅 bits if only resource allocation type 0 is configured, where 𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅 is defined in Clause 5.1.2.2.1 of [6,
TS 38.214];

- �log 2 �𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅,𝐾𝐾2 �𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅,𝐾𝐾2 + 1�/2�� bits if only resource allocation type 1 is configured, or
max� �log 2 �𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅,𝐾𝐾2 �𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅,𝐾𝐾2 + 1�/2��, 𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅 � + 1 bits if resourceAllocationDCI-1-2-r16 is configured as
𝐷𝐷𝐷𝐷,𝐵𝐵𝐵𝐵𝐵𝐵 𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠 𝐷𝐷𝐷𝐷,𝐵𝐵𝐵𝐵𝐵𝐵
'dynamicSwitch', where 𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅,𝐾𝐾2 = ��𝑁𝑁𝑅𝑅𝑅𝑅 + �𝑁𝑁𝐷𝐷𝐷𝐷,𝐵𝐵𝐵𝐵𝐵𝐵 𝑚𝑚𝑚𝑚𝑚𝑚 𝐾𝐾2�� /𝐾𝐾2�, 𝑁𝑁𝑅𝑅𝑅𝑅 is the size of the active

3GPP
Release 16156T 137 3GPP TS 38.212 V16.6.0 (2021-06)

𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠
DL bandwidth part, 𝑁𝑁𝐷𝐷𝐷𝐷,𝐵𝐵𝐵𝐵𝐵𝐵 is defined as in clause 4.4.4.4 of [4, TS 38.211] and 𝐾𝐾2 is determined by
higher layer parameter resourceAllocationType1GranularityDCI-1-2. If the higher layer parameter
resourceAllocationType1GranularityDCI-1-2 is not configured, 𝐾𝐾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 𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅 LSBs provide the resource allocation as defined in Clause 5.1.2.2.1
of [6, TS 38.214].

- For resource allocation type 1, the �log 2 �𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅,𝐾𝐾2 �𝑁𝑁𝑅𝑅𝑅𝑅𝑅𝑅,𝐾𝐾2 + 1�/2�� LSBs provide the resource allocation
as defined in Clause 5.1.2.2.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 5.1.2.1 of [6, TS 38.214]. The
bitwidth for this field is determined as ⌈log 2 (𝐼𝐼)⌉ 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 7.3.1.2.2-5 otherwise, only applicable to resource allocation type 1, as defined in
Clause 7.3.1.6 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 5.1.2.3 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 5.1.4.2 of [6, TS 38.214]. The bitwidth for this field is
determined as ⌈log 2 (𝑛𝑛𝑍𝑍𝑍𝑍 + 1)⌉ bits, where 𝑛𝑛𝑍𝑍𝑍𝑍 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 5.1.3.1 of [6, TS 38.214]

- New data indicator – 1 bit

- Redundancy version – 0, 1 or 2 bits determined by higher layer parameter numberOfBitsForRV-DCI-1-2

- If 0 bit is configured, rv id to be applied is 0;

- 1 bit according to Table 7.3.1.2.3-1;

- 2 bits according to Table 7.3.1.1.1-2.

- HARQ process number – 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,

3GPP
Release 16156T 138 3GPP TS 38.212 V16.6.0 (2021-06)

- 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]

- PUCCH resource indicator – 0 or 1 or 2 or 3 bits determined by higher layer parameter

numberOfBitsForPUCCH-ResourceIndicatorDCI-1-2

- 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 (𝐼𝐼)⌉ bits, where I is the number of entries in the higher layer
parameter DL-DataToUL-ACK-DCI-1-2.

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, 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.

- 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 7.3.1.2.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
{𝑝𝑝0 , … , 𝑝𝑝𝑣𝑣−1 } shall be determined according to the ordering of DMRS port(s) given by Tables 7.3.1.2.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 equals max{𝑥𝑥𝐴𝐴 , 𝑥𝑥𝐵𝐵 }, where 𝑥𝑥𝐴𝐴 is the "Antenna
ports" bitwidth derived according to dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 and 𝑥𝑥𝐵𝐵 is the
"Antenna ports" bitwidth derived according to dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2. 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 𝑥𝑥𝐵𝐵 .

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 7.3.1.2.2-1/2/3/4.

- 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,

3GPP
Release 16156T 139 3GPP TS 38.212 V16.6.0 (2021-06)

- 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 7.3.1.1.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 7.3.1.1.1-1 and the second bit is defined by Table 7.3.1.1.3-1;

- 2 bits as defined by Table 7.3.1.1.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 7.3.1.1.1-1 and the second and third bits are defined by Table 7.3.1.1.2-24;

- 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].

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.

Table 7.3.1.2.3-1: Redundancy version

Value of the Redundancy Value of rvid to be applied

version field
0 0
1 3

7.3.1.3 DCI formats for other purposes

7.3.1.3.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.

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,

3GPP
Release 16156T 140 3GPP TS 38.212 V16.6.0 (2021-06)

- 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].

7.3.1.3.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.

7.3.1.3.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.

7.3.1.3.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.

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.

3GPP
Release 16156T 141 3GPP TS 38.212 V16.6.0 (2021-06)

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 7.3.1.1.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 7.3.1.1.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.

7.3.1.3.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.

7.3.1.3.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].

7.3.1.3.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.

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 higher layer parameter
dormancyGroupOutsideActiveTime, where each bit corresponds to one of the SCell group(s) configured by

3GPP
Release 16156T 142 3GPP TS 38.212 V16.6.0 (2021-06)

higher layers parameter dormancyGroupOutsideActiveTime, with MSB to LSB of the bitmap corresponding to
the first to last configured SCell group.

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].

7.3.1.4 DCI formats for scheduling of sidelink

7.3.1.4.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 𝐼𝐼⌉ bits, where I is the number of resource pools for transmission configured by the
higher layer parameter sl-TxPoolScheduling.

- Time gap – 3 bits determined by higher layer parameter sl-DCI-ToSL-Trans, as defined in clause 8.1.2.1 of [6,
TS 38.214]

- HARQ process number – 4 bits as defined in clause 16.4 of [5, TS 38.213]

- New data indicator – 1 bit as defined in clause 16.4 of [5, TS 38.213]

- Lowest index of the subchannel allocation to the initial transmission –�log2 (N SL

subChannel )� bits as defined in
clause 8.1.2.2 of [6, TS 38.214]

- SCI format 1-A fields according to clause 8.3.1.1:

- Frequency resource assignment.

- Time resource assignment.

- PSFCH-to-HARQ feedback timing indicator –�log 2 𝑁𝑁fb_timing � bits, where 𝑁𝑁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 multiple transmit resource pools are provided in sl-TxPoolScheduling, 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.

7.3.1.4.2 Format 3_1

DCI format 3_1 is used for scheduling of LTE PSCCH and LTE PSSCH in one cell.

3GPP
Release 16156T 143 3GPP TS 38.212 V16.6.0 (2021-06)

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, as defined in clause 16.6 of
[5, TS 38.213]

- Carrier indicator –3 bits as defined in 5.3.3.1.9A of [11, TS 36.212].

- 
SL
Lowest index of the subchannel allocation to the initial transmission - log2 ( N subchannel )  bits as defined in
5.3.3.1.9A of [11, TS 36.212].

- Frequency resource location of initial transmission and retransmission, as defined in 5.3.3.1.9A of [11, TS
36.212]

- Time gap between initial transmission and retransmission, as defined in 5.3.3.1.9A of [11, TS 36.212]

- SL index – 2 bits as defined in 5.3.3.1.9A of [11, TS 36.212]

- SL SPS configuration index – 3 bits as defined in clause 5.3.3.1.9A of [11, TS 36.212].

- Activation/release indication – 1 bit as defined in clause 5.3.3.1.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.

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 , a 3 ,..., a A−1 , and
the parity bits by p 0 , p1 , p 2 , p 3 ,..., 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
according to Clause 5.1 by setting L to 24 bits and using the generator polynomial g CRC24C (D ) . The output bit
b0 , b1 , b2 , b3 ,..., bK −1 is

bk = a k for k = 0,1,2,..., A − 1

bk = 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 ,..., x rnti ,15 , where
xrnti , 0 corresponds to the MSB of the RNTI, to form the sequence of bits c0 , c1 , c2 , c3 ,..., cK −1 . The relation between
c k and b k is:

c k = bk for k = 0, 1, 2, …, A + 7

ck = (bk + xrnti ,k − A−8 ) mod 2 for k = A + 8 , A + 9 , A + 10 ,..., A + 23 .

7.3.3 Channel coding

After encoding the bits are denoted by d 0 , d1 , d 2 , d 3 ,..., d N −1 , where N is the number of coded bits.

3GPP
Release 16156T 144 3GPP TS 38.212 V16.6.0 (2021-06)

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 , f1 , 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:

- Rate matching of SL-SCH follows the rate matching according to clause 6.2.5 by setting 𝐼𝐼𝐿𝐿𝐿𝐿𝐿𝐿𝐿𝐿 = 0

- Clause 6.2.7 is replaced by clause 8.2.1

8.2.1 Data and control multiplexing

Denote the coded bits for SL-SCH as g 0𝑆𝑆𝑆𝑆−𝑆𝑆𝑆𝑆𝑆𝑆 , g1𝑆𝑆𝑆𝑆−𝑆𝑆𝑆𝑆𝑆𝑆 , g 2𝑆𝑆𝑆𝑆−𝑆𝑆𝑆𝑆𝑆𝑆 , g 3𝑆𝑆𝑆𝑆−𝑆𝑆𝑆𝑆𝑆𝑆 , ⋯ , g 𝐺𝐺𝑆𝑆𝑆𝑆−𝑆𝑆𝑆𝑆𝑆𝑆
𝑆𝑆𝑆𝑆−𝑆𝑆𝑆𝑆𝑆𝑆 −1 .

Denote the coded bits for the 2nd-stage SCI, as g 0𝑆𝑆𝑆𝑆𝑆𝑆2 , g1𝑆𝑆𝑆𝑆𝑆𝑆2 , g 2𝑆𝑆𝑆𝑆𝑆𝑆2 , g 3𝑆𝑆𝑆𝑆𝑆𝑆2 , ⋯ , g 𝐺𝐺𝑆𝑆𝑆𝑆𝑆𝑆2
𝑆𝑆𝑆𝑆𝑆𝑆2 −1 .

Denote the multiplexed data and control coded bit sequence as g 0 , g1 , ⋯ , g 𝐺𝐺−1 , where G is the total number of coded
bits for transmission.

Assuming that 𝑁𝑁𝐿𝐿 is the number of layers onto which the SL-SCH transport block is mapped, the multiplexed data and
control coded bit sequence g 0 , g1 , ⋯ , g 𝐺𝐺−1 is obtained as follows:
𝑆𝑆𝑆𝑆𝑆𝑆2
Denote 𝑄𝑄𝑚𝑚 is modulation order of the 2nd-stage SCI.

if 𝑁𝑁𝐿𝐿 = 1,

for 𝑖𝑖 = 0 to 𝐺𝐺 𝑆𝑆𝑆𝑆𝑆𝑆2 + 𝐺𝐺 𝑆𝑆𝑆𝑆−𝑆𝑆𝑆𝑆𝑆𝑆 − 1

if 0 ≤ 𝑖𝑖 < 𝐺𝐺 𝑆𝑆𝑆𝑆𝑆𝑆2

g 𝑖𝑖 = g 𝑖𝑖𝑆𝑆𝑆𝑆𝑆𝑆2

end if

if G 𝑆𝑆𝑆𝑆𝑆𝑆2 ≤ 𝑖𝑖 ≤ G 𝑆𝑆𝑆𝑆𝑆𝑆2 + G 𝑆𝑆𝑆𝑆−𝑆𝑆𝑆𝑆𝑆𝑆 − 1

𝑆𝑆𝑆𝑆−𝑆𝑆𝑆𝑆𝑆𝑆
g 𝑖𝑖 = g 𝑖𝑖−𝐺𝐺 𝑆𝑆𝑆𝑆𝑆𝑆2

end if

3GPP
Release 16156T 145 3GPP TS 38.212 V16.6.0 (2021-06)

end for

end if

if 𝑁𝑁𝐿𝐿 = 2,
𝑅𝑅𝑅𝑅
let 𝑀𝑀𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐,𝑆𝑆𝑆𝑆𝑆𝑆2 𝑆𝑆𝑆𝑆𝑆𝑆2
= 𝐺𝐺 𝑆𝑆𝑆𝑆𝑆𝑆2 /𝑄𝑄𝑚𝑚
𝑅𝑅𝑅𝑅
set 𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐 =0
𝑅𝑅𝑅𝑅
for 𝑖𝑖 = 0 to 𝑀𝑀𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐,𝑆𝑆𝑆𝑆𝑆𝑆2 −1

for 𝑣𝑣 = 0 to 𝑁𝑁𝐿𝐿 − 1
𝑆𝑆𝑆𝑆𝑆𝑆2
for 𝑞𝑞 = 0 to 𝑄𝑄𝑚𝑚 −1

if 𝑣𝑣 = 0
𝑆𝑆𝑆𝑆𝑆𝑆2
g 𝑚𝑚𝑅𝑅𝑅𝑅 = g 𝑖𝑖∙𝑄𝑄 𝑆𝑆𝑆𝑆𝑆𝑆2 +𝑞𝑞
𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐 𝑚𝑚

else

g 𝑚𝑚𝑅𝑅𝑅𝑅 = 𝑥𝑥 // placeholder bit

𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐

end if
𝑅𝑅𝑅𝑅 𝑅𝑅𝑅𝑅
𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐 = 𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐 +1

end for

for 𝑖𝑖 = 0 to 𝐺𝐺 𝑆𝑆𝑆𝑆−𝑆𝑆𝑆𝑆𝑆𝑆 − 1

g 𝑚𝑚𝑅𝑅𝑅𝑅 = g 𝑖𝑖𝑆𝑆𝑆𝑆−𝑆𝑆𝑆𝑆𝑆𝑆
𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐

𝑅𝑅𝑅𝑅 𝑅𝑅𝑅𝑅
𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐 = 𝑚𝑚𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐𝑐 +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 𝑎𝑎0 to 𝑎𝑎𝐴𝐴−1 as 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 𝑎𝑎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. the most significant bit of the first field is mapped
to 𝑎𝑎0 .

8.3.1.1 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:

- Priority – 3 bits as specified in clause 5.4.3.3 of [12, TS 23.287] and clause 5.22.1.3.1 of [8, TS 38.321].

3GPP
Release 16156T 146 3GPP TS 38.212 V16.6.0 (2021-06)

N SL SL
subChannel �N subChannel + 1�
- Frequency resource assignment – �log2 ( )� bits when the value of the higher layer
2

subChannel �N subChannel + 1��2N subChannel + 1�

N SL SL SL
parameter sl-MaxNumPerReserve is configured to 2; otherwise �log2 ( )�
6
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].

- 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 𝑁𝑁rsv_period � bits as defined in clause 16.4 of [5, TS 38.213], where
𝑁𝑁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 𝑁𝑁pattern � bits as defined in clause 8.4.1.1.2 of [4, TS 38.211], where 𝑁𝑁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 8.3.1.1-1.

- Beta_offset indicator – 2 bits as provided by higher layer parameter sl-BetaOffsets2ndSCI and Table 8.3.1.1-2.

- Number of DMRS port – 1 bit as defined in Table 8.3.1.1-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 8.1.3.1 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 8.1.3.2 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 higher layer parameter sl-NumReservedBits, with value set to zero.

Table 8.3.1.1-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 Reserved
11 Reserved

Table 8.3.1.1-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

3GPP
Release 16156T 147 3GPP TS 38.212 V16.6.0 (2021-06)

Table 8.3.1.1-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 attachement is performed according to clause 7.3.2 except that scrambling is not performed.

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.

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 𝑎𝑎0 to 𝑎𝑎𝐴𝐴−1 as
follows:

8.4.1.1 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 7.3.1.1.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 8.4.1.1-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].

3GPP
Release 16156T 148 3GPP TS 38.212 V16.6.0 (2021-06)

Table 8.4.1.1-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

8.4.1.2 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:

- HARQ process number – 4 bits.

- New data indicator – 1 bit.

- Redundancy version – 2 bits as defined in Table 7.3.1.1.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.

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 2nd-
′
stage SCI transmission prior to duplication for the 2nd layer if present, denoted as 𝑄𝑄𝑆𝑆𝑆𝑆𝑆𝑆2 , is determined as follows:
𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃
𝑁𝑁𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠 −1
𝑆𝑆𝑆𝑆𝑆𝑆2
′
(𝑂𝑂𝑆𝑆𝑆𝑆𝑆𝑆2 + 𝐿𝐿𝑆𝑆𝑆𝑆𝑆𝑆2 ) ∙ 𝛽𝛽𝑜𝑜𝑜𝑜𝑜𝑜𝑜𝑜𝑜𝑜𝑜𝑜 𝑆𝑆𝑆𝑆𝑆𝑆2
𝑄𝑄𝑆𝑆𝑆𝑆𝑆𝑆2 = min �� 𝑆𝑆𝑆𝑆𝑆𝑆2 ∙ 𝑅𝑅
� , �𝛼𝛼 � 𝑀𝑀𝑠𝑠𝑠𝑠 (𝑙𝑙)�� + γ
𝑄𝑄𝑚𝑚
𝑙𝑙=0

where

- 𝑂𝑂𝑆𝑆𝑆𝑆𝑆𝑆2 is the number of the 2nd-stage SCI bits

- 𝐿𝐿𝑆𝑆𝑆𝑆𝑆𝑆2 is the number of CRC bits for the 2nd-stage SCI, which is 24 bits.
𝑆𝑆𝑆𝑆𝑆𝑆2
- 𝛽𝛽𝑜𝑜𝑜𝑜𝑜𝑜𝑜𝑜𝑜𝑜𝑜𝑜 is indicated in the corresponding 1st-stage SCI.
𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃
- 𝑀𝑀𝑠𝑠𝑠𝑠 (𝑙𝑙) is the scheduled bandwidth of PSSCH transmission, expressed as a number of subcarriers.

- 𝑀𝑀𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃
𝑠𝑠𝑠𝑠 (𝑙𝑙) is the number of subcarriers in OFDM symbol 𝑙𝑙 that carry PSCCH and PSCCH DMRS associated
with the PSSCH transmission.

3GPP
Release 16156T 149 3GPP TS 38.212 V16.6.0 (2021-06)

𝑆𝑆𝑆𝑆𝑆𝑆2
- 𝑀𝑀𝑠𝑠𝑠𝑠 (𝑙𝑙) is the number of resource elements that can be used for transmission of the 2nd-stage SCI in OFDM
𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 𝑠𝑠ℎ 𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃
symbol 𝑙𝑙 , for 𝑙𝑙 = 0,1,2 ⋯ , 𝑁𝑁𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠 − 1 and for 𝑁𝑁𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠 = 𝑁𝑁𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠 − 𝑁𝑁𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠 , in PSSCH transmission,
𝑠𝑠ℎ
where 𝑁𝑁𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠 = sl-lengthSymbols - 2, where sl-lengthSymbols is the number of sidelink symbols within the slot
provided by higher layers as defined in [6, TS 38.214]. If higher layer parameter sl-PSFCH-Period = 2 or 4,
𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃 𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃
𝑁𝑁𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠 = 3 if "PSFCH overhead indication" field of SCI format 1-A indicates "1", and 𝑁𝑁𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠 = 0 otherwise. If
𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃
higher layer parameter sl-PSFCH-Period = 0, 𝑁𝑁𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠 = 0. If higher layer parameter sl-PSFCH-Period is 1,
𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃
𝑁𝑁𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠 = 3.

- 𝑆𝑆𝑆𝑆𝑆𝑆2
𝑀𝑀𝑠𝑠𝑠𝑠 𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃
(𝑙𝑙) = 𝑀𝑀𝑠𝑠𝑠𝑠 (𝑙𝑙) - 𝑀𝑀𝑃𝑃𝑃𝑃𝑃𝑃𝐶𝐶𝐻𝐻
𝑠𝑠𝑠𝑠 (𝑙𝑙)

- γ is the number of vacant resource elements in the resource block to which the last coded symbol of the 2nd-
stage SCI belongs.

- 𝑅𝑅 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 𝑑𝑑0 , 𝑑𝑑1 , 𝑑𝑑2 , 𝑑𝑑3 , ⋯ , 𝑑𝑑𝑁𝑁−1 , where 𝑁𝑁 is the number of coded bits.

Rate matching is performed according to Clause 5.4.1 by setting 𝐼𝐼𝐵𝐵𝐵𝐵𝐵𝐵 = 1.

The output bit sequence after rate matching is denoted as g 0𝑆𝑆𝑆𝑆𝑆𝑆2 , g1𝑆𝑆𝑆𝑆𝑆𝑆2 , g 2𝑆𝑆𝑆𝑆𝑆𝑆2 , g 3𝑆𝑆𝑆𝑆𝑆𝑆2 , ⋯ , g 𝐺𝐺𝑆𝑆𝑆𝑆𝑆𝑆2
𝑆𝑆𝑆𝑆𝑆𝑆2 −1 , where 𝐺𝐺
𝑆𝑆𝑆𝑆𝑆𝑆2
= 𝑄𝑄′𝑆𝑆𝑆𝑆𝑆𝑆2 ∙
𝑆𝑆𝑆𝑆𝑆𝑆2 𝑆𝑆𝑆𝑆𝑆𝑆2
𝑄𝑄𝑚𝑚 and 𝑄𝑄𝑚𝑚 is modulation order of the 2nd-stage SCI. A UE is not expected to have 𝐺𝐺 𝑆𝑆𝑆𝑆𝑆𝑆2 > 4096.

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 16156T 150 3GPP TS 38.212 V16.6.0 (2021-06)

Annex A:
Change history

3GPP
Release 16156T 151 3GPP TS 38.212 V16.6.0 (2021-06)

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 suppport 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 16156T 152 3GPP TS 38.212 V16.6.0 (2021-06)

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 postioning 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

3GPP
Release 16156T 153 3GPP TS 38.212 V16.6.0 (2021-06)

2021-06 RAN#92-e RP-211243 0071 - F Alignment CR for TS 38.212 (post RAN1#105-e) 16.6.0

3GPP

Error Control Coding (2nd Edition), Shu Lin, Daniel J. Costello
No ratings yet
Error Control Coding (2nd Edition), Shu Lin, Daniel J. Costello
1,271 pages
Kim - Artificial Intelligence For 6G (2022) (Kim) (9783030950408) (2022)
100% (3)
Kim - Artificial Intelligence For 6G (2022) (Kim) (9783030950408) (2022)
534 pages
3GPP TS 38.508-1
No ratings yet
3GPP TS 38.508-1
1,317 pages
3GPP TS 38.331
No ratings yet
3GPP TS 38.331
1,328 pages
3GPP TS 23.501
No ratings yet
3GPP TS 23.501
694 pages
3gpp Ts 36.331 - RRC Protocol Specification
No ratings yet
3gpp Ts 36.331 - RRC Protocol Specification
456 pages
3GPP TS 23.501
No ratings yet
3GPP TS 23.501
430 pages
3GPP TS 31.102 V16.2.0
No ratings yet
3GPP TS 31.102 V16.2.0
315 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
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
Chapter 3 2022
100% (1)
Chapter 3 2022
127 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 23.040
No ratings yet
3GPP TS 23.040
216 pages
Mess Bill Month
No ratings yet
Mess Bill Month
401 pages
38104-I20 - Base Station (BS) Radio Transmission and Reception
No ratings yet
38104-I20 - Base Station (BS) Radio Transmission and Reception
377 pages
TS36.300 TNL Address Discovery
No ratings yet
TS36.300 TNL Address Discovery
366 pages
Study On 6G Use Cases Stage 1 Rel 20 1743561996
No ratings yet
Study On 6G Use Cases Stage 1 Rel 20 1743561996
172 pages
3GPP TS 36.331: Technical Specification
No ratings yet
3GPP TS 36.331: Technical Specification
360 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
Compressed Sensing in Radar Signal Processing
No ratings yet
Compressed Sensing in Radar Signal Processing
379 pages
Research: David Deutsch and Chiara Marletto
No ratings yet
Research: David Deutsch and Chiara Marletto
18 pages
d20
No ratings yet
d20
623 pages
Numbering 23003 c90
No ratings yet
Numbering 23003 c90
92 pages
ETSI TS 138 213: 5G NR Physical Layer Procedures For Control (3GPP TS 38.213 Version 16.6.0 Release 16)
No ratings yet
ETSI TS 138 213: 5G NR Physical Layer Procedures For Control (3GPP TS 38.213 Version 16.6.0 Release 16)
190 pages
3GPP TS 23.501
No ratings yet
3GPP TS 23.501
391 pages
Suvra Sekhar Das PHD, Ramjee Prasad PHD - Orthogonal Time Frequency Space Modulation - A Waveform For 6G (River Publishers Series in Communications) - River Publishers (2022)
No ratings yet
Suvra Sekhar Das PHD, Ramjee Prasad PHD - Orthogonal Time Frequency Space Modulation - A Waveform For 6G (River Publishers Series in Communications) - River Publishers (2022)
238 pages
NR Protocol PDF
No ratings yet
NR Protocol PDF
835 pages
3GPP TR 38.811
No ratings yet
3GPP TR 38.811
126 pages
SM PCF Jul2020
No ratings yet
SM PCF Jul2020
197 pages
UNIT IV - Compression
No ratings yet
UNIT IV - Compression
39 pages
38874-g00 Study On Integrated Access and Backhaul
No ratings yet
38874-g00 Study On Integrated Access and Backhaul
111 pages
Log TCap
No ratings yet
Log TCap
28 pages
Jpeg
No ratings yet
Jpeg
36 pages
3GPP TS 36.331: Technical Specification
No ratings yet
3GPP TS 36.331: Technical Specification
216 pages
Cyclic Codes
No ratings yet
Cyclic Codes
94 pages
3GPP Offload
No ratings yet
3GPP Offload
291 pages
3GPP TS 23.682: Technical Specification
No ratings yet
3GPP TS 23.682: Technical Specification
134 pages
Layer 1
No ratings yet
Layer 1
140 pages
3GPP TS 29.503
No ratings yet
3GPP TS 29.503
205 pages
Radio Link Supervision in LTE
100% (3)
Radio Link Supervision in LTE
65 pages
Documento LTE 3gpp TS 36.101
No ratings yet
Documento LTE 3gpp TS 36.101
220 pages
S1 Application Protocol (S1AP)
No ratings yet
S1 Application Protocol (S1AP)
254 pages
3GPP TS 38.306
No ratings yet
3GPP TS 38.306
174 pages
3GPP TS 29.571
No ratings yet
3GPP TS 29.571
100 pages
3GPP TS 23.204: Technical Specification
No ratings yet
3GPP TS 23.204: Technical Specification
59 pages
Unicode CPP PDF
No ratings yet
Unicode CPP PDF
139 pages
3gpp Pathloss
No ratings yet
3gpp Pathloss
98 pages
3GPP TS 36.423
No ratings yet
3GPP TS 36.423
208 pages
Lecture 6
No ratings yet
Lecture 6
6 pages
ETN642 Lec11 ChannelCoding Handouts
No ratings yet
ETN642 Lec11 ChannelCoding Handouts
13 pages
TS 23401-8e0 Rel8 - GPRS Enhancement To LTE
No ratings yet
TS 23401-8e0 Rel8 - GPRS Enhancement To LTE
242 pages
3GPP TS 38.211
No ratings yet
3GPP TS 38.211
97 pages
38340-g50 Backhaul Adaptation Protocol (BAP) Specification
No ratings yet
38340-g50 Backhaul Adaptation Protocol (BAP) Specification
22 pages
Hamming Code
0% (2)
Hamming Code
6 pages
Information Theory, IT Entropy Mutual Information Use in NLP
No ratings yet
Information Theory, IT Entropy Mutual Information Use in NLP
23 pages
3GPP TS 23.003 - GTP
No ratings yet
3GPP TS 23.003 - GTP
100 pages
Mtech Thesis TD1410 2019
No ratings yet
Mtech Thesis TD1410 2019
37 pages
36212-910 - Multiplexing and Channel Coding
No ratings yet
36212-910 - Multiplexing and Channel Coding
60 pages
NR - User Equipment Radio Transmission & Reception
No ratings yet
NR - User Equipment Radio Transmission & Reception
234 pages
36413-922 S1 Application Protocol (S1AP)
No ratings yet
36413-922 S1 Application Protocol (S1AP)
237 pages
Compression PDF
No ratings yet
Compression PDF
27 pages
On The Design Details of SS PBCH Signal Generation and PRACH in 5G-NR
No ratings yet
On The Design Details of SS PBCH Signal Generation and PRACH in 5G-NR
21 pages
Am PCF Jul2020
No ratings yet
Am PCF Jul2020
57 pages
PFCP 3GPP Spec
No ratings yet
PFCP 3GPP Spec
194 pages
g10 SCEF T6 Interface Diameter PDF
No ratings yet
g10 SCEF T6 Interface Diameter PDF
51 pages
Spécification 36212-940
No ratings yet
Spécification 36212-940
61 pages
Chapter 5: Introduction To Information Theory and Coding: Efficient and Reliable Communication
No ratings yet
Chapter 5: Introduction To Information Theory and Coding: Efficient and Reliable Communication
22 pages
Solution To Practice Problem Set 3
No ratings yet
Solution To Practice Problem Set 3
4 pages
3 GPP
No ratings yet
3 GPP
96 pages
36212-900 PHYmultiplexing Coding
No ratings yet
36212-900 PHYmultiplexing Coding
63 pages
3GPP TS 23.288
No ratings yet
3GPP TS 23.288
67 pages
Chapter 2 - Data Transmission
No ratings yet
Chapter 2 - Data Transmission
3 pages
v16 5g-Ausf
No ratings yet
v16 5g-Ausf
50 pages
3GPP TS 23.236: Technical Specification
No ratings yet
3GPP TS 23.236: Technical Specification
41 pages
Information Theory and Coding: Faculty of Engineering
No ratings yet
Information Theory and Coding: Faculty of Engineering
10 pages
NR - Physical Channels and Modulation
No ratings yet
NR - Physical Channels and Modulation
130 pages
Mastering FT8 A Comprehensive Guide to the Ultimate Digital Mode
From Everand
Mastering FT8 A Comprehensive Guide to the Ultimate Digital Mode
Duarte Braga
No ratings yet
38113-h40 - Base Station (BS) ElectroMagnetic Compatibility (EMC)
No ratings yet
38113-h40 - Base Station (BS) ElectroMagnetic Compatibility (EMC)
34 pages
3GPP TS 38.211
No ratings yet
3GPP TS 38.211
97 pages
Cyclic Redundancy Checks
100% (1)
Cyclic Redundancy Checks
12 pages
32426-c00 - EPC KPIs
No ratings yet
32426-c00 - EPC KPIs
84 pages
3GPP TS 22.011
No ratings yet
3GPP TS 22.011
28 pages
Resume Vikash+tiwari+10314802818
No ratings yet
Resume Vikash+tiwari+10314802818
1 page
Classic Classes (Ankul Sir) : Synonym Set - I
No ratings yet
Classic Classes (Ankul Sir) : Synonym Set - I
18 pages
Oracle Seating A0abusn
No ratings yet
Oracle Seating A0abusn
8 pages
Distributions - Questions About KL Divergence - Cross Validated
No ratings yet
Distributions - Questions About KL Divergence - Cross Validated
3 pages
MATH3067 (Coding Theory) 2012: R3 R3-R1 R3 R3-R2
No ratings yet
MATH3067 (Coding Theory) 2012: R3 R3-R1 R3 R3-R2
3 pages
PDF
No ratings yet
PDF
5 pages
Cisco Systems Venue
No ratings yet
Cisco Systems Venue
10 pages
Linux Unicode Programming
No ratings yet
Linux Unicode Programming
10 pages
3GPP TS 36.304
No ratings yet
3GPP TS 36.304
30 pages
Short Block-Length Codes For Ultra-Reliable Low Latency Communications
No ratings yet
Short Block-Length Codes For Ultra-Reliable Low Latency Communications
8 pages
Ride Details Bill Details: Thanks For Travelling With Us, Vikram Singh
No ratings yet
Ride Details Bill Details: Thanks For Travelling With Us, Vikram Singh
3 pages
Hash List Percobaan 2
No ratings yet
Hash List Percobaan 2
1 page
IITK SPO Terms and Condtions
No ratings yet
IITK SPO Terms and Condtions
3 pages
Errata
No ratings yet
Errata
2 pages
Coding System in Computer
No ratings yet
Coding System in Computer
4 pages
SERB ECR Review Template
No ratings yet
SERB ECR Review Template
2 pages
What Is Difference Between ARQ and HARQ
No ratings yet
What Is Difference Between ARQ and HARQ
1 page
Tabela ASCII (American Standard Code II) IA5 (International Alphabet)
No ratings yet
Tabela ASCII (American Standard Code II) IA5 (International Alphabet)
1 page
Umesh Kumar Gupta: Educational Qualifications
No ratings yet
Umesh Kumar Gupta: Educational Qualifications
2 pages
9.1.2.5 Lab - Hashing Things Out
No ratings yet
9.1.2.5 Lab - Hashing Things Out
3 pages
Electromania: Team Event (Y16) Points: 35
No ratings yet
Electromania: Team Event (Y16) Points: 35
2 pages
Automatic Number Plate Recognition: Unlocking the Potential of Computer Vision Technology
From Everand
Automatic Number Plate Recognition: Unlocking the Potential of Computer Vision Technology
Fouad Sabry
No ratings yet
Automotive Scan Tool PID Diagnostics
From Everand
Automotive Scan Tool PID Diagnostics
Mandy Concepcion
4.5/5 (5)
Automatic Number Plate Recognition: Fundamentals and Applications
From Everand
Automatic Number Plate Recognition: Fundamentals and Applications
Fouad Sabry
No ratings yet

Uploaded by

Uploaded by

3GPP TS 38.212 V16.6.

3rd Generation Partnership Project;

3GPP support office address

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

6.3.1.3.1 UCI encoded by Polar code ............................................................................................................ 56

7.3.1.3.1 Format 2_0 .................................................................................................................................... 139

Annex A: Change history .................................................................................................................... 150

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

5.1 CRC calculation

- g CRC24A (D ) = [ D 24 + D 23 + D18 + D17 + D14 + D11 + D10 + D 7 + D 6 + D 5 + D 4 + D 3 + D + 1] for a CRC length

- g CRC24B (D ) = [ D 24 + D 23 + D 6 + D 5 + D + 1] for a CRC length L = 24 ;

- g CRC24C (D ) = [ D 24 + D 23 + D 21 + D 20 + D17 + D15 + D13 + D12 + D 8 + D 4 + D 2 + D + 1] for a CRC length L = 24 ;

- g CRC16 (D ) = [ D16 + D12 + D 5 + 1] for a CRC length L = 16 ;

- g CRC11 (D ) = [ D11 + D10 + D 9 + D 5 + 1] for a CRC length L = 11 ;

- g CRC6 (D ) = [ D 6 + D 5 + 1] for a CRC length L = 6 .

a0 D A+ L−1 + a1 D A+ L−2 + ... + a A−1 D L + p0 DL−1 + p1 D L−2 + ... + pL−2 D1 + pL−1

5.2 Code block segmentation and code block CRC attachment

Number of code blocks: C = 2 ;

Number of code blocks: C = 1

for i = A'− A to A'−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:

For LDPC base graph 1,

For LDPC base graph 2,

elseif B > 560

elseif B > 192

The bit sequence crk is calculated as:

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

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

crk =< NULL > ;

5.3 Channel coding

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

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

5.3.1 Polar coding

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

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

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

5.3.1.2 Polar encoding

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

5.3.2 Low density parity check coding

if ck ≠< NULL >

d k −2 Zc =< NULL > ;

- Each element of value 0 in H BG is replaced by an all zero matrix 0 of size Z c × Z c ;

Table 5.3.2-1: Sets of LDPC lifting size Z

Set index ( iLS ) Set of lifting sizes ( Z )

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

5.3.3 Channel coding of small block lengths

5.3.3.1 Encoding of 1-bit information

Table 5.3.3.1-1: Encoding of 1-bit information

Qm Encoded bits d 0 , d1 , d 2 ,..., d N −1

5.3.3.2 Encoding of 2-bit information

Table 5.3.3.2-1: Encoding of 2-bit information

Qm Encoded bits d 0 , d1 , d 2 ,..., d N −1

5.3.3.3 Encoding of other small block lengths

For 3 ≤ K ≤ 11 , the code block is encoded by d i =  ∑ ck ⋅ M i ,k  mod 2 , where i = 0, 1, , N − 1 , N = 32 , and M i ,k

Table 5.3.3.3-1: Basis sequences for (32, K ) code

5.4 Rate matching

5.4.1.1 Sub-block interleaving

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

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

Table 5.4.1.1-1: Sub-block interleaver pattern P(i )