Bluetooth Low Energy (BLE)
BLE as name suggest it works like Classic Bluetooth and also it is low powered and low range , it is design as a low energy and lost cost signal transmitting system. It can be defined as a Wireless Personal area technology used for transmitting data over a short range. BLE is 60-80% cheaper than classic Bluetooth and it is use for simple applications requiring small periodic transfer of data.
BLE is 60-80% cheaper than classic Bluetooth and it is use for simple applications requiring small periodic transfer of data.
Apple’s Ibeacon has a very specific Standardize format for BLE advertising.It has four main pieces of Information, they are;
UUID: 16 byte String used to differentiate a large group of related beacons.
Major: This is a 2 byte string to distinguish a smaller subset of beacons within the larger group.
Minor: This is a 2 byte String to identified individual Beacons.
Tx Power: This is used to determine proximity (distance) of the beacon. This is a kind of signal strength sometimes also refer to as RSSI (Received signal strength Indicator). TX power is defined as the strength of signal exactly form 1 meter from the device.
Eddy stone is also a product using Bluetooth Low Energy for Real-life Applications similar to Apple’s IBeacon Eddy stone is designed by Google Developers the uniqueness of Eddy stone is it’s a Open Beacon Format.
One of the things beacons do is that they repeatedly broadcast Identifiers and that identifier marks a important place, objects in a way user devices understand. The signal sent by beacon marks a particular Cloud resource or an API; these can be very useful for providing service to the user displaying a message or activating some Event.
Eddy Stone Supports Two data Packet Types, all packet data type are shown below.
UID: it contains an identifier of a beacon, its 16 byte long and split in two parts namely Namespace and Instance, namespace having 10 bytes and Instance having 6 bytes.
URL: Eddy stone URL contains s single field the size of the field depends on the length of URL.
TLM: This packet is designed to be broadcast by the beacon alongside the “data’ packets for fleet management.
EID: This packet is designed for Security. The Ephemeral ID is random and can be resolved by requesting Cloud resolver.