If proximity services are to be the next big hope for generating data, and money, from smartphone users, cellular networks will once again have to justify their role in that value chain. Small cells and the 3G/4G’s location capabilities make a strong case, based around high levels of security, privacy enforcement and ubiquity. But the unlicensed spectrum options mean a far wider variety of service providers can play, and Bluetooth beacons’ simplicity have made them a popular choice for supporting services from targeted in-store promotions to mobile payments to smart home services.
Apple’s iBeacon, the dominant format so far, is just the beginning of the story however, not the end. This week sees Google mounting its challenge to iBeacon, promising to open up the space still further, while the WiFi Alliance is starting to certify devices for compliance with WiFi Aware, which provides beacon-like capabilities over 802.11. That could work with Bluetooth Low Energy, with BLE providing the last hop as it often does on cellular systems, or in some scenarios, it could replace BLE entirely with WiFi.
Google’s beacon platform, Eddystone, like most of its efforts in the mobile web world, manages to be open source but also heavily controlled by the search giant. It is multi-platform, unlike iBeacon, which can only send its alerts to iDevices. While Apple uses services like iBeacon and Apple Pay to encourage increased uptake of its smartphones, making its walled garden as attractive as possible, Google needs to ensure users of all devices – not just Android – can access the services which deliver its advertising and data revenues. So Eddystone will support Android, iOS and another other platform with support for Bluetooth Low Energy (BLE).
Support for Eddystone is built into the ‘Nearby’ application programming interface (API), available to developers from Google Play Services (which is Android-based), or from GitHub under the Apache 2.0 licence.
Google has also improved on iBeacon by removing the necessity for users to have an application installed. It is not the first to do that – last November, Samsung asserted its independence from Google’s Android worldview by releasing its Proximity technology and Placedge software developers’ kit (SDK). These form a mobile marketing platform based on BLE beacons, but with no need for the user to have an app – for instance, from the store they are visiting – on their device.
Placedge does this by supporting device-level notification, which works with any gadget provided the retailer, or other marketeer, has registered its beacons with Samsung. In Eddystone’s case, it users URLs, which can work with any browser, as well as the UUIDs (universally unique identifier) that iBeacons employ to initiate communication with mobile devices. iBeacon, by contrast, uses only UUIDs.
Google will no doubt be looking well beyond classic in-store applications and seeking to leverage Eddystone as part of a broader IoT (internet of things) platform. This explains why it is taking a different approach to most existing players by not trying to create a vertical stack, but inviting a wide range of third parties into its ecosystem, unifying that with Eddystone, which basically just simplifies the set-up of the beacons, and the way they communicate with devices and back end software.
Matthew Kulick, a Google product manager, told ReadWrite: “You’ve got people who specialize in deploying beacons into people’s apps. It’s a relatively interesting ecosystem. That’s why we’re trying to offer tools and services here at multiple layers of the stack.”
The Eddystone APIs allow developers to associate a beacon with a physical location (the Proximity Beacon API) and extract data from nearby beacons, (the Nearby API). They also include management tools for companies deploying large numbers of beacons. A telemetry format will allow beacons to alert their operators to problems such as low battery levels. And Eddystone’s Ephemeral IDs claim to address some privacy concerns by encrypting the ID, so that only authorized clients can use them, and changing them frequently.
Eddystone’s success will depend on creating a wide developer base, and also on signing beacon hardware partners targeting interesting markets. The initial list of Eddystone backers includes Bluvision, Estimote and Kontakt.io, while Samsung’s initial hardware partners were GigaLane, Radius Networks, Roximity and Swirl.
The list of names indicates the fragmentation of this sector, both at hardware level and in terms of companies offering dashboard management systems, and of course tools to analyse all the data the beacons produce. Apple has a host of hardware partners, one of the most prominent being Qualcomm spin-out Gimbal, which was notably missing from the Eddystone launch.
Google admitted there had been no talks with Gimbal as yet, raising the spectre of an Apple/Gimbal alliance against the newcomer. However, the company will be thinking far more widely than just about near term alliances. Eddystone is likely to be just an early concrete indicator of a bigger Google vision for how users and devices interact in the world of ‘connected everything’. For instance, beacons are clearly a stepping stone to Google’s concept, unveiled last fall, of the Physical Web.
This is an experimental project and Google is opening up the code in the hope of creating a developer ecosystem and, in time, a de facto standard. A primary aim is to interact with connected objects without the need to install applications for each purpose. The mobile world is already shifting from downloaded, specific apps to more generalized web services, and the large numbers of gadgets which will potentially be involved in the IoT will make the apps route impractical in many areas.
Google expects the capability to be built, in future, into the operating systems of the handsets and tablets which will control the various gadgets around the smart home or office. Google’s UX designer and Chrome team member, Scott Jenson described the concept as the extension of the power of the URL to all kinds of connected objects.
“Our core premise is that you should be able to walk up to any ‘smart’ physical object (eg a vending machine, a poster, a toy, a bus stop, a rental car) and interact with it without first downloading an app,” he wrote. “The user experience of smart objects should be much like links in a web browser: ie just tap and use.” The idea is that the ‘things’ would broadcast URLs to web-based software which any nearby device can receive.”
The first Physical Web software works in the background, monitoring beacons as the user passes them, for possible interactions. A clear difference from Apple’s system is that Physical Web will not offer proactive notifications because “push notifications in general are too easily abused”. Rather it will provide a list, possibly curated according to the user’s past preferences. “The phone agent can sort by both signal strength as well as personal preference and history, among many other possible factors,” Jenson wrote in the documentation.
WiFi Aware may well become part of Physical Web, as it evolves, too. The latest WiFi Alliance specifications enable device users to locate others nearby in order to join them in game-playing, business discussions or content sharing. That connectivity could take place over conventional WiFi or over the peer-to-peer system, WiFi Direct. Supporting devices discover one another and then synchronize, creating what the Alliance calls a “common heartbeat”. This is highly energy efficient and works well in crowded environments, the body said. The devices form clusters and exchange small messages to allow for automatic discovery of nearby services, and a WiFi connection can then be made to an interesting application.
Similar ad hoc, P2P communications services are already available, using Bluetooth or WiFi (in the latter, Apple’s Bonjour is a well-used mechanism for automatic service discovery). But Aware will standardize the way they work, to simplify and encourage uptake and to introduce elements like security. The technology should be added to chips this year and available in smartphones and tablets next year.
WiFi Aware uses ‘neighbor awareness’ software which works continuously in the background, saving power by sending clusters of very small ping messages rather than broadcasting all the time. This is a similar approach to that of Bluetooth beacons (over which Aware can run, the Alliance’s head of marketing, Kelly Davis-Felner, told NetworkWorld). The software also helps users ascertain what kind of games or services are available before making a connection. However, in its current form, it has to be built into an app in order to be used.
Like beacons, WiFi Aware sees the supporters of connectivity technologies adding higher value capabilities to embed their standards tightly into the whole wireless experience, enabling new services while requiring limited effort from end users to activate them. In particular, these will rely on location and context awareness so that connectivity supports personally relevant services and so encourages higher usage.
“The Aware program has broad vendor support and momentum and is important to this industry, which is a sign that things will happen quickly,” Davis-Felner said.
No additional infrastructure is needed for deployment and native OS support is not essential either, though the Alliance acknowledged this would be an important element in getting developers and users to support the new capability. Initial supporters include the major WiFi chip vendors, Broadcom, Intel, Marvell and Realtek.