Showing all posts tagged beacon:

Aruba Networks Sensors Everything

In case you missed it, Aruba Networks, an HP Enterprise Company announced the availability of their new Aruba Sensor product this week. This was spoken about at Atmosphere back in March, but then had seemingly disappeared. This new sensor enables Aruba Network's Meridian cloud analytics and wayfinding solution and best in class beacon management capabilities to be used on any wireless network. These sensors have a Low-Energy Bluetooth (BLE) radio to act as a beacon and manage other beacons in within a 25 meter radius and a wireless radio to provide network connectivity. Power is delivered through either AC power or USB and both power options offer security locks to ensure the safety of the Sensor. Making the same solution available for any wireless network is a huge deal as it allows for standardization of an engagement solution. ClearPass, Meridian and the Aruba Sensor/Beacon offer tremendous capabilities for any organization's network. Kudos to the team for embracing the market as a whole!



Who's Got it Better Than Aruba? Nobody, When It's Integrated Wi-Fi and Bluetooth

Wireless Field Day wrapped up last week with an incredible visit to Levi's Stadium, home of my San Francisco 49ers. As both a rabid football and Wi-Fi fan, it doesn't get any better than this to culminate an already awesome week. Aruba Networks and Levi's Stadium have set a new bar in terms of connectivity, engagement with the fan base and building for the mobile generation. Mobile Engagement at the stadium is done leveraging a custom app that has been location enabled using Aruba's Meridian SDK and a hybrid Wi-Fi and low energy bluetooth (BLE) infrastructure. If you aren't familiar with beacons and low energy bluetooth, please refer to my previous posts on the subject as they will serve as a good primer.

Managing and Deploying a Beacon Infrastructure
We've all seen a lot of hype around what BLE can do for you, but little has been mentioned about some of the challenges around managing these infrastructures. I had an opportunity to spend some time with Aruba Meridian back in January of this year and go through a class in which we built an underlying beacon infrastructure configuration and then developed an app that used that infrastructure. This process involved using the Aruba Beacons app and individually configuring each beacon. This process applies for firmware upgrades and reprogramming the beacons as well, even after deployment unless some other system is in place. Inherently beacons require that you are within their proximity 30-50' typically to do this kind of work. Needless to say in an environment like Levi's Stadium this would be unmanageable.


The Aruba Advantage
Aruba's infrastructure enables the management of beacons via bluetooth radios resident on their new access points or retrofit on the previous generation of APs via a USB bluetooth beacon. Aruba entered the hardware world of beacons to do right by their customers in developing an end-to-end solution that is supportable. This configuration enables beacon configuration and firmware updates to be executed via the Meridian cloud and pushed down to the beacons via controllers/instant APs and over the bluetooth radios to the beacons themselves.

Meridian
I have been a fan of Meridian Apps from the beginning and commend Aruba for pulling the trigger and acquiring the company. The "better together" mantra definitely rings true here as Meridian simplifies the most difficult piece of engaging customers--the mobile app. If you've never explored this world, it is a confusing mix of custom app developers, SDKs, etc. each with their own pros and cons. Meridian offers two levels of integration, one is the Meridian app maker and the second is the their SDK.

AppMaker and Navigation
The AppMaker simplifies the app creation process so much that most organizations could do this themselves if desired. I do recommend some guidance around the structure and design of the app, but it is built so that a marketing person could actually construct the app. My first go at building an app that included some points of interest, wayfinding, etc. took a couple of hours for something that would pass as an enterprise-grade mobile app. I've made multiple comments on social media about the wayfinding capabilities, especially the Americans with Disabilities Act (ADA) routing. The mobile app creator simply draws in the "roads" and the Meridian engine handles the routing. For each of these roads there is a flag as to whether or not that road is ADA accessible, enabling a user to request accessible routing if desired.

BluDot
"Google Maps, but Indoors" is one of the phrases heard most when it comes to describing what wayfinding is to the layperson. Aruba's BluDot solution gives you that real-time blue dot experience that shows you your current position. This makes finding directions easier as there is no need to enter a source and a destination, you simply need to know where you want to go. BluDot is powered by a combination of beacons and the Meridian cloud service and is the best in the business at doing this. The maps use a scalar vector floor plan to ensure navigation and zooming in/out look great and enable the app creator to create points of interest throughout the map.


Campaigns
Campaigns are the traditional push messaging of the beaconing world and allow for interaction with end users. Campaigns can be configured to run once, on a set schedule, or for a particular zone. Again Aruba does a brilliant job in making this easy to implement and understand. These push messages can make your visitors aware of a guest network, offer incentives, make them aware of current promotions, etc.


Google's Eddystone-Updating the Physical Web


Much ado has been made about the Apple iBeacon over the past couple of years with market analysts predicting a rise from $4B to $44B in iBeacon influenced sales. Outside of retail, some interesting use cases have cropped up and have been tested, however mainstream adoption for other verticals isn't there yet. Enter Apple's archrival Google with their Eddystone, an open-source, cross-platform low energy bluetooth (BLE) beacon. The open nature of the Google Eddystone and its ability to broadcast a URL offers some new and interesting use cases, especially since it no longer requires a mobile app. The requirement for a mobile app is the single largest hurdle to adoption of any beacon strategy as it requires end-users to opt in to using a company's solution in a major way. The upfront cost of a mobile app and often lack of understanding around mobile app strategy scares some companies away from attempting this and impedes the overall growth of the solution. Every conversation that I have had around iBeacon solutions to-date involves customer education around what is and is not possible and the level of effort required to make some things work.

What is Different?
Designed to be cross-platform, Google's Eddystone supports the Nearby API and is available on GitHub under Apache 2.0 license.

The Infobubble
Anyone interested in creating awareness of who they are, what they are doing, or empowering a device to do the same in a given location now has the ability to advertise to passersby. This has many implications from brand awareness to interacting with a specific device. Most importantly this can happen on the smallest of scales, increasing the chance for adoption and interaction since there is no dependency on a mobile app. Check out the Physical Web Cookbook for many newer ideas.

Multiple Frame Types
Google Eddystone supports multiple frame types enabling users to interact in a variety of ways. These frames are designated in the Service Data field associated with the Service UUID by using the high order four bits of the first octet. Github provides all this information in much more depth.

Frame Type
High-Order 4 Bits
Low-Order 4 Bits
(Reserved for Future Use)
Byte Value
Unique Identifier (UID)
0000
0000
0x00
Uniform Resource Locator (URL)
0001
0000
0x10
Telemetry Data (TLM)
0002
0000
0x20


Universally Unique Identifier (UUID)
If this sounds familiar, it is because it is the same type of identifier that iBeacons use. Google implemented the same 128-bit value that enables applications and specific use cases using major and minor numbers. This form of interaction is tied to a specific app and as such is limited to users who have that specific app installed.

URLs
The implementation of URL broadcast is meant to address the issues in which users aren't so interested in installing an app and caters to a "one-time use" scenario. This powerful option can provide a user with information through a standard web browser, ensuring that all users have access to this data. Effectively this URL broadcast could replace every instance of a QR code with the added benefit of not actually having to take a picture of the QR code, this data can just be available over the air.

Ephemeral Identifiers (EIDs)
A secured identifier that only permits authorized access. A 10-byte namespace is used to ensure uniqueness across multiple Eddystone implementations. Security is achieved using a truncated hash of a fully qualified domain name (FQDN) or an elided version 4 UUID which involves removing some information from the UUID.

Telemetry Data
Diagnostic data enabling an organization to better manage their beacon infrastructure. This includes battery life and other critical info. It is important to know that this type of information must be paired with either EID or URL since it does not contain a beacon ID. Telemetry data may include battery voltage, beacon temperature, advertising PDU count, and uptime.

Eddystone Ecosystem

Nearby API

Proximity Beacon API
The Proximity Beacon API is a new interface enabling users to manage their beacons via the cloud and use a REST interface. This enables monitoring of the telemetry data previously mentioned as well as reconfiguration of the beacons.

BKON Eddystone
I opted for the BKON Eddystones to try, there are a few options out there, but I liked the approach and packaging that I saw on the BKON site and acquired them through Amazon (2 for $60). AAA batteries were included and already installed. Also included a screwdriver and 3M dual-sided sticky tape. One thing I am not a fan of is the lack of screw type mounts as seen on the Aruba beacons. I'm not convinced the 3M sticky tape will hold up as long as a battery will, especially for beacons in tougher climates--outdoors, fridge/freezer, high humidity, etc. That being said though, the overall packaging and included items are great!

PHY.Net
Setting up with PHY.net was painless, simple field with beacon ID (located on side of beacon), valid email address and contact info. BKON sends a validation email to confirm.



Browsing...and a surprise
As of right now a specific browser is needed to browse the Physical Web. The screenshot to the right is from BKON's own "BeaconPages" available for IOS. Alternatively, you can install "Physical Web" available on both IOS and Android. I found it interesting that this Physical Web app picked up my HP printer via Bluetooth and let me view the configuration page. Interestingly, the Bluetooth radio is configured as "off" on the HP printer. I could pull my MAC and IP addresses, subnet mask, gateway, DNS info and host names via the Physical Web browser. I would have to log in to the printer to change any settings, but I was still surprised at how much information was readily available. Perhaps the next blog post will be on security.....