throbber
IPR2019-00744
`U.S. Patent No. 7,167,487
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`
`
`
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`
`
`
`
`
`
`MICROSOFT CORPORATION
`
`Petitioner
`
`v.
`
`UNILOC 2017 LLC
`
`Patent Owner
`
`
`
`
`
`IPR2019-00744
`
`U.S. PATENT NO. 7,167,487
`
`
`
`
`
`
`
`
`
`
`
`
`
`PATENT OWNER OPPOSITION TO MOTION FOR JOINDER
`
`
`
`
`
`
`
`
`
`
`

`

`IPR2019-00744
`U.S. Patent No. 7,167,487
`
`
`
`
`I.
`
`INTRODUCTION
`
`Table of Contents
`
`II. ARGUMENT
`
`A.
`
`Joinder will cause rather than avoid undue prejudice.
`
`1. Joinder will cause undue prejudice to Uniloc.
`
`2. Joinder is not necessary to prevent undue prejudice to Microsoft.
`
`B.
`
`The General Plastic factors weigh against institution and joinder.
`
`3
`
`3
`
`4
`
`5
`
`6
`
`8
`
`C. Microsoft is not taking an understudy role and joinder will impact the
`schedule or unduly prejudice Uniloc.
`11
`
`D. Microsoft’s joinder motions admit the cumulative nature of
`Microsoft’s petitions.
`
`III. CONCLUSION
`
`11
`
`11
`
`
`
`
`
`
`
`
`
`2
`
`

`

`IPR2019-00744
`U.S. Patent No. 7,167,487
`
`
`
`I.
`
`INTRODUCTION
`
`Four months after Apple filed two petitions challenging the ’487 patent on
`
`November 12, 2018,1 Microsoft filed two petitions of its own challenging the same
`
`patent on March 4, 2019.2 Rather than seeking to join the Apple IPR, Microsoft
`
`argued its petitions “present [the] art in a different light and rel[y] on other art not
`
`cited in [Apple’s] petitions.” See Petitions at 8. On July 2, 2019, after trial was
`
`instituted in the Apple IPRs and after Uniloc filed its preliminary responses in the
`
`Apple IPRs and the Microsoft IPRs, Microsoft made an about face – insisting its
`
`petitions are not really that different from Apple’s and should be joined to the Apple
`
`IPRs even though joinder will add new issues to the Apple IPRs. Microsoft’s wait
`
`and see approach is a transparent attempt to game the system. Its joinder motions
`
`should be denied because Microsoft fails to show joinder of new issues to the Apple
`
`IPR is necessary to avoid prejudice to Microsoft. To the contrary, joinder will
`
`unduly prejudice Uniloc.
`
`II. ARGUMENT
`
`As the moving party, Microsoft has the burden of proof to establish that it is
`
`entitled to the requested relief. 37 C.F.R. §§ 42.20(c), 42.122(b). When determining
`
`whether to grant a motion for joinder, the Board considers factors including: (1) time
`
`and cost considerations, including the impact joinder would have on the trial
`
`schedule; and (2) how briefing and discovery may be simplified. See Order
`
`
`1 See IPR2019-00222 and IPR2019-00252 (referred to here as the “Apple IPRs”).
`2 See IPR2019-00744 and IPR2019-00745 (referred to here as the “Microsoft IPRs”).
`3
`
`
`
`
`

`

`IPR2019-00744
`U.S. Patent No. 7,167,487
`
`
`
`Authorizing Motion for Joinder (Paper 15, 4), Kyocera Corp. v. SoftView, LLC,
`
`IPR2013-00004 (PTAB Apr. 24, 2013).
`
`Even when a party seeks to join a nearly identical petition, joinder should not
`
`be granted as a matter of right. See 35 U.S.C. § 316(b); 37 C.F.R. § 42.1(b); 157
`
`CONG. REC. S1376 (daily ed. Mar. 8, 2011) (statement of Sen. Kyl) (“The Director
`
`is given discretion . . . over whether to allow joinder. This safety valve will allow
`
`the Office to avoid being overwhelmed if there happens to be a deluge of joinder
`
`petitions in a particular case.”).
`
`And when a party seeks to join new issues, joinder is granted “only in limited
`
`circumstances—namely, where fairness requires it and to avoid undue prejudice to
`
`a party.” Proppant Express Investments, LLC v. Oren Techs., LLC, Case IPR2018-
`
`00914, Paper 38, p. 4 (Mar. 13, 2019) (designated: Mar. 13, 2019) (Precedential
`
`Opinion Panel decision).
`
`Here, Microsoft’s motion should be denied because joinder of new issues will
`
`unduly prejudice Uniloc and complicate briefing and discovery. Further, joinder of
`
`new issues is not necessary to avoid prejudice to Microsoft. Finally, the General
`
`Plastic factors weigh against institution and joinder
`
`A.
`
`Joinder will cause rather than avoid undue prejudice.
`
`Microsoft’s motion should be denied under Proppant because joinder of
`
`Microsoft’s new issues will cause rather than avoid undue prejudice to a party.
`
`Proppant explains that the Board will exercise discretion to join new issues to an
`
`existing proceeding “only in limited circumstances—namely, where fairness
`
`
`
`
`4
`
`

`

`IPR2019-00744
`U.S. Patent No. 7,167,487
`
`
`
`requires it and to avoid undue prejudice to a party.” Proppant, Case IPR2018-00914,
`
`Paper 38, p. 4. Circumstances leading to this “narrow exercise of [the Board’s]
`
`jurisdiction may include, for example, actions taken by a patent owner in a
`
`co-pending litigation such as the late addition of newly asserted claims.” Id. On the
`
`other hand, “the Board does not generally expect fairness and prejudice concerns to
`
`be implicated by, for example, the mistakes or omissions of a petitioner.” Id.
`
`1.
`
`Joinder will cause undue prejudice to Uniloc.
`
`Joinder of new issues to the Apple IPRs will unduly prejudice Uniloc.
`
`Uniloc’s patent owner responses in the Apple IPRs are due August 27, 2019. If
`
`Microsoft’s joinder motions are granted, Uniloc will have less than one month to
`
`prepare its respective patent owner responses. In each Apple IPR, Uniloc will be
`
`required to not only respond to Apple’s petition but Microsoft’s distinct petition
`
`containing art presented “in a different light” and new art. As Microsoft
`
`acknowledges, this will also require Uniloc to: (1) address an addition expert report;
`
`(2) depose an additional expert; and (3) supplement its own expert testimony. See
`
`IPR2019-00744, Paper 7, p. 2, 11, 16-17; IPR2019-00745, Paper 7, p. 2, 11, 17.
`
`Less than one month is not “ample time” to do this, as Microsoft insists. There is a
`
`reason the scheduling orders entered in the Apple IPRs gave approximately three
`
`months after institution to accomplish these tasks.
`
`Microsoft insists joinder will cause no prejudice because “Uniloc has already
`
`had significant time to consider the arguments presented in the March 4, 2019
`
`Microsoft Petition[s].” See IPR2019-00744, Paper 7, p. 17; IPR2019-00745, Paper
`
`
`
`
`5
`
`

`

`IPR2019-00744
`U.S. Patent No. 7,167,487
`
`
`
`7, p. 17. This logic would justify allowing less than one month from institution to
`
`file a patent owner response in every IPR. Uniloc had significant time to consider
`
`arguments presented in the November 12, 2018 Apple petitions before the Apple
`
`IPRs were instituted, but this of course does not justify allowing Uniloc less than
`
`one month after institution to file responses. Less than one month is not sufficient
`
`time for Uniloc to prepare a response to a distinct petition that requires addressing
`
`new references, references presented in a “different light,” and a separate expert
`
`response.
`
`Microsoft also argues that introduction of a new reference in the Apple IPRs
`
`will simplify briefing, but what Microsoft really means is that it believes
`
`introduction of the new reference will bolster Microsoft’s position. Introducing new
`
`art at this stage will not simplify the Apple IPRs; it will prejudice Uniloc.
`
`2.
`
`Joinder is not necessary to prevent undue prejudice to
`Microsoft.
`
`Microsoft’s motion does not attempt to identify any prejudice to Microsoft
`
`that joinder will avoid. Microsoft’s failure to allege (much less prove) joinder is
`
`necessary to avoid prejudice is alone enough reason to deny Microsoft’s motion
`
`under Proppant.
`
`Microsoft argues joinder is necessary because Uniloc filed multiple suits on
`
`the same patent but identifies no action by Uniloc in co-pending litigation that makes
`
`joinder necessary to avoid prejudice to Microsoft. The mere fact that Microsoft and
`
`Apple were sued on the same patent in separate suits does not mean Microsoft will
`
`be prejudiced unless its IPRs are joined to the Apple IPRs. Further, Uniloc’s second
`
`
`
`
`6
`
`

`

`IPR2019-00744
`U.S. Patent No. 7,167,487
`
`
`
`complaint against Microsoft for infringement of the ’487 patent was not an action in
`
`co-pending litigation that created a need for Microsoft to seek joinder. Uniloc filed
`
`its first complaint against Microsoft for infringement of the ’487 patent on July 24,
`
`2018. It withdrew the ’487 patent from that suit in August 2018. Microsoft filed its
`
`petitions against the ’487 patent on March 4, 2019. One day later, Uniloc filed its
`
`second complaint against Microsoft on the ’487 patent. The July 2018 and March
`
`2019 complaints are identical with respect to the ’487 patent.3 Thus, the March 2019
`
`complaint did not create any change in circumstance necessitating joinder. And
`
`indeed, Microsoft did not respond to the March 5, 2019 complaint by seeking
`
`joinder.
`
`Microsoft’s real reason for seeking joinder is evident from the nature and
`
`timing of its petitions and joinder motions. In March 2019, Microsoft filed petitions
`
`that sought to distinguish Microsoft’s IPRs from Apple’s IPRs, insisting Microsoft
`
`presented the art in a different light and relied on art not cited by Apple. This was a
`
`transparent attempt to guard against denial if the Apple’s IPRs were denied. Four
`
`months later, after Uniloc’s preliminary responses identified omissions in
`
`Microsoft’s petitions and after the Board instituted trial in the Apple IPRs, Microsoft
`
`made an about face and requested joinder. Microsoft’s desire for joinder was
`
`prompted by the institution of the Apple IPRs and concerns about omissions in
`
`
`3 See EX1027 (original complaint filed in Uniloc 2017 LLC et al. v Microsoft
`Corporation, Case No. 8:18-cv-01279 (C.D. Cal.)); EX1028 (original complaint
`filed in Uniloc 2017 LLC v. Microsoft Corporation, Case No. 8:19-cv-
`00428 (C.D. Cal.)).
`
`7
`
`
`
`
`

`

`IPR2019-00744
`U.S. Patent No. 7,167,487
`
`
`
`Microsoft’s petitions identified by Uniloc’s preliminary responses, not any change
`
`in circumstances caused by actions of Uniloc in co-pending litigation. Indeed,
`
`Microsoft uses its motions for joinder to indirectly reply to Uniloc’s patent owner
`
`responses.4 This is precisely the type of circumstance Proppant would not support
`
`joinder of new issues. Proppant, Case IPR2018-00914, Paper 38, p. 4 (“the Board
`
`does not generally expect fairness and prejudice concerns to be implicated by, for
`
`example, the mistakes or omissions of a petitioner”).
`
`Microsoft chose to file its own defective petitions fully aware of the pending
`
`Apple IPRs. It made a deliberate decision to distinguish its petitions from the Apple
`
`petitions. If Microsoft’s petitions are denied as they should be, that will be a result
`
`of Microsoft’s own mistakes and omissions. There is no prejudice in requiring
`
`Microsoft to accept the consequence of its own strategy.
`
`B.
`
`The General Plastic factors weigh against institution and joinder.
`
`Section 315(c) requires that a petition accompanying a request for
`
`joinder “warrants the institution of an inter partes review under section 314.”
`
`35 U.S.C. § 315(c). In General Plastic Industrial Co., Ltd. v. Canon Kabushiki
`
`Kaisha, Case IPR2016-01357, slip op. at 15–16 (PTAB Sept. 6, 2017) (Paper 19)
`
`(precedential), the Board articulated a non-exhaustive list of factors to be considered
`
`in determining whether to exercise discretion under § 314(a) to deny a petition that
`
`
`4 Uniloc’s patent owner responses explain Microsoft’s petitions should be denied
`under Liberty Mutual because it fails to explain why its new references should be
`considered. Microsoft’s joinder motion attempts to cure this deficiency, spending
`significant time arguing why its new reference should be considered in addition to
`the references shared with the Apple IPR.
`8
`
`
`
`
`

`

`IPR2019-00744
`U.S. Patent No. 7,167,487
`
`
`
`challenges the same patent as a previous petition. Application of the General Plastic
`
`factors is not limited solely to instances when multiple petitions are filed by the same
`
`petitioner. Valve Corp. v. Elec. Scripting Prods., Inc., Case IPR2019-00062, -00063,
`
`-00084, Paper 11, p. 2 (Apr. 2, 2019) (designated: May 7, 2019). Rather, when
`
`different petitioners challenge the same patent, the Board considers any relationship
`
`between those petitioners when weighing the General Plastic factors. Id.
`
`Here, the first General Plastic factor weighs against institution because Apple
`
`previously filed two petitions directed to the same claims of the same patent. Apple
`
`and Microsoft were defendants in district court litigation involving the same patent
`
`owner and same patent. As in Valve Corporation, here the complete overlap in the
`
`challenged claims and the significant relationship between Apple and Microsoft with
`
`respect to the ’487 patent weigh against institution and joinder.
`
`The second factor also weighs against institution and joinder of the Microsoft
`
`petitions because the new art Microsoft seeks to add could have been found and
`
`asserted in the Apple IPRs with reasonable diligence. Microsoft’s joinder motions
`
`argue the TS23.107 reference “is not some stray reference, but instead integrates
`
`cleanly with the art presented by the Apple IPR[s] and is admitted by the ’487 patent
`
`as highly relevant to minimum bit rate characteristics.” See IPR2019-00744, Paper
`
`7, p. 7; IPR2019-00745, Paper 7, p. 7.
`
`The third factor weighs against institution and joinder because, at the time
`
`Microsoft filed its joinder motions, Microsoft had already received Uniloc’s
`
`preliminary responses. The third factor is directed to “Petitioner’s potential benefit
`
`
`
`
`9
`
`

`

`IPR2019-00744
`U.S. Patent No. 7,167,487
`
`
`
`from receiving and having the opportunity to study Patent Owner’s Preliminary
`
`Response, as well as [the Board’s] institution decisions on the first-filed petitions,
`
`prior to filing follow-on petitions.” Valve Corp., Case IPR2019-00062, -00063, -
`
`00084, Paper 11, p. 12. While Microsoft did not have the benefit of the Board’s
`
`institution decisions in the Apple IPRs or Uniloc’s preliminary responses when it
`
`filed its petitions, Microsoft is now seeking to take advantage of the institution
`
`decisions and the preliminary responses in its joinder motions. Microsoft’s joinder
`
`motions should not be allowed benefit from the preliminary responses and the
`
`institution decisions.
`
`Factors four and five weigh against institution and joinder because Microsoft
`
`provides no adequate explanation for the time elapsed between the filing of the
`
`Apple IPRs and Microsoft’s joinder motions, which seek to add new art to the Apple
`
`IPRs. The TS23.107 reference was known sometime before Microsoft filed its
`
`petitions on March 4, 2019. Microsoft offers no explanation for waiting until July
`
`to seek to add the reference to the Apple IPRs.
`
`Factors six and seven weigh against institution and joinder because adding
`
`Microsoft’s references and arguments to the Apple IPRs will burden the Board’s
`
`finite resources and hinder the Board’s ability to issue a final determination not later
`
`than 1 year after the date of institution. In Valve, the Board found these factors
`
`weighed against institution because Valve waited until after institution to file not
`
`one, but three additional petitions. Here, although Microsoft filed its petition before
`
`the Apple IPRs were instituted, Microsoft waited until after the institution decisions
`
`
`
`
`10
`
`

`

`IPR2019-00744
`U.S. Patent No. 7,167,487
`
`
`
`in the Apple IPRs to seek joinder of new art to the Apple IPRs. Microsoft’s attempt
`
`to take two bites at the apple (by distinguishing its petitions before institution of the
`
`Apple IPRs but then minimizing the differences after) implicates the same efficiency
`
`concerns underpinning General Plastic that were implicated in Valve Corporation.
`
`C. Microsoft is not taking an understudy role.
`
`Joinder should also be denied because Microsoft admits it is not taking on a
`
`true understudy role. Because Microsoft seeks to add a reference to each ground, it
`
`cannot take on a true understudy rule. Microsoft knows this, offering only to take a
`
`“largely” understudy role and “deferring to Apple” only where issues overlap.
`
`Microsoft clearly intends to take a lead role regarding the new art it seeks to join.
`
`D. Microsoft’s motions admit the cumulative nature of its petitions.
`
` Finally, Microsoft’s joinder motions admit the cumulative nature of
`
`Microsoft’s petitions. As explained in Uniloc’s preliminary responses, the
`
`cumulative nature of Microsoft’s petitions is grounds for the Board to deny
`
`institution. Doing so will promote efficiency and discourage serial challenges to a
`
`patent. Microsoft would have the Board compound the problem of serial challenges
`
`to the patent by joining new issues to the already-instituted Apple IPRs. Doing so
`
`will only prejudice Uniloc further.
`
`III. CONCLUSION
`
`For the foregoing reasons, joinder should be denied.
`
`
`
`11
`
`
`
`
`
`
`

`

`
`Date: August 2, 2019
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`IPR2019-00744
`U.S. Patent No. 7,167,487
`
`By: Brett A. Mangrum
`Brett A. Mangrum
`Attorney for Patent Owner
`Reg. No. 64,783
`
`Ryan Loveless
`Attorney for Patent Owner
`Reg. No. 51,970
`
`
`CERTIFICATE OF SERVICE
`
`
`
`Pursuant to 37 C.F.R. §§ 42.6(e), we certify that we served an electronic
`
`copy of the foregoing document along with any accompanying exhibits via the
`
`Patent Review Processing System (PRPS) and email to Petitioner’s counsel of
`
`record at the following address:
`
`
`
`Lead Counsel
`
`Back Up
`Counsel
`
`Back Up
`Counsel
`
`Back Up
`Counsel
`
`Back Up
`Counsel
`
`
`
`
`
`
`Andrew M.
`Mason
`
`Todd M.
`Siegel
`
`Joseph T.
`Jakubek
`
`64,034
`
`andrew.mason@klarquist.com
`
`73,232
`
`todd.siegel@klarquist.com
`
`34,190
`
`joseph.jakubek@klarquist.com
`
`John Lunsford
`
`67,185
`
`john.lunsford@klarquist.com
`
`John D.
`Vandenberg
`
`31,312
`
`john.vandenberg@klarquist.com
`
`12
`
`

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