Strategic Design That Gets Results
Eddystone is an Google technology which allows mobile apps to listen for signals from beacons in the physical world and react accordingly. It is a technology which uses bluetooth low-energy(Bluetooth/LE/BLE) connection to communicate with nearby devices. This is a location sensing application connects with these in-store beacons while detecting enabled smartphones to send push notifications.
Eddystone is a BLE format developed by Google. It’s open and multiplatform, so you can use it with both Android and iOS. There are four types of data a beacon can broadcast with Eddystone, described by three frames: Eddystone-UID for broadcasting beacons IDs. Eddystone-TLM for beacon telemetry.
Beacons are simple devices that send one-way bluetooth low energy (BLE) signals. These signals can be read by nearby Bluetooth-enabled devices. Beacons can be deployed at fixed places such as airports, museums, and bus stops, and attached to movable objects such as bicycles and taxis.
Eddystone can be detected by both Android and iOS devices. The Eddystone format includes the following:
Eddystone-UID contains an identifier of a beacon. An app installed on the phone can use the identifier to trigger desired action, just like with iBeacon. Whereas the iBeacon identifier is composed of three parts: UUID, major number and minor number, and is 20 bytes long, Eddystone-UID is 16 bytes long and split into two parts:
Eddystone-URL packet contains a single field: URL. The size of the field depends on the length of the URL.The promise and purpose of the Eddystone-URL packet ties directly into the concept of Physical Web. Whereas with iBeacon or Eddystone-UID there’s a need for an app to take the beacon’s identifier and translate it into certain actions, with Eddystone-URL the data is encoded directly in the beacon’s advertising packet. This means that the user can access content—usually in form of a website—without the developer needing to build a native experience.
Eddystone-TLM packet is designed to be broadcast by the beacon alongside the “data” packets (i.e., UID and/or URL) for the purposes of fleet management. Nearby Bluetooth-capable devices can read these packets and relay them to a fleet management service—like the Estimote Cloud. This service can then notify the owner of the beacon that, e.g., the battery is running out.
Eddystone-EID packet is designed for security. The Ephemeral ID is seemingly random and can be resolved by requesting cloud resolver hosted by Google. Resolved EID will return description and attachments assigned to it using Google Beacon Proximity API or Google Developer Console.