`
`Filed on behalf of Nokia of America Corporation
`By: David A. Nelson
`
`Stephen A. Swedlow
`
`Brianne M. Straka
`
`John P. Poulos
`
`QUINN EMANUEL URQUHART & SULLIVAN LLP
`
`191 N Wacker Drive Suite 2700
`
`Chicago, Illinois 60606
`
`Telephone: (312) 705-7400
`
`Fax: (312) 705-7401
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`_____________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`_____________________
`
`NOKIA OF AMERICA CORPORATION
`Petitioner
`
`v.
`
`INTELLECTUAL VENTURES II LLC
`Patent Owner
`
`_____________________
`
`PETITION FOR INTER PARTES REVIEW
`OF U.S. PATENT NO. 8,897,828
`
`
`
`
`Mail Stop PATENT BOARD
`Patent Trial and Appeal Board
`U.S. Patent & Trademark Office
`P.O. Box 1450
`Alexandra, VA 22313-1450
`
`
`
`
`

`

`
`
`TABLE OF CONTENTS
`
`Page
`
`I.
`
`Introduction ...................................................................................................... 1
`
`II. Mandatory Notices (37 C.F.R. § 42.8(a)(1)) ................................................... 3
`
`III. Grounds for Standing (37 C.F.R. § 42.104(a)) ................................................ 4
`
`IV.
`
`Identification of Challenge (37 C.F.R. § 42.104(b)) ....................................... 4
`
`A.
`
`B.
`
`Citation of Prior Art .............................................................................. 4
`
`Statutory Grounds for the Challenge ..................................................... 5
`
`V.
`
`The ’828 Patent ................................................................................................ 6
`
`A. Overview of the ’828 Patent .................................................................. 6
`
`B.
`
`C.
`
`D.
`
`Summary of Prosecution History ........................................................ 11
`
`Level of Ordinary Skill in the Art ....................................................... 15
`
`Claim Construction.............................................................................. 15
`
`VI. Overview of the Applied References ............................................................ 16
`
`A.
`
`Zeira 292 .............................................................................................. 17
`
`B. Whinnett .............................................................................................. 22
`
`C.
`
`D.
`
`R1-99151 ............................................................................................. 24
`
`Public Availability of 3GPP References Cited ................................... 27
`
`VII. Overview of the Grounds .............................................................................. 28
`
`VIII. Ground 1: Zeira 292 in combination with Whinnett renders claims 1,
`5-6, 8, 12-13, 15, 19-20, 22, 26-27, 29, 33-34, 36, and 40-41 obvious. ....... 29
`
`A.
`
`Claim 1 ................................................................................................ 29
`
`1.
`
`2.
`
`3.
`
`4.
`
`“A method performed by user equipment (UE), the
`method comprising:” [1.P] ........................................................ 29
`
`“receiving, by the UE, an indication of whether
`accumulation of transmit power control (TPC)
`commands is enabled;” [1.1] ..................................................... 29
`
`“determining, by the UE, a path loss of a downlink
`channel;” [1.2] ........................................................................... 32
`
`“receiving, on a single physical channel by the UE if
`accumulation is enabled, an allocation of a scheduled
`
`
`
`i
`
`

`

`
`
`
`
`5.
`
`6.
`
`uplink resource and a TPC command, wherein the TPC
`command is accumulated with other received TPC
`commands;” [1.3] ...................................................................... 33
`
`“calculating, by the UE if accumulation is enabled,
`transmit power in association with an uplink
`communication based on both the path loss and the
`accumulated TPC commands; and” [1.4] ................................. 38
`
`“receiving, on the single physical channel by the UE if
`accumulation is not enabled, an allocation of a scheduled
`uplink resource to transmit data at a power level
`calculated by the UE based on the path loss.” [1.5] ................ 39
`
`B.
`
`C.
`
`D.
`
`Claim 5 ................................................................................................ 42
`
`Claim 6 ................................................................................................ 43
`
`Claim 8 ................................................................................................ 44
`
`1.
`
`2.
`
`3.
`
`4.
`
`5.
`
`6.
`
`“A user equipment (UE) characterized in that:” [8.P] .............. 44
`
`“circuitry is configured to receive, by the UE, an
`indication of whether accumulation of transmit power
`control (TPC) commands is enabled;” [8.1] ............................. 44
`
`“circuitry is configured to determine a path loss of a
`downlink channel;” [8.2] .......................................................... 44
`
`“the circuitry is further configured to receive, on a single
`physical channel if accumulation is enabled, an allocation
`of a scheduled uplink resource and a TPC command,
`wherein the TPC command is accumulated with other
`received TPC commands;” [8.3] ............................................... 44
`
`“circuitry is configured to calculate, by the UE if
`accumulation is enabled, transmit power in association
`with an uplink communication based on both the path
`loss and the accumulated TPC commands; and” [8.4] ............. 45
`
`“the circuitry is further configured to receive, on the
`single physical channel by the UE if accumulation is not
`enabled, an allocation of a scheduled uplink resource to
`transmit data at a power level calculated by the UE based
`on the path loss.” [8.5] .............................................................. 45
`
`E.
`
`Claim 12 .............................................................................................. 45
`
`ii
`
`

`

`
`
`
`
`F.
`
`G.
`
`Claim 13 .............................................................................................. 45
`
`Claim 15 .............................................................................................. 46
`
`1.
`
`2.
`
`3.
`
`4.
`
`5.
`
`6.
`
`“A method performed by a wireless network, the method
`comprising:” [15.P] ................................................................... 46
`
`“sending, by the wireless network, an indication of
`whether accumulation of transmit power control (TPC)
`commands is enabled;” [15.1] ................................................... 46
`
`“determining, by a user equipment (UE), a path loss of a
`downlink channel;” [15.2] ........................................................ 46
`
`“receiving, on a single physical channel by the UE if
`accumulation is enabled, an allocation of a scheduled
`uplink resource and a TPC command, wherein the TPC
`command is accumulated with other received TPC
`commands;” [15.3] .................................................................... 46
`
`“calculating, by the UE if accumulation is enabled,
`transmit power in association with an uplink
`communication based on both the path loss and the
`accumulated TPC commands; and” [15.4] ............................... 46
`
`“receiving, on the single physical channel by the UE if
`accumulation is not enabled, an allocation of a scheduled
`uplink resource to transmit data to the wireless network
`at a power level calculated by the UE based on the path
`loss.” [15.5] ............................................................................... 46
`
`H.
`
`Claim 19 .............................................................................................. 47
`
`I.
`
`J.
`
`Claim 20 .............................................................................................. 47
`
`Claim 22 .............................................................................................. 47
`
`1.
`
`2.
`
`3.
`
`4.
`
`“A wireless network characterized in that:” [22.P] .................. 47
`
`the wireless network is configured to send an indication
`of whether accumulation of transmit power control (TPC)
`commands is enabled;” [22.1] ................................................... 47
`
`“a user equipment (UE) characterized in that:” [22.2] ............. 47
`
`“circuitry is configured to determine, by the UE, a path
`loss of a downlink channel;” [22.3] .......................................... 48
`
`iii
`
`

`

`
`
`
`
`5.
`
`6.
`
`7.
`
`“circuitry is configured to receive, on a single physical
`channel if accumulation is enabled, an allocation of a
`scheduled uplink resource and a TPC command, wherein
`the TPC command is accumulated with other received
`TPC commands;” [22.4] ........................................................... 48
`
`“circuitry is configured to calculate, by the UE if
`accumulation is enabled, transmit power in association
`with an uplink communication based on both the path
`loss and the accumulated TPC commands; and” [22.5] ........... 48
`
`“the circuitry is further configured to receive, on the
`single physical channel by the UE if accumulation is not
`enabled, an allocation of a scheduled uplink resource to
`transmit data to the wireless network at a power level
`calculated by the UE based on the path loss.” [22.6] ............... 48
`
`K.
`
`L.
`
`Claim 26 .............................................................................................. 48
`
`Claim 27 .............................................................................................. 49
`
`M. Claim 29 .............................................................................................. 49
`
`1.
`
`2.
`
`3.
`
`4.
`
`5.
`
`“A method performed by a network device, the method
`comprising:” [29.P] ................................................................... 49
`
`“sending, by the network device, an indication of
`whether accumulation of transmit power control (TPC)
`commands is enabled;” [29.1] ................................................... 49
`
`“sending, on a single physical channel by the network
`device if accumulation is enabled, an allocation of a
`scheduled uplink resource and a TPC command to be
`accumulated with other received TPC commands at a
`user equipment (UE);” [29.2] ................................................... 49
`
`“receiving, by the network device if accumulation is
`enabled, uplink communication at a transmit power,
`wherein the transmit power is calculated at the UE based
`on both a determined path loss of a downlink channel and
`the accumulated TPC commands; and” [29.3] ......................... 49
`
`“sending, on the single physical channel to the UE if
`accumulation is not enabled, an allocation of a scheduled
`uplink resource to transmit data to the network device at
`
`iv
`
`

`

`
`
`a power level calculated at the UE based on the path
`loss.” [29.4] ............................................................................... 49
`
`N.
`
`O.
`
`P.
`
`Claim 33 .............................................................................................. 50
`
`Claim 34 .............................................................................................. 50
`
`Claim 36 .............................................................................................. 50
`
`1.
`
`2.
`
`3.
`
`4.
`
`5.
`
`“A network device characterized in that:” [36.P] ..................... 50
`
`“circuitry is configured to send, by the network device,
`an indication of whether accumulation of transmit power
`control (TPC) commands is enabled;” [36.1] ........................... 50
`
`“the circuitry is further configured to send, on a single
`physical channel if accumulation is enabled, an allocation
`of a scheduled uplink resource and a TPC command to be
`accumulated with other received TPC commands at a
`user equipment (UE);” [36.2] ................................................... 50
`
`“circuitry is configured to receive, if accumulation is
`enabled, uplink communication at a transmit power,
`wherein the transmit power is calculated at the UE based
`on both a determined path loss of a downlink channel and
`the accumulated TPC commands; and” [36.3] ......................... 51
`
`“the circuitry is further configured to send, on the single
`physical channel if accumulation is not enabled, an
`allocation of a scheduled uplink resource to transmit data
`to the network device at a power level calculated at the
`UE based on the path loss.” [36.4] ............................................ 51
`
`Q.
`
`R.
`
`Claim 40 .............................................................................................. 51
`
`Claim 41 .............................................................................................. 52
`
`S. Motivation to Combine Zeira 292 and Whinnett ................................ 52
`
`IX. Ground 2: Zeira 292 in combination with Whinnett and R1-99151
`renders claims 2, 9, 16, 23, 30, and 37 obvious. ........................................... 55
`
`A.
`
`B.
`
`C.
`
`D.
`
`Claim 2 ................................................................................................ 55
`
`Claim 9 ................................................................................................ 56
`
`Claim 16 .............................................................................................. 57
`
`Claim 23 .............................................................................................. 57
`
`
`
`v
`
`

`

`
`
`X.
`
`
`
`E.
`
`F.
`
`Claim 30 .............................................................................................. 57
`
`Claim 37 .............................................................................................. 57
`
`G. Motivation to Combine Zeira 292, Whinnett, and R1-99151 ............. 57
`
`Conclusion ..................................................................................................... 60
`
`
`
`
`
`vi
`
`

`

`
`
`TABLE OF AUTHORITIES
`
`CASES
`
`Page
`
`Cuozzo Speed Techs., LLC v. Lee,
`136 S. Ct. 2131, 2142 (2016) .................................................................. 15, 16
`
`Ex parte Schulhauser,
`No. 2013-007847, 2016 WL 6277792 (PTAB Apr. 28, 2016) ........ 14, 15, 16
`
`LG Elecs. v. Core Wireless Licensing S.A.R.L.,
`IPR2015-01988, Paper 7, at 12-14 (PTAB Apr. 1, 2016) .............................28
`
`Nuvasive v. Warsaw Orthopedic, Inc.,
`IPR2013- 00206, Paper No. 17 at 6 (PTAB Sept. 23, 2013) ........................15
`
`
`
`STATUTORY AUTHORITIES
`
`35 U.S.C. § 102(a) ..................................................................................................... 5
`
`35 U.S.C. § 102(b) ..................................................................................................... 5
`
`35 U.S.C. § 102(e) ..................................................................................................... 5
`
`35 U.S.C. § 112 ........................................................................................................43
`
`RULES AND REGULATIONS
`
`37 C.F.R. § 42.6(e) ...................................................................................................60
`
`37 C.F.R. § 42.8(a)(1) ................................................................................................ 3
`
`37 C.F.R. § 42.8(b)(3) ................................................................................................ 3
`
`37 C.F.R. § 42.8(b)(3) ................................................................................................ 3
`
`37 C.F.R. § 42.10(a) ................................................................................................... 3
`
`37 C.F.R. § 42.24(a)(i) .............................................................................................59
`
`37 C.F.R. § 42.100(b) ..............................................................................................15
`
`37 C.F.R. § 42.104(a) ................................................................................................. 4
`
`37 C.F.R. § 42.104(b) ..........................................................................................4, 28
`
`37 C.F.R. § 42.105(a) ............................................................................................... 60
`
`
`
`vii
`
`

`

`
`
`
`
`EXHIBIT LIST
`
`Exhibit No.
`
`Description
`
`1001
`
`1002
`
`1003
`1004
`1005
`
`1006
`
`1007
`
`1008
`
`1009
`
`1010
`
`1011
`
`1012
`
`U.S. Patent No. 8,897,828 to Anderson, issued November 25, 2014
`U.S. Patent No. 8,897,828 to Anderson, File History (mail room
`date earliest to latest)
`Declaration of Paul S. Min, Ph.D.
`Curriculum Vitae of Paul S. Min, Ph.D.
`U.S. Patent No. 6,728,292 to Zeira et al. issued April 27, 2004
`U.S. Patent Application Publication No. 2004/0219919 to
`Whinnett et al. published November 4, 2004
`3GPP TSG RAN WG1#3 TDoc R1-99151, “Adaptive Step Power
`Control (ASPC)” by Panasonic (Matsushita Communication
`Industrial Co., Ltd.), available at
`http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_03/Docs/zip
`s/R1-99151.zip (uploaded 3/24/1999 at 6:21 PM)
`“UMTS Networks Architecture, Mobility and Services,”
`published in 2001 by John Wiley & Sons, Ltd. (“UMTS
`Textbook”)
`3GPP TSG RAN WG1 Ad Hoc TDoc R1-040665, “Draft
`Agenda” by RAN WG1 Chairman, available at
`http://www.3gpp.org/ftp/tsg_ran/wg1_rl1/TSGR1_AH/Rel-
`6_AH_0406/Docs/ZIPs/R1-040665.zip (uploaded 6/15/2004 at
`10:08 AM)
`3GPP TSG RAN WG1 Ad Hoc TDoc R1-040705, “Scheduling
`Schemes for EDCH” by Lucent, available at
`http://www.3gpp.org/ftp/tsg_ran/wg1_rl1/TSGR1_AH/Rel-
`6_AH_0406/Docs/ZIPs/R1-040705.zip (uploaded at 6/18/2004 at
`3:10 PM)
`3GPP TSG RAN WG1 Ad Hoc TDoc R1-040706, “SHO Support
`for E-DCH” by Lucent, available at
`http://www.3gpp.org/ftp/tsg_ran/wg1_rl1/TSGR1_AH/Rel-
`6_AH_0406/Docs/ZIPs/R1-040706.zip (uploaded at 6/18/2004 at
`3:10 PM)
`3GPP TSG RAN WG1 Ad Hoc TDoc R1-040739, “Per-Cell, Per-
`UE, Per-MAC-d Flow basis Scheduling Signaling in Enhanced
`
`viii
`
`

`

`
`
`
`
`Exhibit No.
`
`Description
`
`Uplink” by NEC, available at
`http://www.3gpp.org/ftp/tsg_ran/wg1_rl1/TSGR1_AH/Rel-
`6_AH_0406/Docs/ZIPs/R1-040739.zip (uploaded 6/18/2004 at
`2:42 AM)
`3GPP TSG RAN WG1 Ad Hoc TDoc R1-040746, “Requirements
`for UL Signalling” by Nokia, available at
`http://www.3gpp.org/ftp/tsg_ran/wg1_rl1/TSGR1_AH/Rel-
`6_AH_0406/Docs/ZIPs/R1-040746.zip (uploaded 6/18/2004 at
`8:27 AM)
`3GPP TR25.804 V0.2.1 (2004-05), 3rd Generation Partnership
`Project; Technical Specification Group Radio Access Network;
`Feasibility Study on Uplink Enhancements for UTRA TDD;
`(Release 6), available at
`http://www.3gpp.org/ftp/specs/archive/25_series/25.804/25804-
`021.zip (uploaded 7/23/2004 at 12:29 PM)
`3GPP TR 25.896 V6.0.0 (2004-03), 3rd Generation Partnership
`Project; Technical Specification Group Radio Access Network;
`Feasibility Study for Enhanced Uplink for UTRA FDD (Release
`6), available at
`http://www.3gpp.org/ftp/specs/archive/25_series/25.896/25896-
`600.zip (uploaded 4/3/2004 at 7:39 AM)
`3GPP TR 21.900 V6.2 (2004-06), 3rd Generation Partnership
`Project; Technical Specification Group Services and System
`Aspects; Technical Specification Group working methods
`(Release 6), available at
`http://www.3gpp.org/ftp/Specs/archive/21_series/21.900/21900-
`620.zip (uploaded 6/23/2004 at 2:12 PM)
`R1-99151 Page, available at
`http://www.3gpp.org/ftp/tsg_ran/wg1_rl1/TSGR1_03/Docs/zips/
`25.302 Specs Listing, available at
`http://www.3gpp.org/FTP/Specs/archive/25_series/25.302/
`25.302 Page, available at
`http://www.3gpp.org/DynaReport/25302.htm
`
`1013
`
`1014
`
`1015
`
`1016
`
`1017
`
`1018
`
`1019
`
`ix
`
`

`

`
`
`
`
`Exhibit No.
`
`Description
`
`1020
`
`1021
`
`1022
`
`1023
`
`1024
`
`1025
`
`1026
`
`1027
`
`1028
`
`1029 - 1050
`
`1051
`
`25.302 Archived Page, available at
`https://web.archive.org/web/20040417184449/http://www.3gpp.o
`rg:80/ftp/Specs/html-info/25302.htm
`25.221 Specs Listing, available at
`http://www.3gpp.org/ftp/Specs/archive/25_series/25.221/
`25.221 Page, available at
`http://www.3gpp.org/DynaReport/25221.htm
`25.221 Archived Page, available at
`https://web.archive.org/web/20040623014016/http://www.3gpp.o
`rg:80/ftp/Specs/html-info/25221.htm
`25.211 Spec Listing, available at
`http://www.3gpp.org/ftp/Specs/archive/25_series/25.211/
`25.211 Page, available at
`http://www.3gpp.org/DynaReport/25211.htm
`25.211 Archived Page, available at
`https://web.archive.org/web/20040624005951/http://www.3gpp.o
`rg:80/ftp/Specs/html-info/25211.htm
`3GPP TS 25.224 V6.0.0 (2003-12), 3rd Generation Partnership
`Project; Technical Specification Group Radio Access Network;
`Physical layer procedures (TDD) (Release 6), available at
`http://www.3gpp.org/ftp/Specs/archive/25_series/25.224/25224-
`600.zip (uploaded 1/13/2004 at 1:19 PM)
`3GPP TS 25.225 V6.0.0 (2003-12), 3rd Generation Partnership
`Project; Technical Specification Group Radio Access Network;
`Physical layer – Measurements (TDD) (Release 6), available at
`http://www.3gpp.org/ftp/Specs/archive/25_series/25.225/25225-
`600.zip (uploaded 1/13/2004 at 1:15 PM)
`Intentionally Left Blank
`3GPP TS 25.302 V6.1.0 (2004-03), 3rd Generation Partnership
`Project; Technical Specification Group Radio Access Network;
`Services provided by the physical layer (Release 6), available at
`http://www.3gpp.org/ftp/Specs/archive/25_series/25.302/25302-
`610.zip (uploaded 3/23/2004 at 4:59 PM)
`
`x
`
`

`

`
`
`
`
`
`
`Exhibit No.
`
`Description
`
`1052
`
`1053
`
`1054
`
`1055
`
`1056
`
`1057
`
`1058
`
`3GPP TS 25.221 V6.1.0 (2004-06), 3rd Generation Partnership
`Project; Technical Specification Group Radio Access Network;
`Physical channels and mapping of transport channels onto
`physical channels (TDD) (Release 6), available at
`http://www.3gpp.org/ftp/Specs/archive/25_series/25.221/25221-
`610.zip (uploaded 6/17/2004 at 12:11 PM)
`3GPP TS 25.211 V6.1.0 (2004-06), 3rd Generation Partnership
`Project; Technical Specification Group Radio Access Network;
`Physical channels and mapping of transport channels onto
`physical channels (FDD) (Release 6)
`http://www.3gpp.org/ftp/Specs/archive/25_series/25.211/25211-
`610.zip (uploaded 6/17/2004 at 11:31 AM)
`3GPP FAQs, 3GPP: A Global Initiative, available at
`http://www.3gpp.org/contact/3gpp-faqs (last accessed 7/2/2018)
`Delegates Corner, 3GPP: A Global Initiative, available at
`http://www.3gpp.org/specifications-groups/delegates-corner (last
`accessed 7/2/2018)
`3GPP TSG RAN WG1 #28 TDoc R1-02-1166, “Comments on
`Proposals to Restrict the OFDM Study Item to FDD Only” by
`IPWireless, available at
`http://www.3gpp.org/ftp/tsg_ran/wg1_rl1/TSGR1_28/Docs/Zips/
`R1-02-1166.zip (uploaded 8/26/2002 at 8:33 PM)
`3GPP TSG RAN WG1 Meeting #35 TDoc R1-031163, “[DRAFT
`r1] Report of 3GPP TSG RAN WG1 #33 (New York, NY, USA,
`25 – 29 August, 2003)” by WG1 Secretary, available at
`http://www.3gpp.org/ftp/tsg_ran/wg1_rl1/TSGR1_35/Docs/Zips/
`R1-031163.zip (uploaded 11/19/2003 at 9:46 AM)
`3GPP TSG RAN Meeting #23 TDoc RP-040130, “Proposed
`Work Item on Optimisation of Channelisation Code Utilisation
`for TDD” by IPWireless, available at
`http://www.3gpp.org/ftp/tsg_ran/tsg_ran/tsgr_23/docs/ZIP/RP-
`040130.zip (uploaded 3/11/2004 at 9:55 PM)
`
`xi
`
`

`

`
`
`
`
`ACRONYM GLOSSARY
`
`Acronym
`
`Term
`
`3GPP
`
`3rd Generation Partnership Project
`
`UMTS
`
`Universal Mobile Telecommunications Service
`
`W-CDMA Wideband Code Division Multiple Access
`
`Node B
`
`Base Station
`
`UE
`
`User Equipment / Mobile Station
`
`UTRA
`
`Universal Terrestrial Radio Access
`
`xii
`
`

`

`
`
`I.
`
`Introduction
`
`Nokia of America Corporation (“Nokia”) petitions for inter partes review of
`
`claims 1-2, 5-6, 8-9, 12-13, 15-16, 19-20, 22-23, 26-27, 29-30, 33-34, 36-37, 40-41
`
`of U.S. Patent No. 8,897,828 to Anderson (“the ʼ828 patent”). Nokia demonstrates
`
`in this petition that a reasonable likelihood exists that all claims of the ’828 patent
`
`are unpatentable.
`
`The ’828 patent should never have been granted. As of the ’828 patent’s
`
`priority date, one of ordinary skill in the art would have recognized the features in
`
`the ’828 patent’s claims—namely, a combination of open loop and closed loop
`
`power control—were already known in the prior art. (Min Decl., NAC1003, ¶¶76-
`
`98; 172-196.) Any differences between the prior art and the ’828 patent claims are
`
`not patentably significant and would have been obvious to a person of ordinary skill
`
`in the art.
`
`The specification and the original claims of the application that led to the ’828
`
`patent were directed to a combination of open loop and closed loop power control.
`
`(’828 File History, NAC1002 at 1-29.) This system and method although were
`
`already known in the prior art, and the claims were rejected in light of WO 00/57574
`
`(“Zeira 574”). (Id. at 344-353.) In response, the Applicant added trivial limitations
`
`to the claims related to how transmit power control (“TPC”) commands and
`
`scheduling allocations are communicated from the base station to the UE. First, the
`
`
`
`1
`
`

`

`
`
`Applicant amended the claims to add a downlink channel to carry an allocation of a
`
`scheduled uplink resource in addition to the TPC commands. (Id. at 412-428.)
`
`These claims although were rejected by Zeira 574 in view of U.S. Publication No.
`
`2005/0025056 (“Chen”) (Id. at 455-474.) Next, the Applicant amended the claims
`
`to include a shared channel. (Id. at 483-494.) These claims were finally rejected by
`
`Zeira 574, Chen, and U.S. Publication No. 2001/0036823 (“Van Lieshout”). (Id. at
`
`568-594.) The Applicant appealed and the rejection was affirmed (Id. at 971-978.)
`
`In response, the Applicant canceled all of the pending claims and added new claims.
`
`(Id. at 988-998.) These claims, which were allowed after 10 years of prosecution,
`
`differed from the previous claims in two respects (1) the Applicant amended the
`
`claimed “shared channel” to a “single physical channel” and (2) the Applicant added
`
`conditional limitations, specifically the UE receives “an indication of whether
`
`accumulation of transmit power control (TPC) commands is enabled … if
`
`accumulation is enabled, a transmit power in association with an uplink
`
`communication [is] based on both the path loss and the accumulated TPC
`
`commands; and … if accumulation is not enabled, … power level [is] calculated …
`
`based on the path loss. (Id. at 1037-1051.)
`
`But sending an allocation of scheduled uplink resource on the same physical
`
`channel that carries TPC commands was also already well-known before the ’828
`
`patent was filed. In particular, it is a Node-B scheduling feature of a 3GPP UTRA
`
`
`
`2
`
`

`

`
`
`enhanced uplink system. (Min Decl., NAC1003, ¶87.) Not covered during this
`
`lengthy prosecution, enhanced uplink systems were well-known, and had been
`
`published and used in the 3GPP community prior to the filing date of the ’828 patent.
`
`(Id. at ¶¶69-71.) Using a known closed/open loop power control scheme in a known
`
`enhanced uplink system does not merit patentability. (Id. at ¶¶172-191.)
`
`Accordingly, Nokia respectfully requests inter partes review of claims 1-2, 5-6, 8-
`
`9, 12-13, 15-16, 19-20, 22-23, 26-27, 29-30, 33-34, 36-37, 40-41 of the ʼ828 patent.
`
`II. Mandatory Notices (37 C.F.R. § 42.8(a)(1))
`
`REAL PARTY-IN-INTEREST: The real party-in-interest is Petitioner Nokia of
`
`America Corporation (“Nokia”).1
`
`RELATED MATTERS: The ’828 patent is the subject of the following civil
`
`actions: Intellectual Ventures II LLC v. Sprint Spectrum L.P. et al. 2:17-cv-00662
`
`(TXED) (Lead) and Intellectual Ventures II LLC v. T-Mobile USA, Inc. et al. 2:17-
`
`cv-00661 (TXED) both filed September 21, 2017.
`
`LEAD AND BACKUP COUNSEL: Pursuant to 37 C.F.R. § 42.8(b)(3) and
`
`42.10(a), Petitioner appoints Brianne Straka (Reg. No. 70,152) as lead counsel and
`
`John P. Poulos (Reg. No. 72,551) as back-up counsel, at the address: QUINN
`
`EMANUEL URQUHART & SULLIVAN LLP, 191 N Wacker Drive Suite 2700
`
`Chicago, Illinois 60606, phone number (312) 705-7400 and facsimile (312) 705-
`
`
`1 Alcatel Lucent USA was acquired by Nokia in 2016.
`
`
`
`3
`
`

`

`
`
`7401. Petitioner also appoints John McKee (Reg. No. 65,926) as back-up counsel
`
`at the address: QUINN EMANUEL URQUHART & SULLIVAN LLP, 51 Madison
`
`Avenue 22nd Floor, New York, New York 10010, phone number (212) 849-7000
`
`and facsimile (212) 849-7100.
`
`SERVICE INFORMATION: Petitioner consents to electronic service by email
`
`at:
`
`briannestraka@quinnemanuel.com,
`
`johnmckee@quinnemanuel.com,
`
`johnpoulos@quinnemanuel.com, and katherinefuller@quinnemanuel.com.
`
`III. Grounds for Standing (37 C.F.R. § 42.104(a))
`
`The undersigned and Nokia certify that the ’828 patent is available for inter
`
`partes review. Nokia further certifies that it is not barred or estopped from
`
`requesting inter partes review on the grounds herein.
`
`IV.
`
`Identification of Challenge (37 C.F.R. § 42.104(b))
`
`A. Citation of Prior Art
`
`The ’828 patent was filed on August 12, 2004 as U.S. Application No.
`
`10/917,968. The following prior art documents applied on the grounds of
`
`unpatentability were published and/or filed prior the ’828 patent’s priority date,
`
`August 12, 2004.
`
`U.S. Patent No. 6,728,292 to Zeira et al. titled “Combined Closed
`
`Loop/Open Loop Power Control in a Time Division Duplex Communication
`
`System,” (NAC1005, “Zeira 292”) was filed June 11, 2003, and issued April 27,
`
`
`
`4
`
`

`

`
`
`2004. Zeira 292 qualifies as prior art to the ’828 patent at least under 35 U.S.C.
`
`§§ 102(a) and 102(e).
`
`U.S. Application Publication No. 2004/0219919 to Whinnett et al. titled
`
`“Management of Uplink Scheduling Modes in a Wireless Communication System,”
`
`(NAC1006, “Whinnett”) was filed April 30, 2003 and published November 4, 2004.
`
`Whinnett qualifies as prior art to the ’828 patent under 35 U.S.C. § 102(e).
`
`3GPP TSG RAN WG1#3 TDoc R1-99151 entitled “Adaptive Step Power
`
`Control (ASPC)” by Panasonic (Matsushita Communication Industrial Co., Ltd.)
`
`(NAC1007, “R1-99151”) was distributed at the TSG-RAN Working Group 1
`
`meeting #3 March 22-26, 1999, and was publicly available as least as early as March
`
`24, 1999, when it was publicly posted on 3GPP’s FTP server. (NAC1003 at ¶¶204-
`
`212.) R1-99151 qualifies as prior art to the ’828 patent at least under 35 U.S.C. §§
`
`102(a) and 102(b).
`
`B.
`
`Statutory Grounds for the Challenge
`
`Nokia challenges claims of 1-2, 5-6, 8-9, 12-13, 15-16, 19-20, 22-23, 26-27,
`
`29-30, 33-34, 36-37, 40-41 of the ’828 patent and requests that these claims be found
`
`unpatentable in view of the following references:
`
`
`
`5
`
`

`

`
`
`Ground
`
`References
`
`Basis
`
`Claims Challenged
`
`1
`
`Zeira 292 + Whinnett
`
`§ 103
`
`1, 5-6, 8, 12-13, 15, 19-
`20, 22, 26-27, 29, 33-34,
`36, 40-41
`
`2
`
`Zeria 292 + Whinnett + R1-99151
`
`§ 103 2, 9, 16, 23, 30, 37
`
`
`V. The ’828 Patent
`
`A. Overview of the ’828 Patent
`
`The ’828 patent describes a power control method in a wireless
`
`communication system that utilizes aspects of both open loop and closed loop power
`
`control systems to control power levels. (’828 patent, NAC1001, 7:64-8:2.) The
`
`’828 patent recognizes that open and closed loop power control methods were well-
`
`known and often used in wireless communications. (Id. at 1:41-2:32.) The ’828
`
`patent begins by discussing open and closed loop power control schemes generally,
`
`and then their advantages and disadvantages. (Id. at 5:15-7:63.)
`
`In an open loop power control system, the network receives an uplink signal
`
`from a UE, measures an interference value, and determines an error metric based on
`
`the uplink signal. (Id. at 5:51-63.) This error metric is used to update a signal to
`
`noise-plus-interference ratio (“SNIR”) Target value. (Id. at 5:62-63.) On the
`
`downlink, the network sends the SNIR Target value, interference measurements, a
`
`beacon signal, and an indication of the beacon signal power level to the UE. (Id. at
`
`
`
`6
`
`

`

`
`
`5:63-6:3.) The UE saves the SNIR Target value and interference measurements and
`
`measures the received power level of the beacon signal. (Id. at 5:65-6:5.) By
`
`comparing the beacon signal measured power level with indication of the beacon
`
`signal power level, the UE can determine a path loss. (Id. at 6:6-7.) The UE can use
`
`the SNIR Target, the interference measurements, and the computed path loss to set
`
`a transmit power level for future uplink transmissions. (Id. at 6:6-12.) An open loop
`
`power control system can be seen in Figure 2 below.
`
`(Id. at Figure 2.)
`
`
`
`Open loop power control quickly adjusts transmit power for fast channel
`
`fading by determining path loss on a per frame bases. (Id. at 2:11-13.) The
`
`interference level per timeslot although is updated at a relatively slow rate. (Id. at
`
`7:32-33.) Therefore, an open loop power control system can quickly adapt to path
`
`loss changes