US 8266266

I'll search for this specific patent number across USPTO and litigation sources.

Let me narrow the search to the specific patent and any 2026 Federal Circuit activity.

Let me check for any 2026 appellate activity and confirm the PTAB outcomes.

US 8,266,266 — Analyst Summary

Search scope / grounding note: I queried for the exact identifier "8266266" and retrieved (a) the USPTO/Google Patents full-text record, (b) the issued-patent PDF front page, and (c) litigation/PTAB records. Section-level detail below comes from the authoritative full text you supplied plus the issued PDF front matter. Where I could not verify something, I say so explicitly rather than filling the gap.

Bibliographic data (verified)

Abstract (verbatim from the issued PDF front page)

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

Plain-language overview of the independent claims

The document is organized around four independent claim families (method/system pairs), plus a portable-router claim family. Only claim 1 could be confirmed by number from the litigation record; the remaining groupings are drawn from the claim-language passages reproduced in the specification/definitional text you supplied. I did not have the literal, numbered claim set in the fetched text, so I flag the numbering below as inferred except for claim 1.

1. Claim 1 (confirmed) — Selective AAA method. A method of selectively controlling/customizing source access to a network where the source computer has transparent access via a gateway device and needs no configuration software. Steps: receive a request at the gateway; identify an attribute of the source from a packet the gateway received; look up a source profile in a source profile database external to the gateway using that attribute; and determine the source's access rights (including rights to a requested destination) from that profile. Confirmed by the Stubblebine declaration in Nomadix v. Hospitality Core Services, which distinguishes claim 1 of the '266 patent from claim 6 of the '246 patent ("one can literally infringe claim 1 of the '266 patent without literally infringing claim 6 of the '246 patent").

2. System counterpart to #1. A gateway device + external source profile database storing attribute-identifiable access information + a AAA server that decides whether the source may access the network and defines the source's destination access rights. Supporting detail in the specification: the packet may carry VLAN ID, circuit ID, and/or MAC address; the database may be RADIUS or LDAP; profiles may include historical/duration data for billing; the database may sit inside the AAA server.

3. Redirection method. A method of redirecting a source attempting to reach a destination through a gateway: receive the request, identify the source by attribute, access an external source profile database, and determine access rights; includes assigning a location identifier as the attribute, updating the database for new sources, and logging usage in an accounting database.

4. Transparent-communication system. A computer + network gateway device + a service-provider network containing an authentication server external to the gateway, whose source profile database represents authorized users and is compared against source data to grant/deny access; optionally includes an accounting system; source data may be an attribute of the computer or login information.

5. "New user" creation method/system. For a user whose home-network settings are unchanged: receive a request at the gateway, determine entitlement from a user profile database, and redirect to a login page when the profile lacks access rights (otherwise forward to the destination). Includes portal-page redirection, a login page maintained local to the gateway, HTTP request/response-based redirection, and updating the profile with user-supplied information.

6. Portal-page redirection method/system. Receive a request for a destination address, redirect the user to a portal page (administrator-created or user-customized) while the user's computer "remains configured for accessing the home network" and no additional configuration software is installed; the AAA server may be "located entirely within the gateway device."

7. Portable "nomadic" router claim. A portable router/translator making a terminal location- and device-transparent, comprising five modules: (1) stores the user's digital communication address; (2) detects the network location; (3) detects attached communication devices; (4) auto-converts the location address to the user's address for data communication; (5) auto-selects a detected communication device. The specification describes proxy-ARP-based interception, packet translation across link/network/transport/application layers, and PCMCIA Type II/III form factors.

Litigation / PTAB posture (verified, and relevant to any 2026 diligence)

• Family has litigation (Darts-IP flag on the record).
• District court: Nomadix, Inc. v. Hospitality Core Services LLC d/b/a Blueprint RF, No. 2:14-cv-08256 DDP (VBKx), C.D. Cal. The '266 patent was one of seven asserted (with 6,636,894; 6,868,399; 8,156,246; 8,266,269; 8,364,806; 8,788,690). Blueprint counterclaimed for invalidity/unenforceability (inequitable conduct, prosecution laches), alleging the "'894, '246, '266, '269 and '806" patents are duplicative "captive portal" patents.
• PTAB:
  • IPR2016-00077 — filed Oct. 27, 2015 by Hospitality Core Services, LLC; outcome listed as Settlement.
  • IPR2018-00376 — filed Dec. 22, 2017 by Guest-Tek Interactive Entertainment Ltd.; outcome Not Instituted – Merits.
  • IPR2018-01668 — outcome Not Instituted – Procedural.

⚠️ On the 2026 CAFC question — important limitation

I found no Federal Circuit docket, opinion, or briefing in 2026 that names US 8,266,266. My searches surfaced 2026 CAFC materials for unrelated patents (e.g., US Patent No. 7,679,637 LLC v. Google LLC, Fed. Cir. Jan. 22, 2026; Enviro Tech v. Safe Foods, No. 2024-2160; TJTM Technologies v. Google, No. 2025-1218) — none of which involve 8,266,266, and I am deliberately not conflating them with your target. The most recent activity I can substantiate for this patent is the 2017 IPR filing and the 2014–2016 district court matter.

CAVEAT: this is a negative search result, not proof of absence. Public web indexes are incomplete for CAFC dockets, and a pending appeal might not be indexed by docket number tied to the patent. To close this out authoritatively you should query USPTO PatentCenter (application 12/685,585) for the "Appeal" / "Federal Circuit" transaction history, and the CAFC CM/ECF docket by the patent number or by Nomadix/Gate Worldwide as party — neither of which I was able to reach with the tools available here.

Residual uncertainty

• The literal text of all 28 claims was not present in the fetched record; my claim overviews 2–7 are reconstructed from the specification/claim-language text supplied and should be confirmed against the published claim set before being relied on.
• Current ownership is layered and worth tracing: original assignee Nomadix, Inc.; security interests recorded to NTT DOCOMO, INC. (2015, 2017); assignment of the security agreement and of interest to GATE WORLDWIDE HOLDINGS LLC (Jan. 23, 2018); a security interest to Knobbe, Martens, Olson & Bear, LLP (2019) released back to Nomadix (May 2019); and a quitclaim from Gate Worldwide Holdings to NOMADIX, INC. (Nov. 22, 2019). Google Patents nonetheless lists Gate Worldwide Holdings LLC as current assignee, which is in tension with the 2019 quitclaim — treat assignee-of-record as uncertain and confirm via USPTO Assignment records.

I'll search for litigation involving US patent 8,266,266 across patent litigation sources.

Let me gather more detail on the district court case outcome and the PTAB proceedings.

Let me search for the later PTAB proceedings and any additional district court litigation.

I'll start by pulling the structured list and then verify the PTAB dockets via web search.

I have three PTAB numbers from the patent's own litigation/PTAB metadata. Let me verify what each targeted and its outcome.

Now let me pin down IPR2018-01668 and the grounds/panels for the others.

PTAB Proceedings — U.S. Patent No. 8,266,266 (US8266266B2)

Data-integrity flag. The structured "PTAB proceedings on file" block supplied for this task states the USPTO ODP API returns no AIA trial proceedings for US 8,266,266. That is contradicted by the patent's own front-page/litigation metadata on Google Patents, which lists three PTAB dockets tied to this family: IPR2016-00077 (Settlement), IPR2018-00376 (Not Instituted – Merits), and IPR2018-01668 (Not Instituted – Procedural). Treat the ODP "no activity" result as an ingest gap, not as ground truth. All three numbers below are taken from the patent record; nothing here is invented.

Proceedings overview

Three PTAB dockets are associated with this patent family — one instituted and later settled before any merits decision, and two where institution was denied — meaning no claim of US 8,266,266 has ever been canceled, but equally no claim has ever been confirmed in a Final Written Decision, so the patent is neither "hardened" nor "dead": it is simply unchallenged on the merits and now expired (term ended 2019-12-08), which is the single most important defensive fact a defendant has.

Breakdown: active = 0; claims invalidated by FWD = 0 proceedings / 0 claims; claims sustained by FWD = 0 proceedings / 0 claims (no FWD ever issued); settled = 1 (IPR2016-00077); institution denied = 2 (IPR2018-00376 on the merits; IPR2018-01668 on procedural grounds).

Estimates vs. verified facts: everything below is sourced from the patent text's own PTAB/litigation metadata, the Board's termination judgment, a PTO Litigation Center docket listing, a petitioner-side press release, and Nomadix's public statements. Where a source does not state something (e.g., the specific prior art in IPR2016-00077), I say so rather than fill the gap.

IPR2016-00077 — Hospitality Core Services, LLC (d/b/a Blueprint RF) v. Nomadix, Inc.

• Type: Inter Partes Review (35 U.S.C. §§ 311–319)
• Filed: 2015-10-27
• Status: Verbatim: "Settlement" (Google Patents family-litigation entry) / docket status "Terminated‑Settled" (Patexia). Plain English: instituted, then killed by a joint motion to terminate before the Board reached the merits — no Final Written Decision, no claim outcomes.
• Judge panel: Howard B. Blankenship, Glenn J. Perry, and Trevor M. Jefferson, Administrative Patent Judges; Blankenship authored the termination judgment.
• Petition grounds: Challenged claims 1–28 of U.S. Pat. No. 8,266,266 B2. The Board's judgment confirms the case was an IPR, but the specific prior-art references and the § 102 / § 103 allocation are not stated in the sources reviewed — do not assume the district-court art (ATCOM/iPORT, SPINACH, Vos, Ikudome) carried over to the '266 petition.
• Institution decision: Instituted 2016-05-09 (per Patexia docket record). The Board's later termination judgment is consistent with institution: it notes that the merits had not been decided and that Patent Owner "has not yet submitted its patent owner response to the petition" — a post-institution posture. The panel's institution reasoning is not in the sources reviewed.
• Final Written Decision: None. None was ever issued. Claims 1–28 were neither canceled nor held patentable.
• Settlement / termination: Joint Motion to Terminate filed 2016-06-28 in IPR2016-00077 and two companion proceedings (see pattern signals below); the Board granted termination and entered judgment under 37 C.F.R. §§ 42.5, 42.71, 42.73, 42.74 on 2016-07-27. The parties' settlement agreement was filed under 37 C.F.R. § 42.74(b) and, on joint request, was accorded business-confidential treatment under § 42.74(c) and kept separate from the patent files — the terms are effectively confidential and not public. The termination expressly notes that the settlement also resolved the parallel district court case Nomadix, Inc. v. Hospitality Core Services LLC, No. 14-cv-08256 (C.D. Cal.).
  • Judgment PDF: https://www.docketalarm.com/cases/PTAB/IPR2016-00081/Inter_Partes_Review_of_U.S._Pat._8266269/docs/07-27-2016-Board/Termination___Settlement_After_Institution-18-Judgment___Termination_Pursuant_to_Settlement.pdf
  • Portal record: https://portal.unifiedpatents.com/ptab/case/IPR2016-00077
• Appeal: None. No FWD ⇒ nothing appealable to the Federal Circuit.
• Defensive value: This is a nullity for defensive purposes but a goldmine for § 315(e) analysis — because the proceeding ended without an FWD, no statutory estoppel attached to Hospitality Core Services/Blueprint RF. Conversely, the petitioner's art and expert work product never became a public, Board-blessed invalidity finding, so you get no free roadmap. If you are a Blueprint privy, note the settlement — not the IPR — is what binds you.

IPR2018-00376 — Guest-Tek Interactive Entertainment Ltd. v. Nomadix, Inc.

• Type: Inter Partes Review
• Filed: 2017-12-22 (per PTO Litigation Center listing, Patent # 8,266,266, Title "Systems and Methods For Providing Dynamic Network Authorization, Authentication and Accounting," Petitioner Guest-Tek Interactive Entertainment Ltd.)
• Status: Verbatim: "Not Instituted ‑ Merits". Plain English: institution denied on the merits — the Board was not persuaded there was a reasonable likelihood of prevailing on any challenged claim.
• Judge panel: Not disclosed in the sources reviewed.
• Petition grounds: Directed at the '266 patent. Notably, Guest-Tek filed Blueprint's earlier IPR2016-00077 petition as Exhibit 1006 in its own case — i.e., it recycled and built on the earlier challenger's art. The precise claims challenged and the art/references are not verified from the sources reviewed.
• Institution decision: Denied, 2018-06-29. Nomadix's public statement describes the denial thus: the PTAB "explained that Guest-Tek had failed to demonstrate a reasonable likelihood that it could show unpatentability of any of the claims from the Nomadix patents." Procedural record: Notice of Filing Date Accorded to Petition dated 2018-01-09; Patent Owner's Mandatory Notices 2018-01-12; Patent Owner Preliminary Response 2018-04-09 (47 pages); denial about 2½ months later. (Nomadix's release says the Board denied Guest-Tek's petitions on "two of Nomadix's patents" that day; the '266 was one.)
• Final Written Decision: None (institution denied).
• Settlement / termination: Not a settlement. Terminated by denial of institution.
• Appeal: No FWD ⇒ no Federal Circuit appeal of this proceeding. Guest-Tek's appellate activity in this period was elsewhere: the Ninth Circuit appeal No. 20-55439 (Nomadix, Inc. v. Guest-Tek Interactive Entertainment Ltd.), which concerned a contractual forum-selection clause in the parties' license and whether Nomadix could enjoin Guest-Tek from using the PTAB — not a PTAB merits appeal. Brief: https://fingfx.thomsonreuters.com/gfx/legaldocs/byprjomlpe/ —
  corrected link: https://fingfx.thomsonreuters.com/gfx/legaldocs/byprjomqlpe/nomadix%20brief2.pdf
• Defensive value: The most useful precedent in the file. A well-funded, adversarially motivated competitor (Guest-Tek) took a full shot at the '266 with the benefit of a prior petitioner's work product and lost at the institution stage. That does not estop anyone else — a denial is not a validity holding and has no collateral effect — but it is a strong signal that the '266's claims are not low-hanging fruit under § 102/§ 103, and it hands you Nomadix's POPR framing as a roadmap of the claim constructions the patent owner will fight for.

IPR2018-01668 — Petitioner unidentified v. Nomadix, Inc. (target patent unconfirmed)

• Type: Inter Partes Review (inferred from the IPR docket number series)
• Filed: Not verified. A docket number in the IPR2018-01xxx range places the filing in roughly mid-2018, i.e., shortly after the 2018-06-29 denial in IPR2018-00376, but I did not confirm a filing date from a primary source.
• Status: Verbatim: "Not Instituted ‑ Procedural". Plain English: institution was denied for a procedural reason rather than on the merits — typically a § 315(b) one-year time bar, a § 325(d) discretionary denial, failure to identify all real parties-in-interest, improper service, or a defective petition — but the specific procedural defect is not stated in the sources reviewed.
• Judge panel: Not disclosed.
• Petition grounds: Not verified.
• Institution decision: Denied; date and reasoning not verified.
• Final Written Decision: None.
• Appeal: None.
• ⚠️ Critical caveat: This docket appears in the family-level litigation/PTAB metadata on the patent page (https://portal.unifiedpatents.com/ptab/case/IPR2018-01668). Family-level metadata is not patent-specific — the Nomadix family includes the '246, '266, '269, '806 and '690 patents, all asserted in the same campaigns. I could not confirm that IPR2018-01668 targets U.S. Pat. No. 8,266,266 specifically. Do not assert in a brief, or to a client, that this proceeding challenged the '266 without pulling the petition from PTAB E2E first. Given that Guest-Tek filed IPR2019-00211 and IPR2019-00258 (both dated 2018-11-12, on the '857 and '922 patents) as a later wave, IPR2018-01668 is more likely an interim 2018 filing on a different Nomadix patent or a defective earlier Guest-Tek petition.
• Defensive value: Low and unquantified. A procedural denial establishes no patentability and creates no estoppel, and it does not tell you anything about the '266's merits. Treat as a lead to run down, not as evidence.

Strategic summary

Claim status: everything is untested. No claim of US 8,266,266 has been canceled by the PTAB, and no claim has been sustained through a Final Written Decision. The IPR2016-00077 challenge reached claims 1–28 and was settled after institution and before any merits ruling; IPR2018-00376 was denied institution on the merits; IPR2018-01668 was denied on procedural grounds (target unconfirmed). So for claim-status purposes the entire claim set — claims 1–28 — is UNTESTED at the PTAB. There are no "surviving" claims in the IPR sense (nothing was narrowed by certificate), and there is no IPR certificate to cite. Anyone who tells you "the PTAB invalidated the '266" is wrong; anyone who tells you "the PTAB upheld the '266" is also wrong. The only reason the claims were never invalidated is that no challenger ever got a Final Written Decision.

The real defensive lever is expiration, not validity. The patent's anticipated expiration is 2019-12-08, and current Google Patents legal status is "Expired ‑ Fee Related." That means: (i) no prospective injunctive relief is available for post-expiration conduct; (ii) damages are limited to past infringement within the § 286 six-year lookback and are capped by the expiration date; and (iii) the acquisition chain — NTT DOCOMO security interests (2015-09-30, 2017-08-29), assignment/security assignment to Gate Worldwide Holdings LLC (2018-01-23), and a quitclaim back to Nomadix, Inc. (2019-11-22) — is worth auditing for standing and ownership defects before you concede anything. If a demand letter arriving in 2026 cites this patent, the threshold question is not patentability; it is whether any damages window remains open at all.

Estoppel: essentially none, so your prior-art runway is wide. Section 315(e)(2) estoppel attaches only to a petitioner that obtains a Final Written Decision. IPR2016-00077 ended in settlement judgment under 37 C.F.R. § 42.73 without an FWD, and the Board expressly found the merits undecided — so no § 315(e) estoppel runs against Hospitality Core Services/Blueprint RF or its privies from that case. IPR2018-00376 and (if it concerns the '266) IPR2018-01668 ended in denials of institution, which likewise produce no estoppel. Practically: any defendant today may raise any § 102/§ 103 ground in district court on patents or printed publications, including art already put before the Board, subject only to ordinary IPR-filing and § 315(b) bars if you file a new petition. One caution — the settlement judgment in IPR2016-00077 recorded a confidential settlement agreement; if Nomadix asserts the '266 against a Blueprint successor or privy, the litigation defense may be governed by that agreement rather than by the patent, so get the settlement agreement produced.

Pattern signals. (1) Repeat challengers are the norm for this family. Blueprint/Hospitality Core Services filed a coordinated multi-patent salvo in October 2015 — IPR2016-00052 ('894), IPR2016-00073 ('246), IPR2016-00077 ('266), IPR2016-00081 ('269), IPR2016-00092 ('806) — and all were resolved together by the single 2016-06-28/2016-07-27 settlement. Guest-Tek then filed its own wave in December 2017 (including IPR2018-00376 on the '266, reusing Blueprint's petition as an exhibit) and another wave on 2018-11-12 (IPR2019-00211, IPR2019-00258). (2) Nomadix litigated hard and asymmetrically: it fought PTAB challenges, sued Guest-Tek for breach of the license in 2016 (C.D. Cal. No. 2:16-cv-08033), predicted $15M+ in unpaid royalties, and in 2019 sued again to enforce a forum-selection clause to stop Guest-Tek from filing IPRs — obtaining a permanent injunction and summary judgment, appealed by Guest-Tek at Ninth Circuit No. 20-55439. Guest-Tek later withdrew PTAB filings on the eve of decision as a result. (3) No defensive aggregator on the '266. Unified Patents' role here is portal/database provider only (the Unified Patents URLs in the patent record are litigation-data links); the petitioners were commercial competitors, not a defensive aggregator. That matters: there is no third-party IPR horse you can ride. (4) No Federal Circuit appeal exists on this patent — unsurprising, since no FWD ever issued. Parallel appellate activity is contractual (Ninth Circuit) and foreign (Canadian Federal Court, Guest Tek Interactive Entertainment Ltd. v. Nomadix, Inc., on the '760 and '345 Canadian patents, decided in Nomadix's favor on non-infringement and validity).

Recommended next steps

1. Lead with expiration, not invalidity. Confirm the expiration date and any terminal disclaimer / PTA on the face of the patent, then confirm the last date of potentially infringing conduct. With the term ending 2019-12-08 and status Expired ‑ Fee Related, the practical damages exposure is bounded, and any current-sales infringement theory is legally impossible.
2. Run down IPR2018-01668 before you rely on anything. Pull the proceeding in PTAB E2E (https://ptacts.uspto.gov/ptabweb) and confirm (a) the petitioner, (b) the challenged patent, and (c) the procedural ground for denial. Until then, cite it only as "a related PTAB docket in the Nomadix family, target patent unverified."
3. There is no FWD to quote. Because no Final Written Decision issued in any of the three dockets, do not draft an argument that "claims X were canceled." There is no disposition to link; the honest statement is "the patent's claims have never been tested to judgment at the PTAB."
4. Pull and read the two institution denials. The IPR2018-00376 denial (2018-06-29) and Nomadix's POPR filed 2018-04-09 are the closest thing to a Board-endorsed read of the '266 claims. That POPR is your best free preview of the claim-construction positions Nomadix will take and the art it fears — and because a denial creates no estoppel, you retain those grounds.
5. Audit the chain of title and any confidential settlement. Verify standing of whoever is asserting the patent (Nomadix → NTT DOCOMO security interests → Gate Worldwide Holdings → quitclaim back to Nomadix, 2018–2019). Separately, if the counterparty is a Blueprint/Hospitality Core Services privy, demand the IPR2016-00077 settlement agreement filed as an exhibit under § 42.74(b) — it is confidential but discoverable in litigation, and it disposed of the whole 2015 IPR wave plus the C.D. Cal. 14-cv-08256 case.
6. Estoppel check you can affirmatively make: no IPR FWD ⇒ no § 315(e)(2) estoppel against any prior petitioner or privy. If you elect to file your own IPR, the usual § 315(b) one-year bar from service of a complaint still applies, and the PTAB's Fintiv-era § 314(a) discretion plus § 325(d) remain live risks given three prior attempts on this family.

Sources consulted: patent record at https://patents.google.com/patent/US8266266/en; Board Judgment — Termination Pursuant to Settlement, IPR2016-00077/-00081/-00092 (2016-07-27); PTO Litigation Center report, 2015-10-28 and 2017-12-27; Patexia docket summary for IPR2016-00077; Nomadix press release, "Patent Trial and Appeal Board Denies Guest-Tek's Petitions for Review of Nomadix Patents," 2018-07-02; Ninth Circuit Appellant's Opening Brief, No. 20-55439; Canadian Federal Court decision (Guest Tek Interactive Entertainment Ltd. v. Nomadix, Inc.).

I'll research this chain before writing. Let me run several searches in parallel.

Let me dig into the litigation campaign, the Gate Worldwide Holdings entity, and any reel/frame data.

US 8,266,266 B2 — Assignment Chain Reconstruction

Data-quality caveat, stated up front: I could retrieve the event-level assignment history (Google Patents legal-events feed, litigation dockets, PTAB records, corporate filings) but I could not retrieve the USPTO Assignment Center reel/frame numbers or the recorded correspondent-of-record fields for this patent from the sources available to me. Google Patents' legal-events feed reproduces conveyance type, assignor and assignee but not reel/frame or correspondent. I am therefore not supplying reel/frame numbers — fabricating them would be worse than omitting them. Every entry below is traceable to the Google Patents legal-events block reproduced in the authoritative patent text, plus docket corroboration. Treat reel/frame and correspondent as open verification items against https://assignmentcenter.uspto.gov/.

Inventors

Unusual patterns: No "all inventors departed within 12 months" signature. The relevant anomaly is different and arguably more significant: the sole founder-inventor on this family, Joel Short, died in Nov. 2004, and co-founder Kleinrock retired. That leaves the portfolio without its technical champion roughly four years before Nomadix began its first serious assertion wave (2007–2010), and is consistent with the later pattern of the portfolio being managed as a financial asset secured against borrowing rather than as the core of a going concern.

⚠️ Note: Leonard Kleinrock is described in the Blueprint RF counterclaim (C.D. Cal. 2:14-cv-08256, Dkt. 69) as a "named inventor of the Nomadix patents," but he is not a named inventor on US 8,266,266. He is the founder/CEO/Chairman, not an inventor of record here.

Original assignee

Nomadix, Inc. — Woodland Hills / Agoura Hills, California. Private company founded 1998 in Santa Monica by Dr. Leonard Kleinrock and Joel Short.

• Primary line of business: network gateway equipment and software for visitor-based networks (hotels, MDUs, airports) — access gateways, bandwidth managers, TV casting. Product line includes the EG 6000 Edge Gateway and AG 2500.
• Did it ship a product embodying the claims? Yes. The first product, the Nomadix Universal Subscriber Gateway, shipped September 1999 (the same month as the priority filing). Nomadix reported >50,000 units shipped and 100+ patents across 15 functional areas (IPWatchdog 2016-02-26). This is a genuine product company, not a paper assignee — an important fact for the verdict.
• Current status: Operating, but not independent. Corporate-parent trail from docket filings:
  • Oct. 2014 (C.D. Cal. 2:14-cv-08256, Dkt. 4): Nomadix identifies DOCOMO interTouch as its parent, NTT DOCOMO as parent of DOCOMO interTouch.
  • Dec. 2019 (C.D. Cal. 2:19-cv-10202, Dkt. 4): Nomadix identifies GWHSPV, LLC as parent of Nomadix, and Gate Worldwide Holdings LLC as parent of GWHSPV, LLC.
  • Third-party IP-owner profile (Onscope) currently lists Nomadix's parent as DOCOMO InterTouch Interactive Pte. Ltd.
  • Net: the brand and products continue; the equity has been passed among a DOCOMO-linked group and the Gate Worldwide Holdings holding structure.

Assignment timeline

The chain below is the complete set of post-issuance assignment events in the Google Patents legal-events record. Reel/frame and correspondent fields were not retrievable and are marked as such — they are not omitted by accident.

IMPORTANT STRUCTURAL POINT: six of the seven recorded events are security interests, modifications, and releases — not transfers of title. Only two events move actual ownership interest: the 2018-01-23 assignment of assignor's interest to Gate Worldwide Holdings LLC, and the 2019-11-22 quitclaim back to Nomadix, Inc. Do not read this as a seven-link cascading transfer chain; it is a secured-lending history wrapped around two title movements.

• 2015-09-30 (executed) / recorded on or about 2015-09-30 — Reel/frame not retrieved

  • Conveyance: Security Agreement (listed as "SECURITY INTEREST (SEE DOCUMENT FOR DETAILS)")
  • Assignor: Nomadix, Inc.
  • Assignee: NTT DOCOMO, INC.
  • Correspondent: not retrieved
  • Context: Securitization — Nomadix pledges its patent estate as collateral to its corporate parent's parent. Not a sale of title.

• 2017-08-29 (executed) / recorded on or about 2017-08-29 — Reel/frame not retrieved

  • Conveyance: Modification to Patent Security Agreement
  • Assignor: Nomadix, Inc.
  • Assignee: NTT DOCOMO, INC.
  • Correspondent: not retrieved
  • Context: Securitization — amendment/extension of the 2015 collateral package, typically reflecting additional pledged assets or revised covenants. A credit-stress marker, not an ownership event.

• 2018-01-23 (executed) / recorded on or about 2018-01-23 — Reel/frame not retrieved

  • Conveyance: Assignment of Patent Security Agreement
  • Assignor: NTT DOCOMO, INC.
  • Assignee: GATE WORLDWIDE HOLDINGS LLC
  • Correspondent: not retrieved
  • Context: Internal reorg / securitization — the secured party role is novated from DOCOMO to the Gate Worldwide Holdings holding layer. No change in the debtor (Nomadix).

• 2018-01-23 (executed) / recorded on or about 2018-01-23 — Reel/frame not retrieved

  • Conveyance: Assignment of Assignor's Interest (i.e., actual title transfer)
  • Assignor: Nomadix, Inc.
  • Assignee: GATE WORLDWIDE HOLDINGS LLC
  • Correspondent: not retrieved
  • Context: Internal reorg — the operative title movement of the chain. Nomadix becomes an operating subsidiary and Gate Worldwide Holdings becomes the recorded patent holder. This is the single event most worth pulling the reel/frame for.

• 2019-03-20 (executed) / recorded on or about 2019-03-20 — Reel/frame not retrieved

  • Conveyance: Security Interest
  • Assignor: Nomadix, Inc.
  • Assignee: Knobbe, Martens, Olson & Bear, LLP — a law firm, not a financial institution
  • Correspondent: not retrieved (note: Knobbe Martens is itself the named secured party here; it separately appears in the litigation dockets as Nomadix's counsel of record — Mark Lezama and Douglas Muehlhauser filed for Nomadix in C.D. Cal.)
  • Context: Fee-security / distress marker — granting a security interest to outside IP litigation counsel is a classic pattern of unpaid-fee collateralization. Released roughly nine weeks later.

• 2019-05-28 (executed) / recorded on or about 2019-05-28 — Reel/frame not retrieved

  • Conveyance: Release by Secured Party
  • Assignor: Knobbe, Martens, Olson & Bear, LLP
  • Assignee: Nomadix, Inc.
  • Correspondent: not retrieved
  • Context: Lien release — the fee lien is satisfied or restructured. Consistent with a financing event, not a fire-sale.

• 2019-11-22 (executed) / recorded on or about 2019-11-22 — Reel/frame not retrieved

  • Conveyance: Quitclaim
  • Assignor: GATE WORLDWIDE HOLDINGS LLC
  • Assignee: Nomadix, Inc.
  • Correspondent: not retrieved
  • Context: Internal reorg reversal — title returns to the operating entity 22 months after leaving it. Note this directly contradicts Google Patents' header field listing Gate Worldwide Holdings LLC as "Current Assignee"; on the recorded events, Nomadix, Inc. appears to be the current titleholder.

Corroborating non-assignment evidence for the 2018 reorg: in Nomadix, Inc. v. Guest-Tek Interactive Entertainment Ltd. (C.D. Cal. 2:16-cv-08033), Gate Worldwide Holdings LLC moved to substitute itself as plaintiff and then withdrew the motion on or before 2019-02-25, with the court ordering GWH to withdraw "no later than 2/25/2019." That motion is the litigation-side fingerprint of the 2018-01-23 title transfer, and its withdrawal lines up with the 2019-11-22 quitclaim.

Timeline diagram

timeline
    title Ownership and assertion history of US 8266266
    1998 : Nomadix founded
    1999 : Priority applications filed
         : First gateway product ships
    2010 : Continuation application filed
    2012 : Patent issues to Nomadix Inc
    2014 : Blueprint RF suit filed
    2015 : Security interest to NTT DOCOMO
    2017 : DOCOMO security agreement modified
    2018 : Title assigned to Gate Worldwide
         : GWH moves to substitute in Guest-Tek
    2019 : Fee security interest to Knobbe
         : Title quitclaimed back to Nomadix
         : Mikrotikls suit filed

NPE / troll-pattern signals

1. Shell-entity transfer — NOT PRESENT.
Gate Worldwide Holdings LLC and GWHSPV, LLC are holding companies, but the evidence runs the other way from a shell pattern: the operating entity (Nomadix, Inc.) remained the plaintiff of record in every suit, shipped products continuously, and regained recorded title via the 2019-11-22 quitclaim. A shell-entity transfer would leave an empty operating company and a litigation-only assignee; here the operating company retook the asset. Reel/frame citation: the 2018-01-23 Assignment of Assignor's Interest and the 2019-11-22 Quitclaim (reel/frame not retrieved).

2. Known asserter in the chain — NOT PRESENT.
Neither Nomadix, Inc., NTT DOCOMO, Gate Worldwide Holdings LLC, GWHSPV, LLC, nor Knobbe Martens appears on the listed NPE rosters (Acacia, Marathon, IV, IPNav, Wi-LAN, Mosaid/Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, Document Generation Corp, Spangenberg entities). No Unified Patents or RPX high-frequency-plaintiff listing surfaced for any link. Note that Unified Patents did file IPRs against the family (IPR2016-00077, IPR2016-00081, IPR2018-00376, IPR2018-01668) — but that is Unified acting as a defensive challenger, which is a different relationship than the patent owner being a known asserter.

3. Repeat correspondent across the chain — UNCLEAR / NOT VERIFIABLE.
The correspondent field is exactly what I could not retrieve. Two things I can say without conflating them:

• Knobbe, Martens, Olson & Bear, LLP appears in this chain as a party (the 2019-03-20 secured party), not as correspondent. That is a fee-security role, which is materially different from the "one lawyer running a family of shell LLCs" tell.
• Knobbe Martens attorneys (Mark Lezama, Douglas Muehlhauser) appear as Nomadix's counsel of record across the 2010–2019 dockets. If the Assignment Center shows Knobbe as correspondent on multiple links, that would still be ordinary outside-counsel portfolio maintenance for a single client, not the NPE signature — the NPE signature requires the same attorney recording for nominally unrelated LLCs. I have no evidence of that here.
  Action item: pull the correspondent fields for all seven recordings before treating this signal as anything.

4. Cascading transfers — NOT PRESENT.
Only two title movements (2018-01-23 out, 2019-11-22 back), both between entities in the same controlled group, separated by 22 months. The intervening entries are security interests and releases. This is not a chained-LLC cascade.

5. Pre-litigation transfer — NOT PRESENT.
Check each suit against the nearest antecedent assignment:

• Suit filed 2014-10-24 (Blueprint RF, 2:14-cv-08256); nearest assignment is 2015-09-30 — the transfer post-dates the suit by 11 months.
• Suit filed 2016 (Guest-Tek, 2:16-cv-08033); nearest assignment 2018-01-23 post-dates it.
• Suit filed 2019-12-02 (Mikrotikls, 2:19-cv-10202); nearest prior event is the 2019-05-28 release and 2019-11-22 quitclaim — the quitclaim is 10 days before filing, but it is a transfer back to the already-operating plaintiff, i.e., a clean-standing-record housekeeping step, not a transfer to an asserter. Timing is close; character is wrong for the signal.

6. Bankruptcy fire-sale — NOT PRESENT.
No Chapter 7/11 filing for Nomadix, Inc. surfaced. The 2019-03-20 fee security interest to Knobbe Martens followed by a 2019-05-28 release is the closest analogue to distress, and it was resolved by release, not by a court-supervised sale. No Kodak/Nortel/Polaroid-style auction.

7. Privateering — NOT PRESENT.
This is the closest call. Nomadix is a DOCOMO-affiliated operating company suing competitors (Blueprint RF, Guest-Tek, HP, Mikrotikls) in its own name. But privateering requires an operating sponsor transferring to an NPE that asserts against the sponsor's competitors. Here the parent (DOCOMO) transferred to its own holding entity, the holding entity never asserted (its substitution motion was withdrawn), and title came back. There is no evidence DOCOMO used the patent against its rivals.

8. Defensive aggregator — NOT PRESENT.
The chain does not end at RPX, AST, LOT, Unified Patents, or OIN. The IPR filers (Unified) are adverse parties, not assignees.

Verdict

Operating-company assertion.

Justification: The patent has been asserted by Nomadix, Inc. — an entity that ships products embodying the claims (Universal Subscriber Gateway since Sept. 1999; >50,000 units; EG 6000/AG 2500 today) — against actual competitors in its own market, beginning with Nomadix v. Hospitality Core Services LLC d/b/a Blueprint RF (C.D. Cal. 2:14-cv-08256, filed 2014-10-24), where the court granted Nomadix summary judgment of infringement of the related '246 patent on 2016-01-27. Every recorded assignment event is either a security interest / modification / release (2015-09-30, 2017-08-29, 2018-01-23 security, 2019-03-20, 2019-05-28) or an intra-group title movement (2018-01-23 assignment to Gate Worldwide Holdings LLC, reversed by the 2019-11-22 quitclaim back to Nomadix), with no known NPE appearing anywhere in the chain. The residual uncertainty is genuine but bounded: the Gate Worldwide Holdings/GWHSPV holding layer and the 2019 fee-security interest to Knobbe Martens show a portfolio being managed as a financeable asset, and I could not verify reel/frame or correspondent, so signals 3 and the precise character of signal 1 remain open.

Verification link: https://assignment.uspto.gov/patent/index.html (search patent number 8266266) — also https://assignmentcenter.uspto.gov/ ; corroborating record at https://patents.google.com/patent/US8266266/en

I'll research US patent 8,266,266 and its cited prior art references.

Let me get the detailed cited references from the patent front page.

Let me look for the specific cited references list on the patent's front page.

Prior-Art Analysis — US Patent 8,266,266 B2

A note on scope and sourcing

Two things to flag up front, per the operating rules:

1. Date discrepancy. Your instruction states the current date as April 26, 2026; my environment clock reads October 1, 2026. I have not silently reconciled these — treat the analysis as current as of the environment date.
2. Source limitation. I was asked to search "the USPTO database." My available tool is a general web search; the searches resolved to USPTO-derived mirrors and aggregators (Google Patents, uspto.report, Justia, Docket Alarm, Unified Patents), not a direct PatentCenter / Patent Application Information Retrieval (PAIR) or Public Search query. I therefore could retrieve the patent's bibliographic data and its "References Cited" list, but not the examiner's applied-rejection record (the X/Y/A category tags and the specific § 102/§ 103 rejections applied during prosecution). I state that limitation explicitly rather than inventing an examiner's rationale.

I also note that the previously generated "Litigation summary" section supplied to me consists only of process narration and contains no findings — I cannot build on substantive conclusions from it because none were stated.

B. Patent identification (literal, no auto-correction)

Key point for prior art: the effective prior-art cutoff is 1998-12-08. Because 8,266,266 is a continuation of application 09/693,060 (which issued as US 7,194,554 B1), family members issued after that date (US 8,713,641; US 7,194,554; US 6,636,894) are co-owned family, not § 102 prior art, and any reference in the specification to 08/816,174, 09/458,569, 09/458,579, 09/458,602, or provisional 60/161,093 is likewise related-application material, not prior art.

C. The claim set (mapped from the specification, with caveat)

I could not retrieve the exact granted claim text of 8,266,266 from the mirrors. What the specification supplies are six to eight distinct invention summaries that the claims almost certainly track. I map prior art to those claim families, not to invented claim numbers:

• Family 1 — Network-access AAA method/system: receiving at a gateway device a request; identifying an attribute of the source from a packet; accessing a source profile database external to the gateway device; determining access rights; (optionally RADIUS/LDAP).
• Family 2 — Redirection method: redirecting a source/computer through the gateway to a portal page or login page.
• Family 3 — Transparent-communication system: computer + network gateway device + service-provider network with an external authentication server holding a source-profile database.
• Family 4 — Dynamic new-user creation: entitlement check against a user profile; redirect to login page; update profile.
• Family 5 — Accounting: historical logs, accounting start/stop, billing.

Caveat: exact independent-claim numbering must be verified against the granted document; the mapping below should be read as "claims directed to…", not as confirmed numerals.

D. Cited prior art — closest references

The "References Cited" list on 8,266,266 is very large (well over 400 U.S. patent documents spanning US 4,720,783-era through the 1990s, plus foreign and non-patent items). Below are the references that are substantively closest to the claim families, with the data I could actually confirm. Dates are the U.S. grant dates as listed.

Also cited (non-patent / procedural items), worth noting:

• The RADIUS specification line (Rigney et al., IETF RFC 2138, 1997) is the natural NPL anchor for the claims reciting a "RADIUS database."
• The Nomadix "Nomadic router/translator" material (FIGS. 3–15 of 8,266,266) is the applicant's own disclosure, not prior art.

E. § 102 anticipation analysis (feature-based)

Because I could not retrieve the examiner's applied rejections, the following is my own § 102 mapping — i.e., references that, on their face, disclose each claimed element. A reference anticipates only if it discloses all elements of a claim; several below are closer to § 103 (obviousness) candidates when combined.

F. What I could not verify (stated rather than fabricated)

• The exact published claims of 8,266,266 and their numbers — I could not retrieve them from the mirrors, so the "which claim(s)" mapping above is family-level, not numeral-level.
• The examiner's applied § 102/§ 103 rejections and the X/Y/A category assignments for 8,266,266 specifically. The searches returned category-tagged search reports for other patents (e.g., WO2013041902A1, JP2008543231A), which are not 8,266,266 and must not be attributed to it.
• The specific prior art raised in the three PTAB proceedings identified on the family (IPR2016-00077 — settled; IPR2018-00376 — not instituted on the merits; IPR2018-01668 — not instituted on procedure). Petitioners' exhibits are not reliably retrievable here, so I am not naming references from those petitions.
• Descriptions for entries marked "low confidence" (US 5,898,830, US 5,796,952, US 5,858,812) — confirm against the actual documents before relying on them.

If you can provide the granted claim text of US 8,266,266 (or PAIR access), I can convert Section E into a claim-by-claim § 102/§ 103 chart with specific numerals.

I'll ground the prior-art record before building the §103 analysis. Let me pull the citation/prior-art tables for this patent and the related IPR grounds.

Good — the RADIUS RFCs and the cited U.S. patent list are now grounded. Let me pull the actual IPR petition grounds and the content of the key references so I can name specific combinations rather than speculate.

Obviousness Analysis — US 8,266,266 B2 (35 U.S.C. § 103)

Scope note on "the Prior Art section of this page." The Google Patents record I was given for US 8,266,266 did not render its "Citations / References Cited" tables in the fetched text — those sections were stripped, leaving only the narrative specification, the "Definitions" block, and a handful of in‑specification citations (RFC 2002 Mobile IP; U.S. app. 08/816,174; provisional 60/161,093; the two Redirection Applications). I therefore reconstructed the prior‑art corpus from three verifiable sources and flag the provenance of each: (a) the certificate‑of‑citation list for US 8,266,266 itself (uspto.report/patent/grant/8266266); (b) the References‑Cited list of the sibling patent US 9,548,935, which shares the identical 12/685,585 lineage (US9548935.pdf); and (c) the litigation/IPR record in Nomadix v. Hospitality Core Services (C.D. Cal. 2:14‑cv‑08256) and IPR2016‑00077 / IPR2018‑00376. Claim groupings below are carried over from the earlier section (only claim 1's number is confirmed there); I do not re‑derive them.

1. Legal frame and the effective‑date problem (threshold issue)

The Graham/KSR inquiry turns first on the critical date. The '266 lists a priority date of Dec. 8, 1998 (provisional 60/111,497), but it issued from a continuation‑in‑part chain ('554 filed Oct. 20, 2000, CIP of the Dec. 8, 1999 '894/'602 applications). Any limitation not supported by the earlier disclosure is entitled only to Oct. 20, 2000. This matters because Blueprint RF expressly alleged Nomadix failed to disclose material art including WO 98/40990 (Short PCT, published Sept. 17, 1998) and the Kleinrock papers (2:14‑cv‑08256, dkt. 69). If any asserted claim is entitled only to the CIP date, WO 98/40990 falls more than one year before it and becomes pre‑AIA § 102(b) art usable as § 103 predicate — an applicant's own publication is not exempt. I could not verify from the retrieved materials (i) the exact priority date the Office accorded each of the 28 claims, or (ii) the substantive content of WO 98/40990 or the Kleinrock papers; both should be confirmed in the file wrapper before any of that roadmap is relied on.

The safe course is to build the § 103 case on references that predate Dec. 8, 1998 itself, so the grounds hold regardless of how the priority contest resolves.

2. The "clean‑date" prior‑art set

Caveat: I could not verify the publication dates or full content of the ATCOM/IPORT papers or the Slemmer provisional; portions of that family may post‑date even the earliest priority date and may be § 102(e) art only. The grounds below are ordered from strongest (clean‑date references only) to weakest.

3. Grounds of rejection

Ground 1 — Claim 1 and the "system counterpart" family: RFC 2138 + RFC 2139 + Levergood

Mapping. RFC 2138 supplies: (i) a gateway‑side client (the NAS) that receives a request for network access and forwards identification data; (ii) identification of the source by attributes carried in the request (User‑Name, NAS‑IP‑Address, NAS‑Port, Calling‑Station‑Id); (iii) a source‑profile database external to the gateway ("a single 'database' of users"); and (iv) access rights defining the rights of the source to access a requested destination — the Filter‑Id/filter‑list mechanism is literally per‑user destination/content filtering, and the server "can also specify the client(s) or port(s) to which the user is allowed access." RFC 2139 supplies the accounting limbs. Levergood supplies the missing "transparent access / no configuration software" element: proxy‑intermediated identification and authorization with nothing installed on the client.

Motivation. The specification itself concedes the database is conventional — it states the AAA server "can comprise a Remote Authentication Dial‑In User Service (RADIUS) or a Lightweight Directory Access Protocol (LDAP) database, which are well known to those of skill in the art," and describes "conventional subscriber databases" as already storing cost and elapsed time. That is an applicant admission that collapses the gap. Under KSR, this is the paradigm case of "us[ing] a known technique [centralized AAA] to improve a similar device [an access gateway] in the same way," with a predictable result.

Likely rebuttal and its weakness. Patent Owner would argue RADIUS is a dial AAA protocol and says nothing about a gateway performing transparent packet‑address translation or identifying a source by MAC/VLAN/circuit ID. That is a real gap and is why Ground 1 alone is probably insufficient for the dependent claims reciting those attributes; Ground 2 is needed to close it.

Ground 2 — Claim 1 + redirection/portal families: Levergood + Slemmer/ATCOM‑IPORT

Mapping. Levergood supplies the HTTP interception → redirect → login page → cookie/session → authorization loop that the redirection and "new user" claims recite. The ATCOM/IPORT record supplies a venue (hotel) gateway that performs exactly this in the claimed environment, and Blueprint's contention charts map the '266 to those papers. The combination therefore reads on: receiving the request at the gateway; redirecting to a portal/login page while the computer "remains configured for accessing the home network"; and the gateway‑local login page.

Motivation. Both references are in the same field (public/venue network access control), address the same problem (gate a paying or authorized user), and the '266 specification describes hotels, airports and multi‑dwelling units as the target venues — i.e., the art was ready for improvement and the market supplied the design incentive (KSR rationales (C) and (D)). Combining a known proxy‑redirect access‑control front end with a known venue gateway is a predictable arrangement of known elements.

Weakness. The particular mechanism the '266 claims for making redirection transparent — Stack Address Translation and Home Page Redirect, with the gateway "appearing to be" the destination server — is more specific than generic proxy redirection. The '246 claim 6 litigation turned precisely on those terms (dkt. 142, Jan. 27, 2016), which signals the fight line for the '266 portal claims as well.

Ground 3 — Differentiated per‑source / per‑destination authorization: Kalkbrenner + RFC 2138 + Levergood

Mapping. The claims reciting that "a first source [is permitted] to access a particular Internet destination address, while … a second source [is refused] access to that same address," and that a source's bandwidth or homepage may vary, are met by Kalkbrenner's per‑user QoS differentiation in distributed hypermedia, combined with RFC 2138's Filter‑Id/Service‑Type per‑user configuration. Kalkbrenner is the reference Blueprint actually pleaded against the '266 (IPR2016‑00077 petition, Oct. 27, 2015).

Motivation. Where a network operator already assigns per‑user service profiles in the AAA server (RFC 2138) and per‑user QoS is known in hypermedia delivery (Kalkbrenner), applying the QoS profile at the gateway is the simple substitution of one known element for another to obtain a predictable result.

Ground 4 — Accounting claims: RFC 2139 + Moen ('537) + Biggs ('740)

Mapping. "Historical data relating to the duration of network access for use in determining the charges due" is met by RFC 2139's Accounting‑Request start/stop with time stamps and elapsed‑time/byte attributes, in the billing context of Moen (billing users for communicating over a network) and Biggs (telephone‑call‑record billing). The '266 specification even names implementations ("Eclipse Internet Billing System … TRU RADIUS Accountant"), i.e., admitted prior products.

Motivation. Combining a standard accounting protocol with known network‑usage billing models yields nothing more than the predictable aggregation of usage records — KSR rationales (A) and (B).

Ground 5 — "New user" / login‑page claims: RFC 2138 (Access‑Challenge) + Levergood

Mapping. "Redirecting the user to a login page when the user profile does not include rights" is met by Levergood's login redirect, and RFC 2138's Access‑Challenge/Reply‑Message mechanism is a standardized "ask the unidentified user for more information, then accept or reject" flow. Prompting an unknown user for credentials/billing data before granting service is the ordinary, expected behavior of both references.

Ground 6 — Portable "nomadic router" family: RFC 2002 (Mobile IP) + RFC 2131 (DHCP) + Shuen ('528)

Mapping (weaker). The five claimed modules — store the user's communication address; detect the network location; detect attached communication devices; convert the location address to the user's address; auto‑select a detected device — map onto Mobile IP's home‑address/care‑of‑address mapping and agent discovery, DHCP's automatic configuration, and a multi‑homed device with interface selection.

Motivation and its limits. The '266 specification admits that "The Internet RFC 2002 Mobile IP protocol specifies the mapping between permanent and temporary IP addresses," then distinguishes the invention on the ground that "the Mobile IP protocols are not necessarily running in, or supported by, the host CPU but rather are internal to the nomadic router." That is a genuine argument that the placement of the mobility function in a portable intermediate device was not suggested. A petitioner would need art showing a proxy‑positioned mobility translator (including the proxy‑ARP interception the specification describes) to make this ground work; I did not locate such a reference in the retrieved record, and I would not assert this ground without it. I also note the related risk: the nomadic‑router disclosure appears in the '266 specification largely as background, and if it originates in Nomadix's own earlier WO 98/40990 filing, the priority‑date question in § 1 becomes decisive for this family.

4. Counterweights the analysis must carry

1. The '266 has never been held obvious. IPR2016‑00077 was terminated by settlement (no estoppel, no merits holding); IPR2018‑00376 was not instituted on the merits; IPR2018‑01668 was not instituted on procedural grounds. Blueprint's partial‑SJ invalidity motion was directed only at claims 6–7 of the '246 patent (Stubblebine Decl. ¶ 52), so the '266's merits were not adjudicated there either. Any obviousness conclusion here is a paper assessment, not a record holding.
2. Secondary considerations. Hospitality‑industry commercial success, adoption across hotels/airports, and long‑felt need were squarely asserted. A nexus to the claimed transparent‑gateway features could rebut even a strong prima facie case.
3. The enforceability overlay. Blueprint's counterclaim alleged inequitable conduct and prosecution laches for the alleged non‑disclosure of WO 98/40990 and the Kleinrock materials. If proven, unenforceability would moot § 103 — but it is not § 103, and the earlier settlement may have resolved it.
4. Scope differentiation survived one attack. Stubblebine's ¶ 51 position (that claim 1 of the '266 differs in scope from claim 6 of the '246, defeating same‑invention double patenting) suggests the '266's claim 1 has a somewhat distinct footprint from claim 6 of the '246 — useful to Patent Owner but not dispositive of § 103.

5. Bottom line

• Strongest § 103 ground: RFC 2138 + RFC 2139 + Levergood (5,708,780) against claim 1 and the AAA/accounting families — the AAA‑server‑external‑database and per‑source access‑right limitations are (a) squarely disclosed by RADIUS and (b) admitted as conventional in the '266 specification itself.
• Strong second ground: Levergood + Slemmer/ATCOM‑IPORT against the redirection/portal and "new user" families, with Kalkbrenner added for the differentiated‑authorization claims.
• Weakest ground: the portable "nomadic router" claims, which likely require art showing a proxy‑positioned translator, plus a resolution of the WO 98/40990 priority question.
• Unresolved and potentially outcome‑determinative: the per‑claim priority date, and the content/dates of the Slemmer provisional, ATCOM/IPORT papers, Kalkbrenner, WO 98/40990 and the Kleinrock papers. I could not verify any of these from the fetched record, and I flag them rather than assume them.