Google Nest Mini gets louder and gains onboard Assistant processing | SlashGear
Google debuts Nest Mini with wall mount and dedicated ML chip | VentureBeat
From the horse’s mouth
Nest Mini brings twice the bass and an upgraded Assistant (Product Blog Post)
The Google Nest Mini smart speaker, which is the successor to the Google Home Mini smart speaker, shows up a significant number of improvements including a richer sound. But it has also come about with the idea of locally processing your voice commands for better Google Assistant performance.
The traditional approach to processing voice commands that are said to a smart speaker or similar device is for that device to send them out as a voice recording to the cloud servers that are part of the voice-driven assistant platform. These servers then implement their artificial-intelligence and machine-learning technology to strip background noise, interpret the commands and supply the appropriate replies or actions back to that device.
But Google has improved on this by using a leaf out of the book associated with edge-computing technology. This is where some of the data storage or processing is performed local to the user before the data is sent to a cloud computing system. Here, Google uses a dedicated machine-language processor chip in their Nest Mini smart speaker to do some of the command processing before sending data about the user’s command to the Google Assistant cloud system.
It reduces the idea of your Google Nest Mini smart speaker being a simple conduit between your home network and the Google Assistant cloud. The key benefit is that you see a quicker response from the Google Assistant via that device. You also have the benefit of reducing the Internet bandwidth associated with handling the voice-driven home assistant activity, avoiding reduced performance for online gaming or multimedia streaming.
Google is working on taking this further with having Google-Assistant-based devices that have this kind of local processing process logic associated with user requests and programmable actions locally. It also includes keeping the logic associated with the Assistant liaising with other smart devices local to your home network, allowing for improvements to performance, user privacy and data security.
It could be seen by Amazon and others as a way to improve the performance of their voice-driven home-assistant platforms. This is more so where the competition between these platforms becomes more keen. As well, there could be a chance for third-party Google Assistant (Home) implementations to look towards using local processing to improve the Assistant’s response.
An issue that will crop up is having multiple devices that have this kind of local processing existing on the same home network help each other to increase the voice-driven assistant’s performance. This can also include using a software approach to make the devices equipped with the local processing provide improved performance for those that don’t have this processing. It will be an issue with the likes of Google Nest Mini and similar entry-level devices that appeal to the idea of having many installed around the house, along with the idea of equipping smart displays with this kind of local processing.
What I see of this is that the use of edge-computing technology is coming to the fore as far as improving responsiveness in the common voice-driven home-assistant platforms.