US 8051181

I'll search for current information on this patent number, then reconcile it with the authoritative patent text provided.

Let me search for the claim text and any 2026 docket activity.

Let me try to retrieve the actual claim text and check for any 2026 Federal Circuit docket activity.

Bottom line

I found solid, corroborated bibliographic data for US 8,051,181 and confirmed its litigation posture, including current (2026) Federal Circuit activity. However, I could not retrieve the verbatim claim set (the "What is claimed is" text) within this session, and no source I found shows any 2026 CAFC docket entry naming the '181 patent specifically. I flag that explicitly below rather than reconstruct claim language from memory.

One clarification on the authoritative text I was given: the Google Patents fetch (https://patents.google.com/patent/US8051181/en) contains the specification/definitions, classification, and metadata, but the OCR-extracted claim section is not present in the fetched body. So the claim overview below is an inference from the specification's own summary paragraphs (which in this family typically track the claims), not verbatim claim text.

Bibliographic data (authoritative — from the fetched patent text)

Note literally: the status shown is "Expired - Fee Related" with an adjusted expiration of 2020-04-29 — so as of 2026 the patent is not in force, regardless of the litigation history.

Abstract (verbatim; corroborated by multiple independent sources)

"A technique is disclosed for establishing a secure communication link between a first computer and a second computer over a computer network. Initially, a secure communication mode of communication is enabled at a first computer without a user entering any cryptographic information for establishing the secure communication mode of communication. Then, a secure communication link is established between the first computer and a second computer over a computer network based on the enabled secure communication mode of communication. The secure communication link is a virtual private network communication link over the computer network in which one or more data values that vary according to a pseudo-random sequence are inserted into each data packet."

Sources: Forbes (2011-11-07), Mandour Law (ITC complaint coverage), km-ip blog, AppleInsider forum — all reproduce this same abstract text for 8051181.

Plain-language overview of the independent claims — ⚠️ INFERENCE, NOT VERIFIED

I could not confirm verbatim independent-claim language. What follows is derived from the specification's summary section (which mirrors the claims in this family) and from a European search report on a same-priority family member (EP 2323335 A3, application EP 10 01 2357), which grouped claims as: (i) claims 1–4, 8–14, 16–19, 23–29 — "a method and computer readable medium for loading a secure communication software module"; (ii) claims 5–7, 20–22 — "a method and computer readable medium for forming a virtual private connection based on a computer address hopping regime"; (iii) a further group — "setting up a secure communication using a secure domain name server."

Based on that, the independent claims of the '181 patent most likely fall into roughly these families:

1. "One-click" VPN establishment. Enable a secure communication mode at the first computer without the user entering any cryptographic information (e.g., by merely selecting an icon or entering a command); then establish a secure communication link between the two computers based on the enabled mode. The link is a VPN link in which one or more data values varying according to a pseudo-random sequence are inserted into each data packet (i.e., an address-hopping / agile-network VPN), with dependent claims reciting address hopping, a moving window of valid values, or a discriminator field matched against a table of valid discriminator values.

2. Software-module loading / setup-parameter claims. Determining whether the secure communication software module is already stored on the first computer; if not, accessing a predetermined network address to load it; then automatically establishing the secure VPN link. A related variant recites entering a command defining a setup parameter so the secure mode is established automatically whenever a communication link is established.

3. Secure domain-name-service (SDNS) claims. Transmitting a non-standard top-level domain name (e.g., .scom, .sorg, .snet, .sedu, .smil, .sint) over the VPN to a predetermined network address (the SDNS), and/or a portal that authenticates a query against a domain-name database storing secure network addresses keyed to non-standard TLDs.

4. Application-layer encapsulation / firewall-traversal claims. Sending an information packet whose payload carries virtual-private-connection data inserted at the application layer of the client; the server-side receives it at the kernel layer of its OS, determines whether the packet contains that VPN data, and replies with a kernel-layer-modified packet — the packets being UDP, TCP/IP, or ICMP.

I would not rely on any of these as literal claim language. To get the authoritative claim set, the right sources are USPTO PatentCenter (application 11/679,416), Google Patents' claim tab, or FreePatentsOnline (http://www.freepatentsonline.com/8051181.html).

Litigation / PTAB posture (from the patent record and search results)

• PTAB: IPR2014-00485 and IPR2014-00486 (Unified Patents) — both listed as Not Instituted – Procedural. I found no instituted IPR or final written decision that invalidated the '181 itself in the sources retrieved; the high-profile VirnetX IPR losses concerned sibling patents ('135, '151, '504, '211).
• District court: Texas Eastern District Court, 6:11-cv-00563 (the November 2011 VirnetX/SAIC v. Apple action asserting the '181 against iPhones, iPads, iPods and Macs over FaceTime/VPN-on-Demand). That case produced the ~$368M Apple verdict in Nov. 2012.
• ITC: Section 337 investigations 337-TA-818 and 337-TA-858, both arising from the 2011 '181 complaint against Apple (the refiled complaint added SAIC to cure a standing/procedural defect).
• CAFC: The patent record lists appeals 19-1050 and 21-1672. Important caveat: VirnetX's own investor filings describe the substance of those appeals as concerning the '135, '151, '504 and '211 patents, not the '181 — the Google Patents entry is family-level litigation data, so those docket numbers should not be read as '181-specific merits rulings. For 19-1050 the CAFC affirmed in part/reversed in part (Nov 22, 2019), rehearing denied Feb 10, 2020; the related 19-1672 appeal was vacated as moot (Mar 31, 2023), rehearing denied Jun 27, 2023, and certiorari denied Feb 20, 2024.

2026 CAFC docket check — negative result

I searched specifically for 2026 Federal Circuit activity tied to 8051181 and found none. The 2026 VirnetX-related appellate reporting I retrieved concerns other VirnetX patents (headlines about the Federal Circuit "reversing part of the VirnetX v. Apple $502M verdict" and "tossing out two of four patent violations," with a remand to the E.D. Tex. to recalculate damages). Given that the '181 expired for fee-related reasons on 2020-04-29 and its family's main appellate fights have run their course (final cert denial Feb 20, 2024), the absence of a 2026 '181-specific docket is unsurprising — but treat this as "not found in the sources searched," not as proof of absence.

Confidence and caveats

• High confidence: number, title, inventors, application number and dates, assignee chain, expiry status, abstract text, and the ITC/E.D. Tex./PTAB case identifiers.
• Medium confidence: the four independent-claim families sketched above (grounded in the specification summary + a same-priority EP search report, but not verbatim).
• Uncertain: exact claim numbering, exact count of claims, and any 2026 CAFC docket specifically naming the '181. I did not auto-correct any identifier; "8051181" was used literally throughout, and I excluded hits for similar numbers except where explicitly noted as sibling-patent context.

I'll research litigation involving US patent 8051181. Let me run several searches.

Let me dig deeper into the specific cases involving the '181 patent.

Let me verify a few more specifics — the Cisco matter, the 2016/2018 Apple II verdict, and the PTAB proceedings.

Important caveats up front

• I'm working from the Google Patents page for US8051181 (fetched 2026‑09‑30) plus live web results. I was not able to reach portal.unifiedpatents.com or PACER directly before hitting my tool‑call limit, so the litigation list below is built from the Google Patents "Family has litigation" data, SEC filings (VirnetX 10‑K/10‑Q), Federal Register/USITC notices, and Federal Circuit filings. Treat items marked "unconfirmed" as needing a PACER/ITC/PTAB docket check.
• I have not auto-corrected any numbers. Case numbers, patent numbers and investigation numbers appear exactly as found in the sources.
• Note a recurring press error: several news outlets (e.g., the German ZDNet.de article and a MacMagazine piece) attribute the $368.2M November 2012 Apple verdict to US 8,051,181. VirnetX's own 10‑K describes that verdict as covering four other patents ('135, '504, '211, '151), and US 8,051,181 did not issue until November 1, 2011 — after the complaint in that case was filed. I flag this because it will otherwise contaminate any litigation list you build for the '181 patent.

Known litigation / proceedings involving US 8,051,181

Notes and context

• The only district‑court vehicle for the '181 patent identified in my sources is the E.D. Tex. line of cases originating with 6:11-cv-00563 (filed Nov. 1, 2011, asserting the '181 patent against Apple) and then folded into 6:12-cv-00855 via the July 1, 2013 consolidated and amended complaint. VirnetX's 10‑K states: "On July 1, 2013, we filed a consolidated and amended complaint to include U.S. Patent No. 8,051,181 and consolidate Civil Action No. 6:11-cv-00563-LED."
• Earlier VirnetX cases do not involve the '181 patent. The Aug. 11, 2010 case (6:10-cv-00417, against Aastra, Apple, Cisco and NEC) and the Jan. 12, 2011 case (6:11-cv-00018, against Mitel, Siemens and Avaya) predate issuance of the '181 patent (issued Nov. 1, 2011) and, per VirnetX's filings, asserted the '135, '504, '211 and '151 patents. Cisco's non‑infringement verdict (March 4, 2013) was in the 6:10-cv-00417 line and did not involve the '181 patent; the Federal Circuit appeal captioned VirnetX Inc. v. Cisco Systems, Inc., No. 18‑1197, is Apple's appeal from that case and likewise lists only '135, '151, '504 and '211.
• I could not confirm that any claim of the '181 patent was actually tried to a jury verdict. The published verdict descriptions for the consolidated January–February 2016 trial ($625.6M, Feb. 4, 2016) and the Sept. 30, 2016 Apple I retrial ($302.4M) and the ensuing appeals speak of the '135, '151, '504 and '211 patents. Third-party reporting (Southeast Texas Record) lists '181 among the patents in the third amended complaint in 6:12-cv-00855, so '181 was pleaded in Apple II.
• The Feb. 3–4, 2016 verdict in Apple II was $625.6M (jury found Apple's modified VPN On‑Demand, iMessage and FaceTime infringed; willfulness found). On July 29, 2016 the court vacated its consolidation orders and directed separate retrials; Apple I was retried (verdict $302.4M Sept. 30, 2016; final judgment Sept. 29, 2017 totaling ~$439.7M including enhanced damages, interest, costs and fees), and Apple II was reset for jury selection April 2, 2018. Post‑2018 outcomes and dollar figures for Apple II are not confirmed by my sources.
• PTAB proceedings against related patents (same family, not the '181 patent itself) include IPR2015-01046/‑01047 ('135 and '151; Mangrove Partners, joined by Apple and Black Swamp IP) and various Apple/Cisco reexaminations of '135, '504 and '211. Those are the cases behind VirnetX Inc. v. Mangrove Partners Master Fund, Ltd. and the 2019 Federal Circuit decisions (e.g., 931 F.3d 1363). They are related‑family litigation, not '181‑patent litigation — I mention them only so you don't mistakenly attribute them to the '181 patent.
• Google Patents litigation record for US8051181 also gives a "First worldwide family litigation filed" pointer to the Darts‑ip family 46300296, indicating foreign family litigation exists. I have not verified any non‑U.S. proceedings.

Patent status

The Google Patents record shows US8051181B2 as "Expired – Fee Related," adjusted expiration 2020‑04‑29, with original assignee/applicant VirnetX Inc. (inventors Victor Larson; Robert Dunham Short, III; Edmund Colby Munger; Michael Williamson) and assignment from Science Applications International Corporation recorded June 21, 2007.

Bottom line

Litigation touching US 8,051,181 is not absent. It centers on VirnetX's enforcement campaign against Apple: E.D. Tex. 6:11‑cv‑00563 (filed Nov. 1, 2011), absorbed into 6:12‑cv‑00855 (filed Nov. 6, 2012), plus two ITC investigations (337‑TA‑818, terminated for lack of standing in Aug. 2012; and 337‑TA‑858, instituted Oct. 16, 2012), plus a Unified Patents IPR pair (IPR2014‑00485/‑00486, not instituted) and an inter partes reexamination (95/001,949) that VirnetX appealed (Fed. Cir. 16‑1480), with the Federal Circuit affirming the PTAB's invalidity findings on Dec. 9, 2016. Federal Circuit appeal No. 19‑1050 (from 6:12‑cv‑00855‑RWS and 6:11‑cv‑00563‑RWS) is documented; No. 21‑1672 is listed in the Google Patents record but I could not verify its parties or disposition. For a definitive judgment docket, the next step would be to pull these case numbers directly from PACER and the ITC EDIS docket, which I was unable to do here.

I'll research this. Start with the proceeding numbers surfaced in the patent's family data and general VirnetX PTAB history.

Let me verify the panels, decision dates, and whether any other AIA proceedings touched this patent.

Key finding: the '181 claims were all canceled — but via inter partes reexamination, not IPR. Let me pin down the reexam details and check for any other challenges.

PTAB / AIA-trial report — US 8,051,181 B2

"Method for establishing secure communication link between computers of virtual private network" · VirnetX Inc. (orig. assignee: Science Applications Int'l Corp.) · priority 1998-10-30 · granted 2011-11-01 · Expired – Fee Related

Source-of-record caveat up front: the structured USPTO ODP block supplied with this file returns no AIA trial proceedings for this patent. That block is incomplete. Two AIA trials were filed on the '181 patent (both by Apple in March 2014); both were denied institution, so they never became "instituted trials" and would be excluded from any docket feed limited to instituted proceedings. I flag them below as web-sourced. Separately — and far more important — the patent's claims were all cancelled in a pre-AIA inter partes reexamination, which is not an AIA trial at all and therefore would never appear in an AIA-trial feed. A defendant reading only the ODP block would badly misread this patent's status.

Proceedings overview

Two AIA trial petitions were filed on the '181 patent — both IPRs by Apple, both denied institution on 2014-09-16 as time-barred under 35 U.S.C. § 315(b); zero institutions, zero Final Written Decisions, zero claim-level AIA rulings. Because the AIA-track record is empty, the patent's actual status comes from a different vehicle: Apple's inter partes reexamination Control No. 95/001,949, in which all 29 claims were rejected, affirmed by the Board, affirmed by the Federal Circuit, and cancelled by reexamination certificate on 2017-06-13. Breakdown: active 0 · claims invalidated by AIA trial 0 · claims sustained 0 · settled 0 · institution denied 2. Bottom line for a defendant: the PTAB never killed this patent, but the Patent Office did — claims 1–29 are cancelled. If a demand letter cites US 8,051,181, there is no live claim to infringe, and the '181 patent is now useful to you only as invalidating prior art / as evidence about a related VirnetX patent.

Control No. 95/001,949 — Apple Inc. (third-party requester) v. VirnetX Inc. — claims cancelled

Not an AIA trial. This is a pre-AIA inter partes reexamination under former 35 U.S.C. §§ 311–318, conducted by the examiner and reviewed on appeal by the PTAB. It is included first because it is the only proceeding that reached a merits, claim-level outcome on the '181 patent.

• Type: Pre-AIA inter partes reexamination (CRU/TC 3900) — included for completeness; not an IPR/PGR/CBM.
• Filed: Request filed 2012-03-28; Order Granting Request 2012-06-04.
• Status: Concluded — all claims cancelled. Inter partes reexamination certificate issued 2017-06-13, cancelling claims 1–29.
• Judge panel (PTAB appeal): Jeffrey B. Robertson, Denise M. Pothier (writing), Jeremy J. Curcuri. Oral hearing 2015-09-11.
• Petition/request grounds: All 29 claims rejected over Beser (US 6,496,867), Mattaway (US 6,131,121) and Provino (US 6,557,037). The Board's affirmance made these specific § 102 findings (quoted from the CAFC's 2016-1480 opinion):
  • "claims 1-12, 14, 15, and 17-29 anticipated by U.S. Patent No. 6,496,867 to Beser"
  • "claims 1, 2, 7-9, 12-17, 19-21, and 24-29 anticipated by U.S. Patent No. 6,131,121 to Mattaway"
  • "claims 1-15, 18-23, and 28-29 anticipated by U.S. Patent No. 6,557,037 to Provino"
• Institution / decision timeline: Action Closing Prosecution 2013-01-16; Right of Appeal Notice 2013-08-16; Owner Appeal Brief 2014-03-14; Examiner's Answer 2014-07-15; Board Decision on Appeal (Appeal No. 2015-004512) 2015-09-29 — "We AFFIRM the Examiner's decision to reject claims 1–29."
• Claim-level disposition: ALL claims 1–29 unpatentable/cancelled. No claim survived. The two references the Federal Circuit actually relied on — Mattaway and Provino — together cover every claim of the '181 patent (the court expressly declined to reach Beser).
• Illustrative claims as recited in the Board's decision (quoted exactly):
  • Claim 1: "A non-transitory machine-readable medium comprising instructions for a method of communicating with a first device associated with a secure name and an unsecured name, the method comprising: receiving, at a network address corresponding to the secure name associated with the first device, a message from a second device of the desired to securely communicate with the first device; and sending a message over a secure communication link from the first device to the second device."
  • Claim 2: "A method of using a first device to communicate with a second device having a secure name, the method comprising: from the first device, sending a message to a secure name service, the message requesting a network address associated with the secure name of the second device; at the first device, receiving a message containing the network address associated with the secure name of the second device; and from the first device, sending a message to the network address associated with the secure name of the second device using a secure communication link."
• Settlement / termination: None — litigated to final judgment.
• Appeal: Yes. VirnetX appealed to the Federal Circuit on 2015-11-30; docket VirnetX Inc. v. Apple Inc., No. 2016-1480 (Fed. Cir.). Issues: claim construction and the Board's anticipation findings over Mattaway and Provino (Beser not reached). Disposition: AFFIRMED, decided 2016-12-09 (O'Malley, Mayer, Wallach, J.J.; nonprecedential). Opinion: https://www.docketalarm.com/cases/US_Court_of_Appeals_Federal_Circuit/16-1480/VirnetX_Inc._v._Apple_Inc/docs/43.pdf
  • VirnetX publicly said it was "evaluating all of our options, including potentially seeking rehearing en banc." I could not confirm from the sources reviewed whether a rehearing petition was filed or denied; the reexam certificate issued 2017-06-13 nonetheless.
• Key sources: PTAB Decision on Appeal (Appeal 2015-004512) — https://www.finnegan.com/a/web/[58645/2016](https://assignmentcenter.uspto.gov/search/patent/reelFrameDetail?reelFrame=58645-2016).01.13-2015004512-Apple-v-Virnetx-Decision-Reexam.pdf · Apple's E.D. Tex. brief describing the reexam and the 2017-06-13 certificate — https://storage.courtlistener.com/recap/gov.uscourts.txed.[140694](/patent/140694)/gov.uscourts.txed.140694.964.0.pdf · VirnetX 2016-12-09 press release — https://ir.virnetx.com/news-releases/news-release-details/federal-circuit-issues-decisions-patent-office-proceedings
• Defensive value: Dispositive. Every claim you could be accused of infringing is cancelled. Any infringement theory built on claims 1–29 of the '181 patent is not merely weak — it is directed at a patent with no enforceable claims. If a demand letter or complaint asserts the '181 patent, that is a strong signal of a boilerplate portfolio assertion and a ground for fees/§ 285 argument.

IPR2014-00485 — Apple Inc. v. VirnetX Inc.

• Type: Inter Partes Review
• Filed: 2014-03-10 (verified by the Board's own decision; exhibit cover sheets in the record carry a 2014-03-07 date — the Board treats 2014-03-10 as the filing date). Challenged claims 1–29.
• Status (verbatim from the decision caption): "Denying Petitioner's Motion for Joinder and Denying Institution of Inter Partes Review, 37 C.F.R. §§ 42.108, 42.122" — i.e., no trial instituted; proceeding terminated. (The ODP-style docket shows status "Terminated.")
• Judge panel: Toni R. Scheiner (writing), Michael P. Tierney, Karl D. Easthom. (One law-firm summary lists the panel as "Easthom, Siu, Tierney"; the decision itself names Scheiner/Tierney/Easthom — trust the decision.)
• Petition grounds: Claims 1–29 challenged as anticipated under § 102 by either RFC 2543 or Provino, and as obvious under § 103 over various combinations including RFC 2543, RFC 1889, RFC 2327, RFC 2401, Kiuchi, Provino, Beser, and Kosiur. Grounds differed from those in IPR2014-00486. Also relied on the declaration of Dr. Roch Guerin.
• Institution decision: Denied — 2014-09-16 (Paper 18). Reasoning in two sentences: Apple was served with VirnetX's infringement complaint on the '181 patent on 2011-11-01, so its 2014-03-10 petition was facially outside the § 315(b) one-year window; Apple tried to cure the bar by moving to join its petitions into five other VirnetX proceedings that were timely filed — but those cases challenged a different patent (US 7,987,274) — and the Board held joinder under § 315(c) is discretionary and "not persuaded that joinder of proceedings involving claims of differing scope in two distinct patents is warranted or justified on the facts presented." Joinder denied ⇒ petition untimely ⇒ no institution.
• Final Written Decision: None.
• Settlement / termination: No settlement; terminated by the institution denial. No estoppel attaches.
• Appeal: None. (A denied-institution decision is not appealable to the Federal Circuit; VirnetX's counsel obtained non-institution.)
• Sources: Paper 18, Apple Inc. v. VirnetX, Inc., IPR2014-00485 (PTAB Sept. 16, 2014) — https://www.docketalarm.com/cases/PTAB/IPR2014-00485/Inter_Partes_Review_of_U.S._Pat._8051181/docs/09-16-2014-Board/Institution_Decision-18-Decision___Denying_Petitioners_Motion_for_Joinder_and_Denying_Institution_of_Inter_Partes_Review.pdf · practitioner summary — https://natlawreview.com/article/apple-inc-v-virnetx-inc-denying-institution-and-motion-joinder-ipr2014-00485 · VirnetX counsel case study — https://www.finnegan.com/en/work/experience/joinder-and-ipr-institution-denied-based-on-time-bar-ipr2014-00485-00486-ptab.html
• Defensive value: Apple tried to kill the '181 patent at the PTAB and was shut out on a timing technicality, not on the merits. Neither this IPR nor its companion produced a single claim ruling. Do not cite IPR2014-00485 for any proposition about claim validity — there is nothing there. It is useful only as: (a) a demonstration that the § 315(b) bar is enforced even where a petitioner offers a plausible joinder theory, and (b) a reminder that Apple's winning '181 argument ultimately ran through reexam, not the Board.

IPR2014-00486 — Apple Inc. v. VirnetX Inc.

• Type: Inter Partes Review
• Filed: 2014-03-10. Challenged claims 1–29 (different grounds from IPR2014-00485).
• Status (verbatim): "Denying Petitioner's Motion for Joinder and Denying Institution of Inter Partes Review, 37 C.F.R. §§ 42.108, 42.122" — no trial instituted; terminated.
• Judge panel: Toni R. Scheiner (writing), Michael P. Tierney, Karl D. Easthom.
• Petition grounds: Same statutory and reference universe as its companion (Apple described the two as raising "different grounds"), i.e. § 102 over RFC 2543/Provino and § 103 over combinations drawn from RFC 2543, RFC 1889, RFC 2327, RFC 2401, Kiuchi, Provino, Beser, and Kosiur.
• Institution decision: Denied — 2014-09-16 (Paper 18), on the same reasoning as IPR2014-00485: the § 315(b) one-year clock ran from 2011-11-01 service; Apple's motion to join these '181 petitions into Microsoft's and Apple's timely '274-patent proceedings was denied because § 315(c) joinder is discretionary and the two patents have "claims of differing scope"; without joinder the petitions were untimely. The Board noted VirnetX's opposition arguments that joinder would inject "nineteen new grounds of unpatentability, three new declarations totaling over 660 pages, and one declarant."
• Final Written Decision: None.
• Settlement / termination: No settlement; terminated by institution denial.
• Appeal: None (not appealable).
• Sources: Paper 18 — https://www.docketalarm.com/cases/PTAB/IPR2014-00486/Inter_Partes_Review_of_U.S._Pat._8051181/docs/09-16-2014-Board/Institution_Decision-18-Decision___Denying_Petitioners_Motion_for_Joinder_and_Denying_Institution_of_Inter_Partes_Review.pdf
• Defensive value: Identical to IPR2014-00485 — no merits ruling, no estoppel, no claim-level value. Note the Board's own Paper 18 in this case flags the parallel inter partes reexamination 95/001,949 as the live validity vehicle for the '181 patent — which is exactly where the patent died.

Strategic summary

Claim status on US 8,051,181. Every claim — 1 through 29 — is CANCELLED. Not narrowed, not partially sustained: the 2017-06-13 inter partes reexamination certificate cancelled all 29 claims after (i) the examiner's rejection of all claims, (ii) the Board's affirmance in Appeal No. 2015-004512 (2015-09-29), and (iii) the Federal Circuit's affirmance in VirnetX Inc. v. Apple Inc., No. 2016-1480 (Fed. Cir. 2016-12-09). Untested claims: none. Sustained claims: none. The claims most commonly asserted in VirnetX's '181 theories — claim 1 (the "non-transitory machine-readable medium … secure name" claim) and claim 2 (the "secure name service" method claim) — are both dead, and the Federal Circuit's affirmance rested on Mattaway and Provino, which together cover the entire claim set. If anyone tells you the '181 patent is "the TARP patent still in VirnetX's quiver," that is wrong for this patent number. (It is true that sibling VirnetX patents in the same specification family had a mixed record — the '151, '504 and '211 patents went through IPRs with real FWDs, and those FWDs were litigated up and down; but none of that is the '181 patent.) A defendant should independently verify the current status of whatever patent number a demand letter actually cites, and should not assume the '181 patent is a stand-in for its siblings.

Estoppel landscape. There is essentially no IPR estoppel facing a defendant on this patent. § 315(e)(2) estoppel attaches only after a Final Written Decision, and neither IPR2014-00485 nor -00486 produced an institution, let alone an FWD — so Apple's grounds (RFC 2543, RFC 1889, RFC 2327, RFC 2401, Kiuchi, Provino, Beser, Kosiur) remain un-adjudicated at the PTAB and un-estopped. The one-year § 315(b) bar in the 2014 decisions is also petitioner-specific; it does not run against a different defendant served at a different time. In practice this analysis is academic: with all claims cancelled there is no claim to invalidate, and the practical use of the reexam art is now offensive — Beser, Mattaway and Provino (all U.S. patents) are strong, Board-and-Federal-Circuit-endorsed § 102 art against the '181 patent's specification family, including against later VirnetX continuations that recycle the same "secure name / secure communication link" claim language. Note also that pre-AIA reexam estoppel (former § 315(c)) is keyed to claims "finally determined to be valid and patentable" — a condition that never arose here, since no claim survived.

Pattern signals. Apple was the sole AIA petitioner on the '181 patent, and it filed two parallel IPRs simultaneously (a common hedge when the grounds are alternative rather than cumulative), both dead on arrival at the § 315(b) gate. There is no defensive aggregator in the '181 chain — the Unified Patents attribution in the Google Patents family data is a data-provider credit, not a petitioner. VirnetX's PTAB appeal posture, by contrast, was aggressive and repeated: it appealed essentially every adverse VirnetX validity ruling in this era (16-1480 on the '181 reexam; consolidated 16-1211 on the '180/'274 FWDs; 15-1934 on the '697 FWDs; 17-2593 and 17-1591 in the Black Swamp IPRs), and while it sometimes won reversals in the IPR track, it lost the '181 squarely, on a nonprecedential affirmance in which the panel did not even need to reach the Beser ground. The family data also shows CAFC dockets 19-1050 and 21-1672, but I could not confirm from the sources reviewed that either concerns the '181 patent specifically — do not assume they do without pulling the dockets.

Recommended next steps

1. If you are a defendant and a demand letter or complaint cites US 8,051,181, the answer is documentary, not argumentative. Pull the reexamination certificate (Control No. 95/001,949, issued 2017-06-13, cancelling claims 1–29) and the Federal Circuit's disposition in No. 2016-1480 — "AFFIRMED" on the finding that "the Mattaway and Provino references … together cover all claims of the '181 patent" (https://www.docketalarm.com/cases/US_Court_of_Appeals_Federal_Circuit/16-1480/VirnetX_Inc._v._Apple_Inc/docs/43.pdf). The Board's underlying decision is at https://www.finnegan.com/a/web/[58645/2016](https://assignmentcenter.uspto.gov/search/patent/reelFrameDetail?reelFrame=58645-2016).01.13-2015004512-Apple-v-Virnetx-Decision-Reexam.pdf. All 29 claims are cancelled; there is no infringement case to answer. Consider a Rule 11 / § 285 posture if the assertion persists after notice.
2. If your real target is a related VirnetX patent (the '151, '504, '211, '135, '697, '180, '274 line), do not extrapolate from the '181 record. Those patents had a genuinely mixed PTAB history — some claims cancelled in FWDs, some claims surviving and being asserted for years — and the '181 patent's reexam route gives you no estoppel and no claim-level precedent for them. Confirm which patent number is actually asserted before building a strategy.
3. If someone is weighing a new AIA petition on the '181 patent: don't. Every claim is cancelled; a petition would be a waste of the fee and would be dismissed. The § 315(b) clock analysis in IPR2014-00485/-00486 is, however, worth citing if you are opposing a petitioner's motion for joinder under § 315(c) to cure an untimely petition — the Board's refusal to join proceedings on different patents is a clean, on-point authority.
4. Docket-hygiene note. The ODP AIA-trial feed for this patent is empty and will stay empty — non-instituted IPRs are not reflected, and the reexam is outside the AIA-trial schema. For this patent, always cross-check the reexamination certificate and file history (PTAB E2E / PatentCenter, Control No. 95/001,949) rather than relying on an AIA-trials-only view.

I'll research the actual assignment records before drafting. Let me run parallel searches.

Let me dig for the actual reel/frame numbers and correspondent data.

Ownership Record — US 8,051,181 B2

Patent: US 8,051,181 B2 — "Method for Establishing Secure Communication Link Between Computers of Virtual Private Network"
App. 11/679,416 · filed 2007-02-27 · issued 2011-11-01 · priority 1998-10-30 · status Expired – Fee Related (adjusted expiration 2020-04-29)
Verification entry points: USPTO Assignment Center · Assignment Search (legacy UI) · Google Patents legal events

Inventors

Unusual pattern — noted, but not the fire-sale type. The four inventors' assignment of their entire interest to SAIC was recorded 2007-06-21, roughly 8.5 years after the 1998-10-30 earliest priority date and in the same recordation window as the SAIC→VirnetX transfer. Ordinary employee invention assignments are recorded within weeks of execution; an eight-year lag recorded simultaneously with the portfolio sale is a signature of title-perfection due diligence ahead of a divestiture, i.e., SAIC cleaning up chain-of-title before/while selling. Second pattern: two of the four inventors (Short, Munger) moved to the acquiring entity (VirnetX, 2006) rather than away from the original assignee — the inventors followed the patents into the monetization vehicle. Munger and Short are identified in VirnetX's SEC filings as co-inventors on substantially all of the portfolio.

Original assignee

Two answers, because the face of the patent and the chain of title diverge:

• Named on the issued patent / current assignee: VirnetX Inc. (Google Patents lists both "Original Assignee" and "Current Assignee" as VirnetX Inc.; Espacenet lists applicants "VIRNETX INC; SCIENCE APPLICATIONS INTERNATIONAL CORPORATION; VIRNETX, INC").
• First assignee of the inventors' rights: Science Applications International Corporation (SAIC) — the operating defense/IT contractor.

VirnetX Inc. — incorporated in Delaware in August 2005 as a "development stage company… formed to commercialize a patent portfolio." Primary line of business: patent licensing and assertion for secure real-time communications (VPN/VoIP/DNS security). It attempted a product line (Secure Domain Name Registry / GABRIEL Connection Technology) but its revenue is licensing/settlement-derived. Wholly owned subsidiary of VirnetX Holding Corporation (NASDAQ: VHC), formed via reverse merger with PASW, Inc. in July 2007; HQ moved from Scotts Valley, CA to 308 Dorla Court, Suite 206, Zephyr Cove, Nevada. Status: operating, but as a public licensing/assertion entity, not a product company.

SAIC — large defense/technical-services contractor (San Diego, CA). Status: operating. In 2013 it separated into Leidos Holdings, Inc. (NYSE: LDOS) and a new SAIC. VirnetX's filings refer to its upstream counterparty as "Leidos, Inc. (f/k/a Science Applications International Corporation)." SAIC never filed bankruptcy; the patents were not sold in insolvency proceedings.

Assignment timeline

Record-retrieval caveat (stated plainly): the USPTO Assignment Center entries for this patent exist and are mirrored in Google Patents' legal-events feed, but the reel/frame numbers for the '181-specific records could not be retrieved in this session (the Assignment Center UI is not machine-readable here and no cached copy surfaced). Parties, dates and conveyance types below are taken from the Google Patents legal-events mirror of the assignment records and are corroborated by VirnetX's SEC filings. Reel/frame cells are left blank rather than guessed. The one reel/frame I can verify (50383/669) belongs to a sibling application, not to the '181, and is labeled as such.

1. Execution date not shown / recorded 2007-06-21 — Reel not retrieved

   • Conveyance: Assignment (reassignment)
   • Assignor: Larson, Victor; Munger, Edmund Colby; Williamson, Michael; Short, Robert Dunham, III
   • Assignee: SCIENCE APPLICATIONS INTERNATIONAL CORPORATION
   • Correspondent: not retrievable for this record
   • Context: title perfection — inventors' rights confirmed to SAIC (late recording, ~8.5 yrs post-priority).

2. Execution date not shown / recorded 2007-06-21 — Reel not retrieved

   • Conveyance: Assignment (reassignment)
   • Assignor: SCIENCE APPLICATIONS INTERNATIONAL CORPORATION
   • Assignee: VIRNETX, INC. (5615 Scotts Valley Drive, Suite 110, Scotts Valley, CA 95066 on the contemporaneous family records)
   • Correspondent: not retrievable for this record. Family-level data point: the only correspondent I could verify on this patent family is Lee Hayes, PLLC, 601 W. Riverside Ave., Ste. 1400, Spokane, WA 99201, on Assignment reel 50383/669 — SAIC→VirnetX, executed 2006-12-21, recorded 2019-09-16 — which covers application 15/185,760 ("Agile Network Protocol For Secure Communications Using Secure Domain Names"), a later continuation. Not confirmed as correspondent for the '181 record itself; treat as family context only.
   • Context: transfer-to-asserter — SAIC moves the portfolio to a newly formed licensing vehicle while retaining a continuing economic stake (see signal 7).

3. 2012-01-19 (recorded) — Reel not retrieved

   • Conveyance: Change of Address of Assignee (name/address change only — no change in ownership)
   • Assignor: n/a
   • Assignee: VIRNETX INC.
   • Correspondent: not retrievable
   • Context: administrative change-of-address only.

Unrecorded but documented encumbrance (flagged, not asserted as a recorded assignment): VirnetX's S-1/prospectus states it "granted SAIC a security interest in some of our intellectual property, including the patents and patent applications we obtained from SAIC," together with reversion-to-SAIC triggers and a 25%/35% proceeds-share to SAIC on enforcement recoveries. This is a documented contingent interest affecting standing (a Texas court held VirnetX lacked prudential standing alone because SAIC's objection rights + equity interest amounted to an ownership interest, forcing SAIC's joinder — and SAIC was added as co-plaintiff in the ITC complaint, Inv. No. 337-TA-858, on 2012-09-14). It does not appear as a separate recorded assignment on the '181 legal-events feed.

Timeline diagram

timeline
    title Ownership of US 8051181
    1998 : Earliest provisional filed by SAIC inventors
    1999 : Utility application filed
    2006 : SAIC agrees to assign family to VirnetX
    2007 : Inventor assignment recorded to SAIC
         : SAIC to VirnetX assignment recorded
         : VirnetX sues Microsoft
    2011 : Patent issues on 1 Nov
         : Apple suit filed naming this patent
    2012 : Change of address recorded for assignee
    2020 : Patent term ends

NPE / troll-pattern signals

1. Shell-entity transfer — PRESENT.
SAIC, an operating defense/IT contractor, assigned the family to VirnetX Inc., a Delaware entity incorporated August 2005 — after the inventions were made and roughly a year before the assignment (executed 2006-12-21 per the family record; recorded 2007-06-21). VirnetX's own SEC language describes it as "a development stage company… formed to commercialize a patent portfolio," with licensing/settlement as revenue. Caveat against over-reading the naming tell: VirnetX is not an anonymous single-member LLC — it is a publicly disclosed NPE under VirnetX Holding Corp (VHC), and it attempted a product (GABRIEL). The finding rests on the operating→licensing-only transfer and the absence of product revenue, not on the name.

2. Known asserter in the chain — PRESENT.
VirnetX is a high-frequency patent plaintiff surfaced across the asserter directories: it appears as assignee in the Unified Patents portal (e.g., US-8051181-B2 entry), and RPX Corporation filed seven IPRs against VirnetX patents (IPR2014-00171 through IPR2014-00177, filed Nov 2013). Enforcement history on this family and its siblings: Microsoft (E.D. Tex. 6:07-cv-00080, settled for $200M, 2010), Apple (6:11-cv-00563 filed 2011-11-01; 6:12-cv-00855; 6:13-cv-00211; 6:13-cv-00581), Cisco (6:10-cv-00417), Mitel/Siemens/Avaya (6:11-cv-00018), and ITC 337-TA-818 / 337-TA-858. The '181 patent was named in 337-TA-858 and in the Apple E.D. Tex. actions.

3. Repeat correspondent across the chain — UNCLEAR.
No correspondent of record is retrievable for any of the three '181 entries, so recurrence across the chain cannot be tested. The single verified family data point is Lee Hayes, PLLC (Spokane, WA) on reel 50383/669, which is one appearance only and covers a sibling application — per the prompt's own rule, a single appearance is not a finding. (Litigation/PTAB counsel — McKool Smith; Finnegan's Joseph E. Palys / Naveen Modi — are advocacy counsel, not assignment correspondents, and are not treated as this signal.)

4. Cascading transfers — NOT PRESENT.
Only one ownership transfer (SAIC→VirnetX, 2006/2007) plus a 2012-01-19 change of address. No chained LLCs, no serial re-assignments inside 24 months, no shared-agent addresses in the chain.

5. Pre-litigation transfer — NOT PRESENT for this patent (present at family level).
The ownership transfer predates the first suit naming the '181 by ~5 years (transfer Nov/Dec 2006 vs. VirnetX v. Apple, 6:11-cv-00563, filed 2011-11-01). The near-simultaneity pattern does exist a level up: the assignment executed 2006-12-21 and VirnetX filed against Microsoft on 2007-02-15, ~2 months later. But that suit asserted the '135 and '759 patents, not the '181. Marked not present for the '181 specifically.

6. Bankruptcy fire-sale — NOT PRESENT.
Neither SAIC nor VirnetX entered Chapter 7/11; no trustee/auction transfer appears. SAIC's 2013 split into Leidos/SAIC was a tax-free corporate separation, not insolvency.

7. Privateering — PRESENT (the strongest signal).
SAIC did not simply sell: it retained a continuing economic interest in the assertion proceeds. Per VirnetX's SEC filings, SAIC (now Leidos) is entitled to 35% of excess litigation recoveries from certain targets (Microsoft et al.) and 25% from others, plus 10% of any acquisition proceeds, a $35M cumulative royalty stream, an exclusive royalty-free license back outside VirnetX's field of use, and outright reversion of the patents to SAIC on payment default. A security interest was granted to SAIC over the very patents sold. Independent scholarship characterizes the arrangement as "VirnetX is a privateering NPE for Leidos," with Leidos receiving 20–30% of royalties/settlements/awards depending on target. SAIC's standing-controlling rights were litigated (defendants won a prudential-standing dismissal until SAIC was joined), and SAIC was added as co-plaintiff in ITC Inv. No. 337-TA-858 on 2012-09-14 specifically to cure that standing defect. This is the textbook operating-company → third-party-vehicle privateering structure.

8. Defensive aggregator — NOT PRESENT (inverse condition present).
The chain does not terminate at RPX, AST, LOT, Unified, or OIN. To the contrary, RPX is adverse — it petitioned for IPR against VirnetX (IPR2014-00171 et seq., denied as time-barred because Apple was a real party in interest). The portfolio remains in an asserting entity; it has not been neutralized.

Verdict

NPE — high confidence.

Two independent strong signals are documented, not inferred: (i) privateering — the original operating assignee (SAIC) retained a 25–35% contingency share of enforcement recoveries, a reversion right, a security interest, and a license-back, exactly the structure that distinguishes a privateering vehicle from an arm's-length sale, and the entity had to add SAIC as co-plaintiff in ITC 337-TA-858 to fix standing; and (ii) known asserter — VirnetX is an established high-frequency plaintiff (Apple, Microsoft, Cisco, Avaya, Siemens, Mitel, NEC, Aastra; RPX-filed IPRs IPR2014-00171–00177), and the operating→licensing-only transfer into a Delaware shell incorporated in August 2005 is a third (weaker) supporting signal. The pre-litigation and cascading-transfer signals are not present here, so this is a privateering-style NPE rather than a churned shell chain.

Verify at: https://assignmentcenter.uspto.gov/ (search patent number 8051181) — reconfirm the reel/frame numbers for the two 2007-06-21 recordings and the 2012-01-19 change of address, and pull the correspondent of record for each, which is the one field I could not retrieve.

I'll search for the USPTO record and, critically, the "References Cited" list that appears on the face of US 8,051,181. Let me run several targeted queries.

Good — I'm getting leads. Let me pull the actual "References Cited" list from multiple sources, including the USPTO report page and FreePatentsOnline.

The uspto.report page has the reference list. Let me drill into the specific U.S. patent documents cited on the '181 face, and cross-check against the sibling/parent patent (US 7,188,180) which shares the same reference set.

Scope, method, and a material limitation — read this first

I ran the requested USPTO-directed searches for the literal number 8051181. Two things must be stated up front, because they bound how much of the requested deliverable I can complete honestly:

1. The authoritative patent text I was given does not include the "References Cited" section. The fetched body (https://patents.google.com/patent/US8051181/en) contains the Abstract, Specification/Definitions, Classifications and bibliographic metadata — but the front‑page "(56) References Cited" list and the "What is claimed is" claim set are not present in that fetch. So I cannot reproduce the front‑page citation list verbatim from the authoritative source.

2. What I recovered about the citation list comes from USPTO-derived/third-party mirrors, principally uspto.report (a mirror of the granted US record) and a PTAB PTACTS petition PDF. I got the foreign patent documents and the non-patent literature ("Other References") listed on the '181 record, but I did not obtain a complete, verified list of the U.S. patent documents cited on the '181 face. I flag that gap explicitly rather than reconstruct it.

Literal-number discipline: everything below concerns US 8,051,181 B2 (application 11/679,416). Note that the citation list legitimately contains a GB 2334181 foreign document — that is a different (UK) document and is not to be conflated with US 8051181.

A. Citations appearing on the US 8,051,181 record (as retrieved)

A.1 Foreign patent documents

These are reproduced from the uspto.report/patent/grant/8051181 record (USPTO-derived). Some entries appear duplicated because the source lists them in multiple formats.

(Source: https://uspto.report/patent/grant/8051181)

I do not have reliable titles/assignees for most of these from the retrieved data, so I am not going to guess at descriptions.

A.2 Non-patent literature ("Other References")

(Source: https://uspto.report/patent/grant/8051181)

A.3 U.S. patent documents — NOT RETRIEVED

This is the piece you specifically asked for, and I want to be unambiguous: I was not able to obtain a verified list of the U.S. patent documents cited on the face of US 8,051,181. The searched mirror returned the foreign documents and the NPL, but not the U.S.-patent sub-table. I will not fabricate reference numbers, dates, or claim mappings to fill that gap.

Important cross-check note on the "self-citations": the '181 is, per the E.D. Tex. Markman record, a divisional of a continuation-in-part of application 09/504,783, and it shares a priority chain (1998‑10‑30 provisional → 09/429,643 → 09/504,783 → 10/702,486 → 11/679,416). Its siblings — US 6,502,135; 6,839,759; 7,010,604; 7,188,180; 7,418,504; 7,490,151; 7,921,211 — share the same priority and inventive entity and therefore are generally not § 102 prior art against the '181. If the '181 face lists them, they are family/priority cross-references, not anticipatory art. (E.D. Tex. 6:12‑cv‑855, Dkt. 180, at 2.)

B. Preliminary § 102 relevance assessment — heavily caveated

Two hard constraints force me to label this preliminary and non-conclusive:

• I do not have the verbatim claim set of the '181. § 102 anticipation requires that a single reference disclose every limitation of a claim, arranged as in the claim. Without the literal claims I cannot make a finding of anticipation; I can only indicate topical relevance.
• A reference appearing on the face of a patent is not a finding that it anticipates anything. Front-page listings are IDS citations; the "X/Y/A" relevance categories live in the examiner's search report and the file history, which I did not retrieve.

Within those limits, mapping to the claim families sketched in the earlier section (one-click/automatic VPN establishment; software-module loading; SDNS; application-layer encapsulation/firewall traversal; dependent claims on pseudo-random hopping / moving-window / discriminator fields):

Bottom line on § 102: On the record I could retrieve, I cannot identify any single reference that anticipates a specific claim of US 8,051,181. The most frequently recurring theme in the '181's citation list is the IPSec RFC family and the Fasbender Mobile-IP privacy paper, plus the foreign patent documents — but a § 102 conclusion is not supportable without (a) the verbatim claims and (b) the examiner's relevance categorizations from the file history.

C. References that are NOT '181 citations (flagged to prevent misattribution)

My searches surfaced several prior-art lists from other VirnetX proceedings. Do not treat these as citations on the '181:

• A PTAB PTACTS petition listed Aziz US 5,548,646 (filed 1994‑09‑15, issued 1996‑08‑20, "Signatureless Transmission…"), Yinger US 5,960,204 (filed 1996‑10‑28, issued 1999‑09‑28, "Installing Applications on an as-needed basis"), and Barlow US 5,204,961 (filed 1990‑06‑25, issued 1993‑04‑20, multilevel network security), together with RFC 1122, RFC 791, Caronni "SKIP," Maughan "ISAKMP," Edwards "High Security Web Servers and Gateways," and Lee RFC 1945. But that petition's exhibits reference the '135 and '151 patents, not the '181. These are candidates for the sibling patents' invalidity fights.
• The FreePatentsOnline page for US 9,413,766 (a later VirnetX family member) cites e.g. Rosen US 7,307,990 and Sheymov US 7,197,563 — those are the '3766's citations, not the '181's.
• The WO 2012/048206 A3 search report cites US 6,502,135 (Munger) as an "A" reference against a later application — again not a '181 citation.

I am not auto-correcting or merging any of these into the '181.

D. Where to obtain the authoritative data I could not

To complete the § 102 analysis properly, retrieve from authoritative sources:

• USPTO PatentCenter, application 11/679,416 — the file wrapper contains the PTO‑892 form ("References Cited"), the examiner's search report/IDS relevance codes, and non-patent-literature listings. (https://patentcenter.uspto.gov)
• USPTO Patent Public Search / PatFT for the granted patent's "(56) References Cited."
• Google Patents "Citations / Cited By" tabs and the claim tab for US 8,051,181.
• FreePatentsOnline: http://www.freepatentsonline.com/8051181.html — for the claim set and reference table.

E. What I could NOT verify (explicit)

• The complete U.S. patent document citation list on the '181 face (A.3).
• The verbatim claim set of US 8,051,181 (so any claim-number mapping above is an inference from the specification summary and a same-priority EP search report, not claim language).
• The examiner's § 102 vs § 103 relevance categories for any listed reference.
• Titles/assignees for most of the foreign documents in A.1.
• Any 2026 docket entry specifically naming the '181 — none found in the sources searched (consistent with the record showing the patent expired‑fee‑related, adjusted expiration 2020‑04‑29, per the earlier section's authoritative bibliographic data).

If you can supply the file-wrapper PTO‑892 (or the claim set), I can produce a reference-by-reference, claim-by-claim § 102 chart with actual citations rather than the indicative mapping above.

I'll research the prior art cited on this patent's page before running the §103 analysis.

Strong lead: the '181 was subject to inter partes reexamination 95/001,949, which cancelled claims. Let me pin down the specific prior art relied on.

Obviousness Analysis — U.S. Patent No. 8,051,181 (VirnetX)

Statutory framework: 35 U.S.C. § 103(a) (pre‑AIA, consistent with the '181's pre‑AIA priority chain and reexamination posture), applied per KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007), and MPEP 2141–2143.

0. Corrections to the previously generated section (flagged per instructions)

I found material that contradicts two statements in the earlier section. Treat these as superseding:

Consequence for this task: because all 29 claims were cancelled, the claims are legally treated as though they never existed (Fresenius USA v. Baxter, 721 F.3d 1330 (Fed. Cir. 2013)), and the fee‑related expiration of 2020‑04‑29 is moot. The § 103 question is therefore retrospective/defensive — useful for understanding the art, not for attacking a live claim.

1. What the "Prior Art" material on this page actually is — transparency

Two caveats before the analysis:

1. The fetched Google Patents body for US8051181 contains a "Prior art keywords" tag set: secure; message; packets; packet; tarp. These are algorithmically generated relevance tags, not citations of prior art. The fetched body did not include the "References Cited" list. I did not and will not treat those keywords as references.
2. The fetched body does contain the patent's own background discussion of the prior art: proxy servers, Chaum's mixes, the "crowds" scheme, the ZKS Anonymous IP Protocol / onion‑routing, and firewalls (the "Definitions"/"FIG. 1" block). Statements in a specification describing what was known can operate as admitted prior art (MPEP 2129). I flag that the fetch blends background text with detailed‑description text (the TARP/agile‑routing passages beginning "a secure mechanism for communicating over the internet employs … TARP routers" appear to be detailed description, not background), so any admission‑based argument must be verified against the printed columns before being asserted.

Since reexamination is limited to "patents or printed publications" (pre‑AIA 35 U.S.C. § 311), every reference below is documentary.

2. The prior art of record

Because the '181's claims were held unpatentable in a contested reexamination that was affirmed on appeal, the art of record is the single most authoritative § 103 evidence available. Per the Federal Circuit's summary of the PTAB decision (VirnetX v. Apple, No. 16‑1480):

The Federal Circuit affirmed without reaching Beser: "we find no error in the Board's claim constructions or findings with respect to the Mattaway and Provino references, which together cover all claims of the '181 patent." Mattaway ∪ Provino = claims 1–29.

Corroboration that these were the right families of art: the same reference families were applied across the family in other proceedings — Beser and RFC 2401/RFC 2543 in the sibling '163 IPR (Apple v. VirnetX, IPR2017‑00337 petition, where the Board found "Beser teaches a request to look up an IP address"); Aventail, RFC 2401 and RFC 2543 in IPR2015‑00871 (Finnegan FWD compendium); Kiuchi in the Mangrove/Apple IPRs (VirnetX cert petition appendix); and Provino as Apple's primary reexam reference against the '504/'211 (Fed. Cir., VirnetX v. Apple).

3. Independent-claim scope (grounded, with confidence noted)

• Claim 1 appears to require: a message of a desire to securely communicate is received … at a network address corresponding to a secure name associated with the first device, and then another message is sent over a secure communication link from the first device to the second device. This is quoted from Apple's stay motion summarizing VirnetX's own ACP response (Ex. L, 95/001,949) — high confidence, since it is patentee‑authored claim gloss.
• Independent claims 1, 2, 28 use the term "secure communication link," which VirnetX told the examiner "requires encryption" under BRI (Ex. I at 10) — high confidence.
• VirnetX also disclaimed a secure communication link that is not "direct," distinguishing Aventail on the ground that "[a]ll communications between the client and target stop and start at the intermediate SOCKS server" (VirnetX's opening claim construction brief). This is a binding narrowing constraint on any § 103 theory and is discussed in § 5.
• The EP search report for same‑priority EP 2 323 335 A3 groups the family's claims as: (i) "loading a secure communication software module"; (ii) "forming a virtual private connection based on a computer address hopping regime"; (iii) a third group (EP2323335A3). Medium confidence that this maps onto the '181's independent claims; I could not retrieve the verbatim '181 claim set. The previously generated inference of an "application‑layer encapsulation / firewall‑traversal" claim family in the '181 is unverified and I do not rely on it.

4. § 103 analysis

4.1 Threshold point: three separate single references anticipate the claims

A claim that is anticipated by a single reference is, a fortiori, obvious — the Federal Circuit repeatedly describes anticipation as "the epitome of obviousness." Here the Board found three independent single‑reference anticipations covering every one of claims 1–29, and the Federal Circuit affirmed the judgment of unpatentability on two of them. Any proposed combination that includes Beser, Mattaway, or Provino as the primary reference therefore carries an extremely strong prima facie case, and the motivation‑to‑combine inquiry collapses into the "combining prior art elements according to known methods to yield predictable results" rationale (MPEP 2143(A)).

I therefore analyze obviousness in two tiers: (A) the record grounds, and (B) reconstructed multi‑reference combinations.

4.2 Ground A — record grounds (strongest)

A‑1. Mattaway + Provino (the ground actually affirmed). Mattaway alone anticipates claims 1, 2, 7–9, 12–17, 19–21, 24–29; Provino alone anticipates claims 1–15, 18–23, 28–29. Because the two sets jointly cover all 29 claims, the Board's § 103‑equivalent bottom line is that no claim recites anything beyond the two references' collective disclosure. Motivation: both address the identical problem of brokering a connection to a destination that is not directly addressable on the public network — the "finite number of identified, predictable solutions" situation under KSR. A PHOSITA in October 1998 choosing between address‑assignment/name‑resolution mechanisms and secure‑connection brokers had a small, well‑enumerated menu (proxy, SOCKS, relay, tunnel broker, name server).

A‑2. Beser (+ Mattaway or Provino). Beser's teaching that a node issues "a request to look up an IP address" (as the Board found in the '163 IPR) supplies the secure‑name → network‑address element of claim 1 directly. Adding Mattaway or Provino to Beser supplies any residual connection‑establishment and encryption elements, with the rationale of substitution of one known element (a directory/lookup‑based setup) for another (a broker‑based setup) to obtain a predictable result.

A‑3. Beser + Aventail. Aventail (a commercial SOCKS‑based secure remote‑access product, applied with RFC 2401/RFC 2543 in IPR2015‑00871) supplies a fully commercialized secure remote‑access solution. Motivation: improving a name‑resolution/setup system with a known client‑initiated secure‑access gateway. Caveat: VirnetX's disclaimer requires direct client↔target communication, so this ground must be pleaded with Aventail's server in a non‑terminating role; otherwise it is self‑defeating (see § 5).

4.3 Ground B — reconstructed combinations

B‑1. Kiuchi + Rescorla (S‑HTTP) + RFC 1034 (+ RFC 2401/RFC 2543) — the secure‑name/DNS family.
Kiuchi (T. Kiuchi & S. Kaihara, "C‑HTTP — The Development of a Secure, Closed HTTP‑based Network on the Internet," Proc. SNDSS 1996) plus RFC 1034 (Mockapetris, "Domain Names — Concepts and Facilities") plus Rescorla & Schiffman's S‑HTTP Internet‑Draft were the § 103 ground actually briefed in the '151/'211 proceedings (Supreme Court petition appendix). Motivation: Kiuchi teaches a closed, secure, name‑addressed network on the open Internet; RFC 1034 teaches the standard name‑to‑address lookup machinery; a PHOSITA seeking to let a user type a name rather than an ephemeral address would predictably look to the DNS model. Note the literal‑reading flag: the petition cites RFC 1034 as "Nov. 1997," whereas RFC 1034 is historically November 1987. I do not auto‑correct the identifier; either date is prior art, but the discrepancy should be verified against the reference itself before reliance.

B‑2. Aziz + Caronni (SKIP) [+ Edwards; + Martin] — the "pseudo‑random data values in each packet" / "no user‑entered cryptographic information" family.

• Aziz et al., U.S. Patent No. 5,548,646, "System for Signatureless Transmission and Reception of Data Packets Between Computer Networks," filed 1994‑09‑15, issued 1996‑08‑20.
• Caronni et al., "SKIP — Securing the Internet," 5th Int'l Workshops on Enabling Technologies (WET ICE '96), June 1996.
  These (with Edwards and Martin as secondary references) were used in claim charts against the '759, '151, '135 and '504 family members (PTACTS exhibit listing for the Microsoft/Mitel invalidity contentions). Motivation: Aziz/SKIP disclose automated, signatureless session‑key establishment and per‑packet security‑association identifiers. Aziz's key‑ID field that changes per packet is a known technique for tagging packets against a moving window of valid values, and SKIP's cryptographic‑cookie/Diffie‑Hellman directory exchange is a known technique for establishing keys without the user manually entering keying material. A PHOSITA seeking to make VPN setup transparent to the user (the very problem the '181's abstract frames) had a strong, explicit reason to apply SKIP's automatic key management to a tunneling system.

B‑3. Stallings + Eastlake (DNSSEC) + Halsall (sliding window) + Wells ("Security Icon") — the printed‑publication cluster cited in the same‑priority EP search report.
The EP search report for EP 2 323 335 A3 cites, with relevance codes:

• X — W. Stallings, Cryptography and Network Security, Principles and Practice, 2nd ed., pp. 399–440 (§§ 13.4 "Encapsulating security payload," 13.5 "Combining security associations") — against claims 1 and 16;
• Y — D. Eastlake, "Domain Name System Security Extensions," Internet‑Draft (Apr. 1998) — claims 15, 30;
• Y — F. Halsall, Data Communications, Computer Networks and Open Systems (Addison‑Wesley, 1996), pp. 198–203 (sliding window; § 4.3.4 sequence numbers) — claims 6, 21;
• Y — Laurie Wells, "Subject: Security Icon," Usenet microsoft.public.inetexplorer.ie4.security (1998‑10‑19) — claims 12, 13, 27, 28;
• Y — US 5,689,566 (Nguyen); WO 98/27783 (Northern Telecom); WO 98/55930 (Philips) — claims 4, 9–11, 14, 18, 24–26, 29 and 5, 7, 20, 22.

Motivation, element by element:

• Stallings supplies the complete IPSec ESP + security‑association architecture (encapsulation, encryption of the payload, association chaining). A PHOSITA building a secure overlay on IP in 1998 would, as a matter of ordinary design practice, implement it as an ESP‑style encapsulated payload — the "known technique to improve similar devices in the same way" rationale.
• Halsall supplies the classic sliding‑window/sequence‑number validation technique, which is precisely the "moving window of valid values" concept: a receiver accepts any of the next N expected sequence values and rejects everything else. Combining a packet‑tagging scheme with a sliding window is an obvious substitution of one known validation mechanism for another, with predictable results (robustness to reordering/loss without weakening rejection of forgeries).
• Eastlake (DNSSEC) supplies secure, authenticated name resolution, motivating the "secure domain name" element.
• Wells (a Usenet post in an Internet Explorer security newsgroup) supplies the user‑facing "click a security icon to enable a secure/encrypted session" concept — i.e., enabling the secure mode without the user entering cryptographic information. This is the single most direct documentary hit on the '181's one‑click framing. Date vulnerability: 1998‑10‑19 is only 11 days before the '181's earliest priority date (1998‑10‑30); its status turns on (i) whether the asserted claims are entitled to the provisional's date, (ii) whether the invention was reduced to practice earlier, and (iii) whether a Usenet newsgroup posting qualifies as a publicly accessible "printed publication." Each is a real, litigable issue — but the content match is close, and the same "one‑click/icon" concept also appears as a Y reference in the EPO's reasoning, which is independent corroboration that examiners treated it as material.
• WO 98/27783 and US 5,689,566 supply the storing/loading‑a‑software‑module‑to‑establish‑the‑secure‑connection element (the "is the module already on the machine; if not, fetch it from a predetermined address; then connect" family), with the obvious motivation of reducing user and administrator configuration overhead.
• WO 98/55930 (Philips) supplies address‑selection variation.

B‑4. The '181's own background as admitted prior art. The specification describes proxy servers, Chaum's mixes, "crowds," ZKS onion routing with layered encryption, UDP‑wrapped, hop‑controlled traffic and untraceable IP addresses, and firewalls. A § 103 ground may cite these admissions as evidence of the state of the art and of the PHOSITA's familiarity with hop‑by‑hop layered encryption and decoys — which is the conceptual core of "data values that vary according to a pseudo‑random sequence inserted into each data packet." (Verify the background/detailed‑description split in the printed patent first — see § 1.)

4.4 Motivation‑to‑combine rationales (MPEP 2143)

1. Known elements combined by known methods → predictable result. Each of the three record references and each secondary reference addresses a discrete, well‑understood function (name lookup, address assignment, encapsulation, key exchange, packet validation, UI enablement). Assembling them into a secure remote‑access system yields nothing more than the expected sum of the parts.
2. Finite number of identified, predictable solutions. By late 1998 the design space for "let a client securely reach a resource on a public network" was small: proxy/SOCKS, IPSec tunnel, secure name‑server‑brokered connection, or overlay routing. KSR holds that where a finite number of predictable options exists, the selection is obvious.
3. Design incentive / market pressure. The references themselves evidence the demand (Wells' newsgroup traffic; Aventail's commercial product; ZKS's commercial onion‑routing service discussed in the '181's background). Reducing user‑entered keying material and configuration was an explicit, recognized goal.
4. Substitution of one known technique for another. Sliding windows in place of full sequence tables (Halsall); secure name resolution in place of manual address exchange (Eastlake/RFC 1034); automatic session‑key establishment in place of manual keys (Aziz/Caronni).
5. Teaching of the problem by one reference + the solution by another. Kiuchi/Aventail teach the problem of securing a closed community over an open network; RFC 2401/Stallings teach the ready‑made solution (ESP tunnels + security associations).

5. Anticipated counterarguments, and how they fare

6. Bottom line

1. The claims are obvious over the record prior art, and this is no longer an open question. All 29 claims of US 8,051,181 were rejected in inter partes reexamination 95/001,949 and cancelled by certificate on 2017‑06‑13; the Board's judgment of unpatentability — resting on anticipations by Provino (U.S. 6,557,037), Mattaway (U.S. 6,131,121) and Beser (U.S. 6,496,867), with Provino and Mattaway together covering every claim — was affirmed by the Federal Circuit in Appeal No. 16‑1480. Three separate single‑reference anticipations make the § 103 case stronger than the usual one.
2. The best reconstructed § 103 grounds, in descending order of strength: (A‑1) Mattaway + Provino; (A‑2) Beser + Mattaway or Provino; (B‑1) Kiuchi + Rescorla (S‑HTTP) + RFC 1034, all anchored to the direct‑communication disclaimer; (B‑2) Aziz '646 + Caronni (SKIP) [+ Edwards + Martin] for the per‑packet varying‑value and automated‑key‑management elements; (B‑3) Stallings (ch. 13.4/13.5) + Halsall + Eastlake (DNSSEC) + Wells ("Security Icon") + WO 98/27783 / US 5,689,566 for the encapsulation, sliding‑window, secure‑name, one‑click‑enablement and module‑loading elements.
3. Motivation is readily articulated: identical problem, finite and predictable solution set, component substitutions of known techniques for known purposes, and explicit market/design incentive — the KSR/MPEP 2143 playbook.
4. Where a challenger should be careful: RFC 2401 (November 1998 date, and the printed‑publication fight VirnetX actually won on this point in IPR2016‑01585), RFC 2543, and the late‑1998 secondary references (Wells, 1998‑10‑19); and the direct‑communication disclaimer, which disqualifies any ground built on a terminating intermediate server.
5. Confidence: high on the reexamination outcome, the three record references, the claim count and the independent claims; medium on the reconstructed combinations B‑1/B‑2/B‑3 (grounded in family‑level and same‑priority‑EP citations rather than the '181's own file wrapper or claim text); unverified — I could not retrieve the verbatim '181 claim set in this session, and the claim mappings in § 2 are as reported by the Federal Circuit's summary of the PTAB decision, not from the claim text itself. The previously generated claim‑family inference (especially the "application‑layer encapsulation / firewall traversal" family) should be treated as superseded by § 2.