throbber

`
`
`
`
`
`Case No. IPR2014-00173
`
`
`
`Paper No.
`Filed: March 6, 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 Preliminary Response
`to Petition for Inter Partes Review
`of U.S. Patent No. 7,490,151
`
`
`
`
`
`
`
`
`
`
`

`

`Table of Contents
`Introduction ...................................................................................................... 1
`The Petition Fails to Meet the Requirements for Instituting an
`Inter Partes Review ......................................................................................... 2
`A.
`The Petition Should Not Be Considered Under 35 U.S.C.
`§§ 312(a)(2) and 315(b) ........................................................................ 3
`1.
`There Is a Long-Standing Relationship Between RPX
`and Apple .................................................................................... 4
`a)
`RPX and Apple Worked Jointly to Challenge
`VirnetX Patents ................................................................. 4
`RPX and Apple Have Tried to Hide Apple’s
`Involvement ...................................................................... 6
`The Petition Fails to Name a Real Party-in-Interest ................... 8
`a)
`RPX and Apple Violated the First Guan Factor .............10
`b)
`RPX and Apple Violated the Second Guan Factor ........10
`c)
`RPX and Apple Violated the Third Guan Factor ...........11
`d)
`RPX Is Like the Requester in Guan ...............................13
`Trial May Not Be Instituted Under 35 U.S.C. § 315(b) ...........14
`a)
`Apple Is a Time-Barred Real Party-in-Interest ..............14
`b)
`Apple Is a Time-Barred Privy ........................................15
`Policy Considerations Support Denying the Petition ...............17
`4.
`The Petition Fails to Comply with 35 U.S.C. § 312(a)(3) and
`37 C.F.R. § 42.104(b)(4) .....................................................................19
`RPX’s Petition Should Be Denied Under 35 U.S.C. § 325(d) ............23
`The Proposed Grounds Treat Aventail as a Single Document
`Instead of Two Separate Documents ...................................................26
`
`b)
`
`2.
`
`3.
`
`
`
`
`
`Case No. IPR2014-00173
`
`
`
`I.
`II.
`
`B.
`
`C.
`D.
`
`i
`
`

`

`
`
`
`
`
`
`Case No. IPR2014-00173
`
`E.
`
`E.
`
`F.
`G.
`H.
`I.
`J.
`
`The Board Should Not Institute Based on the Petition’s
`Redundant Grounds .............................................................................28
`III. The Petition’s Claim Constructions Are Flawed and Should Be
`Rejected .........................................................................................................33
`A. Overview of the ’151 Patent ................................................................34
`B.
`Level of Ordinary Skill in the Art .......................................................36
`C.
`“DNS Request” (Claims 1, 4, 7, 10, 13, and 16) ................................37
`D.
`“Domain Name” (Construe as Part of “Domain Name Server
`(DNS) Proxy Module” or “Domain Name Server (DNS)
`Module”) .............................................................................................38
`“Domain Name Server” (Construe as Part of “Domain Name
`Server (DNS) Proxy Module” or “Domain Name Server (DNS)
`Module”) .............................................................................................40
`“Domain Name Server (DNS) Proxy Module” (Claims 1 and 7) .......42
`“Domain Name Server (DNS) Module” (Claim 13) ...........................43
`“Secure Server” (Claims 1-3, 5-9, and 11-15) ....................................44
`“IP Address Hopping Scheme” (Claims 5 and 11) .............................45
`“Automatically Initiating an Encrypted Channel” /
`“Automatically Creating a Secure Channel” (Claims 1, 5-7, and
`11-13) ..................................................................................................47
`“Client” (Claims 1-16) ........................................................................48
`“Determining” (Claims 1, 2, 7, 8, 13, and 14) ....................................51
`“Forwarding the DNS Request” (Claims 1, 7, and 13) .......................52
`“Intercepts DNS Requests / Intercepting a DNS Request /
`Intercepted DNS Request” (Claims 1, 7, and 13) ...............................52
`If Trial Is Instituted, VirnetX Requests an 18-Month Schedule ...................52
`Conclusion .....................................................................................................53
`
`K.
`L.
`M.
`N.
`
`IV.
`V.
`
`ii
`
`

`

`
`
`
`
`
`
`Case No. IPR2014-00173
`
`
`TABLE OF AUTHORITIES
`
` Page(s)
`
`Federal Cases
`Apple Inc. v. Int’l Trade Comm’n,
`725 F.3d 1356 (Fed. Cir. 2013) .......................................................................... 26
`Apple Inc. v. VirnetX Inc.,
`IPR2013-00348 (June 12, 2013) Paper No. 1 ....................................................... 4
`Apple Inc. v. VirnetX Inc.,
`IPR2013-00349 (Sept. 17, 2013) Paper No. 10 .................................................. 26
`Apple Inc. v. VirnetX Inc.,
`IPR2013-00354 (Sept. 19, 2013) Paper No. 15 ............................................ 20, 32
`Asahi Glass Co. v. Toledo Eng’g Co.,
`505 F. Supp. 2d 423 (N.D. Ohio 2007) .............................................................. 16
`CallCopy, Inc. v. Verint Ams., Inc.,
`IPR2013-00486 (Feb. 5, 2014) Paper No. 11 ..................................................... 27
`Chef Am., Inc. v. Lamb-Weston, Inc.,
`358 F.3d 1371 (Fed. Cir. 2004) .......................................................................... 51
`EMC Corp. v. Personal Web Techs., LLC,
`IPR2013-00087 (June 5, 2013) Paper No. 25 ..................................................... 29
`Garmin Int’l, Inc. v. Cuozzo Speed Techs. LLC,
`IPR2012-00001 (Jan. 9, 2013) Paper No. 15 ...................................................... 34
`Graham v. John Deere Co. of Kansas City,
`383 U.S. 1 (1966) ................................................................................................ 28
`Gustafson v. Alloyd Co., Inc.,
`513 U.S. 561 (1995) ............................................................................................ 15
`Idle Free Sys., Inc. v. Bergstrom, Inc.,
`IPR2012-00027 (June 11, 2013) Paper No. 26 ................................................... 29
`
`iii
`
`

`

`
`
`
`
`Case No. IPR2014-00173
`
`
`In re Guan et al. Inter Partes
`Reexamination Proceeding, Control No. 95/001,045, Decision
`Vacating Filing Date (Aug. 25, 2008) .........................................................passim
`Intelligent Bio-Systems, Inc. v. Illumina Cambridge Ltd.,
`IPR2013-00324 (Nov. 21, 2013) Paper No. 19 .................................................. 24
`LaRose Indus., LLC v. Capriola Corp.,
`IPR2013-00120 (July 22, 2013) Paper No. 20 ............................................ 29, 33
`Liberty Mut. Ins. Co. v. Progressive Cas. Ins. Co.,
`CBM2012-00003 (Oct. 25, 2012) Paper No. 7 ................................. 28, 29, 30, 33
`Motorola Solutions, Inc. v. Mobile Scanning Techs., LLC,
`IPR2013-00093 (Apr. 29, 2013) Paper No. 28 ................................................... 34
`Phelps v. Hamilton,
`122 F.3d 1309 (10th Cir. 1997) .......................................................................... 16
`Phillips v. AWH Corp.,
`415 F.3d 1303 (Fed. Cir. 2005) (en banc) .................................................... 34, 41
`SAP Am., Inc. v. Versata Dev. Group, Inc.,
`CBM2012-00001 (June 11, 2013) Paper 70 ....................................................... 39
`SAP Am., Inc. v. Pi-Net Int’l, Inc.,
`CBM2013-00013 (Sept. 19, 2013) Paper No. 15 ............................................... 15
`ScentAir Techs., Inc. v. Prolitec, Inc., Case
`IPR2013-00180 (Aug. 26, 2013) Paper No. 18 .................................................. 30
`Tasco, Inc. v. Pagnani,
`IPR2013-00103 (May 23, 2013) Paper No. 6 ..................................................... 19
`Taylor v. Sturgell,
`553 U.S. 880 (2008) ............................................................................................ 17
`Wowza Media Sys., LLC et al. v. Adobe Sys., Inc.,
`IPR2013-00054 (July 13, 2013) Paper No. 16 ................................................... 19
`In re Zletz,
`893 F.2d 319 (Fed. Cir. 1989) ............................................................................ 33
`
`iv
`
`

`

`
`
`
`
`Case No. IPR2014-00173
`
`
`State Cases
`Arpadi et al. v. First MSP Corp. et al.,
`68 Ohio St. 3d 453 (Sept. 21, 1993) ................................................................... 17
`Federal Statutes
`35 U.S.C. § 311 .......................................................................................................... 8
`35 U.S.C. § 311(b) ................................................................................................... 21
`35 U.S.C. § 312(a) ................................................................................................. 1, 2
`35 U.S.C. § 312(a)(2) ................................................................................. 3, 8, 14, 53
`35 U.S.C. § 312(a)(3) ................................................................................. 1, 3, 19, 23
`35 U.S.C. § 313 .......................................................................................................... 1
`35 U.S.C. § 314(a) ................................................................................................... 18
`35 U.S.C. § 315 ........................................................................................................ 14
`35 U.S.C. § 315(b) ............................................................................................passim
`35 U.S.C. § 315(e) ................................................................................................... 18
`35 U.S.C. § 316(a)(1) ............................................................................................... 53
`35 U.S.C. § 325(d) ............................................................................................passim
`Rules
`Fed. R. Civ. P. 17(a)................................................................................................. 18
`Regulations
`37 C.F.R. § 42.8 ....................................................................................................... 52
`37 C.F.R. § 42.100(b) .............................................................................................. 33
`37 C.F.R. § 42.100(c) ............................................................................................... 53
`37 C.F.R. § 42.104(b)(4) ...................................................................................passim
`
`v
`
`

`

`
`
`
`
`Case No. IPR2014-00173
`
`
`37 C.F.R. § 42.107 ..................................................................................................... 1
`Other Authorities
`77 Fed. Reg. 48680, Changes to Implement Inter Partes Review
`Proceedings (Aug. 14, 2012) .............................................................................. 23
`77 Fed. Reg. 48756, Office Patent Trial Practice Guide
`(Aug. 14, 2012) ............................................................................................passim
`157 Cong. Rec. S1041-42 (daily ed. Mar. 1, 2011) ................................................. 24
`
`
`
`
`
`vi
`
`

`

`
`I.
`
`
`
`
`
`Case No. IPR2014-00173
`
`Introduction
`Patent Owner VirnetX Inc. respectfully submits this Preliminary Response
`
`in accordance with 35 U.S.C. § 313 and 37 C.F.R. § 42.107, responding to the
`
`Petition for Inter Partes Review (the “Petition”) filed by RPX Corporation.
`
`VirnetX requests that the Board not institute inter partes review for several
`
`reasons.
`
`First, Apple Inc. contracted with RPX to file several inter partes review
`
`petitions on its behalf, including the petition in this inter partes review. Apple is
`
`time-barred from challenging VirnetX’s U.S. Patent No. 7,490,151 (“the ’151
`
`patent”) under 35 U.S.C. § 315(b), and it cannot hire RPX to challenge the ’151
`
`patent in its place. Apple is a real party-in-interest in this proceeding, and Apple
`
`and RPX are privies. Thus, the case should be dismissed under 35 U.S.C.
`
`§§ 312(a) and 315(b).
`
`Second, the Petition fails to comply with several rules and regulations
`
`regarding the content of petitions. The Petition either never or rarely cites the
`
`asserted prior art references, violating the particularity requirements of 35 U.S.C.
`
`§ 312(a)(3) and 37 C.F.R. § 42.104(b)(4). The Petition attempts to combine two
`
`references in an anticipation analysis, in violation of Federal Circuit case law, and
`
`its backup obviousness argument lacks any analysis, in violation of Supreme Court
`
`precedent. The Petition also proposes horizontally and vertically redundant
`
`
`
`
`
`

`

`
`grounds without identifying how any one ground improves on any other, violating
`
`Case No. IPR2014-00173
`
`
`
`
`
`Board precedent requiring petitioners to identify differences in the proposed
`
`rejections.
`
`Third, the proposed rejections here are duplicative of the proposed rejections
`
`in copending reexaminations of the ’151 patent, which rely on many of the same
`
`references and rejections proposed by RPX. The Board should decline to institute
`
`this duplicative proceeding under 35 U.S.C. § 325(d).
`
`Finally, RPX proposes a series of incorrect claim constructions. Because its
`
`unpatentability challenges are premised on incorrect claim constructions, RPX has
`
`not met its burden of demonstrating a reasonable likelihood of prevailing in
`
`proving unpatentability of any ’151 patent claim.
`
`II. The Petition Fails to Meet the Requirements for Instituting an
`Inter Partes Review
`Trial should not be instituted because RPX’s Petition does not comply with
`
`numerous statutes and regulations that must be satisfied for institution. Violations
`
`include:
`
`(1) not identifying all real parties in interest under 35 U.S.C. § 312(a);
`
`(2) being barred under 35 U.S.C. § 315(b) because a real party in interest or
`
`privy of RPX was served with a complaint alleging infringement of the ’151 patent
`
`more than one year before the Petition was filed;
`
`2
`
`

`

`
`
`
`
`
`
`Case No. IPR2014-00173
`
`(3) failing to comply with 35 U.S.C. § 312(a)(3)’s particularity requirement
`
`and 37 C.F.R. § 42.104(b)(4)’s requirement to “specify where each element of the
`
`claim is found in the prior art patents or printed publications relied upon” by citing
`
`almost solely to expert declarations, which often generalize the references, as
`
`opposed to citing the references themselves;
`
`(4) relying on references already at issue in other proceedings, resulting in
`
`cumulative proceedings that warrant dismissing this Petition under 35 U.S.C.
`
`§ 325(d);
`
`(5) impermissibly combining two separate references in an anticipation
`
`rejection and offering a backup obviousness position without any analysis; and
`
`(6) proposing redundant grounds without identifying how any one ground
`
`improves on any other.
`
`A. The Petition Should Not Be Considered Under 35 U.S.C.
`§§ 312(a)(2) and 315(b)
`The Petition fails to identify at least Apple as a real party-in-interest (“RPI”),
`
`as required by 35 U.S.C. § 312(a)(2), and is barred under § 315(b) because Apple
`
`is RPX’s privy and is time-barred from challenging the ’151 patent. Several policy
`
`considerations also support denial of the Petition.
`
`3
`
`

`

`
`
`
`
`
`
`Case No. IPR2014-00173
`
`1.
`
`There Is a Long-Standing Relationship Between RPX and
`Apple
`RPX and Apple Worked Jointly to Challenge VirnetX
`a)
`Patents
`RPX is a defensive patent services provider that, by its own admission,
`
`“serves as an extension of a client’s in-house legal team,” acts as a “trusted
`
`intermediary” for its clients, and “selectively clear[s its] clients” from litigation.
`
`(Exs. 2006, 2007 at 3, 2008.) To fund these services, RPX receives yearly
`
`subscription fees from clients like Apple. (Ex. 2007 at 9.)
`
`
`
`
`
`
`
`In 2010, and intermittently through late 2013, RPX and Apple discussed
`
`creating an Apple-funded program to challenge specific patents through post-grant
`
`proceedings at the U.S. Patent and Trademark Office (“USPTO”), but no program
`
`was created during those three years. (Ex. 2039 at 15.) Following a series of
`
`setbacks against VirnetX, however, Apple reversed course.
`
`After a district court ordered Apple to pay VirnetX approximately $368M in
`
`damages, (Ex. 2009), Apple filed a series of IPR petitions against VirnetX’s
`
`patents. (See, e.g., Apple Inc. v. VirnetX Inc., IPR2013-00348, Paper No. 1 (June
`
`12, 2013).) But in an August 5, 2013, Board call, it became clear that Apple’s IPR
`
`petitions would likely be found time-barred under 35 U.S.C. § 315(b), and the
`
`4
`
`

`

`
`discussion turned to whether Apple could properly seek joinder with a series of
`
`Case No. IPR2014-00173
`
`
`
`
`
`IPR petitions filed by New Bay Capital. (Ex. 2031 at 3-5.) Seeing its chance to
`
`challenge VirnetX’s patents in inter partes review slipping away, Apple
`
`immediately contacted RPX to discuss setting up a means for RPX to challenge
`
`VirnetX’s patents. (Ex. 2039 at 15 (discussing VirnetX and “challeng[ing] patents
`
`of questionable quality” on Aug. 8, 2013); see also Exs. 2042-2044.)
`
`In response to Apple’s inquiries regarding VirnetX, RPX proposed that
`
`Apple join a “Premium Services” plan in which RPX would, among other things,
`
`initiate a “proactive IPR program” in exchange for an increase in Apple’s yearly
`
`membership fees. (Ex. 2045 at 11-13.) Apple and RPX discussed the plan and
`
`Apple agreed to a one-time payment of $500,000 with the express purpose of
`
`targeting so-called “questionable” patents through the filing of IPRs. (Ex. 2047.)
`
`The VirnetX patents were identified as part of RPX’s “Premium Services”
`
`presentation. (Ex. 2045 at 16.)
`
`On October 18, New Bay informed the Board of its intent to terminate its
`
`IPR proceedings, ending Apple’s hopes of joining New Bay’s petitions and setting
`
`off a flurry of activity by Apple and RPX. (Ex. 2032; Exs. 2034-37.) That same
`
`day, Apple contacted RPX to finalize their agreement. (Ex. 2046 (emailing RPX
`
`to set up a call); Ex. 2047 (emailing RPX a revised agreement).) Apple also gave
`
`RPX consent to use its attorneys at Sidley Austin for challenging VirnetX’s
`
`5
`
`

`

`
`patents. (Ex. 2041 at 5.) And within days, Apple, through its attorneys at Sidley
`
`Case No. IPR2014-00173
`
`
`
`
`
`Austin, formally objected to terminating New Bay’s IPR petitions. (Ex. 2033.)
`
`RPX, in turn, on October 21, retained Apple’s same team of Sidley Austin
`
`attorneys who filed Apple’s IPR petitions. (Ex. 2041.) The next day, Apple and
`
`RPX signed an “Addendum Agreement” allowing RPX to file IPR petitions on
`
`behalf of Apple in exchange for an initial contribution of $500,000 to finance the
`
`petitions. (Ex. 2050; Ex. 2051; Ex. 2052; Ex. 1073 at 1-2.) Within a month,
`
`RPX—represented by Apple’s counsel at Sidley Austin (Ex. 1074 at 13:12-18:11,
`
`Ex. 2001 at 71:11-22)—filed this Petition and six others, raising grounds
`
`“substantially identical” or “substantially similar” to those raised by Apple.1 (See
`
`e.g., Pet. at 6; Ex. 2001 at 53:12-54:3.) Apple also gave RPX access to its expert.
`
`(See Ex. 2039 at 14.)
`
`b) RPX and Apple Have Tried to Hide Apple’s
`Involvement
`Despite the undisputed relationship between Apple and RPX and Apple’s
`
`involvement with the Petition, Apple and RPX have attempted to give the
`
`impression throughout this proceeding that they are unconnected entities and that
`
`
`1 While the petitions are similar, there are differences as well. For instance,
`
`RPX’s petitions respond to certain arguments made by VirnetX in its preliminary
`
`responses in the earlier Apple cases.
`
`6
`
`

`

`
`Apple is not an RPI or a privy of RPX. For instance, neither party disclosed
`
`Case No. IPR2014-00173
`
`
`
`
`
`RPX’s relationship with Apple’s counsel—even when asked directly by the Board
`
`whether Apple’s counsel aided RPX in preparing its petitions. (Ex. 2001 at 69:6-
`
`71:4.) RPX and Apple only admitted that they shared counsel after VirnetX
`
`disclosed the existence of metadata within RPX’s petitions revealing Sidley
`
`Austin’s involvement. (Ex. 2001 at 71:11-22.) Even then, RPX and Apple limited
`
`their disclosure to select facts. (Ex. 1074 at 6:13-9:13.)
`
`Similarly, in opposing VirnetX’s motion for additional discovery, Apple and
`
`RPX continued to assert that there were no communications between Apple and
`
`RPX regarding the RPX petitions. (See, e.g., Paper No. 23 at 2.) The facts
`
`discussed above, however, show otherwise. (See, e.g., Ex. 2039 at 14.) Likewise,
`
`just three days ago, Apple represented to the Board that no pre-filing
`
`communications exist between Sidley Austin and Apple regarding the RPX IPRs.
`
`(Ex. 2053 at 27:6-28:8; 29:19-30:8.) But Apple’s communication regarding
`
`consent for RPX to use Sidley Austin in the IPRs calls into question this
`
`representation. (Ex. 2041 at 5.)
`
`Apple and RPX also rely on the Addendum Agreement they carefully
`
`crafted to assert that they did not have any pre-filing communications and Apple is
`
`not an RPI or privy of RPX. They point to the provision in the agreement stating
`
`that “[i]n no event will RPX disclose to Member [Apple] any nonpublic
`
`7
`
`

`

`
`information regarding any planned or filed petitions or proceedings before the
`
`Case No. IPR2014-00173
`
`
`
`
`
`USPTO pursuant to Section 1.” (Ex. 1073 at 2.) But the facts show that RPX did
`
`disclose to Apple nonpublic information regarding its planned petitions (e.g., that
`
`RPX was retaining Apple’s expert “to support the RPX IPR petitions”), thus not
`
`adhering to the terms of the Addendum Agreement. (Ex. 2039 at 14.)
`
`Apple and RPX continue to provide only select information regarding
`
`communications between them. (See, Ex. 2039 at 15-17; Ex. 2054.) Nevertheless,
`
`as discussed below, the facts still reveal that Apple is an unnamed RPI and a time-
`
`barred privy of RPX.
`
`The Petition Fails to Name a Real Party-in-Interest
`2.
`35 U.S.C. § 312(a)(2) states that “[a] petition filed under section 311 may be
`
`considered only if . . . the petition identifies all real parties in interest.” 35 U.S.C.
`
`§ 312(a)(2). Because this Petition fails to do so, it must be denied.
`
`The “‘real party-in-interest’ is the party that desires review of the patent.”
`
`Office Patent Trial Practice Guide, 77 Fed. Reg. 48759 (hereinafter, “TPG”).
`
`While this may include the petitioner itself, it also includes “the party or parties at
`
`whose behest the petition has been filed.” Id. The TPG instructs that generally, “a
`
`party that funds and directs and controls an IPR . . . petition or proceeding
`
`constitutes a ‘real party-in-interest.” Id. at 48760. While actual control or having
`
`the “opportunity to control” are two ways to establish that a party is an RPI, these
`
`8
`
`

`

`
`are not the only ways. See id. RPI determinations are handled on a “case-by-case
`
`Case No. IPR2014-00173
`
`
`
`
`
`basis” and should involve a “deeper consideration of the facts.” Id.
`
`In re Guan, which the TPG approvingly cites as providing “additional
`
`guidance” on RPI issues (id. at 48759), identifies, among other things, three
`
`prohibitions that, if any one is violated, results in a party being an RPI:
`
`[A party] cannot do any of the following and not identify
`the other entity as real party in interest:
`
`1). Accept payment from another group, pay the
`requester
`to
`file
`the
`request
`for
`inter partes
`reexamination . . . .
`
`2). Obtain money for foundation grants, file a “quid pro
`quo” request for an inter partes reexamination where the
`foundation wants reexamination on a specific patent the
`foundation deems anti-competitive . . . .
`
`3). Allow another entity to direct or control the content,
`(e.g., provide the prior patents/printed publications on
`which the reexam is to be based) of the request . . . .
`
`In re Guan et al. Inter Partes Reexamination Proceeding, Control No. 95/001,045,
`
`Decision Vacating Filing Date at 8 (Aug. 25, 2008) (emphasis added). While
`
`violating any one of the three Guan prohibitions requires finding that Apple is an
`
`RPI, Apple and RPX have violated each of them.
`
`9
`
`

`

`
`
`
`
`
`
`Case No. IPR2014-00173
`
`RPX and Apple Violated the First Guan Factor
`a)
`RPX and Apple violated the first Guan prohibition—“accept[ing] payment
`
`from another group, pay[ing] the requester to file the request for inter partes
`
`[review]”—when RPX accepted Apple’s $500,000 payment to file this Petition and
`
`the others pending before the Board. Guan at 8. RPX admits that the terms of the
`
`Addendum Agreement apply to this particular IPR proceeding (see Pet. at 2-3), so
`
`it cannot selectively contend that Apple’s payment for services under the same
`
`agreement does not pertain to this proceeding.
`
`While RPX states that after receiving the funds from Apple, it is “solely
`
`responsible for payment of any expenses of preparing and filing petitions” (Pet. at
`
`3; see also Ex. 2001 64:15-65:5), this cannot negate that Apple gave the funds to
`
`RPX to file the petitions on its behalf and RPX used those funds to file the Petition.
`
`(See Ex. 1073 at 1-2; see also Ex. 2049 (Apple expressing concern that its funds
`
`would not be entirely used up by a specific end date); Ex. 2048.) Similarly, Apple
`
`would remain an RPI even if others also paid RPX to challenge VirnetX’s patents.
`
`b) RPX and Apple Violated the Second Guan Factor
`RPX and Apple also violated the second Guan prohibition—“obtain[ing]
`
`money for foundation grants, fil[ing] a ‘quid pro quo’ request for inter partes
`
`[review] where the foundation wants reexamination on a specific patent that the
`
`foundation deems anti-competitive.” Guan at 8. The Addendum Agreement
`
`10
`
`

`

`
`characterizes Apple’s payment as contributing to an internal RPX “Innovation
`
`Case No. IPR2014-00173
`
`
`
`
`
`Promotion Fund” (“Fund”) where RPX would “use reasonable efforts to collect
`
`additional contributions from other RPX members.” (Ex. 1073.) This is
`
`indistinguishable from Guan’s “foundation” where the funds were paid, and the
`
`“foundation grants” the petitioner sought. Guan at 3, 8. Indeed, similar to Guan,
`
`the Addendum Agreement states that the Fund will be used for “[f]iling with the
`
`United States Patent and Trademark Office . . . requests for . . . inter partes review
`
`with respect to patents of [alleged] questionable quality.” (Ex. 1073 at 1.)
`
`The Office rightly saw through this arrangement in Guan and found that the
`
`party paying the petitioner was an RPI. Guan at 8. Apple’s contribution to the
`
`Fund for RPX’s IPR program is no different. Indeed, regardless of how the
`
`“Fund” is characterized, it cannot be disputed that Apple engaged RPX to provide
`
`services that include filing this Petition for a fee of $500,000.
`
`RPX and Apple Violated the Third Guan Factor
`c)
`RPX and Apple also violated Guan’s third prohibition—“[a]llow[ing]
`
`another entity to direct or control the content, (e.g., provid[ing] the prior
`
`patents/printed publications on which the reexam is to be based) of the request.”
`
`Guan at 8. Guan expands on what it means to direct or control content by
`
`explaining that boilerplate statements by a requester that it “controlled the content”
`
`of a request fail to satisfy the RPI inquiry where there is ambiguity. Id. at 2, 5, 8.
`
`11
`
`

`

`
`Looking to the requester’s actions, the Office determined that if the requester
`
`Case No. IPR2014-00173
`
`
`
`
`
`received the “prior patents/printed publications on which the reexam is to be
`
`based” from another party or allowed that party to conduct a “technical review,”
`
`even if only to ensure accuracy, the other party has directed and controlled the
`
`filing to such an extent that it must be named as an RPI. Id. at 2, 8. Guan also
`
`explains that an entity cannot be named as the sole real party in interest if it
`
`receives funding and even a “suggestion” from another party that a particular
`
`patent should be challenged. Id. at 7-8.
`
`Here, RPX and Apple have done all of this. They had discussions about
`
`VirnetX only three days after Apple discussed with the Board the time-bar issues
`
`with its petitions pending last year. (See supra Section II.A.1) RPX received
`
`Apple’s prior art, Apple’s experts, and the patents and claims to be reviewed. (Id.)
`
`And Apple’s team of attorneys at Sidley Austin helped review, prepare, and file
`
`RPX’s IPR petitions. (Id.) Apple was complicit in these activities, expressly
`
`consenting to having RPX retain Apple’s attorneys at Sidley Austin regarding
`
`VirnetX’s patents, and providing RPX access to its expert “to support the RPX IPR
`
`petitions.” (Ex. 2041 at 5; Ex. 2039 at 14.) The self-serving statements in the
`
`Petition and the Addendum Agreement regarding control cannot change these
`
`facts. Thus, under the third Guan factor, Apple is an RPI.
`
`12
`
`

`

`
`
`
`
`
`
`Case No. IPR2014-00173
`
`d) RPX Is Like the Requester in Guan
`RPX offers the same services to Apple that the requester offered in Guan. In
`
`Guan, the Office said the requester provides “freedom to operate services” and
`
`“undertake[s] ‘projects’ to file reexaminations to open up market competition and
`
`broaden competition.” Guan at 2. RPX similarly states that it “is the leading
`
`provider of patent risk solutions” and pursues efforts such as its IPR program that
`
`has targeted VirnetX’s patents. (Pet. at 2; Ex. 2045 at 11; see also Exs. 2006-2008,
`
`describing RPX’s business model). As a company that makes no products and has
`
`no risk itself regarding VirnetX’s patents, RPX had no incentive to file these IPR
`
`petitions other than to be paid to act on Apple’s behalf. Indeed, once Apple
`
`initiated a discussion with RPX regarding challenging VirnetX patents at the
`
`USPTO (Ex. 2039 at 15; Ex. 2042), RPX quickly filed IPR petitions on the same
`
`patents as Apple’s time-barred petitions (see generally, Pet.).
`
`As the Office noted, entities like the Guan requester and RPX cannot be
`
`used to “act as a ‘shill’ in an inter partes [review petition] to shield the identity of
`
`the real party or parties in interest” and/or to circumvent estoppel provisions.
`
`Guan at 7. Consistent with this view, the TPG identifies the “nature of the entity
`
`filing the petition” as a “relevant factor” in assessing RPI issues. TPG at 48760.
`
`Because RPX’s business model is to be paid to act on behalf of its clients (in
`
`this case Apple), and because RPX and Apple engaged in each of the three
`
`13
`
`

`

`
`prohibited activities in Guan, Apple is an RPI in these proceedings. Indeed, RPX
`
`Case No. IPR2014-00173
`
`
`
`
`
`“serves as an extension of a client’s in-house legal team” (Ex. 2006) and is no
`
`different than a law firm that is retained to prepare and file IPR petitions. An
`
`entity, such as Apple, would not be able to hide behind a law firm, and it should
`
`not be allowed to hide behind RPX. Accordingly, RPX’s Petition should be denied
`
`under 35 U.S.C. § 312(a)(2) for failing to name all real parties-in-interest.
`
`Trial May Not Be Instituted Under 35 U.S.C. § 315(b)
`3.
`Under 35 U.S.C. § 315 “[a]n inter partes review may not be instituted if the
`
`petition requesting the proceeding is filed more than 1 year after the date on which
`
`the petitioner, real party in interest, or privy of the petitioner is served with a
`
`complaint alleging infringement of the patent.” 35 U.S.C. § 315(b) (emphasis
`
`added). Because the Board previously found that Apple was time-barred from
`
`challenging the ’151 patent in inter partes review, § 315(b) also bars this Petition.
`
`Apple Is a Time-Barred Real Party-in-Interest
`a)
`On April 5, 2011, VirnetX served a complaint against Apple, alleging
`
`infringement of the ’151 patent. (Ex. 2035.) Over two years later, Apple filed a
`
`series of IPR petitions challenging a number of VirnetX patents, including the ’151
`
`patent. These were denied by the Office as time-barred under § 315(b). (See, e.g.,
`
`Exs. 2010-2016.) Because Apple is an RPI, as dis

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