Estimating distance to iBeacon on iOS

There is a new iBeacon Document released by Apple on June 2, 2014 that states:

When building an application that uses either GPS or beacon, it is important to consider this accuracy. The values reported by the Core Location objects (the horizontalAccuracy property in the CLLocation class, or the accuracy property in the CLBeacon class) indicate this level of uncertainty, or the margin of error. Both are measured in meters. The higher the value, the lower the certainty of the position of the device or beacon. Keep in mind that depending on the physical surroundings a low accuracy may not be possible.

I suspect that's Apple's 'confidence' metric when reading their CLProximity values. I interpret that as obtaining something like:

CLProximityNear with an accuracy value of 5; Apple pinpoints your position within a 5m margin of error.

The general sentiment I'm getting from my general analysis of sources is that using beacon technology for distance approximation is probably not the strength of the technology.

EDIT: Chaise Hocking from Shine Technologies in Melbourne has an insightful blog post that has some experiments and results regarding the accuracy property.


Is there a way to get the distance estimate between an iOS device and a beacon WITHOUT having the 1-meter calibration value saved on the iOS device beforehand?

YES, you simply read the CLBeacon accuracy field as you suspected. This is an estimate of the distance to the beacon in meters.

This estimate uses an undocumented calculation that is based on the RSSI measurements (likely a 30 second running average, perhaps discarding outliers) combined with the 1-meter RSSI calibration value embedded in the iBeacon advertisement. A port of this calculation to Android is shown here.

And, no, there is no way to read the calibration value from an app. It is obscured by iOS, which disallows seeing the details of iBeacon Bluetooth LE advertisements. See here for a detailed explanation.

Tags:

Ios

Ibeacon