Appendix 10 - U.S. Patent No. 8,885,587 · 2017. 5. 25. · By complying with the TS 36.213 and TS 36.300 standards, Defendants’ Accused Products infringe at least claims 3-5, 9-11

Huawei Technologies Co., et al. v. Samsung Electronics Co., et al. Case No. 3:16-cv-02787-WHO (N.D. Cal.)

1

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

feeding back

Acknowledgement /

Negative-

acknowledgement

(ACK/NACK)

information for

carrier aggregation,

the method

comprising:

Defendants’ Accused Products, including at least those identified on Exhibit A, operate on an LTE

network, support carrier aggregation, and feed back ACK/NACK information for carrier aggregation.

For example, the TS 36.213 v10.2.0 standard defines the characteristics of the physical layer procedures in

the FDD and TDD modes of E-UTRA, and 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:

10.1.2.2 FDD HARQ-ACK procedures for more than one configured serving

cell

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:

Samsung Exhibit 1011, Page 1

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




receiving downlink

control information

(DCI) which is sent

by a base station and

transmitted by a

downlink component

carrier; and

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


3

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

• PUCCHδ is a UE specific correction value, also referred to as a TPC

command, included in a PDCCH with DCI format 1A/1B/1D/1/2A/2/2B/2C

for the primary cell or sent jointly coded with other UE specific


4

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.

feeding back

ACK/NACK

information

according to a

command indicated

by a common field

preset in the DCI,

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:


5
















Defendants’ Accused Products are further compliant with, for example, subsection 10.1 of the TS 36.213


3GPP TS 36.213 v10.2.0, Sec 10.1.2.2:


cell


6





3GPP TS 36.213 v10.2.0, Sec 10.1.3.2:


cell





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 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


7

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


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.



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









8

carrier as an ARI

command.











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(PUCCH,in where 10 −≤≤ Ai

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

corresponding PDCCH in subframe 4−n on the primary cell, or for a


9

PDCCH indicating downlink SPS release (defined in section 9.2) in

subframe 4−n on the primary cell, the PUCCH resource is

(1)PUCCHiCCE,

)1(iPUCCH, Nnn += , and for transmission mode that support up to two

transport blocks, the PUCCH resource )1(1PUCCH, +in is given by

(1)PUCCHiCCE,

)1(1PUCCH, 1 Nnn i ++=+ where iCCE,n is the number of the first CCE used

for transmission of the corresponding PDCCH and (1)PUCCHN is configured

by higher layers.

- …


corresponding PDCCH in subframe 4−n on the secondary cell, the

value of )1(PUCCH,in , and the value of )1(

1PUCCH, +in for the transmission mode

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

Table 10.1.2.2.1-2 maps to two PUCCH resources ),( )1(1PUCCH,

)1(PUCCH, +ii nn ,

otherwise, the PUCCH resource value maps to a single PUCCH resource


10

)1(PUCCH,in .

…

10.1.2.2.2 PUCCH format 3 HARQ-ACK procedure

For FDD with PUCCH format 3, the UE shall use PUCCH resource ),3(PUCCH

pn or

),1(PUCCH

pn for transmission of HARQ-ACK in subframe n on antenna port p

where

- for a PDSCH transmission only on the primary cell indicated by the

detection of a corresponding PDCCH in subframe 4−n , or for a PDCCH

indicating downlink SPS release (defined in section 9.2) in

subframe 4−n on the primary cell, the UE shall use PUCCH format

1a/1b and PUCCH resource ),1(PUCCH

pn with (1)PUCCHCCE

),1(PUCCH

0 Nnn pp +== , where CCEn is

the number of the first CCE (i.e. lowest CCE index used to

construct the PDCCH) used for transmission of the corresponding

PDCCH and (1)PUCCHN is configured by higher layers. For two antenna

port transmission the PUCCH resource for 1pp = is given by

(1)PUCCHCCE

),1(PUCCH 11 Nnn pp ++== .

- …

- for a PDSCH transmission on the secondary cell indicated by the

detection of a corresponding PDCCH in subframe 4−n , the UE shall


11

use PUCCH format 3 and PUCCH resource ),3(PUCCH

pn with the value of ),3(PUCCH

pn

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

resource ),3(PUCCH

0ppn = for antenna port 0p and the second PUCCH resource

),3(PUCCH

1ppn = for antenna port 1p , otherwise, the PUCCH resource value

maps to a single PUCCH resource ),3(PUCCH

0ppn = for antenna port 0p . A UE

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:


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


12

10.1.3.1-1, the UE shall …


corresponding PDCCH within subframe(s) mkn − , where mk K∈ on the

primary cell, or for a PDCCH indicating downlink SPS release

(defined in section 9.2) within subframe(s) mkn − , where mk K∈ on

the primary cell, the PUCCH resource is

( ) (1)PUCCH,CCE1

(1),PUCCH 1 NnNmNmMn mcci ++⋅+⋅−−= + , …

- …


corresponding PDCCH within subframe(s) kn − , where Kk ∈ on the

secondary cell, the value of )1(PUCCH,in , and the value of )1(

1PUCCH, +in for a

subframe n with 2=M or for a subframe n with 1=M and a

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

subframe n with 1=M , or for a subframe n with 2=M , a PUCCH


13

resource value in Table 10.1.2.2.1-2 maps to two PUCCH resources

),( )1(1PUCCH,

)1(PUCCH, +ii nn , otherwise, the PUCCH resource value maps to a

single PUCCH resource )1(PUCCH,in . 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 cells in a given subframe.

-

…


selection and sub-frame n with 2>M and two configured serving cells,


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(PUCCH,0n is determined according to higher layer

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


14

‘1’ (defined in Table 7.3-X) or a PDCCH indicating downlink

SPS release (defined in section 9.2) within the subframe(s)


‘1’, the PUCCH resource ( )(1) (1)PUCCH,1 1 CCE, PUCCH1 c c mn M m N m N n N+= − − ⋅ + ⋅ + + …

o …

- Otherwise,




either ‘1’ or ‘2’ or a PDCCH indicating downlink SPS release

(defined in section 9.2) within the subframe(s) mkn − , where

mk K∈ with the DAI value in the PDCCH equal to either ‘1’ or

‘2’, the PUCCH resource ( ) (1)PUCCH,CCE1

(1),PUCCH 1 NnNmNmMn mcci ++⋅+⋅−−= + ,…

o …

For Secondary cell:


detection of a corresponding PDCCH on the primary cell within the

subframe(s) mn k− , where mk K∈ with the DAI value in the PDCCH

equal to either ‘1’ or ‘2’, the PUCCH resources

( ) (1)PUCCH,CCE1



15


corresponding PDCCH within the subframe(s) kn − , where Kk ∈ on the

secondary cell, the value of )1(2PUCCH,n and )1(

3PUCCH,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.

-

…


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

PUCCH resource ),3(PUCCH

pn or ),1(PUCCH

pn for transmission of HARQ-ACK in subframe

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 Kkm ∈ with the DAI value in the PDCCH equal to ‘1’ (defined in

Table 7.3-X), or for a PDCCH indicating downlink SPS release


16

(defined in section 9.2) within subframe(s) mkn − , where Kkm ∈ with

the DAI value in the PDCCH equal to ‘1’, the UE shall use PUCCH

format 1a/1b and PUCCH resource ),1(PUCCH

pn with

(1)PUCCHmCCE,1

),1(PUCCH )1(0 NnNmNmMn cc

pp ++⋅+⋅−−= += for antenna port 0pp = ,…

- - for 1>M and a PDSCH transmission only on the primary cell

where there is not a corresponding PDCCH detected within

subframe(s) mkn − , where Kkm ∈ and an additional PDSCH transmission

only on the primary cell indicated by the detection of a

corresponding PDCCH within subframe(s) mkn − , where Kkm ∈ with the

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 Kkm ∈ with the DAI value in the

PDCCH equal to ‘1’, the UE shall transmit ( ) ( )0 , 1b b in subframe n

using PUCCH format 1b on PUCCH resource (1)PUCCHn selected from A PUCCH

resources (1)PUCCH,in where 0 1i A≤ ≤ − , according to Table 10.1.3.2-1 and

Table 10.1.3.2-2 for 2=A and 3=A , respectively. For a UE

configured with a transmission mode that supports up to two

transport blocks on the primary cell, 3=A ; otherwise, 2=A .

o The PUCCH resource )1(PUCCH,0n is determined according to higher

layer configuration and Table 9.2-2. The PUCCH resource )1(PUCCH,1n


17

is determined as (1) (1)PUCCH,1 1 CCE, PUCCH( 1) c c mn M m N m N n N+= − − ⋅ + ⋅ + + , where

(1)PUCCHN is configured by higher layers,…

…


detection of a corresponding PDCCH within subframe(s) mkn − , where

Kkm ∈ , the UE shall use PUCCH format 3 and PUCCH resource ),3(PUCCH

pn

where the value of ),3(PUCCH

pn is determined according to higher layer

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 Kkm ∈ , or a PDCCH indicating downlink SPS release

(defined in section 9.2) within subframe(s) mkn − , where Kkm ∈ , is

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)


18

mkn − , where Kkm ∈ .

. . .

Defendants’ Accused Products are compliant with, for example, subsection 7.5 of the 3GPP TS 36.300


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:


19

- 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.



3GPP TS 36.213 v10.2.0, Sec 10.1:

10.1 UE procedure for determining physical uplink control channel assignment

…


20

A UE transmits PUCCH only on the primary cell.

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.

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.



3GPP TS 36.213 v10.2.0, Sec 5.1.2.1:









21











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


downlink primary

component carrier.

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.



3GPP TS 36.213 v10.2.0, Sec 5.1.2.1:



22

















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)


23

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.



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


24

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:












25







a feedback module,

configured to feed-

back

Acknowledgement/Ne

gative-

acknowledgement

(ACK/NACK)

feedback information

according to a

command indicated by

a common field preset

in the DCI,

Defendants’ Accused Products identified on Exhibit A are user equipment devices containing a feedback

module, including the Accused Products’ application and baseband processors, RF front end, antennas,

internal and external RAM, software, and firmware. This feedback module that is configured to 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, subsections 5.1 and 7.1 of the 3GPP TS

36.213 v10.2.0 standard, which provide in relevant part as follows:

3GPP TS 36.213 v10.2.0, Sec 5.1.2.1:




26















Defendants’ Accused Products are further compliant with, for example, subsection 10.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 10.1.2.2:


cell




27



3GPP TS 36.213 v10.2.0 Sec 10.1.3.2:


cell





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 a transmission

power control (TPC)

command and an ACK

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

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


28

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


transmitted by a non-

system-linked

downlink component

carrier as an ARI

command.

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.



3GPP TS 36.213 v10.2.0, Sec 5.1.2.1:













29









3GPP TS 36.213 v10.2.0, Sec 10.1.2.2.1:


procedure

For FDD with two configured serving cells and PUCCH format 1b with

channel selection…

The UE shall determine the A PUCCH resources, )1(PUCCH,in where 10 −≤≤ Ai

ordered according to the serving cell in increasing order of j given in

Table 10.1.2.2.1-1, according to


corresponding PDCCH in subframe 4−n on the primary cell, or for a

PDCCH indicating downlink SPS release (defined in section 9.2) in


30

subframe 4−n on the primary cell, the PUCCH resource is

(1)PUCCHiCCE,

)1(iPUCCH, Nnn += , and for transmission mode that support up to two

transport blocks, the PUCCH resource )1(1PUCCH, +in is given by

(1)PUCCHiCCE,

)1(1PUCCH, 1 Nnn i ++=+ where iCCE,n is the number of the first CCE used

for transmission of the corresponding PDCCH and (1)PUCCHN is configured

by higher layers.

- …


corresponding PDCCH in subframe 4−n on the secondary cell, the

value of )1(PUCCH,in , and the value of )1(

1PUCCH, +in for the transmission mode

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

Table 10.1.2.2.1-2 maps to two PUCCH resources ),( )1(1PUCCH,

)1(PUCCH, +ii nn ,

otherwise, the PUCCH resource value maps to a single PUCCH resource

)1(PUCCH,in .


31

…


For FDD with PUCCH format 3, the UE shall use PUCCH resource ),3(PUCCH

pn or

),1(PUCCH

pn for transmission of HARQ-ACK in subframe n on antenna port p

where

- for a PDSCH transmission only on the primary cell indicated by the

detection of a corresponding PDCCH in subframe 4−n , or for a PDCCH

indicating downlink SPS release (defined in section 9.2) in

subframe 4−n on the primary cell, the UE shall use PUCCH format

1a/1b and PUCCH resource ),1(PUCCH

pn with (1)PUCCHCCE

),1(PUCCH

0 Nnn pp +== , where CCEn is

the number of the first CCE (i.e. lowest CCE index used to

construct the PDCCH) used for transmission of the corresponding

PDCCH and (1)PUCCHN is configured by higher layers. For two antenna

port transmission the PUCCH resource for 1pp = is given by

(1)PUCCHCCE

),1(PUCCH 11 Nnn pp ++== .

- …


detection of a corresponding PDCCH in subframe 4−n , the UE shall

use PUCCH format 3 and PUCCH resource ),3(PUCCH

pn with the value of ),3(PUCCH

pn


32

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

resource ),3(PUCCH

0ppn = for antenna port 0p and the second PUCCH resource

),3(PUCCH

1ppn = for antenna port 1p , otherwise, the PUCCH resource value

maps to a single PUCCH resource ),3(PUCCH

0ppn = for antenna port 0p . A UE

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:


procedure


selection and two configured serving cells and a subframe n with 2≤M


10.1.3.1-1, the UE shall …


33


corresponding PDCCH within subframe(s) mkn − , where mk K∈ on the

primary cell, or for a PDCCH indicating downlink SPS release

(defined in section 9.2) within subframe(s) mkn − , where mk K∈ on

the primary cell, the PUCCH resource is

( ) (1)PUCCH,CCE1


- …


corresponding PDCCH within subframe(s) kn − , where Kk ∈ on the

secondary cell, the value of )1(PUCCH,in , and the value of )1(

1PUCCH, +in for a

subframe n with 2=M or for a subframe n with 1=M and a

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

subframe n with 1=M , or for a subframe n with 2=M , a PUCCH

resource value in Table 10.1.2.2.1-2 maps to two PUCCH resources


34

),( )1(1PUCCH,

)1(PUCCH, +ii nn , otherwise, the PUCCH resource value maps to a

single PUCCH resource )1(PUCCH,in . 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 cells in a given subframe.

-

…


selection and sub-frame n with 2>M and two configured serving cells,


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(PUCCH,0n is determined according to higher layer

configuration and Table 9.2-2.




‘1’ (defined in Table 7.3-X) or a PDCCH indicating downlink


35

SPS release (defined in section 9.2) within the subframe(s)


‘1’, the PUCCH resource ( )(1) (1)PUCCH,1 1 CCE, PUCCH1 c c mn M m N m N n N+= − − ⋅ + ⋅ + + …

o …

- Otherwise,




either ‘1’ or ‘2’ or a PDCCH indicating downlink SPS release

(defined in section 9.2) within the subframe(s) mkn − , where

mk K∈ with the DAI value in the PDCCH equal to either ‘1’ or

‘2’, the PUCCH resource ( ) (1)PUCCH,CCE1

(1),PUCCH 1 NnNmNmMn mcci ++⋅+⋅−−= + ,…

o …

For Secondary cell:


detection of a corresponding PDCCH on the primary cell within the

subframe(s) mn k− , where mk K∈ with the DAI value in the PDCCH

equal to either ‘1’ or ‘2’, the PUCCH resources

( ) (1)PUCCH,CCE1




36

corresponding PDCCH within the subframe(s) kn − , where Kk ∈ on the

secondary cell, the value of )1(2PUCCH,n and )1(

3PUCCH,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.

-

…


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

PUCCH resource ),3(PUCCH

pn or ),1(PUCCH

pn for transmission of HARQ-ACK in subframe

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 Kkm ∈ with the DAI value in the PDCCH equal to ‘1’ (defined in

Table 7.3-X), or for a PDCCH indicating downlink SPS release


37

(defined in section 9.2) within subframe(s) mkn − , where Kkm ∈ with

the DAI value in the PDCCH equal to ‘1’, the UE shall use PUCCH

format 1a/1b and PUCCH resource ),1(PUCCH

pn with

(1)PUCCHmCCE,1

),1(PUCCH )1(0 NnNmNmMn cc

pp ++⋅+⋅−−= += for antenna port 0pp = ,…

- - for 1>M and a PDSCH transmission only on the primary cell

where there is not a corresponding PDCCH detected within

subframe(s) mkn − , where Kkm ∈ and an additional PDSCH transmission

only on the primary cell indicated by the detection of a

corresponding PDCCH within subframe(s) mkn − , where Kkm ∈ with the

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 Kkm ∈ with the DAI value in the

PDCCH equal to ‘1’, the UE shall transmit ( ) ( )0 , 1b b in subframe n

using PUCCH format 1b on PUCCH resource (1)PUCCHn selected from A PUCCH

resources (1)PUCCH,in where 0 1i A≤ ≤ − , according to Table 10.1.3.2-1 and

Table 10.1.3.2-2 for 2=A and 3=A , respectively. For a UE

configured with a transmission mode that supports up to two

transport blocks on the primary cell, 3=A ; otherwise, 2=A .

o The PUCCH resource )1(PUCCH,0n is determined according to higher

layer configuration and Table 9.2-2. The PUCCH resource )1(PUCCH,1n


38

is determined as (1) (1)PUCCH,1 1 CCE, PUCCH( 1) c c mn M m N m N n N+= − − ⋅ + ⋅ + + , where

(1)PUCCHN is configured by higher layers,…

…


detection of a corresponding PDCCH within subframe(s) mkn − , where

Kkm ∈ , the UE shall use PUCCH format 3 and PUCCH resource ),3(PUCCH

pn

where the value of ),3(PUCCH

pn is determined according to higher layer

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 Kkm ∈ , or a PDCCH indicating downlink SPS release

(defined in section 9.2) within subframe(s) mkn − , where Kkm ∈ , is

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)


39

mkn − , where Kkm ∈ .

. . .



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:


40

- 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.



3GPP TS 36.213 v10.2.0, Sec 10.1:

…

A UE transmits PUCCH only on the primary cell.


41

10. The user

equipment according

to claim 9, wherein the

at least one piece of


system-linked

downlink component

carrier comprises DCI

corresponding to

physical downlink

shared channel

(PDSCH) transmission

of a downlink primary

component carrier.

The Defendant’s Accused Products infringe claim 9 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 9, 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 10.1.2.2 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:












42








11. The user

equipment according

to claim 9, wherein the

at least one piece of


system-linked

downlink component

carrier comprises at


transmitted by a

downlink primary

component carrier.

The Defendant’s Accused Products infringe claim 9 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.

3GPP TS 36.213 v10.2.0, Sec 5.1.2.1:









43












Documents

Appendix 10 - U.S. Patent No. 8,885,587 · 2017. 5. 25. · By complying with the TS 36.213 and TS 36.300 standards, Defendants’ Accused Products infringe at least claims 3-5, 9-11