3GPP TS 36.213 V8.1.0 (2007-11)
`
`Technical Specification
`
`
`
`3rd Generation Partnership Project;
`Technical Specification Group Radio Access Network;
`Evolved Universal Terrestrial Radio Access (E-UTRA);
`Physical layer procedures
`(Release 8)
`
`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.
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2007 (3GPP TS 36.213 v8.1) – 001
`IPR2017-01508
`
`

`

`
`Release 8
`
`2
`
`3GPP TS 36.213 V8.1.0 (2007-11)
`
`
`
`
`
`
`
`
`
`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.
`
`© 2007, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
`All rights reserved.
`
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2007 (3GPP TS 36.213 v8.1) – 002
`IPR2017-01508
`
`

`

`
`Release 8
`
`3
`
`3GPP TS 36.213 V8.1.0 (2007-11)
`
`Contents
`Foreword ............................................................................................................................................................ 5
`1
`Scope ........................................................................................................................................................ 6
`2
`References ................................................................................................................................................ 6
`3
`Definitions, symbols, and abbreviations .................................................................................................. 6
`3.1
`Symbols ................................................................................................................................................................. 6
`3.2
`Abbreviations ........................................................................................................................................................ 6
`4
`Synchronisation procedures ..................................................................................................................... 7
`4.1
`Cell search ............................................................................................................................................................. 7
`4.2
`Timing synchronisation ........................................................................................................................................ 7
`4.2.1
`Synchronisation primitives.............................................................................................................................. 7
`4.2.2
`Radio link monitoring ..................................................................................................................................... 7
`4.2.3
`Inter-cell synchronisation ................................................................................................................................ 7
`4.2.4
`Transmission timing adjustments ................................................................................................................... 7
`5
`Power control ........................................................................................................................................... 8
`5.1
`Uplink power control ............................................................................................................................................ 8
`5.1.1
`Physical uplink shared channel ....................................................................................................................... 8
`5.1.1.1
`UE behaviour ............................................................................................................................................. 8
`5.1.1.2
`eNodeB behaviour ..................................................................................................................................... 9
`5.1.2
`Physical uplink control channel ...................................................................................................................... 9
`5.1.2.1
`UE behaviour ............................................................................................................................................. 9
`5.1.2.2
`eNodeB behaviour ................................................................................................................................... 10
`5.1.3
`Sounding Reference Symbol ......................................................................................................................... 10
`5.1.3.1
`UE behaviour ........................................................................................................................................... 10
`5.1.3.2
`eNodeB behaviour ................................................................................................................................... 10
`5.2
`Downlink power allocation ................................................................................................................................. 10
`5.2.1
`UE behaviour ................................................................................................................................................. 11
`5.2.2
`eNodeB behaviour ......................................................................................................................................... 11
`5.2.3
`Downlink channel subcarrier transmit power offset .................................................................................... 11
`6
`Random access procedure ...................................................................................................................... 11
`6.1
`Physical non-synchronized random access procedure ....................................................................................... 11
`6.1.1
`Timing ........................................................................................................................................................... 12
`6.1.1.1
`Synchronized ........................................................................................................................................... 12
`6.1.1.2
`Unsynchronized ....................................................................................................................................... 12
`6.1.2
`Preamble Sequence selection ........................................................................................................................ 12
`7
`Physical downlink shared channel related procedures ........................................................................... 12
`7.1.
`UE procedure for receiving the physical downlink shared channel .................................................................. 12
`7.1.1
`Resource allocation type 0 ............................................................................................................................ 12
`7.1.2
`Resource allocation type 1 ............................................................................................................................ 12
`7.1.3
`Resource allocation type 2 ............................................................................................................................ 12
`7.2
`UE procedure for reporting channel quality indication (CQI), precoding matrix indicator (PMI) and rank ... 13
`7.2.1
`Aperiodic/Periodic CQI Reporting using PUSCH ....................................................................................... 13
`7.2.2
`Periodic CQI Reporting using PUCCH ........................................................................................................ 14
`7.2.3
`Channel quality indicator (CQI) definition ................................................................................................... 15
`7.2.4
`Precoding definition ...................................................................................................................................... 15
`8
`Physical uplink shared channel related procedures ................................................................................ 15
`8.1
`eNodeB procedure for receiving physical uplink shared channel ..................................................................... 15
`8.2
`UE sounding procedure ....................................................................................................................................... 16
`8.2.1
`Sounding definition ....................................................................................................................................... 16
`8.3
`UE ACK/NACK procedure ................................................................................................................................ 16
`9
`Physical downlink control channel procedures ...................................................................................... 16
`9.1
`UE procedure for determining physical downlink control channel assignment ................................................ 16
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2007 (3GPP TS 36.213 v8.1) – 003
`IPR2017-01508
`
`

`

`
`Release 8
`
`4
`
`3GPP TS 36.213 V8.1.0 (2007-11)
`
`Physical uplink control channel procedures ........................................................................................... 16
`10
`UE procedure for determining physical uplink control channel assignment ..................................................... 16
`10.1
`Uplink ACK/NACK timing ................................................................................................................................ 16
`10.2
`Change history ............................................................................................... 17
`Annex A (informative):
`
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2007 (3GPP TS 36.213 v8.1) – 004
`IPR2017-01508
`
`

`

`
`Release 8
`
`5
`
`3GPP TS 36.213 V8.1.0 (2007-11)
`
`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
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2007 (3GPP TS 36.213 v8.1) – 005
`IPR2017-01508
`
`

`

`
`Release 8
`
`6
`
`3GPP TS 36.213 V8.1.0 (2007-11)
`
`Scope
`1
`The present document specifies and establishes the characteristics of the physicals layer procedures in the FDD and
`TDD modes of E-UTRA.
`
`References
`2
`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]
`
`[2]
`
`[3]
`
`[4]
`
`[5]
`
`
`
`3GPP TR 21.905: “Vocabulary for 3GPP Specifications”
`
`3GPP TS 36.201: “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Layer –
`General Description”
`
`3GPP TS 36.211: “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and
`modulation”
`
`3GPP TS 36.212: “Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and
`channel coding”
`
`3GPP TS 36.214: “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer –
`Measurements”
`
`3
`
`Definitions, symbols, and abbreviations
`
`Symbols
`3.1
`For the purposes of the present document, the following symbols apply:
`
`DL
`RBN
`UL
`RBN
`sT
`
`
`
`RB
`scN as defined in [3]
`Downlink bandwidth configuration, expressed in units of
`RB
`Uplink bandwidth configuration, expressed in units of
`scN as defined in [3]
`Basic time unit as defined in [3]
`
`Abbreviations
`3.2
`For the purposes of the present document, the following abbreviations apply.
`
`ACK
`BCH
`CCE
`CCPCH
`CQI
`
`Acknowledgement
`Broadcast Channel
`Control Channel Element
`Common Control Physical Channel
`Channel Quality Indicator
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2007 (3GPP TS 36.213 v8.1) – 006
`IPR2017-01508
`
`

`

`
`Release 8
`
`7
`
`3GPP TS 36.213 V8.1.0 (2007-11)
`
`CRC
`DL
`DTX
`EPRE
`MCS
`NACK
`PCFICH
`PDSCH
`PHICH
`PRACH
`PRB
`PUCCH
`PUSCH
`QoS
`RBG
`RE
`RPF
`RS
`SIR
`SINR
`SRS
`TA
`TTI
`UE
`UL
`VRB
`
`Cyclic Redundancy Check
`Downlink
`Discontinuous Transmission
`Energy Per Resource Element
`Modulation and Coding Scheme
`Negative Acknowledgement
`Physical Control Format Indicator Channel
`Physical Downlink Shared Channel
`Physical Hybrid ARQ Indicator Channel
`Physical Random Access Channel
`Physical Resource Block
`Physical Uplink Control Channel
`Physical Uplink Shared Channel
`Quality of Service
`Resource Block Group
`Resource Element
`Repetition Factor
`Reference Signal
`Signal-to-Interference Ratio
`Signal to Interference plus Noise Ratio
`Sounding Reference Symbol
`Time alignment
`Transmission Time Interval
`User Equipment
`Uplink
`Virtual Resource Block
`
`4
`
`Synchronisation procedures
`
`Cell search
`4.1
`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
`
`Synchronisation primitives
`
`4.2.2
`
`Radio link monitoring
`
`Inter-cell synchronisation
`4.2.3
`[For example, for cell sites with a multicast physical channel]
`
`Transmission timing adjustments
`4.2.4
`Upon reception of a timing advance command, the UE shall adjust its uplink transmission timing. The timing advance
`command is expressed in multiples of 16 sT and is relative to the current uplink timing.
`
`For a timing advance command received on subframe n, then corresponding adjustment occurs at the beginning of
`subframe n+x.
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2007 (3GPP TS 36.213 v8.1) – 007
`IPR2017-01508
`
`

`

`
`Release 8
`
`8
`
`3GPP TS 36.213 V8.1.0 (2007-11)
`
`Editor’s note: RAN1 needs to agree on 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
`DFT-SOFDM symbol in which the physical channel is transmitted.
`
`Uplink power control
`5.1
`Uplink power control controls the transmit power of the different uplink physical channels.
`
`A cell wide overload indicator (OI) is exchanged over X2 for inter-cell power control. An indication X also exchanged
`over X2 indicates PRBs that an eNodeB scheduler allocates to cell edge UEs and that will be most sensitive to inter-cell
`interference.
`
`[Note: Above lines regarding OI, X and X2 to be moved to an appropriate RAN3 spec when it becomes available]
`
`5.1.1
`
`Physical uplink shared channel
`
`UE behaviour
`5.1.1.1
`The setting of the UE Transmit power PUSCH
`P
`subframe i is defined by
`
` for the physical uplink shared channel (PUSCH) transmission in
`
`P
`PUSCH
`
`
`
`)(i
`
`
`
`
`
`min{P
`MAX
`
`10,
`
`log
`
`10
`
`(
`
`M
`
`PUSCH
`
`(
`
`i
`
`))
`
`
`
`P
`O_PUSCH
`
`
`
`)( j
`
`
`
`
`
`PL
`
`
`
`MCS
`
`(
`
`
`
`(iMCS
`
`))
`
`
`
`f
`
`
`
`)}(i
`
` [dBm]
`
`where,
`
`
`
`
`
`
`
`
`
`
`
`MAXP
`is the bandwidth of the PUSCH transmission expressed in number of resource blocks taken from
`)(
`M
`PUSCH i
`the resource allocation valid for uplink subframe i from scheduling grant received on subframe
`.
`Ki 
`PUSCH
`oP is a parameter with 1 dB resolution composed of the sum of a 8-bit cell specific nominal
`)(
`O_PUSCH jP
`
` signaled from higher layers for j=0 and 1 in the range of [-126,24] dBm
`component
`
`)( j
`P
` PUSCHO_NOMINAL_
`
` configured by RRC for j=0 and 1 in the range of [-8, 7]
`and a 4-bit UE specific component
`)(
`O_UE_PUSCH jP
`
`dB. For PUSCH (re)transmissions corresponding to a configured scheduling grant then j=0 and for PUSCH
`(re)transmissions corresponding to a received PDCCH with scheduling grant format associated with a new
`packet transmission then j=1.
`  1,9.0,8.0,7.0,6.0,5.0,4.0,0
`
` PL is the downlink pathloss estimate calculated in the UE
`
`table entries can be set to zero)
`table values are cell specific and given by RRC (
`(MCS MCS
`)
`(
`))
`(MCS
`iMCS
`
`
`and MCS(i) is the PUSCH MCS valid for subframe i taken from a PDCCH with scheduling grant format
`received on subframe
`.
`Ki 
`PUSCH
`is a UE specific correction value, also referred to as a TPC command and is included in PDCCH with
`
`PUSCH
`scheduling grant format or jointly coded with other TPC commands in PDCCH with TPC-PUSCH format. The
`current PUSCH power control adjustment state is given by
` which is defined by:
`)(i
`f
`o
`
`is the maximum allowed power that depends on the UE power class
`
` is a 3-bit cell specific parameter signaled from higher layers
`
`f
`
`)(
`i
`
`
`
`f
`
`(
`
`i
`
`)1
`
`
`PUSCH
`
`(
`
`Ki
`
`
`PUSCH
`
`)
`
` if
`
`)(f
`
` represents accumulation
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2007 (3GPP TS 36.213 v8.1) – 008
`IPR2017-01508
`
`

`

`
`Release 8
`
`9
`
`3GPP TS 36.213 V8.1.0 (2007-11)
`
`
`
` where
`=[4]
` and
`)0(
`0
`K
`f
`
`PUSCH
` The UE attempts to decode a PDCCH of scheduling grant format and a PDCCH of TPC-
`PUSCH format in every subframe except when in DRX
` dB for a subframe where no TPC command is decoded or where DRX occurs.
`0
`
`PUSCH 
` The
` dB accumulated values signaled on PDCCH with scheduling grant format are
`
`PUSCH
`either [-1,0,1,3] or [-3,-1,1,3] as semi-statically configured by higher layers.
` The
` dB accumulated values signaled on PDCCH with TPC-PUSCH format are one
`
`PUSCH
`of [-1,1], [-1,0,1,3] or [-3,-1,1,3] as semi-statically configured by higher layers.
`(
`)
`if
` represents current absolute value
`)(f
`Ki
`
`
`
`o
`
`f
`
`
`
`)(i
`
`PUSCH
`PUSCH
` where
`(
`Ki 
`
`PUSCH
`subframe
`Ki 
`
`)
`
` was signaled on PDCCH with scheduling grant format on
`
`PUSCH
`
`
`PUSCH
`]4[
`
` where
`
`K
`
`
`
`PUSCH
` dB absolute values signaled on PDCCH with scheduling grant format are [-4,-
`
`PUSCH
`
` The
`
`1,1,4].
` type (accumulation or current absolute) is a UE specific parameter that is given by RRC.
`
`o
`
`
`
`)(f
`
`5.1.1.2
`
`eNodeB behaviour
`
`5.1.2
`
`Physical uplink control channel
`
`UE behaviour
`5.1.2.1
`The setting of the UE Transmit power PUCCH
`P
`subframe i is defined by
`
`for the physical uplink control channel (PUCCH) transmission in
`
`P
`PUCCH
`
`
`
`)(i
`
`
`
`
`
`min{P
`MAX
`
`,
`
`P
`O_PUCCH
`
`
`
`PL
`
`
`
`MCS_PUCCH
`
`(
`
`MCS
`
`)
`
`
`
`
`
` )}(ig
`
`[dBm]
`
`
`
`where
`
`
`
`
`
`
`
`table is signaled by RRC (table entries can be set to zero).
`(
`)
`MCS_PUCCH MCS
`o MCS is the PUCCH format defined in Table 5.4-1 in [3]
` is a 5-bit cell specific parameter signaled via BCCH on the PDSCH with 1 dB resolution in the
`P
`O_PUCCH
`range of [-127, -96] dBm
` is a UE specific correction value, also referred to as a TPC command, included in a PDCCH with a
`
`PUCCH
`scheduling assignment format or sent jointly coded with other UE specific PUCCH correction values on a
`PDCCH with a TPC- PUDCCH format.
`o The UE attempts to decode a PDCCH with a TPC- PUCCH format and a PDCCH with a scheduling
`assignment format on every subframe except when in DRX.
` from a PDCCH with a scheduling assignment format overrides that from a PDCCH with a
`
`PUCCH
`TPC-PUCCH format when both are decoded in a given subframe.
`=0 dB for a subframe where neither a PDCCH with scheduling assignment format or PDCCH
`
`PUCCH
`with TPC-PUCCH format is decoded or where DRX occurs.
` )(ig
`
`(ig
`
`)1
`(
`)
`)(ig
` where
` is the current PUCCH power control adjustment
`Ki
`
`
`
`PUCCH
`PUCCH
`)0(
`0
`state with initial condition
`.
`g
`
`
`o
`
`o
`
`o
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2007 (3GPP TS 36.213 v8.1) – 009
`IPR2017-01508
`
`

`

`
`Release 8
`
`10
`
`3GPP TS 36.213 V8.1.0 (2007-11)
`
`o The
` dB values signaled on PDCCHs with scheduling assignment format are either [-1,0,1,3]
`
`PUCCH
`or [-3,-1,1,3] as semi-statically configured by higher layers.
`o The
` dB values signaled on PDCCHs with TPC-PUCCH format are [-1,1] or [-1,0,1,3] or [-
`
`PUCCH
`3,-1,1,3] as semi-statically configured by higher layers.
`
`
`
`5.1.2.2
`
`eNodeB behaviour
`
`5.1.3
`
`Sounding Reference Symbol
`
`UE behaviour
`5.1.3.1
`The setting of the UE Transmit power
`
`SRSP
`
`for the Sounding Reference Symbol transmitted on subframe i is defined by
`
`P
`SRS
`
`)(
`i
`
`
`
`min{
`P
`MAX
`
`,
`
`P
`SRS_OFFSET
`
`
`
`10
`
`log
`10
`
`(
`
`M
`
`SRS
`
`)
`
`
`
`P
`O_PUSCH
`
`
`
`
`
`PL
`
`
`
`(
`
`MCS
`
`)
`REF 
`
`MCS
`
`f
`
`)}(
`i
`
` [dBm]
`
`where
`
`
`
`
`
`
`
`
`
`P
`SRS_OFFSET
`
` is a parameter semi-statically configured by higher layers.
`
`SRSM is the bandwidth of the SRS transmission expressed in number of resource blocks and is semi-statically
`configured by higher layers.
` is a fixed reference MCS level semi-statically configured by higher layers
`MCS
`
`REF
`
`f
`
`)(i
`
` is the current power control adjustment state for the PUSCH
`
`
`
`5.1.3.2
`
`
`eNodeB behaviour
`
`Downlink power allocation
`5.2
`The eNodeB determines the downlink transmit energy per resource element.
`
`A UE shall assume downlink reference symbol EPRE is constant across the downlink system bandwidth and constant
`across all subframes until different RS boosting information is received.
`
`For each UE, the PDSCH-to-RS EPRE ratio among REs in all the OFDM symbols containing RS is equal and is
`denoted by P_A.
`
`For each UE, the PDSCH-to-RS EPRE ratio among REs in all the OFDM symbols not containing RS is equal and is
`denoted by P_B.
`
`The cell-specific ratio between P_A and P_B is determined by eNodeB based on the cell-specific RS boosting value.
`
`
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2007 (3GPP TS 36.213 v8.1) – 010
`IPR2017-01508
`
`

`

`
`Release 8
`
`11
`
`3GPP TS 36.213 V8.1.0 (2007-11)
`
`5.2.1
`
`UE behaviour
`
`5.2.2
`
`eNodeB behaviour
`
`Downlink channel subcarrier transmit power offset
`5.2.3
`[Definition of and restrictions on the subcarrier transmit power offset for each downlink channel type]
`
`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, frequency position and preamble format)
`2. Parameters for determining the root sequences and their cyclic shifts in the preamble sequence set for the cell
`(index to root sequence table, cyclic shift (Ncs), and set type (normal or high-speed set))
`
`Physical non-synchronized random access procedure
`6.1
`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, preamble transmission power (PREAMBLE_TRANSMISSION_POWER), associated RA-
`RNTI, and PRACH resource are indicated by higher layers as part of the request.
`3. A preamble sequence is then selected from the preamble sequence set using the preamble index.
`4. A single preamble transmission then occurs using the selected preamble sequence with transmission power
`PREAMBLE_TRANSMISSION_POWER on the indicated PRACH resource.
`
`5.
`6.
`
`If no associated PDCCH with RA-RNTI is detected then the physical random access procedure is exited.
`
`If an associated PDCCH with RA-RNTI is detected then the corresponding DL-SCH transport block is passed
`to the higher layers and the physical random access procedure is exited.
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2007 (3GPP TS 36.213 v8.1) – 011
`IPR2017-01508
`
`

`

`12
`
`3GPP TS 36.213 V8.1.0 (2007-11)
`
`
`Release 8
`
`6.1.1
`
`Timing
`
`6.1.1.1
`
`6.1.1.2
`
`Synchronized
`
`Unsynchronized
`
`6.1.2
`
`Preamble Sequence selection
`
`7
`
`Physical downlink shared channel related procedures
`
`7.1.
`
`UE procedure for receiving the physical downlink shared
`channel
`A resource allocation field in each PDCCH includes two parts, a type field and information consisting of the actual
`resource allocation. PDCCH with type 0 and type 1 resource allocation have the same format and are distinguished
`from each other via the type field. For system bandwidth less than or equal to 10 PRBs the resource allocation field in
`each PDCCH contains only information of the actual resource allocation. PDCCH with type 2 resource allocation have
`a different format from PDCCH with a type 0 or type 1 resource allocation. PDCCH with a type 2 resource allocation
`do not have a type field.
`
`Resource allocation type 0
`7.1.1
`In resource allocations of type 0, a bitmap indicates the resource block groups that are allocated to the scheduled UE.
`The size of the group is a function of the system bandwidth that is shown in Table 7.1.1-1.
`
`Table 7.1.1-1: Type 0 Resource Allocation RBG Size vs. DL System Bandwidth
`RBG Size System Bandwidth
`(P)
`DL
`RBN
`
`1
`≤10
`2
`11 - 26
`3
`27 - 64
`4
`64 - 110
`
`
`
`Resource allocation type 1
`7.1.2
`In resource allocations of type 1, a bitmap indicates to a scheduled UE the resource blocks from the set of resource
`blocks from one of the P resource block group subsets where P is the resource block group size associated with the
`system bandwidth that is shown in Table 7.1.1-1.
`
`Resource allocation type 2
`7.1.3
`In resource allocations of type 2, the resource allocation information indicates to a scheduled UE a set of contiguously
`allocated physical or virtual resource blocks depending on the setting of a 1-bit flag carried on the associated PDCCH.
`PRB allocations vary from a single PRB up to a maximum number of PRBs spanning the system bandwidth. For VRB
`allocations .the resource allocation information consists of a starting VRB number and a number of consecutive VRBs
`where each VRB is mapped to multiple non-consecutive PRBs.
`
`A type 2 resource allocation field consists of a resource indication value (RIV) corresponding to a starting resource
`). The resource indication value
`) and a length in terms of contiguously allocated resource blocks ( CRBs
`block (
`RB
`L
`start
`is defined by
`
`if
`
`(
`
`L
`CRBs
`
`
`
`)1
`
`
`
`
`N
`
`DL
`RB
`
`2/
`
` then
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2007 (3GPP TS 36.213 v8.1) – 012
`IPR2017-01508
`
`

`

`
`Release 8
`
`13
`
`3GPP TS 36.213 V8.1.0 (2007-11)
`
`RIV
`
`
`
`N
`
`DL
`RB
`
`(
`
`L
`CRBs
`
`)1
`
`
`RB
`
`
`
`start
`
`else
`
`RIV
`
`
`
`N
`
`DL
`RB
`
`(
`
`N
`
`DL
`RB
`
`
`
`L
`CRBs
`
`
`
`)1
`
`
`
`(
`
`N
`
`DL
`RB
`
`1
`
`
`RB
`
`)
`
`
`
`start
`
`
`
`7.2 UE procedure for reporting channel quality indication (CQI),
`precoding matrix indicator (PMI) and rank
`The time and frequency resources that can be used by the UE to report CQI, PMI, and rank are controlled by the eNB.
`CQI, PMI, and rank reporting is periodic or aperiodic. A UE transmits CQI, PMI, and rank reporting on a PUCCH for
`subframes with no PUSCH transmission and on a PUSCH for those subframes with scheduled PUSCH transmissions
`with or without an associated scheduling grant. 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
`
`Frequency non-selective
`
`Frequency selective
`
`
`
`Periodic CQI reporting channels
`
`Aperiodic CQI reporting channel
`
`PUCCH
`
`PUSCH
`
`PUCCH
`
`PUSCH
`
`PUSCH
`
`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
`
`When reporting rank the UE reports a single rank.
`
`When reporting PMI the UE reports either single or multiple PMI reports. The number of RBs represented by a single
`DL
`RBN or a smaller subset of RBs. A UE shall determine the codebook subset to report based on a
`UE PMI report can be
`bitmap given by RRC. The number of RBs represented by a single PMI report is configured by the network.
`
`The set of subbands (S) a UE shall evaluate for CQI reporting is semi-statically configured by higher layers. A
`subband is a set of k contiguous PRBs where k is also semi-statically configured by higher layers. The term
`“Wideband CQI” denotes the 5-bit CQI value obtained over the set S.
`
`Aperiodic/Periodic CQI Reporting using PUSCH
`7.2.1
`A UE shall perform aperiodic CQI reporting using the PUSCH upon receiving an indication sent in the scheduling
`grant.
`
`The aperiodic CQI report size and message format is given by RRC.
`
`
`
`The minimum reporting interval for aperiodic reporting of CQI and PMI is 1 subframe. In the case of frequency
`selective CQI and PMI reports the subband size for CQI and PMI shall be the same. The subband size for CQI and
`PMI shall be the same for transmitter-receiver configurations with and without precoding.
`
`A UE is semi-statically configured by higher layers to feed back CQI on the PUSCH using one of the following CQI
`reporting types:
` Wideband feedback
`o A UE shall report one wideband CQI value.
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2007 (3GPP TS 36.213 v8.1) – 013
`IPR2017-01508
`
`

`

`
`Release 8
`
`14
`
`3GPP TS 36.213 V8.1.0 (2007-11)
`
` Higher Layer-configured subband feedback
`o A UE shall report a wideband CQI and one CQI for each subband in the set of subbands (S) semi-
`statically configured by higher layers. Subband CQI are encoded differentially with respect to the
`wideband CQI using 3-bits.
`o Supported subband size (k) include those given in Table 7.2.1-1. In Table 7.2.1-1 the k values are
`semi-statically configured by higher layers as a function of system bandwidth..
`
`Table 7.2.1-1: Subband Size vs. DL System Bandwidth
`System Bandwidth
`Subband Size
`(k)
`DL
`RBN
`
`6 - 7
`(wideband CQI only)
`8 - 10
`4
`11 - 26
`4
`27 - 64
`6
`64 - 110
`4, 8
`
` UE-selected subband feedback
`o The UE shall select the M best subbands of size k (where k and M are given in Table 7.2.1-2 for each
`system bandwidth range) within the set of subbands S semi-statically configured by higher layers and
`
`
`DL
`/
`N
`k
`RB
`M
`
`bits...
`
` 
` 
`
`
`
` 
`
`log
`
`2
`
` 
`
`report the positions of these M subbands using
`
`
`
`
`
`o The UE shall also report one CQI value reflecting trans