Browse Prior Art Database

3D printed keys authorization

IP.com Disclosure Number: IPCOM000248960D
Publication Date: 2017-Jan-24
Document File: 2 page(s) / 30K

Publishing Venue

The IP.com Prior Art Database

Abstract

Nowadays almost every security system is digital. It is good and bad solution at the same time. Bad is that there are no digital solution that can’t be broken at some point. In this publication we propose solution of access keys that will connect mechanic and digital world, creating unhackable protection.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

1

3D printed keys authorization

We are proposing usage of 3D printed keys, on which there will be printed some code (for example special version of QR Code). Idea is to create 2 identical keys at the same time. One will stay in special container in the institution, second one will be held by customer. Institution and customer is just example, which can help illustrate the idea. When customer comes to institution, to access his, i.e. money, he will put his key into special scanner. In the same time, key held by institution would be picked up from container and those 2 keys will be scanned in the same moment, mm by mm, verifying if they are identical. Memory about look of those keys should be cleaned right after every mm of key is scanned, to avoid leak of that information. Such solution creates protection that can’t be stolen through hacking!

First of all such key would have to be 3D printed. Schema of key would be like this:

We are proposing size of this key to be in the same size as normal keys (height ~5-10cm, width ~4cm, not more than 1cm thick). On the “feet” of the key there would be unique ID of the key, which will be only value stored in computer system, handling keys. On the head of the key, there will be 3D code (for example QR code, with added 3D add ons), which is represented by star on the schema above. During creating for example account for customer in bank, there will be created 2 identical keys with randomly generated ID and code. First one will be given to customer, second one will be stored in special rack.

In computer system there will be only one information and it only stored – Key ID and its localization in rack, so machine will be able to find it. Suck rack could look inside like on this schema:

Keys in this rack (which should have appropriate size) could be stored in rows, so machine will be able to quickly find coordinates of...