This disclosure relates generally to a field of wireless communication and, more particularly, to methods, devices, and systems for increasing wireless communication range.
Bluetooth devices such as Bluetooth speakers, smart phones, smart locks, and various smart Bluetooth sensors and wearable devices, have become widely used in many applications. As Bluetooth technology is designed for low power and low cost operation, the communication range of Bluetooth devices is typically quite short. For example, the typical communication range between two Bluetooth devices, such as a smart phone and a Bluetooth Low Energy (BLE) sensor, is limited to tens of meters in open space and a few meters inside a house, and the Bluetooth transmission typically cannot penetrate walls. The short communication range limits the use of Bluetooth devices in scenarios where longer communication range is required.
Conventional schemes to increase wireless communication range typically involve increasing the transmission power or antenna gain on both sides of the radio frequency transmission. However, for Bluetooth devices, especially the BLE sensors and wearable devices, increasing the transmission power or antenna gain of the devices is often impractical and would defeat the design goal of low power and low cost Bluetooth devices. Thus, it is desired to extend the communication range of Bluetooth devices without having to increase the transmission power or production cost of the Bluetooth devices.
The accompanying drawings, which constitute a part of this specification, illustrate several embodiments and, together with the description, serve to explain the disclosed principles.
Exemplary embodiments are described with reference to the accompanying drawings. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. Wherever convenient, the same reference numbers are used throughout the drawings to refer to the same or like parts. While examples and features of disclosed principles are described herein, modifications, adaptations, and other implementations are possible without departing from the spirit and scope of the disclosed embodiments. Also, the words “comprising,” “having,” “containing,” and “including,” and other similar forms are intended to be equivalent in meaning and be open ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items, or meant to be limited to only the listed item or items. It must also be noted that as used herein and in the appended claims, the singular forms “a,” “an,” and “the” include plural references unless the context clearly dictates otherwise. It is intended that the following detailed description be considered as exemplary only, with the true scope and spirit being indicated by the following claims.
The illustrated components and steps are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
In some embodiments, the client devices may be Bluetooth devices or sensors (or other wireless devices such as WIFI devices, Zigbee devices, etc.), and the hub 120 may be used to increase the communication range between the client devices. Bluetooth devices operate in one of two modes: as a master device or a slave device. The master device provides a network clock and determines the frequency hopping sequence, and the slave devices synchronize to the master's clock and follow the master's hopping frequency. Each of the client devices shown in
In some embodiments, the client devices may communicate with the hub 120 through a network 140. For example, as shown in
The present disclosure provides a wireless hub that can be used to effectively increase the wireless communication range between the client devices. The wireless hub may support long range transmission without requiring modification of the wireless client devices. The wireless hub may function as a transparent relay that the client devices may not necessary be aware of. In some embodiments, the wireless hub may be a Bluetooth hub and support all the public profiles of Bluetooth. It is also possible to control the wireless hub through a cloud server, for example, by using a smart phone application. Furthermore, the wireless hub may be configured to connect to a cloud server and capable of adaptively reconfigure itself based on the use history, interaction, and/or activities of the client devices and the wireless hub. It should be noted that the hub 120 may also be called as a router, and in this disclosure, the terms of hub and router are inter-exchangeable.
In the following description, Bluetooth protocols and devices are used to illustrate the design of the wireless hub. It should be understood, however, that similar constructions of the wireless hub can be applied to scenarios where other wireless communication protocols are used without departing from the spirit and scope of the present disclosure.
The RF front end system 220 is communicatively coupled to the Bluetooth transceiver 210 and the antenna 240. The RF front end system 220 may improve RF performance of the Bluetooth transceiver 210 by increasing its receiving sensitivity and transmission power. The RF front end system 220 may include a RF sampling block 222, a RF switching logic 224, one or more RF switching blocks (e.g., 225 and 226), RF transmission gain block 228, and one or more RF receiving gain blocks (e.g., 229 and 230).
The RF sampling block 222 is coupled to the Bluetooth transceiver 210 and samples the RF signal received from the Bluetooth transceiver 210. For example, a small portion of the RF signal (e.g., less than 1%) outputted from the Bluetooth transceiver 210 may be passed to the RF sampling block 222, and the remaining portion of the RF signal outputted from the Bluetooth transceiver 210 may be passed to the RF switching block 225 for transmitting to the antenna 240. In other words, the RF sampling block 222 samples the RF signal outputted from the Bluetooth transceiver 210 at a rate substantially lower than that of the RF signals flowing to the antenna 240. The RF sampling block 222 converts the sampled RF signal into voltage signal and outputs the voltage signal to the RF switching logic 224. In some embodiments, the RF sampling block 222 may include a low pass filter that filters the voltage signal before sending it to the RF switching logic 224. The filtered voltage signal may also be converted into logarithmic signals for passing to the RF switching logic 224.
The RF switching logic 224 is coupled to the RF sampling block 222 to receive the voltage signals and switches the RF front end system 220 between a transmitting mode and a receiving mode. For example, the RF switching logic 224 may send control signals to the RF switching blocks 225 and 226 to switch the RF front end system 220 between the transmitting mode and the receiving mode based on the voltage signals received from the RF sampling block 222. The control signals may be sent from the RF switching logic 224 to the RF switching blocks 225 and 226 within hundreds of nanoseconds. In some embodiments, the RF switching logic 224 may compare the received voltage signal to a predetermined threshold, and if the voltage signal is greater than the predetermined threshold, switch the RF front end system 220 to the transmitting mode.
The RF transmission gain block 228 is configured to increase signal power of the RF signal received from the Bluetooth transceiver 210. The RF transmission gain block 228 may be enabled or disabled by the RF switching logic 224. For example, the RF switching logic 224 may be connected with the RF transmission gain block 228 and may send control signal to the RF transmission gain block 228 to enable or disable the RF transmission gain block 228. In some embodiments, the RF transmission gain block 228 may include a ceramic filter and step RF attenuator to shape the RF signal received from the Bluetooth transceiver 210 before amplifying the RF signal.
The RF receiving gain blocks 229 and 230 are configured to suppress the noise figure of the receiving chain. The RF receiving gain blocks 229 and 230 may be enabled or disabled by the RF switching logic 224. For example, the RF switching logic 224 may be connected with the RF receiving gain blocks 229 and 230 and may send control signals to the RF receiving gain blocks to enable or disable the RF receiving gain blocks 229 and 230. As illustrated in the Friis formula, the total noise factor of a cascade of stages is given as:
where Fi and Gi are the noise factor and available power gain, respectively, of the i-th stage, and n is the number of stages. It can be seen that the overall noise figure of RF receiver is primarily established by the noise figure of its first gain stage. Consequently, a cascade of RF receiving gain blocks, such as the RF receiving gain blocks 229 and 230, may be used to further lower the noise figure of the RF front end system 220. Although two RF receiving gain blocks 229 and 230 are used in
As shown in
A person having ordinary skill in the art should appreciate that the above described Bluetooth hub 200 can be modified to apply to scenarios where other wireless communication protocols are used. For example, the Bluetooth transceiver 210 in
As shown in
The reconfigurable antenna system 520 may include a plurality of antenna elements, and each of the antenna elements may be turned on or off independently. Thus, a unique antenna radiation pattern may be formed by turning on or off each of the antenna elements. In other words, different antenna configurations may be produced by turning on or off each of the antenna elements. The reconfigurable antenna system 520 may be configured by the antenna logic system 510 with a specific antenna configuration of the antenna elements.
The antenna logic system 510 includes a feedback logic input port connected to the Bluetooth transceiver 210 and a control logic output port connected to the reconfigurable antenna system 520. In some embodiments, during an initialization stage, the reconfigurable antenna system 520 may scan through each of the antenna configurations. The Bluetooth transceiver 210 (or a processor associated with the Bluetooth transceiver 210) may generate a received signal strength indicator (RSSI) for each of the antenna configurations based on signals received from Bluetooth client devices. The antenna logic system 510 may receive feedback from the Bluetooth transceiver 210, including the RSSI of each of the antenna configurations for each client device.
For each of the Bluetooth client devices, the antenna logic system 510 may select a preferred antenna configuration based on the RSSIs and configure the reconfigurable antenna system 520 with the preferred antenna configuration for the corresponding client device. For example, the antenna logic system 510 may select an antenna configuration corresponding to the highest RSSI among all the antenna configurations. In some embodiments, the antenna logic system 510 may take into account both the RSSI and the prior selected antenna configuration in deciding which antenna configuration to select for the client device. In some embodiments, the antenna logic system 510 may take into account the RSSI, the bit error rate (BER), the packet error rate (PER), and/or the noise floor of the communication path in deciding which antenna configuration to select for the client device. By selecting the antenna configuration based on the feedback provided by the Bluetooth transceiver 210, the reconfigurable antenna system 520 may achieve higher antenna gain and receive less noise, thereby increasing the communication range of the Bluetooth client devices.
A person having ordinary skill in the art should appreciate that the above described Bluetooth hub 500 can be modified to apply to scenarios where other wireless communication protocols are used. For example, the Bluetooth transceiver 210 in
At step 602, the Bluetooth hub scans through the different antenna configurations and generates a corresponding RSSI for each of the antenna configurations. For example, during an initialization stage, the reconfigurable antenna system 520 may scan through the antenna configurations, and the Bluetooth transceiver 210 (or a processor associated with the Bluetooth transceiver 210) may generate the RSSI corresponding to each of the antenna configurations. If there is a plurality of Bluetooth client devices in the system, the Bluetooth hub may generate a set of RSSIs for each of the client devices. The Bluetooth transceiver 210 (or a processor associated with the Bluetooth transceiver 210) may feedback the RSSIs to the antenna logic system 510 for selection of the antenna configuration. In some embodiments, a processor of the Bluetooth hub may select an antenna configuration based on the RSSIs and feedback the selected antenna configuration to the antenna logic system 510.
Referring back to
At step 606, the Bluetooth hub configures the reconfigurable antenna system 520 with the selected antenna configuration, and the selected antenna configuration is used to communicate with the corresponding Bluetooth client device. For example, the antenna logic system 510 may configure the reconfigurable antenna system 520 with the selected antenna configuration via the control logic output port. The selected antenna configuration may be used to communicate with the corresponding Bluetooth client device within a timeout, that is, a predetermined time period. After the timeout, the method 600 may return to step 602 to scan through the antenna configurations and obtain updated RSSIs for each of the antenna configurations. In some embodiments, the timeout may be set to a value less than one second, for example, 300 ms. The antenna logic system 510 may update the selected antenna configuration based on the updated RSSIs. Thus, a selected antenna configuration is used to communicate with a client device for a predetermined time period, and the selected antenna configuration is updated after the predetermined time period to reflect the current RF channel conditions. By selecting the antenna configuration based on the RSSI and update the selected antenna configuration periodically, the method 600 achieves higher antenna gain and lower noise, and as a result, increases the communication range of the client devices.
The RF energy splitter 810 is coupled with the RF front end system 220, and the RF energy flows from the RF front end system 220 to the RF energy splitter 810. The RF energy splitter 810 is configured to divide the RF energy, for example, equally, into N parts and feed the split RF energy into each of the N directional antenna elements 820-1 to 820-N. Each of the directional antenna elements 820-1 to 820-N may be configured to radiate in a different direction, and the combination of all the antenna elements may cover the entire area of the network. For example, each of the directional antenna elements 820-1 to 820-N may be configured to radiate in a direction towards 1/N part of the area. In doing so, higher antenna gain may be achieved for the Bluetooth hub in comparison with those using omni-directional antennas.
In some embodiments, the Bluetooth hub may determine, for a particular Bluetooth device, which directional antenna element receives the strongest signal from that Bluetooth device. The Bluetooth hub may determine that the Bluetooth device falls in an area covered by that directional antenna element, and use that directional antenna element to transmit RF signals for the Bluetooth device. For example, the Bluetooth hub may feed all of the RF energy for the Bluetooth device to that directional antenna element, instead of equally dividing the RF energy to all the antenna elements.
A person having ordinary skill in the art should appreciate that the above described Bluetooth hub 800 can be modified to apply to scenarios where other wireless communication protocols are used. For example, the Bluetooth transceiver 210 in
Since both the WIFI devices and Bluetooth devices operate at the industrial, scientific and medical (ISM) radio bands, there may exist internal interferences between the Bluetooth module 920 and the WIFI module 930 within the wireless communication hub 900. To minimize the interference between the Bluetooth module 920 and the WIFI module 930, the Bluetooth module 920 and the WIFI module 930 may be placed apart on the PCB 910, for example, at opposite ends of the PCB 910. As shown in
It should be understood that although a WIFI module and a Bluetooth module are included in
Since both the WIFI devices and Bluetooth devices operate at the ISM radio bands, to minimize the interference between the Bluetooth module 920 and the WIFI module 930, the Bluetooth module 920 and the WIFI module 930 may be placed apart on the PCB 910, for example, by having a physical distance greater than a predetermined minimum distance.
In some embodiments, interference between the communication modules may be reduced by using different antenna polarizations and PCB RF paths between each communication modules. As shown in
In some embodiments, interference between the communication modules may be reduced by using time-domain isolation. For example, a processor (e.g., a CPU) of the wireless communication hub may function as a communication controller and execute a timing algorithm to determine the time slots for each of the communication module to transmit and/or receive data. When the WIFI module is transmitting and/or receiving data, the processor may send control signal to the Bluetooth module such that the Bluetooth module refrains from transmission at the same time when the WIFI module is transmitting and/or receiving data. Similarly, when the Bluetooth module is transmitting and/or receiving data, the processor may send control signal to the WIFI module such that the WIFI module refrains from transmission at the same time when the Bluetooth module is transmitting and/or receiving data.
It should be understood that although a WIFI module and a Bluetooth module are included in
As shown in
At the next hopping cycle, different frequency channels for the WIFI communication and the Bluetooth communication may be used. As shown in
It should be understood that although WIFI communication and Bluetooth communication are described in connection with
The specification has described methods, devices, and systems for increasing wireless communication range. The illustrated steps are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. Thus, these examples are presented herein for purposes of illustration, and not limitation. For example, steps or processes disclosed herein are not limited to being performed in the order described, but may be performed in any order, and some steps may be omitted, consistent with disclosed embodiments. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
It is intended that the disclosure and examples be considered as exemplary only, with a true scope and spirit of disclosed embodiments being indicated by the following claims.
This application is a divisional application of U.S. application Ser. No. 14/639,711, filed on Mar. 5, 2015. U.S. application Ser. No. 14/639,711 is based on and claims priority to U.S. Provisional Application No. 62/110,250, filed Jan. 30, 2015, entitled “METHODS, DEVICES AND SYSTEMS FOR INCREASING WIRELESS COMMUNICATION RANGE,” and U.S. Provisional Application No. 62/110,262, filed Jan. 30, 2015, entitled “BLUETOOTH TRANSPARENT RELAY.” The entire contents of the above referenced applications are all incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5408197 | Miyake | Apr 1995 | A |
5513382 | Agahi-Kesheh | Apr 1996 | A |
5521561 | Yrjola | May 1996 | A |
5689817 | Fok | Nov 1997 | A |
6054896 | Wright | Apr 2000 | A |
6097703 | Larsen | Aug 2000 | A |
6236622 | Blackman | May 2001 | B1 |
6404386 | Proctor, Jr. | Jun 2002 | B1 |
6681100 | Ge | Jan 2004 | B1 |
6957047 | Young et al. | Oct 2005 | B1 |
7363003 | Takatani et al. | Apr 2008 | B2 |
7961689 | Stratford | Jun 2011 | B2 |
8219026 | Naik et al. | Jul 2012 | B2 |
8433242 | Kenington et al. | Apr 2013 | B2 |
8976724 | Hauser et al. | Mar 2015 | B2 |
9264907 | Laroia | Feb 2016 | B2 |
9730003 | Gu et al. | Aug 2017 | B2 |
9769594 | Zhang et al. | Sep 2017 | B2 |
9960834 | Zhang et al. | May 2018 | B2 |
9986495 | Gu et al. | May 2018 | B2 |
9990790 | Petel et al. | Jun 2018 | B2 |
10178494 | Zhao et al. | Jan 2019 | B2 |
10225098 | Gu et al. | Mar 2019 | B2 |
20010012757 | Boyle | Aug 2001 | A1 |
20010014911 | Doi | Aug 2001 | A1 |
20020028655 | Rosener | Mar 2002 | A1 |
20020072329 | Bandeira | Jun 2002 | A1 |
20030095524 | Stephens et al. | May 2003 | A1 |
20030214437 | Rawnick | Nov 2003 | A1 |
20050070329 | Lection | Mar 2005 | A1 |
20050088980 | Olkkonen | Apr 2005 | A1 |
20050212708 | Fifield | Sep 2005 | A1 |
20050248962 | Searfoss | Nov 2005 | A1 |
20070041344 | Yaqub | Feb 2007 | A1 |
20070188358 | Somayajula | Aug 2007 | A1 |
20070222697 | Caimi | Sep 2007 | A1 |
20080043996 | Dolph | Feb 2008 | A1 |
20090011726 | Nishimura | Jan 2009 | A1 |
20090063703 | Finkelstein et al. | Mar 2009 | A1 |
20090147884 | Sridharan | Jun 2009 | A1 |
20090253373 | Gorbachov | Oct 2009 | A1 |
20090303387 | Chen | Dec 2009 | A1 |
20100015919 | Tian | Jan 2010 | A1 |
20100048131 | Hirsch et al. | Feb 2010 | A1 |
20100103316 | Colsey | Apr 2010 | A1 |
20100121891 | Zampiello | May 2010 | A1 |
20100302979 | Reunamaki | Dec 2010 | A1 |
20100303244 | Kim | Dec 2010 | A1 |
20100315225 | Teague | Dec 2010 | A1 |
20110021142 | Desai | Jan 2011 | A1 |
20110028093 | Patel | Feb 2011 | A1 |
20110066850 | Ekberg | Mar 2011 | A1 |
20110117842 | Hong | May 2011 | A1 |
20110131520 | Al-Shaykh et al. | Jun 2011 | A1 |
20110142413 | Kang | Jun 2011 | A1 |
20110215971 | Rao | Sep 2011 | A1 |
20110249596 | Ross | Oct 2011 | A1 |
20120052802 | Kasslin et al. | Mar 2012 | A1 |
20120057518 | Herrala | Mar 2012 | A1 |
20120115464 | Jang | May 2012 | A1 |
20120116548 | Goree | May 2012 | A1 |
20120200774 | Ehlers, Sr. | Aug 2012 | A1 |
20120326942 | Simmons | Dec 2012 | A1 |
20120329395 | Husted et al. | Dec 2012 | A1 |
20130017816 | Talty | Jan 2013 | A1 |
20130033996 | Song | Feb 2013 | A1 |
20130045684 | Linde | Feb 2013 | A1 |
20130148020 | Cook | Jun 2013 | A1 |
20130154897 | Sorensen | Jun 2013 | A1 |
20130254159 | Thramann | Sep 2013 | A1 |
20140006947 | Garmark | Jan 2014 | A1 |
20140041038 | Lessin | Feb 2014 | A1 |
20140066062 | Chen et al. | Mar 2014 | A1 |
20140073244 | Ko et al. | Mar 2014 | A1 |
20140105054 | Sægrov | Apr 2014 | A1 |
20140119407 | Miller | May 2014 | A1 |
20140169569 | Toivanen et al. | Jun 2014 | A1 |
20140169599 | Solum | Jun 2014 | A1 |
20140181656 | Kumar et al. | Jun 2014 | A1 |
20140181683 | Lim | Jun 2014 | A1 |
20140207489 | Wartena | Jul 2014 | A1 |
20140213189 | Kim et al. | Jul 2014 | A1 |
20140213197 | An | Jul 2014 | A1 |
20140287704 | Dupuy | Sep 2014 | A1 |
20140327578 | Rowson | Nov 2014 | A1 |
20140342670 | Kang et al. | Nov 2014 | A1 |
20140370811 | Kang | Dec 2014 | A1 |
20150002425 | Lee et al. | Jan 2015 | A1 |
20150026746 | Fondberg et al. | Jan 2015 | A1 |
20150031288 | Tubbesing | Jan 2015 | A1 |
20150039269 | Mejegard et al. | Feb 2015 | A1 |
20150095170 | Lang | Apr 2015 | A1 |
20150105022 | Jung | Apr 2015 | A1 |
20150105880 | Slupik | Apr 2015 | A1 |
20150188240 | Eom | Jul 2015 | A1 |
20150234372 | Slupik | Aug 2015 | A1 |
20150245182 | Scagnol et al. | Aug 2015 | A1 |
20150278215 | Lee | Oct 2015 | A1 |
20150296020 | Granqvist et al. | Oct 2015 | A1 |
20150319046 | Plummer et al. | Nov 2015 | A1 |
20150351145 | Burks | Dec 2015 | A1 |
20150382436 | Kelly et al. | Dec 2015 | A1 |
20160006121 | El-Sallabi | Jan 2016 | A1 |
20160063778 | Bruns et al. | Mar 2016 | A1 |
20160088424 | Polo et al. | Mar 2016 | A1 |
20160095060 | Seddighrad et al. | Mar 2016 | A1 |
20160119438 | Abramson | Apr 2016 | A1 |
20160065295 | Stanescu | May 2016 | A1 |
20160147506 | Britt et al. | May 2016 | A1 |
20160154392 | Jo | Jun 2016 | A1 |
20160157048 | Kerai | Jun 2016 | A1 |
20160217672 | Yoon et al. | Jul 2016 | A1 |
20160258617 | Wang | Sep 2016 | A1 |
20170004692 | Britt et al. | Jan 2017 | A1 |
20170065295 | Patel et al. | Mar 2017 | A1 |
20170099597 | Choi et al. | Apr 2017 | A1 |
20170127304 | Britt et al. | May 2017 | A1 |
20170201854 | Choi et al. | Jul 2017 | A1 |
20170215030 | Choi et al. | Jul 2017 | A1 |
20170272166 | Albrecht et al. | Sep 2017 | A1 |
20170353979 | Lee et al. | Dec 2017 | A1 |
20190260660 | Abuan et al. | Aug 2019 | A1 |
Number | Date | Country |
---|---|---|
2749659 | Feb 2012 | CA |
101026406 | Aug 2007 | CN |
102882567 | Jan 2013 | CN |
2004-506983 | Mar 2004 | JP |
2004-272376 | Sep 2004 | JP |
2009-060163 | Mar 2009 | JP |
2011-524101 | Aug 2011 | JP |
2012-500590 | Jan 2012 | JP |
2013-529423 | Jul 2013 | JP |
2013-258672 | Dec 2013 | JP |
2014-519236 | Aug 2014 | JP |
2015-008368 | Jan 2015 | JP |
2017-511028 | Apr 2017 | JP |
2007033194 | Mar 2007 | WO |
2012150534 | Nov 2012 | WO |
2013086036 | Jun 2013 | WO |
2014082665 | Jun 2014 | WO |
Entry |
---|
International Application No. PCT/US2016/015124, International Search Report and Written Opinion dated May 26, 2016. |
International Application No. PCT/US2016/015617, International Search Report and Written Opinion dated Apr. 21, 2016. |
International Application No. PCT/US2016/015105, International Search Report and Written Opinion dated Jun. 3, 2016. |
Non-Final Office Action for U.S. Appl. No. 14/919,124, dated Oct. 7, 2016, 14 pages. |
Final Office Action for U.S. Appl. No. 14/789,614, dated Oct. 14, 2016, 16 pages. |
Non-Final Office Action for U.S. Appl. No. 14/930,307, dated Oct. 20, 2016, 15 pages. |
Non-Final Office Action for U.S. Appl. No. 14/639,711, dated Jun. 17, 2016, 14 pages. |
Final Office Action for U.S. Appl. No. 14/919,124, dated Apr. 7, 2017, 13 pages. |
Non-Final Office Action for U.S. Appl. No. 15/450,534, dated Apr. 7, 2017, 8 pages. |
International Application No. PCT/US2016/015105, International Preliminary Report on Patentability dated Aug. 1, 2017. |
International Application No. PCT/US2016/015124, International Preliminary Report on Patentability dated Aug. 1, 2017. |
International Application No. PCT/US2016/015617, International Preliminary Report on Patentability dated Aug. 1, 2017. |
Non-Final Office Action for U.S. Appl. No. 14/919,124, dated Nov. 2, 2017, 13 pages. |
Final Office Action for U.S. Appl. No. 15/450,534, dated Sep. 8, 2017, 10 pages. |
Partial Search Report for European Application No. 16744028.8, dated Jul. 25, 2018, 16 pages. |
Partial Search Report for European Application No. 16744033.8, dated Jul. 27, 2018, 15 pages. |
First Office Action for Chinese Application No. 201510329041.X, dated Jul. 31, 2018, with Search Report, 7 pages. |
Non-Final Office Action for U.S. Appl. No. 15/693,568, dated Aug. 9, 2018, 16 pages. |
Non-Final Office Action for U.S. Appl. No. 14/930,307, dated Feb. 23, 2018, 14 pages. |
Non-Final Office Action for U.S. Appl. No. 14/919,124, dated May 18, 2018, 14 pages. |
Extended Search Report for European Application No. 16744028.8 dated Oct. 31, 2018. |
Extended Search Report for European Application No. 16744033.8 dated Nov. 9, 2018. |
Non-Final Office Action dated Jan. 25, 2019, issued in related U.S. Appl. No. 14/919,124 (19 pages). |
Final Office Action dated Apr. 4, 2019, issued in related U.S. Appl. No. 15/693,568 (12 pages). |
Final Office Action dated Dec. 30, 2016, issued in related U.S. Appl. No. 14/639,711 (14 pages). |
Notice of Allowance dated May 19, 2017, issued in related U.S. Appl. No. 14/639,711 (11 pages). |
Notice of Allowance dated Jul. 11, 2018, issued in related U.S. Appl. No. 14/930,307 (7 pages). |
Notice of Allowance dated Mar. 16, 2018, issued in related U.S. Appl. No. 15/450,534 (7 pages). |
Notice of Allowance dated Mar. 28, 2017, issued in related U.S. Appl. No. 14/789,614 (6 pages). |
Notice of Allowance dated Apr. 20, 2018, issued in related U.S. Appl. No. 15/633,826 (23 pages). |
Non-Final Office Action dated May 3, 2018, issued in related U.S. Appl. No. 15/615,391 (13 pages). |
Notice of Allowance dated Oct. 19, 2018, issued in related U.S. Appl. No. 15/615,391 (8 pages). |
Second Office Action dated Apr. 1, 2019, issued in related Chinese Application No. 201510329041.X (8 pages), with English machine translation. |
Notice of Reasons for Rejection dated Oct. 29, 2019, issued in related Japanese Patent Application No. 2017-534352, with English machine translation (11 pages). |
Notice of Reasons for Refusal dated Oct. 8, 2019, issued in related Japanese Patent Application No. 2017-534348, with English machine translation (8 pages). |
Notice of Reasons for Rejection dated Jan. 21, 2020, issued in related Japanese Patent Application No. 2017-534348, with English machine translation (7 pages). |
Non-Final Office Action dated Sep. 17, 2019, issued in related U.S. Appl. No. 14/919,124 (19 pages). |
Office Action for European Application No. 16744033.8, dated Apr. 3, 2020, 4 pages. |
Office Action for European Application No. 16744028.8, dated Apr. 6, 2020, 5 pages. |
Number | Date | Country | |
---|---|---|---|
20170013399 A1 | Jan 2017 | US |
Number | Date | Country | |
---|---|---|---|
62110250 | Jan 2015 | US | |
62110262 | Jan 2015 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14639711 | Mar 2015 | US |
Child | 15276424 | US |