US 7739302

I'll search for authoritative information on US 7,739,302 and any 2026 CAFC activity.

Let me check specifically for 2026 Federal Circuit activity and current docket status.

US Patent 7,739,302 — Analyst Summary

Sourcing note: The authoritative full text supplied in this task (Google Patents, https://patents.google.com/patent/US7739302/en, fetched 2026-09-12) is the primary basis for everything below. Supplementary searches returned the Google Patents record, FreePatentsOnline's record of the pre-grant publication, the child patent US 8,306,994, RPX/Insight records for the family, and a 2020 Unified Patents prior-art contest page.

---

1. Bibliographic data (as listed in the record)

Relation to parent: This application is a continuation of Ser. No. 09/144,954, filed Sep. 1, 1998, now US 6,317,837 ("Internal Network Node with Dedicated Firewall").

Assignment chain (per the record): Applianceware, Inc. → Optifacio, Inc. (2002) → Opticaute, Inc. (2004/2006) → Robust Networks, LLC (2007) → Mineral Lassen LLC (2015) → Intellectual Ventures Assets 57 LLC (2017) → IQ Holdings, LLC (2018) → Firenet Technologies, LLC (2018). A separate Brightwood Loan Services collateral-agent security interest naming KEMP Technologies Inc. appears (2019), released in 2022.

---

2. 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."

---

3. Plain-language overview of each independent claim

There are five independent claims (1, 5, 10, 12, 22). The remaining 25 claims are dependent. Claim text below is paraphrased for readability; where the granted language is awkward or ambiguous, I flag it.

Claim 1 — Network arrangement with an in-path NAD server.
A network holds a client and at least one network attached device (NAD). A NAD server sits between them. The server receives a data packet containing a request for access to the NAD. Its stored instructions cause it to (a) check whether the packet header includes at least one of an IP source address, an IP destination address, or a route; (b) filter the packet based at least on an IP address in the header; (c) decide whether the access request is authorized; and (d) grant access only if authorized — so the NAD is protected from unauthorized requests in addition to any firewall protection.
Drafting note (literal): the phrase "the NAD being further configured to filter the data packet based at least on an IP address in a header" is embedded inside the NAD-server claim, which reads as a drafting artifact. I have reproduced it as written rather than "correcting" it.

Claim 5 — LAN arrangement with the firewall inside the NAD.
A LAN has a client and a NAD. The NAD itself contains (i) a data management component and (ii) an internal firewall management component. That internal component judges, for each request and independently of any firewall external to the NAD, whether access is authorized. Authorization is decided by filtering on IP addresses in the packet header, and requires the header to contain information relating to network source, destination, and route. The data management component grants access only on authorization. Critically, "at least some of the plurality of requests originate from within the network without passing through the [external] firewall" — i.e., the claim is expressly directed at internal threat traffic that a perimeter firewall never sees.

Claim 10 — System for managing access from outside a network running a bastion firewall (means-plus-function).
A system for managing outside access to a NAD on a network protected by a bastion firewall, comprising: means for receiving a request and determining whether it should be authorized (by checking the header for at least one of source IP, destination IP, route; filtering at least on a header IP address); and means for granting access when authorized and denying when unauthorized. The request may originate inside or outside the network, and at least one request has passed into the network through a firewall.
Dependent claim 11 adds that access is available only through a server coupled to the NAD.

Claim 12 — Apparatus (machine/device) claim.
An apparatus with a processing unit, a network interface, an attached-device interface providing a communication path to a directly attached device, and memory storing instructions that: decide whether requests from the network interface should be authorized or unauthorized; check the header for at least one of source IP, destination IP, route (filtering at least on a header IP address); deny unauthorized requests; allow authorized ones; requests may originate inside or outside the network, and at least one has passed through a firewall.
Notable dependents: 15 (selectively generate a new packet to an intermediary computing device — proxy behavior); 17 (deny/allow performed at an application layer); 20 (directly attached device interface comprises a SCSI interface); 18/19 (heterogeneous network protocols, one being TCP/IP).

Claim 22 — Apparatus (means-plus-function).
An apparatus with: means for receiving network requests for access to a NAD (requests may be internal or external; at least one passed into the network through a firewall); means for filtering each request to prevent unauthorized access, by examining the packet header to determine whether it includes at least one of source IP, destination IP, or route, and filtering based at least on a header IP address; and means for allowing access for requests the filter deems authorized — such that the NAD is protected in addition to any firewall protection.
Notable dependents: 23/24 (means for managing access over a device interface / SCSI interface); 25 (selectively generating a new packet to another device — proxy); 26 (logging each allowed request); 28 (filtering performed at an application layer of the network stack).

Common technical thread across independent claims: header-based packet filtering (IP source/destination/route) performed by a firewall dedicated to a NAD or its server, layered on top of — and in some claims exercised independently of — a perimeter/bastion firewall.

Specification support: the disclosure's FIG. 6 filtering sequence (header completeness → authorized network interface → valid source/destination addresses → correct port) and the FIG. 7 proxy embodiment, plus FIG. 8's per-NAD embedded NADFW-MS, map onto these claim families.

---

4. Litigation and enforcement posture

The Google Patents record lists these litigations (all pre-2026):

• N.D. Georgia, No. 1:19-cv-03199
• E.D. Texas, No. 2:18-cv-00270
• N.D. California, No. 3:18-cv-06502
• S.D. New York, No. 1:18-cv-05564
• N.D. California, No. 3:19-cv-00798

A 2020 Unified Patents patroll prior-art contest for US 7,739,302 ("Proxy firewall for Protecting Devices on a Network," $2,500 prize) states that the patent was asserted against Kemp Technologies, Fortinet, Citrix, A10 Networks, and Fujitsu (https://patroll.unifiedpatents.com/contests/3c5LNHXhhC639WoA6). A Limestone validity report also exists for the patent.

---

5. CAFC 2026 docket search — explicit uncertainty

I could not confirm any 2026 Court of Appeals for the Federal Circuit docket involving US 7,739,302. Searches for "Firenet Technologies" + Federal Circuit 2026, and for "7,739,302" / "7739302" + Federal Circuit appeal, returned no results.

I am stating this as a negative finding, not a verified absence — CAFC docket data is not fully indexed by the search tools available to me, and a docket could exist that I cannot retrieve. Two contextual observations bear on plausibility, however:

1. The record lists the patent as "Expired – Fee Related," with an adjusted expiration of 2020-05-29, i.e., the patent term is over.
2. The only litigations listed are from 2018–2019 district court cases, with no listed appeal.

Given (1) and (2), a 2026 Federal Circuit appeal on this patent would be unusual, though not impossible (e.g., a long-running appeal or a collateral fee/standing dispute). Anyone needing certainty should query the CAFC's own docket system (PACER/CM-ECF) and the USPTO PatentCenter record for application 09/951,877 directly.

---

6. Data caveats

• Claim count discrepancy: the pre-grant publication US 2002/0049899 A1 carried 45 claims; the granted patent carries 30. The granted text is controlling.
• Assignee field: Google Patents lists "Original Assignee: Individual," while assignment records show Applianceware, Inc.; Google's own disclaimer notes listed assignees "may be inaccurate." Treat the assignment chain above as record-derived, not adjudicated.
• Claim 1 and claim 11 language contains grammatical anomalies in the published text (noted above). I have preserved the literal wording rather than auto-correcting it, per the operating rules.
• All bibliographic values above are transcribed literally from the authoritative record; where the record itself is ambiguous, I have said so rather than resolving it.

I'll search for litigation involving US 7,739,302 specifically.

Let me search the Unified Patents litigation caselist directly and verify each listed case.

Let me pull the Unified Patents litigation caselist for this patent and check each case's patent assertions.

I hit the tool-call ceiling before I could retrieve the Unified Patents portal caselist page directly (the patents=7739302 filter URL). Here is everything I can ground, with verification status flagged per field.

---

Litigation Involving US Patent 7,739,302

Bottom line

Litigation is known. US 7,739,302 was asserted as part of a four-patent network-security portfolio by FireNet Technologies, LLC — per Unified Patents, "an NPE and entity of IPinvestments Group" — in a 2018–2019 district-court campaign against five defendants. All five are listed in the patent's own litigation record. I found no appellate (CAFC) proceeding on the '302.

Source note / limitation: the defendant-to-case-number mapping below is drawn from the patent's Google Patents litigation block (authoritative text supplied with this task) cross-referenced against Unified Patents' campaign coverage and RPX's litigation records. The Google Patents block lists case numbers and jurisdictions but does not itself label which defendant sits in which case. Where I have not independently verified a pairing, I say so.

---

District court litigation

Verified in detail (case 1 only). For FireNet Technologies, LLC v. KEMP Technologies Inc., 1:18-cv-05564, I confirmed: filed 2018-06-20 in S.D.N.Y.; presiding judge Andrew L. Carter, Jr.; magistrate Barbara C. Moses; cause of action 35 U.S.C. § 271; jury demanded by plaintiff; § 290 AO-120 notice filed to the USPTO; KEMP served 2018-06-27, answer due 2018-07-18, extended by order (D.I. 12) to 2018-08-17, and answered with a jury demand on 2018-08-17 (D.I. 14). Plaintiff's counsel of record: Andrey Belenky, Hanna Glomska Cohen, Dmitry A. Kheyfits. Defendant's counsel: Stewart M. Leviss. Sources: https://dockets.justia.com/docket/new-york/nysdce/1:2018cv05564/[496016](/patent/496016) · https://unicourt.com/case/pc-db1-firenet-technologies-llc-v-kemp-technologies-inc-[789691](/patent/789691) · https://litigation.rpxcorp.com/litigation/nysdce-496016-firenet-technologies-v-kemp-technologies

Case-number discrepancy — flagged, not corrected. The Google Patents litigation block lists 3:19-cv-00798 (N.D. Cal.). An RPX-derived snippet in the earlier sections of this analysis renders the Fortinet case as "4:19-cv-00798." I could not resolve which is correct. Per the strict rule, I am not auto-correcting either identifier; the Google Patents record's 3:19-cv-00798 is what I would use, but verify against PACER.

Assertion-scope caveat — important. These were portfolio suits. The campaign asserted four patents in the same family (US 6,317,837 / US 7,739,302 / US 8,306,994 / US 8,892,600). Unified Patents' PATROLL prompt for the '302 states affirmatively that "[t]his patent has been asserted in district court against companies such as Kemp Technologies, Fortinet, Citrix, A10 Networks, and Fujitsu," citing the case list filtered to patent 7739302 (https://portal.unifiedpatents.com/litigation/caselist?patents=7739302&sort=-filed_date). I could not retrieve that filtered page to count assertions per defendant, so I cannot tell you whether the '302 was asserted against each named defendant or only some of them — only that the patent record and Unified both associate all five with '302-inclusive campaign activity.

---

Related proceedings that are NOT district-court litigation on the '302

• IPR2020-00471 — Unified Patents, LLC v. Firenet Technologies, LLC (PTAB). Filed 2020-03-13; instituted 2020-09-01; closed 2021-03-18. Challenged patent: US 8,892,600, a family sibling — not the '302. The '302 appears in this record only as petitioner's Exhibit 1012, alongside Ex. 1011 ('994) and Ex. 1013 ('837), plus Ex. 1015 (the '302's file history). Do not cite this as an IPR on the '302. Source: https://services.patexia.com/lawsuits/Unified-Patents-LLC-v-Firenet-Technologies-LLC-id-[133475](/patent/133475)/documents

• Unified Patents PATROLL prior-art contest on US 7,739,302. Contest window 2020-09-30 to 2020-11-17, $2,500 prize; prior art sought on at least claim 1. This is a crowdsourced art hunt, not a legal proceeding. Source: https://patroll.unifiedpatents.com/contests/3c5LNHXhhC639WoA6

• Brightwood Loan Services LLC IP security agreement (2019-04-05), released 2022-01-24, recorded against this patent with KEMP Technologies Inc. as assignor — a lien entry, not litigation, but it names a litigation defendant. Worth checking for standing/ownership purposes.

---

⚠️ Contradiction with a previously generated section — flagging explicitly

The earlier PTAB section of this analysis states that IPR2020-00471 resulted in "No Final Written Decision" and characterizes the 2021-03-18 document as a "Termination Decision Document," adding that "no § 315(e)(2) estoppel attached to anyone."

A live search result contradicts the substance of that characterization. Unified Patents' own published insight, dated 2021-03-18, states: "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." Source: https://www.unifiedpatents.com/insights/2021/3/18/firenet-technologies-patent-held-unpatentable

Per the operating rules, I prefer the search result over the prior analysis. Corrected position: all claims of US 8,892,600 were held unpatentable by the PTAB on 2021-03-18, and FireNet Technologies was the patent owner. I note the Patexia docket styles the 2021-03-18 filing as a "Termination Decision Document," which is consistent with a proceeding that ends by judgment rather than by a routine merits FWD (e.g., a request for adverse judgment under 37 C.F.R. § 42.73(b)). The two accounts can be reconciled on that basis, but the previously generated statement that the case simply "terminated pre-FWD" with "no FWD anywhere in this family" should not be relied on.

Scope limit: this correction concerns the '600, still not the '302. My independent conclusion on the '302 remains that I found no PTAB proceeding against it. But the downstream estoppel conclusion in the earlier section — "no § 315(e)(2) estoppel attached to anyone" — needs to be re-run, because a merits determination (or adverse judgment) in the '600 IPR can carry § 315(e) estoppel consequences for the petitioner and its real parties in interest as to the '600.

---

CAFC / appellate check

I found no Court of Appeals for the Federal Circuit proceeding involving US 7,739,302, in 2026 or any other year. Searches on the patent number, on "Firenet Technologies" + Federal Circuit, and on the five district-court case numbers surfaced no appeal.

This is a negative finding, not a verified absence. CAFC dockets are not fully indexed by the tools I have. Two observations bear on plausibility: (a) the '302 is recorded as Expired – Fee Related with an adjusted expiration of 2020-05-29, so any live controversy would be about past damages; and (b) the only '302-related district-court filings in the record are from 2018–2019. A separate point to check: because the PTAB held the '600 claims unpatentable in March 2021, FireNet may have appealed that decision — I could not confirm whether an appeal of IPR2020-00471 was filed, and I would not assume either way. Anyone needing certainty should query the CAFC's PACER/CM-ECF docket directly.

---

What I could not verify

1. Filing dates, docket numbers, judges, and outcomes for cases 2–5. I verified only the KEMP case in detail; tool limits stopped further retrieval.
2. Defendant-to-case-number pairing for cases 2–5 — inferred from RPX/Unified campaign coverage, not read off a complaint caption.
3. Per-defendant assertion lists — I could not confirm the '302 (as opposed to a sibling patent) was asserted against each of the five defendants, only that Unified and the patent record associate the '302 with the campaign.
4. Outcomes. UniCourt shows the KEMP case as "Pending – Other Pending," but that database entry is stale (last updated 2018). I found no judgment, dismissal, or settlement order for any of the five cases.
5. The Fortinet case-number discrepancy (3:19-cv-00798 vs. 4:19-cv-00798).

Recommended verification path: PACER dockets for 1:18-cv-05564 (S.D.N.Y.), 2:18-cv-00270 (E.D. Tex.), 3:18-cv-06502 and 3:19-cv-00798 (N.D. Cal.), and 1:19-cv-03199 (N.D. Ga.); plus the Unified Patents Portal caselist filtered to patent 7739302, and the CAFC docket for any appeal of IPR2020-00471.

I'll start by verifying the canonical list and checking whether any AIA trial proceedings exist outside the ODP ingest.

Let me run more targeted checks on specific proceeding numbers and the litigation defendants.

Found a lead — an IPR involving Unified and Firenet. Let me dig into proceeding numbers and whether any petition targeted the '302 patent itself.

PTAB / AIA Trial Analysis — U.S. Patent No. 7,739,302

Canonical source check first. The "PTAB proceedings on file" block supplied with this task (USPTO Open Data Portal ingest) returns zero AIA trial proceedings for US 7,739,302. Everything below is either (a) the empty-set finding itself, or (b) web-search-surfaced material that I explicitly flag as not a proceeding against the '302.

Proceedings overview

There are no AIA trial proceedings on US 7,739,302 — 0 IPRs, 0 PGRs, 0 CBMs, 0 derivation proceedings — meaning the patent has never been subjected to claim-level PTAB scrutiny at all: no claims canceled, no claims sustained, nothing instituted, nothing settled, nothing denied. The only PTAB-adjacent activity I could surface is (i) an IPR against a sibling patent in the same family (U.S. 8,892,600, IPR2020-00471), which the ODP would index under the '600, not the '302, and (ii) a Unified Patents PATROLL crowdsourcing contest aimed at the '302 that does not appear to have ripened into a filed petition. The defensive posture for a defendant today is therefore not "the patent is hardened by surviving IPRs" and not "specific claims are canceled" — it is something considerably better: the '302 appears to have expired on 2020-05-29 per the recorded adjusted-expiration date, its claims stand untested, and the practical § 286 damages window against any newly sued party has closed. See the strategic summary; the expiration point must be verified against USPTO Patent Center before you rely on it.

---

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

Scope caveat, stated up front: this proceeding was not filed against US 7,739,302. Unified's own announcement identifies the challenged patent as U.S. 8,892,600 ("the '600 patent"), which is the fourth member of the same family (all four family members share the 1998-09-01 priority date). The '302 appears in the IPR2020-00471 record as a petitioner's exhibit (Ex. 1012), alongside sibling patents US 8,306,994 (Ex. 1011, "Kentworthy '994") and US 6,317,837 (Ex. 1013, "Kentworthy '837"). Do not cite this proceeding as an IPR on the '302. I include it only because it is the nearest thing to PTAB activity touching this family, and because the exhibit set suggests the petitioner was litigating family-member priority/§ 112 issues — a detail worth mining if you ever have to attack the '302's 1998-09-01 priority claim.

• Type: Inter Partes Review
• Filed: 2020-03-13 (notice of accord filing date 2020-03-18)
• Status: Closed (not in the ODP list for the '302; record shows a termination decision). No final written decision.
• Judge panel: Not retrieved. I could not confirm APJ names from the sources I reached — do not assume a panel composition.
• Petition grounds: Not retrieved at claim/art granularity. Petitioner's exhibit list (Exs. 1009–1019) includes U.S. 6,098,172 (Coss), U.S. 6,147,976 (Shand), the '994, '302 and '837 family patents, Part 1/Part 2 — Building Internet Firewalls, the '302 file history, U.S. 7,209,256 (Kageyama), U.S. 5,559,933 (Boswell), U.S. 6,560,639 (Dan), and U.S. 6,345,300 (Bakshi). I have not verified which claims or which statutory bases (§ 102 / § 103 / § 112) were pleaded, and I will not guess.
• Institution decision: Instituted — "Trial Instituted Document" entered 2020-09-01, with a scheduling order the same day. The panel's reasoning is not in my retrieved material.
• Final Written Decision: None issued. The case terminated before the FWD deadline (which would have fallen on or about 2021-09-01, one year from institution).
• Settlement / termination: Termination Decision Document entered 2021-03-18, roughly six and a half months post-institution. A petitioner's updated mandatory notices was filed 2021-03-15, three days before termination. The termination basis is not stated in the material I retrieved — it is consistent with a joint motion to terminate in view of settlement (terms, if any, would typically be confidential), but it could also be an adverse judgment or other closure. Note also a joint stipulation to treat Exhibit 1005 as a declaration (2020-08-26) and an unidentified board document (2020-11-30).
• Appeal: None found. No Federal Circuit appeal appears in the record I reviewed for this proceeding; because no FWD issued, an appeal of a merits decision would not have been available. Flagging as unverified rather than confirming a negative.
• Defensive value: Low directly, real indirectly. It establishes nothing about the validity of any '302 claim. Its value is (1) exhibit-set intelligence about how the family's 1998-09-01 priority date can be attacked, and (2) the fact that termination pre-FWD means no § 315(e)(2) estoppel attached to anyone from this proceeding.

No proceeding found — Unified Patents PATROLL prior-art contest on the '302 (not a PTAB filing)

• What it is: On 2020-09-29 (contest window 2020-09-30 to 2020-11-17, $2,500 prize), Unified Patents ran a PATROLL contest seeking prior art on at least claim 1 of US 7,739,302. A $1,250 award to contest winner Euclid Woo was announced 2021-05-11. The contest page describes the patent as owned by FireNet Technologies, LLC (an IP Investments Group / IPinvestments Group NPE) and as having been asserted against KEMP Technologies, Fortinet, Citrix, A10 Networks, and Fujitsu.
• Why it matters: This is affirmative evidence that a defensive aggregator actively hunted art against the '302 and, on the public record I could reach, never filed. Combined with the ODP's zero-result return, that is a meaningful negative signal about the '302 specifically. It is not a proceeding and should never be cited as one.

---

Strategic summary

Claim status: all 30 claims of the '302 are UNTESTED at the PTAB; zero are canceled; zero are sustained through AIA trial. The patent issued with 30 claims (independent claims 1, 5, 10, 12, and 22). No AIA tribunal has ever construed, canceled, or upheld any of them. So there is no claim-level FWD to hand a judge, and equally no IPR-sanctioned narrowing to give the patent owner comfort. What the patent owner does have from the PTAB is nothing at all — no institution on the '302, and a family-sibling IPR (IPR2020-00471) that it apparently resolved before any FWD.

Estoppel landscape: essentially wide open on the '302. Section 315(e)(2) estoppel attaches only to grounds the petitioner raised or reasonably could have raised in a proceeding that reached a final written decision. There has been no institution on the '302 and no FWD anywhere in this family, so no IPR estoppel bars any invalidity ground against the '302 — not Unified, not its members/privies, not the 2018–2019 district-court defendants, nobody. If you are newly asserted against, your full § 102/§ 103/§ 112 toolkit in the district court is intact, and you are not estopped from filing an IPR (subject to the ordinary § 315(b) one-year bar running from your own service date, and the practical problem that a petition on an expired patent buys you little). The one thing to check is whether any identity of parties — e.g., a defendant that was an undisclosed real party in interest in IPR2020-00471 — could import estoppel from the '600; that inquiry matters only for the '600, not the '302.

Pattern signals. The patent owner is a serial monetizer (FireNet Technologies, LLC, IP Investments Group; RPX reports Intellectual Ventures retained an interest in the campaign). The campaign asserted a four-patent network-security portfolio — including the '302 — against KEMP (1:18-cv-05564, S.D.N.Y., filed 2018-06-20), Fujitsu (2:18-cv-00270, E.D. Tex.), A10 Networks (3:18-cv-06502, N.D. Cal.), Fortinet (3:19-cv-00798, N.D. Cal. per the Google Patents litigation block; RPX's snippet renders it "4:19-cv-00798" — verify), and Citrix (1:19-cv-03199, N.D. Ga.). A defensive aggregator (Unified Patents) is in the chain — it filed the family IPR and funded the art hunt against the '302 — but it did not file on the '302, and no defendant appears to have filed on the '302 either. The patent owner did not pursue any PTAB appeal in this record (there was no FWD to appeal), so there is no "aggressive PTAB appellate" signal to flag. Finally, note a chain-of-title anomaly worth a standing inquiry: the assignment record shows a 2019-04-05 intellectual-property security agreement recorded by Brightwood Loan Services LLC as collateral agent with KEMP Technologies Inc. as assignor, released 2022-01-24 — while the current assignee is listed as Firenet Technologies LLC. That is odd for a patent whose owner was suing KEMP in 2018, and it is exactly the kind of record you examine for standing/ownership defects.

The expiration point dominates everything else. The structured data records the '302 as Expired – Fee Related, with an adjusted expiration of 2020-05-29 (consistent with a 20-year term measured from the 1998-09-01 earliest benefit date plus roughly 636 days of PTA). An expired patent cannot be prospectively infringed — injunctive relief is off the table, and the only theoretical exposure is back damages. Under 35 U.S.C. § 286, recovery is barred for infringement occurring more than six years before the complaint is filed. The last possible day of infringement was 2020-05-29, so a complaint would have had to be filed by 2026-05-29 to reach even a single day of pre-expiration infringement. As of today (2026-09-12), a newly filed suit reaches back only to 2020-09-12 — after the patent expired — leaving essentially no compensable period. Verify the expiration date and any term extension or revival on Patent Center before you bet a case on it, and check the term of the sibling patents ('994, '600) separately, since they share the 1998-09-01 priority and face the same or an earlier term limit.

Recommended next steps

1. Lead with the negative finding on PTAB activity, and make it a sword, not a shrug. There is no FWD, no institution, no canceled claim, and no estoppel on the '302. If opposing counsel implies the patent has been "tested and survived," that is false — it has never been tested.
2. Verify the 2020-05-29 expiration immediately in USPTO Patent Center (term, PTA, any maintenance-fee lapse or revival, and any terminal disclaimer in the file history). If it holds, the demand letter is worth little: any 2026-or-later complaint reaches only post-expiration conduct. Expect the patent owner to rely on pre-2020 sales under an earlier-filed, still-pending case — so check the status of the 2018–2019 Firenet cases.
3. If you are a defendant in a live legacy case (KEMP/Fujitsu/A10/Fortinet/Citrix), the § 286 window is measured from that complaint, so the expiration analysis is less forgiving — your priorities there are (a) the Brightwood/KEMP title entry for standing, and (b) the priority-date vulnerability of the 1998-09-01 claim that Unified was probing in IPR2020-00471, which is now unestopped and unadjudicated.
4. Do the RPI/privity check on IPR2020-00471 before assuming you are free of estoppel. Confirm the full petitioner and RPI disclosure and whether any current defendant was a privy; estoppel from that case can only touch the '600, but the ownership overlap could matter.
5. If you want PTAB cover anyway, remember the statutory limits: an IPR petition on an expired patent is rarely worth the fee, and § 315(b) may already bar you depending on service date. The better play is a district-court § 101/§ 112/§ 103 motion and a damages-window attack.
6. Docs to pull: IPR2020-00471 record (institution decision, 2021-03-18 termination decision, Ex. 1012 = the '302, Ex. 1013 = the '837), filed via USPTO PTAB E2E / Patent Trial and Appeal Board End-to-End; litigation dockets for 1:18-cv-05564, 2:18-cv-00270, 3:18-cv-06502, 3:19-cv-00798, and 1:19-cv-03199.

Sources actually relied on (all retrieved 2026-09-12): the supplied ODP "PTAB proceedings on file" block (zero results); Unified Patents PATROLL contest page for US 7,739,302 (https://patroll.unifiedpatents.com/contests/3c5LNHXhhC639WoA6); Unified Patents insights posts of 2020-03-16 ("FireNet Technologies patent challenged as likely invalid," identifying U.S. 8,892,600), 2020-09-16 ("$2,500 for FireNet Technologies prior art"), and 2021-05-11 ("$1,250 Awarded for FireNet Technologies prior art"); the Patexia docket page for Unified Patents, LLC v. Firenet Technologies, LLC, IPR2020-00471 (https://services.patexia.com/lawsuits/Unified-Patents-LLC-v-Firenet-Technologies-LLC-id-[133475](/patent/133475)/documents); RPX campaign coverage; and the Google Patents page for US7739302B2 (claims, assignment chain, litigation list, adjusted expiration). Items I could not confirm — the IPR2020-00471 panel, its grounds, the termination basis, and whether any '302 petition was ever filed — are flagged as unconfirmed above rather than filled in.

I'll research the assignment chain for US 7739302 across the sources available to me.

Good — strong NPE signals emerging. Now let me try to pin down reel/frame numbers and correspondents of record.

Research limitation notice (read first)

I could not retrieve the USPTO Assignment Center records themselves — the Assignment Center search and its backing API were not reachable from my available tools, and no cached mirror of the reel/frame pages for this patent surfaced. I have therefore not included any reel/frame numbers or correspondent (attorney) names. Fabricating those would be worse than omitting them. Everything below is grounded in (a) the patent's own Google Patents legal-events/assignment record (quoted in the authoritative text you supplied), and (b) RPX and Unified Patents records on the resulting litigation campaign. Reel/frame and correspondent of record must be pulled directly from USPTO Assignment Center by searching patent number 7739302; I flag each field I could not verify.

Also note a terminology caveat: the dates in the Google Patents legal-events feed are recording dates, not execution dates. Execution dates are not exposed in that feed. The Assignment Center record is the only place to get execution dates, and it is the field I could not reach.

---

Inventors

Pattern notes:

• Only one inventor across the entire family (US 6,317,837 → US 7,739,302 → US 8,306,994 → US 8,892,600). No co-inventor attrition to analyze.
• The inventor personally appears as an assignor in the chain. Recorded 2004-07-23, an assignment of Kenworthy, Stacy → Opticaute, Inc. (conveyance: "ASSIGNMENT OF ASSIGNORS INTEREST"), and recorded again 2006-12-04, Kenworthy, Stacy → Opticaute, Inc. (conveyance: "ASSIGNMENT OF ADDITIONAL RIGHTS"). This means the inventor's personal residual interest was swept up years after the corporate asset had already moved on — a cleanup pattern typical of a distressed asset monetization, not a normal employment assignment.
• Two assignments were recorded on the same day, 2004-07-23: Optifacio, Inc. → Opticaute, Inc. and Kenworthy → Opticaute, Inc. Simultaneous corporate and inventor conveyances on one recording date is the signature of a title-cure exercise preparing a portfolio for sale.
• Not determinable from available data: whether the inventor departed the original assignee within 12 months of filing (1998-09-01). The patent does not state employment end dates.

---

Original assignee

• Entity named on the issued patent: Google Patents lists the Original Assignee as "Individual" for US 7,739,302. That is consistent with the record: the application (Ser. No. 09/951,877) was filed 2001-09-11 as a continuation of Ser. No. 09/144,954 (now US 6,317,837), and the file is associated with inventor Kenworthy personally rather than a corporate assignee.
• The operating company behind the family is ApplianceWare, Inc. — named as assignor in the recorded assignment of 2002-01-16 to Optifacio, Inc. The parent patent US 6,317,837 appears in the family citation record under assignee Applianceware, Llc.
• Business: ApplianceWare was a network-attached storage / "appliance" software-and-hardware developer — the patent's own specification is written from the perspective of a vendor shipping a NAD server product (CD-ROM towers, printers, video codecs on a LAN). The claims recite a NAD server that ships with an integrated firewall management component.
• Did they ship a product embodying the claims? The specification describes a commercial NAD server implementation in detail, and the claims are drafted to that server. On the record available to me I cannot confirm a productized shippable unit was ever sold under the claim set.
• Current status: No evidence ApplianceWare still operates. The recorded chain shows the family leaving ApplianceWare's hands in 2002 (to Optifacio) and then passing through Opticaute (2004, 2006) and Robust Networks, LLC (2007) — a sequence consistent with a failed dot-com-era venture's IP being liquidated. I could not verify any acquisition, dissolution, or bankruptcy filing for ApplianceWare, Optifacio, or Opticaute; treat that as unknown rather than confirmed.

---

Assignment timeline

All 11 entries below are recorded assignments/reassignments per the patent's legal-events record. Execution dates not retrieved. Reel/frame not retrieved. Correspondent not retrieved.

1. 2002-01-16 (recorded)

   • Conveyance: Assignment of assignors' interest
   • Assignor: ApplianceWare, Inc.
   • Assignee: Optifacio, Inc.
   • Correspondent: not retrieved — requires Assignment Center lookup
   • Context: First transfer out of the operating company, ~4 months after the continuation was filed; asset sale or wind-down.

2. 2004-07-23 (recorded) — same-day pair with #3

   • Conveyance: Assignment of assignors' interest
   • Assignor: Optifacio, Inc.
   • Assignee: Opticaute, Inc.
   • Correspondent: not retrieved
   • Context: Internal reorg / near-identical name change (Optifacio → Opticaute); no new operating business introduced.

3. 2004-07-23 (recorded) — same-day pair with #2

   • Conveyance: Assignment of assignors' interest
   • Assignor: Kenworthy, Stacy (individually)
   • Assignee: Opticaute, Inc.
   • Correspondent: not retrieved
   • Context: Title cure — the inventor's personal residual interest is conveyed on the same day as the corporate interest, consolidating clean title.

4. 2006-12-04 (recorded)

   • Conveyance: Assignment of additional rights
   • Assignor: Kenworthy, Stacy
   • Assignee: Opticaute, Inc.
   • Correspondent: not retrieved
   • Context: Second, later conveyance of "additional rights" from the inventor — a follow-on title-cure ~2 years after the first; the family is being assembled for sale.

5. 2007-02-15 (recorded)

   • Conveyance: Assignment of assignors' interest
   • Assignor: Opticaute, Inc.
   • Assignee: Robust Networks, LLC
   • Correspondent: not retrieved
   • Context: Transfer to an LLC vehicle; Opticaute, Inc. disappears from the chain and is never seen again.

6. 2015-11-18 (recorded)

   • Conveyance: Merger
   • Assignor: Robust Networks, LLC
   • Assignee: Mineral Lassen LLC
   • Correspondent: not retrieved — this is the highest-value correspondent lookup in the chain
   • Context: Corporate merger used as the conveyance vehicle; Mineral Lassen LLC is a known Intellectual Ventures–linked holding entity (see signal 2).

7. 2017-09-26 (recorded)

   • Conveyance: Assignment of assignors' interest
   • Assignor: Mineral Lassen LLC
   • Assignee: Intellectual Ventures Assets 57 LLC
   • Correspondent: not retrieved
   • Context: Transfer into the IV asset-holding shell numbering series; start of the cascading 2017–2018 transfers.

8. 2018-01-19 (recorded)

   • Conveyance: Assignment of assignors' interest
   • Assignor: Intellectual Ventures Assets 57 LLC
   • Assignee: IQ Holdings, LLC
   • Correspondent: not retrieved
   • Context: Second hop in a three-hop cascade; entity has no operating business.

9. 2018-04-13 (recorded)

   • Conveyance: Assignment of assignors' interest
   • Assignor: IQ Holdings, LLC
   • Assignee: Firenet Technologies, LLC
   • Correspondent: not retrieved
   • Context: Transfer-to-asserter; current owner; suit filed ~9 weeks later (see signal 5).

10. 2019-04-05 (recorded)

    • Conveyance: Intellectual property security agreement
    • Assignor: KEMP Technologies Inc.
    • Assignee: Brightwood Loan Services LLC, as collateral agent
    • Correspondent: not retrieved
    • Context: Anomaly. This is a security interest, not a title transfer, and the grantor named is a defendant in the FireNet litigation (KEMP), not the patent owner. On its face this looks like a collateral filing on KEMP's own IP portfolio that landed on this patent's legal-events record; I flag it as ambiguous and unverified rather than treating it as part of the ownership chain.

11. 2022-01-24 (recorded)

    • Conveyance: Release of security interest in patents
    • Assignor: Brightwood Loan Services LLC
    • Assignee: KEMP Technologies Inc.
    • Correspondent: not retrieved
    • Context: Release of the 2019-04-05 security interest; pairs with entry 10 and confirms entry 10 was a lien, not an ownership transfer.

Current assignee of record: Firenet Technologies LLC (confirmed by the patent header and by Unified Patents' ownership statement).

Relevant litigation for the transfer-timing analysis (not assignments):

• FireNet Technologies, LLC v. KEMP Technologies Inc., 1:18-cv-05564 (S.D.N.Y.), filed 2018-06-20
• FireNet Technologies, LLC v. Fujitsu, 2:18-cv-00270 (E.D. Tex.), filed 2018
• FireNet Technologies, LLC v. Fortinet, 4:19-cv-00798 (N.D. Cal.)
• FireNet Technologies, LLC v. Citrix, 1:19-cv-03199 (N.D. Ga.)
• Also asserted against A10 Networks.
• Unified Patents IPR IPR2020-00471 against family member US 8,892,600; Unified Patents Patroll contest on US 7,739,302, Sep 30 – Nov 17, 2020.

---

Timeline diagram

timeline
    title Ownership of US 7739302
    1998 : Filed by ApplianceWare
         : Parent patent issued
    2001 : Continuation filed by inventor
    2002 : Assigned to Optifacio Inc
    2004 : Assigned to Opticaute Inc
         : Inventor assigns personal rights
    2006 : Additional rights to Opticaute
    2007 : Assigned to Robust Networks LLC
    2010 : Patent issued
    2015 : Merger into Mineral Lassen LLC
    2017 : Transferred to IV Assets 57 LLC
    2018 : Transferred to IQ Holdings LLC
         : Transferred to Firenet Technologies
         : First suit filed against KEMP
    2019 : Suits against Fortinet and Citrix
    2020 : Unified Patents IPR and prior art contest

---

NPE / troll-pattern signals

1. Shell-entity transfer — PRESENT.
Three consecutive licensing-only vehicles with no operating business: Intellectual Ventures Assets 57 LLC (2017-09-26), IQ Holdings, LLC (2018-01-19), and Firenet Technologies, LLC (2018-04-13). "Firenet Technologies" is an operating-sounding name applied to a patent that is owned by it, but RPX identifies it as "an affiliate of Georgia-based IP Investments Group LLC (d/b/a IPinvestments Group), a monetization firm controlled by Michael W. McLaughlin" — i.e., a single-purpose assertion LLC, not a product company. Strongest single piece of evidence: Firenet's only commercial activity on the record is filing infringement suits (KEMP, Fujitsu, Fortinet, Citrix, A10), and Unified Patents describes it flatly as "an NPE and entity of IPinvestments Group."

2. Known asserter in the chain — PRESENT.
Two independent matches against public NPE lists:

• Intellectual Ventures appears directly in the chain as Intellectual Ventures Assets 57 LLC (2017-09-26) and via IV-linked Mineral Lassen LLC (2015-11-18). IV is named on the standard known-asserter list.
• Firenet Technologies, LLC / IP Investments Group is a high-frequency plaintiff tracked by both Unified Patents (Patroll contest, IPR2020-00471 against family member US 8,892,600) and RPX (network security campaign coverage, July 2018 – July 2019).
• Additionally, RPX states that "Intellectual Ventures LLC (IV) retains an interest" in this very campaign — a retained-interest structure, which is materially different from a clean divestiture.

3. Repeat correspondent across the chain — UNCLEAR / NOT VERIFIABLE.
This is the signal I most wanted and could least verify. I did not retrieve any reel/frame entry, so I cannot name or compare correspondents of record. No finding either way. Two cautions for whoever completes this: (a) do not substitute FireNet's litigation counsel (the S.D.N.Y. docket lists Andrey Belenky, Hanna Glomska Cohen, and Dmitry A. Kheyfits) for the assignment correspondent — they are different roles and different filings; (b) the highest-yield lookups are the 2015-11-18 merger into Mineral Lassen LLC, the 2017-09-26 IV Assets 57 LLC transfer, and the two 2018 transfers, since those are the links most likely to share a single recording attorney.

4. Cascading transfers — PRESENT.
Three title transfers in 6 months and 18 days: 2017-09-26 (Mineral Lassen → IV Assets 57), 2018-01-19 (IV Assets 57 → IQ Holdings), 2018-04-13 (IQ Holdings → Firenet). If the 2006-12-04 additional-rights conveyance is counted as the closing step of the Opticaute consolidation, the family also shows a distinct second cascade in 2004–2007 (Optifacio → Opticaute → Robust Networks).

5. Pre-litigation transfer — PRESENT, strongly.
Assignment to Firenet Technologies, LLC recorded 2018-04-13; first suit (KEMP, 1:18-cv-05564, S.D.N.Y.) filed 2018-06-20 — approximately 9 weeks. The remaining suits against Fujitsu, Fortinet, and Citrix followed within 15 months. The chain was plainly assembled to create a clean standing record in the asserting entity.

6. Bankruptcy fire-sale — UNCLEAR.
The 2002 → 2007 chain (ApplianceWare → Optifacio → Opticaute → Robust Networks) has the shape of a post-dot-com liquidation, and the same-day 2004-07-23 title cures plus the 2006-12-04 "additional rights" cleanup are consistent with distress. But I have no bankruptcy filing, docket, or sale-order evidence for any of those three entities. Not a finding on the current record.

7. Privateering — UNCLEAR.
RPX's "campaign in which Intellectual Ventures LLC (IV) retains an interest" supports a retained-interest structure, which is a cousin of privateering. But classic privateering involves an operating company funding an NPE against competitors; here the transferor (IV) is itself a licensing entity, so the better characterization is NPE-to-NPE with retained economics. Marking unclear rather than stretching the definition.

8. Defensive aggregator (anti-NPE) — NOT PRESENT.
The chain terminates at Firenet Technologies, LLC, an assertion vehicle, not at RPX, AST, LOT, Unified Patents, or OIN. Note the inverse case: Unified Patents attacked this family (IPR2020-00471, plus a $2,500 Patroll prior-art contest on the '302 specifically) — so the patent has been contested, but not neutralized by acquisition. The patent is also now Expired – Fee Related with expiration adjusted to 2020-05-29, which independently moots it.

---

Verdict

NPE — high confidence.

Four independent strong signals: (i) a shell-entity hand-off on 2017-09-26 / 2018-01-19 / 2018-04-13 through Intellectual Ventures Assets 57 LLC, IQ Holdings, LLC, and Firenet Technologies, LLC — none of which ship a product; (ii) a known asserter squarely in the chain, since IV is named on public NPE lists and Firenet/IP Investments Group is a tracked high-frequency plaintiff per Unified Patents and RPX, with RPX noting IV retains an interest in the campaign; (iii) a cascading three-hop transfer compressed into under 7 months in 2017–2018; and (iv) a pre-litigation transfer to Firenet recorded 2018-04-13, only ~9 weeks before the first suit against KEMP on 2018-06-20. The 2004–2007 transfers out of a defunct appliance vendor (Optifacio → Opticaute → Robust Networks) explain how the family entered monetization, and Unified Patents' description of Firenet as "an NPE and entity of IPinvestments Group" removes any residual doubt about the current owner's character.

Caveat on confidence: the verdict rests on party identity, 2017–2018 transfer dates, and litigation timing — not on reel/frame entries or correspondent recurrence, which I could not retrieve. Signal 3 (repeat correspondent) is the one item that could raise or lower this from high to very high confidence and it remains unverified.

Verification link: USPTO Assignment Center — search patent 7739302 (alternate index: assignment.uspto.gov). Pull reel/frame, execution date, and correspondent for the 11 entries above; the 2015-11-18 merger and 2017-09-26 / 2018-01-19 / 2018-04-13 transfers are the four records most worth a correspondent comparison.

I'll research US 7,739,302 and its cited prior art. Let me start with several targeted searches.

I have the full citation list. Let me pull details on the most relevant references and the ranked invalidity analysis.

Prior-Art Analysis — US 7,739,302 B2

"Network attached device with dedicated firewall security"
Inventor: Stacy Kenworthy (Atlanta, GA) · Appl. No. 09/951,877, filed 2001-09-11 · Granted 2010-06-15
Continuation of App. 09/144,954 (filed 1998-09-01), now US 6,317,837 ("Internal network node with dedicated firewall")
Family: US 6,317,837 / US 7,739,302 / US 8,306,994 / US 8,892,600 (all priority 1998-09-01)
Assignee chain: ApplianceWare/Optifacio → Opticaute → Robust Networks → Mineral Lassen → IV Assets 57 → IQ Holdings → Firenet Technologies LLC
Status: Expired – Fee Related, adjusted expiration 2020-05-29. Multiple district-court assertions (N.D. Ga. 1:19-cv-03199; E.D. Tex. 2:18-cv-00270; N.D. Cal. 3:18-cv-06502 and 3:19-cv-00798; S.D.N.Y. 1:18-cv-05564) against Kemp, Fortinet, Citrix, A10 Networks, Fujitsu.
Source: https://patents.google.com/patent/US7739302/en

Note on § 102 framework used below. The application was filed 2001-09-11 and is a continuation of a 1998-09-01 application, so pre-AIA 35 U.S.C. § 102 applies and the critical date is 1998-09-01 (rebuttable by a later actual invention date, but that is the working assumption). A reference therefore anticipates only if it is (i) a printed publication/public patent before 1998-09-01 (§ 102(a)), (ii) published/patented before 1997-09-01 (§ 102(b)), or (iii) a U.S. patent granted on an application filed before 1998-09-01 (§ 102(e)). Anticipation also requires a single reference disclosing every element of the claim as arranged; references that meet only some limitations are § 103 material, not § 102 art. The mappings below are potentially anticipates only and would require full element-by-element charts.

---

1. The claim set to be mapped (30 claims, as granted)

Claim 1's closing phrase ("the NAD being further configured to filter the data packet…") is a drafting anomaly (the antecedent "NAD server" is not what "the NAD" refers to); it is a useful claim-construction lever, but note it does not change the prior-art analysis.

---

2. Master table — all 56 references cited in US 7,739,302

Tier = my relevance ranking for the broad independent claims (1, 5, 10, 12, 22). "§102 basis" reflects the earliest date that can be used.

Tier 1 — Closest art; direct § 102 candidates

Tier 2 — Strong § 103 combiners; possible § 102 on narrower claims

Tier 3 — Cited, but not § 102 prior art against the 1998-09-01 date (or only peripherally relevant)

---

3. Deep dive — the strongest § 102 candidates

3.1 US 5,826,014 A (Coley et al., Network Engineering Software) — the single closest citation

• Full citation: US 5,826,014 A, "Firewall system for protecting network elements connected to a public network," Christopher D. Coley & Ralph E. Wesinger Jr., filed 1996-02-06, granted 1998-10-20. Family member US 6,061,798 A (filed 1998-10-19; granted 2000-05-09).
• § 102 basis: § 102(e), effective as of the 1996-02-06 filing date (grant itself came after the critical date, which is irrelevant under § 102(e)).
• Description: A firewall comprising a stand-alone computing platform connected between the public network and the network element(s) to be protected, "such that all access to the protected network elements must go through the firewall." The firewall application is preferably the only application on the box. Proxy agents are assigned to each incoming request by the service protocol/port number indicated in the request; an assigned proxy agent verifies the authority of the incoming request to access the network element (verifying source address authorization, destination validity, permitted time window, passwords) and, once verified, completes the connection to the protected network element on behalf of the request's source.
• Why it maps onto the '302 claims: the "firewall box between the network and the protected element" architecture is functionally the '302's "NAD server disposed between the network client and the NAD." The proxy-agent verification of source address and destination is the '302's header-based authorization; "completes the connection on behalf of the source" is the '302's proxy/generated-packet concept. US 6,061,798's own claim 1 ("a firewall box comprising a stand alone computing platform… at least one proxy agent… 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") reads with striking similarity to '302 claims 1, 11, 12 and 22.
• Potentially anticipates: claims 1, 10, 12, 22 (independent), and dependent claims 6–9, 11, 13, 16.
• Weak point: the '302 claim 1 requires protection "in addition to any protection afforded by a firewall." US 5,826,014 is the firewall, so a patentee may argue this limitation is unmet — this is the key dispute, and it is why the reference may end up being § 103 rather than § 102 art on claim 1 (though claim 10's "network running a bastion firewall" framing is easier).

3.2 US 5,623,601 A (Milkway Networks) — cleanest § 102(b) reference

• Full citation: US 5,623,601 A, "Apparatus and method for providing a secure gateway for communication and data exchanges between networks," Milkway Networks Corporation, filed 1994-11-18, granted 1997-04-22.
• § 102 basis: § 102(b) — granted more than one year before the 1998-09-01 filing date. This is the strongest date-wise reference in the set.
• Description: A gateway station with a kernel modified to disable packet forwarding, plus application-level proxy processes; a generic proxy listens on all 64K ports; the gateway establishes a first communications session with the source and a second, independent session with the destination, transparently passing data between them; access is gated by rule bases and per-source authentication; data-sensitivity screening is performed at the application layer.
• Potentially anticipates: claims 1, 5, 10, 12, 22; dependent claims 9, 15, 16, 17, 25, 28. The two-session proxy mechanism directly reads on claims 15/25 ("selectively generate a new packet… to an intermediary computing device") and the application-layer screening maps to claims 17/28.
• Weak point: the '302 is directed to a NAD server/network attached device; '601 is a network-boundary gateway. That distinction is the likely battleground, and the Limestone study ranked it below US 6,321,336.

3.3 US 6,321,336 B1 (Secure Computing / Applegate & Romatoski) — highest-ranked by third-party analytics

• Full citation: US 6,321,336 B1, "System and method for redirecting network traffic to provide secure communication," John Applegate & Jeff Romatoski, Secure Computing Corp., filed 1998-03-13, granted 2001-11-20.
• § 102 basis: § 102(e) as of the 1998-03-13 filing date (months before the critical date).
• Description: A firewall between an internal network and an external network (the Internet) that intercepts a communication, stores the original destination address in a session control block, rewrites the IP header destination address and recalculates the IP checksum, and — once the communication is authorized — performs a system call to retrieve the original destination and routes the communication to the intended destination. It also hides internal computer identities (network address hiding) and logs attempted security breaches and suspicious activity.
• Potentially anticipates: claims 1, 10, 12, 22; deps 13, 14, 26.
• Note: the independent TechsonIP Limestone validity report for US 7,739,302 ranks US 6,321,336 B1 #1 (score 1.295) among its invalidity candidates — https://s3.amazonaws.com/report.limestoneip.com/9MBZuq8Ezs5v7FFaH-IFHo.full.html

3.4 US 6,032,259 A (IBM) — authentication server on a dedicated path

• Full citation: US 6,032,259 A, "Secure network authentication server via dedicated serial communication path," IBM, filed 1997-05-16, granted 2000-02-29.
• § 102 basis: § 102(e) @1997-05-16.
• Description: An authentication server that gates access to a resource over a dedicated (serial) communication path, separate from the general network. Confidence note: I have the bibliographic record and title but not the full text; the description above is inferred from the title and should be verified against the specification before it is relied on in a chart.
• Potentially anticipates: claims 1, 11, 12, 23 — the dedicated-path-plus-server architecture is the closest cited art to the '302's "NAD server… configured to electronically communicate with the NAD over a connection" and to claim 11's "network access to the NAD is only available through the server."

3.5 US 5,968,176 A (3Com) — multilayer firewall

• Full citation: US 5,968,176 A, "Multilayer firewall system," 3Com Corp., filed 1997-05-29, granted 1999-10-19. § 102(e) @1997-05-29.
• Description: A firewall enforcing security policy at multiple layers of the protocol stack, including the application layer.
• Potentially anticipates: claims 1, 5, 10, 22; and is the most direct prior art for dependent claims 17 and 28 (filtering "at an application layer"), which the specification expressly ties to the ISO/OSI layered model (FIG. 4, ¶[0031]).

3.6 US 6,061,797 A (IBM) — outside access through a firewall

• Full citation: US 6,061,797 A, "Outside access to computer resources through a firewall," IBM, filed 1996-10-21, granted 2000-05-09. § 102(e) @1996-10-21.
• Potentially anticipates: claims 10 and 1 — this is the most on-point cited art for claim 10's "managing access from outside of a network running a bastion firewall" and claim 5's "at least some of the plurality of requests originate from within the network without passing through the firewall."

3.7 US 5,950,015 A (Abirnet) and US 5,778,174 A (U.S. West)

• US 5,950,015 A, "Network session wall passively listening to communication session, with use of access rules, stops further communication between network devices by emulating messages to the devices," filed 1996-10-29, granted 1999-09-28 (§ 102(e)). Rule-driven interception with selective session termination → potentially anticipates claim 1 (filter + deny) and claim 22 (means for filtering/blocking).
• US 5,778,174 A, "Method and system for providing secured access to a server connected to a private computer network," U.S. West, filed 1996-12-10, granted 1998-07-07 — the rare reference that is both § 102(a) and § 102(e) art (granted pre-critical-date). Potentially anticipates claims 1, 10, 12, 22.

3.8 GB 2 318 031 A (Secure Computing) — proxy firewall, published pre-critical-date

• Full citation: GB 2 318 031 A, "Network firewall with proxy," Secure Computing Corp., priority 1996-09-13, published 1998-04-08. § 102(a) (published before the invention, less than one year before the filing date).
• Potentially anticipates: claims 1, 10, 11, 22, and — as a foreign counterpart of the same Assignee's proxy architecture — provides § 103 support for claims 15 and 25.

3.9 Device-specific references for the NAD limitations (claims 21 & 29)

• US 5,642,337 A (Sony, "Network with optical mass storage devices," filed 1995-03-14, granted 1997-06-24 — § 102(b)): optical mass-storage devices attached to a LAN. Directly relevant to the '302's CD-ROM/optical NAD species and to claims 21, 29.
• US 5,909,493 A (Ricoh, filed 1996-10-16, granted 1999-06-01 — § 102(e)) and US 5,719,786 A (Novell, filed 1993-02-03, granted 1998-02-17 — § 102(a)): networked peripherals/audio-video media devices → claims 21, 29.
• US 5,987,547 A (Texas Instruments, filed 1997-03-31, granted 1999-11-16 — § 102(e)): network computer with an interchangeable attached storage drive → claims 12, 20, 21, 29 and the "directly attached device"/interface limitation.

---

4. References not cited in the '302 prosecution that third parties rank highly

These do not appear in the '302 citation list but come from the Limestone validity report commissioned for the Firenet Technologies litigation and should be considered separately:

Also worth checking (family citations, not '302 citations): US 6,658,526 B2 (Storage Technology, "Network attached virtual data storage subsystem") and US 6,047,353 A (EMC, "Method and apparatus for monitoring of host activities relating to an attached storage device") — both bear directly on the "network attached device"/storage-monitoring concept underlying claims 1, 5, 12, and 21.

---

5. Bottom line and explicit caveats

1. Best § 102 candidates on the independent claims: US 5,826,014 (network-engineering-software firewall box; § 102(e)); US 5,623,601 (Milkway; the only strong § 102(b) reference); US 6,321,336 (Secure Computing; § 102(e); top-ranked by third-party analytics); US 6,032,259 (IBM); US 5,968,176 (3Com).
2. Best § 102 candidates on the dependent limitations: US 5,968,176 for claim 17/28 (application-layer filtering); US 5,826,014 and US 5,950,015 for claim 9/16 (port-based filtering); US 5,642,337/US 5,909,493/US 5,987,547 for claims 20/21/23/24/29 (SCSI, peripheral/storage NADs); US 6,061,797 for claim 10's "outside a network running a bastion firewall."
3. Every mapping above is a "potential anticipation," not a conclusion. Pre-AIA anticipation requires that a single reference disclose all limitations as arranged, including claim 1's "in addition to any protection afforded by a firewall," claim 5's "independently of a firewall external to the NAD," and claim 10's "network running a bastion firewall." Because most cited references are the firewall/gateway, they are more naturally § 103 combiners than § 102 anticipating references, and that framing should be charted first.
4. Do not treat the whole 56-reference list as § 102 art. At least 8 of the listed references (US 6,349,336; US 6,393,474; US 6,539,425; EP 1 396 960; US 6,715,084; EP 1 420 600; US 6,751,677; US 7,120,931), plus WO 99/12298, WO 99/46906 and US H1944 H1, have effective prior-art dates after the 1998-09-01 critical date and cannot be § 102 art against US 7,739,302's claims. They were almost certainly cited during prosecution of the later continuations (US 8,306,994 / US 8,892,600).
5. Scope of my confidence: the bibliographic data, dates, and claim text above are taken from the authoritative patent text and the Google Patents record; the descriptions of US 5,826,014, US 5,623,601, US 6,321,336 and US 6,061,798 are grounded in the retrieved abstracts/claims. The one-line descriptions of the lower-tier references and of US 6,032,259 are title-derived; verify each against its full specification before relying on it in a chart.

Sources: https://patents.google.com/patent/US7739302/en · https://patents.google.com/patent/[US6233618B1](/patent/US6233618B1) · https://patents.google.com/patent/[US6119236A](/patent/US6119236A) · http://patentimages.storage.googleapis.com/68/16/84/67a7ac1dbd148b/US8306994.pdf · https://www.freepatentsonline.com/[5826014](/patent/5826014).html · https://www.freepatentsonline.com/[5623601](/patent/5623601).html · https://www.freepatentsonline.com/[6321336](/patent/6321336).html · https://portal.unifiedpatents.com/patents/patent/US-[6061798](/patent/6061798)-A · https://patroll.unifiedpatents.com/contests/3c5LNHXhhC639WoA6 · http://s3.amazonaws.com/report.limestoneip.com/9MBZuq8Ezs5v7FFaH-IFHo.full.html

I'll ground this analysis by verifying the key prior-art references cited on the patent page before constructing the combinations.

Good grounding on the firewall references. Let me verify the remaining high-value references from the cited list.

Obviousness Analysis — US 7,739,302 B2

"Network attached device with dedicated firewall security"

Analyst note. This analysis picks up from the patent text already supplied rather than re-describing it. I focus on (a) the effective prior-art date, (b) which of the 56 examiner-cited references are actually available as §102/§103 art, (c) limitation-by-limitation combinations, and (d) motivations to combine under KSR. Where I could not verify something (e.g., the file wrapper), I say so.

---

1. Legal framework and the effective critical date

Two consequences drive everything below:

1. The parent US 6,317,837 B1 is not prior art to the '302. The '302 is a straight continuation of the '837 and claims the same 1998‑09‑01 date, so the '837 is part of the same family and cannot be used as a §102/§103 reference against it. It appears in the page's "Family Cites Families" list, not the §102 "Citations" list, and should be treated as such.
2. A large block of the examiner-cited art post-dates 1998‑09‑01 and is not available. The obviousness case must be built on the pre‑1998‑09‑01 subset (§102(b)/(e) references).

1.1 Availability screen of the cited references

Usable-art core (pre‑1998‑09‑01): Milkyway '601, Sony '337, Secure Computing GB '031, US West '174, Colly '014, Ricoh '093, Abirnet '015, 3Com '176, TI '547, Nortel '807, Cylink '077, IBM '475, IBM '797, Internet Dynamics '027, Shipley '236, Nomadix '892, NSA '755, Content Advisor '618, Secure Computing '336, StorageTek '526, EMC '353, Dataplow '846, EMC '120, ITT '209, Microsoft '507, Fuji Xerox '670.

---

2. What the independent claims actually require (and what they do not)

Reading the four independent claims (1, 5/10/12/22) together, the shared inventive core reduces to three functional requirements:

Three observations sharpen the §103 inquiry:

• L3 is drafted in the disjunctive ("at least one of … and …"). Under the SuperGuide line of construction, this reads on any one of source IP, destination IP, or route. That means the claim is met by the most rudimentary stateless packet filter — a point the examiner's own art (Colly, Milkyway, IBM, GB '031) satisfies many times over.
• L5 is a statement of result / intended use. "Such that the NAD is protected … in a manner that is in addition to any protection afforded by a firewall" recites an advantage, not structure. Per In re Otto / In re Schreiber line, result language does not patentably distinguish where the structure is old. The motivation supplied by L5 is better used against the patent: it is the stated design goal, and the art supplies it.
• The claim's antecedent structure is defective. Claim 1 shifts mid‑sentence from "the NAD server … cause the NAD server to:" to "the NAD being further configured to filter…". There is no antecedent for "the NAD being configured"; the filtering step is grammatically attributed to the device rather than the server. That ambiguity should be tested under Nautilus (reasonable certainty) and under §112(b), but I would not lead with it — it is more useful as a claim-construction lever than as an invalidity ground.

Claim 5 adds the only truly distinctive-sounding limitation in the family: the internal firewall management component determines authorization "independently of a firewall external to the NAD," and "at least some of the plurality of requests originate from within the network without passing through the firewall." Claim 12 and 22 carry the same "originates one of within and external to the network" language. This is the insider-threat limitation, and it is the one the obviousness case must address most carefully.

---

3. The differences over the art, stated narrowly

Once the intended-use preamble is stripped out, the difference between claim 1 and the pre‑1998 art is essentially:

(i) placing the packet‑filtering/proxy admission-control function on the node that serves the attached peripheral device rather than only on the perimeter bastion host, and (ii) doing so for requests that may originate inside the LAN.

Both halves of that difference are directly taught. Colly '014 expressly claims a "firewall box … for protecting a network element from access over a network to which the network element is attached," with proxy agents that (a) are "assigned … in accordance with a port number," (b) "verif[y] that a source address … comports with a list of authorized … addresses," and (c) discard packets whose source is a node behind the firewall (source-routing elimination — the "route of the data packet" element). Colly's protected element can be any server, including the internal E‑mail system 320 of its FIG. 3. Sony '337 supplies a network server fronting optical mass‑storage devices — the exact NAD taxonomy the '302 lists ("CD‑ROM drives, DVD drives, optical drives …").

That is the whole case. Below I present it as six discrete combinations, with the KSR rationale for each.

---

4. Combinations that render the claims obvious

Combination A — Colly '014 + Sony '337 (+ 3Com '176 for L5)

Targets: claims 1, 5, 10, 11, 12, 22, 23, 25, 29, 30

Motivation to combine. (1) Colly's stated purpose — protecting a network element rather than an entire enclave — is precisely the '302's stated purpose, so the fields are the same and the reference is "reasonably pertinent." (2) Substituting the generic protected server of Colly with the already‑known, already‑networked peripheral server of Sony is a mere substitution of one known element for another, obtaining predictable results (KSR, rationale (B)). (3) Colly itself supplies a design incentive for dedicating security to the resource: its specification warns that a firewall host bundled with other applications (the SendMail example) exposes source/destination information to attackers. (4) Sony shows the peripheral server "ready for improvement" (KSR rationale (D)) — it already fronts multiple clients and devices and has no access control.

Anticipation note: Colly's claims 1–4 and 9–10 read very close to claim 1 alone; a §102 challenge keyed on Colly is worth evaluating if claim 1 is construed with the preamble as non‑limiting.

---

Combination B — Milkyway '601 + GB '031 + IBM '475 + Sony '337

Targets: claims 1, 4, 5, 6, 9, 10, 13, 16, 17, 22, 28

Motivation to combine. All four references address the same problem (controlling which external requests may reach an internal resource) and come from the same 1994–1998 firewall design literature. GB '031 and Milkyway '601 are explicitly complementary in the art's own framing — Milkyway's background criticizes non‑transparent application gateways for their per‑service overhead, while GB '031 provides the generic rule‑driven proxy relay that solves it. A PHOSITA designing a device server for a heterogeneous LAN in 1998 would consult this literature as a body (KSR: "the combination of familiar elements according to known methods is likely to be obvious when it does no more than yield predictable results"). IBM '475 supplies the rules‑administration component, and coupling a validated rule base to a proxy is a routine engineering step.

---

Combination C — ITT '209 + 3Com '176 + Internet Dynamics '027

Targets: the insider/threat-model limitations of claim 5 and the L5 "second layer" language of claims 1 and 22

Motivation to combine. The '302's own Background concedes that a bastion firewall is unidirectional and that "once a bastion firewall is penetrated, … the user typically gains unrestricted access to all resources of the LAN, including any NADs." That concession is the design incentive, and it is the applicant's own. ITT '209 demonstrates that multi‑level access control inside a network was a known technique; 3Com '176 demonstrates that layering firewall functionality was known; Internet Dynamics '027 supplies the reason to move the check to the resource (avoiding redundant filters). Using a known technique (ITT's intra‑network multi‑level control) to improve a similar device (an enclave perimeter) is KSR rationale (C). The only remaining gap — "independently of a firewall external to the NAD" — is met by the fact that ITT‑type controls operate on internal traffic that never reaches the perimeter.

---

Combination D — TI '547 / StorageTek '526 / Ricoh '093 + Colly '014

Targets: claims 12, 20, 21, 23, 24, 29 (apparatus + SCSI + device types)

Motivation to combine. Claim 12 is a generic computing platform claim; its only distinguishing element is that the admission-control instructions run on the node that also hosts a directly attached device interface. TI '547 discloses exactly that architecture (network interface + local disk + transceiver in one node), and Colly '014 supplies the admission-control instructions. A PHOSITA integrating a proxy/filter into an existing network-attached appliance is doing nothing more than adding a known security function to a known appliance — the epitome of an obvious combination, and one that yields only predictable results.

---

Combination E — Abirnet '015 / Content Advisor '618 + Sony '337

Targets: claim 26 (logging) and claim 24 (SCSI device management)

Abirnet US 5,958,015 A discloses a network session wall that passively listens to a communication session using access rules and stops further communication (monitoring/auditing all sessions); Content Advisor US 6,233,618 B1 discloses "access control of networked data" with rule enforcement. The '302's own specification (FIG. 6, step 612) describes writing discard reasons to a log file — and identifies the purpose as periodic security review. Claim 26's "means for logging each request that is determined to be allowed" is a routine audit‑trail feature that was standard in the 1996–1998 firewall art. Logging is a classic "non‑technical, ancillary" feature that does not confer patentability where the underlying filtering is old.

---

Combination F — Microsoft '507 + Nomadix '892 + Secure Computing '336

Targets: claims 2, 3, 18, 19, 27 (heterogeneous protocols / distributed modules)

Motivation to combine. Supporting multiple client OS protocols on one resource server was a defining requirement of the mid‑1990s LAN appliance market (Sony '337's optical server and Fuji Xerox '670's network server both contemplate heterogeneous clients). IBM '797's two‑segment tunneling application literally discloses the "distributed program modules" of claim 3. These are implementation refinements, not inventive contributions.

---

5. Claim‑by‑claim disposition summary

---

6. §103 motivations, generalized

A PHOSITA at 1998‑09‑01 was a network systems engineer with 3–5 years' experience in TCP/IP LAN administration and firewall deployment, familiar with the Check Point / Milkyway / Secure Computing / Raptor product literature and with the Cheswick & Bellovin, "Firewalls and Internet Security" (1994) monograph that several of the cited references themselves cite.

Four KSR rationales apply to nearly every combination above:

1. (A) Known elements combined by known methods → predictable result. Packet filtering on source/destination IP and port, with default‑deny and logging, was the canonical firewall design by 1995. Applying it to a resource server instead of a perimeter host is a change in location, not in kind.
2. (C)/(D) Known technique, ready for improvement. The '302's own Background frames the improvement: bastion firewalls are unidirectional and NAD servers "are not equipped with a second layer of security." A design incentive stated in the applicant's own specification can supply the motivation.
3. (F) Design incentive from the art's own criticisms. Colly criticizes bundled‑application firewalls; Milkyway criticizes non‑transparent gateways; GB '031 addresses generic relay. The literature was actively steering designers toward rule‑driven, resource‑proximate filtering.
4. Classification evidence of recognized category. The '302 faces H04L 63/0218 — "Distributed architectures, e.g. distributed firewalls" and H04L 63/0281 — "Proxies." The existence of an established classification for distributed (non‑perimeter) firewall architectures is objective evidence that the concept was a recognized, populated design space by the relevant date — the opposite of an unexpected breakthrough.

---

7. Counter‑arguments the patent owner will raise

I do not want to overstate certainty. The following are genuine vulnerabilities in the obviousness case:

1. The insider‑threat limitation of claim 5 is the strongest non‑obviousness argument. Colly's FIG. 3 architecture is outward‑facing; ITT '209 is a multi‑level‑security system with a different flavor (MAC/label‑based) than the header‑field filtering claimed. A patent owner will argue the cited art does not teach or suggest that the majority of a device server's traffic is intra‑LAN and never traverses the perimeter. The counter is the combination C motivation — but this is where a defendant should expect the fight.
2. Colly's firewall box is "stand‑alone" and dedicated ("No other applications … other than those related to support of the firewall application"). Claim 1 arguably requires the filtering instructions on the NAD server itself, which also runs the data‑management component. The FIG. 7 proxy embodiment of the '302 narrows this somewhat (the proxy NAD server 110A generates new packets for the NAD server 110B), but the specification's FIG. 1 direct‑access embodiment is the one most at risk under the combination, and Colly cuts the other way (away from co‑locating a general‑purpose application host with the firewall). A defendant relying on Colly should pair it with Sony '337 or TI '547 so that the server is the protected node.
3. "Route of the data packet" is vague. If construed broadly (source‑routing options), Colly's source‑routing elimination covers it; if construed as network‑layer path/route‑table information, the mapping is less clean and US 6,009,475 becomes important.
4. Drafting defects cut both ways. The antecedent mismatch in claim 1 ("the NAD being further configured to filter") could be argued as indefinite or, conversely, as merely a typographical error correctable by reference to the specification. Do not build the case on it.
5. Secondary considerations are largely unevidenced. The family has been litigated — Unified Patents records cases in E.D. Tex. (2:18‑cv‑00270), N.D. Ga. (1:19‑cv‑03199), N.D. Cal. (3:18‑cv‑06502 and 3:19‑cv‑00798), and S.D.N.Y. (1:18‑cv‑05564), asserted by Firenet Technologies LLC (current assignee) against KEMP Technologies. Assertion is not evidence of non‑obviousness, but a well‑funded defendant should anticipate a nexus/commercial‑success narrative. On the record before me there is no evidence of long‑felt need, failure of others, copying, or industry praise.
6. Third‑party validity scoring supports the challenge but is not authority. A Limestone validity report for US 7,739,302 ranks US 6,321,336 B1 (1.295), EP 1 042 744 A2 (1.251), EP 0 895 684 A2 (1.220), US 5,898,784 A (1.194), and US 5,826,014 A (1.192) as the closest art. That is independent corroboration that Colly '014 is the pivot reference — but note that EP 1 042 744 A2 (remote access‑controlled communication, Sun, prio. 1997‑09‑12) and EP 0 895 684 A2 (internet protocol filter, Nortel, prio. 1996‑04‑24) are not on the patent's face and would require a separate availability check (§102(e) foreign‑publication dates differ). Source: http://s3.amazonaws.com/report.limestoneip.com/9MBZuq8Ezs5v7FFaH-IFHo.full.html

---

8. What I could and could not verify

Verified (via live retrieval today): claim sets and abstracts of US 6,317,837 B1, US 5,623,601 A, GB 2 318 031 A, US 6,061,797 A, US 5,826,014 A, and corroborating prosecution/assignment metadata. URLs:

• https://patents.google.com/patent/[US5826014A](/patent/US5826014A)
• https://patents.google.com/patent/[US5623601A](/patent/US5623601A)
• https://patents.google.com/patent/GB2318031A
• https://patents.google.com/patent/[US6061797A](/patent/US6061797A)
• https://patents.google.com/patent/US6317837
• https://www.freepatentsonline.com/[5826014](/patent/5826014).html
• https://portal.unifiedpatents.com/patents/patent/US-[6317837](/patent/6317837)-B1 (litigation/assignee lineage)
• https://portal.unifiedpatents.com/litigation/Georgia%20Northern%20District%20Court/case/1%3A19-cv-03199

Not verified / caveats:

• The file wrapper of the '302 (and of the parent '837) — I did not review the examiner's rejections, the claim amendments adding "IP address in a header" and "route," or any §103 arguments traversed. The narrowing addition of those terms suggests the examiner did raise art of the Colly/Milkyway type; if so, prosecution history estoppel will constrain the patent owner's ability to broaden on infringement, and the precise reasons for allowance could reveal the gap the applicant successfully exploited.
• Several references' 102(e) dates are inferred from the filing dates shown on the page rather than confirmed from certified copies.
• I could not complete verification of US 5,968,176, US 6,009,475, and US 6,233,618 due to a tool‑call limit; their characterizations above rely on their titles and on consistent secondary descriptions (e.g., the Limestone report lists US 5,968,176 among firewalls cited in this space). Treat those three as provisional and confirm before relying on them in a written opinion.

---

9. Bottom line

Claim 1 is highly likely obvious, and I would rate the risk of invalidity as substantial. The claim's operative content — an interposed node filtering access requests to a network‑attached peripheral on the basis of packet‑header IP information, default‑deny — is squarely disclosed by US 5,826,014 (Colly) read with US 5,642,337 (Sony), with the dedicated second layer supplied by US 5,968,176 (3Com). The "in addition to any protection afforded by a firewall" clause is intended‑use language that supplies no structural distinction. The disjunctive "at least one of" header limitation further collapses the claim onto ordinary packet filtering.

Claim 5 is the lone defensible redoubt. Its "requests originate from within the network without passing through the firewall / independently of a firewall external to the NAD" language captures the insider‑threat scenario, and the best available art (ITT '209, 3Com '176, Internet Dynamics '027) teaches the concept of intra‑network access control without cleanly teaching its relocation to a device server as a second layer. A well‑constructed obviousness case can reach it (Combination C), but this is where an IPR petitioner should concentrate its expert declaration and where the patent owner will concentrate its rebuttal.