Embodiments of the present disclosure relate generally to access control systems and more specifically to embodiments of an ultra-wide band (UWB) device for access control systems.
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.
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.
Disclosed herein are embodiments of an ultra-wideband (UWB) module for 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 500 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.
A reader system 108 is positioned proximate to the handle 106 of the door 104. In an embodiment, the handle 106 has as its default state to be in the locked state. The reader system 108 is operable to selectively place the handle 106 in the unlocked state responsive to being presented with an authorized credential contained in a credential device 112, which can communicate with the reader system 108 via a wireless interface 110. In various different embodiments, the credential device 112 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 100 of
The server 208 could perform one or more functions for the reader system 108 such as authorization, authentication, and/or the like. In some embodiments, the reader system 108 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 208 could include a communication interface, a processor, and data storage containing instructions executable by the processor for carrying out the functions of the server 208.
The reader 302 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 302 could also include a processor and data storage containing instructions executable by the processor for carrying out the functions of the reader 302.
In some embodiments, the reader 302 was installed and in use prior to the UWB module 304 being connected as an add-on module. In other embodiments, the reader 302 and the UWB module 304 are installed together as (or as at least part of) the reader system 108. The UWB module 304 could be connected via the communication link 306 to an existing hardware port (or expansion port, expansion slot, or the like) of the reader 302. In some embodiments, the communication link 306 is or includes a data cable. Further detail regarding an example architecture of the UWB module 304 is provided below in connection with
In an example, a user carrying a credential device may approach the reader system 108. Upon the credential device coming into a threshold range of the reader system 108, 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 302, for example. The reader 302 may then establish a secret, such as a scrambled time stamp (STS), with the credential device to facilitate ranging using UWB communication. UWB ranging may be carried out using the UWB module 304, for example. This may occur upon receipt of data from the reader 302. 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 302 or the UWB module 304 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 302 may release the credential to allow access to the user.
The UWB module may include a battery 308 or other type of local power source including energy harvesters, capacitors, and the like. The battery 308 may be used to provide power for the UWB module 304 such that it is unnecessary for the UWB module 304 to receive power from the reader system 108, the door lock battery, or any other external power source. This can conserve power for the reader system 108 and may be advantageous as the it may be easier to replace a battery in the removeable UWB module 304 than any other battery in the reader system 108.
As a general matter, the reader 352 could be similar to the reader 302 of
The UWB module 402 includes a controller 426, antennas 428a and 428b, a battery 430, a secure element 432, and a UWB front end 434. The controller 426 may also be a BLE SoC microcontroller, or any other type of control circuit. The battery 430 may be used to provide power for the UWB module 402 so that the UWB module does not need to be powered by the reader power, lock power, or any other power source. The controller 426 may be capable of UWB communication through the UWB front end 434, 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 432 may be configured to cache secure data such as an STS, PACS ID, and the like. The components of the UWB modules 402 may be described in further detail with respect to
In an example, a user carrying a credential device may approach the reader 400. Upon the credential device coming into a threshold range of the reader system 108, the controller 406 may exchange a credential with the credential device using BLE through the antenna 408b. The controller 406 may then establish a secret, such as a scrambled time stamp (STS), with the credential device to facilitate ranging using UWB communication. UWB ranging may be carried out by the controller 426 of the UWB module 402, for example. This may occur upon receipt of data from the controller 406. 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 406 and 426 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 406 may release the credential to allow access to the user.
Also included is a third step down regulator (6-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®8607 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 504 that is connected to input voltage Vusb and to ground, and that is further connected to a data link 505. In an embodiment, Wi-fi functionality is not powered by USB, and USB only powers BLE and UWB circuits.
The ESP32 WROOM extension connector 522 could provide a connection option to an ESP32 module designed for Wi-fi connectivity, and could be configured to operate at up to a 500 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 506 could be the NRF52840, manufactured by Nordic Semiconductor®, which is headquartered in Trondheim, Norway. In an embodiment, the BLE SoC 506 includes at least one onboard antenna. In at least one embodiment, the BLE SoC 506 is the core microcontroller for the UWB module having the example architecture 500. In some embodiments, both the reader and the UWB module (a.k.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 506 in at least one assignment is shown in Table 1 at the end of this detailed description.
The BLE SoC 506 is connected to both input voltage 3V3 and a 32 MHz crystal oscillator, and is also connected to the data link 505, as well as to a data link 507, a data link 508, a data link 509, a data link 510, a data link 511, a data link 512, a data link 513, a data link 514, a data link 515, and a data link 516. The data link 507 is connected to both an optional display and to the RevE expansion debug pinheader 517, which in turn is connected via a data link 518 to the RevE expansion connector 519. The UWB module can be powered via the RevE expansion connector 519 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 508 is connected to the general debug pinheader 520, which in turn is connected via a data link 521 to the ESP32 Wroom extension connector 522. The RevE expansion connector 519 is connected to both input voltage Vinreader and to ground, whereas the ESP32 Wroom extension connector 522 is connected to both input voltage 5Vwi-fi and to ground.
In the depicted embodiment, the third portion 500C also includes a secure element 524, an embedded video engine 526, a backlight driver 530, and a display connector 528. As indicated by a board/printed circuit board (PCB) boundary 525, the secure element 524 could be or could reside on a PCB that is separate from a main board of the UWB-module architecture 500. The data link 510 is connected to both the secure element 524 and the embedded video engine 526. The secure element 524 could be or include a secure access module (SAM). In an embodiment, the secure element 524 is an ST33 ARM SC300 secure microcontroller manufactured by STMicroelectronics®, which is headquartered in Geneva, Switzerland.
The embedded video engine 526 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 526 on the board helps to unload the main microcontroller (i.e., the BLE SoC 506). The embedded video engine 526 could be wired to drive an external display in RGB mode, and to control the backlight driver 530. The embedded video engine 526 is connected to input voltage 3V3, and also by a data link 529 to the backlight driver 530 and by a data link 527 to the display controller 528. The backlight driver 530 is connected to the display controller 528 by a data link 531. In the depicted embodiment, the backlight driver 530 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 530 is used to control a display backlight. A shutdown pin of the backlight driver 530 is controlled in an embodiment by the embedded video engine 526 via a pulse width modulation (PWM), to allow for dimming.
The display connector 528 is further connected to input voltage 3V3, and with the BLE SoC 506 via a data link 532. The display connector 528 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 528 could be a dedicated flat flex connector (FFC). In an embodiment, the supported display is 2.4″ in size with 320×240 pixel resolution. A supported display could use an ILI9341 controller form ILI Technology® Corporation of Taiwan.
The JTAG connector 533 could be the FTSH-105-01-F-DV-K, manufactured by Samtec®, Inc., headquartered in New Albany, Indiana. The JTAG connector 533 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 use used optionally to trace data. JTAG pins and SW pins are shared. In an embodiment, with respect to the pins of the JTAG connector 533, 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 500 that is described herein.
The first level shifter 536 could be a TXB0108 8-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 536. This allows for both the SE 542 and the below-described UWB IC 551 of
The second level shifter 539 could include both a TXB0108 8-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 2-bit bidirectional I2C level shifter. In an embodiment, the PCA9306DCUR is used for the I2C interface to the SE 542. The second level shifter 539 is connected to the data link 513 and also to a data link 540, which is in turn connected to both the NXP SE debug connector 541 and the NXP secure element (SE) 542. In an embodiment, the NXP SE debug connector 541 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 536 and the second level shifter 539 are used because the below-described UWB IC 551 of
The SE 542 is connected via a data link 544 to the SE SPI pinheader 543, which itself is also connected to input voltage 1V8 and to ground. In addition to being connected to the SE SPI pinheader 543 via the data link 544 and to both the second level shifter 539 and the NXP SE debug connector 541 via the data link 540, the SE 542 is also connected to input voltage 3V3, input voltage 1V8, and a data link 545. In an embodiment, the SE 542 supports secure ranging. The SE 542 could be a Java Card SE with an NFC front end. In at least one embodiment, the SE 542 is the SN110U, which is a single chip secure element and NFC controller manufactured by NXP Semiconductors® N.V., 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.
In at least one embodiment, the UWB 551 can be an SR100T, which is a secure fine ranging chipset that, like the SN110U that can be used as the SE 542, is manufactured by NXP Semiconductors® N.V. In an embodiment, the SR100T is a fully integrated single chip Impulse Radio Ultra-Wideband (IR-UWB) low-energy transceiver IC, compliant with IEEE 802.15.4 HRP UWB PHY. It is designed for secure ranging applications in a mobile environment. It supports super high frequency (SHF) UWB bands from 6.0 GHz to 8.5 GHz for worldwide use. It has a programmable transmitter output power of up to 12 dBm, 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 1.8V+/−7%.
The SR100T also supports angle of arrival (AoA) measurement, and has integrated I/Q phase and amplitude mismatch compensation. Its form factor is a 3.8 mm×3.1 mm 68-pin Wafer Level Chip Scale Package (WLCSP) package with 0.35 mm pitch. It includes an ARM® Cortex-M33 32 Bit processor having 128 kB code RAM, 128 kB data RAM, 64 kB ROM, and ARM® TrustZone technology and S-DMA for security. The SR100T further has a BSP32 CoolFlux SubSystem having a 200 MHz clock, 32 kB code RAM, and 2×16 kB data RAM. The SR100T also has a hardwired DSP for the first receive data link 566, the second received data link 556, and the transmission data link 552; operating frequencies of 250 MHz, 500 MHz, and 1000 MHz; 2×4 kB RAM for channel estimators, and 4×32 kB RAM for RF data log.
As depicted in
The UWB IC 551 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 558, the first SAW bandpass filter 560, the second matching circuit 562, and the first antenna port 564. The second RF pipeline includes the second RF switch 567, the second SAW bandpass filter 569, the third matching circuit 571, and the second antenna port 574.
In the depicted embodiment, the UWB IC 551 is connected to the first matching circuit 553 via the transmission data link 552, which also connects the UWB IC 551 with the first RF switch 558. The first matching circuit 553 in turn is connected via a data link 554 to the radar port 555, 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 551 is connected via the transmission data link 552 to the first RF switch 558. The UWB IC 551 is also connected to the first RF switch 558 via the second receive data link 556 and the data link 557. The first RF switch 558, which is further connected to input voltage 1V8RF, could be an XMSSJR6G0BA, which is manufactured by Murata® Manufacturing Company, Ltd., which is headquartered in Kyoto, Japan. The first RF switch 558 is in turn connected via a data link 559 to the first SAW bandpass filter 560, which is in turn connected via a data link 561 to the second matching circuit 562. The second matching circuit 562 is in turn connected via a data link 563 to the first antenna port 563, which in at least one embodiment is in turn connected to a first external UWB antenna.
In the second RF pipeline, the UWB IC 551 is connected to the second RF switch 567 via the data link 565 and also via the first receive data link 566. The UWB IC 551 is also connected to input voltage 1V8RF and to ground. The second RF switch could also be an XMSSJR6G0BA. The second RF switch 567 is in turn connected via a data link 568 to the second SAW bandpass filter 569, which is in turn connected via a data link 570 to the third matching circuit 571. The third matching circuit 571 is in turn connected via a data link 572 to the second antenna port 574, 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 500, 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
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 555 that can be connected to a radar antenna, the first antenna port 564 that can be connected to a first external UWB antenna, the second antenna port 574 that can be connected to a second external UWB antenna, and the third antenna port 548 that can be connected to the (external) BLE antenna 550. U.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.
In some embodiments, the machine 600 can operate as a standalone device or can be connected (e.g., networked) to other machines. In a networked deployment, the machine 600 can operate in the capacity of a server machine, a client machine, or both in server-client network environments. In some examples, the machine 600 can act as a peer machine in peer-to-peer (P2P) (or other distributed) network environment. The machine 600 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. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations.
The machine (e.g., computer system) 600 can include a hardware processor 602 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 604, a static memory (e.g., memory or storage for firmware, microcode, a basic-input-output (BIOS), unified extensible firmware interface (UEFI), etc.) 606, and mass storage 608 (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) 630. The machine 600 can further include a display unit 610, an alphanumeric input device 612 (e.g., a keyboard), and a user interface (UI) navigation device 614 (e.g., a mouse). In some examples, the display unit 610, input device 612 and UI navigation device 614 can be a touch screen display. The machine 600 can additionally include a storage device (e.g., drive unit) 608, a signal generation device 618 (e.g., a speaker), a network interface device 620, and one or more sensors 616, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The machine 600 can include an output controller 628, 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 602, the main memory 604, the static memory 606, or the mass storage 608 can be, or include, a machine readable medium 622 on which is stored one or more sets of data structures or instructions 624 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 624 can also reside, completely or at least partially, within any of registers of the processor 602, the main memory 604, the static memory 606, or the mass storage 608 during execution thereof by the machine 600. In some examples, one or any combination of the hardware processor 602, the main memory 604, the static memory 606, or the mass storage 608 can constitute the machine readable media 622. While the machine readable medium 622 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 624.
The term “machine readable medium” can include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 600 and that cause the machine 600 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 622 can be representative of the instructions 624, such as instructions 624 themselves or a format from which the instructions 624 can be derived. This format from which the instructions 624 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 624 in the machine readable medium 622 can be processed by processing circuitry into the instructions to implement any of the operations discussed herein. For example, deriving the instructions 624 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 624.
In some examples, the derivation of the instructions 624 can include assembly, compilation, or interpretation of the information (e.g., by the processing circuitry) to create the instructions 624 from some intermediate or preprocessed format provided by the machine readable medium 622. The information, when provided in multiple parts, can be combined, unpacked, and modified to create the instructions 624. 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 624 can be further transmitted or received over a communications network 626 using a transmission medium via the network interface device 620 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) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, peer-to-peer (P2P) networks, among others. In some examples, the network interface device 620 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 626. In some examples, the network interface device 620 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 600, 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. The drawings show, by way of illustration, specific embodiments in which the invention can be practiced. These embodiments are also referred to herein as “examples.” Such examples can include elements in addition to those shown or described. However, the present inventors also contemplate examples in which only those elements shown or described are provided. Moreover, the present inventors also contemplate examples using any combination or permutation of those elements shown or described (or one or more aspects thereof), either with respect to a particular example (or one or more aspects thereof), or with respect to other examples (or one or more aspects thereof) shown or described herein.
In this document, the terms “a” or “an” are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of “at least one” or “one or more.” In this document, the term “or” is used to refer to a nonexclusive or, such that “A or B” includes “A but not B,” “B but not A,” and “A and B,” unless otherwise indicated. In this document, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein.” Also, in the following claims, the terms “including” and “comprising” are open-ended, that is, a system, device, article, composition, formulation, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms “first,” “second,” and “third,” etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.
The above description is intended to be illustrative, and not restrictive. For example, the above-described examples (or one or more aspects thereof) may be used in combination with each other. Other embodiments can be used, such as by one of ordinary skill in the art upon reviewing the above description. The Abstract is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Also, in the above Detailed Description, various features may be grouped together to streamline the disclosure. This should not be interpreted as intending that an unclaimed disclosed feature is essential to any claim. Rather, inventive subject matter may lie in less than all features of a particular disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description as examples or embodiments, with each claim standing on its own as a separate embodiment, and it is contemplated that such embodiments can be combined with each other in various combinations or permutations. The scope of the invention should be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.
This application is a national stage application under 35 U.S.C. § 371 of PCT Appl. No. PCT/EP2020/058201, titled “Ultra-Wide Band Device for Access Control Reader System,” filed Mar. 24, 2020, which claims priority to U.S. Prov. Pat. Appl. No. 62/906,995, titled “Ultra-Wide Band Module for Physical Access Control System,” filed Sep. 27, 2019, and to U.S. Prov. Pat. Appl. No. 62/823,341, titled “Physical Access Control Systems with Localization-Based Intent Detection,” filed Mar. 25, 2019, each of which is hereby incorporated by reference herein in its entirety.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/EP2020/058201 | 3/24/2020 | WO |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2020/193570 | 10/1/2020 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
7446644 | Schaffzin | Nov 2008 | B2 |
7499674 | Salokannel et al. | Mar 2009 | B2 |
7597250 | Finn | Oct 2009 | B2 |
7756002 | Batra et al. | Jul 2010 | B2 |
7881746 | Desai | Feb 2011 | B2 |
7995644 | Sahinoglu et al. | Aug 2011 | B2 |
8001055 | Weiss | Aug 2011 | B2 |
8355671 | Kramer et al. | Jan 2013 | B2 |
8430310 | Ho | Apr 2013 | B1 |
8478360 | Soliman | Jul 2013 | B2 |
8736438 | Vasquez et al. | May 2014 | B1 |
8913599 | Gonikberg et al. | Dec 2014 | B2 |
9007173 | Mcintyre et al. | Apr 2015 | B2 |
9058702 | Chao | Jun 2015 | B2 |
9357381 | Cho et al. | May 2016 | B2 |
9367978 | Sullivan | Jun 2016 | B2 |
9408147 | Polo et al. | Aug 2016 | B2 |
9485607 | Aarnio | Nov 2016 | B2 |
9501884 | Mcintyre et al. | Nov 2016 | B2 |
9530265 | Lee et al. | Dec 2016 | B2 |
9666005 | Ellis et al. | May 2017 | B2 |
9721404 | Muller | Aug 2017 | B2 |
9769627 | Siswick et al. | Sep 2017 | B2 |
9830443 | Mutz | Nov 2017 | B2 |
9942849 | Hariharan et al. | Apr 2018 | B1 |
10117046 | Ledvina et al. | Oct 2018 | B2 |
10152837 | Mallard | Dec 2018 | B1 |
10171129 | Hammerschmidt et al. | Jan 2019 | B1 |
10182309 | Mahasenan | Jan 2019 | B2 |
10228444 | Jonsson | Mar 2019 | B2 |
10229548 | Daniel-Wayman | Mar 2019 | B2 |
10235854 | Trani | Mar 2019 | B2 |
10356553 | Sant et al. | Jul 2019 | B2 |
10486646 | Ledvina et al. | Nov 2019 | B2 |
10567034 | Hammerschmidt et al. | Feb 2020 | B2 |
10602556 | Foster et al. | Mar 2020 | B2 |
10652925 | Naguib et al. | May 2020 | B2 |
10660037 | Hariharan et al. | May 2020 | B2 |
10728244 | Trani | Jul 2020 | B2 |
10759389 | Ledvina et al. | Sep 2020 | B2 |
10819029 | Amiri et al. | Oct 2020 | B2 |
11100734 | Ahn | Aug 2021 | B2 |
11164411 | Kuenzi | Nov 2021 | B2 |
11237243 | Jonsson | Feb 2022 | B2 |
11295563 | Kuenzi | Apr 2022 | B2 |
11405784 | Pirch | Aug 2022 | B2 |
11770708 | Pirch et al. | Sep 2023 | B2 |
20030204742 | Gupta et al. | Oct 2003 | A1 |
20030232620 | Runkle et al. | Dec 2003 | A1 |
20040250074 | Kilian-Kehr | Dec 2004 | A1 |
20070149123 | Palin | Jun 2007 | A1 |
20070149124 | Onozawa | Jun 2007 | A1 |
20070288995 | Terada et al. | Dec 2007 | A1 |
20100034375 | Davis et al. | Feb 2010 | A1 |
20110187493 | Elfstroem et al. | Aug 2011 | A1 |
20120266221 | Castelluccia et al. | Oct 2012 | A1 |
20130217332 | Altman et al. | Aug 2013 | A1 |
20130225080 | Doss et al. | Aug 2013 | A1 |
20130237148 | McCann | Sep 2013 | A1 |
20130287211 | Rhelimi | Oct 2013 | A1 |
20140070003 | Radicella | Mar 2014 | A1 |
20140229385 | Neafsey | Aug 2014 | A1 |
20140298398 | Neely | Oct 2014 | A1 |
20140342667 | Aarnio | Nov 2014 | A1 |
20140355582 | Kamath et al. | Dec 2014 | A1 |
20150029010 | Wisnia | Jan 2015 | A1 |
20150200706 | Bottazzi et al. | Jul 2015 | A1 |
20150200925 | Lagerstedt et al. | Jul 2015 | A1 |
20150310681 | Avery et al. | Oct 2015 | A1 |
20150332532 | Lee et al. | Nov 2015 | A1 |
20160055692 | Trani | Feb 2016 | A1 |
20160086406 | Baumgarte | Mar 2016 | A1 |
20160147988 | Mutz et al. | May 2016 | A1 |
20160234008 | Hekstra et al. | Aug 2016 | A1 |
20160241559 | Trani et al. | Aug 2016 | A1 |
20160241999 | Chin et al. | Aug 2016 | A1 |
20160248782 | Troesch | Aug 2016 | A1 |
20160267760 | Trani | Sep 2016 | A1 |
20160278006 | Lee et al. | Sep 2016 | A1 |
20160316500 | Aliyar | Oct 2016 | A1 |
20160353233 | Yong | Dec 2016 | A1 |
20160358394 | Konicek et al. | Dec 2016 | A1 |
20160360341 | Srivatsa et al. | Dec 2016 | A1 |
20170004665 | Chang et al. | Jan 2017 | A1 |
20170019765 | Hoyer et al. | Jan 2017 | A1 |
20170053467 | Meganck et al. | Feb 2017 | A1 |
20170070919 | Verger et al. | Mar 2017 | A1 |
20170074000 | Banvait | Mar 2017 | A1 |
20170151918 | Boesen | Jun 2017 | A1 |
20170153636 | Boesen | Jun 2017 | A1 |
20170158202 | Yang | Jun 2017 | A1 |
20170228953 | Lupovici | Aug 2017 | A1 |
20170232930 | Murar et al. | Aug 2017 | A1 |
20170236346 | Murar et al. | Aug 2017 | A1 |
20170236351 | Menard et al. | Aug 2017 | A1 |
20170301166 | Earles et al. | Oct 2017 | A1 |
20170303084 | Brückner | Oct 2017 | A1 |
20170330226 | Kuenzi et al. | Nov 2017 | A1 |
20170359689 | Chhabra et al. | Dec 2017 | A1 |
20180081025 | Jonsson et al. | Mar 2018 | A1 |
20180144563 | Reymann | May 2018 | A1 |
20180162321 | Spiess | Jun 2018 | A1 |
20180225898 | Kirkland et al. | Aug 2018 | A1 |
20180234797 | Ledvina et al. | Aug 2018 | A1 |
20180310159 | Katz et al. | Oct 2018 | A1 |
20180315262 | Love | Nov 2018 | A1 |
20190051072 | Okada | Feb 2019 | A1 |
20190052314 | Caruana | Feb 2019 | A1 |
20190061686 | Neuhoff et al. | Feb 2019 | A1 |
20190073846 | Kamkar et al. | Mar 2019 | A1 |
20190097317 | Di Nallo et al. | Mar 2019 | A1 |
20190098499 | Lerch et al. | Mar 2019 | A1 |
20190116619 | Hauck et al. | Apr 2019 | A1 |
20190135229 | Ledvina et al. | May 2019 | A1 |
20190266822 | Ruggieri | Aug 2019 | A1 |
20200053689 | Mcqueen et al. | Feb 2020 | A1 |
20200106877 | Ledvina et al. | Apr 2020 | A1 |
20200150261 | Naguib et al. | May 2020 | A1 |
20200168017 | Prostko et al. | May 2020 | A1 |
20200238952 | Lindsay et al. | Jul 2020 | A1 |
20200259522 | Hammerschmidt et al. | Aug 2020 | A1 |
20200259896 | Sachs et al. | Aug 2020 | A1 |
20200314651 | Pirch et al. | Oct 2020 | A1 |
20200320188 | Graff et al. | Oct 2020 | A1 |
20200349785 | Kuenzi et al. | Nov 2020 | A1 |
20200351781 | Hariharan et al. | Nov 2020 | A1 |
20210142600 | Tiwari et al. | May 2021 | A1 |
20210352608 | Chun et al. | Nov 2021 | A1 |
20210383624 | Hoyer et al. | Dec 2021 | A1 |
20220157106 | Pirch et al. | May 2022 | A1 |
20220172529 | Pirch et al. | Jun 2022 | A1 |
20220172536 | Pirch et al. | Jun 2022 | A1 |
20220189224 | Pirch | Jun 2022 | A1 |
20220189228 | Pirch et al. | Jun 2022 | A1 |
20220189229 | Pirch et al. | Jun 2022 | A1 |
20220191700 | Jung et al. | Jun 2022 | A1 |
20220377555 | Pirch et al. | Nov 2022 | A1 |
Number | Date | Country |
---|---|---|
2018389642 | May 2020 | AU |
2020249420 | Jan 2023 | AU |
2020249424 | Mar 2023 | AU |
2020249425 | Mar 2023 | AU |
2019373730 | Apr 2023 | AU |
2020247109 | Jun 2023 | AU |
2020247388 | Jun 2023 | AU |
2020247386 | Jul 2023 | AU |
101133343 | Feb 2008 | CN |
102150448 | Aug 2011 | CN |
202703516 | Jan 2013 | CN |
103544746 | Jan 2014 | CN |
104063930 | Sep 2014 | CN |
104620552 | May 2015 | CN |
104661308 | May 2015 | CN |
105723043 | Jun 2016 | CN |
105931326 | Sep 2016 | CN |
107206966 | Sep 2017 | CN |
107730663 | Feb 2018 | CN |
108475447 | Aug 2018 | CN |
108701177 | Oct 2018 | CN |
108701382 | Oct 2018 | CN |
108778855 | Nov 2018 | CN |
109074618 | Dec 2018 | CN |
109076487 | Dec 2018 | CN |
111738377 | Oct 2020 | CN |
111738378 | Oct 2020 | CN |
113039823 | Jun 2021 | CN |
113614559 | Nov 2021 | CN |
113614797 | Nov 2021 | CN |
113614798 | Nov 2021 | CN |
113631947 | Nov 2021 | CN |
113678014 | Nov 2021 | CN |
116071857 | May 2023 | CN |
113614798 | Aug 2023 | CN |
102017110144 | Oct 2018 | DE |
2355050 | Aug 2011 | EP |
2706720 | Mar 2014 | EP |
2617242 | Oct 2016 | EP |
3101874 | Dec 2016 | EP |
3118820 | Jan 2017 | EP |
3355281 | Aug 2018 | EP |
3376475 | Sep 2018 | EP |
3928111 | Dec 2021 | EP |
202117041715 | Dec 2021 | IN |
202117042210 | Dec 2021 | IN |
202117019181 | Jan 2022 | IN |
202117041276 | Aug 2022 | IN |
202117041409 | Sep 2022 | IN |
202117041414 | Sep 2022 | IN |
202117041712 | Sep 2022 | IN |
202117041714 | Sep 2022 | IN |
H02186082 | Jul 1990 | JP |
2002334361 | Nov 2002 | JP |
2005320742 | Nov 2005 | JP |
2007066107 | Mar 2007 | JP |
2007102405 | Apr 2007 | JP |
2007316980 | Dec 2007 | JP |
2008205548 | Sep 2008 | JP |
2009075010 | Apr 2009 | JP |
2009127284 | Jun 2009 | JP |
2010079609 | Apr 2010 | JP |
2010126898 | Jun 2010 | JP |
2010226246 | Oct 2010 | JP |
2010277557 | Dec 2010 | JP |
2012511761 | May 2012 | JP |
2015090583 | May 2015 | JP |
2015106266 | Jun 2015 | JP |
2015227594 | Dec 2015 | JP |
2016094801 | May 2016 | JP |
2017029701 | Feb 2017 | JP |
6205237 | Sep 2017 | JP |
2017538875 | Dec 2017 | JP |
6419202 | Oct 2018 | JP |
2018178506 | Nov 2018 | JP |
2018206355 | Dec 2018 | JP |
2018537017 | Dec 2018 | JP |
2019528387 | Oct 2019 | JP |
2020510567 | Apr 2020 | JP |
2022506040 | Jan 2022 | JP |
2022526155 | May 2022 | JP |
2022526335 | May 2022 | JP |
2022526336 | May 2022 | JP |
2022526337 | May 2022 | JP |
2022527064 | May 2022 | JP |
2022527065 | May 2022 | JP |
2022528637 | Jun 2022 | JP |
7213967 | Jan 2023 | JP |
7225431 | Feb 2023 | JP |
7228056 | Feb 2023 | JP |
7241909 | Mar 2023 | JP |
2023054074 | Apr 2023 | JP |
2023071643 | May 2023 | JP |
2023071680 | May 2023 | JP |
2023080067 | Jun 2023 | JP |
101077406 | Oct 2011 | KR |
20170040240 | Apr 2017 | KR |
20170140367 | Dec 2017 | KR |
20180087429 | Aug 2018 | KR |
20190023713 | Mar 2019 | KR |
PA03010049 | Dec 2004 | MX |
2021011587 | Jul 2023 | MX |
WO-2013178163 | Dec 2013 | WO |
WO-2014016695 | Jan 2014 | WO |
WO-2016007627 | Jan 2016 | WO |
WO-2016059451 | Apr 2016 | WO |
WO-2016089837 | Jun 2016 | WO |
2017058925 | Apr 2017 | WO |
WO-2017136725 | Aug 2017 | WO |
WO-2017144345 | Aug 2017 | WO |
WO-2017181132 | Oct 2017 | WO |
WO-2018071671 | Apr 2018 | WO |
2018091660 | May 2018 | WO |
WO-2018148687 | Aug 2018 | WO |
WO-2019016599 | Jan 2019 | WO |
WO-2019224329 | Nov 2019 | WO |
2020089484 | May 2020 | WO |
WO-2020193566 | Oct 2020 | WO |
WO-2020193568 | Oct 2020 | WO |
WO-2020193570 | Oct 2020 | WO |
WO-2020193576 | Oct 2020 | WO |
WO-2020193577 | Oct 2020 | WO |
WO-2020193578 | Oct 2020 | WO |
WO-2020193580 | Oct 2020 | WO |
Entry |
---|
U.S. Appl. No. 17/309,102, filed Apr. 23, 2021, Systems, Methods, and Devices for Access Control. |
U.S. Appl. No. 16/828,001, filed Mar. 24, 2020, Physical Access Control Systems With Localization-Based Intent Detection. |
U.S. Appl. No. 17/593,174, filed Sep. 10, 2021, Ultra-Wide Band Device for Access Control Reader System. |
U.S. Appl. No. 17/593,336, filed Sep. 15, 2021, Reader Coordination for Access Control. |
U.S. Appl. No. 17/593,338, filed Sep. 15, 2021, Physical Access Control Systems With Localization-Based Intent Detection. |
U.S. Appl. No. 17/593,340, filed Sep. 15, 2021, Physical Access Control Systems With Localization-Based Intent Detection. |
U.S. Appl. No. 17/593,342, filed Sep. 15, 2021, Physical Access Control Systems With Localization- Based Intent Detection. |
“International Application Serial No. PCT/EP2019/080113, International Search Report dated Feb. 7, 2020”, 4 pgs. |
“International Application Serial No. PCT/EP2019/080113, Written Opinion dated Feb. 7, 2020”, 5 pgs. |
“U.S. Appl. No. 17/309,102, Preliminary Amendment Filed Apr. 23, 2021”, 8 pgs. |
“International Application Serial No. PCT/EP2019/080113, International Preliminary Report on Patentability dated May 14, 2021”, 7 pgs. |
“U.S. Appl. No. 17/593,174 Preliminary Amendment filed Sep. 10, 2021”, 7 pgs. |
“U.S. Appl. No. 17/593,336 Preliminary Amendment filed Sep. 15, 2021”, 8 pgs. |
“U.S. Appl. No. 17/593,338 Preliminary Amendment filed Sep. 15, 2021”, 6 pgs. |
“U.S. Appl. No. 17/593,340 Preliminary Amendment filed Sep. 15, 2021”, 7 pgs. |
“International Application Serial No. PCT/EP2020/058210, International Preliminary Report on Patentability dated Oct. 7, 2021”, 15 pgs. |
“International Application Serial No. PCT/EP2020/058197, International Preliminary Report on Patentability dated Oct. 7, 2021”, 10 pgs. |
“International Application Serial No. PCT/EP2020/058201, International Preliminary Report on Patentability dated Oct. 7, 2021”, 10 pgs. |
“International Application Serial No. PCT/EP2020/058221, International Preliminary Report on Patentability dated Oct. 7, 2021”, 12 pgs. |
“International Application Serial No. PCT/EP2020/058199, International Preliminary Report on Patentability dated Sep. 28, 2021”, 8 pgs. |
“International Application Serial No. PCT/EP2020/058216, International Preliminary Report on Patentability dated Sep. 28, 2021”, 9 pgs. |
“International Application Serial No. PCT/EP2020/058218, International Preliminary Report on Patentability dated Sep. 28, 2021”, 7 pgs. |
“U.S. Appl. No. 16/828,001, Non Final Office Action dated Feb. 17, 2022”, 10 pgs. |
“Indian Application Serial No. 202117041715, First Examination Report dated Mar. 15, 2022”, w/ English Translation, 8 pgs. |
“Indian Application Serial No. 202117042210, First Examination Report dated Mar. 17, 022”, w/ English Translation, 5 pgs. |
“European Application Serial No. 20714984.0, Response filed Mar. 30, 2022 Communication Pursuant to Rules 161(1) and 162 EPC dated Sep. 30, 2021”, 40 pgs. |
“European Application Serial No. 20714986.5, Response filed Apr. 12, 2022 Communication Pursuant to Rule 161(1) and 162 EPC dated Oct. 5, 2021”, 30 pgs. |
“European Application Serial No. 20714545.9, Response filed Apr. 12, 2022 to Communication Pursuant to Rule 161(1) and 162 EPC dated Oct. 5, 2021”, 77 pgs. |
“European Application Serial No. 20714987.3, Response filed Apr. 12, 2022 to Communication Pursuant to Rules 161(1) and 162 EPC dated Oct. 5, 2021”, 78 pgs. |
“European Application Serial No. 20714985.7, Response filed Apr. 12, 2022 to Communication Pursuant to Rules 161(1) and 162 EPC dated Oct. 5, 2021”, 18 pgs. |
“European Application Serial No. 20714988.1, Response Filed Apr. 11, 2022 to Communication pursuant to Rules 161(1) and 162 EPC Filed Oct. 5, 2021”, 20 pgs. |
“U.S. Appl. No. 16/828,001, Response filed May 16, 2022 to Non Final Office Action dated Feb. 17, 2022”, 13 pgs. |
“Google: core/java/android/companion/BluetoothLeDeviceFilter.java—platform/frameworks/base—Git at Google”, Android Core Code, Bluetooth Companion, [Online] Retrieved from the Internet: <https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/companion/BluetoothLeDeviceFilter.java>, (Jan. 1, 2017), 9 pgs. |
“International Application Serial No. PCT/EP2020/058197, International Search Report dated Jul. 28, 2020”, 5 pgs. |
“International Application Serial No. PCT/EP2020/058197, Written Opinion dated Jul. 28, 2020”, 8 pgs. |
“International Application Serial No. PCT/EP2020/058199, International Search Report dated Jun. 8, 2020”, 5 pgs. |
“International Application Serial No. PCT/EP2020/058199, Written Opinion dated Jun. 8, 2020”, 7 pgs. |
“International Application Serial No. PCT/EP2020/058201, International Search Report dated Jun. 26, 2020”, 5 pgs. |
“International Application Serial No. PCT/EP2020/058201, Written Opinion dated Jun. 26, 2020”, 8 pgs. |
“International Application Serial No. PCT/EP2020/058210, International Search Report dated Jun. 29, 2020”, 4 pgs. |
“International Application Serial No. PCT/EP2020/058210, Written Opinion dated Jun. 29, 2020”, 13 pgs. |
“International Application Serial No. PCT/EP2020/058216, International Search Report dated Jun. 26, 2020”, 5 pgs. |
“International Application Serial No. PCT/EP2020/058216, Written Opinion dated Jun. 26, 2020”, 8 pgs. |
“International Application Serial No. PCT/EP2020/058218, International Search Report dated Jun. 15, 2020”, 5 pgs. |
“International Application Serial No. PCT/EP2020/058218, Written Opinion dated Jun. 15, 2020”, 6 pgs. |
“International Application Serial No. PCT/EP2020/058221, International Search Report dated Jun. 29, 2020”, 5 pgs. |
“International Application Serial No. PCT/EP2020/058221, Written Opinion dated Jun. 29, 2020”, 10 pgs. |
“European Application Serial No. 19801788.1, Response to Communication pursuant to Rules 161(1) and 162 EPC filed Nov. 24, 2021”, 18 pgs. |
“European Application Serial No. 21210676.9, Extended European Search Report dated Jan. 14, 2022”, 7 pgs. |
“Indian Application Serial No. 202117019181, First Examination Report dated Feb. 22, 2022”, w/ English Translation, 9 pgs. |
“Indian Application Serial No. 202117019181, First Examination Report dated Feb. 22, 2022”, w/ English translation, 7 pgs. |
“Australian Application Serial No. 2019373730, First Examination Report dated Apr. 11, 2022”, 4 pgs. |
“Canadian Application Serial No. 3,070,588, Non Final Office Action dated May 12, 2022”, 4 pgs. |
“U.S. Appl. No. 16/828,001, Notice of Allowance dated Jun. 8, 2022”, 10 pgs. |
“Australian Application Serial No. 2020247109, First Examination Report dated Jun. 21, 2022”, 3 pgs. |
“Australian Application Serial No. 2020249424, First Examination Report dated Jul. 7, 2022”, 3 pgs. |
“Australian Application Serial No. 2020249420, First Examination Report dated Jul. 12, 2022”, 3 pgs. |
“Application Serial No. 17 812,426, Preliminary Amendment Filed Jul. 13, 2022”, 12 pgs. |
“Japanese Application Serial No. 2021-523189, Notification of Reasons for Refusal dated Jul. 12, 2022”, w/ English translation, 14 pgs. |
“Australian Application Serial No. 2020249425, First Examination Report dated Jul. 20, 2022”, 3 pgs. |
“Australian Application Serial No. 2020247388, First Examination Report dated Jul. 26, 2022”, 3 pgs. |
“Indian Application Serial No. 202117041276, First Examination Report dated Aug. 29, 2022”, w/ English Translation, 5 pgs. |
“European Application Serial No. 21210676.9, Voluntary Amendment filed on Aug. 4, 2022”, 11 pgs. |
“Indian Application Serial No. 202117041414, First Examination Report dated Sep. 5, 2022”, w/ English Translation, 6 pgs. |
“Indian Application Serial No. 202117041409, First Examination Report dated Sep. 7, 2022”, w/ English Translation, 6 pgs. |
“Indian Application Serial No. 202117019181, Response filed Aug. 22, 2022 to First Examination Report dated Feb. 22, 2022”, W/ English Claims, 22 pgs. |
“Indian Application Serial No. 202117041714, First Examination Report dated Sep. 7, 2022”, w/ English Translation, 8 pgs. |
“Indian Application Serial No. 202117041712, First Examination Report dated Sep. 8, 2022”, w/ English Translation, 5 pgs. |
“Australian Application Serial No. 2019373730, Response Filed Aug. 26, 22 to First Examination Report dated Apr. 11, 2022”, 15 pgs. |
“Canadian Application Serial No. 3,070,588, Response Filed Sep. 8, 2022 to Non Final Office Action dated May 12, 2022”, 15 pgs. |
“Indian Application Serial No. 202117041715, Response Filed Sep. 9, 22 to First Examination Report dated Mar. 15, 2022”, W/ English Claims, 9 pgs. |
“Indian Application Serial No. 202117041715, Voluntary Amendment Filed Sep. 15, 2022”, 70 pgs. |
“Indian Application Serial No. 202117042210, Voluntary Amendment Filed Sep. 15, 2022”, W/ English Claims, 12 pgs. |
“Indian Application Serial No. 202117042210, Response Filed Sep. 16, 2022 to First Examination Report dated Mar. 17, 2022”, W/ English Claims, 11 pgs. |
“Australian Application Serial No. 2020249420, Response Filed Sep. 21, 2022 to First Examination Report dated Jul. 12, 2022”, 12 pgs. |
“Japanese Application Serial No. 2021-557175, Notification of Reasons for Refusal dated Sep. 27, 2022”, w/ English Translation, 6 pgs. |
“Japanese Application Serial No. 2021-557177, Notification of Reasons for Refusal dated Sep. 27, 2022”, w/ English Translation, 18 pgs. |
“Australian Application Serial No. 2020247109, Response Filed Oct. 3, 2022 to First Examination Report dated Jun. 21, 2022”, 10 pgs. |
“Japanese Application Serial No. 2021-523189, Response Filed Oct. 5, 2022 to Notification of Reasons for Refusal dated Jul. 12, 2022”, W/ English Claims, 21 pgs. |
Canadeo, C. M, “Code selection for enhancing UWB multiple access communication performance using TH-PPM and DS-BPSK modulations”, 2003 IEEE Wireless Communications and Networking, WCNC 2003, [Online] Retrieved from the internet: < https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=1200432>, (2003), 678-682. |
Drutarovsky, Milos, “Real-Time Wireless UWB Sensor Network for Person Monitoring”, 2017 14th International Conference on Telecommunications (ConTEL), [Online] Retrieved from the internet: < https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=8000034>, (2017), 19-26. |
Hu, Sanming, “Measurements of UWB Antennas Backscattering Characteristics for RFID Systems”, 2007 IEEE International Conference on Ultra-Wideband, [Online] Retrieved from the internet: < https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=4380922>, (2007), 94-99. |
“U.S. Appl. No. 17/309,102, Non Final Office Action dated Mar. 28, 2023”, 10 pgs. |
“U.S. Appl. No. 17/593,174, Non Final Office Action dated Apr. 27, 2023”, 11 pgs. |
“U.S. Appl. No. 17/593,336, Non Final Office Action dated Apr. 3, 2023”, 12 pgs. |
“U.S. Appl. No. 17/593,338, Non Final Office Action dated Dec. 20, 2022”, 10 pgs. |
“U.S. Appl. No. 17/593,338, Response filed Mar. 1, 2023 to Non Final Office Action dated Dec. 20, 2022”, 12 pgs. |
“U.S. Appl. No. 17/593,342, Non Final Office Action dated Jan. 25, 2023”, 12 pgs. |
“U.S. Appl. No. 17/593,342, Notice of Allowance dated May 10, 2023”, 5 pgs. |
“U.S. Appl. No. 17/593,342, Response filed Apr. 12, 2023 to Non Final Office Action dated Jan. 25, 2023”, 13 pgs. |
“U.S. Appl. No. 17/593,342, Supplemental Notice of Allowability dated May 22, 2023”, 2 pgs. |
“U.S. Appl. No. 17/812,426, Non Final Office Action dated Mar. 2, 2023”, 10 pgs. |
“U.S. Appl. No. 17/812,426, Notice of Allowance dated May 8, 2023”, 10 pgs. |
“U.S. Appl. No. 17/812,426, Response filed Apr. 19, 2023 to Non Final Office Action dated Mar. 2, 2023”, 9 pgs. |
“Australia Application Serial No. 2020247107, Subsequent Examiners Report dated Feb. 28 2023”, 3 pgs. |
“Australian Application Serial No. 2019373730, Response Filed Dec. 1, 22 to Subsequent Examiners Report dated Sep. 21, 2022”, 18 pgs. |
“Australian Application Serial No. 2019373730, Subsequent Examiners Report dated Sep. 21, 2022”, 7 pgs. |
“Australian Application Serial No. 2020247107, First Examination Report dated Sep. 13, 2022”, 4 pgs. |
“Australian Application Serial No. 2020247107, Response Filed Jan. 31, 2023 to First Examination Report dated Sep. 13, 2022”, 15 pgs. |
“Australian Application Serial No. 2020247109, Response Filed Jan. 31, 2023 to Subsequent Examiners Report dated Oct. 28, 2022”, 8 pgs. |
“Australian Application Serial No. 2020247109, Subsequent Examiners Report dated Oct. 28, 2022”, 3 pgs. |
“Australian Application Serial No. 2020247386, Response Filed Dec. 21, 2022 to First Examination Report dated Aug. 30, 2022”, 11 pgs. |
“Australian Application Serial No. 2020247386, Response Filed Mar. 20, 2023 to Subsequent Examiners Report dated Dec. 23, 2022”, No. Claim Amendments, 2 pgs. |
“Australian Application Serial No. 2020247386, Subsequent Examiners Report dated Apr. 13, 2023”, 3 pgs. |
“Australian Application Serial No. 2020247386, Subsequent Examiners Report dated Dec. 12, 2022”, 3 pgs. |
“Australian Application Serial No. 2020247388, Response Filed Jan. 31, 2023 to Subsequent Examiners Report dated Nov. 17, 2022”, 12 pgs. |
“Australian Application Serial No. 2020247388, Response filed Oct. 26, 2022 to First Examination Report dated Jul. 26, 2022”, 120 pgs. |
“Australian Application Serial No. 2020247388, Subsequent Examiners Report dated NOv. 17, 2022”, 3 pgs. |
“Australian Application Serial No. 2020249424, Response filed Oct. 26, 2022 to First Examination Report dated Jul. 7, 2022”, 121 pgs. |
“Australian Application Serial No. 2020249425, Response filed Oct. 11, 2022 Filed to First Examination Report dated Jul. 20, 2022”, 9 pgs. |
“Canadian Application Serial No. 3,117,588, Examiners Rule 86(2) Requisition dated Mar. 14, 2023”, 7 pgs. |
“Canadian Application Serial No. 3,134,738, Examiner's Rule 86(2) Requisition dated Nov. 18, 2022”, 4 pgs. |
“Canadian Application Serial No. 3,134,738, Response File Mar. 13, 2023 to Examiner's Rule 86(2) Requisition dated Nov. 18, 2022”, 10 pgs. |
“Canadian Application Serial No. 3,134,749, Response Filed Mar. 27, 2023 to Examiner's Rule 86(2) Report dated Dec. 1, 2022”, 10 pgs. |
“Canadian Application Serial No. 3,134,751, Examiner's Rule 86(2) Requisition dated Nov. 18, 2022”, 5 pgs. |
“Canadian Application Serial No. 3,134,751, Response Filed Mar. 16, 2023 to Examiner's Rule 86(2) Requisition dated Nov. 18, 2022”, 13 pgs. |
“Canadian Application Serial No. 3,134,864, Examiner's Rule 86(2) Requisition dated NOv. 18, 2022”, 4 pgs. |
“Canadian Application Serial No. 3,134,864, Response Filed Mar. 13, 2023 to Examiner's Rule 86(2) Requisition dated Nov. 18, 2022”, 7 pgs. |
“Canadian Application Serial No. 3,134,866, Examiner's Rule 86(2) Requisition dated Nov. 18, 2022”, 4 pgs. |
“Canadian Application Serial No. 3,134,866, Response Filed Mar. 8, 32 to Examiner's Rule 86(2) Requisition dated Nov. 18, 2022”, 8 pgs. |
“Canadian Application Serial No. 3,134,867, Examiner's Rule 86(2) Requisition dated Nov. 18, 2022”, 4 pgs. |
“Canadian Application Serial No. 3,134,867, Response Filed Mar. 9, 2023 to Examiner's Rule 86(2) Requisition dated Nov. 18, 2022”, No. Claim Amendments, 10 pgs. |
“Canadian Application Serial No. 3,134,931, Examiner's Rule 86(2) Requisition dated Dec. 8, 2022”, 3 pgs. |
“Canadian Application Serial No. 3,134,931, Response Filed Apr. 3, 23 to Examiner's Rule 86(2) Requisition dated Dec. 8, 2022”, 12 pgs. |
“Canadian Application Serial No. 3,134,749, Examiner's Rule 86(2) Report dated Dec. 1, 2022”, 4 pgs. |
“Chinese Application Serial No. 202080022914.1, Office Action dated Oct. 24, 2022”, w/ English translation, 20 pgs. |
“Chinese Application Serial No. 202080022914.1, Response Filed Feb. 17, 2023 to Office Action dated Oct. 24, 2022”, W/ English Claims, 12 pgs. |
“Chinese Application Serial No. 202080023684.0, Office Action dated Mar. 22, 2023”, w/ English Translation, 15 pgs. |
“Chinese Application Serial No. 202080023684.0, Office Action dated Sep. 30, 2022”, w/ English Translation, 23 pgs. |
“Chinese Application Serial No. 202080023684.0, Response Filed Jan. 29, 2023 to Office Action dated Sep. 30, 2022”, W/ English Claims, 33 pgs. |
“European Application Serial No. 20714545.9, Communication Pursuant to Rule 114(2) EPC dated Nov. 21, 2022”, 53 pgs. |
“European Application Serial No. 20714545.9, Communication Pursuant to Rule 114(2) EPC dated Dec. 1, 2022”, 7 pgs. |
“European Application Serial No. 22198344.8, Extended European Search Report dated Jan. 5, 2023”, 10 pgs. |
“Indian Application Serial No. 202117041276, Response Filed Feb. 28, 2023 to First Examination Report dated Aug. 29, 2022”, W/ English Claims, 19 pgs. |
“Indian Application Serial No. 202117041409, Response Filed Mar. 7, 2023 to First Examination Report dated Sep. 7, 2022”, W/ English Claims, 17 pgs. |
“Indian Application Serial No. 202117041409; Voluntary Amendment Filed Mar. 7, 2023”, W/ English Claims, 11 pgs. |
“Indian Application Serial No. 202117041414, Response Filed Mar. 3, 2023 to First Examination Report dated Sep. 5, 2022”, W/ English Claims, 23 pgs. |
“Indian Application Serial No. 202117041414, Voluntary Amendment Filed Mar. 3, 2023”, W/ English Claims, 11 pgs. |
“Indian Application Serial No. 202117041712, Response Filed Mar. 7, 23 to First Examination Report dated Sep. 8, 2022”, W/ English Claims, 16 pgs. |
“Indian Application Serial No. 202117041714, Response Filed Mar. 7, 2023 to First Examination Report dated Sep. 7, 2022”, W/ English Claims, 17 pgs. |
“Japanese Application Serial No. 2021-557174, Notification of Reasons for Refusal dated Apr. 18, 2023”, w/ English Translation, 10 pgs. |
“Japanese Application Serial No. 2021-557174, Notification of Reasons for Refusal dated Nov. 1, 2022”, w/ English Translation, 8 pgs. |
“Japanese Application Serial No. 2021-557174, Response Filed Jan. 18, 2023 to Notification of Reasons for Refusal dated Nov. 1, 2022”, W/ English Claims, 17 pgs. |
“Japanese Application Serial No. 2021-557175, Response Filed Dec. 19, 2022 to Notification of Reasons for Refusal dated Sep. 27, 2022”, W/ English Claims, 16 pgs. |
“Japanese Application Serial No. 2021-557176, Notification of Reasons for Refusal dated Nov. 1, 2022”, w/ English Translation, 12 pgs. |
“Japanese Application Serial No. 2021-557176, Response Filed Jan. 18, 2023 to Notification of Reasons for Refusal dated Nov. 1, 2022”, W/ English Claims, 15 pgs. |
“Japanese Application Serial No. 2021-557177, Response Filed Dec. 16, 2022 to Notification of Reasons for Refusal dated Sep. 27, 2022”, W/ English Claims, 16 pgs. |
“Japanese Application Serial No. 2021-557178, Final Notification of Reasons for Refusal dated May 9, 2023”, w/ English Translation, 4 pgs. |
“Japanese Application Serial No. 2021-557178, Notification of Reasons for Refusal dated Oct. 18, 2022”, w/ English translation, 9 pgs. |
“Japanese Application Serial No. 2021-557178, Request Filed Jan. 13, 2023 to Notification of Reasons for Refusal dated Oct. 18, 2022”, W/ English Claims, 16 pgs. |
“Japanese Application Serial No. 2021-557179, Notification of Reasons for Refusal dated Oct. 18, 2022”, w/ English translation, 10 pgs. |
“Japanese Application Serial No. 2021-557179, Notification of Reasons for Rejection dated May 9, 2023”, W/English Translation, 6 pgs. |
“Japanese Application Serial No. 2021-557179, Response Filed Jan. 13, 2023 to Notification of Reasons for Refusal dated Oct. 18, 2022”, W/ English Claims, 18 pgs. |
“Japanese Application Serial No. 2021-557180, Final Notification of Reasons for Refusal dated Apr. 18, 2023”, w/ English translation, 8 pgs. |
“Japanese Application Serial No. 2021-557180, Notification of Reasons for Refusal dated Nov. 1, 2022”, w/ English Translation, 10 pgs. |
“Japanese Application Serial No. 2021-557180, Response Filed Jan. 18, 23 to Notification of Reasons for Refusal dated Nov. 1, 2022”, W/ English Claims, 19 pgs. |
“Korean Application Serial No. 10-2021-7013164, Notice of Preliminary Rejection dated Mar. 31, 2023”, w/ English Translation, 13 pgs. |
Angelico, Bruno, “Ultra-wideband Performance in a Dense Multipath Environment with Time and Spatial Diversity”, 16th IST Mobile and Wireless Communications Summit, [Online]. Retrieved from the Internet: <https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=4299254>, (2007). |
Huang, Jingjing, et al., “Secret Key Generation Exploiting Ultra-wideband Indoor Wireless Channel Characteristics”, IEEE Military Communications Conference, [Online]. Retrieved from the Internet: <https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6735631>, (2013), 5 pgs. |
Madiseh, Ghoreishi M, “Verification of Secret Key Generation from UWB Channel Observations”, IEEE International Conference on Communications, [Online]. Retrieved from the Internet: <https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=5199564>, (2009), 5 pgs. |
Miri, Jamel, “Privacy group distance bounding protocol on TH-UWB based NTRU public key cryptosystem”, Sixth International Conference on Communications and Networking, [Online]. Retrieved from the Internet: <https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=8285598>, (2017). |
Ranganathan, Aanjhan, et al., “Are We Really Close? Verifying Proximity in Wireless Systems”, in IEEE Security & Privacy, vol. 15, No. 3, (May/Jun. 2017), 7 pgs. |
Somayazulu, V S, “Multiple access performance in UWB systems using time hopping vs. direct sequence spreading”, IEEE Wireless Communications and Networking Conference Record, [Online]. Retrieved from the Internet: <https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=993322>, (2002). |
U.S. Appl. No. 17/812,426 U.S. Pat. No. 11,765,588, filed Jul. 13, 2022, Physical Access Control Systems With Localization-Based Intent Detection. |
U.S. Appl. No. 18/446,657, filed Aug. 9, 2023, Physical Access Control Systems With Localization-Based Intent Detection. |
“Application Serial No. 17 593,174, Response filed Jul. 27, 2023 to Non Final Office Action dated Apr. 27, 2023”, 10 pages. |
“European Application Serial No. 20714986.5, Communication Pursuant to Article 94(3) EPC dated Jun. 30, 2023”, 7 pages. |
“Canadian Application Serial No. 3,134,749, Examiners Rule 86(2) Report dated Sep. 13, 2023”, 4 pages. |
“Australia Application Serial No. 2020247107, Response Filed May 22, 2023 to Subsequent Examiners Report dated Feb. 28, 2023”, No. Amendments to Claims, 3 pgs. |
“Australian Application Serial No. 2020247386, Response Filed May 29, 2023 to Subsequent Examiners Report dated Apr. 13, 2023”, No. Amendments to Claims, 2 pgs. |
“Chinese Application Serial No. 202080023684.0, Response Filed Jun. 5, 2023 to Office Action dated Mar. 22, 2023”, with Concise Statement of Relevance, 4 pages. |
“Application Serial No. 17 593,338, Notice of Allowance dated Jun. 14, 2023”, 10 pgs. |
“Korean Application Serial No. 10-2021-7013164, Response Filed May 30, 2023 to Notice of Preliminary Rejection dated Mar. 31, 2023”, with English claims, 35 pages. |
“Australian Application Serial No. 2020247107, Subsequent Examiners Report dated Jun. 22, 2023”, 3 pgs. |
“Application Serial No. 17 309,102, Response filed Jun. 26, 2023 to Non Final Office Action dated Mar. 28, 2023”, 11 pgs. |
“Application Serial No. 17 593,336, Response filed Jun. 28, 2023 to Non Final Office Action dated Apr. 3, 2023”, 12 pgs. |
“Application Serial No. 17 593,338, Supplemental Notice of Allowability dated Jul. 6, 2023”, 3 pgs. |
“Application Serial No. 17 593,340, Non Final Office Action dated Jul. 12, 2023”, 8 pgs. |
“Canadian Application Serial No. 3,117,588, Response Filed Jul. 6, 2023 to Examiners Rule 86(2) Requisition dated Mar. 14, 2023”, 28 pgs. |
“Japanese Application Serial No. 2021-557174, Response Filed Jul. 12, 2023 to Notification of Reasons for Refusal dated Apr. 18, 2023”, with English claims, 11 pages. |
“Japanese Application Serial No. 2021-557180, Response Filed Jul. 14, 2023 to Final Notification of Reasons for Refusal dated Apr. 18, 2023”, with English claims, 10 pages. |
“Application Serial No. 17 309,102, Final Office Action dated Jul. 25, 2023”, 10 pgs. |
“Korean Application Serial No. 10-2021-7030781, Notice of Preliminary Rejection dated Jul. 20, 2023”, with English translation, 11 pages. |
“Application Serial No. 17 593,342, Supplemental Notice of Allowability dated Aug. 1, 2023”, 2 pgs. |
“Application Serial No. 17 593,338, Supplemental Notice of Allowability dated Aug. 9, 2023”, 3 pgs. |
“Chinese Application Serial No. 202080023684.0, Decision of Rejection dated Jul. 27, 2023”, with English translation, 17 pages. |
“Korean Application Serial No. 10-2021-7030765, Notice of Preliminary Rejection dated Jul. 28, 2023”, with English translation, 16 pages. |
“Japanese Application Serial No. 2021-557178, Response Filed Aug. 4, 2023 to Final Notification of Reasons for Refusal dated May 9, 2023”, with English claims, 10 pages. |
“Japanese Application Serial No. 2021-557179, Response Filed Aug. 4, 2023 to Notification of Reasons for Rejection dated May 9, 2023”, with English claims, 9 pages. |
“Korean Application Serial No. 10-2021-7030699, Notice of Preliminary Rejection dated Jul. 28, 2023”, with English translation, 11 pages. |
“Application Serial No. 17 593,342, Supplemental Notice of Allowability dated Aug. 22, 2023”, 2 pgs. |
“Korean Application Serial No. 10-2021-7030785, Notice of Preliminary Rejection dated Jul. 28, 2023”, with English translation, 11 pages. |
“European Application Serial No. 22198344.8, Response Filed Aug. 11, 2023 Extended European Search Report dated Jan. 5, 2023”, No. Claim Amendments, 8 pgs. |
“Australian Application Serial No. 2020247107, Response Filed Aug. 14, 2023 to Subsequent Examiners Report dated Jun. 22, 2023”, 13 pgs. |
“Canadian Application Serial No. 3,134,864, Office Action dated Aug. 23, 2023”, 3 pgs. |
“Canadian Application Serial No. 3,134,867, Examiners Rule 86(2) Report dated Sep. 13, 2023”, 5 pgs. |
“Australian Application Serial No. 2023200489, First Examination Report dated Sep. 11, 2023”, 3 pgs. |
“Application Serial No. 17 593,338, Corrected Notice of Allowability dated Sep. 21, 2023”, 3 pgs. |
“Application Serial No. 17 309, 102, Response filed Sep. 22, 2023 to Final Office Action dated Jul. 25, 2023”, 12 pgs. |
“Chinese Application Serial No. 201980073003.9, Office Action dated Sep. 1, 2023”, with English translation, 25 pages. |
“Korean Application Serial No. 10-2021-7030696, Notice of Preliminary Rejection dated Sep. 19, 2023”, with English translation, 6 pages. |
“Application Serial No. 17 593,336, Notice of Allowance dated Oct. 2, 2023”, 5 pgs. |
“Application Serial No. 17 593,340, Response filed Oct. 11, 2023 to Non Final Office Action dated Jul. 12, 2023”, 9 pgs. |
“Canadian Application Serial No. 3,134,931, Office Action dated Oct. 5, 2023”, 3 pgs. |
“Korean Application Serial No. 10-2021-7030765, Response filed Sep. 21, 2023 to Notice of Preliminary Rejection dated Jul. 28, 2023”, with English claims, 26 pages. |
“Korean Application Serial No. 10-2021-7030699, Response filed Sep. 25, 2023 to Notice of Preliminary Rejection dated Jul. 28, 2023”, with English claims 31 pages. |
“Korean Application Serial No. 10-2021-7030785, Response filed Oct. 4, 2023 to Notice of Preliminary Rejection dated Jul. 28, 2023”, with English claims 30 pages. |
“U.S. Appl. No. 17/994,839, Notice of Allowability dated Oct. 27, 2023”, 2 pages. |
“U.S. Appl. No. 17/309,102, Notice of Allowance dated Oct. 19, 2023”, 7 pgs. |
“Japanese Application Serial No. 2023-005052, Notification of Reasons for Refusal dated Oct. 17, 2023”, with English translation, 16 pages. |
“U.S. Appl. No. 17/593,338, Corrected Notice of Allowability dated Oct. 20, 2023”, 2 pgs. |
“Korean Application Serial No. 10-2021-7030781, Response filed Sep. 20, 2023 to Notice of Preliminary Rejection dated Jul. 20, 2023”, No Amendments to Claims, 10 pgs. |
“Korean Application Serial No. 10-2021-7030782, Notice of Preliminary Rejection dated Nov. 23, 2023”, with English translation, 9 pages. |
Number | Date | Country | |
---|---|---|---|
20220189224 A1 | Jun 2022 | US |
Number | Date | Country | |
---|---|---|---|
62906995 | Sep 2019 | US | |
62823341 | Mar 2019 | US |