Release 12
`
`126
`
`3GPP TS 36.213 V12.3.0 (2014-09)
`
`Table 8.2-2: UE Specific SRS Periodicity ½Rs and Subframe Offset Configuration ½ffset
`for trigger type 0, TDD
`
`SRS Configuration Index SRS Periodicity SRS Subframe Offset
`TsRs (ms)
`lsRs
`Toffset
`0, 1
`0
`2
`1
`2
`0 2
`1, 2
`2
`2
`0, 3
`3
`2
`4
`2
`1 3
`0, 4
`5
`2
`6
`2
`1 4
`2, 3
`7
`2
`2, 4
`8
`2
`2
`3 4
`9
`10 - 14
`lsRs- 10
`5
`15 - 24
`10
`lsRs - 15
`25 - 44
`lsRs- 25
`20
`45 - 84
`40
`lsRs- 45
`85 - 164
`lsRs- 85
`80
`165 - 324
`ISRs - 165
`160
`325 - 644
`320
`ISRs- 325
`645 - 1023
`reserved
`reserved
`
`Table 8.2-3: ksRS for TDD
`
`0
`
`1
`
`1st symbol
`of UoPTS
`
`2nd symbol
`ofUoPTS
`
`subframe index n
`2 3 4 5
`
`6
`
`7
`
`8 9
`
`1st symbol
`ofUoPTS
`
`2nd symbol
`of UoPTS
`
`0
`
`1
`
`1
`
`2 3 4
`
`2 3 4
`
`5
`
`6
`
`6
`
`7
`
`8 9
`
`7
`
`8 9
`
`ksRS in case UpPTS
`length of 2 symbols
`ksRS
`in case UpPTS
`length of 1 symbol
`
`Table 8.2-4: UE Specific SRS Periodicity TsRs,i and Subframe Offset Configuration T,,ffset,I
`for trigger type 1, FDD
`
`SRS Configuration Index SRS Periodicity SRS Subframe Offset
`TsRS,1 (ms)
`lsRs
`T,,ffset ,I
`0 - 1
`lsRs
`2
`2 - 6
`lsRs- 2
`5
`7 - 16
`10
`lsRs- 7
`17 - 31
`reserved
`reserved
`
`3GPP
`
`Samsung Ex. 1006
`
`IPR2022-00464
`Apple EX1006 Page 126
`
`

`

`Release 12
`
`127
`
`3GPP TS 36.213 V12.3.0 (2014-09)
`
`Table 8.2-5: UE Specific SRS Periodicity TsRs,i and Subframe Offset Configuration I;,ffiet, i
`for trigger type 1, TDD
`
`SRS Configuration Index SRS Periodicity SRS Subframe Offset
`TSRS,1 (ms)
`lsRs
`T;,ffiet, l
`0
`reserved
`1
`0 2
`1, 2
`2
`0, 3
`3
`1, 3
`4
`5
`0 4
`6
`1 4
`7
`2 3
`8
`2 4
`3, 4
`9
`10 - 14
`ISRs- 10
`15 - 24
`"'""- 15
`25 - 31
`reserved
`
`reserved
`2
`2
`2
`2
`2
`2
`2
`2
`2
`5
`10
`reserved
`
`3GPP
`
`Samsung Ex. 1006
`
`IPR2022-00464
`Apple EX1006 Page 127
`
`

`

`Release 12
`
`
`128
`
`3GPP TS 36.213 V12.3.0 (2014-09)
`
`UE HARQ-ACK procedure
`8.3
`For FDD, and serving cell with frame structure type 1, an HARQ-ACK received on the PHICH assigned to a UE in
`subframe i is associated with the PUSCH transmission in subframe i-4.
`
`For FDD-TDD, and serving cell with frame structure type 1, and UE not configured to monitor PDCCH/EPDCCH in
`another serving cell with frame structure type 2 for scheduling the serving cell, an HARQ-ACK received on the PHICH
`assigned to a UE in subframe i is associated with the PUSCH transmission in subframe i-4.
`
`For FDD-TDD, if a serving cell is a secondary cell with frame structure type 1 and if the UE is configured to monitor
`PDCCH/EPDCCH in another serving cell with frame structure type 2 for scheduling the serving cell, then an HARQ-
`ACK received on the PHICH assigned to a UE in subframe i is associated with PUSCH transmission on the serving cell
`in subframe i-6.
`
`For TDD, if the UE is not configured with EIMTA-MainConfigServCell-r12 for any serving cell and, if a UE is
`configured with one serving cell, or if the UE is configured with more than one serving cell and the TDD UL/DL
`configuration of all the configured serving cells is the same,
`
`- For frame structure type 2 UL/DL configuration 1-6, an HARQ-ACK 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 HARQ-ACK received on the PHICH in the resource
`0
`corresponding to
`, as defined in subclause 9.1.2, assigned to a UE in subframe i is associated with
`I
`=
`PHICH
`the PUSCH transmission in the subframe i-k as indicated by the following Table 8.3-1. For frame structure type
`1
`2 UL/DL configuration 0, an HARQ-ACK received on the PHICH in the resource corresponding to
`,
`I
`=
`PHICH
`as defined in subclause 9.1.2, assigned to a UE in subframe i is associated with the PUSCH transmission in the
`subframe i-6.
`
`For TDD, if a UE is configured with more than one serving cell and the TDD UL/DL configuration of at least two
`configured serving cells is not the same, or if the UE is configured with EIMTA-MainConfigServCell-r12 for at least
`one serving cell, or FDD-TDD and serving cell is frame structure type 2,
`
`- For serving cell with an UL-reference UL/DL configuration (defined in subclause 8.0) belonging to
`{1,2,3,4,5,6}, an HARQ-ACK received on the PHICH assigned to a UE in subframe i is associated with the
`PUSCH transmission in the subframe i-k for the serving cell as indicated by the following Table 8.3-1, where
`"TDD UL/DL Configuration" in Table 8.3-1 refers to the UL-reference UL/DL Configuration.
`
`- For a serving cell with UL-reference UL/DL configuration 0 (defined in subclause 8.0), an HARQ-ACK
`received on the PHICH in the resource corresponding to
`, as defined in subclause 9.1.2, assigned to a
`0
`I
`=
`PHICH
`UE in subframe i is associated with the PUSCH transmission in the subframe i-k for the serving cell as indicated
`by the following Table 8.3-1, where "TDD UL/DL Configuration" in Table 8.3-1 refers to the UL-reference
`UL/DL configuration. For a serving cell with UL-reference UL/DL configuration 0, an HARQ-ACK received on
`1
`the PHICH in the resource corresponding to
`, as defined in subclause 9.1.2, assigned to a UE in
`I
`=
`PHICH
`subframe i is associated with the PUSCH transmission in the subframe i-6 for the serving cell.
`
`- For FDD-TDD, if a serving cell is a secondary cell with UL-reference UL/DL configuration 0 and if the UE is
`configured to monitor PDCCH/EPDCCH in another serving cell with frame structure type 1 for scheduling the
`serving cell, for downlink subframe i, if a transport block was transmitted in the associated PUSCH subframe i-6
`for the serving cell then PHICH resource corresponding to that transport block is not present in subframe i.
`
`3GPP
`
`IPR2022-00464
`Apple EX1006 Page 128
`
`

`

`Release 12
`
`129
`
`3GPP TS 36.213 V12.3.0 (2014-09)
`
`Table 8.3-1 k for TDD configurations 0-6
`
`subframe number i
`TDD UU DL
`Confiauration 0 1 2 3 4 5 6 7 8 9
`7 4
`7 4
`0
`1
`4
`4
`2
`3
`4
`5
`6
`
`6
`
`6
`
`6
`
`6 4
`
`7 4
`
`6
`
`6
`6 6
`6 6
`6
`
`6
`
`The physical layer in the UE shall deliver indications to the higher layers as follows:
`
`For FDD, and for IDD with a UE configured with one serving cell, and for IDD with a UE configured with more than
`one serving cell and with IDD UVDL configuration of all configured serving cells the same, and UE is not configured
`with EIMT A -MainConfigServCell-r 12 for any serving cell, for downlink or special subframe i, if a transport block was
`transmitted in the associated PUSCH subframe then:
`
`if ACK is decoded on the PHI CH corresponding to that transport block in subframe i, or if that transport block is
`disabled by PDCCH/EPDCCH received in downlink or special 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 IDD, if the UE is configured with more than one serving cell, and if at least two serving cells have different UIJDL
`configurations, or the UE is configured with EIMTA-MainConfigSe/'vCell-rl 2 for at least one serving cell, or for FDD(cid:173)
`IDD, for downlink or special subframe i, if a transport block was transmitted in the associated PUSCH subframe then:
`
`if ACK is decoded on the PHI CH corresponding to that transport block in subframe i, or if that transport block is
`disabled by PDCCH/EPDCCH received in downlink or special subframe i, ACK for that transport block shall be
`delivered to the higher layers; or
`
`if a PHICH resource corresponding to that transport block is not present in subframe i or ifUE is not expected to
`receive PHICH corresponding to that 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.
`
`3GPP
`
`Samsung Ex. 1006
`
`IPR2022-00464
`Apple EX1006 Page 129
`
`

`

`Release 12
`
`130
`
`3GPP TS 36.213 V12.3.0 (2014-09)
`
`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/EPDCCH with DCI format 0 is set to 1 and the uplink resource block assignment is type 0 otherwise no
`PUSCH frequency hopping is performed.
`
`AUE performing PUSCH frequency hopping shall determine its PUSCH Resource Allocation (RA) for the first slot of
`a subframe (SJ) including the lowest index PRB ( nik (n)) in subframe n from the resource allocation field in the latest
`PDCCH/EPDCCH with DCI format 0 for the same transport block. If there is no PDCCH/EPDCCH 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/EPDCCH, 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
`
`Ne:; - if ff% - (Ne:; mod 2) Type 1 PUSCH hopping
`N:ffscH = Ne:;
`Type 2 N sb = 1 PUSCH hopping
`{
`Ne:; - if ff%
`
`Type 2 N sb > 1 PUSCH hopping
`
`For type 1 and type 2 PUSCH hopping, N~ = N ~ + 1 if N ~
`N~ = N ~
`in other cases. The size of the resource allocation field in DCI format 0 after excluding either 1 or 2 bits
`shall be y = ilog 2(N:(N: + 1) / 2) l - NUL _ hop, whereNuz._hop = 1 or 2 bits. The number of contiguous RBs
`that can be assigned to a type- 1 hopping user is limited to l2Y / N: J. The number of contiguous RBs that can be
`assigned to a type-2 hopping user is limited to min ( l 2 Y I N: J, lN JiBusCH / N sb J ), where the number of sub-bands
`
`is an odd number where N~ defined in [3].
`
`Nsb is given by higher layers.
`
`AUE 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 subclause 8.4.1 and type 2 is described in subclause
`8.4.2.
`
`Table 8.4-1 : Number of Hopping Bits NuL hop vs. System Bandwidth
`
`System BW #Hopping bits for 2nd slot RA
`(NuL hop)
`NJ{;
`6-49
`50-110
`
`1
`2
`
`The parameter Hopping-mode provided by higher layers determines if PUSCH frequency hopping is "inter-subframe"
`or "intra and inter-subframe".
`
`3GPP
`
`Samsung Ex. 1006
`
`IPR2022-00464
`Apple EX1006 Page 130
`
`

`

`Release 12
`
`131
`
`3GPP TS 36.213 V12.3.0 (2014-09)
`
`8.4.1
`
`Type 1 PUSCH hopping
`
`For PUSCH hopping type 1 the hopping bit or bits indicated in Table 8.4-1 detennine npRB (i) as defined in Table 8.4-2.
`The lowest index PRB ( ntk (i)) of the 1st slot RA in subframe i is defined as nik (i) = nik (i) + JV~ I 2 , where
`nik (i) = RBsrART , and RBsTART is obtained from the uplink scheduling grant as in subclause 8.4 and subclause 8.1.
`
`The lowest index PRB ( n PRB (i) ) of the 2nd slot RA in subframe i is defined as n PRB (i) = ii PRB (i) + JV~ I 2 .
`
`The set of physical resource blocks to be used for PUSCH transmission are LCRBs contiguously allocated resource
`blocks from PRB index ntk o) for the 1st slot, and from PRB index npRB(i) for the 2nd slot, respectively, where
`LcRBs is obtained from the uplink scheduling grant as in subclause 8.4 and subclause 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] subclause 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
`Nsb > 1 for IDD, where N sb is defined in [3].
`
`Table 8.4-2: PDCCH/EPDCCH DCI format O hopping bit definition
`
`System BW
`NJ{;
`
`Number of
`Hopping bits
`
`Information in
`hopping bits
`
`6 - 49
`
`50 - 110
`
`1
`
`2
`
`0
`
`1
`
`00
`
`01
`
`10
`
`11
`
`npRB(i)
`(lNifSCH 12J +ntk ci))modNkBUSCH,
`
`Tvoe 2 PUSCH HoDD na
`(lN~SCH /4j +nftk o))modN~ SCH
`(- lN:suscH I 4j +nftk co)mod NkBUSCH
`(lN~SCH 12J +nftk o))modN~ SCH
`
`Tvoe 2 PUSCH HoDD na
`
`8.5
`
`UE Reference Symbol (RS) procedure
`
`IfUL sequence-group hopping or sequence hopping is configured in a serving cell, it applies to all Reference Symbols
`(SRS, PUSCH and PUCCH RS) . If disabling of the sequence-group hopping and sequence hopping is configured for the
`UE in the serving cell through the higher-layer parameter Disable-sequence-group-hopping, the sequence-group
`hopping and sequence hopping for PUSCH RS are disabled.
`
`3GPP
`
`Samsung Ex. 1006
`
`IPR2022-00464
`Apple EX1006 Page 131
`
`

`

`Release 12
`
`
`132
`
`3GPP TS 36.213 V12.3.0 (2014-09)
`
`8.6
`
`I
`
`MCS
`
`), and
`
`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 (
`− check the "CSI request" bit field, and
`− compute the total number of allocated PRBs (
`
`PRBN
`
`) based on the procedure defined in subclause 8.1, and
`
`− compute the number of coded symbols for control information.
`
`8.6.1 Modulation order and redundancy version determination
`For
`, the modulation order (
`) is determined as follows:
`
`0
`
`£ I
`
`MCS £
`
`28
`
`mQ
`
`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
`in Table 8.6.1-1.
`Q
`
`'m
`
`.
`
`If the UE is not capable of supporting 64QAM in PUSCH or has been configured by higher layers to transmit
`only QPSK and 16QAM,
`is first read from Table 8.6.1-1. The modulation order is set to
`,4min(
`)
`Q
`Q
`Q =
`m
`
`'m
`
`'m
`
`If the parameter ttiBundling provided by higher layers is set to TRUE, then the modulation order is set to
`. Resource allocation size is restricted to
` applies in this case if the UE does not indicate
`3
`2=mQ
`N
`PRB £
`support by higher layers to operate without it.
`
`-
`
`-
`
`-
`
`For
`
`29
`
`£ I
`
`MCS £
`
`31
`
` the modulation order (
`
`mQ
`
`) is determined as follows:
`
`-
`
` or, if DCI format 4 is used and only 1 TB is enabled and
`if DCI format 0 is used and
`29
`I
`MCS =
`the enabled TB and the signalled number of transmission layers is 1, and if
`
`I
`
`MCS =
`
`for
`
`29
`
`-
`
`-
`
`-
`
`-
`
`-
`
`the "CSI request" bit field is 1 bit and the bit is set to trigger an aperiodic report and,
`
`N
`
`PRB £
`
`4
`
` or,
`
`the "CSI request" bit field is 2 bits and is triggering an aperiodic CSI report for one serving cell according to
`4
`Table 7.2.1-1A, and,
` or,
`N
`PRB £
`the "CSI request" bit field is 2 bits and is triggering an aperiodic CSI report for more than one serving cell
`according to Table 7.2.1-1A and,
`, or,
`20
`N
`PRB £
`
`the "CSI request" bit field is 2 bits and is triggering an aperiodic CSI report for one CSI process according to
`4
`Table 7.2.1-1B and
`, or,
`N
`PRB £
`
`the "CSI request" bit field is 2 bits and is triggering an aperiodic CSI report for more than one CSI process
`20
`according to Table 7.2.1-1B and
`,
`N
`PRB £
`
`then the modulation order is set to
`
`2=mQ
`
`.
`
`- Otherwise, the modulation order shall be determined from the DCI transported in the latest PDCCH/EPDCCH
`with DCI format 0/4 for the same transport block using
`. If there is no PDCCH/EPDCCH with
`0
`28
`£ I
`MCS £
`DCI format 0/4 for the same transport block using
`, the modulation order shall be determined from
`0
`28
`£ I
`MCS £
`
`-
`
`the most recent semi-persistent scheduling assignment PDCCH/EPDCCH, when the initial PUSCH for the
`same transport block is semi-persistently scheduled, or,
`
`3GPP
`
`IPR2022-00464
`Apple EX1006 Page 132
`
`

`

`Release 12
`
`133
`
`3GPP TS 36.213 V12.3.0 (2014-09)
`
`-
`
`the random access response grant for the same transport block, when the PUSCH is initiated by the random
`access response grant.
`
`The UE shall use/ Mes and Table 8.6.1-1 to determine the redundancy version (l'V;,n) to use in the physical uplink shared
`channel.
`
`Table 8.6.1-1 : Modulation, TBS index and redundancy version table for PUSCH
`
`MCSlndex Modulation Order TBS Index Redundancy Version
`Q~
`/ Mes
`/TBS
`fVldx
`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
`2
`10
`11
`4
`10
`12
`4
`11
`13
`4
`12
`14
`4
`13
`15
`4
`14
`16
`4
`15
`17
`4
`16
`18
`4
`17
`19
`4
`18
`20
`4
`19
`21
`6
`19
`22
`6
`20
`23
`6
`21
`22
`24
`6
`25
`6
`23
`26
`6
`24
`27
`6
`25
`28
`6
`26
`29
`30
`31
`
`0
`0
`0
`0
`0
`0
`0
`0
`0
`0
`0
`0
`0
`0
`0
`0
`0
`0
`0
`0
`0
`0
`0
`0
`0
`0
`0
`0
`0
`1
`2
`3
`
`reserved
`
`8.6.2
`
`Transport block size determination
`
`For 0 s /Mes s 28 , the UE shall first determine the IBS index ( /TBs ) using / Mes 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 IBS is determined by the procedure in subclause 7.1.7.2.1. For a transport block that is
`mapped to two-layer spatial multiplexing, the IBS is determined by the procedure in subclause 7 .17.2.2.
`
`For29 s / Mes s 31,
`
`-
`
`ifDCI format 0 is used and / MCS = 29 or, ifDCI format 4 is used and only 11B is enabled and / MCS = 29
`for the enabled 1B and the number of transmission layers is 1, and if
`
`-
`
`-
`
`the "CSI request" bit field is 1 bit and is set to trigger an aperiodic CSI report and N PRB s 4 , or
`
`the "CSI request" bit field is 2 bits and is triggering an aperiodic CSI report for one serving cell according to
`Table 7.2.1-lA, and , N PRB s 4 or,
`
`3GPP
`
`Samsung Ex. 1006
`
`IPR2022-00464
`Apple EX1006 Page 133
`
`

`

`Release 12
`
`
`134
`
`3GPP TS 36.213 V12.3.0 (2014-09)
`
`-
`
`-
`
`-
`
`the "CSI request" bit field is 2 bits and is triggering aperiodic CSI report for more than one serving cell
`20
`according to Table 7.2.1-1A and,
`, or,
`N
`PRB £
`
`the "CSI request" bit field is 2 bits and is triggering an aperiodic CSI report for one CSI process according to
`Table 7.2.1-1B and
`, or,
`4
`N
`PRB £
`
`the "CSI request" bit field is 2 bits and is triggering an aperiodic CSI report for more than one CSI process
`20
`according to Table 7.2.1-1B and,
`
`N
`PRB £
`
`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/EPDCCH for the same transport
`block using
`. If there is no initial PDCCH/EPDCCH with an uplink DCI format for the same
`0
`28
`£ I
`MCS £
`transport block using
`, the transport block size shall be determined from
`28
`0
`£ I
`MCS £
`
`-
`
`-
`
`the most recent semi-persistent scheduling assignment PDCCH/EPDCCH, 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.
`
`0
` and
`In DCI format 4 a transport block is disabled if either the combination of
`I
`MCS =
`28
`1
`I
`N
`of
` and
` is signalled, otherwise the transport block is enabled.
`PRB =
`MCS =
`
`N
`
`PRB >
`
`1
`
` or the combination
`
`3GPP
`
`IPR2022-00464
`Apple EX1006 Page 134
`
`

`

`Release 12
`
`135
`
`3GPP TS 36.213 V12.3.0 (2014-09)
`
`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 f3!:/:/- ACK, f3:/t-set and /J;J;t shall be configured to values
`
`according to Table 8.6.3-1,2,3 with the higher layer signalled indexes I ~Q- ACK, I :ft.set, and I ;j;t, respectively .
`
`Multiple codeword PUSCH transmission offsets /3::::,Q- ACK, f3:/t-set and /J;J;t shall be configured to values
`
`according to Table 8.6.3-1,2,3 with the higher layer signalled indexes l ~)i~CK, I :ft.set,MC and I ;j;t,MC,
`respectively.
`
`If the UE is configured with higher layer parameter UplinkPowerContro/D edicated-v l 2x0 for serving cell c, and if a
`subframe belongs to uplink power control subframe set 2 as indicated by the higher layer parameter tpc-SubframeSet(cid:173)
`rl 2, then for that subframe, the UE shall use
`
`-
`
`-
`
`.
`.
`the higher layer mdexes
`
`I HARQ- ACK
`offset,set2
`
`'
`
`] RI
`offset ,set2 and
`
`respectively in Tables 8.6.3-1,2,3, to determine
`codeword PUSCH transmissions, and
`
`HARQ- ACK
`offset
`/J
`
`,
`
`.
`I CQI
`] RI
`I HARQ- ACK
`I CQI
`offset' and
`offset,se/2 1ll place of offset
`offset
`·
`l fi
`l
`d /JCQI
`·
`/JRI
`offset an
`offset respective y or smg e
`
`'
`
`. d
`th high
`erlayer 1ll exes
`e
`CQI
`offset,MC respectively in Tables 8.6.3-1,2,3, to determine
`I
`multiple codeword PUSCH transmissions.
`
`I HARQ- ACK
`offset,MC,set2,
`
`f I HARQ- ACK
`d I CQI
`.
`] RI
`offset,MC,set2 an
`offset,MC,set2 1ll place O
`offset,MC
`/JHARQ- ACK
`/JRI
`offset and
`offset
`
`d
`] RI
`offset,MC an
`.
`/J CQI
`offset respectively for
`
`•
`
`,
`
`Table 8.6.3-1: Mapping of HARQ-ACK offset values and the index signalled by higher layers
`
`IHARQ- ACK
`offset
`
`or IHARQ-ACK
`offset,MC
`
`/JHARQ- ACK
`offset
`
`0
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`2.000
`
`2.500
`
`3.125
`
`4.000
`
`5.000
`
`6.250
`
`8.000
`
`10.000
`
`12.625
`
`15.875
`
`20.000
`
`31.000
`
`50.000
`
`80.000
`
`126.000
`
`1.0
`
`3GPP
`
`Samsung Ex. 1006
`
`IPR2022-00464
`Apple EX1006 Page 135
`
`

`

`Release 12
`
`136
`
`3GPP TS 36.213 V12.3.0 (2014-09)
`
`Table 8.6.3-2: Mapping of RI offset values and the index signalled by higher layers
`
`I:J.se1 or I:J.set,MC
`
`0
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`/3:J.set
`
`1.250
`
`1.625
`
`2.000
`
`2.500
`
`3.125
`
`4.000
`
`5.000
`
`6.250
`
`8.000
`
`10.000
`
`12.625
`
`15.875
`
`20.000
`
`reserved
`
`reserved
`
`reserved
`
`3GPP
`
`Samsung Ex. 1006
`
`IPR2022-00464
`Apple EX1006 Page 136
`
`

`

`Release 12
`
`137
`
`3GPP TS 36.213 V12.3.0 (2014-09)
`
`Table 8.6.3-3: Mapping of CQI offset values and the index signalled by higher layers
`
`I CQI
`offset
`
`ICQI
`or offset ,MC
`
`p CQI
`offset
`
`0
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`reserved
`
`reserved
`
`1.125
`
`1.250
`
`1.375
`
`1.625
`
`1.750
`
`2.000
`
`2.250
`
`2.500
`
`2.875
`
`3.125
`
`3.500
`
`4.000
`
`5.000
`
`6.250
`
`3GPP
`
`Samsung Ex. 1006
`
`IPR2022-00464
`Apple EX1006 Page 137
`
`

`

`Release 12
`
`
`138
`
`3GPP TS 36.213 V12.3.0 (2014-09)
`
`UE transmit antenna selection
`8.7
`UE transmit antenna selection is configured by higher layers via parameter ue-TransmitAntennaSelection.
`A UE configured with transmit antenna selection for a serving cell is not expected to
`
`•
`
`•
`
`•
`
`•
`
`be configured with more than one antenna port for any uplink physical channel or signal for any configured
`serving cell, or
`
`be configured with trigger type 1 SRS transmission on any configured serving cell, or
`
`be configured with simultaneous PUCCH and PUSCH transmission, or
`
`be configured with demodulation reference signal for PUSCH with OCC for any configured serving cell (see
`[3], subclause 5.5.2.1.1), or
`
`receive DCI Format 0 indicating uplink resource allocation type 1 for any serving cell.
`
`•
`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
`for PUSCH in response to the most recent command received via DCI Format 0 in subclause 5.3.3.2 of [4].
`If a UE is configured with more than one serving cell, the UE may assume the same transmit antenna port value is
`indicated in each PDCCH/EPDCCH with DCI format 0 in a given subframe.
`
`If open-loop UE transmit antenna selection is enabled by higher layers, the transmit antenna for PUSCH/SRS to be
`selected by the UE is not specified.
`
`3GPP
`
`IPR2022-00464
`Apple EX1006 Page 138
`
`

`

`Release 12
`
`
`139
`
`3GPP TS 36.213 V12.3.0 (2014-09)
`
`9
`
`9.1
`
`Physical downlink control channel procedures
`
`UE procedure for determining physical downlink control
`channel assignment
`
`PDCCH assignment procedure
`9.1.1
` according to
`The control region of each serving cell consists of a set of CCEs, numbered from 0 to
`1
`N
`,CCE -k
`subclause 6.8.1 in [3], where
` is the total number of CCEs in the control region of subframe
`.
`k
`N
`,CCE
`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, where monitoring implies attempting to decode each of the PDCCHs in the set
`according to all the monitored DCI formats.
`
`)
`
`(L
` at
`The set of PDCCH candidates to monitor are defined in terms of search spaces, where a search space
`kS
` { }8,4,2,1ÎL
`
`aggregation level
` 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
` are given by
`kS
`{
`} i
`+
`
`L
`
` mY(
`
`
`)
`¢+
`k
`
`mod
`
`ë
`N
`
`,CCE
`
`k
`
`/
`
`L
`
`û
`
`
`
`. For the PDCCH UE specific search
`. For the common search space
` is defined below,
`where
`0,
`,
`1
`i
`L
`mm =¢
`kY
`=- !
`space, for the serving cell on which PDCCH is monitored, if the monitoring UE is configured with carrier indicator field
`(
`)
`L n
`then
` where
` is the carrier indicator field value, else if the monitoring UE is not configured
`Mmm
`CIn
`=¢
`+
`×
`CI
`)
`(LM
`(
`)
`L
`with carrier indicator field then
`, where
`.
` is the number of PDCCH candidates to
`0,
`,
`1
`mm =¢
`m
`M
`=- !
`monitor in the given search space.
`
`Note that the carrier indicator field value is the same as ServCellIndex given in [11].
`
`The UE shall monitor one common search space in every non-DRX subframe at each of the aggregation levels 4 and 8
`on the primary cell.
`
`The UE shall monitor common search space on a cell to decode the PDCCHs necessary to decode PMCH on that cell if
`configured to decode PMCH by higher layers.
`
`If a UE is not configured for EPDCCH monitoring, and if the UE is not configured with a carrier indicator field, then
`the UE shall monitor one PDCCH UE-specific search space at each of the aggregation levels 1, 2, 4, 8 on each activated
`serving cell in every non-DRX subframe.
`
`If a UE is not configured for EPDCCH monitoring, and if the UE is configured with a carrier indicator field, then the
`UE 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 in every non-DRX subframe.
`
`If a UE is configured for EPDCCH monitoring on a serving cell, and if that serving cell is activated, and if the UE is not
`configured with a carrier indicator field, then the UE shall monitor one PDCCH UE-specific search space at each of the
`aggregation levels 1, 2, 4, 8 on that serving cell in all non-DRX subframes where EPDCCH is not monitored on that
`serving cell.
`
`If a UE is configured for EPDCCH monitoring on a serving cell, and if that serving cell is activated, and if the UE is
`configured with a carrier indicator field, then the UE shall monitor one or more PDCCH UE-specific search spaces at
`each of the aggregation levels 1, 2, 4, 8 on that serving cell as configured by higher layer signalling in all non-DRX
`subframes where EPDCCH is not monitored on that serving cell.
`
`The common and PDCCH UE-specific search spaces on the primary cell may overlap.
`
`3GPP
`
`IPR2022-00464
`Apple EX1006 Page 139
`
`

`

`Release 12
`Release 12
`
`140
`140
`
`3GPP TS 36.213 V1231} [2014-09)
`3GPP TS 36.213 V12.3.0 (2014-09)
`
`A UE configured with the carrier indicator field associated with monitoring PDCCH on serving cell 5‘ shall monitor
`AUE configured with the carrier indicator field associated with monitoring PDCCH on serving cell c shall monitor
`PDCCH configured with carrier indicator field and wifli CRC scrambled by C-RNTI in the PDCCH UE specific search
`PDCCH configured with carrier indicator field and with CRC scrambled by C-RNTI in the PDCCH UE specific search
`space of serving cell c.
`space of serving cell c.
`A UE configured with the carrier indicator field associated with monitoring PDCCH on the primary cell shall monitor
`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 PDCCH UE specific
`PDCCH configured with carrier indicator field and with CRC scrambled by SPS C-RNTI in the PDCCH UE specific
`search space of the primary cell.
`search space of the primary cell.
`The UE shall monitor the common search space for PDCCH without carrier indicator field.
`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
`For the serving cell on which PDCCH is monitored, if the UE is not configured with a carrier indicator field, it shall
`monitor the PDCCH UE specific search space for PDCCH without carrier indicator field, if the UE is configured with a
`monitor the PDCCH UE specific search space for PDCCH without carrier indicator field, if the UE is configured with a
`carrier indicator field it shall monitor the PDCCH UE specific search space fior PDCCH with carrier indicator field.
`carrier indicator field it shall monitor the PDCCH 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
`AUE 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
`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.
`monitored, the UE shall monitor PDCCH candidates at least for the same serving cell.
`A UE configured to monitor PDCCH candidates with CRC scrambled by C-RNTI or SPS C-RNTI with a common
`AUE configured to monitor PDCCH candidates with CRC scrambled by C-RNTI or SPS C-RNTI with a common
`payload size and with the same first CCE index items
`(as described in subclause 10. 1) but with difl'erent sets of DCI
`payload size and with the same first CCE index nccr (as described in subclause 10. 1) but with different sets ofDCI
`information fields as defined in [4] in the
`information fields as defined in [4] in the
`
`-
`
`common search space
`common search space
`PDCCH UE specific search space
`PDCCH UE specific search space
`on the prinlary cell shall assume that for the PDCCH candidates with CRC scrambled by C-RNTI or SPS C-RNTI,
`on the primary cell shall assume that for the PDCCH candidates with CRC scrambled by C-RNTI or SPS C-RNTI,
`
`-
`
`-
`
`-
`
`if the UE is configured with the carrier indicator field associated with monitoring the PDCCH on the
`if the UE is configured with the carrier indicator field associated with monitoring the PDCCH on the
`primary cell, only the PDCCH in the common search space is transmitted by the primary cell;
`primary cell, only the PDCCH in the common search space is transmitted by the primary cell;
`otherwise, only the PDCCH in the UE specific search space is transmitted by the primary cell.
`otherwise, only the PDCCH in the UE specific 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 (IF, and
`AUE 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 ClF for the given
`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 g'ven DCI format size may be transmitted in 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 PDCCH UE specific search space corresponding to any of the possible values of CIF for the given
`serving cell in any PDCCH UE specific search space corresponding to any of the possible values of CIF for the given
`DCI format size.
`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 m