Simon Forrest, Senior Manager of Marketing, Imagination Technologies
There has been a lot of momentum lately around wearable initiatives and technologies focused on creating a new generation of chips built specifically for these devices. We provide an overview of the current trends and best practices for designing wearable devices that offer the best possible user experience.
Today, low-end Internet of Things (IoT) devices and wearables typically use multiple general purpose chips to achieve microcontroller, sensor and radio functionality, leading to expensive and often compromised solutions. Meanwhile, high-end devices such as smart watches or smart glasses use existing smartphone chips which in turn lead to overpowered and expensive devices.
To reach the incredible volumes predicted by analysts, systems-on-chips (SoCs) for wearable devices and IoT must be designed from the ground-up. Working with our partners, Imagination is enabling the design of new chips that extend battery life, enhance data and device security and feature the right balance between processor, graphics, video and multi-standard connectivity solutions.
We are also focused on building the necessary standards, operating environments and other ecosystem technologies to support these chips.
Rule #1: One size does not fit all
Wearables have different features and require a specific type of SoC. If you are creating computing platforms for smart devices, there are two main categories to consider:
Input wearables are devices such as fitness bands, heart rate monitors, sleep monitors and near field communication (NFC) rings. They are essentially smart, connected sensors with minimal or no displays that have extremely low power requirements. Their main role is to collect raw data, then filter and send it to a central hub, be it a mobile device (smartphone or tablet) or a residential gateway in your connected home. On the hub, this data is translated into usable information. Additional functionality can then enable automatic actions or alerts based on that information.
For this category, the essential element is designing for the lowest power connectivity possible. You typically require a high performance 32-bit MCU-class processor for fast, efficient processing, ideally a compact-footprint, unified MCU/MPU and DSP embedded processor core. Designers will also need to select a solution for baseband communications; combining Bluetooth-LE (low energy) with FM in one small integrated radio solution is ideal for ultra-lowpower wearable applications.
Depending on the application area, designers can also include dedicated hardware to support a gyroscope or motion sensors.
Output wearables are devices such as smart watches or smart glasses that provide quick and easy, at-a-glance access to immediate information. This information is usually specifically tailored for a small screen and is available to the user quickly and in real-time. Output wearables are aimed at accelerating daily tasks, and offer a more intuitive way of interacting with technology.
When it comes to designing chipsets for output wearables, designers need to make sure that each processor inside the SoC is used as efficiently as possible. Low power is still the dominant factor when architecting the underlying system, but the focus should be on creating a general-purpose platform that performs a subset of the tasks a smartphone or a tablet might do.
An example of such a platform for smart glasses can be designed by pairing a low-power, high-performance CPU with the smallest available OpenGL ES 3.0/OpenCL GPUs, HEVC-capable hardware video transcoders, a configurable OpenVX-ready ISP pipeline and a connectivity processor that supports Wi-Fi 802.11n 1×1 and Bluetooth.
Rule #2: Augment the user experience
An important aspect of wearable devices is the user experience and interface. Designing interfaces for wearables should be based on how consumers will use them, not on replicating smartphone or tablet experiences.
Even though using a popular, off-the-shelf operating system like Android might sound like a quick and easy fix for devices with a screen, what you really want to design is a customized, fully-skinned interface that fits within the confines of a miniature display surface. For example, Google has recently launched Android Wear, an operating system designed specifically for wearables.
Source: Android Wear: http://developer.android.com/wear/index.html
More importantly, wearables should augment other mobile devices, not try to replace (part of) their functionality. Trying to cram features in by using a checklist approach will lead to underpowered solutions that users will quickly abandon. Instead, companies should focus on optimizing user and machine interfaces to ensure that wearable devices work well together and with other mobile devices.
Source: Android Wear: http://developer.android.com/wear/index.html
Rule #3: Design new wearable SoCs
Every engineer has heard of the “design and reuse” approach. However, the principle can only apply to solutions that have proven to work universally; this is not the case for wearables.
Even though wearables are mobile devices at heart, they have different and specific requirements to smartphones and tablets (more on this later on).
Re-using mobile SoCs for every wearable category out there (smart watches, smart glasses, smart wristbands, etc.) is unsustainable not only because these devices come in distinct shapes and sizes, but mainly because their power profiles can vary radically.
Source: SpeedUP smartwatch: http://speedup.co.id/
Today’s wearable devices are generally a magnitude off in terms of battery life. Most current wearable fitness devices usually last for two to three days when in fact they should be providing weeks or months of uninterrupted service. Reports have placed some smart watches at battery life of less than one day; most consumers would expect at least one week. People have different expectations between smartphones, tablets and wearables and don’t usually factor a charging regime into their daily habits for a these ultra-portable devices.
Plus, if a smart watch is supposed to act as a regular watch during the day and a sleep health monitor at night, when would you charge it? Energy harvesting technologies offer a potential solution here; again, high-performance at ultra-low power is an overarching requirement.
Rule #4: Wearables must be always on, always connected devices
Small form factors of wearable devices dictate the use of extremely small batteries, which of course limits the battery life of these devices. Because of this, wearables need smart technologies that implement low power methodologies in various points of the design. This is to ensure that the processors operate as efficiently as possible and in ways which suit short bursts of intense activity followed by longer periods of idleness. Designers must implement (or choose processors that already implement) advanced power management techniques such as automatically enabled clock gating, the ability to intelligently turn power on/off for specific cores or clusters, and intelligently using the Microkernel firmware to offer lower latency workload feedback into DVFS and power management decision process.
To complement the hardware, wearables must support the appropriate low power standards that enable prolonged “always on” functionality. Although there are many options to choose from, it seems that the main contender to the title is Bluetooth LE.
Bluetooth LE is a power-friendly version of the Bluetooth wireless technology designed to provide practical connectivity for the mass market. The power-efficiency of Bluetooth LE creates opportunity for devices that run off a tiny battery for long periods of time; even better, Bluetooth is compatible with existing smartphones and tablets for device-to-device communication.
Rule #5: A combination of reliable hardware and software security protocols is vital
Wearables require multiple layers of security due to the sensitive nature of the data they have access to:
- Device security: wearable devices need to run operating systems and applications securely; this requires support for multiple secure environments.
- Link security: transmission of information between wearables and a central hub must be protected and encrypted.
- Cloud security: storage of personal information is another delicate area; consumers want to know that their details are safe from unwanted intruders and unauthorized use.
These security layers must be enabled both in hardware and software, and can scale from the core level all the way up to the system level. An example of implementing core-level security is a virtualization-based approach where multiple operating systems can co-exist in multiple security contexts, thus supporting secure content delivery, secure payments, identity protection and more, across multiple applications and content sources.
Rule #6: A viable and growing ecosystem is essential
More and more companies are waking up to the reality of how important a developer ecosystem is to the success of any consumer platform. The same rule applies to wearables: developers need to see the value added factor of wearables; otherwise they will not create more than a few apps.
Source: Ineda SoC: www.inedasystems.com
Another important element in creating a thriving environment for wearables is an open approach to APIs and device intercommunication. For example, limiting compatibility to only certain brands of devices means consumers will have no incentive to buy a wearable unless they own that particular brand. Efforts such as the recent AllSeen Alliance are steps in the right direction in order to create an open standard for platforms and APIs.
Rule #7: Set the right price
Finally, wearables need to adopt a three tier pricing model similar to their smartphone and tablet brethren that makes them accessible to the largest possible number of consumers. There is so much buzz around wearables that even fashion brands like Nike are getting in on this new product category.
By creating entry-level, mid-range and high-end devices, companies can create an instant, compelling and complete line-up of devices that addresses the growing consumer demand. The sensible approach when designing SoCs for any market is to utilize proven solutions. For the past decade, Imagination Technologies has been creating multimedia, processor and connectivity IP that has shipped in billions of mobile and embedded devices from some of the industry’s leading silicon vendors. Imagination provides a one-stop shop which includes all the required IP, design services and complementary software tools and platforms required for any company to succeed. On top of these IP system-optimized technologies, Imagination can offer unique value-added solutions like FlowCloud – a platform that helps companies deliver a complete IoT-ready solution, including all the security involved in device to device and device to cloud communication with back end services.
Pulling it all together
Given their potential, there is a clear opportunity for wearable devices to succeed considering everyone from chip makers and OEMs to consumers and carriers believe this category of devices will be in high demand in the coming decade. Once it reaches critical mass, wearable technology will become embedded within every aspect of our lives, allowing us to do everything better, faster and simpler.
Imagination is proud to already have our IP in such SoCs, and our customers are giving us great feedback on our wearables roadmap. Together with industry initiatives such as the AllSeen Alliance or the cool new Android Wear from Google, and key partners including Ineda Systems, Ingenic Semiconductor, Microchip Technology and others, we are taking a leading role in building the ecosystems and technologies needed for a new generation of SoCs.