US 8712371

I'll search for authoritative information on US 8712371, including any 2026 CAFC docket activity.

Let me get the actual claim text and check for any 2026 litigation/docket activity.

Let me check the Justia record for claim text and any litigation, plus confirm no 2026 CAFC activity.

US Patent 8,712,371 — Summary

Note on scope: I ran the requested searches against Google Patents, Justia/FPO family records, and litigation databases. I did not find any Court of Appeals for the Federal Circuit 2026 docket activity tied to US 8,712,371. Searches for "8712371 + CAFC + 2026" returned zero results, and my follow-up litigation query was cut off by a tool-step limit. I state this explicitly rather than inferring that no such appeal exists. Also note: several search hits discuss "the '871 patent" (e.g., an Endo/Mylan Delaware Hatch-Waxman decision). Those are different patents using a shorthand number, not US 8,712,371, and I have not conflated them.

Bibliographic data (per Google Patents, fetched 2026-09-30)

Prosecution chain (from the patent's own Cross-Reference): continuations of 12/950,379 (now US 8,285,249) → continuation of 11/881,460 (now US 7,899,438) → CIP of 11/824,336 (now US 7,945,238, filed June 28, 2007). It belongs to a very large Kajeet family (roughly 20+ co-pending "Feature management of a communication device" cases filed March 6, 2013, plus later continuations such as US 10,555,140; US 11,206,516; US 11,516,629 and, post-assignment, US 12,382,259).

Abstract (verbatim)

"A system and method for the real-time management of a device, and more particularly to the establishment and enforcement of policies or rules associated with the feature or functions that may be performed with the device, such as making and receiving calls, exchanging data, playing games and music, sending and receiving email, accessing web sites, and paying for goods and services. If a child or employee is using the device, there may be a need to regulate how that device can be used and to determine who will pay for what goods or services. In addition to providing all of the features associated with a device, service providers need to be able to establish and enforce rules (policies) regulating how and when that device can be used and who will pay for a good or service requested by the user of the device."

Specification core (architecture the claims sit on)

The disclosure centers on a network-side service manager (20) that, after validation of the mobile station (10) via VLR/HLR or AAA server/home agent, enforces provisioned voice/data policies. For data sessions it routes to a policy enforcement point (PEP) 28 that queries a policy decision point (PDP) 29; the PDP "maintains or stores a list of policies that have been established to control the features and functions of the mobile station 10 and decides, based on those policies, to either accept or reject the service request." On failure the PEP may terminate, redirect/rewrite, or degrade the session, and notify the subscriber, the requester, or an administrator. Enforcement/charging is layered by global rules first, then local (user-level) rules, with wallets (user, administrator, promotional, dynamic) establishing payment precedence and back-up.

Claim coverage — important caveat

I could not retrieve the verbatim issued claim set of US 8,712,371 from an authoritative source in this session. The provided Google Patents text truncates in the Description (ending mid-sentence at "Under this hierarchy,"), and my attempts to pull the numbered claims from Justia/FPO/Google returned either empty claim tables or the claim text of a related family member, US 2011/0081881 A1 (the publication associated with application 12/950,379, now US 8,285,249). Rather than present that text as if it were 8,712,371's claims, I flag the following as an inference from the family and specification, subject to verification:

• Independent system claim. A system for managing, in real time, a communication device used on a communication network, comprising (a) a policy decider storing a list of policies controlling features/functions of the device and automatically deciding to accept or deny a request sent to or from the device based on that list — including at least a content-management policy for content sent, received, or used by the device; and (b) a policy enforcer that communicates the request to the policy decider and enforces the accept/deny decision by taking action consistent with the accepted or denied request.
• Sibling independent claims in this family (per related cases and the file-history record listing 30 claims in the co-pending cases) typically add limitations on: enforcing policies on requests initiated by the device versus by another party; providing notice to the requesting party and/or the subscriber; and multi-wallet precedence/charging rules.

Uncertainty statement: the substance above (policy decider/policy enforcer, accept/deny enforcement, content policy) is corroborated by US 2011/0081881 A1 and by the 8,712,371 specification itself, but the exact claim wording and claim count of 8,712,371 specifically is unverified in this session. Treat the plain-language renderings as approximations, not quote-able claim language.

Litigation (not CAFC, but relevant)

Google Patents' litigation layer (Unified Patents, CC BY 4.0) lists four 2018 California Central District Court matters tied to this family, and a "First worldwide family litigation filed" flag with Darts-ip family ID 40161185:

• https://portal.unifiedpatents.com/litigation/California%20Central%20District%20Court/case/8%3A18-cv-01519
• https://portal.unifiedpatents.com/litigation/California%20Central%20District%20Court/case/8%3A18-cv-01312
• https://portal.unifiedpatents.com/litigation/California%20Central%20District%20Court/case/2%3A18-cv-03899
• https://portal.unifiedpatents.com/litigation/California%20Central%20District%20Court/case/2%3A18-cv-00643

Ownership/security-interest history: Kajeet, Inc. → Silicon Valley Bank security interest (recorded 2021-12-17) → release by secured party (2025-01-21) → assignment to Wireless Management Solutions, LLC (recorded 2025-01-29). This assignment post-dates the 2018 district court matters.

What I could not confirm

1. Whether US 8,712,371 itself has any 2026 Federal Circuit appeal — no docket hit was returned; negative search results are not proof of absence.
2. The exact issued claims of 8,712,371 — see caveat above.
3. Current real-party-in-interest status of the 2018 cases following the 2025 assignment to Wireless Management Solutions, LLC — not verified.

If you want, I can run a follow-up pass specifically on the CAFC docket and CourtListener RECAP for 8:18-cv-01519 / 8:18-cv-01312 to confirm appellate activity and obtain the verbatim claim set.

I'll research litigation involving US patent 8712371 specifically. Let me run several targeted searches.

Let me research the specific case numbers identified and search for additional litigation.

Let me research the remaining cases: the Trend Micro, Norton, and 8:18-cv-01312 matters.

Litigation Involving U.S. Patent No. 8,712,371

Scope note / important caution: The '371 patent at issue here is U.S. Patent No. 8,712,371 B2, titled "Feature management of a communication device," inventors Baker et al., granted April 29, 2014, priority date June 28, 2007, originally assigned to Kajeet, Inc. and (as of January 29, 2025) assigned to Wireless Management Solutions, LLC. My searches for "371" also surfaced a large number of unrelated patents sharing the "371" suffix (e.g., 5,280,371 Honeywell; 5,396,371 NICE; 8,301,371; 9,708,371). I have excluded those — they are different patents and must not be confused with the patent you asked about.

The Google Patents litigation record for US 8,712,371 lists four U.S. district court case numbers in the Central District of California: 2:18-cv-00643, 2:18-cv-03899, 8:18-cv-01312, and 8:18-cv-01519. Below is what I could verify for each, plus related Kajeet enforcement activity.

1. Kajeet, Inc. v. Liminex, Inc. (d/b/a GoGuardian)

Source: Norcal Record report ("Liminex alleged to have infringed Kajeet patents in GoGuardian products"); Patexia docket for Kajeet, Inc v. Liminex Inc.

2. Kajeet, Inc. v. Mobicip, LLC

Sources: Stanford NPE Litigation Database (case/patent records for 8,712,371, 8,774,755, and 8,667,559); UniCourt docket summary; Patexia docket.

3. Kajeet, Inc. v. Qustodio, LLC

Sources: UniCourt docket (Kajeet, Inc. v. Qustodio, LLC); Unified Patents litigation page for case 8:18-cv-01519; Law360 article "Central Calif. Courts Taking It Slow With Patent Eligibility" (March 7, 2019).

4. Case No. 8:18-cv-01312 (C.D. Cal.)

I am flagging this one explicitly as unverified. The number appears in the Google Patents "family has litigation" data for US 8,712,371, but I could not independently confirm the defendant, filing date, or outcome.

Related Kajeet enforcement activity (patents-in-suit including 8,712,371 family members, but '371 assertion not confirmed)

• Kajeet, Inc. v. Norton — U.S. District Court for the District of Delaware. The complaint excerpt I retrieved pleads the '559 patent (8,667,559) against Norton's accused products. I could not confirm the case number or whether the '371 patent was also asserted. (Source: archived D. Del. complaint excerpt.)
• Kajeet, Inc. v. Trend Micro — U.S. District Court, Western District of Texas, Waco Division. Venue/transfer briefing references the '559 Patent and Kajeet's license and settlement agreements. Again, I could not confirm the case number or that '371 was asserted. (Source: W.D. Tex. docket excerpt.)

Post-grant / PTAB activity (context)

I did not find any IPR, PGR, or CBM proceeding directed at U.S. 8,712,371 itself.

For context, PTAB proceedings I encountered involving the same Kajeet patent family concern other patents:

• IPR2022-00001, Gen Digital Inc. (f/k/a NortonLifeLock) v. Kajeet, Inc. — challenged U.S. 8,667,559 ("Feature Management of a Communication Device"), with a revised motion to amend litigated in 2023. This is the '559 patent, not '371.
• A separate IPR referencing "the 371 Patent" (IPR by HTC Corp./HTC America against U.S. 8,301,371 of TeleCommunication Systems) is a different patent and is not relevant to U.S. 8,712,371.

Summary

Confirmed litigation asserting U.S. 8,712,371:

1. Kajeet v. Liminex (GoGuardian) — C.D. Cal. 2:18-cv-00643, filed Jan. 25, 2018 — settled (notice of settlement Apr. 2018).
2. Kajeet v. Mobicip — C.D. Cal. 2:18-cv-03899, filed May 10, 2018 — status pending at last available docket snapshot.
3. Kajeet v. Qustodio — C.D. Cal. 8:18-cv-01519, filed Aug. 24, 2018 — § 101 dismissal without prejudice (Feb. 2019), then dismissed with prejudice Feb. 7, 2020.

Unverified: C.D. Cal. 8:18-cv-01312 (listed for the '371 family by Google Patents, but I could not confirm the defendant or outcome).

Possible but unconfirmed for '371: Kajeet v. Norton (D. Del.) and Kajeet v. Trend Micro (W.D. Tex.) — both appear to be part of the same Kajeet enforcement campaign, but my sources tied them to the '559 patent.

No litigation I could find names the current assignee, Wireless Management Solutions, LLC, as plaintiff — all identified suits were filed by Kajeet, Inc.

Caveat on completeness: Because I was unable to run PACER/CAFC dockets directly and hit search limits, this list may be incomplete. I recommend confirming the Mobicip final disposition, the identity/outcome of 8:18-cv-01312, and whether '371 was asserted in the Norton and Trend Micro matters via PACER/Unified Patents before relying on this as exhaustive.

I'll start by verifying the ODP "no proceedings" result and searching for any IPR/PGR/CBM activity on this patent.

Let me search more specifically for any AIA proceedings naming the '371 patent itself.

The searches so far show IPRs against sibling Kajeet patents (notably '559), not the '371. Let me confirm there's nothing naming the '371 and check the C.D. Cal. litigation and any related PTAB filings.

PTAB / AIA Trial Proceedings — US 8,712,371 ("Feature management of a communication device")

Caveat on sourcing. The canonical list supplied in the "PTAB proceedings on file" block is the USPTO Open Data Portal result: no AIA trial proceedings indexed against US 8,712,371. I ran targeted web searches to catch anything ODP hasn't ingested. My searches surfaced a great deal of Kajeet "Feature management of a communication device" IPR activity — but on the sibling patent US 8,667,559, not on '371. I flag the distinction explicitly below because conflating the two would be the single most dangerous error in this analysis. My search budget was exhausted before I could run the final confirming queries against PTAB E2E and the FWD PDF for the '559 case, so the '559 outcome is described only to the depth I could verify.

Proceedings overview

Zero (0) AIA trial proceedings — IPR, PGR, or CBM — are on file against US 8,712,371. The structured ODP data reports none, and no web source I found names '371 as the challenged patent in any PTAB case; the count across every status category (active / claims invalidated / sustained / settled / institution denied) is therefore 0 / 0 / 0 / 0 / 0, meaning the '371 patent has never been tested at the PTAB and stands exactly as issued — no claim has been canceled, narrowed, or confirmed by the Board, so a defendant gets neither the gift of dead claims nor the hardened-claim inference that a failed IPR would provide.

No proceedings to enumerate

Because the proceeding count is zero, there are no per-proceeding entries to populate. Rather than invent numbers — which the task expressly forbids — I'll instead document the near-miss family activity a defendant will encounter if it searches by title or patent owner, and explain why each is not a proceeding against '371.

IPR2022-00001 — Gen Digital Inc. (f/k/a NortonLifeLock Inc.) v. Kajeet, Inc. — NOT an '371 proceeding

• Type: Inter Partes Review
• Challenged patent: U.S. Patent No. 8,667,559 — a different Kajeet patent that shares the title "Feature management of a communication device" and, per the '559 petition exhibits, the same specification/originating application (Ex. 2012 = App. Ser. No. 13/603,218, which is the application that issued as '371). Source: Docket Alarm, IPR2022-00001
• Filed: 2021-10-01
• Status (verbatim): "Final Written Decision"; Terminated 2023-04-13; Tech Center 2400, Art Unit 2437
• Judge panel: Iftikhar Ahmed, Juliet Mitchell Dirba, Karl Easthom, Meredith Petravick
• Challenged claims: 1–2, 5–15, 18–21, 27–29
• Petition grounds: (1) § 103 obviousness over Putzolu (U.S. Pat. 6,578,076) for claims 1–2, 5–12, 27–29; (2) § 103 over Putzolu in view of Rothman (U.S. Pat. 7,826,835) for claims 2, 7, 8; (3) § 103 over Bhat (Pub. 2005/0021978) for claims 13–15, 18–21. (Source: ai-lab.exparte IPR2022-00001 summary)
• Claim-level disposition: Not verified. I could not retrieve the FWD text. What I can confirm from the public record is that the case ran to a Final Written Decision with a contested Motion to Amend, and that the Board's Preliminary Guidance "disagree[d] with Patent Owner's argument that the specification discloses an alternative where enforcement is performed by a user device." (Quoted in Petitioner's Sur-Reply, 2023-02-16.) Do not treat this as a finding about '371's claims.
• Why it matters anyway: This is the only Kajeet "Feature management" patent the PTAB has actually adjudicated, and the panel's written-description reasoning about the shared specification is the closest thing to a Board read on the common disclosure that '371 also relies on. It is persuasive context, not precedent and not estoppel.

Litigation (not PTAB, but part of the posture)

• Kajeet, Inc. v. Mobicip, LLC, C.D. Cal. 2:18-cv-03899 (filed 2018-05-10) — Kajeet asserted '371, '755, and '559. Source: Stanford NPE Database
• Three further C.D. Cal. cases are recorded in the structured data: 8:18-cv-01519, 8:18-cv-01312, 2:18-cv-00643 (Kajeet as plaintiff).
• Later Kajeet assertions referenced in the '559 IPR record: Kajeet v. NortonLifeLock, D. Del. 1:20-cv-01339-MN, and Kajeet v. Trend Micro, W.D. Tex. 6:21-cv-00389-ADA.
• Ownership: reassigned KAJEET, INC. → WIRELESS MANAGEMENT SOLUTIONS, LLC on 2025-01-29 (recorded via USPTO Assignment). Identical title/priority family continues in US12382259B2 (granted 2025-08-05) and US20250330783A1.

⚠️ Name-confusion trap (do not rely on this case)

Sanho Corp. v. Kajjet Technology International Limited, Inc., Fed. Cir. No. 2023-1336 (decided 2024-07-31), arose from PTAB IPR2021-00886 — but "Kajjet" (a/k/a j5create, a Taiwan peripheral maker) is a different entity from Kajeet, Inc., and the patent there was US 10,572,429 ("Port Extension Apparatus"). It has nothing to do with '371. (CAFC opinion PDF)

Strategic summary

Claims canceled vs. sustained vs. untested. For '371, the answer is unambiguous: everything is untested. No claim of '371 has been canceled, amended, disclaimed, or confirmed by the Board, because no AIA trial has ever been instituted. (I note the patent text as reproduced does not include the claims, so I cannot enumerate them here; I am not asserting any claim number as surviving or dead.) The Board has, however, taken a skeptical view of the shared specification in the '559 IPR — it rejected Kajeet's contention that the spec discloses enforcement performed on the user device, and the petitioner pressed a written-description attack on Kajeet's substitute claims. Because '371 shares that disclosure, that reasoning is live ammunition, but it binds no one and decides nothing about '371.

Estoppel landscape. There is no § 315(e)(2) estoppel running against anyone with respect to '371: estoppel attaches only after an FWD in a proceeding on that patent, and the only Kajeet FWD is on '559. Critically, an FWD on '559 does not estop any ground against '371 — § 315(e) estoppel is patent-specific and claim-specific. So for a defendant now accused of infringing '371, the entire § 102/§ 103 prior-art space (patents and printed publications) remains open, unencumbered by any prior petitioner's estoppel. Conversely, Kajeet has not been able to obtain any Board-backed "hardening" of '371 — the patent's validity rests solely on the original prosecution. The two bars that do matter are statutory, not estoppel: § 315(b) (one year from service of a complaint alleging infringement of '371 — note the 2018 C.D. Cal. defendants are long past this window) and § 315(a)(1) (a previously filed DJ action of invalidity on '371 forecloses IPR).

Pattern signals. The family has attracted one IPR — IPR2022-00001 — filed by an accused infringer (NortonLifeLock/Gen Digital) against the sibling '559, and carried through to an FWD, with Kajeet litigating a Motion to Amend to the end. There is no defensive-aggregator IPR on the family: "Unified Patents" appears in the structured data only as the source of litigation records and in third-party patent-portal pages, not as a petitioner against any Kajeet patent. Kajeet's litigation posture was decidedly offensive (plaintiff in the 2018 C.D. Cal. cluster, plus D. Del. and W.D. Tex. suits), and the 2025-01-29 transfer to Wireless Management Solutions, LLC — an entity taking only the patent rights — is a classic monetization/asset-isolation signal. A plaintiff now asserting '371 is more likely to be monetizing than practicing.

Recommended next steps

• No PTAB activity exists against '371 — say it plainly and plan around the absence. A well-asserted patent usually attracts at least one IPR; the fact that '371 has skated for a decade-plus means either the accused parties settled/never fought, or they were time-barred. That is not evidence of strength.
• If you are a defendant served more than one year ago, an IPR on '371 is almost certainly time-barred under § 315(b). Pivot to (i) ex parte reexamination under 35 U.S.C. § 302 (no § 315(b)-style bar, though it lacks the PTAB's "broadest reasonable interpretation" advantage and estoppel leverage), (ii) district-court § 282 invalidity on the clear-and-conviction standard, or (iii) inter partes reexamination if you were not served.
• If you were served within the last year, you likely still have a window. Because no FWD has ever issued on '371, you face no estoppel risk from the filing, and you are not bound by anything decided in IPR2022-00001. The '559 petition's art — Putzolu (6,578,076), Rothman (7,826,835), Bhat (Pub. 2005/0021978) — is a validated, Board-tested starting kit targeted at the same specification, and none of it is estopped against '371. Pull the '559 FWD (I could not retrieve it here — get it from PTAB E2E at the IPR2022-00001 case page and via the PTAB decisions blob) to see exactly which limitations the panel found or did not find disclosed, and reuse the petitioner's expert framing.
• Mine the '559 record for the written-description/figure issue. Petitioner's Sur-Reply (2023-02-16, available on the IPR2022-00001 docket) alleges Kajeet "doctored Figure 2" to manufacture support for enforcement-on-the-user-device. If '371 claims contain that limitation and its priority depends on the same disclosure, that is a § 112 written-description attack worth developing — but verify against '371's actual claim text, which I do not have in the provided record.
• Track the family, not just '371. Continuations issuing from this priority chain (e.g., US12382259B2 and US20250330783A1) can keep a campaign alive after '371 claims are narrowed; monitor whether the new owner (Wireless Management Solutions, LLC) re-asserts the family.

Bottom line: there is no proceeding number, no institution decision, no FWD, no appeal, and no settlement to quote for '371 — because there has never been an AIA trial on it. I will not manufacture one. Verification I could not complete within this session: the claim-level holding of the '559 FWD and a final E2E sweep for any post-2023 '371 petition; treat those as open items to confirm before filing.

I'll start by gathering what's verifiable about the ownership chain before writing anything.

Good leads. Let me dig into the specific assignment reel/frame and the 2018 litigation.

Significant: Kajeet was the plaintiff in 2018. Now let me pin down the 2025 assignee and the recorded reel/frame data.

US 8,712,371 — Ownership Chain Reconstruction

Patent: US 8,712,371 B2 — Feature management of a communication device
App. 13/603,218 · filed 2012-09-04 · granted 2014-04-29 · priority 2007-06-28 · anticipated expiry 2027-06-28
Source of record for this analysis: Google Patents legal-events feed (https://patents.google.com/patent/US8712371/en) plus litigation dockets. Caveat up front: Google Patents renders the underlying USPTO assignment records but does not expose all reel/frame and correspondent fields in its legal-events widget. I was able to retrieve only one reel/frame for this family (see below) and no assignment correspondent of record for any link. Those cells are marked not retrieved rather than guessed. Verify at the USPTO Assignment Center: https://assignmentcenter.uspto.gov/ (or https://assignment.uspto.gov/patent/index.html — search by patent number 8712371).

Inventors

Pattern note. All six named inventors executed an assignment of interest to Kajeet, Inc. (recorded 2012-09-21 per Google Patents legal events). That recording covers the 2012 continuation filing, not the 2007 priority filing, so it reflects an obligation to assign running forward through the family rather than an employee-exodus event. I found no evidence that any inventor departed Kajeet within 12 months of filing; departure timing is not determinable from the records I retrieved, and I am explicitly not asserting a fire-sale-precursor pattern here. One inventor (Baker) continues to appear as an assignor-inventor on 2020 and 2023 family filings, which is consistent with continuity rather than attrition.

Original assignee

Kajeet, Inc. (originally Bethesda, MD; now 7901 Jones Branch Drive, Suite 350, McLean, VA 22102). Per the Google Patents record the original assignee on the issued patent is Kajeet Inc; the current listed assignee is Wireless Management Solutions LLC.

• Primary line of business: Kajeet is an operating company in managed wireless connectivity, primarily K-12 education — Kajeet SmartSpot® hotspots, LTE-embedded Chromebooks/laptops/tablets, #1 provider of Wi-Fi on school buses in North America, Kajeet Connect fixed wireless, and private LTE/CBRS networks. Historically it ran a kid-focused MVNO cell-phone service with exactly the parental feature-management/wallet functionality claimed here — i.e., the patent reads on Kajeet's own commercial product line, not a paper asset.
• Product embodying the claims: Yes. Kajeet maintains a public "Patents and Licensing" page that expressly lists 8,712,371 among the patents protecting its products and services (https://www.kajeet.com/company/patents-and-licensing).
• Current status: Operating. Kajeet holds active public-sector contracts as of 2025 (e.g., an ESUCC/AEPA cooperative mobile & cellular connectivity award running to 02/28/2027). It is not in bankruptcy. The 2021 Silicon Valley Bank entry below reflects a secured-creditor relationship, not a Kajeet insolvency — the 2023 failure was SVB's, and Kajeet's obligation was released in 2025.

Assignment timeline

Recorded events, chronological, per the Google Patents legal-events feed. All four are post-issuance-chain recordings on this patent. Correspondent is "not retrieved" on every entry — I could not pull the recording attorney/agent of record for this patent from the sources available, so I am not reporting one.

• Executed ~2012-09 / recorded 2012-09-21 — Reel/frame not retrieved

  • Conveyance: Assignment of assignors' interest
  • Assignor: Baker, Matthew Donald; Geller, Steven Ira; Kesser, Douglas Owen; Neal, Daniel John; Politi, Carol Ann; Weintraub, Ben Julian
  • Assignee: KAJEET, INC.
  • Correspondent: not retrieved
  • Context: Initial inventor → company assignment on the 2012 continuation filing (confirms original ownership; nothing unusual).

• Recorded 2021-12-17 — Reel/frame not retrieved

  • Conveyance: Security Interest (Security Agreement)
  • Assignor: KAJEET, INC.
  • Assignee: SILICON VALLEY BANK
  • Correspondent: not retrieved
  • Context: Securitization — Kajeet pledges the patent portfolio as collateral for a venture-debt facility. Standard operating-company financing; not evidence of distress on its own.

• Recorded 2025-01-21 — Reel/frame not retrieved

  • Conveyance: Release by Secured Party
  • Assignor: SILICON VALLEY BANK
  • Assignee: KAJEET, INC.
  • Correspondent: not retrieved
  • Context: Lien release — the security interest is cleared, leaving the patent unencumbered eight days before it is transferred. Classic sequencing for a clean-title sale.

• Executed 2024-10-03 (unverified) / recorded 2025-01-29 — Reel/frame 070046/0381 (unverified — see note)

  • Conveyance: Assignment of assignors' interest
  • Assignor: KAJEET, INC.
  • Assignee: WIRELESS MANAGEMENT SOLUTIONS, LLC (Chevy Chase, MD)
  • Correspondent: not retrieved
  • Context: Transfer out of the operating company to a third-party LLC — the only assignment of title away from Kajeet in the patent's history. This is the link that determines the NPE call.

  Reel/frame caveat (important): the reel/frame 070046/0381 surfaced on an "ASSIGNMENT OF ASSIGNORS' INTEREST / KAJEET, INC. → WIRELESS MANAGEMENT SOLUTIONS, LLC, MARYLAND" record in this patent family (encountered via a sibling family member's Google Patents assignment entry). I could not directly confirm that this same reel/frame covers US 8,712,371 specifically, nor confirm the 2024-10-03 execution date. Treat both as unverified until pulled on the Assignment Center. The 2025-01-29 recorded assignment to WMS is confirmed by the Google Patents legal-events feed for this patent.

Related, but separate from this patent's own chain: the same 2025 WMS acquisition covers sibling family members — e.g., US 12,382,259 B2, granted 2025-08-05 to Wireless Management Solutions, LLC — and a further continuation (application 19/257,188, published as US 2025/0330783 A1) was filed 2025-07-01. So the portfolio changed hands as a group and continued prosecution is being funded by the new owner.

Timeline diagram

timeline
    title Ownership of US 8712371
    2007 : Priority application filed
    2012 : Continuation filed by Kajeet
         : Inventors assign to Kajeet Inc
    2014 : Patent issued 29 April
    2018 : Kajeet sues Qustodio and Mobicip
    2020 : Kajeet sues Cujo LLC
    2021 : Kajeet grants security interest to SVB
    2025 : SVB releases security interest
         : Kajeet assigns patent to Wireless Management Solutions LLC
         : New continuation filed by new owner

NPE / troll-pattern signals

1. Shell-entity transfer — UNCLEAR (leaning not established, but a live watch item).
The patent did move out of an operating assignee into an LLC: KAJEET, INC. → WIRELESS MANAGEMENT SOLUTIONS, LLC, recorded 2025-01-29. But the tells the framework requires for a finding are absent or unverified: the name does not use an IP/Patents/Licensing/Holdings/Ventures suffix; I found no registered-agent service address, no single-member Delaware/Texas registration data, and no evidence WMS has no products. Chevy Chase, MD is immediately adjacent to Kajeet's historical Bethesda, MD base, and at least one inventor (Baker) appears in public assignee profiles tied to both entities — which is at least as consistent with an insider-affiliated portfolio vehicle as with an outsider shell. Insufficient evidence to call it; do not score it as present on naming alone.

2. Known asserter in the chain — NOT PRESENT.
No assignee in this chain matches any of the listed NPE directories (Acacia, Marathon, Intellectual Ventures, IPNav, Wi-LAN, Mosaid/Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, Document Generation Corp, Spangenberg entities). Positive counter-evidence: the Stanford NPE Litigation Database classifies Kajeet, Inc. as "Product company" (Asserter Category 8) for its suits on this family, including US 8,667,559 and US 8,774,755 — i.e., the database that exists to flag NPEs declined to flag Kajeet. WMS does not appear on any NPE list I could confirm.

3. Repeat correspondent across the chain — INSUFFICIENT DATA (not a finding).
I could not retrieve the assignment correspondent of record for any of the four recordings, so recurrence cannot be tested. Do not treat this as negative — it is simply unmeasured. Note for the record that the litigation counsel were consistent across the assertion campaign (Frederick W. Kosmo, Jr. and Hubert Kim of Wilson Turner Kosmo LLP; Corby R. Vowell and Richard A. Wojcio, Jr. as pro hac vice counsel; Brandon C. Fernald as local counsel, e.g. in Kajeet v. Mobicip, 2:18-cv-03899). Litigation counsel consistency is not an assignment-correspondent finding and I am not scoring it as one.

4. Cascading transfers — NOT PRESENT.
There is exactly one transfer of title away from Kajeet in eighteen years (2025-01-29). No chained LLCs, no round-trip, no sub-24-month sequence of successive assignees. The two intervening SVB entries are a lien and its release — not transfers of ownership.

5. Pre-litigation transfer — NOT PRESENT.
The four 2018 C.D. Cal. suits on this family were filed while Kajeet still owned the patent, roughly seven years before the 2025 assignment to WMS. The assignment therefore cannot be characterized as venue/standing engineering for that campaign. (Open item: if WMS files assertion suits in 2026, the 2025-01-29 transfer would retroactively look like a pre-litigation transfer for a new campaign — that is a forward-looking watch item, not a present finding.)

6. Bankruptcy fire-sale — NOT PRESENT.
No Chapter 7 or Chapter 11 proceeding involving Kajeet was found, and Kajeet shows active 2025–2027 public contracts plus a live product line. The SVB entries reflect a secured loan and its consensual release, not a bankruptcy sale.

7. Privateering — UNCLEAR.
The 2025 transfer to an uncharacterized LLC, executed eight days after the lien release and followed by funding of a new continuation, is structurally compatible with privateering (operating company hands the portfolio to a monetizer). But privateering is a finding only when paired with evidence the NPE asserts on the operating company's behalf against its competitors, typically via SEC filings or press. I found no WMS-filed lawsuits and no Kajeet SEC disclosure of such an arrangement. Not established.

8. Defensive aggregator — NOT PRESENT.
The chain does not terminate at RPX, AST, LOT, Unified Patents, or OIN.

Assertion history (for context on signals 1–7)

• 8:18-cv-01519 — Kajeet, Inc. v. Qustodio LLC (C.D. Cal.) — US 8,712,371 pleaded as Exhibit A to Kajeet's opposition to Qustodio's Rule 12(b)(6) motion (filed 2018-12-21). Qustodio ultimately secured dismissal on § 101 ineligibility plus attorneys' fees, and a SLAPP counterclaim (Stradling). The court initially dismissed without prejudice on 2019-02-28, directing Alice-compliant pleading.
• 2:18-cv-03899 — Kajeet, Inc. v. Mobicip, LLC (C.D. Cal.), filed 2018-05-10; Judge Kronstadt. Local-counsel disputes and pro hac vice denials dominate the early docket.
• 8:18-cv-01312 and 2:18-cv-00643 — C.D. Cal. complaints in the same campaign; defendant names not confirmed in the sources retrieved, so I am not naming them.
• 2:20-cv-00253 — Kajeet, Inc. v. Cujo LLC (C.D. Cal.), filed ~2020-01-13, related to 2:18-cv-03899.
• Google Patents flags this family as having "First worldwide family litigation filed" (Darts-ip family 40161185) and lists four 2018 C.D. Cal. cases.

Verdict

Operating-company assertion.

All recorded assertion activity on US 8,712,371 was brought by the operating patent owner itself: Kajeet, Inc. — a shipping product company whose own patents-and-licensing page lists this patent, and which the Stanford NPE Litigation Database categorizes as a "Product company" — sued direct parental-control competitors (Qustodio, Mobicip, Cujo) in C.D. Cal. between 2018 and 2020, pleading this patent as Exhibit A in Kajeet v. Qustodio. No strong NPE signal is documented: there is exactly one transfer of title in eighteen years (KAJEET, INC. → WIRELESS MANAGEMENT SOLUTIONS, LLC, recorded 2025-01-29, executed 2024-10-03 per an unverified family-level reel 070046/0381), preceded only by an SVB security interest (recorded 2021-12-17) and its release (recorded 2025-01-21) — no cascading LLCs, no known asserter, no bankruptcy, no defensive aggregator.

Confidence caveat and required follow-up. This verdict describes the documented assertion period. The 2025-01-29 transfer to an uncharacterized Maryland LLC sits after all known litigation, was sequenced immediately after a lien release, and was followed by the new owner funding a continuation (app. 19/257,188, pub. 2025/0330783 A1) and taking issuance of US 12,382,259 B2 — a profile that would justify reclassifying to NPE — moderate confidence if WMS begins asserting. Before any such call, pull the actual records and fill the two gaps I could not: (a) the recording correspondent/attorney on each of the four entries, and (b) the reel/frame and execution date for the Kajeet→WMS assignment, at https://assignmentcenter.uspto.gov/. If the WMS correspondent matches the correspondent on unrelated high-frequency-plaintiff LLC recordings, that single data point would convert signal 3 from "insufficient data" to a scored finding and would materially strengthen an NPE read.

I'll research the prior-art citations for US 8,712,371. Let me run targeted searches.

The generic searches returned the patent's own text and unrelated search reports. Let me target the "References Cited" sections directly.

I'm getting closer — I found the family's "References Cited" lists on sibling patents. Now let me pull US 8,712,371's own cited references (its PDF / Justia record).

Prior-Art Analysis — US 8,712,371 B2 ("Feature management of a communication device")

Important scope and integrity statement (read first)

The task asks me to "search the USPTO database for the specific patent number 8712371" and "look at each patent citation for 8712371." I must be explicit about what I was and was not able to retrieve, per my operating rules:

• I did confirm the patent's identity and bibliographic data against the Google Patents record for US 8,712,371 B2 (name-matched to 8,712,371; no similar-number substitution was performed). Confirmed identifiers: Application 13/603,218; filed 2012-09-04; priority 2007-06-28; assignee-of-record Kajeet, Inc. (current listed assignee: Wireless Management Solutions, LLC); title match; inventors match. Source: https://patents.google.com/patent/US8712371/en
• I could not retrieve the verbatim "(56) References Cited" box of 8,712,371 itself. The authoritative page text provided to me truncates mid-Description (ending at "Under this hierarchy,") and my search retrievals returned either the specification text or search reports for unrelated patents (e.g., US 11,110,049 and various PCT/EP search reports that have nothing to do with this patent — I am not attributing those to 8,712,371).
• What I can ground is (a) the applicant-admitted prior art inside the 8,712,371 specification itself, and (b) the References Cited lists of sibling family members that share the same specification and inventors (US 11,206,516; US 8,594,619) — these are not verified as 8,712,371's own examiner citations, so I flag them as family-shared/provisional. My tool budget was exhausted before I could pull the 8,712,371 PDF's (56) box or the file wrapper directly.

Net: I will not present a fabricated citation table. Below I separate (1) verified-to-family art, (2) applicant-admitted art, (3) IPR-asserted art, and I mark every anticipation mapping as provisional because the verbatim claims of 8,712,371 remain unverified (as already flagged in the earlier summary section). A § 102 anticipation call requires a single reference disclosing every element as arranged — I cannot make that call rigorously without the exact claim language.

1. Applicant-admitted prior art in the 8,712,371 specification (verified, quote-grounded)

These are discussed in the patent's own BACKGROUND and therefore are admitted prior art usable under § 102(a)/(b) or § 103:

Source: US 8,712,371 specification, BACKGROUND and DETAILED DESCRIPTION (fetched text above), esp. paragraphs corresponding to the "Telcordia" passage.

2. References Cited across the Kajeet family (same spec/inventors — provisional for 8,712,371)

Pulled from the "(56) References Cited" boxes of US 11,206,516 (US11206516.pdf) and US 8,594,619 (US8594619.pdf), which share this specification. Treat as family-shared, not yet verified against 8,712,371's own front page.

2a. U.S. Patent Documents (examiner-cited)

2b. Foreign Patent Documents (family-shared)

Caveat: the family lists above are shared-specification siblings and therefore overlap heavily with what an examiner would cite against 8,712,371 — but 8,712,371 was filed 2012-09-04, before the 2013-03-06 sibling filings, so its examiner citation set may differ. Verify against 8,712,371's own (56) box.

3. IPR-asserted art — Gen Digital (NortonLifeLock) v. Kajeet, IPR2022-00001 (highly relevant to this family)

This PTAB petition challenges sibling US 8,667,559 (same title, same specification, same inventors), so its prior art is directly on point for 8,712,371's disclosure. Source: https://ai-lab.exparte.com/case/ptab/IPR2022-00001/doc/summary/1

Also relevant to claim construction: the IPR record shows prosecution argument that the invention is a "distributed architecture" where the decision is "performed at the server level," construed from the phrase "the decision being based on one or more policies that are stored at the server." This constrains how broadly any 8,712,371 independent claim reads — and thus how far Putzolu/Bhat can go to § 102.

4. Anticipation vs. obviousness — how to read the table above

Under 35 U.S.C. § 102, a claim is anticipated only if a single reference discloses each and every element as arranged in the claim. On the record available:

• No single reference above is a clean § 102 anticipate-the-independent-claim reference. The likely independent claim (per the earlier inferred structure: a policy decider storing policies incl. a content-management policy + a policy enforcer acting on the accept/deny decision) is not fully disclosed in one item:
  • Putzolu discloses the server-decides/client-enforces split but, on the IPR record, is asserted as § 103 art (obviousness), not as anticipation.
  • Rothman discloses mobile feature-policy control but not the full client/server decision-architecture.
  • Bhat discloses policy caching at an enforcement point but not the device-feature/wallet layer.
• The realistic § 103 combinations are: Putzolu (architecture) + Rothman (mobile feature policy); Putzolu + Bhat (local decision caching); and Telcordia (A1) + prepaid-wallet art (McMullin/Fleming/Sokol/Ozaki/Matsumoto) for wallet/charging limitations.
• Any actual § 102 rejections in the file history would most plausibly target dependent claims (e.g., PEP caching → Bhat; administrator-set multi-device plans → Rothman), not the independent claims.

Because the verbatim issued claims of 8,712,371 are still unverified (consistent with my earlier summary section), the claim-number mappings above are approximations, not quote-able claim language. I am not assigning specific claim numbers to § 102 rejections, because doing so would be fabrication.

5. What I could not confirm (explicit)

1. 8,712,371's own verbatim "(56) References Cited" list — not retrieved; the authoritative text I was given truncates before the citation box, and my searches for 8,712,371-specific citations returned the specification text or unrelated search reports. The list in Section 2 is from sibling family members and is provisional for 8,712,371.
2. The verbatim issued claims of 8,712,371 — still unverified (see prior section), so § 102 claim-by-claim anticipation cannot be finalized.
3. Literal-number/discrepancy issues flagged, not auto-corrected:
   • Putzolu reference appears as US 6,578,076 (IPR petition) vs. US 6,578,676 / "Putzold" (family (56) OCR).
   • US 6,364,047 vs. US 6,564,047 (Steele) both appear in the family list.
   • EP 0137884 A1 shows conflicting dates (7/1983 vs. 4/1985).
   • US 5,914,472 inventor OCR'd as both "Foladare et al." and "Holzner et al."
   • Several later citations (6,957,058 onward) are partially truncated in the OCR.
4. Whether any of the 2018 California Central District cases or the 2025 assignment to Wireless Management Solutions, LLC affected the reexam/IPR citation posture — not verified.

Recommended verification path (one query each, which I lacked budget for): the 8,712,371 PDF's (56) box (patentimages.storage.googleapis.com/.../US8712371.pdf), the USPTO PatentCenter file wrapper / IFW "References Cited", and Google Patents' "Cited By" + "Citations" tabs for 8,712,371 specifically. If you want, I can run a focused pass on just the 8,712,371 PDF and file wrapper to replace all Section 2 entries with the patent's own verified citation set and then produce a final § 102/§ 103 chart tied to actual claim numbers.

I'll first try to locate the actual Prior Art / Citations section for this patent, since the fetched text does not contain a numbered reference list.

The fetched page contains no numbered Citation/prior-art table — only the narrative Background. Let me try to retrieve the actual front-page references and any PTAB art for this family, plus known art in the field.

This is a valuable lead — an actual PTAB proceeding against a sibling patent. Let me dig into IPR2022-00001 and related art.

Important threshold note on "the Prior Art section of this page"

The Google Patents page as fetched for US 8,712,371 contains no itemized Citation / "References Cited" / "Prior Art" table. The fetched text terminates in the Description (mid-sentence at "Under this hierarchy,"), and the only prior-art content actually present is the prose Background — which itself identifies and describes a set of prior systems and publications. I am therefore doing two things, and labeling them separately:

1. Admitted prior art (AAPA) from the patent's own Background — the only "Prior Art section" content that exists in the supplied record. This is usable in a §103 analysis. (MPEP §2129; K/S HIMPP v. Hear-Wear Techs. — applicant-admitted prior art may be relied on for obviousness.)
2. Art located via search — principally the PTAB record in IPR2022-00001, Gen Digital Inc. (f/k/a NortonLifeLock) v. Kajeet, Inc., which challenged US 8,667,559, a sibling in the same family and specification ("Feature management of a communication device"). That record is the single most probative external evidence of how a skilled challenger maps this specification onto art, and it names the references I use below.

I did not verify the full text of any reference in this session, and — as flagged in the previously generated sections — I still do not have the verbatim issued claims of 8,712,371. The claim-scope reconstructions below are the same approximations used earlier ("policy decider" / "policy enforcer" / content-management policy), and I mark them as such. Do not treat them as quotable claim language.

1. Effective filing date and the prior-art window

Per the patent's Cross-Reference, US 8,712,371 (app. 13/603,218, filed 2012-09-04) is a continuation of 12/950,379 → continuation of 11/881,460 (now US 7,899,438, filed 2007-07-26) → CIP of 11/824,336 (filed 2007-06-28). Google Patents lists the priority date as 2007-06-28 and anticipated expiration as 2027-06-28.

Two consequences matter for §103:

• The presumptive critical date is 2007-06-28, but the CIP taint is a live issue. Subject matter first added in 11/881,460 gets only the 2007-07-26 date; subject matter added even later (e.g., the "wallet" discussion appears fully developed only in the later filings) gets no earlier date. A challenger should chart each claim limitation to the earliest supporting disclosure. This matters less than it usually would because the gap is only ~28 days, but it is the correct analysis and it is the same priority-attack theory that was actually run in IPR2024-00981 against a different patent (the Board/patent owner there litigated the priority chart and the effective date of new matter — see the petition excerpt at ptacts.uspto.gov).
• Practically, any reference published or filed before mid-2007 is fair game under §102(a)/(b)/(e).

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

Consistent with the level of skill urged in the IPR records discussed below: a bachelor's degree in computer science, computer/electrical engineering, or equivalent, plus ~3 years of experience in network policy management, mobile data services, or telecommunications charging/billing systems, with graduate education or significant work experience substitutable. This is a mature, well-populated art — a point that cuts strongly in favor of obviousness (predictability of results, finite number of known solutions).

3. The reference set

Note on Telcordia. The Background's own characterization of Telcordia is unusually damaging: it concedes a system that (i) operates in real time, (ii) applies parental controls, (iii) restricts spending parameters, and (iv) does so for a download/content service. That is close to the asserted core of the '371 disclosure, and it is the applicant's own admission.

4. Ground 1 — Putzolu alone: the architecture claim

Target: the independent system claim as reconstructed (policy decider storing a list of policies controlling features/functions and automatically rendering accept/deny decisions on requests to/from the device; policy enforcer communicating the request and enforcing the decision).

Obviousness here is essentially a single-reference, all-elements case if the independent claim is architecture-level. The only genuine gap is the application (a telephone/mobile content context rather than generic network resources), which Ground 2 closes.

Caveat and counter-argument. Putzolu is a data-networking policy framework, not a consumer mobile feature-control product. Kajeet's strongest response is that the claim's purpose — regulating a child's or employee's phone use and who pays — imports a different problem than quality-of-service/access control in an IP network. Under KSR, that is a weak argument when the field is one of design choice, but it is the argument to expect.

5. Ground 2 — Putzolu + Rothman: the mobile-feature and content-policy claims

This is the primary obviousness ground and the one with the clearest motivation-to-combine story.

• Rothman supplies the entire mobile-telephone application layer: device features (picture-taking, text messaging), an administrator-placed plan, and fleet/group management of multiple phones.
• Putzolu supplies the server-side decision / client-side enforcement split.
• The combination yields: a server storing policies for controlling a mobile device's features and content, automatically deciding accept/deny, and an enforcer acting on the decision.

Motivations a POSITA would have had (KSR + MPEP 2143):

1. Known technique applied to a known, ready-for-improvement device (MPEP 2143.A: combining prior-art elements per known methods to yield predictable results). A POSITA seeking to impose administrator controls on a mobile handset would naturally adopt the dominant, off-the-shelf client/server policy paradigm rather than invent one.
2. Design choice / simplification: removing policy interpretation and the policy store from the handset is an obvious engineering choice with the recognized benefit that the user cannot tamper with or inspect the policies — the identical benefit the '371 applicant relies on. (This was argued expressly in the IPR record: "policies are not accessed by the user device.")
3. Art-recognized problem: administrators (parents, employers, schools) wanting to constrain feature use is the very problem the '371 Background concedes existed in the prior art; both references address the same family of problems.
4. Finite, predictable solutions: centralized policy decisioning with distributed enforcement was one of a small number of known architectures.
5. Analogy: both references are in the same field of endeavor (network/service policy management), satisfying In re Bigio / In re Clay.

Reasonable expectation of success: high. No new hardware, protocol, or network element is required; the '371 specification itself describes implementing the invention with standard IS-41/IS-771/IS-826 triggers and standard PEP/PDP roles.

Teaching away: none identified. Rothman affirmatively invites extension to additional controllable features, which is the opposite of teaching away.

6. Ground 3 — Putzolu + Rothman + Bhat: the "caching / updated-decision / inbound-request" claims

For any claim in the '371 set that recites (or that Kajeet argues confers patentability by reciting) local storage of a policy decision, receipt of an updated decision, or enforcement on a request that originates from a third party rather than the device:

• Bhat teaches a PEP that caches a decision and later acts on an updated policy decision — squarely on point.
• The specification's own discussion of requests "initiated by another device seeking to communicate with the user's device" (e.g., an inbound text message denied by policy) is a routine application of the same decision/enforcement loop; Putzolu's policy client handles requests arriving from either direction.

Motivation: caching decisions at the enforcement point is a textbook latency/backhaul-traffic optimization (Bhat's own stated purpose), and a POSITA would apply it to a mobile policy system to avoid a server round-trip on every SMS/MMS/call. Predictable result, no teaching away.

7. Ground 4 — Admitted prior art (Telcordia + prepaid/subaccount/affinity) + Putzolu + Rothman: the charging- and wallet-adjacent claims

If 8,712,371's claims include any charging, who-pays, wallet, balance, or multi-account precedence element (the '371 family is titled "feature management," but the specification and the asserted sibling claims blur into billing), the Background concedes most of the substance:

• Telcordia — real-time parental controls over paid/premium downloads, limiting a child's spending within parameters. This is the closest admitted art to any "content policy + real-time spend control" limitation.
• Stored-value accounts funded by credit card/EFT — admitted.
• Corporate master account with subaccounts charged to departments/phones — i.e., per-transaction allocation of charges to different funding sources tied to different devices/users, admitted.
• Affinity accounts / group promotions — i.e., a promotional pool of value applied to a group before ordinary charges, admitted. This is functionally a promotional wallet in all but name.
• Rollover minutes, automatic refill, low-balance alerts, unlimited packages — admitted, and collectively establish the ordinary skill level around balance tracking and threshold notification.

Combination logic: Take Telcordia's real-time, parameter-limited parental spend control (admitted, and squarely in the same field); add Putzolu's decision/enforcement split to move the control decisions to a network server; add Rothman's administrator-defined mobile feature policies and multi-device plans. A POSITA would be motivated by the Background's own framing of the problem — guaranteeing that emergency/key services remain available while preventing overspending — and by the admitted shortfall of alert-only systems (which "do[] not actually limit usage of the service").

Where this ground is weakest: if the claims recite a specific multi-wallet order of precedence with back-up payment reverting between wallets (the "Grandma's wallet" / admin-wallet-covers-user-wallet construct), Ground 4's references show the components (multiple funding sources, promotional pools, precedence) but the record I have does not show a single reference or an articulated combination expressly teaching automatic reversion to a secondary wallet when the primary designated wallet is exhausted. That is the most defensible non-obviousness foothold in the family, and a challenger would want a dedicated prepaid/electronic-wallet reference (or a second tier of art on hierarchical payment sourcing) to close it.

8. Limitations most likely to survive, and what art would be needed

9. Secondary considerations

• Long-felt need / failure of others is available to Kajeet: the Background itself frames a recognized, unmet need (prepaid exhaustion cutting off emergency calls; alert-only systems requiring manual intervention). This is the strongest Graham factor for the patentee.
• Commercial success (the Kajeet consumer service, ~43 US patents, school-district deployments) could be argued, but nexus is the problem: the products embody the whole Kajeet platform, not the claimed subject matter, and the specification attributes nothing unexpected to the claims.
• Copying / industry praise — not in evidence.
• Weighing against the patentee: the enablement-by-conventional-elements posture of the specification (standard IS-136/IS-95 air interfaces, IS-41/IS-771/IS-826 triggers, standard PEP/PDP roles) supports that the claimed advance is arrangement, not invention. The §101 ruling in Kajeet v. Qustodio, No. 8:18-cv-01519 JAK (C.D. Cal. Feb. 28, 2019) — where the defendant analogized the asserted claims (including 8,712,371) to Bascom v. AT&T as well-known and conventional — is consistent with, though not dispositive of, a §103 vulnerability.

10. Bottom line

1. On the reconstructed architecture claims, US 8,712,371 is likely obvious under §103. Putzolu (US 6,578,076) supplies every structural element — server-side policy decisioning plus client-side enforcement of a decision made without local policy access. Rothman (US 7,826,835) supplies the mobile-device, administrator-plan, multi-phone feature-control application and closes the field-of-use gap. Motivation: the two references are in the same field and address the same administrator-control problem the '371 Background concedes; the combination is a predictable application of a known technique to a known, improvement-ready device (KSR; MPEP 2143.A).
2. Claims adding cached/updated decisions or third-party-initiated requests are also obvious over Putzolu + Rothman + Bhat (US 2005/0021978 A1).
3. Charging/balance claims are strongly exposed to the patent's own admitted prior art, especially Telcordia Converged Real-Time Charging (real-time, parameter-limited parental controls over premium downloads) combined with the admitted subaccount/affinity/auto-refill art, viewed through Putzolu's decision/enforcement split.
4. The most defensible limitations are the specific multi-wallet precedence-with-automatic-back-up mechanism and the device-independent dynamic wallet, plus possibly location-gated policy override — none of which is met by the references I could confirm.
5. Direct, high-value corroboration exists: the PTAB instituted and reached a final written decision in IPR2022-00001 against sibling US 8,667,559 on precisely these reference combinations. Because the family shares one specification, a petitioner challenging 8,712,371 would run a substantially parallel case. I could not verify the outcome of that FWD or whether any claim of the '559 survived; do not assume invalidation.

11. Verification steps I recommend before relying on any of the above

1. Pull the verbatim issued claims of 8,712,371 from USPTO PatentCenter/Public PAIR (app. 13/603,218) — this is the single biggest gap; everything above is element-level analysis against a reconstructed claim.
2. Retrieve the "References Cited" front-page list and the file-wrapper citations for 8,712,371, which I could not obtain in this session; the examiner's own art is the cheapest obviousness starting point and its absence here is a data gap, not a finding.
3. Confirm the title, filing date, and pertinence of US 6,578,076 (Putzolu) and US 7,826,835 (Rothman) from full text, and identify Choudhary's publication number.
4. Confirm the outcome of IPR2022-00001 (Paper 50+ / Final Written Decision of Apr. 13, 2023) and check whether the Qustodio or Gryphon litigations generated §103 contentions or expert reports naming additional art.
5. Run the family-wide priority chart (which limitations entered at 11/824,336 vs. 11/881,460) to fix the critical date per limitation.