US 11095640

I'll research the specific patent's claims text and check for any CAFC 2026 docket activity.

Let me find the actual claim language and check for any 2026 CAFC activity.

Let me try to retrieve the actual claims text and confirm no CAFC case names the '640 specifically.

I hit the tool-step limit before I could pull the verbatim claim set from a claims-bearing source, so some claim-level detail below is flagged as unverified. Here is the concise summary for US 11,095,640 B1 specifically — no similar numbers substituted.

US Patent No. 11,095,640 B1 — Summary

Sourcing note: The authoritative full text in this record (from https://patents.google.com/patent/US11095640B1/en) is truncated before the "Claims" section and before the "References Cited" table, so I could not read the literal claim set from the primary source. Claim-level descriptions below draw on the patent's own Abstract and Specification (in the record) plus the verbatim claim-17 limitation published in Unified Patents' PATROLL chart. Where I am inferring, I say so.

1. Bibliographic data

⚠️ Date-discrepancy flag (do not reconcile silently). The Unified Patents portal page for the same patent reports the dates one day earlier on every field: priority 2010-03-14, application date 2018-11-25, grant date 2021-08-16, expiration 2031-08-01. This is consistent with a UTC-vs-local (US Pacific) rendering difference rather than a data error, but per the operating rules I am flagging it rather than auto-correcting it. Google Patents (2010-03-15 / 2018-11-26 / 2021-08-17 / 2031-08-02) is used above because it is the source of the authoritative record in this project.

2. Abstract (verbatim, from the USPTO-derived record)

"A system and method provide automatic access to applications or data. A portable physical device, referred to herein as a Personal Digital Key or 'PDK', stores one or more profiles in memory, including a biometric profile acquired in a secure trusted process and uniquely associated with a user that is authorized to use and associated with the PDK. The PDK wirelessly transmits identification information including a unique PDK identification number, the biometric profile and a profile over a secure wireless channel to a reader. A computing device is coupled to the reader. An auto login server is coupled to the reader and the computing device and launches one or more applications associated with a user name identified by the received profile."

That abstract is effectively a paraphrase of the first independent claim, which is why it is the most reliable basis for describing claim 1 below.

3. Plain-language overview of the independent claims

Confidence framing: I can state with high confidence the substance of the auto-login independent claim (it tracks the Abstract almost word-for-word) and high confidence about the single verbatim claim-17 limitation recovered from the PATROLL chart. I could not verify the exact number, ordering, or total count (the record elsewhere references a 20-claim set, claims 1–20) — so treat the mapping of claim numbers below as probable, not confirmed.

Independent claim on automatic login / application launch (claim 1, per the Abstract)

A system for automatic access to applications or data, comprising:

• A Personal Digital Key (PDK) — a portable device carried by a user or affixed to an object — with memory storing one or more profiles, including a biometric profile that was acquired in a secure, trusted ("Notary"-administered) process and is uniquely associated with the user;
• The PDK wirelessly transmits identification information over a secure channel — specifically a unique PDK identification number, the biometric profile, and a profile — to a reader;
• A computing device coupled to the reader; and
• An auto login server coupled to the reader and the computing device that launches one or more applications associated with a user name identified by the received profile.

Plain English: a badge/fob-like key holds your identity and biometric template; when you come near a reader, the key hands over your ID and profile over an encrypted link, and a backend "auto login server" signs you in and starts the right applications for you — no password typing. The specification's motivating example is eliminating the "constant and time-consuming login and logout of healthcare providers."

Independent claim on proximity-gated access (claim 17 — the claim asserted and the PATROLL target)

The only verbatim claim text I recovered is element [17.1(b)]:

"the personal digital key including a profile uniquely associated with a user authorized to use the device when the personal digital key is proximal to the device and …"

Read with the surrounding structure, claim 17 is a system claim that recites:

• (a) a "device" (a controlled resource — e.g., a computing device/appliance), and
• **(b) a personal digital key carrying a profile that authorizes the user to use the device while the PDK is within proximity — plus at least one further element.

The W.D. Tex. infringement theory corroborates the shape of this claim: the complaint characterized claim 17 as covering the "proximity-based grant of access and automatic logout/securing when the device exceeds a defined proximity." The PATROLL chart meets that further element with De La Huerga's proximity auto-logoff teaching ("log the user off when he moves from the computer terminal beyond the limited range").

Plain English: access to a machine/resource is granted based on the key being nearby, and access is automatically cut / the device secured when the key goes out of range — proximity is the gate in both directions.

Possible additional independent claims (UNVERIFIED)

The specification and family materials describe two additional subject areas that may correspond to further independent claims in the '640 (a method counterpart and a tracking claim directed to a tracking server that logs reader-reported PDK location information in a location log for display). I could not verify whether the '640 itself contains a tracking independent claim or a method independent claim, or their claim numbers. The record's prior sections refer to a 20-claim set (claims 1–20), which is consistent with claim 1 + several dependents, and claim 17 + several dependents, with possibly one or two more independents. Do not rely on this paragraph as a claim-identification finding.

4. CAFC 2026 docket check — nothing names the '640

Searching the Federal Circuit dockets for Proxense's 2025–2026 appeals, every identified appeal concerns other Proxense patents, not US 11,095,640:

The 2026 appellate activity — Proxense's opening brief arguing the PTAB abused its discretion by staying the parallel ex parte reexamination 90/015,052 — arises from the '954 IPRs (Microsoft v. Proxense), not from any proceeding on 11,095,640. (ip fray, "PTAB abused discretion by staying reexamination that favored patentee, Proxense tells Federal Circuit"; dockets Proxense, LLC v. Microsoft Corp., No. 26-1025; Proxense, LLC v. Apple Inc., No. 25-2168.)

Conclusion on the CAFC check: as of the date of this analysis, no Federal Circuit docket names US 11,095,640. The '640 has never had a PTAB final written decision, so there is no appeal from which one could arise (consistent with the PTAB section of this record).

5. Uncertainty / what I could not verify

1. Verbatim claim language. The authoritative record is truncated before the claims. I have exactly one verbatim claim limitation (claim 17, element [17.1(b)]) and no verbatim text for claim 1 or any other claim. My claim-1 description is reconstructed from the patent's own Abstract, not quoted.
2. Independent-claim count and numbering. I could not confirm how many independent claims the '640 has, or which numbers they occupy. The "claim 1 = auto-login, claim 17 = proximity-gated access" mapping is a reasonable inference, flagged as such.
3. Claim count. The 20-claim figure appears only in the earlier sections of this record; I could not independently re-verify it.
4. Do not conflate family members. Materials returned during this search included substantially identical specifications under different patent numbers (e.g., US 11,132,882; US 10,217,339; US 10,171,460; US 9,807,091; US 9,418,205; and later continuations US 12,056,558 / US 12,238,092). Those are separate patents sharing the same 2010 priority family and are not US 11,095,640. Per the operating rules I have not substituted them.
5. Litigation status. The only district-court assertion naming the '640 is Proxense, LLC v. Hyundai Motor Co. et al., No. 6:25-cv-00016 (W.D. Tex.), which the record describes as voluntarily dismissed in April 2025. I did not re-verify a live docket in this session.

Bottom line: US 11,095,640 B1 is a 2021-issued Proxense (Giobbi) continuation, priority 2010-03-15, claiming a PDK-based system that auto-logs a user into applications/data via a proximity reader and an auto-login server, and — per asserted claim 17 — that gates and automatically terminates/secures access based on proximity. No CAFC 2026 docket names this patent.

I'll research litigation involving US Patent No. 11095640 across patent litigation databases.

Let me dig into the specific litigation references — the Texas Western District Court case and the Hyundai assertion mentioned.

I found the key case. Let me verify the current status and check whether the '640 patent appears in other Proxense cases.

Litigation Involving US Patent No. 11,095,640

Short answer: I found one district-court case in which US 11,095,640 ("the '640 patent") was asserted. It has been terminated by voluntary dismissal. I found no CAFC appeal, no PTAB proceeding (IPR/PGR), and no ITC action naming the '640 patent.

Case: Proxense, LLC v. Hyundai Motor Company et al.

The '640 patent's role in that case. It was one of four patents-in-suit, alongside U.S. Patent Nos. 10,073,960; 9,251,332; and 9,450,956. The complaint attached the '640 patent as Exhibit 4 and recited its issuance date (August 17, 2021) and title. Proxense alleged infringement of at least claim 17 of the '640 patent, targeting Hyundai/Kia/Genesis vehicles incorporating Car Connectivity Consortium (CCC) "Digital Key" technology (NFC / BLE / UWB) and associated OEM servers — specifically the proximity-based grant of access and automatic logout/securing when the device exceeds a defined proximity. (Compl. ¶¶ 26–27, 31, 87–89.) The complaint described the four patents as not standard-essential and not subject to FRAND commitments.

Corroborating sources

• Google Patents page for US11095640B1 (lists the W.D. Tex. litigation link to case 6:25-cv-00016 and the Darts-IP family 44559428 litigation flag).
• Unified Patents PATROLL contest page: "The patent is owned by Proxense LLC… The patent has been asserted against Hyundai." Unified also ran a prior-art contest ($2,000/$3,000) on claim 17 of US-11095640-B1.
• Docket records (dockets.justia.com / PACER Monitor): Proxense, LLC v. Hyundai Motor Company et al, 6:2025cv00016, filed January 14, 2025; voluntary dismissal April 14, 2025.

Items I should flag for caution

• No separate case number for a refiling. Because the Hyundai action was voluntarily dismissed in April 2025, a re-filed action is possible, but I did not find a confirmed second case number or a live docket for the '640 patent. Treat any refiling as unverified until confirmed on PACER.
• Do not conflate the '640 patent with similarly numbered patents. Proxense asserted other patents (e.g., 9,450,956 — the "'956 patent") against Hyundai and LG, and asserted U.S. 8,352,730 etc. against Samsung, Microsoft, and Google. Those cases do not involve 11,095,640. I found no assertion of the '640 patent against LG, Samsung, Google, Microsoft, Apple, or any other party.
• No PTAB proceeding found for the '640 patent. The PATROLL contests were crowdsourced prior-art hunts, not filed IPRs; I found no IPR/PGR petition on US 11,095,640. (By contrast, the PTAB did invalidate two other Proxense patents in the Microsoft dispute — not the '640 patent.)

Bottom line: The only known litigation involving US 11,095,640 is Proxense, LLC v. Hyundai Motor Company et al., No. 6:25-cv-00016 (W.D. Tex., filed Jan. 14, 2025), which was voluntarily dismissed on April 14, 2025. No other litigation, appeal, or PTAB challenge on this specific patent was found.

I'll start by verifying the structured block's "no proceedings" default against live sources.

The search surfaced significant Proxense IPR activity across the family — but I need to confirm whether any petition targets 11095640 specifically.

Let me pin down whether any IPR petition names the '640 patent, and identify the patents in the Intel v. Proxense IPRs.

PTAB Proceedings — US 11,095,640 B1 ("Proximity-Based System for Automatic Application or Data Access and Item Tracking")

Assignee: Proxense, LLC · Inventor: John J. Giobbi · Filing date: 2018-11-26 · Issued: 2021-08-17 · Priority date: 2010-03-15 · Adjusted expiration: 2031-08-02

Proceedings overview

Zero (0) AIA trial proceedings are on file against US 11,095,640. The structured USPTO Open Data Portal block reports no IPR, PGR, or CBM for this patent, and my web searches surfaced no petition, institution decision, FWD, or termination naming the '640 patent — so the breakdown is 0 active / 0 invalidated / 0 sustained / 0 settled / 0 institution-denied. The bottom-line defensive posture for a defendant is therefore unusual and favorable in a narrow sense, but not a validity win: the patent has never been tested at the PTAB, so claims 1–20 (including asserted claim 17) remain fully live and presumptively valid. The absence of an IPR is a vulnerability signal in the opposite direction — this is a patent that a well-funded NPE is actively asserting while a defensive aggregator (Unified Patents / PATROLL, co-sponsored by CNCF) has been publicly hunting prior art on claim 17 since 2025-06-27, meaning an IPR petition is a live possibility rather than a historical fact.

⚠️ Do not confuse this patent with its family members. Proxense is one of the most-IPR'd NPE portfolios in the country, and press coverage routinely blurs the patents together. The petitions below are real, but they target other Proxense patents, not the '640. Treating a family-member FWD as binding precedent for the '640 is a serious analytical error — different claims, different specification support, and no claim-preclusive effect.

Proceedings on US 11,095,640

None. No proceeding number exists to report, and per the operating rules I will not invent one.

Family-adjacent activity you must know about (NOT proceedings on the '640)

I'm listing these strictly as context and as a leading indicator — none of them is a proceeding on US 11,095,640.

Litigation driving the interest

• Proxense, LLC v. Hyundai Motor Company, Hyundai Motor America, Genesis Motor America LLC, Kia Corporation, Kia America, Inc., No. 6:25-cv-00016 (W.D. Tex., Judge Alia Moses), filed 2025-01-14. The complaint asserts four patents — the '960, '332, '956, and the '640 — and asserts at least claim 17 of the '640. The accused functionality is proximity-based vehicle access: access granted when the smart device is nearby, secured/logged out when the device exceeds a defined proximity.
• Per Unified Patents' PATROLL page, "The patent has been asserted against Hyundai." Unified's separate '956 contest notes the "'956 patent had been asserted against Hyundai."

Defensive-aggregator activity on THIS patent (the key signal)

• PATROLL contest — "Proxense: US-11095640-B1 (Authenticating Users to Access Data)," sponsored by Unified Patents, co-sponsored by the Cloud Native Computing Foundation as part of the CNCF Cloud Native Heroes Challenge.
  • Prize: $3,000 · Start: 2025-06-27 · End: 2025-08-12 · Status: ended, winner announced 2025-09-25.
  • Stated target: "Unified is seeking prior art on at least claim 17 of US-11095640-B1."
  • Key finding: the winning reference is Cihula (proximity-based access control with key device, sensors, encrypted unique ID + timestamp, automatic logoff on leaving range), charted against De La Huerga as a secondary reference. Unified published the chart at https://www.unifiedpatents.com/s/PATROLL_Proxense-US11095640_Claim-Chart.pdf.
  • Why this matters: Cihula/De La Huerga is a § 102/§ 103 combination that has never been before the Board on the '640. It is exactly the art a defendant would want, and it is now public and pre-packaged.

Petitions on sibling patents (listed only to avoid miscitation)

• [Microsoft Corp.](/litigations/by-plaintiff/Microsoft%20Corp.) v. Proxense, LLC, IPR2024-00573 — U.S. 8,646,042. Panel: APJs Dang, McKone, Beamer. Oral hearing 2025-05-13; FWD 2025-08-04 holding claims 1, 5, 6, 8–11, 13, and 14 unpatentable under § 103 (Apple joined). Grounds pivoted on a mean-plus-function construction dispute that Petitioner conceded was "largely dispositive."
• Microsoft Corp. v. Proxense, LLC, IPR2024-00846 — U.S. 8,886,954. Panel: Dang, Turner, McKone. Instituted 2024-11-18 (all of claims 1–29 challenged); FWD determined claims 1, 2, 4, 5, 7–13, 15, 16, 18–24, and 26–29 unpatentable.
• Google LLC v. Proxense, LLC, IPR2024-00233 — U.S. 8,886,954 (institution granted); Apple Inc. v. Proxense, LLC, IPR2024-01334 (joined to -00233).
• Microsoft v. Proxense, IPR2024-00775 ('730), IPR2024-00776 / -01335 ('905), IPR2024-01327 ('954); Apple v. Proxense, IPR2024-01398 / -01399, -01485, -01486, IPR2025-00074 ('042, '730, '954, '289); Google IPR2024-00233, -00784, -01318 / -01319 / -01320 ('960); Samsung IPR2021-01349, -01438, -01444 (institution denied on the '730).
• Intel Corp. v. Proxense, LLC, IPR2025-00327, -00328, -00329 — patents 8,457,672 ('672), 8,219,129 ('129), and 9,265,043 ('043) — not the '640. Discretionary denial 2025-06-26 (Paper 12) under the "settled expectations" doctrine: patents in force over nine years, no persuasive reason shown for Board resources. Acting Director Stewart's guidance (significant change in law, or non-commercialization/non-assertion in the petitioner's technology space) is now the roadmap for older-portfolio challenges.
• A Proxense v. Apple / Microsoft Federal Circuit appeal is pending, with an appellate opening brief dated 2026-04-03, arising out of the '954/'042/'289/'960 IPRs. Proxense is arguing, among other things, that the PTAB improperly stayed ex parte reexam 90/015,052 and then disregarded the CRU's contrary determinations.

Strategic summary

Claim status on the '640. Every claim — 1 through 20, independent and dependent, including asserted claim 17 — is UNTESTED and, as of today, UN-CANCELED. No claim of the '640 has been invalidated by any tribunal, so there is no "claims 1–5 are dead, ignore the demand letter" argument available here. Conversely, there is no "the patent survived two IPRs and is hardened" argument either, because the patent has never faced one. What you have is a 2021-issued patent with a 2010 priority date, an active W.D. Tex. assertion, and a publicly-funded prior-art bounty that has already produced a Cihula-based chart against the very claim being asserted. The absence of PTAB activity is genuinely notable — patents asserted this aggressively usually draw petitions within 12–18 months of suit — and the most likely explanations are (a) defendants are pursuing district-court invalidity instead, (b) claim 17's proximity-logout limitation makes institution harder than the biometric-verification siblings, or (c) petitions are in preparation under the Intel "settled expectations" framework, where the fact that the '640 was issued only in 2021 (roughly five years, not nine-plus) materially improves the case for institution relative to the family members Intel lost on.

Estoppel landscape. Because no IPR was ever instituted on the '640, § 315(e)(2) estoppel does not attach to this patent at all. Google, Microsoft, Apple, Samsung, and Intel have all taken their shots at other Proxense patents; none of those estoppel rulings import to the '640. Practically, a defendant currently facing the '640 is unencumbered — every prior-art ground is available, including the Cihula/De La Huerga combination and any art that a sibling-case petitioner raised unsuccessfully or that the CRU sustained in the '052 reexam. One watch item: if a hypothetical petitioner were in privity with a prior petitioner on a sibling patent and the same art were asserted, Proxense would argue IPR estoppel by extension, but that argument is materially weaker where the patents and claims differ. Note also that the litigation-driven § 315(b) one-year bar is running for the Hyundai defendants from 2025-01-14 service — that clock expired on or about 2026-01-14 unless the case was dismissed without prejudice or service was later than the filing date.

Pattern signals. Proxense is a prolific and aggressive PTAB appellant — it fought the '954 and '042 IPRs through to FWD and is now pressing a Federal Circuit appeal that attacks the Board's handling of parallel reexamination, which tells you the patent owner litigates rather than folds. There is no settlement pattern visible in the family; these cases go to FWD. The defensive aggregator presence is real and specifically aimed at the '640: Unified Patents ran a PATROLL contest co-sponsored by CNCF targeting claim 17, which is the standard precursor to a Unified-filed or Unified-funded IPR. If Unified files, the petitioner will be a proxy with no § 315(b) clock of its own and no exposure to the Hyundai case.

Recommended next steps

1. Do not treat the empty PTAB record as a validity finding. It is a gap, not a win. If you are the Hyundai/Kia/Genesis defendant or a similarly-situated target, your invalidity case must be built in district court, and the strongest available footing is the public Cihula/De La Huerga chart produced through the Unified/CNCF PATROLL campaign (published 2025-09-25 at https://www.unifiedpatents.com/insights/2025/9/25/3000-awarded-for-cloud-native-heroes-challenge-prior-art-found-on-proxense-640; chart PDF at https://www.unifiedpatents.com/s/PATROLL_Proxense-US11095640_Claim-Chart.pdf). Verify the chart independently — PATROLL submissions are not examiner- or Board-vetted, and prosecution-cited art was expressly excluded from consideration.
2. If you still have an open § 315(b) window (i.e., you were served after ~2026-01-14, or served later than the complaint filing date), an IPR on the '640 is worth pricing out now. The Intel framework is your friend here: the '640 issued in 2021, so the "settled expectations" bar that killed IPR2025-00327/328/329 does not straightforwardly apply, and Unified's PATROLL listing supplies the non-commercialization "otherwise applied" argument.
3. Verify the Hyundai posture before relying on it. The docket was last retrieved 2025-02-25 and at least one aggregator lists 6:25-cv-00016 as closed; that could mean settlement, dismissal, or simply stale data. A settlement would not affect PTAB estoppel (none exists), but it would affect the § 315(b) analysis and the identity of any real party in interest.
4. Bracket the family-wide exposure. If a counterparty is asserting more than one Proxense patent against you, the '954, '730, '042, '289, '960, and '905 have now been invalidated in whole or in substantial part at the Board — check the FWDs at PTAB E2E (https://ptacts.uspto.gov/) and the Federal Circuit docket for the pending Proxense v. Apple/Microsoft appeal before assuming any of those patents still has teeth. The '640 is the outlier that has not been touched.

Confidence note: I could not locate any PTAB proceeding naming US 11,095,640 in searches of PTAB dockets, Law360, Docket Alarm, or Unified Patents' case pages. My search coverage is not a substitute for a live PTAB E2E / USPTO PatentCenter docket pull, and I was unable to complete a final confirmatory query. Treat "no PTAB activity" as the well-supported default per the structured data, but run the docket yourself before filing anything that depends on it.

I'll research this patent's ownership chain, litigation, and any NPE associations before drafting the analysis.

Let me dig into the specific assignment record and Proxense's corporate history.

Let me try to pin down the specific assignment reel/frame and correspondent of record for this patent.

Ownership & NPE Analysis — US 11,095,640 B1

Patent: US 11,095,640 B1 — "Proximity-based system for automatic application or data access and item tracking"
Application: 16/200,580 · filed 2018-11-26 · granted 2021-08-17 · earliest priority 2010-03-15 (continuation family)
Assignee of record: Proxense, LLC (Bend, OR)

Verification note: I pulled the patent full text, the Google Patents legal‑events record, the W.D. Tex. docket for the flagged case (6:25‑cv‑00016), PTAB/assignment extracts from related Proxense filings, and Unified Patents / ip fray coverage. I could not directly query assignmentcenter.uspto.gov from this session, so the reel/frame for this specific patent is reported as unconfirmed rather than guessed.

Inventors

• Giobbi is the founder/CEO of the assignee itself, so there is no "inventor departs the assignee" pattern here — he is the assignee's control person. (Contrast the sibling Personal Digital Key Initialization family, US 10,374,795, which lists Giobbi + David L. Brown + Fred S. Hirt — but that is a different patent, not this one.)
• Giobbi has been publicly identified as Proxense's CEO continuously from 2001 through the 2026 ip fray interview, so no inventor‑departure fire‑sale tell.

Original assignee

Proxense, LLC — 689 NW Stonepine Dr, Bend, OR 97701 (mailing address of record: 1120 NW Couch St, 10th Fl, Portland, OR 97209).

• What it was: A genuine operating company. Founded 2001 by John Giobbi; from ~2004–2012 it developed proximity‑based wireless payment/authentication and asset‑tracking technology, shipped/licensed early deployments (e.g., a 2008 deal with casino‑systems vendor Bally Technologies to track chips, cash boxes and staff), and was covered as a product company in the Bend Bulletin and InformationWeek/DarkReading. The '640 specification is squarely its commercial subject matter (hospital auto‑login, equipment/patient tracking).
• Primary line of business today: Patent licensing/enforcement. ip fray describes Proxense as "a non‑practising entity (NPE) and former operating company" and quotes Giobbi: "Litigation has been the path we've had to take…" Unified Patents' portal classifies Proxense as "NPE (Small Company)."
• Current status: Operating as a licensing/assertion entity — entity is active on the Oregon registry (Entity 785675‑92, status ACT, registered agent Corporation Service Company, manager John Giobbi), not dissolved, and not in any disclosed bankruptcy.

Assignment timeline

USPTO assignment record for this patent is thin — effectively a single link. Google Patents' legal‑events record shows exactly one post‑filing assignment for 16/200,580:

• Executed 2018‑11‑26 to 2018‑12‑21 (execution date not independently confirmed) / recorded 2018‑12‑21 — Reel/Frame: not retrieved (see note)
  • Conveyance: Assignment of Assignors' Interest (inventor → company)
  • Assignor: Giobbi, John J.
  • Assignee: Proxense, LLC, 689 NW Stonepine Drive, Bend, OR 97701
  • Correspondent: Not confirmed for this specific record. Flagged pattern: on the sibling Proxense patent US 9,298,905 (same Giobbi/Proxense family), the recorded assignment (Reel/Frame 034843/0145, recorded 2015‑01‑29) carries correspondent Paige M. Alsbury, 201 S. Main Street, Suite 250, Salt Lake City, UT 84111. That is a single appearance in a different patent's chain — I am not counting it as a repeat‑correspondent finding for the '640 chain, because I could not confirm the '640 correspondent.
  • Context: Routine inventor‑to‑company assignment. The assignee is the same operating company that filed the application — i.e., this is not a third‑party transfer; it perfects Proxense's title to its founder's invention.

A note on the reel/frame: Google Patents' event log for this patent (fetched 2026‑09‑18) reports the 2018‑12‑21 assignment but does not expose a reel/frame in the text I retrieved, and I could not complete a direct Assignment Center lookup in this session. I am therefore not fabricating a reel/frame number. Operators should confirm it at the Assignment Center (link in Verdict) — but note the substantive finding stands regardless: no post‑issuance sale, no transfer to a separate NPE vehicle, no change of assignee appears anywhere in the record.

No other recorded assignments were found (no security agreements, no mergers, no name changes, no releases). The chain of title terminates at Proxense, LLC — the original applicant/assignee.

Timeline diagram

timeline
    title Ownership of US 11095640
    2001 : Proxense LLC founded by Giobbi
    2010 : Earliest priority application filed
    2018 : Continuation filed by Proxense LLC
         : Giobbi assigns rights to Proxense
    2021 : Patent US 11095640 issued
    2025 : Asserted against Hyundai in W D Texas

NPE / troll-pattern signals

1. Shell-entity transfer — NOT PRESENT.
   No transfer ever occurred. The only recorded assignment (2018‑12‑21) runs Giobbi → Proxense, LLC, the original operating applicant — not to a "…IP Holdings / Licensing / Ventures" vehicle. There is no successor LLC in the chain. (Weak/ambiguous tell only: Proxense's Oregon registered agent is Corporation Service Company, per OR entity 785675‑92 — but this is the same Oregon LLC that has existed since 2011/2001, not a fresh Delaware‑or‑Texas single‑purpose shell, so naming/agent evidence alone does not support a shell finding.)

2. Known asserter in the chain — PRESENT (moderate evidence).
   Proxense, LLC is not on the classic named list (Acacia/Marathon/IV/Wi‑LAN/Mosaid, etc.), but it is surfaced as a high‑frequency NPE plaintiff by the asserter‑tracking sources: Unified Patents' portal tags the patent owner as "NPE (Small Company)" (e.g., IPR2024‑00776, Microsoft v. Proxense), and ip fray states plainly that Proxense is "a non‑practising entity (NPE) and former operating company." Proxense is the plaintiff in the flagged W.D. Tex. suit 6:25‑cv‑00016 (filed 2025‑01‑14) asserting the '640 patent. This is the single strongest signal in the file.

3. Repeat correspondent across the chain — UNCLEAR / NOT PRESENT.
   Only one link exists, so recurrence cannot be established for this chain. A correspondent (Paige M. Alsbury) does recur in the sibling US 9,298,905 assignment (Reel/Frame 034843/0145, 2015‑01‑29), but a single appearance on a different patent is not a recurrence finding. Flagged for further checking if the '640 reel is retrieved and shows the same correspondent.

4. Cascading transfers — NOT PRESENT.
   No chained LLCs, no back‑to‑back assignments, no <24‑month cascade. The chain is one link.

5. Pre-litigation transfer — NOT PRESENT.
   The assignment is dated 2018‑12‑21; the first assertion naming this patent (against Hyundai) was filed 2025‑01‑14 — roughly six years later. That is the opposite of a 6‑month pre‑suit transfer to set venue/standing.

6. Bankruptcy fire‑sale — NOT PRESENT.
   No evidence of Chapter 7/11 proceedings for Proxense; assignee entity is active and the patent was never sold in a bankruptcy auction.

7. Privateering — NOT PRESENT.
   Classic privateering requires an operating company to hand patents to a separate NPE. Here there is no separate entity: the former operating company itself became the asserters, retaining title. That is a direct operating‑company‑to‑PAE conversion, not privateering by proxy, and no SEC/Patent‑Progress/EFF coverage of a privateering arrangement was found.

8. Defensive aggregator — NOT PRESENT.
   The chain does not terminate at RPX, AST, LOT, Unified, or OIN. The inverse posture is documented instead: Unified Patents ran a PATROLL bounty specifically against this patent ("Proxense: US‑11095640‑B1", $3,000 CNCF‑co‑sponsored contest, ended Aug/Sep 2025, seeking prior art on at least claim 17) — i.e., the defensive community is attacking this patent, not holding it.

Verdict

NPE — moderate confidence.

The assignment record is a clean single link (Giobbi → Proxense, LLC, recorded 2018‑12‑21) and terminates at the original applicant, so none of the transfer‑pattern tells (shell transfer, cascading LLCs, pre‑suit transfer, bankruptcy sale, privateering) are present — which is exactly why this is not "high confidence," despite the entity being a textbook NPE. What drives the call is a single strong signal: the current owner/plaintiff is affirmatively classified as an NPE by Unified Patents (portal: "NPE (Small Company)") and by ip fray ("non‑practising entity (NPE) and former operating company"), and it is running an active multi‑defendant assertion campaign in W.D. Tex. — including the flagged 6:25‑cv‑00016 (filed 2025‑01‑14, Proxense v. Hyundai/Kia/Genesis) asserting the '640 patent — with prior campaigns vs. Samsung, Google, Microsoft, Apple and LG. In short: the patent never moved to a shell; the operating company itself turned into the asserter. If the enumerated "known asserter in the chain" signal is weighted as strong, this is defensibly arguable as high confidence; I hold it at moderate pending retrieval of the '640 reel/frame and any correspondent recurrence.

Verify at USPTO Assignment Center: https://assignmentcenter.uspto.gov/ (search by patent number 11095640 or application 16/200,580); mirror index at https://assignment.uspto.gov/patent/index.html

Corroborating sources

• Google Patents legal events / assignee: https://patents.google.com/patent/US11095640/en
• First suit naming the '640: Proxense, LLC v. Hyundai Motor Co., No. 6:25‑cv‑00016 (W.D. Tex., filed 2025‑01‑14) — https://dockets.justia.com/docket/texas/txwdce/6:2025cv00016/1172820476
• Unified Patents portal (NPE classification): https://portal.unifiedpatents.com/ptab/case/IPR2024-00776
• Unified Patents PATROLL bounty on this patent: https://patroll.unifiedpatents.com/contests/JpdxJNu7FZE8pttdY
• ip fray, Proxense described as NPE / former operating company: https://ipfray.com/ptab-abused-discretion-by-staying-[reexamination](/resources/patent-reviews)-that-favored-patentee-proxense-tells-federal-circuit/
• Oregon entity record, Proxense LLC (785675-92), registered agent Corporation Service Company: https://www.city-data.com/business-entities/OR/PROXENSE-LLC-785675-92-OR.html

Caveats: (1) The '640 reel/frame is unconfirmed — do not treat any reel number for this patent as verified until pulled from Assignment Center. (2) The Paige M. Alsbury correspondent appears on a sibling patent's assignment (US 9,298,905, Reel 034843/0145), not on this one, and is reported here as context only. (3) The 2018‑12‑21 execution date vs. recording date was not independently separated.

I'll research the prior art citations for US 11,095,640 as they appear on the patent's face.

Let me pull the patent's front-page reference lists from multiple mirrors.

Let me retrieve the actual front-page "References Cited" lists for the '640 and its immediate parent.

Prior Art Analysis — US Patent No. 11,095,640 B1

Verification limitation (read first)

I was asked to walk "each patent citation" on the face of US 11,095,640. I must be straight with you: I could not retrieve the patent's own "(56) References Cited" block. The authoritative full text supplied in this record is truncated before the claims and before the front-page reference list, and my search budget expired mid-retrieval. I will not reconstruct a citation list from memory and present it as the face of the patent.

What follows therefore separates three tiers:

1. Art I can verify and that legally matters most — the references charted against claim 17 in the Unified/CNCF PATROLL campaign.
2. Art that demonstrably appears in the Proxense family's cited-record (retrieved from a same-family patent's face), which is what the '640's list is most likely to mirror.
3. Explicitly flagged inference.

One inference from the PATROLL rules is unusually valuable and I want to lead with it: the contest states that "prior art that has been previously cited during prosecution will not be considered." Because Cihula and De La Huerga were the winning submission, that strongly implies neither was before the examiner in the '640 prosecution — i.e., the two most relevant references are not on the patent's face. That is the single most important finding for your question.

1. Patent identification (literal)

Critical prior-art threshold: every reference must predate the effective filing date. Because the '640 is a continuation in a family running back to a 2010-03-15 provisional, references published before 2010-03-15 are the operative universe (pre-AIA § 102(b) statutory bar / AIA § 102(a)(1)). Anything later — e.g., US 9,276,914 B2 (Google, 2014 priority) — is not § 102 prior art against the '640.

2. Most relevant prior art (§ 102 anticipation candidates)

These are the references that actually bear on validity. All predate 2010-03-15 by six years or more, so all qualify as § 102(b) statutory-bar art.

Reference 1 — Cihula (Intel)

Reference 2 — De La Huerga '338

Reference 3 — De La Huerga '886

Reference 4 — De La Huerga '085

Reference 5 — Applicant's own incorporated family (disqualified as § 103 art, powerful as admissions)

The '640 specification expressly incorporates: Ser. No. 11/292,330; 11/620,581; 11/620,577; 11/744,832; 11/314,199 ("Biometric Personal Data Key (PDK) Authentication"); and 11/939,451 ("Tracking System Using Personal Digital Key Groups"). These describe the PDK, the receiver-decoder circuit, biometric PDK authentication, and PDK-group location tracking — the exact architecture claimed.

⚠️ Do not plead these as § 102/§ 103 art. They are commonly owned and (if qualifying only under pre-AIA § 102(e) / AIA § 102(a)(2)) are removed by the pre-AIA § 103(c) / AIA § 102(b)(2)(C) common-ownership exception. Their value is as applicant admissions about the state of the art and as corroboration.

3. Art reflected in the Proxense family's cited record

Retrieved from the face of a same-family patent (US 10,217,339, "Proximity-based system for object tracking and automatic application initialization"), and from a same-title continuation's reference list (justia, US 12,238,092). The '640, being a continuation, is likely to carry a substantially overlapping list — but I flag this as inference, not confirmation.

Representative entries (bibliographic data only; individual titles/fields not all independently verified):

• US 4,661,821 (Smith) — vandalism-resistant UHF antenna
• US 5,623,552 (Lane); US 5,886,634 (Muhme, G07C 9/00111); US 5,910,776 (Black); US 6,104,290 (Naguleswaran); US 6,325,285 (Baratelli) — access-control / identification art
• US 6,728,397 (McNeal); US 6,879,966 and US 7,565,329 (Lapsley); US 6,930,643 (Byrne); US 7,049,963 (Waterhouse, A01K 11/004); US 7,079,079 (Tibor); US 7,123,149 and US 7,349,557 (Bonalle / Tibor); US 7,231,068; US 7,314,164 — RF identification and tracking
• US 7,319,395 (Puzio); US 7,333,002 (Bixler); US 7,356,181 (Nowak); US 7,361,919 (Setlak); US 7,573,382 (Choubey); US 7,652,892 (Shiu); US 7,764,236 (Hill); US 7,943,868 (Anders) — biometrics, asset and personnel tracking
• US 7,961,078 (Reynolds, G06K 7/10297); US 8,026,821 (Reeder); US 8,081,215 (Kuo); US 8,082,160 (Collins); US 8,089,354 (Perkins, A61B 5/1113); US 8,193,923 (Rork); US 8,215,552 (Rambadri); US 8,248,263 (Shervey); US 8,258,942 (Lanzone); US 8,325,011 (Butler, G06K 7/0008) — RFID readers, location tracking, access control
• Same-title continuation list (US 12,238,092) additionally includes US 5,923,757 (Hocker); 5,928,327 (Wang); 5,942,985 (Chin); 5,991,749 (Morrill); 6,016,476 (Maes); 6,035,038 (Campinos); 6,038,334 (Hamid); 6,038,666 and 6,041,410 (Hsu); 6,042,006 (Van Tilburg); 6,052,468 (Hillhouse); 6,078,796 / 6,079,996 region; 6,104,290 (Naguleswaran) — payment, smartcard, and identification art.

Assessment: this family's cited art is overwhelmingly access-control, RFID-tracking, smartcard and biometric-verification material. It is generally § 103 combination fodder, not § 102 anticipation material, because it tends to disclose individual pieces (a badge reader, a tracking log, a biometric terminal) rather than the full proximity-gated-authentication-plus-automatic-application-launch combination of a single independent claim.

4. Claim-level § 102 mapping

Caveat: the claims were not available to me in this record. Mapping is anchored on the one claim-17 limitation I could recover verbatim and on the specification/abstract characterization of the claim families.

Key legal point: § 102 requires every limitation in a single reference. On the record I have, only Cihula plausibly anticipates an entire independent claim (claim 17). The rest is properly a § 103 case — which is precisely the ground already developed in the Obviousness section of this analysis (Cihula in view of De La Huerga, with motivation supplied by the resource-left-unlocked problem Cihula itself identifies).

5. Bottom line

• I could not pull the '640's own front-page "(56) References Cited" block. Treat any citation list presented to you as the face of US 11,095,640 as unverified unless pulled from USPTO Patent Full-Text or PatentCenter directly.
• The most relevant prior art is probably not on the patent's face. The PATROLL contest's express exclusion of prosecution-cited art, combined with Cihula + De La Huerga winning it, indicates those two references were not before the examiner on the '640.
• Highest § 102 value: Cihula (US 2004/0128500 A1 / US 7,178,034 B2) against claim 17.
• De La Huerga (US 2005/0091338 A1 / US 7,941,534 B2) is the key reference for the auto-login/auto-logoff family and for the departure-securing element.
• The family-cited art (Lapsley, Muhme, Waterhouse, Perkins, Reynolds, Bonallee/Tibor, etc.) is real but is § 103-grade — it maps to tracking and access-control elements individually, not to a complete independent claim.
• Verify every date and title on the face of each reference before relying on it; the per-reference dates above marked verify are from my retrieval and should be confirmed.

Confidence: High that US 11,095,640 B1 is the correct and only patent under analysis. High that Cihula and De La Huerga are the operative references. Moderate on the De La Huerga '886/'085 grant dates. Low/unverified: the '640's actual on-face citation list, which is the literal subject of your request and which I could not complete.

I'll research the prior art references relevant to US 11,095,640, including the PATROLL contest prior art and the references cited on the patent's face.

Let me retrieve the specific prior art references and the claim language.

Let me get the actual claim language for claim 17 and any other independent claims.

Obviousness Analysis — U.S. Patent No. 11,095,640 B1 under 35 U.S.C. § 103

Scope caveat (must be stated up front): The "full patent text" in the record is truncated before the claims, so I do not have the verbatim claim set in front of me. The analysis below is grounded in (a) the single verbatim claim limitation I could recover from the winning PATROLL chart — element [17.1(b)] — and (b) the specification's and litigation record's characterization of what the independent claims cover. I flag every place where I am inferring claim scope rather than quoting it. This is an analyst's obviousness opinion, not a legal conclusion, and it does not disturb the statutory presumption of validity.

1. The legal framework and the level of ordinary skill

Governing test (§ 103, Graham v. John Deere, 383 U.S. 1 (1966); KSR Int'l v. Teleflex, 550 U.S. 398 (2007)). The question is whether the differences between the claimed subject matter and the prior art are such that the subject matter as a whole would have been obvious at the time of the invention to a person having ordinary skill in the art ("POSITA"). Under KSR, a combination of known elements is obvious where the combination is "nothing more than the predictable use of prior art elements according to their established functions," and the motivation to combine need not be found expressly in a single reference — it may come from the nature of the problem, the field of endeavor, or common sense.

Effective filing / priority date. Per the record, the earliest priority date is 2010-03-15 (provisional 61/314,032). Whether pre-AIA or AIA § 102/103 applies to any given claim depends on the continuation chain and the 2013-03-16 AIA transition; that dispute does not matter to the primary references below, because each is a printed publication / patent published 6–8 years before 2010-03-15 and therefore qualifies as prior art under either regime (pre-AIA § 102(b) statutory bar; AIA § 102(a)(1)).

Level of ordinary skill (proposed). A POSITA here would be a person with a bachelor's degree in EE, CS, or a related field and ~2–4 years of experience, or equivalent, in short-range wireless authentication / RFID / access-control systems. The references below are all squarely within that person's field.

What the patent admits as known (helpful context). The specification's own "Definitions"/background sections characterize as conventional: (i) RFID-based proximity authentication generally ("in contrast to many conventional RF ID devices"); (ii) challenge-response/CHAP device authentication; (iii) biometric templates matched at a point of transaction; and (iv) the general problem of untracked hospital equipment. These are applicant admissions about the state of the art and narrow the distance the prior art must travel.

2. The challenged claim(s) and their limitations

2a. Claim 17 (independent — the claim Unified Patents targeted)

The PATROLL contest and the W.D. Tex. complaint both identified claim 17 as the key independent claim. The only limitation I can quote verbatim from the winning chart is:

"[17.1(b)] the personal digital key including a profile uniquely associated with a user authorized to use the device when the personal digital key is proximal to the device…"

From this and the chart's structure, claim 17 appears to be a system claim reciting at least:

• (A) a "device" (a target/controlled resource — e.g., a computing device or appliance);
• (B) a "reader"/sensor/wireless interface in communication with a personal digital key ("PDK");
• (C) a PDK including a profile uniquely associated with a user, where the user is authorized to use the device when the PDK is proximal to the device (i.e., proximity-gated authorization); and
• (D) at least one further element that the winning chart's second row (quoting De La Huerga) was used to meet — reading the chart, that element concerns enabling access while proximal and disabling/securing it when the device moves out of range (the chart pulled De La Huerga's "log the user off when he moves from the computer terminal beyond the limited range" passage for exactly this purpose). The Hyundai complaint's own infringement theory corroborates this: it described claim 17 as covering "proximity-based grant of access and automatic logout/securing when the device exceeds a defined proximity."

⚠️ I cannot confirm the exact number/order of limitations in claim 17, nor whether it includes express biometric limitations. The analysis is therefore organized around the limitations I can substantiate and is expressly conditional on the verbatim claim language.

2b. The auto-login independent claim(s) (per the specification/abstract)

The specification and abstract describe an independent claim set directed to:

a PDK storing a biometric profile and another profile; a reader that wirelessly receives the profile over a secure wireless channel; a computing device coupled to the reader; and an auto login server coupled to both that launches one or more applications associated with a user name identified by the profile.

2c. The tracking claim(s)

The specification describes claims directed to a tracking server that logs locations of PDK-associated users/equipment in a location log for display.

3. The prior art references

Reference A — Cihula (U.S. Pub. No. 2004/0128500 A1; issued as U.S. Pat. No. 7,178,034 B2)

"Method and apparatus for strong authentication and proximity-based access retention" (Cihula, Patel). Published 2004-07-01 — § 102(b) prior art.

What it discloses (as verified from the reference and the winning chart):

• A "secure asset grouping" (100) including a key device (400) carried by a user, sensors (112, 116) placed near "target resources" (110, 114), and an authentication agent (104) that "identifies users who request access to target resource(s)." (Cihula ¶¶[0015]–[0022].)
• The key device stores a unique ID used "to identify the user associated with the key device… used by control logic to determine whether or not the associated user is authorized." (Chart citing Cihula.)
• Proximity-based access control: the sensor "wirelessly communicate[s] with users' key devices that are near the resources"; the key device "communicates with the sensor… when [it] is close enough to [the sensor] for wireless communication to occur." (Chart at Cihula 3:22–30, 7:x.)
• A target resource(s) interface "through which control logic may selectively enable or disable access to target resources." (Cihula 4:47–50.)
• Session keys, timestamps, and encryption for strong authentication; sessions that end "when… the key device has left a certain area."
• Optional biometric/further verification (password, "thumb scan, a retinal scan, a voice print, or a facial comparison"). (Cihula ¶[0019].)

This reference alone discloses elements (A)–(C) of claim 17: a device/target resource, a wireless reader/sensor, and a PDK (key device) with a profile/ID authorizing use when proximal.

Reference B — De La Huerga (U.S. Pub. No. 2005/0091338 A1; issued as U.S. Pat. No. 7,941,534 B2)

"System and method to authenticate users to computer systems" (Carlos De La Huerga). Published 2005-04-28 — § 102(b) prior art.

What it discloses:

• A portable electronic security device that authenticates a user to a computer terminal/system and, once authenticated, logs the user on.
• The critical passage the winning chart relied on:

  "When the electronic security device has wireless communication that has a limited range (e.g. 3 m or less) it can be used to log the user off when he moves from the computer terminal beyond the limited range. To do this the computer terminal transmits signals addressed to the device on a periodic basis, which in turn transmits a response signal back… When the user leaves the area near the computer workstation… the response signals are no longer received by the computer terminal, which then logs the user off…" (De La Huerga at 12:22–42.)

De La Huerga supplies the proximity-gated logoff/secure-on-departure limitation (element (D)), and does so explicitly in the context of automatic login/logout of a workstation.

Additional/corroborating references

• De La Huerga, U.S. Pat. No. 6,346,886 — electronic identification apparatus (wristband-mounted transceiver with memory, lockdown on removal) — relevant to patient/asset PDK tracking claims.
• De La Huerga, U.S. Pat. No. 5,960,085 — "Security badge for automated access control and secure data gathering" — mobile transceiver + interrogator/recommitment signals, terminating access if recommitment response is missed — relevant to proximity time-out/logoff.
• The applicant's own earlier PDK work (cited in the '640 specification as incorporated by reference): U.S. Ser. No. 11/292,330 (now U.S. Pat. No. 9,613,483), Ser. No. 11/744,832, Ser. No. 11/314,199, and Ser. No. 11/939,451 ("Tracking System Using Personal Digital Key Groups"), and U.S. Pub. No. 2007/0260883. These describe, in the applicant's own words, a PDK, a receiver-decoder circuit, biometric PDK authentication, and PDK-group location tracking — i.e., the very architecture the '640 claims. ⚠️ Caveat: because these are commonly owned, they may be disqualified as § 103 prior art by the common-ownership exception (pre-AIA § 103(c) / AIA § 102(b)(2)(C)) if they qualify only under § 102(e)/(a)(2). They remain powerful evidence of the state of the art and of what the applicant itself considered conventional, and they should be treated as corroborating, not as standalone § 103 grounds.

⚠️ Prosecution-history caveat. PATROLL expressly excludes art "previously cited during prosecution." The winning chart used Cihula and De La Huerga, which strongly implies neither was before the examiner in the '640 prosecution — a relevant fact for any § 325(d) or Advanced Bionics analysis in a future IPR.

4. Obviousness combinations

Ground 1 — Claim 17: Cihula in view of De La Huerga

Where each limitation is met

Motivation to combine (why a POSITA would do it).

1. Same field of endeavor. Both references address the same problem — proximity-based authentication of a person to a controlled computer/electronic resource — and both are classified in access-control/computer-security art. A POSITA improving Cihula's secure asset grouping would naturally consult De La Huerga, and vice-versa.
2. Addressing a recognized deficiency in Cihula. Cihula's own text flags the problem that a card-based system can leave a resource unlocked ("users may forget to remove their card from the reader when they are done"). De La Huerga's automatic-logoff-on-departure is a known, ready solution to precisely that problem. KSR sanctions exactly this "known technique to improve similar devices in the same way."
3. Predictable combination of known elements with established functions. Cihula already contemplates sessions ending "when the key device has left a certain area"; substituting/supplementing Cihula's session-ending logic with De La Huerga's periodic-interrogation-then-logoff mechanism is the predictable use of a known element for its established function.
4. Reasonable expectation of success. Both use conventional short-range wireless signaling and a security server; no new hardware or untested principle is required. There is no teaching away — De La Huerga's 3 m range and Cihula's adjustable proximity zone are compatible, adjustable parameters.
5. Design incentive / market pressure. The '640 specification itself states the motivation: eliminating "the constant and time-consuming login and logout of healthcare providers" while preserving "application or data security."

Result: The combination of Cihula and De La Huerga discloses every limitation of claim 17 as I can recover it. If claim 17 includes a biometric limitation, see Ground 2.

Ground 2 — Claim 17 (+ any biometric limitations): Cihula + De La Huerga + a biometric-PDK reference

If claim 17 (or a dependent claim) requires a biometric profile stored on the PDK and/or a reader-acquired biometric input compared to that profile, add:

• Cihula itself discloses "further verification, such as… a thumb scan, a retinal scan, a voice print, or a facial comparison" (¶[0019]) — biometrics at the reader for authorization; and
• The applicant's earlier biometric-PDK applications (Ser. No. 11/314,199, "Biometric Personal Data Key (PDK) Authentication"; and U.S. Pub. No. 2007/0260883) describe storing a biometric profile in the PDK's tamper-proof memory and differentiating among multiple PDKs by distance/location/duration metrics.

Motivation: Biometrics for "strong authentication" was a recognized, well-documented tool (Cihula calls its system "strong authentication"). Moving the biometric template onto the personal token to avoid a central database of biometrics — as the applicant's own prior filings did — is a predictable design choice, and the '640 specification itself frames it as a benefit ("personal biometric information need not be stored in any local or remote storage database"). Combining the fine-grained biometric verification of the PDK references with the proximity/logoff framework of Cihula + De La Huerga is a mere substitution of one known authentication factor for another, with predictable results.

Ground 3 — Auto-login claim(s): De La Huerga + Cihula (+ biometric PDK reference)

For the claim set reciting "PDK + reader + computing device + auto login server that launches applications associated with a user name":

• De La Huerga discloses automatic logon/logoff of a workstation based on the presence/absence of the security device, including re-establishing access "within a time range."
• Cihula supplies the key-device + sensor + authentication-agent architecture (the "server" analog) and session/key management.
• A biometric PDK reference (Cihula ¶[0019]; applicant's Ser. No. 11/314,199) supplies the biometric profile.

Motivation: De La Huerga expressly targets the "constant and time-consuming" manual logon problem (its own background discusses physicians' cumbersome terminal access) — the identical problem the '640 auto-login claims purport to solve. A POSITA seeking single-sign-on / proximity auto-login would combine De La Huerga's logon/logoff mechanism with Cihula's authenticated key-device architecture as a predictable improvement. The "auto login server" is merely the logical locus for centralized credential handling already suggested by Cihula's authentication agent and De La Huerga's "computer network [that] maintains the reauthentication code."

Ground 4 — Tracking claim(s): Cihula/De La Huerga + a proximity-tracking reference

The tracking claims (tracking server + location log + display of PDK locations) are largely a data-aggregation overlay on the same reader/PDK infrastructure. De La Huerga's '886 wristband apparatus and '085 security-badge system, plus the applicant's own Ser. No. 11/939,451 ("Tracking System Using Personal Digital Key Groups," which the '640 specification incorporates), disclose associating a tracked person/object with a wireless identifier and logging/transmitting its location. Combining known location-logging with Cihula's fixed sensors at known positions is the predictable use of a known technique (RF location logging) for its established purpose.

5. Secondary considerations (§ 103 rebuttal factors)

I found no evidence of unexpected results, long-felt-but-unsolved need, industry praise, copying, or licensing in the record. Two points to watch:

• Nexus. Any asserted commercial success must have a nexus to the claimed subject matter. Here the core functional elements (proximity-gated access + auto logoff/logon + RFID identification) are old, which weakens any nexus argument.
• Family litigation posture. The Board's July 2025 IPR decision in Microsoft v. Proxense — holding challenged claims of a different Proxense patent (the PDK/RDC "hybrid device" family) obvious over a "two-level authentication" reference, a "digital content security system," and an NFC-memory reference — signals that the PTAB reads this technology space broadly and is receptive to multi-reference obviousness theories against Proxense's portfolio. That decision is not precedent on the '640 patent but is informative about how a POSITA's knowledge in this field will be characterized.

6. Bottom line

• Claim 17 is vulnerable to § 103. Cihula (US 2004/0128500 A1 / US 7,178,034) alone supplies the proximity-gated PDK/target-resource authorization architecture, and De La Huerga (US 2005/0091338 A1 / US 7,941,534) supplies the specific proximity-based automatic logoff/logon element the chart was built around. The combination is a predictable use of prior-art elements for their established functions with a clear, articulated motivation (solving the "resource left unlocked / constant manual logout" problem both references identify). This is the same combination Unified Patents' winning PATROLL submission used to chart claim 17.
• The auto-login and tracking claims are likewise exposed to obviousness over De La Huerga (proximity auto-logon/logoff of workstations) in combination with Cihula's authenticated key-device architecture and the applicant's own earlier PDK/biometric/tracking disclosures.

Confidence / limitations on this opinion:

• High confidence: the identity and content of Cihula and De La Huerga, their prior-art dates, and that the combination was accepted by PATROLL as a full-limitation chart of claim 17.
• Moderate confidence: that claim 17 includes the automatic-secure-on-departure limitation and excludes express biometric limitations.
• Low confidence / not verified: the verbatim full text of claim 17, the total number and wording of independent claims, and the exact pre-AIA vs. AIA priority/§ 103(c) analysis for the applicant's own commonly-owned family. I did not have the authoritative claim set available. A final infringement/invalidity-grade opinion requires the issued claims and the full prosecution history (to confirm which references were/weren't before the examiner).