throbber

`Case 6:10—cv—OO417—LED Document 266
`Filed 04/25/12 Page 1 of 31 PageID #: 7521
`
`
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`TYLER DIVISION
`
`

`
`VIRNETX INC.,
`
`
`§ §
`
`§ §
`
`Plaintiff,
`
`vs.

`CASE NO. 6:10-CV-417
`
`

`
`§ §
`
`CISCO S¥STE1VIS, INC, et al.,
`
`
`Defendants.
`
`§ §
`
`MEMORANDUM OPINION AND ORDER
`
`
`This Mem9¥aHde—Qplfllefl—GGHS¥FHCS the disputed claim terms in US. Patent Nos.
`
`6,502,135 (“the ‘135 Patent”), 6,839,759 (“the ‘759 Patent”), 7,188,180 (“the ‘180 Patent”),
`
`
`74330—4 (“the ‘5071 Patent”), 7490151 (“the ‘ 151 Patent”), and 7,921,211 (“the ‘211 Patent”).
`
`Further, as stated at the Mark/mm hearing and agreed by the parties, the Court ORDERS
`
`that VirnetX Inc’s Motion to Compel from Apple a Complete Response to VirnetX’s Eighth
`
`Common Interrogatory (Docket No. 179) is DENIED AS MOOT.
`
`BA CKGRO UN D
`
`
`VirnetX Inc. (“VirnetX”) asserts all six patents-in-suit against Aastra Technologies Ltd;
`
`
`Aastra USA, Inc; Apple Inc; Cisco Systems, Inc; NEC Corporation; and NEC Corporation of
`
`
`
`creating a virtual private network (“VPN”) between a client computer and a target computer. The
`
`
`‘75‘7Patent discloses a method—for establishing a VPN w1thout a user entenng user 1dent1ficat10n
`
`information. The ‘180 Patent discloses a method of establishing a secure communication link
`
`—beM&anutemThe‘504md‘fllPaenmdi&loseammdomamnameseMceThe
`
`
`
`
`New Bay Capital, LLC
`EXIIO’IS-Page 1 of31
`
`New Bay Capital, LLC
`Ex.1013-Page 1 of 31
`
`

`

`Filed 04/25/12 Page 2 of 31 PageID #: 7522
`Case 6:10—cv—00417—LED Document 266
`
`
`‘151 Patent discloses a domain name service capable of handling both standard and non-standard
`
`domain name service queries.
`
`
`
`an ancestor application for every patent—in—suit. The ‘ 135 Patent issued on December 31, 2002,
`
`
`from the ‘783 Application. The ‘151 Patent issued from a division of the ‘783 Application. The
`
`‘180 Patent issued from a division of a continuation-in-part of the ‘783 Application. Both the
`
`
`‘759 and ‘504 Patents issued frem a eontjnuatien of a centiniiatiQn-in-pant of the ‘783
`
`Application. Finally, the ‘21] Patent is a continuation of the application that resulted in the ‘504
`
`
`patent.
`
`The Court has already construed many of the terms at issue in a previous case that
`
`
`involved the ‘135, ‘759, and ‘ 180 Patents. Sec VirnetX, Inc. v. Microsoft Corp, 2009 US. Dist.
`
`LEXIS 65667, No. 6:07cv80 (ED. TeX. July 30, 2009) (“Microsoft”).
`
`APPLICABLE LAW
`
`“It is a ‘bedrock principle’ of patent law that ‘the claims of a patent define the invention
`
`to which the patentee is entitled the right to exclude.” Phillips v. AWH Corp, 415 F.3d 1303,
`
`1312 (Fed. Cir. 2005) (en banc) (quoting lnnova/Pure Water Inc. v. Safari Water Filtration Svs.,
`
`Inc, 381 F.3d 1111, 1115 (Fed. Cir. 2004)). In claim construction, courts examine the patent’s
`
`
`
`flmrdencrtcrdefinrflrrpatentedmm scope. See id, CR. Bard, Inc.
`V. US.
`
`Surgical Corp, 388 F.3d 858, 861 (Fed. Cir. 2004); Bell Atl. Network Servs., Inc. v. Covad
`
`
`Commc’ns Group, Inc., 262 F.3d 1258, 1267 (Fed. Cir. 2001). This intrinsic evidence includes
`
`the claims themselves, the specification, and the prosecution history. See Phillips, 415 F.3d at
`
`
`13b4, CRBardlnc, 388F3dat86l Courts giveclahntermstheirordinarrantbamrstomed—
`
`
`meaning as understood by one of ordinary skill in the art at the time of the invention in the
`
`
`
`New Bay Capital, LLC
`EXIIO’IS-Page 2 of31
`
`New Bay Capital, LLC
`Ex.1013-Page 2 of 31
`
`

`

`
`Case 6:10—cv—00417—LED Document 266
`Filed 04/25/12 Page 3 of 31 PageID #: 7523
`
`
`context of the entire patent. Phillips, 415 F.3d at 1312—13; Alloc, Inc. v. Ini’l Trade Comm ’n,
`
`342 F.3d 1361, 1368 (Fed. Cir. 2003).
`
`
`Ibel'
`
`I
`
`I
`
`‘l
`
`l
`
`'I
`
`'l
`
`'l "I
`
`.
`
`3
`
`particular claim terms Phillips, 415 F.3d at 1314. First. a term’s context in the asserted claim
`
`
`can be very instructive. Id Other asserted or unasserted claims can also aid in determining the
`
`claim’s meaning because claim terms are typically used consistently throughout the patent. Id.
`
`
`Differences amongthe lim rm
`
`n l
`
`i
`
`in n
`
`r
`
`n in
`
`rm’ m nin
`
`Id.F r
`
`example, when a dependent claim adds a limitation to an independent claim, it is presumed that
`
`
`
`flmlependemfiamrdoesmfindudeflredmfitamn. Id at 1314—15.
`
`
`“[C]laims ‘must be read in view of the specification, of which they are a part.” 1d.
`
`
`(quoting Marknzan V. Wesiview Instruments, Inc., 52 F .3d 967, 979 (Fed. Cir. 1995) (en banc)).
`
`“[T]he specification ‘is always highly relevant to the claim construction analysis. Usually, it is
`
`dispositive; it is the single best guide to the meaning of a disputed term.” Id. (quoting Viironics
`
`Corp. v. Concepironic, Inc, 90 F.3d 1576, 1582 (Fed. Cir. 1996)); see also Teleflex, Inc. v.
`
`Ficosa N. Am. Corp, 299 F.3d 1313, 1325 (Fed. Cir. 2002). This is true because a patentee may
`
`
`—defineMQMEms,gm&adahnwma-'
`
`possess, or disclaim or disavow the claim scope. Phillips, 415 F.3d at 1316. In these situations,
`
`the inventor s lexicography governs. Id Also, the specification may resolve ambiguous claim
`
`terms “where the ordinary and accustomed meaning of the words used in the claims lack
`
`
`—su£fimemdafi1ympemfimemopeofmedebeascefiamedfiommewordsalme”
`
`Teleflex, Inc, 299 F.3d at 1325. But, “‘[a]1though the specification may aid the court in
`
`
`interpreting the meaning of disputed claim language, particular embodiments and examples
`
`
`appearing in the specification will not generally be read into the claims’” ('omark (Tommc’ns,
`
`
`
`
`
`New Bay Capital, LLC
`Ex.1013-Page 3 of31
`
`New Bay Capital, LLC
`Ex.1013-Page 3 of 31
`
`

`

`Filed 04/25/12 Page 4 of 31 PageID #: 7524
`Case 6:10—ov—OO417—LED Document 266
`
`
`Inc. v. Harris Corp, 156 F.3d 1182, 1187 (Fed. Cir. 1998) (quoting Constant v. Advanced
`
`ll/Iicro-Devices, Inc., 848 F.2d 1560, 1571 (Fed. Cir. 1988)), see also Phillips, 415 F.3d at 1323.
`
`
`wmnmmmwmwmmmmm—
`
`because a patent applicant may also define a term in prosecuting the patent. Home Diagnostics,
`
`
`Inc, v. Lifescan, Inc, 381 F.3d 1352, 1356 (Fed. Cir. 2004) (“As in the case of the specification,
`
`a patent applicant may define a term in prosecuting a patent”).
`
`
`
`
`in determining the legally operative meaning of claim language.” Phillips, 415 F.3d at 1317
`
`
`—fquotingCR Bard, Inc, 388F3d at 862).?echmcahlrctronarreswrd1reatrsescmaydmtmurt—
`
`understand the underlying technology and the manner in which one skilled in the art might use
`
`
`claim terms, but technical dictionaries and treatises may provide definitions that are too broad or
`
`may not be indicative of how the term is used in the patent. 1d. at 1318. Similarly, expert
`
`testimony may aid a court in understanding the underlying technology and determining the
`
`particular meaning of a term in the pertinent field, but an expert’s conclusory, unsupported
`
`assertions as to a term’s definition is entirely unhelpful to a court. Id. Generally, extrinsic
`
`
`
`
`claim terms.” Id.
`
`
`Defendants also contend that some claims at issue are invalid for indefiniteness. A claim
`
`is invalid under 35 U.S.C. § 112 11 2 if it fails to particularly point out and distinctly claim the
`
`
`I'
`mm I'
`
`I
`
`I'
`
`.
`
`I
`
`I'
`
`. H
`
`I'
`
`under 35 U.S.C. § 112 11 2 as indefinite must show by clear and convincing evidence that one
`
`skilled in the art would not understand the scope of the claim when read in light of the
`
`
`
`
`
`New Bay Capital, LLC
`EXIIO’IS-Page 4 of31
`
`New Bay Capital, LLC
`Ex.1013-Page 4 of 31
`
`

`

`
`Case 6:10—cv—00417—LED Document 266
`Filed 04/25/12 Page 5 of 31 PageID #: 7525
`
`
`
`specification. Intellectual Prop. Dev, Inc. v. UA-Columbia Cablevision of Weslchester, Inc, 336
`
`F.3d 1308, 1319 (Fed. Cir. 2003).
`
`
`LEVELOFQRDINARLSKJLLINIHEART
`
`The parties agree that a person of ordinary skill in the art would have a master’s degree in
`
`
`
`computer networking and computer network security.
`
`
`CLAIM TERMS
`
`virtual private network
`
`
`
`VimetX pmposesianetwolkeflcomputerwthichpnyatelsncommumcate with each other
`
`
`by encrypting traffic on insecure communication paths between the computers.” Defendants
`
`
`propose the following emphasized additions: “a network of computers which privately and
`
`directly communicate with each other by encrypting traffic on insecure communication paths
`
`
`between the computers where the communication is both secure and anonymous.”
`
`secure and anonymous
`
`VirnetX proposes the same construction adopted by this Court
`
`in Microsoft. See
`
`Microsoft, 2009 US. Dist. LEXIS 65667, at *8. Defendants seek to explicitly include the “secure
`
`and anonymous” language that was implicitly included in the Court’s Microsoft construction. See
`
`
`id. at >“16 (“lT he Count constnies ‘yintual private network’ as requiring both data 5301va and
`
`
`anonymity”). Just as in Microsoft, the parties here dispute whether a virtual private network
`
`
`
`See id. at * 14—17. For the same reasons stated in Microsoft, the Court finds that a virtual private
`
`
`network requires both data security and anonymity. For clarity. this language is now explicitly
`
`included in the Court’s construction of “virtual private network.”
`
`
`
`
`
`New Bay Capital, LLC
`Ex.1013-Page 5 of31
`
`New Bay Capital, LLC
`Ex.1013-Page 5 of 31
`
`

`

`
`Case 6:10—cv—OO417—LED Document 266
`Filed 04/25/12 Page 6 of 31 PageID #: 7526
`
`
`
`directly
`
`Defendants propose that communication within a virtual private network is “direct” based
`
`
`on arguments that VimetX made to the United States Patent and Trademark Office (“PTO”) to
`
`overcome rejections based on the Aventail reference during reexamination of the ‘135 Patent,l
`
`
`
`
`First, Aventail has not been shown to demonstrate that computers connected via
`
`the Aventail system are able to communicate with each other as though they were
`on the same network. .
`.
`
`.
`
`
`Second, according to Aventail, Aventail Connect’s fundamental operation
`
`EmeempaHbE—wnh—usefi—Hansnnttmg—datathatissensitfietenetwerk
`'F
`.
`
`Third, Aventail has not been shown to disclose a VPN because computers
`
`connected according to Aventail do not communicate directly with each other.
`
`
`Docket No. 182 Attach. 16, at 5—7. Defendants argue that VirnetX‘s third distinction warrants a
`
`finding that communication over a virtual private network must be direct.
`
`VirnetX argues that its statements during reexamination are not a clear disavowal of
`
`
`claim scope. Rather, VirnetX contends that it “overcame Aventail on the ground that Aventail
`
`did not teach a VPN at all.” Docket No. 173, at 8. However, the statements made by VirnetX—
`
`
`particularly points one and three—reveal that the reason Aventail did not disclose a VPN was
`
`because it did not permit direct communication between the source and target computers.
`
`—Vfirnd?6furfimrarguesmmfidmnmdeadydfiawm1fainrscop€reganfingmyoneof
`
`the three distinctions between Aventail and a VPN. For support, VirnetX relies on Momentus
`
`
`Golf, Inc. v. Swingn'te GolfCorp., 187 Fed. App’x 981 (Fed. Cir. 2006), which involved a patent
`
`directed to a golf club swing aide. During prosecution of the Momemus Golf patent, the
`
`
`
`—apphcanfifified“AhofiowdevfiethlG—“S%chb%wadweig%canmtmefifi
`
`
`
`
`
`I‘ n
`u
`“|
`
`SOCKS server.
`
`
`
`
`New Bay Capital, LLC
`Ex.1013-Page 6 of31
`
`New Bay Capital, LLC
`Ex.1013-Page 6 of 31
`
`

`

`
`Case 6:10—ov—OO417—LED Document 266
`Filed 04/25/12 Page 7 of 31 PageID #: 7527
`
`
`
`requirement in applicant’s claims that the center of gravity of the trainer be substantially at the
`
`center of a solid round stock.” Momentus Golf, 187 Fed. App’x at 984 (quoting prosecution
`
`
`history) Thedistfificouflhddmmmisstammentmresentedwmsavowdfiflgdflumnfls—
`
`with 10725% club head weight because they would not meet the center of gravity requirement.
`
`
`Id. at 982. The Federal Circuit agreed that the district court‘s interpretation was a fathomable
`
`one. Id. at 983—84. However, it reversed the district court because another interpretation was also
`
`‘9, anll‘
`
`
`clearly disavowed hollow clubs with 10—25% club head weight. Id. at 984 (emphasis added). The
`
`
`mommmmmmmnywmmmmmmm
`
`
`10—25% club head weight or (2) hollow clubs with 10—25% club head weight. In light of the
`
`
`competing interpretations, the Federal Circuit determined that there was only a disclaimer of the
`
`more narrow interpretation.
`
`The instant case does not present such an ambiguous statement. VirnetX stated that
`
`
`
`
`
`.“Aventail has not been shown to disclose the VPN . . for at least three reasons.” Docket No. 182
`
`Attach. 16, at 5. VirnetX then proceeded to independently present and discuss each of the three
`
`
`
`at 5—6 (discussing the first reason); id. at 6—7 (discussing the second reason); id. at 7 (discussing
`
`
`the third reason). In Momentus Golf, the applicant combined two potential distinctions in a single
`
`sentence, creating ambiguity as to whether the distinctions were independent or intertwined.
`
`mvwwmmmmmmmmommmm—
`
`alone, served to distinguish the claimed VPN from the Aventail reference. See Andersen Corp. v.
`
`
`Fiber Composites, LLC, 474 F.3d 1361, 13721 (Fed. Cir. 2007) (“An applicant‘s invocation of
`
`
`multiple grounds for distinguishing a prior art reference does not immunize each of them from
`
`
`
`
`
`New Bay Capital, LLC
`ExflO’IS-Page 7 of31
`
`New Bay Capital, LLC
`Ex.1013-Page 7 of 31
`
`

`

`Filed 04/25/12 Page 8 of 31 PageID #: 7528
`Case 6:10—ov—OO417—LED Document 266
`
`
`being used to construe the claim language”). Accordingly, the Court finds that the claimed
`.
`.
`.
`.
`.
`.
`2
`“Virtual private networ ” requires direct communication between member computers.
`
`
`fl—e (:
`l
`
`l
`
`(L
`
`'l
`
`I
`
`'
`
`l
`
`l
`
`I77
`
`(L
`
`l
`
`I
`
`l:
`
`l
`
`I':|]
`
`privately and directly communicate with each other by encrypting traffic on insecure paths
`
`between the computers where the communication is both secure and anonymous.”
`
`virtual private link
`
`
`VirnetX proposes “a communication link that permits
`
`computers
`
`to privately
`
`communicate with each other by encrypting traffic on insecure communication paths between the
`
`
`—eompfiers;9efendanfi.exwfimemoAasfiaenfifimpmpese“aanmavfiuapmfie
`
`network.” The Aastra entities propose “a link in a virtual private network that accomplishes data
`
`
`security and anonymity through the use of hop tables.”
`
`VirnetX’s proposed construction closely tracks its proposal for “virtual private network,”
`
`replacing “a network of computers which” with “a communication link that permits computers
`
`
`
`
`
`the computers are linked together;to.” “Network of computers” implies that likewise a
`
`“communication link that permits computers [to communicate]” implies a computer network.
`
`Defendants also note the similaritv between VirnetX’s proposed construction of “virtual
`
`private network” and “virtual private link.” Defendants contend that VimetX’s proposal
`
`is
`
`
`
`.. .”.‘ti:
`
`
`
`Jan. 5, 2012. As a simplification, Defendants propose “a link in a virtual private networ
`
`
`The Aastra entities argue that a virtual private link should be limited to virtual private
`
`network links that use hop tables to achieve data security and anonymity. An embodiment of
`
`
`
`the Mar/(man hearingHIthat
`2 Defendants stipulated at
`they were not arguing “directly” requires a direct
`
`,
`.
`.
`i
`i
`,,
`.
`Big 49_an Jan-2017131111 1 D find 111: m,le”'n‘(1 1h”
`
`conununication do not impede “direct" conununication between a client and target computer.
`
`
`New Bay Capital, LLC
`Ex.1013-Page 8 of31
`
`New Bay Capital, LLC
`Ex.1013-Page 8 of 31
`
`

`

`
`Case 6:10—cv—00417—LED Document 266
`Filed 04/25/12 Page 9 of 31 PageID #: 7529
`
`
`
`claim 13 of the ‘135 Patent, which contains the term “virtual private link,” is depicted in Figure
`
`31. A detailed description of this embodiment is also provided in the specification. See ‘135
`
`
`Patent cols 4414—4535 ThisWSW tables; thus Aastra
`
`argues that this limitation should be imported into the claims.
`
`
`The Court rejects Aastra‘s attempt to incorporate limitations of a preferred embodiment
`
`into the claims. See Falcma v. Kent State Univ, 669 F.3d 1349, 1355 (Fed. Cir. 2012) (cautioning
`
`
`
`notes that the use of hopping is one option for accomplishing the data security and anonymity
`
`
`W.tfiefifimm.W—13W,W3Wmamm
`
`
`transport server 3102 to allocate a hopping table (or hopping algorithm or other regime) for the
`
`"37
`purpose of creating a VPN with client 3103 (emphasis added)). Thus, the applicants envisioned
`
`alternate methods of implementing data security and anonymity beyond hopping tables, and
`
`importing the hopping limitation into the claims is inappropriate.
`
`
`The patent specification, in the detailed description of Figure 31, uses the term virtual
`
`private network and virtual private link interchangeably. Compare id. col. 44:3740 (“When a
`
`
` mammmmnm
`
`. .”), with id. col. 45: 10—13 (noting that the signaling
`.
`between the user and the transport server .
`
`
`server requests the transport server to create a hopping table for the purpose of creating a VFN
`
`with client 3103.”), and id. col. 45:32—35 (“After a VPN has become inactive for a certain time
`
`pefiod®gmehmrl$eVENcanbewMaficaflgutomMManspofiserw3LQZm
`
`
`signaling server 3101.”); see Nystrom v. Trex Co, Inc, 424 F.3d 1136, 1143 (Fed. Cir. 2005)
`
`
`(“Different terms or phrases in separate claims may be construed to cover the same subject
`
`
`matter where the written description and prosecution history indicate that such a reading of the
`
`
`
`
`
`New Bay Capital, LLC
`Ex.1013-Page 9 of31
`
`New Bay Capital, LLC
`Ex.1013-Page 9 of 31
`
`

`

`
`Case 6:10—cv—00417—LED Document 266
`Filed 04/25/12 Page 10 of 31 PageID #: 7530
`
`
`
`terms or phrases is proper”). Finally, VirnetX’s and Defendants’ proposed constructions of
`
`virtual private link are very similar to their proposed constructions for virtual private network.
`
`
`—Accmmngl¥4he_CmMJomtmes“wfiudpfivamhnk”u“awfiudpfivaRDen&oflng—
`
`previously defined.”
`
`
`secure communication link
`
`VirnetX proposes “an encrypted communication link.” Defendants propose “virtual
`
`
`private network communication link.” The parties in A/[icrosofl agreed that this term, as used in
`
`the ‘759 Patent, did not require construction because the claims themselves provide a definition
`
`
`efthe term. (W, ”999 US. Dist. LEXPS 65667, at >5-43. Forinstanee, claim 1 states: “the
`
`
`secure communication link being a virtual private network communication link over the
`
`
`computer network.” ‘759 Patent col. 57:20—22. Here, the parties also agree that, as to the ‘759
`
`Patent, the term means “virtual private network communication link.” However, the claims of the
`
`‘504 and ‘211 Patents use this term without further defining it. Thus, the parties dispute the
`
`construction of the term as used in the ‘504 and ‘211 Patents.
`
`VirnetX contends that “secure” means the link uses some form of data encryption,
`
`
`highlighting the following passage from the ‘504 Patent specification: “Data securitv is usuallv
`
`tackled using some form of data encryption.” ‘504 Patent col. 1:55—56. VirnetX argues that the
`
`
`
`to limit “secure communication link” to that interpretation. VirnetX further argues Defendants’
`
`
`proposal improperly imports a limitation from the preferred embodiment, which discloses a
`
`secure communication link that is also a virtual private network communication link. VirnetX
`
`
` Wmmmam
`
`
`private network communication link for all possible embodiments of the claims.” Docket No.
`
`
`
`10
`
`
`New Bay Capital, LLC
`Ex.1013-Page T0 of31
`
`New Bay Capital, LLC
`Ex.1013-Page 10 of 31
`
`

`

`
`
`Case 6:10—cv—00417—LED Document 266 Filed 04/25/12 Page 11 of31 PageID #: 7531
`
`
`
`192, at 4. Finally, VirnetX argues that it did not narrow the interpretation of “secure
`
`communication link” during the prosecution of the ‘504 and ‘211 Patents.
`
`3|
`
`I
`
`"I'I'Iil'li
`
`3|
`
`Invention: “The secure communication link is a virtual private network communication link over
`
`
`the computer network.“ ‘504 Patent col. 6:61—62. Defendants further argue that the detailed
`
`description of the invention also uses the terms “secure communication link” and “virtual private
`
` n
`
`rk mmni
`
`inlink” nnm l Dfn n
`
`l hihlih
`
`irnX’
`
`r mn
`
`regarding “secure communication link” while prosecuting US. Patent No. 8,051,181 (“the ‘181
`
`
`
`’,II
`
`I“
`
`..|.
`
`~
`
`
`The ‘ 181 Patent is related to the patents-in-suit; it is a division of a continuation-in-part
`
`
`of the ‘783 Application that serves as an ancestor application for all of the patents—in—suit. The
`
`Federal Circuit has held that arguments to the PTO regarding one patent application are
`
`applicable to related patent applications. See Microsoft Corp. v. Mulii-I'ech 532s, Inc, 357 F.3d
`
`
`
`
`
`is relevant1340, 1349 (Fed. Cir. 2004) (“[T]he prosecution history of one patent to an
`
`understanding of the scope of a common term in a second patent stemming from the same parent
`
`
`
`may be applicable to a previously filed application. See Verizon Servs. Corp. v. Vonage Holdings
`
`Corp, 503 F73d l295, I307 CF ed. Cir. 2007) (rejecting the argument that a disclaimer should not
`
`apply because it occurred after the patent under consideration had issued). Here, the ‘181 Patent
`
`
`issuedafterallofthepatents-in-wij Itsapplicanonsvasfilecflateuhanjheapphcanonsfofihe—
`
`
`patents-in-suit except for the ‘211 Patent, which was filed approximately six months earlier.
`
`
`When prosecuting the “181 Patent, VirnetX distinguished the Aventail reference from the
`
`
`“secure communication link” limitation using arguments nearly identical
`to those discussed
`
`
`ll
`
`
`New Bay Capital, LLC
`ExflO’lB—Page 11 of31
`
`New Bay Capital, LLC
`Ex.1013-Page 11 of 31
`
`

`

`
`Case 6:10—cv—00417—LED Document 266
`Filed 04/25/12 Page 12 of 31 PageID #: 7532
`
`
`earlier regarding Aventail and the “virtual private networ ” term. VirnetX argued that Aventail
`
`failed to disclose a “secure communication link” for the same three reasons asserted in the ‘ 135
`
`
`—Leexamina1ion__CampazeDocketNo L82Attach LQMS—7Carg11mentLregardingjdfiuaJ—
`
`l. at 678 (arguments regarding
`private network” and Aventail), with Docket No. 202 Attach.
`
`
`“secure communication link“ and Aventaib. Therefore” for the same reasons stated earlier
`
`regarding “virtual private network,” a “secure communication link” also requires direct
`
`
`
`mmni 1n
`
`nin
`
`“Secure communication link” was originally used in the claims of the ‘759 Patent, which
`
`
`wasalmmmsuemhfiwmzyffirerejmepaniesageedmmfididnmmqmmnmion—
`
`
`because the claim language itself defined the term as “being a virtual private network
`
`
`communication link.” ‘759 Patent col. 57:20722. However, the later—filed applications that issued
`
`as the ‘504 and ‘211 Patents removed this defining language from the claims. Accordingly the
`
`term is not so limited in the ‘504 and ‘211 Patents as in the ‘759 Patent.
`
`
`Defendants argue that the Summary of the Invention defined a secure communication
`
`link as a virtual private network communication link. However, this discussion in the Summary
`
`
`
`
`invention, a user can conveniently
`According to one aspect of the present
`
`establish a VPN using a “one—click” .
`.
`. technique without being required to enter
`
`[information] for establishing a V‘PlTThe advantages of the present invention are
`provrded by a method for establishing a secure communication link .
`.
`.
`.
`
`
`‘504 Patent col. 6:36—42. Thus, the advantage of being able to seamlessly establish a one-click
`
`
`VPN is provided by “a method for establishing a secure communication link.” The description
`
`
`
`6:43—7 :10 (describing the one-click embodiment). It is within this description of the preferred
`
`
`embodiment that the specification acknowledges that the “secure communication link is a virtual
`
`12
`
`
`New Bay Capital, LLC
`Ex.1013-Page T2 of31
`
`New Bay Capital, LLC
`Ex.1013-Page 12 of 31
`
`

`

`Filed 04/25/12 Page 13 of 31 PageID #: 7533
`Case 6:10—cv—00417—LED Document 266
`
`
`private network communication link.” Id. col. 6:61—63. The patentee is not acting as his own
`
`lexicographer here; rather, he is describing a preferred embodiment. The claims and specification
`
`
`fiM‘so4M‘mmwmmpmmwmmmem
`
`virtual private network limitation originally present in the ‘759 Patent claims. Thus, secure
`
`
`communication link shall be interpreted without this limitation in the ‘304 and 711 Patents.
`
`VirnetX proposes that a secure communication link is an encrypted link. However, claim
`
`
`28 ofthe ‘504 Palent3 covqs “Itlhe system of claim 1, wherein the secure eemmunieatien link
`
`uses encryption.” ‘504 Patent col. 57:17—18. VimetX’s proposal seeks to import a limitation
`
`
`
`differentiation. See Curtis‘s-Wright Flow Control Corp. v. Velan, 1110.7 438 F.3d 1374, 1380 (Fed.
`
`
`Cir. 2006) (“‘[C]laim differentiation” refers to the presumption that an independent claim should
`
`not be construed as requiring a limitation added by a dependent claim”). The specification notes
`
`that “[d]ata security is usually tackled using some form of data encryption.” ‘504 Patent col.
`
`1:55—56 (emphasis added). Therefore, encryption is not the only means of addressing data
`
`security. Accordingly, a secure communication link is one that provides data security, which
`
`.
`
`l
`
`l
`
`
`.
`.
`
`The Court construes “secure communication link” as “a direct communication link that
`
`
`provides data security. 4
`
`
`
`
`
`
`
`3 Claim 28 of the ‘211 Patent is similar.
`4 As the Court discussed earlier, the ‘7 59 Patent claims further limit the secure communication link recited therein.
`
`. 1.11:1“
`.
`l
`.
`l
`.
`1
`.’l
`'
`recited in the “759 Patent claims is a “virtual private network conuuunication link."
`
`"l'l”
`
`l3
`
`
`New Bay Capital, LLC
`Ex.1013-Page 13 of31
`
`New Bay Capital, LLC
`Ex.1013-Page 13 of 31
`
`

`

`
`Case 6:10—cv—00417—LED Document 266
`Filed 04/25/12 Page 14 of 31 PageID #: 7534
`
`
`domain name service
`
`VirnetX proposes “a lookup service that returns an IP address for a requested domain
`
`
`name,” adopting the Court’s previous construction of this term in A/ficrosofi. Defendants propose
`
`to append “to the requester” to VirnetX’s proposed construction.
`
`
`
`
`VirnetX provides an expert declaration stating that one of skill in the art, after reading the
`
`
`specification, would understand that a domain name service does not necessarily return the
`
`requested TP address to the requester, See Docket No, 173 Attach. 17 W 7—8 (stating that in the
`
`
`eofiefiofaDNSprexy,$ePaddre%mayherfiumed%oWiginflwwesfingcfiefi,$e
`
`
`proxy, or both). VirnetX also argues that the specification envisions a domain name service that
`
`
`does not always return an address to the requester. For instance, the specification states:
`
`According to certain aspects of the invention, a specialized DNS server traps DNS
`
`—requestsand,ifthemquestisfiomaspeaalQLpeofuser...,thesemerdoesnm
`return the true IP address of the target node, but instead automatically sets up a
`virtual private network between the target node and the user.
`
`
`O
`O
`Cu
`
`
`Court’s Microsofi construction by arguing that a domain name service does not necessarily
`
`
`return the requested TP address to the requester.
`
`
`VirnetX’s expert explains that “in one mode, the domain name request can be received by
`
`
`aBNSproxyerNSmoxymodfiejwfithhrmmrmarforwmdflwmmmafimercfion—
`
`
`that can return an IP address” Docket No. 173 Attach. l7 1l 8. Thus, VirnetX argues, a domain
`
`
`name request may cause an TP address to be returned “to the client, or to a DNS proxy .
`
`.
`
`.
`
`, or
`
`
`MVMVMetX’sexpenEefleaNewmscfibmgascenanoJaafledmme‘Bngemm
`
`cited above by VirnetX. This scenario is further described in detail in the specification and
`
`
`depicted in Figure 26. See T35 Patent col. 38zl3—42 (describing the operation of the system
`
`
`l4
`
`
`New Bay Capital, LLC
`m-Page 14 of31
`
`New Bay Capital, LLC
`Ex.1013-Page 14 of 31
`
`

`

`Filed 04/25/12 Page 15 of 31 PageID #: 7535
`Case 6:10—cv—00417—LED Document 266
`
`
`depicted in Figure 26), VimetX asserts that Defendants’ proposed construction precludes this
`
`preferred embodiment.
`
`
`Contrary to VimetX’s argumenLJlefendantstLoposedJnnfianonudoeLnotuprechldLa—
`
`preferred embodiment. The “specialized” or “modified” DNS server
`
`referenced in the
`
`
`specification is shown as 2602 in Figure 26. This modified DNS server contains a DNS proxy
`
`function and a standard DNS server function. Requests for non-secure sites are passed through to
`
`
`the D SS semer, and an IP address is returned te the requesting elient In this case two separate
`
`domain name requests are effectively being made: (1) between the client computer 2601 and the
`
`mmmmmmmmmmfi
`
`the original client request is for a secure site, then the DNS Proxy 2610 establishes a VPN
`
`
`connection between the client and the secure site. The specification explains the final stages of
`
`this process:
`
`
`Thereafter, DN S proxy 2610 returns to user computer 2601 the resolved address
`passed to it by the gatekeeper (this address could be different from the actual
`
`target computer) 2604, preferably using a secure administrative VPN. The address
`that is returned need not be the actual address of the destination computer.
`
`Id. col. 383642. The DNS Proxy 2610, operating as an internal component of the modified
`
`
`DNS server 2602, returns an address to the requester, the client computer 2601. Thus, viewing
`
`the modified DNS server 2602 as a black box, it returned an address to the requesting client
`
`computer,
`
`For these reasons, the Court finds that a domain name service inherently returns the IP
`
`
`address for a requested domain name to the requesting party. The Court construes “domain name
`
`
`seMce”%“abekupseMcemMraurmmEaddregfmamqu%te¢W
`
`requester.”
`
`
`
`
`New Bay Capital, LLC
`Ex.1013-Page 15 of31
`
`15
`
`New Bay Capital, LLC
`Ex.1013-Page 15 of 31
`
`

`

`
`Case 6:10—cv—00417—LED Document 266
`Filed 04/25/12 Page 16 of 31 PageID #: 7536
`
`
`domain name
`
`VirnetX proposes the same construction adopted by the Court in Microsoft: “a name
`
`
`corresponding to an IP address.” Defendants propose “a hierarchical sequence of words in
`
`decreasing order of specificity that corresponds to a numerical TP address.” In Microsoft, the
`
`
`
`that analysis is incorporated herein. See Microsoft, 2009 US. Dist. LEXIS 65667, at *24—25. For
`
`
`the same reasons stated in Zl/[icrosoft,
`the Court construes “domain name” as “a name
`
`corresponding to an IF address.”
`
`BNSproxyserver
`
`VirnetX proposes “a computer or program that responds to a domain name inquiry in
`
`
`place of a DNS/”Defendants propose “a computer or program that responds to a domain name
`
`inquiry in place of a DNS, and prevents destination servers from determining the identity of the
`
`entity sending the domain name inquiry.” VirnetX’s proposal and the first portion of Defendants”
`
`proposal reflect the construction adopted by this Court in Microsoft. Id. at *39. Here, the dispute
`
`is whether a DNS proxy server “prevents destination servers from determining the identity of the
`
`
`entity sending the domain name inquiry.”
`
`Defendants derive support for their proposed limitation directly from the Background of
`
`
`,|.. :3I | I
`
`
`
`
`
`originating clients.” ‘ 135 Patent col. 1:49—50. VirnetX argues that this statement should be read
`
`
`in the context of the sentence that precedes it: "To hide traffic from a local administrator or ISP,
`
`a user can employ a local proxy server in communicating over an encrypted channel with an
`
`eutsideprexysuchthatthelecal administratererISP enlJyLseesthe encrypted traffic.”ld cel.
`
`lI46—49. VirnetX contends that these statements are not regarding all proxy servers, but merely
`
`
`detail how proxy servers may be configured to achieve anonymity.
`
`16
`
`
`New Bay Capital, LLC
`Ex.1013-Page T6 of31
`
`New Bay Capital, LLC
`Ex.1013-Page 16 of 31
`
`

`

`
`Case 6:10—cv—00417—LED Document 266
`Filed 04/25/12 Page 17 of 31 PageID #: 7537
`
`
`VirnetX also argmes that adopting Defendants’ construction would read out a preferred
`
`embodiment disclosed in Figure 26 of the ‘135 Patent. In Figure 26, user computer 2601, after
`
`'IE
`
`.
`
`I'I'IE
`
`I'
`
`Unsecure Target Site 2611. In this configuration. the DNS Proxy does not prevent the destination
`
`
`servers (secure and unsecure target websites) from learning the identity of the originating client
`
`(user computer). Rather, the DNS Proxy enables direct communication between the originating
`
`
`
`
`rejected. See Globetrotter Software, Inc. v. Elan Computer Grp., Inc, 362 F.3d 1367, 1381 (Fed.
`
`
` orpzeezfimcm'rm'
`
`
`claim ‘is rarely, if ever, correct.” (quoting lr’itronics Corp. v. Conceptronic, 90 F .3d 1576, 1583
`
`
`(Fed. Cir. 1996)».
`
`For these reasons and those stated in Microsoft, see 2009 US. Dist. LEXIS 65667, at
`
`*39—42, the Court construes “DN S proxy server” as “a comput

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