How to design hardware to offer maximum connectivity without sacrificing security? That is the question I attempt to answer while explaining this challenge from the perspective of designing automobiles…
Recent reports of vehicle thefts in Europe have highlighted vulnerabilities in smart key systems, which were intended to enhance security. These systems relied on outdated wireless tech, creating security gaps. In response, the Bluetooth SIG introduced Channel Sounding in the new Bluetooth specifications, improving precision and security for proximity-based systems, such as keyless entry.
The first real test, however, was whether Channel Sounding could become a viable product. Moving beyond technical validation, key questions emerged: What do customers need? Will it perform reliably across scenarios? Can it be low-cost, scalable, and compatible with existing systems?
Let’s explore this through the vehicle access use case. Customers expect a seamless and secure experience when accessing their vehicle, just as they do with a mechanical key. That means:
- Consistency: It should work the same way every time.
- Reliability: No glitches. No waiting.
- Security: It must be tamper-proof.
- Affordability: It should not drive up the vehicle’s cost.
The Bluetooth Channel Sounding feature checks many boxes—accuracy, security, and theoretical reliability.
But in the real world, the picture is more complex. Most smart keys are integrated into smartphones, raising the question: Is Channel Sounding supported on phones? The answer was no at the time, and widespread adoption might take several years to occur. It is important to understand the technical complexity (software update vs hardware design) and the market conditions that factor into the adoption of any new standard.
Another challenge is latency. Cars can pair with multiple phones using Bluetooth for audio, fitness, location, and other purposes, making a low-latency connection difficult. While Channel Sounding interleaves ranging and data exchange, its performance in noisy environments with multiple BLE devices is yet to be proven at this time. Great on paper, but uncertain in real-world product terms.
When selecting an architecture and technology for a product with connectivity, several key considerations should be taken into account. Often, thinking about ‘what customers want’ can guide us to make the correct choices for the product.
| The hidden pitfalls of connected devices—and how smart design can avoid them |
| These takeaways underscore that in the rapidly evolving world of connected electronics, robust security, real-world performance, and user-centric design are non-negotiable for successful products. • Technology on paper vs product reality. A technology that appears robust in theory may encounter significant hurdles in real-world product integration, particularly in terms of user experience, compatibility, and cost. • Customer-centric product development. Successful connectivity products must prioritise reliability, seamless operation, security, and affordability—mirroring the dependability of mechanical keys without added complexity or cost. • Smartphone integration challenges. Transitioning vehicle keys to smartphones introduces new obstacles, such as ensuring consistent performance across platforms and keeping up with updates and changes on multiple platforms. • Environmental and ecosystem factors are critical. Connectivity solutions must account for unpredictable real-world environments, as signal range can drop dramatically due to obstacles like walls, other vehicles, or even the human body, requiring robust design margins. • Security must be built-in, not bolted on. High-profile attacks, such as remote vehicle takeovers and medical device recalls, highlight the need for security to be integral to the design process, ensuring proper isolation, authentication, and encryption from the outset. • Ecosystem complexity increases attack surface. Modern vehicles and IoT products connect via multiple wireless protocols (Wi-Fi, BLE, cellular, proprietary RF), each introducing potential vulnerabilities. A single weak link can compromise the entire system. • Lessons from medical device recalls. Basic design lapses, such as missing authentication and unencrypted data, can have life-threatening consequences, reinforcing the need for rigorous security hygiene in all connected products. • Proactive design prevents costly failures. Addressing connectivity and security challenges early in the design phase, rather than reacting to field failures, saves time, money, and reputation. |
Connectivity is more challenging
Connectivity is far more complex than simply adding a motor or light to a product.
OOPS! THIS IS EFY PRIME CONTENT…
which means that you need to be an EFY PRIME subscriber to read it.
EFY PRIME content is our best content. Hence, you need to make a small investment to access all of our content including EFY Prime content.
If you’re already an EFY PRIME member, feel free to login below.
Else, CLICK HERE to invest in an EFY Prime account and become our VIP customer who can access all our content, and that too without the clutter of ads!
BENEFITS OF EFY PRIME MEMBERSHIP:
(1) Zero Clutter AD free experience
(2) Super-fast user experience
(3) Focussed reading experience with no distractions
(4) Access to all our content including our Best-of-Best which is EFY Prime