US 7881697

I'll verify the patent against live sources before summarizing.

Let me check for litigation specifically involving this patent and its current owner.

Verification note on sources

I ran three live searches (Google Patents, Justia, Unified Patents, RPX, Docket Alarm/PTAB, Justia Dockets, Kajeet's own patent list). The patent text you supplied matches the Google Patents and Justia records. Important caveat: Google Patents/Justia/third‑party aggregators are not the USPTO's own systems, and I have no direct PACER/PTAB/CAFC query access from this tooling. Treat the litigation section below as "nothing found," not as a certification of no litigation.

US 7,881,697 B2 — Summary

Chain of title (as recorded): Kajeet → security interests in favor of BlueCrest Venture Finance Master Fund, Draper Fisher Jurvetson Growth Fund 2006 L.P., and Silicon Valley Bank (2009–2011, with later releases); extended family includes reissues/continuations such as US 9,237,433 B1, US 8,995,952 B1, US 9,137,386 B1, and US 10,555,140 B2.

Abstract (as issued)

A system and method for the real‑time management of a device, and more particularly to the allocation of electronic wallets that are associated with one or more devices and various controls that enable at least two entities to manage how the device is utilized for various activities and to pay for goods and services. Each device is associated with at least two electronic wallets, a user wallet and an administrator wallet. The administrator can establish rules that designate how and when the device can be used and which wallet will be used to pay for goods and services desired by the user, but in the event the user wallet is depleted or low on funds, the administrator wallet can serve as a backup funding source for specified types of goods and/or services. Additional wallets can also be associated with the device to authorize and pay for goods and services, under the control of the administrator wallet, such as a promotional wallet that could be designated for use with the device before a primary or administrative wallet was used, or a dynamic wallet that could be associated for use with multiple different devices as well as other wallets, but acts in conjunction with the user and administrator wallets. Additional rules can be established to perform many other functions, such as manage the movement of value between wallets and from other sources to the wallets.

Background in one paragraph

The patent frames the problem as the trade‑off between postpaid abuse (unbounded bills) and prepaid failure (a child's account hits zero and the phone stops working when it's actually needed). It reviews prior partial fixes — rollover minutes, auto‑refill, unlimited bundles, spend alerts, Telcordia's Converged Real‑Time Charging parental controls — and argues each either removes the spending cap or merely warns rather than controls. The asserted novelty is the multi‑wallet + rule hierarchy model, not prepaid billing per se.

Plain‑language overview of the independent claims

Claim 1 — "Administrator wallet + two‑tier rule engine"

A real‑time system for managing a telecommunication device used by a user, comprising:

1. An administrator wallet that electronically stores units of value, is accessible by an administrator, and is associated with at least the telecommunication device; and
2. A function manager that manages multiple different functions the device can perform, which carries two kinds of rules:
   • a global rule answering "is this function permitted at all?", and
   • a local rule answering "who pays for it — the user or the administrator wallet?"

Plain reading: the core is the separation of permission (global rule) from allocation of cost (local rule), with the administrator's wallet as a first‑class funding source. This is a system claim, so the elements must be embodied in an apparatus/system, not merely a business practice.

Claim 14 — "Dynamic wallet controlled by a third‑party financier"

A real‑time system for funding a telecommunication device, comprising:

1. A dynamic wallet storing units of value, accessible by a financier (the patent's example is a grandparent), and identified by a unique identifier rather than being tied to a particular device; and
2. A function manager with a global rule (is the function permitted?) and a local rule that applies only if the global rule permits, specifying whether the cost is borne by the user or the dynamic wallet.

Plain reading: this is the "Grandma's wallet" embodiment from FIG. 2 — a sponsor who is neither the user nor the administrator can pre‑fund and attach a portable wallet to someone else's device for a defined purpose, while the administrator's permission rules still gate everything.

Claim 18 — "Promotional wallet with a cap"

A real‑time system for managing a telecommunication device, comprising a function manager, including:

1. a global rule specifying whether a function is permitted; and
2. a local rule that applies if the function is permitted and specifies whether units of value are paid by the user or a promotional wallet, where the promotional wallet stores value and is associated with the device, and where, if the function is a promotional function, the promotional wallet pays until a predetermined limit is met.

Plain reading: the distinctive hook is the predetermined limit — the promotion funds the activity up to a threshold, after which the claim's rule structure presupposes another payer takes over (dependent claim 19 expressly makes that the user wallet).

Dependent‑claim architecture (for context)

• Fallback / precedence: 2 (admin pays if user can't), 3 (reverse fallback to user wallet if admin wallet is short), 4 (charge‑card backstop), 8 (promotional wallet used first when funded).
• Contact‑based allocation: 6 (admin‑designated contacts billed to admin wallet), 7 (listed names/numbers billed to the user).
• Administration UI and alerts: 9 (low‑balance alert), 10 (web‑based function manager), 11–12 (transfers, including automatic/periodic "allowance" style transfers), 13 (gift refill with message to recipient).
• Dynamic/promotional extensions: 15, 17 (financier‑accessible funding function to associate the wallet and set/change local rules), 16 (three‑way split among user, dynamic wallet, administrator wallet), 19–20 (post‑limit payer, and administrator control over whether the promotional function is permitted).

Litigation / PTAB status (as of my searches)

• CAFC, 2026: I found no docket, appeal, or opinion referencing US 7,881,697. Nothing surfaced in a 2026 Federal Circuit context. Google Patents shows a family‑level flag ("Family has litigation"), which is a family‑aggregate flag, not evidence of a 2026 appeal on this patent.
• PTAB: The IPRs I found in Kajeet's portfolio target other patents — notably IPR2022‑00001 (Gen Digital/NortonLifeLock v. Kajeet, on US 8,667,559), with a Kajeet revised contingent motion to amend. I found no IPR petition against 7,881,697 itself. District‑court stays were entered in related Kajeet cases (e.g., Kajeet v. Gryphon Online Safety, D. Del. 1:19‑cv‑02370‑MN; Kajeet v. NortonLifeLock, 1:20‑cv‑01339‑MN) pending those '559 IPR outcomes.
• District court assertions: Kajeet's enforcement campaign (2018–2021) named Qustodio, Liminex/GoGuardian, Lightspeed Solutions, Asavie, Infoweise, Viasat, Lumen, Trend Micro, McAfee, Mosyle, CyberReef, Impero, and others. The patents I saw actually asserted in the records I retrieved were predominantly the "Feature management" family (e.g., '559, '612, '371, '825) — not 7,881,697. I could not confirm any complaint specifically pleading 7,881,697.

Explicit uncertainty: I cannot rule out (a) an unindexed 2026 filing, (b) a CAFC appeal docketed after my search corpus was last crawled, or (c) assertions of 7,881,697 in complaints where the asserted‑patent list wasn't surfaced by search. For a definitive answer you'd want a direct PACER/Docket Navigator query on the patent number and on the current owner, Wireless Management Solutions LLC.

Analyst observations

1. The independent claims are narrow in an interesting way. Claim 1 does not require a user wallet at all — only an administrator wallet plus the two‑tier global/local rule split. The user wallet arrives only in the dependents and in independent claims 14 and 18 (as the alternatives to the dynamic/promotional wallets). That makes claims 14 and 18 arguably the more exposed ones in an invalidity analysis, since third‑party‑funded and promotional‑credit schemes were commercially common by 2007.
2. All claims are Beauregard‑style system claims. There are no method claims, so infringement requires an accused system with the recited wallet/rule‑manager structure — a point that matters for anyone mapping the patent onto a software service.
3. The "predetermined limit" in claim 18 is the load‑bearing phrase, and the specification's corresponding disclosure is thin: the promotional‑wallet example (§ discussing 10 free voice minutes) and the statement that promotional wallets may last "for a specified period of time, for a specified number of services, or for any of numerous other purposes." Expect a §112 written‑description or indefiniteness fight over how the limit is established and reset.
4. Prosecution‑history caution: the specification expressly states that a promotional wallet cannot be used to call a 900‑number blocked by a global rule, and that a dynamic wallet "would not be able to authorize services for a user that were blocked by the administrator." Those statements could be read as disclaimers limiting the scope of the dynamic/promotional wallet claims relative to the administrator's control.
5. Term note: with priority at 2007‑06‑28 and an adjusted expiration of 2028‑11‑22, the listed expiration runs past the nominal 20‑year date — consistent with PTA and/or terminal disclaimers tied to the continuation family. Verify against the face of the issued patent before relying on it.

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

Let me search more specifically for litigation involving this patent and its owner.

Let me check the Stanford NPE database and other litigation trackers directly for this patent.

Bottom line

I did not find a single litigation (district court or CAFC appeal) in which U.S. Patent No. 7,881,697 was specifically identified as an asserted patent. I also could not complete all of the searches I wanted to run — I hit the tool step limit — so this answer is based on the searches that did complete. I want to be explicit about that limitation rather than overstate confidence.

What I can confirm is that the '697 patent belongs to a patent family that has been actively enforced, and that Google Patents flags litigation for the family. Details below.

1. Verified facts about the patent (from the authoritative full text)

• Patent: US 7,881,697 B2 — "System and methods for managing the utilization of a communications device"
• Application: 12/027,240; filed 2008-02-06; granted 2011-02-01
• Priority: 2007-06-28 (continuation of App. Ser. No. 11/824,336, which issued as US 7,945,238)
• Inventors: Baker, Geller, Kesser, Neal, Weintraub, Politi
• Original assignee: Kajeet, Inc.
• Current assignee (recorded 2025-01-29): Wireless Management Solutions, LLC
• Litigation flag: The Google Patents record states: "Family has litigation / First worldwide family litigation filed" with a Darts-IP link (family ID 40161185). This confirms that some member of this family has been litigated — but the Google Patents page does not name the asserted patent or the case.

2. Enforcement activity I could associate with this patent owner / family

The following were surfaced by searching Kajeet, Inc., the original assignee. Important caveat: the sources I retrieved tie these matters to sibling patents in the same 2007-06-28 priority family — most notably US 8,667,559 — not to the '697 patent itself.

The W.D. Tex. (Waco Division) complaint text I retrieved cites the '559 Patent throughout ("'559 Patent at 2:36-44," "12:48-62"), confirming that the Kajeet campaign was publicly framed around the '559 patent.

3. What I could not verify (and did not fabricate)

• I could not confirm any case in which the '697 patent specifically is named in a complaint, infringement contention, or judgment.
• I could not retrieve filing dates, case numbers, or outcomes for the Qustodio matter.
• I could not confirm which patent (or patents) the Gen Digital IPR challenged.
• Given that the family has ~34 U.S. applications (including US 7,945,238, US 7,899,438, US 8,667,559, US 8,600,348, and later continuations), Google's family-level litigation flag may be triggered by any of these — it is not bilateral proof that the '697 itself was asserted.

Note also that because the '697 patent is a continuation of 11/824,336, any litigation asserting the '336/'238 patent is a different patent number, and under your "interpret literally / do not auto-correct" rule I am not treating those as litigation involving 7,881,697.

4. Sources I recommend checking (I ran out of search steps before clearing these)

• Unified Patents litigation portal: https://portal.unifiedpatents.com/litigation/caselist
• Stanford NPE Litigation Database — by patent: https://npe.law.stanford.edu/cases-by-patent (search patent 7881697)
• Darts-IP family link from the patent record: https://patents.darts-ip.com/?family=40161185 (this is the exact link Google cites for the "family has litigation" flag — the most direct way to resolve which family member was litigated)
• CourtListener / RECAP and PACER for Kajeet, Inc. and Wireless Management Solutions, LLC as party
• Docket Alarm for the PTAB IPR2022-00001 record (to identify the challenged patent)

Recommendation: Pull the Darts-IP family record for family 40161185 and run a PACER/CourtListener party search on "Kajeet" and "Wireless Management Solutions" with a patent-case nature-of-suit filter. That should conclusively establish whether the '697 patent itself — as opposed to its '559/'238/'348 siblings — was ever asserted, and if so, give you the plaintiff, defendant, jurisdiction, case number, filing date, and status you asked for. I'd be glad to continue this research if you re-run me with fresh search steps.

I'll start by verifying the structured "no PTAB activity" signal against live sources.

Let me verify whether any AIA trial petition has ever targeted the '697 patent itself, and check the broader Kajeet PTAB pattern.

Proceedings overview

Total AIA trial proceedings on U.S. Patent No. 7,881,697 ("the '697 patent"): zero. The structured USPTO Open Data Portal block reports no AIA trial proceedings on file, and my independent web searching found no IPR, PGR, or CBM petition that names the '697 patent as the challenged patent. The bottom line for a defendant: there is no claim-cancellation history to exploit and no PTAB record to mine for estoppel — all 20 claims (1–20) are untested at the Board, and nothing about this specific patent is "hardened" or "dead" by way of an AIA verdict. The only PTAB activity in this family sits on sibling patents (most notably U.S. 8,667,559 and U.S. 7,899,438), which is useful intelligence but is not a proceeding on the '697 patent.

I want to be explicit about the evidence limits: I could not locate any Federal Circuit appeal, settlement, or FWD that adjudicated the '697 patent, and I am not going to manufacture proceeding numbers to fill the template. The section below therefore (a) states the null result plainly, and (b) reports the documented adjacent proceedings — clearly labeled as concerning other patents in the same family, since a defendant's counsel will inevitably encounter them.

Proceedings on the '697 patent

None. No IPR, PGR, or CBM proceeding has been instituted against U.S. 7,881,697. Consequently:

• Claims canceled by PTAB: none.
• Claims sustained by PTAB: none (sustained-and-untested are distinguishable — nothing has been adjudicated).
• Settled / terminated: not applicable.
• Institution denied: not applicable.
• Federal Circuit appeal: none traceable to this patent.
• Statutory estoppel (35 U.S.C. § 315(e)(2)): none attaches to the '697 patent. No petitioner or privy is barred from raising any ground against these claims, because no petitioner ever ran a trial on them.

Caveat on the "zero" — one ambiguous hit you should chase

A search returned a page whose URL referenced IPR2025-00631 (captioned in the page title as "Revvo Technologies Inc. v. Tire Stickers LLC") but whose exhibit content was a **D. Del. docket entry from Kajeet, Inc. v. Gryphon Online Safety, Inc., No. 1:19-cv-02370-MN (June 10, 2022)**. The caption and the exhibit are inconsistent, so I cannot confirm this is an AIA proceeding involving the '697 patent — it may be a scraping/normalization artifact, or an IPR whose real caption I could not verify. Verification required on PTAB E2E before you rely on it in any way. My default remains "no PTAB activity on this patent."

• Confirm at PTAB E2E: https://e2e.uspto.gov/ (search by patent number 7881697)
• Confirm at the PTAB decisions/statistics portal: https://ptabdata.uspto.gov/

Also worth noting for completeness: a PGR is unavailable (the '697 patent's effective filing date long predates 2013-03-16), and CBM review is a dead end — the CBM program sunset for new petitions on 2020-09-16, and in any event the '697 claims are wallet/telecom-usage claims, a marginal CBM fit at best.

Adjacent proceedings — same family, different patents (context only)

These are not proceedings on the '697 patent. I include them because they define the family's PTAB exposure and the art that has already been tested.

IPR2022-00001 — Gen Digital Inc. (f/k/a NortonLifeLock Inc.) v. Kajeet, Inc.

• Type: Inter Partes Review
• Patent challenged: U.S. 8,667,559 ("Feature management of a communication device") — not the '697 patent
• Filed: 2021-10-01 (filed as NortonLifeLock Inc.)
• Status: Final Written Decision; terminated 2023-04-13; certificate re claims reported issued 2023-06-28
• Judge panel: Reported as Meredith C. Petravick (opinion author), Juliet Mitchell Dirba, Iftikhar Ahmed (one docket source also lists Karl D. Easthom)
• Petition grounds: Challenged claims 1–2, 5–15, 18–21, 27–29 under § 103, in three grounds — (1) Putzolu (U.S. 6,578,076) alone; (2) Putzolu + Rothman (U.S. 7,826,835) for claims 2, 7, 8; (3) Bhat (US 2005/0021978) for claims 13–15, 18–21. A § 112 written-description attack was deployed against Patent Owner's contingent motion to amend.
• Institution decision: Instituted 2022-04-21 on all challenged claims.
• Final Written Decision: Reported (Patexia) as invalidating all instituted claims — 1, 2, 5–15, 18–21, 27–29. Note a discrepancy I could not fully resolve: a district-court complaint analysis states the IPR certificate canceled claim 27 only (the sole claim asserted in that suit). Both accounts are consistent with the certificate canceling every claim the Board held unpatentable; but I have not verified the claim-by-claim disposition from the face of the FWD, so treat the "all claims" characterization as reported, not confirmed.
• Motion to amend: Kajeet filed an original and then a revised contingent motion to amend (substitute claims 31–32, 35–45; inadvertently included 33, 34, 46 were withdrawn). The Board's preliminary guidance disagreed that the specification supported enforcement on the user device. Petitioner's sur-reply called the amended Figure 2 a "doctored image." The MTA did not save the claims.
• Settlement / termination: No — went to FWD.
• Appeal: I found no Federal Circuit appeal of this FWD in the sources reviewed (the In re Trend Micro, No. 22-133, mandamus petition surfaced in the exhibit list is a venue/transfer dispute, not an appeal of this FWD).
• Defensive value: Not on your patent. But it establishes that this family's server-based policy claims have been held obvious over Putzolu/Rothman/Bhat, and it triggered district-court stays (see below). If your case involves the '559, claim 27 is gone.

IPR2023-00178 — Trend Micro Inc. v. Kajeet, Inc.

• Type: Inter Partes Review
• Patent challenged: U.S. 7,899,438 ("Feature management of a communication device") — not the '697 patent
• Filed: 2022-11-10 (per Patexia; case numbering is FY-based)
• Status: Terminated – Settled (decision date 2023-09-01)
• Judge panel: Juliet Mitchell Dirba (author), Karl D. Easthom, Iftikhar Ahmed
• Petition grounds: Challenged claims 1, 2, 3, 6, 10, 27, 33 (grounds not fully verified)
• Institution decision: Instituted 2023-05-12 on the challenged claims
• Final Written Decision: None — settled before FWD
• Settlement / termination: Terminated by settlement; terms are not public (settlement agreements filed in IPRs are typically confidential, and this one was not disclosed in the sources reviewed).
• Appeal: None found.
• Defensive value: Confirms the pattern — Kajeet's litigation targets filed IPRs against the family and Kajeet settled rather than litigate to judgment once the related '559 claims fell.

Litigation context (not PTAB, but the driver of these filings): Kajeet filed a wave of suits in W.D. Tex. and D. Del. in 2019–2021 against Trend Micro (6:21-cv-00389-ADA), NortonLifeLock (1:20-cv-01339-MN), Roqos (1:19-cv-02371-MN), Gryphon Online Safety (1:19-cv-02370-MN), Asavie (6:20-cv-00705), JAMF (6:20-cv-00302), Lightspeed (6:20-cv-00203), CenturyLink/Lumen (6:21-cv-00705), and Infoweise (6:21-cv-00704). The public complaint analyses I reviewed show claim 27 of the '559 and claim 27 of the '438 being asserted — I found no confirmation that the '697 patent was ever asserted in that campaign. In Kajeet v. Gryphon (D. Del.), the court stayed the case on 2022-06-10 pending the IPR FWDs, reasoning the FWD "is likely to resolve prior-art-based invalidity arguments," and noting Kajeet had itself agreed to stay related case 20-1339-MN.

Strategic summary

Claim status on the '697 patent. All 20 claims — independent claims 1, 14, and 18, and dependent claims 2–13, 15–17, and 19–20 — are UNTESTED. None is canceled; none is sustained by any tribunal. What the Board has adjudicated (on sibling patents) tells you something about the family's exposure to Putzolu/Rothman/Bhat, but those references were aimed at server-side, distributed policy-architecture claims. The '697 claims are directed at something materially different: hierarchical electronic wallets (user wallet / administrator wallet, plus promotional and dynamic wallets) and precedence between global and local rules governing who pays (see claims 1, 3, 4, 8, 12, 14, 18). A defendant should expect the '559 art to be a starting point, not a knock-out — the wallet-and-precedence limitations are not what Putzolu/Rothman/Bhat were doing. Conversely, the '697 claims carry obvious § 101 exposure (stored-value/accounting concepts on generic telecom hardware) and, given the 2007 priority date, thick § 103 exposure from the prepaid-account and parental-control art cited in the patent's own background.

Estoppel landscape. Because no AIA trial has ever touched the '697 patent, § 315(e)(2) estoppel is a non-issue in both directions. You may run any § 102/§ 103/§ 112 ground, with any reference, in any forum, including grounds that a hypothetical prior petitioner "reasonably could have raised." There is no petitioner IPR estoppel, no prior-art printing restriction, and no need to route around a petitioner's privity. (Separately, if a defendant is being sued on the '559 or '438, the Gen Digital and Trend Micro petitioners' estoppel is their problem, not yours — and for the '559, claim 27 is reported canceled.)

Pattern signals. (1) Petitioner concentration: NortonLifeLock/Gen Digital filed the family's first IPR against the '559; Trend Micro followed against the '438 — different petitioners, same family, both triggered by Kajeet's own infringement campaign, not by a defensive aggregator. I found no Unified Patents (or similar) filing in this chain. (2) Patent owner posture: Kajeet litigated the '559 IPR hard to an FWD (including a twice-filed contingent motion to amend) and then settled the '438 IPR before judgment — a rational portfolio-preservation pattern, not an aggressive PTAB-appeals posture. No Kajeet appeal of any FWD to the Federal Circuit was found. (3) Ownership drift you must account for: Google Patents records an assignment of the '697 patent from Kajeet, Inc. to Wireless Management Solutions, LLC on 2025-01-29. Any current demand is likely coming from WMS, and the litigation history above is Kajeet's, not WMS's. (4) Family is still moving: continuation filings persist (e.g., US 2023/0283997 A1), so fresh claims in this family can appear — monitor the family, not just the '697. (5) Term: the '697 patent's adjusted expiration is 2028-11-22 — roughly two years of runway, which caps the value of any licensing demand.

Recommended next steps

1. Verify the null result before you brief it. Search PTAB E2E (https://e2e.uspto.gov/) and the PTAB data portal (https://ptabdata.uspto.gov/) by patent number 7881697, and cross-check the USPTO assignment records for the 2025-01-29 Kajeet → Wireless Management Solutions transfer. Confirm in the Patent Center that no adverse judgment or disclaimer has narrowed the claims. If E2E also returns nothing, you can represent to the court that the '697 patent has never been the subject of an AIA trial.

2. Resolve the two open factual items flagged above if they matter to your case: (a) whether IPR2025-00631 is in fact a proceeding touching this patent family (the caption/exhibit mismatch means you must pull the case from E2E rather than trust the aggregator); and (b) the claim-by-claim disposition in IPR2022-00001's FWD ("all instituted claims" vs. "claim 27 only"). Both are for sibling patents, but the FWD is the best available read on how the Board treats this specification, so get the paper itself: PTAB E2E docket for IPR2022-00001; aggregated docket at https://www.docketalarm.com/cases/PTAB/IPR2022-00001/Gen_Digital_Inc._v._Kajeet_Inc/; petition/grounds summary at https://ai-lab.exparte.com/case/ptab/IPR2022-00001/doc/summary/1.

3. Build your invalidity case on the wallet claims, not the policy-architecture art. Because there is no IPR estoppel, serve your full § 102/§ 103/§ 112 contentions without narrowing. Focus on prepaid stored-value account prior art, hierarchical wallet/allocation references, and administrator-controlled spending systems — including the art the '697 patent's own background section concedes (prepaid accounts, automated refill, affinity/sub-accounts, Telcordia Converged Real-Time Charging). Consider a § 101 motion as a low-cost parallel track; the claims recite stored value, allocation, and priority rules, which invites an Alice step-two fight.

4. Weigh the timing. There are no pending proceedings and therefore no statutory trial deadline, no institution-decision date, no oral-hearing date, and no FWD due date for this patent. If you want PTAB relief you must create it: a petition under § 102/§ 103 against claims 1, 14, and 18 would face no § 325(d) or Fintiv baggage from this patent's own history (though the Gryphon stay order shows courts in this litigation have been receptive to staying pending an FWD in the family). Note the 2028-11-22 expiration when weighing ROI.

5. Do not overstate the family's wins as wins on the '697. If opposing counsel argues the PTAB has "invalidated Kajeet's patent," the correct response is: the PTAB has never adjudicated U.S. 7,881,697; the canceled claims belong to U.S. 8,667,559, a different patent with materially different claim scope. Conversely, do not assume the family's Putzolu/Rothman/Bhat success transfers to these wallet claims — it does not, on the current record.

I'll research the assignment record, corporate history, and any litigation/assertion activity before writing this up.

Assignment Record Reconstruction — US 7,881,697 B2

Patent: US 7,881,697 B2 — "System and methods for managing the utilization of a communications device"
App. No.: 12/027,240 · filed 2008-02-06 · granted 2011-02-01 · priority 2007-06-28
Continuation of: 11/824,336 (filed 2007-06-28; issued as US 7,945,238)
Family ID: 40161185 (34 family members) · Google Patents flags "Family has litigation"

Data-availability caveat up front: The sources reachable for this review — Google Patents legal events, patent-assignment aggregators, and litigation databases — do not expose reel/frame numbers or the correspondent of record for this patent. I therefore cannot supply reel/frame or attorney names in the timeline below without fabricating them, which the operating rules prohibit. Every reel/frame slot is marked [not retrieved], and the correspondent question is carried through to Signal 3 as unclear. To close this out, pull the patent number in USPTO Assignment Center (https://assignmentcenter.uspto.gov/ — the search page formerly at https://assignment.uspto.gov/patent/index.html) and read the Reel/Frame and Correspondent fields directly.

Inventors

Pattern notes:

• All six inventors conveyed to Kajeet, Inc. in a single recorded assignment on 2008-02-06, the same day the application was filed. No inventor retained or re-acquired any interest on the record — i.e., no inventor-departure / re-assignment churn is visible. Whether any inventor left Kajeet within 12 months of filing is not determinable from assignment records (departures are not recorded events).
• The inventor set is broad (six) for a single continuation filing, which is typical of an early-stage operating company where the patent was prosecuted as a company asset, not a founder invention.

Original assignee

Kajeet, Inc. — a Delaware corporation, HQ at the time of issuance in Bethesda/McLean, MD; later 7901 Jones Branch Drive, Suite 350, McLean, VA 22102 (per CPUC utility filings and Kajeet collateral).

• Line of business: Wireless managed service provider. Founded as a kid-safe MVNO (prepaid phones with parental controls) — exactly the product the patent describes — and it did ship the product embodying the claims: Kajeet sold parental-control cellular service with wallet-style budgeting, and later became a leading MVNO for schools (E-Rate/off-campus Wi-Fi), IoT connectivity, and private 5G/neutral-host networks. Its own materials claim 43 US patents in mobile technologies and ~3,000 customers.
• Assertion activity: Kajeet asserted family patents in its own name in a "parental controls" campaign: Kajeet v. Roqos (D. Del. 1:19-cv-02371), Kajeet v. Asavie, Kajeet v. Cujo (C.D. Cal. 2:20-cv-00253), Kajeet v. Trend Micro (W.D. Tex. 6:21-cv-00389), Kajeet v. Qustodio (C.D. Cal.), Kajeet v. Infoweise (W.D. Tex. 6:21-cv-00704). The patents asserted were '559 and '438 — family members, not the '697 patent at issue here — targeting genuine competitors (NortonLifeLock/Gen Digital, Trend Micro, Cujo, Roqos, Asavie). Gen Digital's IPR2022-00001 cancelled claim 27 of the '559 patent (certificate 2023-06-28). RPX characterized the campaign as "parental controls."
• Current status: Operating as of the latest available data (2025 Kajeet collateral, active FCC/CPUC filings, active 2025 patent issuances). No bankruptcy proceeding was located. Not the current assignee of this patent.

Assignment timeline

All entries below are drawn from the Google Patents legal-events record. Reel/frame numbers are [not retrieved] — the accessible sources do not publish them. Record series dates are as listed by Google Patents.

• 2008-02-06 (executed) / recorded 2008-02-06 — Reel [not retrieved]

  • Conveyance: Assignment of interest (inventors → company)
  • Assignor: Baker, Geller, Kesser, Neal, Weintraub, Politi (individually)
  • Assignee: KAJEET, INC.
  • Correspondent: [not retrieved] — this is the single most important field to pull manually; see Signal 3
  • Context: Formation of title — the six inventors convey the application to their employer on the filing date.

• 2009-02-25 (executed) / recorded 2009-02-25 — Reel [not retrieved]

  • Conveyance: Security Agreement
  • Assignor: KAJEET, INC.
  • Assignee: BLUECREST VENTURE FINANCE MASTER FUND LIMITED
  • Correspondent: [not retrieved]
  • Context: Securitization — venture-debt collateral pledge; no ownership transfer.

• 2010-12-30 (executed) / recorded 2010-12-30 — Reel [not retrieved]

  • Conveyance: Security Agreement
  • Assignor: KAJEET, INC.
  • Assignee: DRAPER FISHER JURVETSON GROWTH FUND 2006, L.P.
  • Correspondent: [not retrieved]
  • Context: Securitization — equity-investor collateral pledge; no ownership transfer.

• 2011-01-07 (executed) / recorded 2011-01-07 — Reel [not retrieved]

  • Conveyance: Security Agreement
  • Assignor: KAJEET, INC.
  • Assignee: SILICON VALLEY BANK
  • Correspondent: [not retrieved]
  • Context: Securitization — bank credit facility collateral pledge; no ownership transfer.

• 2011-03-16 (executed) / recorded 2011-03-16 — Reel [not retrieved]

  • Conveyance: Release by Secured Party
  • Assignor (releasing party): BLUECREST VENTURE FINANCE MASTER FUND LIMITED → KAJEET, INC.
  • Correspondent: [not retrieved]
  • Context: Lien discharge — Bluecrest collateral released (likely repaid/refinanced).

• 2011-05-11 (executed) / recorded 2011-05-11 — Reel [not retrieved]

  • Conveyance: Release
  • Assignor (releasing party): SILICON VALLEY BANK → KAJEET INC
  • Correspondent: [not retrieved]
  • Context: Lien discharge — SVB collateral released.

• 2021-12-17 (executed) / recorded 2021-12-17 — Reel [not retrieved]

  • Conveyance: Security Interest
  • Assignor: KAJEET, INC.
  • Assignee: SILICON VALLEY BANK
  • Correspondent: [not retrieved]
  • Context: Securitization — new/refinanced SVB facility; coincides with the period of Kajeet's assertion campaign.

• 2024-10-03 (executed) / recorded 2024-10-03 — Reel [not retrieved]

  • Conveyance: Release by Secured Party
  • Assignor (releasing party): DRAPER FISHER JURVETSON GROWTH FUND 2006, L.P. → KAJEET, INC.
  • Correspondent: [not retrieved]
  • Context: Lien discharge — DFJ collateral released, clearing a 14-year-old encumbrance ahead of the 2025 transfer.

• 2025-01-21 (executed) / recorded 2025-01-21 — Reel [not retrieved]

  • Conveyance: Release by Secured Party
  • Assignor (releasing party): SILICON VALLEY BANK → KAJEET, INC.
  • Correspondent: [not retrieved]
  • Context: Lien discharge — final SVB encumbrance cleared ~8 days before the ownership assignment.

• 2025-01-29 (executed) / recorded 2025-01-29 — Reel [not retrieved]

  • Conveyance: Assignment of Interest (ownership transfer — the only one besides the 2008 founder assignment)
  • Assignor: KAJEET, INC.
  • Assignee: WIRELESS MANAGEMENT SOLUTIONS, LLC
  • Correspondent: [not retrieved] — if a single attorney/firm appears here, on the sibling family recordings, and on other Wireless Management Solutions recordings, that is the recurring-correspondent finding; it cannot be called without the field
  • Context: Portfolio transfer to an asset-holding LLC — captured the whole Kajeet family (Google Patents now lists Wireless Management Solutions, LLC as current assignee across 2025 family issuances such as US 12,382,259 B2, and IP aggregator ipqwery shows the LLC holding 45 IP assets whose first patent is the 2007 "System and methods for managing the utilization of a communications device", i.e., this patent's family).

Note on the pre-2025 chain: every intervening recording (2009–2021) is a lien or lien release, not an ownership change. The patent sat with Kajeet, Inc. from 2008 until the 2025-01-29 transfer. The last recorded ownership event, and the current assignee of record, is Wireless Management Solutions, LLC.

Timeline diagram

timeline
    title Ownership of US 7881697
    2007 : Filed by Kajeet Inc
         : Priority date 2007 Jun 28
    2008 : Continuation filed Feb 6
         : Inventors assign to Kajeet Inc
    2009 : Secured loan to Bluecrest
    2010 : Secured loan to DFJ Growth
    2011 : Patent issued Feb 1
         : Secured loan to Silicon Valley Bank
         : Bluecrest security released
         : SVB security released
    2019 : Kajeet parental controls suits begin
    2021 : New SVB security interest
    2022 : Gen Digital IPR on family patent
    2024 : DFJ security interest released
    2025 : SVB security interest released
         : Assigned to Wireless Mgmt Solutions LLC

NPE / troll-pattern signals

1. Shell-entity transfer — UNCLEAR (leaning present-weak).
   The only ownership transfer in 18 years is Kajeet, Inc. → Wireless Management Solutions, LLC, 2025-01-29 (reel [not retrieved]). Supporting facts: the LLC is not the operating company; aggregator data shows it holds the entire ~45-asset Kajeet family, so it is not a purchased single patent; and the transfer was preceded by three lien releases (2024-10-03, 2025-01-21) that produced clean title. Against an NPE call: the name suffix is "Solutions," not IP/Patents/Holdings/Licensing; no registered-agent address or single-member LLC registration was retrieved; no corporate filing or SEC record was located confirming whether the LLC is Kajeet's captive IP-holding vehicle or a third-party acquirer. That distinction is the whole ballgame here, and it is unresolved.

2. Known asserter in the chain — NOT PRESENT (as to published NPE lists).
   No assignee in the chain matches Acacia, Marathon, Intellectual Ventures, IPNav, Wi-LAN, Mosaid/Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, Document Generation Corp, or Spangenberg entities. Wireless Management Solutions, LLC does not appear on the RPX or Unified high-frequency-plaintiff lists reachable here. Kajeet, by contrast, is a serial plaintiff (≥6 suits, 2019–2022) — but it sued in its own name as an operating company, and the Unified Patents portal tracks this family under the Wireless Management Solutions assignee entry.

3. Repeat correspondent across the chain — UNCLEAR / NOT DETERMINABLE.
   No correspondent of record was retrievable for any of the ten recordings. This is the highest-value missing field: if one attorney or firm signed the 2008 Kajeet assignment, the 2021 SVB security interest, the 2024/2025 releases, and the 2025 Wireless Management Solutions assignment, that recurrence would be a strong signal. It can be neither confirmed nor excluded on the current record. Recommend direct Assignment Center pull before finalizing any enforcement or damages view.

4. Cascading transfers — NOT PRESENT.
   One ownership transfer (2025-01-29) against a 2007 priority date. No chain of consecutively-named LLCs, no <24-month daisy chain. The 2008–2021 lag is the opposite of cascading. (Reel [not retrieved] for the 2025 entry.)

5. Pre-litigation transfer — NOT PRESENT (as to this patent).
   The 2025-01-29 assignment to Wireless Management Solutions post-dates the family's assertion campaign (2019–2022) by ~3 years. No infringement suit naming US 7,881,697 was located; the campaign patents were '559 and '438. If a new Wireless Management Solutions complaint naming '697 surfaces, this signal would flip, since a 2025-01-29 transfer would then sit tightly against an assertion date.

6. Bankruptcy fire-sale — NOT PRESENT.
   No Chapter 7/11 filing for Kajeet was located. The 2024-10-03 and 2025-01-21 recordings are captioned "Release by Secured Party" — discharges of Draper Fisher Jurvetson and SVB liens — not foreclosure transfers or §363 sales. Kajeet also continued filing and receiving patents through 2025.

7. Privateering — NOT PRESENT.
   Kajeet litigated in its own name against operating competitors (Gen Digital/NortonLifeLock, Trend Micro, Cujo, Roqos, Asavie, Qustodio). There is no evidence of an operating company funding a shell to sue on its behalf in this chain. (The reverse pattern — an operating company moving patents out to an LLC after its campaign largely collapsed — is the scenario to keep watching.)

8. Defensive aggregator — NOT PRESENT.
   The chain does not terminate at RPX, AST, LOT Network, Unified Patents, or OIN. It terminates at a private LLC.

Verdict

NPE — moderate confidence.

Two things drive the call. First, the sole ownership transfer in the patent's 18-year life is Kajeet, Inc. → Wireless Management Solutions, LLC on 2025-01-29, moving the entire ~45-asset family to a non-operating LLC, after a sequence of lien releases (2024-10-03 DFJ; 2025-01-21 SVB) engineered clean title — the classic shape of a monetization transfer, though the LLC may equally be a Kajeet captive. Second, the family has an established assertion pedigree: a documented multi-defendant "parental controls" campaign by Kajeet (2019–2022, incl. Kajeet v. Roqos, Kajeet v. Trend Micro, Kajeet v. Cujo) and an IPR on a sibling patent, so this portfolio is already understood by Unified Patents and RPX as an assertion asset. The confidence is only moderate, not high, because the standard NPE-list match is absent, there is no verified suit by Wireless Management Solutions, and I could not retrieve a single reel/frame number or correspondent name — the two fields (recurring correspondent, transfer-to-asserter timing) that would settle the question.

Verification links: USPTO Assignment Center search — https://assignmentcenter.uspto.gov/ (search "7881697"; the mirrored index is https://assignment.uspto.gov/patent/index.html). Patent record and full legal-events list — https://patents.google.com/patent/US7881697/en.

Open items to close before relying on this: (1) reel/frame and correspondent for all ten recordings listed above; (2) confirmation of the corporate relationship, if any, between Kajeet, Inc. and Wireless Management Solutions, LLC (state LLC registry / Kajeet SEC or press disclosures); (3) whether any 2025–2026 complaint names US 7,881,697, which would convert Signal 5 to present and lift the verdict to high confidence.

I'll research the cited prior art for US 7,881,697. Let me run several targeted searches.

Let me try to pull the citation list directly from primary sources.

I have the citation list from Justia. Let me now verify the full list and get details on the key references.

Prior-Art Analysis — US 7,881,697 B2

Task: Identify the prior art cited against/within US 7,881,697 and map it to the claims under 35 U.S.C. § 102.

⚠️ Scope and source caveats (read first)

1. Tool limit reached. I retrieved the front-page citation list from a live Justia record but then hit the search step limit before I could (a) open each cited reference individually, or (b) run the USPTO Patent Public Search / Patent Center "References Cited" view. Nothing below should be treated as a completed, per-reference verification.
2. What is verified vs. inferred. In the tables, the patent numbers, dates, and inventor surnames are transcribed from the live Justia "Referenced Cited" record for US 7,881,697. The titles/descriptions and § 102 mappings are my analytical inferences and are flagged accordingly. Where I do not have high confidence in a reference's subject matter, I say so.
3. The list may be incomplete. The retrieved Justia snippet truncated at the entry WO0208498… on the foreign-document side. The authoritative list is the front page of the issued patent and the USPTO IFW (IDS + PTO-892).
4. Legal framework. Priority is 2007-06-28 and this application was filed 2008-02-06 — well before the AIA first-to-file changeover. Pre-AIA § 102 governs (§ 102(a), (b), (e), and pre-AIA § 103). References published after 2007-06-28 cannot be § 102(a)/(b) art; they can only matter under § 102(e) if their effective U.S. filing date precedes the priority date.
5. Citing a reference ≠ rejecting on it. Front-page citations include applicant-submitted IDS art and background art that the examiner never used. The '697 patent issued with all 20 claims intact, which on its face suggests no cited reference was held anticipatory.

A. U.S. patent documents cited in US 7,881,697

B. Foreign patent documents cited

(The JP/KR entries use the era-year numbering as rendered in the Justia record — e.g., "13-134689" = Heisei 13 = 2001.)

C. Which references are the strongest § 102 candidates, and on which claims

Because anticipation requires a single reference disclosing every element, the realistic § 102 candidates here are narrow. Ranked by plausible overlap with the elemental structure of the independent claims:

Claim 1 requires three things together: (i) an administrator wallet storing value; (ii) a function manager; (iii) a global permission rule and a local payment-allocation rule.

• US 7,330,717 (Gidron et al.) — best candidate for the rule engine, weakest for the wallet. If this reference is the Boston Communications-style "supervisory control over wireless phone usage" patent, it discloses administrator-set permission/restriction rules applied to a subscriber device in real time — i.e., the "global rule … specifies whether a function is permitted" element of claims 1, 14, and 18. On its face it does not appear to disclose a second, funding wallet with a payment-allocation rule, so it is more naturally a § 103 primary reference than a standalone § 102 anticipation. Its § 102(e) date depends on a U.S. filing before 2007-06-28 — verify.
• US 6,957,058 (Chan et al.) — best candidate for the wallet/funding elements. A prepaid-card system with a stored-value account, real-time debiting, and replenishment maps well onto the "electronically storing units of value" element of claims 1, 14, and 18 and onto dependent claim 12 (automatic, periodic/level-triggered transfers). If it also discloses a sponsor account that backstops a user account, it reaches the administrator-wallet fallback of dependent claims 2–3. This is the reference most worth reading in full.
• US 5,221,838 (Gutman et al.) and US 6,885,877 (Ozaki et al.) — these are classic "electronic wallet"/electronic-purse references. They anticipate only the wallet-storing-value element (claim preambles); neither appears to disclose a function manager or global/local rule split. Expect them to be cited as § 103 background, not standalone § 102 art.
• US 2005/0216424 A1 (Gandre et al.) — if this is a promotions/loyalty-credit disclosure, it is the only listed U.S. reference with a plausible read on claim 18's "promotional wallet … until a predetermined limit has been met." Given the specification's thin disclosure of the "predetermined limit," this reference is directly relevant to the § 112 written-description exposure flagged in the earlier analysis.
• US 2007/0125840 A1 (Law et al.) — the closest-in-time U.S. publication (2007-06-07, three weeks before priority). Worth checking for account-funding/transfer disclosures bearing on claims 11–13 (transfer/gift functions).
• US 2008/0033880 A1 (Fiebiger et al.) — cannot be § 102(a)/(b) art (published after priority). Only relevant if it qualifies under § 102(e) via a pre-2007-06-28 U.S. filing. If it does, it postdates nothing else in the list and is a candidate for the cl. 1/14 rule-manager elements.

Claims with no clear anticipatory art in this list: independent claim 14's "dynamic wallet … accessible by a financier … represented by a unique identifier" (third-party sponsor wallet not tied to a device) and claim 18's capped promotional wallet have the thinnest coverage in the cited set. That is consistent with the earlier observation that claims 14 and 18 are the more exposed claims — but on these citations the exposure comes more from § 103 combinations than from clean § 102 anticipation.

D. What I could not do, and what would settle it

• ❌ I could not open the individual references to confirm titles, abstracts, or the specific passages the examiner/inventor relied on. Every "subject matter" description above other than the numbers/dates is my trained-knowledge inference and is unverified in this session. In particular I could not verify the titles or content of US 5,285,382, US 6,990,182, US 7,155,411, US 2001/0007983, US 2003/0026404, US 2003/0055785, US 2004/0143550, US 2004/0229600, US 2005/0216424, US 2007/0003034, US 2007/0058812, US 2007/0060100, US 2007/0125840, and US 2008/0033880.
• ❌ I could not retrieve the complete foreign list (truncated at WO 02/08498…).
• ❌ I could not confirm whether the earlier parent application 11/824,336 (which issued as US 7,945,238) cited a different or larger art set, which matters because claims carried over from the parent can be attacked with the parent's own art.

Recommended next steps (in priority order):

1. USPTO Patent Public Search / Patent Center → US 7,881,697 → "References Cited" and the IFW PTO-892 (examiner-cited) vs. the IDS (applicant-cited), to separate what the examiner actually relied on.
2. Pull the full text of US 6,957,058 and US 7,330,717 first — they are the two references most likely to carry § 102/§ 103 weight against claims 1, 12, and the "global rule" element.
3. Confirm the exact pre-2007-06-28 U.S. filing dates for US 7,330,717 and US 2008/0033880 (the two post-priority publications) to fix their § 102(e) status.
4. Confirm the exact publication day of EP 1798659 (June 2007) against the 2007-06-28 priority date.
5. Check EP 1041520, FR 2863088, and the KR/JP family for stored-value-with-supervisor-account disclosures, since foreign art is often where multi-account funding models appear.

I can complete the per-reference verification pass if you re-run me with fresh search steps.

I'll research the prior art landscape before building the §103 analysis. Let me run several targeted searches.

Strong prior-art references are surfacing. Let me firm up the key ones and check whether any PTAB proceeding has already mapped prior art against this family.

Obviousness Analysis — US 7,881,697 B2 under 35 U.S.C. § 103

I. A note on the "Prior Art section" and source discipline

Flag first, per your rules: the prompt directs me to "use the results from the Prior Art section of this page," but no discrete prior-art section was supplied in this pass — I received the earlier-generated summary/litigation sections and the full patent text only. I therefore reconstructed the prior-art universe from three verifiable sources and will label which is which:

1. The patent's own admitted background art (US 7,881,697, col. describing prepaid services, rollover minutes, auto‑refill, unlimited bundles, spend alerts, sub‑accounts/affinity accounts, and the Telcordia™ Converged Real‑Time Charging system).
2. References appearing on the face of sister applications in the same family — surfaced in a search of US 8,774,755 (a Kajeet continuation), which carries a large enumerated U.S. reference list (patents.google.com/patent/US8774755).
3. References I retrieved and read directly (identifiable below by URL).

I could not complete three intended searches (the BCG granted‑patent text, the full text of US 2006/0276180, and the Gen Digital v. Kajeet IPR2022‑00001 grounds) because I hit the tool step limit. Where I rely on a reference only because it appeared in a cited‑reference list rather than a full‑text read, I say so. Dates and claim counts stated below are from the sources I actually retrieved; treat grant dates after 2007‑06‑28 as irrelevant to §102(b) but relevant to §102(e) only if the underlying application predates the invention date.

Governing law: The '697 was filed 2008‑02‑06 with priority to 2007‑06‑28, so pre‑AIA § 102/§ 103 apply, and KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007) governs the obviousness inquiry. The § 102(b) one‑year bar falls at 2006‑06‑28; the effective filing date for § 102(a)/(e) is 2007‑06‑28.

II. Person Having Ordinary Skill in the Art (POSITA)

A POSITA here is an engineer or system architect with a bachelor's degree in electrical engineering, computer science, or equivalent, plus 2–4 years' experience designing or integrating wireless prepaid/postpaid rating, charging, and network policy‑control systems (e.g., IN/WIN platforms, IS‑41/IS‑826 triggers, SCP/AAA policy engines), or equivalent practical experience. This is a mature, integration‑heavy art: by 2003–2006 the elemental building blocks — prepaid balances, per‑number screening lists, real‑time rating engines, threshold alerts, and web provisioning portals — were standard and well documented (see the BCG and Telcordia references below).

III. The prior-art landscape relevant to the independent claims

Also material — the Kajeet/Telcordia case study. Telcordia's own published case study states that Kajeet's commercial system (built on Telcordia's hosted Service Delivery Suite, implemented in 2006 and beta‑tested with ~100 users in August 2006) included "WalletManager to determine how much can be spent, designate who pays for what, transfer money between parents' and children's e‑wallets, and cut off services when spending limits are reached," plus ContactManager and TimeManager (telcorda.com case study). This is a double‑edged document: it corroborates that the platform that enabled the claimed system was third‑party technology predating the June 2007 priority date (supporting § 103), while simultaneously raising § 102(a)/(b) public‑use/derivation questions against the applicant. Anyone contesting validity should run this down carefully; I flag it rather than opine.

IV. Claim‑by‑claim § 103 analysis

Independent Claim 1 — administrator wallet + two‑tier rule engine

Claim 1 requires: (a) an administrator wallet storing units of value, accessible by an administrator, associated with at least the device; and (b) a function manager for multiple device functions, carrying (i) a global rule specifying whether a function is permitted and (ii) a local rule specifying whether the charge is paid by the user or the administrator wallet.

Primary combination: US 7,337,396 in view of US 2005/0282559 (and optionally Telcordia 2007/0293191).

• US 7,337,396 discloses the two‑account structure — the secured account (password‑held by the benefactor) is, in substance, the claimed "administrator wallet," and the handset's associated lists supply the payment‑allocation rule ("calls … to a number of the secured list … debited to the secured account"). Its abstract and specification state this expressly.
• US 7,337,396 further discloses an asymmetric permission rule: 911 calls are connected "regardless [of] the credit in either account" — i.e., a rule that determines permission independent of any wallet balance. That is the claimed global rule in nascent form.
• US 2005/0282559 (BCG) supplies the full articulation of the permission layer: supervisor‑defined profiles, allowed/blocked number lists, time‑of‑day restrictions, and Boolean combinations — i.e., "a global rule that specifies whether a function is permitted."
• Telcordia 2007/0293191 additionally discloses real‑time rating with configurable rules applied "by priority" and shared group balances.

Motivation to combine. Both references are in the same field (wireless subscriber usage control/charging), address the same problem (a payer wanting to cap a user's spend while preserving essential connectivity), and are combinable by simple configuration: BCG's permission rules and US 7,337,396's account‑selection rules are two orthogonal attributes of the same call‑processing decision point (the switch/service manager of FIG. 1). A POSITA implementing BCG's profile system on the US 7,337,396 dual‑account switch would necessarily produce a system in which one rule set decides whether the call proceeds and another decides which account pays — the exact two‑tier structure of claim 1. Under KSR, this is "a combination of familiar elements according to known methods … yield[ing] predictable results." The patent's own Background concedes that Telcordia's system placed "limited real‑time controls" over accounts and limited a child's spending "within a set of parameters," which narrows the gap claim 1 must bridge to essentially the naming of two rule tiers.

Best non‑obviousness argument for the patentee: no single reference uses two formally separate rule classes ("global" vs. "local") with the express statement that the local rule governs who pays rather than whether the function is allowed. That is a genuine, if narrow, structural distinction — and it is the natural battleground.

Dependent Claims 2–13

Claim 2 (admin wallet pays if user cannot). US 7,337,396 expressly contemplates the secured account being charged when the dependent account lacks credit (the caller is prompted for the secured password; a home‑location number can be charged as a "safety net"). Alternatively, US 6,584,183 ("if … insufficient funds in a pre‑paid account … a message is generated … requesting authorization to charge an additional fee") discloses the fallback directly. Obvious.

Claim 3 (reverse fallback — user wallet pays if admin wallet is short). US 7,881,697's own specification admits the arrangement "could be reversed," describing it as a design choice. The specification statement is an admission that the reversal was within the skill of the art. Combined with US 7,337,396's multi‑account bounce logic, obvious (mere reversal of a known priority order = KSR "simple substitution … known element for another").

Claim 4 (charge card backstop). US 7,249,092 (American Express subsidiary card with controlled spending) combined with US 7,337,396. Charge‑card‑funded prepaid top‑up and auto‑refill are admitted prior art in the '697 Background ("automatically bills some amount to a credit card to recharge the user's prepaid account"). Strong § 103 case.

Claim 5 (units of value = credits for services/applications). Prepaid airtime units, game credits, and content credits are ubiquitous and effectively admitted. Obvious.

Claims 6 & 7 (list‑based allocation: admin pays for designated contacts; user pays for listed names/numbers). This is the core of US 7,337,396 (secured list vs. dependent list, each mapped to a different account) and of US 6,788,927 (financing‑party list + direction parameter). Claim 7 in particular is close to anticipation. Very strong § 103 case; potential § 102 exposure.

Claim 8 (promotional wallet used first if funded). Applying bonus/free minutes before paid balances is longstanding prepaid practice; the '697 specification itself describes the "10 free voice minutes" promotional wallet and states the promotional wallet "would then be used first." US 2006/0116105 (Comverse, multiple identities with real‑time rating) and Telcordia's rating‑rule priority are corroborating. Obvious.

Claim 9 (low‑balance alert). The '697 Background admits alerts as prior art ("a parent could be alerted when a child has spent more than $10 on text messages"). Telcordia 2007/0293191 claims real‑time threshold notification. Anticipated/admitted.

Claim 10 (web‑based function manager). US 7,337,396 discloses a customer logging "onto a web page … [to] obtain the status of the accounts … and … modify … the telephone numbers of the secured list" — i.e., web administration of the payment/permission rules. BCG likewise discloses a customer console (web‑based GUI/portlet). Obvious.

Claims 11–12 (transfers, including automatic/periodic "allowance" transfers). US 2007/0077911 (transferring prepaid units between accounts) plus the patent's own admission that auto‑refill (scheduled credit‑card top‑up) was known. Automating a manual transfer on a schedule is a predictable application of known automation to a known transfer. Obvious.

Claim 13 (gift function — third party deposits value and messages the recipient). Gift/prepaid‑card top‑up and gifting of airtime are old; US 2007/0125840 (extended e‑wallet management) and the general electronic‑wallet references support the deposit mechanism. The added "communicate … regarding the deposit" is a conventional notification. Obvious, though this claim has slightly more room than the others if no reference is found combining deposit + personalized message.

Independent Claim 14 — dynamic wallet controlled by a third‑party financier

Primary combination: US 6,788,927 in view of US 2005/0282559 (or Telcordia 2007/0293191).

• US 6,788,927 discloses a financing‑party account that pays for a designated subscriber's calls on designated numbers, from a prepaid account, without real‑time user input — the "dynamic wallet accessible by a financier" paying per a "local rule." Claim 1 of US 6,788,927 recites the database of financing‑party numbers, financed‑party numbers, and direction parameters, with charges deducted from the financing party's prepaid account.
• US 2004/0225561 (Nokia) discloses the sponsor defining the allowed number set and the sponsor bearing billing — the same architecture in the more familiar parent/child or employer/employee framing.
• For the "represented by a unique identifier" (rather than being tied to a device) limitation, the device‑independent wallet art — US 7,206,769 (Thomson), US 7,155,411 (Microsoft), US 7,024,390 (Fujitsu) — teaches portable electronic wallets identified by an ID and attachable to multiple payees. The '697 specification itself states the wallet "just needs to have a unique identifier."
• The global‑rule half of claim 14 is supplied by US 2005/0282559/Telcordia (permission), which the patent's FIG. 2 also requires ("a dynamic wallet would not be able to authorize services … blocked by the administrator").

Motivation to combine. Combining a third‑party‑funded wallet with an administrator's permission engine is the natural, low‑risk union of two references that each already describe one half of the same problem ("a sponsor will pay, but only within the administrator's permitted envelope"). Both are in the wireless charging field; the combination merely requires the sponsor's wallet to be consulted after the permission check — an ordering step the Telcordia reference already implements through rule priority. Result is predictable.

Claims 15 & 17 (financier‑accessible funding function to associate the wallet and set/change the local rule). US 6,788,927 expressly discloses web‑based and DTMF provisioning by which the financing party populates the financing‑party payment database; US 7,337,396 discloses web modification of the lists. Obvious.

Claim 16 (three‑way split: user, dynamic wallet, administrator wallet). US 7,337,396 (two accounts) + US 6,788,927 (third‑party account) + Telcordia's "share balances among a group." Adding a third funding tier to a two‑tier allocation is a predictable extension with a clear incentive (grandparent/family gifting, corporate sponsorship). Obvious, moderately strong.

Independent Claim 18 — promotional wallet with a predetermined limit

Claim 18 requires: a global permission rule; a local rule designating payment by the user or a promotional wallet; and if the function is promotional, the promotional wallet pays "until a predetermined limit has been met."

Primary combination: Telcordia 2007/0293191 (or the admitted Telcordia Converging Real‑Time Charging system) in view of US 2005/0282559, plus the ubiquitous prepaid "bonus/free minutes burned first" practice (US 2006/0116105).

• Free/bonus airtime and content credits that expire or cap out after a fixed quantity are ancient in prepaid telephony; the '697 specification itself gives the "10 free voice minutes … used first" example as an existing promotional construct.
• Telcordia supplies the global permission rule (a promotional wallet cannot be used for a blocked 900‑number, as the '697 specification concedes).
• The only genuinely contestable phrase is "predetermined limit," and its specification support is thin — the patent gives no mechanism for setting, tracking, or resetting the limit. That cuts both ways: thin disclosure helps the patentee on § 103 (harder to show the reference discloses the exact limitation) but exposes the claim to § 112 written‑description/indefiniteness attack (as the earlier-generated analyst observations already noted).

Claims 19 & 20. Claim 19 (user wallet pays after the limit) is a straight application of the US 7,337,396 bounce logic. Claim 20 (administrator controls whether the promotional function is permitted) is anticipated by the notion that administrator/global rules gate promotions — expressly stated in the '697 specification and in BCG's profile‑based permissions. Obvious.

V. Consolidated motivation‑to‑combine analysis (KSR factors)

A POSITA would have combined the above references for reasons that are articulated, not hindsight‑driven:

1. Same field of endeavor. All primary references are wireless subscriber rating/charging/usage‑control systems, sharing the same network decision points (MSC/SCP/service manager) recited in the '697's FIG. 1.
2. Same problem, same solution direction. Each reference targets the tension the '697 Background describes: cap spending (BCG profiles, US 7,337,396 dependent account) without eliminating essential connectivity (US 7,337,396 "safety net," US 6,584,183 sponsored calls, the '697 Background's own framing of the emergency‑call problem).
3. Predictable combination of known elements. BCG/Telcordia (permission) and US 7,337,396/US 6,788,927 (payment allocation) are orthogonal attributes of one call‑processing decision. KSR holds that "if a technique has been used to improve one device, and a person of ordinary skill … would recognize that it would improve similar devices in the same way, using the technique is obvious."
4. Design incentive / market pressure. The telco "family plan," MVNO "tween" market, and employer‑liability concerns created an explicit, documented demand (the Kajeet/Telcordia case study describes exactly this: parents wanting to "designate who pays for what"). KSR recognizes market demand as a motivation.
5. The patent's own admissions. The '697 Background concedes rollover minutes, auto‑refill, unlimited bundles, spend alerts, sub‑accounts, affinity accounts, and Telcordia's real‑time parental controls. These admissions shrink the distance from the prior art and are usable as applicant admissions under KSR.

VI. Where the § 103 case is weakest (for the patentee's benefit, and for accuracy)

1. The two formally distinct rule classes. No reference I found uses "global rule"/"local rule" as separate claim elements with the express division of labor (permission vs. payer). A patentee will argue the combination produces a new architecture, not a mere aggregation, and will point to the absence of any reference teaching that the payment rule must be subordinated to the permission rule. This is the strongest non‑obviousness argument.
2. Claim 18's "predetermined limit." The record I assembled does not establish a reference disclosing a promotional wallet that pays a defined function "until a predetermined limit has been met" with the residual allocated elsewhere. If no such reference exists, claim 18 (and its dependents) may survive § 103 while being vulnerable under § 112.
3. Claim 14's "dynamic wallet … represented by a unique identifier" not tied to a device. The close references (US 6,788,927, US 2004/0225561) tie sponsor payment to phone numbers, which is a form of device association. The patentee can argue the device‑independent, ID‑keyed wallet is a real structural difference. The counter is the general e‑wallet art (US 7,206,769; US 7,155,411; US 7,024,390).
4. Prosecution‑history/considered‑references problem. Many of the strongest secondary references (Comverse, Boncle, UTStarcom, Coulter, Microsoft, Thomson, Fujitsu) appear on the face of the family's own continuity applications. If they were before the examiner, the examiner's allowance implies the applicant argued around them. I could not verify from my retrievals which of these were specifically before the examiner of the '697 or of its parent 11/824,336 — this matters enormously and should be checked against the file wrappers before relying on this analysis in a validity challenge. The references most likely not considered — US 7,337,396 (granted 2008‑02‑19) and US 6,788,927 — are, notably, among the most damaging.

VII. Contradictions / corrections to prior sections

• No contradiction found between the patent text I was given and the references retrieved; the family continuity relationships and claim counts stated in the earlier "Patent summary" match.
• One reconciliation: the earlier summary listed the Telcordia Converged Real‑Time Charging system only as admitted background art. Searching confirms it is also patented third‑party art (Telcordia US 2007/0293191 A1, prov. 2006‑05‑26). That upgrades it from a mere admission to a usable § 102(e)/§ 103 reference, which strengthens the obviousness case beyond what the earlier summary implied.
• Consistency with the litigation section: nothing in this § 103 analysis depends on the pending/possible litigation. Note, however, that the earlier section's finding — that Kajeet's enforcement campaign was publicly framed around US 8,667,559 rather than the '697 — is consistent with the possibility that the '697's claims were regarded as narrower or more exposed, which the above claim‑level analysis supports.

VIII. Bottom line

• Claims 1–13: a strong § 103 case exists via US 7,337,396 (primary) + US 2005/0282559 (BCG) ± Telcordia 2007/0293191 ± US 6,788,927. Claim 1's two‑tier rule split is the only real hurdle, and it is bridgeable by the "permission rules on a dual‑account switch" combination; claims 6, 7, and 9 are close to § 102.
• Claims 14–17: strong § 103 via US 6,788,927 + US 2004/0225561 + general e‑wallet art, with claim 14's "device‑independent unique identifier" the chief point of attack.
• Claims 18–20: the weakest link in the prior art I assembled, because "predetermined limit" lacks a clean reference — but the specification's thin support for that term makes them vulnerable on § 112 instead. Watch the IPR/validity record for whatever the challengers actually plead.

Limitations of this analysis, stated plainly: I could not complete the searches for the BCG granted‑patent text, the full text of US 2006/0276180, or the Gen Digital v. Kajeet IPR2022‑00001 grounds (which challenged a sibling patent and would reveal which prior art a sophisticated petitioner considered best). I also could not verify which references were before the examiner during prosecution of the '697 or its parent. Both gaps should be closed before relying on this in a validity opinion, an IPR petition, or an invalidity contention.