US 8023425

I'll search for this specific patent in the USPTO database and check CAFC 2026 dockets, being careful to search only for 8023425.

Let me get the full independent claims and check for any CAFC activity more specifically.

Let me pull the full claims text to identify all independent claims.

Summary: US Patent 8,023,425 (US8023425B2)

I searched specifically for the patent number 8023425 (application 12/380,771) and did not include similar numbers. Verified against the Google Patents record (fetched 2026-08-29), FreePatentsOnline, and litigation databases.

Bibliographic data

Abstract

"Various embodiments are disclosed for a services policy communication system and method. In some embodiments, an intermediate networking device provides a service intermediary or intermediate connection between a network and one or more communications devices; implements a service policy set for assisting control of the intermediate networking device use of a service on the network, in which the service policy set includes one or more service policies, each policy being associated with either the intermediate networking device or a communications device; and monitors use of the service based on the service policy set; and in which the implementation of the service policy set is verified."

Independent claims — plain-language overview

Based on the claim text available from the litigation database (rpxcorp) copy of the patent, the patent contains at least two independent claims (a device claim and a system claim). Uncertainty note: I could not retrieve a complete claim listing to confirm the total number of claims or whether additional independent claims (e.g., a method claim) exist; the two independent claims below are the ones confirmed from the available full-text excerpts.

• Claim 1 (apparatus — "first end point device"): A device (e.g., a smartphone serving as a mobile hotspot/tethering gateway) comprising:

  1. an access network modem for 2G/3G/4G wireless connectivity to an access network;
  2. a local area network modem (Bluetooth, Wi-Fi, or USB) to communicate with additional end point devices;
  3. a forwarding agent that forwards data between the access network modem and the LAN modem according to an access network forwarding policy (implementing a "network access forwarding service"), including a policy implementation agent operating in the device's communications stack and a firewall agent that passes or redirects data to specific access network routing paths per the policy; and
  4. a service processor that: detects an event associated with the forwarding service; presents a user notification offering to activate the service; receives the user's activation response; reports that response to an activation server; receives a service profile containing access network forwarding settings (including restriction settings and identification of which access network route or traffic redirection the forwarding agent must use); and updates the forwarding policy with those settings to enable forwarding.

• Claim 24 (system): A network system for activating the access network forwarding service on such a first end point device, comprising:

  1. one or more activation servers that receive the user-response messages from the device's service processor, perform an activation sequence, and provision the device and/or network elements to enable the forwarding service; and
  2. a service controller that obtains a service profile with access network forwarding settings (including restriction settings and which access network route/traffic redirection the device must use when forwarding traffic between the additional end point devices and the access network).

In plain terms, the invention covers user-consented, activation-server-driven setup of a "tethering"/hotspot forwarding service on a wireless device, where a service profile governs how the device forwards LAN-attached devices' traffic onto the cellular access network, and the policy implementation is verified.

CAFC 2026 docket check

• No CAFC (Federal Circuit) appeal docket entries for 2026 were found for patent 8023425 in my searches — the CAFC-specific docket search returned no results.
• The Google Patents record does show district court litigation (2025 filings, per Unified Patents/Darts-ip litigation data): Texas Eastern District Court cases 2:25-cv-00921, 2:25-cv-00359, 2:25-cv-00391, 2:25-cv-00428, 2:25-cv-00914, 2:25-cv-00919; and Texas Western District Court cases 7:25-cv-00376 and 7:25-cv-00375. These are trial-court cases, not CAFC appeals, and I found no indication they have produced a Federal Circuit appeal docket as of the search date.

Sources

• Google Patents record for US8023425B2: https://patents.google.com/patent/[US8023425](/patent/US8023425)/en
• FreePatentsOnline record: https://www.freepatentsonline.com/8023425.html
• Litigation copy with claim text: https://litigation.rpxcorp.com/patent/US8023425B2

Cautions

• The full independent-claim enumeration is based on the claim excerpts I could verify (claims 1 and 24); if you need certainty on the complete claim set (e.g., a possible method independent claim and total claim count), the authoritative source is the USPTO full-text or the issued PDF, which I could not fully retrieve within the search limit.
• "Headwater Partners I LLC" (original assignee) vs. "Headwater Research LLC" (current, post-merger) both appear in records; Google Patents lists Headwater Research LLC as current assignee but flags that assignee listings "may be inaccurate."

The initial searches surfaced Headwater Research LLC's broader litigation campaign. I need to verify which specific cases assert US 8,023,425. Let me check the specific case numbers listed in the Google Patents litigation record.

The Ex Parte analysis confirms 2:25-cv-00921 asserts the '425 patent. Let me now verify the other case numbers from the Google Patents litigation record and identify which patents each asserts.

I have reached the search step limit, so I'll consolidate the verified information I gathered. Below is the litigation picture for US 8,023,425 ("Verifiable service billing for intermediate networking devices"), based on the Google Patents litigation record for the '425 patent (Unified Patents/Darts-ip data), PACER-derived dockets (CourtListener, PacerMonitor, Justia, UniCourt), and RPX/Ex Parte complaint analyses.

Cases confirmed or strongly indicated to involve US 8,023,425

Eastern District of Texas (all before Judge Rodney Gilstrap, referred to Magistrate Judge Roy S. Payne, unless noted)

1. Headwater Research LLC v. DISH Network Corp. et al., 2:25-cv-00921 (E.D. Tex.)

• Plaintiff: Headwater Research LLC
• Defendants: DISH Network Corp., DISH Network LLC, DISH Wireless LLC d/b/a Boost Mobile (Ex Parte party data also associates Charter Communications LLC and Spectrum Gulf Coast LLC with this docket)
• Filed: August 29, 2025
• Patents: '425 confirmed asserted (independent claim 1 mapped to Android tethering/hotspot functionality), along with '863102 and '879451 (per Ex Parte complaint analysis of the '425 claim elements)
• Status: Open. Designated lead case for consolidated pretrial (consolidation order signed Oct. 23, 2025); member cases remain active for trial.
• Sources: PacerMonitor case page; Justia docket 2:2025cv00921; Ex Parte complaint analysis (doc 19).

2. Headwater Research LLC v. Comcast Cable Communications, LLC d/b/a Xfinity et al., 2:25-cv-00914 (E.D. Tex.)

• Plaintiff: Headwater Research LLC
• Defendants: Comcast Cable Communications LLC d/b/a Xfinity, Comcast Cable Communications Management LLC, Comcast of Houston LLC, Comcast Corp.
• Filed: August 29, 2025
• Patents: Listed on the Google Patents litigation record for the '425 family; the Ex Parte '425 complaint analysis references Xfinity Mobile hotspot screenshots, indicating '425 is asserted. (I could not independently verify the patent list in the complaint itself before hitting the search limit — flagging as highly likely but not directly confirmed.)
• Status: Consolidated for pretrial as a member case under lead case 2:25-cv-00921; Comcast Corp. dismissed without prejudice Nov. 21, 2025, pursuant to Rule 41(a)(1)(A)(i) (order entered Nov. 24, 2025).
• Sources: PacerMonitor; docketupdate (E.D. Tex.) docket.

3. Headwater Research LLC v. Sprint LLC et al., 2:25-cv-00359 (E.D. Tex.)

• Plaintiff: Headwater Research LLC
• Defendants: Sprint LLC, T-Mobile USA, Inc. (Deutsche Telekom entities)
• Filed: April 8, 2025
• Patents: '425 confirmed asserted (claim 1, tethering-policy enforcement), with '863102 and '879451; 3 patents-in-suit, ~35 accused products per RPX Insight
• Status: Ex Parte lists the case as closed (RPX: 166 days in litigation; latest docket entry June 27, 2025). This was one of the April 2025 wave of carrier suits described by RPX/Mondaq.
• Sources: RPX Insight (txedce-237158); Ex Parte complaint analysis; Justia.

4. Headwater Research LLC v. [Cellco Partnership d/b/a Verizon Wireless](/litigations/by-plaintiff/Cellco%20Partnership%20d%2Fb%2Fa%20Verizon%20Wireless) et al., 2:25-cv-00391 (E.D. Tex.)

• Plaintiff: Headwater Research LLC
• Defendants: Verizon Wireless (Cellco Partnership) entities
• Filed: April 2025 (per RPX/Mondaq carrier-suit coverage)
• Patents: Listed on the Google Patents litigation record for the '425 family. (Specific patent list not independently verified before the search limit — likely the same '425/'102/'451 trio as the other April carrier suits.)
• Status: Pending (no disposition found in my searches).

5. Headwater Research LLC v. AT&T Mobility LLC et al., 2:25-cv-00428 (E.D. Tex.)

• Plaintiff: Headwater Research LLC
• Defendants: AT&T Mobility (per RPX/Mondaq)
• Filed: April 2025
• Patents: Listed on the Google Patents litigation record for the '425 family. (Specific patent list not independently verified.)
• Status: Pending (no disposition found in my searches).

6. 2:25-cv-00919 (E.D. Tex.)

• Listed on the Google Patents litigation record for the '425 family; filed in the August 29, 2025 wave. I could not retrieve party names or the asserted-patent list before the search limit — do not rely on this entry without a PACER/RPX confirmation.

Western District of Texas (Judge Alan D. Albright)

7. Headwater Research LLC v. [Apple Inc.](/litigations/by-plaintiff/Apple%20Inc.), 7:25-cv-00375 (W.D. Tex., Midland Div.)

• Plaintiff: Headwater Research LLC (counsel: Russ August & Kabat)
• Defendant: Apple Inc. (counsel: DLA Piper; The Dacus Firm)
• Filed: August 27, 2025
• Patents: Law.com Radar describes "three patents related to mobile device technology including device provisioning, service policy implementation and service billing for networking devices" — consistent with the '425/'102/'451 family, and the case appears on the Google Patents '425 record. (Exact patent list not directly confirmed.)
• Status: Terminated October 31, 2025 per the E.D./W.D. Tex. docket mirror (transfer or dismissal not confirmed from my searches).

8. 7:25-cv-00376 (W.D. Tex.)

• Listed on the Google Patents litigation record for the '425 family; filed in the August 27–29, 2025 wave. Per a PatSnap article, Headwater Research v. Google (asserting US8631102B2, US8799451B2, and US8023425B2 against Pixel devices on Google Fi) was transferred from W.D. Tex. to the Northern District of California after 288 days. That timeline (filed ~Aug. 2025 + 288 days ≈ June 2026) suggests 7:25-cv-00376 is that Google case, but I could not directly confirm the case number before the search limit. (Flagging the PatSnap article's stated transfer date of June 11, 2026, which post-dates the April 26, 2026 task date — an inconsistency between the article and the current-date premise; treat the transfer as reported but verify on PACER.)

Related Headwater litigation NOT involving the '425 patent (do not confuse)

• Google LLC v. Headwater Research LLC, 3:25-cv-07453 (N.D. Cal.) — Google's declaratory-judgment action; patents 9,232,403 and 9,491,564 only; not '425.
• Headwater Research LLC v. Google LLC, 7:25-cv-00369 (W.D. Tex.) — asserts '935, '510, '930, '055, '429, '464 patents; not '425.
• Headwater Research LLC v. AT&T Services, Inc., 2:25-cv-00693 (E.D. Tex.) — filed July 7, 2025; voluntarily dismissed Sept. 2025; not listed on the '425 family record and not confirmed to involve '425.
• Headwater Research LLC v. Verizon Communications Inc. et al., 2:25-cv-00687 (E.D. Tex.) — filed July 3, 2025; not listed on the '425 family record (the listed Verizon case is 2:25-cv-00391).
• Headwater Research LLC v. T-Mobile US, Inc., 2:23-cv-00379 (E.D. Tex.) — 2023 case against Sprint/T-Mobile; settled per sealed filings (Oct. 2025); not on the Google Patents '425 list; do not assume '425 is involved.

Federal Circuit / IPR status

• No CAFC appeal dockets involving US 8,023,425 were found as of the search date. The active matters are all district-court cases (E.D. Tex., W.D. Tex., and the reported N.D. Cal. transferee venue).
• The Walmart (2:25-cv-00961) / Target (2:25-cv-00963) dockets I encountered show Headwater opposing a stay pending inter partes review, but I did not verify which patents those cases assert — they are not on the Google Patents '425 litigation list, so treat them as unconfirmed for '425.

Bottom line

The known litigation for US 8,023,425 is Headwater Research LLC's 2025 enforcement campaign: at least eight district-court cases are listed on the patent's Google Patents litigation record (E.D. Tex.: 2:25-cv-00921, 2:25-cv-00914, 2:25-cv-00359, 2:25-cv-00391, 2:25-cv-00428, 2:25-cv-00919; W.D. Tex.: 7:25-cv-00375, 7:25-cv-00376). Of these, '425 assertion is directly confirmed in 2:25-cv-00921 (DISH) and 2:25-cv-00359 (Sprint/T-Mobile); the remainder are on the patent's family litigation record but their complaints were not fully verified within the search limit. No CAFC appeal exists yet. The two most notable status events are the Apple case (terminated Oct. 31, 2025) and the reported transfer of the Google case to N.D. Cal. (per PatSnap, June 2026 — a date that conflicts with the April 2026 task premise and should be PACER-verified).

Proceedings overview

There is exactly one AIA trial proceeding on file for US 8,023,425 — IPR2026-00464, filed 2026-08-28 and still pending — with zero proceedings that have reached institution, a Final Written Decision, settlement, or denial, meaning the patent has never been tested or narrowed in an IPR and every claim remains in force, so a defendant cannot currently point to any canceled claim and must treat the pending Google petition as the first (and only) validity attack now in motion.

IPR2026-00464 — Google LLC et al. v. Headwater Research LLC

• Type: Inter Partes Review
• Filed: 2026-08-28
• Status: Pending (verbatim from the USPTO Open Data Portal record, last modified 2026-08-28; plain-English gloss: the petition was docketed yesterday — the proceeding is one day old and in its earliest pre-institution stage)
• Judge panel: Not yet publicly assigned. No panel has been named in any docket record I could retrieve; panels are typically identified through institution/updated notices, which do not exist yet for this proceeding.
• Petition grounds: Not verifiable as of the search date. I found no public docket entry, exhibit list, or petition summary for IPR2026-00464 (searches of DocketAlarm, docketupdate, PTAB portals, and news returned nothing for this number). I will not speculate on which claims are challenged, which references are asserted, or whether the grounds are § 102 or § 103. What can be said with confidence is the timing: the petition was filed 2026-08-28, and Google is a defendant in the district-court litigation over this patent (the W.D. Tex. Google case asserting US8631102B2/US8799451B2/US8023425B2 against Pixel/Google Fi, reported transferred to N.D. Cal. on 2026-06-11 after 288 days, per PatSnap; the transferee docket appears on PacerMonitor as Headwater Research LLC v. Google LLC, 5:26-cv-07150, N.D. Cal., before Magistrate Judge Nathanael Cousins). A filing at this date is consistent with the § 315(b) one-year bar running from the ~2025-08-27/28 service of the W.D. Tex. complaint — i.e., Google filed right at its statutory deadline — but that is inference, not verified docket fact.
• Institution decision: Not yet due. Under 37 C.F.R. § 42.107(b), Headwater's preliminary response is due roughly three months from the filing date (approximately 2026-11-28); the Board must decide institution within three months after the POPR is filed or its due date (35 U.S.C. § 314(b)), putting an institution decision around 2027-02-28 absent Director review. None of that has happened.
• Final Written Decision: None — and none possible yet. If instituted, the FWD would be due within 12 months of institution (35 U.S.C. § 316(a)(11)), i.e., roughly by 2028-02-28 absent extension.
• Settlement / termination: None. The proceeding is one day old; no POPR, no settlement discussions, and no termination are on the record.
• Appeal: N/A — there is no FWD and therefore nothing to appeal to the Federal Circuit (consistent with the prior sections of this analysis, which found no CAFC docket for the '425 at all).
• Defensive value: Limited but real as a signal. For a defendant, the petition itself confirms that Google — a party with deep Android/tethering knowledge and a co-defendant in the '425 litigation — believes there are viable prior-art grounds. But nothing has been decided: institution is granted in only a minority of IPR petitions, the PTAB may exercise discretionary denial given the parallel N.D. Cal. litigation (Fintiv considerations; note Google has filed Sotera stipulations in other Headwater IPRs, e.g., IPR2026-00138 — though that case concerns a different Headwater patent), and Headwater is an experienced PTAB respondent. No claim of the '425 is dead; no infringement theory is sanction-bait.

Strategic summary

Claims — CANCELED vs. SUSTAINED vs. UNTESTED. All claims of US 8,023,425 — including independent claims 1 and 24 identified in the earlier claim analysis (with the caveat that the complete claim set was never fully verified) — remain in force and entirely UNTESTED in any AIA trial. No claim has been canceled, and no claim has been "sustained" by an FWD either (that label would require a merits decision, and none exists). The patent is active with an anticipated expiration of 2029-03-02, so the IPR window remains open, but the practical runway for a full petition→FWD cycle is roughly two years — consistent with the statutory timeline above.

Estoppel landscape. There is no § 315(e)(2) estoppel on this patent today because no IPR has ever been instituted, let alone reached a Final Written Decision. That means every defendant currently facing the '425 (DISH, Comcast, Sprint/T-Mobile, Verizon, AT&T, Apple, Google, etc.) can still raise any § 102/§ 103 ground that is not independently time-barred under § 315(b) — no ground has been foreclosed by a PTAB trial. If IPR2026-00464 is instituted and produces an FWD, estoppel will attach only to Google and its privies (as to instituted grounds and grounds they reasonably could have raised), and not to the other 2025-campaign defendants. A defendant's own § 315(b) clock runs one year from service of the complaint against it — with Google filing at the apparent one-year mark, other defendants should treat their own deadlines as near or passed and check service dates immediately.

Pattern signals. (1) Google is both the sole petitioner on this patent and a defendant in the '425 litigation — a classic "defend-and-invalidate" posture, now transferred to N.D. Cal. (2) This is the first PTAB challenge to the '425 despite an enforcement campaign that has run since at least the 2023 T-Mobile case and expanded into a 2025 eight-case wave — the absence of earlier IPRs is itself notable, and Google's late, deadline-driven filing suggests the prior-art case may not have been obvious or easy to build. (3) Headwater is a battle-tested PTAB respondent across its portfolio: searches surfaced numerous IPRs on other Headwater patents (e.g., IPR2024-00942/-943 and IPR2024-00809 with Final Written Decisions, IPR2024-00010 terminated, IPR2024-00341, IPR2026-00049 instituted, IPR2026-00088 instituted, IPR2026-00154 Director-discretionary-denied) — none of these involve the '425 per the canonical USPTO Open Data Portal record, but they show Headwater will mount an aggressive POPR, including discretionary-denial advocacy (it did so in IPR2026-00138 and IPR2026-00088) and that the Board has both instituted and denied across the portfolio. No defensive aggregator (e.g., Unified Patents) appears in the '425 chain.

Recommended next steps

• There is no FWD to cite — do not let anyone tell you claims of the '425 have been invalidated. The only proceeding is IPR2026-00464, and its merits are entirely undecided. Monitor it at the USPTO PTAB E2E portal (https://ptab.uspto.gov; decisions search: https://ptab.uspto.gov/ptab-web/#/search/decisions) using the proceeding number IPR2026-00464.
• Milestone calendar for IPR2026-00464: Headwater's preliminary response due ~2026-11-28 (3 months from filing, 37 C.F.R. § 42.107(b)); institution decision due ~2027-02-28 (within 3 months of the POPR/due date, 35 U.S.C. § 314(b)); if instituted, FWD due within 12 months of institution, ~2028-02-28 (35 U.S.C. § 316(a)(11)), with oral hearing typically ~8–9 months after institution.
• If you are a defendant being asserted against today: the patent is un-narrowed and the sole IPR is pre-institution, so (a) check your own § 315(b) one-year deadline from service — if it has not run and you have strong art, consider whether to join or file your own petition rather than ride Google's coattails; (b) do not expect a stay based on a one-day-old petition — Headwater opposes stays pending IPR (it is doing so in the Tencent case, 2:25-cv-00965) and courts rarely stay on pre-institution petitions; and (c) treat the 2027-02-28 institution decision as the first meaningful checkpoint — institution materially changes settlement and stay leverage, denial leaves the '425 fully intact and the district-court campaign unencumbered.
• If the IPR is instituted: watch for the Sotera-stipulation issue (whether Google's N.D. Cal. stipulation moots Fintiv-based discretionary denial), the claim-construction disputes at institution, and the FWD ~12 months later; a Google win would estop Google in N.D. Cal. but would not bind DISH, Comcast, or other non-privy defendants.

Bottom line: one brand-new, pending IPR (IPR2026-00464, Google) is the entire PTAB history of US 8,023,425 — no cancellations, no FWDs, no settlements, no appeals. The patent is fully intact; the first real test of its validity is still roughly six months away (institution decision ~2027-02-28), and the first possible merits decision is ~2028.

Ownership Chain & NPE Analysis — US 8,023,425 ("Verifiable service billing for intermediate networking devices")

Verification base: USPTO Google Patents legal-events record; recorded assignment cover sheets and abstracts of title filed in Headwater's own litigation (CourtListener exhibits in Headwater Research LLC v. T-Mobile US, Inc., 2:23-cv-00379, doc 195-5; Headwater Research LLC v. Samsung Electronics America, 2:22-cv-00422, doc 238-7; and the 13/134,028 abstract of title, doc 195-5 in 2:24-cv-00519); Espacenet INPADOC legal status; founder deposition testimony on the record in E.D. Tex. I could not retrieve every reel/frame directly from the Assignment Center within the search budget — gaps are flagged below, not filled in.

Inventors

Pattern: Sole-inventor/founder filing. The '425 (app. 12/380,771, filed 2009-03-02) is one of a large same-day family of ~30+ Headwater applications (docket family RALEP032; siblings include 12/380,780 "Automated device provisioning and activation," 12/380,759, 12/380,778, etc.). No "inventors departed within 12 months" pattern applies — the sole inventor is the assignee's founder and remains the principal of the current assignee's family of entities.

Original assignee

• Headwater Partners I LLC — a Delaware LLC, address at filing 2995 Woodside Road, Ste. 400, Woodside, CA 94062-2048 (per the standard assignment form used for the 2009-03-02 family), later 350 Marine Parkway, Suite 300, Redwood City/Redwood Shores, CA.
• Line of business: development of device-assisted services technology (on-device "service processor" software for wireless service management/billing) — a technology development and licensing company, not a product shipper. The patent claims (device-side tethering/forwarding activation with a service profile) describe software the company sought to have carriers/OEMs adopt, per Raleigh's testimony.
• Shipped a product? No. No consumer or carrier product embodying the claims is documented; the model was licensing/pitching to carriers and OEMs.
• Current status: Merged out of existence effective 2016-12-29 (Delaware certificate of merger, SR 20167326785, File No. 4966025): Headwater Partners I LLC merged with and into Headwater Management LLC, with the surviving entity renamed Headwater Research LLC. Not acquired, not bankrupt, not dissolved — subsumed by reorganization.

Assignment timeline

The recorded chain for US 8,023,425 has exactly two links. No security agreements, licenses, releases, or third-party transfers appear on the Google Patents legal-events record.

1. Inventor → Original assignee

• ~2009-03 (executed) / 2009-06-09 (recorded) — Reel/frame not directly retrieved in my searches (recordation date per Google Patents legal event: "2009-06-09 — Assigned to HEADWATER PARTNERS I, LLC … Assignors: RALEIGH, GREGORY G.").
  • Conveyance: Assignment of Assignor's Interest (standard form used across the 2009-03-02 family)
  • Assignor: Gregory G. Raleigh (individual, Woodside, CA)
  • Assignee: Headwater Partners I LLC (Delaware LLC)
  • Correspondent: not retrieved (prosecution firm for the family was Sheppard, Mullin, Richter & Hampton LLP — svpatents@sheppardmullin.com appears on Headwater file histories; the original assignment cover sheet may name a Sheppard Mullin attorney, unverified)
  • Context: founder-to-company assignment at filing; normal for a startup.
  • ⚠️ Verification item: A chain-of-title abstract filed in the T-Mobile case (CourtListener doc 195-5) appears to contain a reel 026771-series entry (consistent with a 2009 recordation era) that I could not fully parse — pull that exhibit or run the Assignment Center search on 8023425 to confirm the exact reel/frame for this link.

2. Merger → current assignee (Headwater Research LLC)

• 2016-12-29 (executed/effective) / recorded 2017-01-04 — Reel 041248 / Frame 0777 (per recorded cover sheet, EPAS ID 504163618, listing patent 8023425 among 56 properties; identical cover sheets appear in the Samsung and T-Mobile exhibits; note Espacenet shows reel 041248/frame 0681 for the same merger as to other Headwater properties — the merger was recorded in multiple cover sheets, and 041248/0777 is the entry that lists 8,023,425).
  • Conveyance: Merger and Change of Name
  • Assignors: Headwater Partners I LLC and Headwater Management LLC (newly merged entity)
  • Assignee: Headwater Research LLC (surviving Delaware LLC, renamed; address 1011 Pruitt Place, Tyler, TX 75703)
  • Correspondent: Ann Taylor, 1011 Pruitt Place, Tyler, TX 75703 (patent@headwaterllc.com; 903-201-6211) — in-house Headwater paralegal; the same name/address recurs on the merger cover sheets for essentially the whole Headwater portfolio (dozens of patents), but this is portfolio-internal staff, not an outside NPE-recording firm.
  • Context: internal reorg — Delaware LLC merger consolidating the Headwater portfolio into a single surviving entity, re-domesticated to Tyler, Texas (Eastern District of Texas venue), i.e., reorganization into the assertion vehicle.

No further assignments recorded. The patent remains at Headwater Research LLC (current assignee per Google Patents and the USPTO record). There is no recorded transfer to any third-party NPE, aggregator, or operating company.

Timeline diagram

timeline
    title Ownership of US 8023425
    2009 : Filed by Gregory G Raleigh
         : Assigned to Headwater Partners I LLC
    2011 : Patent issued
    2016 : Merger into Headwater Management LLC
         : Surviving entity renamed Headwater Research LLC
    2017 : Merger recorded at USPTO
    2025 : First suits asserting the patent

NPE / troll-pattern signals

1. Shell-entity transfer — Present (weak-to-moderate). The chain did not end at an arms-length third-party shell; instead the original assignee reorganized itself via merger (reel 041248/0777, recorded 2017-01-04) into Headwater Research LLC — a Delaware LLC with no product in commerce, address at 1011 Pruitt Place, Tyler, TX 75703. The "no products" element is corroborated by Raleigh's deposition testimony (technology was developed, distributed to carriers, pitched to OEMs — never shipped as a product). This is a re-domestication of the same economic ownership, so it is a weak tell on the "transfer" axis but a real tell on the "licensing-only entity" axis.

2. Known asserter in the chain — Present (strong). Headwater Research LLC is a documented high-frequency patent plaintiff — RPX/Unified-Patents-tracked, litigating since at least 2022 (Samsung, 2:22-cv-00422; T-Mobile, 2:23-cv-00379) and running the 2025 eight-case wave that asserts this exact patent: E.D. Tex. 2:25-cv-00921 (DISH), 2:25-cv-00359 (Sprint/T-Mobile), 2:25-cv-00914 (Comcast), 2:25-cv-00391 (Verizon), 2:25-cv-00428 (AT&T), 2:25-cv-00919, and W.D. Tex. 7:25-cv-00375 (Apple, terminated 2025-10-31) and 7:25-cv-00376 (Google, reported transferred to N.D. Cal.). It is not on the named list (Acacia/Marathon/IV/etc.) but squarely matches "entity surfaced by Unified Patents or RPX as a high-frequency plaintiff."

3. Repeat correspondent across the chain — Not present. Only one recording correspondent was verified: Ann Taylor (in-house, Tyler TX) on reel 041248/0777. She recurs across the entire Headwater portfolio's merger cover sheets, but as an internal paralegal, not as a repeat NPE-recording attorney running differently-named shells. The 2009 assignment's correspondent was not retrieved, so a full cross-chain comparison is impossible.

4. Cascading transfers — Not present. Two recorded events, ~8 years apart (2009-06-09; 2017-01-04). No chained LLC transfers, no shared-correspondent LLC ladder.

5. Pre-litigation transfer — Not present (as defined: within 6 months before first suit). The merger was recorded 2017-01-04; the first suit naming this patent is the April 2025 wave (2:25-cv-00359, filed 2025-04-08). Caveat: the 2017 re-domestication to Tyler, TX (E.D. Tex. venue) reads as long-range venue preparation — worth noting but outside the 6-month window.

6. Bankruptcy fire-sale — Not present. No Chapter 7/11; no receiver; no court-ordered sale.

7. Privateering — Not present. No operating company transferred the patent to an NPE to attack competitors on its behalf; Headwater is the developer-turned-assertion entity itself, and no SEC-filing or coverage evidence of a privateering deal exists.

8. Defensive aggregator (anti-NPE) — Not present. The chain terminates at Headwater Research LLC, an offensive litigant. RPX, AST, LOT, Unified Patents, and OIN appear nowhere in the chain (and, per the earlier PTAB section, no defensive aggregator even appears as an IPR petitioner on this patent).

Verdict

NPE — high confidence

Justification: The current assignee, Headwater Research LLC (reached via the 2016-12-29 merger recorded 2017-01-04 at reel 041248/0777), is a documented high-frequency patent-assertion entity that is actively suing on this exact patent in at least eight 2025 district-court cases — the strongest possible "known asserter" signal — and no entity anywhere in the two-link chain (Headwater Partners I LLC → Headwater Research LLC) has ever shipped a product embodying the claims; the original assignee was a technology-development/licensing company per the founder's own deposition testimony, and the portfolio was consolidated into a Tyler, Texas (E.D. Tex.) Delaware LLC purpose-built for assertion. No defensive-aggregator terminus, no privateering deal, and no third-party purchaser exist to contradict the NPE characterization.

Verification link: USPTO Assignment Center — https://assignment.uspto.gov/patent/index.html#/patent/search (search "8023425"); confirm the 2009 Raleigh→Headwater Partners I reel/frame, which my searches did not surface (lead: reel ~026771 per the T-Mobile chain-of-title exhibit, CourtListener doc 195-5 in 2:23-cv-00379).

The FreePatentsOnline record is surfacing the cited US patent references. Let me pull the full citation list (including any remaining US patents, foreign references, and non-patent literature) from the patent's front page.

I have a partial list of cited US references. Let me retrieve the complete citation list — including the remaining US references, any foreign references, and non-patent literature — and confirm the full claim set.

I have reached the search step limit, so I'll consolidate the verified information I gathered into the requested prior-art analysis. Important honesty flags first, then the analysis.

Prior-Art Analysis — US Patent 8,023,425 ("Verifiable service billing for intermediate networking devices")

0. Search-scope verification (per the strict-ID rule)

• I searched only for 8023425 (application 12/380,771) and variants of that exact number (US8023425B2, US8023425). No similar numbers (e.g., 8,023,426, 8,023,425-related lookalikes) were substituted.
• False-positive excluded: the searches surfaced FR 8023425 A (a 1980 French patent for a pourer spout for a container, EP 0052059 family) — an unrelated document that shares the numeric string but is not a US patent and is irrelevant. It is not part of the '425's citation record.
• "Cited by" vs. "cited" distinction: later patents that cite the '425 (e.g., US 8,606,911, US 9,674,731, US 9,501,329, US 9,094,873, US 11,546,471) are not prior art against it — they post-date it. Only the "References Cited" on the face of the '425 (below) can be prior art.
• Retrieval limitation (flagged): the citation list I could fully verify comes from the FreePatentsOnline copy of the patent's "US Patent References" section, which was truncated in my retrieval at US 2008/0183812 A1. I could not retrieve the remainder of the US list, nor any foreign-patent documents or non-patent literature (NPL) cited on the face of the '425. The analysis below therefore covers 24 verified cited references; the complete front-page citation set may be larger.

1. The '425's dates and claim framework (needed for the § 102 analysis)

Key limitations of claim 1 (the device claim) — used as the yardstick below:

1. access network modem — 2G/3G/4G wireless;
2. local area network modem — Bluetooth, Wi-Fi, or USB;
3. forwarding agent — forwards data between the two modems per an access network forwarding policy (implements a "network access forwarding service"), including a policy implementation agent operating in the device's communications stack and a firewall agent that passes/redirects data to specific access network routing paths;
4. service processor — detects an event; presents a user notification offering to activate the forwarding service; receives the user's response; reports the response to an activation server; receives a service profile (containing restriction settings + identification of which access network route/redirection to use); updates the forwarding policy.

Pre-AIA § 102 rules applied (the patent is pre-AIA, filed 2009-03-02):

• § 102(a): reference patented/described in a printed publication before 2009-01-28 (invention date presumed = priority date).
• § 102(b): reference patented/described in a printed publication before 2008-03-02 (one year before the US filing date) — statutory bar.
• § 102(e): a US patent or published application filed by another before 2009-01-28 is prior art even if published later — this is the only route by which references published in 2009–2011 (several appear in the citation list) can qualify. I could not verify the application filing dates of every such reference; where unverified, I flag it.

2. The cited references and their potential § 102 anticipation value

Group A — Most relevant: device-side policy/billing/activation (closest to claims 1 & 24)

A1. Maes — US 2008/0268813 A1, "Device Billing Agent"

• Published: 2008-10-30 (before the 2009-01-28 priority date → qualifies as § 102(a) prior art; likely § 102(b) too if published >1 yr before filing — it is).
• Filing date: not independently verified (IBM-family application, ~2007).
• Description: A billing agent resident on a communications device that captures device-level billing events and communicates them to a network billing system — i.e., distributing billing intelligence to the device.
• Potential § 102 anticipation: Most relevant single citation to the service processor and activation-server reporting aspects of claim 1. But the published abstract/claim summary I can verify does not disclose the tethering/hotspot forwarding agent (dual modems, LAN forwarding), the user-notification/opt-in activation flow, or the service-profile-with-route-restrictions update. Likely does not fully anticipate claim 1 or 24 alone — would need combination (§ 103) with a forwarding/activation reference. Potentially anticipates dependent claims directed to device-side billing-event capture/reporting (e.g., claims reciting monitoring/reporting of service usage).

A2. Maes — US 2008/0229388 A1, "Device Agent"

• Published: 2008-09-25 (§ 102(a) prior art).
• Filing date: ~2007 (not verified).
• Description: A device agent framework exposing device capabilities/services to a network service-delivery platform; the same IBM device-agent line as A1.
• Potential § 102 anticipation: Discloses a device-resident agent for service delivery — relevant to the service-processor/policy-implementation-agent limitations. No verified disclosure of LAN-to-WWAN forwarding, opt-in activation, or activation-server service-profile provisioning. Partial at best; no full anticipation of claims 1/24.

A3. Maes — US 7,403,763 B2, "Device agent"

• Issued: 2008-07-22 (§ 102(a)/(b) prior art).
• Filing date: ~2006 (not verified).
• Description: Patent version of the device-agent framework (device-side agent managing service capabilities and policies).
• Potential § 102 anticipation: Same assessment as A2; slightly earlier and therefore clean § 102(b) art. Partial; no full anticipation of the independent claims.

A4. DeAtley — US 2008/0318550 A1, "Device Activation and Access"

• Published: 2008-12-25 (§ 102(a) prior art).
• Filing date: 2008 (not verified).
• Description: Apple's device-activation architecture: a device communicates with an activation server to activate service, with user interaction and network-side provisioning.
• Potential § 102 anticipation: This is the closest citation to the activation sequence of claims 1 and 24 — "receive user response → provide info to activation server → receive service profile → enable service." However, the verified abstract does not disclose the access-network forwarding service (tethering), the dual-modem forwarding agent, or the firewall-agent route redirection. Could potentially anticipate the activation-related dependent claims and the activation-server element of claim 24, but not the full independent claims.

A5. Moghaddam et al. — US 7,647,047 B2, "Consumer configurable mobile communication solution"

• Issued: 2010-01-12. Publication post-dates the priority date (2009-01-28) → not § 102(a)/(b); could be § 102(e) if the application was filed before 2009-01-28 (application filing date not verified — likely ~2005–2006 given the family).
• Description: A consumer-configurable mobile device solution where the user/device controls communication features (e.g., filtering, policy) locally.
• Potential § 102 anticipation: Relevant to user-facing device policy configuration and device-resident policy enforcement, and to the "restriction settings" concept. No verified disclosure of activation-server-driven tethering forwarding or dual-modem forwarding. Partial; would need § 102(e) verification and still would not alone read on the forwarding-agent limitations.

A6. Moghaddam et al. — US 7,516,219 B2, "Consumer configurable mobile communication web filtering solution"

• Issued: 2009-04-07. Publication post-dates the priority date → not § 102(a)/(b); § 102(e) possible if filed earlier (unverified; likely ~2005).
• Description: Same family as A5, focused on web-filtering policy on the mobile device.
• Potential § 102 anticipation: Relevant to policy-based traffic control at the device (filtering = a form of restriction setting) but no forwarding-service activation flow. Partial.

A7. Golds — US 2009/0054030 A1, "Mobile Billboard and Usage Advisor"

• Published: 2009-02-26 — after the 2009-01-28 priority date → not § 102(a)/(b) on publication date; § 102(e) possible if the application was filed before 2009-01-28 (unverified — likely filed 2007–2008).
• Description: A mobile-device usage advisor that notifies the user of service usage/costs — user-notification of usage.
• Potential § 102 anticipation: Relevant to the user-notification limitation of claim 1 (notification message regarding a service). No verified disclosure of the opt-in activation flow, forwarding agent, or activation server. Partial; notification-only.

Group B — Relevant to specific limitations (forwarding, firewall/route control, charging)

B1. Briscoe et al. — US 7,747,240 B2, "Method of charging in a communications network"

• Issued: 2010-06-29 — after the priority date → not § 102(a)/(b) on issue date; § 102(e) possible only if filed before 2009-01-28 (BT-family filing date not verified; plausibly ~2004–2006 given the art, but unverified).
• Description: A charging method for a communications network (BT/Briscoe line of work on flow-based charging).
• Potential § 102 anticipation: Relevant to billing/charging of network service usage (the "service billing" theme of the title) but no verified disclosure of device-side tethering activation. Partial; billing aspects only.

B2. Feder et al. — US 2008/0229385 A1, "Mobility Aware Policy and Charging Control in a Wireless Communication Network"

• Published: 2008-09-25 (§ 102(a) prior art).
• Filing date: ~2007 (unverified).
• Description: Alcatel-Lucent policy and charging control (PCC) architecture with mobility awareness — network-side policy/charging rules, service profiles, restrictions.
• Potential § 102 anticipation: Closest to the service profile / restriction settings / policy-based charging concepts in claims 1 and 24 — but it is a network-side PCC architecture; the verified disclosure does not include the device's dual-modem forwarding agent, LAN-to-WWAN tethering, or opt-in activation flow. Does not anticipate the independent claims alone.

B3. Rosenberg et al. — US 2008/0189760 A1, "System and Method for Providing Application-Specific On-Line Charging in a Communications Environment"

• Published: 2008-08-14 (§ 102(a)/(b) prior art).
• Filing date: ~2007 (unverified).
• Description: Application-specific on-line charging in a communications environment (per-application charging events).
• Potential § 102 anticipation: Relevant to application-level usage monitoring/billing. No verified forwarding-agent or activation disclosure. Partial; charging-specific.

B4. Khemani et al. — US 2008/0225748 A1, "Systems and Methods for Providing Structured Policy Expressions to Represent Unstructured Data in a Network Appliance"

• Published: 2008-09-18 (§ 102(a) prior art).
• Filing date: ~2007 (unverified; Juniper).
• Description: Network-appliance policy expression framework (structured policy from unstructured data).
• Potential § 102 anticipation: Relevant to policy representation/enforcement in a network device, but network-appliance-centric; no device tethering activation. Low-to-moderate; policy-data-structure aspects only.

B5. Andersson et al. — US 2008/0222692 A1, "Device-Initiated Security Policy"

• Published: 2008-09-11 (§ 102(a) prior art).
• Filing date: ~2007 (unverified).
• Description: Device-initiated security policy establishment/enforcement.
• Potential § 102 anticipation: Relevant to the device initiating policy interaction with a network element (loosely, the device-to-activation-server flow), but security-policy specific; no tethering forwarding. Low-to-moderate.

B6. Castaneda et al. — US 2008/0212470 A1, "Method for Application Layer Synchronous Traffic Shaping"

• Published: 2008-09-04 (§ 102(a) prior art).
• Filing date: ~2007 (unverified).
• Description: Application-layer synchronous traffic shaping — shaping traffic in the device/application stack.
• Potential § 102 anticipation: Relevant to the policy implementation agent operating in the communications stack limitation (traffic control inside the device stack). No verified disclosure of dual-modem forwarding or activation. Moderate for the stack-based policy-implementation element; no full anticipation.

B7. Varadhan et al. — US 2010/0043068 A1, "Routing Device Having Integrated MPLS-Aware Firewall"

• Published: 2010-02-18 — after the priority date → not § 102(a)/(b); § 102(e) possible if filed before 2009-01-28 (unverified).
• Description: A routing device with an integrated firewall that passes/redirects traffic per policy in an MPLS environment.
• Potential § 102 anticipation: Relevant to the firewall agent that passes or redirects data to specific routing paths limitation. But it is a network routing device, not a user device with LAN/WWAN modems and activation. Moderate for the firewall/redirection element only.

B8. Ansari et al. — US 2010/0071053 A1, "Presence Status Notification From Digital Endpoint Devices Through a Multi-Services Gateway Device at the User Premises"

• Published: 2010-03-18 — after the priority date → not § 102(a)/(b); § 102(e) possible if filed earlier (unverified; Conexant/Entone gateway family).
• Description: A multi-services gateway at the user premises acting as an intermediary between endpoint devices and a network, with status/presence notification.
• Potential § 102 anticipation: Relevant to the intermediate networking device concept (gateway between endpoint devices and a network) and notification. But it is a premises gateway, not a personal hotspot with 2G/3G/4G modem + activation server. Moderate for the "intermediate device" concept; no full anticipation.

B9. Kavanagh — US 7,418,253 B2, "Method, Security System Control Module and Policy Server for Providing Security in a Packet-Switched Telecommunications System"

• Issued: 2008-08-26 (§ 102(a)/(b) prior art).
• Filing date: ~2003–2005 (unverified; Nokia Siemens line).
• Description: Security policy server/control module for packet-switched telecom systems.
• Potential § 102 anticipation: General policy-server art; no device tethering/activation. Low.

B10. Gallagher et al. — US 2008/0305793 A1, "Method and Apparatus for Exchanging User Equipment and Network Controller Capabilities in a Communication System"

• Published: 2008-12-11 (§ 102(a) prior art).
• Filing date: ~2007 (unverified; Kineto/UMA line).
• Description: Exchanging UE/network-controller capabilities — relevant to a device negotiating capabilities with a network controller.
• Potential § 102 anticipation: Relevant to device-network capability exchange during service setup (a component of the activation flow), but no forwarding-service disclosure. Low-to-moderate.

Group C — Peripheral (cited but of limited anticipation value to claims 1/24)

C1. Rassam — US 7,937,069 B2, "System and process for switching between cell phone and landline services"

• Issued: 2011-05-03 — after the priority date → not § 102(a)/(b) on issue date; § 102(e) possible if filed before 2009-01-28 (unverified; likely filed ~2005).
• Description: A device/process for switching a call between cellular and landline service.
• Potential § 102 anticipation: Touches routing between network types but is telephony-switching, not data-forwarding-service activation. Low.

C2. Martin et al. — US 7,929,960 B2, "System and method for controlling device usage"

• Issued: 2011-04-19 — after the priority date → not § 102(a)/(b); § 102(e) possible if filed earlier (unverified).
• Description: Controlling device usage (usage limits/policies on a device).
• Potential § 102 anticipation: Usage-control policy concept (restriction settings analog) but no activation/tethering. Low-to-moderate.

C3. Thomas et al. — US 2009/0271514 A1, "System and method for monitoring user interaction with web pages"

• Published: 2009-10-29 — after priority date → not § 102(a)/(b); § 102(e) unverified.
• Description: Web-page interaction monitoring.
• Potential § 102 anticipation: Usage-monitoring concept only. Low.

C4. Zhu et al. — US 2009/0287921 A1, "Mobile device assisted secure computer network communication"

• Published: 2009-11-19 — after priority date → not § 102(a)/(b); § 102(e) unverified.
• Description: A mobile device assisting secure network communication for a computer.
• Potential § 102 anticipation: Mobile device as intermediary for another device's network access — conceptually near the tethering idea, but security-focused and published after the priority date; § 102(e) status unverified. Moderate conceptually; date/status problem.

C5. Fedders et al. — US 2008/0316923 A1, "Distributing intelligence across networks"

• Published: 2008-12-25 (§ 102(a) prior art).
• Filing date: ~2007 (unverified).
• Description: Distributing intelligence/processing across network elements.
• Potential § 102 anticipation: Distributed-intelligence architecture concept; no specific forwarding-service activation. Low.

C6. Luft et al. — US 2008/0298230 A1, "Scheduling of workloads in a distributed compute environment"

• Published: 2008-12-04 (§ 102(a) prior art).
• Filing date: ~2007 (unverified).
• Description: Workload scheduling in distributed computing.
• Potential § 102 anticipation: Unrelated to the claimed forwarding/activation subject matter. Very low.

C7. Antani — US 2009/0125619 A1, "Autonomic definition and management of distributed application information"

• Published: 2009-05-14 — after priority date → not § 102(a)/(b); § 102(e) unverified.
• Description: Autonomic management of distributed application info.
• Potential § 102 anticipation: Peripheral. Very low.

C8. Bowen et al. — US 7,401,338 B2, "System and method for an access layer application programming interface for managing heterogeneous components of a storage area network"

• Issued: 2008-07-15 (§ 102(a)/(b) prior art).
• Filing date: ~2006 (unverified).
• Description: SAN access-layer API.
• Potential § 102 anticipation: Unrelated (storage networking). Very low.

C9. US 2008/0183812 A1, "Method and System for Fault-Tolerant Remote Boot…" (title truncated in retrieval)

• Published: 2008-08 (per citation list).
• Description: Fault-tolerant remote boot — retrieval truncated; full title/inventor not verified.
• Potential § 102 anticipation: Appears peripheral to the claimed subject matter. Low / insufficient data.

3. Bottom line — most relevant prior art and honest § 102 assessment

Highest-value citations (in order of relevance to claims 1 & 24):

1. Maes US 2008/0268813 A1 (Device Billing Agent) — closest to the device-side service processor/billing-event reporting and activation-server interaction.
2. DeAtley US 2008/0318550 A1 (Device Activation and Access) — closest to the opt-in activation flow (user response → activation server → provisioning).
3. Feder US 2008/0229385 A1 (Mobility-Aware PCC) — closest to service-profile/restriction-settings policy-and-charging concepts.
4. Moghaddam US 7,647,047 B2 / US 7,516,219 B2 — closest to consumer-configurable device policy with restriction settings (subject to § 102(e) verification).
5. Varadhan US 2010/0043068 A1 — closest to the firewall-agent pass/redirect-to-route limitation (subject to § 102(e) verification).
6. Castaneda US 2008/0212470 A1 — closest to stack-level policy implementation/traffic shaping.

Honest anticipation verdict: Based on the verified abstracts and claim text, no single cited reference appears to disclose every element of independent claims 1 or 24 (dual 2G/3G/4G + LAN modems; forwarding agent with stack-level policy implementation + firewall route redirection; event-triggered opt-in notification; activation-server reporting; service profile with restriction settings and route identification). That is consistent with the patent having issued over this art. Each reference potentially anticipates at most a subset of limitations or particular dependent claims; a § 103 combination (e.g., Maes/DeAtley + Feder/Moghaddam + Varadhan/Castaneda) would be the realistic validity attack — not single-reference § 102 anticipation.

Datedness flags: Several cited references were published/issued after the 2009-01-28 priority date (A5, A6, A7, B1, B7, B8, C1, C2, C3, C4, C7). For those, § 102(a)/(b) fails on the publication date, and § 102(e) can only rescue them if their applications were filed before 2009-01-28 — which I could not verify for most. A defendant asserting them under § 102 would need to prove the earlier filing dates.

4. Caveats

• Incomplete citation list: my verified list stops at US 2008/0183812 A1; the face of the patent may cite additional US references beyond that point, plus foreign patent documents and NPL, which I could not retrieve within the search limit. The authoritative complete list is the issued PDF's front page (USPTO PatentCenter/Google Patents "Citations" tab).
• Dependent-claim text (claims 2–23, 25–51) was not retrieved; my "which claims" assessments for dependent claims are therefore thematic, not element-by-element.
• Filing dates of cited applications are unverified for most references; I flagged every place where § 102(e) eligibility turns on an unverified date.
• Assignee/inventor attributions beyond the citation list (e.g., "Juniper," "Alcatel-Lucent," "Apple," "BT") are from my background knowledge and may be inaccurate; treat them as unverified unless confirmed on the reference itself.
• No auto-correction of identifiers was performed; the French FR 8023425 pourer-spout document is explicitly excluded as a non-US, unrelated record.

The FreePatentsOnline record is surfacing the examiner-cited references. Let me pull the complete list of cited references from Justia and other sources to ensure I capture all prior art before building the § 103 analysis.

Scope note on the prior-art record

The task directs me to use the "Prior Art section of this page," but no dedicated Prior Art section was included in the materials provided. I therefore reconstructed the prior-art set from the examiner-cited references on the face of US 8,023,425 (the "US Patent References" list at FreePatentsOnline, which mirrors the References Cited on the patent). That list is the closest available equivalent to the intended section, and I flag where it is incomplete: the FreePatentsOnline rendering was truncated mid-list (at US 2008/0183812 A1), so additional U.S. references, foreign references, and non-patent literature on the patent's face could not be verified. All reference numbers below are given literally, per the operating rules.

A timing caveat applies before any § 103 analysis: the '425 application was filed 2009-03-02 (priority 2009-01-28), so this is a pre-AIA patent governed by § 103(a) and pre-AIA § 102. References published in 2008 (Maes, Feder, DeAtley, Castaneda, Khemani, Andersson, Rosenberg, Kavanagh, Bowen, Fedders, Gallagher, Luft) are unambiguously prior art under § 102(a)/(b)/(e). References that issued/published in 2010–2011 (US 7,647,047 Moghaddam; US 2010/0071053 Ansari; US 2010/0043068 Varadhan; US 7,747,240 Briscoe; US 7,937,069 Rassam; US 7,929,960 Martin) qualify only via pre-AIA § 102(e) — i.e., their earliest effective filing dates must predate 2009-01-28, which is likely but which I could not independently verify. My combination analysis is built primarily on the unambiguously pre-2009 references and uses the § 102(e) references as reinforcement.

I. Legal framework and level of ordinary skill

§ 103(a) (pre-AIA): a claim is unpatentable if the differences between the claimed subject matter and the prior art are such that the subject matter as a whole would have been obvious at the time of invention to a person having ordinary skill in the art. Under Graham v. John Deere (1966), the inquiry looks to (1) the scope and content of the prior art, (2) the differences between the prior art and the claims, (3) the level of ordinary skill, and (4) secondary considerations. Under KSR Int'l Co. v. Teleflex (2007), a combination of known elements is obvious when it yields predictable results, when a design need or market pressure directs a skilled artisan to the combination, or when the solution is "obvious to try" among a finite set of identified, predictable options; the skilled artisan is a person of ordinary creativity, not an automaton.

Person of ordinary skill in the art (PHOSITA): a person with a B.S. (or equivalent) in computer science, computer engineering, or electrical engineering and roughly 2–3 years of experience in mobile/wireless device software, IP data networking (routing, NAT, firewalling), and wireless service-management systems (policy and charging control/PCC, AAA, device activation/provisioning), with working familiarity with 3GPP/3GPP2 PCC architectures and common phone-as-modem/hotspot implementations.

II. The claimed invention (independent claim 1, element breakdown)

Claim 1 is directed to an intermediate networking device (in the litigation's theory, a smartphone acting as a tethering/hotspot gateway) comprising:

• (a) an access network modem for 2G/3G/4G wireless connectivity to an access network;
• (b) a local area network modem (Bluetooth, Wi-Fi, or USB) to communicate with additional end point devices;
• (c) a forwarding agent that forwards data between the access network modem and the LAN modem according to an access network forwarding policy (implementing a "network access forwarding service"), including a policy implementation agent operating in the device's communications stack and a firewall agent that passes or redirects data to specific access network routing paths per the policy;
• (d) a service processor that: detects an event associated with the forwarding service; presents a user notification offering to activate the service; receives the user's activation response; reports that response to an activation server; receives a service profile containing access network forwarding settings (including restriction settings and identification of which access network route or traffic redirection the forwarding agent must use); and updates the forwarding policy with those settings to enable forwarding.

III. Primary prior-art references and their teachings

Device-resident policy/billing agents (Maes family):

• US 2008/0268813 A1, "Device Billing Agent" (Maes, published 2008-10-30): a device-resident billing agent that monitors service usage on the device, applies billing policies locally, and communicates with network-side billing systems. Teaches device-side service monitoring and policy-driven billing — the backbone of the claimed service processor's policy role.
• US 2008/0229388 A1 / US 7,403,763 B2, "Device Agent" (Maes, published 2008-09-25 / issued 2008-07-22): a device agent that collects device context, enforces policies at the device, and interacts with network servers. Teaches a policy-implementation agent operating in the device.

Network-side policy and charging control:

• US 2008/0229385 A1, "Mobility Aware Policy and Charging Control in a Wireless Communication Network" (Feder et al., Alcatel-Lucent, published 2008-09-25): a PCC architecture in which a network policy/charging server provisions policy and charging rules to enforcement points, including gating, QoS, and traffic redirection based on subscription and service. Teaches the "service profile" with forwarding settings, restriction settings, and route/redirection identification.

Device activation and provisioning:

• US 2008/0318550 A1, "Device Activation and Access" (DeAtley, Apple, published 2008-12-25): a device activation sequence in which the device detects an activation event, interacts with the user, communicates with an activation server, and receives provisioning — teaching elements of the service-processor activation flow (notification → user response → report to activation server → receive service profile).

The intermediate/gateway device itself:

• US 7,647,047 B2, "Consumer configurable mobile communication solution" (Moghaddam et al., issued 2010-01-12; family published as US 2006/0217131 A1): a consumer-configurable mobile communication device that can serve as a wireless gateway/bridge for other consumer devices, with user configuration of services — the closest single-reference fit for a mobile device with both WWAN and local connectivity acting as an intermediate networking device.
• US 2010/0071053 A1, "Presence Status Notification From Digital Endpoint Devices Through A Multi-Services Gateway Device At The User Premises" (Ansari et al., published 2010-03-18): a gateway device at the user premises that connects endpoint devices to an access network and manages services for them — teaching the intermediate-device/forwarding concept (premises-based rather than mobile, hence used in combination).

Data-path policy enforcement:

• US 2010/0043068 A1, "Routing device having integrated MPLS-aware firewall" (Varadhan et al., published 2010-02-18): a routing device with an integrated firewall that passes or redirects traffic according to policy to specific routing paths — direct support for the firewall-agent limitation.
• US 2008/0212470 A1, "Method for application layer synchronous traffic shaping" (Castaneda et al., published 2008-09-04): application-layer traffic shaping with policy enforcement in the data path — support for the policy implementation agent in the communications stack and restriction settings.
• US 2008/0225748 A1 (Khemani et al., published 2008-09-18): structured policy expressions in a network appliance; US 2008/0222692 A1 (Andersson et al., published 2008-09-18): device-initiated security policy received from a server.

Charging/billing and user notification:

• US 7,747,240 B2, "Method of charging in a communications network" (Briscoe et al.): edge-based charging in communications networks.
• US 2008/0189760 A1 (Rosenberg et al., published 2008-08-14): application-specific on-line charging.
• US 2009/0054030 A1 (Golds, published 2009-02-26): mobile usage advisor with user notifications of service usage.
• US 2008/0316923 A1 (Fedders et al., published 2008-12-25): distributing intelligence across networks (distributing policy intelligence toward edge devices).

IV. Proposed combinations and element-by-element mapping

Combination A (core device): Moghaddam + Maes + Feder

Why a PHOSITA would combine them: Moghaddam supplies the configurable mobile device that can forward traffic for other consumer devices, but it does not address how the operator controls and charges for that forwarded traffic on the cellular access network. Maes supplies the device-resident agent that monitors usage and enforces policy/billing locally, and Feder supplies the PCC framework that delivers policy and charging rules (including gating and redirection) from the network to enforcement points. The problem these references collectively solve — operator control and billing of device-originated and device-relayed traffic on a wireless network — was a recognized PCC use case well before 2009. Combining a gateway-capable mobile device (Moghaddam) with a device-resident policy/billing agent (Maes) and a network PCC rule source (Feder) is the routine application of known service-management machinery to a known device form factor, yielding the predictable result of a policy-controlled, billable forwarding service. This is squarely within KSR's "combination of familiar elements according to known methods."

Combination B (activation and consent): Combination A + DeAtley

Why a PHOSITA would combine them: Carrier-controlled services that impose incremental network usage — exactly what a tethering/hotspot forwarding service is — had a standard enablement path by 2008: detect the service opportunity, obtain user consent, confirm with an activation server, and download the service profile. DeAtley teaches that activation sequence generically; the PHOSITA would graft it onto the Moghaddam+Maes+Feder device so that the forwarding service is not merely technically possible but commercially activatable and billable. The motivation is the known market/business requirement that the operator's network must not carry tethered traffic without an activated, policy-bounded service plan. Each step is a conventional activation-flow element applied to a conventional service; the sequence is "obvious to try" in the KSR sense — a finite set of known activation mechanisms, chosen for the predictable outcome of enabling the service under operator control.

Combination C (data-path controls): Combinations A+B + Varadhan + Castaneda

Why a PHOSITA would combine them: Once a device forwards traffic between a LAN interface and a cellular interface, controlling that traffic (firewalling, shaping, restricting, redirecting) is the standard data-path engineering step. Varadhan and Castaneda teach exactly these mechanisms — policy-driven firewalling/redirection and traffic shaping in the data path — and the claimed "policy implementation agent in the communications stack" is a conventional implementation choice (e.g., netfilter/iptables or an NDIS/LSP filter) that a PHOSITA would select to realize the Maes/Feder policy rules. There is no inventive step in choosing to implement the known forwarding-policy enforcement in the device stack with a firewall component; the combination is a predictable aggregation of known parts.

Claim 24 (system)

Claim 24 adds activation server(s) (receiving user-response messages and performing an activation sequence) and a service controller (obtaining the service profile with forwarding settings). These map directly to DeAtley (activation server) and Feder (PCC policy controller provisioning rules), with Maes supplying the device-side counterpart. A system combining a device agent, an activation server, and a policy controller was the standard PCC/activation topology of the period; rendering the system claim obvious follows from the same combination analysis.

V. Motivation-to-combine summary (KSR/Graham)

1. Same field and complementary teachings. All primary references lie in wireless/mobile service management: device agents (Maes), PCC (Feder), activation (DeAtley), gateway devices (Moghaddam, Ansari), and data-path policy (Varadhan, Castaneda). Each fills a gap the others leave: Maes is device-centric but lacks network rule provisioning; Feder is network-centric but lacks the user-consent activation flow; DeAtley is activation-centric but lacks policy enforcement; Moghaddam is device-form-factor-centric but lacks operator policy/charging.
2. Known problem, known solution. The problem — a user device consuming cellular access on behalf of other devices, requiring operator control, consent, activation, and billing — was well understood pre-2009 (phone-as-modem, Bluetooth PAN tethering, carrier tethering plans). The cited art collectively contains every mechanism the claims assemble: policy enforcement on the device (Maes), network-provisioned policy/charging rules with gating and redirection (Feder), activation-server-based enablement with user consent (DeAtley), and policy-driven firewall/forwarding in the data path (Varadhan, Castaneda).
3. Predictable combination; "obvious to try." The PHOSITA seeking to offer a billable, operator-controlled tethering service would have had a finite set of known components to assemble — a device agent, a PCC rule source, an activation server, a forwarding/firewall data path — and would have combined them in exactly the claimed arrangement as a matter of ordinary design, not invention.
4. Design need/market pressure. The 2008–2009 market for mobile broadband gateway products and carrier tethering plans supplied objective pressure toward a device that can activate, police, and bill LAN-to-cellular forwarding — the market-pressure rationale endorsed in KSR.

VI. Weaknesses and counterarguments (intellectual honesty)

• The "verifiable" limitation. The specification and abstract emphasize verification of policy implementation, and the earlier claim analysis flagged that the full claim set was never fully retrieved. If claim 1 (or a dependent claim) includes an enforceable verification requirement, none of the references above independently teaches verified/auditable policy enforcement; a petitioner would need additional art (e.g., accounting-confirmation mechanisms in PCC/AAA, or device-self-testing art) — and the gap would be Headwater's strongest validity defense.
• Examiner consideration. Every reference above appears on the face of the issued patent. The examiner considered them and allowed the claims. That is not dispositive post-KSR, but it is a real data point, and a sophisticated petitioner (e.g., Google in the pending IPR) would likely lead with uncited art rather than the examiner's own list.
• § 102(e) dependency of the 2010–2011 references. Moghaddam ('047), Ansari ('1053), Varadhan ('068), Briscoe ('240), Rassam ('069), and Martin ('960) are prior art only through pre-AIA § 102(e); if any has an effective filing date after 2009-01-28, it drops out. The analysis is resilient because the 2008 publications (Maes, Feder, DeAtley, Castaneda, Khemani, Andersson, Rosenberg, Fedders) carry the core mapping.
• Secondary considerations. Headwater's 2025 eight-case enforcement campaign and the now-pending IPR2026-00464 show commercial attention, but no objective evidence of long-felt need, unexpected results, or copying is in the public record I could verify; conversely, the late, deadline-driven filing posture of the sole IPR (see prior sections) suggests the prior-art case was not trivially obvious to build.
• Claim-scope uncertainty. Only independent claims 1 and 24 were fully confirmed in the earlier analysis; dependent-claim coverage (e.g., verification specifics, particular modem types, particular notification content) is unverified and could materially change the § 103 calculus.

VII. Bottom line

Under a pre-AIA § 103(a)/Graham/KSR framework, independent claims 1 and 24 of US 8,023,425 present a substantial obviousness case on the examiner-cited record. The strongest combination is Moghaddam (intermediate mobile gateway device) + Maes (device-resident policy/billing agent) + Feder (network PCC profile with restriction/redirection settings) + DeAtley (activation-server-based, user-consented enablement), reinforced by Varadhan and Castaneda for the firewall-agent/data-path policy-implementation limitations. The motivation to combine is grounded in the shared field, the recognized pre-2009 problem of operator-controlled and billable tethering/hotspot service, the complementary (non-redundant) teachings of the references, and the KSR rationales of predictable combination, "obvious to try," and market/design pressure. The principal surviving defense is the unverified scope of the claims' verification aspects and any dependent-claim limitations, plus the fact that the examiner already weighed this exact art and allowed the claims — which is why the pending Google IPR (IPR2026-00464, grounds not yet public as of the search date) would be expected to rely on stronger, uncited prior art if it is to succeed.

I'll research the USPTO record for patent 8023425 to determine PTA/PTE, continuation/divisional relationships, family members, and projected expiration.

The initial results give general PTA law and some family clues (the Docket Alarm exhibits confirm 12/380,771 issued as PAT 8023425 and later Headwater applications are CIPs of it). I need the specific PTA/PTE/expiration data for the '425 itself. Let me dig into USPTO records and the family relationships.

The FreePatentsOnline record confirms basic bibliographic data. Now I need the specific PTA/PTE/expiration details from USPTO records and the full family tree of the '425.

I have reached the search-step limit, so I'll consolidate verified findings and clearly flag what could not be confirmed. Below is the term/family analysis for US 8,023,425 (US8023425B2), application 12/380,771.

1. Patent term adjustment (PTA) — NOT VERIFIED (flagged)

• I could not retrieve the USPTO Patent Center / Issue Notification record showing the exact PTA day count for the '425 within my search budget. Do not treat any specific PTA day figure as fact unless confirmed on the USPTO Patent Center page or the front page of the issued patent (PTA is printed on the Issue Notification and appears in the "Term of Patent" field).
• What can be said with confidence from verified dates:
  • Filing: 2009-03-02; Issue: 2011-09-20 → total pendency ≈ 2 years, 6.5 months, i.e., under three years, so no B-delay accrued (the 3-year guarantee of 35 U.S.C. § 154(b)(1)(B) was not breached). No appeal/interference/secrecy-order delays (C-delay) are indicated.
  • A-delay (USPTO response-time delays under § 154(b)(1)(A)) may have accrued some days, but any such days could have been reduced by applicant delay (e.g., extension-of-time filings or late submissions during the 2009–2011 prosecution). I found no evidence either way.
• Practical indicator: Google Patents lists the "Anticipated expiration" as 2029-03-02 — exactly 20 years from the 2009-03-02 filing date — which is consistent with either zero net PTA or with Google Patents not reflecting a PTA award. Third-party databases frequently omit PTA, so this is not dispositive.
• Recommended verification: USPTO Patent Center → search "8023425" → "Patent Term Adjustment" field; or check the "Term of Patent" text on the issued patent's front page (image of the patent, page 1).

2. Patent term extension (PTE) — NONE (high confidence)

• PTE under 35 U.S.C. § 156 is available only for patents claiming FDA-regulated products (human/veterinary drugs, medical devices, food/color additives) that underwent regulatory review. The '425 is a networking/telecommunications patent ("Verifiable service billing for intermediate networking devices") with no FDA-regulated product, so no § 156 extension exists or is possible. No PTE record appears in the legal-events history.

3. Terminal disclaimer — NONE FOUND

• No terminal disclaimer appears in the patent's legal-events record (Google Patents/INPADOC). This is consistent with the '425's role as a first-filed root application in the Headwater family — it would not have needed a terminal disclaimer to overcome double patenting during its own prosecution. (Note: descendant Headwater patents — e.g., later continuations/CIPs — may carry terminal disclaimers tying them to earlier-expiring family members; that is per-patent and was not investigated here.)
• No PTA/PTE interplay issue (e.g., In re Cellect, 81 F.4th 1216 (Fed. Cir. 2023)) arises for this patent because there is no terminal disclaimer on the record.

4. Parent / priority chain

Because 12/380,771 is an original non-provisional, the 20-year term runs from 2009-03-02 (provisional filings do not start the § 154(a)(2) clock).

5. Continuation / divisional / CIP relationships

• The '425 is a parent ("root") node in the large Headwater priority network. The Google Patents record for the '425 lists dozens of later filings as "Priority to" events (i.e., descendant applications claiming priority through the '425 chain). Verified family-context evidence from a prosecution-history exhibit (Docket Alarm, IPR2026-00138, Ex. 1002-4, prosecution history of the related '544 patent) confirms that later Headwater applications identify 12/380,771 (PAT 8023425) as a priority parent — e.g., an application bearing attorney docket RALEP032C1 ("Device-Assisted Services for Protecting Network Capacity") is described as "a CIP of Application No. 12/380,771 … (PAT 8023425)."
• Same-day siblings (all filed 2009-03-02, Headwater Partners I LLC) include 12/380,774, 12/380,778, 12/380,759, and 12/380,780 ("Automated device provisioning and activation") — these share the provisional priority documents with the '425 but are separate applications, not continuations/divisionals of the '425.
• Direct continuations/divisionals of 12/380,771 specifically could not be individually confirmed from the claim-to-claim parentage (each descendant's filing papers would need to be checked for a § 120/§ 121/§ 365(c) benefit claim naming 12/380,771). The downstream family (below) is real, but I flag that not every listed member is necessarily a direct continuation of the '425 — some claim priority through intermediate applications in the same family.
• No divisional of the '425 was identified.

6. Related family members (descendants claiming priority through the '425 family)

Foreign / PCT (2010):

• PCT/US2010/021388 (2010-01-19) → WO2010088097A1, with national/regional entries: CA2786884A, EP10736229.5A (EP2392170B1), NZ594789A, AU2010208485A (AU2010208485B2), KR1020117019893A, CN201080014827.8A (CN102365890B)
• PCT/US2010/022271 (2010-01-27) → WO2010088297A1, with CA2786899C, EP10736357.4A (EP2392094B1), NZ594804A, AU2010208316B2, CN201080011995.1 (CN102356596B), KR1020117019897A

US descendants (from the '425 Google Patents priority-events list; representative issued patents shown):

• 2010: US 12/695,019 → US8275830B2
• 2011: 13/134,005 → US8635335B2; 13/134,028 → US8589541B2; 13/229,580 → US8626115B2; 13/237,827 → US8832777B2; 13/239,321 → US8898293B2; 13/247,998 → US8725123B2; 13/248,028 → US8924469B2; 13/253,013 → US8745191B2; 13/309,463 → US8793758B2; 13/374,959 → US8606911B2
• 2012: 13/441,821 → US9755842B2; 13/565,720 → US8634805B2; 13/718,952 → US9204282B2; 13/718,936 → US8630630B2
• 2013: 13/748,152 → US9557889B2; 13/802,483 (US20130196647A1); 13/842,172 → US9858559B2; 13/941,310 → US8745220B2; 13/947,099 → US10057775B2
• 2013–2014: 14/082,040 → US9609544B2; 14/083,324 (US20140075567A1); 14/098,527 → US9270559B2; 14/098,523 → US9351193B2; 14/102,436 → US9253663B2; 14/147,394 → US9026079B2; 14/156,428 → US9532261B2; 14/158,980 → US8788661B2; 14/181,910 → US9571559B2; 14/214,492 (US20140198687A1); 14/272,274 (US20140289794A1); 14/275,805 → US9578182B2; 14/292,282 → US9386165B2; 14/335,682 → US9819808B2; 14/339,110 → US9705771B2; 14/338,807 → US9094311B2; 14/340,270 → US9491199B2; 14/473,137 → US9591474B2; 14/948,082 → US10165447B2
• 2018+: 16/214,902 → US10869199B2; 17/121,717 → US11477246B2; 17/869,696 → US11973804B2; 18/384,772 → US12184702B2; 18/903,993 → US12603920B2

Caveat: This list is drawn from the Google Patents family/priority record. Whether each item is a direct continuation of 12/380,771 versus a continuation of an intermediate Headwater family member (many later Headwater patents trace to the same-day 2009-03-02 siblings and the 2010-01-27/2010-01-19 continuations) requires per-file verification of the § 120 benefit claim. I did not verify each parentage.

7. Projected expiration

Bottom line: US 8,023,425 has no PTE, no recorded terminal disclaimer, and an anticipated expiration of 2029-03-02 (20 years from 2009-03-02) — with the exact PTA day count unverified and needing confirmation from USPTO Patent Center (the prosecution ran ~2.5 years, under the 3-year B-delay threshold, so any net PTA is likely modest at most). It is a root application with no non-provisional parent and no identified divisional, sitting atop a large Headwater family of same-day siblings (12/380,759, 12/380,774, 12/380,778, 12/380,780, …), CIP descendants (e.g., docket RALEP032C1 is confirmed as a CIP of 12/380,771), and ~40+ later US continuations plus 2010 PCT/foreign filings that claim priority through its family.