throbber

`
`Filed: August 30, 2019
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`____________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`____________________
`
`GOOGLE LLC, ZTE (USA), INC., SAMSUNG ELECTRONICS CO., LTD.,
`LG ELECTRONICS INC., HUAWEI DEVICE USA, INC.,
`HUAWEI DEVICE CO. LTD., HUAWEI TECHNOLOGIES CO. LTD.,
`HUAWEI DEVICE (DONGGUAN) CO. LTD.,
`HUAWEI INVESTMENT & HOLDING CO. LTD.,
`HUAWEI TECH. INVESTMENT CO. LTD., and
`HUAWEI DEVICE (HONG KONG) CO. LTD.,
` Petitioner
`
`v.
`
`CYWEE GROUP LTD.
`Patent Owner
`
`____________________
`
`Case IPR2018-01257
`Patent No. 8,552,978
`____________________
`
`
`
`PATENT OWNER’S REPLY IN SUPPORT OF MOTION TO TERMINATE
`
`
`
`

`

`
`
`
`2001
`
`2002
`
`2003
`
`2004
`
`2005
`
`2006
`
`2007
`
`2008
`
`2009
`
`2010
`
`2011
`
`2012
`
`2013
`
`Case IPR2018-01257
`Patent No. 8,552,978
`
`LIST OF EXHIBITS
`
`Declaration of Dr. Gary L. Blank [WITHDRAWN]
`
`Curriculum Vitae of Dr. Gary L. Blank CV [WITHDRAWN]
`
`Claim Construction Opinion and Order (Doc. 117), Cywee
`Group Ltd. v. Samsung Elecs. Co., Ltd., C.A. No. 2:17-CV-
`00140-WCB-RSP (E.D. Tex., July 9, 2018)
`
`
`
`Expert Declaration of Dr. Joseph LaViola, Ph.D., in Support
`of Patent Owner Response
`
`Curriculum Vitae of Dr. Joseph LaViola, Ph.D.
`
`Order (Doc. 153), Cywee Group Ltd. v. Samsung Elecs. Co.,
`Ltd., C.A. No. 2:17-CV-00140-WCB-RSP (E.D. Tex., Aug.
`14, 2018)
`
`Memorandum Opinion (Doc. 55), CyWee Group Ltd. v.
`Motorola Mobility LLC, C.A. No. 17-780-RGA (D. Del.,
`Dec. 21, 2018)
`
`File History of U.S. Application No. 10/396,439
`
`File History of U.S. Application No. 12/413,722
`
`File History of U.S. Application No. 13/367,058
`
`Expert Declaration of Dr. Joseph LaViola, Ph.D., in Support
`of Motion to Amend
`
`File History of U.S. Provisional Application 61/292,558
`
`Google’s Responses to CyWee’s Requests for Production,
`CyWee Group Ltd. v. Google, Inc., No. 1:18-cv-00571 (D.
`Del.) (Sep. 4, 2018)
`
`ii
`
`

`

`
`2014
`
`2015
`
`2016
`
`2017
`
`2018
`
`2019
`
`2020
`
`2021
`
`2022
`
`2023
`
`2024
`
`2025
`
`2026
`
`2027
`
`Case IPR2018-01257
`Patent No. 8,552,978
`
`Google/Samsung 2011-2012 Mobile Application Distribution
`Agreement (Android)
`
`CyWee Group, Ltd. v. Samsung Elecs. Co. Ltd., C.A. No.
`2:17-CV-00140-WCB-RSP, Doc.
`1-1
`(Exhibit A,
`Infringement Claim Chart)
`
`Web Print-Out “Introducing PAX: the Android Networked
`Cross-License Agreement,” available at
`<https://blog.google/outreach-initiatives/public-
`policy/introducing-pax-android-networked-cross-license-
`agreement/>
`
`List of IPR Petitions Filed against Seven Networks, LLC
`
`Demonstrative: Relationship of Android Defendants
`
`Transcript of Call Authorizing Patent Owner to File Motion
`to Terminate (July 8, 2019)
`
`Declaration of Shun-nan Liou
`
`CyWee, Where Technology Entertains 2009.09
`
`JIL Game System Hardware Specification Ver. 1.5
`
`JIL Phone Bill of Materials (May 24, 2010)
`
`Photographs of JIL Phone Prototype
`
`CyWee Phone API Reference
`
`CyWee Motion Fusion Solution
`
`CyWee Where technology entertains Technical Presentation:
`Motion Technology and Gaming Applications
`
`
`iii
`
`

`

`
`2028
`
`2029
`
`2030
`
`2031
`
`2032
`
`2033
`
`2034
`
`2035*
`
`2036
`
`2037
`
`2038
`
`2039
`
`Case IPR2018-01257
`Patent No. 8,552,978
`
`July 29, 2009 email to James Shen, Qualcomm
`
`Attachment to July 29, 2009 email to James Shen,
`Qualcomm
`
`CyWee/Qualcomm Mutual NDA (April 23, 2008)
`
`Attitude.cpp file (last modified February 12, 2010)
`
`Expert Declaration of Dr. Joseph LaViola, Ph.D., in Support
`of Patent Owner’s Reply in Support of Motion to Amend
`
`Transcript of Deposition of Prof. Majid Sarrafzadeh (July 24,
`2019)
`
`Attitude.cpp file, with Line Numbers (last modified February
`12, 2010)
`
`Amended Notice of Deposition of Collin W. Park
`(previously filed as Paper 62)
`
`Complaint for Patent Infringement, CyWee Group Ltd., v.
`Samsung Elec. Co., Ltd., et al., C.A. No. 2;17-cv-00140-
`WCB-RSP, Dkt. 1 (filed Feb. 17, 2017)
`
`Petition, LG Elec. Inc. v. CyWee Group Ltd., IPR2019-
`00559, Paper 1 (Jan. 10, 2019)
`
`Petition, LG Elec. Inc. v. CyWee Group Ltd., IPR2019-
`00560, Paper 1 (Jan. 10, 2019)
`
`Petition, LG Elec. Inc. v. CyWee Group Ltd., IPR2019-
`01203, Paper 1 (June 15, 2019)
`
`
`
`
`* Pursuant to 37 C.F.R. § 42.6(d) previously filed papers and exhibits will not be
`filed again under the new exhibit numbers unless so requested by the Board.
`
`iv
`
`

`

`
`2040*
`
`2041*
`
`2042
`
`2043
`
`2044
`
`2045
`
`2046
`
`2047
`
`2048
`
`Case IPR2018-01257
`Patent No. 8,552,978
`
`Web Print-Out “Introducing PAX: the Android Networked
`Cross-License Agreement,” available at
`<https://blog.google/outreach-initiatives/public-
`policy/introducing-pax-android-networked-cross-license-
`agreement/>
`(previously filed as Ex. 2016)
`
`Declaration of Collin W. Park
`(previously filed as Ex. 1038)
`
`Web Print-Out, Morgan Lewis, Lawflash Article “Statutory
`Time Bar Applies to Privity and RPI Relationships Arising
`After Filing of IPR Petition,” (June 27, 2019), available at
`< https://www.morganlewis.com/pubs/statutory-time-bar-
`applies-to-privity-rpi-relationships-arising-after-ipr-petition-
`filing>
`
`CyWee Litigation Timeline
`
`CyWee Group, Ltd. v. LG Elecs., Inc., et al., Exemplary
`Claim Chart
`Transcript of Deposition of Collin W. Park (August 21,
`2019)
`
`Google U.S. Trademark Reg. No. 4,692,657, Statement of
`Use (filed December 2, 2014)
`
`Aug. 16-20, 2019, Correspondence between C. Key and M.
`Smith
`
`LG Electronics, Inc. Filings for ZNFG011C (Google Pixel 2
`XL), External Photographs (submitted Sep. 11, 2017)
`
`v
`
`

`

`Google Misstates The Law. First, Google asserts that “RPI is the
`
`Case IPR2018-01257
`Patent No. 8,552,978
`
`
`
`relationship between a party and a proceeding; it does not describe the relationship
`
`between parties.” Opp at 8 (emphasis in original).1 The Federal Circuit disagrees
`
`and has made clear that the RPI and Privity analyses are concerned with
`
`“evaluating the relationship between a party bringing a suit and non-party.” AIT,
`
`897 F.3d 1336, 1356 (Fed. Cir. 2018). The Federal Circuit also made clear that it is
`
`the relationship as it relates to the subject matter of the proceeding that is relevant.
`
`Id. at 1349, 1353. It is impossible under AIT for LG to not be at least an RPI to
`
`Google’s Petition when Google is admittedly an RPI to LG’s identical joinder
`
`petition. The relationship between the parties is the same. The subject matter is the
`
`same. Google’s contrary positions simply have no legal or factual support.
`
`Second, Google insists that this IPR is not being “directed, funded, or
`
`controlled” by any of the Android Defendants. Opp. at 4, 7-8. But the Federal
`
`Circuit has rejected the “direction and control” test as inappropriately narrow. AIT,
`
`897 F.3d at 1356. Rather, RPI/Privity determinations require “a flexible approach...
`
`with an eye toward determining whether the non-party is a clear beneficiary that
`
`
`
`1 Citing Aruze Gaming Macau, Ltd. v. MGT Gaming, Inc., IPR2014-01288, Paper
`13 at 11 (Feb. 20, 2015), Petitioner asserts that Aruze was cited favorably by AIT,
`897 F.3d at 1365, n.7. However, Aruze was cited for the proposition that § 315 and
`§ 312(a)(2) are distinct inquires, not for what Petitioner asserts here. See id.
`Google’s contrary indication is disingenuous and borders on an outright attempt to
`mislead the Board.
`
`1
`
`

`

`
`has a preexisting, established relationship with the petitioner.” Id. at 1351
`
`Case IPR2018-01257
`Patent No. 8,552,978
`
`(emphasis added). When faced with the proper legal standard put forth in AIT,
`
`Google cannot refute that the Android Defendants are RPIs/Privies.
`
`The Android Defendants Are “Clear Beneficiaries” Of These
`
`Proceedings With Preexisting, Established Relationships. Notably, Google
`
`never denies that any of the Android Defendants are “clear beneficiaries” of this
`
`IPR or that they have “preexisting, established relationships” with Google. Google
`
`instead limply asserts that it has its own, separate interests in invalidating CyWee’s
`
`Patents because it was sued separately. Opp. at 9. The controlling law makes clear
`
`that the point of the RPI/Privity analysis “is not to probe [the petitioner]’s interest
`
`(it does not need any); rather, it is to probe the extent to which [the non-party]...
`
`has an interest in and will benefit from [the petitioner]’s actions.” Id. at 1353;
`
`Ventex co., Ltd. v. Columbia Sportswear N. Am., Inc., IPR2017-00651, Paper 148,
`
`9-10 (PTAB, Jan. 24, 2019). Each Android Defendant has a “considerable interest
`
`in [Google]’s pursuit of an invalidity determination for claims of both the ‘[438]
`
`and ‘[978] patents... There cannot be any credible assertion that a determination of
`
`invalidity as to the claims of the patents would not inure to the benefit of” the
`
`Android Defendants in the related district court litigations. Id. at 9.
`
`Mr. Park
`
`2
`
`
`
`
`
`

`

`
`
`Mr. Park also admits
`
`Case IPR2018-01257
`Patent No. 8,552,978
`
` 2 Ex. 2045, 26:22-27:19, 29:8-30:1; 41:7-19.
`
`
`
`
`
` and he asserted a
`
`common interest privilege as between LG and Google. Id. at 22:2-30:1; 37:5-38-8,
`
`41:7-19, 45:3-9. These facts establish a clear, preexisting legal relationship, which
`
`at a minimum brings into serious question the accuracy of Google’s identification
`
`of RPIs/Privies. In response, Google has refused to produce any relevant
`
`agreements despite its duty to “serve relevant information that is inconsistent with
`
`[its] position” that the Android Defendants are not RPIs/Privies. 37 C.F.R.
`
`42.51(b)(1)(iii); Ex. 2047 at 1. By refusing to produce facts to rebut CyWee’s
`
`evidence,3 Google must accept the resulting consequence that it has failed to meet
`
`its burden of demonstrating that it has identified all RPIs/Privies as the statute
`
`requires. I.M.L. SLU v. WAG Acquisition, LLC, IPR2016-01658, 2018 WL
`
`1128521 at *5-*6 (PTAB Feb. 27, 2018).
`
`Google has long maintained substantial business relationships with the
`
`
`
`2
` Ex.
`2045, 26:22-27:19; 29:8-30:1. That is the exact same “interest” an RPI has with an
`IPR Petitioner because that is the goal of every IPR. AIT, 897 F.3d at 1348.
`
` 3
`
` The Board granted CyWee’s Motion for Additional Discovery in the related
`IPR2019-00143, Paper 20, based on similar evidence as presented here.
`
`3
`
`

`

`
`Android Defendants relevant to the Petition subject matter. CyWee has accused the
`
`Case IPR2018-01257
`Patent No. 8,552,978
`
`Defendants’ hardware running Google’s Android OS of infringement. Google
`
`relied on a Samsung phone as its own “evidence of use” to register its ANDROID
`
`cellphone trademark. Ex. 2046. Google is the curator of the Android software
`
`repository. Ex. 1030 at 2. According to its FCC filings, LG manufactures the Pixel
`
`2 XL for Google, see Ex. 2048, one of the four Google devices CyWee accused in
`
`its district court complaint against Google. Ex. 1026, at 16-17 ¶ 38, and 23-25 ¶¶
`
`91-107. Google’s sole explanation for identifying Huawei as an RPI to this IPR
`
`was
`
`
`
`Ex. 2047 at 4. LG is the ODM for the Google Pixel
`
`2 XL, an accused device in the Google lawsuit. Ex. 2045, 228:13-20; Ex. 2048.
`
`Thus,
`
` it should have named
`
`LG as an RPI. It is therefore clear that Google is acting on behalf of all members of
`
`the common interest and joint defense groups in filing its IPR, including time-
`
`barred Samsung and LG.
`
`Collin Park’s Declaration Is Not Competent Or Credible. LG correctly
`
`identified that it has an RPI relationship with Google. Realizing that its honest
`
`disclosure is fatal to the Google IPRs, LG’s lead IPR counsel now attempts to
`
`retreat, in part, by arguing for an RPI standard expressly rejected by the Federal
`
`Circuit in AIT,
`
` Ex. 2045, 191:3-14. As
`
`4
`
`

`

`
`a result, Mr. Park’s opinions and conclusions on RPIs/Privies lack the proper, legal
`
`Case IPR2018-01257
`Patent No. 8,552,978
`
`foundation. Mr. Park also cannot provide any contrary factual evidence because he
`
`admitted he
`
`, despite a legal
`
`obligation to do so. Id. at 96:14-101:15, 116:8-119:1.
`
`Mr. Park cites to several specific IPR Petitions filed by Morgan Lewis,
`
`claiming it is his firm’s common practice to disclose parties to a petition to which
`
`joinder is sought as RPIs out of abundance of caution, even when it does not
`
`believe those parties to be RPIs. Ex. 1036, ¶ 10 (citing to IPRs 2017-01617, 01682,
`
`and 01808); Ex. 2045, 69:17-70:10. However, review of the cited IPR Petitions
`
`shows that Morgan Lewis does the opposite. The cited IPR Petitions clearly
`
`indicate which parties are not believed to be RPIs. Morgan Lewis’s other clients
`
`identified parties that “are co-defendants with Petitioner [] in the pending multi-
`
`district litigation identified below [] but are not real parties-in-interest to this
`
`proceeding.” See, e.g., IPR2017-01617, Paper 1 at 4. That did not happen here.
`
`LG’s petitions here unequivocally identify Google and Huawei as RPIs.
`
`Mr. Park’s declaration deserves no weight. Mr. Park admits
`
` when he executed his declaration and admits
`
`
`
`
`
` as required by statute. His declaration
`
`is at best materially misleading as to whether Morgan Lewis has used similar
`
`language in other IPR petitions. The IPRs must be terminated.
`
`5
`
`

`

`Case IPR2018-01257
`Patent No. 8,552,978
`
`Respectfully submitted,
`
`
`
`
`
`
`
`/Jay P. Kesan/
`Jay P. Kesan
`Reg. No. 37,488
`
`Counsel for Patent Owner
`Cywee Group Ltd.
`
`
`
`Dated: August 30, 2019
`
`
`
`
`
`
`
`
`
`
`6
`
`

`

`
`
`Certificate of Service
`
`Case IPR2018-01257
`Patent No. 8,552,978
`
`Pursuant to 37 C.F.R. § 42.6(e), the undersigned certifies that on the date
`
`indicated below, a complete and entire copy of this submission, including the
`
`exhibits hereto, was provided by email to Petitioners’ counsel via email, as agreed
`
`to by Petitioners’ Service Information in the Petition submissions, by serving the
`
`email addresses of record as follows:
`
`Counsel for Google:
`
`Matthew A. Smith
`smith@smithbaluch.com
`
`
`
`Andrew S. Baluch
`baluch@smithbaluch.com
`
`
`
`
`
`Yeuzhong Feng
`yfeng@brinksgilson.com
`
`ZTE_CyweeIPRs@brinksgilson.com
`
`
`Christopher M. Colice
`colice@smithbaluch.com
`
`Counsel for ZTE:
`
`James R. Sobieraj
`jsobierah@brinksgilson.com
`
`Andrea Shoffstall
`ashoffstall@brinksgilson.com
`
`Counsel for Samsung:
`
`Naveen Modi
`Chetan Bansal
`PH-Samsung-CyweeiIPR@paulhastings.com
`
`
`
`
`
`
`
`
`
`

`

`
`
`Counsel for LG:
`
`Collin Park
`collin.park@morganlewis.com
`
`Jeremy Peterson
`jeremy.peterson@morganlewis.com
`
`Case IPR2018-01257
`Patent No. 8,552,978
`
`
`
`Andrew Devkar
`andrew.devkar@morganlewis.com
`
`Adam Brooke
`adam.brooke@morganlewis.com
`
`
`
`
`
`
`
`
`
`
`
`
`
`/Jay P. Kesan/
`Jay P. Kesan
`Reg. No. 37,488
`
`Counsel for Patent Owner
`Cywee Group Ltd.
`
`MLB_CyweeLGE@morganlewis.com
`
`Counsel for Huawei:
`
`Kristopher L. Reed
`Benjamin M. Kleinman
`Norris P. Boothe
`HuaweiCywee@kilpatricktownsend.com
`
`
`
`
`Dated: August 30, 2019
`
`
`
`
`
`
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

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.

throbber

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.

Become a Member

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

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket