US 7689716

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

Let me check for litigation and any 2026 CAFC activity, plus the independent claims.

US 7,689,716 — Analyst Summary

Scope note / confidence caveat up front: My searches of USPTO-derived sources (Google Patents, USPTO PatentCenter links, Unified Patents litigation portal, PTAB filing reports) confirmed bibliographic data for this patent. However, the full automatic text I retrieved was truncated immediately before the claims section, and my searches did not surface a verbatim claim listing. So the bibliographic summary below is well-grounded, while my claim descriptions are drawn from the patent's own "summary of the invention" passages and should be treated as paraphrase, not verbatim claim text. I flag the specific uncertainties at the end.

Bibliographic data

Assignee chain (per Google Patents reassignment records): Nomadix, Inc. → NTT DOCOMO, INC. (security interests, 2015 and 2017) → GATE WORLDWIDE HOLDINGS LLC (assignment of security agreement + assignment of assignors' interest, both 2018-01-23) → QUITCLAIM back to NOMADIX, INC. on 2019-11-22. This matters: the assignment record and the "current assignee" field do not tell a clean single story, and I would treat current ownership as requiring confirmation against the USPTO Assignment database rather than relying on the Google Patents "current assignee" label.

Abstract (as published)

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

Plain-language overview of the independent claims

The specification's summary-of-invention section recites what appear to be the independent-claim families. In plain terms:

1. Method for selectably controlling/customizing source access to a network. A gateway device receives a request from a source computer; the gateway identifies an attribute of the source from a packet the source computer sent; the gateway looks up a source profile in a source profile database located externally to the gateway device; and the gateway determines the source's access rights from that profile. The core assertion is "transparent" access — no configuration software on the source computer.

2. System counterpart (selectably controlling/customizing access). A gateway device + an external source profile database keyed by a packet-derived source attribute + an AAA server that decides (a) whether the source is entitled to access the network and (b) what the source's access rights to destination sites are.

3. Method for redirecting a source attempting to access a destination through a gateway device. Same identification/lookup/access-rights determination, framed around the redirection scenario; the gateway need not require network-specific software on the source computer.

4. System for enabling transparent communication between a computer and a service provider network. A computer + network gateway device + external service-provider authentication server holding a source profile database, which compares source data (attribute or login information) against stored profiles to decide access.

5. Method for dynamically creating new users with transparent access to a destination network. Receive the request at the gateway; check a user profile in a user profile database; if the profile lacks rights, redirect the user to a login page; forward to the destination if rights exist. Notable dependent/summary features: redirect via HTTP response to the browser, login page maintained locally to the gateway, updating the user profile database with entered user information.

6. System counterpart for dynamically creating new users. Gateway device + user profile database + AAA server that redirects to a login page when stored access information does not establish the user's right of access.

7. Method for redirecting users with transparent access to a destination network. Receive a request for a destination (e.g., an Internet address) and redirect the user to a portal page (administrator-created or user-customized), while the user's computer remains configured for its home network and no configuration software is installed.

8. System counterpart for redirecting users to a portal page. Gateway device + AAA server that intercepts the request and redirects to a portal page; in one described embodiment the AAA server is located entirely within the gateway device, with the portal page on a server local to the gateway.

Two features recur across these families and are worth noting because they are the practical differentiators: (i) identification from packet-borne attributes (MAC address, VLAN tag, circuit ID, location/port identifier, user ID) rather than requiring user input, and (ii) the external/centralized source profile database (RADIUS or LDAP), justified in the specification as easing administration across many gateway devices and preserving ISP confidentiality.

Litigation and PTAB posture

• District court: The Google Patents family entry lists C.D. Cal. cases 2:09-cv-08441, 2:10-cv-00381, 2:11-cv-02604, and 2:14-cv-00322, plus a "first worldwide family litigation" Darts-IP reference. The related Nomadix v. Hospitality Core Services LLC d/b/a Blueprint RF matter (C.D. Cal. 2:14-cv-08256 DDP) asserted the 8,156,246 / 8,266,266 / 8,266,269 / 8,364,806 / 8,788,690 patents per the Stubblebine declaration — i.e., I did not find the '716 itself in that asserted set.
• PTAB: The October 2015 petition wave by Hospitality Core Services targeted 8,266,266 (IPR2016-00077), 8,266,269 (IPR2016-00081), and 8,364,806 (IPR2016-00092). I found no IPR on the '716 in my searches. I cannot rule one out from the sources I reached.

CAFC 2026 dockets — negative finding

My searches returned no authoritative evidence of any 2026 Federal Circuit docket, appeal, or decision involving US 7,689,716. I want to be explicit rather than hedge: this is a negative search result, not proof of absence. Two reasons I could not establish a firm negative: I hit my tool-step ceiling before completing Federal Circuit docket queries, and the free sources I reached (Google Patents, Unified Patents' portal, PTAB filing digests) are not CAFC docket systems. A definitive answer requires a direct query of the Federal Circuit's CM/ECF docket and PACER — I did not get to run that.

Contextually relevant: the patent's recorded adjusted expiration is 2022-02-22, and its status is "Expired – Lifetime." That makes a fresh infringement appeal arising in 2026 unlikely, though it does not preclude a 2026 appeal from an IPR or a damages/standing dispute on an expired patent.

Uncertainty flags

1. Exact independent-claim numbering and verbatim language — not verified. The eight claim families above derive from summary passages in the specification, not from the claim set. If you need to chart or assert these claims, pull the claim listing from USPTO PatentCenter or the patent PDF.
2. Total claim count — unknown to me from these sources; I am not stating one.
3. Priority date — 1998-12-08 (Google Patents) vs. 1998-12-07 (Unified Patents). Unresolved.
4. Current ownership — the listed current assignee (Gate Worldwide Holdings LLC) conflicts with the 2019-11-22 quitclaim to Nomadix, Inc. Confirm at the USPTO Assignment database.
5. CAFC 2026 — negative finding only; PACER/CM-ECF not queried.

Sources: https://patents.google.com/patent/US7689716/en (full text, bibliographic data, assignment records, classifications, litigation links); https://wiki.golden.com/wiki/US_Patent_7689716_Systems_and_methods_for_providing_dynamic_network_authorization%2C_authentication_and_accounting-W4NZRMX (abstract, grant/assignee attributes); https://natlawreview.com/node/53960/printable/pdf (PTAB IPR petition listings); https://www.docketalarm.com/cases/PTAB/IPR2016-00092/ (Stubblebine declaration, Blueprint RF asserted-patent list); https://portal.unifiedpatents.com/patents/patent/US-[6128664](/patent/6128664)-A (priority-date and assignee cross-reference).

I'll search for litigation information on US patent 7689716 across patent litigation databases.

Let me gather case-specific details from litigation databases.

Litigation Involving U.S. Patent No. 7,689,716 ("the '716 Patent")

Scope note on interpretation: I interpreted the number literally as 7,689,716 (the "716 Patent"), issued March 30, 2010, filed June 28, 2006, claiming priority to Dec. 8, 1998, original assignee Nomadix, Inc., current assignee Gate Worldwide Holdings LLC, legal status "Expired – Lifetime" (adjusted expiration 2022‑02‑22). I excluded cases that asserted only other Nomadix family patents (e.g., the '892, '894, '399, '727, '995, '110, '554 patents) except where they help date/contextualize the '716.

Because the '716 Patent did not issue until March 2010, any case filed earlier could not have asserted it at filing; it was added later via (amended) infringement contentions. I flag this where relevant.

Cases I could confirm in which the '716 Patent was asserted / placed at issue

1. Nomadix, Inc. v. Hewlett-Packard Company, et al. (lead consolidated case)

• Plaintiff: Nomadix, Inc.
• Defendants: Hewlett-Packard Company; Wayport, Inc.; iBAHN Corporation; Aruba Networks, Inc.; and Solutioninc Technologies Ltd. (per the court's June 13, 2011 order naming these five collectively as "Defendants").
• Jurisdiction: U.S. District Court, Central District of California (Western Division).
• Case No.: CV 09‑08441 DDP (VBKx).
• Filing date: November 17, 2009 (Complaint).
• '716 involvement: The original complaint asserted U.S. Pat. Nos. 6,130,892; 7,088,727; 7,554,995; 6,636,894; 7,195,554; 6,868,399; and 6,789,110 (the '716 did not yet exist). After the '716 issued in March 2010, Defendants' Supplemental Joint Invalidity Contentions dated July 22, 2011 added Exhibit C7 directed at the '716 Patent; the court's opinion confirms the '716 was in suit and Defendants moved (unsuccessfully) to supplement contentions asserting the '716 was invalid over the SPINACH system and other references.
• Outcome/status: Settled — announced November 27, 2012, including a license to HP under key portions of Nomadix's patent portfolio; terms undisclosed.
• Sources: Justia order, N.D. Cal.…C.D. Cal. 2:09‑cv‑08441; casemine opinion (’716 / SPINACH); settlement announcement.

2. Nomadix, Inc. v. Solutioninc Technologies Limited

• Plaintiff: Nomadix, Inc.
• Defendant: Solutioninc Technologies Limited (counter‑claimant).
• Jurisdiction: U.S. District Court, Central District of California (Western Division).
• Case No.: 2:10‑cv‑00381 DDP (VBKx).
• Filing date: January 19, 2010 (Complaint).
• '716 involvement: The asserted patents in this case are reported to include 6,130,892; 7,088,727; 7,554,995; 6,636,894; 7,194,554; 6,868,399; 6,789,110; 7,689,716; and 6,875,009. The case was consolidated with the HP case (2:09‑cv‑08441) for pretrial purposes.
• Outcome/status: Claim-construction/Markman rulings issued (e.g., Oct. 24, 2011 claim-construction order by Judge Pregerson); the case proceeded within the same pre‑trial program that resolved via the HP settlement. I did not find a separate reported judgment on the '716 in this docket.
• Sources: Studicata summary (patent list incl. 7,689,716); Solutioninc filing referencing Case No. 2:10‑cv‑00381; Stanford NPE database.

3. Nomadix, Inc. v. iBAHN General Holdings Corporation

• Parties: Nomadix, Inc. and iBAHN General Holdings Corporation (Nomadix filed an amended answer to iBAHN's complaint and counterclaims, so iBAHN pursued affirmative claims/counterclaims here).
• Jurisdiction: U.S. District Court, Central District of California.
• Case No.: CV 11‑02604 DDP (VBKx) — matches the 2:11‑cv‑02604 listed on the patent's Google Patents "litigation" section.
• Filing date: 2011 (docket entry reflects Nomadix's amended answer filed May 2, 2011).
• '716 involvement: This case is listed on the USPTO/Google Patents family-litigation data for the '716 Patent.
• Outcome/status: Not confirmed in my search results; I did not locate a final judgment specific to this docket.
• Source: USPTO/Google Patents family document list citing "Nomadix, Inc. v. iBahn General Holdings Corporation… Case No. CV11‑02604 DDP (VBKx)".

A case listed on the patent's face that I could not verify

4. C.D. Cal. Case No. 2:14‑cv‑00322

• The Google Patents page for US 7,689,716 lists a fourth litigation entry: "US case filed in California Central District Court … case/2:14-cv-00322."
• I was unable to confirm the plaintiff(s), defendant(s), asserted patents, or outcome for this docket within my searches. I am explicitly flagging this rather than guessing the parties. Note it is numerically distinct from the better‑known Nomadix v. Hospitality Core Services (Blueprint RF) case, which was No. 2:14‑cv‑08256 and asserted 6,636,894; 6,868,399; 8,156,246; 8,266,266; 8,266,269; 8,364,806; and 8,788,690 — not the '716.
• Source for the 2:14‑cv‑00322 listing: Google Patents US7689716 page – litigation section.

Related family litigation (context — '716 itself was not asserted, because it did not exist yet)

• IP3 Networks, Inc. v. Nomadix, Inc. (declaratory judgment), Case No. 04‑cv‑1485 (DMS/BTM) (POR), U.S. District Court, Southern District of California (2004–2005). Documents from this case appear in the '716 file history as cited material — meaning they were references of record, not an assertion of the '716.
• Nomadix, Inc. v. Second Rule LLC, Case No. 07‑cv‑1946 DDP (VBKx), C.D. Cal., complaint filed March 23, 2007 (asserting 6,130,892; 7,088,727; 6,636,894; 6,857,009; 6,868,399 — again, not the '716, which issued in 2010).
• Linksmart Wireless Technology, LLC v. T‑Mobile USA, Inc., et al. (E.D. Tex., Nos. 2:08‑cv‑00264‑DF‑CE and consolidated cases). Nomadix and Bestcomm Networks were third‑party defendants brought in by Best Western International; this concerned Linksmart's patents, not the '716.
• Nomadix v. Guest‑Tek Interactive Entertainment Ltd. (C.D. Cal. No. 2:19‑cv‑04980‑AB‑FFM; Ninth Circuit No. 20‑55439). This is a contract/forum‑selection‑clause dispute stemming from a 2010 license and Guest‑Tek's PTAB inter partes reviews of Nomadix patents. I could not confirm the '716 specifically was among the patents at issue in that dispute.
• Sources: US7689716 file-history references (IP3 Networks; Second Rule); Guest‑Tek 9th Cir. opening brief.

PTAB / appellate activity specifically on the '716

• I found no confirmed IPR, PGR, or CBM proceeding directed specifically at the '716 Patent in my search results, and no Federal Circuit appeal specifically adjudicating the '716 Patent. Nomadix family patents were subject to IPRs generally (e.g., IPR2016‑00081 against U.S. 8,266,269; the Guest‑Tek IPRs referenced above), but I cannot attribute any of those to the '716 without confirmation.

Summary table

Caveats

• The Google/Unified Patents litigation data and the file-history documents I retrieved are not full PACER dockets; I could not retrieve PACER or CourtListener dockets directly in this session to confirm every filing date, party, and terminal disposition. Where I say "not confirmed," I mean exactly that.
• Case 2:14‑cv‑00322 is listed on the patent's own page but I could not tie it to named parties — please verify via PACER/CourtListener before relying on it.
• Some sources appear to reference related patents as "7,195,554" (in the HP complaint list) while the patent's own specification refers to "7,194,554"; I am not auto‑correcting these — I have preserved each as found and recommend confirming the correct number in the source docket.

If you want, I can attempt targeted PACER/CourtListener lookups for the four dockets (particularly 2:14‑cv‑00322 and 2:11‑cv‑02604) to fill in the missing parties, filing dates, and dispositions.

I'll verify the structured list against public sources before writing anything up.

Initial hits are mostly about other "768" patents (Regents' '768, PayRange's '768) and Nomadix's sibling patents. Let me target 7,689,716 specifically.

Proceedings overview

AIA trial proceedings on file for US 7,689,716: zero. The USPTO Open Data Portal returns no IPR, PGR, or CBM for this patent, and my independent web sweep (PTAB petitions, institution decisions, Docket Alarm/IPR trackers, and the patent's own Google Patents family-litigation block at https://patents.google.com/patent/US7689716/en) surfaced no petition ever filed against 7,689,716 — no proceedings are active, none invalidated claims, none settled, and none were denied institution, which means every claim of the '716 patent is untested at the Board and there is no § 315(e)(2) estoppel running against anyone. The bottom-line posture for a defendant is unusual and, on balance, favorable: there is no IPR win to inherit and no FWD to cite, but there is also no adverse PTAB record pinning your validity defense — and critically, the patent itself is expired (per the Google Patents legal-status block, "Expired – Lifetime," adjusted expiration 2022-02-22), so the realistic dispute is historical damages, not injunctive exposure.

No proceedings to itemize

There is no {PROCEEDING_NUMBER} to report for 7,689,716. I will not manufacture one. Two things a careful reader should know about why the record looks this way:

1. The "768" search collisions are not this patent. Public documents referring to "the '768 patent" in an IPR/PGR context almost always mean a different patent — e.g., the Regents of the University of Minnesota interleaver patent (U.S. 7,768,230/7,688,768 line) or PayRange's U.S. 10,891,608 family. Those hits are not US 7,689,716.
2. Nomadix's PTAB exposure was on siblings, not on 7,689,716. The Board has substantial Nomadix history on related family members — this is where the art and the arguments live, and it is the most useful adjacent intelligence for a defendant — but it is not a proceeding on this patent:

To be explicit about what I verified on the siblings: in IPR2016-00081 the panel (APJs Howard B. Blankenship, Glenn J. Perry, Trevor M. Jefferson; opinion by Perry) instituted on 2016-05-05 on claims 1–20 over the sole ground of obviousness based on Slemmer (U.S. 6,226,677) in view of Vu (U.S. 5,623,601), while declining the § 102(e) anticipation ground and the Slemmer/IPORT/Applegate combination. The identical institution structure appears in IPR2016-00092 (same panel, opinion by Blankenship, entered 2016-05-05, claims 1–20, Slemmer + Vu). Sources:

• IPR2016-00081 institution: 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
• IPR2016-00092 institution: 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

I did not retrieve final written decisions for those sibling proceedings, so I will not state claim-level outcomes for them. Do not treat the table above as validity findings about 7,689,716.

The only 7,689,716-specific administrative footprint I could identify is district-court activity, not PTAB: the patent appears as Exhibit C7 in Defendants' Supplemental Joint Invalidity Contentions in Nomadix, Inc. v. Hewlett-Packard Co., No. 09-CV-8441 (C.D. Cal.) and Nomadix, Inc. v. Solutioninc Technologies Ltd., No. 2:10-CV-00381 (C.D. Cal.), dated 2011-07-22 (11 pages). That is a prior-art roadmap developed by litigation defendants, not an instituted trial.

Strategic summary

Claim status. Claims of 7,689,716 are UNSUSTAINED, UNCANCELED, and UNTESTED at the PTAB — every claim remains in force as issued, and all are expired. There is no claims CANCELED list, because no AIA trial ever reached a final written decision on this patent. If a demand letter cites a particular claim, that claim has not been canceled by the Board, but it also carries no affirmative PTAB validation — a nominal patent owner cannot tell you the Board confirmed it, and you cannot tell the owner the Board killed it. The real vulnerability of this patent is temporal, not procedural: with an adjusted expiration of 2022-02-22, any continuing royalty theory must rest on pre-expiration conduct, and 35 U.S.C. § 286 caps recovery to infringement occurring within six years before the complaint was filed.

Estoppel landscape. Because no IPR/PGR was instituted and no FWD issued against 7,689,716, § 315(e)(2) estoppel is a null set — no petitioner and no privy is barred from any ground on this patent. That cuts both ways but mostly for the defendant: the entire § 102/§ 103 prior-art universe is available to you, and you are not limited to art "reasonably could have been raised" by some earlier challenger. What does bite is the mirror-image constraint: § 315(b). If your client (or a real party in interest/privy) was served with a complaint alleging infringement of 7,689,716 more than one year ago, an IPR petition is time-barred. The family's own history shows how sharp that clause is — Hospitality Core Services and Guest-Tek each had to time petitions to their respective litigations.

Pattern signals. The recurring challengers against this Nomadix family were Hospitality Core Services / Blueprint RF (2015–2016 petitions, IPR2016-00081 and -00092) and Guest-Tek Interactive Entertainment (a cluster of December 2017 petitions, one of which is listed as filed 2017-12-22 against 8,266,266 and 2017-12-28 against 8,725,899). No defensive aggregator (e.g., Unified Patents) appears in the 7,689,716 chain; the '716 litigation is a collection of hotel/HSIA-industry defendants rather than a coordinated anti-troll campaign. Note also the Guest-Tek proceedings were collateral-damaged by contract, not by the Board: Nomadix obtained a permanent injunction from the C.D. Cal. enforcing a forum-selection clause in a 2010 license agreement to force Guest-Tek to withdraw its PTAB filings, and the Ninth Circuit affirmed (Nomadix, Inc. v. Guest-Tek Interactive Entertainment Ltd., No. 20-55439). Guest-Tek's opening brief is at https://fingfx.thomsonreuters.com/gfx/legaldocs/byprjomqlpe/nomadix%20brief2.pdf, and the practitioner write-up is at https://www.sternekessler.com/news-insights/insights/inter-and-intra-circuit-split-emerges-forum-selection-clauses-barring/. Check your client's own Nomadix license agreements for a forum-selection clause before you file anything at the PTAB — 7,689,716 sits in the same portfolio/licensing program, and that clause is the single most effective non-merits way to lose a PTAB challenge in this family.

Recommended next steps

1. Confirm the negative before relying on it. Re-run the proceeding list at PTAB E2E (https://ptacts.uspto.gov/ptacts/public-informations) and the Google Patents family/litigation tab (https://patents.google.com/patent/US7689716/en) as of today (2026-10-01). My sweep found nothing, but ODP ingest and third-party trackers lag, and a newly filed petition would not necessarily appear in the canonical block.
2. Because there is no PTAB activity, there is no FWD to cite. Do not tell a court or an adversary that any claim of 7,689,716 has been canceled or held unpatentable — that would misrepresent the record. Your best affirmative-use path is a § 282 district-court invalidity case, and the ready-made starting point is the defendants' 2011-07-22 contentions (Exhibit C7) plus the Slemmer (U.S. 6,226,677) + Vu (U.S. 5,623,601) combination the Board found sufficient to institute on the sibling '269 and '806 patents on 2016-05-05. Art that clears the institution threshold against the family is a credible basis for a § 103 attack here — subject to the caveat that the claims differ and institution ≠ unpatentability.
3. Watch the calendar on § 315(b). If you want a PTAB forum at all, the petition must be on file within one year of service of the first infringement complaint on your client or its privies. With no estoppel to worry about and no prior petitioner to piggyback on, a timely IPR is your only chance to create claim-level cancellation — but weigh it against the expired-patent dynamic, where the marginal benefit of a PTAB win may be smaller than a clean § 286 damages cut.
4. Screen for arbitration/forum-selection provisions. Run the license/HSIA service agreement history (Guest-Tek, Blueprint RF, hotel-property chains) before committing to a PTAB strategy; the Ninth Circuit disposition above shows a contractual clause can strip your PTAB remedy entirely.

Confidence and limits. I am highly confident that no AIA trial proceeding existed against 7,689,716 as of the ODP ingest and that none appeared in my searches. I did not obtain final written decisions, judge panels, or settlement terms for any Nomadix proceeding — including those on siblings — so any statement of claim-level outcomes for the family would be fabrication, and I have avoided it. Two items rest on a single source each and deserve independent verification: the 2022-02-22 expiration (Google Patents legal-status block, which is expressly an assumption, not a legal conclusion) and the exact filing dates of the Guest-Tek 2017 petitions (reference-list entries in later patents, not the petitions themselves).

I'll start by verifying what assignment records are actually retrievable, then cross-reference.

US 7,689,716 B2 — Ownership & Assignment Analysis

Data-source note (read first). The USPTO Assignment Center could not be queried directly from this environment, and no reel/frame numbers for this patent were retrievable in this session. Everything below is drawn from the Google Patents legal-events record reproduced in the authoritative full text supplied (which mirrors the underlying USPTO assignment records but does not expose reel/frame or correspondent fields), plus publicly indexed litigation and corporate filings. No reel/frame numbers or correspondent names are asserted here — I will not invent them. Fields marked not available are genuinely unavailable, not omitted.

Inventors

• The named inventors are the original founding team of Nomadix, Inc. The application (US 11/427,143) was filed 2006-06-28 as a continuation in the 09/458,xxx family (the two parent applications were filed 1999-12-08, claiming a 1998-12-08 priority date), so all three were long-tenured Nomadix personnel by filing, not recent hires.
• Pattern check — inventor exodus: not determinable. I could not verify any inventor's departure date from Nomadix, and the 2006 filing is a continuation of 1999 work, so the "all inventors gone within 12 months of filing" fire-sale precursor cannot be confirmed or refuted from available sources. I am flagging this as an open item rather than asserting a pattern.
• The record shows the application was filed by Nomadix, Inc. (2006-06-28), i.e. Nomadix was assignee at filing. The individual inventor→Nomadix employment assignment document is not itemized in the legal-events feed.

Original assignee

• Entity on the issued patent (granted 2010-03-30): Nomadix, Inc. (assignee at filing 2006-06-28; original assignee per Google Patents).
• Primary line of business: public-access / hospitality internet gateway hardware and software — the AG 2000 through AG 5900 gateway line, plus HSG, USG/USG II, and NITO 500/1500 products. These are exactly the products Nomadix maps to this patent in its own public Nomadix Product–Patent Listing (which lists 7,689,716 among the patents covering its gateway products). That is direct evidence of a product embodying the claims.
• Status: Operating. Nomadix, Inc. continues to sell gateways and Wi-Fi infrastructure (current product portfolios include the EG 1000/3000/6000 gateway family and AP series access points). It is not dissolved and, on the evidence available, not in bankruptcy. Since 2018 it sits inside a holding structure: per Nomadix's own corporate disclosure in Nomadix, Inc. v. SIA Mikrotikls et al., C.D. Cal. 2:19-cv-10202 (filed 2019-12-02), the interested parties are GWHSPV, LLC (parent of Nomadix, Inc.) and Gate Worldwide Holdings LLC (parent of GWHSPV, LLC).
• Assignee-of-record discrepancy to be aware of: Google Patents' header lists the current assignee as Gate Worldwide Holdings LLC, yet the last recorded event (2019-11-22) is a quitclaim from Gate Worldwide Holdings LLC back to Nomadix, Inc., and Nomadix sued in its own name ten days later. Either the header field is stale or the quitclaim is reflected differently in the assignee-of-record index. This should be resolved against the Assignment Center's "current assignee" view before relying on either name.

Assignment timeline

Source: Google Patents legal events. Reel/frame and correspondent: available only in USPTO Assignment Center, not retrievable here.

• 2015-09-30 (executed date not exposed) / recorded 2015-09-30 — Reel not available

  • Conveyance: Security Agreement ("SECURITY INTEREST (SEE DOCUMENT FOR DETAILS)")
  • Assignor: Nomadix, Inc.
  • Assignee: NTT DOCOMO, INC.
  • Correspondent: not available
  • Context: Securitization — Nomadix pledges its patent estate as collateral to a strategic/creditor investor.

• 2017-08-29 / recorded 2017-08-29 — Reel not available

  • Conveyance: Modification to Patent Security Agreement
  • Assignor: Nomadix, Inc.
  • Assignee: NTT DOCOMO, INC.
  • Correspondent: not available
  • Context: Securitization — amendment/extension of the 2015 collateral package.

• 2018-01-23 / recorded 2018-01-23 — Reel not available

  • Conveyance: Assignment of Patent Security Agreement
  • Assignor: NTT DOCOMO, INC.
  • Assignee: GATE WORLDWIDE HOLDINGS LLC
  • Correspondent: not available
  • Context: Securitization transfer — DOCOMO assigns the secured-party interest (the collateral side), not the patent itself.

• 2018-01-23 / recorded 2018-01-23 — Reel not available

  • Conveyance: Assignment of Assignors' Interest (see document for details)
  • Assignor: Nomadix, Inc.
  • Assignee: GATE WORLDWIDE HOLDINGS LLC
  • Correspondent: not available
  • Context: Internal reorg / creditor-driven recapitalization — this is the operative transfer of the patent rights themselves, executed the same day as the security-interest transfer (see Signal 4).

• 2019-03-20 / recorded 2019-03-20 — Reel not available

  • Conveyance: Security Interest
  • Assignor: Nomadix, Inc.
  • Assignee: Knobbe, Martens, Olson & Bear, LLP
  • Correspondent: not available
  • Context: Securitization of a different kind — a law firm taking a security interest in the patent estate, typically to secure unpaid legal fees. This is a distress indicator, not an NPE transfer.

• 2019-05-28 / recorded 2019-05-28 — Reel not available

  • Conveyance: Release by Secured Party
  • Assignor: Knobbe, Martens, Olson & Bear, LLP
  • Assignee: NOMADIX, INC.
  • Correspondent: not available
  • Context: Lien release — the Knobbe security interest is discharged ~10 weeks after recording.

• 2019-11-22 / recorded 2019-11-22 — Reel not available

  • Conveyance: Quitclaim
  • Assignor: GATE WORLDWIDE HOLDINGS LLC
  • Assignee: NOMADIX, INC.
  • Correspondent: not available
  • Context: Internal reorg reversal — the holding entity quitclaims title back down to the operating company, 10 days before Nomadix's next infringement suit.

If the Assignment Center shows no additional entries beyond these seven, that is itself consistent with the finding below: the chain never leaves the Nomadix corporate family.

Timeline diagram

timeline
    title Ownership of US 7689716
    1998 : Priority date 08 Dec
    1999 : Parent applications filed
    2006 : Continuation filed by Nomadix Inc
    2010 : Patent issued to Nomadix Inc
    2015 : Security interest to NTT DOCOMO
    2017 : DOCOMO security agreement modified
    2018 : Security agreement reassigned to Gate
         : Patent rights assigned to Gate
    2019 : Security interest to Knobbe Martens
         : Knobbe release recorded
         : Quitclaim back to Nomadix Inc
         : Nomadix sues MikroTik

NPE / troll-pattern signals

1. Shell-entity transfer — NOT PRESENT (on available evidence).
The 2018-01-23 assignment moves title to Gate Worldwide Holdings LLC, which carries the "Holdings" naming tell. But the tell is superficial here: (a) it is the recorded parent of Nomadix's parent GWHSPV, LLC, per Nomadix's own Rule 7.1 disclosure in 2:19-cv-10202; (b) the patents were quitclaimed back to Nomadix, Inc. on 2019-11-22; and (c) an operating product line (AG/HSG/USG/NITO gateways) continues to be sold against the patent. A single-purpose licensing shell does not quitclaim the portfolio back to the operating entity. I found no evidence of a registered-agent address, no-products status, or single-member LLC structure for Gate.

2. Known asserter in the chain — NOT PRESENT.
Neither NTT DOCOMO, INC. (a large operating telco), Gate Worldwide Holdings LLC, GWHSPV, LLC, Knobbe, Martens, Olson & Bear, LLP (a law firm taking a lien), nor Nomadix, Inc. matches the public NPE lists named in the brief (Acacia, Marathon, IV, IPNav, Wi-LAN, Mosaid/Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, Document Generation Corp, Spangenberg entities) or any entity I could surface from Unified Patents/RPX high-frequency-plaintiff directories. Note the caveat: Nomadix is itself a serial plaintiff (suit activity in 2007, 2009, 2010, 2014, 2016, 2019) — but it asserts as the practicing manufacturer against competitors, which is a different classification.

3. Repeat correspondent across the chain — UNCLEAR / NOT ASSESSABLE.
The correspondent (attorney of record) field is exactly the field the Assignment Center exposes and that this environment could not retrieve. I will not guess. This is the single highest-value verification step outstanding — if one firm/attorney filed the 2015, 2017, 2018 (×2), 2019-03-20, 2019-05-28 and 2019-11-22 recordings, that would be a strong recurrence signal; if the correspondents are a mix of Nomadix in-house/corporate counsel and DOCOMO's/Gate's deal counsel, the "reorg not shell farm" reading is reinforced. Note for context: Nomadix's litigation counsel of record in the 2019 case (Douglas Muehlhauser) is a litigator, not a recording correspondent, and should not be conflated with the assignment correspondent.

4. Cascading transfers — NOT PRESENT as an NPE pattern (but cluster noted).
There are five recorded events in ~22 months (2018-01-23 ×2 → 2019-03-20 → 2019-05-28 → 2019-11-22), which fits the "<24 months" trigger. However, the pattern's substance is wrong for an NPE cascade: the two 2018-01-23 filings are one collateral transfer and one equity/asset transfer to the same entity on the same day, and the 2019 events are a lien, that lien's release, and a quitclaim back down to the operating company. Assignees do not share a shell-farm address — they are a telco, a holding company, and a law firm — and the chain converges on the original operating assignee rather than fanning out through chained LLCs.

5. Pre-litigation transfer — UNCLEAR.
The 2019-11-22 quitclaim (Gate → Nomadix) is followed 10 days later by Nomadix, Inc. v. SIA Mikrotikls et al., C.D. Cal. 2:19-cv-10202, filed 2019-12-02. Ten days is well inside the 6-month window. But I could not confirm that US 7,689,716 is asserted in that suit, and Google Patents' family litigation links for this patent point to the 2009/2010/2011/2014 cases instead (2:09-cv-08441, 2:10-cv-00381, 2:11-cv-02604, 2:14-cv-00322). The '716 does appear in the claim-construction record of Nomadix v. Hewlett-Packard, C.D. Cal. 2:09-cv-08441 (the "network location of the user host device" construction, '716 Patent col. 20 and col. 37), but that construction post-dates issuance and is not a pre-suit transfer. On the evidence in hand this signal is unresolved, and the 10-day gap is more naturally explained as cleaning up the record so the operating company could sue in its own name.

6. Bankruptcy fire-sale — NOT PRESENT (on available evidence).
No Chapter 7/11 filing by Nomadix, Inc. was located in the sources searched, and there is no assignment to a bankruptcy estate, trustee, or §363 sale purchaser anywhere in the chain. Caveat: the 2019-03-20 security interest to Knobbe Martens (a law firm securing fees) plus the 2015–2018 creditor collateralization are distress indicators consistent with a company under financial strain — but distress is not the same as a bankruptcy sale, and I am not treating it as one.

7. Privateering — NOT PRESENT.
Classic privateering requires an operating company to hand patents to an NPE that asserts against the operating company's competitors. Here the operating company keeps the patents and does its own suing (Nomadix, Inc. as plaintiff in 2:09-cv-08441, 2:10-cv-00381, 2:14-cv-08256, 2:16-cv-08033, 2:19-cv-10202). NTT DOCOMO and Gate took creditor/equity positions, not assertion mandates. No SEC filing or Patent Progress/EFF coverage was located describing a privateering arrangement for this family.

8. Defensive aggregator — NOT PRESENT.
The chain terminates inside the Nomadix / GWHSPV / Gate Worldwide Holdings corporate family. It does not end at RPX, AST, LOT Network, Unified Patents, or OIN. The patent is therefore not neutralized.

Verdict

Operating-company assertion.

Nomadix, Inc. — the original assignee and the entity to which the 2019-11-22 quitclaim returned the patent — ships gateway products that its own public patent listing maps to US 7,689,716 (AG 2000–AG 5900, HSG, USG, NITO families), and it has asserted the family in its own name against actual market competitors (Hewlett-Packard et al., 2:09-cv-08441; Solution Inc. Technologies, 2:10-cv-00381; Hospitality Core Services d/b/a Blueprint RF, 2:14-cv-08256; Guest-Tek, 2:16-cv-08033; SIA Mikrotikls et al., 2:19-cv-10202). The only non-operating links in the chain are NTT DOCOMO's 2015-09-30 security interest and its 2018-01-23 reassignment to Gate Worldwide Holdings LLC, paired with a same-day assignment of Nomadix's own interest — a creditor/holding-company recapitalization that was reversed by quitclaim on 2019-11-22 — plus a 2019-03-20 fee lien to Knobbe Martens released on 2019-05-28. Five recordings in 22 months is clustering, but it converges on the operating company rather than fanning into shell LLCs, and no NPE-list assignee, no asserter correspondent, and no bankruptcy sale appears anywhere in the record.

Two residual caveats that could move the verdict: (i) if the Assignment Center correspondent fields show a single repeat filing agent across all seven recordings for an entity outside the Nomadix corporate family, revisit Signal 3; and (ii) if US 7,689,716 is confirmed as asserted in 2:19-cv-10202, the 10-day quitclaim-to-filing gap becomes a clean record title move — still an operating-company assertion, but worth documenting as Signal 5.

Verify at: https://assignment.uspto.gov/patent/index.html (search patent number 7689716) — or the current front end at https://assignmentcenter.uspto.gov/. Retrieve the reel/frame and correspondent for each of the seven entries above; those two fields are the only material gaps in this analysis.

I'll search for the specific patent and its cited prior art references.

Let me pull the specific citation lists for this patent.

Let me retrieve the front-page references list directly.

I've hit my tool-step ceiling, so this is a synthesis of what I retrieved. Two important framing notes before the substance:

Ground-truth confirmation. The USPTO-derived record for US 7,689,716 B2 is confirmed: Systems and methods for providing dynamic network authorization, authentication and accounting, Application No. 11/427,143, filed 2006-06-28, issued 2010-03-30, inventors Joel E. Short; Florence C. I. Pagan; Josh J. Goldstein, assignee of record at issue Nomadix, Inc. (Agoura Hills, CA). Front-page (56) "References Cited" data, the patent PDF, and the justia/uspto.report mirrors all match this number exactly — no similar-number substitution is being reported.

Material limitation on this deliverable (read this first). I was able to retrieve the front-page cited-reference list only in partial form (the PDF snippet I reached was truncated mid-list), and I still do not have the verbatim claim set. Two searches aimed at completing the front page returned my step ceiling rather than data. So:

• The US-patent list below is complete only through US 5,845,070 (Dec. 1998) and then resumes with a lower-confidence batch. Anything after that point I did not recover and will not invent.
• My §102 mapping is reference → claim family (using the families from the prior section), not claim → element. That is a screening aid, not an anticipation opinion.

1. Where the citation data comes from (and its reliability)

Three distinct prior-art streams exist for this patent, and they are not the same list:

Stream C matters most for "most relevant prior art," because that is where parties did the element-by-element work. I flagged in the prior section that the '716 was not in the Blueprint RF asserted set; the new results refine that: Exhibit C7 to Defendants' Supplemental Joint Invalidity Contentions (July 22, 2011) charts U.S. Pat. No. 7,689,716 in the HP / Solutioninc cases. So the '716 was squarely in the HP-case invalidity fight even though it was not in the Blueprint RF IPR set.

2. Front-page U.S. patent documents (Stream A) — as recovered

2a. The references most relevant on their face

These are the ones I would actually brief for §102, with descriptions I am confident enough to state:

Note on a conflict to flag explicitly: the web-archive capture I reached lists US 7,150,040 B2 (Sun Microsystems, filed 1998-12-01, granted 2006-12-12) as an "Authenticated firewall tunneling framework," and the unifiedpatents page shows US 6,754,831 B2 / US 7,150,040-line art with a 1998-11-30 priority. These are firm-date, on-point "authenticated access to a network through a securing intermediary" references that sit just before the '716's 1998-12-08 date and are not in the front-page (56) list I recovered. I am raising them as potentially material rather than asserting they were cited.

2b. The remainder of the recovered (56) list

Recovered literally from the front page. Some entries show OCR degradation in the source (inventor names garbled); I have not corrected them, per the literal-ID rule.

US 4,026,642 A 5/1977 Tanaka et al.      US 5,251,207 A 10/1993 Abensour et al.
US 4,233,661 A 11/1980 Bolton et al.     US 5,253,161 A 10/1993 Nemirovsky et al.
US 4,509,277 A 4/1985 Bolton             US 5,280,581 A 1/1994 Balrhick et al.
US 4,649,533 A 3/1987 Chorley et al.    US 5,287,269 A 2/1994 Dorrough et al.
US 4,654,793 A 3/1987 Elrod              US 5,287,461 A 2/1994 Moore
US 4,691,346 A 9/1987 Vanacore           US 5,289,371 A 2/1994 Abel et al.
US 4,757,267 A 7/1988 Riskin             US 5,289,576 A 2/1994 Holzard
US 4,806,743 A 2/1989 Thebery           US 5,309,437 A 5/1994 Perlman et al.
US 4,816,654 A 3/1989 Anderl et al.     US 5,319,648 A 6/1994 Bux et al.
US 5,019,907 A 5/1991 Postman           US 5,321,395 A 6/1994 Van Santhriuk
US 5,030,807 A 7/1991 Landt et al.      US 5,325,362 A 6/1994 Aziz
US 5,113,499 A 5/1992 Ankney et al.     US 5,334,821 A 8/1994 Campo et al.
US 5,148,389 A 9/1992 Hughes            US 5,335,268 A 8/1994 Kelly Jr. et al.
US 5,149,945 A 9/1992 Johnson et al.    US 5,337,352 A 8/1994 Kebayashi et al.
US 5,159,592 A 10/1992 Perkins          US 5,351,186 A 9/1994 ...
US 5,221,838 A 6/1993 Gutman et al.
US 5,225,120 A 7/1993 Brown et al.
US 5,235,595 A 8/1993 O'Dowell

— 1996–1998 cluster —
US 5,636,216 A 6/1997 Fox et al.          US 5,781,189 A 7/1998 Holleran et al.
US 5,651,058 A 7/1997 Hackett-Jones      US 5,781,550 A 7/1998 Templin et al.
US 5,664,228 A 9/1997 Mital               US 5,781,552 A 7/1998 Hashimoto
US 5,694,549 A 12/1997 Carlin et al.      US 5,781,909 A 7/1998 Logan et al.
US 5,696,898 A 12/1997 Baker et al.       US 5,787,483 A 7/1998 Jam et al.
US 5,708,654 A 1/1998 Arndt et al.        US 5,790,541 A 8/1998 Patrick et al.
US 5,708,655 A 1/1998 Toth et al.         US 5,790,800 A 8/1998 Gauvin et al.
US 5,708,780 A 1/1998 Levergood et al.    US 5,793,763 A 8/1998 Mayes et al.
US 5,710,883 A 1/1998 Hong et al.         US 5,793,966 A 8/1998 Amstein et al.
US 5,724,355 A 3/1998 Bruno et al.        US 5,793,978 A 8/1998 Fowler
US 5,727,159 A 3/1998 Kikinis             US 5,798,706 A 8/1998 Kraemer et al.
US 5,727,950 A 3/1998 Cook et al.         US 5,802,320 A 9/1998 Baehr et al.
US 5,740,171 A 4/1998 Mazzola et al.      US 5,802,454 A 9/1998 Goshay et al.
US 5,742,604 A 4/1998 Edsall et al.       US 5,802,502 A 9/1998 Gell et al.
US 5,742,668 A 4/1998 Pepe et al.         US 5,805,803 A 9/1998 Birrell et al.
US 5,742,762 A 4/1998 Scholl et al.       US 5,809,415 A 9/1998 Rossmann
US 5,744,789 A 4/1998 Kashi                US 5,812,531 A 9/1998 Cheung et al.
US 5,745,884 A 4/1998 Carnegie et al.     US 5,812,776 A 9/1998 Gifford
US 5,749,075 A 5/1998 Toader et al.       US 5,822,526 A 10/1998 Waskiewicz
US 5,751,971 A 5/1998 Dobbins et al.      US 5,825,772 A 10/1998 Dobbins et al.
US 5,754,774 A 5/1998 Bittinger et al.    US 5,841,769 A 11/1998 Okanoue et al.
US 5,761,309 A 6/1998 Ohashi et al.       US 5,845,070 A 12/1998 ...
US 5,761,683 A 6/1998 Logan et al.
US 5,768,384 A 6/1998 Berson

(list truncated here in the source I reached; entries beyond US 5,845,070 not recovered)

Also listed in the family's related-art tables (found via the family cross-reference, not confirmed as '716 front-page cites): US 5,835,061 (Wayport, 1998-11-03), US 5,856,974 (Internetwork address mapping gateway), US 6,857,009 B1 ("System and method for network access without reconfiguration," 1999-10-21), US 5,703,654, and US 5,742,604.

3. Foreign patent documents (Stream A)

4. Other publications (Stream B and Stream C) — the §102-critical set

These are the references that actually drove the invalidity fight, and they are non-patent literature, so they matter a great deal for §102(a)/(b):

Caution I must state plainly: I could not confirm the full patent number behind the "'118 Patent" as used in the Nomadix v. HP order, nor the Vos article's full citation, from the sources I reached. I am reporting those identifiers literally as the source used them rather than guessing a number.

5. §102 anticipation screen (reference → claim family)

Because the verbatim claims were not retrievable, this maps to the families enumerated in the prior section. Treat as screening, not opinion.

Rule reminder applied: strict §102 requires a single reference disclosing every element arranged as in the claim. Most of the strongest art here (SPINACH, ATCOM, Micros-Fidelio, the '118/Vos pairing) was pleaded as combinations in the C.D. Cal. contentions, which is a §103 posture, not §102. I am not upgrading any of those to a §102 assertion.

6. Corrections / additions to the prior section

1. Claim count is now bounded. The Nomadix v. HP claim-construction order construes claims 25–35 as the "network location" family and cites the '716 specification at 37:5–30. So the patent has at least 35 claims — updating the prior section's "total claim count unknown."
2. The '716 was litigated on validity. New: Exhibit C7 of Defendants' Supplemental Joint Invalidity Contentions (July 22, 2011, Nomadix v. HP, 09-cv-8441 and v. Solutioninc, 2:10-cv-00381) charts the '716. This is consistent with, and sharpens, the prior section's note that the '716 was in the 42-page July 2010 prior-art table.
3. Priority-date discrepancy persists. Google Patents says 1998-12-08; the unifiedpatents record for US-7689716-B2 says 1998-12-07. Unresolved; flagged, not corrected.

7. What I could not do (explicit)

• Complete the (56) list past US 5,845,070 (Dec. 1998) — the PDF text I reached was truncated; my two attempts to complete it returned the step ceiling.
• Retrieve verbatim claims — so §102 element-by-element matching is not possible from what I have. Pull the claim set from USPTO PatentCenter (App. 11/427,143) or the granted PDF before charting.
• Confirm the "'118 Patent**" and "Vos article" full citations** — reported literally as the Nomadix v. HP order used them.
• Run a native USPTO (PatentCenter / PatentsView / ODP) citation export — my retrieval was via Google Patents, uspto.report, and patentimages mirrors of the same underlying documents.

Sources: https://patents.google.com/patent/US7689716/en ; https://patentimages.storage.googleapis.com/61/63/5c/eec43d66147c56/US7689716.pdf (front page (56) list) ; https://uspto.report/patent/grant/7,689,716 ; https://patents.justia.com/patent/7689716 (Other Publications) ; https://www.casemine.com/judgement/us/5914ee91add7b049349605eb (Nomadix, Inc. v. Hewlett-Packard Co., No. CV 09-08441 DDP (VBKx) — SPINACH and '118-Patent/Vos §102(a) analysis) ; https://patentimages.storage.googleapis.com/70/23/f5/f3a443a26d5cd2/[US10341243](/patent/US10341243).pdf (Exhibit C7 = '716) ; https://cases.justia.com/federal/district-courts/california/cacdce/2:2009cv08441/[459068/458](https://assignmentcenter.uspto.gov/search/patent/reelFrameDetail?reelFrame=459068-0458)/0.pdf (claim construction: claims 25–35, "network location") ; https://portal.unifiedpatents.com/patents/patent/US-[6128664](/patent/6128664)-A (priority-date 1998-12-07 record).

I'll gather the prior-art references cited on this patent's page and in the relevant Nomadix family, then build the §103 combinations. Let me run several targeted searches.

Good — I now have the litigation/IPR prior-art landscape. Let me pull the '716's own claim text and its cited references, plus specifics on the key references (Slemmer, Vu, Wesinger, IPORT).

§103 Obviousness Analysis — US 7,689,716

Preliminary notes: what I am relying on, and three contradictions/caveats

Conflict flagged (1) — the operative date. The task header states "Current Date: April 26, 2026," while the system context and the previously generated section state 2026-10-01. I treat the analysis as current as of April 2026 per the task line, and note the discrepancy rather than resolving it.

Conflict flagged (2) — claim text. The previously generated section correctly warned that verbatim claim language was not retrieved. In this pass I located a claim set at Justia for US 2006/0239254 A1 — the pre-grant publication of the same application (11/427,143). Those published claims are not necessarily the claims that issued in the '716. I use them below only as a representative mapping source, clearly labeled.

Conflict flagged (3) — no discrete "Prior Art" panel. The authoritative full text you supplied is the specification, which names no statutory prior-art references of its own besides the incorporated Short/Nomadic-router disclosures and the earlier Nomadix applications. The "Prior Art section" of this page therefore has to be reconstructed from (a) the references the Nomadix family itself lists as cited, and (b) the invalidity record generated against the sibling patents in this family. That is the corpus I use, and I identify each item's provenance.

Governing law. The '716 is a pre-AIA patent (effective filing 2006-06-28, benefit claimed to 1999-12-08 and 1998-12-08). Section 103 analysis proceeds under pre-AIA 35 U.S.C. § 103(a), with the critical date presumptively 1998-12-08 if and only if the claims are supported by that earlier disclosure. Given the '716's 2006 continuation filing, this is itself a live issue: any claim element first supported only by the 2006 disclosure takes a 2006 critical date. I flag this because it changes which art is available, and I do not resolve it here.

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

A person having ordinary skill as of 1998 would hold a B.S. in computer science or electrical engineering (or equivalent experience) plus roughly 2–3 years working with TCP/IP internetworking, and would be familiar as a matter of course with: IP addressing and subnetting; ARP; DHCP; NAT/PAT; application-layer proxies and firewalls; HTTP request/response mechanics; and the then-standard AAA protocol RADIUS (RFC 2058/2059, 1997). This is a modest skill level — the field was already well populated with commercial gateways, firewalls, and proxies by 1998.

2. Scope and content of the prior art (the reconstructed "Prior Art section")

3. The claims under analysis (representative)

From the '716 specification's own summary passages (treated in the prior section as the independent-claim families), and from the published claims of US 2006/0239254 A1, the operative limitations cluster into four groups:

• (A) Transparent gateway + packet-attribute identification. Receive a request at a gateway from a source computer; identify an attribute (MAC address, VLAN ID, circuit ID, user ID, location/port) from a packet; look up a source profile in a source profile database external to the gateway (RADIUS/LDAP); determine access rights.
• (B) Destination/Source-selective AAA. Authorization keyed not just to source identity but to the requested destination (IP address, port, protocol), per packet/session; accounting start/stop logging.
• (C) Redirect to portal/login. Intercept the request; redirect the browser to a portal page, and where rights are absent, to a login page; gateway/AAA presents network-location-specific information; user's computer remains configured for its home network with no added software.
• (D) Translation. Modify outbound packets so source IP corresponds to the gateway, and inbound packets so destination IP corresponds to the host.

(Published claim 1 additionally recites a "redirection determination module," a "user-device location detection module," and a "network packet translation module." I map to those where indicated.)

4. Grounds of obviousness

Ground 1 — Slemmer in view of Vu (primary ground)

Covers: limitation groups (A), (B), (D).

Slemmer supplies the intelligent intermediate routing node that sits between a remote device and a host/network, intercepts the device's packets, performs address translation, and consults a configuration database keyed to the remote device to decide how to route. Vu supplies the access-control function: interception of a connection request, authentication of the source, and allow/deny against a configuration so that some sources reach a destination and others do not.

Motivation. Both references are in the same field and address the same problem — controlling access of a remote/mobile computing device to a network through an intermediary. A POSITA seeking to add per-source access control to Slemmer's routing/translation node would naturally look to the established firewall/access-control art that Vu embodies; the combination is the routine juxtaposition of two known functional blocks (routing/translation + access control) with no change in their respective operating principles, and yields nothing more than the predictable aggregate of each. KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007) (combination of known elements, each performing its known function).

Independent corroboration that this is a serious ground: in IPR2016-00081 (Hospitality Core Services v. Nomadix, on sibling patent '269), the Board's institution table lists a §103(a) challenge over "Slemmer and Vu," claims 1–20 — and the Board instituted trial on exactly that ground (it declined the alternative Slemmer+IPORT+Applegate ground). That is a PTAB determination of a reasonable likelihood that Slemmer+Vu renders obvious a Nomadix gateway-redirection claim set closely related to the '716's subject matter.

Ground 2 — Slemmer + Vu + RADIUS (RFC 2058/2059)

Covers: the limitation that the source profile database is external to the gateway and that the system comprises an AAA server.

Slemmer's device-keyed configuration lookup is described as local to the intermediate node. RFC 2058/2059 disclose precisely the claimed architecture of an external authentication/authorization/accounting server holding user profiles, including accounting start/stop records — the '716's accounting function.

Motivation. Centralizing AAA is a recognized, desirable design choice for exactly the reason the '716 specification itself gives: a single consolidated profile store is easier to administer than many local stores, supports many gateways, and lets the provider keep control of the data. Where a reference teaches a locally maintained configuration database (Slemmer) and the art separately teaches a standardized external AAA server (RADIUS), substituting one for the other is the application of a known technique to improve a similar device in the same way — a textbook KSR rationale. There is no teaching away.

Ground 3 — Wesinger + RFC 1919 (transparency ground)

Covers: the "no configuration software installed on the source computer" / transparent-access limitation, and source-attribute authorization.

Wesinger's firewall intercepts a client's connection request and consults a configuration database (FIG. 7: per-source-network ALLOW/DENY rules, plus time-based rules) to allow or block the connection — i.e., identification of the source from the packet and determination of that source's access rights. Critically, Wesinger states the problem the '716 claims to solve: classical proxies require "custom software … or custom user procedures," and Wesinger's stated object is "maximum user convenience, such that the steps required to establish a connection are transparent to the user." RFC 1919 supplies the concrete mechanism — the transparent proxy — for intercepting and handling traffic without client-side configuration or awareness.

Motivation. Here the references supply their own motivation: Wesinger articulates the very need (transparency, no client software) that RFC 1919's transparent-proxy technique satisfies. Combining them is not hindsight; it is a reference expressly identifying a deficiency in the prior art and the companion reference supplying the known remedy. This is the strongest motivation showing available, because the "transparent access without client reconfiguration" language sits in the preamble/field of the '716 claims.

Ground 4 — Wesinger (or Slemmer) + ATCOM/IPORT

Covers: limitation group (C) — redirect to portal page, and to login page where rights are absent; the proxied handshake; address translation to the redirection server.

The IPORT materials (as established in the Peckham declaration) disclose, in a single enclosure, a gateway, a redirection server, and a portal/login page; address translation diverts the user's packet to the redirection server; the gateway conducts a proxied TCP handshake pretending to be the requested website so that the user's stack accepts the redirect; the browser is redirected to the portal/login page; and after payment the user is added to an "active user" list so subsequent requests pass through. That is limitation group (C) almost element-for-element (see the '269/'246 redirection claims, e.g., '246 claim 6's "redirection server"/"processor" and the '269 IPR record).

Motivation. Wesinger/Slemmer/Vu supply the access-control and routing/translation substrate; IPORT supplies the portal/login presentation and proxied-redirect step. A POSITA adding captive-portal authentication to a transparent gateway would combine them, because the portal is simply the user interface through which the access-control decision is made and payment collected — an obvious convenience/functionality addition with a predictable result.

Ground 5 — Short PCT WO 98/40990 + Wesinger/Vu + RADIUS

Covers: the pervasive "transparent gateway" and translation limitations (group D), including modification of outbound source IP and inbound destination IP.

WO 98/40990 discloses translation of packet content at all layers of the stack, proxy-ARP interception of outbound packets, DHCP interception, and host-independent operation — the '716 specification is substantially built on this disclosure (the '716's FIG. 3–15 and the "Nomadic router" passages reproduce it). Combined with Wesinger/Vu for authorization and RADIUS for the external profile store, this renders the gateway/translation architecture and the transparency limitation obvious.

Caveat I will not paper over: WO 98/40990 names the same inventive entity and published 1998-09-17. Its status as §102 art versus merely the inventors' own incorporated work depends on the priority-date determination and the pre-AIA §102(a)/(b) analysis, and I have not resolved that. Anyone charting this ground should settle the priority question first.

Ground 6 — Location/circuit-ID identification: Micros-Fidelio and US 5,835,061

Covers: the dependent/summary limitations tying identification to a location identifier (hotel room, communications port, circuit ID, VLAN ID), and the "user-device location detection module" of published claim 1.

The '716 specification expressly points to "a local management system, such as a hotel property management system," obtaining user/room data at check-in. Micros-Fidelio is exactly such a hotel PMS, and Stewart US 5,835,061 discloses location-based service access. Combining a location-aware PMS with a gateway that already identifies sources from packet attributes is the straightforward automation of a manual administrative step the '716 itself describes being done "automatically … when the user checks into his or her room."

5. Motivation to combine — consolidated KSR rationales

1. Same field, same problem, overlapping disclosure. Every primary reference addresses controlling a remote/mobile device's access to a network through an intermediary. The field was crowded by 1998 (Slemmer, Vu, Wesinger, Short, IPORT, Stewart), which is itself strong evidence of obviousness.
2. Each element performs its known function; predictable aggregate. Routing/translation (Slemmer, Short) + access control (Vu, Wesinger) + centralized AAA (RADIUS) + captive portal (IPORT). No reference's principle of operation is changed by the combination, and no unpredictable result arises.
3. Explicit statement of the need in the art. Wesinger and RFC 1919 articulate the transparency/no-client-software objective that the '716 asserts as its point of novelty — the classic "reference identifies the deficiency and the companion supplies the fix" showing.
4. Known design incentives. Offloading AAA to a standardized external server (RADIUS) for administrative ease, scalability across many gateways, and provider control of profile data — reasons the '716 specification gives verbatim, which are therefore admissions about what the art recognized as desirable.
5. Automation of a manual step. Using a PMS/location data to authorize is the automation of a known manual hotel practice, a recognized obviousness rationale.

6. What the record says about whether these grounds actually bite

I want to be candid about the litigation outcome rather than assume invalidity:

• In Nomadix v. Hospitality Core Services (Blueprint RF), C.D. Cal. 2:14-cv-08256, the asserted set was '894, '399, '246, '266, '269, '806, '690 — the '716 was not among them, so there is no direct court holding on the '716 that I located.
• The '716 (Exhibit C7) was charted in the defendants' Supplemental Joint Invalidity Contentions in Nomadix v. Hewlett-Packard, No. 09-cv-08441 and Nomadix v. Solutioninc, No. 2:10-cv-00381 (C.D. Cal., dated 2011-07-22, 11 pages) — so a §102/§103 challenge to the '716 was formally mounted, but I did not retrieve the chart's contents or any resulting ruling.
• On the sibling patents, Nomadix survived the §102/§103 summary-judgment motions on some patents (the court declined to invalidate '399 and '690 at the pleading stage on §101), and Blueprint asserted that Nomadix's broad constructions would render the claims invalid — a position the court did not accept as dispositive. I do not have the court's ultimate holding on the §103 motion and will not characterize it.
• The Board did institute on Slemmer+Vu against '269, which is the single most probative item in the recovered record for Ground 1.

Objective indicia to weigh against the prima facie case: commercial success of Nomadix's hospitality gateways; a long-felt need for guest internet access without reconfiguring laptops; copying by competitors; and industry recognition. These are genuine Graham factor-four considerations. But note the tension the record exposes: the IPORT/ATCOM art shows the industry was already solving the transparency/redirect problem in late 1998, which undercuts a "long-felt, unmet need" narrative even as it supports the obviousness case.

7. Confidence, and the factual disputes a challenger must still win

High confidence:

• The '716's claim families correspond to the limitation groups above (supported by the specification's own summary and by the published claims of the same application).
• Slemmer, Vu, Wesinger, RFC 1919, RFC 2058/2059, WO 98/40990, and the ATCOM/IPORT materials are all in the relevant field and were all actually deployed in the invalidity record against this family.
• The Board instituted on Slemmer + Vu against the closely related '269.

Material uncertainties:

1. Verbatim granted claims of the '716 were not verified. The Justia claim set is for US 2006/0239254 A1 (application 11/427,143). I cannot confirm it equals the issued '716 claims. Pull the issued claims from USPTO PatentCenter before relying on any mapping.
2. IPORT's date. The Peckham declaration puts "server only" IPORT versions in service ~Nov. 1998 — just weeks before the 1998-12-08 priority date — and Nomadix disputed characterization. Whether IPORT is §102(b) or §103 art, and whether it discloses all of group (C), is genuinely contested.
3. Critical date. 1998-12-08 (Google Patents) vs. 1998-12-07 (carried from the prior section from a Unified Patents record). Unresolved; and the 2006 continuation filing means some claims may take a later date.
4. Cohen US 6,389,462, Brendel US 6,182,139, Applegate. Listed in the family's contentions, but I could not independently verify their disclosures; do not build a primary ground on them.
5. Ownership context (relevant to the real party in interest if any validity challenge is revived): the recorded quitclaim to Nomadix, Inc. on 2019-11-22 conflicts with the Google Patents "current assignee = Gate Worldwide Holdings LLC" label. Confirm at the USPTO Assignment database.
6. Expiry. The patent's recorded status is Expired – Lifetime, adjusted expiration 2022-02-22. Validity analysis is unaffected, but any challenge would now be defensive/non-infringement-driven rather than an IPR (IPRs require a claim that could be challenged; expired claims cannot be amended, and institutions on expired patents are rare).

Bottom line. On the recovered record, the strongest §103 case is Slemmer + Vu, reinforced by RADIUS (RFC 2058/2059) for the external-profile/AAA limitation, and by Wesinger + RFC 1919 for the transparency and source-attribute-authorization limitations; ATCOM/IPORT carries the portal/login-redirect limitations if its pre-critical-date status holds. The combination rationale is well supported — the references occupy the same field, address the same problem, and Wesinger and RFC 1919 expressly state the transparency objective the '716 claims as its contribution. The principal risks to the case are the unverified claim text and the contested priority date, not the absence of motivation to combine.

Sources relied on: https://patents.google.com/patent/US7689716/en; https://patents.justia.com/patent/20060239254 (published claims of App. 11/427,143); 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 (institution table: Slemmer §102(e); Slemmer+Vu §103; Slemmer+IPORT+Applegate §103); https://www.docketalarm.com/cases/PTAB/IPR2016-00081/.../Exhibit-1042-Declaration_of_William_Peckham.pdf (ATCOM/IPORT redirection, address translation, proxied handshake); https://patentimages.storage.googleapis.com/31/9b/04/e13c584a909ac3/[US9548935](/patent/US9548935).pdf (defendants' claim charts: Slemmer US 6,226,677; Micros-Fidelio; ATCOM/IPORT white paper & manual; Short PCT WO98/40990; Vu 5,623,601; Cohen 6,389,462; Brendel 6,182,139; RFC 1919); https://patentimages.storage.googleapis.com/31/ae/7f/8a7553d0f03cd5/US6804783.pdf and https://patentimages.storage.googleapis.com/pdfs/US20060053486.pdf (Wesinger US 5,898,830 family — transparency object, configuration database, FIG. 7 ALLOW/DENY rules); https://portal.unifiedpatents.com/patents/patent/US-[11949562](/patent/11949562)-B2 (Exhibit C7 — '716 in HP/Solutioninc invalidity contentions); 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 (Blueprint §112/§102/§103 motions and asserted patent set).