Huawei Technologies Co., et al. v. Samsung Electronics Co., et al.
`Case No. 3:16-cv-02787-WHO (N.D. Cal.)
`
`
`
`Appendix 10 - U.S. Patent No. 8,885,587
`Defendants’ Accused Products operate on a Long-Term Evolution (LTE) network, and are compliant with all mandatory
`provisions of the LTE standards, for example, 3GPP TS 36.213 ( including version 10.2.0, and all subsequent releases and versions)
`(collectively, “the TS 36.213 standard”) and 3GPP TS 36.300 (including version 10.3.0, and all subsequent releases and versions)
`(collectively, “the TS 36.300 standard”). By complying with the TS 36.213 and TS 36.300 standards, Defendants’ Accused
`Products infringe at least claims 3-5, 9-11 of U.S. Patent No. 8,885,587, as explained more fully below.
`3. A method for
`Defendants’ Accused Products, including at least those identified on Exhibit A, operate on an LTE
`feeding back
`network, support carrier aggregation, and feed back ACK/NACK information for carrier aggregation.
`Acknowledgement /
`
`For example, the TS 36.213 v10.2.0 standard defines the characteristics of the physical layer procedures in
`Negative-
`the FDD and TDD modes of E-UTRA, and Defendants’ Accused Products are compliant with, for
`acknowledgement
`example, subsection 10.1 of the TS 36.213 v10.2.0 standard, which provides in relevant part as follows:
`(ACK/NACK)
`
`information for
`3GPP TS 36.213 v10.2.0, Sec 10.1.2.2:
`carrier aggregation,
`10.1.2.2 FDD HARQ-ACK procedures for more than one configured serving
`the method
`cell
`comprising:
`The FDD HARQ-ACK feedback procedures for more than one configured
`serving cell are either based on a PUCCH format 1b with channel
`selection HARQ-ACK procedure as described in section 10.1.2.2.1 or a
`PUCCH format 3 HARQ-ACK procedure as described in section 10.1.2.2.2.
`
`3GPP TS 36.213 v10.2.0, Sec 10.1.3.2:
`
`
`
`1
`
`Samsung Exhibit 1011, Page 1
`
`
`Case No. 3:16-cv-02787-WHO (N.D. Cal.)
`
`
`
`Appendix 10 - U.S. Patent No. 8,885,587
`Defendants’ Accused Products operate on a Long-Term Evolution (LTE) network, and are compliant with all mandatory
`provisions of the LTE standards, for example, 3GPP TS 36.213 ( including version 10.2.0, and all subsequent releases and versions)
`(collectively, “the TS 36.213 standard”) and 3GPP TS 36.300 (including version 10.3.0, and all subsequent releases and versions)
`(collectively, “the TS 36.300 standard”). By complying with the TS 36.213 and TS 36.300 standards, Defendants’ Accused
`Products infringe at least claims 3-5, 9-11 of U.S. Patent No. 8,885,587, as explained more fully below.
`3. A method for
`Defendants’ Accused Products, including at least those identified on Exhibit A, operate on an LTE
`feeding back
`network, support carrier aggregation, and feed back ACK/NACK information for carrier aggregation.
`Acknowledgement /
`
`For example, the TS 36.213 v10.2.0 standard defines the characteristics of the physical layer procedures in
`Negative-
`the FDD and TDD modes of E-UTRA, and Defendants’ Accused Products are compliant with, for
`acknowledgement
`example, subsection 10.1 of the TS 36.213 v10.2.0 standard, which provides in relevant part as follows:
`(ACK/NACK)
`
`information for
`3GPP TS 36.213 v10.2.0, Sec 10.1.2.2:
`carrier aggregation,
`10.1.2.2 FDD HARQ-ACK procedures for more than one configured serving
`the method
`cell
`comprising:
`The FDD HARQ-ACK feedback procedures for more than one configured
`serving cell are either based on a PUCCH format 1b with channel
`selection HARQ-ACK procedure as described in section 10.1.2.2.1 or a
`PUCCH format 3 HARQ-ACK procedure as described in section 10.1.2.2.2.
`
`3GPP TS 36.213 v10.2.0, Sec 10.1.3.2:
`
`
`
`1
`
`Samsung Exhibit 1011, Page 1
`
`
`
`receiving downlink
`control information
`(DCI) which is sent
`by a base station and
`transmitted by a
`downlink component
`carrier; and
`
`
`
`
`
`10.1.3.2 TDD HARQ-ACK procedure for more than one configured serving
`cell
`The TDD HARQ-ACK feedback procedures for more than one configured
`serving cell are either based on a PUCCH format 1b with channel
`selection HARQ-ACK procedure as described in section 10.1.3.2.1 or a
`PUCCH format 3 HARQ-ACK procedure as described in section 10.1.3.2.2.
`Defendants’ Accused Products receive downlink control information (DCI) which is sent by a base station
`and transmitted by a downlink component carrier. More specifically, the Defendants’ Accused Products
`receive DCI from a base station on the physical downlink control channel (PDCCH), which is transmitted
`on a downlink component carrier.
`
`Defendants’ Accused Products are compliant with, for example, subsections 5.1 and 7.1 of the TS 36.213
`v10.2.0 standard, which provides in relevant part as follows:
`
`3GPP TS 36.213 v10.2.0, Sec 7.1:
`7.1 UE procedure for receiving the physical downlink shared channel
`Except the subframes indicated by the higher layer parameter mbsfn-
`SubframeConfigList, a UE shall upon detection of a PDCCH of a serving
`cell with DCI format 1, 1A, 1B, 1C, 1D, 2, 2A, 2B or 2C intended for
`the UE in a subframe, decode the corresponding PDSCH in the same
`subframe with the restriction of the number of transport blocks defined
`in the higher layers.
`A UE may assume that positioning reference signals are not present in
`
`2
`
`Samsung Exhibit 1011, Page 2
`
`
`
`
`
`
`
`resource blocks in which it shall decode PDSCH according to a detected
`PDCCH with CRC scrambled by the SI-RNTI or P-RNTI with DCI format 1A or
`1C intended for the UE.
`[A UE is not expected to receive in a MBSFN subframe PDSCH and PRS with
`different CP sizes. A UE configured to decode PRS only in MBSFN
`subframes is not expected to decode other transmissions in those MBSFN
`subframes.]
`A UE configured with the carrier indicator field for a given serving
`cell may assume that the carrier indicator field is not present in any
`PDCCH of the serving cell with CRC scrambled by SI-RNTI, P-RNTI, RA-
`RNTI, Temporary C-RNTI, TPC-RNTI, SPS C-RNTI or by C-RNTI if located in
`the common search space that is described in section 9.1. Otherwise,
`the configured UE shall assume that for the given serving cell the
`carrier indicator field is present in PDCCH located in the UE specific
`search space described in section 9.1 when the PDCCH CRC is scrambled
`by C-RNTI or SPS C-RNTI.
`
`3GPP TS 36.213 v10.2.0, Sec 5.1.2.1:
`5.1.2.1 UE Behaviour
` is a UE specific correction value, also referred to as a TPC
`•
`PUCCHδ
`command, included in a PDCCH with DCI format 1A/1B/1D/1/2A/2/2B/2C
`for the primary cell or sent jointly coded with other UE specific
`
`3
`
`Samsung Exhibit 1011, Page 3
`
`
`
`
`
`
`
`feeding back
`ACK/NACK
`information
`according to a
`command indicated
`by a common field
`preset in the DCI,
`
`
`PUCCH correction values on a PDCCH with DCI format 3/3A whose CRC
`parity bits are scrambled with TPC-PUCCH-RNTI.
`o The UE attempts to decode a PDCCH of DCI format 3/3A with the
`UE’s TPC-PUCCH-RNTI and one or several PDCCHs of DCI format
`1A/1B/1D/1/2A/2/2B/2C with the UE’s C-RNTI or SPS C-RNTI on
`every subframe except when in DRX.
`o If the UE decodes a PDCCH with DCI format
`1A/1B/1D/1/2A/2/2B/2C for the primary cell and the
`corresponding detected RNTI equals the C-RNTI or SPS C-RNTI
`of the UE, the UE shall use the PUCCHδ
` provided in that PDCCH
`unless the TPC field in the DCI format is used to determine
`the PUCCH resource as in section 10.1.
`
`Defendants’ Accused Products feed back ACK/NACK feedback information according to a command
`indicated by a common field preset in the downlink control information. More specifically, the
`Defendants’ Accused Products will feed back ACK/NACK information on the physical uplink control
`channel (PUCCH) according to the contents of the received transmit power control (TPC) field of the DCI,
`which is a common field that can be used both to indicate TPC and ACK resource indication (ARI).
`
`Defendants’ Accused Products are compliant with, for example, subsection 5.1 of the TS 36.213 v10.2.0
`standard, which provides in relevant part as follows:
`
`3GPP TS 36.213 v10.2.0, Sec 5.1.2.1:
`
`4
`
`Samsung Exhibit 1011, Page 4
`
`
`
`
`
`
`
`•
`
` is a UE specific correction value, also referred to as a TPC
`PUCCHδ
`command, included in a PDCCH with DCI format 1A/1B/1D/1/2A/2/2B/2C
`for the primary cell or sent jointly coded with other UE specific
`PUCCH correction values on a PDCCH with DCI format 3/3A whose CRC
`parity bits are scrambled with TPC-PUCCH-RNTI.
`o The UE attempts to decode a PDCCH of DCI format 3/3A with the
`UE’s TPC-PUCCH-RNTI and one or several PDCCHs of DCI format
`1A/1B/1D/1/2A/2/2B/2C with the UE’s C-RNTI or SPS C-RNTI on
`every subframe except when in DRX.
`o If the UE decodes a PDCCH with DCI format
`1A/1B/1D/1/2A/2/2B/2C for the primary cell and the
`corresponding detected RNTI equals the C-RNTI or SPS C-RNTI
`of the UE, the UE shall use the PUCCHδ
` provided in that PDCCH
`unless the TPC field in the DCI format is used to determine
`the PUCCH resource as in section 10.1.
`
`
`Defendants’ Accused Products are further compliant with, for example, subsection 10.1 of the TS 36.213
`v10.2.0 standard, which provides in relevant part as follows:
`
`3GPP TS 36.213 v10.2.0, Sec 10.1.2.2:
`10.1.2.2 FDD HARQ-ACK procedures for more than one configured serving
`cell
`
`5
`
`Samsung Exhibit 1011, Page 5
`
`
`
`
`
`
`
`wherein the common
`field is configured as
`one command
`according to a type of
`a downlink
`component carrier
`transmitting the DCI,
`and the common field
`is indicative of one of
`
`The FDD HARQ-ACK feedback procedures for more than one configured
`serving cell are either based on a PUCCH format 1b with channel
`selection HARQ-ACK procedure as described in section 10.1.2.2.1 or a
`PUCCH format 3 HARQ-ACK procedure as described in section 10.1.2.2.2.
`
`3GPP TS 36.213 v10.2.0, Sec 10.1.3.2:
`10.1.3.2 TDD HARQ-ACK procedure for more than one configured serving
`cell
`The TDD HARQ-ACK feedback procedures for more than one configured
`serving cell are either based on a PUCCH format 1b with channel
`selection HARQ-ACK procedure as described in section 10.1.3.2.1 or a
`PUCCH format 3 HARQ-ACK procedure as described in section 10.1.3.2.2.
`
`The common field in the DCI received by Defendants’ Accused Products is configured as one command
`according to a type of a downlink component carrier transmitting the DCI. This common field is
`indicative of one of a TPC command and an ARI command. This common field is configured by
`configuring the common field in at least one piece of DCI transmitted by a system-linked downlink
`component carrier as a TPC command and configuring the common field in at least one piece of DCI
`transmitted by a non-system-linked downlink component carrier as an ARI command.
`
`For example, the LTE standards provide HARQ-ACK feedback procedures for both FDD and TDD
`through PUCCH on the uplink primary cell. The downlink primary cell is system-linked to the uplink
`
`6
`
`Samsung Exhibit 1011, Page 6
`
`
`
`
`
`
`
`a transmission power
`control (TPC)
`command and an
`ACK resource
`indication (ARI)
`command, wherein
`the common field is
`configured by
`configuring the
`common field in at
`least one piece of
`DCI transmitted by a
`system-linked
`downlink component
`carrier as a TPC
`command and
`configuring the
`common field in at
`least one piece of
`DCI transmitted by a
`non-system-linked
`downlink component
`
`primary cell, while downlink secondary cells are non-system-linked to the uplink primary cell. For carrier
`aggregation, a component carrier corresponds to a serving cell, thus a downlink primary component carrier
`corresponds to a downlink primary cell, and a downlink secondary component carrier corresponds to a
`downlink secondary cell. The LTE standards further explain that when the base station uses the PDCCH
`on the downlink primary cell to schedule PDSCH on the downlink primary cell, the UE will interpret the
`TPC command field in the PDCCH as a transmit power control command. Whereas, when the base station
`uses PDCCH on a downlink secondary cell to schedule PDSCH on a downlink secondary cell, the UE will
`interpret this same TPC command field as an ARI command.
`
`Defendants’ Accused Products are compliant with, for example, subsection 5.1 of the TS 36.213 v10.2.0
`standard, which provides in relevant part as follows:
`
`3GPP TS 36.213 v10.2.0, Sec 5.1.2.1:
`5.1.2
`Physical uplink control channel
`5.1.2.1 UE behaviour
` is a UE specific correction value, also referred to as a TPC
`•
`PUCCHδ
`command, included in a PDCCH with DCI format 1A/1B/1D/1/2A/2/2B/2C
`for the primary cell or sent jointly coded with other UE specific
`PUCCH correction values on a PDCCH with DCI format 3/3A whose CRC
`parity bits are scrambled with TPC-PUCCH-RNTI.
`o The UE attempts to decode a PDCCH of DCI format 3/3A with the
`UE’s TPC-PUCCH-RNTI and one or several PDCCHs of DCI format
`
`7
`
`Samsung Exhibit 1011, Page 7
`
`
`
`carrier as an ARI
`command.
`
`
`
`
`
`1A/1B/1D/1/2A/2/2B/2C with the UE’s C-RNTI or SPS C-RNTI on
`every subframe except when in DRX.
`o If the UE decodes a PDCCH with DCI format
`1A/1B/1D/1/2A/2/2B/2C for the primary cell and the
`corresponding detected RNTI equals the C-RNTI or SPS C-RNTI
`of the UE, the UE shall use the PUCCHδ
` provided in that PDCCH
`unless the TPC field in the DCI format is used to determine
`the PUCCH resource as in section 10.1.
`
`
`Defendants’ Accused Products are compliant with, for example, subsection 10.1 of the TS 36.213 v10.2.0
`standard, which provides in relevant part as follows:
`
`3GPP TS 36.213 v10.2.0, Sec 10.1.2.2.1:
`10.1.2.2.1
`PUCCH format 1b with channel selection HARQ-ACK
`procedure
`For FDD with two configured serving cells and PUCCH format 1b with
`channel selection…
`The UE shall determine the A PUCCH resources, )1(
`
` where
`n
`Ai
`0
`1
`≤≤
`−
`PUCCH,i
`ordered according to the serving cell in increasing order of j given in
`Table 10.1.2.2.1-1, according to
`- for a PDSCH transmission indicated by the detection of a
` on the primary cell, or for a
`corresponding PDCCH in subframe
`4−n
`
`8
`
`Samsung Exhibit 1011, Page 8
`
`
`
`
`
`
`
`1
`
`PUCCH
`
`1
`
`PDCCH indicating downlink SPS release (defined in section 9.2) in
`subframe
` on the primary cell, the PUCCH resource is
`4−n
`(1)
`)1(
`, and for transmission mode that support up to two
`n
`n
`N
`=
`i
`CCE,
`PUCCH
`PUCCH,
`i
`transport blocks, the PUCCH resource )1(
`n
` is given by
`PUCCH, +i
`(1)
`)1(
` where
` is the number of the first CCE used
`n
`n
`1 N
`++
`=+
`n
`CCE,
`i
`i
`PUCCH
`PUCCH,
`1
`for transmission of the corresponding PDCCH and (1)
` is configured
`N
`by higher layers.
`- …
`- for a PDSCH transmission indicated by the detection of a
`corresponding PDCCH in subframe
` on the secondary cell, the
`4−n
`value of )1(
`, and the value of )1(
`n
` for the transmission mode
`n
`PUCCH,i
`PUCCH, +i
`that support up to two transport blocks is determined according to
`higher layer configuration and Table 10.1.2.2.1-2. The TPC field in
`the DCI format of the corresponding PDCCH shall be used to
`determine the PUCCH resource values from one of the four resource
`values configured by higher layers, with the mapping defined in
`Table 10.1.2.2.1-2. For a UE configured for a transmission mode
`that support up to two transport blocks a PUCCH resource value in
`)1(
`)1(
`,
`Table 10.1.2.2.1-2 maps to two PUCCH resources
`n
`i n
`(
`,
`)
`+i
`PUCCH,
`PUCCH,
`1
`otherwise, the PUCCH resource value maps to a single PUCCH resource
`
`+
`
`CCE,
`
`i
`
`9
`
`Samsung Exhibit 1011, Page 9
`
`
`
`
`
`
`
`n
`
`)1(
`PUCCH,i
`
`.
`
`n
`
`…
`
`PUCCH format 3 HARQ-ACK procedure
`10.1.2.2.2
`p
`,3(
`)
` or
`For FDD with PUCCH format 3, the UE shall use PUCCH resource
`PUCCH
`pn
`,1(
`)
` for transmission of HARQ-ACK in subframe n on antenna port p
`PUCCH
`where
`- for a PDSCH transmission only on the primary cell indicated by the
`, or for a PDCCH
`detection of a corresponding PDCCH in subframe
`4−n
`indicating downlink SPS release (defined in section 9.2) in
`subframe
` on the primary cell, the UE shall use PUCCH format
`4−n
`pp
`,1(
`)
`=
`(1)
`pn
`,1(
`)
`1a/1b and PUCCH resource
` with
`, where CCEn
` is
`n
`n
`N
`=
`+
`0
`CCE
`PUCCH
`PUCCH
`PUCCH
`the number of the first CCE (i.e. lowest CCE index used to
`construct the PDCCH) used for transmission of the corresponding
` is configured by higher layers. For two antenna
`PDCCH and (1)
`N
`port transmission the PUCCH resource for
`p = is given by
`1p
`pp
`,1(
`)
`=
`(1)
`.
`n
`n
`N
`1
`++
`=
`1
`PUCCH
`PUCCH
`- …
`- for a PDSCH transmission on the secondary cell indicated by the
`detection of a corresponding PDCCH in subframe
`, the UE shall
`4−n
`
`PUCCH
`
`CCE
`
`10
`
`Samsung Exhibit 1011, Page 10
`
`
`
`
`
`
`
`
`
`)
`
`)
`
`p
`p
`,3(
`)
`,3(
`)
` with the value of
`use PUCCH format 3 and PUCCH resource
`n
`n
`PUCCH
`PUCCH
`is determined according to higher layer configuration and Table
`10.1.2.2.2-1. The TPC field in the DCI format of the corresponding
`PDCCH shall be used to determine the PUCCH resource values from one
`of the four resource values configured by higher layers, with the
`mapping defined in Table 10.1.2.2.2-1. For a UE configured for two
`antenna port transmission, a PUCCH resource value in Table
`10.1.2.2.2-1 maps to two PUCCH resources with the first PUCCH
`0ppn
`,3(
`= for antenna port 0p and the second PUCCH resource
`resource
`PUCCH
`1ppn
`,3(
`= for antenna port 1p , otherwise, the PUCCH resource value
`PUCCH
`0ppn
`,3(
`= for antenna port 0p . A UE
`maps to a single PUCCH resource
`PUCCH
`shall assume that the same HARQ-ACK PUCCH resource value is
`transmitted in each DCI format of the corresponding secondary cell
`PDCCH assignments in a given subframe..
`
`)
`
`
`3GPP TS 36.213 v10.2.0, Sec 10.1.3.2:
`10.1.3.2.1
`PUCCH format 1b with channel selection HARQ-ACK
`procedure
`For TDD HARQ-ACK multiplexing with PUCCH format 1b with channel
`selection and two configured serving cells and a subframe n with
`2≤M
`where M is the number of elements in the set K defined in Table
`
`
`
`11
`
`Samsung Exhibit 1011, Page 11
`
`
`
`
`
`
`
`10.1.3.1-1, the UE shall …
`- for a PDSCH transmission indicated by the detection of a
`mkn −
`corresponding PDCCH within subframe(s)
`, where mk
`K∈ on the
`primary cell, or for a PDCCH indicating downlink SPS release
`mkn −
`(defined in section 9.2) within subframe(s)
`, where mk
`K∈ on
`the primary cell, the PUCCH resource is
`(
`)
`(1)
`n
`mM
`NmN
`N
`n
`1
`⋅−−
`=
`+
`⋅+
`+
`, …
`c
`CCE
`PUCCH
`- …
`- for a PDSCH transmission indicated by the detection of a
`corresponding PDCCH within subframe(s)
`kn − , where
`Kk ∈ on the
`secondary cell, the value of )1(
`, and the value of )1(
`n
` for a
`n
`PUCCH,i
`PUCCH, +i
`subframe n with
` or for a subframe n with
`1=M and a
`2=M
`transmission mode on the secondary cell that supports up to two
`transport blocks is determined according to higher layer
`configuration and Table 10.1.2.2.1-2. The TPC field in the DCI
`format of the corresponding PDCCH shall be used to determine the
`PUCCH resource values from one of the four resource values
`configured by higher layers, with the mapping defined in Table
`10.1.2.2.1-2. For a UE configured for a transmission mode on the
`secondary cell that supports up to two transport blocks and a
`1=M , or for a subframe n with
`, a PUCCH
`subframe n with
`2=M
`
`,
`
`m
`
`(1)
`PUCCH
`
`1
`
`,
`
`i
`
`c
`
`1
`+
`
`12
`
`Samsung Exhibit 1011, Page 12
`
`
`
`
`
`
`
`resource value in Table 10.1.2.2.1-2 maps to two PUCCH resources
`)1(
`)1(
`, otherwise, the PUCCH resource value maps to a
`n
`i n
`(
`,
`)
`+i
`PUCCH,
`PUCCH,
`1
`single PUCCH resource )1(
`. A UE shall assume that the same HARQ-
`n
`PUCCH,i
`ACK PUCCH resource value is transmitted in the TPC field on all
`PDCCH assignments on the secondary cells in a given subframe.
`-
`
`…
`For TDD HARQ-ACK multiplexing with PUCCH format 1b with channel
` and two configured serving cells,
`selection and sub-frame n with
`2>M
`where M is the number of elements in the set K defined in Table
`10.1.3.1-1…
`
`For Primary cell:
`- If for a PDSCH transmission on the primary cell where there is not
`a corresponding PDCCH detected within the subframe(s)
`kn − , where
`Kk ∈ ,
`o the value of )1(
`n
` is determined according to higher layer
`PUCCH,0
`configuration and Table 9.2-2.
`o for a PDSCH transmission on the primary cell indicated by the
`detection of a corresponding PDCCH within the subframe(s)
`mkn −
`, where mk
`K∈ with the DAI value in the PDCCH equal to
`
`13
`
`Samsung Exhibit 1011, Page 13
`
`
`
`
`
`
`
`‘1’ (defined in Table 7.3-X) or a PDCCH indicating downlink
`SPS release (defined in section 9.2) within the subframe(s)
`, where mk
`K∈ with the DAI value in the PDCCH equal to
`mkn −
`(
`)
`(1)
`n
`M m
`N m N
`n
`N
`1
`=
`− − ⋅
`+ ⋅
`+
`+
`‘1’, the PUCCH resource
` …
`c
`PUCCH,1
`CCE,
`o …
`- Otherwise,
`o for a PDSCH transmission on the primary cell indicated by the
`detection of a corresponding PDCCH within the subframe(s)
`, where mk
`K∈ with the DAI value in the PDCCH equal to
`mkn −
`either ‘1’ or ‘2’ or a PDCCH indicating downlink SPS release
`mkn −
`, where
`(defined in section 9.2) within the subframe(s)
`K∈ with the DAI value in the PDCCH equal to either ‘1’ or
`mk
`(
`)
`(1)
`n
`mM
`NmN
`n
`N
`1
`=
`⋅−−
`⋅+
`+
`+
`,…
`‘2’, the PUCCH resource
`c
`CCE
`PUCCH
`o …
`For Secondary cell:
`- for a PDSCH transmission on the secondary cell indicated by the
`detection of a corresponding PDCCH on the primary cell within the
`, where mk
`K∈ with the DAI value in the PDCCH
`subframe(s)
`n k−
`equal to either ‘1’ or ‘2’, the PUCCH resources
`(
`)
`(1)
`n
`mM
`NmN
`N
`n
`1
`⋅−−
`=
`+
`⋅+
`+
`, …
`c
`CCE
`PUCCH
`
`,
`
`i
`
`c
`
`1
`+
`
`,
`
`m
`
`(1)
`PUCCH
`
`14
`
`c
`
`1
`+
`
`m
`
`(1)
`PUCCH
`
`,
`
`i
`
`c
`
`1
`+
`
`,
`
`m
`
`(1)
`PUCCH
`
`m
`
`Samsung Exhibit 1011, Page 14
`
`
`
`
`
`
`
`PUCCH,
`
`2
`
`PUCCH,
`
`3
`
`- for a PDSCH transmission indicated by the detection of a
`corresponding PDCCH within the subframe(s)
`kn − , where
`Kk ∈ on the
`secondary cell, the value of )1(
`and )1(
`n
`n
` is determined
`according to higher layer configuration and Table 10.1.2.2.1-2. The
`TPC field in the DCI format of the corresponding PDCCH shall be
`used to determine the PUCCH resource values from one of the four
`resource values configured by higher layers, with the mapping
`defined in Table 10.1.2.2.1-2. A UE shall assume that the same
`HARQ-ACK PUCCH resource value is transmitted in the TPC field on
`all PDCCH assignments on the secondary cell in a given subframe.
`-
`
`…
`PUCCH format 3 HARQ-ACK procedure
`10.1.3.2.2
`For TDD HARQ-ACK transmission with PUCCH format 3 and sub-frame n with
`1≥M and more than one configured serving cell, where M is the number
`of elements in the set K defined in Table 10.1.3.1-1, the UE shall use
`p
`)
`,3(
`pn
`,1(
`)
` or
` for transmission of HARQ-ACK in subframe
`PUCCH resource
`n
`PUCCH
`PUCCH
`n on antenna port p where
`- for a single PDSCH transmission only on the primary cell indicated
`by the detection of a corresponding PDCCH within subframe(s)
`mkn − ,
`where
`km ∈ with the DAI value in the PDCCH equal to ‘1’ (defined in
`K
`Table 7.3-X), or for a PDCCH indicating downlink SPS release
`
`15
`
`Samsung Exhibit 1011, Page 15
`
`
`
`
`
`
`
`)
`
`c
`
`+
`
`1
`
`m
`
`(1)
`PUCCH
`
`km ∈ with
`mkn − , where
`(defined in section 9.2) within subframe(s)
`K
`the DAI value in the PDCCH equal to ‘1’, the UE shall use PUCCH
`pn
`,1(
`)
`format 1a/1b and PUCCH resource
` with
`PUCCH
`p =
`0p
`pp
`,1(
`=
`n
`mM
`NmN
`N
`n
`(
`)1
`−
`=
`⋅−
`+
`⋅+
`+
`,…
` for antenna port
`0
`c
`CCE,
`PUCCH
`1>M and a PDSCH transmission only on the primary cell
`- -
`for
`where there is not a corresponding PDCCH detected within
`mkn − , where
`km ∈ and an additional PDSCH transmission
`subframe(s)
`K
`only on the primary cell indicated by the detection of a
`mkn − , where
`km ∈ with the
`corresponding PDCCH within subframe(s)
`K
`DAI value in the PDCCH equal to ‘1’ (defined in Table 7.3-X) or a
`PDCCH indicating downlink SPS release (defined in section 9.2)
`within the subframe(s)
`mkn − , where
`km ∈ with the DAI value in the
`K
`b in subframe n
`PDCCH equal to ‘1’, the UE shall transmit ( )
`( )
`b
`0 ,
`1
` selected from A PUCCH
`using PUCCH format 1b on PUCCH resource (1)
`n
`PUCCH
`resources (1)
`n
` where 0
`≤ ≤ − , according to Table 10.1.3.2-1 and
`i A
`1
`PUCCH,i
`3=A
`2=A
`Table 10.1.3.2-2 for
` and
`, respectively. For a UE
`configured with a transmission mode that supports up to two
`3=A
`2=A
`; otherwise,
`.
`transport blocks on the primary cell,
`o The PUCCH resource )1(
` is determined according to higher
`n
`layer configuration and Table 9.2-2. The PUCCH resource )1(
`n
`
`PUCCH,0
`
`16
`
`PUCCH,1
`
`
`
`Samsung Exhibit 1011, Page 16
`
`
`
`
`
`
`
`is determined as (1)
`n
`M m
`N m N
`(
`1)
`− − ⋅
`+ ⋅
`c
`PUCCH,1
` is configured by higher layers,…
`N
`
`+
`
`n
`
`CCE,m
`
`+
`
`N
`
`(1)
`PUCCH
`
`1
`+
`
`, where
`
`c
`
`=
`
`(1)
`PUCCH
`
`…
`- for a PDSCH transmission on the secondary cell indicated by the
`detection of a corresponding PDCCH within subframe(s)
`mkn − , where
`p
`,3(
`)
`km ∈ , the UE shall use PUCCH format 3 and PUCCH resource
`
`n
`K
`PUCCH
`p
`)
`,3(
`where the value of
` is determined according to higher layer
`n
`PUCCH
`configuration and Table 10.1.2.2.2-1 and the TPC field in the
`corresponding PDCCH shall be used to determine the PUCCH resource
`value from one of the four resource values configured by higher
`layers, with the mapping defined in Table 10.1.2.2.2-1. If a PDCCH
`corresponding to a PDSCH on the primary cell within subframe(s)
`mkn − , where
`km ∈ , or a PDCCH indicating downlink SPS release
`K
`mkn − , where
`km ∈ , is
`(defined in section 9.2) within subframe(s)
`K
`detected, the TPC field in the PDCCH with the DAI value greater
`than ‘1’ shall be used to determine the PUCCH resource value from
`one of the four resource values configured by higher layers, with
`the mapping defined in Table 10.1.2.2.2-1. A UE shall assume that
`the same HARQ-ACK PUCCH resource value is transmitted on all PDCCH
`assignments in the primary cell and in each secondary cell that are
`used to determined the PUCCH resource value within the subframe(s)
`
`17
`
`Samsung Exhibit 1011, Page 17
`
`
`
`
`
`
`
`k m ∈ .
`K
`
`mkn − , where
`. . .
`Defendants’ Accused Products are compliant with, for example, subsection 7.5 of the 3GPP TS 36.300
`v10.3.0 standard, which provides in relevant part as follows:
`
`3GPP TS 36.300 v10.3.0, Sec 7.5:
`7.5 Carrier Aggregation
`When CA is configured, the UE only has one RRC connection with the
`network. At RRC connection establishment/re-establishment/handover, one
`serving cell provides the NAS mobility information (e.g. TAI), and at
`RRC connection re-establishment/handover, one serving cell provides the
`security input. This cell is referred to as the Primary Cell (PCell).
`In the downlink, the carrier corresponding to the PCell is the Downlink
`Primary Component Carrier (DL PCC) while in the uplink it is the Uplink
`Primary Component Carrier (UL PCC).
`Depending on UE capabilities, Secondary Cells (SCells) can be
`configured to form together with the PCell a set of serving cells. In
`the downlink, the carrier corresponding to an SCell is a Downlink
`Secondary Component Carrier (DL SCC) while in the uplink it is an
`Uplink Secondary Component Carrier (UL SCC).
`The configured set of serving cells for a UE therefore always consists
`of one PCell and one or more SCells:
`
`18
`
`Samsung Exhibit 1011, Page 18
`
`
`
`
`
`
`
`- For each SCell the usage of uplink resources by the UE in addition
`to the downlink ones is configurable (the number of DL SCCs
`configured is therefore always larger than or equal to the number
`of UL SCCs and no SCell can be configured for usage of uplink
`resources only);
`- From a UE viewpoint, each uplink resource only belongs to one
`serving cell;
`- The number of serving cells that can be configured depends on the
`aggregation capability of the UE (see subclause 5.5);
`- PCell can only be changed with handover procedure (i.e. with
`security key change and RACH procedure);
`- PCell is used for transmission of PUCCH;
`- Unlike SCells, PCell cannot be de-activated (see subclause 11.2);
`- Re-establishment is triggered when PCell experiences RLF, not when
`SCells experience RLF;
`- NAS information is taken from PCell.
`
`
`Defendants’ Accused Products are compliant with, for example, subsection 10.1 of the TS 36.213 v10.2.0
`standard, which provides in relevant part as follows:
`
`3GPP TS 36.213 v10.2.0, Sec 10.1:
`10.1 UE procedure for determining physical uplink control channel assignment
`…
`
`19
`
`Samsung Exhibit 1011, Page 19
`
`
`
`4. The method
`according to claim 3,
`wherein the at least
`one piece of DCI
`transmitted by a
`system-linked
`downlink component
`carrier comprises
`DCI corresponding to
`physical downlink
`shared channel
`(PDSCH)
`transmission of a
`downlink primary
`component carrier.
`
`
`
`
`
`A UE transmits PUCCH only on the primary cell.
`The Defendant’s Accused Products infringe claim 3 for at least the reasons given above. Furthermore, at
`least one piece of DCI transmitted by a system-linked downlink component carrier comprises DCI
`corresponding to a physical downlink shared channel (PDSCH) transmission of a downlink primary
`component carrier.
`
`As explained above in connection with claim 3, the downlink primary component carrier is a system-
`linked downlink component carrier. And as explained above in connection with claim 3, the base station
`may send DCI on the PDCCH of the downlink primary component carrier to schedule PDSCH, and the UE
`will interpret the TPC command field sent in this DCI as a transmit power control command.
`
`Defendants’ Accused Products are compliant with, for example, subsection 5.1 of the 3GPP TS 36.213
`v10.2.0 standard, which provides in relevant part as follows:
`
`3GPP TS 36.213 v10.2.0, Sec 5.1.2.1:
`5.1.2
`Physical uplink control channel
`5.1.2.1 UE behaviour
` is a UE specific correction value, also referred to as a TPC
`•
`PUCCHδ
`command, included in a PDCCH with DCI format 1A/1B/1D/1/2A/2/2B/2C
`for the primary cell or sent jointly coded with other UE specific
`PUCCH correction values on a PDCCH with DCI format 3/3A whose CRC
`parity bits are scrambled with TPC-PUCCH-RNTI.
`
`20
`
`Samsung Exhibit 1011, Page 20
`
`
`
`
`
`
`
`5. The method
`according to claim 3,
`wherein the at least
`one piece of DCI
`transmitted by a
`system-linked
`downlink component
`carrier comprises at
`least one piece of
`DCI transmitted by a
`downlink primary
`component carrier.
`
`o The UE attempts to decode a PDCCH of DCI format 3/3A with the
`UE’s TPC-PUCCH-RNTI and one or several PDCCHs of DCI format
`1A/1B/1D/1/2A/2/2B/2C with the UE’s C-RNTI or SPS C-RNTI on
`every subframe except when in DRX.
`o If the UE decodes a PDCCH with DCI format
`1A/1B/1D/1/2A/2/2B/2C for the primary cell and the
`corresponding detected RNTI equals the C-RNTI or SPS C-RNTI
`of the UE, the UE shall use the PUCCHδ
` provided in that PDCCH
`unless the TPC field in the DCI format is used to determine
`the PUCCH resource as in section 10.1.
`The Defendant’s Accused Products infringe claim 3 for at least the reasons given above. Furthermore, at
`least one piece of DCI transmitted by the system-linked downlink component carrier comprises at least one
`piece of DCI transmitted by a downlink primary component carrier.
`
`As explained above in connection with claim 3, a base station may send DCI on the PDCCH of the
`downlink primary component carrier to schedule PDSCH, and the UE will interpret the TPC command
`field sent in this DCI as a transmit power control command.
`
`Defendants’ Accused Products are compliant with, for example, subsection 5.1 of the 3GPP TS 36.213
`v10.2.0 standard, which provides in relevant part as follows:
`
`3GPP TS 36.213 v10.2.0, Sec 5.1.2.1:
`5.1.2
`Physical uplink control channel
`
`21
`
`Samsung Exhibit 1011, Page 21
`
`
`
`
`
`5.1.2.1 UE behaviour
` is a UE specific correction value, also referred to as a TPC
`•
`PUCCHδ
`command, included in a PDCCH with DCI format 1A/1B/1D/1/2A/2/2B/2C
`for the primary cell or sent jointly coded with other UE specific
`PUCCH correction values on a PDCCH with DCI format 3/3A whose CRC
`parity bits are scrambled with TPC-PUCCH-RNTI.
`o The UE attempts to decode a PDCCH of DCI format 3/3A with the
`UE’s TPC-PUCCH-RNTI and one or several PDCCHs of DCI format
`1A/1B/1D/1/2A/2/2B/2C with the UE’s C-RNTI or SPS C-RNTI on
`every subframe except when in DRX.
`o If the UE decodes a PDCCH with DCI format
`1A/1B/1D/1/2A/2/2B/2C for the primary cell and the
`corresponding detected RNTI equals the C-RNTI or SPS C-RNTI
`of the UE, the UE shall use the PUCCHδ
` provided in that PDCCH
`unless the TPC field in the DCI format is used to determine
`the PUCCH resource as in section 10.1.
`
`
`
`9. A user equipment,
`comprising:
`a receiving module,
`configured to receive
`downlink control
`
`Defendants’ Accused Products identified on Exhibit A are user equipment devices containing a receiving
`module, including the Accused Products’ application and baseband processors, RF front end, antennas,
`internal and external RAM, software, and firmware.
`
`Defendants’ Accused Products contain a receiving module that is configured to receive (and does receive)
`
`
`
`22
`
`Samsung Exhibit 1011, Page 22
`
`
`
`
`
`information (DCI) that
`is sent by a base
`station and transmitted
`by a downlink
`component carrier; and
`
`downlink control information (DCI) which is sent by a base station and transmitted by a downlink
`component carrier. More specifically, the Defendants’ Accused Products receive DCI from a base station
`on the physical downlink control channel (PDCCH), which is transmitted on a downlink component
`carrier.
`
`Defendants’ Accused Products are compliant with, for example, subsection 5.1 of the 3GPP TS 36.213
`v10.2.0 standard, which provides in relevant part as follows:
`
`3GPP TS 36.213 v10.2.0, Sec 7.1:
`7.1 UE procedure for receiving the physical downlink shared channel
`Except the subframes indicated by the higher layer parameter mbsfn-
`SubframeConfigList, a UE shall upon detection of a PDCCH of a serving
`cell with DCI format 1, 1A, 1B, 1C, 1D, 2, 2A, 2B or 2C intended for
`the UE in a subframe, decode the corresponding PDSCH in the same
`subframe with the restriction of the number of transport blocks defined
`in the higher layers.
`A UE may assume that positioning reference signals are not present in
`resource blocks in which it shall decode PDSCH according to a detected
`PDCCH with CRC scrambled by the SI-RNTI or P-RNTI with DCI format 1A or
`1C intended for the UE.
`[A UE is not expected to receive in a MBSFN subframe PDSCH and PRS with
`different CP sizes. A UE configured to decode PRS only in MBSFN
`subframes is not expected to decode other transmissions in those MBSFN
`
`
`
`23
`
`Samsung Exhibit 1011, Page 23
`
`
`
`
`
`
`
`subframes.]
`A UE configured with the carrier indicator
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
Still Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site
