Internet-of-things devices and related methods for performing in-call interactions

A miniaturized multiprotocol audio/voice internet-of-things device (MAVID) initiates a wireless call in response to a command received from a first user. The MAVID carries out the wireless call between the first user and a second user. The wireless call utilizes wireless protocols such as WiFi, Bluetooth, third generation mobile technology (3G), fourth generation mobile technology (4G), and Digital Enhanced Cordless Telecommunications (DECT). The MAVID performs an in-call interaction, such as connecting to and utilizing an internet-based application or controlling a consumer electronic device, in response to a voice command from either the first user or the second user, while carrying out the wireless call.

The present application is related to U.S. patent application Ser. No. 15/788,201 filed on Oct. 19, 2017, and presently titled “Multiprotocol Audio/Voice Internet-Of-Things Devices and Related System.” The disclosure in this related application is hereby incorporated fully by reference into the present application.

BACKGROUND

The internet-of-things (IoT) refers to the networking of physical objects embedded with electronic devices. As more objects are networked, new ways of interacting with them become available. IoT devices can collect, process, act on, and communicate data for such purposes as automation, user reporting, and remote control. IoT devices are rapidly being deployed in home, industrial, metropolitan, and environmental applications.

IoT devices communicate using numerous wireless protocols, including WiFi, Bluetooth, ZigBee, and more. Manufacturers of different IoT devices may use any one of these numerous wireless protocols. The existence of numerous wireless protocols hinders communicating with IoT devices having different wireless protocols, and is commonly referred to as the “basket of remotes” problem.

In addition, many IoT devices use voice control for ease of use. However, present IoT devices are typically not engaged to initiate and carry out live voice calls between remote users, including voice over Internet protocol (VoIP), cellular, and landline calls. Users often rely on other devices and software for initiating and carrying out voice calls. As a result, many ways of interacting with ToT devices based on live voice calls have not been explored.

SUMMARY

The present disclosure is directed to Internet-of-things (IoT) devices and related methods for performing in-call interactions, substantially as shown in and/or described in connection with at least one of the figures, and as set forth in the claims.

DETAILED DESCRIPTION

FIG. 1illustrates a system diagram of a portion of an exemplary multiprotocol audio/voice internet-of-things device (MAVID) according to one implementation of the present application. As illustrated inFIG. 1, MAVID110includes package112, antennas114a,114b,114c, and114d, diplexer116, RF switch118, dual-band wireless communication module120, having WiFi communication module122and Bluetooth communication module124, ZigBee communication module126, Digital Enhanced Cordless Telecommunications (DECT) communication module128, third generation and fourth generation mobile technology (3G/4G) communication module129, multipoint control unit (MCU)130, microphone132, voice digital signal processor (VDSP)134, quad serial peripheral interface (QSPI) flash memory136, and power supply138.

As shown inFIG. 1, diplexer116, RF switch118, dual-band wireless communication module120, having WiFi communication module122and Bluetooth communication module124, ZigBee communication module126, DECT communication module128, MCU130, VDSP134, and power supply138are located inside package112. Package112may be a small form factor package having dimensions of approximately one inch by inch (1″×1″) or less. As also shown inFIG. 1, antennas114a,114b,114c, and114d,3G/4G communication module129, microphone132, and QSPI flash memory136are located outside package112. Antennas114a,114b,114c, and114d,3G/4G communication module129, microphone132, and QSPI flash memory136may be located, for example, on a printed circuit board (PCB) (not shown inFIG. 1). Package112may also be located on the PCB.

Antennas114a,114b,114c, and114dlocated outside package112are used to receive or transmit RF signals according to various wireless protocols. For example, antennas114a,114b,114c, and114dare used to receive or transmit RF signals according to the WiFi, Bluetooth, ZigBee, and DECT protocols respectively. The WiFi protocol includes the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards. For example the WiFi protocol may be IEEE 802.11a, 802.11b, 802.11g, and/or 802.11n standards and use 2.4 GHz and/or 5 GHz frequency bands. The Bluetooth protocol includes versions of the Bluetooth specifications, such as Bluetooth Basic Rate, Bluetooth Enhanced Data Rate (EDR), and/or Bluetooth Low Energy (LE). The Bluetooth protocol may comply with IEEE 802.15.1 standards and use the 2.4 GHz frequency band. The ZigBee protocol includes versions of the ZigBee Alliance specifications, such as ZigBee 2006 and/or ZigBee PRO. The ZigBee protocol may comply with IEEE 802.15.4 standards and use 868 MHz, 915 MHz, and/or 2.4 GHz frequency bands. The DECT protocol includes versions of the DECT standards, such as DECT Common Interface (CI), DECT Cordless Advanced Technology—internet and quality (CAT-iq), and/or DECT Ultra Low Energy (ULE). The DECT protocol may comply with European Telecommunications Standards Institute (ETSI) EN 300 175, TS 102 527, and/or TS 102 939 standards and use the 1.9 GHz frequency band. Antennas114a,114b,114c, and114dmay be, for example, patch antennas or microstrip antennas or other types of antennas. In one implementation, antennas114a,114b,114c, and114dmay each be an antenna array having more than one element. In one implementation, a single antenna may be used for more than one wireless protocol. For example a single antenna may be used for both WiFi and Bluetooth protocols.

Antenna114ais coupled to diplexer116. Diplexer116differentiates RF signals in different frequency bands. For example, in the present implementation, diplexer116differentiates signals in the 2.4 GHz frequency band from signals in the 5 GHz frequency band. The 2.4 GHz signals are coupled to WiFi communication module122in dual band wireless communication module120. The 5 GHz signals are coupled to RF switch118, which switches the signals between transmit and receive lines, and are then coupled to WiFi communication module122in dual band wireless communication module120. Antennas124b,124c, and124dare coupled to Bluetooth communication module124, ZigBee communication module126, and DECT communication module128respectively.

WiFi communication module122, Bluetooth communication module124, ZigBee communication module126, and DECT communication module128process RF signals according to the standards of the WiFi protocol, the Bluetooth protocol, the ZigBee protocol, and the DECT protocol respectively. Because concurrent use of multiple wireless protocols generally results in interference and collisions, WiFi communication module122, Bluetooth communication module124, ZigBee communication module126, and DECT communication module128are also responsive to and controlled by control signals from MCU130. As shown inFIG. 1, WiFi communication module122, Bluetooth communication module124, ZigBee communication module126, and DECT communication module128are coupled to MCU130through hardware communication interfaces, such as secure digital input output (SDIO), universal asynchronous receiver/transmitter (UART), and pulse code modulation (PCM) interfaces. These interfaces are bidirectional, allowing the communication modules to report data to MCU130for additional processing, and allowing MCU130to send control signals to the communication modules.

For example, WiFi communication module122, Bluetooth communication module124, ZigBee communication module126, and DECT communication module128may report information regarding current and planned operational states, bit and packet error rates, signal and noise power levels, frequencies and channels, and timing. MCU130may perform interference assessments based on information reported by the communication modules, determine interference solutions based on the interference assessments, and send control signals to the communication modules based on the determined interference solutions. Thus, MCU acts as a packet traffic arbiter (PTA) to manage the coexistence of multiple wireless protocols, enabling MAVID110to concurrently form wireless RF communication links over those multiple wireless protocols.

InFIG. 1, 3G/4G communication module129is coupled to MCU130. MCU130interacts with 3G/4G communication module129in substantially the same manner as the other wireless communication modules described above. 3G/4G communication module129may be located outside package112for other considerations such as size, heat dissipation, and/or electrical isolation. Optionally, as shown inFIG. 1, dual-band wireless communication module120, ZigBee communication module126, and/or DECT communication module128are coupled through a PTA interface, to more efficiently compare data from one wireless communication module with data from another wireless communication module and reduce the processing burden of MCU130. In one implementation, MAVID110may form wireless RF communication links over other wireless protocols instead of, or in addition to, those shown inFIG. 1. For example, MAVID110may use Long Range (LoRa), Z-Wave, and any other wireless protocols.

As shown inFIG. 1, MAVID110includes microphone132. Microphone132is configured to receive voice from a user. In the present implementation, microphone132is a microphone array with three microphone elements. Microphone132may provide beamforming capability to improve reception of far-field voice and enable voice tracking. In various implementations, microphone132may be a single microphone element or a microphone array with more or fewer microphone elements than shown inFIG. 1. The number of microphone elements may depend on how critical sound is for MAVID110.

Microphone132is coupled to VDSP134. VDSP134is configured to receive and process voice signals from microphone132. VDSP134performs voice signal conditioning, such as noise filtration, voice cleanup, and gain control. VDSP134also performs voice recognition analysis. In one implementation, VDSP134employs a wake-up scheme wherein components of MAVID110are kept in a low-power operational state until the occurrence of a detectable event, such as VDSP134recognizing a user speaking “Jarvis” or another keyword.

As shown inFIG. 1, VDSP134is coupled to MCU130through hardware communication interfaces, such serial peripheral interface (SPI), inter-integrated circuit (I2C), general purpose input output (GPIO), and inter-IC sound (I2S) interfaces. These interfaces allow MCU130to provide feedback to VDSP134, and VDSP134to provide voice control signals to MCU130. MCU130is configured to enable wireless RF communication links over multiple wireless protocols in response to the voice control signals received from VDSP134. For example, while MAVID110is streaming audio to a speaker (not shown inFIG. 1) over the Bluetooth protocol, a user may speak the words “lights show.” VDSP134may provide a voice control signal to MCU130corresponding to voice recognition of the words “lights show.” MCU130may process both the voice control signal and information reported by Bluetooth communication module124, and then enable MAVID110to connect to lights (not shown inFIG. 1) over the ZigBee protocol while maintaining the connection to the speaker over the Bluetooth protocol. In other examples, MCU130enables MAVID110to communicate over multiple wireless protocols in response to voice control signals corresponding to voice recognition of different words.

As also shown inFIG. 1, MAVID110includes QSPI flash memory136coupled to MCU130. MCU130may process information stored in QSPI flash memory136, in addition to voice control signals and information reported by wireless communication modules. For example, QSPI flash memory136may store a previous multiprotocol connection's configuration, so that MCU130can access the configuration and reduce processing burden of MCU130upon a similar subsequent multiprotocol connection. Power supply138supplies power to components of MAVID110. MCU130may also process information from external hardware communication interfaces such as external inter-IC sound (I2S) (shown as “Aux In (I2S)” inFIG. 1), serial peripheral interface (SPI), inter-integrated circuit (I2C), general purpose input output (GPIO), pulse width modulation (PWM), universal asynchronous receiver transmitter (UART), secure digital/secure digital input output (SD/SDIO), and/or universal serial bus (USB) interfaces. One of the external hardware communication interfaces (shown as “Audio Out” inFIG. 1) enables MCU130to communicate with at least one speaker (not shown inFIG. 1). The speaker may be external to MAVID110or integrated with MAVID110.

MCU130can initiate a wireless call in response to a user command. In one example, a user command may be a voice command such as a voice command received from microphone132. In another example, a user command may be a non-voice command such as an input received from hardware communication interfaces after a user pushes a button on an input panel. After MCU130receives a user command, MCU130initiates a wireless call over wireless RF communication links as discussed above. For example, MCU130can initiate VoIP, landline, and cellular calls over the WiFi, DECT, and 3G/4G protocols respectively by connecting to a router, cordless phone dock, or base station respectively. Once initiated, MCU130can carry out the wireless call over the respective wireless protocol. For example, microphone132can receive voice signals and MCU130can transmit corresponding audio signals through antennas114a,114b,114c, and114d, and antennas114a,114b,114c, and114dcan receive audio signals and MCU130can transmit corresponding audio signals to a speaker through the “Audio Out” interface shown inFIG. 1. As used herein, the phrase “wireless call” refers to the wireless exchange of audio signals between MAVID110and the next link in the call chain; it is not necessary that the entire call chain be wireless.

While in-call, MCU130performs in-call interactions in response to voice control signals. Voice control signals can correspond to voice recognition of words or sounds from the MAVID end of the wireless call. For example, MCU130may receive voice control signals from VDSP134corresponding to voice recognition of words or sounds from a MAVID user received through microphone132during the wireless call. Voice control signals can also correspond to voice recognition of words or sounds at another end of the wireless call. For example, MCU130may receive voice control signals through any voice recognition over internet protocol (VRoIP) technique corresponding to voice recognition of words or sounds from other users during the wireless call. MCU130may process the voice control signals using various algorithms to perform an in-call interaction.

In one implementation, the in-call interaction may be recognition of keyword. For example, MCU130may check for a specific keyword among the voice control signals and register that it recognized the keyword. MCU130may perform another in-call interaction after registering keyword recognition such as, for example, waking up components of MAVID110from a low-power operational state. In one implementation, the in-call interaction may be execution of a request. For example, MCU130may delimit the start of a request using a keyword, delimit the end of a request based on time intervals, associate parts of the request with data stored in memory, and execute the request based on the associations. Executing a request may involve connecting to and utilizing an internet-based application, for example, over the WiFi protocol. In another implementation, executing a request may involve controlling a consumer electronic device. A consumer electronic device may be any IoT device integrated with a wireless protocol module, such as a television, a computer, a printer, a flash drive, an on-board diagnostics (OBD) dongle, a refrigerator, a coffee maker, a home security alarm, a security camera, a washer, a dryer, a thermostat, or a heating, ventilation, and air conditioning (HVAC) device. MCU130may execute a request utilizing WiFi, ZigBee, Bluetooth, 3G/4G, LoRa, Z-Wave, DECT, and any other wireless protocols as discussed above. In one implementation, the protocol utilized to execute a request may differ from the protocol utilized to initiate or carry out a wireless call. In one implementation, the protocol utilized to execute a request may differ from the protocol utilized to execute another request.

MAVID110is a wireless IoT device that enables two-way voice communication between users. The user does not need additional devices and software in order to carry out a voice call on his/her MAVID IoT device. Because MAVID110enables multiple wireless protocols, a user can talk to and receive audio from MAVID110as though it were a VoIP phone, a cordless phone, and a cellular phone. In addition, while in-call, MAVID110performs IoT interactions in response to voice commands. MAVID110can perform these in-call interactions where the voice commands originate from users on either end of the call, and where the voice commands involve requests to connect to applications or to control devices having various wireless protocols.

FIG. 2is a flowchart illustrating an exemplary method executed by a MAVID for performing an in-call interaction according to one implementation of the present application. Certain details and features have been left out of flowchart200that are apparent to a person of ordinary skill in the art. For example, a step may comprise one or more sub steps or may involve specialized equipment, as is known in the art. While steps240through252indicated in flowchart200are sufficient to describe one implementation disclosed herein, other implementations disclosed herein may use steps different from those shown in flowchart200.

As illustrated in flowchart200, step240includes initiating a wireless call to User2and User3in response to a command from User1. In the present example, User1speaks the voice command “Jarvis, call friends.” A MAVID, such as MAVID110inFIG. 1, initiates the wireless call to Users2and User3in response to the voice command. The MAVID may be programmed to associate voice control signals corresponding to the word “friends” with User2and User3prior to step240or concurrently with step240. In other examples, the MAVID may initiate the wireless call in response to a non-voice command. For example, User1may push a button on an input panel, and the MAVID may initiate the wireless call in response to the input.

As illustrated in flowchart200, step242includes carrying out the wireless call between User1, User2, and User3. In the present example, User1, User2, and User3each speak the greeting “Hello.” Next, User1asks User2and User3“Do you want to join me for dinner tomorrow at Restaurant X in City Y?” Next, User2asks “At what time?” The MAVID transmits audio signals corresponding to the words spoken by User1to User2and User3, and receives audio signals corresponding to the words spoken by User2and User3and transmits it to User1, for example, using a speaker. The MAVID may also relay audio signals between User2and User3. The MAVID may carry out the wireless call over various wireless protocols, such as over the WiFi, DECT, and 3G/4G protocols, as discussed above.

As illustrated in flowchart200, step244includes performing an in-call interaction in response to a voice command from User1, while carrying out the wireless call between User1, User2, and User3. In the present example, User1speaks the voice command “Jarvis, check availability for Restaurant X for tomorrow around 6:45 p.m.” Within the voice command, the word “Jarvis” represents a keyword that the MAVID can recognize and use to perform additional interaction as discussed above. Within the voice command, the words “check availability for Restaurant X for tomorrow around 6:45 p.m.” represent a request that the MAVID can recognize and execute. In the present example, while maintaining the call, the MAVID executes the request by connecting to and utilizing internet-based applications, such as internet-based restaurant reservation applications like OpenTable®. In the present example, the MAVID (referred to as “Jarvis” inFIG. 2) also provides feedback confirming that it successfully executed the request by outputting the words “The only available reservation for Restaurant X for tomorrow is 6:30 p.m.” In some implementations, the MAVID may provide feedback that it failed to recognize a request, or that it recognized but failed to execute a request.

As illustrated in flowchart200, step246includes canying out the wireless call between User1, User2, and User3. The MAVID continues carrying out the wireless call in a manner similar to that discussed above with reference to step242. In the present example, User2states “If it is raining, I may arrive late.” The MAVID receives audio signals corresponding to the words spoken by User2and transmits it to User1, for example, using a speaker. The MAVID may also relay audio signals between User2and User3.

As illustrated in flowchart200, step248includes performing an in-call interaction in response to a voice command from User2, while carrying out the wireless call between User1, User2, and User3. In step248, User2who speaks the voice command is a different user than User1who initiated the wireless call. User1and User2may be at opposite ends of the wireless call. The MAVID performs an in-call interaction in a manner similar to that discussed above with reference to step244. In the present example, User2speaks the voice command “Jarvis, check weather forecast for tomorrow in City Y.” Within the voice command, the word “Jarvis” represents a keyword that the MAVID can recognize and use to perform additional interaction as discussed above. Within the voice command, the words “check weather forecast for tomorrow in City Y” represent a request that the MAVID can recognize and execute. In the present example, while maintaining the call, the MAVID executes the request by connecting to and utilizing internet-based applications, such as internet-based weather forecast applications like National Weather Service®. In the present example, the MAVID (referred to as “Jarvis” inFIG. 2) also provides feedback confirming that it successfully executed the request by outputting the words “Tomorrow in City Y it will be sunny with a 5% chance of rain.”

As illustrated in flowchart200, step250includes carrying out the wireless call between User1, User2, and User3. The MAVID continues carrying out the wireless call in a manner similar to that discussed above with reference to steps242and246. In the present example, User3states “I cannot hear either of you because User1's TV is too loud.” The MAVID receives audio signals corresponding to the words spoken by User3and transmits it to User1, for example, using a speaker. The MAVID may also relay audio signals between User3and User2.

As illustrated in flowchart200, step252includes performing an in-call interaction in response to a voice command from User3, while carrying out the wireless call between User1, User2, and User3. In step252, User3who speaks the voice command is a different user than User1who initiated the wireless call. User1and User3may be at opposite ends of the wireless call. The MAVID performs an in-call interaction in a manner similar to that discussed above with reference to steps244and248. In the present example, User3speaks the voice command “Jarvis, turn User1's TV down.” Within the voice command, the “Jarvis” represents a keyword that the MAVID can recognize and use to perform additional interaction as discussed above. Within the voice command, the words “turn User1's TV down” represent a request that the MAVID can recognize and execute. In the present example, while maintaining the call, the MAVID executes the request by controlling a consumer electronic device, such as WiFi-enabled smart TV. In the present example, the MAVID does not provide feedback confirming that it successfully executed the request, and instead simply lowers the volume on User1's TV. The MAVID may be programmed to grant User3permissions to control User1's TV prior to step252or concurrently with step252.

Using a MAVID to execute the method illustrated in flowchart200enables a user to carry out a voice call on the MAVID without requiring additional devices and software. Moreover, while in-call, users on either end of the call can speak voice commands and the MAVID can respond by connecting to applications or controlling IoT devices having various wireless protocols. Thus the method illustrated in flowchart200introduces many ways of interacting with IoT devices based on live voice calls.

FIG. 3illustrates an exemplary diagram of a portion of a communication system according to one implementation of the present application. As illustrated inFIG. 3, communication system300includes MAVID310within speaker311, users360and362, router364, laptop computer366, consumer electronic device368, and internet application370.

In response to a command from user360, MAVID310initiates a wireless call. As shown inFIG. 3, the wireless call utilizes the WiFi protocol. In the present implementation, MAVID310is within speaker tower311having integrated therein MAVID310. MAVID310inFIG. 3may have any other implementations and advantages described above with respect to MAVID110inFIG. 1. MAVID310wirelessly connects to and communicates with router364over the WiFi protocol. Router364has an integrated WiFi module that enables use of the WiFi protocol. MAVID310instructs router364to connect to and communicate with laptop computer366of user362over a VoIP network. MAVID310then carries out the call.

Laptop computer366may have an integrated microphone and speaker that it uses in conjunction with VoIP software, such as Skype®. Laptop computer366receives voice signals from user362and transmits corresponding audio signals to MAVID310, where MAVID310outputs the audio signals to speaker311for user360to hear. Similarly, MAVID310receives voice signals from user360and transmits corresponding audio signals to laptop computer366, where laptop computer366outputs the audio signals for user362to hear. In one implementation, MAVID310may carry out a call between more than two users. In one implementation, MAVID310may carry out a call having a non-human user. In one implementation, communication system300may include multiple MAVIDs, any of which can initiate and carry out a call.

While carrying out the wireless call, MAVID310performs an in-call interaction in response to a voice command from either user360or362. As discussed above, the voice command may include a keyword that MAVID310can recognize and use to perform additional interaction, and a request that the MAVID310can recognize and execute. As shown inFIG. 3, MAVID310executes requests by controlling consumer electronic device368and utilizing internet application370. Consumer electronic device368may be any IoT device integrated with a wireless protocol module, such as a television, a lighting system, a telephone, a computer, a printer, a flash drive, an on-board diagnostics (OBD) dongle, a refrigerator, a coffee maker, a home security alarm, a security camera, a washer, a dryer, a thermostat, or a heating, ventilation, and air conditioning (HVAC) device. In the present implementation, MAVID310controls consumer electronic device368over the Bluetooth protocol. In other implementations, MAVID310may control consumer electronic device368over WiFi, ZigBee, 3G/4G, LoRa, Z-Wave, DECT, or any other wireless protocol. MAVID310utilizes internet application370by connecting to router364, and then connecting to internet application370over an internet protocol (IP) connection. MAVID310may provide feedback regarding execution of a request during the call, as discussed above. In one implementation, communication system300may include more than two users, and MAVID310may perform an in-call interaction in response to a voice command from any of the users.

FIG. 4illustrates an exemplary diagram of a portion of a communication system according to one implementation of the present application. As illustrated inFIG. 4, communication system400includes MAVID410within speaker tower411, users460and462, router464, consumer electronic device468, internet application470, and phone docks472and474.

In response to a command from user460, MAVID410initiates a wireless call. As shown inFIG. 4, the wireless call utilizes the DECT protocol. In the present implementation, MAVID410is within speaker411having integrated therein MAVID410. MAVID410inFIG. 4may have any other implementations and advantages described above with respect to MAVID110inFIG. 1. MAVID410wirelessly connects to and communicates with phone dock472over the DECT protocol. Phone dock472has an integrated DECT module that enables use of the DECT protocol. MAVID410instructs phone dock472to connect to and communicate with phone dock474of user462over a public switched telephone network (PSTN). MAVID410then carries out the call. Phone dock474may be used in conjunction with a handheld phone having an integrated microphone and speaker. Phone dock474receives voice signals from user462and transmits corresponding audio signals to MAVID410, where MAVID410outputs the audio signals for user460to hear. Similarly, MAVID410receives voice signals from user460and transmits corresponding audio signals to phone dock474, where phone dock474outputs the audio signals for user462to hear. In one implementation, MAVID410may carry out a call between more than two users. In one implementation, MAVID410may carry out a call having a non-human user. In one implementation, communication system400may include multiple MAVIDs, any of which can initiate and carry out a call.

While carrying out the wireless call, MAVID410performs an in-call interaction in response to a voice command from either user460or462. As discussed above, the voice command may include a keyword that MAVID410can recognize and use to perform additional interaction, and a request that the MAVID410can recognize and execute. As shown inFIG. 4, MAVID410executes requests by controlling consumer electronic device468and utilizing internet application470. Consumer electronic device468may be any IoT device integrated with a wireless protocol module, such as a television, a lighting system, a telephone, a computer, a printer, a flash drive, an on-board diagnostics (OBD) dongle, a refrigerator, a coffee maker, a home security alarm, a security camera, a washer, a dryer, a thermostat, or a heating, ventilation, and air conditioning (HVAC) device. In the present implementation, MAVID410controls consumer electronic device468over the Bluetooth protocol. In other implementations, MAVID410may control consumer electronic device468over WiFi, ZigBee, 3G/4G, LoRa, Z-Wave, DECT, or any other wireless protocol. MAVID410utilizes internet application470by connecting to router464, and then connecting to internet application470over an IP connection. MAVID410may provide feedback regarding execution of a request during the call, as discussed above. In one implementation, communication system400may include more than two users, and MAVID410may perform an in-call interaction in response to a voice command from any of the users.

FIG. 5illustrates an exemplary diagram of a portion of a communication system according to one implementation of the present application. As illustrated inFIG. 5, communication system500includes MAVID510within speaker tower511, users560and562, router564, consumer electronic device568, internet application570, base station576, mobile phone578, and optional mobile phone580.

In response to a command from user560, MAVID510initiates a wireless call. As shown inFIG. 5, the wireless call utilizes the 3G/4G protocols. In the present implementation, MAVID510is within speaker511having integrated therein MAVID510. MAVID510inFIG. 5may have any other implementations and advantages described above with respect to MAVID110inFIG. 1. MAVID510wirelessly connects to and communicates with base station576over the 3G/4G protocols. Optionally, MAVID510may connect to optional mobile phone580over the Bluetooth protocol and then connect to base station576over the 3G/4G protocols. In other words, MAVID510may use optional mobile phone580as a hotspot. Base station576enables use of the 3G/4G protocols. MAVID510instructs base station576to connect to and communicate with mobile phone578of user562over a 3G/4G network. MAVID510then carries out the call. Mobile phone578may have an integrated microphone and speaker. Mobile phone578receives voice signals from user562and transmits corresponding audio signals to MAVID510, where MAVID510outputs the audio signals for user560to hear. Similarly, MAVID510receives voice signals from user560and transmits corresponding audio signals to mobile phone578, where mobile phone578outputs the audio signals for user562to hear. In one implementation, MAVID510may carry out a call between more than two users. In one implementation, MAVID510may carry out a call having a non-human user. In one implementation, communication system500may include multiple MAVIDs, any of which can initiate and carry out a call.

While carrying out the wireless call, MAVID510performs an in-call interaction in response to a voice command from either user560or562. As discussed above, the voice command may include a keyword that MAVID510can recognize and use to perform additional interaction, and a request that the MAVID510can recognize and execute. As shown inFIG. 5, MAVID510executes requests by controlling consumer electronic device568and utilizing internet application570. Consumer electronic device568may be any IoT device integrated with a wireless protocol module, such as a television, a lighting system, a telephone, a computer, a printer, a flash drive, an on-board diagnostics (OBD) dongle, a refrigerator, a coffee maker, a home security alarm, a security camera, a washer, a dryer, a thermostat, or a heating, ventilation, and air conditioning (HVAC) device. In the present implementation, MAVID510controls consumer electronic device568over the Bluetooth protocol. In other implementations, MAVID510may control consumer electronic device568over WiFi, ZigBee, 3G/4G, LoRa, Z-Wave, DECT, or any other wireless protocol. MAVID510utilizes internet application570by connecting to router564, and then connecting to internet application570over an IP connection. MAVID510may provide feedback regarding execution of a request during the call, as discussed above. In one implementation, communication system500may include more than two users, and MAVID510may perform an in-call interaction in response to a voice command from any of the users.

FIG. 6illustrates an exemplary diagram of a portion of a communication system according to one implementation of the present application. As illustrated inFIG. 6, communication system600includes wearable MAVID610, users660and662, router664, laptop computer666, consumer electronic device668, and internet application670. InFIG. 6, communication system600includes a wearable MAVID610, rather than a speaker tower MAVID—as was the case with respect toFIG. 3. Because a MAVID forms RF communication links wirelessly and contains several essential components in a small form factor package, a MAVID can easily be formed as wearable MAVID610so that user660can conveniently reposition and bring the MAVID along with him. Wearable MAVID610may be any MAVID ergonomically designed to be worn by a user without creating a substantial obstruction. In the present implementation, wearable MAVID610is a necklace. In various implementations wearable MAVID610may be, for example, a button, a watch, eyeglasses, headphones, or an earpiece. Wearable MAVID610inFIG. 6may have any other implementations and advantages described above with respect to MAVID110inFIG. 1. Communication system600inFIG. 6may have any other implementations and advantages described above with respect to communication system300inFIG. 3.

FIG. 7illustrates a configurations chart of exemplary MAVIDs according to various implementations of the present application. The columns of configurations chart700show three different configurations, referred to as configurations A, B, and C. The rows of configurations chart700show five different MAVID features, including Voice Recognition, WiFi, Bluetooth LE, Bluetooth Audio, and ZigBee. In various implementations, more or fewer MAVID features may exist. In configurations chart700, MAVID features available for a given configuration are shown by an “X” mark in the corresponding row. Configuration A is shown to have all MAVID features available. Configuration A may correspond to a target application where a full-feature MAVID is desirable, such as an in-home application. For the purpose of an example only, configuration A corresponds to MAVID710a, where MAVID710ais within speaker tower711ahaving integrated therein MAVID710a. Configuration B is shown to have all MAVID features available except for the WiFi feature. The WiFi feature may not be supported, or may supported but temporarily turned off. Configuration B may correspond to a target application where user760is regularly out of range of WiFi devices. As another example, configuration B corresponds to MAVID710b, where MAVID710bis a wearable MAVID. Configuration C is shown to have all MAVID features available except for the Bluetooth Audio feature. The Bluetooth Audio feature may not be supported, or may supported but temporarily turned off. Configuration C may correspond to a target application where it is unnecessary for a MAVID to transmit audio over Bluetooth. As yet another example, configuration C corresponds to MAVID710c, where MAVID710cis within security camera711chaving integrated therein MAVID710e. MAVID features may be implemented in a modular fashion to facilitate configuring a MAVID for a given target application. An optimized configuration may reduce the manufacturing cost and/or power consumption of the MAVID.

Thus, various implementations of the present application perform voice controlled IoT interactions over multiple wireless protocols while carrying out a wireless call. From the above description it is manifest that various techniques can be used for implementing the concepts described in the present application without departing from the scope of those concepts. Moreover, while the concepts have been described with specific reference to certain implementations, a person of ordinary skill in the art would recognize that changes can be made in form and detail without departing from the scope of those concepts. As such, the described implementations are to be considered in all respects as illustrative and not restrictive. It should also be understood that the present application is not limited to the particular implementations described above, but many rearrangements, modifications, and substitutions are possible without departing from the scope of the present disclosure.