US20200043271A1 - Electronic door system - Google Patents

Abstract

A door assembly includes a door, an electronic locking mechanism, and a camera system. The electronic locking mechanism is coupled to the door. The electronic locking mechanism has a first transceiver configured to facilitate wireless communication with a first external device via a first wireless communication protocol. The camera system is disposed within the door. The camera system has a second transceiver configured to facilitate wireless communication with a second external device via a second wireless communication protocol that is different than the first wireless communication protocol.

Description

CROSS-REFERENCE TO RELATED PATENT APPLICATION
• This application claims the benefit of U.S. Provisional Application No. 62/714,273, filed Aug. 3, 2018, which is incorporated herein by reference in its entirety.
BACKGROUND
• Electronic entry door features, such as electronic door locks (e.g., push button, biometric sensor, RFID reader), intercoms, cameras, motion sensors, and lighting, have been provided as modular, battery powered solutions for installation on or near an entry door, to provide additional security and convenience, and may, for example, provide for remote communication with a user (e.g., homeowner, business owner, resident, or employee), for example, through wireless communication (e.g., Wi-Fi or cellular) with the user's cell phone, tablet, or computer.
SUMMARY
• One embodiment relates to a door assembly. The door assembly includes a door, an electronic locking mechanism, and a camera system. The electronic locking mechanism is coupled to the door. The electronic locking mechanism has a first transceiver configured to facilitate wireless communication with a first external device via a first wireless communication protocol. The camera system is disposed within the door. The camera system has a second transceiver configured to facilitate wireless communication with a second external device via a second wireless communication protocol that is different than the first wireless communication protocol.
• Another embodiment relates to a modular door assembly. The modular door assembly includes a door slab, a first selectively-accessible connection box embedded in the door slab, and a second selectively-accessible connection box embedded in the door slab. The first selectively-accessible connection box includes a first interface configured to selectively interface with a first connector of an electronic locking mechanism. The second selectively-accessible connection box is configured to selectively receive and store a camera device within the door slab. The second selectively-accessible connection box includes a second interface configured to selectively interface with a second connector of the camera device.
• Still another embodiment relates to a door assembly. The door assembly includes a door slab, a first electrically-controllable component coupled to or embedded within the door slab, a second electrically-controllable component coupled to or embedded within the door slab, and a controller operatively connected to the first electrically-controllable component. The controller is configured to control operation of the first electrically-controllable component. Operation of the second electrically-controllable component is controllable independent of the controller.
BRIEF DESCRIPTION OF THE DRAWINGS
• FIG. 1 is a schematic view of an integrated electronic door system with power supplied to the door slab through electrical wiring in the core, according to an exemplary embodiment.
• FIG. 2 is a schematic view of an integrated electronic door system with power supplied to the door slab through electrical wiring in the core, according to another exemplary embodiment.
• FIG. 3 is a schematic view of an integrated electronic door system with power supplied to the door slab through electrical wiring in the core, according to another exemplary embodiment.
• FIG. 4 is a schematic block diagram of an electronic control system for an integrated electronic control system having independently operable electronic features, according to an exemplary embodiment.
• FIG. 5 is a schematic view of an integrated electronic door system with power supplied to the door slab through electrical wiring and a controller in the core, according to another exemplary embodiment.
• FIG. 6 is a schematic view of an integrated electronic door system with power supplied to the door slab through electrical wiring and a controller in the frame, according to another exemplary embodiment.
• FIG. 7 is a schematic block diagram of an electronic control system for an integrated electronic control system having independently operable electronic features, according to an exemplary embodiment.
• FIG. 8 is a front view of a composite door with a portion removed to expose the internal structure thereof, according to an exemplary embodiment.
• FIG. 9 is a side view of the door ofFIG. 8; and
• FIG. 10 is a cross-sectional view of the door ofFIG. 9 showing the internal structure of thereof.
• FIG. 11 is a schematic block diagram of an electronic door system, according to an exemplary embodiment.
• FIG. 12 is a schematic diagram of a door assembly of the electronic door system ofFIG. 11, according to an exemplary embodiment.
• FIG. 13 is a schematic diagram of a door assembly of the electronic door system ofFIG. 11, according to another exemplary embodiment.
• FIG. 14 is a block diagram of a wireless bridge of the door assembly ofFIGS. 12 and 13, according to an exemplary embodiment.
• FIG. 15 is a block diagram of a locking system of the door assembly ofFIGS. 12 and 13, according to an exemplary embodiment.
• FIG. 16 is a block diagram of a camera system of the door assembly ofFIGS. 12 and 13, according to an exemplary embodiment.
• FIG. 17 is a block diagram of a controller of the door assembly ofFIGS. 12 and 13, according to an exemplary embodiment.
• FIG. 18 is a block diagram of a door server of the electronic door system ofFIG. 11, according to an exemplary embodiment.
• FIG. 19 is a block diagram of a camera server of the electronic door system ofFIG. 11, according to an exemplary embodiment.
• FIG. 20 is a block diagram of a user device useable with the electronic door system ofFIG. 11, according to an exemplary embodiment.
• FIG. 21 is a schematic block diagram of a first communication process between components of the electronic door system ofFIG. 11, according to an exemplary embodiment.
• FIG. 22 is a schematic block diagram of a second communication process between components of the electronic door system ofFIG. 11, according to an exemplary embodiment.
• FIG. 23 is a schematic block diagram of a third communication process between components of the electronic door system ofFIG. 11, according to an exemplary embodiment.
• FIG. 24 is a schematic block diagram of a fourth communication process between components of the electronic door system ofFIG. 11, according to an exemplary embodiment.
• FIG. 25 is a schematic block diagram of a fifth communication process between components of the electronic door system ofFIG. 11, according to an exemplary embodiment.
DETAILED DESCRIPTION
• Before turning to the figures, which illustrate certain exemplary embodiments in detail, it should be understood that the present disclosure is not limited to the details or methodology set forth in the description or illustrated in the figures. It should also be understood that the terminology used herein is for the purpose of description only and should not be regarded as limiting.
• As utilized herein, the term “key” (e.g., device key, user key, bridge key, cryptographic key, etc.) means a numeric or alphanumeric code, which, for example, may be a parameter used in a block cipher algorithm that determines a forward cipher function. As utilized herein, the term “nonce” (e.g., handshake nonce, reply nonce, modified reply nonce, etc.) means a value that is used (e.g., only once) within a specified context. The terms “circuit” or “circuitry,” as utilized herein, connote hardware, software, or any combination thereof. In other words, a particular circuit described herein may be implemented using hardware components, instructions stored on one or more computer-readable storage media that are executable by processing circuitry (e.g., a microprocessor) to implement the associated functions described herein, or a combination of hardware and executable instructions. All such implementations are contemplated within the scope of the present disclosure.
• Electronic Door Arrangements
• As shown inFIGS. 8-10,fiberglass doors10 typically include a door-shaped solid (e.g., wooden)frame member14, a polymeric foam-type core12 positioned within theframe member14, a first orfront door skin24 secured to a first side of theframe member14, and a second orrear door skin26 secured to a second side, opposite the first side, of theframe member14. Thefront door skin24 and therear door skin26 may, for example, be formed as fiberglass reinforced compression molded panels prepared from a molding compound.
• According to an exemplary embodiment, a composite (e.g., having a fiberglass or foam filled frame) door assembly may be provided with one or more electronic features integrated into the door and in wired electrical communication with the building's electrical system to provide an integrated electronic (or “smart”) entry door solution, without the need for separate end user installation of one or more modular electronic components.
• While the electronic features and systems described herein may be integrated into many types of doors, the foam filled cavity of a composite fiberglass door facilitates incorporation of internal electronic features within the door, without requiring extensive machining or modification, as may be the case with a solid or monolithic door. Fiberglass doors typically include a door-shaped frame member (e.g., having wooden horizontal rails and vertical stiles), first and second fiberglass reinforced compression molded door skins secured to opposed first and second sides of the frame member, and a polymeric foam-type core (e.g., sprayed-in foam or cut block foam pieces) positioned between the door skins and within the frame member.
• The door may include, within its foamed-in enclosure, electrical wiring for one or more electronic features, with the electrical wiring extending through a hinged portion (e.g., a hinged edge, etc.) of the door and into the door jamb for connection with the electrical system of the building. Exemplary electrical connections between the door edge and the door jamb, include, for example, electric transfer hinges (e.g.,Series 1100 electric hinge, manufactured by ACSI) and flexible conduits (e.g., CDL series “concealed door loop,” manufactured by Command Access Technologies).
• In some embodiments, an electronic feature that is integral to the door, such as, for example, an electrically activated privacy window (as manufactured, for example, by Innovative Glass Corp) may be connected to a building electrical system by electrical wiring integrated into a composite door. As shown inFIG. 1, a door assembly, shown asdoor system100, includes an electrically-operated window (e.g., a glass window, etc.), shown asprivacy window120, connected toelectrical wiring110 routed through an interior core (e.g., a foam core, etc.), shown ascore106, of a slab, shown asdoor slab105, to a flexible conduit or electric transfer hinge115 (as shown), and into a jamb, shown asdoor jamb107. Theelectrical wiring110 may be connected directly or indirectly byexternal wiring112 with a switch, shown ascontrol switch190, installed, for example, on an interior building wall W, and connected with the building electrical system for user activation and deactivation of theprivacy window120. In other embodiments, thecontrol switch190 is additionally or alternatively disposed directly on a rear surface of the door. In still other embodiments, thecontrol switch190 is in wireless communication (e.g., RFID, Bluetooth®, infrared, Wi-Fi, etc.) with theprivacy window120 for wireless control of theprivacy window120, for example, through communication with a transceiver connected with theprivacy window120. In still other embodiments, a transceiver connected with theprivacy window120 is configured to communicate with a smart phone or other computing device C for remote user control of theprivacy window120 using, for example, a smart phone application.
• Theelectrical wiring110 may be installed in thedoor slab105 after installation of thecore106, for example, into a slot or other such cutout in thecore106. In one embodiment, a channel for theelectrical wiring110 may be drilled into thecore106 of a completed door, allowing for post-production installation of an integrated electronic system. Alternatively, in other embodiments, theelectrical wiring110 may be installed in the door cavity prior to installation of thecore106. For example, theelectrical wiring110 may be secured (e.g., taped) against an interior surface of at least one of the door skins, and thecore106 may be subsequently installed (e.g., sprayed or inserted) over and/or around theelectrical wiring110.
• In other embodiments, electronic features conventionally provided as mountable modular electronic components may be integrated into a door slab, with integrated electrical wiring connecting the electronic features to the building electrical system. As shown inFIG. 2, a door assembly, shown asdoor system200, includes an electrically-operated locking mechanism (e.g., an electronic door latch, an electronic deadbolt, an electronic strike plate, etc.), shown asdoor lock230, and security camera, shown ascamera240, connected toelectrical wiring210 routed through an interior core (e.g., a foam core, etc.), shown ascore206, of a slab, shown asdoor slab205, (installed either before or after foam installation, as discussed above) to a flexible conduit or electric transfer hinge215 (as shown), and into a jamb, shown asdoor jamb207. Thecamera240 may be fully enclosed within thedoor slab205, with only a lens of thecamera240 exposed on a front surface of the door slab205 (e.g., through an opening in the outer door skin). The camera may240 be electrically connected with one or more sensors integrated into the door slab205 (e.g., motion sensors, vibration sensors) to activate thecamera240 when activity at thedoor system200 is detected.
• To prevent contact between the electronic features and their electrical wiring connections with the core206 (which may be flammable), the electronic features and their wiring connections may be fully enclosed in housing members embedded in either or both of the outer door frame (e.g., theframe member14, etc.) and thecore206.
• As shown inFIG. 2, theelectrical wiring210 may be connected directly or indirectly byexternal wiring212 with a switch, shown ascontrol switch290, installed on an interior building wall W and connected with the building electrical system for user operation of thedoor lock230 and the camera240 (e.g., for specific control, for powering on/off, etc.). In other embodiments, thecontrol switch290 is additionally or alternatively disposed directly on a rear surface of thedoor slab205. In still other embodiments, thecontrol switch290 is in wireless communication (e.g., RFID, Bluetooth®, infrared, Wi-Fi, etc.) with any of the electronic door features, for example, through communication with a transceiver connected with the corresponding electronic door feature. Additionally or alternatively, any one or more of the electronic door features may be provided with its own control system (e.g., an integrated controller, etc.) for remote user control of the electronic feature, for example, through wireless communication (e.g., Wi-Fi, cellular, Bluetooth, etc.) with a smart phone or other computing device C (e.g., a locally stored or web-based application). Either or both of thedoor lock230 and thecamera240 may be provided with backup battery units, for example, for powered operation of thedoor lock230 and/or thecamera240 in the event of loss of power to the building.
• In some integrated electronic door systems, electronic features may require different electrical power supplies (e.g., high voltage and low voltage power supplies). As shown inFIG. 3, a door assembly, shown asdoor system300, includes (i) an electrically-operated window (e.g., a glass window, etc.), shown asprivacy window320, connected to first wiring, shown as high voltageelectrical wiring310a, and (ii) an electrically-operated locking mechanism, shown asdoor lock330, and a security camera, shown ascamera340, connected to second, different wiring, shown as low voltageelectrical wiring310b. The high voltageelectrical wiring310aand the low voltageelectrical wiring310bare routed through an interior core (e.g., a foam core, etc.), shown ascore306, of a slab, shown asdoor slab305, (installed either before or after foam installation, as discussed above) to a flexible conduit or electric transfer hinge315 (as shown), and into a jamb, shown as door jamb307, for connection with an external power source (e.g., a building power source, etc.). The high voltageelectrical wiring310aand the low voltageelectrical wiring310bmay be connected directly or indirectly byexternal wiring312 with a switch, shown ascontrol switch390, installed on an interior building wall W and connected with the building electrical system for user operation of one or more of theprivacy window320, thedoor lock330, and the camera340 (e.g., for specific control, for powering on/off, etc.). In other embodiments, thecontrol switch390 is disposed directly on a rear surface of thedoor slab205. In still other embodiments, thecontrol switch390 is in wireless communication (e.g., RFID, Bluetooth®, infrared, Wi-Fi, etc.) with any of the electronic door features, for example, through communication with a transceiver connected with the corresponding electronic door feature.
• Additionally or alternatively, any one or more of the electronic door features may be provided with its own control system (e.g., an integrated controller, etc.) for remote user control of the electronic feature, for example, through wireless communication (e.g., Wi-Fi, cellular, Bluetooth, etc.) with a smart phone or other computing device C (e.g., a locally stored or web-based application). Either or both of thedoor lock330 and thecamera340 may be provided with backup battery units, for example, for powered operation of thedoor lock330 and/or thecamera340 in the event of loss of power to the building. Additionally or alternatively, an internal power supply, shown asbackup battery395, may be integrated into thedoor slab305 for connection with one or more of the electronic features of thedoor system300 to supply backup power to the electronic features in the event of building power loss. In an exemplary embodiment, thebackup battery395 may be configured to supply only low voltage power to the corresponding low voltage electronic devices (e.g., thedoor lock330, thecamera340, etc.) without powering high voltage electronic device(s) (e.g., theprivacy window320, etc.). Thebackup battery395 may be a rechargeable battery connected with the building power supply and may be configured to recharge when power to the building is operational and/or restored.
• Referring now toFIG. 4, a schematic block diagram of an electronic control system, shown ascontrol system400, for an integrated electronic door (e.g., similar to thedoor system300 ofFIG. 3, etc.) is shown according to an exemplary embodiment. As shown inFIG. 4, thecontrol system400, a privacy window420, adoor lock430, and a camera440 are installed in adoor slab405 and connected byelectrical wiring412 through a flexible conduit orelectric transfer hinge415 to an external power source and/or to an optional internal power supply, shown asbattery backup495, positioned within thedoor slab405. As shown inFIG. 4, a light source (e.g., a LED light strip, etc.), shown as lighting element450, is installed in a jamb, shown asdoor jamb407, (e.g., above thedoor slab405, etc.) and is connected byelectrical wiring411 to an external power source, shown as building power source408. The lighting element450 and/or the camera440 may be electrically connected with one or more sensors integrated into thedoor jamb407 and/or the door slab405 (e.g., motion sensors, vibration sensors, etc.) to activate the lighting element450 and/or the camera440 when activity at thedoor slab405 is detected.
• As shown inFIG. 4, thedoor lock430, the camera440, and the lighting element450 are in wireless communication with a local Wi-Fi router, shown asrouter497, for communication with a user interface I. As one example, the user interface I may be a voice controlled personal assistant (e.g., Amazon Echo® or the like) in wireless communication with therouter497, or a smartphone or other computing device C in communication with the router via cloud service communication (e.g., cloud service management by any one or more of the door manufacturer and/or the lock, camera, and/or lighting element provider). The privacy window420 is in wireless communication (e.g., Bluetooth®, Wi-Fi, etc.) with a switch, shown ascontrol switch490, for local user control of the privacy window420 and/or the lighting element450.
• In still other embodiments, an electronic door system may include an integrated controller (e.g., a control board, a control system, etc.) embedded in a composite door for integrated, single-source control of a plurality of electronic door features. As shown inFIG. 5, a door assembly, shown asdoor system500, includes an electrically-operated window (e.g., a glass window, etc.), shown asprivacy window520, an electrically-operated locking mechanism, shown asdoor lock530, and a security camera, shown ascamera540, connected by first wiring, shown as high voltageelectrical wiring510a, and second wiring, shown as low voltageelectrical wiring510bto a controller, shown ascontrol board580, respectively. Thecontrol board580 is connected to (i) external wiring, shown as externalelectrical wiring512, and (ii) the high voltageelectrical wiring510aand the low voltageelectrical wiring510brouted through an interior core (e.g., a foam core, etc.), shown ascore506, of the door slab505 (installed either before or after foam installation, as discussed above) to an electric transfer hinge or flexible conduit515 (as shown), and into a jamb, shown asdoor jamb507, for connection with an external power source (e.g., a building power source, etc.). As shown inFIG. 5, the electrical wiring (e.g., the high voltageelectrical wiring510a, the low voltageelectrical wiring510b, the externalelectrical wiring512, etc.) is connected (directly or indirectly) with a switch, shown ascontrol switch590, installed on an interior building wall W and connected with the building electrical system for user operation of one or more of theprivacy window520, thedoor lock530, and the camera540 (e.g., for specific control, for powering on/off, etc.). In other embodiments, thecontrol switch590 is additionally or alternatively disposed directly on a rear surface of thedoor slab505. In still other embodiments, thecontrol switch590 is in wireless communication (e.g., RFID, Bluetooth®, infrared, Wi-Fi, etc.) with any of the electronic door features, for example, through communication with a transceiver connected with the corresponding electronic door feature.
• Thecontrol board580 may be provided with a wireless transceiver for wireless communication (e.g., Wi-Fi, cellular, Bluetooth, etc.) between any one or more of the installed electronic features and a smart phone or other computing device C (e.g., using a locally stored or web-based application). Additionally or alternatively, any one or more of the installed electronic features may be provided with their own control systems (e.g., an integrated controller, etc.) for remote user control of the electronic feature, for example, through wireless communication (e.g., Wi-Fi, cellular, Bluetooth, etc.) with a smart phone or other computing device C (e.g., using a locally stored or web-based application). Either or both of thedoor lock530 and thecamera540 may be provided with backup battery units, for example, for powered operation of thedoor lock530 and/or thecamera540 in the event of loss of power to the building. Additionally or alternatively, an internal power supply, shown asbackup battery595, may be integrated into thedoor slab505 for connection with one or more of the electronic features of thedoor system500 to supply backup power to the electronic features in the event of building power loss. In an exemplary embodiment, thebackup battery595 is configured to supply only low voltage power to the corresponding low voltage electronic devices (e.g., thedoor lock530, thecamera540, etc.) without powering the high voltage electronic device(s) (e.g., theprivacy window520, etc.). Thebackup battery595 may be a rechargeable battery connected with the building power supply and may be configured to recharge when power to the building is operational and/or restored.
• In other embodiments, a composite door may include electrical features and wiring embedded or otherwise disposed in an outer frame portion (e.g., theframe member14, etc.) of the door such that a door may be assembled from a complete, electronics-integrated door frame member, for example, to reduce door assembly time. As shown inFIG. 6, a door assembly, shown asdoor system600, includes an electrically-operated window (e.g., a glass window, etc.), shown asprivacy window620, an electrically-operated locking mechanism, shown asdoor lock630, and a security camera, shown ascamera640, connected by first wiring, shown as high voltageelectrical wiring610a, and second wiring, shown as low voltageelectrical wiring610b, to a controller, shown ascontrol board680, respectively. Thecontrol board680 is connected to (i) external wiring, shown aselectrical wiring612, and (ii) the high voltageelectrical wiring610aand the low voltageelectrical wiring610brouted through an interior core (e.g., a foam core, etc.), shown ascore606, of the door slab605 (installed either before or after foam installation, as discussed above) to an electric transfer hinge or flexible conduit615 (as shown), and into a jamb, shown asdoor jamb607, for connection with an external power source (e.g., a building power source, etc.). Theelectrical wiring610a,610b,612 is routed through channels in a door frame member (e.g., like theframe member14; a through hole drilled or otherwise formed in the upper door rail, and the inner and outer door stiles; etc.), shown asframe601. Thecamera640 is retained in a first modular housing, shown ascamera housing641, received in a cavity in an upper edge of an upper door rail of theframe601 with a lens of thecamera640 aligned with an aperture in the door slab605 (e.g., an outer door skin thereof, etc.). Thecontrol board680 is retained in a second modular housing, shown as acontroller housing681, received in the upper edge of the upper door rail of theframe601. In other embodiments, thecontroller housing681 is otherwise positioned within the frame601 (e.g., received in the outer edge of one of the door stiles, etc.). The housing enclosures may protect the circuitry of thecontrol board680 and/or thecamera640, and their electrical wiring connections, from contact with the core606 (e.g., which may be constructed from flammable material, etc.).
• As shown inFIG. 6, the electrical wiring (e.g., the high voltageelectrical wiring510a, the low voltageelectrical wiring510b, the externalelectrical wiring512, etc.) is connected (directly or indirectly) with a switch, shown ascontrol switch690, installed on an interior building wall W and connected with the building electrical system for user operation of one or more of theprivacy window620, thedoor lock630, and the camera640 (e.g., for specific control, for powering on/off, etc.). In other embodiments, thecontrol switch690 is additionally or alternatively disposed directly on a rear surface of thedoor slab605. In still other embodiments, thecontrol switch690 is in wireless communication (e.g., RFID, Bluetooth®, infrared, Wi-Fi, etc.) with any of the electronic door features, for example, through communication with a transceiver connected with the corresponding electronic door feature.
• Thecontrol board680 may be provided with a wireless transceiver for wireless communication (e.g., Wi-Fi, cellular, Bluetooth, etc.) between any one or more of the installed electronic features and a smart phone or other computing device C (e.g., using a locally stored or web-based application). Additionally or alternatively, any one or more of the installed electronic features may be provided with their own control systems (e.g., an integrated controller, etc.) for remote user control of the electronic feature, for example, through wireless communication (e.g., Wi-Fi, cellular, Bluetooth, etc.) with a smart phone or other computing device C (e.g., using a locally stored or web-based application). Either or both of thedoor lock630 and thecamera640 may be provided with backup battery units, for example, for powered operation of thedoor lock630 and/or thecamera640 in the event of loss of power to the building. Additionally or alternatively, an internal power supply, shown asbackup battery695, may be integrated into thedoor slab605 for connection with one or more of the electronic features of thedoor system600 to supply backup power to the electronic features in the event of building power loss. In an exemplary embodiment, thebackup battery695 may be configured to supply only low voltage power to the corresponding low voltage electronic devices (e.g., thedoor lock630, thecamera640, etc.) without powering the high voltage electronic device(s) (e.g., the privacy window620). Thebackup battery695 may be a rechargeable battery connected with the building power supply and may be configured to recharge when power to the building is operational and/or restored. Like thecontrol board680, thebackup battery695 may be enclosed in a third housing installed in theframe601, for example, to facilitate installation, and/or to provide a fire safe enclosure for thebackup battery695 and its wiring connections.
• Referring now toFIG. 7, a schematic block diagram of an electronic control system, shown ascontrol system700, for an integrated electronic door (e.g., similar to thedoor system600 ofFIG. 6, etc.) is shown according to an exemplary embodiment. As shown inFIG. 7, thecontrol system700, aprivacy window720, adoor lock730, and acamera740 are installed in adoor slab705 and connected by electrical wiring to a controller, shown ascontrol board780, which is connected byelectric wiring712 through anelectric transfer hinge715 to an external power source, and to an optional internal power supply, shown asbackup battery795, disposed within thedoor slab705. As shown inFIG. 7, a light source (e.g., a LED light strip, etc.), shown aslighting element750, is installed in a jamb, shown asdoor jamb707, (e.g., above thedoor slab705, etc.) and is connected by electrical wiring711 to an external power source, shown as building power source708.
• Thecontrol board780 is in wireless communication with a local Wi-Fi router, shown asrouter797, for communication with a user interface I. As one example, the user interface I may be a voice controlled personal assistant (e.g., Amazon Echo® or the like) in wireless communication with therouter797, or a smartphone or other computing device C in communication with the router via cloud service communication (e.g., cloud service management by any one or more of the door manufacturer and/or the lock, camera, and/or lighting element provider). Theprivacy window720 may be in wireless communication (e.g., Bluetooth®) with a wall mountedcontrol switch790 for local user control of theprivacy window720.
• Electronic Door System
• According to the exemplary embodiment shown inFIG. 11, a door system (e.g., a smart door system, etc.), shown aselectronic door system1000, includes a door assembly, shown aselectronic door assembly1100, (i) electrically coupled to a first power source (e.g., a mains power supply, a building power system, etc.), shown asexternal power source1602, and (ii) communicably coupled to (a) an intermediary device, shown aswireless router1600, (b) one or more user devices (e.g., a smartphone, a mobile phone, a cell phone, a tablet, a laptop, a computer, a smartwatch, a smartcard, a keycard, etc.), shown asuser devices1900, directly and/or indirectly via thewireless router1600, and (c) one or more remote servers, shown asdoor server1700 andcamera server1800, via thewireless router1600 and/or theuser devices1900. According to an exemplary embodiment, thedoor server1700 and thecamera server1800 are independent servers (e.g., the functions performed by one server are not performed by the other server, etc.). In some embodiments, thedoor server1700 and/or thecamera server1800 include a plurality of servers. In some embodiments, thedoor server1700 and thecamera server1800 are a single server or a single plurality of servers (e.g., the functions of thedoor server1700 and thecamera server1800 described herein may be performed by the same server(s), etc.).
• As shown inFIG. 11, theelectronic door assembly1100 includes various electrically-operated components including a first electrically-operated component, shown aswireless bridge1200, a second electrically-operated component, shown as lockingsystem1300, a third electrically-operated component, shown ascamera system1400, and a fourth electrically-operated component, shown ascontroller1500. In some embodiments, theelectronic door assembly1100 does not include one or more of thewireless bridge1200, thelocking system1300, thecamera system1400, and thecontroller1500.
• As shown inFIG. 11, thedoor server1700 and/or thecamera server1800 are configured to communicate with the user devices1900 (e.g., using a first communication protocol, using a long-range communication protocol, cellular, Internet, radio, etc.) and theuser devices1900 are configured to (i) communicate directly with one or more components of the electronic door assembly1100 (e.g., using a second communication protocol, using a short-range communication protocol, Bluetooth, Bluetooth low energy (“BLE”), near-field communication (“NFC”), radio frequency identification (“RFID”), Wi-Fi, using a long-range communication protocol, cellular, etc.) and/or (ii) communicate indirectly with one or more components of the electronic door assembly1100 (e.g., using a third communication protocol, Wi-Fi, BLE, etc.) through thewireless router1600 and/or the wireless bridge1200 (e.g., when within BLE range, when within range of thewireless router1600, when within range of thewireless bridge1200, etc.). Theuser devices1900 may thereby function as an intermediary device that facilitates data transmissions between (i) thedoor server1700 and/or thecamera server1800 and (ii) one or more components of the electronic door assembly1100 (e.g., one or more components of theelectronic door assembly1100 may be “disconnected devices” that do not communicate with thedoor server1700 and/or thecamera server1800, etc.). In some embodiments, theuser devices1900 are configured to communicate with one or more components of theelectronic door assembly1100 through thedoor server1700, thecamera server1800, thewireless router1600, and/or the wireless bridge1200 (e.g., when not within wireless range of theelectronic door assembly1100, etc.). In some embodiments, thecamera server1800 does not communicate directly with theuser devices1900. In such embodiments, thecamera server1800 may communicate with theuser devices1900 through the door server1700 (e.g., thedoor server1700 functions as an intermediary, etc.).
• As shown inFIG. 11, thedoor server1700 and/or thecamera server1800 are configured to communicate with the wireless router1600 (e.g., using a long-range communication protocol, Internet, etc.) and thewireless router1600 is configured to (i) communicate directly with one or more components of the electronic door assembly1100 (e.g., using Wi-Fi, etc.) and/or (ii) communicate indirectly with one or more components of theelectronic door assembly1100 through the wireless bridge1200 (e.g., using Wi-Fi, etc.). Thewireless router1600 may thereby function as an intermediary device that facilitates data transmissions between (i) thedoor server1700 and/or thecamera server1800 and (ii) one or more components of theelectronic door assembly1100.
• According to an exemplary embodiment, thedoor server1700 is configured to manage a plurality of access credentials or user profiles for one or more users that have access to thelocking system1300, thecamera system1400, and/or thecontroller1500 of theelectronic door assembly1100. In general, a user profile may include one or more files that include data related to operation of thelocking system1300, thecamera system1400, and/or thecontroller1500. For example, the user profile may contain a user schedule of when an associatedlocking system1300 may be accessed (unlocked, locked, etc.). The schedule may specify lock access permissions, e.g., by day of the week, including starting times (hours, minutes, etc.) and ending times (hours, minutes, etc.) for each corresponding permission. For example, a schedule may specify the time spans in which the associatedlocking system1300 may be unlocked via theuser device1900 of the specific user associated with the user profile. As another example, the schedule may specify time periods in which typical interactions are expected to occur, and a level of trust may be determined based on these time periods. Accordingly, an unlock request sent within an expected time period may be more trusted by the associatedlocking system1300 than a request sent at an unexpected/atypical time. In one embodiment, a default user schedule is set (e.g., by the manufacturer, etc.). Additionally, a list of typical user schedules may also be provided to allow a user to select from one of many configuration options. In this manner, a manufacturer may provide various recommended operational settings to a user. A user may also customize a schedule to tailor the schedule as he or she desires (e.g., an administrator, etc.).
• A user profile may further specify a model/serial number of the associatedlocking system1300 and what types of accesses are available for that user. For example, such accesses may include: reading software/hardware version information of the associatedlocking system1300, updating software of the associatedlocking system1300, reading a shackle/latch/dead-bolt state of the associatedlocking system1300, locking, unlocking, disarming, reading/setting a time/clock value, reading a battery level, reading/clearing event related data (e.g., flags, counters, etc.), reading a log of the lock, reading/setting/resetting a keypad code of the associatedlocking system1300, reading communications data for the associated locking system1300 (e.g., transmission statuses, transmission power levels, channel information, addressing information, etc.), reading/setting default values stored for the associated locking system1300 (e.g., default disarm times, default unlock times, etc.), among others. A user profile may also specify a start time and a revocation date/time for the user profile (i.e., when the user profile begins to be valid and when the user profile expires and is no longer valid). A user profile may provide maximum disarm/unlock times for the associatedlocking system1300. A user profile may also provide an indication of a trust level of a corresponding user device1900 (e.g., whether a time value/timestamp provided by theuser device1900 is trusted or not). Thelocking system1300 may be configured to allow or disallow certain functionality based on the trust level of arespective user device1900 requesting access thereto. The trust level may be stored as an independent permission that the user may or may not have access to (e.g., the trust level may be managed/adjusted by the software of thelocking system1300, theuser device1900, thedoor server1700, etc.). As an example, only a highly trusteduser device1900 may be able to upgrade the firmware of arespective locking system1300 or change certain settings.
• Additionally, thelocking system1300 may have a security algorithm that factors in a trust level and time value. For example, as arespective user device1900 successfully interacts with arespective locking system1300 more often, therespective locking system1300 may increase (or adjust) a trust level for therespective user device1900. However, if a time value is out of sync with the maintained time of therespective locking system1300 or authentication fails, therespective locking system1300 may decrease (or adjust) a trust level for therespective user device1900. The time value provided by therespective user device1900 may be compared to a time value maintained by therespective locking system1300, and a degree of closeness between the two times may be used to indicate a trust level for the respective user device1900 (e.g., the closer the two times are to being in sync, the higher the trust level, etc.). If a trust level decreases below a certain threshold, therespective locking system1300 may discontinue or limit interactions with therespective user device1900. A trust level may also be based on the schedule discussed above. For example, arespective user device1900 may be regarded as more or less trusted based on the time therespective user device1900 is accessing arespective locking system1300, and whether that time falls within certain time periods as defined by the schedule. The time value provided by therespective user device1900 may also be used to sync the clock of arespective locking system1300 with that of therespective user device1900 or may be used otherwise during authenticated communications. Any of the user profile items discussed may have default values (e.g., manufacturer defaults) or user provided values (e.g., from a user with administrator permission access, etc.). A user profile is not limited to the above data, and additional data may be included or excluded.
• According to an exemplary embodiment, theelectronic door system1000 implements an approach that provides for secure communication between theuser device1900 and thelocking system1300 using a two key authentication scheme, without both keys being stored on the locking system1300 (e.g., during a manufacturing phase). In such an embodiment, (i) a first key or a device key is known/stored on thelocking system1300 and thedoor server1700 that is unique to thelocking system1300 and (ii) a second key or a user key is known/stored on each of theuser devices1900 that is unique to each of theuser devices1900 or user profiles and not pre-stored on thelocking system1300. Each device key, each user key, and each user profile may be specific to arespective locking system1300. In this manner, the device key, the user key, and the user profile may uniquely relate to asingle locking system1300. According to an exemplary embodiment, thedoor server1700 is configured to encrypt each user profile with the device key of thelocking system1300 that the user profile is associated with. When attempting to access alocking system1300, auser device1900 may receive a device identifier from thelocking system1300 and compare the device identifier to a list of device identifiers associated with one or more encrypted user profiles currently loaded onto the user device1900 (e.g., that were delivered according to a profile delivery protocol, etc.). If a match is found, theuser device1900 may transmit the associated encrypted user profile to thelocking system1300. The encrypted user profile includes the user key. Thelocking system1300 may decrypt the encrypted user profile using the device key pre-stored thereon to obtain the user key. Theuser device1900 may then generate and transmit an encrypted command to thelocking system1300. The encrypted command is encrypted using the user key. Thelocking system1300 may then decrypt the encrypted command using the user key obtained from the decrypted user profile and initiate the action specified by the decrypted command (e.g., unlocking a physical locking component, implementing a firmware update, etc.). In some embodiments, the two key authentication process including the device key and the user key additionally includes a handshake nonce, a reply nonce, and/or a modified reply nonce, as described in more detail herein.
• It should be understood that the two key authentication scheme described herein between thedoor server1700, theuser devices1900, and thelocking systems1300 may similarly be applied between (i) thedoor server1700, theuser devices1900, and thecontroller1500, (ii) thedoor server1700, theuser devices1900, and thecamera system1400, and/or (iii) thecamera server1800, theuser devices1900, and thecamera system1400.
• Further, it should be understood that the two key authentication scheme described herein is not meant to be limiting, but is provided as an example of one possible way to provide secure communication between thedoor server1700, theuser devices1900, and thelocking systems1300 of theelectronic door system1000. In other embodiments, secure communication is otherwise established using a different authentication scheme such as an authentication scheme that employs digital signatures, challenge-response procedures, multi-factor authentication (e.g., two-factor authentication, user profile plus a biometric, a user profile plus a PIN, etc.), and/or still other suitable authentication schemes. Further, such a two-key authentication scheme may or may not be used in implementations where a component of theelectronic door assembly1100 is in direct communication with thedoor server1700 and/or the camera server1800 (i.e., the communication is routed through thewireless router1600, not the user devices1900).
Electronic Door Assembly
• As shown inFIGS. 12 and 13, theelectronic door assembly1100 includes a door, shown asdoor1102, having a slab (e.g., a solid slab, a composite slab, etc.), shown asdoor slab1104; a jamb, shown asdoor jamb1106; a knob, shown asdoor knob1108, configured to facilitate opening thedoor1102; and one or more hinges, shown ashinges1110, pivotally coupling a hinged edge of thedoor slab1104 to thedoor jamb1106. According to the exemplary embodiment shown inFIGS. 12 and 13, one of thehinges1110 is an electric transfer hinge that facilitates connecting one or more electrically-operated door components of the electronic door assembly1100 (e.g., thewireless bridge1200, thelocking system1300, thecamera system1400, thecontroller1500, etc.) to theexternal power source1602. In other embodiments, all of thehinges1110 are standard mechanical hinges and the electrically-operated door components are otherwise coupled to the external power source1602 (e.g., via an electrical conduit, etc.).
• As shown inFIGS. 12 and 13, thedoor1102 includes a first transparent panel, shown aswindow1112, embedded within thedoor slab1104. Thewindow1112 includes a privacy element, shown asblocker1114, embedded therein or integrated therewith. In some embodiments, theblocker1114 is or includes electrically-controllable shades/blinds disposed within thewindow1112 or disposed along an interior side of thewindow1112. In some embodiments, theblocker1114 is additionally or alternatively integrated into or disposed along thewindow1112 such that thewindow1112 has an electrically-controllable opacity (e.g., an electrically-controllable coating, an electrically-controllable film, etc.). In some embodiments, thedoor1102 does not include thewindow1112 or thewindow1112 does not include theblocker1114.
• As shown inFIGS. 12 and 13, thedoor1102 includes side panels, shown aspanels1116, disposed along the right side and the left side of thedoor jamb1106. In other embodiments, thedoor1102 includes only one of thepanels1116 along the right side of thedoor jamb1106 or the left side of thedoor jamb1106. In still other embodiments, thedoor1102 does not include thepanels1116. As shown inFIGS. 12 and 13, each of thepanels1116 includes a second transparent panel, shown aswindow1118, embedded within thepanels1116. Thewindows1118 include privacy elements, shown asblockers1120, embedded therein or integrated therewith. In some embodiments, theblockers1120 are or include electrically-controllable shades/blinds disposed within thewindows1118 or disposed along an interior side of thewindows1118. In some embodiments, theblockers1120 are additionally or alternatively integrated into or disposed along thewindows1118 such that thewindows1118 have an electrically-controllable opacity (e.g., an electrically-controllable coating, an electrically-controllable film, etc.). In some embodiments, theblockers1120 are the same as theblocker1114. In some embodiments, theblockers1120 are different than theblocker1114. In some embodiments, thepanels1116 do not include thewindows1118 or thewindows1118 do not include theblockers1120.
• As shown inFIGS. 12 and 13, theelectronic door assembly1100 includes a light source, shown aslighting system1122, including one or more lighting elements, shown as lights1124. In some embodiments, thelights1124 are separate from thedoor1102 and configured to be disposed along an exterior surface of a building proximate thedoor1102. In some embodiments, thelights1124 are integrated into the door1102 (e.g., thedoor slab1104, thedoor jamb1106, thepanels1116, etc.). In some embodiments, thelights1124 are selectively/releasably coupled to the door1102 (e.g., thedoor1102 includes one or more light sockets that may be selectively accessed, etc.). In some embodiments, theelectronic door assembly1100 does not include thelighting system1122.
• As shown inFIGS. 12 and 13, one or more of thewireless bridge1200, thelocking system1300, thecamera system1400, and thecontroller1500 are integrated into thedoor1102. In some embodiments, one or more of thewireless bridge1200, thelocking system1300, thecamera system1400, and thecontroller1500 are integrated into thedoor1102 at the time of manufacture. In other embodiments, one or more of thewireless bridge1200, thelocking system1300, thecamera system1400, and thecontroller1500 are integrated into thedoor1102 post-manufacture (e.g., by a retailer, by a contractor, by the end consumer, etc.). In some embodiments, one or more of thewireless bridge1200, thelocking system1300, thecamera system1400, and thecontroller1500 are separate from thedoor1102 or coupled to an exterior thereof.
• According to an exemplary embodiment, theelectronic door assembly1100 is a modular door assembly. As shown inFIGS. 12 and 13, thedoor slab1104 includes a first selectively-accessible connection box, shown as lockingsystem connection box1130, embedded in thedoor slab1104. In other embodiments, the lockingsystem connection box1130 is embedded in thedoor jamb1106 and/or thepanels1116. In some embodiments, the lockingsystem connection box1130 includes a door or cover that facilitates selectively accessing an interior of the lockingsystem connection box1130. As shown inFIGS. 12 and 13, the lockingsystem connection box1130 includes a first interface (e.g., an electrical connector, etc.), shown as lockingsystem interface1132, disposed within the interior of the lockingsystem connection box1130 and configured to selectively interface with a first connector of thelocking system1300. Accordingly, thedoor1102 can be manufactured and sold without thelocking system1300 and then the end user can select and install a locking system of their choosing (whether electrically-operated or mechanically-operated). In other embodiments, thelocking system1300 is provided with and/or hardwired into thedoor1102.
• As shown inFIGS. 12 and 13, thedoor slab1104 includes a second selectively-accessible connection box, shown as camerasystem connection box1140, embedded in thedoor slab1104. In other embodiments, the camerasystem connection box1140 is embedded in thedoor jamb1106 and/or thepanels1116. In some embodiments, the camerasystem connection box1140 includes a door or cover that facilitates selectively accessing an interior of the camerasystem connection box1140. As shown inFIGS. 12 and 13, the camerasystem connection box1140 is configured to selectively receive and hold thecamera system1400. In some embodiments, the door or cover of the camerasystem connection box1140 is replaced with a door or cover that defines an aperture when thecamera system1400 is installed in the door1102 (e.g., such that a camera lens of thecamera system1400 can see outside of the camerasystem connection box1140, etc.). As shown inFIGS. 12 and 13, the camerasystem connection box1140 includes a second interface (e.g., an electrical connector, etc.), shown ascamera system interface1142, disposed within the interior of the camerasystem connection box1140 and configured to selectively interface with a second connector of thecamera system1400. Accordingly, thedoor1102 can be manufactured and sold without thecamera system1400 and then the end user can select and install a camera system of their choosing. In other embodiments, thecamera system1400 is provided with and/or hardwired into thedoor1102.
• As shown inFIGS. 12 and 13, thedoor slab1104 includes a third selectively-accessible connection box, shown ashinge connection box1150, embedded in thedoor slab1104. In some embodiments, thehinge connection box1150 includes a door or cover that facilitates selectively accessing an interior of thehinge connection box1150. As shown inFIGS. 12 and 13, thehinge connection box1150 includes a third interface (e.g., an electrical connector, etc.), shown ashinge interface1152, disposed within the interior of thehinge connection box1150 and configured to selectively interface with a third connector of one of thehinges1110. Accordingly, thedoor1102 can be manufactured and sold without an electric transfer hinge and then the end user can select and install an electric transfer hinge as desired. In other embodiments, one of thehinges1110 is an electric transfer hinge and is provided with and/or hardwired into thedoor1102.
• As shown inFIGS. 12 and 13, the lockingsystem connection box1130 and the camerasystem connection box1140 are electrically coupled to the hinge connection box1150 (e.g., hardwired, connected during manufacturing, etc.) and thehinge1110 is configured to be electrically connected to theexternal power source1602. Thehinge1110 may therefore facilitate powering thelocking system1300 and thecamera system1400 with theexternal power source1602. As shown inFIGS. 12 and 13, thewindow1112 is electrically connected to thehinge connection box1150. In other embodiments, thewindow1112 is electrically connected directly to thehinge1110. Thehinge1110 may therefore facilitate powering theblocker1114 of thewindow1112 with theexternal power source1602. As shown inFIGS. 12 and 13, thewindows1118 are electrically connected directly to thehinge1110. In other embodiments, thewindows1118 are electrically connected to thehinge connection box1150. Thehinge1110 may therefore facilitate powering theblockers1120 of thewindow1118 with theexternal power source1602. As shown inFIGS. 12 and 13, thelighting system1122 is electrically connected directly to thehinge1110. In other embodiments, thelighting system1122 is electrically connected to thehinge connection box1150. Thehinge1110 may therefore facilitate powering thelighting system1122 with theexternal power source1602. In still other embodiments, thelighting system1122 is directly connected to theexternal power source1602.
• As shown inFIG. 12, thewireless bridge1200 is separate from thedoor1102 and connected to the external power source1602 (e.g., a wall outlet proximate thedoor1102, etc.). As shown inFIG. 13, thewireless bridge1200 is disposed within thedoor1102 and connected to theexternal power source1602 through thehinge connection box1150 and/or thehinge1110. As shown inFIG. 13, thedoor slab1104 includes a fourth selectively-accessible connection box, shown as wirelessbridge connection box1160, embedded in thedoor slab1104 and connected to thehinge connection box1150. In other embodiments, the wirelessbridge connection box1160 is embedded in thedoor jamb1106 and/or thepanels1116. In some embodiments, the wirelessbridge connection box1160 includes a door or cover that facilitates selectively accessing an interior of the wirelessbridge connection box1160. As shown inFIG. 13, the wirelessbridge connection box1160 is configured to selectively receive and hold thewireless bridge1200. The wirelessbridge connection box1160 includes a fourth interface (e.g., an electrical connector, etc.), shown aswireless bridge interface1162, disposed within the interior of the wirelessbridge connection box1160 and configured to selectively interface with a fourth connector of thewireless bridge1200. Accordingly, thedoor1102 can be manufactured and sold without thewireless bridge1200 and then the end user can select and install a wireless bridge of their choosing. In other embodiments, thewireless bridge1200 is provided with and/or hardwired into thedoor1102. In still other embodiments, theelectronic door assembly1100 does not include thewireless bridge1200. In such embodiments, thelocking system1300, thecamera system1400, and/or thecontroller1500 may have the functionality of thewireless bridge1200, as described in more detail herein.
• As shown inFIG. 12, thecontroller1500 is separate from thedoor1102 and connected to theblocker1114, theblockers1120, and thelighting system1122 to facilitate controlling the operation thereof with thecontroller1500. According to the exemplary embodiment shown inFIG. 12, thecontroller1500 is coupled to theexternal power source1602 via thehinge1110 and/or thehinge connection box1150. In other embodiments, thecontroller1500 is directly coupled to theexternal power source1602. In some embodiments, thecontroller1500 is additionally or alternatively connected to thelocking system1300 and/or thecamera system1400 to facilitate controlling the operation thereof with thecontroller1500.
• As shown inFIG. 13, thecontroller1500 is disposed within thedoor1102 and connected to theexternal power source1602 through thehinge connection box1150 and/or thehinge1110. As shown inFIG. 13, thedoor slab1104 includes a fifth selectively-accessible connection box, shown ascontroller connection box1170, embedded in thedoor slab1104 and connected to thehinge connection box1150. In other embodiments, thecontroller connection box1170 is embedded in thedoor jamb1106 and/or thepanels1116. In some embodiments, thecontroller connection box1170 includes a door or cover that facilitates selectively accessing an interior of thecontroller connection box1170. As shown inFIG. 13, thecontroller connection box1170 is configured to selectively receive and hold thecontroller1500. Thecontroller connection box1170 includes a fifth interface (e.g., an electrical connector, etc.), shown ascontroller interface1172, disposed within the interior of thecontroller connection box1170 and configured to selectively interface with a fifth connector of thecontroller1500. Accordingly, thedoor1102 can be manufactured and sold without thecontroller1500 and then the end user can select and install acontroller1500 at the time of their choosing. In other embodiments, thecontroller1500 is provided with and/or hardwired into thedoor1102. In still other embodiments, theelectronic door assembly1100 does not include thecontroller1500. In such embodiments, thelocking system1300 and/or thecamera system1400 may have the functionality of thecontroller1500.
• As shown inFIGS. 12 and 13, thecontroller1500 is connected to a user interface, shown asswitch1606. According to an exemplary embodiment, theswitch1606 is configured to facilitate selectively activating theblocker1114, theblockers1120, and/or thelighting system1122. In some embodiments, theswitch1606 is configured to be installed in a wall proximate thedoor1102. In some embodiments, theswitch1606 is configured to be installed along thedoor slab1104 and/or the panels1116 (e.g., along an interior surface thereof, etc.). In some embodiments, theswitch1606 is wirelessly connected to thecontroller1500. In some embodiments, theswitch1606 is connected to thecontroller1500 via a wired connection. In some embodiments, thecontroller1500 is embedded within theswitch1606.
• As shown inFIGS. 12 and 13, thedoor1102 includes a secondary power source, shown asinternal energy storage1604, disposed within thedoor slab1104. In some embodiments, theinternal energy storage1604 is additionally or alternatively disposed within thedoor jamb1106 and/or thepanels1116. In some embodiments, theinternal energy storage1604 is removable. According to an exemplary embodiment, theinternal energy storage1604 is configured to provide power to one or more components of the door1102 (e.g., thewireless bridge1200, thelocking system1300, thecamera system1400, thecontroller1500, thelighting system1122, etc.) in the event that theexternal power source1602 stops powering the components of the electronic door assembly1100 (e.g., in the event of a power outage, etc.). In some embodiments, thedoor1102 does not include theinternal energy storage1604.
• In some embodiments, theelectronic door assembly1100 is voice activation capable. Theelectronic door assembly1100 may be configured to accept various voice commands to the control thelocking system1300, thecamera system1400, thewindow1112, thewindows1118, and/or thelighting system1122. By way of example, the voice commands may include a command to lock or unlock a locking mechanism of thelocking system1300. By way of another example, the voice command may include a command to activate or deactivate a camera device of thecamera system1400. By way of yet another example, the voice command may include a command to activate or deactivate thewindow1112 and/or thewindows1118. By way of still another example, the voice command may include a command to turn on or turn off thelights1124 of thelighting system1122.
• In one implementation, theelectronic door assembly1100 may include a microphone within thedoor1102, thelocking system1300, thecamera system1400, and/or thecontroller1500. For example, the microphone of theelectronic door assembly1100 may be configured to acquire sound data indicative of a voice command. A component of the electronic door assembly1100 (e.g., a processing circuit of thelocking system1300, thecamera system1400, thecontroller1500, etc.) may be configured to analyze the sound data to determine the voice command. In some implementations, the component of theelectronic door assembly1100 may be configured to perform a voice authentication process to determine whether the person is permitted to provide voice commands to theelectronic door assembly1100. The component of theelectronic door assembly1100 may then provide the received voice command to an appropriate component of the electronic door assembly1100 (e.g., thelocking system1300, thecamera system1400, thecontroller1500, etc.) to take action (e.g., lock, unlock, activate, deactivate, turn on, turn off, etc.).
• In another implementation, theelectronic door assembly1100 may be connectable to an external device that has a microphone such as (i) a smart hub device or a portable smart device (e.g., a smartphone, a smartwatch, a tablet, etc.) having a digital personal assistant (e.g., Amazon Alexa, Google Assistant, Microsoft Cortana, etc.) or (ii) theswitch1606. For example, a microphone of the external device may be configured to acquire sound data indicative of a voice command. The external device (e.g., a processing circuit thereof, etc.) may be configured to analyze the sound data to determine the voice command. In some implementations, the external device may be configured to perform a voice authentication process to determine whether the person is permitted to provide voice commands to theelectronic door assembly1100. The external device may then provide the received voice command to an appropriate component of the electronic door assembly1100 (e.g., thelocking system1300, thecamera system1400, thecontroller1500, etc.) to take action (e.g., lock, unlock, activate, deactivate, turn on, turn off, etc.). As another example, a microphone of the external device may be configured to acquire sound data indicative of a voice command and then the external device may transmit the sound data to a component of theelectronic door assembly1100 for further processing as described above.
Wireless Bridge
• In general, thewireless bridge1200 is configured to receive a first wireless signal in a first communication protocol and convert the first signal to a second wireless signal in a second communication protocol, and vice versa. As shown inFIG. 14, thewireless bridge1200 includes aprocessing circuit1202, afirst transceiver1222, and asecond transceiver1224. In some embodiments, thewireless bridge1200 includes adoor connector1226 configured to interface with thewireless bridge interface1162. In some embodiments, thewireless bridge1200 includes an outlet connector1228 (e.g., a wall plug, etc.) configured to interface directly with the external power source1602 (e.g., a wall outlet, etc.). In some embodiments, thewireless bridge1200 does not include thedoor connector1226 or theoutlet connector1228. In such embodiments, thewireless bridge1200 may be hardwired within thedoor1102.
• As shown inFIG. 14, theprocessing circuit1202 has aprocessor1204 and amemory1206. Theprocessing circuit1202 may include a general-purpose processor, an ASIC, one or more FPGAs, a DSP, circuits containing one or more processing components, circuitry for supporting a microprocessor, a group of processing components, or other suitable electronic processing components. In some embodiments, theprocessor1204 is configured to execute computer code stored in thememory1206 to facilitate the activities described herein. Thememory1206 may be any volatile or non-volatile computer-readable storage medium capable of storing data or computer code relating to the activities described herein. According to an exemplary embodiment, thememory1206 includes computer code modules (e.g., executable code, object code, source code, script code, machine code, etc.) configured for execution by theprocessor1204.
• According to an exemplary embodiment, thefirst transceiver1222 is configured to receive and transmit wireless signals using a first wireless communication protocol. By way of example, the first wireless communication protocol may be a short-range communication protocol. In one embodiment, thefirst transceiver1222 includes Bluetooth components for establishing a Bluetooth connection with a Bluetooth enabled device (e.g., theuser devices1900, thelocking system1300, thecontroller1500, etc.). According to an exemplary embodiment, thesecond transceiver1224 is configured to receive and transmit wireless signals using a second wireless communication protocol. By way of example, the second wireless communication protocol may be a short-range communication protocol. In one embodiment, thesecond transceiver1224 includes Wi-Fi components for establishing a Wi-Fi connection with a Wi-Fi enabled device (e.g., theuser devices1900, thelocking system1300, thecontroller1500, thewireless router1600, etc.). In another embodiment, thefirst transceiver1222 and/or thesecond transceiver1224 include different types of components that facilitate a different type of short-range wireless communication protocol (e.g., radiofrequency, RFID, ZigBee, NFC, etc.). In other embodiments, thefirst transceiver1222 and/or thesecond transceiver1224 include components that facilitate a long-range wireless communication protocol (e.g., cellular, etc.)
• As shown inFIG. 14, thememory1206 of thewireless bridge1200 includes abridge circuit1208. Thebridge circuit1208 may be configured to convert a first wireless signal received by thefirst transceiver1222 in a first wireless communication protocol (e.g., BLE, cellular, etc.) to a second wireless signal in a second communication protocol (e.g., Wi-Fi, BLE, etc.) to be emitted by thesecond transceiver1224. Thebridge circuit1208 may be also configured to convert the second wireless signal received by thesecond transceiver1224 in the second wireless communication protocol to the first wireless signal in the first communication protocol to be emitted by thefirst transceiver1222.
• As shown inFIG. 14, thebridge circuit1208 includes adevice circuit1210, aprofile management circuit1212, and acommunication circuit1214. Thedevice circuit1210 is configured to acquire a device identifier from devices proximate the wireless bridge1200 (e.g., based on an identifier broadcasted by arespective locking system1300, arespective controller1500, arespective camera system1400, etc.). Theprofile management circuit1212 is configured to receive and store encrypted bridge profiles and bridge keys sent to thewireless bridge1200 by thedoor server1700, as described in more detail herein.
• Thecommunication circuit1214 is configured to generate and transmit an encrypted command to a respective component of a respectiveelectronic door assembly1100. The encrypted command may include a command for therespective locking system1300, therespective camera system1400, and/or therespective controller1500 to initiate a communication session with thewireless bridge1200. According to an exemplary embodiment, the command is encrypted using the bridge key associated with the bridge profile that was transmitted to a component of the respectiveelectronic door assembly1100 at the start of the communication session. In some embodiments, thecommunication circuit1214 is configured to generate a modified reply nonce based on a reply nonce received from the component of the respectiveelectronic door assembly1100 as described in more detail herein (e.g., in response to the component of the respectiveelectronic door assembly1100 successfully decrypting the encrypted bridge profile, etc.). In such embodiments, thecommunication circuit1214 is configured to encrypt the command using both the bridge key and the modified reply nonce.
Locking System
• In general, thelocking system1300 is configured to receive an encrypted user profile from arespective user device1900 or the door server1700 (e.g., directly, indirectly through thewireless bridge1200, indirectly through thewireless router1600, etc.) and make an access and/or a management control decision based on the encrypted user profile (e.g., whether to permit unlocking, updating, etc. by the respective user device1900). In some embodiments, thelocking system1300 is or includes an electronic door lock such as an electrically operated deadbolt. In some embodiments, thelocking system1300 is or includes an electric strike. In some embodiments, thelocking system1300 is or includes a magnetically operated locking mechanism (e.g., an electromagnetic locking mechanism, etc.). In some embodiments, thelocking system1300 is or includes a mortise locking mechanism. In some embodiments, thelocking system1300 is or includes a multi-point lockset. In some embodiments, thelocking system1300 includes two or more of the above in combination. In some embodiments (e.g., embodiments where theelectronic door assembly1100 does not include thecontroller1500, etc.), the functions of thecontroller1500 described herein may be performed by thelocking system1300. In some embodiments, the functions of thelocking system1300 described herein may be performed by thecontroller1500. In some embodiments, operation of thelocking system1300 is controllable independent of the controller1500 (e.g., thecontroller1500 and thelocking system1300 perform independent authentication processes, etc.).
• As shown inFIG. 15, thelocking system1300 includes aprocessing circuit1302, afirst transceiver1322, asecond transceiver1324, adoor connector1326, auser interface1328, alock mechanism1330, and abattery1332. In some embodiments, thelocking system1300 does not include thesecond transceiver1324, thedoor connector1326, and/or thebattery1332. Theprocessing circuit1302 has aprocessor1304, amemory1306, and atimer1320. Theprocessing circuit1302 may include a general-purpose processor, an ASIC, one or more FPGAs, a DSP, circuits containing one or more processing components, circuitry for supporting a microprocessor, a group of processing components, or other suitable electronic processing components. In some embodiments, theprocessor1304 is configured to execute computer code stored in thememory1306 to facilitate the activities described herein. Thememory1306 may be any volatile or non-volatile computer-readable storage medium capable of storing data or computer code relating to the activities described herein. According to an exemplary embodiment, thememory1306 includes computer code modules (e.g., executable code, object code, source code, script code, machine code, etc.) configured for execution by theprocessor1304. Thetimer1320 is configured to maintain a time value for thelocking system1300. For example, thetimer1320 may be the clock of theprocessor1304 or may be any other time keeping circuit of thelocking system1300. The time value maintained by thetimer1320 may be used in secured communications (e.g., in syncing time with theuser devices1900, in providing timestamps related to events for logging purposes, etc.).
• According to an exemplary embodiment, thefirst transceiver1322 is configured to facilitate wireless communication using a first communication protocol. By way of example, the first communication protocol may be a short-range communication protocol. In one embodiment, thefirst transceiver1322 includes Bluetooth components for establishing a Bluetooth connection with theuser devices1900, thewireless bridge1200, thecamera system1400, and/or thecontroller1500. In another embodiment, thefirst transceiver1322 includes a different type of components that facilitate a different type of short-range and/or wireless communication protocol (e.g., radiofrequency, RFID, ZigBee, Wi-Fi, NFC, etc.). In embodiments where thelocking system1300 includes thesecond transceiver1324, thesecond transceiver1324 is configured to facilitate wireless communication using a second communication protocol. In one embodiment, thesecond transceiver1324 includes wired or wireless (e.g., Wi-Fi) components for communicating with Internet connected devices (e.g., thecamera system1400, thecontroller1500, thewireless router1600, theuser devices1900, thedoor server1700, thecamera server1800, etc.). In another embodiment, thesecond transceiver1324 includes cellular components for communicating with thedoor server1700, thecamera server1800, and/or theuser devices1900 via a cellular network.
• In embodiments where thelocking system1300 includes thedoor connector1326, thedoor connector1326 is configured to selectively interface with thelocking system interface1132. In embodiments where thelocking system1300 does not include thedoor connector1326, thelocking system1300 may be hardwired within thedoor1102.
• Theuser interface1328 may include a display screen and/or one or more user input devices (e.g., touch screens, buttons, microphones, speakers, displays, a keypad, a directional pad, etc.) to allow a user to interact with thelocking system1300. By way of an example, theuser interface1328 may facilitate waking thelocking system1300 from a sleep mode. By way of another example, theuser interface1328 may facilitate manually entering an unlock combination.
• Thelock mechanism1330 may include one or more physical and/or electronic locking mechanisms (e.g., pins, shackles, dials, buttons, shafts, keyholes, motors, latches, deadbolts, etc.). In embodiments that include thebattery1332, thebattery1332 is configured to provide power to thelocking system1300 to facilitate the operation thereof (e.g., locking, unlocking, etc.). Thebattery1332 may be rechargeable and/or replaceable. Such a battery operatedlocking system1300 may therefore operate in the event of power loss to the building in which theelectronic door assembly1100 is installed. In embodiments that do not include thebattery1332, thelocking system1300 may couple to another power source to facilitate the operation thereof (e.g., theexternal power source1602, theinternal energy storage1604, etc.). In some embodiments, thelocking system1300 includes an input/output port (e.g., a USB port, a COM port, a networking port, etc.) that may be used to establish a physical connection to another device. For example, such a physical connection may be used by a manufacturer or installer to program or otherwise communicate with thelocking system1300.
• According to an exemplary embodiment, thememory1306 of thelocking system1300 includes various modules or circuits configured to make access control decisions. As shown inFIG. 15, thememory1306 of thelocking system1300 includes auser input circuit1308, anaccess control circuit1310, and abridge circuit1312. In some embodiments, thememory1306 does not include the bridge circuit1312 (e.g., in embodiments where theelectronic door assembly1100 includes thewireless bridge1200, in embodiments where thecamera system1400 or thecontroller1500 function as a wireless bridge, etc.).
• Theuser input circuit1308 is configured to receive inputs through theuser interface1328. By way of example, theuser input circuit1308 may receive an input to awaken thelocking system1300 from a sleep mode. By way of another example, theuser input circuit1308 may receive a manual access code to unlock or otherwise access thelocking system1300. By way of another example, theuser input circuit1308 may receive an encrypted user profile and/or an encrypted command from a respective user device1900 (e.g., directly, indirectly, etc.). By way of yet another example, theuser input circuit1308 may receive an updated or new device key from the door server1700 (e.g., through theuser device1900 and/or thewireless bridge1200, through thewireless router1600 and/or thewireless bridge1200, etc.).
• Theaccess control circuit1310 is configured to store a device identifier, a device key, and/or a manual access code for thelocking system1300. Theaccess control circuit1310 may be configured to broadcast the device identifier via the first transceiver1322 (e.g., in response to being awoken from a sleep mode, etc.). In response to the broadcast or in response to a user selecting theelectronic door assembly1100 associated with thelocking system1300 in an app, thelocking system1300 may receive an associated encrypted user profile from arespective user device1900 or thedoor server1700. Theaccess control circuit1310 is configured to decrypt the encrypted user profile using (i) the device key pre-stored thereon and/or (ii) a handshake nonce appended to the encrypted user profile (in embodiments where the handshake nonce is used) to obtain a user key from the decrypted user profile. In some embodiments, theaccess control circuit1310 is configured to generate and transmit a reply nonce to therespective user device1900 or thedoor server1700 via thefirst transceiver1322 or the second transceiver1324 (e.g., depending on the proximity of theuser device1900 to thelocking system1300, depending on whether thelocking system1300 only includes thefirst transceiver1322, etc.) in response to successfully decrypting the encrypted user profile.
• Theaccess control circuit1310 may receive an encrypted command from therespective user device1900 or the door server1700 (e.g., after successfully decrypting the encrypted user profile, etc.) via thefirst transceiver1322 or the second transceiver1324 (e.g., depending on the proximity of theuser device1900 to thelocking system1300, depending on whether thelocking system1300 only includes thefirst transceiver1322, etc.). Theaccess control circuit1310 is configured to decrypt the encrypted command using the user key obtained from the decrypted user profile. In some embodiments, theaccess control circuit1310 is configured to generate a modified reply nonce based on the reply nonce to decrypt the encrypted command along with the user key (in embodiments where theaccess control circuit1310 generates and transmits the reply nonce to theuser device1900 or thedoor server1700 and theuser device1900 or thedoor server1700 generates and encrypts the command with the user key and the modified reply nonce). Theaccess control circuit1310 is configured to initiate an action specified by the decrypted command (e.g., unlocking a physical locking component, implementing a firmware update, etc.) in response to successfully decrypting the encrypted command. A similar procedure may be performed between thewireless bridge1200 and theaccess control circuit1310 based on an encrypted bridge profile and encrypted command received from thewireless bridge1200, as described in more detail herein. Theaccess control circuit1310 is configured to initiate a communication session between thelocking system1300 and thewireless bridge1200 following such a successful procedure.
• According to an exemplary embodiment, theaccess control circuit1310 is configured to perform the decryption of the encrypted user profile and the encrypted command using a single decryption algorithm. By way of example, the decryption algorithm may be or include a Counter with Cipher Block Chaining-Message Authentication Code (“CCM”) algorithm as described in further detail inRecommendation for Block Cipher Modes of Operation: the CCM Mode for Authentication and Confidentialitypublished by the National Institute of Standards and Technology in May 2004 and authored by Morris Dworkin, which is incorporated herein by reference in its entirety.
• In some embodiments, the two key authentication scheme using the device key and the user key eliminates any need to pair (e.g., using Bluetooth pairing, etc.) thelocking system1300 to theuser devices1900 to create a secure communication session between thelocking system1300 and theuser devices1900. In such embodiments, thelocking system1300, therefore, does not store the user keys received from theuser devices1900 after a communication session between thelocking system1300 and theuser devices1900 ends (e.g., after implementing the command, due to the inability to decrypt the encrypted command, in response to a lack of receiving an encrypted command for a predefined period of time, etc.).
• It should be understood that the two key authentication scheme implemented by theaccess control circuit1310 described herein is not meant to be limiting, but is provided as an example of one possible way to provide secure communication between theuser devices1900 and thelocking system1300. In other embodiments, secure communication is otherwise established by theaccess control circuit1310 using a different authentication scheme such as an authentication scheme that employs digital signatures, challenge-response procedures, multi-factor authentication (e.g., two-factor authentication, user profile plus a biometric, a user profile plus a PIN, etc.), and/or still other suitable authentication schemes. In still other embodiments, thedoor server1700 performs the access control decision, which is then transmitted to thelocking system1300 through theuser device1900, through thewireless bridge1200/wireless router1600, or directly. In yet other embodiments, thecontroller1500 performs the access control decision, which is then transmitted to thelocking system1300 directly (e.g., via Bluetooth, through a wired connection, etc.) or indirectly (e.g., through thewireless bridge1200, through thewireless router1600, etc.).
• Thebridge circuit1312 is configured to convert a first wireless signal received by thefirst transceiver1322 in the first wireless communication protocol (e.g., BLE, cellular, etc.) to a second wireless signal in the second communication protocol (e.g., Wi-Fi, BLE, etc.) to be emitted by thesecond transceiver1324. Thebridge circuit1312 may be also configured to convert the second wireless signal received by thesecond transceiver1324 in the second wireless communication protocol to the first wireless signal in the first communication protocol to be emitted by thefirst transceiver1322. Accordingly, thelocking system1300 may function as a wireless bridge (e.g., thewireless bridge1200, etc.).
Camera System
• In general, thecamera system1400 is configured to acquire video data regarding an environment outside thedoor1102. The video data may be stored locally and/or remotely in thecamera server1800. As shown inFIG. 16, thecamera system1400 includes aprocessing circuit1402, afirst transceiver1422, asecond transceiver1424, adoor connector1426, acamera1428, asensor1430, and abattery1432. In some embodiments, thecamera system1400 does not include thesecond transceiver1424, thedoor connector1426, thesensor1430, and/or thebattery1432. Theprocessing circuit1402 has aprocessor1404, amemory1406, and atimer1420. Theprocessing circuit1402 may include a general-purpose processor, an ASIC, one or more FPGAs, a DSP, circuits containing one or more processing components, circuitry for supporting a microprocessor, a group of processing components, or other suitable electronic processing components. In some embodiments, theprocessor1404 is configured to execute computer code stored in thememory1406 to facilitate the activities described herein. Thememory1406 may be any volatile or non-volatile computer-readable storage medium capable of storing data or computer code relating to the activities described herein. According to an exemplary embodiment, thememory1406 includes computer code modules (e.g., executable code, object code, source code, script code, machine code, etc.) configured for execution by theprocessor1404. Thetimer1420 is configured to maintain a time value for thecamera system1400. For example, thetimer1420 may be the clock of theprocessor1404 or may be any other time keeping circuit of thecamera system1400. The time value maintained by thetimer1420 may be used in time stamping the video data acquired by thecamera system1400.
• According to an exemplary embodiment, thefirst transceiver1422 is configured to facilitate wireless communication using a first communication protocol. In one embodiment, thefirst transceiver1422 includes wired or wireless (e.g., Wi-Fi) components for communicating with Internet connected devices (e.g., thecontroller1500, thewireless router1600, theuser devices1900, thedoor server1700, thecamera server1800, etc.). In another embodiment, thefirst transceiver1422 includes cellular components for communicating with thedoor server1700, thecamera server1800, and/or theuser devices1900 via a cellular network. In embodiments where thecamera system1400 includes thesecond transceiver1424, thesecond transceiver1424 is configured to facilitate wireless communication using a second communication protocol. By way of example, the second communication protocol may be a short-range communication protocol. In one embodiment, thesecond transceiver1424 includes Bluetooth components for establishing a Bluetooth connection with theuser devices1900, thewireless bridge1200, thecamera system1400, and/or thecontroller1500. In another embodiment, thesecond transceiver1424 includes a different type of components that facilitate a different type of short-range and/or wireless communication protocol (e.g., radiofrequency, RFID, ZigBee, Wi-Fi, NFC, etc.).
• In embodiments where thecamera system1400 includes thedoor connector1426, thedoor connector1426 is configured to selectively interface with thecamera system interface1142. In embodiments where thecamera system1400 does not include thedoor connector1426, thecamera system1400 may be hardwired within thedoor1102. Thecamera1428 is a camera device configured to capture the video data. Thesensor1430 may be or include a proximity sensor, a motion sensor, a door bell sensor, and/or still another suitable sensor configured to detect activity outside of or proximate thedoor1102. In embodiments that include thebattery1432, thebattery1432 is configured to provide power to thecamera system1400 to facilitate the operation thereof (e.g., sense activity, activate thecamera1428, etc.). Thebattery1432 may be rechargeable and/or replaceable. Such a battery operatedcamera system1400 may therefore operate in the event of power loss to the building in which theelectronic door assembly1100 is installed. In embodiments that do not include thebattery1432, thecamera system1400 may couple to another power source to facilitate the operation thereof (e.g., theexternal power source1602, theinternal energy storage1604, etc.).
• As shown inFIG. 16, thememory1406 of thecamera system1400 includes arecording circuit1408, asensor circuit1410, and abridge circuit1412. In some embodiments, thememory1406 does not include the sensor circuit1410 (e.g., in embodiments where thecamera system1400 does not include thesensor1430, etc.) and/or the bridge circuit1412 (e.g., in embodiments where theelectronic door assembly1100 includes thewireless bridge1200, in embodiments where thelocking system1300 or thecontroller1500 function as a wireless bridge, etc.).
• Therecording circuit1408 is configured to control operation of thecamera1428 and control transmission of the video data acquired by thecamera1428 to thecamera server1800. Therecording circuit1408 may transmit the video data upon request, periodically according to a preselected or defined transmission interval, or continuously. Thesensor circuit1410 is configured to receive sensor signals from thesensor1430 and activate thecamera1428 in response to the sensor signals indicating activity at or proximate thedoor1102. In other embodiments (e.g., without thesensor1430, etc.), thecamera1428 may be continuously active or active during preset time periods.
• Thebridge circuit1412 is configured to convert a first wireless signal received by thefirst transceiver1422 in the first wireless communication protocol (e.g., Wi-Fi, cellular, etc.) to a second wireless signal in the second communication protocol (e.g., BLE, Wi-Fi, etc.) to be emitted by thesecond transceiver1424. Thebridge circuit1412 may be also configured to convert the second wireless signal received by thesecond transceiver1424 in the second wireless communication protocol to the first wireless signal in the first communication protocol to be emitted by thefirst transceiver1422. Accordingly, thecamera system1400 may function as a wireless bridge (e.g., thewireless bridge1200, etc.).
Controller
• In general, thecontroller1500 is configured to facilitate controlling operation of one or more components of theelectronic door assembly1100 based on a command received thereby. Thecontroller1500 may receive the command from theswitch1606, directly from theuser device1900, and/or indirectly from theuser device1900 through thedoor server1700, thewireless router1600, and/or thewireless bridge1200. In some embodiments, thecontroller1500 is configured to receive an encrypted user profile from arespective user device1900 or the door server1700 (e.g., directly, indirectly through thewireless bridge1200, indirectly through thewireless router1600, etc.) and make an access and/or a management control decision based on the encrypted user profile (e.g., whether to permit unlocking, updating, activation, etc. by the respective user device1900). In some embodiments (e.g., embodiments where theelectronic door assembly1100 does not include thecontroller1500, etc.), the functions of thecontroller1500 described herein may be performed by thelocking system1300. In some embodiments, the functions of thelocking system1300 described herein may be performed by thecontroller1500. In some embodiments, operation of thecontroller1500 is independent of the locking system1300 (e.g., thecontroller1500 and thelocking system1300 perform independent authentication processes, etc.).
• As shown inFIG. 17, thecontroller1500 includes aprocessing circuit1502, afirst transceiver1522, asecond transceiver1524, adoor connector1526, awindow interface1528, alight interface1530, aswitch interface1532, and abattery1534. In some embodiments, thecontroller1500 does not include thefirst transceiver1522, thesecond transceiver1524, thedoor connector1526, thewindow interface1528, thelight interface1530, theswitch interface1532, and/or thebattery1534. Theprocessing circuit1502 has aprocessor1504, amemory1506, and atimer1520. Theprocessing circuit1502 may include a general-purpose processor, an ASIC, one or more FPGAs, a DSP, circuits containing one or more processing components, circuitry for supporting a microprocessor, a group of processing components, or other suitable electronic processing components. In some embodiments, theprocessor1504 is configured to execute computer code stored in thememory1506 to facilitate the activities described herein. Thememory1506 may be any volatile or non-volatile computer-readable storage medium capable of storing data or computer code relating to the activities described herein. According to an exemplary embodiment, thememory1506 includes computer code modules (e.g., executable code, object code, source code, script code, machine code, etc.) configured for execution by theprocessor1504. Thetimer1520 is configured to maintain a time value for thecontroller1500. For example, thetimer1520 may be the clock of theprocessor1504 or may be any other time keeping circuit of thecontroller1500. The time value maintained by thetimer1520 may be used in secured communications (e.g., in syncing time with theuser devices1900, in providing timestamps related to events for logging purposes, etc.).
• In embodiments where thecontroller1500 includes thefirst transceiver1522, thefirst transceiver1522 is configured to facilitate wireless communication using a first communication protocol. By way of example, the first communication protocol may be a short-range communication protocol. In one embodiment, thefirst transceiver1522 includes Bluetooth components for establishing a Bluetooth connection with theuser devices1900, thewireless bridge1200, thecamera system1400, and/or thelocking system1300. In another embodiment, thefirst transceiver1522 includes a different type of components that facilitate a different type of short-range and/or wireless communication protocol (e.g., radiofrequency, RFID, ZigBee, Wi-Fi, NFC, etc.). In embodiments where thecontroller1500 includes thesecond transceiver1524, thesecond transceiver1524 is configured to facilitate wireless communication using a second communication protocol. In one embodiment, thesecond transceiver1524 includes wired or wireless (e.g., Wi-Fi) components for communicating with Internet connected devices (e.g., thecamera system1400, thelocking system1300, thewireless router1600, theuser devices1900, thedoor server1700, thecamera server1800, etc.). In another embodiment, thesecond transceiver1524 includes cellular components for communicating with thedoor server1700, thecamera server1800, and/or theuser devices1900 via a cellular network.
• In embodiments where thecontroller1500 includes thedoor connector1526, thedoor connector1526 is configured to selectively interface with thecontroller interface1172. In embodiments where thecontroller1500 does not include thedoor connector1526, thecontroller1500 may be hardwired within thedoor1102 or separate from thedoor1102. In embodiments where thecontroller1500 includes the window interface1528 (e.g., when thedoor1102 includes thewindow1112, thewindows1118, etc.), thewindow interface1528 is configured to connect thecontroller1500 to thewindow1112 and/or thewindows1118 to facilitate providing commands to theblocker1114 and theblockers1120, respectively. In embodiments where thecontroller1500 includes the light interface1530 (e.g., when thedoor1102 includes thelighting system1122, etc.), thelight interface1530 is configured to connect thecontroller1500 to thelighting system1122 to facilitate providing commands to thelights1124. In embodiments where thecontroller1500 includes the switch interface1532 (e.g., when theelectronic door assembly1100 includes theswitch1606, etc.), theswitch interface1532 is configured to connect thecontroller1500 to theswitch1606 to facilitate user control of theblocker1114, theblockers1120, and/or thelights1124 with theswitch1606.
• In embodiments where thecontroller1500 includes thebattery1534, thebattery1534 is configured to provide power to thecontroller1500 to facilitate the operation thereof (e.g., receiving commands, providing commands, etc.). Thebattery1534 may be rechargeable and/or replaceable. Such a battery operatedcontroller1500 may therefore operate in the event of power loss to the building in which theelectronic door assembly1100 is installed. In embodiments that do not include thebattery1534, thecontroller1500 may couple to another power source to facilitate the operation thereof (e.g., theexternal power source1602, theinternal energy storage1604, etc.). In some embodiments, thecontroller1500 includes an input/output port (e.g., a USB port, a COM port, a networking port, etc.) that may be used to establish a physical connection to another device. For example, such a physical connection may be used by a manufacturer or installer to program or otherwise communicate with thecontroller1500.
• According to an exemplary embodiment, thememory1506 of thecontroller1500 includes various modules or circuits configured to facilitate controlling operation of one or more components of theelectronic door assembly1100. As shown inFIG. 17, thememory1506 of thecontroller1500 includes auser input circuit1508, anaccess control circuit1510, and abridge circuit1512. In some embodiments, thememory1506 does not include the access control circuit1510 (e.g., in embodiments where thecontroller1500 does not perform authentication procedures, etc.) and/or the bridge circuit1512 (e.g., in embodiments where theelectronic door assembly1100 includes thewireless bridge1200, in embodiments where thecamera system1400 or thelocking system1300 function as a wireless bridge, etc.).
• Theuser input circuit1508 is configured to receive inputs from theswitch1606, the user devices1900 (e.g., directly, indirectly, etc.), thedoor server1700, and/or thecamera server1800. By way of example, theuser input circuit1508 may receive an encrypted user profile and/or an encrypted command from arespective user device1900 or the door server1700 (e.g., directly, indirectly, etc.). By way of another example, theuser input circuit1508 may receive a first input from theswitch1606 to activate/deactivate theblocker1114 and/or theblockers1120 and/or receive a second input from theswitch1606 to turn on/turn off thelights1124. By way of yet another example, theuser input circuit1508 may receive an updated or new device key from the door server1700 (e.g., through theuser device1900 and/or thewireless bridge1200, through thewireless router1600 and/or thewireless bridge1200, etc.).
• Theaccess control circuit1510 is configured to store a device identifier and/or a device key. Theaccess control circuit1510 may be configured to broadcast the device identifier via thefirst transceiver1522. In response to the broadcast or in response to a user selecting theelectronic door assembly1100 associated with thecontroller1500 in an app, thecontroller1500 may receive an associated encrypted user profile from arespective user device1900 or thedoor server1700. Theaccess control circuit1510 is configured to decrypt the encrypted user profile using (i) the device key pre-stored thereon and/or (ii) a handshake nonce appended to the encrypted user profile (in embodiments where the handshake nonce is used) to obtain a user key from the decrypted user profile. In some embodiments, theaccess control circuit1510 is configured to generate and transmit a reply nonce to therespective user device1900 or the door sever1700 via thefirst transceiver1522 or the second transceiver1524 (e.g., depending on the proximity of theuser device1900 to thecontroller1500, depending on whether thecontroller1500 only includes thefirst transceiver1522, etc.) in response to successfully decrypting the encrypted user profile.
• Theaccess control circuit1510 may receive an encrypted command from therespective user device1900 or the door server1700 (e.g., after successfully decrypting the encrypted user profile, etc.) via thefirst transceiver1522 or the second transceiver1524 (e.g., depending on the proximity of theuser device1900 to thecontroller1500, depending on whether thecontroller1500 only includes thefirst transceiver1522, etc.). Theaccess control circuit1510 is configured to decrypt the encrypted command using the user key obtained from the decrypted user profile. In some embodiments, theaccess control circuit1510 is configured to generate a modified reply nonce based on the reply nonce to decrypt the encrypted command along with the user key (in embodiments where theaccess control circuit1510 generates and transmits the reply nonce to theuser device1900 and theuser device1900 generates and encrypts the command with the user key and the modified reply nonce). Theaccess control circuit1510 is configured to initiate an action specified by the decrypted command (e.g., unlocking a physical locking component, implementing a firmware update, turn on/off lights, activating/deactivating blockers, etc.) in response to successfully decrypting the encrypted command. A similar procedure may be performed between thewireless bridge1200 and theaccess control circuit1510 based on an encrypted bridge profile and encrypted command received from thewireless bridge1200, as described in more detail herein. Theaccess control circuit1510 is configured to initiate a communication session between thecontroller1500 and thewireless bridge1200 following such a successful procedure.
• According to an exemplary embodiment, theaccess control circuit1510 is configured to perform the decryption of the encrypted user profile and the encrypted command using a single decryption algorithm. By way of example, the decryption algorithm may be or include a Counter with Cipher Block Chaining-Message Authentication Code (“CCM”) algorithm as described in further detail inRecommendation for Block Cipher Modes of Operation: the CCM Mode for Authentication and Confidentialitypublished by the National Institute of Standards and Technology in May 2004 and authored by Morris Dworkin.
• In some embodiments, the two key authentication scheme using the device key and the user key eliminates any need to pair (e.g., using Bluetooth pairing, etc.) thecontroller1500 to theuser devices1900 to create a secure communication session between thecontroller1500 and theuser devices1900. In such embodiments, thecontroller1500, therefore, does not store the user keys received from theuser devices1900 after a communication session between thecontroller1500 and theuser devices1900 ends (e.g., after implementing the command, due to the inability to decrypt the encrypted command, in response to a lack of receiving an encrypted command for a predefined period of time, etc.).
• It should be understood that the two key authentication scheme implemented by theaccess control circuit1510 described herein is not meant to be limiting, but is provided as an example of one possible way to provide secure communication between theuser devices1900 and thecontroller1500. In other embodiments, secure communication is otherwise established by theaccess control circuit1510 using a different authentication scheme such as an authentication scheme that employs digital signatures, challenge-response procedures, multi-factor authentication (e.g., two-factor authentication, user profile plus a biometric, a user profile plus a PIN, etc.), and/or still other suitable authentication schemes. In still other embodiments, thedoor server1700 performs the control decisions, which is then transmitted to thecontroller1500 through theuser device1900, through thewireless bridge1200/wireless router1600, or directly. In yet other embodiments, thelocking system1300 performs the control decisions, which are then transmitted to thecontroller1500 directly (e.g., via Bluetooth, through a wired connection, etc.) or indirectly (e.g., through thewireless bridge1200, through thewireless router1600, etc.). While the authentication scheme implemented by thecontroller1500 and thelocking system1300 are disclosed herein to be the same, in other embodiments, (i) thecontroller1500 and thelocking system1300 implement different authentication schemes or (ii) authentication to one of thecontroller1500 or thelocking system1300 automatically grants access to the other (i.e., both don't have to run independent authentication schemes).
• Thebridge circuit1512 is configured to convert a first wireless signal received by thefirst transceiver1522 in the first wireless communication protocol (e.g., BLE, cellular, etc.) to a second wireless signal in the second communication protocol (e.g., Wi-Fi, BLE, etc.) to be emitted by thesecond transceiver1524. Thebridge circuit1512 may be also configured to convert the second wireless signal received by thesecond transceiver1524 in the second wireless communication protocol to the first wireless signal in the first communication protocol to be emitted by thefirst transceiver1522. Accordingly, thecontroller1500 may function as a wireless bridge (e.g., thewireless bridge1200, etc.).
• In some embodiments (e.g., where thecontroller1500 is Wi-Fi capable, cellular capable, etc.), thecontroller1500 is configured to discover electronics coupled to thedoor1102 and automatically register the components to thedoor server1700. By way of example, thecontroller1500 may detect that alocking system1300 is installed in the door1102 (e.g., thedoor connector1326 is inserted into thelocking system interface1132, etc.). Thecontroller1500 may then pull data from thelocking system1300 and transmit that data to thedoor server1700, which may subsequently link thelocking system1300 with the user profiles associated with therespective door1102. Accordingly, when user profiles are transmitted to theuser devices1900 associated with therespective door1102 by thedoor server1700, the user profiles may include the data necessary to access the locking system1300 (e.g., without any user interaction necessary to link thelocking system1300 to thedoor1102 and/or theiruser devices1900, etc.).
• Door Server
• As shown inFIG. 18, thedoor server1700 includes aprocessing circuit1702 and anetwork interface1720. Theprocessing circuit1702 has aprocessor1704 and amemory1706. Theprocessing circuit1702 may include a general-purpose processor, an application specific integrated circuit (“ASIC”), one or more field programmable gate arrays (“FPGAs”), a digital-signal-processor (“DSP”), circuits containing one or more processing components, circuitry for supporting a microprocessor, a group of processing components, or other suitable electronic processing components. In some embodiments, theprocessor1704 is configured to execute computer code stored in thememory1706 to facilitate the activities described herein. Thememory1706 may be any volatile or non-volatile computer-readable storage medium capable of storing data or computer code relating to the activities described herein. According to an exemplary embodiment, thememory1706 includes computer code modules (e.g., executable code, object code, source code, script code, machine code, etc.) configured for execution by theprocessor1704.
• According to an exemplary embodiment, thenetwork interface1720 is configured to facilitate wireless communication from and to the door server1700 (i) directly to and from thecamera server1800, (ii) directly to and from theuser devices1900, (iii) directly to and from at least one of the components of theelectronic door assembly1100, (iv) indirectly to and from at least one of the components of theelectronic door assembly1100 through theuser devices1900 and/or thewireless bridge1200, (v) indirectly to and from at least one of the components of theelectronic door assembly1100 through thewireless router1600 and/or thewireless bridge1200, and/or (vi) indirectly to and from at least one of the components of theelectronic door assembly1100 through theuser devices1900 and/or thewireless router1600.
• According to an exemplary embodiment, thememory1706 of thedoor server1700 includes various modules or circuits configured to (i) generate and securely store the device keys, the user keys, the bridge keys, the user profiles, and the bridge profiles and (ii) selectively and/or dynamically deliver encrypted user profiles and/or encrypted bridge profiles (e.g., each including an associated user key, bridge key, etc.) to theuser devices1900 and/or thewireless bridges1200 based on one or more factors such as, for example, the location of theuser devices1900, the permissions of the users (e.g., clearance/authorization level, time schedule, etc.) of theuser devices1900, and/or still other possible factors.
• As shown inFIG. 18, thememory1706 of thedoor server1700 includes a devicekey circuit1708, auser key circuit1710, anonce circuit1712, auser profile circuit1714, and acamera circuit1716. In some embodiments, thememory1706 does not include thenonce circuit1712 and/or thecamera circuit1716. Further, the type of modules or circuits within thememory1706 may vary depending on the authentication scheme utilized. By way of example, when the two-key authentication protocol described herein is used, thedoor server1700 may include the devicekey circuit1708, theuser key circuit1710, thenonce circuit1712, and/or theuser profile circuit1714. By way of another example, when a different authentication protocol is used, thedoor server1700 may include various other types of modules or circuits to perform such authentication protocols.
• The devicekey circuit1708 is configured to generate and securely store the device keys (e.g., which may be provided to thelocking system1300 and/or thecontroller1500 at the time of manufacturing, etc.). As an example, the devicekey circuit1708 may correspond to a first database of keys and may include the software configured to store and retrieve such keys from the first database. The devicekey circuit1708 may be further configured to facilitate updating, replacing, or deleting the device keys (e.g., if a respective device key on arespective locking system1300 and/orcontroller1500 is compromised, etc.), which may be propagated to the associatedlocking system1300 and/orcontroller1500 using the methods described herein (e.g., directly, indirectly, etc.).
• Theuser key circuit1710 is configured to generate and securely store the user keys (e.g., when a user is registered to arespective locking system1300,controller1500, etc.). As an example, theuser key circuit1710 may correspond to a second database of keys and may include the software configured to store and retrieve such keys from the second database. Theuser key circuit1710 may be further configured to facilitate updating, replacing, or deleting the user keys (e.g., if a user's access is revoked, if a user key expires, etc.), which may be updated in the associated user profile as necessary. While not shown, thedoor server1700 may also include a bridge key circuit. The bridge key circuit may be configured to generate and securely store bridge keys. As an example, the bridge key circuit may correspond to a third database of keys and may include the software configured to store and retrieve such keys from the third database.
• Thenonce circuit1712 is configured to generate a handshake nonce for each of the user profiles each time the user profiles are transmitted to theuser devices1900. In some embodiments, the handshake nonce is not used. In some embodiments, thenonce circuit1712 is configured to generate a handshake nonce for each of the bridge profiles each time the bridge profiles are transmitted to the wireless bridges1200.
• Theuser profile circuit1714 is configured to generate and securely store the user profiles. As an example, theuser profile circuit1714 may correspond to a fourth database of user profiles and may include the software configured to store and retrieve such user profiles from the fourth database. Theuser profile circuit1714 may be further configured to facilitate updating, replacing, or deleting the user profiles. By way of example, theuser profile circuit1714 may be configured to generate a user profile for a specific user,locking system1300, and/orcontroller1500 when a new user is added to arespective locking system1300, added to arespective controller1500, in response to a respective user profile expiring, etc. Theuser profile circuit1714 is further configured to encrypt the user profiles prior to or as they are being transmitted to theuser devices1900. By way of example, when a user profile is transmitted to arespective user device1900, theuser profile circuit1714 may be configured to (i) insert the associated user key into or append the associated user key to the user profile, (ii) encrypt the user profile and user key using (a) the device key associated with aspecific locking system1300 and/orcontroller1500 and/or (b) the handshake nonce (in embodiments where the handshake nonce is used) to generate an encrypted user profile, and/or (iii) append (a) the user key and/or (b) the handshake nonce (in embodiments where the handshake nonce is used) to the encrypted user profile. The user profile circuit114 may be further configured to facilitate updating, replacing, or deleting the user profiles (e.g., if a user's access is revoked, if a user key is updated, etc.).
• While not shown, thedoor server1700 may also include a bridge profile circuit. The bridge profile circuit is configured to generate and securely store the bridge profiles. As an example, the bridge profile circuit may correspond to a fifth database of bridge profiles and may include the software configured to store and retrieve such bridge profiles from the fifth database. The bridge profile circuit may be further configured to facilitate updating, replacing, or deleting the bridge profiles. The bridge profile circuit is further configured to encrypt the bridge profiles prior to or as they are being transmitted to the wireless bridges1200. By way of example, when a bridge profile is transmitted to a respective wireless bridge, the bridge profile circuit may be configured to (i) insert the associated bridge key into or append the associated bridge key to the user profile, (ii) encrypt the bridge profile and bridge key using (a) the device key associated with a specific door component or device (e.g., thelocking system1300, thecamera system1400, thecontroller1500, etc.) and/or (b) the handshake nonce (in embodiments where the handshake nonce is used) to generate an encrypted bridge profile, and/or (iii) append (a) the bridge key and/or (b) the handshake nonce (in embodiments where the handshake nonce is used) to the encrypted bridge profile.
• Thecamera circuit1716 is configured to access thecamera server1800 to facilitate accessing thecamera server1800 with theuser devices1900. By way of example, in some implementations, theuser devices1900 may not be able to access thecamera server1800 directly. Instead, theuser devices1900 may request to access thecamera server1800 through an app stored on theuser devices1900, which will cause a request to be sent to thecamera circuit1716, which will subsequently contact thecamera server1800. If thecamera server1800 approves the access request, thecamera circuit1716 may relay pre-stored video, a live video stream, and/or provide other control functionality to theuser devices1900.
Camera Server
• As shown inFIG. 19, thecamera server1800 includes aprocessing circuit1802 and anetwork interface1820. Theprocessing circuit1802 has aprocessor1804 and amemory1806. Theprocessing circuit1802 may include a general-purpose processor, an application specific integrated circuit (“ASIC”), one or more field programmable gate arrays (“FPGAs”), a digital-signal-processor (“DSP”), circuits containing one or more processing components, circuitry for supporting a microprocessor, a group of processing components, or other suitable electronic processing components. In some embodiments, theprocessor1804 is configured to execute computer code stored in thememory1806 to facilitate the activities described herein. Thememory1806 may be any volatile or non-volatile computer-readable storage medium capable of storing data or computer code relating to the activities described herein. According to an exemplary embodiment, thememory1806 includes computer code modules (e.g., executable code, object code, source code, script code, machine code, etc.) configured for execution by theprocessor1804.
• According to an exemplary embodiment, thenetwork interface1820 is configured to facilitate wireless communication from and to the camera server1800 (i) directly to and from thedoor server1700, (ii) directly to and from theuser devices1900, (iii) directly to and from thecamera system1400, (iv) indirectly to and from theuser devices1900, (v) indirectly to and from thecamera system1400 through theuser devices1900 and/or thewireless bridge1200, (vi) indirectly to and from thecamera system1400 through thewireless router1600 and/or thewireless bridge1200, and/or (vii) indirectly to and from thecamera system1400 through theuser devices1900 and/or thewireless router1600.
• According to an exemplary embodiment, thememory1806 of thecamera server1800 includes various modules or circuits configured to receive, store, and transmit video data acquired by thecamera system1400 to theuser devices1900. As shown inFIG. 19, thememory1806 of thecamera server1800 includes anaccess circuit1808 and acamera circuit1810. Thecamera circuit1810 is configured to receive and store video data acquired by thecamera system1400. Theaccess circuit1808 is configured to determine whether arespective user device1900 is permitted to access the camera data stored in thecamera circuit1810. According to an exemplary embodiment, a user is able to link acamera system1400 to their user profile (e.g., at the time of installing thecamera system1400 in thedoor1102, etc.). Accordingly, when the user attempts to access the video data (e.g., through thecamera circuit1716 of thedoor server1700, etc.), theaccess circuit1808 is configured to determine if the user profile on theuser device1900 attempting to access the camera data is associated with thecamera system1400 that acquired the video data. If so, theaccess circuit1808 is configured to transmit the video data to theuser device1900 for viewing (e.g., directly, through thecamera circuit1716 of thedoor server1700, etc.). In some embodiments, theuser devices1900 can access a live video feed directly from thecamera system1400 without having to go through thecamera server1800. In such embodiments, thecamera system1400 may be configured to implement a similar authentication scheme described herein in relation to thelocking system1300 and thecontroller1500.
User Device
• In general, theuser device1900 is configured to selectively receive and store an encrypted user profile from thedoor server1700 to facilitate accessing and/or at least partially managing the operation of one or more components of theelectronic door assembly1100 to which theuser device1900 has access. By way of example, theuser device1900 may be used to unlock, lock, and/or otherwise manage the function of the locking system1300 (e.g., change settings, update firmware, etc. directly through thelocking system1300 or indirectly through the controller1500). By way of another example, theuser device1900 may be used to activate, deactivate, and/or otherwise manage the function of thelighting system1122, thewindow1112, and/or the windows1118 (e.g., through thecontroller1500, through thelocking system1300, etc.). By way of yet another example, theuser device1900 may be used to (i) activate and deactivate thecamera system1400 and/or (ii) view live and/or pre-recorded video captured by thecamera system1400. Theuser device1900 may access, control, and/or manage various components of theelectronic door system1000 through the use of an application (“app”) that is configured to run on theuser device1900. For example, the app may be installed on a mobile phone or other portable device, and the app may be used to configure, control, and/or communicate with thewireless bridge1200, thelocking system1300, thecamera system1400, thecontroller1500, thewireless router1600, thedoor server1700, and/or thecamera server1800 over a wireless connection. In some embodiments, theuser device1900 is a portable device such as a smartphone, a cell phone, a mobile phone, a tablet, a smart watch, a laptop computer, and/or another type of suitable portable device. In another embodiment, theuser device1900 is a desktop computer (e.g., connected to theelectronic door assembly1100 via a wired connection, remote from theelectronic door assembly1100, etc.).
• As shown inFIG. 20, theuser device1900 includes aprocessing circuit1902, afirst transceiver1922, asecond transceiver1924, athird transceiver1926, and auser interface1928. Theprocessing circuit1902 has aprocessor1904, amemory1906, and atimer1920. Theprocessing circuit1902 may include a general-purpose processor, an ASIC, one or more FPGAs, a DSP, circuits containing one or more processing components, circuitry for supporting a microprocessor, a group of processing components, or other suitable electronic processing components. In some embodiments, theprocessor1904 is configured to execute computer code stored in thememory1906 to facilitate the activities described herein. Thememory1906 may be any volatile or non-volatile computer-readable storage medium capable of storing data or computer code relating to the activities described herein. According to an exemplary embodiment, thememory1906 includes computer code modules (e.g., executable code, object code, source code, script code, machine code, etc.) configured for execution by theprocessor1904. Thetimer1920 is configured to maintain a time value for theuser device1900. For example, thetimer1920 may be the clock of theprocessor1904 or may be any other time keeping circuit of theuser device1900. The time value maintained by thetimer1920 may be used in secured communications (e.g., in syncing time with thelocking system1300, in providing timestamps related to events for logging purposes, etc.).
• According to an exemplary embodiment, (i) thefirst transceiver1922 is configured to facilitate communicating with one or more of the components of theelectronic door system1000 using a first communication protocol, (ii) thesecond transceiver1924 is configured to facilitate communicating with one or more of the components of theelectronic door system1000 using a second communication protocol, and (iii) thethird transceiver1926 is configured to facilitate communicating with one or more of the components of theelectronic door system1000 using a third communication protocol. By way of example, (i) at least one of the first communication protocol, the second communication protocol, or the third communication protocol may be a long-range communication protocol and (ii) at least one of the first communication protocol, the second communication protocol, or the third communication protocol may be a short-range communication protocol. In one embodiment, thefirst transceiver1922 includes cellular components for communicating with (i) thedoor server1700 and/or thecamera server1800 via a cellular network and/or (ii) theelectronic door assembly1100 through thedoor server1700 and/or thecamera server1800. In some embodiments, the cellular components facilitate communicating directly with components of theelectronic door assembly1100 directly (e.g., without thedoor server1700, thecamera server1800, thewireless router1600, thewireless bridge1200, etc. functioning as an intermediary; one or more components of theelectronic door assembly1100 include cellular components; etc.). In one embodiment, thesecond transceiver1924 includes wireless (e.g., Wi-Fi, etc.) components for communicating with (i) thedoor server1700 and/or thecamera server1800 over the Internet or other network, (ii) one or more components of theelectronic door assembly1100 directly (e.g., when in Wi-Fi range, etc.), and/or (iii) one or more components of theelectronic door assembly1100 indirectly through thewireless bridge1200,wireless router1600, thedoor server1700, and/or the camera server1800 (e.g., when connected to an internet connection, etc.). In one embodiment, thethird transceiver1926 includes Bluetooth components for establishing a Bluetooth connection with (i) one or more components of theelectronic door assembly1100 directly (e.g., when in range of Bluetooth compatible components of theelectronic door assembly1100, etc.) and/or (ii) one or more components of theelectronic door assembly1100 indirectly through the wireless bridge1200 (e.g., when in Bluetooth range of thewireless bridge1200 and when attempting to communicate with non-Bluetooth compatible components of theelectronic door assembly1100, etc.). In another embodiment, thethird transceiver1926 includes a different type of components that facilitate a different type of short-range and/or wireless communication protocol (e.g., radiofrequency, RFID, ZigBee, NFC, etc.). In some embodiments, theuser device1900 does not include one or more of thefirst transceiver1922, thesecond transceiver1924, and thethird transceiver1926.
• Theuser interface1928 may include a display screen and/or one or more user input devices (e.g., touch screens, buttons, microphones, speakers, displays, keyboards, stylus inputs, mice, track pads, etc.) to allow a user to interact with theuser device1900, thelocking system1300, thecamera system1400, thecontroller1500, thedoor server1700, thecamera server1800, and/or any apps running on theuser device1900.
• According to an exemplary embodiment, thememory1906 of theuser device1900 includes various modules or circuits configured to receive, manage, and transmit the encrypted user profiles and/or the encrypted commands. As shown inFIG. 20, thememory1906 of theuser device1900 includes anapplication circuit1908 having aprofile management circuit1910, auser input circuit1912, adoor system circuit1914, and a command circuit1918.
• Theprofile management circuit1910 is configured to receive and store the encrypted user profiles and user keys sent to thefirst transceiver1922 and/or thesecond transceiver1924 of theuser device1900 by thedoor server1700. Theuser input circuit1912 is configured to (i) provide various graphical user interfaces on a display of theuser interface1928 and (ii) receive inputs provided to theuser interface1928 by the user and perform functions associated therewith. Thedoor system circuit1914 is configured to identify a respectiveelectronic door assembly1100 that theuser device1900 is trying to access (e.g., based on an identifier broadcasted by arespective locking system1300, arespective controller1500, etc.; based on anelectronic door assembly1100 selected in the app on theuser device1900; etc.) and provide the corresponding encrypted user profile (e.g., without the appended user key, with the handshake nonce appended, etc.) stored in theprofile management circuit1910 to thefirst transceiver1922, thesecond transceiver1924, and/or the third transceiver1926 (depending on the current connections available and the proximity of theuser device1900 to the electronic door assembly1100) to deliver the encrypted user profile to the respectiveelectronic door assembly1100 to facilitate controlling various functions of the respective electronic door assembly1100 (e.g., unlock, lock, change settings, update firmware, turn on lights, activate blockers, etc.).
• Thecommand circuit1916 is configured to generate and transmit an encrypted command to the respectiveelectronic door assembly1100. The encrypted command may include a command for therespective locking system1300 to perform some action such as unlock, lock, change settings, update firmware, etc. The encrypted command may include a command for therespective controller1500 to perform some action such as unlock, lock, change settings, update firmware, turn on lights, turn off lights, activate blockers, deactivate blockers, activate camera, deactivate camera, etc. The encrypted command may include a command for therespective camera system1400 to activate, deactivate, provide a live feed, etc. According to an exemplary embodiment, the command is encrypted using the user key associated with the user profile that was transmitted to a component of the respectiveelectronic door assembly1100 at the start of the communication session. In some embodiments, thecommand circuit1916 is configured to generate a modified reply nonce based on a reply nonce received from the component of the respectiveelectronic door assembly1100 as described in more detail herein (e.g., in response to the component of the respectiveelectronic door assembly1100 successfully decrypting the encrypted user profile, etc.). In such embodiments, thecommand circuit1916 is configured to encrypt the command using both the user key and the modified reply nonce.
Communication Processes
• Referring now toFIGS. 21-25, various possible communication processes between components of theelectronic door system1000 are shown according to various exemplary embodiments. As shown inFIG. 21, afirst communication process2100 is shown according to an embodiment where a user device (e.g., theuser device1900, etc.) is within communication range (e.g., BLE, Wi-Fi, cellular, etc.) of a door device (e.g., thelocking system1300, thecamera system1400, thecontroller1500, etc.) such that the user device can communicate directly with the door device via a short-range communication protocol or a long-range communication protocol (e.g., without an intermediary device, etc.). At ACT1, a server (e.g., thedoor server1700, etc.) receives a request to add a user or the user device to a door system (e.g., thedoor system1000, etc.) including the door device. At ACT2, the server is configured to generate an encrypted user profile in response to the request. The server is configured to encrypt the user profile and a user key with a device key associated with the door device and a handshake nonce. The server is configured to append the user key associated with the user device and the handshake nonce to the encrypted user profile. At ACT3, the server is configured to transmit the encrypted user profile to the user device.
• At ACT4, the user device is configured to store the user key appended to the encrypted user profile. At ACT5, the user device is configured to transmit the encrypted user profile with the handshake nonce appended thereto to the door device. At ACT6, the door device is configured to decrypt the encrypted user profile with a pre-stored device key and the appended handshake nonce to obtain the user key from the decrypted user profile. At ACT7, the door device is configured to generate a reply nonce. At ACT5, the door device is configured to transmit the reply nonce to the user device.
• At ACT5, the user device is configured to generate a modified reply nonce based on the reply nonce received from the door device. At ACT10, the user device is configured to generate an encrypted command. The command is encrypted using the user key and the modified reply nonce. At ACT11, the user device is configured to transmit the encrypted command to the door device. At ACT12, the door device is configured to generate a modified reply nonce based on the reply nonce (i.e., independent of the user device). At ACT13, the door device is configured to decrypt the encrypted command using the user key obtained from the user profile and the modified reply nonce. The door device is then configured to perform an action specified by the decrypted command. It should be understood that, in some implementations, the handshake nonce, the reply nonce, and the modified reply nonce are omitted from thefirst communication process2100.
• As shown inFIG. 22, asecond communication process2200 is shown according to an embodiment where a user device (e.g., theuser device1900, etc.) is not within short-range communication (e.g., BLE, etc.) of a door device (e.g., thelocking system1300, thecamera system1400, thecontroller1500, etc.) but is within short-range communication (e.g., Wi-Fi, etc.) of an intermediary device (e.g., thewireless bridge1200, thewireless router1600, etc.) such that the user device can communicate with the door device via a short-range communication protocol through the intermediary device. At ACT1, the door device is configured to broadcast a device identifier (e.g., periodically, continuously, when awoken, etc.). At ACT2, a bridge (e.g., thewireless bridge1200, etc.) is configured to receive the device identifier and transmit a request for a bridge profile with the device identifier to a server (e.g., thedoor server1700, etc.) through a router (e.g., thewireless router1600, etc.).
• At ACT3, the server is configured to generate an encrypted bridge profile in response to the request and based on the device identifier. The server is configured to encrypt the bridge profile and a bridge key with a device key associated with the door device and a handshake nonce. The server is configured to append the bridge key associated with the bridge and the handshake nonce to the encrypted bridge profile. At ACT4, the server is configured to transmit the encrypted bridge profile to the bridge through the router.
• At ACT5, the bridge is configured to store the bridge key appended to the encrypted bridge profile. At ACT6, the bridge is configured to transmit the encrypted bridge profile with the handshake nonce appended thereto to the door device. At ACT7, the door device is configured to decrypt the encrypted bridge profile with a pre-stored device key and the appended handshake nonce to obtain the bridge key from the decrypted bridge profile. At ACT5, the door device is configured to generate a reply nonce. At ACT5, the door device is configured to transmit the reply nonce to the bridge.
• At ACT10, the bridge is configured to generate a modified reply nonce based on the reply nonce received from the door device. At ACT11, the bridge is configured to generate an encrypted command. The command is encrypted using the bridge key and the modified reply nonce. At ACT12, the bridge is configured to transmit the encrypted command to the door device. At ACT13, the door device is configured to generate a modified reply nonce based on the reply nonce (i.e., independent of the bridge). At ACT14, the door device is configured to decrypt the encrypted command using the bridge key obtained from the bridge profile and the modified reply nonce. The door device is then configured to perform an action specified by the decrypted command, in this instance, initiate a communication session between the bridge and the door device.
• At ACT15, the server receives a request to add a user or the user device to a door system (e.g., thedoor system1000, etc.) including the door device. ACT15 can come before, during, or after ACT1-ACT14. At ACT16, the server is configured to generate an encrypted user profile in response to the request. The server is configured to encrypt the user profile and a user key with a device key associated with the door device and a handshake nonce. The server is configured to append the user key associated with the user device and the handshake nonce to the encrypted user profile. At ACT17, the server is configured to transmit the encrypted user profile to the user device. In some embodiments, ACT17 includes transmitting the encrypted user profile to the user device through the router.
• At ACT18, the user device is configured to store the user key appended to the encrypted user profile. At ACT19, the user device is configured to transmit the encrypted user profile to the door device through the router and the bridge. At ACT20, the door device is configured to decrypt the encrypted user profile with the pre-stored device key and the appended handshake nonce to obtain the user key from the decrypted user profile. At ACT21, the door device is configured to generate a reply nonce. At ACT22, the door device is configured to transmit the reply nonce to the user device through the bridge and the router.
• At ACT23, the user device is configured to generate a modified reply nonce based on the reply nonce received from the door device. At ACT24, the user device is configured to generate an encrypted command. The command is encrypted using the user key and the modified reply nonce. At ACT25, the user device is configured to transmit the encrypted command to the door device through the router and the bridge. At ACT26, the door device is configured to generate a modified reply nonce based on the reply nonce (i.e., independent of the user device). At ACT27, the door device is configured to decrypt the encrypted command using the user key obtained from the user profile and the modified reply nonce. The door device is then configured to perform an action specified by the decrypted command.
• It should be understood that, in some implementations, the handshake nonce, the reply nonce, and the modified reply nonce are omitted from thesecond communication process2200. In some embodiments, the bridge does not perform ACT2 until the user device performs ACT19 (e.g., the bridge requests the bridge profile to establish communication with the door device after the user device requests access such that continuous communication with the door device is not necessary). In some embodiments, the bridge does not perform ACT6 until the user device performs ACT19 (e.g., the bridge establishes communication with the door device after the user device requests access such that continuous communication with the door device is not necessary, etc.). In some instances, ACT19, ACT22, and ACT25 are performed between the user device, the bridge, and the door device and not the router (e.g., when the user device is in range of the bridge, etc.).
• As shown inFIG. 23, athird communication process2300 is shown according to an embodiment where a user device (e.g., theuser device1900, etc.) is not within short-range communication (e.g., BLE, Wi-Fi, etc.) of a door device (e.g., thelocking system1300, thecamera system1400, thecontroller1500, etc.) or an intermediary device (e.g., thewireless bridge1200, thewireless router1600, etc.). At ACT1, the door device is configured to broadcast a device identifier (e.g., periodically, continuously, when awoken, etc.). At ACT2, a bridge (e.g., thewireless bridge1200, etc.) is configured to receive the device identifier and transmit a request for a bridge profile with the device identifier to a server (e.g., thedoor server1700, etc.) through a router (e.g., thewireless router1600, etc.).
• At ACT3, the server is configured to generate an encrypted bridge profile in response to the request and based on the device identifier. The server is configured to encrypt the bridge profile and a bridge key with a device key associated with the door device and a handshake nonce. The server is configured to append the bridge key associated with the bridge and the handshake nonce to the encrypted bridge profile. At ACT4, the server is configured to transmit the encrypted bridge profile to the bridge through the router.
• At ACT5, the bridge is configured to store the bridge key appended to the encrypted bridge profile. At ACT6, the bridge is configured to transmit the encrypted bridge profile with the handshake nonce appended thereto to the door device. At ACT7, the door device is configured to decrypt the encrypted bridge profile with a pre-stored device key and the appended handshake nonce to obtain the bridge key from the decrypted bridge profile. At ACT5, the door device is configured to generate a reply nonce. At ACT5, the door device is configured to transmit the reply nonce to the bridge.
• At ACT10, the bridge is configured to generate a modified reply nonce based on the reply nonce received from the door device. At ACT11, the bridge is configured to generate an encrypted command. The command is encrypted using the bridge key and the modified reply nonce. At ACT12, the bridge is configured to transmit the encrypted command to the door device. At ACT13, the door device is configured to generate a modified reply nonce based on the reply nonce (i.e., independent of the bridge). At ACT14, the door device is configured to decrypt the encrypted command using the bridge key obtained from the bridge profile and the modified reply nonce. The door device is then configured to perform an action specified by the decrypted command, in this instance, initiate a communication session between the bridge and the door device.
• At ACT15, the user device is configured to transmit an access request to the server to access the door device. In some embodiments (e.g., in instances where theuser device1900 is within short-range communication of thewireless router1600, etc.), ACT15 is replaced with ACT15A and ACT15B. At ACT15A, the user device is configured to transmit an access request to the router. At ACT15B, the router is configured to transmit the access request to the server. At ACT16, the server is configured to generate an encrypted user profile in response to the request. The server is configured to encrypt the user profile and a user key with the device key associated with the door device and a handshake nonce. The server is configured to append the handshake nonce to the encrypted user profile. At ACT17, the server is configured to transmit the encrypted user profile to the door device through the router and the bridge.
• At ACT18, the door device is configured to decrypt the encrypted user profile with the pre-stored device key and the appended handshake nonce to obtain the user key from the decrypted user profile. At ACT19, the door device is configured to generate a reply nonce. At ACT20, the door device is configured to transmit the reply nonce to the server through the bridge and the router.
• At ACT21, the server is configured to generate a modified reply nonce based on the reply nonce received from the door device. At ACT22, the server is configured to generate an encrypted command based on the access request. The command is encrypted using the user key and the modified reply nonce. At ACT23, the server is configured to transmit the encrypted command to the door device through the router and the bridge. At ACT24, the door device is configured to generate a modified reply nonce based on the reply nonce (i.e., independent of the server). At ACT25, the door device is configured to decrypt the encrypted command using the user key obtained from the user profile and the modified reply nonce. The door device is then configured to perform an action specified by the decrypted command.
• It should be understood that, in some implementations, the handshake nonce, the reply nonce, and the modified reply nonce are omitted from thethird communication process2300. In some embodiments, the bridge does not perform ACT2 until the user device performs ACT15 (e.g., the bridge requests the bridge profile to establish communication with the door device after the user device requests access such that continuous communication with the door device is not necessary). In some embodiments, the bridge does not perform ACT6 until the user device performs ACT15 (e.g., the bridge establishes communication with the door device after the user device requests access such that continuous communication with the door device is not necessary, etc.).
• As shown inFIG. 24, afourth communication process2400 is shown according to an embodiment where a user device (e.g., theuser device1900, etc.) is not within short-range communication (e.g., BLE, Wi-Fi, etc.) of a door device (e.g., thelocking system1300, thecamera system1400, thecontroller1500, etc.) or an intermediary device (e.g., thewireless bridge1200, thewireless router1600, etc.). At ACT1, the user device is configured to transmit an access request to the server to access the door device. In some embodiments (e.g., in instances where theuser device1900 is within short-range communication of thewireless router1600, etc.), ACT1 is replaced with ACT1A and ACT1B. At ACT1A, the user device is configured to transmit an access request to the router. At ACT1B, the router is configured to transmit the access request to the server. At ACT2, the server is configured to generate an encrypted user profile in response to the request. The server is configured to encrypt the user profile and a user key with the device key associated with the door device and a handshake nonce. The server is configured to append the handshake nonce to the encrypted user profile. At ACT3, the server is configured to transmit the encrypted user profile to the door device through the router and the bridge.
• At ACT4, the door device is configured to decrypt the encrypted user profile with the pre-stored device key and the appended handshake nonce to obtain the user key from the decrypted user profile. At ACT5, the door device is configured to generate a reply nonce. At ACT6, the door device is configured to transmit the reply nonce to the server through the bridge and the router.
• At ACT7, the server is configured to generate a modified reply nonce based on the reply nonce received from the door device. At ACT5, the server is configured to generate an encrypted command based on the access request. The command is encrypted using the user key and the modified reply nonce. At ACT5, the server is configured to transmit the encrypted command to the door device through the router and the bridge. At ACT10, the door device is configured to generate a modified reply nonce based on the reply nonce (i.e., independent of the server). At ACT11, the door device is configured to decrypt the encrypted command using the user key obtained from the user profile and the modified reply nonce. The door device is then configured to perform an action specified by the decrypted command. It should be understood that, in some implementations, the handshake nonce, the reply nonce, and the modified reply nonce are omitted from thefourth communication process2400.
• As shown inFIG. 25, afifth communication process2500 is shown according to an embodiment where a user device (e.g., theuser device1900, etc.) is not within short-range communication (e.g., BLE, Wi-Fi, etc.) of a door device (e.g., thelocking system1300, thecamera system1400, thecontroller1500, etc.) or an intermediary device (e.g., thewireless bridge1200, thewireless router1600, etc.). At ACT1, a server (e.g., thedoor server1700, etc.) receives a request to add a user or the user device to a door system (e.g., thedoor system1000, etc.) including the door device. At ACT2, the server is configured to generate an encrypted user profile in response to the request. The server is configured to encrypt the user profile and a user key with a device key associated with the door device and a handshake nonce. The server is configured to append the user key associated with the user device and the handshake nonce to the encrypted user profile. At ACT3, the server is configured to transmit the encrypted user profile to the user device.
• At ACT4, the user device is configured to store the user key appended to the encrypted user profile. At ACT5, the user device is configured to transmit the encrypted user profile with the handshake nonce appended thereto to the door device through the server, the router, and the bridge. At ACT6, the door device is configured to decrypt the encrypted user profile with a pre-stored device key and the appended handshake nonce to obtain the user key from the decrypted user profile. At ACT7, the door device is configured to generate a reply nonce. At ACT5, the door device is configured to transmit the reply nonce to the user device through the bridge, the router, and the server.
• At ACT5, the user device is configured to generate a modified reply nonce based on the reply nonce received from the door device. At ACT10, the user device is configured to generate an encrypted command. The command is encrypted using the user key and the modified reply nonce. At ACT11, the user device is configured to transmit the encrypted command to the door device through the server, the router, and the bridge. At ACT12, the door device is configured to generate a modified reply nonce based on the reply nonce (i.e., independent of the user device). At ACT13, the door device is configured to decrypt the encrypted command using the user key obtained from the user profile and the modified reply nonce. The door device is then configured to perform an action specified by the decrypted command. It should be understood that, in some implementations, the handshake nonce, the reply nonce, and the modified reply nonce are omitted from thefifth communication process2500.
• As utilized herein, the terms “approximately,” “about,” “substantially”, and similar terms are intended to have a broad meaning in harmony with the common and accepted usage by those of ordinary skill in the art to which the subject matter of this disclosure pertains. It should be understood by those of skill in the art who review this disclosure that these terms are intended to allow a description of certain features described and claimed without restricting the scope of these features to the precise numerical ranges provided. Accordingly, these terms should be interpreted as indicating that insubstantial or inconsequential modifications or alterations of the subject matter described and claimed are considered to be within the scope of the disclosure as recited in the appended claims.
• It should be noted that the term “exemplary” and variations thereof, as used herein to describe various embodiments, are intended to indicate that such embodiments are possible examples, representations, or illustrations of possible embodiments (and such terms are not intended to connote that such embodiments are necessarily extraordinary or superlative examples).
• The term “coupled” and variations thereof, as used herein, means the joining of two members directly or indirectly to one another. Such joining may be stationary (e.g., permanent or fixed) or moveable (e.g., removable or releasable). Such joining may be achieved with the two members coupled directly to each other, with the two members coupled to each other using a separate intervening member and any additional intermediate members coupled with one another, or with the two members coupled to each other using an intervening member that is integrally formed as a single unitary body with one of the two members. If “coupled” or variations thereof are modified by an additional term (e.g., directly coupled), the generic definition of “coupled” provided above is modified by the plain language meaning of the additional term (e.g., “directly coupled” means the joining of two members without any separate intervening member), resulting in a narrower definition than the generic definition of “coupled” provided above. Such coupling may be mechanical, electrical, or fluidic.
• References herein to the positions of elements (e.g., “top,” “bottom,” “above,” “below”) are merely used to describe the orientation of various elements in the FIGURES. It should be noted that the orientation of various elements may differ according to other exemplary embodiments, and that such variations are intended to be encompassed by the present disclosure.
• The hardware and data processing components used to implement the various processes, operations, illustrative logics, logical blocks, modules and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose single- or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or, any conventional processor, controller, microcontroller, or state machine. A processor also may be implemented as a combination of computing devices, such as 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. In some embodiments, particular processes and methods may be performed by circuitry that is specific to a given function. The memory (e.g., memory, memory unit, storage device) may include one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage) for storing data and/or computer code for completing or facilitating the various processes, layers and modules described in the present disclosure. The memory may be or include volatile memory or non-volatile memory, and may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. According to an exemplary embodiment, the memory is communicably connected to the processor via a processing circuit and includes computer code for executing (e.g., by the processing circuit or the processor) the one or more processes described herein.
• The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.
• Although the figures and description may illustrate a specific order of method steps, the order of such steps may differ from what is depicted and described, unless specified differently above. Also, two or more steps may be performed concurrently or with partial concurrence, unless specified differently above. Such variation may depend, for example, on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations of the described methods could be accomplished with standard programming techniques with rule-based logic and other logic to accomplish the various connection steps, processing steps, comparison steps, and decision steps.
• It is important to note that the construction and arrangement of the door systems and the components thereof as shown in the various exemplary embodiments is illustrative only. Additionally, any element disclosed in one embodiment may be incorporated or utilized with any other embodiment disclosed herein. Although only one example of an element from one embodiment that can be incorporated or utilized in another embodiment has been described above, it should be appreciated that other elements of the various embodiments may be incorporated or utilized with any of the other embodiments disclosed herein.

Claims (20)

1. A door assembly comprising:

a door;

an electronic locking mechanism coupled to the door, the electronic locking mechanism having a first transceiver configured to facilitate wireless communication with a first external device via a first wireless communication protocol; and

a camera system disposed within the door, the camera system having a second transceiver configured to facilitate wireless communication with a second external device via a second wireless communication protocol that is different than the first wireless communication protocol.

2. The door assembly ofclaim 1, wherein the first wireless communication protocol is a Bluetooth communication protocol and the second wireless communication protocol is a Wi-Fi communication protocol.

3. The door assembly ofclaim 1, wherein the first external device and the second external device are the same device.

4. The door assembly ofclaim 1, wherein at least one of the electronic locking mechanism or the camera system communicates with the first external device or the second external device, respectively, through an intermediary device.

5. The door assembly ofclaim 1, wherein the first external device includes at least one of a first remote server, a user device, a wireless bridge, or a wireless router, and wherein the second external device includes at least one of the first remote server, a second remote server, the user device, the wireless bridge, or the wireless router.

6. The door assembly ofclaim 1, wherein the camera system includes a third transceiver configured to facilitate wireless communication via the first wireless communication protocol, and wherein the camera system is configured to operate as a wireless bridge that converts an input signal received in the second wireless communication protocol to an output signal transmitted in the first wireless communication protocol.

7. The door assembly ofclaim 1, further comprising a wireless bridge including a third transceiver configured to communicate via the first wireless communication protocol and a fourth transceiver configured to communicate via the second wireless communication protocol, wherein the wireless bridge is configured to convert an input signal received in the second wireless communication protocol to an output signal transmitted in the first wireless communication protocol.

8. The door assembly ofclaim 7, wherein the wireless bridge is separate from the door or disposed within the door.

9. The door assembly ofclaim 1, further comprising:

a first connection box embedded in the door, wherein the first connection box includes a first interface configured to selectively interface with a first connector of the electronic locking mechanism; and

a second connection box embedded in the door, wherein the second connection box is configured to selectively receive the camera system, and wherein the second connection box includes a second interface configured to selectively interface with a second connector of the camera system.

10. The door assembly ofclaim 9, further comprising:

an electric transfer hinge coupled to an edge of the door, the electric transfer hinge configured to (i) facilitate pivotally coupling the door to a door jamb and (ii) facilitate electrically coupling the electronic locking mechanism and the camera system to an external power source; and

a third connection box embedded in the door;

wherein the third connection box includes a third interface configured to selectively interface with a third connector of the electric transfer hinge; and

wherein the first connection box and the second connection box are electrically coupled to the third connection box.

11. The door assembly ofclaim 1, further comprising:

at least one of:

(i) a window embedded within the door, wherein the window at least one of (a) includes electrically-controllable shades or (b) has an electrically-controllable opacity; or

(ii) a lighting system; and

a controller configured to facilitate controlling operation of the at least one of the window or the lighting system.

12. The door assembly ofclaim 11, wherein the controller is disposed within the door.

13. The door assembly ofclaim 11, wherein the controller is separate from the door.

14. The door assembly ofclaim 11, further comprising a switch configured to facilitate selectively activating the at least one of the window or the lighting system.

15. The door assembly ofclaim 14, wherein the controller is embedded in the switch.

16. The door assembly ofclaim 11, wherein the controller includes at least one of (i) a third transceiver configured to facilitate wireless communication via the first wireless communication protocol or (ii) a fourth transceiver configured to facilitate wireless communication via the second wireless communication protocol.

17. The door assembly ofclaim 16, wherein the controller includes the third transceiver and the fourth transceiver, and wherein the controller is configured to operate as a wireless bridge that converts an input signal received in the second wireless communication protocol to an output signal transmitted in the first wireless communication protocol.

18. A modular door assembly comprising:

a door slab;

a first selectively-accessible connection box embedded in the door slab; and

a second selectively-accessible connection box embedded in the door slab;

wherein the first selectively-accessible connection box includes a first interface configured to selectively interface with a first connector of an electronic locking mechanism;

wherein the second selectively-accessible connection box is configured to selectively receive and store a camera device within the door slab; and

wherein the second selectively-accessible connection box includes a second interface configured to selectively interface with a second connector of the camera device.

19. The modular door assembly ofclaim 18, further comprising a third selectively-accessible connection box embedded in the door slab, wherein the third selectively-accessible connection box includes a third interface configured to selectively interface with a third connector of an electric transfer hinge, and wherein the first selectively-accessible connection box and the second selectively-accessible connection box are electrically coupled to the third selectively-accessible connection box.

20. A door assembly comprising:

a door slab;

a first electrically-controllable component coupled to or embedded within the door slab;

a second electrically-controllable component coupled to or embedded within the door slab; and

a controller operatively connected to the first electrically-controllable component, the controller configured to control operation of the first electrically-controllable component;

wherein operation of the second electrically-controllable component is controllable independent of the controller.

Images