US 8788690

I'll run targeted searches for this exact patent number and its litigation/appeal history.

Let me search for the litigation/appeal history and the abstract/claims text.

Let me do a final round of targeted searches on any 2026 appellate activity and the claim text.

Bottom line

I confirmed an exact match for US 8,788,690 B2 — no similar-number substitution. No Federal Circuit 2026 docket involving US 8,788,690 was found. The only 2026 CAFC activity my searches surfaced involves different patents (WAG Acquisition, LLC v. Google LLC et al., Nos. 2024‑1627/1630, Rule 36 affirmances entered March 9, 2026), which concern streaming-media patents, not the '690 patent. I flag that explicitly so it is not mis-attributed.

Bibliographic data (as reported in the public record)

Sources: https://patents.google.com/patent/[US8788690B2](/patent/US8788690B2)/en ; https://uspto.report/patent/grant/[8,788,690](/patent/8788690)

Assignee note: the record shows a 2018‑01‑23 assignment to GATE WORLDWIDE HOLDINGS LLC, followed by a 2019‑11‑22 QUITCLAIM back to NOMADIX, INC., plus NTT DOCOMO security interests (2015, 2017) and a Knobbe Martens security interest (2019) that was released in May 2019. The "Gate Worldwide Holdings LLC" entry in the Google Patents header therefore appears stale relative to the later quitclaim; I would treat Nomadix, Inc. as the likely current owner, but I cannot confirm this with full confidence.

Priority/continuity: the '690 is a continuation in a large family all carrying the 1998‑12‑08 priority date, including US 8,244,886; 8,156,246; 8,370,477; 8,364,806; 8,606,917; 8,725,889; 8,725,888; 9,548,935; 10,110,436; and 10,341,243. The record also lists external priority claims from US 09/458,569 (→ US 6,636,894), US 09/458,602 (→ US 8,713,641), and US 09/693,060 (→ US 7,194,554).

⚠️ Discrepancy in the source record: Google Patents shows both a "Priority date: 1998‑12‑08" and separate "Priority claimed from" entries dated 1999‑12‑08 and 2000‑10‑20. These dates are internally inconsistent, and I am not able to resolve which is authoritative for the '690 specifically.

Abstract

I do not have the verbatim abstract text. The fetched patent document began at the classification/bibliographic material and the "Definitions" extraction, and did not include the Abstract or the numbered claims section. Rather than paraphrase from memory and risk fabricating text, I am stating this plainly.

What the record does establish thematically: the patent is directed to transparent network access via a gateway/access-controller device — identifying a source, determining its access/authorization rights from a profile, and redirecting unauthorized users to a login or portal page without requiring reconfiguration of the user's computer.

Independent claims — plain-language overview

The fetched record includes a claim-language section (labeled "Definitions") that appears to reproduce independent-claim text. I identified at least three distinct independent claims. Claim numbering is not confirmed, since the numbered claims listing was not in the fetched material.

1. Method for granting access — "source-IP profile lookup, with destination-based bypass"
An access controller receives a TCP connection request (with source IP and destination IP) from a source computer. It decides whether login is required by (a) comparing the source IP against profiles of authorized source devices — if matched, access is granted with no further authorization; (b) if not matched, checking whether the destination IP is one of a set of destination IP addresses associated with the access controller — if so, access is granted with no further authorization (a whitelist/closed-garden bypass); (c) if neither, the controller determines authorization is required, serves a login page, authenticates the credentials returned, and grants access if authentication succeeds.

2. System for providing network access — same logic, apparatus form
An access controller receives the TCP connection request (source IP + destination IP) and redirects the source device to a login page when authentication is required. The authentication test is the same two-step one: source-IP profile match → grant without further authorization; else destination-IP whitelist check → grant without further authorization; else authorize only after the user's login-page credentials are authenticated.

3. Method of managing network access — "spoofed-redirect" / captive portal claim
The system receives a packet containing a request for network content from an external server; determines the client's authorization rights from a user profile selected from a user profile database; and, if the client is not entitled to the requested content, generates a redirection response that (i) causes the client to request content from a different network location than the one originally requested and (ii) is configured to appear as though it originated from the external server the user asked for. That redirection response is then transmitted back to the client. This third claim is the classic Nomadix "transparent captive portal" concept (referred to in the spec and litigation as Home Page Redirect / Stack Address Translation).

Litigation and 2026 appellate activity

• District court: The '690 patent was one of seven Nomadix patents asserted in Nomadix, Inc. v. Hospitality Core Services LLC d/b/a Blueprint RF, No. 2:14‑cv‑08256 DDP (VBKx) (C.D. Cal., filed 2014‑10‑24). The court's Jan. 27, 2016 summary-judgment order addressed validity challenges to the '246, '266, '269, '806, and '690 patents; Blueprint also brought inequitable conduct / prosecution laches counterclaims referencing the '690, alleging unreasonably voluminous prior-art disclosures ("burying") and failure to disclose Brendel and RFC 1919. The case was dismissed by joint stipulation in June 2016. Sources: https://cases.justia.com/federal/district-courts/california/cacdce/2:2014cv08256/[602501/142](https://assignmentcenter.uspto.gov/search/patent/reelFrameDetail?reelFrame=602501-0142)/0.pdf ; https://litigation.rpxcorp.com/litigation/cacdce-[602501](/patent/602501)-nomadix-inc-v-hospitality-core-services-llc
• PTAB: Related IPRs (e.g., IPR2016‑00081) were filed against sibling patents in the same family; claim charts against the '690 (Slemmer, ATCOM/IPORT, Micros-Fidelio, WO 98/40990) appear in the record.
• CAFC 2026: No docket or opinion concerning US 8,788,690 was located. For completeness — and to avoid conflation — the 2026 Federal Circuit items returned by search were:
  • WAG Acquisition, LLC v. Google LLC, Disney, Hulu, Netflix, No. 2024‑1630, and WAG Acquisition, LLC v. Disney, Hulu, Netflix, Google, Amazon, Nos. 2024‑1627/1628/1631–1634, both AFFIRMED under Fed. Cir. R. 36 on March 9, 2026 (Panels: Lourie, Wallach, Chen) — these arise from IPRs on WAG's streaming-media patents (e.g., 8,825,887), not Nomadix or the '690. https://cafc.uscourts.gov/opinions-orders/24-1630.RULE_36_JUDGMENT.3-9-2026_2658157.pdf
  • A January 29, 2026 CAFC decision affirming a California summary judgment of noninfringement for Hulu in a streaming patent dispute — again a WAG/Madison-lineage matter.

Separately, the Google Patents record links the '690 family to a California Central District Court case, 2:14‑cv‑08256, which I confirmed is the Blueprint RF action above.

Explicit uncertainties

1. Abstract text — not available in the material I could retrieve; not reproduced.
2. Exact claim count and claim numbering — the numbered claims were not in the fetched document. The three independent claims above are reconstructed from the record's claim-language extraction and should be verified against the official USPTO claim set before being relied on.
3. Priority date — the source record is internally inconsistent (1998‑12‑08 vs. 1999‑12‑08 vs. 2000‑10‑20); unresolved.
4. Current assignee — Google Patents says Gate Worldwide Holdings LLC; the assignment chain shows a later quitclaim to Nomadix, Inc. I could not definitively confirm the present owner.
5. No CAFC 2026 proceeding for this patent was found — this is a negative search result, not proof of absence.

I'll search for litigation involving US patent 8788690.

Let me dig deeper into the specific litigation references.

Important: search results return a mix of two different patents both nicknamed "the '878 patent" — US 8,788,690 (Nomadix) and US 10,715,878 (AlmondNet/Intent IQ). Let me carefully separate these and confirm only the 8,788,690 matters.

Litigation Involving U.S. Patent No. 8,788,690

Preliminary — Correctly identifying the patent (critical)

Before listing cases, I must flag a significant disambiguation problem, because the numeral string "8788690" pulls back search results for two entirely different patents that both get nicknamed "the '878 patent":

Per your strict instruction ("do not return results for similar numbers"), I am excluding all AlmondNet/Intent IQ matters — the Roku, Samsung, Meta, Amazon, Microsoft, and Roku/Intent IQ cases and the IPRs IPR2022‑01315 (Roku), IPR2022‑01505 (Samsung), and IPR2023‑01281 (Meta). Those IPRs are expressly captioned against Patent 10,715,878 (see the PTAB mandatory notice: "Case No.: IPR2022‑01505 Patent 10,715,878"). They are not about 8,788,690 and must not be attributed to it.

The '690 patent itself was granted July 22, 2014 (App. No. 14/094,712, filed 2013‑12‑02; inventors Joel E. Short, Florence C. I. Pagan, Joshua J. Goldstein), so any asserted case necessarily post-dates mid‑2014.

District court litigation

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

This is the only district court case I could positively confirm that named 8,788,690 as an asserted patent. It is also the case Google Patents lists as the '690 family's U.S. litigation (C.D. Cal. 2:14-cv-08256), cross-referenced to Unified Patents.

Related proceedings (not litigation of the '690 patent itself)

These arose from the same dispute but target sibling Nomadix patents, not 8,788,690 — listed only to avoid confusion:

• IPR2016‑00081, Hospitality Core Services, LLC v. Nomadix, Inc. — U.S. Patent 8,266,269.
• IPR2016‑00092, Hospitality Core Services, LLC v. Nomadix, Inc. — U.S. Patent 8,364,806.
• Related district cases cited on the '690 docket (all pre‑date the '690 grant and involve other patents): Nomadix v. Second Rule LLC, 2:07‑cv‑01946; Nomadix v. Hewlett‑Packard Co., 09‑cv‑8441; Nomadix v. Solutioninc Technologies Ltd., 2:10‑cv‑00381; and 2:14‑cv‑00322.

Caveats and open items (stated honestly)

• Completeness is not guaranteed. I hit my tool‑call limit before I could pull the Unified Patents litigation page, the Darts‑IP family record, or PACER/CAFC dockets directly. The "family has litigation" flag on Google Patents points to the same 2:14‑cv‑08256 case, but a Darts‑IP "first worldwide family litigation" entry could indicate additional foreign or later U.S. actions I could not verify.
• Unverified post‑2014 Nomadix cases. Nomadix filed later suits (e.g., Nomadix, Inc. v. SIA Mikrotikls, C.D. Cal. 2:19‑cv‑10202). I could not confirm from the retrieved material whether 8,788,690 was among the patents asserted there, so I am not listing it as verified litigation for this patent. It should be checked against the complaint in that docket.
• No appellate (CAFC) decision specifically on 8,788,690 appeared in my search; the Blueprint matter resolved at summary judgment and by stipulation before any appeal surfaced.
• Ownership vs. litigation. The recorded assignment chain (NTT DOCOMO security interests 2015/2017; assignment to Gate Worldwide Holdings LLC 2018; quitclaim back to Nomadix 2019) is a title/security record, not litigation, and is noted only for context.

Bottom line: Based on the available search results, the only litigation I can confirm involving U.S. 8,788,690 is Nomadix, Inc. v. Hospitality Core Services LLC d/b/a Blueprint RF, No. 2:14‑cv‑08256 (C.D. Cal.), filed Oct. 24, 2014, resolved by summary judgment (Jan. 27, 2016) and joint dismissal (June 2016). All "878 IPR" and AlmondNet/Roku/Samsung/Meta matters refer to a different patent (10,715,878) and are excluded.

Proceedings overview

Total: 0 AIA trial proceedings on file against US 8,788,690 — the structured "PTAB proceedings on file" block (USPTO ODP, most recent ingest) reports no IPR, PGR, or CBM ever instituted, denied, or settled on this patent; breakdown is therefore 0 active / 0 claims invalidated / 0 claims sustained / 0 settled / 0 institution-denied, and my independent web checks surfaced no additional proceeding that ODP may have missed (I did find a large body of IPR activity on other Nomadix patents and a set of 2022–2024 IPRs against a different patent also nicknamed the "′878 patent" — see the caution below). Bottom-line defensive posture: no PTAB estoppel applies and no claim has been canceled — but that is not good news for the patent owner, because the patent itself appears to have expired on 2019-12-08 ("Expired – Fee Related" per Google Patents) and was never worth an IPR to the defendants who litigated it in 2015–2018. The absence of PTAB activity here is a weakness signal, not a strength signal: the ′690 patent was co-asserted with six sibling Nomadix patents that did draw IPRs, yet no petitioner bothered to challenge the ′690 itself.

⚠️ Do-not-conflate warning for anyone briefing this patent. Search results (and some expert declarations) refer to "the ′878 Patent" IPRs — IPR2022-01315 (Roku), IPR2022-01505 (Samsung), IPR2023-01281 (Meta) and IPR2022-00773 (Meta). Those are against U.S. Patent No. 10,715,878 B2 (AlmondNet), not Nomadix's 8,788,690. The petition text itself confirms it: "Petition for Inter Partes Review of U.S. Patent No. 10,715,878 B2," and it distinguishes "U.S. Patent No. 8,677,398 B2, an earlier patent in the same family" — an AlmondNet family. See https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1555815](/patent/1555815)/download-documents and https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1555167](/patent/1555167)/download-documents. Do not cite those numbers as 8788690 history.

Per-proceeding detail

None. There are no AIA trial proceedings to itemize for US 8,788,690.

Because the instructions say "do not invent proceeding numbers," I am not going to dress up the adjacent activity as ′690 proceedings. What follows is the verifiable adjacent record, clearly labeled, so a defendant understands the landscape without mis-citing anything.

Adjacent PTAB activity — SIBLING Nomadix patents (NOT 8,788,690)

These are the Nomadix IPRs I could verify. They are on different patents and must not be presented as ′690 PTAB history:

• IPR2016-00081 — Hospitality Core Services, LLC d/b/a Blueprint RF v. Nomadix, Inc. (U.S. Patent No. 8,266,269). Filed on or about 2015-10/11. Blueprint RF's mandatory notices confirm it also petitioned on related Nomadix patents co-asserted in Nomadix, Inc. v. Hospitality Core Services LLC, No. 14-cv-08256 (C.D. Cal.). Petitioner counsel: Michael J. Mehrman. Source: https://www.docketalarm.com/cases/PTAB/IPR2016-00081/Inter_Partes_Review_of_U.S._Pat._8266269/
• IPR2016-00092 — Hospitality Core Services, LLC v. Nomadix, Inc. (U.S. Patent No. 8,364,806). Source: https://www.docketalarm.com/cases/PTAB/IPR2016-00092/Inter_Partes_Review_of_U.S._Pat._8364806/
• Guest-Tek Interactive Entertainment Ltd. v. Nomadix, Inc. — a series of petitions filed beginning December 2017 (the docket shows IPR2018-00376, and Nomadix's Ninth Circuit briefing describes "a series of IPR petitions" filed from December 2017 through mid-2019, culminating in IPR2019-00211 and IPR2019-00253, with Final Written Decisions due no later than 2020-05-28 and 2020-05-30 respectively). On 2018-06-29, the Board denied institution of two Guest-Tek petitions for failure to show a reasonable likelihood of unpatentability. Nomadix press release: https://www.globenewswire.com/news-release/2018/07/02/[1532569](/patent/1532569)/0/en/Patent-Trial-and-Appeal-Board-Denies-Guest-Tek-s-Petitions-for-Review-of-Nomadix-Patents.html. The patents challenged in the 2019 proceedings are not identified in the briefing I could verify, and none is identified as the ′690.
• Guest-Tek ultimately was enjoined by the district court (early 2020) to withdraw the pending IPRs as a breach of the license agreement's forum-selection clause; the Ninth Circuit affirmed on 2021-09-03 in Nos. 20-55439 & 20-56008 (Nomadix, Inc. v. Guest-Tek Interactive Entm't Ltd., C.D. Cal. No. 2:16-cv-08033). Memorandum: https://cdn.ca9.uscourts.gov/datastore/memoranda/2021/09/03/20-55439.pdf. This is a contract appeal, not a PTAB appeal, and it did not adjudicate the validity of any claim.

Critically: the ′690 patent was one of seven Nomadix patents asserted in Nomadix v. Hospitality Core Services (Complaint dated 2014-10-24; the seven were U.S. 6,636,894; 6,868,399; 8,156,246; 8,266,266; 8,266,269; 8,364,806; and 8,788,690), and it was squarely in the district-court invalidity fight — Blueprint RF served claim charts against it under § 102/§ 103 and § 112/double-patenting, and the court's 2016-01-27 summary-judgment order addressed the validity of the ′246, ′266, ′269, ′806 and ′690 patents. Yet Blueprint RF did not take the ′690 to the PTAB, and neither did Guest-Tek. See https://cases.justia.com/federal/district-courts/california/cacdce/2:2014cv08256/[602501/142](https://assignmentcenter.uspto.gov/search/patent/reelFrameDetail?reelFrame=602501-0142)/0.pdf.

Strategic summary

Claim status — everything is UNTESTED at the PTAB. No claim of 8,788,690 has been canceled, no claim has been sustained in a Final Written Decision, and no claim has been construed by the Board. There is no FWD to quote and no claim list to give you. The only adjudication touching the ′690's validity is district-court motion practice in Nomadix v. Hospitality Core Services: the court declined to declare the ′399 and ′690 patents invalid at the pleading stage (Order at Dkt. 47; "The Court therefore declines, at this stage in the litigation, to declare the ′399 and ′690 patents invalid"), and the 2016-01-27 SJ order took up the ′690 along with four siblings. I could not verify from the sources available to me how the court resolved the § 102/§ 103 and § 112/double-patenting challenges specific to the ′690, so I will not state an outcome. Note that this patent is a 1998-priority continuation whose anticipated expiration is 2019-12-08 and whose Google Patents legal status is "Expired – Fee Related" — for a modern assertion, that caps exposure to pre-expiration conduct within the § 286 six-year lookback and eliminates prospective injunctive relief as a practical matter.

Estoppel landscape — clean slate for you. Because no AIA trial was ever instituted on the ′690, no § 315(e)(2) estoppel attaches to this patent. A defendant asserted today can run any prior-art ground it wants — Madhavan/Baum/Harrington/Damick, Slemmer (U.S. 6,226,677), the ATCOM/iPORT materials, Micros-Fidelio, Cohen, Brendel, RFC 1919, the Short PCT (WO 98/40990) — free of PTAB estoppel, and can do so in an IPR, in district court, or via ex parte reexamination. Two caveats: (1) if Nomadix (or a privy/petitioner such as Blueprint RF, if you are in privity with it) obtained an FWD on a sibling patent in the same family, privity-based arguments could surface, but no estoppel flows from the ′690; and (2) the same prior art that Blueprint RF already charted in 2015 is now public record, so the tools are unusually well-developed for a fresh challenger.

Pattern signals. Nomadix is a frequent PTAB target across its portfolio (Blueprint RF 2015–2016; Guest-Tek from December 2017; Blueprint RF used the Nomadix litigation as a test bed for its petitions), and its patents survive more often than not — the Board denied Guest-Tek's two June 2018 petitions outright. Nomadix also litigates hard on the contract side, going so far as to enjoin IPRs via a license forum-selection clause and win Ninth Circuit affirmance. There is no sign of a defensive aggregator (e.g., Unified Patents) in the ′690's chain — the Unified Patents references I found concern unrelated patents. Assignee history is churned (Nomadix → security interests to NTT DOCOMO → assignment to Gate Worldwide Holdings LLC in 2018 → quitclaim back to Nomadix on 2019-11-22), so confirm standing/ownership before treating any demand letter as authoritative about who holds the right to sue.

Recommended next steps

1. Do not tell a court or a client that "the ′878 patent survived two IPRs" or that "claims were canceled" — neither is true for US 8,788,690. If opposing counsel asserts PTAB history on this patent, demand the proceeding number; there isn't one for 8788690.
2. Verify the PTAB docket yourself before relying on this memo. The authoritative sources are PTAB E2E (https://ptacts.uspto.gov/ptabweb/) and the USPTO Patent Center for Application No. 14/094,712 (https://patentcenter.uspto.gov/). Search the patent number directly. The structured ODP block controls, but confirm it.
3. Lead with the expiration, not the PTAB. Anticipated expiration 2019-12-08 + "Expired – Fee Related" status means any current assertion can only reach past damages (and only within § 286's six-year window). Pair this with § 102/§ 103 art that Blueprint RF already charted publicly — Slemmer (U.S. 6,226,677), ATCOM/iPORT, Micros-Fidelio, WO 98/40990 — for an invalidity position with a proven paper trail.
4. Check the live continuations before you conclude the family is dead. The ′690 family lists later continuations, including US 9,548,935, US 9,160,672, US 10,110,436 and US 10,343,243 (see https://patents.google.com/patent/US8788690/en and https://patents.google.com/patent/US9548935/en). If a troll's demand cites one of these instead of the ′690, this memo does not cover it and fresh PTAB/litigation analysis is required.
5. If an AIA proceeding on the ′690 is filed after this memo, the milestones to diary are: PO preliminary response (3 months from notice of filing date), institution decision (statutory deadline 6 months from petition filing), and Final Written Decision (statutory 1-year trial deadline from institution). Nothing is currently on the clock.

I'll analyze the provided patent text first, then search for the recorded assignment details (reel/frame, correspondents) and any litigation/asserter data.

Good leads. Let me search for the specific assignment reel/frame records and the Gate Worldwide/Nomadix ownership structure.

Let me dig into the specific assignment records and the Gate Worldwide Holdings / GWHSPV structure.

US 8788690 — Ownership & Assignment Reconstruction

Data-access note up front (important): The authoritative patent text supplied and my searches surfaced the Google Patents legal-events record in full, but my available tools did not return the USPTO Assignment Center reel/frame numbers or the recorded correspondents of record for this patent. I therefore present the ownership chain as captured in the legal-events record (which uses the same underlying assignment data) and explicitly flag every field I could not verify. I have not fabricated reel/frame numbers, execution dates, or correspondents. Where the record is silent, I say so.

Inventors

Pattern notes:

• Nomadix was co-founded by Dr. Leonard Kleinrock and Dr. Joel Short (per Nomadix's own complaint in Nomadix, Inc. v. SIA Mikrotikls, C.D. Cal. 2:19-cv-10202, ¶¶15–17). Kleinrock is not a named inventor on this particular patent; Short is.
• I found no evidence that all inventors departed Nomadix within 12 months of filing, and no fire-sale-precursor pattern. Inventor-employer relationship is inferred from the original assignment to Nomadix, Inc., not from a verified employment record.

Original assignee

• Entity on the issued patent: Nomadix, Inc.
• Primary line of business: Public-access network gateway hardware/software (hotel, airport, café, MDU Internet access gateways); also a media/digital-signage arm (Nomadix Media).
• Did they ship a product embodying the claims? Yes. Nomadix's complaint describes commercially deployed "gateways" used by hotels and cafés for transparent network access, redirection, bandwidth control, and billing — the core subject matter of this patent family. It is described as an "industry pioneer and leader in the public access market" (2:19-cv-10202 Am. Compl. ¶¶15–19).
• Current status (determinable): Operating, and held within a holding structure: the Nomadix, Inc. v. SIA Mikrotikls Certificate of Interested Parties (filed 2019-12-02, Dkt. 4) identifies GWHSPV, LLC as parent of Nomadix, Inc. and Gate Worldwide Holdings LLC as parent of GWHSPV, LLC. No bankruptcy or dissolution evidence found.

Assignment timeline

Reel/frame and correspondent fields: NOT VERIFIED. The USPTO Assignment Center entries for this patent were not retrievable with the tools available to me. The following is reconstructed from the Google Patents legal-events record (same underlying assignment data), which for the key transfers shows only "SEE DOCUMENT FOR DETAILS." I flag each gap.

• 2015-09-30 (recorded) — Reel NNNNNN/NNNN not retrieved

  • Conveyance: Security Interest ("Security Interest — see document for details")
  • Assignor: Nomadix, Inc.
  • Assignee: NTT DOCOMO, INC.
  • Correspondent: not retrieved — see flag below.
  • Context: Securitization — NTT DOCOMO took a security interest in Nomadix's patent estate (financing), not an ownership transfer.

• 2017-08-29 (recorded) — Reel NNNNNN/NNNN 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 NTT DOCOMO security interest.

• 2018-01-23 (recorded) — Reel NNNNNN/NNNN not retrieved

  • Conveyance: Assignment of Assignors Interest ("see document for details")
  • Assignor: Nomadix, Inc.
  • Assignee: Gate Worldwide Holdings LLC
  • Correspondent: not retrieved
  • Context: Internal reorganization / holding-company restructuring — '690 moved into the Gate Worldwide Holdings family (which the litigation record confirms is the parent of Nomadix).

• 2018-01-23 (recorded) — Reel NNNNNN/NNNN not retrieved

  • Conveyance: Assignment of Patent Security Agreement
  • Assignor: NTT DOCOMO, INC.
  • Assignee: Gate Worldwide Holdings LLC
  • Correspondent: not retrieved
  • Context: Securitization — the NTT DOCOMO security interest was assigned over to the new holding entity alongside the ownership transfer.

• 2019-03-20 (recorded) — Reel NNNNNN/NNNN not retrieved

  • Conveyance: Security Interest
  • Assignor: Nomadix, Inc.
  • Assignee: Knobbe, Martens, Olson & Bear, LLP
  • Correspondent: not retrieved
  • Context: Securitization — a law firm (Knobbe Martens) recorded a security interest in Nomadix's patents, consistent with a fee/retainer collateral arrangement. (Note: this is a secured-party entry, not a correspondent-of-record finding.)

• 2019-05-28 (recorded) — Reel NNNNNN/NNNN not retrieved

  • Conveyance: Release by Secured Party
  • Assignor: Knobbe, Martens, Olson & Bear, LLP
  • Assignee: Nomadix, Inc.
  • Correspondent: not retrieved
  • Context: Release — the Knobbe Martens security interest was discharged.

• 2019-11-22 (recorded) — Reel NNNNNN/NNNN not retrieved

  • Conveyance: Quitclaim
  • Assignor: Gate Worldwide Holdings LLC
  • Assignee: Nomadix, Inc.
  • Correspondent: not retrieved
  • Context: Internal reorganization — ownership quitclaimed back to the operating entity, roughly 10 days before the 2019-12-02 MikroTik complaint. Google Patents still lists "Gate Worldwide Holdings LLC" as current assignee, which conflicts with this quitclaim; treat the current owner as uncertain but most consistent with Nomadix, Inc. (the named plaintiff in every subsequent suit). Verify on Assignment Center.

• 2019-12-08 — Anticipated expiration (Google Patents legal-status entry; not an assignment). The patent term would run from the earliest priority/filing chain; this entry reflects an expected lapse, and Google's status flags the patent "Expired – Fee Related."

Correspondent flag: I could not retrieve any correspondent of record, so I cannot make a repeat-correspondent finding. The only law-firm entity appearing anywhere in the record is Knobbe, Martens, Olson & Bear, LLP, and it appears as a secured party (2019-03-20), not as a recording correspondent. I am not converting a security-interest role into a correspondent finding.

Timeline diagram

timeline
    title Ownership of US 8788690
    1998 : Priority date
    2013 : Application filed by Nomadix
    2014 : Patent issued
         : Family litigation begins
    2015 : NTT DOCOMO security interest
    2017 : Security agreement modified
    2018 : Assigned to Gate Worldwide Holdings
         : NTT DOCOMO security interest assigned
    2019 : Knobbe Martens security interest
         : Release by secured party
         : Quitclaim back to Nomadix
         : Nomadix sues MikroTik

NPE / troll-pattern signals

1. Shell-entity transfer — Unclear. The 2018-01-23 transfer moved '690 from Nomadix, Inc. to Gate Worldwide Holdings LLC, a "Holdings" name that fits the suffix tell. However, the litigation record (2:19-cv-10202, Dkt. 4) shows Gate Worldwide Holdings as the corporate parent of the operating company (via GWHSPV, LLC → Nomadix, Inc.), and the 2019-11-22 quitclaim returned the patent to Nomadix, Inc. There is no evidence of a licensing-only shell with a registered-agent address. Name alone is not a finding.

2. Known asserter in the chain — Not present. No assignee in the chain matches the public NPE lists (Acacia, Marathon, IV, IPNav, Wi-LAN, Conversant/Mosaid, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, etc.). NTT DOCOMO and Knobbe Martens appear only as secured parties, not as asserting owners. Nomadix is a frequent patent plaintiff, but it is an operating vendor, not a listed NPE.

3. Repeat correspondent across the chain — Unable to assess / insufficient data. No correspondent of record was retrievable for any of the seven recorded events, so recurrence cannot be tested. This is a gap, not a clean bill of health — it should be re-run against the Assignment Center.

4. Cascading transfers — Unclear / weak. There are multiple recorded events across 2018–2019 (two transfers on 2018-01-23; security interest and release in 2019; quitclaim 2019-11-22), all within a ~22-month window. But they stay inside one corporate family (Nomadix ↔ Gate Worldwide Holdings) and reflect financing + reorganization, not chained unrelated LLCs with shared correspondent addresses.

5. Pre-litigation transfer — Unclear. The 2019-11-22 quitclaim precedes the 2019-12-02 MikroTik complaint by ~10 days, but that case asserted the '554, '894, '246, '995, and '727 patents — not clearly the '690. The earlier family suit (2:14-cv-08256, Nomadix v. Hospitality Core Services d/b/a Blueprint RF) predates the 2018 transfer, so the chronology does not show a clean "transfer-then-sue-on-this-patent" setup.

6. Bankruptcy fire-sale — Not present. No Chapter 7/11 proceeding found for Nomadix, Inc. or Gate Worldwide Holdings LLC.

7. Privateering — Not present. No evidence Nomadix transferred rights to an NPE to assert on its behalf; Nomadix litigates directly in its own name.

8. Defensive aggregator — Not present. The chain does not terminate at RPX, AST, LOT, Unified Patents, or OIN; it terminates back at the operating entity.

Verdict

Operating-company assertion.

The chain is a financing-and-reorganization sequence inside a single corporate family, not an NPE play: Nomadix, Inc. (original assignee and product vendor) → NTT DOCOMO security interest (2015-09-30, modified 2017-08-29) → Gate Worldwide Holdings LLC (2018-01-23 ownership + security-interest assignment) → Knobbe Martens security interest (2019-03-20) with release (2019-05-28) → quitclaim back to Nomadix, Inc. (2019-11-22). The asserted owner throughout has been the operating company Nomadix, Inc., which ships gateway products embodying the claims and sues direct competitors (BluePrint RF / Hospitality Core Services, iBAHN, HP, Guest-Tek, MikroTik) in its own name. No shell LLC, no listed NPE, and no defensive aggregator appears. Two caveats: (a) this verdict rests on the Google Patents legal-events record because I could not retrieve reel/frame numbers or correspondents from the Assignment Center; and (b) Google still lists "Gate Worldwide Holdings LLC" as current assignee despite the 2019 quitclaim, so current ownership should be confirmed on the Assignment Center before relying on the verdict.

Verify at: https://assignment.uspto.gov/patent/index.html (search patent number 8788690) and https://assignmentcenter.uspto.gov/ — specifically confirm the reel/frame and correspondent of record for the 2018-01-23 Nomadix→Gate Worldwide Holdings assignment and the 2019-11-22 quitclaim.

I'll research the prior art cited against US 8,788,690. Let me first note the critical disambiguation issue that already surfaced in the litigation section — the numeral string "8788690" pulls back two different patents, so I must keep results separated.

Let me pull the specific "References Cited" list and non-patent literature for US 8,788,690, plus the invalidity-contention art.

Let me get the actual front-page "References Cited" list for US 8,788,690 and confirm the Slemmer/ATCOM art details.

I've reached my research limit, so below I've synthesized what I could confirm. Per the operating rules, I'm flagging uncertainty where it exists rather than filling gaps.

Prior Art for U.S. Patent No. 8,788,690 ("Systems and Methods for Providing Content and Services on a Network System")

0. Disambiguation (building on the litigation section — not repeating it)

The numeral string "8788690" still pulls AlmondNet/Intent IQ material for U.S. 10,715,878. Everything below is confined to U.S. 8,788,690 B2 (Nomadix; App. No. 14/094,712, filed 2013‑12‑02; granted 2014‑07‑22). I have excluded all AlmondNet art.

One contradiction to flag explicitly: Google Patents states the '690 priority date as 1998‑12‑08, while the Unified Patents record for US‑8788690‑B2 lists 1998‑12‑07. Both trace to Provisional Application No. 60/111,497 (Redirection Application family, filed Dec. 1998). I cannot resolve which date the family treats as authoritative from the retrieved material.

1. What the '690 actually claims (needed to assess §102)

The '690 is a continuation whose specification repeats the "Definitions"/description reproduced in your authoritative text. Its claims, per that text, are directed to a method/system for granting access to a computer network, comprising:

• receiving at an access controller a TCP connection request having a source IP address and a destination IP address;
• determining whether the source must login, by comparing the source IP against profiles of authorized source devices (each profile including an IP);
• if the source IP is not matched, determining whether the destination IP is among a plurality of destination IPs associated with the access controller → if so, grant access without further authorization;
• otherwise providing a login page, authenticating credentials, and authorizing access.

The specification also discloses location‑based redirection to alternate content/portal pages, with a redirection response that appears to originate from the requested external server — the subject matter of the sibling application US 2010/0332615 and the related family claims.

Practical consequence: the references most dangerous to the '690 are not the general networking art on its cover, but the four that were actually chart against the '690 in litigation (Slemmer, ATCOM/IPORT, Micros‑Fidelio, and the Short PCT), plus the proxy/redirection patents named in the inequitable‑conduct allegations (Vu, Cohen, Brendel) and RFC 1919.

2. The most relevant prior art — references charted against the '690

These are drawn from Blueprint RF's invalidity‑contention exhibits in Nomadix v. Hospitality Core Services LLC, No. 2:14‑cv‑08256 (C.D. Cal.), as itemized in the "References Cited" section of the family member US 9,548,935 (pp. 42–43) and the Unified Patents family record.

Which of these are the best §102 candidates. On the contention charts as itemized, Slemmer (No. 1) and the ATCOM/IPORT white papers (No. 2) are the two references actually charted alone against the '690, and thus the only ones pressed as standalone §102 anticipation. Numbers 3–5 are charted in combinations, i.e., §103. Numbers 6–9 appear across the family's charts but I could not confirm they were charted against the '690 specifically (they are strongly associated with the sibling '269/'246 charts).

3. The '690's own front‑page "References Cited" (patent documents & NPL)

I could not retrieve the cover page of US 8,788,690 in isolation; the family members US 9,548,935 and US 10,341,243 carry substantially the same list. That list is dominated by examiner‑cited general networking/telephony art, e.g.:

• U.S. 4,026,642 (Tanaka, 5/1977); 4,233,661 (Bolton, 11/1980); 4,509,277 (Bolton, 4/1985); 4,649,533 (Chorley, 3/1987); 4,654,793 (Elrod, 3/1987); 4,677,588 (Benjamin, 6/1987); 4,691,346 (Vanacore, 9/1987); 4,757,267 (Riskin, 7/1988); 4,806,743 (Therery, 2/1989); 4,811,011 (Sollinger, 3/1989); 4,816,654 (Andrei, 3/1989); 5,019,697 (Postman, 5/1991); 5,030,807 (Landt, 7/1991); 5,048,079 (Harrington, 9/1991); 5,065,393 (Smith, 11/1991); 5,077,607 (Johnson, 12/1991); 5,113,499 (Ankney, 5/1992); 5,124,984 (Engel, 6/1992); 5,142,622 (Owens, 8/1992); 5,148,389 (Hughes, 9/1992); 5,140,545 (Johnson, 9/1992); 5,159,592 (Perkins, 10/1992); 5,166,931 (Riddle, 11/1992); 5,185,860 (Wu, 2/1993); 5,221,838 (Gutman, 6/1993); 5,226,124 (Brown, 7/1993); 5,235,595 (O'Dowd, 8/1993); 5,243,652 (Teare, 9/1993); 5,251,207 (Abensour, 10/1993); 5,225,161 (Nemirovsky, 11/1993) — etc.

• Foreign patent documents: AU 2003255101 (3/2004); AU 2006207853 (11/2007).

• Non‑patent literature (from the family front pages / Justia listing):

• DNS & Bind, Liu et al., O'Reilly, Sep. 1998 (URL: cse.unl.edu/~ylu/csce855/notes/OReilly-DNS-and-BIND.pdf);

• Yokoi, T. et al., "Internet Quality & Traffic Management (III)," Journal of the Institute of Electronics, Information and Communication Engineers, Jan. 25, 2000, vol. 83, no. ;

• Zhao et al., "Flexible Connectivity Management for Mobile Hosts," Stanford Univ. Technical Report No. CSL‑TR‑97‑735, Sep. 1997; and "Flexible Network Support for Mobility," MobiCom '98 (1998).

These front‑page items are §102(b) printed publications where dated before the 1998‑12‑08 priority date (DNS & Bind, Zhao/MobiCom), but the Yokoi (Jan. 2000) reference post‑dates the '690's Dec. 1998 priority and could only matter if the effective date were later. The majority of the U.S.‑patent items are background/sub‑combination art (telephony, vending, facsimile), not stand‑alone anticipators of the '690's access‑granting claims.

4. Cross‑reference and honesty caveats

• I could not pull the '690's actual granted claim set verbatim. My claim mapping above is reasoning from the specification/definitions in your authoritative text and from the sibling application US 2010/0332615. The precise independent/dependent numbering should be verified against the granted patent before relying on any §102 mapping.
• The contention charts themselves were not retrieved. I have the titles and captions of the Slemmer and ATCOM/IPORT charts against the '690 (Google/Unified Patents/Justia listings), but not the claim‑by‑claim element mapping. The "which claim(s)" column is therefore my reasoned projection, not a quotation of Blueprint RF's chart.
• Dates for Slemmer (6,226,677), Cohen (6,389,462), and the ATCOM white papers should be confirmed against the documents; I flagged the ones I could not verify.
• The inequitable‑conduct allegations are unproven. The court's order (2:14‑cv‑08256) records Blueprint's allegations that Nomadix "buried" prior art and omitted Brendel '139 and RFC 1919 — those are pleading allegations, and the case resolved on summary judgment and stipulation, not a finding of inequitable conduct.

Bottom line: The prior art that actually matters for U.S. 8,788,690 is Slemmer U.S. 6,226,677 and the 1998 ATCOM/INFO IPORT white papers — the only references charted as standalone §102 anticipators — with Micros‑Fidelio and the applicant's own Short PCT WO 98/40990 supplied in combination (§103). Vu '601, Cohen '462, Brendel '139, and RFC 1919 supply the "connection handshake data that appears to come from the external server" limitations central to the redirection claims. The roughly 30 U.S. patent documents and the foreign/NPL items on the front page are general background art, not anticipators.

Source anchors: Google Patents https://patents.google.com/patent/US8788690/en; family front matter https://patentimages.storage.googleapis.com/31/9b/04/e13c584a909ac3/US9548935.pdf (References Cited, pp. 42–43); Unified Patents family record https://portal.unifiedpatents.com/patents/patent/US-[9160674](/patent/9160674)-B2; court order https://cases.justia.com/federal/district-courts/california/cacdce/2:2014cv08256/[602501](/patent/602501)/69/0.pdf.

I'll research the prior art references associated with this patent before building the § 103 analysis.

I have a rich set of prior art references now. Let me nail down the key references and the actual claim text.

Obviousness Analysis — U.S. Patent No. 8,788,690 under 35 U.S.C. § 103

Scope, sources, and a necessary caveat

I built this analysis from the claim-language extraction and prior-art record associated with the '690 patent and its siblings — specifically the "OTHER PUBLICATIONS" prior-art/claim-chart lists reproduced on sibling patents US 9,548,935, US 10,341,243, and US 10,367,748, and the PTAB decisions/claim charts from IPR2016‑00081 and IPR2016‑00092. Citing:

• IPR2016‑00092 Decision on Institution ('806 patent) — grounds and reference identifications: https://www.docketalarm.com/cases/PTAB/IPR2016-00092/Inter_Partes_Review_of_U.S._Pat._8364806/docs/05-05-2016-Board/Decision_Granting_Institution-8-Decision_to_Institute_Inter_Partes_Review.pdf
• IPR2016‑00081 Decision on Institution ('269 patent): 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
• Prior-art / claim-chart lists naming the '690: https://patentimages.storage.googleapis.com/31/9b/04/e13c584a909ac3/US9548935.pdf (refs. 17–25) and https://patentimages.storage.googleapis.com/70/23/f5/f3a443a26d5cd2/US10341243.pdf
• Slemmer, US 6,226,677 B1: https://patents.google.com/patent/[US6226677B1](/patent/US6226677B1)
• District-court MSJ addressing the §§ 102/103 challenge: https://cases.justia.com/federal/district-courts/california/cacdce/2:2014cv08256/[602501/142](https://assignmentcenter.uspto.gov/search/patent/reelFrameDetail?reelFrame=602501-0142)/0.pdf

⚠️ Flagged uncertainty carried forward: the prior "Independent claims — plain-language overview" section stated that the numbered claims were not in the fetched document. My claim-element mapping below therefore rests on the reconstructed claim language, not a verbatim claim set. Before this analysis is relied on in any filing, every element must be re-keyed to the official USPTO claim text. Where an element appears only in my reconstruction, I say so.

1. Which § 103 applies, and the effective filing date problem

The '690 issued from App. No. 14/094,712, filed 2013‑12‑02 — i.e., after the AIA's 2013‑03‑16 first-inventor-to-file cutoff. But if the application never contained a claim with an effective filing date on or after 2013‑03‑16 (it is a continuation in a 1998/1999 chain), the pre‑AIA § 103(a) governs. That is the working assumption here.

This matters because it determines the prior-art date of the primary reference:

• Slemmer (US 6,226,677 B1) was filed 1999‑01‑15 and issued 2001‑05‑01.
  • It is § 102(e)(2) art as of its 1999‑01‑15 filing date.
  • If the '690's effective date is 1998‑12‑08, Slemmer's 1999 filing date does not predate it, and Slemmer is not § 102(e) art (and § 102(a) art only if it "invented" earlier — a fact question).
  • If the effective date is 1999‑12‑08 or 2000‑10‑20, Slemmer is § 102(e) art.
• Vu (US 5,623,601, issued 1997‑04‑22), Applegate (US 6,321,336 B1, issued 2001‑11‑20), Brendel (US 6,182,139), Cohen (US 6,389,462), Kirsch (US 6,189,030), and RFC 1919 predate all candidate dates; the ATCOM/IPORT white papers (Nov. 1998) and the Micros‑Fidelio materials are date-sensitive at the margins.

This ties directly to the unresolved discrepancy flagged in the bibliographic section (1998‑12‑08 vs. 1999‑12‑08 vs. 2000‑10‑20). Obviousness of the '690 cannot be finally assessed without resolving it, because Slemmer's status as prior art hinges on it.

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

A POSITA here would be a software/network engineer with a B.S. in computer science or electrical engineering (or equivalent) and roughly 2–4 years of experience with TCP/IP networking, HTTP, proxy/gateway design, and network access control — i.e., someone who understands TCP connection handshakes, browser redirect messages, transparent vs. classic proxying (RFC 1919), DHCP, and AAA databases (RADIUS/LDAP). Nomadix's own expert in the Blueprint litigation, Dr. Stuart Stubblebine, defined the technical backdrop in exactly these terms — including the meaning of "connection handshake" and the distinction between a "proxy" and a "browser redirect message." (Declaration of Dr. Stuart Stubblebine, Nomadix Ex. 2008: https://www.docketalarm.com/cases/PTAB/IPR2016-00092/Inter_Partes_Review_of_U.S._Pat._8364806/docs/02-10-2016-Patent_Owner/Exhibit-2008-Stubblebine_Decl_ISO_Opp_SJ_Mtn.pdf)

3. The independent claims (as reconstructed) and their element breakdown

4. The prior-art references in the record

The '690-specific charts in the record pair these as:

• Slemmer + Micros‑Fidelio (17 pp., Jul. 22, 2015; also 35 pp., Jul. 24, 2015);
• ATCOM/IPORT + Short PCT WO 98/40990 + ATCOM Manual + Micros‑Fidelio + Vu + '266 app + Cohen + Brendel + RFC 1919 (24 pp., Jul. 24, 2015; also 56 pp. chart with ATCOM 430 / Micros‑Fidelio / Short PCT, Jul. 17, 2015).

So the record already embodies two concrete § 103 combinations aimed at the '690.

5. Claim-by-claim obviousness

5.1 Claim C (spoofed-redirect / captive portal)

This is the strongest § 103 case in the record.

Conclusion: Slemmer alone discloses all substantive elements of Claim C except the express "profile database" framing; that framing is supplied by Micros‑Fidelio (or by the specification's own admission that RADIUS/LDAP profile stores were well known). Slemmer + IPORT, or Slemmer + Brendel/RFC 1919, supplies the transparent-proxy "appear-to-originate-from-the-origin-server" limitation with a reasonable expectation of success, because Slemmer itself already performs the spoof (its proxy answers "as if it were the web server"), and RFC 1919 documents that transparency as a known design choice.

5.2 Claim A (method: source-IP lookup with destination-IP bypass)

Conclusion: every element has a home in Slemmer, with the authorization/profile store supplied by Micros‑Fidelio (or RADIUS/LDAP, admitted in the spec). Slemmer alone is close to anticipatory for the substance of Claim A; adding Micros‑Fidelio (or Vu) is at most an obvious refinement.

5.3 Claim B (system: redirect to login page)

Claim B is Claim A's logic in apparatus form plus the "redirect to a login page" act. Slemmer's forced proxy server (FIG. 1, Block 130; FIG. 2, Block 204) is the "access controller," and its redirect to www.login.com is the redirect. Slemmer + Vu is the exact combination the Board found sufficient to institute IPR on the sibling '269 and '806 patents (which claim the same redirection/handshake subject matter) — a useful, on-point indication of how the PTAB viewed these references in this family:

"we institute an inter partes review … based only on … claims 1–20 as obvious based on Slemmer and Vu." (IPR2016‑00092 Decision on Institution, at 2.)

6. Motivation to combine (the dispositive § 103 question)

Under KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007), and MPEP 2143, the motivation may be found in the references, the nature of the problem, or common sense. Here it is plentiful:

1. Same field, same problem. All primary references address the same problem: controlling/redirecting a network user's access in a hospitality/ISP "captive portal" environment. KSR: combining known elements from the same field with predictable results is obvious.
2. Slemmer states the goal the '690 claims. Slemmer expressly identifies the need for "browser independent redirection which cannot be disabled" and for requiring the user to view/interact with content before freely browsing — i.e., the very portal-then-authorize flow of Claims A/B/C.
3. Slemmer → IPORT is a natural, documented combination. Slemmer (LodgeNet) and IPORT (ATCOM) were contemporaneous commercial hotel-gateway products solving the same problem; a POSITA would look to either. Slemmer's "sandboxing" and IPORT's "active user" list are the same technical mechanism.
4. Micros‑Fidelio supplies the profile/logic. Hotels already used PMS data (room, guest, check-in status) to decide who gets complimentary or paid access; feeding that into the gateway's authorization test is the predictable use of a known data source for its known purpose.
5. Vu / Brendel / Cohen / RFC 1919 supply the transparent-proxy and handshake mechanics. These are the standard toolkit for "answer the user as if you were the origin server" — the exact limitation the patentees argued distinguishes the claims. Adopting a documented transparent-proxy technique (RFC 1919; Vu; Brendel) to implement a redirect the gateway already performs is a textbook "use a known technique to improve a similar device in the same way" case (KSR).
6. Predictable results, no new interaction. Nothing in the combination produces an unexpected result; combining a forced-proxy gateway (Slemmer) with a profile store (Micros‑Fidelio) and transparent-proxy handshake (Vu/Brendel/RFC 1919) yields exactly the claimed captive portal.

Suggested primary combinations (strongest → weakest):

1. Slemmer + Vu — mirrors the Board's instituted ground for the sibling '269/'806; best-supported apparatus/method ground for Claims A and B.
2. Slemmer + Micros‑Fidelio — the '690-specific chart in the record; best for the source-IP-profile and destination-IP-bypass limitations of Claims A/B and the profile-based authorization of Claim C.
3. ATCOM/IPORT + Micros‑Fidelio + Vu (or Brendel / RFC 1919) — the '690-specific chart; strongest for the spoofed-redirect limitation of Claim C (the IPORT gateway's "sender-field" spoof) and the login/portal flow.
4. Slemmer + Applegate + IPORT — adds Applegate's express "redirect the destination IP address to an alternate machine" side-effect.

7. Evidence that cuts the other way (must be addressed)

• No tribunal has held the '690 claims obvious. The § 102/103 summary-judgment motion in Nomadix v. Hospitality Core Services was denied (Jan. 27, 2016), and it targeted claims 6–7 of the '246 patent, not the '690. The PTAB instituted only on the siblings ('269/'806) and only on Slemmer + Vu. There is no IPR against the '690 in the record. This is a defensive/prospective invalidity analysis, not a report of an adjudication.
• Nomadix's interposition arguments (from the preliminary responses). Nomadix argued, and the examiner twice accepted, that the references (esp. Slemmer) do not disclose the "connection-handshake" / "appear to be from the first device" limitations, and that Petitioner's inherency theory was technologically unsupported. A '690 § 103 attack must therefore affirmatively prove the handshake/spoofing limitation from the references — the IPORT "sender-field" description and Slemmer's "responds as if it were the web server" are the best evidence, and Brendel/RFC 1919 reinforce it.
• Same-inventor reference caveat (Short PCT WO 98/40990). Because WO 98/40990 is the patentees' own earlier PCT, its use as § 103 art is complicated (pre‑AIA § 103(c) common-ownership/common-inventorship considerations, and § 102(a) "by another" issues given the 1998/1999 priority). I would not rest a § 103 ground on it; the third-party references (Slemmer, Vu, IPORT, Micros‑Fidelio, Brendel, Cohen, Applegate, RFC 1919) are cleaner.
• Priority-date risk (see § 1). If the '690's effective date is 1998‑12‑08, Slemmer's 1999‑01‑15 filing post-dates it, and Slemmer may drop out as § 102(e)/§ 103 art — leaving the IPORT/Micros‑Fidelio combination (Nov. 1998) as the load-bearing ground. Resolving the 1998‑12‑08 vs. 1999‑12‑08 vs. 2000‑10‑20 discrepancy is a precondition to any final opinion.

8. Bottom line

• Under pre-AIA § 103(a) and KSR, the record supports strong obviousness positions on all three independent claims:
  • Claims A & B (source-IP profile lookup with destination-IP whitelist bypass, else login/authenticate): Slemmer + Vu (the Board's own instituted combination for the '269/'806 siblings) and Slemmer + Micros‑Fidelio.
  • Claim C (spoofed captive-portal redirect appearing to originate from the requested external server): Slemmer alone (proxy "responds as if it were the web server"; HTTP redirect to a login page), reinforced by Brendel / RFC 1919 and, most pointedly, by the ATCOM/IPORT gateway's documented re-insertion of the original destination address into the "sender" field.
• The motivation to combine is supplied by the shared field (hospitality/ISP captive portals), Slemmer's express statement of the portal-then-authorize objective, the commercial contemporaneity of Slemmer and IPORT, and the well-documented transparent-proxy technique (RFC 1919; Vu; Brendel) — all with predictable results.
• Confidence: high on the substance for Claim C and Claims A/B's destination-bypass and login elements; moderate on the "appear to originate from the external server"/connection-handshake limitation, which the patentee successfully defended at the examiner and PTAB level and which an attacker must prove affirmatively; and contingent on the unresolved effective-filing-date question that controls Slemmer's availability as prior art.

Verification items before reliance: (1) obtain the official numbered claim set and re-key every element; (2) resolve the priority date; (3) confirm the publication/availability dates of the IPORT white papers and Micros‑Fidelio materials against the chosen critical date. Flagged explicitly because the earlier sections already flagged the missing claim set and the priority-date inconsistency, and this analysis inherits both.