Secure visitor registration at an electronic lock

Abstract

Secure registration of a user with an electronic lock is provided. Registration with the lock can include a verification process and a secure registration mode based on a unique enrollment code (UEC) associated with a registration invitation link that can be provided to the user. Selection of the link can direct the user's mobile device to a client application where an option to initiate the verification process can be provided. The UEC can be transmitted to the lock and presented by the lock. The user's device can capture the presented UEC, which can be compared to the UEC generated in association with the link. When verified, the lock can enter a secure registration mode where the user can enroll an actuation code, or the lock can pair with the mobile device through a short-range wireless connection, which can allow the user to actuate the lock via the client application.

Description

[0001] Cross-reference to related applications

[0002] This application, filed as a PCT international application on August 17, 2022, claims priority and benefit to U.S. Provisional Patent Application No. 63 / 234,012, filed on August 17, 2021, the disclosure of which is incorporated herein by reference in its entirety. Priority claims are made to the above-referenced application to the extent appropriate. Technical Field

[0003] This invention relates to the field of electronic locks. More specifically, this invention relates to a system and method for providing secure registration of a user with an electronic lock. Background Technology

[0004] Electronic locks are gaining increasing acceptance and widespread use in both residential and commercial markets due to the numerous benefits they offer. One example advantage can include the ability to lock or unlock doors using mobile devices such as smartphones or tablets. Another example advantage can include using programmed codes or biometric input, such as fingerprints or retinal scans, to lock or unlock doors. These advantages are useful not only to owners or tenants of homes with electronic locks but also to allowing visitor users to lock and unlock doors using their mobile devices, programmed codes, or biometrics, rather than providing them with physical keys. For example, a visitor user could be an individual the owner wishes to grant access to perform permitted actions associated with the electronic lock (e.g., locking, unlocking, adding lock actuation codes), typically for a short period.

[0005] To provide security against man-in-the-middle (MITM) attacks, denial-of-service attacks, or other attack vectors, current electronic locks may require physical actuation of a pairing button located on an internal component of the electronic lock, mounted on the inside of the door. For example, actuation of the pairing button could trigger the electronic lock to enter wireless (e.g., Pairing mode, where the requirement for physical actuation of the pairing button can limit the use of electronic locks. The pairing time window. However, a drawback of this security measure is that visitor users may not be able to pair their mobile devices with the electronic lock or register codes or biometric features to actuate the lock without accessing the inside of the door. Therefore, to grant visitor users access to the inside of the door, the owner may need to be present in the house. This is not only inconvenient, but also impractical for the owner in various situations.

[0006] Therefore, a security system and method are needed to enable individuals to register as visitor users of an electronic lock without accessing its internal components. Summary of the Invention

[0007] This disclosure generally relates to systems and methods for providing secure registration of visitor users with electronic locks.

[0008] In a first aspect, an electronic lock is provided, comprising: a latch assembly including a bolt movable between a locked position and an unlocked position; a motor configured to receive an actuation command that causes the motor to move the bolt from the locked position to an unlocked position or from the unlocked position to the locked position; a wireless circuit configured to wirelessly communicate with a client application installed on a mobile device; a code output interface configured to present a unique registration code; at least one processor; and a memory communicatively connected to the processor, the memory storing instructions that, when executed, cause the electronic lock to: receive a unique registration code associated with a registration invitation link provided to a guest user; present the unique registration code via the code output interface in response to receiving an instruction to initiate a registration code verification process based on the selection of the registration invitation link; and enter a secure registration mode in response to receiving an instruction that the unique registration code has been received and verified by a mobile device, the secure registration mode enabling the guest user to register as a user of the electronic lock.

[0009] On the other hand, a method for providing secure registration of a user with an electronic lock is provided, the method comprising: receiving a unique registration code associated with a registration invitation link provided to a visitor user; presenting the unique registration code via a code output interface in response to receiving an instruction to initiate a registration code verification process; and entering a secure registration mode in response to receiving an instruction that the unique registration code has been received and verified by a mobile device, the secure registration mode enabling the visitor user to register as a user of the electronic lock.

[0010] On the other hand, a system for providing secure registration of a user with an electronic lock is provided, the system comprising: at least one processor; and a memory communicatively connected to said at least one processor, the memory storing instructions that, when executed, cause the system to: provide a user interface on a mobile device in response to receiving a selection of a registration invitation link associated with a guest user account of the electronic lock and a unique registration code, the user interface including an option to initiate registration with the electronic lock; receive a selection of the option to initiate registration with the electronic lock when the mobile device approaches the electronic lock; notify a server of the selection to initiate registration; receive input via the user interface of a unique registration code presented by the electronic lock based on the selection to initiate registration; and verify the presented unique registration code against the unique registration code associated with the registration invitation link, so that the electronic lock can enter a secure registration mode that allows the guest user to register as a user of the electronic lock.

[0011] This summary is provided to introduce, in a simplified form, some concepts that will be further described in the following detailed description. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter. Attached Figure Description

[0012] The following accompanying drawings illustrate specific embodiments of the present disclosure and therefore do not limit the scope of the disclosure. The drawings are not drawn to scale and are intended for use in conjunction with the explanations in the following detailed description. Embodiments of the present disclosure will now be described in conjunction with the accompanying drawings, wherein similar reference numerals denote similar elements.

[0013] Figure 1 This is a block diagram of an example environment in which various aspects of this disclosure can be implemented.

[0014] Figure 2 It is a data flow diagram, which graphically represents an example data flow as part of providing security registration for visitor users with electronic locks.

[0015] Figure 3 Is Figure 1 An example of a side view of a portion of an electronic lock as seen in an example environment.

[0016] Figure 4 Is Figure 1 An example of a rear perspective view of a portion of an electronic lock as seen in an example environment.

[0017] Figure 5 Is Figure 1 An example of a front perspective view of a portion of an electronic lock as seen in an example environment.

[0018] Figure 6 Is Figure 1 A schematic diagram of an electronic lock seen in an example environment.

[0019] Figure 7 Is Figure 1 This is an example of a schematic representation of a mobile device seen in an example environment.

[0020] Figure 8 Is Figure 1 The example environment provides a flowchart of the method for secure registration of guest users with electronic locks.

[0021] Figure 9 This is an example of a sample user interface provided by a client application running on the administrator's mobile device, where the user interface can be used to invite guest users as users of the electronic lock.

[0022] Figure 10This is an example of a registration invitation link that can be sent to and received by a visitor's mobile device.

[0023] Figure 11 This is an example of an option to register for an electronic lock, provided in a sample user interface of a client application running on a guest's mobile device, in response to the selection of a registration invitation link.

[0024] Figure 12 This is an example of a unique registration code captured by a visitor's mobile device and associated with the selected registration invitation link presented by the electronic lock.

[0025] Figure 13 This is an example of an electronic lock in secure registration mode, where the electronic lock can receive a biometric activation password from the visitor user.

[0026] Figure 14 This is another example of a graphical representation of an electronic lock in secure registration mode, where the electronic lock is able to receive an alphanumeric activation password from a visitor user.

[0027] Figure 15 This is an example of a graphical representation of an electronic lock in pairing mode, where the electronic lock and the visitor's mobile device can communicate and exchange information via a short-range wireless connection. Detailed Implementation

[0028] Various embodiments of the invention will be described in detail with reference to the accompanying drawings, wherein similar reference numerals in several views represent similar parts and components. Reference to various embodiments does not limit the scope of the invention, which is limited only by the scope of the appended claims. Furthermore, any examples set forth in this specification are not intended to be limiting, but merely illustrate some of the many possible embodiments of the claimed invention.

[0029] As briefly described above, embodiments of the present invention aim to provide secure registration of electronic locks with guest users. For example, one or more aspects of this disclosure can be used to enable individuals to register as guest users of an electronic lock without accessing its internal components. In some examples, registration with an electronic lock may include a registration code verification process and a secure registration mode based on a unique registration code verification, which can be performed to ensure that the guest user is authorized to register as a user of the electronic lock. For example, a unique registration code can be generated and associated with a registration invitation link that can be provided to the guest user. The selection of the link can direct the guest user's mobile computing device to a client application associated with the electronic lock, where options for initiating the registration code verification process can be provided.

[0030] In some examples, as part of the registration code verification process, a unique registration code can be transmitted to and presented by the electronic lock. A guest user can use their mobile device to capture or otherwise receive the unique registration code presented by the electronic lock. The presented and captured unique registration code can be compared with a unique registration code generated in conjunction with the registration invitation link. When the unique registration code is validated, the electronic lock can enter secure registration mode. The unique registration code is not a lock actuation password and cannot be used to actuate the electronic lock from the locked position to the unlocked position. Instead, the unique registration code enables the guest user to verify their identity, allowing the electronic lock to enter secure registration mode. For example, while the electronic lock is in secure registration mode, a guest user can register a password with the electronic lock that allows them to actuate the lock, or the electronic lock can be paired with a guest mobile device via a short-range wireless connection, allowing the guest user to actuate the lock via a client application running on the guest mobile device.

[0031] In terms of examples, various wireless protocols can be used. In an example embodiment, the Wi-Fi protocol (802.11x) can be used to connect the electronic lock to a server (cloud) device, while different wireless protocols (e.g., include Low power (BLE) wireless protocols can be used for short-range communication between electronic locks and other devices, such as mobile devices used to actuate locks. In other embodiments, various other wireless protocols can be used, such as other short-range or long-range wireless protocols (e.g., cellular, RFID / NFC, etc.). wait).

[0032] The term "lock" or "lockset" is broadly intended to include any type of lock, including but not limited to bolts, knob locks, lever handle locks, mortise locks, and slide locks, whether mechanical, electronic, or electromechanical. Locking points can have various mounting structures and / or locations, including but not limited to: being fixed inside the door frame with mortises, mounted on the outside of the door frame or supporting structure, and / or directly fixed to the door.

[0033] Although this disclosure describes these features as implemented on an electronic latch lock for illustrative purposes, these features are applicable to any type of lock, including but not limited to latches, ball locks, handle locks, etc. Furthermore, the exemplary aspects of this application can be applied to other types of IoT devices where security is an issue, such as wireless / connected home devices that store user data.

[0034] Figure 1An operating environment 102 is shown, in which various aspects of this disclosure can be implemented. As shown, the operating environment 102 includes a door 104, which includes an electronic lock 100 (also referred to as a wireless electronic lock) installed at the house. The electronic lock 100 may be operable or configurable to lock and unlock the door 104 based on programmed code or biometric input, or via a client application 116 (e.g., an electronic lock application) running on a user computing device (e.g., an administrator mobile device 110, a visitor mobile device 112).

[0035] The administrator user 106 of the electronic lock 100 is the primary user or authorized person, such as the owner or tenant of a house with a door 104 including the electronic lock 100 installed. The administrator user 106 has a mobile computing device (referred to herein as administrator mobile device 110), such as a smartphone or tablet with wireless communication capabilities. The administrator mobile device 110 is capable of communicating 105 with the server 114, 115 with the electronic lock 100, and 125 with the mobile phone or other mobile computing device of the visitor user 108 (referred to herein as visitor mobile device 112). For example, the administrator mobile device 110 may be operable or configured to wirelessly communicate with the server 114, the electronic lock 100, and the visitor mobile device 112 using one or more wireless protocols.

[0036] Guest user 108 may be a person whom administrator user 106 may wish to grant access to perform at least a subset of actions associated with electronic lock 100 (e.g., locking, unlocking, changing some settings). For example, guest user 108 may be a short-term user of electronic lock 100, such as a vacation rental user, pet sitter, cleaner, etc. In some examples, administrator user 106 may wish to allow guest user 108 to register as a user of electronic lock 100 so that guest user 108 can perform locking actions. In some examples, electronic lock 100 may be configured to enter a secure registration mode, which may allow guest user 108 to register a password (e.g., numeric, alphanumeric, biometric, etc.) with electronic lock 100 so that guest user 108 can actuate lock 100. In other examples, when in registration mode, electronic lock 100 may be enabled to pair with guest mobile device 112, which may allow guest user 108 to actuate lock 100 via client application 116 running on guest mobile device 112.

[0037] According to an aspect of this disclosure, the electronic lock 100 can be configured to enter a secure registration mode based on verification of a unique registration code. For example, a registration code verification process can be performed to ensure that the intended visitor user 108 is authorized to register as a user of the electronic lock 100. In some examples, the unique registration code is a limited-use (e.g., one-time use, valid for a limited time period) code. According to one aspect, the unique registration code is not a lock actuation password and cannot be used to actuate the electronic lock 100 from the locked position to the unlocked position. Instead, the unique registration code enables the visitor user 108 to pair the visitor mobile device 112 with the electronic lock 100 or register a password (e.g., numeric, alphanumeric, biometric) with the electronic lock 100, allowing the visitor user 108 to actuate the lock 100. For example, when the administrator user 106 is not in the house, this registration code verification process can enhance the security of visitor user registration, thereby preventing unauthorized third-party users from registering as users of the electronic lock 100 and gaining access to the house. The registration code verification process also enables visitor user 108 to securely register with electronic lock 100 and then actuate lock 100 without access to the inside of door 104 (e.g., without needing to actuate a pairing button on electronic lock 100 that may be located inside door 104). Visitor mobile device 112 is operable or configured to communicate wirelessly with server 114 130, electronic lock 100 135, and administrator mobile device 110 125 using one or more wireless protocols.

[0038] Server 114 may be a physical server or a virtual server hosted in a cloud storage environment 118. In some examples, electronic lock 100 is operable or configured to communicate 140 with server 114. This communication 140 may optionally occur via one or more wireless communication protocols (e.g., Wi-Fi (IEEE 802.11), short-range wireless communication to a Wi-Fi bridge, or other connection mechanisms). Server 114 may be operable or configured to expose one or more application programming interfaces (APIs) that can be used for communication between administrator mobile device 110 and server 114 (communication 105), communication between guest mobile device 112 and server 114 (communication 130), and communication between server 114 and electronic lock 100. In some examples, server 114 may be operable or configured to typically manage user accounts associated with electronic lock 100 (e.g., administrator user accounts and guest user accounts) and forward instructions between authorized mobile devices and electronic lock 100.

[0039] In some examples, as part of a registration code verification process that can be performed to ensure that the expected visitor user 108 is authorized to register as a user of the electronic lock 100, the server 114 may be operable or configured to provide a unique registration code to the electronic lock 100. As will be described in further detail below, the electronic lock 100 may be operable or configured to present (e.g., visually, audibly, tactilely) a unique registration code, which may be captured by sensors included in the visitor's mobile device 112. For example, the unique registration code may be verified by a client application 116 running on the visitor's mobile device 112, or transmitted to the server 114 for verification. After the unique registration code is verified, the electronic lock 100 may be instructed to enter a secure registration mode. In other example implementations, the unique registration code may be presented (e.g., visually, audibly, tactilely) by the visitor's mobile device 112, captured by sensors included in the electronic lock 100, and verified by the electronic lock 100 or the server 114.

[0040] Figure 2 This is a data flow diagram that graphically represents an example data flow as part of providing security registration for visitor user 108 with electronic lock 100. The example data flow illustrates the various communications involved in providing security registration for visitor user 108 with electronic lock 100, from receiving a request to register visitor user 108 to initiating the security registration mode of electronic lock 100. Various arrows are labeled with circled numbers, indicating example data flows and / or operations between components. It should be understood that some messages may not be in sequence. Figure 2 The order of the changes is shown (e.g., substantially simultaneously or in reverse order).

[0041] Now refer to Figure 2The circled number 1 indicates a request to register visitor user 108 as a user of electronic lock 100. For example, in response to an option made by administrator user 106 of electronic lock 100 to register visitor user 108 or invite visitor user 108 to register as a user of electronic lock 100, this request may be generated by a client application 116 running on administrator user device 110. In some examples, client application 116 may provide a user interface (UI) that includes various options, such as, for example, the option to invite / register visitor user 108 as a user of electronic lock 100. As another example, the UI may include one or more access permission options associated with visitor user 108, such as access level or type (e.g., visitor user to administrator user), the period for which the visitor user's access is permitted (e.g., one-time period, cyclical period), permitted lock actuation methods (e.g., allowing actuation of electronic lock 100 using client (lock) application 116, allowing registration of numeric, alphanumeric, or alphanumeric passwords, biometric features (e.g., fingerprint, retinal scan, facial features, voice), and / or another type of unique password for electronic lock 100), and / or other access permission options. In some examples, a request to invite / register a guest user 108 may include one or more access permission options selected by the administrator user 106 via the client application UI.

[0042] In some examples, server 114 may operate to create a guest user account associated with electronic lock 100 based on a request and selection made by administrator user 106. In some examples, server 114 may further operate to generate a unique registration code, which may be associated with the guest user account and transmitted to guest user 108, and used to verify guest user 108 to allow electronic lock 100 to enter secure registration mode. In other examples, the unique registration code may be generated by a client application 116 running on administrator mobile device 110.

[0043] The circled number 2a indicates a response to the request. In some examples, the response may include a registration invitation link that can be shared with guest user 108. For example, when selected, the registration invitation link can operate to redirect guest mobile device 112 to the login page of client application 116, where guest user 108 can use client application 116 to access the guest user account associated with electronic lock 100 and verify his / her identity for registering as a user of electronic lock 100.

[0044] In some examples, the registration invitation can be sent from the administrator's mobile device 110 to the guest's mobile device 112, as indicated by the circled number 2b. For example, in some implementations, the registration invitation may include a text message, email, social media message, or other type of electronic message, or it may be wirelessly sent to the guest's mobile device 112 via a wireless protocol or other means.

[0045] In other examples, the registration invitation may be sent from server 114 to the visitor's mobile device 112, as indicated by the circled number 2c. For example, in some implementations, the request to invite / register visitor user 108 as a user of the electronic lock 100 may also include the visitor user 108's contact information (e.g., phone number, email address, social media identifier), which server 114 may use to send a registration invitation link to the visitor's mobile device 112 via text message, email, or other types of electronic messaging. In this case, the communication indicated by the circled number 2a may alternatively include a notification that a registration invitation link associated with the visitor user's account has been automatically sent to visitor user 108 based on the contact information.

[0046] According to one aspect, in response to receiving a selection of the registration invitation link, the guest mobile device 112 can operate to open the client application 116, and if the application is already installed on the device, it will be redirected to the login page of the client application 116; or if the client application 116 is not yet installed on the guest mobile device 112, the guest mobile device 112 may first be redirected to a location where the client application 116 can be accessed. It should be understood that the client application 116 can be downloaded based on permission granted by the guest user 108.

[0047] In some examples, the login page is a registration page and / or includes options for initiating registration with the electronic lock 100. In some examples, before redirecting the user to the login page, a link may first direct the user to a password setting page, where the guest user 108 can establish a password to access the guest user account created on behalf of the electronic lock 100. In some examples, the registration invitation link may include a token that can be parsed to enable the client application 116 to access the guest user account associated with the electronic lock 100.

[0048] In some examples, when visitor user 108 is located at and near the electronic lock 100, visitor user 108 may have the option to initiate registration with the electronic lock 100. In some examples, as part of registering visitor user 108 as a user of the electronic lock 100, visitor mobile device 112 may utilize Global Positioning System (GPS) data to ensure that the visitor user and associated visitor mobile device are located at the home where the electronic lock 100 is installed. In some examples, as part of registering visitor user 108 as a user of the electronic lock 100, a unique registration code may be presented, wherein the presentation of the unique registration code may be captured or received and compared with a unique registration code linked to the visitor user account associated with the electronic lock 100. For example, after verifying the unique registration code, the electronic lock 100 may be enabled to enter secure registration mode.

[0049] In some examples, the unique registration code can be one of various types of passwords that can be presented by the code output interface of the electronic lock 100 and captured by sensors included in the visitor mobile device 112. An example unique registration code may include a visual password presented via one or more lights (e.g., light-emitting diode (LED) lights) included in the electronic lock 100. For example, one or more lights may be included in a keypad that may be included in the electronic lock 100, or may be detached from the keypad. In some examples, one or more lights may be configured or operable to light up or emit pulses according to a specific rhythm. In other examples, the lights may light up in a specific mode (e.g., a static mode or a dynamic mode). In some examples, the unique registration code embodied as a visual password may be captured by a camera included in the visitor mobile device 112. In other examples, the unique registration code embodied as a visual password may be observed by the visitor user 108 and entered into the visitor mobile device 112 via a UI input method.

[0050] Another example of a unique registration code could be an auditory password presented via a speaker or other sound-emitting element included in the electronic lock 100. For example, the sound-emitting element could be configured or operable to emit a series of sounds (e.g., beeps, tones, musical melodies) or pulses according to a specific rhythm and / or pitch. In some examples, the unique registration code embodied as an auditory password could be captured by a microphone included in the visitor's mobile device 112.

[0051] Another example of a unique registration code could be a haptic password presented via a haptic actuator element in the electronic lock 100. For example, the haptic actuator element could be configured or operable to provide mechanical feedback using tactile feedback, such as vibration patterns. In some examples, the unique registration code embodied as a haptic password could be captured by a ceramic piezoelectric sensor, accelerometer, or other type of haptic sensor included in the guest mobile device 112. In other examples, the guest user 108 could sense the unique registration code embodied as a haptic password, and the guest user 108 could input a representation of the haptic password into the guest mobile device 112 via a UI input method.

[0052] The unique registration code can take various other forms. For example, the unique registration code can represent a specific pattern of a light-emitting diode, or it can represent other display types, such as a specific pattern of a display on a touchscreen. In some instances, the specific pattern can be an alphanumeric code, a barcode, a QR code, etc. It should be understood that other types of unique registration codes are possible and are within the scope of this disclosure.

[0053] In some examples, selecting the option to initiate registration with the electronic lock 100 allows a client application 116 running on the guest's mobile device 112 to transmit a message, represented by the circled number 3, to the server 114, instructing the electronic lock 100 to present a unique registration code associated with the registration invitation and the guest user's account. For example, a unique registration code specific to the guest user's registration invitation, based on a token, can be transmitted to the electronic lock 100, as represented by the circled number 4. In some examples, the communication represented by the circled number 4 may include instructions that the electronic lock 100 can be operated or configured to process in order to present the unique registration code.

[0054] In some examples, as indicated by the circled number 5, based on instructions received from server 114, electronic lock 100 may display a visual password using one or more lights (e.g., LEDs) included in electronic lock 100 according to a specific rhythm or pattern (e.g., static or dynamic pattern), play an auditory password using a sound-emitting element included in electronic lock 100, or generate a tactile password presented via a tactile actuator element included in electronic lock 100. In some examples, guest user 108 may use guest mobile device 112 to capture a unique registration code presented by electronic lock 100, or guest user 108 may observe the unique registration code presented by electronic lock 100 and enter the presented unique registration code into the UI provided by client application 116.

[0055] According to one aspect, the captured / entered unique registration code can be compared with a unique registration code linked to a registration invitation associated with guest user 108 to verify guest user 108. In some examples, a client application 116 running on guest mobile device 112 can access the assigned unique registration code and can be operable or configured to compare and verify the captured / entered unique registration code. For example, after verifying the unique registration code, client application 116 can transmit the verification to a server, as indicated by the circled number 6. In other examples, the captured / entered unique registration code can be transmitted to server 114 for comparison and verification, which can alternatively be represented by the circled number 6.

[0056] In some examples, verification communication may be provided to the electronic lock 100, as indicated by the circled number 7a. For example, after verifying the unique registration code, the electronic lock 100 may be instructed to enter secure registration mode. In some examples, such as if verification is performed by the server 114, a notification that the captured / entered unique registration code has been verified may be transmitted to the visitor's mobile device 112, as indicated by the circled number 7b.

[0057] According to one aspect, when the electronic lock 100 is in secure registration mode, the electronic lock 100 can be operated or configured to complete visitor user account registration. In some examples, when the electronic lock 100 is in secure registration mode, the electronic lock 100 can be configured to receive input of a lock actuation password that a visitor user 108 can use to actuate the lock 100. This input is represented by a circled number 8.

[0058] In some examples, the lock actuation password can be numbers, letters, or alphanumeric codes, which the visitor user 108 can enter into the input interface 202 included in the electronic lock 100. For example, the input interface 202 may include a keypad and / or buttons. In other examples, the lock actuation password can be a biometric feature, such as a fingerprint, retinal scan, facial features, voiceprint, etc., which the visitor user 108 can enter into the input interface 202 included in the electronic lock 100. In this example, the input interface 202 may include a biometric interface (e.g., a fingerprint sensor, a retinal scanner, a camera including facial recognition, or an audio interface that can use voice recognition to actuate the lock), where the visitor user's biometric feature can be used to actuate the lock without requiring the input of a specific lock actuation password.

[0059] In some implementations, when the electronic lock 100 is in a secure registration mode, it can be configured to enter a pairing mode that enables it to pair with a guest mobile device 112 via a short-range wireless connection (e.g., BLE connection). For example, pairing with the guest mobile device 112 allows a guest user 108 to actuate the electronic lock 100 using a client application 116 running on the guest mobile device 112. In some examples, the client application 116 may provide one or more options in its UI that the guest user 108 can select to lock or unlock the electronic lock 100. In some examples, the client application 116 may also provide an option in its UI that allows the guest user 108 to enter a lock actuation password into the guest mobile device 112 to register the password with the electronic lock 100.

[0060] As described above, in other example implementations, a unique registration code may be presented by the guest mobile device 112 and received by the electronic lock 100 (e.g., captured by or input into the input interface 202) to verify the guest user 108 and allow the electronic lock 100 to enter a secure registration mode. For example, the communication represented by the circled number 4 may include a client application 116 running on the guest mobile device 112 that may be operable or configured to process instructions to present the unique registration code. Thus, the presented unique registration code may be verified by the electronic lock 100 (e.g., where a unique registration code linked to a registration invitation associated with the guest user 108 may be pre-transmitted to the electronic lock 100) or transmitted by the lock to the server 114 for verification.

[0061] Figures 3 to 5 An example of an electronic lock 100 installed at door 104 according to this disclosure is shown. Referring now to… Figure 3 As shown in the figure, door 104 has an inner side 204 and an outer side 206. Electronic lock 100 may include an inner component 208, an outer component 210, and a latch assembly 212. Latch assembly 212 is shown including an extended position (locked) and a retracted position (unlocked, e.g., ...). Figures 3 to 5 A movable latch 214 is shown between the door 104 and the door frame (not shown). Specifically, the latch 214 is configured to slide longitudinally, and when the latch 214 is retracted, the door 104 is in the unlocked state. When the latch 214 is extended, the latch 214 can protrude from the door 104 into the door frame (not shown) to lock the door.

[0062] In some examples, the inner component 208 is mounted on the inner side 204 of door 104, and the outer component 210 is mounted on the outer side 206 of door 104. The latching assembly 212 is typically at least partially mounted in a hole formed in door 104. The term "outside" is widely used to refer to the area outside door 104, while "inside" is widely used to refer to the area inside door 104. For example, for an external entrance door, the outer component 210 may be mounted on the exterior of the building, while the inner component 208 may be mounted inside the building. For an interior door, the outer component 210 may be mounted inside the building, but outside the room protected by the electronic lock 100, and the inner component 208 may be mounted inside the protected room. The electronic lock 100 is applicable to both interior and exterior doors.

[0063] Reference Figure 4 The internal component 208 may include a processing unit 402 (schematically shown) containing electronic circuitry for the electronic lock 100. In some examples, the internal component 208 includes a manual turn 404 that can be used on the inside 204 of the door 104 to move the latch 214 between an extended position and a retracted position. The processing unit 402 is operable to execute a plurality of software instructions (i.e., firmware) that, when executed, cause the electronic lock 100 to implement the method and otherwise operate and have the functionality as described herein. The processing unit 402 may include a device generally referred to as a processor, such as a central processing unit (CPU), digital signal processor (DSP), or other similar device, and may be embodied as a separate unit or a device shared with components of the electronic lock 100. The processing unit 402 may include a memory communicatively connected to the processor for storing the software instructions. Alternatively, the electronic lock 100 may also include a separate memory device electrically connected to the processing unit 402 for storing software instructions for bidirectional communication between instructions, data, and signals.

[0064] In some examples, internal component 208 includes a pairing button 406 (illustrated) that, when actuated, can initiate a secure registration mode. For example, the secure registration mode can enable the electronic lock 100 to receive a lock actuation password to be registered with the electronic lock 100, or it can enable the electronic lock 100 to communicate with a mobile device (e.g., a guest mobile device 112) within short-range wireless communication range, allowing the mobile device to pair with and actuate the electronic lock 100. An example method of biometric registration with the electronic lock 100 is described in U.S. Patent Publication No. 2021 / 0158067, entitled “SYSTEM AND METHOD OF ENROLLING USERS OF A WIRELESS BIOMETRIC LOCKSET,” the entire contents of which are incorporated herein by reference.

[0065] In some examples, initiating a secure registration mode via actuating the pairing button 406 may be limited to users with access to the inside 204 of door 104. Therefore, aspects of this disclosure can be used to initiate a secure registration mode without accessing the pairing button 406 or the inside 204 of door 104.

[0066] Reference Figure 5 External component 210 may include external circuitry 617 that is communicatively and electrically connected to processing unit 402. For example, external component 210 may include the input interface 202 described above. Figure 5 As shown, in some examples, input interface 202 may include keyboard 502 and / or buttons. For example, keyboard 502 and / or buttons may be operable or configured to receive an actuation password entered by a user via selecting a series of buttons or markings (e.g., numbers, letters, or alphanumeric) included in keyboard 502.

[0067] Keyboard 502 can be any of a variety of different types of keyboards. For example, keyboard 502 may include a plurality of buttons 508 that can be mechanically actuated by a user (e.g., physically pressed). In some examples, keyboard 502 includes a touch interface 510 for receiving user input, such as a touchscreen or touch keyboard. Touch interface 510 may be configured to detect user selection or “button press” by contact, without requiring pressure or mechanical actuation. Examples of touch interfaces are described in U.S. Patent No. 9,424,700, “ELECTRONIC LOCK HAVING USAGE AND WEAR LEVELING OF ATOUCH SURFACETHROUGH RANDOMIZED CODE ENTRY,” the entire contents of which are incorporated herein by reference.

[0068] In other examples, input interface 202 may include a biometric sensor, such as a fingerprint sensor, a retinal scanner, a camera including facial recognition, an audio interface through which the lock can be actuated using voice recognition, or other types of sensors. For example, a biometric sensor may be operable or configured to receive user input for an actuation password by sensing the user's biometric characteristics.

[0069] When a user enters a valid actuation password into input interface 202, the processor can operate to provide a lock actuation command to the motor to move the latch 214 between an extended position and a retracted position. In some examples, external component 210 is electrically connected to internal component 208. Specifically, input interface 202 can be electrically connected to internal component 208, specifically to processing unit 402, via, for example, a cable (not shown) passing through door 104. When a user enters a valid actuation password recognized by processing unit 402 via input interface 202, the motor can be energized to retract the latch 214 of latch component 212, thereby allowing door 104 to open from the closed position. In some examples, electronic lock 100 may include more than one input interface 202. For example, external component 210 may include keypad 502 and biometric sensors.

[0070] In some examples, the electronic lock 100 may include a key slot 504 for receiving a key (not shown). For example, when a valid key is inserted into the key slot 504, the valid key is able to move the latch 214 between an extended position and a retracted position. The outer side 206 of the door 104 may also include a handle 506, which may be included in or detached from the electronic lock 100.

[0071] In some examples, the electronic lock 100 may include a code output interface 512 operable or configurable to present a unique registration code that, upon verification, enables the electronic lock 100 to enter a secure registration mode. For example, the code output interface 512 may include one or more lights (e.g., LEDs) operable to illuminate according to a specific rhythm or pattern (e.g., static or dynamic mode), an acoustic element operable to play an auditory password, a tactile actuator element operable to emit a tactile password, or another type of code output element operable to present a unique registration code.

[0072] In some examples, the code output interface 512 may include a keypad 502 and / or buttons 508 of the electronic lock 100. For example, in a particular embodiment, the keypad 502 and / or buttons 508 may also be operable or configured to receive signals from the processing unit 402 to illuminate one or more buttons 508 or markers associated with buttons 508 according to a specific rhythm or pattern (e.g., a static or dynamic pattern) based on a unique registration code. For example, the rhythm or pattern of button 508 illumination may visually reveal a unique registration code that may be sensed or entered into the visitor mobile device 112 and verified to allow a visitor user to register an activation password for the electronic lock 100. As an example, the activation password may be a numeric, alphanumeric, or alphanumeric password that the visitor user 108 can enter via the keypad 502.

[0073] As described above, guest user 108 can use guest mobile device 112 to capture the unique registration code presented by the code output interface 512 of electronic lock 100, or guest user 108 can observe the unique registration code presented by electronic lock 100 and input the presented unique registration code into the UI provided by client application 116. For example, the unique registration code can be verified by client application 116 running on guest user device 112, or transmitted to server 114 for verification. After the unique registration code is verified, electronic lock 100 can be instructed to enter secure registration mode, wherein electronic lock 100 can be enabled to receive and store the actuation password entered by guest user 108 and / or enable to communicate and pair with guest mobile device 112 when guest mobile device 112 is within the short-range wireless communication range of electronic lock 100.

[0074] In other example implementations, the unique registration code may be presented by the visitor's mobile device 112 (e.g., visually, auditorily, or tactilely) and captured by sensors 514 that may be included in the electronic lock 100. For example, the electronic lock 100 may include one or more sensors 514 (such as a camera, proximity sensor, ceramic piezoelectric sensor, accelerometer, or other type of sensor) that may be operable or configured to capture the unique registration code presented by the mobile computing device. In other example implementations, the unique registration code may be presented by the visitor's mobile device 112 (e.g., visually, auditorily, or tactilely) and observed by the visitor user 108, who may input the unique registration code into the electronic lock 100 using a keyboard 502 or other input interface 202. In some examples, the unique registration code may be verified by the electronic lock 100. In other examples, the unique registration code may be transmitted to and verified by a server 114.

[0075] Furthermore, the electrical connection between the external component 210 and the internal component 208 allows the processing unit 402 to communicate with other features included in the external component 210, as described below.

[0076] Figure 6 This is a schematic representation of an electronic lock 100 installed on door 104. Internal component 208, external component 210, and latch component 212 are shown.

[0077] External component 210 is shown to include an input interface 202, which may include a keyboard 502 and an optional external antenna 602 for communicating with remote devices. In some examples, external component 210 may include one or more sensors 514 that can sense conditions outside door 104. In response to such sensed conditions, a notification may be sent by electronic lock 100 to server 114, administrator mobile device 110, or visitor mobile device 112, including information associated with the sensed event (e.g., the time and description of the sensed event, or a remote feed of sensor data obtained via the sensors). In some examples, external component 210 may include one or more sensors 514 that can receive a unique registration code.

[0078] In some examples, the external antenna 602 can be used in conjunction with an optional internal antenna 604, allowing the processing unit 402 to determine the location of the mobile device. The door can only be actuated (unlocked or locked) if the mobile device (e.g., administrator mobile device 110 or guest mobile device 112) is paired with the electronic lock 100 and determined to be located outside the door 104. This prevents unauthorized users from being outside the door 104 of the electronic lock 100 and using an authorized mobile device that may be located inside the door, even if that authorized mobile device is not used to actuate the door. However, this feature is not mandatory but adds extra security. In alternative arrangements, the electronic lock 100 may be activated solely from the input interface 202 (via entering a valid actuation password) or from a client application 116 installed on a mobile device (e.g., administrator mobile device 110 or guest mobile device 112). In some implementations, the external antenna 602 may be omitted entirely.

[0079] As described above, internal component 208 includes processing unit 402. Internal component 208 may also include motor 606 and optional internal antenna 604.

[0080] As shown, the processing unit 402 includes at least one processor 608 communicatively connected to the security chip 610, memory 612, various wireless communication interfaces (e.g., including a Wi-Fi interface 614 and / or a Bluetooth interface 616), and battery 618. The processing unit 402 is located within internal component 208 and is capable of operating the electronic lock 100 (e.g., actuating the latch 214 via an actuation motor 606).

[0081] In a particular example, Bluetooth interface 616 includes a Bluetooth Low Energy (BLE) interface. Additionally, in some embodiments, Bluetooth interface 616 is associated with a security chip 622, for example, a security chip being an encryption circuit capable of storing encrypted information and generating encryption keys that can be used to generate certificates for communication with other systems (e.g., administrator mobile device 110, guest mobile device 112).

[0082] In some examples, processor 608 can process signals received from various devices to determine whether the electronic lock 100 should be actuated. This processing can be based on a set of pre-programmed instructions (i.e., firmware) stored in memory 612. In some embodiments, processing unit 402 may include multiple processors 608, including one or more general-purpose or special-purpose instruction processors. In some examples, processing unit 402 is configured to capture input events from a user's input interface and store such input events in memory 612. In other examples, processor 608 may receive signals from external antenna 602, internal antenna 604, or motion sensor 620 (e.g., vibration sensor, gyroscope, accelerometer, motion / position sensor, or combinations thereof) and be able to verify the received signals to actuate lock 100. In other examples, processor 608 may receive signals from Bluetooth interface 616 to determine whether to actuate electronic lock 100.

[0083] In some examples, internal component 208 also includes a battery 618 that powers the electronic lock 100. In one example, battery 618 may be a standard single-use (disposable) battery. Alternatively, battery 618 may be rechargeable. In a further embodiment, battery 618 is entirely optional and can be replaced by an alternative power source (e.g., an AC power connection).

[0084] As described above, internal component 208 may also include a motor 606 capable of actuating latch 214. In use, motor 606 may receive an actuation command from processing unit 402, causing motor 606 to actuate latch 214 from a locked position to an unlocked position or from an unlocked position to a locked position. In some examples, motor 606 actuates latch 214 to a relative state. In some examples, motor 606 receives a specified lock or unlock command, wherein if latch 214 is in the correct position, motor 606 may actuate only latch 214. For example, if door 104 is locked and motor 606 receives a lock command, no action is taken. If door 104 is locked and motor 606 receives an unlock command, motor 606 may actuate latch 214 to unlock door 104.

[0085] As described above, an optional internal antenna 604 may also be located within internal component 208. In some examples, internal antenna 604 may be operable or configured to operate in conjunction with external antenna 602 to determine the location of administrator mobile device 110 or visitor mobile device 112. In some examples, only mobile devices determined to be located on the outer side 206 of door 104 can unlock (or lock) door 104. For example, this can prevent unauthorized users from being near electronic lock 100 and using authorized mobile devices that may be located on the inner side 208 of door 104, even if the authorized mobile device is not used to unlock door 104. In alternative embodiments, internal antenna 604 may be omitted entirely, since electronic lock 100 can only be actuated by authorized mobile devices.

[0086] In some embodiments, processing unit 402 may include a security chip 610 communicatively interconnected with one or more instances of processor 608. In some examples, security chip 610 may, for example, generate and store encrypted information that can be used to generate a certificate that can be used to verify electronic lock 100 with remote systems such as server 114 or mobile devices (e.g., administrator mobile device 110 or guest mobile device 112)

[0087] In some embodiments, the security chip 610 may include a write-once capability, wherein a portion of the memory of the security chip 610 can be written to only once and then locked. This memory can be used, for example, to store encrypted information derived from characteristics of the electronic lock 100 or its communication channels with the server 114, the administrator mobile device 110, or the guest mobile device 112. Therefore, once written, such encrypted information can be used in a certificate generation process that ensures that if any characteristics reflected in the encrypted information are altered, the certificate generated by the security chip 610 becomes invalid, rendering the electronic lock 100 unable to perform various functions (such as communicating with the server 114, the administrator mobile device 110, or the guest mobile device 112), or in some cases, completely inoperable.

[0088] In some embodiments, the security chip 610 may be configured to generate a unique registration code that, when received and verified by the visitor mobile device 112, triggers a secure registration mode for the electronic lock 100. In some examples, the secure registration mode may enable the electronic lock 100 to receive an activation password from the user and store it in memory 612. In other examples, the secure registration mode may enable the electronic lock 100 to pair with a nearby mobile device (e.g., the visitor mobile device 112 on which the client application 116 is running).

[0089] In some examples, the unique registration code can be a random value. In other examples, the administrator user 106 can change the unique registration code by setting their own code or by requesting a random value generated by a client application 116 running on the administrator's mobile device 110. In some examples, the length of the unique registration code is variable. According to one aspect, to increase security, the unique registration code can be a limited-use password. For example, the unique registration code can be limited to single use, or it can be valid for a preset or administrator-selected duration.

[0090] Memory 612 may include any of a variety of memory devices, such as those using various types of computer-readable or computer storage media. A computer storage medium or computer-readable medium can be any medium capable of containing or storing a program used by or in conjunction with an instruction execution system, apparatus, or device. For example, a computer storage medium may include dynamic random access memory (DRAM) or variations thereof, solid-state memory, read-only memory (ROM), electrically erasable programmable ROM, and other types of devices and / or articles of manufacture for storing data. Computer storage media typically include at least one or more tangible media or devices. In some examples, a computer storage medium may include embodiments comprising entirely non-transitory components.

[0091] As described above, the processing unit 402 may include one or more wireless interfaces, such as a Wi-Fi interface 614 and / or a Bluetooth interface 616. Other RF circuitry may also be included. In the illustrated example, interfaces 614 and 616 are capable of communicating using at least one wireless communication protocol. In some examples, the processing unit 402 may communicate with a remote device via the Wi-Fi interface 614 or with a local device via the Bluetooth interface 616. In some examples, the processing unit 402 may communicate with the administrator mobile device 110 or the guest mobile device 112 and the server 114 via the Wi-Fi interface 614, and may also communicate with the administrator mobile device 110 or the guest mobile device 112 via the Bluetooth interface 616 when the mobile device is near the electronic lock 100. In some embodiments, the processing unit 402 may be configured to communicate with the administrator mobile device 110 or the guest mobile device 112 via the Bluetooth interface 616, and when the administrator mobile device 110 or the guest mobile device 112 is outside the range of the BLE wireless signal, the communication between the administrator mobile device 110 or the guest mobile device 112 and the electronic lock 100 may be relayed via the server 114 (e.g., via the WI-FI interface 614).

[0092] It should be understood that, in alternative embodiments, other wireless protocols may also be implemented via one or more additional wireless interfaces. In some examples, the electronic lock 100 can wirelessly communicate with external devices via a desired wireless communication protocol. In some examples, the external device can wirelessly control the operation of the electronic lock 100, such as the operation of the latch 214. The electronic lock 100 may utilize wireless protocols, including but not limited to the IEEE 802.11 standard (…). ), IEEE 802.15.4 standard ( and ), IEEE 802.15.1 standard ( ), cellular networks, wireless LANs, near-field communication protocols, and / or other network protocols. In some examples, the electronic lock 100 can wirelessly communicate with networked and / or distributed computing systems (such as those existing in a cloud computing environment).

[0093] In a particular embodiment, processor 608 may receive signals of communication indicating an intention to actuate electronic lock 100 from administrator mobile device 110 or guest mobile device 112 via Bluetooth interface 616 via a wireless communication protocol (e.g., BLE). As described further below, processor 608 may also initiate communication with server 114 via Wi-Fi interface 614 (or another wireless interface) to confirm an attempt to actuate electronic lock 100 or to receive an actuation command to actuate electronic lock 100.

[0094] In a particular embodiment, processor 608 may receive signals for unique registration code communication via Wi-Fi interface 614, which may instruct the processor to present the unique registration code to verify guest user 108. Additionally, processor 608 may receive signals from server 114 via Wi-Fi interface 614 or from guest mobile device 112 via Bluetooth interface 616 to transmit successful verification and authorization of the unique registration code to complete the registration of guest user 108.

[0095] Additionally, various other settings can be viewed and / or modified from server 114 via Wi-Fi interface 614. Thus, administrator user 106 or guest user 108 can use administrator mobile device 110 or guest mobile device 112 to access the account associated with electronic lock 100, such as viewing and modifying the lock's settings, which can then be propagated from server 114 to electronic lock 100. In alternative embodiments, other types of wireless interfaces can be used; typically, the wireless interface used for communicating with mobile devices can operate using a different wireless protocol than the wireless interface used for communicating with server 114.

[0096] As described above, in some example embodiments, the electronic lock 100 may include an integrated motion sensor 620. The use of such a motion sensor (e.g., an accelerometer, gyroscope, or other position or motion sensor) and the wireless capabilities of mobile devices or electronic devices (i.e., fobs) with these capabilities built in can help determine various types of motion events (e.g., door opening or closing events, lock actuation or lock position events, or knocking events based on door vibration). In some cases, motion events may cause the electronic lock 100 to perform certain processes (e.g., communicating with or sending data to mobile devices 110, 112 near the electronic lock 100; presenting a unique registration code). In alternative embodiments, other lock actuation sequences may not require the use of the motion sensor 620. For example, if an administrator mobile device 110 or a visitor mobile device 112 is within range of the electronic lock 100 while using a specific wireless protocol (e.g., BLE), a connection can be established with the electronic lock 100. Other arrangements using other connection sequences and / or communication protocols are also possible.

[0097] Overall reference Figures 1 to 6 In the example embodiment, the electronic lock 100 can be used on both the interior and exterior doors 104. The description herein is a non-limiting example of a wireless electronic lock. It should be noted that the electronic lock 100 can be used on other types of doors 104 (such as garage doors or dog doors), or other types of doors that require an authentication process to unlock (or lock). Therefore, the electronic lock 100 can be configured as a latch as in some of the examples described herein, but should be understood to be suitable for a variety of mechanical configurations and motor / sowary combinations for latch and / or latch actuation.

[0098] In some embodiments, the electronic lock 100 is made of a hybrid metal and plastic, with engineered cavities to house electronics and an antenna. For example, in some embodiments, the lock utilizes an antenna located near the outer surface of the lock, designed within the metal body of the lock itself. The metal body can be engineered to meet stringent physical security requirements and also allows the embedded front-mounted antenna to effectively propagate RF energy.

[0099] Figure 7 A schematic diagram of a mobile device 700 (such as an administrator mobile device 110 and a guest mobile device 112) is shown, which can be used in embodiments of this disclosure to enable secure registration of a guest user 108 with an electronic lock 100. For example, one or more aspects of this disclosure can be used to enable a guest user 108 to register as a guest user of the electronic lock 100 without needing to access the internal components 208 of the electronic lock 100.

[0100] In some embodiments, the mobile device 700 operates to enable security devices to establish Bluetooth or BLE connections with a network, such as the electronic lock 100. The mobile device 700 can then communicate with the server 114 via Wi-Fi or a mobile data connection. The mobile device 700 is thus able to operate to transmit information between the electronic lock 100 and the server 114. Figure 7 The mobile device 700 shown includes an input device 702, an output device 704, a processor 706, a wireless Wi-Fi interface 708, a wireless BLE interface 710, a power supply 712, and a memory 714.

[0101] Input device 702 is used to receive input from external sources. Such sources may include input received from a user (e.g., administrative user 106 or guest user 108) and / or input received from the electronic lock 100. For example, input received from a user may be received via a touchscreen, stylus, keyboard, microphone, camera, etc. In other examples, input received from the electronic lock 100 may be received via a camera, microphone, motion sensor (e.g., accelerometer, gyroscope, or other position or motion sensor) or other types of sensors. According to a particular example, guest mobile device 112 may be operable to receive a unique registration code presented by the electronic lock 100 via input device 702.

[0102] Output device 704 operates to provide information output from mobile device 700. In one example, a display is capable of outputting visual information. In another example, a speaker is capable of outputting audio information. In some examples, output device 704 can operate to present a unique registration code, which can be entered into or sensed by electronic lock 100, for verifying visitor user 108 and enabling secure registration mode of electronic lock 100. Furthermore, location data of mobile device 700 (such as GPS information) can be provided to electronic lock via output device 704 or any of the interfaces 708, 710 described below to provide further information about the current presence / location of mobile device 700.

[0103] Processor 706 operates to read data and instructions. For example, data and instructions may be stored locally, received from an external source, or accessed from removable media.

[0104] The Wi-Fi interface 708 can operate similarly to the Wi-Fi interface 614. For example, it can establish a Wi-Fi connection with the server 114.

[0105] The wireless (BLE) interface 710 can operate similarly to the Bluetooth interface 616. For example, it can establish a BLE connection with the electronic lock 100.

[0106] Power supply 712 can be operated to provide power to processor 706.

[0107] The memory 714 includes software applications 720 and an operating system 722. The memory 714 contains data and instructions that the processor 706 can use to implement various functions of the mobile device 700.

[0108] Software application 720 can include applications that can perform various functions on mobile device 700. One such application is client application 116. In one example implementation, when client application 116 runs on administrator mobile device 110, client application 116 can be configured to provide a user interface, receive an option to register visitor user 108 as a visitor user of electronic lock 100, and transmit the registration option to server 114 to generate a unique registration code that can be used to verify visitor user 108 and allow visitor user 108 to complete registration with electronic lock 100. In another example implementation, when client application 116 runs on visitor mobile device 112, client application 116 can be configured to provide a user interface, receive an option to complete registration with electronic lock 100 (e.g., when visitor mobile device 112 is near electronic lock 100), receive a unique registration code presented by electronic lock 100, and verify the received unique registration code or use server 114 to verify the received unique registration code. For example, after verifying the unique registration code, the electronic lock 100 can enter a secure registration mode, which allows the visitor user 108 to complete the registration with the electronic lock 100.

[0109] In some examples, when the electronic lock 100 is in secure registration mode, the electronic lock 100 can be triggered to enter Bluetooth pairing mode, which enables the guest mobile device 112 and the electronic lock 100 to perform a pairing process. When the pairing process is complete, the guest user 108 is able to perform at least a subset of electronic lock actions (e.g., actuate the electronic lock 100, add an access / actuation password) via the client application 116.

[0110] Now refer to Figure 8 An example flowchart of a method 800 for providing secure registration of visitor user 108 with electronic lock 100, for example, allowing an individual to register as a user of electronic lock without accessing internal components of electronic lock 100 (e.g., inside a house protected by electronic lock 100).

[0111] In operation 802, an option to add guest user 108 as a user of electronic lock 100 can be received. For example, the administrator user 106 of electronic lock 100 can use a client application 116 running on the administrator's mobile device 110 to notify the server 114 of a request to allow guest user 108 to register as a user of electronic lock 100. For example, a guest user account associated with electronic lock 100 can be created and stored on server 114. In some examples, the option to add guest user 108 as a user of electronic lock 100 may also include one or more access control options. In some examples, the option to add guest user 108 as a user of electronic lock 100 may also include the guest user's contact information (e.g., guest mobile device phone number, email address, social media identifier). One or more access control options and guest user contact information can be stored in association with the guest user account.

[0112] According to one aspect, the registration of a user with the electronic lock 100 using this disclosure can be enhanced with the inclusion of a verification process to ensure that the intended visitor user 108 is authorized to register as a user of the electronic lock 100. Therefore, in operation 804, a unique registration code can be generated for the verification process. For example, the unique registration code can be uniquely associated with a visitor user account of the electronic lock 100, which can be created based on one or more selections made by the administrator user 106 to add visitor user 108 as a user of the electronic lock 100. In some examples, the unique registration code can be generated by a client application 116 running on the administrator's mobile device 110 and transmitted to the server 114. In other examples, the unique registration code can be generated by the server 114. As mentioned above, the unique registration code can be a password unique to the visitor user registration selection / request and can be stored at the server 114 in association with the visitor user account of the electronic lock 100. In some examples, the unique registration code can represent a unique static or dynamic pattern of information that can be presented visually, audibly, or tactilely. Registration codes can represent any type of pattern or visual / auditory indicator (such as LEDs, visual numbers, etc.).

[0113] In operation 806, the registration invitation link can be transmitted to and received by the guest mobile device 112. For example, the registration invitation link can link to the guest user account of the electronic lock 100 and a unique registration code generated for the guest user's registration request. When selected, the registration invitation link can redirect the guest mobile device 112 to the login page of the client application 116.

[0114] At operation 808, a request to initiate registration with electronic lock 100 may be received. In some examples, the selection of the option to initiate registration with electronic lock 100 may be made by visitor user 108, received by visitor mobile device 112, and transmitted to server 114. In some examples, the option to initiate registration with electronic lock 100 may be included in the UI provided by client application 116. In one example, when client application 116 is running on visitor mobile device 112, and when visitor mobile device 112 is within short-range wireless communication range of electronic lock 100 and receives a short-range wireless communication beacon (e.g., BLE beacon) sent by electronic lock 100, client application 116 may provide the option to initiate registration in the client application UI. In other examples, in response to determining that it is near electronic lock 100 using GPS data captured at visitor mobile device, visitor mobile device 112 may provide the option to initiate registration in the client application UI. In some examples, in response to the selection to initiate registration, electronic lock 100 may also receive instructions from server 114 to initiate a registration code verification process.

[0115] In operation 810, a unique registration code associated with the registration invitation link and the guest user account can be transmitted to the electronic lock 100. In some examples, the unique registration code may be included in instructions received from server 114 to initiate the registration code verification process.

[0116] In operation 812, a unique registration code can be presented. In some examples, the electronic lock 100 can present the unique registration code using the code output interface 512. In one example, the unique registration code can be visually presented via one or more lights or a keypad 502. In other examples, the electronic lock 100 can audibly present the unique registration code by playing sound using a speaker or other sound-generating element that may be included in the electronic lock 100. In other examples, the electronic lock 100 can tactilely present the unique registration code by providing tactile feedback (such as vibration patterns) using tactile actuator elements that may be included in the electronic lock 100. In yet another example, the electronic lock 100 can visually present the unique registration code on a touchscreen or other display, for example, by presenting an alphanumeric code or other visual code on the display.

[0117] In yet another example implementation, the unique registration code may be presented by the guest mobile device 112. For example, the guest mobile device 112 may be instructed to display the unique registration code (e.g., on a screen), audibly play or inform the unique registration code (e.g., via a speaker), or tactilely present the unique registration code (e.g., via a haptic actuator). In some examples, the unique registration code may be shared with the guest user 108. For example, the unique registration code may be included in a registration invitation received by the guest mobile device 112. In other examples, the unique registration code may be transmitted to the guest mobile device 112 via server 114 in a separate message.

[0118] In operation 814, a unique registration code can be received in response to its presentation. In some examples, when the unique registration code is presented by the electronic lock 100, it can be sensed by sensors included in the guest mobile device 112. For example, a camera, microphone, accelerometer, or other input device 702 included in the guest mobile device 112 can be used to sense the displayed, played, or otherwise presented unique registration code. In other examples, the unique registration code presented by the electronic lock 100 can be observed by the guest user 108, who can input the unique registration code into the guest mobile device 112 using a touchscreen, stylus, keyboard, microphone, camera, or other input device 702 included in the guest mobile device 112.

[0119] In other examples, when the unique registration code is presented by the visitor's mobile device 112, the unique registration code may be sensed by an input interface 202 (e.g., a camera, microphone, tactile sensor) included in the electronic lock 100 or observed by the visitor user 108, who may enter the unique registration code using a keyboard 502 included in the electronic lock 100 or another input interface 202.

[0120] In operation 816, the presented unique registration code can be verified. For example, the received unique registration code can be compared with a unique registration code generated for and uniquely associated with the guest user account of the electronic lock 100. In some examples, before verification, the received unique registration code can be converted into a format in which it can be compared with the unique registration code associated with the guest user account.

[0121] In one example implementation, when a unique registration code is presented by the electronic lock 100 and received by the visitor's mobile device 112, the presented and received unique registration code can be verified by a client application 116 running on the visitor's mobile device 112. For example, as described above, the unique registration code can be included in a registration invitation sent to the visitor's mobile device 112; or, in response to the initiation of a registration code verification process by the electronic lock 100 or at another time, the unique registration code can be sent by the server 114 to the client application 116. In some examples, after verifying the unique registration code, the client application 116 can send a successful verification indication to the server 114.

[0122] In another example implementation, the visitor's mobile device 112 can send a unique registration code, both presented and received, to the server 114 for verification.

[0123] In another example implementation, when a unique registration code is presented by a visitor's mobile device 112 and received by the electronic lock 100, the electronic lock 100 can verify the received unique registration code. In some examples, after verifying the unique registration code, the client application 116 can send a successful verification indication to the server 114.

[0124] Alternatively, in another example implementation, the electronic lock 100 may send the presented and received unique registration code to the server 114 for verification.

[0125] In the various embodiments described above, one or more of the electronic lock 100, server 114, and client application 116 may additionally verify the location of the mobile device 112. This may be based, for example, on sensing the visitor's mobile device 112 at the electronic lock 100, or by determining the location of the visitor's mobile device 112 via GPS data at the client application 116, or sending the location to the server 114 and / or the electronic lock 100.

[0126] In operation 818, after successful verification of the unique registration code, the electronic lock 100 can enter a secure registration mode. In some implementations, the electronic lock 100 can receive instructions from the server 114 to enter the secure registration mode. For example, when the unique registration code is presented by the electronic lock 100 and verified by the guest mobile device 112 or the server 114, a successful verification indication can be transmitted to the electronic lock 100. In other examples, such as when the electronic lock 100 is configured to verify a unique registration code presented by the guest mobile device 112, the electronic lock 100 can operate to automatically enter the secure registration mode based on successful verification of the unique registration code. According to one aspect, when the electronic lock 100 enters the secure registration mode, the electronic lock 100 can operate to receive input of a lock actuation password that the guest user 108 can use to actuate the lock 100, or it can operate to enter a pairing mode in which the electronic lock 100 can communicate with the guest mobile device 112 via a short-range wireless connection (e.g., BLE connection) to receive lock actuation instructions from a client application 116 running on the guest mobile device 112.

[0127] During operation 820, visitor user 108 can be securely registered as a user of electronic lock 100. In some examples, during secure registration mode, visitor user 108 can use input interface 202 to enter a lock actuation password that can be registered with electronic lock 100, enabling visitor user 108 to actuate electronic lock 100. As an example, visitor user 108 can enter biometric features (such as fingerprints, retinal scans, facial features, voiceprints, etc.), or numbers, letters, or alphanumeric codes.

[0128] In other examples, during secure registration mode, the electronic lock 100 can enter pairing mode, where the lock and the visitor mobile device 112 can communicate and exchange information via a short-range wireless connection. For example, pairing the visitor mobile device 112 with the electronic lock 100 allows the electronic lock 100 to receive lock actuation commands from a client application 116 running on the visitor mobile device 112. Therefore, a visitor user 108 can use the electronic lock 100 to gain access to the house without first navigating the inside of the electronic lock 100 to register as a user of the lock. In some examples, the visitor user 108 can use the electronic lock 100 based on one or more access control choices made by the managing user 100.

[0129] Figures 9 to 15 Various graphical representations of the aspects of providing security registration for visitor user 108 and electronic lock 100 are shown. Now refer to... Figure 9 This illustrates a representation of a sample UI 902 that can be provided by an electronic lock application 116 running on an administrator's mobile device 110. For example, Figure 9The UI 902 shown is a representation of the UI that can be displayed on the screen 904 of the administrator's mobile device 110, and the administrator user 106 can use this UI to select to add the guest user 108 as a user of the electronic lock 100.

[0130] According to one aspect, UI 902 may include various options associated with selecting a new user to add to electronic lock 100. In some examples, administrator user 106 may have more than one electronic lock 100 associated with administrator user account, and UI 902 may include a list (not shown) of electronic locks 100 associated with the account from which administrator user 106 may select the desired lock. In some examples, when the desired electronic lock 100 is selected (either by administrator user 106 or automatically), UI 902 may include option 906 to add the user to electronic lock 100.

[0131] In some examples, after selecting option 906 to add a user, UI 902 may also include option 908 for entering information about the user (such as the user's name). In some examples, UI 902 may also include additional options such as option 910 for entering permission levels (e.g., guest user 108 to administrator user 106); option 912 for allowing the user to be mobile (e.g., using client application 116 to activate the lock); option 914 for allowing the user to activate the lock using input interface 202 of electronic lock 100 (e.g., fingerprint sensor, retinal scanner, camera including facial recognition, audio interface that can use voice recognition to actuate the lock, another type of biometric sensor, keypad 502); option 916 for allowing the user to change lock settings; option 918 for selecting the duration of access for the user; and one or more options 920 for sharing an invitation link with guest user 108. In some examples, the option 920 for sharing one or more invitation links may include the option to send the invitation link via text message, email, social media message, or another communication method.

[0132] In some examples, the option to share an invitation link via a specific communication method can be operated to instruct the administrator's mobile device 110 to open a communication application on the administrator's mobile device 110 and initiate a communication that includes an invitation link and can be sent to the guest user 108. For example, the administrator user 106 can enter the guest user's contact information and send an invitation link to the guest user 108.

[0133] In other examples, the option to share an invitation link via a specific communication method can be operated to provide an option to enter the visitor user's contact information and another option to send an invitation link. When the latter option is selected, the server 114 can be instructed to send an invitation link to the visitor user 108 based on the entered contact information.

[0134] In other examples, an option to copy the invitation link may be provided, allowing administrator user 106 to paste it into a communication that can be sent to guest user 108 via a specific communication method. It should be understood that additional and / or alternative options may be provided in UI 902, and these options are within the scope of this disclosure.

[0135] Now refer to Figure 10 An example messaging application user interface 1002 is shown displayed on the screen 1010 of a guest mobile device 112. For example, in response to the selection to add guest user 108 as a user of electronic lock 100, an example invitation message 1004 may be generated by the managing mobile device 110 or server 114. It should be understood that the format of the invitation message 1004 may vary based on various factors, such as the chosen communication method. For example, Figure 10 The example invitation message 1004 shown is a text message displayed in the text messaging application user interface 1010. However, in other examples, the invitation message 1004 could be an email, a social media message, or other types of communication.

[0136] As shown in the figure, the invitation message 1004 may include a registration invitation link 1006 next to the registration instruction 1008. In some examples, selecting the registration invitation link 1006 may redirect the visitor's mobile device 112 to the login page of the client application 116. If the client application 116 has not yet been downloaded to the visitor's mobile device 112, the visitor's mobile device 112 may initially be redirected to a location where the client application 116 can be accessed and downloaded (e.g., a mobile app store or webpage associated with server 114). As mentioned above, in some examples, the registration invitation link 1006 may link to the visitor user account and unique registration code of the electronic lock 100, which may be created based on a request to invite the visitor user 108 as an administrator user of the electronic lock 100.

[0137] Now refer to Figure 11 The diagram illustrates a representation of an example UI 1102 that the client application 116 can operate to display on the screen 1010 of the guest mobile device 112. For example, after the client application 116 is installed or opened on the guest mobile device 112, the example UI 1102 may be included in a login page displayed by the client application 116. In some examples, and as shown, UI 1102 may include an option 1104 for initiating registration with the electronic lock 100. For example, in response to the selection of option 1104 for initiating registration, communication may be provided to the electronic lock 100 to initiate a registration code verification process.

[0138] Now refer to Figure 12An illustration is provided showing a visitor user 108 and a visitor mobile device 112 near an electronic lock 100, and a unique registration code 1202 presented by the electronic lock 100 and captured by the visitor mobile device 112. According to one aspect, when the visitor user 108 is near the electronic lock 100, the visitor user 108 can select option 1104 to initiate registration. For example, the electronic lock 100 can present the unique registration code 1202 via a code output interface 512, which in the illustrated example includes a plurality of lights or LEDs that can be illuminated to visually present the unique registration code 1202. Further, the visitor mobile device 112 can be operated to capture the presented unique registration code 1202 via an input device 702, which in the illustrated example includes a camera. For example, the captured unique registration code 1202 can be compared with a unique registration code 1202 stored associated with the visitor user account of the electronic lock 100.

[0139] In some examples, after verifying the presented unique registration code 1202, the electronic lock 100 can receive verification communication, which can initiate a secure registration mode. In some examples, when the electronic lock 100 is in secure registration mode, the lock can be enabled to receive the lock actuation password to be registered with the electronic lock 100. In one example, and as... Figure 13 As shown, the lock actuation password can be the biometric attribute of the visitor user 108, such as a fingerprint, which can be received by the electronic lock 100 via the input interface 202 (such as a fingerprint sensor). In another example, and as... Figure 14 As shown, the lock actuation password can be an alphanumeric password, which can be received by the electronic lock 100 via an input interface 202 (such as a keypad 502).

[0140] In some examples, when the electronic lock 100 is in a secure registration mode, it can be enabled to enter a pairing mode. This allows the electronic lock 100 to communicate 1502 with a mobile device (e.g., a guest mobile device 112) within short-range wireless communication range, enabling the mobile device to pair with the electronic lock 100. For example, when the guest mobile device 112 and the electronic lock 100 are paired, a client application 116 running on the guest mobile device 112 can be used to send a lock actuation command to the electronic lock 100, and the electronic lock 100 can operate to receive and execute the lock actuation command for moving the latch 214 between a locked position and an unlocked position.

[0141] Overall reference Figures 1 to 15Although this disclosure generally describes a pairing arrangement in which the electronic lock 100 transmits a registration code to the guest mobile device 112, in alternative embodiments, such as where the electronic lock 100 also includes a camera (not shown), the guest mobile device 112 can be configured to output a unique registration code 1202 via a flash device (e.g., a camera) included in the input device 702, which is captured by the electronic lock's camera. In this case, in response to the selection of a registration invitation link, the unique registration code is provided to the mobile device, and the electronic lock can be configured to capture the unique registration code and enter a secure registration mode after verification (e.g., at the electronic lock or via a cloud account, such as at server 114). For this arrangement, the above process is generally equivalent.

[0142] For example, embodiments of the invention have been described above with reference to block diagrams and / or operational examples of methods, systems, and computer program products according to embodiments of the invention. Functions / actions marked in blocks may not occur in the order shown in any flowchart. For example, depending on the functions / actions involved, two blocks shown consecutively may actually be executed substantially simultaneously, or these blocks may sometimes be executed in reverse order.

[0143] The descriptions and illustrations of one or more embodiments provided in this application are not intended to limit or restrict the scope of the claimed invention in any way. The embodiments, examples, and details provided in this application are considered sufficient to convey ownership and enable others to make and use the best mode of the claimed invention. The claimed invention should not be construed as limited to any embodiments, examples, or details provided in this application. Various features (structural and methodological) are intended to be selectively included or omitted, whether in combination or separately, to produce embodiments with a particular set of features. Having provided the descriptions and illustrations of this application, those skilled in the art can contemplate variations, modifications, and alternative embodiments falling within the spirit of a broader aspect of the overall inventive concept embodied in this application, without departing from the broader scope of the claimed invention.

Claims

1. An electronic lock, comprising: A latch assembly including a pin movable between a locked position and an unlocked position; A motor configured to receive an actuation command that causes the motor to move the pin from the locked position to the unlocked position or from the unlocked position to the locked position; A wireless circuit configured to wirelessly communicate with a client application installed on a mobile device; Code output interface, which is configured to present a unique registration code; At least one processor; as well as A memory, communicatively connected to the at least one processor, stores instructions that, when executed, cause the electronic lock to: Receive a unique registration code associated with the registration invitation link provided to the guest user; In response to receiving an instruction to initiate a registration code verification process based on the selection of the registration invitation link, the unique registration code is presented via the code output interface; as well as In response to receiving an indication that the unique registration code has been received and verified by the mobile device, the system enters a secure registration mode, which enables the guest user to register as a user of the electronic lock.

2. The electronic lock of claim 1, wherein the registration invitation link includes a token linked to a visitor user account associated with the electronic lock.

3. The electronic lock according to claim 1, wherein the unique registration code is a visual password presented by illuminating one or more lights included in the electronic lock according to a specific pattern.

4. The electronic lock according to claim 1, wherein the unique registration code is an auditory password presented by generating sound according to a specific pattern or frequency using a sound-generating element included in the electronic lock.

5. The electronic lock according to claim 1, wherein the unique registration code is a tactile password presented by generating vibrations according to a specific pattern using a tactile actuator element included in the electronic lock.

6. The electronic lock according to claim 1, wherein the unique registration code and the registration invitation link are created based on a request from the electronic lock's managing user to add the guest user as a user of the electronic lock.

7. The electronic lock according to claim 1, wherein when the electronic lock enters the security registration mode, the instruction causes the electronic lock to: Receive the lock actuation password; and The lock actuation password is stored, and subsequent input of the lock actuation password causes the at least one processor to execute the actuation command to cause the motor to move the pin from the locked position to the unlocked position or from the unlocked position to the locked position.

8. The electronic lock according to claim 7, wherein the lock actuation password includes: Biometric password received via biometric input interface; or Alphanumeric password received via keyboard.

9. The electronic lock according to claim 1, wherein when the electronic lock enters the security registration mode, the instruction causes the electronic lock to: Enter wireless communication pairing mode; and When the mobile device is within the wireless communication range of the electronic lock, a wireless communication channel is established with the mobile device.

10. The electronic lock of claim 9, wherein the instruction further causes the electronic lock to: Pair with the mobile device; Receive actuation commands from a client application installed on the mobile device; and The actuation command is executed to cause the motor to move the pin from the locked position to the unlocked position or from the unlocked position to the locked position.

11. A method for providing secure registration of a user with an electronic lock, wherein the electronic lock comprises: A latch assembly including a pin movable between a locked position and an unlocked position; A motor configured to receive an actuation command that causes the motor to move the pin from the locked position to the unlocked position or from the unlocked position to the locked position; A wireless circuit configured to wirelessly communicate with a client application installed on a mobile device; Code output interface, which is configured to present a unique registration code; At least one processor; as well as The memory is communicatively connected to the at least one processor; The method includes: Receive a unique registration code associated with the registration invitation link provided to the guest user; In response to receiving an instruction to initiate a registration code verification process, the unique registration code is presented via the code output interface; and In response to receiving an indication that the unique registration code has been received and verified by the mobile device, the system enters a secure registration mode, which enables the guest user to register as a user of the electronic lock.

12. The method of claim 11, wherein presenting the unique registration code comprises one of the following: One or more lights included in the electronic lock are illuminated according to a specific pattern; Sound is generated according to a specific pattern or frequency using a sound-generating element included in the electronic lock; or Vibrations are generated according to a specific pattern using tactile actuator elements included in the electronic lock.

13. The method of claim 11, further comprising, when the electronic lock enters the security registration mode: Receive the lock actuation password; and The lock actuation password is stored, and subsequent input of the lock actuation password causes the at least one processor to execute the actuation command to cause the motor to move the pin from the locked position to the unlocked position or from the unlocked position to the locked position.

14. The method of claim 13, wherein receiving the lock actuation password comprises: Receive biometric passwords received via the biometric input interface; or Receive alphanumeric passwords received via the keyboard.

15. The method of claim 11, further comprising, when the electronic lock enters the security registration mode: Enter wireless communication pairing mode; and When the mobile device is within the wireless communication range of the electronic lock, a wireless communication channel is established with the mobile device.

16. The method of claim 15, further comprising: Pair with the mobile device; Receive the actuation command from the client application installed on the mobile device; as well as The actuation command is executed to cause the motor to move the pin from the locked position to the unlocked position or from the unlocked position to the locked position.

17. A system for providing secure registration of a user with an electronic lock, the system comprising: At least one processor; as well as A memory, communicatively connected to the at least one processor, stores instructions that, when executed, cause the system to: In response to receiving a selection of a registration invitation link and a unique registration code associated with a guest user account of the electronic lock, a user interface is provided on the mobile device including the option to initiate registration with the electronic lock; When the mobile device approaches the electronic lock, it receives a selection of an option to initiate registration with the electronic lock; The server is notified of the selection made to initiate registration; The user interface receives input of the unique registration code presented by the electronic lock based on the selection to initiate registration; as well as The presented unique registration code is verified by comparing it with the unique registration code associated with the registration invitation link, so that the electronic lock can enter the secure registration mode, which allows visitor users to register as users of the electronic lock.

18. The system of claim 17, wherein the registration invitation link is created in response to an option made via an administrative account associated with the electronic lock to add the visitor user as a user of the electronic lock.

19. The system of claim 17, wherein upon receiving the input of the unique registration code, the system is operable to receive: A visual code, which is presented as illuminating one or more lights included in the electronic lock according to a specific pattern; An auditory code, which is presented as sound generated by a sound-generating element included in the electronic lock according to a specific pattern or frequency; or The tactile code is presented as vibrations generated according to a specific pattern by tactile actuator elements included in the electronic lock.

20. The system of claim 17, wherein, before providing a user interface including the option to initiate registration with the electronic lock, an option to establish a password for accessing the guest user account is provided via the user interface.

Images