ETSI TS 136 212 V8.4.0 (2008-11)
Technical Specification
LTE;
Evolved Universal Terrestrial Radio Access (E-UTRA);
Multiplexing and channel coding
(3GPP TS 36.212 version 8.4.0 Release 8)
3GPP TS 36.212 version 8.4.0 Release 8
1
ETSI TS 136 212 V8.4.0 (2008-11)
Reference
RTS/TSGR-0136212v840
Keywords
LTE
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
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.
© European Telecommunications Standards Institute 2008.
All rights reserved.
TM
TM
TM
TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
2
ETSI TS 136 212 V8.4.0 (2008-11)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
http://webapp.etsi.org/key/queryform.asp.
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
3
ETSI TS 136 212 V8.4.0 (2008-11)
Contents
Intellectual Property Rights ................................................................................................................................2
Foreword.............................................................................................................................................................2
Foreword.............................................................................................................................................................5
1
Scope ........................................................................................................................................................6
2
References ................................................................................................................................................6
3
Definitions, symbols and abbreviations ...................................................................................................6
3.1
3.2
3.3
4
4.1
4.2
5
Definitions..........................................................................................................................................................6
Symbols..............................................................................................................................................................6
Abbreviations .....................................................................................................................................................7
Mapping to physical channels ..................................................................................................................7
Uplink.................................................................................................................................................................7
Downlink............................................................................................................................................................7
Channel coding, multiplexing and interleaving........................................................................................8
5.1
Generic procedures.............................................................................................................................................8
5.1.1
CRC calculation............................................................................................................................................8
5.1.2
Code block segmentation and code block CRC attachment .........................................................................9
5.1.3
Channel coding ...........................................................................................................................................10
5.1.3.1
Tail biting convolutional coding ...........................................................................................................11
5.1.3.2
Turbo coding .........................................................................................................................................12
5.1.3.2.1
Turbo encoder..................................................................................................................................12
5.1.3.2.2
Trellis termination for turbo encoder...............................................................................................13
5.1.3.2.3
Turbo code internal interleaver........................................................................................................13
5.1.4
Rate matching .............................................................................................................................................15
5.1.4.1
Rate matching for turbo coded transport channels ................................................................................15
5.1.4.1.1
Sub-block interleaver.......................................................................................................................15
5.1.4.1.2
Bit collection, selection and transmission........................................................................................16
5.1.4.2
Rate matching for convolutionally coded transport channels and control information.........................18
5.1.4.2.1
Sub-block interleaver.......................................................................................................................18
5.1.4.2.2
Bit collection, selection and transmission........................................................................................19
5.1.5
Code block concatenation ...........................................................................................................................20
5.2
Uplink transport channels and control information ..........................................................................................20
5.2.1
Random access channel ..............................................................................................................................20
5.2.2
Uplink shared channel ................................................................................................................................20
5.2.2.1
Transport block CRC attachment ..........................................................................................................21
5.2.2.2
Code block segmentation and code block CRC attachment..................................................................22
5.2.2.3
Channel coding of UL-SCH..................................................................................................................22
5.2.2.4
Rate matching .......................................................................................................................................22
5.2.2.5
Code block concatenation .....................................................................................................................22
5.2.2.6
Channel coding of control information .................................................................................................22
5.2.2.6.1
Channel quality information formats for wideband CQI reports.....................................................25
5.2.2.6.2
Channel quality information formats for higher layer configured subband CQI reports.................26
5.2.2.6.3
Channel quality information formats for UE selected subband CQI reports ...................................26
5.2.2.6.4
Channel coding for CQI/PMI information in PUSCH.....................................................................27
5.2.2.7
Data and control multiplexing...............................................................................................................28
5.2.2.8
Channel interleaver ...............................................................................................................................29
5.2.3
Uplink control information on PUCCH ......................................................................................................31
5.2.3.1
Channel coding for UCI HARQ-ACK ..................................................................................................31
5.2.3.2
Channel coding for UCI scheduling request .........................................................................................31
5.2.3.3
Channel coding for UCI channel quality information ...........................................................................31
5.2.3.3.1
Channel quality information formats for wideband reports.............................................................32
5.2.3.3.2
Channel quality information formats for UE-selected sub-band reports .........................................33
5.2.3.4
Channel coding for UCI channel quality information and HARQ-ACK ..............................................34
5.2.4
Uplink control information on PUSCH without UL-SCH data ..................................................................34
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
4
ETSI TS 136 212 V8.4.0 (2008-11)
5.2.4.1
Channel coding of control information .................................................................................................35
5.2.4.2
Control information mapping................................................................................................................35
5.2.4.3
Channel interleaver ...............................................................................................................................36
5.3
Downlink transport channels and control information .....................................................................................36
5.3.1
Broadcast channel .......................................................................................................................................36
5.3.1.1
Transport block CRC attachment ..........................................................................................................36
5.3.1.2
Channel coding .....................................................................................................................................37
5.3.1.3
Rate matching .......................................................................................................................................37
5.3.2
Downlink shared channel, Paging channel and Multicast channel .............................................................37
5.3.2.1
Transport block CRC attachment ..........................................................................................................38
5.3.2.2
Code block segmentation and code block CRC attachment..................................................................38
5.3.2.3
Channel coding .....................................................................................................................................38
5.3.2.4
Rate matching .......................................................................................................................................39
5.3.2.5
Code block concatenation .....................................................................................................................39
5.3.3
Downlink control information ....................................................................................................................39
5.3.3.1
DCI formats...........................................................................................................................................40
5.3.3.1.1
Format 0 ..........................................................................................................................................40
5.3.3.1.2
Format 1 ..........................................................................................................................................41
5.3.3.1.3
Format 1A........................................................................................................................................41
5.3.3.1.3A
Format 1B........................................................................................................................................43
5.3.3.1.4
Format 1C........................................................................................................................................44
5.3.3.1.4A
Format 1D........................................................................................................................................44
5.3.3.1.5
Format 2 ..........................................................................................................................................45
5.3.3.1.5A
Format 2A........................................................................................................................................49
5.3.3.1.6
Format 3 ..........................................................................................................................................51
5.3.3.1.7
Format 3A........................................................................................................................................51
5.3.3.2
CRC attachment ....................................................................................................................................51
5.3.3.3
Channel coding .....................................................................................................................................52
5.3.3.4
Rate matching .......................................................................................................................................52
5.3.4
Control format indicator .............................................................................................................................52
5.3.4.1
Channel coding .....................................................................................................................................53
5.3.5
HARQ indicator..........................................................................................................................................53
5.3.5.1
Channel coding .....................................................................................................................................53
Annex A (informative):
Change history ...............................................................................................55
History ..............................................................................................................................................................57
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
5
ETSI TS 136 212 V8.4.0 (2008-11)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
Y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
1
6
ETSI TS 136 212 V8.4.0 (2008-11)
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".
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].
Definition format
<defined term>: <definition>.
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
PUSCH
N symb
Uplink bandwidth configuration, expressed in number of resource blocks [2]
UL
N symb
Number of SC-FDMA symbols in an uplink slot
N SRS
Number of SC-FDMA symbols used for SRS transmission in a subframe (0 or 1).
Number of SC-FDMA symbols carrying PUSCH in a subframe
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
3.3
7
ETSI TS 136 212 V8.4.0 (2008-11)
Abbreviations
For the purposes of the present document, the following abbreviations apply:
BCH
CFI
CP
DCI
DL-SCH
FDD
HI
MCH
PBCH
PCFICH
PCH
PDCCH
PDSCH
PHICH
PMCH
PMI
PRACH
PUCCH
PUSCH
RACH
RI
SRS
TDD
TPMI
TRI
UL-SCH
Broadcast channel
Control Format Indicator
Cyclic Prefix
Downlink Control Information
Downlink Shared channel
Frequency Division Duplexing
HARQ indicator
Multicast channel
Physical Broadcast channel
Physical Control Format Indicator channel
Paging channel
Physical Downlink Control channel
Physical Downlink Shared channel
Physical HARQ indicator channel
Physical Multicast channel
Precoding Matrix Indicator
Physical Random Access channel
Physical Uplink Control channel
Physical Uplink Shared channel
Random Access channel
Rank Indication
Sounding Reference Signal
Time Division Duplexing
Transmitted Precoding Matrix Indicator
Transmitted Rank IndicationUCI Uplink Control Information
Uplink Shared channel
4
Mapping to physical channels
4.1
Uplink
Table 4.1-1 specifies the mapping of the uplink transport channels to their corresponding physical channels. Table 4.1-2
specifies the mapping of the uplink control channel information to its corresponding physical channel.
Table 4.1-1
TrCH
UL-SCH
RACH
Physical Channel
PUSCH
PRACH
Table 4.1-2
Control information
UCI
4.2
Physical Channel
PUCCH, PUSCH
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.
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
8
ETSI TS 136 212 V8.4.0 (2008-11)
Table 4.2-1
TrCH
DL-SCH
BCH
PCH
MCH
Physical Channel
PDSCH
PBCH
PDSCH
PMCH
Table 4.2-2
Control information
CFI
HI
DCI
5
Physical Channel
PCFICH
PHICH
PDCCH
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 section 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 a 0 , a1 , a 2 , a 3 ,..., a A−1 , and the parity bits by p 0 , p1 , p 2 , p 3 ,..., p L −1 . 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:
a 0 D A+ 23 + a1 D A+ 22 + ... + a A−1 D 24 + p 0 D 23 + p1 D 22 + ... + p 22 D 1 + 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:
a 0 D A+15 + a1 D A+14 + ... + a A−1 D 16 + p 0 D15 + p1 D 14 + ... + p14 D 1 + p15
yields a remainder equal to 0 when divided by gCRC16(D), and the polynomial:
a0 D A + 7 + a1D A + 6 + ... + a A −1D 8 + p0 D7 + p1D 6 + ... + 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 ,..., b B −1 , where B = A+ L. The relation between ak and bk is:
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
bk = a k
for k = 0, 1, 2, …, A-1
bk = p k − A
for k = A, A+1, A+2,..., A+L-1.
5.1.2
9
ETSI TS 136 212 V8.4.0 (2008-11)
Code block segmentation and code block CRC attachment
The input bit sequence to the code block segmentation is denoted by b0 , b1 , b2 , b3 ,..., b B −1 , where B > 0. If B is larger
than the maximum code block size 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 (K r −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 +
Number of segments of size K − : C − = ⎢
⎣
− B′ ⎥
ΔK
Number of segments of size K + : C + = C − C − .
ETSI
⎥
⎦
.
3GPP TS 36.212 version 8.4.0 Release 8
10
ETSI TS 136 212 V8.4.0 (2008-11)
end if
Number of filler bits: F = C + ⋅ K + + C − ⋅ K − − B ′
for k = 0 to F-1
-- Insertion of filler bits
c 0 k =< 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 , c r 3 ,..., c r ( K r −L−1) is used to calculate the CRC parity bits p r 0 , p r1 , p r 2 ,..., p r (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 c 0 , c1 , c 2 , c 3 ,..., c K −1 , where K is the
number of bits to encode. After encoding the bits are denoted by d 0(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;
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
-
11
ETSI TS 136 212 V8.4.0 (2008-11)
turbo coding.
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
UL-SCH
DL-SCH
PCH
MCH
BCH
Coding scheme
Coding rate
Turbo coding
1/3
Tail biting
convolutional
coding
1/3
Table 5.1.3-2: Usage of channel coding scheme and coding rate for control information
Control Information
Coding scheme
Tail biting
convolutional
coding
Block code
Repetition code
Block code
Tail biting
convolutional
coding
DCI
CFI
HI
UCI
5.1.3.1
Coding rate
1/3
1/16
1/3
variable
1/3
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 ,..., s 5 , then the initial value of the shift register shall be set to
s i = c ( K −1−i )
ck
d k(0)
d k(1)
d k( 2)
Figure 5.1.3-1: Rate 1/3 tail biting convolutional encoder
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
12
ETSI TS 136 212 V8.4.0 (2008-11)
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
5.1.3.2.1
Turbo coding
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 0 ( D) ⎦
G(D) = ⎢1,
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 c 0 , c1 , c 2 , c 3 ,..., c K −1 , and the bits output from the first and second 8state 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 8state constituent encoder.
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
13
ETSI TS 136 212 V8.4.0 (2008-11)
xk
zk
ck
z ′k
ck′
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 c 0 , 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:
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
14
ETSI TS 136 212 V8.4.0 (2008-11)
c i′ = c Π (i ) , i=0, 1,…, (K-1)
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
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
Ki
40
48
56
64
72
80
88
96
104
112
120
128
136
144
152
160
168
176
184
192
200
208
216
224
232
240
248
256
264
272
280
288
296
304
312
320
328
336
344
352
360
368
376
384
392
400
408
f1
f2
3
7
19
7
7
11
5
11
7
41
103
15
9
17
9
21
101
21
57
23
13
27
11
27
85
29
33
15
17
33
103
19
19
37
19
21
21
115
193
21
133
81
45
23
243
151
155
10
12
42
16
18
20
22
24
26
84
90
32
34
108
38
120
84
44
46
48
50
52
36
56
58
60
62
32
198
68
210
36
74
76
78
120
82
84
86
44
90
46
94
48
98
40
102
i
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
Ki
416
424
432
440
448
456
464
472
480
488
496
504
512
528
544
560
576
592
608
624
640
656
672
688
704
720
736
752
768
784
800
816
832
848
864
880
896
912
928
944
960
976
992
1008
1024
1056
1088
f1
f2
25
51
47
91
29
29
247
29
89
91
157
55
31
17
35
227
65
19
37
41
39
185
43
21
155
79
139
23
217
25
17
127
25
239
17
137
215
29
15
147
29
59
65
55
31
17
171
52
106
72
110
168
114
58
118
180
122
62
84
64
66
68
420
96
74
76
234
80
82
252
86
44
120
92
94
48
98
80
102
52
106
48
110
112
114
58
118
60
122
124
84
64
66
204
i
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
ETSI
Ki
1120
1152
1184
1216
1248
1280
1312
1344
1376
1408
1440
1472
1504
1536
1568
1600
1632
1664
1696
1728
1760
1792
1824
1856
1888
1920
1952
1984
2016
2048
2112
2176
2240
2304
2368
2432
2496
2560
2624
2688
2752
2816
2880
2944
3008
3072
3136
f1
f2
67
35
19
39
19
199
21
211
21
43
149
45
49
71
13
17
25
183
55
127
27
29
29
57
45
31
59
185
113
31
17
171
209
253
367
265
181
39
27
127
143
43
29
45
157
47
13
140
72
74
76
78
240
82
252
86
88
60
92
846
48
28
80
102
104
954
96
110
112
114
116
354
120
610
124
420
64
66
136
420
216
444
456
468
80
164
504
172
88
300
92
188
96
28
i
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
Ki
3200
3264
3328
3392
3456
3520
3584
3648
3712
3776
3840
3904
3968
4032
4096
4160
4224
4288
4352
4416
4480
4544
4608
4672
4736
4800
4864
4928
4992
5056
5120
5184
5248
5312
5376
5440
5504
5568
5632
5696
5760
5824
5888
5952
6016
6080
6144
f1
f2
111
443
51
51
451
257
57
313
271
179
331
363
375
127
31
33
43
33
477
35
233
357
337
37
71
71
37
39
127
39
39
31
113
41
251
43
21
43
45
45
161
89
323
47
23
47
263
240
204
104
212
192
220
336
228
232
236
120
244
248
168
64
130
264
134
408
138
280
142
480
146
444
120
152
462
234
158
80
96
902
166
336
170
86
174
176
178
120
182
184
186
94
190
480
3GPP TS 36.212 version 8.4.0 Release 8
5.1.4
5.1.4.1
15
ETSI TS 136 212 V8.4.0 (2008-11)
Rate matching
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)
vk( 0)
d k(1)
vk(1)
d k( 2)
vk( 2)
ek
wk
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.
Π
The bit stream d k(1) is interleaved according to the sub-block interleaver defined in subclause 5.1.4.1.1 with an output
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
= 32 to be the number of columns of the matrix. The columns of the matrix are numbered 0, 1,
(1) Assign C subblock
TC
− 1 from left to right.
2,…, C subblock
TC
TC
(2) Determine the number of rows of the matrix Rsubblock
, by finding minimum integer R subblock such that:
(
TC
TC
D ≤ Rsubblock
× C subblock
)
TC
− 1 from top to bottom.
The rows of rectangular matrix are numbered 0, 1, 2,…, Rsubblock
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
(
16
)
ETSI TS 136 212 V8.4.0 (2008-11)
(
)
TC
TC
TC
TC
(3) If Rsubblock
× C subblock
> D , then N D = Rsubblock
× C subblock
− D dummy bits are padded such that yk = <NULL>
for k = 0, 1,…, ND - 1. Then, write the input bit sequence, i.e. y N D + k = d k(i ) , k = 0, 1,…, D-1, into
(
)
TC
TC
× C subblock
matrix row by row starting with bit y0 in column 0 of row 0:
the Rsubblock
y0
⎡
⎢
yCTC
⎢
subblock
⎢
⎢
⎢ y ( RTC
TC
subblock −1)×Csubblock
⎣
y1
yCTC
M
yCTC
M
subblock +1
y( RTC
L
L
O
L
y2
M
subblock + 2
TC
subblock −1)×Csubblock +1
y ( RTC
TC
subblock −1)×Csubblock + 2
yCTC
⎤
⎥
y 2CTC
⎥
subblock −1
⎥
⎥
y( RTC ×CTC
⎥
subblock
subblock −1) ⎦
subblock −1
M
For d k( 0) and d k(1) :
(4) Perform the inter-column permutation for the matrix based on the pattern P( j )
{
} that is shown in
TC
j∈ 0,1,...,Csubblock
−1
table 5.1.4-1, where P(j) is the original column position of the j-th permuted column. After permutation of the
TC
TC
columns, the inter-column permuted Rsubblock
× C subblock
matrix is equal to
(
y P ( 0)
⎡
⎢
y P ( 0)+CTC
⎢
subblock
⎢
⎢
⎢ y P ( 0)+( RTC
TC
subblock −1)×Csubblock
⎣
M
)
y P (1)
y P ( 2)
y P (1)+CTC
y P ( 2)+CTC
M
M
subblock
y P (1)+( RTC
TC
subblock −1)×Csubblock
L
L
O
L
subblock
y P ( 2)+( RTC
TC
subblock −1)×Csubblock
y P (CTC
subblock −1)
y P (CTC
M
TC
subblock −1)+Csubblock
y P (CTC
TC
TC
subblock −1) +( Rsubblock −1)×Csubblock
(5) The output of the block interleaver is the bit sequence read out column by column from the inter-column
TC
TC
permuted Rsubblock
× C subblock
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) +CTC
…
subblock
)
TC
TC
and K Π = Rsubblock
× C subblock
.
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
Π
⎛
⎛⎢
⎥⎞
TC
⎟
⎥ + C subblock
⎜ ⎢ R TC
⎟
⎥⎠
⎝ ⎣ subblock ⎦
π (k )= ⎜ P⎜ ⎢
⎜
⎝
k
(
)
⎞
TC
× k mod Rsubblock
+ 1⎟ mod K Π
⎟
⎠
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
5.1.4.1.2
Number of columns
Inter-column permutation pattern
TC
C subblock
TC
< P(0), P(1),..., P(C subblock
− 1) >
32
< 0, 16, 8, 24, 4, 20, 12, 28, 2, 18, 10, 26, 6, 22, 14, 30,
1, 17, 9, 25, 5, 21, 13, 29, 3, 19, 11, 27, 7, 23, 15, 31 >
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
w K Π + 2 k = v k(1)
for k = 0,…, K Π − 1
ETSI
⎤
⎥
⎥
⎥
⎥
⎥
⎦
3GPP TS 36.212 version 8.4.0 Release 8
17
ETSI TS 136 212 V8.4.0 (2008-11)
w K Π + 2 k +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 IR ⎥
⎞
⎟
⎥, K w ⎟
C
⎦
⎝⎣
⎠
- N cb = min ⎜⎜ ⎢
for downlink turbo coded transport channels
- N cb = K w
for uplink turbo coded transport channels
where NIR is equal to:
⎢
N IR = ⎢
⎢⎣ K MIMO
⋅ min
⎥
⎥
M DL_HARQ , M limit ⎥⎦
(
N soft
)
where:
Nsoft is the total number of soft channel bits [4].
KMIMO is equal to 2 if the UE is configured to receive PDSCH transmissions based on transmission modes 3 or 4 as
defined in Section 7.1 in [3], 1 otherwise.
MDL_HARQ is the maximum number of DL HARQ processes (8 for FDD; 4, 6, 7, 9, 10, 12 or 15 for TDD depending on
the UL/DL configuration defined in [2]).
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 and 6 for 64QAM, and where
-
NL is equal to 1 for transport blocks mapped onto one transmission layer, and
-
NL is equal to 2 for transport blocks mapped onto two or four transmission layers.
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 ⋅ Q m ⋅ ⎣G ′ / C ⎦
else
set E = N L ⋅ Q m ⋅ ⎡G ′ / C ⎤
end if
⎛
⎡
⎤
⎥ ⋅ rv idx
TC
⎢
⎢ 8 R subblock ⎥
⎥
TC
Set k 0 = R subblock
⋅⎜2⋅ ⎢
⎜
⎝
N cb
⎞
TC
+ 2 ⎟ , where R subblock
is the number of rows defined in subclause 5.1.4.1.1.
⎟
⎠
Set k = 0 and j = 0
while { k < E }
if w( k0 + j ) mod Ncb ≠< NULL >
ek = w( k0 + j ) mod N cb
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
18
ETSI TS 136 212 V8.4.0 (2008-11)
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)
vk( 0)
d k(1)
vk(1)
d k( 2)
vk( 2)
ek
wk
Figure 5.1.4-2. Rate matching for convolutionally coded transport channels and control information
The bit stream d k( 0) is interleaved according to the sub-block interleaver defined in subclause 5.1.4.2.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.2.1.
Π
The bit stream d k(1) is interleaved according to the sub-block interleaver defined in subclause 5.1.4.2.1 with an output
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.
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
, by finding minimum integer R subblock
such that:
(2) Determine the number of rows of the matrix R subblock
(
CC
CC
D ≤ R subblock
× C subblock
)
The rows of rectangular matrix are numbered 0, 1, 2,…, Rsubblock − 1 from top to bottom.
CC
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
(
19
)
ETSI TS 136 212 V8.4.0 (2008-11)
(
)
CC
CC
CC
CC
(3) If R subblock
× C subblock
> D , then N D = R subblock
× C subblock
− D dummy bits are padded such that yk = <NULL>
for k = 0, 1,…, ND - 1. Then, write the input bit sequence, i.e. y N D + k = d k(i ) , k = 0, 1,…, D-1, into
(
)
CC
CC
× Csubblock
matrix row by row starting with bit y0 in column 0 of row 0:
the Rsubblock
y0
⎡
⎢
yC CC
⎢
subblock
⎢
⎢
⎢ y CC
CC
⎣ ( R subblock −1)× C subblock
y1
yC CC
y2
yC CC
subblock +1
M
subblock + 2
M
y( R CC
M
y( R CC
CC
subblock −1) × C subblock +1
CC
subblock −1) × C subblock + 2
L
L
O
L
(4) Perform the inter-column permutation for the matrix based on the pattern P( j )
yC CC
⎤
⎥
y2C CC
⎥
1
−
subblock
⎥
⎥
⎥
y( R CC ×C CC
subblock
subblock −1) ⎦
subblock −1
M
{
} that is shown in
CC
j∈ 0,1,...,Csubblock
−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
CC
× Csubblock
matrix is equal to
columns, the inter-column permuted Rsubblock
(
y P ( 0)
⎡
⎢
y P ( 0)+C CC
⎢
subblock
⎢
⎢
⎢ y P ( 0)+ ( RCC
CC
subblock −1)×Csubblock
⎣
M
)
y P (1)
y P ( 2)
y P (1)+C CC
y P ( 2)+C CC
M
y P (1)+( RCC
M
subblock
CC
subblock −1)×Csubblock
subblock
y P ( 2)+( RCC
CC
subblock −1)×Csubblock
L
L
O
L
y P (C CC
subblock −1)
y P (C CC
M
CC
subblock −1) +Csubblock
y P ( C CC
CC
CC
subblock −1) + ( Rsubblock −1)×Csubblock
⎤
⎥
⎥
⎥
⎥
⎥
⎦
(5) The output of the block interleaver is the bit sequence read out column by column from the inter-column
(
)
CC
CC
permuted Rsubblock
× Csubblock
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) +C CC
subblock
(
CC
CC
… and K Π = Rsubblock
× C subblock
)
Π −1
Table 5.1.4-2 Inter-column permutation pattern for sub-block interleaver
Number of columns
Inter-column permutation pattern
CC
C subblock
CC
< P(0), P(1),..., P(C subblock
− 1) >
32
< 1, 17, 9, 25, 5, 21, 13, 29, 3, 19, 11, 27, 7, 23, 15, 31,
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:
wk = v k( 0)
for k = 0,…, K Π − 1
w K Π + 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 K w ≠< NULL >
ek = w j mod K w
ETSI
,
3GPP TS 36.212 version 8.4.0 Release 8
20
ETSI TS 136 212 V8.4.0 (2008-11)
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 and channel interleaving 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 and channel interleaving
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
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. Data arrives to the coding unit in form
of a maximum of one transport block every transmission time interval (TTI). The following coding steps can be
identified:
−
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
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
−
21
ETSI TS 136 212 V8.4.0 (2008-11)
Channel interleaver
The coding steps for UL-SCH transport channel are shown in the figure below.
[o0ACK o1ACK
Lo
ACK
O ACK −1
]
Figure 5.2.2-1: Transport channel processing for UL-SCH
5.2.2.1
Transport block CRC attachment
Error detection is provided on UL-SCH transport blocks through a Cyclic Redundancy Check (CRC).
The entire transport block is used to calculate the CRC parity bits. Denote the bits in a transport block delivered to layer
1 by a 0 , a1 , a 2 , a 3 ,..., a A−1 , and the parity bits by p 0 , p1 , p 2 , p 3 ,..., p L −1 . A is the size of the transport block and L is the
number of parity bits.
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).
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
5.2.2.2
22
ETSI TS 136 212 V8.4.0 (2008-11)
Code block segmentation and code block CRC attachment
The bits input to the code block segmentation are denoted by b0 , b1 , b2 , b3 ,..., b B −1 where B is the number of bits in the
transport block (including CRC).
Code block segmentation and code block CRC attachment are performed according to 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 (K r −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 (K r −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(3i ) ,..., 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(3i ) ,..., 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 f 0 , f1, f 2 , f3 ,..., fG −1 , where G is the total number of coded bits
for transmission excluding the bits used for control transmission, when control information is multiplexed with the ULSCH 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. 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 and channel quality information o0 , o1 , o 2 ,..., oO −1 is done independently.
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
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
⎛⎡
⎜⎢
PUSCH
⎜ ⎢ O ⋅ M scPUSCH ⋅ N symb
Q′ = min⎜
− ΔPUSCH
⎢
offset
C −1
⎜⎢
10
10
Kr
⋅
∑
⎜⎢
r =0
⎝⎢
23
ETSI TS 136 212 V8.4.0 (2008-11)
⎞
⎤
⎟
⎥
⎥, 4 ⋅ M PUSCH −current ⎟
⎟
sc
⎥
⎟
⎥
⎟
⎥⎥
⎠
PUSCH -current
where O is the number of ACK/NACK bits or rank indicator bits, 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
M scPUSCH , N symb
, C , and K r are obtained from the initial PDCCH for the same transport block.
For HARQ-ACK information
− ACK
− ACK
Q ACK = Qm ⋅ Q ′ and [ ΔPUSCH
= ΔHARQ
], where ΔHARQ
shall be determined
offset
offset
offset
according to [4]. .
For rank indication
RI
QRI = Qm ⋅ Q ′ and [ ΔPUSCH
= ΔRI
offset
offset ], where Δ offset shall be determined according to [4].
For HARQ-ACK information
−
Each positive acknowledgement (ACK) is encoded as a binary "1" and each negative acknowledgement
(NAK) is encoded as a binary "0"
−
If HARQ-ACK consists of 1-bit of information, i.e., [o 0ACK ] , it is first encoded according to Table 5.2.2.6-1.
−
If HARQ-ACK consists of 2-bits of information, i.e., [o0ACK o1ACK ] , 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
2
Encoded HARQ-ACK
4
[o0ACK y x x]
6
[o0ACK y x x x x ]
[o0ACK y]
Table 5.2.2.6-2: Encoding of 2-bit HARQ-ACK
Qm
2
Encoded HARQ-ACK
[o0ACK o1ACK o 2ACK o 0ACK o1ACK o 2ACK ]
4
[o0ACK o1ACK x x o 2ACK o0ACK x x o1ACK o2ACK x x]
6
[o 0ACK o1ACK x x x x o 2ACK o 0ACK x x x x o1ACK o 2ACK x x x x]
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 the case that HARQ-ACK consists of one or two bits information, the bit sequence q 0ACK , q1ACK , 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 .
ACK
For the case that HARQ-ACK consists of more than two bits information, i.e. [o0
O ACK > 2 , the bit sequence q 0ACK , q1ACK , q 2ACK ,..., q QACK
is obtained as
ACK −1
ETSI
o1ACK L oOACK
] with
ACK
−1
3GPP TS 36.212 version 8.4.0 Release 8
q
ACK
i
=
O ACK −1
∑ (o
n =0
ACK
n
24
ETSI TS 136 212 V8.4.0 (2008-11)
)
⋅ M (i mod 32 ),n mod 2
where i = 0, 1, 2, …, QACK-1 and the basis sequences Mi,n are defined in Table 5.2.2.6.4-1.
The vector sequence output of the channel coding for HARQ-ACK information is denoted by q ACK , q ACK ,..., q ACK
′
0
1
Q ACK −1
,
where Q ′ACK = Q ACK / Q m , and is obtained as follows:
Set i ,k to 0
while i < QACK
T
q ACK = [q iACK ...q iACK
+ Qm −1 ]
k
i = i + Qm
k = k +1
end while
For rank indication (RI)
−
If RI consists of 1-bit of information, i.e., [o0RI ] , it is first encoded according to Table 5.2.2.6-3.
−
If RI consists of 2-bits of information, i.e., [o0RI o1RI ] , it is first encoded according to Table 5.2.2.6-4 where
o 2RI = (o 0RI + o1RI ) mod 2 .
Table 5.2.2.6-3: Encoding of 1-bit RI
Qm
2
Encoded RI
4
[o0RI y x x]
6
[o0RI y x x x x ]
[o 0RI y]
Table 5.2.2.6-4: Encoding of 2-bit RI
Encoded RI
Qm
2
[o0RI o1RI o 2RI o0RI o1RI o 2RI ]
[o0RI o1RI x x o 2RI o0RI x x o1RI o 2RI x
[o0RI o1RI x x x x o 2RI o 0RI x x x x o1RI o 2RI
4
6
x]
x x x x]
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.
The bit sequence q 0RI , q1RI , q 2RI ,..., q QRI
RI −1
is 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 . The vector sequence output of the channel coding for rank
information is denoted by q RI , q RI ,..., q RI
0
1
′ −1
QRI
′ = QRI / Qm , and is obtained as follows:
, where QRI
Set i ,k to 0
while i < QRI
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
q RI = [q iRI ...q iRI
+Q
m −1
k
25
ETSI TS 136 212 V8.4.0 (2008-11)
]T
i = i + Qm
k = k +1
end while
For channel quality control information (CQI and/or PMI)
When the UE transmits channel quality control information bits, it shall determine the number of coded symbols Q′ for
channel quality information as
⎡
⎢
PUSCH
(O + L) ⋅ M scPUSCH ⋅ N symb
⎢
′
Q =⎢
− ΔPUSCH
offset
C −1
⎢
10 10 ⋅ ∑ K r
⎢⎢
r =0
⎤
⎥
⎥ where O is the number of CQI bits, L is the number of CRC bits given by
⎥
⎥
⎥⎥
O ≤ 11
⎧0
CQI
, and [ ΔPUSCH
= ΔCQI
L=⎨
offset
offset ], where Δ offset shall be determined according to [4]. .
8
otherwise
⎩
PUSCH
M scPUSCH , N symb
, C , and K r are obtained from the initial PDCCH for the same transport block.
−
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 o 0 , o1 , o 2 ,..., 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 is o 0 , o1 , o 2 ,..., 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 q0 , q1, q2 , q3 ,..., qQ −1 .
5.2.2.6.1
Channel quality information formats for wideband CQI reports
Table 5.2.2.6.1-1 shows the fields and the corresponding bit widths for the channel quality information feedback for
wideband reports for PDSCH transmissions over closed-loop spatial multiplexing. N in Table 5.2.2.6.1-1 is defined in
subclause 7.2 [3].
Table 5.2.2.6.1-1: Fields for channel quality information (CQI) feedback for wideband CQI reports
(closed loop spatial multiplexing PDSCH transmission)
Field
Wideband CQI codeword 0
Wideband CQI codeword 1
Precoding matrix indication
Bitwidth
2 antenna ports
4 antenna ports
Rank = 1 Rank = 2 Rank = 1 Rank > 1
4
4
4
4
0
4
0
4
2N
N
4N
4N
The channel quality bits in Table 5.2.2.6.1-1 form the bit sequence o 0 , o1 , o 2 ,..., 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
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
26
ETSI TS 136 212 V8.4.0 (2008-11)
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.
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 widths for the channel quality information feedback for
higher layer configured report for PDSCH transmissions over single antenna port, transmit diversity and open loop
spatial multiplexing. N in Table 5.2.2.6.2-1 is defined in subclause 7.2 [3].
Table 5.2.2.6.2-1: Fields for channel quality information (CQI) feedback for higher layer configured
subband CQI reports
(single antenna port, transmit diversity and open loop spatial multiplexing PDSCH transmission)
Field
Bitwidth
Wide-band CQI codeword
Subband differential CQI
2N
4
Table 5.2.2.6.2-2 shows the fields and the corresponding bit widths for the channel quality information feedback for
higher layer configured report for PDSCH transmissions over closed loop spatial multiplexing. N in Table 5.2.2.6.2-2
is defined in subclause 7.2 [3].
Table 5.2.2.6.2-2: Fields for channel quality information (CQI) feedback for higher layer configured
subband CQI reports
(closed loop spatial multiplexing PDSCH transmission)
Field
Wide-band CQI codeword 0
Subband differential CQI codeword 0
Wide-band CQI codeword 1
Subband differential CQI codeword 1
Precoding matrix indication
Bitwidth
2 antenna ports
4 antenna ports
Rank = 1 Rank = 2 Rank = 1 Rank > 1
4
4
4
4
2N
2N
2N
2N
0
0
2
4
0
0
4
2N
2N
1
4
4
The channel quality bits in Table 5.2.2.6.2-1 through Table 5.2.2.6.2-2 form the bit sequence o 0 , o1 , o 2 ,..., 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.
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 over single antenna port, transmit diversity and open loop spatial
multiplexing. L in Table 5.2.2.6.3-1 is defined in subclause 7.2 [3].
Table 5.2.2.6.3-1: Fields for channel quality information (CQI) feedback for UE selected subband CQI
reports
(single antenna port, transmit diversity and open loop spatial multiplexing PDSCH transmission)
Field
Bitwidth
Wide-band CQI codeword
Subband differential CQI
Position of the M selected subbands
4
2
L
Table 5.2.2.6.3-2 shows the fields and the corresponding bit widths for the channel quality information feedback for UE
selected subband CQI for PDSCH transmissions over closed loop spatial multiplexing. L in Table 5.2.2.6.3-2 is
defined in subclause 7.2 [3].
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
27
ETSI TS 136 212 V8.4.0 (2008-11)
Table 5.2.2.6.3-2: Fields for channel quality information (CQI) feedback for UE selected subband CQI
reports
(closed loop spatial multiplexing PDSCH transmission)
Field
Wide-band CQI codeword 0
Subband differential CQI codeword 0
Wide-band CQI codeword 1
Subband differential CQI codeword 1
Position of the M selected subbands
Precoding matrix indication
Bitwidth
2 antenna ports
4 antenna ports
Rank = 1 Rank = 2 Rank = 1 Rank > 1
4
4
4
4
2
2
2
2
0
4
0
4
0
2
0
2
L
L
L
L
4
2
8
8
The channel quality bits in Table 5.2.2.6.3-1 through Table 5.2.2.6.3-2 form the bit sequence o 0 , o1 , o 2 ,..., 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 be
in the increasing order of the subband index [3], wideband PMI followed by the PMI for the M selected subband. The
first bit of each field corresponds to MSB and the last bit LSB.
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 o 0 , o1 , o 2 , o3 ,..., oO −1 where O is the
number of 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.
The channel quality indication 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 Mi,n and defined in Table 5.2.2.6.4-1.
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
28
ETSI TS 136 212 V8.4.0 (2008-11)
Table 5.2.2.6.4-1: Basis sequences for (32, O) code
i
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Mi,0
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
Mi,1
1
1
0
0
1
1
0
0
1
0
0
1
0
1
0
1
1
0
1
0
0
1
0
1
1
1
0
1
0
0
1
0
Mi,2
0
1
0
1
1
0
1
0
0
1
1
1
0
0
0
0
1
0
0
0
1
0
0
1
1
0
1
1
1
1
1
0
Mi,3
0
0
1
1
1
0
0
1
1
1
0
0
1
1
0
0
0
1
1
0
0
1
0
0
1
0
1
1
0
1
1
0
Mi,4
0
0
0
0
0
1
1
1
1
1
0
0
0
0
1
1
1
1
1
0
0
0
1
1
1
0
0
0
1
1
1
0
Mi,5
0
0
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
1
1
0
0
0
0
0
1
1
1
1
1
1
0
Mi,6
0
0
1
0
0
1
1
0
0
1
1
1
0
0
0
1
1
0
1
1
1
0
0
0
1
1
0
0
1
1
1
0
Mi,7
0
0
0
0
1
1
0
1
1
0
1
0
1
1
1
1
0
0
1
0
0
0
1
0
1
1
0
1
0
1
1
0
Mi,8
0
0
1
1
0
1
1
1
0
0
0
1
1
0
0
0
0
1
0
0
0
0
1
1
1
0
1
1
1
1
1
0
Mi,9
0
1
1
0
0
0
1
0
1
1
1
0
1
1
0
1
1
0
0
0
0
1
0
1
1
0
1
1
0
0
1
0
Mi,10
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
0
0
0
0
1
1
1
1
0
1
0
0
0
0
1
0
The encoded CQI/PMI block is denoted by b0 , b1 , b2 , b3 ,..., b B −1 where B = 32 and
bi =
O −1
∑ (o n ⋅ M i,n ) mod 2
where i = 0, 1, 2, …, B-1.
n=0
The output bit sequence q0 , q1, q2 , q3 ,..., qQ −1 is obtained by circular repetition of the encoded CQI/PMI block as
follows
q i = b(i mod B ) where i = 0, 1, 2, …, Q-1.
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 ,..., qQ −1 and the coded bits of the UL-SCH denoted by f 0 , f 1 , 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 + Q ) and H ′ = H / Q m , and
where g , i = 0,..., H ′ − 1 are column vectors of length Q m . H is the total number of coded bits allocated for UL-SCH
i
data and CQI/PMI data.
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
29
ETSI TS 136 212 V8.4.0 (2008-11)
( (
)
)
PUSCH
UL
Denote the number of SC-FDMA symbols per subframe for PUSCH transmission by N symb
= 2 ⋅ N symb
− 1 − N SRS .
The control information and the data shall be multiplexed as follows:
Set i, j, k to 0
while j < Q -- first place the control information
g = [q j ... q j +Qm −1 ]T
k
j = j + Qm
k = k +1
end while
while i < G -- then place the data
g = [ f i ... f i + Qm −1 ]T
k
i = i + Qm
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 HARQACK information is present on both slots in the subframe and is mapped to resources around the uplink demodulation
reference signals.
The input to the channel interleaver are denoted by g , g , g ,..., g
0
q ACK , q ACK , q ACK ,..., q ACK
′
0
1
2
Q ACK −1
1
2
H ′−1
, q RI , q RI , q RI ,..., q RI′
0
1
Q RI −1
2
and
'
. The number of modulation symbols in the subframe is given by H " = H ′ + Q RI
.. The
output bit sequence from the channel interleaver is derived as follows:
PUSCH
(1) Assign C mux = N symb
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.
′ = Rmux / Qm .
(2) The number of rows of the matrix is Rmux = (H "⋅Q m ) / C mux and we define Rmux
The rows of the rectangular matrix are numbered 0, 1, 2,…, R mux − 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′
0
1
2
Q RI −1
is written onto
the columns indicated by Table 5.2.2.8-1, and by sets of Qm rows starting from the last row and moving upwards
according to the following pseudocode.
Set i, j to 0.
′ −1
Set r to R mux
′
while i < QRI
c RI = Column Set ( j )
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
y
30
ETSI TS 136 212 V8.4.0 (2008-11)
= q RI
r ×C mux + c RI
i
i = i +1
′ − 1 − ⎣i 4⎦
r = R mux
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, i.e., y = g for k = 0, 1,…, H ′ − 1 , into the (R mux × C mux ) matrix by sets of
k
k
Qm rows starting with the vector y in column 0 and rows 0 to (Q m − 1) and skipping the matrix entries that are
0
already occupied:
y
⎡
0
⎢
y
⎢
C mux
⎢
⎢
⎢y
′ −1)× C mux
⎣ ( Rmux
y
y
1
y
M
y
y
M
C mux +1
′ −1)× C mux +1
( Rmux
y
2
M
C mux + 2
′ −1)× C mux + 2
( Rmux
L
L
O
L
y
⎤
⎥
y
⎥
2 C mux −1
⎥
⎥
y ′
⎥
( Rmux × C mux −1) ⎦
C mux −1
M
(5) If HARQ-ACK information is transmitted in this subframe, the vector sequence q ACK , q ACK , q ACK ,..., q ACK
′
0
1
2
Q ACK −1
is written onto the columns indicated by Table 5.2.2.8-2, and by sets of Qm rows starting from the last row and
moving upwards according to the following pseudocode. Note that this operation overwrites some of the channel
interleaver entries obtained in step (4).
Set i, j to 0.
′ −1
Set r to R mux
while i < Q ′ACK
c ACK = ColumnSet ( j )
y
r ×C mux + c ACK
= q ACK
i
i = i +1
′ − 1 − ⎣i 4⎦
r = R mux
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 (R mux × C mux )
matrix. The bits after channel interleaving are denoted by
ETSI
h0 , h1 , h2 ,..., h H + QRI −1 .
3GPP TS 36.212 version 8.4.0 Release 8
31
ETSI TS 136 212 V8.4.0 (2008-11)
Table 5.2.2.8-1: Column set for Insertion of rank information
CP configuration
Normal
Extended
Column Set
{1, 4, 7, 10}
{0, 3, 5, 8}
Table 5.2.2.8-2: Column set for Insertion of HARQ-ACK information
CP configuration
Normal
Extended
5.2.3
Column Set
{2, 3, 8, 9}
{1, 2, 6, 7}
Uplink control information on PUCCH
Data arrives to the coding unit in form of indicators for measurement indication, scheduling request and HARQ
acknowledgement.
Three forms of channel coding are used, one for the channel quality information (CQI), another for HARQ-ACK
(acknowledgement) and scheduling request and another for combination of channel quality information (CQI) and
HARQ-ACK.
a0 , a1 ,..., a A−1
b0 , b1 ,..., b B −1
Figure 5.2.3-1: Processing for UCI
5.2.3.1
Channel coding for UCI HARQ-ACK
The HARQ acknowledgement bits are received from higher layers. Each positive acknowledgement (ACK) is encoded
as a binary "1" and each negative acknowledgement (NAK) is encoded as a binary "0". The HARQ-ACK bits are
processed according to [2].
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 bits input to the channel coding block are denoted by a 0 , a1 , a 2 , a 3 ,..., a A−1 where A is the number
of 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.
The channel quality indication 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 Mi,n and defined in Table 5.2.3.3-1.
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
32
ETSI TS 136 212 V8.4.0 (2008-11)
Table 5.2.3.3-1: Basis sequences for (20, A) code
i
0
Mi,0
1
Mi,1
1
Mi,2
0
Mi,3
0
Mi,4
0
Mi,5
0
Mi,6
0
Mi,7
0
Mi,8
0
Mi,9
0
Mi,10
1
Mi,11
1
Mi,12
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 ,..., b B −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
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 over a single antenna port, transmit diversity or with open loop spatial
multiplexing.
Table 5.2.3.3.1-1: UCI fields for channel quality information (CQI) feedback for wideband reports
(single antenna port, transmit diversity or open loop spatial multiplexing PDSCH transmission)
Field
Wide-band CQI
Bitwidth
4
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 with closed loop spatial multiplexing.
Table 5.2.3.3.1-2: UCI fields for channel quality and precoding information (CQI/PMI) feedback for
wideband reports (closed loop spatial multiplexing PDSCH transmission)
Field
Wide-band CQI
Spatial differential CQI
Precoding matrix indication
Bitwidths
2 antenna ports
4 antenna ports
Rank = 1 Rank = 2 Rank = 1 Rank > 1
4
4
4
4
0
3
0
3
2
1
4
4
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 for open and closed loop spatial multiplexing.
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
33
ETSI TS 136 212 V8.4.0 (2008-11)
Table 5.2.3.3.1-3: UCI fields for rank indication (RI) feedback for wideband reports
Field
2 antenna ports
Rank indication
1
Bitwidths
4 antenna ports
Max 2 layers Max 4 layers
1
2
The channel quality bits in Table 5.2.3.3.1-1 through Table 5.2.3.3.1-3 form the bit sequence a 0 , a1 , a 2 , a 3 ,..., 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.
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 over a single antenna port, transmit diversity or
with open loop spatial multiplexing.
Table 5.2.3.3.2-1: UCI fields for channel quality information (CQI) feedback for UE-selected sub-band
reports (single antenna port, transmit diversity or open loop spatial multiplexing PDSCH
transmission)
Field
Sub-band CQI
Sub-band label
Bitwidth
4
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 with closed loop spatial multiplexing.
Table 5.2.3.3.2-2: UCI fields for channel quality information (CQI) feedback for UE-selected sub-band
reports (closed loop spatial multiplexing PDSCH transmission)
Field
Sub-band CQI
Spatial differential CQI
Sub-band label
Bitwidths
2 antenna ports
4 antenna ports
Rank = 1 Rank = 2 Rank = 1 Rank > 1
4
4
4
4
0
3
0
3
1 or 2
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 with closed loop spatial
multiplexing.
Table 5.2.3.3.2-3: UCI fields for channel quality and precoding information (CQI/PMI) feedback for UEselected sub-band reports (closed loop spatial multiplexing PDSCH transmission)
Field
Wide-band CQI
Spatial differential CQI
Precoding matrix indication
Bitwidths
2 antenna ports
4 antenna ports
Rank = 1 Rank = 2 Rank = 1 Rank > 1
4
4
4
4
0
3
0
3
2
1
4
4
Table 5.2.3.3.2-4 shows the fields and the corresponding bit widths for the rank indication feedback for UE-selected
sub-band reports for PDSCH transmissions for open and closed loop spatial multiplexing.
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
34
ETSI TS 136 212 V8.4.0 (2008-11)
Table 5.2.3.3.2-4: UCI fields for rank indication (RI) feedback for UE-selected sub-band reports
Field
Rank indication
2 antenna ports
1
Bitwidths
4 antenna ports
Max 2 layers Max 4 layers
1
2
The channel quality bits in Table 5.2.3.3.2-1 through Table 5.2.3.3.2-4 form the bit sequence a 0 , a1 , a 2 , a 3 ,..., 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.
5.2.3.4
Channel coding for UCI channel quality information and HARQ-ACK
This section 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′ , a 2′ , a3′ ,..., a ′A′−1 and output bit sequence b0′ , b1′ , b2′ , b3′ ,..., b B′ ′−1 , where B ′ = 20 . The
HARQ acknowledgement bits are denoted by a0′′ in case one HARQ acknowledgement bit or a0′′ , a1′′ in case two HARQ
acknowledgement bits are reported per subframe. Each positive acknowledgement (ACK) is encoded as a binary "1"
and each negative acknowledgement (NAK) is encoded as a binary "0".
The output of this channel coding block for normal CP is denoted by b0 , b1 , b2 , b3 ,..., b B −1 , where
bi = bi′ , i = 0,..., B ′ − 1
In case one HARQ acknowledgement bit is reported per subframe:
bB′ = a0′′ and B = (B ′ + 1)
In case two HARQ acknowledgement 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
acknowledgement bits are jointly coded. The HARQ acknowledgement bits are denoted by a0′′ in case one HARQ
acknowledgement bit or [a 0′′ , a1′′] in case two HARQ acknowledgement bits are reported per subframe.
The channel quality information denoted by a0′ , a1′ , a 2′ , a3′ ,..., a ′A′−1 is multiplexed with the HARQ acknowledgement bits
to yield the sequence a 0 , a1 , a 2 , a 3 ,..., a A−1 as follows
a i = a i′ , i = 0,..., A′ − 1
and
a A′ = a 0′′ and A = ( A′ + 1) in case one HARQ-acknowledgement bit is reported per subframe, or
a A′ = a 0′′ , a( A′+1) = a1′′ and A = ( A′ + 2) in case two HARQ-acknowledgement bits are reported per subframe.
The sequence a 0 , a1 , a 2 , a 3 ,..., a A−1 is encoded according to section 5.2.3.3 to yield the output bit sequence
b0 , b1 , b2 , b3 ,..., b B −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:
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
35
−
Channel coding of control information
−
Control information mapping
−
Channel interleaver
5.2.4.1
ETSI TS 136 212 V8.4.0 (2008-11)
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 PUSCH ⋅ N PUSCH
sc
symb
Q′ = min⎜ ⎢
PUSCH
−
Δ
offset
⎜⎢
10
⎜
⋅ OCQI
10
⎝⎢
⎞
⎤
⎟
⎥
PUSCH ⎟
⎥ , 4 ⋅ M sc
⎟
⎥
⎟
⎥
⎠
where O is the number of ACK/NACK bits or rank indicator bits, OCQI is the number of CQI bits including CRC bits,
M scPUSCH is the scheduled bandwidth for PUSCH transmission in the current subframe expressed as a number of
subcarriers in [2].
HARQ − ACK
PUSCH
HARQ − ACK
Q ACK = Qm ⋅ Q ′ and [ Δ offset
= Δ offset
− ΔCQI
shall be
offset ], where Δ offset
For HARQ-ACK information
determined according to [4].
For rank indication
PUSCH
RI
RI
QRI = Qm ⋅ Q ′ and [ Δ offset
= Δ offset
− Δ CQI
offset ], where Δ offset shall be determined according to [4].
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 ,..., qQ −1 , the coded vector sequence output for
HARQ-ACK is denoted by q ACK , q ACK , q ACK ,..., q ACK
′
0
RI
RI
RI
RI
denoted by q 0 , q 1 , q 2 ,..., q Q ′
RI
5.2.4.2
1
−1
2
Q ACK −1
and the coded vector sequence output for rank indication is
.
Control information mapping
The input are the coded bits of the channel quality information denoted by q0 , q1, q2 , q3 ,..., qQ −1 . The output is denoted
by g , g , g , g ,..., g
0
1
2
3
H ′ −1
, where H = Q and H ′ = H / Q m , and where g , i = 0,..., H ′ − 1 are column vectors of
i
length Q m .
( (
)
)
PUSCH
UL
Denote the number of SC-FDMA symbols per subframe for PUSCH transmission by N symb
= 2 ⋅ N symb
− 1 − N SRS .
The control information shall be mapped as follows:
Set j, k to 0
while j < Q
g = [q j ... q j +Qm −1 ]T
k
j = j + Qm
k = k +1
end while
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
5.2.4.3
36
ETSI TS 136 212 V8.4.0 (2008-11)
Channel interleaver
The vector sequences g , g , g ,..., g
0
1
2
H ′−1
, q RI , q RI , q RI ,..., q RI′
0
1
Q RI −1
2
and q ACK , q ACK , q ACK ,..., q ACK
′
0
1
2
Q ACK −1
are channel
interleaved according subclause 5.2.2.8. The bits after channel interleaving are denoted by h0 , h1 , h2 ,..., hH +Q
5.3
Downlink transport channels and control information
5.3.1
Broadcast channel
RI
−1
.
Figure 5.3.1-1 shows the processing structure for the BCH transport channel. Data arrives to the coding unit in form of a
maximum of one transport block every transmission time interval (TTI) of 40ms. The following coding steps can be
identified:
−
Add CRC to the transport block
−
Channel coding
−
Rate matching
The coding steps for BCH transport channel 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
r
Rate matching
e0 , e1 ,..., e E −1
Figure 5.3.1-1: Transport channel processing for BCH
5.3.1.1
Transport block CRC attachment
Error detection is provided on BCH transport blocks through a Cyclic Redundancy Check (CRC).
The entire transport block is used to calculate the CRC parity bits. Denote the bits in a transport block delivered to layer
1 by a 0 , a1 , a 2 , a 3 ,..., a A−1 , and the parity bits by p 0 , p1 , p 2 , p 3 ,..., p L −1 . A is the size of the transport block and L is the
number of parity bits.
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 eNode-B transmit antenna configuration with the
sequence x ant ,0 , x ant ,1 ,..., x ant ,15 as indicated in Table 5.3.1.1-1 to form the sequence of bits c 0 , c1 , c 2 , c3 ,..., c K −1 where
ck = ak
for k = 0, 1, 2, …, A-1
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
c k = ( p k − A + x ant ,k − A ) mod 2
37
ETSI TS 136 212 V8.4.0 (2008-11)
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 eNode-B
PBCH CRC mask
< x ant ,0 , x ant ,1 ,..., x ant ,15 >
1
2
4
5.3.1.2
<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>
<0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1>
Channel coding
Information bits are delivered to the channel coding block. They are denoted by c0 , c1 , c2 , c3 ,..., c K −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 .
5.3.1.3
Rate matching
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 ,..., e E −1 , where E is the number of rate matched bits.
5.3.2
Downlink shared channel, Paging channel and Multicast channel
Figure 5.3.2-1 shows the processing structure for the DL-SCH, PCH and MCH transport channels. Data arrives to the
coding unit in form of a maximum of one transport block every transmission time interval (TTI). The following coding
steps can be identified:
−
Add CRC to the transport block
−
Code block segmentation and code block CRC attachment
−
Channel coding
−
Rate matching
−
Code block concatenation
The coding steps for DL-SCH, PCH and MCH transport channels are shown in the figure below.
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
38
ETSI TS 136 212 V8.4.0 (2008-11)
a0 , a1 ,..., a A −1
Transport block
CRC attachment
b0 , b1 ,..., b B −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 channel processing for DL-SCH, PCH and MCH
5.3.2.1
Transport block CRC attachment
Error detection is provided on transport blocks through a Cyclic Redundancy Check (CRC).
The entire transport block is used to calculate the CRC parity bits. Denote the bits in a transport block delivered to layer
1 by a 0 , a1 , a 2 , a 3 ,..., a A−1 , and the parity bits by p 0 , p1 , p 2 , p 3 ,..., p L −1 . A is the size of the transport block and L is the
number of parity bits.
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 ,..., b B −1 where B is the number of bits in the
transport block (including CRC).
Code block segmentation and code block CRC attachment are performed according to 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 (K r −1) , where r is the code block number
and Kr is the number of bits for code block number r.
5.3.2.3
Channel coding
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 (K r −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.
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
39
ETSI TS 136 212 V8.4.0 (2008-11)
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.3.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.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.2.
The bits after code block concatenation are denoted by f 0 , f1, f 2 , f3 ,..., fG −1 , where G is the total number of coded bits
for transmission.
5.3.3
Downlink control information
A DCI transports downlink or uplink scheduling information, or uplink power control commands for one RNTI. The
RNTI is implicitly encoded in the CRC.
Figure 5.3.3-1 shows the processing structure for the 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.
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
40
ETSI TS 136 212 V8.4.0 (2008-11)
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 DCI
5.3.3.1
DCI formats
The ordering of the information bits in the payload description below starts with a 0 and ends with a A−1 .
The information fields are multiplexed according to the order they are listed in each DCI format. The first bit of each
information field corresponds to MSB.
5.3.3.1.1
Format 0
DCI format 0 is used for the scheduling of PUSCH.
The following information is transmitted by means of the DCI format 0:
- Flag for format0/format1A differentiation – 1 bit, where value 0 indicates format 0 and value 1 indicates format 1A
- Hopping flag – 1 bit as defined in section 8.4 of [3]
⎡
UL
UL
- Resource block assignment and hopping resource allocation – log 2 ( N RB
( N RB
+ 1) / 2)
⎤
bits
- For PUSCH hopping:
- NUL_hop MSB bits are used to obtain the value of n~PRB (i ) as indicated in subclause [8.4] of [3]
-
⎛
⎜
⎝
UL
UL
( N RB
+ 1) / 2)⎤
⎡log 2 ( N RB
− N UL_hop ⎞⎟ bits provide the resource allocation of the first slot in the UL
⎠
subframe
- For non-hopping PUSCH:
-
⎛
⎜
⎝
UL
UL
( N RB
+ 1) / 2) ⎤ ⎞⎟ bits provide the resource allocation in the UL subframe as defined in section
⎡log 2 ( N RB
⎠
8.1 of [3]
- Modulation and coding scheme and redundancy version – 5 bits as defined in section 8.6 of [3]
- New data indicator – 1 bit
- TPC command for scheduled PUSCH – 2 bits as defined in section 5.1.1.1 of [3]
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
41
ETSI TS 136 212 V8.4.0 (2008-11)
- Cyclic shift for DM RS – 3 bits as defined in section 5.5.2.1.1 of [2]
- UL index – 2 bits as defined in sections 5.1.1.1 and 8 of [3] (this field just applies to TDD operation and is not
present in FDD)
- CQI request – 1 bit as defined in section 7.2.1 of [3]
If the number of information bits in format 0 is less than for format 1A, zeros shall be appended to format 0 until the
payload size equals that of format 1A.
5.3.3.1.2
Format 1
DCI format 1 is used for the scheduling of one PDSCH codeword.
The following information is transmitted by means of the DCI format 1:
- Resource allocation header (resource allocation type 0 / type 1) – 1 bit as defined in section 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 section 7.1.6.1 of [3]:
⎡
⎤
DL
- N RB
/ P bits provide the resource allocation
- For resource allocation type 1 as defined in section 7.1.6.2 of [3]:
- ⎡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.1] of [3]
- Modulation and coding scheme – 5 bits as defined in section 7.1.7 of [3]
- HARQ process number – 3 bits (FDD), 4 bits (TDD)
- New data indicator – 1 bit
- Redundancy version – 2 bits
- TPC command for PUCCH – 2 bits as defined in section 5.1.2.1 of [3]
- Downlink Assignment Index (this field just applies to TDD operation) – 2 bits
If 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 number of information bits in format 1 belongs to one of the sizes in Table 5.3.3.1.2-1, one zero bit shall be
appended to format 1.
Table 5.3.3.1.2-1: Ambiguous Sizes of Information Bits
{12, 14, 16 ,20, 24, 26, 32, 40, 44, 56}
5.3.3.1.3
Format 1A
DCI format 1A is used for the compact scheduling of one PDSCH codeword.
The following information is transmitted by means of the DCI format 1A:
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
42
ETSI TS 136 212 V8.4.0 (2008-11)
- Flag for format0/format1A differentiation – 1 bit, where value 0 indicates format 0 and value 1 indicates format 1A
- If the DCI 1A CRC is scrambled by RA-RNTI, P-RNTI, or SI-RNTI:
1A
- The flag for format0/format1A differentiation bit indicates column N PRB
of the TBS table defined in [3].
1A
1A
- If flag for format0/format1A differentiation bit is 0 then N PRB
= [ 2 ] else N PRB
= [ 3 ].
- Else
- The flag for format0/format1A differentiation bit indicates the DCI format
- Endif
- Localized/Distributed VRB assignment flag – 1 bit as defined in 7.1.6.3 of [3]
⎡
⎤
DL
DL
- Resource block assignment – log 2 ( N RB
( N RB
+ 1) / 2) bits as defined in section 7.1.6.3 of [3]:
- For localized VRB:
⎡log 2 ( N RBDL ( N RBDL + 1) / 2)⎤ bits provide the resource allocation
- For distributed VRB:
DL
- For N RB
< 50 or if the DCI 1A CRC is scrambled by RA-RNTI, P-RNTI, or SI-RNTI
⎡
⎤
DL
DL
- log 2 ( N RB
( N RB
+ 1) / 2) bits provide the resource allocation
DL
- For N RB
≥ 50
- 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
DL
- ( log 2 ( N RB
( N RB
+ 1) / 2)
⎤
− 1) bits provide the resource allocation
- Modulation and coding scheme – 5bits as defined in section 7.1.7 of [3]
- HARQ process number – 3 bits (FDD) , 4 bits (TDD)
- New data indicator – 1 bit
- If the DCI 1A CRC is scrambled by RA-RNTI, P-RNTI, or SI-RNTI:
- 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 indicates new data
- Endif
- Redundancy version – 2 bits
- TPC command for PUCCH – 2 bits as defined in section 5.1.2.1 of [3]
- Downlink Assignment Index (this field just applies to TDD operation and is not present in FDD) – 2 bits
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
43
ETSI TS 136 212 V8.4.0 (2008-11)
If the number of information bits in format 1A is less than for format 0, zeros shall be appended to format 1A until the
payload size equals that of format 0.
If the number of information bits in format 1A 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, or SI-RNTI then the following fields among the
fields above are reserved:
- HARQ process number
- TPC command for PUCCH
- Downlink Assignment Index (used for TDD only)
5.3.3.1.3A
Format 1B
DCI format 1B is used for the compact scheduling of one PDSCH codeword with precoding information.
The following information is transmitted by means of the DCI format 1B:
- Localized/Distributed VRB assignment flag – 1 bit
⎡
⎤
DL
DL
- Resource block assignment – log 2 ( N RB
( N RB
+ 1) / 2) bits
- For localized VRB:
⎡log 2 ( N RBDL ( N RBDL + 1) / 2)⎤ bits provide the resource allocation
- For distributed VRB:
DL
- For N RB
< 50
⎡
⎤
DL
DL
- log 2 ( N RB
( N RB
+ 1) / 2) bits provide the resource allocation
DL
- For N RB
≥ 50
- 1 bit indicates if N gap = N gap,1 or N gap = N gap,2
⎡
DL
DL
- ( log 2 ( N RB
( N RB
+ 1) / 2)
⎤
− 1) bits provide the resource allocation
- Modulation and coding scheme – 5bits
- HARQ process number – 3 bits (FDD) , 4 bits (TDD)
- New data indicator – 1 bit
- Redundancy version – 2 bits
- TPC command for PUCCH – 2 bits
- Downlink Assignment Index (this field just applies to TDD operation) – 2 bits
- 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
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
44
ETSI TS 136 212 V8.4.0 (2008-11)
Table 5.3.3.1.3A-1: Number of bits for TPMI information
Number of antenna ports
at eNode-B
2
4
Number
of bits
2
4
Table 5.3.3.1.3A-2: Content of PMI confirmation
Bit field mapped
to index
0
Message
Precoding according to the indicated TPMI in
the TPMI information field
Precoding according to the latest PMI report on
PUSCH using the precoder(s) indicated by the
reported PMI(s)
1
5.3.3.1.4
Format 1C
DCI format 1C is used for very compact scheduling of one PDSCH codeword.
The following information is transmitted by means of the DCI format 1C:
- 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 –
DL
step
DL
step
⎡log 2 (⎣( N VRB,
gap1 / N RB ⎦ ⋅ ( ⎣N VRB, gap1 / N RB ⎦ + 1) / 2 )⎤ bits
- Transport block size index – 5 bits
Here, N gap and
5.3.3.1.4A
DL
step
N VRB,
gap1 are defined in [2] and N RB is defined in [3].
Format 1D
DCI format 1D is used for the compact scheduling of one PDSCH codeword 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
⎡
⎤
DL
DL
- Resource block assignment – log 2 ( N RB
( N RB
+ 1) / 2) bits
- For localized VRB:
⎡log 2 ( N RBDL ( N RBDL + 1) / 2)⎤ bits provide the resource allocation
- For distributed VRB:
DL
- For N RB
< 50
⎡
⎤
DL
DL
- log 2 ( N RB
( N RB
+ 1) / 2) bits provide the resource allocation
DL
- For N RB
≥ 50
- 1 bit indicates if N gap = N gap,1 or N gap = N gap,2
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
⎡
DL
DL
- ( log 2 ( N RB
( N RB
+ 1) / 2)
45
⎤
ETSI TS 136 212 V8.4.0 (2008-11)
− 1) bits provide the resource allocation
- Modulation and coding scheme – 5bits
- HARQ process number – 3 bits (FDD) , 4 bits (TDD)
- New data indicator – 1 bit
- Redundancy version – 2 bits
- TPC command for PUCCH – 2 bits
- Downlink Assignment Index (this field just applies to TDD operation) – 2 bits
- 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
Table 5.3.3.1.4A-1: Number of bits for TPMI information
Number of antenna ports
at eNode-B
2
4
5.3.3.1.5
Number
of bits
2
4
Format 2
DCI format 2 is used for scheduling PDSCH to UEs configured in closed-loop spatial multiplexing mode.
The following information is transmitted by means of the DCI format 2:
In general:
- Resource allocation header (resource allocation type 0 / type 1) – 1 bit as defined in section 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 defined in section 7.1.6.1 of [3]:
⎡
⎤
DL
- N RB
/ P bits provide the resource allocation
- For resource allocation type 1 as defined in section 7.1.6.2 of [3]:
- ⎡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]
- TPC command for PUCCH – 2 bits as defined in section 5.1.2.1 of [3]
- Downlink Assignment Index (this field just applies to TDD operation and is not present in FDD) – 2 bits
- HARQ process number - 3 bits (FDD), 4 bits (TDD)
- Transport block to codeword swap flag – 1 bit
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
46
ETSI TS 136 212 V8.4.0 (2008-11)
For transport block 1:
- Modulation and coding scheme – 5 bits as defined in section 7.1.7 of [3]
- New data indicator – 1 bit
- Redundancy version – 2 bits
For transport block 2:
- Modulation and coding scheme – 5 bits as defined in section 7.1.7 of [3]
- New data indicator – 1 bit
- Redundancy version – 2 bits
Precoding information – number of bits as specified in Table 5.3.3.1.5-3
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.
Table 5.3.3.1.5-1: Transport block to codeword mapping
(two transport blocks enabled)
transport block
to codeword
swap flag value
codeword 1
(enabled)
codeword 2
(enabled)
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 1
transport block 1
codeword 2
transport block 2
(enabled)
(disabled)
enabled
disabled
transport block 1
-
disabled
enabled
transport 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]. The combination of a single enabled codeword and TRI=2 in Table 5.3.3.1.5-5 is only supported for
retransmission of the corresponding HARQ process.
If the number of information bits in format 2 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-2 and Table 5.3.3.1.5-3 are used for indicating that the eNode-B 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) reported by the UE on PUSCH, not coming from PUCCH, on or before subframe n-4.
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
47
ETSI TS 136 212 V8.4.0 (2008-11)
Table 5.3.3.1.5-3: Number of bits for precoding information
Number of antenna ports at eNode-B
Number of bits for precoding information
2
4
3
6
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
48
ETSI TS 136 212 V8.4.0 (2008-11)
Table 5.3.3.1.5-4: Content of precoding information field for 2 antenna ports
One codeword:
Codeword 1 enabled,
Two codewords:
Codeword 1 enabled,
Codeword 2 disabled
Bit field
mapped to
index
0
Codeword 2 enabled
Message
TRI=1: transmit diversity
Bit field
mapped
to index
0
Message
TRI=2: Precoding
corresponding to
precoder matrix
1 ⎡1 1 ⎤
2 ⎢⎣1 − 1⎥⎦
1
TRI=1: Precoding
corresponding to
precoding vector
[1 1]T /
2
3
4
5
6
7
TRI=2: Precoding
according to the latest
PMI report on
PUSCH, using the
precoder(s) indicated
by the reported
PMI(s)
3
reserved
4
reserved
5
reserved
6
reserved
7
reserved
T
j] / 2
T
TRI=1: Precoding
corresponding to
precoder vector
[1
2
− 1] / 2
TRI=1: Precoding
corresponding to
precoder vector
[1
TRI=2: Precoding
corresponding to
precoder matrix
1 ⎡1 1 ⎤
2 ⎢⎣ j − j ⎥⎦
2
TRI=1: Precoding
corresponding to
precoder vector
[1
1
− j] / 2
T
TRI=1:
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 of all
precoders implied by the
reported PMI(s)
TRI=1:
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 of all
precoders implied by the
reported PMI(s)
reserved
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
49
ETSI TS 136 212 V8.4.0 (2008-11)
Table 5.3.3.1.5-5: Content of precoding information field for 4 antenna ports
One codeword:
Codeword 1 enabled,
Two codewords:
Codeword 1 enabled,
Codeword 2 disabled
Codeword 2 enabled
Bit field
mapped to
index
0
1
2
TRI=1: transmit diversity
TRI=1: TPMI=0
TRI=1: TPMI=1
M
Message
Bit field
mapped
to index
0
1
TRI=2: TPMI=0
TRI=2: TPMI=1
M
M
M
15
TRI=2: TPMI=15
16
TRI=1: TPMI=15
16
17
17
18
19
TRI=1: Precoding
according to the latest
PMI report on PUSCH
using the precoder(s)
indicated by the reported
PMI(s)
TRI=2: TPMI=0
TRI=2: TPMI=1
TRI=2: Precoding
according to the latest
PMI report on PUSCH
using the precoder(s)
indicated by the reported
PMI(s)
TRI=3: TPMI=0
18
TRI=3: TPMI=1
M
M
TRI=3: TPMI=15
M
M
32
33
TRI=2: TPMI=15
33
34
TRI=2: Precoding
according to the latest
PMI report on PUSCH
using the precoder(s)
indicated by the reported
PMI(s)
reserved
34
TRI=3: Precoding
according to the latest
PMI report on PUSCH
using the precoder(s)
indicated by the reported
PMI(s)
TRI=4: TPMI=0
35
TRI=4: TPMI=1
M
M
49
50
TRI=4: TPMI=15
TRI=4: Precoding
according to the latest
PMI report on PUSCH
using the precoder(s)
indicated by the reported
PMI(s)
Reserved
35 – 63
51 – 63
5.3.3.1.5A
Message
Format 2A
DCI format 2A is used for scheduling PDSCH to UEs configured in open-loop spatial multiplexing mode.
The following information is transmitted by means of the DCI format 2A:
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
50
ETSI TS 136 212 V8.4.0 (2008-11)
In general:
- Resource allocation header (resource allocation type 0 / type 1) – 1 bit
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 [3],
⎡
⎤
DL
- N RB
/ P bits provide the resource allocation
- For resource allocation type 1 [3],
- ⎡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.1] of [3]
- TPC command for PUCCH – 2 bits
- Downlink Assignment Index (this field just applies to TDD operation) – 2 bits
- HARQ process number - 3 bits (FDD), 4 bits (TDD)
- Transport block to codeword swap flag – 1 bit
For transport block 1:
- Modulation and coding scheme – 5 bits
- New data indicator – 1 bit
- Redundancy version – 2 bits
For transport block 2:
- Modulation and coding scheme – 5 bits
- New data indicator – 1 bit
- Redundancy version – 2 bits
Precoding information – number of bits as specified in Table 5.3.3.1.5A-1
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. The combination of a single enabled
codeword and RI=2 in Table 5.3.3.1.5A-2 is only supported for retransmission of the corresponding HARQ process.
For transmission with 2 antenna ports, the precoding information field is not present. The number of transmission
layers, RI, is equal to 2 if both codewords are enabled; and is equal to 1 if codeword 1 is enabled while codeword 2 is
disabled.
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
51
ETSI TS 136 212 V8.4.0 (2008-11)
Table 5.3.3.1.5A-1: Number of bits for precoding information
Number of antenna ports at eNode-B
Number of bits for precoding information
2
4
0
2
Table 5.3.3.1.5A-2: Content of precoding information field for 4 antenna ports
One codeword:
Two codewords:
Codeword 1 enabled,
Codeword 1 enabled,
Codeword 2 disabled
Bit field
mapped to
index
0
1
5.3.3.1.6
Codeword 2 enabled
Message
RI=1: transmit diversity
Bit field
mapped
to index
0
2
RI=2: precoder cycling
with large delay CDD
reserved
1
2
3
reserved
3
Message
RI=2: precoder cycling
with large delay CDD
RI=3: precoder cycling
with large delay CDD
RI=4: precoder cycling
with large delay CDD
reserved
Format 3
DCI format 3 is used for the transmission of TPC commands for PUCCH and PUSCH with 2-bit power adjustments.
The following information is transmitted by means of the DCI format 3:
- TPC command number 1, TPC command number 2,…, TPC command number N
⎢L
⎥
where N = ⎢ format 0 ⎥ , and where Lformat 0 is equal to the payload size of format 0 before CRC attachment,
2
⎣
⎦
including any padding bits appended to format 0. The parameter tpc-Index provided by higher layers determines
the index to the TPC command for a given UE.
If
⎢ Lformat 0 ⎥ Lformat 0
⎢ 2 ⎥ < 2 , a bit of value zero shall be appended to format 3.
⎣
⎦
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.
The following information is transmitted by means of the DCI format 3A:
- TPC command number 1, TPC command number 2,…, TPC command number M
where M = Lformat 0 , and where Lformat 0 is equal to the payload size of format 0 before CRC attachment, including
any padding bits appended to format 0. The parameter tpc-Index provided by higher layers determines the index to the
TPC command for a given UE.
5.3.3.2
CRC attachment
Error detection is provided on DCI transmissions through a Cyclic Redundancy Check (CRC).
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
52
ETSI TS 136 212 V8.4.0 (2008-11)
The entire PDCCH payload is used to calculate the CRC parity bits. Denote the bits of the PDCCH payload
by a 0 , a1 , a 2 , a 3 ,..., a A−1 , and the parity bits by p 0 , p1 , p 2 , p 3 ,..., p L −1 . A is the PDCCH 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 ,..., b B −1 , where B = A+ L.
In the case where UE transmit antenna selection is not configured or applicable, after attachment, the CRC parity bits
are scrambled with the corresponding RNTI x rnti ,0 , x rnti ,1 ,..., x rnti ,15 to form the sequence of bits c 0 , c1 , c 2 , c 3 ,..., c B −1 .
The relation between ck and bk is:
c k = bk
for k = 0, 1, 2, …, A-1
c k = (bk + x rnti ,k − A )mod 2
for k = A, A+1, A+2,..., A+15.
In the case where UE transmit antenna selection is configured and applicable, after attachment, the CRC parity bits of
PDCCH with DCI format 0 are scrambled with the antenna selection mask x AS ,0 , x AS ,1 ,..., x AS ,15 as indicated in Table
5.3.3.2-1 and the corresponding RNTI x rnti ,0 , x rnti ,1 ,..., x rnti ,15 to form the sequence of bits c 0 , c1 , c 2 , c 3 ,..., c B −1 . The
relation between ck and bk is:
c k = bk
for k = 0, 1, 2, …, A-1
c k = (bk + x rnti ,k − A + x AS ,k − A )mod 2
for k = A, A+1, A+2,..., A+15.
Table 5.3.3.2-1: UE transmit antenna selection mask
UE transmit antenna selection
Antenna selection mask
< xAS ,0 , xAS ,1 ,..., x AS ,15 >
UE port 0
UE port 1
5.3.3.3
<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, 1>
Channel coding
Information bits are delivered to the channel coding block. They are denoted by c0 , c1 , c2 , c3 ,..., c K −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 .
5.3.3.4
Rate matching
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 ,..., e E −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,
DL
of the DCI in that subframe. The CFI takes values CFI = 1, 2 or 3. For system bandwidths N RB
> [10] , the span of the
DL
≤ [10] , the span of the DCI
DCI in units of OFDM symbols, 1, 2 or 3, is given by the CFI. For system bandwidths N RB
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.
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
53
ETSI TS 136 212 V8.4.0 (2008-11)
CFI
Channel coding
b0 , b1 ,..., b31
Figure 5.3.4-1 Coding for CFI
5.3.4.1
Channel coding
The control format indicator is coded according to Table 5.3.4-1.
Table 5.3.4-1: CFI codewords
CFI codeword
5.3.5
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>
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>
HARQ indicator
Data arrives to the coding unit in form of indicators for HARQ acknowledgement.
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
5.3.5.1
Channel coding
The HARQ indicator is coded according to Table 5.3.5-1, where for a positive acknowledgement HI = 1 and for a
negative acknowledgement HI = 0.
ETSI
3GPP TS 36.212 version 8.4.0 Release 8
54
Table 5.3.5-1: HI codewords
HI codeword
HI
< b0, b1, b2 >
0
< 0,0,0 >
1
< 1,1,1 >
ETSI
ETSI TS 136 212 V8.4.0 (2008-11)
3GPP TS 36.212 version 8.4.0 Release 8
55
ETSI TS 136 212 V8.4.0 (2008-11)
Annex A (informative):
Change history
Date
TSG #
2006-09
2006-10
2006-10
2006-11
TSG Doc.
CR
2006-11
2006-12
2007-01
2007-01
2007-02
2007-02
2007-02
2007-02
2007-02
2007-03
2007-03
2007-03
2007-05
2007-05
2007-05
2007-06
RAN#35
RP-070170
2007-06
2007-07
2007-07
2007-08
2007-08
2007-08
2007-09
2007-09
10/09/07
12/09/07
28/11/07
05/03/08
RAN#37
RAN_37
RAN_38
RAN_39
RP-070730
RP-070730
RP-070949
RP-080145
0001
0002
28/05/08
28/05/08
28/05/08
28/05/08
28/05/08
28/05/08
28/05/08
28/05/08
28/05/08
28/05/08
28/05/08
28/05/08
28/05/08
28/05/08
28/05/08
28/05/08
28/05/08
28/05/08
28/05/08
28/05/08
RAN_40
RAN_40
RAN_40
RAN_40
RAN_40
RAN_40
RAN_40
RAN_40
RAN_40
RAN_40
RAN_40
RAN_40
RAN_40
RAN_40
RAN_40
RAN_40
RAN_40
RAN_40
RAN_40
RAN_40
RP-080433
RP-080433
RP-080433
RP-080433
RP-080433
RP-080433
RP-080433
RP-080433
RP-080433
RP-080433
RP-080433
RP-080433
RP-080433
RP-080433
RP-080433
RP-080433
RP-080433
RP-080433
RP-080433
RP-080457
0003
0004
0005
0006
0008
0009
0010
0011
0012
0013
0014
0015
0016
0017
0018
0019
0020
0021
0022
0023
09/09/08
09/09/08
09/09/08
RAN_41
RAN_41
RAN_41
RP-080669
RP-080669
RP-080669
26
28
29
Change history
Rev Subject/Comment
Skeleton
Updated skeleton
Endorsed skeleton
Added TC. Added Broadcast, Paging and MBMS transport
channels in Table 4.2-1.
Endorsed v 0.2.0
Added CC. Added type of coding for each transport channel or
control information.
Editor"s version
Endorsed v 0.3.0
Added QPP turbo Interleaver description.
Editor"s version
Endorsed v 0.4.0
Added CRC details for PDSCH, PDCCH and PUSCH. Added QPP
turbo-interleaver parameters. Set Z to 6144. Added details on code
block segmentation.
Editor"s version
For information at RAN#35
Editor"s version
Editor"s version
Editor"s version
Editor"s version
Editor"s version
Added circular buffer rate matching for PDSCH and PUSCH.
Miscellaneous changes.
Editor"s version
Editor"s version
Endorsed by email following decision taken at RAN1#49b
Editor"s version including decision from RAN1#49bis.
Editor"s version
Editor"s version
Editor"s version with decisions from RAN1#50
Editor"s version
- For approval at RAN#37
- Approved version
- Update of 36.212
- Update to 36.212 incorporating decisions from RAN1#51bis and
RAN1#52
- Joint coding of CQI and ACK on PUCCH
1 ACK insertion into PUSCH
1 Introduction of format 1C
1 Miscellaneous fixes to 36.212
1 On multiplexing scheme for indicators
1 On the soft buffer split of MIMO and TDD
- Resource assignment field for distributed VRB
- Clarifying the use of the different DCI formats
1 Clarifying the value of NL
- Payload size for DCI formats 3 and 3A
- Coding of ACK on PUSCH
1 Coding of RI on PUSCH and mapping
- CRC for control information on PUSCH
- Introduction of Downlink Assignment Index
- Coding of CQI/PMI on PUSCH coming from PUCCH
- Simultaneous transmission of aperiodic CQI and UL control
- Encoding of antenna indicator on DCI format 0
- PDCCH coverage in narrow bandwidths
- Closed-loop and open-loop spatial multiplexing
- Formula for linkage between PUSCH MCS and amount of
resources used for control
- Correction to PUSCH Channel Interleaver
- Correction of mapping of ACK/NAK to binary bit values
- Correction to bit collection, selection and transmission
ETSI
Old
0.0.0
0.0.1
0.1.0
New
0.0.0
0.0.1
0.1.0
0.1.1
0.1.1
0.2.0
0.2.0
0.2.1
0.2.1
0.2.2
0.3.0
0.3.1
0.3.2
0.4.0
0.2.2
0.3.0
0.3.1
0.3.2
0.4.0
0.4.1
0.4.1
0.4.2
1.0.0
1.0.1
1.1.0
1.1.1
1.1.2
1.2.0
0.4.2
1.0.0
1.0.1
1.1.0
1.1.1
1.1.2
1.2.0
1.2.1
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.2
1,4.0
1.4.1
1.4.2
2.0.0
8.0.0
8.1.0
1.2.2
1.2.3
1.3.0
1.3.1
1.3.2
1.4.0
1,4,1
1.4.2
2.0.0
8.0.0
8.1.0
8.2.0
8.2.0
8.2.0
8.2.0
8.2.0
8.2.0
8.2.0
8.2.0
8.2.0
8.2.0
8.2.0
8.2.0
8.2.0
8.2.0
8.2.0
8.2.0
8.2.0
8.2.0
8.2.0
8.2.0
8.2.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.4.0
8.4.0
8.4.0
3GPP TS 36.212 version 8.4.0 Release 8
Date
TSG #
TSG Doc.
09/09/08 RAN_41 RP-080669
CR
30
09/09/08
09/09/08
09/09/08
09/09/08
09/09/08
RAN_41
RAN_41
RAN_41
RAN_41
RAN_41
RP-080669
RP-080669
RP-080669
RP-080669
RP-080669
31
32
33
35
09/09/08
09/09/08
09/09/08
09/09/08
09/09/08
09/09/08
09/09/08
09/09/08
11/09/08
09/09/08
RAN_41
RAN_41
RAN_41
RAN_41
RAN_41
RAN_41
RAN_41
RAN_41
RAN_41
RAN_41
RP-080669
RP-080669
RP-080669
RP-080669
RP-080669
RP-080669
RP-080669
RP-080669
RP-080736
RP-080669
37
38
39
41
42
43
44
45
46
09/09/08
RAN_41
RP-080669
09/09/08
RAN_41
RP-080669
36
47
48
91
56
ETSI TS 136 212 V8.4.0 (2008-11)
Change history
Rev Subject/Comment
Padding one bit to DCI format 1 when format 1 and format 0/1A
have the same size
- Modification of M_limit
- Definition of Formats 2 and 2A
2 Corrections to DCI formats
1 Format 1B confirmation flag
Corrections to Rank information scrambling in Uplink Shared
Channel
2 Clarification of TPC commands signaled in DCI formats 3/3A
- Clarification on UE transmit antenna selection mask
1 Linking of control resources in PUSCH to data MCS
- Definition of Bit Mapping for DCI signalling
1 Clarification on resource allocation in DCI format 1/2/2A
- DCI Format 1A changes needed for scheduling Broadcast Control
- DCI format1C
- Miscellaneous corrections
1 Correction on downlink multi-user MIMO
Corrections to DL DCI Formats In case of Ambiguous Payload
Sizes
CR for RE provisioning for the control information in case of CQIonly transmission on PUSCH
2 Coding and multiplexing of multiple ACK/NACK in PUSCH
ETSI
Old
8.3.0
New
8.4.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.4.0
8.4.0
8.4.0
8.4.0
8.4.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.3.0
8.4.0
8.4.0
8.4.0
8.4.0
8.4.0
8.4.0
8.4.0
8.4.0
8.4.0
8.4.0
8.3.0
8.4.0
8.3.0
8.4.0
3GPP TS 36.212 version 8.4.0 Release 8
57
History
Document history
V8.3.0
November 2008
Publication
V8.4.0
November 2008
Publication
ETSI
ETSI TS 136 212 V8.4.0 (2008-11)