AU2021381391A1 - Virtual entry system - Google Patents

Abstract

A system and method are disclosed for providing access to a secure area. The method includes receiving, from a mobile device, a selection associated with information related to a navigation interface, sending, to the mobile device in response to receiving the selection, information related to a communication interface, the information related to the communication interface including a meeting code and receiving, from the mobile device, a first request to initiate a communication session between the mobile device and an electronic device, the first request including the meeting code. The method further includes initiating, based on the first request, a communication session between the mobile device and the electronic device and receiving a second request to unlock a door of the building in response to the communication session.

Description

VIRTUAL ENTRY SYSTEM

PRIORITY CLAIM

[0001] This application claims the benefit of U.S. Application No. 17/100,798, filedNovember 20, 2020 and U.S. Provisional Application No. 63/187,049, filed June 4, 2021, the disclosures of which are expressly incorporated by reference herein in their entirety.

FIELD

[0002] In one exemplary aspect, the present disclosure is related to devices and methods for connecting to a virtual private network (VPN), and it is further related to using the VPN connection to route information between a remote server and a computing device, for example to facilitate a virtual entry system for a secured space, such as a building.

BACKGROUND

[0003] In general, connecting to a VPN requires a user to authenticate their identity by logging into the VPN. Once authenticated, the user can access data and connect to servers communicatively coupled to the VPN. However, if a user experiences network connectivity issues, the connection to the VPN may be lost, requiring the user to again log into the VPN.

[0004] Conventional virtual entry systems may include one or more guest call boxes located outside a building and a resident call box in one or more rooms of the building. If the building includes multiple units, then a resident call box may be placed inside each of the units. Therefore, the number of call boxes needed to service a building can increase with the number of units, resulting in high initial and maintenance costs. In the alternative, virtual entry systems may employ the resident cell phone or landline for buzzing in residents. However, the installation and maintenance of the guest call box is still significant.

[0005] Systems and techniques are needed to provide greater ease of connecting to a VPN. In addition, systems and techniques are needed to reduce or eliminate the number of call boxes required to service a building, which may include use of improved systems and techniques for connecting to a VPN.

SUMMARY

[0006] Systems and techniques are described herein for connecting to a VPN. For example, a microcontroller attachment that includes network interface controllers (NICs) can be attached to a microcontroller, and a computing device can be communicatively coupled (e.g., using an electrical cable) to the microcontroller attachment to connect the computing device to a VPN. [0007] In some cases, the microcontroller attachment and microcontroller can be components of an entry subsystem. The computing device can be an electronic lock, which can connect to a virtual private network to which a virtual entry server is communicatively coupled. A guest arriving at a building can use the entry subsystem and virtual entry server to initiate a communication session between the guest’s mobile device or a smart building communication device and an electronic device of a resident of the building. The resident can use the electronic device to unlock a door of the building, allowing the guest to enter.

[0008] In one example, a method performed by a system of one or more computers for operating a virtual entry system for a building is provided. The method includes receiving, from a mobile device, a selection associated with information related to a navigation interface, initiating, based on the selection, a communication session between an electronic device and a smart building communication device, and receiving an unlock request to unlock a door of the building in response to the communication session.

[0009] This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used in isolation to determine the scope of the claimed subject matter. The subject matter should be understood by reference to appropriate portions of the entire specification of this patent, any or all drawings, and each claim.

[0010] A bank of statements is provided at the end of this specification which also sets forth various examples related to the subject matter of this case. Note that any specific feature of any example can be integrated with any other feature of any other example. The examples are not meant to be described as independent embodiments but rather examples in which various features can be mixed and matched with other features of other examples.

[0011] The foregoing, together with other features and embodiments, will become more apparent upon referring to the following specification, claims, and accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Illustrative examples of the present application are described in detail below with reference to the following figures:

[0013] FIG. 1 A is block diagram of a microcontroller system that includes a microcontroller attachment communicatively coupled to a microcontroller;

[0014] FIG. IB is a block diagram of a microcontroller device;

[0015] FIG. 2 is a block diagram of another microcontroller system that includes a microcontroller attachment communicatively coupled to the microcontroller of FIG. 1A.

[0016] FIG. 3, a block diagram of a virtual entry system that includes a virtual entry server communicatively coupled to an entry subsystem;

[0017] FIG. 4 is a swim lane diagram illustrating actions performed by the components of the virtual entry system of FIG. 3; [0018] FIG. 5 is a flow diagram illustrating an example of a process for operating a virtual entry system for a building;

[0019] FIG. 6A is a flow diagram illustrating an example of a process for receiving a request to unlock a door;

[0020] FIG. 6B is a flow diagram illustrating another example of a process associated with a request to unlock a door;

[0021] FIG. 6C illustrates a flow diagram illustrating another example associated with a process to unlock a door;

[0022] FIG. 7, a block diagram of an alternative examples of a virtual entry system that includes a virtual entry server communicatively coupled to an entry subsystem;

[0023] FIG. 8 is a swim lane diagram illustrating actions performed by the components of the virtual entry system of FIG. 7;

[0024] FIG. 9 is a flow diagram illustrating an example of a process for operating a virtual entry system for a building;

[0025] FIG. 10 is a flow diagram illustrating an example of a process for receiving a request to unlock a door;

[0026] FIGS. 11A-1 IB represent various method examples;

[0027] FIGS. 12-13 illustrate further method examples related to access to secure spaces;

[0028] FIGs. 14A-14C illustrate various method examples;

[0029] FIG. 15 includes a system for using a FOB or other device to gain access to a secure space;

[0030] FIGs. 16A-16B illustrate method examples associated with the use of a FOB or similar device; and

[0031] FIG. 17 is a diagram illustrating an example of a system for implementing certain aspects of the present technology.

DETAILED DESCRIPTION

[0032] Certain aspects and examples of this disclosure are provided below. Some of these aspects and examples may be applied independently and some of them may be applied in combination as would be apparent to those of skill in the art. In the following description, for the purposes of explanation, specific details are set forth in order to provide a thorough understanding of examples of the application. However, it will be apparent that various examples may be practiced without these specific details. The figures and description are not intended to be restrictive. [0033] The ensuing description provides examples only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the examples will provide those skilled in the art with an enabling description for implementing an example system. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the application as set forth in the appended claims.

[0034] Virtual Private Networks (VPNs) provide a secure way for users to remotely connect an electronic device to a network (e.g., an office or school network) in which the device would otherwise not be within proximity of. Connecting to a VPN typically includes first connecting to a local network, then entering one or more credentials into a VPN interface. If the connection to the VPN is lost (e.g., if a device loses its connection to the local network) then a user must typically reenter their credentials. Therefore, a connection loss can be frustrating and timeconsuming.

[0035] As can be appreciated, the process of connecting to a VPN can be simplified using a device that establishes a VPN connection with little or no input from a user. In that regard, examples are described herein of a microcontroller device for connecting to a VPN that establishes a VPN connection with little or no input from a user.

[0036] In one example, the microcontroller device includes a pair of network interface controllers (NICs). In another example, a microcontroller attachment is coupled to a microcontroller and the microcontroller attachment includes a pair of NICs. A first network interface controller (NIC) can be configured to communicate with a first dynamic host configuration protocol (DHCP) server and establish a VPN connection. A second NIC can be configured to receive a second DHCP address from a second DHCP server running on the microcontroller or the microcontroller device and send the second DHCP address to a device capable of connecting to a network. The device capable of connecting to the network can connect to the VPN through a communicative coupling to the microcontroller device, e.g., through a coupling to the first or second NIC.

[0037] Such an exemplary microcontroller device can be used to simplify the process of connecting a computing device to a VPN. For example, in some implementations, the computing device can simply be plugged into the microcontroller device to connect to a VPN, reducing or eliminating any additional steps (e.g., log in steps) required when establishing the VPN connection. For example, conventional systems may require a user to connect to a network and input a password. In addition, because the computing device can send and receive data through a physical coupling, the chance of being disconnected from the VPN due to a network error can be reduced or eliminated. In general, the computing device can be any electronic device that can connect to a network.

[0038] The exemplary microcontroller device may be used to improve secure network systems. For example, the microcontroller device described herein can be used to facilitate remote, secure entry of a building. In that regard, virtual entry systems and methods for facilitating remote, secure communication between a resident (or other building personnel) of a building and a guest (to enable, for instance, remote, secure entry to the resident’s building) are described herein. For example, a guest arriving at a building can receive on their mobile device a navigation interface that the guest can use to enter or search for a name or unit number of a particular resident of the building. Upon selecting the name or unit number of the particular resident, a virtual entry server can send to the guest’s mobile device information related to a communication interface, such as a meeting code, to initiate a communication session between the mobile device and an electronic device of the particular resident (or other building personnel). In another example, the virtual entry server can send information to at least one of an internet protocol (IP) camera(s), a smart door bell, etc. (hereinafter sometimes simply referred to as a “smart building communication device” or a “connected building computing device”), to facilitate a communication session between the smart communication device and an electronic device of the particular resident (or other building personnel).

[0039] In further aspects, the resident can remotely unlock the door of the building, for example, by selecting an option to unlock the door using a user interface of the electronic device, which communicates the request to unlock the door to the virtual entry server. The door can be physically coupled to an electronic lock. In response to the request to unlock the door, the virtual entry server can transmit a signal to an entry subsystem that includes or is communicatively coupled to the electronic lock. Upon receiving the signal from the virtual entry server, the entry subsystem can communicate instructions to the electronic lock to unlock the door, allowing the guest to enter the building.

[0040] To ensure the security of the virtual entry process described above, the virtual entry system includes an entry subsystem having a microcontroller device connected to a VPN to which the virtual entry server is also connected. The microcontroller device can ensure communications between the entry subsystem and the virtual entry server are secure. In one example, the entry subsystem uses the microcontroller device shown and described with respect to FIGURES 1 A, IB, and/or 2.

[0041] The microcontroller device, together with the connected computing device(s), may define components of an example of a virtual entry system. Such virtual entry systems and their methods of use provide advantages at least in terms of reducing on-site hardware for secure building entry. For example, guest call boxes that are typically placed outside of a building and resident call boxes that are typically placed inside each unit of a building can be replaced with the components of the virtual entry system. As a result, instead of communicating using call boxes, a guest and resident can simply use their respective computing devices to communicate. Therefore, building managers can save time and money by avoiding the initial installation of the call boxes, the cost to power the call boxes, and their downstream maintenance and operation costs. Furthermore, conventional call boxes can be prone to hardware failures, which can be reduced or eliminated by implementing the disclosed virtual entry system. In addition, the virtual entry system provides an alternative for those buildings, especially older buildings, that may not include certain physical requirements to support a conventional call box (e.g., in terms of electrical wiring in the building).

[0042] Various aspects of the systems and methods described herein will be discussed below with respect to the figures. More specifically, examples of an improved microcontroller system (or device) for connecting to a VPN will first be described with respect to FIGURES 1A, IB, and 2. Thereafter, an example of a virtual entry system having an entry subsystem, which may be defined at least in part by a microcontroller device connected to a VPN to which a virtual entry server is also connected (such as the microcontroller device shown and described with respect to FIGURES 1 A, IB, and/or 2), will be described with respect to FIGURES 3-7.

[0043] FIG. 1A is block diagram of an example of a microcontroller system 100A that includes a microcontroller attachment 110 communicatively (and optionally physically) coupled to a microcontroller 120. In general, the microcontroller 120 provides basic computing functionality, and the microcontroller attachment 110 provides added computing functionality to the microcontroller 120 for connecting to a VPN in a simplified manner. Although examples of the microcontroller system 100A will be described herein as having a microcontroller attachment 110 communicatively (and optionally physically) coupled to a microcontroller 120, it should be appreciated that the microcontroller attachment 110 and microcontroller 120 may instead be configured as an integrated microcontroller device, as described in greater detail with respect to FIG. 2. In that regard, the term “microcontroller device” may be generally used herein when describing improved systems and techniques for connecting to a VPN.

[0044] The microcontroller 120 can be any single board computer that includes a microprocessor. In some implementations, the microcontroller 120 is a Raspberry Pi microcontroller, such as a Raspberry Pi Zero or an Orange Pi microcontroller such as an Orange Pi Zero LTS. The microcontroller 120 includes a microprocessor 122, which can be any integrated circuit that includes a central processing unit (CPU). The microcontroller 120 can further include a memory 126, which can store data to be retrieved by one or more of the components of the microcontroller.

[0045] The microcontroller 120 further includes a power input 124, which can be an electrical connection through which the microcontroller can receive electrical power. In some implementations, the power input 124 can receive electrical power from a power grid (not shown). In the example of FIG. 1A, the power input 124 receives electrical power from a first network interface controller (NIC) 102 of the microcontroller attachment 110 through an electrical connection to the first NIC 102.

[0046] The microcontroller 120 can further include a communications module (comms module) 126. The communications module 128 can include one or more of an Ethernet port, an integrated wireless local area network (LAN), a Bluetooth communications unit, and one or more ports such as an HDMI, mini-HDMI, or USB port.

[0047] The microcontroller 120 is communicatively coupled to the microcontroller attachment 110 for connecting a computing device 130 to a network, such as a VPN. More specifically, in the depicted example, the microcontroller attachment 110 includes the first NIC 102, which is communicatively coupled to the microcontroller 120 via one or more electrical connections. The first NIC 102 is configured to communicate with a first DHCP server 140 e.g., to retrieve a DHCP address over a network. The first NIC 102 is also configured to communicatively couple to the computing device 130. For example, the first NIC can include an Ethernet port, to which the computing device 130 can couple using an Ethernet cable. In some implementations, the first NIC 102 receives power (e.g., through a power over Ethernet (POE) network switch). The first NIC 102 is further configured to establish a VPN connection to which the computing device 130 can connect.

[0048] The microcontroller attachment 110 further includes a power output 106 and a power input 108. The power input 108 can be an electrical connection through which the microcontroller attachment 110 can receive electrical power. The power input 108 can receive an electrical current e.g., through a power cable that connects to the power input. In some examples, the power input 108 is a 48 V DC power input. For instance, the power input 108 can receive electrical power from a power grid. In an alternative example, the power input 108 can receive electrical power from the microcontroller 120.

[0049] The power output 106 can be used to output electrical power (e.g., by connecting a current carrying wire to the power output). The power output 106 can output an electrical current (e.g., a direct current (DC)). For example, the power output 106 can be a 12 V DC power output. The power output 106 can be used, for instance, to provide output power to at least one of the computing device 130 and the microcontroller 120. In some implementations, the power output 106 is omitted from the microcontroller attachment 110, such as in instances where output power can be provided by other sources (e.g., the microcontroller 120, the power grid, etc.).

[0050] The microcontroller attachment 110 also includes a second NIC 104, which is configured to supply a DHCP address (e.g., a DHCP address received from the first NIC 102) to the computing device 130. For example, the first NIC 102 and the second NIC 104 can be communicatively coupled by an Ethernet cable. As another example, the second NIC 104 receives a second DHCP address from a second DHCP server (not shown) running on or communicatively coupled to the microcontroller 120. The second NIC 104 can send the second DHCP address to the computing device 130. In some implementations, the microcontroller 120 includes a microcontroller NIC (not shown) that can run its own DHCP server and retrieve a DHCP address from said DHCP server. The microcontroller 120 can send the DHCP address to the computing device 130 or to the microcontroller attachment 110, which can send the DHCP address to the computing device.

[0051] In some implementations, the second NIC 104 receives power from the first NIC 102 (e.g., through POE). While not shown in the example microcontroller system 100A of FIG. 1 A, in some implementations, the second NIC 104 is communicatively coupled to the computing device 130 (e.g., through an Ethernet cable). In some implementations, the second NIC 104 is configured to supply power (e.g., power received from the first NIC 102) to the computing device 130 using POE.

[0052] The microcontroller system 100A can be used to establish a VPN connection for a computing device 130 using the following exemplary steps. In one step, the microcontroller attachment 110 is configured for connecting to a VPN. For example, the manufacturer can preconfigure the microcontroller attachment 110 by loading information related to the VPN client onto a memory of the microcontroller attachment 110 (not shown). This can allow the VPN client to sync and/or log into a VPN concentrator maintained by a remote host such as a cloud service provider. Syncing and/or logging into the VPN concentrator can facilitate access to the cloud service provider by the computing device 130.

[0053] In another step, the microcontroller attachment 110 can be communicatively coupled to a network 150. In some implementations, one or more of the first NIC 102 and the second NIC 104 is communicatively coupled to the network 150. For example, an Ethernet cable can be used to connect the first NIC 102 and/or the second NIC 104 to a modem to establish a network connection. The microcontroller attachment 110 can then establish a connection to a VPN router. Data can be transferred between the first NIC 102 and the second NIC 104 and between the first and second NICs and the VPN router.

[0054] Once connected to the VPN, the microcontroller attachment 110 can establish a secure connection to a remote server 160 using the first NIC 102 and the VPN connection. The microcontroller attachment 110 can include an LED that is illuminated to indicate that the secure connection to the remote server 160 was established. In general, the remote server 160 can be any server to which a user wants to connect their computing device 130 (which is communicatively coupled to the microcontroller attachment 110 through the first NIC 102). Therefore, the type of server can vary depending on the computing device to be connected. For example, the server 160 can be a network video recorder (NVR) server, a voice over internet protocol (VoIP) server, or a virtual entry server, to name a few examples. The computing device 130 can be any electronic device that can connect to a network. For example, the computing device 130 can be a camera, a phone, a printer, a laptop, or a virtual entry subsystem, as described in greater detail below.

[0055] In another step, a user can connect the computing device 130 to the microcontroller attachment 110. For example, an Ethernet cable can be used to connect the computing device 130 to the first NIC 102 of the microcontroller attachment 110. Once connected, the computing device 130 can connect to the VPN and use the secure connection established by the microcontroller attachment 110 to connect to the remote server 160. Therefore, by connecting the computing device 130 to the VPN, it can access cloud and remote services provided by the remote server 160. For instance, in some implementations, a user can connect to a webpage using the computing device 130 (or a mobile device communicatively coupled to the computing device 130) to establish certain network configurations. For example, the network configurations can include the static IP for the first NIC 102, the hostname, and a DHCP network range for the second NIC 104. In some implementations, the first NIC 102 is configured to have a static IP (e.g., instead of retrieving an IP address via the DHCP server).

[0056] The foregoing description is directed to a microcontroller attachment 110 configured to be communicatively (and optionally physically) coupled to the microcontroller for connecting a computing device to a VPN. However, in some implementations, as noted above, an integrated microcontroller device can include one or more components of the microcontroller attachment 110 and the microcontroller 120, and the integrated microcontroller device can be configured to perform one or more functions that can be performed by the combination of the microcontroller attachment and the microcontroller. [0057] FIG. IB depicts a block diagram of an example of an integrated microcontroller device 180. In general, the microcontroller device 180 includes some or all of the components of the microcontroller attachment 110 and the microcontroller 120 described above. In that regard, the microcontroller device 180 includes the first NIC 102, the second NIC 104, the power input 108, and the optional power output 106 of the microcontroller attachment 110. Moreover, the microcontroller device 180 includes the microprocessor 122, the memory 126, and the communications module 128 of the microcontroller 120.

[0058] Like the microcontroller attachment 110, the microcontroller device 180 is communicatively coupled to the computing device 130 and the first DHCP server 140 through the first NIC 102. Moreover, the microcontroller device 180 is communicatively coupled to the remote server 160 through the network 150 via the interface of the second NIC 104.

[0059] With this integrated architecture, the microcontroller device 180 can establish a VPN connection in substantially the same manner described above with respect to the microcontroller attachment 110.

[0060] Based on the foregoing, it can be appreciated that the microcontroller attachment 110 and microcontroller 120 may be configured as an integrated microcontroller device as described herein without departing from the scope of the present disclosure. Such an integrated microcontroller device may be developed, for instance, as an original equipment manufacturer (OEM) device specific for an intended application, such as the virtual entry system described below. Comparatively, the microcontroller attachment 110 may be designed as a specific addon for use with existing, commercially available microcontrollers.

[0061] As noted above, in one application, the exemplary microcontroller device may be used in an entry subsystem of a virtual entry system. A “virtual entry system” can be understood to facilitate entry to a building (or other secured space) without requiring a human to physically unlock a door or other secured entry point of the building. Such virtual entry systems can include entry subsystems that can receive commands from a remote server, such as a virtual entry server communicatively coupled to the entry subsystem over a network. For example, the commands received by the entry subsystem can include a command directed to unlocking a door of a building.

[0062] FIG. 2 is a block diagram of an alternative example of a microcontroller system 200 for use in an exemplary entry subsystem of a virtual entry system. In the depicted example, the microcontroller system 200 has a microcontroller attachment 210 communicatively coupled to the microcontroller 120. Like the microcontroller attachment 110, the microcontroller attachment 210 includes the first NIC 102, the second NIC 104, the power output 106, and the power input 108. The microcontroller attachment 210 additionally includes components that facilitate the use of the microcontroller attachment 210 as a component in an entry subsystem for a virtual entry system.

[0063] For instance, in one aspect, the microcontroller attachment 210 can include a request exit button 216, which can be used to manually request that a lock be unlocked (e.g., a lock to which the entry subsystem is communicatively coupled to).

[0064] The microcontroller attachment 210 may also include a power converter 212, which can be electrically coupled to the power input 108, the first NIC 102, and a jumper 214. For example, the power converter 212 can be a buck converter, such as a stepdown buck converter. The power input 108 can power the power converter 212, which can receive power through a power over Ethernet (POE) connection to the first NIC 102. For example, the power converter 212 can be used to convert the power received from the first NIC 102 to 12 V DC. The power converter can also supply a current to the jumper 214 (e.g., 500 mA or more, 1 A or more).

[0065] The jumper 214 can also be used to supply power to a relay 218. Tripping relay 218 (e.g., changing a state of the relay such that a current through a wire connected to the relay is either started or stopped) causes a lock to which the microcontroller attachment 210 is connected to be locked or unlocked. For example, pressing the request exit button 216 can unlock a lock by tripping relay 218.

[0066] The microcontroller attachment 210 can also include a relay controller 220, which can adj ust the amount of time that the relay 218 remains tripped, therefore adj usting the amount of time that the lock remains unlocked. For example, the relay controller 220 can be a potentiometer. The amount of time that the relay 218 remains tripped can be in the interval of 3 seconds to 1 minute (e.g., 5 seconds or more, 10 seconds or more, 20 seconds or more).

[0067] In the example of FIG. 2, the microcontroller attachment 210 includes a light 222. For example, the light 222 can be an LED. As described above, the microcontroller attachment 210 can establish a VPN connection. In some implementations, the microcontroller attachment 210 can activate the light 222 to indicate that the VPN connection has been successfully established. In other implementations, the microcontroller attachment 210 can activate the light 222 to illuminate an area surrounding the microcontroller attachment. In still other implementations, the light 222 is omitted from the microcontroller attachment 210.

[0068] The microcontroller attachment 210 may further include a reset button 224. In some implementations, the reset button 224 is used to reset the connection of the microcontroller attachment 210 to the remote server 160, a VPN, or another network. [0069] FIG. 3 depicts a block diagram of an example of a virtual entry system 300. In the depicted example, the virtual entry system 300 includes a virtual entry server 320 communicatively coupled to an entry subsystem 340 through a network 150. The entry subsystem 340 may be communicatively coupled to the network 150 through the microcontroller system 200. It should be appreciated that the microcontroller system 100A and/or the microcontroller device 180 described above may instead be used to define at least a portion of the entry subsystem 340. Moreover, it should be appreciated that the entry subsystem 340 may be communicatively coupled to the network 150 through any other suitable VPN device or system configured to provide a secure connection between the virtual entry server 320 and the entry subsystem 340.

[0070] The network 150 can be any kind of network capable of enabling communication between the various components of FIGs. 1A, IB, 2, and 3 (e.g., between the microcontroller attachment 110 or 210 and the remote server 160, between the microcontroller device 180 and the remote server 160, and between the mobile device 312, the electronic device 314, the virtual entry server 320, and the entry subsystem 340). For example, the network can be a WiFi network.

[0071] A mobile device 312 of the guest 302 and an electronic device 314 of a resident 304 are connected to the network 150. The mobile device 312 can be any mobile electronic device that is capable of sending and receiving information over a network. For example, the mobile device 312 can be a smartphone, a wearable electronic device, or a tablet computer. The electronic device 314 can be any electronic device that is capable of participating in a communication session. For example, the electronic device 314 can be a smartphone, a landline, a wearable electronic device, a tablet computer, or another electronic device that includes a telephone service application (e.g., a plain old telephone service (POTS) application), a softphone application, a voice over internet protocol (VoIP) application, or video-chat application. In other examples, the electronic device 314 is a device that is housed in the secured location, building, or property 350. For example, the electronic device 314 can be an electronic kiosk or smart home system. In other examples, the electronic device 314 is tied to building personnel other than the resident.

[0072] The virtual entry server 320 includes a communication module 322 and an identifier database 324. The identifier database 324 maintains one or more identifiers that are specific to names and/or unit numbers of residents of buildings, such as the resident 304 of the building 350. The communication module is configured to facilitate a communication session between the mobile device 312 and the electronic device 314, as described in greater detail below with respect to FIG. 4.

[0073] The entry subsystem 340 may be communicatively coupled to an electronic lock 354 (which defines a computing device) on a door 352 of a building 350 (or other secured space) through the first NIC 102 or the second NIC 104 if the microcontroller system 200 is used, or through any other suitable interface of any other VPN system or device. The entry subsystem 340 may be located within a certain distance of the electronic lock 354 such that the entry subsystem 340 can communicate with the lock 354. In that regard, the entry subsystem 340 can communicate with the lock 354 through a wireless connection such as Bluetooth or through a wired connection such as a cable attached between the entry subsystem and the lock.

[0074] The electronic lock 354 is configured to be selectively locked and unlocked by the entry subsystem 340 (e.g., tripping relay 218 to lock or unlock the electronic lock 354, as described above with respect to Fig. 2). The electronic lock 354 can be any electronic lock suitable for communicative coupling to the entry subsystem 340.

[0075] In some implementations, the entry subsystem 340 includes a card reader such as a proximity card reader (not shown) which the resident 304 can use to unlock the electronic lock 354. For example, when the resident 304 places a proximity card on or near the proximity card reader of the entry subsystem 340, the proximity card reader can determine whether the proximity card is a valid key for unlocking the electronic lock 354. If the proximity card reader determines that the proximity card is valid, then the entry subsystem 340 sends instructions to the electronic lock 354 to unlock the door 352.

[0076] Certain components of the virtual entry system 300 can replace conventional building call box systems. For example, the entry subsystem 340 is configured to communicate over the network 150 with the virtual entry server 320 to allow the guest 302, who is within proximity of the entry subsystem 340, to communicate with the resident 304 of the building 350 (or other building personnel). If the resident 304 wants to allow the guest 302 to enter the building 350, the resident can use the electronic device 314 to communicate a request to unlock the electronic lock 354 using a signal sent to the electronic lock by the entry subsystem 340.

[0077] Other components that can be utilized as part of an entry system include a sensor 360, which may include a camera 360 which can be in communication with the network 150, the electronic device 314, and/or the entry subsystem 340. The sensor 360 can be any kind of sensor such as a heat sensor, a motion sensor, an audio sensor such as a microphone, a video camera, motion detection component, or a combination of different types of sensors. The sensor 360 can be used as described below to confirm a presence of the guest 302 at the location of the building 350.

[0078] A wireless network 358 can be provided as well. This can represent a WiFi access point connected to the entry subsystem 340 and/or the network 150. The access point can be used as described below to assist in confirming a presence of the guest 302 at the building 350. The wireless network can be any network protocol such as Bluetooth, cellular, 4G/5G and so forth.

[0079] In other aspects, an output device 362 may be included, which can be a speaker, display screen, or another component that produces some kind of output. An input device 364, such as a doorbell or some other physical button can also be used to confirm the user’s presence. The input device 364 can be connected to the entry subsystem 340 and/or the network 150 to provide a signal (such as a brief high voltage) indicating that the user pressed the button, for instance, when instructed to by the system.

[0080] In some aspects, the sensor 360 described above can also be an electronic sensor that can confirm a signal from a key fob 366, which is a small electronic device that can be used to confirm a user’s location, start a vehicle, or open a door. A delivery driver, for example, can have a key fob 366 used in connection with the sensor 360, and an aspect of enabling access to a secure area described below can include at least in part use of the key fob 366 or similar.

[0081] An object 356, such as a code (e.g., a QR code, a barcode, etc.), other visual object, or near-field communication object can also be provided for use in a process of confirming that the user is at the building 350 as well. The object 356 may sometimes be referred to throughout as a “QR code”, a “code”, a “fixed object”, a “greeting panel”, or the like. Various approaches to using these elements are outlined more fully below.

[0082] FIG. 4 is a swim lane diagram illustrating actions performed by components of the virtual entry system 300. At stage 402, the mobile device 312 of the guest 302 obtains and displays a navigation interface. Stage 402 may occur, for example, when the guest 302 is within a certain distance of the entry subsystem 340, such as when the guest 302 walks up to the door 352 of the building 350.

[0083] When the mobile device 312 is within a certain distance to the entry subsystem 340, the entry subsystem can detect the mobile device and send the device information, such as the navigation interface. In some implementations, the entry subsystem 340 can detect the mobile device 312 and send information to the mobile device using near-field communication (NFC), Bluetooth, or beacon technology. For example, the communications module 128 can enable communication using NFC, Bluetooth, or beacon technology. In other implementations, a device other than the entry subsystem 340 can detect the mobile device and/or send information, such as the information related to the navigation homepage, to the mobile device. In some implementations, the information related to the navigation interface is sent in response to detecting the mobile device using one or more of the above methods of detection. In some implementations, the entry subsystem 340 can store the information locally on a memory unit (e.g., the memory 126). In other implementations, the entry subsystem 340 can retrieve the information over a network prior to sending the information to the mobile device 312.

[0084] In some implementations, an application of the mobile device 312 can determine the device’s location. For example, the application can include or perform location based services. As another example, the application can be one that runs in the background of the mobile device 312 and collects geographic location information associated with the device (e.g., using GPS data). If the location of the mobile device 312 is within a certain distance of the entry subsystem 340, the building 350, the door 352, or the lock 354, then the application can display a notification on the mobile device. For example, the notification can include a welcome message that includes identifying information about the building 350. As another example, the notification can include a selectable option to view information related to the navigation interface. The information related to the navigation interface can be received by the mobile device 312 over a network (e.g., a mobile network of the mobile device).

[0085] In some implementations, the guest 302 may use the mobile device 312 to scan an object 356, such as a code (e.g., a barcode or QR code) that is printed on or near the electronic lock 354 or the door 352, wherein scanning the code causes the mobile device 312 to display a webpage that includes the information, such as the navigation interface. Detecting the mobile device 312 is advantageous because it allows the entry subsystem 340 to verify that the guest 302 is physically present within a certain proximity to the entry subsystem. Such a verification can prevent entities that are not within a certain proximity to the entry subsystem 340 (e.g., not near the building 350) from attempting to initiate a communication session or attempting to request that the door 352 be unlocked when they are not close enough to enter the building. In some implementations, the sensor 360 can be used to confirm a presence of the guest 302 at the location of the building 350.

[0086] The navigation interface can include information that identifies the building 350 and presents one or more selectable options using the mobile device 312. For example, one of the selectable options can prompt a user to enter an access code to enter the building. For example, the navigation homepage can display a message such as “Enter access code”. After the guest 302 selects the option to enter an access code, the navigation interface can display a prompt, allowing the user to enter an access code using the mobile device 312.

[0087] As another example, one of the selectable options can prompt a guest to enter or select a resident’s name to initiate a communication session with the resident. For example, the navigation homepage can display an editable textbox, with which the guest 302 can enter the name of a resident.

[0088] As another example, the navigation homepage can display a directory of one or more residents of the building 350, and the guest 302 can navigate through the directory to find the name of a particular resident. Once the guest 302 has found the name of the particular resident, the guest can select the name.

[0089] As another example, one of the selectable options can prompt a guest to enter or navigate to a resident’s unit number to initiate a communication session with the resident. For example, the navigation homepage can display an editable textbox, with which the guest 302 can enter the unit number of a resident.

[0090] As another example, the navigation homepage can display a directory of one or more unit numbers of the building 350, and the guest 302 can navigate through the directory to find the unit number of a particular resident. Once the guest 302 has found the unit number of the particular resident, the guest can select the unit number.

[0091] As another example, one of the selectable options can initiate a communication session with a particular entity, such as a front desk or leasing office for the building 350. For example, the navigation homepage can display a message such as “Call front desk” or “Call leasing office”. Selecting the option to initiate a communication session with the particular entity can result in the mobile device 312 initiating a communication session with the entity.

[0092] As another example, one of the selectable options can be to request the virtual entry server issue a one-time virtual credential to gain access to the building 350. For example, the virtual entry server can issue a one-time virtual credential, and the communication interface can prompt the guest 302 to sync the mobile device 312 with the entry subsystem 340 (e.g., to confirm that the guest is present at the building 350). Syncing the mobile device 312 with the entry subsystem 340 can include scanning, using the mobile device, a code (e.g., a barcode or QR code) that is printed on or near the electronic lock 354 or the door 352, etc. Notification of the code being scanned can be sent to the virtual entry server 320 (e.g., over a network). Once the mobile device 312 is synced, the virtual entry server 320 can generate a door unlock signal and send the door unlock signal to the electronic lock 354. In response to sending the door unlock signal, the virtual entry server 320 can prevent the one-time virtual credential from being used to gain access to the building 350, such that the guest 302 would have to request another one-time virtual credential to gain access to the building using this option.

[0093] At stage 404, the mobile device 312 receives one or more inputs from the guest 302. For example, a first input can correspond to selecting the option to enter a building code, and a second input may correspond to entering the building code. As another example, a first input can correspond to selecting or navigating to a resident’s name, and a second input can correspond to entering or selecting a resident’s name. As another example, a first input can correspond to selecting or navigating to a resident’s unit number, and a second input can correspond to entering or selecting a resident’s unit number. As yet another example, the input can correspond to selecting the option to initiate a communication session with a particular entity.

[0094] If the mobile device 312 receives an input corresponding to entering a building code, then the mobile device can send the building code to the virtual entry server 320 for validation. The virtual entry server 320 validates the code. If the validation is successful (e.g., if the virtual entry server 320 determines that the building code is a valid code that can be used to enter the building 350), then the virtual entry server can send instructions to unlock the door 352, as described in greater detail with respect to stage 414. If the validation is not successful (e.g., if the virtual entry server 320 determines that the building code is not a valid code that can be used to enter the building 350), then the virtual entry server does not send instructions to unlock the door 352. Instead, the virtual entry server may send a message to the mobile device 312 indicating that the validation was not successful.

[0095] At stage 406, the mobile device 312 sends a request to initiate a communication session. For example, if the input received in stage 404 corresponds to a selection of a resident’s name or unit number, or corresponds to the selection of the option to initiate a communication session with the particular entity, the mobile device can communicate this selection by sending a request to initiate a communication session to the virtual entry server 320. The request to initiate the communication session can include an indication of the one or more inputs received at stage 404, so that the virtual entry server receives information indicating with which entity the communication session should be initiated. For example, the request to initiate the communication session can include a particular identifier for the resident, unit, or other entity of the building 350. Upon receiving the particular identifier for the resident, unit, or other entity of the building 350, the virtual entry server 320 can use the identifier database 324 to determine information, related to the identifier, to use to initiate the communication session. [0096] At stage 408, the virtual entry server 320 initiates the communication session. For example, the virtual entry server 320 receives the request to initiate the communication session and determines, from the request, with which resident or entity to initiate the communication session. The communication session can be a telephone call or a video-chat or VoIP communication session that is hosted by the communication module 322 of the virtual entry server 320, to name a few examples.

[0097] After the virtual entry server 320 has determined the parties with which to initiate the communication session, the server sends information corresponding to a communication interface to the mobile device 312. For example, the information corresponding to a communication interface can include a meeting code that the mobile device 312 can use to connect to a corresponding communication session. More particularly, the communication module 322 can generate the meeting code that corresponds to a communication session hosted by the communication module 322, wherein the communication session is between the mobile device 312 and another electronic device (e.g., an electronic device of a particular resident or an electronic device or telephone of an entity such as a front desk or leasing office of the building 350).

[0098] When the mobile device 312 receives the information corresponding to the communication interface, the receipt of the information can cause the mobile device to launch a certain application of the mobile device. For example, the application can be a video-chat or VoIP application installed on the mobile device. As another example, the receipt of the information can cause the mobile device to launch a certain web application on the mobile device 312, such as a web communication application corresponding to a video-chat or VoIP application. In some implementations, the web application can be hosted by the virtual entry server 320 (e.g., the communication module 322 of the virtual entry server).

[0099] In some implementations, receipt of the information corresponding to the communication interface can cause the mobile device 312 to display the meeting code. The meeting code can be selectable, and selection of the meeting code can cause the mobile device 312 to open a communication application such as a local or web video-chat or V oIP application. The communication application can send the meeting code to the virtual entry server 320 over a network, e.g., the network 150. The virtual entry server 320 (e.g., the communication module 322 of the virtual entry server) can use the received meeting code to determine that the guest 302 has confirmed that the communication session is to be initiated.

[0100] The communication module 322 hosts the communication session, allowing the mobile device 312 to communicate using the communication application. In the example of FIG. 4, the communication module 322 hosts a communication session between the mobile device 312 of the guest 302 and the electronic device 314 of the resident 304. Accordingly, the communication module 322 can send a notification to the electronic device 314, the notification indicating that a request to communicate with the resident 304 was sent to the communication module 322. In some implementations, the notification can include identifying information of the guest 302, such as the guest’s name, which can be provided by the guest using the mobile device 312.

[0101] In some implementations, instead of participating in a video-chat or VoIP communication session, as described above, the guest 302 and the resident 304 can communicate through a telephone call. For example, the communication interface can prompt the guest 302 to open their default telephone calling application on the mobile device 312 and dial a phone number sent to the mobile device 312 by the virtual entry server 320 (e.g., sent by the communication module 322 of the virtual entry server 320).

[0102] In some implementations, the virtual entry system 300 (e.g., the communication module 322 of the virtual entry system) places a call to a phone (e.g., a POTS phone or a VoIP phone) in response to the guest 302 selecting a name or unit number of a resident they want to communicate with. For example, the virtual entry system 300 can use a phone number associated with the phone to place the call. The phone can be connected to a cloud server (e.g., a cloud communication service). For example, the phone can be connected to the cloud server through a VPN connection established by the entry subsystem 340 or through standard port forwarding that may forward data through a firewall. In some implementations, the phone receives a call from the cloud server and, in response to receiving the call from the cloud server, attempts to initiate a communication session with the resident 304 (e.g., with the electronic device 314 of the resident 304).

[0103] If the input received in stage 404 corresponds to a selection of a resident’s name or unit number, the mobile device can communicate this selection to the virtual entry server 320. As a security feature, if the virtual entry server 320 receives a call when there has not been a selection of a resident’s name or unit number to warrant a call to the virtual entry server, then the server can determine that the call is not a valid call. The virtual entry server 320 can decline calls that it determines are not valid calls.

[0104] The resident 304 can choose to accept or deny the request to communicate. If the resident 304 denies the request to communicate using the electronic device 314, then the electronic device 314 can send information indicative of this to the virtual entry server 320, which can communicate to the mobile device 312 that the resident 304 denied the request to communicate.

[0105] If instead the resident 304 accepts the request to communicate using the electronic device 314, then the virtual entry server 320 (e.g., the communication module 322 of the virtual entry server 320) initiates a communication session between the mobile device 312 and the electronic device 314, and the resident 304 is able to communicate with the guest 302. For example, accepting the request to communicate using the electronic device 314 can cause the electronic device to open a communication application such as a local or web video-chat or VoIP application. The resident 304 can then use the communication application to communicate with the guest 302 over the network 150. The communication application used by the guest 302 and the resident 304 can display a communication interface using the mobile device 312 and electronic device 314, respectively.

[0106] In some implementations, when the communication session is a video chat, the video chat can be one or two-directional. An example of a two-directional video chat is one in which both parties can at least see each other using the video chat application. An example of a onedirectional video chat is one in which only one party (e.g., the resident 304) can see the other party (e.g., the guest 302), while both parties can hear each other.

[0107] Hosting, by the communication module 322, a communication session between the guest 302 and the resident 304 provides an opportunity for the resident 304 to communicate with the guest 302 prior to allowing the guest 302 to enter the building 350. For example, if the guest 302 is a delivery person who is at the building 350 to deliver a package for the resident 304, the guest can convey this information to the resident, who can then decide whether or not to allow the guest to enter the building 350.

[0108] In the example of FIG. 4, the resident 304 decides to allow the guest 302 to enter the building 350. The resident 304 can indicate this decision using the electronic device 314, e.g., using the communication interface of the electronic device. For example, the communication interface of the electronic device 314 can include a “door unlock” button.

[0109] At stage 410, the electronic device 314 sends a request to unlock the door 352. For example, the electronic device 314 can send the request to unlock the door 352 to the virtual entry server 320 in response to receiving an input from the resident 304 indicating the same. In some implementations, the resident 304 indicates the decision to allow the guest 302 to enter the building 350 by entering a door access code to a communication interface of the electronic device 314. For example, the communication interface can register the input of the door access code and communicate the access code to the virtual entry server 320. [0110] At stage 412, the virtual entry server 320 receives the request to unlock the door 352 and at stage 414, the virtual entry server 320 sends, to the entry subsystem 340, an instruction to unlock the door 352.

[oni] At stage 416, the virtual entry server 320 generates a door unlock signal in response to receiving the instruction to unlock the door 352 and sends the door unlock signal to the electronic lock 354. In response to receiving the door unlock signal, the electronic lock 354 unlocks the door 352 (e.g., by tripping relay 218). Whereas the door 352 was locked prior to the electronic lock 354 receiving the door unlock signal, when the door 352 is unlocked, the guest 302 is able to open the door and enter the building 350.

[0112] With respect to a third party device, the system can include one or more of a network, a virtual entry server in communication with the network and an entry subsystem in communication with the network. The entry subsystem can be communicatively coupled to an electronic lock configured to selectively lock a lockable structure. The entry subsystem can include a VPN device which can be a 3^rd party device. The system can include a first computing device in communication with the network that can be configured to receive information related to a navigation interface from the virtual entry server. The first computing device can be configured to receive the information related to a navigation interface using near-field communication (NFC), Bluetooth, or beacon technology. In another aspect, the first computing device can be configured to receive the information related to a navigation interface over a network. The first computing device can receive the information related to the navigation interface in response to an application of the first computing device determining that the first computing device is within a threshold distance of the entry subsystem. The application of the first computing device can include a location-based service that determines a geographic location of the first computing device.

[0113] In another aspect, the system can include a second computing device in communication with the network that is configured to send a request to unlock the lockable structure to the virtual entry server over the network. The virtual entry server can be configured to send, to the entry subsystem over the network, instructions to unlock the lockable structure, in response to receiving the request to unlock the lockable structure.

[0114] FIG. 5 is a flow diagram illustrating an example of a process 500 for operating a virtual entry system for a building. The process 500 is described as being performed by a virtual entry server. For example, the virtual entry server 320, can perform the process 500.

[0115] At operation 502, the virtual entry server receives, from a mobile device, a selection associated with information related to a navigation interface. For example, the navigation interface can display, on the mobile device, selectable options such as an option to enter a building access code, an option to enter or navigate to a resident’s name to initiate a communication session with the resident, an option to enter or navigate to a resident’s unit number to initiate a communication session with the resident, or an option to initiate a communication session with a particular entity such as a front desk or leasing office of the building. The selection associated with the information related to the navigation interface can include a selection of one of the options and information input to the mobile device, such as a building code, or the name or unit number of a resident.

[0116] In some implementations, the virtual entry server can send the mobile device the information related to the navigation interface. For example, the virtual entry server can send the information related to the navigation interface to an entry subsystem communicatively coupled to an electronic lock of a door of the building, and the entry subsystem can send the information related to the navigation interface to the mobile device. In other implementations, the mobile device can retrieve the information related to the navigation interface from a website hosted by the virtual entry server.

[0117] In some implementations, the navigation interface can include a selectable option to initiate an automated attendant system that dictates at least a portion of the information related to the navigation interface. For example, a guest can select the option to initiate the automated attendant system, which the guest can use to hear a directory of names of residents of a building or unit numbers corresponding to the residents. The navigation interface can provide an option for a guest to select a name or unit number by providing an input to the mobile device (e.g., by pressing a button or number on a keypad corresponding to the guest’s selection). Therefore, a guest that is visually impaired can use the navigation interface to select a resident with which to communicate. In some implementations, the navigation interface can include an option to initiate a communication session between the mobile device 312 and an attendant that can assist the guest with the selection of a name or unit number.

[0118] In some implementations, the virtual entry server performs a location verification process for the guest. For example, the location verification process can include verifying, by the virtual entry server, the location of the guest (e.g., using GPS data received from a mobile device of the guest or other location data from an application of the mobile device). As another example the location verification process can including prompting, by the virtual entry server, the guest to enter their location. The location verification process can be performed prior to initiating a communication session between the mobile device and electronic device. For example, the location verification process can be performed to ensure that the guest is at the location at which they say they are. In some implementations, the information related to the navigation interface is sent to the mobile device in response to a successful verification that the guest is within a certain distance of the building.

[0119] In some implementations, part of the location verification process can include prompting the guest to enter (e.g., using the mobile device of the guest) a building code that is unique to a certain building. For example, a property manager can place the building code so that it is visible to a guest (e.g., by placing the building code by an entrance of the building). The virtual entry server may send the mobile device information related to the navigation interface in response to receiving an indication that the guest entered the building code corresponding to the building. The guest may be given a predetermined number of tries to enter the building code, and if the correct code is not entered in the predetermined number of tries, the virtual entry server may block the mobile device from being sent the information related to the navigation interface or from initiating a communication session. For example, the virtual entry server can block the UMEI, MAC, or IP address of the mobile device. In some implementations, the sensor 360 can be used to confirm a presence of the guest 302 at the location of the building 350.

[0120] At operation 504, the virtual entry server sends, to the mobile device in response to receiving the selection, information related to a communication interface, the information related to the communication interface including a meeting code. For example, if the selection received at operation 502 includes the name or unit number of a resident, then the virtual entry server can send the mobile device information related to a communication interface. For example, when received by the mobile device, the information can cause a communication interface for a web application corresponding to a communication application to be displayed on the mobile device.

[0121] The communication interface displayed on the mobile device can also display a meeting code. The meeting code can be a code specific to a communication session to be initiated between the mobile device and another device, such as an electronic device of a resident, front desk, or leasing office. That is, the virtual entry server can use the meeting code to determine the parties that may participate in the communication session.

[0122] In some implementations, the virtual entry server generates the meeting code to initiate a communication session that it hosts. For example, the virtual entry server can include a communication module configured to host a communication session. In other implementations, the virtual entry server does not host the communication session and instead the virtual entry server is communicatively coupled to a third-party communication server (e.g., a communication server maintained by a third-party video-chat or VoIP communication service). The third-party communication server can generate the meeting code and send the meeting code to the virtual entry server. An advantage of hosting the communication session using a communication module or third-party communication server is that the guest 302 need not reveal a phone number associated with the mobile device 312, which provides confidentiality to the guest 302.

[0123] At operation 506, the virtual entry server receives, from the mobile device, a first request to initiate a communication session between the mobile device and an electronic device, the first request including the meeting code. For example, the virtual entry server can use the meeting code to determine that a communication session is to be hosted between the mobile device and the electronic device. After identifying the parties of the communication session, the virtual entry server can initiate a communication session between the mobile device and the electronic device (e.g., host the communication session using a communication module of the virtual entry server).

[0124] In some implementations in which the communication session is hosted by a third- party communication server, the virtual entry server can receive the first request to initiate the communication session, including the meeting code, and send the first request and/or meeting code to the third-party communication server, which can use the first request and/or meeting code to initiate the communication session (e.g., host the communication session between the mobile device and the electronic device).

[0125] At operation 508, the virtual entry server initiates, based on the first request, a communication session between the mobile device and the electronic device. For example, the communication module of the virtual entry server can host the communication session between the mobile device and the electronic device, allowing a guest using the mobile device and a resident using the electronic device to communicate. If instead a third-party communication server hosts the communication session, the virtual entry server can send a request to the third- party communication server to initiate the communication session between the mobile device and the electronic device.

[0126] In some implementations, the virtual entry server initiates the communication session in response to receiving the first request including the meeting code. For example, the virtual entry server can use the meeting code to determine which parties to participate in the communication session. In some implementations, the virtual entry server sends the meeting code to the third-party communication server, which can use the meeting code to initiate the communication session. [0127] At operation 510, the virtual entry server receives a second request to unlock a door in response to the communication session. For example, during or after the communication session, the resident can send, using the electronic device, the second request to unlock the door of the building, and the virtual entry server can receive the second request from the electronic device.

[0128] In some implementations, instead of receiving the second request from the electronic device, the virtual entry server can receive the second request from an additional electronic device. For example, the additional electronic device can be an electronic security device that the resident has in their home (e.g., a smart home device). As another example, the additional electronic device can be a virtual assistant device, such as Amazon Alexa or Google Home device.

[0129] The virtual entry server can receive the second request, and in response to receiving the second request, the virtual entry server can send instructions to unlock the door of the building to a computing system. For example, the computing system can be an entry subsystem communicatively coupled to an electronic lock attached to the door. The entry subsystem can perform operations to unlock the door by communicating with the electronic lock, as described in greater detail below with respect to FIG. 6.

[0130] FIG. 6A is a flow diagram illustrating an example of a process 600 for receiving a request to unlock a door. The process 600 is described as being performed by an entry subsystem of a virtual entry system. For example, the entry subsystem 340 of the virtual entry system can perform the process 600.

[0131] At operation 602, the entry subsystem obtains information related to a navigation interface. For example, the entry subsystem can obtain the information related to the navigation interface from a virtual entry server or from a website hosted by the virtual entry server. The information related to the navigation interface can include a URL of the navigation interface. The information related to the navigation interface can include information corresponding to a building at which the entry subsystem is located. The information related to the navigation interface is described in greater detail above with respect to FIGs. 4-5.

[0132] At operation 604, the entry subsystem sends the information related to the navigation interface to a mobile device. For example, the entry subsystem can send the information related to the navigation interface to a mobile device of a guest who is outside the building at which the entry subsystem is located (e.g., using NFC).

[0133] At operation 606, the entry subsystem receives a request to unlock a door, the request being sent based on a communication session between an electronic device and the mobile device, the communication session being implemented in response to sending the information related to the navigation interface. For example, the communication session can be between the mobile device of the guest and an electronic device of a resident of the building. The communication session allows the resident an opportunity to communicate with the guest, prior to deciding whether to let the guest into the building by requesting to unlock a door of the building. If the resident decides to let the guest into the building, the resident can input their request to the electronic device. In some implementations, the electronic device can send the request to unlock the door to the virtual entry server, which can send the request to the entry subsystem. In other implementations, the electronic device can send the request to unlock the door to the entry subsystem.

[0134] FIG. 6B illustrates a method 610 covering operations from the standpoint of the system. At operation 612, the system performs the step of receiving, from a mobile device, a selection associated with information related to a navigation interface. At operation 614, the system performs the step of initiating, based on the selection, a communication session between an electronic device and a smart building communication device and at operation 616, the system performs the step of receiving an unlock request to unlock a door of the building in response to the communication session. The operations can further include sending to a computing system, instructions to unlock a door of the building in response to receiving the unlock request. The unlock request can be received from the electronic device. The steps can further include sending to the mobile device information related to the navigation interface. In one aspect, the information related to the navigation interface can include one or more names of residents of the building. The information related to the navigation interface can include one or more unit numbers associated with residents of the building.

[0135] In another aspect, the information related to the navigation interface can include a selectable option to call a particular entity, such as a resident or manager, of the building. The mobile device can receive the information related to the navigation interface through near-field communication, Bluetooth, or beacon technology. In one aspect, the mobile device can receive the information related to the navigation interface in response to scanning a barcode or QR code. The information related to the navigation interface can further include a selectable option to initiate an automated attendant system that dictates at least a portion of the information related to the navigation interface.

[0136] The smart building communication device is at least one of an IP camera having voice down and a smart doorbell. The communication session between the electronic device and the smart building communication device can be a one-way video communication session or a two- way audio communication session. The information related to the navigation interface can be obtained from a virtual entry server. The unlock request can be received from a virtual entry server, which receives the unlock request from the electronic device. The unlock request can be received from a smart home device.

[0137] FIG. 6C illustrates yet another process or method 630 associated with unlocking a door. The method in this example can include a first step 632 of transmitting, from an entry subsystem, a navigation interface to a mobile device and a second step 634 of receiving user input on the navigation interface from a user of the mobile device. The method can further include a step 636 of establishing, based on the user input, a communication session between an electronic device and the mobile device and a step 638 of receiving, based on the communication session, a request to unlock a lockable structure.

[0138] FIG. 7 depicts a block diagram of an alternative example of a virtual entry system 300’. The virtual entry system 300’ is substantially identical to the virtual entry system 300 described above except for the differences hereinafter noted. In that regard, identical reference numerals will be used to describe the components of the virtual entry system 300’ except with a prime (‘) at the end.

[0139] The virtual entry system 300’ differs from the virtual entry system 300 described above in that it further includes at least one smart building communication device 360’ located near a secure building entry (e.g., a locked door) that can facilitate an audio and/or video communication session with the electronic device 314’ of the particular resident. The communication module 322’ of the virtual entry server 320’ facilitates a communication session between the smart building communication device 360’ and the electronic device 314, as described in greater detail with respect to FIG. 8.

[0140] The smart building communication device 360’ provides audio and/or video input to the electronic device 314’ of the particular resident and audio and/or video output to the guest 302’ requesting access to the secure building entry. In that regard, the at least one smart building communication device 360’ may include a video input device, such as an internet protocol (IP) camera(s), a smart doorbell (such as the Ring™ doorbell), or another device capable of capturing the video input of the guest 302’ for sending to the electronic device 314’ of the particular resident. If the resident is not using a video-enabled device (such as a landline), the electronic device 314’ of the particular resident will not receive video input.

[0141] An audio input device, such as microphone, may also be included as part of the smart building communication device 360’ or as a separate component. The audio input device is configured to capture the audio input of the guest 302’ for sending to the electronic device 314’ of the particular resident. In this manner, the resident can receive audio and video input from the guest 302’ after the guest has requested access to the building, such as in one or more of the manners described above (e.g., by scanning a building QR code with the mobile device 312’, by detecting the mobile device 312’ and sending information to the mobile device using NFC, Bluetooth, or beacon technology, etc.).

[0142] Audio voice down capability may be included in the smart building communication device 360’ or as a separate component to provide audio output to the guest 302’. More specifically, the smart building communication device 360’ may include a speaker to provide audio output, which may have an IP amplifier to provide IP audio over a standard Ethernet network connection. The speaker can provide audio output to the guest 302’ captured by an audio input device at or near the electronic device 314’ of the particular resident. In this manner, the guest 302’ can receive audio input from the resident after the guest has requested access to the building. The audio input may instead be captured by an audio input device of a security system, a concierge, a leasing office or a front desk of the office, etc.

[0143] Any suitable voice down capability may be used. For instance, the IP camera(s) may be configured with an adapter that is configured to enable or provide one or more of a microphone capability, a speaker capability, and/or a lighting capability (to assist in video input) to the IP camera, such as the adapter shown and described in U.S. Provisional Patent Application No. 63/136,084, entitled “Camera Adaptor” (Attorney Docket No. 110663- 678465), the entire disclosure of which is hereby expressly incorporated by reference herein. The smart doorbell may be configured with a similar adaptor that is configured to enable or provide one or more of a microphone capability, a speaker capability, and/or a lighting capability. Moreover, it should be appreciated that audio voice down capability may be integrated into the smart building communication device 360’.

[0144] As can be appreciated, the smart building communication device 360’ is configured to provide audio and video input from the guest 302’ to the electronic device 314’, and provide at least audio input from the electronic device 314’ to the guest 302’. In other words, the smart building communication device 360’ is configured to provide at least one-way video between the guest 302’ and the electronic device 314’ and two-way audio between the guest 302’ and the electronic device 314’. In this manner, the resident (or other building personnel) can visually verify the identity of the guest 302’ and communicate verbally with the guest after the guest has requested access to the building if the electronic device 314’ of the resident supports video streaming. In one example, the electronic device 314’ of the resident supports video streaming through a native application platform for the smart building communication device 360’ (e.g., the Ring app for the Ring™ doorbell).

[0145] The smart building communication device 360’ is communicatively coupled to the virtual entry server 320’ through any suitable wired or wireless infrastructure using a video streaming protocol suitable to enable the electronic device 314’ to display content and provide audio in a web browser, app, etc. For instance, RTMP (Real-Time Messaging Protocol), RTSP (Real-Time Streaming Protocol), etc., may be used. The virtual entry server 320’ may also display video content captured by the smart building communication device 360’ on a surveillance monitor as a live stream (while optionally being recorded). In that regard, the smart building communication device 360’ may double as a surveillance camera.

[0146] FIG. 8 is a swim lane diagram illustrating actions performed by components of the virtual entry system 300’. In general, the actions performed by components of the virtual entry system 300’ incorporates the smart building communication device 360’ into the virtual entry system 300’. Certain actions performed by components of the virtual entry system 300’ that may be identical to actions performed by components of the virtual entry system 300 described above with respect to FIG. 4 are labeled with identical reference numerals except with a prime (‘) at the end. In that regard, the following description of actions performed by components of the virtual entry system 300’ will mostly focus on differences from the actions performed by components of the virtual entry system 300. In that regard, any of the actions performed by components of the virtual entry system 300 may be used in the virtual entry system 300’.

[0147] At stage 402’, the mobile device 312’ of the guest 302’ obtains and displays a navigation interface. Stage 402’ may occur, for example, when the guest 302’ is within a certain distance of the entry subsystem 340’, the building 350, the door 352, or the lock 354. If the location of the mobile device 312’ is within a certain distance of the entry subsystem 340’, the building 350, the door 352, or the lock 354, then the application can display a notification on the mobile device. For example, the notification can include a welcome message, a selectable option to view information related to the navigation interface, etc. The information related to the navigation interface can be received by the mobile device 312’ over a network (e.g., a mobile network of the mobile device).

[0148] In some implementations, the guest 302’ may use the mobile device 312’ to scan a code (e.g., a barcode or QR code) that is printed on or near the electronic lock 354’ or the door 352’, wherein scanning the code causes the mobile device 312’ to display a webpage that includes the information, such as the navigation interface. [0149] The navigation interface can include information that identifies the building 350’ and presents one or more selectable options using the mobile device 312’. For example, one of the selectable options can prompt a user to enter an access code to enter the building. As another example, one of the selectable options can prompt a guest to enter or select a resident’s name to initiate a communication session with the resident. As another example, the navigation homepage can display a directory of one or more residents of the building 350’, and the guest 302’ can navigate through the directory to find the name of a particular resident. As another example, one of the selectable options can prompt a guest to enter or navigate to a resident’s unit number to initiate a communication session with the resident. As another example, the navigation homepage can display a directory of one or more unit numbers of the building 350’, and the guest 302’ can navigate through the directory to find the unit number of a particular resident. As another example, one of the selectable options can initiate a communication session with a particular entity, such as a front desk or leasing office for the building 350’. As another example, one of the selectable options can be to request the virtual entry server issue a one-time virtual credential to gain access to the building 350’.

[0150] At stage 404’, the mobile device 312’ receives one or more inputs from the guest 302’. For example, a first input can correspond to selecting the option to enter a building code, and a second input may correspond to entering the building code. As another example, a first input can correspond to selecting or navigating to a resident’s name, and a second input can correspond to entering or selecting a resident’s name. As another example, a first input can correspond to selecting or navigating to a resident’s unit number, and a second input can correspond to entering or selecting a resident’s unit number. As yet another example, the input can correspond to selecting the option to initiate a communication session with a particular entity.

[0151] At stage 406’, the mobile device 312’ sends a request to initiate a communication session. For example, if the input received in stage 404’ corresponds to a selection of a resident’s name or unit number, or corresponds to the selection of the option to initiate a communication session with the particular entity, the mobile device can communicate this selection by sending a request to initiate a communication session to the virtual entry server 320’. The request to initiate the communication session can include an indication of the one or more inputs received at stage 404’, so that the virtual entry server receives information indicating with which entity the communication session should be initiated. For example, the request to initiate the communication session can include a particular identifier for the resident, unit, or other entity of the building 350’. Upon receiving the particular identifier for the resident, unit, or other entity of the building 350’, the virtual entry server 320’ can use the identifier database 324’ to determine information, related to the identifier, to use to initiate the communication session.

[0152] At stage 408’, the virtual entry server 320’ initiates the communication session. For example, the virtual entry server 320’ receives the request to initiate the communication session and determines, from the request, with which resident or entity to initiate the communication session. The virtual entry server 320’ may initiate the communication session after verifying the location of the guest (e.g., using GPS data received from a mobile device of the guest or other location data from an application of the mobile device) and/or after the resident 304 accepts the request to communicate. The communication session can be a one or two-way video and a two-way audio chat between the electronic device 314’ and the smart building communication device 360’ that is hosted by the communication module 322’ of the virtual entry server 320’.

[0153] More specifically, at stage 420’, the smart building communication device 360’ captures audio and video input from the guest 302’, and at stage 424’, the electronic device 314’ of the particular resident receives audio and video output corresponding to the audio and video input captured by the smart building communication device 360’. At stage 424’, the electronic device 314’ receives audio and video input from the resident, and at stage 420’, the smart building communication device 360’ receives audio and video output corresponding to the audio and video input captured by the electronic device 314’. The communication session between the electronic device 314’ and the smart building communication device 360’ may continue until the resident decides whether to allow the guest 302’ to enter the building 350’.

[0154] In the example of FIG. 8, the resident 304’ decides to allow the guest 302’ to enter the building 350’. The resident 304’ can indicate this decision using the electronic device 314, e.g., using the communication interface of the electronic device. For example, the communication interface of the electronic device 314’ can include a “door unlock” button.

[0155] At stage 410’, the electronic device 314’ sends a request to unlock the door 352’. For example, the electronic device 314’ can send the request to unlock the door 352’ to the virtual entry server 320’ in response to receiving an input from the resident 304’ indicating the same. In some implementations, the resident 304’ indicates the decision to allow the guest 302’ to enter the building 350’ by entering a door access code to a communication interface of the electronic device 314’. For example, the communication interface can register the input of the door access code and communicate the access code to the virtual entry server 320’. [0156] At stage 412’, the virtual entry server 320’ receives the request to unlock the door 352’ and at stage 414’, the virtual entry server 320’ sends, to the entry subsystem 340’, an instruction to unlock the door 352’.

[0157] At stage 416’, the virtual entry server 320’ generates a door unlock signal in response to receiving the instruction to unlock the door 352’ and sends the door unlock signal to the electronic lock 354’. In response to receiving the door unlock signal, the electronic lock 354’ unlocks the door 352’ (e.g., by tripping a relay, like relay 218). Whereas the door 352’ was locked prior to the electronic lock 354’ receiving the door unlock signal, when the door 352’ is unlocked, the guest 302’ is able to open the door and enter the building 350’.

[0158] FIG. 9 is a flow diagram illustrating an example of a process 500’ for operating a virtual entry system for a building. The process 500’ is described as being performed by a virtual entry server. For example, the virtual entry server 320’, can perform the process 500’. [0159] At operation 502’, the virtual entry server may receive, from a mobile device, one or more signals representing a scanned barcode or QR code, which is a code printed on or near the electronic lock 354 or the door 352. Scanning the code causes the mobile device 312 to display a webpage that includes the information, such as the navigation interface, at operation 504’.

[0160] In some implementations, the virtual entry server can send the information related to the navigation interface to an entry subsystem communicatively coupled to an electronic lock of a door of the building, and the entry subsystem can send the information related to the navigation interface to the mobile device. In other implementations, the mobile device can retrieve the information related to the navigation interface from a website hosted by the virtual entry server.

[0161] In some implementations, the navigation interface can include a selectable option to initiate an automated attendant system that dictates at least a portion of the information related to the navigation interface. For example, a guest can select the option to initiate the automated attendant system, which the guest can use to hear a directory of names of residents of a building or unit numbers corresponding to the residents. The navigation interface can provide an option for a guest to select a name or unit number by providing an input to the mobile device (e.g., by pressing a button or number on a keypad corresponding to the guest’s selection). Therefore, a guest that is visually impaired can use the navigation interface to select a resident with which to communicate. In some implementations, the navigation interface can include an option to initiate a communication session between the mobile device 312 and an attendant that can assist the guest with the selection of a name or unit number. [0162] In some implementations, the virtual entry server performs a location verification process for the guest. For example, the location verification process can include verifying, by the virtual entry server, the location of the guest (e.g., using GPS data received from a mobile device of the guest or other location data from an application of the mobile device). As another example the location verification process can including prompting, by the virtual entry server, the guest to enter their location. The location verification process can be performed prior to initiating a communication session between the smart building communication device 360’ and the electronic device 314’ (or an electronic device of other building personnel). For example, the location verification process can be performed to ensure that the guest is at the location at which they say they are. In some implementations, the information related to the navigation interface is sent to the mobile device in response to a successful verification that the guest is within a certain distance of the building.

[0163] In some implementations, part of the location verification process can include prompting the guest to enter (e.g., using the mobile device of the guest) a building code that is unique to a certain building. For example, a property manager can place the building code so that it is visible to a guest (e.g., by placing the building code by an entrance of the building). The virtual entry server may send the mobile device information related to the navigation interface in response to receiving an indication that the guest entered the building code corresponding to the building. The guest may be given a predetermined number of tries to enter the building code, and if the correct code is not entered in the predetermined number of tries, the virtual entry server may block the mobile device from being sent the information related to the navigation interface or from initiating a communication session. For example, the virtual entry server can block the UMEI, MAC, or IP address of the mobile device.

[0164] At operation 506’, the virtual entry server receives, from a mobile device, a selection associated with information related to a navigation interface. For example, the navigation interface can display, on the mobile device, selectable options such as an option to enter a building access code, an option to enter or navigate to a resident’s name to initiate a communication session with the resident, an option to enter or navigate to a resident’s unit number to initiate a communication session with the resident, or an option to initiate a communication session with a particular entity such as a front desk or leasing office of the building. The selection associated with the information related to the navigation interface can include a selection of one of the options and information input to the mobile device, such as a building code, or the name or unit number of a resident. [0165] At operation 508’, the virtual entry server initiates, based on the selection received, a session between the smart building communication device 360’ and the electronic device 314’ (or an electronic device of other building personnel). The communication module of the virtual entry server can host the communication session between the smart building communication device and the electronic device, allowing a guest using the smart building communication device and a resident using the electronic device to communicate. If instead a third-party communication server hosts the communication session, the virtual entry server can send a request to the third-party communication server to initiate the communication session between the smart building communication device and the electronic device.

[0166] At operation 510’, the virtual entry server receives a request to unlock a door in response to the communication session (an “unlock request”). For example, during or after the communication session, the resident can send, using the electronic device, the unlock request, and the virtual entry server can receive the unlock request from the electronic device.

[0167] In some implementations, instead of receiving the unlock request from the electronic device, the virtual entry server can receive the unlock request from an additional electronic device. For example, the additional electronic device can be an electronic security device that the resident has in their home (e.g., a smart home device). As another example, the additional electronic device can be a virtual assistant device, such as Amazon Alexa or Google Home device.

[0168] The virtual entry server can receive the unlock request, and in response to receiving the unlock request, the virtual entry server can send instructions to unlock the door of the building to a computing system. For example, the computing system can be an entry subsystem communicatively coupled to an electronic lock attached to the door. The entry subsystem can perform operations to unlock the door by communicating with the electronic lock, as described in greater detail below with respect to FIG. 6A or FIG. 6B.

[0169] FIG. 10 is a flow diagram illustrating an example of a process 600’ for receiving a request to unlock a door. The process 600’ is described as being performed by an entry subsystem of a virtual entry system. For example, the entry subsystem 340’ of the virtual entry system can perform the process 600’.

[0170] At operation 602’, the entry subsystem obtains information related to a navigation interface. For example, the entry subsystem can obtain the information related to the navigation interface from a virtual entry server or from a website hosted by the virtual entry server. The information related to the navigation interface can include a URL of the navigation interface. The information related to the navigation interface can include information corresponding to a building at which the entry subsystem is located. The information related to the navigation interface is described in greater detail above with respect to FIGs. 8-9.

[0171] At operation 604’, the entry subsystem sends the information related to the navigation interface to a mobile device. For example, the entry subsystem can send the information related to the navigation interface to a mobile device of a guest who is outside the building at which the entry subsystem is located (e.g., using NFC).

[0172] At operation 606’, the entry subsystem receives a request to unlock a door, the unlock request being sent based on a communication session between an electronic device and asmart building communication device, the communication session being implemented in response to sending the information related to the navigation interface. For example, the communication session can be between the smart building communication device and an electronic device of a resident of the building. The communication session allows the resident an opportunity to communicate with the guest, prior to deciding whether to let the guest into the building by requesting to unlock a door of the building. If the resident decides to let the guest into the building, the resident can input an unlock request to the electronic device. In some implementations, the electronic device can send the unlock request to the virtual entry server, which can send the unlock request to the entry subsystem. In other implementations, the electronic device can send the unlock request to the entry subsystem.

[0173] In some cases, at least a subset of the processes 500, 600, 500’, and 600’ illustrated by the flow diagrams of FIGs. 5-6 and 9-10 may be performed remotely by one or more network servers (e.g., of a cloud service). In some examples, the processes described herein (e.g., the message validation processes 500, 600, 500’, and 600’ and/or other processes described herein) may be performed by a computing device or apparatus.

[0174] At least a subset of the processes 500, 600, 500’, and 600’ illustrated by the flow diagrams of FIGs. 5-6 and 9-10 may be performed by a computing device with the architecture of the computing system 1700 shown in FIG. 17. The computing device can include any suitable device, such as a mobile device (e.g., a mobile phone), a desktop computing device, a tablet computing device, a wearable device (e.g., a VR headset, an AR headset, AR glasses, a network-connected watch or smartwatch, or other wearable device), a server computer, an autonomous vehicle or computing device of an autonomous vehicle, a robotic device, a television, and/or any other computing device with the resource capabilities to perform the processes described herein, including the processes 500, 600, 500’, and 600’.

[0175] In some cases, the computing device or apparatus may include various components, such as one or more input devices, one or more output devices, one or more processors, one or more microprocessors, one or more microcomputers, one or more cameras, one or more sensors, and/or other component(s) that are configured to carry out the steps of processes described herein. In some examples, the computing device may include a display, a network interface configured to communicate and/or receive the data, any combination thereof, and/or other component(s). The network interface may be configured to communicate and/or receive Internet Protocol (IP) based data or other type of data.

[0176] The components of the computing device can be implemented in circuitry. For example, the components can include and/or can be implemented using electronic circuits or other electronic hardware, which can include one or more programmable electronic circuits (e.g., microprocessors, graphics processing units (GPUs), digital signal processors (DSPs), central processing units (CPUs), and/or other suitable electronic circuits), and/or can include and/or be implemented using computer software, firmware, or any combination thereof, to perform the various operations described herein.

[0177] The processes illustrated by conceptual diagrams and flow diagrams of FIGs. 5-6 and 9-10 are organized as logical flow diagrams, the operation of which represents a sequence of operations that can be implemented in hardware, computer instructions, or a combination thereof. In the context of computer instructions, the operations represent computer-executable instructions stored on one or more computer-readable storage media that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures, and the like that perform particular functions or implement particular data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement the processes.

[0178] Additionally, the processes illustrated by conceptual diagrams and flow diagrams of FIGs. 5-6 and 9-10 and/or other processes described herein may be performed under the control of one or more computer systems configured with executable instructions and may be implemented as code (e.g., executable instructions, one or more computer programs, or one or more applications) executing collectively on one or more processors, by hardware, or combinations thereof. As noted above, the code may be stored on a computer-readable or machine-readable storage medium, for example, in the form of a computer program comprising a plurality of instructions executable by one or more processors. The computer-readable or machine-readable storage medium may be non-transitory. [0179] The disclosure next introduces a number of different entry technologies particularly designed to enable access to a secure space such as a building through a locked door and which has a requirement to confirm that the user desiring access is physically at the location of the secure space. Various authenti cation/ verification techniques are described next with reference to FIG. 3 and its various components. In one example, the system can verify the physical presence of the guest 302 at the property 350 or at a particular location by the user via their mobile device 312 scanning an object 356, such as a QR code/Barcode or other graphical object, by sensing a presence of the guest 302 at the location of the building 350 with the sensor 360, or by other methods described herein. A universal resource locator (website or server location) is stored within the object which can cause the mobile device 312 to launch a graphical program such as a browser, which can then be populated with the website address to take the user to the webpage. A user interface can be transmitted to the user device (from a server such as the entry subsystem 340 (or other component) which can present a user interface such as a directory that the user can interact with to select the person 304 at the building 350 and to request entry authorization. The person 304 may be a resident or manager or some other person (who may or may not be in the building but may have authorization to grant access to the secure space).

[0180] In another aspect, confirming that the person (through their mobile device) is at the location 350 can be achieved through use of a wireless network 358. If the wireless network 358 is WiFi, for example, in the 802. 11 protocol, even without actually accessing the Internet, the mobile device 312 will exchange information with the wireless network 358 access point. For example, a MAC (media access control) address, as a unique identifier of the network interface controller (NIC) for use as a network address to communicate with the network 150, can be revealed to the wireless network 358 just as part of a scan of the mobile device 312 for available networks in the area. This approach can be used for any networking technology such as Ethernet, WiFi, Bluetooth, and others. The wireless network 358 can represent any of these and can include a beacon, access point, or any other component to enable wireless communications. In one example, the system can “sniff’ data sent over an unencrypted WiFi network that is readily available in that the mobile device 312 shares that information when seeking to access the wireless network 358. That data, such as the MAC address, can be used to confirm that the user is at the location. Cell Tower or WiFi triangulation can also be used to confirm or generally determine a location of the mobile device 312 and thus the guest 302. [0181] In one example, the wireless network 358 can send an identifier called a basic service set identifier (BSSID) that is included in all packets. It identifies the network associated with the wireless network 358. It can include the MAC address of the access point of the wireless network 358 for the service set. A SSID is a service set identifier or network name for the network that can also be sent. The mobile device 312 will log this received data and the system can backtrack that data to identify the user’s MAC address using a backtrack tool.

[0182] In another aspect, after the user has scanned an object 356, such as a code or NFC object, the system may transmit a user interface to the mobile device 312 for performing some task. In addition, the user interface or an audio instruction via the output device 362 can be provided to cause the user to scan the object 356 or to scan a different object. The first scan can be to provide a user interface or computer code to be transmitted to the mobile device 312. This can be an application, a user interface or other code. In one aspect, the code can detect whether the user has again scanned the obj ect 356 and thus confirmed their location. In another aspect, the code on the mobile device 312 can detect the secondary scan of the object 356 and communicate with the entry subsystem 340 or some other server to confirm that the user is at the building 350. In another aspect, the system can confirm a redirect of the URL via the second can and/or can check that it was a mobile device that scanned the QR code or object 356 by validating the browser/OS system of the mobile device 312.

[0183] In another aspect, the user could scan or be asked or instructed to scan or enter an alphanumeric building ID or building code to verify that they are in front of the building. As users could memorize or record such an ID and use it at a different location, in one aspect, the system could provide a dynamically changing ID associated with the building, such that the user might have to type in, speak, scan, or otherwise provide the building ID that is only available via a display, placard or other means at the location.

[0184] Via the output device 362 or via the mobile device 312, the system could ask the guest 302 to enter a confirmation code printed on the object 356, or scan another code. In another aspect, the QR code or other code could be dynamic in that the output device 362 may include a display that could present different codes for scanning. The first code could be to access the system and receive a user interface for performing the necessary tasks to be confirmed for entry. Once the server receives the access request via the URL, and starts to engage with the user, then the system can alter or present a new code for scanning upon request to confirm that the user is at the location. For example, the guest 302 scans the QR code 356 and as a result they can be auto connected to Bluetooth/Wi-Fi/NFC to see the directory listing or some other user interface to achieve a task (open a door, access a storage location for delivered packages, pick up a package, and so forth) and contact another person 304 in any of the approached described herein.

[0185] FIG. 11A illustrates an example method 1100 for authenticating that the user is physically at the location. The method 1100 includes one or more of verifying, via use of a mobile device, a physical presence of a user at a location (1102), transmitting a user interface to the mobile device, the user interface being applicable to grant access to the user to a secure space at the location (1104), receiving an interaction with the user interface from the user (1106), based on the interaction, establishing a communication session between the mobile device and a device of an authorized person associated with the location (1108), receiving a request to unlock the secure space at the location (1110) and, based on the request, unlocking the secure space at the location (1112).

[0186] Verifying the physical presence at the location 350 can be accomplished via one or more of the mobile device 312 scanning a fixed object 356, a determination that the mobile device 312 is in fact mobile, the mobile device 312 scanning an object 362 (such as a dynamic display), the mobile device 312 scanning multiple objects, a user interaction with the mobile device 312 (such as via a display, via physical gestures, or other approaches) and a user interface provided via a wireless communication link to a system (such as the entry subsystem 340 and/or wireless network 150), a receipt of an interaction by the user with an input device 364, such as a physical button at the location 350, a global positioning system confirmation, an IP address lookup, a triangulation technique, an audio confirmation from the user, a speech analysis of speech from the user, a facial recognition analysis of the user, an analysis of data received from the mobile device to a wireless network, and/or receipt of a confirmation code from a user of the mobile device 312.

[0187] When the step of verifying the physical presence at the location is accomplished via the determination that the mobile device 312 is in fact mobile, the method further can include validating one of a browser, a software module, or an operating system on the mobile device 312. Establishing the communication session further can include initiating a call from the mobile device 312 to the device of the authorized person 304.

[0188] In another aspect, the guest 302 can tap the QR/greeting panel 356 and get the web address for the directory via NFC for validation of their physical presence.

[0189] There are other options as well for verifying that the user is at a location. In a first aspect, the guest 302 can scan the code 356 to receive a user interface, make a selection of a person 304 via a directory. When this occurs, a call or other communication starts and the guest 302 hears a message to press the door button or other physical object 364 to confirm they want to place the call. The input device 364, such as a door button or other physical object can be like a doorbell that would generate a sensor input that when pressed, goes high or low for a brief period of time. This sends a signal to the entry subsystem 340 that the guest 302 is in fact present and wants to process the call. At this point, the call or other communication session is connected like normal. The input device 364, such as a physical button or object can be like an loT (Internet of Things) device. As noted above, a sensor 360 can also be included, which may be implemented at least in part as a microphone which can receive speech, and a speech recognition and spoken language understanding models can be utilized to confirm that the user has said what the message instructions them to say.

[0190] FIG. 1 IB illustrates an example method 1130 related to using both a first interaction and a second interaction with one or more objects. The example method 1130 includes one or more of transmitting a user interface to a mobile device based on a first interaction of the mobile device with a first object at a location (1132), receiving a confirmation that the mobile device is at the location based on a second interaction of the mobile device with a second object at the location (1134) and, based on the confirmation, enabling access to a secure area at the location (1136). The first interaction of the mobile device with the first object can include a first scan of a first visual code and the second interaction can include a second scan of the mobile device with a second visual code. The visual codes might be the same or different. One might be fixed and the other dynamic. The first object can include a first near field communication object or a first QR code and the second object can include a second near field communication object or a second QR code.

[0191] FIG. 12 illustrates a method 1200 related to pressing an input device 364 or a physical object, e.g., a button at the location 350 for verifying that the guest 302 is physically at the location 350. The method 1200 can include one or more of receiving a request based on a scan of a code by a first device at a location (1202), providing, based on the request, the first device a user interface (1204), receiving, via an interaction by a user with the user interface, a selection of a person from the user interface (1206), presenting a message on the first device for the user to press a physical object (1208), confirming a presence of the user at the location based on a signal caused by the user pressing the physical object to yield a confirmation (1210), and, based on the confirmation, establishing a communication session between the first device and a second device (1212).

[0192] The method can further include receiving a request from the second device to grant access to a secure space at the location and, based on the request, unlocking a locked component to grant access to the secure space the location to the user. The locked component can be a door 352 and the secure space can be a room in a building 350. The signal caused by the user pressing the physical object can be a high signal that is set high for a period of time indicating that the user has pressed the physical object.

[0193] In another aspect, the physical object or input device 364 can be a smart door bell (e.g., a Ring™ doorbell described above) or any third party device for audio and/or the sensor 360, such as a camera 360 on the building 350. When the guest 302 selects a resident or another authorized person 304 to call (hereainfter sometimes simply “resident 304” or “person 304”), the input device 364 goes off hook to connect the call to the resident 304 and ask the guest 302 to press the input device 364 (e.g., the doorbell button) to confirm the calling. This verifies that the guest is actually at the door 352 and allows the call to connect video/audio through the input device 364 using only the guest mobile device 312 for enabling the user to receive the directory listing.

[0194] FIG. 13 illustrates a method 1300 in this regard. An example method 1300 includes one or more of presenting a directory listing user interface on a mobile device at a location (1302), receiving a request from a user of the mobile device of a chosen person from the directory listing (1304), based on the request, instructing via a fixed device configured at the location, the user to press an input device or physical object to yield a user interaction (1306), based on the user interaction, establishing a communication session between the fixed device configured at the location and a device associated with the chosen person (1308) and authorizing, via the device associated with the chosen person, access, for the user of the mobile device, to a secure space at the location (1310). The user can be confirmed to be at the location 350 based on the user interaction with the physical object at the location. The input device 364 can be a physical object that can include a button. The fixed device can include the object 356, such as a code (e.g., a QR code, a barcode, etc.), or a device having at least one of an audio capability and a video capability, such as the smart building communication device 360’ (e.g., an IP camera with audio voice down capability), or another suitable device.

[0195] FIG. 14A illustrates another example method 1400 related to the use of the wireless network 358 such as a WiFi network. The method includes one or more of determining that a mobile device is within a range of a wireless network (1402), transmitting, from a server, a splash page to the mobile device from the wireless network, the splash page having an object that a user can interact with (1404), receiving an interaction with the object from the user (1406), based on the interaction, establishing a communication session with a second device (1408) and receiving a confirmation from the second device to enable access to a secure space for the user (1410). Note that with the splash page, the user is never granted access to the Internet or other network except for the wireless network 358 (which can be WiFi, Bluetooth, etc.), which merely provides an interactable user interface for the purpose of gaining entry and not to access a network. After the communication session is established with the second device, the system may then transmit a secondary page to the mobile device which can be a main menu, a directory that the user can interact with, or the system can indicate or have an object to select to disconnect from the wireless network. In this regard, the step (1410) may not be performed until after the secondary page is provided such that the user may select from a directory on a secondary page the resident or other person associated with the building that they need to communicate with to obtain access to the secure space. The wireless network 358 in this example does not grant access to another network like the Internet but just uses the concept of the “splash page” or the initial page presented to the user when they connect to the wireless network 358 in order to perform the specific tasks associated with granting entry to the secure space.

[0196] FIG. 14B illustrates another method 1412 related to the “splash page”. This method 1420 can include one or more of identifying a mobile device at a location (1422), presenting a splash page from a wireless private network (1424), receiving an interaction from a user with the splash page (1426), based on the interaction, establishing a communication with a user device and the mobile device (1428), disconnecting the mobile device from the wireless private network without granting any access to the Internet via the wireless private network (1430) and receiving, from the user device, a confirmation to enable access to a secure area at the location for the user (1432).

[0197] FIG. 14C illustrates another method 1450 which relates to the use of splash pages. The method 1450 can include one or more of identifying a mobile device at a location (1452), transmitting a first splash page from a wireless private network to the mobile device (1454), receiving an interaction from a user with the first splash page (1456), based on the interaction, establishing a communication with a user device and the mobile device (1458), after establishing the communication with the user device and the mobile device, transmitting a second splash page from the wireless private network to the mobile device (1460) and granting access to a secure space at the location based on the communication, wherein the mobile device is never granted access to the Internet via the wireless private network (1462).

[0198] Note that the access control systems disclosed herein can be used to provide the ability to enable access to a secure space and integrate in some cases third-party access control systems. A secure command can be transmitted to a third party access control system to control a door or other access and to read or receive a door status such as locked, unlocked, closed, and any timing associated with these various settings. Signals can be provided through a cellular connection, the Internet, a modem, a POTS system, and signals such as DTMF tones can be used to provide commands to third party access control systems as well. Application programming interfaces (APIs) might be established as well to enable access to the secure space. Thus, the entry subsystem 340 or the virtual entry server 320 might be a third-party entity or operated by a third-party entity and not the same entity as operates an application or other components of the system.

[0199] FIG. 15 illustrates another example system 1500 and its associated method shown in FIG. 16. As shown in FIG. 15, a person 1502 such as a driver (hereinafter “driver 1502”) delivering a package 1508 can gain access through a door 352 or other opening to a secure space using an authentication system and method disclosed herein. For instance, in the depicted embodiment, the driver 1502 carries a FOB 1504 as well as a mobile device 1506 used for scanning the package 1508. In that regard, the driver can arrive at a location and scan the package 1508. The data from the scan can be transmitted through a network 150 to a server 1510. The data transmitted to the server 1510 can include package validation data (e.g., it’s the proper package at the proper location) along with GPS or other location-based data for the device 1506 or driver 1502. The server 1510 can validate the data and then send an activation signal to the FOB 1504. The activation signal can be transmitted via Bluetooth from the mobile device 1506 to the FOB 1504 or can communicate via the wireless network 358 (such as a WiFi network , cellular network or otherwise). Note that the FOB 1504 might also be built into the mobile device 1506 such that they both perform the same function of pressing the FOB 1504 and/or the mobile device 1506 next to a scanner or reader device (not shown) which transmits the data to the server 1510 which can then check a database to confirm that the updated information is there associated with the scan of the package 1508. The server 1510 can then send an unlock command to the lock 354 and unlock that door and any other door necessary to deliver the package (such as a user mailbox, or package room at the building). Then, a predetermined time or a dynamic time later, the driver FOB 1504 access is removed from the door control system 354/1510. For example, the time might be simply 15 minutes or it might be 5 minutes from the time the location data indicates that the driver has started to leave the building. The door access could also be cut off due to other triggering events like the door closing/locking, another driver arriving, or another package being scanned for the location, and so forth.

[0200] FIG. 16A illustrates a method 1600 associated with the use of the FOB 1504. The method includes one or more of receiving first data associated with a scan of a package, by a person, at a location, the first data including location-based data (1602), validating the first data and updating a database to yield an updated database (1604), activating a device associated with the person that enables, upon interaction with a sensor at the location, access to a secure space at the location (1606), receiving second data via a sensor interacting with the device, the sensor being located at the location, the second data (1608), confirming the second data by referencing the updated database to yield a confirmation (1610) and unlocking, based on the confirmation, a door to enable the person to access the secure space (1612). The device might be a FOB 1504 used to interact with a sensor device (such as sensor 360) to enable the unlocking of the door 352 or it might be the same mobile device 1506 used to scan the package 1508. The connection between a device 1504/1506 and the access control 352 might be via a wireless link like Bluetooth or a near-field communication protocol.

[0201] FIG. 16B illustrates another method 1620 related to the use of a FOB 1504 or similar device. The method 1620 can include receiving, at a server, first data associated with a scan of an object via a mobile device by a user, the first data comprising at least location-based data confirming that the mobile device is at a location (1622), based on the first data, activating an access component associated with gaining access to a secure area at the location (1624), receiving an interaction of the access component with an access controller (1626), based on the interaction, transmitting second data to the server (1628) and, based on the first data and the second data, transmitting an unlock signal to enable the user to gain access to the secure area at the location (1630). Transmitting the unlock signal further can include transmitting a first unlock signal to unlock a first door at the location and transmitting a second unlock signal to unlock a second door at the location. The method can further include maintaining an active state of the access component for a period of time after activating the access component. In another aspect, the method can include deactivating the access component after either a predetermined period of time, a dynamic period of time, or a period of time based on one or more parameters.

[0202] The first data further can include data identifying the object. The first data further can include data identifying the object and whether the object is to be delivered to the location. The step of transmitting the unlock signal can further be based on whether the first data identifies that the objects is to be delivered to the location.

[0203] FIG. 17 is a diagram illustrating an example of a system for implementing certain aspects of the present technology. In particular, FIG. 17 illustrates an example of computing system 1700, which can be for example any computing device making up internal computing system, a remote computing system, a camera, or any component thereof in which the components of the system are in communication with each other using connection 1705. Connection 1705 can be a physical connection using a bus, or a direct connection into processor 1710, such as in a chipset architecture. Connection 1705 can also be a virtual connection, networked connection, or logical connection.

[0204] In some examples, computing system 1700 is a distributed system in which the functions described in this disclosure can be distributed within a datacenter, multiple data centers, a peer network, etc. In some examples, one or more of the described system components represents many such components each performing some or all of the function for which the component is described. In some examples, the components can be physical or virtual devices.

[0205] Example system 1700 includes at least one processing unit (CPU or processor) 1710 and connection 1705 that couples various system components including system memory 1715, such as read-only memory (ROM) 1720 and random access memory (RAM) 1725 to processor 1710. Computing system 1700 can include a cache 1712 of high-speed memory connected directly with, in close proximity to, or integrated as part of processor 1710.

[0206] Processor 1710 can include any general purpose processor and a hardware service or software service, such as services 1732, 1734, and 1736 stored in storage device 1730, configured to control processor 1710 as well as a special-purpose processor where software instructions are incorporated into the actual processor design. Processor 1710 may essentially be a completely self-contained computing system, containing multiple cores or processors, a bus, memory controller, cache, etc. A multi-core processor may be symmetric or asymmetric.

[0207] To enable user interaction, computing system 1700 includes an input device 1745, which can represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech, etc. Computing system 1700 can also include output device 1735, which can be one or more of a number of output mechanisms. In some instances, multimodal systems can enable a user to provide multiple types of input/output to communicate with computing system 1700.

[0208] Computing system 1700 can include communications interface 1740, which can generally govern and manage the user input and system output. The communication interface may perform or facilitate receipt and/or transmission wired or wireless communications using wired and/or wireless transceivers, including those making use of an audio jack/plug, a microphone jack/plug, a universal serial bus (USB) port/plug, an Apple® Lightning® port/plug, an Ethernet port/plug, a fiber optic port/plug, a proprietary wired port/plug, a BLUETOOTH® wireless signal transfer, a BLUETOOTH® low energy (BLE) wireless signal transfer, an IBEACON® wireless signal transfer, a radio-frequency identification (RFID) wireless signal transfer, near-field communications (NFC) wireless signal transfer, dedicated short range communication (DSRC) wireless signal transfer, 802.11 Wi-Fi wireless signal transfer, wireless local area network (WLAN) signal transfer, Visible Light Communication (VLC), Worldwide Interoperability for Microwave Access (WiMAX), Infrared (IR) communication wireless signal transfer, Public Switched Telephone Network (PSTN) signal transfer, Integrated Services Digital Network (ISDN) signal transfer, 3G/4G/5G/LTE cellular data network wireless signal transfer, ad-hoc network signal transfer, radio wave signal transfer, microwave signal transfer, infrared signal transfer, visible light signal transfer, ultraviolet light signal transfer, wireless signal transfer along the electromagnetic spectrum, or some combination thereof.

[0209] The communications interface 1740 may also include one or more Global Navigation Satellite System (GNSS) receivers or transceivers that are used to determine a location of the computing system 1700 based on receipt of one or more signals from one or more satellites associated with one or more GNSS systems. GNSS systems include, but are not limited to, the US-based Global Positioning System (GPS), the Russia-based Global Navigation Satellite System (GLONASS), the China-based BeiDou Navigation Satellite System (BDS), and the Europe-based Galileo GNSS. There is no restriction on operating on any particular hardware arrangement, and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.

[0210] Storage device 1730 can be a non-volatile and/or non-transitory and/or computer- readable memory device and can be a hard disk or other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, a floppy disk, a flexible disk, a hard disk, magnetic tape, a magnetic strip/stripe, any other magnetic storage medium, flash memory, memristor memory, any other solid-state memory, a compact disc read only memory (CD-ROM) optical disc, a rewritable compact disc (CD) optical disc, digital video disk (DVD) optical disc, a blu-ray disc (BDD) optical disc, a holographic optical disk, another optical medium, a secure digital (SD) card, a micro secure digital (microSD) card, a Memory Stick® card, a smartcard chip, a EMV chip, a subscriber identity module (SIM) card, a mini/micro/nano/pico SIM card, another integrated circuit (IC) chip/card, random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash EPROM (FLASHEPROM), cache memory (L1/L2/L3/L4/L5/L#), resistive random-access memory (RRAM/ReRAM), phase change memory (PCM), spin transfer torque RAM (STT-RAM), another memory chip or cartridge, and/or a combination thereof.

[0211] The storage device 1730 can include software services, servers, services, etc., that when the code that defines such software is executed by the processor 1710, it causes the system to perform a function. In some examples, a hardware service that performs a particular function can include the software component stored in a computer-readable medium in connection with the necessary hardware components, such as processor 1710, connection 1705, output device 1735, etc., to carry out the function.

[0212] As used herein, the term “computer-readable medium” includes, but is not limited to, portable or non-portable storage devices, optical storage devices, and various other mediums capable of storing, containing, or carrying instruction(s) and/or data. A computer-readable medium may include a non-transitory medium in which data can be stored and that does not include carrier waves and/or transitory electronic signals propagating wirelessly or over wired connections. Examples of a non-transitory medium may include, but are not limited to, a magnetic disk or tape, optical storage media such as compact disk (CD) or digital versatile disk (DVD), flash memory, memory or memory devices. A computer-readable medium may have stored thereon code and/or machine-executable instructions that may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted using any suitable means including memory sharing, message passing, token passing, network transmission, or the like.

[0213] In some examples the computer-readable storage devices, mediums, and memories can include a cable or wireless signal containing a bit stream and the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.

[0214] Specific details are provided in the description above to provide a thorough understanding of the examples and examples provided herein. However, it will be understood by one of ordinary skill in the art that the examples may be practiced without these specific details. For clarity of explanation, in some instances the present technology may be presented as including individual functional blocks including functional blocks comprising devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software. Additional components may be used other than those shown in the figures and/or described herein. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the examples in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the examples.

[0215] Individual examples may be described above as a process or method which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed, but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

[0216] Processes and methods according to the above-described examples can be implemented using computer-executable instructions that are stored or otherwise available from computer-readable media. Such instructions can include, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or a processing device to perform a certain function or group of functions. Portions of computer resources used can be accessible over a network. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, source code, etc. Examples of computer-readable media that may be used to store instructions, information used, and/or information created during methods according to described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, networked storage devices, and so on.

[0217] Devices implementing processes and methods according to these disclosures can include hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof, and can take any of a variety of form factors. When implemented in software, firmware, middleware, or microcode, the program code or code segments to perform the necessary tasks (e.g., a computer-program product) may be stored in a computer-readable or machine-readable medium. A processor(s) may perform the necessary tasks. Typical examples of form factors include laptops, smart phones, mobile phones, tablet devices or other small form factor personal computers, personal digital assistants, rackmount devices, standalone devices, and so on. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example.

[0218] The instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are example means for providing the functions described in the disclosure.

[0219] In the foregoing description, aspects of the application are described with reference to specific examples thereof, but those skilled in the art will recognize that the application is not limited thereto. Thus, while illustrative examples of the application have been described in detail herein, it is to be understood that the inventive concepts may be otherwise variously embodied and employed, and that the appended claims are intended to be construed to include such variations, except as limited by the prior art. Various features and aspects of the abovedescribed application may be used individually or jointly. Further, examples can be utilized in any number of environments and applications beyond those described herein without departing from the broader spirit and scope of the specification. The specification and drawings are, accordingly, to be regarded as illustrative rather than restrictive. For the purposes of illustration, methods were described in a particular order. It should be appreciated that in alternate examples, the methods may be performed in a different order than that described.

[0220] Where components are described as being “configured to” perform certain operations, such configuration can be accomplished, for example, by designing electronic circuits or other hardware to perform the operation, by programming programmable electronic circuits (e.g., microprocessors, or other suitable electronic circuits) to perform the operation, or any combination thereof.

[0221] The phrase “coupled to” refers to any component that is physically connected to another component either directly or indirectly, and/or any component that is in communication with another component (e.g., connected to the other component over a wired or wireless connection, and/or other suitable communication interface) either directly or indirectly.

[0222] Claim language or other language reciting “at least one of’ a set and/or “one or more” of a set indicates that one member of the set or multiple members of the set (in any combination) satisfy the claim. For example, claim language reciting “at least one of A and B” means A, B, or A and B. In another example, claim language reciting “at least one of A, B, and C” means A, B, C, or A and B, or A and C, or B and C, or A and B and C. The language “at least one of’ a set and/or “one or more” of a set does not limit the set to the items listed in the set. For example, claim language reciting “at least one of A and B” can mean A, B, or A and B, and can additionally include items not listed in the set of A and B.

[0223] The various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the examples disclosed herein may be implemented as electronic hardware, computer software, firmware, or combinations thereof. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

[0224] The techniques described herein may also be implemented in electronic hardware, computer software, firmware, or any combination thereof. Such techniques may be implemented in any of a variety of devices such as general purposes computers, wireless communication device handsets, or integrated circuit devices having multiple uses including application in wireless communication device handsets and other devices. Any features described as modules or components may be implemented together in an integrated logic device or separately as discrete but interoperable logic devices. Any Statement or claimed element recited herein can be implemented by any of the hardware components disclosed in whole or in part. If implemented in software, the techniques may be realized at least in part by a computer-readable data storage medium comprising program code including instructions that, when executed, performs one or more of the methods described above. The computer- readable data storage medium may form part of a computer program product, which may include packaging materials. The computer-readable medium may comprise memory or data storage media, such as random access memory (RAM) such as synchronous dynamic random access memory (SDRAM), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), FLASH memory, magnetic or optical data storage media, and the like. The techniques additionally, or alternatively, may be realized at least in part by a computer-readable communication medium that carries or communicates program code in the form of instructions or data structures and that can be accessed, read, and/or executed by a computer, such as propagated signals or waves. [0225] The program code may be executed by a processor, which may include one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, an application specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Such a processor may be configured to perform any of the techniques described in this disclosure. A general purpose processor may be a microprocessor; but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). Accordingly, the term “processor,” as used herein may refer to any of the foregoing structure, any combination of the foregoing structure, or any other structure or apparatus suitable for implementation of the techniques described herein. In addition, in some aspects, the functionality described herein may be provided within dedicated software modules or hardware modules configured for encoding and decoding, or incorporated in a combined video encoder-decoder (CODEC).

BANK OF STATEMENTS

[0226] Statements 1 - 7 relate to FIGS. 11A-1 IB and an approach to verifying physical presence by scanning a code or providing two scans, one to start a process and second to confirm a person at a location.

[0227] Statements 8 - 11 relate to FIG. 12 and an idea of a user pressing a button to confirm location and establishing a call between devices.

[0228] Statements 12-15 relate to FIG. 13 and an idea of using a directory listing plus the user pressing an input device, such as by ringing the bell to confirm location.

[0229] Statement 16 relates to FIG. 14A and determining a range of a mobile device within a wireless network.

[0230] Statements 17-18 relate to FIG. 14B and the use of a splash page, but not access to the Internet, to connect a user to a resident to authorize entrance.

[0231] Statement 19 relates to FIG. 14C and the use of multiple splash pages and granting access to a building but not access to the Internet. [0232] Statements 20 - 21 relate to FIG. 16A and how to provide a driver delivering a package access to a secure area.

[0233] Statements 22-30 relate to FIG. 16B and how a driver can use a FOB for package delivery.

[0234] Statements 31-64 relate to the method of FIG. 6B and associated systems for performing the recited operations.

[0235] Statements 65-84 relate to the method FIG. 6C and associated systems for performing the related operations.

[0236] Statement 1. A method comprising: verifying, via use of a mobile device, a physical presence of a user at a location; transmitting a user interface to the mobile device, the user interface being applicable to grant access to the user to a secure space at the location; receiving an interaction with the user interface from the user; based on the interaction, establishing a communication session between the mobile device and a device of an authorized person associated with the location; receiving a request to unlock the secure space at the location; and based on the request, unlocking the secure space at the location.

[0237] Statement 2. The method of Statement 1, wherein verifying the physical presence at the location is accomplished via one or more of the mobile device scanning a fixed object, a determination that the mobile device is in fact mobile, the mobile device scanning a dynamic object, the mobile device scanning multiple objects, a user interaction with the mobile device and a user interface provided via a wireless communication link to a system, a receipt of an interaction by the user with an input device at the location, and/or receipt of a confirmation code from a user of the mobile device.

[0238] Statement 3. The method of any previous Statement, wherein when the step of verifying the physical presence at the location is accomplished via the determination that the mobile device is in fact mobile, the method further comprises validating one of a browser, a software module, or an operating system on the mobile device.

[0239] Statement 4. The method of any previous Statement, wherein establishing the communication session further comprises: initiating a call from the mobile device to the device of the authorized person.

[0240] Statement 5. A method comprising: transmitting a user interface to a mobile device based on a first interaction of the mobile device with a first object at a location; receiving a confirmation that the mobile device is at the location based on a second interaction of the mobile device with a second object at the location; based on the confirmation, enabling access to a secure area at the location.

[0241] Statement 6. The method of Statement 5, wherein the first interaction of the mobile device with the first object comprises a first scan of a first visual code and the second interaction comprises a second scan of the mobile device with a second visual code.

[0242] Statement 7. The method of any previous Statement, wherein the first object comprises a first near field communication object or a first QR code and wherein the second object comprises a second near field communication object or a second QR code.

[0243] Statement 8. A method comprising: receiving a request based on a scan of a code by a first device at a location; providing, based on the request, the first device a user interface; receiving, via an interaction by a user with the user interface, a selection of a person from the user interface; presenting a message on the first device for the user to provide input on an input device; confirming a presence of the user at the location based on a signal caused by the user providing input on the input device to yield a confirmation; and based on the confirmation, establishing a communication session between the first device and a second device.

[0244] Statement 9. The method of Statement 8, further comprising: receiving a request from the second device to grant access to a secure space at the location; and based on the request, unlocking a locked component to grant access to the secure space the location to the user.

[0245] Statement 10. The method of any previous Statement, wherein the locked component comprises a door and the secure space comprises a room in a building.

[0246] Statement 11. The method of any previous Statement, wherein the signal caused by the user providing input on the input device comprises a high signal that is set high for a period of time indicating that the user has pressed the physical object.

[0247] Statement 12. A method comprising: presenting a directory listing user interface on a mobile device at a location; receiving a request from a user of the mobile device of a chosen person from the directory listing; based on the request, instructing via a fixed device configured at the location, the user to provide input on an input device to yield a user interaction; based on the user interaction, establishing a communication session between the fixed device configured at the location and a device associated with the chosen person; and authorizing, via the device associated with the chosen person, access, for the user of the mobile device, to a secure space at the location.

[0248] Statement 13. The method of Statement 12, wherein the user is confirmed to be at the location based on the user interaction with the input device at the location.

[0249] Statement 14. The method of any previous Statement, wherein the input device comprises a button.

[0250] Statement 15. The method of any previous Statement, wherein the fixed device comprises at least one of an audio capability and a video capability.

[0251] Statement 16. A method comprising: determining that a mobile device is within a range of a wireless network; transmitting, from a server, a splash page to the mobile device from the wireless network, the splash page having an object that a user can interact with; receiving an interaction with the object from the user; based on the interaction, establishing a communication session with a second device; and receiving a confirmation from the second device to enable access to a secure space for the user.

[0252] Statement 17. A method comprising: identifying a mobile device at a location; presenting a splash page from a wireless private network; receiving an interaction from a user with the splash page; based on the interaction, establishing a communication with a user device and the mobile device; disconnecting the mobile device from the wireless private network without granting any access to the Internet via the wireless private network; and receiving, from the user device, a confirmation to enable access to a secure area at the location for the user.

[0253] Statement 18. The method of Statement 17, wherein the wireless private network comprises a WiFi network.

[0254] Statement 19. A method comprising: identifying a mobile device at a location; transmitting a first splash page from a wireless private network to the mobile device; receiving an interaction from a user with the first splash page; based on the interaction, establishing a communication with a user device and the mobile device; after establishing the communication with the user device and the mobile device, transmitting a second splash page from the wireless private network to the mobile device; and granting access to a secure space at the location based on the communication, wherein the mobile device is never granted access to the Internet via the wireless private network. [0255] Statement 20. A method comprising: receiving first data associated with a scan of a package, by a person, at a location, the first data including location-based data; validating the first data and updating a database to yield an updated database; activating a device associated with the person that enables, upon interaction with a sensor at the location, access to a secure space at the location; receiving second data via a sensor interacting with the device, the sensor being located at the location; confirming the second data by referencing the updated database to yield a confirmation; and unlocking, based on the confirmation, a door to enable the person to access the secure space.

[0256] Statement 21. The method of Statement 20, further comprising: receiving, at a server, first data associated with a scan of an obj ect via a mobile device by a user, the first data comprising at least location-based data confirming that the mobile device is at a location; based on the first data, activating an access component associated with gaining access to a secure area at the location; receiving an interaction of the access component with an access controller; based on the interaction, transmitting second data to the server; and based on the first data and the second data, transmitting an unlock signal to enable the user to gain access to the secure area at the location.

[0257] Statement 22. A method comprising: receiving, at a server, first data associated with a scan of an object via a mobile device by a user, the first data comprising at least location-based data confirming that the mobile device is at a location; based on the first data, activating an access component associated with gaining access to a secure area at the location; receiving an interaction of the access component with an access controller; based on the interaction, transmitting second data to the server; and based on the first data and the second data, transmitting an unlock signal to enable the user to gain access to the secure area at the location.

[0258] Statement 23. The method of Statement 22, wherein transmitting the unlock signal further comprises transmitting a first unlock signal to unlock a first door at the location and transmitting a second unlock signal to unlock a second door at the location.

[0259] Statement 24. The method of any previous Statement, further comprising: maintaining an active state of the access component for a period of time after activating the access component.

[0260] Statement 25. The method of any previous Statement, further comprising: deactivating the access component after either a predetermined period of time, a dynamic period of time, or a period of time based on one or more parameters.

[0261] Statement 26. The method of any previous Statement, wherein the first data further comprises data identifying the object.

[0262] Statement 27. The method of any previous Statement, wherein the first data further comprises data identifying the object and whether the object is to be delivered to the location.

[0263] Statement 28. The method of any previous Statement, wherein transmitting the unlock signal is further based on whether the first data identifies that the objects is to be delivered to the location.

[0264] Statement 30. A system having a processor and a computer-readable storage medium having instructions which, when executed by the processor, perform operations associated with any previous statement.

[0265] Statement 31. A method performed by a system of one or more computers for operating a virtual entry system for a building, the method comprising: receiving, from a mobile device, a selection associated with information related to a navigation interface; initiating, based on the selection, a communication session between an electronic device and a smart building communication device; and receiving an unlock request to unlock a door of the building in response to the communication session.

[0266] Statement 32. The method of Statement 31, further comprising sending to a computing system, instructions to unlock a door of the building in response to receiving the unlock request.

[0267] Statement 33. The method of any preceding Statement, wherein the unlock request is received from the electronic device.

[0268] Statement 34. The method of any preceding Statement, further comprising sending to the mobile device information related to the navigation interface. [0269] Statement 35. The method of any preceding Statement, wherein the information related to the navigation interface includes one or more names of residents of the building.

[0270] Statement 36. The method of any preceding Statement, wherein the information related to the navigation interface includes one or more unit numbers associated with residents of the building.

[0271] Statement 37. The method of any preceding Statement, wherein the information related to the navigation interface includes a selectable option to call a particular entity of the building.

[0272] Statement 38. The method of any preceding Statement, wherein the mobile device receives the information related to the navigation interface through near-field communication, Bluetooth, or beacon technology.

[0273] Statement 39. The method of any preceding Statement, wherein the mobile device receives the information related to the navigation interface in response to scanning a barcode or QR code.

[0274] Statement 40. The method of any preceding Statement, wherein the information related to the navigation interface includes a selectable option to initiate an automated attendant system that dictates at least a portion of the information related to the navigation interface.

[0275] Statement 41. The method of any preceding Statement, wherein the smart building communication device is at least one of an IP camera having voice down and a smart doorbell.

[0276] Statement 42. The method of any preceding Statement, wherein the communication session between the electronic device and the smart building communication device is a one-way video communication session and a two-way audio communication session.

[0277] Statement 43. The method of any preceding Statement, wherein the information related to the navigation interface is obtained from a virtual entry server.

[0278] Statement 44. The method of any preceding Statement, wherein the unlock request is received from a virtual entry server, which receives the unlock request from the electronic device.

[0279] Statement 45. The method of any preceding Statement, wherein the unlock request is received from a smart home device.

[0280] Statement 46. A virtual entry system comprising: a network; a virtual entry server in communication with the network; an entry subsystem in communication with the network, the entry subsystem communicatively coupled to an electronic lock configured to selectively lock a lockable structure; and smart building communication device in communication with the network, wherein the smart building communication device is configured to capture at least one of video and audio input.

[0281] Statement 47. The virtual entry system of Statement 46, wherein the entry subsystem includes a microcontroller device comprising: one or more processors; one or more non-transitory machine-readable storage media; a first network interface controller (NIC) configured to communicate with a first dynamic host configuration protocol (DHCP) server to receive a first DHCP address and configured to establish a virtual private network (VPN) connection for the electronic lock to communicate with a remote server, the first NIC configured to be communicatively coupled to the electronic lock; and a second NIC configured to receive a second DHCP address from a second DHCP server running on the microcontroller device and send the second DHCP address to the electronic lock.

[0282] Statement 48. The virtual entry system of Statement 47, wherein a first computing device in communication with the network is configured to receive information related to a navigation interface from the virtual entry server.

[0283] Statement 49. The virtual entry system of any preceding Statement, wherein the first computing device is configured to receive the information related to a navigation interface using near-field communication (NFC), Bluetooth, or beacon technology.

[0284] Statement 50. The virtual entry system of any preceding Statement, wherein the first computing device receives the information related to the navigation interface in response to an application of the first computing device determining that the first computing device is within a threshold distance of the entry subsystem.

[0285] Statement 51. The virtual entry system of any preceding Statement, wherein the first computing device receives the information related to the navigation interface in response to scanning a barcode or QR code. [0286] Statement 52. The virtual entry system of any preceding Statement, wherein the application of the first computing device includes a location based service that determines a geographic location of the first computing device.

[0287] Statement 53. The virtual entry system of any preceding Statement, wherein a second computing device in communication with the network is configured to send an unlock request to unlock the lockable structure to the virtual entry server over the network.

[0288] Statement 54. The virtual entry system of any preceding Statement, wherein the virtual entry server is configured to send, to the entry subsystem over the network, instructions to unlock the lockable structure, in response to receiving the unlock request.

[0289] Statement 55. The virtual entry system of any preceding Statement, wherein the smart building communication device is at least one of an IP camera having voice down and a smart doorbell.

[0290] Statement 56. The virtual entry system of any preceding Statement, wherein the virtual entry server is configured to facilitate a communication session between the second computing device and the smart building communication device as a one-way video communication session and a two-way audio communication session.

[0291] Statement 57. A virtual entry system comprising: a network; a virtual entry server in communication with the network; and an entry subsystem in communication with the network, the entry subsystem communicatively coupled to an electronic lock configured to selectively lock a lockable structure, the entry subsystem comprising: a microcontroller device comprising: one or more processors; one or more non-transitory machine-readable storage media; a first network interface controller (NIC) configured to communicate with a first dynamic host configuration protocol (DHCP) server to receive a first DHCP address and configured to establish a virtual private network (VPN) connection for the electronic lock to communicate with a remote server, the first NIC configured to be communicatively coupled to the electronic lock; and a second NIC configured to receive a second DHCP address from a second DHCP server running on the microcontroller device and send the second DHCP address to the electronic lock. [0292] Statement 58. The virtual entry system of Statement 57, wherein a first computing device in communication with the network is configured to receive information related to a navigation interface from the virtual entry server.

[0293] Statement 59. The virtual entry system of any preceding Statement, wherein the first computing device is configured to receive the information related to a navigation interface using near-field communication (NFC), Bluetooth, or beacon technology.

[0294] Statement 60. The virtual entry system of any preceding Statement, wherein the first computing device is configured to receive the information related to a navigation interface over a network.

[0295] Statement 61. The virtual entry system of any preceding Statement, wherein the first computing device receives the information related to the navigation interface in response to an application of the first computing device determining that the first computing device is within a threshold distance of the entry subsystem.

[0296] Statement 62. The virtual entry system of any preceding Statement, wherein the application of the first computing device includes a location based service that determines a geographic location of the first computing device.

[0297] Statement 63. The virtual entry system of any preceding Statement, wherein a second computing device in communication with the network is configured to send a request to unlock the lockable structure to the virtual entry server over the network.

[0298] Statement 64. The virtual entry system of any preceding Statement, wherein the virtual entry server is configured to send, to the entry subsystem over the network, instructions to unlock the lockable structure, in response to receiving the request to unlock the lockable structure.

[0299] Statement 65. A method comprising: transmitting, from an entry subsystem, a navigation interface to a mobile device; receiving user input on the navigation interface from a user of the mobile device; establishing, based on the user input, a communication session between an electronic device and the mobile device; and receiving, based on the communication session, a request to unlock a lockable structure.

[0300] Statement 66. The method of Statement 65, wherein the navigation interface is obtained from a virtual entry server.

[0301] Statement 67. The method of any preceding statement, wherein the lockable structure comprises a door. [0302] Statement 68. The method of any previous Statement, wherein the request to unlock the lockable structure is received from one of the electronic device and the mobile device. [0303] Statement 69. The method of any previous Statement, wherein the request to unlock the lockable structure is from a virtual entry server, which receives the request from the electronic device.

[0304] Statement 70. The method of any previous Statement, wherein the electronic device is owned by a second user inside a building comprising the lockable structure.

[0305] Statement 71. The method of any previous Statement, wherein the mobile device of the user is outside a building comprising the lockable structure.

[0306] Statement 72. A system comprising: an electronic lock configured to selectively lock a lockable structure; an entry subsystem communicatively coupled to the electronic lock, wherein the entry subsystem is configured to perform operations comprising: transmitting a navigation interface to a mobile device; receiving user input on the navigation interface from a user of the mobile device; establishing, based on the user input, a communication session between an electronic device and the mobile device; receiving, based on the communication session, a request to unlock the lockable structure; and unlocking the lockable structure via the electronic lock.

[0307] Statement 73. The system of Statement 72, wherein the system further comprises: a first network interface controller (NIC) configured to communicate with a first dynamic host configuration protocol (DHCP) server to receive a first DHCP address and configured to establish a virtual private network (VPN) connection for the electronic lock to communicate with a remote server, the first NIC configured to be communicatively coupled to the electronic lock; and a second NIC configured to receive a second DHCP address from a second DHCP server running on a microcontroller device and send the second DHCP address to the electronic lock.

[0308] Statement 74. The system of any previous Statement, wherein the mobile device receives the navigation interface in response to an application of the mobile device determining that the mobile device is within a threshold distance of the system. [0309] Statement 75. The system of any previous Statement, wherein the application of the mobile device comprises a location-based service that determines a geographic location of the mobile device.

[0310] Statement 76. The system of any previous Statement, wherein the electronic device is configured to send the request to unlock the lockable structure to the system.

[0311] Statement 77. The system of any previous Statement, wherein the system is configured to send instructions to unlock the lockable structure, in response to receiving the request to unlock the lockable structure.

[0312] Statement 78. The system of any previous Statement, wherein the navigation interface is obtained from a virtual entry server.

[0313] Statement 79. The system of any previous Statement, wherein the request to unlock the lockable structure is received from one of the electronic device and the mobile device.

[0314] Statement 80. The system of any previous Statement, wherein the request to unlock the lockable structure is from a virtual entry server, which receives the request from the electronic device.

[0315] Statement 81. The system of any previous Statement, wherein the electronic device is owned by a second user inside a building comprising the lockable structure.

[0316] Statement 82. The system of any previous Statement, wherein the mobile device of the user is outside a building comprising the lockable structure.

[0317] Statement 83. The system of any previous Statement, wherein the lockable structure is a door.

[0318] Statement 84. The system of any previous Statement, wherein the navigation interface comprises a selectable option to initiate an automated attendant system that dictates at least a portion of information related to the navigation interface.

Claims (24)

CLAIMS WHAT IS CLAIMED IS:

1. A method performed by a system of one or more computers for operating a virtual entry system for a building, the method comprising: receiving, from a mobile device, a selection associated with information related to a navigation interface; sending, to the mobile device in response to receiving the selection, information related to a communication interface, the information related to the communication interface including a meeting code; receiving, from the mobile device, a first request to initiate a communication session between the mobile device and an electronic device, the first request including the meeting code; initiating, based on the first request, a communication session between the mobile device and the electronic device; and receiving a second request to unlock a door of the building in response to the communication session.

2. The method of claim 1, further comprising sending to a computing system, instructions to unlock a door of the building in response to receiving the second request.

3. The method of claim 1, wherein the second request is received from the electronic device.

4. The method of claim 1, wherein the second request is received from an additional electronic device.

5. The method of claim 1, further comprising sending to the mobile device information related to the navigation interface.

6. The method of claim 1, wherein the information related to the navigation interface includes one or more names of residents of the building.

7. The method of claim 1, wherein the information related to the navigation interface includes one or more unit numbers associated with residents of the building.

8. The method of claim 1, wherein the information related to the navigation interface includes a selectable option to call a particular entity of the building.

9. The method of claim 8, wherein the particular entity of the building is a leasing office or a front desk of the office.

10. The method of claim 1, wherein the mobile device receives the information related to the navigation interface through near-field communication, Bluetooth, or beacon technology.

65

11. The method of claim 1, wherein the mobile device receives the information related to the navigation interface in response to scanning a barcode or QR code.

12. The method of claim 1, wherein the information related to the navigation interface includes a selectable option to initiate an automated attendant system that dictates at least a portion of the information related to the navigation interface.

13. The method of claim 12, wherein the portion of the information dictated by the automated attendant system includes one or more names of residents of the building.

14. The method of claim 12, wherein the portion of the information dictated by the automated attendant system includes one or more unit numbers associated with residents of the building.

15. The method of claim 1, further comprising: receiving, from the electronic device, a third request to generate a one-time credential for use in unlocking the door of the building; generating the one-time credential in response to receiving the third request; sending, to the mobile device, a request to sync the mobile device; receiving an indication that the mobile device has been synced; and sending the one-time credential to the mobile device in response to receiving the indication that the mobile device has been synced.

16. The method of claim 15, further comprising: receiving an indication that the door was unlocked using the one-time credential; and preventing the one-time credential from being used to unlock the door in response to receiving the indication that the door was unlocked.

17. A virtual entry system comprising: a network; a virtual entry server in communication with the network; and an entry subsystem in communication with the network, the entry subsystem communicatively coupled to an electronic lock configured to selectively lock a lockable structure, the entry subsystem comprising: a microcontroller device comprising: one or more processors; one or more non-transitory machine-readable storage media; a first network interface controller (NIC) configured to communicate with a first dynamic host configuration protocol (DHCP) server to receive a first DHCP address and configured to establish a virtual private network

66 (VPN) connection for the electronic lock to communicate with a remote server, the first NIC configured to be communicatively coupled to the electronic lock; and a second NIC configured to receive a second DHCP address from a second DHCP server running on the microcontroller device and send the second DHCP address to the electronic lock.

18. The virtual entry system of claim 17, wherein a first computing device in communication with the network is configured to receive information related to a navigation interface from the virtual entry server.

19. The virtual entry system of claim 18, wherein the first computing device is configured to receive the information related to a navigation interface using near-field communication (NFC), Bluetooth, or beacon technology.

20. The virtual entry system of claim 18, wherein the first computing device is configured to receive the information related to a navigation interface over a network.

21. The virtual entry system of claim 20, wherein the first computing device receives the information related to the navigation interface in response to an application of the first computing device determining that the first computing device is within a threshold distance of the entry subsystem.

22. The virtual entry system of claim 21, wherein the application of the first computing device includes a location based service that determines a geographic location of the first computing device.

23. The virtual entry system of claim 17, wherein a second computing device in communication with the network is configured to send a request to unlock the lockable structure to the virtual entry server over the network.

24. The virtual entry system of claim 23, wherein the virtual entry server is configured to send, to the entry subsystem over the network, instructions to unlock the lockable structure, in response to receiving the request to unlock the lockable structure.

67