throbber
Case 6:10-cv-00417-LED Document 182 Filed 12/07/11 Page 1 of 37 PageID #: 4276
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`TYLER DIVISION
`
`
`
`VirnetX Inc.,
`
`
`
`v.
`
`Cisco Systems, Inc., Apple Inc.,
`Aastra USA, Inc., Aastra Technologies Ltd.,
`NEC Corporation, and NEC Corporation of
`America,
`
`
`
`
`Civil Action No. 6:10-cv-00417-LED
`JURY TRIAL DEMANDED
`
`
`
`
`Plaintiff,
`
`Defendants. 
`
`
`
`
`
`DEFENDANTS’ RESPONSIVE CLAIM CONSTRUCTION BRIEF
`
`
`
`
`
`
`
`
`VIRNETX EXHIBIT 2030
`Mangrove v. VirnetX
`Trial IPR2015-01046
`
`Page 1 of 37
`
`

`
`Case 6:10-cv-00417-LED Document 182 Filed 12/07/11 Page 2 of 37 PageID #: 4277
`
`TABLE OF CONTENTS
`
`I. 
`
`INTRODUCTION ..................................................................................................................1 
`
`II.  LEGAL STANDARDS ..........................................................................................................1 
`
`III.  PATENTS-IN-SUIT ...............................................................................................................1 
`
`IV.  DISPUTED CLAIM CONSTRUCTIONS .............................................................................2 
`
`A.  Disputes Concerning Virtual Private Networks ............................................................. 2 
`
`1.  Virtual Private Network ......................................................................................... 2 
`
`2.  Virtual Private Link ............................................................................................... 7 
`
`3.  Secure Server ......................................................................................................... 8 
`
`4.  Secure Communication Link ............................................................................... 10 
`
`B.  Disputes Relating to Domain Names ............................................................................ 11 
`
`1.  Domain Name ...................................................................................................... 11 
`
`2.  Domain Name Service ......................................................................................... 13 
`
`3.  Secure Domain Name Service ............................................................................. 14 
`
`4.  Domain Name Service System ............................................................................ 16 
`
`5.  DNS Proxy Server ............................................................................................... 17 
`
`C.  Disputes Concerning Indicating, Indications, and Indicate .......................................... 19 
`
`1.  An Indication That The Domain Name Service System Supports Establishing A
`Secure Communication Link ............................................................................... 19 
`
`D.  Disputes Concerning the Scope of Virtual Private Networks ...................................... 21 
`
`1.  “Between [A] and [B]” ........................................................................................ 21 
`
`2.  Target Computer .................................................................................................. 22 
`
`E.  Disputes Relating to Websites ...................................................................................... 25 
`
`1.  Web Site ............................................................................................................... 25 
`
`2.  Secure Web Computer ......................................................................................... 27 
`
`F.  Disputes pertaining to the ‘759 Patent .......................................................................... 28 
`
`ii
`
`Page 2 of 37
`
`

`
`Case 6:10-cv-00417-LED Document 182 Filed 12/07/11 Page 3 of 37 PageID #: 4278
`
`1.  Cryptographic Information .................................................................................. 28 
`
`2.  Enabling A Secure Communication Mode Of Communication .......................... 29 
`
`G.  Dispute Regarding The “Generating” Limitation ......................................................... 30 
`
`
`
`
`
`iii
`
`Page 3 of 37
`
`

`
`Case 6:10-cv-00417-LED Document 182 Filed 12/07/11 Page 4 of 37 PageID #: 4279
`
`TABLE OF AUTHORITIES
`
`Cases 
`Am. Piledriving Equip. v. Geoquip, Inc.,
`637 F.3d 1324 (Fed. Cir. 2011) ............................................................................................... 7
`Ciena Corp. v. Nortel Networks Inc.,
`No. 2:05-CV-14, 2006 U.S. Dist. LEXIS 97450 (E.D. Tex. Apr. 25, 2006) ................... 17, 21
`Eon-Net LP v. Flagstar Bancorp,
`653 F.3d 1314 (Fed. Cir. 2011) ............................................................................................. 18
`Every Penny Counts, Inc. v. Am. Express Co.,
`563 F.3d 1378 (Fed. Cir. 2009) ............................................................................................... 4
`Golden Hour Data Sys. v. emsCharts, Inc.,
`614 F.3d 1367 (Fed. Cir. 2010) ............................................................................................. 18
`i4i Ltd. P’ship v. Microsoft Corp.,
`598 F.3d 831 (Fed. Cir. 2010) ............................................................................................... 24
`Lindemann Maschinenfabrik GMBH v. Am. Hoist & Derrick Co.,
`730 F.2d 1452 (Fed. Cir. 1984) ............................................................................................. 26
`Merck & Co., Inc. v. Teva Pharms. USA, Inc.,
`395 F.3d 1364 (Fed. Cir. 2005) ............................................................................................. 24
`Microsoft Corp. v. Multi-Tech. Sys.,
`357 F.3d 1340 (Fed. Cir. 2003) ............................................................................................. 17
`Momentus Golf, Inc. v. Swingrite Golf Corp.,
`187 F. App’x. 981 (Fed. Cir. 2006) ......................................................................................... 6
`Omega Eng'g., Inc. v. Raytek Corp.,
`334 F.3d 1314 (Fed. Cir. 2003) ............................................................................................. 10
`On Demand Mach. Corp. v. Ingram Indus.,
`442 F.3d 1331 (Fed. Cir. 2006) ............................................................................................. 30
`Phillips v. AWH Corp.,
`415 F.3d 1303 (Fed. Cir. 2005) ............................................................................................. 12
`Seachange Int’l, Inc. v. C-COR Inc.,
`413 F.3d 1361 (Fed. Cir. 2005) ............................................................................................... 7
`Vivid Techs., Inc. v. Am. Science & Eng'g, Inc.,
`200 F.3d 795 (Fed. Cir. 1999) ................................................................................................. 7
`
`
`
`iv
`
`Page 4 of 37
`
`

`
`Case 6:10-cv-00417-LED Document 182 Filed 12/07/11 Page 5 of 37 PageID #: 4280
`
`I.
`
`INTRODUCTION
`
`To prevail at trial in its litigation against Microsoft, VirnetX relied on this Court’s
`
`constructions of key language from the patents-in-suit—such as “virtual private network” and
`
`“secure domain name.” VirnetX then turned around and told the Patent Office that this Court’s
`
`constructions were wrong. Specifically, in distinguishing prior art in subsequent reexamination
`
`proceedings, VirnetX argued that the terms “virtual private network” and “secure domain name”
`
`contain limitations found nowhere in this Court’s constructions.
`
`Now VirnetX seeks to reverse course once again. While conceding that its reexamination
`
`arguments require narrowing of this Court’s prior definition of “secure domain name,” VirnetX
`
`asks this Court not only to disregard its reexamination arguments concerning “virtual private
`
`network,” but also to revisit and broaden the construction of that language from the Microsoft
`
`case. VirnetX should not be permitted to expand and contract the scope of the asserted claims to
`
`suit whatever validity or infringement dispute it currently confronts. Defendants’ proposed
`
`claim constructions avoid that result by applying settled claim construction principles to interpret
`
`the asserted claims consistent with VirnetX’s statements to the Patent Office, both in the original
`
`applications and during subsequent reexamination proceedings.
`
`II.
`
`LEGAL STANDARDS
`
`This Court is familiar with the pertinent claim construction principles. For convenience,
`
`Defendants cite to relevant authority in the body of the brief.
`
`III.
`
`PATENTS-IN-SUIT
`
`The six Patents-in-Suit are closely related. The specifications of the ‘135 and ‘151
`
`Patents are substantively identical, as are the specifications of the ‘180, ‘759, ‘504, and ‘211
`
`
`
`Page 5 of 37
`
`

`
`Case 6:10-cv—00417-LED Document 182
`
`Filed 12/07/11 Page 6 of 37 PagelD #: 4281
`
`Patents.‘ The latter patents are based on a continuation-in—part to the ‘ 135 Patent, adding new
`
`material to the specification, most notably a section titled “One-Click Secure On-Line
`
`Communications and Secure Domain Name Service” and related Figures 34 and 35.
`
`Several of the Patents-in-Suit have been subject to reexamination. The Patent Office
`
`granted Microsofi’s request for interpartes reexamination of the ‘I35 and ‘I80 Patents, but
`
`confirmed the claims after Microsoft settled with VirnetX and withdrew from the
`
`reexaminations. Since that time, the Patent Office has initiated new reexaminations of the ‘ 135,
`
`‘151, ‘ 180, and ‘759 Patents.
`
`IV.
`
`DISPUTED CLAINI CONSTRUCTIONS2
`
`A.
`
`Disputes Concerning Virtual Private Networks
`
`1.
`
`Virtual Private Network
`
`communication is both secure and anon n ous
`
`Virtual Private Network
`
`VirnetX’s Proposed Construction
`a network of computers which
`privately communicate with each
`other by encrypting traffic on
`insecure communication paths
`between the con uters
`
`Defendants’ Proposed Construction
`a network of computers which privately and
`directly communicate with each other by
`encrypting traffic on insecure communication
`paths between the computers where the
`
`Proceedings that occurred afier this Court’s Claim Construction Order in the Microsofi
`
`litigation warrant modification of the Court’s pervious construction of “virtual private networ ”
`
`(1) to expressly reflect this Court’s prior ruling that communications in a “virtual private
`
`networ ” are both secure and anonymous, and (2) to specify that the claimed network of
`
`computers directly communicate with each other, as Vi1netX represented to the Patent Office in
`
`subsequent reexamination proceedings.
`
`1 Not all of the patents or claims from those patents are asserted against all of defendants. Each Defendant joins in
`this brief to the extent the disputed term appears in the patent claims asserted against that Defendant.
`2 The parties agree that a person of ordinary skill in the art would have a Master’s degree in computer science or
`computer engineering. or in a related field, as well as about two years of experience in computer networking and in
`some aspect of security with respect to computer networks. The parties also agree that such person would have
`actual experience with networking protocols as well as the security of those protocols.
`
`Page 6 of 37
`
`Page 6 of 37
`
`

`
`Case 6:10-cv-00417-LED Document 182 Filed 12/07/11 Page 7 of 37 PageID #: 4282
`
`a)
`
`Secure And Anonymous
`
`This Court already decided that a virtual private network requires “both data security and
`
`anonymity” (Microsoft case, D.I. 246 (attached as Ex. A) at 8-9) and expressly recognized that
`
`the disclosed virtual private networks were designed to prevent eavesdroppers on insecure
`
`networks from intercepting data and determining which computers were communicating, and
`
`therefore must accomplish both data security and anonymity. Nevertheless, the Court’s prior
`
`Order did not explicitly incorporate those requirements into the text of its construction.3
`
`Defendants’ construction expresses these requirements so as to avoid jury confusion.
`
`In the Microsoft case, Microsoft largely hinged its noninfringement case on the argument
`
`that its accused products did not achieve anonymity. See e.g. Microsoft case, D.I. 393 (attached
`
`as Ex. D) at 62:20-65:15; Microsoft case, D.I. 396 (attached as Ex. F) at 19:4-32:6. Accordingly,
`
`both parties repeatedly referred to an element required by the prior Claim Construction Order but
`
`absent from the express definition of “virtual private network.” While no party disputed that a
`
`“virtual private network” must achieve data security and anonymity4, the parties had to rely on
`
`cross examination to convey those requirements to the jury, thereby complicating the trial and
`
`increasing the risk of jury confusion. Express incorporation of all of the requirements of a
`
`virtual private network into the construction will remove ambiguity and ensure that claim
`
`construction issues are not left to the jury. See Every Penny Counts, Inc. v. Am. Express Co., 563
`
`
`3 After the Court's claim construction order, Microsoft moved to have the “data security and anonymity” language
`incorporated in the Court’s construction of virtual private network. Microsoft case, D.I. 247. Neither party disputed
`that a virtual private network requires anonymity when the Court considered the issue at the pretrial conference.
`Microsoft case, D.I. 339 (attached as Ex. O) at 6:16-14:16. VirnetX went so far as to promise that its expert would
`not contradict that “private” requires both anonymity and security.” Id. at 12:20-13:2. Microsoft eventually agreed
`to rely on cross examination of VirnetX’s expert witnesses, instead of express incorporation into the construction, to
`convey that requirement to the jury. Id. at 14:2-4.
`4 See Microsoft case, D.I. 391 (attached as Ex. B) at 88:18-89:17, 155:8-15; Microsoft case, D.I. 392 (attached as
`Ex. C) at 64:1-71:12, 85:19-89:1, 93:10-15; Microsoft case, D.I. 393 (Ex. D) at 42:1-43:11, 62:20-65:15; Microsoft
`case, D.I. 395 (attached as Ex. E) at 100:12-101:25, 105:1-9; Microsoft case, D.I. 396 (Ex. F) at 19:5-32:6, 70:2-
`88:12, 98:22-109:19, 118:12-121:19, 126:8-18; Microsoft case, D.I. 397 (attached as Ex. G) at 56:3-59:8; Microsoft
`case, D.I. 398 (attached as Ex. H) at 136:12-137:16.
`
`3
`
`Page 7 of 37
`
`

`
`Case 6:10-cv-00417-LED Document 182 Filed 12/07/11 Page 8 of 37 PageID #: 4283
`
`F.3d 1378, 1383 (Fed. Cir. 2009).
`
`In its opening brief, VirnetX now argues—contrary to this Court’s ruling in the Microsoft
`
`case—that a virtual private network does not require anonymity. But the intrinsic evidence
`
`shows otherwise. The Background of the Invention frames the patent as addressing “two
`
`security issues . . . called data security and anonymity.” ‘135 Patent (attached as Ex. 1) at 1:35-
`
`36 (emphasis added). It also explains that anonymity involves “prevent[ing] an eavesdropper
`
`from discovering that terminal 100 is in communication with terminal 110.” Id. at 1:26-27. And
`
`the specification consistently equates the word “private” in “virtual private network” with
`
`“anonymity,” explaining that “[a]nonymity would thus be an issue, for example, for companies
`
`that want to keep their market research interests private.” Id. at 1:32-33 (emphasis added). The
`
`rest of the specification describes ways to solve the twin security issues of data security and
`
`anonymity. Id. at 2:66-3:17, 19:66-20:3, 23:11-36, 37:40-49, 37:63-38:6, 39:29-33. As the
`
`Court previously recognized, because the Detailed Description of the Invention section refers
`
`back to the anonymity features disclosed earlier in the specification, the term VPN requires
`
`anonymity wherever it appears. Ex. A at 8-9.
`
`Ultimately, VirnetX’s claim construction brief simply rehashes a settled dispute from the
`
`Microsoft case about the “purpose” of encapsulation. D.I. 173 at 5. That discussion is beside the
`
`point. For one thing, the aforementioned teachings of the patents-in-suit, which define a virtual
`
`private network as requiring “anonymity,” do not hinge on their use of encapsulation. Ex. 1 at
`
`7:49-58 (describing how anonymity is accomplished by having the destination field of the IP
`
`header point to an intermediary router instead of the ultimate destination). Indeed, this Court’s
`
`Claim Construction Order expressly acknowledges that techniques other than tunneling exist to
`
`achieve anonymity. Ex. A at 9-10. Furthermore, to the extent that “encapsulation” plays a role
`
`4
`
`Page 8 of 37
`
`

`
`Case 6:10-cv-00417-LED Document 182 Filed 12/07/11 Page 9 of 37 PageID #: 4284
`
`in anonymity, the virtual private network described and claimed by the patents-in-suit ensures
`
`anonymity regardless of whether that result is the “purpose.” In any case, encapsulation can
`
`serve several purposes depending on its implementation, including data security and anonymity.
`
`Kelly Decl. at ¶ 5. VirnetX’s reiteration of its arguments from the Microsoft litigation should
`
`again be rejected.
`
`b)
`
`Directly
`
`In reexamination proceedings following this Court’s Claim Construction Order in the
`
`Microsoft case, VirnetX responded to office actions rejecting several claims of the ‘135 and ‘180
`
`Patents in light of the “Aventail” reference. In particular, VirnetX argued that Aventail does not
`
`“disclose a VPN because computers connected according to Aventail do not communicate
`
`directly with each other.” ‘135 reexam (attached as Ex. I) at 5-7 (emphasis added); see also
`
`‘180 reexam (attached as Ex. K) at 11-13. Defendants’ construction incorporates VirnetX’s clear
`
`mandate to the Patent Office that computers in a “virtual private network” communicate directly
`
`with each other, and that absent direct communication between the computers, there is no virtual
`
`private network.
`
`
`
`VirnetX confirmed that a “virtual private network” requires direct communication
`
`between computers by further distinguishing the Aventail reference from the claimed invention:
`
`The [Aventail] client cannot open a connection with the target itself. . . . Instead,
`the client computer and target computer are deliberately separated by the
`intermediate SOCKS server.
`
`Ex. I at 7 (emphasis added); see also Ex. K at 13. VirnetX summarized Aventail by explaining
`
`that, unlike the claimed virtual private network, in Aventail, “[r]egardless of the number of
`
`servers or proxies between the client and target, at least one is required . . . .” Id. (referring to a
`
`network diagram from the Aventail reference). Finally, VirnetX relied on expert testimony that
`
`“Aventail has not been shown to disclose a VPN because computers connected according to
`
`5
`
`Page 9 of 37
`
`

`
`Case 6:10-cv-00417-LED Document 182 Filed 12/07/11 Page 10 of 37 PageID #: 4285
`
`Aventail do not communicate directly with each other.” ‘135 reexam, Nieh declaration (attached
`
`as Ex. J) at ¶ 26 (emphasis added); ‘180 reexam, Nieh declaration (attached as Ex. L) at ¶ 29.
`
`VirnetX therefore repeatedly and clearly confirmed that “virtual private network”
`
`communications must be direct.
`
`Confronted with its own unambiguous statements to the Patent Office, VirnetX protests
`
`that it “was not forced to overcome a reference by disclaiming a certain scope of VPN taught by
`
`Aventail [but rather] overcame Aventail on the ground that Aventail did not teach a VPN at all.”
`
`D.I. 173 at 7-8. This is a difference without a distinction. In arguing that Aventail does not
`
`disclose a VPN, VirnetX clearly defines “virtual private networks” as requiring direct
`
`communications between communicating computers.
`
`Nor can VirnetX escape the consequences of its statements to the Patent Office by
`
`portraying them as a case of ambiguous disclaimer. The disclaimer case VirnetX cites,
`
`Momentus Golf, Inc. v. Swingrite Golf Corp., 187 F. App’x. 981 (Fed. Cir. 2006), concerned an
`
`ambiguity not present here. There, the patentee argued to the Patent Office that “[a] hollow
`
`device having 10-25% club head weight cannot meet the requirement in applicant’s claims that
`
`the center of gravity of the trainer be substantially at the center of a solid round stock.” Id. at
`
`983. The Federal Circuit found that statement to be ambiguous because it was unclear whether
`
`the patent owner was disclaiming (1) devices that were both hollow and had 10-25% head
`
`weight, or (2) devices that either were hollow or that had 10-25% head weight. Id. at 983-84.
`
`Here, in contrast, VirnetX unequivocally argued that Aventail does not disclose a VPN
`
`because it does not teach direct communication between computers. VirnetX also attempted to
`
`distinguish Aventail on the same grounds in the reexamination of the ‘180 Patent. Ex K at 11-
`
`6
`
`Page 10 of 37
`
`

`
`Case 6:10-cv-00417-LED Document 182
`
`Filed 12/07/11 Page 11 of 37 PagelD #: 4286
`
`13. VirnetX suggests that because it distinguished Aventail on additional independent grounds,5
`
`there cannot be a clear disclaimer. But the case law makes it clear that “an applicant's argument
`
`that a prior art reference is distinguishable on a particular ground can serve as a disclaimer of
`
`claim scope even if the applicant distinguishes the reference on other grounds as well.” Am.
`
`Piledriving Equip. v. Geoquip, Inc., 637 F.3d 1324, 1336 (Fed. Cir. 2011). Furthermore, “[A]n
`
`applicant’s argument made during prosecution may lead to a disavowal of claim scope even if
`
`the Examiner did not rely on the argument.” Seachange Inf’I, Inc. v. C-COR Inc., 413 F.3d
`
`1361, 1374 (Fed. Cir. 2005). As such, the Court should construe virtual private network to
`
`require direct communications.6
`
`2.
`
`Virtual Private Link
`
`VirnetX’s Proposed Construction
`
`Defendants’ Proposed Construction
`
`between the co uters
`
`Virtual Private Link
`
`a communication link that permits
`computers to privately communicate
`with each other by encrypting trafic
`on insecure communication paths
`
`a link in a virtual private network
`
`a)
`
`Defendants’ Construction of Virtual Private Link
`
`Defendants agree that a “virtual private link,” as referenced in claim 13 of the ‘ 135
`
`Patent, is a link in a virtual private network.
`
`b)
`
`Aastra’s Construction of Virtual Private Link
`
`Defendant Aastra submits that a virtual private link (“VP ” is “a link in a virtual private
`
`5 During reexamination, VirnetX also argued that two additional reasons existed why Aventail did not disclose
`VPN. In particular, VirnetX argued that computers connected via the Aventail system are not able to communicate
`with each other as though they were on the same network, and that Aventail’s operation is incompatible with users
`transmitting data that is sensitive to network information. Ex. I at 5-7; see also Ex. K at 11-13. Defendants do not
`believe that these additional VPN requirements are relevant to the disputed issues in the current case and therefore
`have not included them in their proposed construction. See Vivid TecI1s., Inc. 1'. Am. Science & Eng’g, Inc. , 200 F.3d
`795. 803 (Fed. Cir. 1999) (“[O]nly those temis need be construed that are in controversy. and only to the extent
`necessary to resolve the controversy”). However, should a dispute arise. Defendants reserve the right to seek
`further clarification from the Court or other appropriate remedies.
`6 VirnetX admits that it likewise narrowed the definition of “secure domain name service” during reexamination and
`that the Court’s prior construction of that term should be narrowed accordingly. See D.I. 173 at 17-18.
`
`Page 11 of 37
`
`Page 11 of 37
`
`

`
`Case 6:10-cv-00417-LED Document 182
`
`Filed 12/07/11 Page 12 of 37 PagelD #: 4287
`
`network that accomplishes data security and anonymity through the use of hop tables.”7 In
`
`addition to requiring a VPL to have all the characteristics of a virtual private network, the
`
`specification further dictates that hop tables must be used to create a VPL.
`
`When a packet is received from a known user, the signaling server activates a
`virtual private link (VPL) between the user and the transport server, where
`hopping tables are allocated and maintained. When the user logs onto the
`signaling server, the user's computer is provided with hop tables for
`communicating with the transport sewer, thus activating the VPL.
`
`Ex. 1 at 44:37-43 (emphasis added). The specification also explains how anonymity and security
`
`are accomplished through the use of hopping technology. See id. at 3: 10-17 and 3:39-42.
`
`Accordingly, Aastra submits that a virtual private link is a link in a VPN that requires the use of
`
`hop tables.
`
`3.
`
`Secure Server
`
`Term
`
`VirnetX’s Proposed Construction
`
`Defendants’ Proposed Construction a Server that requires authorization
`
`Secure Server
`
`for access and that can communicate
`in a secure communication link
`
`ires authorization for access
`a server that r
`and co
`unifigres in a VPN
`
`Defendants’ proposed construction recognizes that the word “secure” in the context of the
`
`patent refers to a server that communicates in a virtual private network. The specification plainly
`
`dictates that for a server to be “secure,” it must achieve both the data security and anonymity
`
`requirements of a VPN:
`
`“It is desired for the communications [over the intemet] to be secure, that is,
`immune to eavesdropping. For example, terminal 100 may transmit secret
`infonnation to terminal 110 over the Internet 107. Also, it may be desired to
`prevent an eavesdropperfrom discovering that terminal 100 is in
`communication with terminal 110. .
`.
`. These two security issues may be called
`data security and anonymity.”
`
`‘ 151 Patent (attached as Ex. 2) at 1:34-48 (emphasis added); see also 19:43-48. Moreover, the
`
`specification indicates that the secure server claimed in the ‘I51 Patent communicates in a virtual
`
`7 Only Defendant Aastra advances this construction and argument.
`
`Page 12 of 37
`
`Page 12 of 37
`
`

`
`Case 6:10-cv-00417-LED Document 182 Filed 12/07/11 Page 13 of 37 PageID #: 4288
`
`private network:
`
`“[A] specialized DNS server traps DNS requests and, if the request is from a
`special type of user (e.g., one for which secure communication services are
`defined), the server . . . automatically sets up a virtual private network . . . . .”
`
`Id. at 37:33-49 (emphasis added). Indeed, this Court previously cited the same portion of the
`
`‘135 Patent’s specification in concluding that a “secure web site” communicates in a virtual
`
`private network. Ex. A at 18 (citing ‘135 Patent at 37:63-38:13). Just as a “secure web site”
`
`communicates in a “virtual private network,” so too does a “secure server” communicate in a
`
`“virtual private network.”
`
`While the only mention of the precise phrase “secure server” in the ‘151 Patent occurs in
`
`the claims, the other related Patents-in-Suit dictate that a “secure server” is a server that
`
`communicates in a virtual private network. The specifications of the ‘504, ‘211, ‘180, and ‘759
`
`Patents all state that “software module 3309 accesses secure server 3320 through VPN
`
`communication link 3321,” ‘180 Patent (attached as Ex. 3) at 52:55-56 (emphasis added), and
`
`that “[s]erver 3320 can only be accessed through a VPN communication link.” Id. at 52:29-30
`
`(emphasis added). The Patents distinguish “secure servers” from “non-secure servers” based on
`
`whether the server communicates in a VPN:
`
`computer 3301 can establish a VPN communication link 3323 with secure server
`computer 3320 through proxy computer 3315. Alternatively, computer 3301 can
`establish a non-VPN communication link 3324 to a non-secure website, such as
`non-secure server computer 3304.
`
`Id. at 53:20-25. Together, these passages explain that a secure server is a server dedicated to
`
`VPNs.
`
`
`
`Defendants’ proposed construction also comports with this Court’s constructions of other
`
`claim terms that use the word “secure.” The Court previously decided (and the parties agree)
`
`that “secure computer network address” means “a network address that requires authorization for
`
`9
`
`Page 13 of 37
`
`

`
`Case 6:10-cv-00417-LED Document 182
`
`Filed 12/07/11 Page 14 of 37 PagelD #: 4289
`
`access and is associated with a computer capable of virtual private network communications.”
`
`Ex. A at 28. The parties also agree that the construction for “secure domain name,” by virtue of
`
`incorporating the term “secure computer network address,” also communicates in a VPN. D.I.
`
`175 Ex. A. Finally, although the parties disagree about the construction of the term “secure web
`
`site,” both Defendants’ and VimetX’s proposed definitions specify that it “can communicate in a
`
`virtual private network.” D.I. 175 Ex. B. Because the word “secure” in the context of servers
`
`should be given the same meaning as in the context of related claim terms, Defendants’ proposal
`
`should be adopted. Omega Eng'g., Inc. v. Raytek Corp, 334 F.3d 1314, 1334 (Fed. Cir. 2003)
`
`(“[\V]e presume, unless otherwise compelled, that the same claim term in the same patent or
`
`related patents carries the same construed meaning”).
`
`4.
`
`Secure Communication Link
`
`virtual private network communication link
`
`VirnetX’s Proposed
`
`Construction
`
`Defendants’ Proposed Construction
`
`_
`
`Secure Communication Link
`
`an encrypted communication link
`
`Defendants’ proposed construction is taken verbatim from the definition provided in the
`
`Summary of the Invention, which states that “[t]he secure communication link is a virtual
`
`private network communication link over the computer network.” ‘504 Patent (attached as Ex.
`
`5) at 6261-63 (emphasis added). The rest of the specification consistently defines secure
`
`communication link in the same way. Thus, the Detailed Description of the Invention explains
`
`when secure communication links are specified, all communication links will be VPN
`
`communication links:
`
`[w]hen software module 3309 is being installed or when the user is off-line, the
`user can optionally specify that all communication links established over
`computer network 3302 are secure communication links. Thus, anytime that a
`communication link is established, the link is a VPN link.”
`
`Id. at 52:15-19 (emphasis added). Similarly, selecting a secure communication link enables a
`
`Page 14 of 37
`
`10
`
`Page 14 of 37
`
`

`
`Case 6:10-cv-00417-LED Document 182
`
`Filed 12/07/11 Page 15 of 37 PagelD #: 4290
`
`computer to establish a VPN communication link: “[a]dditionally, a user at computer 3301 can
`
`optionally select a secure communication link through proxy computer 3315. Accordingly,
`
`computer 3301 can establish a VPN communication link 3323 with secure server computer
`
`3320 through proxy computer 3315.” Id. at 52:25-29 (emphasis added).8
`
`In the Microsoft case, VirnetX actually conceded that a secure communication link is a
`
`VPN communication link. See Microsoft case D.I. 194 (attached as Ex. M) at 31-32. VimetX
`
`now reverses course by engaging in a tortured reading of the specification. But even the passage
`
`VirnetX cites explains that a secure communication link is a VPN because it can securely access
`
`a private network. D.I. 173 at 11-12 (citing ‘504 Patent at 50:21-53). VirnetX’s only purported
`
`support for its construction of secure communication link is the specification’s discussion of
`
`“data security.” See D.I. 173 at 10 (citing ‘504 at 1:55-56). The specification clearly
`
`distinguishes “secure,” which encompasses data security and anonymity from “data security.”
`
`Ex. 5 at 1:33-54. Therefore, VirnetX’s discussion of “data security”—a phrase that does not
`
`appear in the disputed claim language—is not relevant to the construction of “secure
`
`communication link.”9
`
`B.
`
`Disputes Relating to Domain Names
`
`1.
`
`Domain Name
`
`Defendants’ Proposed Construction .
`
`Domain Name
`
`VirnetX’s Proposed Construction
`a name corresponding to an [P
`address
`
`a hieml-Fhical sequence (if“iords in
`decreasing order of specificity that
`corres s nds to a numerical IP address
`
`VirnetX’s proposed construction reads out the meaning of “domain.” Compare ‘I81
`
`8 These descriptions are also consistt with the specification‘s use of the word “secure.” See Section IV.A.3.,
`supra. As this Court previous recognized, in the context of the patent, “’secure’ relates to registered users who have
`the ability to set up a virtual private network with a target node.” Ex. A at 18.
`9 In the Microsofl case. this Court declined to construe the term “secure communication link” because the claims of
`the ‘759 Patent explain “the secure communication link being a virtual private network.” Ex. A at 25. Here, the
`claim language of the ‘504 and ‘2ll Patents does not itself explain that the secure communication link is a virtual
`private network communication link.
`
`Page 15 of 37
`
`11
`
`Page 15 of 37
`
`

`
`Case 6:10-cv-00417-LED Document 182 Filed 12/07/11 Page 16

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