US 8156246

I'll search for this specific patent number on USPTO resources and CAFC dockets.

Let me gather more detail on the claims and any appellate activity.

US Patent 8,156,246 — Summary

Important scope note: I could not run a native USPTO Patent Center / CAFC docket query directly; my findings below come from patent databases (Google Patents, Justia, Unified Patents, Patexia/CourtListener) and the authoritative full text you supplied. I found no CAFC 2026 (or any year) docket activity for this patent, and I flag uncertainty where it exists.

Bibliographic data (from the supplied Google Patents record, consistent with secondary sources)

Continuity (from the patent's own text): the application is in the family of Nomadix "Gateway Device" filings, including the application that issued as US 6,636,894 (the "Redirection Application") and the applications issuing as US 8,713,641 and US 7,194,554, plus provisional 60/161,093 ("Location-Based Identification and Authorization for use With a Gateway Device"). Assignment records in the supplied text show security interests to NTT DOCOMO (2015, 2017), assignment to Gate Worldwide Holdings LLC (2018), and a quitclaim back to Nomadix (2019).

Abstract (verbatim, as published)

"Systems and methods for managing and providing content and services on a network system. Aspects of the invention include location-based determination of network content and services that may be provided to client computers. Other aspects of the invention include authorization and authentication components that determine access rights of client computers. Additional aspects include systems and methods for redirecting client computers to different network content. The disclosed systems and methods may be used in numerous network system applications."

Plain-language overview of the independent claims

⚠️ Caveat: The Google Patents page supplied did not contain a complete, verbatim claim listing (the claims section was truncated). The overview below is reconstructed from the abstract, the "Summary of the Invention," and the claim-patterned passages in the supplied text. Claim numbering and exact antecedent language should be verified against the official USPTO full-text document before being relied upon.

The patent appears to carry several independent claims (and method/system counterparts) falling into four functional families:

1. Location-based content substitution. The system receives a client computer's request for content, then produces "alternate content" based in part on a physical location identifier received with the request, and sends that alternate content back to the client. The alternate content differs from the requested content; the location identifier may originate from an intermediary network device. The specification defines the "physical location" broadly — e.g., a hotel room or room type, suite, office, airport terminal, airplane, building, multi-unit residence, wing of a building, or retail outlet.

2. Network-access management with spoofed-source redirection. A method implemented at a network management system that: (a) receives data packets from a client computer containing a request for network content from an external server; (b) determines authorization rights of the client computer based on a user profile drawn from a user profile database; (c) if the client is not entitled, generates a redirection response that causes the client to request content at a different network location, where the redirection response is configured to appear to the client as though it originated from the external server (i.e., the redirect is transparent/spoofed to look like the third‑party site); and (d) transmits that redirection response to the client.

3. Dynamic Authentication, Authorization and Accounting (AAA) for transparent access. A method/system in which the gateway device receives a request from a source computer for network access, identifies an attribute of the source from a packet (e.g., MAC address, User ID, VLAN ID, circuit ID, login/password, or physical port/location), looks up a source profile in a source profile database that is external to the gateway device (e.g., a RADIUS or LDAP database), and determines the source's access rights — which may be specific to a destination address, port, network, content type, or protocol, and may apply to each packet. The claimed system includes the gateway device, the external source profile database, and a AAA server that makes the entitlement/authorization determination. Configuration software on the client is expressly not required.

4. Redirection to a portal and/or login page for dynamic user creation. Received at the gateway device, a user request for a destination (e.g., an Internet address) is redirected to a portal page, and from there, where the user lacks rights, to a login page (which may be hosted local to the gateway device) at which the user supplies billing/identity information that is used to authorize access and update the user profile. The redirect is transparent to the user and requires no change to the user's home network settings and no added client software. A counterpart system claim recites a gateway device plus an AAA server that intercepts the request and performs the redirect, with the AAA server optionally located entirely within the gateway device and the portal page maintained on a local server.

Asserted-contour detail worth flagging

The claim passage the record presents as a network-access-management claim (family 2 above) recites that the redirection response is "configured to indicate to the computer that the redirection response originated from the external server" — i.e., a transparent/interception-style redirect rather than an explicit proxy redirect. That limitation is a distinguishing feature commonly relied on in Nomadix's enforcement of this family.

Litigation and post-grant activity (no 2026 CAFC appeal found)

• IPR2016‑00073 — Hospitality Core Services, LLC v. Nomadix, Inc., petition for inter partes review of U.S. Patent No. 8,156,246 filed Oct. 23, 2015 (petition and the '246 patent as Exhibit 1001 / prosecution-history excerpts as Exhibit 1002). The Google Patents litigation record states it was Not Instituted – Merits (NIM). Petitioner: Hospitality Core Services.
• C.D. Cal. 2:14‑cv‑08256 — Nomadix, Inc. v. Hospitality Core Services LLC (filed 2014). A court document in that file discusses the '246 patent's descent from the Nomadix '849/'266 patents and notes the examiner applied WO 98/40990 in related prosecution.
• C.D. Cal. 2:19‑cv‑10202 — a later Nomadix case in the Central District of California (per Unified Patents data).
• Nomadix, Inc. v. SIA Mikrotikls — additional asserted‑patent litigation involving the same Nomadix family.
• CAFC 2026: My searches surfaced no Federal Circuit docket in 2026 naming 8,156,246, and none in any year. Given the patent's 1998 priority / 2019 expiration and its "Expired – Fee Related" status, a 2026 appellate proceeding would be unusual. I cannot confirm any such appeal exists, and I am not asserting one does.

Explicit uncertainties

1. The complete verbatim claim set of 8,156,246 was not present in the supplied source; claim numbering and exact wording above are reconstructions and should be verified against the USPTO full text.
2. The "current assignee" field at Google Patents carries its own disclaimer and conflicts with the 2019 quitclaim back to Nomadix — treat ownership as Nomadix, Inc. subject to recorded security interests/assignments, pending verification.
3. I did not obtain a live USPTO Patent Center or CAFC PACER/docket query; the absence of 2026 CAFC activity is based on the searches above and should not be treated as a definitive docket clearance.

I'll research litigation involving US Patent 8,156,246. Let me run several targeted searches.

Let me gather more detail on the identified cases and PTAB proceedings.

Let me search for additional Nomadix cases that may have asserted the '246 patent, and confirm the MikroTik disposition.

Litigation involving U.S. Patent No. 8,156,246

Below is what I could verify from public litigation records and the patent's own "Family has litigation" entries. I'm interpreting the patent number literally: US 8,156,246 B2, granted 2012‑04‑10, titled "Systems and methods for providing content and services on a network system," originally assigned to Nomadix, Inc. (now shown as Gate Worldwide Holdings LLC). I did not include cases involving other Nomadix patents (e.g., the '894, '554, '727) unless the '246 itself was asserted.

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

Key ruling on the '246 patent: On January 27, 2016, Judge Dean D. Pregerson issued an Order re Motions for Summary Judgment (Dkt. 142), addressing cross-motions on infringement/non-infringement of the '246 and construing two disputed claim 6 terms — "redirection server" and "processor." The court treated the dispute as essentially claim construction. (Order, Dkt. 142)

Defendant also asserted counterclaims of invalidity and unenforceability (inequitable conduct) against the "captive portal" patents, including the '246. (Dkt. 69)

Related PTAB proceeding — not a court case but listed by Google Patents as litigation:

• Hospitality Core Services, LLC v. Nomadix, Inc., IPR2016-00073 (U.S. Patent 8,156,246)
  • Petition filed: October 23, 2015
  • Decision Denying Institution of Inter Partes Review: May 3, 2016 ("Not Instituted – Merits")
  • Petitioner's Request for Rehearing filed June 1, 2016; Board granted withdrawal of the rehearing request June 21, 2016 (the rehearing requests in IPR2016-00052 and ‑00073 were withdrawn per the parties' settlement). (PTAB docket via Patexia; Google Patents IPR link)

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

Supporting records: The AO‑120 form filed in this case lists the '246 patent among those at issue. (AO 120 report) Claim construction was litigated (Claim Construction Order, Dkt. 146; hearing transcript from the Oct. 31, 2022 Markman hearing), and the schedule was repeatedly amended, with trial ultimately set for October 2024 before the case was dismissed in July 2023. (Docket; Claim construction order)

3. Apparent/uncertain additional involvement: Nomadix, Inc. v. Hewlett-Packard Company, et al.

(Google Patents US10341243, listing HP contentions) — I could not independently confirm the full procedural history of the '246 in that case, so treat this as probable but not fully verified.

Summary

• Two district-court litigations are confirmed as asserting U.S. 8,156,246:
  1. Nomadix, Inc. v. Hospitality Core Services LLC (d/b/a Blueprint RF), 2:14-cv-08256 DDP (VBKx), C.D. Cal. — settled/dismissed 2016.
  2. Nomadix, Inc. v. SIA Mikrotikls, et al., 2:19-cv-10202 DDP (Ex), C.D. Cal. — dismissed July 25, 2023.
• One PTAB challenge to the '246: Hospitality Core Services, LLC v. Nomadix, Inc., IPR2016-00073 — institution denied (May 3, 2016); rehearing request withdrawn (June 21, 2016).
• Possible additional involvement in the HP/SolutionInc cases (2:09-cv-08441 and 2:10-cv-00381) via supplemental contentions, but this is not fully verified.
• No Federal Circuit appeal specifically resolving the '246 patent's validity or infringement was identified.

Caveats / limitations: PACER dockets are paywalled, so some procedural details (exact complaint filing dates, precise dismissal reasons, and any sealed settlement terms) could not be independently confirmed. Settlements in both district-court cases were confidential, so no outcome on the merits of the '246 claims was reached in either. The Google Patents page for US 8,156,246 links only the two C.D. Cal. cases (2:14-cv-08256 and 2:19-cv-10202) and IPR2016-00073; I found no other litigation asserting this specific patent number.

I'll start by verifying the proceeding(s) referenced in the patent text itself, since the structured block says "none" but the Google Patents page lists a PTAB case.

IPR2016-00073 is confirmed against this patent. Now let me check for any other proceedings, including the 2018 Guest-Tek petitions and later filings.

Now I need to pin down IPR2018-00376 (Guest-Tek) — the exhibit list ties it to application 13/244,866, which became this patent. Let me verify and check for later Guest-Tek petitions.

PTAB / AIA Trial Analysis — US 8,156,246

Threshold note on the source of record. The structured "PTAB proceedings on file" block returns zero AIA trials for this patent. That block is not corroborated by the patent's own front-page record or by the PTAB docket. The Google Patents record for US8156246 (https://patents.google.com/patent/US8156246/en) itself lists a PTAB case — "PTAB case IPR2016-00073 filed (Not Instituted - Merits)" — and independent verification confirms it. The ODP ingest gap is unsurprising: both proceedings against this patent were denied institution before any Final Written Decision, and ODP coverage of pre-2017, non-instituted PTAB cases is notoriously incomplete. Treat the ODP "none" as a data gap, not as evidence of no PTAB history.

Proceedings overview

On the canonical ODP feed: 0 proceedings. On verified independent research: 2 IPR petitions have named US 8,156,246 — both ended in institution denial, so the breakdown is 0 active / 0 claims invalidated / 0 claims sustained on the merits / 2 institution denials (one of which terminated after a global settlement); no PGR or CBM was ever filed.

The bottom line for a defendant is not "the patent is hardened." It is the opposite: no claim of '246 has ever been canceled, and — just as importantly — no claim has ever been reviewed on the merits. Both petitions died at the § 314(a) threshold, which is a finding that the petitioner failed to show a reasonable likelihood of prevailing, not a holding that the claims are valid. A demand letter citing claims 1–17 is not "sanction-bait," and you cannot leverage a PTAB kill: there is no FWD to point to, no § 315(e)(2) estoppel against anyone, and the prior art HCS assembled sits fully available in the public record. You are litigating an untested patent.

IPR2016-00073 — Hospitality Core Services, LLC v. Nomadix, Inc.

• Type: Inter Partes Review (35 U.S.C. §§ 311–319)
• Filed: 2015-10-23 (confirmed against the PTO Litigation Center report for the week of 2015-10-26, which lists "Trial Number – IPR2016-00073, Filing Date – 10/23/2015, Patent # – 8,156,246, Title – SYSTEMS AND METHODS FOR PROVIDING CONTENT AND SERVICES ON A NETWORK SYSTEM, Patent Owner – NOMADIX, INC., Petitioner – HOSPITALITY CORE SERVICES, LLC, Tech Center – 2400")
• Status: Terminated (verbatim from the docket). Combined with Google Patents' characterization, "Not Instituted - Merits": the Board denied institution, the petitioner's rehearing request was withdrawn, and the case closed.
• Judge panel: Howard B. Blankenship, Glenn J. Perry, and Trevor M. Jefferson (per the Board's 2016-06-21 Order, Paper 11).
• Petition grounds: Challenged claims 1–17 of U.S. Patent No. 8,156,246 B2 — the entire claim set implicated in this proceeding. The publicly posted petition exhibit list (Papers/Exhibits 1001–1044) indicates § 102/§ 103 grounds built on redirection/network-access art including Slemmer (a comparison flowchart of "Nomadix and Slemmer Redirection Techniques" is Exhibit 1038), U.S. Patent No. 5,623,601 to Vu (Exhibit 1041), ATCOM/INFO "iPORT" product literature and press releases (Exhibits 1033–1035, 1039), Wingate Inns high-speed-Internet materials (Exhibit 1036), a Network World article by Ellen Messmer dated 1998-12-07 (Exhibit 1037), and U.S. Provisional Patent Application No. 60/111,497 (Exhibit 1040). Support declarations came from William Peckham (Exhibit 1042) and a Supplemental Declaration of Keith Olson (Exhibit 1044, 2016-06-01). Caveat: I was unable to retrieve the full text of the 2016-05-03 denial or the petition itself, so treat the art list as indicative of the ground clusters rather than a verbatim ground-by-ground mapping.
• Institution decision: Denied on 2016-05-03 (Paper 8, "Decision Denying Institution of Inter Partes Review"). The Board did not find a reasonable likelihood that Hospitality Core Services would prevail on any of claims 1–17 under § 314(a). I do not have the panel's verbatim reasoning; the Patent Owner Preliminary Response was filed 2016-02-04 (Paper 6).
• Final Written Decision: None issued. This is dispositive for estoppel analysis — no FWD means no § 315(e) estoppel, and no claim-level patentability adjudication of any kind.
• Settlement / termination: Yes, but not as a PTAB settlement of a live trial. On 2016-05-27 the petitioner filed a Request for Rehearing (Paper 9); on 2016-06-20 it moved to withdraw (Paper 10, unopposed); the Board granted the withdrawal on 2016-06-21 (Paper 11), expressly stating it "will not issue any decision in response to Petitioner's withdrawn Requests for Rehearing." The parties then executed a confidential settlement agreement, and on 2016-06-28 filed a joint motion to terminate five Hospitality Core Services IPRs (IPR2016-00052 ('894), -00073 ('246), -00077 ('266), -00081 ('269), -00092 ('806)) plus the co-pending C.D. Cal. litigation, Nomadix, Inc. v. Hospitality Core Services LLC, No. 2:14-cv-08256. Terms are confidential and not public.
• Appeal: None possible. An institution denial is final and non-appealable under § 314(d). No FWD → no Federal Circuit appeal. There is no CAFC docket for this patent.
• Defensive value: Low as a sword, moderate as intelligence. The denial is a § 314(a) threshold ruling, not a validity holding — but it did cost Nomadix a real defense spend and shows the Board was unpersuaded by an iPORT/Wingate-era anticipation theory. Because there was no FWD, HCS and its privies face no estoppel (though a new petitioner was never exposed to it anyway). The genuine value: the full petition exhibit set is public, so you can lift HCS's Slemmer/Vu/iPORT/Wingate/60/111,497 package at a fraction of the cost — while remembering it failed.

Real links: the Board's order covering both -00052 and -00073 is at https://www.docketalarm.com/cases/PTAB/IPR2016-00052/Inter_Partes_Review_of_U.S._Pat._6636894/docs/06-21-2016-Board/Order-11-Granting_Petitioners_Motions_to_Withdraw_Requests_for_Rehearing.pdf; the paper-by-paper docket is at https://www.docketalarm.com/cases/PTAB/IPR2016-00073/ and https://services.patexia.com/lawsuits/Hospitality-Core-Services-LLC-v-Nomadix-Inc-id-65839/documents/. Cross-check against USPTO PTAB E2E (https://ptacts.uspto.gov/, formerly PTAB E2E case search) before relying on any of them.

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

Confidence flag. I identify this proceeding as an IPR against the '246 patent with high, but not certain, confidence. The mapping rests on the case's patent-owner exhibits, which consist of the prosecution history of U.S. Appl. No. 13/244,866 — and 13/244,866 is the application that issued as US 8,156,246 (per the patent's own front-page record). The procedural timeline corroborates it (see below). I could not retrieve a PTAB decision document that states the patent number in terms.

• Type: Inter Partes Review
• Filed: on or about 2017-12 (case number IPR2018-00376; the "Notice of Filing Date Accorded to Petition" is dated 2018-01-09, and Patent Owner's Power of Attorney is dated 2018-01-12). Treat the exact filing date as approximate — I could not retrieve the petition cover page.
• Status: Institution denied (per Nomadix's 2018-07-02 press release reporting the Board's denial of Guest-Tek petitions on 2018-06-29 — not a verbatim PTAB status string, which I did not retrieve).
• Judge panel: Not publicly retrieved. Tech Center 2400.
• Petition grounds: Challenged claims of the '246 patent (the 2018-04-09 Patent Owner Preliminary Response runs 47 pages). The patent-owner exhibit set (Exhibits 2002–2010) is essentially the '246 patent's own prosecution file: the Notice of Allowance for 13/244,866 dated 2011-12-30 (Ex. 2007), the Second Preliminary Amendment for 13/244,866 dated 2011-12-15 (Ex. 2008), the Notice of References Cited dated 2011-11-18 (Ex. 2010), the Interview Request responding to the Pre-Interview Communication of 2011-11-18 (Ex. 2007), and an Order Reexamination in Application No. 90/007,220 dated 2004-11-18 (Ex. 2006). Petitioner also cited the IPR2016-00077 petition as an exhibit (Ex. 1006), a tell that Guest-Tek was recycling the Hospitality Core Services filings. The precise § 102/§ 103 ground mapping per claim is not established by what I retrieved.
• Institution decision: Denied 2018-06-29. Nomadix's press release quotes the standard § 314(a) formulation — the PTAB "explained that Guest-Tek had failed to demonstrate a reasonable likelihood that it could show unpatentability of any of the claims from the Nomadix patents." (Note the PR also documents that Guest-Tek had issued a 2018-06-21 press release incorrectly claiming the PTAB had instituted trials on the same two patents — the reverse of the actual outcome. If you see that Guest-Tek release in a deal-room file, it is wrong.) Timing is internally consistent with the mapping: a PO preliminary response filed 2018-04-09 pushes the § 314(b) institution deadline to roughly 2018-07-09, and the denial issued 2018-06-29.
• Final Written Decision: None issued. No claim-level adjudication.
• Settlement / termination: No PTAB settlement in this case — it died at institution. (The parties' commercial dispute did not end: Nomadix sued Guest-Tek for breach of a license agreement in C.D. Cal. in 2016, seeking royalties Nomadix said exceeded $15 million.) Search results also show a second Guest-Tek denial announced in the same 2018-06-29 press release on a second Nomadix patent — the likely candidate is the '899 patent (IPR2018-00392), but I could not confirm that pairing and am not asserting it.
• Appeal: None. § 314(d) makes the denial non-appealable. However, Guest-Tek did litigate the PTAB-access question in another forum: it appealed a district-court judgment enforcing a license-agreement forum-selection clause against it, arguing the clause could not bar its IPRs — briefing reproduced at https://fingfx.thomsonreuters.com/gfx/legaldocs/byprjpe/nomadix%20brief2.pdf and https://fingfx.thomsonreuters.com/gfx/legaldocs/akpezgeozvr/nomadix%20brief1.pdf. That appeal (Ninth Circuit, not Federal Circuit) concerned contract/injunction and fee issues, not the validity of '246. I did not confirm its disposition; do not rely on it without checking.
• Defensive value: Modest and cautionary. It confirms that two unrelated challengers independently failed the § 314(a) threshold on this family — useful for framing the patent as non-trivial to invalidate — but it also shows Nomadix uses license-agreement forum-selection clauses to try to choke off PTAB challenges, and used a parallel breach-of-contract action to recover its IPR fees. If you are a licensee (or an ex-licensee), review your license's forum-selection and dispute-resolution clause before filing anything at the PTAB — that fight is real, expensive, and independent of whether your IPR is good.

Link to the press release: https://www.globenewswire.com/fr/news-release/2018/07/02/1532569/0/en/Patent-Trial-and-Appeal-Board-Denies-Guest-Tek-s-Petitions-for-Review-of-Nomadix-Patents.html

Adjacent activity that is not an AIA trial (do not miscount these)

• Ex parte reexamination 90/007,220 (Order dated 2004-11-18) appears in the '246-related exhibit record. Because the '246 patent did not issue until 2012-04-10, this reexam cannot have been directed at the '246 claims; it most plausibly concerned an earlier family member. Do not cite it as a '246 validity proceeding.
• CBM and PGR: I found no CBM or PGR against '246. The CBM transitional program sunset for new petitions on 2020-09-16, so CBM is no longer an option regardless of whether it ever was.
• District court: the '246 patent was asserted in C.D. Cal. 2:14-cv-08256, where the court addressed whether "processor" and "redirection server" in claim 6 are means-plus-function terms under Williamson v. Citrix Online (https://cases.justia.com/federal/district-courts/california/cacdce/2:2014cv08256/602501/142/0.pdf). That is a § 112 angle IPR cannot reach.
• Status of the patent itself: the Google Patents record lists anticipated expiration 2019-12-08 and legal status "Expired - Fee Related." If accurate, the patent is expired — no injunctive relief, only historical damages. The chain of title shows security interests to NTT DOCOMO (2015, 2017), assignment to Gate Worldwide Holdings LLC (2018-01-23), and a quitclaim back to Nomadix, Inc. (2019-11-22), yet Google still lists Gate Worldwide Holdings as "current assignee." Verify the live ownership and expiry record with the USPTO Assignment and Patent Center records before relying on either.

Strategic summary

Claim status of US 8,156,246. CANCELED: none. SUSTAINED on the merits: none — an institution denial is not a patentability holding, and no FWD was ever issued. UNTESTED: claims 1–17 (the set challenged in IPR2016-00073; I could not confirm whether the patent contains claims beyond 17). The only thing resembling "surviving claims" is the entire claim set, surviving by default. That is a materially weaker defensive posture than a patent with a clean merits win, because you cannot tell a court or an adversary "the Board already blessed these claims." Conversely, you cannot tell them the Board killed any of them either.

Estoppel landscape. There is no § 315(e)(2) estoppel — for anyone. Statutory estoppel attaches only to a petitioner in an IPR "that results in a final written decision under section 318(a)." Two institution denials and one pre-institution termination produce zero FWDs and therefore zero estoppel. Practically:

• Hospitality Core Services and its privies are not statutorily barred from re-litigating the same art — though General Plastic § 314(a) discretion makes a rerun on the same claims very unlikely to be instituted.
• Guest-Tek and its privies are likewise not estopped, subject to the same discretionary hurdle.
• You may raise any § 102/§ 103 ground on patents and printed publications that anyone could have raised, including all of HCS's Slemmer/Vu/iPORT/Wingate/60/111,497 art. Two hard constraints: § 315(b) bars your IPR if you were served with a complaint alleging infringement of '246 more than one year before filing; § 315(a)(1) bars it if you first filed a DJ action challenging validity. And you cannot get § 112, assignor estoppel, inequitable conduct, or system-art ("on-sale"/public-use) grounds into an IPR at all.

Pattern signals.

• Serial multi-patent petitioner campaigns. Hospitality Core Services filed five IPRs in October 2015 against five Nomadix patents ('894, '246, '266, '269, '806); all five resolved in the 2016 global settlement. Guest-Tek ran multiple waves (2018, 2019) across the Nomadix portfolio and even filed a follow-on petition on the '899 patent that was denied under General Plastic (IPR2018-01660, denial at Paper 10, 2019-08-08, rehearing denied — write-up at https://www.ptablitigationblog.com/strategic-decision-to-forgo-expert-does-not-allow-a-second-bite/). Conclusion: this portfolio attracts repeat challengers, but the Board has repeatedly used its § 314(a)/§ 325(d) discretion to shut down second bites. A first-time petition from a new petitioner is a different posture.
• No defensive aggregator confirmed. The "Unified Patents" string on the Google Patents page sits in the data-licensing attribution for the PTAB entry ("'Unified Patents PTAB Data' by Unified Patents is licensed under…"), not in a petitioner field. I found no evidence that Unified Patents or any other aggregator petitioned against the '246 patent. The https://portal.unifiedpatents.com/ptab/case/IPR2016-00073 link on the Google Patents page is a link to the data provider's copy of the same HCS case, not aggregator involvement.
• No patent-owner PTAB appeals. With no FWD, Nomadix had nothing to appeal to the Federal Circuit on this patent. Nomadix's litigation energy on this family has gone to district-court contract/licensing enforcement (including using a forum-selection clause to try to bar Guest-Tek's IPRs) rather than to PTAB appeals.

Recommended next steps

1. Do not accept "no PTAB activity on file." Pull the primary dockets. Request or download the full text of IPR2016-00073 Paper 8 (Decision Denying Institution, 2016-05-03), Paper 6 (POPR, 2016-02-04), Paper 9 (Request for Rehearing, 2016-05-27), and the 2018-06-29 denial in IPR2018-00376 from USPTO PTAB E2E (https://ptacts.uspto.gov/) or the PTAB Decisions site. The -00073 POPR and denial are the closest thing to a merits record that exists for '246, and they tell you exactly which claim limitations the Board found the art did not reach.
2. Report the ODP gap. If you are relying on the ODP feed for a clearance or FTO opinion, supplement it — the feed missed at least two proceedings against this patent. Cite the Google Patents front-page PTAB entry and the PTAB E2E dockets as the corrective.
3. Build your invalidity case from HCS's public exhibit set, not from the denial. Start with Slemmer, U.S. Patent No. 5,623,601 (Vu), ATCOM/INFO iPORT (1998 product literature and 1998-10-21/10-29 press releases), Wingate Inns, the Messmer Network World article of 1998-12-07, and Provisional Application 60/111,497 — all pre-dating the 1998-12-08 priority date, all public. Then differentiate on the claim limitations the Board evidently found lacking; do not simply re-file HCS's theory.
4. Calendar the § 315(b) bar now. Determine the service date of the earliest complaint alleging infringement of '246. If you are already past one year, IPR is unavailable and your validity case lives in district court (where § 112 indefiniteness, system art, and a § 282 burden structure are in play) or in a DJ action.
5. Read your license. If you have ever licensed Nomadix patents, the forum-selection/dispute-resolution clause may be used to attack an IPR filing and to seek fees, as it was against Guest-Tek. Get a written opinion on enforceability before you file.
6. Confirm the patent's expiry and current owner. The record indicates an anticipated expiration of 2019-12-08 and a possible ownership quitclaim back to Nomadix, Inc. on 2019-11-22, but Google also lists Gate Worldwide Holdings LLC as current assignee. Establish standing and the damages window (no post-expiration relief; back-damages limited by § 286) as early as possible — this may moot the entire dispute more cheaply than any IPR.

One explicit limitation: I did not retrieve the verbatim text of either institution decision, and the case-number-to-patent mapping for IPR2018-00376 is an inference from the prosecution-history exhibits (Application No. 13/244,866) plus a consistent procedural timeline. Please confirm both against PTAB E2E before you put either in a brief.

I'll research the recorded assignment chain, correspondents, and NPE signals for this patent.

Assignment Record Reconstruction — US Patent 8,156,246

Sourcing note (read first). I could not open the USPTO Assignment Center record directly (only web search was available to me in this pass), and the Google Patents legal-events data in the supplied authoritative text gives dates, conveyance types and party names but no reel/frame numbers and no correspondent. I therefore report the chain from the authoritative supplied record and explicitly mark every reel/frame and correspondent field as not retrieved. I have not invented any reel, frame, or attorney name. Where I have reel/frame data from a different record, I say so and label it as not transferable.

Verification entry points: USPTO Assignment Search and Assignment Center (search 8156246); Google Patents legal events for US8156246B2.

Inventors

Pattern notes / cautions:

• These three are the named inventors on the 2011 continuation (13/244,866), not on the 1998 original filing. All three are also named on the sibling Nomadix "dynamic AAA" filing that issued as US 7,194,554, so this is a stable, small inventor group that stayed with the original assignee — not an inventor-departure pattern.
• Departure dates within 12 months of filing: cannot be determined. No employment-termination or personnel data for Short/Pagan/Goldstein is available in a primary source I could reach. I am not asserting a departure pattern, and I am not asserting its absence.
• The 1998 priority and 2011 filing date mean the classic "inventors leave, portfolio gets sold" tell is inapplicable here — the distress in this chain is corporate/lender distress in 2015–2019, addressed below, not inventor attrition.

Original assignee

Nomadix, Inc. (Newbury Park / Agoura Hills, California), named assignee on the face of the issued patent.

• Did it ship products embodying the claims? Yes — and this specific patent is listed as product-practiced. Nomadix's own published Nomadix Product / Patent Listing states that its AG 2000, AG 2100, AG 2300, AG 2400, AG 3000, AG 3100, AG 5000, AG 5000 Metro, AG 5500, AG 5600, AG 5800, AG 5900, NWCG, NITO 500, NITO 1500, USG II, HSG, USG products "may be covered by" a patent list that includes 8,156,246. Source: https://nomadix.com/wp-content/uploads/library/Nomadix-Product-Patent-Listing.pdf. That is documentary evidence of product practice, not merely a marketing claim.
• Primary line of business: network gateway appliances and software for visitor-based networks — public-access gateways (USG/HSG line) sold into hospitality, airports, multi-dwelling units and convention venues; the patent family is the core "nomadic router / transparent gateway" technology (US 6,130,892; 6,636,894; 7,194,554; etc.).
• Current status: operating but acquired/controlled. Nomadix was acquired in 2015 as part of the InterTouch transaction (see below), taken through a 2018 New York state-court foreclosure sale, and (per the 2019-11-22 quitclaim) received the '246 patent back from Gate Worldwide Holdings. Third-party IP owner profiles currently list Nomadix's parent as DOCOMO InterTouch Interactive Pte. Ltd. — https://onscope.com/ipowner/en/owner/profile/[961383](/patent/961383)-nomadix-inc.html. Nomadix also filed new applications as recently as 2020–2023 (e.g., "Distributed management of secure wi-fi network," "Dual-network casting system"), which is inconsistent with a dissolved or purely shell existence.
• Serial-plaintiff history (relevant to the NPE analysis): Nomadix itself, not a downstream licensee, has been the plaintiff — Nomadix v. Second Rule LLC (C.D. Cal. 2007), Nomadix v. Hewlett-Packard (C.D. Cal. No. 09-cv-08441), Nomadix v. SolutionInc Technologies (C.D. Cal. No. 10-cv-00381), Nomadix v. Hospitality Core Services / Blueprint RF (C.D. Cal. No. 2:14-cv-08256, where the '246 was asserted), Nomadix v. Guest-Tek Interactive Entertainment (C.D. Cal. No. 2:16-cv-08033), and Nomadix v. SIA Mikrotikls.

Assignment timeline

All entries below are taken from the Google Patents legal-events ("reassignment") record in the supplied authoritative text. Reel/frame and correspondent were not retrievable in this pass and are marked "not retrieved" — I will not guess them. The USPTO-equivalent fields to fill are the reel/frame on each cover sheet and the "Correspondent Name / Address" block (usually the recording attorney or firm).

1. 2015-09-30 (executed date not shown) / recorded 2015-09-30 — Reel not retrieved / Frame not retrieved

   • Conveyance: SECURITY INTEREST (see document for details)
   • Assignor: Nomadix, Inc.
   • Assignee: NTT DOCOMO, INC. (11-1, Nagatacho 2-chome, Chiyoda-ku, Tokyo 100-6150, Japan)
   • Correspondent: not retrieved. (Context datum, explicitly not transferable: NTT DOCOMO's recorded correspondent on its own inventor-to-DOCOMO assignment filings is Osha Liang LLP, 909 Fannin, Suite 3500, Houston, TX 77010 — e.g. Reel 041149/0185 and Reel 045320/0470. I could not confirm Osha Liang is the correspondent on the Nomadix security-interest reel.)
   • Context: securitization — Nomadix's patent estate pledged as collateral for the InterTouch Holdings promissory note held by NTT DOCOMO.

2. 2017-08-29 (executed date not shown) / recorded 2017-08-29 — Reel not retrieved / Frame not retrieved

   • Conveyance: MODIFICATION TO PATENT SECURITY AGREEMENT
   • Assignor: Nomadix, Inc.
   • Assignee: NTT DOCOMO, INC.
   • Correspondent: not retrieved.
   • Context: securitization (amendment) — covenant/default-related amendment to the 2015 pledge, recorded roughly one month before GWH declared default.

3. 2018-01-23 / recorded 2018-01-23 — Reel not retrieved / Frame not retrieved

   • Conveyance: ASSIGNMENT OF PATENT SECURITY AGREEMENT
   • Assignor: NTT DOCOMO, INC.
   • Assignee: GATE WORLDWIDE HOLDINGS LLC
   • Correspondent: not retrieved.
   • Context: transfer of the lender's collateral position — DOCOMO assigned the note/security package (reported balance ≈ $50 million) to GWH, which had declared default in September 2017.

4. 2018-01-23 / recorded 2018-01-23 — Reel not retrieved / Frame not retrieved

   • Conveyance: ASSIGNMENT OF ASSIGNORS INTEREST (see document for details)
   • Assignor: Nomadix, Inc.
   • Assignee: GATE WORLDWIDE HOLDINGS LLC
   • Correspondent: not retrieved.
   • Context: foreclosure / lender credit-bid acquisition — GWH, the sole bidder in the New York state-court-supervised sale of InterTouch Holdings LLC, took the Nomadix entity and its IP. This is the operative ownership transfer, not a licensing-shell spin-out.

5. 2019-03-20 / recorded 2019-03-20 — Reel not retrieved / Frame not retrieved

   • Conveyance: SECURITY INTEREST (see document for details)
   • Assignor: Nomadix, Inc.
   • Assignee: KNOBBE, MARTENS, OLSON & BEAR, LLP
   • Correspondent: not retrieved (note: Knobbe Martens was Nomadix's litigation counsel in the Guest-Tek matter, e.g. Declaration of Mark Lezama, Nomadix v. Guest-Tek, C.D. Cal. No. 2:16-cv-08033).
   • Context: attorney's lien for unpaid fees — a law firm taking a patent security interest is a classic cash-stress indicator, not an NPE structure.

6. 2019-05-28 / recorded 2019-05-28 — Reel not retrieved / Frame 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 — the firm's security interest was satisfied/released roughly two months after recordation.

7. 2019-11-22 / recorded 2019-11-22 — Reel not retrieved / Frame not retrieved

   • Conveyance: QUITCLAIM
   • Assignor: GATE WORLDWIDE HOLDINGS LLC
   • Assignee: NOMADIX, INC.
   • Correspondent: not retrieved.
   • Context: asset return to the operating entity — GWH quitclaimed the patent back to Nomadix. This is the last recorded link, so the recorded chain terminates at Nomadix, Inc., not at GWH.

Corroborating corporate narrative (not an assignment record, but it explains the conveyances above): Koliner et al. v. … (S.D. Ohio No. 2:19-cv-01999) recites that Moorer formed InterTouch Holdings, LLC in 2015 to acquire InterTouch Pre and Nomadix; that InterTouch Holdings executed a promissory note held by NTT Docomo, collateralized by equity in InterTouch Pre and Nomadix; that NTT Docomo assigned the note and guarantee to GWH; that GWH declared default in September 2017 and, after a 2018 New York state-court action and a court-supervised fall-2018 sale in which GWH was the sole bidder, took ownership of InterTouch Holdings including Nomadix; and that InterTouch Topco/InterTouch Holdings filed Chapter 11 in Delaware, dismissed January 10, 2019, after which the New York court confirmed the sale. https://cases.justia.com/federal/district-courts/ohio/ohsdce/2:2019cv01999/[225883](/patent/225883)/27/0.pdf

Nothing in the record suggests the 8,156,246 assignments were handled through a patent-broker or NPE-formation channel. The conveyances are collateral, foreclosure, attorney-lien and lien-release instruments.

Contradiction to flag (per cross-reference instruction): the earlier section noted that Google Patents lists Gate Worldwide Holdings LLC as current assignee while also carrying a disclaimer. The last recorded conveyance in the supplied record is a 2019-11-22 quitclaim GWH → Nomadix, Inc., which directly contradicts GWH-as-current-assignee. Treat Nomadix, Inc. as the likely record owner as of 2019-11-22, subject to confirming the Assignment Center abstract.

Timeline diagram

timeline
    title Ownership of US 8156246
    1998 : Priority date
    2011 : Continuation filed
    2012 : Patent issued to Nomadix
    2014 : Suit filed vs Hospitality Core Services
    2015 : InterTouch acquires Nomadix
         : Security interest pledged to NTT DOCOMO
    2017 : Default declared on DOCOMO note
    2018 : DOCOMO assigns security to Gate
         : Gate wins foreclosure sale of Nomadix
    2019 : Knobbe lien recorded
         : Knobbe lien released
         : Gate quitclaims patent back to Nomadix
         : Patent term expires

NPE / troll-pattern signals

Additional distress markers found (not on the requested list, but material):

• 2019-03-20 attorney security interest to Knobbe, Martens, Olson & Bear LLP and 2019-05-28 release — textbook unpaid-legal-fee lien on a patent portfolio, ~2 months apart.
• Expiration / fee status: "Expired – Fee Related"; anticipated term expiry 2019-12-08. A patent lapsing for non-payment three weeks after the quitclaim back to Nomadix is itself a monetization-disappointment marker for this specific asset.
• IPR2016-00073 (Hospitality Core Services) was not instituted on the merits — the '246 survived the only post-grant challenge.

Verdict

Operating-company assertion.

Justification: The recorded chain does not contain a single NPE structural element — it is a secured-lender foreclosure sequence (Nomadix → NTT DOCOMO security interest 2015-09-30; modification 2017-08-29; DOCOMO → Gate Worldwide Holdings security assignment and Nomadix → Gate assignment of interest, both 2018-01-23) followed by an attorney's lien (Knobbe Martens, 2019-03-20; released 2019-05-28) and a quitclaim back to the operating company, Nomadix, Inc. (2019-11-22). The patent is documented as product-practiced — it appears by number in Nomadix's own AG/USG/HSG product-patent listing — and every assertion of the '246 and its family was brought by Nomadix in its own name against named commercial competitors (HP, SolutionInc, Second Rule, Hospitality Core Services/Blueprint RF, Guest-Tek, MikroTik), with the first '246 suit (C.D. Cal. 2:14-cv-08256, 2014) predating all recorded transfers. Verification link: https://assignment.uspto.gov/patent/index.html (search 8156246), cross-checked against Google Patents legal events.

Caveats I must state explicitly. (a) Reel/frame numbers and correspondent of record were not retrieved; the timeline above rests on the date/conveyance data in the supplied authoritative record plus the S.D. Ohio recap of the InterTouch/GWH foreclosure, so any contested ownership question should be verified against the Assignment Center abstract before reliance. (b) Nomadix's post-2015 conduct is licensing- and enforcement-weighted (a long campaign plus a 2018 Guest-Tek forum-selection dispute over PTAB challenges), which is NPE-adjacent behaviour by an operating vendor — but the entity sells products reading on the claims, so it does not meet the "NPE — high/moderate confidence" definition as those verdicts are defined here. (c) Ownership status after 2019-12-08 is best described as expired, so any current "assignee" field should be read as historical.

I'll research the prior art cited against US 8,156,246. Let me run several targeted searches.

Let me get the specific front-page references cited on the '246 patent.

Let me pull the front-page references and the IPR petition art.

I hit the tool-call limit before I could pull a verbatim copy of the '246 front page, so let me answer with what the searches actually produced — and be explicit about the one thing I could not obtain.

1. Scope limitation (please read first)

I could not retrieve the verbatim front‑page "(56) References Cited" list for U.S. 8,156,246 itself.

• The authoritative Google Patents text you supplied for US8156246B2 contains the bibliographic data, abstract, summary, and description, but the reference list and claims sections were not present in the delivered text.
• My web searches resolved to (a) the same Google Patents record, (b) family members' art lists (e.g., Unified Patents art lists for US‑10341243‑B2 and US‑8266269, and uspto.report's list for US‑8,364,806), and (c) litigation/family documents — not a certified reproduction of the '246 examiner's citation list.

Because of the strict "no fabrication" rule, the references below are grounded in the records my searches actually surfaced (the Nomadix family prosecution/litigation record), and I label each by source strength. Treat this as a well‑grounded reconstruction, not a certified copy of the '246 front page. Exact claim‑number anticipation mapping cannot be given because the '246 claim set was also truncated in the source.

2. Controlling law and date (needed for the §102 analysis)

• Earliest claimed priority: 1998‑12‑08 (per the record; external priority from US 09/458,569, US 09/458,602, and US 09/693,060).
• Application 13/244,866 was filed 2011‑09‑26, but as a continuation claiming benefit back to 1998, its effective filing date is pre‑2013‑03‑16, so pre‑AIA 35 U.S.C. §102 governs (subsections (a), (b), (e), (g)) — unless prosecution added claims not entitled to the 1998 priority, which I cannot verify here.
• Practical critical dates:
  • §102(b) statutory bar: prior art published/patented/on sale before 1997‑12‑08 (one year before the 1998‑12‑08 priority).
  • §102(a): known/used by others, or patented/published, before the invention date (presumptively before 1998‑12‑08).
  • §102(e): US patents/publications by another with an earlier effective filing date.

Important caveat: if any of the '246 claims are not entitled to the 1998‑12‑08 benefit, the AIA §102 regime (effective filing date on/after 2013‑03‑16) would apply instead. That determination is claim‑by‑claim and cannot be made from the truncated record.

3. Most relevant prior art documented in the family record

A. Art expressly relied on in related prosecution (highest confidence)

⚠️ I verified that WO 98/40990 was applied in related prosecution, but I did not independently verify its title, exact publication date, or the passages relied on. Confirm before use.

B. Art from Nomadix's own family‑wide invalidity contentions (Nomadix v. Hewlett‑Packard / Second Rule)

These were raised against the Nomadix family as a whole (09‑CV‑8441; 07‑1946) and, if timely, would apply to the '246's overlapping claims:

⚠️ I confirmed these references exist in the litigation record but I did not retrieve their bibliographic details or the technical content relied upon.

C. Classic US patent art appearing in a sibling's (56) list (same specification family)

uspto.report's reference list for US 8,364,806 (a sibling in the same 1998‑12‑08 family) includes the following, which are the type of §102 references the family examiner cited. Representative high‑relevance items:

** I am not fully certain of these items' exact titles/dates and, critically, whether they appear on the '246 front page specifically (they are documented for a sibling, not verified for the '246). Verify each against the '246 (56) list.

D. Art listed in Unified Patents' art set for family member US‑10341243‑B2

Programmatically related art (may or may not equal the '246 examiner citations):

More items in that art set include US‑6,787,110‑B1 and US‑7,194,554‑B1 — but these are Nomadix's own patents/same family and are generally not §102 prior art (common ownership / same inventive entity). Flagging that explicitly.

4. Which claims each reference potentially anticipates

Because the '246 claim set was truncated in the supplied source, I can only map references to the four claim families identified in the earlier analysis, not to literal claim numbers:

• Family 1 (location‑based alternate‑content substitution): Kikinis US 5,727,159 (content delivery) and the Vos publication are the most on‑point; neither is confirmed to disclose the "physical location identifier from an intermediary device" limitation.
• Family 2 (authorization‑based redirection with spoofed source): Levergood US 5,708,780, the SPINACH art, and the Ikudome work are the closest; the spoofed‑source ("originated from the external server") limitation is the likely differentiator.
• Family 3 (dynamic AAA w/ external source‑profile DB): SPINACH, Ikudome, and US 5,623,601 (secure gateway) are candidates; the "external RADIUS/LDAP source‑profile database" limitation is the likely differentiator.
• Family 4 (portal/login redirection, transparent, no client config): Levergood US 5,708,780 and the Vos publication are the strongest candidates; the "no reconfiguration of home network settings" limitation is the likely differentiator.

5. What I could not verify — recommended next steps

1. Pull the exact (56) front page of US 8,156,246 from USPTO Patent Center or the patentimages PDF (patentimages.storage.googleapis.com) — my searches did not return it.
2. Pull the IPR2016‑00073 petition (Hospitality Core Services v. Nomadix, filed 2015‑10‑23, record states Not Instituted – Merits). Its stated grounds would identify the precise art the petitioner asserted against the '246. I flagged its existence but could not retrieve its contents.
3. Pull the Nomadix v. HP (09‑CV‑8441) invalidity contention exhibits (Exhibits C1–C7, S1–S3, V1–V3) to get the Vos/SPINACH/Ikudome/Birrell bibliographic details.
4. Confirm the priority entitlement of each '246 claim to decide pre‑AIA vs. AIA §102.

If you can supply the '246 front‑page reference list or the claim set (both were absent from the delivered record), I can produce the precise, claim‑by‑claim §102 anticipation table you asked for.

I'll research the prior art cited on the face of US 8,156,246 and the references applied during its family's prosecution, then build the § 103 combinations.

Let me pull the specific cited references and the key prior-art content.

Obviousness Analysis — U.S. Patent No. 8,156,246 B2

Under 35 U.S.C. § 103 (as it applies to pre‑AIA applications)

Analyst note / scope caveats (carried forward and expanded from the summary section). The supplied Google Patents record for US 8,156,246 truncated both the "References Cited" list and the verbatim claim set. Accordingly: (a) the claim text I analyze below is the claim‑family reconstruction from the earlier section, and any limitation‑by‑limitation chart here must be re‑verified against the official USPTO full‑text before being relied on; and (b) the prior‑art citations I use are those I could independently verify (via the patent family's own face references, the Nomadix IPR record, the Nomadix v. Hospitality Core Services counterclaim/orders, and the Canadian Guest Tek decision). I flag below where a reference's qualifying date needs verification. This is a technical analysis, not a legal opinion, and it is not a validity clearance.

1. Governing law and the effective‑filing‑date issue

Which § 103 applies. The '246 issued from application 13/244,866 (filed 2011‑09‑26), a continuation of 09/693,060 (2000‑10‑20), which is a CIP of 09/458,569 and 09/458,602 (both 1999‑12‑08) and claims benefit of provisional 60/111,497 (1998‑12‑08). Because no claim has an effective filing date on or after March 16, 2013, the pre‑AIA §§ 102/103 framework governs. That matters because pre‑AIA § 103 permits "prior art" to be disqualified by an earlier date of invention, and pre‑AIA § 102(e) gives U.S. patents/published applications prior‑art effect as of their filing/priority date.

Mixed effective dates. The '246's content is not unitary in date:

This is favorable to an obviousness attack: the later the family's effective date, the more art qualifies, and several candidate references (Levergood '780; WO 98/40990; WO 98/12643; RFC 1919; the ATCOM IPORT system) comfortably predate even the earliest (1998‑12‑08) date.

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

Consistent with the Nomadix family's own litigation record, a POSITA as of the 1998–1999 window would be a networking engineer or computer scientist with a bachelor's degree and ~2–4 years' experience in TCP/IP internetworking, or equivalent, familiar with: IP routing, NAT/address translation, DHCP, HTTP/HTML, proxy servers (classical and transparent), ARP, and the RFC corpus (including RFC 1919 on transparent proxies). The Guest Tek decision (2021 FC 276, https://www.ippractice.ca/decision/?cite=2021+FC+276) and the C.D. Cal. Nomadix orders apply essentially this level.

3. The prior‑art references (verified evidence)

4. Element‑by‑element mapping to the four claim families

Family 1 — Location‑based substitution of "alternate content"

Why combinable. Substituting a location‑specific page for a requested page is nothing more than using a location attribute as the key to a lookup table that Levergood already teaches using a user/profile attribute as the key. A POSITA seeking to give a hotel/airport/retail‑venue operator a location‑relevant landing page would predictably swap a user key for a port/VLAN key — precisely the "substitution of one known element for another to obtain a predictable result" identified in KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398, 416 (2007). Using VLAN tagging or SNMP polling to obtain the location was conventional (802.1Q, RFC 1157). This family is the weakest of the four on its own, because "alternate content" is admittedly broad and the specification's own examples (hotel room, suite, airport, MDU, retail outlet) are conventional venue categories.

Family 2 — Network‑access management with spoofed‑origin redirection

(the limitation the earlier section rightly flagged as the enforcement contour: "the redirection response configured to indicate to the computer that the redirection response originated from the external server")

Why combinable. This is an almost textbook case of known elements arranged as in the prior art: Levergood supplies the redirect‑on‑failed‑authorization logic; IPORT/WO 98/40990/RFC 1919 supply the transparent‑proxy technique for making the redirect appear to come from the requested origin so that off‑the‑shelf browsers (which would otherwise reject an unrelated reply) accept it. The motivation is explicit in the art itself — the IPORT documents explain the handshake was "necessary to cause the protocol stack on the user's computer to accept the packets" (Peckham Decl., ¶5), and the Nomadix inequitable‑conduct counterclaim itself characterizes WO 98/40990 as describing "essentially the same process" (https://cases.justia.com/federal/district-courts/california/cacdce/2:2014cv08256/602501/69/0.pdf). The Bowman/Graham factors line up: scope and content of the prior art are squarely in the same field; the single difference (using the spoofing handshake for an authorization‑denial redirect rather than for a nomadic‑router reconfiguration) is a difference of application, not of technology.

Family 3 — Dynamic AAA with an external source‑profile database

Why combinable. "Authenticate a user at a gateway by sending packet‑derived attributes to a centralized RADIUS/LDAP server and honoring the returned authorization" was the industry‑standard AAA paradigm by 1998 (RADIUSs raison d'être). Levergood supplies the server‑side authorization decision; WO 98/40990 supplies transparent client access without reconfiguration; RADIUS/LDAP supply the external database location. The claimed advance — externalizing the profile DB and varying rights per source/destination — is a predictable use of known techniques to solve the known administrative problem the specification itself concedes ("administering and maintaining one consolidated database … is easier than multiple smaller databases").

Family 4 — Redirect to portal and then login page to create users

Why combinable. The IPORT system already disclosed almost this entire flow in 1998 (transparent intercept → browser redirect → portal/login page → payment → active‑user list), and Levergood supplied the session‑identifier/profile‑update mechanics. The claimed "dynamic creation of new users" is the natural, predictable consequence of combining a captive portal with a writable profile store.

5. The specific § 103 combinations, with motivations

Ground 1 — Primary: IPORT (or WO 98/40990) + Levergood '780.
Renders obvious the redirection‑with‑spoofed‑origin + authorization‑from‑profile families (2 and 4).
Motivation: both references address the same problem (controlling access to a network by a roving/hotel/airport user and steering that user to a login/portal page); both use browser‑redirectable HTTP; Levergood expressly teaches consulting an authorization server before serving the request; IPORT expressly teaches the transparent handshake that makes the redirect acceptable to an unmodified browser. Combining them yields nothing more than the predictable aggregation of two known techniques. (This is essentially the composite the Defendant pleaded as "designing around" by "practicing prior art.")

Ground 2 — Primary: Levergood '780 + Van Horne '430 + RADIUS/LDAP.
Renders obvious Family 3.
Motivation: externalizing authentication to a central server (RADIUS) and keying it on packet attributes was the standard network‑access‑server design; Van Horne supplies DHCP‑based client configuration and authorization; the administrative‑efficiency rationale is expressly stated in the '246 specification itself (a strong "reason that would have prompted the combination").

Ground 3 — Primary: WO 98/40990 + 802.1Q VLAN tagging / SNMP (RFC 1157).
Renders obvious the location‑identification aspects and the transparent gateway address translation.
Motivation: the '246's own disclosure describes VLAN tagging and SNMP querying as alternative implementations of location identification — an express admission that these were known, interchangeable mechanisms ("substitution of one known element for another"), satisfying the KSR rationale.

Ground 4 — Primary: Levergood '780 + WO 98/12643.
Renders obvious Family 1 (alternate‑content substitution).
Motivation: WO 98/12643 teaches redirecting a user to a selected host via a dynamically generated URL; Levergood teaches delivering content customized by profile. Using a venue/port identifier as the profile key to select venue‑specific content is a predictable design choice.

6. Objective indicia (secondary considerations) — limited and mixed

• Skepticism / unexpected results: weak. The record does not show that the claimed subject matter produced surprising results; the '246's own specification frames the advantages as convenience/administrative ("no configuration software," "consolidated database"), which courts generally treat as expected benefits of the known techniques.
• Commercial success: arguably probative but vulnerable. Nomadix's gateway products saw real adoption in hotels, MDUs, and airports; if a nexus can be proven, this supports nonobviousness. However, the record also shows Defendant allegations that the features were "combinations of known, pre‑existing inventions or technology," and the Guest Tek court declined to find Guest Tek's device infringed the other Nomadix patents — suggesting the asserted scope may be narrower than a blanket monopoly.
• Licensing/industry acquiescence: RADIUS/LDAP‑based centralized AAA was already ubiquitous, undercutting an argument that the combinations were non‑obvious.
• Failure of others: not established in the record I reviewed.
• Survival of IPR2016‑00073: the Board denied institution on the merits (May 3, 2016), and the rehearing request was withdrawn June 21, 2016 (PTAB/Patexia record). This is some evidence the petition's particular grounds did not meet the threshold, but a non‑institution is not a merits adjudication of validity and carries little weight against a properly articulated § 103 combination. It should not be over‑read either way.

7. Weaknesses, counterarguments, and honest uncertainties

1. Claim‑text gap (material). Because the verbatim claims were truncated in the supplied source, the mapping above is at the family level. A limitation‑by‑limitation chart against the actual issued claims is required before asserting a § 103 conclusion with confidence. Treat the combination identification as robust but the element‑level correspondence as provisional.
2. Priority/qualification verification is required for Brendel '139 and Van Horne '430 — I could confirm their identities and use as asserted art but not, in this review, their precise filing/priority dates for § 102(e) purposes.
3. The ATCOM IPORT evidence is affidavit‑based (Peckham, ¶¶2–7) and was submitted in IPR2016‑00081 (the '269 patent), not IPR2016‑00073. Its applicability to the '246 turns on whether the '246's redirection claims share the same effective date and scope — likely, given the patents' common specification, but needs confirmation.
4. Teaching‑away argument. Blueprint argued the patents "teach away from relying exclusively on DHCP" in favor of static address translation (MSJ record, 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). If accepted, it could complicate a DHCP‑based combination — but it does not help against combinations grounded on transparent proxy/IPORT, which use address translation rather than DHCP.
5. Inequitable‑conduct allegations are relevant context. The Defendant's counterclaim asserts that WO 98/40990 (and Kleinrock papers) were material prior art withheld or "buried", with specific page cites (WO 98/40990 pp. 3, 13). If substantiated, that (a) supports the materiality of the art to the family and (b) undercuts any inference of nonobviousness drawn from issuance.
6. No controlling § 103 adjudication exists. Neither C.D. Cal. case reached the merits (both settled/dismissed); the IPR was not instituted; and I found no Federal Circuit decision resolving the '246's validity.

8. Bottom line

On the record assembled above, each of the four reconstructed claim families would have been obvious under pre‑AIA § 103 to a POSITA as of the 1998–1999 window, through these principal combinations:

The strongest single challenge is IPORT (or WO 98/40990) in view of Levergood '780, because it hits the enforcement contour the earlier sections identified — the requirement that the redirection response "indicate … that the redirection response originated from the external server" — with prior art that expressly describes the gateway "proxying (pretending to be) the website requested by the user's browser" and inserting the original destination address in the "sender" field. Whether the issued claims are ultimately invalid turns on the precise claim language (unavailable here), the verified effective dates, and whether any family member's earlier‑filed claims operate as § 102(e) art against the very application that issued as the '246 — all of which I have flagged as requiring verification rather than asserting as settled.