# US 12,002,314 B2 · Authentication of Internet of Things devices, including electronic locks > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,002,314 B2 - Document ID: US12002314B2 - Status: Granted - Kind: B2 - Application number: 17/276,068 - Filed: 2019-09-13 - Published: 2022-02-17 - Granted: 2024-06-04 - Earliest claimed: 2018-09-14 - Assignees: ASSA ABLOY Americas Residential Inc. - Applicants: ASSA ABLOY Americas Residential Inc. - Inventors: James Creighton Hart; Derek Imanuel - Web page: https://patentgrep.com/patent/US12002314B2 ## CPC - G07C 9/00571: {operated by interacting with a central unit} - H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)} - G07C 9/00309: {operated with bidirectional data transmission between data carrier and locks} - G07C 9/0069: {actuated in a predetermined sequence} - H04L 63/0869: {for achieving mutual authentication (cryptographic mechanisms or cryptographic arrangements for mutual authentication H04L9/3273)} - H04W 4/80: Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication - H04W 12/03: Protecting confidentiality, e.g. by encryption - H04W 12/0431: Key distribution or pre-distribution; Key agreement - H04W 12/069: using certificates or pre-shared keys - H04W 12/50: Secure pairing of devices - G07C 9/00563: {using personal physical data of the operator, e.g. finger prints, retinal images, voicepatterns} - G07C 2009/00388: {code verification carried out according to the challenge/response method} - G07C 2009/00412: {the transmitted data signal being encrypted} - G07C: TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract Methods and systems for authenticating an Internet of Things device, such as an electronic lock, are disclosed. One method includes generating a first challenge at a server; transmitting the first challenge to the Internet of Things device; receiving a first signed certificate from the Internet of Things device, the first signed certificate being the first random number challenge signed with a private key associated with the internet of things device; and verifying the first signed certificate with the first challenge and a public key associated with the Internet of Things device. Mutual authentication of the server from the Internet of Things device is also provided. ## Claims ### Claim 1 A method of authenticating an Internet of Things device comprising: verifying a device certificate received from the Internet of Things device is valid and created based on a root certificate associated with a manufacturer of the Internet of Things device; after verifying the device certificate, generating a first challenge at a server; transmitting the first challenge to the Internet of Things device; receiving a first response from the Internet of Things device, the first response being signed with a private key of the Internet of Things device; and verifying the first response with the first challenge and a public key associated with the Internet of Things device, wherein secured data communication between the Internet of Things device and the server is enabled based at least in part on successful verification of the device certificate and the first response. ### Claim 2 (depends on 1) The method of claim 1, further comprising: receiving a second challenge from the Internet of Things device; responding to the second challenge to produce a second response, the second response being signed with a private key of the server; transmitting the second response to the Internet of Things device; and receiving confirmation of authentication from the Internet of Things device. ### Claim 3 (depends on 1) The method of claim 1, wherein the Internet of Things device is an electronic lock. ### Claim 4 (depends on 1) The method of claim 1, wherein the transmitting occurs via a mobile device in data communication with both the Internet of Things device and the server. ### Claim 5 (depends on 4) The method of claim 4, wherein the mobile device is in data communication with the Internet of Things device via a Bluetooth connection. ### Claim 6 (depends on 4) The method of claim 4, wherein the mobile device is in data communication with the server via a Wi-Fi connection. ### Claim 7 (depends on 1) The method of claim 1, wherein the transmitting occurs directly between the Internet of Things device and the server via a wireless network connection. ### Claim 8 (depends on 1) The method of claim 1, further comprising: before generating the first challenge, receiving an authentication request from a mobile device, the mobile device being associated with a user account; and authenticating and establishing a data connection with the mobile device, the mobile device also being in data communication with the Internet of Things device. ### Claim 9 (depends on 8) The method of claim 8, wherein the device certificate received from the Internet of Things device is validated at the server against a certificate issued by the manufacturer of the Internet of Things device. ### Claim 10 (depends on 1) The method of claim 1, wherein the first challenge comprises a first random number challenge. ### Claim 11 (depends on 1) The method of claim 1, wherein the first response is the first challenge signed with the private key associated with the Internet of Things device. ### Claim 12 (depends on 2) The method of claim 2, wherein the second response is the second challenge signed with the private key associated with the server. ### Claim 13 A method of authenticating data communication between an electronic lock and a server comprising: generating, at the electronic lock, a lock certificate based at least in part on a manufacturer root certificate of a manufacturer of the electronic lock; transmitting the lock certificate to the server; after the lock certificate is verified at the server, generating a random number challenge at the electronic lock; transmitting the random number challenge to the server; receiving a signed certificate from the server, the signed certificate being based on the lock certificate and signed with a private key associated with the server; verifying the signed certificate with the random number challenge and a public key associated with the server; signing a second random number challenge received from the server at the electronic lock; and transmitting the signed second random number challenge to the server, wherein the signed second random number challenge is verified at the server; wherein secured data communication between the electronic lock and the server is enabled based at least in part on successful verification of the lock certificate, the signed certificate, and the signed second random number challenge. ### Claim 14 (depends on 13) The method of claim 13, wherein transmitting the random number challenge to the server comprises transmitting the random number challenge to a mobile device for forwarding to the server. ### Claim 15 (depends on 13) The method of claim 13, wherein verifying the signed certificate comprises decrypting the signed certificate using a public key of the server at the electronic lock. ### Claim 16 A method of authenticating data communication between an electronic lock and a cloud server comprising: receiving, at a mobile device, a lock certificate from the electronic lock, the lock certificate being based at least in part on a manufacturer root certificate of a manufacturer of the electronic lock; transmitting the lock certificate from the mobile device to the cloud server; at the mobile device, requesting a first challenge from the electronic lock to authenticate the cloud server; communicating, with the mobile device, the first challenge from the electronic lock to the cloud server; communicating, with the mobile device, a first signature result from the cloud server to the electronic lock, the first signature result being signed with a private key of the cloud server; at the mobile device, requesting a second challenge from the cloud server to authenticate the electronic lock; communicating, with the mobile device, the second challenge from the cloud server to the electronic lock; and communicating, with the mobile device, a second signature result from the electronic lock to the cloud server, the second signature result being signed with a private key of the electronic lock, wherein secured data communication between the electronic lock and the cloud server is enabled based at least in part on successful verification of the lock certificate, the first signature result, and the second signature result. ### Claim 17 (depends on 16) The method of claim 16, wherein, based on the first signature result and the second signature result, communication is enabled between the electronic lock and the cloud server. ### Claim 18 (depends on 17) The method of claim 17, wherein, upon authenticating the cloud server at the electronic lock and authenticating the electronic lock at the cloud server, the electronic lock is enabled to communicate with the cloud server via a Wi-Fi connection without requiring intermediation by the mobile device. ### Claim 19 An electronic lock comprising: a latch movable between a locked position and an unlocked position; a motor operatively connected to the latch and configured to drive the latch between the locked position and the unlocked position; at least one wireless communication interface; and a programmable circuit configured to selectively actuate the motor and communicate with a server regarding a status of the electronic lock, the programmable circuit configured to perform an authentication process comprising: generating, at the electronic lock, a lock certificate based at least in part on a manufacturer root certificate of a manufacturer of the electronic lock; transmitting the lock certificate to the server; after the lock certificate is verified at the server, generating a random number challenge at the electronic lock; transmitting the random number challenge to the server via the at least one wireless communication interface; receiving a signed certificate from the server, the signed certificate being based on the lock certificate and signed with a private key associated with the server; verifying the signed certificate with the random number challenge and a public key associated with the server; signing a second random number challenge received from the server at the electronic lock; and transmitting the signed second random number challenge to the server, wherein the signed second random number challenge is verified at the server; wherein secured data communication between the electronic lock and the server is enabled based at least in part on successful verification of the lock certificate, the signed certificate, and the signed second random number challenge. ### Claim 20 (depends on 19) The electronic lock of claim 19, wherein, upon completion of the authentication process, the electronic lock is enabled to receive a command from the server to actuate the motor and drive the latch between the locked position and the unlocked position.