KeyMe, LLC v. The Hillman Group, Inc.
1:19-cv-01539
D. Del.Jan 25, 2021Background
- This is a claim-construction opinion in KeyMe, LLC v. The Hillman Group, Inc., concerning disputed terms in U.S. Patent No. 8,682,468 for self-service key-duplication systems (kiosks).
- The patent describes kiosks that capture geometric information of a key, receive security/user information, store identifying information, and create duplicate keys (by cutting or shaping).
- Parties disputed meanings of multiple claim terms including "kiosk," "security information," various "identifying information" phrases, a likely typographical error about which key's bit heights are determined, and whether certain steps require an active "recognizing" action versus passive receipt/verification.
- The Court relied on intrinsic evidence (claims and specification), claim-differentiation principles, and Federal Circuit/U.S. Supreme Court claim-construction authority; it also corrected an obvious claim typo under the CBT Flint/Novo standard.
- The Court generally refused to import limitations from specific embodiments (e.g., retail-floor deployment, "free-standing" kiosks, or a requirement that security information be unique/personal) and construed terms to encompass disclosed embodiments such as key cutters that use inventoried blanks.
Issues
| Issue | Plaintiff's Argument (KeyMe) | Defendant's Argument (Hillman) | Held |
|---|---|---|---|
| "kiosk" scope | Plain meaning; a self-contained device | Must be a "self-service, free-standing device for deployment on a retail floor" | "Kiosk" = device with a self-contained structure housing hardware, allowing key duplication without a skilled locksmith; not limited to retail or necessarily free-standing |
| "security information" | Plain meaning (information used for security) | Must be "unique information that is personal to a user" | "Information that is used for security"; not limited to unique or personal data |
| "[first/second/third] identifying information based on [first/second/fifth] security information" | Can be identical to received security information; may identify user or key | Must be derived from but not identical to security info and identify a user | Identifying information may be identical to or derived from security information and may identify a user or a key |
| "automatically determines bit heights...based on the [captured/second] geometric information about the second key" (typo) | Correct obvious typo so it refers to determining bit heights of the second key based on second-key data | Opposes rewriting claim language | Court corrects the obvious error: claim read to determine bit heights of the second key using geometric information about the second key (correction allowed under CBT Flint/Novo) |
| "[receives ...] security information ... corresponds to ... but not ..." | No separate "recognizing" step required beyond receiving/verification | Claims require an additional recognition step | No separate recognition step; receiving/verification language suffices |
| "[identifies] stored geometric information ... includes X but not Y" | Plain meaning; no separate recognition required | Requires recognition of inclusion/exclusion | No recognition step read in; claim limits that the stored geometric data include X and not Y |
| "verifies that the [X] security information corresponds to the [Y] identifying information" | Plain meaning (verify/confirm synonymous) | "Verify" implies a secondary confirmatory step after recognition | No construction necessary; court treated "verify" as ordinary meaning and rejected a separate-step requirement |
| "key shaping device" / "a shaping tool" | Broad: includes devices that duplicate keys by cutting inventoried blanks or shaping from stock | Narrow: "shaping" excludes cutters that merely cut blanks; requires shaping from raw stock and replication | "Key shaping device" and "shaping tool" include disclosed key-cutter embodiments that cut inventoried blanks; "shaping" not limited to non-cutting methods; no additional construction needed |
Key Cases Cited
- Teva Pharm. USA, Inc. v. Sandoz, Inc., 574 U.S. 318 (2015) (claim construction is a legal question but subsidiary factual findings receive deference)
- Markman v. Westview Instruments, Inc., 517 U.S. 370 (1996) (claims define the invention; courts construe claims)
- Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir. 2005) (framework for claim construction; use specification and intrinsic evidence)
- Vitronics Corp. v. Conceptronic, Inc., 90 F.3d 1576 (Fed. Cir. 1996) (specification is the best guide to claim meaning)
- O2 Micro Int'l Ltd. v. Beyond Innovation Tech. Co., 521 F.3d 1351 (Fed. Cir. 2008) (construe terms when parties dispute scope)
- Liebel-Flarsheim Co. v. Medrad, Inc., 358 F.3d 898 (Fed. Cir. 2004) (do not import limitations from specification absent clear intent)
- CBT Flint Partners, LLC v. Return Path, Inc., 654 F.3d 1353 (Fed. Cir. 2011) (standard for correcting an obvious claim error)
- EPOS Techs. Ltd. v. Pegasus Techs. Ltd., 766 F.3d 1338 (Fed. Cir. 2014) (a claim construction that excludes a preferred embodiment is rarely correct)