US 8774755

I'll verify this patent against live sources, including any 2026 CAFC activity, before summarizing.

Let me check for litigation and appellate activity, plus the claim text.

Let me try to pull the actual claim text and any litigation record.

Verification note

I searched for US 8774755 specifically (Google Patents full text, USPTO/PTAB document hits, and Federal Circuit 2026 round-ups). No 2026 CAFC docket or opinion referencing US 8774755 surfaced in any of my searches. Absence of results in a search is not proof of absence, so I cannot affirmatively confirm or rule out a pending 2026 appeal — I simply found no record of one. Everything below is drawn from the authoritative full text you supplied plus corroborating records surfaced in search.

Bibliographic data — US 8,774,755 B1

Priority chain (verbatim from the specification): 13/786,974 → continuation of 13/763,348 (filed Feb. 8, 2013) → continuation of 13/603,218 (filed Sep. 4, 2012) → continuation of 12/950,379 (filed Nov. 19, 2010, now US 8,285,249) → continuation of 11/881,460 (filed Jul. 26, 2007, now US 7,899,438) → continuation-in-part of 11/824,336 (filed Jun. 28, 2007, now US 7,945,238).

Family context: The patent is one of ~19 co-pending applications filed the same day (Mar. 6, 2013) all titled "Feature Management of a Communication Device," and is related to 12/027,240 (now US 7,881,697) and 12/950,291 (now US 8,078,140). Same-day siblings include US 8,774,754 (also issued Jul. 8, 2014). Continuations in this line later produced US 9,237,433, US 10,285,025, US 11,206,516, and US 11,516,629, among others.

Litigation record on the Google Patents page: the family is flagged as having litigation, with a US case noted in the California Central District Court, case 2:18-cv-03899, and a Darts-IP worldwide family litigation link (family 40161185). I did not locate any 2026 filing or appellate docket tied to this patent number.

Abstract (verbatim)

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

Plain-language overview of the disclosed invention

The patent describes a network-side system for real-time feature management of a communication device (exemplified by a prepaid cell phone) by an administrator (parent, employer, guardian, etc.):

• Wallets, not accounts. Unlike a conventional account, multiple "wallets" can attach to one device, one wallet can span multiple devices, and wallets can be dynamic (tied to no particular device). At minimum each device has a user wallet and an administrator wallet, with an order of precedence governing which wallet pays, and back-up wallets covering a low/zero balance.
• Global rules + local rules. Global (carrier-level) rules are checked first (e.g., 911 calls always allowed and free; 900-number calls blocked); local rules then govern specifics — allowed/blocked number lists, who pays for which call/text, feature enablement, time-of-day limits.
• Enforcement architecture. FIG. 1 (voice) uses a Service Manager triggered by the O-MSC; FIG. 2 (data) uses a Policy Enforcement Point (PEP) 28 working with a Policy Decision Point (PDP) 29 to accept, reject, redirect/rewrite, or degrade a service request, notifying the subscriber and/or requester on a policy failure.
• Feature management UI. FIGs. 3–5 show a Contact Manager and feature pages letting an administrator turn features on/off or meter them (downloads, feeds/text messaging, mobile web, picture messaging, instant messaging), set group-wide switches, and use an "Override Restrictions" control to carve exceptions out of otherwise applicable restrictions.
• Promotional and dynamic wallets slot into the payment hierarchy, but are still subject to the global/local rule screening (a promotional wallet cannot be used to call a blocked 900 number).

Independent claims — uncertainty flagged

I must be explicit here: the full text you supplied ends mid-sentence in the Detailed Description ("…each device requires at least two wallets to be associated wi…") and does not include the claims. My searches did not surface the verbatim claim set for US 8,774,755. I therefore cannot give you a reliable, quotable plain-language reading of each independent claim, and I will not reconstruct claim language from memory.

What I can state with grounding:

1. The patent's own framing (Technical Field, Abstract, Summary-style passages) indicates the claimed subject matter is a computing-device/system-plus-method implementation of real-time policy establishment and enforcement, with the recurring elements being a computing device, an administrator, a user, a policy/rule, and a feature or function of the device — consistent with the Google Patents "prior art keywords" string (computing device, administrator, user, policy, rule).
2. The disclosure repeatedly distinguishes claims that produce "two separate decisions" — global rules applied in order relative to local rules — which is the kind of limitation one would expect to see recited in at least one independent claim.
3. Given the family's pattern (many same-title continuations issued the same day), the independent claims of the '755 patent are highly likely to be drafted as apparatus/system claims to a computing device plus corresponding method claims, but I cannot confirm the claim count, the exact preamble, or the specific limitations without the claim text.

To close this gap, the authoritative sources to pull are: the full-text claims on the Google Patents page for US8774755B1 (the "Claims" section, which was not included in the excerpt provided), and the USPTO PatentCenter/Patent Public Search record for application 13/786,974.

Summary of litigation/timing items I could and could not confirm

• Confirmed: The patent has a litigation flag; one noted US case is California Central District Court 2:18-cv-03899. Assignments to Silicon Valley Bank (2021-12-17), release (2025-01-21), and assignment to Wireless Management Solutions, LLC (2025-01-29) appear in the record.
• Not confirmed: Any 2026 CAFC docket for US 8,774,755. My targeted sweep of 2026 Federal Circuit decisions and summaries produced no hit for this patent number, and a search for "Wireless Management Solutions" infringement suits returned no results. Treat this as "no evidence found," not as "no such proceeding exists."

If you can supply the claims section of the '755 patent (or its PatentCenter claim listing), I can produce the requested limitation-by-limitation plain-language breakdown of each independent claim with direct quotations.

I'll search for litigation involving US patent 8774755 specifically. Let me run several targeted searches.

Let me dig deeper into the identified case and check for any additional litigation, including from the current assignee.

Let me verify the specifics and check for other cases asserting this patent.

Litigation Involving U.S. Patent No. 8,774,755

Summary

Based on the sources I was able to search (Stanford NPE Litigation Database, the Unified Patents litigation portal link embedded in the Google Patents record, UniCourt, Patexia, and news/RPX coverage), only one lawsuit is specifically identified as asserting U.S. Patent No. 8,774,755. I could not confirm any additional case in which the '755 patent itself was pleaded.

Case Identified

Kajeet, Inc. v. Mobicip, LLC

Sources:

• Stanford NPE Litigation Database, patent page for 8774755: https://npe.law.stanford.edu/patent/8774755 (lists the single case: Kajeet, Inc. v. Mobicip, LLC, 2:18-cv-03899, C.D. Cal.)
• Stanford NPE Litigation Database case page: https://npe.law.stanford.edu/case/[200304](/patent/200304) (identifies asserted patents as 8,712,371; 8,774,755; 8,667,559)
• UniCourt docket summary: https://unicourt.com/case/pc-db1-kajeet-inc-v-mobicip-llc-[758131](/patent/758131)
• Patexia docket documents: https://services.patexia.com/lawsuits/Kajeet-Inc-v-Mobicip-LLC-id-[112865](/patent/112865)/documents
• Google Patents "litigation" link for US8774755 (points to the Unified Patents case page): https://portal.unifiedpatents.com/litigation/California%20Central%20District%20Court/case/2%3A18-cv-03899

Notable early docket activity (2:18-cv-03899)

• The court repeatedly denied Kajeet's requests to recognize Wilson Turner Kosmo LLP as local counsel and denied several pro hac vice applications because local counsel did not maintain an office in the district (Local Rule 83-2.1.3.4).
• On July 10, 2018, the court struck a stipulation extending the defendant's answer deadline and ordered Kajeet to retain in-district local counsel by July 30, 2018, "or a failure to do so will result in the dismissal of this action." The answer deadline was continued to August 2, 2018.

Important caveat: I was unable to retrieve a reliable post-August 2018 docket or a final disposition (settlement, dismissal, judgment, etc.) for this case. I am not able to confirm with high confidence how it terminated. This would need to be verified directly on PACER (C.D. Cal. 2:18-cv-03899) or via a current litigation database.

Important Distinction — Other Kajeet Cases Do NOT Involve the '755 Patent

Kajeet, Inc. conducted a broader "parental controls" patent-enforcement campaign between roughly 2018 and 2022 against numerous defendants, but the cases I found asserted different Kajeet patents — most commonly U.S. 8,667,559 (the '559 patent), U.S. 8,712,371 (the '371 patent), U.S. 7,899,438 (the '438 patent), and U.S. 8,706,079 (the '079 patent). I did not find the '755 patent pleaded in those actions. Do not treat the following as '755 litigation:

• Kajeet, Inc. v. Liminex, Inc. (d/b/a GoGuardian), 2:18-cv-00643 (C.D. Cal.) — asserted the '371 and '559 patents
• Kajeet, Inc. v. Qustodio (C.D. Cal.) — dismissed on patent ineligibility (referenced in Stradling's case description)
• Kajeet, Inc. v. Infoweise Pty., Ltd., 6:21-cv-00704-ADA (W.D. Tex.) — asserted the '559 patent
• Kajeet, Inc. v. Cujo LLC, 2:20-cv-00253 (C.D. Cal.) — asserted the '438/'559 family
• Kajeet, Inc. v. Roqos, Inc., 1:19-cv-02371 (D. Del.) — asserted the '559/'438 patents
• Kajeet, Inc. v. NortonLifeLock Inc., 1:20-cv-01339-MN (D. Del.) and related 1:19-cv-02370 — '559 family
• Kajeet, Inc. v. Trend Micro, Inc., 6:21-cv-00389-ADA (W.D. Tex.) — '559 family
• Kajeet, Inc. v. JAMF Software, LLC, 6:20-cv-00302 (W.D. Tex.) — different patent
• Kajeet, Inc. v. Lightspeed Solutions, LLC, 6:20-cv-00203 (W.D. Tex.) — different patent

These are listed only to show the campaign context and to prevent misattribution to the '755 patent.

Procedure- and Ownership-Related Notes (Not Litigation)

• Litigation flag on the patent record: The Google Patents page for US8774755 carries a "Family has litigation" flag and a Darts-IP worldwide-family-litigation link (family 40161185), consistent with the Mobicip case above.
• Ownership changes relevant to future enforcement risk (per Google Patents assignment records):
  • 2021-12-17: security interest to Silicon Valley Bank (assignor Kajeet, Inc.)
  • 2025-01-21: release by secured party (Silicon Valley Bank → Kajeet, Inc.)
  • 2025-01-29: assignment of interest to Wireless Management Solutions, LLC (assignor Kajeet, Inc.)
  • Current listed assignee: Wireless Management Solutions LLC
• The '755 patent is Active, with an adjusted expiration of July 15, 2027 (per the Google Patents record).

I found no litigation asserted by Wireless Management Solutions, LLC involving the '755 patent in the sources available to me. That absence may simply reflect limits in my searches and the recency of the 2025 assignment.

Bottom Line

• One lawsuit specifically involving U.S. 8,774,755 was identified: Kajeet, Inc. v. Mobicip, LLC, No. 2:18-cv-03899 (C.D. Cal., filed May 10, 2018), in which the '755 patent was asserted alongside U.S. 8,712,371 and U.S. 8,667,559.
• Outcome unknown to me with confidence — the docket material I retrieved ends at mid-2018 and shows the case pending; I could not confirm a later settlement, dismissal, or judgment.

If you need a definitive, current status, the authoritative step is a direct PACER pull of C.D. Cal. Case No. 2:18-cv-03899 (and a check of any later complaints filed by Wireless Management Solutions, LLC as the new assignee). I am explicitly flagging that I could not fully verify the terminal disposition from the sources available, rather than asserting one.

I'll verify the structured "no proceedings" default against live sources before writing this up.

Let me run additional targeted searches to check for any IPR/PGR/CBM on the '755 patent specifically, including family-level proceedings.

Let me verify two things: (1) whether any PTAB case ever named the '755 patent itself, and (2) an ambiguous "lapse for failure to pay maintenance fees" signal I saw that I can't yet attribute to a specific patent in this family.

Proceedings overview

Total AIA trial proceedings naming U.S. 8,774,755: 0. The structured USPTO ODP block states the ODP API returns no AIA trial proceedings for this patent, and my independent web sweep found nothing to contradict that: no IPR, PGR, or CBM petition has ever named the '755 patent as the challenged patent, so the breakdown is 0 active / 0 claims invalidated / 0 claims sustained / 0 settled / 0 institution-denied. The '755 patent has never been tested at the PTAB. That cuts in the patent owner's favor on the narrow question of PTAB history (no cancellation, no adverse FWD, no file-wrapper admissions), but it also means a defendant has a clean, unused IPR window and no estoppel running against it — subject only to the § 315(b) one-year bar for any party previously served. The patent is not hardened by repeated PTAB survival; it is simply untested. I flag one inconsistency in the record that I could not resolve (see "Unresolved record discrepancies" at the end).

Important — what my searches did find: two AIA proceedings against same-specification siblings in this family (all titled "Feature management of a communication device"), one of which canceled claims. Those are not proceedings on the '755, and I do not present them as such, but a defendant asserting or defending the '755 needs them. They are set out below under a clearly separated heading.

Proceedings on U.S. 8,774,755

None. No proceeding number exists to report, and I will not invent one. For the avoidance of doubt, the correct verification step is a patent-number search in PTAB E2E (https://ptabtrials.uspto.gov) and the PTAB Decisions page (https://www.uspto.gov/patents/ptab/decisions), both of which index by challenged patent number.

Family-adjacent proceedings (NOT on the '755) — highly material context

These challenge different patent numbers that share the '755's specification and priority chain. Do not cite them as '755 outcomes; do cite the art and the reasoning.

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

• Type: Inter Partes Review
• Challenged patent: U.S. 8,667,559 (a same-title sibling in the '755's continuation family) — not the '755
• Filed: 2021-10-01
• Status: Final Written Decision (terminated 2023-04-13); patent owner's claims canceled as to the challenged set, with a certificate reportedly issuing 2023-06-28
• Judge panel: Iftikhar Ahmed, Juliet Mitchell Dirba, Karl Easthom, Meredith Petravick; opinion authored by Petravick. Tech Center 2400, Art Unit 2437
• Petition grounds: § 103 obviousness in three grounds — (1) claims 1–2, 5–12, 27–29 over Putzolu (U.S. 6,578,076); (2) claims 2, 7, 8 over Putzolu in view of Rothman (U.S. 7,826,835); (3) claims 13–15, 18–21 over Bhat (US 2005/0021978). Challenged set: claims 1–2, 5–15, 18–21, 27–29
• Institution decision: Instituted 2022-04-21
• Final Written Decision: Issued 2023-04-13. The Board found the challenged claims unpatentable; third-party claim-level analysis of the resulting certificate identifies claim 27 (the method claim most commonly asserted in the parallel district court campaign) as canceled. I could not retrieve the FWD text itself, so I am not asserting a verified per-claim scorecard beyond that; treat the exact distribution of canceled vs. surviving dependent claims as unverified.
• Motion to Amend (notable for '755 purposes): Kajeet filed a revised contingent motion to amend. In its Preliminary Guidance the Board "disagree[d] with Patent Owner's argument that the specification discloses an alternative where enforcement is performed by a user device" (Paper 32 at 9), and Petitioner argued the amended claims lacked written description under § 112. Source: Petitioner's Sur-Reply (https://ptabdata.blob.core.windows.net/files/2022/IPR2022-[00001/2023](https://assignmentcenter.uspto.gov/search/patent/reelFrameDetail?reelFrame=1-2023)-01-26%20Kajeet%20Reply%20ISO%20Revised%20Motion%20to%20Amend.pdf). That is a party brief quoting the Board's preliminary guidance, not the FWD itself — weight it accordingly.
• Settlement / termination: No settlement; decided on the merits.
• Appeal: Not confirmed. I found no Federal Circuit docket or opinion on appeal from this FWD. Absence of a hit is not proof of absence.
• Defensive value: The '559 and '755 share one specification, so the Putzolu / Rothman / Bhat combination is validated, Board-tested § 103 art against these disclosure-level teachings. A defendant facing the '755 should start there. But the '559 is a different claim set than the '755; the art does not transfer automatically, and Gen Digital and its privies are estopped under § 315(e)(2) from re-running these grounds — a different petitioner is not.

Sources: DocketAlarm (https://www.docketalarm.com/cases/PTAB/IPR2022-00001/Gen_Digital_Inc._v._Kajeet_Inc/); Patexia (https://services.patexia.com/lawsuits/Gen-Digital--Inc-v-Kajeet-Inc-id-[155483](/patent/155483)).

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

• Type: Inter Partes Review
• Challenged patent: U.S. 7,899,438 (the '755's priority-chain ancestor: 11/881,460 → US 7,899,438; the '755 is a fourth-generation continuation of it) — not the '755
• Filed: 2022-11-10
• Status: Terminated–Settled (decision date 2023-09-01)
• Judge panel: Juliet Mitchell Dirba, Karl D. Easthom, Iftikhar Ahmed; authored by Dirba
• Petition grounds: Claims challenged were 1, 2, 3, 6, 10, 27, 33. The specific art and statutory bases are not confirmed from the sources I retrieved.
• Institution decision: 2023-05-12
• Final Written Decision: None. The proceeding terminated on settlement before an FWD.
• Settlement / termination: Terminated–Settled, 2023-09-01. Terms are confidential and not public.
• Appeal: None (no FWD to appeal).
• Defensive value: Low direct value — no claim-level ruling, no estoppel-generating FWD. Its significance is behavioral: it shows Kajeet settling an IPR (concurrently with its district-court campaign), and it shows a second, independent petitioner (Trend Micro) willing to attack this family.

Source: Patexia (https://services.patexia.com/lawsuits/Trend-Micro-Inc-v-Kajeet-Inc-id-[183366](/patent/183366)).

Strategic summary

Claim status of the '755 itself: 100% UNTESTED. No claim of U.S. 8,774,755 has been canceled, confirmed, or construed by the PTAB. There are no surviving-as-narrowed claims to list, because there has been no narrowing. I also restate a limitation from the earlier sections of this analysis that bears directly on PTAB work: the claim text of the '755 was not supplied in the authoritative full text (the excerpt ends mid-sentence in the Detailed Description), and my searches did not surface a verbatim claim set. Without the claims, no one — including me — can responsibly map the '559 invalidation art onto the '755. Pull the claims from Google Patents' "Claims" section (https://patents.google.com/patent/[US8774755](/patent/US8774755)) or PatentCenter for application 13/786,974 before committing to a petition.

Estoppel landscape. § 315(e)(2) estoppel from the two family proceedings attaches to Gen Digital/NortonLifeLock and its privies (as to the '559) and to Trend Micro and its privies (as to the '438, and only as to grounds actually raised, since there was no FWD — practically no § 315(e)(2) estoppel from a pre-FWD settlement). None of that estoppel touches the '755. For a defendant now facing the '755: the entire prior-art field is open, and the Putzolu/Rothman/Bhat package has never been run against these claims. The one timing constraint is § 315(b): a party served with a complaint asserting the '755 more than one year ago is time-barred absent joinder. Notably, the only defendant ever sued on the '755 — Mobicip, LLC, No. 2:18-cv-03899 (C.D. Cal., filed 2018-05-10) — never filed an IPR against it, and as a 2018-served defendant would have been time-barred after mid-2019. So the sole past defendant is not the source of any estoppel, and no third party has stepped in.

Pattern signals. (1) The same panel — Ahmed, Dirba, Easthom — sat on both family IPRs, with Petravick added on IPR2022-00001; that panel has already read this specification and already rejected Kajeet's argument that the spec supports device-side enforcement. (2) Kajeet has fought to the FWD once and settled once — it is neither an automatic settler nor an automatic appellant. (3) I found no defensive aggregator (e.g., Unified Patents) in the chain for the '755; the Google Patents litigation flag points to the Mobicip case and a Darts-IP family link (family 40161185). (4) Ownership has moved off the original patentee: Wireless Management Solutions, LLC took assignment from Kajeet (recorded 2025-01-29), which is the classic precondition for a new assertion campaign. I found no PTAB filings and no litigation by Wireless Management Solutions in the sources available to me — I am flagging that as "no evidence found," not as a negative finding.

The biggest structural point for a defendant: the '755 is a 2013-filed continuation in a family where the PTAB has already invalidated the commonly asserted '559 method claim and where a prior-generation sibling drew its own IPR. The specification is therefore heavily litigated and pre-scrubbed, while the '755's own claims are virgin. That is the paradigm case for a well-funded IPR petition — and also the paradigm case for a patent owner choosing to assert the '755 precisely because it has not been invalidated.

Unresolved record discrepancies (flagging, per instructions)

1. Possible maintenance-fee lapse — attribution unconfirmed. One search result surfaced Google Patents legal-event entries for a Kajeet-family patent reading "LAPS — Lapse for failure to pay maintenance fees," "PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES," with an effective date of 2026-02-04. I could not confirm which patent number those events attach to, and the snippet's page context mixed multiple family members. This directly conflicts with the '755 record supplied to me, which shows Status: Active, adjusted expiration 2027-07-15, and which is authoritative per the briefing. My working assumption is that the lapse pertains to a different Kajeet-family patent, but a defendant must verify this before investing in a petition, because a pre-2027 lapse would moot the whole exercise. Verify at USPTO PatentCenter / Maintenance Fee records for 8,774,755.
2. Mobicip outcome still unconfirmed. Consistent with the earlier section of this analysis, the C.D. Cal. docket material I retrieved ends in mid-2018 and shows the case pending; I could not confirm how it terminated. This matters for § 315(b)/privity analysis.
3. No CAFC activity on the '755 confirmed. No 2026 Federal Circuit docket or opinion referencing 8,774,755 surfaced. Absence of search results ≠ absence of a proceeding.

Recommended next steps

• Run the canonical check. Search patent number 8774755 in PTAB E2E (https://ptabtrials.uspto.gov) and the PTAB Decisions page (https://www.uspto.gov/patents/ptab/decisions) to confirm the zero count; then pull PACER for C.D. Cal. 2:18-cv-03899 for the Mobicip disposition, and check for any complaint filed by Wireless Management Solutions, LLC (its 2025-01-29 assignment makes a new campaign plausible).
• Resolve the maintenance-fee question first. If the '755 lapsed effective 2026-02-04, stop — there is no case to defend. If it is active through the listed 2027-07-15 adjusted expiration, the IPR window is short and a petition should be filed promptly.
• Get the '755 claims before doing anything else. The claims were absent from the authoritative text supplied. Until you can compare them to the '559 claims that IPR2022-00001 invalidated, you cannot tell whether the Putzolu/Rothman/Bhat package transfers.
• If you file, build on the family art but re-map it. Use Putzolu (U.S. 6,578,076), Rothman (U.S. 7,826,835), and Bhat (US 2005/0021978) as the starting combination — they are Board-tested against this specification — then add a primary reference if the '755's independent claims recite wallet/administrator-rule limitations that the '559 claims did not. Reuse the written-description attack on any device-side-enforcement amendment: the Board already signaled skepticism at Paper 32 in IPR2022-00001, and Kajeet's own first expert reportedly conceded the point.
• Track the Panel. Ahmed / Dirba / Easthom (plus Petravick) have adjudicated this family twice. Their familiarity is a genuine asset if you petition.
• Cite the FWD directly, don't paraphrase me. For the '559 outcome, link the FWD and certificate via PTAB E2E / PTAB Decisions; for any appeal, check CourtListener (https://www.courtlistener.com). I have deliberately not quoted FWD language I could not retrieve.

Bottom line for a defendant: "No IPR has ever been filed on U.S. 8,774,755. It is untested, not hardened — but its specification has already lost bad at the PTAB once, and the art that did it is in the public record."

I'll research the assignment record for US 8,774,755, focusing on the ownership chain, correspondents of record, and NPE signals.

Let me dig into the specific assignment records and the entities involved.

Let me examine the assignment records and IP owner profiles more closely.

I hit the tool-call limit before I could pull every detail, so I'll be explicit about what I could and could not verify. A key limitation up front: I could not retrieve the USPTO Assignment Center reel/frame numbers or the correspondent-of-record for any of the recorded events on this patent. Google Patents mirrors the legal events (dates + conveyance type + assignor + assignee) but not the reel/frame or correspondent fields. Treat the timeline below as confirmed-as-to-events but unconfirmed as-to-reel/frame and correspondent. Do not read the absence below as "no such data exists" — it means my accessible sources did not expose it.

Inventors

Pattern note — no fire-sale precursor found. The fire-sale tell you asked me to watch for (all inventors departing the original assignee within ~12 months of filing) is not present in the form of departures, but note the opposite pattern: these inventors stayed associated with the portfolio for years. Patent-profile aggregators show Baker, Geller, and Kesser each still tied to Kajeet entities across 14+ applications, plus 1 application each later recorded to Wireless Management Solutions, LLC (Chevy Chase, MD) — i.e., the same inventors' names carry through into the assignee-of-today's portfolio. That is consistent with an internal family, not an inventor walkout.

(I could not confirm exact employment contracts or contemporaneous titles — flagging that as unverified.)

Original assignee

Kajeet, Inc. (Bethesda, MD, later McLean, VA per patent-profile address changes).

• Primary business: a genuine operating wireless company — an MVNO / "wireless managed service provider" focused on K-12 education, sold direct-to-schools via its Sentinel® network-based filtering and device-management platform, SmartSpot hotspots, and smartSIM multi-carrier SIMs. Its own materials claim ~40 foundational US wireless patents, 3,000+ customers, 5.5M+ lines.
• Did it ship a product embodying the claims? Yes, by strong indication. Kajeet's Sentinel platform in commerce performs network-side, real-time per-device policy/data-control/filtering — the same functional space as the '755 disclosure (global/local policy enforcement points). Kajeet's own "Patents and Licensing" page still lists 8,774,755 among the patents protecting its products/services.
• Current status: Operating. I found no indication of acquisition, dissolution, or bankruptcy of Kajeet, Inc.

Assignment timeline

Recorded legal events on the '755 patent (Google Patents legal-events mirror; reel/frame and correspondent not retrievable from my sources):

• recorded 2021-12-17 — Reel NNNNNN/NNNN — NOT RETRIEVED
  • Conveyance: Security Interest (SECURITY INTEREST — see document for details)
  • Assignor: Kajeet, Inc.
  • Assignee: Silicon Valley Bank
  • Correspondent: not retrieved
  • Context: securitization — Kajeet pledged its IP as collateral for venture debt.
• recorded 2025-01-21 — Reel NNNNNN/NNNN — NOT RETRIEVED
  • Conveyance: Release by Secured Party
  • Assignor: Silicon Valley Bank
  • Assignee: Kajeet, Inc.
  • Correspondent: not retrieved
  • Context: lien discharge — the security interest was released back to Kajeet (consistent with the loan being satisfied; note SVB itself failed in March 2023 and its assets went to First Citizens, so the release was administered post-collapse).
• recorded 2025-01-29 — Reel NNNNNN/NNNN — NOT RETRIEVED
  • Conveyance: Assignment of Interest
  • Assignor: Kajeet, Inc.
  • Assignee: Wireless Management Solutions, LLC
  • Correspondent: not retrieved — this is the single most important missing datum; see signal 3.
  • Context: transfer to a patent-holding entity — the operating company moved the patent into an LLC that (per IP-owner data) holds ~45 IP assets, essentially the entire Kajeet patent family, with no products I could identify.

Not found / not attributed:

• I could not retrieve the original inventor→Kajeet assignment (standard filing-time assignment). It is presumably on record but I have no citable reel/frame.
• A Bluecrest Venture Finance Master Fund Ltd. assignee entry (2009) appears in a Kajeet portfolio assignment table, but that table spans the whole portfolio — I cannot confirm it touches the '755 patent, so I am not counting it as a '755 assignment.

Family corroboration for the 2025 transfer: a same-family continuation, US 12,382,259 B2, issued 2025-08-05 and is listed to Wireless Management Solutions, LLC — confirming the whole "Feature management" line moved to WMS, not just the '755.

Timeline diagram

timeline
    title Ownership of US 8774755
    2007 : Filed by Kajeet Inc
    2014 : Issued to Kajeet Inc
    2018 : Kajeet asserts patent v Mobicip
    2021 : Security interest to Silicon Valley Bank
    2025 : SVB security interest released
         : Assigned to Wireless Management Solutions LLC

NPE / troll-pattern signals

1. Shell-entity transfer — UNclear (leaning present).
A transfer did occur from an operating company (Kajeet) to an LLC. The LLC suffix plus a portfolio of ~45 IP assets that map back almost entirely to one originator (Kajeet family; first patent 2007 "System and methods for managing…," last 2023) is consistent with a licensing-only holding entity. But I could not confirm the concrete tells you require — registered-agent service address, single-member charter, or absence of any product in commerce — and I found no products under the WMS name. Address appears as a normal Chevy Chase, MD location, not a known registered-agent mass-filing address. Record it as suggestive, not established. Cite: 2025-01-29 assignment, Kajeet → Wireless Management Solutions, LLC.

2. Known asserter in the chain — NOT present.
Neither Kajeet, Inc., Silicon Valley Bank, nor Wireless Management Solutions, LLC matches the public high-frequency NPE lists you named (Acacia, Marathon, IV, IPNav, Wi-LAN/Mosaid-Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, Document Generation Corp, Spangenberg). No Unified Patents / RPX high-frequency-plaintiff hit surfaced for WMS.

3. Repeat correspondent across the chain — UNclear / INSUFFICIENT DATA.
I was unable to retrieve any correspondent-of-record for the three recorded events. This is the signal I'd most want and the one I least have; without it I cannot say whether one lawyer ran the SVB release and the WMS assignment back-to-back (a classic tell). Flagging this as an open verification item, not a null finding.

4. Cascading transfers — NOT present.
Only a single LLC enters the chain, with no <24-month chain of successive LLCs. One transfer (2025-01-29), preceded only by a lender security interest and its release.

5. Pre-litigation transfer — NOT present.
The first (and so far only) suit naming the '755 was Kajeet, Inc. v. Mobicip, LLC, 2:18-cv-03899 (C.D. Cal., filed 2018-05-10) — asserted by the original operating owner, not by any successor. The 2025 transfer to WMS post-dates that case by ~7 years, so the '755 chain was not arranged to enable the 2018 assertion. (See prior section for the case; not repeated here.)

6. Bankruptcy fire-sale — NOT present.
No Chapter 7/11 for Kajeet, Inc. surfaced. The only lender-related event is the SVB security interest (2021-12-17) and its release (2025-01-21) — a securitization/lien-discharge sequence, not a distressed asset sale. Note separately that Silicon Valley Bank (the lender, not Kajeet) failed in 2023; that does not convert this into a Kajeet bankruptcy.

7. Privateering — UNclear.
No SEC-filing, Patent Progress, or EFF coverage surfaced tying a Kajeet→WMS transfer to assertion on Kajeet's behalf against competitors. The 2018 Mobicip suit was, per the Stanford NPE database, filed by a "Product company" asserter (Kajeet itself), i.e., operating-company assertion — which cuts against the privateering reading unless WMS later begins suing Kajeet's competitors.

8. Defensive aggregator — NOT present.
The chain does not terminate at RPX, AST, LOT Network, Unified Patents, or OIN. Inverse signal not triggered.

Verdict

NPE — moderate confidence.

The single strong driver is the 2025-01-29 assignment from operating company Kajeet, Inc. to Wireless Management Solutions, LLC, an entity that (per IP-owner data) holds ~45 assets concentrated almost entirely in the Kajeet family and for which I found no products in commerce — the classic shape of an operating-company-to-holding-LLC transfer. It is moderated by real counter-evidence: the historical assertion on this patent was operating-company assertion (Kajeet, a genuine product company, sued Mobicip itself in 2018), the chain contains no cascading LLCs, no known asserter, and no pre-litigation timing, and WMS has no litigation record I could find as of this analysis. I am downgrading from high to moderate because two confirmatory datapoints are missing: (a) the correspondent of record on the 2025 assignment, and (b) confirmation that WMS is licensing-only. Either one resolved could move this to high confidence (or, if WMS ships products, back to operating-company).

Verify directly (authoritative):

• USPTO Assignment Center — https://assignmentcenter.uspto.gov/ (search patent 8,774,755, then open each event to read reel/frame + correspondent)
• USPTO Patent Assignment legacy search — https://assignment.uspto.gov/patent/index.html
• Cross-checks: Google Patents legal events for US8774755; PEDS/ODP for app 13/786,974; WMS as a litigation plaintiff on Unified Patents / RPX.

Explicit caveats / things I did not verify: I did not fabricate reel/frame numbers or correspondents; where the data was unavailable I said so. I did not find any 2026 assignment, 2026 suit, or WMS assertion involving the '755. And I could not confirm the terminal disposition of the 2018 Mobicip case.

I'll research the prior-art citations for US 8,774,755 specifically. Let me run targeted searches.

Let me try to pull the actual front-page citations from patent databases.

The searches aren't surfacing the front-page citation list. Let me try to retrieve the patent's PDF front page and the USPTO full-text record directly.

Important retrieval limitation (please read first)

I was unable to retrieve the front-page "References Cited" list for US 8,774,755 from any source reachable in this session. Specifically:

• The Google Patents full text you supplied is authoritative and complete as to what it contains, but it does not include (a) the front-page citation table (the "U.S. PATENT DOCUMENTS" / "FOREIGN PATENT DOCUMENTS" / "OTHER PUBLICATIONS" blocks), or (b) the Claims section — the text terminates mid-sentence at "…each device requires at least two wallets to be associated wi…".
• My targeted searches for the citation table (Google Patents citation list, FreePatentsOnline, Justia, the patentimages PDF front page, and the USPTO PTAB/PatentCenter record for application 13/786,974) returned the specification and family-listing material but not the enumerated cited references.

I am therefore not able to give you a verified "each patent citation for 8774755" list, and I will not reconstruct one from memory — that would risk fabricating citations, which the operating rules forbid. What follows distinguishes (A) what I can ground in the authoritative text or confirmed records from (B) what I could not verify.

A. References that ARE grounded in the specific record

A1. The patent's own "Background" — admitted/acknowledged prior art (no patent numbers given)

These are the only prior-art teachings the specification itself cites (by name or generic practice), and they are the closest thing to admissible prior art evident on the face of the document:

These are the only prior-art items I can tie to the '755 document itself. Note that the specification frames each of them as an incomplete solution — i.e., these were treated as the relevant background art, not as anticipatory references.

A2. Related/priority documents (citations in the cross-reference — NOT prior art)

The '755 spec cross-references the following, all sharing the June 28, 2007 priority chain, so they are not § 102 prior art to this patent (they are the same inventive family):

• U.S. Appl. No. 13/763,348 (filed Feb. 8, 2013)
• U.S. Appl. No. 13/603,218 (filed Sep. 4, 2012)
• U.S. Appl. No. 12/950,379 → US 8,285,249 (issued Oct. 9, 2012)
• U.S. Appl. No. 11/881,460 → US 7,899,438 (issued Mar. 1, 2011)
• U.S. Appl. No. 11/824,336 → US 7,945,238 (issued May 17, 2011)
• U.S. Appl. No. 12/027,240 → US 7,881,697 (issued Feb. 1, 2011)
• U.S. Appl. No. 12/950,291 → US 8,078,140 (issued Dec. 13, 2011)

I mention these only to prevent misattribution — a common error would be to list these same-family patents as § 102 art. They are not, absent a priority break (and the burden of showing a priority break would fall on a challenger).

A3. Family context (also not prior art)

The ~19 same-day, same-title applications filed Mar. 6, 2013 (siblings such as US 8,774,754, US 8,587,335, US 8,634,803, etc.) share the same priority and are likewise not prior art.

B. What I could NOT verify (stated plainly)

1. The enumerated front-page patent citations for US 8,774,755 (any U.S. patent documents, foreign documents, or other publications cited by the applicant or the examiner). Not returned by any search.
2. The examiner's PTO-892 references (i.e., what the Examiner actually relied on). Not retrieved.
3. The application's IDS / PTO-1449 submissions for application 13/786,974. Not retrieved.
4. The claim set itself. Because the claims are absent from the supplied text, I cannot perform the requested "which claim(s) it potentially anticipates under 35 U.S.C. § 102" mapping on a claim-number basis. Any such mapping I produced would be fabricated.

I am explicitly flagging these gaps rather than filling them by inference.

C. Why the § 102 mapping cannot be completed as posed (methodological note)

For a pre-AIA case with a June 28, 2007 priority date (the '755 patent's earliest priority via the 11/824,336 CIP chain; the 11/881,460 filing was July 26, 2007), § 102 analysis requires:

• the actual claim language (missing here), and
• the actual reference list and its dates (missing here).

Without both, a claim-by-claim anticipation statement is not defensible. Note also that a reference showing "parental controls that limit spending in real time" (the Telcordia-type art) would most plausibly be argued against claims reciting a single control/policy construct — whereas the '755 disclosure's stated point of novelty is the combination of multiple wallets with an order of precedence, global-then-local rule ordering producing two separate decisions, and back-up/dynamic wallets that still cannot override administrator-blocked services. That distinction is exactly what the specification itself draws against the admitted prior art (e.g., the promotional-wallet example that still cannot call a blocked 900 number). So the admission in the Background is best understood as the art the patent distinguishes over, not as anticipating art.

D. Where to get the verified citation list (authoritative steps)

To complete the task as specified, pull these:

1. Google Patents page for US8774755B1 → the "Citations" and "Cited By" tables (Patent Citations / Non-Patent Citations). The rendered page contains these tables even though the text dump I received omitted them. URL: https://patents.google.com/patent/US8774755/en
2. USPTO Patent Public Search / PatentCenter for application 13/786,974 → the "References Cited" tab (PTO-892 and PTO-1449 forms), plus the applicant IDS list.
3. USPTO Patent Center "Documents" for the same application → the examiner's Notice of References Cited and any Information Disclosure Statements.
4. FreePatentsOnline / Justia record for 8774755 (Justia exposed a "References Cited" style listing in a related family member, e.g., patents.justia.com/patent/12382259, which lists the family's cross-citations).

Once the citation table and the claim set are in hand (the two items missing from the supplied materials), I can produce the requested row-by-row table: full citation → publication/filing date → brief description → the specific independent claim(s) each reference arguably anticipates under § 102, with the element-by-element correspondence.

E. Cross-check against the previously generated sections

• The earlier "Patent summary" section flagged that the claims were not available and that it would not reconstruct claim language from memory. That remains true in this pass — the supplied text still ends at "…each device requires at least two wallets to be associated wi…" and still contains no claims and no front page. No contradiction to flag; the limitation simply persists.
• The earlier "Litigation summary" (the one lawsuit specifically asserting '755, Kajeet, Inc. v. Mobicip, LLC, No. 2:18-cv-03899, C.D. Cal.) is not directly relevant to the § 102 question, but it is the likely place where a defendant would have identified prior art against the '755 claims — if you want the litigation-driven prior-art art list (invalidity contentions) rather than the prosecution-cited list, that would come from the Mobicip pleading/Invalidity Contentions in PACER, which I likewise could not retrieve here.

Bottom line: I could not extract the specific patent citations for US 8,774,755 from the sources available in this session, and the claims needed for a § 102 claim-by-claim mapping are not in the provided text. I have given you the only prior art actually identified on the face of the document (the admitted Background art, led by the Telcordia Converged Real-Time Charging system), separated the non-prior-art family references, and specified exactly where the verified citation list and claims can be pulled. I have not fabricated any citation or claim mapping.

I'll first try to retrieve the two things the prior analysis flagged as missing: the actual claim set of the '755 patent, and the prior-art references cited on its Google Patents record.

Let me pull the claim text and cited references from the Justia and PatentCenter mirrors.

The claim text still isn't surfacing. Let me try to pull it via the sibling patents and the Justia "References Cited" list.

Obviousness Analysis — U.S. 8,774,755 B1 under 35 U.S.C. § 103

0. Scope, and what I could and could not verify

Before the analysis, three explicit caveats — the first two are carried forward from the earlier sections and are not resolved.

1. The claim set is still unavailable to me. The authoritative full text you supplied terminates mid-sentence in the Detailed Description and contains no Claims section. My searches this round (Google Patents, Justia, PatentCenter mirrors, PTAB dockets) again failed to return the verbatim claim language of the '755 patent. This is a material limitation on the analysis below: a § 103 analysis is claim-by-claim and limitation-by-limitation. What follows is therefore a ground-level obviousness assessment of the disclosed subject matter as the specification characterizes it, not a limitation-by-limitation rejection. I flag this rather than reconstruct claim language, which I will not do.

2. I could not retrieve the "Prior Art" section of the Google Patents page verbatim. Google's "References Cited / Cited By / Similar Documents" block was not included in the page text you supplied, and my searches did not surface that block for US8774755B1. What I did recover is the "Non-Patent Citations" list from the Justia record for the '755 patent, which is part of the applicant/examiner references of record, plus the patent's own admitted prior art in the Background. I have built the analysis on those. If the page's Prior Art section contains U.S. patent documents not in my recovered list, my analysis will be incomplete — treat the grounds below as a framework to be populated with the actual reference list.

No contradiction with the previously generated sections. The "claims unavailable" flag stands unchanged.

1. The prior art actually on the table

1a. Admitted prior art in the specification (usable as prior art regardless of reference list)

The '755 specification expressly concedes the following existed before the invention — under In re Nomiya / MPEP 2129, applicant admissions are prior art for § 103:

Two of these admissions are especially damaging to patentability, because they map directly onto the patent's asserted points of novelty:

• Telcordia supplies real-time, server-side, per-account policy control over premium data downloads — i.e., feature management of a device with a spend/usage parameter.
• Subaccounts + affinity accounts supply the concept of multiple differentiated funding buckets attached to one subscriber, which is the conceptual kernel of "wallets."

1b. Non-patent literature cited of record (recovered from the Justia record for 8774755)

These are the references I could verify appear in the '755 record. Critical dates matter (see §2):

Take-away: the applicant's own IDS cited a dense, multi-year body of art covering each of the invention's three pillars — (i) server-side real-time mobile payment/wallet administration, (ii) rule-based transaction authorization/denial, and (iii) family/parental control of a mobile device. That is an unusually strong prior-art posture for a § 103 attack.

1c. Art I could NOT confirm is of record

During search I encountered a partial international search report (PCT/US2011/037542, published as JP 2013-526818) citing WO 93/17512 (Nokia), EP 1 761 088 (Orange), GB 2 292 047 (Motorola) and EP 1 085 395 (Phone.com) for call-origination control and wireless-device feature provision. I could not verify that these are in the '755 file. They are attractive for a § 103 ground (see Ground 3), but they are flagged as unconfirmed and must be checked against the actual '755 reference list before being relied on.

2. Governing law, priority date, and the critical date

• Pre-AIA 35 U.S.C. § 103(a) applies. Application 13/786,974 was filed March 6, 2013, before the March 16, 2013 AIA cutover, and it rides a domestic-priority chain to 2007.
• Priority chain (verbatim from the specification): 13/786,974 → 13/763,348 (Feb. 8, 2013) → 13/603,218 (Sep. 4, 2012) → 12/950,379 (Nov. 19, 2010, now US 8,285,249) → 11/881,460 (Jul. 26, 2007, now US 7,899,438) → CIP of 11/824,336 (Jun. 28, 2007, now US 7,945,238).
• Consequence for prior-art date: the claims are presumptively entitled to at least the July 26, 2007 filing date (and to June 28, 2007 for subject matter carried over from the '336 parent), making the pre-July-2006 (or pre-June-2006) art § 102(b) prior art. Every NPL reference in § 1b above is comfortably § 102(b) art.
• Caveat to preserve: any claim limitation not supported by the 2007 disclosures is only entitled to the 2013 filing date, which would change the prior-art window. This is a real sub silentio risk for the "dynamic wallet" and "promotional wallet" limitations if they were added in later applications — I could not verify support, so I flag it.
• Framework: Graham v. John Deere factors (scope/content of claims; differences; PHOSITA level; secondary considerations); KSR Int'l v. Teleflex, 550 U.S. 398 (2007) (predictable variation; "combination of familiar elements according to known methods"; design incentives); MPEP 2143 (articulated reasoning rationales: A–G).

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

Based on the field (wireless network charging/policy control) and the reference density, the likely POSITA is: a telecommunications network engineer or software architect with a bachelor's degree in EE/CS and 3–5 years of experience in mobile network charging, prepaid systems, or OSS/BSS policy platforms, or equivalent — i.e., a person conversant with IS-41/IS-826 triggers, PDSN/PEP/PDP architectures, and prepaid billing engines. This level is important: it is a POSITA who would treat IN/CAMEL/IP multimedia-subsystem policy control and payment-gateway rule engines as interchangeable, well-understood building blocks.

4. Best reconstruction of the claim scope (flagged as reconstruction, not quotation)

Because I cannot quote the claims, I use the specification's own statements plus the Google Patents "prior art keywords" string (computing device; administrator; user; policy; rule), which Google derives from the claim text:

Strong textual anchors within the specification:

• "Some of the key features of wallets in the context of the present invention are: (1) … real-time management or control of a device; (2) that each device requires at least two wallets … at least one user wallet and at least one administrator wallet; (3) that an order of precedence can be established between the wallets … and any wallet can be used to back up a payment by a second wallet …; and (4) that local rules and global rules can be established …"
• "Global rules and local rules can be applied in order, so as to result in two separate decisions…"
• "a dynamic wallet would not be able to authorize services for a user that were blocked by the administrator, but could pay for those services that were allowed."

Working hypothesis (to be confirmed against the claims): at least one independent claim recites a computing device / system (or a corresponding method) comprising: a memory storing global rules and local rules and first and second wallets (user + administrator) each associated with a device; logic to evaluate the global rules before the local rules in a defined order of precedence, producing two separate decisions; and logic to authorize/deny the service request and charge it to a wallet according to the precedence. Dependent claims likely add promotional wallet, dynamic wallet, allowed/blocked number lists, time-of-day restrictions, override restrictions, and unified feature on/off switches.

If that hypothesis holds, the analysis below applies. If the independent claim is materially narrower (e.g., the "two separate decisions" architecture is recited as a specific ordered evaluation producing an intermediate authorization before charging), Grounds 2 and 4 below weaken and the caveat in § 7 becomes central.

5. Grounds of rejection under § 103

The table below gives each proposed combination, the claim elements it reaches, and the KSR articulation for why the POSITA would combine. None of this is a substitute for an actual limitation-by-limitation chart, which I cannot build without claim text.

Ground 1 — Telcordia Converged Real-Time Charging + Integrated Mobile "Family-friendly Mobile Services"

Motivation: Both references address the same problem the specification identifies (uncontrolled spend/use of a child's phone) in the same field (wireless service control). KSR rationale: combination of prior-art elements according to known methods to yield predictable results. Telcordia already discloses the enforcement engine; Integrated Mobile supplies the family-administrator interface and the notion of differentiating what the child may do from what the parent pays for.

Strength: Strong for any claim that is essentially "server-side, real-time, administrator-configured allow/deny plus charge for a mobile device feature."

Ground 2 — Integrated Mobile + Tang "Distributed Family Wallet Architecture" (+ Boyd "Wallet Phone" / Labrou "Wireless Wallet" for enablement)

Motivation: Tang is literally "Distributed Family Wallet Architecture" — the same organizing metaphor and the same user population (a family with several spenders and one funding authority) as the '755 patent. A POSITA seeking to implement the family-control system of Integrated Mobile on a prepaid platform would have been led directly to Tang's multi-purse structure to implement differentiated funding. KSR: "a finite number of identified, predictable solutions"; design incentive to reduce parental administration burden. The wallet references (Boyd, Labrou, Mjolsnes) supply enablement/obviousness of reducing a wallet to practice on a wireless handset.

Strength: Strong for the "one device ↔ multiple wallets" and "administrator wallet backs up user wallet" limitations. This is the combination that most directly attacks the patent's asserted point (2) of novelty ("each device requires at least two wallets").

Ground 3 — Telephony feature-control art (call-origination restriction) + the network policy enforcement art of Ground 1/2

Candidate primary references (UNCONFIRMED as of record in '755 — verify):

• EP 1 085 395 (Phone.com) — controlling features/services provisioned to a wireless device from a network platform.
• GB 2 292 047 (Motorola) — restricting or barring call origination at the network for a mobile subscriber.
• WO 93/17512 (Nokia) — subscriber-controlled service restriction in a cellular system.

Motivation: The specification's global-rule examples (911 free; 900 blocked) are the paradigm of pre-existing telephony screening. A POSITA implementing the Ground 1/2 system would necessarily reuse the carrier's existing global screening tables for the global layer and the administrator's configuration for the local layer. Lennox supplies the explicit teaching that feature/rule ordering and override must be resolved by precedence rules — i.e., the "two separate decisions" architecture. KSR: use of a known technique (ordered rule tables) to improve a similar device in the same way.

Strength: Moderate-to-strong for global/local rule layering and for allowed/blocked lists and time-of-day limits, which the specification presents as ordinary implementations rather than inventions.

Ground 4 — Promotional wallet + dynamic wallet limitations as obvious design variants

Motivation: Once the Ground 2 multi-wallet hierarchy exists, adding a carrier-sponsored bucket ("free 10 minutes") or a grandparent-funded bucket is a purely conventional extension — KSR "obvious to try" / "predictable variation," and the specification gives no unexpected technical effect for the precedence ordering beyond its own asserted convenience.

6. The through-line motivation (why a POSITA would combine them all)

The § 103 case is unusually clean here for three structural reasons:

1. All references target one problem-space. Mobile commerce with a stored-value/administrator-controlled funding source (Boyd, Labrou, Tang, Mjolsnes, Ebringer, IBM TDB, Pierce, Varshney) and parental/family control of a mobile device (Integrated Mobile, Telcordia) are the same commercial field the patent claims. Combining them is not "combining two arts"; it is combining references within one art.
2. The patent's own background concedes most of the architecture. Telcordia gives real-time server-side control; subaccounts give differentiated billing buckets; alerts give thresholds; affinity accounts give promotions. What remains is ordering and association — classic fields for obviousness.
3. The asserted novelty is arithmetic, not technical. Points (2)–(4) of the specification's own "key features" list (≥2 wallets; precedence; backup; global+local rules producing two decisions) are configurations of a database and a rule engine, i.e., precisely the "predictable variations" KSR treats as obvious, especially where the reference (Lennox) teaches that rule interaction must be resolved by precedence in telephony.

7. Where the claims might survive — the counter-case I would expect the patent owner to make

I flag these honestly, because a one-sided § 103 memo is useless:

• "Two separate decisions" as a specific ordered evaluation. If the independent claim recites that the global rule evaluation yields an intermediate authorization before the wallet/charging logic runs — and limits over the mere use of ordered rule tables — the patent owner will argue the prior art discloses screening (Ground 3) or payment routing (Ground 2) but not the interleaved two-decision structure. This is the strongest non-obviousness argument and I cannot assess it without the claim text.
• Dynamic wallet non-override property. If claimed affirmatively ("a dynamic wallet is incapable of authorizing a service blocked by the administrator"), it is arguably a negative limitation with no explicit prior-art teaching, and the applicant may be able to rely on In re Miller-type arguments that the reference must be shown to disclose the absence.
• Secondary considerations. The family's 2018 enforcement campaign (Kajeet v. Mobicip, C.D. Cal. 2:18-cv-03899, asserting the '755 patent alongside U.S. 8,712,371 and U.S. 8,667,559 — see the previously generated Litigation summary) could be used to argue commercial success, licensing, or copying. No secondary-considerations evidence (nexus, sales, praise) surfaced in my searches, so this is speculative and would need discovery.
• § 101 susceptibility (defensive observation only). The Mobicip-family complaint was not a validity ruling, but in the broader campaign a Kajeet v. Qustodio action was reportedly resolved on patent ineligibility. A claim drawn to "establishing rules and paying for services on a generic computing device" invites an Alice challenge that would sit alongside § 103. This is not a § 103 argument and I mention it only because it materially affects the risk profile.

8. Bottom line

1. I cannot give you a complete § 103 analysis of the '755 patent as issued, because neither the claims nor the page's Prior Art section were retrievable this round. That is a hard limitation, not a judgment call.
2. On the disclosed subject matter, the obviousness case is strong and can be run on four grounds:
   • Ground 1: Telcordia Converged Real-Time Charging (admitted) + Integrated Mobile "Family-friendly Mobile Services" (2003) — covers real-time, administrator-set, server-side policy enforcement and charging.
   • Ground 2: Integrated Mobile + Tang "Distributed Family Wallet Architecture" (2000) + Boyd/Labrou/Mjolsnes — covers multi-wallet association, precedence, and back-up payment, i.e., the patent's asserted point (2).
   • Ground 3: telephony screening/feature-control art (Phone.com EP 1 085 395; Motorola GB 2 292 047; Nokia WO 93/17512 — each unconfirmed as of record, verify) + Lennox "Feature Interaction in Internet Telephony" (2000) — covers global/local rule layering, allowed/blocked lists, time-of-day limits, and the precedence/override that produces the "two separate decisions."
   • Ground 4: admitted prior art (affinity accounts, promotions, bonus minutes) + Tang/Lennox — covers promotional and dynamic wallets and their subordination to administrator blocks.
3. Every reference in Grounds 1, 2 and 4 is dated 1999–2005, placing it more than one year before the July 26, 2007 priority date — i.e., § 102(b) prior art usable in a § 103 combination under pre-AIA law.
4. The single most important next step is to obtain (a) the verbatim claim set of the '755 patent and (b) the "References Cited" block from the Google Patents page or the file wrapper in PatentCenter for application 13/786,974. With those two inputs I can convert the above into a proper limitation-by-limitation § 103 chart and reconcile it against what the examiner actually applied during prosecution — which is the only way to know whether the claims as issued already survived these combinations.