throbber

`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`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., HUAWEI DEVICE (HONG KONG) CO. LTD.
`Petitioners
`v.
`
`CYWEE GROUP LTD.
`(record) Patent Owner
`
`
`
`
`
`Case IPR2019-XXX
`Patent No. 8,552,978
`
`
`
`
`MOTION FOR JOINDER TO IPR2018-01257
`UNDER 37 C.F.R. §§ 42.22 AND 42.122(b)
`
`
`
`

`

`
`
`Petitioners, 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., Huawei Device (Hong Kong)
`
`Co. Ltd. (“Huawei” or “Petitioners”) submit concurrently herewith a Petition for
`
`Inter Partes Review of U.S. Patent No. 8,552,978 (“Petition”). Pursuant to 35
`
`U.S.C. § 315(c) and 37 C.F.R. § 42.122(b), Petitioners respectfully request that
`
`their Petition be instituted and joined with pending inter partes review IPR2018-
`
`01257 (“the Google IPR”).
`
`Huawei’s motion for joinder and accompanying Petition are timely under 37
`
`C.F.R. §§ 42.22 and 42.122(b), as they are submitted within one month of
`
`December 11, 2018, the date that the Google IPR was instituted. Google IPR,
`
`Paper 8.
`
`Joinder is appropriate because it will promote efficient resolution of the
`
`issues without affecting scheduling for the pending proceeding. The Petition
`
`challenges the same claims instituted in the Google IPR, and relies on the same
`
`substantive arguments and substantive evidentiary record. No new grounds of
`
`unpatentability are asserted in the Petition and there will be no impact on the trial
`
`schedule for the existing review. Therefore, joinder would neither complicate the
`
`issues nor unduly delay the Google IPR.
`
`
`
`1
`
`

`

`
`
`Absent joinder, Huawei may be prejudiced as it has a significant interest in
`
`the underlying validity determination at issue in this proceeding, given the
`
`potential impact on litigation proceedings between CyWee and Huawei involving
`
`the same patent. Joinder would protect Huawei’s interests and avoid the potential
`
`prejudice to Huawei that could result from a settlement between CyWee and
`
`Google.
`
`Huawei has notified counsel for Petitioner in the Google IPR regarding the
`
`subject of this motion, and counsel does not oppose Huawei’s present motion.
`
`BACKGROUND AND RELATED PROCEEDINGS
`
`CyWee is the owner of U.S. Patent No. 8,552,978 (“the ’978 Patent”). The
`
`’978 Patent is asserted against Huawei in CyWee v. Huawei Technology, Inc., et
`
`al., 2-17-cv-00495 (E.D. Tex.) (“the Underlying Litigation”).
`
`The ’978 Patent was also asserted in the following actions:
`
`Cywee Group Ltd. v. Google, Inc., Case No. 1-18-cv-00571, (D. Del.);
`
`Cywee Group Ltd. v. ZTE Corporation et al., Case No. 3-17-cv-
`
`02130, (S.D. Cal.);
`
`Cywee Group Ltd. v. HTC Corporation et al., Case No. 2-17-cv-
`
`00932, (W.D. Wash.);
`
`Cywee Group Ltd. v. Motorola Mobility LLC, Case No. 1-17-cv-
`
`00780, (D. Del.);
`
`2
`
`
`
`
`
`
`
`
`
`
`
`

`

`
`
`
`
`
`
`
`
`Cywee Group Ltd. v. LG Electronics, Inc. et al., Case No. 3-17-cv-
`
`01102, (S.D. Cal.);
`
`Cywee Group Ltd. v. Samsung Electronics Co. Ltd. et al., Case No. 2-
`
`17-cv-00140, (E.D. Tex.);
`
`Cywee Group Ltd. v. Apple Inc., Case No. 4-14-cv-01853, (N.D. Cal.).
`
`The Google IPR, Case IPR2018-01257, was filed by Google on June 14,
`
`2018 and, like the instant Petition, challenges claims 10 and 12 of the ’978 Patent.
`
`On December 11, 2018, the Board instituted the Google IPR. Ex. 1012. The ’978
`
`patent is also at issue in Samsung Electronics Co., Ltd. v. Cywee Group Ltd.,
`
`IPR2019-00534, in which that petitioner also requested to join the Google IPR.
`
`Petitioners are also concurrently filing a petition challenging claims 1 and 3-5 of
`
`U.S. Patent No. 8,441,438 along with a motion to join Google LLC v. Cywee
`
`Group Ltd., IPR2018-01258, which the Board instituted on December 11, 2018.
`
`I.
`
`STATEMENT OF REASONS FOR RELIEF REQUESTED
`
`A. Legal Standard
`
`The Leahy–Smith America Invents Act (AIA) permits joinder of IPR
`
`proceedings. See generally Pub. L. No. 112-29, 125 Stat. 284 (2011). The statutory
`
`provision governing IPR joinder, 35 U.S.C. § 315(c), reads:
`
`(c) JOINDER.—If the Director institutes an inter partes
`review, the Director, in his or her discretion, may join as a party
`to that inter partes review any person who properly files a
`3
`
`
`
`

`

`
`
`petition under section 311 that the Director, after receiving a
`preliminary response under section 313 or the expiration of the
`time for filing such a response, determines warrants the
`institution of an inter partes review under section 314.
`
`Motions for joinder should: (1) set forth reasons why joinder is appropriate;
`
`(2) identify any new grounds of unpatentability asserted in the petition; (3) explain
`
`what impact (if any) joinder would have on the trial schedule for the existing
`
`review; and (4) address specifically how briefing and discovery may be simplified.
`
`See Kyocera Corp. v. Softview LLC, IPR2013-00004, Paper 15 at 4 (PTAB April
`
`24, 2013); see also Samsung Elecs. Co. v. Unifi Sci. Batteries, LLC, IPR2013-
`
`00236, Paper 22 at 3 (PTAB Oct. 17, 2013). Each of these factors supporting
`
`joinder are present in this motion and are discussed in detail below.
`
`B.
`
`Joinder Is Appropriate
`
`Joinder is appropriate here because it will not “unduly complicate or delay”
`
`the Google IPR. SAP America Inc. v. Clouding IP, LLC, IPR2014-00306, Paper 13
`
`at 4 (PTAB May 19, 2014). Indeed, there is “a policy preference for joining a party
`
`that does not present new issues that might complicate or delay an existing
`
`proceeding.” Enzymotec Ltd. v. Neptune Techs. & Bioresources, Inc., IPR2014-
`
`00556, Paper 19 at 6 (PTAB July 9, 2014).
`
`The Board has authority to join a properly-filed IPR petition to an IPR
`
`proceeding. See 35 U.S.C. § 315(c). The Board has found that joinder is
`4
`
`
`
`

`

`
`
`appropriate when, like here, (1) joinder is timely (2) no new grounds of
`
`unpatentability are introduced; (3) the party joining the proceeding agrees to
`
`consolidated filings and discovery; (4) joinder will not affect the schedule; and (5)
`
`joinder will streamline the proceedings, reduce the costs and burdens on the
`
`parties, and increase efficiencies for the Board without prejudicing the parties. See,
`
`e.g., Motorola Mobility LLC v. Softview LLC, IPR2013-00256, Paper 10 at 4-10
`
`(PTAB Jun. 20, 2013); see also Mylan Pharms. Inc. v. Novartis AG, IPR2015-
`
`00268, Paper 17 (PTAB April 10, 2015). As detailed below, joinder of the instant
`
`proceeding to the Google IPR is appropriate for all of these reasons.
`
`1.
`
`This Joinder Motion and the Petition Are Timely
`
`The Petition and the instant motion for joinder are timely under 35 U.S.C.
`
`§ 315(c), 37 C.F.R. §§ 42.22, and 42.122(b), as they are being submitted within
`
`one month of the date that the Google IPR was instituted. Rule 42.122(b) states
`
`that a motion for joinder shall be filed no later than one month after the granting of
`
`the petition that is sought to be joined. Google’s petition was granted on December
`
`11, 2018. See IPR2018-01257, Paper 8. The Petition, filed concurrently herewith
`
`on January 11, 2019, was filed no later than one month from the institution date of
`
`the Google IPR.
`
`2.
`
`Joinder Will Not Introduce Any New Grounds of
`Patentability
`
`5
`
`
`
`
`
`

`

`
`
`Huawei’s Petition is based only on the grounds on which the Board granted
`
`the Google IPR, for which joinder is requested. It challenges the same claims of
`
`the ‘978 Patent based on the same arguments, evidence, and grounds of
`
`unpatentability that were raised in the Google IPR. In addition, Huawei has
`
`submitted the same expert witness declaration as that entered on behalf of Google
`
`in the Google IPR. There is nothing new for the Patent Owner to address or for the
`
`Board to consider in response to the Petition.
`
`3. Huawei Agrees to Consolidated Proceedings, Including
`Briefing and other Filings.
`
`
`Huawei agrees to allow Google to take the lead in the joined proceedings
`
`and to work with Google to submit consolidated filings in an arrangement similar
`
`to that adopted by the Board in other joined proceedings. See, e.g., Motorola
`
`Mobility LLC, IPR2013-00256, Paper 10 at 9; Twitter, Inc. and Yelp Inc. v.
`
`Evolutionary Intelligence, LLC, IPR2014-00812, Paper 12 at 3 (PTAB June 25,
`
`2014); IPR2014-00086, Paper 16 at 2-4 (PTAB June 25, 2014). In the unlikely
`
`event that a procedural or substantive issue arises in the joined proceeding with
`
`which Huawei disagrees with Google, Huawei will request a conference call to
`
`seek permission and explain its reasons to submit a short separate filing, if needed,
`
`directed to points of procedural or substantive disagreement with Google. In such a
`
`circumstance, and at the Board’s discretion, the Board also may authorize Patent
`
`Owner corresponding pages to respond separately to any Huawei filing. See Dell
`6
`
`
`
`

`

`
`
`Inc. v. Network-1 Solutions, Inc., IPR2013-00385, Paper 17 at 8 (PTAB July 29,
`
`2013); Motorola Mobility, LLC, IPR2013-00256, Paper 10 at 8-9.
`
`Huawei will rely on Google to take testimony and defend depositions of
`
`witnesses, unless Google wishes otherwise or until Google terminates its
`
`involvement in the joined proceeding, and Huawei will refrain from requesting or
`
`reserving any additional deposition or oral hearing time. Huawei is willing to agree
`
`to other procedural concessions necessary to minimize complication or delay and
`
`result in a speedy trial with little or no impact on the Google IPR or the Board. In
`
`short, as long as Google remains an active participant in the IPR, Huawei will
`
`work with Google to avoid procedural disruptions and will assume the primary role
`
`only if Google ceases to participate in the IPR. See, e.g., Mylan Pharms. Inc.,
`
`IPR2015-00268, Paper 17 at 5.
`
`4.
`
`Joinder Will Not Impact the Board’s Ability to Complete
`the Review Within the One-Year Period
`
`
`Joinder in this case will not impact the Board’s ability to complete its review
`
`in a timely manner because of the complete overlap between the two petitions for
`
`the raised grounds. As discussed above, Huawei will adhere to all applicable
`
`deadlines set forth in the Google IPR Scheduling Order and coordinate its
`
`approach and filings with Google. Additionally, no additional expert discovery will
`
`be needed as the Petition relies on the same declaration from the same expert filed
`
`
`
`7
`
`

`

`
`
`in the Google IPR. Thus, in the event that Google settles, Huawei will be well-
`
`positioned to continue participating in this proceeding without any delay.
`
`The first deadline in the Google IPR is Patent Owner’s response to Google’s
`
`petition (37 C.F.R. § 42.120) and any motion to amend the patent (37 C.F.R. §
`
`42.121). Pursuant to the Scheduling Order in the Google IPR, this deadline is
`
`currently set for March 12, 2019 – over seven weeks from the date of this motion.
`
`IPR2018-01257, Paper 9 at 8. Should the Board grant Huawei’s motion for joinder,
`
`Patent Owner will have ample time to complete its submissions by its deadline.
`
`And because Huawei’s petition for inter partes review does not raise any new
`
`issues, Patent Owner’s Response will not require any analysis beyond what Patent
`
`Owner is already required to undertake to respond to Google’s petition. Also,
`
`Patent Owner has filed a Request for Rehearing on Decision to Institute, further
`
`mitigating any impact joinder may have on the schedule in the Google Petition.
`
`IPR2018-01257, Paper 10.
`
`In view of the above, Huawei submits that the current schedule in the
`
`Google IPR can remain unchanged and that joinder will not affect the Board’s
`
`ability to complete its review and issue a final decision within the statutory time
`
`limits under 35 U.S.C. § 316(a)(11) and 37 C.F.R. § 42.100(c).
`
`5.
`
`Joinder Will Streamline the Proceedings, Reduce the Costs
`and Burdens on the Parties, and Increase Efficiencies for
`the Board Without Prejudicing the Parties
`
`8
`
`
`
`
`
`

`

`
`
`Granting joinder will not prejudice the parties or burden the Board. Rather,
`
`joinder will promote judicial efficiency. As discussed above, the validity of the
`
`‘978 Patent is squarely at issue in the Underlying Litigation and the Google IPR. A
`
`final written decision on the validity of the challenged claims will simplify,
`
`minimize, or even entirely resolve, issues in the Underlying Litigation. If the
`
`claims are invalidated in a final decision, the Underlying Litigation is greatly
`
`simplified. If the Board permits Huawei to join the Google IPR and the challenged
`
`claims are upheld in a final written decision, Huawei may be estopped from further
`
`challenging the validity of the claims on these grounds, thus avoiding duplication
`
`of Patent Owner’s efforts in the litigation against Huawei. See 35 U.S.C. §
`
`315(e)(2). Accordingly, regardless of the Board’s final decision, joinder simplifies
`
`the issues and reduces duplicate efforts and the possibility of inconsistencies.
`
`Finally, permitting joinder will not prejudice the parties to the Google IPR.
`
`Huawei raises no issues that are not already before the Board and agrees to
`
`coordinate its filings and arguments with Google. Thus, neither Google nor Patent
`
`Owner will need to expend any additional resources beyond those required in the
`
`Google IPR. Indeed, because the Petition does not raise any new issues, joinder
`
`will not require any additional analysis or otherwise affect the content of Patent
`
`Owner’s Response. Further, Patent Owner will suffer no prejudice from joinder
`
`because the IPR proceedings will provide a relatively inexpensive full and fair
`
`
`
`9
`
`

`

`
`
`opportunity to respond to the challenged claims in a venue that should proceed
`
`more quickly than the litigation against Huawei. See Sony Corp. v. Yissum
`
`Research Development Co. of the Hebrew Univ. of Jerusalem, IPR2013-00326,
`
`Paper 15 at 7 (PTAB Sept. 24, 2013).
`
`II. THE CLAIM CONSTRUCTION RULE CHANGE DOES NOT
`AFFECT THE INSTANT PETITION AND MOTION FOR JOINDER
`The Board instituted inter partes review for the Google Petition under the
`
`broadest reasonable interpretation (BRI) standard. Ex. 1007 at 9-16. While the
`
`claim construction standard has changed from BRI to Phillips for petitions filed
`
`after November 13, 2018, the Board should apply the BRI standard to Huawei’s
`
`petition. Huawei is seeking joinder as a co-petitioner to the Google proceeding,
`
`see 35 U.S.C. § 315(c) (“join as a party to that inter partes review.”) As is
`
`customary, granting of this motion would result in Huawei being “joined as a
`
`petitioner in that case [i.e., the Google IPR] pursuant to 37 C.F.R. § 42.122” and
`
`the dismissal of Huawei’s copy-cat petition pursuant to 37 C.F.R. § 42.71(a). See,
`
`e.g., Samsung Electronics America, Inc. v. Uniloc 2017 LLC, IPR2018-01383,
`
`Paper 9 at 6 (Nov. 19, 2018). Thus, the rules applicable to the Google IPR
`
`(including the BRI claim construction standard) should also apply to Huawei’s
`
`
`
`10
`
`

`

`
`
`Petition, as “that case” will proceed and Huawei’s copy-cat petition will be
`
`dismissed.1
`
`III. CONCLUSION
`
`For the foregoing reasons, Huawei respectfully requests that its Petition for
`
`Inter Partes Review of U.S. Patent No. 8,552,978 be granted and that the
`
`proceedings be joined with pending IPR proceeding IPR2018-01257.
`
`Respectfully submitted,
`
`
`Dated: January 11, 2019
`
`
`
`/s/Kristopher L. Reed (Reg. No. 58,694)
`Kristopher L. Reed
`KILPATRICK TOWNSEND &
`STOCKTON LLP
`Two Embarcadero Center 19th Floor
`San Francisco, CA 94111
`(303) 571-4000
`kreed@kilpatricktownsend.com
`
`Counsel for Petitioners
`
`
`
`1 If the Board deems that its rule(s) require application of the Phillips standard to
`
`Huawei’s Petition, Huawei seeks waiver of such rule(s) pursuant to 37 C.F.R. §
`
`42.5(b).
`
`
`
`11
`
`

`

`
`
`CERTIFICATE OF SERVICE
`
`Pursuant to 37 C.F.R. § 42.6(e) and 42.105(b), the undersigned certifies that
`
`on January 11, 2019 a copy of this MOTION FOR JOINDER UNDER 37
`
`C.F.R. §§ 42.22 AND 42.122(b) was served upon the Patent Owner via express
`
`mail at the following address:
`
`DING YU TAN
`8819 Purdy Crescent Trail
`Richmond, TX 77406
`In addition, a courtesy copy was served electronically upon counsel of
`
`record for Patent Owner in the litigation pending before the U.S. District Court for
`
`the Eastern District of Texas entitled CyWee Group Ltd. v. Huawei Technologies
`
`Co., Inc., et al., Case No. 2:17-CV-0495-WCB-RSP (E.D. Tex.) at the following
`
`addresses:
`
`Michael W. Shore (Texas 18294915)
`mshore@shorechan.com
`Alfonso G. Chan (Texas 24012408)
`achan@shorechan.com
`Christopher Evans (Texas 24058901)
`cevans@shorechan.com
`Ari B. Rafilson (Texas 24060456)
`arafilson@shorechan.com
`William D. Ellerman (Texas 24007151)
`wellerman@shorechan.com
`Paul T. Beeler (Texas 24095432)
`pbeeler@shorechan.com
`SHORE CHAN DEPUMPO LLP
`901 Main Street, Suite 3300
`Dallas, Texas 75202
`Telephone: (214) 593-9110
`
` - i -
`
`

`

`
`
`
`A courtesy copy was also served electronically upon counsel of record for
`
`Patent Owner in Google LLC v. Cywee Group Ltd., IPR2018-01257 at the
`
`following addresses:
`
`Jay P. Kesan - jkesan@dimuro.com
`Cecil E. Key - ckey@dimuro.com
`Arlen Papazian - apapazian@dimuro.com
`DimuroGinsberg PC
`
` courtesy copy was also served electronically upon counsel of record for
`
` A
`
`Petitioner Google LLC in Google LLC v. Cywee Group Ltd., IPR2018-01257 at the
`
`following addresses:
`
`Matthew A. Smith - smith@smithbaluch.com
`Andrew S. Baluch - baluch@smithbaluch.com
`Christopher M. Colice - colice@smithbaluch.com
`SMITH BALUCH LLP
`
`
`
`/s/Kristopher L. Reed
`Kristopher L. Reed (Reg. No. 58,694)
`
`Counsel for Petitioners
`
`
`Date: January 11, 2019
`
`
`
`
`
`
`
`
`
`
`71450056V.2
`
` - ii -
`
`

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