US 7194554

I'll verify the patent against live sources before summarizing.

Let me check for any recent (2025–2026) litigation or appellate activity involving this patent.

US Patent 7,194,554 — Verification Summary

Sources consulted: the authoritative full text supplied for US7194554B1 (Google Patents), uspto.report/patent/grant/7,194,554, plus live web searches. I did not reach the USPTO PatentCenter/PAIR record or the CAFC docket system directly, so issuance details are corroborated from two independent reproductions of the front-page data rather than from a primary USPTO feed. No search result returned a similar-but-different patent number in a way that would affect this record.

Bibliographic data

Assignee note (uncertainty flagged): Google Patents lists the current assignee as Gate Worldwide Holdings LLC, while the assignment chain in the same record shows a Nov. 22, 2019 quitclaim from Gate Worldwide Holdings LLC back to Nomadix, Inc., and uspto.report lists the assignee as Nomadix, Inc. I therefore cannot state with high confidence who the recorded owner is today; the assignment record should be checked in USPTO Assignment Search. (There are also 2015/2017 security interests to NTT DOCOMO and a 2019 security interest to Knobbe, Martens, Olson & Bear, released May 28, 2019.) uspto.report also notes a Certificate of Correction, which I have not reviewed.

Litigation / CAFC 2026 check: The Google Patents record lists three U.S. District Court, California Central District Court cases — 2:09-cv-08441, 2:10-cv-00381, and 2:19-cv-10202 — plus related historical Nomadix/IPE Networks and IP3 Networks actions (S.D. Cal. 04 CV 1485). I found no Federal Circuit docket, 2026 or otherwise, naming 7,194,554 or Nomadix. My CAFC-targeted searches returned unrelated 2026 appeals (e.g., Oasis Tooling v. Siemens, No. 2026-* series; Contour IP Holding v. GoPro, No. 2026-2012). Given the patent expired March 17, 2021, active 2026 appellate activity over this patent is unlikely, but I cannot rule it out from public search alone — treat "no 2026 CAFC docket" as unconfirmed rather than established.

Abstract (verbatim)

"Systems and methods for selectably controlling and customizing source access to a network, where the source is associated with a source computer, and wherein the source computer has transparent access to the network via a gateway device and no configuration software need be installed on the source computer to access the network. A user may be prevented access from a particular destination or site based upon the user's authorization while being permitted to access to other sites that the method and system deems accessible. The method and system can identify a source without that source's knowledge, and can access customizable access rights corresponding to that source in a source profile database. The source profile database can be a remote authentication dial-in user service (RADIUS) or a lightweight directory access protocol (LDAP) database. The method and system use source profiles within the source profile database to dynamically authorize source access to networks and destinations via networks."

Independent claims in plain language

Claim 1 — Method of selectably controlling/customizing source access (the core AAA method).
A method where a computer accesses a network through a gateway device with zero client-side configuration — the gateway "enables the source computer to access any network regardless of network configurations via a packet translation learned during a self configuration," and no configuration software is installed on the source computer. The method has four steps:

1. The gateway receives a request from the source computer for network access;
2. The gateway identifies an attribute associated with the source from a packet the source computer sent;
3. The gateway accesses a source profile in a source profile database located external to the gateway device, the profile being looked up by that attribute; and
4. The system determines the source's access rights from the source profile — i.e., what the source is permitted to reach on the network.

So: transparent, no-client-software access control, with per-source authorization decided from an externally hosted profile database keyed on a packet attribute.

Claim 10 — System for selectably controlling/customizing source access (apparatus counterpart).
A system with three cooperating elements: (a) a gateway device that receives the access request and provides config-free, network-agnostic access via a packet translation learned during self configuration; (b) a source profile database external to the gateway storing access information identifiable by an attribute derived from a packet sent by the source computer; and (c) an AAA (Authentication, Authorization and Accounting) server in communication with both, which determines whether the source is entitled to access the network and what its access rights are for reaching destination sites.

Claim 17 — Method for redirecting a source attempting to access a destination through a gateway device.
A method where the gateway again provides config-free, network-agnostic access via a self-configuration-learned packet translation, without requiring network-specific software on the source computer. The method:

1. Receives the source's request for network access;
2. Identifies the source by an attribute;
3. Accesses a source profile database external to the gateway holding the source's access rights;
4. Determines those access rights (defining which destination sites the source may reach); and
5. Directs the source to a redirection site when no source profile for it is found in the database — i.e., the unknown-user (captive-portal/redirect) case is a positive limitation of this independent claim, not merely a dependent option.

Dependent-claim notes: Claim 2 (destination-specific rights), 3 (location identifier as the attribute), 4/5 (RADIUS / LDAP), 6 (database updated for new sources), 7 (historical access log), 8 (MAC address, User ID, or VLAN ID), 9 (receiving a destination address); claims 11–16 (VLAN ID/circuit ID/MAC address; RADIUS; LDAP; multiple source profiles; per-profile historical duration data for billing; database within the AAA server); claims 18–24 (RADIUS/LDAP, location identifier, database update, separate accounting database with historical log, destination address).

Drafting artifact to note (do not auto-correct): Claim 24 depends from claim 19 but recites "determining if the source computer is entitled to access the destination address…" — language that appears in the specification's summary but is not recited in claim 19. As issued, that dependency is textually disjointed; I flag it rather than silently harmonizing it. The record also shows a Certificate of Correction on this patent, which may bear on claim text.

Caveats on confidence

• High confidence: title, inventors, application number, filing date, issue date, 24 claims and their text, abstract, expiration/adjusted-expiration date, and the three California district court case numbers — all from the authoritative full text plus a second reproduction.
• Lower confidence: (1) current recorded assignee (Gate Worldwide Holdings LLC vs. Nomadix, Inc. conflict described above); (2) whether any Certificate of Correction altered claim wording; (3) absence of 2026 CAFC activity — I could not query the CAFC docket directly, so this is an absence of evidence in search results, not proof of absence.

I'll research litigation involving US 7,194,554 using multiple sources.

Let me search for the other specific district court cases and any recent litigation.

Let me gather more detail on the specific cases and check for any additional litigation.

Litigation Involving U.S. Patent No. 7,194,554

Scope note. I searched for the literal number 7194554 only. Several searches returned hits for the unrelated patent US 5,894,554 (Parallel Networks/Oracle, dynamic web page generation) and US 6,554,995/'554-type shorthand — those are not US 7,194,554 and I have excluded them, as instructed.

The '554 patent ("Systems and methods for providing dynamic network authorization authentication and accounting," Nomadix, Inc.; filed 2000-10-20; granted 2007-03-20; priority 1998-12-08) is now expired (expiration adjusted to 2021-03-17), so no new litigation can be filed asserting it. All known suits are historic.

1. Nomadix, Inc. v. Hewlett-Packard Company, et al.

Key developments

• Claim construction (Dkt. 458): The court construed terms of the '554 patent, including the "determining the access rights of the source based upon the identification of the source…" limitation found in claims 10 and 17. Nomadix proposed "no construction necessary"; Defendants urged a narrowing construction requiring access rights to be based on both source identity and content/destination requested. The court agreed with Nomadix and held no construction necessary, also rejecting Defendants' proposed ordering of steps. (See the order text reproduced at https://docs.justia.com/cases/federal/district-courts/california/cacdce/2:2009cv08441/[459068/458](https://assignmentcenter.uspto.gov/search/patent/reelFrameDetail?reelFrame=459068-0458) and https://app.midpage.ai/document/nomadix-inc-v-hewlett-packard-1000000895881.)
• Invalidity/motions (Dkt. 807, March 22, 2012): Defendants moved to supplement invalidity contentions to assert that the '118 patent (Ip3/Networks-style reference) and the SPINACH/Vos prior art invalidated the '554 and '399 patents (previously asserted only against the '894 and '716 patents). Judge Pregerson denied the motion for lack of diligence. (https://law.justia.com/cases/federal/district-courts/california/cacdce/2:2009cv08441/[459068/807](https://assignmentcenter.uspto.gov/search/patent/reelFrameDetail?reelFrame=459068-0807)/)
• Standing (Dkt. 715, May 7, 2012): Defendants moved to dismiss for lack of subject-matter jurisdiction, arguing the University of California co-owned the patents. The court denied the motion, finding an assignment presumptively vested legal title in Nomadix and that joinder of UC was not required. (https://cases.justia.com/federal/district-courts/california/cacdce/2:2009cv08441/[459068/965](https://assignmentcenter.uspto.gov/search/patent/reelFrameDetail?reelFrame=459068-0965)/0.pdf)

Outcome / status: The case proceeded through claim construction, invalidity practice and trial-stage discovery. I could not verify the final judgment or settlement disposition from the sources retrieved; I am not aware of a public appellate decision in this docket. Treat the ultimate outcome as unconfirmed.

2. Nomadix, Inc. v. Solutioninc Technologies Limited

Key developments

• Consolidated with 2:09-cv-08441 for pre-trial purposes (Solutioninc's opposition at http://www.jafarilawgroup.com/wp-content/themes/ts_child/images/pdf/solutionInc-opp-to-ex-parte-application-043012.pdf refers to itself as "the consolidated companion case number 2:09-cv-08441-DDP-VBK").
• iBAHN counterclaims: iBAHN Corporation counterclaimed in this case asserting its own network-access patents ('754, '073, '376, etc.) against Nomadix, producing the reported Markman decision, Nomadix, Inc. v. Hewlett-Packard Co., 2011 Markman 5037162 / 2011 WL (C.D. Cal. Oct. 24, 2011), which addressed both Nomadix's and iBAHN's terms. (Summary: https://www.studicata.com/summaries/united-states-district-court-central-district-of-california/nomadix-inc-v-solutioninc-techs-limited-2011-figyaw/)
• File-history citation confirms the '554 written description was cited against later Nomadix family members in this litigation (see US 8,266,266 and US 9,548,935 file wrappers referencing "Complaint filed Jan. 19, 2010, Nomadix, Inc. vs. SolutionInc Technologies Ltd., No. CV10-0381 (C.D. Cal. 2010)").

Outcome / status: Unconfirmed. The dockets show extensive pre-trial activity through 2012 but I did not retrieve a final judgment, consent judgment or dismissal order. Stanford's NPE database classifies Nomadix as a "Practicing Entity / Product company," not an NPE (https://npe.law.stanford.edu/case/[143905](/patent/143905)).

3. Nomadix, Inc. v. SIA Mikrotikls, et al.

Key developments

• Claim construction (Dkt. 146/147, March 8, 2023): The court construed five asserted patents. It resolved most terms by stipulation, expressly adopting the earlier HP order (Nomadix v. Hewlett-Packard, CV09-08441, Dkt. 458) for overlapping subject matter. One term remained in dispute (relating to the '727 patent's "incorrectly configured messages"), where the court found no construction necessary and rejected MikroTik's narrowing proposal. (https://www.courtlistener.com/docket/16536918/147/nomadix-inc-v-sia-mikrotikls/authorities/ ; https://www.cetient.com/case/nomadix-inc-v-sia-mikrotikls-[9516034](/patent/9516034))
• Case was actively litigated into 2023: scheduling orders (Dkt. 93-1, 100, 101, 103, 149, 163), protective orders, a supplemental protective order, and an October 31, 2022 hearing transcript.

Outcome / status: Dismissed. On July 25, 2023, the parties filed a Joint Stipulation to Dismiss Case pursuant to FRCP 41(a)(1)(A)(ii) (Dkt. 168, by Nomadix counsel Mehran Arjomand of Morrison & Foerster LLP), and a "Report of Determination of Patent/Trademark Action (CLOSE) (AO 120)" was entered closing the case. The stipulation language indicates a settlement/license-type resolution, though the terms are not public. (https://www.docketalarm.com/cases/California_Central_District_Court/2--19-cv-10202/Nomadix_Inc._v._SIA_Mikrotikls_et_al/)

Cases that did not involve the '554 patent (negative findings worth noting)

Because these are frequently conflated with the '554 family, I checked them:

• Nomadix, Inc. v. IP3 Networks, Inc., No. 04 CV 1485 BTM (S.D. Cal., filed Oct. 2004) — predates issuance of the '554 patent (2007); asserted '892, '727, '894, '009, '399.
• Nomadix, Inc. v. Second Rule LLC, No. CV 07-1946 (C.D. Cal.) — pre-dates full '554 assertion; no retrieved record confirms '554 was asserted.
• Nomadix, Inc. v. Hospitality Core Services LLC d/b/a Blueprint RF, No. CV 14-08256 DDP (VBKx) (C.D. Cal.) — the patents in suit were '894, '399, '246, '266, '269, '806, '690; the '554 is not among them.
• Linksmart Wireless Technology, LLC v. T-Mobile USA, et al. (E.D. Tex. 2008–2010) — Nomadix was a third-party defendant (indemnity/contract), not a '554 infringement plaintiff.

Bottom line

1. Three district court actions are known to have put U.S. 7,194,554 at issue, all in the Central District of California before Judge Dean D. Pregerson: 2:09-cv-08441 (HP/Wayport/iBAHN), 2:10-cv-00381 (Solutioninc, consolidated with the former), and 2:19-cv-10202 (SIA Mikrotīkls et al.).
2. The only verified disposition among them is 2:19-cv-10202, dismissed by joint stipulation under FRCP 41(a)(1)(A)(ii) on July 25, 2023.
3. The '554 claim construction from the HP case (Dkt. 458) was expressly adopted by stipulation in the 2023 MikroTik order — making it the operative construction of the '554 claims in both litigations.
4. I could not verify final judgments or settlement amounts in the 2009/2010 cases, and I found no CAFC appeal (and no IPR/PGR at the PTAB) squarely involving U.S. 7,194,554 in the retrieved sources. I would not assert those outcomes without pulling the closing dockets from PACER via the C.D. Cal. case numbers above.

Caveat on identifiers: I have reproduced case numbers, patent numbers and docket citations exactly as returned by the sources. If any digit appears transposed (e.g., the "CV10-0381" vs. "2:10-cv-00381" shorthand), that reflects the source document, not my correction.

I'll start by verifying the structured data against live sources.

Let me check for any AIA trial proceedings specifically targeting 7194554.

Let me specifically probe for any IPR/CBM number naming this patent.

Proceedings overview

Total AIA trial proceedings on US 7,194,554: zero. The USPTO Open Data Portal structured block returns no IPR, PGR, or CBM proceedings for this patent, and my web searches (PTAB E2E / PTActs dockets, IPWatchdog, CourtListener, litigation reporting) surfaced no petition, institution decision, or final written decision naming US 7,194,554 as the challenged patent — the breakdown by status is therefore 0 active / 0 claims invalidated / 0 claims sustained / 0 settled / 0 institution-denied, which means the patent has never been stress-tested at the PTAB, no claim has been canceled or confirmed by the Board, and no § 315(e)(2) estoppel exists against anyone — a defendant today can raise any prior-art ground, with no estoppel ceiling, but also gets no free win from a canceled claim.

The single web hit that appears to reference a "'554 patent" (an Apple petition citing earlier IPR2019-01172, IPR2019-01319, and IPR2020-00675 against "the '554 patent") is almost certainly a different patent and I am flagging it as unverified, not as a proceeding on this patent — see the flag below.

No proceedings to report

There is no {PROCEEDING_NUMBER} — {Petitioner} v. {Patent Owner} entry to write for US 7,194,554. Per the operating rules, I will not invent one. What follows is what the record does show, and what I could not confirm.

What the Nomadix PTAB activity in the record actually targets (different patents):

• Guest-Tek's 2017–2018 IPR campaign (e.g., IPR2018-00376, IPR2018-00392, IPR2018-01660) challenged US 8,266,266 and US 8,725,899 — continuation/family members, not the '554. Guest-Tek's follow-on IPR2018-01660 (Decision 2019-04-16) was denied institution on General Plastic grounds after a prior petition on the same claims of the '899 patent was denied.
• Hospitality Core Servs., LLC v. Nomadix, Inc., IPR2016-00077 appears in a Guest-Tek exhibit list as a Nomadix-family petition; I could not verify which Nomadix patent it targeted, so I do not attribute it to the '554.
• The Ninth Circuit affirmed a permanent injunction barring Guest-Tek from filing PTAB petitions against Nomadix patents at all, because its 2010 license agreement's forum-selection clause was breached by the IPR filings (Nomadix, Inc. v. Guest-Tek Interactive Ent. Ltd., Nos. 20-56008 / 20-56009, 2021-09-03, https://www.courtlistener.com/opinion/[5090920](/patent/5090920)/nomadix-inc-v-guest-tek-interactive/). The court vacated the portion of the $1,099,310 fee award covering PTAB fees.

⚠️ Unverified flag — do not rely on this as a proceeding on the '554

A February 2025 petition hosted on PTActs (ptacts.uspto.gov/ptacts/public-informations/petitions/1548464) states:

"IPR petitions were previously filed against the '554 patent in IPR2019-01172 (6/12/2019), IPR2019-01319 (7/18/2019), and IPR2020-00675 (3/2/2020) by different petitioners, separately and independent of Apple. These proceedings were terminated due to settlement and are no longer pending."

Why I am not reporting these as proceedings on US 7,194,554: the same document's substantive analysis turns on the references Numazawa, Gu, Fukiharu, and Giel and on claim elements such as a "detecting means" that "detects whether an object is proximate" and a CPU that "reduces power to the displaying means" — i.e., a mobile-terminal proximity/display-power patent. That subject matter is facially inconsistent with US 7,194,554, which claims gateway-based Authentication, Authorization and Accounting (RADIUS/LDAP source-profile lookups, MAC/VLAN/circuit-ID attributes, redirection of unauthenticated sources). The correct reading is that this petition's "'554 patent" is a different patent whose number happens to end in 554 (e.g., a 9,xxx,554 or 10,xxx,554), being described in the customary shorthand.

Action item: before citing anything here, pull the caption and patent number from the face of the IPR2019-01172 / IPR2019-01319 / IPR2020-00675 Notices of Filing Date Accorded to Petition in PTAB E2E (https://ptacts.uspto.gov/ptabweb/). If — contrary to the art-based reading above — one of them is captioned against US 7,194,554, then three settled IPRs plus Apple's later petition exist and the analysis below changes materially. I could not complete that verification and will not guess.

Strategic summary

Claim status. All 24 claims of US 7,194,554 are UNTESTED at the PTAB. None are canceled; none are Board-sustained. The only adversarial narrowing on record is from district court claim construction, not an AIA trial: in the HP / Solutioninc matters (C.D. Cal. 2:09-cv-08441 and 2:10-cv-00381) and again in Nomadix v. SIA Mikrotikls (C.D. Cal. 2:19-cv-10202), the court construed "regardless of network configurations" (claims 1 and 17) as "regardless of network address settings" and held no construction necessary for "determining the access rights of the source based upon the identification of the source..." (claim 1) or "the source"/"the gateway device" (claims 1, 17). MikroTik's indefiniteness challenges to claims 1, 17, and 24 were withdrawn. Note the asymmetry: the '554's independent claims (1, 10, 17) and its system claim 10 have effectively zero adjudicated validity history, while the sibling patents Nomadix actually litigated heavily ('894, '399, '246, '995, '727) carry the claim-construction baggage.

Estoppel landscape. Because no IPR/PGR was ever instituted on the '554, § 315(e)(2) estoppel is entirely absent. A defendant asserted against the '554 today faces no bar on any § 102/§ 103 ground, no General Plastic follow-on risk of its own, and no need to work around a petitioner-privity chain — but it also cannot inherit anyone else's win, and there is no IPR record to leverage for a § 315(a)/(b) or Fintiv-style stay argument.

The dominating fact is expiration. Per the structured data, the '554 is "Expired – Lifetime," with an adjusted expiration of 2021-03-17. That means: (a) no injunctive relief; (b) no ongoing royalty; (c) any back-damages theory is capped by the § 286 six-year lookback, which from 2026-10-01 reaches back only to 2020-10-01 — i.e., a damages window of roughly 2020-10-01 through 2021-03-17, about five and a half months. Any assertion built on post-2021-03-17 conduct is a non-starter, and the troll/assertion economics are thin even on the surviving window.

Pattern signals. No petitioner has ever filed an IPR against the '554. Nomadix's PTAB exposure is concentrated in the Guest-Tek campaign against the '266 and '899 continuations, and Nomadix's most aggressive posture was offensive — suing to enjoin Guest-Tek from filing PTAB petitions at all, and winning that injunction on appeal. No defensive aggregator (Unified Patents, RPX, Unified's IPR fund) appears in the chain for this patent; the Unified Patents litigation portal entries are ordinary district-court docket records, not third-party challenges.

Recommended next steps

1. Confirm the zero count yourself before relying on it. Run the patent number through PTAB E2E (https://ptacts.uspto.gov/ptabweb/) and the PTAB Decisions search (https://www.uspto.gov/patents/ptab/decisions). The absence of any proceeding is the single most load-bearing fact in this memo.
2. Close out the "554" ambiguity. Retrieve the captions of IPR2019-01172, IPR2019-01319, and IPR2020-00675 from PTActs and confirm the challenged patent numbers. If they are not US 7,194,554, note in your file that the shorthand is a false positive. If any is, this memo must be rewritten around three settled IPRs (settlement terms are confidential; expect nothing usable) plus a live Apple petition with an institution decision to track.
3. Lead with expiration and § 286. Any demand letter citing US 7,194,554 should be met with: patent expired 2021-03-17 (https://patents.google.com/patent/US7194554/en); no injunctive or prospective relief available; damages reachable only for conduct in the ~2020-10-01 to 2021-03-17 window.
4. Verify standing before anything else. The structured data shows the patent was assigned to Gate Worldwide Holdings LLC on 2018-01-23 and quitclaimed back to Nomadix, Inc. on 2019-11-22, with Knobbe Martens' security interest released in between. A demand from Gate Worldwide Holdings, or from any entity that is not the current recorded owner, raises an immediate real-party-in-interest / standing question.
5. No § 315(b) clock is running (nothing to time-bar), and no estoppel constrains you — meaning if you do end up in an IPR or district court, your invalidity case on the '554 is unencumbered by anyone else's prior art choices.

Confidence statement: high confidence that no AIA trial proceeding targets US 7,194,554 as of the ODP ingest, based on the structured block plus multiple targeted searches; low confidence on the nature of the "554" references in the Apple petition chain, which I flag rather than assert. I could not retrieve a PTAB FWD, institution decision, or CAFC appeal specifically addressing US 7,194,554 because — on the evidence available to me — none exists.

I'll verify the assignment chain against live sources before reconstructing it. Note up front: my available tooling is web search only — I cannot query assignmentcenter.uspto.gov's underlying database directly, so I'll be explicit about which links are verified versus unverified.

Key ownership facts are surfacing (GWHSPV, LLC and Gate Worldwide Holdings LLC as parents). Let me dig for the actual reel/frame records and the corporate-history context.

Verification note before the findings

Tooling limitation, stated plainly. I could query only live web search — I could not reach the USPTO Assignment Center database (assignmentcenter.uspto.gov) or its legacy twin (assignment.uspto.gov) directly, and no indexed surface in my searches returned reel/frame numbers or recorded correspondents for US 7,194,554. The assignment events below therefore come from the USPTO-sourced assignment/reassignment events reproduced in the authoritative full text of the patent (the "reassignment" entries in the Google Patents legal-events record) plus one primary court record (the Dec. 2, 2019 Rule 7.1 certificate in Nomadix v. SIA Mikrotikls). Reel/frame and correspondent fields are marked "not retrieved" because they were unavailable to me — not because such records are absent. The Google Patents dates are, on that platform's conventions, generally recordation dates; execution dates were not available for any link. Anyone relying on this for a standing or ownership opinion must re-run it at the Assignment Center.

Inventors

Pattern note — a partial correction to the record. Nomadix's own complaint in Nomadix, Inc. v. SIA MikroTikls (C.D. Cal. 2:19-cv-10202, Am. Compl. ¶15) describes "Nomadix's founders, Dr. Leonard Kleinrock and Dr. Joel Short." Kleinrock is not a named inventor on the '554 patent and does not appear in its assignment chain. Do not carry the founder narrative over to this patent's inventorship — the '554 inventive entity is Short/Pagan/Goldstein. (Kleinrock appears on other Nomadix family members.)

Departure pattern: no finding, insufficient data. All three inventors assigned to Nomadix, and Short is still publicly identified as a Nomadix founder in 2019 pleadings. I have no evidence of any inventor departing within 12 months of filing, and I will not infer one — the "all inventors leave fast" tell is simply not testable from what I could reach.

Original assignee

Nomadix, Inc. — named on the issued patent (assignee of record via the 2001-01-22 inventor assignment).

• Primary line of business: network edge/guest-access gateways. Nomadix commercialized the Universal Subscriber Gateway (USG); the patent's own prior-art listing cites Nomadix product literature ("USG Product Timeline, Nomadix, Inc., 2701 Ocean Park Blvd., Suite 231, Santa Monica, California 90405" and "Universal Subscriber Gateway" — reproduced at freepatentsonline.com/7194554.html). This is the rare case where the asserted patent's specification cites the assignee's own shipped product, i.e. the assignee demonstrably shipped an embodiment of the claimed subject matter.
• Claim-embodying product: yes — the gateway/redirection products that the claims describe were Nomadix's core commercial line, and Nomadix sued competitors in that same product market (MikroTik routers, Solutioninc, Guest-Tek — all gateway vendors).
• Current status: operating, but now inside a holding structure. The Dec. 2, 2019 Certificate of Interested Parties filed by Nomadix in 2:19-cv-10202 identifies GWHSPV, LLC as parent of Nomadix, Inc., and Gate Worldwide Holdings LLC as parent of GWHSPV, LLC (docket at dockets.justia.com/docket/california/cacdce/2:2019cv10202/766115). Onscope lists Nomadix's parent entity as DOCOMO InterTouch Interactive Pte Ltd (onscope.com/ipowner/en/owner/profile/961383-nomadix-inc.html) — lower confidence, unverified against a filing, and in tension with the 2019 court record. No bankruptcy filing for Nomadix surfaced in any search.

Assignment timeline

Caveat: reel/frame and correspondent were not retrievable (see note above). Records are listed by the date carried in the USPTO-sourced event entry; where two entries share a date they are distinguished by conveyance.

• executed date not retrieved / recorded 2001-01-22 — Reel not retrieved/not retrieved

  • Conveyance: Assignment of assignors' interest
  • Assignor: Goldstein, Josh J.; Pagan, Florence C. I.; Short, Joel E.
  • Assignee: Nomadix, Inc.
  • Correspondent: not retrieved. (Contextual cross-reference: the patent's own front-page Attorney/Agent of Record is Knobbe, Martens, Olson & Bear, LLP, Irvine, CA, which is the prosecution correspondent, not a recording correspondent — the two should not be conflated.)
  • Context: Original inventor-to-company assignment; routine founder/employee conveyance.

• executed date not retrieved / recorded 2015-09-30 — Reel not retrieved/not retrieved

  • Conveyance: Security Interest
  • Assignor: Nomadix, Inc.
  • Assignee: NTT DOCOMO, INC.
  • Correspondent: not retrieved.
  • Context: Securitization — the patent pledged as collateral to the corporate parent/lender, not a transfer of title.

• executed date not retrieved / recorded 2017-08-29 — Reel not retrieved/not retrieved

  • Conveyance: Modification to Patent Security Agreement
  • Assignor: Nomadix, Inc.
  • Assignee: NTT DOCOMO, INC.
  • Correspondent: not retrieved.
  • Context: Amendment/extension of the 2015 collateral agreement — indicates the secured financing stayed outstanding for ~2 years.

• executed date not retrieved / recorded 2018-01-23 — Reel not retrieved/not retrieved

  • Conveyance: Assignment of Patent Security Agreement
  • Assignor: NTT DOCOMO, INC.
  • Assignee: GATE WORLDWIDE HOLDINGS LLC
  • Correspondent: not retrieved.
  • Context: Secured-party substitution — DOCOMO's collateral position transferred to Gate Worldwide Holdings, signaling DOCOMO was exiting the Nomadix credit relationship.

• executed date not retrieved / recorded 2018-01-23 — Reel not retrieved/not retrieved

  • Conveyance: Assignment of Assignors' Interest
  • Assignor: NOMADIX, INC.
  • Assignee: GATE WORLDWIDE HOLDINGS LLC
  • Correspondent: not retrieved.
  • Context: Title transfer out of the operating company into its (new) holding parent — coincides with the "developments with Gate Worldwide Holdings and the related New York action" that Guest-Tek cited when it withdrew from an amendment stipulation in Feb. 2018 (2:16-cv-08033, Order re Motion to Supplement, Dkt. 261). Note the two same-day 2018-01-23 records: DHHS-style financing and title moved to the same entity on the same day.

• executed date not retrieved / recorded 2019-03-20 — Reel not retrieved/not retrieved

  • Conveyance: Security Interest
  • Assignor: NOMADIX, INC.
  • Assignee: Knobbe, Martens, Olson & Bear, LLP
  • Correspondent: not retrieved. (Cross-reference: Knobbe Martens is simultaneously the patent's prosecution firm of record and Nomadix's litigation counsel in 2:19-cv-10202 — Douglas G. Muehlhauser and Perry D. Oldham, 2040 Main St., 14th Floor, Irvine, CA.)
  • Context: Distress tell — a law firm taking a security interest in the client's patent, i.e. a fee lien rather than any acquisition.

• executed date not retrieved / recorded 2019-05-28 — Reel not retrieved/not retrieved

  • Conveyance: Release by Secured Party
  • Assignor: Knobbe, Martens, Olson & Bear, LLP
  • Assignee: NOMADIX, INC.
  • Correspondent: not retrieved.
  • Context: Release of the two-month-old firm lien — the fee dispute/lien was cleared quickly.

• executed date not retrieved / recorded 2019-11-22 — Reel not retrieved/not retrieved

  • Conveyance: Quitclaim
  • Assignor: GATE WORLDWIDE HOLDINGS LLC
  • Assignee: NOMADIX, INC.
  • Correspondent: not retrieved.
  • Context: Title pushed back down into the operating entity 10 days before Nomadix filed suit on this patent (2:19-cv-10202, filed Dec. 2, 2019) — a clean pre-suit title-cleaning step.

Post-chain litigation events (not assignments, for context): claim construction order construing '554 claim 1 and claim 24 (2:19-cv-10202, Dkt. 147, Mar. 8, 2023); joint stipulation of dismissal under FRCP 41(a)(1)(A)(ii), July 25, 2023 (Dkt. 168). Patent expired/adjusted expiration 2021-03-17.

Timeline diagram

timeline
    title Ownership of US 7194554
    1999 : CIP application filed by Nomadix
    2000 : Application 09 693 060 filed
    2001 : Inventors assign to Nomadix Inc
    2007 : Patent 7194554 issued
    2015 : Nomadix grants security interest to NTT DOCOMO
    2017 : Security agreement modified with NTT DOCOMO
    2018 : DOCOMO secured interest assigned to Gate Worldwide Holdings
         : Nomadix assigns title to Gate Worldwide Holdings
    2019 : Knobbe Martens records security interest
         : Knobbe security interest released
         : Gate quitclaims title back to Nomadix
         : Nomadix sues MikroTik on the patent
    2021 : Patent expires
    2023 : MikroTik case dismissed

NPE / troll-pattern signals

1. Shell-entity transfer — unclear. Title did move out of Nomadix into GATE WORLDWIDE HOLDINGS LLC (recorded 2018-01-23) and back (quitclaim, 2019-11-22). "Holdings" is a name-suffix tell, but the entity is not a single-purpose patent shell: the 2019 court certificate shows it is the parent of GWHSPV, LLC, which is the parent of the still-operating Nomadix, Inc., and the recording shows it also took over DOCOMO's secured-lender position. No registered-agent address, single-member LLC registration, or product-less licensing posture was verified. I will not call this a shell on naming alone.

2. Known asserter in the chain — not present. No record surfaces Acacia, Marathon, IV, IPNav, Wi-LAN, Mosaid/Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, Document Generation Corp, or any Spangenberg entity. The opposite datapoint exists: Stanford's NPE Litigation Database classifies this patent's asserter, Nomadix, as category "8 Product company" (https://npe.law.stanford.edu/patent/7194554). I could not run the RPX Insurance or Unified Patents asserter directories directly, so treat "not present" as no list match found, not as a clear bill.

3. Repeat correspondent across the chain — unclear, and I want to be precise about why. I could not retrieve the recording correspondents for any link, so the recurrence test cannot be run as designed. What I can show is a firm recurring in a different capacity: Knobbe, Martens, Olson & Bear, LLP is (a) the patent's front-page Attorney/Agent of Record, (b) Nomadix's counsel in 2:19-cv-10202, and (c) the assignee in the 2019-03-20 security-interest record, released 2019-05-28. That is three touchpoints — but only one is a recorded assignment entry, and many reputable firms do both prosecution and NPE-side work. Not a finding of a shadow-NPE lawyer; flagged as a distressed-vendor lien.

4. Cascading transfers — present (moderate). Five recorded events within 22 months: 2018-01-23 (×2), 2019-03-20, 2019-05-28, 2019-11-22 — two of which land on the same day in the same assignee. All events after 2015 involve Nomadix, DOCOMO, Gate Worldwide Holdings, and Knobbe Martens, i.e. a closed set of related parties, which is the mild form of the tell (churn inside a family) rather than the severe form (chained unrelated LLCs sharing a correspondent address).

5. Pre-litigation transfer — present. Recorded 2019-11-22: quitclaim from Gate Worldwide Holdings LLC to Nomadix, Inc.; 2019-12-02: Nomadix files 2:19-cv-10202 naming 7,194,554 (per the AO-120 Report on the Filing of an Action, Dkt. 6). That is 10 days between the title move and the complaint — squarely inside the 6-month window, and consistent with arranging clean standing in the plaintiff's name before filing. (The 2021 expiry and 2023 dismissal mean this maneuver had no lasting assertion payoff.)

6. Bankruptcy fire-sale — not present. No Chapter 7/11 proceeding for Nomadix surfaced. The 2015–2018 DOCOMO security-interest sequence is a secured financing / secured-party substitution, not a bankruptcy sale.

7. Privateering — unclear. A large operating telecom (NTT DOCOMO) held a security interest, transferred that secured position to a holding vehicle in Jan. 2018, and the same vehicle took title the same day. That resembles a divestiture-then-assertion posture, but the plaintiff of record in every 2010s suit was Nomadix, Inc., the operating company that ships the accused-competitor-facing products — not a separate assertion vehicle. No SEC filing or Patent Progress/EFF coverage was located tying DOCOMO to assertions "on its behalf." Do not score this.

8. Defensive aggregator — not present. The chain terminates at Nomadix, Inc. (with Gate Worldwide Holdings LLC above it). No RPX, AST, LOT, Unified Patents, or OIN interest appears.

Verdict

Operating-company assertion.

Justification. The only post-issuance title movements are an intra-family churn: inventor assignment to Nomadix (recorded 2001-01-22), a Nomadix→NTT DOCOMO security interest (2015-09-30) modified in 2017, both the secured position and title moved to Gate Worldwide Holdings LLC (2018-01-23), a two-month law-firm fee lien and release (2019-03-20 / 2019-05-28), and a quitclaim back to Nomadix on 2019-11-22 — 10 days before the Dec. 2, 2019 MikroTik complaint; at every assertion the plaintiff was Nomadix, Inc., the company that shipped the Universal Subscriber Gateway cited in the patent's own prior-art listing and sued direct product competitors in that market, which is why Stanford's NPE Litigation Database tags this patent's asserter as "Product company" (https://npe.law.stanford.edu/patent/7194554). The NPE-verdict threshold is not met — there is no shell-entity LLC, no listed NPE assignee, and no bankruptcy sale — but two signals deserve monitoring rather than dismissal: the present pre-litigation transfer (2019-11-22 → 2:19-cv-10202) and the present multi-link churn cluster (five recorded events in 22 months, two on 2018-01-23), neither of which is explained by a simple "original assignee kept it" fact pattern.

This is an "insufficient data" caveat, not a clean bill: the verdict rests on assignment events and one primary court record, because reel/frame numbers and recorded correspondents were unreachable with my tools. Verify at the USPTO Assignment Center before relying on it:

• https://assignmentcenter.uspto.gov/
• https://assignment.uspto.gov/patent/index.html (search patent number 7194554)
• Cross-check: https://dockets.justia.com/docket/california/cacdce/2:2019cv10202/766115 (Rule 7.1 parent-entity chain) and https://npe.law.stanford.edu/patent/7194554 (asserter category).

I'll research this against live sources before producing the prior-art analysis.

Let me pull the patent's cited-references (front page) list and its forward citations.

I hit my tool-call budget, so I'll report exactly what the live sources returned — including an important gap I could not close — rather than fill it with invented citations.

Prior-Art Analysis — US Patent 7,194,554 B1

1. Record identification (the specific number, not a look-alike)

The searches returned the correct patent and no confusingly similar number (no 7,194,553 / 7,194,554-alike interfered with the record):

URLs: https://patents.google.com/patent/[US7194554B1](/patent/US7194554B1)/en · https://worldwide.espacenet.com/publicationDetails/biblio?CC=US&NR=[7194554B1](/patent/7194554B1)&KC=B1&FT=D · https://uspto.report/patent/grant/7,194,554

2. Critical caveat you need before using this analysis

The authoritative full text supplied for this patent does not contain the front-page "(56) References Cited" list. It contains the "Cited By (126)" list (patents that cite '554 forward), not the examiner/applicant backward citations that actually constitute prior art under §102.

And I could not retrieve the true backward-citation list (the examiner-cited U.S. patents, foreign patents, and NPL on the '554 front page) from a primary source within my search budget. My targeted queries for the '554 reference list returned the reference lists of other patents instead (e.g., US 10,339,841; US 10,510,536; an EPO search report — none of which are the '554 front page).

That distinction is decisive here:

• Backward citations ("References Cited") = the real §102/§103 prior art for '554.
• Forward citations ("Cited By") = NOT prior art to '554 — by definition they post-date it. Reporting them as "prior art that anticipates '554" would be an error of law.

I therefore give you (a) the forward list I can verify, correctly labeled as non-prior-art, and (b) the best available proxy for the real backward list — the reference list of US 7,689,716, the direct continuation of '554 (same specification, same family ID 37863956) — clearly flagged as a family proxy, not the '554 front page.

3. Forward citations ("Cited By") — verifiably on the '554 record

These are from the authoritative Google Patents "Cited By (126)" panel (the prompt's fetch truncated the list after the fifth entry). These are not §102 prior art to '554.

(List continues to 126 entries on the Google Patents page; I could not enumerate beyond the truncated fifth entry.)

4. Family-proxy backward references (US 7,689,716 — the '554 continuation)

Flagged: this is the reference list of a sibling, not of '554. It is highly probative because '716 shares '554's specification and claims priority to the same 1998-12-08 date, but the two front pages are not guaranteed identical.

Source: https://patents.justia.com/patent/[7689716](/patent/7689716)

Selected cited U.S. patents (dates as shown), with title-derived descriptions only:

Additional family-line references surfaced via the Unified Patents record for sibling US 8,266,269 (https://portal.unifiedpatents.com/patents/patent/[8266269](/patent/8266269)):

Reminder: the tables in §4 are family-level and title-derived. I did not verify that each appears on the '554 front page, and I did not read their specifications.

5. §102 anticipation assessment (hedged, because I lack the '554 front page)

§102 requires every element of a claim in a single reference. The pivotal limitation of independent claims 1, 10 and 17 is the combination of:

• (a) a gateway providing network-agnostic access "via a packet translation learned during a self configuration," with no configuration software on the source computer;
• (b) a source profile database located external to the gateway, keyed on a packet-derived attribute;
• (c) (claim 17 only) redirecting the source to a redirection site when no profile is found.

Most candidates above hit only one or two elements — which makes them §103 obviousness references more than §102 anticipatory references:

• US 6,219,786 B1 (monitoring/controlling network access, 1998-09-08) — closest on (b)/(e) if it discloses an external access-control database; strong §102 candidate vs. claims 7/10/15 (access control + monitoring/accounting), weaker vs. 1/17 absent the self-configuration packet translation.
• US 6,154,775 A (dynamic firewall rule processing) and US 5,848,233 A (dynamic packet filter assignment) — strong on per-packet/per-source authorization (element iii/e), §102 candidates vs. claims 2, 11, 24, but not the transparent-gateway element.
• US 5,835,061 A (Wayport, geographic-based service, 1995-06-05) — §102 candidate vs. claim 3 / claim 20 (location identifier as the attribute).
• US 5,852,812 and US 5,864,610 — §102 candidates vs. claims 7/15/22 (historical usage/accounting/billing) and possibly the AAA "accounting" function of claim 10.
• US 6,757,831 B2 (authenticated firewall tunneling, 1998-11-30) — authentication + tunneling; relevant to claim 10's "entitled to access" determination.
• US 5,859,974 / 5,856,974 address-mapping gateway — relevant to the "packet translation" element of claims 1/10/17, though not "learned during self configuration."
• RADIUS/LDAP references (e.g., RFC 2058/2138 and LDAP RFCs) — §102 candidates vs. claims 4, 5, 12, 13, 18, 19.

I cannot name a single reference I can confirm anticipates independent claim 1, 10, or 17, because I don't have the '554 front page and read none of these specifications. Treat the mappings above as hypotheses to verify against full texts.

6. The authoritative source for real '554 prior art (pointer, not content)

In the litigation, the defendants actually produced a claim-by-claim prior-art comparison against the '554 patent:

• Defendants' Supplemental Joint Invalidity Contentions, July 22, 2011, in Nomadix, Inc. v. Hewlett-Packard Co., No. 2:09-cv-08441 DDP (VBKx) and Nomadix, Inc. v. Solutioninc Technologies Ltd., No. 2:10-cv-00381 DDP (VBKx) (C.D. Cal.). Exhibit C5 = "Claim Comparison for U.S. Pat. No. 7,194,554" (18 pages), alongside Exhibits C1–C4 and C6–C7 mapping to U.S. Pat. Nos. 6,130,892; 7,088,727; 7,554,995; 6,636,894; 6,868,399; and 7,689,716. (Surfaced via the reference list reproduced in the file history of Nomadix's later US 10,341,243.)
• The same litigation's references list also names NPL pertinent to '554-adjacent claims: Hubbard et al., "Firewalling the Net," BT Technology Journal, Apr. 1997; Haverinen, "Improving User Privacy with Firewall Techniques on the Wireless LAN Access Point," PIMRC 2002; and the Devera "HTB Linux Queuing Discipline Manual" (2002).

Recommendation: obtain exhibits C5 and the 2011 Supplemental Joint Invalidity Contentions (via PACER for C.D. Cal. 2:09-cv-08441) and the '554 front page via USPTO PatentCenter — those are the primary sources that answer your question precisely; my §4 mapping is only a screened stand-in.

7. Confidence summary

• High: the patent's identity, dates, 24 claims, independent claims 1/10/17, and that the supplied record gives forward citations only; the five forward citations in §3; the litigation exhibit structure (C5 = '554) and case numbers.
• Medium: the family-proxy reference lists in §4 (they are '716 / sibling references, most likely but not confirmed to be on the '554 front page).
• Low / flagged: any specific §102 element-by-element mapping — explicitly hypothetical, because (i) I never obtained the '554 "(56) References Cited" list, and (ii) I read no reference specifications. No reference here should be cited as anticipating a '554 claim without a full-text, element-by-element check.
• Do not treat the §3 "Cited By" items as prior art to '554 — they are not.

I'll verify the prior art of record before analyzing. Let me search for the references cited on this patent and related litigation.

I have litigation context. Now let me pin down the actual prior art of record and the references named on the patent page.

Obviousness Analysis — US 7,194,554 B1 under 35 U.S.C. § 103

Analyst note / evidence flag (read first). The instruction was to use "the Prior Art section of this page." The page text supplied for US7194554B1 contains three things that could be called prior-art material, and only one of them is actually usable as § 102/§ 103 art:

The supplied excerpt was truncated before the front-page "(56) References Cited" section (the examiner/applicant-cited art), and my searches did not recover that list, so I could not verify the actual art of record. Everything below is therefore built from (a) references that are identifiable from the page and from the prosecution/litigation record I could confirm via search, and (b) the specification's own admissions. I flag confidence levels throughout and do not assert the contents of any reference I could not open.

1. Governing framework and the person of ordinary skill

• Law: Graham v. John Deere, 383 U.S. 1 (1966) (scope/content; differences; PHOSITA level; secondary considerations); KSR Int'l v. Teleflex, 550 U.S. 398 (2007) (expansive motivation rationales; predictable variation of known elements); In re Keller, 642 F.2d 413 (CCPA 1981) (test is what the combined teachings suggest, not bodily incorporation).
• PHOSITA (my construction): a person with a B.S. in EE/CS (or equivalent) and about 2–3 years of experience designing ISP/dial-access, firewall, or subscriber-management network equipment and the RADIUS/AAA stacks that go with them, as of the relevant priority date. This is a low-to-moderate skill level; the art was well-populated by 1998.
• Critical threshold — the priority date is contested and outcome-determinative. The '554 is a continuation-in-part of Ser. No. 09/458,569 (filed 1999-12-08), which claims benefit of provisional 60/111,497 (1998-12-08). Under pre-AIA § 102/§ 103, each claim is entitled only to the date of the disclosure that supports it. Claims (or limitations) supported only by new matter added in the 2000-10-20 CIP get a 2000-10-20 effective date, not 1998-12-08. I cannot resolve, from the page, which limitations are new matter — and this is itself a principal invalidity battleground. I therefore present the analysis for both readings, because the answer differs materially.

2. Qualifying prior art (what a § 103 case can actually stand on)

Important exclusion: the Nomadix family members (US 6,636,894; US 8,713,641) share the '554's inventive entity and are therefore presumptively unavailable as § 102(a)/(e) "by another" art. However, WO 98/40990 (PA-1) is a § 102(b) statutory-bar publication and is not disqualified by common inventorship — an inventor's own publication more than one year before filing is a bar. Whether it is § 102(b) art here again depends on the priority-date question in § 1.

3. Claim 1 (independent method claim) — element mapping and combinations

Combination 1 (primary): PA-1 + PA-2 [optionally + PA-6].

• PA-1 supplies every element of the "transparent, zero-client-configuration gateway" preamble and element (b) — the limitation the patentee will rely on hardest.
• PA-2 supplies elements (c)–(e) almost literally: RADIUS is an external AAA server with a user profile database, keyed by packet-supplied attributes, returning authorization and enforcing it.
• PA-6 supplies the per-destination (claim 2) flavor of "access rights."

Combination 2 (alternative primary): PA-4 (Vu) + PA-2 + PA-5. Vu gives the authenticating gateway + per-source destination control; PA-5 supplies transparency (no client reconfiguration); PA-2 supplies the external profile database and accounting.

Would a POSITA have combined these? Yes — see § 6 for the articulated rationales. The combination is the textbook KSR case: two complementary, well-understood subsystems (a transparent access gateway and the industry-standard AAA server) arranged in the only architecturally sensible way (AAA server behind/alongside the gateway, profiles external to it), yielding predictable results.

Anticipation vs. obviousness for the "self configuration" phrase. Note the Bristol-Myers-type risk for the patentee: the '554 specification defines this limitation by incorporation by reference to the earlier Gateway Device Application, i.e., the patent itself concedes the mechanism pre-existed the CIP. That is powerful § 103 evidence that element (b) is not the invention.

4. Claim 10 (independent system claim)

Claim 10 is the apparatus counterpart: (i) gateway + (ii) external source profile database + (iii) AAA server that determines entitlement and access rights.

• Element (iii) is essentially PA-2 (RADIUS) literally — a RADIUS server is an Authentication, Authorization and Accounting server.
• Element (ii) is PA-2/PA-3 (external server/directory).
• Element (i) is PA-1 or PA-4.

Combination: PA-1 + PA-2 (+ PA-3). Because the claim recites an "AAA server" as a named, known component, the obviousness case for claim 10 is stronger than for claim 1 — the claim appears to claim the mere juxtaposition of a known gateway and a known AAA server. Under KSR, "if a technique has been used to improve one device, and a person of ordinary skill in the art would recognize that it would improve similar devices in the same way, using the technique is obvious." Centralizing AAA behind a gateway for a multi-gateway deployment is exactly the motivation the patentee itself recites.

5. Claim 17 (independent redirect method claim)

Claim 17 adds the positive limitation: "directing the source to a redirection site when the source profile is not located within the source profile database."

• The pre-redirect elements track claims 1/10 (PA-1 + PA-2).
• The redirect-on-unknown-user step is the classic "captive portal" handshake. Two independent lines of support:
  1. Generic, well-known HTTP-redirect-to-login technique. Web-proxy and firewall authentication had for years intercepted an unauthenticated request and returned a login/redirect page (a standard "intercept-and-redirect" pattern). A POSITA would recognize this as a routine implementation choice once authorization is centralized in PA-2.
  2. Applicant's own disclosure (admitted art). The '554 specification repeatedly describes the home-page-redirect (HPR)/stack-address-translation (SAT) flow and incorporates by reference the Redirection Application (Ser. No. 09/458,569) and a concurrently filed redirect application. That incorporation is an admission that the redirection mechanism was separately developed, described elsewhere, and pre-existing relative to the CIP's new matter — good § 103 evidence for the redirect step.

Combination: PA-1 + PA-2 + known intercept-and-redirect technique (proxy/firewall login interception). Motivation: redirecting an unknown/unauthenticated source to a provisioning/login page is the natural way to let a gateway both deny access and offer a path to becoming authorized — exactly the three-outcome logic (access / pending / no access) the '554's Fig. 2 describes.

6. Dependent claims

Two flags for claim 24:

1. Drafting/scope defect (from the earlier section, restated because it bears on § 103): claim 24 depends from claim 19 (an LDAP dependent of claim 17) yet recites "determining if the source computer is entitled to access the destination address" — language that appears in the '554's summary but is not recited in claim 19. As issued, claim 24's antecedent basis is disjointed. A Certificate of Correction exists on this patent; I could not verify whether it changed claim 24. If claim 24 is construed by its literal text, its effective scope may collapse to the claim 17 + LDAP combination, making its denial limitation essentially a negative-claim accessory to already-known Access-Reject behavior.
2. Even taking claim 24 at face value, "deny access where the profile indicates denial" is the negative mirror of PA-2's Access-Reject — obvious.

7. Motivation to combine (KSR / MPEP § 2143 rationales)

A POSITA in 1998–2000 would have combined PA-1/PA-4 with PA-2/PA-3 for multiple, independently sufficient reasons:

1. Known technique for a known problem. RADIUS was the established mechanism for "authenticate the subscriber, return their rights, log their usage." The '554's Background concedes such subscriber databases existed and tracked usage/billing. Applying the known AAA framework to a gateway front-end is predictable.
2. Design incentive expressly articulated by the applicant. The '554's own specification states the motivation — an external, consolidated profile database (i) avoids per-gateway database maintenance across many gateways, (ii) eases administration, and (iii) lets an ISP/third party keep the data confidential. Under KSR and In re Kemps-type reasoning, the patentee's own stated objection/objective can supply the rational motivation.
3. Predictable result / combination of known elements. Gateway (PA-1/PA-4) + external AAA server (PA-2) is an aggregation of two known components, each performing its known function, with no unpredictable interaction.
4. Same field, common need. Both families target ISP/hospitality subscriber access; the problem (per-user, per-destination authorization with accounting, no client reconfiguration) was the recognized problem of the era — the '554's Background frames it as the "all-or-nothing" limitation of the prior art, i.e., an acknowledged design need.
5. Market/industry pull. Hotel/resort and multi-tenant networks needed centralized billing and outsourced AAA; the PMS-integration art (PA-8) and the outsourced-AAA model point the same direction.

8. Secondary considerations & patentee-side counterarguments

Patentee's likely rebuttals (weigh honestly):

• "No configuration software / regardless of network configuration" was arguably the novel core; if the claims are read to require the self-configuration packet-translation mechanism, and if PA-1/WO 98/40990 is excluded on priority grounds (see § 1/§ 9), the case weakens considerably. The patentee will argue WO 98/40990 and the family disclosures are not "by another" and/or fall outside the (earlier) critical date.
• Commercial success / copying: Nomadix built a substantial hospitality-Wi-Fi business; competitors (Blueprint RF, MikroTik) were accused of copying. This can support nonobviousness if a nexus is shown between the claimed combination and the success — but success here is plausibly attributable to Nomadix's sales/installation channel and the hospitality market, weakening nexus.
• Long-felt need: the "all-or-nothing" problem the Background frames is a real long-felt need — but the solution is a combination of known elements, which KSR discounts.

Bottom line on secondary considerations: I would not expect them to carry the day against the § 103 combinations above, though they are the patentee's best ground given the named "AAA server" and "RADIUS/LDAP" limitations.

9. Weaknesses, split of outcomes, and confidence

• The single largest uncertainty is the priority date. If the challenged claims are entitled to Dec 8, 1998, PA-1 (published 1998-09-17, < 1 year before) is not a § 102(b) bar and may be disqualified as same-inventor art → the § 103 case must rest on PA-2/PA-4/PA-5/PA-6 alone. If the claims rest on 2000-10-20 CIP matter, PA-1 becomes § 102(b) art and the combinations in § 3–§ 5 become strong. I cannot decide this from the page.
• I could not verify the examiner-cited "(56) References Cited" list, nor open PA-4/PA-6 text, nor confirm the Certificate of Correction's effect on claims 1/17/24. My descriptions of Vu (PA-4) and Brendel (PA-6) are stated at a deliberately general level; treat the mappings as analytical hypotheses to be verified against the reference texts, not as verified quotations.
• No finding that the '554 claims were held invalid. Litigation (C.D. Cal. 2:09-cv-08441 against HP; 2:14-cv-08256 against Blueprint RF; 2:19-cv-10202 against SIA MikroTikls, which asserted the '554 and produced a Mar. 8, 2023 claim-construction order construing "determining the access rights…" and "regardless of network configurations") tested validity, and I found no IPR or CBM final written decision invalidating the '554 specifically (the CBM I confirmed targets the '399 patent; IPR2016-00081 targets the '269 patent). This is an absence of evidence, not proof of validity.
• Formal legal caveat: obviousness is decided on the totality of the record, including a POSITA's knowledge and any objective indicia; no combination can be "proved" without the actual reference texts, the file history, and the priority record. This memo is a screening-level analysis, not an invalidity opinion.

10. One-line conclusions

1. Claims 1, 10, 17 and their RADIUS/LDAP/accounting dependents (4, 5, 7, 12, 13, 15, 16, 18, 19, 22, 24) are the most vulnerable, because they name known components (external profile database, AAA server, RADIUS/LDAP, accounting log) that the art of record supplies directly — PA-1 + PA-2 (+ PA-3), or PA-4 + PA-2 + PA-5.
2. Claims 3, 8, 11, 20 (location/MAC/VLAN/circuit-ID attributes) are also vulnerable via PA-2's NAS-Port / Calling-Station-Id attributes and PA-7.
3. The hardest limitation to defeat is the claim 1 preamble/claim 10 element (b) — "regardless of network configurations… packet translation learned during a self configuration… no configuration software." If PA-1 (WO 98/40990) is available, it falls; if it is excluded on priority/same-inventor grounds, the whole case is materially weaker.
4. Outcome therefore turns on a priority-date determination I could not make from the supplied page and my searches — flag this as the decisive open issue.

Sources consulted: the supplied authoritative Google Patents text for US7194554B1 (https://patents.google.com/patent/US7194554B1/en); Espacenet bibliographic record for US7194554B1; the C.D. Cal. record in Nomadix, Inc. v. SIA MikroTikls, No. 2:19-cv-10202 (claim construction order, Doc. 147, filed 2023-03-08, construing the '554), and the Nomadix v. Hospitality Core Services (Blueprint RF), No. 2:14-cv-08256, § 102/§ 103 filings and Jan. 27, 2016 summary-judgment order identifying the invalidity references discussed above. I did not reach the USPTO PatentCenter/PAIR record, the (56) references list, or the Certificate of Correction.