US 8412949

I'll search for authoritative information on US patent 8412949, including any litigation activity.

I have the patent specification. Let me get the full claim set and check for any CAFC 2026 docket activity.

Let me confirm the complete claim set and check whether '949 itself has been asserted or challenged.

US Patent 8,412,949 — Analyst Summary

Important scope note: I searched for this exact number. All substantive bibliographic and claim data below comes from the authoritative full-text you supplied (Google Patents, fetched 2026-09-29) plus the USPTO/Justia claim text returned in search. I did not find any litigation or PTAB/CAFC docket that specifically names 8,412,949. Details on that point are flagged below.

1. Bibliographic data

Family / continuations (related, not '949 itself): 13/791,553 → US 8,838,993; 14/448,891 → US 9,251,326; 14/986,306 → US 10,374,795; 16/503,066 → US 10,764,044; 16/893,155 → US 11,182,792; 17/501,734 → US 12,014,369; 18/664,076 → US 12,597,030 (issued 2026-04-07). The patent is flagged by Google Patents as part of a family with litigation.

2. Abstract (verbatim)

"A system and method provide efficient, secure, and highly reliable authentication for transaction processing and/or access control applications. A personal digital key (PDK) is programmed using a trusted programming device to initialize and/or register the PDK for use. In one embodiment, the initialization and registration processes are administered by a specialized trusted Notary to ensure the processes follow defined security procedures. In a biometric initialization, the programming device acquires a biometric input from a user and writes the biometric data to a tamperproof memory in the PDK. In registration, the Programmer communicates to one or more remote registries to create or update entries associated with the user PDK. Once initialized and registered, the PDK can be used for various levels of secure authentication processes."

3. Independent claims — plain language

The claim set as retrieved is a method claim (1) and an apparatus claim (15). (See uncertainty note in §5.)

Claim 1 — Method of using a programming device to initialize a PDK

1. Read user information from the user's PDK (the PDK is a separate device from the Programmer).
2. Determine the user PDK's status using a registry that holds status data about the PDK.
3. If the user PDK is in good standing, determine the user is authorized for initialization.
4. Read notary information from a notary PDK.
5. Determine the notary PDK is authorized to witness the initialization.
6. Acquire a biometric input from the user via the Programmer.
7. Receive data from the notary PDK indicating the notary witnessed the biometric acquisition.
8. If both user and notary are authorized, generate a biometric profile including the biometric input.
9. Store the biometric profile on the user's PDK.

Representative dependent claims: good standing = not lost/stolen/expired/revoked (2), or never initialized (3); scan + transform (hash) the biometric (4) with quality check and re-scan (5); store initialization history (user PDK ID, notary ID, programmer ID, site ID) on the Programmer (6) and on the user PDK (7); mutual hardware authentication — the user PDK validates the Programmer before initialization proceeds (8); notary authorization via registry status check (9–10); Programmer good-standing check incl. unaltered software (11–12); remote notary (13); and transmitting registry information to a remote registry to add/update an entry (14).

Claim 15 — Apparatus (Programmer) for programming a user's PDK
An apparatus with: (a) a PDK interface that receives user information from a user PDK separate from the apparatus and notary information from a notary PDK; (b) a biometric reader that acquires a biometric input from the user; and (c) a processor coupled to both, adapted to determine the user PDK's status against a remote registry, determine the user is authorized for initialization based at least in part on the user information, and — the claim text was truncated at this point in the retrieved source — proceed with the witnessed initialization scheme described in claim 1.

4. Litigation / PTAB / CAFC status — what I could and could not verify

• No docket entry naming US 8,412,949 was found. The Proxense enforcement campaign documents I retrieved assert other patents from the same family — e.g., in Proxense v. Google (W.D. Tex. 6:23-cv-320) the asserted patents listed are US 8,352,730 ('730), US 8,886,954 ('954), US 9,928,905 ('905), US 8,646,042 ('042), US 9,679,289 ('289), and US 10,073,960 ('960). '949 does not appear in that list.
• Federal Circuit activity in 2026 relates to '954, not '949. Per ip fray, Proxense's Federal Circuit opening brief argues the PTAB abused its discretion by staying a parallel ex parte reexamination and quashing the examiner's positive determination. That appeal arises from IPRs of US 8,886,954 ("Biometric personal data key (PDK) authentication") — a different patent number. I found no CAFC appeal docketed in 2026 for 8,412,949.
• PTAB activity: the IPRs/rexams I saw cover '730, '954, '905, '989, '700, and the hybrid-device patents ('042/'289). A Sept 21, 2026 Bloomberg Law report describes a PTAB obviousness ruling against a Proxense patent "relating to a hybrid device having a personal digital key and receiver-decoder circuit," in an Apple IPR — that subject matter points to the hybrid-device patents, not '949.
• Bottom line: Based only on the sources I could retrieve, I have no authoritative evidence that 8,412,949 has been asserted in district court, challenged at the PTAB, or docketed at the CAFC in 2026. It may be in a family "with litigation" (Google flags family-level litigation), but the number itself is not confirmed in any retrieved docket. Treat any assertion that '949 is on a 2026 CAFC docket as unverified.

5. Explicit uncertainties

1. Full claim set not fully retrieved. I have verified text for claims 1–14 and only the preamble/body-opening of claim 15. I do not know the exact total number of claims, the full text of claim 15, or whether any independent claim beyond 1 and 15 exists. I will not guess at these.
2. Priority date discrepancy across sources. Google Patents shows the prior-art/priority date as 2006-05-05. A Unified Patents entry for a different family member (US 2015/0026480 A1, app. 14/448,891) lists priority 2006-05-04. I did not find a basis to reconcile this, and it does not clearly apply to '949.
3. No independent verification of the CAFC 2026 docket absent a search hit. My conclusion in §4 is a negative finding from available results, not proof of absence; a PACER/CAFC docket search by case number would be needed to be definitive.
4. Per your standing rule, I have used the identifiers exactly as they appear (e.g., "8,412,949," "8,886,954," "8,352,730") and have not auto-corrected any of them.

I'll search for litigation involving US patent 8412949 across patent litigation databases.

Let me refine my search to look for Proxense's known patent campaigns and check litigation databases.

Let me search more specifically for the '949 patent being asserted, and check Unified Patents and RPX.

Summary conclusion

I did not find any litigation in which US Patent No. 8,412,949 ("Personal digital key initialization and registration for secure transactions," Proxense, LLC) was specifically asserted. The patent's owner, Proxense, LLC, has been a prolific patent plaintiff in the Western District of Texas (Waco Division, Judge Alan D. Albright) since ~2020, but in every Proxense complaint I could retrieve, the asserted patents are sibling patents in the same PDK/family — not the '949 patent itself.

I want to be transparent: this is a negative finding based on the searches I was able to complete, not a certified "no litigation exists." I was unable to directly query PACER or the Unified Patents litigation caselist (searches for those endpoints did not return usable case lists for this number), so a residual possibility remains that a short-lived or non-Texas suit exists. The one affirmative signal in favor of litigation is the Google Patents "Family has litigation" / Darts‑IP flag on this patent's page (https://patents.google.com/patent/[US8412949](/patent/US8412949)/en), but that flag attaches to the patent family, not necessarily to the '949 patent individually.

What the searches did surface (and why they are not the '949 patent)

Every Proxense case I located asserts a defined set of patents, and 8,412,949 does not appear in any of those sets:

Sources: Google Patents page for US8412949; Darts‑IP family litigation link; Docket Alarm / CourtListener dockets and pleadings (e.g., https://www.courtlistener.com/docket/67312721/1/4/proxense-llc-v-microsoft-corporation/ ; https://www.docketalarm.com/cases/[PTAB](/ptab)/IPR2024-01399/...Exhibit-1027... ; https://insight.rpxcorp.com/litigation/txwdce-[1217252](/patent/1217252)-proxense-v-microsoft#overview ; https://unicourt.com/case/pc-db5-casegub80976f1a2f6-[1837728](/patent/1837728) ; https://ai-lab.exparte.com/case/ptab/IPR2021-01447/doc/12).

Notably, the related IPR proceedings I saw (e.g., IPR2021‑01439, IPR2021‑01447, IPR2024‑00232/00775/01333, IPR2024‑00784, IPR2024‑01399, IPR2024‑00846) all target patents such as 9,298,905; 9,235,700; 8,352,730 — again not 8,412,949.

Important nuance about the '949 patent's family

US 8,412,949 has a prosecution/priority family that includes US 8,838,993; US 9,251,326; US 10,374,795; US 10,764,044; US 11,182,792; US 12,014,369; and US 12,597,030 (per the Google Patents family timeline). The Google Patents page carries a "Family has litigation" flag with a Darts‑IP link, which indicates some member(s) of this family have been litigated — but that does not establish that the '949 patent itself was asserted, and my retrieved Proxense complains do not name it.

What I could not verify

• PACER / Unified Patents caselist: I was unable to retrieve a clean case list for 8,412,949 from https://portal.unifiedpatents.com/litigation/caselist or PACER. No hit matching the exact number appeared.
• Any pre-Proxense or non‑W.D. Tex. suit: none surfaced.
• The Target (6:20‑cv‑00879) and LG complaints were retrieved only in part, so I could not fully confirm their complete asserted-patent lists.

Caveat on identifiers

Per the strict rule, I have not auto-corrected any alphanumeric identifiers. Two identifiers in the retrieved Intel complaint text appear irregular as literally returned — "8,457,62" and "9,251,332" — and I am reproducing them exactly as retrieved rather than assuming intended numbers.

Bottom line: Based on available sources, no litigation is known that specifically asserts US 8,412,949; the Proxense campaigns litigate closely related PDK-family patents. To confirm definitively, I would recommend a direct PACER docket search on the patent number, an RPX Insight "patents-in-suit" lookup, and a Unified Patents portal search — which I was not able to complete here.

If you want, I can run another targeted pass against RPX Insight's patent page or the Darts‑IP family link to try to pin down the exact family member(s) litigated.

I'll start by checking the live record for any AIA trial proceedings involving this patent, since the ODP structured data reports none.

Let me search specifically for the '949 patent in PTAB proceedings and its litigation history.

The searches so far show extensive PTAB activity against Proxense's related patents, but nothing yet on the '949 itself. Let me dig specifically into the Samsung 2021 IPRs and the '949's assertion history.

Proceedings overview

Total AIA trial proceedings on US 8,412,949: 0. There is nothing to break down by status (no active trials, no claims invalidated, no claims sustained, no settlements, no institution denials) — the patent's PTAB trial history is empty as of the ODP ingest and as of my independent searches on 2026-09-29. The bottom-line defensive posture for a defendant is therefore unusual and worth reading carefully: the '949 patent has never been tested at the Board, but its sibling and child patents in the same Proxense family have been challenged repeatedly and have fared badly — several have had all claims cancelled or held unpatentable. So the patent is not "hardened" by survival; it is simply untested, and the family-level record gives a defendant both a roadmap and a caution.

No proceedings on file for the '949 patent

I could not identify any IPR, PGR, or CBM naming U.S. Patent No. 8,412,949 as the challenged patent. I will not invent a proceeding number to fill this template. The structured ODP block states the API returns no AIA trial proceedings, and my searches across Google Patents, Docket Alarm's PTAB docket index, CourtListener, and IP/legal news returned no petition, institution decision, FWD, or appeal captioned against the '949.

What I did find is that essentially every other asserted Proxense patent in this family has been or is being challenged at the PTAB. That is the finding that matters to a defendant, so I lay it out below — clearly labeled as family-level context, not proceedings on the '949.

Family-level PTAB context (NOT proceedings on the '949)

None of the following represents an AIA trial on the '949 patent. They are listed to show the litigation/PTAB neighborhood, because a defendant assessing the '949 will inevitably be looking at the same cast.

Recurring panel on the Proxense matters: APJs Thu A. Dang, David C. McKone, and Norman H. Beamer (and Kevin F. Turner on IPR2024-00846). Proxense's lead counsel is David L. Hecht (Hecht Partners LLP); petitioners have been represented by Finnegan (Google), Duane Morris (Apple), and Fish & Richardson (Microsoft service address).

Also on the family (not AIA trials, and none confirmed on the '949): ex parte reexaminations 90/015,052 ('730), 90/015,053 ('905), and 90/015,054 (Giobbi application). The Board stayed reexam '052 pending IPR2024-00232 and admonished Proxense for failing to update its mandatory notices.

Strategic summary

Claim status on the '949 itself: entirely UNTESTED. No claim of US 8,412,949 has been cancelled, confirmed, or even construed by the PTAB. Its claims remain presumptively valid and fully enforceable (subject to district-court challenges). Contrast this with the family: the '730 patent had all claims (1–17) cancelled via adverse judgment on 2025-04-28, and the '905 and '042 patents had all challenged claims held unpatentable in FWDs on 2025-07-17 and 2025-08-04 respectively — both now on appeal. If a demand letter or complaint you receive cites the '949, you cannot point to a cancelled claim of this patent. You can, however, point to a family-wide pattern in which Proxense conceded or lost claim sets before the Board.

Estoppel landscape. Because there is no IPR on the '949, § 315(e)(2) estoppel has not attached to anyone with respect to this patent. No petitioner is barred from raising § 102/§ 103 grounds against the '949 in district court, and no institution decision has defined the ground set. Conversely, Proxense is not estopped either. The practical upshot is that a defendant's invalidity case on the '949 is unconstrained — the full prior art may be run, including art already used in the family IPRs (Ludtke, Kon, Lapsley, etc.) and, importantly, Proxense's own adverse admissions in the sibling proceedings (e.g., its concessions of unpatentability that produced the '730 cancellations) are fair game as statements against interest and for § 325(d)/IPR-similarity arguments.

Pattern signals. The same petitioners are filing serially across the Proxense portfolio: Microsoft (00775, 00405, 00407, 00573, 00846, 01327, 01398, 00776), Google (00232, 00233, 00234, 00782–00784, 01318–01320), and Apple (01318–01335 range, 01485, 01486, 00074, 00562). The pattern is textbook: challenge the asserted claims of each patent Proxense pleases into litigation (Proxense v. Microsoft 6:23-cv-00319; Proxense v. Google 6:23-cv-00320; Proxense v. Apple 6:24-cv-00143; Proxense v. Samsung 6:21-cv-00210 — all W.D. Tex., Judge Alan D. Albright). Proxense has been filing or joining appeals aggressively (notices of appeal in IPR2024-00573/'042 on 2025-10-06, and CAFC No. 25-2130 in the '905 case), which signals it is still contesting the family losses. I found no evidence of a defensive aggregator (e.g., Unified Patents) as petitioner; the challenges are all Big-Tech defendants responding to assertion. (Unified Patents' portal appears as a data source, not as a petitioner here.)

Recommended next steps

• If you are a defendant and the '949 is asserted against you: the absence of an IPR on the '949 is the headline. There is no cancelled claim to cite and no FWD to quote. Your invalidity defense must be built from scratch — but you can borrow heavily from the family IPRs, where Proxense has already conceded or lost the same specification's claims. Start by pulling the '730 adverse-judgment orders (IPR2024-00232 and IPR2024-00775, both 2025-04-28, PTAB) and the '905 and '042 FWDs (2025-07-17 and 2025-08-04), because the '949 shares the specification and prosecution lineage (11/744,832 → 8,412,949 → 8,838,993 → 9,251,326 → 10,374,795 → 10,764,044 → 11,182,792 → 12,014,369 → 12,597,030).
• Confirm the negative before relying on it. Verify directly on PTAB E2E / PTAB Center and the USPTO ODP that no petition is pending against 8,412,949 — a recently filed petition may not yet be indexed. A timely-filed IPR on the '949 could change the posture materially and trigger § 315(b) timing analysis against the underlying district-court complaint date.
• Calendar the family's appeal deadlines. The '905 and '042 FWDs are on appeal (CAFC 25-2130 and the '042 appeal noticed 2025-10-06). Federal Circuit dispositions there will directly affect the validity narrative for the shared specification and may produce claim-construction or § 112 ¶ 6 rulings that a '949 defendant can leverage.
• Watch the ex parte reexams. 90/015,052, -053, and -054 remain live family-side validity challenges. Though not AIA trials, their outcomes can alter claim scope in related patents and bear on obviousness-type double patenting and terminal-disclaimer issues touching the '949.
• On timing: because there is no active IPR on the '949, there are no institution-decision, oral-hearing, or statutory 1-year FWD milestones to track for this patent. The relevant clocks are those of the pending sibling trials and their Federal Circuit appeals.

Verification note / limits. This analysis rests on (i) the structured ODP block stating no AIA proceedings, and (ii) web sources including the Google Patents page for US 8,412,949, Docket Alarm's PTAB docket index, CourtListener RECAP filings, and IP/legal news. I did not have direct access to a PTAB E2E docket for the '949, so I cannot rule out a very recently filed petition that is not yet indexed. Where I could not verify a fact — including whether the '949 was among the patents asserted in the Samsung, Google, Microsoft, or Apple complaints — I have said so rather than assert it. All dates are YYYY-MM-DD.

I'll research this patent's ownership chain across the sources you named. Let me start with several parallel searches.

Good — Proxense is clearly the key entity. Let me dig into the assignment records and the litigation/enforcement history.

US 8,412,949 B2 — Ownership Chain Reconstruction

Patent: Personal digital key initialization and registration for secure transactions
App. No.: 11/744,832 · Filed: 2007-05-05 · Priority: 2006-05-05 · Issued: 2013-04-02
Current assignee of record (per Google Patents legal events): Proxense, LLC

Data-availability caveat (read first): I was able to confirm the existence and date of a recorded assignment from the Google Patents legal-events tab, but I could not retrieve the reel/frame number, execution date, or recorded correspondent for the assignment on THIS patent from the sources reachable in this session. I have not invented those values. Where a related-patent data point is the only evidence available, it is labeled as such. Verify the missing fields directly at the USPTO Assignment Center: https://assignmentcenter.uspto.gov/ and https://assignment.uspto.gov/patent/index.html (search "8412949").

Inventors

All three are named as assignors on the initial assignment recorded 2007-07-24 (Google Patents legal events, "ASSIGNMENT OF ASSIGNORS INTEREST," assignors BROWN, DAVID L.; HIRT, FRED S.; GIOBBI, JOHN J.), which establishes they were under an obligation to assign to Proxense at filing. Giobbi is the recurring named inventor across the Proxense family (e.g., title of related app. 14/521,982 → US 9,298,905 lists "Inventor: John J. Giobbi").

Unusual patterns: None detected. I found no evidence of inventors departing the original assignee within 12 months of filing, and no evidence of a pre-issuance portfolio dump. The "all inventors leaving" fire-sale tell does not appear here — the same inventor group stayed associated with Proxense's prosecution across the family.

Original assignee

PROXENSE, LLC — a Bend, Oregon company (recorded address in the family: 689 NW Stonepine Drive, Bend, Oregon 97701).

• Business: Per its own 2016 portfolio-sale letter, Proxense was "established in 2005 and developed and commercialized fundamental technologies related to electronic identification, electronic commerce, access control and location tracking." So it began life as an operating startup, not a paper LLC.
• Did it ship a product embodying the claims? Historically asserted to have commercialized, but no current product evidence found. By July 2016 the company stated it had "never engaged in any patent enforcement litigation" and that "there are no current licenses granted under the Proxense patents." That is a licensor-holdout posture, not a shipping-product posture, and I found no product revenue or SKU evidence.
• Current status: Still in existence and operating as an IP-holding / monetization entity. No bankruptcy, dissolution, or assignment-out of record was found. It is now an active patent plaintiff (see NPE section).

Assignment timeline

Only one recorded assignment could be confirmed for US 8,412,949.

• 2007-07-24 (recorded) — Reel/Frame not retrieved (field unavailable from indexed sources; verify at Assignment Center)
  • Conveyance: Assignment of Assignors' Interest (inventor → company)
  • Assignor(s): David L. Brown; Fred S. Hirt; John J. Giobbi
  • Assignee: Proxense, LLC (Bend, Oregon)
  • Correspondent: Not retrieved for this patent. Adjacent data point (different patent, same owner/family): on related app. 14/521,982 → US 9,298,905, the inventor→Proxense assignment was recorded at Reel/Frame 034843/0145 (executed/recorded 2015-01-29) with correspondent Paige M. Alsbury, 201 S. Main Street, Suite 250, Salt Lake City, UT 84111. Because that is a different patent, it is flagged as context only — not as a record entry in this chain, and it does not by itself satisfy the "repeat correspondent" test.
  • Context: Initial founder/inventor-to-company assignment. No consideration event, no third-party transfer.

No post-issuance assignment of record was found. There is no assignment to any licensing-only LLC, no security interest, no merger, and no defensive-aggregator transfer on this patent. Per Google Patents, Proxense, LLC remains the current assignee, with an adjusted expiration of 2029-08-13.

Timeline diagram

timeline
    title Ownership of US 8412949
    2006 : Priority provisional filed
    2007 : Application filed by Proxense
         : Inventors assign rights to Proxense
    2013 : Patent issued to Proxense
    2016 : Proxense offers portfolio for sale
    2021 : Proxense sues Samsung
    2024 : Proxense sues Apple and Intel

NPE / troll-pattern signals

1. Shell-entity transfer — NOT PRESENT. The chain contains only the inventor→Proxense assignment (recorded 2007-07-24). The patent never left the original operating assignee. No "IP/Holdings/Licensing/Ventures" LLC appears anywhere in the record, and no registered-agent-service address is present.

2. Known asserter in the chain — PARTIALLY PRESENT (current owner is a high-frequency plaintiff). Proxense, LLC is not one of the classic named NPEs (Acacia, Marathon, IV, Wi-LAN, etc.), but it is tracked as an active patent plaintiff by both RPX Insight (https://insight.rpxcorp.com/litigation/txwdce-1172779468-proxense-v-apple) and Unified Patents (portal lists Proxense LLC as assignee of the family, e.g. https://portal.unifiedpatents.com/patents/patent/US-[6683954](/patent/6683954)-B1). It has asserted across a family including US 8,352,730; 8,886,954; 9,298,905; 8,646,042; 9,679,289; 9,049,188 against Apple, Samsung, Intel, Google, and Microsoft. The '949 patent is not among the currently asserted patents-in-suit in those campaigns, but it belongs to the same asserted family.

3. Repeat correspondent across the chain — UNCLEAR / INSUFFICIENT DATA. The chain has a single link, so recurrence within this chain cannot exist by definition. The one Proxense correspondent I could document (Paige M. Alsbury, Salt Lake City, UT) appears on a different patent's assignment (Reel/Frame 034843/0145), not on '949. I have no attorney name for the '949 recording. Note also Greg T. Gsuocka (gsuocka@patentlawworks.net), who authored Proxense's 2016 portfolio-sale/§287 notice letters — but that is enforcement/notice counsel, not an assignment correspondent.

4. Cascading transfers — NOT PRESENT. Zero chained LLC-to-LLC transfers; a single recorded assignment in ~16 years.

5. Pre-litigation transfer — NOT PRESENT. The only assignment (2007) predates the first Proxense assertion campaign (Samsung, filed 2021-03-05) by roughly 14 years. Nothing was transferred within 6 months of any suit.

6. Bankruptcy fire-sale — NOT PRESENT. No Chapter 7/11, no sale order, no assignment out of a proceeding. Note, however, Proxense's 2016 offer to sell the entire portfolio (letter to Tim Cook/Apple dated July 25, 2016, filed as Doc. 1-39 in 6:24-cv-00143) — an attempted private sale that, on the record available, did not close (the patent remains with Proxense).

7. Privateering — NOT PRESENT (inverse). Privateering requires an operating company transferring to an NPE that sues on its behalf. Here the original developer is the asserter; there was no transfer to a proxy. Not applicable.

8. Defensive aggregator — NOT PRESENT. The chain does not terminate at RPX, AST, LOT, Unified, or OIN. Unified Patents appears only as an adverse challenger/monitor of Proxense, not as an owner.

Verdict

NPE — moderate confidence.

There is exactly one recorded assignment — inventors → Proxense, LLC, recorded 2007-07-24 — and no subsequent transfer of record, so the owner of '949 is the original operating assignee rather than a shell LLC; that fact alone rules out the classic shell-entity cascade (signals 1, 4, 5, 6 all absent). What pushes toward "NPE — moderate" is the current owner's conduct: Proxense is a high-frequency patent plaintiff tracked by RPX and Unified Patents, and its own 2016 portfolio letter expressly marketed the family as having "no current licenses" so that a buyer "will be able to use the Proxense patents offensively" — a monetization, not manufacturing, thesis. That is one strong-ish assertion signal plus the absence of any product evidence, warranting moderate rather than high confidence; the missing reel/frame and correspondent fields mean this should be re-verified before reliance.

Verification: https://assignmentcenter.uspto.gov/ (search patent 8412949) · https://patents.google.com/patent/US8412949/en (legal events)

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

Let me dig deeper for the specific cited references in this patent.

Let me look for the patent's front-page references directly from a patent database.

Prior-Art Analysis: US Patent No. 8,412,949

1. Confirmed Identification of the Patent

I have confirmed the patent against the authoritative Google Patents record (fetched 2026‑09‑29) and secondary databases. Interpreting the identifier literally, US 8,412,949 is:

Note: My initial searches also returned an unrelated US 2,676,005 ("Disintegrating and gathering chain") and a mining-tools listing that happened to also display the string "US8412949." Those are false hits and are excluded per your instruction to return only the specific patent and its references.

2. Important Limitation on the Citation List (Stated Explicitly)

I was not able to retrieve the authoritative USPTO front-page "(56) References Cited" list for US 8,412,949. My searches hit retrieval limits before I could pull the examiner-cited U.S. patent documents, foreign documents, and non-patent literature. Per my operating rules, I will not fabricate cited reference numbers, dates, or § 102 mappings. What follows distinguishes (a) references I could verify from the patent document itself, from (b) items I could not confirm.

Also note: the claims text was not included in the authoritative document text supplied to me, so I cannot perform a precise claim-by-claim anticipation mapping. Any reference-level § 102 statement below is therefore framed at the level of the disclosed subject matter, not tied to specific claim numbers.

3. References Verified From the Patent Document Itself

These appear on the face of the specification. They are incorporated-by-reference and/or same-family applications — not third-party prior art — and therefore generally cannot anticipate this patent (they share inventors/priority and, where applicable, are the applicant's own work):

Related family members (continuations/divisionals — NOT prior art)

These are later filings claiming priority from 11/744,832, so they cannot be § 102 art against it:

• US 13/791,553 → US 8,838,993 B2
• US 14/448,891 → US 9,251,326 B2
• US 14/986,306 → US 10,374,795 B1
• US 16/503,066 → US 10,764,044 B1
• US 16/893,155 → US 11,182,792 B2
• US 17/501,734 → US 12,014,369 B2
• US 18/664,076 → US 12,597,030 B2

4. What the § 102 Inquiry Actually Requires Here

Because I could not retrieve the examiner-cited references, I can only outline the framework the analysis must follow. For any candidate reference against US 8,412,949, the reference must:

1. Qualify as prior art under § 102(a)(1)/(a)(2) (post-AIA) or pre-AIA § 102(a)/(b)/(e) — i.e., have an effective date before 2006‑05‑05 (or, for § 102(b)/102(a)(1) printed-publication art, before 2006‑05‑05) and not be disqualified (e.g., not the inventors' own work within the grace-period/commonly-owned exceptions).
2. Disclose every limitation of a given claim, arranged as in the claim, for § 102 anticipation.

The patent's independent claim(s) as issued are directed to a trusted initialization/registration method and system — i.e., a Programmer that (a) validates a user PDK and a Notary PDK against a registry, (b) acquires a biometric input witnessed by the Notary, (c) writes a biometric profile to tamperproof PDK memory, and (d) writes and stores initialization/registration history for auditing (see the Summary: "the Programmer is communicatively coupled with a PDK from the user and a PDK from the Notary … If both the user and the Notary are authorized, the Programmer prompts the user to provide a biometric input"). A § 102 grant would require a single reference teaching this notarized, dual-PDK, registry-validated enrollment combination — a relatively specific combination.

5. Recommendation to Complete the Analysis

To close this properly and cite real references, the following authoritative sources should be pulled directly (I could not complete these retrievals):

• USPTO Patent Center / Public PAIR for application 11/744,832 → "References Cited" (Form PTO‑892), and the examiner's Non‑Final/Notice of Allowance citing the art actually relied upon.
• Google Patents → "Citations" tab for US 8,412,949 (patent and non-patent literature cited during prosecution).
• Docket/PTAB and District Court records — the Google Patents record notes "Family has litigation" (Darts‑IP family 38694426), and PTO petitions in this family (e.g., documents referencing Proxense/related patents) can reveal the prior art actually asserted.

6. Bottom Line

• US 8,412,949 is correctly identified as the Proxense "Personal digital key initialization and registration" patent (Giobbi/Brown/Hirt; app. 11/744,832; priority 2006‑05‑05; granted 2013‑04‑02).
• The references I could verify appear in the patent text are its own family/incorporated-by-reference applications and priority provisionals — these are not § 102 prior art against it.
• I could not verify the patent's examiner-cited "(56) References Cited" list, and the claim text was not provided to me, so I cannot responsibly name specific anticipating references or map them to specific claims. I am flagging this rather than inventing citations or § 102 conclusions. Pulling the PTO‑892 and the prosecution file wrapper (Section 5) is the required next step.

I'll start by gathering grounding information, since the provided page text appears to be truncated before the claims and does not include a citations/prior-art list.

Let me try to retrieve the patent's citation/prior-art lists and any PTAB/litigation record for this specific patent.

Let me pin down which prior-art references were actually asserted against this patent and its family, and try to retrieve the patent's own "References Cited" list.

Obviousness Analysis — U.S. Patent No. 8,412,949 B2

Patent: "Personal Digital Key Initialization and Registration for Secure Transactions" (Giobbi, Brown, Hirt; assignee Proxense LLC). Filed 2007‑05‑05; priority 2006‑05‑05 (provisionals 60/798,172; 60/798,843; 60/838,788; 60/824,758; 60/894,608); granted 2013‑04‑02. Source: https://patents.google.com/patent/[US8412949B2](/patent/US8412949B2)/en

A. Threshold caveat on the record (read this first)

Three things materially limit how far I can take this analysis, and I will not paper over them:

1. The supplied page text is truncated before the claims. It ends mid‑sentence in the description ("In another e…"). I therefore cannot quote or chart claim 1 as issued, and I will not reconstruct claim language and present it as verified. My analysis runs against the disclosed subject matter (Abstract, Summary, FIGS. 8–14 descriptions) at the level of generality that this family's claims are known to track, and I flag below where claim text is essential.
2. The page's "Prior Art" block is not a citation list. What the Google Patents page exposes under prior art is (a) auto‑generated "Prior art keywords" — pdk, user, notary, biometric, information — and (b) the applicant's own incorporated applications and provisional priority documents. Google Patents' "Prior art keywords" are an algorithmic extraction from the document, not art of record. There is no "References Cited" / examiner‑citation list in the material I was given.
3. Consequences for § 103: the references the patent incorporates by reference — U.S. App. Ser. Nos. 11/292,330 (filed 2005‑11‑30), 11/620,581 and 11/620,577 (both filed 2007‑01‑05) — are commonly owned (all Proxense/Giobbi) and therefore largely disqualified as § 103 art under pre‑AIA 35 U.S.C. § 103(c)(1), and in any event 11/620,581 and 11/620,577 post‑date the 2006‑05‑05 priority date. The provisionals 60/798,172 et al. are priority documents, not prior art. That leaves, on this page, only the background art the applicant itself admits in the "Description of the Related Art" — a legally significant admission.

B. Governing law and framework

The application was filed before 16 March 2013, so pre‑AIA 35 U.S.C. § 103(a) applies. That means: (i) the effective filing date is presumptively 2006‑05‑05, and prior art must predate it (§ 102(a)/(b)/(e)); (ii) § 103(c)(1) screening of commonly‑owned 102(e)/(g) art applies; (iii) KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007), Graham v. John Deere Co., 383 U.S. 1 (1966), and MPEP 2143 govern the motivation‑to‑combine and predictability analysis; (iv) no post‑AIA "additional elements" savings clause is available to the patentee.

The strongest structural lever for a challenger is priority: if any claim limitation (e.g., the remote/networked Notary or the registry create/update step) is not supported by the 2006‑05‑05 provisionals, the effective date slides to 2007‑05‑05 or 2007‑03‑13, opening a one‑year window of intervening art. I could not verify provisional support from the supplied text; this requires the provisional specs.

POSITA (2006): a bachelor's degree in EE/CS/comp‑eng plus ~2–4 years in secure credentialing, smart cards, or biometric authentication; or equivalent. I state this as my construction, not as something in the record.

C. The subject matter at issue (as disclosed, not as claimed)

From the Abstract and Summary, the patent's asserted contribution is a trusted provisioning ("initialization") and enrollment ("registration") workflow for a portable credential, comprising:

D. Prior art available on the provided page

D1 — Applicant's admitted art (§ 102(b)-quality admissions). The Background concedes as known: magnetic credit/debit/ATM cards and employee badges; contactless cards/tokens placed near compatible readers; PIN/password augmentation of account numbers; and third‑party biometric "enrollment" in a database compared against a point‑of‑transaction biometric capture, which the applicant expressly criticizes as "time‑consuming, risky, error‑prone and considered intrusive." These admissions alone supply: the credential, the reader, the biometric match, and the enrollment-then-verify architecture.

D2 — Co‑pending Proxense applications (Ser. Nos. 11/292,330; 11/620,581; 11/620,577) — cited by the patent itself as describing PDKs and receiver‑decoder circuits. Because they are commonly owned, they are poor § 103 art (pre‑AIA § 103(c)); I flag them as the only "citations" actually on the page, and note they cannot do the work a challenger needs.

D3 — Reference surfaced by search but unverified as to this patent: US 7,275,160 B2, "Trusted system" (Koninklijke Philips). My search returned US8412949B2 appearing in a table on the US7,275,160 page. I could not verify whether '160 is cited by the '949 patent or merely cites it, so I do not rely on it. If '160 is in the '949 file wrapper as art of record, it is a strong candidate for the "trusted module validates a device before it may participate" teaching (element E2/E3 analogue).

D4 — Art from the actual § 103 contests over this family (contextual, not page-sourced). Search results show the Proxense family has been litigated and reviewed extensively, including IPR2024‑00232/‑00233 and IPR2024‑00846 (Microsoft v. Proxense), IPR2024‑00573 (Microsoft, U.S. 8,646,042), and Apple‑initiated IPRs, plus ex parte reexamination 90/015,052 on U.S. 8,352,730. Named references appearing in that record include Ludtke (applied and later withdrawn in the '052 reexam) and Maillard / Davis / Lundkvist / Schneier (asserted against the unrelated U.S. 10,298,564 family). Reported URL: https://ipfray.com/wp-content/uploads/2026/04/26-04-03-Proxense-v.-Apple-Microsoft-appellate-opening-brief-1.pdf. I flag plainly: I could not confirm which of these references was asserted against the '949 patent specifically, and I will not attribute a disclosure to a reference I have not read.

D5 — Highly probative development. Per Bloomberg Law (item dated Sept. 21, 2026; note this post-dates the stated current date of April 26, 2026 — I reproduce the search result as found rather than reconciling the dates), the PTAB held claims of a Proxense "hybrid device" patent unpatentable as obvious over combinations disclosing "a PDK that stores biometric profiles in a tamper‑proof memory that is acquired in a secure trusted process…" (https://news.bloomberglaw.com/ip-law/case-patents-obviousness-p-t-a-b-816). That finding, if it stands, is essentially the F5/E4/E5 core of the '949 disclosure found to be obvious — strong evidence that the '949's remaining novelty, if any, is concentrated in the Notary audit architecture (E1, E3, E6), not the PDK itself.

E. Combinations that would render the claims obvious

Ground 1 — Admitted enrollment art + trusted-issuer credential provisioning (Broadest)

Combination: D1 (admitted database enrollment + biometric match at point of transaction) + admitted contactless/smart‑credential architecture + conventional smart‑card personalization / issuing-terminal practice.
Rationale: The applicant's own Background frames the problem — biometrics in a central database expose users and impair enrollment. It is a predictable, two‑reference substitution to move the biometric template onto the credential and have the reader compare a live capture to the on‑card template (E4/E5), while keeping the reader/terminal that already exists in the admitted contactless art. KSR supports this: the improvement is "the mere substitution of one known element for another … to obtain the predictable result" of removing centralized biometric storage.
Weakness: Does not by itself reach the dual‑PDK Notary witness (E1/E3) or the triple‑written audit history (E6). Those need Grounds 3–4.

Ground 2 — PKI/registration-authority provisioning → "Notary"

Combination: D1 + conventional Registration Authority / Certification Authority provisioning of a cryptographic device (identity proofing of the applicant by an RA before a credential is issued to that identity).
Rationale: A POSITA in 2006 would readily map "the Programmer validates the user's identity and the Notary's authority before writing a binding profile" onto the routine RA/CA split (a verifier with delegated authority whose credential the issuing device must validate). The motivation is explicit in the reference domain: a credential is only as trustworthy as the identity proofing that preceded issuance — precisely the "trust, credibility and confidence" problem the specification identifies. E2/E3 are met by an RA validating its own authority (e.g., a CA‑issued RA certificate) and the applicant's standing; E1's "read the Notary PDK" is met by presenting the RA's credential to the issuing device.

Ground 3 — Database "good standing"/revocation checking + issuance-terminal journalling (reaches E2, E6)

Combination: Ground 2 + conventional credit‑card authorization/validation database and revocation‑list / blacklist practice (both expressly admitted and both already invoked by the '949 itself in FIGS. 7D and 11) + conventional terminal journaling (issuer ID, terminal ID, site ID, timestamp retained at the terminal and on the card, as in card personalization logs and ATM journals).
Rationale: E2's registry "good standing" check is the admitted validation‑database function applied at issuance rather than at transaction. E6's history record is the admitted transaction‑journal concept. Motivation: auditability and fraud investigation, the very justification the specification gives ("recalled in the future for auditing purposes"), is a known problem with a known solution, and the combination is a mere rearrangement of prior art elements — the strongest KSR posture.

Ground 4 — Offline credential issuance with deferred batch upload (reaches E8)

Combination: Grounds 1–3 + conventional store‑and‑forward batch settlement practice for POS terminals.
Rationale: Offline capture with later synchronization is the canonical solution to intermittent connectivity; the specification's own claim of benefit ("alleviates the need for a continuous connection") is the standard justification. This is a design choice among a finite set of known options with predictable results.

Ground 5 — Obviousness-type double patenting (non‑§ 103, but practically the same kill)

The search record shows the PTAB/CRU treating claims of U.S. 8,352,730 and U.S. 8,886,954 as "not patentably distinct" despite not being identical (IPR2024‑00846, Ex. 2017). Because '949 is the parent of US 8,838,993 → 9,251,326 → 10,374,795 → 10,764,044 → 11,182,792 → 12,014,369 → 12,597,030, the same non‑patentable‑distinctness theory is available against any '949 claim that does not recite the initialization/registration workflow narrowly. This is often the cheaper attack.

F. Where the § 103 case is weakest (and the patentee's best rebuttal)

A rigorous analysis must state the counter‑case:

1. The dual‑credential Notary architecture (E1 + E3) is the least obviously conventional element. A challenger must show art or a reason why the user's credential and the witness's credential are both presented to, and independently validated by, the same programming device, with initialization barred unless both clear. Grounds 1–2 assume this mapping; they do not prove it. Absent a reference teaching a second authoritative credential validated at the point of programming, the patentee argues non‑obvious arrangement of known parts.
2. The Notary PDK as a distributed, recallable audit ledger (E6, writing initialization history to the Notary's own device so all initializations can be recovered if the Notary's rights are revoked). That specific reciprocal‑audit mechanism has a colorable non‑obviousness argument grounded in the patent's stated purpose.
3. The "no biometric data retained anywhere but the user's PDK" invariant, enforced at initialization (E5), is a genuine architectural constraint that the admitted third‑party enrollment art teaches away from — the admitted art's entire model is database storage.
4. Secondary considerations the patentee can assert: industry adoption of the PDK/reader model, the Proxense licensing program, and the family's extensive litigation (Darts‑IP family‑litigation flag on the page) as evidence of commercial significance. Counter: the search record shows the reexamination CRU repeatedly rejected, on the merits, the same art and grounds the PTAB later accepted (per the Proxense appellate brief at ipfray.com), which both proves the questions are close and weakens any "settled expectations" narrative.
5. Priority-date exposure cuts the other way if unproven: if claim limitations lack 2006‑05‑05 provisional support, a § 112 written‑description/priority attack pairs with § 103 to pull in 2006–2007 art.

G. Bottom line

• Most likely to succeed: a three‑reference combination of (i) the applicant's admitted database‑enrollment prior art, (ii) a trusted smart‑credential personalization/issuing terminal with registry good‑standing checks and journaling, and (iii) offline batch‑upload practice — with an RA/CA‑style reference supplying the "Notary" authority element. Under KSR this is a predictable substitution plus a rearrangement of known elements solving expressly recognized problems, i.e., obvious under pre‑AIA § 103(a).
• The trench warfare will be over E1/E3/E6 — the dual‑PDK witnessed initialization and the Notary‑side audit ledger. If the claims recite those with specificity and the provisionals support them, they survive; if the claims are written at the disclosed behavioral level ("validate the notary," "write history data"), a reference teaching any second authoritative credential plus logging anticipates or renders them obvious.
• Highest‑value next step (and biggest gap in my analysis): obtain the issued claims and the file wrapper. Because the supplied page truncates before the claims and contains no examiner citation list, I could not chart claim limitations or verify which references are of record. I am not asserting that any of Ludtke, Maillard, Davis, Lundkvist, Schneier, or US 7,275,160 was applied against the '949 patent — my searches tied those to sibling patents, and search results would control over my recollection if they conflicted.

Confidence: high on the legal framework, the admitted‑art admissions, and the general combination logic; low‑to‑moderate on limitation‑by‑limitation mapping, because the claim text was not in the provided record.