throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`____________________________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`____________________________________
`
`MICROSOFT CORPORATION,
`Petitioner
`
`v.
`
`VIRNETX, INC.,
`Patent Owner
`
`____________________________________
`
`U.S. Patent No. 6,502,135
`
`(Trial No. _____________)
`
`____________________________________
`
`
`
`MOTION FOR JOINDER UNDER 35 U.S.C. § 315(c) AND
`37 C.F.R. § 42.122(b)
`
`
`
`
`
`
`
`
`Mail Stop Patent Board
`Patent Trial and Appeal Board
`U.S. Patent and Trademark Office
`P.O. Box 1450
`Alexandria, VA 22313-
`
`

`
`
`
`
`Attorney Docket No. 38868-0003IP1
`
`IPR of U.S. Patent No. 6,502,135
`
`TABLE OF CONTENTS
`
`STATEMENT OF RELIEF REQUESTED ..................................................................................... 2 
`I. 
`BACKGROUND AND RELATED PROCEEDINGS ................................................................. 4 
`II. 
`THE BOARD HAS DISCRETION TO JOIN THE INSTANT IPR WITH THE RPX IPR
`III. 
`UPON ITS INSTITUTION ........................................................................................................................ 6 
`THE BOARD SHOULD EXERCISE ITS DISCRETION BY GRANTING JOINDER
`IV. 
`UNDER THE PRESENT CIRCUMSTANCES ....................................................................................... 7 
`A.  The grounds of unpatentability raised in Microsoft’s Petition are a subset of those at issue in
`the RPX IPR ............................................................................................................................................ 7 
`B.  Joinder is appropriate .................................................................................................................... 8 
`C.  Joinder will not affect timely completion of the RPX IPR .......................................................... 9 
`D.  Briefing and discovery can be simplified .................................................................................... 10 
`V.  CONCLUSION ................................................................................................................................. 11 
`
`
`
`
`

`
`
`
`1
`
`

`
`
`
`
`I.
`
`Attorney Docket No. 38868-0003IP1
`
`IPR of U.S. Patent No. 6,502,135
`
`STATEMENT OF RELIEF REQUESTED
`
`Microsoft Corporation (“Microsoft”) submits concurrently herewith a
`
`Petition for inter partes review of claims 1, 3, 4, 7, 8, 10, 12, and 13 of U.S. Patent
`
`No. 6,502,135 (“the ‘135 patent”) (“Petition”). The Petition is being filed within
`
`one year of service by VirnetX, Inc. (“VirnetX”) of a complaint against Microsoft
`
`alleging infringement of the ‘135 Patent.1 As such, Microsoft respectfully submits
`
`that, for at least the reasons outlined in the Petition, 35 U.S.C. § 315(b) is
`
`inapplicable and does not bar institution of the inter partes review of the ‘135
`
`patent that is requested in Microsoft’s Petition.
`
`                                                            
`1 The ’135 patent is the subject of Civ. Act. No. 6:13-cv-00351-LED (E.D. Tex),
`
`which was filed April 22, 2013 (“the 2013 VirnetX litigation”). The complaint in
`
`the 2013 VirnetX litigation was served on April 23, 2013. VirnetX has also
`
`asserted the ‘135 patent against Microsoft in two prior instances: VirnetX, Inc. v.
`
`Microsft Corporation (Case No. 6:07-cv-80 (E.D. Tex.), filed February 2007, and
`
`VirnetX, Inc. v. Microsoft (Case No. 6:10-cv-94 (E.D. Tex.), filed March 2010.
`
`These prior litigations were dismissed pursuant to a settlement agreement that
`
`expressly preserved Microsoft’s ability to later challenge the validity of the
`
`patents-in-suit.
`
`
`

`
`2
`
`

`
`
`
`
`Attorney Docket No. 38868-0003IP1
`
`IPR of U.S. Patent No. 6,502,135
`
`If, however, the Board decides that 35 U.S.C. § 315(b) is applicable and bars
`
`Microsoft from instituting an inter partes review of the ‘135 patent, Microsoft
`
`moves for joinder, pursuant to 35 U.S.C. § 315(c) and 37 C.F.R. § 42.122(b), with
`
`respect to the pending inter partes review designated as IPR2014-00171 (“the RPX
`
`IPR”) and requested by RPX Corporation (“RPX”), upon institution of the RPX
`
`IPR.
`
`In accordance with the Board’s Representative Order identifying matters to
`
`be addressed in a motion for joinder (IPR2013-00004, Paper No. 15)2, Microsoft
`
`submits that: (1) joinder is appropriate because it will promote efficient
`
`determination of the validity/invalidity of the ‘135 patent without prejudice to the
`
`existing parties; (2) the grounds of unpatentability raised in Microsoft’s Petition
`
`are a subset of those at issue in the RPX IPR; (3) joinder would not affect the
`
`timely completion of that proceeding; and (4) Microsoft is willing to accept
`
`reasonable restrictions on briefing and discovery that will minimize the burden of
`                                                            
`2 A motion for joinder should: (1) set forth the 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 Corporation v. Softview LLC,
`
`IPR2013-00004, Paper No. 15 at 4 (April 24, 2013).
`

`
`3
`
`

`
`Attorney Docket No. 38868-0003IP1
`
`
`IPR of U.S. Patent No. 6,502,135
`
`
`joinder on the Board and on the parties. Moreover, absent joinder, Microsoft’s
`
`interests will not be fully and fairly represented in the RPX IPR.
`
`Accordingly, if the Board declines to institute the inter partes review of the
`
`‘135 patent requested in the attached Petition, Microsoft respectfully asks the
`
`Board to grant Microsoft joinder.
`
`
`
`II. BACKGROUND AND RELATED PROCEEDINGS
`
`VirnetX has asserted varying sets of claims of the ‘135 patent against
`
`various defendants in numerous law suits.3 Microsoft has been targeted in three (3)
`
`of those law suits, most recently in Civ. Act. No. 6:13-cv-00351-LED (E.D. Tex),
`
`filed April 22, 2013 (“the 2013 VirnetX litigation”).4
`
`                                                            
`3 The ’135 patent is the subject of the following ongoing civil actions: (i) Civ. Act.
`
`No. 6:13-cv-00211-LED (E.D. Tex.), filed February 26, 2013; (ii) Civ. Act. No.
`
`6:12-cv-00855-LED (E.D. Tex.), filed November 6, 2012; (iii) Civ. Act. No. 6:10-
`
`cv-00417-LED (E.D. Tex.), filed August 11, 2010; (iv) Civ. Act. No. 6:11-cv-
`
`00018-LED (E.D. Tex), (iv) Civ. Act. No. 6:13-cv-00351-LED (E.D. Tex), filed
`
`April 22, 2013 (“the 2013 VirnetX litigation”); (v) Civ. Act. No. 6:10-cv-00094
`
`(E.D. Tex); and (vi) Civ. Act. No. 6:07-cv-00080 (E.D. Tex).
`
`4 See FN 1 of the instant motion, above at page 2.  
`

`
`4
`
`

`
`
`
`
`Attorney Docket No. 38868-0003IP1
`
`IPR of U.S. Patent No. 6,502,135
`
`The ’135 patent is the subject of two petitions for inter partes review filed
`
`by RPX, including the RPX IPR and a separate petition which has been designated
`
`IPR2014-00172. The ’135 patent is also the subject of merged inter partes
`
`reexamination nos. 95/001,679 and 95/001,682, in which all claims of the ‘135
`
`patent have been non-finally rejected on multiple grounds of anticipation and
`
`obviousness.
`
`In the Petition accompanying the instant motion for joinder, Microsoft
`
`requests cancelation of claims 1, 3, 4, 7, 8, 10, 12, and 13 of the ‘135 patent, and
`
`proposes the following grounds of rejection:
`
`1) Claims 1, 3, 4, 7, 8, 10, 12, and 13 are anticipated under
`§ 102(b) by Aventail Connect v 3.01/2.5 Administrator’s
`Guide (“Aventail”);
`2) Claims 1, 3, 4, 7, 8, 10, 12, and 13 are obvious under §
`103 based on Aventail;
`3) Claim 4 is obvious under § 103 over Aventail in view of
`Mockapetris, P., RFC 1035, “Domain Names –
`Implementation and Specification,” November 1987
`(“RFC 1035”);
`4) Claims 1, 3, 4, 7, 8, 10, and 12 are anticipated under §
`102(b) by Takahiro Kiuchi and Shigekoto Kaihara, “C-
`HTTP - The Development of a Secure, Closed HTTP-
`based Network on the Internet,” the Proceedings of
`SNDSS 1996 (“Kiuchi”); and
`5) Claim 8 is obvious under § 103 over Kiuchi in view of
`Mockapetris, P., RFC 1034, “Domain Names – Concepts
`and Facilities,” November 1987 (“RFC 1034”).
`
`
`5
`
`
`

`
`

`
`
`
`
`
`
`
`Attorney Docket No. 38868-0003IP1
`IPR of U.S. Patent No. 6,502,135
`
`
`III. THE BOARD HAS DISCRETION TO JOIN THE INSTANT IPR
`WITH THE RPX IPR UPON ITS INSTITUTION
`
`The Board, acting on behalf of the Director, has the discretion to grant
`
`joinder to an inter partes review to an entity that properly files, no later than one
`
`month after the institution of the inter partes review, a petition for a like
`
`proceeding. See 35 U.S.C. § 315(c) (“the Director, in his or her discretion, may
`
`join as a party to [an instituted] inter partes review any person who properly files a
`
`petition under section 311”); 37 C.F.R. § 42.122(b) (“Any request for joinder must
`
`be filed, as a motion under § 42.22, no later than one month after the institution
`
`date of any inter partes review for which joinder is requested”).
`
`Because the instant motion for joinder is being submitted prior to the
`
`institution of the RPX IPR, it is timely under 35 U.S.C. § 315 and 37 C.F.R. §
`
`42.122(b). Because Microsoft has paid the fee for the accompanying Petition that
`
`is prescribed by the Director and has requested cancelation of claims of the ‘135
`
`patent only on grounds that can be raised under 35 U.S.C. §§ 102 and 103, the
`
`Petition has been properly filed. See 35 U.S.C. § 311 (“The Director shall
`
`establish . . . fees to be paid by the person requesting the review . . . A petitioner . .
`
`. may request to cancel as unpatentable 1 or more claims of a patent only on a
`
`ground that could be raised under section 102 or 103”). Accordingly, under the
`

`
`6
`
`

`
`Attorney Docket No. 38868-0003IP1
`
`
`IPR of U.S. Patent No. 6,502,135
`
`
`applicable statutes and regulations, the Board has discretion to grant Microsoft
`
`joinder to the RPX IPR.
`
`
`
`IV. THE BOARD SHOULD EXERCISE ITS DISCRETION BY
`GRANTING JOINDER UNDER THE PRESENT
`CIRCUMSTANCES
`
`Each of the four factors identified in the Board’s representative order on
`
`joinder favor joinder under the present circumstances. These factors are
`
`individually addressed under separate headings below.5
`
`A. The grounds of unpatentability raised in Microsoft’s Petition are
`a subset of those at issue in the RPX IPR
`
`In the Petition accompanying the instant motion for joinder, Microsoft
`
`requests cancelation of claims 1, 3, 4, 7, 8, 10, 12, and 13 of the ‘135 patent on
`
`grounds that are a subset of the grounds that were proposed by RPX in the RPX
`
`IPR.6 Microsoft acknowledges that the declaration in the present petition (“the
`
`                                                            
`5 See FN2 of the instant motion, above at page 3, listing the four factors detailed in
`
`the Board’s representative order on joinder, Kyocera Corporation v. Softview LLC,
`
`IPR2013-00004, Paper No. 15 at 4 (April 24, 2013). 
`
`6 Compare the five grounds of rejection proposed by Microsoft, listed above at
`
`page 5, with the grounds of rejection requested by RPX in RPX Corporation, v.
`

`
`7
`
`

`
`Attorney Docket No. 38868-0003IP1
`
`
`IPR of U.S. Patent No. 6,502,135
`
`
`Guerin Declaration”) is from a different expert than the one in the RPX IPR, but
`
`submits that submission of this declaration was necessitated by the lack of
`
`relationship between Microsoft and the primary declarant in the RPX IPR, Michael
`
`Fratto. Moreover, Microsoft presents the Guerin Declaration for the purposes of
`
`preserving its ability to rely upon expert evidence in case RPX discontinues its
`
`participation in the IPR. Nevertheless, since the petition submitted with this
`
`motion is directed to a subset of grounds in the RPX petition, the Guerin
`
`Declaration is similarly directed to a subset of grounds in the RPX IPR and
`
`supports conclusions already set forth in the RPX IPR. Accordingly, joinder to the
`
`pending RPX IPR would therefore not impact that proceeding’s substantive
`
`complexity.
`
`B. Joinder is appropriate
`
`Absent joinder, Microsoft’s interests will not be fully and fairly represented
`
`in the RPX IPR. Moreover, because the RPX IPR has not yet been instituted,
`
`joinder to the RPX IPR will neither slow nor otherwise prejudice that proceeding
`
`or the existing parties, and joinder to the RPX IPR would promote an efficient and
`
`comprehensive determination of the validity/invalidity of the ’135 patent.
`
`                                                                                                                                                                                                
`VirnetX, Inc. and Science Application International Corporation, IPR2014-00171,
`
`Paper No. 1 (November 20, 2013).
`

`
`8
`
`

`
`
`
`
`
`
`
`
`
`Attorney Docket No. 38868-0003IP1
`IPR of U.S. Patent No. 6,502,135
`
`C. Joinder will not affect timely completion of the RPX IPR
`
`Because the instant motion for joinder is being presented prior to the
`
`institution of the RPX IPR, the Board will have no need to modify a previously-
`
`existing schedule, and will instead have the opportunity to establish a schedule in
`
`the RPX IPR that can efficiently drive that proceeding forward, while
`
`accommodating the needs of each party. For example, the Patent Owner’s
`
`Preliminary Response period can be reasonably shortened since the grounds in the
`
`present petition are a subset of those in the RPX IPR. Similarly, Microsoft is
`
`willing to accept reasonable reductions in the time periods applicable to its filings.
`
`Moreover, to the extent needed or desired, the Board has the power, under 35
`
`U.S.C. 316(a)(11) to adjust the one-year deadline in the case of joinder.
`
`As such, any burdens of joinder on the Board and on the parties can be
`
`minimized, if not altogether avoided, and joinder can be expected to have little or
`
`no impact on the RPX IPR’s timely completion. Cf. Sony Corporation of America
`
`and Hewlett-Packard Co. v. Network-1 Security Solutions, Inc., IPR2013-00495 ,
`
`Paper No. 13 at 5 (September 13, 2013) (finding that the Board’s ability to
`
`complete the trial in one year would not be impacted by joinder, because joinder
`
`would raise no substantive issues that were not already before the Board).
`
`
`

`
`9
`
`

`
`
`
`
`
`
`
`
`
`Attorney Docket No. 38868-0003IP1
`IPR of U.S. Patent No. 6,502,135
`
`D. Briefing and discovery can be simplified
`
`The grounds of unpatentability for the ‘135 patent proposed by Microsoft are
`
`a subset of those raised by RPX. As such, Microsoft envisions few, if any,
`
`differences in position between Microsoft and RPX. Moreover, were differences
`
`in position between Microsoft and RPX to arise, those differences would center
`
`around the same references and issues, and would therefore be limited relative to a
`
`situation in which a joined party proposed wholly new rejections and art. Thus,
`
`Microsoft predicts that little, if any, complexity will be added to briefing and
`
`discovery if the Board grants Microsoft joinder to the RPX IPR.
`
`Moreover, Microsoft respectfully submits that briefing and discovery can be
`
`streamlined to minimize any impact to the schedule or to the volume of materials
`
`to be submitted to the Board. To this end, if the Board deems it appropriate, and if
`
`Microsoft is permitted to state its positions on the record, Microsoft is willing to
`
`entertain, for example, briefing and discovery procedures similar to those ordered
`
`by the Board in IPR2013-00256, which included consolidated filings. See
`
`Motorola Mobility LLC v. Softview LLC, IPR2013-00256, Paper No. 10 at 9 (June
`
`10
`
`20, 2013).
`
`
`

`
`

`
`
`
`
`
`V. CONCLUSION
`
`
`
`
`Attorney Docket No. 38868-0003IP1
`IPR of U.S. Patent No. 6,502,135
`
`Microsoft respectfully submits that, for at least the reasons presented above,
`
`joinder of Microsoft to the RPX IPR would be warranted if the Board declines to
`
`institute the inter partes review of the ‘135 patent that is requested in Microsoft’s
`
`Petition. Accordingly, Microsoft requests that, if the inter partes review of the
`
`‘135 patent that is petitioned for by Microsoft is not instituted, the Board grant
`
`Microsoft joinder to the RPX IPR.
`
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`
`
`
`/W. Karl Renner/
`
`W. Karl Renner, Reg. No. 41,265
`Fish & Richardson P.C.
`P.O. Box 1022
`Minneapolis, MN 55440-1022
`T: 202-626-6447
`F: 202-783-2331
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Dated: March 31, 2014
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`
`11
`
`

`
`
`
`
`Attorney Docket No. 38868-0003IP1
`IPR of U.S. Patent No. 6,502,135
`
`
`
`
`CERTIFICATE OF SERVICE
`Pursuant to 37 CFR §§ 42.6(e)(4)(i) et seq. and 42.105(b), the undersigned
`certifies that on March 31, 2014, a complete and entire copy of this Petition for
`Inter Partes Review, Motion for Joinder, and all supporting exhibits were provided
`via FedEx, to the Patent Owner by serving the correspondence address of record as
`follows:
`
`Finnegan, Henderson, Farabow
`Garrett & Dunner LLP
`901 New York Avenue, NW
`Washington, DC 20001
`
`
`
`
`
`/Edward G. Faeth/
`
`Edward G. Faeth
`Fish & Richardson P.C.
`60 South Sixth Street, Suite 3200
`Minneapolis, MN 55402
`(202) 626-6420
`
`
`
`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