US 6839759

Patent Overview: US6839759B2

Title: Method for establishing secure communication link between computers of virtual private network without user entering any cryptographic information

Patent number: US6839759B2
Application number: US10/702,522
Filing date: 2003-11-07
Publication date (grant): 2005-01-04
Priority date (as listed): 1998-10-30
Inventors: Victor Larson; Robert Dunham Short, III; Edmund Colby Munger; Michael Williamson
Original assignee: Science Applications International Corp (SAIC)
Current assignee (as listed): VirnetX Inc.
Legal status (as listed): Expired – Lifetime (anticipated expiration 2019-10-29)

Purpose and plain-language scope (per the supplied text):
The patent concerns establishing a secure communication link between computers in a virtual private network (VPN) without the user entering any cryptographic information. The supplied excerpt identifies "computer," "packets," "secure communication," "secure," and "packet" as prior-art keywords, and indexes description terms including tunneling, signaling, synchronised, and biological transmission. The title and keyword list are the only substantive technical descriptions in the excerpt; no claims, abstract, or detailed description text is included in the supplied material. Priority is noted as claimed from US09/429,643 and US09/504,783 (see US7010604B1 and US6502135B1).

What the excerpt does not establish:

• The actual claim language and therefore the precise metes and bounds of the claimed scope.
• The specific technical mechanisms by which the secure link is established without user-entered cryptographic information (beyond indexed keywords such as tunneling and signaling).
• What the cited prior art references disclose or how they relate to the claims.
• The completeness, accuracy, or legal effect of the listed assignments, legal status, or litigation entries — the source itself labels these as assumptions and not legal conclusions.
• Any facts about omitted portions of the document, which were excluded from the supplied text.

Source: https://patents.google.com/patent/[US6839759](/patent/US6839759)/en

I'll research litigation involving US patent 6839759. Let me search authoritative litigation sources.

Let me search for more specific case details and outcomes.

Let me dig deeper into which cases specifically asserted the '759 patent and get case details.

I've reached my research step limit. Here is what I was able to confirm. Note: I could not fully verify every Google Patents "family litigation" link against the '759 patent's specific involvement, so I flag confidence levels.

Litigation involving US Patent 6,839,759 ("the '759 patent")

Important scoping note: The '759 patent ("Method for establishing secure communication link between computers of virtual private network without user entering any cryptographic information," issued Jan. 4, 2005, filed Nov. 7, 2003 as appl. 10/702,522, priority Oct. 30, 1998; original assignee Science Applications International Corp. ("SAIC"), later VirnetX Inc.) is one patent in a large VirnetX/SAIC patent family that was litigated and reexamined extensively. Many VirnetX cases asserted other family members (e.g., the '135, '151, '504, '211, '180 patents) rather than the '759 patent. Below I separate cases where I found direct evidence the '759 patent was at issue from those where the connection is unverified.

1. VirnetX Inc. (and SAIC) v. [Microsoft Corp.](/litigations/by-plaintiff/Microsoft%20Corp.) — CONFIRMED '759 ASSERTION

• Court/jurisdiction: U.S. District Court for the Eastern District of Texas, Tyler Division
• Case number: 6:07-cv-00080 (a.k.a. 6:07CV80, "LED")
• Plaintiff(s): VirnetX Inc.; Science Applications International Corp. (SAIC, as involuntary/co-plaintiff)
• Defendant(s): Microsoft Corporation
• Filing date: 2007 (original complaint Feb. 2007; First Amended Complaint Apr. 5, 2007; Second Amended Complaint June 10, 2008)
• Patents asserted: U.S. Pat. Nos. 6,502,135 and 6,839,759 (the '759 patent is confirmed via Microsoft's filing of a "Motion for Partial Summary Judgment of Invalidity of U.S. Patent No. 6,839,759" and the supporting Wicker Declaration, Dec. 18, 2009, No. 6:07CV80).
• Outcome/status: Tried in March 2010; jury found Microsoft willfully infringed and awarded $105.75 million (verdict summary, E.D. Tex. Mar. 16, 2010). Case resolved by stipulated Order of Dismissal entered June 1, 2010, dismissing all claims against Microsoft with prejudice (settlement). VirnetX has characterized this as a ~$200 million settlement.

2. VirnetX Inc. v. Cisco Systems, Inc., et al. — '759 INCLUDED (with caveats)

• Court/jurisdiction: U.S. District Court for the Eastern District of Texas, Tyler Division
• Case number: 6:10-cv-00417-LED ("the -417 case")
• Plaintiff(s): VirnetX Inc.
• Defendant(s): Aastra, Apple, Cisco Systems, and NEC (multiple defendants)
• Filing date: Aug. 11, 2010
• '759 connection: The '759 patent appears in the -417 case's Joint Claim Construction materials and in the court's Claim Construction Order (Doc. 266, Apr. 25, 2012). Cisco was also the third-party requester in the inter partes reexamination of the '759 patent (see item 4). The order denying VirnetX's motion for new trial after the Cisco trial (in which the jury found Cisco did not infringe and that the asserted claims of the '135, '504 and '211 patents were not invalid) references the '759 patent's "no cryptographic information" limitation. So the '759 patent was in play, but the published Cisco verdict language emphasizes the '135/'504/'211 patents — I cannot confirm from the sources retrieved whether a '759 claim remained in the Cisco trial at verdict.
• Outcome/status (overall -417 case): First Apple trial (2012) → jury verdict ~$368M against Apple (willful). On appeal, VirnetX Inc. v. Cisco Sys., Inc., 767 F.3d 1308 (Fed. Cir. 2014) ("VirnetX I") affirmed the jury's validity finding and VPN-on-Demand infringement, vacated the FaceTime infringement finding and the damages award, and remanded. The case was later consolidated/related to the -855 case and had extensive further trials and appeals (see below). The Cisco portion ended with a Cisco non-infringement verdict.

3. Related VirnetX cases where the '759 connection is UNVERIFIED

These appear in VirnetX's SEC filings/Google Patents family-litigation links, but I could not confirm that the '759 patent (as opposed to sibling family patents such as the '135/'151/'180) was actually asserted:

• VirnetX Inc. v. Apple Inc., No. 6:13-cv-00211-LED (E.D. Tex.) — Apple was served with a new complaint in Dec. 2012 that matured into this case; the asserted patents appear to center on the '135 patent. A VirnetX press release noted a post-judgment on-going royalty of 0.98% and directed the clerk to close Cause No. 6:13-cv-211.
• VirnetX Inc. v. Apple Inc., No. 6:12-cv-00855-LED (E.D. Tex., filed Nov. 6, 2012, "Apple II"/-855 case) — asserted the '135, '504, '211 and '151 patents (not the '759).
• VirnetX Inc. v. Mitel Networks Corp., et al. (including Siemens and Avaya), E.D. Tex., filed Jan. 12, 2011 — three VirnetX patents asserted; all defendants ultimately took licenses and the case was dismissed (Aug. 18, 2013). The specific patents are not identified in the material retrieved.
• VirnetX Inc. v. Microsoft Corp. (2013 case) — per VirnetX filings, this asserted the '135 and '180 patents, not the '759.

4. Post-grant / appellate proceedings specific to the '759 patent (not district-court litigation, but same patent)

• Inter partes reexamination No. 95/001,746 of the '759 patent (filed Sept. 7, 2011; Cisco Systems as third-party requester). The USPTO issued a closing action rejecting claims 1, 3–10, 12–16, 18–25, and 27–30 and confirming claims 2, 11, 17, and 26. (A related reexamination, 95/001,972, involved the sibling '180 patent.)
• VirnetX Inc. v. Cisco Systems, Inc., No. 19-1043 (Fed. Cir.) — VirnetX's appeal of the PTAB's invalidity findings in inter partes reexamination 95/001,746 involving the '759 patent. Oral argument Jan. 8, 2020; the Federal Circuit issued a Rule 36 judgment affirming the PTAB on Jan. 21, 2020.
• VirnetX also reported that on Sept. 19, 2014 the USPTO partially terminated certain inter partes reexamination proceedings with respect to certain claims of U.S. Pat. Nos. 6,502,135; 6,839,759; 7,418,504; and 7,921,211.

5. Appeals/cases listed on the patent's Google Patents "family litigation" page (literal list)

The Google Patents page for US 6,839,759 lists these family-litigation links. I interpret them literally but could not individually verify that each involves the '759 patent rather than a sibling:

• E.D. Tex. 6:07-cv-00080
• E.D. Tex. 6:10-cv-00417
• E.D. Tex. 6:13-cv-00211
• U.S. Supreme Court No. 19-832
• Fed. Cir. 13-1489 (this corresponds to VirnetX I, 767 F.3d 1308)
• Fed. Cir. 18-1197 (Apple's appeal of the Apple I final judgment)
• Fed. Cir. 22-2234

Bottom line

Based on the sources retrieved, the clearest district-court litigation involving the '759 patent is VirnetX/SAIC v. Microsoft, No. 6:07-cv-00080 (E.D. Tex.), which produced a $105.75M willful-infringement verdict in March 2010 and was dismissed with prejudice (settled) on June 1, 2010. The '759 patent was also part of the patent set in the VirnetX v. Cisco Systems, et al., No. 6:10-cv-00417 (E.D. Tex.) case and was the subject of inter partes reexamination 95/001,746, affirmed on appeal in VirnetX v. Cisco, No. 19-1043 (Fed. Cir. Jan. 21, 2020).

Caveats / limits of this search: I hit my research step limit before I could (a) confirm the exact patents asserted in the 2011 Mitel/Siemens/Avaya case and the 6:13-cv-00211 Apple case, (b) pull the precise docket-level '759 infringement contentions from PACER/CourtListener for the Cisco trial, or (c) verify the Supreme Court 19-832 and Fed. Cir. 22-2234 connections. Those should be verified directly on the Unified Patents litigation portal (https://portal.unifiedpatents.com/litigation/caselist), PACER, and CourtListener before being relied upon. I also note that the case numbers and dates above are reproduced literally from the sources retrieved and have not been independently normalized.

I'll start by verifying the structured-data baseline and then hunting for any PTAB proceedings the ODP ingest may have missed.

The initial searches surfaced a reexamination (not an AIA trial) and a family of New Bay/Apple proceedings. Let me pin down which patents those proceedings actually challenged.

The New Bay IPRs covered the '135, '151, '504 and '211 — not the '759. Let me now specifically test whether any AIA trial ever targeted the '759 itself, including CBM and Unified Patents activity.

Proceedings overview

Zero AIA trial proceedings have ever been filed against US 6,839,759. The canonical PTAB proceedings block from the USPTO Open Data Portal returns no IPR, PGR, or CBM for this patent, and my web searches did not surface any AIA trial petition that the ODP ingest might have missed — the VirnetX IPR wave (New Bay Capital, Apple, Mangrove Partners, Black Swamp IP, Cisco) hit the sibling patents in the family ('135, '151, '504, '211, '643, '696, '697, '181), not the '759. Status breakdown: 0 active / 0 claims invalidated / 0 claims sustained / 0 settled / 0 institution denials. Bottom line for a defendant: this is the one VirnetX Larson-family patent that came through the PTAB era with its claims untouched by an AIA trial — you cannot piggyback on an existing FWD, and there is no cancellation to point at. Any validity attack has to be built from scratch.

Because there are no proceedings to enumerate, the per-proceeding template below is supplied only for the related non-AIA Office activity I was able to confirm, clearly labeled as outside the AIA-trial scope.

No AIA trial proceedings on file

I found no petition, institution decision, FWD, or termination for the '759 under 35 U.S.C. §§ 311–319 (IPR), §§ 321–329 (PGR), or AIA § 18 (CBM). I want to be explicit about confidence: the structured ODP block is the authoritative negative, and it is corroborated by the pattern in the search results, where every identified VirnetX PTAB case maps to a different patent number. I would still verify with a one-minute E2E/PTAB search before relying on this in a brief.

New Bay Capital, LLC v. VirnetX, Inc. — does NOT involve the '759

• Type: Inter Partes Review (4 petitions)
• Filed: 2013-06-23
• Status: Terminated (all four)
• Patents challenged: IPR2013-00375 → US 6,502,135; IPR2013-00376 → US 7,490,151; IPR2013-00377 → US 7,418,504; IPR2013-00378 → US 7,921,211. The '759 is not among them.
• Judge panel: Judges Easthom, Medley, Siu, Tierney (per Finnegan's case report).
• Disposition: New Bay moved to terminate all four; the Board granted termination (Paper 14/16/17, Nov. 2013). This is the proceeding underlying the "curious case of New Bay Capital" — a non-practicing challenger who, per VirnetX, demanded ~10% of the Apple judgment to drop the petitions. Apple's joinder motions died with the terminated proceedings. Not relevant to the '759 except as family context.

Apple Inc. / Mangrove Partners / Black Swamp IP, LLC — do NOT involve the '759

• Type: IPR
• Notable numbers: IPR2015-01046, IPR2015-01047, IPR2015-01009, IPR2015-01010, IPR2016-00062, IPR2016-00063, IPR2016-00331, IPR2016-00332, IPR2016-00693, IPR2016-00957.
• Patents challenged: US 8,843,643; US 6,502,135; US 7,490,151; US 8,504,696; US 7,418,504; US 7,921,211. Again, no '759.
• Why this matters: it establishes that sophisticated challengers with full access to the Larson family (Apple filed on the '135, '151, '643, '696, '504, '211) chose not to file on the '759. That is a meaningful negative signal, discussed below.

Related Office activity (NOT an AIA trial) — flagging because it bears on the '759's claim scope

Ex parte reexamination, Control No. 95/001,746 (and PTAB Appeal No. 2015-007843)

• Type: Ex parte reexamination under 35 U.S.C. § 302 — not an AIA trial; reexamination is not an IPR/PGR/CBM.
• Evidence: A 2015 Apple-filed IPR exhibit (in IPR2015-01009, on the '643 patent) lists the '759 patent as "Control No. 95/001,746; Appeal No. 2015-007843 | Pending; Examiner's…" — i.e., a pending reexamination with an examiner rejection on appeal to the PTAB. Source: IPR2015-01009 exhibit 2004 / the '643 petition record.
• What I could NOT confirm: the reexamination certificate outcome (claims confirmed as-is, confirmed with amendment, or cancelled), and the disposition of Appeal No. 2015-007843. Do not assume the claims were cancelled — the best available inference runs the other way: in the later VirnetX v. Apple damages record, VirnetX/Apple identified the family patents whose "claims [were] cancelled in post-grant proceedings, after exhausting all appeals to the PTAB and the Federal Circuit" as US 8,051,181, 8,504,697, 7,418,504 and 7,921,211 — the '759 is conspicuously absent from that list. Cite: E.D. Tex. 6:10-cv-417 Dkt. 964. Treat the reexam outcome as unverified and pull the reexam certificate from USPTO Patent Center before relying on it.

District-court validity history on the '759 (relevant to, but not part of, PTAB practice)

• VirnetX, Inc. v. [Microsoft Corp.](/litigations/by-plaintiff/Microsoft%20Corp.), No. 6:07-cv-80 (E.D. Tex.) — Microsoft moved for SJ of invalidity of the '759 (Dec. 2009); the '759 claim terms were construed in the July 30, 2009 Microsoft claim-construction opinion.
• VirnetX, Inc. v. Cisco Systems, Inc., No. 6:10-cv-417 (E.D. Tex.) — VirnetX asserted '759 claims 1, 2, 8–14, 16, 17, 23–29 against Cisco. The March 2013 jury found no infringement on all patents; the court then granted JMOL that Cisco failed to prove the '759 invalid. See the CourtListener docket for 6:10-cv-00417 and VirnetX's 2013 press release. The '759 was dropped from Apple's contested-issues list in that same case (the '759 claims appear only in the Cisco portion of the pleadings).

Strategic summary

Claim status — CANCELED vs. SUSTAINED vs. UNTESTED. There is no PTAB record for the '759 at all, which means no claim of the '759 has ever been canceled by the Board, and no claim has been "tested" in an AIA trial. Every claim stands as issued (subject to the undisclosed reexamination outcome). This is the inverse of the rest of the Larson family: the '135, '151, '504, '211, '181 and '697 have all been through PTAB reexamination/IPR gauntlets, and several were held unpatentable — the '151's FWD on remand (2020-07-14) found all challenged claims unpatentable under § 102/§ 103 over Kiuchi, which defeated Apple. The '759's narrow escape is the anomaly, and it cuts against a defendant hoping for an easy § 103 kill.

Estoppel landscape — there is none to exploit. Because no IPR/PGR/CBM was instituted on the '759, § 315(e)(2) estoppel does not attach to anyone with respect to this patent. There is no petitioner privity chain, no "raised or reasonably could have raised" bar, and no ground that a district court can knock out as estopped. For a defendant being asserted against today, the entire universe of prior art remains available — including the references Cisco ran in E.D. Tex. (Altiga VPN System, OSF DCE, Schulzrinne, SSL 3.0, Kiuchi, Kent, Aziz/PK Firewall, per the '759 claim charts in VirnetX's exhibit lists), many of which were never put in front of an AIA-trial panel. The only prior-art headwind is discretionary: if you later get into an AIA proceeding, § 325(d) could let the Board discount art already considered in the '759 reexamination — but the reexam is not an AIA trial, so that is an argument, not an estoppel.

Pattern signals. (1) No serial petitioner — nobody has ever filed a single IPR on the '759, let alone stacked them. (2) The patent owner litigates hard and appeals aggressively — VirnetX appealed to the Federal Circuit repeatedly (17-1591/1592/1593, 17-2490, 17-2593, 22-2234) and took the § 315(c) joinder question to the Supreme Court in VirnetX Inc. v. Apple Inc., No. 23-315 (cert. denied). If you file on the '759, expect maximal appellate pushback. (3) No defensive aggregator — I found no Unified Patents, RPX, or similar aggregator petition on the '759; the challenger set is Apple/Cisco/New Bay/Mangrove/Black Swamp, all tied to the Apple/Cisco district-court campaigns. (4) Practical ceiling: the '759 expired 2019-10-29 (per the ODP legal-status block), so any remaining exposure is past damages only, within the § 286 six-year window — an important scoping point before spending IPR money.

Recommended next steps

1. If you are a defendant and the demand letter cites '759 claims 1, 2, 8–14, 16, 17, or 23–29: those are exactly the claims VirnetX pressed against Cisco and lost on infringement — but the court upheld validity by JMOL. There is no FWD to link to and quote, because no IPR was ever filed. Your realistic path is an invalidity attack in court, or a fresh IPR petition.
2. Before filing any IPR: (a) confirm the reexamination certificate for Control No. 95/001,746 and the disposition of Appeal No. 2015-007843 on USPTO Patent Center — if the reexam amended or cancelled claims, your analysis changes materially; (b) confirm the expiration date (2019-10-29) and map the six-year damages window; (c) run § 315(b) — if your client was served with a '759 complaint more than one year ago, you are time-barred absent joinder (and note the '759's § 315(c) joinder questions were litigated all the way to the Supreme Court in No. 23-315).
3. If you want to confirm the zero-AIA-trial finding independently: search PTAB E2E / the USPTO PTAB decisions site and PATENTSCOPE docket for "6,839,759" and "IPR" / "CBM". The negative result is the finding; document the search date.
4. If no PTAB activity exists, say so plainly in your invalidity contentions: the absence is itself a signal. Well-asserted patents that spend a decade in litigation usually attract IPRs — that the '759 did not (despite Apple challenging six sibling patents) suggests challengers viewed its claim scope as harder to invalidate on printed publications, and drove VirnetX's non-infringement loss at Cisco instead. Build your defense on non-infringement and on Cisco's accrued prosecution/claim-construction record rather than assuming a PTAB shortcut exists.

Caveats I will not paper over: (i) I could not confirm the reexamination outcome — treat all '759 claim status as "as-issued, subject to unverified reexam" rather than "clean"; (ii) my searches were bounded and the only way to be certain of a global negative on AIA trials is a direct E2E docket check; and (iii) the '759's ODP record shows heavy litigation (E.D. Tex. 6:07-cv-00080, 6:10-cv-00417, 6:13-cv-00211) and multiple CAFC appeals, but those are Article III matters, not AIA trials, and I have not attempted to resolve their ultimate outcomes here.

I'll research this patent's ownership record before writing up. Let me run several targeted searches.

Good — I found a chain-of-title citation. Let me verify the reel/frame details and the VirnetX/SAIC deal terms.

Method note up front: I could not open the Assignment Center UI directly in this session, so I reconstructed the chain from (a) the Google Patents legal-events record embedded in the authoritative full text supplied, and (b) USPTO 37 CFR 3.73(b) chain-of-title statements filed in sibling applications of the same family (cited below with reel/frame). Fields I could not verify — specifically the Assignment Division correspondent of record, execution dates, and the '759-specific reel/frame numbers — are flagged as not retrieved rather than filled in.

Inventors

Four named inventors, all listed on the face of US 6,839,759 B2 and all appearing as assignors on the inventors'-interest assignment to the original assignee:

Pattern notes (evidence-based only):

• Not established: I found no evidence that all inventors departed SAIC within 12 months of filing. The 2003-11-07 continuation filing is 4 years after the 1999-10-29 parent filing, and Munger and Short surfaced at VirnetX only in 2006 — three years after the 2003 assignment. That is a "inventors followed the patents into the asserting entity" pattern, not a prompt post-filing exodus.
• Genuinely unusual: two of the four inventors (Short, Munger) were later employed by the entity that acquired the portfolio and monetized it. Per contemporaneous reporting (ALM Intellectual Property supplement, Fall 2013), Munger and Short had tried and failed to interest Phoenix Technologies — where VirnetX founder Kendall Larsen then worked — in commercializing the invention, and Larsen subsequently left to raise money around it. This is inventor-adjacent NPE formation, which is worth flagging but is not by itself a transfer signal.

Original assignee

Science Applications International Corporation (SAIC) — the assignee named on the issued patent and the assignee in the 2003-11-07 inventors'-interest assignment recorded for this application.

• Line of business: large U.S. defense/intelligence IT and systems-integration contractor (NYSE: SAI at the time). Government services, not commercial networking products.
• Product embodying the claims: No evidence that SAIC ever shipped a product embodying the '759 claims. The '759 claims are directed to one-click/no-click VPN session establishment using hopped packet values — functionality that SAIC's services business was not selling. The 2007 Microsoft complaint (below) pleaded infringement by Microsoft products, and VirnetX's own later filings confirm the portfolio was acquired to be licensed and enforced, with SAIC retaining only a back-license outside VirnetX's field of use.
• Current status: SAIC is an operating company, but it is not the same legal person as the 2003 assignee in every respect — in 2013 the legacy SAIC renamed itself Leidos Holdings, Inc. and spun off a new, smaller SAIC (the "new SAIC"). The legacy entity that took the VirnetX assignment and the 2006 transfer is the Leidos-side lineage. I did not verify in SEC filings which of the two successors retained the VirnetX royalty/reversion interest — flagging as unresolved rather than guessing.

Assignment timeline

Three USPTO events are visible for this patent. The dates below are as recorded in the Google Patents legal-events table; the only reel/frame values I could positively tie to this family come from USPTO chain-of-title statements in sibling applications (noted inline).

• 2003-11-07 (executed on or about filing; recording date as shown in Google Patents legal events, not independently confirmed) — Reel not retrieved for this patent; the family-chain counterpart is Reel 019722/0321

  • Conveyance: Assignment of inventors' interest
  • Assignor: Victor Larson; Edmund Colby Munger; Michael Williamson; Robert Dunham Short III
  • Assignee: Science Applications International Corporation
  • Correspondent: Not retrieved. Google Patents omits the Assignment Division correspondent field. Not a finding — see the correspondent note in the next entry.
  • Context: Original employment/ownership assignment incident to the 2003-11-07 continuation filing; internal to SAIC.

• 2007-01-10 (per Google Patents legal events) / recorded 2007-08-21 per the family chain-of-title statement — Reel 019722/0525

  • Conveyance: Assignment (portfolio transfer), not a change of name. The reel/frame is documented for the family in a USPTO 37 CFR 3.73(b) statement reproduced in Apple Inc. v. VirnetX Inc., IPR2013-00397, Exhibit 1002 (U.S. Pat. 7,921,211 file history), which states VirnetX is assignee "by virtue of an assignment recorded … at Reel 019722, Frame 0525 on August 21, 2007"; the same reel/frame pair appears in the U.S. Pat. 8,560,705 file history (Unified Patents / Mangrove‑era IPR exhibits) as "Science Applications International Corporation To: VirnetX Inc."
  • Assignor: Science Applications International Corporation
  • Assignee: VirnetX Inc. (Delaware; wholly-owned subsidiary of VirnetX Holding Corporation, Zephyr Cove, NV)
  • Correspondent: Not retrieved. One adjacent data point, expressly not treated as a finding: the 3.73(b) chain-of-title statement in the U.S. 8,504,697 file history shows a filer of record "Toby H. Kusmer / Jessica Brown." That is prosecution counsel signing a chain-of-title statement, not the Assignment Division correspondent who filed the recording — I could not verify the firm or any recurrence across the chain, so signal 3 is left unclear rather than asserted.
  • Context: Transfer to an asserting entity formed 15 months earlier (VirnetX incorporated August 2005, before it owned anything) for the purpose of monetization — the acquisition closed November 2006, and the first infringement suit naming this patent was filed 2007-02-15, i.e., roughly three months after execution and before the August 2007 recordation. Per VirnetX's SEC filings, SAIC received 15% of VirnetX's in-field revenues, 50% of out-of-field license revenues, 35% of litigation proceeds recovered from Microsoft and certain other companies, 25% from other parties, plus a security interest and a full reversion of the patents on payment default. That is a revenue-share/privateering structure, not an outright sale.

• 2012-01-19 — recorded same date (Google Patents legal events) — Reel not retrieved

  • Conveyance: Change of Address of Assignee — no transfer of right, title, or interest
  • Assignor: VirnetX Inc.
  • Assignee: VirnetX Inc.
  • Correspondent: Not retrieved.
  • Context: Administrative address update only; ownership unchanged. Do not count this as a link in the chain.

Recorded security interests: VirnetX's prospectus discloses that it "granted SAIC a security interest in some of our intellectual property, including the patents and patent applications we obtained from SAIC." I did not find a corresponding USPTO-recorded security agreement or release for US 6,839,759 in Google Patents legal events, and could not confirm one in the Assignment Center. Flagging as unresolved — an unrecorded-but-disclosed security interest is a common posture and is not, on its own, evidence of anything.

No assignments after 2012 are visible. Ownership has sat with VirnetX Inc. from 2007 to expiry (anticipated 2019-10-29; status Expired – Lifetime).

Timeline diagram

timeline
    title Ownership of US 6839759
    1998 : Earliest priority application filed
    1999 : Parent application filed
    2003 : Continuation application filed
         : Inventors assign rights to SAIC
    2005 : VirnetX incorporated with no assets
    2006 : VirnetX acquires portfolio from SAIC
    2007 : SAIC to VirnetX assignment recorded
         : First infringement suit filed
    2012 : Assignee change of address recorded
    2019 : Patent expires

NPE / troll-pattern signals

1. Shell-entity transfer — PRESENT in substance, atypical in form. SAIC (large operating defense contractor) transferred the portfolio to VirnetX Inc., a Delaware corporation incorporated August 2005 — i.e., an empty entity created ~15 months before it acquired anything, sitting under a public holding company. Recorded at Reel 019722/0525 (recording 2007-08-21; transfer executed November 2006). Caveat against over-reading the naming tell: the assignee is not an anonymous single-purpose LLC with a registered-agent address — it is "VirnetX Inc.," a subsidiary of a NYSE-listed company with ~14–15 employees, its own later patent filings, and a claimed GABRIEL/SDNR product line. The transfer is real; the "death-by-registered-agent" version of the tell is not.

2. Known asserter in the chain — PRESENT. VirnetX Inc. / VirnetX Holding Corp. is one of the most-litigated patent holders in the country and is described as a patent-holding company in trade press (Ars Technica: "VirnetX is a patent-holding company… it makes all its money from licensing and litigating patents"; it was specifically targeted by RPX's "Premium Services" IPR program after Apple asked RPX to challenge VirnetX's patents). Assertions naming this patent (US 6,839,759) include: VirnetX v. Microsoft, E.D. Tex. 6:07-cv-00080 (filed 2007-02-15, '759 expressly named in the complaint), 6:10-cv-00417 (2010, re-asserting the '135 and '759 patents; $105.7M verdict March 2010, $200M settlement May 2010), 6:13-cv-00211 (April 2013, Skype products), and the August 2010 Apple/Cisco/NEC/Aastra action in which the '759 patent was asserted. Appellate/Supreme Court dockets on the patent family include Fed. Cir. 13-1489, 14-1395, 18-1197, 22-2234 and Sup. Ct. 19-832 (VirnetX v. Cisco). Whether VirnetX appears by name on a specific RPX/Unified "high-frequency plaintiff" published list I could not verify in this session — the signal rests on the docket record, which is stronger evidence anyway.

3. Repeat correspondent across the chain — UNCLEAR / not established. The Assignment Division correspondent field was not retrievable for any of the three records. The only attorney names adjacent to this family's chain of title are the filers of §3.73(b) statements ("Toby H. Kusmer / Jessica Brown" on the U.S. 8,504,697 file history), which is prosecution counsel, not recording counsel. Per your own rule, a single appearance is not a finding, and I have no second appearance to pair it with. Do not score this signal without pulling the correspondents off the Assignment Center entries for Reel 019722/0321, 019722/0525, and the 2012 change-of-address record.

4. Cascading transfers — NOT PRESENT. The chain is two real links over roughly seven years (inventors → SAIC in 2003; SAIC → VirnetX in 2006/2007), followed by an administrative change of address in 2012. There is no chained sequence of LLC-to-LLC hops inside a 24-month window, and no common-principal pattern is visible.

5. Pre-litigation transfer — PRESENT, strongly. The SAIC→VirnetX transfer was executed in November 2006 (Google's legal-events entry for the reassignment is dated 2007-01-10; USPTO recording of Reel 019722/0525 followed on 2007-08-21). VirnetX filed VirnetX v. Microsoft, 6:07-cv-00080 (E.D. Tex.) on 2007-02-15, expressly pleading infringement of U.S. Pat. No. 6,839,759 — about three months after execution and before the assignment was recorded at USPTO. This is a textbook set-up-the-assertion transfer, and it also matches the academic characterization of VirnetX as patents moved to an NPE "just prior to litigation."

6. Bankruptcy fire-sale — NOT PRESENT. No bankruptcy of SAIC or of any successor is implicated in this chain. SAIC is solvent and operating (now Leidos + new SAIC after the 2013 split). The "sale" was a negotiated monetization deal with a revenue split, not a distress liquidation.

7. Privateering — PRESENT. The disclosed economics are the classic signature: SAIC (an operating contractor that did not want to sue its own customers) transferred title to VirnetX while retaining a reversion on default, a security interest, a license back outside VirnetX's field of use, 35% of litigation proceeds from Microsoft and certain other targets and 25% from the rest, plus a 10% cut of any acquisition proceeds. SAIC later had to be joined as a co-plaintiff in the ITC actions to cure a standing defect — direct confirmation that SAIC kept a live interest in the patents it "sold." Assertions ran against Microsoft, Apple, Cisco, NEC and Aastra.

8. Defensive aggregator (anti-NPE) — NOT PRESENT. The chain terminates at VirnetX. RPX and Unified Patents appear in the record only as adverse parties — RPX filed IPRs against VirnetX's patents (e.g., RPX Corp. v. VirnetX Inc., IPR2014-00171, filed 2013-11-20, on the '151 patent) and Mangrove Partners' IPRs ultimately invalidated the '135 and '151 claims in July 2020. No defensive aggregator ever took title.

Verdict

NPE — high confidence.

The chain is a two-link transfer from an operating defense contractor (SAIC) to VirnetX Inc., an entity incorporated in August 2005 with no assets, executed November 2006 and recorded at Reel 019722/0525 on 2007-08-21 — with VirnetX filing suit on 2007-02-15 (E.D. Tex. 6:07-cv-00080) asserting US 6,839,759 by name roughly three months after execution and before recordation (pre-litigation transfer), and with SAIC retaining a 35%/25% share of litigation proceeds, a reversion, a security interest, and later joining as co-plaintiff (privateering). The current assignee is a serial asserter on the public docket (Microsoft 2007/2010/2013, Apple/Cisco/NEC/Aastra 2010, multiple Fed. Cir. and Supreme Court appeals), which satisfies the known-asserter signal independently of any published NPE list.

Verify the records directly at the USPTO Assignment Center, searching patent number 6839759: https://assignmentcenter.uspto.gov/ — the two entries to pull are the SAIC→VirnetX assignment (cross-reference Reel 019722/0525) and the 2012-01-19 change-of-address filing, and the fields I could not retrieve (execution date, correspondent of record, exact reel/frame for the patent-specific entries) are precisely the ones that would convert signal 3 from unclear to present or not present.

I'll research US patent 6839759 and its cited prior art references. Let me start with several targeted searches.

Let me dig into the specific "References Cited" on the face of this patent and the reexamination prior art.

Let me get the front-page "References Cited" listing and the examiner's cited references directly.

Prior-Art Analysis — US Patent No. 6,839,759 B2

1. Patent verification (literal identifiers)

Source: https://patents.google.com/patent/US6839759/en

Important caveat up front: US 6,839,759 entered reexamination with an Information Disclosure Citation (PTO/SB/08) and no Notice of References Cited (PTO-892) (see the reexam transmittal, Reexam Control No. 95001746: "☒ Information Disclosure Citation, PTO/SB/08"). I could not retrieve the verbatim front-page "References Cited / U.S. Patent Documents" list from the sources available to me. The references below are therefore the ones that were actually applied against the '759 claims in reexamination and in the VirnetX v. Microsoft invalidity briefing — i.e., the prior art that genuinely matters for § 102 purposes.

2. The most relevant prior art applied against the '759 claims

2(a) Kiuchi — the primary reference

• Full citation: Takahiro Kiuchi and Shigekoto Kaihara, "C-HTTP — The Development of a Secure, Closed HTTP-based Network on the Internet," Proceedings of the Symposium on Network and Distributed System Security (SNDSS 1996).
• Publication date: 1996 (more than one year before the 1998-10-30 priority date).
• § 102 basis: 35 U.S.C. § 102(b) — the requester expressly asserted this.
• Brief description: A closed, firewall-protected network in which a client-side proxy, a server-side proxy, and a C-HTTP name server cooperate. The client-side proxy asks the C-HTTP name server whether it may communicate with the host in a given URL; the name server returns the IP address and public key of the server-side proxy plus request/response nonces. The proxies authenticate each other and establish an encrypted channel automatically, without the user entering any cryptographic information. Kiuchi describes the resulting "closed HTTP-based virtual network" as an alternative to leased private circuits (i.e., a VPN-like construct).
• Potentially anticipating claims: The reexam request and Microsoft's claim charts applied Kiuchi as a primary reference across the independent claims 1 and 16 and the dependent claims generally. The specific features mapped were the "enabling … without a user entering any cryptographic information" step and the "virtual private network communication link" limitation.
• Litigation posture worth flagging: On appeal (VirnetX Inc. v. Cisco Systems, Inc., 778 F. App'x 899 (Fed. Cir. 2019)), the court held that Kiuchi's "user agent" (also called a client) and its "client-side proxy" are different components, and that treating them both as the recited "client" was not supported by substantial evidence (778 F. App'x at 905, 907–908). In the later PTAB appeal (Appeal 2020-000639, Reexam Control 95/001,714, Patent 7,490,151) the Board nonetheless found Kiuchi's "user agent" corresponds to the recited client. In short: Kiuchi is the single most material § 102 reference, but its anticipation of the '759 claims was contested and, at least in part, rejected on appeal.

2(b) The Kiuchi-based combinations and secondary references

These were relied on individually or in combination by the third-party requester (Cisco) in the inter partes reexamination; the Federal Circuit/PTO record shows they were applied to the '759 and its sibling patents:

• § 102 basis / procedural caveat: VirnetX objected that the requester had not shown that Kent, Martin, Kent ESP, RFC 793, RFC 791, or Maughan were "printed publications" within the meaning of the reexamination statute (In re Cronyn; Carella v. Starlight Archery), and petitioned on that basis. This is a genuine vulnerability/defense to keep in mind: several of these references, especially RFC 2401 (Nov. 1998), post-date the 1998-10-30 priority date and would not qualify as § 102(b) art as of that date.

2(c) Examiner-cited / of-record patent art directly relevant to the claimed subject matter

The record confirms that the examiner's Reasons for Allowance turned on the absence of the "no cryptographic information from the user" limitation:

"The prior arts of record do not teach a method, based on a secure communication mode at a first computer, for establishing without a user entering any cryptographic information a secure communication link between the first and a second computers of a private virtual network over a computer network."

The "prior arts of record" for the parent application (09/558,209, later the '759) included VirnetX's own sibling filings that share the 1998-10-30 priority (US 6,502,135; US 7,010,604; US 6,826,616; US 7,188,180; US 7,490,151). These are not § 102 prior art against '759 — they are same-family/priority members, which is why the reexam requester had to reach for Kiuchi and the RFC-based references instead.

3. Bottom line on anticipation

• Leading § 102(b) reference: Kiuchi, "C-HTTP" (SNDSS 1996) — asserted against claims 1 and 16 (and their dependents), i.e., essentially the whole claim set, and the reference the requester built its substantial-new-question case on.
• Secondary / combination references: Kent (RFC 2401), Kent ESP (RFC 2406), Martin, Maughan (RFC 2408), RFC 791, RFC 793, Aziz, Caronni, Edwards, and RFC 1034.
• Reexamination outcome on the record I have: in Reexam Control 95/001,746, claims 2, 11, 17, and 26 were confirmed, while claims 1, 3–10, 12–16, 18–25, and 27–30 were rejected in the Office Action; VirnetX appealed the rejections (the VirnetX v. Cisco appeal, 778 F. App'x 899, and PTAB Appeal 2020-000639 in the related '151 reexam, both discuss Kiuchi's scope). I do not have a reliable final disposition of every '759 claim in this record, so I will not assert one.

4. What I could not confirm (stated explicitly rather than guessed)

1. The verbatim front-page "References Cited" U.S. patent list for US 6,839,759 — the reexam transmittal indicates an SB/08 IDS rather than a PTO-892, and I could not pull the printed front page. I therefore have not listed examiner-cited U.S. patents as "citations for 6839759"; doing so would risk fabricating a list.
2. The exact bibliographic form of "Caronni," "Aziz," and "Edwards" (report vs. patent). I have reproduced only the short names used in the PTAB/claim-chart exhibits and the one substantive characterization of Aziz that appears in the record.
3. Whether any single one of these references anticipates (as opposed to renders obvious) each individual claim — that requires a limitation-by-limitation chart, and the record shows the parties disputed precisely this (e.g., the Kiuchi "user agent vs. client" issue).

If you want, I can next build a claim-by-claim § 102 chart for independent claims 1 and 16 against Kiuchi as primary reference, or pull the Microsoft 2009 motion for partial summary judgment of invalidity (VirnetX v. Microsoft, No. 6:07-cv-80, E.D. Tex., Dec. 18, 2009), which contains the full pre-reexam invalidity position (Kiuchi, Kent, Aziz, and Kent+Caronni charts).

I'll research the prior art cited against this patent — both the references of record and the art relied on in the inter partes reexamination — before constructing the §103 analysis.

Let me pull the specific rejection grounds from the '759 reexamination and the identities of the key references.

Now let me retrieve the specific rejection grounds and the face-of-patent references.

Obviousness Analysis — US 6,839,759 B2 under 35 U.S.C. § 103

Governing law note. The claims of the '759 patent have an effective filing date no later than April 26, 2000 (continuation of 09/558,209), so pre‑AIA § 103(a) applies, with the critical date being "the time the invention was made." The reexamination order in the parallel family proceeding fixed the analogous Larson-family effective date as April 26, 2000 (IPR2014‑00405 Ex. 1024‑2). KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007), governs the combination analysis; Graham v. John Deere supplies the factual framework.

Caveat on sources. I could not retrieve the verbatim ground table from the Action Closing Prosecution or from PTAB Decision 1 in Appeal 2017‑010852. What follows is anchored to (a) the prior art identified by the third‑party requester in the '759 reexamination, (b) the reference list in the requester's transmittal, and (c) the Board's holding that the rejection of the '759 claims rested on Kent (RFC 2401). Where I am inferring a mapping rather than quoting the record, I say so.

1. POSITA and claim construction

Level of ordinary skill. In this family, the Board has characterized the skill level as "moderately high" (Apple v. VirnetX, IPR2014‑00403, Paper 42 at 35), and petitioners in related proceedings have proposed a master's degree in computer science/computer engineering plus approximately two years of experience (PTAB petition excerpt). A POSITA therefore understands IPsec/IKE key negotiation, proxy-mediated firewalls, DNS resolution, and client-side tunnelling software.

Claim construction. "Virtual private network communication link" was construed in the parallel VirnetX v. Microsoft Markman as "a network of computers which privately communicate with each other by encrypting traffic on insecure communication paths between the computers" (E.D. Tex. 6:07‑cv‑00080). In IPR2014‑00481 it was construed more broadly as a "transmission path between two devices that restricts access to data, addresses, or other information on the path … including … authentication, encryption, or address hopping," requiring that the link "traverse[] a portion of a public network." The Board in Appeal 2018‑001175 expressly held the construction "may, but does not require, computers to communicate directly with each other" — i.e., indirect/proxy-mediated communication is within the claim (Appeal 2018‑001175 Decision on Rehearing). This is decisive for obviousness, because it removes the principal escape hatch the patent owner used to distinguish proxy-based prior art.

2. The claim limitations that must be met

Claim 1 (per the '759 reexamination record) requires only:

1. Enabling a secure communication mode at the first computer without a user entering any cryptographic information for enabling that mode;
2. Establishing the secure link between the two computers based on the enabled mode; and
3. The link being a VPN communication link over the computer network.

Claim 16 is the computer-readable-medium counterpart with the same method body. Nothing in claim 1 requires address hopping, a discriminator field, a pseudo-random sequence, an icon click, or a download. Those features appear only in dependent claims. This matters enormously: the independent claim is directed to the ergonomic/administrative result of automating cryptographic enrolment, not to any novel cryptography.

3. The prior art of record and what each reference teaches

Also relevant — the patent's own background admissions. The '759 specification's "Prior Art" discussion admits that (i) "a user can employ a local proxy server in communicating over an encrypted channel with an outside proxy such that the local administrator or ISP only sees the encrypted traffic," and (ii) ZKS (Zero-Knowledge Systems) Anonymous IP Protocol "allows users to select up to any of five different pseudonyms, while desktop software encrypts outgoing traffic and wraps it in User Datagram Protocol (UDP) packets," with the user "permitted to control the number of hops." These are admissions that transparent, desktop-resident, encrypted tunnelling software requiring no user key entry was known. That materially shortens the distance between the prior art and claim 1.

4. Ground 1 — Kiuchi anticipates, or in the alternative renders obvious, claims 1 and 16

Claim 1 [1.0] — enabling a secure mode without a user entering cryptographic information. Kiuchi's user agent "should be specified as a proxy server for external (outside the firewall) access" and the client-side proxy performs the negotiation. All keying material — the C‑HTTP name server's certificates, the Nonces, the derived symmetric data-exchange key, and the connection ID — is generated and exchanged machine-to-machine. Kiuchi at 66: "the server-side proxy … generates both a connection ID derived from the server-side proxy's name, date and random numbers (32 bits) using MD5, and also a second symmetric data exchange key for response encryption." Nothing in Kiuchi requires the end user to type a key, password, or certificate. Kiuchi at 67: "In C‑HTTP, keys are stored only on the firewall of a given institution."

Claim 1 [1.1] — establishing the link based on the enabled mode. The client-side proxy's request to the C‑HTTP name server causes the automatic establishment of the secure connection; the name server "returns an IP address associated with the secure hostname," the server-side proxy "authenticates the client-side proxy" and issues a connection ID, and "the connection is established" (Kiuchi at 65–66). Establishment is a consequence of the security negotiation, not of user-supplied data.

Claim 1 [1.2] — VPN over the computer network. Kiuchi: "a closed HTTP-based virtual network can be constructed for closed groups … built on the Internet" (Kiuchi at 64, 69). Under both the Markman and IPR2014‑00481 constructions, this is a VPN over a public network.

This mapping was accepted by the Board across the family. See IPR2015‑01047 Institution Decision (docketalarm), and the Board's systematic reliance on Kiuchi to invalidate sibling claims (IPR2015‑01046, IPR2015‑01047; affirmed in VirnetX v. Apple, IPWatchdog, Mar. 31, 2023). The patent owner's only meaningful counter — a disclaimer of "indirect" VPNs made during reexamination of the '135 patent — was already litigated and rejected as applied to Kiuchi's direct-communication C‑HTTP design (VirnetX, 778 F. App'x at 906).

Why this is at minimum obvious even if anticipation is arguable: the sole arguable gap is whether "enabling a secure communication mode at the first computer" is disclosed as a discrete step. Even granting that gap, it is a matter of sequence and labelling, not of substance — enabling a proxy configuration that makes every subsequent connection secure is the same act as configuring the proxy. In re Kollar and In re Montgomery-type reasoning applies: the recitation of a step that is inherent in, or the necessary consequence of, a disclosed configuration does not confer patentability.

5. Ground 2 — Kiuchi in view of Kent (RFC 2401) (the ground the Board actually maintained)

This is not hypothetical: the Board, in Appeal 2017‑010852 Decision 1 (Feb. 11, 2016), entered new grounds of rejection of claims 1, 3–10, 12–16, 18–25 and 27–30 based on Kent, and maintained those rejections on rehearing on July 31, 2018, over the patent owner's argument that Kent disclosed an administrator, not a user, establishing security (CISCO Appeal 2017‑010852 Decision on Rehearing). The Board rejected that argument, holding Kent teaches "an embodiment where an application — as opposed to a user — can establish security services."

The combination. Kiuchi supplies the VPN-over-the-Internet with machine-negotiated keys and Nonces (claims 1 steps 1, 3); Kent supplies the express teaching that security services may be established by an application rather than by a user, i.e., automatic Security Association establishment without human entry of cryptographic material (claim 1 step 1's negative limitation).

Motivation to combine — the KSR/Phelps rationales:

1. Same field, same problem, same solution mechanism. Both references address securing communications across an insecure public network by automatic negotiation of session security parameters. Combining IPsec-style automated SA establishment with a proxy-mediated closed network is the combination of two references "from the same field of endeavor, … directed to the same purpose."
2. The prior art itself expresses the desire for transparency. Kiuchi's design goal is that "a C‑HTTP based network is made available simply by installing proxies" and that keys live on the firewall, not with users. RFC 2401's architecture incorporates automated key management precisely to relieve endpoints of manual keying. The asserted benefit of the '759 invention — that "a user can conveniently establish a VPN … without being required to enter user identification information, a password and/or an encryption key" — is the stated objective of the combined art.
3. Automation of a known manual step is obvious. Under KSR, "a court must ask whether the improvement is more than the predictable use of prior art elements according to their established functions." Relieving the user of manually entering key material that the system is already capable of generating and distributing (DHCP-style auto-provisioning per RFC 2131; IKE per Kent) is a paradigmatic design change — "the mere automation of a previously manual process" — with a predictable result.
4. Finite number of identified approaches. The available options for "get the crypto into the endpoint without the user typing it" were few and all known: pre-provisioned firewall-stored keys (Kiuchi), certificate/CA distribution, and automated negotiation (Kent/IKE). The claim selects none of them specifically — it merely claims the result.
5. Reasonable expectation of success. Both references concern packet-switched IP networking over the Internet; there is no interoperability barrier, and the combination requires no new hardware.

6. Ground 3 — the dependent claims

Even if claim 1 survived, the dependent claims add features that the same art supplies, singly or in combination:

• "Enabling by selecting a displayed hyperlink/icon" / "one-click" and "no-click." Aventail and the Aventail + RFC 2401 + RFC 2543 ground used in IPR2015‑00871 address a client-side VPN connection initiated by the user from the desktop. Independently, Kiuchi's own disclosure uses a connection-ID URL of the form http://server.in.current.connection/sample.html=@=6zdDfldfcZLj8Vli, which the user selects and which the client-side proxy converts into a secure connection request — i.e., selecting a displayed link causes the secure link to be established (Kiuchi at 65). That is the "click" limitation.
• "Determining whether a secure communication software module is stored on the first computer" and downloading it from a predetermined network address if not. Kiuchi at 68: "A C‑HTTP based network is made available simply by installing proxies on the firewall and registering their information with the C‑HTTP name server." Combined with the contemporaneous applet/ActiveX/plug-in distribution art and RFC 2131's automatic client configuration, installing-on-demand is the routine implementation of a known software-distribution requirement.
• "Data values that vary according to a pseudo-random sequence" / discriminator field. Kiuchi's Nonce values, generated by the C‑HTTP name service and validated against "a moving window of valid Nonce values," were mapped by the reexamination requester to the discriminator-field limitations of sibling claim 9 of the '180 patent (Exhibit E‑2, Kiuchi chart); RFC 2401's anti-replay sequence numbers supply an alternative. The '180 reexamination Board maintained rejections of analogous claims on this basis (Appeal 2018‑001175).
• Automatic re-establishment of the secure mode when a link comes up. Predictable automation of a known configuration step; both Kiuchi's proxy registration and RFC 2131-style auto-provisioning teach unwatched, automatic network joining.
• Secure DNS / non-standard TLD features. Being disclosed but not claimed in the '759 claims, these are largely irrelevant to the § 103 analysis of the '759 claim set; if any dependent claim incorporates them, note that VirnetX itself argued (and the Board found) that a "secure domain name" cannot be resolved by a conventional DNS — an admission that narrows the claim and invites a Kiuchi + RFC 1034 or Kiuchi + Rescorla combination, exactly the ground Mangrove/Apple used successfully against the '135 and '151 patents.

Combination motivation for the dependent claims mirrors Ground 2: each added feature is an implementation detail (client launcher, download mechanism, sequence-number validation) that the references address in the same context, and none produces an unexpected result. As the Board observed in the family proceedings, once the primary reference is properly construed, "the skill level involved here is moderately high," and such implementation choices are ordinary.

7. Rebuttal of likely patent-owner arguments

8. Bottom line

Claim 1 and claim 16 would have been obvious under § 103(a). The best ground is Kiuchi in view of Kent (RFC 2401) — the very ground the Board entered and maintained against these claims, and a ground with demonstrated success across the family. Kiuchi alone is a strong alternative on anticipation (or, failing that, single-reference obviousness). The dependent claims fall to the same primary references plus one or more of Aventail, Beser, RFC 2131, RFC 1034, and the H.235/H.323 key-exchange art, depending on the specific limitation.

The reason the combination is obvious is not merely that each element is separately known; it is that the asserted invention is defined by what the system does not require the user to do. Reducing manual user configuration is the expressed purpose of every reference in the combination, and under KSR that is a predictable, well-motivated design choice rather than a patentable advance.

Uncertainty flags

1. Verbatim ground table not retrieved. I did not obtain the Action Closing Prosecution's or Board Decision 1's itemized rejection table for 95/001,746; the specific reference pairings beyond "based on Kent" are my reconstruction from the requester's transmittal list and the Board's rehearing decision. Treat Ground 2 as well supported and Ground 3's sub-combinations as the strongest plausible pairings rather than as confirmed record.
2. Claim 16 text. As flagged in the earlier summary, claim 16's verbatim preamble is uncaptured. If its body differs materially from claim 1, the effect is likely minimal (the Board treated claims 1, 3–10, 12–16, 18–25, 27–30 together), but do not treat it as settled.
3. Claims 2, 11, 17, 26 were confirmed at the Action Closing Prosecution stage but rejected claims 1 and 16 were on appeal as of the Decision on Rehearing (July 31, 2018). I could not obtain the final inter partes reexamination certificate for 95/001,746. Do not represent any claim of the '759 patent as cancelled on the basis of this analysis.
4. Date discrepancy. The prior sections of this analysis state a 2026‑09‑30 analysis date with "Today's date 2026-09-30," while this task specifies April 26, 2026. The substantive analysis is unaffected, but the record should be reconciled before publication.
5. No 2026 appellate activity on the '759 patent specifically was identified — consistent with the earlier summary, and unsurprising given the October 29, 2019 anticipated expiration.