The present technology relates to consumer goods and, more particularly, to methods, systems, products, features, services, and other elements directed to media playback systems or some aspect thereof.
Options for accessing and listening to digital audio in an out-loud setting were limited until in 2003, when SONOS, Inc. filed for one of its first patent applications, entitled “Method for Synchronizing Audio Playback between Multiple Networked Devices,” and began offering a media playback system for sale in 2005. The SONOS Wireless HiFi System enables people to experience music from many sources via one or more networked playback devices. Through a software control application installed on a smartphone, tablet, or computer, one can play what he or she wants in any room that has a networked playback device. Additionally, using a controller, for example, different songs can be streamed to each room that has a playback device, rooms can be grouped together for synchronous playback, or the same song can be heard in all rooms synchronously.
Given the ever-growing interest in digital media, there continues to be a need to develop consumer-accessible technologies to further enhance the listening experience.
Features, aspects, and advantages of the presently disclosed technology may be better understood with regard to the following description, appended claims, and accompanying drawings.
The drawings are for purposes of illustrating example embodiments, but it should be understood that the inventions are not limited to the arrangements and instrumentality shown in the drawings. In the drawings, identical reference numbers identify at least generally similar elements. To facilitate the discussion of any particular element, the most significant digit or digits of any reference number refers to the Figure in which that element is first introduced. For example, element 103a is first introduced and discussed with reference to
I. Overview
Many audio playback devices, such as wireless headphones or other portable devices, provide vocal guidance to users in the form of audio output to deliver relevant information regarding operation or status of the playback device. Examples of such vocal guidance can include a power state (e.g., “your battery is at 10%”), a connection status (e.g., “connected to John's iPhone”), an indication of audio transport (e.g., “audio moved to the Bedroom”), an incoming call notification (e.g., “call from Jane”), or other such informational output. Because such playback devices may have limited memory and/or processing power, the available library of audio output for vocal guidance may be generally restricted to a handful of pre-selected words or phrases. Such limitations can be problematic when outputting information that can include a very large number of possible audio outputs. For example, indicating a connection status with an audio output in the form of “connected to device X” is challenging when “device X” can be any one of thousands of possible device names.
One possible workaround is to limit the output to a smaller subset of available information for which output audio can be stored locally on the device. For example, the output can simply be “connected to a device” or “connected to computer” without further specificity. This approach, however, may fail to provide the user relevant information, such as which particular device among the user's many devices is connected. Another possible workaround is to generate audio output dynamically using text-to-speech algorithms that translate text directly into audio output intended to represent a speaker reading the text. However, such text-to-speech approaches can result in unnatural and robotic-sounding audio output. This approach can be particularly undesirable when a device name (or other text field provided as input to the text-to-speech algorithm) is non-phonetic, such as a serial number or gibberish text string.
Yet another workaround is for the audio output to be generated remotely (e.g., via cloud servers) and transmitted to the playback device for audio playback. This approach, however, introduces additional latency due to the time needed to transmit requests to, and receive responses from, the remote servers. Additionally, this approach may sacrifice some degree of user privacy, as a user's information (e.g., source device names, etc.) may be transmitted over a wide area network to remote servers, unbeknownst to the user. Moreover, this approach can be power-intensive, resulting in a shorter battery life which can be particularly undesirable for portable audio playback devices such as headphones. Finally, this technique cannot be used when a wide area connection is unavailable.
Accordingly, there remains a need to provide useful vocal guidance to users of wireless audio playback devices. As described in more detail below, in some embodiments, wireless playback devices can include two wireless transceivers configured to communicate over separate data networks (e.g., WIFI and BLUETOOTH). In operation, the playback device may be paired locally with a source device over a first data network (e.g., pairing with a smartphone over a BLUETOOTH connection). The playback device can provide vocal guidance to the user at various stages of operation, for example to indicate a battery level, a connection status, an audio transport command, etc. In some embodiments, the playback device can provide vocal guidance regarding a connection status by receiving information from a source device such as a device ID, MAC address, device model, etc. The playback device may then access a library, which may be stored locally, to retrieve an appropriate audio output based at least in part on the device ID or other identifying information. For example, if the device ID of the connected source device is “Tom's Samsung Galaxy Tab S4,” the corresponding audio output based on accessing the library may be “Samsung Galaxy Tab.” This identified audio output can be stitched together as needed to generate a suitable output, such as “disconnected from Samsung Galaxy Tab.” This audio output take the form of a pre-recorded audio clip (or combination of clips), and so avoids undesirably robotic-sounding audio that can result from fully text-to-speech based approaches.
The vocal guidance described herein may be advantageously employed in any of a variety of specialized devices. For example, the vocal guidance may be implemented in a playback device having a distributed architecture. The playback device may comprise one or more amplifiers configured to drive one or more speakers. The one or more speakers may be integrated with the playback device (e.g., to form an all-in-one smart speaker) or separate from the playback device (e.g., to form a smart amplifier). The playback device may further comprise one or more network interface components to facilitate communication over one or more wireless networks. For example, the one or more network interface components may be capable of wirelessly communicating with a first computing device over a first wireless network (e.g., cellular network and/or a wireless local area network (WLAN)) and wirelessly communicating (e.g., simultaneously wirelessly communicating) with a second computing device over another network, such as a BLUETOOTH network. The playback device may further comprise a plurality of processing components configured to execute instructions that cause the playback device to perform various operations. The plurality of processing components may comprise low-power processor(s) and high-power processor(s) that are constructed differently from the low-power processor(s). Additionally, the low-power processor(s) may execute a different operating system than the high-power processor(s). For example, the high-power processor(s) may be configured to support virtual memory (e.g., an abstraction of the available storage resources) and execute an operating system that may at least partially employ virtualized memory, such as a General-Purpose Operating System (GPOS). In contrast, the low-power processor(s) may not be configured to support virtual memory and execute an operating system that does not require virtual memory support, such as a Real-Time Operating System (RTOS) or other Special-Purpose Operating System (SPOS).
It should be appreciated that the vocal guidance described herein may be advantageously employed in specialized devices separate and apart from playback devices. For example, the vocal guidance described herein may be employed in any Internet of Things (IoT) device. An IoT device may be, for example, a device designed to perform one or more specific tasks (e.g., making coffee, reheating food, locking a door, providing power to another device, playing music) based on information received via a network (e.g., a wide area network (WAN) such as the Internet). Examples of such IoT devices include: a smart thermostat, a smart doorbell, a smart lock (e.g., a smart door lock), a smart outlet, a smart light, a smart camera, a smart kitchen appliance (e.g., a smart oven, a smart coffee maker, a smart microwave), and a smart speaker (including the network accessible and/or voice-enabled playback devices described above).
While some embodiments described herein may refer to functions performed by given actors, such as “users” and/or other entities, it should be understood that this description is for purposes of explanation only. The claims should not be interpreted to require action by any such example actor unless explicitly required by the language of the claims themselves.
II. Example Operating Environment
Within these rooms and spaces, the MPS 100 includes one or more computing devices. Referring to
With reference still to
As further shown in
In some implementations, the various playback devices, NMDs, and/or controller devices 102-104 may be communicatively coupled to at least one remote computing device associated with a voice assistant service (“VAS”) and at least one remote computing device associated with a media content service (“MCS”). For instance, in the illustrated example of
As further shown in
In various implementations, one or more of the playback devices 102 may take the form of or include an on-board (e.g., integrated) network microphone device. For example, the playback devices 102a-e include or are otherwise equipped with corresponding NMDs 103a-e, respectively. A playback device that includes or is equipped with an NMD may be referred to herein interchangeably as a playback device or an NMD unless indicated otherwise in the description. In some cases, one or more of the NMDs 103 may be a stand-alone device. For example, the NMDs 103f and 103g may be stand-alone devices. A stand-alone NMD may omit components and/or functionality that is typically included in a playback device, such as a speaker or related electronics. For instance, in such cases, a stand-alone NMD may not produce audio output or may produce limited audio output (e.g., relatively low-quality audio output).
The various playback and network microphone devices 102 and 103 of the MPS 100 may each be associated with a unique name, which may be assigned to the respective devices by a user, such as during setup of one or more of these devices. For instance, as shown in the illustrated example of
As discussed above, an NMD may detect and process sound from its environment, such as sound that includes background noise mixed with speech spoken by a person in the NMD's vicinity. For example, as sounds are detected by the NMD in the environment, the NMD may process the detected sound to determine if the sound includes speech that contains voice input intended for the NMD and ultimately a particular VAS. For example, the NMD may identify whether speech includes a wake word associated with a particular VAS.
In the illustrated example of
Upon receiving the stream of sound data, the VAS 190 determines if there is voice input in the streamed data from the NMD, and if so the VAS 190 will also determine an underlying intent in the voice input. The VAS 190 may next transmit a response back to the MPS 100, which can include transmitting the response directly to the NMD that caused the wake-word event. The response is typically based on the intent that the VAS 190 determined was present in the voice input. As an example, in response to the VAS 190 receiving a voice input with an utterance to “Play Hey Jude by The Beatles,” the VAS 190 may determine that the underlying intent of the voice input is to initiate playback and further determine that intent of the voice input is to play the particular song “Hey Jude.” After these determinations, the VAS 190 may transmit a command to a particular MCS 192 to retrieve content (i.e., the song “Hey Jude”), and that MCS 192, in turn, provides (e.g., streams) this content directly to the MPS 100 or indirectly via the VAS 190. In some implementations, the VAS 190 may transmit to the MPS 100 a command that causes the MPS 100 itself to retrieve the content from the MCS 192.
In certain implementations, NMDs may facilitate arbitration amongst one another when voice input is identified in speech detected by two or more NMDs located within proximity of one another. For example, the NMD-equipped playback device 102d in the environment 101 (
In certain implementations, an NMD may be assigned to, or otherwise associated with, a designated or default playback device that may not include an NMD. For example, the Island NMD 103f in the Kitchen 101h (
Further aspects relating to the different components of the example MPS 100 and how the different components may interact to provide a user with a media experience may be found in the following sections. While discussions herein may generally refer to the example MPS 100, technologies described herein are not limited to applications within, among other things, the home environment described above. For instance, the technologies described herein may be useful in other home environment configurations comprising more or fewer of any of the playback, network microphone, and/or controller devices 102-104. For example, the technologies herein may be utilized within an environment having a single playback device 102 and/or a single NMD 103. In some examples of such cases, the local network 111 (
While specific implementations of MPS's have been described above with respect to
a. Example Playback & Network Microphone Devices
As shown, the playback device 102 includes at least one processor 212, which may be a clock-driven computing component configured to process input data according to instructions stored in memory 213. The memory 213 may be a tangible, non-transitory, computer-readable medium configured to store instructions that are executable by the processor 212. For example, the memory 213 may be data storage that can be loaded with software code 214 that is executable by the processor 212 to achieve certain functions.
In one example, these functions may involve the playback device 102 retrieving audio data from an audio source, which may be another playback device. In another example, the functions may involve the playback device 102 sending audio data, detected-sound data (e.g., corresponding to a voice input), and/or other information to another device on a network via at least one network interface 224. In yet another example, the functions may involve the playback device 102 causing one or more other playback devices to synchronously playback audio with the playback device 102. In yet a further example, the functions may involve the playback device 102 facilitating being paired or otherwise bonded with one or more other playback devices to create a multi-channel audio environment. Numerous other example functions are possible, some of which are discussed below.
As just mentioned, certain functions may involve the playback device 102 synchronizing playback of audio content with one or more other playback devices. During synchronous playback, a listener may not perceive time-delay differences between playback of the audio content by the synchronized playback devices. U.S. Pat. No. 8,234,395 filed on Apr. 4, 2004, and titled “System and method for synchronizing operations among a plurality of independently clocked digital data processing devices,” which is hereby incorporated by reference in its entirety, provides in more detail some examples for audio playback synchronization among playback devices.
To facilitate audio playback, the playback device 102 includes audio processing components 216 that are generally configured to process audio prior to the playback device 102 rendering the audio. In this respect, the audio processing components 216 may include one or more digital-to-analog converters (“DAC”), one or more audio preprocessing components, one or more audio enhancement components, one or more digital signal processors (“DSPs”), and so on. In some implementations, one or more of the audio processing components 216 may be a subcomponent of the processor 212. In operation, the audio processing components 216 receive analog and/or digital audio and process and/or otherwise intentionally alter the audio to produce audio signals for playback.
The produced audio signals may then be provided to one or more audio amplifiers 217 for amplification and playback through one or more speakers 218 operably coupled to the amplifiers 217. The audio amplifiers 217 may include components configured to amplify audio signals to a level for driving one or more of the speakers 218.
Each of the speakers 218 may include an individual transducer (e.g., a “driver”) or the speakers 218 may include a complete speaker system involving an enclosure with one or more drivers. A particular driver of a speaker 218 may include, for example, a subwoofer (e.g., for low frequencies), a mid-range driver (e.g., for middle frequencies), and/or a tweeter (e.g., for high frequencies). In some cases, a transducer may be driven by an individual corresponding audio amplifier of the audio amplifiers 217. In some implementations, a playback device may not include the speakers 218, but instead may include a speaker interface for connecting the playback device to external speakers. In certain embodiments, a playback device may include neither the speakers 218 nor the audio amplifiers 217, but instead may include an audio interface (not shown) for connecting the playback device to an external audio amplifier or audio-visual receiver.
In addition to producing audio signals for playback by the playback device 102, the audio processing components 216 may be configured to process audio to be sent to one or more other playback devices, via the network interface 224, for playback. In example scenarios, audio content to be processed and/or played back by the playback device 102 may be received from an external source, such as via an audio line-in interface (e.g., an auto-detecting 3.5 mm audio line-in connection) of the playback device 102 (not shown) or via the network interface 224, as described below.
As shown, the at least one network interface 224, may take the form of one or more wireless interfaces 225 and/or one or more wired interfaces 226. A wireless interface may provide network interface functions for the playback device 102 to wirelessly communicate with other devices (e.g., other playback device(s), NMD(s), and/or controller device(s)) in accordance with a communication protocol (e.g., any wireless standard including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.11ad, 802.11af, 802.11ah, 802.11ai, 802.11aj, 802.11aq, 802.11ax, 802.11ay, 802.15, BLUETOOTH, 4G mobile communication standard, 5G mobile communication standard, and so on). A wired interface may provide network interface functions for the playback device 102 to communicate over a wired connection with other devices in accordance with a communication protocol (e.g., IEEE 802.3). While the network interface 224 shown in
In general, the network interface 224 facilitates data flow between the playback device 102 and one or more other devices on a data network. For instance, the playback device 102 may be configured to receive audio content over the data network from one or more other playback devices, network devices within a LAN, and/or audio content sources over a WAN, such as the Internet. In one example, the audio content and other signals transmitted and received by the playback device 102 may be transmitted in the form of digital packet data comprising an Internet Protocol (IP)-based source address and IP-based destination addresses. In such a case, the network interface 224 may be configured to parse the digital packet data such that the data destined for the playback device 102 is properly received and processed by the playback device 102.
As shown in
In operation, the voice-processing components 220 are generally configured to detect and process sound received via the microphones 222, identify potential voice input in the detected sound, and extract detected-sound data to enable a VAS, such as the VAS 190 (
In some implementations, the voice-processing components 220 may detect and store a user's voice profile, which may be associated with a user account of the MPS 100. For example, voice profiles may be stored as and/or compared to variables stored in a set of command information or data table. The voice profile may include aspects of the tone or frequency of a user's voice and/or other unique aspects of the user's voice, such as those described in previously referenced U.S. Patent Publication No. 2017/0242653.
As further shown in
In some implementations, the power components 227 of the playback device 102 may additionally include an internal power source 229 (e.g., one or more batteries) configured to power the playback device 102 without a physical connection to an external power source. When equipped with the internal power source 229, the playback device 102 may operate independent of an external power source. In some such implementations, the external power source interface 228 may be configured to facilitate charging the internal power source 229. As discussed before, a playback device comprising an internal power source may be referred to herein as a “portable playback device.” Those portable playback devices that weigh no more than fifty ounces (e.g., between three ounces and fifty ounces, between five ounces and fifty ounces, between ten ounces and fifty ounces, between ten ounces and twenty-five ounces, etc.) may be referred to herein as an “ultra-portable playback device.” Those playback devices that operate using an external power source instead of an internal power source may be referred to herein as a “stationary playback device,” although such a device may in fact be moved around a home or other environment.
The playback device 102 may further include a user interface 240 that may facilitate user interactions independent of or in conjunction with user interactions facilitated by one or more of the controller devices 104. In various embodiments, the user interface 240 includes one or more physical buttons and/or supports graphical interfaces provided on touch sensitive screen(s) and/or surface(s), among other possibilities, for a user to directly provide input. The user interface 240 may further include one or more of lights (e.g., LEDs) and the speakers to provide visual and/or audio feedback to a user.
As an illustrative example,
As further shown in
As mentioned above, the playback device 102 may be constructed as a portable playback device, such as an ultra-portable playback device, that comprises an internal power source.
In some embodiments, the playback device 102 may take the form of a wired and/or wireless headphone (e.g., an over-ear headphone, an on-ear headphone, or an in-ear headphone). For instance,
It should be appreciated that the playback device 102 may take the form of other wearable devices separate and apart from a headphone. Wearable devices may include those devices configured to be worn about a portion of a subject (e.g., a head, a neck, a torso, an arm, a wrist, a finger, a leg, an ankle, etc.). For example, the playback device 102 may take the form of a pair of glasses including a frame front (e.g., configured to hold one or more lenses), a first temple rotatably coupled to the frame front, and a second temple rotatable coupled to the frame front. In this example, the pair of glasses may comprise one or more transducers integrated into at least one of the first and second temples and configured to project sound towards an ear of the subject.
While specific implementations of playback and network microphone devices have been described above with respect to
By way of illustration, SONOS, Inc. presently offers (or has offered) for sale certain playback devices that may implement certain of the embodiments disclosed herein, including a “SONOS ONE,” “PLAY:1,” “PLAY:3,” “PLAY:5,” “PLAYBAR,” “AMP,” “CONNECT:AMP,” “PLAYBASE,” “BEAM,” “CONNECT,” and “SUB.” Any other past, present, and/or future playback devices may additionally or alternatively be used to implement the playback devices of example embodiments disclosed herein. Additionally, it should be understood that a playback device is not limited to the examples illustrated in
b. Example Playback Device Configurations
For purposes of control, each zone in the MPS 100 may be represented as a single user interface (“UI”) entity. For example, as displayed by the controller devices 104, Zone A may be provided as a single entity named “Portable,” Zone B may be provided as a single entity named “Stereo,” and Zone C may be provided as a single entity named “Living Room.”
In various embodiments, a zone may take on the name of one of the playback devices belonging to the zone. For example, Zone C may take on the name of the Living Room device 102m (as shown). In another example, Zone C may instead take on the name of the Bookcase device 102d. In a further example, Zone C may take on a name that is some combination of the Bookcase device 102d and Living Room device 102m. The name that is chosen may be selected by a user via inputs at a controller device 104. In some embodiments, a zone may be given a name that is different than the device(s) belonging to the zone. For example, Zone B in
As noted above, playback devices that are bonded may have different playback responsibilities, such as playback responsibilities for certain audio channels. For example, as shown in
Additionally, playback devices that are configured to be bonded may have additional and/or different respective speaker drivers. As shown in
In some implementations, playback devices may also be “merged.” In contrast to certain bonded playback devices, playback devices that are merged may not have assigned playback responsibilities, but may each render the full range of audio content that each respective playback device is capable of. Nevertheless, merged devices may be represented as a single UI entity (i.e., a zone, as discussed above). For instance,
In some embodiments, a stand-alone NMD may be in a zone by itself. For example, the NMD 103h from
Zones of individual, bonded, and/or merged devices may be arranged to form a set of playback devices that playback audio in synchrony. Such a set of playback devices may be referred to as a “group,” “zone group,” “synchrony group,” or “playback group.” In response to inputs provided via a controller device 104, playback devices may be dynamically grouped and ungrouped to form new or different groups that synchronously play back audio content. For example, referring to
In various implementations, the zones in an environment may be assigned a particular name, which may be the default name of a zone within a zone group or a combination of the names of the zones within a zone group, such as “Dining Room+Kitchen,” as shown in
Referring back to
In some embodiments, the memory 213 of the playback device 102 may store instances of various variable types associated with the states. Variables instances may be stored with identifiers (e.g., tags) corresponding to type. For example, certain identifiers may be a first type “a1” to identify playback device(s) of a zone, a second type “1” to identify playback device(s) that may be bonded in the zone, and a third type “c1” to identify a zone group to which the zone may belong. As a related example, in
In yet another example, the MPS 100 may include variables or identifiers representing other associations of zones and zone groups, such as identifiers associated with Areas, as shown in
The memory 213 may be further configured to store other data. Such data may pertain to audio sources accessible by the playback device 102 or a playback queue that the playback device (or some other playback device(s)) may be associated with. In embodiments described below, the memory 213 is configured to store a set of command data for selecting a particular VAS when processing voice inputs.
During operation, one or more playback zones in the environment of
As suggested above, the zone configurations of the MPS 100 may be dynamically modified. As such, the MPS 100 may support numerous configurations. For example, if a user physically moves one or more playback devices to or from a zone, the MPS 100 may be reconfigured to accommodate the change(s). For instance, if the user physically moves the playback device 102c from the Patio zone to the Office zone, the Office zone may now include both the playback devices 102c and 102n. In some cases, the user may pair or group the moved playback device 102c with the Office zone and/or rename the players in the Office zone using, for example, one of the controller devices 104 and/or voice input. As another example, if one or more playback devices 102 are moved to a particular space in the home environment that is not already a playback zone, the moved playback device(s) may be renamed or associated with a playback zone for the particular space.
Further, different playback zones of the MPS 100 may be dynamically combined into zone groups or split up into individual playback zones. For example, the Dining Room zone and the Kitchen zone may be combined into a zone group for a dinner party such that playback devices 102i and 102l may render audio content in synchrony. As another example, bonded playback devices in the Den zone may be split into (i) a television zone and (ii) a separate listening zone. The television zone may include the Front playback device 102b. The listening zone may include the Right, Left, and SUB playback devices 102a, 102j, and 102k, which may be grouped, paired, or merged, as described above. Splitting the Den zone in such a manner may allow one user to listen to music in the listening zone in one area of the living room space, and another user to watch the television in another area of the living room space. In a related example, a user may utilize either of the NMD 103a or 103b (
c. Example Controller Devices
The memory 413 of the controller device 104 may be configured to store controller application software and other data associated with the MPS 100 and/or a user of the system 100. The memory 413 may be loaded with instructions in software 414 that are executable by the processor 412 to achieve certain functions, such as facilitating user access, control, and/or configuration of the MPS 100. The controller device 104 may be configured to communicate with other network devices via the network interface 424, which may take the form of a wireless interface, as described above.
In one example, system information (e.g., such as a state variable) may be communicated between the controller device 104 and other devices via the network interface 424. For instance, the controller device 104 may receive playback zone and zone group configurations in the MPS 100 from a playback device, an NMD, or another network device. Likewise, the controller device 104 may transmit such system information to a playback device or another network device via the network interface 424. In some cases, the other network device may be another controller device.
The controller device 104 may also communicate playback device control commands, such as volume control and audio playback control, to a playback device via the network interface 424. As suggested above, changes to configurations of the MPS 100 may also be performed by a user using the controller device 104. The configuration changes may include adding/removing one or more playback devices to/from a zone, adding/removing one or more zones to/from a zone group, forming a bonded or merged player, separating one or more playback devices from a bonded or merged player, among others.
As shown in
The playback control region 442 (
The playback zone region 443 (
For example, as shown, a “group” icon may be provided within each of the graphical representations of playback zones. The “group” icon provided within a graphical representation of a particular zone may be selectable to bring up options to select one or more other zones in the MPS 100 to be grouped with the particular zone. Once grouped, playback devices in the zones that have been grouped with the particular zone will be configured to play audio content in synchrony with the playback device(s) in the particular zone. Analogously, a “group” icon may be provided within a graphical representation of a zone group. In this case, the “group” icon may be selectable to bring up options to deselect one or more zones in the zone group to be removed from the zone group. Other interactions and implementations for grouping and ungrouping zones via a user interface are also possible. The representations of playback zones in the playback zone region 443 (
The playback status region 444 (
The playback queue region 446 may include graphical representations of audio content in a playback queue associated with the selected playback zone or zone group. In some embodiments, each playback zone or zone group may be associated with a playback queue comprising information corresponding to zero or more audio items for playback by the playback zone or zone group. For instance, each audio item in the playback queue may comprise a uniform resource identifier (URI), a uniform resource locator (URL), or some other identifier that may be used by a playback device in the playback zone or zone group to find and/or retrieve the audio item from a local audio content source or a networked audio content source, which may then be played back by the playback device.
In one example, a playlist may be added to a playback queue, in which case information corresponding to each audio item in the playlist may be added to the playback queue. In another example, audio items in a playback queue may be saved as a playlist. In a further example, a playback queue may be empty, or populated but “not in use” when the playback zone or zone group is playing continuously streamed audio content, such as Internet radio that may continue to play until otherwise stopped, rather than discrete audio items that have playback durations. In an alternative embodiment, a playback queue can include Internet radio and/or other streaming audio content items and be “in use” when the playback zone or zone group is playing those items. Other examples are also possible.
When playback zones or zone groups are “grouped” or “ungrouped,” playback queues associated with the affected playback zones or zone groups may be cleared or re-associated. For example, if a first playback zone including a first playback queue is grouped with a second playback zone including a second playback queue, the established zone group may have an associated playback queue that is initially empty, that contains audio items from the first playback queue (such as if the second playback zone was added to the first playback zone), that contains audio items from the second playback queue (such as if the first playback zone was added to the second playback zone), or a combination of audio items from both the first and second playback queues. Subsequently, if the established zone group is ungrouped, the resulting first playback zone may be re-associated with the previous first playback queue or may be associated with a new playback queue that is empty or contains audio items from the playback queue associated with the established zone group before the established zone group was ungrouped. Similarly, the resulting second playback zone may be re-associated with the previous second playback queue or may be associated with a new playback queue that is empty or contains audio items from the playback queue associated with the established zone group before the established zone group was ungrouped. Other examples are also possible.
With reference still to
The sources region 448 may include graphical representations of selectable audio content sources and/or selectable voice assistants associated with a corresponding VAS. The VASes may be selectively assigned. In some examples, multiple VASes, such as AMAZON's Alexa, MICROSOFT's Cortana, etc., may be invokable by the same NMD. In some embodiments, a user may assign a VAS exclusively to one or more NMDs. For example, a user may assign a first VAS to one or both of the NMDs 102a and 102b in the Living Room shown in
d. Example Audio Content Sources
The audio sources in the sources region 448 may be audio content sources from which audio content may be retrieved and played by the selected playback zone or zone group. One or more playback devices in a zone or zone group may be configured to retrieve for playback audio content (e.g., according to a corresponding URI or URL for the audio content) from a variety of available audio content sources. In one example, audio content may be retrieved by a playback device directly from a corresponding audio content source (e.g., via a line-in connection). In another example, audio content may be provided to a playback device over a network via one or more other playback devices or network devices. As described in greater detail below, in some embodiments, audio content may be provided by one or more media content services.
Example audio content sources may include a memory of one or more playback devices in a media playback system such as the MPS 100 of
In some embodiments, audio content sources may be added or removed from a media playback system such as the MPS 100 of
III. Example Distributed Processing Architectures
A distributed processor architecture may be employed in devices, such as playback devices or other IoT devices, to significantly reduce power consumption. For example, a high-power processor that executes a GPOS may be employed, in at least some respects, as a co-processor to a less powerful (and less power hungry) processor executing an SPOS. As a result, the high-power processor can be completely powered off in situations where the functionality of the high-power processor is not needed without interrupting other operations, such as reading one or more capacitive touch sensors to detect audio playback commands, obtaining audio content via BLUETOOTH, and/or playing back the audio content. An example of a device employing such a distributed processing architecture is shown in
As shown in
The network interface component(s) 502 may facilitate wireless communication to one or more external devices shown as the first computing device 510 and the second computing device 516. The network interface component(s) 502 may comprise the first network circuit 520 that enables communication over the first communication link 512 using a first communication protocol and a second network circuit 522 that enables communication over the second communication link 518 using a second, different communication protocol. For example, the first network circuit 520 may enable communication using an IEEE 802 protocol and/or a cellular network protocol while the second network circuit 522 may enable communication using another protocol, such as a BLUETOOTH protocol. Thus, the network interface component(s) 502 may enable communication (e.g., simultaneous communication) with multiple computing devices using different communication protocols.
In some embodiments, the first network circuit 520 may be implemented as a WI-FI circuit (e.g., comprising a WI-FI transceiver) that is configured to communicate with the first computing device 510 over a WI-FI network. In these embodiments, the first computing device 510 may be, for example, a network router and/or a computing device that is accessible over the Internet (e.g., a cloud server). Additionally (or alternatively), the second network circuit 522 may be implemented as a BLUETOOTH circuit (e.g., comprising a BLUETOOTH transceiver) that is configured to communicate with the second computing device 516 using a BLUETOOTH connection. In such instances, the second computing device 516 may be, for example, a portable computing device such as a smartphone or a tablet.
The network circuits 520 and 522 may comprise one or more network processors that execute instructions stored in a memory that cause the network circuits 520 and 522 to perform various operations. For example, the network circuits 520 and 522 may each comprise a read-only memory (ROM) that stores firmware that may be executed by the one or more network processors. Examples of ROM include programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), and electrically erasable programmable read-only memory (EEPROM). Additionally (or alternatively), the network circuits 520 and 522 may comprise a read-write memory (e.g., a memory that is both readable and writable) that stores instructions that may be executed by the one or more network processors.
It should be appreciated that the network interface component(s) 502 may be implemented as one or more circuit dies. For example, the network interface component(s) 502 may be implemented as a single circuit die. In another example, the first network circuit 510 may be implemented as a first circuit die and the second network circuit 522 may be implemented as a second circuit die. Thus, the network interface component(s) 502 may be implemented in any of a variety of ways.
The processing components 504 may be coupled to the network interface component(s) 502 and configured to control one or more aspects of the operation of the device 500. The processing components 504 may comprise first processor(s) 524 and second processor(s) 526. The first processor(s) 524 may have a different construction than the second processor(s) 526. Additionally, the first processor(s) 524 may execute first operating system(s) 528 while the second processors 526 may execute second operating system(s) 530 that are different from the first operating system(s) 528.
In some embodiments, the first processor(s) 501 may not be configured to support virtualized memory and the first operating system(s) 528 may comprise an operating system that does not require support for virtualized memory, such as a RTOS or other SPOS. For example, the first processor(s) 524 may not comprise a memory management unit (MMU) configured to translate virtual memory addresses to physical addresses. In these embodiments, the first processor(s) 524 may comprise a general-purpose processor (GPP), such as a reduced instruction set computer (RISC) processor, and/or a single-purpose processor (SPP), such as a DSP or a neural processing unit (NPU). For example, the first processor(s) 524 may comprise a RISC processor and a DSP. Example GPPs that do not support virtualized memory include ARM CORTEX-M series processors (e.g., CORTEX-MO, CORTEX-MO+, CORTEX-M1, CORTEX-M3, CORTEX-M4, CORTEX-M7, CORTEX-M23, CORTEX-M33, and CORTEX-M35P processors). Example SPPs that do not support virtualized memory include TENSILICA HIFI DSPs (e.g., HIFI MINI, HIFI 3, HIFI 3z, HIFI 4, and HIFI 5 DSPs).
In some embodiments, the second processor(s) 526 may be configured to support virtualized memory and the second operating system(s) 530 may comprise an operating system that at least partially employs virtualized memory. For example, the second processor(s) 526 may comprise a memory management unit (MMU) configured to translate virtual memory addresses to physical addresses. In these embodiments, the second processor(s) 526 may comprise a GPP. Example GPPs that support virtualized memory include ARM CORTEX-A series processors (e.g., CORTEX-A5, CORTEX-A7, CORTEX-A8, CORTEX-A9, CORTEX-A12, CORTEX-A15, CORTEX-A17, CORTEX-A32, CORTEX-A35, CORTEX-A53, CORTEX-A57, CORTEX-A72, CORTEX-A73, CORTEX-A75, CORTEX-A76 processors).
One or more of the processors in the plurality of processing components 504 (e.g., first processor(s) 524 and/or second processor(s) 526) may have a plurality of power states including an awake state and one or more low-power states (e.g., one or more sleep states such as a light sleep state and a deep sleep state). In an awake state, the processor may be capable of executing instructions, power may be maintained to the processor caches (e.g., L1, L2, and/or L3 caches), and the clocks may be on (e.g., core clock, bus clock, etc.). In light sleep states, the power consumption may be reduced relative to the awake states by turning off one or more clocks while maintaining power to the processor caches. Thus, light sleep states may offer some power consumption reduction relative to awake states while still being able to transition to awake states expeditiously. In deep sleep states, the power consumption may be reduced relative to the light sleep states by both turning off one or more clocks and powering down one or more processor caches. Deep sleep states may include those states where the processor is entirely powered off. Thus, deep sleep states may offer an additional power consumption reduction relative to light sleep states and require additional time to transition to awake states relative to light sleep states.
Given that the first processor(s) 524 may have a different construction that the second processor(s) 526, the first processor(s) 524 may have a different peak power consumption (e.g., power consumption under full load) than the second processor(s) 526. For example, the first processor(s) 524 may have a lower peak power consumption than the second processor(s) 526. The difference in power consumption may arise at least in part from the increased complexity of the second processor(s) 526 to provide, for example, virtual memory support. Thus, in some embodiments, operations are distributed between the first processor(s) 524 and the second processor(s) 526 such that only those operations that cannot be practically performed by the first processor(s) 524 are performed by the second processor(s) 526. In these embodiments, the first processor(s) 524 may cause the second processor(s) 526 to remain in a low-power state until a particular operation needs to be performed that requires the second processor(s) 526. As a result, the second processor(s) 526 may, in at least some respects, function as one or more co-processors to the first processor(s) 524.
The data storage 506 may comprise, for example, one or more tangible, non-transitory, computer-readable media configured to store instructions that are executable by the processing components 504. The data storage 506 may comprise any combination of volatile memory (e.g., a memory that only maintains data while powered) and non-volatile memory (e.g., a memory that maintains data even after being power cycled). Examples of volatile memory include random-access memory (RAM) such as static random-access memory (SRAM) and dynamic random-access memory (DRAM). Examples of non-volatile memory include flash memory, such as NOR flash memory and NAND flash memory, disk drives, and magnetic tape.
The data storage 506 may comprise a first memory 532 and a second memory 534. In some embodiments, the first memory 532 may be only directly accessible by the first processor(s) 524 (and thus not be directly accessible by the second processor(s) 526) and the second memory 534 may be only directly accessible by the second processor(s) 526 (and thus not be directly accessible by the first processor(s) 524). In these embodiments, the first and second processor(s) 524 and 526, respectively, may share information via one or more communication buses, such as a SPI bus. In other embodiments, at least one of the first memory 532 and the second memory 534 may be a shared memory that is directly accessible by both the first processor(s) 524 and the second processor(s) 526. In these embodiments, the first and second processor(s) 524 and 526, respectively, may share information by storing the information to be shared in the shared memory. Additionally (or alternatively), the first and second processor(s) 524 and 526, respectively, may share information via one or more communication buses.
In some embodiments, the first operating system(s) 528, first processor(s) 524, and the first memory 532 can together be configured to provide vocal guidance as described in more detail elsewhere herein. For example, when the playback device is coupled to the second computing device 516 (e.g., a source device such as a smartphone) over the second communication link 518 (e.g., a BLUETOOTH connection) via the second network circuit 522, the playback device can provide vocal guidance to inform the user of the connection status. For example, the device may play back corresponding audio such as “connected to John's iPhone.” In at least some embodiments, these operations can be performed entirely using the first processor(s) 524 and the first memory 532, without necessarily requiring operation of the second processor(s) 526 and second memory 534. This approach can reduce power consumption by providing vocal guidance while relying only on the less power-hungry first processor(s) 524. In at least some embodiments, the corresponding audio can be selected using a library of pre-recorded audio clips, which can be stored in the first memory 532. As described in more detail below, particular audio clips can be selected and optionally combined to provide suitable vocal guidance to the user. Additionally or alternatively, the library of pre-recorded audio clips and/or the vocal guidance engine itself can be revised, updated, or overwritten periodically by receiving updates from a first computing device 510 (e.g., one or more remote servers) over the first communication link 512 (e.g., a WLAN connection). In such instances, the information and instructions to update the vocal guidance engine and/or the library can be transmitted from the second processor(s) 526 to the first processor(s) 524, and/or the second processor(s) 526 may update the first memory 532 directly.
It should be appreciated that the processing components 504 and the data storage 506 may be implemented in any of a variety of ways. In some embodiments, each of the first processor(s) 524 are separate and distinct from the second processor(s) 526. For example, the first processor(s) 524 may combined with at least part of the first memory 532 in a first system-on-chip (SoC) and the second processor(s) 526 may be combined with at least part of the second memory 534 in a second SoC that is separate from the first SoC. In other embodiments, the first processor(s) 524 may be combined with the second processor(s) 526 in a single circuit die. For example, the first processor(s) 524, the one or more circuit processors 526, at least part of the first memory 532, and at least part of the second memory 534 may be integrated into a single SoC. Thus, the processing components 504 and the data storage 506 may be implemented in any number of circuit dies.
The electronic component(s) 508 may comprise any of a variety of components that the processing components 504 may control or otherwise communicate with. Examples of such components include: a display, an electric motor, a heating element, a switch, a speaker, a light, and a sensor (e.g., a microphone, a capacitive touch sensor, an infrared light sensor, etc.). The implementation of the electronic component(s) 508 may vary based on the particular function of the device 500. For example, the device 500 may be a playback device and the electronic component(s) 508 may comprise a speaker for sound reproduction and one or more capacitive touch sensors for detection of audio playback commands (e.g., play/pause, increase volume, decrease volume, etc.).
Some electronic component(s) 508 may not directly interface with the processing components 504. Instead, these electronic component(s) 508 may interface with the processing components 504 via intermediary component(s) 514. For example, the electronic component(s) 508 may comprise a capacitive touch sensor that the processing components 504 may not be able to directly read. In this example, the intermediary component(s) 514 may comprise a programmable SoC (PSoC) that is configured to read the capacitive touch sensor and provide an output over a communication bus (e.g., an I2C bus) that may be received by the processing components 504. Other example intermediary component(s) 514 include audio codecs and amplifiers (e.g., class D audio amplifiers).
In some embodiments, only the first processor(s) 524 communicate (e.g., is communicatively coupled) with the intermediary component(s) 514 and/or the electronic component(s) 508. Thus, the second processor(s) 526 may not directly communication with the intermediary component(s) 514 and/or electronic component(s) 508. By routing all communication with the intermediary component(s) 514 and/or the electronic component(s) 508 through the first processor(s) 524, the second processor(s) 526 may be completely turned off without interfering with such communication. For example, the first processor(s) 524 may communicate with intermediary component(s) 514 over an I2C bus that is not directly accessible by the second processor(s) 526 (e.g., the second processor(s) 526 cannot directly transmit and/or receive data over the I2C bus).
In some embodiments, the second processor(s) 526 may be booted before the first processor(s) 524. For example, the second processor(s) 526 may initially boot first and provide code to the first processor(s) 524 over a communication bus, such as a SPI bus. The first processor(s) 524 may boot upon receipt of the code from the second processor(s) 526. Once the first processor(s) 524 have completed booting, the second processor(s) 526 may be put in a low-power state should the second processor(s) 526 no longer be needed. In other embodiments, the first processor(s) 524 may be booted before second processor(s) 526.
It should be appreciated that one or more components may be omitted from the device 500 without departing from the scope of the present disclosure. In some embodiments, the device 500 may only communicate using a single protocol (or set of protocols), such as IEEE 802 protocols, and the second network circuit 522 that enables communication with the second computing device 516 may be omitted. Additionally (or alternatively), the electronic component(s) 508 in the device 500 may not need any of the intermediary component(s) 514. For example, the electronic component(s) 508 may only include components that may directly interface with the processing components 504. Thus, the intermediary component(s) 514 may be omitted.
In some embodiments, aspects of the distributed architecture shown in
The circuit board 602 may comprise a substrate (e.g., an insulative substrate) and a plurality of conductive elements (e.g., circuit traces, pads, vias, etc.). The substrate may provide mechanical support for the components mounted to the circuit board 602. The substrate may be a rigid substrate (e.g., to form a rigid circuit board) or a flexible substrate (e.g., to form a flexible circuit board). The plurality of conductive elements may be disposed on and/or integrated with the substrate to couple (e.g., electrically couple) components attached to the circuit board 602.
The power component(s) 612 may distribute power to one or more other components of the module 600 (e.g., other components attached to the circuit board 602). The power component(s) 614 may perform, for example, any combination of the following operations: (1) DC/DC conversion, (2) battery charging, and (3) power sequencing. The power component(s) 614 may be implemented as, for example, a power management integrated circuit (PMIC). The power component(s) 612 may receive power from a power source 614 via a power interface 604. The power source 614 may comprise an internal power source, such as a battery, and/or an external power source, such as a wall outlet. The power interface 604 may comprise one or more ports (e.g., one or more electrical connectors attached to the circuit board 602) where the module 600 may be coupled (e.g., electrically coupled) to the power source 604.
The processing components 504 and the data storage 506 may be attached to the circuit 602 in a variety of ways depending on, for example, how the processing components 504 and the data storage 506 are constructed. In some embodiments, the processing components 504 and the data storage 506 may be integrated into a single system-on-a-chip (SoC) that may be attached to the circuit board 602. In other embodiments, the processing components 504 and the data storage 506 may be integrated into separate circuit dies that may be separately attached to the circuit board 602 (e.g., and electrically coupled using circuit traces). For example, first processor(s) (e.g., first processor(s) 524) and a first portion of the data storage 506 (e.g., a volatile memory accessible by the first processor(s)) may be integrated into a first SoC, the second processor(s) (e.g., second processor(s) 526) and a second portion of the data storage 506 (e.g., a volatile memory accessible by the second processor(s)) may be integrated into a second SoC, and a remainder of the data storage 506 (e.g., a non-volatile memory accessible by the first and/or second processors) may be integrated into a separate memory integrated circuit (IC). In this example, each of the first SoC, the second SoC, and the memory IC may be attached to the circuit board 602. Thus, the processing components 504 and the data storage 506 may be distributed between any number of ICs that may be attached to the circuit board 602.
The network interface component(s) 502 may be distributed between the internal network interface component(s) 616A that may be attached to the circuit board 602 and the external network interface component(s) 616B that may be external to the module 600. The internal network interface component(s) 616A may be coupled to the external network interface component(s) 616B via a communication interface 606. The communication interface 606 may comprise one or more ports (e.g., one or more electrical connectors attached to the circuit board 602) where the module 600 may be coupled (e.g., electrically coupled) to the external network interface component(s) 616B. The particular way in which the network interface component(s) 502 are distributed may vary based on the particular implementation. In some embodiments, the internal network interface component(s) 616A may comprise one or more ICs to generate wireless signals including, for example, one or more wireless transceiver ICs (e.g., a WI-FI transceiver IC, a BLUETOOTH transceiver IC, or a WI-FI and
BLUETOOTH transceiver IC) while the external network interface component(s) 616B may comprise one or more components that radiate the wireless signal (e.g., one or more antennas). In other embodiments, all of the network interface component(s) 502 may be integrated into the internal network interface component(s) 616A and the communication interface 606 may be removed. In still yet other embodiments, all of the network interface component(s) 502 may integrated into the external network interface component(s) 616B and the communication interface 606 may couple the processing components to the external network interface component(s) 616B.
The intermediary component(s) 514 may be distributed between the internal intermediary component(s) 610A that may be attached to the circuit board 602 and the external intermediary component 610B that may be external to the module 600. The internal intermediary component(s) 610A may be coupled to the external intermediary component 610B via an electronic component interface 608. The electronic component interface 608 may comprise one or more ports (e.g., one or more electrical connectors attached to the circuit board 602) where the module 600 may be coupled (e.g., electrically coupled) to the external intermediary component(s) 610B. The particular way in which the intermediary component(s) 514 are distributed may vary based on the particular implementation. In some embodiments, all of the intermediary component(s) 514 may be integrated into the internal network interface component(s) 616A. For example, the internal intermediary component(s) 610A may comprise one or more audio amplifiers that are coupled (via the electronic component interface 608) to electronic component(s) 508, such as one or more speakers. In other embodiments, each of the internal intermediary component(s) 610A and the external intermediary component(s) 610B may comprise at least one component. In still yet other embodiments, all of the intermediary component(s) 514 may be integrated into the external network interface component(s) 616B.
It should be appreciated that the module 600 shown in
IV. Vocal Guidance Systems and Methods
As noted previously, audio playback devices may provide vocal guidance to users to communicate relevant information regarding operation or status of the playback device. Such vocal guidance can be particularly useful in the case of wireless playback devices, as vocal guidance can be used to provide information regarding a battery level, a connection status (e.g., BLUETOOTH connection to or disconnection from a particular source device), an incoming call notification, or other such informational output.
Another example of vocal guidance relates to audio transfer between playback devices. Certain media playback systems may be capable of “moving” audio playback from one device to another. For example, a user listening to audio content via wireless headphones while away from home may later return home and wish to transfer audio playback from the wireless headphones to stationary devices placed in the user's home. In some embodiments, the user may provide instructions to transfer the audio playback (e.g., by activating one or more buttons on the headphones). In response, the media playback system may determine the appropriate destination playback device(s), after which audio playback may continue on those devices and may be discontinued on the wireless headphones. In some instances, it can be useful to alert the user of this activity, for example by providing vocal guidance. As one example, if the media playback system transfers audio playback from the wireless headphones to a playback device located in the user's living room, the vocal guidance can take the form of audio output played back via the wireless headphones such as “audio moved to Living Room.”
Because audio playback devices may have limited memory and/or processing power, the available library of pre-recorded audio output for vocal guidance may be generally restricted to a handful of pre-selected words or phrases. In particular, there is a need to provide sufficient information to a user via vocal guidance without necessarily relying on remote computing devices to generate the audio output.
The vocal guidance control 702 also receives an input of the device state 708, which can be or include, for example a BLUETOOTH connectivity status, a battery level, incoming call information, an audio transport activity, or other such device information. In operation, the control 702 may drive output of vocal guidance based on the device state 708, the rules database 704, and the library 706 together. For example, when the playback device is newly connected to a source device via a BLUETOOTH connection (as reflected in the device state 708), the control 702 accesses the rules database 704 and the library 706 to either select a suitable audio output 712, and/or to synthesize an audio output 710. For example, if an entire audio output is stored in the library 706, the audio output can be selected for playback as vocal guidance. Alternatively, various audio clips in the vocal guidance library 706 can be selected and combined for output. For example, a first audio clip of “connected to” and a second clip of “iPhone” can be combined together to a single audio output. In some embodiments, some or all of the audio output can be synthesized using a text-to-speech algorithm, which translates textual information into an audio file. Such synthesized audio output can optionally be combined with pre-recorded audio clips stored in the library 706. Whether synthesized or selected, the audio output is transmitted for playback (block 714) to audio playback components (e.g., amplifiers, electroacoustic transducers, etc.).
As noted previously, some wireless playback devices can include two wireless transceivers configured to communicate over separate data networks (e.g., WIFI and BLUETOOTH). In operation, the playback device may be paired locally with a source device over a first data network (e.g., pairing with a smartphone over a BLUETOOTH connection). In some embodiments, the playback device can provide vocal guidance regarding a connection status by receiving information from a source device such as a device ID, MAC address, device model, etc. The control 702 may then access the library 706 and the rules database 704 to retrieve or synthesize an appropriate audio output based at least in part on the identity of the source device. For example, if the device ID of the connected source device is “Tom's Samsung Galaxy Tab S4,” the corresponding audio output based on accessing the library may be “Samsung Galaxy Tab.” This identified audio output can be stitched together as needed to generate a suitable output, such as “disconnected from Samsung Galaxy Tab.” This audio output may be a pre-recorded audio file (or combination of files) stored in the library 706, and so avoids undesirably robotic-sounding audio that can result from fully text-to-speech based approaches.
In various embodiments, the library 706 and/or the rules database 704 can be updated or revised. For example, the library 706 may be language-specific, and accordingly may be overwritten with a different library if the user selects a different language for the device. Additionally or alternatively, the library may be updated to include additional audio clips (e.g., additional device names, room names, etc.). In such instances, updating the rules database 704 and/or the library 706 can involve communicating with one or more remote computing devices over a wide area network connection (e.g., over a WI-FI connection).
In some embodiments, the rules database 704 can include one or more rules that specify which audio clips to be played back under various conditions and when to stitch them together. For example, the rules database can specify certain combinations of variables which can then be associated with particular audio clips in the library 706. For example, in the case of a newly connected source device over BLUETOOTH, the rules database 704 can include a rule specifying a combination of the outputs “connected to” and “<device name>” where <device name> is a variable that can be populated with a particular entry in the library 706. In various examples, the particular rules 704 can be language-agnostic or may be specific to particular languages or sets of languages.
Table 1 illustrates an example of various parameters that can be used for vocal guidance. As shown below, exemplary types of parameters include device name, caller name, battery level, music service provider name, language, voice assistant name (e.g., ALEXA), and room name (e.g., “Bedroom”). In various embodiments, the device name can be or include information obtained via a BLUETOOTH or other suitable wireless communication network. For example, a connection over BLUETOOTH can provide a device ID as well as a Class of Device (CoD) field. The device ID may be user-customized or can include default values set by a manufacturer or retailer.
In various embodiments, a plurality of audio clips can be pre-recorded and stored (e.g., in the library 706) for each of the parameter types. For example, for “battery level,” pre-recorded audio clips ranging from 5% to 100%, in 5% increments, can be stored. Similarly, pre-recorded audio clips can be stored that correspond to specified music service providers, languages, voice assistants, and rooms. With respect to device names, a set of audio clips can be stored in the library 706 corresponding to various hardware devices likely to be encountered as source devices. For example, a plurality of audio clips can be stored in the library 706 corresponding to audio output of “iPhone,” “Samsung Galaxy Tab,” and other such device names.
Table 2 illustrates examples of various audio clips that can be pre-recorded that can be used for vocal guidance. As shown below, these example clips can be stored (e.g., in the library 706) for use in providing vocal guidance.
Table 3 illustrates an example of vocal guidance in the form of rule-based audio outputs based on particular events. For example, when battery status is to be output via vocal guidance, the vocal guidance control 702 can access the rule (“1, B”) in the rules database 704. The audio associated with Clip ID 1 in Table 2 is then concatenated with value B from Table 1, resulting in an audio output of “your battery is at 90%.” The other listed rules can be applied similarly, providing rule-based audio outputs that provide relevant information to a user in the form of vocal guidance.
The examples shown in Tables 1-3 are for purposes of illustration only, and one of skill in the art will readily appreciate that there may be many variations in the particular parameters, rules, and audio outputs listed here. Additionally, the rules can include further complexity such as exceptions (e.g., scenarios in which the rule should not be applied, or in which the rule should be varied), and fallback values for audio output when a particular value is not identified. For example, if a room name is not identified, the audio output can provide an output corresponding to the particular playback device to which audio is moved (e.g., “Sound moved to Beam”).
In various examples, the rules can include logic for matching one or more parameters to particular audio clips. This matching may be straightforward for certain parameters. For example, battery levels can be rounded to the nearest 5% and matched to the corresponding pre-recorded audio with the selected percentage value. Similarly, room names can be selected from pre-defined lists, and so each room name can be matched via an exact text match to a pre-defined list of all possible room names and corresponding audio output. Voice assistant names and music service provider names may likewise be selected using an exact-match lookup from pre-identified lists of possible names of voice assistants and music service providers that are supported by the playback device.
In various embodiments, audio outputs associated with the parameter type “caller name” may either be synthesized using a text-to-speech algorithm or pre-recorded audio corresponding to a plurality of common names can be stored in the library 706. Additionally or alternatively, the playback device may determine whether or not the incoming call matches a stored contact in the user's device or other address book, and may provide an output in the form of “call from known contact” or “call from unknown contact.”
As noted previously, the device name can be or include information obtained from the source device itself, for example via a BLUETOOTH or other suitable wireless communication network. In some embodiments, when the source device connects to the playback device via a BLUETOOTH or other suitable connection, the source device can provide a device ID as well as a Class of Device (CoD) and any other such identifying information. The device ID may be user-customized or can include default values set by a manufacturer or reseller. As such, providing vocal guidance that incorporates a device name can be challenging due to the wide range of values that can be found in this field.
To address these challenges, the rules for matching a particular source device to a suitable pre-recorded audio output can take a number of forms. In some embodiments, the device ID provided by the source device can be searched against a list of device names stored in the library 706. Based on textual overlap, a particular device name stored in the library 706 can be matched to the particular device ID. For example, if the device ID is “Jared's iPhone X,” the source device may be matched to the device name “iPhone X” and a corresponding audio clip can be used to provide an audio output (e.g., “connected to iPhone X”).
In some embodiments, the device ID may not match (e.g., may have no or insufficient textual overlap with) any of the device names stored in the library 706. In such instances, a fallback device name can be used for audio output. The fallback value may be, for example, based on the Class of Device field (e.g., “smartphone,” “laptop,” etc.), based on the manufacturer (e.g., as determined using a MAC address, serial number, or other such information), or the fallback can be a catch-all term such as “device.” Accordingly, if no specific device name is matched to the particular source device, the vocal guidance may provide an audio output such as “connected to smartphone,” “connected to Samsung device,” or simply “connected to device.”
In at least some instances, the rules can be language-agnostic, such that only the particular parameters and associated pre-recorded audio outputs need to be updated or revised when switching between one language and another. Depending on the particular grammatical structure, in some instances some or all of the rules themselves may also be modified as needed.
In some embodiments, the library of pre-recorded audio clips, the rules database, and/or any component of the vocal guidance engine can be revised, updated, or overwritten periodically by receiving updates from an external computing device. For example, the library may be updated to be populated with room names that correspond to the rooms that have been identified with that particular user account or media playback system. As another example, the playback device may transmit text to be associated with new audio output, such as a particular name or word for which the library does not currently have an associated audio clip. The remote computing devices may in turn generate or retrieve a suitable audio clip which can then be transmitted to the playback device, for example by updating the library. In some examples, the playback device may retrieve updated vocal guidance data only when connected via a wide area communications network (e.g., via a WIFI connection). As noted previously, wireless playback devices with distributed architectures may only periodically communicate via such networks and/or may only periodically activate the associated processors and memory. As such, by only updating the library when connected to a wide area network, the power consumption can be reduced.
In block 804, the playback device receives information via a first wireless data network. This wireless data network can be different from the wireless data network over which the playback device is coupled with the source device. In some examples, the first wireless data network is a WIFI network. The information received over the WIFI network can be used to update the library (block 806). For example, the information can include new source device names, new audio content, or new rules indicating when a particular audio content should be played back based on the source device ID or other information. Based on this information, the playback device can update the library, for example by expanding the library or by overwriting at least a portion of the library.
In block 808, the playback device connects to a particular source device over a second wireless data network. In some examples, the second wireless data network can be different from the first. In some instances, the first data network can be a WIFI network and the second data network can be a BLUETOOTH network.
The method 800 continues in block 810 with retrieving audio content from the library that is associated with the connected source device. For example, as described previously, the source device can provide information to the playback device, such as a device ID, device class, etc. The playback device may access the library to search for a match for the device ID or other such identifying information. The match can be an exact match, a partial match, a match with the greatest degree of textual overlap, or a match identified using any other suitable criteria. Once the source device is matched to a particular device name and associated audio content in the library, the retrieved audio content is played back (block 812). For example, if the source device provides a device ID of “Sally's Surface Pro,” the playback device may access the library and find a closest match for a device name of “Surface Pro.” The playback device may play back an audio output that includes this match, for example the phrase “connected to Surface Pro.”
As noted previously, the vocal guidance described herein may be advantageously employed in specialized devices separate and apart from playback devices. For example, the vocal guidance described herein may be employed in any Internet of Things (IoT) device. An IoT device may be, for example, a device designed to perform one or more specific tasks (e.g., making coffee, reheating food, locking a door, providing power to another device, playing music) based on information received via a network (e.g., a wide area network (WAN) such as the Internet). Examples of such IoT devices include: a smart thermostat, a smart doorbell, a smart lock (e.g., a smart door lock), a smart outlet, a smart light, a smart camera, a smart kitchen appliance (e.g., a smart oven, a smart coffee maker, a smart microwave), and a smart speaker (including the network accessible and/or voice-enabled playback devices described above).
V. Conclusion
The description above discloses, among other things, various example systems, methods, apparatus, and articles of manufacture including, among other components, firmware and/or software executed on hardware. It is understood that such examples are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of the firmware, hardware, and/or software aspects or components can be embodied exclusively in hardware, exclusively in software, exclusively in firmware, or in any combination of hardware, software, and/or firmware. Accordingly, the examples provided are not the only way(s) to implement such systems, methods, apparatus, and/or articles of manufacture.
It should be appreciated that references to transmitting information to particular components, devices, and/or systems herein should be understood to include transmitting information (e.g., messages, requests, responses) indirectly or directly to the particular components, devices, and/or systems. Thus, the information being transmitted to the particular components, devices, and/or systems may pass through any number of intermediary components, devices, and/or systems prior to reaching its destination. For example, a control device may transmit information to a playback device by first transmitting the information to a computing system that, in turn, transmits the information to the playback device. Further, modifications may be made to the information by the intermediary components, devices, and/or systems. For example, intermediary components, devices, and/or systems may modify a portion of the information, reformat the information, and/or incorporate additional information.
Similarly, references to receiving information from particular components, devices, and/or systems herein should be understood to include receiving information (e.g., messages, requests, responses) indirectly or directly from the particular components, devices, and/or systems. Thus, the information being received from the particular components, devices, and/or systems may pass through any number of intermediary components, devices, and/or systems prior to being received. For example, a control device may receive information from a playback device indirectly by receiving information from a cloud server that originated from the playback device. Further, modifications may be made to the information by the intermediary components, devices, and/or systems. For example, intermediary components, devices, and/or systems may modify a portion of the information, reformat the information, and/or incorporate additional information.
The specification is presented largely in terms of illustrative environments, systems, procedures, steps, logic blocks, processing, and other symbolic representations that directly or indirectly resemble the operations of data processing devices coupled to networks. These process descriptions and representations are typically used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art. Numerous specific details are set forth to provide a thorough understanding of the present disclosure. However, it is understood to those skilled in the art that certain embodiments of the present disclosure can be practiced without certain, specific details. In other instances, well known methods, procedures, components, and circuitry have not been described in detail to avoid unnecessarily obscuring aspects of the embodiments. Accordingly, the scope of the present disclosure is defined by the appended claims rather than the forgoing description of embodiments.
When any of the appended claims are read to cover a purely software and/or firmware implementation, at least one of the elements in at least one example is hereby expressly defined to include a tangible, non-transitory medium such as a memory, DVD, CD, Blu-ray, and so on, storing the software and/or firmware.
The present application claims the benefit of priority to U.S. Patent Application No. 62/706,560, filed Aug. 25, 2020, which is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
4741038 | Elko et al. | Apr 1988 | A |
4941187 | Slater | Jul 1990 | A |
4974213 | Siwecki | Nov 1990 | A |
5036538 | Oken et al. | Jul 1991 | A |
5440644 | Farinelli et al. | Aug 1995 | A |
5588065 | Tanaka et al. | Dec 1996 | A |
5740260 | Odom | Apr 1998 | A |
5761320 | Farinelli et al. | Jun 1998 | A |
5923902 | Inagaki | Jul 1999 | A |
5949414 | Namikata et al. | Sep 1999 | A |
6032202 | Lea et al. | Feb 2000 | A |
6088459 | Hobelsberger | Jul 2000 | A |
6256554 | DiLorenzo | Jul 2001 | B1 |
6301603 | Maher et al. | Oct 2001 | B1 |
6311157 | Strong | Oct 2001 | B1 |
6366886 | Dragosh et al. | Apr 2002 | B1 |
6404811 | Cvetko et al. | Jun 2002 | B1 |
6408078 | Hobelsberger | Jun 2002 | B1 |
6469633 | Wachter | Oct 2002 | B1 |
6522886 | Youngs et al. | Feb 2003 | B1 |
6594347 | Calder et al. | Jul 2003 | B1 |
6594630 | Zlokarnik et al. | Jul 2003 | B1 |
6611537 | Edens et al. | Aug 2003 | B1 |
6611604 | Irby et al. | Aug 2003 | B1 |
6631410 | Kowalski et al. | Oct 2003 | B1 |
6757517 | Chang | Jun 2004 | B2 |
6778869 | Champion | Aug 2004 | B2 |
6937977 | Gerson | Aug 2005 | B2 |
7099821 | Visser et al. | Aug 2006 | B2 |
7103542 | Doyle | Sep 2006 | B2 |
7130608 | Hollstrom et al. | Oct 2006 | B2 |
7130616 | Janik | Oct 2006 | B2 |
7143939 | Henzerling | Dec 2006 | B2 |
7174299 | Fujii et al. | Feb 2007 | B2 |
7228275 | Endo et al. | Jun 2007 | B1 |
7236773 | Thomas | Jun 2007 | B2 |
7295548 | Blank et al. | Nov 2007 | B2 |
7356471 | Ito et al. | Apr 2008 | B2 |
7383297 | Atsmon et al. | Jun 2008 | B1 |
7391791 | Balassanian et al. | Jun 2008 | B2 |
7483538 | McCarty et al. | Jan 2009 | B2 |
7571014 | Lambourne et al. | Aug 2009 | B1 |
7577757 | Carter et al. | Aug 2009 | B2 |
7630501 | Blank et al. | Dec 2009 | B2 |
7643894 | Braithwaite et al. | Jan 2010 | B2 |
7657910 | McAulay et al. | Feb 2010 | B1 |
7661107 | Van Dyke et al. | Feb 2010 | B1 |
7702508 | Bennett | Apr 2010 | B2 |
7792311 | Holmgren et al. | Sep 2010 | B1 |
7853341 | McCarty et al. | Dec 2010 | B2 |
7961892 | Fedigan | Jun 2011 | B2 |
7987294 | Bryce et al. | Jul 2011 | B2 |
3014423 | Thaler et al. | Sep 2011 | A1 |
8019076 | Lambert | Sep 2011 | B1 |
8032383 | Bhardwaj et al. | Oct 2011 | B1 |
8041565 | Bhardwaj et al. | Oct 2011 | B1 |
8045952 | Qureshey et al. | Oct 2011 | B2 |
8073125 | Zhang et al. | Dec 2011 | B2 |
8073681 | Baldwin et al. | Dec 2011 | B2 |
8103009 | McCarty et al. | Jan 2012 | B2 |
8136040 | Fleming | Mar 2012 | B2 |
8165867 | Fish | Apr 2012 | B1 |
8234395 | Millington | Jul 2012 | B2 |
8239206 | LeBeau et al. | Aug 2012 | B1 |
8255224 | Singleton et al. | Aug 2012 | B2 |
8284982 | Bailey | Oct 2012 | B2 |
8290603 | Lambourne | Oct 2012 | B1 |
8340975 | Rosenberger | Dec 2012 | B1 |
8364481 | Strope et al. | Jan 2013 | B2 |
8385557 | Tashev et al. | Feb 2013 | B2 |
8386261 | Mellott et al. | Feb 2013 | B2 |
8386523 | Mody et al. | Feb 2013 | B2 |
8423893 | Ramsay et al. | Apr 2013 | B2 |
8428758 | Naik et al. | Apr 2013 | B2 |
8453058 | Coccaro et al. | May 2013 | B1 |
8473618 | Spear et al. | Jun 2013 | B2 |
8483853 | Lambourne | Jul 2013 | B1 |
8484025 | Moreno et al. | Jul 2013 | B1 |
8588849 | Patterson et al. | Nov 2013 | B2 |
8600443 | Kawaguchi et al. | Dec 2013 | B2 |
8710970 | Oelrich et al. | Apr 2014 | B2 |
8719039 | Sharifi | May 2014 | B1 |
8738925 | Park et al. | May 2014 | B1 |
8775191 | Sharifi et al. | Jul 2014 | B1 |
8831761 | Kemp et al. | Sep 2014 | B2 |
8831957 | Taubman et al. | Sep 2014 | B2 |
8848879 | Coughlan et al. | Sep 2014 | B1 |
8861756 | Zhu et al. | Oct 2014 | B2 |
8874448 | Kauffmann et al. | Oct 2014 | B1 |
8938394 | Faaborg et al. | Jan 2015 | B1 |
8942252 | Balassanian et al. | Jan 2015 | B2 |
8983383 | Haskin | Mar 2015 | B1 |
8983844 | Thomas et al. | Mar 2015 | B1 |
9015049 | Baldwin et al. | Apr 2015 | B2 |
9042556 | Kallai et al. | May 2015 | B2 |
9060224 | List | Jun 2015 | B1 |
9094539 | Noble | Jul 2015 | B1 |
9098467 | Blanksteen et al. | Aug 2015 | B1 |
9124650 | Maharajh et al. | Sep 2015 | B2 |
9124711 | Park et al. | Sep 2015 | B2 |
9148742 | Koulomzin et al. | Sep 2015 | B1 |
9190043 | Krisch et al. | Nov 2015 | B2 |
9208785 | Ben-David et al. | Dec 2015 | B2 |
9215545 | Dublin et al. | Dec 2015 | B2 |
9245527 | Lindahl | Jan 2016 | B2 |
9251793 | Lebeau et al. | Feb 2016 | B2 |
9253572 | Beddingfield, Sr. et al. | Feb 2016 | B2 |
9262612 | Cheyer | Feb 2016 | B2 |
9263042 | Sharifi | Feb 2016 | B1 |
9275637 | Salvador et al. | Mar 2016 | B1 |
9288597 | Carlsson et al. | Mar 2016 | B2 |
9300266 | Grokop | Mar 2016 | B2 |
9304736 | Whiteley et al. | Apr 2016 | B1 |
9307321 | Unruh | Apr 2016 | B1 |
9318107 | Sharifi | Apr 2016 | B1 |
9319816 | Narayanan | Apr 2016 | B1 |
9324322 | Torok et al. | Apr 2016 | B1 |
9335819 | Jaeger et al. | May 2016 | B1 |
9361878 | Boukadakis | Jun 2016 | B2 |
9361885 | Ganong, III et al. | Jun 2016 | B2 |
9368105 | Freed et al. | Jun 2016 | B1 |
9373329 | Strope et al. | Jun 2016 | B2 |
9374634 | Macours | Jun 2016 | B2 |
9386154 | Baciu et al. | Jul 2016 | B2 |
9390708 | Hoffmeister | Jul 2016 | B1 |
9401058 | De La Fuente et al. | Jul 2016 | B2 |
9412392 | Lindahl et al. | Aug 2016 | B2 |
9426567 | Lee et al. | Aug 2016 | B2 |
9431021 | Scalise et al. | Aug 2016 | B1 |
9443527 | Watanabe et al. | Sep 2016 | B1 |
9472201 | Sleator | Oct 2016 | B1 |
9472203 | Ayrapetian et al. | Oct 2016 | B1 |
9484030 | Meaney et al. | Nov 2016 | B1 |
9489948 | Chu et al. | Nov 2016 | B1 |
9494683 | Sadek | Nov 2016 | B1 |
9509269 | Rosenberg | Nov 2016 | B1 |
9510101 | Polleros | Nov 2016 | B1 |
9514476 | Kay et al. | Dec 2016 | B2 |
9514752 | Sharifi | Dec 2016 | B2 |
9516081 | Tebbs et al. | Dec 2016 | B2 |
9536541 | Chen et al. | Jan 2017 | B2 |
9548053 | Basye et al. | Jan 2017 | B1 |
9548066 | Jain et al. | Jan 2017 | B2 |
9552816 | Vanlund et al. | Jan 2017 | B2 |
9554210 | Ayrapetian et al. | Jan 2017 | B1 |
9560441 | McDonough, Jr. et al. | Jan 2017 | B1 |
9576591 | Kim et al. | Feb 2017 | B2 |
9601116 | Casado et al. | Mar 2017 | B2 |
9615170 | Kirsch et al. | Apr 2017 | B2 |
9615171 | O'Neill et al. | Apr 2017 | B1 |
9626695 | Balasubramanian et al. | Apr 2017 | B2 |
9632748 | Faaborg et al. | Apr 2017 | B2 |
9633186 | Ingrassia, Jr. et al. | Apr 2017 | B2 |
9633368 | Greenzeiger et al. | Apr 2017 | B2 |
9633660 | Haughay et al. | Apr 2017 | B2 |
9633661 | Typrin et al. | Apr 2017 | B1 |
9633671 | Giacobello et al. | Apr 2017 | B2 |
9633674 | Sinha et al. | Apr 2017 | B2 |
9640179 | Hart et al. | May 2017 | B1 |
9640183 | Jung et al. | May 2017 | B2 |
9641919 | Poole et al. | May 2017 | B1 |
9646614 | Bellegarda et al. | May 2017 | B2 |
9648564 | Cui et al. | May 2017 | B1 |
9653060 | Hilmes et al. | May 2017 | B1 |
9653075 | Chen et al. | May 2017 | B1 |
9659555 | Hilmes et al. | May 2017 | B1 |
9672821 | Krishnaswamy et al. | Jun 2017 | B2 |
9674587 | Triplett et al. | Jun 2017 | B2 |
9685171 | Yang | Jun 2017 | B1 |
9691378 | Meyers et al. | Jun 2017 | B1 |
9691379 | Mathias et al. | Jun 2017 | B1 |
9697826 | Sainath et al. | Jul 2017 | B2 |
9697828 | Prasad et al. | Jul 2017 | B1 |
9698999 | Mutagi et al. | Jul 2017 | B2 |
9704478 | Vitaladevuni et al. | Jul 2017 | B1 |
9721566 | Newendorp et al. | Aug 2017 | B2 |
9721568 | Polansky et al. | Aug 2017 | B1 |
9721570 | Beal et al. | Aug 2017 | B1 |
9728188 | Rosen et al. | Aug 2017 | B1 |
9734822 | Sundaram et al. | Aug 2017 | B1 |
9736578 | Iyengar et al. | Aug 2017 | B2 |
9743204 | Welch et al. | Aug 2017 | B1 |
9743207 | Hartung | Aug 2017 | B1 |
9747011 | Lewis et al. | Aug 2017 | B2 |
9747899 | Pogue et al. | Aug 2017 | B2 |
9747920 | Ayrapetian et al. | Aug 2017 | B2 |
9747926 | Sharifi et al. | Aug 2017 | B2 |
9749760 | Lambourne | Aug 2017 | B2 |
9754605 | Chhetri | Sep 2017 | B1 |
9762967 | Clarke et al. | Sep 2017 | B2 |
9769420 | Moses | Sep 2017 | B1 |
9779725 | Sun et al. | Oct 2017 | B2 |
9779732 | Lee et al. | Oct 2017 | B2 |
9779734 | Lee | Oct 2017 | B2 |
9779735 | Civelli et al. | Oct 2017 | B2 |
9805733 | Park | Oct 2017 | B2 |
9811314 | Plagge et al. | Nov 2017 | B2 |
9813810 | Nongpiur | Nov 2017 | B1 |
9813812 | Berthelsen et al. | Nov 2017 | B2 |
9818407 | Secker-Walker et al. | Nov 2017 | B1 |
9820036 | Tritschler et al. | Nov 2017 | B1 |
9820039 | Lang | Nov 2017 | B2 |
9826306 | Lang | Nov 2017 | B2 |
9865259 | Typrin et al. | Jan 2018 | B1 |
9865264 | Gelfenbeyn | Jan 2018 | B2 |
9881616 | Beckley et al. | Jan 2018 | B2 |
9900723 | Choisel et al. | Feb 2018 | B1 |
9916839 | Scalise et al. | Mar 2018 | B1 |
9947316 | Millington et al. | Apr 2018 | B2 |
9947333 | David | Apr 2018 | B1 |
9972318 | Kelly et al. | May 2018 | B1 |
9972343 | Thorson et al. | May 2018 | B1 |
9973849 | Zhang et al. | May 2018 | B1 |
9979560 | Kim et al. | May 2018 | B2 |
10013381 | Mayman et al. | Jul 2018 | B2 |
10013995 | Lashkari et al. | Jul 2018 | B1 |
10025447 | Dixit et al. | Jul 2018 | B1 |
10026401 | Mutagi et al. | Jul 2018 | B1 |
10048930 | Vega et al. | Aug 2018 | B1 |
10049675 | Haughay | Aug 2018 | B2 |
10051366 | Buoni et al. | Aug 2018 | B1 |
10051600 | Zhong et al. | Aug 2018 | B1 |
10057698 | Drinkwater et al. | Aug 2018 | B2 |
RE47049 | Zhu et al. | Sep 2018 | E |
10068573 | Aykac et al. | Sep 2018 | B1 |
10074369 | Devaraj et al. | Sep 2018 | B2 |
10074371 | Wang et al. | Sep 2018 | B1 |
10079015 | Lockhart et al. | Sep 2018 | B1 |
10089981 | Elangovan et al. | Oct 2018 | B1 |
10108393 | Millington et al. | Oct 2018 | B2 |
10115400 | Wilberding | Oct 2018 | B2 |
10116748 | Farmer et al. | Oct 2018 | B2 |
10127911 | Kim et al. | Nov 2018 | B2 |
10134388 | Lilly | Nov 2018 | B1 |
10134399 | Lang et al. | Nov 2018 | B2 |
10136204 | Poole et al. | Nov 2018 | B1 |
10152969 | Reilly et al. | Dec 2018 | B2 |
10181323 | Beckhardt et al. | Jan 2019 | B2 |
10186265 | Lockhart et al. | Jan 2019 | B1 |
10186266 | Devaraj et al. | Jan 2019 | B1 |
10192546 | Piersol et al. | Jan 2019 | B1 |
10224056 | Torok et al. | Mar 2019 | B1 |
10225651 | Lang | Mar 2019 | B2 |
10229680 | Gillespie et al. | Mar 2019 | B1 |
10241754 | Kadarundalagi Raghuram Doss et al. | Mar 2019 | B1 |
10248376 | Keyser-Allen et al. | Apr 2019 | B2 |
10276161 | Hughes et al. | Apr 2019 | B2 |
10297256 | Reilly et al. | May 2019 | B2 |
10339917 | Aleksic et al. | Jul 2019 | B2 |
10339957 | Chenier et al. | Jul 2019 | B1 |
10346122 | Morgan | Jul 2019 | B1 |
10354650 | Gruenstein et al. | Jul 2019 | B2 |
10365887 | Mulherkar | Jul 2019 | B1 |
10365889 | Plagge et al. | Jul 2019 | B2 |
10366688 | Gunn et al. | Jul 2019 | B2 |
10366699 | Dharia et al. | Jul 2019 | B1 |
10374816 | Leblang et al. | Aug 2019 | B1 |
10381001 | Gunn et al. | Aug 2019 | B2 |
10381002 | Gunn et al. | Aug 2019 | B2 |
10381003 | Wakisaka et al. | Aug 2019 | B2 |
10388272 | Thomson et al. | Aug 2019 | B1 |
10433058 | Torgerson et al. | Oct 2019 | B1 |
10445057 | Vega et al. | Oct 2019 | B2 |
10445365 | Luke et al. | Oct 2019 | B2 |
10469966 | Lambourne | Nov 2019 | B2 |
10499146 | Lang et al. | Dec 2019 | B2 |
10510340 | Fu et al. | Dec 2019 | B1 |
10511904 | Buoni et al. | Dec 2019 | B2 |
10515625 | Metallinou et al. | Dec 2019 | B1 |
10522146 | Tushinskiy | Dec 2019 | B1 |
10546583 | White et al. | Jan 2020 | B2 |
10573312 | Thomson et al. | Feb 2020 | B1 |
10573321 | Smith et al. | Feb 2020 | B1 |
10580405 | Wang et al. | Mar 2020 | B1 |
10586540 | Smith et al. | Mar 2020 | B1 |
10599287 | Kumar et al. | Mar 2020 | B2 |
10600406 | Shapiro et al. | Mar 2020 | B1 |
10602268 | Soto | Mar 2020 | B1 |
10614807 | Beckhardt et al. | Apr 2020 | B2 |
10621981 | Sereshki | Apr 2020 | B2 |
10622009 | Zhang et al. | Apr 2020 | B1 |
10623811 | Cwik | Apr 2020 | B1 |
10624612 | Sumi et al. | Apr 2020 | B2 |
10643609 | Pogue et al. | May 2020 | B1 |
10645130 | Corbin et al. | May 2020 | B2 |
10672383 | Thomson et al. | Jun 2020 | B1 |
10679625 | Lockhart et al. | Jun 2020 | B1 |
10681460 | Woo et al. | Jun 2020 | B2 |
10685669 | Lan et al. | Jun 2020 | B1 |
10694608 | Baker et al. | Jun 2020 | B2 |
10706843 | Elangovan et al. | Jul 2020 | B1 |
10712997 | Wilberding et al. | Jul 2020 | B2 |
10728196 | Wang | Jul 2020 | B2 |
10740065 | Jarvis et al. | Aug 2020 | B2 |
10748531 | Kim | Aug 2020 | B2 |
10762896 | Yavagal et al. | Sep 2020 | B1 |
10777189 | Fu et al. | Sep 2020 | B1 |
10797667 | Fish et al. | Oct 2020 | B2 |
10824682 | Alvares | Nov 2020 | B2 |
10847143 | Millington et al. | Nov 2020 | B2 |
10847149 | Mok et al. | Nov 2020 | B1 |
10848885 | Lambourne | Nov 2020 | B2 |
RE48371 | Zhu et al. | Dec 2020 | E |
10867596 | Yoneda et al. | Dec 2020 | B2 |
10878811 | Smith et al. | Dec 2020 | B2 |
10878826 | Li et al. | Dec 2020 | B2 |
10897679 | Lambourne | Jan 2021 | B2 |
10911596 | Do et al. | Feb 2021 | B1 |
10943598 | Singh et al. | Mar 2021 | B2 |
10971158 | Patangay et al. | Apr 2021 | B1 |
11127405 | Antos et al. | Sep 2021 | B1 |
11206052 | Park | Dec 2021 | B1 |
11277512 | Leeds | Mar 2022 | B1 |
20010003173 | Lim | Jun 2001 | A1 |
20010042107 | Palm | Nov 2001 | A1 |
20020022453 | Balog et al. | Feb 2002 | A1 |
20020026442 | Lipscomb et al. | Feb 2002 | A1 |
20020034280 | Infosino | Mar 2002 | A1 |
20020046023 | Fujii et al. | Apr 2002 | A1 |
20020072816 | Shdema et al. | Jun 2002 | A1 |
20020116196 | Tran | Aug 2002 | A1 |
20020124097 | Isely et al. | Sep 2002 | A1 |
20030015354 | Edwards et al. | Jan 2003 | A1 |
20030038848 | Lee et al. | Feb 2003 | A1 |
20030040908 | Yang et al. | Feb 2003 | A1 |
20030070182 | Pierre et al. | Apr 2003 | A1 |
20030070869 | Hlibowicki | Apr 2003 | A1 |
20030072462 | Hlibowicki | Apr 2003 | A1 |
20030095672 | Hobelsberger | May 2003 | A1 |
20030130850 | Badt et al. | Jul 2003 | A1 |
20030157951 | Hasty, Jr. | Aug 2003 | A1 |
20030235244 | Pessoa et al. | Dec 2003 | A1 |
20040024478 | Hans et al. | Feb 2004 | A1 |
20040093219 | Shin et al. | May 2004 | A1 |
20040105566 | Matsunaga et al. | Jun 2004 | A1 |
20040127241 | Shostak | Jul 2004 | A1 |
20040128135 | Anastasakos et al. | Jul 2004 | A1 |
20040234088 | McCarty et al. | Nov 2004 | A1 |
20050031131 | Browning et al. | Feb 2005 | A1 |
20050031132 | Browning et al. | Feb 2005 | A1 |
20050031133 | Browning et al. | Feb 2005 | A1 |
20050031134 | Leske | Feb 2005 | A1 |
20050031137 | Browning et al. | Feb 2005 | A1 |
20050031138 | Browning et al. | Feb 2005 | A1 |
20050031139 | Browning et al. | Feb 2005 | A1 |
20050031140 | Browning | Feb 2005 | A1 |
20050033582 | Gadd et al. | Feb 2005 | A1 |
20050047606 | Lee et al. | Mar 2005 | A1 |
20050077843 | Benditt | Apr 2005 | A1 |
20050164664 | DiFonzo et al. | Jul 2005 | A1 |
20050195988 | Tashev et al. | Sep 2005 | A1 |
20050201254 | Looney et al. | Sep 2005 | A1 |
20050207584 | Bright | Sep 2005 | A1 |
20050235334 | Togashi et al. | Oct 2005 | A1 |
20050254662 | Blank et al. | Nov 2005 | A1 |
20050268234 | Rossi et al. | Dec 2005 | A1 |
20050283330 | Laraia et al. | Dec 2005 | A1 |
20050283475 | Beranek et al. | Dec 2005 | A1 |
20060004834 | Pyhalammi et al. | Jan 2006 | A1 |
20060023945 | King et al. | Feb 2006 | A1 |
20060041431 | Maes | Feb 2006 | A1 |
20060093128 | Oxford | May 2006 | A1 |
20060104451 | Browning et al. | May 2006 | A1 |
20060147058 | Wang | Jul 2006 | A1 |
20060190269 | Tessel et al. | Aug 2006 | A1 |
20060190968 | Jung et al. | Aug 2006 | A1 |
20060247913 | Huerta et al. | Nov 2006 | A1 |
20060262943 | Oxford | Nov 2006 | A1 |
20070018844 | Sutardja | Jan 2007 | A1 |
20070019815 | Asada et al. | Jan 2007 | A1 |
20070033043 | Hyakumoto | Feb 2007 | A1 |
20070038999 | Millington | Feb 2007 | A1 |
20070060054 | Romesburg | Mar 2007 | A1 |
20070071206 | Gainsboro et al. | Mar 2007 | A1 |
20070071255 | Schobben | Mar 2007 | A1 |
20070076131 | Li et al. | Apr 2007 | A1 |
20070076906 | Takagi et al. | Apr 2007 | A1 |
20070140058 | McIntosh et al. | Jun 2007 | A1 |
20070140521 | Mitobe et al. | Jun 2007 | A1 |
20070142944 | Goldberg et al. | Jun 2007 | A1 |
20070147651 | Mitobe et al. | Jun 2007 | A1 |
20070201639 | Park et al. | Aug 2007 | A1 |
20070254604 | Kim | Nov 2007 | A1 |
20070286426 | Xiang et al. | Dec 2007 | A1 |
20080037814 | Shau | Feb 2008 | A1 |
20080090537 | Sutardja | Apr 2008 | A1 |
20080090617 | Sutardja | Apr 2008 | A1 |
20080144858 | Khawand et al. | Jun 2008 | A1 |
20080146289 | Korneluk et al. | Jun 2008 | A1 |
20080182518 | Lo | Jul 2008 | A1 |
20080207115 | Lee et al. | Aug 2008 | A1 |
20080208594 | Cross et al. | Aug 2008 | A1 |
20080221897 | Cerra et al. | Sep 2008 | A1 |
20080247530 | Barton et al. | Oct 2008 | A1 |
20080248797 | Freeman et al. | Oct 2008 | A1 |
20080291896 | Tuubel et al. | Nov 2008 | A1 |
20080301729 | Broos et al. | Dec 2008 | A1 |
20090003620 | McKillop et al. | Jan 2009 | A1 |
20090005893 | Sugii et al. | Jan 2009 | A1 |
20090010445 | Matsuo | Jan 2009 | A1 |
20090018828 | Nakadai et al. | Jan 2009 | A1 |
20090043206 | Towfiq et al. | Feb 2009 | A1 |
20090052688 | Ishibashi et al. | Feb 2009 | A1 |
20090076821 | Brenner et al. | Mar 2009 | A1 |
20090153289 | Hope et al. | Jun 2009 | A1 |
20090191854 | Beason | Jul 2009 | A1 |
20090197524 | Haff et al. | Aug 2009 | A1 |
20090220107 | Every et al. | Sep 2009 | A1 |
20090228919 | Zott et al. | Sep 2009 | A1 |
20090238377 | Ramakrishnan et al. | Sep 2009 | A1 |
20090238386 | Usher et al. | Sep 2009 | A1 |
20090248397 | Garcia et al. | Oct 2009 | A1 |
20090249222 | Schmidt et al. | Oct 2009 | A1 |
20090264072 | Dai | Oct 2009 | A1 |
20090323907 | Gupta et al. | Dec 2009 | A1 |
20090326949 | Douthitt et al. | Dec 2009 | A1 |
20100014690 | Wolff et al. | Jan 2010 | A1 |
20100023638 | Bowman | Jan 2010 | A1 |
20100035593 | Franco et al. | Feb 2010 | A1 |
20100041443 | Yokota | Feb 2010 | A1 |
20100070922 | DeMaio et al. | Mar 2010 | A1 |
20100075723 | Min et al. | Mar 2010 | A1 |
20100088100 | Lindahl | Apr 2010 | A1 |
20100092004 | Kuze | Apr 2010 | A1 |
20100161335 | Whynot | Jun 2010 | A1 |
20100172516 | Lastrucci | Jul 2010 | A1 |
20100178873 | Lee et al. | Jul 2010 | A1 |
20100179874 | Higgins et al. | Jul 2010 | A1 |
20100185448 | Meisel | Jul 2010 | A1 |
20100211199 | Naik et al. | Aug 2010 | A1 |
20110033059 | Bhaskar et al. | Feb 2011 | A1 |
20110035580 | Wang et al. | Feb 2011 | A1 |
20110044461 | Kuech et al. | Feb 2011 | A1 |
20110044489 | Saiki et al. | Feb 2011 | A1 |
20110046952 | Koshinaka | Feb 2011 | A1 |
20110066634 | Phillips et al. | Mar 2011 | A1 |
20110091055 | Leblanc | Apr 2011 | A1 |
20110103615 | Sun | May 2011 | A1 |
20110131032 | Yang, II et al. | Jun 2011 | A1 |
20110145581 | Malhotra et al. | Jun 2011 | A1 |
20110170707 | Yamada et al. | Jul 2011 | A1 |
20110182436 | Murgia et al. | Jul 2011 | A1 |
20110202924 | Banguero et al. | Aug 2011 | A1 |
20110218656 | Bishop et al. | Sep 2011 | A1 |
20110267985 | Wilkinson et al. | Nov 2011 | A1 |
20110276333 | Wang et al. | Nov 2011 | A1 |
20110280422 | Neumeyer et al. | Nov 2011 | A1 |
20110285808 | Feng et al. | Nov 2011 | A1 |
20110289506 | Trivi et al. | Nov 2011 | A1 |
20110299706 | Sakai | Dec 2011 | A1 |
20120020486 | Fried et al. | Jan 2012 | A1 |
20120022863 | Cho et al. | Jan 2012 | A1 |
20120022864 | Leman et al. | Jan 2012 | A1 |
20120078635 | Rothkopf et al. | Mar 2012 | A1 |
20120086568 | Scott et al. | Apr 2012 | A1 |
20120123268 | Tanaka et al. | May 2012 | A1 |
20120128160 | Kim et al. | May 2012 | A1 |
20120131125 | Seidel et al. | May 2012 | A1 |
20120148075 | Goh et al. | Jun 2012 | A1 |
20120162540 | Ouchi et al. | Jun 2012 | A1 |
20120163603 | Abe et al. | Jun 2012 | A1 |
20120177215 | Bose et al. | Jul 2012 | A1 |
20120183149 | Hiroe | Jul 2012 | A1 |
20120224715 | Kikkeri | Sep 2012 | A1 |
20120297284 | Matthews, III et al. | Nov 2012 | A1 |
20120308044 | Vander Mey et al. | Dec 2012 | A1 |
20120308046 | Muza | Dec 2012 | A1 |
20130006453 | Wang et al. | Jan 2013 | A1 |
20130024018 | Chang et al. | Jan 2013 | A1 |
20130034241 | Pandey et al. | Feb 2013 | A1 |
20130039527 | Jensen et al. | Feb 2013 | A1 |
20130051755 | Brown et al. | Feb 2013 | A1 |
20130058492 | Silzle et al. | Mar 2013 | A1 |
20130066453 | Seefeldt | Mar 2013 | A1 |
20130080146 | Kato et al. | Mar 2013 | A1 |
20130124211 | McDonough | May 2013 | A1 |
20130148821 | Sorensen | Jun 2013 | A1 |
20130170647 | Reilly et al. | Jul 2013 | A1 |
20130179173 | Lee et al. | Jul 2013 | A1 |
20130183944 | Mozer et al. | Jul 2013 | A1 |
20130191119 | Sugiyama | Jul 2013 | A1 |
20130191122 | Mason | Jul 2013 | A1 |
20130198298 | Li et al. | Aug 2013 | A1 |
20130211826 | Mannby | Aug 2013 | A1 |
20130216056 | Thyssen | Aug 2013 | A1 |
20130262101 | Srinivasan | Oct 2013 | A1 |
20130315420 | You | Nov 2013 | A1 |
20130317635 | Bates et al. | Nov 2013 | A1 |
20130322462 | Poulsen | Dec 2013 | A1 |
20130322665 | Bennett et al. | Dec 2013 | A1 |
20130324031 | Loureiro | Dec 2013 | A1 |
20130329896 | Krishnaswamy et al. | Dec 2013 | A1 |
20130331970 | Beckhardt et al. | Dec 2013 | A1 |
20130332165 | Beckley et al. | Dec 2013 | A1 |
20130339028 | Rosner et al. | Dec 2013 | A1 |
20130343567 | Triplett et al. | Dec 2013 | A1 |
20140003611 | Mohammad et al. | Jan 2014 | A1 |
20140003625 | Sheen et al. | Jan 2014 | A1 |
20140003635 | Mohammad et al. | Jan 2014 | A1 |
20140005813 | Reimann | Jan 2014 | A1 |
20140006026 | Lamb et al. | Jan 2014 | A1 |
20140006825 | Shenhav | Jan 2014 | A1 |
20140019743 | DeLuca | Jan 2014 | A1 |
20140034929 | Hamada et al. | Feb 2014 | A1 |
20140046464 | Reimann | Feb 2014 | A1 |
20140064501 | Olsen et al. | Mar 2014 | A1 |
20140073298 | Rossmann | Mar 2014 | A1 |
20140075306 | Rega | Mar 2014 | A1 |
20140075311 | Boettcher et al. | Mar 2014 | A1 |
20140094151 | Klappert et al. | Apr 2014 | A1 |
20140100854 | Chen et al. | Apr 2014 | A1 |
20140109138 | Cannistraro et al. | Apr 2014 | A1 |
20140122075 | Bak et al. | May 2014 | A1 |
20140136195 | Abdossalami et al. | May 2014 | A1 |
20140145168 | Ohsawa et al. | May 2014 | A1 |
20140146983 | Kim et al. | May 2014 | A1 |
20140149118 | Lee et al. | May 2014 | A1 |
20140163978 | Basye et al. | Jun 2014 | A1 |
20140164400 | Kruglick | Jun 2014 | A1 |
20140167931 | Lee et al. | Jun 2014 | A1 |
20140168344 | Shoemake et al. | Jun 2014 | A1 |
20140172953 | Blanksteen | Jun 2014 | A1 |
20140181271 | Millington | Jun 2014 | A1 |
20140192986 | Lee et al. | Jul 2014 | A1 |
20140195252 | Gruber et al. | Jul 2014 | A1 |
20140207457 | Biatov et al. | Jul 2014 | A1 |
20140214429 | Pantel | Jul 2014 | A1 |
20140215332 | Lee et al. | Jul 2014 | A1 |
20140219472 | Huang et al. | Aug 2014 | A1 |
20140222436 | Binder et al. | Aug 2014 | A1 |
20140229184 | Shires | Aug 2014 | A1 |
20140244013 | Reilly | Aug 2014 | A1 |
20140244712 | Walters et al. | Aug 2014 | A1 |
20140249817 | Hart et al. | Sep 2014 | A1 |
20140252386 | Ito et al. | Sep 2014 | A1 |
20140254805 | Su et al. | Sep 2014 | A1 |
20140258292 | Thramann et al. | Sep 2014 | A1 |
20140259075 | Chang et al. | Sep 2014 | A1 |
20140269757 | Park et al. | Sep 2014 | A1 |
20140270282 | Tammi et al. | Sep 2014 | A1 |
20140274185 | Luna et al. | Sep 2014 | A1 |
20140274203 | Ganong, III et al. | Sep 2014 | A1 |
20140274218 | Kadiwala et al. | Sep 2014 | A1 |
20140277650 | Zurek et al. | Sep 2014 | A1 |
20140278372 | Nakadai et al. | Sep 2014 | A1 |
20140278933 | McMillan | Sep 2014 | A1 |
20140291642 | Watabe et al. | Oct 2014 | A1 |
20140303969 | Inose et al. | Oct 2014 | A1 |
20140310002 | Nitz et al. | Oct 2014 | A1 |
20140310614 | Jones | Oct 2014 | A1 |
20140330896 | Addala et al. | Nov 2014 | A1 |
20140334645 | Yun et al. | Nov 2014 | A1 |
20140340888 | Ishisone et al. | Nov 2014 | A1 |
20140357248 | Tonshal et al. | Dec 2014 | A1 |
20140358535 | Lee et al. | Dec 2014 | A1 |
20140363022 | Dizon et al. | Dec 2014 | A1 |
20140363024 | Apodaca | Dec 2014 | A1 |
20140365227 | Cash et al. | Dec 2014 | A1 |
20140369491 | Kloberdans et al. | Dec 2014 | A1 |
20140372109 | Iyer et al. | Dec 2014 | A1 |
20150006176 | Pogue et al. | Jan 2015 | A1 |
20150006184 | Marti et al. | Jan 2015 | A1 |
20150010169 | Popova et al. | Jan 2015 | A1 |
20150014680 | Yamazaki et al. | Jan 2015 | A1 |
20150016642 | Walsh et al. | Jan 2015 | A1 |
20150018992 | Griffiths et al. | Jan 2015 | A1 |
20150019201 | Schoenbach | Jan 2015 | A1 |
20150019219 | Tzirkel-Hancock et al. | Jan 2015 | A1 |
20150036831 | Klippel | Feb 2015 | A1 |
20150039303 | Lesso et al. | Feb 2015 | A1 |
20150039317 | Klein et al. | Feb 2015 | A1 |
20150058018 | Georges et al. | Feb 2015 | A1 |
20150063580 | Huang et al. | Mar 2015 | A1 |
20150066479 | Pasupalak et al. | Mar 2015 | A1 |
20150086034 | Lombardi et al. | Mar 2015 | A1 |
20150091709 | Reichert et al. | Apr 2015 | A1 |
20150092947 | Gossain et al. | Apr 2015 | A1 |
20150104037 | Lee et al. | Apr 2015 | A1 |
20150106085 | Lindahl | Apr 2015 | A1 |
20150110294 | Chen et al. | Apr 2015 | A1 |
20150112672 | Giacobello et al. | Apr 2015 | A1 |
20150124975 | Pontoppidan | May 2015 | A1 |
20150128065 | Torii et al. | May 2015 | A1 |
20150134456 | Baldwin | May 2015 | A1 |
20150154976 | Mutagi | Jun 2015 | A1 |
20150161990 | Sharifi | Jun 2015 | A1 |
20150169279 | Duga | Jun 2015 | A1 |
20150170645 | Di et al. | Jun 2015 | A1 |
20150170665 | Gundeti et al. | Jun 2015 | A1 |
20150172843 | Quan | Jun 2015 | A1 |
20150179181 | Morris et al. | Jun 2015 | A1 |
20150180432 | Gao et al. | Jun 2015 | A1 |
20150181318 | Gautama et al. | Jun 2015 | A1 |
20150189438 | Hampiholi et al. | Jul 2015 | A1 |
20150200454 | Heusdens et al. | Jul 2015 | A1 |
20150201271 | Diethorn et al. | Jul 2015 | A1 |
20150221678 | Yamazaki et al. | Aug 2015 | A1 |
20150222563 | Burns et al. | Aug 2015 | A1 |
20150222987 | Angel, Jr. et al. | Aug 2015 | A1 |
20150228274 | Leppanen et al. | Aug 2015 | A1 |
20150228803 | Koezuka et al. | Aug 2015 | A1 |
20150237406 | Ochoa et al. | Aug 2015 | A1 |
20150243287 | Nakano et al. | Aug 2015 | A1 |
20150245152 | Ding et al. | Aug 2015 | A1 |
20150245154 | Dadu et al. | Aug 2015 | A1 |
20150249889 | Iyer et al. | Sep 2015 | A1 |
20150253292 | Larkin et al. | Sep 2015 | A1 |
20150253960 | Lin et al. | Sep 2015 | A1 |
20150254057 | Klein et al. | Sep 2015 | A1 |
20150263174 | Yamazaki et al. | Sep 2015 | A1 |
20150271593 | Sun et al. | Sep 2015 | A1 |
20150277846 | Yen et al. | Oct 2015 | A1 |
20150280676 | Holman et al. | Oct 2015 | A1 |
20150296299 | Klippel et al. | Oct 2015 | A1 |
20150302856 | Kim et al. | Oct 2015 | A1 |
20150319529 | Klippel | Nov 2015 | A1 |
20150325267 | Lee et al. | Nov 2015 | A1 |
20150331663 | Beckhardt et al. | Nov 2015 | A1 |
20150334471 | Innes et al. | Nov 2015 | A1 |
20150338917 | Steiner et al. | Nov 2015 | A1 |
20150341406 | Rockefeller et al. | Nov 2015 | A1 |
20150346845 | Di Censo et al. | Dec 2015 | A1 |
20150348548 | Piernot et al. | Dec 2015 | A1 |
20150348551 | Gruber et al. | Dec 2015 | A1 |
20150355878 | Corbin | Dec 2015 | A1 |
20150363061 | De, III et al. | Dec 2015 | A1 |
20150363401 | Chen et al. | Dec 2015 | A1 |
20150370531 | Faaborg | Dec 2015 | A1 |
20150371657 | Gao | Dec 2015 | A1 |
20150371659 | Gao | Dec 2015 | A1 |
20150371664 | Bar-Or et al. | Dec 2015 | A1 |
20150380010 | Srinivasan | Dec 2015 | A1 |
20150382047 | Van Os et al. | Dec 2015 | A1 |
20160007116 | Holman | Jan 2016 | A1 |
20160018873 | Fernald et al. | Jan 2016 | A1 |
20160021458 | Johnson et al. | Jan 2016 | A1 |
20160026428 | Morganstern et al. | Jan 2016 | A1 |
20160029142 | Isaac et al. | Jan 2016 | A1 |
20160035321 | Cho et al. | Feb 2016 | A1 |
20160035337 | Aggarwal et al. | Feb 2016 | A1 |
20160036962 | Rand et al. | Feb 2016 | A1 |
20160042748 | Jain et al. | Feb 2016 | A1 |
20160044151 | Shoemaker et al. | Feb 2016 | A1 |
20160050488 | Matheja et al. | Feb 2016 | A1 |
20160055850 | Nakadai et al. | Feb 2016 | A1 |
20160057522 | Choisel et al. | Feb 2016 | A1 |
20160070526 | Sheen | Mar 2016 | A1 |
20160072804 | Chien et al. | Mar 2016 | A1 |
20160077710 | Lewis et al. | Mar 2016 | A1 |
20160086609 | Yue et al. | Mar 2016 | A1 |
20160088036 | Corbin et al. | Mar 2016 | A1 |
20160088392 | Huttunen et al. | Mar 2016 | A1 |
20160093304 | Kim et al. | Mar 2016 | A1 |
20160094718 | Mani et al. | Mar 2016 | A1 |
20160094917 | Wilk et al. | Mar 2016 | A1 |
20160098393 | Hebert | Apr 2016 | A1 |
20160098992 | Renard et al. | Apr 2016 | A1 |
20160103653 | Jang | Apr 2016 | A1 |
20160104480 | Sharifi | Apr 2016 | A1 |
20160111110 | Gautama et al. | Apr 2016 | A1 |
20160125876 | Schroeter et al. | May 2016 | A1 |
20160127780 | Roberts et al. | May 2016 | A1 |
20160133259 | Rubin et al. | May 2016 | A1 |
20160134966 | Fitzgerald et al. | May 2016 | A1 |
20160134982 | Iyer | May 2016 | A1 |
20160140957 | Duta et al. | May 2016 | A1 |
20160148615 | Lee et al. | May 2016 | A1 |
20160154089 | Altman | Jun 2016 | A1 |
20160155442 | Kannan et al. | Jun 2016 | A1 |
20160155443 | Khan et al. | Jun 2016 | A1 |
20160157035 | Russell et al. | Jun 2016 | A1 |
20160162469 | Santos | Jun 2016 | A1 |
20160171976 | Sun et al. | Jun 2016 | A1 |
20160173578 | Sharma et al. | Jun 2016 | A1 |
20160173983 | Berthelsen et al. | Jun 2016 | A1 |
20160180853 | Wanlund et al. | Jun 2016 | A1 |
20160189716 | Lindahl et al. | Jun 2016 | A1 |
20160196499 | Khan et al. | Jul 2016 | A1 |
20160203331 | Khan et al. | Jul 2016 | A1 |
20160210110 | Feldman | Jul 2016 | A1 |
20160212538 | Fullam et al. | Jul 2016 | A1 |
20160216938 | Millington | Jul 2016 | A1 |
20160217789 | Lee et al. | Jul 2016 | A1 |
20160225385 | Hammarqvist | Aug 2016 | A1 |
20160232451 | Scherzer | Aug 2016 | A1 |
20160234204 | Rishi et al. | Aug 2016 | A1 |
20160234615 | Lambourne | Aug 2016 | A1 |
20160239255 | Chavez et al. | Aug 2016 | A1 |
20160240192 | Raghuvir | Aug 2016 | A1 |
20160241976 | Pearson | Aug 2016 | A1 |
20160253050 | Mishra et al. | Sep 2016 | A1 |
20160260431 | Newendorp et al. | Sep 2016 | A1 |
20160283841 | Sainath et al. | Sep 2016 | A1 |
20160302018 | Russell et al. | Oct 2016 | A1 |
20160314782 | Klimanis | Oct 2016 | A1 |
20160316293 | Klimanis | Oct 2016 | A1 |
20160322045 | Hatfield et al. | Nov 2016 | A1 |
20160336519 | Seo et al. | Nov 2016 | A1 |
20160343866 | Koezuka et al. | Nov 2016 | A1 |
20160343949 | Seo et al. | Nov 2016 | A1 |
20160343954 | Seo et al. | Nov 2016 | A1 |
20160345114 | Hanna et al. | Nov 2016 | A1 |
20160352915 | Gautama | Dec 2016 | A1 |
20160353217 | Starobin et al. | Dec 2016 | A1 |
20160353218 | Starobin et al. | Dec 2016 | A1 |
20160357503 | Triplett et al. | Dec 2016 | A1 |
20160364206 | Keyser-Allen et al. | Dec 2016 | A1 |
20160366515 | Mendes et al. | Dec 2016 | A1 |
20160372113 | David et al. | Dec 2016 | A1 |
20160372688 | Seo et al. | Dec 2016 | A1 |
20160373269 | Okubo et al. | Dec 2016 | A1 |
20160373909 | Rasmussen et al. | Dec 2016 | A1 |
20160379634 | Yamamoto et al. | Dec 2016 | A1 |
20170003931 | Dvortsov et al. | Jan 2017 | A1 |
20170012207 | Seo et al. | Jan 2017 | A1 |
20170012232 | Kataishi et al. | Jan 2017 | A1 |
20170019732 | Mendes et al. | Jan 2017 | A1 |
20170025124 | Mixter et al. | Jan 2017 | A1 |
20170025615 | Seo et al. | Jan 2017 | A1 |
20170025630 | Seo et al. | Jan 2017 | A1 |
20170026769 | Patel | Jan 2017 | A1 |
20170032244 | Kurata | Feb 2017 | A1 |
20170034263 | Archambault et al. | Feb 2017 | A1 |
20170039025 | Kielak | Feb 2017 | A1 |
20170040002 | Basson et al. | Feb 2017 | A1 |
20170040018 | Tormey | Feb 2017 | A1 |
20170041724 | Master et al. | Feb 2017 | A1 |
20170053648 | Chi | Feb 2017 | A1 |
20170053650 | Ogawa | Feb 2017 | A1 |
20170060526 | Barton et al. | Mar 2017 | A1 |
20170062734 | Suzuki et al. | Mar 2017 | A1 |
20170070478 | Park et al. | Mar 2017 | A1 |
20170076212 | Shams et al. | Mar 2017 | A1 |
20170076720 | Gopalan et al. | Mar 2017 | A1 |
20170076726 | Bae | Mar 2017 | A1 |
20170078824 | Heo | Mar 2017 | A1 |
20170083285 | Meyers et al. | Mar 2017 | A1 |
20170084277 | Sharifi | Mar 2017 | A1 |
20170084292 | Yoo | Mar 2017 | A1 |
20170084295 | Tsiartas et al. | Mar 2017 | A1 |
20170090864 | Jorgovanovic | Mar 2017 | A1 |
20170092278 | Evermann et al. | Mar 2017 | A1 |
20170092297 | Sainath et al. | Mar 2017 | A1 |
20170092299 | Matsuo | Mar 2017 | A1 |
20170092889 | Seo et al. | Mar 2017 | A1 |
20170092890 | Seo et al. | Mar 2017 | A1 |
20170094215 | Western | Mar 2017 | A1 |
20170103748 | Weissberg et al. | Apr 2017 | A1 |
20170103754 | Higbie et al. | Apr 2017 | A1 |
20170103755 | Jeon et al. | Apr 2017 | A1 |
20170110124 | Boesen et al. | Apr 2017 | A1 |
20170110144 | Sharifi et al. | Apr 2017 | A1 |
20170117497 | Seo et al. | Apr 2017 | A1 |
20170123251 | Nakada et al. | May 2017 | A1 |
20170125037 | Shin | May 2017 | A1 |
20170125456 | Kasahara | May 2017 | A1 |
20170133007 | Drewes | May 2017 | A1 |
20170133011 | Chen et al. | May 2017 | A1 |
20170134872 | Silva et al. | May 2017 | A1 |
20170139720 | Stein | May 2017 | A1 |
20170140449 | Kannan | May 2017 | A1 |
20170140748 | Roberts et al. | May 2017 | A1 |
20170140759 | Kumar et al. | May 2017 | A1 |
20170151930 | Boesen | Jun 2017 | A1 |
20170177585 | Rodger et al. | Jun 2017 | A1 |
20170178662 | Ayrapetian et al. | Jun 2017 | A1 |
20170180561 | Kadiwala et al. | Jun 2017 | A1 |
20170188150 | Brunet et al. | Jun 2017 | A1 |
20170188437 | Banta | Jun 2017 | A1 |
20170193999 | Aleksic et al. | Jul 2017 | A1 |
20170206896 | Ko et al. | Jul 2017 | A1 |
20170206900 | Lee et al. | Jul 2017 | A1 |
20170214996 | Yeo | Jul 2017 | A1 |
20170236512 | Williams et al. | Aug 2017 | A1 |
20170236515 | Pinsky et al. | Aug 2017 | A1 |
20170242649 | Jarvis et al. | Aug 2017 | A1 |
20170242651 | Lang et al. | Aug 2017 | A1 |
20170242653 | Lang et al. | Aug 2017 | A1 |
20170242657 | Jarvis et al. | Aug 2017 | A1 |
20170243576 | Millington et al. | Aug 2017 | A1 |
20170243587 | Plagge et al. | Aug 2017 | A1 |
20170245076 | Kusano et al. | Aug 2017 | A1 |
20170255612 | Sarikaya et al. | Sep 2017 | A1 |
20170257686 | Gautama et al. | Sep 2017 | A1 |
20170269975 | Wood et al. | Sep 2017 | A1 |
20170270919 | Parthasarathi et al. | Sep 2017 | A1 |
20170278512 | Pandya et al. | Sep 2017 | A1 |
20170287485 | Civelli et al. | Oct 2017 | A1 |
20170300990 | Tanaka et al. | Oct 2017 | A1 |
20170330565 | Daley et al. | Nov 2017 | A1 |
20170332168 | Moghimi et al. | Nov 2017 | A1 |
20170346872 | Naik et al. | Nov 2017 | A1 |
20170352357 | Fink | Dec 2017 | A1 |
20170353789 | Kim et al. | Dec 2017 | A1 |
20170357475 | Lee et al. | Dec 2017 | A1 |
20170357478 | Piersol et al. | Dec 2017 | A1 |
20170366393 | Shaker et al. | Dec 2017 | A1 |
20170374454 | Bernardini et al. | Dec 2017 | A1 |
20170374552 | Xia et al. | Dec 2017 | A1 |
20180018964 | Reilly et al. | Jan 2018 | A1 |
20180018967 | Lang et al. | Jan 2018 | A1 |
20180020306 | Sheen | Jan 2018 | A1 |
20180025733 | Qian et al. | Jan 2018 | A1 |
20180033428 | Kim et al. | Feb 2018 | A1 |
20180033438 | Toma et al. | Feb 2018 | A1 |
20180040324 | Wilberding | Feb 2018 | A1 |
20180047394 | Tian et al. | Feb 2018 | A1 |
20180053504 | Wang et al. | Feb 2018 | A1 |
20180054506 | Hart et al. | Feb 2018 | A1 |
20180061396 | Srinivasan et al. | Mar 2018 | A1 |
20180061402 | Devaraj et al. | Mar 2018 | A1 |
20180061404 | Devaraj et al. | Mar 2018 | A1 |
20180061419 | Melendo Casado et al. | Mar 2018 | A1 |
20180061420 | Patil et al. | Mar 2018 | A1 |
20180062871 | Jones et al. | Mar 2018 | A1 |
20180084367 | Greff et al. | Mar 2018 | A1 |
20180088900 | Glaser et al. | Mar 2018 | A1 |
20180091898 | Yoon et al. | Mar 2018 | A1 |
20180091913 | Hartung et al. | Mar 2018 | A1 |
20180096683 | James et al. | Apr 2018 | A1 |
20180096696 | Mixter | Apr 2018 | A1 |
20180107446 | Wilberding et al. | Apr 2018 | A1 |
20180108351 | Beckhardt et al. | Apr 2018 | A1 |
20180122372 | Wanderlust | May 2018 | A1 |
20180122378 | Mixter et al. | May 2018 | A1 |
20180130469 | Gruenstein et al. | May 2018 | A1 |
20180132217 | Stirling-Gallacher | May 2018 | A1 |
20180132298 | Birnam et al. | May 2018 | A1 |
20180137861 | Ogawa | May 2018 | A1 |
20180152557 | White et al. | May 2018 | A1 |
20180158454 | Campbell et al. | Jun 2018 | A1 |
20180165055 | Yu et al. | Jun 2018 | A1 |
20180167981 | Jonna et al. | Jun 2018 | A1 |
20180174597 | Lee et al. | Jun 2018 | A1 |
20180182383 | Kim et al. | Jun 2018 | A1 |
20180182390 | Hughes et al. | Jun 2018 | A1 |
20180182397 | Carbune et al. | Jun 2018 | A1 |
20180188948 | Ouyang et al. | Jul 2018 | A1 |
20180190274 | Kirazci et al. | Jul 2018 | A1 |
20180190285 | Heckman et al. | Jul 2018 | A1 |
20180197533 | Lyon et al. | Jul 2018 | A1 |
20180199130 | Jaffe | Jul 2018 | A1 |
20180199146 | Sheen | Jul 2018 | A1 |
20180204569 | Nadkar et al. | Jul 2018 | A1 |
20180205963 | Matei et al. | Jul 2018 | A1 |
20180210698 | Park et al. | Jul 2018 | A1 |
20180211665 | Park et al. | Jul 2018 | A1 |
20180218747 | Moghimi et al. | Aug 2018 | A1 |
20180219976 | Decenzo et al. | Aug 2018 | A1 |
20180225933 | Park et al. | Aug 2018 | A1 |
20180228006 | Baker et al. | Aug 2018 | A1 |
20180233130 | Kaskari et al. | Aug 2018 | A1 |
20180233136 | Torok et al. | Aug 2018 | A1 |
20180233137 | Torok et al. | Aug 2018 | A1 |
20180233139 | Finkelstein et al. | Aug 2018 | A1 |
20180233142 | Koishida et al. | Aug 2018 | A1 |
20180233150 | Gruenstein et al. | Aug 2018 | A1 |
20180234765 | Torok et al. | Aug 2018 | A1 |
20180261213 | Arik et al. | Sep 2018 | A1 |
20180262793 | Lau et al. | Sep 2018 | A1 |
20180262831 | Matheja et al. | Sep 2018 | A1 |
20180270565 | Ganeshkumar | Sep 2018 | A1 |
20180277107 | Kim | Sep 2018 | A1 |
20180277113 | Hartung et al. | Sep 2018 | A1 |
20180277119 | Baba et al. | Sep 2018 | A1 |
20180277133 | Deetz et al. | Sep 2018 | A1 |
20180286394 | Li et al. | Oct 2018 | A1 |
20180286414 | Ravindran et al. | Oct 2018 | A1 |
20180293484 | Wang et al. | Oct 2018 | A1 |
20180308470 | Park et al. | Oct 2018 | A1 |
20180314552 | Kim et al. | Nov 2018 | A1 |
20180322891 | Van Den Oord et al. | Nov 2018 | A1 |
20180324756 | Ryu et al. | Nov 2018 | A1 |
20180335903 | Coffman et al. | Nov 2018 | A1 |
20180336274 | Choudhury et al. | Nov 2018 | A1 |
20180349093 | McCarty et al. | Dec 2018 | A1 |
20180358009 | Daley et al. | Dec 2018 | A1 |
20180365567 | Kolavennu et al. | Dec 2018 | A1 |
20180367944 | Heo et al. | Dec 2018 | A1 |
20190012141 | Piersol et al. | Jan 2019 | A1 |
20190013019 | Lawrence | Jan 2019 | A1 |
20190014592 | Hampel et al. | Jan 2019 | A1 |
20190033446 | Bultan et al. | Jan 2019 | A1 |
20190042187 | Truong et al. | Feb 2019 | A1 |
20190043488 | Bocklet et al. | Feb 2019 | A1 |
20190043492 | Lang | Feb 2019 | A1 |
20190051298 | Lee et al. | Feb 2019 | A1 |
20190066672 | Wood et al. | Feb 2019 | A1 |
20190066687 | Wood et al. | Feb 2019 | A1 |
20190074025 | Lashkari et al. | Mar 2019 | A1 |
20190079724 | Feuz et al. | Mar 2019 | A1 |
20190081507 | Ide | Mar 2019 | A1 |
20190081810 | Jung | Mar 2019 | A1 |
20190082255 | Tajiri et al. | Mar 2019 | A1 |
20190087455 | He et al. | Mar 2019 | A1 |
20190088261 | Lang et al. | Mar 2019 | A1 |
20190090056 | Rexach et al. | Mar 2019 | A1 |
20190096408 | Li et al. | Mar 2019 | A1 |
20190098400 | Buoni et al. | Mar 2019 | A1 |
20190104119 | Giorgi et al. | Apr 2019 | A1 |
20190104373 | Wodrich et al. | Apr 2019 | A1 |
20190108839 | Reilly et al. | Apr 2019 | A1 |
20190115011 | Khellah et al. | Apr 2019 | A1 |
20190130906 | Kobayashi et al. | May 2019 | A1 |
20190163153 | Price et al. | May 2019 | A1 |
20190172452 | Smith et al. | Jun 2019 | A1 |
20190173687 | Mackay et al. | Jun 2019 | A1 |
20190179607 | Thangarathnam et al. | Jun 2019 | A1 |
20190179611 | Wojogbe et al. | Jun 2019 | A1 |
20190182072 | Roe et al. | Jun 2019 | A1 |
20190206391 | Busch et al. | Jul 2019 | A1 |
20190206412 | Li et al. | Jul 2019 | A1 |
20190219976 | Giorgi et al. | Jul 2019 | A1 |
20190220246 | Orr et al. | Jul 2019 | A1 |
20190221206 | Chen et al. | Jul 2019 | A1 |
20190237067 | Friedman et al. | Aug 2019 | A1 |
20190239008 | Lambourne | Aug 2019 | A1 |
20190239009 | Lambourne | Aug 2019 | A1 |
20190243603 | Keyser-Allen et al. | Aug 2019 | A1 |
20190243606 | Jayakumar et al. | Aug 2019 | A1 |
20190244608 | Choi et al. | Aug 2019 | A1 |
20190281397 | Lambourne | Sep 2019 | A1 |
20190287546 | Ganeshkumar | Sep 2019 | A1 |
20190288970 | Siddiq | Sep 2019 | A1 |
20190289367 | Siddiq | Sep 2019 | A1 |
20190295542 | Huang et al. | Sep 2019 | A1 |
20190295563 | Kamdar et al. | Sep 2019 | A1 |
20190297388 | Panchaksharaiah et al. | Sep 2019 | A1 |
20190304443 | Bhagwan | Oct 2019 | A1 |
20190311710 | Eraslan et al. | Oct 2019 | A1 |
20190311712 | Firik et al. | Oct 2019 | A1 |
20190311720 | Pasko | Oct 2019 | A1 |
20190317606 | Jain et al. | Oct 2019 | A1 |
20190342962 | Chang et al. | Nov 2019 | A1 |
20190347063 | Liu et al. | Nov 2019 | A1 |
20190348044 | Chun et al. | Nov 2019 | A1 |
20190362714 | Mori et al. | Nov 2019 | A1 |
20190364375 | Soto et al. | Nov 2019 | A1 |
20190364422 | Zhuo | Nov 2019 | A1 |
20190371310 | Fox et al. | Dec 2019 | A1 |
20200007987 | Woo et al. | Jan 2020 | A1 |
20200034492 | Verbeke et al. | Jan 2020 | A1 |
20200051554 | Kim et al. | Feb 2020 | A1 |
20200074990 | Kim et al. | Mar 2020 | A1 |
20200090647 | Kurtz | Mar 2020 | A1 |
20200092687 | Devaraj et al. | Mar 2020 | A1 |
20200098354 | Lin et al. | Mar 2020 | A1 |
20200098379 | Tai et al. | Mar 2020 | A1 |
20200105245 | Gupta et al. | Apr 2020 | A1 |
20200105256 | Fainberg et al. | Apr 2020 | A1 |
20200105264 | Jang et al. | Apr 2020 | A1 |
20200152206 | Shen et al. | May 2020 | A1 |
20200175989 | Lockhart et al. | Jun 2020 | A1 |
20200184964 | Myers et al. | Jun 2020 | A1 |
20200184980 | Wilberding | Jun 2020 | A1 |
20200193973 | Tolomei et al. | Jun 2020 | A1 |
20200211539 | Lee | Jul 2020 | A1 |
20200211550 | Pan et al. | Jul 2020 | A1 |
20200211556 | Mixter et al. | Jul 2020 | A1 |
20200213729 | Soto | Jul 2020 | A1 |
20200216089 | Garcia et al. | Jul 2020 | A1 |
20200234709 | Kunitake | Jul 2020 | A1 |
20200251107 | Wang et al. | Aug 2020 | A1 |
20200265838 | Lee et al. | Aug 2020 | A1 |
20200310751 | Anand et al. | Oct 2020 | A1 |
20200336846 | Rohde et al. | Oct 2020 | A1 |
20200395006 | Smith et al. | Dec 2020 | A1 |
20200395010 | Smith et al. | Dec 2020 | A1 |
20200395013 | Smith et al. | Dec 2020 | A1 |
20200409652 | Wilberding et al. | Dec 2020 | A1 |
20200409926 | Srinivasan | Dec 2020 | A1 |
20210035561 | D'Amato et al. | Feb 2021 | A1 |
20210035572 | D'Amato et al. | Feb 2021 | A1 |
20210067867 | Kagoshima | Mar 2021 | A1 |
20210118429 | Shan | Apr 2021 | A1 |
20210166680 | Jung et al. | Jun 2021 | A1 |
20210183366 | Reinspach et al. | Jun 2021 | A1 |
20210280185 | Tan et al. | Sep 2021 | A1 |
Number | Date | Country |
---|---|---|
2017100486 | Jun 2017 | AU |
2017100581 | Jun 2017 | AU |
1323435 | Nov 2001 | CN |
101310558 | Nov 2008 | CN |
101480039 | Jul 2009 | CN |
101661753 | Mar 2010 | CN |
101686282 | Mar 2010 | CN |
101907983 | Dec 2010 | CN |
102123188 | Jul 2011 | CN |
102256098 | Nov 2011 | CN |
102567468 | Jul 2012 | CN |
103052001 | Apr 2013 | CN |
103181192 | Jun 2013 | CN |
103210663 | Jul 2013 | CN |
103546616 | Jan 2014 | CN |
103811007 | May 2014 | CN |
104010251 | Aug 2014 | CN |
104035743 | Sep 2014 | CN |
104053088 | Sep 2014 | CN |
104092936 | Oct 2014 | CN |
104104769 | Oct 2014 | CN |
104115224 | Oct 2014 | CN |
104282305 | Jan 2015 | CN |
104538030 | Apr 2015 | CN |
104575504 | Apr 2015 | CN |
104635539 | May 2015 | CN |
104865550 | Aug 2015 | CN |
105187907 | Dec 2015 | CN |
105204357 | Dec 2015 | CN |
105206281 | Dec 2015 | CN |
105284076 | Jan 2016 | CN |
105493442 | Apr 2016 | CN |
105679318 | Jun 2016 | CN |
106028223 | Oct 2016 | CN |
106375902 | Feb 2017 | CN |
106531165 | Mar 2017 | CN |
106708403 | May 2017 | CN |
107004410 | Aug 2017 | CN |
107919123 | Apr 2018 | CN |
109712626 | May 2019 | CN |
1349146 | Oct 2003 | EP |
1389853 | Feb 2004 | EP |
2051542 | Apr 2009 | EP |
2166737 | Mar 2010 | EP |
2683147 | Jan 2014 | EP |
2986034 | Feb 2016 | EP |
3128767 | Feb 2017 | EP |
3133595 | Feb 2017 | EP |
2351021 | Sep 2017 | EP |
3270377 | Jan 2018 | EP |
3285502 | Feb 2018 | EP |
S63301998 | Dec 1988 | JP |
H0883091 | Mar 1996 | JP |
2001236093 | Aug 2001 | JP |
2003223188 | Aug 2003 | JP |
2004347943 | Dec 2004 | JP |
2004354721 | Dec 2004 | JP |
2005242134 | Sep 2005 | JP |
2005250867 | Sep 2005 | JP |
2005284492 | Oct 2005 | JP |
2006092482 | Apr 2006 | JP |
2007013400 | Jan 2007 | JP |
2007142595 | Jun 2007 | JP |
2008079256 | Apr 2008 | JP |
2008158868 | Jul 2008 | JP |
2010141748 | Jun 2010 | JP |
2013037148 | Feb 2013 | JP |
2014071138 | Apr 2014 | JP |
2014137590 | Jul 2014 | JP |
2015161551 | Sep 2015 | JP |
2015527768 | Sep 2015 | JP |
2016095383 | May 2016 | JP |
2017072857 | Apr 2017 | JP |
2017129860 | Jul 2017 | JP |
2017227912 | Dec 2017 | JP |
2018055259 | Apr 2018 | JP |
20100036351 | Apr 2010 | KR |
100966415 | Jun 2010 | KR |
20100111071 | Oct 2010 | KR |
20130050987 | May 2013 | KR |
20140005410 | Jan 2014 | KR |
20140035310 | Mar 2014 | KR |
20140054643 | May 2014 | KR |
20140112900 | Sep 2014 | KR |
200153994 | Jul 2001 | WO |
2003093950 | Nov 2003 | WO |
2008048599 | Apr 2008 | WO |
2012166386 | Dec 2012 | WO |
2013184792 | Dec 2013 | WO |
2014064531 | May 2014 | WO |
2014159581 | Oct 2014 | WO |
2015017303 | Feb 2015 | WO |
2015037396 | Mar 2015 | WO |
2015105788 | Jul 2015 | WO |
2015131024 | Sep 2015 | WO |
2015178950 | Nov 2015 | WO |
2016014142 | Jan 2016 | WO |
2016022926 | Feb 2016 | WO |
2016033364 | Mar 2016 | WO |
2016057268 | Apr 2016 | WO |
2016085775 | Jun 2016 | WO |
2016165067 | Oct 2016 | WO |
2016171956 | Oct 2016 | WO |
2016200593 | Dec 2016 | WO |
2017039632 | Mar 2017 | WO |
2017058654 | Apr 2017 | WO |
2017138934 | Aug 2017 | WO |
2017147075 | Aug 2017 | WO |
2017147936 | Sep 2017 | WO |
2018027142 | Feb 2018 | WO |
2018067404 | Apr 2018 | WO |
Entry |
---|
US 9,299,346 B1, 03/2016, Hart et al. (withdrawn) |
Non-Final Office Action dated Feb. 20, 2018, issued in connection with U.S. Appl. No. 15/211,748, filed Jul. 15, 2016, 31 pages. |
Non-Final Office Action dated Jun. 20, 2019, issued in connection with U.S. Appl. No. 15/946,585, filed Apr. 5, 2018, 10 pages. |
Non-Final Office Action dated Apr. 21, 2021, issued in connection with U.S. Appl. No. 16/109,375, filed Aug. 22, 2018, 9 pages. |
Non-Final Office Action dated Aug. 21, 2019, issued in connection with U.S. Appl. No. 16/192,126, filed Nov. 15, 2018, 8 pages. |
Non-Final Office Action dated Feb. 21, 2019, issued in connection with U.S. Appl. No. 16/214,666, filed Dec. 10, 2018, 12 pages. |
Non-Final Office Action dated Jan. 21, 2020, issued in connection with U.S. Appl. No. 16/214,711, filed Dec. 10, 2018, 9 pages. |
Non-Final Office Action dated Jan. 21, 2020, issued in connection with U.S. Appl. No. 16/598,125, filed Oct. 10, 2019, 25 pages. |
Non-Final Office Action dated Oct. 21, 2019, issued in connection with U.S. Appl. No. 15/973,413, filed May 7, 2018, 10 pages. |
Non-Final Office Action dated Jul. 22, 2020, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 11 pages. |
Non-Final Office Action dated May 22, 2018, issued in connection with U.S. Appl. No. 15/946,599, filed Apr. 5, 2018, 19 pages. |
Non-Final Office Action dated Sep. 22, 2020, issued in connection with U.S. Appl. No. 16/539,843, filed Aug. 13, 2019, 7 pages. |
Non-Final Office Action dated Jun. 23, 2021, issued in connection with U.S. Appl. No. 16/439,032, filed Jun. 12, 2019, 13 pages. |
Non-Final Office Action dated May 23, 2019, issued in connection with U.S. Appl. No. 16/154,071, filed Oct. 8, 2018, 36 pages. |
Non-Final Office Action dated Nov. 23, 2020, issued in connection with U.S. Appl. No. 16/524,306, filed Jul. 29, 2019, 14 pages. |
Non-Final Office Action dated Sep. 23, 2020, issued in connection with U.S. Appl. No. 16/177,185, filed Oct. 31, 2018, 17 pages. |
Non-Final Office Action dated Aug. 24, 2017, issued in connection with U.S. Appl. No. 15/297,627, filed Oct. 19, 2016, 13 pages. |
Non-Final Office Action dated Jul. 24, 2019, issued in connection with U.S. Appl. No. 16/439,009, filed Jun. 12, 2019, 26 pages. |
Non-Final Office Action dated Jul. 25, 2017, issued in connection with U.S. Appl. No. 15/273,679, filed Jul. 22, 2016, 11 pages. |
Non-Final Office Action dated Dec. 26, 2018, issued in connection with U.S. Appl. No. 16/154,469, filed Oct. 8, 2018, 7 pages. |
Non-Final Office Action dated Jan. 26, 2017, issued in connection with U.S. Appl. No. 15/098,867, filed Apr. 14, 2016, 16 pages. |
Non-Final Office Action dated Oct. 26, 2017, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 12 pages. |
Non-Final Office Action dated Oct. 26, 2021, issued in connection with U.S. Appl. No. 16/736,725, filed Jan. 7, 2020, 12 pages. |
Non-Final Office Action dated Jun. 27, 2018, issued in connection with U.S. Appl. No. 15/438,749, filed Feb. 21, 2017, 16 pages. |
Non-Final Office Action dated Jun. 27, 2019, issued in connection with U.S. Appl. No. 16/437,437, filed Jun. 11, 2019, 8 pages. |
Non-Final Office Action dated Jun. 27, 2019, issued in connection with U.S. Appl. No. 16/437,476, filed Jun. 11, 2019, 8 pages. |
Non-Final Office Action dated Mar. 27, 2020, issued in connection with U.S. Appl. No. 16/790,621, filed Feb. 13, 2020, 8 pages. |
Non-Final Office Action dated May 27, 2020, issued in connection with U.S. Appl. No. 16/715,713, filed Dec. 16, 2019, 14 pages. |
Non-Final Office Action dated Oct. 27, 2020, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 13 pages. |
Non-Final Office Action dated Oct. 27, 2020, issued in connection with U.S. Appl. No. 16/715,984, filed Dec. 16, 2019, 14 pages. |
Non-Final Office Action dated Oct. 27, 2020, issued in connection with U.S. Appl. No. 16/819,755, filed Mar. 16, 2020, 8 pages. |
Non-Final Office Action dated Oct. 28, 2019, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 11 pages. |
Non-Final Office Action dated Oct. 28, 2021, issued in connection with U.S. Appl. No. 16/378,516, filed Apr. 8, 2019, 10 pages. |
Non-Final Office Action dated Oct. 28, 2021, issued in connection with U.S. Appl. No. 17/247,736, filed Dec. 21, 2020, 12 pages. |
Non-Final Office Action dated Mar. 29, 2019, issued in connection with U.S. Appl. No. 16/102,650, filed Aug. 13, 2018, 11 pages. |
Non-Final Office Action dated Mar. 29, 2021, issued in connection with U.S. Appl. No. 16/528,265, filed Jul. 31, 2019, 18 pages. |
Non-Final Office Action dated Nov. 29, 2021, issued in connection with U.S. Appl. No. 16/989,350, filed Aug. 10, 2020, 15 pages. |
Non-Final Office Action dated Sep. 29, 2020, issued in connection with U.S. Appl. No. 16/402,617, filed May 3, 2019, 12 pages. |
Non-Final Office Action dated Dec. 3, 2020, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 11 pages. |
Non-Final Office Action dated Jul. 3, 2019, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 7 pages. |
Non-Final Office Action dated May 3, 2019, issued in connection with U.S. Appl. No. 16/178,122, filed Nov. 1, 2018, 14 pages. |
Non-Final Office Action dated Oct. 3, 2018, issued in connection with U.S. Appl. No. 16/102,153, filed Aug. 13, 2018, 20 pages. |
Non-Final Office Action dated Apr. 30, 2019, issued in connection with U.S. Appl. No. 15/718,521, filed Sep. 28, 2017, 39 pages. |
Non-Final Office Action dated Jun. 30, 2017, issued in connection with U.S. Appl. No. 15/277,810, filed Sep. 27, 2016, 13 pages. |
Non-Final Office Action dated Apr. 4, 2019, issued in connection with U.S. Appl. No. 15/718,911, filed Sep. 28, 2017, 21 pages. |
Non-Final Office Action dated Aug. 4, 2020, issued in connection with U.S. Appl. No. 16/600,644, filed Oct. 14, 2019, 30 pages. |
Non-Final Office Action dated Jan. 4, 2019, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 6 pages. |
Non-Final Office Action dated Nov. 5, 2021, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 21 pages. |
Non-Final Office Action dated Apr. 6, 2020, issued in connection with U.S. Appl. No. 16/424,825, filed May 29, 2019, 22 pages. |
Non-Final Office Action dated Feb. 6, 2018, issued in connection with U.S. Appl. No. 15/211,689, filed Jul. 15, 2016, 32 pages. |
Non-Final Office Action dated Feb. 6, 2018, issued in connection with U.S. Appl. No. 15/237,133, filed Aug. 15, 2016, 6 pages. |
Steven J. Nowlan and Geoffrey E. Hinton “Simplifying Neural Networks by Soft Weight-Sharing” Neural Computation 4, 1992, 21 pages. |
Tsiami et al. “Experiments in acoustic source localization using sparse arrays in adverse indoors environments”, 2014 22nd European Signal Processing Conference, Sep. 1, 2014, 5 pages. |
Tsung-Hsien Wen et al: “A Network-based End-to-End Trainable Task-oriented Dialogue System”, Corr Arxiv, vol. 1604.04562v1, Apr. 15, 2016, pp. 1-11, XP055396370, Stroudsburg, PA, USA. |
Tweet: “How to start using Google app voice commands to make your life easier Share This Story shop @Bullet”, Jan. 21, 2016, https://bgr.com/2016/01/21/best-ok-google-voice-commands/, 3 page. |
Ullrich et al. “Soft Weight-Sharing for Neural Network Compression.” ICLR 2017, 16 pages. |
United States Patent and Trademark Office, U.S. Appl. No. 60/490,768, filed Jul. 28, 2003, entitled “Method for synchronizing audio playback between multiple networked devices,” 13 pages. |
United States Patent and Trademark Office, U.S. Appl. No. 60/825,407, filed Sep. 12, 2006, entitled “Controlling and manipulating groupings in a multi-zone music or media system,” 82 pages. |
UPnP; “Universal Plug and Play Device Architecture,” Jun. 8, 2000; version 1.0; Microsoft Corporation; pp. 1-54. |
Vacher at al. “Recognition of voice commands by multisource ASR and noise cancellation in a smart home environment” Signal Processing Conference 2012 Proceedings of the 20th European, IEEE, Aug. 27, 2012, 5 pages. |
Vacher et al. “Speech Recognition in a Smart Home: Some Experiments for Telemonitoring,” 2009 Proceedings of the 5th Conference on Speech Technology and Human-Computer Dialogoue, Constant, 2009, 10 pages. |
“S Voice or Google Now?”; https://web.archive.org/web/20160807040123/lowdown.carphonewarehouse.com/news/s-voice-or-google-now/ . . . , Apr. 28, 2015; 4 pages. |
Wen et al. A Network-based End-to-End Trainable Task-oriented Dialogue System, Corr (Arxiv), Apr. 15, 2016, 11 pages. |
Wu et al. End-to-End Recurrent Entity Network for Entity-Value Independent Goal-Oriented Dialog Learning. DSTC6—Dialog System Technology Challenges, Dec. 10, 2017, 5 pages. |
Wung et al. “Robust Acoustic Echo Cancellation in the Short-Time Fourier Transform Domain Using Adaptive Crossband Filters” IEEE International Conference on Acoustic, Speech and Signal Processing ICASSP, 2014, p. 1300-1304. |
Xiao et al. “A Learning-Based Approach to Direction of Arrival Estimation in Noisy and Reverberant Environments,” 2015 IEEE International Conference on Acoustics, Speech and Signal Processing, Apr. 19, 2015, 5 pages. |
Xiaoguang et al. “Robust Small-Footprint Keyword Spotting Using Sequence-To-Sequence Model with Connectionist Temporal Classifier”, 2019 IEEE, Sep. 28, 2019, 5 pages. |
Xu et al. An End-to-end Approach for Handling Unknown Slot Values in Dialogue State Tracking. ARXIV.org, Cornell University Library, May 3, 2018, 10 pages. |
Yamaha DME 64 Owner's Manual; copyright 2004, 80 pages. |
Yamaha DME Designer 3.0 Owner's Manual; Copyright 2008, 501 pages. |
Yamaha DME Designer 3.5 setup manual guide; copyright 2004, 16 pages. |
Yamaha DME Designer 3.5 User Manual; Copyright 2004, 507 pages. |
Zaykovskiy, Dmitry. Survey of the Speech Recognition Techniques for Mobile Devices. Proceedings of Specom 2006, Jun. 25, 2006, 6 pages. |
Non-Final Office Action dated Jan. 6, 2021, issued in connection with U.S. Appl. No. 16/439,046, filed Jun. 12, 2019, 13 pages. |
Non-Final Office Action dated Mar. 6, 2020, issued in connection with U.S. Appl. No. 16/141,875, filed Sep. 25, 2018, 8 pages. |
Non-Final Office Action dated Sep. 6, 2017, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 13 pages. |
Non-Final Office Action dated Sep. 6, 2018, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 29 pages. |
Non-Final Office Action dated Dec. 7, 2021, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 36 pages. |
Non-Final Office Action dated Sep. 8, 2020, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 19 pages. |
Non-Final Office Action dated Apr. 9, 2018, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 18 pages. |
Non-Final Office Action dated Apr. 9, 2021, issued in connection with U.S. Appl. No. 16/780,483, filed Feb. 3, 2020, 45 pages. |
Non-Final Office Action dated Feb. 9, 2021, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 16 pages. |
Non-Final Office Action dated May 9, 2018, issued in connection with U.S. Appl. No. 15/818,051, filed Nov. 20, 2017, 22 pages. |
Non-Final Office Action dated Sep. 9, 2020, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 29 pages. |
Notice of Allowance dated Aug. 10, 2021, issued in connection with U.S. Appl. No. 17/157,686, filed Jan. 25, 2021, 9 pages. |
Notice of Allowance dated Aug. 2, 2021, issued in connection with U.S. Appl. No. 16/660,197, filed Oct. 22, 2019, 7 pages. |
Notice of Allowance dated Mar. 31, 2021, issued in connection with U.S. Appl. No. 16/813,643, filed Mar. 9, 2020, 11 pages. |
Notice of Allowance dated Aug. 4, 2021, issued in connection with U.S. Appl. No. 16/780,483, filed Feb. 3, 2020, 5 pages. |
Notice of Allowance dated Dec. 2, 2019, issued in connection with U.S. Appl. No. 15/718,521, filed Sep. 28, 2017, 15 pages. |
Notice of Allowance dated Dec. 4, 2017, issued in connection with U.S. Appl. No. 15/277,810, filed Sep. 27, 2016, 5 pages. |
Notice of Allowance dated Jul. 5, 2018, issued in connection with U.S. Appl. No. 15/237,133, filed Aug. 15, 2016, 5 pages. |
Notice of Allowance dated Jul. 9, 2018, issued in connection with U.S. Appl. No. 15/438,741, filed Feb. 21, 2017, 5 pages. |
Notice of Allowance dated Apr. 1, 2019, issued in connection with U.S. Appl. No. 15/935,966, filed Mar. 26, 2018, 5 pages. |
Notice of Allowance dated Aug. 1, 2018, issued in connection with U.S. Appl. No. 15/297,627, filed Oct. 19, 2016, 9 pages. |
Notice of Allowance dated Jun. 1, 2021, issued in connection with U.S. Appl. No. 16/219,702, filed Dec. 13, 2018, 8 pages. |
Notice of Allowance dated Jun. 1, 2021, issued in connection with U.S. Appl. No. 16/685,135, filed Nov. 15, 2019, 10 pages. |
Notice of Allowance dated Sep. 1, 2021, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 22 pages. |
Notice of Allowance dated Aug. 10, 2020, issued in connection with U.S. Appl. No. 16/424,825, filed May 29, 2019, 9 pages. |
Notice of Allowance dated Feb. 10, 2021, issued in connection with U.S. Appl. No. 16/138,111, filed Sep. 21, 2018, 8 pages. |
Notice of Allowance dated Apr. 11, 2018, issued in connection with U.S. Appl. No. 15/719,454, filed Sep. 28, 2017, 15 pages. |
Notice of Allowance dated Oct. 11, 2019, issued in connection with U.S. Appl. No. 16/437,476, filed Jun. 11, 2019, 9 pages. |
Notice of Allowance dated Sep. 11, 2019, issued in connection with U.S. Appl. No. 16/154,071, filed Oct. 8, 2018, 5 pages. |
Notice of Allowance dated Aug. 12, 2021, issued in connection with U.S. Appl. No. 16/819,755, filed Mar. 16, 2020, 6 pages. |
Notice of Allowance dated Dec. 12, 2018, issued in connection with U.S. Appl. No. 15/811,468, filed Nov. 13, 2017, 9 pages. |
Notice of Allowance dated Jul. 12, 2017, issued in connection with U.S. Appl. No. 15/098,805, filed Apr. 14, 2016, 8 pages. |
Notice of Allowance dated Jun. 12, 2019, issued in connection with U.S. Appl. No. 15/670,361, filed Aug. 7, 2017, 7 pages. |
Notice of Allowance dated May 12, 2021, issued in connection with U.S. Appl. No. 16/402,617, filed May 3, 2019, 8 pages. |
Notice of Allowance dated Sep. 12, 2018, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 15 pages. |
Notice of Allowance dated Dec. 13, 2017, issued in connection with U.S. Appl. No. 15/784,952, filed Oct. 16, 2017, 9 pages. |
Notice of Allowance dated Feb. 13, 2019, issued in connection with U.S. Appl. No. 15/959,907, filed Apr. 23, 2018, 10 pages. |
Notice of Allowance dated Jan. 13, 2020, issued in connection with U.S. Appl. No. 16/192,126, filed Nov. 15, 2018, 6 pages. |
Notice of Allowance dated Jan. 13, 2021, issued in connection with U.S. Appl. No. 16/539,843, filed Aug. 13, 2019, 5 pages. |
Notice of Allowance dated Nov. 13, 2020, issued in connection with U.S. Appl. No. 16/131,409, filed Sep. 14, 2018, 11 pages. |
Notice of Allowance dated Aug. 14, 2017, issued in connection with U.S. Appl. No. 15/098,867, filed Apr. 14, 2016, 10 pages. |
Notice of Allowance dated Aug. 14, 2020, issued in connection with U.S. Appl. No. 16/598,125, filed Oct. 10, 2019, 5 pages. |
Notice of Allowance dated Feb. 14, 2017, issued in connection with U.S. Appl. No. 15/229,855, filed Aug. 5, 2016, 11 pages. |
Notice of Allowance dated Jan. 14, 2021, issued in connection with U.S. Appl. No. 17/087,423, filed Nov. 2, 2020, 8 pages. |
Notice of Allowance dated Jun. 14, 2017, issued in connection with U.S. Appl. No. 15/282,554, filed Sep. 30, 2016, 11 pages. |
Notice of Allowance dated Nov. 14, 2018, issued in connection with U.S. Appl. No. 15/297,627, filed Oct. 19, 2016, 5 pages. |
Notice of Allowance dated Dec. 15, 2017, issued in connection with U.S. Appl. No. 15/223,218, filed Jul. 29, 2016, 7 pages. |
Notice of Allowance dated Jan. 15, 2020, issued in connection with U.S. Appl. No. 16/439,009, filed Jun. 12, 2019, 9 pages. |
Notice of Allowance dated Mar. 15, 2019, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 9 pages. |
Notice of Allowance dated Oct. 15, 2019, issued in connection with U.S. Appl. No. 16/437,437, filed Jun. 11, 2019, 9 pages. |
Japanese Patent Office, Office Action and Translation dated Apr. 20, 2021, issued in connection with Japanese Patent Application No. 2020-513852, 9 pages. |
Japanese Patent Office, Office Action and Translation dated Feb. 24, 2021, issued in connection with Japanese Patent Application No. 2019-517281, 4 pages. |
Japanese Patent Office, Office Action and Translation dated Apr. 27, 2021, issued in connection with Japanese Patent Application No. 2020-518400, 10 pages. |
Japanese Patent Office, Office Action and Translation dated Aug. 27, 2020, issued in connection with Japanese Patent Application No. 2019-073349, 6 pages. |
Japanese Patent Office, Office Action and Translation dated Jul. 30, 2020, issued in connection with Japanese Patent Application No. 2019-517281, 6 pages. |
Japanese Patent Office, Office Action and Translation dated Jul. 6, 2020, issued in connection with Japanese Patent Application No. 2019-073348, 10 pages. |
Japanese Patent Office, Office Action and Translation dated Jul. 6, 2021, issued in connection with Japanese Patent Application No. 2019-073349, 6 pages. |
Japanese Patent Office, Office Action and Translation dated Oct. 8, 2019, issued in connection with Japanese Patent Application No. 2019-521032, 5 pages. |
Japanese Patent Office, Office Action dated Dec. 7, 2021, issued in connection with Japanese Patent Application No. 2020-513852, 6 pages. |
Japanese Patent Office, Office Action Translation dated Nov. 5, 2019, issued in connection with Japanese Patent Application No. 2019-517281, 2 pages. |
Japanese Patent Office, Office Action Translation dated Oct. 8, 2019, issued in connection with Japanese Patent Application No. 2019-521032, 8 pages. |
Jo et al., “Synchronized One-to-many Media Streaming with Adaptive Playout Control,” Proceedings of SPIE, 2002, pp. 71-82, vol. 4861. |
Johnson, “Implementing Neural Networks into Modern Technology,” IJCNN'99. International Joint Conference on Neural Networks . Proceedings [Cat. No. 99CH36339], Washington, DC, USA, 1999, pp. 1028-1032, vol. 2, doi: 10.1109/IJCNN.1999.831096. [retrieved on Jun. 22, 2020]. |
Jones, Stephen, “Dell Digital Audio Receiver: Digital upgrade for your analog stereo,” Analog Stereo, Jun. 24, 2000 http://www.reviewsonline.com/articles/961906864.htm retrieved Jun. 18, 2014, 2 pages. |
Jose Alvarez and Mathieu Salzmann “Compression-aware Training of Deep Networks” 31st Conference on Neural Information Processing Systems, Nov. 13, 2017, 12pages. |
Joseph Szurley et al, “Efficient computation of microphone utility in a wireless acoustic sensor network with multi-channel Wiener filter based noise reduction”, 2012 IEEE International Conference on Acoustics, Speech and Signal Processing, Kyoto, Japan, Mar. 25-30, 2012, pp. 2657-2660, XP032227701, DOI: 10.1109/ICASSP .2012.6288463 ISBN: 978-1-4673-0045-2. |
Ketabdar et al. Detection of Out-of-Vocabulary Words in Posterior Based ASR. Proceedings of Interspeech 2007, Aug. 27, 2007, 4 pages. |
Kim et al. Character-Aware Neural Language Models. Retrieved from the Internet: URL: https://arxiv.org/pdf/1508.06615v3.pdf, Oct. 16, 2015, 9 pages. |
Korean Patent Office, Korean Examination Report and Translation dated Nov. 25, 2021, issued in connection with Korean Application No. 10-2021-7008937, 14 pages. |
Korean Patent Office, Korean Examination Report and Translation dated Apr. 26, 2021, issued in connection with Korean Application No. 10-2021-7008937, 15 pages. |
Korean Patent Office, Korean Office Action and Translation dated Oct. 14, 2021, issued in connection with Korean Application No. 10-2020-7011843, 29 pages. |
Korean Patent Office, Korean Office Action and Translation dated Aug. 16, 2019, issued in connection with Korean Application No. 10-2018-7027452, 14 pages. |
Korean Patent Office, Korean Office Action and Translation dated Apr. 2, 2020, issued in connection with Korean Application No. 10-2020-7008486, 12 pages. |
Korean Patent Office, Korean Office Action and Translation dated Mar. 25, 2020, issued in connection with Korean Application No. 10-2019-7012192, 14 pages. |
Korean Patent Office, Korean Office Action and Translation dated Aug. 26, 2020, issued in connection with Korean Application No. 10-2019-7027640, 16 pages. |
Korean Patent Office, Korean Office Action and Translation dated Mar. 30, 2020, issued in connection with Korean Application No. 10-2020-7004425, 5 pages. |
Korean Patent Office, Korean Office Action and Translation dated Jan. 4, 2021, issued in connection with Korean Application No. 10-2020-7034425, 14 pages. |
Korean Patent Office, Korean Office Action and Translation dated Sep. 9, 2019, issued in connection with Korean Application No. 10-2018-7027451, 21 pages. |
Korean Patent Office, Korean Office Action dated May 8, 2019, issued in connection with Korean Application No. 10-2018-7027451, 7 pages. |
Korean Patent Office, Korean Office Action dated May 8, 2019, issued in connection with Korean Application No. 10-2018-7027452, 5 pages. |
Lei et al. Accurate and Compact Large Vocabulary Speech Recognition on Mobile Devices. Interspeech 2013, Aug. 25, 2013, 4 pages. |
Lengerich et al. An End-to-End Architecture for Keyword Spotting and Voice Activity Detection, arXiv:1611.09405v1, Nov. 28, 2016, 5 pages. |
Louderback, Jim, “Affordable Audio Receiver Furnishes Homes With MP3,” TechTV Vault. Jun. 28, 2000 retrieved Jul. 10, 2014, 2 pages. |
Maja Taseska and Emanual A.P. Habets, “MMSE-Based Blind Source Extraction in Diffuse Noise Fields Using a Complex Coherence-Based a Priori Sap Estimator.” International Workshop on Acoustic Signal Enhancement 2012, Sep. 4-6, 2012, 4pages. |
Matrix—The Ultimate Development Board Sep. 14, 2019 Matrix—The Ultimate Development Board Sep. 14, 2019 https-//web.archive.org/web/20190914035838/https-//www.matrix.one/ , 1 page. |
Mesaros et al. Detection and Classification of Acoustic Scenes and Events: Outcome of the DCASE 2016 Challenge. IEEE/ACM Transactions on Audio, Speech, and Language Processing. Feb. 2018, 16 pages. |
Morales-Cordovilla et al. “Room Localization for Distant Speech Recognition,” Proceedings of Interspeech 2014, Sep. 14, 2014, 4 pages. |
Newman, Jared. “Chromecast Audio's multi-room support has arrived,” Dec. 11, 2015, https://www.pcworld.com/article/3014204/customer-electronic/chromcase-audio-s-multi-room-support-has . . . , 1 page. |
Ngo et al. “Incorporating the Conditional Speech Presence Probability in Multi-Channel Wiener Filter Based Noise Reduction in Hearing Aids.” EURASIP Journal on Advances in Signal Processing vol. 2009, Jun. 2, 2009, 11 pages. |
Non-Final Office Action dated Jul. 12, 2021, issued in connection with U.S. Appl. No. 17/008,104, filed Aug. 31, 2020, 6 pages. |
Non-Final Office Action dated Jun. 18, 2021, issued in connection with U.S. Appl. No. 17/236,559, filed Apr. 21, 2021, 9 pages. |
Non-Final Office Action dated Dec. 21, 2020, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 22 pages. |
Non-Final Office Action dated Jul. 22, 2021, issued in connection with U.S. Appl. No. 16/179,779, filed Nov. 2, 2018, 19 pages. |
Non-Final Office Action dated Apr. 23, 2021, issued in connection with U.S. Appl. No. 16/660,197, filed Oct. 22, 2019, 9 pages. |
Non-Final Office Action dated Jun. 25, 2021, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 11 pages. |
Non-Final Office Action dated Jul. 8, 2021, issued in connection with U.S. Appl. No. 16/813,643, filed Mar. 9, 2020, 12 pages. |
Non-Final Office Action dated Dec. 9, 2020, issued in connection with U.S. Appl. No. 16/271,550, filed Feb. 8, 2019, 35 pages. |
Non-Final Office Action dated Jul. 9, 2021, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 18 pages. |
International Bureau, International Preliminary Report on Patentability, dated Apr. 23, 2019, issued in connection with International Application No. PCT/US2017/057220, filed on Oct. 18, 2017, 7 pages. |
International Bureau, International Preliminary Report on Patentability, dated Mar. 31, 2020, issued in connection with International Application No. PCT/US2018053123, filed on Sep. 27, 2018, 12 pages. |
International Bureau, International Preliminary Report on Patentability, dated Mar. 31, 2020, issued in connection with International Application No. PCT/US2018053472, filed on Sep. 28, 2018, 8 pages. |
International Bureau, International Preliminary Report on Patentability, dated Mar. 31, 2020, issued in connection with International Application No. PCT/US2018053517, filed on Sep. 28, 2018, 10 pages. |
International Bureau, International Preliminary Report on Patentability, dated Sep. 7, 2018, issued in connection with International Application No. PCT/US2017/018728, filed on Feb. 21, 2017, 8 pages. |
International Bureau, International Preliminary Report on Patentability, dated Sep. 7, 2018, issued in connection with International Application No. PCT/US2017/018739, filed on Feb. 21, 2017, 7 pages. |
International Bureau, International Search Report and Written Opinion dated Nov. 10, 2020, issued in connection with International Application No. PCT/US2020/044250, filed on Jul. 30, 2020, 15 pages. |
International Bureau, International Search Report and Written Opinion dated Dec. 11, 2019, issued in connection with International Application No. PCT/US2019/052129, filed on Sep. 20, 2019, 18 pages. |
International Bureau, International Search Report and Written Opinion dated Nov. 13, 2018, issued in connection with International Application No. PCT/US2018/045397, filed on Aug. 6, 2018, 11 pages. |
International Bureau, International Search Report and Written Opinion dated Jan. 14, 2019, issued in connection with International Application No. PCT/US2018053472, filed on Sep. 28, 2018, 10 pages. |
International Bureau, International Search Report and Written Opinion dated Jul. 14, 2020, issued in connection with International Application No. PCT/US2020/017150, filed on Feb. 7, 2020, 27 pages. |
International Bureau, International Search Report and Written Opinion dated Nov. 14, 2017, issued in connection with International Application No. PCT/US2017/045521, filed on Aug. 4, 2017, 10 pages. |
International Bureau, International Search Report and Written Opinion dated Jul. 17, 2019, issued in connection with International Application No. PCT/US2019/032934, filed on May 17, 2019, 17 pages. |
International Bureau, International Search Report and Written Opinion dated Nov. 18, 2019, issued in connection with International Application No. PCT/US2019/048558, filed on Aug. 28, 2019, 11 pages. |
International Bureau, International Search Report and Written Opinion dated Nov. 18, 2019, issued in connection with International Application No. PCT/US2019052841, filed on Sep. 25, 2019, 12 pages. |
International Bureau, International Search Report and Written Opinion dated Mar. 2, 2020, issued in connection with International Application No. PCT/US2019064907, filed on Dec. 6, 2019, 11 pages. |
International Bureau, International Search Report and Written Opinion dated Mar. 2, 2020, issued in connection with International Application No. PCT/US2019/064907, filed on Dec. 6, 2019, 9 pages. |
International Bureau, International Search Report and Written Opinion dated Dec. 20, 2019, issued in connection with International Application No. PCT/US2019052654, filed on Sep. 24, 2019, 11 pages. |
International Bureau, International Search Report and Written Opinion dated Sep. 21, 2020, issued in connection with International Application No. PCT/US2020/037229, filed on Jun. 11, 2020, 17 pages. |
International Bureau, International Search Report and Written Opinion dated Oct. 22, 2020, issued in connection with International Application No. PCT/US2020/044282, filed on Jul. 30, 2020, 15 pages. |
International Bureau, International Search Report and Written Opinion dated Apr. 23, 2021, issued in connection with International Application No. PCT/US2021/070007, filed on Jan. 6, 2021, 11 pages. |
International Bureau, International Search Report and Written Opinion dated Jul. 24, 2018, issued in connection with International Application No. PCT/US2018/019010, filed on Feb. 21, 2018, 12 pages. |
International Bureau, International Search Report and Written Opinion, dated Feb. 27, 2019, issued in connection with International Application No. PCT/US2018/053123, filed on Sep. 27, 2018, 16 pages. |
International Bureau, International Search Report and Written Opinion dated Sep. 27, 2019, issued in connection with International Application No. PCT/US2019/039828, filed on Jun. 28, 2019, 13 pages. |
International Bureau, International Search Report and Written Opinion dated Nov. 29, 2019, issued in connection with International Application No. PCT/US2019/053253, filed on Sep. 29, 2019, 14 pages. |
International Bureau, International Search Report and Written Opinion dated Sep. 4, 2019, issued in connection with International Application No. PCT/US2019/033945, filed on May 24, 2019, 8 pages. |
International Bureau, International Search Report and Written Opinion dated Aug. 6, 2020, issued in connection with International Application No. PCT/FR2019/000081, filed on May 24, 2019, 12 pages. |
International Bureau, International Search Report and Written Opinion dated Dec. 6, 2018, issued in connection with International Application No. PCT/US2018/050050, filed on Sep. 7, 2018, 9 pages. |
International Bureau, International Search Report and Written Opinion dated Dec. 6, 2019, issued in connection with International Application No. PCT/US2019050852, filed on Sep. 12, 2019, 10 pages. |
International Bureau, International Search Report and Written Opinion dated Oct. 6, 2017, issued in connection with International Application No. PCT/US2017/045551, filed on Aug. 4, 2017, 12 pages. |
International Bureau, International Search Report and Written Opinion dated Apr. 8, 2020, issued in connection with International Application No. PCT/US2019/067576, filed on Dec. 19, 2019, 12 pages. |
International Searching Authority, International Search Report and Written Opinion dated Feb. 8, 2021, issued in connection with International Application No. PCT/EP2020/082243, filed on Nov. 16, 2020, 10 pages. |
International Searching Authority, International Search Report and Written Opinion dated Feb. 12, 2021, issued in connection with International Application No. PCT/US2020/056632, filed on Oct. 21, 2020, 10 pages. |
International Searching Authority, International Search Report and Written Opinion dated Dec. 19, 2018, in connection with International Application No. PCT/US2018/053517, 13 pages. |
International Searching Authority, International Search Report and Written Opinion dated Nov. 22, 2017, issued in connection with International Application No. PCT/US2017/054063, filed on Sep. 28, 2017, 11 pages. |
International Searching Authority, International Search Report and Written Opinion dated Apr. 23, 2021, issued in connection with International Application No. PCT/US2020/066231, filed on Dec. 18, 2020, 9 pages. |
International Searching Authority, International Search Report and Written Opinion dated Jan. 23, 2018, issued in connection with International Application No. PCT/US2017/57220, filed on Oct. 18, 2017, 8 pages. |
International Searching Authority, International Search Report and Written Opinion dated May 23, 2017, issued in connection with International Application No. PCT/US2017/018739, Filed on Feb. 21, 2017, 10 pages. |
International Searching Authority, International Search Report and Written Opinion dated Oct. 23, 2017, issued in connection with International Application No. PCT/US2017/042170, filed on Jul. 14, 2017, 15 pages. |
International Searching Authority, International Search Report and Written Opinion dated Oct. 24, 2017, issued in connection with International Application No. PCT/US2017/042227, filed on Jul. 14, 2017, 16 pages. |
International Searching Authority, International Search Report and Written Opinion dated May 30, 2017, issued in connection with International Application No. PCT/US2017/018728, Filed on Feb. 21, 2017, 11 pages. |
Japanese Patent Office, Decision of Refusal and Translation dated Jun. 8, 2021, issued in connection with Japanese Patent Application No. 2019-073348, 5 pages. |
Japanese Patent Office, English Translation of Office Action dated Nov. 17, 2020, issued in connection with Japanese Application No. 2019-145039, 5 pages. |
Japanese Patent Office, English Translation of Office Action dated Aug. 27, 2020, issued in connection with Japanese Application No. 2019-073349, 6 pages. |
Japanese Patent Office, English Translation of Office Action dated Jul. 30, 2020, issued in connection with Japanese Application No. 2019-517281, 26 pages. |
Japanese Patent Office, Non-Final Office Action and Translation dated Nov. 5, 2019, issued in connection with Japanese Patent Application No. 2019-517281, 6 pages. |
Japanese Patent Office, Notice of Reasons for Refusal and Translation dated Jun. 22, 2021, issued in connection with Japanese Patent Application No. 2020-517935, 4 pages. |
Japanese Patent Office, Notice of Reasons for Refusal and Translation dated Nov. 28, 2021, issued in connection with Japanese Patent Application No. 2020-550102, 9 pages. |
Japanese Patent Office, Office Action and Translation dated Mar. 16, 2021, issued in connection with Japanese Patent Application No. 2020-506725, 7 pages. |
Japanese Patent Office, Office Action and Translation dated Nov. 17, 2020, issued in connection with Japanese Patent Application No. 2019-145039, 7 pages. |
Non-Final Office Action dated Jun. 1, 2017, issued in connection with U.S. Appl. No. 15/223,218, filed Jul. 29, 2016, 7 pages. |
Non-Final Office Action dated Nov. 2, 2017, issued in connection with U.S. Appl. No. 15/584,782, filed May 2, 2017, 11 pages. |
Non-Final Office Action dated Nov. 3, 2017, issued in connection with U.S. Appl. No. 15/438,741, filed Feb. 21, 2017, 11 pages. |
Non-Final Office Action dated Nov. 4, 2019, issued in connection with U.S. Appl. No. 16/022,662, filed Jun. 28, 2018, 16 pages. |
Non-Final Office Action dated Sep. 5, 2019, issued in connection with U.S. Appl. No. 16/416,752, filed May 20, 2019, 14 pages. |
Non-Final Office Action dated Feb. 7, 2017, issued in connection with U.S. Appl. No. 15/131,244, filed Apr. 18, 2016, 12 pages. |
Non-Final Office Action dated Feb. 8, 2017, issued in connection with U.S. Appl. No. 15/098,892, filed Apr. 14, 2016, 17 pages. |
Non-Final Office Action dated Mar. 9, 2017, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 13 pages. |
Non-Final Office Action dated Oct. 9, 2019, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 16 pages. |
Non-Final Office Action dated Jul. 1, 2020, issued in connection with U.S. Appl. No. 16/138,111, filed Sep. 21, 2018, 14 pages. |
Non-Final Office Action dated Jan. 10, 2018, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 15 pages. |
Non-Final Office Action dated Jan. 10, 2018, issued in connection with U.S. Appl. No. 15/229,868, filed Aug. 5, 2016, 13 pages. |
Non-Final Office Action dated Jan. 10, 2018, issued in connection with U.S. Appl. No. 15/438,725, filed Feb. 21, 2017, 15 pages. |
Non-Final Office Action dated Sep. 10, 2018, issued in connection with U.S. Appl. No. 15/670,361, filed Aug. 7, 2017, 17 pages. |
Non-Final Office Action dated Aug. 11, 2021, issued in connection with U.S. Appl. No. 16/841,116, filed Apr. 6, 2020, 9 pages. |
Non-Final Office Action dated Feb. 11, 2021, issued in connection with U.S. Appl. No. 16/876,493, filed May 18, 2020, 16 pages. |
Non-Final Office Action dated Mar. 11, 2021, issued in connection with U.S. Appl. No. 16/834,483, filed Mar. 30, 2020, 11 pages. |
Non-Final Office Action dated Oct. 11, 2019, issued in connection with U.S. Appl. No. 16/177,185, filed Oct. 31, 2018, 14 pages. |
Non-Final Office Action dated Sep. 11, 2020, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 8 pages. |
Non-Final Office Action dated Sep. 11, 2020, issued in connection with U.S. Appl. No. 16/219,702, filed Dec. 13, 2018, 9 pages. |
Non-Final Office Action dated Apr. 12, 2021, issued in connection with U.S. Appl. No. 16/528,224, filed Jul. 31, 2019, 9 pages. |
Non-Final Office Action dated Dec. 12, 2016, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 11 pages. |
Non-Final Office Action dated Feb. 12, 2019, issued in connection with U.S. Appl. No. 15/670,361, filed Aug. 7, 2017, 13 pages. |
Non-Final Office Action dated Jan. 13, 2017, issued in connection with U.S. Appl. No. 15/098,805, filed Apr. 14, 2016, 11 pages. |
Non-Final Office Action dated Nov. 13, 2018, issued in connection with U.S. Appl. No. 15/717,621, filed Sep. 27, 2017, 23 pages. |
Non-Final Office Action dated Nov. 13, 2018, issued in connection with U.S. Appl. No. 16/160,107, filed Oct. 15, 2018, 8 pages. |
Non-Final Office Action dated Nov. 13, 2019, issued in connection with U.S. Appl. No. 15/984,073, filed May 18, 2018, 18 pages. |
Non-Final Office Action dated Oct. 13, 2021, issued in connection with U.S. Appl. No. 16/679,538, filed Nov. 11, 2019, 8 pages. |
Non-Final Office Action dated May 14, 2020, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 8 pages. |
Non-Final Office Action dated Sep. 14, 2017, issued in connection with U.S. Appl. No. 15/178,180, filed Jun. 9, 2016, 16 pages. |
Non-Final Office Action dated Sep. 14, 2018, issued in connection with U.S. Appl. No. 15/959,907, filed Apr. 23, 2018, 15 pages. |
Non-Final Office Action dated Apr. 15, 2020, issued in connection with U.S. Appl. No. 16/138,111, filed Sep. 21, 2018, 15 pages. |
Non-Final Office Action dated Dec. 15, 2020, issued in connection with U.S. Appl. No. 17/087,423, filed Nov. 2, 2020, 7 pages. |
Non-Final Office Action dated Jan. 15, 2019, issued in connection with U.S. Appl. No. 16/173,797, filed Oct. 29, 2018, 6 pages. |
Non-Final Office Action dated Nov. 15, 2019, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 17 pages. |
Non-Final Office Action dated Mar. 16, 2018, issued in connection with U.S. Appl. No. 15/681,937, filed Aug. 21, 2017, 5 pages. |
Non-Final Office Action dated Oct. 16, 2018, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 16 pages. |
Non-Final Office Action dated Sep. 16, 2021, issued in connection with U.S. Appl. No. 16/879,553, filed May 20, 2020, 24 pages. |
Non-Final Office Action dated Aug. 17, 2021, issued in connection with U.S. Appl. No. 17/236,559, filed Apr. 21, 2021, 10 pages. |
Non-Final Office Action dated Sep. 17, 2020, issued in connection with U.S. Appl. No. 16/600,949, filed Oct. 14, 2019, 29 pages. |
Non-Final Office Action dated Apr. 18, 2018, issued in connection with U.S. Appl. No. 15/811,468, filed Nov. 13, 2017, 14 pages. |
Non-Final Office Action dated Aug. 18, 2021, issued in connection with U.S. Appl. No. 16/845,946, filed Apr. 10, 2020, 14 pages. |
Non-Final Office Action dated Jan. 18, 2019, issued in connection with U.S. Appl. No. 15/721,141, filed Sep. 29, 2017, 18 pages. |
Non-Final Office Action dated Oct. 18, 2019, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 27 pages. |
Non-Final Office Action dated Sep. 18, 2019, issued in connection with U.S. Appl. No. 16/179,779, filed Nov. 2, 2018, 14 pages. |
Non-Final Office Action dated Apr. 19, 2017, issued in connection with U.S. Appl. No. 15/131,776, filed Apr. 18, 2016, 12 pages. |
Non-Final Office Action dated Dec. 19, 2019, issued in connection with U.S. Appl. No. 16/147,710, filed Sep. 29, 2018, 10 pages. |
Non-Final Office Action dated Feb. 19, 2020, issued in connection with U.S. Appl. No. 16/148,879, filed Oct. 1, 2018, 15 pages. |
Non-Final Office Action dated Sep. 2, 2020, issued in connection with U.S. Appl. No. 16/290,599, filed Mar. 1, 2019, 17 pages. |
Non-Final Office Action dated Sep. 2, 2021, issued in connection with U.S. Appl. No. 16/947,895, filed Aug. 24, 2020, 16 pages. |
Dell, Inc. “Dell Digital Audio Receiver: Reference Guide,” Jun. 2000, 70 pages. |
Dell, Inc. “Start Here,” Jun. 2000, 2 pages. |
“Denon 2003-2004 Product Catalog,” Denon, 2003-2004, 44 pages. |
European Patent Office, European EPC Article 94.3 dated Nov. 11, 2021, issued in connection with European Application No. 19784172.9, 5 pages. |
European Patent Office, European EPC Article 94.3 dated Feb. 23, 2021, issued in connection with European Application No. 17200837.7, 8 pages. |
European Patent Office, European EPC Article 94.3 dated Feb. 26, 2021, issued in connection with European Application No. 18789515.6, 8 pages. |
European Patent Office, European Extended Search Report dated Oct. 7, 2021, issued in connection with European Application No. 21193616.6, 9 pages. |
European Patent Office, European Extended Search Report dated Nov. 25, 2020, issued in connection with European Application No. 20185599.6, 9 pages. |
European Patent Office, European Extended Search Report dated Feb. 3, 2020, issued in connection with European Application No. 19197116.7, 9 pages. |
European Patent Office, European Extended Search Report dated Jan. 3, 2019, issued in connection with European Application No. 177570702, 8 pages. |
European Patent Office, European Extended Search Report dated Jan. 3, 2019, issued in connection with European Application No. 17757075.1, 9 pages. |
European Patent Office, European Extended Search Report dated Oct. 30, 2017, issued in connection with EP Application No. 17174435.2, 11 pages. |
European Patent Office, European Extended Search Report dated Aug. 6, 2020, issued in connection with European Application No. 20166332.5, 10 pages. |
European Patent Office, European Office Action dated Jul. 1, 2020, issued in connection with European Application No. 17757075.1, 7 pages. |
European Patent Office, European Office Action dated Jan. 14, 2020, issued in connection with European Application No. 17757070.2, 7 pages. |
European Patent Office, European Office Action dated Jan. 21, 2021, issued in connection with European Application No. 17792272.1, 7 pages. |
European Patent Office, European Office Action dated Jan. 22, 2019, issued in connection with European Application No. 17174435.2, 9 pages. |
European Patent Office, European Office Action dated Sep. 23, 2020, issued in connection with European Application No. 18788976.1, 7 pages. |
European Patent Office, European Office Action dated Oct. 26, 2020, issued in connection with European Application No. 18760101.8, 4 pages. |
European Patent Office, European Office Action dated Aug. 30, 2019, issued in connection with European Application No. 17781608.9, 6 pages. |
European Patent Office, European Office Action dated Sep. 9, 2020, issued in connection with European Application No. 18792656.3, 10 pages. |
European Patent Office, Examination Report dated Jul. 15, 2021, issued in connection with European Patent Application No. 19729968.8, 7 pages. |
European Patent Office, Extended Search Report dated Aug. 13, 2021, issued in connection with European Patent Application No. 21164130.3, 11 pages. |
European Patent Office, Extended Search Report dated May 16, 2018, issued in connection with European Patent Application No. 17200837.7, 11 pages. |
European Patent Office, Extended Search Report dated Jul. 25, 2019, issued in connection with European Patent Application No. 18306501.0, 14 pages. |
European Patent Office, Extended Search Report dated May 29, 2020, issued in connection with European Patent Application No. 19209389.6, 8 pages. |
European Patent Office, Summons to Attend Oral Proceedings mailed on Dec. 20, 2019, issued in connection with European Application No. 17174435.2, 13 pages. |
Fadilpasic,“Cortana can now be the default PDA on your Android”, IT Pro Portal: Accessed via WayBack Machine; http://web.archive.org/web/20171129124915/https://www.itproportal.com/2015/08/11/cortana-can-now-be- . . . , Aug. 11, 2015, 6 pages. |
Final Office Action dated Jul. 23, 2021, issued in connection with U.S. Appl. No. 16/439,046, filed Jun. 12, 2019, 12 pages. |
Final Office Action dated Oct. 6, 2017, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 25 pages. |
Final Office Action dated Feb. 10, 2021, issued in connection with U.S. Appl. No. 16/219,702, filed Dec. 13, 2018, 9 pages. |
Final Office Action dated Feb. 10, 2021, issued in connection with U.S. Appl. No. 16/402,617, filed May 3, 2019, 13 pages. |
Final Office Action dated Nov. 10, 2020, issued in connection with U.S. Appl. No. 16/600,644, filed Oct. 14, 2019, 19 pages. |
Final Office Action dated Apr. 11, 2019, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 17 pages. |
Final Office Action dated Aug. 11, 2017, issued in connection with U.S. Appl. No. 15/131,776, filed Apr. 18, 2016, 7 pages. |
Final Office Action dated Dec. 11, 2019, issued in connection with U.S. Appl. No. 16/227,308, filed Dec. 20, 2018, 10 pages. |
Final Office Action dated Sep. 11, 2019, issued in connection with U.S. Appl. No. 16/178,122, filed Nov. 1, 2018, 13 pages. |
Final Office Action dated Apr. 13, 2018, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 18 pages. |
Final Office Action dated Apr. 13, 2018, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 20 pages. |
Final Office Action dated May 13, 2020, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 20 pages. |
Final Office Action dated Jul. 15, 2021, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 22 pages. |
Final Office Action dated Jun. 15, 2017, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 15 pages. |
Final Office Action dated Jun. 15, 2021, issued in connection with U.S. Appl. No. 16/819,755, filed Mar. 16, 2020, 12 pages. |
Final Office Action dated Oct. 15, 2018, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 18 pages. |
Final Office Action dated Oct. 15, 2020, issued in connection with U.S. Appl. No. 16/109,375, filed Aug. 22, 2018, 9 pages. |
Final Office Action dated Oct. 16, 2018, issued in connection with U.S. Appl. No. 15/438,725, filed Feb. 21, 2017, 10 pages. |
Final Office Action dated May 18, 2020, issued in connection with U.S. Appl. No. 16/177,185, filed Oct. 31, 2018, 16 pages. |
Final Office Action dated Feb. 21, 2018, issued in connection with U.S. Appl. No. 15/297,627, filed Oct. 19, 2016, 12 pages. |
Final Office Action dated May 21, 2020, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 21 pages. |
Final Office Action dated Feb. 22, 2021, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 20 pages. |
Notice of Allowance dated Oct. 15, 2020, issued in connection with U.S. Appl. No. 16/715,713, filed Dec. 16, 2019, 9 pages. |
Notice of Allowance dated Oct. 15, 2021, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 8 pages. |
Notice of Allowance dated Sep. 15, 2021, issued in connection with U.S. Appl. No. 16/685,135, filed Nov. 15, 2019, 10 pages. |
Notice of Allowance dated Apr. 16, 2021, issued in connection with U.S. Appl. No. 16/798,967, filed Feb. 24, 2020, 16 pages. |
Notice of Allowance dated Aug. 16, 2017, issued in connection with U.S. Appl. No. 15/098,892, filed Apr. 14, 2016, 9 pages. |
Notice of Allowance dated Aug. 17, 2017, issued in connection with U.S. Appl. No. 15/131,244, filed Apr. 18, 2016, 9 pages. |
Notice of Allowance dated Feb. 17, 2021, issued in connection with U.S. Appl. No. 16/715,984, filed Dec. 16, 2019, 8 pages. |
Notice of Allowance dated Jul. 17, 2019, issued in connection with U.S. Appl. No. 15/718,911, filed Sep. 28, 2017, 5 pages. |
Notice of Allowance dated Jun. 17, 2020, issued in connection with U.S. Appl. No. 16/141,875, filed Sep. 25, 2018, 6 pages. |
Notice of Allowance dated Sep. 17, 2018, issued in connection with U.S. Appl. No. 15/211,689, filed Jul. 15, 2016, 6 pages. |
Notice of Allowance dated Apr. 18, 2019, issued in connection with U.S. Appl. No. 16/173,797, filed Oct. 29, 2018, 9 pages. |
Notice of Allowance dated Dec. 18, 2019, issued in connection with U.S. Appl. No. 16/434,426, filed Jun. 7, 2019, 13 pages. |
Notice of Allowance dated Feb. 18, 2020, issued in connection with U.S. Appl. No. 16/022,662, filed Jun. 28, 2018, 8 pages. |
Notice of Allowance dated Jul. 18, 2019, issued in connection with U.S. Appl. No. 15/438,749, filed Feb. 21, 2017, 9 pages. |
Notice of Allowance dated Jul. 18, 2019, issued in connection with U.S. Appl. No. 15/721,141, filed Sep. 29, 2017, 8 pages. |
Notice of Allowance dated Mar. 18, 2021, issued in connection with U.S. Appl. No. 16/177,185, filed Oct. 31, 2018, 8 pages. |
Notice of Allowance dated Aug. 19, 2020, issued in connection with U.S. Appl. No. 16/271,560, filed Feb. 8, 2019, 9 pages. |
Notice of Allowance dated Dec. 19, 2018, issued in connection with U.S. Appl. No. 15/818,051, filed Nov. 20, 2017, 9 pages. |
Notice of Allowance dated Jul. 19, 2018, issued in connection with U.S. Appl. No. 15/681,937, filed Aug. 21, 2017, 7 pages. |
Notice of Allowance dated Mar. 19, 2021, issued in connection with U.S. Appl. No. 17/157,686, filed Jan. 25, 2021, 11 pages. |
Notice of Allowance dated Aug. 2, 2019, issued in connection with U.S. Appl. No. 16/102,650, filed Aug. 13, 2018, 5 pages. |
Notice of Allowance dated Dec. 2, 2020, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 11 pages. |
Notice of Allowance dated Dec. 2, 2021, issued in connection with U.S. Appl. No. 16/841,116, filed Apr. 6, 2020, 5 pages. |
Notice of Allowance dated Sep. 2, 2020, issued in connection with U.S. Appl. No. 16/214,711, filed Dec. 10, 2018, 9 pages. |
Notice of Allowance dated Jul. 20, 2020, issued in connection with U.S. Appl. No. 15/984,073, filed May 18, 2018, 12 pages. |
Notice of Allowance dated Mar. 20, 2018, issued in connection with U.S. Appl. No. 15/784,952, filed Oct. 16, 2017, 7 pages. |
Notice of Allowance dated Oct. 20, 2021, issued in connection with U.S. Appl. No. 16/439,032, filed Jun. 12, 2019, 8 pages. |
Notice of Allowance dated Sep. 20, 2018, issued in connection with U.S. Appl. No. 15/946,599, filed Apr. 5, 2018, 7 pages. |
Notice of Allowance dated Apr. 21, 2021, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 8 pages. |
Notice of Allowance dated Feb. 21, 2020, issued in connection with U.S. Appl. No. 16/416,752, filed May 20, 2019, 6 pages. |
Notice of Allowance dated Jan. 21, 2020, issued in connection with U.S. Appl. No. 16/672,764, filed Nov. 4, 2019, 10 pages. |
Notice of Allowance dated Jan. 21, 2021, issued in connection with U.S. Appl. No. 16/600,644, filed Oct. 14, 2019, 7 pages. |
Notice of Allowance dated Oct. 21, 2019, issued in connection with U.S. Appl. No. 15/946,585, filed Apr. 5, 2018, 5 pages. |
Notice of Allowance dated Aug. 22, 2017, issued in connection with U.S. Appl. No. 15/273,679, filed Sep. 22, 2016, 5 pages. |
Notice of Allowance dated Jan. 22, 2018, issued in connection with U.S. Appl. No. 15/178,180, filed Jun. 9, 2016, 9 pages. |
Notice of Allowance dated Jul. 22, 2020, issued in connection with U.S. Appl. No. 16/131,409, filed Sep. 14, 2018, 13 pages. |
Notice of Allowance dated Jul. 22, 2020, issued in connection with U.S. Appl. No. 16/790,621, filed Feb. 13, 2020, 10 pages. |
Notice of Allowance dated Nov. 22, 2021, issued in connection with U.S. Appl. No. 16/834,483, filed Mar. 30, 2020, 10 pages. |
Notice of Allowance dated Aug. 23, 2021, issued in connection with U.S. Appl. No. 16/109,375, filed Aug. 22, 2018, 10 pages. |
Notice of Allowance dated Jun. 23, 2021, issued in connection with U.S. Appl. No. 16/814,844, filed Mar. 10, 2020, 8 pages. |
Notice of Allowance dated Apr. 24, 2019, issued in connection with U.S. Appl. No. 16/154,469, filed Oct. 3, 2018, 5 pages. |
Notice of Allowance dated Oct. 25, 2021, issued in connection with U.S. Appl. No. 16/723,909, filed Dec. 20, 2019, 11 pages. |
Notice of Allowance dated Aug. 26, 2020, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 9 pages. |
Notice of Allowance dated May 26, 2021, issued in connection with U.S. Appl. No. 16/927,670, filed Jul. 13, 2020, 10 pages. |
Notice of Allowance dated Apr. 27, 2020, issued in connection with U.S. Appl. No. 16/700,607, filed Dec. 2, 2019, 10 pages. |
Notice of Allowance dated Mar. 27, 2019, issued in connection with U.S. Appl. No. 16/214,666, filed Dec. 10, 2018, 6 pages. |
Notice of Allowance dated Mar. 28, 2018, issued in connection with U.S. Appl. No. 15/699,982, filed Sep. 8, 2017, 17 pages. |
Notice of Allowance dated May 28, 2021, issued in connection with U.S. Appl. No. 16/524,306, filed Jul. 29, 2019, 9 pages. |
Notice of Allowance dated Dec. 29, 2017, issued in connection with U.S. Appl. No. 15/131,776, filed Apr. 18, 2016, 13 pages. |
Notice of Allowance dated Jan. 29, 2021, issued in connection with U.S. Appl. No. 16/290,599, filed Mar. 1, 2019, 9 pages. |
Final Office Action dated Feb. 22, 2021, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 12 pages. |
Final Office Action dated Jun. 22, 2020, issued in connection with U.S. Appl. No. 16/179,779, filed Nov. 2, 2018, 16 pages. |
Final Office Action dated Mar. 23, 2020, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 11 pages. |
Final Office Action dated Feb. 24, 2020, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 20 pages. |
Final Office Action dated Apr. 26, 2019, issued in connection with U.S. Appl. No. 15/721,141, filed Sep. 29, 2017, 20 pages. |
Final Office Action dated Nov. 29, 2021, issued in connection with U.S. Appl. No. 17/236,559, filed Apr. 21, 2021, 11 pages. |
Final Office Action dated Apr. 30, 2019, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 6 pages. |
Final Office Action dated Jun. 4, 2021, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 38 pages. |
Final Office Action dated Oct. 4, 2021, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 17 pages. |
Final Office Action dated Feb. 5, 2019, issued in connection with U.S. Appl. No. 15/438,749, filed Feb. 21, 2017, 17 pages. |
Final Office Action dated Feb. 7, 2020, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 8 pages. |
Final Office Action dated Jun. 8, 2021, issued in connection with U.S. Appl. No. 16/271,550, filed Feb. 8, 2019, 41 pages. |
Final Office Action dated Sep. 8, 2020, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 12 pages. |
Fiorenza Arisio et al. “Deliverable 1.1 User Study, analysis of requirements and definition of the application task,” May 31, 2012, http://dirha.fbk.eu/sites/dirha.fbk.eu/files/docs/DIRHA_D1.1., 31 pages. |
First Action Interview Office Action dated Mar. 8, 2021, issued in connection with U.S. Appl. No. 16/798,967, filed Feb. 24, 2020, 4 pages. |
First Action Interview Office Action dated Aug. 14, 2019, issued in connection with U.S. Appl. No. 16/227,308, filed Dec. 20, 2018, 4 pages. |
First Action Interview Office Action dated Jun. 15, 2020, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 4 pages. |
First Action Interview Office Action dated Jun. 2, 2020, issued in connection with U.S. Appl. No. 16/109,375, filed Aug. 22, 2018, 10 pages. |
First Action Interview Office Action dated Jan. 22, 2020, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 3 pages. |
First Action Interview Office Action dated Jul. 5, 2019, issued in connection with U.S. Appl. No. 16/227,308, filed Dec. 20, 2018, 4 pages. |
Freiberger, Kari, “Development and Evaluation of Source Localization Algorithms for Coincident Microphone Arrays,” Diploma Thesis, Apr. 1, 2010, 106 pages. |
Giacobello et al. “A Sparse Nonuniformly Partitioned Multidelay Filter for Acoustic Echo Cancellation,” 2013, IEEE Workshop on Applications of Signal Processing to Audio and Acoustics, Oct. 2013, New Paltz, NY, 4 pages. |
Giacobello et al. “Tuning Methodology for Speech Enhancement Algorithms using a Simulated Conversational Database and Perceptual Objective Measures,” 2014, 4th Joint Workshop on Hands-free Speech Communication and Microphone Arrays HSCMA, 2014, 5 pages. |
Han et al. “Deep Compression: Compressing Deep Neural Networks with Pruning, Trained Quantization and Huffman Coding.” ICLR 2016, Feb. 15, 2016, 14 pages. |
Hans Speidel: “Chatbot Training: How to use training data to provide fully automated customer support”, Jun. 29, 2017, pp. 1-3, XP055473185, Retrieved from the Internet: URL:https://www.crowdguru.de/wp-content/uploads/Case-Study-Chatbot-training-How-to-use-training-data-to-provide-fully-automated-customer-support.pdf [retrieved on May 7, 2018]. |
Helwani et al “Source-domain adaptive filtering for MIMO systems with application to acoustic echo cancellation”, Acoustics Speech and Signal Processing, 2010 IEEE International Conference, Mar. 14, 2010, 4 pages. |
Hirano et al. “A Noise-Robust Stochastic Gradient Algorithm with an Adaptive Step-Size Suitable for Mobile Hands-Free Telephones,” 1995, International Conference on Acoustics, Speech, and Signal Processing, vol. 2, 4 pages. |
Indian Patent Office, Examination Report dated May 24, 2021, issued in connection with Indian Patent Application No. 201847035595, 6 pages. |
Indian Patent Office, Examination Report dated Feb. 25, 2021, issued in connection with Indian Patent Application No. 201847035625, 6 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Apr. 1, 2021, issued in connection with International Application No. PCT/US2019/052129, filed on Sep. 20, 2019, 13 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Jul. 1, 2021, issued in connection with International Application No. PCT/US2019/067576, filed on Dec. 19, 2019, 8 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Aug. 10, 2021, issued in connection with International Application No. PCT/US2020/017150, filed on Feb. 7, 2020, 20 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Dec. 10, 2020, issued in connection with International Application No. PCT/US2019/033945, filed on May 25, 2018, 7 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Mar. 10, 2020, issued in connection with International Application No. PCT/US2018/050050, filed on Sep. 7, 2018, 7 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Apr. 15, 2021, issued in connection with International Application No. PCT/US2019/054332, filed on Oct. 2, 2019, 9 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Jan. 15, 2019, issued in connection with International Application No. PCT/US2017/042170, filed on Jul. 14, 2017, 7 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Jan. 15, 2019, issued in connection with International Application No. PCT/US2017/042227, filed on Jul. 14, 2017, 7 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Mar. 25, 2021, issued in connection with International Application No. PCT/US2019/050852, filed on Sep. 12, 2019, 8 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Aug. 27, 2019, issued in connection with International Application No. PCT/US2018/019010, filed on Feb. 21, 2018, 9 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Mar. 31, 2020, issued in connection with International Application No. PCT/US2018/053517, filed on Sep. 28, 2018, 10 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Feb. 5, 2019, issued in connection with International Application No. PCT/US2017/045521, filed on Aug. 4, 2017, 7 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Feb. 5, 2019, issued in connection with International Application No. PCT/US2017/045551, filed on Aug. 4, 2017, 9 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Jan. 7, 2021, issued in connection with International Application No. PCT/US2019/039828, filed on Jun. 28, 2019, 11 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Apr. 8, 2021, issued in connection with International Application No. PCT/US2019/052654, filed on Sep. 24, 2019, 7 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Apr. 8, 2021, issued in connection with International Application No. PCT/US2019/052841, filed on Sep. 25, 2019, 8 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Apr. 8, 2021, issued in connection with International Application No. PCT/US2019/053253, filed on Sep. 26, 2019, 10 pages. |
International Bureau, International Preliminary Report on Patentability, dated Apr. 11, 2019, issued in connection with International Application No. PCT/US2017/0054063, filed on Sep. 28, 2017, 9 pages. |
International Bureau, International Preliminary Report on Patentability, dated Jun. 17, 2021, issued in connection with International Application No. PCT/US2019/064907, filed on Dec. 6, 2019, 8 pages. |
International Bureau, International Preliminary Report on Patentability, dated Mar. 2, 2021, issued in connection with International Application No. PCT/US2019/048558, filed on Aug. 28, 2019, 8 pages. |
International Bureau, International Preliminary Report on Patentability, dated Feb. 20, 2020, issued in connection with International Application No. PCT/US2018/045397, filed on Aug. 6, 2018, 8 pages. |
Notice of Allowance dated Jun. 29, 2020, issued in connection with U.S. Appl. No. 16/216,357, filed Dec. 11, 2018, 8 pages. |
Notice of Allowance dated Mar. 29, 2021, issued in connection with U.S. Appl. No. 16/600,949, filed Oct. 14, 2019, 9 pages. |
Notice of Allowance dated May 29, 2020, issued in connection with U.S. Appl. No. 16/148,879, filed Oct. 1, 2018, 6 pages. |
Notice of Allowance dated Sep. 29, 2021, issued in connection with U.S. Appl. No. 16/876,493, filed May 18, 2020, 5 pages. |
Notice of Allowance dated Apr. 3, 2019, issued in connection with U.S. Appl. No. 16/160,107, filed Oct. 15, 2018, 7 pages. |
Notice of Allowance dated Jun. 3, 2021, issued in connection with U.S. Appl. No. 16/876,493, filed May 18, 2020, 7 pages. |
Notice of Allowance dated Jul. 30, 2018, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 5 pages. |
Notice of Allowance dated Jul. 30, 2019, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 9 pages. |
Notice of Allowance dated Mar. 30, 2020, issued in connection with U.S. Appl. No. 15/973,413, filed May 7, 2018, 5 pages. |
Notice of Allowance dated Nov. 30, 2018, issued in connection with U.S. Appl. No. 15/438,725, filed Feb. 21, 2017, 5 pages. |
Notice of Allowance dated Oct. 30, 2019, issued in connection with U.S. Appl. No. 16/131,392, filed Sep. 14, 2018, 9 pages. |
Notice of Allowance dated Oct. 30, 2020, issued in connection with U.S. Appl. No. 16/528,016, filed Jul. 31, 2019, 10 pages. |
Notice of Allowance dated May 31, 2019, issued in connection with U.S. Appl. No. 15/717,621, filed Sep. 27, 2017, 9 pages. |
Notice of Allowance dated Jun. 4, 2021, issued in connection with U.S. Appl. No. 16/528,265, filed Jul. 31, 2019, 17 pages. |
Notice of Allowance dated Mar. 4, 2020, issued in connection with U.S. Appl. No. 16/444,975, filed Jun. 18, 2019, 10 pages. |
Notice of Allowance dated Feb. 5, 2020, issued in connection with U.S. Appl. No. 16/178,122, filed Nov. 1, 2018, 9 pages. |
Notice of Allowance dated Oct. 5, 2018, issued in connection with U.S. Appl. No. 15/211,748, filed Jul. 15, 2018, 10 pages. |
Notice of Allowance dated Feb. 6, 2019, issued in connection with U.S. Appl. No. 16/102,153, filed Aug. 13, 2018, 9 pages. |
Notice of Allowance dated Feb. 6, 2020, issued in connection with U.S. Appl. No. 16/227,308, filed Dec. 20, 2018, 7 pages. |
Notice of Allowance dated Apr. 7, 2020, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 7 pages. |
Notice of Allowance dated Apr. 7, 2020, issued in connection with U.S. Appl. No. 16/147,710, filed Sep. 29, 2018, 15 pages. |
Notice of Allowance dated Jun. 7, 2019, issued in connection with U.S. Appl. No. 16/102,153, filed Aug. 13, 2018, 9 pages. |
Notice of Allowance dated Jun. 7, 2021, issued in connection with U.S. Appl. No. 16/528,224, filed Jul. 31, 2019, 9 pages. |
Notice of Allowance dated Nov. 8, 2021, issued in connection with U.S. Appl. No. 17/008,104, filed Aug. 31, 2020, 9 pages. |
Notice of Allowance dated Aug. 9, 2018, issued in connection with U.S. Appl. No. 15/229,868, filed Aug. 5, 2016, 11 pages. |
Notice of Allowance dated Dec. 9, 2021, issued in connection with U.S. Appl. No. 16/845,946, filed Apr. 10, 2020, 10 pages. |
Notice of Allowance dated Mar. 9, 2018, issued in connection with U.S. Appl. No. 15/584,782, filed May 2, 2017, 8 pages. |
Oord et al. WaveNet: A Generative Model for Raw Audio. Arxiv.org, Cornell University Library, Sep. 12, 2016, 15 pages. |
Optimizing Siri on HomePod in Far-Field Settings. Audio Software Engineering and Siri Speech Team, Machine Learning Journal vol. 1, Issue 12. https://machinelearning.apple.com/2018/12/03/optimizing-siri-on-homepod-in-far-field-settings.html. Dec. 2018, 18 pages. |
Palm, Inc., “Handbook for the Palm VII Handheld,” May 2000, 311 pages. |
Parada et al. Contextual Information Improves OOV Detection in Speech. Proceedings of the 2010 Annual Conference of the North American Chapter of the Association for Computational Linguistics, Jun. 2, 2010, 9 pages. |
Pre-Appeal Brief Decision mailed on Jun. 2, 2021, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 2 pages. |
Preinterview First Office Action dated Aug. 5, 2019, issued in connection with U.S. Appl. No. 16/434,426, filed Jun. 7, 2019, 4 pages. |
Preinterview First Office Action dated Mar. 25, 2020, issued in connection with U.S. Appl. No. 16/109,375, filed Aug. 22, 2018, 6 pages. |
Preinterview First Office Action dated Sep. 30, 2019, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 4 pages. |
Preinterview First Office Action dated May 7, 2020, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 5 pages. |
Preinterview First Office Action dated Jan. 8, 2021, issued in connection with U.S. Appl. No. 16/798,967, filed Feb. 24, 2020, 4 pages. |
Presentations at WinHEC 2000, May 2000, 138 pages. |
Renato De Mori. Spoken Language Understanding: A Survey. Automatic Speech Recognition & Understanding, 2007. IEEE, Dec. 1, 2007, 56 pages. |
Restriction Requirement dated Aug. 14, 2019, issued in connection with U.S. Appl. No. 16/214,711, filed Dec. 10, 2018, 5 pages. |
Restriction Requirement dated Aug. 9, 2018, issued in connection with U.S. Appl. No. 15/717,621, filed Sep. 27, 2017, 8 pages. |
Rottondi et al., “An Overview on Networked Music Performance Technologies,” IEEE Access, vol. 4, pp. 8823-8843, 2016, DOI: 10.1109/ACCESS.2016.2628440, 21 pages. |
Rybakov et al. Streaming keyword spotting on mobile devices, arXiv:2005.06720v2, Jul. 29, 2020, 5 pages. |
Shan et al. Attention-based End-to-End Models for Small-Footprint Keyword Spotting, arXiv:1803.10916v1, Mar. 29, 2018, 5 pages. |
Snips: How to Snips—Assistant creation & Installation, Jun. 26, 2017, 6 pages. |
Souden et al. “An Integrated Solution for Online Multichannel Noise Tracking and Reduction.” IEEE Transactions on Audio, Speech, and Language Processing, vol. 19. No. 7, Sep. 7, 2011, 11 pages. |
Souden et al. “Gaussian Model-Based Multichannel Speech Presence Probability” IEEE Transactions on Audio, Speech, and Language Processing, vol. 18, No. 5, Jul. 5, 2010, 6pages. |
Souden et al. “On Optimal Frequency-Domain Multichannel Linear Filtering for Noise Reduction.” IEEE Transactions an Audio, Speech, and Language Processing, vol. 18, No. 2, Feb. 2010, 17pages. |
Speidel, Hans. Chatbot Training: How to use training data to provide fully automated customer support. Retrieved from the Internet: URL: https://www.crowdguru.de/wp-content/uploads/Case-Study-Chatbox-training-How-to-use-training-iata-to-provide-fully-automated-customer-support.pdf. Jun. 29, 2017, 4 pages. |
Stemmer et al. Speech Recognition and Understanding on Hardware-Accelerated DSP. Proceedings of Interspeech 2017: Show & Tell Contribution, Aug. 20, 2017, 2 pages. |
Advisory Action dated Jun. 10, 2020, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 4 pages. |
Advisory Action dated Aug. 13, 2021, issued in connection with U.S. Appl. No. 16/271,550, filed Feb. 8, 2019, 4 pages. |
Advisory Action dated Apr. 23, 2021, issued in connection with U.S. Appl. No. 16/219,702, filed Dec. 13, 2018, 3 pages. |
Advisory Action dated Apr. 24, 2020, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 4 pages. |
Advisory Action dated Jun. 28, 2018, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 3 pages. |
Advisory Action dated Dec. 31, 2018, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 4 pages. |
Advisory Action dated Sep. 8, 2021, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 4 pages. |
Advisory Action dated Jun. 9, 2020, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 3 pages. |
Andra et al. Contextual Keyword Spotting in Lecture Video With Deep Convolutional Neural Network. 2017 International Conference on Advanced Computer Science and Information Systems, IEEE, Oct. 28, 2017, 6 pages. |
Anonymous,. S Voice or Google Now—The Lowdown. Apr. 28, 2015, 9 pages. [online], [retrieved on Nov. 29, 2017]. Retrieved from the Internet (URL:http://web.archive.org/web/20160807040123/http://lowdown.carphonewarehouse.com/news/s-voice-or-google-now/29958/). |
Anonymous: “What are the function of 4 Microphones on iPhone 6S/6S+?”, ETrade Supply, Dec. 24, 2015, XP055646381, Retrieved from the Internet: URL:https://www.etradesupply.com/blog/4-microphones-iphone-6s6s-for/ [retrieved on Nov. 26, 2019]. |
Audhkhasi Kartik et al. End-to-end ASR-free keyword search from speech. 2017 IEEE International Conference on Acoustics, Speech and Signal Processing, Mar. 5, 2017, 7 pages. |
AudioTron Quick Start Guide, Version 1.0, Mar. 2001, 24 pages. |
AudioTron Reference Manual, Version 3.0, May 2002, 70 pages. |
AudioTron Setup Guide, Version 3.0, May 2002, 38 pages. |
Australian Patent Office, Australian Examination Report Action dated Apr. 14, 2020, issued in connection with Australian Application No. 2019202257, 3 pages. |
Australian Patent Office, Australian Examination Report Action dated Oct. 3, 2019, issued in connection with Australian Application No. 2018230932, 3 pages. |
Australian Patent Office, Australian Examination Report Action dated Apr. 7, 2021, issued in connection with Australian Application No. 2019333058, 2 pages. |
Australian Patent Office, Australian Examination Report Action dated Aug. 7, 2020, issued in connection with Australian Application No. 2019236722, 4 pages. |
Australian Patent Office, Examination Report dated Jun. 28, 2021, issued in connection with Australian Patent Application No. 2019395022, 2 pages. |
Australian Patent Office, Examination Report dated Oct. 30, 2018, issued in connection with Australian Application No. 2017222436, 3 pages. |
“Automatic Parameter Tying in Neural Networks” ICLR 2018, 14 pages. |
Bertrand et al. “Adaptive Distributed Noise Reduction for Speech Enhancement in Wireless Acoustic Sensor Networks” Jan. 2010, 4 pages. |
Bluetooth. “Specification of the Bluetooth System: The ad hoc SCATTERNET for affordable and highly functional wireless connectivity,” Core, Version 1.0 A, Jul. 26, 1999, 1068 pages. |
Bluetooth. “Specification of the Bluetooth System: Wireless connections made easy,” Core, Version 1.0 B, Dec. 1, 1999, 1076 pages. |
Canadian Patent Office, Canadian Examination Report dated Dec. 1, 2021, issued in connection with Canadian Application No. 3096442, 4 pages. |
Canadian Patent Office, Canadian Examination Report dated Nov. 2, 2021, issued in connection with Canadian Application No. 3067776, 4 pages. |
Canadian Patent Office, Canadian Examination Report dated Oct. 26, 2021, issued in connection with Canadian Application No. 3072492, 3 pages. |
Canadian Patent Office, Canadian Examination Report dated Mar. 9, 2021, issued in connection with Canadian Application No. 3067776, 5 pages. |
Canadian Patent Office, Canadian Office Action dated Nov. 14, 2018, issued in connection with Canadian Application No. 3015491, 3 pages. |
Chinese Patent Office, Chinese Office Action and Translation dated Jul. 2, 2021, issued in connection with Chinese Application No. 201880077216.4, 22 pages. |
Chinese Patent Office, Chinese Office Action and Translation dated Mar. 30, 2021, issued in connection with Chinese Application No. 202010302650.7, 15 pages. |
Chinese Patent Office, First Office Action and Translation dated Dec. 1, 2021, issued in connection with Chinese Application No. 201780077204.7, 11 pages. |
Chinese Patent Office, First Office Action and Translation dated Mar. 20, 2019, issued in connection with Chinese Application No. 201780025028.2, 18 pages. |
Chinese Patent Office, First Office Action and Translation dated Mar. 27, 2019, issued in connection with Chinese Application No. 201780025029.7, 9 pages. |
Chinese Patent Office, First Office Action and Translation dated May 27, 2021, issued in connection with Chinese Application No. 201880026360.5, 15 pages. |
Chinese Patent Office, First Office Action and Translation dated Dec. 28, 2020, issued in connection with Chinese Application No. 201880072203.8, 11 pages. |
Chinese Patent Office, First Office Action and Translation dated Nov. 5, 2019, issued in connection with Chinese Application No. 201780072651.3, 19 pages. |
Chinese Patent Office, First Office Action dated Feb. 28, 2020, issued in connection with Chinese Application No. 201780061543.6, 29 pages. |
Chinese Patent Office, Second Office Action and Translation dated May 11, 2020, issued in connection with Chinese Application No. 201780061543.6, 17 pages. |
Chinese Patent Office, Second Office Action and Translation dated Jul. 18, 2019, issued in connection with Chinese Application No. 201780025029.7, 14 pages. |
Chinese Patent Office, Second Office Action and Translation dated Sep. 23, 2019, issued in connection with Chinese Application No. 201780025028.2, 15 pages. |
Chinese Patent Office, Second Office Action and Translation dated Mar. 31, 2020, issued in connection with Chinese Application No. 201780072651.3, 17 pages. |
Chinese Patent Office, Third Office Action and Translation dated Sep. 16, 2019, issued in connection with Chinese Application No. 201780025029.7, 14 pages. |
Chinese Patent Office, Third Office Action and Translation dated Aug. 5, 2020, issued in connection with Chinese Application No. 201780072651.3, 10 pages. |
Chinese Patent Office, Translation of Office Action dated Jul. 18, 2019, issued in connection with Chinese Application No. 201780025029.7, 8 pages. |
Chung et al. Empirical Evaluation of Gated Recurrent Neural Network on Sequence Modeling. Dec. 11, 2014, 9 pages. |
Cipriani,. The complete list of OK, Google commands—CNET. Jul. 1, 2016, 5 pages. [online], [retrieved on Jan. 15, 2020]. Retrieved from the Internet: (URL:https://web.archive.org/web/20160803230926/https://www.cnet.com/how-to/complete-list-of-ok-google-commands/). |
Corrected Notice of Allowability dated Mar. 8, 2017, issued in connection with U.S. Appl. No. 15/229,855, filed Aug. 5, 2016, 6 pages. |
Couke et al. Efficient Keyword Spotting using Dilated Convolutions and Gating, arXiv:1811.07684v2, Feb. 18, 2019, 5 pages. |
Number | Date | Country | |
---|---|---|---|
20220066734 A1 | Mar 2022 | US |
Number | Date | Country | |
---|---|---|---|
62706560 | Aug 2020 | US |