Layer 1

3GPP TS 36.212 V13.9.
0 (2019-06)
Technical Specification
3rd Generation Partnership Project;

Technical Specification Group Radio Access Network;
Evolved Universal Terrestrial Radio Access (E-UTRA);
Multiplexing and channel coding
(Release 13)
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 13 2 3GPP TS 36.212 V13.9.0 (2019-06)
Keywords
E-UTRA, radio, Layer 1
3GPP
Postal address
3GPP support office address

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

The copyright and the foregoing restriction extend to reproduction in all media.
© 2019, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
All rights reserved.
UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
GSM® and the GSM logo are registered and owned by the GSM Association
3GPP
Release 13 3 3GPP TS 36.212 V13.9.0 (2019-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 Channel coding, multiplexing and interleaving ..................................................................................... 10
5.1 Generic procedures .......................................................................................................................................... 10
5.1.1 CRC calculation ......................................................................................................................................... 10
5.1.2 Code block segmentation and code block CRC attachment ....................................................................... 11
5.1.3 Channel coding........................................................................................................................................... 12
5.1.3.1 Tail biting convolutional coding ........................................................................................................... 13
5.1.3.2 Turbo coding ........................................................................................................................................ 14
5.1.3.2.1 Turbo encoder ................................................................................................................................. 14
5.1.3.2.2 Trellis termination for turbo encoder .............................................................................................. 15
5.1.3.2.3 Turbo code internal interleaver ....................................................................................................... 15
5.1.4 Rate matching............................................................................................................................................. 17
5.1.4.1 Rate matching for turbo coded transport channels ............................................................................... 17
5.1.4.1.1 Sub-block interleaver ...................................................................................................................... 17
5.1.4.1.2 Bit collection, selection and transmission ....................................................................................... 18
5.1.4.2 Rate matching for convolutionally coded transport channels and control information ........................ 21
5.1.4.2.1 Sub-block interleaver ...................................................................................................................... 22
5.1.4.2.2 Bit collection, selection and transmission ....................................................................................... 22
5.1.5 Code block concatenation .......................................................................................................................... 23
5.2 Uplink transport channels and control information ......................................................................................... 23
5.2.1 Random access channel .............................................................................................................................. 24
5.2.2 Uplink shared channel ................................................................................................................................ 24
5.2.2.1 Transport block CRC attachment ......................................................................................................... 25
5.2.2.2 Code block segmentation and code block CRC attachment ................................................................. 25
5.2.2.3 Channel coding of UL-SCH ................................................................................................................. 26
5.2.2.4 Rate matching ....................................................................................................................................... 26
5.2.2.5 Code block concatenation ..................................................................................................................... 26
5.2.2.6 Channel coding of control information ................................................................................................. 26
5.2.2.6.1 Channel quality information formats for wideband CQI reports .................................................... 39
5.2.2.6.2 Channel quality information formats for higher layer configured subband CQI reports ................ 48
5.2.2.6.3 Channel quality information formats for UE selected subband CQI reports .................................. 58
5.2.2.6.4 Channel coding for CQI/PMI information in PUSCH .................................................................... 66
5.2.2.6.5 Channel coding for more than 11 bits of HARQ-ACK information ............................................... 67
5.2.2.7 Data and control multiplexing .............................................................................................................. 68
5.2.2.8 Channel interleaver ............................................................................................................................... 68
5.2.3 Uplink control information on PUCCH ..................................................................................................... 70
5.2.3.1 Channel coding for UCI HARQ-ACK ................................................................................................. 71
5.2.3.2 Channel coding for UCI scheduling request ......................................................................................... 77
5.2.3.3 Channel coding for UCI channel quality information .......................................................................... 77
5.2.3.3.1 Channel quality information formats for wideband reports ............................................................ 78
5.2.3.3.2 Channel quality information formats for UE-selected sub-band reports......................................... 85
5.2.3.4 Channel coding for UCI channel quality information and HARQ-ACK .............................................. 94
5.2.4 Uplink control information on PUSCH without UL-SCH data .................................................................. 95
5.2.4.1 Channel coding of control information ................................................................................................. 95
3GPP
Release 13 4 3GPP TS 36.212 V13.9.0 (2019-06)
5.2.4.2 Control information mapping ............................................................................................................... 96

5.2.4.3 Channel interleaver ............................................................................................................................... 96
5.3 Downlink transport channels and control information..................................................................................... 96
5.3.1 Broadcast channel ...................................................................................................................................... 96
5.3.1.2 Channel coding ..................................................................................................................................... 97
5.3.1.3 Rate matching ....................................................................................................................................... 98
5.3.2 Downlink shared channel, Paging channel and Multicast channel ............................................................. 98
5.3.2.2 Code block segmentation and code block CRC attachment ................................................................. 99
5.3.2.3 Channel coding ..................................................................................................................................... 99
5.3.2.4 Rate matching ....................................................................................................................................... 99
5.3.2.5 Code block concatenation ..................................................................................................................... 99
5.3.3 Downlink control information .................................................................................................................. 100
5.3.3.1 DCI formats ........................................................................................................................................ 100
5.3.3.1.1 Format 0 ........................................................................................................................................ 100
5.3.3.1.2 Format 1 ........................................................................................................................................ 102
5.3.3.1.3 Format 1A ..................................................................................................................................... 103
5.3.3.1.3A Format 1B ..................................................................................................................................... 105
5.3.3.1.4 Format 1C ..................................................................................................................................... 106
5.3.3.1.4A Format 1D ..................................................................................................................................... 107
5.3.3.1.5 Format 2 ........................................................................................................................................ 108
5.3.3.1.5A Format 2A ..................................................................................................................................... 112
5.3.3.1.5B Format 2B ..................................................................................................................................... 114
5.3.3.1.5C Format 2C ..................................................................................................................................... 115
5.3.3.1.5D Format 2D ..................................................................................................................................... 117
5.3.3.1.6 Format 3 ........................................................................................................................................ 118
5.3.3.1.7 Format 3A ..................................................................................................................................... 119
5.3.3.1.8 Format 4 ........................................................................................................................................ 119
5.3.3.1.9 Format 5 ........................................................................................................................................ 121
5.3.3.1.10 Format 6-0A .................................................................................................................................. 122
5.3.3.1.11 Format 6-0B .................................................................................................................................. 122
5.3.3.1.12 Format 6-1A .................................................................................................................................. 123
5.3.3.1.13 Format 6-1B .................................................................................................................................. 125
5.3.3.1.14 Format 6-2..................................................................................................................................... 126
5.3.3.2 CRC attachment.................................................................................................................................. 126
5.3.3.3 Channel coding ................................................................................................................................... 127
5.3.3.4 Rate matching ..................................................................................................................................... 127
5.3.4 Control format indicator ........................................................................................................................... 127
5.3.4.1 Channel coding ................................................................................................................................... 127
5.3.5 HARQ indicator (HI) ............................................................................................................................... 128
5.3.5.1 Channel coding ................................................................................................................................... 128
5.4 Sidelink transport channels and control information ..................................................................................... 128
5.4.1 Sidelink broadcast channel ....................................................................................................................... 128
5.4.1.1 Transport block CRC attachment ....................................................................................................... 129
5.4.1.2 Channel coding ................................................................................................................................... 129
5.4.1.3 Rate matching ..................................................................................................................................... 129
5.4.2 Sidelink shared channel ............................................................................................................................ 129
5.4.3 Sidelink control information .................................................................................................................... 130
5.4.3.1 SCI formats ......................................................................................................................................... 130
5.4.3.1.1 SCI format 0.................................................................................................................................. 130
5.4.4 Sidelink discovery channel ....................................................................................................................... 131
6 Narrowband IoT ................................................................................................................................... 131
6.1 Mapping to physical channels ........................................................................................................................ 131
6.2 Generic procedures ........................................................................................................................................ 131
6.3 Uplink transport channels and control information ....................................................................................... 132
6.3.1 Random access channel ............................................................................................................................ 132
6.3.2 Uplink shared channel .............................................................................................................................. 132
6.3.3 Uplink control information on NPUSCH without UL-SCH data ............................................................. 133
6.4 Downlink transport channels and control information ................................................................................... 133
6.4.1 Broadcast channel .................................................................................................................................... 133
3GPP
Release 13 5 3GPP TS 36.212 V13.9.0 (2019-06)
6.4.2 Downlink shared channel and Paging channel ......................................................................................... 133

6.4.3 Downlink control information .................................................................................................................. 134
6.4.3.1 DCI Format N0 ................................................................................................................................... 134
6.4.3.2 DCI Format N1 ................................................................................................................................... 135
6.4.3.3 DCI Format N2 ................................................................................................................................... 135
Annex A (informative): Change history ............................................................................................. 137
3GPP
Release 13 6 3GPP TS 36.212 V13.9.0 (2019-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 13 7 3GPP TS 36.212 V13.9.0 (2019-06)
1 Scope
The present document specifies the coding, multiplexing and mapping to physical channels for E-UTRA.
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 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and
modulation".
[3] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer
procedures".
[4] 3GPP TS 36.306: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE)
radio access capabilities".
[5] 3GPP TS36.321, "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access
Control (MAC) protocol specification"
[6] 3GPP TS36.331, "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource
Control (RRC) protocol specification"
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in [1] and the following apply. A term
defined in the present document takes precedence over the definition of the same term, if any, in [1].
BL/CE: A Bandwidth-reduced Low-complexity or Coverage Enhanced (BL/CE) UE is capable of coverage

enhancement mode A support and intends to access a cell in a coverage enhancement mode or is configured in a
coverage enhancement mode.
3.2 Symbols
For the purposes of the present document, the following symbols apply:
DL
N RB Downlink bandwidth configuration, expressed in number of resource blocks [2]
UL
N RB Uplink bandwidth configuration, expressed in number of resource blocks [2]
SL
N RB Sidelink bandwidth configuration, expressed in number of resource blocks [2]
3GPP
Release 13 8 3GPP TS 36.212 V13.9.0 (2019-06)
RB
N sc Resource block size in the frequency domain, expressed as a number of subcarriers
PUSCH
N symb Number of SC-FDMA symbols carrying PUSCH in a subframe
PUSCH-initial
N symb Number of SC-FDMA symbols carrying PUSCH in the initial PUSCH transmission subframe
UL
N symb Number of SC-FDMA symbols in an uplink slot
SL
N symb Number of SC-FDMA symbols in a sidelink slot
N SRS Number of SC-FDMA symbols used for SRS transmission in a subframe (0 or 1).
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
BCH Broadcast channel

CFI Control Format Indicator
CP Cyclic Prefix
CSI Channel State Information
DCI Downlink Control Information
DL-SCH Downlink Shared channel
EPDCCH Enhanced Physical Downlink Control channel
FDD Frequency Division Duplexing
HI HARQ indicator
LAA Licensed-Assisted Access
MCH Multicast channel
MPDCCH MTC Physical Downlink Control Channel
NPBCH Narrowband Physical Broadcast channel
NPDCCH Narrowband Physical Downlink Control channel
NPDSCH Narrowband Physical Downlink Shared channel
NPRACH Narrowband Physical Random Access channel
NPUSCH Narrowband Physical Uplink Shared channel
PBCH Physical Broadcast channel
PCFICH Physical Control Format Indicator channel
PCH Paging channel
PDCCH Physical Downlink Control channel
PDSCH Physical Downlink Shared channel
PHICH Physical HARQ indicator channel
PMCH Physical Multicast channel
PMI Precoding Matrix Indicator
PRACH Physical Random Access channel
PSBCH Physical Sidelink Broadcast Channel
PSCCH Physical Sidelink Control Channel
PSDCH Physical Sidelink Discovery Channel
PSSCH Physical Sidelink Shared Channel
PUCCH Physical Uplink Control channel
PUSCH Physical Uplink Shared channel
RACH Random Access channel
RI Rank Indication
SCI Sidelink Control Information
SL-BCH Sidelink Broadcast Channel
SL-DCH Sidelink Discovery Channel
SL-SCH Sidelink Shared Channel
SR Scheduling Request
SRS Sounding Reference Signal
TDD Time Division Duplexing
TPMI Transmitted Precoding Matrix Indicator
UCI Uplink Control Information
UL-SCH Uplink Shared channel
3GPP
Release 13 9 3GPP TS 36.212 V13.9.0 (2019-06)
4 Mapping to physical channels

The mapping to physical channels for Narrowband IoT is provided in subclause 6.1.
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

DL-SCH PDSCH
BCH PBCH
PCH PDSCH
MCH PMCH
Table 4.2-2

CFI PCFICH
HI PHICH
DCI PDCCH, EPDCCH, MPDCCH
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 to its corresponding physical channel.
3GPP
Release 13 10 3GPP TS 36.212 V13.9.0 (2019-06)
Table 4.3-1

SL-SCH PSSCH
SL-BCH PSBCH
SL-DCH PSDCH
Table 4.3-2

SCI PSCCH
5 Channel coding, multiplexing and interleaving

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 Generic procedures

This subclause contains coding procedures which are used for more than one transport channel or control information
type.
5.1.1 CRC calculation

Denote the input bits to the CRC computation by a0 , a1 , a 2 , a3 ,...,a A1 , and the parity bits by p0 , p1 , p 2 , p3 ,..., p L1 . 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:
- gCRC24A(D) = [D24 + D23 + D18 + D17 + D14 + D11 + D10 + D7 + D6 + D5 + D4 + D3 + D + 1] and;
- gCRC24B(D) = [D24 + D23 + D6 + D5 + D + 1] for a CRC length L = 24 and;
- gCRC16(D) = [D16 + D12 + D5 + 1] for a CRC length L = 16.
- gCRC8(D) = [D8 + D7 + D4 + D3 + D + 1] for a CRC length of L = 8.
The encoding is performed in a systematic form, which means that in GF(2), the polynomial:
a0 D A 23  a1 D A 22  ... a A1 D 24  p0 D 23  p1 D 22  ... p 22 D1  p 23
yields a remainder equal to 0 when divided by the corresponding length-24 CRC generator polynomial, gCRC24A(D) or
gCRC24B(D), the polynomial:
a0 D A15  a1 D A14  ... a A1 D16  p0 D15  p1 D14  ... p14 D1  p15
yields a remainder equal to 0 when divided by gCRC16(D), and the polynomial:
a0 D A 7  a1D A 6  ...  a A1D8  p0 D7  p1D6  ...  p6 D1  p7
yields a remainder equal to 0 when divided by gCRC8(D).
The bits after CRC attachment are denoted by b0 , b1 , b2 , b3 ,...,bB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.
3GPP
Release 13 11 3GPP TS 36.212 V13.9.0 (2019-06)
5.1.2 Code block segmentation and code block CRC attachment

The input bit sequence to the code block segmentation is denoted by b0 , b1 , b2 , b3 ,...,bB 1 , where B > 0. If B is larger
than the maximum code block size Z, segmentation of the input bit sequence is performed and an additional CRC
sequence of L = 24 bits is attached to each code block. The maximum code block size is:
- Z = 6144.
If the number of filler bits F calculated below is not 0, filler bits are added to the beginning of the first block.
Note that if B < 40, filler bits are added to the beginning of the code block.
The filler bits shall be set to <NULL> at the input to the encoder.
Total number of code blocks C is determined by:
if B  Z
L=0
Number of code blocks: C  1
B  B
else
L = 24
Number of code blocks: C  B / Z  L .
B  B  C  L
end if
The bits output from code block segmentation, for C  0, are denoted by c r 0 , c r1 , c r 2 , c r 3 ,...,c r Kr 1 , where r is the
code block number, and Kr is the number of bits for the code block number r.
Number of bits in each code block (applicable for C  0 only):
First segmentation size: K  = minimum K in table 5.1.3-3 such that C  K  B 
if C  1
the number of code blocks with length K  is C  =1, K   0 , C   0
else if C  1
Second segmentation size: K  = maximum K in table 5.1.3-3 such that K  K 
K  K  K
 C  K   B 
Number of segments of size K  : C    .
 K 
Number of segments of size K  : C   C  C  .
end if
Number of filler bits: F  C   K   C   K   B 
for k = 0 to F-1 -- Insertion of filler bits
3GPP
Release 13 12 3GPP TS 36.212 V13.9.0 (2019-06)
c0k  NULL 
end for
k=F
s=0
for r = 0 to C-1
if r  C 
Kr  K
else
Kr  K
end if
while k  K r  L
c rk  bs
k  k 1
s  s 1
end while
if C >1
The sequence cr 0 , cr1 , cr 2 , cr 3 ,...,cr Kr L1 is used to calculate the CRC parity bits pr 0 , pr1 , pr 2 ,..., pr L1
according to subclause 5.1.1 with the generator polynomial gCRC24B(D). For CRC calculation it is
assumed that filler bits, if present, have the value 0.
while k  K r
crk  pr ( k  L  K r )
k  k 1
end while
end if
k 0
end for
5.1.3 Channel coding

The bit sequence input for a given code block to channel coding is denoted by c0 , c1 , c 2 , c3 ,...,c K 1 , where K is the
number of bits to encode. After encoding the bits are denoted by d 0(i ) , d1(i ) , d 2(i ) , d 3(i ) ,...,d D(i )1 , where D is the number of
encoded bits per output stream and i indexes the encoder output stream. The relation between c k and d k(i ) and between
K and D is dependent on the channel coding scheme.
The following channel coding schemes can be applied to TrCHs:
- tail biting convolutional coding;
- turbo coding.
3GPP
Release 13 13 3GPP TS 36.212 V13.9.0 (2019-06)
Usage of coding scheme and coding rate for the different types of TrCH is shown in table 5.1.3-1. Usage of coding
scheme and coding rate for the different control information types is shown in table 5.1.3-2.
The values of D in connection with each coding scheme:
- tail biting convolutional coding with rate 1/3: D = K;
- turbo coding with rate 1/3: D = K + 4.
The range for the output stream index i is 0, 1 and 2 for both coding schemes.
Table 5.1.3-1: Usage of channel coding scheme and coding rate for TrCHs.
TrCH Coding scheme Coding rate

UL-SCH
DL-SCH
PCH
Turbo coding 1/3
MCH
SL-SCH
SL-DCH
BCH Tail biting
convolutional 1/3
SL-BCH
coding
Table 5.1.3-2: Usage of channel coding scheme and coding rate for control information.
Control Information Coding scheme Coding rate

Tail biting
DCI convolutional 1/3
coding
CFI Block code 1/16
HI Repetition code 1/3
Block code variable
Tail biting
UCI
convolutional 1/3
coding
SCI Tail biting
convolutional 1/3
coding
5.1.3.1 Tail biting convolutional coding

A tail biting convolutional code with constraint length 7 and coding rate 1/3 is defined.
The configuration of the convolutional encoder is presented in figure 5.1.3-1.
The initial value of the shift register of the encoder shall be set to the values corresponding to the last 6 information bits
in the input stream so that the initial and final states of the shift register are the same. Therefore, denoting the shift
register of the encoder by s 0 , s1 , s 2 ,...,s5 , then the initial value of the shift register shall be set to
s i  cK 1i 
3GPP
Release 13 14 3GPP TS 36.212 V13.9.0 (2019-06)
ck
D D D D D D
d k(0) G0 = 133 (octal)
d k(1) G1 = 171 (octal)
d k( 2) G2 = 165 (octal)
Figure 5.1.3-1: Rate 1/3 tail biting convolutional encoder.
The encoder output streams d k(0) , d k(1) and d k( 2) correspond to the first, second and third parity streams, respectively as
shown in Figure 5.1.3-1.
5.1.3.2 Turbo coding
5.1.3.2.1 Turbo encoder

The scheme of turbo encoder is a Parallel Concatenated Convolutional Code (PCCC) with two 8-state constituent
encoders and one turbo code internal interleaver. The coding rate of turbo encoder is 1/3. The structure of turbo encoder
is illustrated in figure 5.1.3-2.
The transfer function of the 8-state constituent code for the PCCC is:
 g1 ( D ) 
G(D) = 1, ,
 g 0 ( D) 
where
g0(D) = 1 + D2 + D3,
g1(D) = 1 + D + D3.
The initial value of the shift registers of the 8-state constituent encoders shall be all zeros when starting to encode the
input bits.
The output from the turbo encoder is
d k(0)  x k
d k(1)  z k
d k( 2)  z k
for k  0,1,2,...,K  1 .
If the code block to be encoded is the 0-th code block and the number of filler bits is greater than zero, i.e., F > 0, then
the encoder shall set ck, = 0, k = 0,…,(F-1) at its input and shall set d k(0)  NULL  , k = 0,…,(F-1) and
d k(1)  NULL  , k = 0,…,(F-1) at its output.
The bits input to the turbo encoder are denoted by c0 , c1 , c 2 , c3 ,...,c K 1 , and the bits output from the first and second 8-
state constituent encoders are denoted by z 0 , z1 , z 2 , z 3 ,...,z K 1 and z 0 , z1 , z 2 , z 3 ,...,z K 1 , respectively. The bits output
from the turbo code internal interleaver are denoted by c0 , c1 ,...,cK 1 , and these bits are to be the input to the second 8-
state constituent encoder.
3GPP
Release 13 15 3GPP TS 36.212 V13.9.0 (2019-06)
xk
1st constituent encoder

zk
ck
D D D
Output
Input
Turbo code internal
interleaver 2nd constituent encoder z k
Output
ck
D D D
xk
Figure 5.1.3-2: Structure of rate 1/3 turbo encoder (dotted lines apply for trellis termination only).
5.1.3.2.2 Trellis termination for turbo encoder

Trellis termination is performed by taking the tail bits from the shift register feedback after all information bits are
encoded. Tail bits are padded after the encoding of information bits.
The first three tail bits shall be used to terminate the first constituent encoder (upper switch of figure 5.1.3-2 in lower
position) while the second constituent encoder is disabled. The last three tail bits shall be used to terminate the second
constituent encoder (lower switch of figure 5.1.3-2 in lower position) while the first constituent encoder is disabled.
The transmitted bits for trellis termination shall then be:
d K(0)  x K , d K(0)1  z K 1 , d K(0) 2  x K , d K(0) 3  z K 1
d K(1)  z K , d K(1)1  x K  2 , d K(1) 2  z K , d K(1) 3  x K 2
d K( 2)  x K 1 , d K( 2)1  z K  2 , d K( 2) 2  x K 1 , d K( 2)3  z K 2
5.1.3.2.3 Turbo code internal interleaver

The bits input to the turbo code internal interleaver are denoted by c0 , c1 ,...,c K 1 , where K is the number of input bits.
The bits output from the turbo code internal interleaver are denoted by c0 , c1 ,...,cK 1 .
The relationship between the input and output bits is as follows:
ci  c  i  , i=0, 1,…, (K-1)
3GPP
Release 13 16 3GPP TS 36.212 V13.9.0 (2019-06)
where the relationship between the output index i and the input index (i) satisfies the following quadratic form:
 
(i)  f1  i  f 2  i 2 mod K
The parameters f 1 and f 2 depend on the block size K and are summarized in Table 5.1.3-3.
Table 5.1.3-3: Turbo code internal interleaver parameters.
i K f1 f2 i K f1 f2 i K f1 f2 i K f1 f2
1 40 3 10 48 416 25 52 95 1120 67 140 142 3200 111 240
2 48 7 12 49 424 51 106 96 1152 35 72 143 3264 443 204
3 56 19 42 50 432 47 72 97 1184 19 74 144 3328 51 104
4 64 7 16 51 440 91 110 98 1216 39 76 145 3392 51 212
5 72 7 18 52 448 29 168 99 1248 19 78 146 3456 451 192
6 80 11 20 53 456 29 114 100 1280 199 240 147 3520 257 220
7 88 5 22 54 464 247 58 101 1312 21 82 148 3584 57 336
8 96 11 24 55 472 29 118 102 1344 211 252 149 3648 313 228
9 104 7 26 56 480 89 180 103 1376 21 86 150 3712 271 232
10 112 41 84 57 488 91 122 104 1408 43 88 151 3776 179 236
11 120 103 90 58 496 157 62 105 1440 149 60 152 3840 331 120
12 128 15 32 59 504 55 84 106 1472 45 92 153 3904 363 244
13 136 9 34 60 512 31 64 107 1504 49 846 154 3968 375 248
14 144 17 108 61 528 17 66 108 1536 71 48 155 4032 127 168
15 152 9 38 62 544 35 68 109 1568 13 28 156 4096 31 64
16 160 21 120 63 560 227 420 110 1600 17 80 157 4160 33 130
17 168 101 84 64 576 65 96 111 1632 25 102 158 4224 43 264
18 176 21 44 65 592 19 74 112 1664 183 104 159 4288 33 134
19 184 57 46 66 608 37 76 113 1696 55 954 160 4352 477 408
20 192 23 48 67 624 41 234 114 1728 127 96 161 4416 35 138
21 200 13 50 68 640 39 80 115 1760 27 110 162 4480 233 280
22 208 27 52 69 656 185 82 116 1792 29 112 163 4544 357 142
23 216 11 36 70 672 43 252 117 1824 29 114 164 4608 337 480
24 224 27 56 71 688 21 86 118 1856 57 116 165 4672 37 146
25 232 85 58 72 704 155 44 119 1888 45 354 166 4736 71 444
26 240 29 60 73 720 79 120 120 1920 31 120 167 4800 71 120
27 248 33 62 74 736 139 92 121 1952 59 610 168 4864 37 152
28 256 15 32 75 752 23 94 122 1984 185 124 169 4928 39 462
29 264 17 198 76 768 217 48 123 2016 113 420 170 4992 127 234
30 272 33 68 77 784 25 98 124 2048 31 64 171 5056 39 158
31 280 103 210 78 800 17 80 125 2112 17 66 172 5120 39 80
32 288 19 36 79 816 127 102 126 2176 171 136 173 5184 31 96
33 296 19 74 80 832 25 52 127 2240 209 420 174 5248 113 902
34 304 37 76 81 848 239 106 128 2304 253 216 175 5312 41 166
35 312 19 78 82 864 17 48 129 2368 367 444 176 5376 251 336
36 320 21 120 83 880 137 110 130 2432 265 456 177 5440 43 170
37 328 21 82 84 896 215 112 131 2496 181 468 178 5504 21 86
38 336 115 84 85 912 29 114 132 2560 39 80 179 5568 43 174
39 344 193 86 86 928 15 58 133 2624 27 164 180 5632 45 176
40 352 21 44 87 944 147 118 134 2688 127 504 181 5696 45 178
41 360 133 90 88 960 29 60 135 2752 143 172 182 5760 161 120
42 368 81 46 89 976 59 122 136 2816 43 88 183 5824 89 182
43 376 45 94 90 992 65 124 137 2880 29 300 184 5888 323 184
44 384 23 48 91 1008 55 84 138 2944 45 92 185 5952 47 186
45 392 243 98 92 1024 31 64 139 3008 157 188 186 6016 23 94
46 400 151 40 93 1056 17 66 140 3072 47 96 187 6080 47 190
47 408 155 102 94 1088 171 204 141 3136 13 28 188 6144 263 480
3GPP
Release 13 17 3GPP TS 36.212 V13.9.0 (2019-06)
5.1.4 Rate matching
5.1.4.1 Rate matching for turbo coded transport channels

The rate matching for turbo coded transport channels is defined per coded block and consists of interleaving the three
information bit streams d k(0) , d k(1) and d k( 2) , followed by the collection of bits and the generation of a circular buffer as
depicted in Figure 5.1.4-1. The output bits for each code block are transmitted as described in subclause 5.1.4.1.2.
d k(0) Sub-block vk(0)

interleaver
virtual circular
buffer
ek
d k(1) Sub-block vk(1) Bit wk Bit selection
interleaver collection and pruning
d k( 2) Sub-block vk( 2)
interleaver
Figure 5.1.4-1. Rate matching for turbo coded transport channels.
The bit stream d k(0) is interleaved according to the sub-block interleaver defined in subclause 5.1.4.1.1 with an output
sequence defined as v 0(0) , v1(0) , v 2(0) ,...,v K(0) 1 and where K  is defined in subclause 5.1.4.1.1.

sequence defined as v 0(1) , v1(1) , v 2(1) ,...,v K(1) .
 1
The bit stream d k( 2) is interleaved according to the sub-block interleaver defined in subclause 5.1.4.1.1 with an output
sequence defined as v 0( 2) , v1( 2) , v 2( 2) ,...,v K( 2) 1 .

The sequence of bits e k for transmission is generated according to subclause 5.1.4.1.2.
5.1.4.1.1 Sub-block interleaver
The bits input to the block interleaver are denoted by d 0(i ) , d1(i ) , d 2(i ) ,...,d D(i) 1 , where D is the number of bits. The output
bit sequence from the block interleaver is derived as follows:
TC
(1) Assign C subblock  32 to be the number of columns of the matrix. The columns of the matrix are numbered 0, 1,
TC
2,…, Csubblock  1 from left to right.
TC TC
(2) Determine the number of rows of the matrix Rsubblock , by finding minimum integer Rsubblock such that:

D  Rsubblock
TC
 Csubblock
TC

TC
The rows of rectangular matrix are numbered 0, 1, 2,…, Rsubblock  1 from top to bottom.
3GPP
Release 13 18 3GPP TS 36.212 V13.9.0 (2019-06)

TC
(3) If Rsubblock  Csubblock
TC

 D , then N D  Rsubblock
TC
 Csubblock
TC

 D dummy bits are padded such that yk = <NULL> 
for k = 0, 1,…, ND - 1. Then, y N D  k  d k(i ) , k = 0, 1,…, D-1, and the bit sequence yk is written into
TC

the Rsubblock  C subblock
TC

matrix row by row starting with bit y0 in column 0 of row 0:
 y0 y1 y2  yCTC 
subblock 1
 
 yCTC yCTC yCTC  y 2CTC 
subblock subblock 1 subblock  2 subblock 1
      
 
 y( RTC y( RTC y( RTC  y( RTC CTC 
 subblock 1)Csubblock subblock subblock 1) 
TC TC TC
subblock 1)Csubblock 1 subblock 1)Csubblock  2
For d k(0) and d k(1) :
(4) Perform the inter-column permutation for the matrix based on the pattern P j   TC
j 0,1,...,Csubblock 1  that is shown in
table 5.1.4-1, where P(j) is the original column position of the j-th permuted column. After permutation of the
TC
columns, the inter-column permuted Rsubblock  Csubblock
TC

matrix is equal to 
 y P ( 0) y P (1) y P ( 2)  y P (CTC 
subblock 1)
 
 y P (0)CTC y P (1)CTC y P ( 2)CTC  y P (CTC TC 
subblock subblock subblock subblock 1)Csubblock
      
 
 y P (0)( RTC y P (1)( RTC y P ( 2)( RTC  y P (CTC 
 subblock 1)( Rsubblock 1)Csubblock 
TC TC TC TC TC
subblock 1)Csubblock subblock 1)Csubblock subblock 1)Csubblock
(5) The output of the block interleaver is the bit sequence read out column by column from the inter-column
TC
permuted Rsubblock 
 Csubblock
TC

matrix. The bits after sub-block interleaving are denoted
by v 0(i ) , v1(i ) , v 2(i ) ,...,v K(i ) , where v 0(i ) corresponds to y P (0) , v1(i ) to y P(0)CTC …
 1
 
subblock
and K   Rsubblock
TC
 Csubblock
TC
.
For d k( 2) :
(4) The output of the sub-block interleaver is denoted by v 0( 2) , v1( 2) , v 2( 2) ,...,v K( 2) 1 , where v k( 2)  y ( k ) and where

   
 (k )  P 
   RTC
k
   C TC
 subblock  k mod R TC

subblock  1 mod K
  
   subblock 
  
The permutation function P is defined in Table 5.1.4-1.
Table 5.1.4-1 Inter-column permutation pattern for sub-block interleaver.
Number of columns Inter-column permutation pattern

TC
Csubblock  P(0), P(1),...,P(C subblock
TC
 1) 
< 0, 16, 8, 24, 4, 20, 12, 28, 2, 18, 10, 26, 6, 22, 14, 30,
32
1, 17, 9, 25, 5, 21, 13, 29, 3, 19, 11, 27, 7, 23, 15, 31 >
5.1.4.1.2 Bit collection, selection and transmission

The circular buffer of length K w  3K  for the r-th coded block is generated as follows:
wk  v k(0) for k = 0,…, K   1
wK  2k  v k(1) for k = 0,…, K   1
3GPP
Release 13 19 3GPP TS 36.212 V13.9.0 (2019-06)
wK  2k 1  v k( 2) for k = 0,…, K   1
Denote the soft buffer size for the transport block by NIR bits and the soft buffer size for the r-th code block by Ncb bits.
The size Ncb is obtained as follows, where C is the number of code blocks computed in subclause 5.1.2:
N  
- N cb  min  IR , K w  for DL-SCH and PCH transport channels
 C  
- Ncb  K w for UL-SCH, MCH, SL-SCH and SL-DCH transport channels
For UE category 0, for DL-SCH associated with SI-RNTI and RA-RNTI and PCH transport channel, Ncb is always
equal to Kw.
where NIR is equal to:
 N soft 
N IR   
 K C  K MIMO  min M DL_HARQ , M limit 
where:
If the UE signals ue-CategoryDL-v1310 indicating UE category M1, Nsoft is the total number of soft channel bits
according to the UE category indicated by ue-CategoryDL-v1310. Otherwise, if the UE signals ue-CategoryDL-v13xy,
and is configured with transmission mode 9 or transmission mode 10 and the higher layer parameter maxLayersMIMO-
r10 is configured to eightLayers, Nsoft is the total number of soft channel bits according to the UE category indicated by
ue-CategoryDL-v13xy. Otherwise, if the UE signals ue-CategoryDL-r12 indicating UE category 0, or if the UE signals
ue-CategoryDL-r12 indicating UE category 14 and is configured by higher layers with altCQI-Table-r12 for the DL
cell, Nsoft is the total number of soft channel bits according to the UE category indicated by ue-CategoryDL-r12.
Otherwise, if the UE signals ue-Category-v11a0, and is configured by higher layers with altCQI-Table-r12 for the DL
cell, Nsoft is the total number of soft channel bits according to the UE category indicated by ue-Category-v11a0.
Otherwise, if the UE signals ue-Category-v1020, and is configured with transmission mode 9 or transmission mode 10,
or is configured with transmission mode 3 or transmission mode 4 and the higher layer parameter maxLayersMIMO-r10
is configured to fourLayers, for the DL cell, Nsoft is the total number of soft channel bits [4] according to the UE
category indicated by ue-Category-v1020 [6]. Otherwise, Nsoft is the total number of soft channel bits [4] according to
the UE category indicated by ue-Category (without suffix) [6].
If Nsoft = 35982720 or 47431680,
KC= 5,
elseif Nsoft = 303562752,
KC= 32,
if the UE is configured by higher layers with altCQI-Table-r12,
KC = 3/2
else
KC = 2
end if.
if the UE is configured by higher layers with altCQI-Table-r12,
KC = 2
3GPP
Release 13 20 3GPP TS 36.212 V13.9.0 (2019-06)
else
KC = 8/3
end if.
elseif Nsoft = 7308288 and the UE is configured by higher layers with altCQI-Table-r12,
if the UE is capable of supporting no more than a maximum of two spatial layers for the DL cell in the transmission
mode configured for the UE, or if the configured maximum number of layers indicated by the maxLayersMIMO-
r10 field is no more than two,
KC = 3
else
KC = 3/2
end if.
elseif Nsoft = 3654144 and the UE is capable of supporting no more than a maximum of two spatial layers for the DL
cell, or if the configured maximum number of layers indicated by the maxLayersMIMO-r10 field is no more than two,
KC = 2
else
KC = 1
End if.
KMIMO is equal to 2 if the UE is configured to receive PDSCH transmissions based on transmission modes 3, 4, 8, 9 or
10 as defined in subclause 7.1 of [3], and is equal to 1 otherwise. For BL/CE UE KMIMO is equal to 1.
MDL_HARQ is the maximum number of DL HARQ processes as defined in clause 7 of [3].
Mlimit is a constant equal to 8.
Denoting by E the rate matching output sequence length for the r-th coded block, and rvidx the redundancy version
number for this transmission (rvidx = 0, 1, 2 or 3), the rate matching output bit sequence is ek , k = 0,1,..., E  1 .
Define by G the total number of bits available for the transmission of one transport block.
Set G  G N L  Qm  where Qm is equal to 2 for QPSK, 4 for 16QAM, 6 for 64QAM and 8 for 256QAM, and where
- For transmit diversity:
- NL is equal to 2,
- Otherwise:
- NL is equal to the number of layers a transport block is mapped onto
Set   G  mod C , where C is the number of code blocks computed in subclause 5.1.2.
if r  C    1
set E  N L  Qm  G  / C 
else
set E  N L  Qm  G  / C 
end if
3GPP
Release 13 21 3GPP TS 36.212 V13.9.0 (2019-06)
  N  
Set k 0  R subblock
TC
  2   TCcb   rvidx  2  , where Rsubblock
TC
is the number of rows defined in subclause 5.1.4.1.1.
 
  8 R subblock  
Set k = 0 and j = 0
while {k < E }
if w( k0  j ) mod Ncb  NULL 
ek  w( k0  j ) mod Ncb
k = k +1
end if
j = j +1
end while
5.1.4.2 Rate matching for convolutionally coded transport channels and control
information
The rate matching for convolutionally coded transport channels and control information consists of interleaving the
three bit streams, d k(0) , d k(1) and d k( 2) , followed by the collection of bits and the generation of a circular buffer as
depicted in Figure 5.1.4-2. The output bits are transmitted as described in subclause 5.1.4.2.2.
d k(0) Sub-block vk(0)

interleaver
virtual circular
buffer
ek
d k(1) Sub-block vk(1) Bit wk Bit selection
interleaver collection and pruning
d k( 2) Sub-block vk( 2)
interleaver
Figure 5.1.4-2. Rate matching for convolutionally coded transport channels and control information.
sequence defined as v 0(0) , v1(0) , v 2(0) ,...,v K(0) 1 and where K  is defined in subclause 5.1.4.2.1.

sequence defined as v 0(1) , v1(1) , v 2(1) ,...,v K(1) .
 1
The bit stream d k( 2) is interleaved according to the sub-block interleaver defined in subclause 5.1.4.2.1 with an output
sequence defined as v 0( 2) , v1( 2) , v 2( 2) ,...,v K( 2) 1 .

The sequence of bits e k for transmission is generated according to subclause 5.1.4.2.2.
3GPP
Release 13 22 3GPP TS 36.212 V13.9.0 (2019-06)
5.1.4.2.1 Sub-block interleaver
The bits input to the block interleaver are denoted by d 0(i ) , d1(i ) , d 2(i ) ,...,d D(i) 1 , where D is the number of bits. The output
bit sequence from the block interleaver is derived as follows:
CC
(1) Assign C subblock  32 to be the number of columns of the matrix. The columns of the matrix are numbered 0, 1,
CC
2,…, C subblock  1 from left to right.
CC CC
(2) Determine the number of rows of the matrix Rsubblock , by finding minimum integer Rsubblock such that:
CC

D  Rsubblock  C subblock
CC

The rows of rectangular matrix are numbered 0, 1, 2,…, Rsubblock  1 from top to bottom.
CC

CC
(3) If Rsubblock  C subblock
CC

 D , then N D  Rsubblock
CC
 C subblock
CC

 D dummy bits are padded such that yk = <NULL> 
for k = 0, 1,…, ND - 1. Then, y N D  k  d k(i ) , k = 0, 1,…, D-1, and the bit sequence yk is written into
CC

the Rsubblock  Csubblock
CC

matrix row by row starting with bit y0 in column 0 of row 0:
 y0 y1 y2  yC CC 
 subblock 1 
 yC CC yC CC yC CC  y2C CC 
subblock 1 subblock  2 subblock 1
 subblock

      
 y CC CC y( R CC CC y( R CC CC  y( R CC C CC 
 ( Rsubblock 1)C subblock subblock 1)C subblock 1 subblock 1) C subblock  2 subblock subblock 1) 
(4) Perform the inter-column permutation for the matrix based on the pattern P j   CC
j 0,1,...,Csubblock  that is shown in
1
table 5.1.4-2, where P(j) is the original column position of the j-th permuted column. After permutation of the
CC
columns, the inter-column permuted Rsubblock  Csubblock
CC

matrix is equal to 
 y P ( 0) y P (1) y P ( 2)  y P (C CC 
subblock 1)
 
 y P (0)C CC y P (1)C CC y P ( 2)C CC  y P (C CC 1)C CC 
subblock subblock subblock subblock subblock
      
 
 y P (0)( RCC 1)C CC y P (1)( RCC y P ( 2)( RCC  y P (C CC 1)( RCC 1)C CC 
 subblock 
CC CC
subblock subblock subblock 1)Csubblock subblock 1)Csubblock subblock subblock
(5) The output of the block interleaver is the bit sequence read out column by column from the inter-column
CC

permuted Rsubblock  Csubblock
CC

matrix. The bits after sub-block interleaving are denoted by v 0(i ) , v1(i ) , v 2(i ) ,...,v K(i )
 1
,
where v 0(i ) corresponds to y P (0) , v1(i ) to y P(0)CCC

subblock
… and K   Rsubblock
CC

 Csubblock
CC

Table 5.1.4-2 Inter-column permutation pattern for sub-block interleaver.
Number of columns Inter-column permutation pattern

CC
Csubblock  P(0), P(1),...,P(C subblock
CC
 1) 
< 1, 17, 9, 25, 5, 21, 13, 29, 3, 19, 11, 27, 7, 23, 15, 31,
32
0, 16, 8, 24, 4, 20, 12, 28, 2, 18, 10, 26, 6, 22, 14, 30 >
This block interleaver is also used in interleaving PDCCH modulation symbols. In that case, the input bit sequence
consists of PDCCH symbol quadruplets [2].
5.1.4.2.2 Bit collection, selection and transmission

The circular buffer of length K w  3K  is generated as follows:
3GPP
Release 13 23 3GPP TS 36.212 V13.9.0 (2019-06)
wk  v k(0) for k = 0,…, K   1
wK  k  v k(1) for k = 0,…, K   1
w2 K  k  v k( 2) for k = 0,…, K   1
Denoting by E the rate matching output sequence length, the rate matching output bit sequence is ek , k = 0,1,..., E  1 .
Set k = 0 and j = 0
while {k < E }
if w j mod Kw  NULL 
ek  w j mod Kw
k = k +1
end if
j = j +1
end while
5.1.5 Code block concatenation

The input bit sequence for the code block concatenation block are the sequences e rk , for r  0,...,C  1 and
k  0,...,E r  1 . The output bit sequence from the code block concatenation block is the sequence f 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
f k  e rj
k  k 1
j  j 1
end while
r  r 1
end while
5.2 Uplink transport channels and control information

If the UE is configured with a Master Cell Group (MCG) and Secondary Cell Group (SCG) [6], the procedures
described in this clause are applied to the MCG and SCG, respectively. When the procedures are applied to a SCG, the
term primary cell refers to the primary SCell (PSCell) of the SCG.
3GPP
Release 13 24 3GPP TS 36.212 V13.9.0 (2019-06)
If the UE is configured with a PUCCH SCell [6], the procedures described in this clause are applied to the group of DL
cells associated with the primary cell and the group of DL cells associated with the PUCCH SCell, respectively. When
the procedures are applied to the group of DL cells associated with the PUCCH SCell, the term primary cell refers to
the PUCCH SCell.
If the UE is configured with a LAA SCell, the procedures described in this clause are applied assuming the LAA SCell
is an FDD SCell.
5.2.1 Random access channel

The sequence index for the random access channel is received from higher layers and is processed according to [2].
5.2.2 Uplink shared channel

Figure 5.2.2-1 shows the processing structure for the UL-SCH transport channel on one UL cell. Data arrives to the
coding unit in the form of a maximum of two transport blocks every transmission time interval (TTI) per UL cell. The
following coding steps can be identified for each transport block of an UL cell:
- Add CRC to the transport block
- Code block segmentation and code block CRC attachment
- Channel coding of data and control information
- Rate matching
- Code block concatenation
- Multiplexing of data and control information
- Channel interleaver
The coding steps for one UL-SCH transport block are shown in the figure below. The same general processing applies
for each UL-SCH transport block on each UL cell with restrictions as specified in [3].
3GPP
Release 13 25 3GPP TS 36.212 V13.9.0 (2019-06)
a0 , a1 ,..., aA 1
Transport block
CRC attachment
b0 , b1 ,..., bB 1
Code block segmentation

Code block CRC attachment
cr 0 , cr1 ,..., cr K r 1
Channel coding
dr(i0) , dr(1i ) ,..., dr(i)Dr 1
[o0RI o1RI oORIRI 1 ]

Rate matching
[o0 o1 oO 1 ] [o0ACK o1ACK oOACK

ACK
1
]
er 0 , er1 ,..., er Er 1
Code block Channel Channel Channel

concatenation coding coding coding
RI RI RI ACK ACK ACK

q0 , q1 , , qN L QCQI 1 q , q ,..., q  q0 , q1 ,..., q Q
f 0 , f1 ,..., f G 1 0 1 QRI 1 ACK 1
Data and Control multiplexing
g 0 , g 1 ,..., g H 1
Channel Interleaver
h0 , h1 ,..., hH  N
L QRI 1
Figure 5.2.2-1: Transport block processing for UL-SCH.
5.2.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 a0 , a1 , a 2 , a3 ,...,a A1 , and the parity bits by p0 , p1 , p 2 , p3 ,..., p L1 . A is the size of the transport block 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 subclause 6.1.1 of [5].
The parity bits are computed and attached to the UL-SCH transport block according to subclause 5.1.1 setting L to 24
bits and using the generator polynomial gCRC24A(D).
5.2.2.2 Code block segmentation and code block CRC attachment

The bits input to the code block segmentation are denoted by b0 , b1 , b2 , b3 ,...,bB1 where B is the number of bits in the
transport block (including CRC).
3GPP
Release 13 26 3GPP TS 36.212 V13.9.0 (2019-06)
Code block segmentation and code block CRC attachment are performed according to subclause 5.1.2.
The bits after code block segmentation are denoted by c r 0 , c r1 , c r 2 , c r 3 ,...,c r Kr 1 , where r is the code block number
and Kr is the number of bits for code block number r.
5.2.2.3 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 Kr 1 , where r is the code block number, and Kr 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 turbo encoded according to
subclause 5.1.3.2.
After encoding the bits are denoted by d r(i0) , d r(1i ) , d r(i2) , d r(i3) ,...,d r(i)D 1 , with i  0,1, and 2 and where Dr is the number of
r
bits on the i-th coded stream for code block number r, i.e. Dr  K r  4 .
5.2.2.4 Rate matching

Turbo coded blocks are delivered to the rate matching block. They are denoted by d r(i0) , d r(1i ) , d r(i2) , d r(i3) ,...,d r(i)D 1 ,
r
with i  0,1, and 2 , and where r is the code block number, i is the coded stream index, and Dr is the number of bits in
each coded stream of code block number r. The total number of code blocks is denoted by C and each coded block is
individually rate matched according to subclause 5.1.4.1.
After rate matching, the bits are denoted by er 0 , er1 , er 2 , er 3 ,...,er Er 1 , where r is the coded block number, and where
E r is the number of rate matched bits for code block number r.
5.2.2.5 Code block concatenation

The bits input to the code block concatenation block are denoted by er 0 , er1 , er 2 , er 3 ,...,er Er 1 for 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 subclause 5.1.5.
The bits after code block concatenation are denoted by f0 , f1, f 2 , f3 ,..., fG 1 , where G is the total number of coded bits
for transmission of the given transport block over N L transmission layers excluding the bits used for control
transmission, when control information is multiplexed with the UL-SCH transmission.
5.2.2.6 Channel coding of control information

Control data arrives at the coding unit in the form of channel quality information (CQI and/or PMI), HARQ-ACK and
rank indication, and CSI-RS resource indication (CRI). Different coding rates for the control information are achieved
by allocating different number of coded symbols for its transmission. When control data are transmitted in the PUSCH,
the channel coding for HARQ-ACK, rank indication (including RI only, joint report of RI/i1, joint report of CRI/RI,
joint report of CRI/RI/ i1,joint report of CRI/RI/PTI, and joint report of RI/PTI), CRI and channel quality information
o0 , o1 , o2 ,...,oO1 is done independently.
For the cases with TDD primary cell, the number of HARQ-ACK bits is determined as described in subclause 7.3 of
[3].
When the UE transmits HARQ-ACK bits, rank indicator bits or CRI bits, it shall determine the number of coded
modulation symbols per layer Q  for HARQ-ACK, rank indicator, or CRI bits as follows.
For the case when only one transport block is transmitted in the PUSCH conveying the HARQ-ACK bits, rank indicator
bits or CRI bits:
3GPP
Release 13 27 3GPP TS 36.212 V13.9.0 (2019-06)
  
 PUSCH  

PUSCH initial
O  M sc PUSCH initial
 N symb   offset PUSCH 
Q   min   C 1
, 4  M sc

 
   K r  
 r 0 
where
- O is the number of HARQ-ACK bits, rank indicator bits or CRI bits, and
PUSCH
- M sc is the scheduled bandwidth for PUSCH transmission in the current sub-frame for the transport block,
expressed as a number of subcarriers in [2], and
PUSCH-initial
- N symb is the number of SC-FDMA symbols per subframe for initial PUSCH transmission for the same
PUSCH-initial
transport block, respectively, given by N symb  2  N symb
UL
 
 1  N SRS , where 
- N SRS is equal to 1
- if UE configured with one UL cell is configured to send PUSCH and SRS in the same subframe for initial
transmission, or
- if UE transmits PUSCH and SRS in the same subframe in the same serving cell for initial transmission, or
- if the PUSCH resource allocation for initial transmission even partially overlaps with the cell-specific
SRS subframe and bandwidth configuration defined in subclause 5.5.3 of [2], or
- if the subframe for initial transmission in the same serving cell is a UE-specific type-1 SRS subframe as
defined in Subclause 8.2 of [3], or
- if the subframe for initial transmission in the same serving cell is a UE-specific type-0 SRS subframe as
defined in subclause 8.2 of [3] and the UE is configured with multiple TAGs.
- Otherwise N SRS is equal to 0.

PUSCH initial
- M sc , C , and K r are obtained from the initial PDCCH or EPDCCH or MPDCCH for the same
transport block. If there is no initial PDCCH or EPDCCH with DCI format 0 or MPDCCH with DCI format 6-
PUSCH initial
0A/6-0B for the same transport block, M sc , C , and K r shall be determined from:
- the most recent semi-persistent scheduling assignment PDCCH or EPDCCH or MPDCCH, when the initial
PUSCH for the same transport block is semi-persistently scheduled, or,
- the random access response grant for the same transport block, when the PUSCH is initiated by the random
access response grant.
For the case when two transport blocks are transmitted in the PUSCH conveying the HARQ-ACK bits, rank indicator
bits or CRI bits:
 
Q  max min Qtemp
 , 4  M sc
PUSCH

, Qmin with  
 
 PUSCH  initial(1) PUSCH  initial(1) PUSCH  initial( 2) PUSCH  initial( 2) 
 O  M sc  N symb  M sc  N symb   offset
PUSCH

   (1)
Qtemp 
C 1 C ( 2 ) 1
 PUSCH  initial(1) 
  (1) PUSCH  initial( 2)
K r  M sc PUSCH  initial( 2)
 N symb   PUSCH  initial(1)
K r  M sc
( 2)
 N symb 
 r 0 r 0 
where
- O is the number of HARQ-ACK bits, rank indicator bits or CRI bits, and
3GPP
Release 13 28 3GPP TS 36.212 V13.9.0 (2019-06)
-   O if O  2 , Qmin
Qmin   2O / Qm  if 3  O  11 with Qm  min Qm1
 
, Qm2 where Qmx , x  1,2 is the
  2O1 / Qm   2O2 / Qm
modulation order of transport block "x", and Qmin   if O  11 with O1  O / 2 and
O2  O  O / 2 .
- M scPUSCH-initial( x) , x  {1,2} are the scheduled bandwidths for PUSCH transmission in the initial sub-frame for the
first and second transport block, respectively, expressed as a number of subcarriers in [2], and
- PUSCH-initial(x)
N symb , x  {1,2} are the number of SC-FDMA symbols per subframe for initial PUSCH transmission for
PUSCH-initial( x )
the first and second transport block given by N symb  
 2  N symb
UL

 1  N SRS
( x)

, x  {1,2} , where
- ( x)
N SRS , x  {1,2} is equal to 1
- if UE configured with one UL cell is configured to send PUSCH and SRS in the same subframe for initial
transmission, or
- if UE transmits PUSCH and SRS in the same subframe in the same serving cell for initial transmission of
transport block "x", or
- if the PUSCH resource allocation for initial transmission of transport bock "x" even partially overlaps
with the cell-specific SRS subframe and bandwidth configuration defined in subclause 5.5.3 of [2] , or
- if the subframe for initial transmission of transport block "x" in the same serving cell is a UE-specific
type-1 SRS subframe as defined in Subclause 8.2 of [3], or
- if the subframe for initial transmission of transport block "x" in the same serving cell is a UE-specific
type-0 SRS subframe as defined in subclause 8.2 of [3] and the UE is configured with multiple TAGs.
- ( x)
Otherwise N SRS , x  {1,2} is equal to 0.
PUSCH initial( x )
- M sc , x  {1,2} , C ( x ) , x  {1,2} , and K r( x) , x  {1,2} are obtained from the initial PDCCH or
EPDCCH for the corresponding transport block.
For HARQ-ACK, QACK  Qm  Q and  offset

PUSCH
  offset
HARQ  ACK
, where Qm is the modulation order of a given
transport block. For UEs configured with no more than five DL cells,  offset
HARQ  ACK
shall be determined according to [3]
depending on the number of transmission codewords for the corresponding PUSCH. For UEs configured with more
than five DL cells, offset
HARQ  ACK
shall be determined according to [3] depending on the number of transmission
codewords for the corresponding PUSCH and and the number of HARQ-ACK feedback bits.
For rank indication or CRI, QRI  Qm  Q , QCRI  Qm  Q and  offset

PUSCH
  offset
RI
, where Qm is the modulation
order of a given transport block, and  offset

RI
shall be determined according to [3] depending on the number of
transmission codewords for the corresponding PUSCH, and on the uplink power control subframe set for the
corresponding PUSCH when two uplink power control subframe sets are configured by higher layers for the cell.
For HARQ-ACK
- Each positive acknowledgement (ACK) is encoded as a binary '1' and each negative acknowledgement (NACK)
is encoded as a binary '0'
- If HARQ-ACK feedback consists of 1-bit of information, i.e., [o0ACK ] , it is first encoded according to Table
5.2.2.6-1.
- If HARQ-ACK feedback consists of 2-bits of information, i.e., [o0ACK o1ACK ] with o0ACK corresponding to
HARQ-ACK bit for codeword 0 and o1ACK corresponding to that for codeword 1, or if HARQ-ACK feedback
3GPP
Release 13 29 3GPP TS 36.212 V13.9.0 (2019-06)
consists of 2-bits of information as a result of the aggregation of HARQ-ACK bits corresponding to two DL cells
with which the UE is configured by higher layers, or if HARQ-ACK feedback consists of 2-bits of information
corresponding to two subframes for TDD, it is first encoded according to Table 5.2.2.6-2 where
o2ACK  (o0ACK  o1ACK ) mod 2 .
Table 5.2.2.6-1: Encoding of 1-bit HARQ-ACK.
Qm Encoded HARQ-ACK
2 [o0ACK y]
4 [o0ACK y x x]
6 [o0ACK y x x x x ]
Table 5.2.2.6-2: Encoding of 2-bit HARQ-ACK.
Qm Encoded HARQ-ACK
2
[o0ACK o1ACK o2ACK o0ACK o1ACK o2ACK ]
4
[o0ACK o1ACK x x o2ACK o0ACK x x o1ACK o2ACK x x]
6 [o0ACK o1ACK x x x x o2ACK o0ACK x x x x o1ACK o2ACK x x x x]
- If HARQ-ACK feedback consists of 3  O ACK  11 bits of information as a result of the aggregation of HARQ-
ACK bits corresponding to one or more DL cells with which the UE is configured by higher layers, i.e.,
o0ACK o1ACK ,...,oOACK
ACK
1
, then a coded bit sequence q~0ACK q~1ACK ,...,q~31
ACK
is obtained by using the bit sequence
ACK
1
as the input to the channel coding block described in subclause 5.2.2.6.4. In turn, the bit
sequence q 0ACK , q1ACK , q 2ACK ,...,qQACK
ACK 1
is obtained by the circular repetition of the bit sequence
q~ ACK ~ ACK
q ~
,...,q ACK
so that the total bit sequence length is equal to Q .
0 1 31 ACK
- If HARQ-ACK feedback consists of 11  O ACK  22 bits of information as a result of the aggregation of HARQ-
ACK bits corresponding to one or more DL cells with which the UE is configured by higher layers, i.e.,
ACK
1
, then the coded bit sequence q 0ACK , q1ACK , q 2ACK ,...,qQACK
ACK 1
is obtained by using the bit
sequence o0ACK o1ACK ,...,oOACK
ACK
1
as the input to the channel coding block described in subclause 5.2.2.6.5.
- If HARQ-ACK feedback consists of O ACK >22 bits of information as a result of the aggregation of HARQ-ACK
bits corresponding to one or more DL cells with which the UE is configured by higher layers, the coded bit
sequence is denoted by q 0ACK , q1ACK , q 2ACK ,...,qQACK
ACK 1
. The CRC attachment, channel coding and rate matching
of the HARQ-ACK bits are performed according to subclauses 5.1.1 setting L to 8 bits, 5.1.3.1 and 5.1.4.2,
respectively. The input bit sequence to the CRC attachment operation is o0ACK o1ACK ,...,oOACK
ACK
1
. The output bit
sequence of the CRC attachment operation is the input bit sequence to the channel coding operation. The output
bit sequence of the channel coding operation is the input bit sequence to the rate matching operation.
The "x" and "y" in Table 5.2.2.6-1 and 5.2.2.6-2 are placeholders for [2] to scramble the HARQ-ACK bits in a way that
maximizes the Euclidean distance of the modulation symbols carrying HARQ-ACK information.
For FDD or TDD HARQ-ACK multiplexing or the aggregation of more than one DL cell including at least one cell
using FDD and at least one cell using TDD when HARQ-ACK consists of one or two bits of information, the bit
sequence q 0ACK , q1ACK , q 2ACK ,...,qQACK
ACK 1
is obtained by concatenation of multiple encoded HARQ-ACK blocks where
Q ACK is the total number of coded bits for all the encoded HARQ-ACK blocks. The last concatenation of the encoded
HARQ-ACK block may be partial so that the total bit sequence length is equal to QACK .
3GPP
Release 13 30 3GPP TS 36.212 V13.9.0 (2019-06)
For UEs configured by higher layers with codebooksizeDetermination-r13 = dai, the bit sequence
o0ACK o1ACK ,..., oOACK
ACK
1
is determined according to the Downlink Assignment Index (DAI) as in Table 5.3.3.1.2-2 and
ACK
as defined in [3]. Otherwise, the bit sequence o0 o1ACK ,..., oOACK
ACK
1
is determined as below.
For FDD when HARQ ACK consists of 2 or more bits of information as a result of the aggregation of more than one
ACK
DL cell, the bit sequence o0 o1ACK ,..., oOACK
ACK
1
is the result of the concatenation of HARQ-ACK bits for the multiple
DL cells according to the following pseudo-code:
Set c = 0 – cell index: lower indices correspond to lower RRC indices of corresponding cell
Set j = 0 – HARQ-ACK bit index

DL
Set N cells to the number of cells configured by higher layers for the UE
DL
while c < N cells
if transmission mode configured in cell c {1,2,5,6,7} – 1 bit HARQ-ACK feedback for this cell
o ACK
j  HARQ-ACK bit of this cell
j=j+1
else
if the UE is not configured with spatial bundling on PUSCH by higher layers o ACK
j  HARQ-ACK bit
corresponding to the first codeword of this cell
j=j+1
o ACK
j  HARQ-ACK bit corresponding to the second codeword of this cell
j=j+1
else
o ACK
j  binary AND operation of the HARQ-ACK bits corresponding to the first and second codewords of
this cell
j=j+1
end if
end if
c=c+1
end while
For the aggregation of more than one DL cell including a primary cell using FDD and at least one secondary cell using
ACK
TDD, the bit sequence o0 o1ACK ,..., oOACK
ACK
1
is the result of the concatenation of HARQ-ACK bits for one or
DL DL
multiple DL cells. Define N cells as the number of cells configured by higher layers for the UE and Bc as the number
of subframes for which the UE needs to feed back HARQ-ACK bits in UL subframe n for the c-th serving cell. For a
cell using TDD, the subframes are determined by the DL-reference UL/DL configuration if the UE is configured with
higher layer parameter eimta-HARQ-ReferenceConfig, and determined by the UL/DL configuration otherwise. For a
cell using TDD, BcDL  1 if subframe n-4 in the cell is a DL subframe or a special subframe with special subframe
configurations 1/2/3/4/6/7/8/9 and normal downlink CP or a special subframe with special subframe configurations
1/2/3/5/6/7 and extended downlink CP, and BcDL  0 otherwise. For a cell using FDD, BcDL  1 .
3GPP
Release 13 31 3GPP TS 36.212 V13.9.0 (2019-06)
ACK
The bit sequence o0 o1ACK ,..., oOACK
ACK
1
is performed according to the following pseudo-code:

DL
while c < N cells
if Bc  1
DL
o ACK
j  HARQ-ACK bit of this cell
j=j+1
else
if the UE is not configured with spatial bundling on PUSCH by higher layers o ACK
j  HARQ-ACK bit
corresponding to the first codeword of this cell
j=j+1
o ACK
j  HARQ-ACK bit corresponding to the second codeword of this cell
j=j+1
else
o ACK
j  binary AND operation of the HARQ-ACK bits corresponding to the first and second codewords
of this cell
j=j+1
end if
end if
end if
c=c+1
end while
For the cases with TDD primary cell when HARQ-ACK is for the aggregation of one or more DL cells and the UE is
ACK
configured with PUCCH format 3, PUCCH format 4 or PUCCH format 5 [3], the bit sequence o0 o1ACK ,..., oOACK
ACK
1
is the result of the concatenation of HARQ-ACK bits for the one or more DL cells configured by higher layers and the
multiple subframes as defined in [3].
DL
Define N cells as the number of cells configured by higher layers for the UE and BcDL as the number of subframes for
which the UE needs to feed back HARQ-ACK bits as defined in Subclause 7.3 of [3].
The number of HARQ-ACK bits for the UE to convey if it is configured with PUCCH format 3, PUCCH format 4 or
PUCCH format 5 is computed as follows:
Set k = 0 – counter of HARQ-ACK bits
Set c=0 – cell index: lower indices correspond to lower RRC indices of corresponding cell
DL
while c < N cells
3GPP
Release 13 32 3GPP TS 36.212 V13.9.0 (2019-06)
set l = 0;
while l < BcDL
if transmission mode configured in cell c  {1,2,5,6,7} -- 1 bit HARQ-ACK feedback for this cell
k=k+1
else
k=k+2
end if
l = l+1
end while
c=c+1
end while
When PUCCH format 3 is configured, if k ≤ 20 when TDD is used in all the configured serving cell(s) of the UE, or if k
≤ 21 when FDD is used in at least one of the configured serving cells with TDD primary cell; or when PUCCH format 4
or PUCCH format 5 is configured and when the UE is not configured with spatial bundling on PUSCH by higher layers,
the multiplexing of HARQ-ACK bits is performed according to the following pseudo-code:

DL
while c < N cells
set l = 0;
while l < BcDL
o~jACK  ocACK
,l HARQ-ACK bit of this cell as defined in Subclause 7.3 of [3]
j=j+1
else
[o~jACK , o~jACK
1 ]  [oc , 2l , oc , 2l 1 ] HARQ-ACK bits of this cell as defined in Subclause 7.3 of [3]
ACK ACK
j=j+2
end if
l = l+1
end while
c=c+1
end while
When PUCCH format 3 is configured, if k > 20 when TDD is used in all the configured serving cell(s) of the UE, or if k
> 21 when FDD is used in at least one of the configured serving cells with TDD primary cell, spatial bundling is applied
to all subframes in all cells; or when PUCCH format 4 or PUCCH format 5 is configured and when the UE is
configured with spatial bundling on PUSCH by higher layers, the multiplexing of HARQ-ACK bits is performed
according to the following pseudo-code:
3GPP
Release 13 33 3GPP TS 36.212 V13.9.0 (2019-06)

DL
while c < N cells
set l = 0;
while l < BcDL
if transmission mode configured in cell c  {1,2,5,6,7} – 1 bit HARQ-ACK feedback for this cell
o~jACK  ocACK
, l HARQ-ACK bit of this cell as defined in Subclause 7.3 of [3]
j=j+1
else
o~jACK  ocACK
,l binary AND operation of the HARQ-ACK bits corresponding to the first and second
codewords of this cell as defined in Subclause 7.3 of [3]
j=j+1
end if
l = l+1
end while
c=c+1
end while
For O
ACK
 11 or O
ACK
 22 , the bit sequence o0ACK o1ACK ,...,oOACK
ACK
1
is obtained by setting oi
ACK
 oi ACK .
For 11  o  22 , the bit sequence o0ACK o1ACK ,...,oOACK is obtained by setting oi / 2  oi

ACK ACK ACK
ACK
1
if i is even and
oACK
O ACK / 2  ( i 1) / 2
 oi ACK if i is odd.
 
For the cases with TDD primary cell when HARQ-ACK is for the aggregation of two DL cells and the UE is configured
with PUCCH format 1b with channel selection, the bit sequence o0ACK o1ACK ,...,oOACK
ACK
1
is obtained as described in
subclause 7.3 of [3].
For TDD HARQ-ACK bundling, a bit sequence q~0ACK , q~1ACK , q~2ACK ,..., q~QACK
ACK 1
is obtained by concatenation of
multiple encoded HARQ-ACK blocks where Q ACK is the total number of coded bits for all the encoded HARQ-ACK
blocks. The last concatenation of the encoded HARQ-ACK block may be partial so that the total bit sequence length is

equal to QACK . A scrambling sequence w0ACK w1ACK w2ACK w3ACK  is then selected from Table 5.2.2.6-A with index
i  N bundled  1 mod 4 , where N bundled is determined as described in subclause 7.3 of [3]. The bit sequence
q 0ACK , q1ACK , q 2ACK ,...,qQACK
ACK 1
is then generated by setting m  1 if HARQ-ACK consists of 1-bit and m  3 if
HARQ-ACK consists of 2-bits and then scrambling q~0ACK , q~1ACK , q~2ACK ,..., q~QACK
ACK 1
as follows
Set i ,k to 0
while i  QACK
if q~i ACK  y // place-holder repetition bit
3GPP
Release 13 34 3GPP TS 36.212 V13.9.0 (2019-06)

qiACK  q~iACK
1  wACK 
k / m  mod 2
k  (k  1) mod 4m
else
if q~i ACK  x // a place-holder bit
qiACK  q~i ACK

else // coded bit

qiACK  q~i ACK  wACK 
k / m  mod 2
k  (k  1) mod 4m
end if
i  i 1
end while
Table 5.2.2.6-A: Scrambling sequence selection for TDD HARQ-ACK bundling.
i wACK
0 w1ACK w2ACK w3ACK 
0 [1 1 1 1]
1 [1 0 1 0]
2 [1 1 0 0]
3 [1 0 0 1]
When HARQ-ACK information is to be multiplexed with UL-SCH at a given PUSCH, the HARQ-ACK information is
multiplexed in all layers of all transport blocks of that PUSCH, For a given transport block, the vector sequence output
of the channel coding for HARQ-ACK information is denoted by q ACK , q ACK ,...,q ACK

, where q ACK ,
0 1 Q ACK 1 i
i  0,...,QACK  1 are column vectors of length Qm  N L  and where QACK  Q ACK / Qm is obtained as follows:
Set i ,k to 0
while i  QACK
 [qiACK ...qiACK
ACK
qˆ k Qm 1 ] -- temporary row vector
NL
   
 [qˆ kACK qˆ kACK ]T -- replicating the row vector q̂
ACK
q kACK NL times and transposing into a column vector
k
i  i  Qm
k  k 1
end while
where N L is the number of layers onto which the UL-SCH transport block is mapped.
For rank indication (RI) (RI only, joint report of RI and i1, joint report of CRI and RI, joint report of CRI, RI and i1,
joint report of CRI, RI, and PTI, and joint report of RI and PTI) or CRI
3GPP
Release 13 35 3GPP TS 36.212 V13.9.0 (2019-06)
- The corresponding bit widths for CRI feedback for PDSCH transmissions are given by Tables 5.2.2.6.1-2A,
5.2.2.6.2-3A, 5.2.2.6.3-3A, 5.2.3.3.1-3E, and 5.2.3.3.2-4E,
- The corresponding bit widths for RI feedback for PDSCH transmissions are given by Tables 5.2.2.6.1-2,
5.2.2.6.1-2B, 5.2.2.6.2-3, 5.2.2.6.2-3B, 5.2.2.6.3-3, 5.2.2.6.3-3B, 5.2.3.3.1-3, 5.2.3.3.1-3A, 5.2.3.3.1-3B,
5.2.3.3.1-3C, 5.2.3.3.1-3D, 5.2.3.3.2-4, and 5.2.3.3.2-4A, 5.2.3.3.2-4B, 5.2.3.3.2-4C, 5.2.3.3.2-4D which are
determined assuming the maximum number of layers as follows:
- If the maxLayersMIMO-r10 is configured for the DL cell, the maximum number of layers is determined
according to maxLayersMIMO-r10 for the DL cell
- Else,
- If the UE is configured with transmission mode 9, and the supportedMIMO-CapabilityDL-r10 field is

included in the UE-EUTRA-Capability, the maximum number of layers is determined according to the
minimum of the configured number of CSI-RS ports and the maximum of the reported UE downlink
MIMO capabilities for the same band in the corresponding band combination.
- If the UE is configured with transmission mode 9, and higher layer parameter eMIMO-Type, and eMIMO-
Type is set to 'CLASS B' with K>1, and RI and CRI are transmitted in the same reporting instance, and
the supportedMIMO-CapabilityDL-r10 field is included in the UE-EUTRA-Capability, the maximum
number of layers is determined according to the minimum of the maximum of number of antenna port of
the configured CSI-RS resources and the maximum of the reported UE downlink MIMO capabilities for
the same band in the corresponding band combination,.
- If the UE is configured with transmission mode 9, and the supportedMIMO-CapabilityDL-r10 field is not
included in the UE-EUTRA-Capability, the maximum number of layers is determined according to the
minimum of the configured number of CSI-RS ports and ue-Category (without suffix).
- If the UE is configured with transmission mode 9, and higher layer parameter eMIMO-Type, and eMIMO-
Type is set to 'CLASS B' with K>1, and RI and CRI are transmitted in the same reporting instance, and
the supportedMIMO-CapabilityDL-r10 field is not included in the UE-EUTRA-Capability, the maximum
number of layers is determined according to the minimum of the maximum of number of antenna port of
the configured CSI-RS resources and ue-Category (without suffix).
included in the UE-EUTRA-Capability, the maximum number of layers for each CSI process is
determined according to the minimum of the configured number of CSI-RS ports for that CSI process and
the maximum of the reported UE downlink MIMO capabilities for the same band in the corresponding
band combination.
- If the UE is configured with transmission mode 10, and higher layer parameter eMIMO-Type, and
eMIMO-Type is set to 'CLASS B' with K>1, and RI and CRI are transmitted in the same reporting
instance, and the supportedMIMO-CapabilityDL-r10 field is included in the UE-EUTRA-Capability, the
maximum number of layers for each CSI process is determined according to the minimum of the
maximum of number of antenna port of the configured CSI-RS resources in that CSI process and the
maximum of the reported UE downlink MIMO capabilities for the same band in the corresponding band
combination.
not included in the UE-EUTRA-Capability, the maximum number of layers for each CSI process is
determined according to the minimum of the configured number of CSI-RS ports for that CSI process and
ue-Category (without suffix).
- If the UE is configured with transmission mode 10, and higher layer parameter eMIMO-Type, and
eMIMO-Type is set to 'CLASS B' with K>1, and RI and CRI are transmitted in the same reporting
instance, and the supportedMIMO-CapabilityDL-r10 field is not included in the UE-EUTRA-Capability,
the maximum number of layers for each CSI process is determined according to the minimum of the
maximum of number of antenna port of the configured CSI-RS resources in that CSI process and ue-
Category (without suffix).
- Otherwise the maximum number of layers is determined according to the minimum of the number of
PBCH antenna ports and ue-Category (without suffix).
3GPP
Release 13 36 3GPP TS 36.212 V13.9.0 (2019-06)
- If RI feedback consists of 1-bit of information, i.e., [o0RI ] , it is first encoded according to Table 5.2.2.6-3. The
[o0RI ] to RI mapping is given by Table 5.2.2.6-5.
- If RI feedback consists of 2-bits of information, i.e., [o0RI o1RI ] with o0RI corresponding to MSB of 2-bit input
and o1RI corresponding to LSB, it is first encoded according to Table 5.2.2.6-4 where o2RI  (o0RI  o1RI ) mod 2 .
The [o0RI o1RI ] to RI mapping is given by Table 5.2.2.6-6.
Table 5.2.2.6-3: Encoding of 1-bit RI.
Qm Encoded RI
2 [o0RI y]
4 [o0RI y x x]
6 [o0RI y x x x x ]
Table 5.2.2.6-4: Encoding of 2-bit RI.
Qm Encoded RI
2
[o0RI o1RI o2RI o0RI o1RI o2RI ]
4
[o0RI o1RI x x o2RI o0RI x x o1RI o2RI x x]
6
[o0RI o1RI x x x x o2RI o0RI x x x x o1RI o2RI x x x x]
Table 5.2.2.6-5: o0RI to RI mapping.

RI
o0RI
0 1
1 2
Table 5.2.2.6-6: o0RI , o1RI to RI mapping.

RI
o0RI , o1RI
0, 0 1
0, 1 2
1, 0 3
1, 1 4
Table 5.2.2.6-7: o0RI , o1RI , o2RI to RI mapping.
o0RI , o1RI , o 2RI RI

0, 0, 0 1
0, 0, 1 2
0, 1, 0 3
0, 1, 1 4
1, 0, 0 5
1, 0, 1 6
1, 1, 0 7
1, 1, 1 8
3GPP
Release 13 37 3GPP TS 36.212 V13.9.0 (2019-06)
- If RI feedback for a given DL cell consists of 3-bits of information, i.e., [o0RI o1RI o2RI ] with o0RI corresponding
to MSB of 3-bit input and o2RI corresponding to LSB. The [o0RI o1RI o 2RI ] to RI mapping is given by Table
5.2.2.6-7.
- If RI feedback consists of 3  O RI  11 bits of information, i.e., [o0RI o1RI ,...,oORIRI 1 ] , then a coded bit sequence
[q~ RI q~ RI ,...,q~ RI ] is obtained by using the bit sequence [o RI o RI ,...,o RI ] as the input to the channel coding
0 1 31 0 1 O RI 1
block described in subclause 5.2.2.6.4.
- If RI feedback consists of 11  O RI  22 bits of information as a result of the aggregation of RI bits

corresponding to multiple DL cells or multiple CSI processes, i.e., [o0RI o1RI ,...,oORIRI 1 ] , then the coded bit
sequence q 0RI , q1RI , q 2RI ,...,qQRIRI 1 is obtained by using the bit sequence [o0RI o1RI ,...,oORIRI 1 ] as the input to the
channel coding block described in subclause 5.2.2.6.5.
- If RI feedback consists of O RI  22 bits of information as a result of the aggregation of RI bits corresponding to

multiple DL cells or multiple CSI processes, i.e., [o0RI o1RI ,...,oORIRI 1 ] , then the coded bit sequence is denoted by
q 0RI , q1RI , q 2RI ,...,qQRIRI 1 . The CRC attachment, channel coding and rate matching of the HARQ-ACK bits are
performed according to subclauses 5.1.1 setting L to 8 bits, 5.1.3.1 and 5.1.4.2, respectively. The input bit
sequence to the CRC attachment operation is [o0RI o1RI ,...,oORIRI 1 ] . The output bit sequence of the CRC
attachment operation is the input bit sequence to the channel coding operation. The output bit sequence of the
channel coding operation is the input bit sequence to the rate matching operation.
- A UE capable of supporting only up to 5 serving cells is not expected to support CRI/RI payload larger than 22
bits.
The "x" and "y" in Table 5.2.2.6-3 and 5.2.2.6-4 are placeholders for [2] to scramble the RI bits in a way that maximizes
the Euclidean distance of the modulation symbols carrying rank information.
For the case where RI feedback for more than one DL cell is to be reported, the RI report for each DL cell is
concatenated prior to coding in increasing order of cell index.
For the case where RI feedback for more than one CSI process is to be reported, the RI reports are concatenated prior to
coding first in increasing order of CSI process index for each DL cell and then in increasing order of cell index.
For the case where RI feedback consists of one or two bits of information the bit sequence q 0RI , q1RI , q 2RI ,...,qQRI 1 is
RI
obtained by concatenation of multiple encoded RI blocks where Q RI is the total number of coded bits for all the
encoded RI blocks. The last concatenation of the encoded RI block may be partial so that the total bit sequence length is
equal to Q RI .
For the case where RI feedback consists of 3  O RI  11 bits of information, the bit sequence q 0RI , q1RI , q 2RI ,...,qQRIRI 1 is
obtained by the circular repetition of the bit sequence q~ RI q~ RI ,...,q~ RI so that the total bit sequence length is equal
0 1 31
to Q RI .
For the case where CRI feedback is to be reported, the same procedures for RI are applied for CRI.When rank
information is to be multiplexed with UL-SCH at a given PUSCH, the rank information is multiplexed in all layers of
all transport blocks of that PUSCH. For a given transport block, the vector sequence output of the channel coding for
rank information is denoted by q RI , q RI ,...,q RI   1 are column vectors of length
, where q RI , i  0,...,QRI
0 1  1
QRI i
Qm  N L  and where   QRI / Qm . The vector sequence is obtained as follows:

QRI
Set i, j, k to 0
while i  QRI
qˆ  [qiRI ...qiRI
RI
k Qm 1 ] -- temporary row vector
3GPP
Release 13 38 3GPP TS 36.212 V13.9.0 (2019-06)
NL
 
 [qˆ  qˆ RI ]T -- replicating the row vector q̂ NL times and transposing into a column vector
RI RI
q RI
k k k k
i  i  Qm
k  k 1
end while
where N L is the number of layers onto which the UL-SCH transport block is mapped.
The same processing procedures for RI and RI multiplexing with UL-SCH at a given PUSCH are applied for CRI, using
CRI instead of RI in the equations.
For channel quality control information (CQI and/or PMI denoted as CQI/PMI);
When the UE transmits channel quality control information bits, it shall determine the number of modulation coded
symbols per layer Q  for channel quality information as
  
 PUSCH 

 (O  L )  M PUSCH initial( x )
 N PUSCH initial( x )
  Q ( x)

Q  min 
sc symb offset
, M sc
PUSCH
 N symb  ( x ) 
PUSCH RI
 C ( x ) 1
 Q

  K r( x ) 
m


 r 0  
where
- O is the number of CQI/PMI bits, and

O  11
L is the number of CRC bits given by L  
0
- , and
8 otherwise
QCQI  Qm( x )  Q and  offset   offset , where  offset shall be determined according to [3] depending on the
PUSCH CQI CQI
-
number of transmission codewords for the corresponding PUSCH, and on the uplink power control subframe set
for the corresponding PUSCH when two uplink power control subframe sets are configured by higher layers for
the cell.
- ( x)
If neither RI nor CRI is not transmitted then QRI  0.
The variable "x" in K r( x ) represents the transport block index corresponding to the highest IMCS value indicated by the
initial UL grant. In case the two transport blocks have the same IMCS value in the corresponding initial UL grant, "x =1",
which corresponds to the first transport block. M scPUSCH initial( x ) , C ( x ) , and K r( x ) are obtained from the initial PDCCH
or EPDCCH or MPDCCH for the same transport block. If there is no initial PDCCH or EPDCCH with DCI format 0 or
MPDCCH with DCI format 6-0A/6-0B for the same transport block, M scPUSCH initial( x ) , C ( x ) , and K r( x ) shall be
determined from:
- the most recent semi-persistent scheduling assignment PDCCH or EPDCCH or MPDCCH, when the initial
PUSCH for the same transport block is semi-persistently scheduled, or,
- the random access response grant for the same transport block, when the PUSCH is initiated by the random
access response grant.
PUSCH initial( x )
N symb is the number of SC-FDMA symbols per subframe for initial PUSCH transmission for the same
transport block.
For UL-SCH data information G  N L( x )  N symb

PUSCH

 M scPUSCH  Qm( x )  QCQI  QRI( x ) , where 
- N L( x ) is the number of layers the corresponding UL-SCH transport block is mapped onto, and
3GPP
Release 13 39 3GPP TS 36.212 V13.9.0 (2019-06)
PUSCH
- M sc is the scheduled bandwidth for PUSCH transmission in the current sub-frame for the transport block,
and
PUSCH
- N symb is the number of SC-FDMA symbols in the current PUSCH transmission sub-frame given by
PUSCH
Nsymb  
 2  Nsymb
UL
 
 1  N SRS , where
- N SRS is equal to 1 for non-BL/CE UEs and BL/CE UEs in CEModeA
- if UE configured with one UL cell is configured to send PUSCH and SRS in the same subframe for the
current subframe, or
- if UE transmits PUSCH and SRS in the same subframe for the current subframe in the same serving cell,
or
- if the PUSCH resource allocation for the current subframe even partially overlaps with the cell-specific
SRS subframe and bandwidth configuration defined in subclause 5.5.3 of [2], or
- if the current subframe in the same serving cell is a UE-specific type-1 SRS subframe as defined in
Subclause 8.2 of [3], or
- if the current subframe in the same serving cell is a UE-specific type-0 SRS subframe as defined in
subclause 8.2 of [3] and the UE is configured with multiple TAGs.
- Otherwise N SRS is equal to 0.
In case of CQI/PMI report for more than one DL cell, o0 , o1 , o2 ,...,oO1 is the result of concatenating the CQI/PMI
report for each DL cell in increasing order of cell index. For the case where CQI/PMI feedback for more than one CSI
process is to be reported, o0 , o1 , o2 ,...,oO1 is the result of concatenating the CQI/PMI reports in increasing order of
CSI process index for each DL cell and then in increasing order of cell index.
- If the payload size is less than or equal to 11 bits, the channel coding of the channel quality information is
performed according to subclause 5.2.2.6.4 with input sequence o0 , o1 , o2 ,...,oO1 .
- For payload sizes greater than 11 bits, the CRC attachment, channel coding and rate matching of the channel
quality information is performed according to subclauses 5.1.1, 5.1.3.1 and 5.1.4.2, respectively. The input bit
sequence to the CRC attachment operation is o0 , o1 , o2 ,...,oO1 . The output bit sequence of the CRC attachment
operation is the input bit sequence to the channel coding operation. The output bit sequence of the channel
coding operation is the input bit sequence to the rate matching operation.
The output sequence for the channel coding of channel quality information is denoted by q 0 , q1 , q 2 , q3 ,...,q N L QCQI 1 ,
where N L is the number of layers the corresponding UL-SCH transport block is mapped onto.
5.2.2.6.1 Channel quality information formats for wideband CQI reports

If the parameter CQI-ReportModeAperiodic is configured to the value of rm12 by higher layers [6], the fields and the
corresponding bit widths for channel quality information and rank indication feedback are described as below.
Table 5.2.2.6.1-1, Table 5.2.2.6.1-1A and Table 5.2.2.6.1-1B show the fields and the corresponding bit widths for the
channel quality information feedback for wideband reports for PDSCH transmissions associated with transmission
mode 4, transmission mode 6, transmission mode 8 configured with PMI/RI reporting, transmission mode 9 configured
with PMI/RI reporting with 2/4/8 antenna ports, and transmission mode 10 configured with PMI/RI reporting with 2/4/8
antenna ports, and transmission mode 9/10 configured with PMI/RI reporting with 2/4/8 antenna ports and higher layer
parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' for a CSI process with K>1, and K=1 except with
alternativeCodebookEnabledCLASSB_K1=TRUE. The number of configured CSI-RS resources in a CSI process K is
defined in [3] and alternativeCodebookEnabledCLASSB_K1 is configured by higher layers [6].
Table 5.2.2.6.1-1C and Table 5.2.2.6.1-1D show the fields and the corresponding bit widths for the channel quality
information feedback for wideband reports for PDSCH transmissions associated with transmission mode 9/10
configured with PMI/RI reporting with 8/12/16 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-
Type is set to 'CLASS A'.
3GPP
Release 13 40 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.2.2.6.1-1E shows the fields and corresponding bit widths for the channel quality information feedback for
wideband reports for PDSCH transmissions associated with transmission mode 9/10 configured with PMI/RI reporting
with 2/4/8 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K=1 and
higher layer parameter alternativeCodebookEnabledCLASSB_K1=TRUE configured.
For Table 5.2.2.6.1-1, Table 5.2.2.6.1-1A, Table 5.2.2.6.1-1B, Table 5.2.2.6.1-1C, Table 5.2.2.6.1-D and Table
5.2.2.6.1-1E, N is defined in subclause 7.2 of [3]. For Table 5.2.2.6.1-1C and Table 5.2.2.6.1-D, the codebook
configuration  N1 , N2 , O1 , O2  is defined in [3], and CodebookConfig is configured by higher layers [6]. The
S1 , S 2  in rank 3 and 4 are defined as S1 , S 2   1, 1 for CodebookConfig=1, S1 , S 2   
O1 O2 
parameters , 
 2 2 
S1 , S 2    O1 ,
O2   O 
for CodebookConfig=2,  for CodebookConfig=3, S1 , S 2    O1 , 2  for
 2   4 
CodebookConfig=4. The parameters S1 , S 2  in rank 5 to 8 are defined as S1 , S 2   1, 1 for CodebookConfig=1,
S1 , S 2    1 , 2  for CodebookConfig=2/3/4.

O O
 4 4 
Table 5.2.2.6.1-1: Fields for channel quality information feedback for wideband CQI and subband PMI
reports (transmission mode 4, transmission mode 6, transmission mode 8 configured with PMI/RI
reporting except with alternativeCodeBookEnabledFor4TX-r12=TRUE, transmission mode 9
configured with PMI/RI reporting with 2/4 antenna ports except with
alternativeCodeBookEnabledFor4TX-r12=TRUE, transmission mode 10 configured with PMI/RI
reporting with 2/4 antenna ports except with alternativeCodeBookEnabledFor4TX-r12=TRUE, and
transmission mode 9/10 configured with PMI/RI reporting and higher layer parameter eMIMO-Type,
and eMIMO-Type is set to 'CLASS B' with 2/4 antenna ports with K>1, and K=1 except with
alternativeCodebookEnabledCLASSB_K1=TRUE, except with alternativeCodeBookEnabledFor4TX-
r12=TRUE).
Field Bit width

2 antenna ports 4 antenna ports
Rank = 1 Rank = 2 Rank = 1 Rank > 1
Wideband CQI codeword 0 4 4 4 4
Precoding matrix indicator 2N N 4N 4N
Table 5.2.2.6.1-1A: Fields for channel quality information feedback for wideband CQI and subband
PMI reports (transmission mode 9 configured with PMI/RI reporting with 8 antenna ports,
transmission mode 10 configured with PMI/RI reporting with 8 antenna ports, and transmission mode
9/10 configured with PMI/RI reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is
set to 'CLASS B' with 8 antenna ports with K>1, and K=1 except with
alternativeCodebookEnabledCLASSB_K1=TRUE).
Bit width
Field
Rank = 1 Rank = 2 Rank = 3 Rank = 4
Wideband first PMI i1 4 4 2 2
Subband second PMI i2 4N 4N 4N 3N
Bit width
Field
Subband second PMI i2 0 0 0 0
3GPP
Release 13 41 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.2.2.6.1-1B: Fields for channel quality information feedback for wideband CQI and subband
PMI reports with 4 antenna ports (transmission mode 8, transmission mode 9 and transmission mode
10 configured with PMI/RI reporting, 4 antenna ports and alternativeCodeBookEnabledFor4TX-
r12=TRUE, and transmission mode 9/10 configured with PMI/RI reporting and higher layer parameter
eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with 4 antenna ports with K>1, and K=1 except
with alternativeCodebookEnabledCLASSB_K1=TRUE, with alternativeCodeBookEnabledFor4TX-
r12=TRUE)
Bit width
Field
Table 5.2.2.6.1-1C: Fields for channel quality information feedback for wideband CQI and subband
PMI reports (transmission mode 9/10 configured with PMI/RI reporting and higher layer parameter
eMIMO-Type, and eMIMO-Type is set to 'CLASS A' with codebook configuration ( N1, N2 , O1, O2 ) and
CodebookConfig=1)
Bit width
Field
Rank = 1 Rank = 2 Rank =3 Rank =4
Wideband
CQI 4 4 4 4
codeword 0
Wideband
CQI 0 4 4 4
codeword 1
  N1O1    7  N 2    N1O1    7  N 2 
log 2 N1O1  log 2 N1O1 
Wideband
log 2      log 2     
first PMI i1,1   S1    3    S1    3 
Wideband
first PMI i1,2 log 2 N 2O2  log 2 N 2O2  log 2  N 2O2  log 2  N 2O2 
Subband
second PMI 2N 2N N N
i2
Bit width
Field
Wideband
CQI 4 4 4 4
codeword 0
Wideband
CQI 4 4 4 4
codeword 1
Wideband
first PMI i1,1
log 2  N1O1 / S1  log 2  N1O1 / S1  log 2  N1O1 / S1  log 2  N1O1 / S1 
log 2  N 2O2 / S2  log 2  N 2O2 / S2  log 2  N 2O2 / S2  log 2  N 2O2 / S2 
Wideband
first PMI i1,2
Subband
second PMI 0 0 0 0
i2
Table 5.2.2.6.1-1D: Fields for channel quality information feedback for wideband CQI and subband
PMI reports (transmission mode 9/10 configured with higher layer parameter eMIMO-Type, and
eMIMO-Type is set to 'CLASS A' with codebook configuration ( N1, N2 , O1, O2 ) and CodebookConfig=2/3/4)
Bit width
Field
3GPP
Release 13 42 3GPP TS 36.212 V13.9.0 (2019-06)
Wideband
CQI 4 4 4 4
codeword 0
Wideband
CQI 0 4 4 4
codeword 1
Wideband   N1O1    7  N 2    N1O1    7  N 2 
first PMI log 2 N1O1 / 2 log 2 N1O1 / 2 log 2      log 2     
i1,1   S1    3    S1    3 
Wideband   N 2O2     N 2O2  
first PMI log 2 N 2O2 / 2 log 2 N 2O2 / 2 log 2  S   log 2  S  
i1,2   2    2 
Subband
second PMI 4N 4N 4N 3N
i2
Bit width
Field
Rank = 5 Rank = 6 Rank = 7 Rank= 8
Wideband
CQI 4 4 4 4
codeword 0
Wideband
CQI 4 4 4 4
codeword 1
Wideband
first PMI log 2  N1O1 / S1  log 2  N1O1 / S1  log 2  N1O1 / S1  log 2  N1O1 / S1 
i1,1
Wideband
first PMI log 2  N 2O2 / S2  log 2  N 2O2 / S2  log 2  N 2O2 / S2  log 2  N 2O2 / S2 
i1,2
Subband
second PMI 0 0 0 0
i2
Table 5.2.2.6.1-1E: Fields for channel quality information feedback for wideband CQI and subband
PMI reports (transmission mode 9/10 configured with PMI/RI reporting and higher layer parameter
eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with 2/4/8 antenna ports with K=1 with
alternativeCodebookEnabledCLASSB_K1=TRUE)
Field Bit width

Rank = 1 Rank = 2 Rank = 1 Rank =2 Rank =3 Rank =4
Wideband CQI codeword 0 4 4 4 4 4 4
Precoding matrix indicator 2N N 3N 3N 2N N
Field Bit width
8 antenna ports
Rank = 1 Rank = 2 Rank = 3 Rank =4 Rank =5~8
Wideband CQI codeword 0 4 4 4 4 4
Precoding matrix indicator 4N 4N 4N 3N 0
If the parameter CQI-ReportModeAperiodic is configured to the value of rm10-v13xy by higher layers [6], the fields and
the corresponding bit widths for channel quality information and rank indication feedback are described as below.
Table 5.2.2.6.1-1F shows the fields and the corresponding bit width for the channel quality information feedback for
higher layer configured report for PDSCH transmissions associated with transmission mode 1, transmission mode 2,
transmission mode 3, transmission mode 7, transmission mode 8 configured without PMI/RI reporting, transmission
mode 9 configured without PMI/RI reporting or configured with 1 antenna port, and transmission mode 10 configured
without PMI/RI reporting or configured with 1 antenna port.
3GPP
Release 13 43 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.2.2.6.1-1G shows the fields and the corresponding bit width for the channel quality information feedback for
higher layer configured report for PDSCH transmissions associated with transmission mode 9/10 configured without
PMI reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with 2/4/8 antenna ports.
Table 5.2.2.6.1-1F: Fields for channel quality information feedback for wideband CQI reports
(transmission mode 1, transmission mode 2, transmission mode 3, transmission mode 7,
transmission mode 8 configured without PMI/RI reporting, transmission mode 9 configured without
PMI/RI reporting or configured with 1 antenna port, and transmission mode 10 configured without
PMI/RI reporting or configured with 1 antenna port)
Field Bit width

Wide-band CQI 4
Table 5.2.2.6.1-1G Fields for channel quality information feedback for wideband CQI reports
(transmission mode 9/10 configured without PMI reporting and higher layer parameter eMIMO-Type,
and eMIMO-Type is set to 'CLASS B' with 2/4/8 antenna ports)
Field Bit width

Rank = 1 Rank > 1
Wide-band CQI codeword 0 4 4
If the parameter CQI-ReportModeAperiodic is configured to the value of rm11-v13xx by higher layers [6], the fields and
the corresponding bit widths for channel quality information and rank indication feedback are described as below.
Table 5.2.2.6.1-1H, Table 5.2.2.6.1-1I and Table 5.2.2.6.1-1J show the fields and the corresponding bit widths for the
channel quality information feedback for higher layer configured report for PDSCH transmissions associated with
transmission mode 4, transmission mode 5, transmission mode 6, transmission mode 8 configured with PMI/RI
reporting, transmission mode 9 configured with PMI/RI reporting with 2/4/8 antenna ports, transmission mode 10
configured with PMI/RI reporting with 2/4/8 antenna ports, and transmission mode 9/10 configured with PMI/RI
reporting with 2/4/8 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with
K>1, and K=1 except with alternativeCodebookEnabledCLASSB_K1=TRUE. The number of configured CSI-RS
resources in a CSI process K is defined in [3] and alternativeCodebookEnabledCLASSB_K1 is configured by higher
layers [6].
Table 5.2.2.6.1-1J-1 and Table 5.2.2.6.1-1J-2 show the fields and the corresponding bit widths for the channel quality
information feedback for higher layer configured report for PDSCH transmissions associated with transmission mode
9/10 configured with PMI/RI reporting with 8/12/16 antenna ports and higher layer parameter eMIMO-Type, and
eMIMO-Type is set to 'CLASS A'.
Table 5.2.2.6.1-1J-3 shows the fields and the corresponding bit widths for the channel quality information feedback for
higher layer configured report for PDSCH transmissions associated with transmission mode 9/10 configured with
PMI/RI reporting with 2/4/8 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS
B' with K=1 and alternativeCodebookEnabledCLASSB_K1=TRUE.
For Table 5.2.2.6.1-1H, Table 5.2.2.6.1-1I, Table 5.2.2.6.1-1J, Table 5.2.2.6.1-1J-1, Table 5.2.2.6.1-1J-2 and Table
5.2.2.6.1-1J-3, N is defined in subclause 7.2 of [3]. For Table 5.2.2.6.1-1J-1 and Table 5.2.2.6.1-1J-2, the codebook
O1 O2 
parameters , 
 2 2 
S1 , S 2    O1 ,
O2   O 
 2   4 

O O
 4 4 
3GPP
Release 13 44 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.2.2.6.1-1H: Fields for channel quality information feedback for wideband CQI reports
(transmission mode 4, transmission mode 5, transmission mode 6, transmission mode 8 configured
with PMI/RI reporting except with alternativeCodeBookEnabledFor4TX-r12=TRUE, transmission mode
9 configured with PMI/RI reporting with 2/4 antenna ports except with
transmission mode 9/10 configured with PMI/RI reporting with 2/4 antenna ports and higher layer
parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K>1, and K=1 except with
r12=TRUE)
Field Bit width

Wide-band CQI codeword 0 4 4 4 4
Precoding matrix indicator 2 1 4 4
Table 5.2.2.6.1-1I: Fields for channel quality information feedback for wideband CQI reports
(transmission mode 9 configured with PMI/RI reporting with 8 antenna ports, transmission mode 10
configured with PMI/RI reporting with 8 antenna ports, and transmission mode 9/10 configured with
PMI/RI reporting with 8 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is
set to 'CLASS B' with K>1, and K=1 except with alternativeCodebookEnabledCLASSB_K1=TRUE).
Bitwidth
Field
Wideband second PMI i2 4 4 4 3
Field Bitwidth
Table 5.2.2.6.1-1J: Fields for channel quality information feedback for wideband CQI reports with 4
antenna ports (transmission modes 8, 9 and 10 configured with PMI/RI reporting, 4 antenna ports and
alternativeCodeBookEnabledFor4TX-r12=TRUE, and transmission mode 9/10 configured with PMI/RI
reporting with 4 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set to
'CLASS B' with K>1, and K=1 except with alternativeCodebookEnabledCLASSB_K1=TRUE, with
alternativeCodeBookEnabledFor4TX-r12=TRUE)
Bitwidth
Field
3GPP
Release 13 45 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.2.2.6.1-1J-1: Fields for channel quality information feedback for wideband CQI reports
(transmission mode 9/10 configured with higher layer parameter eMIMO-Type, and eMIMO-Type is set
to 'CLASS A' with codebook configuration ( N1, N2 , O1, O2 ) and CodebookConfig=1)
Bit width
Field
Wideband
CQI
4 4 4 4
codeword
0
Wideband
CQI
0 4 4 4
codeword
1
Wideband   N1O1    7  N 2    N1O1    7  N 2 
first PMI log 2 N1O1  log 2 N1O1  log 2      log 2     
i1,1   S1    3    S1    3 
Wideband
first PMI log 2 N 2O2  log 2 N 2O2  log 2  N 2O2 / S2  log 2  N 2O2 / S2 
i1,2
Wideband
second 2 2 1 1
PMI i2
Bit width
Field
Wideband
CQI
4 4 4 4
codeword
0
Wideband
CQI
4 4 4 4
codeword
1
Wideband
i1,1
Wideband
i1,2
Wideband
second 0 0 0 0
PMI i2
3GPP
Release 13 46 3GPP TS 36.212 V13.9.0 (2019-06)
to 'CLASS A' with codebook configuration ( N1, N2 , O1, O2 ) and CodebookConfig=2/3/4)
Bit width
Field
Wideband
CQI codeword 4 4 4 4
0
Wideband
1
  N1O1    7  N 2    N1O1    7  N 2 
Wideband first
log 2 N1O1 / 2 log 2 N1O1 / 2 log 2      log 2     
PMI i1,1
  S1    3    S1    3 
  N 2O2     N 2O2  
Wideband first
PMI i1,2 log 2 N2O2 / 2 log 2 N2O2 / 2 log 2   log 2  
  S2     S2  
Wideband
4 4 4 3
second PMI i2
Bit width
Field
Wideband
0
Wideband
1
log 2  N1O1 / S1  log 2  N1O1 / S1  log 2  N1O1 / S1  log 2  N1O1 / S1 
Wideband first
PMI i1,1
Wideband first
PMI i1,2
log 2  N 2O2 / S2  log 2  N 2O2 / S2  log 2  N 2O2 / S2  log 2  N 2O2 / S2 
Wideband
0 0 0 0
second PMI i2
to 'CLASS B' with 2/4/8 antenna ports with K=1 and alternativeCodebookEnabledCLASSB_K1=TRUE)
Field Bit width

Precoding matrix indicator 2 1 3 3 2 1
Field Bit width
8 antenna ports
Rank = 1 Rank = 2 Rank = 3 Rank =4 Rank =5 to Rank = 8
Precoding matrix indicator 4 4 4 3 0
Table 5.2.2.6.1-2 shows the fields and the corresponding bit width for the rank indication feedback for wideband CQI
reports for PDSCH transmissions associated with transmission mode 3, transmission mode 4, transmission mode 8
configured with PMI/RI reporting, transmission mode 9 configured with PMI/RI reporting with 2/4/8 antenna ports,
transmission mode 10 configured with PMI/RI reporting with 2/4/8 antenna ports, and transmission mode 9/10
configured with PMI/RI reporting with 2/4/8 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type
is set to 'CLASS B' with K=1, transmission mode 9/10 configured with PMI/RI reporting with 8/12/16 antenna ports
and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS A', and transmission mode 9/10
configured without PMI reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with
K=1 with 2/4/8 antenna ports.
3GPP
Release 13 47 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.2.2.6.1-2A shows the fields and the corresponding bit width for the CRI feedback for wideband CQI reports for
PDSCH transmissions associated with transmission mode 9/10 configured with PMI/RI reporting for Class B CSI
reporting with K>1 CSI-RS resources and one port per CSI-RS resource.
Table 5.2.2.6.1-2B shows the fields and the corresponding bit width for the joint CRI and RI feedback for wideband
CQI reports for PDSCH transmissions associated with transmission mode 9/10 configured without PMI reporting and
higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K>1, and transmission mode 9/10
configured with PMI/RI reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with
K>1 CSI-RS resources and more than one ports for at least one CSI-RS resource.
Table 5.2.2.6.1-2: Fields for rank indication feedback for wideband CQI reports (transmission mode 3,
transmission mode 4, transmission mode 8 configured with PMI/RI reporting, transmission mode 9
configured with PMI/RI reporting with 2/4/8 antenna ports, and transmission mode 10 configured with
PMI/RI reporting with 2/4/8 antenna ports, transmission mode 9/10 configured with PMI/RI reporting
with 2/4/8 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS
B' with K=1, and transmission mode 9/10 configured with PMI/RI reporting with 8/12/16 antenna ports
and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS A', and transmission
mode 9/10 configured without PMI reporting and higher layer parameter eMIMO-Type, and eMIMO-
Type is set to 'CLASS B' with K=1 with 2/4/8 antenna ports).
Bit width
4 antenna ports 8/12/16 antenna ports
Field 2 antenna
Max 1 or 2 Max 4 Max 1 or 2 Max 4 Max 8
ports
layers layers layers layers layers
Rank 1 2 3
1 1 2
indication
Table 5.2.2.6.1-2A: Fields for CRI feedback for wideband CQI reports
(transmission mode 9/10 configured with PMI/RI reporting for Class B CSI reporting with K>1 CSI-RS
resources and 1 port per CSI-RS resource).
Bit width
Field
K=2 K=3 and K=4 K=5 to K=8
CRI 1 2 3
Table 5.2.2.6.1-2B: Fields for joint CRI and RI feedback for wideband CQI reports (transmission mode
9/10 configured without PMI reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is
set to 'CLASS B' with K>1, and transmission mode 9/10 configured with PMI/RI reporting and higher
layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K>1 CSI-RS resources and >1
ports for at least one CSI-RS resource).
Bit width
Field 2 antenna
ports
CRI log 2 K  log 2 K  log 2 K  log 2 K  log 2 K  log 2 K 
Rank 1 2 3
1 1 2
indication
The channel quality bits in Table 5.2.2.6.1-1, Table 5.2.2.6.1-1A, Table 5.2.2.6.1-1B, Table 5.2.2.6.1-1C, Table
5.2.2.6.1-1D, Table 5.2.2.6.1-1E, Table 5.2.2.6.1-1F, Table 5.2.2.6.1-1G, Table 5.2.2.6.1-1H, Table 5.2.2.6.1-1I, Table
5.2.2.6.1-1J, Table 5.2.2.6.1-1J-1, Table 5.2.2.6.1-1J-2 Table 5.2.2.6.1-1J-3 and Table 5.2.2.6.1-2B form the bit
sequence o0 , o1 , o2 ,...,oO1 with o0 corresponding to the first bit of the first field in the table, o1 corresponding to the
second bit of the first field in the table, and oO 1 corresponding to the last bit in the last field in the table. The field of
PMI shall be in the increasing order of the subband index [3]. The first bit of each field corresponds to MSB and the last
bit LSB. The RI bits sequence in Table 5.2.2.6.1-2 and Table 5.2.2.6.1-2B and the CRI sequence in Table 5.2.2.6.1-2A
are encoded according to subclause 5.2.2.6.
3GPP
Release 13 48 3GPP TS 36.212 V13.9.0 (2019-06)
For transmission mode 9/10 configured with Class B CSI reporting and K>1, the number of antenna port in Table
5.2.2.6.1-2B refers to the maximum number of antenna ports of K CSI-RS resources configured for the CSI-process for
the UE.
5.2.2.6.2 Channel quality information formats for higher layer configured subband CQI
reports
Table 5.2.2.6.2-1 shows the fields and the corresponding bit width for the channel quality information feedback for
higher layer configured report for PDSCH transmissions associated with transmission mode 1, transmission mode 2,
mode 9 configured without PMI/RI reporting or configured with 1 antenna port, and transmission mode 10 configured
without PMI/RI reporting or configured with 1 antenna port. N in Table 5.2.2.6.2-1 is defined in subclause 7.2 of [3].
Table 5.2.2.6.2-1A shows the fields and the corresponding bit width for the channel quality information feedback for
higher layer configured report for PDSCH transmissions associated with transmission mode 9/10 configured without
PMI reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with 2/4/8 antenna ports.
Table 5.2.2.6.2-1: Fields for channel quality information feedback for higher layer configured subband
CQI reports (transmission mode 1, transmission mode 2, transmission mode 3, transmission mode 7,
PMI/RI reporting or configured with 1 antenna port, and transmission mode 10 configured without
PMI/RI reporting or configured with 1 antenna port)
Field Bit width

Wide-band CQI codeword 4
Subband differential CQI 2N
Table 5.2.2.6.2-1A Fields for channel quality information feedback for higher layer configured
subband CQI reports (transmission mode 9/10 configured without PMI reporting and higher layer
parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with 2/4/8 antenna ports)
Field Bit width

Rank = 1 Rank > 1
Subband differential CQI codeword 0 2N 2N
Subband differential CQI codeword 1 0 2N
transmission mode 4, transmission mode 5, transmission mode 6, transmission mode 8 configured with PMI/RI
reporting, transmission mode 9 configured with PMI/RI reporting with 2/4/8 antenna ports, transmission mode 10
configured with PMI/RI reporting with 2/4/8 antenna ports, and transmission mode 9/10 configured with PMI/RI
K>1, and K=1 except with alternativeCodebookEnabledCLASSB_K1=TRUE. The number of configured CSI-RS
resources in a CSI process K is defined in [3] and alternativeCodebookEnabledCLASSB_K1 is configured by higher
layers [6].
Table 5.2.2.6.2-2B-1 and Table 5.2.2.6.2-2B-2 show the fields and the corresponding bit widths for the channel quality
9/10 configured with PMI/RI reporting with 8/12/16 antenna ports and higher layer parameter eMIMO-Type, and
eMIMO-Type is set to 'CLASS A'.
Table5.2.2.6.2-2B-3 shows the fields and the corresponding bit widths for the channel quality information feedback for
PMI/RI reporting with 2/4/8 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS
B' with K=1 and alternativeCodebookEnabledCLASSB_K1=TRUE.
3GPP
Release 13 49 3GPP TS 36.212 V13.9.0 (2019-06)
For Table 5.2.2.6.2-2, Table 5.2.2.6.2-2A, Table 5.2.2.6.2-2B, Table 5.2.2.6.2-2B-1, Table 5.2.2.6.2-2B-2 and Table
5.2.2.6.2-2B-3, N is defined in subclause 7.2 of [3]. For Table 5.2.2.6.2-2B-1 and Table 5.2.2.6.2-2B-2, the codebook
O1 O2 
parameters , 
 2 2 
S1 , S 2    O1 ,
O2   O 
 2   4 

O O
 4 4 
Table 5.2.2.6.2-2: Fields for channel quality information feedback for higher layer configured subband
CQI reports (transmission mode 4, transmission mode 5, transmission mode 6, transmission mode 8
configured with PMI/RI reporting except with alternativeCodeBookEnabledFor4TX-r12=TRUE,
transmission mode 9 configured with PMI/RI reporting with 2/4 antenna ports except with
transmission mode 9/10 configured with PMI/RI reporting with 2/4 antenna ports and higher layer
parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K>1, and K=1 except with
r12=TRUE)
Field Bit width

Subband differential CQI codeword 0 2N 2N 2N 2N
Subband differential CQI codeword 1 0 2N 0 2N
Table 5.2.2.6.2-2A: Fields for channel quality information feedback for higher layer configured
subband CQI reports (transmission mode 9 configured with PMI/RI reporting with 8 antenna ports,
transmission mode 10 configured with PMI/RI reporting with 8 antenna ports, and transmission mode
9/10 configured with PMI/RI reporting with 8 antenna ports and higher layer parameter eMIMO-Type,
and eMIMO-Type is set to 'CLASS B' with K>1, and K=1 except with
Bitwidth
Field
3GPP
Release 13 50 3GPP TS 36.212 V13.9.0 (2019-06)

Subband differential CQI codeword 1 0 2N 2N 2N
Field Bitwidth
Table 5.2.2.6.2-2B: Fields for channel quality information feedback for higher layer configured
subband CQI reports with 4 antenna ports (transmission modes 8, 9 and 10 configured with PMI/RI
reporting, 4 antenna ports and alternativeCodeBookEnabledFor4TX-r12=TRUE, and transmission
mode 9/10 configured with PMI/RI reporting with 4 antenna ports and higher layer parameter eMIMO-
Type, and eMIMO-Type is set to 'CLASS B' with K>1, and K=1 except with
alternativeCodebookEnabledCLASSB_K1=TRUE, with alternativeCodeBookEnabledFor4TX-
r12=TRUE)
Bitwidth
Field
Table 5.2.2.6.2-2B-1: Fields for channel quality information feedback for higher layer configured
subband CQI reports (transmission mode 9/10 configured with higher layer parameter eMIMO-Type,
and eMIMO-Type is set to 'CLASS A' with codebook configuration ( N1, N2 , O1, O2 ) and
CodebookConfig=1)
Bit width
Field
3GPP
Release 13 51 3GPP TS 36.212 V13.9.0 (2019-06)
Wideband
CQI
4 4 4 4
codeword
0
Subband
differential
CQI 2N 2N 2N
2N
codeword
0
Wideband
CQI
0 4 4 4
codeword
1
Subband
differential
CQI 0 2N 2N 2N
codeword
1
Wideband   N1O1    7  N 2    N1O1    7  N 2 
first PMI log 2 N1O1  log 2 N1O1  log 2      log 2     
i1,1   S1    3    S1    3 
Wideband
first PMI log 2 N 2O2  log 2 N 2O2  log 2  N 2O2 / S2  log 2  N 2O2 / S2 
i1,2
Wideband
second 2 2 1 1
PMI i2
Bit width
Field
Wideband
CQI
4 4 4 4
codeword
0
Subband
differential
CQI 2N 2N 2N
2N
codeword
0
Wideband
CQI
4 4 4 4
codeword
1
Subband
differential
CQI 2N 2N 2N
2N
codeword
1
Wideband
first PMI log 2  N1O1 / S1  log 2  N1O1 / S1  log 2  N1O1 / S1  log 2  N1O1 / S1 
i1,1
Wideband
first PMI log 2  N 2O2 / S2  log 2  N 2O2 / S2  log 2  N 2O2 / S2  log 2  N 2O2 / S2 
i1,2
Wideband
second 0 0 0 0
PMI i2
and eMIMO-Type is set to 'CLASS A' with codebook configuration ( N1, N2 , O1, O2 ) and
CodebookConfig=2/3/4)
Bit width
Field
3GPP
Release 13 52 3GPP TS 36.212 V13.9.0 (2019-06)
Wideband
0
Subband
differential
2N 2N 2N
CQI codeword 2N
0
Wideband
1
Subband
differential
0 2N 2N 2N
CQI codeword
1
  N1O1    7  N 2    N1O1    7  N 2 
Wideband first
log 2 N1O1 / 2 log 2 N1O1 / 2 log 2      log 2     
PMI i1,1
  S1    3    S1    3 
  N 2O2     N 2O2  
log 2 N 2O2 / 2 log 2 N 2O2 / 2
Wideband first
PMI i1,2 log 2   log 2  
  S2     S2  
Wideband
4 4 4 3
second PMI i2
Bit width
Field
Wideband
0
Subband
differential
2N 2N 2N
CQI codeword 2N
0
Wideband
1
Subband
differential
2N 2N 2N 2N
CQI codeword
1
Wideband first
PMI i1,1
Wideband first
PMI i1,2
Wideband
0 0 0 0
second PMI i2
3GPP
Release 13 53 3GPP TS 36.212 V13.9.0 (2019-06)
and eMIMO-Type is set to 'CLASS B' with 2/4/8 antenna ports with K=1 and
Field Bit width

Subband differential CQI codeword 0 2N 2N 2N 2N 2N 2N
Subband differential CQI codeword 1 0 2N 0 2N 2N 2N
Precoding matrix indicator 2 1 3 3 2 1
Field Bit width
8 antenna ports
Rank = 1 Rank = 2 Rank = 3 Rank =4 Rank =5 to Rank = 8
Subband differential CQI codeword 0 2N 2N 2N 2N 2N
Subband differential CQI codeword 1 0 2N 2N 2N 2N
Precoding matrix indicator 4 4 4 3 0
Table 5.2.2.6.2-2C, Table 5.2.2.6.2-2D and Table 5.2.2.6.2-2E show the fields and the corresponding bit widths for the
transmission mode 4, transmission mode 6, transmission mode 8 configured with subband PMI/RI reporting,
transmission mode 9 configured with subband PMI/RI reporting with 2/4/8 antenna ports, transmission mode 10
configured with subband PMI/RI reporting with 2/4/8 antenna ports, and transmission mode 9/10 configured with
subband PMI/RI reporting with 2/4/8 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set to
'CLASS B' with K>1 and K=1 except with alternativeCodebookEnabledCLASSB_K1=TRUE. The number of
configured CSI-RS resources in a CSI process K is defined in [3] and alternativeCodebookEnabledCLASSB_K1 is
configured by higher layers [6].
Table 5.2.2.6.2-2E-1 and Table 5.2.2.6.2-2E-2 show the fields and the corresponding bit widths for the channel quality
9/10 configured with subband PMI/RI reporting with 8/12/16 antenna ports and higher layer parameter eMIMO-Type,
and eMIMO-Type is set to 'CLASS A'.
Table5.2.2.6.2-2E-3 shows the fields and the corresponding bit widths for the channel quality information feedback for
subband PMI/RI reporting with 2/4/8 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set to
'CLASS B' with K=1 and alternativeCodebookEnabledCLASSB_K1=TRUE.
For Table 5.2.2.6.2-2C, Table 5.2.2.6.2-2D, Table 5.2.2.6.2-2E, Table 5.2.2.6.2-2E-1, Table 5.2.2.6.2-2E-2 and Table
5.2.2.6.2-2E-3, N is defined in subclause 7.2 of [3]. For 5.2.2.6.2-2E-1 and Table 5.2.2.6.2-2E-2, the codebook
O1 O2 
parameters , 
 2 2 
S1 , S 2    O1 ,
O2   O 
 2   4 

O O
 4 4 
3GPP
Release 13 54 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.2.2.6.2-2C: Fields for channel quality information feedback for higher layer configured
subband CQI and subband PMI reports
(transmission mode 4 and transmission mode 6 configured with subband PMI reporting,
transmission mode 8 configured with subband PMI reporting except with
alternativeCodeBookEnabledFor4TX-r12=TRUE, transmission mode 9 and transmission 10
configured with subband PMI reporting with 2/4 antenna ports except with
alternativeCodeBookEnabledFor4TX-r12=TRUE, and transmission mode 9/10 configured with
subband PMI/RI reporting with 2/4 antenna ports and higher layer parameter eMIMO-Type, and
eMIMO-Type is set to 'CLASS B' with K>1, and K=1 except with
r12=TRUE).
Field Bit width

Rank = 1 Rank = 2 Rank = 1 Rank = 2 Rank = 3 Rank = 4
Wide-band CQI codeword 0 4 4 4 4 4 4
Wide-band CQI codeword 1 0 4 0 4 4 4
Subband differential CQI codeword 1 0 2N 0 2N 2N 2N
Subband precoding matrix indicator 2N N 4N 4N 4N 4N
Table 5.2.2.6.2-2D: Fields for channel quality information feedback for higher layer configured
subband CQI and subband PMI reports with 8 antenna ports (transmission mode 9 configured with
subband PMI reporting, transmission mode 10 configured with subband PMI reporting, and
transmission mode 9/10 configured with subband PMI/RI reporting and higher layer parameter
eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K>1, and K=1 except with
Bitwidth
Field
Field Bitwidth
Table 5.2.2.6.2-2E: Fields for channel quality information feedback for higher layer configured
subband CQI and subband PMI reports with 4 antenna ports (transmission modes 8, 9 and 10
configured with subband PMI reporting, 4 antenna ports and alternativeCodeBookEnabledFor4TX-
r12=TRUE, transmission mode 9/10 configured with subband PMI/RI reporting with 2/4 antenna ports
and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K>1, and K=1 with
except with alternativeCodebookEnabledCLASSB_K1=TRUE, with
Bitwidth
Field
3GPP
Release 13 55 3GPP TS 36.212 V13.9.0 (2019-06)

Table 5.2.2.6.2-2E-1: Fields for channel quality information feedback for higher layer configured
subband CQI reports and subband PMI reports (transmission mode 9/10 configured with higher layer
parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS A' with codebook configuration ( N1, N2 , O1, O2 )
and CodebookConfig=1)
Bitwidth
Field
Wideband CQI
4 4 4 4
codeword 0
Subband
differential CQI 2N 2N 2N 2N
codeword 0
Wideband CQI
0 4 4 4
codeword 1
Subband
differential CQI 0 2N 2N 2N
codeword 1
  N1O1    7  N 2    N1O1    7  N 2 
log 2 N1O1  log 2 N1O1 
Wideband first
log 2      log 2     
PMI i1,1
  S1    3    S1    3 
Wideband first
PMI i1,2 log 2 N 2O2  log 2 N 2O2  log 2  N2O2  log 2  N2O2 
Subband
second PMI i2
2N 2N N N
Bitwidth
Field
Wideband CQI
4 4 4 4
codeword 0
Subband
codeword 0
Wideband CQI
4 4 4 4
codeword 1
Subband
codeword 1
log 2  N1O1 / S1  log 2  N1O1 / S1  log 2  N1O1 / S1  log 2  N1O1 / S1 
Wideband first
PMI i1,1
Wideband first
PMI i1,2
Subband
0 0 0 0
second PMI i2
subband CQI reports and subband PMI reports (transmission mode 9/10 configured with higher layer
parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS A' with codebook configuration ( N1, N2 , O1, O2 )
and CodebookConfig=2/3/4)
Field Bitwidth
3GPP
Release 13 56 3GPP TS 36.212 V13.9.0 (2019-06)
Wideband
CQI
4 4 4 4
codeword
0
Subband
differential
CQI 2N 2N 2N 2N
codeword
0
Wideband
CQI
0 4 4 4
codeword
1
Subband
differential
CQI 0 2N 2N 2N
codeword
1
Wideband   N1O1   7  N 2    N1O1    7  N 2 
first PMI log 2 N1O1 / 2 log 2 N1O1 / 2 log 2  S     3  log 2  S     3 
i1,1   1    1   
Wideband   N 2O2    N 2O2 
first PMI log 2 N 2O2 / 2 log 2 N 2O2 / 2 log 2  S   log 2  S  
i1,2   2    2 
Subband
second 4N 4N 4N 3N
PMI i2
Bitwidth
Field
Wideband
CQI
4 4 4 4
codeword
0
Subband
differential
CQI 2N 2N 2N 2N
codeword
0
Wideband
CQI
4 4 4 4
codeword
1
Subband
differential
CQI 2N 2N 2N 2N
codeword
1
Wideband
i1,1
Wideband
i1,2
Subband
second 0 0 0 0
PMI i2
3GPP
Release 13 57 3GPP TS 36.212 V13.9.0 (2019-06)
subband CQI reports and subband PMI reports (transmission mode 9/10 configured and higher layer
parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with 2/4/8 antenna ports with K=1 and
Field Bit width

Subband differential CQI codeword 1 0 2N 2N 2N 2N 2N
Precoding matrix indicator 2N N 3N 3N 2N N
Field Bit width
8 antenna ports
Rank = 1 Rank = 2 Rank = 3 Rank =4 Rank = 5 to Rank = 8
Subband differential CQI codeword 0 2N 2N 2N 2N 2N

Subband differential CQI codeword 1 0 2N 2N 2N 2N
Precoding matrix indicator 4N 4N 4N 3N 0
Table 5.2.2.6.2-3 shows the fields and the corresponding bit width for the rank indication feedback for higher layer
configured subband CQI reports for PDSCH transmissions associated with transmission mode 3, transmission mode 4,
transmission mode 8 configured with PMI/RI reporting, transmission mode 9 configured with PMI/RI reporting with
2/4/8 antenna ports, transmission mode 10 configured with PMI/RI reporting with 2/4/8 antenna ports, and transmission
mode 9/10 configured with PMI/RI reporting with 2/4/8 antenna ports and higher layer parameter eMIMO-Type, and
eMIMO-Type is set to 'CLASS B' with K=1, transmission mode 9/10 configured with PMI/RI reporting with 8/12/16
antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS A', and transmission mode
9/10 configured without PMI reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B'
with K=1 with 2/4/8 antenna ports.
Table 5.2.2.6.2-3A shows the fields and the corresponding bit width for the CSI-RS resource indication feedback for
higher layer configured subband CQI reports for PDSCH transmissions associated with transmission mode 9/10
configured with 1 antenna port for each CSI-RS resource and higher layer parameter eMIMO-Type, and eMIMO-Type is
set to 'CLASS B' with K>1.
Table 5.2.2.6.2-3B shows the fields and the corresponding bit width for the joint CRI and RI feedback for higher layer
configured subband CQI reports for PDSCH transmissions associated with transmission mode 9/10 configured without
PMI reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K>1, and
transmission mode 9/10 configured with PMI/RI reporting and higher layer parameter eMIMO-Type, and eMIMO-Type
is set to 'CLASS B' with K>1 and 2/4/8 antenna ports.
3GPP
Release 13 58 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.2.2.6.2-3: Fields for rank indication feedback for higher layer configured subband CQI reports
(transmission mode 3, transmission mode 4, transmission mode 8 configured with PMI/RI reporting,
transmission mode 9 configured with PMI/RI reporting with 2/4/8 antenna ports, transmission mode
10 configured with PMI/RI reporting with 2/4/8 antenna ports, transmission mode 9/10 configured with
PMI/RI reporting with 2/4/8 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type
is set to 'CLASS B' with K=1, transmission mode 9/10 configured with PMI/RI reporting with 8/12/16
antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS A', and
transmission mode 9/10 configured without PMI reporting and higher layer parameter eMIMO-Type,
and eMIMO-Type is set to 'CLASS B' with K=1 with 2/4/8 antenna ports).
Bit width
Field 2 antenna
ports
Rank 1 2 3
1 1 2
indication
Table 5.2.2.6.2-3A: Fields for CRI feedback for higher layer configured subband CQI reports
(transmission mode 9/10 configured with 1 antenna port for each CSI-RS resource and higher layer
parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K>1).
Bit width
Field
K=2 K = 3 and K = 4 K = 5 to K = 8
CRI 1 2 3
Table 5.2.2.6.2-3B: Fields for joint CRI and RI feedback for higher layer configured subband CQI
reports (transmission mode 9/10 configured without PMI reporting and higher layer parameter
eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K>1, and transmission mode 9/10 configured
with PMI/RI reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B'
with K>1 and 2/4/8 antenna ports).
Bit width
Field 2 antenna
ports
Rank 1 2 3
1 1 2
indication
The channel quality bits in Table 5.2.2.6.2-1, Table 5.2.2.6.2-2, Table 5.2.2.6.2-2A, Table 5.2.2.6.2-2B, Table 5.2.2.6.2-
2C, Table 5.2.2.6.2-2D, Table 5.2.2.6.2-2E, Table 5.2.2.6.2-2B-1, Table 5.2.2.6.2-2B-2, Table 5.2.2.6.2-2B-3, Table
5.2.2.6.2-2E-1, Table 5.2.2.6.2-2E-2, Table 5.2.2.6.2-2E-3, and Table 5.2.2.6.2-3B form the bit sequence
o0 , o1 , o2 ,...,oO1 with o0 corresponding to the first bit of the first field in each of the tables, o1 corresponding to the
second bit of the first field in each of the tables, and oO 1 corresponding to the last bit in the last field in each of the
tables. The field of the PMI and subband differential CQI shall be in the increasing order of the subband index [3]. The
first bit of each field corresponds to MSB and the last bit LSB. The RI bits sequence in Table 5.2.2.6.2-3, 5.2.2.6.2-3B
and the CRI sequence in Table 5.2.2.6.2-3A are encoded according to subclause 5.2.2.6.
the UE.
5.2.2.6.3 Channel quality information formats for UE selected subband CQI reports
Table 5.2.2.6.3-1 shows the fields and the corresponding bit widths for the channel quality information feedback for UE
selected subband CQI for PDSCH transmissions associated with transmission mode 1, transmission mode 2,
mode 9 configured without PMI/RI reporting or configured with 1 antenna port, transmission mode 10 configured
3GPP
Release 13 59 3GPP TS 36.212 V13.9.0 (2019-06)
without PMI/RI reporting or configured with 1 antenna port, and transmission mode 6 for BL/CE UEs. L in Table
5.2.2.6.3-1 is defined in subclause 7.2 of [3].
Table 5.2.2.6.3-1A shows the fields and the corresponding bit widths for the channel quality information feedback for
UE selected subband CQI for PDSCH transmissions associated with transmission mode 9/10 configured without PMI
reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with 2/4/8 antenna ports.
Table 5.2.2.6.3-1: Fields for channel quality information feedback for UE selected subband CQI
reports (transmission mode 1, transmission mode 2, transmission mode 3, transmission mode 7,
PMI/RI reporting or configured with 1 antenna port, transmission mode 10 configured without PMI/RI
reporting or configured with 1 antenna port, and transmission mode 6 for BL/CE UEs)
Field Bit width

Wide-band CQI codeword 4
Subband differential CQI 2
Position of the M selected subbands L
Table 5.2.2.6.3-1A Fields for channel quality information feedback for UE selected subband CQI
reports (transmission mode 9/10 configured without PMI reporting and higher layer parameter eMIMO-
Type, and eMIMO-Type is set to 'CLASS B' with 2/4/8 antenna ports)
Field Bit width

Rank = 1 Rank >1
Subband differential CQI codeword 0 2 2
Subband differential CQI codeword 1 0 2
Position of the M selected subbands L L
channel quality information feedback for UE selected subband CQI for PDSCH transmissions associated with
transmission mode 4, transmission mode 6, transmission mode 8 configured with PMI/RI reporting, transmission mode
9 configured with PMI/RI reporting with 2/4/8 antenna port, transmission mode 10 configured with PMI/RI reporting
with 2/4/8 antenna ports, and transmission mode 9/10 configured with PMI/RI reporting with 2/4/8 antenna ports and
higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K>1 and K=1 except with
alternativeCodebookEnabledCLASSB_K1=TRUE, where the number of configured CSI-RS resources in a CSI process
K is defined in [3] and alternativeCodebookEnabledCLASSB_K1 is configured by higher layers [6].
Table 5.2.2.6.3-2C and Table 5.2.2.6.3-2D show the fields and the corresponding bit widths for the channel quality
information feedback for UE selected subband CQI for PDSCH transmissions associated with transmission mode 9/10
configured with PMI/RI reporting with 8/12/16 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-
Table 5.2.2.6.3-2E shows the fields and the corresponding bit widths for the channel quality information feedback for
UE selected subband CQI for PDSCH transmissions associated with transmission mode 9/10 configured with PMI/RI
K=1 and alternativeCodebookEnabledCLASSB_K1=TRUE.
For Table 5.2.2.6.3-2, Table 5.2.2.6.3-2A, Table 5.2.2.6.3-2B, Table 5.2.2.6.3-2C, Table 5.2.2.6.3-2D and Table
5.2.2.6.3-2E, L is defined in subclause 7.2 of [3]. For Table 5.2.2.6.3-2C and Table 5.2.2.6.3-2D, the codebook
O1 O2 
parameters , 
 2 2 
S1 , S 2    O1 ,
O2   O 
 2   4 
3GPP
Release 13 60 3GPP TS 36.212 V13.9.0 (2019-06)
S1 , S 2   
O1 O2 
,  for CodebookConfig=2/3/4.
 4 4 
Table 5.2.2.6.3-2: Fields for channel quality information feedback for UE selected subband CQI
reports
(transmission mode 4, transmission mode 6, transmission mode 8 configured with PMI/RI reporting
except with alternativeCodeBookEnabledFor4TX-r12=TRUE, transmission mode 9 configured with
PMI/RI reporting with 2/4 antenna ports except with alternativeCodeBookEnabledFor4TX-r12=TRUE,
transmission mode 10 configured with PMI/RI reporting with 2/4 antenna ports except with
reporting with 2/4 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set to
'CLASS B' with K>1, and K=1 except with alternativeCodebookEnabledCLASSB_K1=TRUE, except
with alternativeCodeBookEnabledFor4TX-r12=TRUE)
Field Bit width

Subband differential CQI codeword 0 2 2 2 2
Position of the M selected subbands L L L L
Table 5.2.2.6.3-2A: Fields for channel quality information feedback for UE selected subband CQI
reports (transmission mode 9 configured with PMI/RI reporting with 8 antenna ports, transmission
mode 10 configured with PMI/RI reporting with 8 antenna ports, and transmission mode 9/10
configured with PMI/RI reporting with 8 antenna ports and higher layer parameter eMIMO-Type, and
Bit width
Field
Rank = Rank = Rank = Rank = Rank = Rank = Rank = Rank =
1 2 3 4 5 6 7 8
Wide-band CQI codeword 0 4 4 4 4 4 4 4 4
Subband differential CQI
2 2 2 2 2 2 2 2
codeword 0
Wide-band CQI codeword 1 0 4 4 4 4 4 4 4
Subband differential CQI
0 2 2 2 2 2 2 2
codeword 1
Position of the M selected
subbands
L L L L L L L L
Wideband first PMI i1 4 4 2 2 2 2 2 0
Wideband second PMI i2 4 4 4 3 0 0 0 0
Subband second PMI i2 4 4 4 3 0 0 0 0
3GPP
Release 13 61 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.2.2.6.3-2B: Fields for channel quality information feedback for UE selected subband CQI
reports with 4 antenna ports (transmission modes 8, 9 and 10 configured with PMI/RI reporting, 4
antenna ports and alternativeCodeBookEnabledFor4TX-r12=TRUE, and transmission mode 9/10
configured with PMI/RI reporting with 4 antenna ports and higher layer parameter eMIMO-Type, and
alternativeCodebookEnabledCLASSB_K1=TRUE, with alternativeCodeBookEnabledFor4TX-
r12=TRUE)
Bit width
Field
Position of the M selected subbands L L L L
Table 5.2.2.6.3-2C: Fields for channel quality information feedback for UE selected subband CQI
reports (transmission mode 9/10 configured with PMI/RI reporting and higher layer parameter eMIMO-
Type, and eMIMO-Type is set to 'CLASS A' with codebook configuration ( N1, N2 , O1, O2 ) and
CodebookConfig=1)
Bit width
Field
Wide-band CQI
4 4 4 4
codeword 0
Subband
differential CQI 2 2 2 2
codeword 0
Wide-band CQI
0 4 4 4
codeword 1
Subband
codeword 1
Position of the
M selected L L L L
subbands
  N1O1    7  N 2    N1O1    7  N 2 
log 2 N1O1  log 2 N1O1 
Wideband first
log 2      log 2     
PMI i1,1   S1    3    S1    3 
Wideband first
log 2 N 2O2  log 2 N 2O2  log 2  N 2O2 / S2  log 2  N 2O2 / S2 
PMI i1,2
Wideband
2 2 1 1
second PMI i2
Subband
2 2 1 1
second PMI i2
Bit width
Field
3GPP
Release 13 62 3GPP TS 36.212 V13.9.0 (2019-06)
Wide-band CQI
4 4 4 4
codeword 0
Subband
codeword 0
Wide-band CQI
4 4 4 4
codeword 1
Subband
codeword 1
Position of the
M selected L L L L
subbands
Wideband first
PMI i1,1
Wideband first
PMI i1,2
Wideband
0 0 0 0
second PMI i2
Subband
0 0 0 0
second PMI i2
Table 5.2.2.6.3-2D: Fields for channel quality information feedback for UE selected subband CQI
Type, and eMIMO-Type is set to 'CLASS A' with codebook configuration ( N1, N2 , O1, O2 ) and
CodebookConfig=2/3/4)
Bit width
Field
3GPP
Release 13 63 3GPP TS 36.212 V13.9.0 (2019-06)
Wide-
band CQI
4 4 4 4
codeword
0
Subband
differential
CQI 2 2 2 2
codeword
0
Wide-
band CQI
0 4 4 4
codeword
1
Subband
differential
CQI 0 2 2 2
codeword
1
Position
of the M
selected
L L L L
subbands
Wideband   N1O1    7  N 2    N1O1    7  N 2 
first PMI log 2 N1O1 / 2 log 2 N1O1 / 2 log 2      log 2     
i1,1   S1    3    S1    3 
log 2  N 2O2 / S2 
Wideband
first PMI log 2 N 2O2 / 2 log 2 N 2O2 / 2 log 2  N 2O2 / S2 
i1,2
Wideband
second 4 4 4 3
PMI i2
Subband
second 4 4 4 3
PMI i2
Bit width
Field
3GPP
Release 13 64 3GPP TS 36.212 V13.9.0 (2019-06)
Wide-
band CQI
4 4 4 4
codeword
0
Subband
differential
CQI 2 2 2 2
codeword
0
Wide-
band CQI
4 4 4 4
codeword
1
Subband
differential
CQI 2 2 2 2
codeword
1
Position
of the M
selected
L L L L
subbands
log 2  N1O1 / S1 

Wideband
first PMI log 2  N1O1 / S1  log 2  N1O1 / S1  log 2  N1O1 / S1 
i1,1
Wideband
i1,2
Wideband
second 0 0 0 0
PMI i2
Subband
second 0 0 0 0
PMI i2
Table 5.2.2.6.3-2E: Fields for channel quality information feedback for UE selected subband CQI
reports (transmission mode 9/10 configured with PMI/RI reporting with 2/4/8 antenna ports and
higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K=1 and
Field Bit width

Subband differential CQI codeword 0 2 2 2 2 2 2
Subband differential CQI codeword 1 0 2 2 2 2 2
Position of the M selected subbands L L L L L L
Wideband Precoding matrix indicator 2 1 3 3 2 1
Subband Precoding matrix indicator 2 1 3 3 2 1
Field Bit width
8 antenna ports
Subband differential CQI codeword 0 2 2 2 2 2
Subband differential CQI codeword 1 0 2 2 2 2
Position of the M selected subbands L L L L L
Wideband Precoding matrix indicator 4 4 4 3 0
Subband Precoding matrix indicator 4 4 4 3 0
Table 5.2.2.6.3-3 shows the fields and the corresponding bit widths for the rank indication feedback for UE selected
subband CQI reports for PDSCH transmissions associated with transmission mode 3, transmission mode 4, transmission
3GPP
Release 13 65 3GPP TS 36.212 V13.9.0 (2019-06)
mode 8 configured with PMI/RI reporting, transmission mode 9 configured with PMI/RI reporting with 2/4/8 antenna
ports, transmission mode 10 configured with PMI/RI reporting with 2/4/8 antenna ports, and transmission mode 9/10
is set to 'CLASS B' with K=1, transmission mode 9/10 configured with PMI/RI reporting with 8/12/16 antenna ports
and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS A', and transmission mode 9/10
K=1 with with 2/4/8 antenna ports.
Table 5.2.2.6.3-3A shows the fields and the corresponding bit widths for the CSI-RS resource indication feedback for
UE selected subband CQI reports for PDSCH transmissions associated with transmission mode 9/10 configured with 1
antenna port for each CSI-RS resource and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B'
with K>1.
Table 5.2.2.6.3-3B shows the fields and the corresponding bit widths for the joint CRI and RI feedback for UE selected
subband CQI report for PDSCH transmissions associated with transmission mode 9/10 configured without PMI
reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K>1, and transmission
mode 9/10 configured with PMI/RI reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is set to
'CLASS B' with K>1 and 2/4/8 antenna ports.
Table 5.2.2.6.3-3: Fields for rank indication feedback for UE selected subband CQI reports
(transmission mode 3, transmission mode 4, transmission mode 8 configured with PMI/RI reporting,
transmission mode 9 configured with PMI/RI reporting with 2/4/8 antenna ports and transmission
mode 10 configured with PMI/RI reporting with 2/4/8 antenna ports, transmission mode 9/10
configured with PMI/RI reporting with 2/4/8 antenna ports and higher layer parameter eMIMO-Type,
and eMIMO-Type is set to 'CLASS B' with K=1, transmission mode 9/10 configured with PMI/RI
reporting with 8/12/16 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set
to 'CLASS A', and transmission mode 9/10 configured without PMI reporting and higher layer
parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K=1 with with 2/4/8 antenna ports).
Bit width
Field 2 antenna
ports
Rank 1 2 3
1 1 2
indication
Table 5.2.2.6.3-3A: Fields for CSI-RS resource indication feedback for UE selected subband CQI
reports (transmission mode 9/10 configured with 1 antenna port for each CSI-RS resource and higher
layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K>1).
Bit width
Field
K=2 K = 3 and K= 4 K = 5 to K = 8
CRI 1 2 3
Table 5.2.2.6.3-3B: Fields for joint CRI and RI feedback for UE selected subband CQI report
and eMIMO-Type is set to 'CLASS B' with K>1, and transmission mode 9/10 configured with PMI/RI
reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K>1 and
2/4/8 antenna ports).
Bit width
Field 2 antenna
ports
Rank 1 2 3
1 1 2
indication
3GPP
Release 13 66 3GPP TS 36.212 V13.9.0 (2019-06)
The channel quality bits in Table 5.2.2.6.3-1, Table 5.2.2.6.3-2, Table 5.2.2.6.3-2A, Table 5.2.2.6.3-2B, Table 5.2.2.6.3-
2C, Table 5.2.2.6.3-2D, Table 5.2.2.6.3-2E, and Table 5.2.2.6.3-3B form the bit sequence o0 , o1 , o2 ,...,oO1 with o0
corresponding to the first bit of the first field in each of the tables, o1 corresponding to the second bit of the first field in
each of the tables, and oO 1 corresponding to the last bit in the last field in each of the tables. The field of PMI shall
start with the wideband PMI followed by the PMI for the M selected subbands. The first bit of each field corresponds to
MSB and the last bit LSB. The RI bits sequence in Table 5.2.2.6.3-3, Table 5.2.2.6.3-3B, and the CRI sequence in Table
5.2.2.6.3-3A are encoded according to subclause 5.2.2.6.
the UE.
5.2.2.6.4 Channel coding for CQI/PMI information in PUSCH

The channel quality bits input to the channel coding block are denoted by o0 , o1 , o2 , o3 ,...,oO1 where O is the number
of bits. The number of channel quality bits depends on the transmission format. When PUCCH-based reporting format
is used, the number of CQI/PMI bits is defined in subclause 5.2.3.3.1 for wideband reports and in subclause 5.2.3.3.2
for UE selected subbands reports. When PUSCH-based reporting format is used, the number of CQI/PMI bits is defined
in subclause 5.2.2.6.1 for wideband reports, in subclause 5.2.2.6.2 for higher layer configured subbands reports and in
subclause 5.2.2.6.3 for UE selected subbands reports.
The channel quality information is first coded using a (32, O) block code. The code words of the (32, O) block code are
a linear combination of the 11 basis sequences denoted M i,n and defined in Table 5.2.2.6.4-1.
Table 5.2.2.6.4-1: Basis sequences for (32, O) code.
i Mi,0 Mi,1 Mi,2 Mi,3 Mi,4 Mi,5 Mi,6 Mi,7 Mi,8 Mi,9 Mi,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
3GPP
Release 13 67 3GPP TS 36.212 V13.9.0 (2019-06)
The encoded CQI/PMI block is denoted by b0 , b1 , b2 , b3 ,...,bB 1 where B  32 and
O 1
bi   on  M i,n mod 2 where i = 0, 1, 2, …, B-1.
n 0
The output bit sequence q0 , q1 , q2 , q3 ,..., qNL QCQI 1 is obtained by circular repetition of the encoded CQI/PMI block as
follows
qi  bi mod B  where i = 0, 1, 2, …, NL·QCQI-1, where NL is the number of layers the corresponding UL-SCH
transport block is mapped onto .
5.2.2.6.5 Channel coding for more than 11 bits of HARQ-ACK information
The HARQ-ACK bits input to the channel coding block are denoted by o0ACK o1ACK ,...,oOACK
ACK
1
where 11  O ACK  22
is the number of bits.
The sequences of bits o0ACK , o1ACK , o2ACK ,...,o ACK and o ACK , o ACK , o ACK ,...,oOACK
O ACK / 2 1 
O ACK / 2 
O ACK / 2 1  
O ACK / 2  2  
ACK
1 
are encoded
as follows
 O ACK / 2  1
 onACK  M i,n mod 2

 
q~i 
n 0
and
O ACK   O ACK / 2  1
 
~  o ACK
q~i    M i , n  mod 2
 O / 2  n 
ACK
n 0
where i = 0, 1, 2, …, 31 and the basis sequences M i ,n are defined in Table 5.2.2.6.4-1.
The output bit sequence q0ACK , q1ACK , q2ACK ,...,qQACK ACK 1

is obtained by the concatenation and circular repetition of the bit
~ ~ ~ ~
sequences q~0 , q~1 , q~2 ,...,, q~31 and q~0 , q~1 , q~2 ,...,, q~31 as follows:
Set i = 0
while i  Q / 2  Qm
q iACK  q~i mod 32
i=i+1
end while
Set i = 0
while i  Q  Q / 2 Qm
~
q ACK
Q / 2 Q
 q~i mod 32
  m i
i=i+1
end while
3GPP
Release 13 68 3GPP TS 36.212 V13.9.0 (2019-06)
5.2.2.7 Data and control multiplexing

The control and data multiplexing is performed such that HARQ-ACK information is present on both slots and is
mapped to resources around the demodulation reference signals. In addition, the multiplexing ensures that control and
data information are mapped to different modulation symbols.
The inputs to the data and control multiplexing are the coded bits of the control information denoted by
q0 , q1 , q2 , q3 ,...,q N L QCQI 1 and the coded bits of the UL-SCH denoted by f 0 , f1 , f 2 , f 3 ,..., f G 1 . The output of the data
and control multiplexing operation is denoted by g , g , g , g ,...,g
0 1 2 3 H 1

, where H  G  N L  QCQI and 
H   H / N L  Qm  , and where g , i  0,...,H   1 are column vectors of length Qm  N L  . H is the total number of
i
coded bits allocated for UL-SCH data and CQI/PMI information across the N L transmission layers of the transport
block.
In case where more than one UL-SCH transport block are transmitted in a subframe of an UL cell, the CQI/PMI
information is multiplexed with data only on the UL-SCH transport block with highest IMCS value on the initial grant. In
case the two transport blocks have the same IMCS value in the corresponding initial UL grant, the CQI/PMI information
is multiplexed with data only on the first transport block. For that UL-SCH transport block or in the case of single
transport block transmission, and assuming that N L is the number of layers onto which the UL-SCH transport block is
mapped, the control information and the data shall be multiplexed as follows:
Set i, j, k to 0
while j  N L .QCQI -- first place the control information
g k  [q j ...q j  N ]T
L Qm 1
j  j  N L  Qm
k  k 1
end while
while i  G -- then place the data
g k  [ f i ... f iQm N L 1 ]T
i  i  Qm  N L
k  k 1
end while
5.2.2.8 Channel interleaver

The channel interleaver described in this subclause in conjunction with the resource element mapping for PUSCH in [2]
implements a time-first mapping of modulation symbols onto the transmit waveform while ensuring that the HARQ-
ACK and RI information are present on both slots in the subframe. HARQ-ACK information is mapped to resources
around the uplink demodulation reference signals while RI information is mapped to resources around those used by
HARQ-ACK.
The input to the channel interleaver are denoted by g , g , g ,...,g , q RI , q RI , q RI ,...,q RI and
0 1 2 H 1 0 1 2 QRI 1
q ACK , q ACK , q ACK ,...,q ACK


. In case where more than one UL-SCH transport block are transmitted in a subframe of
0 1 2 QACK 1
an UL cell, the HARQ-ACK and RI information are multiplexed with data on both UL-SCH transport blocks.
  H   QRI
The number of modulation symbols per layer in the subframe is given by H total '
. The output bit sequence
from the channel interleaver is derived as follows:
3GPP
Release 13 69 3GPP TS 36.212 V13.9.0 (2019-06)
(1) Assign C mux  N symb

PUSCH
to be the number of columns of the matrix. The columns of the matrix are numbered 0,
1, 2,…, C mux  1 from left to right. Nsymb
PUSCH
is determined according to subclause 5.2.2.6.
(2) The number of rows of the matrix is Rmux  H total

  Qm  N L  / Cmux and we define Rmux
  Rmux / Qm  N L  .
The rows of the rectangular matrix are numbered 0, 1, 2,…, Rmux  1 from top to bottom.
(3) If rank information is transmitted in this subframe, the vector sequence q RI , q RI , q RI ,...,q RI is written onto
0 1 2 QRI 1
the columns indicated by Table 5.2.2.8-1, and by sets of Qm  N L  rows starting from the last row and moving
upwards according to the following pseudo-code.
Set i, j to 0.
 1
Set r to Rmux

while i < QRI
c RI  Column Set  j 
y  q RI
r Cmux  c RI i
i  i 1
  1  i 4
r  Rmux
j   j  3 mod 4
end while
Where ColumnSet is given in Table 5.2.2.8-1 and indexed left to right from 0 to 3.
(4) Write the input vector sequence, for k = 0, 1,…, H   1 , into the Rmux  C mux  matrix by sets of Qm  N L  rows
starting with the vector y in column 0 and rows 0 to Qm  N L  1 and skipping the matrix entries that are
0
already occupied:
 y y y  y
C mux 1

 0 1 2

 y y y  y 
C mux C mux 1 C mux  2 2C mux 1
      
 
y  y y  y  
 ( Rmux 1)C mux  1)C mux 1
( Rmux  1)C mux  2
( Rmux ( Rmux C mux 1) 
The pseudocode is as follows:
Set i, k to 0.
while k < H  ,
if y is not assigned to RI symbols

i
y g
i k
k=k+1
end if
i = i+1
end while
3GPP
Release 13 70 3GPP TS 36.212 V13.9.0 (2019-06)
(5) If HARQ-ACK information is transmitted in this subframe, the vector sequence q ACK , q ACK , q ACK ,...,q ACK

0 1 2 QACK 1
is written onto the columns indicated by Table 5.2.2.8-2, and by sets of Qm  N L  rows starting from the last row
and moving upwards according to the following pseudo-code. Note that this operation overwrites some of the
channel interleaver entries obtained in step (4).
Set i, j to 0.
 1
Set r to Rmux
while i < QACK
c ACK  ColumnSet j 
y  q ACK
r Cmux  c ACK i
i  i 1
  1  i 4
r  Rmux
j   j  3 mod 4
end while
Where ColumnSet is given in Table 5.2.2.8-2 and indexed left to right from 0 to 3.
(6) The output of the block interleaver is the bit sequence read out column by column from the Rmux  C mux 
matrix. The bits after channel interleaving are denoted by h0 , h1 , h2 ,..., hH  N L QRI 1 , where N L is the number
of layers the corresponding UL-SCH transport block is mapped onto.
Table 5.2.2.8-1: Column set for Insertion of rank information.
CP configuration Column Set

Normal {1, 4, 7, 10}
Extended {0, 3, 5, 8}
Table 5.2.2.8-2: Column set for Insertion of HARQ-ACK information.
CP configuration Column Set

Normal {2, 3, 8, 9}
Extended {1, 2, 6, 7}
The same channel interleaver procedures for RI are applied for CRI, using CRI instead of RI in the equations.
5.2.3 Uplink control information on PUCCH

Data arrives to the coding unit in the form of indicators for measurement indication, scheduling request and HARQ
acknowledgement.
Three forms of channel coding are used as shown in Figure 5.2.3-1,
- one for HARQ-ACK and for combination of HARQ-ACK and periodic CSI transmitted on PUCCH format 3,
including the cases with scheduling request,
- another for the channel quality information CQI/PMI transmitted on PUCCH format 2,
- and another for combination of CQI/PMI and HARQ-ACK transmitted on PUCCH format 2/2a/2b.
3GPP
Release 13 71 3GPP TS 36.212 V13.9.0 (2019-06)
A fourth form of channel coding is used as shown in Figure 5.2.3-2, for HARQ-ACK and for combination of HARQ-
ACK and periodic CSI transmitted on PUCCH format 4 or PUCCH format 5 including the cases with scheduling
request, or for periodic CSI transmitted on PUCCH format 4 or PUCCH format 5 including the cases with scheduling
request.
a0 , a1 ,..., a A1
Channel coding
b0 , b1 ,..., bB 1
Figure 5.2.3-1: Processing for UCI.
a0 , a1 ,..., a A 1
CRC attachment
c0 , c1 ,..., c K 1
Channel coding
d 0(i ) , d1(i ) ,..., d D(i )1
Rate matching
e0 , e1,..., eE 1
Figure 5.2.3-2: Processing for UCI.
5.2.3.1 Channel coding for UCI HARQ-ACK

The HARQ-ACK bits are received from higher layers for each subframe of each cell. Each positive acknowledgement
(ACK) is encoded as a binary '1' and each negative acknowledgement (NACK) is encoded as a binary '0'. For UEs
configured with no more than five DL cells, or for UEs configured by higher layers with codebooksizeDetermination-
r13 = cc, and for the case where PUCCH format 3, PUCCH format 4 or PUCCH format 5 [2] is configured by higher
layers and is used for transmission of the HARQ-ACK feedback information, the HARQ-ACK feedback consists of the
concatenation of HARQ-ACK bits for each of the serving cells. For UEs configured by higher layers with
codebooksizeDetermination-r13 = dai, the HARQ-ACK feedback consists of the HARQ-ACK bits for the serving cells
depending on the Downlink Assignment Index (DAI) as in Table 5.3.3.1.2-2 and as defined in [3]. For cells configured
with transmission modes 1, 2, 5, 6 or 7 [3], i.e., single codeword transmission modes, 1 bit of HARQ-ACK information,
a k , is used for that cell. For cells configured with other transmission modes, 2 bits of HARQ-ACK information are
used for those cells, i.e., a k , a k 1 with a k corresponding to HARQ-ACK bit for codeword 0 and a k 1 corresponding to
that for codeword 1.
ACK
Define O as the number of HARQ-ACK feedback bits and N APUCCH/N
format 3
as the number of HARQ-ACK
feedback bits including the possible concurrent transmission of scheduling request and/or periodic CSI when PUCCH
format 3 is used for transmission of HARQ-ACK feedback (subclause 10.1 in [3]), and N APUCCH/N
format 4
as the number of
HARQ-ACK feedback bits including the possible concurrent transmission of scheduling request and/or periodic CSI
3GPP
Release 13 72 3GPP TS 36.212 V13.9.0 (2019-06)
when PUCCH format 4 is used for transmission of HARQ-ACK feedback (subclause 10.1 in [3]), and N APUCCH
/N
format 5
as
the number of HARQ-ACK feedback bits including the possible concurrent transmission of scheduling request and/or
periodic CSI when PUCCH format 5 is used for transmission of HARQ-ACK feedback (subclause 10.1 in [3]).
For UEs configured by higher layers with codebooksizeDetermination-r13 = dai, the bit sequence
o~0ACK , o~1ACK ,...,o~OACK
ACK
1
is determined according to the Downlink Assignment Index (DAI) as in Table 5.3.3.1.2-2 and
as defined in [3]. Otherwise, the bit sequence o ~ ACK , o~ ACK ,...,o~ ACK is determined as below.
0 1 O ACK 1
~ ACK , o~ ACK ,...,o~ ACK is the result of the concatenation of HARQ-ACK bits for
For FDD, the sequence of bits o 0 1 O ACK 1
different cells according to the following pseudo-code:

DL
Set N cells to the number of cells configured by higher layers for the UE
DL
while c < N cells
if transmission mode configured in cell c {1,2,5,6,7} -- 1 bit HARQ-ACK feedback for this cell
o~ jACK  HARQ-ACK bit of this cell
j=j+1
else
if the UE is configured with spatial bundling on PUCCH by higher layers and if the UE is configured with
PUCCH format 4 or PUCCH format 5 or PUCCH format 3 with more than 5 serving cells
o ACK
j  binary AND operation of the HARQ-ACK bits corresponding to the first and second codewords of
this cell
j=j+1
else
o~ jACK  HARQ-ACK bit corresponding to the first codeword of this cell
j=j+1
o~ jACK  HARQ-ACK bit corresponding to the second codeword of this cell
j=j+1
end if
end if
c=c+1
end while
For the aggregation of more than one DL cell including a primary cell using FDD and at least one secondary cell using
~ ACK , o~ ACK ,...,o~ ACK is the result of the concatenation of HARQ-ACK bits for different
TDD, the sequence of bits o 0 1 O ACK 1
DL DL
cells. Define N cells as the number of cells configured by higher layers for the UE and Bc as the number of subframes
for which the UE needs to feed back HARQ-ACK bits in UL subframe n for the c-th serving cell. For a cell using TDD,
the subframes are determined by the DL-reference UL/DL configuration if the UE is configured with higher layer
3GPP
Release 13 73 3GPP TS 36.212 V13.9.0 (2019-06)
parameter eimta-HARQ-ReferenceConfig, and determined by the UL/DL configuration otherwise. For a cell using TDD,
BcDL  1 if subframe n-4 in the cell is a DL subframe or a special subframe with special subframe configurations
1/2/3/4/6/7/8/9 and normal downlink CP or a special subframe with special subframe configurations 1/2/3/5/6/7 and
extended downlink CP, and BcDL  0 otherwise. For a cell using FDD, BcDL  1 .
~ ACK , o~ ACK ,...,o~ ACK is performed according to the following pseudo-code:
The sequence of bits o0 1 O ACK 1

DL
while c < N cells
if
BcDL  1
o~ jACK  HARQ-ACK bit of this cell
j=j+1
else
if the UE is configured with spatial bundling on PUCCH by higher layers and if the UE is configured with
PUCCH format 4 or PUCCH format 5 or PUCCH format 3 with more than 5 serving cells
o ACK
j  binary AND operation of the HARQ-ACK bits corresponding to the first and second codewords
of this cell
j=j+1
else
o~ jACK  HARQ-ACK bit corresponding to the first codeword of this cell
j=j+1
o~ jACK  HARQ-ACK bit corresponding to the second codeword of this cell
j=j+1
end if
end if
c=c+1
end while
~ ACK , o~ ACK ,...,o~ ACK is obtained from the HARQ-ACK

For the cases with TDD primary cell, the sequence of bits o 0 1 O ACK 1
bits for different cells and different subframes.
DL
Define N cells as the number of cells configured by higher layers for the UE and BcDL as the number of subframes for
which the UE needs to feed back HARQ-ACK bits in cell c as defined in Subclause 7.3 of [3].
The number of HARQ-ACK bits k and the number of HARQ-ACK bits after spatial bundling kb are computed as
follows:
Set k = 0 – counter of HARQ-ACK bits
3GPP
Release 13 74 3GPP TS 36.212 V13.9.0 (2019-06)
Set kb = 0 – counter of HARQ-ACK bits after spatial bundling
DL
while c < N cells
set l = 0;
while l < BcDL
k=k+1
kb = kb + 1
else
k=k+2
kb = kb + 1
end if
l = l+1
end while
c=c+1
end while
In case the transmission of HARQ-ACK feedback using PUCCH format 3, PUCCH format 4 or PUCCH format 5
coincides with a sub-frame configured to the UE by higher layers for transmission of scheduling request, the number of
scheduling request bit OSR is 1; otherwise OSR=0.
In case the transmission of HARQ-ACK feedback using PUCCH format 3, PUCCH format 4 or PUCCH format 5
coincides with a sub-frame configured to the UE by higher layers for transmission of periodic CSI, OCSI is the number
of periodic CSI bit(s) for the CSI report as defined in subclause 7.2.2 [3]; otherwise OCSI=0.
For PUCCH format 3, the number of HARQ-ACK feedback bits O ACK is computed as follows:
If the UE is configured with more than 5 serving cells and spatial bundling on PUCCH is configured, then:
- O ACK  k b ,
else set kmax  20 when TDD is used in all the configured serving cell(s) of the UE and kmax  21 when FDD is used
in at least one of the configured serving cells with TDD primary cell.
If k  kmax and O
CSI
 0 , or if k  O CSI  O SR  22 and OCSI  0 , or if k  O CSI  O SR  22 and k  k , then
b max
- O ACK  k
else,
O ACK  k b
- .
For PUCCH format 4 or PUCCH format 5, O ACK  k if the UE is not configured with spatial bundling on PUCCH by
higher layers; otherwise O ACK  k b .
3GPP
Release 13 75 3GPP TS 36.212 V13.9.0 (2019-06)
If O ACK  k , the multiplexing of HARQ-ACK bits is performed according to the following pseudo-code:

DL
while c < N cells
set l = 0;
while l < BcDL
o~jACK  ocACK
j=j+1
else
[o~jACK , o~jACK
1 ]  [oc , 2l , oc , 2l 1 ] HARQ-ACK bit of this cell as defined in Subclause 7.3 of [3]
ACK ACK
j=j+2
end if
l = l+1
end while
c=c+1
end while
If O ACK  k b , spatial bundling is applied to all subframes in all cells and the multiplexing of HARQ-ACK bits is
performed according to the following pseudo-code

DL
while c < N cells
set l = 0;
while l < BcDL
if transmission mode configured in cell c  {1,2,5,6,7} – 1 bit HARQ-ACK feedback for this cell
o~jACK  ocACK
j=j+1
else
o~jACK  ocACK
,l binary AND operation of the HARQ-ACK bits corresponding to the first and second
codewords of this cell as defined in Subclause 7.3 of [3]
j=j+1
end if
3GPP
Release 13 76 3GPP TS 36.212 V13.9.0 (2019-06)
l = l+1
end while
c=c+1
end while
In case the transmission of HARQ-ACK feedback using PUCCH format 3, PUCCH format 4 or PUCCH format 5 [2]
coincides with a sub-frame configured to the UE by higher layers for transmission of scheduling request, the scheduling
request bit (1 = positive SR; 0 = negative SR) is appended at the end of the sequence of concatenated HARQ-ACK bits.
In case the transmission of HARQ-ACK feedback using PUCCH format 3, PUCCH format 4 or PUCCH format 5 [2]
coincides with a sub-frame configured to the UE by higher layers for transmission of periodic CSI, and periodic CSI is
not dropped as defined in subclause 7.3.2 and subclause 10.1.1 of [3], the periodic CSI bits for the CSI report as defined
in subclause 7.2.2 [3] are appended at the end of the sequence of concatenated HARQ-ACK bits and scheduling request
bit (if any), where in case of CSI report for more than one DL cell, the CSI report for each DL cell is appended in
increasing order of cell index. As with the transmission of the scheduling request, the procedure above is used with
N APUCCH
/N
format 3
, N APUCCH
/N
format 4
or N APUCCH
/N
format 5
including the number of periodic CSI bits and scheduling request bit
(if any).
For N APUCCH
/N
format 3
 11 , the bit sequence a0 , a1, a2 ,...,, aN PUCCH format 3 1 is obtained by setting ai  o~i ACK .
A/ N
For 11  N APUCCH  22 , the bit sequence a0 , a1, a2 ,...,, aN PUCCH format 3 1 is obtained by setting ai / 2  o~i
format 3 ACK
/N if i is
A/ N
 o~i ACK if i is odd.

even and a
N APUCCHforma
/N
t3
/ 2 (i 1) / 2
For N APUCCH
/N
format 3
 11 , the sequence of bits a0 , a1, a2 ,...,, aN PUCCH format 3 1 is encoded as follows
A/ N
PUCCH format 3
NA 1
 a n  M i,n  mod 2
/N
~
bi 
n 0
~ ~ ~ ~
The output bit sequence b0 , b1 , b2 ,...,, bB1 is obtained by circular repetition of the sequence b0 , b1 , b2 ,...,, b31
~
bi  bi mod 32
where i = 0, 1, 2, …, B-1 and where B  4  N sc

RB
.
For 11  N APUCCH format 3

 22 , the sequences of bits a0 , a1 , a2 ,...,, a N PUCCH format3 / 2 1 and
/N
 A/ N 
     
a N PUCCH format 3 / 2 , a N PUCCH format 3 / 2 1 , a N PUCCH format 3 / 2  2 ,...,, a N PUCCH format 3 1 are encoded as follows
A/ N A/ N A/ N A/ N
 N PUCCH format 3 / 2  1
 A / N 
 an  M i,n mod 2

~
bi 
n 0
and
N PUCCH format 3   N PUCCH format 3 / 2  1

~ A/ N  A / N 
~  a  M i ,n  mod 2
bi    N A / N
PUCCH format 3
/ 2  n 
n 0
3GPP
Release 13 77 3GPP TS 36.212 V13.9.0 (2019-06)
The output bit sequence b0 , b1 , b2 ,...,, bB1 where B  4  N sc RB

is obtained by the alternate concatenation of the bit
~ ~ ~ ~ ~
~ ~ ~~ ~ ~
~
sequences b0 , b1 , b2 ,...,, b23 and b0 , b1 , b2 ,...,, b23 as follows
Set i, j = 0
while i  4  N sc
RB
~ ~
bi  b j , bi 1  b j 1
~
~ ~
~
bi  2  b j , bi 3  b j 1
i=i+4
j=j+2
end while
 22 , the bit sequence a0 , a1 , a2 ,...,, aN PUCCH format 4 1 is obtained by setting ai  o~i

ACK
For N APUCCH
/N
format 4
, and the output bit
A/ N
sequence after the rate matching is denoted by e0 , e1 , e2 ,...,, eE 1 , where E  Qm  M RB

PUCCH 4
 N symb
PUSCH
 N scRB , Qm is the
PUSCH PUCCH 4
modulation order of the PUCCH format 4, N symb is determined according to subclause 5.2.4.1, and M RB
represents the bandwidth of the PUCCH format 4 in terms of resource blocks [2]. The CRC attachment, channel coding
and rate matching are performed according to subclauses 5.1.1 by setting L to 8 bits, 5.1.3.1 and 5.1.4.2, respectively.
The input bit sequence to the CRC attachment operation is a0 , a1 , a2 ,...,, aN PUCCH format 4 1 . The output bit sequence of the
A/ N
CRC attachment operation is the input bit sequence to the channel coding operation. The output bit sequence of the
channel coding operation is the input bit sequence to the rate matching operation.
 22 , the bit sequence a0 , a1 , a2 ,...,, aN PUCCH format 5 1 is obtained by setting ai  o~i

ACK
For N APUCCH
/N
format 5
, and the output bit
A/ N
sequence after the rate matching is denoted by e0 , e1 , e2 ,...,, eE 1 , where E  Qm  N symb

PUSCH
 N scRB / 2 , Qm is the
PUSCH
modulation order of the PUCCH format 5 and N symb is determined according to subclause 5.2.4.1. The CRC
attachment, channel coding and rate matching are performed according to subclauses 5.1.1 by setting L to 8 bits, 5.1.3.1
and 5.1.4.2, respectively. The input bit sequence to the CRC attachment operation is a0 , a1 , a2 ,...,, aN PUCCH format 5 1 . The
A/ N
output bit sequence of the CRC attachment operation is the input bit sequence to the channel coding operation. The
output bit sequence of the channel coding operation is the input bit sequence to the rate matching operation.
When PUCCH format 3, PUCCH format 4 or PUCCH format 5 is not used for transmission of HARQ-ACK feedback,
the HARQ-ACK bits are processed for transmission according to subclause 10.1 in [3].
5.2.3.2 Channel coding for UCI scheduling request

The scheduling request indication is received from higher layers and is processed according to [2].
5.2.3.3 Channel coding for UCI channel quality information

The channel quality and possible concurrent scheduling request bits input to the channel coding block are denoted by
a0 , a1 , a 2 , a3 ,...,a A1 where A is the number of bits, and where the scheduling request bit (if present) is prepended to
the sequence of channel quality bits. The number of channel quality bits depends on the transmission format as
indicated in subclause 5.2.3.3.1 for wideband reports and in subclause 5.2.3.3.2 for UE-selected subbands reports.
For PUCCH format 2, the channel quality information is coded using a (20, A) code. The code words of the (20, A) code
are a linear combination of the 13 basis sequences denoted M i,n and defined in Table 5.2.3.3-1.
3GPP
Release 13 78 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.2.3.3-1: Basis sequences for (20, A) code.
i Mi,0 Mi,1 Mi,2 Mi,3 Mi,4 Mi,5 Mi,6 Mi,7 Mi,8 Mi,9 Mi,10 Mi,11 Mi,12
0 1 1 0 0 0 0 0 0 0 0 1 1 0
1 1 1 1 0 0 0 0 0 0 1 1 1 0
2 1 0 0 1 0 0 1 0 1 1 1 1 1
3 1 0 1 1 0 0 0 0 1 0 1 1 1
4 1 1 1 1 0 0 0 1 0 0 1 1 1
5 1 1 0 0 1 0 1 1 1 0 1 1 1
6 1 0 1 0 1 0 1 0 1 1 1 1 1
7 1 0 0 1 1 0 0 1 1 0 1 1 1
8 1 1 0 1 1 0 0 1 0 1 1 1 1
9 1 0 1 1 1 0 1 0 0 1 1 1 1
10 1 0 1 0 0 1 1 1 0 1 1 1 1
11 1 1 1 0 0 1 1 0 1 0 1 1 1
12 1 0 0 1 0 1 0 1 1 1 1 1 1
13 1 1 0 1 0 1 0 1 0 1 1 1 1
14 1 0 0 0 1 1 0 1 0 0 1 0 1
15 1 1 0 0 1 1 1 1 0 1 1 0 1
16 1 1 1 0 1 1 1 0 0 1 0 1 1
17 1 0 0 1 1 1 0 0 1 0 0 1 1
18 1 1 0 1 1 1 1 1 0 0 0 0 0
19 1 0 0 0 0 1 1 0 0 0 0 0 0
After encoding the bits are denoted by b0 , b1 , b2 , b3 ,...,bB 1 where B  20 and with
A1
bi   a n  M i ,n  mod 2 where i = 0, 1, 2, …, B-1.
n 0
For PUCCH format 4, the output bit sequence after the rate matching is denoted by e0 , e1 , e2 ,...,, eE 1 , where
E  Qm  M RB
PUCCH 4
 N symb
PUSCH
 N scRB , Qm is the modulation order of the PUCCH format 4, N symb
PUSCH
is determined according
PUCCH 4
to subclause 5.2.4.1, and M RB represents the bandwidth of the PUCCH format 4 in terms of resource blocks [2].
The CRC attachment, channel coding and rate matching are performed according to subclauses 5.1.1 by setting L to 8
bits, 5.1.3.1 and 5.1.4.2, respectively. The input bit sequence to the CRC attachment operation is a0 , a1 , a2 ,...,, a A1 . The
output bit sequence of the CRC attachment operation is the input bit sequence to the channel coding operation. The
output bit sequence of the channel coding operation is the input bit sequence to the rate matching operation.
For PUCCH format 5, the output bit sequence after the rate matching is denoted by e0 , e1 , e2 ,...,, eE 1 , where
E  Qm  N symb
PUSCH
 N scRB / 2 , Qm is the modulation order of the PUCCH format 5 and N symb
PUSCH
is determined
according to subclause 5.2.4.1. The CRC attachment, channel coding and rate matching are performed according to
subclauses 5.1.1 by setting L to 8 bits, 5.1.3.1 and 5.1.4.2, respectively. The input bit sequence to the CRC attachment
operation is a0 , a1 , a2 ,...,, a A1 . The output bit sequence of the CRC attachment operation is the input bit sequence to the
channel coding operation. The output bit sequence of the channel coding operation is the input bit sequence to the rate
matching operation.
5.2.3.3.1 Channel quality information formats for wideband reports

Table 5.2.3.3.1-1 shows the fields and the corresponding bit widths for the channel quality information feedback for
wideband reports for PDSCH transmissions associated with a transmission mode 1, transmission mode 2, transmission
mode 3, transmission mode 7, transmission mode 8 configured without PMI/RI reporting, transmission mode 9
configured without PMI/RI reporting or configured with 1 antenna port, transmission mode 10 configured without
PMI/RI reporting or configured with 1 antenna port, and transmission mode 9/10 configured without PMI with higher
layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B'.
3GPP
Release 13 79 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.2.3.3.1-1A shows the fields and the corresponding bit widths for the channel quality information feedback for
wideband reports for PDSCH transmissions associated with transmission mode 9/10 configured without PMI reporting
and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with 2/4/8 antenna ports.
Table 5.2.3.3.1-1: UCI fields for channel quality information feedback for wideband CQI reports
(transmission mode 1, transmission mode 2, transmission mode 3, transmission mode 7,
reporting or configured with 1 antenna port, and transmission mode 9/10 configured without PMI with
higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B').
Field Bit width

Wide-band CQI 4
Table 5.2.3.3.1-1A: UCI fields for channel quality information feedback for wideband CQI reports
and eMIMO-Type is set to 'CLASS B' with 2/4/8 antenna ports)
Field Bit width

Rank = 1 Rank > 1
Wide-band CQI 4 4
Spatial differential CQI 0 3
Table 5.2.3.3.1-2 shows the fields and the corresponding bit widths for the channel quality and precoding matrix
information feedback for wideband reports for PDSCH transmissions associated with transmission mode 4,
transmission mode 5, transmission mode 6, and transmission mode 8 configured with PMI/RI reporting except with
alternativeCodeBookEnabledFor4TX-r12=TRUE.
Table 5.2.3.3.1-2: UCI fields for channel quality information feedback for wideband CQI reports
(transmission mode 4, transmission mode 5, transmission mode 6, and transmission mode 8
configured with PMI/RI reporting except with alternativeCodeBookEnabledFor4TX-r12=TRUE)
Bit width
Field 2 antenna ports 4 antenna ports
Wide-band CQI 4 4 4 4
Spatial differential CQI 0 3 0 3
Table 5.2.3.3.1-2A and Table 5.2.3.3.1-2B show the fields and the corresponding bit widths for the channel quality and
precoding matrix information feedback for wideband reports for PDSCH transmissions associated with transmission
mode 9 configured with PMI/RI reporting except with alternativeCodeBookEnabledFor4TX-r12=TRUE, and
transmission mode 10 configured with PMI/RI reporting except with alternativeCodeBookEnabledFor4TX-r12=TRUE,
and transmission mode 9/10 configured with PMI/RI reporting with 2/4/8 antenna ports and higher layer parameter
eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K=1 and except with
alternativeCodebookEnabledCLASSB_K1=TRUE, K>1, except with alternativeCodeBookEnabledFor4TX-r12=TRUE.
The number of configured CSI-RS resources in a CSI process K is defined in [3] and
alternativeCodebookEnabledCLASSB_K1 is configured by higher layers [6].
Table 5.2.3.3.1-2A-1and Table 5.2.3.3.1-2A-2 show the fields and the corresponding bit widths for the channel quality
and precoding matrix information feedback for wideband reports for PDSCH transmissions associated with
transmission mode 9 /10 configured with PMI/RI reporting with higher layer parameter eMIMO-Type, and eMIMO-
3GPP
Release 13 80 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.2.3.3.1-2A: UCI fields for transmission of wideband CQI and precoding information (i2)
(transmission mode 9 configured with PMI/RI reporting except with
alternativeCodeBookEnabledFor4TX-r12=TRUE, and transmission mode 10 configured with PMI/RI
reporting except with alternativeCodeBookEnabledFor4TX-r12=TRUE, and transmission mode 9/10
and eMIMO-Type is set to 'CLASS B' with K=1 and except with
alternativeCodebookEnabledCLASSB_K1=TRUE, K>1, except with
Bit width
2 antenna ports 4 antenna ports 8 antenna ports
Field
Rank = Rank = Rank = Rank > Rank = Rank = Rank = Rank >
1 2 1 1 1 2,3 4 4
Wide-band CQI 4 4 4 4 4 4 4 4
Spatial differential CQI 0 3 0 3 0 3 3 3
Wide-band PMI (2 or 4
antenna ports) 2 1 4 4 4 4 3 0
or i2 (8 antenna ports)
Table 5.2.3.3.1-2A-1: UCI fields for transmission of wideband CQI and precoding information (i2)
(transmission mode 9/10 configured PMI/RI with higher layer parameter eMIMO-Type, and eMIMO-
Type is set to 'CLASS A' and with codebook configuration ( N1, N2 , O1, O2 ) , and CodebookConfig=1 )
Bit width
Field 8/12/16 antenna ports
Rank = 1 Rank = 2 Rank = 3 Rank = 4 Rank = 5 Rank = 6 Rank = 7 Rank = 8
Wide-band CQI 4 4 4 4 4 4 4 4
Wide-band
2 2 1 1 0 0 0 0
i2
Table 5.2.3.3.1-2A-2: UCI fields for transmission of wideband CQI and precoding information (i2)
(transmission mode 9/10 configured PMI/RI with higher layer parameter eMIMO-Type, and eMIMO-
Type is set to 'CLASS A' and with codebook configuration ( N1, N2 , O1, O2 ) , and CodebookConfig=2/3/4 )
Bit width
Rank = 1 Rank = 2 Rank = 3 Rank = 4 Rank = 5 Rank = 6 Rank = 7 Rank = 8
Wide-band CQI 4 4 4 4 4 4 4 4
Wide-band i2 4 4 4 3 0 0 0 0
Table 5.2.3.3.1-2B: UCI fields for transmission of wideband CQI and precoding information (i1, i2) for
transmission mode 9 configured with PMI/RI reporting with 8 antenna ports, transmission mode 10
PMI/RI reporting with 8 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is
set to 'CLASS B' with K=1 and except with alternativeCodebookEnabledCLASSB_K1=TRUE, K>1
Bit width
Field 8 antenna ports
Rank = 1 Rank = 2 Rank = 3 Rank =4 Rank = 5 Rank = 6 Rank = 7 Rank = 8
Wide-band CQI 4 4 4 4 4 4 4 4
i1 3 3 1 1 2 2 2 0
Wide-band i2 1 1 3 3 0 0 0 0
Table 5.2.3.3.1-2C and Table 5.2.3.3.1-2D show the fields and the corresponding bit widths for the channel quality and
precoding matrix information feedback for wideband reports for PDSCH transmissions for 4 antenna ports associated
with transmission modes 8, 9 and 10 configured with PMI/RI reporting and alternativeCodeBookEnabledFor4TX-
r12=TRUE, and transmission mode 9/10 configured with PMI/RI reporting and higher layer parameter eMIMO-Type,
3GPP
Release 13 81 3GPP TS 36.212 V13.9.0 (2019-06)
and eMIMO-Type is set to 'CLASS B' with 4 antenna ports with K=1 and except with
alternativeCodebookEnabledCLASSB_K1=TRUE, K>1, and alternativeCodeBookEnabledFor4TX-r12=TRUE.
Table 5.2.3.3.1-2E shows the fields and the corresponding bit widths for the channel quality and precoding matrix
information feedback for wideband reports for PDSCH transmissions associated with transmission mode 9/10
is set to 'CLASS B' with K=1 and alternativeCodebookEnabledCLASSB_K1=TRUE.
Table 5.2.3.3.1-2C: UCI fields for transmission of wideband CQI and precoding information (i2) with 4
alternativeCodeBookEnabledFor4TX-r12=TRUE, and transmission mode 9/10 configured with 4
antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K=1
and except with alternativeCodebookEnabledCLASSB_K1=TRUE, K>1, and
alternativeCodeBookEnabledFor4TX-r12=TRUE))
Bit width
Wideband i2 4 4 4 4
Table 5.2.3.3.1-2D: UCI fields for transmission of wideband CQI and precoding information (i1, i2)
with 4 antenna ports (transmission modes 8, 9 and 10 configured with PMI/RI reporting, 4 antenna
ports and alternativeCodeBookEnabledFor4TX-r12=TRUE, and transmission mode 9/10 configured
with 4 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B'
with K=1 and except with alternativeCodebookEnabledCLASSB_K1=TRUE, K>1, and
Bit width
i1 2 2 0 0
Wideband i2 2 2 4 4
Table 5.2.3.3.1-2E: UCI fields for transmission of wideband CQI and precoding information
(transmission mode 9/10 configured with PMI/RI reporting with 2/4/8 antenna ports and higher layer
parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K=1 and
Bit width
Rank = 1 Rank = 2 Rank = 1 Rank = 2 Rank = 3 Rank = 4
Wide-band CQI 4 4 4 4 4 4
Spatial differential CQI 0 3 0 3 3 3
Wide-band PMI 2 1 3 3 2 1
Bit width
Rank = 1 Rank = 2 Rank = 3 Rank = 4 Rank = 5 to Rank = 8
Wide-band CQI 4 4 4 4 4
Spatial differential CQI 0 3 3 3 3
Wide-band PMI 4 4 4 3 0
Table 5.2.3.3.1-3 shows the fields and the corresponding bit widths for the rank indication feedback for wideband
reports for PDSCH transmissions associated with transmission mode 3, transmission mode 4, transmission mode 8
3GPP
Release 13 82 3GPP TS 36.212 V13.9.0 (2019-06)
configured with PMI/RI reporting, transmission mode 9 configured with PMI/RI reporting with 2/4/8 antenna ports,
transmission mode 10 configured with PMI/RI reporting with 2/4/8 antenna ports, transmission mode 9/10 configured
with PMI/RI reporting with 2/4/8 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set to
'CLASS B', transmission mode 9/10 configured with PMI/RI reporting with 8/12/16 antenna ports and higher layer
parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS A', and transmission mode 9/10 configured without PMI
reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with 2/4/8 antenna ports.
Table 5.2.3.3.1-3: UCI fields for rank indication feedback for wideband reports (transmission mode 3,
transmission mode 4, transmission mode 8 configured with PMI/RI reporting, transmission mode 9
configured with PMI/RI reporting with 2/4/8 antenna ports, transmission mode 10 configured with
PMI/RI reporting with 2/4/8 antenna ports, transmission mode 9/10 configured with PMI/RI reporting
with 2/4/8 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS
B', transmission mode 9/10 configured with PMI/RI reporting with 8/12/16 antenna ports and higher
layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS A', and transmission mode 9/10
configured without PMI reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is set to
'CLASS B' with 2/4/8 antenna ports).
Bit width
Field 2 antenna
ports
Rank 1 2 3
1 1 2
indication
Table 5.2.3.3.1-3A shows the fields and the corresponding bit widths for the joint transmission of rank indication and i1
for wideband reports for PDSCH transmissions associated with transmission mode 9 and transmission mode 10, and
transmission mode 9/10 configured with 2/4/8 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-
Type is set to 'CLASS B' with K=1 and except with alternativeCodebookEnabledCLASSB_K1=TRUE, and K>1, except
with alternativeCodeBookEnabledFor4TX-r12 =TRUE.
Table 5.2.3.3.1-3A: UCI fields for joint report of RI and i1 (transmission mode 9 configured with PMI/RI
reporting with 2/4/8 antenna ports except with alternativeCodeBookEnabledFor4TX-r12 =TRUE and
transmission mode 10 configured with PMI/RI reporting with 2/4/8 antenna ports except with
alternativeCodeBookEnabledFor4TX-r12 =TRUE, and transmission mode 9/10 configured with 2/4/8
and except with alternativeCodebookEnabledCLASSB_K1=TRUE, and K>1, except with
alternativeCodeBookEnabledFor4TX-r12 =TRUE)
Bit width
Field 2 antenna
ports
Rank
1 1 2
indication 4 5 5
i1 - - -
Table 5.2.3.3.1-3B shows the fields and the corresponding bit widths for the joint transmission of rank indication and i1
for wideband reports for PDSCH transmissions associated with transmission modes 8, 9 and 10 configured with PMI/RI
reporting with 4 antenna ports and alternativeCodeBookEnabledFor4TX-r12 =TRUE, and transmission mode 9/10
configured with 4 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with
K=1 and except with alternativeCodebookEnabledCLASSB_K1=TRUE, and K>1, with
alternativeCodeBookEnabledFor4TX-r12 =TRUE..
3GPP
Release 13 83 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.2.3.3.1-3B: UCI fields for joint report of RI and i1 with 4 antenna ports (transmission modes 8,
9 and 10 configured with PMI/RI reporting, 4 antenna ports and alternativeCodeBookEnabledFor4TX-
r12=TRUE, and transmission mode 9/10 configured with 4 antenna ports and higher layer parameter
eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K=1 and except with
alternativeCodebookEnabledCLASSB_K1=TRUE, and K>1, with alternativeCodeBookEnabledFor4TX-
r12 =TRUE)
Bit width
Max 1 or 2 layers Max 4 layers
Rank indication and i1 4 5
Table 5.2.3.3.1-3C shows the fields and the corresponding bit widths for the joint report of CRI and rank indication
feedback for wideband reports for PDSCH transmissions associated with transmission mode 9/10 configured with
PMI/RI reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K>1, and
transmission mode 9/10 configured without PMI reporting and higher layer parameter eMIMO-Type, and eMIMO-Type
is set to 'CLASS B' with K>1.
Table 5.2.3.3.1-3C: UCI fields for joint report of CRI and rank indication feedback for wideband
Type, and eMIMO-Type is set to 'CLASS B' with K>1, and transmission mode 9/10 configured without
PMI reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with
K>1).
Bit width
Field 2 antenna
ports
Rank 1 2 3
1 1 2
indication
Table 5.2.3.3.1-3D shows the fields and the corresponding bit widths for the joint report of CRI , rank indication and i1
feedback for wideband reports for PDSCH transmissions associated with transmission mode 9/10 configured with
PMI/RI reporting with 4/8 ports, and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with
K>1, with alternativeCodeBookEnabledFor4TX-r12=TRUE.
Table 5.2.3.3.1-3D: UCI fields for joint report of CRI, rank indication and i1 feedback for wideband
reports (transmission mode 9/10 configured with PMI/RI reporting with 8 ports, and higher layer
parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K>1, transmission mode 9/10
configured with PMI/RI reporting with 4 ports Class B CSI reporting with K>1 with
alternativeCodeBookEnabledFor4TX-r12=TRUE).
Bit width
Field
Max 1 or 2 Max 4 layers Max 8 layers
layers
CRI log 2 K  log 2 K  log 2 K  log 2 K  log 2 K 
Rank indication and
4 5 4 5 5
i1
Table 5.2.3.3.1-3E shows the fields and the corresponding bit widths for the CRI feedback for wideband reports for
PDSCH transmissions associated with transmission mode 9/10 configured with 1 antenna port for each CSI-RS
resource, Class B CSI reporting with K>1.
3GPP
Release 13 84 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.2.3.3.1-3E: Fields for CRI feedback for wideband CQI reports (transmission mode 9/10
configured with 1 antenna port for each CSI-RS resource for Class B CSI reporting with K>1).
Bit width
Field
K=2 K = 3 and K = 4 K = 5 to K = 8
CRI 1 2 3
Table 5.2.3.3.1-4 shows the fields and the corresponding bit widths for the precoding matrix information feedback for
wideband reports for PDSCH transmissions associated with transmission mode 9/10 configured with PMI/RI reporting
with 8/12/16 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS A'. The
parameters S1 , S 2  in rank 1 and rank 2 are defined as S1 , S 2   1, 1 for CodebookConfig=1 and
S1 , S 2   2, 2 for CodebookConfig =2,3 and 4. The parameters S1 , S 2  in rank 3 and 4 are defined as
S1 , S 2   1, 1 for CodebookConfig=1, S1 , S 2   
O1 O2   O 
,  for CodebookConfig=2, S1 , S 2    O1 , 2  for
 2 2   2 
S1 , S 2    O1 ,
O2 
CodebookConfig=3,  for CodebookConfig=4. The parameters S1 , S 2  in rank 5 to 8 are
 4 
 O1 O2 
defined as S1 , S 2   1, 1 for CodebookConfig=1, S1 , S 2    ,  for CodebookConfig=2/3/4.
 4 4 
Table 5.2.3.3.1-4: UCI fields for channel quality information feedback for precoding information (i1)
to 'CLASS A' with codebook configuration ( N1, N2 , O1, O2 ) )
Bit width
Field
Wideband   N1O1    7  N 2    N1O1    7  N 2 
first PMI log 2 N1O1 / S1  log 2 N1O1 / S1  log 2      log 2     
i1,1   S1    3    S1    3 
Wideband log 2 N 2 O2 / S 2 
first PMI log 2 N 2 O2 / S 2  log 2 N 2 O2 / S 2  log 2 N 2 O2 / S 2 
i1,2
Bit width
Field
Wideband
first PMI log 2 N1O1 / S1  log 2 N1O1 / S1  log 2 N1O1 / S1  log 2 N1O1 / S1 
i1,1
Wideband
first PMI log 2 N 2 O2 / S 2  log 2 N 2 O2 / S 2  log 2 N 2 O2 / S 2  log 2 N 2 O2 / S 2 
i1,2
The channel quality bits in Table 5.2.3.3.1-1 through Table 5.2.3.3.1-4 form the bit sequence a0 , a1 , a 2 , a3 ,...,a A1
with a 0 corresponding to the first bit of the first field in each of the tables, a1 corresponding to the second bit of the
first field in each of the tables, and a A1 corresponding to the last bit in the last field in each of the tables. The first bit
of each field corresponds to MSB and the last bit LSB. The RI feedback for one bit is mapped according to Table
5.2.2.6-5 with o0RI replaced by a0 . The RI feedback for two bits is mapped according to Table 5.2.2.6-6 with o0RI , o1RI
replaced by a0 , a1 . The RI feedback for three bits is mapped according to Table 5.2.2.6-7 with o0RI , o1RI , o2RI replaced
by a0 , a1 , a2 . The same procedures for RI mapping are applied to CRI, replacing RI with CRI. The mapping for the
jointly coded RI and i1 is provided in Table 7.2.2-1E of [3].
When multiplexed with UL-SCH, the channel coding and multiplexing for the transmission configurations in Table
5.2.3.3.1-3, Table 5.2.3.3.1-3A, Table 5.2.3.3.1-3B, Table 5.2.3.3.1-3C and Table 5.2.3.3.1-3D is performed assuming
RI transmission in subclause 5.2.2.6. All other transmission configurations in this subclause are coded and multiplexed
assuming CQI/PMI transmission in subclause 5.2.2.6.
3GPP
Release 13 85 3GPP TS 36.212 V13.9.0 (2019-06)
5.2.3.3.1-3C, 5.2.3.3.1-3D refers to the maximum number of antenna ports of K CSI-RS resources configured for the
CSI-process for the UE.
5.2.3.3.2 Channel quality information formats for UE-selected sub-band reports

Table 5.2.3.3.2-1 shows the fields and the corresponding bit widths for the sub-band channel quality information
feedback for UE-selected sub-band reports for PDSCH transmissions associated with transmission mode 1, transmission
mode 2, transmission mode 3, transmission mode 7, transmission mode 8 configured without PMI/RI reporting,
transmission mode 9 configured without PMI/RI reporting or configured with 1 antenna port, and transmission mode 10
configured without PMI/RI reporting or configured with 1 antenna port.
Table 5.2.3.3.2-1A shows the fields and the corresponding bit widths for the sub-band channel quality information
feedback for UE-selected sub-band reports for PDSCH transmissions associated with transmission mode 9/10
2/4/8 antenna ports.
Table 5.2.3.3.2-1: UCI fields for channel quality information feedback for UE-selected sub-band CQI
reports (transmission mode 1, transmission mode 2, transmission mode 3, transmission mode 7,
reporting or configured with 1 antenna port, and transmission mode 9/10 configured without PMI/RI
with higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B')
Field Bit width

Sub-band CQI 4
Sub-band label 1 or 2
Table 5.2.3.3.2-1A: UCI fields for channel quality information feedback for UE-selected subband CQI
reports (transmission mode 9/10 configured without PMI reporting and higher layer parameter eMIMO-
Type, and eMIMO-Type is set to 'CLASS B' with 2/4/8 antenna ports)
Field Bit width

Rank = 1 Rank > 1
Wide-band CQI 4 4
Sub-band label 1 or 2 1 or 2
Table 5.2.3.3.2-2 shows the fields and the corresponding bit widths for the sub-band channel quality information
feedback for UE-selected sub-band reports for PDSCH transmissions associated with transmission mode 4, transmission
mode 5, transmission mode 6, and transmission mode 8 configured with PMI/RI reporting except with
Table 5.2.3.3.2-2: UCI fields for channel quality information feedback for UE-selected sub-band
reports (transmission mode 4, transmission mode 5, transmission mode 6 and transmission mode 8
Bit width
Sub-band CQI 4 4 4 4
Sub-band label 1 or 2 1 or 2 1 or 2 1 or 2
Table 5.2.3.3.2-2A and Table 5.2.3.3.2-2B show the fields and the corresponding bit widths for the sub-band channel
quality information feedback for UE-selected sub-band reports for PDSCH transmissions associated with transmission
mode 9 configured with PMI/RI reporting with 2/4/8 antenna ports except with alternativeCodeBookEnabledFor4TX-
r12=TRUE, and transmission mode 10 configured with PMI/RI reporting with 2/4/8 antenna ports except with
alternativeCodeBookEnabledFor4TX-r12=TRUE, and transmission mode 9/10 configured with PMI/RI reporting and
3GPP
Release 13 86 3GPP TS 36.212 V13.9.0 (2019-06)
higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS A' with CodebookConfig=2/3/4, and
transmission mode 9/10 configured with PMI/RI reporting with 2/4/8 antenna ports and higher layer parameter eMIMO-
Type, and eMIMO-Type is set to 'CLASS B' with K=1 and except with
alternativeCodebookEnabledCLASSB_K1=TRUE, or K>1, except with alternativeCodeBookEnabledFor4TX-
r12=TRUE. The number of configured CSI-RS resources in a CSI process K is defined in [3] and
alternativeCodebookEnabledCLASSB_K1 is configured by higher layers [6].
Table 5.2.3.3.2-2A-1 shows UCI fields for channel quality information feedback for UE-selected sub-band reports
(transmission mode 9/10 configured with 2/4/8 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-
Type is set to 'CLASS B' with K=1 and alternativeCodebookEnabledCLASSB_K1=TRUE, and transmission mode 9/10
2/4/8 antenna ports.
Table 5.2.3.3.2-2B-1 shows the fields and the corresponding bit widths for the sub-band channel quality information
configured with PMI/RI reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS A' with
CodebookConfig=1.
Table 5.2.3.3.2-2C shows the fields and the corresponding bit widths for the sub-band channel quality information
feedback for UE-selected sub-band reports for PDSCH transmissions associated with transmission modes 8, 9 and 10
configured with PMI/RI reporting and alternativeCodeBookEnabledFor4TX-r12 =TRUE, and transmission mode 9/10
configured with PMI/RI reporting with 4 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is
set to 'CLASS B' with K=1 and except with alternativeCodebookEnabledCLASSB_K1=TRUE, and with
Table 5.2.3.3.2-2A: UCI fields for channel quality information feedback for UE-selected sub-band
reports (transmission mode 9 configured with PMI/RI reporting with 2/4 antenna ports except with
alternativeCodeBookEnabledFor4TX-r12=TRUE, and transmission mode 10 configured with PMI/RI
transmission mode 9/10 configured with 2/4 antenna ports and higher layer parameter eMIMO-Type,
and eMIMO-Type is set to 'CLASS B' with K=1 and except with
alternativeCodebookEnabledCLASSB_K1=TRUE, K>1 except with
Bit width
Sub-band CQI 4 4 4 4
Wide-band i2 0 0 0 0
Sub-band i2 0 0 0 0
Sub-band label 1 or 2 1 or 2 1 or 2 1 or 2
Table 5.2.3.3.2-2A-1: UCI fields for channel quality information feedback for UE-selected sub-band
reports (transmission mode 9/10 configured with 2/4/8 antenna ports and higher layer parameter
eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K=1 and
alternativeCodebookEnabledCLASSB_K1=TRUE, transmission mode 9/10 configured without PMI
reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with 2/4/8
antenna ports)
Bit width
Rank = 1 Rank > 1
Wide-band CQI 0 0
Sub-band CQI 4 4
Wide-band i2 0 0
Sub-band i2 0 0
Sub-band label 1 or 2 1 or 2
3GPP
Release 13 87 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.2.3.3.2-2B: UCI fields for channel quality feedback for UE-selected sub-band reports
(transmission mode 9 configured with PMI/RI reporting with 8 antenna ports, transmission mode 10
PMI/RI reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS A' with
CodebookConfig=2/3/4, and transmission mode 9/10 configured with 8 antenna ports and higher
layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K=1 except with
alternativeCodebookEnabledCLASSB_K1=TRUE, and K>1)
Bit width
8/12/16 antenna ports
Field
Rank = 1 Rank = 2, 3 Rank = 4 Rank = 5, 6, 7 Rank = 8
PTI=0 PTI=1 PTI=0 PTI=1 PTI=0 PTI=1 PTI=0 PTI=1 PTI=0 PTI=1
Wide-band CQI 4 0 4 0 4 0 4 0 4 0
Sub-band CQI 0 4 0 4 0 4 0 4 0 4
Spatial differential CQI 0 0 3 3 3 3 3 3 3 3
Wide-band i2 4 0 4 0 3 0 0 0 0 0
Sub-band i2 0 4 0 2 0 2 0 0 0 0
Sub-band label 0 1 or 2 0 1 or 2 0 1 or 2 0 1 or 2 0 1 or 2
Table 5.2.3.3.2-2B-1: UCI fields for channel quality feedback for UE-selected sub-band reports
(transmission mode 9/10 configured with PMI/RI reporting and higher layer parameter eMIMO-Type,
and eMIMO-Type is set to 'CLASS A' with CodebookConfig=1)
Bit width
Field
Rank = 1 Rank = 2 Rank = 3, 4 Rank = 5, 6, 7 Rank = 8
PTI=0 PTI=1 PTI=0 PTI=1 PTI=0 PTI=1 PTI=0 PTI=1 PTI=0 PTI=1
Wide-band CQI 4 0 4 0 4 0 4 0 4 0
Sub-band CQI 0 4 0 4 0 4 0 4 0 4
Spatial differential CQI 0 0 3 3 3 3 3 3 3 3
Wide-band i2 2 0 2 0 1 0 0 0 0 0
Sub-band i2 0 2 0 2 0 1 0 0 0 0
Sub-band label 0 1 or 2 0 1 or 2 0 1 or 2 0 1 or 2 0 1 or 2
Table 5.2.3.3.2-2C: UCI fields for channel quality feedback for UE-selected sub-band reports with 4
alternativeCodeBookEnabledFor4TX-r12=TRUE, and transmission mode 9/10 configured with 4
and except with alternativeCodebookEnabledCLASSB_K1=TRUE, and K>1, with
Bit width
Rank = 1 Rank = 2 Rank = 3 Rank=4
PTI=0 PTI=1 PTI=0 PTI=1 PTI=1 PTI=1
Sub-band CQI 0 4 0 4 4 4
Wide-band i2 4 0 4 0 0 0
Sub-band i2 0 4 0 2 2 2
Sub-band label 0 1 or 2 0 1 or 2 1 or 2 1 or 2
Table 5.2.3.3.2-3 shows the fields and the corresponding bit widths for the wide-band channel quality and precoding
matrix information feedback for UE-selected sub-band reports for PDSCH transmissions associated with transmission
mode 4, transmission mode 5, transmission mode 6 and transmission mode 8 configured with PMI/RI reporting except
with alternativeCodeBookEnabledFor4TX-r12=TRUE.
3GPP
Release 13 88 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.2.3.3.2-3: UCI fields for channel quality information feedback for UE-selected sub-band CQI
reports (transmission mode 4, transmission mode 5, transmission mode 6 and transmission mode 8
Bit width
Table 5.2.3.3.2-3A and Table 5.2.3.3.2-3B show the fields and the corresponding bit widths for the wide-band channel
quality and precoding matrix information feedback for UE-selected sub-band reports for PDSCH transmissions
associated with transmission mode 9 configured with PMI/RI reporting with 2/4/8 antenna ports except with
alternativeCodeBookEnabledFor4TX-r12=TRUE, transmission mode 10 configured with PMI/RI reporting with 2/4/8
antenna ports except with alternativeCodeBookEnabledFor4TX-r12=TRUE, and transmission mode 9/10 configured
with PMI/RI reporting with 2/4/8 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set to
'CLASS B' with K=1 and except with alternativeCodebookEnabledCLASSB_K1=TRUE, and K>1, except with
alternativeCodeBookEnabledFor4TX-r12=TRUE
Table 5.2.3.3.2-3A-1 shows the fields and the corresponding bit widths for the wide-band channel quality and precoding
mode 9/10 configured with PMI/RI reporting with 2/4/8 antenna ports and higher layer parameter eMIMO-Type, and
eMIMO-Type is set to 'CLASS B' with K=1 and alternativeCodebookEnabledCLASSB_K1=TRUE.
Table 5.2.3.3.2-3C shows the fields and the corresponding bit widths for the wide-band channel quality and precoding
modes 8, 9 and 10 configured with PMI/RI reporting, 4 antenna ports and alternativeCodeBookEnabledFor4TX-
r12=TRUE, and transmission mode 9/10 configured with PMI/RI reporting with 4 antenna ports and higher layer
parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K=1 and except with
alternativeCodebookEnabledCLASSB_K1=TRUE, K>1 with alternativeCodeBookEnabledFor4TX-r12=TRUE.
Table 5.2.3.3.2-3A: UCI fields for wide-band channel quality and precoding matrix information
feedback for UE-selected sub-band reports (transmission mode 9 configured with PMI/RI reporting
with 2/4 antenna ports except with alternativeCodeBookEnabledFor4TX-r12=TRUE, transmission
mode 10 configured with PMI/RI reporting with 2/4 antenna ports except with
reporting with 2/4 antenna ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set to
'CLASS B' with K=1 and except with alternativeCodebookEnabledCLASSB_K1=TRUE, K>1, except
Bit width
i1 0 0 0 0
Wide-band i2 2 1 4 4
3GPP
Release 13 89 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.2.3.3.2-3A-1: UCI fields for wide-band channel quality and precoding matrix information
feedback for UE-selected sub-band reports (transmission mode 9/10 configured with 2/4/8 antenna
ports and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K=1 and
Bit width
Wideband CQI 4 4 4 4 4 4
i1 0 0 0 0 0 0
Wide-band i2 2 1 3 3 2 1
Bit width
Wideband CQI 4 4 4 4 4
Spatial differential CQI 0 3 3 3 3
i1 0 0 0 0 0
Wide-band i2 4 4 4 3 0
Table 5.2.3.3.2-3B: UCI fields for wide-band channel quality and precoding matrix information
feedback for UE-selected sub-band reports (transmission mode 9 configured with PMI/RI reporting
with 8 antenna ports and transmission mode 10 configured with PMI/RI reporting with 8 antenna
ports, and transmission mode 9/10 configured with PMI/RI reporting with 8 antenna ports and higher
layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K=1 and except with
alternativeCodebookEnabledCLASSB_K1=TRUE, K>1)
Bit width
8 antenna ports
Field
Rank = 1 Rank = 2 Rank = 3
i1 4 0 4 0 2 0
Wide-band i2 0 4 0 4 0 4
Bit width
8 antenna ports
Field
Rank = 4 Rank = 5, 6, 7 Rank = 8
i1 2 0 2 0 0 0
Wide-band i2 0 3 0 0 0 0
Table 5.2.3.3.2-3B-1 shows the fields and the corresponding bit widths for the wide-band channel quality and precoding
'CLASS A' with CodebookConfig=1. The parameters S1 , S 2  are defined as S1 , S 2   1, 1 for
CodebookConfig=1.
Table 5.2.3.3.2-3B-2 shows the fields and the corresponding bit widths for the wide-band channel quality and precoding
'CLASS A' with CodebookConfig=2/3/4. . The parameters S1 , S 2  in rank 1 and rank 2 are defined as
S1 , S 2   2, 2 for CodebookConfig =2,3 and 4. The parameters S1 , S 2  in rank 3 and 4 are defined as
S1 , S 2   
O1 O2   O 
,  for CodebookConfig =2, S1 , S 2    O1 , 2  for CodebookConfig =3,
 2 2   2 
3GPP
Release 13 90 3GPP TS 36.212 V13.9.0 (2019-06)
S1 , S 2    O1 ,
O2 
 for CodebookConfig =4. The parameters S1 , S 2  in rank 5 to 8 are defined as
 4 
S1 , S 2    1 , 2  for CodebookConfig =2/3/4.

O O
 4 4 
Table 5.2.3.3.2-3B-1: UCI fields for wide-band channel quality and precoding matrix information
feedback for UE-selected sub-band reports (transmission mode 9/10 configured with higher layer
parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS A' with codebook configuration ( N1, N2 , O1, O2 ) ,
and CodebookConfig=1)
Bit width
Field Rank = 1 Rank = 2 Rank = 3
Wide- 0 4 0 4 0 4
band CQI
Spatial 0 0 0 3 0 3
differential
CQI
Wideband   N1O1  0   N1O1  0   N1O1    7  N 2  0
first PMI log 2   log 2   log 2     
  S1    S1    3 
i1,1   S1 
Wideband   N 2O2  0   N 2O2  0   N 2O2  0
first PMI log 2   log 2  
log 2  
  S 2    S 2    S 2 
i1,2
Wide- 0 2 0 2 0 1
band i2
Bit width
Field Rank = 4 Rank = 5 to Rank = 8
PTI=0 PTI=1 PTI=0 PTI=1
Wide- 0 4 0 4
band CQI
Spatial 0 3 0 3
differential
CQI
Wideband   N1O1    7  N 2  0   N1O1  0
first PMI log 2      log 2  
i1,1   S1    3    S1 
Wideband   N 2O2  0   N 2O2  0
first PMI log 2   log 2  
  S 2 
i1,2   S 2 
Wide- 0 1 0 0
band i2
3GPP
Release 13 91 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.2.3.3.2-3B-2: UCI fields for wide-band channel quality and precoding matrix information
feedback for UE-selected sub-band reports (transmission mode 9/10 configured with higher layer
parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS A' with codebook configuration
( N1, N2 , O1, O2 ) , and CodebookConfig=2/3/4)
Bit width
Field Rank = 1 Rank = 2 Rank = 3
Wide- 0 4 0 4 0 4
band CQI
Spatial 0 0 0 3 0 3
differential
CQI
Wideband   N1O1  0   N1O1  0   N1O1    7  N 2  0
first PMI log 2   log 2   log 2     
  S1    S1    3 
i1,1   S1 
Wideband   N 2O2  0   N 2O2  0   N 2O2  0
first PMI log 2   log 2  
log 2  
i1,2   S 2    S 2    S 2 
Wide- 0 4 0 4 0 4
band i2
Bit width
Field Rank = 4 Rank = 5 to Rank = 8
PTI=0 PTI=1 PTI=0 PTI=1
Wide- 0 4 0 4
band CQI
Spatial 0 3 0 3
differential
CQI
Wideband   N1O1    7  N 2  0   N1O1  0
first PMI log 2      log 2  
i1,1   S1    3    S1 
Wideband   N 2O2  0   N 2O2  0
first PMI log 2   log 2  
  S 2    S 2 
i1,2
Wide- 0 3 0 0
band i2
Table 5.2.3.3.2-3C: UCI fields for wide-band channel quality and precoding matrix information
feedback for UE-selected sub-band reports with 4 antenna ports (transmission modes 8, 9 and 10
configured with PMI/RI reporting and alternativeCodeBookEnabledFor4TX-r12=TRUE, and
transmission mode 9/10 configured with higher layer parameter eMIMO-Type, and eMIMO-Type is set
to 'CLASS B' with K=1 and except with alternativeCodebookEnabledCLASSB_K1=TRUE, and K>1,
Bit width
Rank = 1 Rank = 2 Rank = 3 Rank=4
i1 4 0 4 0 0 0
Wide-band i2 0 4 0 4 4 4
Table 5.2.3.3.2-4 shows the fields and the corresponding bit width for the rank indication feedback for UE-selected sub-
band reports for PDSCH transmissions associated with transmission mode 3, transmission mode 4, transmission mode 8
3GPP
Release 13 92 3GPP TS 36.212 V13.9.0 (2019-06)
configured with PMI/RI reporting except with alternativeCodeBookEnabledFor4TX-r12=TRUE, transmission mode

9/10 configured with PMI/RI reporting with 2/4/8 antenna ports with higher layer parameter eMIMO-Type, and
eMIMO-Type is set to 'CLASS B' with K=1 and alternativeCodebookEnabledCLASSB_K1=TRUE, and transmission
mode 9/10 configured without PMI reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is set to
'CLASS B' with K=1 and alternativeCodebookEnabledCLASSB_K1=TRUE for 2/4/8 antenna ports.
Table 5.2.3.3.2-4: UCI fields for rank indication feedback for UE-selected sub-band reports
(transmission mode 3, transmission mode 4, and transmission mode 8 configured with PMI/RI
reporting except with alternativeCodeBookEnabledFor4TX-r12=TRUE, and transmission mode 9/10
configured with PMI/RI reporting with 2/4/8 antenna ports with higher layer parameter eMIMO-Type,
and eMIMO-Type is set to 'CLASS B' with K=1 and alternativeCodebookEnabledCLASSB_K1=TRUE,
and transmission mode 9/10 configured without PMI reporting and higher layer parameter eMIMO-
Type, and eMIMO-Type is set to 'CLASS B' with K=1 and
alternativeCodebookEnabledCLASSB_K1=TRUE for 2/4/8 antenna ports).
Bit width
Field 2 antenna
ports
Rank 1 2 3
1 1 2
indication
Table 5.2.3.3.2-4A shows the fields and the corresponding bit width for the rank indication and precoder type indication
(PTI) feedback for UE-selected sub-band reports for PDSCH transmissions associated with transmission mode 9
configured with PMI/RI reporting with 2/4/8 antenna ports and transmission mode 10 configured with PMI/RI reporting
with 2/4/8 antenna ports, and transmission mode 9/10 configured with PMI/RI reporting with 2/4/8 antenna ports and
higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K=1 and except with
alternativeCodebookEnabledCLASSB_K1=TRUE, or K>1, except with alternativeCodeBookEnabledFor4TX-
r12=TRUE for 4Tx, and transmission mode 9/10 configured with PMI/RI reporting with 8/12/16 antenna ports and
higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS A'.
Table 5.2.3.3.2-4B shows the fields and the corresponding bit width for the rank indication and precoder type indication
(PTI) feedback with 4 antenna ports for UE-selected sub-band reports for PDSCH transmissions associated with
transmission mode 8, transmission mode 9 and transmission mode 10 configured with PMI/RI reporting and
alternativeCodeBookEnabledFor4TX-r12 =TRUE, and transmission mode 9/10 configured with PMI/RI reporting and
higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K=1 and except with
alternativeCodebookEnabledCLASSB_K1=TRUE, K>1, with alternativeCodeBookEnabledFor4TX-r12=TRUE.
Table 5.2.3.3.2-4A: UCI fields for joint report of RI and PTI (transmission mode 9 configured with
PMI/RI reporting with 2/4/8 antenna ports except with alternativeCodeBookEnabledFor4TX-r12=TRUE,
transmission mode 10 configured with PMI/RI reporting with 2/4/8 antenna ports except with
alternativeCodeBookEnabledFor4TX-r12=TRUE, transmission mode 9/10 configured with PMI/RI
reporting with 2/4/8 antenna ports with higher layer parameter eMIMO-Type, and eMIMO-Type is set
to 'CLASS B' with K=1 and except with alternativeCodebookEnabledCLASSB_K1=TRUE, or K>1,
except with alternativeCodeBookEnabledFor4TX-r12=TRUE for 4Tx, and transmission mode 9/10
and eMIMO-Type is set to 'CLASS A')
Bit width
Field 2 antenna
ports
Rank indication 1 1 2 1 2 3
Precoder type 1 1 1
- - -
indication
3GPP
Release 13 93 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.2.3.3.2-4B: UCI fields for joint report of RI and PTI with 4 antenna ports (transmission mode 8,
transmission mode 9 and transmission mode 10 configured with PMI/RI reporting and
reporting and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K=1 and
except with alternativeCodebookEnabledCLASSB_K1=TRUE, K>1, with
Bit width
Rank indication 1 2
Precoder type indication 1 1
Table 5.2.3.3.2-4C shows the fields and the corresponding bit widths for the joint report of CRI and rank indication
K>1,and transmission mode 9/10 configured without PMI reporting with 2/4 antenna ports and higher layer parameter
eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K>1.
Table 5.2.3.3.2-4D shows the fields and the corresponding bit widths for the joint report of CRI , rank indication and
PTI feedback for UE-selected sub-band reports for PDSCH transmissions associated with transmission mode 9/10
K>1.
Table 5.2.3.3.2-4C: UCI fields for joint report of CRI and rank indication feedback for UE-selected
subband reports (transmission mode 9/10 configured with PMI/RI reporting with 2/4 antenna ports
and higher layer parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K>1, and
transmission mode 9/10 configured without PMI reporting with 2/4 antenna ports and higher layer
parameter eMIMO-Type, and eMIMO-Type is set to 'CLASS B' with K>1).
Bit width Bit width

Field
Max 1 or 2 layers Max 4 layers Max 1 or 2 layers Max 4 layers
CRI
log 2 K  log 2 K  log 2 K  log 2 K 
Rank indication 1 1 2 2
Table 5.2.3.3.2-4D: UCI fields for joint report of CRI, RI and PTI (transmission mode 9/10 configured
with PMI/RI reporting with 8 antenna ports with higher layer parameter eMIMO-Type, and eMIMO-Type
is set to 'CLASS B' with K>1, transmission mode 9/10 configured with PMI/RI reporting with 4
antenna ports with Class B CSI reporting with K>1with alternativeCodeBookEnabledFor4TX-
r12=TRUE)
Bit width
Field
Max 1 or 2 Max 4 layers Max 8 layers
layers
CRI log 2 K  log 2 K  log 2 K  log 2 K  log 2 K 
Rank indication 1 2 1 2 3
Precoder type
1 1 1 1 1
indication
Table 5.2.3.3.2-4E shows the fields and the corresponding bit width for CRI feedback for UE-selected sub-band reports
for PDSCH transmissions associated with transmission mode 9/10 configured with 1 antenna port for each CSI-RS
resource reporting for Class B CSI reporting with K>1.
3GPP
Release 13 94 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.2.3.3.2-4E: Fields for CRI feedback for transmission mode 9/10 configured with 1 antenna
port for each CSI-RS resource for Class B CSI reporting with K>1).
Bit width
Field
K=2 K = 3 and K = 4 K = 5 to K = 8
CRI 1 2 3
The channel quality bits in Table 5.2.3.3.2-1 through Table 5.2.3.3.2-4E form the bit sequence a0 , a1 , a 2 , a3 ,...,a A1
with a 0 corresponding to the first bit of the first field in each of the tables, a1 corresponding to the second bit of the
first field in each of the tables, and a A1 corresponding to the last bit in the last field in each of the tables. The first bit
of each field corresponds to MSB and the last bit LSB. The RI feedback for one bit is mapped according to Table
5.2.2.6-5 with o0RI replaced by a0 . The RI feedback for two bits is mapped according to Table 5.2.2.6-6 with o0RI , o1RI
replaced by a0 , a1 . The RI feedback for three bits is mapped according to Table 5.2.2.6-7 with o0RI , o1RI , o2RI replaced
by a0 , a1 , a2 . The same procedures for RI mapping are applied to CRI, replacing RI with CRI.
When multiplexed with UL-SCH, the channel coding and multiplexing for the transmission configurations in Table
5.2.3.3.2-4, Table 5.2.3.3.2-4A, Table 5.2.3.3.2-4B, Table 5.2.3.3.2-4C and Table 5.2.3.3.2-4D is performed assuming
RI transmission in subclause 5.2.2.6. All other transmission configurations in this subclause are coded and multiplexed
assuming CQI/PMI transmission in subclause 5.2.2.6.
5.2.3.3.2-4C, 5.2.3.3.2-4D refers to the maximum number of antenna ports of K CSI-RS resources configured for the
CSI-process for the UE.
5.2.3.4 Channel coding for UCI channel quality information and HARQ-ACK
This subclause defines the channel coding scheme for the simultaneous transmission of channel quality information and
HARQ-ACK information in a subframe.
When normal CP is used for uplink transmission, the channel quality information is coded according to subclause
5.2.3.3 with input bit sequence a0 , a1 , a2 , a3 ,...,aA1 and output bit sequence b0 , b1 , b2 , b3 ,...,bB 1 , where B   20 . The
HARQ-ACK bits are denoted by a0 in case one HARQ-ACK bit or a0 ,a1 in case two HARQ-ACK bits are reported
per subframe. Each positive acknowledgement (ACK) is encoded as a binary '1' and each negative acknowledgement
(NACK) is encoded as a binary '0'.
The output of this channel coding block for normal CP is denoted by b0 , b1 , b2 , b3 ,...,bB 1 , where
bi  bi , i  0,...,B   1
In case one HARQ-ACK bit is reported per subframe:
bB  a0 and B  B  1
In case two HARQ-ACK bits are reported per subframe:
bB  a0 , bB1  a1 and B  B  2
When extended CP is used for uplink transmission, the channel quality information and the HARQ-ACK bits are jointly
coded. The HARQ-ACK bits are denoted by a0 in case one HARQ-ACK bit or a0 , a1 in case two HARQ-ACK bits
are reported per subframe.
The channel quality information denoted by a0 , a1 , a2 , a3 ,...,aA1 is multiplexed with the HARQ-ACK bits to yield the
sequence a0 , a1 , a 2 , a3 ,...,a A1 as follows
ai  ai , i  0,...,A  1
and
3GPP
Release 13 95 3GPP TS 36.212 V13.9.0 (2019-06)
a A  a 0 and A   A  1 in case one HARQ-ACK bit is reported per subframe, or
a A  a 0 , a A1  a1 and A   A  2 in case two HARQ-ACK bits are reported per subframe.
The sequence a0 , a1 , a 2 , a3 ,...,a A1 is encoded according to subclause 5.2.3.3 to yield the output bit sequence
b0 , b1 , b2 , b3 ,...,bB 1 where B  20 .
5.2.4 Uplink control information on PUSCH without UL-SCH data

When control data are sent via PUSCH without UL-SCH data, the following coding steps can be identified:
- Channel coding of control information
- Control information mapping
- Channel interleaver
5.2.4.1 Channel coding of control information

Control data arrives at the coding unit in the form of channel quality information (CQI and/or PMI), HARQ-ACK and
rank indication. Different coding rates for the control information are achieved by allocating different number of coded
symbols for its transmission. When the UE transmits HARQ-ACK bits or rank indicator bits, it shall determine the
number of coded symbols Q  for HARQ-ACK or rank indicator as
  O  M scPUSCH  N symb
PUSCH
  offset
PUSCH
 

Q   min  PUSCH 
, 4  M sc
 OCQI  MIN  
 
where O is the number of HARQ-ACK bits as defined in subclause 5.2.2.6, or rank indicator bits, OCQI  MIN is the
number of CQI bits including CRC bits assuming rank equals to 1 for all serving cells for which an aperiodic CSI report
PUSCH
is triggered [3], M sc is the scheduled bandwidth for PUSCH transmission in the current subframe expressed as a
PUSCH
number of subcarriers in [2], and N symb is the number of SC-FDMA symbols in the current PUSCH transmission
PUSCH
sub-frame given by N symb  
 2  N symb
UL
 
 1  N SRS , where N SRS is equal to 1 if UE is configured to send PUSCH and
SRS in the same subframe for the current subframe, or if the PUSCH resource allocation for the current subframe even
partially overlaps with the cell-specific SRS subframe and bandwidth configuration defined in subclause 5.5.3 of [2], or
if the current subframe is a UE-specific type-1 SRS subframe as defined in Subclause 8.2 of [3], or if the current
subframe is a UE-specific type-0 SRS subframe as defined in subclause 8.2 of [3] and the UE is configured with
multiple TAGs. Otherwise N SRS is equal to 0.
For HARQ-ACK information QACK  Qm  Q and [  offset

PUSCH
  offset
HARQ  ACK
 offset
CQI
]. For UEs configured with no
more than five DL cells,  offset
HARQ  ACK
shall be determined according to [3]. For UEs configured with more than five DL
cells,  offset
HARQ  ACK
shall be determined according to [3] depending on the number of HARQ-ACK feedback bits.
For rank indication or CRI, QRI  Qm  Q , QCRI  Qm  Q and [  offset

PUSCH
  offset
RI
 offset
CQI
], where  offset shall
RI
be determined according to [3].
For CQI and/or PMI information QCQI  N symb

PUSCH
 M scPUSCH  Qm  QRI .
The channel coding and rate matching of the control data is performed according to subclause 5.2.2.6. The coded output
sequence for channel quality information is denoted by q0 , q1 , q2 , q3 ,..., qQCQI 1 , the coded vector sequence output for
3GPP
Release 13 96 3GPP TS 36.212 V13.9.0 (2019-06)
HARQ-ACK is denoted by q ACK , q ACK , q ACK ,...,q ACK


and the coded vector sequence output for rank indication or
0 1 2 QACK 1
RI RI RI RI
CRI, is denoted by q 0 , q1 , q 2 ,...,q Q 1
.
RI
5.2.4.2 Control information mapping

The input are the coded bits of the channel quality information denoted by q0 , q1 , q2 , q3 ,..., qQCQI 1 . The output is
denoted by g , g , g , g ,...,g , where H  QCQI and H   H / Qm , and where g , i  0,...,H   1 are column
0 1 2 3 H 1 i
vectors of length Q m . H is the total number of coded bits allocated for CQI/PMI information.
The control information shall be mapped as follows:
Set j, k to 0
while j  QCQI
g  [q j ... q j Qm 1 ]T
k
j  j  Qm
k  k 1
end while
5.2.4.3 Channel interleaver
The vector sequences g , g , g ,...,g , q RI , q RI , q RI ,...,q RI and q ACK , q ACK , q ACK ,...,q ACK are channel
0 1 2 H 1 0 1 2 QRI 1 0 1 2 
QACK 1
interleaved according subclause 5.2.2.8. The bits after channel interleaving are denoted by h0 , h1 , h2 ,...,hH QRI 1 .
5.3 Downlink transport channels and control information

If the UE is configured with a Master Cell Group (MCG) and Secondary Cell Group (SCG) [6], the procedures
described in this clause are applied to the MCG and SCG, respectively. When the procedures are applied to a SCG, the
term primary cell refers to the primary SCell (PSCell) of the SCG.
If the UE is configured with a PUCCH SCell [6], the procedures described in this clause are applied to the group of DL
cells associated with the primary cell and the group of DL cells associated with the PUCCH SCell, respectively. When
the procedures are applied to the group of DL cells associated with the PUCCH SCell, the term primary cell refers to
the PUCCH SCell.
If the UE is configured with a LAA SCell, the procedures described in this clause are applied assuming the LAA SCell
is an FDD SCell.
5.3.1 Broadcast channel

Figure 5.3.1-1 shows the processing structure for the BCH transport channel. Data arrives to the coding unit in the form
of a maximum of one transport block every transmission time interval (TTI) of 40ms. The following coding steps can
be identified:
- Channel coding
- Rate matching
The coding steps for BCH transport channel are shown in the figure below.
3GPP
Release 13 97 3GPP TS 36.212 V13.9.0 (2019-06)
a0 , a1 ,..., a A1
CRC attachment
c0 , c1 ,..., c K 1
Channel coding
d0(i) , d1(i) ,...,d D(i)1
Rate matching
e0 , e1 ,..., e E 1
Figure 5.3.1-1: Transport channel processing for BCH.

Error detection is provided on BCH transport blocks through a Cyclic Redundancy Check (CRC).
1 by a0 , a1 , a 2 , a3 ,...,a A1 , and the parity bits by p0 , p1 , p 2 , p3 ,..., p L1 . A is the size of the transport block and set to
24 bits 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 subclause 6.1.1 of [5].
The parity bits are computed and attached to the BCH transport block according to subclause 5.1.1 setting L to 16 bits.
After the attachment, the CRC bits are scrambled according to the eNodeB transmit antenna configuration with the
sequence xant,0 , xant,1 ,...,xant,15 as indicated in Table 5.3.1.1-1 to form the sequence of bits c0 , c1 , c2 , c3 ,...,c K 1 where
ck  ak for k = 0, 1, 2, …, A-1
ck   pk  A  xant,k  A mod 2 for k = A, A+1, A+2, ..., A+15.
Table 5.3.1.1-1: CRC mask for PBCH.
Number of transmit antenna ports at eNodeB PBCH CRC mask

 x ant,0 , x ant,1 ,...,x ant,15 
1 <0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0>
2 <1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1>
4 <0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1>
5.3.1.2 Channel coding

Information bits are delivered to the channel coding block. They are denoted by c0 , c1 , c2 , c3 ,...,cK 1 , where K is the
number of bits, and they are tail biting convolutionally encoded according to subclause 5.1.3.1.
After encoding the bits are denoted by d 0(i ) , d1(i ) , d 2(i ) , d 3(i ) ,...,d D(i) 1 , with i  0,1, and 2 , and where D is the number of bits
on the i-th coded stream, i.e., D  K .
3GPP
Release 13 98 3GPP TS 36.212 V13.9.0 (2019-06)

A tail biting convolutionally coded block is delivered to the rate matching block. This block of coded bits is denoted
by d 0(i ) , d1(i ) , d 2(i ) , d 3(i ) ,...,d D(i) 1 , with i  0,1, and 2 , and where i is the coded stream index and D is the number of bits in
each coded stream. This coded block is rate matched according to subclause 5.1.4.2.
After rate matching, the bits are denoted by e0 , e1 , e2 , e3 ,...,eE 1 , where E is the number of rate matched bits as defined
in subclause 6.6.1 of [2].
5.3.2 Downlink shared channel, Paging channel and Multicast channel

Figure 5.3.2-1 shows the processing structure for each transport block for the DL-SCH, PCH and MCH transport
channels. Data arrives to the coding unit in the form of a maximum of two transport blocks every transmission time
interval (TTI) per DL cell. The following coding steps can be identified for each transport block of a DL cell:
- Code block segmentation and code block CRC attachment
- Channel coding
- Rate matching
- Code block concatenation
The coding steps for PCH and MCH transport channels, and for one transport block of DL-SCH are shown in the figure
below. The same processing applies for each transport block on each DL cell.
a0 , a1 ,..., a A 1
Transport block
CRC attachment
b0 , b1 ,..., bB 1
Code block segmentation

Code block CRC attachment
cr 0 , cr1 ,..., cr K r 1
Channel coding
d r(i0) , d r(1i ) ,..., d r(i)D

r 1
Rate matching
er 0 , er1 ,..., er Er 1
Code block
concatenation
f 0 , f1 ,..., f G 1
Figure 5.3.2-1: Transport block processing for DL-SCH, PCH and MCH.
3GPP
Release 13 99 3GPP TS 36.212 V13.9.0 (2019-06)

Error detection is provided on transport blocks through a Cyclic Redundancy Check (CRC).
The parity bits are computed and attached to the transport block according to subclause 5.1.1 setting L to 24 bits and
using the generator polynomial gCRC24A(D).
5.3.2.2 Code block segmentation and code block CRC attachment

The bits input to the code block segmentation are denoted by b0 , b1 , b2 , b3 ,...,bB1 where B is the number of bits in the
transport block (including CRC).
Code block segmentation and code block CRC attachment are performed according to subclause 5.1.2.
The bits after code block segmentation are denoted by c r 0 , c r1 , c r 2 , c r 3 ,...,c r Kr 1 , where r is the code block number
and Kr is the number of bits for code block number r.

Code blocks are delivered to the channel coding block. They are denoted by c r 0 , c r1 , c r 2 , c r 3 ,...,c r Kr 1 , where r is the
code block number, and Kr 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 turbo encoded according to subclause 5.1.3.2.
After encoding the bits are denoted by d r(i0) , d r(1i ) , d r(i2) , d r(i3) ,...,d r(i)D 1 , with i  0,1, and 2 , and where Dr is the number of
r
bits on the i-th coded stream for code block number r, i.e. Dr  K r  4 .

Turbo coded blocks are delivered to the rate matching block. They are denoted by d r(i0) , d r(1i ) , d r(i2) , d r(i3) ,...,d r(i)D 1 ,
r
with i  0,1, and 2 , and where r is the code block number, i is the coded stream index, and Dr is the number of bits in
each coded stream of code block number r. The total number of code blocks is denoted by C and each coded block is
individually rate matched according to subclause 5.1.4.1.
After rate matching, the bits are denoted by er 0 , er1 , er 2 , er 3 ,...,er Er 1 , where r is the coded block number, and where
E r is the number of rate matched bits for code block number r.
5.3.2.5 Code block concatenation

The bits input to the code block concatenation block are denoted by er 0 , er1 , er 2 , er 3 ,...,er Er 1 for 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 subclause 5.1.5.
The bits after code block concatenation are denoted by f0 , f1, f 2 , f3 ,..., fG 1 , where G is the total number of coded bits
for transmission. This sequence of coded bits corresponding to one transport block after code block concatenation is
referred to as one codeword in subclause 6.3.1 of [2]. In case of multiple transport blocks per TTI, the transport block to
codeword mapping is specified according to subclause 5.3.3.1.5, 5.3.3.1.5A or 5.3.3.1.5B, depending on the DCI
Format.
3GPP
Release 13 100 3GPP TS 36.212 V13.9.0 (2019-06)
5.3.3 Downlink control information

A DCI transports downlink, uplink or sidelink scheduling information, requests for aperiodic CQI reports, LAA
common information, notifications of MCCH change [6] or uplink power control commands for one cell and one RNTI.
The RNTI is implicitly encoded in the CRC.
Figure 5.3.3-1 shows the processing structure for one DCI. The following coding steps can be identified:
- Information element multiplexing
- CRC attachment
- Channel coding
- Rate matching
The coding steps for DCI are shown in the figure below.
a0 , a1 ,..., a A 1
CRC attachment
c0 , c1 ,..., c K 1
Channel coding
d 0(i ) , d1(i ) ,..., d D(i )1
Rate matching
e0 , e1,..., eE 1
Figure 5.3.3-1: Processing for one DCI.
5.3.3.1 DCI formats

The fields defined in the DCI formats below are mapped to the information bits a0 to aA-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.
5.3.3.1.1 Format 0
DCI format 0 is used for the scheduling of PUSCH in one UL cell.
The following information is transmitted by means of the DCI format 0:
- Carrier indicator – 0 or 3 bits. This field is present according to the definitions in [3].
- Flag for format0/format1A differentiation – 1 bit, where value 0 indicates format 0 and value 1 indicates format 1A
- Frequency hopping flag – 1 bit as defined in subclause 8.4 of [3]. This field is used as the MSB of the
corresponding resource allocation field for resource allocation type 1.
3GPP
Release 13 101 3GPP TS 36.212 V13.9.0 (2019-06)
UL
- Resource block assignment and hopping resource allocation – log 2 ( N RB UL
( N RB  1) / 2)  bits
- For PUSCH hopping (resource allocation type 0 only):
- NUL_hop MSB bits are used to obtain the value of n~PRB (i) as indicated in subclause 8.4 of [3]

-  log 2 ( N RB

UL UL
( N RB 
 1) / 2)  N UL_hop  bits provide the resource allocation of the first slot in the UL

subframe
- For non-hopping PUSCH with resource allocation type 0:

-  log 2 ( N RB

UL UL
( N RB 
 1) / 2)  bits provide the resource allocation in the UL subframe as defined in

subclause 8.1.1 of [3]
- For non-hopping PUSCH with resource allocation type 1:
- The concatenation of the frequency hopping flag field and the resource block assignment and hopping
resource allocation field provides the resource allocation field in the UL subframe as defined in subclause
8.1.2 of [3]
- Modulation and coding scheme and redundancy version – 5 bits as defined in subclause 8.6 of [3]
- New data indicator – 1 bit
- TPC command for scheduled PUSCH – 2 bits as defined in subclause 5.1.1.1 of [3]
- Cyclic shift for DM RS and OCC index – 3 bits as defined in subclause 5.5.2.1.1 of [2]
- UL index – 2 bits as defined in subclauses 5.1.1.1, 7.2.1, 8 and 8.4 of [3] (this field is present only for TDD
operation with uplink-downlink configuration 0)
- Downlink Assignment Index (DAI) – 2 bits as defined in subclause 7.3 of [3] (this field is present only for cases
with TDD primary cell and either TDD operation with uplink-downlink configurations 1-6 or FDD operation)
- CSI request – 1, 2 or 3 bits as defined in subclause 7.2.1 of [3]. The 2-bit field applies to UEs configured with no
more than five DL cells and to
- UEs that are configured with more than one DL cell and when the corresponding DCI format is mapped onto
the UE specific search space given by the C-RNTI as defined in [3];
- UEs that are configured by higher layers with more than one CSI process and when the corresponding DCI
format is mapped onto the UE specific search space given by the C-RNTI as defined in [3];
- UEs that are configured with two CSI measurement sets by higher layers with the parameter csi-
MeasSubframeSet, and when the corresponding DCI format is mapped onto the UE specific search space
given by the C-RNTI as defined in [3];
the 3-bit field applies to UEs that are configured with more than five DL cells and when the corresponding DCI
format is mapped onto the UE specific search space given by the C-RNTI as defined in [3];
otherwise the 1-bit field applies
- SRS request – 0 or 1 bit. This field can only be present in DCI formats scheduling PUSCH which are mapped onto
the UE specific search space given by the C-RNTI as defined in [3]. The interpretation of this field is provided in
subclause 8.2 of [3]
UL
- Resource allocation type – 1 bit. This field is only present if N RB  N RB
DL
. The interpretation of this field is
provided in subclause 8.1 of [3]
If the number of information bits in format 0 mapped onto a given search space is less than the payload size of format
1A for scheduling the same serving cell and mapped onto the same search space (including any padding bits appended
to format 1A), zeros shall be appended to format 0 until the payload size equals that of format 1A.
3GPP
Release 13 102 3GPP TS 36.212 V13.9.0 (2019-06)
5.3.3.1.2 Format 1
DCI format 1 is used for the scheduling of one PDSCH codeword in one cell.
- Resource allocation header (resource allocation type 0 / type 1) – 1 bit as defined in subclause 7.1.6 of [3]
If downlink bandwidth is less than or equal to 10 PRBs, there is no resource allocation header and resource
allocation type 0 is assumed.
- Resource block assignment:
- For resource allocation type 0 as defined in subclause 7.1.6.1 of [3]:
DL
- N RB 
/ P bits provide the resource allocation
- log 2 P  bits of this field are used as a header specific to this resource allocation type to indicate the
selected resource blocks subset
- 1 bit indicates a shift of the resource allocation span

DL
- N RB  
/ P  log 2 P   1 bits provide the resource allocation
where the value of P depends on the number of DL resource blocks as indicated in subclause 7.1.6.1 of [3]
- Modulation and coding scheme – 5 bits as defined in subclause 7.1.7 of [3]
- HARQ process number – 3 bits (for cases with FDD primary cell), 4 bits (for cases with TDD primary cell)
- Redundancy version – 2 bits
- TPC command for PUCCH – 2 bits as defined in subclause 5.1.2.1 of [3]
- Downlink Assignment Index – number of bits as specified in Table 5.3.3.1.2-2.
- HARQ-ACK resource offset (this field is present when this format is carried by EPDCCH. This field is not present
when this format is carried by PDCCH) – 2 bits as defined in subclause 10.1 of [3]. The 2 bits are set to 0 when
this format is carried by EPDCCH on a secondary cell, or when this format is carried by EPDCCH on the
primary cell scheduling PDSCH on a secondary cell and the UE is configured with PUCCH format 3 for HARQ-
ACK feedback.
If the UE is not configured to decode PDCCH or EPDCCH with CRC scrambled by the C-RNTI and the number of
information bits in format 1 is equal to that for format 0/1A, one bit of value zero shall be appended to format 1.
If the UE is configured to decode PDCCH or EPDCCH with CRC scrambled by the C-RNTI and the number of
information bits in format 1 is equal to that for format 0/1A for scheduling the same serving cell and mapped onto the
UE specific search space given by the C-RNTI as defined in [3], one bit of value zero shall be appended to format 1.
If the number of information bits in format 1 carried by PDCCH belongs to one of the sizes in Table 5.3.3.1.2-1, one or
more zero bit(s) shall be appended to format 1 until the payload size of format 1 does not belong to one of the sizes in
Table 5.3.3.1.2-1 and is not equal to that of format 0/1A mapped onto the same search space.
Table 5.3.3.1.2-1: Ambiguous Sizes of Information Bits.
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}
3GPP
Release 13 103 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.3.3.1.2-2: Number of bits for Downlink Assignment Index.
Number
of bits
4 For UEs configured by higher layers with codebooksizeDetermination-r13 = dai and when a DCI
format scheduling PDSCH is mapped onto the UE specific search space given by the C-RNTI as
defined in [3], the 4-bit DAI consists of a 2-bit counter DAI and a 2-bit total DAI.
- Counter DAI – 2 bits as defined in subclause 7.3 of [3]
- Total DAI – 2 bits as defined in subclause 7.3 of [3]
2 For UEs not configured with codebooksizeDetermination-r13 = dai, or for UEs configured by
higher layers with codebooksizeDetermination-r13 = dai and when a DCI format scheduling
PDSCH is not mapped onto the UE specific search space given by the C-RNTI as defined in [3],
this field is present for FDD or TDD operation, for cases with TDD primary cell.
If the UL/DL configuration of all TDD serving cells is same and the UE is not configured to decode
PDCCH with CRC scrambled by eimta-RNTI, then this field only applies to serving cell with UL/DL
configuration 1-6
If at least two TDD serving cells have different UL/DL configurations or the UE is configured to
decode PDCCH with CRC scrambled by eimta-RNTI, then this field applies to a serving cell with
DL-reference UL/DL configuration 1-6 as defined in subclause 10.2 of [3]
0 For UEs not configured with codebooksizeDetermination-r13 = dai, or for UEs configured by
higher layers with codebooksizeDetermination-r13 = dai and when a DCI format scheduling
PDSCH is not mapped onto the UE specific search space given by the C-RNTI as defined in [3],
this field is not present for FDD or TDD operation, for cases with FDD primary cell.
5.3.3.1.3 Format 1A
DCI format 1A is used for the compact scheduling of one PDSCH codeword in one cell and random access procedure
initiated by a PDCCH order. The DCI corresponding to a PDCCH order can be carried by PDCCH or EPDCCH.
The following information is transmitted by means of the DCI format 1A:
- Flag for format0/format1A differentiation – 1 bit, where value 0 indicates format 0 and value 1 indicates format 1A
Format 1A is used for random access procedure initiated by a PDCCH order only if format 1A CRC is scrambled
with C-RNTI and all the remaining fields are set as follows:
- Localized/Distributed VRB assignment flag – 1 bit is set to '0'
 DL
- Resource block assignment – log 2 ( N RB DL
( N RB 
 1) / 2) bits, where all bits shall be set to 1
- Preamble Index – 6 bits
- PRACH Mask Index – 4 bits, [5]
- All the remaining bits in format 1A for compact scheduling assignment of one PDSCH codeword are set to
zero
Otherwise,
- Localized/Distributed VRB assignment flag – 1 bit as defined in 7.1.6.3 of [3]
 DL
( N RB 
 1) / 2) bits as defined in subclause 7.1.6.3 of [3]:
- For localized VRB:
log 2 ( N RB
DL DL
( N RB  1) / 2) bits provide the resource allocation
3GPP
Release 13 104 3GPP TS 36.212 V13.9.0 (2019-06)
- For distributed VRB:

DL
- If N RB  50 or if the format 1A CRC is scrambled by RA-RNTI, P-RNTI, SI-RNTI, SC-RNTI or G-
RNTI:
 DL
- log 2 ( N RB DL
( N RB 
 1) / 2) bits provide the resource allocation
- Else
- 1 bit, the MSB indicates the gap value, where value 0 indicates N gap  N gap,1 and value 1 indicates
N gap  N gap,2
 DL
- ( log 2 ( N RB DL
( N RB  1) / 2)   1) bits provide the resource allocation,
where N gap is defined in [2].
- Modulation and coding scheme – 5bits as defined in subclause 7.1.7 of [3]
- HARQ process number – 3 bits (for cases with FDD primary cell) , 4 bits (for cases with TDD primary cell)
- If the format 1A CRC is scrambled by RA-RNTI, P-RNTI, SI-RNTI, SC-RNTI or G-RNTI:

DL
- If N RB  50 and Localized/Distributed VRB assignment flag is set to 1
- the new data indicator bit indicates the gap value, where value 0 indicates N gap  N gap,1 and value
1 indicates N gap  N gap,2 .
- Else the new data indicator bit is reserved.
- Else
- The new data indicator bit as defined in [5]
- If the format 1A CRC is scrambled by RA-RNTI, P-RNTI, or SI-RNTI:
- The most significant bit of the TPC command is reserved.

1A
- The least significant bit of the TPC command indicates column N PRB of the TBS table defined of [3].
1A 1A
- If least significant bit is 0 then N PRB = 2 else N PRB = 3.
- Else
- The two bits including the most significant bit indicates the TPC command
- SRS request – 0 or 1 bit. This field can only be present in DCI formats scheduling PDSCH which are mapped onto
the UE specific search space given by the C-RNTI as defined in [3]. The interpretation of this field is provided in
subclause 8.2 of [3]. This field is not present when the DCI is used for scheduling PDSCH in a LAA SCell.
3GPP
Release 13 105 3GPP TS 36.212 V13.9.0 (2019-06)
ACK feedback.
If the UE is not configured to decode PDCCH or EPDCCH with CRC scrambled by the C-RNTI, and the number of
information bits in format 1A is less than that of format 0, zeros shall be appended to format 1A until the payload size
equals that of format 0.
If the UE is configured to decode PDCCH or EPDCCH with CRC scrambled by the C-RNTI and the number of
information bits in format 1A mapped onto a given search space is less than that of format 0 for scheduling the same
serving cell and mapped onto the same search space, zeros shall be appended to format 1A until the payload size equals
that of format 0, except when format 1A assigns downlink resource on a secondary cell without an uplink configuration
associated with the secondary cell.
If the number of information bits in format 1A carried by PDCCH belongs to one of the sizes in Table 5.3.3.1.2-1, one
zero bit shall be appended to format 1A.
When the format 1A CRC is scrambled with a RA-RNTI, P-RNTI, SI-RNTI, SC-RNTI or G-RNTI then the following
fields among the fields above are reserved:
- HARQ process number
- Downlink Assignment Index (used for cases with TDD primary cell and either FDD operation or TDD operation,
and is not present for cases with FDD primary cell and either FDD operation or TDD operation)
5.3.3.1.3A Format 1B
DCI format 1B is used for the compact scheduling of one PDSCH codeword in one cell with precoding information.
The following information is transmitted by means of the DCI format 1B:
- Carrier indicator – 0 or 3 bits. The field is present according to the definitions in [3].
- Localized/Distributed VRB assignment flag – 1 bit as defined in subclause 7.1.6.3 of [3]
 DL
( N RB 
 1) / 2) bits as defined in subclause 7.1.6.3 of [3]
log 2 ( N RB
DL DL

DL
- For N RB  50
 DL
- log 2 ( N RB DL
( N RB 
DL
- For N RB  50
N gap  N gap,2
 DL
- ( log 2 ( N RB DL
( N RB  1) / 2)   1) bits provide the resource allocation
- HARQ process number – 3 bits (for cases with FDD primary cell) , 4 bits (for cases with TDD primary cell)
3GPP
Release 13 106 3GPP TS 36.212 V13.9.0 (2019-06)
- TPMI information for precoding – number of bits as specified in Table 5.3.3.1.3A-1
TPMI information indicates which codebook index is used in Table 6.3.4.2.3-1 or Table 6.3.4.2.3-2 of [2]
corresponding to the single-layer transmission.
- PMI confirmation for precoding – 1 bit as specified in Table 5.3.3.1.3A-2
ACK feedback.
If PMI confirmation indicates that the eNodeB has applied precoding according to PMI(s) reported by the UE, the
precoding for the corresponding RB(s) in subframe n is according to the latest PMI(s) in an aperiodic CSI reported on
or before subframe n-4.
Table 5.3.3.1.3A-1: Number of bits for TPMI information.
Number of antenna ports Number

at eNodeB of bits
2 2
4 4
Table 5.3.3.1.3A-2: Content of PMI confirmation.
Bit field mapped

Message
to index
0 Precoding according to the indicated TPMI in
the TPMI information field
1 Precoding using the precoder(s) according to
PMI(s) indicated in the latest aperiodic CSI
report.
For aperiodic CSI mode 2-2:
- Precoding of scheduled resource blocks
belonging to the reported preferred M
subband(s), use precoder(s) according to the
preferred M subband PMI(s) indicated in the
latest aperiodic CSI report;
- Precoding of scheduled resource blocks not
belonging to the reported preferred M
subband(s), precoding using a precoder
according to the wideband PMI indicated in the
latest aperiodic CSI report.
If the number of information bits in format 1B is equal to that for format 0/1A for scheduling the same serving cell and
mapped onto the UE specific search space given by the C-RNTI as defined in [3], one bit of value zero shall be
appended to format 1B.
If the number of information bits in format 1B carried by PDCCH belongs to one of the sizes in Table 5.3.3.1.2-1, one
or more zero bit(s) shall be appended to format 1B until the payload size of format 1B does not belong to one of the
sizes in Table 5.3.3.1.2-1 and is not equal to that of format 0/1A mapped onto the same search space.
5.3.3.1.4 Format 1C
DCI format 1C is used for very compact scheduling of one PDSCH codeword, notifying MCCH change [6], notifying
SC-MCCH change [6] , reconfiguring TDD, and LAA common information.
The following information is transmitted by means of the DCI format 1C:
3GPP
Release 13 107 3GPP TS 36.212 V13.9.0 (2019-06)
If the format 1C is used for very compact scheduling of one PDSCH codeword
- 1 bit indicates the gap value, where value 0 indicates N gap  N gap,1 and value 1 indicates N gap  N gap,2
- DL
For N RB  50 , there is no bit for gap indication
- Resource block assignment – log 2 N VRB,

DL
gap1 / N RB   ( N VRB,gap1 / N RB   1) / 2 bits as defined in
step DL step
DL step
7.1.6.3 of [3] where N VRB,gap1 is defined in [2] and N RB is defined in [3]
Else if the format 1C is used for notifying MCCH change
- Information for MCCH change notification – 8 bits as defined in subclause 5.8.1.3 of [6]
- Reserved information bits are added until the size is equal to that of format 1C used for very compact
scheduling of one PDSCH codeword
Else if the format 1C is used for notifying SC-MCCH change
- Information for SC-MCCH change notification – 8 bits as defined in subclause 5.8a.1.3 of [6]
Else if the format 1C is used for reconfiguring TDD
- UL/DL configuration indication:
UL/DL configuration number 1, UL/DL configuration number 2,…, UL/DL configuration number I
L 
Where each UL/DL configuration is 3 bits, I   format 1c  , Lformat 1c is equal to the payload size of format 1C
 3 
used for very compact scheduling of one PDSCH codeword. The parameter eimta-UL-DL-ConfigIndex
provided by higher layers determines the index to the UL/DL configuration indication for a serving cell.
- Zeros are added until the size is equal to that of format 1C used for very compact scheduling of one PDSCH
codeword
Else
- Subframe configuration for LAA – 4 bits as defined in clause 13A of [3]
5.3.3.1.4A Format 1D
DCI format 1D is used for the compact scheduling of one PDSCH codeword in one cell with precoding and power
offset information.
The following information is transmitted by means of the DCI format 1D:
- Localized/Distributed VRB assignment flag – 1 bit as defined in subclause 7.1.6.3 of [3]
 DL
( N RB 
 1) / 2) bits as defined in subclause 7.1.6.3 of [3]:
log 2 ( N RB
DL DL
3GPP
Release 13 108 3GPP TS 36.212 V13.9.0 (2019-06)

DL
- For N RB  50
 DL
- log 2 ( N RB DL
( N RB 
DL
- For N RB  50
N gap  N gap,2
 DL
- ( log 2 ( N RB DL
( N RB  1) / 2)   1) bits provide the resource allocation
- TPMI information for precoding – number of bits as specified in Table 5.3.3.1.4A-1
TPMI information indicates which codebook index is used in Table 6.3.4.2.3-1 or Table 6.3.4.2.3-2 of [2]
corresponding to the single-layer transmission.
- Downlink power offset – 1 bit as defined in subclause 7.1.5 of [3]
ACK feedback.
Table 5.3.3.1.4A-1: Number of bits for TPMI information.
Number of antenna ports Number

at eNodeB of bits
2 2
4 4
If the number of information bits in format 1D is equal to that for format 0/1A for scheduling the same serving cell and
mapped onto the UE specific search space given by the C-RNTI as defined in [3], one bit of value zero shall be
appended to format 1D.
If the number of information bits in format 1D carried by PDCCH belongs to one of the sizes in Table 5.3.3.1.2-1, one
or more zero bit(s) shall be appended to format 1D until the payload size of format 1D does not belong to one of the
sizes in Table 5.3.3.1.2-1 and is not equal to that of format 0/1A mapped onto the same search space.
5.3.3.1.5 Format 2
3GPP
Release 13 109 3GPP TS 36.212 V13.9.0 (2019-06)
- For resource allocation type 0 defined in subclause 7.1.6.1 of [3]:
DL
- N RB 

DL
- N RB  
- HARQ process number - 3 bits (for cases with FDD primary cell), 4 bits (for cases with TDD primary cell)
- Transport block to codeword swap flag – 1 bit
In addition, for transport block 1:
- Precoding information – number of bits as specified in Table 5.3.3.1.5-3
ACK feedback.
If both transport blocks are enabled, the transport block to codeword mapping is specified according to Table
5.3.3.1.5-1.
In case one of the transport blocks is disabled as specified in subclause 7.1.7.2 of [3], the transport block to codeword
swap flag is reserved and the transport block to codeword mapping is specified according to Table 5.3.3.1.5-2.
3GPP
Release 13 110 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.3.3.1.5-1: Transport block to codeword mapping

(two transport blocks enabled).
transport block
codeword 0 codeword 1
to codeword
(enabled) (enabled)
swap flag value
0 transport block 1 transport block 2
1 transport block 2 transport block 1
Table 5.3.3.1.5-2: Transport block to codeword mapping

(one transport block enabled).
codeword codew
transport transport
0 ord 1
block 1 block 2
(enabled) (disabled)
transport
enabled disabled -
block 1
transport
disabled enabled -
block 2
The interpretation of the precoding information field depends on the number of enabled codewords according to Table
5.3.3.1.5-4 and Table 5.3.3.1.5-5. Note that TPMI indicates which codebook index is used in Table 6.3.4.2.3-1 or Table
6.3.4.2.3-2 of [2]. For a single enabled codeword, indices 18 to 34 inclusive in Table 5.3.3.1.5-5 are only supported for
retransmission of the corresponding transport block if that transport block has previously been transmitted using two
layers with closed-loop spatial multiplexing.
If the number of information bits in format 2 carried by PDCCH belongs to one of the sizes in Table 5.3.3.1.2-1, one
zero bit shall be appended to format 2.
Some entries in Table 5.3.3.1.5-4 and Table 5.3.3.1.5-5 are used for indicating that the eNodeB has applied precoding
according to PMI(s) reported by the UE. In these cases the precoding for the corresponding RB(s) in subframe n is
according to the latest PMI(s) in an aperiodic CSI reported on or before subframe n-4. For aperiodic CSI mode 2-2:
Precoding of scheduled resource blocks belonging to the reported preferred M subband(s) use precoder(s) according to
the preferred M subband PMI indicated by the latest aperiodic CSI report; Precoding of scheduled resource blocks not
belonging to the reported preferred M subband(s) use a precoder according to the wideband PMI indicated by the latest
aperiodic CSI report.
Table 5.3.3.1.5-3: Number of bits for precoding information.
Number of antenna ports at eNodeB Number of bits for precoding information

2 3
4 6
3GPP
Release 13 111 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.3.3.1.5-4: Content of precoding information field for 2 antenna ports.
One codeword: Two codewords:

Codeword 0 enabled, Codeword 0 enabled,
Codeword 1 disabled Codeword 1 enabled
Bit field Bit field
mapped to Message mapped Message
index to index
0 2 layers: Transmit 0 2 layers: Precoding
diversity corresponding to
precoder matrix
1 1 1 
2 1 1
1 1 layer: Precoding 1 2 layers: Precoding
corresponding to corresponding to
precoding vector precoder matrix
1 1T / 2 1 1 1 
2  j  j 
2 1 layer: Precoding 2 2 layers: Precoding
corresponding to according to the latest
precoder vector PMI report on
1  1 / 2
T PUSCH, using the
precoder(s) indicated
by the reported
PMI(s)
3 1 layer: Precoding 3 reserved

corresponding to
precoder vector
1 j T / 2
4 1 layer: Precoding 4 reserved
corresponding to
precoder vector
1  j / 2
T
5 1 layer: 5 reserved
Precoding according to
the latest PMI report on
PUSCH, using the
precoder(s) indicated by
the reported PMI(s),
if RI=2 was reported,
st
using 1 column
multiplied by 2 of all
precoders implied by the
reported PMI(s)
6 1 layer: 6 reserved
Precoding according to
the latest PMI report on
PUSCH, using the
precoder(s) indicated by
the reported PMI(s),
if RI=2 was reported,
nd
using 2 column
multiplied by 2 of all
precoders implied by the
reported PMI(s)
7 reserved 7 reserved
3GPP
Release 13 112 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.3.3.1.5-5: Content of precoding information field for 4 antenna ports.

Bit field Bit field
index to index
0 4 layers: Transmit 0 2 layers: TPMI=0
diversity
1 1 layer: TPMI=0 1 2 layers: TPMI=1
2 1 layer: TPMI=1
 
15 2 layers: TPMI=15
 
16 1 layer: TPMI=15 16 2 layers: Precoding
according to the latest
PMI report on PUSCH
using the precoder(s)
indicated by the reported
PMI(s)
17 1 layer: Precoding 17 3 layers: TPMI=0
PMI report on PUSCH
PMI(s)
18 2 layers: TPMI=0 18 3 layers: TPMI=1
19 2 layers: TPMI=1
 
 
33 2 layers: TPMI=15 33 3 layers: Precoding
PMI report on PUSCH
PMI(s)
34 2 layers: Precoding 34 4 layers: TPMI=0
PMI report on PUSCH
PMI(s)
35 – 63 reserved 35 4 layers: TPMI=1
 
50 4 layers: Precoding
PMI report on PUSCH
PMI(s)
51 – 63 Reserved
5.3.3.1.5A Format 2A
3GPP
Release 13 113 3GPP TS 36.212 V13.9.0 (2019-06)
- For resource allocation type 0 as defined in subclause 7.1.6.1 of [3]
DL
- N RB 

DL
- N RB  
- Transport block to codeword swap flag – 1 bit
- Precoding information – number of bits as specified in Table 5.3.3.1.5A-1
ACK feedback.
If both transport blocks are enabled, the transport block to codeword mapping is specified according to Table
5.3.3.1.5-1.
In case one of the transport blocks is disabled, the transport block to codeword swap flag is reserved and the transport
block to codeword mapping is specified according to Table 5.3.3.1.5-2.
The precoding information field is defined according to Table 5.3.3.1.5A-2. For a single enabled codeword, index 1 in
Table 5.3.3.1.5A-2 is only supported for retransmission of the corresponding transport block if that transport block has
previously been transmitted using two layers with large delay CDD.
3GPP
Release 13 114 3GPP TS 36.212 V13.9.0 (2019-06)
For transmission with 2 antenna ports, the precoding information field is not present. The number of transmission layers
is equal to 2 if both codewords are enabled; transmit diversity is used if codeword 0 is enabled while codeword 1 is
disabled.
If the number of information bits in format 2A carried by PDCCH belongs to one of the sizes in Table 5.3.3.1.2-1, one
zero bit shall be appended to format 2A.
Table 5.3.3.1.5A-1: Number of bits for precoding information.
Number of antenna ports at eNodeB Number of bits for precoding information

2 0
4 2
Table 5.3.3.1.5A-2: Content of precoding information field for 4 antenna ports.

Bit field Bit field
index to index
0 4 layers: Transmit 0 2 layers: precoder
diversity cycling with large delay
CDD
1 2 layers: precoder 1 3 layers: precoder
cycling with large delay cycling with large delay
CDD CDD
2 reserved 2 4 layers: precoder
cycling with large delay
CDD
3 reserved 3 reserved
5.3.3.1.5B Format 2B
The following information is transmitted by means of the DCI format 2B:
DL
- N RB 

DL
- N RB  
where the value of P depends on the number of DL resource blocks as indicated in subclause [7.1.6.1] of [3]
3GPP
Release 13 115 3GPP TS 36.212 V13.9.0 (2019-06)
- Scrambling identity– 1 bit as defined in subclause 6.10.3.1 of [2]
- SRS request – [0-1] bit. This field can only be present for TDD operation and if present is defined in subclause 8.2
of [3]
ACK feedback.
If both transport blocks are enabled, the number of layers equals two; transport block 1 is mapped to codeword 0; and
transport block 2 is mapped to codeword 1. Antenna ports 7 and 8 are used for spatial multiplexing.
In case one of the transport blocks is disabled, the number of layers equals one; the transport block to codeword
mapping is specified according to Table 5.3.3.1.5-2; and the antenna port for single-antenna port transmission is
according to Table 5.3.3.1.5B-1.
Table 5.3.3.1.5B-1: Antenna port for single-antenna port transmission (one transport block disabled).
New data indicator of the disabled transport block Antenna port

0 7
1 8
If the number of information bits in format 2B carried by PDCCH belongs to one of the sizes in Table 5.3.3.1.2-1, one
zero bit shall be appended to format 2B.
5.3.3.1.5C Format 2C
The following information is transmitted by means of the DCI format 2C:
3GPP
Release 13 116 3GPP TS 36.212 V13.9.0 (2019-06)
DL
- N RB 

DL
- N RB  
- Antenna port(s), scrambling identity and number of layers – 3 bits as specified in Table 5.3.3.1.5C-1 where nSCID is
the scrambling identity for antenna ports 7 and 8 defined in subclause 6.10.3.1 of [2], or 4bits as specified in
Table 5.3.3.1.5C-2 where nSCID is the scrambling identity for antenna ports 7, 8, 11 and 13 defined in subclause
6.10.3.1 of [2] when higher layer parameter dmrs-tableAlt is set to 1.
of [3]
ACK feedback.
If both transport blocks are enabled; transport block 1 is mapped to codeword 0; and transport block 2 is mapped to
codeword 1.
In case one of the transport blocks is disabled; the transport block to codeword mapping is specified according to Table
5.3.3.1.5-2. For the single enabled codeword, Value = 4, 5, 6 in Table 5.3.3.1.5C-1 or Value = 12, 13,14 in Table
5.3.3.1.5C-2 are only supported for retransmission of the corresponding transport block if that transport block has
previously been transmitted using two, three or four layers, respectively.
If the number of information bits in format 2C carried by PDCCH belongs to one of the sizes in Table 5.3.3.1.2-1, one
zero bit shall be appended to format 2C.
3GPP
Release 13 117 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.3.3.1.5C-1: Antenna port(s), scrambling identity and number of layers indication
One Codeword: Two Codewords:

Value Message Value Message
0 1 layer, port 7, nSCID=0 0 2 layers, ports 7-8, nSCID=0
1 1 layer, port 7, nSCID=1 1 2 layers, ports 7-8, nSCID=1
2 1 layer, port 8, nSCID=0 2 3 layers, ports 7-9
3 1 layer, port 8, nSCID=1 3 4 layers, ports 7-10
4 2 layers, ports 7-8 4 5 layers, ports 7-11
7 Reserved 7 8 layers, ports 7-14
Table 5.3.3.1.5C-2: Antenna port(s), scrambling identity and number of layers indication
One Codeword: Two Codewords:

Value Message Value Message
0 1 layer, port 7, nSCID=0 (OCC=2) 0 2 layer, port 7-8, nSCID=0 (OCC=2)
4 1 layer, port 7, nSCID=0 (OCC=4) 4 2 layer, port 11,13, nSCID=0 (OCC=4)
5 1 layer, port 7, nSCID=1 (OCC=4) 5 2 layer, port 11,13, nSCID=1 (OCC=4)
6 1 layer, port 8, nSCID=0 (OCC=4) 6 3 layer, port 7-9
10 1 layer, port 13, nSCID=0 (OCC=4) 10 7 layers, ports 7-13
11 1 layer, port 13, nSCID=1 (OCC=4) 11 8 layers, ports 7-14
12 2 layers, ports 7-8 12 Reserved
15 Reserved 15 Reserved
5.3.3.1.5D Format 2D
The following information is transmitted by means of the DCI format 2D:
3GPP
Release 13 118 3GPP TS 36.212 V13.9.0 (2019-06)
DL
- N RB 

DL
- N RB  
- Antenna port(s), scrambling identity and number of layers – 3 bits as specified in Table 5.3.3.1.5C-1 where nSCID is
the scrambling identity for antenna ports 7 and 8 defined in subclause 6.10.3.1 of [2], or 4bits as specified in
Table 5.3.3.1.5C-2 where nSCID is the scrambling identity for antenna ports 7, 8, 11 and 13 defined in subclause
6.10.3.1 of [2] when higher layer parameter dmrs-tableAlt is set to 1.
of [3]
- PDSCH RE Mapping and Quasi-Co-Location Indicator – 2 bits as defined in subclauses 7.1.9 and 7.1.10 of [3]
ACK feedback.
If both transport blocks are enabled; transport block 1 is mapped to codeword 0; and transport block 2 is mapped to
codeword 1.
In case one of the transport blocks is disabled; the transport block to codeword mapping is specified according to Table
5.3.3.1.5-2. For the single enabled codeword, Value = 4, 5, 6 in Table 5.3.3.1.5C-1 or Value = 12, 13,14 in Table
5.3.3.1.5C-2 are only supported for retransmission of the corresponding transport block if that transport block has
previously been transmitted using two, three or four layers, respectively.
If the number of information bits in format 2D carried by PDCCH belongs to one of the sizes in Table 5.3.3.1.2-1, one
zero bit shall be appended to format 2D.
5.3.3.1.6 Format 3
DCI format 3 is used for the transmission of TPC commands for PUCCH and PUSCH with 2-bit power adjustments.
3GPP
Release 13 119 3GPP TS 36.212 V13.9.0 (2019-06)
- TPC command number 1, TPC command number 2,…, TPC command number N
L 
where N   format0  , and where Lformat0 is equal to the payload size of format 0 before CRC attachment when
 2 
format 0 is mapped onto the common search space, including any padding bits appended to format 0. The
parameter tpc-Index or tpc-Index-PUCCH-SCell-r13 provided by higher layers determines the index to the TPC
command for a given UE.
 Lformat 0  Lformat 0
If  2   2 , a bit of value zero shall be appended to format 3.
 
For BL/CE UE, Lformat 0 and format 0 are replaced by Lformat 6-0A and format 6-0A, respectively, in the description above.
5.3.3.1.7 Format 3A
DCI format 3A is used for the transmission of TPC commands for PUCCH and PUSCH with single bit power
adjustments.
- TPC command number 1, TPC command number 2,…, TPC command number M
where M  Lformat0 , and where Lformat0 is equal to the payload size of format 0 before CRC attachment when format
0 is mapped onto the common search space, including any padding bits appended to format 0. The parameter tpc-Index
or tpc-Index-PUCCH-SCell-r13 provided by higher layers determines the index to the TPC command for a given UE.
For BL/CE UE, Lformat 0 and format 0 are replaced by Lformat 6-0A and format 6-0A, respectively, in the description above.
5.3.3.1.8 Format 4
DCI format 4 is used for the scheduling of PUSCH in one UL cell with multi-antenna port transmission mode,
  
  N RB
UL
/ P  1  
- Resource block assignment - max  log 2 ( N RB
UL UL
( N RB  1) / 2) , log 2      bits, where P is the
   
   4   
UL RBG size as defined in subclause 8.1.2 of [3]
- For resource allocation type 0:
-


The  log 2 ( N RB
UL UL
( N RB 
 1) / 2)  LSBs provide the resource allocation in the UL subframe as defined in

- For resource allocation type 1:
   N RB
UL
/ P  1 
- The log 2     LSBs provide the resource allocation in the UL subframe as defined in
 
  4  
- Cyclic shift for DM RS and OCC index – 3 bits as defined in subclause 5.5.2.1.1 of [2]
3GPP
Release 13 120 3GPP TS 36.212 V13.9.0 (2019-06)
- Downlink Assignment Index (DAI) – 2 bits as defined in subclause 7.3 of [3] (this field is present only for cases
with TDD primary cell and either TDD operation with uplink-downlink configurations 1-6 or FDD operation)
- CSI request – 1, 2 or 3 bits as defined in subclause 7.2.1 of [3]. The 2-bit field applies to UEs configured with no
more than five DL cells and to
- UEs that are configured with more than one DL cell;
- UEs that are configured by higher layers with more than one CSI process;
- UEs that are configured with two CSI measurement sets by higher layers with the parameter csi-
MeasSubframeSet;
the 3-bit field applies to UEs that are configured with more than five DL cells;
otherwise the 1-bit field applies
- SRS request – 2 bits as defined in subclause 8.2 of [3]
- Resource allocation type – 1 bit as defined in subclause 8.1 of [3]
Precoding information and number of layers: number of bits as specified in Table 5.3.3.1.8-1. Bit field as shown in
Table 5.3.3.1.8-2 and Table 5.3.3.1.8- 3. Note that TPMI for 2 antenna ports indicates which codebook index is to be
used in Table 5.3.3A.2-1 of [2], and TPMI for 4 antenna ports indicates which codebook index is to be used in Table
5.3.3A.2-2, Table 5.3.3A.2-3, Table 5.3.3A.2-4 and Table 5.3.3A.2-5 of [2]. If both transport blocks are enabled,
transport block 1 is mapped to codeword 0; and transport block 2 is mapped to codeword 1. In case one of the transport
blocks is disabled, the transport block to codeword mapping is specified according to Table 5.3.3.1.5-2. For a single
enabled codeword, indices 24 to 39 in Table 5.3.3.1.8-3 are only supported for retransmission of the corresponding
transport block if that transport block has previously been transmitted using two layers.
Table 5.3.3.1.8-1: Number of bits for precoding information.
Number of antenna ports at UE Number of bits for precoding information

2 3
4 6
3GPP
Release 13 121 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.3.3.1.8-2: Content of precoding information field for 2 antenna ports

Codeword 0 enabled Codeword 0 enabled
Bit field mapped to index Message Bit field mapped to index Message
1 1 layer: TPMI=1 1-7 reserved
2 1 layer: TPMI=2
… …
5 1 layer: TPMI=5
6-7 reserved
Table 5.3.3.1.8-3: Content of precoding information field for 4 antenna ports

Codeword 0 enabled Codeword 0 enabled
Bit field mapped to index Message Bit field mapped to index Message
… … … …
… … … …
40-63 reserved 28 4 layers: TPMI=0
29 - 63 Reserved
If the number of information bits in format 4 is equal to the payload size for DCI format 1, 2, 2A, 2B, 2C or 2D
associated with the configured DL transmission mode in the same serving cell, one zero bit shall be appended to format
4.
5.3.3.1.9 Format 5
DCI format 5 is used for the scheduling of PSCCH, and also contains several SCI format 0 fields used for the
scheduling of PSSCH.
- Resource for PSCCH – 6 bits as defined in subclause 14.2.1 of [3]
-TPC command for PSCCH and PSSCH – 1 bit as defined in subclauses 14.2.1 and 14.1.1 of [3]
- SCI format 0 fields according to 5.4.3.1.1:
- Frequency hopping flag
- Resource block assignment and hopping resource allocation
- Time resource pattern
If the number of information bits in format 5 mapped onto a given search space is less than the payload size of format 0
for scheduling the same serving cell, zeros shall be appended to format 5 until the payload size equals that of format 0
including any padding bits appended to format 0.
3GPP
Release 13 122 3GPP TS 36.212 V13.9.0 (2019-06)
5.3.3.1.10 Format 6-0A

DCI format 6-0A is used for the scheduling of PUSCH in one UL cell.
The following information is transmitted by means of the DCI format 6-0A:
- Flag format 6-0A/format 6-1A differentiation – 1 bit, where value 0 indicates format 6-0A and value 1 indicates
format 6-1A
- Frequency hopping flag – 1 bit, where value 0 indicates frequency hopping is not enabled and value 1 indicates
frequency hopping is enabled as defined in subclause 5.3.4 of [2]
  N UL  
- Resource block assignment – log 2  RB   +5 bits for PUSCH as defined in [3]:
  6  
  N UL  
- log 2  RB   MSB bits provide the narrowband index as defined in subclause 5.2.4 of [2]
  6  
- 5 bits provide the resource allocation using UL resource allocation type 0 within the indicated narrowband
- Modulation and coding scheme – 4 bits as defined in subclause 8.6 of [3]
- Repetition number – 2 bits as defined in subclause 8.0 of [3]
- HARQ process number – 3 bits
- Downlink Assignment Index (DAI) – 2 bits as defined in subclause 7.3 of [3] (This field is present only for cases
with TDD primary cell and either TDD operation with uplink-downlink configurations 1-6 or FDD operation.
This field is reserved when the configured maximum repetition number is larger than 1 for MPDCCH, or when
the higher layer parameter csi-NumRepetitionCE-r13 indicates more than one subframe)
- CSI request – 1 bit as defined in subclause 7.2.1 of [3]
- SRS request –1 bit. The interpretation of this field is provided in subclause 8.2 of [3]
- DCI subframe repetition number – 2 bits as defined in subclause 9.1.5 of [3]
If the number of information bits in format 6-0A mapped onto a given search space is less than the payload size of
format 6-1A for scheduling the same serving cell and mapped onto the same search space (including any padding bits
appended to format 6-1A), zeros shall be appended to format 6-0A until the payload size equals that of format 6-1A.
5.3.3.1.11 Format 6-0B

DCI format 6-0B is used for the scheduling of PUSCH in one UL cell.
The following information is transmitted by means of the DCI format 6-0B:
- Flag for format 6-0B/format 6-1B differentiation – 1 bit, where value 0 indicates format 6-0B and value 1
indicates format 6-1B
  N UL  
- Resource block assignment – log 2  RB   +3 bits for PUSCH as defined in [3]:
  6  
3GPP
Release 13 123 3GPP TS 36.212 V13.9.0 (2019-06)
  N UL  
  6  
- 3 bits provide the resource allocation within the indicated narrowband as specified in subclause 8.1.3 of [3]
- Modulation and coding scheme – 4 bits as defined in subclause 8.6 of [3]
- Repetition number – 3 bits as defined in subclause 8.0 of [3]
- HARQ process number – 1 bit
If the number of information bits in format 6-0B mapped onto a given search space is less than the payload size of
format 6-1B for scheduling the same serving cell and mapped onto the same search space (including any padding bits
appended to format 6-1B), zeros shall be appended to format 6-0B until the payload size equals that of format 6-1B.
5.3.3.1.12 Format 6-1A

DCI format 6-1A is used for the compact scheduling of one PDSCH codeword in one cell and random access procedure
initiated by a PDCCH order. The DCI corresponding to a PDCCH order can be carried by MPDCCH.
The following information is transmitted by means of the DCI format 6-1A:
- Flag format 6-0A/format 6-1A differentiation – 1 bit, where value 0 indicates format 6-0A and value 1 indicates
format 6-1A
Format 6-1A is used for random access procedure initiated by a PDCCH order only if format 6-1A CRC is
scrambled with C-RNTI and all the remaining fields are set as follows:
  N DL  
- Resource block assignment – log 2  RB   +5 bits, where all bits shall be set to 1
  6  
- PRACH Mask Index – 4 bits, [5]
- Starting CE level – 2 bits provide the PRACH starting CE level as defined in [5]
- All the remaining bits in format 6-1A for compact scheduling assignment of one PDSCH codeword are set to
zero
Otherwise,
- Frequency hopping flag – 1 bit, where value 0 indicates frequency hopping is not enabled and value 1 indicates
frequency hopping is enabled as defined in subclause 6.4.1 of [2]
  N DL  
- Resource block assignment – log 2  RB   +5 bits for PDSCH as defined in [3]:
  6  
  N DL  
  6  
- 5 bits provide the resource allocation using DL resource allocation type 2 within the indicated narrowband
- Repetition number – 2 bits as defined in subclause 7.1.11 of [3]
3GPP
Release 13 124 3GPP TS 36.212 V13.9.0 (2019-06)
- If the format 6-1A CRC is scrambled by RA-RNTI:
- The most significant bit of the TPC command is reserved.

1A
- The least significant bit of the TPC command indicates column N PRB of the TBS table defined of [3].
1A 1A
- If least significant bit is 0 then N PRB = 2 else N PRB = 3.
- Else
- The two bits including the most significant bit indicate the TPC command
- Downlink Assignment Index – number of bits as specified in Table 5.3.3.1.2-2. This field is reserved when the
configured maximum repetition number is larger than 1 for MPDCCH, or when the higher layer parameter csi-
NumRepetitionCE-r13 indicates more than one subframe.
- Antenna port(s) and scrambling identity – 2 bits indicating the values 0 to 3, as specified in Table 5.3.3.1.5C-1.
This field is present only if PDSCH transmission is configured with TM9 for DCI formats scheduling PDSCH
which are mapped onto the UE specific search space given by the C-RNTI as defined in [3].
- SRS request –1 bit. The interpretation of this field is provided in subclause 8.2 of [3]
- TPMI information for precoding – number of bits as specified in Table 5.3.3.1.3A-1.
- TPMI information indicates which codebook index is used in Table 6.3.4.2.3-1 or Table 6.3.4.2.3-2 of [2]
corresponding to the single-layer transmission. This field is present only if PDSCH transmission is
configured with TM6 for DCI formats scheduling PDSCH which are mapped onto the UE specific search
space given by the C-RNTI as defined in [3].
- PMI confirmation for precoding – 1 bit as specified in Table 5.3.3.1.3A-2. This field is present only if PDSCH
transmission is configured with TM6 for DCI formats scheduling PDSCH which are mapped onto the UE
specific search space given by the C-RNTI as defined in [3].
- HARQ-ACK resource offset – 2 bits as defined in subclause 10.1 of [3]
When the format 6-1A CRC is scrambled with a RA-RNTI, then the following fields among the fields above are
reserved:
- New data indicator
- Downlink Assignment Index
- HARQ-ACK resource offset
If the UE is not configured to decode MPDCCH with CRC scrambled by the C-RNTI, and the number of information
bits in format 6-1A is less than that of format 6-0A, zeros shall be appended to format 6-1A until the payload size
equals that of format 6-0A.
If the UE is configured to decode MPDCCH with CRC scrambled by the C-RNTI and the number of information bits in
format 6-1A mapped onto a given search space is less than that of format 6-0A for scheduling the same serving cell and
mapped onto the same search space, zeros shall be appended to format 6-1A until the payload size equals that of format
6-0A.
3GPP
Release 13 125 3GPP TS 36.212 V13.9.0 (2019-06)
5.3.3.1.13 Format 6-1B

DCI format 6-1B is used for the scheduling of one PDSCH codeword in one cell.
The following information is transmitted by means of the DCI format 6-1B:
- Flag for format 6-0B/format 6-1B differentiation – 1 bit, where value 0 indicates format 6-0B and value 1
indicates format 6-1B
Format 6-1B is used for random access procedure initiated by a PDCCH order only if format 6-1B CRC is
scrambled with C-RNTI and all the remaining fields are set as follows:
  N DL  
- Reserved bits – log 2  RB   +2 bits, where all bits shall be set to 1
  6  
- PRACH Mask Index – 4 bits [5]
- Starting CE level – 2 bits provide the PRACH starting CE level as defined in [5]
- All the remaining bits in format 6-1B for compact scheduling assignment of one PDSCH codeword are set to
zero
Otherwise,
  N DL  
- Resource block assignment – log 2  RB   +1 bits for PDSCH as defined in [3]:
  6  
  N DL  
  6  
- 1 bit provides the resource allocation within the indicated narrowband, where value 0 indicates RBs with
PRB index {0, 1, 2, 3} and value 1 indicates that all 6 PRBs are used.
- HARQ process number – 1 bit
- HARQ-ACK resource offset – 2 bits as defined in subclause 10.1 of [3]
- DCI subframe repetition number –2 bits as defined in subclause 9.1.5 of [3]
When the format 6-1B CRC is scrambled with a RA-RNTI then the following fields among the fields above are
reserved:
- HARQ-ACK resource offset
If the UE is not configured to decode MPDCCH with CRC scrambled by the C-RNTI, and the number of information
bits in format 6-1B is less than that of format 6-0B, zeros shall be appended to format 6-1B until the payload size equals
that of format 6-0B.
If the UE is configured to decode MPDCCH with CRC scrambled by the C-RNTI and the number of information bits in
format 6-1B mapped onto a given search space is less than that of format 6-0B for scheduling the same serving cell and
3GPP
Release 13 126 3GPP TS 36.212 V13.9.0 (2019-06)
mapped onto the same search space, zeros shall be appended to format 6-1B until the payload size equals that of format
6-0B.
5.3.3.1.14 Format 6-2

DCI format 6-2 is used for paging and direct indication.
The following information is transmitted by means of the DCI format 6-2:
- Flag for paging/direct indication differentiation – 1 bit, with value 0 for direct indication and value 1 for paging
- If Flag=0:
- Direct Indication information – 8 bits provide direct indication of system information update and other fields,
as defined in [6]
- Reserved information bits are added until the size is equal to that of format 6-2 with Flag=1
- If Flag=1:
  N DL  
- Resource block assignment – log 2  RB   bits for the narrowband index as defined in subclause 7.1.6 of
  6  
[3]
5.3.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 a0 , a1 , a 2 , a3 ,...,a A1 , and
the parity bits by p0 , p1 , p 2 , p3 ,..., p L1 . A is the payload size and L is the number of parity bits.
The parity bits are computed and attached according to subclause 5.1.1 setting L to 16 bits, resulting in the
sequence b0 , b1 , b2 , b3 ,...,bB1 , where B = A+ L.
In the case where closed-loop UE transmit antenna selection is not configured or applicable, after attachment, the CRC
parity bits are scrambled with the corresponding RNTI xrnti,0 , xrnti,1 ,...,xrnti,15 , where xrnti, 0 corresponds to the MSB of
the RNTI, to form the sequence of bits c0 , c1 , c 2 , c3 ,...,c B 1 . The relation between ck and bk is:
c k  bk for k = 0, 1, 2, …, A-1
ck  bk  xrnti,k  A mod 2 for k = A, A+1, A+2,..., A+15.
In the case where closed-loop UE transmit antenna selection is configured and applicable, after attachment, the CRC
parity bits with DCI format 0 are scrambled with the antenna selection mask xAS ,0 , xAS ,1 ,..., xAS ,15 as indicated in Table
5.3.3.2-1 and the corresponding RNTI xrnti,0 , xrnti,1 ,...,xrnti,15 to form the sequence of bits c0 , c1 , c 2 , c3 ,...,c B 1 . The
relation between ck and bk is:
c k  bk for k = 0, 1, 2, …, A-1
ck  bk  xrnti,k  A  x AS ,k  A mod 2 for k = A, A+1, A+2,..., A+15.
3GPP
Release 13 127 3GPP TS 36.212 V13.9.0 (2019-06)
Table 5.3.3.2-1: UE transmit antenna selection mask.
UE transmit antenna selection Antenna selection mask

 xAS ,0 , xAS ,1 ,..., xAS ,15 
UE port 0 <0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0>
UE port 1 <0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1>

After encoding the bits are denoted by d 0(i ) , d1(i ) , d 2(i ) , d 3(i ) ,...,d D(i )1 , with i  0,1, and 2 , and where D is the number of
bits on the i-th coded stream, i.e., D  K .

A tail biting convolutionally coded block is delivered to the rate matching block. This block of coded bits is denoted by
d 0(i ) , d1(i ) , d 2(i ) , d 3(i ) ,...,d D(i )1 , with i  0,1, and 2 , and where i is the coded stream index and D is the number of bits in
After rate matching, the bits are denoted by e0 , e1 , e2 , e3 ,...,eE 1 , where E is the number of rate matched bits.
5.3.4 Control format indicator

Data arrives each subframe to the coding unit in the form of an indicator for the time span, in units of OFDM symbols,
of the DCI carried by PDCCH in that subframe of the corresponding DL cell. The CFI takes values CFI = 1, 2 or 3. For
system bandwidths N RBDL
 10 , the span of the DCI carried by PDCCH in units of OFDM symbols, 1, 2 or 3, is given by
DL
the CFI. For system bandwidths N RB  10 , the span of the DCI carried by PDCCH in units of OFDM symbols, 2, 3 or
4, is given by CFI+1.
The coding flow is shown in Figure 5.3.4-1.
CFI
Channel coding
b0 , b1 ,..., b31
Figure 5.3.4-1 Coding for CFI.

The control format indicator is coded according to Table 5.3.4-1.
Table 5.3.4-1: CFI code words.
CFI code word

CFI < b0, b1, …, b31 >
1 <0,1,1,0,1,1,0,1,1,0,1,1,0,1,1,0,1,1,0,1,1,0,1,1,0,1,1,0,1,1,0,1>
3GPP
Release 13 128 3GPP TS 36.212 V13.9.0 (2019-06)
2 <1,0,1,1,0,1,1,0,1,1,0,1,1,0,1,1,0,1,1,0,1,1,0,1,1,0,1,1,0,1,1,0>
3 <1,1,0,1,1,0,1,1,0,1,1,0,1,1,0,1,1,0,1,1,0,1,1,0,1,1,0,1,1,0,1,1>
4
(Reserved) <0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0>
5.3.5 HARQ indicator (HI)

Data arrives to the coding unit in the form of indicators for HARQ acknowledgement for one transport block.
The coding flow is shown in Figure 5.3.5-1.
HI
Channel coding
b0 , b1 , b2
Figure 5.3.5-1 Coding for HI.

The HI is coded according to Table 5.3.5-1, where for a positive acknowledgement HI = 1 and for a negative
acknowledgement HI = 0.
Table 5.3.5-1: HI code words.
HI code word
HI < b0, b1, b2 >
0 < 0,0,0 >
1 < 1,1,1 >
5.4 Sidelink transport channels and control information

5.4.1 Sidelink broadcast channel
Figure 5.4.1-1 shows the processing structure for the SL-BCH transport channel. Data arrives to the coding unit in the
form of a maximum of one transport block. The following coding steps can be identified:
- Channel coding
- Rate matching
The coding steps for SL-BCH transport channel are shown in the figure below. In addition, after rate matching PUSCH
interleaving is applied according to subclauses 5.2.2.7 and 5.2.2.8 without any control information in order to apply a

time-first rather than frequency-first mapping, where Cmux  2  N symb
SL

 3 and the sequence of bits f is equal to e.
3GPP
Release 13 129 3GPP TS 36.212 V13.9.0 (2019-06)
a0 , a1 ,..., a A1
CRC attachment
c0 , c1 ,..., c K 1
Channel coding
d0(i) , d1(i) ,...,d D(i)1
Rate matching
e0 , e1 ,..., e E 1
Figure 5.4.1-1: Transport channel processing for SL-BCH.

Error detection is provided on transport blocks through a Cyclic Redundancy Check (CRC).
The parity bits are computed and attached according to subclause 5.1.1 setting L to 16 bits, resulting in the sequence of
bits c0 , c1 , c2 , c3 ,...,c K 1 where c k  bk for k = 0, 1, 2, …, K-1 and K=A+L.

After encoding the bits are denoted by d 0(i ) , d1(i ) , d 2(i ) , d 3(i ) ,...,d D(i) 1 , with i  0,1, and 2 , and where D is the number of bits
on the i-th coded stream, i.e., D  K .

A tail biting convolutionally coded block is delivered to the rate matching block. This block of coded bits is denoted
by d 0(i ) , d1(i ) , d 2(i ) , d 3(i ) ,...,d D(i) 1 , with i  0,1, and 2 , and where i is the coded stream index and D is the number of bits in
After rate matching, the bits are denoted by e0 , e1 , e2 , e3 ,...,eE 1 , where E is the number of rate matched bits as defined
in subclause 9.6.1 of [2].
5.4.2 Sidelink shared channel

The processing of the sidelink shared channel follows the downlink shared channel according to subclause 5.3.2, with
the following differences:
- Data arrives to the coding unit in the form of a maximum of one transport block every transmission time interval
(TTI)
3GPP
Release 13 130 3GPP TS 36.212 V13.9.0 (2019-06)
- In the step of code block concatenation, the sequence of coded bits corresponding to one transport block after
code block concatenation is referred to as one codeword in subclause 9.3.1 of [2].
- PUSCH interleaving is applied according to subclauses 5.2.2.7 and 5.2.2.8 without any control information in

order to apply a time-first rather than frequency-first mapping, where Cmux  2  N symb
SL
1 . 
5.4.3 Sidelink control information

An SCI transports sidelink scheduling information for one destination ID.
The processing for one SCI follows the downlink control information according to subclause 5.3.3, with the following
differences:
- In the step of CRC attachment, no scrambling is performed.

SL

 1 and the sequence of
bits f is equal to e.
5.4.3.1 SCI formats

The fields defined in the SCI formats below are mapped to the information bits a0 to aA-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 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.
5.4.3.1.1 SCI format 0

SCI format 0 is used for the scheduling of PSSCH.
The following information is transmitted by means of the SCI format 0:
- Frequency hopping flag – 1 bit as defined in subclause 14.1.1 of [3].
 SL
- Resource block assignment and hopping resource allocation – log 2 ( N RB SL
( N RB  1) / 2)  bits
- For PSSCH hopping:
- NSL_hop MSB bits are used to obtain the value of n~PRB (i) as indicated in subclause 8.4 of [3]

-  log 2 ( N RB

SL SL
( N RB 
 1) / 2)  N SL_hop  bits provide the resource allocation in the subframe

- For non-hopping PSSCH:

-  log 2 ( N RB

SL SL
( N RB 
 1) / 2)  bits provide the resource allocation in the subframe as defined in subclause

8.1.1 of [3]
- Time resource pattern – 7 bits as defined in subclause 14.1.1 of [3].
- Timing advance indication – 11 bits as defined in subclause 14.2.1 of [3]
- Group destination ID – 8 bits as defined by higher layers
3GPP
Release 13 131 3GPP TS 36.212 V13.9.0 (2019-06)
5.4.4 Sidelink discovery channel

The processing of the sidelink discovery channel follows the downlink shared channel according to subclause 5.3.2,
with the following differences:
- Data arrives to the coding unit in the form of a maximum of one transport block every transmission time interval
(TTI)
- In the step of code block concatenation, the sequence of coded bits corresponding to one transport block after
code block concatenation is referred to as one codeword in subclause 9.5.1 of [2].

SL
1 .
6 Narrowband IoT
6.1 Mapping to physical channels

For Narrowband IoT, transport channels are mapped onto narrowband physical channels, the channel coding,
multiplexing, and interleaving of which are specified in subclauses 6.3 and 6.4 for the uplink and downlink,
respectively. Table 6.1-1 specifies the mapping of the uplink transport channels to their corresponding physical
channels. Table 6.1-2 specifies the mapping of the downlink transport channels to their corresponding physical
channels.Table 6.1-3 specifies the mapping of control channel information to its corresponding physical channel.
Table 6.1-1

UL-SCH NPUSCH (format 1)
RACH NPRACH
Table 6.1-2

DL-SCH NPDSCH
BCH NPBCH
PCH NPDSCH
Table 6.1-3

UCI NPUSCH (format 2)
DCI NPDCCH
6.2 Generic procedures

The generic procedures for channel coding, multiplexing and interleaving are as in subclause 5.1 unless otherwise noted
in clause 6.
Usage of coding scheme and coding rate for the different types of TrCH is shown in table 6.2-1. Usage of coding
scheme and coding rate for the different control information types is shown in table 6.2-2.
3GPP
Release 13 132 3GPP TS 36.212 V13.9.0 (2019-06)
Table 6.2-1: Usage of channel coding scheme and coding rate for TrCHs.
TrCH Coding scheme Coding rate

UL-SCH Turbo coding 1/3
BCH Tail biting
DL-SCH convolutional 1/3
PCH coding
Table 6.2-2: Usage of channel coding scheme and coding rate for control information.
Control Information Coding scheme Coding rate

Tail biting
DCI convolutional 1/3
coding
UCI Block code 1/16
6.3 Uplink transport channels and control information

6.3.1 Random access channel
The sequence for the random access channel is processed according to [2].
6.3.2 Uplink shared channel

Figure 6.3.2-1 shows the processing structure for the UL-SCH transport channel. Data arrives to the coding unit in the
form of a maximum of one transport block over a number of resource units per UL cell. The number of resource units is
scheduled according to [3]. The following coding steps can be identified:
- CRC attachment
- Channel coding
- Rate matching
a0 , a1 ,..., a A 1
CRC attachment
c0 , c1 ,..., c K 1
Channel coding
d 0(i ) , d1(i ) ,..., d D(i )1
Rate matching
e0 , e1,..., eE 1
Figure 6.3.2-1: Transport block processing for UL-SCH.
3GPP
Release 13 133 3GPP TS 36.212 V13.9.0 (2019-06)
The CRC attachment, channel coding, and rate matching are performed according to subclauses 5.2.2.1, 5.2.2.3, and
5.2.2.4, respectively, with the following differences:
- In subclause 5.1.4.1.2 in the calculation of G  , Qm is 1 for π/2-BPSK and 2 for π/4-QPSK, and rvidx = 0 or 2.
In addition, after rate matching interleaving is applied per resource unit according to subclauses 5.2.2.7 and 5.2.2.8
without any control information in order to apply a time-first rather than frequency-first mapping, where the input
sequence to 5.2.2.7 is the portion of e for a resource unit instead of f, and where Cmux  N symb
UL
 
 1 N slots
UL
is the number of
SC-FDMA symbols for NPUSCH in a UL resource unit as given in subclause 10.1.2.3 of [2].
6.3.3 Uplink control information on NPUSCH without UL-SCH data

When control data is sent via NPUSCH without UL-SCH data and arrives to the coding unit in the form of an indicator
for HARQ acknowledgement for one transport block, the coding flow is as shown in Figure 6.3.3-1.
o0ACK
Channel coding
b0 , b1 , b2 ,..., b15
Figure 6.3.3-1: Coding for HARQ-ACK.
ACK
The one bit information of HARQ-ACK o0 is coded according to Table 6.3.3-1, where for a positive
ACK ACK
acknowledgement o0 = 1 and for a negative acknowledgement o0 = 0.
Table 6.3.3-1: HARQ-ACK code words.
HARQ-ACK HARQ-ACK code word

<o
ACK
> < b0, b1, b2,…,b15 >
0
0 <0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0>
1 <1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1>
6.4 Downlink transport channels and control information

6.4.1 Broadcast channel
The processing structure for the BCH transport channel is according to Subclause 5.3.1, with the following differences:
- The transmission time interval (TTI) is 640ms
- The size of the BCH transport block is set to 34 bits
- The CRC mask for NPBCH is selected according to 1 or 2 transmit antenna ports at eNodeB according to Table
5.3.1.1-1, where the transmit antenna ports are defined in subclause 10.2.6 of [2]
- The number of rate matched bits is defined in subclause 10.2.4.1 of [2].
6.4.2 Downlink shared channel and Paging channel

Figure 6.4.2-1 shows the processing structure for each transport block for the DL-SCH and PCH transport channels.
Data arrives to the coding unit in the form of a maximum of one transport blocks over a number of resource units per
DL cell. The following coding steps can be identified for each transport block of a DL cell:
3GPP
Release 13 134 3GPP TS 36.212 V13.9.0 (2019-06)
- CRC attachment
- Channel coding
- Rate matching
a0 , a1 ,..., a A 1
CRC attachment
c0 , c1 ,..., c K 1
Channel coding
d 0(i ) , d1(i ) ,..., d D(i )1
Rate matching
e0 , e1,..., eE 1
Figure 6.4.2-1: Transport block processing for DL-SCH and PCH.
The CRC attachment, channel coding, and rate matching is performed according to subclauses 5.1.1, 5.1.3.1 and
5.1.4.2, respectively. For the CRC attachment, the parity bits are computed and attached according to subclause 5.1.1
setting L to 24 bits, resulting in the sequence of bits c0 , c1 , c2 , c3 ,...,c K 1 where c k  bk for k = 0, 1, 2, …, K-1 and
K=A+L.
6.4.3 Downlink control information

A DCI transports downlink or uplink scheduling information for one cell and one RNTI. The RNTI is implicitly
encoded in the CRC. The processing structure for one DCI is according to Subclause 5.3.3.
6.4.3.1 DCI Format N0

DCI format N0 is used for the scheduling of NPUSCH in one UL cell.
The following information is transmitted by means of the DCI format N0:
- Flag for format N0/format N1 differentiation – 1 bit, where value 0 indicates format N0 and value 1 indicates
format N1
- Subcarrier indication – 6 bits as defined in subclause 16.5.1.1 of [3]
- Resource assignment – 3 bits as defined in subclause 16.5.1.2 of [3]
- Scheduling delay – 2 bits as defined in subclause 16.5.1 of [3]
- Modulation and coding scheme – 4 bits as defined in subclause 16.5.1.2 of [3]
- Redundancy version – 1 bit as defined in subclause 16.5.1.2 of [3]
- Repetition number – 3 bits as defined in subclause 16.5.1.2 of [3]
- DCI subframe repetition number – 2 bits as defined in subclause 16.6 in [3]
3GPP
Release 13 135 3GPP TS 36.212 V13.9.0 (2019-06)

DCI format N1 is used for the scheduling of one NPDSCH codeword in one cell and random access procedure initiated
by a NPDCCH order. The DCI corresponding to a NPDCCH order is carried by NPDCCH.
- Flag for format N0/format N1 differentiation – 1 bit, where value 0 indicates format N0 and value 1 indicates
format N1
- NPDCCH order indicator – 1 bit
Format N1 is used for random access procedure initiated by a NPDCCH order only if NPDCCH order indicator is
set to '1', format N1 CRC is scrambled with C-RNTI, and all the remaining fields are set as follows:
- Starting number of NPRACH repetitions – 2 bits as defined in subclause 16.3.2 of [3]
- Subcarrier indication of NPRACH – 6 bits as defined in subclause 16.3.2 of [3]
- All the remaining bits in format N1 are set to one
Otherwise,
- Scheduling delay – 3 bits as defined in subclause 16.4.1 of [3]
- HARQ-ACK resource – 4 bits as defined in subclause 16.4.2 of [3].
- DCI subframe repetition number – 2 bits as defined in subclause 16.6 in [3]
When the format N1 CRC is scrambled with a RA-RNTI, then the following fields among the fields above are reserved:
- HARQ-ACK resource
If the number of information bits in format N1 is less than that of format N0, zeros shall be appended to format N1 until
the payload size equals that of format N0.

DCI format N2 is used for paging and direct indication.
Flag for paging/direct indication differentiation – 1 bit, with value 0 for direct indication and value 1 for paging
If Flag=0:
- Direct Indication information – 8 bits provide direct indication of system information update and other fields, as
defined in [6]
- Reserved information bits are added until the size is equal to that of format N2 with Flag=1
If Flag=1:
3GPP
Release 13 136 3GPP TS 36.212 V13.9.0 (2019-06)
- DCI subframe repetition number – 3 bits as defined in subclause 16.6 of [3]
3GPP
Release 13 137 3GPP TS 36.212 V13.9.0 (2019-06)
Annex A (informative):
Change history
Change history
Date TSG # TSG Doc. CR Rev Subject/Comment Old New
2006-09 Skeleton 0.0.0
2006-10 Updated skeleton 0.0.0 0.0.1
2006-10 Endorsed skeleton 0.0.1 0.1.0
2006-11 Added TC. Added Broadcast, Paging and MBMS transport 0.1.0 0.1.1
channels in Table 4.2-1.
2006-11 Endorsed v 0.2.0 0.1.1 0.2.0
2006-12 Added CC. Added type of coding for each transport channel or 0.2.0 0.2.1
control information.
2007-01 Editor's version 0.2.1 0.2.2
2007-01 Endorsed v 0.3.0 0.2.2 0.3.0
2007-02 Added QPP turbo Interleaver description. 0.3.0 0.3.1
2007-02 Editor's version 0.3.1 0.3.2
2007-02 Endorsed v 0.4.0 0.3.2 0.4.0
2007-02 Added CRC details for PDSCH, PDCCH and PUSCH. Added 0.4.0 0.4.1
QPP turbo-interleaver parameters. Set Z to 6144. Added details
on code block segmentation.
2007-02 Editor's version 0.4.1 0.4.2
2007-03 RAN#35 RP-070170 For information at RAN#35 0.4.2 1.0.0
2007-03 Editor's version 1.0.0 1.0.1
2007-03 Editor's version 1.0.1 1.1.0
2007-05 Editor's version 1.1.0 1.1.1
2007-05 Editor's version 1.1.1 1.1.2
2007-05 Editor's version 1.1.2 1.2.0
2007-06 Added circular buffer rate matching for PDSCH and PUSCH. 1.2.0 1.2.1
Miscellaneous changes.
2007-06 Editor's version 1.2.1 1.2.2
2007-07 Editor's version 1.2.2 1.2.3
2007-07 Endorsed by email following decision taken at RAN1#49b 1.2.3 1.3.0
2007-08 Editor's version including decision from RAN1#49bis. 1.3.0 1.3.1
2007-08 Editor's version 1.3.1 1.3.2
2007-08 Editor's version 1.3.2 1.4.0
2007-09 Editor's version with decisions from RAN1#50 1,4.0 1,4,1
2007-09 Editor's version 1.4.1 1.4.2
10/09/07 RAN#37 RP-070730 - - For approval at RAN#37 1.4.2 2.0.0
12/09/07 RAN_37 RP-070730 - - Approved version 2.0.0 8.0.0
28/11/07 RAN_38 RP-070949 0001 - Update of 36.212 8.0.0 8.1.0
05/03/08 RAN_39 RP-080145 0002 - Update to 36.212 incorporating decisions from RAN1#51bis and 8.1.0 8.2.0
RAN1#52
28/05/08 RAN_40 RP-080433 0003 - Joint coding of CQI and ACK on PUCCH 8.2.0 8.3.0
28/05/08 RAN_40 RP-080433 0004 1 ACK insertion into PUSCH 8.2.0 8.3.0
28/05/08 RAN_40 RP-080433 0005 1 Introduction of format 1C 8.2.0 8.3.0
28/05/08 RAN_40 RP-080433 0006 1 Miscellaneous fixes to 36.212 8.2.0 8.3.0
28/05/08 RAN_40 RP-080433 0008 1 On multiplexing scheme for indicators 8.2.0 8.3.0
28/05/08 RAN_40 RP-080433 0009 1 On the soft buffer split of MIMO and TDD 8.2.0 8.3.0
28/05/08 RAN_40 RP-080433 0010 - Resource assignment field for distributed VRB 8.2.0 8.3.0
28/05/08 RAN_40 RP-080433 0011 - Clarifying the use of the different DCI formats 8.2.0 8.3.0
28/05/08 RAN_40 RP-080433 0012 1 Clarifying the value of NL 8.2.0 8.3.0
28/05/08 RAN_40 RP-080433 0013 - Payload size for DCI formats 3 and 3A 8.2.0 8.3.0
28/05/08 RAN_40 RP-080433 0014 - Coding of ACK on PUSCH 8.2.0 8.3.0
28/05/08 RAN_40 RP-080433 0015 1 Coding of RI on PUSCH and mapping 8.2.0 8.3.0
28/05/08 RAN_40 RP-080433 0016 - CRC for control information on PUSCH 8.2.0 8.3.0
28/05/08 RAN_40 RP-080433 0017 - Introduction of Downlink Assignment Index 8.2.0 8.3.0
28/05/08 RAN_40 RP-080433 0018 - Coding of CQI/PMI on PUSCH coming from PUCCH 8.2.0 8.3.0
28/05/08 RAN_40 RP-080433 0019 - Simultaneous transmission of aperiodic CQI and UL control 8.2.0 8.3.0
28/05/08 RAN_40 RP-080433 0020 - Encoding of antenna indicator on DCI format 0 8.2.0 8.3.0
28/05/08 RAN_40 RP-080433 0021 - PDCCH coverage in narrow bandwidths 8.2.0 8.3.0
28/05/08 RAN_40 RP-080433 0022 - Closed-loop and open-loop spatial multiplexing 8.2.0 8.3.0
28/05/08 RAN_40 RP-080457 0023 - Formula for linkage between PUSCH MCS and amount of 8.2.0 8.3.0
resources used for control
09/09/08 RAN_41 RP-080669 0026 - Correction to PUSCH Channel Interleaver 8.3.0 8.4.0
09/09/08 RAN_41 RP-080669 0028 - Correction of mapping of ACK/NAK to binary bit values 8.3.0 8.4.0
09/09/08 RAN_41 RP-080669 0029 - Correction to bit collection, selection and transmission 8.3.0 8.4.0
3GPP
Release 13 138 3GPP TS 36.212 V13.9.0 (2019-06)
Change history
09/09/08 RAN_41 RP-080669 Padding one bit to DCI format 1 when format 1 and format 0/1A 8.3.0 8.4.0
0030 -
have the same size
09/09/08 RAN_41 RP-080669 0031 - Modification of M_limit 8.3.0 8.4.0
09/09/08 RAN_41 RP-080669 0032 - Definition of Formats 2 and 2A 8.3.0 8.4.0
09/09/08 RAN_41 RP-080669 0033 2 Corrections to DCI formats 8.3.0 8.4.0
09/09/08 RAN_41 RP-080669 0035 1 Format 1B confirmation flag 8.3.0 8.4.0
09/09/08 RAN_41 RP-080669 Corrections to Rank information scrambling in Uplink Shared 8.3.0 8.4.0
0036 -
Channel
09/09/08 RAN_41 RP-080669 0037 2 Clarification of TPC commands signaled in DCI formats 3/3A 8.3.0 8.4.0
09/09/08 RAN_41 RP-080669 0038 - Clarification on UE transmit antenna selection mask 8.3.0 8.4.0
09/09/08 RAN_41 RP-080669 0039 1 Linking of control resources in PUSCH to data MCS 8.3.0 8.4.0
09/09/08 RAN_41 RP-080669 0041 - Definition of Bit Mapping for DCI signalling 8.3.0 8.4.0
09/09/08 RAN_41 RP-080669 0042 1 Clarification on resource allocation in DCI format 1/2/2A 8.3.0 8.4.0
09/09/08 RAN_41 RP-080669 DCI Format 1A changes needed for scheduling Broadcast 8.3.0 8.4.0
0043 -
Control
09/09/08 RAN_41 RP-080669 0044 - DCI format1C 8.3.0 8.4.0
09/09/08 RAN_41 RP-080669 0045 - Miscellaneous corrections 8.3.0 8.4.0
11/09/08 RAN_41 RP-080736 0046 1 Correction on downlink multi-user MIMO 8.3.0 8.4.0
09/09/08 RAN_41 RP-080669 Corrections to DL DCI Formats In case of Ambiguous Payload 8.3.0 8.4.0
0047 -
Sizes
09/09/08 RAN_41 RP-080669 CR for RE provisioning for the control information in case of 8.3.0 8.4.0
0048 -
CQI-only transmission on PUSCH
09/09/08 RAN_41 RP-080669 0091 2 Coding and multiplexing of multiple ACK/NACK in PUSCH 8.3.0 8.4.0
03/12/08 RAN_42 RP-080983 Clarification of input bits corresponding to 2-bit HARQ-ACK and 8.4.0 8.5.0
0050 2
2-bit RI
03/12/08 RAN_42 RP-080983 0053 - Editorial corrections to 36.212 8.4.0 8.5.0
03/12/08 RAN_42 RP-080983 0055 - Miscellaneous Corrections 8.4.0 8.5.0
03/12/08 RAN_42 RP-080983 0057 - Clarification of mapping of information bits 8.4.0 8.5.0
03/12/08 RAN_42 RP-080983 Completion of 36.212 CR47 (R1-083421) for "new" DCI 8.4.0 8.5.0
0058 -
Formats
03/12/08 RAN_42 RP-080983 Change for determining DCI format 1A TBS table column 8.4.0 8.5.0
0059 -
indicator for broadcast control
03/12/08 RAN_42 RP-080983 0061 2 Defining DCI format 1A for downlink data arrival 8.4.0 8.5.0
03/12/08 RAN_42 RP-080983 0063 1 ACK/NACK transmission on PUSCH for LTE TDD 8.4.0 8.5.0
03/12/08 RAN_42 RP-080983 0065 - Correction in 36.212 related to TDD downlink HARQ processes 8.4.0 8.5.0
03/12/08 RAN_42 RP-080983 0067 1 Correction of control MCS offset and SRS symbol puncturing 8.4.0 8.5.0
03/12/08 RAN_42 RP-080983 0068 1 DCI format 2/2A 8.4.0 8.5.0
03/12/08 RAN_42 RP-080983 0069 - Correction to zero padding in DCI format 1 8.4.0 8.5.0
03/12/08 RAN_42 RP-080983 0071 - Clarification of RI bit field mapping for PUCCH 8.4.0 8.5.0
03/12/08 RAN_42 RP-080983 0072 - Clarifying RNTI bit mapping for PDCCH CRC scrambling 8.4.0 8.5.0
03/12/08 RAN_42 RP-080983 0073 - Clarification on BCH transport block size 8.4.0 8.5.0
03/12/08 RAN_42 RP-080983 Clarification on the number of PUCCH-based CQI/PMI bits 8.4.0 8.5.0
0076 -
when reported on PUSCH
04/03/09 RAN_43 RP-090235 77 1 Corrections to Transmitted Rank Indication 8.5.0 8.6.0
04/03/09 RAN_43 RP-090235 79 1 Correction to the bundled ACK/NACK and DAI transmission 8.5.0 8.6.0
04/03/09 RAN_43 RP-090235 80 2 Corrections to transmission modes 8.5.0 8.6.0
04/03/09 RAN_43 RP-090235 81 1 Correction on ACKNACK transmission on PUSCH for LTE TDD 8.5.0 8.6.0
04/03/09 RAN_43 RP-090235 82 2 Corrections to CQI and RI fields description 8.5.0 8.6.0
04/03/09 RAN_43 RP-090235 83 - Clarifying DCI format 1A and DCI Format 1B 8.5.0 8.6.0
04/03/09 RAN_43 RP-090235 92 1 Clarification on channel coding for UCI HARQ-ACK 8.5.0 8.6.0
27/05/09 RAN_44 RP-090528 Clarify some parameters for determining control resources on 8.6.0 8.7.0
87 -
PUSCH
01/12/09 RAN_46 RP-091168 89 - Clarification on bitwidth of RI 8.7.0 8.8.0
01/12/09 RAN_46 RP-091168 94 - Correction to Channel interleaver for PUSCH RE Mapping 8.7.0 8.8.0
01/12/09 RAN_46 RP-091177 88 1 Editorial corrections to 36.212 8.8.0 9.0.0
01/12/09 RAN_46 RP-091257 95 1 Introduction of enhanced dual layer transmission 8.8.0 9.0.0
16/03/10 RAN_47 RP-100210 96 1 MCCH change notification using DCI format 1C 9.0.0 9.1.0
16/03/10 RAN_47 RP-100211 Addition of missing reference to DCI format 2B + typo 9.0.0 9.1.0
97 -
corrections
01/06/10 RAN_48 RP-100589 98 - Correction to TBS determination for DCI format 1C 9.1.0 9.2.0
14/09/10 RAN_49 RP-100899 99 - Clarify soft buffer size determination for MCH 9.2.0 9.3.0
07/12/10 RAN_50 RP-101320 100 - Introduction of Rel-10 LTE-Advanced features in 36.212 9.3.0 10.0.0
15/03/11 RAN_51 RP-110254 101 - Correction on UE behavior upon receiving DCI format 1B 10.0.0 10.1.0
15/03/11 RAN_51 RP-110256 102 - Corrections to Rel-10 LTE-Advanced features in 36.212 10.0.0 10.1.0
01/06/11 RAN_52 RP-110819 103 3 Correction of DCI format 0 and 4 resource allocation 10.1.0 10.2.0
01/06/11 RAN_52 RP-110819 104 2 Correction to Multi-cluster flag in DCI format 0 10.1.0 10.2.0
01/06/11 RAN_52 RP-110819 107 2 Corrections on HARQ-ACK Channel Coding in the PUSCH 10.1.0 10.2.0
01/06/11 RAN_52 RP-110820 108 3 A clarification for DCI format payload size 10.1.0 10.2.0
01/06/11 RAN_52 RP-110819 110 1 Correction the search space and RNTI for CQI and SRS 10.1.0 10.2.0
request flag
3GPP
Release 13 139 3GPP TS 36.212 V13.9.0 (2019-06)
Change history
01/06/11 RAN_52 RP-110819 111 - Resource dimensioning for CQI only PUSCH transmission 10.1.0 10.2.0
01/06/11 RAN_52 RP-110820 112 1 Correction on bit representations of transport block processing 10.1.0 10.2.0
for UL-SCH
01/06/11 RAN_52 RP-110818 113 - Clarification on PMI indication in DCI format1B and format 2 10.1.0 10.2.0
01/06/11 RAN_52 RP-110820 114 1 Rate maching parameters for CA 10.1.0 10.2.0
01/06/11 RAN_52 RP-110819 116 - HARQ-ACK on PUSCH for TDD with channel selection 10.1.0 10.2.0
configured for 2 serving cells
01/06/11 RAN_52 RP-110823 117 - Single codeword multiple layer transmission in uplink 10.1.0 10.2.0
15/09/11 RAN_53 RP-111228 119 1 Corrections on transport block processing for UL-SCH 10.2.0 10.3.0
15/09/11 RAN_53 RP-111230 120 2 On correction of channel coding of control information 10.2.0 10.3.0
15/09/11 RAN_53 RP-111230 122 1 Size adjustment of DCI format 0, 1A and 1 10.2.0 10.3.0
15/09/11 RAN_53 RP-111232 123 1 Corrections on Nsrs 10.2.0 10.3.0
15/09/11 RAN_53 RP-111232 124 2 Corrections on DCI format 1B/1D 10.2.0 10.3.0
15/09/11 RAN_53 RP-111228 125 - Minor Correction on DCI Format 1 Description 10.2.0 10.3.0
15/09/11 RAN_53 RP-111226 127 - Correction on ACK/NACK mapping 10.2.0 10.3.0
15/09/11 RAN_53 Corrections on channel coding of control information and DCI 10.2.0 10.3.0
RP-111231 128 -
Format 4.
15/09/11 RAN_53 Clarification and correction to configuration signalling condition 10.2.0 10.3.0
RP-111229 129 -
for channel quality information formats
05/12/11 RAN_54 RP-111667 130 1 Corrections on codebook index indication in DCI format 4 10.3.0 10.4.0
05/12/11 RAN_54 RP-111666 131 - HARQ-ACK on UCI-only PUSCH without UL-SCH data 10.3.0 10.4.0
28/02/12 RAN_55 RP-120283 132 2 Corrections on payload size adjustment for DCI format 1A and 1 10.4.0 10.5.0
28/02/12 RAN_55 RP-120283 133 1 Correction of two HARQ-ACK feedback on PUSCH 10.4.0 10.5.0
28/02/12 RAN_55 RP-120285 134 1 Miscellaneous corrections 10.4.0 10.5.0
13/06/12 RAN_56 RP-120739 136 - Correction to Data and control multiplexing 10.5.0 10.6.0
13/06/12 RAN_56 Correction to CSI request field size in DCI format 0 and DCI 10.5.0 10.6.0
RP-120737 138 -
format 4
04/09/12 RAN_57 RP-121272 139 - Introduction of Rel-11 LTE-Advanced features in 36.212 10.6.0 11.0.0
04/12/12 RAN_58 RP-121839 143 - Correction to the parameter ue-Category-v10xy 11.0.0 11.1.0
04/12/12 RAN_58 RP-121846 144 - Finalisation for introducing Rel-11 features 11.0.0 11.1.0
26/02/13 RAN_59 Additional clarifications/corrections for introducing Rel-11 11.1.0 11.2.0
RP-130255 145 -
features
11/06/13 RAN_60 RP-130751 147 2 Correction on the RI bit width 11.2.0 11.3.0
11/06/13 RAN_60 RP-130747 148 - CR on DCI Format 4 payload size 11.2.0 11.3.0
11/06/13 RAN_60 RP-130752 149 - Correction on the time span of the DCI 11.2.0 11.3.0
11/06/13 RAN_60 RP-130752 150 - Correction on ARO bit setting for DL DCIs carried by EPDCCH 11.2.0 11.3.0
11/06/13 RAN_60 RP-130750 151 - Clarification on DL DAI usage in inter-band TDD CA 11.2.0 11.3.0
11/06/13 RAN_60 Correction to bit padding of DCI format 1A for secondary cell 11.2.0 11.3.0
RP-130749 153 -
without uplink component carrier
03/12/13 RAN_62 RP-131893 155 1 Correction on parameter ue-Category 11.3.0 11.4.0
03/12/13 RAN_62 RP-131896 154 3 Introduction of Rel 12 feature for Downlink MIMO Enhancement 11.4.0 12.0.0
10/06/14 RAN_64 RP-140858 156 - Clarification on UE antenna port based CRC masking 12.0.0 12.1.0
10/06/14 RAN_64 RP-140859 157 1 Correction on UCI multiplexing on PUSCH 12.0.0 12.1.0
10/06/14 RAN_64 RP-140862 158 - Introduction of Rel 12 features of TDD-FDD CA and eIMTA 12.0.0 12.1.0
10/06/14 RAN_64 RP-140858 159 - Clarification of downlink subframes 12.0.0 12.1.0
10/09/14 RAN_65 RP-141485 161 - CR for 36.212 on 256QAM and LC-MTC 12.1.0 12.2.0
08/12/14 RAN_66 RP-142106 163 3 CR for 36.212 on 256QAM and LC-MTC 12.2.0 12.3.0
08/12/14 RAN_66 RP-142098 164 3 Clarification of PUSCH rate matching with SRS 12.2.0 12.3.0
08/12/14 RAN_66 RP-142107 166 - Introduction of Dual Connectivity feature into 36.212 12.2.0 12.3.0
09/03/15 RAN_67 RP-150366 162 3 Introduction of D2D feature into 36.212 12.3.0 12.4.0
15/06/15 RAN_68 RP-150936 169 - Corrections on eIMTA RRC parameter naming 12.4.0 12.5.0
15/06/15 RAN_68 RP-150937 171 1 Correction for 36.212 on soft buffer assumption 12.4.0 12.5.0
14/09/15 RAN_69 RP-151466 174 1 Introducing 4-layer MIMO transmission in TM3 and TM4 12.5.0 12.6.0
14/09/15 RAN_69 Introduction of MIMO capability signalling for intra-band 12.50 12.6.0
RP-151467 175 2
contiguous CA
07/12/15 RAN_70 RP-152038 177 - Correction on rank indication bit widths 12.6.0 12.7.0
07/12/15 RAN_70 RP-152027 178 1 Introduction of Rel 13 feature of eCA 12.7.0 13.0.0
07/12/15 RAN_70 RP-152025 179 1 Introduction of EB/FD-MIMO 12.7.0 13.0.0
07/12/15 RAN_70 RP-152026 180 2 Introduction of Rel 13 feature of LAA 12.7.0 13.0.0
07/12/15 RAN_70 RP-152031 182 - Introduction of Rel 13 features for SC-PTM 12.7.0 13.0.0
Change history
Date Meeting TDoc CR Rev Cat Subject/Comment New
version
13.1.0
2016-03 RAN#71 RP-160361 0181 3 B Introduction of Rel-13 features of eMTC in 36.212
13.1.0
2016-03 RAN#71 RP-160358 0185 - F CR on mismatch between 36.212 and 36.331
3GPP
Release 13 140 3GPP TS 36.212 V13.9.0 (2019-06)
13.1.0
2016-03 RAN#71 RP-160358 0186 - F Clarification on Class B CSI report
Correction to RI reporting for UE category with MIMO capability of 13.1.0
2016-03 RAN#71 RP-160365 0189 - A
1 layer
13.1.0
2016-03 RAN#71 RP-160358 0191 - F CR on CRI-RI payload restriction for non-eCA UE
13.2.0
2016-06 RAN#72 RP-161067 0192 3 B Introduction of Rel-13 feature of NB-IoT in 36.212
13.2.0
2016-06 RAN#72 RP-161062 0194 - F Correction on aperiodic CSI reporting mode 1-0 and 1-1
13.2.0
2016-06 RAN#72 RP-161063 0195 - F Correction to S1 and S2 definition and i2 bit width
13.2.0
2016-06 RAN#72 RP-161066 0196 1 F MCS field in DCI format 6-2 for paging for MTC
13.2.0
2016-06 RAN#72 RP-161062 0197 - F Coding of higher layer parameter codebooksizeDetermination-r13
13.2.0
2016-06 RAN#72 RP-161065 0198 - F CR on subframe configuration for LAA
13.2.0
2016-06 RAN#72 RP-161063 0199 - F Correction on the description of DMRS table
13.2.0
2016-06 RAN#72 RP-161065 0200 - F Clarification on the applicability of DL procedures for LAA SCell
13.2.0
2016-06 RAN#72 RP-161062 0201 - F Correction on DAI Presence in DCI formats for eCA
13.2.0
2016-06 RAN#72 RP-161066 0202 - F Identify MPDCCH order in CE mode B in TS 36.212 (Solution 2)
13.2.0
2016-06 RAN#72 RP-161063 0203 - F CR on missing CRI-only table (36.212)
13.2.0
2016-06 RAN#72 RP-161062 0205 - F Correction on citations to a DAI bits table
13.2.0
2016-06 RAN#72 RP-161066 0206 1 F Frequency hopping flag definition in DCI formats for BL/CE UE
13.2.0
2016-06 RAN#72 RP-161066 0207 - F Correction on the DCI payload size for eMTC in TS 36.212
13.2.0
2016-06 RAN#72 RP-161066 0208 - F Channel interleaver correction for eMTC
13.3.0
2016-09 RAN#73 RP-161563 0211 - F Correction on BCH rate matching in TS 36.212
13.3.0
2016-09 RAN#73 RP-161560 0213 - F Correction on bitwidth of CLASS A codebook
13.3.0
2016-09 RAN#73 RP-161560 0214 - F Corrections on CRI bit width in 36.212
13.3.0
2016-09 RAN#73 RP-161562 0215 - F Subband CQI report and TM6
CR for clarification of DCI sizes for format 6-1A (TM6 and TM9) in 13.3.0
2016-09 RAN#73 RP-161562 0216 1 F
TS 36.212
13.3.0
2016-09 RAN#73 RP-161569 0219 - F Correction on SRS request field in DCI format 1A for Rel-13 LAA
13.3.0
2016-09 RAN#73 RP-161925 0220 - F Introduction of 1.2Gbps and 1.6Gbps UE categories in Rel-13
13.4.0
2016-12 RAN#74 RP-162359 0230 1 F Correction on DCI Format N1 in 36.212
13.5.0
2017-03 RAN#75 RP-170612 0242 - F Correction on soft buffer calculation for UE category 17 in Rel-13
13.5.0
2017-03 RAN#75 RP-170609 0244 - F DAI in eMTC
CR for applicability of spatial bundling for PUCCH format 3 with 13.6.0
2017-06 RAN#76 RP-171193 0252 - F
FDD PCell
13.6.0
2017-06 RAN#76 RP-171209 0254 - F Corrections on bit width of PMI for wideband CQI reports in 36.212
Correction on total number of soft channel bits for Cat M1 UE in 13.6.0
2017-06 RAN#76 RP-171196 0262 - F
36.212
13.7.0
2017-12 RAN#78 RP-172678 0269 - F Clarification for DAI for eCA
13.7.0
2017-12 RAN#78 RP-172690 0275 - A Correction on number of SRS symbol for UCI multiplexing
2018-01 - MCC clean-up to correct indentation issues in clause 5 13.7.1
13.8.0
2018-06 RAN#80 RP-181162 0281 - F Ordering of P-CSI plus SR in eCA
13.9.0
2019-06 RAN#84 RP-191276 0317 - F Clarification on the bitwidth of report type 1a for FD-MIMO Class A
13.9.0
2019-06 RAN#84 RP-191275 0320 - F Spatial bundling for PUCCH format 3 with more than 5 CC
3GPP

Layer 1

Uploaded by

Copyright:

Available Formats

Layer 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Layer 1

Uploaded by

Copyright:

Available Formats

3GPP TS 36.212 V13.9.

3rd Generation Partnership Project;

3GPP support office address

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

5.2.4.2 Control information mapping ............................................................................................................... 96

6.4.2 Downlink shared channel and Paging channel ......................................................................................... 133

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

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

3 Definitions, symbols and abbreviations

BL/CE: A Bandwidth-reduced Low-complexity or Coverage Enhanced (BL/CE) UE is capable of coverage

BCH Broadcast channel

4 Mapping to physical channels

TrCH Physical Channel

Control information Physical Channel

TrCH Physical Channel

Control information Physical Channel

TrCH Physical Channel

Control information Physical Channel

5 Channel coding, multiplexing and interleaving

5.1 Generic procedures

5.1.1 CRC calculation

- gCRC24A(D) = [D24 + D23 + D18 + D17 + D14 + D11 + D10 + D7 + D6 + D5 + D4 + D3 + D + 1] and;

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

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

- gCRC8(D) = [D8 + D7 + D4 + D3 + D + 1] for a CRC length of L = 8.

a0 D A 23  a1 D A 22  ... a A1 D 24  p0 D 23  p1 D 22  ... p 22 D1  p 23

yields a remainder equal to 0 when divided by gCRC16(D), and the polynomial:

a0 D A 7  a1D A 6  ...  a A1D8  p0 D7  p1D6  ...  p6 D1  p7

yields a remainder equal to 0 when divided by gCRC8(D).

bk  p k  A for k = A, A+1, A+2,..., A+L-1.

5.1.2 Code block segmentation and code block CRC attachment

Total number of code blocks C is determined by:

Number of code blocks: C  1

Number of code blocks: C  B / Z  L .

Number of bits in each code block (applicable for C  0 only):

First segmentation size: K  = minimum K in table 5.1.3-3 such that C  K  B 

the number of code blocks with length K  is C  =1, K   0 , C   0

Second segmentation size: K  = maximum K in table 5.1.3-3 such that K  K 

Number of segments of size K  : C   C  C  .

Number of filler bits: F  C   K   C   K   B 

for k = 0 to F-1 -- Insertion of filler bits

5.1.3 Channel coding

The following channel coding schemes can be applied to TrCHs:

- tail biting convolutional coding;

The values of D in connection with each coding scheme:

- tail biting convolutional coding with rate 1/3: D = K;

- turbo coding with rate 1/3: D = K + 4.

TrCH Coding scheme Coding rate

Control Information Coding scheme Coding rate

5.1.3.1 Tail biting convolutional coding

The configuration of the convolutional encoder is presented in figure 5.1.3-1.

d k(0) G0 = 133 (octal)

d k(1) G1 = 171 (octal)

Figure 5.1.3-1: Rate 1/3 tail biting convolutional encoder.