BACKGROUND

[0001] Access control systems typically involve the use of credentials to manage the operation of an access control device (e.g., a lock device). Such credentials may be assigned to a particular user or device and are often physical in nature, forming at least a portion of, for example, a smartcard, proximity card, key fob, token device, or mobile device. Thus, current credential systems generally require an interaction between the credential and a reader device (e.g., on or secured to the access control device) such that the reader device may read the credential and determine whether access should be granted. In particular, a user may be required to swipe, tap, or otherwise present the credential to the reader device. As such, access control systems often require an active physical action on behalf of the user in order to grant the user access via the access control device.

SUMMARY

[0002] One embodiment is directed to a unique system, components, and methods for UWB antenna solutions for access control. Other embodiments are directed to apparatuses, systems, devices, hardware, methods, and combinations thereof UWB antenna solutions for access control.

[0003] According to an embodiment, an electronic lock configured to be secured to a door having a secure side and an unsecure side may include an exterior escutcheon on the unsecure side of the door, an interior escutcheon on the secure side of the door, a printed circuit board assembly (PCBA) positioned within the exterior escutcheon, and a plurality of ultra wideband (UWB) antennas secured to an exterior-facing side of the PCBA, wherein the plurality of UWB antennas comprises a first UWB antenna and a second UWB antenna configured to operate on a first UWB channel, and wherein the second UWB antenna is positioned no greater than one half of a wavelength of the first UWB channel from the first UWB antenna along a first axis.

[0004] In some embodiments, the first axis may be a horizontal axis. [0005] In some embodiments, the plurality of UWB antennas may be a third UWB antenna configured to operate on the first UWB channel and positioned no greater than one half of the wavelength of the first UWB channel from the second UWB antenna along the first axis. [0006] In some embodiments, the plurality of UWB antennas may be a third UWB antenna configured to operate on the first UWB channel and positioned no greater than one half of the wavelength of the first UWB channel from the second UWB channel along a second axis perpendicular to the first axis.

[0007] In some embodiments, the electronic lock may further include a third UWB antenna secured to an interior side of the PCBA.

[0008] In some embodiments, the electronic lock may further include a waveguide positioned between the third UWB antenna and a surface of the interior escutcheon, and the waveguide may be structured to allow for unobstructed radio frequency (RF) transmission. [0009] In some embodiments, the electronic lock may further include a housing defined at least in part by the interior escutcheon and the exterior escutcheon, and a cavity within the housing may define the waveguide.

[0010] In some embodiments, the plurality of UWB antennas may include a third UWB antenna configured to operate on a second UWB channel and positioned no greater than one half of a wavelength of the second UWB channel from the second UWB antenna.

[0011] In some embodiments, the second UWB antenna may be positioned one half of the wavelength of the first UWB channel from the first UWB antenna and the third UWB antenna may be positioned one half of the wavelength of the second UWB channel from the second UWB antenna.

[0012] In some embodiments, the one half of the wavelength of the first UWB channel may be determined based on a center frequency of the first UWB channel.

[0013] In some embodiments, the electronic lock may further include a processor and a memory comprising a plurality of instructions stored thereon that, in response to execution by the processor, causes the electronic lock to determine whether a user intends to access a passageway secured by the door based on signals received by the plurality of UWB antennas. [0014] According to another embodiment, an access control device may include a lock mechanism adapted to control access to a passageway, a printed circuit board assembly having a first side and a second side, a first ultra wideband antenna secured to the first side of the printed circuit board assembly and configured to operate on a first ultra wideband channel, a second ultra wideband antenna secured to the first side of the printed circuit board assembly no greater than one half of a wavelength of the first ultra wideband channel from the first ultra wideband antenna along a first axis and configured to operate on a first ultra wideband channel, an exterior escutcheon adapted to be secured to an unsecure side of a door and to house the printed circuit board assembly, a processor, and a memory comprising a plurality of instructions stored thereon that, in response to execution by the processor, causes the access control device to determine whether a user intends to access the passageway based on signals received by the first ultra wideband antenna and the second ultra wideband antenna from a mobile device of the user.

[0015] In some embodiments, the access control device may further include a third ultra wideband antenna secured to the first side of the printed circuit board assembly no greater than one half of the wavelength of the first ultra wideband channel from the second ultra wideband antenna along the first axis and configured to operate on the first ultra wideband channel.

[0016] In some embodiments, the access control device may further include a third ultra wideband antenna secured to the first side of the printed circuit board assembly no greater than one half of the wavelength of the first ultra wideband channel from the second ultra wideband antenna along a second axis perpendicular to the first axis and configured to operate on the first ultra wideband channel.

[0017] In some embodiments, the access control device may further include a third ultra wideband antenna secured to the second side of the printed circuit board assembly.

[0018] In some embodiments, the access control device may further include an interior escutcheon adapted to be secured to a secure side of the door and a waveguide structured to allow for unobstructed radio frequency (RF) transmission that is positioned between the third ultra wideband antenna and a surface of the interior escutcheon.

[0019] In some embodiments, the access control device may further include a housing defined at least in part by the interior escutcheon and the exterior escutcheon, and a cavity within the housing may define the waveguide.

[0020] In some embodiments, the access control device may further include a third ultra wideband antenna configured to operate on a second ultra wideband channel and secured to the first side of the printed circuit board assembly no greater that one half of a wavelength of the second ultra wideband channel from the second ultra wideband antenna. [0021] In some embodiments, the one half of the wavelength of the first ultra wideband channel may be determined based on a center frequency of the first ultra wideband channel. [0022] According to yet another embodiment an access control system may include a mobile device and an access control device including a printed circuit board assembly having a first side and a second side, a first ultra wideband antenna secured to the first side of the printed circuit board assembly and configured to operate on a first ultra wideband channel, a second ultra wideband antenna secured to the first side of the printed circuit board and configured to operate on the first ultra wideband channel, an exterior escutcheon adapted to be secured to a structure at an unsecure side of a passageway and to house the printed circuit board assembly, a processor, and a memory comprising a plurality of instructions stored thereon that, in response to execution by the processor, causes the access control device to determine whether a user intends to access the passageway based on signals received by the first ultra wideband antenna and the second ultra wideband antenna from the mobile device.

[0023] This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used as an aid in limiting the scope of the claimed subject matter. Further embodiments, forms, features, and aspects of the present application shall become apparent from the description and figures provided herewith.

BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The concepts described herein are illustrative by way of example and not by way of limitation in the accompanying figures. For simplicity and clarity of illustration, elements illustrated in the figures are not necessarily drawn to scale. Where considered appropriate, references labels have been repeated among the figures to indicate corresponding or analogous elements.

[0025] FIG. l is a simplified block diagram of at least one embodiment of an access control system for leveraging ultra wideband (UWB) antenna solutions for increased accuracy for intent detection;

[0026] FIG. 2 is a simplified block diagram of at least one embodiment of a computing device;

[0027] FIG. 3 is a side view of at least one embodiment of an electronic lock for levering the UWB antenna solutions; [0028] FIGS. 4-10 illustrate various embodiments of UWB antenna arrangements; and [0029] FIG. 11 is a simplified flow diagram of at least one embodiment of a method for performing a UWB ranging session.

DETAILED DESCRIPTION

[0030] Although the concepts of the present disclosure are susceptible to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and will be described herein in detail. It should be understood, however, that there is no intent to limit the concepts of the present disclosure to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives consistent with the present disclosure and the appended claims.

[0031] References in the specification to “one embodiment,” “an embodiment,” “an illustrative embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may or may not necessarily include that particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. It should further be appreciated that although reference to a “preferred” component or feature may indicate the desirability of a particular component or feature with respect to an embodiment, the disclosure is not so limiting with respect to other embodiments, which may omit such a component or feature. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

Additionally, it should be appreciated that items included in a list in the form of “at least one of A, B, and C” can mean (A); (B); (C); (A and B); (B and C); (A and C); or (A, B, and C).

Similarly, items listed in the form of “at least one of A, B, or C” can mean (A); (B); (C); (A and B); (B and C); (A and C); or (A, B, and C). Further, with respect to the claims, the use of words and phrases such as “a,” “an,” “at least one,” and/or “at least one portion” should not be interpreted so as to be limiting to only one such element unless specifically stated to the contrary, and the use of phrases such as “at least a portion” and/or “a portion” should be interpreted as encompassing both embodiments including only a portion of such element and embodiments including the entirety of such element unless specifically stated to the contrary. [0032] The disclosed embodiments may, in some cases, be implemented in hardware, firmware, software, or a combination thereof. The disclosed embodiments may also be implemented as instructions carried by or stored on one or more transitory or non-transitory machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. A machine-readable storage medium may be embodied as any storage device, mechanism, or other physical structure for storing or transmitting information in a form readable by a machine (e.g., a volatile or non-volatile memory, a media disc, or other media device).

[0033] In the drawings, some structural or method features may be shown in specific arrangements and/or orderings. However, it should be appreciated that such specific arrangements and/or orderings may not be required. Rather, in some embodiments, such features may be arranged in a different manner and/or order than shown in the illustrative figures unless indicated to the contrary. Additionally, the inclusion of a structural or method feature in a particular figure is not meant to imply that such feature is required in all embodiments and, in some embodiments, may not be included or may be combined with other features.

[0034] The terms longitudinal, lateral, and transverse may be used to denote motion or spacing along three mutually perpendicular axes, wherein each of the axes defines two opposite directions. The directions defined by each axis may also be referred to as positive and negative directions. Additionally, the descriptions that follow may refer to the directions defined by the axes with specific reference to the orientations illustrated in the figures. For example, the directions may be referred to as distal/proximal, left/right, and/or up/down. It should be appreciated that such terms may be used simply for ease and convenience of description and, therefore, used without limiting the orientation of the system with respect to the environment unless stated expressly to the contrary. For example, descriptions that reference a longitudinal direction may be equally applicable to a vertical direction, a horizontal direction, or an off-axis orientation with respect to the environment. Furthermore, motion or spacing along a direction defined by one of the axes need not preclude motion or spacing along a direction defined by another of the axes. For example, elements described as being “laterally offset” from one another may also be offset in the longitudinal and/or transverse directions, or may be aligned in the longitudinal and/or transverse directions. The terms are therefore not to be construed as further limiting the scope of the subject matter described herein. [0035] Referring now to FIG. 1, in the illustrative embodiment, an access control system 100 for leveraging ultra wideband (UWB) antenna solutions for increased accuracy for detecting user intent to gain access to a passageway is shown. The illustrative access control system 100 includes an access control device 102, a management system 104, and a UWB device 106. Further, the management system 104 may include a management server 110, a gateway device 112, an access control panel 114, and/or a mobile device 116.

[0036] As described in detail below, the access control device 102 may control access to a passageway (e.g., through a doorway) via a lock mechanism 120 based on an intent of the user of a UWB device 106 (e.g., a UWB-capable smartphone) inferred based on UWB communication signals received from the UWB device 106. In particular, the access control device 102 may determine the location of the UWB device 106 relative to the access control device 102 based on phase difference of arrival (PDoA) and angle of arrival (AoA) calculations from UWB signals received by the UWB antennas 122 of the access control device 102. It should be appreciated that the access control device 102 may determine the relative location of the UWB device 106 as a two-dimensional location or a three-dimensional location depending on the particular embodiment. Further, the access control device 102 may determine whether the relative location of the UWB device 106 corresponds with a location indicative of the user’s intent to access the passageway (e.g., based on one or more threshold distances, threshold angles, and/or previously stored intent locations). If the relative location indicates that the user intends to access the passageway, in some embodiments, the access control device 102 may automatically control the lock mechanism 120 without requiring user input or a physical action by the user (e.g., to unlock the lock mechanism 120).

[0037] It should be appreciated that the access control device 102, the management system 104, the UWB device 106, the management server 110, the gateway device 112, the access control panel 114, and/or the mobile device 116 may be embodied as any type of device or collection of devices suitable for performing the functions described herein.

[0038] More specifically, in the illustrative embodiment, the access control device 102 may be embodied as any type of device capable of controlling access through a passageway. For example, in various embodiments, the access control device 102 may be embodied as an electronic lock (e.g., a mortise lock, a cylindrical lock, or a tubular lock) or a peripheral controller of a passageway. In some embodiments, it should be appreciated that the access control device 102 may be embodied as an electronic lock similar to the electronic lock 302 of FIG. 3. Depending on the particular embodiment, the access control device 102 may include a credential reader or be electrically/communicatively coupled to a credential reader configured to communicative with UWB device 106. As described herein, the access control device 102 includes a plurality of UWB antennas 122 for determining the relative location of UWB devices 106 in the vicinity of the access control device 102 (e.g., user mobile devices that may be interested in gaining access through the passageway secured by the access control device 102). Further, it should be appreciated that the access control device 102 may also include other wireless communication circuitry for communicating with the UWB device 106 and/or other devices via corresponding protocols (e.g., Wi-Fi, Bluetooth (e.g., including BLE), Zigbee, Z- Wave, Near Field Communication (NFC), Thread, etc.). Additionally, in various embodiments, the access control device 102 may include a capacitive sense circuitry (e.g., a capacitive touch sensor), proximity sensor, and/or other access control circuitry.

[0039] The illustrative access control device 102 includes a lock mechanism 120 configured to control access through a passageway. For example, in some embodiments, the lock mechanism 120 may be configured to be positioned in a locked state in which access to the passageway is denied, or positioned in an unlocked state in which access to the passageway is permitted. In some embodiments, the lock mechanism 120 includes a deadbolt, latch bolt, lever, and/or other mechanism adapted to move between the locked and unlocked state and otherwise perform the functions described herein. However, it should be appreciated that the lock mechanism 120 may be embodied as any another mechanism suitable for controlling access through a passageway in other embodiments.

[0040] As described herein, the access control device 102 includes a plurality of UWB antennas 122 positioned apart from one another such that a UWB signal may be received by the UWB antennas 122 to allow the access control device 102 to determine a relative location of the sending device (e.g., the UWB device 106) based on angle of arrival (AoA) and phase difference of arrival (PDoA) calculations made as part of a ranging session between the devices. It should be appreciated that the number, spacing, and arrangement of the UWB antennas 122 within the access control device 102 directly impact the accuracy of the location tracking. Various embodiments of UWB antenna arrays or arrangements are described below in reference to FIGS. 4-10. [0041] In the illustrative embodiment, the UWB device 106 may be embodied as any mobile device capable of communicating with the access control device 102 via UWB signals (e.g., for UWB ranging), exchanging credential information with the access control device 102, and/or otherwise performing the functions described herein. Accordingly, in some embodiments, in addition to having UWB communication circuitry, it should be appreciated that the UWB device 106 may also include other wireless communication circuitry for communicating with the access control device 102 and/or other devices via corresponding protocols (e.g., Wi-Fi, Bluetooth (e.g., including BLE), Zigbee, Z-Wave, Near Field Communication (NFC), Thread, etc.).

[0042] As described herein, the management system 104 may be configured to manage credentials of the access control system 100. For example, the management system 104 may be responsible for ensuring that the access control devices 102 have updated authorized credentials, whitelists, blacklists, device parameters, and/or other suitable data. Additionally, in some embodiments, the management system 104 may receive security data, audit data, raw sensor data, and/or other suitable data from the access control devices 102 for management of the access control system 100. In some embodiments, one or more of the devices of the management system 104 may be embodied as an online server or a cloud-based server. Further, in some embodiments, the management system 104 may communicate with multiple access control devices 102 at a single site (e.g., a particular building) and/or across multiple sites. That is, in such embodiments, the management system 104 may be configured to receive data from access control devices 102 distributed across a single building, multiple buildings on a single campus, or across multiple locations.

[0043] It should be appreciated that the management system 104 may include one or more devices depending on the particular embodiment of the access control system 100. For example, as shown in FIG. 1, the management system 104 may include a management server 110, a gateway device 112, an access control panel 114, and/or a mobile device 116 depending on the particular embodiment. The functions of the management system 104 described herein may be performed by one or more of those devices in various embodiments. For example, in some embodiments, the management server 110 may perform all of the functions of the management system 104 described herein. Further, in some embodiments, the gateway device 112 may be communicatively coupled to the access control device 102 such that the other devices of the management system 104 (e.g., the management server 110, the access control panel 114, and/or the mobile device 116) may communicate with the access control device 102 via the gateway device 112.

[0044] In some embodiments, the access control device 102 may communicate with the management server 110 over a Wi-Fi connection and/or with the mobile device 116 over a Bluetooth connection. Additionally, the access control device 102 may communicate with the management server 110 and/or the access control panel 114 via the gateway device 112. As such, in the illustrative embodiment, the access control device 102 may communicate with the gateway device 112 over a Wi-Fi connection and/or a Bluetooth connection, and the gateway device 112 may, in turn, forward the communicated data to the relevant management server 110 and/or access control panel 114. In particular, in some embodiments, the gateway device 112 may communicate with the access control panel 114 over a serial communication link (e.g., using RS-485 standard communication), and the gateway device 112 may communicate with the management server 110 over a Wi-Fi connection, an Ethernet connection, or another wired/wireless communication connection. As such, it should be appreciated that the access control device 102 may communicate with the management server 110 via an online mode with a persistent real-time communication connection or via an offline mode (e.g., periodically or in response to an appropriate condition) depending on the particular embodiment (e.g., depending on whether the access control device 102 is offline). As indicated above, in other embodiments, it should be appreciated that the access control device 102 may communicate with the devices of the management system 104 via one or more other suitable communication protocols.

[0045] It should be appreciated that each of the access control device 102, the management system 104, the UWB device 106, the management server 110, the gateway device 112, the access control panel 114, and/or the mobile device 116 may be embodied as one or more computing devices similar to the computing device 200 described below in reference to FIG. 2. For example, in the illustrative embodiment, each of the access control device 102, the management system 104, the UWB device 106, the management server 110, the gateway device 112, the access control panel 114, and the mobile device 116 includes a processing device 202 and a memory 206 having stored thereon operating logic 208 for execution by the processing device 202 for operation of the corresponding device. [0046] It should be further appreciated that, although the management system 104 and the management server 110 are described herein as one or more computing devices outside of a cloud computing environment, in other embodiments, the system 104 and/or server 110 may be embodied as a cloud-based device or collection of devices. Further, in cloud-based embodiments, the system 104 and/or server 110 may be embodied as a “serverless” or server- ambiguous computing solution, for example, that executes a plurality of instructions on-demand, contains logic to execute instructions only when prompted by a particular activity/trigger, and does not consume computing resources when not in use. That is, the system 104 and/or server 110 may be embodied as a virtual computing environment residing “on” a computing system (e.g., a distributed network of devices) in which various virtual functions (e.g., Lambda functions, Azure functions, Google cloud functions, and/or other suitable virtual functions) may be executed corresponding with the functions of the system 104 and/or server 110 described herein. For example, when an event occurs (e.g., data is transferred to the system 104 and/or server 110 for handling), the virtual computing environment may be communicated with (e.g., via a request to an API of the virtual computing environment), whereby the API may route the request to the correct virtual function (e.g., a particular server-ambiguous computing resource) based on a set of rules. As such, when a request for the transmission of updated access control data is made by a user (e.g., via an appropriate user interface to the system 104 or server 110), the appropriate virtual function(s) may be executed to perform the actions before eliminating the instance of the virtual function(s).

[0047] Although only one access control device 102, one management system 104, one UWB device 106, one management server 110, one gateway device 112, one access control panel 114, and one mobile device 116 are shown in the illustrative embodiment of FIG. 1, the system 100 may include multiple access control devices 102, management systems 104, UWB devices 106, management servers 110, gateway devices 112, access control panels 114, and/or mobile devices 116 in other embodiments. For example, as indicated above, the server 110 may be embodied as multiple servers in a cloud computing environment in some embodiments. Further, each user may be associated with one or more separate UWB devices 106 in some embodiments.

[0048] Referring now to FIG. 2, a simplified block diagram of at least one embodiment of a computing device 200 is shown. The illustrative computing device 200 depicts at least one embodiment of an access control device, UWB device, mobile device, management server, gateway device, and/or access control panel that may be utilized in connection with the access control device 102, the management system 104, the UWB device 106, the management server 110, the gateway device 112, the access control panel 114, and/or the mobile device 116 illustrated in FIG. 1. Depending on the particular embodiment, computing device 200 may be embodied as a reader device, credential device, access control device, UWB-capable device, server, desktop computer, laptop computer, tablet computer, notebook, netbook, Ultrabook™, mobile computing device, cellular phone, smartphone, wearable computing device, personal digital assistant, Internet of Things (loT) device, control panel, processing system, router, gateway, and/or any other computing, processing, and/or communication device capable of performing the functions described herein.

[0049] The computing device 200 includes a processing device 202 that executes algorithms and/or processes data in accordance with operating logic 208, an input/output device 204 that enables communication between the computing device 200 and one or more external devices 210, and memory 206 which stores, for example, data received from the external device 210 via the input/output device 204.

[0050] The input/output device 204 allows the computing device 200 to communicate with the external device 210. For example, the input/output device 204 may include a transceiver, a network adapter, a network card, an interface, one or more communication ports (e.g., a USB port, serial port, parallel port, an analog port, a digital port, VGA, DVI, HDMI, FireWire, CAT 5, or any other type of communication port or interface), and/or other communication circuitry. Communication circuitry may be configured to use any one or more communication technologies (e.g., wireless or wired communications) and associated protocols (e.g., Ethernet, Bluetooth®, Wi-Fi®, WiMAX, etc.) to effect such communication depending on the particular computing device 200. The input/output device 204 may include hardware, software, and/or firmware suitable for performing the techniques described herein.

[0051] The external device 210 may be any type of device that allows data to be inputted or outputted from the computing device 200. For example, in various embodiments, the external device 210 may be embodied as the access control device 102, the management system 104, the UWB device 106, the management server 110, the gateway device 112, the access control panel 114, and/or the mobile device 116. Further, in some embodiments, the external device 210 may be embodied as another computing device, switch, diagnostic tool, controller, printer, display, alarm, peripheral device (e.g., keyboard, mouse, touch screen display, etc.), and/or any other computing, processing, and/or communication device capable of performing the functions described herein. Furthermore, in some embodiments, it should be appreciated that the external device 210 may be integrated into the computing device 200.

[0052] The processing device 202 may be embodied as any type of processor(s) capable of performing the functions described herein. In particular, the processing device 202 may be embodied as one or more single or multi-core processors, microcontrollers, or other processor or processing/controlling circuits. For example, in some embodiments, the processing device 202 may include or be embodied as an arithmetic logic unit (ALU), central processing unit (CPU), digital signal processor (DSP), and/or another suitable processor(s). The processing device 202 may be a programmable type, a dedicated hardwired state machine, or a combination thereof. Processing devices 202 with multiple processing units may utilize distributed, pipelined, and/or parallel processing in various embodiments. Further, the processing device 202 may be dedicated to performance of just the operations described herein, or may be utilized in one or more additional applications. In the illustrative embodiment, the processing device 202 is of a programmable variety that executes algorithms and/or processes data in accordance with operating logic 208 as defined by programming instructions (such as software or firmware) stored in memory 206. Additionally or alternatively, the operating logic 208 for processing device 202 may be at least partially defined by hardwired logic or other hardware. Further, the processing device 202 may include one or more components of any type suitable to process the signals received from input/output device 204 or from other components or devices and to provide desired output signals. Such components may include digital circuitry, analog circuitry, or a combination thereof.

[0053] The memory 206 may be of one or more types of non-transitory computer- readable media, such as a solid-state memory, electromagnetic memory, optical memory, or a combination thereof. Furthermore, the memory 206 may be volatile and/or nonvolatile and, in some embodiments, some or all of the memory 206 may be of a portable variety, such as a disk, tape, memory stick, cartridge, and/or other suitable portable memory. In operation, the memory 206 may store various data and software used during operation of the computing device 200 such as operating systems, applications, programs, libraries, and drivers. It should be appreciated that the memory 206 may store data that is manipulated by the operating logic 208 of processing device 202, such as, for example, data representative of signals received from and/or sent to the input/output device 204 in addition to or in lieu of storing programming instructions defining operating logic 208. As shown in FIG. 2, the memory 206 may be included with the processing device 202 and/or coupled to the processing device 202 depending on the particular embodiment. For example, in some embodiments, the processing device 202, the memory 206, and/or other components of the computing device 200 may form a portion of a system-on-a-chip (SoC) and be incorporated on a single integrated circuit chip.

[0054] In some embodiments, various components of the computing device 200 (e.g., the processing device 202 and the memory 206) may be communicatively coupled via an input/output subsystem, which may be embodied as circuitry and/or components to facilitate input/output operations with the processing device 202, the memory 206, and other components of the computing device 200. For example, the input/output subsystem may be embodied as, or otherwise include, memory controller hubs, input/output control hubs, firmware devices, communication links (i.e., point-to-point links, bus links, wires, cables, light guides, printed circuit board traces, etc.) and/or other components and subsystems to facilitate the input/output operations.

[0055] The computing device 200 may include other or additional components, such as those commonly found in a typical computing device (e.g., various input/output devices and/or other components), in other embodiments. It should be further appreciated that one or more of the components of the computing device 200 described herein may be distributed across multiple computing devices. In other words, the techniques described herein may be employed by a computing system that includes one or more computing devices. Additionally, although only a single processing device 202, VO device 204, and memory 206 are illustratively shown in FIG.

2, it should be appreciated that a particular computing device 200 may include multiple processing devices 202, I/O devices 204, and/or memories 206 in other embodiments. Further, in some embodiments, more than one external device 210 may be in communication with the computing device 200.

[0056] Referring now to FIG. 3, in some embodiments, the access control device 102 may be embodied as an electronic lock similar to the electronic lock 302 of FIG. 3, which is secured to a door 304 and configured to control passage through the door 304. It should be appreciated that the door 304 has a secure side 306 (e.g., an exterior side of a perimeter door) and an unsecure side 308 (e.g., an interior side of a perimeter door). Further, as shown, the illustrative electronic lock 302 has a housing defined at least in part by an exterior escutcheon 310 configured to be secured at or to an unsecure side 308 of the door 304 and an interior escutcheon 312 configured to be secured at or to a secure side 306 of the door 304. In the illustrative embodiment, the electronic lock 302 includes a printed circuit board assembly (PCBA) 314 that is positioned within (e.g., mounted within) the exterior escutcheon 310, and the PCBA 314 has an exterior-facing side (or “exterior side”) 316 and an interior-facing side (or simply “interior side”) 318. In some embodiments, the electronic lock 302 also includes a PCBA 320 that is positioned within (e.g., mounted within) the interior escutcheon 312, and the PCBA 320 has an interior-facing side 322 and an exterior-facing side 324.

[0057] As described herein, the electronic lock 302 includes a plurality of UWB antennas 122, which may be secured to an exterior-facing side 316 of the PCBA 314, an interior-facing side 318 of the PCBA 314, an interior-facing side 322 of the PCBA 320, and/or an exteriorfacing side 324 of the PCBA 320 depending on the particular embodiment. For example, in various embodiments described in greater detail below (see, for example, FIGS. 4-10), the electronic lock 302 includes a plurality of UWB antennas 122 secured to an exterior-facing side 316 of the PCBA 314 and zero or more UWB antennas 122 secured to an inter-facing side 318 of the PCBA 314. Further, it should be appreciated that other electronic components of the electronic lock 302 (e.g., processor, memory, sensors, etc.) may be secured to one or more of the PCBAs 314, 320 depending on the particular embodiment.

[0058] In some embodiments, the electronic lock 302 includes a waveguide 326 that is structured to allow for unobstructed radio frequency (RF) transmission to and/or from one or more UWB antennas 122. For example, in some embodiments, the waveguide 326 allows for unobstructed RF transmission to and/or from a UWB antenna 122 secured to the interior-facing side 318 of the PCBA 314. More specifically, in some embodiments, the waveguide 326 may be positioned and/or defined between a UWB antenna 122 secured to the inter-facing side 318 of the PCBA 314 and a surface 328 of the interior escutcheon 312. It should be appreciated that the waveguide 326 may be formed of one or more physical components that allow for the transmission of RF signals and/or formed from the absence of physical components depending on the particular embodiment. For example, in some embodiments, the exterior escutcheon 310 and the interior escutcheon 312 may form at least a portion of a housing of the electronic lock 302 that has a cavity therein defining the waveguide 326.

[0059] Although the escutcheons and sides are described herein with reference to “interior” and “exterior,” it should be appreciated that such terminology is used simply for convenience and brevity of the description. For example, in some embodiments, both sides of the door 304 may be interior in the sense that both sides of the door 304 are within the perimeter of a building (e.g., as for a wholly interior door). Additionally, although the illustrative embodiment depicts the electronic lock 302 as being secured to the door 304, it should be appreciated that the electronic lock 302 (or other embodiment of the access control device 102) may be secured to a different structure in other embodiments (e.g., the door frame, a wall, etc.). For example, in some embodiments, the access control device 102 may be embodied as a wall- mounted reader or peripheral controller.

[0060] The illustrative electronic lock 302 includes a lock mechanism 330, which may be similar to the lock mechanism 120 described above in reference to FIG. 1. In particular, the illustrative lock mechanism 330 may include a deadbolt, latch bolt, lever, and/or other mechanism that may be positioned in a locked state to secure the door 304 and prevent passage through the door 304 (i.e., when the door 304 is closed) or may be positioned in an unlocked state to allow passage through the door 304. Further, in some embodiments, the electronic lock 302 may include a wire harness 332 that extends through at least a portion of the door 304 and electrically couples various electronic components of the electronic lock 302 to one another. For example, the wire harness 332 may form a portion of circuitry that includes the PCBAs 314, 320 (and components thereon), the lock mechanism 330, and/or other components of the electronic lock 302 depending on the particular embodiment.

[0061] FIGS. 4-10 illustrate various UWB antenna 122 arrangements of the access control device 102 and/or the electronic lock 302. Although the description of FIGS. 4-10 applies equally to the electronic lock 302 in various embodiments, it should be appreciated that FIGS. 4-10 are described in reference to the access control device 102 for brevity of the description. In FIGS. 4-5 and 8-9, the solid fill is used to indicate that the corresponding components are secured to a top layer of the corresponding PCBA, and the hashed fill is used to indicate that the corresponding components are on the bottom/opposite layer of the corresponding PCBA. Further, in some embodiments, the UWB antennas 122 are secured to the PCBA 314. For example, in such embodiments, the solid fill components are secured to the exterior-facing side 316 of the PCBA 314, and the hashed fill components are secured to the interior-facing side 318 of the PCBA 314. Each of the UWB antennas 122 is depicted as a round patch antenna with the diameter equal to one half of the wavelength of the UWB channel of operation (e.g., measured based on the center frequency of the channel). However, it should be appreciated that one or more of the UWB antennas 122 may be otherwise shaped and/or sized in other embodiments (e.g., rectangular, irregularly shaped, etc.). For example, depending on the particular embodiment, any given pair of UWB antennas 122 may be spaced part from one another a distance equal to one half of the wavelength of the UWB channel of operation, less than one half of the wavelength of the UWB channel of operation, or greater than one half of the wavelength of the UWB channel of operation. It should be appreciated, however, that the shape, size, and positioning of the UWB antennas 122 can affect the performance of the antenna system.

[0062] In the embodiment of FIG. 4, the access control device 102 includes three UWB antennas 122 spaced apart from one another along an axis (e.g., a horizontal axis or x-axis), and a ground plane on the opposite side of the PCBA. In the embodiment of FIG. 5, the access control device 102 includes five UWB antennas 122 spaced apart from one another along the axis, likewise with a ground plane on the opposite side of the PCBA. Additionally, in the embodiments of FIGS. 4-5, the UWB antennas 122 are illustratively spaced one half of a wavelength of the UWB channel of operation apart from one another. In other embodiments, the UWB antennas 122 may be positioned less than one half of a wavelength from one another. It should be appreciated that the access control device 102 measures the PDoA between pairs of UWB antennas 122 (e.g., RX1 and RX2), the rapid comparison of which increasing the accuracy of UWB-based tracking/ranging. Further, as the number of UWB antennas 122 that are linearly spaced as depicted in FIGS. 4-5 increases, the antenna array naturally narrows the “viewing” angle.

[0063] In the embodiments of FIGS. 6-7, the access control device 102 includes three UWB antennas 122 in which two of the UWB antennas 122 are spaced apart from one another along an axis (e.g., a horizontal axis or x-axis), and a third UWB antenna 122 is spaced apart from the other two UWB antennas 122 along a perpendicular axis (e.g., a vertical axis or y-axis). Additionally, the UWB antennas 122 are illustratively space one half of a wavelength of the UWB channel of operation apart from one another along the corresponding axes. In other embodiments, the UWB antennas 122 may be positioned less than one half of a wavelength from one another. It should be appreciated that the access control device 102 may scan the UWB antenna 126 pair positioned along the first/horizontal axis (e.g., RX1 and RX2) for distance and location of the UWB device 106, whereas the access control device 102 may scan the UWB antenna 126 pair positioned along the second/horizontal axis (e.g., RX2 and RX3) for changes in elevation of the UWB device 106. It should be further appreciated that changes in elevation may initiate a different calibration curve in the horizontal axis (e.g., x-axis), and knowing the elevation information may allow for increased accuracy in the horizontal axis (e.g., x-axis) PDoA result.

[0064] In the embodiments of FIGS. 8-9, the access control device 102 includes four UWB antennas 122 in which three of the UWB antennas 122 are spaced apart from one another along an axis (e.g., a horizontal axis or x-axis), and a fourth UWB antenna 122 is spaced apart from the other three UWB antennas 122 along a perpendicular axis (e.g., a vertical axis or y- axis). Additionally, the UWB antennas 122 are illustratively spaced one half of a wavelength of the UWB channel of operation apart from one another along the corresponding axes. In other embodiments, the UWB antennas 122 may be positioned less than one half of a wavelength from one another. It should be further appreciated that the UWB antennas 122 of the embodiments of FIGS. 8-9 are not all mounted at the same depth (e.g., in the z-axis direction). Instead, in the illustrative embodiment of FIG. 8, three of the UWB antennas 122 (RX1, RX2, and RX3) are secured to the top layer (e.g., exterior-facing side 316) of the PCBA (e.g., the PCBA 314), whereas the fourth UWB antenna 122 (RX4) is secured to the bottom layer (e.g., interior-facing side 318) of the PCBA (e.g., the PCBA 314). Similarly, in the illustrative embodiment of FIG. 9, two of the UWB antennas 122 (RX2 and RX3) are secured to the top layer (e.g., exterior-facing side 316) of the PCBA (e.g., the PCBA 314), and two of the UWB antennas 122 (RX1 and RX4) are secured to the bottom layer (e.g., inter-facing side 318) of the PCBA (e.g., the PCBA 314). As described above, the linear placement of multiple antennas allows for extended performance in the x-axis direction. Additionally, by mounting one or more of the UWB antennas 122 at different depths relative to the top layer (e.g., with small depth differences), performance at extreme angles may be improved. It should be further appreciated that, in some embodiments, the UWB antenna(s) 122 secured to the inter-facing side 318 of the PCBA 314 may benefit from the waveguide 326 providing for unobstructed RF transmission to/from the UWB antenna(s) 122.

[0065] In the embodiment of FIG. 10, the access control device 102 includes five UWB antennas 122 that are sized and spaced for compact dual channel optimization and vertical and horizontal polarization. In particular, the illustrative embodiment is optimized for operation on the universal channel for UWB communication — channels 5 and 9. Accordingly, the illustrative embodiment reflects optimized antenna sizing and spacing for operation on channel 5 while also reflecting optimized sizing and spacing for operation on channel 9. As shown, three of the UWB antennas 122 (RX1, RX2, and RX4) are spaced apart from one another along an axis (e.g., a horizontal axis or x-axis), and three of the UWB antennas 122 (RX3, RX2, and RX5) are spaced apart from one another along a perpendicular axis (e.g., a vertical axis or y-axis). Additionally, the UWB antennas 122 optimized for channel 9 (RX1, RX2, and RX3) are spaced one half of a wavelength of UWB channel 9 (e.g., the center frequency of that channel) apart from one another along the respective axes, and the UWB antennas 122 optimized for channel 5 (RX2, RX4, and RX5) are spaced one half of a wavelength of UWB channel 5 (e.g., the center frequency of that channel) apart from one another along the respective axes. By way of example, the center frequency of UWB channel 9 is 7.9872 GHz (with a half wavelength of 18.8mm). Accordingly, in various embodiments, UWB antennas 122 optimized for operation on UWB channel 9 may be spaced 18.0mm apart, or 16.0mm apart (e.g., which yields improved results relative to 18.0mm spacing based on simulated data). Further, in some embodiments, a ground shield may be added and optimized for the respective channels of operation. Although the embodiment of FIG. 10 is described in reference to UWB channels 5 and 9, it should be appreciated that the access control device 102 may be optimized to operate on additional or alternative UWB channels in other embodiments using technologies similar to those described herein.

[0066] It should be further appreciated that the UWB antenna solutions described herein may be used in conjunction with other communication circuitry and/or other access control technologies depending on the particular embodiment of the access control device 102. For example, in some embodiments, the access control device 102 may combine UWB, Bluetooth (e.g., BLE), Wi-Fi, Ethernet, NFC, proximity card, RS-485, and/or other technologies into a single compact form factor (e.g., with minimal interference or cross talk between antennas structures and/or electrical filtering per antenna to improve in-band and reject out-of-band performance optimal for each wireless technology). Further, in some embodiments, capacitive touch and/or proximity detection may be integrated into a PCBA design that includes the UWB antennas 122. Additionally, in some embodiments, the access control device 102 may include a side-facing UWB antenna (e.g., on a different PCBA) or otherwise angled antenna for improved resolution.

[0067] Referring now to FIG. 11, in use, the access control device 102 may execute a method 1100 for performing a UWB ranging session. It should be appreciated that the particular blocks of the method 1100 are illustrated by way of example, and such blocks may be combined or divided, added or removed, and/or reordered in whole or in part depending on the particular embodiment, unless stated to the contrary. Although the description of FIG. 11 applies equally to the electronic lock 302 in various embodiments, it should be appreciated that FIG. 11 is described in reference to the access control device 102 for brevity of the description.

[0068] The illustrative method 1100 begins with block 1102 in which the access control device 102 measures a time of flight of an RF signal received by the UWB antennas 122 from the UWB device 106. In block 1104, the access control device 102 calculates a distance of the UWB device 106 relative to the access control device 102 based on the time of flight measurement. In block 1106, the access control device 102 may apply a distance calibration correction to the calculated distance to improve the accuracy of the distance calculation.

[0069] In block 1108, the access control device 102 measures the azimuth phase difference of arrival of the RF signal received by the UWB antennas 122 from the UWB device 106. In block 1110, the access control device 102 calculates an azimuth angle of arrival of the RF signal based on the phase difference of arrival and the antenna separation distance of the respect UWB antennas 122. It should be appreciated that the antenna separation distance may be stored in the firmware/software of the access control device 102 for retrieval during such calculations. Further, in some embodiments, the access control device 102 may calculate an azimuth angle of arrival of the RF signal based on a look-up table (e.g., with PDoA as the input) and/or using other techniques. In block 1112, the access control device 102 may apply an azimuth angle of arrival calibration correction to the calculated angle to improve the accuracy of the azimuth angle of arrival calculation.

[0070] In block 1114, the access control device 102 measures the elevation phase difference of arrival of the RF signal received by the UWB antennas 122 from the UWB device 106. In block 1116, the access control device 102 calculates an elevation angle of arrival of the RF signal based on the phase difference of arrival and the antenna separation distance of the respect UWB antennas 122. Further, in some embodiments, the access control device 102 may calculate an elevation angle of arrival of the RF signal based on a look-up table (e.g., with PDoA as the input) and/or using other techniques. In block 1118, the access control device 102 may apply an elevation angle of arrival calibration correction to the calculated angle to improve the accuracy of the elevation angle of arrival calculation.

[0071] In block 1120, the access control device 102 calculates a three-dimensional coordinate of the UWB device 106 based on the calculated azimuth angle of arrival of the RF signal, elevation angle of arrival of the RF signal, and distance of the UWB device 106 relative to the access control device 102.

[0072] Although the blocks 1102-1120 are described in a relatively serial manner, it should be appreciated that various blocks of the method 1100 may be performed in parallel in some embodiments. It should be further appreciated that the method 1100 of FIG. 11 is described by way of example, and the access control device 102 may employ other methods and techniques for determining the relative location of the UWB device 106 based on the received UWB signals in other embodiments.