3GPP TS 36.213

3rd Generation Partnership Project;
3GPP TS 36.213
Technical Specification Group Radio Access Network;
V10.0.0 (2010-12)
Evolved Universal Terrestrial Radio Access (E-UTRA);
Physical layer procedures
Technical Specification
(Release 10)
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this
Specification.
Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners’ Publications Offices.
Release 10 2 3GPP TS 36.213 V10.0.0 (2010-12)
Keywords
UMTS, radio, layer 1
3GPP
Postal address
3GPP support office address

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

The copyright and the foregoing restriction extend to reproduction in all media.
© 2010, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
All rights reserved.
UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP
Organizational Partners
GSM® and the GSM logo are registered and owned by the GSM Association
3GPP
Release 10 3 3GPP TS 36.213 V10.0.0 (2010-12)
Contents
Foreword..........................................................................................................................................................5
1 Scope......................................................................................................................................................6
2 References..............................................................................................................................................6
3 Definitions, symbols, and abbreviations.................................................................................................7
3.1 Symbols...............................................................................................................................................................7
3.2 Abbreviations.......................................................................................................................................................7
4 Synchronisation procedures....................................................................................................................8
4.1 Cell search...........................................................................................................................................................8
4.2 Timing synchronisation.......................................................................................................................................8
4.2.1 Radio link monitoring....................................................................................................................................8
4.2.2 Inter-cell synchronisation...............................................................................................................................8
4.2.3 Transmission timing adjustments...................................................................................................................8
4.3 Timing for Secondary Cell Activation / Deactivation.........................................................................................9
5 Power control.........................................................................................................................................9
5.1 Uplink power control...........................................................................................................................................9
5.1.1 Physical uplink shared channel......................................................................................................................9
5.1.1.1 UE behaviour............................................................................................................................................9
is satisfied where PˆPUSCH , j (i ) is the PUSCH transmit power for the cell with UCI and w(i ) is a scaling factor
of PˆPUSCH , c (i ) for serving cell c without UCI. In this case, no power scaling is applied to
ˆ
PPUSCH , j (i ) unless

c j
ˆ
w( i )  PPUSCH, c (i )  0
and the total transmit power of the UE still
would exceed P̂PowerClass . Note that w(i ) values are the same across serving cells when
w(i )  0 but for certain serving cells w(i ) may be zero.5.1.1.2 Power
headroom 13
5.1.2 Physical uplink control channel...................................................................................................................15
5.1.2.1 UE behaviour..........................................................................................................................................15
5.1.3 Sounding Reference Symbol........................................................................................................................17
5.1.3.1 UE behaviour..........................................................................................................................................17
5.2 Downlink power allocation...............................................................................................................................17
5.2.1 eNodeB Relative Narrowband TX Power restrictions.................................................................................19
6 Random access procedure.....................................................................................................................19
6.1 Physical non-synchronized random access procedure.......................................................................................20
6.1.1 Timing..........................................................................................................................................................20
6.2 Random Access Response Grant.......................................................................................................................21
7 Physical downlink shared channel related procedures..........................................................................22
7.1 UE procedure for receiving the physical downlink shared channel..................................................................22
7.1.1 Single-antenna port scheme.........................................................................................................................26
7.1.2 Transmit diversity scheme..........................................................................................................................27
7.1.3 Large delay CDD scheme...........................................................................................................................27
7.1.4 Closed-loop spatial multiplexing scheme...................................................................................................27
7.1.5 Multi-user MIMO scheme..........................................................................................................................27
7.1.5A Dual layer scheme.......................................................................................................................................27
7.1.5B Up to 8 layer transmission..........................................................................................................................27
7.1.6 Resource allocation.....................................................................................................................................27
7.1.6.1 Resource allocation type 0.....................................................................................................................27
7.1.6.4 PDSCH starting position........................................................................................................................30
7.1.6.5 PRB bundling.........................................................................................................................................30
7.1.7 Modulation order and transport block size determination..........................................................................30
7.1.7.1 Modulation order determination.............................................................................................................31
3GPP
Release 10 4 3GPP TS 36.213 V10.0.0 (2010-12)
7.1.7.2 Transport block size determination........................................................................................................32

7.1.7.2.1 Transport blocks not mapped to two-layer spatial multiplexing............................................................32
7.1.7.2.2 Transport blocks mapped to two-layer spatial multiplexing..................................................................38
7.1.7.2.3 Transport blocks mapped for DCI Format 1C.......................................................................................39
7.1.7.2.4 Transport blocks mapped to three-layer spatial multiplexing................................................................39
7.1.7.2.5 Transport blocks mapped to four-layer spatial multiplexing.................................................................40
7.1.7.3 Redundancy Version determination for Format 1C...............................................................................41
7.2 UE procedure for reporting channel quality indication (CQI), precoding matrix indicator (PMI) and rank
indication (RI)....................................................................................................................................................41
7.2.1 Aperiodic CQI/PMI/RI Reporting using PUSCH........................................................................................44
7.2.2 Periodic CQI/PMI/RI Reporting using PUCCH..........................................................................................49
7.2.3 Channel quality indicator (CQI) definition..................................................................................................58
7.2.4 Precoding Matrix Indicator (PMI) definition...............................................................................................60
7.2.5 Channel-State Information – Reference Symbol (CSI-RS) definition.........................................................61
7.3 UE procedure for reporting ACK/NACK..........................................................................................................61
8 Physical uplink shared channel related procedures...............................................................................64
8.0 UE procedure for transmitting the physical uplink shared channel...................................................................65
8.0.1 Single-antenna port scheme.........................................................................................................................68
8.0.2 Closed-loop spatial multiplexing scheme...................................................................................................68
8.1 Resource Allocation for PDCCH with uplink DCI Format...............................................................................68
8.1.1 Uplink Resource allocation type 0.........................................................................................................68
8.1.2 Uplink Resource allocation type 1.........................................................................................................68
8.2 UE sounding procedure.....................................................................................................................................69
8.3 UE ACK/NACK procedure...............................................................................................................................72
8.4 UE PUSCH Hopping procedure........................................................................................................................73
8.4.1 Type 1 PUSCH Hopping.............................................................................................................................74
8.4.2 Type 2 PUSCH Hopping.............................................................................................................................74
8.5 UE Reference Symbol procedure......................................................................................................................75
8.6 Modulation order, redundancy version and transport block size determination...............................................75
8.6.1 Modulation order and redundancy version determination..........................................................................75
8.6.2 Transport block size determination.............................................................................................................76
8.6.3 Control information MCS offset determination..........................................................................................77
8.7 UE Transmit Antenna Selection........................................................................................................................79
9 Physical downlink control channel procedures.....................................................................................79
9.1 UE procedure for determining physical downlink control channel assignment................................................79
9.1.1 PDCCH Assignment Procedure...................................................................................................................79
9.1.2 PHICH Assignment Procedure....................................................................................................................80
9.1.3 Control Format Indicator assignment procedure.........................................................................................82
9.2 PDCCH validation for semi-persistent scheduling............................................................................................82
9.3 PDCCH control information procedure.............................................................................................................83
10 Physical uplink control channel procedures..........................................................................................84
10.1 UE procedure for determining physical uplink control channel assignment.....................................................84
10.2 Uplink ACK/NACK timing...............................................................................................................................93
11 Physical multicast channel related procedures......................................................................................94
11.1 UE procedure for receiving the physical multicast channel..............................................................................94
11.2 UE procedure for receiving MCCH change notification...................................................................................94
Annex A (informative): Change history................................................................................................95
3GPP
Release 10 5 3GPP TS 36.213 V10.0.0 (2010-12)
Foreword
This Technical Specification (TS) 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 this present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
3GPP
Release 10 6 3GPP TS 36.213 V10.0.0 (2010-12)
1 Scope
The present document specifies and establishes the characteristics of the physicals layer procedures in the FDD and
TDD modes of 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.201: “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Layer –
General Description”
[3] 3GPP TS 36.211: “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and
modulation”
[4] 3GPP TS 36.212: “Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and
channel coding”
[5] 3GPP TS 36.214: “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer –
Measurements”
[6] 3GPP TS 36.101: “Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE)
radio transmission and reception”
[7] 3GPP TS 36.104: “Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS)
radio transmission and reception”
[8] 3GPP TS36.321, “Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access
Control (MAC) protocol specification”
[9] 3GPP TS36.423, “Evolved Universal Terrestrial Radio Access (E-UTRA); X2 Application
Protocol (X2AP)”
[10] 3GPP TS36.133, “Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for
support of radio resource management”
[11] 3GPP TS36.331, “Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource
Control (RRC) protocol specification”
3GPP
Release 10 7 3GPP TS 36.213 V10.0.0 (2010-12)
3 Definitions, symbols, and abbreviations
3.1 Symbols
For the purposes of the present document, the following symbols apply:
nf System frame number as defined in [3]

ns Slot number within a radio frame as defined in [3]
DL RB
N RB Downlink bandwidth configuration, expressed in units of N sc as defined in [3]
UL RB
N RB Uplink bandwidth configuration, expressed in units of N sc as defined in [3]
UL
N symb Number of SC-FDMA symbols in an uplink slot as defined in [3]
RB
N sc Resource block size in the frequency domain, expressed as a number of subcarriers as defined in
[3]
Ts Basic time unit as defined in [3]
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply.
ACK Acknowledgement
BCH Broadcast Channel
CCE Control Channel Element
CIF Carrier Indicator Field.
CQI Channel Quality Indicator
CRC Cyclic Redundancy Check
DAI Downlink Assignment Index
DCI Downlink Control Information
DL Downlink
DL-SCH Downlink Shared Channel
DTX Discontinuous Transmission
EPRE Energy Per Resource Element
MCS Modulation and Coding Scheme
NACK Negative Acknowledgement
PBCH Physical Broadcast Channel
PCFICH Physical Control Format Indicator Channel
PDCCH Physical Downlink Control Channel
PDSCH Physical Downlink Shared Channel
PHICH Physical Hybrid ARQ Indicator Channel
PMCH Physical Multicast Channel
PRACH Physical Random Access Channel
PRB Physical Resource Block
PUCCH Physical Uplink Control Channel
PUSCH Physical Uplink Shared Channel
QoS Quality of Service
RBG Resource Block Group
RE Resource Element
RPF Repetition Factor
RS Reference Signal
SIR Signal-to-Interference Ratio
SINR Signal to Interference plus Noise Ratio
SPS C-RNTI Semi-Persistent Scheduling C-RNTI
SR Scheduling Request
SRS Sounding Reference Symbol
TA Time alignment
TTI Transmission Time Interval
3GPP
Release 10 8 3GPP TS 36.213 V10.0.0 (2010-12)
UE User Equipment
UL Uplink
UL-SCH Uplink Shared Channel
VRB Virtual Resource Block
4 Synchronisation procedures
4.1 Cell search

Cell search is the procedure by which a UE acquires time and frequency synchronization with a cell and detects the
physical layer Cell ID of that cell. E-UTRA cell search supports a scalable overall transmission bandwidth
corresponding to 6 resource blocks and upwards.
The following signals are transmitted in the downlink to facilitate cell search: the primary and secondary
synchronization signals.
4.2 Timing synchronisation

4.2.1 Radio link monitoring
The downlink radio link quality of the primary cell shall be monitored by the UE for the purpose of indicating out-of-
sync/in-sync status to higher layers.
In non-DRX mode operation, the physical layer in the UE shall every radio frame assess the radio link quality,
evaluated over the previous time period defined in [10], against thresholds (Qout and Qin) defined by relevant tests in
[10].
In DRX mode operation, the physical layer in the UE shall at least once every DRX period assess the radio link quality,
evaluated over the previous time period defined in [10], against thresholds (Qout and Qin) defined by relevant tests in
[10].
The physical layer in the UE shall in radio frames where the radio link quality is assessed indicate out-of-sync to higher
layers when the radio link quality is worse than the threshold Qout. When the radio link quality is better than the
threshold Qin, the physical layer in the UE shall in radio frames where the radio link quality is assessed indicate in-sync
to higher layers.
4.2.2 Inter-cell synchronisation

No functionality is specified in this section in this release.
4.2.3 Transmission timing adjustments

Upon reception of a timing advance command, the UE shall adjust its uplink transmission timing for
PUCCH/PUSCH/SRS of the primary cell. The timing advance command indicates the change of the uplink timing
relative to the current uplink timing as multiples of 16 Ts . The start timing of the random access preamble is specified
in [3]. The UL transmission timing for PUSCH/SRS of a secondary cell is the same as the primary cell.
In case of random access response, 11-bit timing advance command [8], TA, indicates NTA values by index values of TA
= 0, 1, 2, ..., 1282, where an amount of the time alignment is given by NTA = TA 16. NTA is defined in [3].
In other cases, 6-bit timing advance command [8], TA, indicates adjustment of the current NTA value, NTA,old, to the new
NTA value, NTA,new, by index values of TA = 0, 1, 2,..., 63, where NTA,new = NTA,old + (TA 31)16. Here, adjustment of NTA
value by a positive or a negative amount indicates advancing or delaying the uplink transmission timing by a given
amount respectively.
For a timing advance command received on subframe n, the corresponding adjustment of the timing shall apply from
the beginning of subframe n+6. When the UE’s uplink PUCCH/PUSCH/SRS transmissions in subframe n and subframe
3GPP
Release 10 9 3GPP TS 36.213 V10.0.0 (2010-12)
n+1 are overlapped due to the timing adjustment, the UE shall transmit complete subframe n and not transmit the
overlapped part of subframe n+1.
If the received downlink timing changes and is not compensated or is only partly compensated by the uplink timing
adjustment without timing advance command as specified in [10], the UE changes NTA accordingly.
4.3 Timing for Secondary Cell Activation / Deactivation

When a UE receives an activation or deactivation command [8] for a secondary cell in subframe n, the corresponding
actions in [8] shall apply no later than subframe n+[x].
5 Power control
Downlink power control determines the energy per resource element (EPRE). The term resource element energy
denotes the energy prior to CP insertion. The term resource element energy also denotes the average energy taken over
all constellation points for the modulation scheme applied. Uplink power control determines the average power over a
SC-FDMA symbol in which the physical channel is transmitted.
5.1 Uplink power control

Uplink power control controls the transmit power of the different uplink physical channels.
For PUSCH, the transmit power PˆPUSCH , c (i ) defined in section 5.1.1, is first scaled by the ratio of the number of
antennas ports with a non-zero PUSCH transmission to the number of configured antenna ports for the transmission
scheme. The resulting scaled power is then split equally across the antenna ports on which the non-zero PUSCH is
transmitted.
For PUCCH or SRS, the transmit power PˆPUCCH (i ) , defined in Section 5.1.2, or PˆSRS,c (i ) is split equally across
the configured antenna ports for PUCCH or SRS. PˆSRS,c (i ) is the linear value of PSRS,c (i ) defined in Section 5.1.3.
A cell wide overload indicator (OI) and a High Interference Indicator (HII) to control UL interference are defined in [9].
5.1.1 Physical uplink shared channel
5.1.1.1 UE behaviour
The setting of the UE Transmit power for a physical uplink shared channel (PUSCH) transmission is defined as follows.
If the UE transmits PUSCH without a simultaneous PUCCH for the serving cell c , then the UE transmit power
PPUSCH , c (i ) for PUSCH transmission in subframe i for the serving cell c is given by
 PCMAX, c (i ), 
PPUSCH,c (i )  min
10 log10 ( M PUSCH,c (i ))  PO_PUSCH,c ( j )   c ( j )  PLc   TF, c (i )  f c (i ) 
 [dBm]
If the UE transmits PUSCH simultaneous with PUCCH for the serving cell c , then the UE transmit power
PPUSCH ,c (i ) for the PUSCH transmission in subframe i for the serving cell c is given by

10 log10 P ˆ  ˆ
CMAX, c (i )  PPUCCH (i ) ,  

PPUSCH,c (i )  min  [dBm]
10 log10 ( M PUSCH,c (i ))  PO_PUSCH,c ( j )   c ( j )  PLc   TF, c (i )  f c (i ) 
 
where,
 PCMAX, c (i ) is the configured UE transmit power defined in [6] in subframe i for serving cell c and
PˆCMAX,c (i ) is the linear value of PCMAX,c (i ) .
3GPP
Release 10 10 3GPP TS 36.213 V10.0.0 (2010-12)
 PˆPUCCH (i ) is the linear value of PPUCCH (i ) defined in section 5.1.2.1
 M PUSCH,c (i ) is the bandwidth of the PUSCH resource assignment expressed in number of resource blocks
valid for subframe i and serving cell c.
 PO_PUSCH, c ( j ) is a parameter composed of the sum of a component PO_NOMINAL_ PUSCH,c ( j ) provided
from higher layers for j=0 and 1 and a component PO_UE_PUSCH,c ( j ) provided by higher layers for j=0 and
1 for serving cell c . For PUSCH (re)transmissions corresponding to a semi-persistent grant then j=0 , for
PUSCH (re)transmissions corresponding to a dynamic scheduled grant then j=1 and for PUSCH
(re)transmissions corresponding to the random access response grant then j=2. PO_UE_PUSCH,c ( 2)  0 and
PO_NOMINAL_PUSCH,c (2)  PO_PRE   PREAMBLE _ Msg 3 , where the parameter
preambleInitialReceivedTargetPower [8] ( PO_PRE ) and  PREAMBLE _ Msg 3 are signalled from higher layers.
 For j =0 or 1,  c   0, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1 is a 3-bit parameter provided by higher
layers for serving cell c . For j=2,  c ( j )  1.
 PLc is the downlink pathloss estimate calculated in the UE for serving cell c in dB and PLc =
referenceSignalPower – higher layer filtered RSRP, where referenceSignalPower is provided by higher layers
and RSRP is defined in [5] for the reference serving cell and the higher layer filter configuration is defined in
[11] for the reference serving cell. The serving cell chosen as the reference serving cell and used for
determining referenceSignalPower and higher layer filtered RSRP is configured by the higher layer parameter
pathlossReferenceLinking.
o  TF , c (i )  10 log10  2 BPRE  K s
 PUSCH
 1   offset  for K S  1.25 and 0 for K S  0 where K S is
given by the parameter deltaMCS-Enabled provided by higher layers for each serving cell c.
BPRE and PUSCH
 offset , for each serving cell c , are computed as below. K S  0 for transmission
mode 2. BPRE  OCQI / N RE for control data sent via PUSCH without UL-SCH data and
C 1
 K r / N RE for other cases.

r 0
 where C is the number of code blocks, K r is the size for code block r , OCQI is the
number of CQI bits including CRC bits and N RE is the number of resource elements
PUSCH  initial PUSCH - initial PUSCH initial
determined as N RE  M sc  N symb , where C , K r , M sc
PUSCH -initial
and N symb are defined in [4].
o  offset
PUSCH
  offset
CQI
for control data sent via PUSCH without UL-SCH data and 1 for other cases.
  PUSCH,c is a correction value, also referred to as a TPC command and is included in PDCCH with DCI
format 0 for serving cell c or jointly coded with other TPC commands in PDCCH with DCI format 3/3A
whose CRC parity bits are scrambled with TPC-PUSCH-RNTI. The current PUSCH power control adjustment
state for serving cell c is given by f c (i ) which is defined by:
o f c (i )  f c (i  1)   PUSCH,c (i  K PUSCH ) if accumulation is enabled based on the parameter

Accumulation-enabled provided by higher layers or if the TPC command  PUSCH,c is included in a
PDCCH with DCI format 0 for serving cell c where the CRC is scrambled by the Temporary C-
RNTI
 where  PUSCH,c (i  K PUSCH ) was signalled on PDCCH with DCI format 0 or 3/3A on
subframe i  K PUSCH , and where f c (0) is the first value after reset of accumulation.
 The value of K PUSCH is
 For FDD, K PUSCH = 4
3GPP
Release 10 11 3GPP TS 36.213 V10.0.0 (2010-12)
 For TDD UL/DL configurations 1-6, K PUSCH is given in Table 5.1.1.1-1
 For TDD UL/DL configuration 0

o If the PUSCH transmission in subframe 2 or 7 is scheduled with a PDCCH
of DCI format 0 in which the LSB of the UL index is set to 1, K PUSCH =
7
K PUSCH
o For all other PUSCH transmissions, is given in Table 5.1.1.1-1.
 The UE attempts to decode a PDCCH of DCI format 0 with the UE’s C-RNTI or SPS C-
RNTI and a PDCCH of DCI format 3/3A with this UE’s TPC-PUSCH-RNTI in every
subframe except when in DRX
 If DCI format 0 for serving cell c and DCI format 3/3A are both detected in the same
subframe, then the UE shall use the  PUSCH, c provided in DCI format 0.
  PUSCH,c  0 dB for a subframe where no TPC command is decoded for serving cell c or
where DRX occurs or i is not an uplink subframe in TDD.
 The  PUSCH,c dB accumulated values signalled on PDCCH with DCI format 0 are given in
Table 5.1.1.1-2. If the PDCCH with DCI format 0 is validated as a SPS activation or release
PDCCH, then  PUSCH,c is 0dB.
 The  PUSCH dB accumulated values signalled on PDCCH with DCI format 3/3A are one of
SET1 given in Table 5.1.1.1-2 or SET2 given in Table 5.1.1.1-3 as determined by the
parameter TPC-Index provided by higher layers.
 If UE has reached PCMAX,c for serving cell c , positive TPC commands for serving cell
c shall not be accumulated
 If UE has reached minimum power, negative TPC commands shall not be accumulated
 UE shall reset accumulation
 For serving cell c , when PO_UE_PUSCH, c value is changed by higher layers
 For the primary cell, when the UE receives random access response message
o f c (i )   PUSCH, c (i  K PUSCH ) if accumulation is not enabled for serving cell c based on the
parameter Accumulation-enabled provided by higher layers
 where  PUSCH,c (i  K PUSCH ) was signalled on PDCCH with DCI format 0 for serving
cell c on subframe i  K PUSCH
 The value of K PUSCH is
 For FDD, K PUSCH = 4
 For TDD UL/DL configurations 1-6, K PUSCH is given in Table 5.1.1.1-1
 For TDD UL/DL configuration 0

o If the PUSCH transmission in subframe 2 or 7 is scheduled with a PDCCH
of DCI format 0 in which the LSB of the UL index is set to 1, K PUSCH =
7
o For all other PUSCH transmissions, K PUSCH is given in Table 5.1.1.1-1.
 The  PUSCH,c dB absolute values signalled on PDCCH with DCI format 0 are given in
Table 5.1.1.1-2. If the PDCCH with DCI format 0 is validated as a SPS activation or release
PDCCH, then  PUSCH,c is 0dB.
3GPP
Release 10 12 3GPP TS 36.213 V10.0.0 (2010-12)
 f c (i )  f c (i  1) for a subframe where no PDCCH with DCI format 0 is decoded for

serving cell c or where DRX occurs or i is not an uplink subframe in TDD.
o For both types of f c () (accumulation or current absolute) the first value is set as follows:
 If PO_UE_PUSCH,c value is changed by higher layers and serving cell c is the

primary cell or, if PO_UE_PUSCH,c value is received by higher layers and serving
cell c is a Secondary cell f c (0)  0
 Else
 If serving cell c is the primary cell
o f c (0)  Prampup   msg 2
 where  msg 2 is the TPC command indicated in the random

access response, see Section 6.2, and
 Prampup is provided by higher layers and corresponds to the
total power ramp-up from the first to the last preamble
Table 5.1.1.1-1
K PUSCH for TDD configuration 0-6
TDD UL/DL subframe number i

Configuratio
n 0 1 2 3 4 5 6 7 8 9
0 - - 6 7 4 - - 6 7 4
1 - - 6 4 - - - 6 4 -
2 - - 4 - - - - 4 - -
3 - - 4 4 4 - - - - -
4 - - 4 4 - - - - - -
5 - - 4 - - - - - - -
6 - - 7 7 5 - - 7 7 -
Table 5.1.1.1-2: Mapping of TPC Command Field in DCI format 0/3 to absolute and accumulated
 PUSCH,c values.
Accumulated
TPC Command Field in  PUSCH,c Absolute  PUSCH,c
DCI format 0/3 [dB] only DCI format 0
[dB]
0 -1 -4
1 0 -1
2 1 1
3 3 4
3GPP
Release 10 13 3GPP TS 36.213 V10.0.0 (2010-12)
Table 5.1.1.1-3: Mapping of TPC Command Field in DCI format 3A to accumulated  PUSCH,c values.
TPC Command Field in Accumulated  PUSCH,c

DCI format 3A [dB]
0 -1
1 1
If the total transmit power of the UE would exceed P̂PowerClass , the UE scales PˆPUSCH , c (i ) for the serving cell c in
subframe i such that the condition
 w(i )  Pˆ PUSCH , c (i )
ˆ
 P  ˆ
PowerClass  PPUCCH (i ) 
c
is satisfied where PˆPUCCH (i ) is the linear value of PPUCCH (i ) , PˆPUSCH , c (i ) is the linear value of
PPUSCH ,c (i ) , P̂PowerClass is the linear value of PPowerClass defined in [6] and w(i ) is a scaling factor of
ˆ
PPUSCH , c (i ) for serving cell c where 0  w(i )  1 . In case there is no PUCCH transmission in subframe i
PˆPUCCH (i )  0 .
If the UE has PUSCH transmission with UCI on cell j and PUSCH without UCI in the remaining cells, and the total
transmit power of the UE would exceed P̂PowerClass , the UE scales PˆPUSCH , c (i ) for the serving cells without UCI
in subframe i such that the condition
 w(i )  Pˆ PUSCH ,c (i )
ˆ
 P  ˆ
PowerClass  PPUSCH , j (i ) 
c j
is satisfied where PˆPUSCH , j (i ) is the PUSCH transmit power for the cell with UCI and w(i ) is a scaling factor of
ˆ ˆ
PPUSCH , c (i ) for serving cell c without UCI. In this case, no power scaling is applied to PPUSCH , j (i ) unless

c j
ˆ
w( i )  PPUSCH, c (i )  0
and the total transmit power of the UE still would exceed P̂PowerClass . Note that
w(i ) values are the same across serving cells when w(i )  0 but for certain serving cells w(i ) may be zero.5.1.1.2
5.1.1.2 Power headroom

There are two types of UE power headroom reports defined. A UE power headroom PH is valid for subframe i for
serving cell c .
Type 1:
If the UE transmits PUSCH in subframe i for serving cell c , power headroom for a Type 1 report is computed using
PH type1,c (i )  PCMAX, c (i )   10 log10 ( M PUSCH,c (i ))  PO_PUSCH,c ( j )   c ( j )  PLc   TF, c (i )  f c (i ) 
[dB]
where, PCMAX , c , M PUSCH,c (i ) , PO_PUSCH, c ( j ) ,  c ( j ). , PLc ,  TF , c (i ) and f c (i ) are defined in

section 5.1.1.1.
If the UE does not transmit PUSCH in subframe i for serving cell c , power headroom for a Type 1 report is
computed using
PH type1,c (i )  PCMAX, c (i )   PO_PUSCH,c ( j )   c ( j )  PLc  f c (i )  [dB]
where, PCMAX,c (i ) is computed assuming MPR=0dB, A-MPR=0dB, TC =0dB, MPR , A-MPR, TC which are
defined in [6]. PO_PUSCH, c ( j ) ,  c ( j ). , PLc , and f c (i ) are defined in section 5.1.1.1.
3GPP
Release 10 14 3GPP TS 36.213 V10.0.0 (2010-12)
Type 2:
If the UE transmits PUSCH simultaneous with PUCCH in subframe i for the primary cell, power headroom for a Type
2 report is computed using
10 10 log10 ( M PUSCH,c ( i ))  PO_PUSCH,c ( j )   c ( j )  PLc   TF, c ( i )  f c ( i )  10 

PH type2 (i )  PCMAX, c (i )  10 log10  
[dB]
  P0_PUCCH  PLc  h  n CQI , n HARQ , n SR    F_PUCCH  F    TxD ( F ' )  g  i   10 
  10 
where, PCMAX,c , M PUSCH,c (i ) , PO_PUSCH, c ( j ) ,  c ( j )  TF , c (i ) and f c (i ) are the primary cell

parameters as defined in section 5.1.1.1 and PO_PUCCH , PLc , h(nCQI , n HARQ , n SR ) ,  F_PUCCH ( F ) ,
 TxD (F ' ) and g (i ) are defined in section 5.1.2.1
If the UE transmits PUSCH without PUCCH in subframe i for the primary cell, power headroom for a Type 2 report is
computed using
 10 10 log10 ( M PUSCH, c ( i ))  PO_PUSCH,c ( j )   c ( j )  PLc   TF, c ( i )  f c ( i )  10 

PH type2 (i )  PCMAX , c (i )  10 log10  
[dB]
  P0_PUCCH  PL c  g  i   10 
  10 
where, PCMAX,c (i ) , M PUSCH,c (i ) , PO_PUSCH, c ( j ) ,  c ( j )  TF , c (i ) and f c (i ) are the primary cell

parameters as defined in section 5.1.1.1, PO_PUCCH , PLc and g (i ) are defined in section 5.1.2.1.
If the UE transmits PUCCH without PUSCH in subframe i for the primary cell, power headroom for a Type 2 report is
computed using
10  PO_PUSCH,c (1)   c (1)  PLc  f c ( i )  10 

PH type2 (i )  PCMAX, c (i )  10 log10  
[dB]
  P0_PUCCH  PLc  h  nCQI , n HARQ , n SR    F_PUCCH  F    TxD ( F ' )  g  i   10 
  10 
where, PO_PUSCH, c (1) ,  c (1) , K PUSCH and f c (i ) are the primary cell parameters as defined in section
5.1.1.1, PCMAX,c (i ) , PO_PUCCH , PLc , h(nCQI , n HARQ , n SR ) ,  F_PUCCH ( F ) ,  TxD (F ' ) and g (i ) are also
defined in section 5.1.2.1.
If the UE does not transmit PUCCH or PUSCH in subframe i for the primary cell, power headroom for a Type 2 report
is computed using
10  PO_PUSCH,c (1)   c (1)  PLc  f c ( i )  10 

PH type2 (i )  PCMAX , c (i )  10 log10  
[dB]
  P0_PUCCH  PLc  g  i   10 
  10 
where, PCMAX ,c (i ) is computed assuming MPR=0dB, A-MPR=0dB, TC =0dB, MPR , A-MPR, TC which are
defined in [6], PCMAX,c , PO_PUSCH, c (1) ,  c (1) , K PUSCH and f c (i ) are the primary cell parameters as
defined in section 5.1.1.1, PO_PUCCH , PLc and g (i ) are defined in section 5.1.2.1
The power headroom shall be rounded to the closest value in the range [40; -23] dB with steps of 1 dB and is delivered
by the physical layer to higher layers.
3GPP
Release 10 15 3GPP TS 36.213 V10.0.0 (2010-12)
5.1.2 Physical uplink control channel
If serving cell c is the primary cell, the setting of the UE Transmit power PPUCCH for the physical uplink control
channel (PUCCH) transmission in subframe i is defined by
PCMAX, c (i ), 
PPUCCH  i   min [dBm]
 
P0_PUCCH  PLc  h nCQI , n HARQ , n SR   F_PUCCH  F    TxD ( F ' )  g  i  

where
 PCMAX,c (i ) is the configured UE transmit power defined in [6] in subframe i for serving cell c.
 The parameter  F_PUCCH ( F ) is provided by higher layers. Each  F_PUCCH ( F ) value corresponds to a PUCCH
format (F) relative to PUCCH format 1a, where each PUCCH format (F ) is defined in Table 5.4-1 of [3].
 If the UE is configured by higher layers to transmit PUCCH on two antenna ports, the value of  TxD (F ' ) is
provided by higher layers where each PUCCH format F’ is defined in [3].
 h(nCQI , n HARQ , n SR ) is a PUCCH format dependent value, where nCQI corresponds to the number of
information bits for the channel quality information defined in section 5.2.3.3 in [4]. n SR = 1 if subframe i is
configured for SR for the UE, otherwise n SR =0. If the UE is configured with one serving cell n HARQ is the
number of HARQ bits sent in subframe i. In the case of ACK/NACK bundling is not applied, if the UE is
configured with more than one serving cell, and if the UE receives an SPS release PDCCH in one of the
subframes i  k m where k m  K and 0  m  M  1 then n HARQ = (number of transport blocks
received in subframes i  k m )+1, if the UE does not receive an SPS release PDCCH in one of the subframes
i  k m then n HARQ = (number of transport blocks received in subframes i  k m ). For FDD, M  1 and
k 0  4 . For TDD, values of M , K and k m are given in Table 10.1-1.
o For PUCCH format 1,1a and 1b h nCQI , n HARQ , n SR  0  

o For PUCCH format 1b with channel selection, if the UE is configured with more than one serving
cell, h(nCQI , nHARQ , nSR ) 

nHARQ  1 , otherwise, h nCQI , n HARQ , nSR   0
2
o For PUCCH format 2, 2a, 2b and normal cyclic prefix
  nCQI 

h nCQI , n HARQ, n SR   
10 log10 
 4
 if nCQI  4


0 otherwise

o For PUCCH format 2 and extended cyclic prefix
  nCQI  nHARQ 

h nCQI , nHARQ , nSR  10 log10 

 4
 if nCQI  nHARQ  4


0 otherwise

o For PUCCH format 3
n HARQ  n SR  1
h(nCQI , n HARQ , n SR ) 
2
 PO_PUCCH is a parameter composed of the sum of a parameter PO_NOMINAL_ PUCCH provided by higher
layers and a parameter PO_UE_PUCCH provided by higher layers.
  PUCCH is a UE specific correction value, also referred to as a TPC command, included in a PDCCH with
DCI format 1A/1B/1D/1/2A/2/2B for the primary cell or sent jointly coded with other UE specific PUCCH
3GPP
Release 10 16 3GPP TS 36.213 V10.0.0 (2010-12)
correction values on a PDCCH with DCI format 3/3A whose CRC parity bits are scrambled with TPC-
PUCCH-RNTI.
o The UE attempts to decode a PDCCH of DCI format 3/3A with the UE’s TPC-PUCCH-RNTI and one
or several PDCCHs of DCI format 1A/1B/1D/1/2A/2/2B with the UE’s C-RNTI or SPS C-RNTI on
every subframe except when in DRX.
o If the UE decodes a PDCCH with DCI format 1A/1B/1D/1/2A/2/2B for the primary cell and the
corresponding detected RNTI equals the C-RNTI or SPS C-RNTI of the UE, the UE shall use the
 PUCCH provided in that PDCCH.
else
 if the UE decodes a PDCCH with DCI format 3/3A, the UE shall use the  PUCCH provided
in that PDCCH
else the UE shall set  PUCCH = 0 dB.
M 1
o g (i )  g (i  1)    PUCCH (i  km ) where g (i ) is the current PUCCH power control adjustment
m 0
state and where g  0  is the first value after reset.
 For FDD, M  1 and k 0  4 .

 For TDD, values of M and k m are given in Table 10.1-1.
 The  PUCCH dB values signalled on PDCCH with DCI format 1A/1B/1D/1/2A/2/2B are
given in Table 5.1.2.1-1. If the PDCCH with DCI format 1/1A/2/2A/2B is validated as an
SPS activation PDCCH, or the PDCCH with DCI format 1A is validated as an SPS release
PDCCH, then  PUCCH is 0dB.
 The  PUCCH dB values signalled on PDCCH with DCI format 3/3A are given in Table
5.1.2.1-1 or in Table 5.1.2.1-2 as semi-statically configured by higher layers.
 If PO_UE_PUCCH value is changed by higher layers,
 g  0  0
 Else
 g (0)  Prampup   msg 2
o where  msg 2 is the TPC command indicated in the random access

response, see Section 6.2 and
o Prampup is the total power ramp-up from the first to the last preamble
provided by higher layers
 If UE has reached PCMAX,c for the primary cell, positive TPC commands for the primary
cell shall not be accumulated
 If UE has reached minimum power, negative TPC commands shall not be accumulated
 UE shall reset accumulation
 when PO_UE_PUCCH value is changed by higher layers
 when the UE receives a random access response message
 g (i )  g (i  1) if i is not an uplink subframe in TDD.
3GPP
Release 10 17 3GPP TS 36.213 V10.0.0 (2010-12)
Table 5.1.2.1-1: Mapping of TPC Command Field in DCI format 1A/1B/1D/1/2A/2B/2/3 to  PUCCH
values.
TPC Command Field in

DCI format  PUCCH [dB]
1A/1B/1D/1/2A/2B/2/3
0 -1
1 0
2 1
3 3
Table 5.1.2.1-2: Mapping of TPC Command Field in DCI format 3A to  PUCCH values.
TPC Command Field in  PUCCH [dB]

DCI format 3A
0 -1
1 1
5.1.3 Sounding Reference Symbol
The setting of the UE Transmit power PSRS for the Sounding Reference Symbol transmitted on subframe i for serving
cell c is defined by

PSRS,c  i   min PCMAX,c (i ), PSRS_OFFSET, c  10 log10 ( M SRS,c )  PO_PUSCH,c ( j )   c ( j )  PLc  f c  i  
[dBm]
where
 PCMAX,c (i ) is the configured UE transmit power defined in [6] in subframe i for serving cell c.
 PSRS_OFFSET,c ( m) is a 4-bit parameter semi-statically configured by higher layers for m=0 and m=1 for
serving cell c . For SRS transmission given trigger type 0 then m=0 and for SRS transmission given trigger
type 1 then m=1. For K S  1.25 , PSRS_OFFSET,c ( m) has 1dB step size in the range [-3, 12] dB. For
K S  0 , PSRS_OFFSET,c ( m) has 1.5 dB step size in the range [-10.5, 12] dB.
 M SRS,c is the bandwidth of the SRS transmission in subframe i for serving cell c expressed in number of
resource blocks.
 f c (i ) is the current PUSCH power control adjustment state for serving cell c , see Section 5.1.1.1.
 PO_PUSCH,c ( j ) and  c ( j ) are parameters as defined in Section 5.1.1.1, where j  1 .
5.2 Downlink power allocation

The eNodeB determines the downlink transmit energy per resource element.
A UE may assume downlink cell-specific RS EPRE is constant across the downlink system bandwidth and constant
across all subframes until different cell-specific RS power information is received. The downlink reference-signal
EPRE can be derived from the downlink reference-signal transmit power given by the parameter referenceSignalPower
provided by higher layers. The downlink reference-signal transmit power is defined as the linear average over the power
contributions (in [W]) of all resource elements that carry cell-specific reference signals within the operating system
bandwidth.
3GPP
Release 10 18 3GPP TS 36.213 V10.0.0 (2010-12)
The ratio of PDSCH EPRE to cell-specific RS EPRE among PDSCH REs (not applicable to PDSCH REs with zero
EPRE) for each OFDM symbol is denoted by either  A or  B according to the OFDM symbol index as given by
Table 5.2-2 and Table 5.2-3. In addition,  A and  B are UE-specific.
For a UE in transmission mode 8 when UE-specific RSs are not present in the PRBs upon which the corresponding
PDSCH is mapped or in transmission modes 1 – 7, the UE may assume that for 16 QAM, 64 QAM, spatial multiplexing
with more than one layer or for PDSCH transmissions associated with the multi-user MIMO transmission scheme,
  A is equal to  power -offset  PA  10 log10 (2) [dB] when the UE receives a PDSCH data transmission
using precoding for transmit diversity with 4 cell-specific antenna ports according to Section 6.3.4.3 of [3];
  A is equal to  power -offset  PA [dB] otherwise
where  power -offset is 0 dB for all PDSCH transmission schemes except multi-user MIMO and where PA is a UE
specific parameter provided by higher layers.
For transmission mode 7, if UE-specific RSs are present in the PRBs upon which the corresponding PDSCH is mapped,
the ratio of PDSCH EPRE to UE-specific RS EPRE within each OFDM symbol containing UE-specific RSs shall be a
constant, and that constant shall be maintained over all the OFDM symbols containing the UE-specific RSs in the
corresponding PRBs. In addition, the UE may assume that for 16QAM or 64QAM, this ratio is 0 dB.
the UE may assume the ratio of PDSCH EPRE to UE-specific RS EPRE within each OFDM symbol containing UE-
specific RSs is 0 dB.
the UE may assume the ratio of PDSCH EPRE to UE-specific RS EPRE within each OFDM symbol containing UE-
specific RS is 0 dB for number of transmission layers less than or equal to two and -3 dB otherwise.
A UE may assume that downlink positioning reference signal EPRE is constant across the positioning reference signal
bandwidth and across all OFDM symbols that contain positioning reference signals in a given positioning reference
signal occasion [10].
If CSI-RS is configured in a serving cell then a UE shall assume downlink CSI-RS EPRE is constant across the
downlink system bandwidth and constant across all subframes.
The cell-specific ratio  B /  A is given by Table 5.2-1 according to cell-specific parameter PB signalled by higher
layers and the number of configured eNodeB cell specific antenna ports.
Table 5.2-1: The cell-specific ratio  B /  A for 1, 2, or 4 cell specific antenna ports
B /  A
PB
One Antenna Port Two and Four Antenna Ports
0 1 5/4
1 4/5 1
2 3/5 3/4
3 2/5 1/2
For PMCH with 16QAM or 64QAM, the UE may assume that the ratio of PMCH EPRE to MBSFN RS EPRE is equal
to 0 dB.
Table 5.2-2: OFDM symbol indices within a slot of a non-MBSFN subframe where the ratio of the
corresponding PDSCH EPRE to the cell-specific RS EPRE is denoted by  A or  B
OFDM symbol indices within a slot where OFDM symbol indices within a slot where
Number of antenna the ratio of the corresponding PDSCH the ratio of the corresponding PDSCH
ports EPRE to the cell-specific RS EPRE is EPRE to the cell-specific RS EPRE is
denoted by  A denoted by  B
Normal cyclic prefix Extended cyclic Normal cyclic prefix Extended cyclic
prefix prefix
3GPP
Release 10 19 3GPP TS 36.213 V10.0.0 (2010-12)
One or two 1, 2, 3, 5, 6 1, 2, 4, 5 0, 4 0, 3
Four 2, 3, 5, 6 2, 4, 5 0, 1, 4 0, 1, 3
Table 5.2-3: OFDM symbol indices within a slot of an MBSFN subframe where the ratio of the
corresponding PDSCH EPRE to the cell-specific RS EPRE is denoted by  A or  B
OFDM symbol indices within a slot where OFDM symbol indices within a slot where
Number of antenna the ratio of the corresponding PDSCH the ratio of the corresponding PDSCH
ports EPRE to the cell-specific RS EPRE is EPRE to the cell-specific RS EPRE is
denoted by  A denoted by  B
Normal cyclic Extended cyclic Normal cyclic Extended cyclic
prefix prefix prefix prefix
ns mod ns mod ns mod ns mod ns mod ns mod ns mod ns mod
2=0 2=1 2=0 2=1 2=0 2=1 2=0 2=1
One or two [1, 2, 3, [0, 1, 2, [1, 2, 3, [0, 1, 2, [0] - [0] -
4, 5, 6] 3, 4, 5, 4, 5] 3, 4, 5]
6]
Four [2, 3, 4, [0, 1, 2, [2, 4, 3, [0, 1, 2, [0, 1] - [0, 1] -
5, 6] 3, 4, 5, 5] 3, 4, 5]
6]
5.2.1 eNodeB Relative Narrowband TX Power restrictions

The determination of reported Relative Narrowband TX Power indication RNTP  n PRB  is defined as follows:
 E A ( n PRB )
0 if ( p)
 RNTPthreshold
 E max_ nom
RNTP ( n PRB )  
1 E A ( n PRB )
if no promise about the upper limit of is made
 ( p)
E max_
 nom
where E A ( nPRB ) is the maximum intended EPRE of UE-specific PDSCH REs in OFDM symbols not containing RS
in this physical resource block on antenna port p in the considered future time interval; nPRB is the physical resource
block number n PRB  0,..., N RB
DL
 1 ; RNTPthreshold takes on one of the following values
RNTPthreshold    ,11,10,9,8,7,6,5,4,3,2,1,0,1,2,3 [dB] and
1
( p)
Pmax 
f
nom 
( p)
E max_ DL
N RB  N SC
RB
( p) RB
where Pmax is the base station maximum output power described in [7], and f , N RB
DL
and N SC are defined in
[3].
6 Random access procedure

Prior to initiation of the non-synchronized physical random access procedure, Layer 1 shall receive the following
information from the higher layers:
1. Random access channel parameters (PRACH configuration and frequency position)
2. Parameters for determining the root sequences and their cyclic shifts in the preamble sequence set for the
primary cell (index to logical root sequence table, cyclic shift ( N CS ), and set type (unrestricted or restricted
set))
3GPP
Release 10 20 3GPP TS 36.213 V10.0.0 (2010-12)
6.1 Physical non-synchronized random access procedure

From the physical layer perspective, the L1 random access procedure encompasses the transmission of random access
preamble and random access response. The remaining messages are scheduled for transmission by the higher layer on
the shared data channel and are not considered part of the L1 random access procedure. A random access channel
occupies 6 resource blocks in a subframe or set of consecutive subframes reserved for random access preamble
transmissions. The eNodeB is not prohibited from scheduling data in the resource blocks reserved for random access
channel preamble transmission.
The following steps are required for the L1 random access procedure:
1. Layer 1 procedure is triggered upon request of a preamble transmission by higher layers.
2. A preamble index, a target preamble received power (PREAMBLE_RECEIVED_TARGET_POWER), a

corresponding RA-RNTI and a PRACH resource are indicated by higher layers as part of the request.
3. A preamble transmission power PPRACH is determined as

PPRACH = min{ PCMAX,c (i ) , PREAMBLE_RECEIVED_TARGET_POWER + PLc }_[dBm], where
PCMAX,c (i ) is the configured UE transmit power defined in [6] for subframe i of the primary cell and PLc
is the downlink pathloss estimate calculated in the UE for the primary cell.
4. A preamble sequence is selected from the preamble sequence set using the preamble index.
5. A single preamble is transmitted using the selected preamble sequence with transmission power P PRACH on the
indicated PRACH resource.
6. Detection of a PDCCH with the indicated RA-RNTI is attempted during a window controlled by higher layers
(see [8], clause 5.1.4). If detected, the corresponding DL-SCH transport block is passed to higher layers. The
higher layers parse the transport block and indicate the 20-bit uplink grant to the physical layer, which is
processed according to section 6.2.
6.1.1 Timing
For the L1 random access procedure, UE’s uplink transmission timing after a random access preamble transmission is
as follows.
a. If a PDCCH with associated RA-RNTI is detected in subframe n, and the corresponding DL-SCH
transport block contains a response to the transmitted preamble sequence, the UE shall, according to
the information in the response, transmit an UL-SCH transport block in the first subframe n  k1 ,
k1  6 , if the UL delay field in section 6.2 is set to zero where n  k1 is the first available UL
subframe for PUSCH transmission. The UE shall postpone the PUSCH transmission to the next
available UL subframe after n  k1 if the field is set to 1.
b. If a random access response is received in subframe n, and the corresponding DL-SCH transport
block does not contain a response to the transmitted preamble sequence, the UE shall, if requested by
higher layers, be ready to transmit a new preamble sequence no later than in subframe n  5 .
c. If no random access response is received in subframe n, where subframe n is the last subframe of the
random access response window, the UE shall, if requested by higher layers, be ready to transmit a
new preamble sequence no later than in subframe n  4 .
In case a random access procedure is initiated by a PDCCH order in subframe n, the UE shall, if requested by higher
layers, transmit random access preamble in the first subframe n  k2 , k2  6 , where a PRACH resource is available.
3GPP
Release 10 21 3GPP TS 36.213 V10.0.0 (2010-12)
6.2 Random Access Response Grant

The higher layers indicate the 20-bit UL Grant to the physical layer, as defined in [8]. This is referred to the Random
Access Response Grant in the physical layer. The content of these 20 bits starting with the MSB and ending with the
LSB are as follows:
- Hopping flag – 1 bit
- Fixed size resource block assignment – 10 bits
- Truncated modulation and coding scheme – 4 bits
- TPC command for scheduled PUSCH – 3 bits
- UL delay – 1 bit
- CQI request – 1 bit
The UE shall perform PUSCH frequency hopping if the single bit frequency hopping (FH) field in a corresponding
Random Access Response Grant is set as 1 and the uplink resource block assignment is type 0, otherwise no PUSCH
frequency hopping is performed. When the hopping flag is set, the UE shall perform PUSCH hopping as indicated via
the fixed size resource block assignment detailed below,
The fixed size resource block assignment field is interpreted as follows:

UL
if N RB  44
Truncate the fixed size resource block assignment to its b least significant bits, where
  UL
b  log 2 N RB  UL
 N RB  
1 / 2 , and interpret the truncated resource block assignment according to the rules for a
regular DCI format 0
else
Insert b most significant bits with value set to ‘0’ after the NUL_hop hopping bits in the fixed size resource block
assignment, where the number of hopping bits NUL_hop is zero when the hopping flag bit is not set to 1, and is defined

 UL
 UL
 
in Table 8.4-1 when the hopping flag bit is set to 1, and b   log 2 N RB  N RB  1 / 2   10  , and interpret the

expanded resource block assignment according to the rules for a regular DCI format 0
end if
The truncated modulation and coding scheme field is interpreted such that the modulation and coding scheme
corresponding to the Random Access Response grant is determined from MCS indices 0 through 15 in Table 8.6.1-1.
The TPC command  msg 2 shall be used for setting the power of the PUSCH, and is interpreted according to Table
6.2-1.
Table 6.2-1: TPC Command  msg 2 for Scheduled PUSCH
TPC Command Value (in dB)

0 -6
1 -4
2 -2
3 0
4 2
5 4
6 6
7 8
In non-contention based random access procedure, the CQI request field is interpreted to determine whether an
aperiodic CQI, PMI, and RI report is included in the corresponding PUSCH transmission according to section 7.2.1. In
contention based random access procedure, the CQI request field is reserved.
3GPP
Release 10 22 3GPP TS 36.213 V10.0.0 (2010-12)
The UL delay applies for both TDD and FDD and this field can be set to 0 or 1 to indicate whether the delay of PUSCH
is introduced as shown in section 6.1.1.
7 Physical downlink shared channel related procedures

For FDD, there shall be a maximum of 8 downlink HARQ processes per serving cell.
For TDD, the maximum number of downlink HARQ processes per serving cell shall be determined by the UL/DL
configuration (Table 4.2-2 of [3]), as indicated in Table 7-1.
The dedicated broadcast HARQ process defined in [8] is not counted as part of the maximum number of HARQ
processes for both FDD and TDD.
Table 7-1: Maximum number of DL HARQ processes for TDD
TDD UL/DL Maximum number of HARQ

configuration processes
0 4
1 7
2 10
3 9
4 12
5 15
6 6
7.1 UE procedure for receiving the physical downlink shared

channel
A UE shall upon detection of a PDCCH of a serving cell with DCI format 1, 1A, 1B, 1C, 1D, 2, 2A, 2B or 2C intended
for the UE in a subframe, decode the corresponding PDSCH in the same subframe with the restriction of the number of
transport blocks defined in the higher layers.
A UE may assume that positioning reference signals are not present in resource blocks in which it shall decode PDSCH
according to a detected PDCCH with CRC scrambled by the SI-RNTI or P-RNTI with DCI format 1A or 1C intended
for the UE.
A UE configured with the carrier indicator field for a given serving cell may assume that the carrier indicator field is not
present in any PDCCH of the serving cell with CRC scrambled by SI-RNTI, P-RNTI, RA-RNTI, Temporary C-RNTI,
TPC-RNTI, SPS C-RNTI or by C-RNTI if located in the common search space that is described in section 9.1.
Otherwise, the configured UE shall assume that for the given serving cell the carrier indicator field is present in
PDCCH located in the UE specific search space described in section 9.1 when the PDCCH CRC is scrambled by C-
RNTI or SPS C-RNTI.
If a UE is configured by higher layers to decode PDCCH with CRC scrambled by the SI-RNTI, the UE shall decode the
PDCCH and the corresponding PDSCH according to any of the combinations defined in Table 7.1-1. The scrambling
initialization of PDSCH corresponding to these PDCCHs is by SI-RNTI.
Table 7.1-1: PDCCH and PDSCH configured by SI-RNTI
DCI format Search Space Transmission scheme of PDSCH corresponding to PDCCH

DCI format 1C Common If the number of PBCH antenna ports is one, Single-antenna
port, port 0 is used, otherwise Transmit diversity.
DCI format 1A Common If the number of PBCH antenna ports is one, Single-antenna
port, port 0 is used, otherwise Transmit diversity
3GPP
Release 10 23 3GPP TS 36.213 V10.0.0 (2010-12)
If a UE is configured by higher layers to decode PDCCH with CRC scrambled by the P-RNTI, the UE shall decode the
PDCCH and the corresponding PDSCH according to any of the combinations defined in Table 7.1-2. The scrambling
initialization of PDSCH corresponding to these PDCCHs is by P-RNTI.
Table 7.1-2: PDCCH and PDSCH configured by P-RNTI

port, port 0 is used (see subclause 7.1.1), otherwise Transmit
diversity (see subclause 7.1.2)
If a UE is configured by higher layers to decode PDCCH with CRC scrambled by the RA-RNTI, the UE shall decode
the PDCCH and the corresponding PDSCH according to any of the combinations defined in Table 7.1-3. The
scrambling initialization of PDSCH corresponding to these PDCCHs is by RA-RNTI.
When RA-RNTI and either C-RNTI or SPS C-RNTI are assigned in the same subframe, UE is not required to decode a
PDSCH indicated by a PDCCH with a CRC scrambled by C-RNTI or SPS C-RNTI.
Table 7.1-3: PDCCH and PDSCH configured by RA-RNTI

The UE is semi-statically configured via higher layer signalling to receive PDSCH data transmissions signalled via
PDCCH according to one of nine transmission modes, denoted mode 1 to mode 9.
For frame structure type 1,
- the UE is not expected to receive PDSCH resource blocks transmitted on antenna port 5 in any subframe in
which the number of OFDM symbols for PDCCH with normal CP is equal to four;
- the UE is not expected to receive PDSCH resource blocks transmitted on antenna port 5, 7, or 8 in the two
PRBs to which a pair of VRBs is mapped if either one of the two PRBs overlaps in frequency with a
transmission of either PBCH or primary or secondary synchronisation signals in the same subframe;
- the UE is not expected to receive PDSCH resource blocks transmitted on antenna port 7 for which
distributed VRB resource allocation is assigned.
- The UE may skip decoding the transport block(s) if it does not receive all assigned PDSCH resource blocks.
If the UE skips decoding, the physical layer indicates to higher layer that the transport block(s) are not
successfully decoded.
For frame structure type 2,
- the UE is not expected to receive PDSCH resource blocks transmitted on antenna port 5 in any subframe in
which the number of OFDM symbols for PDCCH with normal CP is equal to four;
- the UE is not expected to receive PDSCH resource blocks transmitted on antenna port 5 in the two PRBs to
which a pair of VRBs is mapped if either one of the two PRBs overlaps in frequency with a transmission of
PBCH in the same subframe;
- the UE is not expected to receive PDSCH resource blocks transmitted on antenna port 7 or 8 in the two
PRBs to which a pair of VRBs is mapped if either one of the two PRBs overlaps in frequency with a
transmission of primary or secondary synchronisation signals in the same subframe;
3GPP
Release 10 24 3GPP TS 36.213 V10.0.0 (2010-12)
- with normal CP configuration, the UE is not expected to receive PDSCH on antenna port 5 for which
distributed VRB resource allocation is assigned in the special subframe with configuration #1 or #6;
- the UE is not expected to receive PDSCH on antenna port 7 for which distributed VRB resource allocation
is assigned.
- The UE may skip decoding the transport block(s) if it does not receive all assigned PDSCH resource blocks.
If the UE skips decoding, the physical layer indicates to higher layer that the transport block(s) are not
successfully decoded.
If a UE is configured by higher layers to decode PDCCH with CRC scrambled by the C-RNTI, the UE shall decode the
PDCCH and any corresponding PDSCH according to the respective combinations defined in Table 7.1-5. The
scrambling initialization of PDSCH corresponding to these PDCCHs is by C-RNTI.
If the UE is configured with the carrier indicator field for a given serving cell and, if the UE is configured by higher
layers to decode PDCCH with CRC scrambled by the C-RNTI, then the UE shall decode PDSCH of the serving cell
indicated by the carrier indicator field value in the decoded PDCCH.
When a UE configured in transmission mode 3, 4 or 8 receives a DCI Format 1A assignment, it shall assume that the
PDSCH transmission is associated with transport block 1 and that transport block 2 is disabled.
When a UE is configured in transmission mode 7, scrambling initialization of UE-specific reference signals

corresponding to these PDCCHs is by C-RNTI.
The UE does not support transmission mode 8 if extended cyclic prefix is used in the downlink.
3GPP
Release 10 25 3GPP TS 36.213 V10.0.0 (2010-12)
Table 7.1-5: PDCCH and PDSCH configured by C-RNTI
Transmission DCI format Search Space Transmission scheme of PDSCH

mode corresponding to PDCCH
Mode 1 DCI format 1A Common and Single-antenna port, port 0 (see subclause
UE specific by C-RNTI 7.1.1)
DCI format 1 UE specific by C-RNTI Single-antenna port, port 0 (see subclause

7.1.1)
Mode 2 DCI format 1A Common and Transmit diversity (see subclause 7.1.2)
UE specific by C-RNTI
DCI format 1 UE specific by C-RNTI Transmit diversity (see subclause 7.1.2)
DCI format 2A UE specific by C-RNTI Large delay CDD (see subclause 7.1.3) or
Transmit diversity (see subclause 7.1.2)
DCI format 2 UE specific by C-RNTI Closed-loop spatial multiplexing (see
subclause 7.1.4)or Transmit diversity (see
subclause 7.1.2)
DCI format 1D UE specific by C-RNTI Multi-user MIMO (see subclause 7.1.5)
DCI format 1B UE specific by C-RNTI Closed-loop spatial multiplexing (see
subclause 7.1.4) using a single
transmission layer
Mode 7 DCI format 1A Common and If the number of PBCH antenna ports is
UE specific by C-RNTI one, Single-antenna port, port 0 is used
(see subclause 7.1.1), otherwise Transmit
DCI format 1 UE specific by C-RNTI Single-antenna port, port 5 (see subclause
7.1.1)
Mode 8 DCI format 1A Common and If the number of PBCH antenna ports is
UE specific by C-RNTI one, Single-antenna port, port 0 is used
(see subclause 7.1.1), otherwise Transmit
DCI format 2B UE specific by C-RNTI Dual layer transmission, port 7 and 8 (see
subclause 7.1.5A) or single-antenna port,
port 7 or 8 (see subclause 7.1.1)
Mode 9 DCI format 1A Common and Non-MBSFN subframe: If the number of
UE specific by C-RNTI PBCH antenna ports is one, Single-
antenna port, port 0 is used (see subclause
7.1.1), otherwise Transmit diversity (see
subclause 7.1.2)
Signaled MBSFN subframe with unicast
allocation: Single-antenna port, port 7 (see
subclause 7.1.1)
DCI format 2C UE specific by C-RNTI Up to 8 layer transmission, ports 7-14 (see
subclause 7.1.5B)
If a UE is configured by higher layers to decode PDCCH with CRC scrambled by the SPS C-RNTI, the UE shall
decode the PDCCH on the primary cell and any corresponding PDSCH on the primary cell according to the respective
combinations defined in Table 7.1-6. The same PDSCH related configuration applies in the case that a PDSCH is
transmitted without a corresponding PDCCH. The scrambling initialization of PDSCH corresponding to these PDCCHs
and PDSCH without a corresponding PDCCH is by SPS C-RNTI.
When a UE is configured in transmission mode 7, scrambling initialization of UE-specific reference signals

corresponding to these PDCCHs is by SPS C-RNTI.
3GPP
Release 10 26 3GPP TS 36.213 V10.0.0 (2010-12)
Table 7.1-6: PDCCH and PDSCH configured by SPS C-RNTI
Transmission DCI format Search Space Transmission scheme of PDSCH

Mode 1 DCI format 1A Common and Single-antenna port, port 0 (see
UE specific by C-RNTI subclause 7.1.1)
DCI format 1 UE specific by C-RNTI Single-antenna port, port 0 (see

subclause 7.1.1)
DCI format 2A UE specific by C-RNTI Transmit diversity (see subclause 7.1.2)
DCI format 1 UE specific by C-RNTI Single-antenna port, port 5 (see
subclause 7.1.1)
Mode 8 DCI format 1A Common and Single-antenna port, port 7(see
DCI format 2B UE specific by C-RNTI Single-antenna port, port 7 or 8 (see
subclause 7.1.1)
DCI format 2C UE specific by C-RNTI Single-antenna port, port 7 or 8, (see
subclause 7.1.1)
If a UE is configured by higher layers to decode PDCCH with CRC scrambled by the Temporary C-RNTI and is not
configured to decode PDCCH with CRC scrambled by the C-RNTI, the UE shall decode the PDCCH and the
corresponding PDSCH according to the combination defined in Table 7.1-7. The scrambling initialization of PDSCH
corresponding to these PDCCHs is by Temporary C-RNTI.
Table 7.1-7: PDCCH and PDSCH configured by Temporary C-RNTI

DCI format 1A Common and UE If the number of PBCH antenna port is one, Single-antenna
specific by Temporary C- port, port 0 is used (see subclause 7.1.1), otherwise Transmit
RNTI diversity (see subclause 7.1.2)
DCI format 1 UE specific by If the number of PBCH antenna port is one, Single-antenna
Temporary C-RNTI port, port 0 is used (see subclause 7.1.1), otherwise Transmit
The transmission schemes of the PDSCH are described in the following sub-clauses.
7.1.1 Single-antenna port scheme

For the single-antenna port transmission schemes (port 0, port 5, port 7 or port 8) of the PDSCH, the UE may assume
that an eNB transmission on the PDSCH would be performed according to Section 6.3.4.1 of [3].
In case an antenna port p  {7,8} is used, the UE cannot assume that the other antenna port in the set {7,8} is not
associated with transmission of PDSCH to another UE.
3GPP
Release 10 27 3GPP TS 36.213 V10.0.0 (2010-12)
7.1.2 Transmit diversity scheme

For the transmit diversity transmission scheme of the PDSCH, the UE may assume that an eNB transmission on the
PDSCH would be performed according to Section 6.3.4.3 of [3]
7.1.3 Large delay CDD scheme

For the large delay CDD transmission scheme of the PDSCH, the UE may assume that an eNB transmission on the
PDSCH would be performed according to large delay CDD as defined in Section 6.3.4.2.2 of [3].
7.1.4 Closed-loop spatial multiplexing scheme

For the closed-loop spatial multiplexing transmission scheme of the PDSCH, the UE may assume that an eNB
transmission on the PDSCH would be performed according to the applicable number of transmission layers as defined
in Section 6.3.4.2.1 of [3].
7.1.5 Multi-user MIMO scheme

For the multi-user MIMO transmission scheme of the PDSCH, the UE may assume that an eNB transmission on the
PDSCH would be performed on one layer and according to Section 6.3.4.2.1 of [3]. The  power-offset dB value
signalled on PDCCH with DCI format 1D using the downlink power offset field is given in Table 7.1.5-1.
Table 7.1.5-1: Mapping of downlink power offset field in DCI format 1D to the  power -offset value.
Downlink power offset field  power-offset [dB]

0 -10log10(2)
1 0
7.1.5A Dual layer scheme

For the dual layer transmission scheme of the PDSCH, the UE may assume that an eNB transmission on the PDSCH
would be performed with two transmission layers on antenna ports 7 and 8 as defined in Section 6.3.4.4 of [3].
7.1.5B Up to 8 layer transmission

For the 8 layer transmission scheme of the PDSCH, the UE may assume that an eNB transmission on the PDSCH would
be performed with up to 8 transmission layers on antenna ports 7 - 14 as defined in Section 6.3.4.4 of [3].
7.1.6 Resource allocation

The UE shall interpret the resource allocation field depending on the PDCCH DCI format detected. A resource
allocation field in each PDCCH includes two parts, a resource allocation header field and information consisting of the
actual resource block assignment. PDCCH DCI formats 1, 2, 2A, 2B and 2C with type 0 and PDCCH DCI formats 1, 2,
2A and 2B with type 1 resource allocation have the same format and are distinguished from each other via the single bit
resource allocation header field which exists depending on the downlink system bandwidth (section 5.3.3.1 of [4]),
where type 0 is indicated by 0 value and type 1 is indicated otherwise. PDCCH with DCI format 1A, 1B, 1C and 1D
have a type 2 resource allocation while PDCCH with DCI format 1, 2, 2A, 2B and 2C have type 0 or type 1 resource
allocation. PDCCH DCI formats with a type 2 resource allocation do not have a resource allocation header field.
7.1.6.1 Resource allocation type 0

In resource allocations of type 0, resource block assignment information includes a bitmap indicating the resource block
groups (RBGs) that are allocated to the scheduled UE where a RBG is a set of consecutive virtual resource blocks
(VRBs) of localized type as defined in section 6.2.3.1 of [3]. Resource block group size (P) is a function of the system
3GPP
Release 10 28 3GPP TS 36.213 V10.0.0 (2010-12)
DL
bandwidth as shown in Table 7.1.6.1-1. The total number of RBGs ( N RBG ) for downlink system bandwidth of N RB
is given by N RBG   N RB / P  where  N RB / P  of the RBGs are of size P and if N RB mod P  0 then one of the
DL DL DL
DL
RBGs is of size N RB DL
 P  N RB 
/ P . The bitmap is of size N RBG bits with one bitmap bit per RBG such that each
RBG is addressable. The RBGs shall be indexed in the order of increasing frequency and non-increasing RBG sizes
starting at the lowest frequency. The order of RBG to bitmap bit mapping is in such way that RBG 0 to RBG
N RBG  1 are mapped to MSB to LSB of the bitmap. The RBG is allocated to the UE if the corresponding bit value in
the bitmap is 1, the RBG is not allocated to the UE otherwise.
Table 7.1.6.1-1: Type 0 Resource Allocation RBG Size vs. Downlink System Bandwidth
System Bandwidth RBG Size

DL
N RB (P)
≤10 1
11 – 26 2
27 – 63 3
64 – 110 4

In resource allocations of type 1, a resource block assignment information of size N RBG indicates to a scheduled UE
the VRBs from the set of VRBs from one of P RBG subsets. The virtual resource blocks used are of localized type as
defined in section 6.2.3.1 of [3]. Also P is the RBG size associated with the system bandwidth as shown in Table 7.1.6.1-
1. A RBG subset p , where 0  p  P , consists of every P th RBG starting from RBG p . The resource block
assignment information consists of three fields [4].
The first field with  log 2 ( P )  bits is used to indicate the selected RBG subset among P RBG subsets.
The second field with one bit is used to indicate a shift of the resource allocation span within a subset. A bit value of 1
indicates shift is triggered. Shift is not triggered otherwise.
The third field includes a bitmap, where each bit of the bitmap addresses a single VRB in the selected RBG subset in
such a way that MSB to LSB of the bitmap are mapped to the VRBs in the increasing frequency order. The VRB is
allocated to the UE if the corresponding bit value in the bit field is 1, the VRB is not allocated to the UE otherwise. The
TYPE1
portion of the bitmap used to address VRBs in a selected RBG subset has size N RB and is defined as
TYPE1
N RB DL
 N RB /P    log 2 ( P )  1
The addressable VRB numbers of a selected RBG subset start from an offset,  shift ( p ) to the smallest VRB number
within the selected RBG subset, which is mapped to the MSB of the bitmap. The offset is in terms of the number of
VRBs and is done within the selected RBG subset. If the value of the bit in the second field for shift of the resource
allocation span is set to 0, the offset for RBG subset p is given by  shift ( p )  0 . Otherwise, the offset for RBG
subset p is given by  shift ( p )  N RB
RBG subset
( p )  N RB
TYPE1
, where the LSB of the bitmap is justified with the
highest VRB number within the selected RBG subset. N RB RBG subset
( p ) is the number of VRBs in RBG subset p and
can be calculated by the following equation,
3GPP
Release 10 29 3GPP TS 36.213 V10.0.0 (2010-12)
  N DL  1   N DL  1 
  RB 2   P  P , p   RB  mod P
 P   P 
 DL
RBG subset  N 1 DL
 N DL  1 
N RB ( p )    RB 2   P  ( N RB  1) mod P  1 , p   RB  mod P
  P 
  P 
 DL
  N RB  1   P  N DL  1 
, p   RB
 P 2   mod P
    P 
Consequently, when RBG subset p is indicated, bit i for i  0,1, , N RB

TYPE1
 1 in the bitmap field indicates VRB
number,
 i  shift ( p )  2
 P  p  P   i  shift ( p )  mod P .
RBG subset
nVRB ( p)  
 P 

In resource allocations of type 2, the resource block assignment information indicates to a scheduled UE a set of
contiguously allocated localized virtual resource blocks or distributed virtual resource blocks. In case of resource
allocation signalled with PDCCH DCI format 1A, 1B or 1D, one bit flag indicates whether localized virtual resource
blocks or distributed virtual resource blocks are assigned (value 0 indicates Localized and value 1 indicates Distributed
VRB assignment) while distributed virtual resource blocks are always assigned in case of resource allocation signalled
with PDCCH DCI format 1C. Localized VRB allocations for a UE vary from a single VRB up to a maximum number
of VRBs spanning the system bandwidth. For DCI format 1A the distributed VRB allocations for a UE vary from a
DL DL
single VRB up to N VRB VRBs, where N VRB is defined in [3], if the DCI CRC is scrambled by P-RNTI, RA-
RNTI, or SI-RNTI. With PDCCH DCI format 1B, 1D, or 1A with a CRC scrambled with C-RNTI, distributed VRB
DL DL
allocations for a UE vary from a single VRB up to N VRB VRBs if N RB is 6-49 and vary from a single VRB up to
DL step
16 if N RB is 50-110. With PDCCH DCI format 1C, distributed VRB allocations for a UE vary from N RB VRB(s)
up to  N VRB
DL step
/ N RB   N RBstep VRBs with an increment step of N step
RB
step
, where N RB value is determined depending
on the downlink system bandwidth as shown in Table 7.1.6.3-1.
step
Table 7.1.6.3-1: N RB values vs. Downlink System Bandwidth
System BW ( step
N RB
DL
N RB )
DCI format 1C
6-49 2
50-110 4
For PDCCH DCI format 1A, 1B or 1D, a type 2 resource allocation field consists of a resource indication value (RIV)
corresponding to a starting resource block ( RB start ) and a length in terms of virtually contiguously allocated resource
blocks LCRBs . The resource indication value is defined by
if ( LCRBs  1)   N RB
DL
/ 2 then
RIV  N RB
DL
( LCRBs  1)  RBstart
3GPP
Release 10 30 3GPP TS 36.213 V10.0.0 (2010-12)
else
RIV  N RB
DL DL
( N RB  LCRBs  1)  ( N RB
DL
 1  RBstart )
where LCRBs  1 and shall not exceed N VRB  RBstart .

DL
For PDCCH DCI format 1C, a type 2 resource block assignment field consists of a resource indication value (RIV)
step
corresponding to a starting resource block ( RB start = 0 , N RB step
, 2N RB ,…, (  N VRB
DL step
/ N RB   1) N RBstep ) and a
step step
length in terms of virtually contiguously allocated resource blocks ( LCRBs = N RB , 2N RB ,…,
 N VRB
DL step
/ N RB   N RBstep ). The resource indication value is defined by

if ( LCRBs  1)   NVRB
 DL / 2 then
 DL ( LCRBs
RIV  N VRB  
 1)  RBstart
else
 DL ( NVRB
RIV  NVRB  DL  LCRBs
  DL  1  RBstart
 1)  ( NVRB  )

where LCRBs  LCRBs / N RB
step
  RBstart / N RB
, RBstart
step
and  DL   N VRB
NVRB DL step
/ N RB  . Here,

LCRBs  DL  RBstart
 1 and shall not exceed N VRB  .
7.1.6.4 PDSCH starting position

The starting OFDM symbol for the PDSCH of each activated serving cell given by index .l DataStart in the first of the
slots in a subframe is given by
− the higher-layer parameter pdsch-Start for the serving cell on which PDSCH is received if the UE is configured
with carrier indicator field for the given serving cell and if PDSCH and the corresponding PDCCH are received
on different serving cells,
− the span of the DCI given by the CFI of the serving cell according to Section 5.3.4 of [4] otherwise.
7.1.6.5 PRB bundling

A UE configured for transmission mode 9 for a given serving cell c may assume that precoding granularity is multiple
resource blocks in the frequency domain when [if] PMI/RI feedback is configured. Fixed system bandwidth dependent
Precoding Resource block Groups (PRGs) of size P  partition the system bandwidth and each PRG consists of
consecutive PRBs. If N RB DL DL
mod P   0 then one of the PRGs is of size N RB DL
 P N RB  
/ P  . The PRG size is
non-increasing starting at the lowest frequency. The UE may always assume that the same precoder applies on all
scheduled PRBs within a PRG.
The PRG size a UE may assume for a given system bandwidth is given by:
Table 7.1.6.5-1
DL
System Bandwidth ( N RB ) PRG Size ( P  )
(PRBs)
≤10 1
11 – 26 2
27 – 63 3
64 – 110 2
3GPP
Release 10 31 3GPP TS 36.213 V10.0.0 (2010-12)
7.1.7 Modulation order and transport block size determination

To determine the modulation order and transport block size(s) in the physical downlink shared channel, the UE shall
first
− read the 5-bit “modulation and coding scheme” field ( I MCS ) in the DCI
and second if the DCI CRC is scrambled by P-RNTI, RA-RNTI, or SI-RNTI then
− for DCI format 1A:
1A
o set the Table 7.1.7.2.1-1 column indicator N PRB to N PRB from Section 5.3.3.1.3 in [4]
− for DCI format 1C:
o use Table 7.1.7.2.3-1 for determining its transport block size.
else
 to the total number of allocated PRBs based on the procedure defined in Section 7.1.6.
− set N PRB
if the transport block is transmitted in DwPTS of the special subframe in frame structure type 2, then
set the Table 7.1.7.2.1-1 column indicator    0.75 , 1 ,

N PRB  max  N PRB 
else, set the Table 7.1.7.2.1-1 column indicator  .
N PRB  N PRB
The UE may skip decoding a transport block in an initial transmission if the effective channel code rate is higher than
0.930, where the effective channel code rate is defined as the number of downlink information bits (including CRC bits)
divided by the number of physical channel bits on PDSCH. If the UE skips decoding, the physical layer indicates to
higher layer that the transport block is not successfully decoded. For the special subframe configurations 0 and 5 with
normal downlink CP or configurations 0 and 4 with extended downlink CP, shown in Table 4.2-1 of [3], there shall be
no PDSCH transmission in DwPTS of the special subframe.
7.1.7.1 Modulation order determination

The UE shall use Q m = 2 if the DCI CRC is scrambled by P-RNTI, RA-RNTI, or SI-RNTI, otherwise, the UE shall
use I MCS and Table 7.1.7.1-1 to determine the modulation order ( Q m ) used in the physical downlink shared channel.
Table 7.1.7.1-1: Modulation and TBS index table for PDSCH
MCS Index Modulation Order TBS Index

I MCS Qm I TBS
0 2 0
1 2 1
2 2 2
3 2 3
4 2 4
5 2 5
6 2 6
7 2 7
8 2 8
9 2 9
10 4 9
11 4 10
12 4 11
13 4 12
14 4 13
15 4 14
16 4 15
3GPP
Release 10 32 3GPP TS 36.213 V10.0.0 (2010-12)
17 6 15
18 6 16
19 6 17
20 6 18
21 6 19
22 6 20
23 6 21
24 6 22
25 6 23
26 6 24
27 6 25
28 6 26
29 2
30 4 reserved
31 6
7.1.7.2 Transport block size determination

If the DCI CRC is scrambled by P-RNTI, RA-RNTI, or SI-RNTI then
− for DCI format 1A:
o the UE shall set the TBS index ( I TBS ) equal to I MCS and determine its TBS by the procedure in
Section 7.1.7.2.1.
− for DCI format 1C:
o the UE shall set the TBS index ( I TBS ) equal to I MCS and determine its TBS from Table 7.1.7.2.3-
1.
else
 for 0  I MCS  28 , the UE shall first determine the TBS index ( I TBS ) using I MCS and Table 7.1.7.1-1
except if the transport block is disabled in DCI formats 2, 2A, 2B and 2C as specified below. For a transport
block that is not mapped to more than single-layer spatial multiplexing, the TBS is determined by the procedure
in Section 7.1.7.2.1. For a transport block that is mapped to two-layer spatial multiplexing, the TBS is
determined by the procedure in Section 7.1.7.2.2. For a transport block that is mapped to three-layer spatial
multiplexing, the TBS is determined by the procedure in Section 7.1.7.2.4. For a transport block that is mapped
to four-layer spatial multiplexing, the TBS is determined by the procedure in Section 7.1.7.2.5.
 for 29  I MCS  31 , the TBS is assumed to be as determined from DCI transported in the latest PDCCH for
the same transport block using 0  I MCS  28 . If there is no PDCCH for the same transport block using
0  I MCS  28 , and if the initial PDSCH for the same transport block is semi-persistently scheduled, the TBS
shall be determined from the most recent semi-persistent scheduling assignment PDCCH.
 In DCI formats 2, 2A, 2B and 2C a transport block is disabled if I MCS  0 and if rvidx = 1 otherwise the
transport block is enabled.
The NDI and HARQ process ID, as signalled on PDCCH, and the TBS, as determined above, shall be delivered to
higher layers.
7.1.7.2.1 Transport blocks not mapped to two-layer spatial multiplexing

For 1  N PRB  110 , the TBS is given by the ( I TBS , N PRB ) entry of Table 7.1.7.2.1-1.
Table 7.1.7.2.1-1: Transport block size table (dimension 27×110)
I TBS N PRB
3GPP
Release 10 33 3GPP TS 36.213 V10.0.0 (2010-12)
1 2 3 4 5 6 7 8 9 10
0 16 32 56 88 120 152 176 208 224 256
1 24 56 88 144 176 208 224 256 328 344
2 32 72 144 176 208 256 296 328 376 424
3 40 104 176 208 256 328 392 440 504 568
4 56 120 208 256 328 408 488 552 632 696
5 72 144 224 328 424 504 600 680 776 872
6 328 176 256 392 504 600 712 808 936 1032
7 104 224 328 472 584 712 840 968 1096 1224
8 120 256 392 536 680 808 968 1096 1256 1384
9 136 296 456 616 776 936 1096 1256 1416 1544
10 144 328 504 680 872 1032 1224 1384 1544 1736
11 176 376 584 776 1000 1192 1384 1608 1800 2024
12 208 440 680 904 1128 1352 1608 1800 2024 2280
13 224 488 744 1000 1256 1544 1800 2024 2280 2536
14 256 552 840 1128 1416 1736 1992 2280 2600 2856
15 280 600 904 1224 1544 1800 2152 2472 2728 3112
16 328 632 968 1288 1608 1928 2280 2600 2984 3240
17 336 696 1064 1416 1800 2152 2536 2856 3240 3624
18 376 776 1160 1544 1992 2344 2792 3112 3624 4008
19 408 840 1288 1736 2152 2600 2984 3496 3880 4264
20 440 904 1384 1864 2344 2792 3240 3752 4136 4584
21 488 1000 1480 1992 2472 2984 3496 4008 4584 4968
22 520 1064 1608 2152 2664 3240 3752 4264 4776 5352
23 552 1128 1736 2280 2856 3496 4008 4584 5160 5736
24 584 1192 1800 2408 2984 3624 4264 4968 5544 5992
25 616 1256 1864 2536 3112 3752 4392 5160 5736 6200
26 712 1480 2216 2984 3752 4392 5160 5992 6712 7480
N PRB
I TBS
11 12 13 14 15 16 17 18 19 20
0 288 328 344 376 392 424 456 488 504 536
1 376 424 456 488 520 568 600 632 680 712
2 472 520 568 616 648 696 744 776 840 872
3 616 680 744 808 872 904 968 1032 1096 1160
4 776 840 904 1000 1064 1128 1192 1288 1352 1416
5 968 1032 1128 1224 1320 1384 1480 1544 1672 1736
6 1128 1224 1352 1480 1544 1672 1736 1864 1992 2088
7 1320 1480 1608 1672 1800 1928 2088 2216 2344 2472
8 1544 1672 1800 1928 2088 2216 2344 2536 2664 2792
9 1736 1864 2024 2216 2344 2536 2664 2856 2984 3112
10 1928 2088 2280 2472 2664 2792 2984 3112 3368 3496
11 2216 2408 2600 2792 2984 3240 3496 3624 3880 4008
12 2472 2728 2984 3240 3368 3624 3880 4136 4392 4584
13 2856 3112 3368 3624 3880 4136 4392 4584 4968 5160
14 3112 3496 3752 4008 4264 4584 4968 5160 5544 5736
15 3368 3624 4008 4264 4584 4968 5160 5544 5736 6200
16 3624 3880 4264 4584 4968 5160 5544 5992 6200 6456
17 4008 4392 4776 5160 5352 5736 6200 6456 6712 7224
18 4392 4776 5160 5544 5992 6200 6712 7224 7480 7992
19 4776 5160 5544 5992 6456 6968 7224 7736 8248 8504
20 5160 5544 5992 6456 6968 7480 7992 8248 8760 9144
21 5544 5992 6456 6968 7480 7992 8504 9144 9528 9912
22 5992 6456 6968 7480 7992 8504 9144 9528 10296 10680
23 6200 6968 7480 7992 8504 9144 9912 10296 11064 11448
24 6712 7224 7992 8504 9144 9912 10296 11064 11448 12216
25 6968 7480 8248 8760 9528 10296 10680 11448 12216 12576
26 8248 8760 9528 10296 11064 11832 12576 13536 14112 14688
3GPP
Release 10 34 3GPP TS 36.213 V10.0.0 (2010-12)
N PRB
I TBS
21 22 23 24 25 26 27 28 29 30
0 568 600 616 648 680 712 744 776 776 808
1 744 776 808 872 904 936 968 1000 1032 1064
2 936 968 1000 1064 1096 1160 1192 1256 1288 1320
3 1224 1256 1320 1384 1416 1480 1544 1608 1672 1736
4 1480 1544 1608 1736 1800 1864 1928 1992 2088 2152
5 1864 1928 2024 2088 2216 2280 2344 2472 2536 2664
6 2216 2280 2408 2472 2600 2728 2792 2984 2984 3112
7 2536 2664 2792 2984 3112 3240 3368 3368 3496 3624
8 2984 3112 3240 3368 3496 3624 3752 3880 4008 4264
9 3368 3496 3624 3752 4008 4136 4264 4392 4584 4776
10 3752 3880 4008 4264 4392 4584 4776 4968 5160 5352
11 4264 4392 4584 4776 4968 5352 5544 5736 5992 5992
12 4776 4968 5352 5544 5736 5992 6200 6456 6712 6712
13 5352 5736 5992 6200 6456 6712 6968 7224 7480 7736
14 5992 6200 6456 6968 7224 7480 7736 7992 8248 8504
15 6456 6712 6968 7224 7736 7992 8248 8504 8760 9144
16 6712 7224 7480 7736 7992 8504 8760 9144 9528 9912
17 7480 7992 8248 8760 9144 9528 9912 10296 10296 10680
18 8248 8760 9144 9528 9912 10296 10680 11064 11448 11832
19 9144 9528 9912 10296 10680 11064 11448 12216 12576 12960
20 9912 10296 10680 11064 11448 12216 12576 12960 13536 14112
21 10680 11064 11448 12216 12576 12960 13536 14112 14688 15264
22 11448 11832 12576 12960 13536 14112 14688 15264 15840 16416
23 12216 12576 12960 13536 14112 14688 15264 15840 16416 16992
24 12960 13536 14112 14688 15264 15840 16416 16992 17568 18336
25 13536 14112 14688 15264 15840 16416 16992 17568 18336 19080
26 15264 16416 16992 17568 18336 19080 19848 20616 21384 22152
N PRB
I TBS
31 32 33 34 35 36 37 38 39 40
0 840 872 904 936 968 1000 1032 1032 1064 1096
1 1128 1160 1192 1224 1256 1288 1352 1384 1416 1416
2 1384 1416 1480 1544 1544 1608 1672 1672 1736 1800
3 1800 1864 1928 1992 2024 2088 2152 2216 2280 2344
4 2216 2280 2344 2408 2472 2600 2664 2728 2792 2856
5 2728 2792 2856 2984 3112 3112 3240 3368 3496 3496
6 3240 3368 3496 3496 3624 3752 3880 4008 4136 4136
7 3752 3880 4008 4136 4264 4392 4584 4584 4776 4968
8 4392 4584 4584 4776 4968 4968 5160 5352 5544 5544
9 4968 5160 5160 5352 5544 5736 5736 5992 6200 6200
10 5544 5736 5736 5992 6200 6200 6456 6712 6712 6968
11 6200 6456 6712 6968 6968 7224 7480 7736 7736 7992
12 6968 7224 7480 7736 7992 8248 8504 8760 8760 9144
13 7992 8248 8504 8760 9144 9144 9528 9912 9912 10296
14 8760 9144 9528 9912 9912 10296 10680 11064 11064 11448
15 9528 9912 10296 10296 10680 11064 11448 11832 11832 12216
16 9912 10296 10680 11064 11448 11832 12216 12216 12576 12960
17 11064 11448 11832 12216 12576 12960 13536 13536 14112 14688
18 12216 12576 12960 13536 14112 14112 14688 15264 15264 15840
19 13536 13536 14112 14688 15264 15264 15840 16416 16992 16992
20 14688 14688 15264 15840 16416 16992 16992 17568 18336 18336
21 15840 15840 16416 16992 17568 18336 18336 19080 19848 19848
22 16992 16992 17568 18336 19080 19080 19848 20616 21384 21384
23 17568 18336 19080 19848 19848 20616 21384 22152 22152 22920
24 19080 19848 19848 20616 21384 22152 22920 22920 23688 24496
25 19848 20616 20616 21384 22152 22920 23688 24496 24496 25456
3GPP
Release 10 35 3GPP TS 36.213 V10.0.0 (2010-12)
26 22920 23688 24496 25456 25456 26416 27376 28336 29296 29296
N PRB
I TBS
41 42 43 44 45 46 47 48 49 50
0 1128 1160 1192 1224 1256 1256 1288 1320 1352 1384
1 1480 1544 1544 1608 1608 1672 1736 1736 1800 1800
2 1800 1864 1928 1992 2024 2088 2088 2152 2216 2216
3 2408 2472 2536 2536 2600 2664 2728 2792 2856 2856
4 2984 2984 3112 3112 3240 3240 3368 3496 3496 3624
5 3624 3752 3752 3880 4008 4008 4136 4264 4392 4392
6 4264 4392 4584 4584 4776 4776 4968 4968 5160 5160
7 4968 5160 5352 5352 5544 5736 5736 5992 5992 6200
8 5736 5992 5992 6200 6200 6456 6456 6712 6968 6968
9 6456 6712 6712 6968 6968 7224 7480 7480 7736 7992
10 7224 7480 7480 7736 7992 7992 8248 8504 8504 8760
11 8248 8504 8760 8760 9144 9144 9528 9528 9912 9912
12 9528 9528 9912 9912 10296 10680 10680 11064 11064 11448
13 10680 10680 11064 11448 11448 11832 12216 12216 12576 12960
14 11832 12216 12216 12576 12960 12960 13536 13536 14112 14112
15 12576 12960 12960 13536 13536 14112 14688 14688 15264 15264
16 13536 13536 14112 14112 14688 14688 15264 15840 15840 16416
17 14688 15264 15264 15840 16416 16416 16992 17568 17568 18336
18 16416 16416 16992 17568 17568 18336 18336 19080 19080 19848
19 17568 18336 18336 19080 19080 19848 20616 20616 21384 21384
20 19080 19848 19848 20616 20616 21384 22152 22152 22920 22920
21 20616 21384 21384 22152 22920 22920 23688 24496 24496 25456
22 22152 22920 22920 23688 24496 24496 25456 25456 26416 27376
23 23688 24496 24496 25456 25456 26416 27376 27376 28336 28336
24 25456 25456 26416 26416 27376 28336 28336 29296 29296 30576
25 26416 26416 27376 28336 28336 29296 29296 30576 31704 31704
26 30576 30576 31704 32856 32856 34008 35160 35160 36696 36696
N PRB
I TBS
51 52 53 54 55 56 57 58 59 60
0 1416 1416 1480 1480 1544 1544 1608 1608 1608 1672
1 1864 1864 1928 1992 1992 2024 2088 2088 2152 2152
2 2280 2344 2344 2408 2472 2536 2536 2600 2664 2664
3 2984 2984 3112 3112 3240 3240 3368 3368 3496 3496
4 3624 3752 3752 3880 4008 4008 4136 4136 4264 4264
5 4584 4584 4776 4776 4776 4968 4968 5160 5160 5352
6 5352 5352 5544 5736 5736 5992 5992 5992 6200 6200
7 6200 6456 6456 6712 6712 6712 6968 6968 7224 7224
8 7224 7224 7480 7480 7736 7736 7992 7992 8248 8504
9 7992 8248 8248 8504 8760 8760 9144 9144 9144 9528
10 9144 9144 9144 9528 9528 9912 9912 10296 10296 10680
11 10296 10680 10680 11064 11064 11448 11448 11832 11832 12216
12 11832 11832 12216 12216 12576 12576 12960 12960 13536 13536
13 12960 13536 13536 14112 14112 14688 14688 14688 15264 15264
14 14688 14688 15264 15264 15840 15840 16416 16416 16992 16992
15 15840 15840 16416 16416 16992 16992 17568 17568 18336 18336
16 16416 16992 16992 17568 17568 18336 18336 19080 19080 19848
17 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
18 19848 20616 21384 21384 22152 22152 22920 22920 23688 23688
19 22152 22152 22920 22920 23688 24496 24496 25456 25456 25456
20 23688 24496 24496 25456 25456 26416 26416 27376 27376 28336
21 25456 26416 26416 27376 27376 28336 28336 29296 29296 30576
22 27376 28336 28336 29296 29296 30576 30576 31704 31704 32856
23 29296 29296 30576 30576 31704 31704 32856 32856 34008 34008
24 31704 31704 32856 32856 34008 34008 35160 35160 36696 36696
3GPP
Release 10 36 3GPP TS 36.213 V10.0.0 (2010-12)
25 32856 32856 34008 34008 35160 35160 36696 36696 37888 37888
26 37888 37888 39232 40576 40576 40576 42368 42368 43816 43816
N PRB
I TBS
61 62 63 64 65 66 67 68 69 70
0 1672 1736 1736 1800 1800 1800 1864 1864 1928 1928
1 2216 2280 2280 2344 2344 2408 2472 2472 2536 2536
2 2728 2792 2856 2856 2856 2984 2984 3112 3112 3112
3 3624 3624 3624 3752 3752 3880 3880 4008 4008 4136
4 4392 4392 4584 4584 4584 4776 4776 4968 4968 4968
5 5352 5544 5544 5736 5736 5736 5992 5992 5992 6200
6 6456 6456 6456 6712 6712 6968 6968 6968 7224 7224
7 7480 7480 7736 7736 7992 7992 8248 8248 8504 8504
8 8504 8760 8760 9144 9144 9144 9528 9528 9528 9912
9 9528 9912 9912 10296 10296 10296 10680 10680 11064 11064
10 10680 11064 11064 11448 11448 11448 11832 11832 12216 12216
11 12216 12576 12576 12960 12960 13536 13536 13536 14112 14112
12 14112 14112 14112 14688 14688 15264 15264 15264 15840 15840
13 15840 15840 16416 16416 16992 16992 16992 17568 17568 18336
14 17568 17568 18336 18336 18336 19080 19080 19848 19848 19848
15 18336 19080 19080 19848 19848 20616 20616 20616 21384 21384
16 19848 19848 20616 20616 21384 21384 22152 22152 22152 22920
17 22152 22152 22920 22920 23688 23688 24496 24496 24496 25456
18 24496 24496 24496 25456 25456 26416 26416 27376 27376 27376
19 26416 26416 27376 27376 28336 28336 29296 29296 29296 30576
20 28336 29296 29296 29296 30576 30576 31704 31704 31704 32856
21 30576 31704 31704 31704 32856 32856 34008 34008 35160 35160
22 32856 34008 34008 34008 35160 35160 36696 36696 36696 37888
23 35160 35160 36696 36696 37888 37888 37888 39232 39232 40576
24 36696 37888 37888 39232 39232 40576 40576 42368 42368 42368
25 39232 39232 40576 40576 40576 42368 42368 43816 43816 43816
26 45352 45352 46888 46888 48936 48936 48936 51024 51024 52752
N PRB
I TBS
71 72 73 74 75 76 77 78 79 80
0 1992 1992 2024 2088 2088 2088 2152 2152 2216 2216
1 2600 2600 2664 2728 2728 2792 2792 2856 2856 2856
2 3240 3240 3240 3368 3368 3368 3496 3496 3496 3624
3 4136 4264 4264 4392 4392 4392 4584 4584 4584 4776
4 5160 5160 5160 5352 5352 5544 5544 5544 5736 5736
5 6200 6200 6456 6456 6712 6712 6712 6968 6968 6968
6 7480 7480 7736 7736 7736 7992 7992 8248 8248 8248
7 8760 8760 8760 9144 9144 9144 9528 9528 9528 9912
8 9912 9912 10296 10296 10680 10680 10680 11064 11064 11064
9 11064 11448 11448 11832 11832 11832 12216 12216 12576 12576
10 12576 12576 12960 12960 12960 13536 13536 13536 14112 14112
11 14112 14688 14688 14688 15264 15264 15840 15840 15840 16416
12 16416 16416 16416 16992 16992 17568 17568 17568 18336 18336
13 18336 18336 19080 19080 19080 19848 19848 19848 20616 20616
14 20616 20616 20616 21384 21384 22152 22152 22152 22920 22920
15 22152 22152 22152 22920 22920 23688 23688 23688 24496 24496
16 22920 23688 23688 24496 24496 24496 25456 25456 25456 26416
17 25456 26416 26416 26416 27376 27376 27376 28336 28336 29296
18 28336 28336 29296 29296 29296 30576 30576 30576 31704 31704
19 30576 30576 31704 31704 32856 32856 32856 34008 34008 34008
20 32856 34008 34008 34008 35160 35160 35160 36696 36696 36696
21 35160 36696 36696 36696 37888 37888 39232 39232 39232 40576
22 37888 39232 39232 40576 40576 40576 42368 42368 42368 43816
23 40576 40576 42368 42368 43816 43816 43816 45352 45352 45352
3GPP
Release 10 37 3GPP TS 36.213 V10.0.0 (2010-12)
24 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
25 45352 45352 46888 46888 46888 48936 48936 48936 51024 51024
26 52752 52752 55056 55056 55056 55056 57336 57336 57336 59256
N PRB
I TBS
81 82 83 84 85 86 87 88 89 90
0 2280 2280 2280 2344 2344 2408 2408 2472 2472 2536
1 2984 2984 2984 3112 3112 3112 3240 3240 3240 3240
2 3624 3624 3752 3752 3880 3880 3880 4008 4008 4008
3 4776 4776 4776 4968 4968 4968 5160 5160 5160 5352
4 5736 5992 5992 5992 5992 6200 6200 6200 6456 6456
5 7224 7224 7224 7480 7480 7480 7736 7736 7736 7992
6 8504 8504 8760 8760 8760 9144 9144 9144 9144 9528
7 9912 9912 10296 10296 10296 10680 10680 10680 11064 11064
8 11448 11448 11448 11832 11832 12216 12216 12216 12576 12576
9 12960 12960 12960 13536 13536 13536 13536 14112 14112 14112
10 14112 14688 14688 14688 14688 15264 15264 15264 15840 15840
11 16416 16416 16992 16992 16992 17568 17568 17568 18336 18336
12 18336 19080 19080 19080 19080 19848 19848 19848 20616 20616
13 20616 21384 21384 21384 22152 22152 22152 22920 22920 22920
14 22920 23688 23688 24496 24496 24496 25456 25456 25456 25456
15 24496 25456 25456 25456 26416 26416 26416 27376 27376 27376
16 26416 26416 27376 27376 27376 28336 28336 28336 29296 29296
17 29296 29296 30576 30576 30576 30576 31704 31704 31704 32856
18 31704 32856 32856 32856 34008 34008 34008 35160 35160 35160
19 35160 35160 35160 36696 36696 36696 37888 37888 37888 39232
20 37888 37888 39232 39232 39232 40576 40576 40576 42368 42368
21 40576 40576 42368 42368 42368 43816 43816 43816 45352 45352
22 43816 43816 45352 45352 45352 46888 46888 46888 48936 48936
23 46888 46888 46888 48936 48936 48936 51024 51024 51024 51024
24 48936 51024 51024 51024 52752 52752 52752 52752 55056 55056
25 51024 52752 52752 52752 55056 55056 55056 55056 57336 57336
26 59256 59256 61664 61664 61664 63776 63776 63776 66592 66592
N PRB
I TBS
91 92 93 94 95 96 97 98 99 100
0 2536 2536 2600 2600 2664 2664 2728 2728 2728 2792
1 3368 3368 3368 3496 3496 3496 3496 3624 3624 3624
2 4136 4136 4136 4264 4264 4264 4392 4392 4392 4584
3 5352 5352 5352 5544 5544 5544 5736 5736 5736 5736
4 6456 6456 6712 6712 6712 6968 6968 6968 6968 7224
5 7992 7992 8248 8248 8248 8504 8504 8760 8760 8760
6 9528 9528 9528 9912 9912 9912 10296 10296 10296 10296
7 11064 11448 11448 11448 11448 11832 11832 11832 12216 12216
8 12576 12960 12960 12960 13536 13536 13536 13536 14112 14112
9 14112 14688 14688 14688 15264 15264 15264 15264 15840 15840
10 15840 16416 16416 16416 16992 16992 16992 16992 17568 17568
11 18336 18336 19080 19080 19080 19080 19848 19848 19848 19848
12 20616 21384 21384 21384 21384 22152 22152 22152 22920 22920
13 23688 23688 23688 24496 24496 24496 25456 25456 25456 25456
14 26416 26416 26416 27376 27376 27376 28336 28336 28336 28336
15 28336 28336 28336 29296 29296 29296 29296 30576 30576 30576
16 29296 30576 30576 30576 30576 31704 31704 31704 31704 32856
17 32856 32856 34008 34008 34008 35160 35160 35160 35160 36696
18 36696 36696 36696 37888 37888 37888 37888 39232 39232 39232
19 39232 39232 40576 40576 40576 40576 42368 42368 42368 43816
20 42368 42368 43816 43816 43816 45352 45352 45352 46888 46888
21 45352 46888 46888 46888 46888 48936 48936 48936 48936 51024
22 48936 48936 51024 51024 51024 51024 52752 52752 52752 55056
3GPP
Release 10 38 3GPP TS 36.213 V10.0.0 (2010-12)
23 52752 52752 52752 55056 55056 55056 55056 57336 57336 57336
24 55056 57336 57336 57336 57336 59256 59256 59256 61664 61664
25 57336 59256 59256 59256 61664 61664 61664 61664 63776 63776
26 66592 68808 68808 68808 71112 71112 71112 73712 73712 75376
N PRB
I TBS
101 102 103 104 105 106 107 108 109 110
0 2792 2856 2856 2856 2984 2984 2984 2984 2984 3112
1 3752 3752 3752 3752 3880 3880 3880 4008 4008 4008
2 4584 4584 4584 4584 4776 4776 4776 4776 4968 4968
3 5992 5992 5992 5992 6200 6200 6200 6200 6456 6456
4 7224 7224 7480 7480 7480 7480 7736 7736 7736 7992
5 8760 9144 9144 9144 9144 9528 9528 9528 9528 9528
6 10680 10680 10680 10680 11064 11064 11064 11448 11448 11448
7 12216 12576 12576 12576 12960 12960 12960 12960 13536 13536
8 14112 14112 14688 14688 14688 14688 15264 15264 15264 15264
9 15840 16416 16416 16416 16416 16992 16992 16992 16992 17568
10 17568 18336 18336 18336 18336 18336 19080 19080 19080 19080
11 20616 20616 20616 21384 21384 21384 21384 22152 22152 22152
12 22920 23688 23688 23688 23688 24496 24496 24496 24496 25456
13 26416 26416 26416 26416 27376 27376 27376 27376 28336 28336
14 29296 29296 29296 29296 30576 30576 30576 30576 31704 31704
15 30576 31704 31704 31704 31704 32856 32856 32856 34008 34008
16 32856 32856 34008 34008 34008 34008 35160 35160 35160 35160
17 36696 36696 36696 37888 37888 37888 39232 39232 39232 39232
18 40576 40576 40576 40576 42368 42368 42368 42368 43816 43816
19 43816 43816 43816 45352 45352 45352 46888 46888 46888 46888
20 46888 46888 48936 48936 48936 48936 48936 51024 51024 51024
21 51024 51024 51024 52752 52752 52752 52752 55056 55056 55056
22 55056 55056 55056 57336 57336 57336 57336 59256 59256 59256
23 57336 59256 59256 59256 59256 61664 61664 61664 61664 63776
24 61664 61664 63776 63776 63776 63776 66592 66592 66592 66592
25 63776 63776 66592 66592 66592 66592 68808 68808 68808 71112
26 75376 75376 75376 75376 75376 75376 75376 75376 75376 75376
7.1.7.2.2 Transport blocks mapped to two-layer spatial multiplexing

For 1  N PRB  55 , the TBS is given by the ( I TBS , 2  N PRB ) entry of Table 7.1.7.2.1-1.
For 56  N PRB  110 , a baseline TBS_L1 is taken from the ( I TBS , N PRB ) entry of Table 7.1.7.2.1-1, which is then
translated into TBS_L2 using the mapping rule shown in Table 7.1.7.2.2-1. The TBS is given by TBS_L2.
Table 7.1.7.2.2-1: One-layer to two-layer TBS translation table
TBS_L1 TBS_L2 TBS_L1 TBS_L2 TBS_L1 TBS_L2 TBS_L1 TBS_L2

1544 3112 3752 7480 10296 20616 28336 57336
1608 3240 3880 7736 10680 21384 29296 59256
1672 3368 4008 7992 11064 22152 30576 61664
1736 3496 4136 8248 11448 22920 31704 63776
1800 3624 4264 8504 11832 23688 32856 66592
1864 3752 4392 8760 12216 24496 34008 68808
1928 3880 4584 9144 12576 25456 35160 71112
1992 4008 4776 9528 12960 25456 36696 73712
2024 4008 4968 9912 13536 27376 37888 76208
2088 4136 5160 10296 14112 28336 39232 78704
2152 4264 5352 10680 14688 29296 40576 81176
3GPP
Release 10 39 3GPP TS 36.213 V10.0.0 (2010-12)
2216 4392 5544 11064 15264 30576 42368 84760

2280 4584 5736 11448 15840 31704 43816 87936
2344 4776 5992 11832 16416 32856 45352 90816
2408 4776 6200 12576 16992 34008 46888 93800
2472 4968 6456 12960 17568 35160 48936 97896
2536 5160 6712 13536 18336 36696 51024 101840
2600 5160 6968 14112 19080 37888 52752 105528
2664 5352 7224 14688 19848 39232 55056 110136
2728 5544 7480 14688 20616 40576 57336 115040
2792 5544 7736 15264 21384 42368 59256 119816
2856 5736 7992 15840 22152 43816 61664 124464
2984 5992 8248 16416 22920 45352 63776 128496
3112 6200 8504 16992 23688 46888 66592 133208
3240 6456 8760 17568 24496 48936 68808 137792
3368 6712 9144 18336 25456 51024 71112 142248
3496 6968 9528 19080 26416 52752 73712 146856
3624 7224 9912 19848 27376 55056 75376 149776
7.1.7.2.3 Transport blocks mapped for DCI Format 1C

The TBS is given by the I TBS entry of Table 7.1.7.2.3-1.
Table 7.1.7.2.3-1: Transport Block Size Table for DCI format 1C
I TBS 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
TBS 40 56 72 120 136 144 176 208 224 256 280 296 328 336 392 488
I TBS 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
TBS 552 600 632 696 776 840 904 1000 1064 1128 1224 1288 1384 1480 1608 1736
7.1.7.2.4 Transport blocks mapped to three-layer spatial multiplexing

Table 7.7.2.4-1: One-layer to three-layer TBS translation table

1032 3112 2664 7992 8248 24496 26416 78704
1064 3240 2728 8248 8504 25456 27376 81176
1096 3240 2792 8248 8760 26416 28336 84760
1128 3368 2856 8504 9144 27376 29296 87936
1160 3496 2984 8760 9528 28336 30576 90816
1192 3624 3112 9144 9912 29296 31704 93800
1224 3624 3240 9528 10296 30576 32856 97896
1256 3752 3368 9912 10680 31704 34008 101840
1288 3880 3496 10296 11064 32856 35160 105528
1320 4008 3624 10680 11448 34008 36696 110136
1352 4008 3752 11064 11832 35160 37888 115040
1384 4136 3880 11448 12216 36696 39232 119816
3GPP
Release 10 40 3GPP TS 36.213 V10.0.0 (2010-12)
1416 4264 4008 11832 12576 37888 40576 119816

1480 4392 4136 12576 12960 39232 42368 128496
1544 4584 4264 12960 13536 40576 43816 133208
1608 4776 4392 12960 14112 42368 45352 137792
1672 4968 4584 13536 14688 43816 46888 142248
1736 5160 4776 14112 15264 45352 48936 146856
1800 5352 4968 14688 15840 46888 51024 152976
1864 5544 5160 15264 16416 48936 52752 157432
1928 5736 5352 15840 16992 51024 55056 165216
1992 5992 5544 16416 17568 52752 57336 171888
2024 5992 5736 16992 18336 55056 59256 177816
2088 6200 5992 18336 19080 57336 61664 185728
2152 6456 6200 18336 19848 59256 63776 191720
2216 6712 6456 19080 20616 61664 66592 199824
2280 6712 6712 19848 21384 63776 68808 205880
2344 6968 6968 20616 22152 66592 71112 214176
2408 7224 7224 21384 22920 68808 73712 221680
2472 7480 7480 22152 23688 71112 75376 226416
2536 7480 7736 22920 24496 73712
2600 7736 7992 23688 25456 76208
7.1.7.2.5 Transport blocks mapped to four-layer spatial multiplexing

Table 7.1.7.2.5-1: One-layer to four-layer TBS translation table

776 3112 2280 9144 7224 29296 24496 97896
808 3240 2344 9528 7480 29296 25456 101840
840 3368 2408 9528 7736 30576 26416 105528
872 3496 2472 9912 7992 31704 27376 110136
904 3624 2536 10296 8248 32856 28336 115040
936 3752 2600 10296 8504 34008 29296 115040
968 3880 2664 10680 8760 35160 30576 124464
1000 4008 2728 11064 9144 36696 31704 128496
1032 4136 2792 11064 9528 37888 32856 133208
1064 4264 2856 11448 9912 39232 34008 137792
1096 4392 2984 11832 10296 40576 35160 142248
1128 4584 3112 12576 10680 42368 36696 146856
1160 4584 3240 12960 11064 43816 37888 151376
1192 4776 3368 13536 11448 45352 39232 157432
1224 4968 3496 14112 11832 46888 40576 161760
1256 4968 3624 14688 12216 48936 42368 169544
1288 5160 3752 15264 12576 51024 43816 175600
1320 5352 3880 15264 12960 51024 45352 181656
1352 5352 4008 15840 13536 55056 46888 187712
1384 5544 4136 16416 14112 57336 48936 195816
1416 5736 4264 16992 14688 59256 51024 203704
1480 5992 4392 17568 15264 61664 52752 211936
3GPP
Release 10 41 3GPP TS 36.213 V10.0.0 (2010-12)
1544 6200 4584 18336 15840 63776 55056 220296

1608 6456 4776 19080 16416 66592 57336 230104
1672 6712 4968 19848 16992 68808 59256 236160
1736 6968 5160 20616 17568 71112 61664 245648
1800 7224 5352 21384 18336 73712 63776 254328
1864 7480 5544 22152 19080 76208 66592 266440
1928 7736 5736 22920 19848 78704 68808 275376
1992 7992 5992 23688 20616 81176 71112 284608
2024 7992 6200 24496 21384 84760 73712 293736
2088 8248 6456 25456 22152 87936 75376 299856
2152 8504 6712 26416 22920 90816
2216 8760 6968 28336 23688 93800
7.1.7.3 Redundancy Version determination for Format 1C

If the DCI Format 1C CRC is scrambled by P-RNTI or RA-RNTI, then
− the UE shall set the Redundancy Version to 0
Else if the DCI Format 1C CRC is scrambled by SI-RNTI, then
− the UE shall set the Redundancy Version as defined in [8].
7.2 UE procedure for reporting channel quality indication (CQI),

precoding matrix indicator (PMI) and rank indication (RI)
The time and frequency resources that can be used by the UE to report CQI, PMI, and RI are controlled by the eNB. For
spatial multiplexing, as given in [3], the UE shall determine a RI corresponding to the number of useful transmission
layers. For transmit diversity as given in [3], RI is equal to one.
A UE in transmission mode 8 [or 9] is configured with PMI/RI reporting if the parameter pmi-RI-Report is configured
by higher layer signalling; otherwise, it is configured without PMI/RI reporting.
CQI, PMI, and RI reporting is periodic or aperiodic.
A UE shall transmit periodic CQI/PMI, or RI reporting on PUCCH as defined hereafter in subframes with no PUSCH
allocation. A UE shall transmit periodic CQI/PMI or RI reporting on PUSCH as defined hereafter in subframes with
PUSCH allocation, where the UE shall use the same PUCCH-based periodic CQI/PMI or RI reporting format on
PUSCH.
A UE shall transmit aperiodic CQI/PMI, and RI reporting on PUSCH if the conditions specified hereafter are met. For
aperiodic CQI reporting, RI reporting is transmitted only if configured CQI/PMI/RI feedback type supports RI
reporting.
The CQI transmissions on PUCCH and PUSCH for various scheduling modes are summarized in the following table:
Table 7.2-1: Physical Channels for Aperiodic or Periodic CQI reporting
Scheduling Mode Periodic CQI reporting channels Aperiodic CQI reporting channel
Frequency non-selective PUCCH
Frequency selective PUCCH PUSCH
In case both periodic and aperiodic reporting would occur in the same subframe, the UE shall only transmit the
aperiodic report in that subframe.
3GPP
Release 10 42 3GPP TS 36.213 V10.0.0 (2010-12)
When reporting RI the UE reports a single instance of the number of useful transmission layers. For each RI reporting
interval when the UE is configured in transmission modes 4 or 9 or when the UE is configured in transmission mode 8
with PMI/RI reporting, a UE shall determine a RI from the supported set of RI values for the corresponding eNodeB
antenna configuration and UE category and report the number in each RI report. For each RI reporting interval when the
UE is configured in transmission mode 3, a UE shall determine RI for the corresponding eNodeB antenna configuration
and UE category in each reporting interval and report the detected number in each RI report to support selection
between transmit diversity and large delay CDD.
When reporting PMI the UE reports either a single or a multiple PMI report. The number of RBs represented by a
DL
single UE PMI report can be N RB or a smaller subset of RBs. The number of RBs represented by a single PMI report
is semi-statically configured by higher layer signalling. A UE is restricted to report PMI and RI within a precoder
codebook subset specified by a bitmap parameter codebookSubsetRestriction configured by higher layer signalling. For
a specific precoder codebook and associated transmission mode, the bitmap can specify all possible precoder codebook
subsets from which the UE can assume the eNB may be using when the UE is configured in the relevant transmission
mode. Codebook subset restriction is supported for transmission modes 3, 4, 5, 6, 8 and for transmission mode 9 if the
UE is configured with PMI/RI reporting. The resulting number of bits for each transmission mode is given in Table 7.2-
1b. The bitmap forms the bit sequence a Ac 1 ,..., a3 , a2 , a1 , a0 where a0 is the LSB and a Ac 1 is the MSB and
where a bit value of zero indicates that the PMI and RI reporting is not allowed to correspond to precoder(s) associated
with the bit. The association of bits to precoders for the relevant transmission modes are given as follows:
1. Transmission mode 3
a. 2 antenna ports: bit a 1 ,   2 is associated with the precoder in Table 6.3.4.2.3-1 of [3]
corresponding to  layers and codebook index 0 while bit a0 is associated with the precoder for 2
antenna ports in Section 6.3.4.3 of [3].
b. 4 antenna ports: bit a 1 ,   2,3,4 is associated with the precoders in Table 6.3.4.2.3-2 of [3]
corresponding to  layers and codebook indices 12, 13, 14, and 15 while bit a0 is associated with
the precoder for 4 antenna ports in Section 6.3.4.3 of [3].
a. 2 antenna ports: see Table 7.2-1c
b. 4 antenna ports: bit a16( 1)  ic is associated with the precoder for  layers and with codebook
index ic in Table 6.3.4.2.3-2 of [3].
3. Transmission modes 5 and 6
a. 2 antenna ports: bit aic is associated with the precoder for   1 layer with codebook index ic in
Table 6.3.4.2.3-1 of [3].
b. 4 antenna ports: bit aic is associated with the precoder for   1 layer with codebook index ic in
Table 6.3.4.2.3-2 of [3].
b. 4 antenna ports: bit a16 ( 1)  ic is associated with the precoder for  layers and with codebook
index ic in Table 6.3.4.2.3-2 of [3],   1,2 .
b. 4 antenna ports: bit a16( 1)  ic is associated with the precoder for  layers and with second
component codebook index ic in Table 6.3.4.2.3-2 of [3].
3GPP
Release 10 43 3GPP TS 36.213 V10.0.0 (2010-12)
c. 8 antenna ports: bit a f 1( 1)  ic1 is associated with the precoder for  layers (
  {1,2,3,4,5,6,7,8} ) and codebook index ic1 where
f 1()   0,16,32,36,40,44,48,52  and bit a53 g1( 1)  ic2 is associated with the
precoder for  layers (   {1,2,3,4} ) and codebook index ic2 where
g1()   0,16,32,48  . Codebook indices ic1 and ic2 are given in Table 6.3.4.2.3-3,
6.3.4.2.3-4, 6.3.4.2.3-5, 6.3.4.2.3-6, 6.3.4.2.3-7, 6.3.4.2.3-8, 6.3.4.2.3-9, or 6.3.4.2.3-10 of [3] for 
=1,2,3,4,5,6,7, or 8 respectively.
Table 7.2-1b: Number of bits in codebook subset restriction bitmap for applicable transmission
modes.
Number of bits Ac
2 antenna 4 antenna 8 antenna
ports ports ports
Transmission mode 3 2 4
Transmission mode 9 6 64 109
Table 7.2-1c: Association of bits in codebookSubSetRestriction bitmap to precoders in the 2 antenna

port codebook of Table 6.3.4.2.3-1 in [3].
Codebook Number of layers 

index ic
1 2
0 a0 -
1 a1 a4
2 a2 a5
3 a3 -
The set of subbands (S) a UE shall evaluate for CQI reporting spans the entire downlink system bandwidth. A subband
is a set of k contiguous PRBs where k is a function of system bandwidth. Note the last subband in set S may have fewer
DL DL
than k contiguous PRBs depending on N RB . The number of subbands for system bandwidth given by N RB is
defined by N   N RBDL
/ k  . The subbands shall be indexed in the order of increasing frequency and non-increasing
sizes starting at the lowest frequency.
 For transmission modes 1, 2, 3 and 5, as well as transmission mode 8 if the UE is configured without PMI/RI
reporting, transmission mode 4 and 9 with RI=1, and transmission mode 8 with PMI/RI reporting and RI=1, a
single 4-bit wideband CQI is reported according to Table 7.2.3-1.
3GPP
Release 10 44 3GPP TS 36.213 V10.0.0 (2010-12)
 For transmission modes 3, 4 and 9, as well as transmission mode 8 if the UE is configured with PMI/RI
reporting, CQI is calculated assuming transmission of one codeword for RI=1 and two codewords for RI > 1.
 For RI > 1 with transmission mode 4, 8, or 9, if the UE is configured with PMI/RI reporting, PUSCH based
triggered reporting includes reporting a wideband CQI which comprises:
o A 4-bit wideband CQI for codeword 0 according to Table 7.2.3-1
o A 4-bit wideband CQI for codeword 1 according to Table 7.2.3-1
 For RI > 1 with transmission mode 4, 8, or 9, if the UE is configured with PMI/RI reporting, PUCCH based
reporting includes reporting a 4-bit wideband CQI for codeword 0 according to Table 7.2.3-1 and a wideband
spatial differential CQI. The wideband spatial differential CQI value comprises:
o A 3-bit wideband spatial differential CQI value for codeword 1 offset level
 Codeword 1 offset level = wideband CQI index for codeword 0 – wideband CQI index for
codeword 1.
o The mapping from the 3-bit wideband spatial differential CQI value to the offset level is shown in
Table 7.2-2.
Table 7.2-2 Mapping spatial differential CQI value to offset level
Spatial differential CQI Offset level

value
0 0
1 1
2 2
3 3
4 -4
5 -3
6 -2
7 -1
7.2.1 Aperiodic CQI/PMI/RI Reporting using PUSCH

A UE shall perform aperiodic CQI, PMI and RI reporting using the PUSCH in subframe n+k on the serving cell of the
corresponding PUSCH transmission, upon decoding in subframe n either:
 an uplink DCI format, or
 a Random Access Response Grant,
on serving cell c if the respective CQI request field is set to trigger a report and is not reserved. If the CQI request
field is 1 bit [4], a report is triggered if the CQI request field is set to ‘1’. If the CQI request field size is 2 bits [4], a
report is triggered according to the value in Table 7.1.1-1A corresponding to aperiodic CSI reporting.
Table 7.2.1-1A: CSI Request field for PDCCH with uplink DCI format in UE specific search space
Value of CSI request field Description
’00’ No aperiodic CSI report is triggered

‘01’ Aperiodic CSI report triggered for serving cell c
Aperiodic CSI report is triggered for a 1st set of
‘10’ serving cells configured by higher layers
Aperiodic CSI report is triggered for a 2nd set of
‘11’ serving cells configured by higher layers
3GPP
Release 10 45 3GPP TS 36.213 V10.0.0 (2010-12)
Note: PDCCH with DCI formats used to grant PUSCH transmissions as given by DCI format 0 and DCI format 4 are
herein referred to as uplink DCI format when common behaviour is addressed.
When the CQI request field from an uplink DCI format is set to trigger a report, for FDD k=4, and for TDD UL/DL
configuration 1-6, k is given in Table 8-2. For TDD UL/DL configuration 0, if the MSB of the UL index is set to 1 and
LSB of the UL index is set to 0, k is given in Table 8-2; or if MSB of the UL index is set to 0 and LSB of the UL index
is set to 1, k is equal to 7; or if both MSB and LSB of the UL index is set to 1, k is given in Table 8-2.
When the CQI request field from a Random Access Response Grant is set to trigger a report and is not reserved, k is
equal to k1 if the UL delay field in section 6.2 is set to zero, where k1 is given in section 6.1.1. The UE shall
postpone aperiodic CQI, PMI and RI reporting to the next available UL subframe if the UL delay field is set to 1.
The minimum reporting interval for aperiodic reporting of CQI and PMI and RI is 1 subframe. The subband size for
CQI shall be the same for transmitter-receiver configurations with and without precoding.
When aperiodic CQI/PMI/RI report with no transport block associated as defined in section 8.6.2 and positive SR is
transmitted in the same subframe, the UE shall transmit SR, and, if applicable, ACK/NAK, on PUCCH resources as
described in Section 10.1
A UE is semi-statically configured by higher layers to feed back CQI and PMI and corresponding RI on the same
PUSCH using one of the following reporting modes given in Table 7.2.1-1 and described below.
Table 7.2.1-1: CQI and PMI Feedback Types for PUSCH reporting Modes
PMI Feedback Type
No PMI Single PMI Multiple PMI
Wideband Mode 1-2

(wideband CQI)
Feedback Type
PUSCH CQI
UE Selected Mode 2-0 Mode 2-2

(subband CQI)
Higher Layer-
configured Mode 3-0 Mode 3-1
(subband CQI)
For each of the transmission modes defined in Section 7.1, the following reporting modes are supported on PUSCH:
Transmission mode 1 : Modes 2-0, 3-0

Transmission mode 4 : Modes 1-2, 2-2, 3-1
Transmission mode 5 : Mode 3-1
Transmission mode 6 : Modes 1-2, 2-2, 3-1
Transmission mode 8 : Modes 1-2, 2-2, 3-1 if the UE is configured with PMI/RI reporting; modes 2-0, 3-0 if the
UE is configured without PMI/RI reporting
Transmission mode 9 : Modes 1-2, 2-2, 3-1 [if the UE is configured with PMI/RI reporting; modes 2-0, 3-0 if the
UE is configured without PMI/RI reporting]
The aperiodic CQI reporting mode is given by the parameter cqi-ReportModeAperiodic which is configured by higher-
layer signalling.
DL
For N RB  7 , PUSCH reporting modes are not supported.
RI is only reported for transmission modes 3, 4, 8 and 9 if the UE is configured with PMI/RI reporting.
A RI report on an aperiodic reporting mode is valid only for CQI/PMI report on that aperiodic reporting mode
 Wideband feedback
3GPP
Release 10 46 3GPP TS 36.213 V10.0.0 (2010-12)
o Mode 1-2 description:
 For each subband a preferred precoding matrix is selected from the codebook subset
assuming transmission only in the subband
 A UE shall report one wideband CQI value per codeword which is calculated assuming
the use of the corresponding selected precoding matrix in each subband and
transmission on set S subbands.
 The UE shall report the selected precoding matrix indicator for each set S subband
except for transmission mode 9 with 8 CSI-RS ports configured in which case a first
precoding matrix indicator i1 is reported for the set S subbands and a second precoding
matrix indicator i2 is reported for each set S subband, where the mapping from the
first precoding matrix indicator i1 with each second precoding matrix indicator i2 to
the corresponding selected precoding matrix per set S subband is determined by Table
6.3.4.2.3-3, 6.3.4.2.3-4, 6.3.4.2.3-5, 6.3.4.2.3-6, 6.3.4.2.3-7, 6.3.4.2.3-8, 6.3.4.2.3-9, or
6.3.4.2.3-10 for rank 1,2,3,4,5,6,7, or 8 respectively given in [3].
 Subband size is given by Table 7.2.1-3.
 For transmission mode 4 and transmission mode 8, the reported PMI and CQI values
are calculated conditioned on the reported RI. For other transmission modes they are
reported conditioned on rank 1.
 Higher Layer-configured subband feedback
 A UE shall report a wideband CQI value which is calculated assuming transmission on

set S subbands
 The UE shall also report one subband CQI value for each set S subband. The subband
CQI value is calculated assuming transmission only in the subband
 Both the wideband and subband CQI represent channel quality for the first codeword,
even when RI>1.
 For transmission mode 3 the reported CQI values are calculated conditioned on the
reported RI. For other transmission modes they are reported conditioned on rank 1.
 A single precoding matrix is selected from the codebook subset assuming transmission
on set S subbands
 A UE shall report one subband CQI value per codeword for each set S subband which
are calculated assuming the use of the single precoding matrix in all subbands and
assuming transmission in the corresponding subband.
 A UE shall report a wideband CQI value per codeword which is calculated assuming
the use of the single precoding matrix in all subbands and transmission on set S
subbands
 The UE shall report the single selected precoding matrix indicator except for
transmission mode 9 in which case a first and second precoding matrix indicator are
reported corresponding to the single selected precoding matrix.
 For transmission modes 4, 8 and 9, the reported PMI and CQI values are calculated
conditioned on the reported RI. For other transmission modes they are reported
conditioned on rank 1.
o Subband CQI value for each codeword are encoded differentially with respect to their respective
wideband CQI using 2-bits as defined by
3GPP
Release 10 47 3GPP TS 36.213 V10.0.0 (2010-12)
 Subband differential CQI offset level = subband CQI index – wideband CQI index. The
mapping from the 2-bit subband differential CQI value to the offset level is shown in
Table 7.2.1-2.
Table 7.2.1-2: Mapping subband differential CQI value to offset level
Subband differential CQI Offset level

value
0 0
1 1
2 2
3 -1
o Supported subband size (k) is given in Table 7.2.1-3.
Table 7.2.1-3: Subband Size (k) vs. System Bandwidth
System Bandwidth Subband Size

DL
N RB (k)
6-7 NA
8 - 10 4
11 - 26 4
27 - 63 6
64 - 110 8
 UE-selected subband feedback
 The UE shall select a set of M preferred subbands of size k (where k and M are given in
Table 7.2.1-5 for each system bandwidth range) within the set of subbands S.
 The UE shall also report one CQI value reflecting transmission only over the M selected
subbands determined in the previous step. The CQI represents channel quality for the
first codeword, even when RI>1.
 Additionally, the UE shall also report one wideband CQI value which is calculated
assuming transmission on set S subbands. The wideband CQI represents channel quality
for the first codeword, even when RI>1.
 For transmission mode 3 the reported CQI values are calculated conditioned on the
reported RI. For other transmission modes they are reported conditioned on rank 1.
 The UE shall perform joint selection of the set of M preferred subbands of size k within
the set of subbands S and a preferred single precoding matrix selected from the
codebook subset that is preferred to be used for transmission over the M selected
subbands.
 The UE shall report one CQI value per codeword reflecting transmission only over the
selected M preferred subbands and using the same selected single precoding matrix in
each of the M subbands.
 Except for transmission mode 9, the UE shall also report the single selected precoding
matrix indicator preferred for the M selected subbands. . A UE shall also report the
selected single precoding matrix indicator for all set S subbands.
3GPP
Release 10 48 3GPP TS 36.213 V10.0.0 (2010-12)
 For transmission mode 9, a UE shall report a first precoding matrix indicator for all set
S subbands. A UE shall also report a second precoding matrix indicator for all set S
subbands and another second precoding matrix indicator for the M selected subbands
 A single precoding matrix is selected from the codebook subset assuming transmission
on set S subbands
 A UE shall report a wideband CQI value per codeword which is calculated assuming
the use of the single precoding matrix in all subbands and transmission on set S
subbands
 For transmission modes 4, 8 and 9, the reported PMI and CQI values are calculated
conditioned on the reported RI. For other transmission modes they are reported
conditioned on rank 1.
o For all UE-selected subband feedback modes the UE shall report the positions of the M selected
subbands using a combinatorial index r defined as
M 1 N  si
 r 
i 0 M i
where the set  si  i  0 , ( 1  si  N , si  si 1 ) contains the M sorted subband indices and

M 1

 x 
x   x y
  y  is the extended binomial coefficient, resulting in unique label
y  0
 x y

 N  
r  0,,    1 .

   
M 
o The CQI value for the M selected subbands for each codeword is encoded differentially using 2-bits
relative to its respective wideband CQI as defined by
 Differential CQI offset level = M selected subbands CQI index – wideband CQI index
 The mapping from the 2-bit differential CQI value to the offset level is shown in Table
7.2.1-4.
Table 7.2.1-4: Mapping differential CQI value to offset level
Differential CQI value Offset level

0 1
1 2
2 3
3 4
o Supported subband size k and M values include those shown in Table 7.2.1-5. In Table 7.2.1-5 the k
and M values are a function of system bandwidth.
 N 
o The number of bits to denote the position of the M selected subbands is L  log 2 
M 
 .
  
3GPP
Release 10 49 3GPP TS 36.213 V10.0.0 (2010-12)
Table 7.2.1-5: Subband Size (k) and Number of Subbands (M) in S vs. Downlink System Bandwidth
System Bandwidth
DL Subband Size k (RBs) M
N RB
6–7 NA NA
8 – 10 2 1
11 – 26 2 3
27 – 63 3 5
64 – 110 4 6
7.2.2 Periodic CQI/PMI/RI Reporting using PUCCH

A UE is semi-statically configured by higher layers to periodically feed back different CQI, PMI, and RI on the PUCCH
using the reporting modes given in Table 7.2.2-1 and described below.
Table 7.2.2-1: CQI and PMI Feedback Types for PUCCH reporting Modes
PMI Feedback Type

No PMI Single PMI
Feedback Type
PUCCH CQI
Wideband Mode 1-0 Mode 1-1

(wideband CQI)
UE Selected Mode 2-0 Mode 2-1

(subband CQI)
For each of the transmission modes defined in Section 7.1, the following reporting modes are supported on PUCCH:

Transmission mode 8 : Modes 1-1, 2-1 if the UE is configured with PMI/RI reporting; modes 1-0, 2-0 if the UE is
configured without PMI/RI reporting
Transmission mode 9 : Modes 1-1, 2-1 [if the UE is configured with PMI/RI reporting; modes 1-0, 2-0 if the UE
is configured without PMI/RI reporting]
The periodic CQI reporting mode is given by the parameter cqi-FormatIndicatorPeriodic which is configured by
higher-layer signalling. Mode 1-1 is configured to be either submode 1 or submode 2 via higher-layer signaling using
the parameter PUCCH_format1-1_CSI_reporting_mode.
For the UE-selected subband CQI, a CQI report in a certain subframe describes the channel quality in a particular part
or in particular parts of the bandwidth described subsequently as bandwidth part (BP) or parts. The bandwidth parts
shall be indexed in the order of increasing frequency and non-increasing sizes starting at the lowest frequency.
where  N RB / k  subbands are of size
DL
 There are a total of N subbands for a system bandwidth given by N RB DL
k. If  N RB
DL
/ k    N RB
DL
 
/ k   0 then one of the subbands is of size N RB  k  N RB / k .
DL DL
 A bandwidth part j is frequency-consecutive and consists of N j subbands where J bandwidth parts span S or
DL
N RB as given in Table 7.2.2-2. If J  1 then N j is  N RB
DL
/ k / J  . If J>1 then N j is either
 N RB
DL
/k / J or  N RB
DL
/ k / J   1 , depending on N RB , k and J.
DL
3GPP
Release 10 50 3GPP TS 36.213 V10.0.0 (2010-12)
 Each bandwidth part j, where 0 ≤ j ≤ J-1, is scanned in sequential order according to increasing frequency.
 For UE selected subband feedback a single subband out of N j subbands of a bandwidth part is selected along
with a corresponding L-bit label indexed in the order of increasing frequency, where L  log 2  N RB
DL
/ k / J   .
 
The CQI and PMI payload sizes of each PUCCH reporting mode are given in Table 7.2.2-3.
The following CQI/PMI and RI reporting types with distinct periods and offsets are supported for the PUCCH reporting
modes given in Table 7.2.2-3:
 Type 1 report supports CQI feedback for the UE selected sub-bands
 Type 1a report supports subband CQI and second PMI feedback
 Type 2, Type 2b, and Type 2c report supports wideband CQI and PMI feedback
 Type 2a report supports wideband PMI feedback
 Type 3 report supports RI feedback
 Type 4 report supports wideband CQI
 Type 5 report supports RI and wideband PMI feedback
 Type 6 report supports RI and PTI feedback
The periodicity N pd (in subframes) and offset N OFFSET ,CQI (in subframes) for CQI/PMI reporting are determined based on
the parameter cqi-pmi-ConfigIndex ( I CQI / PMI ) given in Table 7.2.2-1A for FDD and Table 7.2.2-1C for TDD. The periodicity
M RI and relative offset N OFFSET , RI for RI reporting are determined based on the parameter ri-ConfigIndex ( I RI ) given in
Table 7.2.2-1B. Both cqi-pmi-ConfigIndex and ri-ConfigIndex are configured by higher layer signalling. The relative
reporting offset for RI N OFFSET , RI takes values from the set {0,1,...,( N pd  1)}
In the case where wideband CQI/PMI reporting is configured:

 The reporting instances for wideband CQI/PMI are subframes satisfying
10  n f   ns / 2  N OFFSET ,CQI  mod N pd   0 .
 In case RI reporting is configured, the reporting interval of the RI reporting is an integer multiple M RI of
period N pd (in subframes).
o The reporting instances for RI are subframes satisfying
10  n f   ns / 2  NOFFSET ,CQI  NOFFSET , RI  mod N pd  M RI   0 .
In the case where both wideband CQI/PMI and subband CQI reporting are configured:
 The reporting instances for wideband CQI/PMI and subband CQI are subframes satisfying
10  n f   ns / 2  NOFFSET ,CQI  mod N pd  0 .
 When PTI is not transmitted or the most recently transmitted PTI was equal to 1:
 The wideband CQI/PMI report has period H  N pd , and is reported on the

   
subframes satisfying 10  n f   n s / 2  N OFFSET ,CQI mod H  N pd  0 . The
integer H is defined as H  J  K  1 , where J is the number of bandwidth parts.
 Between every two consecutive wideband CQI/PMI reports, the remaining J  K

reporting instances are used in sequence for subband CQI reports on K full cycles
of bandwidth parts except when the gap between two consecutive wideband
CQI/PMI reports contains less than J  K reporting instances due to a system frame
number transition to 0, in which case the UE shall not transmit the remainder of the
subband CQI reports which have not been transmitted before the second of the two
wideband CQI/PMI reports. Each full cycle of bandwidth parts shall be in
increasing order starting from bandwidth part 0 to bandwidth part J  1 . The
parameter K is configured by higher-layer signalling.
 When the most recently transmitted PTI is 0:
3GPP
Release 10 51 3GPP TS 36.213 V10.0.0 (2010-12)
 The wideband CQI/PMI report has period H   N pd , and is reported on the

subframes satisfying A UE may be configured to transmit SRS on N p transmit
antenna ports of a serving cell where N p may be configured by higher layer
signalling independently for type 0 and type 1 triggering with cell specific
parameters defined in [3]. For PUSCH transmission mode 1 N p  {0,1,2,4} and
for PUSCH transmission mode 2 N p may be configured with one or more of the
{0,1,2} values for two antenna ports configured and N p may be configured with
one or more of the {0,1,4} values for four 4 antenna ports configured, where
H  is signalled by higher layers.
 Between every two consecutive wideband CQI/PMI reports, the remaining
reporting instances are used for a second precoding matrix indicator with wideband
CQI as described below
 In case RI reporting is configured, the reporting interval of RI is M RI times the wideband CQI/PMI period
H  N pd , and RI is reported on the same PUCCH cyclic shift resource as both the wideband CQI/PMI and
subband CQI reports.
 The reporting instances for RI are subframes satisfying

10  n f   ns / 2  NOFFSET ,CQI  NOFFSET , RI  mod H  N pd  M RI   0
In case of collision of PUCCH reporting type 3, 5, or 6 with 1, 1a, 2, 2a, 2b, 2c, or 4 the latter PUCCH reporting types (1, 1a,
2, 2a, 2b, 2c, or 4) have lower priority and are dropped. See section 10.1 regarding UE behaviour for collision between
CQI/PMI/RI and ACK/NACK and the corresponding PUCCH format assignment.
( 2, p ) ( 2, p )
The CQI/PMI or RI report shall be transmitted on the PUCCH resource n PUCCH as defined in [3], where n PUCCH is
UE specific and configured by higher layers.
In case of collision between CQI/PMI/RI and positive SR in a same subframe, CQI/PMI/RI is dropped.
Table 7.2.2-1A: Mapping of I CQI / PMI to N pd and N OFFSET ,CQI for FDD.
I CQI / PMI Value of N pd Value of N OFFSET ,CQI
0  I CQI / PMI  1 2 I CQI / PMI
2  I CQI / PMI  6 5 I CQI / PMI – 2
7  I CQI / PMI  16 10 I CQI / PMI – 7
17  I CQI / PMI  36 20 I CQI / PMI – 17
37  I CQI / PMI  76 40 I CQI / PMI – 37
77  I CQI / PMI  156 80 I CQI / PMI – 77
157  I CQI / PMI  316 160 I CQI / PMI – 157
I CQI / PMI = 317 Reserved
318  I CQI / PMI  349 32 I CQI / PMI – 318
350  I CQI / PMI  413 64 I CQI / PMI – 350
414  I CQI / PMI  541 128 I CQI / PMI – 414
542  I CQI / PMI  1023 Reserved
3GPP
Release 10 52 3GPP TS 36.213 V10.0.0 (2010-12)
Table 7.2.2-1B: Mapping of I RI to M RI and N OFFSET , RI .
I RI Value of M RI Value of N OFFSET , RI
0  I RI  160 1 − I RI
161  I RI  321 2 − ( I RI – 161)
322  I RI  482 4 − ( I RI – 322)
483  I RI  643 8 − ( I RI – 483)
644  I RI  804 16 − ( I RI – 644)
805  I RI  965 32 − ( I RI – 805)
966  I RI  1023 Reserved
Table 7.2.2-1C: Mapping of I CQI / PMI to N pd and N OFFSET ,CQI for TDD.
I CQI / PMI Value of N pd Value of N OFFSET ,CQI
I CQI / PMI = 0 1 I CQI / PMI
1  I CQI / PMI  5 5 I CQI / PMI – 1
6  I CQI / PMI  15 10 I CQI / PMI – 6
16  I CQI / PMI  35 20 I CQI / PMI – 16
36  I CQI / PMI  75 40 I CQI / PMI – 36
76  I CQI / PMI  155 80 I CQI / PMI – 76
156  I CQI / PMI  315 160 I CQI / PMI – 156
316  I CQI / PMI  1023 Reserved
For TDD periodic CQI/PMI reporting, the following periodicity values apply depending on the TDD UL/DL
configuration [3]:
o The reporting period of N pd  1 is only applicable to TDD UL/DL configurations 0, 1, 3, 4, and 6,

where all UL subframes in a radio frame are used for CQI/PMI reporting.
o The reporting period of N pd  5 is only applicable to TDD UL/DL configurations 0, 1, 2, and 6.
o The reporting periods of N pd  {10,20,40,80,160} are applicable to all TDD UL/DL
configurations.
DL
For N RB  7 , Mode 2-0 and Mode 2-1 are not supported.
The sub-sampled code book for PUCCH 1-1 submode 2 is defined in Table 7.2.2-1D for first and second precoding
matrix indicator i1 and i2 . Joint encoding of rank and first precoding matrix indicator i1 for PUCCH 1-1 submode
1 is defined in Table 7.2.2-1E.
3GPP
Release 10 53 3GPP TS 36.213 V10.0.0 (2010-12)
Table 7.2.2-1D: PUCCH 1-1 submode 2 code book subsampling.
i1 i2 total
RI #bits values #bits values #bits
1 3 {0, 2, 4, 6, 8, 10, 12, 14}, 1 {0, 2} 4
2 3 {0, 2, 4, 6, 8, 10, 12, 14} 1 {0, 1} 4
3 1 {0, 2} 3 {0, 1, 2, 3, 8, 9, 10, 11} 4
4 1 {0, 1} 3 {0, 1, 2, 3, 4, 5, 6, 7} 4
5 2 {0, 1, 2, 3} 0 {0} 2
6 2 {0, 1, 2, 3} 0 {0} 2
7 2 {0, 1, 2, 3} 0 {0} 2
8 0 {0} 0 {0} 0
Table 7.2.2-1E: Joint encoding of RI and i1 for PUCCH 1-1 submode 1.
i1
hypotheses RI
values
0-7 1 {0,2,4,6,8,12,14}
8-15 2 {0,2,4,6,8,12,14}
16-17 3 {0,2}
18-19 4 {0,2}
20-21 5 {0,2}
22-23 6 {0,2}
24-25 7 {0,2}
26 8 {0}
27-31 reserved NA
A RI report in a periodic reporting mode is valid only for CQI/PMI report on that periodic reporting mode.
For the calculation of CQI/PMI conditioned on the last reported RI, in the absence of a last reported RI the UE shall
conduct the CQI/PMI calculation conditioned on the lowest possible RI as given by the bitmap parameter
codebookSubsetRestriction .
 Wideband feedback
 In the subframe where RI is reported (only for transmission mode 3):
 A UE shall determine a RI assuming transmission on set S subbands.
 The UE shall report a type 3 report consisting of one RI.
 In the subframe where CQI is reported:
 A UE shall report a type 4 report consisting of one wideband CQI value which
is calculated assuming transmission on set S subbands. The wideband CQI
represents channel quality for the first codeword, even when RI>1.
 For transmission mode 3 the CQI is calculated conditioned on the last reported
periodic RI. For other transmission modes it is calculated conditioned on
transmission rank 1
3GPP
Release 10 54 3GPP TS 36.213 V10.0.0 (2010-12)
 In the subframe where RI is reported (only for transmission mode 4 and transmission
mode 8 and transmission mode 9):

 The UE shall report a type 3 report consisting of one RI
 In the subframe where RI and a first precoding matrix indicator are reported (only for
transmission mode 9 with submode 1 and the number of ports configured for CSI
reporting exceeds 4)
 A UE shall determine a RI assuming transmission on set S subbands
 The UE shall report a type 5 report consisting of jointly coded RI and a first
precoding matrix indicator corresponding to a single precoding matrix selected
from the codebook subset assuming transmission on set S subbands
 In the subframe where CQI/PMI is reported:

 A single precoding matrix is selected from the codebook subset assuming
transmission on set S subbands
 A UE shall report a type 2/2b/2c report on each respective successive reporting
opportunity consisting of
o A single wideband CQI value which is calculated assuming the use of

a single precoding matrix in all subbands and transmission on set S
subbands.
o For transmission mode 4 and 8 only: a type 2 report composed of the

selected single second precoding matrix indicator (wideband PMI).
o For transmission mode 9 configured to submode 1 only: a type 2b

report composed of the selected single second precoding matrix
indicator (wideband PMI) as defined in Section 7.2.4.
o For transmission mode 9 configured to submode 2 only: a type 2c

report composed of a first and a second precoding matrix indicator
corresponding to the single selected precoding matrix as defined in
Section 7.2.4.
o When RI>1, a 3-bit wideband spatial differential CQI, which is shown

in Table 7.2-2.
 For transmission mode 4, 8 and 9, the PMI and CQI are calculated conditioned
on the last reported periodic RI. For other transmission modes they are
calculated conditioned on transmission rank 1.
 UE Selected subband feedback
 In the subframe where RI is reported (only for transmission mode 3):
 In the subframe where wideband CQI is reported:
 The UE shall report a type 4 report on each respective successive reporting

opportunity consisting of one wideband CQI value which is calculated
assuming transmission on set S subbands. The wideband CQI represents
channel quality for the first codeword, even when RI>1.
3GPP
Release 10 55 3GPP TS 36.213 V10.0.0 (2010-12)
 For transmission mode 3 the CQI is calculated conditioned on the last reported
periodic RI. For other transmission modes it is calculated conditioned on
transmission rank 1.
 In the subframe where CQI for the selected subbands is reported:
 The UE shall select the preferred subband within the set of N j subbands in
each of the J bandwidth parts where J is given in Table 7.2.2-2.
 The UE shall report a type 1 report consisting of one CQI value reflecting
transmission only over the selected subband of a bandwidth part determined in
the previous step along with the corresponding preferred subband L-bit label.
A type 1 report for each bandwidth part will in turn be reported in respective
successive reporting opportunities. The CQI represents channel quality for the
first codeword, even when RI>1.
 For transmission mode 3 the preferred subband selection and CQI values are
calculated conditioned on the last reported periodic RI. For other transmission
modes they are calculated conditioned on transmission rank 1.
 In the subframe where RI is reported (only for transmission mode 4, 8 and 9 if the
number of ports configured for CSI reporting is 2 or 4):
 In the subframe where RI is reported and if the number ports configured for CSI
reporting exceeds 4 then for transmission mode 9:
 A UE shall determine a precoder type indication (PTI).
 The UE shall report a type 6 report consisting of one RI and the PTI.
 In the subframe where wideband CQI/PMI is reported:
 A single precoding matrix is selected from the codebook subset assuming
transmission on set S subbands.
 Except for transmission mode 9, a UE shall report a type 2 report on each

respective successive reporting opportunity consisting of:
o A wideband CQI value which is calculated assuming the use of a

single precoding matrix in all subbands and transmission on set S
subbands.
o The single selected precoding matrix indicator (wideband PMI).
o When RI>1, and additional 3-bit wideband spatial differential CQI,

which is shown in Table 7.2-2.
 For transmission mode 9, a UE shall report a type 2a report if PTI=0 or a type

2b report if either PTI=1 or the the number of ports configured for CSI
reporting is 2 or 4, on each respective successive reporting opportunity
consisting of:
o In case of PTI=1, a wideband CQI value which is calculated assuming

the use of a single precoding matrix in all subbands and transmission
on set S subbands.
o In case of PTI=0, the first precoding matrix indicator is reported

corresponding to the single selected precoding matrix
o In case of PTI=1, the second precoding matrix indicator is reported

corresponding to the single selected precoding matrix
3GPP
Release 10 56 3GPP TS 36.213 V10.0.0 (2010-12)
o In case of PTI=1, when RI>1, and additional 3-bit wideband spatial

differential CQI, which is shown in Table 7.2-2.
 For transmission mode 4, 8 and 9, the PMI and CQI values are calculated
conditioned on the last reported periodic RI. For other transmission modes they
are calculated conditioned on transmission rank 1.
 In the subframe where CQI for the selected subbands is reported:

 The UE shall select the preferred subband within the set of Nj subbands in each
of the J bandwidth parts where J is given in Table 7.2.2-2.
 Except for transmission mode 9 with 8 ports configured for CSI reporting, the
UE shall report a type 1 report per bandwidth part on each respective
successive reporting opportunity consisting of:
o CQI value for codeword 0 reflecting transmission only over the

selected subband of a bandwidth part determined in the previous step
along with the corresponding preferred subband L-bit label.
o When RI>1, an additional 3-bit subband spatial differential CQI value

for codeword 1 offset level
 Codeword 1 offset level = subband CQI index for codeword 0

– subband CQI index for codeword 1.
 Assuming the use of the most recently reported single

precoding matrix in all subbands and transmission on set S
subbands.
o The mapping from the 3-bit subband spatial differential CQI value to
the offset level is shown in Table 7.2-2.
 For transmission mode 9 with 8 ports configured for CSI reporting, if PTI=0
the UE shall report a type 2b report on each respective successive reporting
opportunity consisting of:
o A wideband CQI value which is calculated assuming the use of a

single selected precoding matrix in all subbands and transmission on
set S subbands.
o A second precoding matrix indicator of the preferred precoding

matrix selected from the codebook subset assuming transmission on
set S subbands.



subbands.
 For transmission mode 9, if PTI=1, the UE shall report a type 1a report per
bandwidth part on each respective successive reporting opportunity consisting
of:
o CQI value for codeword 0 reflecting transmission only over the

selected subband of a bandwidth part determined in the previous step
along with the corresponding preferred subband L-bit label.
3GPP
Release 10 57 3GPP TS 36.213 V10.0.0 (2010-12)



subbands.
o A second precoding matrix indicator of the preferred precoding

matrix selected from the codebook subset assuming transmission only
over the selected subband of a bandwidth part determined in the
previous step.
 For transmission mode 4, 8 and 9, the subband selection and CQI values are
calculated conditioned on the last reported periodic wideband PMI and RI. For
other transmission modes they are calculated conditioned on the last reported
PMI and transmission rank 1.
Table 7.2.2-2: Subband Size (k) and Bandwidth Parts (J) vs. Downlink System Bandwidth
System Bandwidth Subband Size k Bandwidth Parts

DL
N RB (RBs) (J)
6–7 NA NA
8 – 10 4 1
11 – 26 4 2
27 – 63 6 3
64 – 110 8 4
If parameter ttiBundling provided by higher layers is set to TRUE and if an UL-SCH in subframe bundling operation
collides with a periodic CQI/PMI/RI reporting instance, then the UE shall drop the periodic CQI/PMI/RI report in that
subframe and shall not multiplex periodic CQI/PMI and/or rank indicator in the PUSCH transmission in that subframe.
Table 7.2.2-3: PUCCH Report Type Payload size per Reporting Mode
PUCCH Reporting Modes

PUCCH
Report Reported Mode State Mode 1-1 Mode 2-1 Mode 1-0 Mode 2-0
Type (bits/BP) (bits/BP) (bits/BP) (bits/BP)
Sub-band RI = 1 NA 4+L NA 4+L
1
CQI RI > 1 NA 7+L NA 4+L
8 antenna ports RI = 1 NA 8+L NA NA
Sub-band CQI /
1a 8 antenna ports 1 < RI < 5 NA 9+L NA NA
second PMI
8 antenna ports RI > 4 NA 7+L NA NA
2 antenna ports RI = 1 6 6 NA NA
Wideband 4 antenna ports RI = 1 8 8 NA NA
2
CQI/PMI 2 antenna ports RI > 1 8 8 NA NA
4 antenna ports RI > 1 11 11 NA NA
8 antenna ports RI < 3 NA 4 NA NA
Wideband first
2a 8 antenna ports 2 < RI < 8 NA 2 NA NA
PMI
8 antenna ports RI = 8 NA 0 NA NA
2b Wideband 8 antenna ports RI = 1 8 8 NA NA
CQI / second 8 antenna ports 1 < RI < 4 11 11 NA NA
PMI 8 antenna ports RI = 4 10 10 NA NA
3GPP
Release 10 58 3GPP TS 36.213 V10.0.0 (2010-12)
8 antenna ports RI > 4 7 7 NA NA

8 antenna ports RI = 1 8 - NA NA
Wideband 8 antenna ports 1 < RI  4 11 - NA NA
2b CQI / first PMI / 8 antenna ports 4 < RI  4 9 - NA NA
second PMI
8 antenna ports RI = 8 7 - NA NA
2-layer spatial multiplexing 1 1 1 1
3 RI 4-layer spatial multiplexing 2 2 2 2
8-layer spatial multiplexing 3 3 NA NA
4 Wideband CQI RI = 1 or RI>1 NA NA 4 4
8 antenna ports, 2-layer
4
spatial multiplexing
5 RI/ first PMI NA NA NA
8 antenna ports, 4 and 8-
5
layer spatial multiplexing
NA 2 NA NA
6
RI/PTI NA 3 NA NA
NA 4 NA NA
7.2.3 Channel quality indicator (CQI) definition

The CQI indices and their interpretations are given in Table 7.2.3-1.
Based on an unrestricted observation interval in time and frequency, the UE shall derive for each CQI value reported in
uplink subframe n the highest CQI index between 1 and 15 in Table 7.2.3-1 which satisfies the following condition, or
CQI index 0 if CQI index 1 does not satisfy the condition:
- A single PDSCH transport block with a combination of modulation scheme and transport block size
corresponding to the CQI index, and occupying a group of downlink physical resource blocks termed the CQI
reference resource, could be received with a transport block error probability not exceeding 0.1.
For transmission mode 9 and feedback reporting modes the UE shall derive the channel measurements for computing

the CQI value reported in uplink subframe n based on only the Channel-State Information (CSI) reference signals
defined in [3]. For other transmission modes and their respective reporting modes the UE shall derive the channel
measurements for computing CQI based on CRS.
A combination of modulation scheme and transport block size corresponds to a CQI index if:
- the combination could be signalled for transmission on the PDSCH in the CQI reference resource according to
the relevant Transport Block Size table, and
- the modulation scheme is indicated by the CQI index, and
- the combination of transport block size and modulation scheme when applied to the reference resource results
in the effective channel code rate which is the closest possible to the code rate indicated by the CQI index. If
more than one combination of transport block size and modulation scheme results in an effective channel code
rate equally close to the code rate indicated by the CQI index, only the combination with the smallest of such
transport block sizes is relevant.
The CQI reference resource is defined as follows:
- In the frequency domain, the CQI reference resource is defined by the group of downlink physical resource
blocks corresponding to the band to which the derived CQI value relates.
- In the time domain, the CQI reference resource is defined by a single downlink subframe n-nCQI_ref,
o where for periodic CQI reporting nCQI_ref is the smallest value greater than or equal to 4, such that it
corresponds to a valid downlink subframe;
3GPP
Release 10 59 3GPP TS 36.213 V10.0.0 (2010-12)
o where for aperiodic CQI reporting nCQI_ref is such that the reference resource is in the same valid
downlink subframe as the corresponding CQI request in an uplink DCI format.
o where for aperiodic CQI reporting nCQI_ref is equal to 4 and downlink subframe n-nCQI_ref corresponds
to a valid downlink subframe, where downlink subframe n-nCQI_ref is received after the subframe with
the corresponding CQI request in a Random Access Response Grant.
A downlink subframe shall be considered to be valid if:
 it is configured as a downlink subframe for that UE, and
 except for transmission mode 9, it is not an MBSFN subframe, and
 it does not contain a DwPTS field in case the length of DwPTS is 7680  Ts and less, and
 it does not fall within a configured measurement gap for that UE.
If there is no valid downlink subframe for the CQI reference resource, CQI reporting is omitted in uplink
subframe n.
- In the layer domain, the CQI reference resource is defined by any RI and PMI on which the CQI is
conditioned.
In the CQI reference resource, the UE shall assume the following for the purpose of deriving the CQI index:
 The first 3 OFDM symbols are occupied by control signalling
 No resource elements used by primary or secondary synchronisation signals or PBCH
 CP length of the non-MBSFN subframes
 Redundancy Version 0
 If CSI-RS is used for channel measurements, the ratio of PDSCH EPRE to CSI-RS EPRE is as given in
Section 7.2.5
 The PDSCH transmission scheme given by Table 7.2.3-0 depending on the transmission mode currently
configured for the UE (which may be the default mode).
 If CRS is used for channel measurements, the ratio of PDSCH EPRE to cell-specific RS EPRE is as given in
Section 5.2 with the exception of  A which shall be assumed to be
o  A  PA   offset  10 log10 ( 2) [dB] for any modulation scheme, if the UE is configured with
transmission mode 2 with 4 cell-specific antenna ports, or transmission mode 3 with 4 cell-specific
antenna ports and the associated RI is equal to one;
o  A  PA   offset [dB] for any modulation scheme and any number of layers, otherwise.
The shift  offset is given by the parameter nomPDSCH-RS-EPRE-Offset which is configured by higher-layer
signalling.
3GPP
Release 10 60 3GPP TS 36.213 V10.0.0 (2010-12)
Table 7.2.3-0: PDSCH transmission scheme assumed for CQI reference resource
Transmission mode Transmission scheme of PDSCH

1 Single-antenna port, port 0
2 Transmit diversity
3 Transmit diversity if the associated rank
indicator is 1, otherwise large delay
CDD
4 Closed-loop spatial multiplexing
5 Multi-user MIMO
6 Closed-loop spatial multiplexing with a
single transmission layer
7 If the number of PBCH antenna ports is
one, Single-antenna port, port 0;
otherwise Transmit diversity
8 If the UE is configured without PMI/RI
reporting: if the number of PBCH
antenna ports is one, single-antenna port,
port 0; otherwise transmit diversity
If the UE is configured with PMI/RI

reporting: closed-loop spatial
multiplexing
9 Closed-loop spatial multiplexing with up

to 8 layer transmission, ports 7-14 (see
subclause 7.1.5B)
Table 7.2.3-1: 4-bit CQI Table
CQI index modulation code rate x 1024 efficiency

0 out of range
1 QPSK 78 0.1523
2 QPSK 120 0.2344
3 QPSK 193 0.3770
4 QPSK 308 0.6016
5 QPSK 449 0.8770
6 QPSK 602 1.1758
7 16QAM 378 1.4766
8 16QAM 490 1.9141
9 16QAM 616 2.4063
10 64QAM 466 2.7305
11 64QAM 567 3.3223
12 64QAM 666 3.9023
13 64QAM 772 4.5234
14 64QAM 873 5.1152
15 64QAM 948 5.5547
7.2.4 Precoding Matrix Indicator (PMI) definition

For transmission modes 4, 5, 6 and 9, precoding feedback is used for channel dependent codebook based precoding and
relies on UEs reporting precoding matrix indicator (PMI). For transmission mode 8, the UE shall report PMI if
configured with PMI/RI reporting. A UE shall report PMI based on the feedback modes described in 7.2.1 and 7.2.2.
For 2 and 4 antenna ports, each PMI value corresponds to a codebook index given in Table 6.3.4.2.3-1 or Table
6.3.4.2.3-2 of [3] as follows:
3GPP
Release 10 61 3GPP TS 36.213 V10.0.0 (2010-12)
 For 2 antenna ports  0,1 and an associated RI value of 1, a PMI value of n   0,1,2,3 corresponds to the
codebook index n given in Table 6.3.4.2.3-1 of [3] with   1 .
 For 2 antenna ports  0,1 and an associated RI value of 2, a PMI value of n   0,1 corresponds to the
codebook index n  1 given in Table 6.3.4.2.3-1 of [3] with   2 .
 For 4 antenna ports  0,1,2,3 , a PMI value of n   0,1,  ,15 corresponds to the codebook index n
given in Table 6.3.4.2.3-2 of [3] with  equal to the associated RI value.
For 8 antenna ports, each PMI value corresponds to a pair of codebook indices given in Table 6.3.4.2.3-3, 6.3.4.2.3-4,
6.3.4.2.3-5, 6.3.4.2.3-6, 6.3.4.2.3-7, 6.3.4.2.3-8, 6.3.4.2.3-9, or 6.3.4.2.3-10 of [3] as follows:
 For 8 antenna ports  15,16,17,18,19,20,21,22  , a first PMI value of n1   0,1,  , f ( )  1
and a second PMI value of n2   0,1, , g ( )  1 corresponds to the codebook indices n1 and n2
given in Table 6.3.4.2.3-j of [3] with  equal to the associated RI value and where j = 2+  ,
f ( )   16,16,4,4,4,4,4,1  and g ( )   16,16,16,8,1,1,1,1  .
For other transmission modes, PMI reporting is not supported.
7.2.5 Channel-State Information – Reference Symbol (CSI-RS) definition

The following parameters for CSI-RS are cell specific and are configured via higher layer signaling:
• Number of CSI-RS ports. The allowable values and port mapping are given in Section 6.10.5 of [3].
• CSI RS Configuration (see Table 6.10.5.2-1 and Table 6.10.5.2-2 in [3])
• CSI RS subframe configuration I CSI RS . The allowable values are given in Section 6.10.5.3 of [3].
• Subframe configuration period TCSI - RS . The allowable values are given in Section 6.10.5.3 of [3].
• Subframe offset  CSI - RS . The allowable values are given in Section 6.10.5.3 of [3].
• UE assumption on reference PDSCH transmitted power for CSI feedback Pc . Pc is the assumed ratio of
PDSCH EPRE to CSI-RS EPRE when UE derives CSI feedback and takes values in the range of [-8, 15] dB
with 1 dB step size.
7.3 UE procedure for reporting ACK/NACK

For FDD, when both ACK/NACK and SR are transmitted in the same sub-frame a UE shall transmit the ACK/NACK
on its assigned ACK/NACK PUCCH resource for a negative SR transmission and transmit the ACK/NACK on its
assigned SR PUCCH resource for a positive SR transmission.
For TDD and all UL-DL configurations except configuration 5, two ACK/NACK feedback modes are supported by
higher layer configuration.
- ACK/NACK bundling, and
- ACK/NACK multiplexing
For TDD UL-DL configuration 5, only ACK/NACK bundling is supported.
For TDD, the UE shall upon detection of a PDSCH transmission or a PDCCH indicating downlink SPS release (defined
in section 9.2) within subframe(s) n  k , where k  K and K is defined in Table 10.1-1 intended for the UE and
for which ACK/NACK response shall be provided, transmit the ACK/NACK response in UL subframe n.
UL
For TDD UL-DL configurations 1-6, the value of the Downlink Assignment Index (DAI) in DCI format 0, VDAI ,
detected by the UE according to Table 7.3-X in subframe n  k ' , where k ' is defined in Table 7.3-Y, represents the
total number of subframes with PDSCH transmissions and with PDCCH indicating downlink SPS release to the
UL
corresponding UE within all the subframe(s) n  k , where k  K . The value VDAI includes all PDSCH
transmission with and without corresponding PDCCH within all the subframe(s) n  k . In case neither PDSCH
transmission, nor PDCCH indicating the downlink SPS resource release is intended to the UE, the UE can expect that
UL
the value of the DAI in DCI format 0, VDAI , if transmitted, is set to 4.
3GPP
Release 10 62 3GPP TS 36.213 V10.0.0 (2010-12)
For TDD UL-DL configurations 1-6, the value of the DAI in DCI format 1/1A/1B/1D/2/2A/2B/2C denotes the
accumulative number of PDCCH(s) with assigned PDSCH transmission(s) and PDCCH indicating downlink SPS
release up to the present subframe within subframe(s) n  k , where k  K , and shall be updated from subframe to
DL
subframe. Denote VDAI as the value of the DAI in PDCCH with DCI format 1/1A/1B/1D/2/2A/2B/2C detected by the
UE according to Table 7.3-X in subframe n  k m , where k m is the smallest value in the set K (defined in Table
10.1-1) such that the UE detects a DCI format 1/1A/1B/1D/2/2A/2B/2C.
For all TDD UL-DL configurations, denote U DAI as the total number of PDCCH(s) with assigned PDSCH
transmission(s) and PDCCH indicating downlink SPS release detected by the UE within the subframe(s) n  k , where
k  K . Denote N SPS , which can be zero or one, as the number of PDSCH transmissions without a corresponding
PDCCH within the subframe(s) n  k , where k  K .
For TDD ACK/NACK bundling or ACK/NACK multiplexing and a subframe n with M  1 , the UE shall generate
one or two ACK/NACK bits by performing a logical AND operation per codeword across M DL subframes
associated with a single UL subframe, of all the corresponding U DAI  N SPS individual PDSCH transmission
ACK/NACKs and individual ACK in response to received PDCCH indicating downlink SPS release, where M is the
number of elements in the set K defined in Table 10.1-1. The UE shall detect if at least one downlink assignment has
been missed, and for the case that the UE is transmitting on PUSCH the UE shall also determine the parameter
N bundled . For TDD UL-DL configuration 0, N bundled shall be 1 if UE detects the PDSCH transmission with or
without corresponding PDCCH within the subframe n  k , where k  K .
- For the case that the UE is not transmitting on PUSCH in subframe n and TDD UL-DL configurations 1-6, if
U DAI  0 and VDAI DL
 
 U DAI  1 mod 4  1 , the UE detects that at least one downlink assignment has
been missed.
- For the case that the UE is transmitting on PUSCH and the PUSCH transmission is adjusted based on a detected
PDCCH with DCI format 0 intended for the UE and TDD UL-DL configurations 1-6, if
UL
VDAI  U DAI  N SPS  1 mod 4  1 the UE detects that at least one downlink assignment has been missed
and the UE shall generate NACK for all codewords where N bundled is determined by the UE as
N bundled  VDAI
UL
 2 . If the UE does not detect any downlink assignment missing, N bundled is determined
by the UE as N bundled  VDAI . UE shall not transmit ACK/NACK if U DAI  N SPS  0 and VDAI  4.
UL UL
- For the case that the UE is transmitting on PUSCH, and the PUSCH transmission is not based on a detected
PDCCH with DCI format 0 intended for the UE and TDD UL-DL configurations 1-6, if U DAI  0 and
DL
VDAI  U DAI  1 mod 4  1 , the UE detects that at least one downlink assignment has been missed and the
UE shall generate NACK for all codewords. The UE determines N bundled  (U DAI  N SPS ) as the number of
assigned subframes. The UE shall not transmit ACK/NACK if U DAI  N SPS  0 .
For TDD ACK/NACK bundling, when the UE is configured by transmission mode 3, 4 or 8 defined in Section 7.1 and
ACK/NACK bits are transmitted on PUSCH, the UE shall always generate 2 ACK/NACK bits assuming both codeword
0 and 1 are enabled. For the case that the UE detects only the PDSCH transmission associated with codeword 0 within
the bundled subframes, the UE shall generate NACK for codeword 1.
3GPP
Release 10 63 3GPP TS 36.213 V10.0.0 (2010-12)
Table 7.3-X: Value of Downlink Assignment Index
UL
VDAI or Number of subframes with PDSCH
DAI
transmission and with PDCCH
MSB, LSB DL
V DAI indicating DL SPS release
0,0 1 1 or 5 or 9
0,1 2 2 or 6
1,0 3 3 or 7
1,1 4 0 or 4 or 8
Table 7.3-Y: Uplink association index k’ for TDD
TDD UL/DL subframe number n

Configuration
0 1 2 3 4 5 6 7 8 9
1 6 4 6 4
2 4 4
3 4 4 4
4 4 4
5 4
6 7 7 5 7 7
For TDD ACK/NACK multiplexing and a subframe n with M  1 , spatial ACK/NACK bundling across multiple
codewords within a DL subframe is performed by a logical AND operation of all the corresponding individual
ACK/NACKs. In case the UE is transmitting on PUSCH, the UE shall determine the number of ACK/NAK feedback
ACK
bits O ACK and the ACK/NACK feedback bits o n , n  0,  , O ACK  1 to be transmitted in subframe n in
case the UE is transmitting on PUSCH.
- If the PUSCH transmission is adjusted based on a detected PDCCH with DCI format 0 intended for the UE,
then O ACK  V DAI
UL
unless VDAIUL
 4 and U DAI  N SPS  0 in which case the UE shall not transmit
ACK/NACK. The spatially bundled ACK/NACK for a PDSCH transmission with a corresponding PDCCH or
ACK
for a PDCCH indicating downlink SPS release in subframe n  k is associated with o DAI ( k ) 1 where
DAI(k) is the value of DAI in DCI format 1A/1B/1D/1/2/2A/2B/2C detected in subframe n  k . For the case
with N SPS  0 , the ACK/NACK associated with a PDSCH transmission without a corresponding PDCCH is
ACK
mapped to oO ACK 1 . The ACK/NACK feedback bits without any detected PDSCH transmission or without
detected PDCCH indicating downlink SPS release are set to NACK.
- If the PUSCH transmission is not adjusted based on a detected PDCCH with DCI format 0 intended for the UE,
is associated with the spatially bundled ACK/NACK for DL subframe n  ki ,
ACK
O ACK  M , and oi
where ki  K . The ACK/NACK feedback bits without any detected PDSCH transmission or without detected
PDCCH indicating downlink SPS release are set to NACK. The UE shall not transmit ACK/NACK if
U DAI  N SPS  0 .
For TDD when both ACK/NACK and SR are transmitted in the same sub-frame, a UE shall transmit the bundled
ACK/NACK or the multiple ACK/NAK responses (according to section 10.1) on its assigned ACK/NACK PUCCH
3GPP
Release 10 64 3GPP TS 36.213 V10.0.0 (2010-12)
resources for a negative SR transmission. For a positive SR, the UE shall transmit b(0), b(1) on its assigned SR
PUCCH resource using PUCCH format 1b according to section 5.4.1 in [3]. The value of b(0), b(1) are generated
according to Table 7.3-1 from the U DAI  N SPS ACK/NACK responses including ACK in response to PDCCH
indicating downlink SPS release by spatial ACK/NAK bundling across multiple codewords within each PDSCH
DL
transmission. For TDD UL-DL configurations 1-6, if U DAI  0 and VDAI  U DAI  1 mod 4  1 , the UE detects
that at least one downlink assignment has been missed.
Table 7.3-1: Mapping between multiple ACK/NACK responses and b(0), b(1)
Number of ACK among multiple ( U DAI  N SPS ) ACK/NACK b(0), b(1)

responses
0 or None (UE detect at least one DL assignment is missed) 0, 0
1 1, 1
2 1, 0
3 0, 1
4 1, 1
5 1, 0
6 0, 1
7 1, 1
8 1, 0
9 0, 1
For TDD when both ACK/NACK and CQI/PMI or RI are configured to be transmitted in the same sub-frame on the
PUCCH, a UE shall transmit CQI/PMI or RI and b(0), b(1) using PUCCH format 2b for normal CP or PUCCH
format 2 for extended CP, according to section 5.2.3.4 in [4] with a0 , a1 replaced by b(0), b(1) . The value of
b(0), b(1) are generated according to Table 7.3-1 from the U DAI  N SPS ACK/NACK responses including ACK
in response to PDCCH indicating downlink SPS release by spatial ACK/NACK bundling across multiple codewords
within each PDSCH transmission. For TDD UL-DL configurations 1-6, if U DAI  0 and
DL
VDAI  U DAI  1 mod 4  1 , the UE detects that at least one downlink assignment has been missed.
When only ACK/NACK or only a positive SR is transmitted a UE shall use PUCCH Format 1a or 1b for the
ACK/NACK resource and PUCCH Format 1 for the SR resource as defined in section 5.4.1 in [3].
8 Physical uplink shared channel related procedures

For FDD, there shall be 8 uplink HARQ processes per serving cell for non-subframe bundling operation, i.e. normal
HARQ operation, and 4 uplink HARQ processes for subframe bundling operation. The subframe bundling operation is
configured by the parameter ttiBundling provided by higher layers.
In case higher layers configure the use of subframe bundling for FDD and TDD, the subframe bundling operation is
only applied to UL-SCH, such that four consecutive uplink subframes are used.
3GPP
Release 10 65 3GPP TS 36.213 V10.0.0 (2010-12)
8.0 UE procedure for transmitting the physical uplink shared

channel
For FDD and normal HARQ operation, the UE shall upon detection on a given serving cell of a PDCCH with uplink
DCI format and/or a PHICH transmission in subframe n intended for the UE, adjust the corresponding PUSCH
transmission in subframe n+4 according to the PDCCH and PHICH information.
For FDD and normal HARQ operation, in case of uplink spatial multiplexing, if the UE detects a PHICH transmission
and the UE does not detect a PDCCH with DCI format 4 in subframe n intended for the UE, the UE shall adjust the
corresponding PUSCH retransmission in subframe n+4 according to the PHICH information, and using the number of
transmission layers and precoding matrix according to the most recent PDCCH, if the number of negatively
acknowledged transport blocks is equal to the number of transport blocks indicated in the most recent PDCCH
associated with the corresponding PUSCH.
For FDD and normal HARQ operation, in case of uplink spatial multiplexing, if the UE detects a PHICH transmission
and the UE does not detect a PDCCH with DCI format 4 in subframe n intended for the UE, and if the number of
negatively acknowledged transport blocks is not equal to the number of transport blocks indicated in the most recent
PDCCH associated with the corresponding PUSCH then the UE shall adjust the corresponding PUSCH retransmission
in subframe n+4 according to the PHICH information, using the precoding matrix with code book index 0 and the
number of transmission layers equal to number of layers corresponding for the negatively acknowledged transport block
from the most recent PDCCH.
If a UE is configured with the carrier indicator field for a given serving cell, the UE shall use the carrier indicator field
value from the detected PDCCH with uplink DCI format to determine the serving cell for the corresponding PUSCH
transmission.
For FDD and normal HARQ operation, if a PDCCH with CSI request field set to trigger an aperiodic CSI report as
describe in section 7.2.1 is detected by a UE on subframe n, then on subframe n+4 UCI is mapped on the corresponding
PUSCH transmission.
For FDD and subframe bundling operation, the UE shall upon detection of a PDCCH with uplink DCI format in
subframe n intended for the UE, and/or a PHICH transmission in subframe n-5 intended for the UE, adjust the
corresponding first PUSCH transmission in the bundle in subframe n+4 according to the PDCCH and PHICH
information.
For FDD and TDD, the NDI as signalled on PDCCH, the RV as determined in section 8.6.1, and the TBS as determined
in section 8.6.2, shall be delivered to higher layers.
For TDD, the number of HARQ processes shall be determined by the DL/UL configuration (Table 4.2-2 of [3]), as
indicated in Table 8-1.
Table 8-1: Number of synchronous UL HARQ processes for TDD
TDD UL/DL Number of HARQ processes for Number of HARQ processes for
configuration normal HARQ operation subframe bundling operation
0 7 3
1 4 2
2 2 N/A
3 3 N/A
4 2 N/A
5 1 N/A
6 6 3
For TDD UL/DL configurations 1-6 and normal HARQ operation, the UE shall upon detection of a PDCCH with uplink
transmission in subframe n+k, with k given in Table 8-2, according to the PDCCH and PHICH information.
For TDD UL/DL configuration 0 and normal HARQ operation the UE shall upon detection of a PDCCH with uplink
transmission in subframe n+k if the MSB of the UL index in the PDCCH with uplink DCI format is set to 1 or PHICH
is received in subframe n=0 or 5 in the resource corresponding to I PHICH  0 , as defined in Section 9.1.2, with k given
in Table 8-2. If, for TDD UL/DL configuration 0 and normal HARQ operation, the LSB of the UL index in the DCI
3GPP
Release 10 66 3GPP TS 36.213 V10.0.0 (2010-12)
format 0 is set to 1 in subframe n or a PHICH is received in subframe n=0 or 5 in the resource corresponding to
I PHICH  1 , as defined in Section 9.1.2, or PHICH is received in subframe n=1 or 6, the UE shall adjust the
corresponding PUSCH transmission in subframe n+7. If, for TDD UL/DL configuration 0, both the MSB and LSB of
the UL index in the PDCCH with uplink DCI format are set in subframe n, the UE shall adjust the corresponding
PUSCH transmission in both subframes n+ k and n+7, with k given in Table 8-2
For TDD UL/DL configurations 1 and 6 and subframe bundling operation, the UE shall upon detection of a PDCCH
with uplink DCI format in subframe n intended for the UE, and/or a PHICH transmission intended for the UE in
subframe n-l with l given in Table 8-2a, adjust the corresponding first PUSCH transmission in the bundle in subframe
n+k, with k given in Table 8-2, according to the PDCCH and PHICH information.
For TDD UL/DL configuration 0 and subframe bundling operation, the UE shall upon detection of a PDCCH with
uplink DCI format in subframe n intended for the UE, and/or a PHICH transmission intended for the UE in subframe n-
l with l given in Table 8-2a, adjust the corresponding first PUSCH transmission in the bundle in subframe n+k, if the
MSB of the UL index in the DCI format 0 is set to 1 or if I PHICH  0 , as defined in Section 9.1.2, with k given in Table
8-2, according to the PDCCH and PHICH information. If, for TDD UL/DL configuration 0 and subframe bundling
operation, the LSB of the UL index in the PDCCH with uplink DCI format is set to 1 in subframe n or if I PHICH  1 , as
defined in Section 9.1.2, the UE shall adjust the corresponding first PUSCH transmission in the bundle in subframe
n+7, according to the PDCCH and PHICH information.
Table 8-2 k for TDD configurations 0-6

Configuratio
n 0 1 2 3 4 5 6 7 8 9
0 4 6 4 6
1 6 4 6 4
2 4 4
3 4 4 4
4 4 4
5 4
6 7 7 7 7 5
Table 8-2a l for TDD configurations 0, 1 and 6

Configuratio
n 0 1 2 3 4 5 6 7 8 9
0 9 6 9 6
1 2 3 2 3
6 5 5 6 6 8
A UE is semi-statically configured via higher layer signalling to transmit PUSCH transmissions signalled via PDCCH
according to one of two uplink transmission modes, denoted mode 1 - 2 as defined in Table 8-3.If a UE is configured by
higher layers to decode PDCCHs with the CRC scrambled by the C-RNTI, the UE shall decode the PDCCH according
to the combination defined in Table 8-3 and transmit the corresponding PUSCH. The scrambling initialization of this
PUSCH corresponding to these PDCCHs and the PUSCH retransmission for the same transport block is by C-RNTI.
Transmission mode 1 is the default uplink transmission mode for a UE until the UE is assigned an uplink transmission
mode by higher layer signalling.
3GPP
Release 10 67 3GPP TS 36.213 V10.0.0 (2010-12)
Table 8-3: PDCCH and PUSCH configured by C-RNTI
Transmission DCI format Search Space Transmission scheme of PUSCH

Mode 1 DCI format 0 Common and Single-antenna port, port 10 (see

DCI format 4 UE specific by C-RNTI Closed-loop spatial multiplexing (see
subclause 8.0.2)
If a UE is configured by higher layers to decode PDCCHs with the CRC scrambled by the C-RNTI and is also
configured to receive random access procedures initiated by PDCCH orders, the UE shall decode the PDCCH according
to the combination defined in Table 8-4.
Table 8-4: PDCCH configured as PDCCH order to initiate random access procedure
DCI format Search Space

DCI format 1A Common and
If a UE is configured by higher layers to decode PDCCHs with the CRC scrambled by the SPS C-RNTI, the UE shall
decode the PDCCH according to the combination defined in Table 8-5 and transmit the corresponding PUSCH. The
scrambling initialization of this PUSCH corresponding to these PDCCHs and PUSCH retransmission for the same
transport block is by SPS C-RNTI. The scrambling initialization of initial transmission of this PUSCH without a
corresponding PDCCH and the PUSCH retransmission for the same transport block is by SPS C-RNTI.
Table 8-5: PDCCH and PUSCH configured by SPS C-RNTI
Transmission DCI format Search Space Transmission scheme of PUSCH


If a UE is configured by higher layers to decode PDCCHs with the CRC scrambled by the Temporary C-RNTI
regardless of whether UE is configured or not configured to decode PDCCHs with the CRC scrambled by the C-RNTI,
the UE shall decode the PDCCH according to the combination defined in Table 8-6 and transmit the corresponding
PUSCH. The scrambling initialization of PUSCH corresponding to these PDCCH is by Temporary C-RNTI.
If a Temporary C-RNTI is set by higher layers, the scrambling of PUSCH corresponding to the Random Access
Response Grant in Section 6.2 and the PUSCH retransmission for the same transport block is by Temporary C-RNTI.
Else, the scrambling of PUSCH corresponding to the Random Access Response Grant in Section 6.2 and the PUSCH
retransmission for the same transport block is by C-RNTI.
Table 8-6: PDCCH configured by Temporary C-RNTI

DCI format 0 Common
If a UE is configured by higher layers to decode PDCCHs with the CRC scrambled by the TPC-PUCCH-RNTI, the UE
shall decode the PDCCH according to the combination defined in table 8-7. The notation 3/3A implies that the UE shall
receive either DCI format 3 or DCI format 3A depending on the configuration.
3GPP
Release 10 68 3GPP TS 36.213 V10.0.0 (2010-12)
Table 8-7: PDCCH configured by TPC-PUCCH-RNTI

DCI format 3/3A Common
If a UE is configured by higher layers to decode PDCCHs with the CRC scrambled by the TPC-PUSCH-RNTI, the UE
shall decode the PDCCH according to the combination defined in table 8.8. The notation 3/3A implies that the UE shall
receive either DCI format 3 or DCI format 3A depending on the configuration.
Table 8-8: PDCCH configured by TPC-PUSCH-RNTI

DCI format 3/3A Common
8.0.1 Single-antenna port scheme

For the single-antenna port transmission schemes (port 10) of the PUSCH, the UE transmission on the PUSCH is
performed according to Section 5.3.2A.1 of [3].
8.0.2 Closed-loop spatial multiplexing scheme

For the closed-loop spatial multiplexing transmission scheme of the PUSCH, the UE transmission on the PUSCH is
performed according to the applicable number of transmission layers as defined in Section 5.3.2A.2 of [3].
8.1 Resource Allocation for PDCCH with uplink DCI Format

Two resource allocation schemes Type 0 and Type 1 are supported for PDCCH with uplink DCI format where the
selected resource allocation type for a decoded PDCCH is indicated by a resource allocation type bit where type 0 is
indicated by 0 value and type 1 is indicated otherwise. The UE shall interpret the resource allocation field depending on
the resource allocation type bit in the uplink PDCCH DCI format detected.
8.1.1 Uplink Resource allocation type 0

The resource allocation information for uplink resource allocation type 0 indicates to a scheduled UE a set of
contiguously allocated virtual resource block indices denoted by nVRB . A resource allocation field in the scheduling
grant consists of a resource indication value (RIV) corresponding to a starting resource block ( RBSTART ) and a length
in terms of contiguously allocated resource blocks ( LCRBs  1). The resource indication value is defined by
UL
if ( LCRBs  1)  N RB /2  then
UL
RIV  N RB ( LCRBs  1)  RBSTART
else
UL UL UL
RIV  N RB ( N RB  LCRBs  1)  ( N RB  1  RBSTART )
8.1.2 Uplink Resource allocation type 1

The resource allocation information for uplink resource allocation type 1 indicates to a scheduled UE two sets of
resource blocks with each set including one or more consecutive resource block groups of size P as given in table
UL
7.1.6.1-1 for uplink system bandwidth N RB . A resource allocation field in the scheduling grant consists of a
combinatorial index r corresponding to a starting and ending RBG index of resource block set 1, s0 and s1  1 , and
M 1 N  s
resource block set 2, s2 and s3  1 respectively, where r is given by equation r  
i
defined in section
i 0 M i
3GPP
Release 10 69 3GPP TS 36.213 V10.0.0 (2010-12)
7.2.1 with M=4 and N   N RB

UL
/ P   1 . Secton 7.2.1 also defines ordering properties and range of values that si
(RBG indices) map to. Only a single RBG is allocated for a set at the starting RBG index if the corresponding ending
RBG index equals the starting RBG index.
8.2 UE sounding procedure

A UE shall transmit Sounding Reference Symbol (SRS) on per serving cell SRS resources based on two trigger types:
- trigger type 0: higher layer signalling
- trigger type 1: UL DCI formats.
A UE may be configured with SRS parameters for trigger type 0 and trigger type 1 on each serving cell. The following
SRS parameters are serving cell specific and semi-statically configurable by higher layers for trigger type 0 and for
trigger type 1.
 Transmission comb k TC , as defined in Section 5.5.3.2 of [3]
 Starting physical resource block assignment n RRC , as defined in Section 5.5.3.2 of [3]
 duration: single or indefinite (until disabled), as defined in [11] for trigger type 0
 srs-ConfigIndex ISRS for SRS periodicity and SRS subframe offset Toffset , as defined in Table 8.2-1 and Table
8.2-2
 SRS bandwidth B SRS , as defined in Section 5.5.3.2 of [3]
 Frequency hopping bandwidth, bhop , as defined in Section 5.5.3.2 of [3] for trigger type 0
cs
 Cyclic shift n SRS , as defined in Section 5.5.3.1 of [3]
 Number of antenna ports
For trigger type 1 and DCI format 4 three sets of SRS parameters are configured by higher layer signalling. The SRS
request field in DCI format 4 indicates the SRS parameter set given in Table 8.1-1. For trigger type 1 and DCI format 0
a single set of SRS parameters is configured by higher layer signalling.
Table 8.1-1: SRS request value for trigger type 1 in DCI format 4
Value of SRS request field Description
’00’ No type 1 SRS trigger

The 1st SRS parameter set configured
‘01’ by higher layers
The 2nd SRS parameter set
‘10’ configured by higher layers
The 3rd SRS parameter set
‘11’ configured by higher layers
The serving cell specific SRS transmission bandwidths C SRS are configured by higher layers. The allowable values
are given in Section 5.5.3.2 of [3].
The serving cell specific SRS transmission sub-frames are configured by higher layers. The allowable values are given
in Section 5.5.3.3 of [3].
When antenna selection is enabled for a given serving cell for a UE that supports transmit antenna selection, the index
a nSRS  , of the UE antenna that transmits the SRS at time nSRS is given by
3GPP
Release 10 70 3GPP TS 36.213 V10.0.0 (2010-12)
a nSRS   nSRS mod 2 , for both partial and full sounding bandwidth, and when frequency hopping is disabled (i.e.,
bhop  BSRS ),
 n SRS   n SRS / 2      n SRS / K   mod 2 when K is even

a ( n SRS )   ,
n SRS mod 2 when K is odd
1 where K mod 4  0
  
0 otherwise
when frequency hopping is enabled (i.e., bhop  B SRS ),
BSRS
where values BSRS, bhop, Nb, and nSRS are given in Section 5.5.3.2 of [3], and K  N
b 'bhop
b' (where N bhop  1
regardless of the N b value), except when a single SRS transmission is configured for the UE.
A UE may be configured to transmit SRS on N p antenna ports of a serving cell where N p may be configured by
higher layer signalling independently for type 0 and type 1 triggering with cell specific parameters defined in [3]. For
PUSCH transmission mode 1 N p  {0,1,2,4} and for PUSCH transmission mode 2 N p  {0,1,2} with two
antenna ports configured for PUSCH and N p  {0,1,4} with 4 antenna ports configured for PUSCH. A UE
configured for SRS transmission on multiple antenna ports of a serving cell shall transmit SRS for all the configured
transmit antenna ports within one SC-FDMA symbol of the same subframe of the serving cell. The SRS transmission
bandwidth and starting physical resource block assignment are the same for all the configured antenna ports of a given
serving cell.
A UE shall not transmit both PUSCH and SRS in the same symbol of a subframe for a given serving cell.
For TDD, when one SC-FDMA symbol exists in UpPTS of a given serving cell, it can be used for SRS transmission.
When two SC-FDMA symbols exist in UpPTS of a given serving cell, both can be used for SRS transmission and both
can be assigned to the same UE.
A UE shall not transmit SRS whenever SRS and PUCCH format 2/2a/2b transmissions happen to coincide in the same
subframe.
A UE shall not transmit SRS whenever SRS transmission and PUCCH transmission carrying ACK/NACK and/or
positive SR happen to coincide in the same subframe if the parameter ackNackSRS-SimultaneousTransmission is FALSE.
A UE shall transmit SRS whenever SRS transmission and PUCCH transmission carrying ACK/NACK and/or positive
SR happen to coincide in the same subframe if the parameter ackNackSRS-SimultaneousTransmission is TRUE.
In UpPTS, whenever SRS transmission instance overlaps with the PRACH region for preamble format 4 or exceeds the
range of uplink system bandwidth configured in the serving cell, the UE shall not transmit SRS.
The parameter ackNackSRS-SimultaneousTransmission provided by higher layers determines if a UE is configured to

support the transmission of ACK/NACK on PUCCH and SRS in one subframe. If it is configured to support the
transmission of ACK/NACK on PUCCH and SRS in one subframe, then in the cell specific SRS subframes UE shall
transmit ACK/NACK and SR using the shortened PUCCH format as defined in Section 5.4.1 of [3], where the
ACK/NACK or the SR symbol corresponding to the SRS location is punctured. This shortened PUCCH format shall be
used in a cell specific SRS subframe even if the UE does not transmit SRS in that subframe. The cell specific SRS
subframes are defined in Section 5.5.3.3 of [3]. Otherwise, the UE shall use the normal PUCCH format 1/1a/1b as
defined in Section 5.4.1 of [3] for the transmission of ACK/NACK and SR.
SRS configuration of a UE in a serving cell for SRS periodicity, TSRS , and SRS subframe offset, Toffset , is defined in
Table 8.2-1 and Table 8.2-2, for FDD and TDD, respectively. The periodicity TSRS of the SRS transmission is
serving cell specific and is selected from the set {2, 5, 10, 20, 40, 80, 160, 320} ms or subframes. For the SRS
periodicity TSRS of 2 ms in TDD, two SRS resources are configured in a half frame containing UL subframe(s) of a
given serving cell.
Type 0 triggered SRS transmission instances in a given serving cell for TDD with TSRS  2 and for FDD are the
subframes satisfying (10  n f  kSRS  Toffset ) mod TSRS  0 , where for FDD kSRS   0,1,...,9 is the subframe
3GPP
Release 10 71 3GPP TS 36.213 V10.0.0 (2010-12)
index within the frame, for TDD kSRS is defined in Table 8.2-3. The SRS transmission instances for TDD with
TSRS  2 are the subframes satisfying ( kSRS  Toffset ) mod 5  0 .
A UE configured for type 1 triggered SRS transmission on serving cell c upon detection of a positive SRS request in
subframe n of serving cell c shall commence SRS transmission in the first subframe satisfying [ n+k, k³4 ] and
(10  n f  kSRS  Toffset ) mod TSRS  0 for TDD with TSRS  2 and for FDD,
( kSRS  Toffset ) mod 5  0 for TDD with TSRS  2
where for FDD kSRS   0,1,...,9 is the subframe index within the frame n f , for TDD kSRS is defined in Table
8.2-3.
A UE shall not transmit SRS whenever SRS and a PUSCH transmission corresponding to a Random Access Response
Grant or a retransmission of the same transport block as part of the contention based random access procedure coincide
in the same subframe.
Table 8.2-1: UE Specific SRS Periodicity TSRS and Subframe Offset Configuration Toffset , FDD
SRS Periodicity TSRS

SRS Configuration Index ISRS SRS Subframe Offset Toffset
(ms)
0–1 2 ISRS
2–6 5 ISRS – 2
7 – 16 10 ISRS – 7
17 – 36 20 ISRS – 17
37 – 76 40 ISRS – 37
77 – 156 80 ISRS – 77
157 – 316 160 ISRS – 157
317 – 636 320 ISRS – 317
637 – 1023 reserved reserved
Table 8.2-2: UE Specific SRS Periodicity TSRS and Subframe Offset Configuration Toffset , TDD
SRS Periodicity TSRS

SRS Configuration Index ISRS SRS Subframe Offset Toffset
(ms)
0 2 0, 1
1 2 0, 2
2 2 1, 2
3 2 0, 3
4 2 1, 3
5 2 0, 4
3GPP
Release 10 72 3GPP TS 36.213 V10.0.0 (2010-12)
6 2 1, 4
7 2 2, 3
8 2 2, 4
9 2 3, 4
10 – 14 5 ISRS – 10
15 – 24 10 ISRS – 15
25 – 44 20 ISRS – 25
45 – 84 40 ISRS – 45
85 – 164 80 ISRS – 85
165 – 324 160 ISRS – 165
325 – 644 320 ISRS – 325
645 – 1023 reserved reserved
Table 8.2-3: kSRS for TDD
subframe index n
0 1 2 3 4 5 6 7 8 9
1st symbol 2nd symbol 1st symbol 2nd
of UpPTS of UpPTS of UpPTS symbol of
UpPTS
kSRS in case 0 1 2 3 4 5 6 7 8 9
UpPTS length
of 2 symbols
kSRS in case 1 2 3 4 6 7 8 9
UpPTS length
of 1 symbol
8.3 UE ACK/NACK procedure

For Frame Structure type 1, an ACK/NACK received on the PHICH assigned to a UE in subframe i is associated with
the PUSCH transmission in subframe i-4.
For Frame Structure type 2 UL/DL configuration 1-6, an ACK/NACK received on the PHICH assigned to a UE in
subframe i is associated with the PUSCH transmission in the subframe i-k as indicated by the following table 8.3-1.
For Frame Structure type 2 UL/DL configuration 0, an ACK/NACK received on the PHICH in the resource
corresponding to I PHICH  0 , as defined in Section 9.1.2, assigned to a UE in subframe i is associated with the PUSCH
transmission in the subframe i-k as indicated by the following table 8.3-1. If, for Frame Structure type 2 UL/DL
configuration 0, an ACK/NACK received on the PHICH in the resource corresponding to I PHICH  1 , as defined in
Section 9.1.2, assigned to a UE in subframe i is associated with the PUSCH transmission in the subframe i-6.
Table 8.3-1 k for TDD configurations 0-6
subframe number i
3GPP
Release 10 73 3GPP TS 36.213 V10.0.0 (2010-12)
TDD UL/DL 0 1 2 3 4 5 6 7 8 9
Configuratio
n
0 7 4 7 4
1 4 6 4 6
2 6 6
3 6 6 6
4 6 6
5 6
6 6 4 7 4 6
The physical layer in the UE shall deliver indications to the higher layers as follows:
For downlink subframe i, if a transport block was transmitted in the associated PUSCH subframe then:
- if ACK is decoded on the PHICH corresponding to the transport block in subframe i, ACK for that
transport block shall be delivered to the higher layers;
- else NACK for that transport block shall be delivered to the higher layers.
For downlink subframe i, in case of a retransmission in the associated PUSCH subframe, if a transport block was
disabled in the associated PUSCH subframe then ACK for that transport block shall be delivered to the higher layers.
8.4 UE PUSCH Hopping procedure

The UE shall perform PUSCH frequency hopping if the single bit frequency hopping (FH) field in a corresponding
PDCCH with DCI format 0 is set to 1 and the uplink resource block assignment is type 0 otherwise no PUSCH
frequency hopping is performed.
A UE performing PUSCH frequency hopping shall determine its PUSCH resource allocation (RA) for the first slot of a
S1
subframe (S1) including the lowest index PRB ( n PRB ( n) ) in subframe n from the resource allocation field in the
latest PDCCH with DCI format 0 for the same transport block. If there is no PDCCH for the same transport block, the
UE shall determine its hopping type based on
- the hopping information in the most recent semi-persistent scheduling assignment PDCCH, when the initial
PUSCH for the same transport block is semi-persistently scheduled or
- the random access response grant for the same transport block, when the PUSCH is initiated by the random
access response grant.
The resource allocation field in DCI format 0 excludes either 1 or 2 bits used for hopping information as indicated by
Table 8.4-1 below where the number of PUSCH resource blocks is defined as
N UL
RB
~ HO
 N RB  N UL
RB mod 2  Type 1 PUSCH hopping

N PUSCH
RB  N UL
RB Type 2 N sb  1 PUSCH hopping
 ~ HO
N
UL
RB  N RB Type 2 N sb  1 PUSCH hopping
~ HO HO HO HO
For type 1 and type 2 PUSCH hopping, N RB  N RB  1 if N RB is an odd number where N RB defined in [3].
~ HO HO
N RB  N RB in other cases. The size of the resource allocation field in DCI format 0 after excluding either 1 or 2 bits
shall be y   log 2 ( N RB
UL UL
( N RB  1) / 2)   N UL _ hop , where NUL_hop = 1 or 2 bits. The number of contiguous RBs that
can be assigned to a type-1 hopping user is limited to
 2 y / N RBUL  . The number of contiguous RBs that can be assigned
3GPP
Release 10 74 3GPP TS 36.213 V10.0.0 (2010-12)
to a type-2 hopping user is limited to min

( 2 y
  N RBPUSCH / N sb  ), where the number of sub-bands N sb is
UL ,
/ N RB
given by higher layers.
A UE performing PUSCH frequency hopping shall use one of two possible PUSCH frequency hopping types based on
the hopping information. PUSCH hopping type 1 is described in section 8.4.1 and type 2 is described in section 8.4.2.
Table 8.4-1: Number of Hopping Bits NUL_hop vs. System Bandwidth
System BW #Hopping bits for

N UL 2nd slot RA
RB
(NUL_hop)
6-49 1
50-110 2
The parameter Hopping-mode provided by higher layers determines if PUSCH frequency hopping is “inter-subframe”
or “intra and inter-subframe”.
8.4.1 Type 1 PUSCH Hopping

~
For PUSCH hopping type 1 the hopping bit or bits indicated in Table 8.4-1 determine n PRB (i ) as defined in Table
8.4-2. The lowest index PRB ( n S1 (i ) ) of the 1st slot RA in subframe i is defined as n S1 (i )  n S1 (i )  N HO / 2 , where
PRB PRB PRB RB
S1
nPRB (i )  RBSTART , and RBSTART is obtained from the uplink scheduling grant as in Section 8.4 and Section 8.1.
HO
The lowest index PRB ( n PRB (i ) ) of the 2nd slot RA in subframe i is defined as nPRB (i )  n PRB (i )  N RB /2.
The set of physical resource blocks to be used for PUSCH transmission are LCRBs contiguously allocated resource
S1
blocks from PRB index nPRB (i ) for the 1st slot, and from PRB index n PRB (i ) for the 2nd slot, respectively, where
LCRBs is obtained from the uplink scheduling grant as in Section 8.4 and Section 8.1.
If the Hopping-mode is "inter-subframe", the 1st slot RA is applied to even CURRENT_TX_NB, and the 2nd slot RA is
applied to odd CURRENT_TX_NB, where CURRENT_TX_NB is defined in [8].
8.4.2 Type 2 PUSCH Hopping

In PUSCH hopping type 2 the set of physical resource blocks to be used for transmission in slot ns is given by the
scheduling grant together with a predefined pattern according to [3] section 5.3.4. If the system frame number is not
acquired by the UE yet, the UE shall not transmit PUSCH with type-2 hopping and N sb  1 for TDD, where N sb is
defined in [3].
Table 8.4-2: PDCCH DCI Format 0 Hopping Bit Definition
System BW Number of Information in ~

n PRB (i )
N UL
RB Hopping bits hopping bits
6 – 49 1
0 


 N PUSCH / 2
RB  ~ S 1 (i )  mod N PUSCH
n PRB 

RB ,
1 Type 2 PUSCH Hopping
00 


 N PUSCH / 4
n PRB 

RB
50 – 110 2
01 


  N PUSCH / 4
RB  ~ S1 (i )  mod N PUSCH
n PRB 

RB
10 


 N PUSCH / 2
n PRB 

RB
11 Type 2 PUSCH Hopping
3GPP
Release 10 75 3GPP TS 36.213 V10.0.0 (2010-12)
8.5 UE Reference Symbol procedure

If UL sequence hopping is configured in the cell, it applies to all reference symbols (SRS, PUSCH and PUCCH RS).
8.6 Modulation order, redundancy version and transport block size

determination
To determine the modulation order, redundancy version and transport block size for the physical uplink shared channel,
the UE shall first
− read the “modulation and coding scheme and redundancy version” field ( I MCS ), and
− check the “CQI request” bit field, and
− compute the total number of allocated PRBs ( N PRB ) based on the procedure defined in Section 8.1, and
− compute the number of coded symbols for control information.
8.6.1 Modulation order and redundancy version determination

For 0  I MCS  28 , the modulation order ( Q m ) is determined as follows:
− If the UE is capable of supporting 64QAM in PUSCH and has not been configured by higher layers to transmit
only QPSK and 16QAM, the modulation order is given by Q m' in Table 8.6.1-1.
− If the UE is not capable of supporting 64QAM in PUSCH or has been configured by higher layers to transmit
only QPSK and 16QAM, Q m' is first read from Table 8.6.1-1. The modulation order is set to
Qm  min(4, Q m' ) .
− If the parameter ttiBundling provided by higher layers is set to TRUE, then the resource allocation size is
restricted to N PRB  3 and the modulation order is set to Q m  2 .
For 29  I MCS  31 , if I MCS  29 , the “CQI request” bit field in an uplink DCI format is set to trigger a report and
N PRB  4 , the modulation order is set to Qm  2 . Otherwise, the modulation order shall be determined from the
DCI transported in the latest PDCCH with DCI format 0 for the same transport block using 0  I MCS  28 . If there is
no PDCCH with DCI format 0 for the same transport block using 0  I MCS  28 , the modulation order shall be
determined from
− the most recent semi-persistent scheduling assignment PDCCH, when the initial PUSCH for the same transport
block is semi-persistently scheduled, or,
− the random access response grant for the same transport block, when the PUSCH is initiated by the random
The UE shall use I MCS and Table 8.6.1-1 to determine the redundancy version (rvidx) to use in the physical uplink
shared channel.
Table 8.6.1-1: Modulation, TBS index and redundancy version table for PUSCH
MCS Index Modulation TBS Redundancy

I MCS Order Index Version
Q m' I TBS rvidx
3GPP
Release 10 76 3GPP TS 36.213 V10.0.0 (2010-12)
0 2 0 0
1 2 1 0
2 2 2 0
3 2 3 0
4 2 4 0
5 2 5 0
6 2 6 0
7 2 7 0
8 2 8 0
9 2 9 0
10 2 10 0
11 4 10 0
12 4 11 0
13 4 12 0
14 4 13 0
15 4 14 0
16 4 15 0
17 4 16 0
18 4 17 0
19 4 18 0
20 4 19 0
21 6 19 0
22 6 20 0
23 6 21 0
24 6 22 0
25 6 23 0
26 6 24 0
27 6 25 0
28 6 26 0
29 1
30 reserved 2
31 3
8.6.2 Transport block size determination

For 0  I MCS  28 , the UE shall first determine the TBS index ( I TBS ) using I MCS and Table 8.6.1-1 except if the
transport block is disabled in DCI format 4 as specified below. For a transport block that is not mapped to two-layer
spatial multiplexing, the TBS is determined by the procedure in Section 7.1.7.2.1. For a transport block that is mapped
to two-layer spatial multiplexing, the TBS is determined by the procedure in Section 7.17.2.2.
For 29  I MCS  31 , if I MCS  29 , the “CQI request” bit in an uplink DCI format is set to trigger a report and
N PRB  4 , then there is no transport block for the UL-SCH and only the control information feedback for the current
PUSCH reporting mode is transmitted by the UE. Otherwise, the transport block size shall be determined from the
initial PDCCH for the same transport block using 0  I MCS  28 . If there is no initial PDCCH with an uplink DCI
format for the same transport block using 0  I MCS  28 , the transport block size shall be determined from
− the most recent semi-persistent scheduling assignment PDCCH, when the initial PUSCH for the same transport
block is semi-persistently scheduled, or,
− the random access response grant for the same transport block, when the PUSCH is initiated by the random
In DCI format 4 a transport block is disabled if either the combination of I MCS  0 and N PRB  1 or the
combination of I MCS  28 and N PRB  1 is signalled, otherwise the transport block is enabled.
3GPP
Release 10 77 3GPP TS 36.213 V10.0.0 (2010-12)
8.6.3 Control information MCS offset determination

Offset values are defined for single codeword PUSCH transmission and multiple codeword PUSCH transmission.
Single codeword PUSCH transmission offsets  offset ,  offset and  offset shall be configured to values
HARQ  ACK RI CQI
HARQ  ACK RI CQI

according to Table 8.6.3-1,2,3 with the higher layer signalled indexes I offset , I offset , and I offset ,
respectively.
Table 8.6.3-1: Mapping of HARQ-ACK offset values and the index signalled by higher layers
HARQ  ACK
I offset  offset
HARQ  ACK
0 2.000
1 2.500
2 3.125
3 4.000
4 5.000
5 6.250
6 8.000
7 10.000
8 12.625
9 15.875
10 20.000
11 31.000
12 50.000
13 80.000
14 126.000
15 reserved
Table 8.6.3-2: Mapping of RI offset values and the index signalled by higher layers
RI
I offset  offset
RI
0 1.250
1 1.625
2 2.000
3 2.500
4 3.125
5 4.000
6 5.000
7 6.250
3GPP
Release 10 78 3GPP TS 36.213 V10.0.0 (2010-12)
8 8.000
9 10.000
10 12.625
11 15.875
12 20.000
13 reserved
14 reserved
15 reserved
Table 8.6.3-3: Mapping of CQI offset values and the index signalled by higher layers
CQI
I offset  offset
CQI
0 reserved
1 reserved
2 1.125
3 1.250
4 1.375
5 1.625
6 1.750
7 2.000
8 2.250
9 2.500
10 2.875
11 3.125
12 3.500
13 4.000
14 5.000
15 6.250
8.7 UE Transmit Antenna Selection

UE transmit antenna selection is configured by higher layers.
If UE transmit antenna selection is disabled or not supported by the UE, the UE shall transmit from UE port 0.
If closed-loop UE transmit antenna selection is enabled by higher layers the UE shall perform transmit antenna selection
in response to the most recent command received via DCI Format 0 in section 5.3.3.2 of [4].
If open-loop UE transmit antenna selection is enabled by higher layers, the transmit antenna to be selected by the UE is
not specified.
3GPP
Release 10 79 3GPP TS 36.213 V10.0.0 (2010-12)
9 Physical downlink control channel procedures
9.1 UE procedure for determining physical downlink control channel

assignment
9.1.1 PDCCH Assignment Procedure
The control region of each serving cell consists of a set of CCEs, numbered from 0 to N CCE , k  1 according to
Section 6.8.1 in [3], where N CCE , k is the total number of CCEs in the control region of subframe k . The UE shall
monitor a set of PDCCH candidates on one or more activated serving cells as configured by higher layer signalling for
control information in every non-DRX subframe, where monitoring implies attempting to decode each of the PDCCHs
in the set according to all the monitored DCI formats.
( L)
The set of PDCCH candidates to monitor are defined in terms of search spaces, where a search space S k at
aggregation level L  1,2,4,8 is defined by a set of PDCCH candidates. For each serving cell on which PDCCH is
( L)
monitored, the CCEs corresponding to PDCCH candidate m of the search space S k are given by
L  (Yk  m) mod  N CCE,k / L   i

where Yk is defined below, i  0, , L  1 . For the common search space m  m . For the UE specific search space,
for the serving cell on which PDCCH is monitored, if the monitoring UE is configured with carrier indicator field then
m  m  M ( L )  nCI where n CI is the carrier indicator field value, else if the monitoring UE is not configured with
carrier indicator field then m  m , where m  0, , M ( L )  1 . M (L ) is the number of PDCCH candidates to monitor
in the given search space.
Note that the carrier indicator field is the same as cellIndex given in [11].
The UE shall monitor one common search space at each of the aggregation levels 4 and 8 on the primary cell.
A UE not configured with a carrier indicator field shall monitor one UE-specific search space at each of the aggregation
levels 1, 2, 4, 8 on each activated serving cell. A UE configured with a carrier indicator field shall monitor one or more
UE-specific search spaces at each of the aggregation levels 1, 2, 4, 8 on one or more activated serving cells as
configured by higher layer signalling.
The common and UE-specific search spaces on the primary cell may overlap.
A UE configured with the carrier indicator field associated with monitoring PDCCH on serving cell c shall monitor
PDCCH configured with carrier indicator field and with CRC scrambled by C-RNTI in the UE specific search space of
serving cell c.
A UE configured with the carrier indicator field associated with monitoring PDCCH on the primary cell shall monitor
PDCCH configured with carrier indicator field and with CRC scrambled by SPS C-RNTI in the UE specific search
space of the primary cell.
The UE shall monitor the common search space for PDCCH without carrier indicator field.
For the serving cell on which PDCCH is monitored, if the UE is not configured with a carrier indicator field, it shall
monitor the UE specific search space for PDCCH without carrier indicator field, if the UE is configured with a carrier
indicator field it shall monitor the UE specific search space for PDCCH with carrier indicator field.
A UE is not expected to monitor the PDCCH of a secondary cell if it is configured to monitor PDCCH with carrier
indicator field corresponding to that secondary cell in another serving cell. For the serving cell on which PDCCH is
monitored, the UE shall monitor PDCCH candidates at least for the same serving cell.
3GPP
Release 10 80 3GPP TS 36.213 V10.0.0 (2010-12)
A UE configured with carrier indicator field for a given serving cell and configured to monitor PDCCH candidates with
CRC scrambled by C-RNTI with a common payload size and with the same first CCE index nCCE (as described in
section 10.1) in the
- common search space
- UE specific search space
may assume that only the PDCCH in the common search space is transmitted by the primary cell.
A UE configured to monitor PDCCH candidates in a given serving cell with a given DCI format size with CIF, and
CRC scrambled by C- RNTI, where the PDCCH candidates may have one or more possible values of CIF for the given
DCI format size, shall assume that a PDCCH candidate with the given DCI format size may be transmitted in the given
serving cell in any UE specific search space corresponding to any of the possible values of CIF for the given DCI
format size.
The aggregation levels defining the search spaces are listed in Table 9.1.1-1. The DCI formats that the UE shall monitor
depend on the configured transmission mode per each serving cell as defined in Section 7.1.
Table 9.1.1-1: PDCCH candidates monitored by a UE.
Search space S k
(L ) Number of PDCCH
candidates M (L )
Type Aggregation level L Size [in CCEs]
1 6 6
UE- 2 12 6
specific 4 8 2
8 16 2
4 16 4
Common
8 16 2
For the common search spaces, Yk is set to 0 for the two aggregation levels L  4 and L  8 .
( L)
For the UE-specific search space S k at aggregation level L , the variable Yk is defined by
Yk   A  Yk 1  mod D
where Y1  nRNTI  0 , A  39827 , D  65537 and k   ns 2  , ns is the slot number within a radio frame.
The RNTI value used for nRNTI is defined in section 7.1 in downlink and section 8 in uplink.
9.1.2 PHICH Assignment Procedure

For PUSCH transmissions scheduled from serving cell c in subframe n, a UE shall determine the corresponding
PHICH resource of serving cell c in subframe n  k PHICH , where k PHICH is always 4 for FDD and is given in table
9.1.2-1 for TDD. For subframe bundling operation, the corresponding PHICH resource is associated with the last
subframe in the bundle.
Table 9.1.2-1: k PHICH for TDD
TDD UL/DL subframe index n

Configuratio
n 0 1 2 3 4 5 6 7 8 9
0 4 7 6 4 7 6
1 4 6 4 6
3GPP
Release 10 81 3GPP TS 36.213 V10.0.0 (2010-12)
2 6 6
3 6 6 6
4 6 6
5 6
6 4 6 6 4 7
group seq group

The PHICH resource is identified by the index pair ( n PHICH , n PHICH ) where n PHICH is the PHICH group number
seq
and n PHICH is the orthogonal sequence index within the group as defined by:
group group group

nPHICH  ( I PRB _ RA  nDMRS ) mod N PHICH  I PHICH N PHICH
seq
nPHICH  group
 ( I PRB _ RA / N PHICH  PHICH
 nDMRS ) mod 2 N SF
where
• n DMRS is mapped from the cyclic shift for DMRS field (according to Table 9.1.2-2) in the most
recent PDCCH with uplink DCI format [4] for the transport block(s) associated with the
corresponding PUSCH transmission. n DMRS shall be set to zero, if there is no PDCCH with uplink
DCI format for the same transport block, and
• if the initial PUSCH for the same transport block is semi-persistently scheduled, or
• if the initial PUSCH for the same transport block is scheduled by the random access response
grant .
PHICH
• N SF is the spreading factor size used for PHICH modulation as described in section 6.9.1 in [3].
•
 for the first TB of a PUSCH with associated PDCCH or for the case of
 no associated PDCCH when the number of negatively acknowledged

lowest _ index

 I PRB _ RA TBs is not equal to the number of TBs indicated in the most recent
I PRB _ RA 
 PDCCH associated with the corresponding PUSCH

 lowest _ index
 I PRB _ RA 1 for a second TB of a PUSCH with associated PDCCH

lowest _ index
where I PRB _ RA is the lowest PRB index in the first slot of the corresponding PUSCH transmission
group
• N PHICH is the number of PHICH groups configured by higher layers as described in section 6.9 of
[3],
•
1 for TDD UL/DL configuration 0 with PUSCH transmiss ion in subframe n  4 or 9
I PHICH  
0 otherwise
3GPP
Release 10 82 3GPP TS 36.213 V10.0.0 (2010-12)
Table 9.1.2-2: Mapping between n DMRS and the cyclic shift for DMRS field in PDCCH with uplink DCI
format in [4]
Cyclic Shift for DMRS Field in PDCCH n DMRS

with uplink DCI format in [4]
000 0
001 1
010 2
011 3
100 4
101 5
110 6
111 7
9.1.3 Control Format Indicator assignment procedure

PHICH duration is signalled by higher layers according to Table 6.9.3-1 in [3]. The duration signalled puts a lower
DL
limit on the size of the control region determined from the control format indicator (CFI). When N RB  10 , if
extended PHICH duration is indicated by higher layers then the UE shall assume that CFI is equal to PHICH duration.
9.2 PDCCH validation for semi-persistent scheduling

A UE shall validate a Semi-Persistent Scheduling assignment PDCCH only if all the following conditions are met:
- the CRC parity bits obtained for the PDCCH payload are scrambled with the Semi-Persistent Scheduling C-
RNTI
- the new data indicator field is set to ‘0’. In case of DCI formats 2, 2A, 2B and 2C, the new data indicator field
refers to the one for the enabled transport block.
Validation is achieved if all the fields for the respective used DCI format are set according to Table 9.2-1 or Table 9.2-
1A.
If validation is achieved, the UE shall consider the received DCI information accordingly as a valid semi-persistent
activation or release.
If validation is not achieved, the received DCI format shall be considered by the UE as having been received with a
non-matching CRC.
Table 9.2-1: Special fields for Semi-Persistent Scheduling Activation PDCCH Validation
DCI format 0 DCI format 1/1A DCI format

2/2A/2B/2C
TPC command for set to ‘00’ N/A N/A
scheduled PUSCH
Cyclic shift DM RS set to ‘000’ N/A N/A
Modulation and coding MSB is set to ‘0’ N/A N/A

scheme and
redundancy version
HARQ process N/A FDD: set to ‘000’ FDD: set to ‘000’

number
TDD: set to ‘0000’ TDD: set to ‘0000’
3GPP
Release 10 83 3GPP TS 36.213 V10.0.0 (2010-12)
Modulation and coding N/A MSB is set to ‘0’ For the enabled
scheme transport block:
MSB is set to ‘0’
Redundancy version N/A set to ‘00’ For the enabled

transport block:
set to ‘00’
Table 9.2-1A: Special fields for Semi-Persistent Scheduling Release PDCCH Validation
DCI format 0 DCI format 1A

TPC command for scheduled set to ‘00’ N/A
PUSCH
Cyclic shift DM RS set to ‘000’ N/A
Modulation and coding scheme and set to ‘11111’ N/A

redundancy version
Resource block assignment and Set to all ‘1’s N/A
hopping resource allocation
HARQ process number N/A FDD: set to ‘000’
TDD: set to ‘0000’

Modulation and coding scheme N/A set to ‘11111’
Redundancy version N/A set to ‘00’
Resource block assignment N/A Set to all ‘1’s
For the case that the DCI format indicates a semi-persistent downlink scheduling activation, the TPC command for
PUCCH field shall be used as an index to one of the four PUCCH resource indices configured by higher layers, with the
mapping defined in Table 9.2-2
Table 9.2-2: PUCCH Resource Index for Downlink Semi-Persistent Scheduling
Value of ‘TPC command for (1, p )

nPUCCH
PUCCH’
The first PUCCH resource index
‘00’
configured by the higher layers
The second PUCCH resource index
‘01’
The third PUCCH resource index
‘10’
The fourth PUCCH resource index
‘11’
9.3 PDCCH control information procedure

A UE shall discard the PDCCH if consistent control information is not detected.
3GPP
Release 10 84 3GPP TS 36.213 V10.0.0 (2010-12)
10 Physical uplink control channel procedures
10.1 UE procedure for determining physical uplink control channel

assignment
If the UE is configured for a single serving cell and is not configured for simultaneous PUSCH and PUCCH
transmission, then in subframe n uplink control information (UCI) shall be transmitted
- on PUCCH using format 1/1a/1b or 2/2a/2b if the UE is not transmitting on PUSCH in subframe n
- on PUSCH if the UE is transmitting on PUSCH in subframe n unless the PUSCH transmission corresponds to
a Random Access Response Grant or a retransmission of the same transport block as part of the contention
based random access procedure, in which case UCI is not transmitted
If the UE is configured for a single serving cell and simultaneous PUSCH and PUCCH transmission, then in subframe
n uplink control information shall be transmitted
- on PUCCH using format 1/1a/1b if the uplink control information consists only of HARQ-ACK/SR
- on PUCCH using format 2/2a/2b if the uplink control information consists only of CQI/PMI/RI.
- on [PUCCH using format 1/1a/1b … if the UCI consists of HARQ-ACK and CQI/PMI/RI] <editors note: not
yet decided>
If the UE is configured with more than one serving cell and is not configured for simultaneous PUSCH and PUCCH
transmission, then in subframe n UCI [from a chosen DL serving cell] shall be transmitted
- on PUCCH if the UE is not transmitting on any PUSCH in subframe n if the UCI consists only of periodic
CQI/PMI/RI
- on primary cell PUSCH if the UCI consists of periodic CQI/PMI/RI and/or HARQ-ACK and if the UE is
transmitting on the primary cell PUSCH in subframe n unless the primary cell PUSCH transmission
corresponds to a Random Access Response Grant or a retransmission of the same transport block as part of the
contention based random access procedure, in which case UCI is not transmitted.
- <editor’s note: which Scell chosen is for discussion in RAN1#63bis> on secondary cell PUSCH if the UCI
consists of only periodic CQI/PMI/RI and if the UE is not transmitting on primary cell PUSCH but is
transmitting on at least one secondary cell PUSCH in subframe n . In case of more than one secondary cell
PUSCH transmission in subframe n the UE shall transmit the periodic UCI on the secondary cell PUSCH
[“that has highest priority PUCCH reporting type” -or- “with lowest cell index”].
- [where the chosen DL serving cell is the one with the highest priority based on [TBD]].
- where reporting prioritization of colliding PUCCH reporting types [of the chosen DL serving cell] is given in
Section 7.2.2.
If the UE is configured with more than one serving cell and simultaneous PUSCH and PUCCH transmission, then in
subframe n uplink control information shall be transmitted
- on PUCCH using format 1/1a/1b/3 if the uplink control information consists only of HARQ-ACK/SR
- on PUCCH if the uplink control information consists only of CQI/PMI/RI and is periodic.
- on [PUCCH using format 1/1a/1b/3 … if the UCI consists of HARQ-ACK and CQI/PMI/RI] <editors note: –
not yet decided >
UE transmits PUCCH only on the primary cell.
3GPP
Release 10 85 3GPP TS 36.213 V10.0.0 (2010-12)
Throughout this section, subframes are numbered in monotonically increasing order; if the last subframe of a radio
frame is denoted as k , the first subframe of the next radio frame is denoted as k  1 .
Using the PUCCH formats defined in section 5.4.1 and 5.4.2 in [3], t he following combinations of uplink control
information on PUCCH are supported:
- Format 1a for 1-bit HARQ-ACK or in case of FDD for 1-bit HARQ-ACK with positive SR
- Format 1b for 2-bit HARQ-ACK or for 2-bit HARQ-ACK with positive SR
- Format 1b for up to 4-bit HARQ-ACK with channel selection when UE is configured with more than one serving
cell or in the case for TDD when UE is configured with a single serving cell
- Format 1 for positive SR
- Format 2 for a CQI/PMI or a RI report when not multiplexed with HARQ-ACK
- Format 2a for a CQI/PMI or a RI report multiplexed with 1-bit HARQ-ACK for normal cyclic prefix
- Format 2b for a CQI/PMI or a RI report multiplexed with 2-bit HARQ-ACK for normal cyclic prefix
- Format 2 for a CQI/PMI or a RI report multiplexed with HARQ-ACK for extended cyclic prefix
- Format 3 for up to 10-bit HARQ-ACK for FDD and for up to 20-bit HARQ-ACK for TDD
- Format 3 for up to 11-bit corresponding to 10-bit HARQ-ACK and 1-bit positive/negative SR for FDD and for up to
21-bit corresponding to 20-bit HARQ-ACK and 1-bit positive/negative SR for TDD.
A UE that supports up to 4 ACK/NACK bits shall use PUCCH format 1b with channel selection for transmission of
HARQ-ACK when configured with more than one serving cell.
A UE that supports more than 4 ACK/NACK bits is configured by higher layer signalling to use either PUCCH format
1b with channel selection or PUCCH format 3 for transmission of HARQ-ACK when configured with more than one
serving cell.
For FDD, a UE shall determine the number of HARQ-ACK bits, O , based on the number configured serving cells
and the downlink transmission modes configured for each serving cell. A UE shall use two HARQ-ACK bits for a
serving cell configured with a downlink transmission mode that support up to two transport blocks; and one HARQ-
ACK bit otherwise.
For PUCCH format 3, a UE shall generate a NACK for a DTX HARQ-ACK response for a transport block associated
with a configured serving cell.
The scrambling initialization of PUCCH format 2, 2a and 2b is by C-RNTI.
In case of collision between a CQI/PMI/RI and an HARQ-ACK in a same subframe without PUSCH and the UE is configured
with a single serving cell, the CQI/PMI/RI is multiplexed with HARQ-ACK on PUCCH if the parameter
simultaneousAckNackAndCQI provided by higher layers is set TRUE, otherwise the CQI/PMI/RI is dropped.
In case of collision between a periodic CQI/PMI/RI and an HARQ-ACK in a same subframe with PUSCH, the periodic
CQI/PMI/RI is multiplexed with the HARQ-ACK in the PUSCH transmission in that subframe.
For TDD and one configured serving cell, two ACK/NACK feedback modes are supported by higher layer
configuration.
- ACK/NACK bundling and
- ACK/NACK multiplexing
For TDD UL-DL configuration 5 and one configured serving cell, only ACK/NACK bundling is supported.
TDD ACK/NACK bundling is performed per codeword across M multiple DL subframes associated with a single UL
subframe n, where M is the number of elements in the set K defined in Table 10.1-1, by a logical AND operation
of all the individual PDSCH transmission (with and without corresponding PDCCH) ACK/NACKs and ACK in
response to PDCCH indicating downlink SPS release. For one configured serving cell the bundled 1 or 2 ACK/NACK
bits are transmitted using PUCCH format 1a or PUCCH format 1b, respectively.
3GPP
Release 10 86 3GPP TS 36.213 V10.0.0 (2010-12)
For TDD ACK/NACK multiplexing and a subframe n with M  1 , where M is the number of elements in the set
K defined in Table 10.1-1, spatial ACK/NACK bundling across multiple codewords within a DL subframe is
performed by a logical AND operation of all the corresponding individual ACK/NACKs. PUCCH format 1b with
channel selection is used in case of one configured serving cell. For TDD ACK/NACK multiplexing and a subframe n
with M  1 , spatial ACK/NACK bundling across multiple codewords within a DL subframe is not performed, 1 or 2
ACK/NACK bits are transmitted using PUCCH format 1a or PUCCH format 1b, respectively for one configured
serving cell.
In the case of TDD and more than one configured serving cell with PUCCH format 1b with channel selection and more
than 4 ACK/NACK bits for the configured serving cells, ACK/NACK bundling across multiple codewords within a DL
subframe and across M multiple DL subframes associated with a single UL subframe n is performed for each serving
cell by a logical AND operation of [all or some of] the individual PDSCH transmission (with and without
corresponding PDCCH) ACK/NACKs and ACK in response to PDCCH indicating downlink SPS release. The bundled
[x] ACK/NACK bit[s] for each configured serving cell is transmitted using PUCCH format 1b with channel selection.
For TDD and more than one configured serving cell with PUCCH format 1b with channel selection and up to 4
ACK/NACK bits for the configured serving cells, ACK/NACK bundling is not performed and the ACK/NACK bits are
transmitted using PUCCH format 1b with channel selection.
In the case of TDD and more than one configured serving cell with PUCCH format 3 and more than 20 ACK/NACK
bits for the configured serving cells, spatial ACK/NACK bundling across multiple codewords within a DL subframe is
performed for each serving cell by a logical AND operation of [all or some of] the corresponding individual
ACK/NACKs and PUCCH format 3 is used. For TDD and more than one configured serving cell with PUCCH format 3
and up to 20 ACK/NACK bits for the configured serving cells, spatial ACK/NACK bundling is not performed and the
ACK/NACK bits transmitted using PUCCH format 3.
A UE is configured by higher layers to transmit HARQ-ACK on one antenna port ( p  p0 ) or two antenna ports
( p  [ p0 , p1 ]) .
(1, p )
For FDD and one configured serving cell, the UE shall use PUCCH resource nPUCCH for transmission of HARQ-
ACK in subframe n on antenna port p for PUCCH format 1a/1b, where
- for a PDSCH transmission indicated by the detection of a corresponding PDCCH in subframe n  4 on the
primary cell, or for a PDCCH indicating downlink SPS release (defined in section 9.2) in subframe n  4 on
(1, p  p0 ) (1)
the primary cell, the UE shall use nPUCCH  nCCE  N PUCCH , where nCCE is the number of the first CCE
(i.e. lowest CCE index used to construct the PDCCH) used for transmission of the corresponding DCI
(1)
assignment and N PUCCH is configured by higher layers. For two antenna port transmission the PUCCH
(1, p  p1 )
resource for p  p1 is given by n PUCCH (1)
 nCCE  1  N PUCCH .
- for a PDSCH transmission on the primary cell where there is not a corresponding PDCCH detected in subframe
(1, p )
n  4 , the value of nPUCCH is determined according to higher layer configuration and Table 9.2-2.
< ----------editors note: CA=2 below; for FDD ------------ >
For FDD with more than one configured serving cell and PUCCH format 1b with channel selection, the UE shall
(1, p ) (1, p )
transmit b( 0)b(1) on PUCCH resource nPUCCH selected from A PUCCH resources, nPUCCH, i where
0  i  A  1 and A  [2,3,4] , according to Table 10.1-1a, Table 10.1-1b, Table 10.1-1c in subframe n on antenna
port p using PUCCH format 1b. HARQ-ACK(j) denote the ACK/NACK/DTX response for a transport block or SPS
release PDCCH associated with serving cell, c where the transport block and serving cell denoted by HARQ-ACK(j)
for A PUCCH resources is given by Table 10.1.0. In Tables 10.1-1a, 10.1-1b, and 10.1-1c the superscript p term in
(1, p )
nPUCCH, x has been dropped for convenience.
3GPP
Release 10 87 3GPP TS 36.213 V10.0.0 (2010-12)
Table 10.1-0: Mapping of Transport Block and Serving Cell to HARQ-ACK(j) for PUCCH format 1b
ACK/NACK channel selection
A HARQ-ACK(j)
HARQ-ACK(0) HARQ-ACK(1) HARQ-ACK(2) HARQ-ACK(3)

2 TB1 Primary cell TB2 Secondary cell NA NA
3 TB1 Serving cell1 TB2 Serving cell1 TB3 Serving cell2 NA
4 TB1 Primary cell TB2 Primary cell TB3 Secondary cell TB4 Secondary cell
(1, p )
The UE shall determine the A PUCCH resources, nPUCCH, i where 0  i  A  1 , according to <editor’s note:
PUCCH resources with channel selection and transmit diversity to be decided>
- <editor’s note: the following sub bullet is only a working assumption [for a PDSCH transmission indicated by
the detection of a corresponding PDCCH in subframe n  4 on the primary cell, or for a PDCCH indicating
downlink SPS release (defined in section 9.2) in subframe n  4 on the primary cell, the PUCCH resource [
(1, p  p0 )
i  f ( nCCE , N PUCCH ) ], where nCCE is the number of the first CCE (<editor’s note: exact function
(1)
nPUCCH,
f, and CCE index used to construct the PDCCH to be decided>) used for transmission of the corresponding DCI
(1)
assignment and N PUCCH is configured by higher layers. ]>
- <editor’s note: the following sub bullet is only a working assumption [for a PDSCH transmission on the
(1, p  p0 )
primary cell where there is not a corresponding PDCCH detected in subframe n  4 , the value of nPUCCH, i
is determined according to higher layer configuration and Table 9.2-2.]>
- for a PDSCH transmission indicated by the detection of a corresponding PDCCH in subframe n  4 on the
(1, p  p0 )
secondary cell, the value of nPUCCH, i is determined according to higher layer configuration. <editor’s note:
ARI (refered to herein as ACK/NACK Resource for PUCCH) for Channel Selection case is FFS … then add
“and Table 10.1-1d” similar to Table 9.2-2>
Table 10.1-1a: Transmission of Format 1b ACK/NACK channel selection for A2

(1, p ) b( 0)b(1)
HARQ-ACK(0) HARQ-ACK(1) nPUCCH, i
(1)
ACK ACK n PUCCH,1 1,1
(1)
ACK NACK/DTX n PUCCH,0 1,1
(1)
NACK/DTX ACK n PUCCH,1 0,0
(1)
NACK NACK/DTX n PUCCH,0 0,0
DTX NACK/DTX No Transmission
3GPP
Release 10 88 3GPP TS 36.213 V10.0.0 (2010-12)
Table 10.1-1b: Transmission of Format 1b ACK/NACK channel selection for A  3
(1, p ) b( 0)b(1)
HARQ-ACK(0) HARQ-ACK(1) HARQ-ACK(2) nPUCCH, i
(1)
ACK ACK ACK n PUCCH,1 1,1
(1)
ACK NACK/DTX ACK n PUCCH,1 1,0
(1)
NACK/DTX ACK ACK n PUCCH,1 0,1
(1)
NACK/DTX NACK/DTX ACK n PUCCH,2 1,1
(1)
ACK ACK NACK/DTX n PUCCH,0 1,1
(1)
ACK NACK/DTX NACK/DTX n PUCCH,0 1,0
(1)
NACK/DTX ACK NACK/DTX n PUCCH,0 0,1
(1)
NACK/DTX NACK/DTX NACK n PUCCH,2 0,0
(1)
NACK NACK/DTX DTX n PUCCH,0 0,0
(1)
NACK/DTX NACK DTX n PUCCH,0 0,0
DTX DTX DTX No Transmission
Table 10.1-1c: Transmission of Format 1b ACK/NACK channel selection for A4

(1, p ) b( 0)b(1)
HARQ-ACK(0) HARQ-ACK(1) HARQ-ACK(2) HARQ-ACK(3) nPUCCH, i
(1)
ACK ACK ACK ACK n PUCCH,1 1,1
(1)
ACK NACK/DTX ACK ACK n PUCCH,2 0,1
(1)
NACK/DTX ACK ACK ACK n PUCCH,1 0,1
(1)
NACK/DTX NACK/DTX ACK ACK n PUCCH,3 1,1
(1)
ACK ACK ACK NACK/DTX n PUCCH,1 1,0
(1)
ACK NACK/DTX ACK NACK/DTX n PUCCH,2 0,0
(1)
NACK/DTX ACK ACK NACK/DTX n PUCCH,1 0,0
(1)
NACK/DTX NACK/DTX ACK NACK/DTX n PUCCH,3 1,0
(1)
ACK ACK NACK/DTX ACK n PUCCH,2 1,1
(1)
ACK NACK/DTX NACK/DTX ACK n PUCCH,2 1,0
(1)
NACK/DTX ACK NACK/DTX ACK n PUCCH,3 0,1
(1)
NACK/DTX NACK/DTX NACK/DTX ACK n PUCCH,3 0,0
(1)
ACK ACK NACK/DTX NACK/DTX n PUCCH,0 1,1
(1)
ACK NACK/DTX NACK/DTX NACK/DTX n PUCCH,0 1,0
(1)
NACK/DTX ACK NACK/DTX NACK/DTX n PUCCH,0 0,1
(1)
NACK/DTX NACK NACK/DTX NACK/DTX n PUCCH,0 0,0
(1)
NACK NACK/DTX NACK/DTX NACK/DTX n PUCCH,0 0,0
DTX DTX NACK/DTX NACK/DTX No Transmission
For FDD with more than one configured serving cell and PUCCH format 3, the UE shall use PUCCH resource
( 3, p )
or nPUCCH for transmission of HARQ-ACK in subframe n on antenna port p where
(1, p )
nPUCCH
3GPP
Release 10 89 3GPP TS 36.213 V10.0.0 (2010-12)
- for a PDSCH transmission only on the primary cell indicated by the detection of a corresponding PDCCH in
subframe n  4 , or for a PDCCH indicating downlink SPS release (defined in section 9.2) in subframe
(1, p )
n  4 on the primary cell, the UE shall use PUCCH format 1a/1b and PUCCH resource nPUCCH with
(1, p  p ) (1)
n PUCCH0  nCCE  N PUCCH , where nCCE is the number of the first CCE (i.e. lowest CCE index used to
(1)
construct the PDCCH) used for transmission of the corresponding DCI assignment and N PUCCH is configured
by higher layers. For two antenna port transmission the PUCCH resource for p  p1 is given by
(1, p  p1 ) (1)
n PUCCH  nCCE  1  N PUCCH
- for a PDSCH transmission only on the primary cell where there is not a corresponding PDCCH detected in
(1, p )
subframe n  4 , the UE shall use PUCCH format 1a/1b and PUCCH resource nPUCCH with the value of
(1, p )
nPUCCH is determined according to higher layer configuration and Table 9.2-2.
- for a PDSCH transmission on the secondary cell indicated by the detection of a corresponding PDCCH in
( 3, p )
subframe n  4 , the UE shall use PUCCH format 3 and PUCCH resource nPUCCH with the value of
( 3, p )
nPUCCH is determined according to higher layer configuration and Table 10.1-1d. The TPC command for
PUCCH field in the DCI format of the corresponding PDCCH shall be used to determine the PUCCH resource
values from one of the four resource values configured by higher layers, with the mapping defined in Table
10.1-1d. A UE shall assume that the same HARQ-ACK PUCCH resource value is transmitted on all PDCCH
assignments corresponding to secondary cells.
Table 10.1-1d: PUCCH Resource Value for HARQ-ACK Resource for PUCCH
Value of ‘HARQ-ACK Resource ( 3, p )

nPUCCH
for PUCCH’
The 1st PUCCH resource value
’00’ configured by the higher layers
The 2nd PUCCH resource value
‘01’ configured by the higher layers
The 3rd PUCCH resource value
The 4th PUCCH resource value
<editor’s note: updates to TDD ACK/NACK for more than one configured cell after significant agreements have been
reached >
For TDD ACK/NACK bundling or TDD ACK/NACK multiplexing and a subframe n with M  1 where M is the
(1, p )
number of elements in the set K defined in Table 10.1-1, the UE shall use PUCCH resource nPUCCH for
transmission of HARQ-ACK in subframe n on antenna port p for PUCCH format 1a/1b, where
- If there is PDSCH transmission on the primary cell indicated by the detection of corresponding PDCCH or there
is PDCCH indicating downlink SPS release within subframe(s) n  k , where k  K and K (defined in
Table 10.1-1) is a set of M elements  k0 , k1 ,  k M 1 depending on the subframe n and the UL-DL
configuration (defined in Table 4.2-2 in [3]), the UE first selects a c value out of {0, 1, 2, 3} which makes
N c  nCCE  N c 1 and shall use (1, p  p0 ) (1)
nPUCCH  ( M  m  1)  N c  m  N c 1  nCCE  N PUCCH , where
(1)
N PUCCH is configured by higher layers, N c  max 0,  [ N RB
DL
 RB
 ( N sc  c  4)] / 36  , and nCCE is the
number of the first CCE used for transmission of the corresponding PDCCH in subframe n  km and the
corresponding m, where km is the smallest value in set K such that UE detects a PDCCH in subframe n  km .
3GPP
Release 10 90 3GPP TS 36.213 V10.0.0 (2010-12)
For two antenna port transmission the PUCCH resource for ACK/NACK bundling p  p1 is given by
(1, p  p1 ) (1)
nPUCCH  ( M  m  1)  N c  m  N c 1  nCCE  1  N PUCCH .
- If there is only a PDSCH transmission on the primary cell where there is not a corresponding PDCCH detected
(1)
within subframe(s) n  k , where k  K and K is defined in Table 10.1-1, the value of nPUCCH is
determined according to higher layer configuration and Table 9.2-2.
Table 10.1-1: Downlink association set index K :  k0 , k1 ,  k M 1 for TDD
UL-DL Subframe n
Configuratio
n 0 1 2 3 4 5 6 7 8 9
0 - - 6 - 4 - - 6 - 4
1 - - 7, 6 4 - - - 7, 6 4 -
2 - - 8, 7, 4, 6 - - - - 8, 7, 4, 6 - -
3 - - 7, 6, 11 6, 5 5, 4 - - - - -
4 - - 12, 8, 7, 11 6, 5, 4, 7 - - - - - -
5 - - 13, 12, 9, 8, 7, 5, 4, 11, 6 - - - - - - -
6 - - 7 7 5 - - 7 7 -
For TDD ACK/NACK multiplexing and sub-frame n with M  1 , where M is the number of elements in the set
(1, p )
K defined in Table 10.1-1, denote nPUCCH, i as the PUCCH resource derived from sub-frame n  ki and HARQ-
ACK(i) as the ACK/NACK/DTX response from sub-frame n  ki , where ki  K (defined in Table 10.1-1) and
0  i  M 1.
- For a PDSCH transmission or a PDCCH indicating downlink SPS release in sub-frame n  ki where ki  K ,
(1, p  p 0)
the PUCCH resource nPUCCH, (1)
i  ( M  i  1)  N c  i  N c 1  nCCE,i  N PUCCH , where c is selected from
 
{0, 1, 2, 3} such that N c  nCCE,i  N c 1 , N c  max 0, [ N RB
DL RB
 ( N sc  c  4)] / 36  , nCCE,i is the
(1)
number of the first CCE used for transmission of the corresponding PDCCH in subframe n  ki , and N PUCCH
is configured by higher layers. <editor’s note: p=p_1 case to be decided>
- For a PDSCH transmission where there is not a corresponding PDCCH detected in subframe n  ki , the value
(1, p )
of nPUCCH,i is determined according to higher layer configuration and Table 9.2-2.
(1, p )
The UE shall transmit b(0), b(1) on PUCCH resource nPUCCH in sub-frame n using PUCCH format 1b
(1, p )
according to section 5.4.1 in [3]. The value of b(0), b(1) and the PUCCH resource nPUCCH are generated by
channel selection according to Table 10.1-2, 10.1-3, and 10.1-4 for M = 2, 3, and 4, respectively where the superscript
p term in nPUCCH,
(1, p )
x has been dropped for convenience. In case b (0), b (1) are mapped to “N/A,” then the UE
shall not transmit ACK/NACK response in sub-frame n .
Table 10.1-2: Transmission of ACK/NACK multiplexing for M = 2

(1)
HARQ-ACK(0), HARQ-ACK(1) nPUCCH b(0), b(1)
(1)
ACK, ACK nPUCCH,1 1, 1
(1)
ACK, NACK/DTX nPUCCH,0 0, 1
(1)
NACK/DTX, ACK nPUCCH,1 0, 0
3GPP
Release 10 91 3GPP TS 36.213 V10.0.0 (2010-12)
(1)
NACK/DTX, NACK nPUCCH,1 1, 0
(1)
NACK, DTX nPUCCH,0 1, 0
DTX, DTX N/A N/A

(1)
HARQ-ACK(0), HARQ-ACK(1), HARQ-ACK(2) nPUCCH b(0), b(1)
(1)
ACK, ACK, ACK nPUCCH,2 1, 1
(1)
ACK, ACK, NACK/DTX nPUCCH,1 1, 1
(1)
ACK, NACK/DTX, ACK nPUCCH,0 1, 1
(1)
ACK, NACK/DTX, NACK/DTX nPUCCH,0 0, 1
(1)
NACK/DTX, ACK, ACK nPUCCH,2 1, 0
(1)
NACK/DTX, ACK, NACK/DTX nPUCCH,1 0, 0
(1)
NACK/DTX, NACK/DTX, ACK nPUCCH,2 0, 0
(1)
DTX, DTX, NACK nPUCCH,2 0, 1
(1)
DTX, NACK, NACK/DTX nPUCCH,1 1, 0
(1)
NACK, NACK/DTX, NACK/DTX nPUCCH,0 1, 0
DTX, DTX, DTX N/A N/A

(1)
HARQ-ACK(0), HARQ-ACK(1), HARQ-ACK(2), HARQ-ACK(3) nPUCCH b(0), b(1)
(1)
ACK, ACK, ACK, ACK nPUCCH,1 1, 1
(1)
ACK, ACK, ACK, NACK/DTX nPUCCH,1 1, 0
(1)
NACK/DTX,NACK/DTX,NACK,DTX nPUCCH,2 1, 1
(1)
ACK, ACK, NACK/DTX, ACK nPUCCH,1 1, 0
(1)
NACK, DTX, DTX, DTX nPUCCH,0 1, 0
3GPP
Release 10 92 3GPP TS 36.213 V10.0.0 (2010-12)
(1)
ACK, ACK, NACK/DTX, NACK/DTX nPUCCH,1 1, 0
(1)
ACK, NACK/DTX, ACK, ACK nPUCCH,3 0, 1
(1)
NACK/DTX, NACK/DTX, NACK/DTX, NACK nPUCCH,3 1, 1
(1)
ACK, NACK/DTX, ACK, NACK/DTX nPUCCH,2 0, 1
(1)
ACK, NACK/DTX, NACK/DTX, ACK nPUCCH,0 0, 1
(1)
ACK, NACK/DTX, NACK/DTX, NACK/DTX nPUCCH,0 1, 1
(1)
NACK/DTX, ACK, ACK, ACK nPUCCH,3 0, 1
(1)
NACK/DTX, NACK, DTX, DTX nPUCCH,1 0, 0
(1)
NACK/DTX, ACK, ACK, NACK/DTX nPUCCH,2 1, 0
(1)
NACK/DTX, ACK, NACK/DTX, ACK nPUCCH,3 1, 0
(1)
NACK/DTX, ACK, NACK/DTX, NACK/DTX nPUCCH,1 0, 1
(1)
NACK/DTX, NACK/DTX, ACK, ACK nPUCCH,3 0, 1
(1)
NACK/DTX, NACK/DTX, ACK, NACK/DTX nPUCCH,2 0, 0
(1)
NACK/DTX, NACK/DTX, NACK/DTX, ACK nPUCCH,3 0, 0
DTX, DTX, DTX, DTX N/A N/A
ACK/NACK repetition is enabled or disabled by a UE specific parameter ackNackRepetition configured by higher

layers. Once enabled, the UE shall repeat any ACK/NACK transmission with a repetition factor N ANRep , where
N ANRep is provided by higher layers and includs the initial ACK/NACK transmission, until ACK/NACK
repetition is disabled by higher layers. For a PDSCH transmission without a corresponding PDCCH detected, the
(1, p )
UE shall transmit the corresponding ACK/NACK response N ANRep times using PUCCH resource nPUCCH
configured by higher layers. For a PDSCH transmission with a corresponding PDCCH detected, or for a PDCCH
indicating downlink SPS release, the UE shall first transmit the corresponding ACK/NACK response once using
PUCCH resource derived from the corresponding PDCCH CCE index (as described in Section 10.1), and repeat the
transmission of the corresponding ACK/NACK response N ANRep  1 times always using PUCCH resource
(1, p ) (1, p )
nPUCCH, ANRep , where nPUCCH, ANRep is configured by higher layers.
For TDD, ACK/NACK repetition is only applicable for ACK/NACK bundling and is not applicable for
ACK/NACK multiplexing. <editor’s note: To be determined whether the configured resource that is used for
ACK/NACK repetition is only for antenna port p  p0 .>
A UE is configured by higher layers to transmit the scheduling request (SR) on one antenna port or two antenna
(1, p ) (1, p )
ports. The scheduling request shall be transmitted on the PUCCH resource(s) nPUCCH  nPUCCH, SRI for antenna
(1, p )
port p as defined in [3], where nPUCCH, SRI is configured by higher layers. The SR configuration for SR
3GPP
Release 10 93 3GPP TS 36.213 V10.0.0 (2010-12)
transmission periodicity SRPERIODICITY and SR subframe offset N OFFSET,SR is defined in Table 10.1-5 by the
parameter sr-ConfigIndex I SR given by higher layers.
SR transmission instances are the uplink subframes satisfying

 10  n f  ns / 2  NOFFSET,SR  mod SRPERIODICITY  0 .
Table 10.1-5: UE-specific SR periodicity and subframe offset configuration
SR periodicity (ms)
SR configuration Index I SR SRPERIODICITY SR subframe offset N OFFSET,SR
0–4 5 I SR
5 – 14 10 I SR  5
15 – 34 20 I SR  15
35 – 74 40 I SR  35
75 – 154 80 I SR  75
155 – 156 2 I SR  155
157 1 I SR  157
10.2 Uplink ACK/NACK timing

For FDD, the UE shall upon detection of a PDSCH transmission in subframe n-4 intended for the UE and for which an
ACK/NACK shall be provided, transmit the ACK/NACK response in subframe n. If ACK/NACK repetition is enabled,
upon detection of a PDSCH transmission in subframe n-4 intended for the UE and for which ACK/NACK response
shall be provided, and if the UE is not repeating the transmission of any ACK/NACK in subframe n corresponding to
a PDSCH transmission in subframes n  N ANRep  3 , … , n  5 , the UE:
 shall transmit only the ACK/NACK response (corresponding to the detected PDSCH transmission in
subframe n  4 ) on PUCCH in subframes n , n  1 , …, n  N ANRep  1 ;
 shall not transmit any other signal in subframes n, n  1 , …, n  N ANRep  1 ; and
 shall not transmit any ACK/NACK response repetitions corresponding to any detected PDSCH transmission
in subframes n  3 , …, n  N ANRep  5 .
For TDD, the UE shall upon detection of a PDSCH transmission within subframe(s) n  k , where k  K and K is
defined in Table 10.1-1 intended for the UE and for which ACK/NACK response shall be provided, transmit the
ACK/NACK response in UL subframe n. If ACK/NACK repetition is enabled, upon detection of a PDSCH
transmission within subframe(s) n  k , where k  K and K is defined in Table 10.1-1 intended for the UE and for
which ACK/NACK response shall be provided, and if the UE is not repeating the transmission of any ACK/NACK in
subframe n corresponding to a PDSCH transmission in a DL subframe earlier than subframe n  k , the UE:
 shall transmit only the ACK/NACK response (corresponding to the detected PDSCH transmission in
subframe n  k ) on PUCCH in UL subframe n and the next N ANRep  1 UL subframes denoted as n1 ,
…, nN ANRep 1 ;
3GPP
Release 10 94 3GPP TS 36.213 V10.0.0 (2010-12)
 shall not transmit any other signal in UL subframe n, n1 , …, nN ANRep 1 ; and
 shall not transmit any ACK/NACK response repetitions corresponding to any detected PDSCH transmission
in subframes ni  k , where k  K i , K i is the set defined in Table 10.1-1 corresponding to UL subframe
ni , and 1  i  N ANRep  1 .
For TDD, ACK/NACK bundling, if the UE detects that at least one downlink assignment has been missed as described
in Section 7.3, the UE shall not transmit ACK/NACK in case the UE is not transmitting on PUSCH.
The uplink timing for the ACK corresponding to a detected PDCCH indicating downlink SPS release shall be the same
as the uplink timing for the ACK/NACK corresponding to a detected PDSCH, as defined above.
11 Physical multicast channel related procedures
11.1 UE procedure for receiving the physical multicast channel

The UE shall decode the PMCH when configured by higher layers. The UE may assume that an eNB transmission on
the PMCH is performed according to Section 6.5 of [3].
The I MCS for the PMCH is configured by higher layers. The UE shall use I MCS for the PMCH and Table 7.1.7.1-1 to
determine the modulation order ( Q m ) and TBS index ( I TBS ) used in the PMCH. The UE shall then follow the
DL
procedure in Section 7.1.7.2.1 to determine the transport block size, assuming N PRB is equal to N RB .
11.2 UE procedure for receiving MCCH change notification

If a UE is configured by higher layers to decode PDCCHs with the CRC scrambled by the M-RNTI, the UE shall
decode the PDCCH according to the combination defined in table 11.2-1.
Table 11.2-1: PDCCH configured by M-RNTI

DCI format 1C Common
The 8-bit information for MCCH change notification [11], as signalled on the PDCCH, shall be delivered to higher
layers.
3GPP
Release 10 95 3GPP TS 36.213 V10.0.0 (2010-12)
Annex A (informative):
Change history
Change history
Date TSG # TSG Doc. CR Rev Subject/Comment Old New
2006-09 Draft version created 0.0.0
2006-10 Endorsed by RAN1 0.0.0 0.1.0
2007-01 Inclusion of decisions from RAN1#46bis and RAN1#47 0.1.0 0.1.1
2007-01 Endorsed by RAN1 0.1.1 0.2.0
2007-02 Inclusion of decisions from RAN1#47bis 0.2.0 0.2.1
2007-02 Endorsed by RAN1 0.2.1 0.3.0
2007-02 Editor’s version including decisions from RAN1#48 & RAN1#47bis 0.3.0 0.3.1
2007-03 Updated Editor’s version 0.3.1 0.3.2
2007-03 RAN#35 RP-070171 For information at RAN#35 0.3.2 1.0.0
2007-03 Random access text modified to better reflect RAN1 scope 1.0.0 1.0.1
2007-03 Endorsed by RAN1 1.0.2 1.1.0
2007-05 Endorsed by RAN1 1.1.2 1.2.0
2007-08 Updated Editor’s version – uplink power control from RAN1#49bis 1.2.1 1.2.2
2007-08 Endorsed by RAN1 1.2.2 1.3.0
2007-09 Updated Editor’s version reflecting RAN#50 decisions 1.3.0 1.3.1
2007-09 Updated Editor’s version reflecting comments 1.3.1 1.3.2
2007-09 Updated Editor’s version reflecting further comments 1.3.2 1.3.3
2007-09 Updated Editor’s version reflecting further comments 1.3.3 1.3.4
2007-09 Updated Edtior’s version reflecting further comments 1.3.4 1.3.5
2007-09 RAN#37 RP-070731 Endorsed by RAN1 1.3.5 2.0.0
2007-09 RAN#37 RP-070737 For approval at RAN#37 2.0.0 2.1.0
12/09/07 RAN_37 RP-070737 - - Approved version 2.1.0 8.0.0
28/11/07 RAN_38 RP-070949 0001 2 Update of 36.213 8.0.0 8.1.0
05/03/08 RAN_39 RP-080145 0002 - Update of TS36.213 according to changes listed in cover sheet 8.1.0 8.2.0
28/05/08 RAN_40 RP-080434 0003 1 PUCCH timing and other formatting and typo corrections 8.2.0 8.3.0
28/05/08 RAN_40 RP-080434 0006 1 PUCCH power control for non-unicast information 8.2.0 8.3.0
28/05/08 RAN_40 RP-080434 0008 - UE ACK/NACK Procedure 8.2.0 8.3.0
28/05/08 RAN_40 RP-080434 0009 - UL ACK/NACK timing for TDD 8.2.0 8.3.0
28/05/08 RAN_40 RP-080434 0010 - Specification of UL control channel assignment 8.2.0 8.3.0
28/05/08 RAN_40 RP-080434 0011 - Precoding Matrix for 2Tx Open-loop SM 8.2.0 8.3.0
28/05/08 RAN_40 RP-080434 0012 - Clarifications on UE selected CQI reports 8.2.0 8.3.0
28/05/08 RAN_40 RP-080434 0013 1 UL HARQ Operation and Timing 8.2.0 8.3.0
28/05/08 RAN_40 RP-080434 0014 - SRS power control 8.2.0 8.3.0
28/05/08 RAN_40 RP-080434 0015 1 Correction of UE PUSCH frequency hopping procedure 8.2.0 8.3.0
28/05/08 RAN_40 RP-080434 0017 4 Blind PDCCH decoding 8.2.0 8.3.0
28/05/08 RAN_40 RP-080434 0019 1 Tx Mode vs DCI format is clarified 8.2.0 8.3.0
28/05/08 RAN_40 RP-080434 0020 - Resource allocation for distributed VRB 8.2.0 8.3.0
28/05/08 RAN_40 RP-080434 0021 2 Power Headroom 8.2.0 8.3.0
28/05/08 RAN_40 RP-080434 0022 - Clarification for RI reporting in PUCCH and PUSCH reporting 8.2.0 8.3.0
modes
28/05/08 RAN_40 RP-080434 0025 - Correction of the description of PUSCH power control for TDD 8.2.0 8.3.0
28/05/08 RAN_40 RP-080434 0026 - UL ACK/NACK procedure for TDD 8.2.0 8.3.0
28/05/08 RAN_40 RP-080434 0027 - Indication of radio problem detection 8.2.0 8.3.0
28/05/08 RAN_40 RP-080434 0028 - Definition of Relative Narrowband TX Power Indicator 8.2.0 8.3.0
28/05/08 RAN_40 RP-080434 0029 - Calculation of ΔTF(i) for UL-PC 8.2.0 8.3.0
28/05/08 RAN_40 RP-080434 0030 - CQI reference and set S definition, CQI mode removal, and 8.2.0 8.3.0
Miscellanious
28/05/08 RAN_40 RP-080434 0031 - Modulation order and TBS determination for PDSCH and PUSCH 8.2.0 8.3.0
28/05/08 RAN_40 RP-080434 0032 - On Sounding RS 8.2.0 8.3.0
28/05/08 RAN_40 RP-080426 0033 - Multiplexing of rank and CQI/PMI reports on PUCCH 8.2.0 8.3.0
28/05/08 RAN_40 RP-080466 0034 - Timing advance command responding time 8.2.0 8.3.0
09/09/08 RAN_41 RP-080670 37 2 SRS hopping pattern for closed loop antenna selection 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 39 2 Clarification on uplink power control 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 41 - Clarification on DCI formats using resource allocation type 2 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 43 2 Clarification on tree structure of CCE aggregations 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 46 2 Correction of the description of PUCCH power control for TDD 8.3.0 8.4.0
3GPP
Release 10 96 3GPP TS 36.213 V10.0.0 (2010-12)
Change history
09/09/08 RAN_41 RP-080670 47 1 Removal of CR0009 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 48 1 Correction of mapping of cyclic shift value to PHICH modifier 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 49 - TBS disabling for DCI formats 2 and 2A 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 50 - Correction of maximum TBS sizes 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 Completion of the table specifying the number of bits for the 8.3.0 8.4.0
51 -
periodic feedback
09/09/08 RAN_41 RP-080670 Clarification of RNTI for PUSCH/PUCCH power control with DCI 8.3.0 8.4.0
54 -
formats 3/3A
09/09/08 RAN_41 RP-080670 55 1 Clarification on mapping of Differential CQI fields 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 59 1 PUSCH Power Control 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 RB restriction and modulation order for CQI-only transmission on 8.3.0 8.4.0
60 -
PUSCH
09/09/08 RAN_41 RP-080670 61 - Modulation order determination for uplink retransmissions 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 62 2 Introducing missing L1 parameters into 36.213 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 63 2 Correcting the range and representation of delta_TF_PUCCH 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 64 1 Adjusting TBS sizes to for VoIP 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 67 - Correction to the downlink resource allocation 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 68 - Removal of special handling for PUSCH mapping in PUCCH region 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 69 - Correction to the formulas for uplink power control 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 70 1 Definition of Bit Mapping for DCI Signalling 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 71 - Clarification on PUSCH TPC commands 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 72 1 Reference for CQI/PMI Reporting Offset 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 74 - Correction to the downlink/uplink timing 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 75 - Correction to the time alignment command 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 77 1 Correction of offset signalling of UL Control information MCS 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 78 2 DCI format1C 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 80 - Correction to Precoder Cycling for Open-loop Spatial Multiplexing 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 81 1 Clarifying Periodic CQI Reporting using PUCCH 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 84 1 CQI reference measurement period 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 86 - Correction on downlink multi-user MIMO 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 87 - PUCCH Reporting 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 88 1 Handling of Uplink Grant in Random Access Response 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 89 - Correction to UL Hopping operation 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 90 - DRS EPRE 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 92 - Uplink ACK/NACK mapping for TDD 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 93 - UL SRI Parameters Configuration 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 94 - Miscellaneous updates for 36.213 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 95 - Clarifying Requirement for Max PDSCH Coding Rate 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 96 - UE Specific SRS Configuration 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 97 - DCI Format 1A changes needed for scheduling Broadcast Control 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 98 - Processing of TPC bits in the random access response 8.3.0 8.4.0
09/09/08 RAN_41 RP-080670 100 1 Support of multi-bit ACK/NAK transmission in TDD 8.3.0 8.4.0
03/12/08 RAN_42 RP-081075 82 3 Corrections to RI for CQI reporting 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 83 2 Moving description of large delay CDD to 36.211 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 102 3 Reception of DCI formats 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 105 8 Alignment of RAN1/RAN2 specification 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 General correction of reset of power control and random access 8.4.0 8.5.0
107 1
response message
03/12/08 RAN_42 RP-081075 108 2 Final details on codebook subset restrictions 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 109 - Correction on the definition of Pmax 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 112 2 CQI/PMI reference measurement periods 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 113 - Correction of introduction of shortened SR 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 114 - RAN1/2 specification alignment on HARQ operation 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 115 - Introducing other missing L1 parameters in 36.213 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 116 - PDCCH blind decoding 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 117 - PDCCH search space 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 119 - Delta_TF for PUSCH 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 Delta_preamble_msg3 parameter values and TPC command in RA 8.4.0 8.5.0
120 -
response
03/12/08 RAN_42 RP-081075 122 1 Correction of offset signaling of uplink control information MCS 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 124 - Miscellaneous Corrections 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 125 - Clarification of the uplink index in TDD mode 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 126 - Clarification of the uplink transmission configurations 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 127 2 Correction to the PHICH index assignment 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 128 - Clarification of type-2 PDSCH resource allocation for format 1C 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 129 - Clarification of uplink grant in random access response 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 130 - UE sounding procedure 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 Change for determining DCI format 1A TBS table column indicator 8.4.0 8.5.0
134 -
for broadcast control
03/12/08 RAN_42 RP-081075 135 - Clarifying UL VRB Allocation 8.4.0 8.5.0
3GPP
Release 10 97 3GPP TS 36.213 V10.0.0 (2010-12)
Change history
03/12/08 RAN_42 RP-081075 136 1 Correction for Aperiodic CQI 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 137 1 Correction for Aperiodic CQI Reporting 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 138 1 Correction to PUCCH CQI reporting mode for N^DL_RB <= 7 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 140 1 On sounding procedure in TDD 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 141 1 Alignment of RAN1/RAN3 specification 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 143 1 TTI bundling 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 144 1 ACK/NACK transmission on PUSCH for LTE TDD 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 145 1 Timing relationship between PHICH and its associated PUSCH 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 Definition of parameter for downlink reference signal transmit 8.4.0 8.5.0
147 1
power
03/12/08 RAN_42 RP-081075 148 1 Radio link monitoring 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 149 1 Correction in 36.213 related to TDD downlink HARQ processes 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 151 - Nominal PDSCH-to-RS EPRE Offset for CQI Reporting 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 152 1 Support of UL ACK/NAK repetition in Rel-8 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 155 - Clarification of misconfiguration of aperiodic CQI and SR 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 Correction of control information multiplexing in subframe bundling 8.4.0 8.5.0
156 1
mode
03/12/08 RAN_42 RP-081075 157 - Correction to the PHICH index assignment 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 158 1 UE transmit antenna selection 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 159 - Clarification of spatial different CQI for CQI reporting Mode 2-1 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 160 1 Corrections for TDD ACK/NACK bundling and multiplexing 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 161 - Correction to RI for Open-Loop Spatial Multiplexing 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 162 - Correction of differential CQI 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 163 - Inconsistency between PMI definition and codebook index 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 164 - PDCCH validation for semi-persistent scheduling 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 Correction to the UE behavior of PUCCH CQI piggybacked on 8.4.0 8.5.0
165 1
PUSCH
03/12/08 RAN_42 RP-081075 Correction on SRS procedure when shortened PUCCH format is 8.4.0 8.5.0
166 -
used
03/12/08 RAN_42 RP-081075 Transmission overlapping of physical channels/signals with PDSCH 8.4.0 8.5.0
167 1
for transmission mode 7
03/12/08 RAN_42 RP-081075 169 - Clarification of SRS and SR transmission 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 171 - Clarification on UE behavior when skipping decoding 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 172 1 PUSCH Hopping operation corrections 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 173 - Clarification on message 3 transmission timing 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 174 - MCS handling for DwPTS 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 Clarification of UE-specific time domain position for SR 8.4.0 8.5.0
175 -
transmission
03/12/08 RAN_42 RP-081075 176 1 Physical layer parameters for CQI reporting 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 177 - A-periodic CQI clarification for TDD UL/DL configuration 0 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 Correction to the definitions of rho_A and rho_B (downlink power 8.4.0 8.5.0
179 1
allocation)
03/12/08 RAN_42 RP-081075 180 - Clarification of uplink A/N resource indication 8.4.0 8.5.0
03/12/08 RAN_42 RP-081075 PDCCH format 0 for message 3 adaptive retransmission and 8.4.0 8.5.0
181 - transmission of control information in message 3 during contention
based random access procedure
03/12/08 RAN_42 RP-081075 To Fix the Discrepancy of Uplink Power Control and Channel 8.4.0 8.5.0
182 -
Coding of Control Information in PUSCH
03/12/08 RAN_42 RP-081122 183 1 CQI reporting for antenna port 5 8.4.0 8.5.0
03/12/08 RAN_42 RP-081110 168 1 Clarification on path loss definition 8.4.0 8.5.0
04/03/09 RAN_43 RP-090236 184 1 Corrections to Transmitted Rank Indication 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 185 4 Corrections to transmission modes 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 186 2 Delta_TF configuration for control only PUSCH 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 187 1 Correction to concurrent SRS and ACK/NACK transmission 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 191 1 PDCCH release for semi-persistent scheduling 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 192 1 Correction on ACKNACK transmission on PUSCH for LTE TDD 8.5.0 8.6.0
04/03/09 RAN_43 193 - Correction to subband differential CQI value to offset level mapping 8.5.0 8.6.0
RP-090236
for aperiodic CQI reporting
04/03/09 RAN_43 RP-090236 194 - Correction for DRS Collision handling 8.5.0 8.6.0
04/03/09 RAN_43 196 2 Alignment of RAN1/RAN4 specification on UE maximum output 8.5.0 8.6.0
RP-090236
power
04/03/09 RAN_43 RP-090236 197 - Transmission scheme for transmission mode 7 with SPS C-RNTI 8.5.0 8.6.0
04/03/09 RAN_43 198 - Clarifying bandwidth parts for periodic CQI reporting and CQI 8.5.0 8.6.0
RP-090236
refererence period
04/03/09 RAN_43 199 2 Correction to the ACK/NACK bundling in case of transmission 8.5.0 8.6.0
RP-090236
mode 3 and 4
04/03/09 RAN_43 RP-090236 200 - ACK/NAK repetition for TDD ACK/NAK multiplexing 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 201 - Clarifying UL ACK/NAK transmission in TDD 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 202 - Corrections to UE Transmit Antenna Selection 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 203 - Correction to UE PUSCH hopping procedure 8.5.0 8.6.0
3GPP
Release 10 98 3GPP TS 36.213 V10.0.0 (2010-12)
Change history
04/03/09 RAN_43 RP-090236 204 - Correction to PHICH resource association in TTI bundling 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 205 - Clarification of the length of resource assignment 8.5.0 8.6.0
04/03/09 RAN_43 206 - Correction on ACK/NACK transmission for downlink SPS resource 8.5.0 8.6.0
RP-090236
release
04/03/09 RAN_43 RP-090236 207 - Introduction of additional values of wideband CQI/PMI periodicities 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 208 2 Correction to CQI/PMI/RI reporting field 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 209 2 Correction to rho_A definition for CQI calculation 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 210 - Correction to erroneous cases in PUSCH linear block codes 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 211 1 Removing RL monitoring start and stop 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 214 1 Correction to type-1 and type-2 PUSCH hopping 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 215 - Contradicting statements on determination of CQI subband size 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 216 - Corrections to SRS 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 219 2 Miscellaneous corrections on TDD ACKNACK 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 221 1 CR for Redundancy Version mapping function for DCI 1C 8.5.0 8.6.0
04/03/09 RAN_43 223 - Scrambling of PUSCH corresponding to Random Access 8.5.0 8.6.0
RP-090236
Response Grant
04/03/09 RAN_43 RP-090236 225 - Removal of SRS with message 3 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 226 3 PRACH retransmission timing 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 227 - Clarifying error handling of PDSCH and PUSCH assignments 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 228 - Clarify PHICH index mapping 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 229 - Correction of CQI timing 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 230 - Alignment of CQI parameter names with RRC 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 231 1 Removal of ‘Off’ values for periodic reporting in L1 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 232 - Default value of RI 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 233 1 Clarification of uplink timing adjustments 8.5.0 8.6.0
04/03/09 RAN_43 RP-090236 234 - Clarification on ACK/NAK repetition 8.5.0 8.6.0
27/05/09 RAN_44 235 1 Correction to the condition of resetting accumulated uplink power 8.6.0 8.7.0
RP-090529
correction
27/05/09 RAN_44 236 - Correction to the random access channel parameters received from 8.6.0 8.7.0
RP-090529
higher layer
27/05/09 RAN_44 RP-090529 237 - Correction on TDD ACKNACK 8.6.0 8.7.0
27/05/09 RAN_44 RP-090529 238 1 Correction on CQI reporting 8.6.0 8.7.0
27/05/09 RAN_44 RP-090529 239 - Correction on the HARQ process number 8.6.0 8.7.0
27/05/09 RAN_44 RP-090529 241 1 CR correction of the description on TTI-bundling 8.6.0 8.7.0
27/05/09 RAN_44 242 1 Clarify latest and initial PDCCH for PDSCH and PUSCH 8.6.0 8.7.0
RP-090529
transmisisons, and NDI for SPS activation
27/05/09 RAN_44 RP-090529 243 - Clarify DRS EPRE 8.6.0 8.7.0
27/05/09 RAN_44 RP-090529 244 1 Clarification on TPC commands for SPS 8.6.0 8.7.0
15/09/09 RAN_45 RP-090888 245 1 Correction to PUSCH hopping and PHICH mapping procedures 8.7.0 8.8.0
15/09/09 RAN_45 RP-090888 246 - Clarification on subband indexing in periodic CQI reporting 8.7.0 8.8.0
15/09/09 RAN_45 RP-090888 247 2 Correction to DVRB operation in TDD transmission mode 7 8.7.0 8.8.0
15/09/09 RAN_45 249 - Clarification of concurrent ACKNACK and periodic PMI/RI 8.7.0 8.8.0
RP-090888
transmission on PUCCH for TDD
15/09/09 RAN_45 RP-090888 250 - Clarify Inter-cell synchronization text 8.7.0 8.8.0
01/12/09 RAN_46 RP-091172 248 1 Introduction of LTE positioning 8.8.0 9.0.0
01/12/09 RAN_46 RP-091172 254 - Clarification of PDSCH and PRS in combination for LTE positioning 8.8.0 9.0.0
01/12/09 RAN_46 RP-091177 255 5 Editorial corrections to 36.213 8.8.0 9.0.0
01/12/09 RAN_46 RP-091257 256 1 Introduction of enhanced dual layer transmission 8.8.0 9.0.0
01/12/09 RAN_46 RP-091177 257 1 Add shorter SR periodicity 8.8.0 9.0.0
01/12/09 RAN_46 RP-091256 258 - Introduction of LTE MBMS 8.8.0 9.0.0
17/12/09 RAN_46 256 1 Correction by MCC due to wrong implementation of CR0256r1 – 9.0.0 9.0.1
RP-091257
Sentence is added to Single-antenna port scheme section 7.1.1
16/03/10 RAN_47 259 3 UE behavior when collision of antenna port 7/8 with PBCH or SCH 9.0.1 9.1.0
RP-100211
happened and when distributed VRB is used with antenna port 7
16/03/10 RAN_47 RP-100210 260 1 MCCH change notification using DCI format 1C 9.0.1 9.1.0
16/03/10 RAN_47 263 - Correction on PDSCH EPRE and UE-specific RS EPRE for Rel-9 9.0.1 9.1.0
RP-100211
enhanced DL transmissions
01/06/10 RAN_48 265 - Clarification for TDD when multiplexing ACK/NACK with SR of 9.1.0 9.2.0
RP-100589
ACK/NACK with CQI/PMI or RI
01/06/10 RAN_48 RP-100590 268 1 Clarification of PRS EPRE 9.1.0 9.2.0
14/09/10 RAN_49 RP-100900 269 - Clarification on Extended CP support with Transmission Mode 8 9.2.0 9.3.0
07/12/10 RAN_50 RP-101320 270 - Introduction of Rel-10 LTE-Advanced features in 36.213 9.3.0 10.0.0
3GPP

3GPP TS 36.213

Uploaded by

Copyright:

Available Formats

3GPP TS 36.213

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3GPP TS 36.213

Uploaded by

Copyright:

Available Formats

3rd Generation Partnership Project;

3GPP support office address

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

7.1.7.2 Transport block size determination........................................................................................................32

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

x the first digit:

1 presented to TSG for information;

2 presented to TSG for approval;

3 or greater indicates TSG approved document under change control.

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

[1] 3GPP TR 21.905: “Vocabulary for 3GPP Specifications”

3 Definitions, symbols, and abbreviations

nf System frame number as defined in [3]

4.1 Cell search

4.2 Timing synchronisation

4.2.2 Inter-cell synchronisation

4.2.3 Transmission timing adjustments

4.3 Timing for Secondary Cell Activation / Deactivation

5.1 Uplink power control

5.1.1 Physical uplink shared channel

 PˆPUCCH (i ) is the linear value of PPUCCH (i ) defined in section 5.1.2.1

 K r / N RE for other cases.

o f c (i )  f c (i  1)   PUSCH,c (i  K PUSCH ) if accumulation is enabled based on the parameter

 The value of K PUSCH is

 For FDD, K PUSCH = 4

 For TDD UL/DL configurations 1-6, K PUSCH is given in Table 5.1.1.1-1

 For TDD UL/DL configuration 0

 The value of K PUSCH is

 For FDD, K PUSCH = 4

 For TDD UL/DL configurations 1-6, K PUSCH is given in Table 5.1.1.1-1

 For TDD UL/DL configuration 0

o For all other PUSCH transmissions, K PUSCH is given in Table 5.1.1.1-1.

 f c (i )  f c (i  1) for a subframe where no PDCCH with DCI format 0 is decoded for

 If PO_UE_PUSCH,c value is changed by higher layers and serving cell c is the

 where  msg 2 is the TPC command indicated in the random

TDD UL/DL subframe number i

TPC Command Field in Accumulated  PUSCH,c

5.1.1.2 Power headroom

where, PCMAX , c , M PUSCH,c (i ) , PO_PUSCH, c ( j ) ,  c ( j ). , PLc ,  TF , c (i ) and f c (i ) are defined in

PH type1,c (i )  PCMAX, c (i )   PO_PUSCH,c ( j )   c ( j )  PLc  f c (i )  [dB]

10 10 log10 ( M PUSCH,c ( i ))  PO_PUSCH,c ( j )   c ( j )  PLc   TF, c ( i )  f c ( i )  10 

where, PCMAX,c , M PUSCH,c (i ) , PO_PUSCH, c ( j ) ,  c ( j )  TF , c (i ) and f c (i ) are the primary cell

 10 10 log10 ( M PUSCH, c ( i ))  PO_PUSCH,c ( j )   c ( j )  PLc   TF, c ( i )  f c ( i )  10 

where, PCMAX,c (i ) , M PUSCH,c (i ) , PO_PUSCH, c ( j ) ,  c ( j )  TF , c (i ) and f c (i ) are the primary cell

10  PO_PUSCH,c (1)   c (1)  PLc  f c ( i )  10 

10  PO_PUSCH,c (1)   c (1)  PLc  f c ( i )  10 

5.1.2 Physical uplink control channel

o For PUCCH format 1,1a and 1b h nCQI , n HARQ , n SR  0  

cell, h(nCQI , nHARQ , nSR ) 

state and where g  0  is the first value after reset.

 For FDD, M  1 and k 0  4 .

 g (0)  Prampup   msg 2

o where  msg 2 is the TPC command indicated in the random access

TPC Command Field in

TPC Command Field in  PUCCH [dB]

5.1.3 Sounding Reference Symbol

5.2 Downlink power allocation

  A is equal to  power -offset  PA [dB] otherwise

5.2.1 eNodeB Relative Narrowband TX Power restrictions