US 8667559

I'll research US patent 8667559 across the requested sources.

Let me search for the PTAB/IPR outcome and any Federal Circuit appeals involving this patent.

Let me look for the actual claim language and any Federal Circuit appeal activity.

US Patent 8,667,559 — Research Summary

Important scoping note: I ran targeted searches against patent databases (Google Patents, FreePatentsOnline, PTAB/Unified Patents dockets, Stanford NPE litigation database) and general web indexes. I was unable to locate any 2026 Court of Appeals for the Federal Circuit docket activity for 8,667,559 — see the caveat at the end. Everything below is tied to a specific source; where my information is incomplete I say so.

Bibliographic data (high confidence — matches the authoritative patent text provided)

The patent is a continuation of U.S. App. 13/763,348 (filed Feb. 8, 2013) → 13/603,218 (Sep. 4, 2012) → 12/950,379 (now U.S. 8,285,249) → 11/881,460 (now U.S. 7,899,438) → a continuation-in-part of 11/824,336 (now U.S. 7,945,238). It is one of ~20 sibling continuations (13/786,685 through 13/787,610) all filed Mar. 6, 2013 and all titled "Feature Management of a Communication Device."

Abstract (verbatim from the patent)

"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."

Independent claims — plain-language overview

The '559 patent has three independent claims: 1, 13, and 27 (claims 1–2, 5–15, 18–21, and 27–29 were the claims challenged in IPR2022-00001, which brackets that structure).

I have direct, quoted claim language for claim 27 and for the common limitation shared by claims 1/13/27, but I do not have the verbatim full text of claims 1 and 13 in front of me. My summaries below are grounded in the IPR petition analyses (Putzolu/Bhat grounds) and the Trend Micro infringement contentions, and I flag the uncertainty.

Claim 1 — System/apparatus involving a computing device and a server.
A computing device sends a request to a server (the request relates to performing a function on the communication network), receives in real time a decision from the server, where "the decision being based on one or more policies that are stored at the server" — and then enforces that decision without locally accessing the policies (the policies are not stored or consulted on the device). The IPR petition characterized claims 1 and 27 as requiring the device to "send a request to a server, receive a decision based on policies stored at the server, and enforce that decision without locally accessing the policies."
(Caveat: I have the shared limitation and its construction verbatim, but not claim 1's complete text.)

Claim 13 — Independent claim directed to locally caching / updating policy decisions.
Per the PTAB petition analysis (Ground 3, Bhat), claim 13 concerns "local caching and updating of policy decisions": a policy enforcement point receives an initial policy decision from a server/policy engine, stores it in a local cache, uses the stored decision for subsequent requests instead of re-contacting the server, and can receive an updated policy decision and determine whether to grant a request based on the original decision plus the update. Claim 13 also contains the same "decision based on one or more policies stored at the server" limitation.
(Caveat: this is derived from the petitioner's characterization, not from verbatim claim text I retrieved.)

Claim 27 — Method for controlling a computing device (quoted via Trend Micro infringement contentions):
A "method for controlling a computing device configured to execute a function using a communication network managed by a service provider," requiring, among other steps, that:

• the device detects an attempt by the computing device to perform a function on the network;
• a request is sent to a server;
• a decision is received in real time from the server, "the decision being based on a policy stored at the server"; and
• "the communication [is] enabled or disabled without storing the policy on the computing device."

The patentee has described the core inventive concept as a distributed architecture: policies live at the server, remote from the device, making them resistant to user manipulation/deletion, while real-time control is preserved. The applicant distinguished prior art during prosecution on the basis that policy decisions are "performed at the server level" rather than on the device (Petitioner's proposed construction of "the decision being based on one or more policies that are stored at the server").

Litigation & post-grant posture (from docket sources)

• IPR2022-00001, Gen Digital Inc. f/k/a NortonLifeLock Inc. v. Kajeet, Inc. — Petition filed Oct. 1, 2021 (some sources show "Filed" dates of Oct. 1, 2021). Institution decision Apr. 21, 2022. Final Written Decision Apr. 13, 2023; case terminated. Challenged claims 1–2, 5–15, 18–21, 27–29. Grounds: (1) obviousness over Putzolu (US 6,578,076); (2) Putzolu + Rothman (US 7,826,835); (3) Bhat (US 2005/0021978). Kajeet filed a revised motion to amend; briefing addressed §101 eligibility of the substitute claims (citing Bascom and ChargePoint).

  • ⚠️ Uncertainty: The Patexia summary fields for "Claims Instituted" and "Claims Invalidated" were blank in my search results, so I cannot confirm from authoritative sources which claims (if any) were cancelled or upheld by the Final Written Decision. I am not going to guess at the outcome.

• District court litigation (Stanford NPE Litigation Database, and Google Patents "Family has litigation" links) includes many cases, e.g., Kajeet, Inc. v. Lightspeed Solutions, LLC (6:20-cv-00203, W.D. Tex.); Kajeet, Inc. v. Cujo LLC (2:20-cv-00253, C.D. Cal.); Kajeet, Inc. v. Mobicip, LLC (2:18-cv-03899, C.D. Cal.); plus Delaware (1:19-cv-02370/02371, 1:20-cv-01339, 1:21-cv-00004/00005/00006), Central California (2:18-cv-00643, 8:18-cv-01312, 8:18-cv-01519), and Texas Western (6:20-cv-00302, 6:20-cv-00705, 6:20-cv-01076, 6:21-cv-00389, 6:21-cv-00704/00705/00707) actions. Trend Micro appears as an accused infringer in assertion contentions referencing claim 27.

CAFC 2026 docket — explicit finding

No CAFC 2026 docket entry for patent 8,667,559 was found. My search for "US8667559 CAFC 2026 docket" returned an unrelated Federal Circuit docketing notice (No. 2026-2012, Contour IP Holding LLC v. GoPro, Inc.), which concerns a completely different patent and party. A follow-up targeted search for Kajeet Federal Circuit appeals related to the IPR also returned no confirmed 2026 appellate activity.

This is a negative finding, not proof of absence. Federal Circuit dockets are captioned by party, not patent number, so an appeal involving the '559 patent could exist under a caption like "Kajeet, Inc. v. [Party]" or "[Party] v. Kajeet, Inc." without surfacing in a patent-number search. I cannot rule that out, and I am flagging this as a genuine limitation of what I was able to verify.

Bottom line

US 8,667,559 is a Kajeet, Inc. continuation patent (family priority June 28, 2007, issued March 4, 2014) claiming server-side, real-time policy enforcement for communication-device feature management, with independent claims 1, 13, and 27. It has been heavily litigated (Delaware, California, and Texas district courts) and was the subject of IPR2022-00001 (Gen Digital/NortonLifeLock v. Kajeet), which reached a Final Written Decision on April 13, 2023. I could not verify the specific claim-level outcome of that FWD, and I found no 2026 CAFC docket activity for the patent — these are the two areas of genuine uncertainty in this report.

I'll research litigation involving US patent 8667559 using the patent record provided and live searches.

Let me gather case-level details from the litigation databases.

Litigation involving US Patent 8,667,559

Bottom line: Yes — US 8,667,559 ("Feature management of a communication device," Kajeet, Inc.) has been asserted in a substantial campaign of district-court suits, plus two PTAB proceedings and one Federal Circuit mandamus proceeding. The patent is a Kajeet, Inc. patent, and Kajeet is the plaintiff/patent owner in every district-court case I found. There is also one known IPR petitioner-side challenge (NortonLifeLock/Gen Digital) and one more (Trend Micro).

Important caveat before the list: The case numbers below come primarily from the Google Patents "family has litigation" record for US 8,667,559 (https://patents.google.com/patent/US8667559/en) and the Stanford NPE database (https://npe.law.stanford.edu/patent/8667559). Google's litigation block is family-level, and the asserted-patent set for this family also includes US 8,712,371, US 8,774,755 and US 7,899,438 ('438). A handful of the listed cases may therefore have asserted a sibling patent rather than the '559 patent itself. Where I could not independently confirm (a) the defendant, or (b) that the '559 patent was asserted, I say so rather than guess.

District court cases (Kajeet, Inc. as plaintiff)

Note on the three July 2021 W.D. Tex. filings (#17–19): the Federal Circuit's In re Trend Micro order (May 11, 2022) records that "Kajeet also filed complaints in the Waco Division of the Western District alleging that two other defendants infringed the '559 patent," which is consistent with these co-pending Waco suits.

PTAB proceedings

Appellate proceedings

One source-discrepancy to flag, not corrected: a third-party summary page (Studicata) captions the Gryphon decision as "Kajeet, Inc. v. Gryphon Online Safety, Inc., United States Court of Appeals, Third Circuit (2021)," yet the holding it describes is attributed to Judge Noreika and involves a Rule 12(b)(6) ruling — i.e., a District of Delaware decision, not a Third Circuit opinion. I am reporting this literally as the source states it, but the appellate attribution appears inconsistent with the described holding.

Things I could NOT confirm (stated explicitly rather than filled in)

• Defendants for C.D. Cal. 2:18-cv-00643 and 8:18-cv-01312; D. Del. 1:19-cv-02371, 1:21-cv-00005, 1:21-cv-00006; W.D. Tex. 6:20-cv-00705, 6:21-cv-00705, 6:21-cv-00707.
• Outcomes for Cujo, Mobicip, Lightspeed, JAMF, Impero, NortonLifeLock (1:20-cv-01339), CyberReef and the Infoweise case.
• The final result of the IPR2022-00001 Final Written Decision, and whether IPR2023-00178 was directed at the '559 patent specifically.

Practical takeaway

Kajeet ran a roughly 2018–2021 parental-controls/mobile-device-management assertion campaign centered on the '559 family (and companion '438/'371/'755 patents) against device-management and parental-control vendors, concentrated in C.D. Cal., D. Del. (Judge Noreika) and W.D. Tex. (Judge Albright, Waco). Early § 101 (Alice) challenges were rejected in both Delaware and California — per RPX, Judge Noreika and Judge Kronstadt each declined to invalidate the asserted claims at the pleading stage, though Delaware did dismiss under-pleaded direct/indirect infringement theories with leave to amend. The campaign subsequently wound down through settlements (Qustodio; Trend Micro's IPR), leaving the '559 patent's validity intact but largely untested by a final judgment on the merits in the sources available to me.

Primary sources: https://patents.google.com/patent/US8667559/en · https://npe.law.stanford.edu/patent/8667559 · https://npe.law.stanford.edu/case/[200304](/patent/200304) · https://dockets.justia.com/docket/texas/txwdce/6:2020cv01076/[1115311](/patent/1115311) · https://portal.unifiedpatents.com/litigation/California%20Central%20District%20Court/case/8%253A18-cv-01519 · https://cases.justia.com/federal/appellate-courts/cafc/22-133/22-133-2022-05-11.pdf · https://services.patexia.com/lawsuits/Trend-Micro-Inc-v-Kajeet-Inc-id-[183366](/patent/183366) · https://litigation.rpxcorp.com/news/66398-in-parental-controls-campaign-kajeet-again-asserts-patent-twice-surviving-early-alice-challenges · https://ai-lab.exparte.com/case/ptab/IPR2022-00001/doc/summary/1

I'll start by checking the structured data and then verify against public sources.

Found a real proceeding the ODP block missed. Let me dig into the outcome and any appeal.

Now let me pin down the Final Written Decision outcome and any appeal.

Proceedings overview

One AIA trial proceeding is on file — contradicting the structured "PTAB proceedings on file" block above, which reports no AIA activity. The single proceeding is IPR2022-00001, Gen Digital Inc. (f/k/a NortonLifeLock Inc.) v. Kajeet, Inc., which was instituted, tried to a Final Written Decision on 2023-04-13, and resulted in cancellation of every challenged claim; the USPTO issued the IPR certificate on 2023-06-28. Bottom line for a defendant: this is the rare "the patent is broken" posture — all 21 claims that were challenged (1, 2, 5–15, 18–21, 27–29) were invalidated, including all three independent claims (1, 13, and 27). Any demand letter that cites claim 1, 13, or 27 should be met with the IPR certificate. The residual exposure is limited to the small set of claims that were never challenged (see the caveat in the Strategic Summary).

Source-conflict flag (required by your operating rules): the ODP-derived block says no AIA proceedings. That block is stale or mis-indexed. The patent's own Google Patents family record lists "PTAB case IPR2022-00001 filed (Final Written Decision)" (patents.google.com/patent/US8667559/en), and Docket Alarm's PTAB docket confirms the case and termination date. I did not rely on the ODP block.

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

• Type: Inter Partes Review (35 U.S.C. §§ 311–319)
• Filed: 2021-10-01
• Status: Final Written Decision — claims canceled; terminated 2023-04-13; IPR certificate issued 2023-06-28
• Judge panel: Meredith C. Petravick (opinion author), Juliet Mitchell Dirba, Iftikhar Ahmed. (Docket Alarm additionally lists Karl Easthom on the panel, likely as a substituted/expanded panel member; Petravick per Patexia wrote the Final Written Decision. Verify against the FWD caption at PTAB E2E / Docket Alarm.)
• Petition grounds — all § 103 obviousness, three grounds:
  • Ground 1: claims 1, 2, 5–12, 27–29 obvious over Putzolu (US 6,578,076) alone — a policy-server/policy-client architecture where the client "outsources" the decision to the server, mapping to independent claims 1 (method) and 27 (method) and their dependents.
  • Ground 2: claims 2, 7, 8 obvious over Putzolu in view of Rothman (US 7,826,835) — Rothman supplying the mobile-telephone policy-management context and multi-device administrator plan.
  • Ground 3: claims 13–15, 18–21 obvious over Bhat (US 2005/0021978) — local caching of an initial policy decision at the enforcement point plus receipt of an updated policy decision, mapping to independent claim 13.
  • (Grounds 1 and 2 overlap on claims 2, 7, 8, which is the normal primary/fallback structure.)
• Institution decision: instituted 2022-04-21, and the Board instituted on all challenged claims (1, 2, 5–15, 18–21, 27–29) — no partial institution and no discretionary denial under § 314(a) or § 325(d) despite the co-pending W.D. Tex. litigation (Kajeet v. Trend Micro, 6:21-cv-00389-ADA, which Kajeet's own Exhibit 2003 shows had an adverse transfer ruling and a set Markman hearing).
• Final Written Decision: 2023-04-13. Verdict at claim level: all challenged claims held unpatentable — 1, 2, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 18, 19, 20, 21, 27, 28, 29. That includes the three independent claims (1, 13, 27) and every instituted dependent claim. No challenged claim was sustained. The practical confirmation is the IPR certificate issued 2023-06-28, which records claim 27 as canceled (a third-party complaint analysis of Kajeet's parallel case states expressly: "claim 27 was subsequently canceled in an Inter Partes Review proceeding (IPR2022-00001, Certificate Issued Jun. 28, 2023)").
  • Caveat on granularity: I am reporting the claim-by-claim disposition from structured PTAB datasets (Patexia, which lists all 21 instituted claims as invalidated) and the certificate reference above, not from having read the FWD text line-by-line. Before you quote claim-level holdings in a brief, pull the FWD PDF from PTAB E2E and cite it directly.
• Motion to Amend: Kajeet did not simply defend — it filed a contingent motion to amend, then a revised contingent motion to amend under the Board's MTA pilot program (a revised MTA exists only where the Board issues preliminary guidance and the PO gets a second shot). The MTA was denied. The record shows why: the Board's preliminary guidance "disagree[d] with Patent Owner's argument that the specification discloses an alternative where enforcement is performed by a user device" (Paper 32 at 9), and Petitioner's sur-reply argued the substitute claims lacked written description under § 112 — characterizing Kajeet's supporting figure as a "doctored image" used to illustrate a "figmentary 'second embodiment,'" and noting Kajeet replaced its first expert (Sharma) after he "was forced to admit his positions were baseless." See Petitioner's Sur-Reply to PO's Revised Motion to Amend, 2023-02-16 and PO's Reply ISO Revised Contingent Motion to Amend, 2023-01-26. Net effect: no substitute claims issued. There is no amended claim set to assert.
• Settlement / termination: No settlement. This went to a contested Final Written Decision with an opposed motion to amend. Termination date 2023-04-13 (the FWD date).
• Appeal: I found no evidence of a Federal Circuit appeal. Consistent with that, the IPR certificate issued 2023-06-28, roughly two weeks after the 60-day appeal window would have closed — certificates ordinarily do not issue while an appeal is pending. Do not state as fact that no appeal was filed, but the timeline is strong circumstantial evidence, and I could not locate a CAFC docket for this IPR. Confirm via the PTAB E2E "Appeal" tab and CourtListener before relying on it.
• Defensive value: Maximal. Every claim asserted in Kajeet's district-court campaign — including claim 27, the sole claim asserted against Roqos (D. Del. 1:19-cv-02371) — is dead. If a demand letter or complaint cites claims 1, 13, or 27, the IPR certificate is a dispositive rejoinder, and continued assertion of those claims invites Rule 11 exposure. The only live questions are the never-challenged claims (below) and whether your accused product reads on them.

Strategic summary

Canceled vs. sustained vs. untested. Claims 1, 2, 5–15, 18–21, 27–29 are canceled — 21 of 29, including all three independent claims. Zero challenged claims were sustained. What remains untested by the PTAB: the claim numbers the petition did not reach. The challenge set skips 3, 4, 16, 17, and 22–26, implying those claims exist and were never adjudicated. Two important nuances: (i) I have not verified the '559 claim set or what those skipped claims recite (the claim text was not in the materials I was given) — pull the patent's claims before telling a client anything definitive; and (ii) the surviving claims are all dependents whose parent independents (1, 13, and/or 21/27) have been canceled, so they are narrow, carry the canceled claim's limitations by incorporation, and would be difficult to assert as standalone theories. A defendant's core message: the broad, commercially useful claim scope of the '559 patent has been eliminated.

Estoppel landscape. Under 35 U.S.C. § 315(e)(2), Gen Digital/NortonLifeLock — and its privies and real parties in interest — are estopped in the district courts from asserting any ground they raised or reasonably could have raised, which on this record captures Putzolu (US 6,578,076), Putzolu in view of Rothman (US 7,826,835), and Bhat (US 2005/0021978), all under § 103. That estoppel is petitioner-specific: a different defendant is not estopped and could still raise Putzolu/Rothman/Bhat or new art — though as a practical matter, claims once canceled stay canceled in rem via the 2023-06-28 certificate. The genuinely useful move for a new defendant is art aimed at the unchallenged claims, plus § 101 and § 112 attacks (note Kajeet itself litigated § 101 subject matter eligibility in its revised MTA — it argued the substitute claims recited patent-eligible subject matter under Bascom and ChargePoint — which is a signal that eligibility is contested terrain on this family).

Pattern signals. One petitioner, one petition, one proceeding on the '559 — no serial filer, no defensive aggregator. Despite Google Patents attributing the entry's source to "Unified Patents PTAB Data," the actual petitioner was NortonLifeLock/Gen Digital, a product company with its own parental-controls business (Norton Family), i.e., a commercial-competitor challenge, not a crowd-funded defensive one. Kajeet, for its part, has been an aggressive serial plaintiff on this family across at least a dozen district-court suits (W.D. Tex., C.D. Cal., D. Del. — including Lightspeed, Cujo, Mobicip, Qustodio, Impero, Roqos, Trend Micro; see Stanford NPE Litigation Database), and it litigated the IPR hard, including two rounds on the MTA and a mid-trial expert substitution. It did not, however, appear to appeal. The overall read: strong patent-owner litigation posture, weak PTAB record.

Recommended next steps

1. Get the FWD PDF and the IPR certificate. Pull the 2023-04-13 Final Written Decision and the 2023-06-28 certificate from PTAB E2E (Docket Alarm mirror) and quote the disposition verbatim. Do not rely on the secondary databases I used above for claim-level language.
2. If you are a defendant facing claims 1, 13, or 27: the certificate canceled them. Attach it to your invalidity contentions or your Rule 12 motion and state plainly that the asserted claims no longer exist. Claim 27 in particular was Kajeet's chosen vehicle against Roqos and is now gone.
3. If you are a defendant facing the unchallenged claims (3, 4, 16, 17, 22–26 — verify existence and text): those were never tested and the certificate does not help you. Build § 103 and § 112 grounds against them, and consider § 101 briefing; check whether Kajeet's own MTA arguments about those dependents' limitations became prosecution-style admissions.
4. Confirm the appeal question. Check the PTAB E2E appeal tab and CourtListener for a Kajeet v. Gen Digital CAFC docket from mid-2023. I found none, and the quick certificate issuance supports that, but "I did not find it" is not the same as "it does not exist."
5. Correct the internal docket. The "no PTAB activity" assumption in your ODP-derived block is wrong for this patent. Fix it before anyone relies on it in a clearance or FTO opinion.

Corrections to the structured block: "no AIA trial proceedings" is inaccurate — IPR2022-00001 exists, was instituted 2022-04-21, went to FWD on 2023-04-13, cancelled all challenged claims, and the certificate issued 2023-06-28. The source in the patent record attributing the IPR entry to "Unified Patents PTAB Data" refers to the data provider, not the petitioner; the petitioner was NortonLifeLock/Gen Digital.

I'll research the assignment/ownership record for US 8667559 before writing. Let me pull from multiple sources.

Let me dig into the assignment record directly and check for any post-issuance transfers.

Let me try to pull the specific assignment records for this patent from Plainsite and the USPTO assignment API.

Inventors

All six named inventors are the same set that appears on the sibling kajeet continuation applications filed the same day (Mar. 6, 2013) — e.g., Ser. Nos. 13/786,745, 13/786,703, 13/786,950:

Pattern note (no adverse finding). There is no evidence of inventors bailing out of the original assignee. To the contrary, the record shows inventors still executing confirmatory assignments to Kajeet years later — e.g., Baker as assignor on assignments dated 2020-04-21 and 2020-11-24, Neal on 2018-08-23, Politi on 2007-08-23 (Plainsite assignment index for Kajeet). A 13-year signing tail is the opposite of a founder-departure/fire-sale pattern. Kajeet's own history page confirms Neal and Weintraub are still running the company. One adjacent datapoint worth noting for completeness: the related kajeet application 13/744,342 (US 8,918,080) adds inventors Michael Merrill Flood and David Pinto — Flood/Pinto do not appear on the '559, so the '559 inventorship is a clean subset.

Original assignee

Kajeet, Inc. — named as both original and current assignee on the face of the patent (Assignee: Kajeet, Inc., Bethesda, MD at filing; the company later moved to McLean, VA).

• Did/does it ship a product embodying the claims? Yes — this is the key fact. Kajeet is an operating MVNO / managed-IoT connectivity provider (founded 2003 by three fathers; original product was a prepaid kid-safe cell service with parental WalletManager, ContactManager, TimeManager and FeatureManager controls — the very subject matter of the '559). It now sells Education Broadband for schools: the SmartSpot hotspot, SmartBus school-bus Wi-Fi, and the Sentinel cloud filtering/administration portal, sold through CDW, working with Verizon/T-Mobile/AT&T. Its own "Patents and Licensing" page expressly lists 8,667,559 among the patents "protecting" those products and services (kajeet.com/company/patents-and-licensing).
• Primary line of business: wireless/IoT connectivity + network-based policy, filtering and device management (K-12 education broadband, government/business IoT).
• Current status: operating, not dissolved, not in bankruptcy. Crunchbase lists Kajeet as "Acquired by MWP Growth Capital" (a growth-capital investment, not a liquidation); it held NTIA/DOC grant funding. Kajeet is privately held, so there are no SEC 10-K/8-K filings to cross-check; I found no Chapter 7/11 proceeding.

Assignment timeline

Scope caveat, stated plainly: I could not run a live query against assignmentcenter.uspto.gov (no interactive access from this workflow), so I am reconstructing from Google Patents legal events, Plainsite's USPTO assignment mirror, and the PTAB litigation record. Here is what is actually evidenced:

• 2007-08-06 (executed) / recorded 2020-04-21 — Reel 52457/0469
  • Conveyance: Assignment of Assignors' Interest (inventor → company)
  • Assignor: Baker, Matthew Donald; Geller, Steven Ira; Kesser, Douglas Owen; Neal, Daniel John; Politi, Carol Ann; Weintraub, Ben Julian
  • Assignee: Kajeet, Inc., P.O. Box 30804, Bethesda, MD 20824-0804
  • Correspondent: not retrieved — I could not confirm the attorney/firm of record on this reel from the sources available. Flagged as an open item rather than guessed at.
  • Context: routine inventor-to-company chain-of-title; recorded late (2020) in support of the re-filed 2020 continuations (Ser. Nos. 16/854,731 / 16/854,746). Note: the Plainsite property list for this reel-surfaced assignment shows app 13/786,966 and the 2020 filings; I could not confirm that Reel 52457/0469 is itself recorded against app 13/786,730. Treat the reel number as applying to the kajeet family, not verified line-by-line to the '559.
• No assignment of US 8,667,559 away from Kajeet, Inc. was found. Google Patents records Kajeet, Inc. as both the original and the current assignee, with no intervening "Assigned to" event for this patent. That is itself the finding: title never left the operating company.

If the Assignment Center in fact shows additional entries for this patent (in particular an inventor→Kajeet record specific to app 13/786,730, or any security interest), they were not retrievable here and should be verified directly.

Timeline diagram

timeline
    title Ownership of US 8667559
    2003 : Kajeet Inc founded
    2007 : Parent application filed
    2013 : Continuation filed Mar 6
    2014 : Patent 8667559 issued
    2018 : Kajeet begins infringement campaign
    2020 : Inventor to Kajeet assignment recorded
    2021 : Gen Digital files IPR petition
    2023 : Claim 27 canceled in IPR

NPE / troll-pattern signals

1. Shell-entity transfer — NOT PRESENT. No operating-to-licensing-LLC hop exists. Record shows Kajeet, Inc. → Kajeet, Inc. throughout (Reel 52457/0469, recorded 2020-04-21, assignee address a real corporate P.O. Box in Bethesda, MD — not a registered-agent service like CT Corporation or CSC). The "IP Holdings / Ventures" suffix pattern is absent; the current assignee is the product company itself.
2. Known asserter in the chain — NOT PRESENT. No Acacia, Marathon, IV, IPNav, Wi-LAN/Conversant, Vringo, Pendrell, Round Rock, MPHJ, Spangenberg entity, etc. appears anywhere in the chain. The Stanford NPE Litigation Database entry for patent 8667559 classifies the asserter category as "8 — Product company" for the flagship case Kajeet, Inc. v. Lightspeed Solutions, LLC (6:20-cv-00203, W.D. Tex.). Kajeet is the plaintiff, and it is a product company.
3. Repeat correspondent across the chain — UNCLEAR (not a finding). I could not retrieve the recorded assignment correspondent for Reel 52457/0469, so I cannot test for recurrence. For completeness, the litigation counsel role repeats across the campaign — Brandon C. Fernald (C.D. Cal. complaints, e.g. 8:18-cv-01519 v. Qustodio) and Jonathan Suder (W.D. Tex., e.g. 6:20-cv-01076 v. Impero) — but those are litigation counsel, not the attorneys who recorded the assignments, and a single firm doing patent work for an operating company is expressly not a finding under the stated rule.
4. Cascading transfers — NOT PRESENT. There are no consecutive assignments through chained LLCs within 24 months. Title is static from 2007 to date; the only activity is confirmatory inventor→Kajeet paperwork (2007, 2013, 2018, 2020, 2020).
5. Pre-litigation transfer — NOT PRESENT. The first infringement suits (C.D. Cal. 2:18-cv-00643 and 8:18-cv-01312, 2018) were filed roughly a decade after the 2007 inventor assignment and four years after issuance (2014-03-04). No title event sits within six months of any filing.
6. Bankruptcy fire-sale — NOT PRESENT. No Chapter 7/11; no patent sold at auction. Kajeet is operating and shipping (SmartSpot/SmartBus/Sentinel).
7. Privateering — NOT PRESENT. Kajeet asserts its own patents in its own name against commercial rivals in parental-control/network-filtering/device-management — Cujo (2:20-cv-00253), Qustodio (8:18-cv-01519), Mobicip (2:18-cv-03899), Roqos (1:19-cv-02371), Gryphon (1:19-cv-02370), Lightspeed (6:20-cv-00203), Jamf (6:20-cv-00302), Impero (6:20-cv-01076), CyberReef (1:21-cv-00004), Trend Micro (6:21-cv-00389), Infoweise (6:21-cv-00704). These are competitors in Kajeet's own market, which is ordinary operating-company assertion — not a proxy NPE suing on Kajeet's behalf.
8. Defensive aggregator — NOT PRESENT as an end-state; if anything, the inverse has occurred. IPR2022-00001 (Gen Digital Inc. f/k/a NortonLifeLock v. Kajeet, filed 2021-10-01, FWD 2023-04-13) invalidated the asserted independent claim 27, with the IPR certificate issuing 2023-06-28; and IPR2023-00178 (Trend Micro v. Kajeet, filed 2022-11-10) terminated settled (2023-09-01). Claim 27 was the claim Kajeet asserted in the Cujo and Roqos complaints. The '559's assertion value has therefore been materially eroded by third-party IPR, not neutralized by a defensive aggregator purchase.

Verdict

Operating-company assertion.

Kajeet, Inc. is both the original and the current assignee of US 8,667,559 with no recorded transfer of title to any licensing entity — the only paper in the chain is the inventor→Kajeet assignment (executed 2007-08-06, recorded 2020-04-21), so there is no shell-entity hop, no cascading LLC chain, and no pre-litigation transfer to point to. Kajeet is a genuine product company (it lists 8,667,559 on its own patents-and-licensing page covering the SmartSpot / SmartBus / Sentinel Education Broadband products) and is a plaintiff against direct competitors in parental-control and network-filtering (Cujo, Qustodio, Mobicip, Roqos, Gryphon, Lightspeed, Jamf, Impero, CyberReef, Trend Micro); the Stanford NPE Litigation Database tags the assertion as "Product company." The one caveat cutting against full assertion health is invalidation of claim 27 in IPR2022-00001 (FWD 2023-04-13; certificate 2023-06-28), which reduces — but does not convert — this into an NPE matter.

Verify at: USPTO Assignment Center — https://assignmentcenter.uspto.gov/ (search patent number 8667559; mirror at https://assignment.uspto.gov/patent/index.html). I recommend specifically confirming the correspondent of record on Reel 52457/0469 and whether an inventor→Kajeet record exists against application 13/786,730, since I could not retrieve either directly.

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

Let me retrieve the specific citation lists for this patent.

Let me try to pull the front-page citation tables directly.

Analysis: US Patent 8,667,559 — Prior Art Identification

Important methodological caveat (read first)

You asked me to look at "each patent citation for 8667559." I was not able to retrieve the front‑page "References Cited" table (the examiner/ID S citation list) for US 8,667,559 in this session. My searches returned the patent's specification text, its priority chain, its family members, and its litigation/IPR docket — but not the enumerated U.S. patent documents that were cited against it during prosecution.

Because the operating rules prohibit auto‑correcting or inventing identifiers, I will not fabricate a citation list. Below I separate (A) what is verified, (B) what is documented inside the patent itself, and (C) what I cannot verify. If you need the exact examiner citations, they must be pulled from the image file wrapper (USPTO PatentCenter for App. 13/786,730) or the Google Patents "Patent Citations" table on the front page — I could not surface those tables here.

A. Patent identification (verified)

Note: the authoritative full text you supplied contains the Description but no claims section, so I cannot map prior art claim‑by‑claim to the actual granted claim set. Any § 102 mapping below is therefore provisional and keyed to the disclosure, not to literal claim language.

B. References documented within the patent itself

These are the only citations I can verify from primary text, and each has a specific legal character:

1. Family / priority references (NOT § 102 prior art to the '559 patent)

Listed in the Cross‑Reference section of the patent:

• U.S. App. 13/763,348, filed Feb 8, 2013 (parent; issued as US 8,634,801)
• U.S. App. 13/603,218, filed Sep 4, 2012 (parent)
• U.S. App. 12/950,379, filed Nov 19, 2010 → US 8,285,249 (Oct 9, 2012)
• U.S. App. 11/881,460, filed Jul 26, 2007 → US 7,899,438 (Mar 1, 2011)
• U.S. App. 11/824,336, filed Jun 28, 2007 → US 7,945,238 (May 17, 2011) — the CIP root of the 2007‑06‑28 priority date

Legal point: because '559 claims the same 2007‑06‑28 priority, these documents share its effective filing date and are therefore not available as § 102(a) or § 102(b) prior art against it. They are relevant only to priority/§ 112 support and to intervening‑rights analysis. They would, however, be § 102(e)/§ 102(a)(2) art against third‑party later filings.

2. Commonly‑assigned related applications (also not prior art)

• U.S. App. 12/027,240, filed Feb 6, 2008 → US 7,881,697 (Feb 1, 2011)
• U.S. App. 12/950,291, filed Nov 19, 2010 → US 8,078,140 (Dec 13, 2011)
• The 19 co‑pending siblings filed 2013‑03‑06: Apps. 13/786,735; 13/786,754; 13/786,775; 13/786,788 (issued as US 8,755,768); 13/786,802; 13/786,685; 13/786,694; 13/786,703; 13/786,745; 13/786,922; 13/786,950; 13/786,966; 13/786,986; 13/787,004; 13/786,917; 13/786,949; 13/786,974; 13/787,610; 13/787,111 — all titled "Feature Management of a Communication Device"

3. Applicant‑admitted prior art (NPL) — the only substantive prior art named in the text

• Telcordia™ Converged Real‑Time Charging system, discussed in the Background: "allows users to place limited real‑time controls over prepaid and postpaid accounts… parental controls over that account can be set to limit that child's spending within a set of parameters."
  • Citations: column 2 / Background of US 8,667,559.
  • § 102 relevance: this is an admission of prior art by the applicant. Under In re Fout / Constant v. Advanced Micro‑Devices, an applicant's own characterization of a prior system can be used under § 102(b)/§ 103. It is potentially anticipatory of claims reciting real‑time limit enforcement on spend for a device feature, if the reference system is shown to disclose the full claimed combination. It almost certainly does not anticipate claims requiring multiple hierarchically‑ordered wallets with administrative precedence and backup payment — the patent expressly distinguishes itself on that ("only partial solutions").
  • Claim mapping (provisional): would target any independent claim whose novelty resides solely in "real‑time enforcement of a spending parameter over a prepaid/postpaid account." I cannot confirm such a claim exists in '559 without the claim set.

4. Standardized network protocols cited as environment (not prior art to the invention)
IS‑136 (TDMA), IS‑95 (CDMA), IS‑41, IS‑771, IS‑826 — cited merely to describe the mobile network context.

C. Prosecution signal that examiner citations exist (but I cannot name them)

The Justia record shows:

"Declaration of Matthew Donald Baker, Steven Ira Geller, Douglas Owen Kesser, Daniel John Neal, Carol Ann Politi and Ben Julian Weintraub Under 37 C.F.R. § 1.131, filed with the USPTO in U.S. Appl. No. 13/786,735 on Sep. 9, 2013, 3,757 pages."

A § 1.131 declaration is filed to swear behind a reference — i.e., to prove prior invention date and thereby remove a specific § 102(a)/§ 102(e) reference from consideration. This is strong evidence that at least one patent reference was cited and overcome on the merits in this family, but the declaration does not itself name the reference in the material I retrieved, and it was filed in sibling App. 13/786,735, not in 13/786,730. I therefore cannot attribute a specific reference to a specific claim.

D. Post‑grant challenge context (verified, but art unknown)

• PTAB IPR2022‑00001 against this patent family — status: Final Written Decision; petitioner identified as Unified Patents (portal.unifiedpatents.com/ptab/case/IPR2022-00001). The instituted grounds and the prior‑art combinations relied on in that IPR are the most current, litigation‑tested prior art on this patent, and I was unable to retrieve the petition or FWD text here. This is a gap you should close before finalizing any opinion.
• Extensive district‑court docket (D. Del. 1:19‑cv‑02370/02371, 1:20‑cv‑01339, 1:21‑cv‑00004/00005/00006; C.D. Cal. 2:18‑cv‑00643/03899, 8:18‑cv‑01312/01512, 2:20‑cv‑00253; W.D. Tex. 6:20‑cv‑00203/00302/00705/01076, 6:21‑cv‑00389/00704/00705/00707), all captioned Kajeet, Inc. v. [defendant]. The invalidity contentions in these cases are the practitioner‑curated prior‑art sets.

E. Bottom line

1. I could not enumerate the examiner's "References Cited" for US 8,667,559, and I will not invent them. The specific references to name are in the file wrapper of App. 13/786,730 and in IPR2022‑00001.
2. The only substantive prior art named inside the patent is the Telcordia Converged Real‑Time Charging system, an applicant admission. Under Constant, it would potentially anticipate only claims whose entire inventive weight rests on real‑time spend enforcement for a communication‑device feature — not the wallet‑hierarchy/administrator‑precedence subject matter that the specification positions as the invention.
3. The nineteen sibling applications and five parent/related patents are same‑priority family members and cannot be § 102 art against '559; they matter only for priority and § 112.
4. The § 1.131 declaration proves at least one reference was cited and sworn behind in this family, but it does not identify it.
5. Because the full text you supplied omits the claims, a claim‑by‑claim § 102 anticipation mapping for '559 cannot be responsibly completed without (a) the granted claims and (b) the actual cited‑reference list.

To close the gaps, retrieve: (i) Google Patents US8667559B1 → "Patent Citations" and "Cited By" tables; (ii) USPTO PatentCenter file wrapper for App. 13/786,730; (iii) PTAB IPR2022‑00001 petition and Final Written Decision. I'll gladly build the full claim‑by‑claim § 102 matrix once those citation tables are in hand.

I'll start by gathering the prior-art record for US8667559 — the claims, its cited references, and the PTAB/litigation history that produced prior-art findings.

The record shows a PTAB challenge (IPR2022-00001) with specific prior-art grounds. Let me pull the claims and the disposition of that IPR.

Preliminary note on the record I was able to verify

Before the analysis, two record-keeping caveats, because they materially affect what follows:

1. The "Prior Art" section as rendered on the page I was given is empty of a citation table. The full text supplied to me for US8667559B1 is truncated mid-sentence in the Detailed Description ("The administrator could also move funds/units between different user wallets or") and contains no "References Cited," "Cited By," or claims section. So I cannot quote verbatim claim language or a prosecution-style list of record art. I have reconstructed claim scope from the sources I could retrieve and flag every reconstruction.

2. The most probative prior-art record for this patent is not the face of the patent — it is the PTAB proceeding it attracted: IPR2022-00001, Gen Digital Inc. (NortonLifeLock) v. Kajeet, Inc., filed 2021-10-01, instituted 2022-04-21, Final Written Decision 2023-04-13, challenging claims 1-2, 5-15, 18-21, and 27-29 (PTAB case data; petition analysis mirror). That petition frames exactly the §103 combinations you are asking about, with express motivations to combine. I could not verify from the retrieved sources which claims survived the Final Written Decision; the Patexia summary lists "Claims Invalidated:" with no entry, and I have a record of a revised contingent motion to amend (substitute claims 31-32, 35-45) filed by Kajeet (PTAB Paper, 2023-01-26). Do not treat the outcome as established from this memo. The institution/FWD dates are verified; the disposition is not.

Everything below this line is analysis, not a legal conclusion.

1. The invention as claimed (reconstructed)

Per the petition's summary and the specification, the '559 patent claims a distributed, server-decided / device-enforced policy architecture for a communication device (mobile phone):

• Independent claims 1 and 27 are characterized by: a computing device sends a request to a server; the server makes a decision based on one or more policies stored at the server; the device receives the decision and enforces it, and does so without locally accessing the policies (mirror summary).
• Independent claim 13 adds local caching of the policy decision at the enforcement point plus receipt of an updated policy decision from the server, with enforcement based on both.
• Dependent claims map to the specification's feature/wallet subject matter: claim 2 (control of device features such as picture-taking / text messaging), claims 7-8 (a plurality of phones administered under an administrator-set plan with group-specific policies), claims 12, 14-15, 18-21, 28-29 (further feature-management and payment/wallet-type limitations).
• Priority: the '559 is a continuation chain descending to a continuation-in-part of Ser. No. 11/824,336, filed 2007-06-28 — the date the page lists as the prior-art date and the date Kajeet's filings assume.
• The specification's own admitted background art — prepaid accounts, low-balance alerts, rollover minutes, automated refill, parent/employer administrative controls, and the "Telcordia™ Converged Real-Time Charging system" for limited real-time parental spending controls — is material, because under §103 the applicant's own characterization of the field defines the "state of the art" against which a POSITA is measured.

Important: because I could not retrieve verbatim claim text, each mapping below is stated at the level of the limitation as reported by the petition and specification. Any limitation-specific conclusion should be re-run against the issued claims.

2. The three references actually relied on

3. Obviousness combinations

Ground 1 — Claims 1, 2, 5-12, 27-29 obvious over Putzolu alone (single-reference §103)

Rationale. Putzolu's disclosure is structurally isomorphic to independent claims 1 and 27: a client device issues a request → a server that holds the policy renders a decision → the client enforces the decision; the client "outsources" policy interpretation to the server so it does not evaluate the policies itself. That reads on the core limitation "the decision being based on one or more policies that are stored at the server" combined with device-side enforcement without local policy access.

Why a POSITA would have found this obvious rather than inventive. The only thing separating Putzolu from claim 1 is the identity of the client — Putzolu's clients are routers/switches; the claim's client is a communication device. Under KSR, substituting a known, art-recognized client for another in a policy architecture is a predictable variation where the reference teaches the technique's general applicability ("enabling centralized control of widely-distributed devices") and there is no disclosed field-of-use restriction. The patent's own background concedes that real-time, server-side parental/administrative control of account behavior was known (Telcordia CRTC), so the client-side novelty is thin. Caveat: a single-reference §103 ground must establish that Putzolu by itself renders the communication-device limitation obvious — a genuine vulnerability, since Putzolu does not name phones. Ground 2 cures this.

Ground 2 — Claims 2, 7, 8 (and dependents) obvious over Putzolu in view of Rothman

Why combine — motivation. Rothman supplies precisely the element Putzolu lacks: policy-governed mobile telephone features (picture-taking, texting) and multi-phone administration under an administrator-defined plan with group-specific policies. The motivation is the classic KSR "known technique applied to a known, ready-for-improvement device" rationale: Putzolu teaches a general-purpose policy engine/server architecture; Rothman teaches the specific, known application environment (mobile phones) and the known market demand (parental and corporate supervision of device features) that the '559 specification itself recites as the problem to be solved. Neither reference teaches away, and the combination yields no unpredictable result — the server simply decides on phone-feature policies instead of network-access policies.

Claim-level mapping. Claim 2's feature-control limitations are met by Rothman's camera/text-messaging controls. Claims 7-8's "plurality of devices under an administrator-set plan with differing policies per group or user" are met by Rothman's administrator-managed fleet with customizable group policies. The administrator role (parent/employer) is the same construct the '559 specification uses.

Ground 3 — Claims 13-15, 18-21 obvious over Bhat (and/or Putzolu + Bhat)

Why combine — motivation. Claim 13's incremental limitation is local caching of the policy decision at the enforcement point plus a later "updated" decision. Bhat discloses exactly this: an initial decision cached at the PEP, reused for subsequent requests (avoiding a round-trip), and an updated decision received when policy changes, with enforcement based on the stored decision plus the update. The motivation is expressly articulated in Bhat itself: reducing network traffic and server load. That is a recognized, results-oriented improvement in the same field (policy-based access control), which satisfies KSR's "obvious to try"/"known technique to improve a similar device" prongs. Caveat: claim 13 is an independent claim, so a Bhat-only ground must show Bhat also supplies the server-side "policies stored at the server" architecture — if it does not, the cleaner formulation is Putzolu + Bhat, with Putzolu supplying the distributed policy server and Bhat supplying caching/updates. The petition as reported ran Bhat alone for claims 13-15 and 18-21; expect the Patent Owner to attack sufficiency, as it did in its motion-to-amend briefing (arguing substitute claims not obvious over Putzolu alone or Putzolu + Rothman, Paper 43 reply).

Ground 4 (extension) — Putzolu + Rothman + Bhat, and/or + admitted background art

For a combined attack on the full challenged set (1-2, 5-15, 18-21, 27-29), the natural three-way combination is Putzolu (distributed PDP/PEP) + Rothman (mobile-phone features; administrator-managed multi-device plans) + Bhat (caching and updating policy decisions). A further, independent support is the admitted prior art in the '559 background: the Telcordia Converged Real-Time Charging system's "limited real-time controls over prepaid and postpaid accounts," including parental controls limiting a child's spending on premium data. Because that is an admission in the specification itself, it can be used as prior art without a separate publication-date fight, and it supplies the real-time/charging/parental-control motivation that a POSITA would have had to apply Putzolu's architecture to a phone.

4. Motivation-to-combine summary a POSITA would articulate

1. Same field, same problem. All three references address controlling access/use of a resource by policy decided at a central point and enforced remotely — the '559 specification's own framing ("real-time management of a device… establishment and enforcement of policies").
2. Predictable result, no field restriction. Putzolu expressly touts "centralized control of widely-distributed devices" and never limits the client to routers; Rothman teaches the phone as a policy client. Combining is a substitution of one known client type for another.
3. Demand pressure. The '559 background documents the pre-existing, well-understood demand for parental/employer feature and spend control on phones (postpaid abuse, prepaid exhaustion, alerts, Telcordia). That demand is the motivation.
4. Engineering-driven improvement. Bhat's caching is a routine efficiency improvement (bandwidth/server-load reduction) that a POSITA would apply to any client-server decision architecture, including Putzolu's.
5. Reason to expect success. The combined system runs on conventional packet-data infrastructure (the specification's own O-PDSN / AAA / PEP / PDP elements), so no new enabling technology is required.

5. Weaknesses, defenses, and what must be re-verified before reliance

• Outcome of IPR2022-00001 is unverified here. If the Panel found the challenged claims not shown unpatentable, or if Kajeet's contingent substitute claims 31-32 / 35-45 were entered, the enforceable claim scope may differ materially from claims 1-29 as I have described them.
• Rothman's critical date. Its status as §102 prior art against a 2007-06-28 priority date depends on its filing/publication date, which I could not confirm. Rothman issued 2010-11-02 (per the petition mirror); a 2010 issue date alone does not establish a pre-2007-06-28 filing date. Verify before asserting it.
• "Without locally accessing the policies." This is the most defensible limitation. If the Patent Owner construes it to require that no policy logic resides on the device, a POSITA-mapping against Putzolu's clients (which may hold some local configuration or wildcard resolution) is exposed. Putzolu's own discussion of wildcard policies and local policy installation is a double-edged disclosure.
• Wallet/payment limitations. None of Putzolu, Rothman, or Bhat appears to disclose the specification's wallet-hierarchy (precedence, backup funding, dynamic/promotional wallets). Dependent claims drawn to those features (possibly among 5-12, 14-15, 18-21, 28-29) are the strongest non-obviousness candidates and are most vulnerable to an argument that the art does not teach charging from an ordered set of accounts. Any §103 attack on those should add a pre-paid/charging-account reference (the specification itself names Telcordia CRTC).
• Secondary considerations. No evidence of objective indicia (licensing, commercial success, copying, praise) is in my retrieved record; the extensive litigation docket on this patent family (Delaware 1:19-cv-02370/02371, 1:20-cv-01339, 1:21-cv-00004/00005/00006; W.D. Tex. 6:20-cv-00203/00302/00705/01076, 6:21-cv-00389/00704/00705/00707; C.D. Cal. 2:18-cv-00643/03899, 2:20-cv-00253, 8:18-cv-01312/01512, per the page's litigation links and the Stanford NPE database) is relevant to willfulness/objective indicia but I have not analyzed those filings.
• Standing §101 overlay. Separately from §103, Kajeet's practice of asserting this family broadly means the outcome may turn on §101 more than §103; that is outside the scope of this request but worth flagging.

6. Bottom line on §103

The strongest, most defensible obviousness theory on the record I could retrieve is:

• Claims 1 and 27: obvious over Putzolu, or (better) Putzolu + Rothman to supply the mobile-device client.
• Claim 2, claims 7-8: obvious over Putzolu + Rothman.
• Claims 13-15, 18-21: obvious over Bhat, or Putzolu + Bhat.
• Full challenged set: Putzolu + Rothman + Bhat, optionally reinforced by the specification's admitted Telcordia CRTC background art.

Motivation exists, is articulated in the references themselves (centralized policy control; reduced bandwidth/server load), and is reinforced by the pre-2007 market demand the patent admits. The genuine fight is over (i) whether Putzolu's policy client satisfies "without locally accessing the policies," (ii) whether the phone-specific limitations need Rothman (they do), and (iii) the wallet/precedence dependent claims, which the cited art does not appear to reach.