This disclosure relates generally to the field of Bluetooth communication and, more particularly, to methods, devices, and systems for Bluetooth audio transmission.
Bluetooth devices such as Bluetooth speakers, smart phones, smart locks, have become widely used in many applications. Conventionally, a Bluetooth enabled client device, such as a smart phone, may communicate to a Bluetooth device, such as a Bluetooth speaker or headset, within a short communication range, typically less than ten meters inside an indoor area. If a wall is located between the Bluetooth device and the client device, generally the Bluetooth transmission does not penetrate the wall, and as a result, communication may not be established between the Bluetooth device and the client device.
At a given time instant, a Bluetooth device may be controlled by a single client device and may not be controlled by multiple client devices simultaneously. For the Bluetooth device to switch from a current controlling client device to another controlling client device, a user associated with the current controlling client device may need to terminate the connection between the current controlling client device and the Bluetooth device, such that another client device may be paired to the Bluetooth device subsequently to gain control of the Bluetooth device. Moreover, where multiple Bluetooth devices are present and each of the devices is associated with a separate application interface, a user of the client device may have to start multiple different applications in order to control the multiple Bluetooth devices.
Thus, it is desirable to extend the communication range of Bluetooth devices without having to increase the transmission power or production cost of the Bluetooth devices. Further, it is desirable to allow multiple client devices to control the Bluetooth devices simultaneously and, in the meantime, provide a unified application interface for a user to manage the Bluetooth devices.
The present disclosure provides a device for providing audio data to a plurality of Bluetooth audio devices. Consistent with some embodiments, the device includes one or more Bluetooth transceivers for communicating with the plurality of Bluetooth audio devices, at least one network interface, one or more processors, and a memory for storing instructions executable by the one or more processors. The one or more processors may be configured to receive the audio data via the at least one network interface, decode the audio data for audio playing, and transmit the decoded audio data to the plurality of Bluetooth audio devices via the one or more Bluetooth transceivers.
Consistent with some embodiments, this disclosure provides a method for providing audio data to a plurality of Bluetooth audio devices. The method includes receiving the audio data via at least one network interface, decoding the audio data for audio playing, and transmitting the decoded audio data to the plurality of Bluetooth audio devices via one or more Bluetooth transceivers.
Consistent with some embodiments, this disclosure provides another device for providing audio data to a plurality of Bluetooth audio devices. The device includes one or more Bluetooth transceivers for communicating with the plurality of Bluetooth audio devices, an antenna, a radio frequency (RF) front end system communicatively coupled to the transceiver and the antenna, at least one network interface, one or more processors, and a memory for storing instructions executable by the one or more processors. The RF front end system includes a RF sampling block coupled to the one or more Bluetooth transceivers and configured to sample signals received from the one or more Bluetooth transceivers and output voltage signals, a RF switching logic coupled to the RF sampling block to receive the voltage signals and configured to switch the RF front end system between a transmitting mode and a receiving mode, a RF transmission gain block coupled to the RF switching logic and configured to increase a transmission power of the signals received from the one or more Bluetooth transceivers, and a RF receiving gain block coupled to the RF switching logic and configured to suppress noise signals contained in radio frequency signals received from the antenna. The one or more processors may be configured to receive the audio data via the at least one network interface, decode the audio data for audio playing, and transmit the decoded audio data to the plurality of Bluetooth audio devices via the one or more Bluetooth transceivers.
Consistent with some embodiments, this disclosure provides another device for providing audio data to a plurality of Bluetooth audio devices. The device includes a configurable antenna system including a plurality of antenna elements, one or more Bluetooth transceivers for communicating with the plurality of Bluetooth audio devices, an antenna logic system communicatively coupled to the one or more Bluetooth transceivers and the configurable antenna system, at least one network interface, one or more processors, and a memory for storing instructions executable by the one or more processors. Each of the antenna elements may be capable of being turned on or off to produce different antenna configurations. The one or more Bluetooth transceivers may be configured to generate a received signal strength indicator (RSSI) for each of the antenna configurations. The RSSI may be generated based on signals received from a client device. The antenna logic system may be configured to receive, from the one or more Bluetooth transceivers, the RSSI for each of the antenna configurations, select an antenna configuration among the antenna configurations based on the RSSI, and configure the configurable antenna system with the selected antenna configuration. The one or more processors may be configured to receive the audio data via the at least one network interface, decode the audio data for audio playing, and transmit the decoded audio data to the plurality of Bluetooth audio devices via the one or more Bluetooth transceivers.
Additional objects and advantages of the present disclosure will be set forth in part in the following detailed description, and in part will be obvious from the description, or may be learned by practice of the present disclosure. The objects and advantages of the present disclosure will be realized and attained by means of the elements and combinations particularly pointed out in the appended claims.
It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only, and are not restrictive of the invention, as claimed.
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.
As shown in
In some embodiments, the hub 120 may also support communication between a Bluetooth-enabled client device and a non-Bluetooth device. For example, a Bluetooth adapter (e.g., Bluetooth adapter 136) may be attached to the non-Bluetooth device (e.g., device 135), and the hub 120 may send and/or receive Bluetooth signals to the non-Bluetooth device through the Bluetooth adapter. For example, the Bluetooth adapter may be connected to a non-Bluetooth device, such as a non-Bluetooth speaker or headset, and enable the non-Bluetooth device to receive Bluetooth signals from a Bluetooth-enabled client device via the hub 120.
In some embodiments, the hub 120 may be used to increase the communication range between a Bluetooth-enabled client device and a Bluetooth device. For example, the hub 120 may be implemented with smart antennas and/or smart front end systems to extend the Bluetooth communication range. Methods and systems for implementing the hub 120 are described in 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 all of which are incorporated herein by reference.
In some embodiments, the client devices may communicate with the hub 120 through a network 150. For example, as shown in
In the following description, Bluetooth protocols and devices are used to illustrate the design of the hub 120. 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 Bluetooth chips 210 and 220 may each include a Bluetooth transceiver and be configured to communicate with Bluetooth devices, such as Bluetooth devices 140 and 145, and Bluetooth adapters 131 and 136. In some embodiments, each of the Bluetooth chips 210 and 220 may include one or more audio connections that can be used to output audio data. Each of the audio connections may be configured to output same or different audio data at a given time instant, so as to produce the desired sound effect. In some implementations, a sound server may be implemented in the Bluetooth hub 200 to route audio data to an appropriate Bluetooth audio device. The sound server may accept sound input from one or more sources and redirecting it to an appropriate Bluetooth audio device. For example, the Bluetooth hub 200 may include PulseAudio or other types of sound server.
The CPU 250 may be configured to execute instructions associated with operations of the Bluetooth hub 200. Additionally, the CPU 250 may execute certain instructions and commands to provide wireless communication, using the Bluetooth chips 210 and 220. The Bluetooth stack 240 may implement functionalities provided in the Bluetooth protocol. For example, the Bluetooth stack 240 may implement the scanning, pairing, and connection functions to establish a Bluetooth connection. The Bluetooth stack 250 may interact with the data bus 230 and/or the Bluetooth chips 210 and 220, and provide data output to the main CPU 240 and/or the application layer 260. The application layer 260 may be used for interacting with and managing end-user applications.
In some implementations, the Bluetooth stack 240 may include software programs designed to facilitate multimedia audio streaming from the Bluetooth hub 200 to a Bluetooth device, such as a Bluetooth speaker or headset. For example, the Bluetooth stack 240 may include Advanced Audio Distribution Profile (A2DP) that allows Bluetooth audio streaming from a Bluetooth enabled client device to a Bluetooth speaker or headset. As another example, the Bluetooth stack 240 may include Audio/Video Distribution Transport Protocol (AVDTP) protocol that specifies the transport protocol for audio and video distribution and streaming over the Bluetooth air interface. As another example, the Bluetooth stack 240 may include Audio/Video Remote Control Profile (AVRCP) protocol that allows a user to control media playback from Bluetooth audio devices, such as Bluetooth speakers or headsets.
In some implementations, the application layer 260 may include a media player used to decode audio and/or video files, such as open source media player MPlayer, window media player, or the like. For example, the hub 200 may perform online music streaming via the network 150 and the media player may be used for playing the audio files downloaded from the Internet.
The Bluetooth hub 200 may also include other auxiliary components, such as random access memory (RAM), read only memory (ROM), secondary storage (for example, a hard disk drive or flash memory). One skilled in the art will readily appreciate that various other components can also be included in the Bluetooth hub 200.
The Bluetooth hub 200 may communicate with a client device, such as a smart phone, on the application layer level, and communicate with the Bluetooth devices on the link layer level. For example, the Bluetooth hub 200 may communicate with a smart phone using WiFi, Bluetooth, or other communication protocols. When communicating with the Bluetooth devices, the Bluetooth hub 200 may operate as a master device that initiates an outgoing connection request to one of the Bluetooth devices that serve as slave devices.
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 chips 210 and 220 and Bluetooth stack 240 in
In some embodiments, the Bluetooth hub 320 may also be configured to communicate with Bluetooth light to change the color and brightness of the bulbs so as to create a particular mood effect. For example, the Bluetooth hub 320 may be configured to change the color of the Bluetooth lights based on the beat of the music that is being played.
In some embodiments, the Bluetooth hub 320 may receive the audio data from a Bluetooth enabled client device, such as a smart phone, a tablet or a computer that supports Bluetooth. For example, the audio data may be stored locally at the Bluetooth enabled client device, and the Bluetooth hub 320 may receive the audio data from the Bluetooth enabled client device via a Bluetooth air interface.
In other embodiments, the Bluetooth hub 320 may receive audio data by online music streaming. For example, the Bluetooth hub 320 may connect to music service sites on the Internet, stream music from the music service sites, and transmit audio signals to various Bluetooth speakers and/or Bluetooth headsets. Further, a user may select the music service site which the Bluetooth hub 320 streams music from by controlling the setting of the Bluetooth hub 320, for example, via a cloud-based server or via a direct connection with the Bluetooth hub using a Bluetooth enabled client device. The Bluetooth hub 320 may be subject to control of multiple users simultaneously. For example, user A may select a music service site for the Bluetooth hub 320 to stream online music, and subsequently user B may change the selected music service site by changing the setting of the Bluetooth hub 320 via a cloud-based server associated with the Bluetooth hub.
As shown in
The Bluetooth hub 320 may be connected to the Bluetooth speakers 310A-310D by performing a Bluetooth pairing procedure, which allows a Bluetooth slave device (e.g., the Bluetooth speaker) to be paired with a Bluetooth master device (e.g., the Bluetooth hub). Once a pairing procedure is completed, the paring information may be stored in the Bluetooth hub 320 and/or in a cloud-based server, and no additional pairing may be required in future to establish communication between the Bluetooth hub and the Bluetooth speakers.
In some embodiments, a user of the Bluetooth hub may share control of a Bluetooth audio device with another user. For example, a user may share control of a Bluetooth speaker with another user such that the other user may change the music played by the Bluetooth hub remotely through the cloud-based server associated with the Bluetooth hub.
In some embodiments, the Bluetooth hub 320 may be configured with a music playing mode for transmitting a particular combination of music and lighting control to the Bluetooth devices. For example, the Bluetooth hub 320 may be configured with a wake-up mode, which gradually increases volume of the corresponding Bluetooth speaker and intensity of the corresponding Bluetooth lighting. As another example, the Bluetooth hub 320 may be configured with a sleep mode, which gradually decreases volume of the corresponding Bluetooth speaker and intensity of the corresponding Bluetooth lighting. As another example, the Bluetooth hub 320 may be configured to play different types of music based on weather, user's mood, or the like. Other examples of applications of the Bluetooth hub include leaving a voice mail that is to be played via the Bluetooth speaker, playing online Karaoke television (KTV), and so on.
In some embodiments, an application may be installed on a client device, such as a smart phone, to manage operations of the Bluetooth hub and Bluetooth devices paired with the Bluetooth hub. During initial set up of the Bluetooth hub, a user may use the application to configure a WiFi network for the Bluetooth hub, and the Bluetooth hub may be configured to automatically scan available Bluetooth devices within its communication range. In some implementations, the Bluetooth hub may be configured to scan for only Bluetooth audio devices and LED lights nearby, and to ignore the other types of Bluetooth devices even if they are detected.
Another section included in the user interface may include general setting of the Bluetooth devices. For example, the general setting section may allow a user to select and/or change icons used to represent the Bluetooth devices, to activate or deactivate a particular Bluetooth device, to test the function of the Bluetooth devices, and so on. In the test mode, if the Bluetooth device is an audio device and is selected, a test sound may be generated by the Bluetooth device. If the Bluetooth device is a LED light and is selected for testing, the LED light may start flashing to indicate a normal operation status.
The user interface may also include a section to adjust the setting of each Bluetooth device individually. For example, for a Bluetooth audio device, the device setting may allow the user to adjust the volume of the audio device. As another example, for a Bluetooth LED light, the device setting may allow the user to adjust the intensity of the light in a sliding bar, adjust the color of the light by a color palette, or the like. Further, an automatic theme may be set for the Bluetooth LED light, such that the Bluetooth LED light may flash based on the music currently played by the Bluetooth audio device. For example, the Bluetooth LED light may identify the genre of the music based on the tag provided by the application programming interface (API) associated with the music, and set the theme based on the genre of the music. As another example, the Bluetooth LED light may adjust its color and brightness based on the rhythm of the music, such as using warm color and changing the color rapidly for fast rhythm, using cold color and changing the color slowly for slow rhythm, or the like. A customized theme may also be set for the Bluetooth LED light, where a predefined light color setting and/or flashing mode may be defined by the user in advance for a predefined theme, such as jazz, rock, and so on.
In some embodiments, if a user has set its user account in the Bluetooth hub for accessing the Internet music service site, the Bluetooth hub may access the music in the Internet music service site using the user's account. If a user account has not been set in the Bluetooth hub for accessing the Internet music service site, the Bluetooth hub may send a message to the client device and cause a prompt message to be displayed on the client device. The prompt message may request the user to enter user account information for accessing the Internet music service site, and after the user account information is entered, the information may be stored in the Bluetooth hub.
In some embodiments, when music is being played in one or more Bluetooth audio devices, and an incoming call is received by the client device, the Bluetooth hub may reduce the volume of the Bluetooth audio devices until the call is terminated. Further, in some embodiments, the Bluetooth audio devices in all the groups may be configured to play the same music synchronously. If the user selects another group and/or another song for playing, the synchronous playing by the Bluetooth audio devices may be terminated.
At step 902, the Bluetooth hub receives a user input from a client device, where the user input identifies a plurality of Bluetooth audio devices for playing audio data. For example, the Bluetooth hub may receive the user input from a network (e.g., network 150), via a network interface. As another example, the client device may be a Bluetooth-enabled client device (e.g., client device 110), and the Bluetooth hub may receive the user input from the client device via one or more Bluetooth transceivers. In some embodiments, the client device may provide a user interface for a user to select a group of Bluetooth audio devices for playing the audio data. For example, as illustrated in
At step 904, the Bluetooth hub receives the audio data via at least one network interface. For example, the Bluetooth hub may receive the audio data from the Internet by performing online audio and/or music streaming. As another example, the Bluetooth hub may receive the audio data by accessing a remote cloud-based network system. In other embodiments, the Bluetooth hub may receive the audio data from a Bluetooth-enabled client device via one or more Bluetooth transceivers.
At step 906, the Bluetooth hub decodes the audio data for audio playing. For example, a media player may be implemented in the Bluetooth hub to decode audio and/or video files.
At step 908, the Bluetooth hub transmits the decoded audio data to the plurality of Bluetooth audio devices via the one or more Bluetooth transceivers. In some embodiments, the same decoded audio data may be transmitted to the plurality of Bluetooth audio devices, such that the plurality of Bluetooth audio devices may play the decoded audio data at substantially the same time. In other embodiments, different decoded audio data may be transmitted to each of the plurality of Bluetooth audio devices to produce a surrounding sound effect, which will be described in more details in connection with
In some embodiments, the Bluetooth hub may receive a user input identifying an audio playing mode associated with the audio data. For example, the user input received in step 902 may also identify an audio playing mode associated with the audio data. As another example, a separate user input from that in step 902 may be received to identify an audio playing mode.
In some embodiments, the identified audio playing mode may be a sleep mode. In response, the Bluetooth hub may cause a volume of each of the plurality of Bluetooth audio devices to decrease gradually, for example, by sending one or more volume control commands to the Bluetooth audio devices. In other embodiments, the identified audio playing mode may be a wake-up mode. In response, the Bluetooth hub may cause a volume of each of the plurality of Bluetooth audio devices to increase gradually, for example, by sending one or more volume control commands to the Bluetooth audio devices.
In some embodiments, the Bluetooth hub may receive a user input identifying a theme associated with the audio data, such that a particular mood effect may be created by the Bluetooth hub. For example, the user input received in step 902 may also identify a theme associated with the audio data. As another example, a separate user input from that in step 902 may be received to identify a theme. In response to the theme identified in the user input, the Bluetooth hub may adjust, based on the theme, a light intensity and/or a color of a plurality of Bluetooth lighting devices via the one or more Bluetooth transceivers. For example, the Bluetooth hub may change the color of the Bluetooth lighting devices based on the beat of the music that is being played.
At step 1002, the Bluetooth hub sends a request to a client device for user account information associated with the audio data. For example, the source of the audio data may be from an Internet music service site, and the Bluetooth hub may send a request to the client device requesting the user account information for accessing the Internet music service site. As another example, the source of the audio data may be from a cloud-based network, and the Bluetooth hub may send a request to the client device requesting the user account information for accessing the cloud-based network. In some embodiments, the client device may provide a user interface for a user to enter the user account information. For example, a prompt message may be displayed on the client device prompting the user to enter the account information for the Bluetooth hub to access the Internet music service site.
At step 1004, the Bluetooth hub receives the user account information from the client device. The Bluetooth hub may store the received user account information such that it may use the stored information to access the Internet music service site in future.
At step 1006, the Bluetooth hub retrieves, based on the user account information, the audio data from Internet via at least one network interface. After the audio data is retrieved, the Bluetooth hub may perform steps 906 and 908 described above in connection with
At step 1102, the Bluetooth hub obtains a plurality of audio channels based on decoded audio data, where each of the audio channels includes a portion of the decoded audio data. For example, the Bluetooth hub may split the decoded audio data into multiple audio channels, and each of the audio channels includes different portion of the decoded audio data.
At step 1104, the Bluetooth hub determines an audio channel associated with each of the plurality of Bluetooth audio devices. For example, the Bluetooth hub may determine the audio channels associated with the Bluetooth audio devices based on the locations of the Bluetooth audio devices. In some implementations, the Bluetooth audio devices may be placed at different corners of an indoor area, and the Bluetooth hub may determine the audio channels associated with the Bluetooth audio devices based on the positions of the Bluetooth audio devices in the indoor area.
At step 1106, the Bluetooth hub transmits the portion of the decoded audio data corresponding to the associated audio channel to each of the plurality of Bluetooth audio devices. Thus, each of the Bluetooth audio devices receives audio data corresponding to a particular audio channel, and when the Bluetooth audio devices play simultaneously, a surrounding sound effect may be produced.
The specification has described methods, devices, and systems for Bluetooth audio transmission. 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.
This application is based on and claims priority to U.S. Provisional Application No. 62/187,956, filed Jul. 2, 2015, entitled “METHODS, DEVICES AND SYSTEMS FOR BLUETOOTH AUDIO TRANSMISSION.” This application is also a continuation-in-part application of application Ser. No. 14/639,711, titled “METHODS, DEVICES AND SYSTEMS FOR INCREASING WIRELESS COMMUNICATION RANGE,” filed Mar. 5, 2015, which is based upon and claims the benefit of priority from Provisional Application No. 62/110,250, titled “METHODS, DEVICES AND SYSTEMS FOR INCREASING WIRELESS COMMUNICATION RANGE,” filed on Jan. 30, 2015, and Provisional Application No. 62/110,262, titled “BLUETOOTH TRANSPARENT RELAY,” filed on Jan. 30, 2015. This application is also a continuation-in-part application of application Ser. No. 14/789,614, titled “METHODS, DEVICES AND SYSTEMS FOR SUPPORTING WIRELESS COMMUNICATION,” filed Jul. 1, 2015, which is based upon and claims the benefit of priority from Provisional Application No. 62/110,250, titled “METHODS, DEVICES AND SYSTEMS FOR INCREASING WIRELESS COMMUNICATION RANGE,” filed on Jan. 30, 2015, and Provisional Application No. 62/110,262, titled “BLUETOOTH TRANSPARENT RELAY,” filed on Jan. 30, 2015. The entire contents of the above-referenced U.S. patent applications including U.S. application Ser. Nos. 14/639,711, 14/789,614, 62/110,250, 62/110,262, and 62/187,956 are 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 | 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 et al. | 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, III | Nov 2005 | A1 |
20070041344 | Yaqub | Feb 2007 | A1 |
20070188358 | Somayajula | Aug 2007 | A1 |
20070222697 | Caimi | Sep 2007 | A1 |
20080043996 | Dolph et al. | Feb 2008 | A1 |
20080318549 | Skubic et al. | Dec 2008 | A1 |
20090011726 | Nishimura | Jan 2009 | A1 |
20090023499 | Mao | Jan 2009 | A1 |
20090063703 | Finkelstein | Mar 2009 | A1 |
20090147884 | Sridharan | Jun 2009 | A1 |
20090253373 | Gorbachov | Oct 2009 | A1 |
20090303387 | Chen et al. | 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 | 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 |
20120116548 | Goree | May 2012 | A1 |
20120165006 | Ge et al. | Jun 2012 | A1 |
20120200774 | Ehlers, Sr. | Aug 2012 | A1 |
20120326942 | Simmons | Dec 2012 | A1 |
20120329395 | Husted et al. | Dec 2012 | A1 |
20130007831 | Wu | Jan 2013 | A1 |
20130017816 | Talty | Jan 2013 | A1 |
20130033996 | Song | Feb 2013 | A1 |
20130045684 | Linde | Feb 2013 | A1 |
20130048734 | Bianconi et al. | Feb 2013 | A1 |
20130148020 | Cook et al. | Jun 2013 | A1 |
20130154897 | Sorensen | Jun 2013 | A1 |
20130254159 | Thramann | Sep 2013 | A1 |
20130337739 | Bernsen et al. | Dec 2013 | A1 |
20140006947 | Garmark | Jan 2014 | A1 |
20140041038 | Lessin et al. | Feb 2014 | A1 |
20140066062 | Chen et al. | Mar 2014 | A1 |
20140073244 | Ko et al. | Mar 2014 | A1 |
20140105054 | Saegrov | Apr 2014 | A1 |
20140119407 | Miller | May 2014 | A1 |
20140169569 | Toivanen | Jun 2014 | A1 |
20140169599 | Solum | Jun 2014 | A1 |
20140181656 | Kumar | 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 et al. | Nov 2014 | A1 |
20140342670 | Kang et al. | Nov 2014 | A1 |
20140370811 | Kang | Dec 2014 | A1 |
20150002425 | Lee et al. | Jan 2015 | A1 |
20150004913 | Linde et al. | Jan 2015 | A1 |
20150026746 | Fondberg | Jan 2015 | A1 |
20150031288 | Tubbesing | Jan 2015 | A1 |
20150039269 | Mejagard et al. | Feb 2015 | A1 |
20150095170 | Lang | Apr 2015 | A1 |
20150105022 | Jung | Apr 2015 | A1 |
20150105880 | Slupik | Apr 2015 | A1 |
20150128194 | Kuang | May 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 |
20160063778 | Bruns | 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 |
20160278011 | Tomida | 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 |
10-0818511 | Mar 2008 | KR |
2007033194 | Mar 2007 | WO |
2012150534 | Nov 2012 | WO |
2013086036 | Jun 2013 | WO |
2014082665 | Jun 2014 | WO |
Entry |
---|
International Search Report and Written Opinion for Application No. PCT/US2016/015617, dated Apr. 21, 2016, 17 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. |
Final Office Action for U.S. Appl. No. 15/450,534, dated Sep. 8, 2017, 10 pages. |
Final Office Action for U.S. Appl. No. 15/276,424, dated Sep. 22, 2017, 14 pages. |
Non- Final Office Action for U.S. Appl. No. 15/276,424, dated Mar. 24, 2017, 14 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. 15/450,534, dated Apr. 7, 2017, 8 pages. |
International Application No. PCT/US2016/015124, International Search Report and Written Opinion dated May 26, 2016. |
International Application No. PCT/US2016/015105, International Search Report and Written Opinion dated Jun. 3, 2016. |
Partial Search Report for European Application No. 16744028.8, dated on Jul. 25, 2018, 16 pages. |
Partial Search Report for European Application No. 16744033.8, dated on 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 US Appl. No. 15/693,568, dated on Aug. 9, 2018, 16 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 for U.S. Appl. No. 14/930,307, dated Feb. 23, 2018, 14 pages. |
Non-Final Office Action for U.S. Appl. No. 15/276,424, dated May 17, 2018, 14 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 to 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 to 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. |
Non-Final Office Action dated Jun. 17, 2016, issued in related U.S. Appl. No. 14/639,711, 14 pages. |
International Application No. PCT/US2017/036141, International Search report and Written Opinion dated Sep. 1, 2017. |
Non-Final Office Action dated May 27, 2016, issued in related U.S. Appl. No. 14/789,614, 16 pages. |
Final Office Action dated May 25, 2017, issued in related U.S. Appl. No. 14/930,307, 18 pages. |
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). |
Number | Date | Country | |
---|---|---|---|
20160227319 A1 | Aug 2016 | US |
Number | Date | Country | |
---|---|---|---|
62187956 | Jul 2015 | US | |
62110250 | Jan 2015 | US | |
62110262 | Jan 2015 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14789614 | Jul 2015 | US |
Child | 14919124 | US | |
Parent | 14639711 | Mar 2015 | US |
Child | 14789614 | US |