US 8302185

I'll run parallel searches for the patent number and any 2026 CAFC docket activity.

Let me check for litigation/appeal activity specifically involving this patent.

Let me pull the complete claim set to identify all independent claims.

US 8,302,185 B2 — "System and method of owner control of electronic devices"

Bottom line on the 2026 docket question: I found no Court of Appeals for the Federal Circuit docket entry, appeal, or 2026 appellate activity naming U.S. Patent No. 8,302,185. Searches for that specific number in a CAFC 2026 context returned nothing. I also found no pending district-court or PTAB proceeding in which 8,302,185 is an asserted or challenged patent. Treat the absence of a hit as "not found," not as proof of non-existence — I did not have a live PACER/CAFC docket search tool.

1. Bibliographic data (per Google Patents, the authoritative text supplied)

Continuity. The patent is a continuation of Ser. No. 10/732,132 (filed Dec. 10, 2003, issued as U.S. Pat. No. 7,793,355 on Sep. 7, 2010), which in turn claims priority to U.S. Provisional Application 60/432,610, filed Dec. 12, 2002, also titled "System and Method of Owner Control of Electronic Devices." Foreign counterpart: WO 2004/053618 A2/A3 (PCT/CA2003/001944), which issued in Europe as EP 1573473 A2.

Assignment chain (per Google Patents): Research In Motion Ltd. → BlackBerry Limited (reassignment recorded 2016-02-17, change of name) → Malikie Innovations Limited (recorded 2023-06-16, assignment; and 2023-06-19, nunc pro tunc assignment).

Important caveat on term: the recorded status is "Expired – Fee Related," with an anticipated expiration of 2023-12-10. If that status is accurate, the patent ceased to be enforceable before the 2026 date of interest, which is itself a plausible reason no 2026 CAFC appeal would name it.

2. Abstract (verbatim)

"A system and method of owner control of an electronic device are provided. Owner identification information, such as data integrity and source authentication information, is stored on the electronic device. Received owner control information is stored on the electronic device where the integrity of the received owner control information is verified and/or the source is authenticated using the owner identification information. In one embodiment, owner identification information comprises an owner signature private key."

Literal-reading note: the abstract's final sentence says "owner signature private key," yet the specification consistently describes the device storing the owner's digital-signature public key (the private key is the owner's secret signing key and is kept restricted on the owner's side). I am reporting the abstract exactly as published rather than auto-correcting it.

3. Plain-language overview of the independent claims

The patent's claim set (as published on Justia's full-text page) includes claim 1 (independent, method) and claim 16 (independent, apparatus).

Claim 1 — Method of owner control of electronic devices. In plain terms: a device (e.g., a corporate-issued smartphone) receives owner information that includes owner identification information, and the owner identification information includes source authentication information. The device separately receives owner control information. The device then uses the received owner identification information to check the integrity of the owner control information, and the source authentication information is usable to authenticate that the owner control information came from the owner. The claim adds that the owner control information includes an authorized software application list that identifies an authorized application by a hash of the application, and the application is used on the device based on an integrity check against that hash.

The nub: the "branding" data installed by the owner (a key/signature) is what later validates any policy ("owner control information") pushed to the device, so a user cannot simply swap in a laxer policy file — the stated problem in the Background. Notably, claim 1 ties the authorization mechanism specifically to hashing the application, rather than to file names.

Claim 16 — Owner control apparatus. In plain terms: an apparatus comprising (a) an owner information store configured to store owner identification information having data integrity information, and (b) an owner control information store configured to store owner control information for controlling operations of an electronic device — with the remainder of the claim (truncated in my retrieved text) evidently tying the two together, i.e., the stored integrity information governs whether the owner control information is accepted/used.

Representative dependent claims (to show scope):

• Claim 2 — owner control information received at a different time than the owner information.
• Claim 3 — deciding whether to use the owner control information based on the integrity check.
• Claim 5 — the data integrity information is a digital signature.
• Claim 10–11 — checking integrity of the owner identification information by digital signature, using a symmetric or asymmetric key.
• Claim 12 — owner control information describes prohibited functions/apps and/or permitted-but-modified use.
• Claim 13 — deciding whether to perform an operation based on whether owner information exists, whether owner control information exists, and/or an operation permissions list.
• Claim 14 — receiving a digitally signed erase command to erase owner information, and performing it based on an integrity check. (This mirrors the Summary's third paragraph.)
• Claim 15 — issuing a cryptographic challenge using an on-device encryption key associated with the owner (owner's public key or a shared secret), and deciding whether to perform an operation based on the challenge result.

4. Litigation / agency activity I could confirm

• No 2026 CAFC activity tied to 8,302,185 found.
• Malikie Innovations Ltd. et al. v. Nintendo Co. Ltd. et al., No. 2:24-cv-01490-JLR (W.D. Wash., filed Sept. 17, 2024; Judge James L. Robart): asserted six patents — US 7,529,305; US 8,115,731; US 9,542,571; US 8,610,397; US 9,313,065; US 8,545,247 — against the Nintendo Switch family and Nintendo Parental Controls App. US 8,302,185 was NOT among the asserted patents. The case was dismissed with prejudice by joint stipulation under FRCP 41(a)(1)(A)(ii) on Dec. 2–3, 2025, each side bearing its own costs. (Sources: CourtListener docket, PatSnap case summary, PACER-based reporting.)
• Nintendo v. Malikie IPRs, IPR2026-00003 through IPR2026-00007 (at least IPR2026-00005 challenges US 8,545,247): the parties jointly moved to terminate in December 2025 after a global agreement — again, no indication 8,302,185 was among the challenged patents.
• UPC proceedings (Malikie v. Nintendo, Hamburg Local Division, UPC_CFI_555/2024) involve EP 2448225, and another action involves EP 2579551 — European family members, not US 8,302,185.

Related family note: Google Patents lists later applications claiming priority through this family — US 2013/0007877 A1 (Ser. No. 13/606,814), US 9,033,216 (Ser. No. 13/618,311), US 9,542,571 (Ser. No. 14/715,227), and US 10,474,841 (Ser. No. 15/402,007) — so the '571 patent that was litigated against Nintendo sits in the same priority lineage as 8,302,185.

5. Explicit uncertainties

1. Full claim set not verified. My retrieved text gave claims 1–16 only. I could not confirm the total number of claims, or whether there is a third independent claim (e.g., a computer-readable-medium or system claim beyond claim 16). Claim 16's text was returned truncated mid-limitation.
2. Legal status is a listing assumption. Google Patents itself disclaims accuracy of the "Expired – Fee Related" status and the 2023-12-10 expiration; I did not verify against USPTO Patent Center maintenance-fee records.
3. Assignee listing is explicitly flagged by Google Patents as possibly inaccurate; I did not independently confirm the Malikie/BlackBerry records.
4. No exhaustive docket search. Absence of a 2026 CAFC hit for '185 is based on web search only, not a PACER/CAFC CM-ECF or PTAB API query, and should be re-verified against primary docket sources.
5. The abstract's "owner signature private key" phrasing conflicts with the specification's public-key usage; I have quoted rather than corrected it.

I'll search patent litigation databases for US 8,302,185.

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

Let me look specifically at whether the '185 patent itself appears in any complaint or litigation.

Summary Answer

Based on the searches I was able to run, I could not identify any litigation that specifically asserts U.S. Patent No. 8,302,185 as an asserted patent in a complaint or counterclaim. I want to state that clearly rather than infer litigation from the patent owner's broader activity.

That said, there is substantial and directly relevant litigation activity in the same patent family by the current owner, which is what a reasonable search surfaced. Details below, along with an important false-positive warning.

1. No confirmed suit on the '185 patent itself

I searched litigation aggregators and the open web for the exact identifier "8,302,185" / "8302185." The results did not return a district court complaint, CAFC appeal, ITC action, or IPR that names this patent. Because I could not complete an exhaustive query of the PACER/Unified Patents docket databases (I hit a tool-call limit before those targeted lookups completed), I cannot rule out a suit entirely — but on the record I retrieved, there is no known litigation on U.S. 8,302,185 specifically.

2. Important false positive to flag

Several results mention an "'830 patent" with "control component," "power supply," and "oscillation" limitations, and IPRs (e.g., IPR2024-00570, and a Samsung IPR). That is a different patent — a haptic/vibration device patent (appears to be U.S. 9,941,830), not U.S. 8,302,185. Per your strict rule, I am not conflating them; US 8,302,185 ("System and method of owner control of electronic devices," Little & Clark) is unrelated to that haptics family.

3. Owner and family context (relevant to any litigation search)

• Current assignee: Malikie Innovations Ltd. (subsidiary of Key Patent Innovations Ltd. / KPI), per the patent record and reassignments from BlackBerry Limited in 2023.
• Original assignee: Research in Motion Ltd.
• Family members (continuations/continuation-in-part of the same disclosure) that could appear in suits instead of the '185: US 7,793,355 ('355, from app. 10/732,132); US 9,033,216; US 9,542,571 ('571); US 10,474,841; and publication US20130007877A1.

The one case I found that does assert owner-control family subject matter is:

This is the '571 patent, not the '185 patent. I flag it because the claims and specification are nearly identical to the '185 (same family), so it is the closest existent assertion of this technology — but it is a different patent number and must not be reported as an '185 case.

4. Broader Malikie campaign (for completeness — no '185 confirmed in any)

Malikie/KPI has filed numerous suits on former BlackBerry patents, e.g.:

• Acer (2:24-cv-00179) and ASUSTek (2:24-cv-00178), E.D. Tex. (asserted patents listed: 7,956,581; 8,334,847; 8,610,397; 9,179,147; 9,292,066 — none is the '185).
• MARA Holdings, 7:25-cv-00222 (W.D. Tex.) — Certicom/ECC cryptography patents.
• Core Scientific, 2:25-cv-00519 (E.D. Tex.); Foundry Digital, 7:25-cv-00567; Match Group, 3:25-cv-00381 (N.D. Tex.); Sophos, 2:24-cv-00905 (E.D. Tex.); Vivint/ADT, 2:25-cv-00554/0555; SAP, 2:25-cv-00946; and vehicle-OEM suits (Toyota, Hyundai, Honda, Stellantis, TCL, Hisense), among others.

In none of the retrieved filings, docket summaries, or RPX/Unified coverage did US 8,302,185 appear as an asserted patent.

5. Confidence and recommended verification

• High confidence: US 8,302,185 is owned by Malikie Innovations Ltd. and is in the same family as the '571 patent asserted against Nintendo.
• Low/uncertain confidence: Whether any suit asserts the '185 itself — I did not find one, but I could not complete a full PACER/Unified Patents docket sweep.

To close the gap definitively, I recommend running these exact-identifier queries, which my session did not complete:

1. Unified Patents litigation portal (portal.unifiedpatents.com/litigation) — search party "Malikie" and filter by patent "8302185."
2. PACER Case Locator / Docket Alarm / CourtListener for "8,302,185" as a full-text string.
3. RPX Empower litigations page for Malikie, checking each complaint's asserted-patent list.

If you'd like, I can run those three targeted lookups to give you a definitive yes/no.

I'll verify the structured "no PTAB activity" default against public sources before reporting.

Let me run additional targeted checks on litigation/PTAB history and any Federal Circuit activity.

One more check: whether PTAB activity exists on sibling family members (useful context, since the family shares a specification).

Proceedings overview

Zero AIA trial proceedings are on file against US 8,302,185. The USPTO Open Data Portal (the canonical source in the "PTAB proceedings on file" block) returns no IPR, PGR, or CBM naming this patent, and my independent web checks — PTAB decision text, PTAB petition documents, and Federal Circuit/News coverage — surfaced no proceeding, FWD, or CAFC appeal directed at the '185. So the breakdown is: 0 active, 0 claims invalidated, 0 claims sustained, 0 settled, 0 institution denials.

The bottom line for a defendant is therefore not "the patent is hardened," but something closer to the opposite: the '185 has never been tested at the PTAB, so no claim has ever been canceled and no § 315(e)(2) estoppel has ever attached to anyone. Two facts dominate the defensive posture instead: (1) the patent's published legal status is "Expired - Fee Related" with an anticipated expiration of 2023-12-10 — meaning any damages theory now has to be built entirely on pre-expiration conduct inside the § 286 six-year lookback; and (2) the "owner control" family around it is live and being asserted, so assertion risk has migrated to the sibling continuations, not this patent. See the family-level activity in the note below.

No proceedings to rank

Because there is no proceeding to place at the top of the list, the requested per-proceeding template is empty for the '185 itself. I am explicitly not populating it, because doing so would require inventing a proceeding number — which the instructions forbid. The only proceeding-adjacent artifact I found in the public record touches a different patent.

Family-level PTAB activity — context only, NOT US 8,302,185

Do not treat this as a proceeding on the '185. It concerns a continuation whose specification is shared with the '185.

• Patent at issue: US 9,542,571 B2 ("System and method of owner application control of electronic devices") — a continuation in the '185 family. The '185 prosecution history page shows continuation filings claiming priority to application 12/869,589 (US 9,033,216 and US 9,542,571 both trace to that 2012 continuation chain; US 10,474,841 traces to a later 2017 continuation).
• Proceeding number: not confirmed from the sources I could retrieve. A petition document for the '571 (with a supporting declaration by Dr. Nathaniel Polish) is hosted on PTAB's petition repository at https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1558569](/patent/1558569), but the snippets I retrieved do not state the trial number or the institution/denial outcome. Treat any trial number you see quoted elsewhere as unverified until you pull it in PTAB E2E (https://ptacts.uspto.gov/ptacts/).
• Grounds described in that petition: claims 1–8 and 10–20 challenged as obvious under § 103, over Hayes in view of Sprigg (Ground 3); Hayes in view of Sprigg, Frank, and Guedalia (Ground 4); and Hayes in view of Sprigg, Frank, Guedalia (Ground 5). This is meaningful art-scouting for anyone attacking the '185: Hayes and Sprigg were used to attack the shared claim concepts of "owner control information" stored in a "protected data store" and application-level memory access control.
• Related litigation: Malikie Innovations Ltd. and Key Patent Innovations Ltd. v. [Nintendo Co., Ltd.](/litigations/by-plaintiff/Nintendo%20Co.%2C%20Ltd.) and Nintendo of America Inc., W.D. Wash. No. 2:24-cv-01490-JLR, asserting the '571 (among others); Judge James L. Robart stayed the case pending the USPTO review. Reported at https://iipla.org/nintendo-successfully-pauses-blackberry-ip-suit-amid-uspto-review/.
• Defensive value: it tells you the family's claims survive an Alice challenge at the pleading stage (Malikie's opposition brief, Dkt. 61, argues the claims recite a "technological improvement" over pre-existing application-control methods), so a pure § 101 motion is unlikely to be a cheap exit.

Strategic summary

Claim status on the '185: all claims UNTESTED. None canceled, none sustained, none adjudicated anywhere the public record reflects. If you have the claim set in hand, that is the operative fact — every claim is presumptively valid under § 282 and has never been through an adversarial validity proceeding. There is no "claim 1 is dead" story here, and any demand letter asserting the '185 is asserting claims that no tribunal has narrowed.

Estoppel landscape: a blank slate. Because no IPR/PGR ran to FWD on this patent, no petitioner, real party in interest, or privy is barred under 35 U.S.C. § 315(e)(2) from raising any § 102/§ 103 ground. The other side of that coin is § 315(b): if you (or a privy/real party in interest) were served with a complaint alleging infringement of the '185 more than one year before you would file, you are time-barred from IPR entirely. Verify service dates against the pleadings before assuming IPR is available. Ex parte reexamination remains available on an expired patent and is not subject to IPR estoppel — and note Malikie is actively fighting reexams (a Unified Patents reexam request on an unrelated ex-BlackBerry video-coding patent was rejected in July 2026 on a pre-order-filing policy ground), so expect a contested reexam.

Pattern signals. No petitioner has filed multiple IPRs against the '185 — because nobody has filed any. Research In Motion Ltd. was the original assignee; the patent passed by name change to BlackBerry Limited (2016-02-17) and then to Malikie Innovations Limited (2023-06-16 and again by nunc pro tunc assignment 2023-06-19, both recorded). Malikie is a Key Patent Innovations NPE; the family is being asserted against Nintendo in the Western District of Washington and, per IAM/Law360 reporting, ex-BlackBerry assets have been asserted against a widening set of targets, with Unified Patents appearing as a challenger elsewhere in the portfolio (reexam, not IPR). No defensive aggregator has taken on the '185. The patent owner has not pursued any PTAB appeal on this patent because there was nothing to appeal.

Recommended next steps

1. Do not litigate the '185 as if an IPR already picked it apart. There is no FWD to link to. If opposing counsel represents otherwise, ask for a proceeding number and check it in PTAB E2E — the claim should not survive contact with the docket.
2. Lead with expiration. The published status is "Expired - Fee Related" (anticipated expiration 2023-12-10; source: https://patents.google.com/patent/US8302185/en). That caps the exposure timeline: under 35 U.S.C. § 286 the recoverable window reaches back only six years from the complaint, and the patent stopped reading on post-2023 conduct. Build your damages model on the intersection of those two dates, and check whether maintenance-fee lapse (as opposed to ordinary end-of-term) affects Reissue/reexam posture.
3. Run the § 315(b) clock now. If you have been served on the '185, calendar the one-year IPR bar date immediately; if it has not yet run, an IPR petition using the family art (Hayes, Sprigg) is worth costing out, because the shared specification makes that art directly applicable and no estoppel currently blocks it.
4. Check the siblings, not just this patent. US 9,033,216, US 9,542,571, and US 10,474,841 share the '185 specification. The live assertion fight is on US 9,542,571 (W.D. Wash. 2:24-cv-01490, stayed pending USPTO review). If you are being asserted, confirm which family member the plaintiff actually pleads — the '185's expiration makes it a weak vehicle, while the '571 is the one with a real enforcement campaign behind it.
5. Verify the '571 proceeding in PTAB E2E before relying on it. I could confirm a petition document exists (https://ptacts.uspto.gov/ptacts/public-informations/petitions/1558569) but not its trial number, institution outcome, or FWD. I am flagging that as an open item rather than guessing.

Caveat on sourcing: the proceeding-count statement rests on the structured ODP block in this prompt plus my web checks; PTAB E2E remains the authoritative live docket and should be re-pulled before you file anything that depends on "no PTAB activity."

I'll research the assignment record for US 8302185 before reconstructing the chain.

I'll research US patent 8302185 and its cited prior art references.

Let me get the specific references cited in US8302185.

Let me fetch the detailed references from the patent pages directly.

Prior-Art Analysis — US 8,302,185 B2

A note on method and limits up front: I was able to pull the bibliographic record and the "References Cited" listing, but I could not complete a fully enumerated USPTO PatentCenter "References Cited" download before my search budget ran out, and the authoritative full text you supplied is truncated before the claims. So: (a) the citation list below is drawn from the Google Patents record (authoritative, supplied) plus the FreePatentsOnline "References Cited" listing, and (b) because I do not have the literal claim text, the §102 mappings are potential/illustrative, keyed to the claimed features as described in the abstract and summary ("owner information store," "owner control information store," integrity/source-authentication check, signed erase command). I flag every place where I am uncertain rather than guess.

1. Identification of the patent

Critical point for §102: Because 8,302,185 is a straight continuation, its effective filing date for the disclosed subject matter is the Dec. 12, 2002 priority date. Any reference whose public date falls after 2002-12-12 does not qualify as §102(a)/(b) prior art against these claims (absent an earlier priority it can rely on). This materially narrows which cited references can actually anticipate.

2. What the claims are directed to (from the supplied abstract/summary)

The claimed subject matter, as described, centers on:

1. An owner information store holding owner information comprising data-integrity and/or source-authentication information (e.g., an owner digital-signature public key).
2. An owner control information store holding owner control information that controls device operation (e.g., authorized/required application lists).
3. Verifying integrity of received owner control information and/or authenticating the source using the owner information before storing/using it.
4. A digitally signed erase command whose execution depends on passing the integrity check.

3. U.S. patent references cited (56) — from the citation record

The listing below reflects the references cited in the 8,302,185 record. Dates shown are the grant/publication dates carried in that listing; I do not have verified filing dates for each, so I have not invented them.

Caveat: The FreePatentsOnline rendering of the "References Cited" block appears to begin mid-list (at US 6,216,116). There may be additional U.S. references above that entry that I could not retrieve. I am not asserting this is the complete U.S. list.

4. Foreign patent references cited

5. Non-patent literature and incorporated references

• Takaragi, "Angou Houshiki to Ouyou [Encryption system and Application]," Journal of Information Processing, vol. 32, No. 6, Information Processing Society of Japan, June 1991 — cited as NPL (originally raised in the Japanese prosecution of the family; also cited in related family members). General cryptographic-systems reference; if it discloses digitally signed policy/control information with a stored verification key, it could be §102(a)/(b) art (pre-2002).
• US 6,219,694 B1 (message redirection system) — not "prior art" in the classic sense; it is incorporated by reference in the specification (background, re message redirection). Should not be treated as an anticipating reference for the owner-control claims.

6. §102 anticipation assessment (potential, claim-by-claim caveat)

Because the literal claims of 8,302,185 were not in the supplied excerpt (and I did not fabricate claim text), the mapping below is stated as feature-level potential anticipation rather than a verified one-to-one claim chart:

• Claims directed to "checking integrity of received owner control information": The closest cited art is US 5,944,821 (Angelo) — secure software registration with integrity assessment — and US 6,167,521 (Smith) — code-source authentication. Both are pre-2002 and could individually or in combination read on an integrity/source-authentication limitation. Whether they disclose owner control information (as opposed to code) is the pivot; they are more likely §103 combination material than clean §102 anticipation.
• Claims directed to "authenticating the source" via stored owner information: US 5,560,008 (Johnson) (remote authentication/authorization) and US 6,216,116 (Barkan) (permits/authorizations) are the strongest §102(a)/(e) candidates.
• Claims directed to controlling which software may be installed/executed: US 6,134,659 (Sprong), US 6,134,593 (Alexander), WO 00/60434, WO 01/78395, and WO 02/097620 are the most on-point pre-2002 references; WO 02/097620 (2002-12-05) is the closest-in-time art.
• Nature of the examiner's usage (important): In the record, these references appear largely as background/§103 combination art rather than standalone anticipation — consistent with the fact that 8,302,185 issued over them (and the parent 7,793,355 also issued). I saw no single pre-2002 reference that, on its face, discloses all of: (i) a stored owner information record with integrity/source-authentication data, (ii) an owner control record, and (iii) a signed erase command gated on verification.
• Post-priority references (EP 1 427 166, GB 2 378 780): appear on the citation list but are not §102 prior art against a Dec. 12, 2002 priority date unless an earlier priority is verified.

7. Forward citations (not prior art — provided for completeness)

The record's "Cited By" set (subsequent patents/applications referencing 8,302,185) includes, among others: US 2005/0198513 (IBM, security screening of devices); US 2005/0257209 (RIM/Adams, owner application control); US 2006/0143137 and US 2006/0168196 (Intel, networked-device management); US 2007/0204324 (RIM, customizing a standardized IT policy); US 2008/0282342 (Sony, trusted-mode resource access); US 2010/0048170 (T-Mobile, software application security access management); US 2010/0275029 (RIM, installing software applications); and US 2010/0299376 / US 2010/0299152 (MobileIron, selective mobile-device management). These are later documents and cannot anticipate 8,302,185; they are only useful for family/landscape context.

8. Bottom line

• The authoritative source (Google Patents text you supplied) confirms the citation set is dominated by pre-2002 U.S. patents (Barkan, Smith, Choy, Sprong, Alexander, Angelo ×2, Travis, Johnson) plus foreign publications (EP 828209, EP 1168141, JP 2002-xxxxxx series, WO 00/60434, WO 01/71590, WO 01/78395, WO 02/097620) and the Takaragi NPL.
• The strongest §102(a) candidates (pre-2002, closest subject matter) are WO 02/097620 A2, WO 00/60434 A1, US 6,134,659, and US 5,944,821; the strongest for the "authenticate the source" element are US 5,560,008 and US 6,216,116.
• EP 1 427 166 and GB 2 378 780 are post-priority and should be excluded from §102 analysis absent an earlier verified priority.
• I could not fully enumerate/verify the complete "References Cited" list or obtain per-reference filing dates within this session, and the literal claim text of 8,302,185 was not in the supplied excerpt; therefore the claim-number-level §102 mappings above are provisional. To firm them up, the next step is a PatentCenter "References Cited" export for application 12/869,589 cross-checked against the granted claim set (which mirrors US 7,793,355). I have deliberately not invented claim numbers or filing dates I could not confirm.

I'll pull the prior-art citations for this patent and cross-check the references that the examiner and the patentee actually cited.

The fetched page appears to have omitted the front-page "References Cited" list. Let me hunt for the specific prior-art citations on the '185 page and its parent.

Obviousness analysis — US 8,302,185 B2 under 35 U.S.C. § 103

Date of analysis: April 26, 2026 · Patent: US 8,302,185 B2 · App. No. 12/869,589 · Priority date 2002‑12‑12 · Critical date for § 103 2002‑12‑12 (the effective filing date this continuation inherits from Provisional 60/432,610 and Ser. No. 10/732,132)

0. Scope note — a contradiction you asked me to flag

The instruction is to "use the results from the Prior Art section of this page." The authoritative full text supplied for US 8,302,185 B2 does not contain a "References Cited" / prior-art table at all. The only prior-art content in that text is:

• the machine-generated "Prior art keywords" field (owner; information; control information; electronic device; owner control), and
• the Background's own admission of a known scheme, quoted verbatim below.

So there is no Google‑Patents "References Cited" list in the corpus I was given, and the page fetch evidently dropped §56 front‑page material. Rather than fabricate a reference list, I reconstructed the prior art of record from two verifiable sources: (a) the international search report for the family's PCT counterpart, WO 2004/053618 A3 (PCT/CA2003/001944 — same inventors, same priority, same specification), and (b) the Google‑Patents citation tables on the parent publication US 2004/0255169 A1 and on WO 2001/078395 A1. I flag this substitution explicitly because it is a deviation from the literal task instruction.

Everything below is built on the previously generated sections (bibliography, claim 1/claim 16 characterization, dependents 2, 3, 5, 10–15, the family/assignment chain) without repeating them.

1. Prior art of record identified

R6, verbatim from the '185 specification (Background): "According to one known scheme for controlling operation of electronic devices, an owner loads a policy file onto a device to restrict the type of operations or software applications that may be executed by the device. However, this type of scheme is sometimes circumvented by a user by either deleting the owner policy file or replacing the owner policy file with a user policy file which may include fewer restrictions than the owner policy file."

Also admitted in the specification: SHA‑1 and MD5 as "known digest algorithms"; digital‑signature private/public key operation as conventional; Bluetooth, IEEE 802.11, IrDA, USB and serial transfer as conventional link types. These admissions are usable as prior art under In re Fout, 675 F.2d 297 (CCPA 1982), and are the cleanest § 103 anchors here.

Critical-date check: R1 (2000), R2 (2002‑01‑02), R3 (1998) and R4 (1999) all pre‑date 2002‑12‑12. Every reference the family examiner coded is therefore available as § 103 prior art against the '185's effective filing date — R2 under § 102(a)/(e), the rest under § 102(b).

2. Legal framework applied

Obviousness is judged under Graham v. John Deere Co., 383 U.S. 1 (1966), and KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007). The rationales I rely on are the MPEP § 2143 groupings: (A) combining prior-art elements according to known methods to yield predictable results; (B) simple substitution of one known element for another; (C) use of a known technique to improve a similar device in the same way; (D) applying a known technique to a known device ready for improvement; (F) design incentives and other market forces. Where a reference anticipates a claim (the ISR's "X" coding against the computer-readable-medium claim is an anticipation-style finding), that claim is a fortiori obvious.

Note one structural point carried over from the prior section: the '185's claim set as retrieved gave claims 1–16, with claim 1 (method) and claim 16 (apparatus) independent. But the PCT counterpart carried 30 claims, including a computer-readable-medium claim at 26/27 ("Computer-readable medium capable of causing an electronic device to perform the method of…"), which is the claim R1 was coded against. If the issued US claim set is the 16-claim set, that claim is simply absent and R1's X coding does not map onto an issued claim. I could not reconcile this and flag it as an open item.

3. Claim 1 — element-by-element

Building on the claim‑1 characterization in the prior section (receive owner information containing source‑authentication information → receive owner control information → use the identification information to check integrity of the control information → authenticate that it came from the owner → authorized‑application list identified by a hash → application used based on an integrity check against that hash):

Ground 1 (primary) — R6 (admitted prior art) in view of R1

What is missing from R6 alone: R6 teaches the policy file but not cryptographic binding of that file to the owner, which is the entire point of the patented improvement. R1 supplies precisely that mechanism — the ISR coded R1 as the single most relevant document ("X") for the claim directed to protection of device‑resident control information, at col. 4, lines 54–67.

Motivation to combine (explicit): The '185 specification articulates the problem itself — users "delet[e] the owner policy file or replac[e] the owner policy file with a user policy file which may include fewer restrictions." Under In re Gershon, 372 F.2d 535, 539 (CCPA 1967), an inventive step is assessed against an articulated identified problem; here the patentee supplied the problem statement in its own Background. A POSITA faced with the express circumvention problem has a strong, self‑evident motivation to authenticate the policy so it cannot be swapped. KSR rationale (C)/(D): applying a known authentication technique (public‑key signature verification) to a known, improvement‑ready device (a device already storing and enforcing an owner policy file).

Predictability: Nothing in the combination is unpredictable. Authenticating a configuration file with the administrator's key while the user lacks the private key is the canonical solution, and the specification concedes that the signature machinery is conventional.

Ground 2 — R6 in view of R2

R2 was cited "A" against claims 1–25 and 27–30 — i.e., the examiner considered it background to the entire independent-claim set. Its 2002‑01‑02 date makes it § 102(a)/(e) art. On the ISR's own coding, R2 is relevant across the whole claim set, which makes R6+R2 the natural "second shot" if R1's disclosure is narrower than assumed. I have not verified R2's disclosure and cannot responsibly assert a specific mapping.

Ground 3 — R4 (and/or R3) as the device-control teaching

R4 (1999) and R3 (1998) are both coded against the full independent-claim range. Where a device‑operation‑control reference is combined with an owner‑authenticated policy reference, the combination reads on claim 1 under KSR rationale (A) — known elements arranged by known methods. Again, disclosure unverified; treat as a candidate ground to develop, not a concluded one.

4. Claim 16 (apparatus) and dependents

Claim 16 recites the two‑store structure (owner‑information store with data‑integrity information; owner‑control‑information store governing device operation). This is the structural counterpart of claim 1 and falls to the same grounds. KSR rationale (B): substituting a cryptographically bound store for a plainly writable policy file is a simple substitution of one known data-handling technique for another, with predictable results. Anticipation‑avoidance is weak here because the claim's novelty lies in the content and function of the stores, not their architecture.

Dependent claims (mapping to the previously listed set):

5. Non‑obviousness positions the patentee would raise

1. Teaching away. The patentee would argue the prior art taught replacing or updating policy files freely, and that binding policy to a stored owner key forecloses legitimate re‑provisioning. This is weak: R6 describes no affirmative preference for unauthenticated policy, and the specification's own claimed solution includes re‑signed updates and signed erase commands, so the combination does not change any reference's principle of operation (the Yamashita/Shamoon line of argument visible in the PTAB materials surfaced in my searches).
2. Secondary considerations. There is a plausible long‑felt‑need story — IT departments in 2002–2003 genuinely could not prevent users from evading policy. But under WBIP, LLC v. Kohler Co., 829 F.3d 1317, 1332 (Fed. Cir. 2016), and Texas Instruments v. International Trade Commission, 988 F.2d 1165, 1178 (Fed. Cir. 1993), the patentee must show the need was persistent and recognized by those of ordinary skill and must show nexus. The '185 specification recites the need at the level of a general assertion and supplies no contemporaneous evidence of unsuccessful prior attempts. Commercial success of BlackBerry Enterprise Server IT policy would have nexus trouble because the '185's asserted contribution is a narrow mechanism, not the BES product as a whole.
3. The hash limitation in claim 1 is the most defensible hook — it is specific and narrow. But the '185 specification concedes the digest algorithms are known, so the patentee cannot argue hashing itself was inventive; the argument collapses into "applying a known integrity technique to the disclosed environment," which is KSR (A).

6. Bottom line

• The record supports a strong § 103 position against claims 1, 3, 5, 10–15 and 16, resting primarily on R6 (the patent's own admitted policy-file scheme) in view of R1 (US 6,061,794 A, the ISR's sole "X" reference), with the motivation supplied by the '185's own articulated circumvention problem.
• Representative combination that would render claim 1 obvious: R6 (owner loads a policy file restricting executable applications, circumvented by deletion/replacement) + an authenticated-control teaching of the kind in R1 (col. 4:54–67) + the specification's admitted hashing algorithms (SHA‑1/MD5). Motivation: prevent the expressly identified circumvention by binding policy to an owner‑held key; reasonable expectation of success because sign‑then‑verify was conventional.
• Confidence: moderate on the R1 anchor (number, date, "X" coding and pin‑cite verified; substantive disclosure unverified), and low on R2/R3/R4/R5 as independent grounds.
• Highest‑value next steps: (i) retrieve the §56 "References Cited" list from the '185's own front page or the file wrapper of Ser. Nos. 10/732,132 and 12/869,589, since that is the actual prior-art section you asked me to use; (ii) pull the full text of US 6,061,794 A around col. 4:54–67; (iii) confirm whether the issued '185 carries the PCT's computer-readable-medium claim, since the R1 X coding attaches to it; and (iv) confirm the issued claim count, which my prior section could not establish beyond claim 16.

Caveat carried forward from the prior section: the '185's recorded legal status is "Expired – Fee Related" with an anticipated expiration of 2023‑12‑10, per Google Patents' own disclaimer of accuracy. That does not affect the § 103 merits but does affect why any of this matters in 2026.