Richard Barrett, Product Director, Wireless Connectivity, told us the following:
Broadcom's 5G WiFi for automotive is derived from the same mobility architectures that support smartphones and tablets. They are lower power by design relative to traditional access point architectures. The SDIO3 interface is used for mobility as it is lower power than current PCIe technologies used in traditional access point.
This part being targeted towards the automotive industry: does this suggest the power draw is somewhat lower than a standard Access Point kind of product? Do you know what digital interface the chip is supporting?
@junko, I'm not talking about all those features being in the handset.
But the vehicle can be designed with a infotainment connection interface, so that the dealer can install brand-new electronics (also sourced from the car manufacturer, which is in the profit interest of both manufacturer and dealer) into an automobile that spent 5 years in the manufacturing and design phase. Or have it installed at the factory, although that seems to needlessly reduce the dealer's opportunity to upsell the electronics.
What's important is to decouple electronic from mechanical design. A six-year design leadtime for infotainment systems just is untenable. Try to persist with that, and you WILL end up with all worthwhile features in the handset.
A side benefit is that consumers can bring old cars back to the dealer for an electronics upgrade. Yes I realize that aftermarket upgrades represent a loss of profit for the manufacturer and dealer -- but the first manufacturer to deal with that not by integrating the system so much that it can't be upgraded, but provide their own upgrade path, is going to have a huge hit with consumers.
ANT is really strong in medical and sports related applications. People are much more familiar with BT in their automobiles. While I'd like to see ANT move into autos, I suspect it will be BT LE that dominates.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.