Sabtu, 01 Agustus 2015

Google Eddystone: Open Source and Cross Platform Beacon Technology

Google Eddystone: Open Source and Cross Platform Beacon Technology - You need to decide whether you’d prefer to have a super-sharp screen or killer battery life. The Lenovo Yoga 920 lasts hours longer than the HP, and performs better in benchmarks and games with the same CPU (although if this is thanks to the Meltdown vulnerability, the playing field is effectively levelled). lasvegas, well we have collected a lot of data from the field directly and from many other blogs so very complete his discussion here about Google Eddystone: Open Source and Cross Platform Beacon Technology, on this blog we also have to provide the latest automotive information from all the brands associated with the automobile. ok please continue reading:

According to Google, Eddystone is a protocol specification that defines a Bluetooth low energy (BLE) message format for proximity beacon messages. It describes several different frame types that may be used individually or in combinations to create beacons that can be used for a variety of applications.

Google Eddystone

Give your users better location and proximity experiences by providing a strong context signal for their devices in the form of Bluetooth low energy (BLE) beacons with Eddystone™, the open beacon format from Google.

The Eddystone specification includes a number of broadcast frame types, including Eddystone-URL, the backbone of the Physical Web.

Eddystone: Openness and Flexibility

Google Eddystone Location Proximity

Well, it is not just the open nature; Eddystone supports multiple frame types for different use cases, making it easy to introduce new functionality easily. Historically, Bluetooth beacons signify one-way communications with the primary goal of sending a notification capable of displaying or transferring information upon a tap. Due to support of multiple frameworks, vendors will be able to use Eddystone for different functionality or purpose.

It can broadcast three signal types: UUID (similar to the iBeacon standard), URL (a successor to the UriBeacon standard) and TLM (a new telemetry signal).

Eddystone

Universally Unique Identifier (UUID): This is a 128-bit value that can separately identify every specific beacon in the world, which an app can listen and perform actions for. For instance, you can walk in WalMart, your favorite retail store. WalMart could deploy beacons in its store. The Walmart app could be programmed to listen for specific beacons and send special coupons or such information. The downside to UUIDs is that you need the appropriate app do anything with the information. This brings us to the second frame type.

URLs: With this capability, users don’t need to download app. The store can send a URL to the user’s phone and the consumer can look up the coupon or relevant information on a web browser. URL instead of UUID looks like a feasible option with universal appeal. It works best for small businesses without a dedicated app.

beacon fleet

Ephemeral Identifiers (EIDs): Privacy and security are the center point of this new technology. With Ephemeral Identifiers (EIDs), you can allow only authorized clients to decode them. While the technical specification of this feature will be released soon, we can be rest assured that this feature will allow users to do tasks in a secure manner.

Telemetry Data: This frame type would allow organization to manage their vast fleets of beacons. Beacons are battery driven and need batteries changed or fixed frequently. Telemetry frame type in sync with Proximity Beacon API can help deployers monitor beacons’ battery health and displacement.

Know more about Google's Eddystone

Tidak ada komentar:

Posting Komentar