`Jeju, Korea, November 5-9, 2007
`DRAFT CHANGE REQUEST
` rev 2 Current version: 8.0.0
`36.213 CR 1
`For HELP on using this form look at the pop-up text over the symbols. Comprehensive instructions on
`how to use this form can be found at http://www.3gpp.org/specs/CR.htm.
`
`R1-075116
`
`CR-Form-v9.3
`
`
`
`
`
`
`
`
`
`Proposed change affects: UICC apps
`
`
`
`ME X Radio Access Network X Core Network
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` Update of 36.213
`Title:
`Source to WG: Editor (Motorola)
`Source to TSG: R1
`Work item code: LTE-Phys
` F
`Category:
`
`
`Use one of the following categories:
`F (correction)
`A (corresponds to a correction in an earlier
`release)
`B (addition of feature),
`C (functional modification of feature)
`D (editorial modification)
`Detailed explanations of the above categories can
`be found in 3GPP TR 21.900.
`
`
`
`
`
`
`
`
`
`Date: 22/11/2007
`Release: Rel-8
`Use one of the following releases:
`R97
`(Release 1997)
`R98
`(Release 1998)
`R99
`(Release 1999)
`Rel-4
`(Release 4)
`Rel-5
`(Release 5)
`Rel-6
`(Release 6)
`Rel-7
`(Release 7)
`(Release 8)
`Rel-8
`
`
`
`
`
`
`
`
`
`Reason for change: Decisions taken at RAN1#50bis and RAN1#51 need to be reflected in 36.213
`Summary of change:
`Inclusion of decisions from RAN1#50bis and RAN1#51 which include uplink
`power control, control channel resource allocation, downlink power boosting, CQI
`reporting for single TX antenna and Tx Diversity as well as subband size details
`for frequency selective CQI and PMI reporting. Updates to PRACH to harmonize
`with RAN2 specification. PHICH duration agreements captured for unicast and
`MBSFN subframes. Refinement of text concerning timing adjustment (e.g.
`eliminating unnecessary text on eNodeB behavior). Text added reflecting
`RAN1#47bis working assumption regarding puncturing PUSCH allocated cell
`edge PRB by PUCCH resource slot when odd number of PRBs in system BW
`and only a single PUCCH resource is allocated.
`Incomplete LTE physical layer procedures specifications
`
`Consequences if
`not approved:
`Clauses affected: 2, 3.1, 3.2, 4.1, 4.2.4, 5, 5.1, 5.1.1.1, 5.1.2.1, 5.1.3.1, 5.2, 6, 6.1, 7.1, 7.1.1, 7.1.2,
`7.1.3, 7.2, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 8, 8.1, 8.2, 9.1, 10.1, 10.2
`Y N
`
`
`
` Other core specifications
`
`
`
` Test specifications
`
`
`
` O&M Specifications
`
`
`
`
`
`
`
`Other specs
`affected:
`
`
`Other comments:
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2006 (3GPP Change Request, R1-075116 ) – 001
`IPR2017-01508
`
`
`
`
`Error! No text of specified style in document.
`
`2
`
`Error! No text of specified style in document.
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2006 (3GPP Change Request, R1-075116 ) – 002
`IPR2017-01508
`
`
`
`
`Error! No text of specified style in document.
`
`3
`
`Error! No text of specified style in document.
`
`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.
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2006 (3GPP Change Request, R1-075116 ) – 003
`IPR2017-01508
`
`
`
`
`Error! No text of specified style in document.
`
`4
`
`Error! No text of specified style in document.
`
`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 Specifica”tions".
`
`3GPP TS 36.201: "LTE Physical LayerEvolved Universal Terrestrial Radio Access (E-UTRA);
`Long Term Evolution (LTE) physical layer – General Descrip“tion ".
`
`3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and
`modul”ation".
`
`3GPP TS 36.212: " Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and
`channel c”oding".
`
`3GPP TS 36.214: "“Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer –
`Measure”ments".
`
`3
`
`Definitions, symbols, and abbreviations
`
`Definitions
`3.1
`For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A
`term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
`
`Definition format
`
`<defined term>: <definition>.
`example: text used to clarify abstract rules by applying them liter.
`
`3.21 Symbols
`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]
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2006 (3GPP Change Request, R1-075116 ) – 004
`IPR2017-01508
`
`
`
`
`Error! No text of specified style in document.
`
`5
`
`Error! No text of specified style in document.
`
`
`
`
`
`3.32 Abbreviations
`For the purposes of the present document, the following abbreviations given in TR 21.905 [1] and the following apply.
`An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any,
`in TR 21.905 [1].
`
`ACK
`BCH
`CCE
`CCPCH
`CQI
`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
`
`Acknowledgement
`Broadcast Channel
`Control Channel Element
`Common Control Physical Channel
`Channel Quality Indicator
`Cyclic Redundancy Check
`Downlink
`Discontinuous Transmission
`Energy Per Resource Element
`Modulation and Coding Scheme
`Negative Acknowledgement
`Physical Ccontrol Fformat Iindicator Cchannel
`Physical Downlink Shared Channel
`Physical Hybrid ARQ Indicator Channel
`Physical Rrandom Aaccess Cchannel
`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 blocks72 sub-carriers and upwards.
`
`The following signals are transmitted in the downlink to facilitate cell search: the primary and secondary
`synchronization signals., and the downlink reference signals.
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2006 (3GPP Change Request, R1-075116 ) – 005
`IPR2017-01508
`
`
`
`
`Error! No text of specified style in document.
`
`6
`
`Error! No text of specified style in document.
`
`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
`...On receiving a random access burst from a UE the network determines if the UE needs a TA adjustment and if so
`signals to the UE a TA command which is a multiple of 0.52 s and is applied as a 1 step adjustment relative to the
`random access channel preamble transmit timing.
`
`
`
`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.A UE receives TA commands as determined by the network to maintain its time alignment. A TA
`command received by the UE will be a multiple of 0.52 s and is applied as a 1 step adjustment relative to current
`uplink timing.
`
`Power control
`5
`Downlink pPower 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 consists of open and closed loop components and controls energy per resource element applied
`for a UE transmission. For intra-cell uplink power control the closed loop component adjusts a set point determined by
`the open loop power control component.Uplink power control controls the transmit power of the different uplink
`physical channels
`
`
`
`Upon reception of an a-periodic transmit power command in an uplink scheduling grant the UE shall adjust its transmit
`EPRE accordingly.
`
`EPRE is set in the UE.
`
`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]
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2006 (3GPP Change Request, R1-075116 ) – 006
`IPR2017-01508
`
`
`
`
`Error! No text of specified style in document.
`
`7
`
`Error! No text of specified style in document.
`
`5.1.1
`
`Physical uplink shared channel
`
`UE behaviour
`5.1.1.1
`The setting of the UE Transmit power
`in subframe is is defined by
`
`P
`PUSCH
`
`P
`PUSCH
`
` for the physical uplink shared channel (PUSCH) transmission
`
`P
`PUSCH
`
`
`
`)(i
`
`
`
`
`min{P
`MAX
`
`10,
`
`log
`10
`
`(
`
`M
`
`PUSCH
`
`(
`
`i
`
`))
`
`
`
`P
`O_PUSCH
`
`
`
`)( j
`
`
`
`
`
`PL
`
`
`
`MCS
`
`(
`
`
`
`(iMCS
`
`))
`
`
`
`f
`
`
`
`)}(i
`
` [dBm]
`
`wWhere,
`
`
`
`MAXP
`
`maxP
`
` is the maximum allowed power that depends on the UE power class
`
` M
` is the bandwidth of the PUSCH transmission expressed in number of assigned resource blocks
`)(
`M
`PUSCH i
`taken from the resource allocation valid for uplink subframe i from scheduling grant received on subframe
`.as indicated in the UL scheduling grant
`Ki
`PUSCH
`
`
`
`
`
`
`
`
`
`oP is a UE specific parameter with 1 dB resolution composed of the sum of a 8-bit cell specific
`)(
`O_PUSCH jP
`
`
`)( j
` signaled from higher layers for j=0 and 1 in the range of [-126,24]
`nominal component
`P
`
` PUSCHO_NOMINAL_
`dBm and a 4-bit UE specific component
` configure by RRC for j=0 and 1 in the range of [-8,
`)(
`O_UE_PUSCH jP
`
`7] 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
`
` is a 3-bit cell specific path loss compensation factorparameter signaled
`from higher layers (can be set to one to allow full path loss compensation) that has 8 values from 0.4 to 1 in
`steps of 0.1 with one of the possible values being zero.
` PL is the downlink pathloss estimate calculated in the UE from a RSRP measurement and signalled RS
`transmit power
` table values areis cell specific and signaled given by RRC
`(MCS
`)
`))
`(
`(MCS
`iMCS
`mcs
`
` table entries can be set to zero) and MCS(i) is the PUSCH MCS valid for subframe
`(
`)
`(MCS
`)
`(MCS MCS
`mcs
`
`i taken from a PDCCH with scheduling grant format received on subframe
`.
`Ki
`oMCS signaled in each UL scheduling grant
`i is a a UE specific correction value, also referred to as a TPC command and is included in
`
`PUSCH
`PDCCH with scheduling grant format or jointly coded with other TPC commands in PDCCH with TPC-
`PUSCH formatand is defined differently dependent on scheduling . The current PUSCH power control
`adjustment state is given by
` as givenwhich is defined by:
`)(i
`f
`o
`
`PUSCH
`
`f
`
`)(
`i
`
`
`
`f
`
`(
`
`i
`
`)1
`
`
`PUSCH
`
`(
`
`Ki
`
`
`PUSCH
`
`)
`
` if
`
`)(f
`
` represents accumulation
`
` where
`
`f
`
`)0(
`
`
`
`0
`
` and
`
`K
`
`PUSCH
`
`=[4]
`
` 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.
`o Scheduled
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2006 (3GPP Change Request, R1-075116 ) – 007
`IPR2017-01508
`
`
`
`
`Error! No text of specified style in document.
`
`8
`
`Error! No text of specified style in document.
`
`(cid:0) i is included in each UL scheduling grant
`(cid:0)Function
` signaled via higher layers
`)(f
`(cid:31)o
`
`f
`
`
`
`)(i
`
`
`
`PUSCH
`
`(
`
`Ki
`
`
`PUSCH
`
`)
`
`if
`
`)(f
`
` represents current absolute value
`
` where
`(
`
`PUSCH
`subframe
`Ki
`
`Ki
`
`PUSCH
`
`PUSCH
`
`
` where
`
`K
`
`PUSCH
`
`]4[
`
`
`
`)
`
` was signaled on PDCCH with scheduling grant format on
`
`PUSCH
`
` dB absolute values signaled on PDCCH with scheduling grant format are [-4,-
`
` The
`
`1,1,4].
` type (accumulation or current absolute) is a UE specific parameter that is given by RRC.
`
`)(f
`
`o
` represents either accumulation or current absolute value
`)(f
`oNot scheduled
`(cid:0) i is included in each DL scheduling assignment or jointly coded with other UE specific correction values on a TPC
`PDCCH
`(cid:0)The UE attempts to detect a TPC PDCCH and a DL scheduling frame on every subframe except when in DRX.
`o The
`i from a DL scheduling assignment overrides any command from a TPC PDCCH when both
`are received in a given subframe.
` Function
` represents accumulation only
`)(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
`subframe is is defined by
`
`P
`PUCCH
`
`P
`pucch
`
` 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
`
`
`
` is the number of assigned resource blocks for the PUCCH
`
`pucchM
`
`(
`)
` table
` is signaled by RRC (
` table entries can be set to zero).
`MCS_PUCCH MCS
`
`
`mcs _
`mcs _
`pucch
`pucch
`o MCS MCS is the PUCCH format defined in Table 5.4-1 in [3]signaled using higher layer signaling
`
`
`
`
`
`
`
` is a 5-bit cell specific parameter signaled via BCCH on the PDSCH with 1 dB resolution
`oP _
`P
`O_PUCCH
`pucch
`in the range of [-127, -96] dBm
`j is a UE specific correction value, also referred to as a TPC command, included in a PDCCH with
`
`PUCCH
`a DL 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 decodetect a PDCCH with a TPC- PDUCCH format and a PDCCH with a DL
`scheduling assignment formatrame on every subframe except when in DRX.
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2006 (3GPP Change Request, R1-075116 ) – 008
`IPR2017-01508
`
`
`
`
`Error! No text of specified style in document.
`
`9
`
`Error! No text of specified style in document.
`
`o
`
`o
`
`o
`
`The TPC command from a PDCCH with a DL scheduling assignment format overrides any
`
`PUCCH
`commandthat from a PDCCH with a TPC-PUDCCH format when both are decodedreceived 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.
` where
` is the current PUCCH power control adjustment
`
` )(ig
`)1
`
`(ig
`(
`)
`)(ig
`Ki
`
`
`
`PUCCH
`PUCCH
`.
`state with initial condition
`)0(
`0
`g
`
`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-staticallyconfigured 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.
`
`
`oFunction
`
`)(g
`
` represents accumulation
`
`5.1.2.2
`
`eNodeB behaviour
`
`5.1.3
`
`Sounding Reference Symbol
`
`UE behaviour
`5.1.23.1
`srsP for the Sounding Reference Symbol transmitted on subframe i is
`The setting of the UE Transmit power
`SRSP
`defined byis set equal to the PUSCH power level
` plus an offset
`.
`P
`P
`pusch
`offset
`
`srs
`
`_
`
`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.32.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.
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2006 (3GPP Change Request, R1-075116 ) – 009
`IPR2017-01508
`
`
`
`
`Error! No text of specified style in document.
`
`10
`
`Error! No text of specified style in document.
`
`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.
`
`
`
`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 (numberPRACH configuration, frequency position, time period, and
`timing offsetpreamble format)
`
`2.Available preamble formats and preamble sequence set. Available root Zadoff-Chu (ZC) sequence
`indicesParameters 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))
`3.2. Preamble transmission r
`
`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.
`2.3. A preamble sequence is then determined selected from the preamble sequence set using the preamble index. set
`as indicated by higher layers.
`3.4. A single preamble transmission then occurs using the selected preamble sequence with transmission power
`PREAMBLE_TRANSMISSION_POWER on the indicated PRACH resource., and the parameters indicated by
`higher layers.
`4.5. If no associated PDCCH with RA-RNTI is detected then response corresponding to the transmitted preamble
`sequence is detected then the L1 status (“No acknowledgment on non-synchronized random access”) is passed
`to the higher layers and the physical random access procedure is exited.
`5.6. If an associated PDCCH with RA-RNTI is detected then the corresponding DL-SCH transport block a
`response corresponding to the transmitted preamble sequence is detected, then the L1 status (“ACK on non-
`synchronized random access received”) is passed to the higher layers and the physical random access
`procedure is exited.
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2006 (3GPP Change Request, R1-075116 ) – 010
`IPR2017-01508
`
`
`
`
`Error! No text of specified style in document.
`
`11
`
`Error! No text of specified style in document.
`
`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
`[For persistent and non-persistent scheduling, Includes pertinent aspects of downlink HARQ procedure and link
`adaptation procedure including any related signalled parameters to eNodeB and UE, ACK/NACK or CQI repetition
`procedure, eNodeB ACK/NACK detection procedure, handling of multiple HARQ processes for MIMO, etc]
`
`A resource allocation field in each scheduling assignment 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
`Part 1 indicates how to interpret Part 2 of theIn resource allocations. In a first resource allocation approach, 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
`
`≤10
`11 - 26
`27 - 64
`64 - 110
`
`1
`2
`3
`4
`
`
`
`
`
` .
`
`Resource allocation type 1
`7.1.2
`In a second resource allocations of approachtype 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. the system bandwidth is divided in subsets of
`resource blocks, and the resource allocation has the capability to indicate one or multiple individual resource blocks to
`the scheduled UE.
`
`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
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2006 (3GPP Change Request, R1-075116 ) – 011
`IPR2017-01508
`
`
`
`
`Error! No text of specified style in document.
`
`12
`
`Error! No text of specified style in document.
`
`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
`block (
`). The resource indication value
`) and a length in terms of contiguously allocated resource blocks ( CRBs
`RB
`L
`start
`is defined by
`
`if
`
`(
`
`L
`CRBs
`
`
`
`)1
`
`
`
`
`N
`
`DL
`RB
`
`2/
`
` then
`
`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
`[Includes CQI reporting needed to support frequency domain scheduling at eNodeB, CQI bin bandwidth, selection of
`CQI MCS, repetition, etc]
`
`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 a 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
`UE PMI report can be
`a 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 .
`
`
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2006 (3GPP Change Request, R1-075116 ) – 012
`IPR2017-01508
`
`
`
`
`Error! No text of specified style in document.
`
`13
`
`Error! No text of specified style in document.
`
`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.
` 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
`8 - 10
`11 - 26
`27 - 64
`64 - 110
`
`(wideband CQI only)
`4
`4
`6
`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
`/
`k
`N
`RB
`M
`
`bits...
`
`
`
`
`
`
`
`
`log
`
`2
`
`
`
`report the positions of these M subbands using
`
`o The UE shall also report one CQI value reflecting transmission only over the selected M best
`subbands determined in the previous step.
`o Additionally, the UE shall also report one wideband CQI value.
`o The best-M CQI value is encoded differentially using 3-bits relative to the wideband CQI.
`o Supported subband size k and M values include those shown in Table 7.2.1-2. In Table 7.2.1-2 the k
`and M values are a function of system bandwidth.
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2006 (3GPP Change Request, R1-075116 ) – 013
`IPR2017-01508
`
`
`
`
`Error! No text of specified style in document.
`
`14
`
`Error! No text of specified style in document.
`
`Table 7.2.1-2: Subband Size (k) and M values vs. DL System Bandwidth
`System Bandwidth Subband Size k [RBs]
`
`DL
`RBN
`
`6 – 7
`8 – 10
`11 - 26
`27 - 64
`64 - 110
`
`(wideband CQI only)
`2
`2
`3
`4
`
`(wideband CQI only)
`1
`3
`5
`6
`
`M
`
`
`.
`
`
`
`Periodic CQI Reporting using PUCCH
`7.2.2
`A UE is semi-statically configured by higher layers to periodically feed back different CQI types on the PUCCH using
`the following periodicity parameters:
`
`
`
`
`
`
`PN is the periodicity of the sub-frame pattern allocated for the CQI reports in terms of subframes were the
`minimum reporting interval is
`.
`N
`is the subframe offset
`
`N
`
`OFFSET
`
`PMIN
`
`
`Support for different CQI report types include
`
` Wideband CQI on set S
` Frequency-selective CQI type
`
`
`The supported subband size (k) values include those given in Table 7.2.1-1 which are a function of system bandwidth.
`
`For the frequency-selective CQI, a CQI report in a certain subframe describes the channel quality in a particular part or
`in particular parts of the bandwidth (a part is frequency-consecutive and an integer multiple of the subband size)
` Which bandwidth part(s) to use varies deterministically from one CQI report subframe to another covering the
`entire set of subbands (S) after a finite period.
`
` A
`
` UE with a scheduled PUSCH transmission in the same subframe as its CQI report shall use the same PUCCH-based
`reporting format when reporting CQI on the PUSCH unless an associated PDCCH with scheduling grant format
`indicates an aperiodic report is required..
`7.2.13 Channel quality indicator (CQI) definition
`[Includes definition of CQI information needed for frequency domain scheduling, may define different CQI MCS]
`
`The number of entries in the CQI table for a single TX antenna = 32.
`
` A
`
` single CQI index corresponds to an index pointing to a value in the CQI table. The CQI index is defined in terms of
`a channel coding rate and modulation scheme (QPSK, 16QAM, 64QAM),
`
` A
`
` UE shall report a CQI