US 8266269

I'll search for authoritative information on US 8266269 and check for any 2026 CAFC activity.

Let me check for any recent USPTO/PTAB or 2026 appellate activity specific to this patent.

Let me try to retrieve the actual claim language for the independent claims.

US Patent 8,266,269 — Analyst Summary

Sources: Google Patents (patents.google.com/patent/US8266269B2/en), FreePatentsOnline, Unified Patents portal, Docket Alarm (PTAB), Justia. Searches were run against the patent number literally ("8266269" / "8,266,269"); results for other Nomadix family members (e.g., 8,266,266; 8,364,806; 8,156,246; 8,788,690) are flagged as related but distinct.

Bibliographic data (as reported)

Abstract (verbatim, per the patent record)

"Systems and methods for managing and providing content and services on a network system. Aspects of the invention include controlling user perceived connection speed. Other aspects of the invention include authorization and authentication components that determine access rights of client computers. Additional aspects include systems and methods for directing client computers to select connection speed. The disclosed systems and methods may be used in numerous network system applications."

Plain-language overview of the invention

The specification describes a gateway/network-management system that sits between client computers (e.g., hotel rooms, MDUs, airports, kiosks) and external networks. The gateway transparently configures clients (DHCP, Proxy ARP, stack address translation) so no client-side reconfiguration is required, performs Authentication/Authorization/Accounting (AAA) using attributes such as MAC address, user ID, circuit ID, or VLAN ID against an internal or external (RADIUS/LDAP) profile database, and redirects clients to portal/login pages. Notably, the specification's "Summary of Invention" also covers location-based content delivery: receiving a content request, producing alternate content based in part on a physical-location identifier (e.g., a specific hotel room, suite, or terminal), and returning that alternate content in response to the request.

Independent claims — overview

Important limitation on this answer: the authoritative full text supplied to me truncates in the Detailed Description and does not include the numbered claims, and my searches did not surface the verbatim claim set. I therefore cannot reproduce exact claim numbers or wording with confidence, and I will not fabricate them. Based on the patent's own "Summary of Invention" and the Abstract, the independent claims are directed to at least the following subject matter:

1. A method of managing network access of a client computer connected to a network-management system — receiving data packet(s) containing a request for network content from an external server; determining authorization rights associated with the client computer (based on a user profile selected from a user-profile database connected to the system); when the rights indicate the client is not entitled to the requested content, producing a redirection response that (a) causes the client to request network content at a different location than the external server, and (b) is configured to appear as though it originated from the external server; and transmitting that redirection response back to the client in response to the content request.

2. Location-based content delivery subject matter (from the Summary) — receiving a content request from a client, producing alternate content based in part on a physical-location identifier received in association with the request, and transmitting the alternate content to the client, where the alternate content may differ from the requested content and the location identifier may originate from an intermediary network device.

Additional independent claims in the family/specification context address dynamic AAA (attribute-based identification of a source, external source-profile database, determining access rights to a requested destination) and transparent redirection to portal/login pages without client reconfiguration. I cannot confirm how many independent claims exist in the '269 patent or their exact scope without the claim text.

CAFC 2026 docket search — result

No 2026 Court of Appeals for the Federal Circuit activity specific to U.S. 8,266,269 was found. Searches of the Federal Circuit's 2026 argument calendars and general docket references returned no case involving this patent number. This is consistent with the record: the patent's last PTAB proceeding (IPR2016-00081) was resolved by settlement, its district-court assertion (C.D. Cal. 2:14-cv-08256) is from 2014–2016, and the patent reached its anticipated expiration in December 2019 and is now marked "Expired – Fee Related." I cannot rule out a non-public or very recent filing, but I found nothing authoritative indicating a pending 2026 appeal.

Uncertainties / caveats

• Current assignee is ambiguous in the records. Google Patents' header lists "Gate Worldwide Holdings LLC" as current assignee, but the recorded assignment history shows Gate Worldwide Holdings LLC quitclaimed the patent back to Nomadix, Inc. on 2019-11-22. Treat "current assignee" with caution pending USPTO Assignment records.
• I could not retrieve the verbatim claim set of the '269 patent, so the independent-claim overview above is derived from the patent's Summary/Abstract and is flagged as such.
• Related but distinct Nomadix patents frequently appearing alongside '269 include 6,636,894; 8,156,246; 8,266,266; 8,364,806; 8,725,888; and 8,788,690 — these are not the patent requested and were not conflated with it.

I'll research litigation involving US Patent 8266269 across patent litigation databases and news sources.

Let me search more specifically for Nomadix's litigation campaigns and the specific patent.

Let me dig deeper into the specific case and the IPR, and check for any other suits asserting the '269 patent.

Litigation Involving U.S. Patent No. 8,266,269

Important identification note: U.S. Patent No. 8,266,269 ("the '269 patent"), titled "Systems and methods for providing content and services on a network system," is a Nomadix, Inc. "captive portal"/gateway patent that issued September 11, 2012 from Application No. 13/329,867 (filed December 19, 2011), claiming priority to 1998. It is distinct from the similarly numbered U.S. Patent No. 8,266,266 ("the '266 patent") and U.S. Patent No. 8,156,246 ("the '246 patent"), which are separate patents frequently asserted alongside it. The results below are limited to the '269 patent as specified.

1. District Court Litigation

Nomadix, Inc. v. Hospitality Core Services LLC, d/b/a Blueprint RF

Details: The '269 patent was one of seven Nomadix patents asserted against Blueprint RF's "Dominion" gateway devices. The other asserted patents were U.S. Patent Nos. 6,636,894 ('894), 6,868,399 ('399), 8,156,246 ('246), 8,266,266 ('266), 8,364,806 ('806), and 8,788,690 ('690). Blueprint RF counterclaimed for declaratory judgment of non-infringement, invalidity, and unenforceability (inequitable conduct/prosecution laches), describing the '894, '246, '266, '269, and '806 patents as the "captive portal" patents.

Key rulings:

• April 3, 2015 – Court denied Blueprint's motions to dismiss (Dkt. 34, 35).
• June 29, 2015 – Court granted in part and denied in part Nomadix's motion to dismiss/strike counterclaims and defenses (Dkt. 69).
• January 27, 2016 – On cross-motions for summary judgment (Dkt. 142), the Court granted Nomadix's motion for summary judgment of infringement of the '246 patent, denied Blueprint's cross-motion of non-infringement, and denied Blueprint's motions for partial summary judgment of invalidity under 35 U.S.C. § 112 (written description/enablement/double patenting) and §§ 102/103.
• June 28, 2016 – The parties filed a Joint Stipulation to Dismiss pursuant to Fed. R. Civ. P. 41(a)(1)(A)(ii) and 41(c).
• June 30, 2016 – Report on the Determination of an Action Regarding a Patent or Trademark (Closing) entered; the case was terminated.

2. PTAB Post-Grant Proceedings

Hospitality Core Services, LLC v. Nomadix, Inc., IPR2016-00081

Details: This IPR was filed by Blueprint RF against the '269 patent in parallel with the district court case. Blueprint RF simultaneously petitioned for review of related patents also at issue in 2:14-cv-08256:

• U.S. Pat. No. 6,636,894 – IPR2016-00052
• U.S. Pat. No. 8,156,246 – IPR2016-00073
• U.S. Pat. No. 8,266,266 – IPR2016-00077
• U.S. Pat. No. 8,364,806 – IPR2016-00092

The '269 IPR was instituted/co-pending and then resolved by settlement, consistent with the June 2016 stipulated dismissal of the district court case.

3. Related (but NOT '269 patent) Nomadix Litigation — for context only

The following Nomadix suits are frequently cited but involved different patents, and several predate the '269 patent's September 11, 2012 issuance:

• Nomadix, Inc. v. Second Rule LLC, No. 07-cv-01946 (C.D. Cal.)
• Nomadix, Inc. v. Hewlett-Packard Co. et al., No. 09-cv-08441 DDP (VBKx) (C.D. Cal.)
• Nomadix, Inc. v. SolutionInc Technologies Ltd., No. 10-cv-00381 DDP (VBKx) (C.D. Cal.)
• iBAHN General Holdings Corp. v. Nomadix, Inc., No. 11-cv-02604 (C.D. Cal.) / Nomadix, Inc. v. iBAHN General Holdings Corp., No. 14-cv-00322 (C.D. Cal.)
• IP3 Networks, Inc. v. Nomadix, Inc., No. 04-cv-01485 (S.D. Cal.)
• Nomadix, Inc. v. Guest-Tek Interactive Entertainment Ltd., No. 2:19-cv-04980-AB-FFM (C.D. Cal.) — a contract/forum-selection dispute concerning PTAB challenges (9th Cir. No. 20-55439); the record referenced the '857 and '922 patents, not the '269 patent.

4. Litigation Summary

• Total known district court cases asserting the '269 patent: 1 — Nomadix, Inc. v. Hospitality Core Services LLC d/b/a Blueprint RF, No. 2:14-cv-08256 DDP (VBKx) (C.D. Cal.), filed 10/24/2014, terminated by stipulated dismissal 06/28–30/2016.
• Total known PTAB proceedings on the '269 patent: 1 — IPR2016-00081, Hospitality Core Services, LLC v. Nomadix, Inc., terminated by settlement.

Caveats / Limitations

The Google Patents family-litigation entry for US8266269 links only to the California Central District Court case 2:14-cv-08256 and PTAB IPR2016-00081, which is consistent with what I found. However, I was unable to run exhaustive PACER, Docket Alarm, RPX Empower, or Unified Patents case-list searches within this session, so I cannot guarantee the list is complete. I found no indication of any Federal Circuit appeal, ITC Section 337 investigation, or additional district court case specific to the '269 patent. The ownership chain (Nomadix → NTT DOCOMO security interests → Gate Worldwide Holdings → back to Nomadix) reflects security/assignment transactions, not separate litigation. If you need a definitive, verified list, a direct PACER and PTAB (PTACTS) docket query on "8,266,269" is recommended.

I'll start by verifying the structured data against public sources, since the ODP block says "none" but the earlier litigation section identified IPR2016-00081.

Let me confirm the termination order and check whether any other AIA proceeding (CBM/PGR/other IPR) exists on this patent.

Let me check whether any other petitioner (e.g., Guest-Tek) filed an IPR on the '269 patent, and confirm the institution date.

PTAB / AIA Trial Proceedings — U.S. Patent No. 8,266,269

⚠️ Data-integrity flag before anything else. The structured "PTAB proceedings on file" block in this prompt says the USPTO ODP API returns no AIA trial proceedings for this patent. That is contradicted by the public record. A fully documented IPR — IPR2016-00081 — exists on this exact patent (docket sheets, institution decision, exhibits, and a termination judgment are all publicly posted). I am therefore treating the ODP "none" result as an ingest/indexing gap, not a substantive fact, and flagging the contradiction rather than repeating it. The canonical proceedings list below is built from the primary documents I could retrieve.

⚠️ Second flag — correction to the earlier "Patent summary" section. That section speculated the independent claims were method claims about managing network access. The Board's institution decision in IPR2016-00081 reproduces claim 1 verbatim, and claim 1 is a system claim: "A system for performing redirection of a user device attempting to communicate through a network, comprising: a network access management system including at least one processor and at least one communications port configured to communicate on a network; the network access management system configured to send connection handshake completion data to a user device in…" (text truncated in the source snippet). The prior section's method-claim characterization should be considered superseded.

Proceedings overview

One (1) AIA trial proceeding has ever been filed against U.S. 8,266,269: IPR2016-00081, terminated by settlement before any Final Written Decision — zero claims invalidated, zero claims sustained, all 20 claims untested on the merits.

Breakdown by status:

Bottom-line defensive posture: The patent is neither "dead" nor "hardened." Unlike a patent with a canceling FWD, there is no claim-level holding anyone can point to, and unlike a patent that survived a merits trial, there is no PTAB validation to overcome. Critically, because the proceeding ended by settlement without a Final Written Decision, no § 315(e)(2) estoppel attached to the petitioner. A defendant asserted today faces an open, uncontested validity landscape — but must also reckon with the fact that the patent expired 2019-12-08, which moots most prospective-injunction/gap-closing strategies and leaves only past-damages exposure.

IPR2016-00081 — 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 (petition filed; notice of filing date accorded 2015-11-09)

• Status: Terminated by settlement. Joint Motion to Terminate filed 2016-06-28; Board Judgment — Termination Pursuant to Settlement entered 2016-07-27. Terminated without rendering a Final Written Decision (37 C.F.R. §§ 42.5(a), 42.71(a), 42.73(a), 42.74).

• Judge panel: Administrative Patent Judges Howard B. Blankenship, Glenn J. Perry, and Trevor M. Jefferson; opinion authored by Judge Perry. (Same panel presided over the termination judgment and the companion proceedings IPR2016-00077 and -00092.)

• Patent Owner's counsel: Knobbe, Martens, Olson & Bear, LLP (Doug G. Muehlhauser; Mark Lezama). Petitioner's counsel: Mehrman Law Office, PC (Michael J. Mehrman) and Smith, Gambrell & Russell, LLP (Stephanie D. Scruggs).

• Petition grounds: All challenged claims 1–20, on three grounds as summarized in the Board's own table:

  Reference(s)	Basis	Claims
  Slemmer	§ 102(e)	1–20
  Slemmer and Vu	§ 103(a)	1–20
  Slemmer, IPORT, and Applegate	§ 103(a)	1–20

  The petition also dedicated argument to why the alternative grounds were "not redundant," and attacked the '269 patent's priority/§ 119(e) benefit chain, drawing on the '894 reexamination history (Control Nos. 90/007,220 and 95/001,831).

• Institution decision: Instituted 2016-05-05 (Decision Granting Institution, 37 C.F.R. § 42.108). The panel found "a reasonable likelihood that [Petitioner] would prevail with respect to at least one of the challenged claims" under § 314(a), but narrowed the trial to a single ground: "we institute an inter partes review of claims 1-20 based only on the following challenge: claims 1-20 as obvious based on Slemmer and Vu." The Slemmer-alone § 102(e) anticipation ground and the Slemmer + IPORT + Applegate § 103 ground were not instituted.

• Final Written Decision: None issued. This is the single most important fact for a defendant. There is no claim-level verdict — claims 1–20 were challenged, institution was granted on all of them, and then the whole thing dissolved by settlement before the Patent Owner even filed its Response.

• Settlement / termination: The parties stated they had "settled their dispute, executing a confidential settlement agreement" executed 2016-06-13, terminating both the five IPRs (IPR2016-00052, -00073, -00077, -00081, -00092) and the co-pending C.D. Cal. litigation (Nomadix, Inc. v. Hospitality Core Services LLC, No. 14-cv-08256). Per the joint motion, "Petitioner has agreed to no longer substantively participate in any further proceedings in IPR2016-00077, -00081, and -00092." The agreement was filed as Exhibit 2012 and granted business-confidential treatment under 37 C.F.R. § 42.74(c) — its terms are not public. The Board's rationale: "[T]he parties submit that the Board has not decided the merits of the inter partes review, and Patent Owner has not yet submitted its patent owner response to the petition… it is appropriate to terminate each proceeding and enter judgment without rendering a final written decision."

• Appeal: None. No FWD → nothing appealable. No Federal Circuit docket number exists for this patent. (Consistent with the earlier "CAFC 2026 docket search" section, which found no appellate activity.)

• Defensive value: Low as a validity weapon, high as intelligence. The only ground the Board was willing to try was Slemmer + Vu under § 103; the Slemmer-alone § 102(e) anticipation theory did not clear the institution threshold on this record. That is a meaningful signal for a defendant designing an invalidity theory — but it is not a merits holding and has zero preclusive or estoppel effect. Do not cite the 2016-05-05 institution decision as evidence that any claim is invalid or valid.

Strategic summary

Claim status of U.S. 8,266,269 — CANCELED vs. SUSTAINED vs. UNTESTED. There is no canceled claim and no sustained claim. All twenty claims (1–20 per the institution decision, which is the only authoritative claim-scope statement I retrieved) are UNTESTED. The Board never reached the merits. Any assertion that a particular claim "survived IPR" or "was killed in IPR" is false for this patent. (Note: the earlier "Patent summary" could not retrieve the full claim set; the institution decision at least confirms claim 1 as a system claim directed to redirection/handshake emulation, which matches the district court's description of the "captive portal" patents.)

Estoppel landscape — the good news for a defendant. § 315(e)(2) estoppel is triggered by a final written decision, not by institution and not by settlement. Because IPR2016-00081 terminated by joint motion before any FWD and before the Patent Owner's Response, no statutory estoppel arises — not against Hospitality Core Services/Blueprint RF, and a fortiori not against any third party. There is therefore no "reasonably could have raised" bar on prior-art grounds as to this patent. Practically: the entire field of prior art (including Slemmer, Vu, IPORT, Applegate, and the Brendel / RFC 1919 / transparent-proxy references Blueprint pressed in district court) is still available to anyone, including a new petitioner. Note that the earlier district-court validity attack on the '269 patent — part of Blueprint's § 112 and §§ 102/103 partial summary judgment motions in No. 14-cv-08256 — was denied by Judge Pregerson on 2016-01-27, and the inequitable-conduct counterclaims survived dismissal (Order at Dkt. 69, 2015-06-29) before the case settled. Those are unadjudicated threads, not wins.

Pattern signals. (1) No repeat petitioner on this patent — Hospitality Core filed exactly one IPR against the '269, paralleled by four IPRs against sibling patents ('894 = IPR2016-00052, '246 = IPR2016-00073, '266 = IPR2016-00077, '806 = IPR2016-00092). The whole campaign settled at once, so all five were resolved on identical terms. (2) The patent owner never had to defend the merits here. Nomadix settled at the earliest permissible post-institution moment and, notably, induced a confidential agreement — a posture consistent with resolving rather than winning. (3) No defensive aggregator on this patent. The "Petitioner: Unified Patents PTAB Data" line you may see on the Google Patents family-litigation pane is a data-source attribution for the litigation feed, not a Unified Patents-filed challenge. Unified Patents did not petition against the '269. Do not report it as a petitioner. (4) Guest-Tek later waged an extensive IPR campaign against other Nomadix patents — IPR2019-00211 ('857), IPR2019-00253 ('922), IPR2018-00376, IPR2018-00392, IPR2018-01660 ('899), IPR2019-01191 — but on my searches none of those is an IPR against the '269. I flag one loose end below.

Unverified lead (do not rely on without checking). Docket Alarm lists IPR2019-01191 (Guest Tek Interactive Entertainment Ltd. v. Nomadix, Inc., filed 2019-06-18, judges Hagy/McNeill/Medley, Institution Denied, Tech Center 2400, Art Unit 2449) with inventors listed as Florence C.I. Pagan, Joel E. Short, Josh J. Goldstein — the same inventive entity as the '269. That inventor overlap makes it worth a direct PTAB look-up to confirm which Nomadix patent claims it targeted. I could not confirm the patent number from the snippet, and the patents litigated in the parallel Nomadix v. Guest-Tek dispute (C.D. Cal. 2:19-cv-04980) were the '857 and '922 patents. Do not list IPR2019-01191 as a '269 proceeding until the patent number is verified.

Recommended next steps

1. If you are a defendant asserting invalidity: you have no FWD to point to, so you cannot argue issue preclusion or § 315(e) estoppel. Your best artifact is the 2016-05-05 institution decision, which tells you the Board credited a Slemmer + Vu § 103 theory against claims 1–20 but declined Slemmer-alone § 102(e). That is a roadmap for a fresh petition (subject to the ordinary § 325(d) discretion, which now applies to a settled rather than denied case and is much weaker).
   • Institution decision (PDF): https://www.docketalarm.com/cases/PTAB/IPR2016-00081/Inter_Partes_Review_of_U.S._Pat._8266269/docs/05-05-2016-Board/Decision_Granting_Institution-11-Decision_Granting_Institution.pdf
   • Full docket: https://www.docketalarm.com/cases/PTAB/IPR2016-00081/Inter_Partes_Review_of_U.S._Pat._8266269/
2. If you are a defendant weighing cost: the patent is expired (anticipated expiration 2019-12-08) and marked "Expired – Fee Related." No injunction is available for future conduct; exposure is limited to past damages within the § 286 six-year look-back and any ongoing royalty obligations under an existing license. That usually argues for a damages/§ 101/§ 112 posture, not a PTAB spend. A fresh IPR on an expired patent is almost never cost-justified unless needed to defeat a live past-damages claim or a related-claim family member.
3. If you need a definitive docket: query PTAB E2E / P-TACTS directly for "8,266,269" (https://ptacts.uspto.gov) to confirm the ODP gap, and pull the termination judgment for the joint-treatment of IPR2016-00077 / -00081 / -00092: 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
4. Do not represent the settlement terms. Exhibit 2012 is under a § 42.74(c) business-confidential order. Any statement that Nomadix "paid," "took a license," or "conceded" is unsupported by the public record.
5. Verify the IPR2019-01191 patent number (item above) before closing the "other proceedings" question.

Bottom line for the client: One IPR, filed 2015-10-27, instituted on claims 1–20 solely on Slemmer + Vu, and killed by settlement on 2016-07-27 with no Final Written Decision and no estoppel. All 20 claims are untested; the patent expired in 2019. There is no PTAB win to inherit and no PTAB loss to fear — the patent's AIA history is a blank sheet.

I'll research the assignment record for US 8,266,269, starting with USPTO Assignment Center and cross-referencing the recorded events.

Let me search for the specific recorded assignment documents and reel/frame numbers.

Assignment & Ownership Analysis — US 8,266,269

Critical sourcing caveat up front: My tool access in this session is search-only and the USPTO Assignment Center (assignment.uspto.gov / assignmentcenter.uspto.gov) is a JavaScript application whose per-record reel/frame, correspondent-of-record, and execution dates are not surfaced in search snippets. I retrieved the chain of recorded events for the '269 patent from the Google Patents "Legal Events" ledger (which mirrors USPTO assignment records and was part of the authoritative full text supplied for this analysis), but I could not independently pull the reel/frame numbers or the correspondent fields. I will not fabricate reel/frame values. Every reel/frame slot below is explicitly marked [not retrieved], and the reader should verify at the Assignment Center link given in the Verdict. This limitation is a data-access issue, not a statement that records are missing — the '269 patent does have a populated assignment history.

Inventors

• The three named inventors are the same inventive team that recurs across the Nomadix gateway family (e.g., the sibling '266, '806, and '246 patents asserted alongside '269 in the Blueprint RF case). This is a single-team, single-company portfolio, not a mixed-provenance one.
• Unusual patterns: No evidence in the assignment record of inventors departing the original assignee within 12 months of filing, and no pre-issuance inventor-to-third-party assignments. Note that the '269 application (13/329,867) is a 2011 continuation of 1998/1999 work, so the inventors' original employment relationship with Nomadix dates to the company's founding era rather than to the 2011 filing date. I cannot confirm departure dates from the records available to me.

Original assignee

Nomadix, Inc. (a Delaware corporation), as stated on the issued patent and confirmed by the USPTO Power of Attorney for the related family, which recites "Nomadix, Inc., a Delaware Corporation, is the Assignee of the entire right, title, and interest."

• Product embodiment: YES — Nomadix shipped commercial gateway products (its Universal Subscriber Gateway / access-gateway line for hotels, MDUs, airports, and venues). Nomadix's own product-patent listing (nomadix.com product patent PDF) expressly lists 8,266,269 among the patents that "may be covered by" its products. This is dispositive that the original assignee is an operating company, not a licensing shell.
• Primary line of business: network access / subscriber-management gateway hardware and software for hospitality and venue networks (captive-portal access control, bandwidth management, AAA).
• Current status: Operating, and — per the closing records below — the current owner again after the 2019 quitclaim/release. Nomadix has been an active enforcer (BluePrint RF, Hewlett-Packard/Aruba/Wayport, Second Rule, iBAHN, Guest-Tek), i.e., it asserts and licenses while still shipping product.

Assignment timeline

Chronological, from the Google Patents Legal Events ledger for US 8,266,269. Execution dates were not retrievable; the dates shown are the recorded/event dates as published. Reel/frame and correspondent could not be retrieved (see caveat).

• Recorded 2015-09-30 — Reel [not retrieved]

  • Conveyance: Security Interest (see document for details)
  • Assignor: NOMADIX, INC.
  • Assignee: NTT DOCOMO, INC.
  • Correspondent: [not retrieved]
  • Context: Securitization — Nomadix pledges the portfolio as collateral for financing/security from NTT DOCOMO.

• Recorded 2017-08-29 — Reel [not retrieved]

  • Conveyance: Modification to Patent Security Agreement
  • Assignor: NOMADIX, INC.
  • Assignee: NTT DOCOMO, INC.
  • Correspondent: [not retrieved]
  • Context: Securitization — amendment/reaffirmation of the existing NTT DOCOMO security interest.

• Recorded 2018-01-23 — Reel [not retrieved]

  • Conveyance: Assignment of Patent Security Agreement
  • Assignor: NTT DOCOMO, INC.
  • Assignee: GATE WORLDWIDE HOLDINGS LLC
  • Correspondent: [not retrieved]
  • Context: Securitization transfer — the secured party's interest is assigned from NTT DOCOMO to Gate Worldwide Holdings LLC.

• Recorded 2018-01-23 — Reel [not retrieved]

  • Conveyance: Assignment of Assignors' Interest (see document for details)
  • Assignor: NOMADIX, INC.
  • Assignee: GATE WORLDWIDE HOLDINGS LLC
  • Correspondent: [not retrieved]
  • Context: Financing/standing transfer — an outright assignment of Nomadix's interest to Gate, executed the same day Gate took over the NTT DOCOMO security interest; contemporaneous with the Guest-Tek litigation and a referenced "related New York action."

• Recorded 2019-03-20 — Reel [not retrieved]

  • Conveyance: Security Interest (see document for details)
  • Assignor: NOMADIX, INC.
  • Assignee: KNOBBE, MARTENS, OLSON & BEAR, LLP
  • Correspondent: [not retrieved]
  • Context: Securitization — a law firm (Nomadix's prosecution/litigation counsel of record) takes a security interest, consistent with a lien securing unpaid legal fees.

• Recorded 2019-05-28 — Reel [not retrieved]

  • Conveyance: Release by Secured Party (see document for details)
  • Assignor: KNOBBE, MARTENS, OLSON & BEAR, LLP
  • Assignee: NOMADIX, INC.
  • Correspondent: [not retrieved]
  • Context: Lien release — Knobbe releases its 2019-03-20 security interest back to Nomadix.

• Recorded 2019-11-22 — Reel [not retrieved]

  • Conveyance: Quitclaim
  • Assignor: GATE WORLDWIDE HOLDINGS LLC
  • Assignee: NOMADIX, INC.
  • Correspondent: [not retrieved]
  • Context: Reversal/cleanup — Gate quitclaims its 2018-01-23 interest back to Nomadix, restoring Nomadix as sole owner.

• Original inventor-to-assignee record (related family): The USPTO Power of Attorney filed for the sibling '806 patent (Case IPR2016-00092) recites an inventor assignment to Nomadix recorded 2001-01-22 at Reel 011469, Frame 0538. That record pertains to the earlier family application, not confirmed for the 2011-filed '269 application, which would have its own (later-recorded) inventor assignment. I could not confirm the '269-specific original assignment reel/frame.

Timeline diagram

timeline
    title Ownership of US 8266269
    1998 : Priority date
    2011 : Application filed by Nomadix
    2012 : Patent issued to Nomadix
    2014 : Blueprint RF suit filed
    2015 : Security interest to NTT DOCOMO
    2016 : Blueprint RF case dismissed
    2017 : NTT DOCOMO agreement modified
    2018 : Assigned to Gate Worldwide Holdings
    2019 : Knobbe security interest
         : Release back to Nomadix
         : Quitclaim from Gate to Nomadix
         : Patent expires

NPE / troll-pattern signals

1. Shell-entity transfer — Not present. No assignee bears IP/Holdings/Ventures-shell indicia in the classic sense; the two non-Nomadix assignees are NTT DOCOMO, INC. (a listed Japanese operating telecom carrier) and Knobbe, Martens, Olson & Bear, LLP (a law firm acting as secured party). Gate Worldwide Holdings LLC is the only "Holdings" name, but it took the interest via a security-agreement assignment and returned it by quitclaim on 2019-11-22, which is the profile of a financing counterparty, not a licensing shell. No evidence of a registered-agent-service address or a standalone Delaware/Texas assertion vehicle in the records retrieved.

2. Known asserter in the chain — Not present. None of NTT DOCOMO, Gate Worldwide Holdings LLC, or Knobbe Martens appears on the public NPE directories (Acacia, Marathon, Intellectual Ventures, Wi-LAN/Conversant, Vringo, Pendrell, etc.). The asserting party in every suit is Nomadix itself, an operating company (see signal 3 of the Verdict rationale).

3. Repeat correspondent across the chain — Unclear. I could not retrieve the correspondent-of-record field for any '269 assignment, so I cannot confirm or refute a recurring recording attorney. Circumstantially relevant but not a finding: Knobbe Martens is (a) the assignEE on the 2019-03-20 security interest, and (b) the firm of record for Nomadix's prosecution and litigation (PTO filings in the related IPRs list "KNOBBE, MARTENS, OLSON & BEAR, LLP" as Nomadix's counsel). A single firm doing both operating-company and secured-party work is not an NPE signal; I am not treating it as one.

4. Cascading transfers — Not present (weak/unclear at most). There is a cluster of recordings in 2018–2019, but they are security interests, a secured-party assignment, and releases/quitclaims, not a chain of unrelated LLCs passing title. The one genuine title movement (Nomadix → Gate, 2018-01-23) was reversed to Nomadix (2019-11-22). This is a financing structure, not a shell cascade.

5. Pre-litigation transfer — Not present. The '269 patent's first suit (Nomadix v. Hospitality Core Services LLC d/b/a Blueprint RF, C.D. Cal. 2:14-cv-08256) was filed 2014-10-24; the earliest recorded post-issuance assignment (NTT DOCOMO security interest) is 2015-09-30, i.e., after suit. The 2018-01-23 Gate event falls well outside any 6-month pre-suit window (the Guest-Tek suit was filed 2016-10).

6. Bankruptcy fire-sale — Not present. No Chapter 7/11 proceeding, no trustee sale, and no court-supervised portfolio sale appears in the record. The NTT DOCOMO/Gate/Knobbe events read as secured financing and lien mechanics, not a bankruptcy liquidation.

7. Privateering — Not present. No operating company is transferring to an NPE to sue competitors; the operating company (Nomadix) is doing its own enforcing and, if anything, is the party helping NTT DOCOMO's/Gate's interests get unwound back to it.

8. Defensive aggregator (anti-NPE) — Not present. The chain does not terminate at RPX, AST, LOT, Unified Patents, or OIN. It terminates back at the original operating assignee, Nomadix.

Verdict

Operating-company assertion

The chain runs inventors → Nomadix, Inc. (the operating manufacturer whose own product-patent listing names 8,266,269), interrupted only by security-interest recordings to NTT DOCOMO, Inc. (2015-09-30 security interest; 2017-08-29 modification) and a financing-related assignment to Gate Worldwide Holdings LLC (2018-01-23) with a same-day assignment of the security agreement, plus a lawyer's-fee lien to Knobbe Martens (2019-03-20). Every one of those encumbrances was released or quitclaimed back to Nomadix by 2019-11-22, and the patent's enforcement history is Nomadix suing direct competitors (BluePrint RF, HP/Aruba/Wayport, Guest-Tek) while shipping gateway hardware — the textbook profile of operating-company assertion, not NPE activity. Two caveats: (i) reel/frame numbers and correspondents could not be verified in this session and must be confirmed directly, and (ii) the patent reached its anticipated expiration on 2019-12-08 and is marked "Expired – Fee Related," so the current-listed owner (Nomadix, following the 2019-11-22 quitclaim; note Google Patents' header still displays "Gate Worldwide Holdings LLC," which conflicts with the recorded quitclaim) holds only an expired right.

Verify at: USPTO Assignment Center — https://assignmentcenter.uspto.gov/ (search "8266269") and the legacy portal https://assignment.uspto.gov/patent/index.html. Request the reel/frame PDFs for each of the seven events above to capture the exact execution dates and correspondent-of-record.

Contradiction flagged for cross-reference: The previously generated Patent summary correctly notes the assignee ambiguity ("Gate Worldwide Holdings LLC" in the Google Patents header vs. the 2019-11-22 quitclaim back to Nomadix). This analysis resolves that ambiguity in favor of Nomadix as owner as of 2019-11-22, based on the recorded quitclaim event — but because I could not open the underlying reel/frame documents, treat the "current owner = Nomadix" conclusion as well-supported but pending document-level confirmation.

I'll research the prior-art citations for US 8,266,269. Let me start with the patent's own citation records.

Let me search directly for the patent's cited references and the IPR petition prior art.

I found the IPR references. Let me get the full IPR exhibit list and the patent's own front-page citations.

Prior Art Analysis — U.S. Patent No. 8,266,269

Scope note up front (important). My retrieval for this task did not surface the patent's own front-page "References Cited" listing (the examiner-cited U.S. patent documents). The authoritative full text you supplied truncates in the Detailed Description and omits the front matter and the numbered claims, and the search results returned the specification body, not the citation block. Consistent with the earlier-generated summary, I therefore treat the front-page citation list as not reliably available and will not invent it.

What I could ground authoritatively is better than a bare front-page list in one respect: the prior art actually asserted against the '269 claims in the only adversarial proceeding on this patent — IPR2016-00081 (Hospitality Core Services, LLC v. Nomadix, Inc.) — plus the references Nomadix's litigation opponent identified in the parallel district-court invalidity contentions. Those are the references with probative § 102/§ 103 weight against this patent. Sources are cited below.

A. The prior art actually applied against the '269 claims — IPR2016-00081

From the Petition's exhibit list and the Board's Decision Granting Institution (Paper 11, May 5, 2016), Hospitality contended that claims 1–20 of the '269 patent are unpatentable as follows (docketalarm.com IPR2016-00081 documents; Google Patents family-litigation record):

Reference details

1. Slemmer — U.S. Patent No. 6,226,677 (Ex. 1005, per petition)

• Full citation: U.S. Patent No. 6,226,677 B1 (Slemmer); issued May 1, 2001 (petition exhibit date "5/1/01").
• Effective-date note for § 102(e): The parallel claim charts in the related litigation reference "Slemmer Provisional 60/109,878" (US 9548935 / US 10341243 embedded document lists). Under pre-AIA § 102(e) and § 119(e), the reference's date is its U.S. filing date — here potentially the provisional filing — which must predate the '269's Dec. 8, 1998 priority to qualify. The petition invoked § 102(e), § 102(b), and § 119(e) (petition table of authorities).
• Description: A network access / gateway-system patent to Slemmer relied on by Hospitality as disclosing the gateway redirect/access-control architecture.
• Claim(s) potentially anticipated: Claims 1–20, under § 102(e) (the sole anticipation ground in the Petition).

2. Vu — U.S. Patent No. 5,623,601 (Ex. 1006)

• Full citation: U.S. Patent No. 5,623,601 (Vu); issued April 22, 1997.
• Description: Network security/gateway access-control patent (relied on for the secure gateway / access-control aspects), used only in combination.
• Claim(s) potentially implicated: Claims 1–20, but only under § 103(a) as combined with Slemmer — not a standalone § 102 reference.

3. IPORT White Papers — ATCOM/INFO (Ex. 1007 and Ex. 1008)

• Full citations: (a) "IPORT Internet Access System – Connection Methods and Concepts for IPORT v2.x," White Paper, ATCOM/INFO, November 1998 (Ex. 1007); (b) "IPORT Internet Access System, IPORT Central Office Solution," White Paper, ATCOM/INFO, November 1998 (Ex. 1008). A related "ATCOM Manual" and "ATCOM/IPORT White Papers" are referenced in the district-court claim charts for the '269 patent.
• Description: Printed publications describing a hotel/hospitality Internet access system (guest authentication, redirect, billing) — the closest non-patent "commercial system" art in the family.
• Claim(s) potentially implicated: Claims 1–20, § 103(a) only (a printed publication can also be § 102(a)/(b) art, but the Petition used it in combination).

4. Applegate (third reference in the Slemmer + IPORT + Applegate combination)

• Full citation / date: Not confirmed by the sources retrieved. Hospitality named "Applegate" as the third element of a § 103(a) combination for claims 1–20; I could not retrieve its full citation or date and will not fabricate it. Treat this entry as unverified pending a look at the IPR exhibit list beyond Ex. 1008.

Outcome nuance: The Board instituted review (decision dated May 5, 2016), but the proceeding was later terminated by settlement (Google Patents family-litigation record lists "PTAB case IPR2016-00081 filed (Settlement)"). Because it settled post-institution, there is no final written decision adjudicating Slemmer's § 102(e) anticipation.

B. Prior art identified in the parallel district-court invalidity contentions (context)

In Nomadix, Inc. v. Hospitality Core Services LLC d/b/a Blueprint RF, No. 2:14-cv-08256 DDP (VBKx) (C.D. Cal.), Blueprint RF's invalidity contentions and inequitable-conduct counterclaims raised the following references against the "captive portal" patents including the '269 patent (Justia Dkt. 69 order; Unified Patents document lists for US 8,266,269 / US 10,341,243 / US 9,548,935). These are the candidate § 102/§ 103 references beyond the IPR set:

Illustrative claim charts in the record map these to the family patents, e.g. "Claim Charts, U.S. Pat. No. 6,636,894; 8,156,246; 8,266,269; 8,364,806 with respect to ATCOM/IPORT White Papers, dated Jul. 24, 2015" and the Blueprint RF § 102/§ 103 invalidity motion (Dkt. 87/117/119) that expressly covered the '269 patent. (Note: some of these embedded lists contain transcription errors — e.g., "8,266,265" and "8,264,806" — which I report as they appear in the source and do not auto-correct.)

C. § 102 anticipation assessment (grounded)

• Only Slemmer was asserted as a § 102 (anticipation) reference against the '269 patent, and only under § 102(e), for claims 1–20. All other references were asserted in combination under § 103(a) (Vu; IPORT; Applegate) — i.e., they are not standalone § 102 anticipatory art as applied.
• § 102 basis distinction to keep straight: pre-AIA § 102(e) art is dated by its U.S. filing date (including a provisional under § 119(e)); pre-AIA § 102(b) art requires publication/patenting more than one year before the U.S. filing (here, before ~Dec. 8, 1998, given the 1998 priority). The Nov. 1998 ATCOM/IPORT white papers and the Sept. 1998 WO 98/40990 are therefore within, not beyond, a year of the Dec. 8, 1998 priority — they qualify, if at all, as § 102(a) / § 102(e)-style art rather than § 102(b), unless an earlier effective date applies.
• Claim-scope caveat: The IPR challenged claims 1–20. The '269's independent claim 1 (per the patent's own Summary) is the "managing network access… producing a redirection response… configured to indicate to the computer that the redirection response originated from the external server" claim; the specification also describes location-based alternate-content subject matter. I could not verify the exact number of claims or whether a second independent claim exists, so I cannot state precisely which individual claims Slemmer maps to beyond "1–20."

D. Caveats / limitations

1. I could not retrieve the patent's own front-page "References Cited" (examiner citations). The references above are drawn from the IPR and litigation record, not the printed front page. If you need the literal front-page list, a direct pull of the '269 patent's PDF (patentimages) or Patent Center file wrapper ("Notice of References Cited") is required.
2. "Applegate" citation unconfirmed — named in the Institution Decision's § 103 table but I could not retrieve its full citation/date; treat as unverified.
3. No final merits ruling: IPR2016-00081 was instituted but settled, so Slemmer's § 102(e) anticipation was never adjudicated on the merits.
4. Family conflation risk: The '269 patent is frequently grouped with '266, '246, '806, '690, '894, '399 in claim charts; references asserted against those sibling patents are not necessarily § 102 art for '269 specifically. I have flagged which references were tied to '269 in the record.
5. Status: The '269 patent is Expired – Fee Related (anticipated expiration recorded Dec. 8, 2019), and I found no 2026 CAFC activity, consistent with the earlier-generated summary.

I'll research the prior-art references cited on the face of US 8,266,269 and its family, then build the § 103 analysis. Let me start with targeted searches.

The Unified Patents page gives useful prior-art leads. Let me retrieve the actual claims and the "References Cited" list.

Let me try to retrieve the actual claim text and the front-page references.

Obviousness Analysis — U.S. Patent No. 8,266,269 under 35 U.S.C. § 103

Analyst note / scope limitation. The authoritative full text supplied to me truncates inside the Detailed Description and does not contain the numbered claims of the '269 patent, and my searches did not surface the verbatim '269 claim set. I therefore do not reproduce claim numbers or claim language verbatim for '269, and I have not fabricated them. The element-level mapping below is built from (a) the claim language recited in the '269 specification's own "Summary of Invention" (the method of managing network access claim and the location-based content subject matter), and (b) the closely parallel sibling claim set of the same Nomadix continuation family as it appears in Nomadix Exhibit 2006, 2nd Preliminary Amendment, filed in IPR2016-00092 (the '806 sibling) — retrieved at
https://www.docketalarm.com/cases/PTAB/IPR2016-00092/Inter_Partes_Review_of_U.S._Pat._8364806/docs/02-10-2016-Patent_Owner/Exhibit-2006-2nd_Preliminary_Amendment.pdf.
Where I rely on that sibling language as a proxy, I say so. Any element-by-element application below must be re-verified against the actual '269 claim set before being relied upon.

1. Person of ordinary skill in the art (POSITA)

For a patent with an effective priority date in the 1998–2000 window, a POSITA would be a networking engineer/architect with a bachelor's degree in EE/CS (or equivalent) and 2–4 years' experience in IP-address management, internetworking gateways/firewalls, HTTP/TCP protocols, and ISP or hospitality HSIA deployments. Critically, the art at that time was highly active and well-populated: transparent proxies, NAT, HTTP redirection, DHCP, RADIUS, and VLAN tagging were all standard commercial/toolkit technologies (e.g., Vu's "transparent proxy" teachings, RFC 2058/2138 RADIUS (Jan./Apr. 1997), RFC 1777 LDAP (1995), IEEE 802.1Q, ISL). This matters under KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007): where the field is one of "known options" and the references address the same problem, a combination is likely obvious.

Effective filing date caveat (material). The record lists the priority date as 1998-12-08 (benefit claims from US 09/458,569 and US 09/458,602, both filed 1999-12-08). However, the applicant's own patent family and the Examiner's citation of references having post-1998 filing dates (see §3 below) indicate that at least some '269 claims were treated as entitled only to a later effective date. Because claim-by-claim priority determines the prior-art universe, this must be resolved claim-by-claim before any § 103 rejection is finalized.

2. Prior art references relied upon

Not used / flagged: EP 0 924 913 A1 appears in searches as a family member of the Nomadix priority chain (Method for supporting internet mobility) and is not independent art. The Blueprint RF invalidity contentions and the HP/SolutionInc. joint invalidity contentions referenced in the '269 file-history listing (Ex. A/B and Exs. C1–C7) contain additional third-party art I could not retrieve in full within this session.

3. Obviousness combinations

Combination 1 — Vu + Levergood (core "spoofed redirect" claims)

The '269 specification's Summary recites a method comprising: (i) receiving data packets containing a request for network content from an external server; (ii) determining authorization rights associated with the client based on a user profile selected from a user profile database; (iii) if not entitled, producing a redirection response that (a) causes the client to request content at a location different from the external server, and (b) is "configured to indicate to the computer that the redirection response originated from the external server"; and (iv) transmitting that response back to the client.

Motivation to combine. Both references address the identical problem — controlling access to networked content where the client is not pre-configured — and both operate at the same point in the network (an intermediary between client and content server). Levergood supplies precisely the missing function (redirecting an unauthorized user to a login/portal) while Vu supplies the mechanism that makes the redirect indistinguishable from the requested server (completing the connection handshake while "pretending to be" the target, i.e., placing the external server's address in the sender field). A POSITA seeking to make a hotel/venue login gateway robust against users who never see the portal would have had strong reason to combine Vu's proxy handshake with Levergood's redirect — indeed, as Dr. Olson explained in IPR2016-00092, the combination of "proxy handshake + proxy redirect message + causing the user's computer to request a portal page server different from the site the user requested" was standard practice in the late 1990s. This is a KSR-type predictable combination of two known techniques.

Combination 2 — Vu + Levergood + Ayers (or Vange) (connection-speed / content-direction claims)

The '269 abstract expressly claims "controlling user perceived connection speed" and "systems and methods for directing client computers to select connection speed." To the extent the independent claims require selecting/directing a content source or speed:

• Ayers discloses directing requests for content to a content server based on network performance — i.e., choosing which server/speed tier serves the user.
• Vange discloses redirecting requests to arbitrary front-ends.

Motivation. Once the Vu+Levergood gateway has intercepted and classified a user, routing that user to a different content/portal endpoint based on measured connection performance (Ayers) is a straightforward, predictable extension — the same gateway is already rewriting the destination. The art taught "front-end selection" as a design variable; applying it to the already-redirected session requires no new mechanism.

Combination 3 — Vu + Levergood + Wayport '061 (location-based alternate content)

The '269 Summary recites producing alternate content based in part on a physical location identifier received with the request (where the location may be a hotel room, suite, airport terminal, building wing, retail outlet), the identifier possibly originating from an intermediary network device.

• Wayport '061 discloses a communications service whose content/services are keyed to the geographic location of the access point — the exact "location identifier" concept, including the venue (hotel/airport) context.
• Levergood/Vu supply the gateway that receives the request and can substitute/redirect content.

Motivation. Both Wayport and Nomadix target the same commercial deployment (public/hotel/airport HSIA), and Wayport expressly teaches that the location of the access point should drive what the user is served. Feeding a location identifier (from the port/access concentrator/VLAN) into the Vu+Levergood redirect engine to select venue-specific alternate content is the natural combination of two references directed to the same hospitality/venue market. KSR: the improvement is "the mere[] ... arrangement of old elements with each performing the same function it had been known to perform."

Combination 4 — Vu + '786 (+ RADIUS RFC 2058/2138 / LDAP RFC 1777) (attribute-based AAA against an external profile database)

To the extent claims require identifying a source by an attribute (MAC address, User ID, VLAN ID, circuit ID) and determining access rights from a source/user profile database external to the gateway (RADIUS or LDAP):

• Vu discloses gateway-side authorization of the client for the requested service.
• '786 discloses monitoring and controlling network access by recognized attributes.
• RFC 2058/2138 (RADIUS) and RFC 1777 (LDAP) disclose exactly the external, attribute-keyed profile databases the specification names.
• '604 (VLAN tagging) supplies the VLAN-ID attribute; '654 supplies proxy-ARP-based identification.

Motivation. Centralizing AAA in a RADIUS/LDAP server was the standard ISP practice of the day (RFC 2058/2138 were published in 1997), and it directly solves the problem the specification itself identifies — multiple gateways needing one consolidated, remotely administered authentication database. Substituting a network-layer attribute (VLAN ID/tag, per '604) for Vu's session-based identity is an obvious design choice because VLAN tagging was the standard mechanism for conveying port/venue identity in DSL/access-concentrator deployments.

Combination 5 — '654 + '974 + '6039 (transparent client configuration without client-side software)

To the extent claims require the client to remain configured for its home network and to be transparently connected via the gateway (DHCP/Proxy ARP/address translation): '654 (proxy-ARP interception), '974 (internetwork address-mapping gateway), and '6039 (automatic static-to-dynamic IP/DNS management at remote-access networks) together disclose each claimed function. All three are cited on the '269 face-of-page prior-art listing, and all three address the same problem (a mobile host with a foreign/home-network configuration reaching a visiting network).

4. Motivation-to-combine summary (KSR / In re KSR factors)

1. Same field, same problem. All principal references address controlling/redirecting access in a shared-access (hotel, airport, ISP, MDU) network.
2. Predictable combination of known techniques. Vu's "pretend to be the target" proxy handshake + Levergood's browser redirect + Wayport's location-keyed service is the mechanical assembly of three known building blocks, each performing its known function.
3. Express teaching/suggestion in the references. Vu expressly authenticates at the time of connection; Levergood expressly redirects unauthorized users; Wayport expressly keys content/services to location; RFC 2058/2138 expressly externalize AAA.
4. Design incentives. The specification itself articulates the motivations (one consolidated AAA database; efficiency and speed of a local portal; venue-specific content) — factors that likewise motivated the POSITA before the effective date.
5. No criticality / no unexpected result. Nothing in the claims appears to require an unconventional ordering or an unpredictable parameter; the claimed selections (RADIUS vs. LDAP, internal vs. external database) are merely recited alternatives.

5. Secondary considerations

No evidence of secondary considerations (long-felt but unmet need, failure of others, unexpected results, licensing due to the merits) is present in the material I retrieved. The commercial success of Nomadix's USG product line is documented in the litigation record, but a nexus between that success and the specific '269 claim limitations would have to be shown — and the 2014–2016 Blueprint RF litigation ended in stipulated dismissal (June 2016) and the parallel IPR2016-00081 terminated by settlement, so there is no adjudicated validity finding for the '269 patent either way.

6. Confidence, contradictions, and gaps

• Contradiction to flag (carried forward): the prior "Patent summary" section states the current assignee is ambiguous. My searches add nothing to resolve it; the record still shows Gate Worldwide Holdings LLC quitclaiming back to Nomadix, Inc. on 2019-11-22. Treat "current assignee" cautiously.
• Highest-confidence combination: Vu + Levergood for the proxy-handshake/spoofed-redirect claims. Both are securely pre-1998 art, and the Vu characterization is independently corroborated by sworn testimony in the family's own IPR (Ex. 1011).
• Medium confidence: + Wayport '061 for location-based content (Wayport is pre-1998 and venue-focused, but I have not verified its location-identifier claim mapping against the '269 claim language).
• Low confidence / verify before relying: the '786, '604, '654, '974, '6039, Vange, Ayers and Ikudome citations. I confirmed their presence on the '269 references/similar-documents listings, but I did not verify their individual publication/filing dates against the '269 priority date. In particular, Vange, Ayers and the Ikudome publications post-date 1998 and may not be prior art at all if the claims are entitled to the 1998-12-08 date; their appearance in the prosecution citations may also reflect applicant-family/IDS submissions rather than examiner § 102/103 reliance. The Ikudome publications in particular appear to be Nomadix's own family and should be excluded as art absent a separate prior-art date.
• Not retrieved: the specific grounds of IPR2016-00081 (the '269 IPR, terminated by settlement) and the Blueprint RF and HP/SolutionInc. invalidity contentions (Exs. A/B and C1–C7 in the '269 file-history listing). Those documents almost certainly contain additional, well-developed § 103 combinations specifically aimed at the '269 claims and should be obtained from PTAB/PTACTS and PACER before finalizing any opinion.
• Bottom line: on the record I could verify, the '269 claims directed to (i) intercepting a request addressed to an external server, (ii) determining entitlement from a profile, and (iii) returning a redirect that appears to originate from the external server are, in my assessment, likely obvious over Vu in view of Levergood (optionally with Wayport '061 for the location-based content claims and with RADIUS/LDAP standards for the external-profile claims). A definitive conclusion requires the verbatim '269 claim set and the IPR2016-00081 petition, which I could not retrieve in this session.