US 8799451

I'll search for the specific patent number 8799451 and related litigation/docket information.

Let me search for the full claims of US8799451 and any CAFC 2026 docket information.

Let me do one more targeted search on the CAFC docket for this specific patent number and confirm the independent claims.

Search Results for US Patent 8799451

Confirmation of the target patent

I searched for the specific patent number 8799451 (US8799451B2; application US12/380,773) and its CAFC/litigation dockets. I did not substitute or auto-correct any identifiers. The searches confirm the following, consistent with the authoritative patent text provided:

Patent summary

Abstract (as published for the family/continuation): Various embodiments are disclosed for a services policy communication system and method. In some embodiments, an intermediate networking device acts as 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 set on the network, the service policy set including one or more service policies associated with the intermediate networking device or one or more communications devices connected to the intermediate networking device, the service set being one or more network services used by the intermediate networking device or one or more communications devices; and monitors use of the service set based on the first service policy set, in which the implementation of the service policy set is verified.

Independent claims — plain-language overview

Based on the issued patent text and litigation-database reproductions of the claims (RPX/Unified Patents), the patent's independent claims are claim 1 (apparatus), claim 14 (computer program product), and claim 15 (method), with the remaining claims dependent. Note: the claim text in the user-provided full specification is truncated before the claims section, so I flag minor wording uncertainty below.

Claim 1 – Apparatus (first end-user device as an intermediate networking device)
A first end-user device that can act as an intermediate networking device. It has one or more modems enabling it to (a) communicate with a network system over a first network, where the first network is a wireless access network, and (b) communicate with one or more other end-user devices over a second network. A processor is configured to:

• provide a forwarding service that forwards "first traffic" between the other end-user devices and the network system (i.e., tethering/hotspot-style bridging);
• implement a first service policy assisting in control of that forwarded first traffic;
• implement a second service policy assisting in control of "second traffic" — the first device's own access to services over the first (wireless access) network — where the second policy differs from the first policy (i.e., the device's own data usage is governed differently from the forwarded traffic);
• monitor or identify successful use or attempted use of the forwarding service (enabling verification/accounting of tethering).
  Memory coupled to the processor stores the instructions.

Claim 14 – Computer program product
A non-transitory computer-readable storage medium with instructions that cause one or more processors of a first end-user device to perform the same functional combination: provide a forwarding service to other end-user devices coupled to the first device over a first network (forwarding traffic between those devices and a network system coupled over a second network, where the second network is the wireless access network); implement first and second differing service policies respectively for the forwarded traffic and the device's own access to services over the wireless access network; and monitor/identify successful or attempted use of the forwarding service.

Claim 15 – Method
A method performed by a first end-user device capable of operating as an intermediate networking device: providing the forwarding service for first traffic between other end-user devices and the network system; implementing a first service policy for controlling that forwarded first traffic; implementing a second, different service policy for controlling second traffic associated with the first device's own access to services over the wireless access network; and monitoring or identifying successful use or attempted use of the forwarding service.

Plain-language essence of all three: the claimed invention covers a user device (e.g., a smartphone or mobile hotspot) that both (1) tethers/forwards traffic for other devices onto a wireless network and (2) manages its own service usage under a separate, distinct service policy, while monitoring/identifying whether the forwarding service is actually being used (or attempted) — enabling verifiable service-policy implementation and billing for intermediate networking devices.

CAFC 2026 docket / litigation search results

• No CAFC 2026 appeal specifically identified for US8799451B2 itself in my searches. The CAFC docket search returned no appeal docket that names 8,799,451 as an asserted patent.
• Active district-court litigation involving 8799451B2 exists (per Google Patents' litigation links and PatSnap/Unified Patents):
  • Headwater Research v. Google (W.D. Tex. 7:25-cv-00375 / 7:25-cv-00376): asserting US8631102B2, US8799451B2, and US8023425B2 against Google Pixel/Android devices and Google Fi; transferred to N.D. California on or about June 11, 2026 — still in district court, no CAFC appeal yet.
  • Headwater Research v. Sprint LLC (E.D. Tex. 2:25-cv-00359): same three patents asserted; dismissed without prejudice per a 2026 PACER order.
• Related CAFC 2026 dockets exist for the Headwater/Verizon case (Headwater Research v. Verizon, E.D. Tex. 2:23-cv-00352-JRG-RSP): Headwater's notice of appeal assigned CAFC No. 2026-1884, and Verizon's cross-appeal assigned CAFC No. 2026-1906 (both docketed and then deactivated pending post-trial motions as of May–June 2026). However, I could not confirm from my search results whether US8799451B2 is one of the asserted patents in the Verizon case — the asserted-patent list for that case was not shown in the retrieved docket pages. Do not assume 8799451 is in the Verizon appeal without checking the district-court pleadings.

Cautions / uncertainties

1. Independent-claim identification: Claims 1, 14, and 15 are identified as independent based on the RPX litigation reproduction; the Google Patents snippet also indicates dependent claims exist ("dependent claims 6"). I could not pull the USPTO full-text claims page directly in this session, so minor wording variances (e.g., "assisting in control of" vs. "assisting control of") may exist between sources.
2. Verizon appeal patent list: Unverified (see above).
3. Assignee: Listed as Headwater Partners I LLC at issue; assignment records show a 2017 merger/name change to Headwater Research LLC — Google Patents' current-assignee label is "Headwater Research LLC."
4. Abstract: The abstract quoted is from the published family/continuation text (EP-2392109-A1 / US20120197792A1) and is consistent with the specification provided; the full text you supplied was truncated before the formal abstract/claims block.

Based on my searches, US Patent 8,799,451 (the '451 patent, "Verifiable service policy implementation for intermediate networking devices") is being actively litigated in 2025–2026 by Headwater Research LLC (formerly Headwater Partners I LLC) against wireless carriers and device makers. All cases below assert '451 together with the same family trio: US 8,023,425 and US 8,631,102.

Confirmed litigation involving US 8,799,451

1. Headwater Research LLC v. [Cellco Partnership d/b/a Verizon Wireless](/litigations/by-plaintiff/Cellco%20Partnership%20d%2Fb%2Fa%20Verizon%20Wireless) et al.

• Plaintiff: Headwater Research LLC
• Defendants: Cellco Partnership d/b/a Verizon Wireless; Verizon Corporate Services Group Inc. (per Justia/Unicourt dockets). Note: Stanford's NPE Litigation Database lists a broader defendant set for this docket — AT&T Corp., AT&T Mobility LLC, AT&T Services, Inc., Sprint LLC, and T-Mobile USA, Inc. — which appears to aggregate related cases; the PACER-derived dockets name only the two Verizon entities.
• Jurisdiction / Case No.: E.D. Tex. (Marshall), 2:25-cv-00391
• Filing date: April 15, 2025
• Judges: Rodney Gilstrap (presiding); Roy S. Payne (magistrate)
• Patents: 8,023,425; 8,631,102; 8,799,451 (complaint asserts at least claim 1 of '451; accused instrumentalities are Verizon wireless devices supporting tethering/hotspot plus Verizon's tethering policy-enforcement systems)
• Status: Open as of the most recent docket entries retrieved (April 2025); no merits ruling or disposition found.
• Sources: Justia docket 2:2025cv00391; unicourt.com case pc-db5-casegu73a15cf9b5fb-2080396; npe.law.stanford.edu/patent/8799451; Ex Parte complaint analysis 2:25-cv-00391.

2. Headwater Research LLC v. AT&T Inc. et al.

• Plaintiff: Headwater Research LLC
• Defendants: AT&T Inc. / AT&T Mobility LLC / AT&T Corp. / AT&T Services, Inc.
• Jurisdiction / Case No.: E.D. Tex. (Marshall), 2:25-cv-00428
• Filing date: April 2025 (April 2025 "trio" per contemporaneous reporting)
• Patents: 8,023,425; 8,631,102; 8,799,451 (complaint asserts at least '451 claim 1; accused tethering-capable AT&T devices and network services)
• Status: Open; no disposition found in my searches.
• Sources: Ex Parte complaint/analysis 2:25-cv-00428 (ai-lab.exparte.com); Mondaq/MarketScreener article "Headwater Research Sues The Major Wireless Carriers For A Third Time This Year" (Aug. 6, 2025).

3. Headwater Research LLC v. Sprint LLC

• Plaintiff: Headwater Research LLC
• Defendants: Sprint LLC (T-Mobile/Deutsche Telekom)
• Jurisdiction / Case No.: E.D. Tex., 2:25-cv-00359
• Filing date: April 2025
• Patents: 8,023,425; 8,631,102; 8,799,451
• Outcome / Status: Dismissed WITHOUT PREJUDICE. Per PatSnap's review of the PACER docket, the court "ACCEPT[ED] AND ACKNOWLEDGE[D]" that all claims were dismissed without prejudice and denied all pending requests for relief as moot (2026 order). No findings on infringement or validity; refiling rights preserved.
• Sources: PatSnap litigation summary (patsnap.com), "Headwater Research v. Sprint LLC — Mobile Tethering Patent Dispute"; Mondaq article.

4. Headwater Research v. Google LLC (two cases)

• Plaintiff: Headwater Research LLC
• Defendants: Google LLC (accused: Pixel smartphones and Android-based devices used on Google Fi, and the Google Fi wireless service)
• Jurisdiction / Case Nos.: W.D. Tex., 7:25-cv-00375 and 7:25-cv-00376
• Filing date: 2025 (per PatSnap, the case spent 288 days in W.D. Tex. before transfer, implying a filing around late August 2025; exact filing date not confirmed)
• Patents: US8631102B2, US8799451B2, US8023425B2
• Status: Transferred to the Northern District of California on June 11, 2026 (procedural venue transfer; all three patents and claims survived intact). Pending in N.D. Cal.; no merits ruling on infringement, validity, or damages.
• Sources: PatSnap "Headwater Research v. Google — Mobile Device Patent Transfer" (reporting the June 11, 2026 transfer); Google Patents litigation links (portal.unifiedpatents.com listings for 7:25-cv-00375 / 7:25-cv-00376).

5. Headwater Research LLC v. Charter Communications Inc. et al.

• Plaintiff: Headwater Research LLC
• Defendants: Charter Communications Inc., et al.
• Jurisdiction / Case No.: E.D. Tex., 2:25-cv-00919
• Filing date: 2025 (docket numbering suggests a September 2025 filing; exact date not confirmed)
• Patents: 8,023,425; 8,631,102; 8,799,451
• Status: Unknown from my searches.
• Source: USPTO PTACTS petition document (ptacts.uspto.gov) listing "Headwater Research LLC v. Charter Communications Inc., et al., E.TX., Case No. 2:25-cv-00919" with patents 8,023,425 / 8,631,102 / 8,799,451; Google Patents litigation links for 2:25-cv-00919.

6. Headwater Research LLC v. [defendants not confirmed] (two cases)

• Jurisdiction / Case Nos.: E.D. Tex., 2:25-cv-00914 and 2:25-cv-00921
• Patents: 8,023,425; 8,631,102; 8,799,451 (per the USPTO PTACTS document)
• Filing date: 2025 (docket numbering suggests September 2025; not confirmed)
• Status: Unknown. The defendant identities could not be confirmed from my search results — do not assume they are the wireless carriers without checking PACER.
• Source: USPTO PTACTS petition document; Google Patents litigation links.

Flagged uncertainties / exclusions

1. Google case filing date and defendant details: The June 11, 2026 transfer date comes from PatSnap (a secondary source); I did not pull the W.D. Tex. docket directly. Note that June 2026 is after the nominal "current date" of April 26, 2026 given in your instructions — the underlying search/fetch data is dated August 29, 2026, so I have reported the later-dated events as retrieved.
2. 2:25-cv-00391 defendant list: Justia/Unicourt name only Cellco Partnership and Verizon Corporate Services Group; Stanford's NPE database lists additional carrier defendants (AT&T, Sprint, T-Mobile) for that same docket number. I flagged this rather than resolving it.
3. Verizon case 2:23-cv-00352 (with CAFC appeals 2026-1884 / 2026-1906): I could not confirm that '451 is among the asserted patents in that older Verizon suit. The reporting I found ties '451 to the 2025 tethering cases, not to the 2023 Verizon suit. Treat '451 as unverified in the CAFC appeals unless the district-court pleadings confirm it.
4. 2:25-cv-00920 (Dish Network) asserts a different patent trio (8,635,335; 10,791,471; 10,237,757) and is not a '451 case — excluded per your instruction not to return similar-but-different matters.
5. No PTAB/IPR proceedings directed to '451 were identified in my searches (the only IPR docket surfaced — IPR2025-00820 — concerns Align Technology, unrelated).

If you need defendant names for 2:25-cv-00914 / 2:25-cv-00921 or the exact Google filing dates, the next step would be pulling the PACER docket sheets for those case numbers directly.

Proceedings overview

There are 2 AIA trial proceedings on US 8,799,451, both Inter Partes Reviews filed by Google LLC et al. on the same day (2026-08-28), both Pending — zero proceedings with claims invalidated, zero with claims sustained (no Final Written Decision anywhere), zero settled, zero institution decisions issued yet. Bottom line for a defendant: the '451 patent is completely untested at the PTAB — every claim (including independent claims 1, 14, and 15) remains in full force — and the immediate question is not merits but whether Director Squires will institute at all under the current discretionary-denial regime ("settled expectations" / Fintiv), given that '451 issued 2014-08-05 (≈12 years old) and is asserted against Google in a parallel N.D. Cal. case.

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

• Type: Inter Partes Review
• Filed: 2026-08-28
• Status: Pending (verbatim from USPTO Open Data Portal; i.e., petition filed, no institution decision — the ordinary pre-institution phase)
• Judge panel: Not yet assigned/public — the petition is one day old as of the data ingest; no panel has been announced.
• Petition grounds: Not yet confirmed from public sources. The petition (Paper 1) and exhibits were filed 2026-08-28 but were not yet indexed in the searchable PTAB databases I could reach. I will not speculate on which claims or which references are asserted. (Filing pattern note only: two same-day petitions on the same patent, captioned "Google LLC et al.," is consistent with Google's broader 2025–2026 Headwater campaign, in which Google has paired Sotera stipulations with art such as Rao, Araujo, Freund, Singh, Montemurro, Wright, Vignaud, and RFCs — see IPR2026-00138 — but that is other-patent context, not a ground list for this proceeding.)
• Institution decision: Not yet issued. Statutory timing: the Director must decide within 3 months of the patent owner's preliminary response (or its due date) — 35 U.S.C. § 314(b). With a 2026-08-28 filing, a PO preliminary response is due on roughly a 3-month clock, so an institution decision would realistically land in Q1–Q2 2027 unless the Director acts earlier. Under Director Squires' practice (personal control of every institution decision since Oct. 2025; discretionary denials under § 314(a) on "settled expectations" and Fintiv grounds — Magnolia Medical, IPR2026-00097), institution is genuinely uncertain for a 12-year-old patent facing parallel litigation.
• Final Written Decision: None — no institution yet, so no trial, no FWD.
• Settlement / termination: None; proceeding is days old.
• Appeal: None; nothing to appeal yet.
• Defensive value: If you are Google or a privy, this petition (if instituted and won) could kill claims of '451 and estop you from nothing more than the grounds raised. If you are any other defendant, Google's petition gives you essentially no direct defense — estoppel does not run to you, and your own § 315(b) one-year clock from service is independently running.

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

• Type: Inter Partes Review
• Filed: 2026-08-28
• Status: Pending (verbatim from USPTO Open Data Portal; same pre-institution phase as above)
• Judge panel: Not yet assigned/public.
• Petition grounds: Not yet confirmed from public sources. Same caveat as IPR2026-00467 — the petition was filed the day before the data ingest and is not yet indexed in accessible databases. The natural inference (same petitioner, same patent, same day) is that Google split the challenge — e.g., different claim sets, different statutory grounds, or different art combinations — across the two petitions, a common hedge against redundancy denials, but that is inference, not verified fact.
• Institution decision: Not yet issued. Same § 314(b) framework as above; expect a decision roughly 3 months after the PO preliminary response (or its due date), i.e., realistically Q1–Q2 2027.
• Final Written Decision: None.
• Settlement / termination: None.
• Appeal: None.
• Defensive value: Identical to IPR2026-00467 — watch it if you're in Google's camp; do not rely on it if you're a separate defendant. If both petitions are instituted, the Board will typically coordinate the trials (and may consolidate or stay one), and Google would face a 12-month statutory trial deadline from institution for the FWD.

Strategic summary

Claim status: 100% untested, 100% in force. No claim of '451 — independent apparatus claim 1, computer-program-product claim 14, method claim 15, or any dependent claim — has been canceled or even substantively reviewed by the PTAB. There is no FWD, no institution decision, no settlement, and no prior IPR history on this specific patent. The only PTAB activity that has ever existed for '451 is these two petitions filed 2026-08-28. (Do not confuse the many other Google v. Headwater IPRs — e.g., IPR2024-00942, IPR2024-00809, IPR2026-00049, -00137, -00138, -00203 — which target other Headwater patents like 9,647,918, 9,609,544, and the '541/'042 family patents, not '451.)

Estoppel landscape. If these IPRs are instituted and reach FWD, 35 U.S.C. § 315(e)(2) will estop Google (and its real parties in interest/privies — note the "et al." caption, whose identity I could not confirm) from asserting in the N.D. Cal. litigation any invalidity ground that was raised or reasonably could have been raised in the IPRs. But the practical reality for a new defendant is the opposite: you are not estopped by Google's proceedings, and unless you are in privity with Google, every § 102/§ 103 ground over patents and printed publications remains available to you — subject to your own § 315(b) one-year bar from service of the complaint. If you were served in 2025 (e.g., the W.D. Tex. / N.D. Cal. Google case, or the E.D. Tex. carrier cases), that clock may be running or expired; check service dates immediately. Because '451 issued from a 2009 application with a 2009 priority date, the § 102(b)/AIA effective-filing-date analysis matters: art published more than one year before the critical date is the strongest available class of references.

Pattern signals. (1) Serial, coordinated petitioner: Google has filed a wave of IPRs across Headwater's portfolio (2024–2026), and these two same-day petitions on '451 are part of that campaign — Google is litigating '451 in N.D. Cal. (transferred from W.D. Tex. 7:25-cv-00375/-00376, where '451, 8,631,102, and 8,023,425 were asserted) and now attacking the patent at the PTAB in parallel. (2) Aggressive patent owner: Headwater (counsel: Russ August & Kabat) has been filing preliminary responses with detailed discretionary-denial briefs attacking the sufficiency of Google's Sotera stipulations (see IPR2026-00137/-00138 papers) — expect the same playbook here against the "settled expectations" and Fintiv factors. (3) Hostile institution climate: since Oct. 2025, Director Squires has personally controlled every institution decision and denied a large majority on discretionary grounds; the "settled expectations" policy disfavors review of patents in force 6+ years, and '451 is ~12 years old. That said, the Board has instituted at least one Google v. Headwater IPR (IPR2026-00049, trial instituted) and a bulk order in April 2026 granted a couple of petitions including a Google/Headwater challenge — so institution is possible but far from assured. (4) No defensive aggregator: unlike many NPE-targeted patents, there is no Unified Patents/OpenSky-style aggregator in the chain here — the petitioner is the accused infringer itself. (5) The pending Supreme Court petition in Google v. VirtaMove (No. 25-1230) challenges the settled-expectations policy; a grant of certiorari could materially change the institution calculus for these very petitions, though the petitions here would likely be decided first.

Recommended next steps

1. Pull the petitions now. Both IPR2026-00466 and IPR2026-00467 were filed 2026-08-28; the papers should be publicly available on PTAB E2E (uspto.gov/PTAB/E2E) and via Docket Navigator/Docket Alarm as they index. Get Paper 1 (petition) and the exhibit list to learn: which claims are challenged, what art/grounds (§ 102/§ 103), who the "et al." co-petitioners/RPIs are, and whether a Sotera stipulation was filed (Google's pattern in IPR2026-00137/-00138 suggests one will appear). This determines everything downstream — including whether you are estopped (if you're a co-petitioner/privy) or unaffected (if not).
2. Calendar the institution milestones. PO preliminary response is due ~3 months from the notice of filing date (likely late Nov. 2026); institution decision is due within 3 months after that response (35 U.S.C. § 314(b)) — realistically Q1–Q2 2027. If instituted, the FWD is statutorily due within 12 months of institution (§ 316(a)(11)), with the possibility of a 6-month extension for good cause. Watch for the Director's bulk institution orders, which under current practice may come in waves rather than per-case.
3. If you are a separate defendant, do not wait on Google. Google's IPRs do not extend § 315(e)(2) estoppel to you, and they do not stop your § 315(b) one-year deadline from service. If you were served recently, consider whether your own petition (with your own art) is warranted; if your deadline has passed, your validity defenses live in district court only, and Google's institution outcome has no binding effect on you (though a Google FWD would be persuasive authority and could support a stay motion in your case).
4. Link the FWD if/when it comes. There is no FWD to link today — the honest statement is that no PTAB merits decision on '451 exists. When the institution decisions issue (and, if instituted, the FWDs), cite them from PTAB E2E and the PTAB Decisions database; until then, any demand letter citing "PTAB victories" against Headwater is referring to other patents in the portfolio, not '451.
5. Track the discretionary-denial overlay. Monitor Google v. VirtaMove (Sup. Ct. No. 25-1230) and Director Squires' § 314(a) guidance — including the Magnolia Medical rationale and any new "true alternative" (Sotera) requirements. These are the single largest variables for whether IPR2026-00466/-00467 ever reach the merits, because Headwater will almost certainly move for discretionary denial citing the parallel N.D. Cal. case and the patent's age.

Bottom line: No claims of '451 have been invalidated, sustained, or even institution-reviewed. The patent is a live, fully enforceable threat, and the only PTAB docket on it consists of two day-old, pre-institution Google petitions facing a skeptical Director. A defendant's realistic PTAB leverage today is procedural (institution risk, estoppel planning, stay arguments) — not a merits win that does not yet exist.

I've hit my tool-call limit, so I'll now reconstruct the assignment record from what the searches returned, flagging clearly which data points are confirmed vs. unverified. I was unable to pull the USPTO Assignment Center directly this session; the reel/frame data below comes from litigation exhibits (PACER/CourtListener archives) and the Google Patents legal-events feed.

Inventors

• Gregory G. Raleigh — sole named inventor on US 8,799,451. Employer at the time of filing: none (founder of Headwater). Raleigh left Qualcomm on September 19, 2008 and filed the '354 provisional (priority basis for this patent) on January 28, 2009 — approximately four months after departing. (Source: E.D. Tex. briefing in the Samsung/Verizon standing disputes, gov.uscourts.txed.220857 / 224519 exhibits.)
• Unusual pattern worth flagging: Raleigh's provisional filing landed within one year of his Qualcomm departure, which triggered a statutory presumption that Qualcomm co-owns the Headwater portfolio. Qualcomm's alleged co-ownership of the family (including the '022/'354 lineage) was litigated as a standing defense in Headwater Research v. Samsung (E.D. Tex. 2:22-cv-00422) and Headwater Research v. Verizon (E.D. Tex. 2:23-cv-00352). This is an ownership-chain vulnerability, not a fire-sale signal, but it makes the chain contested.

Original assignee

• Headwater Partners I LLC (Delaware LLC) is the assignee named on the issued patent (Google Patents legal event, recorded 2009-06-09; original address 350 Marine Parkway, Suite 300, Redwood City/Redwood Shores, CA 94065).
• Primary line of business: development of device-assisted service policy / "service processor" technology — never a shipping product company. Raleigh publicly described pitching the technology to carriers and OEMs ("we distributed it to carriers, pitched it to OEMs") rather than selling products (video cited in the Samsung case, Ex. 1).
• Current status: still exists as a legal entity, now styled Headwater Research LLC (Delaware, principal place of business 1011 Pruitt Place, Tyler, TX 75703 per the 2016 merger certificate). Its business since 2022 is patent assertion — it is the named plaintiff in a large, ongoing multi-defendant campaign.

Assignment timeline

• 2009 (execution date not confirmed) / recorded 2009-06-09 — Reel/frame not confirmed in this session (flagged: I could not pull the Assignment Center record directly; the event is confirmed only via Google Patents' legal-events feed: "ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: RALEIGH, GREGORY G.")

  • Conveyance: Assignment
  • Assignor: Gregory G. Raleigh
  • Assignee: Headwater Partners I, LLC
  • Correspondent: not confirmed for this specific record
  • Context: founder-to-company assignment at formation; no money changes hands — the standard inventor-to-startup transfer.

• 2016-12-29 (effective) / recorded 2017-01-04 — Reel 041248 / Frame 0777 (confirmed from PACER exhibit, Case 2:23-cv-00352 Doc. 200-17, archive.org copy)

  • Conveyance: Merger and Change of Name
  • Assignor: Headwater Partners I LLC (merging into Headwater Management LLC)
  • Newly merged entity: Headwater Management LLC; surviving entity renamed Headwater Research LLC
  • Submitter/correspondent: Ann Taylor (cover sheet signed 01/04/2017)
  • Context: internal Delaware LLC reorg — Headwater Partners I LLC merged with and into Headwater Management LLC under the new name Headwater Research LLC; same ownership, change of name only. No change in economic ownership.

• 2019-05-07 (recorded) — Reel 049108 / Frame 0205 (and referenced prior corrective, Reel 048531 / Frame 0366), per PlainSite's Headwater assignment index

  • Conveyance: Corrective Assignment (correcting the corrective assignment previously recorded at 048531/0366)
  • Assignors: Gregory G. Raleigh; Alireza Raissinia; James Lavine
  • Assignee: Headwater Partners I, LLC
  • Correspondent: not confirmed in snippet
  • Context: Coverage of '451 unverified — this corrective assignment concerns the multi-inventor (Raleigh/Raissinia/Lavine) applications (e.g., 13/134,028); '451 is a Raleigh-only application, so these corrective records may or may not list it. Flag: do not cite as on-chain for '451 without pulling the property list.

No other recorded assignments found: no security agreements, licenses, or transfers to third parties appear on this patent's chain in the sources reviewed. The chain is short: Raleigh → Headwater Partners I LLC (2009) → Headwater Research LLC (2016/2017 name change).

Timeline diagram

timeline
    title Ownership of US 8799451
    2008 : Raleigh leaves Qualcomm
    2009 : Raleigh files provisional
         : Assigned to Headwater Partners I LLC
    2014 : Patent issued
    2016 : Merged into Headwater Management LLC
    2017 : Renamed Headwater Research LLC
    2025 : First infringement suits filed

NPE / troll-pattern signals

1. Shell-entity transfer — present (strong). The assignee is a Delaware LLC (Headwater Partners I LLC / Headwater Research LLC) with no product in commerce; the 2016 merger certificate lists the surviving entity's principal place of business as a residential address (1011 Pruitt Place, Tyler, TX 75703) in the Eastern District of Texas — the forum where Headwater filed its carrier suits. Stanford's NPE Litigation Database independently classifies this as an "Individual-inventor-started" NPE (npe.law.stanford.edu/patent/8799451). This is more than naming inference: the entity's only observable commercial activity since 2022 is assertion.

2. Known asserter in the chain — present (strong). Headwater Research LLC is a high-frequency plaintiff tracked by Unified Patents and the Stanford NPE database; it has asserted the '425/'102/'451 trio against AT&T (2:25-cv-00428), Verizon (2:25-cv-00391), Sprint (2:25-cv-00359, dismissed without prejudice), Google (W.D. Tex. 7:25-cv-00375/-00376, transferred to N.D. Cal.), Charter (2:25-cv-00919), and others, on top of its 2022–2023 Samsung/Motorola/Verizon campaign.

3. Repeat correspondent across the chain — unclear. The 2017 merger cover sheet was submitted by Ann Taylor; earlier Headwater family assignments (e.g., 13/134,028, 2011) were recorded through Sheppard, Mullin, Richter & Hampton LLP (Marc A. Sockol, 390 Lytton Ave, Palo Alto) — but that Sheppard Mullin record is on a related application, not on '451's own chain, and Headwater's current litigation counsel is Russ August & Kabat. I cannot establish recurrence on this patent's specific records without the 2009 cover sheet, so I mark this not confirmed rather than a finding.

4. Cascading transfers — not present. The chain has exactly one substantive link (Raleigh → Headwater Partners I, 2009) plus a 2016/2017 name-change merger. The 2019 corrective assignments are title-correction filings, not cascading LLC transfers.

5. Pre-litigation transfer — not present. The only post-issuance event (2017 name change) predates Headwater's first infringement suits (2022) by five years. No assignment dated within six months before the 2025 suits was found.

6. Bankruptcy fire-sale — not present. No Chapter 7/11 for Headwater Partners I LLC or Headwater Research LLC; the patent was not acquired in any bankruptcy auction.

7. Privateering — not present (but contested standing, see Inventors). No operating company transferred '451 to Headwater to assert against competitors. The inverse allegation exists — Qualcomm's claimed co-ownership based on Raleigh's and Raissinia's pre-departure assignments — but that is a standing dispute, not privateering.

8. Defensive aggregator (anti-NPE) — not present. The chain terminates at Headwater Research LLC, an asserting entity. RPX, AST, LOT, Unified Patents, and OIN do not appear anywhere in the chain.

Verdict

NPE — high confidence.

Two strong signals drive this: (1) the patent resides in an individual-inventor-started Delaware LLC (Headwater Research LLC, formerly Headwater Partners I LLC) that ships no product and whose post-2016 business is assertion — its own merger certificate (Reel 041248/Frame 0777, recorded 2017-01-04) places it at a Tyler, TX residential address in the E.D. Tex. filing district; and (2) the entity is a recognized high-frequency plaintiff per the Stanford NPE Litigation Database and Unified Patents, currently asserting the '451 patent (with 8,023,425 and 8,631,102) against AT&T, Verizon, Sprint, Google, Charter, and others in 2025–2026. The single original assignment from Gregory G. Raleigh to Headwater Partners I LLC (recorded 2009-06-09) plus the 2016/2017 name-change merger is a classic founder-to-assertion-vehicle chain — no operating company, no products, no defensive aggregator anywhere in it.

Verification: USPTO Patent Assignment Search — https://assignmentcenter.uspto.gov/ (search patent 8,799,451; compare Reel 041248/Frame 0777 for the 2017 merger and confirm the 2009 Raleigh assignment reel/frame, which I could not confirm in this session).

I'll research the prior-art citations for US 8,799,451. Let me start with targeted searches.

Let me dig into the specific "References Cited" (backward citations) for this patent.

Important scope note up front

I ran the requested searches against the specific number 8799451 / US8799451B2 (no substitution or auto-correction of any identifier). I was able to confirm the patent's bibliographic record, its family, and its claims — but I was not able to retrieve the authoritative "References Cited" (backward-citation / PTO-892) list for this patent in this session. One search returned the forward citation table (patents citing '451), and a few candidate backward references appeared only indirectly (via citation-table anchor context), not from the prosecution record itself. I also hit the tool-call limit before I could pull the EPO/Espacenet or USPTO Patent Public Search citation list. I will not present indirect hits as confirmed prior art. Everything below is either (a) confirmed from the source cited, or (b) explicitly labeled as unverified.

One housekeeping flag, consistent with the previously generated sections: your instructions say "Current Date: April 26, 2026," while the session header and the fetched patent data are dated later (2026-08-29 ingest / 2026-09-15). The PTAB section of this analysis already flagged that the two Google IPRs on '451 were filed 2026-08-28 — i.e., after the nominal "today." I have kept the previously generated sections intact and flag the discrepancy rather than resolving it.

1. The patent being analyzed (confirmed)

Independent claims to be mapped against § 102 (confirmed from RPX's full-text reproduction, not from the truncated full text you supplied — the supplied text is cut off before the claims):

• Claim 1 — apparatus: first end-user device; modem(s) for a first network (wireless access network) and a second network; processor to (i) provide a forwarding service forwarding first traffic between other end-user devices and the network system, (ii) implement a first service policy for the first (forwarded) traffic, (iii) implement a second service policy for second traffic associated with the first device's own access to services over the first network, "wherein the second service policy differs from the first service policy," and (iv) monitor or identify successful use or attempted use of the forwarding service; plus memory.
• Claim 14 — computer program product on a non-transitory CRM: same functional quartet.
• Claim 15 — method: same functional quartet.
• Dependent claims follow (the Google Patents index confirms dependent-claim content such as "dependent claims 6," "cellular," "limiting," "change," "storage" token counts, but I could not enumerate claims 2–13 and 16+ from a primary source in this session).

2. What I could NOT retrieve, and why it matters for a § 102 answer

The examiner's citation list ("References Cited" on the face, and the PTO-892/PTOL-892 forms in the file wrapper) is the only authoritative answer to "each patent citation for 8799451." My searches returned:

• the "Referenced By" (forward) table on FreePatentsOnline — patents that cite '451, mostly 2013 vintage (see §5); and
• Google Patents forward-citation rows on third-party pages (KR20140005192A, KR20150076137A, AU2007261116B2, US7280818B2), which tell me documents are in a citation relationship with '451 but not reliably in which direction from a search snippet alone.

I did not obtain the PTO-892, the FPO "References Cited" table, or Espacenet's "Cited documents" set. Any claim-by-claim § 102 anticipation assertion made without that list would be speculation, so I have not made one.

3. Candidate backward citations (prior art potentially cited in/against '451) — UNVERIFIED

These are the only documents that surfaced in a citation relationship with '451 in search results. Treat all dates as unconfirmed except where the snippet displayed them.

Bottom line on the candidates: none of the five, on the information actually available, is an apparent full-claim anticipatory reference for independent claim 1, 14, or 15. Their plausible § 102 exposure is confined to individual limitations (policy enforcement; multi-network selection; notification/monitoring), which makes them more naturally § 103 combination art than § 102 art — but that conclusion is provisional until the actual PTO-892 is pulled.

4. Same-family / self references — NOT § 102 prior art (important)

'451 belongs to the large Headwater 12/380,xxx family claiming priority to the 2009-01-28 provisionals (61/206,354, 61/206,944, 61/207,393, 61/207,739). The search surfaced sibling family members that would appear in the citation graph but cannot be § 102 prior art against '451:

• US 8,023,425 B2 (application 12/380,771) — asserted alongside '451 in the 2025–2026 carrier suits (PatSnap lists it expressly as a companion at issue).
• US 8,631,102 B2 (application 13/678,417) — same trio.
• US 2012/0192249 A1 — "Verifiable Service Policy Implementation for Intermediate Networking Devices," filed 2012-04-04, priority 2009-01-28 (RPX) — same title lineage.
• US 2010/0191846 A1 — the pre-grant publication of '451 itself (published 2010-07-29 per Google Patents).
• The many later Headwater continuations in the Google Patents "Priority to …" list (e.g., 13/134,005 → US8635335B2; 13/134,028 → US8589541B2; 13/229,580 → US8626115B2; 13/309,556 → US8893009B2; 13/309,463 → US8793758B2, etc.).

These are common-ownership, same-priority-chain documents: cross-citations among them are not § 102(a)/(b)/(e) art as to '451.

5. Forward citations — also NOT § 102 prior art

FreePatentsOnline's list for '451 (freepatentsonline.com/8799451.html) shows a long "Referenced By" set of later patents, e.g.:

These cite '451; they do not anticipate it (all issued 2013, after '451's 2009 filing/priority). Their only prior-art significance is the rare case where one has a pre-2008-01-28 effective filing date — if so, it would be § 102(e) art in its own right and would need to be checked separately (e.g., US 8,489,720 "Cost-aware, bandwidth management systems…" and US 8,526,329 "Hierarchical communication system…" are the two worth a priority check because both are in the bandwidth/usage-management subject-matter neighborhood and older portfolios).

6. The § 102 framework that governs any mapping here

'451 has a 2009 filing/priority date and was filed before 2013-03-16, so pre-AIA § 102 applies:

• § 102(b) critical date = 2008-01-28 (one year before the 2009-01-28 provisional priority, assuming the provisional supports the claim). Anything published or patented on or before 2008-01-28 is the strongest class of art — a printed publication under § 102(b) needs no prior-filing gymnastics.
• § 102(a) — knowledge/use by others, or patented/published before the invention date (the 2009-01-28 provisional date, subject to swearing behind).
• § 102(e) — US patents and US pre-grant publications by another filed before 2009-01-28, even if they published later. This is the vehicle by which references not on the patent's face become anticipatory art (e.g., candidate #5 above, if it was filed before the critical date — I could not confirm).
• § 102(g) — prior invention by another (rarely used now, but relevant to Headwater's standing/co-ownership dispute, which the assignment section already flagged re: Qualcomm).
• Standards/printed publications (3GPP, IETF RFCs) can be § 102(b) art and are not "patent citations" at all — for this claim set, the relevant bodies of art are PCC/charging policy (3GPP policy-and-charging architecture), AAA (RADIUS/Diameter), and mobile tethering/hotspot practice.

Because the invention predates AIA, the analysis must also be run against the 1-year grace period, meaning a reference published in, say, mid-2008 is not § 102(b) art to '451 (it would have to be § 102(a)/(e) art).

7. Limitation-by-limitation § 102 map (the only defensible form of the answer today)

For each candidate reference, here is what would have to be shown — and none of the candidates on the current record shows it:

The combination of "forwarded-traffic policy ≠ own-traffic policy" + "monitor/identify use or attempted use of the forwarding service" is the point of novelty worth attacking, and it is not met by any reference surfaced in these searches. That is also consistent with the previously generated litigation section: the 2025–2026 suits (Verizon 2:25-cv-00391, AT&T 2:25-cv-00428, Google 7:25-cv-00375/-00376) accuse "tethering-capable devices + carrier tethering policy-enforcement systems" — the plaintiff's theory itself depends on the dual-policy + monitoring combination.

8. Where the real prior art for '451 is likely to be found (and it is not the face of the patent)

For a 2009-priority tethering/policy patent, the face-cited references are usually a small, examiner-bounded set. The stronger § 102 candidates come from three places I could not reach here:

1. The PTO-892 / file wrapper for 12/380,773 — Patent Center and the "References Cited" table (FreePatentsOnline, Espacenet "Cited documents"). This is the deliverable you asked for and I could not retrieve it.
2. The two unfiled-at-ingest Google petitions, IPR2026-00466 and IPR2026-00467 (filed 2026-08-28) — per the previously generated PTAB section, their grounds are not yet public/indexed, so I will not guess the references. When available on PTAB E2E, those petitions will contain Google's chosen § 102/§ 103 art for '451 and will be the single most informative prior-art source. Note the caveat already recorded: the Rao/Araujo/Freund/Singh/Montemurro/Wright/Vignaud/RFC art identified in other Google v. Headwater IPRs (e.g., IPR2026-00138) targets other patents and must not be imported into a '451 analysis without verification.
3. Non-patent literature — pre-2008 3GPP policy/charging specifications, OMA device-management and tethering-related specifications, and IETF AAA/RADIUS/Diameter RFCs, all of which are § 102(b) printed publications if published on or before 2008-01-28. These will not appear in a "patent citation" list but are fully available § 102 art.

9. Explicit uncertainties (do not treat as resolved)

1. The "References Cited" list for US 8,799,451 was not obtained. This is the central limitation of this answer. No § 102 anticipation assertion should be relied upon until the PTO-892 is pulled from the file wrapper.
2. Citation direction is unverified for US 7,280,818 B2, AU 2007261116 B2, KR20140005192A, KR20150076137A. The snippets show them in a citation table with '451 but do not prove '451 cited them (vs. them citing '451). Items 1–5 in §3 are candidates, not findings.
3. US 2004/0107360 A1's "priority date" appeared as "2005-07-07" in one snippet, which is internally inconsistent with a 2004 publication number and may belong to a neighboring row. Flagged, not resolved.
4. US 2009/0286507 A1's date — the "2009-01-27" in the snippet is attached to a Headwater-assignee row, not necessarily to this reference. Its own filing date (critical for a § 102(e) theory) is unconfirmed.
5. Claim enumeration is incomplete — only independent claims 1, 14, 15 were reproduced in full (via RPX); the dependent claims were not retrievable from a primary source in this session, so no dependent-claim § 102 mapping is offered.
6. Consistency with prior sections: this answer does not contradict the previously generated patent summary, litigation summary, PTAB, or assignment sections. Where the earlier PTAB section said "petition grounds not yet confirmed," that constraint still holds and is the reason no IPR-based art is listed here as a § 102 reference.

10. Recommended next actions (to convert the above into a real § 102 chart)

1. Pull the file wrapper for 12/380,773 on USPTO Patent Center (or the FPO/Espacenet "References Cited" tables) and transcribe every item on the PTO-892 with its US class/subclass and examiner initials.
2. For each cited reference, compute its effective filing date vs. 2008-01-28 / 2009-01-28 to classify it as § 102(a), (b), (e), or (g) art — not merely "cited."
3. When PTAB E2E indexes IPR2026-00466 / IPR2026-00467, extract the asserted grounds; that gives a ready-made, well-funded § 102/§ 103 set for '451 specifically.
4. Build the chart against the four-limitation test in §7 above, focusing on the differing-policy and monitor-use-of-forwarding-service limitations, which are the least likely to be met by any single reference and therefore the best § 103 combination targets.
5. Keep § 315(b) timing in view (per the earlier PTAB section): Google's petitions do not estop or toll a separate defendant's one-year clock from service.

Bottom line: I confirmed the target patent's identity and claims, confirmed the applicable pre-AIA § 102 framework and critical dates, and identified the candidate references appearing in '451's citation graph — but I could not retrieve the authoritative examiner-cited reference list, and on the evidence available none of the candidate references is an apparent full-claim anticipation of claims 1, 14, or 15. The dual-differing-policy plus forwarding-service-monitoring combination remains the strongest novelty anchor for '451, and the definitive prior-art set for it will come from the PTO-892 and the two 2026-08-28 Google IPR petitions, neither of which I could obtain here.

I'll research prior art relevant to the '451 claims before constructing the § 103 combinations.

Obviousness analysis — US 8,799,451 B2 under 35 U.S.C. § 103

0. Scope, sourcing, and two explicit flags

Flag 1 — no "Prior Art section" was supplied on this page. You directed me to "use the results from the Prior Art section of this page," but the page content provided to me consists of the Google Patents full text of US8799451B2 (truncated before the claims/abstract block) plus the six previously generated sections. There is no prior-art section on the page. I therefore built the grounds below from (a) the prior-art references already identified in the earlier-generated sections (Rao, Araujo, Freund, Singh, Montemurro, Wright, Vignaud, RFCs), (b) the reference lists surfaced in my own searches this session, and (c) the intrinsic admissions in the '451 specification. Every reference I could not independently verify is labeled [unverified].

Flag 2 — date contradiction, per the standing instruction to flag contradictions explicitly. The header of this task says "Current Date: April 26, 2026," but the previously generated Litigation and PTAB sections report events dated 2026-08-28 (the Google IPR2026-00466/-00467 filings) and 2026-06-11 (the W.D. Tex. → N.D. Cal. transfer). Those are after the nominal current date. I am treating the earlier sections' retrieved data as authoritative for their own facts (as instructed) but flagging that the timeline in this document is internally inconsistent and that the two Google IPR petitions are the single most valuable source of a curated, real-world § 103 ground list for this patent — and their petition papers were not indexed in my searches. Not confirmed: the grounds, claims challenged, and "et al." real parties in interest in IPR2026-00466/-00467.

Claim text used. I confirmed the operative language from the RPX litigation reproduction (litigation.rpxcorp.com/patent/US8799451B2), which resolves the wording uncertainty noted in the Patent Summary section: claim 1 recites a device that (i) has one or more modems to a wireless access network and to other end-user devices, (ii) provides a forwarding service forwarding "first traffic" between those devices and the network system, (iii) implements a first service policy for the first traffic, (iv) implements a second service policy for the first device's own traffic over the wireless network, "wherein the second service policy differs from the first service policy," and (v) "monitor[s] or identif[ies] successful use or attempted use of the forwarding service." Claims 14 and 15 track this combination (medium/instructions form; method form). 69 claims total.

Critical point for the analysis: the claim's "verifiable" hook is only the bare monitoring/identifying step in element (v). It contains no cryptographic attestation, no integrity-check, no signed-report, and no tamper-resistance limitation. That matters enormously: nearly the entire § 103 attack collapses onto element (v), and element (v) is satisfied by ordinary, well-known tethering-detection.

1. Governing law and the critical date

• '451 is a pre-AIA patent (filed 2009-03-02, priority to provisionals dated 2009-01-28). Pre-AIA §§ 102/103 apply; there is no AIA § 102(d) excepted-disclosure carve-out, but pre-AIA § 103(c) common-ownership disqualification applies to § 102(e)/(f)/(g) art.
• Critical date = 2009-01-28 (the earliest provisional). Art must be § 102(a) (known/published/patented before invention) or § 102(b) (>1 year before filing, i.e., before 2008-01-28/2009-01-28 depending on which date is used) or § 102(e) (US application publication filed before the invention date).
• The § 271(e)(1)/Graham/KSR framework: "A patent composed of several elements is not proved obvious merely by demonstrating that each of its elements was, independently, known in the prior art" (KSR Int'l v. Teleflex, 550 U.S. 398, 418 (2007)). The grounds below therefore supply an articulated reason to combine, plus a reasonable expectation of success, for each.

2. Candidate prior art and its § 102 availability

Not prior art — flag and exclude. US 2012/0240197 A1 (Smith Micro, "Managing Tethered Data Traffic Over a Hotspot Network," priority 2011), EP 2760179 / US 9,276,936 (Synchronoss "Tethering enforcement device controller," 2013), and US 8,949,439 (resource-conscious tethering) all post-date the '451 critical date and cannot be used in a § 103 ground against '451. They are confirmatory of the field's later trajectory only.

3. The § 103 grounds

Ground 1 — Qualcomm '865 in view of Rao (and optionally Montemurro)

Element-by-element mapping to claim 1:

Motivation to combine (articulated):

1. Same field, same problem. Both references address the carrier's need to authenticate, authorize and account for data traffic that a subscriber's device generates on behalf of another device — precisely the billing/authorization problem tethering creates.
2. Rao's teaching is expressly generic as to connection type. Once a POSITA has the tethered architecture of '865, applying Rao's "different policies for different networks/interfaces" to distinguish the tethered link from the device's own link is a straightforward, predictable application of a known policy-selection technique — not a new architecture. KSR, 550 U.S. at 417 ("if a technique has been used to improve one device, and a person of ordinary skill in the art would recognize that it would improve similar devices in the same way, using the technique is obvious").
3. Result is predictable and requires no new hardware. Both references are software/firmware-level policies on a device that already has both radios and a memory. No unexpected results.
4. Industry incentive. Carriers of the 2007–2008 era offered tethering as a separately priced feature and policed unauthorized tethering; a POSITA had a strong market reason to make the device's own traffic and the tethered traffic subject to distinct policies.

Ground 2 — Qualcomm '124 in view of Montemurro (and Rao), further in view of Chalk '127 or Qwest '157

'451's claim 1 requires no authentication function, so a ground built on '124 (a device that regulates tethered data calls) is even cleaner than Ground 1 on the forwarding/regulating limitations:

• '124 supplies "first end-user device capable of operating as an intermediate networking device" + "forwarding service" (enabler 210 "can facilitate a tethered data call") + regulation of the forwarded call (analyzer 208 / protector 214 / blocker 216) — which is, at minimum, "a first service policy… for assisting in control of the first traffic."
• Montemurro and Rao supply the second, different policy for the device's own traffic, via the express "different policies for different networks" teaching.
• Chalk '127 supplies the last element with unusual directness: a tethering alert generated by comparing incoming and outgoing data — i.e., monitoring/identifying successful use of the forwarding service. Qwest '157 supplies the same concept from the network-administration side (detecting unauthorized wireless access points).
• Motivation: tethering detection and tethering billing were twin requirements of the same operator feature set; a POSITA combining '124's device-side tethering control with Chalk's tethering-detection alert and Rao/Montemurro's connection-differentiated policy is combining references that "address[] similar problems," the classic KSR rationale. Predictable result: one device that (a) tethers, (b) applies one policy to tethered traffic and a different policy to its own traffic, and (c) knows when tethering is happening.

Ground 3 — Intent-to-use / claim-construction overlay on the "monitor or identify" step

Even standing alone, element (v) is close to a results-oriented functional limitation whose only content is "know when the hotspot is being used or attempted." A Wi-Fi hotspot phone in 2008 necessarily knew client association and DHCP lease events; the '451 specification itself concedes the general state of the art. See § 5 below. Under KSR and In re Kubin, a limitation that claims only the intended result of expressly disclosed or routine functionality adds little to the obviousness inquiry (not a substitute for a full ground — offered as a claim-construction/weight argument, not as an independent § 103 basis).

4. Dependent claims and claims 14/15

• Claims 14 and 15 recite the same combination in medium and method form. The only variation is directional placement of the two networks (in claim 14, "first network" is the device-to-device link and "second network" is the wireless access network; claim 15 matches claim 1's ordering). Both are met by the same grounds, with the mapping adjusted. Because they rise and fall with claim 1's substance, they add no independent patentable weight absent a claim-construction win on element (v).
• The six dependent "dependent claims" noted on Google Patents' term-frequency page (3 cellular / 3 computer-program-product / 15 storage / 14 change / 4 limiting / 6 dependent) are claim-count metadata, not claim content — I could not retrieve dependent-claim text this session, so I cannot give an element-level § 103 ground for each dependent claim. Any dependent claim adding, e.g., "the first service policy comprises a bandwidth limit" or "the second service policy comprises a usage-based billing rate" would fall to Rao/Montemurro (QoS, cost, bandwidth policy factors) nearly automatically. Flag: dependent-claim grounds incomplete due to missing claim text.

5. The patent owner's own specification as § 103 ammunition

The '451 specification contains admissions that sharply narrow the inventive gap:

• It characterizes the pre-existing art as already having "device agent software… present and properly configured" and reporting service usage from the device — the applicant's own statement that "merely determining that billing reports are being received from the device, that the device agent software is present and properly configured (e.g., the billing agent is present and properly configured) is insufficient and easily spoofed." That is a concession that device-side agents implementing and reporting service policy were known in the art, and that the only asserted delta in the family was verifiability. Since issued claim 1 does not claim cryptographic verifiability — only "monitor or identify… use" — the conceded prior art does the heavy lifting.
• It states the motivation directly: "Another form of billing that needs improvement is electronic commerce transaction billing with device assisted central billing," and it characterizes the market need for tethering/intermediate-device differentiation as existing ("users… desire to pay less for lower bandwidth service usage").
• It describes the network-based DPI alternative as inadequate for encrypted flows — which is a motivation to move policy into the device, i.e., a motivation to combine device-side policy references with network-side ones.

6. Where the obviousness case is weak (defendant-side risk assessment)

1. Element (v) is the whole ballgame, and its scope is contested. Patent Owner will argue "monitor or identify successful use or attempted use of the forwarding service" requires detecting tethering as distinct from merely operating the device normally, and will fight any mapping in which tethering detection is merely incidental (as in '865) rather than the reported/purposeful object. Chalk '127 (an actual tethering alert) is the strongest answer; without its pre-critical-date filing date confirmed, element (v) rests on '865's inherent interception plus Qwest's rogue-AP detection — an inference, not a slam dunk.
2. § 102(e) dates for Montemurro, '124, Chalk '127 are unconfirmed. If Montemurro's and '124's US filings post-date the '451 provisional (2009-01-28), they drop out entirely, and Ground 2 collapses to '865 + Rao + Qwest (Rao survives as § 102(b) publication art from 2006). Ground 2 as written should not be filed without confirming those filing dates on USPTO Patent Center / Global Dossier.
3. No single-reference anticipation (§ 102) identified. Nothing in my searches discloses, in one reference, both the tethering-forwarding architecture and the expressly different second policy for the device's own traffic and the monitoring step. This is a §§ 103-only case on independent claims 1/14/15.
4. Secondary considerations. Headwater has no commercial product (Confirmed in the earlier Assignment/NPE section: never a shipping-product company), so no commercial-success or industry-praise nexus is available; the realistic secondary consideration is long-felt need/copying, which Patent Owner may pitch using the 2009–2010 carrier adoption of tethering tiers. That is a weak nexus because the claimed delta (monitoring use of a forwarding service) is not the feature that drove adoption.
5. What Patent Owner will argue. (a) Teaching away / bodily incorporation — that none of Rao, Montemurro or '124 contemplates a device serving as a hotspot for third-party devices while simultaneously applying a separate policy to its own traffic; (b) that '124's block/deny approach is the opposite of a "service policy for assisting in control" (a weak argument, since "assisting in control" is broad and the spec defines policy to include admission control); (c) that "monitor or identify" imports a reporting/verification purpose from the title and specification despite the claim not reciting it (prosecution disclaimer risk is low — I found no such disclaimer).

7. Bottom line

US 8,799,451 B2 is vulnerable to § 103 on all three independent claims, but only through multi-reference combinations, and the outcome turns on two facts I could not verify this session:

• Strongest ground: Qualcomm '865 (US 7,239,865, § 102(b)) + Rao (US 2006/0039354, § 102(b)) + Qwest '157 (US 2008/0066157, § 102(b)) — every reference is pre-2008-01-28 published or issued art, so no § 102(e) date risk. This combination supplies the intermediate/forwarding architecture, the differing policy for different networks, and tethering/unauthorized-AP identification, with a clean KSR motivation.
• Strongest supplementary ground (if dates confirm): '124 (US 2010/0034124) + Montemurro (US 2009/0207817) + Chalk '127 (US 2009/0282127) — adds a purpose-built tethering alert for element (v), but each hinges on a pre-2009-01-28 US filing date.
• The patent's own specification admissions about device agents and spoofable device-side reporting materially weaken any argument of nonobviousness over device-side policy art.

Verification steps required before relying on this analysis: (1) pull IPR2026-00466/-00467 Paper 1 and exhibits from PTAB E2E — Google's actual ground list is the authoritative real-world § 103 attack on '451 and its art may be better than anything I reconstructed; (2) confirm filing/priority dates for US 2009/0207817, US 2010/0034124, US 2009/0282127, US 2009/0217065, US 8,381,127, US 2006/0039364, US 2003/0172112 on Patent Center/Global Dossier; (3) retrieve the dependent-claim text (claims 2–13, 16–69) to complete the element-level analysis; (4) confirm the RPX-reproduced claim text against the USPTO full-text claims page, since the Google Patents copy supplied to me was truncated before the claims block.