throbber

`
`
`
`Case No. IPR2014-00173
`
`
`
`Paper No.
`Filed: January 27, 2014
`
`
`Filed on behalf of: VirnetX Inc.
`By:
`Joseph E. Palys
`
`Naveen Modi
`Finnegan, Henderson, Farabow,
` Garrett & Dunner, L.L.P.
`11955 Freedom Drive
`Reston, VA 20190-5675
`Telephone: 571-203-2700
`Facsimile: 202-408-4400
`E-mail: joseph.palys@finnegan.com
`
` naveen.modi@finnegan.com
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`RPX CORPORATION
`Petitioner
`v.
`VIRNETX INC.
`Patent Owner
`
`
`
`Case IPR2014-00173
`Patent 7,490,151
`
`
`
`
`
`Patent Owner’s Motion for Discovery
`from RPX Corporation and Apple, Inc.
`
`
`
`
`
`
`
`
`
`
`

`

`
`
`
`
`Case No. IPR2014-00173
`
`Table of Contents
`
`
`I.
`Precise Relief Requested ................................................................................. 1
`Factual Background ......................................................................................... 1
`II.
`III. Reasons for the Relief Requested .................................................................... 3
`IV. Conclusion ....................................................................................................... 7
`
`
`
`
`
`i
`
`
`

`

`
`
`
`
`Case No. IPR2014-00173
`
`Table of Authorities
`
`Statutes
`
`35 U.S.C. § 312(a)(2) ............................................................................................. 3, 6
`
`35 U.S.C. § 315(b) ................................................................................................. 3, 6
`
`35 U.S.C. § 316(a)(5) ................................................................................................. 3
`
`Rules
`
`37 C.F.R. § 42.51(b)(2) .............................................................................................. 1
`
`37 C.F.R. § 42.52(a) ................................................................................................... 1
`
`Cases
`
`Asahi Glass Co. v. Toledo Eng’g Co., 505 F. Supp. 2d 423
` (N.D. Ohio 2007) .................................................................................................. 5
`
`In re Echostar Comms. Corp., 448 F.3d 1294, 1301 (Fed. Cir. 2006) ...................... 5
`
`Garmin Int’l, Inc. v. Cuozzo Speed Techs. LLC, IPR2012-00001, Paper 26
`(P.T.A.B. March 5, 2013) ............................................................................ 3, 7
`
`In re Guan, Control No. 95/001,045, Decision Vacating Filing Date
`(USPTO Aug. 25, 2008) .................................................................................. 4
`
`Phelps v. Hamilton, 122 F.3d 1309 (10th Cir. 1997) ................................................ 5
`
`Other
`
`“Office Patent Trial Practice Guide,” 77 Federal Register 157
`(Aug. 14, 2012), pp. 48756-773 .................................................................. 4, 6
`
`ii
`
`
`

`

`
`
`
`
`Case No. IPR2014-00173
`
`I.
`
`Precise Relief Requested
`VirnetX requests that the Board authorize the discovery from RPX and
`
`Apple contained in Exhibits 2002-2005. See 37 C.F.R. §§ 42.51(b)(2), 42.52(a).
`
`II.
`
`Factual Background
`RPX provides defensive patent services to its clients. It acts “as an
`
`extension of a client’s in-house legal team” and “as a trusted intermediary,” and
`
`when litigation arises, “selectively clear[s its] clients from the suit.” (Exs. 2006,
`
`2007 at 3, 2008.) To fund these services, RPX collects fees from its clients.
`
`(Ex. 2007 at 9.)
`
`at 1.)
`
`(Id. at 1-2; see also Ex. 2001 at 64:15-18.)
`
` (Ex. 1073
`
`
`
`
`
`
`
`, RPX
`
`petitioned for IPR of four VirnetX patents Apple was found to infringe.
`
`(Ex. 2009.) RPX contends the grounds in its petitions are “substantially identical”
`
`to the time-barred, non-instituted Apple petitions. (Pet. at 6; Exs. 2010-2016.) But
`
`this is not an instance where the petitions were merely copied or modified from the
`
`public record.
`
`
`
`
`
`
`
`
`
`

`

`
`
`
`
`Case No. IPR2014-00173
`
` (Ex. 2001 at 7:11-18; Ex. 1074 at 8:1-5, 25:13-14.) RPX also
`
`obtained access to Apple’s alleged expert, Michael Fratto, who submitted
`
`declarations with the Apple and RPX petitions. (See, e.g., Exs. 1003 and 2017.)
`
`RPX has also advanced Apple’s interests in these proceedings. Shortly after
`
`the RPX petitions were filed, it came to light that the petitions neglected to
`
`challenge three claims Apple was found to infringe. Over the next two days,
`
`corrected petitions were filed solely to add new challenges to the infringed claims,
`
`much to Apple’s benefit. (See Ex. 2009; Ex. 1074 at 16:15-17:11.) RPX also
`
`requested that these proceedings be expedited, but RPX makes no products that
`
`could infringe VirnetX’s patents. The urgency must be so RPX can “selectively
`
`clear” Apple from its suit with VirnetX.
`
`, throughout these proceedings, they
`
`have attempted to give the impression they are operating independently to avoid
`
`real-party-in-interest (“RPI”) and privity issues. For example, RPX and Apple
`
`took care not to share with the Board the relationship between RPX and Apple’s
`
`counsel. (See Ex. 2001 at 69:6-71:4, demonstrating how both Apple and RPX
`
`refused to answer the Board’s question about whether Apple had provided any
`
`assistance regarding the RPX petitions.) It was not until VirnetX mentioned the
`
`metadata in the RPX petitions (Ex. 2001 at 71:11-22), which demonstrates that
`
`Apple’s counsel was involved with the RPX petitions (Ex. 1074 at 13:12-18:11),
`
`2
`
`

`

`
`
`
`
`Case No. IPR2014-00173
`
`that RPX requested another call with the Board to explain that
`
`
`
` (See id. at 6:13-9:13.)
`
`III. Reasons for the Relief Requested
`VirnetX moves to take additional discovery from RPX and Apple.
`
`VirnetX’s discovery requests are “necessary in the interest of justice,” 35 U.S.C.
`
`§ 316(a)(5), and meet each of the factors set forth in Garmin Int’l, Inc. v. Cuozzo
`
`Speed Techs. LLC, IPR2012-00001, Paper 26, as explained below.
`
`More Than a Possibility and Mere Allegation: VirnetX’s discovery
`
`narrowly focuses on the nature and scope of the relationship between Apple and
`
`RPX as it pertains to RPX’s IPR petitions. (See Exs. 2002-2005.) The discovery
`
`is based on the known aspects of
`
` that are
`
`discussed above (more than a possibility and mere allegation), and is calculated to
`
`render useful information that is favorable to VirnetX’s contention that RPX’s
`
`petitions should be dismissed under 35 U.S.C. § 312(a)(2) for failing to identify
`
`Apple as an RPI, and/or are time-barred under 35 U.S.C. § 315(b) because RPI’s
`
`privy Apple was sued more than a year before RPX filed its petitions. See Garmin,
`
`IPR2012-00001, Paper 26 at 7.
`
`In particular, the requests seek:
`
`3
`
`
`
`
`
`
`
`

`

`
`
`
`
`Case No. IPR2014-00173
`
`; communications
`
`and payments between Apple and RPX regarding the RPX IPRs (useful at least to
`
`show Apple’s involvement and funding of the RPX IPRs);
`
`
`
`
`
`
`
`; communications about the RPX IPRs
`
`between Apple and RPX, Sidley Austin, Howison & Arnott, and Ashe PC (useful
`
`at least to show the nature and degree of Apple’s influence over the RPX IPRs);
`
`and invoices, payments, agreements, communications between RPX and Sidley
`
`Austin, and number of hours spent by various attorneys (useful at least to show the
`
`nature and scope of Sidley’s representation of RPX and who paid for the IPRs).
`
`Each discovery request seeks information related to the factors concerning
`
`RPI and privity set forth in the Trial Practice Guide (“TPG”) and In re Guan. See
`
`TPG at 48759-60; In re Guan, Control No. 95/001,045, Decision Vacating Filing
`
`Date (Aug. 25, 2008) at 8. And while the Board initially declined to allow
`
`additional discovery based on RPX’s representations that they alone control these
`
`proceedings and pay for them (see Ex. 2001 at 73:14-74:10), “sole discretion,”
`
`“control,” and funding are only portions of the RPI/privity inquiry. See Guan;
`
`TPG at 48759-60. Moreover, the facts show otherwise and VirnetX should be
`
`allowed discovery into the selective information provided by RPX and Apple.
`
`4
`
`

`

`
`
`
`
`Case No. IPR2014-00173
`
`In addition, just because RPX and Apple share counsel does not render the
`
`discovery sought less useful. (See Ex. 1074 at 26:3-14.) Indeed, “the existence of
`
`shared counsel supports a finding of privity where other factors present suggest
`
`that a unique relationship exists between the two parties.” Asahi Glass Co. v.
`
`Toledo Eng’g Co., 505 F. Supp. 2d 423, 436 (N.D. Ohio 2007); see also Phelps v.
`
`Hamilton, 122 F.3d 1309, 1319 (10th Cir. 1997) (“control need not be exercised
`
`directly by the non-litigating party. It is sufficient that the choices were in the
`
`hands of counsel responsible to the controlling person; moreover, the requisite
`
`opportunity may exist even when it is shared with other persons.”) (internal
`
`quotations omitted). If it were not a factor, one has to wonder why RPX and Apple
`
`were not forthcoming about sharing counsel in the RPX petitions or the
`
`teleconference of January 8, 2014.
`
`Moreover, RPX and Apple should not be able to object on the basis of any
`
`privilege, especially when they have selectively chosen to disclose certain
`
`information while withholding other information in the RPX petitions and during
`
`the teleconferences. See In re Echostar Comms. Corp., 448 F.3d 1294, 1301 (Fed.
`
`Cir. 2006). It would be extremely prejudicial to VirnetX to allow RPX and Apple
`
`to selectively offer information and not allow VirnetX to seek additional
`
`information. And even if RPX or Apple were to claim privilege, the appropriate
`
`response would be to provide redacted documents and a privilege log.
`
`5
`
`

`

`
`
`
`
`Case No. IPR2014-00173
`
`Litigation Positions and Underlying Basis: VirnetX and RPX are not in
`
`district-court litigation, and none of VirnetX’s requests implicate district-court
`
`litigation positions or strategies of Apple or RPX. VirnetX also does not seek to
`
`prematurely learn RPX’s and Apple’s positions in these IPRs.
`
` Proper
`
`identification of RPIs/privies is a threshold issue under 35 U.S.C. §§ 312(a)(2) and
`
`315(b), so addressing the issue early is warranted. See TPG at 48759.
`
`Ability to Generate Equivalent Information by Other Means: VirnetX’s
`
`discovery requests narrowly target information about
`
`
`
`that is not publicly available. Although VirnetX served subpoenas on RPX in
`
`district court litigations to seek information for those cases, RPX refuses to
`
`produce discovery there. (Exs. 2018 and 2019.) If RPX is compelled to provide
`
`discovery in the district court, the discovery will likely be subject to the district
`
`court’s protective order, which precludes using confidential information in any
`
`proceeding other than the litigation. (See Exs. 2020 at 16, 2021 at 20-21.)
`
`Similarly, VirnetX has served an interrogatory on Apple in the district court case to
`
`seek information for that case. Apple has not responded yet, and when Apple does
`
`respond, any disclosed information will also be likely unavailable in these
`
`proceedings as its response will be subject to the district court’s protective order.
`
`Moreover, resolving discovery issues in the district court will take time. For
`
`example, VirnetX served subpoenas on New Bay Capital on July 15, 2013, but
`
`6
`
`

`

`
`
`
`
`Case No. IPR2014-00173
`
`New Bay has yet to provide any responsive information. (Ex. 2022.) Here,
`
`VirnetX’s preliminary response addressing RPI and privity issues is due March 6,
`
`2014. Any resolution in the district court will likely occur well after that deadline.
`
`Easily Understandable Instructions:
`
` VirnetX’s
`
`instructions
`
`(see
`
`Exs. 2002-2005 at 1-2) are easily understandable and are based on the instructions
`
`already approved by the Board in Garmin. IPR2012-00001, Paper No. 26 at 14.
`
`Requests Not Overly Burdensome: The limited requests seek only a small
`
`set of materials directly related to the RPX IPRs. Moreover, RPX and Apple have
`
`contended that there is little to no relationship between the two companies and
`
`RPX’s relationship with Sidley Austin was brief. Thus, any alleged financial,
`
`human resource, or time burden on RPX or Apple should be negligible. See
`
`Garmin, IPR2012-00001, Paper 26 at 7.
`
`IV. Conclusion
`Based on the above, VirnetX respectfully requests that the Board allow the
`
`discovery contained in Exhibits 2002-2005.
`
`Dated: January 27, 2014
`
`
`
`Respectfully submitted,
`
`By: /Joseph E. Palys/
`Joseph E. Palys
`Registration No. 46,508
`
`Counsel for VirnetX Inc.
`
`7
`
`

`

`
`
`
`
`Case No. IPR2014-00173
`
`Certificate of Service
`I certify that I caused to be served on the counsel identified below a true and
`
`correct copy of
`
`the
`
`foregoing Patent Owner’s Motion
`
`for Discovery
`
`from RPX Corporation and Apple, Inc., by electronic means on January 27, 2014:
`
`Oliver R. Ashe, Jr.
`Ashe, P.C.
`11440 Isaac Newton Sq. North, Suite 210
`Reston, VA 20190
`
`Gregory M. Howison
`Howison & Arnott, LLP
`Lincoln Centre II
`5420 LBJ Freeway, Suite 660
`Dallas, TX 75240
`
`Jeffrey P. Kushan
`Joseph A. Micallef
`Sidley Austin LLP
`1501 K Street NW
`Washington, DC 20005
`
`
`Respectfully submitted,
`
`By: /Joseph E. Palys/
`Joseph E. Palys
`Reg. No. 46,508
`
`Counsel for VirnetX Inc.
`
`
`
`
`
`
`
`Dated: January 27, 2014
`
`
`
`
`
`

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