US 8352730

I'll search for authoritative information on this patent number and check for any 2026 CAFC docket activity.

Let me verify the PTAB outcomes for the two IPRs specifically naming 8352730 and check specifically for a 2026 CAFC docket naming this patent.

US Patent 8,352,730 — Summary (searched: Google Patents/PatentsView full text, Unified Patents PTAB portal, Docket Alarm PTAB, Stanford NPE database, ip fray Federal Circuit coverage)

Important caveat up front: I did not find any Court of Appeals for the Federal Circuit docket that names U.S. Patent No. 8,352,730 as the patent on appeal. The 2026 Federal Circuit activity in this family involves the continuation patent 8,886,954 (details in §5 below). I also did not retrieve the USPTO PatentCenter record directly — the bibliographic data below is reconciled from the patent text at patents.google.com/patent/US8352730B2, the granted-PDF front page (patentimages host), and third-party mirrors (SumoBrain, Unified Patents portal, RPX Insight), which agree with each other.

---

1. Bibliographic data

Small discrepancies I will not auto-correct, just flag: the Unified Patents portal lists the priority date as 2004‑12‑19, the application date as 2005‑12‑19, the grant date as 2013‑01‑07, and expiration 2028‑07‑14 — one day earlier than the Google Patents/PDF values in each case. The authoritative granted PDF front page says Filed Dec. 20, 2005, Patent No. date Jan. 8, 2013, and provisional priority Dec. 20, 2004 / Feb. 14, 2005.

2. Abstract (verbatim, granted text)

"Systems and methods are provided for an integrated device that persistently (or permanently) stores biometric data for a user in a tamper-resistant format. Subsequently, scan data collected from a user (e.g., a finger-print) can be compared against the biometric data. Once the user has been verified by the integrated device, a code can be wirelessly transmitted for authentication. The authentication module sends the code to a trusted key authority. The trusted key authority checks a list of enrolled integrated devices for a match. If there is a match, the authentication module sends a message to an application to allow access by the user. The trusted key authority also stores a profile associated with the code. The profile can contain user information such as name, age, account numbers, preferences, etc. and can also describe the status of the integrated device."

3. Plain-language overview of the four independent claims

Claim 1 — Method of verifying a user during authentication of an "integrated device" (the biometric key).
The claim puts three things together. (a) Storage: the key permanently holds the user's biometric data plus a set of codes and other data values — expressly including a device ID code uniquely identifying the key and a secret decryption value — in a write-once, tamper-proof form that cannot later be altered. The recited biometric types are limited to the group: palm print, retinal scan, iris scan, hand geometry, facial recognition, signature recognition, voice recognition (note: fingerprint is NOT in this list — it appears only in dependent claim 5). (b) Local biometric check: on a request for biometric verification, the key takes scan data and compares it to the stored biometric data. (c) Wireless relay and third-party authentication: if the scan matches, the key wirelessly sends one or more of those codes/data values (including the device ID) for authentication by an "agent" — defined as a third-party trusted authority holding a list of legitimate device ID codes — and, once that agent authenticates, the key/user receives an access message from the agent permitting access to an application drawn from the recited group: casino machine, keyless lock, garage door opener, ATM machine, hard drive, computer software, web site, file.

Claim 8 — Apparatus ("integrated device") version of claim 1. A memory that stores the same package (biometric data + the plurality of codes/other data values including device ID code and secret decryption value) in unalterable tamper-proof form, again with the same closed list of biometric types; a verification unit that receives scan data, compares it, and on a match wirelessly sends the code(s) to the third-party trusted-authority agent; and a radio frequency communicator that, on the agent's authentication, receives the access message allowing access to the recited application group. Dependent claim 11 adds an LED activated to request the biometric scan.

Claim 12 — Method of authenticating an already-verified user (the receiving/verifier side), executed by a computer processor. Receive one or more codes/data values including a device ID code uniquely identifying the integrated device and a secret decryption value, associated with a biometrically verified user, where the device ID code is registered with the third-party trusted-authority agent that holds the list of legitimate device IDs; request authentication of the code(s) from that agent (the authentication asks whether the code(s) are legitimate); receive an access message from the agent; and, on a positive message, allow the biometrically verified user access to the recited application group. This is the "authentication module / gatekeeper" claim.

Claim 15 — System claim. A biometric key that stores the same package (biometric data + codes/other data values including device ID code and secret decryption value) in unalterable tamper-proof form, wirelessly sends the code(s) when scan data is verified against the stored biometric data, with the same closed biometric-type list; plus an authentication unit that receives those codes/data values, forwards them to the third-party trusted-authority agent for authentication, and, on authentication, receives an access message allowing the user to reach the recited application group. Dependent claims 16–17 add that the key may receive an authentication request from the authentication unit and, in response, prompt for a biometric scan; and that if the key cannot verify the scan, it does not send the code(s).

Dependent claims 2–7, 9–11, 13–14, 16–17 add: transmission over a network; registering age verification against the device ID code; codes indicating the biometric verification succeeded; fingerprint-based biometric data (claim 5); establishing a secure communication channel before sending; the "code-only, no biometric prompt" mode (claim 7 — send the code without requesting scan data when the request does not ask for biometric verification); the LED (claim 11); registering date of birth/age with the agent (claim 13); secure channel with the biometric key (claim 14).

4. Post-grant / litigation posture (as found)

• PTAB — IPR2024-01326, [Microsoft Corp.](/litigations/by-plaintiff/Microsoft%20Corp.) v. Proxense, LLC (filed Aug. 20, 2024; judges McKone, Turner, Beamer, Dang). Patent at issue: 8,352,730. Institution DENIED (Paper 8, Nov. 20, 2024, under 35 U.S.C. §314); petitioner's conditional motion for joinder and post-institution fee refund followed (Dec. 2024). Google Patents records this as "Not Instituted – Procedural." Source: Docket Alarm PTAB docket IPR2024-01326.
• PTAB — IPR2024-01486, Apple Inc. v. Proxense, LLC (filed Oct. 16, 2024). Patent at issue: 8,352,730. Google Patents records this as "Not Instituted – Procedural." Apple's petition (as mirrored on ex-parte.com) asserted obviousness over Burger (US 2005/0050367) alone for claims 1‑2, 4‑9, 11‑12, 14‑17, and Burger + Robinson (US 2003/0177102) for claims 3, 10, 13 (the age-verification claims). Because the record I retrieved is a petition/mirror, treat the ultimate disposition as "not instituted" with moderate confidence.
• District court actions naming '730 (all asserted by Proxense, W.D. Tex.): 6:21‑cv‑00210 v. Samsung Electronics (filed Mar. 5, 2021; consent judgment / stipulated dismissal with prejudice under FRCP 41(a)(1)(ii), Jan. 19, 2023, each side bearing its own costs — no merits ruling); 6:23‑cv‑00319 v. Microsoft; 6:23‑cv‑00320 v. Google LLC/Google Payment; 6:24‑cv‑00143 v. Apple; 6:24‑cv‑00283 v. Intel; 6:24‑cv‑00302 v. LG Electronics. Google, Intel, and (per reporting) others have since settled; Apple and Microsoft litigation remains stayed.
• Ex parte reexamination 90/015,052 ("the 052 EPR") on the '730 parent patent was pending before the Central Reexamination Unit. Per Proxense's 2026 appellate brief, the examiner there proposed an amendment clarifying that an "access message" be received by an application, which would have overcome the art; the PTAB then stayed the '052 EPR and later treated the examiner's withdrawal of the Ludtke-based rejection as "moot." This is the crux of the current appeal.

5. CAFC 2026 dockets — what I could and could not confirm

• No 2026 CAFC docket naming 8,352,730 was found. I searched for it specifically and did not locate one. Do not attribute the pending appeal to the '730 patent.
• The relevant 2026 appeal is Proxense, LLC v. Apple Inc. / Proxense, LLC v. Microsoft Corp., consolidated as Appeal No. 2025‑2130 (lead) with 2025‑2131 (member) (dockets.justia.com lists 25‑2131, filed Sept. 22, 2025; consolidation order Oct. 7, 2025; certified list Nov. 4, 2025). That appeal arises from the final written decisions in IPR2024‑00232 and IPR2024‑00846, which found claims of U.S. Patent No. 8,886,954 ("Biometric personal data key (PDK) authentication") unpatentable. Proxense filed its opening brief on/about April 3, 2026 (brief PDF hosted at ipfray.com, filename 26-04-03-Proxense-v.-Apple-Microsoft-appellate-opening-brief), arguing the PTAB violated the APA by staying the parallel ex parte reexamination (the '730 patent's 90/015,052 EPR) just as it was about to affirm patentability, and contesting the Board's construction of "a third party that operates a trusted authority."
• So the '730 patent appears in that appeal as the parent patent whose reexamination was stayed, not as the patent on appeal.

6. Family (for context on the "PDK" lineage)

Continuations claiming priority to 11/314,199 include US 8,886,954 B1, US 9,298,905 B1, US 10,437,976 B2, US 10,698,989 B2, and application US 2019/0384903 A1 (abandoned). Foreign family: EP 1829283 A2, AU 2005319019 A1, CA 2591751 A1, RU 2007127725 A, WO 2006069330 A2.

7. Explicit uncertainties

• I could not open the USPTO PatentCenter or PACER records directly; the IPR institution/denial outcomes for IPR2024‑01326 and IPR2024‑01486 come from secondary dockets (Docket Alarm, Google Patents family metadata, ex‑parte mirrors), so verify against PTAB's own docket before relying on them.
• The one-day date discrepancies noted in §1 (priority, filing, grant, expiration) are unresolved between sources; I have reported both rather than choosing.
• I found no reported claim construction or infringement/validity merits ruling on '730; Google's opening claim‑construction brief in 6:23‑cv‑00320 argued "integrated device" and "plurality of codes and other data values" were indefinite, but I did not confirm the court's ruling.

I'll research litigation involving US patent 8352730. Let me start with the sources you specified and the litigation data already embedded in the patent record.

Good — I have a strong base. Let me dig into the outcomes/status of each case and the PTAB proceedings.

Litigation involving U.S. Patent No. 8,352,730

Bottom line up front: Yes — US 8,352,730 ("Biometric personal data key (PDK) authentication," Proxense LLC) is heavily litigated. It has been asserted by Proxense, LLC in at least six U.S. district court actions, all in the Western District of Texas (Judge Alan D. Albright), and it has been the subject of six AIA post-grant proceedings (IPRs) plus an ex parte reexamination. Critically, all claims 1–17 of the '730 patent were cancelled by PTAB adverse judgment on April 28, 2025, although the reexamination unit later upheld amended claims — a conflict that is still playing out.

Note on scope: I have limited this to matters where US 8,352,730 specifically appears as an asserted patent (or challenged patent). Proxense has filed other suits over sibling patents (e.g., Hyundai/Kia/Genesis, Jan. 2025) that I have not confirmed involve the '730 patent, so I exclude them below.

---

1. District Court Litigation

The '730 patent was asserted in these six actions (per the patent's own litigation record at patents.google.com/patent/US8352730/en, and IPFray/RPX reporting):

Key details:

• Samsung (No. 1) — The parties filed a joint stipulation/consent judgment in January 2023, days before jury trial; financial terms undisclosed. No court ruled on validity or infringement. Sources: Hecht Partners announcement; PatSnap case summary; Korean press (theguru.co.kr). Samsung's own IPRs against Proxense's patents were thereby mooted.
• Google (No. 3) — Stipulated dismissal with prejudice of all infringement claims (defendant's claims/defenses dismissed without prejudice), each side bearing its own costs. IPFray concluded Google "has taken a license."
• Microsoft (No. 2) — Most active. After the PTAB's April 28, 2025 adverse judgments cancelled all '730 claims, Microsoft filed an Opposed Motion to Dismiss the '730 Patent with Prejudice (Dkt. 95, May 9, 2025), arguing the court lacks subject-matter jurisdiction under Rule 12(b)(1). Proxense responded, filed an amended complaint on May 6, 2025 that still asserted '730, and opposed the motion. Resolution of that motion is not captured in the sources I retrieved — treat the '730 dismissal as unresolved/uncertain.

---

2. PTAB Post-Grant Proceedings (all on the '730 patent)

The combined adverse judgments in IPR2024-00775 and IPR2024-00232 (Apr. 28, 2025) resulted in cancellation of all claims 1–17 of the '730 patent. The PTAB also imposed estoppel under 37 C.F.R. § 42.73(d)(3). (Source: PTAB orders quoted in Proxense, LLC v. Microsoft Corp., 6:23-cv-00319, Dkt. 95 and Dkt. 105, and IPFray's summary table.)

---

3. Ex Parte Reexamination

• In re Proxense, LLC / In re Giobbi, Ex Parte Reexamination Control No. 90/015,052, filed June 8, 2022 (third-party requester; requester's counsel Quinn Emanuel, per the Jan. 3, 2024 Decision on Petition). Art unit 3992.
• The PTAB stayed the reexam on March 27, 2025 pending IPR2024-00232, noting Proxense failed to identify the reexam as a related matter and failed to update its mandatory notices.
• After the April 2025 adverse judgments, the PTAB lifted the stay and recommended the examiner consider § 42.73(d)(3) estoppel.
• Per IPFray, the USPTO's Central Reexamination Unit ultimately upheld the '730 patent, finding the amended claims patentable (the amended claims add limitations requiring the user to "complete a transaction" and requiring the "principal parties to the transaction [to] be the user and the application"). This is in tension with the PTAB's cancellation of the original claims 1–17.

(I could not independently confirm the precise date of the CRU decision; treat the "upheld" outcome as reported by IPFray, not as a primary document I retrieved.)

---

4. Appellate Activity

• Federal Circuit — A favorable venue/transfer-related decision for Proxense against Microsoft was reported around April 27, 2024 (IPFray). Google also sought mandamus review of Judge Albright's denial of its transfer motion to N.D. Cal.; the transfer denial was upheld (Biometric Update, Mar. 2024).
• The Microsoft IPR (Law360 docket) is noted as "Final Written Decision – Appealed," so at least one PTAB outcome has been taken up on appeal.
• Proxense reportedly sought Director Review in a parallel matter concerning U.S. Patent No. 8,886,954 ('954), arguing an APA violation — a sibling-patent dispute, not '730 itself.

---

5. Caveats on completeness

• I could not retrieve detailed docket-level status for the Apple (6:24-cv-00143), Intel (6:24-cv-00283), and LG (6:24-cv-00302) actions beyond their filing data and patent lists; reporting as of mid-2025 described them as pending.
• The '730 patent's own Google Patents record flags PTAB cases IPR2024-01326, IPR2024-01486 ("Not Instituted – Procedural"), IPR2024-00775, IPR2024-01333, IPR2024-00232 ("Adverse Judgment"), and IPR2021-01444 ("Not Instituted – Merits") — consistent with the table above.
• Several IPR numbers referenced in the Proxense campaign (e.g., IPR2024-00776, -00783, -01320, -00573, -00407, -00233, -00234) relate to other Proxense patents ('905, '289, '960, '042) and are therefore out of scope for the '730 question.
• Any statement of "current status" is as of the sources retrieved; dockets in the active Microsoft, Apple, Intel, and LG cases may have moved since.

Primary sources cited: patents.google.com/patent/US8352730/en (embedded litigation record); portal.unifiedpatents.com/patents/patent/8352730; CourtListener dockets 67312721 (Microsoft, 6:23-cv-00319) and 95/105; IPFray.com (Google-Samsung settlement and "USPTO upholds core Proxense patent" articles); Law360 (case pages); RPX Insight; Hecht Partners LLP; PatSnap case summary; Justia dockets (6:21-cv-00210); Docket Alarm (IPR2024-01326/01486 and PTAB filings).

I'll reconcile the structured "no PTAB activity on file" block against the proceedings named in the family litigation metadata, then verify each case on public dockets.

Critical development found — I need to verify the April 2025 adverse judgments and reconcile them with the prior section's claim that the '730 patent had only two IPRs.

PTAB / AIA Trial Proceedings — U.S. Patent No. 8,352,730

⚠️ Contradiction flag (read first). The structured "PTAB proceedings on file" block supplied with this task states that the USPTO Open Data Portal returns no AIA trial proceedings for this patent. That block is wrong or stale, and it is contradicted both by the patent's own Google Patents family metadata (which lists six PTAB cases in this family) and by a dozen primary PTAB documents and district-court filings I retrieved. There were six AIA trial proceedings naming 8,352,730, and the patent's original claims were cancelled in their entirety on 2025-04-28. Do not rely on the ODP "zero proceedings" result for this patent. I was not able to query the ODP API directly, so I cannot say whether the endpoint is broken, whether the patent number was mis-keyed, or whether the block's ingest was simply pre-2024.

---

Proceedings overview

Six AIA trials name 8,352,730 — three terminated by adverse judgment cancelling claims, three denied institution; zero claims survived. Two independent claims-invalidated proceedings (IPR2024-00775, which cancelled claims 1–17, and IPR2024-00232, which cancelled claims 1–6 and 8–17; IPR2024-01333 was joined into the latter), plus three institution denials (IPR2024-01326, IPR2024-01486, IPR2021-01444). Bottom line for a defendant today: the asserted patent is a legal nullity as issued — every original claim 1–17 has been cancelled — so any demand letter or complaint citing claims 1, 2, 5, 6, 8, 15, 16 or 17 is bottomless. The only live exposure is the amended claims (18–34) that issued from the parallel ex parte reexamination 90/015,052, and those are a separate, contested, and newly-appealed story (§ Strategic summary).

---

IPR2024-00775 — Microsoft Corporation v. Proxense, LLC

• Type: Inter Partes Review
• Filed: 2024-04-19
• Status: Terminated – Adverse Judgment (structured docket status). Plain English: patent owner conceded and the Board cancelled every claim of the patent.
• Judge panel: Thu A. Dang, Kevin F. Turner, David C. McKone (joint scheduling order in IPR2024-00775/00846, McKone writing); third-party dockets list Justin T. Arbes as the judge writing the final decision. Treat the Arbes attribution as secondary-source.
• Petition grounds: Claims 1–17 challenged under pre-AIA 35 U.S.C. § 103(a): Ground 1 — Burger (US 2005/0050367 A1) for claims 1, 2, 4–9, 11, 12, 14–17; Ground 2 — Burger + Robinson (US 2003/0177102 A1) for dependent claims 3, 10, 13. Petitioner's expert: Stephen Gray (Ex. 1003).
• Institution decision: Instituted 2024-11-18 as to all challenged claims 1–17. (Institution date corroborated by the joint scheduling order entered 2024-11-18 in IPR2024-00775/00846.)
• Final Written Decision: No merits FWD was ever written. Instead, on 2025-04-28 the Board ordered that "adverse judgment is hereby entered against Patent Owner pursuant to 37 C.F.R. § 42.73(b) with respect to claims 1-17 of U.S. Patent No. 8,352,730 B2" and that "claims 1-17 of U.S. Patent No. 8,352,730 B2 are cancelled." The order expressly states it "constitutes a Final Written Decision under 35 U.S.C. § 318(a)" and imposes 37 C.F.R. § 42.73(d)(3) administrative estoppel: "Patent Owner shall not take any action inconsistent with this adverse judgment, including obtaining in any patent a claim that is not patentably distinct from the cancelled claims in this proceeding." Verdict at claim level: claims 1–17 cancelled; nothing sustained.
• Settlement / termination: Not a settlement. Proxense itself requested adverse judgment on 2025-04-15 — "based on the concessions of unpatentability made when Patent Owner authorized entry of the Examiner's amendment in EPR 90/05,052" — under 37 C.F.R. § 42.73(b)(3). This was a strategic move to un-stay the parallel reexamination.
• Appeal: None. No Federal Circuit docket naming the '730 patent was found. As a practical matter, a party that requests adverse judgment forfeits appellate review.
• Defensive value: Dispositive. Claim 1 was cancelled here, along with every other claim. This is the FWD the prior section's account missed, and it is the single most important document about this patent. If opposing counsel asserts the '730 patent against you, cite this order and the Microsoft motion at Dkt. 95 in Proxense v. Microsoft, 6:23-cv-00319 (W.D. Tex.): https://storage.courtlistener.com/recap/gov.uscourts.txwd.[1217252](/patent/1217252)/gov.uscourts.txwd.1217252.95.0.pdf

---

IPR2024-00232 — Google LLC v. Proxense, LLC (Apple Inc. joined via IPR2024-01333)

• Type: Inter Partes Review
• Filed: 2024-01-17 (Google petition; date stated in Apple's 2024-10-16 supplemental paper)
• Status: Terminated – Adverse Judgment (Google Patents family metadata labels this one "Adverse Judgment"). Claims 1–6 and 8–17 cancelled.
• Judge panel: Thu A. Dang, Kevin F. Turner, David C. McKone.
• Petition grounds: Claims 1–6 and 8–17 (note: claim 7 was not challenged in this proceeding), pre-AIA 35 U.S.C. § 103(a): Ground 1 — Ludtke (US 7,188,110 B1) for claims 1, 2, 4–6, 8, 9, 11, 12, 14–17; Ground 2 — Ludtke + Kon (US 2002/0046336 A1) for claims 3, 10, 13. Expert: Stephen Gray.
• Institution decision: Instituted 2024-07-24 (Google DI, Paper 10) as to claims 1–6 and 8–17 on both grounds. The Board preliminarily construed "third-party trusted authority" as "a trusted authority that is an entity separate from the parties to a transaction" — a construction that reappears throughout the family.
• Final Written Decision: No merits FWD. On 2025-04-28 the Board ordered adverse judgment under § 42.73(b) as to "claims 1-6 and 8-17 of U.S. Patent No. 8,352,730 B2" and held those claims cancelled. In the same order the Board lifted the stay of Reexamination Control No. 90/015,052 and recommended that the examiner consider whether § 42.73(d)(3)(i) estoppel should preclude inconsistent action. (Proxense had requested adverse judgment here on 2025-04-15 as well.) Oral argument had been scheduled for 2025-04-22.
• Settlement / termination: Adverse judgment at patent owner's request, not settlement.
• Appeal: None naming the '730 patent.
• Defensive value: Together with IPR2024-00775 this completes the kill — claim 7 is covered by IPR2024-00775, and claims 1–6 and 8–17 by this proceeding. There is no surviving original claim.

---

IPR2024-01333 — Apple Inc. v. Proxense, LLC

• Type: Inter Partes Review (joinder petition under 35 U.S.C. § 315(c))
• Filed: 2024-08-22
• Status: Terminated – Adverse Judgment (joined proceeding; terminated with the Google IPR on 2025-04-28).
• Judge panel: Thu A. Dang, Kevin F. Turner, David C. McKone (Paper 8, 2024-10-08); Docket Alarm metadata also lists Norman Beamer.
• Petition grounds: Claims 1–6 and 8–17 — expressly "substantively identical grounds of rejection, including the same art combinations against the same claims" as the Google petition: Ludtke (§ 103(a)) for claims 1, 2, 4–6, 8, 9, 11, 12, 14–17; Ludtke + Kon (§ 103(a)) for claims 3, 10, 13. Apple also challenged claim 7 in its separate IPR2024-01486 petition.
• Institution decision: Instituted and joined 2024-10-08 (Paper 8). Patent Owner did not oppose joinder; Apple accepted an "understudy" role and agreed not to raise new grounds. Order: "Apple Inc. is hereby joined with Google LLC as a petitioner entity in IPR2024-00232"; all further filings to be made in IPR2024-00232. Apple also filed a preliminary-infringement-based Sotera-style stipulation and, separately, Microsoft filed a Sotera stipulation on 2024-08-20 in connection with its own petitions.
• Final Written Decision: None independent — the joined proceeding terminated by the 2025-04-28 adverse judgment cancelling claims 1–6 and 8–17.
• Settlement / termination: N/A (joined; adverse judgment).
• Appeal: None naming the '730 patent.
• Defensive value: Creates Apple-specific § 315(e) estoppel and confirms that all three of Google, Apple and Microsoft had '730 IPR grounds on file. Because Apple was a joined petitioner on identical grounds, Apple cannot now relitigate those grounds or grounds it reasonably could have raised.

---

IPR2024-01326 — Microsoft Corporation v. Proxense, LLC

• Type: Inter Partes Review
• Filed: 2024-08-20 (with a conditional motion for joinder to Microsoft's earlier IPR2024-00775 filed the same day)
• Status: Institution Denied (Paper 8, 2024-11-20, decision denying institution under 35 U.S.C. § 314). Petitioner's refund request was approved by Board notice dated 2024-12-10.
• Judge panel: David McKone, Kevin Turner, Thu Dang, Norman Beamer.
• Petition grounds: Claims 1–6 and 8–17, pre-AIA § 103(a): Ground 1 — Ludtke for claims 1, 2, 4–6, 8, 9, 11, 12, 14–17; Ground 2 — Ludtke + Kon for claims 3, 10, 13. Microsoft filed a Sotera stipulation on 2024-08-20 (Ex. 1024): if instituted, it would not pursue in district court any ground raised or that could reasonably have been raised against all '730 claims.
• Institution decision: Denied 2024-11-20. I did not retrieve the body of Paper 8, so I cannot quote the panel's reasoning verbatim; the denial is best explained by the fact that this petition was substantially a duplicate of Microsoft's own earlier IPR2024-00775 (already instituted 2024-11-18) and of the Google/Apple Ludtke filings. Flagged as low-confidence as to reasoning.
• Final Written Decision: None.
• Settlement / termination: Procedural termination on denial, with fee refund.
• Appeal: None.
• Defensive value: Superseded — even though this petition was denied, the same petitioner's earlier IPR2024-00775 did the work and cancelled everything. E.g., IPR2024-01326 docket: https://gaeflexstaging-dot-docketupdate.appspot.com/cases/PTAB/IPR2024-01326/Microsoft_Corporation_v._Proxense_LLC/

---

IPR2024-01486 — Apple Inc. v. Proxense, LLC

• Type: Inter Partes Review (joinder petition — Apple sought to join Microsoft's IPR2024-00775)
• Filed: 2024-10-16
• Status: Reported as "Not Instituted – Procedural" in Google Patents family metadata. Treat with moderate confidence — I did not retrieve an institution/denial paper, and by the time a § 314 decision was due the joinder target (IPR2024-00775) had already terminated by adverse judgment on 2025-04-28, which would moot the joinder request.
• Judge panel: Not confirmed in the sources retrieved.
• Petition grounds: Claims 1–2, 4–9, 11–12, 14–17 — Ground 1, Burger; claims 3, 10, 13 — Ground 2, Burger + Robinson (all pre-AIA § 103). Apple characterized this petition as substantively identical to the Microsoft petition (i.e., the Burger line of art, not the Ludtke line), and ranked it second behind IPR2024-01333 in its 2024-10-16 notice ranking petitions. Claim 7 was challenged here and not in the 1333/Google line.
• Institution decision: No institution found.
• Final Written Decision: None.
• Settlement / termination: Procedural (no institution). Petition mirrored at ex-parte: https://ai-lab.exparte.com/case/ptab/IPR2024-01486/doc/1006
• Appeal: None.
• Defensive value: Marginal on its own, but it is useful evidence that Apple had a second, independent Burger-based theory on file and chose to rank it second — relevant to what Apple "reasonably could have raised" under § 315(e)(2).

---

IPR2021-01444 — [[Samsung Electronics America](/litigations/by-defendant/Samsung%20Electronics%20America), Inc.](/litigations/by-plaintiff/Samsung%20Electronics%20America%2C%20Inc.) v. Proxense, LLC

• Type: Inter Partes Review
• Filed: 2021-08-26
• Status: Institution Denied (Paper 11, 2022-02-28, § 314). Terminated 2022-02-28; refund approved 2022-10-31.
• Judge panel: David McKone, Justin Arbes, Kevin Turner, Thu Dang (Arbes writing).
• Petition grounds: Petition challenged claims 1–11 (third-party docket data), pre-AIA § 103. Exhibit set shows a multi-reference attack: Scott (Ex. 1005), Russell (Ex. 1006), Lapsley (Ex. 1007), Robinson (Ex. 1008), Rhoads, Berardi, Rosen, Shreve, Kinoshita, Schneier, with the Declaration of Andrew Wolfe, Ph.D. (Ex. 1003). The Board's decision included a section captioned "Obviousness Ground Based on Scott, Russell, and Lapsley," contending claims 1, 2, 4–9 and 11 were unpatentable.
• Institution decision: Denied 2022-02-28. Reasoning (quoted in the later IPR2024-01326 exhibit set): the Board adopted Patent Owner's position and interpreted "third-party trusted authority" to mean "a trusted authority that is an entity separate from the parties to a transaction" — "The plain meaning of 'third-party trusted authority' suggests an entity or party separate from the principal parties to a transaction" — and found the art deficient, including that "sending a code to a receiver of a door that the user is trying to access" does not satisfy the "third party" limitation. It also found no further construction of "access message" necessary because both claims recite the message is received "from" the agent.
• Final Written Decision: None.
• Settlement / termination: N/A (denial). Samsung's parallel family filings (e.g., IPR2021-01447 on the '905 patent) were likewise denied on 2022-02-28; the underlying W.D. Tex. case 6:21-cv-00210 settled by consent judgment / stipulated dismissal with prejudice on 2023-01-19.
• Appeal: None.
• Defensive value: This is the only proceeding in which Proxense's claim-construction position prevailed — and it mattered, because the Board's "third party = a separate entity" construction became the linchpin the later petitioners (Ludtke, then Burger) used to win. It is also a reminder for a defendant today that Proxense's district-court constructions ("access message," "device ID code") were adopted four times by Judge Albright's court. Docket: https://gaeflexstaging-dot-docketupdate.appspot.com/cases/PTAB/IPR2021-01444/SAMSUNG_ELECTRONICS_AMERICA_INC_v._Proxense_LLC/

---

Strategic summary

Which claims are cancelled vs. sustained vs. untested. All 17 issued claims of 8,352,730 are cancelled — claim-by-claim: claims 1–6 and 8–17 were cancelled in IPR2024-00232 (and in the joined IPR2024-01333) by the 2025-04-28 adverse judgment; claims 1–17 were separately cancelled in IPR2024-00775 by the same date. Claim 7 was cancelled via IPR2024-00775 (it was not challenged in the Google/Apple line). No claim was sustained; no claim is untested. Two points to state carefully: (i) these are adverse judgments, not merits FWDs — the Board never reached a merits determination, and the estoppel flows from 37 C.F.R. § 42.73(b) plus the orders' express § 318(a)/§ 42.73(d)(3) language, not from an obviousness holding; (ii) the cancellation triggered mootness of the district court claims — Microsoft moved on 2025-05-09 to dismiss the '730 claims with prejudice under Rule 12(b)(1), Proxense, LLC v. Microsoft Corp., No. 6:23-cv-00319-ADA (W.D. Tex.), Dkt. 95, citing Fresenius and Sanofi-Aventis.

The live risk is the reexamination, not the patent. The '730 patent was simultaneously in ex parte reexamination 90/015,052 (filed 2022-06-08), and that is where the remaining value sits. Per Proxense's own 2026 Federal Circuit opening brief, the '052 reexam terminated 2026-01-29 with issuance of an ex parte reexamination certificate cancelling claims 1–17 and issuing new claims 18–34. Earlier in that reexam the CRU had proposed an examiner's amendment and told Proxense that "the claims would be allowed if amended to recite: receiving an access message by an application from the agent …"; the PTAB stayed the reexam on 2025-03-27 pending IPR2024-00232, then lifted the stay on 2025-04-28. Two cautions: (a) the same examiner had earlier (2025-05-20 Office Action) rejected all amended claims as "not being patentably distinct" from the cancelled claims 1–17 and, on 2025-07-29, rejected pending claims 18–34 as anticipated by Burger — so the certificate's claims 18–34 are narrow, amendment-derived, and squarely on the firing line; (b) the "access message received by the application" limitation Proxense added is essentially the language of '954 patent claim 1, which the Board held unpatentable in IPR2024-00233 and IPR2024-00846.

Estoppel landscape. Under 35 U.S.C. § 315(e)(2), Google, Apple and Microsoft are estopped in the district court from asserting invalidity grounds they raised or reasonably could have raised in the instituted '730 IPRs — i.e., the Ludtke and Ludtke+Kon grounds (Google/Apple/Microsoft IPR2024-01326) and the Burger and Burger+Robinson grounds (Microsoft IPR2024-00775 / Apple IPR2024-01486). That estoppel is largely academic now that the claims are cancelled. For a new defendant facing the reexam-issued claims 18–34, the picture is more useful: (i) § 315(e)(2) estoppel does not run to a party that was not a petitioner or privy; (ii) the '730 IPRs never produced an FWD on the merits, so there is no issue-preclusive obviousness holding to invoke for or against you; and (iii) § 42.73(d)(3) administrative estoppel does bind the patent owner from obtaining or asserting claims not patentably distinct from cancelled claims 1–17 — the strongest available argument against claims 18–34. Independent art avenues untouched by these proceedings include the Ludtke family applied against the amended claim scope, plus Samsung's Scott/Russell/Lapsley line from IPR2021-01444, none of which was ever adjudicated on the merits.

Pattern signals. (1) Serial, coordinated third-party attack: petitioners were Google (IPR2024-00232), Microsoft (IPR2024-00775, IPR2024-01326), Apple (IPR2024-01333, IPR2024-01486) and Samsung (IPR2021-01444), all on W.D. Tex. defendants filing follow-on joinder petitions on identical grounds — classic "join the lead petition, take an understudy role" efficiency strategy. (2) The '730 patent is one of roughly fourteen sequential Proxense-family IPRs (the brief lists IPR2024-00232, -00233, -00234, -00775, -00776, -00846, -01326, -01327, -01328, -01333, -01334, -01335, -01846 and -01485), so this is an industry-wide, not a single-defendant, challenge. (3) No defensive aggregator (Unified Patents) petition was found for this patent — the "Unified Patents" strings in the Google Patents metadata are the data source attribution, not the petitioner. (4) The patent owner capitulated in the PTAB to buy a reexam outcome: Proxense requested adverse judgment in both '730 IPRs on 2025-04-15, conceding unpatentability, precisely so it could un-stay the reexam and pursue amended claims — an unusual and deliberately transactional posture. (5) Appeal posture: Proxense has appealed aggressively, but not this patent — the pending consolidated Federal Circuit appeal (Appeal Nos. 2025-2130 (lead) / 2025-2131 (member)) arises from the FWDs in IPR2024-00233 and IPR2024-00846, which are '954 patent proceedings (FWDs entered 2025-06-17 and 2025-10-17; notices of appeal at IPR2024-00233 Paper 39 and IPR2024-00846 Paper 33). The '730 patent appears in that appeal only as the parent patent whose reexamination was stayed (APA/appointments-clause issues over the PTAB's docket control).

Contradiction flag (second). The earlier generated section stated that the 2026 appeal rests on "IPR2024-00232 and IPR2024-00846." That is one digit off: Proxense's April 2026 opening brief identifies the appealed FWDs as IPR2024-00233 and IPR2024-00846 ('954 patent). IPR2024-00232 is the '730 patent proceeding that was terminated by adverse judgment and is not appealable. This error does not change the '730 conclusions but would be a factual error if carried into a brief.

---

Recommended next steps

1. If you are a defendant and the demand letter / complaint cites claims 1–17 of 8,352,730 — say so and stop. Those claims do not exist. Attach: (a) the 2025-04-28 adverse judgment order in IPR2024-00775 (cancelling claims 1–17, expressly a § 318(a) FWD); (b) the 2025-04-28 order in IPR2024-00232 (cancelling claims 1–6 and 8–17); and (c) Microsoft's motion explaining the consequence, Proxense, LLC v. Microsoft Corp., No. 6:23-cv-00319-ADA (W.D. Tex. May 9, 2025), Dkt. 95 — https://storage.courtlistener.com/recap/gov.uscourts.txwd.1217252/gov.uscourts.txwd.1217252.95.0.pdf — which argues the claims must be dismissed with prejudice under Rule 12(b)(1) because "Not one claim of the '730 patent remains." Authority: Fresenius USA, Inc. v. Baxter Int'l, Inc., 721 F.3d 1330, 1340 (Fed. Cir. 2013).

2. Identify which claims are actually being asserted before conceding anything. Confirm on USPTO PatentCenter / PTAB E2E whether a reexamination certificate in 90/015,052 actually issued on 2026-01-29 cancelling claims 1–17 and issuing claims 18–34, and obtain the certificate text and the intervening NIRC/office actions. My only source for the certificate is Proxense's own appellate brief (https://ipfray.com/wp-content/uploads/2026/04/26-04-03-Proxense-v.-Apple-Microsoft-appellate-opening-brief-1.pdf), which is advocacy — the same reexam record shows a 2025-07-29 examiner rejection of claims 18–34 over Burger. Do not assume claims 18–34 are valid, and do not assume they are dead.

3. No PTAB milestones are pending for this patent — nothing to wait for. Every '730 IPR is terminated (three by adverse judgment on 2025-04-28, three by denial of institution), so there is no institution-deadline, no oral hearing, and no statutory one-year FWD deadline running. Do not build a stay argument on pending '730 IPRs.

4. Watch the '954 appeal as a proxy for the '730 reexam claims. The live Federal Circuit appeal (Nos. 2025-2130/2025-2131) seeks to revive the PTAB's claim construction of "a third party that operates a trusted authority," and Proxense's newly issued '730 claims 18–34 turn on nearly identical "access message received by the application" language. If the appeal affirms, the § 42.73(d)(3) non-patentably-distinct estoppel plus the FWD findings give you a strong invalidity/estoppel package against claims 18–34. Docket and brief at https://ipfray.com/wp-content/uploads/2026/04/26-04-03-Proxense-v.-Apple-Microsoft-appellate-opening-brief-1.pdf (per curiam consolidated dockets on the Federal Circuit; also available on CourtListener).

5. Preserve your own prior-art runway now. Because the '730 IPRs ended in adverse judgment rather than a merits FWD, your § 315(e)(2) exposure is limited and no issue-preclusion attaches. If you are a defendant outside the Google/Apple/Microsoft privies, art such as Scott, Russell, Lapsley (Samsung's IPR2021-01444 exhibits) and the Ludtke/Kon and Burger/Robinson lines remain available against any surviving claims — subject to your own invalidity contentions and the patent owner's § 42.73(d)(3) estoppel.

Explicit uncertainties. (i) I could not load USPTO PTAB E2E or the ODP API directly; the institution/denial and adverse-judgment facts above are drawn from primary PTAB documents mirrored on Docket Alarm and ex-parte (institution decisions in IPR2024-01333, IPR2024-00232/01333, the scheduling order in IPR2024-00775/00846, IPR2021-01444 Paper 11) and from district-court filings that quote the 2025-04-28 orders verbatim, so verify against PTAB E2E before filing. (ii) The reasoning behind the IPR2024-01326 denial is not in my record — I have not quoted it and I do not vouch for the "duplicate petition" explanation. (iii) IPR2024-01486's disposition ("not instituted – procedural") comes from Google Patents family metadata only; I found no Board paper. (iv) The exact petitioner caption on IPR2024-00232 changed when Apple joined (one appellee-side filing names "Apple Inc. v. Proxense, LLC, IPR2024-00232"), and one scheduling-order copy for IPR2024-00775/00846 is mis-captioned "GOOGLE LLC" even though Microsoft is the IPR2024-00775 petitioner; I have resolved both in favor of the record evidence (Google lead + Apple joined; Microsoft petitioner) and flag them rather than silently harmonizing.

I'll research the assignment record for US 8352730 across USPTO Assignment Center, Google Patents legal events, and third-party sources.

Let me dig for the actual reel/frame numbers and the correspondent of record.

Let me try to pin down the exact reel/frame record via assignment-specific sources.

I hit the tool-call limit mid-research, so let me be precise about what I confirmed versus what I could not retrieve. One key primary quote did come through: the USPTO's 2024‑01‑03 Decision on Petition in reexam 90/015,052 states, "According to Office records, the '730 patent is currently assigned Proxense LLC."

Inventors

• The '730 lists one inventor only. There is no multi-inventor team and therefore no "all inventors departed within 12 months" pattern — the inventor is the assignee's principal. Per Proxense's own W.D. Tex. complaints, "John Giobbi is the founder and CEO of Proxense… a named inventor on approximately 200 patents," and he was previously a Senior VP at WMS Gaming.
• Consequence for an ownership analysis: because inventor and assignee-controller are the same person, there was never a churn risk between inventors and the company, and no inventor-side reversion interest is visible in the record.
• Related applications in the family name the same inventor, with co-inventors appearing only on later, non-'730 patents (e.g., David L. Brown, Fred S. Hirt on US 10,374,795 and the "Dynamic Real-Time Tiered Client Access" family).

Original assignee

• Issued assignee: Proxense, LLC, 689 NW Stonepine Drive, Bend, Oregon 97701 (address per the family's recorded assignment 034843/0145).
• Line of business: proximity-based wireless authentication built on the "personal digital key" (PDK) concept — reader/decoder circuits, ProxPay mobile payment, biometric PDK. Per Proxense's own complaints: founded 2001; "from approximately 2004–2012, Proxense developed… mobile payment technologies," employed "over thirty engineers," and invested "many millions of dollars" in R&D. The patented subject matter is precisely this product line.
• Did it ship a product embodying the claims? Partially — and not in recent years. The claims read on a biometric PDK plus a trusted third-party authority; Proxense's public statements describe building exactly that (biometric capture on a secure element, token passing to a trusted third party, PDK registration). But Proxense's own complaint language frames 2004–2012 as the development era, after which the company shifted to licensing/enforcement. Current status: operating as a patent-assertion/licensing entity; no evidence of a current commercial product line, no evidence of acquisition, dissolution, or bankruptcy in any record I retrieved.
• Not merely "originally assigned": every record I located shows Proxense as the current owner. The 2024 Office statement above, and the AO‑120 notice of suit filed in Proxense v. Microsoft, 6:23‑cv‑00319 (listing "Holder of Patent or Trademark: Proxense, LLC" for the '730, the '954, the '905, the '042, the '289 and the '960), both confirm continuity.

Assignment timeline

Important scoping caveat (stated first, per the constraints). I could not load the Patent Assignment Center result page for patent 8,352,730 directly (the tool call budget ran out), so I do not have the reel/frame number for the original 2006 Giobbi→Proxense assignment, and I will not guess it. What I do have is: (a) Google Patents' legal-events record for the '730 showing one recorded assignment; (b) the Patent Assignment Abstract of Title for the sibling application 14/521,982 (US 9,298,905) — a direct continuation of 11/314,199 — which reproduces the family's assignment record; and (c) the USPTO's own 2024 statement that the '730 "is currently assigned Proxense LLC." Treat item (b) as family-level evidence, not as a document I verified names property 11/314,199.

• Executed [date not captured] / recorded 2006-03-13 — Reel NNNNNN/NNNN (not retrieved)

  • Conveyance: ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS)
  • Assignor: GIOBBI, JOHN J.
  • Assignee: PROXENSE, LLC, Bend, Oregon
  • Correspondent: Not confirmed. The '730's record attorney/agent of record is Patent Law Works LLP (address of record on the file: "Patent Law Works/Proxense," 201 South Main Street, Suite 250 — later 165 South Main St, Suite 2 — Salt Lake City, UT 84111; attorney Greg Sueoka). Patent Law Works is also the firm of record on the '954 and '905 file histories. I cannot confirm that the same firm is named as correspondent on the assignment coversheet itself. ⚠️ If the coversheet correspondent is Patent Law Works, that is a recurrence across the family but is ordinary prosecution-firm work, not an independent NPE tell.
  • Context: founding/inventor-to-company assignment (the standard inventor-assigns-to-employer link; not a fire-sale, not an acquisition).

• Executed [2015, date not captured] / recorded 2015-01-29 — Reel 034843/0145 (Pages: 3; Mailed 2015-01-30)

  • Conveyance: ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS)
  • Assignor: GIOBBI, JOHN J. — Assignee: PROXENSE, LLC, 689 NW Stonepine Drive, Bend, Oregon 97701
  • Correspondent: Not stated in the Abstract of Title extract I retrieved.
  • Context: family housekeeping / confirmatory assignment. Two flags: (i) it is recorded against application 14/521,982 (US 9,298,905), a continuation of the '730, and I could not verify whether the document's property schedule also lists 11/314,199; (ii) it is an assignment to the same original assignee eight years after the first one — a re-recordation pattern, not a transfer to a third party.

Bottom line on the timeline: as best the public record shows, the '730 has been owned by Proxense, LLC continuously since 2006, with no post-issuance transfer, no security agreement, no release, no merger and no change-of-name record appearing in any source I retrieved. The '730 was unitary ownership for the entire 2021–2025 assertion campaign. This is itself the headline finding: there is no assignment chain to audit and therefore no venue- or standing-engineered transfer.

Timeline diagram

timeline
    title Ownership of US 8352730
    2005 : Application filed Dec 20
    2006 : Giobbi assigns to Proxense LLC
    2013 : Patent issued Jan 8
    2015 : Family assignment recorded
         : Reel 034843 frame 0145
    2021 : First suit filed vs Samsung
    2024 : USPTO confirms Proxense owner

NPE / troll-pattern signals

1. Shell-entity transfer — NOT PRESENT. There is no transfer at all out of Proxense. The record assignee is the original R&D company that appears on the face of the patent, at a Bend, Oregon street address (689 NW Stonepine Drive), not a registered-agent service address. No "IP/Holdings/Ventures/Licensing" successor LLC appears anywhere in the chain. The naming alone would not be a finding — but here there is no transfer to analyze.

2. Known asserter in the chain — PRESENT (one strong signal). Proxense, LLC is itself a repeat, high-frequency plaintiff: the '730 alone was asserted in six W.D. Tex. actions (6:21‑cv‑00210 Samsung; 6:23‑cv‑00319 Microsoft; 6:23‑cv‑00320 Google; 6:24‑cv‑00143 Apple; 6:24‑cv‑00283 Intel; 6:24‑cv‑00302 LG), plus a separate Hyundai/Kia/Genesis campaign in Jan. 2025 on sibling patents. Third-party assert-platform dockets (Patentpia, Unified Patents) classify Proxense as "NPE: Yes." But note the limitation: Proxense does not match the classic acquirer list (Acacia, Marathon, IV, Wi‑LAN, Conversant, Vringo, Pendrell, Round Rock, etc.). It is an original-owner assertion entity — a self-asserting startup-turned-licensor, not a portfolio aggregator.

3. Repeat correspondent across the chain — UNCLEAR. The chain has only one meaningful link (2006), so there is nothing to be recurrent within the chain. Across the family, the recurring names are Patent Law Works LLP / Greg Sueoka (prosecution and file-history correspondent for the '730, '954 and '905) and, for the reexam, Hard IP LLC (General), 10 Notch Hill Drive, Livingston, NJ 07039 as patent owner's counsel, with Marissa R. Ducca, Quinn Emanuel, 1300 I Street NW, Suite 900, Washington, DC as third-party requester's correspondent. I did not retrieve any assignment coversheet's correspondent field, so I make no finding here. Per the constraint, a single appearance is not a finding — and I cannot even establish a single appearance on the assignment documents.

4. Cascading transfers — NOT PRESENT. Zero consecutive assignments through chained LLCs. The only two records are both to the same assignee (Giobbi → Proxense, 2006; Giobbi → Proxense, 2015), 9 years apart.

5. Pre-litigation transfer — NOT PRESENT. No assignment precedes the first suit. The earliest possible transfer date (2015-01-29) is more than six years before the first '730 complaint (2021-03-05), and the operative original assignment (2006) is fifteen years before it. There was no venue- or standing-engineering transfer to audit — which is also why Proxense's standing was never successfully challenged in the W.D. Tex. cases.

6. Bankruptcy fire-sale — NOT PRESENT. No Chapter 7/11 record, no trustee sale, no § 363 sale. Proxense's complaints describe a 2004–2012 development era and a later licensing pivot, not an insolvency event. (Absence of evidence here is based on the records I could retrieve; I did not search PACER's bankruptcy index.)

7. Privateering — NOT PRESENT. Privateering requires an operating company transferring to an NPE that asserts on its behalf against that company's competitors. Here the assignee is the company, and the inventor/CEO is inside it; there is no separation between a product company and an assertion vehicle.

8. Defensive aggregator at the end of the chain — NOT PRESENT. No RPX / AST / LOT / Unified / OIN assignment. To the contrary, Unified Patents and RPX are adversarially involved (Unified's PTAB portal tracks '730 IPRs; RPX indices carry the litigation), and Unified/third-party filings drove the reexam.

Verdict

NPE — moderate confidence.

The chain is a single link, Giobbi → Proxense, LLC (recorded 2006‑03‑13; confirmatory re-recordation 2015‑01‑29 at reel 034843/0145 for the sibling 14/521,982), with no post-issuance transfer, security agreement, or aggregator acquisition anywhere in the record — and the USPTO stated on 2024‑01‑03 in reexam 90/015,052 that the '730 "is currently assigned Proxense LLC." That gives exactly one strong signal (the owner is a confirmed repeat patent asserter with no current product, classified "NPE: Yes" by third-party assert platforms), and none of the shell-entity, cascading-transfer, pre-litigation-transfer or fire-sale hallmarks — hence moderate rather than high confidence. The reason I do not reach "Operating-company assertion" is that the current assignee no longer ships products embodying the claims and is suing platform implementers rather than product-market competitors; the reason I do not reach "Insufficient data" is that the ownership question is answered—it is just a very short, clean chain.

Search page for verification: https://assignmentcenter.uspto.gov/ (enter patent number 8352730) and the legacy https://assignment.uspto.gov/patent/index.html (same underlying records).

Explicit uncertainties — please close these before relying on this section:

1. The 2006 reel/frame number is missing from my answer. I could not open the Assignment Center result for 8,352,730. Retrieve it directly; it is the one hard identifier this task asked for that I could not supply.
2. The 2015 record (034843/0145) was captured from the Abstract of Title for application 14/521,982, not for 11/314,199. One document often schedules multiple properties, but I did not verify that the '730 appears on that schedule. Confirm whether the '730 has one recorded assignment or two.
3. No assignment-coversheet correspondent field was retrieved for either record — so the "repeat correspondent" signal is genuinely unclear, not negative.
4. I did not search PACER's bankruptcy index; the "no bankruptcy" call rests on the absence of any such record in the sources I did retrieve.

I'll search for authoritative USPTO records and the key cited references for US 8,352,730.

Let me verify the two references Apple's IPR petition relied on, plus the Prokoski "Personal biometric key" reference.

Prior-Art Analysis — US 8,352,730 (Giobbi / Proxense, LLC)

1. USPTO record confirmation (identity check first)

The number resolves to exactly one patent, and I did not substitute a similar number:

Consistent with the earlier-generated section, I flag but do not "correct" the one-day offsets in the Unified Patents portal (priority 2004-12-19; app. 2005-12-19; grant 2013-01-07; expiry 2028-07-14). Google Patents/SumoBrain/the granted PDF agree with the Dec. 20 dates; the portal is one day earlier on each. The IDS family also shows the reference "US 11/314,199 / 2005-12-20" in the same family record.

Prior-art keywords indexed by the Office/Google for this patent: codes, biometric, data, user, data values — i.e., the search was driven by the "plurality of codes and other data values" language of independent claims 1/8/12/15, which is useful to know when reading the reference set below.

---

2. How to read the § 102 column — a mandatory caveat

The '730's independent claims each co-require five things that must appear in a single reference for true § 102 anticipation:

1. write-once/tamper-proof storage of the user's biometric data plus a plurality of codes and other data values including a device ID code and a secret decryption value;
2. a biometric type from the closed group (palm print, retinal, iris, hand geometry, facial, signature, voice) — fingerprint appears only in dependent claim 5;
3. local (on-device) scan-vs-stored comparison;
4. wireless sending of the code(s) for authentication by an "agent" = a third-party trusted authority possessing a list of device ID codes uniquely identifying legitimate integrated devices; and
5. receipt of an access message from that agent permitting access to an application from the recited group.

Most of the 142 examiner-cited references were placed in the IDS to build the general background of "biometric access control" and "portable credential" art; roughly 80+ of them are directed to unrelated or tangential technology (pay‑TV/conditional‑access decoders such as US 4,759,060 and US 6,034,038; DRM/digital-content and copy-protection art such as US 5,629,980, US 6,775,655, US 6,633,? / US 6,690,? ; music distribution; interactive TV/EPG). Those have no realistic § 102 relationship to the biometric-verification claims and I do not list them individually beyond this note.

Below I give the references that actually bear on the claim language, ranked by § 102 exposure. Where the reference is close but missing a required element, I say so explicitly rather than overclaiming anticipation.

---

3. Tier 1 — References with genuine § 102 anticipation potential

3.1 US 6,041,410 — "Personal identification fob" (Hsu et al., TRW Inc.)

• Full citation / dates: US 6,041,410 A; Appl. 08/995,267 filed Dec. 22, 1997; granted Mar. 21, 2000. Inventors Hsu, Ling, Messenger, Evans; assignee TRW Inc. Foreign counterpart EP 0 924 656 A2 (pub. Jun. 23, 1999), which is the same disclosure.
• Description: A handheld fob containing a fingerprint sensor, a memory storing the user's reference fingerprint image enrolled under agent control, and a correlator that compares the live print to the stored print. On a match the fob derives a numerical value (a CRC of the stored reference image), encrypts it (double-encrypts using a door-supplied public key and the fob's fixed private key), and transmits it wirelessly together with user-identification data to a "door." The door compares the received value with a value previously registered by the user at that door and actuates access on match. The fob's private key is stored so it cannot be discerned by inspection or reverse engineering; the door may broadcast a "wake-up" call to the approaching fob.
• § 102 claims potentially anticipated: Claim 1 (method) — persistent storage of biometric data + stored secret/ID values + local comparison + wireless transmission of a value for verification + access granted on verification. Claim 8 (device). Claim 12 (verifier side) — comparison of the transmitted value against a previously stored/registered value. Claim 15 (system) and dependents 2, 4, 5, 6, 7, 9, 16, 17.
• Why it is not a clean anticipation: the "door" is the verifier, not a third-party trusted authority possessing a list of device ID codes; and there is no express "list of legitimate device IDs." A § 103 case (fob art + remote-authority art) is stronger than pure § 102 against claims 1/8/12/15, but the reference is the single closest structural anticipator of the fob-plus-local-biometric-plus-wireless-code architecture.

3.2 US 6,219,439 — "Biometric authentication system" (Paul M. Burger)

• Full citation / dates: US 6,219,439 B1; Appl. 09/350,771 filed Jul. 9, 1999; granted Apr. 17, 2001; provisional 60/092,196 filed Jul. 9, 1998.
• Description: A dual-input reader with a smart card holding stored biometric data of the user plus a non-biometric identifier, and a fingerprint scanner on the reader. The comparison is performed on board the reader; a control chip prevents any communication with external sources until the user is positively authenticated; then a second comparison of the card's non-biometric identifier against remotely stored user data occurs to further determine authentication status, with a status indicator.
• § 102 claims potentially anticipated: Claim 1 and claim 8 in architecture (stored biometric + stored ID data, local compare, then external verification, then access). Also relevant to claim 6 (secure channel established before sending) and claims 12/15 (external verification of the identifier).
• Gap: no secret decryption value in write-once storage is recited, and the external comparison is against "user data," not a recitation of a third-party trusted authority holding a list of legitimate device ID codes. Also note the '730 patent itself cites Burger in the IDS.

3.3 US 4,993,068 — "Unforgeable personal identification system" (Piosenka et al., Motorola)

• Full citation / dates: US 4,993,068 A; filed Nov. 27, 1989; granted Feb. 12, 1991.
• Description: A portable, credit-card-sized memory device storing encrypted personal identification credentials — expressly facial photo, retina scan, voice and fingerprints — presented at a remote access-control site, where the user physically submits the corresponding biometric; comparison determines allow/deny access to a protected asset.
• § 102 claims potentially anticipated: Claim 8/15 at the level of "portable device storing biometric data in tamper-resistant form; compare; grant access." Relevant to the closed biometric group of independent claims 1/8/15 (retina, facial, voice all present).
• Gap: no wireless relay of a device-ID code to a third-party authority; comparison occurs at the access site. Best used as § 103 background, not standalone anticipation.

3.4 US 6,016,476 — "Portable information and transaction processing system and method utilizing biometric authorization and digital certificate security" (Maes et al., IBM)

• Full citation / dates: US 6,016,476 A; filed Aug. 11, 1997; granted Jan. 18, 2000.
• Description: A portable (smart-card/PCMCIA-like) device that stores biometric authorization data and digital-certificate credentials, performs a local biometric check, and uses public-key/digital-certificate security to authenticate the device/transaction to transaction-processing equipment.
• § 102 claims potentially anticipated: Claim 1 / 8 / 15 as to "persistently store biometric data and credential values; local biometric verification; then cryptographically authenticate to an external processing entity"; and claim 12 (verifier receives code and authenticates).
• Gap: the external entity is a transaction processor, not a third-party authority with a list of legitimate device ID codes.

3.5 US 6,363,485 — "Multi-factor biometric authenticating device and method" (Adams et al., Entrust)

• Full citation / dates: US 6,363,485 B1; filed Sep. 9, 1998; granted Mar. 26, 2002.
• Description: A multi-factor biometric authentication device combining biometric input with cryptographic/binding factors to authenticate a principal to a system; discusses storing biometric/signature data and binding it to a device identity.
• § 102 claims potentially anticipated: architecture for claims 1, 8, 12, 15 (multi-factor, device-bound credential + biometric).
• Gap: no "trusted key authority + list of device ID codes" and no express write-once "secret decryption value."

3.6 US 6,256,737 — "System, method and computer program product for allowing access to enterprise resources using biometric devices" (Bianco et al., Bionetrix Systems — now Citibank per Unified Patents)

• Full citation / dates: US 6,256,737 B1; filed Mar. 9, 1999; granted Jul. 3, 2001.
• Description: Central biometric server architecture — client biometric devices capture prints; a server holds enrolled biometric templates and decides whether to authorize access to enterprise resources. This is the closest cited reference to the "trusted key authority holding a list of enrolled devices" concept of claims 1/8/12/15.
• § 102 claims potentially anticipated: Claims 12 and 15 (remote authority holding enrollment data and returning an access decision) and claim 1 in combination.
• Gap: the client device is not recited as storing a secret decryption value in write-once memory, and it transmits biometric data to the server rather than only a device-ID code — a meaningful difference on the claim text.

---

4. Tier 2 — Secondary references (field-adjacent; § 102(e) or chain-of-priority issues)

4.1 US 6,983,882 / US 2004/0188519 A1 — "Personal biometric authentication and authorization device" (Cassone, Kepler, Ltd.)

• Dates: Appl. 10/403,934 filed Mar. 31, 2003; granted Jan. 10, 2006; pre-grant US 2004/0188519 A1, pub. Sep. 30, 2004 (i.e., before the '730 Dec. 20, 2004 priority).
• Description: A personal "PAD" storing multiple users' biometric data plus user account data, comparing a fingerprint to the stored data and, if matched, releasing/writing credential data (magstripe/smart-card account data) for transactions; the PAD enrolls with an enrollment system that validates a PAD identifier (e.g., MAC address) against a database and returns account data; the account data may be encrypted, and the PAD can be disabled if tampered with.
• § 102 claims potentially anticipated: Claims 1, 8, 12, 15 — device-ID registration with a remote enrollment/validation system, biometric-gated release of credential data, and secure/加密 storage. Effective as prior art under pre-AIA § 102(e) via the 2004 publication (its Mar. 31, 2003 filing date predates the '730's earliest effective date).
• Gap: the external system validates the PAD, but the issued claims recite a trusted authority with a list of device ID codes returned as an "access message"; the mapping is close but not identical.

4.2 US 6,850,147 / US 2002/0140542 A1 — "Personal biometric key" (Prokoski et al., Mikos Ltd.)

• Dates: Appl. filed Apr. 2, 2001; granted Feb. 1, 2005; pub. US 2002/0140542 A1, Oct. 3, 2002. (Both the granted patent and the publication appear in the '730 citation lists.)
• Description: A "personal biometric key" — a compact device storing a user's biometric template and using it to unlock stored credential/key material for authorized use; authorizes transactions/access on biometric match. The title phrase itself tracks the '730's "biometric personal data key."
• § 102 claims potentially anticipated: Claims 1/8/15 (portable biometric key + biometric-gated release of credential material); claim 5 (fingerprint).
• Gap: no third-party trusted authority with a device-ID list; no "secret decryption value" in write-once memory.

4.3 US 2005/0251688 A1 — "Identity verification method using a central biometric authority" (Nanavati)

• Dates: Priority May 13–14, 1999; published Nov. 10, 2005 (continuation publication). Effective prior-art date can reach back to the 1999 priority under § 102(e).
• Description: Verification of identity via a central biometric authority (the exact "third-party trusted authority" concept of claims 1/8/12/15). Relevant to the intent of the "agent" limitation.
• § 102 claims potentially anticipated: Claims 12 and 15 (central authority verifying an identity token); claim 1 in combination.
• Gap: the identity token is not recited as a device-ID code stored in write-once tamper-proof memory with a secret decryption value.

4.4 US 5,623,552 — "Self-authenticating identification card with fingerprint identification" (Lane)

• Dates: filed Jan. 21, 1994; granted Apr. 22, 1997.
• Description: A card that stores a fingerprint template and self-authenticates its bearer before enabling use — background for the "integrated device with stored biometric + stored credential" concept (claims 1/8/15).
• Gap: no wireless code to a remote trusted authority.

4.5 US 5,598,474 — "Process for encrypting a fingerprint onto an I.D. card" (Johnson)

• Dates: filed Mar. 29, 1994; granted Jan. 28, 1997.
• Description: Encrypting a fingerprint onto an ID card for later verification — background relevant to the "secret decryption value"/encrypted-store language of claims 1/8/15.
• Gap: no remote trusted-authority verification.

4.6 US 5,917,913 — "Portable electronic authorization devices and methods therefor" (Wang)

• Dates: filed Dec. 4, 1996; granted Jun. 29, 1999.
• Description: Portable electronic authorization device with authentication of the holder before authorizing a transaction — background for the apparatus/system claims.
• Gap: primary authentication is not remote-trusted-authority-based device-ID lookup.

4.7 US 2002/0150282 A1 — "Fingerprint sensor with feature authentication" (Kinsella)

• Dates: priority Apr. 16, 2001; published Oct. 17, 2002.
• Description: Fingerprint sensing/feature authentication of a holder for a device — supports claim 5 (fingerprint-based data and scan data) and general biometric-verification framing.
• Gap: single-factor sensor art; no code-to-authority relay.

4.8 US 2004/0230488 A1 — "Method for using a sensor to register a biometric for use with a transponder-reader system" (American Express Travel Related Services)

• Dates: priority Jul. 10, 2001; published Nov. 18, 2004.
• Description: Registering a biometric for use with an RF transponder-reader (contactless credential) system — relevant to the wireless/biometric credential elements of claims 1/8/15.
• Gap: IDS-level background; does not recite the trusted-authority list of device IDs.

4.9 US 2004/0129787 A1 — "Secure biometric verification of identity" (Saito et al., IVI Smart Technologies)

• Dates: priority Sep. 10, 2002; published Jul. 8, 2004.
• Description: Secure biometric identity verification with a portable device and a verifying party — background to the "verification unit" and secure-channel limitations (claims 6, 14).

---

5. Tier 3 — Environment/application references (mostly relevant to the recited "application" group and to § 103 motivation)

These are cited to cover the claim-1/8/12/15 "application selected from the group consisting of a casino machine, a keyless lock, a garage door opener, an ATM machine, a hard drive, computer software, a web site and a file":

None of these, alone or as a group, supplies the device-ID-code-to-third-party-trusted-authority limitation; their role is (a) to show the recited application environments were known, and (b) to supply § 103 motivation.

Note on the two Giobbi "Digital content security system" references (US 6,973,576 B1, filed 2000-12-27, granted 2005-12-06; US 7,305,560 B2, granted 2007-12-04): these share the same inventor and assignee, so they are not § 102 prior art against the '730 (an inventor's own work). They appear in the citation list as family/background art and should not be used in a § 102 mapping.

---

6. References asserted in the PTAB proceedings that are NOT in the examiner-cited list

The earlier-generated section established that the operative post-grant challenges turned on art that the Examiner did not cite:

• Burger — US 2005/0050367 A1 (Chameleon Network "Pocket Vault" published application; family includes US 7,003,495, US 7,080,037, US 7,340,439, US 2010/0031043). Petitioner in IPR2024-01486 (Apple Inc. v. Proxense, LLC) asserted that Burger discloses all limitations of claims 1–2, 4–9, 11–12, 14–17: a portable device storing fingerprints + a unique chip ID in write-once memory (element 212), enrolling/registering that encrypted chip ID with a network server through a secure connection, verifying the holder's fingerprint entirely on board, and, only on authentication, wirelessly transmitting the encrypted chip ID for network-server authorization of a transaction. This is materially the same architecture as claims 1/8/12/15 and is the single most dangerous reference in the family of prior art, notwithstanding that it was not before the Examiner during prosecution.
• Robinson — US 2003/0177102 A1, relied on by the same Petitioner only for the age-verification dependent claims (3, 10, 13), i.e., registering a user's age/date of birth in association with a biometric sample and a unique system ID. I could not independently re-verify Robinson's bibliographic details (assignee, exact filing/publication dates) in this session — treat those as unconfirmed and check the PTAB record directly.

Caveat, per the operating rules: the IPR record I relied on is a petition mirror (ex-parte/IPR docket), and the Google Patents family metadata records these petitions as "Not Instituted – Procedural." Verify the ultimate disposition against the PTAB's own docket before treating Burger/Robinson as adjudicated prior art.

---

7. Consolidated mapping: cited reference → claims it could touch under § 102

My conclusion: On the examiner-cited record, no single reference anticipates all limitations of independent claims 1, 8, 12, or 15; the recurring unmet limitations are (i) the third-party trusted authority possessing a list of legitimate device-ID codes and the responsive "access message," and (ii) the secret decryption value stored in write-once/tamper-proof form. The closest examiner-cited single references are US 6,041,410 and US 6,219,439. The references with the highest real-world § 102/§ 103 risk — Burger (US 2005/0050367), which the Office never considered during prosecution — came in through the PTAB, not the IDS.

---

8. Explicit uncertainties

• Robinson, US 2003/0177102 — I could not re-verify its bibliographic data in this session; the description above is from the IPR2024-01486 petition summary, not from the reference itself.
• Volume limit: the '730 lists 142 cited references. I have given detailed treatment to the ~25 with any claim-relevant content and grouped the remainder by subject matter. With ~80 of them in the pay‑TV/DRM/music/interactive‑TV classes, a reference-by-reference § 102 walkthrough of all 142 would be padding rather than analysis; the groups I excluded have no disclosure of local biometric verification or device-ID authentication.
• Sources: USPTO data as mirrored by the granted PDF (patentimages US008352730B2), Google Patents, SumoBrain, USPTO.report, and the Unified Patents portal; the PTAB assertions are from IPR2024-01486 petition mirrors, which I have not validated against the PTAB's own docket. Priority/filing/grant/expiry one-day discrepancies noted in § 1 remain unresolved between sources and are reported rather than corrected.

Obviousness Analysis — U.S. Patent No. 8,352,730 under 35 U.S.C. § 103

Scope note: This section assumes the bibliographic and family facts from the previously generated Summary (§§1–7) and does not repeat them. All prior art is drawn from the "Citations (142)" and "Family Cites Families" listings on the patent's Google Patents page; the "Cited By (45)" and most of "Families Citing this family (21)" entries post-date the '730 priority date and therefore are not prior art to the '730 (they are useful only as evidence of what the field was doing immediately after).

Minor flag: the task states the current date is April 26, 2026; the patent page fetch in the earlier section is stamped 2026‑09‑18. I have not tried to reconcile this metadata discrepancy; nothing in the analysis below turns on it.

---

1. Legal framework and the pre‑AIA posture

Application 11/314,199 was filed December 20, 2005, so the '730 is governed by pre‑AIA § 103(a) with pre‑AIA § 102 prior‑art definitions. Provisional priority is December 20, 2004 / February 14, 2005. The Graham factors (scope/content, differences, PHOSITA level, secondary considerations) apply, as elaborated by KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007), which governs here even though the application predates it.

Two structural facts drive everything below:

1. The independent claims are all the same invention in four postures — key‑side method (claim 1), key apparatus (claim 8), verifier‑side method (claim 12), and system (claim 15). An obviousness showing against claims 1/8/12/15 is largely transferable across the four.
2. The true points of novelty are narrow and identifiable: (i) permanent/write‑once storage of both biometric data and a plurality of codes/values — including a device ID code and a secret decryption value; (ii) local matching on the token; (iii) wireless relay to a third‑party trusted authority holding a list of legitimate device IDs; and (iv) receipt of an access message granting access to a recited application. The recited application list is, on its face, a recitation of intended environments rather than a structural limitation.

The page's own "Prior art keywords" — codes, biometric, data, user, data values — track the "plurality of codes and other data values" limitation, confirming that the examiner treated that phrase as the crux.

---

2. Level of ordinary skill (PHOSITA)

A bachelor's degree in electrical engineering or computer science (or equivalent), plus 2–3 years of experience with secured portable credentials (smart cards, RFID/transponder tags, biometric access control), or equivalent work experience. This is consistent with the art cited on the face of the '730 and with the '730's own characterization of the field. At this level, the following were all routine design choices by December 2004: choosing a biometric modality; choosing an optical vs. capacitive sensor; selecting ROM/OTP/WORM vs. flash memory; choosing a short‑range RF link; and placing an enrollment list on a server rather than on the token.

---

3. Prior‑art inventory from the Citations section, grouped by function

Not prior art (flag): the two Proxense/Margent family publications in the list (WO 2005/050450 A1, priority 2003‑11‑17; WO 2005/086802 A2, priority 2004‑03‑08; US 6,973,576, priority 2000‑12‑27) were published after December 20, 2004, and share the same inventive entity/assignee, so they do not qualify as § 102(a)/(b)/(e) art against the '730. Similarly, everything in "Cited By (45)" (2010–2025) is post‑dating art.

---

4. Element‑by‑element mapping for independent claim 1

---

5. Recommended combinations and the motivation to combine

Combination 1 (primary — against claims 1, 8, 12, 15): Piosenka '068 + TRW '410 + Bionetrix '737, optionally + Johnson '474 (tamper‑proof storage) + IBM '476 (device ID + secret key)

• '068 + '410 render obvious a portable, battery‑powered device that stores a biometric representation, captures a sample on request, compares locally, and — on a match — wirelessly emits a credential. Both are in the identical field (personal identification/access control) and address the identical problem (unauthorized use of credentials). Combining them is the paradigmatic KSR "familiar elements arranged according to known methods," each performing its own known function, yielding the predictable result of a self‑contained wireless biometric credential.
• + '737 supplies the recited agent. The motivation is articulated by the '730's own specification: it distinguishes open‑loop systems (unknown users, e.g., a public grocery store) from closed‑loop systems, and explains that a third‑party authority is used "in order to provide enhanced security." Moving the list of legitimate devices from the token to a server (i) removes the need to periodically update the token's memory, (ii) enables real‑time revocation of lost/stolen keys (a recognized problem in the Background), (iii) enables open‑loop operation across many relying parties, and (iv) lets the token stay small, cheap, and low‑power — a well‑recognized design driver for battery fobs such as '410. POSITAs at the time routinely split "local verification" (privacy, latency, offline capability) from "remote authorization" (revocation, cross‑domain trust); this is exactly the two‑tier architecture found in '737.
• There is no teaching away: '737 discloses server‑side matching as an option, while '552 and '410 disclose token‑side matching. A reference that teaches alternatives does not teach away from either (In re Fulton; Medichem).
• Reasonable expectation of success is high: every link in the chain (biometric sensor, local matcher, RF link, network round‑trip, database lookup, access grant) is individually disclosed by the references and was known to interoperate.

Combination 2 (against claims 1, 8, 15): Cardguard '552 + Motorola '534 + Bionetrix '737 + IBM '476

'552 supplies the self‑authenticating card, '534 supplies secure wireless key exchange to a network domain, '737 supplies the remote authority, and '476 supplies the co‑stored device identity and secret key. Motivation: the '730 itself describes storing "encryption/decryption keys utilized to establish secure communications links" in the same persistent storage as the code and biometric data; '476 and '534 make that an explicit, conventional implementation choice.

Combination 3 (against claims 1, 8, 15, 16, 17): TRW '410 + Bionetrix '737 + a listed‑modality reference

Claim 1's Markush group excludes fingerprint, while claim 5 (depending from claim 1) recites a fingerprint scan. That internal inconsistency is important for the § 103 analysis:

• If the claim is construed so the Markush group governs, then '410 (fingerprint) does not literally read on claim 1, and the petitioner must supply a reference teaching a listed modality (e.g., a retinal/iris or hand‑geometry reader — the page lists US 6,018,739, Raytheon, "Biometric personnel identification system," which I believe concerns an eye/physiological biometric, and US 6,219,439, Burger, "Biometric authentication system"). Substitution of one known biometric modality for another is an obvious design choice, particularly where — as here — the '730 specification itself lists all of these modalities as interchangeable: "the biometric data can include a palm print, a retinal scan, an iris scan, hand geometry recognition, facial recognition, signature recognition, or voice recognition." A specification that recites a list of known equivalents is powerful evidence that the choice among them is not inventive.
• If, instead, the claim is construed to cover fingerprint (as claim 5 implies), then '410 maps directly and the Markush group becomes an indefiniteness/§ 112 problem for Proxense rather than a § 103 shield.

Either way, the combination is available; the branch simply changes which secondary reference is needed.

Combination 4 (against claim 12 — verifier‑side method): Bionetrix '737 + TRW '410 + AmEx '488

Claim 12's steps — receive a code including a device ID registered with a third‑party trusted authority; request authentication of the code from that authority; receive an access message; allow access — are precisely the server‑side/resource‑side steps of '737, with '410/'488 supplying the wireless token that delivers the code. Motivation: outsourcing authentication to a trusted authority is expressly described in the '730 as being for "enhanced security" when the application "is security‑critical," and '737 already teaches the resource server asking the authority. This combination makes claim 12 the weakest of the four independent claims, because it contains neither the write‑once storage limitation nor the co‑stored secret decryption value.

Combination 5 (against dependents 3, 10, 13 — age/DOB registration against the device ID): Sierra '333 + IGT '2002/0098888 + Walker '2004/0127277 + Bionetrix '737

The '730 specification's flagship example is casino age verification. Sierra '333 ("Player identification using biometric data in a gaming environment") and the IGT wireless‑gaming publications establish that associating an identified, biometrically verified player with a stored profile (including eligibility/age) at a casino machine was known. Storing the DOB/age at the authority that already holds the device list is a trivial data‑modeling choice. Motivation: gaming regulators require age verification; a networked player‑tracking server already holds player data, so adding an age/DOB field is an obvious use of the existing data structure (KSR: "a change in a data structure known in the art").

Claim 7 in particular — the "code‑only, no biometric prompt" mode

Claim 7 is arguably the most vulnerable claim in the patent. The '730's own Background section is an admission of the prior art:

"Another technique … is to provide the user with an access object such as a key (e.g., an electronic key) that the user can present to obtain access … a small electronic key fob that allows access to a building or other secured location. A difficulty with using access objects is that authentication merely proves that the access object itself is valid; it does not verify that the legitimate user is using the access object."

That passage, combined with the '730 specification's own statement that "in some embodiments, biometric key 100 operates without biometric verification, and request[s] a fingerprint scan from a user only when biometric verification is needed," plus the transponder art ('488; '443, "Communication and proximity authorization systems"), renders claim 7 obvious — indeed nearly anticipated by the admitted prior art. An applicant's own admission of what was known is prior art (In re Nomiya; Riverwood Int'l).

---

6. Claim‑by‑claim § 103 summary

---

7. Where the rejection is weakest — and how Proxense will likely respond

1. The write‑once "unable to be subsequently altered" limitation. This is the single most defensible limitation in claim 1/8/15. Proxense will argue the cited art (smart cards, transponders) stores credentials in rewritable EEPROM/flash and that the references teach tamper‑resistance, not immutability. The counter is that mask ROM, PROM, and OTP memory were commodity technologies in 2004 and that the specification presents write‑once storage as one of several known alternatives ("a ROM element, a flash memory element, or any other type of non‑volatile storage element … at least some of persistent storage 226 is a memory element that can be written to once but cannot subsequently be altered"). Under KSR's "predictable variation" rationale, selecting a non‑volatile memory that cannot be rewritten to protect enrollment data is close to a per se obvious design choice — but expect this to be the contested battleground, because it is the limitation the examiner appears to have relied on.
2. The co‑stored "device ID code and secret decryption value … [with] biometric data." No single reference in the Citations list clearly discloses all three items in one write‑once store. The rejection must therefore be a true three‑ or four‑reference combination, with an articulated reason to co‑locate the key material with the biometric template (the '730 itself supplies that reason: "persistent storage 226 can store encryption/decryption keys utilized to establish secure communications links"), which actually helps the challenger.
3. "Third‑party trusted authority." This is the construction the Federal Circuit appeal is fighting over in the sibling '954 case (per the Summary, §5: "a third party that operates a trusted authority"). Bionetrix's authentication server may be operated by the same enterprise that owns the protected resource, which could fall outside a narrow reading of "third‑party." Note, however, that the '730 specification defines the term capaciously — the trusted key authority "can be maintained locally" in a closed system — which undercuts a narrow construction and simultaneously broadens the claim's exposure.
4. Secondary considerations. Proxense will point to the commercial PDK line and to the industry's licensing behavior (the Samsung consent judgment, and reported settlements with Google and Intel in the W.D. Tex. cases). The challenger's response: (i) there is a nexus problem — the settlements are litigation‑avoidance decisions rather than evidence of praise for the claimed write‑once, co‑stored secret‑value token, and Proxense's post‑2004 products practice later, differently claimed inventions; (ii) licensing/settlement evidence is weak when it reflects a desire to end litigation rather than a recognition of technical merit; and (iii) a prior adjudication cuts the other way — the Summary (§5) records that claims of the child patent US 8,886,954 were held unpatentable in IPR2024‑00232/00846, and the '730 itself drew IPR petitions from Microsoft (IPR2024‑01326) and Apple (IPR2024‑01486), both recorded as "Not Instituted – Procedural."
5. Examiner allowance is not dispositive. The 142 citations on the face of the '730 mean the examiner saw most of this art and still allowed. That is a real obstacle for an IPR petitioner (the Board will weigh the examiner's allowance and the reasons of record), but it is not a legal bar to a § 103 holding.
6. Cross‑reference to the earlier sections. The Summary (§4) notes the '052 ex parte reexamination of the '730 and the examiner's proposed clarifying amendment concerning the "access message." That is a signal that the receiving‑an‑access‑message step was a live validity issue at the Office. If a challenger attacks the final clause of claim 1 on the theory that '737's "authorization to the resource" is not an "access message … received [by the key]," Proxense's amendment in reexam may have narrowed around it. Any § 103 theory should therefore be built so that the access‑message element is met squarely — either by a reference that returns a grant to the token, or by a construction argument that the message may be received at the authentication module on the user's behalf (as claim 12's structure suggests).

---

8. Contradiction / uncertainty log (things to verify before relying on this)

• Contradiction flagged: claim 1/8/15's Markush group excludes fingerprint, yet dependent claim 5 recites a fingerprint scan. The previously generated Summary (§3) already flagged this ("fingerprint is NOT in this list"). This is not a contradiction with the earlier section — it confirms it — but it materially changes the obviousness theory, so it is repeated here as the pivot between Combinations 1–2 and Combination 3.
• The specific technical contents attributed to US 6,018,739, US 6,219,439, US 6,667,684 B1, and US 2005/0251688 are inferred from the titles, assignees, and dates shown on the patent page plus general knowledge. I have not re‑read their full texts. Verify each before filing any paper, and note the identifier "US 6,667,684 B1" exactly as it appears in the Citations list rather than correcting it.
• The § 102(e) availability of US 2005/0251688 A1 (Nanavati) against a Dec. 20, 2004 priority date depends on whether it is supported by a pre‑Dec. 2004 U.S. filing; treat as tentative.
• The prior generated Summary (§1) records a one‑day disagreement between sources on the priority/filing/grant/expiration dates. That disagreement does not affect any § 103 conclusion above, but it does affect the § 102(b) critical date by one day, which is not outcome‑determinative for any reference relied upon.
• I did not find, and do not assert, any Federal Circuit docket naming the '730. The pending 2026 appeal identified in the earlier section (No. 2025‑2130, consolidated with 2025‑2131) involves US 8,886,954, and the '730 appears there only as the parent whose ex parte reexamination was stayed. Do not attribute that appeal to the '730.