Patent Description:
Document <CIT> discloses a throwable microphone unit for facilitated transfer from user to user, comprising a wireless audio transmitting device adapted for use in a lecture hall, classroom, or auditorium with compatible audio speaker systems, to amplify what the user is saying. The throwable microphone unit is comprising: an outer enclosure having an interior for substantially surrounding and operably protecting the wireless audio transmitting device therewithin from being operationally affected by physical impact from throwing; controls operably associated with transmitting device for allowing users to interact with the transmitting device further comprising: a wireless controller operably associated with said unit for someone other than the user to selectively remotely activate and deactivate said transmitting device. The throwable microphone unit further comprises: an audio recorder for recording of the comments of the user; an RF mute button operably associated with the transmitting device: voice activated transmission of the transmission device; an RFID security tag; a laser pointer; rechargeable batteries; and surface mounted display and controls.

Document <CIT> discloses a mobile device comprising: a first application module configured to receive a first input command from a user; a second application module configured to receive a second input command from the user; and an assistant interface configured to translate the first input command into a first semantic atom and to transmit the first semantic atom to an external server to perform functions at a first external service; the assistant interface further configured to translate the second input command into a second semantic atom and to transmit the second semantic atom to the external server to perform functions at a second external service.

Embodiments of the invention include a smart microphone system according to claim <NUM>.

In some embodiments, the control wireless transmitter communicates a button state signal when the button is switched between the virtual assistant state and the audio output state.

In some embodiments, when the button is in the virtual assistant enable state, the virtual assistant transcribes the audio signal into a string of text. In some embodiments, the virtual assistant transmits the string of text to a virtual assistant server. In some embodiments, the virtual assistant executes a command based on the string of text.

In some embodiments, when the button is in the virtual assistant enable state, the virtual assistant executes a command based on the audio signal.

In some embodiments, when the button is in the audio output state or not in the virtual assistant enable state, the virtual assistant does not receive the audio signal from the wireless receiver. A method is disclosed according to claim <NUM>.

In some embodiments, the method may include executing a command based on the audio signal.

In some embodiments, the method may include communicating the audio signal to the virtual assistant server via the Internet; and outputting a response from the virtual assistant server.

In some embodiments, the method may include in the event the control signal indicates that the control microphone is in the audio output state, not communicating the audio signal to the virtual assistant.

In some embodiments, communicating the audio signal to a virtual assistant further comprises transcribing the audio signal into a string of text, and communicating the string of text to the virtual assistant.

These illustrative embodiments are mentioned not to limit or define the disclosure, but to provide examples to aid understanding thereof. Additional embodiments are discussed in the Detailed Description, and further description is provided there. Advantages offered by one or more of the various embodiments may be further understood by examining this specification or by practicing one or more embodiments presented.

These and other features, aspects, and advantages of the present disclosure are better understood when the following Disclosure is read with reference to the accompanying drawings.

Systems and methods are disclosed for using a smart microphone system that includes a throwable microphone, a virtual assistant, and a control microphone. In some embodiments, the control microphone can be used to mute or unmute the throwable microphone. In some embodiments, the control microphone can be used to send voice commands to the virtual assistant.

<FIG> is a block diagram of a smart microphone system <NUM> according to some embodiments. The smart microphone system <NUM> includes a smart microphone receiver <NUM>. The smart microphone receiver <NUM> may include a processor <NUM>, a virtual assistant processor <NUM>, a network interface <NUM>, a wireless microphone interface <NUM>, etc..

The processor <NUM> may include one or more components of the computational system <NUM> shown in in FIG. The processor <NUM> may control the operation of the various components of the smart microphone receiver <NUM>.

The virtual assistant processor <NUM> may include one or more components of the computational system <NUM> shown in in FIG. In some embodiments, the virtual assistant processor <NUM> may be a separate processor from processor <NUM> or it may be part of processor <NUM>. The virtual assistant processor <NUM>, for example, may be capable of voice interaction from voice commands received from either the control microphone subsystem <NUM> and/or the throwable microphone subsystem <NUM>; music playback; video playback; internet searches; information retrieval; making to-do lists; setting alarms; streaming podcasts; playing audiobooks; providing weather, traffic, sports, news, and other real-time information; etc., etc. To provide these services, for example, the virtual assistant processor <NUM>, may access the Internet <NUM> via the network interface <NUM>.

In some embodiments, the virtual assistant processor <NUM> may send audio to a virtual assistant server (e.g., Amazon Voice Service, Siri Service, Google Assistant Service, etc.) on the Internet <NUM> (e.g., in the cloud). In response, the virtual assistant server may respond with information, questions, data, streaming of data, music, videos, images, etc. In some embodiments, the virtual assistant processor <NUM> may be an Alexa-enabled device, a Siri-enable device, a Google Assistant enabled device, etc..

In some embodiments, the virtual assistant processor <NUM> may include interfaces, processes, and/or protocols that correspond to client-functionality, like speech recognition, audio playback, and volume control. Each interface may, for example, include logically grouped messages such as, for example, directives and/or events. For example, directives are messages sent from the virtual assistant server instructing the virtual assistant processor <NUM> to perform a function. Events are messages sent from the virtual assistant processor <NUM> to the virtual assistant server notifying it that something has occurred.

In some embodiments, the virtual assistant processor <NUM> may include voice recognition software, speech synthesizer software, etc. In some embodiments, the virtual assistant processor <NUM> may send security data, encryption keys, validation data, identification data, etc. to the virtual assistant server.

In some embodiments, wireless microphone interface <NUM> may wirelessly communicate with either or both the control microphone subsystem <NUM> and/or the throwable microphone subsystem <NUM>. In some embodiments, the wireless microphone interface <NUM> may include a transmitter, a receiver, and/or a transceiver. In some embodiments, the wireless microphone interface <NUM> may include an antenna. In some embodiments, the wireless microphone interface <NUM> may include an analog radio transmitter. In some embodiments, the wireless microphone interface <NUM> may communicate digital or analog audio signals over the analog radio. In some embodiments, the wireless microphone interface <NUM> may wirelessly transmit radio signals to the receiver device. In some embodiments, the wireless microphone interface <NUM> may include a Bluetooth®, WLAN, Wi-Fi, WiMAX, Zigbee, or other wireless device to send radio signals to the receiver device. In some embodiments, the wireless microphone interface <NUM> may include one or more speakers or may be coupled with one or more speakers. In some embodiments, the network connection <NUM> may include any type of interface that can connect a computer to the Internet <NUM>. In some embodiments, the network connection <NUM> may include a wired or wireless router, one or more servers, and/or one or more gateways. In some embodiments, the network interface <NUM> may connect the smart microphone receiver <NUM> to the Internet <NUM> via the network connection <NUM> (e.g., via Wi-Fi or an ethernet connection). In some embodiments, the smart microphone receiver <NUM> may be communicatively coupled with the speaker <NUM> and/or the display <NUM>. The display, for example, may include any device that can display images such as a screen, projector, tablet, television, display, etc. In some embodiments, the smart microphone receiver <NUM> may play audio through the speaker <NUM> from the throwable microphone subsystem <NUM> and/or the control microphone subsystem <NUM>. In some embodiments, the smart microphone receiver <NUM> may play audio through the speaker <NUM> streamed from the Internet <NUM>. In some embodiments, the smart microphone receiver <NUM> may play video through display <NUM> streamed from the Internet <NUM> or stored at the smart microphone receiver <NUM>. In some embodiments, the speaker <NUM> and/or the display <NUM> may or may not be integrated with the smart microphone receiver <NUM>. In some embodiments, the speaker <NUM> may be internal speakers or external speakers.

In some embodiments, the throwable microphone subsystem <NUM> may include a wireless communication interface <NUM>, processor <NUM>, sensors <NUM>, and/or a microphone <NUM>.

In some embodiments, the wireless communication interface <NUM> may communicate with the smart microphone receiver <NUM> via the wireless microphone interface <NUM>. In some embodiments, the wireless communication interface <NUM> may include a transmitter, a receiver, and/or a transceiver. In some embodiments, the wireless communication interface <NUM> may include an antenna. In some embodiments, the wireless communication interface <NUM> may include an analog radio transmitter. In some embodiments, the wireless communication interface <NUM> may communicate digital or analog audio signals over the analog radio. In some embodiments, the wireless communication interface <NUM> may wirelessly transmit radio signals to the receiver device. In some embodiments, the wireless communication interface <NUM> may include a Bluetooth®, WLAN, Wi-Fi, WiMAX, Zigbee, or other wireless device to send radio signals to the receiver device. In some embodiments, the wireless communication interface <NUM> may include one or more speakers or may be coupled with one or more speakers.

In some embodiments, the processor <NUM> may include one or more components of the computational system <NUM> shown in in FIG. In some embodiments, the processor <NUM> may control the operation of the wireless communication interface <NUM>, sensors <NUM>, and/or a microphone <NUM>.

In some embodiments, the sensor <NUM> may include a motion sensor and/or an orientation sensor. In some embodiments, the sensor may include any sensor capable of determining position or orientation, such as, for example, a gyroscope. In some embodiments, the sensor <NUM> may measure the orientation along any number of axes, such as, for example, three (<NUM>) axes. In some embodiments, a motion sensor and an orientation sensor may be combined in a single unit or may be disposed on the same silicon die. In some embodiments, the motion sensor and the orientation sensor may be combined a single sensor device.

In some embodiments, a motion sensor may be configured to detect a position or velocity of the throwable microphone subsystem <NUM> and/or provide a motion sensor signal responsive to the position. For example, in response to the throwable microphone subsystem <NUM> facing upward, the sensor <NUM> may provide a sensor signal to the processor <NUM>. The processor <NUM> may determine that the throwable microphone subsystem <NUM> is facing upward based on the sensor signal. As another example, in response to the throwable microphone subsystem <NUM> facing downward, the sensor <NUM> may provide a different sensor signal to the processor <NUM>. The processor <NUM> may determine that the throwable microphone subsystem <NUM> is facing downward based on the sensor signal.

In some embodiments, signals from the sensor <NUM> may be used by the processor <NUM> and/or the processor <NUM> to mute and/or unmute the microphone.

In some embodiments, the microphone <NUM> may be configured to receive sound waves and produce corresponding electrical audio signals. The electrical audio signals may be sent to either or both the processor <NUM> and/or the wireless communication interface <NUM>.

In some embodiments, a control microphone subsystem <NUM> may include a wireless communication interface <NUM>, processor <NUM>, throwable microphone mute button <NUM>, a virtual assistant enable button <NUM>, and/or a control microphone <NUM>. In some embodiments, the control microphone subsystem <NUM> may include one or more lights (or LEDs) that may be used to indicate when either or both the smart microphone system <NUM> is in the mute (or unmute) state or is in the virtual assistant enable state.

In some embodiments, the processor <NUM> may include one or more components of the computational system <NUM> shown in in FIG. In some embodiments, the processor <NUM> may control the operation of the wireless communication interface <NUM>, the throwable microphone mute button <NUM> , the virtual assistant enable button <NUM>, and/or the control microphone <NUM>.

In some embodiments, the throwable microphone mute button <NUM> may include a button disposed on the body of the control microphone subsystem <NUM>. The button may be electrically coupled with the processor <NUM> such that a signal is sent to the processor <NUM> when the throwable microphone mute button <NUM> is pressed or engaged. In response, the processor <NUM> may send a signal to the smart microphone receiver <NUM> indicating that the throwable microphone mute button <NUM> has been pressed or engaged. In response, the smart microphone receiver <NUM> may mute or unmute any sound received from the throwable microphone subsystem <NUM>.

In some embodiments, the virtual assistant enable button <NUM> may include a button disposed on the body of the control microphone subsystem <NUM>. The button may be electrically coupled with the processor <NUM> such that a signal is sent to the processor <NUM> when the virtual assistant enable button <NUM> is pressed or engaged. In response, the processor <NUM> may send a signal to the smart microphone receiver <NUM> indicating that the virtual assistant enable button <NUM> has been pressed or engaged. In response, the smart microphone receiver <NUM> may direct audio from either the control microphone subsystem <NUM> and/or the throwable microphone subsystem <NUM> to the virtual assistant processor <NUM>.

In some embodiments, the control microphone <NUM> may be configured to receive sound waves and produce corresponding electrical audio signals. The electrical audio signals may be sent to either or both the processor <NUM> and/or the wireless communication interface <NUM>.

<FIG> is a flowchart of a process <NUM> for muting a throwable microphone according to some embodiments. In some embodiments, the control microphone subsystem <NUM> may include a throwable microphone mute button <NUM>. The throwable microphone mute button <NUM>, for example, may be engaged to mute or unmute the microphone on the throwable microphone subsystem <NUM>. Thus, a button on one microphone device (e.g., the control microphone subsystem <NUM>) can be used to mute and unmute another microphone device (e.g., throwable microphone subsystem <NUM>).

At block <NUM> a mute button indication can be received. For example, the processor <NUM> of the control microphone subsystem <NUM> can receive an electrical indication from the throwable microphone mute button <NUM> indicating that the throwable microphone mute button <NUM> has been pressed. Alternatively or additionally, if the throwable microphone mute button <NUM> is a switch, the processor <NUM> can receive an electrical indication that a switch has been moved from a first state to a second state. In some embodiments, the control microphone subsystem <NUM> can send a signal to the smart microphone receiver <NUM> indicating that the mute state has been changed.

At block <NUM>, if the smart microphone system <NUM> is in the mute state, then process <NUM> proceeds to block <NUM>. If the smart microphone system <NUM> is in the unmute state, then process <NUM> proceeds to block <NUM>.

At block <NUM>, the smart microphone system <NUM> is changed to the mute state. In some embodiments, the change to the mute state may be a change made within a memory location at the smart microphone system <NUM>. In some embodiments, the change to the mute state may be a change made in a software algorithm or program. In some embodiments, a light (e.g., and LED) on the control microphone subsystem <NUM>, the throwable microphone subsystem <NUM>, and/or the smart microphone receiver <NUM> may be illuminated or unilluminated to indicate that the smart microphone system <NUM> is in the mute state.

At block <NUM>, the smart microphone system <NUM> is changed to the unmute state. In some embodiments, the change to the unmute state may be a change made within a memory location at the smart microphone system <NUM>. In some embodiments, the change to the unmute state may be a change made in a software algorithm or program. In some embodiments, a light (e.g., and LED) on the control microphone subsystem <NUM>, the throwable microphone subsystem <NUM>, and/or the smart microphone receiver <NUM> may be illuminated or unilluminated to indicate that the smart microphone system <NUM> is in the unmute state.

<FIG> is a flowchart of a process <NUM> for muting a throwable microphone according to some embodiments. At block <NUM> audio can be received at the smart microphone receiver <NUM> from either the throwable microphone subsystem <NUM> or the control microphone subsystem <NUM>.

At block <NUM>, it can be determined whether the control microphone state has been enabled. For example, the smart microphone receiver <NUM> can determine that the control microphone state has or has not been enabled based on the state of a switch (e.g., mute button <NUM>) at the control microphone subsystem <NUM>. The control microphone subsystem <NUM> may, for example, communicate the state of the switch to the smart microphone receiver <NUM> periodically or when the state of the switch has been changed. The control microphone subsystem <NUM>, for example, may store the state of the switch in memory.

if the smart microphone receiver <NUM> is in the control microphone enabled state, the process <NUM> proceeds to block <NUM>. If the smart microphone receiver <NUM> is not in the control microphone enable state (e.g., the throwable microphone enable state), the process <NUM> proceeds to block <NUM>.

At block <NUM>, in some embodiments, in the control microphone enable state, the microphone <NUM> in the throwable microphone subsystem <NUM> may be turned off. In some embodiments, in the control microphone enable state, the control microphone <NUM> in the control microphone subsystem <NUM> may be turned on.

At block <NUM>, in some embodiments, in the control microphone enable state, the wireless communication interface <NUM> in the throwable microphone subsystem <NUM> may not send audio signals to the smart microphone receiver <NUM>. In some embodiments, in the control microphone enable state, the wireless communication interface <NUM> may send audio signals to the smart microphone receiver.

At block <NUM>, in some embodiments, in the control microphone enable state, the processor <NUM> in the throwable microphone subsystem <NUM> may receive audio from the microphone <NUM> but may not send the audio to the smart microphone receiver <NUM>. In some embodiments, in the control microphone enable state, the processor <NUM> in the control microphone subsystem <NUM> may receive audio from the control microphone <NUM> and may send the audio to the smart microphone receiver <NUM>.

At block <NUM>, in some embodiments, in the control microphone enable state, the smart microphone receiver <NUM> may receive audio signals from the throwable microphone subsystem <NUM> via the wireless microphone interface <NUM> but may not output audio from the microphone <NUM> to the speaker <NUM>. In some embodiments, in the control microphone enable state, the smart microphone receiver <NUM> may receive audio signals from the control microphone subsystem <NUM> via the wireless microphone interface <NUM> and may output audio from the control microphone <NUM> to the speaker <NUM>.

At block <NUM>, in some embodiments, in the throwable control enable state, audio from the microphone <NUM> in the throwable microphone subsystem <NUM> may not be output via speaker <NUM>. In some embodiments, in the control microphone enable state, audio from the control microphone <NUM> in the control microphone subsystem <NUM> may be output via speaker <NUM>.

At block <NUM>, in some embodiments, in the throwable microphone enable state (e.g., when the control microphone enable state is disabled), the microphone <NUM> in the throwable microphone subsystem <NUM> may be turned on. In some embodiments, in the throwable microphone enable state, the control microphone <NUM> in the control microphone subsystem <NUM> may be turned off.

At block <NUM>, in some embodiments, in the throwable microphone enable state, the wireless communication interface <NUM> in the throwable microphone subsystem <NUM> may send audio signals to the smart microphone receiver <NUM>. In some embodiments, in the throwable microphone enable state, the wireless communication interface <NUM> may not send audio signals to the smart microphone receiver.

At block <NUM>, in some embodiments, in the throwable microphone enable state, the processor <NUM> in the throwable microphone subsystem <NUM> may receive audio from the microphone <NUM> and may send the audio to the smart microphone receiver <NUM>. In some embodiments, in the throwable microphone enable state, the processor <NUM> in the control microphone subsystem <NUM> may receive audio from the control microphone <NUM> and may not send the audio to the smart microphone receiver <NUM>.

At block <NUM>, in some embodiments, in the throwable microphone enable state, the smart microphone receiver <NUM> may receive audio signals from the throwable microphone subsystem <NUM> via the wireless microphone interface <NUM> and may output audio from the microphone <NUM> to the speaker <NUM>. In some embodiments, in the throwable microphone enable state, the smart microphone receiver <NUM> may receive audio signals from the control microphone subsystem <NUM> via the wireless microphone interface <NUM> and may not output audio from the control microphone <NUM> to the speaker <NUM>.

At block <NUM>, in some embodiments, in the throwable microphone enable state, audio from the microphone <NUM> in the throwable microphone subsystem <NUM> may be output via speaker <NUM>. In some embodiments, in the throwable microphone enable state, audio from the control microphone <NUM> in the control microphone subsystem <NUM> may not be output via speaker <NUM>.

Various other techniques may be used for controlling the output of or muting the audio from either or both the control microphone subsystem <NUM> or the throwable microphone subsystem <NUM> such as, for example, as described in <CIT>.

<FIG> is a flowchart of a process <NUM> for communicating with a virtual assistant using a throwable microphone system according to some embodiments. At block <NUM> audio can be received from either the throwable microphone subsystem <NUM> or the control microphone subsystem <NUM> at the smart microphone receiver <NUM>. At block <NUM> it can be determined whether the smart microphone system <NUM> is in the virtual assistant enable state. This can be determined, for example based on a user interaction with the virtual assistant enable button <NUM>. In some embodiments, a light may be illuminated or unilluminated on the smart microphone receiver <NUM> or the control microphone subsystem <NUM> indicating whether the smart microphone receiver <NUM> is in the virtual assistant enable state or not in the virtual assistant enable state.

If the smart microphone receiver <NUM> is in the virtual assistant enable state, then process <NUM> proceeds to <NUM>. At block <NUM> audio received at the throwable microphone subsystem <NUM> or the control microphone subsystem <NUM> is sent to the virtual assistant. For example, the audio may be sent to the virtual assistant processor <NUM>. In some embodiments, the audio may be sent to a virtual assistant server via the Internet <NUM>. In some embodiments, at block <NUM>, the audio may or may not be output via the speaker <NUM>. In some embodiments, a light (e.g., an LED) on the control microphone subsystem <NUM>, the throwable microphone subsystem <NUM>, and/or the smart microphone receiver <NUM> may be illuminated or unilluminated to indicate that the smart microphone system <NUM> is in the virtual assistant enable state.

If the smart microphone receiver <NUM> is not in the virtual assistant enable state, then process <NUM> proceeds to <NUM>. At block <NUM> audio received at the throwable microphone subsystem <NUM> or the control microphone subsystem <NUM> is not sent to the virtual assistant and may be output to speaker <NUM>. In some embodiments, the output to the speaker <NUM> may depend on the audio level selected and/or set by the user and/or whether the speaker <NUM> is turned on. In some embodiments, a light (e.g., and LED) on the control microphone subsystem <NUM>, the throwable microphone subsystem <NUM>, and/or the smart microphone receiver <NUM> may be illuminated or unilluminated to indicate that the smart microphone system <NUM> is not in the virtual assistant enable state.

In some embodiments, audio output to speaker <NUM> (or generally output) can be output to a USB port, a display, a computer, a screen, a video conference, the Internet, etc..

The computational system <NUM>, shown in <FIG> can be used to perform any of the embodiments of the invention. For example, computational system <NUM> can be used to execute processes <NUM>, <NUM>, and/or <NUM>. As another example, computational system <NUM> can be used perform any calculation, identification and/or determination described here. The computational system <NUM> includes hardware elements that can be electrically coupled via a bus <NUM> (or may otherwise be in communication, as appropriate). The hardware elements can include one or more processors <NUM>, including without limitation one or more general-purpose processors and/or one or more special-purpose processors (such as digital signal processing chips, graphics acceleration chips, and/or the like); one or more input devices <NUM>, which can include without limitation a mouse, a keyboard and/or the like; and one or more output devices <NUM>, which can include without limitation a display device, a printer and/or the like.

The computational system <NUM> may further include (and/or be in communication with) one or more storage devices <NUM>, which can include, without limitation, local and/or network accessible storage and/or can include, without limitation, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a random access memory ("RAM") and/or a read-only memory ("ROM"), which can be programmable, flash-updateable and/or the like. The computational system <NUM> might also include a communications subsystem <NUM>, which can include without limitation a modem, a network card (wireless or wired), an infrared communication device, a wireless communication device and/or chipset (such as a Bluetooth device, an <NUM> device, a Wi-Fi device, a WiMax device, cellular communication facilities, etc.), and/or the like. The communications subsystem <NUM> may permit data to be exchanged with a network (such as the network described below, to name one example), and/or any other devices described herein. In many embodiments, the computational system <NUM> will further include a working memory <NUM>, which can include a RAM or ROM device, as described above.

The computational system <NUM> also can include software elements, shown as being currently located within the working memory <NUM>, including an operating system <NUM> and/or other code, such as one or more application programs <NUM>, which may include computer programs of the invention, and/or may be designed to implement methods of the invention and/or configure systems of the invention, as described herein. For example, one or more procedures described with respect to the method(s) discussed above might be implemented as code and/or instructions executable by a computer (and/or a processor within a computer). A set of these instructions and/or codes might be stored on a computer-readable storage medium, such as the storage device(s) <NUM> described above.

In some cases, the storage medium might be incorporated within the computational system <NUM> or in communication with the computational system <NUM>. In other embodiments, the storage medium might be separate from a computational system <NUM> (e.g., a removable medium, such as a compact disc, etc.), and/or provided in an installation package, such that the storage medium can be used to program a general-purpose computer with the instructions/code stored thereon. These instructions might take the form of executable code, which is executable by the computational system <NUM> and/or might take the form of source and/or installable code, which, upon compilation and/or installation on the computational system <NUM> (e.g., using any of a variety of generally available compilers, installation programs, compression/decompression utilities, etc.) then takes the form of executable code.

Claim 1:
A smart microphone system (<NUM>) comprising:
a control microphone subsystem (<NUM>) comprising:
a first microphone;
a first wireless transmitter adapted to receive first audio signal from the first microphone and that is configured to wirelessly communicate the first audio signal; and
a button (<NUM>) that is adapted to switch between a virtual assistant state and audio output state;
wherein the first wireless transmitter is adapted to communicate a state signal indicating either the virtual assistant state or the audio output state;
a throwable microphone subsystem (<NUM>) comprising:
a throwable microphone body;
a second microphone disposed within the throwable microphone body; and
a second wireless transmitter that is adapted to receive second audio signal from the second microphone and wirelessly communicate the second audio signal; and
a smart microphone receiver subsystem comprising:
a wireless receiver that is adapted to receive the first audio signal from the first wireless transmitter of the control microphone subsystem (<NUM>), is adapted to receive the second audio signal from the second wireless transmitter of the throwable microphone subsystem (<NUM>), and is adapted to receive the state signal from the first wireless transmitter of the control microphone subsystem (<NUM>);
an audio output that is adapted to output the second audio signal from the wireless receiver when the control microphone subsystem (<NUM>) is in the audio output state; and
a virtual assistant that is adapted to receive the second audio signal from the wireless receiver when the control microphone subsystem (<NUM>) is in the virtual assistant enable state.