US 8306994

I'll search for authoritative data on this patent, then cross-check against the full patent text provided.

Let me check for any 2025–2026 Federal Circuit activity and current ownership.

US 8,306,994 B2 — Summary

Important caveat up front: My searches did not return any Court of Appeals for the Federal Circuit docket for 2026, nor any USPTO proceeding squarely on the '994 patent itself. I will not invent one. What follows distinguishes (a) data I verified from the granted patent text and search results, from (b) items I could not confirm.

---

Bibliographic data (from the granted patent front page)

Note the number is 8,306,994 — not to be confused with the sibling family members 6,317,837; 7,739,302; and 8,892,600, which appear together in the same litigation complaints.

Ownership history (Google Patents assignment records): Robust Networks, LLC → Mineral Lassen LLC (2015) → Intellectual Ventures Assets 57 LLC (2017) → IQ Holdings, LLC (2018) → Firenet Technologies, LLC (Apr. 13, 2018). Google Patents lists the current assignee as Firenet Technologies LLC. A later 2019 security-agreement reassignment entry names KEMP Technologies Inc. and Brightwood Loan Services LLC, which is collateral-related rather than a change in patent ownership; I'd flag this as something to verify against USPTO assignment records rather than read literally as an ownership transfer of the '994 patent.

---

Abstract (verbatim)

"Dedicated firewall security for a network attached device (NAD) is provided by a firewall management system integrated directly into the NAD or into a NAD server. A local area network arrangement includes a network client and the NAD and the firewall management system includes computer readable medium having computer-executable instructions that perform the steps of receiving a request for network access to the NAD from the network client, determining whether the request for network access to the NAD is authorized, and only if the request for network access is authorized, providing the network client with network access to the NAD."

---

Plain-language overview of the independent claims

The '994 patent has three independent claims: 1 (apparatus/"network arrangement"), 10 (method), and 17 (non-transitory computer-readable storage medium).

Claim 1 — System / network arrangement. A LAN with a network client, a NAD server, and a NAD attached to that server such that the server controls all access to and from the NAD. The server receives a request (in a data packet) from the client, filters the packet based at least on an IP address in its header to decide whether access to the NAD is authorized, then processes the packet for communication with the NAD and grants access if authorized — and denies it otherwise. The key idea: a firewall sits at the NAD server, so access to the device is gated there rather than only at the network perimeter.

Claim 10 — Method. Steps performed by a NAD server on an internal network, where the NAD is attached such that it can receive communications from the internal network only through the NAD server. The NAD server includes a NAD server firewall. The firewall decides authorize/deny based on filtering at least the IP header of the request packet; the server then processes the packet and enables access if authorized, and blocks access if denied.

Claim 17 — Non-transitory computer-readable storage medium. Stored instructions that cause the NAD server to: process a request packet (with at least an IP header) for access to a NAD that is coupled by an interface such that all access requests are processed by the NAD server; filter at least the IP header; authorize based on information in the IP header indicating the source and destination of the packet; process the packet and enable access on authorization; and block unauthorized requests.

Representative dependent claims: the external/bastion firewall operating independently of the NAD server's protection (claims 2, 16); an operating system that processes authorized packets, optionally across multiple network protocols (3, 4, 11, 12, 18, 19); a data manager component with an interface component to the NAD (5, 6, 13, 20); proxy behavior — establishing a link to another server and sending the packet over it (7, 14, 21); and filtering based on network interface, port, or protocol (8, 15, 22). Claim 9 recites authorization based on header information relating to a network source.

Drafting observation: independent claim 17's body refers to "the NAD server firewall" without that element being expressly introduced earlier in the claim, an apparent antecedent-basis gap. I note it as an observable artifact; whether it was ever tested in litigation or reexamination I could not confirm.

---

Prosecution / family context

The specification describes the two-component "NADFW-MS": a firewall component (header-completeness, authorized interface, valid source/destination address, correct port; discarded packets logged) and a data management component (network protocol programs plus interface mechanisms such as SCSI, and optionally acting as a proxy to a second NAD server). The pre-grant publication US 2010/0242098 A1 as indexed by third-party sources shows a claim set of claim 1 with claims 2–45 canceled — i.e., the published version differs from the 22-claim granted set. Treat that publication-vs-grant difference as an indexed-document artifact worth confirming against the file wrapper.

(The 45-claim set I encountered at FreePatentsOnline/y2002/0049899 belongs to US 2002/0049899, the publication of application 09/951,877 — a different document in the same family. I am deliberately not importing it into the '994 record.)

---

Litigation (verified from search results)

The Google Patents page flags "Family has litigation." Cases asserted on the family, naming the '994 patent among the patents-in-suit:

• Firenet Tech LLC v. Fujitsu Ltd, E.D. Tex. 2:18-cv-00270 (filed 07/05/2018; now closed)
• FireNet Technologies, LLC v. KEMP Technologies Inc., S.D.N.Y. 1:18-cv-05564 (filed 06/20/2018) — the complaint's Count III pleads infringement of the '994 patent, specifically claim 10, against KEMP LoadMaster products
• FireNet Technologies, LLC v. Fortinet Inc., N.D. Cal. 3:19-cv-00798 (filed 02/14/2019; closed 08/09/2019)
• FireNet Technologies, LLC v. Citrix Systems, Inc., N.D. Ga. 1:19-cv-03199 (filed 07/12/2019)
• A further N.D. Cal. case, 3:18-cv-06502

PTAB: IPR2020-00471, Unified Patents LLC v. Firenet Technologies LLC, filed Mar. 13, 2020, challenged the '600 sibling patent (8,892,600), not the '994. Notably, US 8,306,994 was submitted as Exhibit 1011 and US 7,739,302 as Exhibit 1012 in that IPR. The proceeding was terminated (termination decision Mar. 18, 2021). No IPR specifically against the '994 patent appeared in my results.

---

What I could not confirm

1. No CAFC 2026 docket for patent 8,306,994 was returned. It is also worth noting the '994 patent's adjusted expiration is Dec. 22, 2018, so a 2026 appeal would most plausibly be a residual damages/licensing matter rather than an active-infringement appeal — but I have no evidence of any such appeal and state this as absence of information, not as a finding.
2. The exact current assignee (Firenet Technologies LLC vs. post-2019 collateral/release entries involving KEMP Technologies Inc. and Brightwood Loan Services LLC) should be verified against the USPTO Assignment database rather than relied on from aggregator pages.
3. I could not verify which specific claims of the '994 patent survived each of the district court cases (dismissals, settlements, or invalidity findings), nor whether the '600 IPR termination had any estoppel or collateral effect on '994 claim 10.

Grounding sources: the authoritative full text supplied for US 8,306,994 B2 (patents.google.com/patent/US8306994/en), the granted-patent PDF at patentimages.storage.googleapis.com (US8306994.pdf), Justia's page for publication 20100242098, RPX Insight for US8892600B2, Unified Patents litigation portal entries, dockets.justia.com case 4:2019cv00798, and the ex parte/Patexia materials for IPR2020-00471.

I'll search litigation-specific sources for this patent number, then verify each case.

Now let me verify each specific case, including status/termination.

Let me check the Unified Patents case list for this patent and the remaining case outcomes.

I hit the tool-step ceiling mid-verification, so some outcomes below remain unconfirmed — I flag each one rather than filling gaps. Everything I did verify is cited.

---

Litigation Involving US 8,306,994 B2

Bottom line: Five district court cases are on record asserting the '994 patent, all filed by FireNet Technologies, LLC between June 2018 and July 2019. No litigation filed after July 12, 2019 surfaced. No Court of Appeals for the Federal Circuit appeal, no ITC § 337 action, and no AIA trial against the '994 was found. One PTAB proceeding involving the family exists (IPR2020-00471), but it challenged sibling US 8,892,600 — the '994 entered that record only as Exhibit 1011.

---

Case table

Google Patents lists exactly these five family-litigation links ("Family has litigation"), matching the set above: E.D. Tex. 2:18-cv-00270; S.D.N.Y. 1:18-cv-05564; N.D. Ga. 1:19-cv-03199; N.D. Cal. 3:19-cv-00798; and N.D. Cal. 3:18-cv-06502 (US8306994B2).

---

Per-case detail

1. FireNet Technologies, LLC v. KEMP Technologies Inc. — S.D.N.Y. 1:18-cv-05564

• Filed June 20, 2018 · Presiding Judge Andrew L. Carter, Jr. · Magistrate Barbara C. Moses designated · Nature of suit: Patent, 35 U.S.C. § 271 · Jury demanded by plaintiff.
• Counsel: Dmitry A. Kheyfits, Andrey Belenky, Hanna Glomska Cohen (plaintiff); Stewart M. Leviss (defendant).
• Docket of record: summons issued 2018-06-21; service affidavit 2018-06-28 (served 6/27/2018, answer due 7/18/2018); extension granted 7/13/2018; KEMP's answer with jury demand filed 8/17/2018 (UniCourt, Justia dockets).
• Per the earlier-generated section of this analysis, Count III of the complaint pleads the '994 patent, specifically claim 10, against KEMP LoadMaster products.
• Status: The UniCourt snapshot (last updated 2018-08-19) shows "Pending – Other Pending." I could not retrieve a termination entry. Circumstantial, not probative: the assignment record shows a 2019-04-05 security agreement naming KEMP TECHNOLOGIES INC. as assignor to Brightwood Loan Services LLC, as collateral agent, released back to KEMP on 2022-01-24. That timing is consistent with a settlement/license, but the instrument is a lien, not a title transfer, and I do not read it as a KEMP outcome. ⚠️ Verify on PACER.

2. Firenet Technologies, LLC v. Fujitsu Ltd. et al. — E.D. Tex. 2:18-cv-00270

• Filed July 5, 2018 · Judge Rodney Gilstrap · Magistrate Roy S. Payne · (the Google Patents litigation link labels this case "Critical").
• Defendants: Fujitsu Ltd. and Fujitsu America, Inc.
• Docket: scheduling conference 3/18/2019; mediator Hon. David Folsom appointed 3/26/2019; agreed protective order 4/9/2019; docket control order setting Markman 10/29/2019, jury selection 5/4/2020 (all from the Unified Patents civil docket for 2:18-cv-00270).
• Then: "Joint MOTION to Stay All Deadlines and Notice of Settlement," followed by "Joint MOTION to Extend Stay" and a "Consent MOTION to Dismiss with Prejudice." Status is recorded as Closed (Ex Parte case record).
• Counts: Count III = the '994 patent; Count IV = the '600 patent (per the reproduced complaint text, ¶¶33–43, at RPX litigation documents).
• Unresolved: a docket fragment at ptacts.uspto.gov shows a 12/15/2022 order granting a stipulation of dismissal as to Fujitsu America, Inc. without prejudice under Rule 41(a)(1)(A)(ii), in a case with at least 79 docket entries. That entry is consistent with a post-settlement housekeeping dismissal, but I could not confirm the fragment belongs to 2:18-cv-00270 rather than a different Firenet matter. Do not rely on it without pulling the docket.

3. FireNet Technologies, LLC v. A10 Networks, Inc. — N.D. Cal. 3:18-cv-06502

• Filed Oct 24, 2018 · initially assigned Magistrate Judge Susan van Keulen; reassigned to Judge Vince Chhabria 12/4/2018.
• Status: Closed 2019-01-22, latest docket entry 2019-02-04; RPX records 91 days in litigation and cause of action "Willful Patent Infringement." Patexia records the status as "Dismissed – Settled," termination date 2019-01-22 (RPX Insight, Patexia summary).
• This is the shortest-lived case in the campaign — dismissed roughly three months after filing, and while active it overlapped with the earlier-filed KEMP and Fujitsu actions.

4. FireNet Technologies, LLC v. Fortinet Inc. — N.D. Cal. 4:19-cv-00798

• Filed February 14, 2019 · Magistrate Judge Kandis A. Westmore · (Google Patents' family-litigation link renders this as 3:19-cv-00798; the Justia docket renders it as 4:2019cv00798. I am not auto-correcting either string — treat the leading division digit as a discrepancy to confirm on PACER.)
• Docket of record: certificate of interested entities filed 2/21/2019 identifying corporate parent Intelleq Holdings, LLC and affiliates Invention Investment Fund I, LP; Invention Investment Fund II, LLC; Intellectual Ventures Assets 54, LLC; and Intellectual Ventures Assets 57, LLC; summons returned executed 2/22/2019; stipulation extending Fortinet's time to respond filed 3/14/2019 (Justia dockets).
• The '994 patent is expressly named in the docket: the 2/14/2019 filing-2 report is a "REPORT on the filing or determination of an action regarding U.S. Patent Nos. 6317837, 7739302, 8306994, 8892600."
• Status: docket last retrieved March 14, 2019; no termination or judgment located. ⚠️ Unverified. Note that a docket described in the earlier-generated summary as "closed 08/09/2019" was not confirmed by any source I retrieved this session — I flag it as unverified rather than repeat it as fact.

5. FireNet Technologies, LLC v. Citrix Systems, Inc. — N.D. Ga. 1:19-cv-03199

• Filed July 12, 2019 (per the Google Patents family-litigation link). Counsel per the earlier-generated section: Kheyfits Belenky LLP with Daniel Arthur Kent (Kent & Risley, LLC) appearing in Georgia.
• Status: Not verified. This was my last outstanding query and the search budget ran out before I could pull a termination entry or judgment. ⚠️ Verify on PACER.
• Caution: a different Citrix patent case (T5.2 Ltd. v. Citrix, S.D. Fla. 24-cv-62093) surfaced in my searches. It is unrelated to the '994 and must not be conflated with this one.

---

Family PTAB proceeding (context — not a '994 proceeding)

IPR2020-00471, Unified Patents, LLC v. Firenet Technologies, LLC — challenged US 8,892,600, not the '994. The '994 was filed as Unified Patents Exhibit 1011 ("Kentworthy '994"), alongside Ex. 1012 ('302) and Ex. 1013 ('837) (Patexia docket).

New evidence this session resolves a gap in the earlier-generated PTAB and assignment sections, both of which left the outcome "unknown":

• Trial instituted — "Trial Instituted Document," 2020-09-01 (scheduling order same day).
• Final Written Decision — 2021-03-18, holding all challenged claims of US 8,892,600 (claims 1–17 and 19–23) unpatentable. Unified Patents' own announcement: "On March 18, 2021, the Patent Trial and Appeal Board (PTAB) issued a final written decision in Unified Patents, LLC v. Firenet Technologies, LLC holding all claims of U.S. Patent 8,892,600 (claims 1-17 and 19-23) unpatentable" (Unified Patents, 2021-03-18).
• A "Termination Decision Document" docket entry also dated 2021-03-18 closes the proceeding.
• Unified's write-up names the campaign defendants as "Kemp Technologies, Fortinet, Citrix, A10 Networks, and Fujitsu" — matching the five cases above.

This is a correction to the earlier-generated sections. The PTAB section stated the FWD was "Unknown / not retrieved" and cautioned "do not treat this proceeding as having produced any estoppel or cancellation." It did produce cancellation of the sibling's claims. Unified's summary of the '302 Patroll contest independently confirms the campaign's defendant list (Patroll).

Critically, this produced no claim-level outcome for the '994. No estoppel, no cancellation, and no Board holding touches claims 1–22 of the '994.

---

What I did not find

1. No Federal Circuit appeal concerning the '994 or the family was located. Absence of a search hit is not proof of absence — I could not run CourtListener or the CAFC docket within the available budget.
2. No ITC § 337 investigation involving the '994.
3. No AIA trial, reexamination certificate, or disclaimer directed at the '994.
4. No litigation filed after July 12, 2019. Combined with the recorded expiration date of 2018-12-22, this is consistent with the campaign being wound down or settled rather than continuing.
5. No outcome data for cases 1 (KEMP), 4 (Fortinet), or 5 (Citrix).

---

Discrepancies and limits, stated plainly

1. Priority date conflict — do not auto-correct: Google Patents gives the '994 priority/filing date as 1998-09-01; the Unified Patents portal entry for US-8306994-B2 states "Priority Date: 1998-08-31." These are one day apart and I have left both exactly as found. The 1998-09-01 date is the one used throughout the earlier-generated sections and the one that appears in the family tables.
2. Fortinet case number: appears as 3:19-cv-00798 (Google Patents) and 4:19-cv-00798 (Justia). Reported literally.
3. Fujitsu docket fragment: the 12/15/2022 Rule 41(a) dismissal of Fujitsu America without prejudice cannot be confirmed as belonging to 2:18-cv-00270. Flagged.
4. KEMP security-interest entries: the 2019-04-05 Brightwood collateral agreement and the 2022-01-24 release are lien instruments. They do not establish that KEMP took title to the '994 and do not establish the outcome of 1:18-cv-05564.
5. Search truncation: I reached the tool-step limit. Cases 1, 4, and 5 need PACER/Unified Patents caselist confirmation before being relied on.

Grounding sources: US8306994B2, Google Patents; Unified Patents civil docket, 2:18-cv-00270; Unified Patents civil docket, 3:18-cv-06502; UniCourt, 1:18-cv-05564; Justia, 1:18-cv-05564; Justia, 4:19-cv-00798; RPX Insight, 3:18-cv-06502; Patexia, 3:18-cv-06502; Patexia, IPR2020-00471; Unified Patents insight, 2021-03-18; Unified Patents Patroll contest, US 7,739,302; Ex Parte case record, 2:18-cv-00270; Ex Parte complaint analysis, 2:18-cv-00270.

I'll verify against public sources before writing up, since the structured block defaults to "no PTAB activity."

The first pass surfaced something important: the '994 appears in an IPR record — but possibly as prior art, not as the challenged patent. Let me pin that down.

Let me search the USPTO PTAB records and Unified's portal directly for proceedings naming the '994.

Proceedings overview

Zero AIA trial proceedings are on file against US 8,306,994. The structured ODP block in this prompt returns no IPR, PGR, or CBM for this patent — 0 active, 0 claims invalidated, 0 claims sustained, 0 settled, 0 institution denials — and my independent web checks did not surface any petition, institution decision, or Final Written Decision naming the '994 as the challenged patent.

The bottom-line defensive posture is unusual and, on balance, more favorable to a defendant than any IPR could be: the bibliographic record for the '994 shows "Expired – Fee Related," expires 2018-12-22 (US8306994B2). A defendant today faces an expired patent whose entire claim set (claims 1–22) is PTAB-untested but also, for practical purposes, unenforceable going forward — no injunctive relief and (subject to the § 286 six-year lookback, discussed below) no recoverable damages. The absence of PTAB activity here is not evidence of a "hardened" patent; it is a symptom of a patent that lapsed before the 2018–2020 assertion campaign against the family matured into AIA challenges.

One caveat on the source rule: the ODP list is canonical for this patent, and it is empty. The proceeding below is a family proceeding, not a proceeding against the '994. I include it because it is the single most probative item of PTAB intelligence about this patent family and because the record in it names the '994.

---

IPR2020-00471 — Unified Patents, LLC v. Firenet Technologies, LLC

⚠️ Not a proceeding against US 8,306,994. The challenged patent is US 8,892,600 (a continuation of the '994 in the same Kenworthy family). The '994 appears in the record only as Petitioner's Exhibit 1011, "U.S. Patent 8,306,994 ('Kenworthy '994')" (Patexia case record). I am reporting it as context; it created no claim-level outcome for the '994.

• Type: Inter Partes Review (35 U.S.C. §§ 311–319; § 103 grounds)
• Filed: 2020-03-13
• Status: Not stated in the sources I could retrieve. The Patexia docket shows Patent Owner activity into at least 2020-06-22 (Power of Attorney for Patent Owner Firenet Technologies, LLC), so the proceeding was live at that point. I could not retrieve the institution decision, an FWD, or a termination order, and I will not guess at the outcome.
• Judge panel: Not retrieved. (Not reported in the sources available to me.)
• Petition grounds (per the Ex Parte AI-Lab petition analysis) — challenged claims 1–17 and 19–23 of the '600:
  • Ground 1 — § 103, claims 1–14, 16, 17, 19–22 obvious over Coley (US 5,826,014) in view of Coss (US 6,098,172). Petitioner mapped Coley's firewall (318) to the claimed "first computing device," Coley's web server (322) + attached hard drive to the "second computing device" with "attached device," and argued Coley's proxy agent "reformulates" packets by initiating new connection requests. Coss supplied IP-source/destination-based filtering.
  • Ground 2 — § 103, claims 15 and 23 obvious over Coley + Coss + Shand (US 6,147,976), with Shand supplying the limitation of "logging . . . information regarding data packets that are rejected."
  • Ground 3 — § 103, claims 1–14, 16, 17, 19–22 obvious over Coss + Gelb (US 5,550,984).
  • No § 112 grounds were asserted. Note the challenged set omits claim 18 — worth flagging if you are mapping this against claim scope.
• Institution decision: Unknown / not retrieved. I could not confirm whether the Board instituted, partially instituted, or denied. Do not treat this proceeding as having produced any estoppel or cancellation without pulling the papers.
• Final Written Decision: Unknown / not retrieved. Consequently I make no representation about whether the '600's claims — or any claim — were canceled or sustained. The one substantive linkage I can state with confidence is that the '994 was never the subject of the FWD; it entered as an exhibit.
• Settlement / termination: Not retrieved. If a termination-by-settlement exists, its terms would in the ordinary course be confidential.
• Appeal: No Federal Circuit appeal identified. (I could not search CourtListener or the CAFC docket for this proceeding within the available tool budget — treat as unverified, not as confirmation of no appeal.)
• Defensive value: Two things matter here. First, a defensive aggregator (Unified Patents) considered the family worth attacking — its own write-up describes Firenet Technologies, LLC as "an IP Investments affiliate and well-known NPE" and states the family was asserted in five district court cases against Kemp Technologies, Fortinet, and Citrix (Unified Patents, 2020-03-16). Second, and more pointedly, the challenger's target was the '600 continuation, and the '994 entered the record as an exhibit rather than as the patent on trial. If you are facing assertion of the '994, the more dangerous family member historically was the '600 — and the '994 appears to have been treated as a document, not as a threat.

---

Strategic summary

Claim status. There is no PTAB claim-level adjudication of US 8,306,994. Claims 1–22 are all UNTESTED at the PTAB — no independent claims canceled (claim 1, claim 10, claim 17 are the independent claims as issued), no dependents canceled, none sustained, none disclaimed in an AIA filing that I could find. That is a genuinely different situation from "survived two IPRs and is hardened": nothing has been tested, so you cannot rely on prior PTAB findings, but you also inherit no adverse claim constructions and no Board endorsement of the patent's validity. The relevant "narrowing" is not claim-based at all — it is temporal. The record lists the '994 with an adjusted expiration of 2018-12-22 and status "Expired – Fee Related" (US8306994B2). That date is consistent with a 20-year term running from the family's 1998-09-01 priority/filing date (the '954 parent), plus adjustment — i.e., end-of-term expiration, not a stray lapse. Confirm this in USPTO Patent Center and the maintenance-fee record before you build a case on it, because it is the pivot of the whole defense.

Estoppel landscape. Because no IPR or PGR was instituted on the '994, no § 315(e)(2) estoppel attaches to anyone with respect to this patent. There is no petitioner, real party in interest, or privy who is barred from raising any § 102/§ 103 ground — in district court or at the Office — against the '994. The estoppel that exists runs the other way: any estoppel generated in IPR2020-00471 binds Unified Patents and its privies only as to the '600, and only for grounds raised or reasonably could have been raised there. Practically, that means every prior-art ground against the '994 remains open, including the family-internal art. If Unified's Coley/Coss/Shand/Gelb combinations were good enough to put the '600 on trial, those references — and the '994's own disclosed embodiments and file-history statements — are candidates for a § 102/§ 103 attack on the '994 in Article III court. Note also that the '994's published application (US20100242098A1, published 2010-09-23) sits in the family chain, so any argument you build around the family's shared specification should be checked for § 102(e)/§ 102(a)(2) and common-ownership consequences.

Pattern signals. Several, and they are coherent. (1) One AIA petitioner, and it was a defensive aggregator — Unified Patents, which files to protect members rather than to win infringement leverage, challenged the family once (2020-03-13). (2) The aggregator aimed at the continuation, not at the '994. That is a tell: the '600 was the live assertion vehicle against Kemp/Fortinet/Citrix, and the '994 was, by 2020, a prior-art exhibit in its own child's IPR. (3) No patent-owner appeal activity is visible on the '994, which is unsurprising for an expired patent. (4) The assignment chain is the standard NPE trail — Robust Networks LLC → Mineral Lassen LLC (2015-11-18) → Intellectual Ventures Assets 57 LLC (2017-09-26) → IQ Holdings LLC (2018-01-19) → Firenet Technologies, LLC (2018-04-13) — with Firenet Technologies LLC now listed as current assignee. (5) Anomaly worth verifying: the assignment record also contains a 2019-04-05 security interest to Brightwood Loan Services LLC, as collateral agent, with Kemp Technologies Inc. as assignor, released back to Kemp Technologies Inc. on 2022-01-24. Kemp was a named defendant in the Firenet campaign, so this may be collateral instrumentation in a settlement/license rather than a title transfer — but the indexing is ambiguous and I would not read it as anything more without the underlying documents.

---

Recommended next steps

1. Lead with expiration, not with invalidity. This is the whole ballgame for a defendant in 2026. The '994 is recorded as expiring 2018-12-22. Pull the maintenance-fee record and the Patent Term Adjustment calculation from USPTO Patent Center (PatentCenter) and confirm it. If it holds:

• No injunctive relief is available against an expired patent.
• § 286 damages are effectively zero for a new suit. Recovery is limited to infringement committed within six years before the complaint. A complaint filed on or after 2024-12-22 cannot reach any act of infringement, because there were no acts after 2018-12-22. Even a complaint filed between 2018-12-22 and 2024-12-22 would be confined to a shrinking pre-expiration window.
• Demand-letter leverage collapses accordingly. If the demand cites the '994's independent claims, the response is not "your claims are invalid" — it is "your patent expired before any actionable damages period and you cannot obtain an injunction."

2. Do not count on PTAB activity as a weapon, because the PTAB has already declined the invitation. There is no '994 proceeding to await, and none is likely: the patent is expired and 28 years from its 1998-01-01-family priority, which makes discretionary denial under current Office practice highly probable. If a live, pre-expiration damages claim somehow exists in an older pending case, an IPR is theoretically available on an expired patent, but the better vehicle to consider would be an ex parte reexamination at the Central Reexamination Unit, which is not subject to § 314 discretionary denial.

3. Mine IPR2020-00471 for your invalidity case — but pull the primary documents first. The petition is public via Unified's portal and the Patexia docket, and the art stack (Coley US 5,826,014; Coss US 6,098,172; Shand US 6,147,976; Gelb US 5,550,984) is directly re-usable against the '994's substantially identical disclosure — the '600 and '994 share the same Kenworthy specification. Retrieve the institution decision and any FWD from USPTO PTAB E2E / PTAB Decisions and check FreeLaw's CourtListener for any CAFC appeal of the '600 outcome, since a Federal Circuit affirmance cancelling '600 claims would be powerful § 282 corroboration of your '994 invalidity theory (and, if any '600 claims survived, an equally clear signal about which limitations the Board found the art does not reach). I could not retrieve either document, so treat the outcome of IPR2020-00471 as unknown until you do.

4. Verify the real party behind the demand. Confirm who currently owns and who is asserting the '994. The public record shows Firenet Technologies, LLC as listed assignee, but the Brightwood/Kemp security-interest entries are unexplained and sit in the same time window as the district court campaign (E.D. Tex. 2:18-cv-00270; S.D.N.Y. 1:18-cv-05564; N.D. Ga. 1:19-cv-03199; N.D. Cal. 3:19-cv-00798 and 3:18-cv-06502). Get a Rule 3.1/standing chain and check whether the asserted claims were previously licensed or released to Kemp — an already-licensed or already-released defendant would have a complete defense independent of expiration.

---

Verification notes / limits, stated plainly. (a) The canonical ODP list is empty for the '994 and I found no contradicting proceeding; I did not invent any proceeding number. (b) IPR2020-00471 is real and verified, but it challenged the '600, not the '994 — do not cite it as an '994 invalidation. (c) I could not obtain the institution decision, FWD, judge panel, settlement status, or any appeal for IPR2020-00471, and I have deliberately left those fields as "unknown" rather than filling them in. (d) The "Expired – Fee Related / 2018-12-22" status is from the Google Patents bibliographic record for US8306994B2; confirm against USPTO maintenance-fee and Patent Term Adjustment records before relying on it.

I'll research this patent's ownership chain and litigation history before building the record.

Let me dig into the original assignee history and the specific assignment entities.

Ownership & Assignment Analysis — US 8,306,994 B2

Patent: Network attached device with dedicated firewall security
App. No. 12/773,716 · Filed 2010-05-04 · Granted 2012-11-06 · Priority 1998-09-01
Family: US 6,317,837 B1 (granted 2001-11-13, from App. 09/144,954) → US 7,739,302 B2 (2012? no — granted 2010-06-15, from App. 09/951,877) → US 8,306,994 B2 (this patent) → US 8,892,600 B2 (granted 2014-11-18, from App. 13/665,523)
Legal status: Expired – Fee Related; adjusted expiration 2018-12-22

Sourcing caveat (read first). The authoritative record I was able to retrieve for this patent is the Google Patents legal-events table (fetched 2026-09-12) plus court dockets and RPX/Unified Patents materials. That source exposes the parties, conveyance type and dates for each recorded assignment but does NOT expose reel/frame numbers or the correspondent of record. I could not verify the Assignment Center entries live within this session. Accordingly, every reel/frame field below is marked [not in retrieved record — verify] rather than filled in. I have not inferred or invented any reel/frame or correspondent. Verify at:

• https://assignmentcenter.uspto.gov/ (search "8306994")
• https://assignment.uspto.gov/patent/index.html (same underlying records)

---

Inventors

• Stacy Kenworthy is the only named inventor on US 8,306,994 and on the three sibling patents (referenced throughout the trial record as "Kentworthy '994 / '302 / '837" — Unified Patents, IPR2020-00471, Exhibits 1011–1013).
• Employer at time of filing: the root application 09/144,954 was filed 1998-09-01 and issued as US 6,317,837 to Applianceware, LLC (per the Google Patents family-citation table). The later chain shows Opticaute, Inc. as assignor to Robust Networks, LLC. I can state the assignees of record; I cannot confirm Kenworthy's employment relationship with Applianceware from the retrieved record. Flagged as determinable only in part.
• Unusual pattern — assignee churn, not inventor churn: I found no evidence of inventor departures. What is anomalous is corporate-identity churn around a single inventor: the family moved across at least three operating-company names (Applianceware → Opticaute → Robust Networks) before the 2015 merger, i.e. the patent was an asset in search of a home long before it was asserted. Departure dates for the inventor could not be established — unclear.

---

Original assignee

• Entity on the face of US 8,306,994: ROBUST NETWORKS LLC (Google Patents "Original Assignee"; the 2010-05-04 continuation was filed under that name — Robust Networks was actually the transferee of record in the 2010-12-20 assignment from Opticaute, Inc.).
• Entity on the family's root patent (US 6,317,837): Applianceware, LLC.
• Primary line of business: both appear to have been small network-appliance / network-attached-storage software vendors. The patent itself describes a "NAD server" running a network-attached-device and firewall management system — i.e. software for serving CD-ROM towers, printers and video codecs across a LAN (cols. 1–3; FIGS. 1–3).
• Did they ship a product embodying the claims? No evidence found. No product literature, no SEC filings (both are private), no marketing record surfaced. Not determinable from the retrieved record — treat as no demonstrated product.
• Current status: Robust Networks, LLC — merged out of existence, expressly stated in the 2015-11-18 record ("Merger", assignor Robust Networks, LLC → Mineral Lassen LLC). Opticaute, Inc. and Applianceware, LLC: no current status evidence found.

---

Assignment timeline

Per the USPTO records as indexed on Google Patents legal events. Reel/frame and correspondent are not exposed by that source and are left to verification.

1. 1998-09-01 (executed) / recorded [n/a] — Reel [verify]

   • Conveyance: Original application filed / assignment to operating company
   • Assignor: Stacy Kenworthy
   • Assignee: Applianceware, LLC (as issued on US 6,317,837)
   • Correspondent: [not in retrieved record — verify]
   • Context: original prosecution-stage assignment to the operating startup that commissioned the invention.

2. 2010-05-04 — application 12/773,716 filed by Robust Networks, LLC (legal event "Application filed by ROBUST NETWORKS LLC"). Reel [verify] — recorded as a filing event, not a recorded conveyance.

3. 2010-12-20 (recorded) — Reel [verify]

   • Conveyance: Assignment of assignors' interest
   • Assignor: OPTICAUTE, INC.
   • Assignee: ROBUST NETWORKS, LLC
   • Correspondent: [not in retrieved record — verify]
   • Context: internal re-org / identity transfer — the prosecution entity taking clean title before issuance.

4. 2015-11-18 (recorded) — Reel [verify]

   • Conveyance: MERGER
   • Assignor: ROBUST NETWORKS, LLC
   • Assignee: MINERAL LASSEN LLC
   • Correspondent: [not in retrieved record — verify]
   • Context: acquisition by merger — first hop out of the operating-company world. Mineral Lassen LLC is a well-documented Las Vegas-based patent-holding vehicle (address of record 2215-B Renaissance Drive, Suite 5, Las Vegas, NV 89119, per EP register entries for its RFID portfolio).

5. 2017-09-26 (recorded) — Reel [verify]

   • Conveyance: Assignment of assignors' interest
   • Assignor: MINERAL LASSEN LLC
   • Assignee: INTELLECTUAL VENTURES ASSETS 57 LLC
   • Correspondent: [not in retrieved record — verify]
   • Context: transfer into an Intellectual Ventures securitization/asset-holding structure — IV Assets 57 is a stated affiliate of FireNet per its own Rule 7.1 disclosures.

6. 2018-01-19 (recorded) — Reel [verify]

   • Conveyance: Assignment of assignors' interest
   • Assignor: INTELLECTUAL VENTURES ASSETS 57 LLC
   • Assignee: IQ HOLDINGS, LLC
   • Correspondent: [not in retrieved record — verify]
   • Context: deed-in-lieu / asset drop-down — second IV-side hop, three months before assertion.

7. 2018-04-13 (recorded) — Reel [verify]

   • Conveyance: Assignment of assignors' interest
   • Assignor: IQ HOLDINGS, LLC
   • Assignee: FIRENET TECHNOLOGIES, LLC
   • Correspondent: [not in retrieved record — verify]
   • Context: transfer-to-asserter — the Georgia monetization vehicle that filed suit 68 days later.

8. 2019-04-05 (recorded) — Reel [verify]

   • Conveyance: Intellectual Property Security Agreement (not an assignment)
   • Assignor: KEMP TECHNOLOGIES INC.
   • Assignee: BRIGHTWOOD LOAN SERVICES LLC, AS COLLATERAL AGENT
   • Correspondent: [not in retrieved record — verify]
   • Context: securitization/lien — KEMP (the first defendant in this campaign) pledging IP as loan collateral. Note the anomaly: this patent is a Firenet/IV asset, not obviously a KEMP asset. Possibly a shared portfolio reel or a settlement-driven transfer. Treat as unresolved — do not read as proof that KEMP took title.

9. 2022-01-24 (recorded) — Reel [verify]

   • Conveyance: Release of Security Interest in Patents
   • Assignor: BRIGHTWOOD LOAN SERVICES LLC
   • Assignee: KEMP TECHNOLOGIES INC.
   • Correspondent: [not in retrieved record — verify]
   • Context: lien release — closing out the 2019 collateral package.

Litigation milestone for cross-reference (not an assignment): first suit in the campaign, FireNet Technologies, LLC v. KEMP Technologies Inc., 1:18-cv-05564 (S.D.N.Y.), filed 2018-06-20; followed by Fujitsu (2:18-cv-00270, E.D. Tex., 2018-07-05), A10 Networks (3:18-cv-06502, N.D. Cal., 2018-10-24), Fortinet (4:19-cv-00798, N.D. Cal., 2019-02-14), Citrix (1:19-cv-03199, N.D. Ga., 2019-07-12). All four family patents asserted in each.

---

Timeline diagram

timeline
    title Ownership of US 8306994
    1998 : Priority application filed
    2001 : Parent patent 6317837 issued
    2010 : Continuation filed by Robust Networks
         : Patent 8306994 granted
    2015 : Merger into Mineral Lassen LLC
    2017 : IV Assets 57 acquires patent
    2018 : IQ Holdings takes title in January
         : Firenet Technologies takes title
         : First Firenet suit filed in June
    2020 : Unified Patents IPR on sibling 8892600
    2021 : Sibling claims cancelled on review

---

NPE / troll-pattern signals

1. Shell-entity transfer — PRESENT.
Concrete, not name-based: on 2015-11-18 an operating company (Robust Networks, LLC) is absorbed by Mineral Lassen LLC, whose only documented address of record is a suite-style Las Vegas address (2215-B Renaissance Drive, Suite 5, Las Vegas, NV 89119). Title then moves through IV Assets 57 LLC (2017-09-26) and IQ Holdings, LLC (2018-01-19) to Firenet Technologies, LLC (2018-04-13). Firenet's own Rule 7.1 disclosure describes it as an affiliate of Intelleq Holdings, LLC (a licensing vehicle), and RPX identifies Firenet as "an affiliate of Georgia-based IP Investments Group LLC (d/b/a IPinvestments Group), a monetization firm." No products in commerce.

2. Known asserter in the chain — PRESENT.
Intellectual Ventures Assets 57 LLC sits squarely in the chain (2017-09-26 transfer). IV is on the enumerated asserter list. Corroboration: Firenet's N.D. Cal. Certificate of Interested Entities (Filed 2019-02-21, Doc. 8, Dkt. 4:19-cv-00798) names Invention Investment Fund I, LP, Invention Investment Fund II, LLC, Intellectual Ventures Assets 54, LLC and Intellectual Ventures Assets 57, LLC as interested parties. Firenet Technologies, LLC also appears as a high-frequency plaintiff in Unified Patents' dockets (IPR2020-00471) and RPX's campaign write-ups.

3. Repeat correspondent across the chain — UNCLEAR (undeterminable).
The Assignment Center correspondent of record is not exposed in the retrieved data, so I cannot call recurrence on the recording side. Separately, and distinct from signal 3's definition: the same litigation counsel recurs across every assertion — Dmitry Kheyfits, Andrey Belenky and Hanna Glomska Cohen of Kheyfits Belenky LLP appear for Firenet in the KEMP, Fujitsu, A10, Fortinet and Citrix suits, with Daniel Arthur Kent (Kent & Risley, LLC) added in Georgia. This is corroborating evidence of a single coordinated campaign, but it is not the assignment-record correspondent and I am not scoring it as such.

4. Cascading transfers — PRESENT.
Four consecutive recorded transfers in 29 months: 2015-11-18 → 2017-09-26 → 2018-01-19 → 2018-04-13. The three fastest hops (IV Assets 57 → IQ Holdings → Firenet) all occurred inside under seven months.

5. Pre-litigation transfer — PRESENT.
Deed to Firenet Technologies, LLC recorded 2018-04-13; first complaint filed 2018-06-20 (FireNet v. KEMP, 1:18-cv-05564). That is 68 days — well inside the 6-month window, and consistent with arranging clean standing immediately before assertion.

6. Bankruptcy fire-sale — NOT PRESENT.
No Chapter 7/11 proceeding, §363 sale, or bankruptcy docket was found for Applianceware, Opticaute, Robust Networks or Mineral Lassen. The 2015 transfer was recorded as a merger, not a bankruptcy disposition.

7. Privateering — PRESENT.
The operating-company → NPE pipeline runs through IV and out to a contested-fee asserter, with IV retaining a disclosed economic interest. Firenet's corporate disclosures list Invention Investment Fund I LP and Invention Investment Fund II LLC — IV's investment funds — as affiliates. RPX describes the campaign flatly as one "in which IV retains an interest." This is the textbook privateering structure: IV parks the asset in an LLC, a monetization firm drives the suits, IV keeps a residual.

8. Defensive aggregator (anti-NPE) — NOT PRESENT (but note the inverse event).
The chain terminates at an asserting entity, not at RPX/AST/LOT/Unified/OIN. However, Unified Patents, LLC v. Firenet Technologies, LLC, IPR2020-00471 challenged the sibling US 8,892,600; the IPR certificate of 2021-10-12 cancelled claims 1–17 and 19–23 of that sibling (Ex Parte Analytics summary). That neutralized a sibling, not this patent's chain — and note this patent was already expired 2018-12-22 by then.

---

Verdict

NPE — high confidence

Three strong signals, each anchored in a dated record rather than a naming convention: (i) a 2018-04-13 assignment into Firenet Technologies, LLC followed by the first suit 68 days later on 2018-06-20 (FireNet v. KEMP, 1:18-cv-05564) — pre-litigation transfer; (ii) a four-link cascade — Robust Networks LLC → Mineral Lassen LLC (2015-11-18) → Intellectual Ventures Assets 57 LLC (2017-09-26) → IQ Holdings, LLC (2018-01-19) → Firenet (2018-04-13) — putting a named asserter (IV) in the chain; and (iii) privateering, evidenced by Firenet's own court filings naming Invention Investment Fund I LP, Invention Investment Fund II LLC and IV Assets 57 LLC as interested parties, with RPX describing the campaign as one "in which IV retains an interest." No product embodying the claims has been identified at any point in the chain. One reservation: the deal documentation that would be most probative here — reel/frame numbers and the recording correspondent — was not available in the retrieved record and should be pulled from the Assignment Center before this memo is relied on.

Verification links

• USPTO Patent Assignment Search: https://assignmentcenter.uspto.gov/ (search 8306994) · mirror: https://assignment.uspto.gov/patent/index.html
• Google Patents legal events + litigation family: https://patents.google.com/patent/US8306994/en
• FireNet v. KEMP (1:18-cv-05564, S.D.N.Y.): https://unicourt.com/case/pc-db1-firenet-technologies-llc-v-kemp-technologies-inc-[789691](/patent/789691)
• FireNet v. Citrix (1:19-cv-03199, N.D. Ga.): https://www.pacermonitor.com/public/case/29106238/FireNet_Technologies,_LLC_v_Citrix_Systems,_Inc
• FireNet v. Fortinet (4:19-cv-00798, N.D. Cal.): https://dockets.justia.com/docket/california/candce/4:2019cv00798/[338325](/patent/338325)
• RPX campaign coverage: https://insight.rpxcorp.com/news/details?searchq=ents%3A%28369352%29
• Unified Patents IPR2020-00471: https://services.patexia.com/lawsuits/Unified-Patents-LLC-v-Firenet-Technologies-LLC-id-[133475](/patent/133475)/documents

---

Two integrity notes on this data

1. Don't read the KEMP collateral entries as ownership. The 2019-04-05 Security Agreement (KEMP → Brightwood Loan Services) and the 2022-01-24 Release are lien instruments recorded against a KEMP-side portfolio. They do not evidence KEMP taking title to the '994 patent, and Google Patents' attachment of those events to this patent is unexplained in the retrieved data. Marked unresolved above.
2. Expiration timing matters for any damages narrative. The patent's adjusted expiration is 2018-12-22, i.e. between the Fortinet filing and the Citrix filing, and roughly 30 months before the IPR on the sibling concluded. Any assertion activity after that date runs into a lapsed-term problem. I state this as a record fact, not a legal conclusion — I'm not rendering a validity or damages opinion here.

I'll research the specific prior art references cited against US 8,306,994. Let me run targeted searches.

Scope note (read first)

I searched for the identifier 8306994 specifically. The results resolve to US 8,306,994 B2 and its published application US 2010/0242098 A1. I did not find any separate USPTO record keyed to a different number that could cause a collision, so the analysis below is anchored to US 8,306,994 B2 only.

Two framing points before the list:

1. The authoritative source used here is the full patent text you supplied (front-page "References Cited" / "Patent Citations" lists), supplemented by search hits for the individual references. I could not open the USPTO PatentCenter file wrapper or the examiner's form PTO-892 directly through search; where I describe a reference's substance I say whether I verified it (via that reference's own text) or am summarizing from its title.
2. § 102 vs. § 103 caveat. A front-page citation list is not an anticipation finding. Under 35 U.S.C. § 102, a single reference must disclose every element of a claim. Most of these references were cited as background or as § 103 art. Below I flag which few are genuinely close to § 102 anticipation of independent claims 1, 10, or 17, and which are realistically only § 103/background.

Family self-citations are NOT prior art: US 6,317,837 B1; US 7,739,302 B2; and US 8,892,600 B2 share the Sep. 1, 1998 priority date and are the patent's own ancestors/descendants. They cannot anticipate or render obvious the '994 claims. Likewise, the "Cited By" list (Centripetal, KEMP-era art, etc.) is later art and is not prior art to a 1998-priority patent.

---

A. The references that are genuinely close to § 102 anticipation

These are the examiner-cited references whose disclosed subject matter most nearly maps onto independent claims 1/10/17 — a NAD server with an integrated firewall that filters an access-request packet on header information (IP address, interface, port) and, if authorized, processes the packet to reach the attached device.

1. US 5,826,014 A — Firewall system for protecting network elements connected to a public network

• Assignee/inventor: Network Engineering Software; Coley et al.
• Filed: Feb. 6, 1996 · Issued/Published: Oct. 20, 1998
• Brief description (verified from the reference): A "firewall box" that is a stand-alone computing platform dedicated to a firewall application. Proxy agents (assigned by port number) verify an incoming access request — checking protocol-vs-port match, source address (validity, range, allow/deny list), user/password, and time-of-day — then initiate a connection to the protected network element on behalf of an authorized request. Unauthorized requests are discarded.
• Potential § 102 relevance: This is the strongest single-reference candidate against claim 1 (filtering an access request for a protected "network element" on header data — port and source address — and only then initiating a connection to the element) and against claim 10 (authorize/deny by filtering; enable access if authorized, block otherwise). Its weakness versus the '994 claims is that the firewall is a stand-alone box rather than "integrated into the NAD server," and the claim language ties filtering to "an IP address in a header." Expect this to be asserted as § 102/§ 103 art rather than a clean anticipation.

2. US 5,623,601 A — Apparatus and method for providing a secure gateway for communication and data exchanges between networks

• Inventor: Vu · Issued: Apr. 22, 1997
• Brief description: A secure gateway (Milkway Networks) that screens inbound/outbound communications between networks before permitting data exchange, i.e., a filtering/proxy gateway sitting in the path to resources on the protected side.
• Potential § 102 relevance: Background/§ 103 against the "determining whether the request … is authorized" and "denying otherwise" limitations of claims 1 and 10. Not a clean § 102 read because it does not tie the filtering to a NAD server that "controls access to and from the NAD" attached to it.

3. US 5,778,174 A — Method and system for providing secured access to a server connected to a private computer network

• Inventor: Cain · Issued: Jul. 7, 1998
• Brief description: Secured-remote-access scheme for a server on a private network — authenticating/filtering access to a server rather than to an entire perimeter.
• Potential § 102 relevance: § 103 art against claim 1's "NAD server … controls access to and from the NAD" and the authorize/deny step. Its "server-through-a-secure-gateway" framing is the closest structural analog to the NAD-server-with-integrated-firewall idea among the 1996–1998 art.

4. GB 2 318 031 A — Network firewall with proxy (Secure Computing Corp.)

• Published: Apr. 8, 1998 (priority Sep. 13, 1996)
• Brief description: Firewall that proxies and screens network traffic to protected interior resources.
• Potential § 102 relevance: Claim 7 / claim 14 / claim 21 (proxy behavior: establishing a link and sending a generated packet onward). The proxy mechanics overlap the '994's proxy-NAD-server embodiment (FIG. 7). § 103 background for claims 1/10/17.

5. WO 1998/022866 A1 — CD-ROM interface (Surfvision)

• Published: May 28, 1998 (priority Nov. 22, 1996)
• Brief description: A network interface for CD-ROM media — directly on point for the '994's disclosed "NAD" (CD-ROM tower / optical drive) and the interface-mechanism concept of claims 5 and 6.
• Potential § 102 relevance: Its importance is subject-matter proximity (network-attached optical drive + interface), not a full claim read. Combined with a firewall reference it is § 103 art for claims 5/6 and the NAD definition.

---

B. Remaining US references cited on the '994 front page

Descriptions below are condensed from title + known subject matter (I verified item 1 above in full; the rest are summarized, not individually full-text-verified). None of these, standing alone, discloses the combination of an integrated firewall at a NAD server plus NAD-access processing of an authorized packet, so they are best characterized as § 103 / background art aimed mainly at dependent claims.

---

C. Foreign / international references cited

---

D. Non-patent literature cited

• Gobioff, Howard et al., "Security for Network Attached Storage" — cited on the '994 front page. This is a network-attached-storage security paper and is the most directly on-point NPL for the "NAD with dedicated security" framing of claims 1/10/17. I did not verify its exact publication venue/date from search; flag it as worth pulling from the file wrapper.

---

E. Bottom line for § 102 purposes

• Best § 102 candidate against claim 1 (and derivatively 10): US 5,826,014 A (Coley et al.) — a dedicated firewall platform with per-port proxy agents that verify source address and only then open a connection to the protected element. Its principal gap relative to the '994 claims is the integration locus (stand-alone firewall box vs. "NAD server configured to … process the data packet for communication with the NAD").
• Best § 102/§ 103 art for the proxy limitations (claims 7, 14, 21): GB 2 318 031 A, WO 1998/031124 A1, US 6,349,336 B1.
• Best § 103 art for the "NAD = CD-ROM/optical/storage + interface mechanism" limitations (claims 5, 6): WO 1998/022866 A1, US 5,642,337 A (Sony), US 6,047,353 A (EMC).
• The remaining ~40 US references are background/§ 103 art directed at firewalls, proxies, authentication, and storage generally; none appears to disclose, in one reference, an integrated NAD-server firewall that filters on an IP header and then processes the packet to the attached device.

---

F. Items I could not verify (stated as absence of information, not findings)

1. I could not open the USPTO PatentCenter file wrapper for 12/773,716 to confirm which references the examiner actually applied versus merely listed, nor to retrieve any PTO-892/PTOL-303. The list above is the front-page citation list from the authoritative text you supplied, plus reference-level search hits.
2. I did not independently pull the full text of most Table B references; their descriptions are title/known-subject summaries, not verified disclosures. The § 102/§ 103 characterizations are analytic, not examiner findings.
3. Publication dates for the foreign and NPL items come from the citation list/search results; the two EP 2004 entries post-date the 1998 priority and therefore are not prior art — I flag them so they are not mistakenly relied on.
4. No IPR/PGR or reexamination certificate specifically applying the § 102 art above to the '994 patent surfaced; the one family IPR I am aware of (IPR2020-00471) targeted sibling US 8,892,600, not the '994.

Grounding sources: authoritative full text for US 8,306,994 B2 (patents.google.com/patent/US8306994/en); granted-PDF front page at patentimages.storage.googleapis.com (US8306994.pdf); the '994 published application US 2010/0242098 A1 (uspto.report/patent/app/20100242098); full text of US 5,826,014 A (patents.google.com/patent/US5826014A); citation list of US 6,182,141 B1 (patents.google.com/patent/US6182141B1); and the family ancestor US 6,317,837 B1 (patentimages.storage.googleapis.com/.../US6317837.pdf).

I'll research the key prior-art references cited on this patent's page before building the § 103 analysis.

Now let me verify the device-server and access-control references.

Obviousness Analysis — US 8,306,994 B2 under 35 U.S.C. § 103

Reference basis: The prior art analyzed below is drawn from the "Prior Art" section of the US8306994B2 page as supplied — specifically the Citations (62) table, the overlapping Patent Citations (64) table, the Family Cites Families (4) table, and the Families Citing this family (76) table. I note up front that the supplied page text is truncated mid-way through the "Patent Citations (64)" table (it ends at "US6009475A … 1996-12-23 … Int"), so my enumeration is drawn from the complete "Citations (62)" table plus the portion of the "Patent Citations (64)" table that rendered.

Caveat on verification depth. The page itself supplies only publication number / priority date / grant date / assignee / title for most references. I separately retrieved and verified the actual claim and description text of US 5,826,014, US 5,623,601, US 5,960,177, GB 2 318 031 A, and US 5,642,337. For the remaining references I have title-, date-, and assignee-level information only and I say so explicitly rather than attribute disclosures to them. I also rely on the third-party Limestone validity ranking run against sibling US 7,739,302 B2 (same specification, same 1998-09-01 priority), which flagged several references that also appear in the '994's own citation list. That ranking is a machine-generated relevance score, not an examiner or court determination, and I treat it only as corroboration that the art was crowded.

---

1. Governing law and the critical date problem

US 8,306,994 issued from application 12/773,716, filed 2010-05-04, as a continuation of 09/951,877 (now US 7,739,302), itself a continuation of 09/144,954 (now US 6,317,837), filed 1998-09-01. All four family members share the 1998-09-01 priority date.

• The application was filed before 2013-03-16 and claims an effective filing date before that date, so pre-AIA §§ 102 and 103 govern. KSR still controls the obviousness standard.
• The controlling date for prior-art qualification is therefore 1998-09-01 (assuming, as the face of the patent indicates, that the '994 claims are supported by the 1998-09-01 disclosure — the litigation record supplies no contrary holding).

This date qualification matters enormously here, and it cuts in two directions the reader should keep in view:

The most important line in that table is the first one: US 5,826,014 is squarely available as § 102(e) art even though it issued seven weeks after the '994's priority date. The patentee could theoretically attempt to swear behind it under 37 CFR 1.131, but there is no evidence in the record of a Rule 131 affidavit, and the reference is "by another" (Coley/Wesinger vs. Kenworthy), so the § 102(e) requirement is satisfied.

---

2. Level of ordinary skill in the art

A person having ordinary skill in this art as of September 1998 would have: (a) a bachelor's degree in computer science, computer engineering, or electrical engineering, or equivalent experience; and (b) two to three years of practical experience designing or administering TCP/IP networks, perimeter firewalls, and LAN file/print/peripheral servers. That person would have been conversant with: packet filtering (source/destination address, port, protocol, and interface checks); application-level and proxy gateways; bastion hosts and dual-homed gateways; TCP/IP header structure; SCSI attachment of peripherals; and the then-standard multi-protocol LAN environment (Appletalk, Netware, TCP/IP) the '994 specification itself describes.

I note the specification strongly supports this level of skill: it describes packet-filtering firewalls, proxy firewalls, and bastion firewalls as ordinary, pre-existing technology ("Bastion firewalls are typically the only layer of security for NADs attached to a LAN"), and describes SCSI-based NAD servers as conventional ("NAD servers are generally dedicated servers, meaning that their sole purpose is to provide access to NADs").

---

3. The invention reduced to its constituent elements

Reading independent claims 1, 10, and 17 together, the claimed advance is a small set of well-known mechanisms in a particular arrangement:

Pivotal construction note. Claim 1 does not recite a "firewall" at all. Its gating limitation is only "filter the data packet to determine, based at least on an IP address in a header of the data packet, whether the received request … should be authorized." That is ordinary packet filtering — the specification itself concedes as much, describing a firewall's packet filter as one that "investigates address information contained in a data packet." "At least based on an IP address" is a floor, not a ceiling; it does not exclude additional port, interface, or protocol checks (indeed, claim 8 recites them). The construction therefore matters: claim 1 is broad, and the narrower scope a challenger must defeat lies principally in the "dedicated to the NAD/NAD server" placement of claim 1's preamble and in the express "NAD server firewall" of claims 10 and 17.

---

4. The principal prior-art references

4.1 US 5,826,014 — Network Engineering Software (Coley & Wesinger) — primary reference

This is the single most damaging reference, and it is expressly cited on the face of the '994 patent. Verified text establishes:

• Firewall dedicated to a network element, not a perimeter. Abstract: "A firewall for isolating network elements from a publicly accessible network to which such network elements are attached. The firewall operates on a stand alone computer connected between the public network and the network elements to be protected such that all access to the protected network elements must go through the firewall." Specification: "The firewall box is connected to a protected network element by a single connection. Consequently, any communication from a publicly accessible network element to a protected network element must pass through the firewall box."
• The protected element is a device on the network. The specification defines "network element" as "network routers, computers, servers, databases, hosts, modems, or like devices that are typically associated with a computer network."
• Explicit IP-address filtering. "One technique used by firewalls to protect network elements is known as 'packet filtering.' A packet filter investigates address information contained in a data packet to determine whether the packet machine, from which the packet originated, is on a list of disallowed addresses. If the address is on the list, the packet is not allowed to pass." And: "the packet filter maintains a list of addresses corresponding to network elements residing behind the firewall. If any incoming access request has a source address of a network element behind the firewall, that packet will be intercepted and discarded."
• Authorize-then-process-then-deny-otherwise. "The assigned proxy agent immediately verifies the access request before a connection is formed… If the access request is authorized, the assigned proxy agent opens, and thereafter manages, the port connection." The claims recite "verifying that an access request packet received over the first connection is authorized to access the network element, the at least one proxy agent initiating a connection to the network element on behalf of the access request if the access request is authorized."
• Multi-directional / "to and from" control. "a firewall in accordance with the present invention also can be utilized to monitor and control packet traffic originating from behind a firewall, allowing and disallowing connection based upon predetermined rules… what, where, who, how and when a user behind the firewall can access the outside world."
• Port and protocol checks. Proxy agents are assigned per port; "if the protocol of an access request is not configured in accordance with the protocol normally associated with that port, the request is discarded." Continuation US 6,061,798 claim 1 recites "initializing a plurality of proxy agents, wherein each of said proxy agents is assigned a corresponding port number and protocol; verifying that incoming connection requests are formatted in accordance with said corresponding protocol."
• Logging. A transaction log recording source address, destination address, time, and user identity.
• Computer-readable-medium embodiment. "the invention can be embodied in the form of an article of manufacture as a machine readable medium such as floppy disk, computer tape, hard drive disk, CD ROM, RAM, or any other suitable memory medium."

In short, US 5,826,014 discloses E2–E6, E8 (proxy agent completing the connection on the element's behalf), E9, E10, and the medium claim format of E17 — everything except the specific framing of the protected element as a "network attached device" (CD-ROM tower, printer, video codec) and the SCSI interface to it.

4.2 US 5,642,337 — Sony, "Network with optical mass storage devices"

Verified text establishes exactly the NAD-server architecture:

• "In such a system, the jukebox would be coupled to a local computer which receives requests for data from a user at the computer or from remote clients over a network."
• Claim 7: "the computer receives the requests from a client over a communication channel and returns the responsive data to the client over the communication channel."
• Claim 8: "means for decoding network protocol encoded SCSI commands received over the network and sending them to the SCSI controller of the slave interface unit for transmission to the SCSI controller of the slave jukebox."
• Claim 9: "means for encoding the responsive data into data packets in accordance with the network protocol."
• The slaves are reached only through the master computer / slave interface units — the SCSI-attached storage device has no independent network presence.

That is E1, E2, E3, E4, and the interface-mechanism half of E6 — a server on a LAN through which all client requests to an attached optical-storage device are processed, with SCSI as the interface mechanism. It supplies precisely the "data manager component … interface mechanism such as … SCSI" of the '994 specification.

4.3 US 5,623,601 — Milkway Networks (Vu)

Verified text establishes:

• A gateway that "transparently imitates a host when a communication data packet is received from a client on one of the networks by initiating a communication session with the client. If the client is determined to have access rights to the requested service, the gateway station imitates the client to the host on the other network by initiating a communications session with the host."
• Explicit source/destination IP rule check — one of the drawing sheets is captioned "Is IP Source Permitted to Communicate With Dest?" and claim 11 checks "a table to determine if a custom proxy process is bound to the destination port number."
• Proxy two-session relaying (claim 19 and the first claim quoted) — directly on point for claim 7/14/21 of the '994.
• Authentication (user ID/password) and data sensitivity screening at the application layer.
• Bastion host / dual-homed gateway / screened-subnet configurations, and a modified kernel that cannot forward packets — "the apparatus in accordance with the invention is modeled on the concept of a bastion host, preferably configured as a dual home firewall."

4.4 GB 2 318 031 A — Secure Computing, "Network firewall with proxy"

Verified text: "all firewalls perform a function know[n] as 'relaying', where Protocol Data Units (PDUs) are received by the firewall from a sending application entity and forwarded to a receiving application entity… some information, or context, must be extracted from the PDUs and subjected to a set of rules. Based on the outcome of the rules check, the firewall performs an action; the PDU is either relayed, modified and relayed, or rejected." It also explains distinguishing services by destination TCP port, and the OSI layer at which a firewall acts as a protocol peer. This is a clean disclosure of E5, E6 (relay/reject), and E9 (proxy).

4.5 US 5,960,177 — Fujitsu (Tanno) — the "firewall integrated in the server/central unit" teaching

This reference is important because it supplies the specific structural point on which claims 10 and 17 might otherwise be defended: that the filtering function and the server function can reside in a single unit. Verified claim text:

• Claim 5: "A central unit which functions as a second firewall against access to a servicing unit via an external network … comprising: first packet communications means for setting up a first connection with said serviced unit …; security check means for determining whether or not packets received … are packets transmitted from a serviced unit of a contract user; and second packet communications means for, when the determination … is that said packets are packets from said serviced unit of a contract user, setting up a second connection with said servicing unit … and transmitting packets to or from said servicing unit."
• Claim 15: the second firewall "setting up a second connection with said servicing unit via said second internal network; and relaying packets between said serviced unit and said servicing unit using said first and second connections."
• The patent's own Figure 1 "packet filtering gateway feature of a firewall" and Figure 2 "IP address translation/relay feature" are described in the reference.
• The system is expressly a first firewall and a second firewall in series (claim 1: "a first firewall is installed for an external network and a serviced unit connected to a second internal network in which a second firewall is installed for said external network").

So US 5,960,177 discloses (i) a firewall function embodied inside a serving/central unit, (ii) two firewalls in series protecting a protected unit, and (iii) proxy-style relay between two connections. That directly maps to the '994's FIG. 7 (proxy NAD server) and FIG. 8 (NADFW-MS installed in the device) embodiments, and to dependent claims 2 and 16.

4.6 References available at title/date level only

I list these because they fill remaining gaps, but I attribute nothing to them beyond what their titles and the '994's own citations support:

• US 6,321,336 (Secure Computing, 1998-03-13) — "System and method for redirecting network traffic to provide secure communication." This is the #1-ranked reference in the third-party Limestone validity run against sibling US 7,739,302, and it appears in the '994's own citation list. I could not verify its disclosure and so do not build a combination on it alone.
• US 6,233,618 (Content Advisor, 1998-03-31) — "Access control of networked data." Title-level only; a plausible secondary reference for network access control.
• US 5,757,924 (Digital Secured Networks Technologies, 1995-09-18) — "Network security device which performs MAC address translation without affecting the IP address." Title-level only; relevant, if at all, to claim 22's interface-based filtering.
• US 5,991,807 (Nortel, 1996-06-24) — "System for controlling users access to a distributive network in accordance with constraints present in common access distributive network interface separate from a server." Title-level only; the "interface separate from a server" phrasing is interesting but I will not over-read it.
• US 6,009,475 (IBM, 1996-12-23) — "Filter rule validation and administration for firewalls." Title-level only.
• US 5,996,077 (Cylink, 1997-06-16) — "Access control system and method using hierarchical arrangement of security devices." Title-level only.
• US 6,041,755 (NSA, 1998-04-13) — "Firewall security apparatus for high-speed circuit switched networks." Title-level only.
• US 5,247,670 (Fuji Xerox, 1988-03-16) — "Network server." Title-level only, but the title alone shows that networked server access to shared resources was a 1980s-era concept.
• USH1944 H1 (Lucent, 1998-03-24) — "Firewall security method and apparatus," a statutory invention registration cited in the family's "Family Cites Families" table.
• US 5,719,786 (Novell, 1993-02-03) — "Digital media data stream network management system," cited on the '994 page.
• US 5,852,717 (Shiva, 1996-11-20) — "Performance optimizations for computer networks utilizing HTTP."
• KR 100528156 B1 (Nomadix, 1997-03-12) — "Nomadic Translator or Router," the only pre-1998-09-01 entry in the "Families Citing this family" table.

Excluded from the prior-art case: the parent US 6,317,837 B1 and sibling US 7,739,302 B2 / US 8,892,600 B2 are the same family and the same disclosure; they are not available as prior art against the '994's claims. I flag this because the '994 was used as Exhibit 1011 in IPR2020-00471 (against sibling US 8,892,600), which is anomalous given the shared priority date; I could not resolve that anomaly and noted it in the earlier section as unresolved.

---

5. The combinations

Combination 1 (lead): US 5,826,014 in view of US 5,642,337

Mapping to independent claim 1:

Every element of claim 1 is accounted for. The combination is a pairing of two references in the same field of endeavor (LAN client/server resource access) with no conflict in structure or operation.

Motivation to combine — why a PHOSITA would have done this, grounded in the references themselves:

1. US 5,826,014 explicitly teaches that its protected "network element" may be a server or a device ("network routers, computers, servers, databases, hosts, modems, or like devices"). A jukebox/optical-storage server of the kind in US 5,642,337 is squarely within that list.
2. US 5,826,014 expressly disparages perimeter-only protection and preaches firewalling each element: it identifies the flank-attack/bypass vulnerability of a firewall "grafted onto an existing computing system," and its stated object is a firewall that "physically resides between a point of public access and a network element to be protected." A skilled artisan seeking to secure the Sony server would apply the Coley firewall to it.
3. The '994 specification concedes the gap was recognized: "Bastion firewalls are typically the only layer of security for NADs attached to a LAN… once a bastion firewall is penetrated … the user typically gains unrestricted access to all resources of the LAN, including any NADs." That is a statement of the problem the artisan faced; US 5,826,014 supplies the known solution.
4. Predictable result. Placing a known packet-filtering/proxy firewall in the pre-existing request path of a known device server does no more than what both references describe. Under KSR, "the combination of familiar elements according to known methods is likely to be obvious when it does no more than yield predictable results."

---

Combination 2: US 5,623,601 (Milkway) in view of US 5,642,337 (Sony)

Substitutes or supplements the primary reference. US 5,623,601 supplies the IP source/destination rule check ("Is IP Source Permitted to Communicate With Dest?"), the two-session proxy relay that maps directly to the '994's FIG. 7, transparent user access, and the bastion-host/dual-homed architecture. US 5,642,337 supplies the device-server. The motivation is the same: Milkway's own background explains that a perimeter firewall fails to protect against internal/back-door access and that the gateway must sit at the boundary of what is protected; the Sony server is the natural boundary for the jukebox.

This combination is especially strong for the method claim 10, whose only affirmative steps are (i) processing a request packet, (ii) the firewall deciding authorize/deny "based on a filtering of at least the IP header," and (iii) enabling or blocking access.

---

Combination 3: US 5,960,177 (Fujitsu) in view of US 5,826,014 and/or US 5,623,601

This combination defeats the strongest potential defense — that the prior-art firewalls were separate boxes, whereas claims 10 and 17 require "the NAD server compris[ing] a NAD server firewall."

US 5,960,177 claim 5 recites "A central unit which functions as a second firewall," and claim 15 has that second firewall "setting up a second connection with said servicing unit via said second internal network; and relaying packets between said serviced unit and said servicing unit." That is a firewall function co-located with the serving unit, performing authorize-then-relay — i.e., the '994's NADFW-MS. US 5,960,177 claim 1 further describes two firewalls in series (first firewall for the external network, second firewall for the serviced unit), which is claim 2 and claim 16 of the '994 almost verbatim.

Motivation: Fujitsu's stated problem is that a protected unit behind a perimeter firewall cannot securely distinguish authorized from unauthorized remote traffic; the solution is to give the protected side its own filtering/relay function. That is precisely the "second layer of security" the '994 claims as its invention — and the '994 spec's own framing ("the present invention provides a NAD with a second layer of firewall security, over and above that which may be provided by a bastion firewall") is a concession that the purpose was recognized in the art.

---

Combination 4: US 6,321,336 (Secure Computing) as an alternative primary reference

Listed here for completeness only. Its 1998-03-13 filing date makes it § 102(e) art, its subject matter ("redirecting network traffic to provide secure communication") is in the same field, and an independent third-party model ranked it first against the '994's sibling with the identical specification. I could not verify its disclosure, so I do not rely on it as a primary reference and flag it as an item warranting file-wrapper/inspection verification.

---

6. Dependent claims

Note that claims 6 and 13 recite "one or more interface components" filtering logic that is grammatically tangled in the granted text ("one or more interface components is configured to receive…"). I leave the claim as issued and do not normalize it. Claims 11, 12, 18, 19 appear to carry a dependency error — claim 18 depends from claim 17 and refers to "the NAD server firewall" although claim 17 introduces the firewall only in the body of its "authorizing" step; this is the same antecedent-basis artifact flagged in the earlier section for claim 17 itself.

---

7. KSR motivation-to-combine factors

Beyond the reference-specific motivations above, four KSR rationales apply across the board:

1. Known technique, known problem. Dedicated per-element firewalls (US 5,826,014), proxy gateways (US 5,623,601; GB 2 318 031 A), and device-controlling servers (US 5,642,337) were all known; the '994 simply relocated known filtering into a known server. KSR: "a patent composed of several elements is not proved obvious merely by demonstrating that each of its elements was, independently, known in the prior art" — but here the arrangement is also suggested, because US 5,826,014 discloses firewalling each network element rather than the perimeter.
2. Design incentive / market pressure. The references themselves (US 5,826,014's discussion of flank attacks and shared platforms; US 5,623,601's discussion of internal back doors; US 5,960,177's discussion of perimeter firewalls being unable to identify packet sources) demonstrate that the field was actively pursuing protection inside the perimeter as of 1995–1998.
3. Predictable results. No reference teaches away from combining a firewall with a device server; the result — a filter that gates a device request — is the very result each reference describes.
4. "Obvious to try." Where the problem is protecting a valuable device from both internal and external users, and the art offers several well-known filter placements, the '994's placement is one of a small number of identified, predictable solutions.

---

8. Counterarguments a patentee would raise, and how they fare

1. "The examiner considered all of these references and still allowed the claims." True and material: the '994's front page lists 62–64 cited references, and the independent claims issued over them. Some weight attaches to examiner allowance (MPEP 716.01(c) cautions that it is not conclusive). The countervailing point is that the strongest § 102(e) reference — US 5,826,014 — issued after the critical date, which is exactly the kind of art that is easily missed; and the "Cited By"/"Families Citing" tables are largely post-1998 and thus irrelevant. The "Prior Art" section thus understates the 1998-era art available from the same field (e.g., the Limestone run surfaced EP 0895684 (Northern Telecom, "Internet protocol filter," 1996-04-24), EP 0743777 (Sun, packet filtering at a network interface, 1995-05-18), US 5,606,668 (Check Point, 1993-12-15), US 5,898,784 (Raptor, 1996-01-16), and US 6,321,336).
2. "No single reference discloses the whole claim." Correct, which is why the combinations are required — but the § 103 case does not require a single reference, and the references are all in the same field with directly stated reasons to combine.
3. "The NAD is a special class of device not contemplated by the art." Weak. The '994's own specification concedes NADs are a subset of network-attached hardware, and US 5,826,014's "network element" definition expressly extends to "servers … and like devices," while US 5,642,337 discloses an optical-storage device server.
4. "The firewall must be dedicated to the NAD." This is the best defense, and it is met head-on by US 5,826,014's single-connection, firewall-per-element architecture and by US 5,960,177's "central unit which functions as a second firewall."
5. "Claim 17's 'non-transitory' limitation." This is a § 101 recital, not a technical distinction; US 5,826,014 expressly discloses media embodiments.

---

9. Secondary considerations

I found no objective evidence of non-obviousness in the materials available: no evidence of unexpected results, no evidence of copying, no licensing program evidence of nexus, and no evidence of a long-felt-but-unmet need attributable to the claims as opposed to the commercial availability of the accused products. Two facts are worth noting neutrally:

• The family attracted five district-court suits (FireNet v. KEMP, Fujitsu, A10, Fortinet, Citrix) and an IPR against the sibling '600 (IPR2020-00471), which was terminated. Litigation alone proves nothing about validity.
• The '994 was submitted as Exhibit 1011 in IPR2020-00471 — i.e., as asserted prior art against its own sibling — which, if accurate, is an anomaly given the shared 1998 priority date and should be verified against the IPR record rather than read as a substantive finding.

---

10. Bottom line

The most probable § 103 rejection would be:

Claim 1 — obvious over US 5,826,014 in view of US 5,642,337.
Claim 10 — obvious over US 5,826,014 (or US 5,623,601) in view of US 5,642,337, further in view of US 5,960,177 for the co-located "central unit which functions as a second firewall."
Claims 2, 16 — as above, further in view of US 5,960,177 (first and second firewalls in series).
Claims 3, 4, 11, 12, 18, 19 — as above, further in view of US 6,061,798 (the continuation of US 5,826,014) claims 1 and the per-port/per-protocol proxy agent disclosure, and US 5,623,601.
Claims 5, 6, 13, 20 — as above, further in view of US 5,642,337 claims 8–9 (network-protocol-encoded SCSI interface to the device).
Claims 7, 14, 21 — as above, further in view of US 5,623,601, US 5,960,177 claim 15, and GB 2 318 031 A.
Claims 8, 9, 15, 22 — as above, further in view of US 5,826,014 (source-address lists, port/protocol assignment, tiered source-based verification) and US 5,623,601 (port binding, all-port listening, source/destination rule check).

The commercial and legal significance is that the '994's independent claims appear vulnerable on the merits to a well-constructed obviousness case built from references already cited on its own face — the § 102(e) status of US 5,826,014 (issued after the critical date) is the likely explanation for why such a combination did not crystallize during prosecution. That said, the patent expired 2018-12-22 and every asserted case appears closed or dormant, so this is an academic-validity conclusion rather than a live-invalidity conclusion.

Explicit limitations of this analysis:

1. I verified the operative disclosure of only five references (US 5,826,014, US 5,623,601, US 5,960,177, GB 2 318 031 A, US 5,642,337). All other references are characterized at title/date level only, and I have not asserted specific disclosures for them.
2. I have not inspected the file wrapper of 12/773,716 and therefore cannot confirm whether any of the combinations above were actually made of record and overcome, nor what arguments were presented.
3. I have not confirmed whether the '994's claims are entitled to the 1998-09-01 priority date as a matter of written description; if they were not, a different (later) critical date could remove some references from the prior art and would need reassessment.
4. Where the supplied page conflicts with anything I might recall about these documents, the supplied page governs, and I have interpreted all numbers literally — including the Fortinet docket-prefix discrepancy (3:19-cv-00798 vs. 4:19-cv-00798) and the "ROBUST NETWORKS LLC" / "Firenet Technologies LLC" assignee strings exactly as they appear.