Patent Description:
Physical access control covers a range of systems and methods to govern access, for example by people, to secure areas or secure assets. Physical access control includes identification of authorized users and/or devices (e.g., vehicles, drones, etc.) and actuation of a gate, door, or other mechanism used to secure an area or actuation of a control mechanism, e.g., a physical or electronic/software control mechanism, permitting access to a secure asset. A PACS can include a reader (e.g., an online or offline reader) that holds authorization data and can be capable of determining whether credentials (e.g., from credential or credential devices such as radio frequency identification (RFID) chips in cards, fobs, or personal electronic devices such as mobile phones) are authorized for an actuator (e.g., door lock, door opener, software control mechanism, turning off an alarm, etc.). In other examples, a PACS can include a host server to which readers and/or actuators (e.g., via a controller) are connected in a centrally managed configuration. In centrally managed configurations, readers can obtain credentials from a credential or credential device and pass those credentials to the PACS host server. The host server can then determine whether the credentials authorize access to the secure area and command the actuator or other control mechanism accordingly.

<CIT> discloses methods and devices for allowing a mobile device (e.g., a key fob or a consumer electronic device, such as a mobile phone, watch, or other wearable device) to interact with a vehicle such that a location of the mobile device can be determined by the vehicle, thereby enabling certain functionality of the vehicle. A device may include both RF antenna(s) and magnetic antenna(s) for determining a location of a mobile device relative to the vehicle. Such a hybrid approach can provide various advantages. Existing magnetic coils on a mobile device (e.g., for charging or communication) may be re-used for distance measurements that are supplemented by the RF measurements. Any device antenna may provide measurements to a machine learning model that determines a region in which the mobile device resides, based on training measurements in the regions.

<CIT>A refers to a secure ranging system using a secure processing system to deliver one or more ranging keys to a ranging radio on a device, and the ranging radio can de-rive locally at the system ranging codes based on the ranging keys. A deterministic random number generator can derive the ranging codes using the ranging key and one or more session parameters, and each device (e.g. a cellular telephone and another device) can independently derive the ranging codes and derive them contemporaneously with their use in ranging operations.

<CIT> shows a waist type wearable indoor mobile positioning terminal which comprises a power supply module, an ultra-wide bandwidth (UWB) locating module, a Bluetooth transmission module, a Zigbee transmission module, an inertial navigation module, an information processing module and a locating waist, wherein the UWB locating module is in two-way connection with the Bluetooth transmission module. The inertial navigation module is in two-way connection with the Zigbee transmission module. The Bluetooth transmission module and the Zigbee transmission module are respectively connected with the information processing module. The information processing module is arranged on the locating waist. The power supply module is used for supplying power for the other modules in the terminal.

<CIT> relates to a system to measure the position of an article and track a moving line of a transport device in an indoor warehouse, capable of being constructed at low cost. According to the present invention, the system comprises a indoor warehouse, a real-time location system ultrawide band (RTLS UWB) communication anchors, a transport apparatus, an RTLS UWB tag, an radio frequency ID (RFID) scanner installed in the transport device, a pallet having the RFID tag attached thereto, an RTLS edge server, an RTLS server, an RTLS manager computer, and an RTLS monitoring server.

<CIT> describes an authentication system of a vehicle for authenticating a portable ID transmitter relative to the vehicle in order to enable vehicle functions for an operator. An authentication arrangement of the authentication system has a first vehicle UWB interface and a second vehicle UWB interface, a control means, optional proximity sensors, and optional LF interfaces. At least one antenna of the first vehicle UWB interface is arranged outside a sheet metal casing of the vehicle.

<CIT> relates to a device for controlling access to a machine, comprising a portable object having a signal transmission member and a device for locking and unlocking a machine. The member for controlling the device is capable of triggering, once the second transceiver of the device has received the signal, the transmission of a signal to a wireless radio receiver supported by the portable object, and comprises a control member for triggering, when the wireless radio receiver has received the second signal, the transmission of a signal, the control member being connected to a calculator member for computing a distance between the portable object and the device using the signals, the portable object comprising a member for independently powering the transmission member, the receiver and the control member thereof. The device comprises a further calculator member for computing an incoming angle of the first signal and/or the third signal such as to trigger, when the angle is within a given angular range and when the distance is lower than a predetermined value, the unlocking of the machine and to trigger, when the distance is higher than a predetermined value, the locking of the machine.

<CIT> discloses a method of managing communication between a portable device and a contactless reader able to communicate using a first wireless technology configured to communicate in a short-range mode. The method comprises the steps of: - establishing a first channel between the contactless reader and a wireless unit, - establishing between the wireless unit and the portable device a second channel using a second wireless technology which is configured: - to operate with a range greater than that of said first wireless technology, - to detect the position of the portable device with respect to the wireless unit, - to handle an anti-collision phase, - establishing a bridge between the contactless reader and the portable device through said first and second channels only if the detected position of the portable device matches with the contactless reader.

<CIT> relates to an apparatus for enhancing the security of short-range communication in connection with an access control device may be provided. The system includes a mobile device and an application executing thereon. The application is configured to store a user-defined authentication for permitting short-range communication with the associated access control device and configured to control access to a secure location. The authentication is related to an action of an end user of the mobile device. The application is configured to determine when the devices are in proximity to one another, detect a movement of a user of the mobile device, and permit short-range communication between the devices when the devices are in proximity to one another and the detected movement is substantially similar to the defined authentication. The permitted short-range communication is related to information for permitting the user to access the secure location.

A more detailed understanding may be had from the following description, which is presented by way of example in conjunction with the following drawings, in which like reference numerals are used across the drawings in connection with like elements.

An aspect of the present invention is disclosed in claim <NUM>. Embodiments of the present invention can be found in dependent claims <NUM>-<NUM>. Disclosed herein are embodiments of a reader system comprising an ultra-wide band (UWB) module and a reader of an access control system. While described herein with respect to physical access control systems (PACS), the UWB module may be utilized for any other type of access control system. UWB is a radio frequency (RF) technique that uses short, low power, pulses over a wide frequency spectrum. The pulses can occur on the order of millions of times per second. The width of the frequency spectrum of a given UWB implementation is generally greater than the lesser of <NUM> megahertz (MHz) and twenty percent of an arithmetic center frequency of the frequency spectrum for the given UWB implementation.

UWB can be used for communication by encoding data via time modulation (e.g., pulse-position encoding). Here, symbols are specified by pulses on a subset of time units out of a set of available time units. Other examples of types of UWB encodings include amplitude modulation and polarity modulation. The wide band transmission tends to be more robust to multipath fading than carrier-based transmission techniques. Further, the lower power of pulses at any given frequency tends to reduce interference with carrier-based communication techniques.

<FIG> depicts an example scenario <NUM> in which a PACS could be used, in accordance with at least one embodiment. As shown in <FIG>, a wall <NUM> has disposed therein a door <NUM>. In an example situation, a secured area lies behind the door <NUM>, which has a lockable handle <NUM> that grants access to the secured area when in an unlocked state and instead prevents access to the secured area when in a locked state.

A reader system <NUM> is positioned proximate to the handle <NUM> of the door <NUM>. In an embodiment, the handle <NUM> has as its default state to be in the locked state. The reader system <NUM> is operable to selectively place the handle <NUM> in the unlocked state responsive to being presented with an authorized credential contained in a credential device <NUM>, which can communicate with the reader system <NUM> via a wireless interface <NUM>. In various different embodiments, the credential device <NUM> could be or include a keycard, a fob, a mobile device (e.g., a smart phone), and/or any other suitable credential device having the communication capabilities and credentials to carry out embodiments of the present disclosure.

It should be understood that the present disclosure is applicable to numerous types of PACSs being used to secure numerous types of areas and/or other resources, assets, and/or the like. The scenario <NUM> of <FIG> is presented purely by way of example and not limitation.

<FIG> depicts an example communication context <NUM> in which the PACS (including, e.g., the reader system <NUM>) of <FIG> could operate, in accordance with at least one embodiment. As shown in <FIG>, the reader system <NUM> could be communicatively connected with a network <NUM> via a communication link <NUM>. Furthermore, a server <NUM> could be communicatively connected with the network <NUM> via a communication link <NUM>. In the present disclosure, a communication link could include one or more wireless-communication links and/or one or more wired-communication links, and could include one or more intermediate devices such as access points, network access servers, switches, routers, bridges, and/or the like. Furthermore, the network <NUM> could be or include a data-communication network such as an Internet Protocol (IP) network and/or one or more communication network of any other type.

The server <NUM> could perform one or more functions for the reader system <NUM> such as authorization, authentication, and/or the like. In some embodiments, the reader system <NUM> performs such functions locally, perhaps as a standalone unit, perhaps involving communication with one or more other devices, systems, servers, and/or the like via a local area network (LAN), for example. The server <NUM> could include a communication interface, a processor, and data storage containing instructions executable by the processor for carrying out the functions of the server <NUM>.

<FIG> depicts an example architecture <NUM> of the reader system <NUM>, in accordance with at least one embodiment. As shown in <FIG>, the reader system <NUM> includes a reader <NUM> and a UWB module <NUM> that are communicatively connected with one another via a communication link <NUM>. The communication link <NUM> may be wired or wireless. In one example, the communication link <NUM> is a BLE communication link. In some embodiments, the reader <NUM> is equipped and configured to use wireless communication such as NFC and/or Bluetooth (e.g., Bluetooth Low Energy (BLE)) to carry out communication with credential devices and to selectively place the handle <NUM> in the unlocked state responsive to being presented with an authorized credential contained in a credential device (e.g., the credential device <NUM>).

The reader <NUM> could include a wireless-communication interface for communicating according to NFC, BLE, and/or the like, and could also include a wired-communication interface for communicating according to Universal Serial Bus (USB) connections, Ethernet connections, and/or the like. The reader <NUM> could also include a processor and data storage containing instructions executable by the processor for carrying out the functions of the reader <NUM>.

In some embodiments, the reader <NUM> was installed and in use prior to the UWB module <NUM> being connected as an add-on module. In other embodiments, the reader <NUM> and the UWB module <NUM> are installed together as (or as at least part of) the reader system <NUM>. The UWB module <NUM> could be connected via the communication link <NUM> to an existing hardware port (or expansion port, expansion slot, or the like) of the reader <NUM>. In some embodiments, the communication link <NUM> is or includes a data cable. Further detail regarding an example architecture of the UWB module <NUM> is provided below in connection with <FIG>.

In an example, a user carrying a credential device may approach the reader system <NUM>. Upon the credential device coming into a threshold range of the reader system <NUM>, a credential may be exchanged using a low energy wireless protocol, such as Bluetooth Low Energy (BLE), for example. This credential exchange may be coordinated using the reader <NUM>, for example. The reader <NUM> may then establish a secret, such as a scrambled time stamp (STS), with the credential device to facilitate ranging using UWB communication. UWB ranging is carried out using the UWB module <NUM>. This occurs upon receipt of data from the reader <NUM>. The data may include the STS, an identifier of the credential such as a PACS ID, and the like. Using the ranging, one or more of the reader <NUM> or the UWB module <NUM> may be used to derive an intent of the user in order to identify an intent trigger. Once an intent trigger is identified, the reader <NUM> may release the credential to allow access to the user.

The UWB module may include a battery <NUM> or other type of local power source including energy harvesters, capacitors, and the like. The battery <NUM> may be used to provide power for the UWB module <NUM> such that it is unnecessary for the UWB module <NUM> to receive power from the reader system <NUM>, the door lock battery, or any other external power source. This can conserve power for the reader system <NUM> and may be advantageous as the it may be easier to replace a battery in the removeable UWB module <NUM> than any other battery in the reader system <NUM>.

<FIG> depicts another example architecture <NUM> of the reader system <NUM>, which is not covered by the invention. As shown in <FIG>, the reader system <NUM> could include a reader <NUM> that itself could include (e.g., as an on-board module, component, or the like) a UWB module <NUM> that includes a battery <NUM>. In an embodiment, the UWB module <NUM> is implemented as an integrated circuit (IC) that is plugged into a board (e.g., a main motherboard) of the reader <NUM>.

As a general matter, the reader <NUM> could be similar to the reader <NUM> of <FIG>, and thus is not described here in as great of detail. As with the architecture <NUM> that is described above in connection with <FIG>, in the case of the architecture <NUM> of <FIG>, the reader <NUM> could be a previously installed reader with the UWB module <NUM> being a later add on, or it could be the case that the reader <NUM> and the UWB module <NUM> are associated with a common, concurrent installation as (or as at least part of) the reader system <NUM>.

<FIG> depicts another example architecture <NUM> for the reader system <NUM>. The reader system <NUM> includes a reader <NUM> and a UWB module <NUM> configured to communicate over a communication link <NUM>. The communication link may be wired or wireless. For example, the reader <NUM> may be configured to communicate with the UWB module <NUM> using BLE. The reader <NUM> includes a controller <NUM>, antennas 408a-408c, a secure element <NUM>, an NFC IC <NUM>, an RFID IC <NUM>, sensors <NUM>, flash memory <NUM>, keypad <NUM>, and interfaces <NUM> and <NUM>. The controller <NUM> may be a BLE SoC microcontroller, or any other type of control circuit. The controller <NUM> may be capable of NFC communication through the NFC IC <NUM> and antenna 408a. The controller may be capable of BLE communication using the antenna 408b, and may be capable of RFID communication through the RFID IC <NUM> and the antenna 408c. The interfaces <NUM> and <NUM> may be a Wiegand interface and an RS485 interface, or any other interface types. The secure element <NUM> may be configured to cache secure data such as an STS, PACS ID, and the like. The components of the reader <NUM> may be collected within a first housing.

The UWB module <NUM> includes a controller <NUM>, antennas 428a and 428b, a battery <NUM>, a secure element <NUM>, and a UWB front end <NUM>. The controller <NUM> may also be a BLE SoC microcontroller, or any other type of control circuit. The battery <NUM> may be used to provide power for the UWB module <NUM> so that the UWB module does not need to be powered by the reader power, lock power, or any other power source. The controller <NUM> may be capable of UWB communication through the UWB front end <NUM>, which may be any circuit configured to package and receive UWB message for transmission and receipt through the antennas 428a and 428b. The secure element <NUM> may be configured to cache secure data such as an STS, PACS ID, and the like. The components of the UWB modules <NUM> may be described in further detail with respect to <FIG> below. The components of the UWB module <NUM> are collected within a second housing separate from the reader <NUM>.

In an example, a user carrying a credential device may approach the reader <NUM>. Upon the credential device coming into a threshold range of the reader system <NUM>, the controller <NUM> may exchange a credential with the credential device using BLE through the antenna 408b. The controller <NUM> may then establish a secret, such as a scrambled time stamp (STS), with the credential device to facilitate ranging using UWB communication. UWB ranging is carried out by the controller <NUM> of the UWB module <NUM>. This may occur upon receipt of data from the controller <NUM>. The data may include the STS, an identifier of the credential such as a PACS ID, and the like. Using the ranging, one or more of the controllers <NUM> and <NUM> may be used to derive an intent of the user in order to identify an intent trigger (such as moving to a specific position). Once an intent trigger is identified, the controller <NUM> may release the credential to allow access to the user.

<FIG> collectively depict an example UWB-module architecture <NUM> of a UWB module (e.g., the UWB module <NUM> of <FIG>, the UWB module <NUM> of <FIG> of <FIG>, the UWB module <NUM> of <FIG>, and/or the like), in accordance with at least one embodiment. In an embodiment, the UWB-module architecture <NUM> is implemented as one or more circuit boards on which one or more of the recited components reside. In other embodiments, distributed architectures can be used. Furthermore, it is noted that a number of specific components, connections, and the like are presented in a specific arrangement in the architecture <NUM> that is depicted and described in connection with <FIG>. It should be understood that this is by way of example and not limitation. In various embodiments, different components and/or different connections could be used in different arrangements, and some components can be omitted in some embodiments. Moreover, some components could be combined. In addition or instead, the functions of one or more components could be distributed across multiple components or combined in different ways. Various different input voltages, crystal oscillators, connectors, integrated circuits, and/or the like could be used in different embodiments. Various components related to debugging could be omitted from some embodiments.

<FIG> depicts a first portion 500A of the example UWB-module architecture <NUM>, in accordance with at least one embodiment. The first portion 500A includes a voltage arrangement <NUM> that includes voltages Vinext, Vin, Vinreader, and Vusb. Also included is a voltage-regulator arrangement <NUM>, which includes a first step down regulator (<NUM>-17V to 3V3), a low noise regulator (3V3 to 1V8), and a second step down regulator (<NUM>-17V to 1V8). The first step down regulator is connected to Vin and the second step down regulator at a first connection, and to input voltage 3V3 at a second connection. The low noise regulator is connected between input voltage 3V3 and <NUM> V8RF. The second step down regulator is connected between Vin and 1V8. The first step down regulator and the second step down regulator could each be an LT®<NUM> manufactured by Analog Devices®, which is headquartered in Norwood, Massachusetts. The low noise regulator could be an LT®<NUM> from Analog Devices ®.

Also included is a third step down regulator (<NUM>-17V to 5V) that is connected between Vin and 5Vwi-fi. The third step down regulator can be disabled when USB powered due to insufficient power. The third step down regulator could be an LT®<NUM> from Analog Devices®, and in at least one embodiment is only activated if the UWB module is supplied via an external power supply.

As a general matter, the UWB module can be powered through an external supply voltage or USB, as examples. In some instances, in which USB is used as the power source, the onboard 5V regulation (i.e., the third step down regulator, used for an external Wi-fi module in some embodiments) is deactivated, as the current consumption would potentially exceed the USB specification. Thus, in at least some embodiments, use of a Wi-fi extension module or any other 5V-supplied extension board would warrant use of an external power supply.

The first portion 500A further includes a Micro USB element <NUM> that is connected to input voltage Vusb and to ground, and that is further connected to a data link <NUM>. In an embodiment, Wi-fi functionality is not powered by USB, and USB only powers BLE and UWB circuits.

<FIG> depicts a second portion 500B of the example UWB-module architecture <NUM>, in accordance with at least one embodiment. In the depicted embodiment, the second portion 500B includes a BLE system on chip (SoC) <NUM>, a RevE expansion debug pinheader <NUM>, a RevE expansion connector <NUM>, a general debug pinheader <NUM>, and an ESP32 WROOM extension connector <NUM>. In an embodiment, RevE refers to a hardware revision of a reader such as an iCLASS SE reader manufactured by HID® Global Corporation, which is headquartered in Austin, Texas.

The ESP32 WROOM extension connector <NUM> could provide a connection option to an ESP32 module designed for Wi-fi connectivity, and could be configured to operate at up to a <NUM> mA current requirement at 5V, as an example. An ESP32 WROOM extension module could provide Wi-fi capability to a RevE reader, making that reader a transparent reader over Wi-fi, and could include an ESP32 WROOM module and an adapter board to a RevE extension connector (e.g., a Hirose connector). A programming adapter (e.g., VCOM via FTDI to Hirose connector) could make loading firmware easier. The Wi-fi module could be plugged into this programming adapter.

The BLE SoC <NUM> could be the NRF52840, manufactured by Nordic Semiconductor®, which is headquartered in Trondheim, Norway. In an embodiment, the BLE SoC <NUM> includes at least one onboard antenna. In at least one embodiment, the BLE SoC <NUM> is the core microcontroller for the UWB module having the example architecture <NUM>. In some embodiments, both the reader and the UWB module (a. platform) use a Nordic NRF52840 as their respective core microcontroller. In embodiments of the UWB module of the present disclosure, a Nordic NRF52840 serves not only as the core controller of the UWB module, but also as the BLE interface used to set up secure UWB ranging sessions. An example pin/peripheral assignment for the NRF52840 for use as the BLE SoC <NUM> in at least one assignment is shown in Table <NUM> at the end of this detailed description.

The BLE SoC <NUM> is connected to both input voltage 3V3 and a <NUM> crystal oscillator, and is also connected to the data link <NUM>, as well as to a data link <NUM>, a data link <NUM>, a data link <NUM>, a data link <NUM>, a data link <NUM>, a data link <NUM>, a data link <NUM>, a data link <NUM>, a data link <NUM>, and a data link <NUM>. The data link <NUM> is connected to both an optional display and to the RevE expansion debug pinheader <NUM>, which in turn is connected via a data link <NUM> to the RevE expansion connector <NUM>. The UWB module can be powered via the RevE expansion connector <NUM> in embodiments in which the UWB module is used as an add-on module to a reader. In some instances, the UWB module is powered via a dedicated power connector. The data link <NUM> is connected to the general debug pinheader <NUM>, which in turn is connected via a data link <NUM> to the ESP32 Wroom extension connector <NUM>. The RevE expansion connector <NUM> is connected to both input voltage Vinreader and to ground, whereas the ESP32 Wroom extension connector <NUM> is connected to both input voltage 5Vwi-fi and to ground.

<FIG> depicts a third portion 500C of the example UWB-module architecture <NUM>, in accordance with at least one embodiment. In the depicted embodiment, the third portion 500C includes a mode selector <NUM>, which could be or include a low profile DIP switch, and could be or include a double switch that allows developers to identify and/or define a number (e.g., <NUM>) different operation modes of the UWB module having the example UWB-module architecture <NUM>. The different operation modes could include a RevE extension mode, a standalone mode, a Wi-fi mode, and a debug mode, as examples. The mode selector <NUM> is connected to the data link <NUM>. The mode selector <NUM> may allow a single firmware image to be developed for these and other multiple operation modes. In an embodiment, the mode selector <NUM> is a CVS-02TB manufactured by NIDEC® Copal Electronics of Torrance, California.

In the depicted embodiment, the third portion 500C also includes a secure element <NUM>, an embedded video engine <NUM>, a backlight driver <NUM>, and a display connector <NUM>. As indicated by a board/printed circuit board (PCB) boundary <NUM>, the secure element <NUM> could be or could reside on a PCB that is separate from a main board of the UWB-module architecture <NUM>. The data link <NUM> is connected to both the secure element <NUM> and the embedded video engine <NUM>. The secure element <NUM> could be or include a secure access module (SAM). In an embodiment, the secure element <NUM> is an ST33 ARM SC300 secure microcontroller manufactured by STMicroelectronics®, which is headquartered in Geneva, Switzerland.

The embedded video engine <NUM> could be an FT811 embedded video engine (EVE) manufactured by Future Technology Devices International® Limited, which is headquartered in Glasgow, Scotland in the United Kingdom. In at least one embodiment, the presence of the embedded video engine <NUM> on the board helps to unload the main microcontroller (i.e., the BLE SoC <NUM>). The embedded video engine <NUM> could be wired to drive an external display in RGB mode, and to control the backlight driver <NUM>. The embedded video engine <NUM> is connected to input voltage 3V3, and also by a data link <NUM> to the backlight driver <NUM> and by a data link <NUM> to the display controller <NUM>. The backlight driver <NUM> is connected to the display controller <NUM> by a data link <NUM>. In the depicted embodiment, the backlight driver <NUM> is the FAN5333, a dedicated LED controller that is manufactured by Fairchild Semiconductor®, a subsidiary of ON Semiconductor®, which is headquartered in Phoenix Arizona. In an embodiment, the backlight driver <NUM> is used to control a display backlight. A shutdown pin of the backlight driver <NUM> is controlled in an embodiment by the embedded video engine <NUM> via a pulse width modulation (PWM), to allow for dimming.

The display connector <NUM> is further connected to input voltage 3V3, and with the BLE SoC <NUM> via a data link <NUM>. The display connector <NUM> could be compatible with the Displaytech® DT024CTFT and DT024CTFT-TS displays, the latter of which supports touch control. These are examples of external thin-film-transistor (TFT) displays that the presently disclosed UWB-module architecture is designed to support, though other displays may be used instead. The display connector <NUM> could be a dedicated flat flex connector (FFC). In an embodiment, the supported display is <NUM>" in size with 320x240 pixel resolution. A supported display could use an ILI9341 controller form ILI Technology® Corporation of Taiwan.

<FIG> depicts a fourth portion 500D of the example UWB-module architecture <NUM>, in accordance with at least one embodiment. In the depicted embodiment, the fourth portion 500D includes a group of Arduino compatible extension headers <NUM>, and also includes a Joint Test Action Group (JTAG) connector <NUM> that is connected to the data link <NUM>, and a flash memory <NUM> that is connected to the data link <NUM> and also to input voltage 3V3. In an embodiment, the flash memory <NUM> could be an MX25L flash memory module manufactured by Macronix® International Co. headquartered in Taiwan. In an embodiment, the particular part used is the MX25L1606EXCI-<NUM>. The flash memory <NUM> could be used for storage of firmware images or other data. The capacity of the flash memory <NUM> could be <NUM> MB as an example. In an embodiment, a similar flash memory module is used in the reader to which the present UWB module is operably connected. The flash memory <NUM> and/or the flash memory module in the reader could be connected to a Queued Serial Peripheral Interface (QSPI) to enable flash access while still maintaining use of a general secure peripheral interface (SPI) interface.

The JTAG connector <NUM> could be the FTSH-<NUM>-<NUM>-F-DV-K, manufactured by Samtec®, Inc. , headquartered in New Albany, Indiana. The JTAG connector <NUM> could be configured to operate in Serial Wire (SW) mode, which is an operating mode for the JTAG port where only two pins, TCLK and TMS, are used for the communication. A third pin can be used optionally to trace data. JTAG pins and SW pins are shared. In an embodiment, with respect to the pins of the JTAG connector <NUM>, TCLK is SWCLK (Serial Wire Clock), TMS is SWDIO (Serial Wire debug Data Input/Output), TDO is SWO (Serial Wire trace Output), and TDI is NC. Multiple JTAG connectors could be used on the board of the UWB module having the example architecture <NUM> that is described herein.

<FIG> depicts a fifth portion 500E of the example UWB-module architecture <NUM>, in accordance with at least one embodiment. In the depicted embodiment, the fifth portion 500E includes a first level shifter <NUM>, a second level shifter <NUM>, a UWB integrated circuit chip debug pinheader <NUM>, a secure element (SE) SPI pinheader <NUM>, an SE debug pinheader <NUM>, and an SE <NUM>.

The first level shifter <NUM> could be a TXB0108 <NUM>-bit bidirectional voltage-level translator manufactured by Texas Instruments® Incorporated, which is headquartered in Dallas, Texas. The TXB0108 is used in at least one embodiment for general purpose I/O and SPI communication. In an embodiment, a core reset signal of the TXB0108 is used to control an output enable of the first level shifter <NUM>. This allows for both the SE <NUM> and the below-described UWB IC <NUM> of <FIG> to be connected to an external circuit if the core reset line is pulled low, which can be done via the BLE SoC EX06 or via a pin header, as examples. The first level shifter <NUM> is connected to the data link <NUM> and to a data link <NUM>, which is in turn connected to the debug connector <NUM>. In an embodiment, the data link <NUM> includes an SPI bus that uses unified configuration interface (UCI) commands for unsecure ranging and UWB IC configuration.

The second level shifter <NUM> could include both a TXB0108 <NUM>-bit bidirectional voltage-level translator as well as a PCA9306DCUR bidirectional voltage-level translator also manufactured by Texas Instruments® Incorporated. The PCA9306DCUR is a dedicated <NUM>-bit bidirectional I<NUM>C level shifter. In an embodiment, the PCA9306DCUR is used for the I<NUM>C interface to the SE <NUM>. The second level shifter <NUM> is connected to the data link <NUM> and also to a data link <NUM>, which is in turn connected to both the NXP SE debug connector <NUM> and the NXP secure element (SE) <NUM>. In an embodiment, the NXP SE debug connector <NUM> is usable for external device connection to update an NXP applet (e.g., Secure Element Management Service (SEMS) agent).

In an embodiment, the first level shifter <NUM> and the second level shifter <NUM> are used because the below-described UWB IC <NUM> of <FIG> is designed for a mobile device and as such has only limited supply voltage support, in particular only for <NUM>. Due to that, the interfaces to the UWB IC <NUM> in the present disclosure undergo voltage-level shifting. In an alternative approach, a host controller that operates at <NUM>. 8V could be used, or the I/O voltage of the host processor could be supplied with <NUM>. An advantage of the depicted architecture is that it makes it easier to interface with external devices. Also, the cross-switch capability of the BLE SoC <NUM> (in embodiments using the nRF52840) leads to flexible peripheral assignments on any of the external interfaces, making it less advantageous to use level shifters for those pins.

The SE <NUM> is connected via a data link <NUM> to the SE SPI pinheader <NUM>, which itself is also connected to input voltage <NUM> V8 and to ground. In addition to being connected to the SE SPI pinheader <NUM> via the data link <NUM> and to both the second level shifter <NUM> and the NXP SE debug connector <NUM> via the data link <NUM>, the SE <NUM> is also connected to input voltage 3V3, input voltage <NUM> V8, and a data link <NUM>. In an embodiment, the SE <NUM> supports secure ranging. The SE <NUM> could be a Java Card SE with an NFC front end. In at least one embodiment, the SE <NUM> is the SN110U, which is a single chip secure element and NFC controller manufactured by NXP Semiconductors® N. , which is headquartered in Eindhoven, Netherlands. In an embodiment, the NFC controller is designed for integration in mobile devices compliant with NFC Forum, EMVCo and ETSI/SWP.

<FIG> depicts a sixth portion 500F of the example UWB-module architecture <NUM>, in accordance with at least one embodiment. In the depicted embodiment, the sixth portion 500F includes the above-mentioned UWB IC <NUM>, as well as a first matching circuit <NUM>, a radar port <NUM>, a first RF switch <NUM>, a first surface acoustic wave (SAW) bandpass filter <NUM>, a second matching circuit <NUM>, a first antenna port <NUM>, a second RF switch <NUM>, a second SAW bandpass filter <NUM>, a third matching circuit <NUM>, a second antenna port <NUM>, a fourth matching circuit <NUM>, a third antenna port <NUM>, and a BLE antenna <NUM>.

In at least one embodiment, the UWB <NUM> can be an SR100T, which is a secure fine ranging chipset that, like the SN110U that can be used as the SE <NUM>, is manufactured by NXP Semiconductors® N. In an embodiment, the SR100T is a fully integrated single chip Impulse Radio Ultra-Wideband (IR-UWB) low-energy transceiver IC, compliant with IEEE <NUM>. <NUM> HRP UWB PHY. It is designed for secure ranging applications in a mobile environment. It supports super high frequency (SHF) UWB bands from <NUM> to <NUM> for worldwide use. It has a programmable transmitter output power of up to 12dBm, as well as a fully coherent receiver for maximum range and accuracy. It integrates all relevant RF components (e.g., matching network, balun), and it complies with FCC & ETSI UWB spectral masks. It uses a supply voltage of <NUM>. 8V +/-<NUM>%.

The SR100T also supports angle of arrival (AoA) measurement, and has integrated I/Q phase and amplitude mismatch compensation. Its form factor is a <NUM> x <NUM> <NUM>-pin Wafer Level Chip Scale Package (WLCSP) package with <NUM> pitch. It includes an ARM® Cortex-M33 <NUM> Bit processor having <NUM> kB code RAM, <NUM> kB data RAM, <NUM> kB ROM, and ARM® TrustZone technology and S-DMA for security. The SR100T further has a BSP32 CoolFlux SubSystem having a <NUM> clock, 32kB code RAM, and 2x16kB data RAM. The SR100T also has a hardwired DSP for the first receive data link <NUM>, the second received data link <NUM>, and the transmission data link <NUM>; operating frequencies of <NUM>, <NUM>, and <NUM>; 2x4kB RAM for channel estimators, and 4x32kB RAM for RF data log.

As depicted in <FIG>, the UWB <NUM> is connected to input voltage <NUM> V8RF, input voltage 1V8, a first crystal oscillator (<NUM>), a second crystal oscillator (<NUM>), the data link <NUM>, the data link <NUM>, a data link <NUM>, a transmission data link <NUM>, a first receive data link <NUM>, a second receive data link <NUM>, a data link <NUM>, and a data link <NUM>.

The UWB IC <NUM> can be considered to be connected to two RF pipelines: a first RF pipeline and a second RF pipeline. The first RF pipeline includes the first RF switch <NUM>, the first SAW bandpass filter <NUM>, the second matching circuit <NUM>, and the first antenna port <NUM>. The second RF pipeline includes the second RF switch <NUM>, the second SAW bandpass filter <NUM>, the third matching circuit <NUM>, and the second antenna port <NUM>.

In the depicted embodiment, the UWB IC <NUM> is connected to the first matching circuit <NUM> via the transmission data link <NUM>, which also connects the UWB IC <NUM> with the first RF switch <NUM>. The first matching circuit <NUM> in turn is connected via a data link <NUM> to the radar port <NUM>, which corresponds to a radar interface that can be used in connection with various embodiments. UWB can be used in radar operations, providing localization accuracies on the scale of tens of centimeters. Due to the possibly variable absorption and reflection of different frequencies in a pulse, both surface and obstructed (e.g., covered) features of an object can be detected. In some cases, the localization provides an angle of incidence in addition to distance.

As stated, in the first RF pipeline, the UWB IC <NUM> is connected via the transmission data link <NUM> to the first RF switch <NUM>. The UWB IC <NUM> is also connected to the first RF switch <NUM> via the second receive data link <NUM> and the data link <NUM>. The first RF switch <NUM>, which is further connected to input voltage <NUM> V8RF, could be an XMSSJR6G0BA, which is manufactured by Murata® Manufacturing Company, Ltd. , which is headquartered in Kyoto, Japan. The first RF switch <NUM> is in turn connected via a data link <NUM> to the first SAW bandpass filter <NUM>, which is in turn connected via a data link <NUM> to the second matching circuit <NUM>. The second matching circuit <NUM> is in turn connected via a data link <NUM> to the first antenna port <NUM>, which in at least one embodiment is in turn connected to a first external UWB antenna.

In the second RF pipeline, the UWB IC <NUM> is connected to the second RF switch <NUM> via the data link <NUM> and also via the first receive data link <NUM>. The UWB IC <NUM> is also connected to input voltage <NUM> V8RF and to ground. The second RF switch could also be an XMSSJR6GOBA. The second RF switch <NUM> is in turn connected via a data link <NUM> to the second SAW bandpass filter <NUM>, which is in turn connected via a data link <NUM> to the third matching circuit <NUM>. The third matching circuit <NUM> is in turn connected via a data link <NUM> to the second antenna port <NUM>, which in at least one embodiment is in turn connected to a second external UWB antenna.

Any suitable number of external UWB antennas can be used in various different embodiments. In embodiments in which a third external UWB antenna is deployed in connection with the presently disclosed example architecture <NUM>, a third RF pipeline is deployed to connect to the third externa UWB antenna. Moreover, a switch can be implemented to facilitate switching between antennas for different communication packets.

Further depicted in <FIG> is the fourth matching circuit <NUM> connected between the data link <NUM> and a data link <NUM>, which further connects to the third antenna port <NUM>. The third antenna port <NUM> provides optional connectivity to an external BLE antenna. In the depicted embodiment, the third antenna port <NUM> is connected via a data link <NUM> with the BLE antenna <NUM>, which could be a <NUM> BLE antenna.

In at least one embodiment, for its RF interfaces, the UWB module of the present disclosure utilizes U. FL connectors manufactured by Hirose® Electric Group, which is headquartered in Tokyo, Japan. These RF interfaces include the radar port <NUM> that can be connected to a radar antenna, the first antenna port <NUM> that can be connected to a first external UWB antenna, the second antenna port <NUM> that can be connected to a second external UWB antenna, and the third antenna port <NUM> that can be connected to the (external) BLE antenna <NUM>. FL connectors are miniature RF coaxial connectors for high frequency signals, commonly used in applications where space is limited. They are often used in laptop mini PCI cards as well as mobile phones. Cables are manufactured by Hirose® can also be used. In some embodiments, Hirose X. FL connectors are used. Among other differences, X. FL connectors are rated for use at higher frequencies than are U. FL connectors.

<FIG> depicts a seventh portion of the example UWB-module architecture <NUM>, in accordance with at least one embodiment. In the depicted embodiment, the seventh portion includes a channel impulse response (CIR) debug connector <NUM>, which is connected to the data link <NUM>. In some embodiments, the CIR debug connector <NUM> is used in connection with pins-of the above-described UWB IC <NUM> of <FIG>-that are used for SPI communication in order to access CIR data that the UWB IC <NUM> obtains. This CIR data can be used for analog debugging (e.g., analog performance debugging, null estimations, and/or the like) of ranging applications. The CIR is used to find the actual first path, i.e., the actual distance between two UWB devices (e.g., the UWB module <NUM> and the credential device <NUM>). It is further noted that the maximum detectable delta between first path and strongest path is known as the dynamic range. As such, the actual first path represents an important debugging parameter in connection with ranging applications.

<FIG> illustrates a block diagram of an example machine <NUM> upon which any one or more of the techniques (e.g., methodologies) discussed herein can perform. Examples, as described herein, can include, or can operate by, logic or a number of components, or mechanisms in the machine <NUM>. Circuitry (e.g., processing circuitry) is a collection of circuits implemented in tangible entities of the machine <NUM> that include hardware (e.g., simple circuits, gates, logic, etc.). Circuitry membership can be flexible over time. Circuitries include members that can, alone or in combination, perform specified operations when operating. In some examples, hardware of the circuitry can be immutably designed to carry out a specific operation (e.g., hardwired). In some examples, the hardware of the circuitry can include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.) including a machine readable medium physically modified (e.g., magnetically, electrically, moveable placement of invariant massed particles, etc.) to encode instructions of the specific operation. In connecting the physical components, the underlying electrical properties of a hardware constituent are changed, for example, from an insulator to a conductor or vice versa. The instructions enable embedded hardware (e.g., the execution units or a loading mechanism) to create members of the circuitry in hardware via the variable connections to carry out portions of the specific operation when in operation. Accordingly, in some examples, the machine readable medium elements are part of the circuitry or are communicatively coupled to the other components of the circuitry when the device is operating. In some examples, any of the physical components can be used in more than one member of more than one circuitry. For example, under operation, execution units can be used in a first circuit of a first circuitry at one point in time and reused by a second circuit in the first circuitry, or by a third circuit in a second circuitry at a different time. Additional examples of these components with respect to the machine <NUM> follow.

In some embodiments, the machine <NUM> can operate as a standalone device or can be connected (e.g., networked) to other machines. In a networked deployment, the machine <NUM> can operate in the capacity of a server machine, a client machine, or both in server-client network environments. In some examples, the machine <NUM> can act as a peer machine in peer-to-peer (P2P) (or other distributed) network environment. The machine <NUM> can be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine.

The machine (e.g., computer system) <NUM> can include a hardware processor <NUM> (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory <NUM>, a static memory (e.g., memory or storage for firmware, microcode, a basic-input-output (BIOS), unified extensible firmware interface (UEFI), etc.) <NUM>, and mass storage <NUM> (e.g., hard drives, tape drives, flash storage, or other block devices) some or all of which can communicate with each other via an interlink (e.g., bus) <NUM>. The machine <NUM> can further include a display unit <NUM>, an alphanumeric input device <NUM> (e.g., a keyboard), and a user interface (UI) navigation device <NUM> (e.g., a mouse). In some examples, the display unit <NUM>, input device <NUM> and UI navigation device <NUM> can be a touch screen display. The machine <NUM> can additionally include a storage device (e.g., drive unit) <NUM>, a signal generation device <NUM> (e.g., a speaker), a network interface device <NUM>, and one or more sensors <NUM>, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The machine <NUM> can include an output controller <NUM>, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

Registers of the processor <NUM>, the main memory <NUM>, the static memory <NUM>, or the mass storage <NUM> can be, or include, a machine readable medium <NUM> on which is stored one or more sets of data structures or instructions <NUM> (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions <NUM> can also reside, completely or at least partially, within any of registers of the processor <NUM>, the main memory <NUM>, the static memory <NUM>, or the mass storage <NUM> during execution thereof by the machine <NUM>. In some examples, one or any combination of the hardware processor <NUM>, the main memory <NUM>, the static memory <NUM>, or the mass storage <NUM> can constitute the machine readable media <NUM>. While the machine readable medium <NUM> is illustrated as a single medium, the term "machine readable medium" can include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions <NUM>.

The term "machine readable medium" can include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine <NUM> and that cause the machine <NUM> to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machine readable medium examples can include solid-state memories, optical media, magnetic media, and signals (e.g., radio frequency signals, other photon based signals, sound signals, etc.). In some examples, a non-transitory machine readable medium comprises a machine readable medium with a plurality of particles having invariant (e.g., rest) mass, and thus are compositions of matter. Accordingly, non-transitory machine-readable media are machine readable media that do not include transitory propagating signals. Specific examples of non-transitory machine readable media can include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

In some examples, information stored or otherwise provided on the machine readable medium <NUM> can be representative of the instructions <NUM>, such as instructions <NUM> themselves or a format from which the instructions <NUM> can be derived. This format from which the instructions <NUM> can be derived can include source code, encoded instructions (e.g., in compressed or encrypted form), packaged instructions (e.g., split into multiple packages), or the like. The information representative of the instructions <NUM> in the machine readable medium <NUM> can be processed by processing circuitry into the instructions to implement any of the operations discussed herein. For example, deriving the instructions <NUM> from the information (e.g., processing by the processing circuitry) can include: compiling (e.g., from source code, object code, etc.), interpreting, loading, organizing (e.g., dynamically or statically linking), encoding, decoding, encrypting, unencrypting, packaging, unpackaging, or otherwise manipulating the information into the instructions <NUM>.

In some examples, the derivation of the instructions <NUM> can include assembly, compilation, or interpretation of the information (e.g., by the processing circuitry) to create the instructions <NUM> from some intermediate or preprocessed format provided by the machine readable medium <NUM>. The information, when provided in multiple parts, can be combined, unpacked, and modified to create the instructions <NUM>. For example, the information can be in multiple compressed source code packages (or object code, or binary executable code, etc.) on one or several remote servers. The source code packages can be encrypted when in transit over a network and decrypted, uncompressed, assembled (e.g., linked) if necessary, and compiled or interpreted (e.g., into a library, stand-alone executable etc.) at a local machine, and executed by the local machine.

The instructions <NUM> can be further transmitted or received over a communications network <NUM> using a transmission medium via the network interface device <NUM> utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks can include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) <NUM> family of standards known as Wi-Fi®, IEEE <NUM> family of standards known as WiMax®), IEEE <NUM>. <NUM> family of standards, peer-to-peer (P2P) networks, among others. In some examples, the network interface device <NUM> can include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network <NUM>. In some examples, the network interface device <NUM> can include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques. The term "transmission medium" shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine <NUM>, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software. A transmission medium is a machine readable medium.

The above description includes references to the accompanying drawings, which form a part of the detailed description.

Claim 1:
A reader system (<NUM>) comprising an ultra-wide band, UWB, module (<NUM>) and a reader (<NUM>) of an access control system, the UWB module (<NUM>) being connectable to the reader (<NUM>) and comprising:
an antenna (428a);
a communication link (<NUM>) configured to interface with the reader (<NUM>);
a UWB front end circuit (<NUM>) connected to the antenna (428a) to facilitate UWB communication with a credential device (<NUM>);
a controller (<NUM>) connected to the UWB front end circuit (<NUM>) and configured to perform ranging for the credential device (<NUM>) using the UWB communication upon receipt of data associated with the credential device from the reader (<NUM>) over the communication link (<NUM>); and
a housing separate from a housing of the reader (<NUM>), the housing containing the antenna (428a), the UWB front end circuit (<NUM>), and the controller (<NUM>).