US 7899438

I'll verify the patent data and check for any 2026 CAFC activity.

Let me try to locate the actual claim text and check for 2026 appellate activity.

Two more targeted checks on claim language and any appellate docket activity.

Retrieve status first

I could not access a USPTO records system or a CAFC docket database directly; my tooling is web search only. I ran three targeted searches on the literal string 7899438 (plus party names and claim-language queries). Findings below are grounded in the authoritative full text you supplied, corroborated by Google Patents, uspto.report, Justia, and Kajeet's own patent list. Where only inference is available, I say so explicitly.

Bibliographic summary — US 7,899,438

Source: https://patents.google.com/patent/US7899438/en ; corroborated by https://uspto.report/patent/grant/[7,899,438](/patent/7899438) and https://www.kajeet.com/company/patents-and-licensing

Abstract (authoritative text as issued)

"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. Modern communication devices are capable of many things, including making and receiving calls, exchanging data, playing games and music, sending and receiving email, accessing web sites, and paying for goods and services. Depending on who is using the communication device, such as a child or an employee, there may be a need or desire to regulate how that communication 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."

(Identical to the "Brief Description of the Invention" in the specification.)

Independent claims — ⚠️ cannot be verified from authoritative text

Explicit uncertainty flag: the authoritative full text you supplied contains the abstract, drawings description, and detailed description, but the claims section is not present in the material I hold, and none of my searches returned the granted claim set for 7,899,438 specifically. Claim text found in search results belonged to unrelated patents (e.g., US 10,410,201; US 10,064,033; US 11,481,756). I am therefore not going to reproduce any claim language as if it were verbatim. Anything below is a specification-grounded inference of the claimed subject matter, not a quotation.

What the specification supports as the likely independent-claim scope (verify against the official claim set before relying on this):

1. Network-side method/system for real-time feature management (FIGS. 1–2). Receiving an origination/service request from a mobile station (10) at a base station (12) and O‑MSC (14) or O‑PDSN (25); validating the device against VLR/HLR (16, 18) or AAA server (27)/home agent (26); authenticating the subscriber by MDN and/or MSID; triggering a service manager (20) that consults a policy decision point (PDP, 29) holding provisioned policies and enforcing them at a policy enforcement point (PEP, 28); and, on policy failure, notifying and taking an action such as terminating, redirecting/rewriting, or degrading the session. Likely recites feature management meaning blocking a feature entirely, capping usage over a period, or restricting usage to a time window.

2. Rate-and-charge / wallet-selectivity mechanism. If the session is allowed, rating and charging the transaction according to an order of precedence: global rules first, then local (user-level) rules, with intervening tiers for promotional and dynamic wallets; and choosing among a user wallet, administrator wallet, promotional wallet, or dynamic wallet, including backup funding when a designated wallet is depleted (two-decision structure noted in the spec: "Global rules and local rules can be applied in order, so as to result in two separate decisions").

3. Administrator-configured policy apparatus (FIGS. 3–5) — the Contact Manager (30) / feature-and-time management pages allowing an administrator to set allowed/blocked number lists, per-contact wallet assignment, an Override Restrictions function (40), and per-feature settings for downloads (52), feeds (54), mobile web (56), picture messaging (58), and instant messaging (60).

Caution: the wallet-allocation subject matter overlaps a different Kajeet-family patent (US 7,945,238), and features may be split across the family rather than recited in the '438 independent claims. One search result (portal.unifiedpatents.com) displayed an abstract about "the allocation of electronic wallets" under a US-7899438-B2 heading; that abstract is not the '438 abstract and appears to belong to sibling US 2009/0006200 A1. Treat it as a metadata conflation, not as '438 content.

Litigation / PTAB signal (family level)

Google Patents lists these under "Family has litigation," so they are family-level associations, not confirmed to name US 7,899,438 as the asserted patent:

• PTAB IPR2023-00178 (Petitioner: Unified Patents) — status: Settlement. https://portal.unifiedpatents.com/ptab/case/IPR2023-00178
• W.D. Tex. 6:20-cv-00705; D. Del. 1:19-cv-02371 and 1:19-cv-02370; C.D. Cal. 2:20-cv-00253

No CAFC 2026 docket activity involving this patent, Kajeet, or Wireless Management Solutions was found. My search for 2026 Federal Circuit appeals returned an empty result set. Absence of results here is weak evidence, not proof — a docket-only database (PACER/CAFC) search would be needed to state this definitively.

Confidence assessment

• High confidence: title, application number, filing date, issue date, publication number, inventors, original assignee, current assignee, abstract, and the specification content.
• Moderate confidence: priority date 2007‑06‑28 and the CIP relationship to Ser. No. 11/824,336 (both flagged as assumptions by Google Patents itself, and the CIP reference appears in the patent's own Cross‑References section).
• Low / unverified: the independent-claim wording and count; the exact relationship of each listed litigation matter to this specific patent. I have no authoritative claim text for 7,899,438 and will not fabricate one.

I'll research litigation involving US 7899438. Let me run several targeted searches.

Let me search for more specifics on the cases asserting the '438 patent.

Let me pin down the Delaware cases and the Trend Micro district court action.

Litigation involving U.S. Patent No. 7,899,438 (the "'438 Patent")

Caveat on scope: The '438 Patent is one member of a large Kajeet patent family (the '559, '371, '612, '249, '433, etc. patents share the same specification). Many Kajeet suits asserted several family members, so I have filtered below to matters where I could confirm the '438 Patent itself was actually asserted. Numbering and dates are reported exactly as they appear in the sources; where I could not confirm a detail, I say so rather than guess.

Confirmed litigation asserting the '438 Patent

1. Kajeet, Inc. v. Gryphon Online Safety, Inc.

• Plaintiff: Kajeet, Inc.
• Defendant: Gryphon Online Safety, Inc.
• Jurisdiction: U.S. District Court for the District of Delaware (Judge Maryellen Noreika)
• Case No.: 1:19-cv-02370-MN
• Filed: December 30, 2019
• Patents asserted: U.S. 8,667,559 ('559) and U.S. 7,899,438 ('438)
• Outcome / status: On March 1, 2021, the court granted Gryphon's Rule 12(b)(6) motion to dismiss the direct and indirect infringement claims (with leave to amend) but denied the § 101 eligibility challenge as to both the '559 and '438 Patents (eligibility could not be resolved at the pleadings stage). The case was later stayed on June 10, 2022 pending the PTAB's final written decision in the IPR proceedings; the docket is marked STAYED, CLOSED, terminated February 27, 2024.
• Sources: https://www.ded.uscourts.gov/opinion/kajeet-inc-v-gryphon-online-safety-inc ; https://www.courtlistener.com/opinion/[9634417](/patent/9634417)/kajeet-inc-v-gryphon-online-safety-inc/

2. Kajeet, Inc. v. Cujo LLC

• Plaintiff: Kajeet, Inc.
• Defendant: Cujo LLC
• Jurisdiction: U.S. District Court for the Central District of California
• Case No.: 2:20-cv-00253
• Filed: 2020 (complaint analyzed in connection with this docket; I did not independently confirm the exact filing date — NPE database shows the venue and number but no date)
• Patents asserted: U.S. 8,667,559 ('559) and U.S. 7,899,438 ('438). The complaint asserts claim 27 of the '438 Patent (a "policy decider" / "policy enforcer" system claim) and expressly reserves the right to assert additional claims.
• Accused products: Cujo's "Smart Firewall" products/services and the "AI Platform for Network Operators" (Compass) products
• Outcome / status: Settlement/dismissal reported in the NPE Litigation Database listing; I could not confirm a final disposition order or date from the sources retrieved.
• Sources: https://npe.law.stanford.edu/patent/7899438 ; complaint analysis at https://ai-lab-cl-prod.azurewebsites.net/case/dct/cacd/2:20-cv-00253/doc/analysis/1

3. Kajeet, Inc. v. Trend Micro Inc. (district court)

• Plaintiff: Kajeet, Inc.
• Defendant: Trend Micro Inc.
• Jurisdiction: U.S. District Court for the Western District of Texas (Waco); a § 1404(a) transfer motion to the Northern District of California was briefed (the court opinion I retrieved analyzes the convenience factors). I could not confirm the W.D. Tex. case number or the exact filing date from the sources retrieved.
• Relevance to the '438 Patent: Trend Micro's subsequent IPR petition (below) challenged claims 1, 2, 3, 6, 10, 27 and 33 of the '438 Patent, which strongly indicates the '438 Patent was among the patents-in-suit against Trend Micro.
• Source: https://www.courtlistener.com/opinion/[10213620](/patent/10213620)/kajeet-inc-v-trend-micro-inc/

Related post-grant proceeding (PTAB, not district-court litigation)

Trend Micro Inc. v. Kajeet, Inc., IPR2023-00178 (PTAB)

• Petitioner: Trend Micro Inc. | Patent Owner: Kajeet, Inc.
• Patent challenged: U.S. 7,899,438 — claims 1, 2, 3, 6, 10, 27, 33
• Filed: November 10, 2022
• Institution decision: May 12, 2023
• Status: Terminated – Settled (decision dated September 1, 2023; panel: Dirba, Easthom, Ahmed)
• Sources: https://services.patexia.com/lawsuits/Trend-Micro-Inc-v-Kajeet-Inc-id-[183366](/patent/183366) ; Google Patents PTAB link https://portal.unifiedpatents.com/ptab/case/IPR2023-00178

Matters I examined but could NOT confirm as asserting the '438 Patent

• Kajeet, Inc. v. NortonLifeLock Inc., 1:19-cv-02371-MN (D. Del.), filed 12/30/2019 — companion to the Gryphon case. The Delaware opinion expressly states in footnote 1: "The '438 Patent is not asserted against Norton." So although some secondary summaries describe the Gryphon/Norton complaint as asserting both the '559 and '438 Patents, the court record indicates the '438 Patent was asserted only against Gryphon.
• Kajeet, Inc. v. Qustodio, LLC, 8:18-cv-01519 (C.D. Cal.), filed 08/24/2018 — asserted U.S. 8,712,371, 8,630,612 and 8,667,559. The '438 Patent appears only as Exhibit M to Kajeet's claim-construction brief, not as an asserted patent. Dismissed with prejudice 02/07/2020.
• Kajeet, Inc. v. Mobicip, LLC, 2:18-cv-03899 (C.D. Cal.), filed 05/10/2018 — asserted U.S. 8,712,371, 8,774,755 and 8,667,559 (no '438).
• Other W.D. Tex. Kajeet dockets tied to the family (e.g., Kajeet v. JAMF Software, 6:20-cv-00302; Kajeet v. Lightspeed Solutions, 6:20-cv-00203; Kajeet v. Asavie Technologies, 6:20-cv-00705, filed 07/31/2020, closed 10/07/2020; Kajeet v. CenturyLink/Lumen, 6:21-cv-00705, filed 07/07/2021) appear in family-level listings, but I could not verify from the retrieved sources that the '438 Patent specifically was asserted in them.

Related PTAB challenge to a sibling patent (context only)

• Gen Digital Inc. (f/k/a NortonLifeLock Inc.) v. Kajeet, Inc., IPR2022-00001, filed October 1, 2021 — challenges U.S. 8,667,559 (not the '438 Patent).

Bottom line

The only confirmed district-court assertions of U.S. 7,899,438 that I could verify are: Kajeet, Inc. v. Gryphon Online Safety, Inc. (D. Del. 1:19-cv-02370), Kajeet, Inc. v. Cujo LLC (C.D. Cal. 2:20-cv-00253), and the Kajeet v. Trend Micro W.D. Tex. action (case number unconfirmed), which spawned IPR2023-00178 — a PTAB proceeding that was terminated by settlement on September 1, 2023, without a final written decision on the merits. In all of these, the plaintiff/patent owner was Kajeet, Inc.; ownership of the '438 Patent was later assigned to Wireless Management Solutions, LLC (recorded January 29, 2025), and I found no litigation filed by that assignee.

Two items I want to flag explicitly as unverified: the exact filing date in Kajeet v. Cujo and the W.D. Tex. case number in Kajeet v. Trend Micro. I did not want to fill those gaps with a plausible-looking number. If you need them pinned down, PACER dockets for C.D. Cal. 2:20-cv-00253 and the W.D. Tex. Trend Micro docket would resolve both.

I'll start by verifying the structured data against what the patent record itself surfaces, then dig into the one proceeding the full-text block hints at.

The patent's own Google Patents record flags a PTAB case — IPR2023-00178, petitioner Unified Patents, marked "(Settlement)". Let me chase the docket details.

Important conflict to resolve: the Google Patents record attributes IPR2023-00178 to "Unified Patents" as data source, while Patexia names Trend Micro Inc. v. Kajeet, Inc. I need to confirm which patent that IPR actually targets.

Proceedings overview

Canonical count on US 7,899,438: zero AIA trial proceedings. The structured PTAB block for this patent returns an empty set from the USPTO Open Data Portal, and that is the operative number. One family-level flag does appear in the patent's own Google Patents record — IPR2023-00178 — but the corroborating public data ties that number to a different Kajeet patent and a different petitioner, so it should not be booked as a challenge to '438 without E2E verification (details below). Bottom line for a defendant: the claimed invention has never been tested at the PTAB — not once. There is no Final Written Decision canceling a single claim of '438, and therefore no claim of '438 can be called dead. The defensive posture is the opposite of hardened: the patent is unblemished but unproven, sitting in a large continuation family with a 2025 assignment to a monetization entity, which means an IPR-based defense is fully available and unencumbered by estoppel.

Flagged item requiring verification — IPR2023-00178 — Petitioner disputed (reported as Trend Micro Inc.) v. Kajeet, Inc.

• Type: Inter Partes Review (reported)
• Filed: 2022-11-10
• Status: Terminated-Settled (Patexia). The Google Patents record for US 7,899,438 lists this proceeding with the parenthetical "(Settlement)", consistent with the Patexia status. Plain English: the parties settled and the Board terminated before any Final Written Decision.
• Judge panel: Juliet Mitchell Dirba, Karl D. Easthom, Iftikhar Ahmed (reported). Patexia lists Dirba as the judge writing the decision — in a settled case that would be the termination decision, not an FWD.
• Petition grounds: Claims reported as challenged: 1, 2, 3, 6, 10, 27, 33. The specific references and the § 102 / § 103 allocation are not in the public record I could retrieve — I will not guess at art that was never established.
• Institution decision: Reported institution-decision date of 2023-05-12. Patexia's "Claims Instituted" field is blank, which is ambiguous — it can mean institution was denied, or simply that the field was not populated before the case settled. I cannot tell you which, and I am not going to assert one.
• Final Written Decision: None issued. The case terminated 2023-09-01 without an FWD. No claim of any patent was canceled or sustained in this proceeding.
• Settlement / termination: Terminated by settlement, 2023-09-01. Terms are not public — PTAB settlements under 35 U.S.C. § 317(b) are filed as confidential agreements; only the fact of termination is on the record.
• Appeal: No. There is no FWD to appeal, and no Federal Circuit docket exists for this proceeding.
• Defensive value: Essentially nil for a '438 defendant — and potentially misleading. Two independent reasons: (1) the proceeding produced no claim-level holding, so it establishes nothing about validity; and (2) the reported caption (Trend Micro v. Kajeet) and the surrounding record point to a sibling Kajeet patent, not '438.

Why I am flagging rather than reporting this as an IPR on '438:

1. The "petitioner" on the Google Patents page is a data credit, not a party. The entry reads "Petitioner: 'Unified Patents PTAB Data' by Unified Patents is licensed under a Creative Commons Attribution 4.0 International License" — the identical pattern used for the district-court entries on the same page ("Source: District Court ... Unified Patents Litigation Data"). Unified Patents is the data licensor here, not the petitioner. Do not brief this as a Unified Patents challenge.

2. The independent source names a different petitioner and a different case posture. Patexia reports IPR2023-00178 as Trend Micro Inc. v. Kajeet, Inc., which pairs with the co-pending W.D. Tex. litigation Kajeet, Inc. v. Trend Micro Inc., No. 6:21-cv-00389-ADA (filed 2021-04-21, Judge Alan D. Albright), where Kajeet's asserted exhibit was US 8,667,559 — the "Feature management of a communication device" sibling, not '438.

3. The Google Patents litigation block is Darts-IP family-level data (family 40161185). Kajeet's family contains dozens of "Feature management of a communication device" continuations, so a PTAB case against any family member will surface on the '438 page. Family-level surfacing is not patent-level targeting.

4. The claim numbers don't help. I do not have the issued claim set of '438 in the record provided (the supplied text is the description, not the claims), so I cannot confirm or refute that 1, 2, 3, 6, 10, 27, 33 are '438 claims. Claim 27 and claim 33 existing is at least plausible for a Kajeet feature-management patent, which is exactly why this needs a primary-source check rather than an inference.

Verification step (do this before relying on anything above): pull the proceeding directly from PTAB E2E at https://ptacts.uspto.gov/ptacts/ and read the Notice of Filing Date Accorded, the petition's mandatory notices (§ 42.8(b)(1) real party-in-interest, which names the true petitioner), and the cover-page patent number. The Unified Patents portal mirror is at https://portal.unifiedpatents.com/ptab/case/IPR2023-00178. If that cover page reads 8,667,559, this entry is a sibling-patent case and '438's PTAB count stays at zero.

Strategic summary

Claim status on '438: entirely UNTESTED. There is no IPR, PGR, or CBM that reached a Final Written Decision on US 7,899,438. No claim has been canceled. No claim has been confirmed. Nothing has been narrowed by the Board. Every claim of the patent — independent and dependent alike — stands exactly as issued on 2011-03-01, subject only to whatever the district courts have done (and I found no invalidity judgment; the litigation hits on the NPE database and the Unified Patents litigation portal are assertion-side cases: Kajeet, Inc. v. Cujo LLC, 2:20-cv-00253 (C.D. Cal.); D. Del. 1:19-cv-02370 and 1:19-cv-02371; and W.D. Tex. 6:20-cv-00705). If a demand letter cites claims 1–33 or any subset, you cannot answer "those claims are already dead." You have to do the work.

Estoppel landscape: wide open. Section 315(e)(2) estoppel attaches only to a petitioner that obtains a Final Written Decision. IPR2023-00178 settled pre-FWD, so no estoppel arose from it for anyone — not for Trend Micro, not for Kajeet's litigation adversaries. And because no IPR against '438 has ever reached institution-and-FWD, there is no § 315(e)(2) bar on any ground against '438. A defendant today can raise any § 102 or § 103 ground, on any reference, including printed publications, patents, and — subject to § 311(b) — prior public use or on-sale art in the form of a patent or printed publication. The practical corollary: your best art is not constrained by what some prior petitioner already tried, because no one has tried. One important vehicle limit: '438 has an effective priority date of 2007-06-28 and a filing date of 2007-07-26, so it is pre-AIA — PGR is unavailable (35 U.S.C. § 321 applies only to first-inventor-to-file patents), and the CBM transitional program sunset on 2020-09-16, so no new CBM petition can be filed. IPR under § 311 is your only AIA trial vehicle, and it is fully available.

Pattern signals. (a) Petitioner concentration: the only trend is that Kajeet has drawn repeat challengers — Gen Digital Inc. (f/k/a NortonLifeLock) filed IPR2022-00001 and Trend Micro filed IPR2023-00178, both against the '559 sibling — so there is an established, and apparently effective, pattern of defendants opening IPR fronts against this family. (b) Patent owner posture: Kajeet litigated aggressively and defended the family with a contingent motion to amend in the '559 IPR (revised motion to substitute claims 31–32, 35–45), a signal that this family is defended with real resources and that Kajeet understands the PTAB threat. (c) Defensive aggregator: not present — the "Unified Patents" string on the Google Patents page is a data license, not a Unified Patents petition (see above). Do not build a Unified Patents narrative on this record. (d) Ownership shift — the most important signal: the patent moved from Kajeet, Inc. to Wireless Management Solutions, LLC, assignment recorded 2025-01-29 (following the 2024-10-03 and 2025-01-21 secured-party releases to Kajeet). The family has roughly 30+ related continuations, and the adjusted expiration runs to 2029-10-05 — four more years of runway. That combination — un-invalidated claims, a fresh monetization assignee, no estoppel, and a thick continuation family the owner can pivot to if you knock out '438 — is the key risk finding. The '438 patent is a soft target with a hard backup.

Recommended next steps

There is no PTAB activity to hand you. State that plainly to your client: the ODP canonical list is empty, and the one family-level flag (IPR2023-00178) settled without an FWD and, on the better public record, targeted US 8,667,559 rather than '438. The absence of any IPR on '438 is itself the signal — this patent has been asserted in at least four district-court actions since 2019 yet no one has ever challenged it at the Board. Either nobody has tried, or somebody looked and chose not to. Both possibilities are worth a two-week prior-art kill study before you decide.

1. Verify the flagged proceeding at the primary source first. Pull IPR2023-00178 from PTAB E2E (https://ptacts.uspto.gov/ptacts/) and read the petition cover page and the § 42.8(b)(1) mandatory notices. Link the exhibited records rather than the aggregator summaries. If the cover page names the '559 patent, close the file on this item.
2. Order the full prosecution history and confirm the priority chain. '438 was filed as a continuation-in-part of U.S. App. Ser. No. 11/824,336 (filed 2007-06-28). Confirm which claims get the 2007-06-28 priority date and which rely on new matter added in the CIP — new-matter claims get the 2007-07-26 date, and any art between those two dates becomes available. This is the single highest-value lever in a pre-AIA family like this one.
3. Build the IPR now. With no § 315(e)(2) estoppel against '438, you have a clean slate: any § 102/§ 103 ground, any qualifying reference, no prior-petitioner ground to avoid duplicating. Deadlines are § 315(b) — one year from service of the complaint — and the statutory trial clock is one year from institution (§ 316(a)(11)). If you are also a defendant in the co-pending family actions, note the joinder route under § 315(c) is unavailable to you as a non-petitioner.
4. Watch the ownership chain and the sibling family. Wireless Management Solutions, LLC took the patent on 2025-01-29. Ask for the assignment and any license/standstill that may have come with it, and map the ~30 sibling continuations — if you invalidate '438, expect a re-assertion on a sibling. A challenge that only kills '438 may be a wasted fee.
5. Preserve the § 101 and § 112 defenses. Nothing at the Board has tested these claims. The specification claims a wireless wallet/policy-enforcement architecture that a court could read as an abstract idea implemented on generic network hardware (Alice step two), and the family's own PTAB record shows a written-description fight over where enforcement occurs (the Board in IPR2022-00001 "disagree[d] with Patent Owner's argument that the specification discloses an alternative where enforcement is performed by a user device"). That is a transferable § 112 vulnerability for the '438 specification, which is shared family subject matter. Raise it in Markman and in any early dispositive motion — do not concede it to the IPR track.

Caveat on sourcing. The proceeding number, filing date, status, panel, and challenged-claim list above come from aggregator and portal data, not from a decision document I was able to open. No Final Written Decision exists for any AIA trial on US 7,899,438, so there is no opinion to quote at claim-level granularity — and I have not manufactured one. Where the record is silent (petition grounds, institution outcome, settlement terms), the answer is "not public" or "unverified," not a guess.

I'll research this patent's ownership chain and cross-reference external sources.

Let me dig deeper into the assignment records, reel/frame data, and the acquiring entity.

Ownership & Assignment Record — US 7,899,438 B2

Patent: US 7,899,438 B2 — "Feature management of a communication device"
Application: 11/881,460 · filed 2007‑07‑26 · priority 2007‑06‑28 (CIP of Ser. No. 11/824,336) · issued 2011‑03‑01
Current assignee (per Google Patents legal events, synced from USPTO assignment records): Wireless Management Solutions, LLC

Data-integrity caveat, read first. I was able to reconstruct the assignment chain (conveyance types, assignors, assignees, dates) from the Google Patents legal‑events table, which mirrors the USPTO assignment record set. I could not retrieve reel/frame numbers or the correspondent of record for any link in this chain — the USPTO Assignment Center (https://assignmentcenter.uspto.gov/) and https://assignment.uspto.gov/patent/index.html were not queryable in this session, and Google Patents does not republish reel/frame or correspondent fields. I therefore list reel/frame as [not retrieved] rather than guess, and I have flagged the correspondent-based signal as unverifiable. Verification URL: https://assignmentcenter.uspto.gov/ (search "7899438" or "11/881,460").

Inventors

All six named inventors, with employer at filing where determinable:

Unusual patterns — assessed:

• No mass-departure pattern found. The opposite: Kesser, Neal, Politi and Weintraub reappear as assignors on later filings in the same family (recorded activity around 2019‑03‑21), and Baker around 2020‑04‑21 — i.e., inventors stayed attached to the portfolio through at least 2019–2020. That is not a fire-sale precursor.
• Founder-inventor concentration is notable: two of six inventors (Neal, Weintraub) are the company's founders, and Neal publicly identifies himself as an inventor on "most" of the portfolio. This is a founder-built portfolio, not an acquired one.
• All six are listed on the original 2007‑08‑23 assignment to Kajeet, consistent with a standard employee/founder invention-assignment program.

Original assignee

Kajeet, Inc. (Bethesda, Maryland at filing; later McLean, Virginia) — named on the issued patent.

• Primary line of business: A youth-oriented MVNO (mobile virtual network operator). Founded 2003 by three fathers (including Neal and Weintraub); national pay‑as‑you‑go service launched March 2007 on the Sprint PCS network, sold through Best Buy, Limited Too and Longs Drugs. It later pivoted to K‑12 education broadband — Education Broadband (2014), the SmartSpot hotspot, SmartBus school‑bus Wi‑Fi, and the patented Sentinel filtering/device‑management platform. Its own collateral describes it as a "leading wireless managed service provider" with "40 foundational US wireless patents."
• Did it ship a product embodying the claims? Yes. The patent's FIG. 3–5 screens (Contact Manager, allowed/blocked number lists, wallet allocation, feature toggles for downloads/feeds/web/picture messaging/IM) describe the actual kajeet parental‑control dashboard shipped to consumers. Kajeet also publicly claimed 5.5M+ lines connected and 3,000+ customers, and stated it is "in IoT."
• Current status: Operating. It shut down its consumer MVNO (~July 2019) to focus on education/IoT, but continues to trade — press and product releases run through 2025–2026 (e.g., SentinelOS, Kajeet Connected Communities). Crunchbase lists an M&A event, "Kajeet acquired by MWP Growth Capital," with the announced date obfuscated; treat that as unconfirmed detail.
• Licensing posture (relevant to NPE analysis): On 2020‑07‑21 Kajeet announced a patent licensing program (36 issued US patents), 8 licensees including Smith Micro and CUJO, advised by Patent Monetization Inc. with litigation counsel Friedman Suder & Cooke. It stated it had sued JAMF Software, Lightspeed Software (W.D. Tex.) and Gryphon (D. Del.). Docket records add Asavie (6:20‑cv‑00705), Impero (6:20‑cv‑01076), Trend Micro (6:21‑cv‑00389), McAfee (1:21‑cv‑00005), Mosyle (1:21‑cv‑00006), CyberReef (1:21‑cv‑00004), Viasat (6:21‑cv‑00707), NortonLifeLock/Gen Digital (1:20‑cv‑01339), and Premier Wireless (4:21‑cv‑01468).

Assignment timeline

Chronological, from the legal-events record. Reel/frame: [not retrieved] for every entry (see caveat above). Execution dates are not exposed by this source; the dates below are the USPTO recordation dates. "Correspondent" is [not retrieved] throughout.

1. 2007‑08‑23 (recorded) — Reel [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: Original inventor-to-employer assignment; the founding link of the chain.

2. 2009‑02‑25 (recorded) — Reel [not retrieved]

   • Conveyance: Security Agreement
   • Assignor: Kajeet, Inc.
   • Assignee: Bluecrest Venture Finance Master Fund Limited
   • Correspondent: [not retrieved]
   • Context: Securitization — venture-debt collateral lien, not a transfer of title.

3. 2010‑12‑30 (recorded) — Reel [not retrieved]

   • Conveyance: Security Agreement
   • Assignor: Kajeet, Inc.
   • Assignee: Draper Fisher Jurvetson Growth Fund 2006, L.P.
   • Correspondent: [not retrieved]
   • Context: Securitization — investor collateral lien arising from the $36.8M Series B (DFJ Growth led, September 2007).

4. 2011‑01‑07 (recorded) — Reel [not retrieved]

   • Conveyance: Security Agreement
   • Assignor: Kajeet, Inc.
   • Assignee: Silicon Valley Bank
   • Correspondent: [not retrieved]
   • Context: Securitization — bank collateral lien; repeats the same correspondent/recording workflow as links 2–3 if filed by Kajeet's outside counsel (unverified).

5. 2011‑03‑16 (recorded) — Reel [not retrieved]

   • Conveyance: Release by Secured Party
   • Assignor: Bluecrest Venture Finance Master Fund Limited
   • Assignee: Kajeet, Inc.
   • Correspondent: [not retrieved]
   • Context: Lien release; title reverts cleanly to Kajeet.

6. 2011‑05‑11 (recorded) — Reel [not retrieved]

   • Conveyance: Release
   • Assignor: Silicon Valley Bank
   • Assignee: Kajeet, Inc.
   • Correspondent: [not retrieved]
   • Context: Lien release; title clean again.

7. 2021‑12‑17 (recorded) — Reel [not retrieved]

   • Conveyance: Security Interest
   • Assignor: Kajeet, Inc.
   • Assignee: Silicon Valley Bank
   • Correspondent: [not retrieved]
   • Context: Securitization — renewed SVB credit facility lien, filed mid-way through the licensing campaign.

8. 2024‑10‑03 (recorded) — Reel [not retrieved]

   • Conveyance: Release by Secured Party
   • Assignor: Draper Fisher Jurvetson Growth Fund 2006, L.P.
   • Assignee: Kajeet, Inc.
   • Correspondent: [not retrieved]
   • Context: Lien release — starts the clean-up sequence that precedes the 2025 sale.

9. 2025‑01‑21 (recorded) — Reel [not retrieved]

   • Conveyance: Release by Secured Party
   • Assignor: Silicon Valley Bank
   • Assignee: Kajeet, Inc.
   • Correspondent: [not retrieved]
   • Context: Lien release — second step of the clean-up sequence; eight days before transfer.

10. 2025‑01‑29 (recorded) — Reel [not retrieved]

    • Conveyance: Assignment of Interest
    • Assignor: Kajeet, Inc.
    • Assignee: Wireless Management Solutions, LLC
    • Correspondent: [not retrieved]
    • Context: Transfer of the portfolio out of the operating company to an LLC; the assignee is also named on the newest continuation in the family, US 12,382,259 B2 (granted 2025‑08‑05), confirming a whole-family transfer rather than a single-patent deal.

Timeline diagram

timeline
    title Ownership of US 7899438
    2007 : Filed by Kajeet Inc
         : Inventors assign rights to Kajeet
    2009 : Bluecrest security agreement
    2010 : DFJ Growth security agreement
    2011 : Issued to Kajeet Inc
         : Silicon Valley Bank security agreement
         : Releases restore clean Kajeet title
    2019 : Kajeet files first infringement suits
    2021 : Silicon Valley Bank renewed security interest
    2024 : DFJ Growth lien released
    2025 : SVB lien released to Kajeet
         : Portfolio assigned to Wireless Management Solutions LLC

NPE / troll-pattern signals

1. Shell-entity transfer — PRESENT (with a material caveat).
On 2025‑01‑29 the operating company (Kajeet, Inc.) moved the entire patent family to Wireless Management Solutions, LLC, an entity for which I found no product, no service, and no commercial presence — the only hits for the name are patent records. The move was executed eight days after the final security-interest release (2025‑01‑21) and after the DFJ release (2024‑10‑03), i.e., the lien stack was cleared immediately before transfer to hand the buyer clean standing. The same assignee holds the 2025 continuation US 12,382,259 B2. Caveat that cuts against a hard call: the LLC's address of record for this family is Chevy Chase, Maryland (per inventor Kesser's assignee profile) — the same corridor as Kajeet's Bethesda/McLean offices — so this may be a captive IP-holding affiliate rather than an arm's-length third-party shell. I could not confirm single-member status or a registered-agent service, which the signal definition requires. Marked present on the "operating company → non-product-holding licensing LLC" prong only.

2. Known asserter in the chain — NOT PRESENT.
Neither Kajeet, Inc. nor Wireless Management Solutions, LLC matches any public NPE roster I compared against (Acacia, Marathon, Intellectual Ventures, IPNav, Wi‑LAN, Mosaid/Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, Document Generation Corp, Spangenberg entities). To the contrary: Unified Patents petitioned against the family (IPR2023‑00178, settled; and IPR2022‑00001, Gen Digital/NortonLifeLock v. Kajeet on US 8,667,559) — the family has been on the receiving end of defensive action, not listed as an asserter. Do note, however, that Kajeet, Inc. is a serial patent plaintiff (roughly a dozen § 271 suits in 2019–2021), which is atypical behavior for a mid-size operating company even though it is not "NPE list" membership.

3. Repeat correspondent across the chain — UNVERIFIABLE (not retrieved).
This is the single most probative signal in the brief and it is the one I could not obtain: the Assignment Center's correspondent-of-record field was inaccessible this session, and Google Patents does not republish it. I therefore cannot say whether one attorney or recording firm handled links 1–10, nor whether that name recurs on other Kajeet-family patents (e.g., US 7,945,238, the sibling filing). This should be the first thing re-run against https://assignmentcenter.uspto.gov/. Note for that follow-up: Kajeet's announced litigation counsel of record is Friedman Suder & Cooke (Jonathan T. Suder filed the § 271 complaints), and its licensing advisor is Patent Monetization Inc. — a recurrence of either name on the 2025‑01‑29 recording would materially strengthen Signal 1 and signal 3.

4. Cascading transfers — NOT PRESENT (as defined).
There is no chain of consecutive LLC-to-LLC assignments inside 24 months, and no shared-correspondent clustering to evidence it. What exists instead is a security-interest cluster (three liens 2009–2011, three releases 2011, one re-lien 2021, two releases 2024–2025) followed by one sale. That is a financing history, not an assignment cascade.

5. Pre-litigation transfer — NOT PRESENT (and inverted).
The first infringement suits (D. Del. 1:19‑cv‑02370 / 1:19‑cv‑02371, then the 2020–2021 wave) were filed by Kajeet, Inc. as patent owner, four to six years before the 2025‑01‑29 transfer. The transfer is therefore post-litigation, not a pre-assertion venue/standing shuffle for the suits already on file. Whether Wireless Management Solutions, LLC intends a fresh assertion wave post-transfer is unknown on this record.

6. Bankruptcy fire-sale — NOT PRESENT.
No Chapter 7 or 11 filing by Kajeet, Inc. appears in the record, and no sale-in-proceedings conveyance is recorded. The 2009–2021 instruments are secured-lending liens (security agreements/security interests), which are not bankruptcy conveyances; related lien releases followed normally. Note that Kajeet's MVNO peers (Amp'd Mobile, Firefly) did fail, but no comparable filing is evidenced here for Kajeet.

7. Privateering — UNCLEAR.
Kajeet asserted its own patents directly against competitors (JAMF, Lightspeed, Gryphon, Trend Micro, NortonLifeLock, McAfee, Impero, CyberReef, Mosyle, Viasat, Asavie) while still shipping Sentinel/SmartSpot — that is classic operating-company assertion, not privateering. A later-stage hand-off to a licensing vehicle would fit the privateering mold, but I found no SEC filing, Patent Progress, or EFF coverage tying Wireless Management Solutions, LLC to Kajeet or to an assertion campaign on Kajeet's behalf. Insufficient evidence either way.

8. Defensive aggregator — NOT PRESENT.
The chain terminates at Wireless Management Solutions, LLC, not at RPX, AST, LOT Network, Unified Patents, or OIN. Inverse signal does not apply — the patent has not been neutralized; if anything, Unified Patents has been fighting the family rather than acquiring it.

Verdict

NPE — moderate confidence.

The chain's terminal link is a 2025‑01‑29 recorded assignment of the whole family from the operating company Kajeet, Inc. to Wireless Management Solutions, LLC, an entity with no demonstrable product or service offering, executed eight days after the final security-interest release (2025‑01‑21) cleared the title — a sequencing pattern typical of arranging clean standing for a licensing/assertion vehicle. That is one strong signal. It is reinforced weakly by the surrounding context: a decade of serial § 271 assertions by the original assignee and a fresh continuation (US 12,382,259 B2, 2025‑08‑05) filed under the new LLC. It falls short of high confidence because (a) the LLC's Chevy Chase, MD address sits in Kajeet's own operating corridor and may indicate a captive IP-holding affiliate rather than an arm's-length troll, and (b) the two most decisive tests — repeat correspondent of record and registered-agent / single-member shell indicators — could not be run, since reel/frame and correspondent fields were not retrievable this session.

Priority follow-up to convert this to high confidence or to clear it: run the patent and application number through https://assignmentcenter.uspto.gov/, record the reel/frame and correspondent of record for the 2025‑01‑29 entry and for the 2019/2020 inventor-assignment entries, and check whether that same correspondent appears on the sibling patents (US 7,945,238, 8,667,559, 8,706,079) and on the Delaware/Texas complaints.

I'll research patent US7899438B2 and its cited prior art. Let me run several searches.

Let me get the specific citation lists from patent databases.

Let me retrieve the actual front-page references from the patent documents themselves.

Prior-Art Analysis — US 7,899,438 B2

1. Confirming the target patent (exact match, no similar numbers)

Source: https://patents.google.com/patent/US7899438/en

Important scope caveat up front: I was able to verify the bibliographic record above, but the authoritative front-page "References Cited (56)" block of US 7,899,438 itself was not retrievable through the sources I could reach in this session, and the full patent text supplied ends mid-sentence in the Detailed Description — the granted claims are not included. Because a § 102 anticipation analysis is claim-by-claim, I cannot responsibly assign specific claim numbers (e.g., "anticipates claim 1") without the claim text. I am therefore explicit below about what is verified vs. what is family-level/inferred, and I flag where I cannot reach high confidence.

2. What "patent citation" means here — two distinct sets

For US 7,899,438 there are two different citation relationships, and conflating them is the most common error in this kind of request:

• References CITED BY the patent (backward citations / "prior art of record") — this is what you want for § 102.
• Patents CITED BY OTHERS (forward citations / "Cited By") — these post-date the 2007-06-28 priority and cannot be § 102 art against it.

I address both, in that order.

3. Backward citations (prior art of record) — verified where possible

The Kajeet family shares one specification, so the examiner-cited art on the sibling members is the best proxy available and is highly probative. The lists below are taken from the front pages of the same-family continuations US 8,634,802 and US 8,712,371 (uspto.report mirror of the printed front page) and US 8,600,348 (USPTO patentimages PDF). I have labeled the source for each.

3(a) U.S. patent documents cited in the family

Confirmed example from the family front pages / Justia record for related Kajeet patents:

Justia record: https://patents.justia.com/patent/[11516629](/patent/11516629)

I want to be candid: the search surface I could reach kept returning the sibling patents' reference lists rather than the 7,899,438 front page, so I will not list additional U.S. patent numbers as "cited by 7,899,438" that I could not actually see on its face. Fabricating that list would be worse than omitting it.

3(b) Foreign patent documents cited in the family (verified from the printed front pages of US 8,634,802 / US 8,712,371)

Publication-date list (verified verbatim):

• EP: 0137884 (Apr 1985); 0172670 (Feb 1986); 1041520 (Apr 2000); 1072997 (Jan 2001); 1132839 (Sep 2001); 1450322 (Aug 2004); 1528513 (May 2005); 1798659 (Jun 2007); 1798943 (Jun 2007)
• FR: 2863088 (Jun 2005)
• GB: 2419970 (May 2006); 2425621 (Nov 2006); 2431072 (Apr 2007)
• JP: S59062976 (Apr 1984); 9-179921 (Jul 1997); 9-185658 (Jul 1997); 2000-48144 (Feb 2000); 2000-251154 (Sep 2000); 2000-331100 (Nov 2000); 2001-134689 (May 2001); 2001-291039 (Oct 2001); 2003-209880 (Jul 2003); 2004-102726 (Apr 2004); 2006-139433 (Jun 2006); 2006-309786 (Nov 2006); 2007-323337 (Dec 2007)
• KR: 2001-088369 (Sep 2001); 2002-010160 (Feb 2002); 2002-016161 (Mar 2002); 2003-044475 (Jun 2003); 10-2004-0089144 (Oct 2004); 10-2005-0048166 (May 2005); 10-2007-0018329 (Feb 2007)
• WO: 01/35353 (May 2001); 02/084989 (Oct 2002); 03/092348 (Nov 2003); 2004/100094 (Nov 2004); 2005/015831 (Feb 2005); 2005/017793 (Feb 2005); 2005/081664 (Sep 2005)

Sources: https://uspto.report/patent/grant/[8634802](/patent/8634802) ; https://uspto.report/patent/grant/[8,712,371](/patent/8712371)

Note two entries post-date (or are only just before) the priority date and would not be § 102 art as printed: JP 2007-323337 (Dec 2007) and JP 2006-309786 (Nov 2006) — 2006-309786 is before, 2007-323337 is after. EP 1798659/1798943 (Jun 2007) are borderline (published the same month as the priority date) and need exact-day checking.

3(c) Non-patent literature ("Other Publications") — verified from US 8,600,348 front page

• Boyd, "Here Comes the Wallet Phone," IEEE Spectrum, Nov. 2005, pp. 12–14 — popular/technical overview of mobile-wallet payment.
• Carstens, "Mechanism for Compiling Payment Information on Mobile Terminals," IP.com #IPCOM000124834D, Jun. 2005 — mobile-terminal payment-information compilation.
• Diesposti et al., "Dual-Use Personal NavCom Service," IEEE 2000, pp. 69–79 — dual-use personal navigation/communication service.
• Ebringer et al., "Parasitic Authentication to Protect Your E-Wallet," IEEE Computer, Oct. 2000, pp. 54–60 — e-wallet authentication/security.
• Hung et al., "Security and Privacy Aspects of SmartFlow Internet Payment System," IEEE 1999 — Internet payment-system security.
• IBM TDB, "Micropayment Scheme," IP.com #IPCOM000013249D (orig. pub. Apr. 1, 2001; IP.com Jun. 18, 2003) — micropayment scheme.
• Integrated Mobile, Inc., "Family-friendly Mobile Services," Executive Overview presentation, Nov. 10, 2003, pp. 1–39 — arguably the closest non-patent art: family/parent-managed mobile service controls.
• Ishikawa et al., "Mixed-Reality…" (title truncated in the retrieved OCR) — mixed-reality computing.

Source (PDF, "(56) References Cited / Other Publications"): https://patentimages.storage.googleapis.com/74/46/f3/1eb7c95af5fdb3/US8600348.pdf

3(d) Prior art named in the 7,899,438 specification itself (background section)

The specification expressly characterizes as known:

• Postpaid and prepaid cellular offerings, rollover minutes, automated refill services.
• Alert-only parental controls (spend-threshold notices that do not actually block usage).
• Affinity accounts and corporate sub-accounts.
• Telcordia™ Converged Real-Time Charging — "allows users to place limited real-time controls over prepaid and postpaid accounts… parental controls… can be set to limit that child's spending within a set of parameters."

The applicant's own characterization of the Telcordia system as providing real-time, parameter-based parental spending controls is the single most dangerous admission in the document for the broadest claims, because the patent's stated point of novelty is real-time policy enforcement.

4. § 102 assessment (properly hedged)

Because the granted claims were not available to me, I can only give a claim-class → reference mapping, not claim numbers:

Bottom line: the most probable § 102 exposure for this patent comes not from a single prior U.S. patent but from (i) the applicant-admitted Telcordia Converged Real-Time Charging system and (ii) Integrated Mobile, Inc.'s "Family-friendly Mobile Services" (Nov. 10, 2003). The U.S. patent art of record (typified by Blinn 7,155,411) is wallet-centric and more naturally § 103 art.

5. Forward citations (context only — NOT § 102 art)

Patents/publications citing US 7,899,438 include, as verified on its Google Patents "Cited By": US 10,567,975 (Hoffberg Family Trust 2, 2020-02-18, priority 2005-10-04); US 10,838,739 (Circle Media Labs, 2020-11-17); US 11,070,681 (Kajeet, 2021-07-20); US 11,206,516 (Kajeet, 2021-12-21). Also a large Kajeet continuation family (US 8,285,249; 8,588,735; 8,594,619; 8,600,348; 8,611,885; 8,630,612; 8,634,801/802/803; 8,639,216; 8,644,796; 8,667,559; 8,706,079; 8,725,109; 8,731,517; 8,755,768; 8,774,754/755; 8,995,952; 9,237,433; 10,009,480; 10,255,025; 10,469,446; 10,555,140; 10,694,346; 11,206,516; 11,516,629; 11,689,901; 12,382,259; and pre-grant pubs US 2013/0029653 A1, US 2023/0283997 A1) all share the 2007-06-28 priority and therefore are not prior art against 7,899,438.

Sources: https://patents.google.com/patent/US7899438/en ; https://www.freepatentsonline.com/[8634821](/patent/8634821).html ; https://www.freepatentsonline.com/[8634805](/patent/8634805).html

6. What I could not confirm (stated plainly, not fabricated)

1. The exact "References Cited (56)" U.S.-patent-document list printed on US 7,899,438's own front page — I could not retrieve it in this session. The lists in §3 are the family/shared-specification lists, clearly labeled as such. Before filing anything, pull the 7,899,438 face page directly (USPTO PatentCenter or the Google Patents PDF) to lock down the true backward-citation set.
2. The granted claim set of 7,899,438 — absent, so no claim-number-specific § 102 mapping is possible. Fetch the issued claims (USPTO PatentCenter, US 11/881,460) before completing the analysis.
3. Exact disclosure content of Integrated Mobile (2003), the Telcordia CRTC system, and each EP/JP/KR/WO reference — I have the citation and date, not a verified feature-by-feature mapping.

Recommended next steps for a defensible § 102 chart: (a) pull the 7,899,438 front page and claims; (b) obtain Integrated Mobile, "Family-friendly Mobile Services" (Nov. 10, 2003) and Telcordia CRTC product literature; (c) map each independent claim limitation to those two references element-by-element; (d) treat the Blinn/U.S.-patent art as § 103 combinations.

I'll start by pulling the authoritative record for this patent — its cited prior art, and the PTAB proceeding referenced on the page — since the patent text supplied above contains a "Prior art keywords / Prior art date" block and a Background discussion but no formal reference list.

The page as fetched contains a "Prior art keywords / Prior art date" block and the Background discussion, but no formal citation table. Let me pull the granted claim set of US7899438 and the cited-reference record so the § 103 analysis is grounded.

Obviousness analysis — US 7,899,438 B2 (35 U.S.C. § 103)

0. Threshold caveats (please read before using this analysis)

Three record problems materially limit what can be asserted with confidence, and I will not paper over them:

1. The supplied page contains no formal "Prior Art" citation list. The material I was given for https://patents.google.com/patent/US7899438/en contains only: (a) Prior art keywords: user, request, recited, policies, administrator; (b) Prior art date 2007-06-28; and (c) the narrative Background of the Invention. There is no "References Cited" table, no cited-by list, and no claim set in the supplied text. The Background is the prior-art content available on the page, and I use it as such below.
2. The claim text of the '438 patent is not in the supplied material. The only claim set I recovered by search belongs to a different patent in the same family — U.S. 9,237,433 (application 13/786,685), whose claim 1 recites a "plan that is shared with a second mobile communications device" and "unallocated electronic units of value in the plan" (https://uspto.report/patent/grant/9,237,433). Per the literal-identifier rule, that claim text must not be attributed to US 7,899,438. I therefore analyze at the level of disclosed subject matter / limitation families, not verbatim claim language.
3. Identifier-confusion warning. Search results returned an unrelated "'943 Patent" concerning electrical stimulation near an ankle (priority § 120 dispute, Droplets-type issue). That is not US 7,899,438 and is excluded.

What the record does establish about the '438 claims: PTAB IPR2023-00178 challenged claims 1, 2, 3, 6, 10, 27, 33 of US 7,899,438 (filed Nov. 10, 2022; instituted May 12, 2023; terminated–settled Sept. 1, 2023; judges Dirba, Easthom, Ahmed) — https://services.patexia.com/lawsuits/Trend-Micro-Inc-v-Kajeet-Inc-id-[183366](/patent/183366). Note the petitioner is recorded as Trend Micro Inc. v. Kajeet, Inc. on that page, whereas the supplied Google page labels the same IPR number as a Unified Patents PTAB entry (https://portal.unifiedpatents.com/ptab/case/IPR2023-00178). I flag the conflict rather than resolve it. Claim 27/33-type numbering implies at least method + system/CRM claim formats.

Bibligraphic frame used: filed 2007-07-26, priority 2007-06-28 (CIP of 11/824,336), granted 2011-03-01; inventors Baker, Geller, Kesser, Neal, Politi, Weintraub; original assignee Kajeet, Inc., current assignee Wireless Management Solutions LLC; Google-listed adjusted expiration 2029-10-05. Because the '438 is a CIP, any reference published after 2007-06-28 but before 2007-07-26 is a § 102(a)(1)/pre-AIA § 102(b)-adjacent issue only if the CIP's new matter is not entitled to the parent's date — a priority attack I cannot complete without the claim/spec comparison.

1. Governing framework applied

Graham v. John Deere factors: (i) scope and content of the prior art; (ii) differences between the prior art and the claims; (iii) level of ordinary skill; (iv) secondary considerations. KSR Int'l v. Teleflex adds that a combination is obvious where prior-art elements are combined "according to known methods to yield predictable results," where the combination is "a simple substitution of one known element for another," or where the claimed arrangement was "obvious to try" from a finite number of identified, predictable solutions.

POSITA (my construction, flagged as an assumption): a B.S. in EE/CS or equivalent, plus 2–4 years' experience in mobile network service provisioning, real-time charging/rating, and prepaid billing platforms — consistent with the IS-41/IS-771/IS-826, PDSN/AAA and PEP/PDP vocabulary already used in the '438 specification.

Claim subject matter the '438 specification discloses (source: the supplied page): real-time enforcement of voice/data policies via a service manager 20, policy enforcement point 28 and policy decision point 29; global rules and local rules with an expressed order of precedence; wallet balance/state checks; allowed/blocked number lists; time-of-day and quality/class-of-service restrictions; user wallet / administrator wallet / promotional wallet / dynamic wallet with a hierarchy and backup funding; and a web-based Contact Manager (FIG. 3) and feature manager (FIG. 4/5) with per-feature "Edit Setting" controls. Notably, the page's own Prior art keywords — user, request, recited, policies, administrator — map directly onto this policy/enforcement architecture and onto the prior art below.

What the Background of the Invention concedes (this is the applicant's own statement of the art):

• Prepaid services limit spend but fail when funds run out — "a prepaid phone service does not solve the problem of ensuring availability of key services even if the prepaid account has run out of money."
• Rollover minutes and automatic credit-card refill exist; refill "is the equivalent of a postpaid phone service" with no spending limit.
• Postpaid "unlimited usage packages" exist but don't cover premium content (games, ringtones).
• Threshold alerts exist ("a parent could be alerted when a child has spent more than $10 on text messages") but "does not actually limit usage."
• Stored-value accounts funded by credit card or bank transfer exist; corporate subaccounts and affinity accounts exist, but "these accounts operate separate from one another in that all of the charges for a particular phone are charged to a particular account, rather than some charges being billed to one account while other charges are billed to another account."
• "The Telcordia™ Converged Real-Time Charging system allows users to place limited real-time controls over prepaid and postpaid accounts. For example, when an account allows a child to download premium data..., parental controls over that account can be set to limit that child's spending within a set of parameters."

Each of these concessions is an admission that a claimed element was known, and each is a motivation hook.

2. Prior-art reference set used

2(a) From the page's own Background (admitted art)

2(b) Contemporaneous prior art cited in this patent family

The '438 front-page reference list was not in the supplied page. The nearest verifiable record is the References Cited table published for US 8,600,348 — a member of the same family (same inventors, Kajeet) — at https://www.freepatentsonline.com/[8600348](/patent/8600348).html. Treat the following as family-level citations to be re-confirmed against the '438 front page, not as confirmed '438 citations:

• Ackley, US 7,302,272 / US 2005/0096009 — "Cell phone parental control"
• Zhou, US 7,869,792 — "Handset based dynamic parental controls"
• Erskine, US 2005/0282559 — "Method and system for providing supervisory control over wireless phone data usage"
• Mazerski, US 2006/0293057 — "System and method for secure web-based mobile phone parental controls"
• Singh, US 2007/0004386 — "Role- and locale-based mobile user device feature control"
• Gidron, US 7,330,717 — "Rule-based system and method for managing the provisioning of user applications on limited-resource and/or wireless devices"
• Joyce, US 7,248,855 / US 2003/0026404 — "Convergent communications system and method with a rule set for authorizing, debiting, settling and recharging a mobile commerce account"
• Cai, US 7,457,609 / US 2007/0099609 — "Methods and systems for controlling services provided to shared plan subscribers"
• Crimi, US 2008/0014904 — "Flexible rating rules and calendar rules implemented in a real-time charging system"
• Ali, US 2007/0058812 — "Enforcing time-based transaction policies on devices lacking independent clocks"
• Watler, US 2007/0060100 — "Systems and methods for mobile station service control"
• Blinn, US 7,155,411 — "Integrating payment accounts and an electronic wallet"
• Law, US 2007/0125840 — "Extended electronic wallet management"
• Nelson, US 6,990,182; Chan, US 6,957,058 — prepaid telephone service / prepaid account regeneration
• Sivalingam, US 2008/0119162 — "Sharing prepaid mobile telephony credit among a group"
• Mock, US 2008/0130849 — "Prepaying usage time for another communication device"
• True, US 2008/0096524 — "Method for providing a multi-member mobile telecommunications service plan"
• Mikan, US 2008/0146211 / US 8,068,825 — "Second party control over mobile device usage"
• Saez, US 2004/0229600 — call screening/management; Patron, US 7,209,957 — downloadable IM usage policies; Moghaddam, US 7,516,219 — web filtering

Publication dates place most of these before the 2007-06-28 priority date, which is why they appear as § 102/§ 103 art in this family.

3. Grounds of rejection — combinations and motivations

Ground 1 — Telcordia RTC + the admitted "stored-value account / subaccount / affinity account" art + Ackley

Covers: real-time policy decision on a per-request basis, administrator-set spend parameters, per-feature (premium data) limits, and allowed/blocked number enforcement.
Motivation, articulated in the patent's own words: the Background states Telcordia's parental controls are "only partial solutions" because a depleted account still denies "key services"; and it states alerts "do not actually limit usage." Those two admissions jointly supply the problem and the design direction — combine real-time charging control with enforcement at the network decision point. Ackley supplies the administrator-configured per-feature control and the parent/child role model. KSR: combination of two known parental-control mechanisms in a known real-time charging platform, yielding the predictable result of a single policy decision that both permits/denies and rates/charges.

Ground 2 — Erskine + Cai + Crimi + Ali

Covers: server-side supervisory control of wireless data usage; control of services across shared-plan subscribers; flexible rating rules and calendar rules in a real-time charging system; and time-based transaction policies enforced where the device lacks an independent clock.
Motivation: the '438 specification claims precisely this nexus — data-session origination, PEP/PDP policy check, and time-of-day restrictions applied server-side. Crimi's calendar/rating rules and Ali's server-enforced time policies are the natural, predictable building blocks for the claimed "policy stored at the server" that governs when a function may run; Cai addresses the "shared with a second device" aspect. A POSITA seeking to enforce parental time windows without trusting the handset would combine these as a matter of ordinary design.

Ground 3 — Joyce + Blinn + Law (wallets)

Covers: a mobile-commerce account governed by an authorizing/debiting/settling/recharging rule set (Joyce); integration of multiple payment accounts with an electronic wallet (Blinn); extended electronic wallet management (Law, e.g., management of multiple wallets by an owner).
Motivation: the claimed "order of precedence between wallets" and "second account is charged when the first is insufficient" is a known payment-architecture convention — cascading/backup funding sources are standard in card and wallet systems. The Background itself acknowledges multiple account types (user, corporate subaccount, affinity) already coexisted but "operate[d] separate from one another," which is an explicit statement of the only difference and thus frames the substitution of a hierarchical funding rule as an improvement of a known structure — the classic KSR "known technique to improve a similar device in the same way."

Ground 4 — Sivalingam + Mock + True + Nelson/Chan

Covers: sharing prepaid credit among a group; prepaying usage time for another communication device; multi-member service plans; prepaid account regeneration.
Motivation: directly addresses any claim limitations directed to a plan shared across devices, unallocated units allocable to a first or second device, and charging a second account when the first is depleted. Mock in particular teaches paying for another device's usage — the functional inverse of the claimed backup-wallet charge — and Sivalingam/True teach group allocation from a common pool. Combining these produces the claimed allocation/decrement behavior with predictable results and no new technical effect.

Ground 5 — Mazerski + Zhou + Singh + Mikan + Gidron/Watler

Covers: secure web-based parent-control UI (Mazerski — cf. the '438 FIG. 3 "Contact Manager" and FIG. 4/5 "Edit Setting" pages); handset-based dynamic parental controls and role/locale-based feature control (Zhou, Singh — cf. the location-conditioned school-control embodiment in the '438 specification); second-party control over mobile device usage (Mikan); rule-based provisioning of applications to limited-resource/wireless devices and mobile station service control (Gidron, Watler — cf. service manager 20 / PEP 28 / PDP 29).
Motivation: the '438's networking architecture (O-MSC → service manager; O-PDSN → AAA → PEP → PDP) is the standard IS-41/IS-771/IS-826 and WAP-gateway topology the Background and specification cite as conventional; adding an administrator-facing rule authoring and enforcement layer to that already-described topology is a straightforward combination of known elements.

Ground 6 — the § 103 meta-ground

Each of the admi​nistered prior-art systems above solves a subset of the same problem, and the '438 Background dissects each subset and its shortfall. Under KSR, "a person of ordinary skill is also a person of ordinary creativity," and where market forces (parental cost control, employer/school subsidization noted in the Background) push toward combining cost control with feature/contact control, the combination is not inventive merely because the individual pieces were each characterized as "partial."

4. Anticipated counter-arguments (and their limits)

• "Teaching away / prior art was only partial." The Background repeatedly calls prior solutions "partial," but a statement of inadequacy is not a teaching away unless it criticizes the combination itself or teaches that the modification should not be made. Under KSR, "[t]he fact that the [prior art] discloses only a partial solution does not..." defeat obviousness where the reference points in the same direction. Nothing on the supplied page disparages combining a real-time charging control with a feature/contact policy engine.
• "The wallet construct is the novelty." But the Background concedes stored-value accounts, subaccounts, affinity accounts, and credit-card refill — i.e., funding sources existed; the claimed increment is a rule for ordering them, which Grounds 3–4 address.
• Secondary considerations. The page shows a large family (~40 related filings), sustained litigation (D. Del. 1:19-cv-02370 and 1:19-cv-02371; C.D. Cal. 2:20-cv-00253; W.D. Tex. 6:20-cv-00705), and an instituted-then-settled IPR. Asserted commercial success or long-felt need would require a nexus to the claimed elements — an argument Patent Owner would need to make, and one that is weakened where the patent's own Background concedes the need was known and partially met.
• Priority/CIP attack. Because the '438 is a CIP of 11/824,336, a challenger retains an independent § 102 argument that claim elements supported only by CIP-added matter get a 2007-07-26 date, potentially disqualifying certain 2007 publications. I cannot complete this without the claim/spec comparison, which the supplied page omits.

5. Bottom line

Most likely to succeed: Ground 2 + Ground 3 as the primary § 103 combination (server-side real-time policy enforcement for time/feature restrictions, plus a hierarchy of payment wallets charged in a defined precedence with a second/administrator wallet as backup), with Ground 1 supplying the admitted real-time parental spend-control base and Grounds 4–5 filling allocation-from-a-shared-plan and UI/administration limitations. The motivation is unusually well documented because the applicant wrote it into its own Background, and a POSITA reading that Background would arrive at the combination with a reasonable expectation of success.

Cannot be completed on this record: a verbatim claim-by-claim § 103 chart, because the '438 claim text was not present in the supplied page and must not be substituted with the US 9,237,433 claim set. Likewise, the exact reference names in the IPR2023-00178 petition (the strongest real-world obviousness attack, since it challenged claims 1, 2, 3, 6, 10, 27 and 33) were not retrievable here; I will not invent them.

Recommended next retrieval steps: (1) the '438 front page "References Cited" table and full claim set; (2) the Trend Micro (or Unified) IPR2023-00178 petition's ground list and exhibit numbers; (3) the '438 specification-vs-11/824,336 comparison to fix the effective priority date. Any of the three would convert the above into a fully supportable chart.