> For the complete documentation index, see [llms.txt](https://docs.drivequant.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drivequant.com/stolen-vehicle-locator/ibeacon-configuration.md).

# iBeacon configuration

This section explains how to configure a Bluetooth beacon to make it compatible with the DriveKit SDK.

iBeacon is a universal, industry-proven standard. DriveQuant does not manufacture Bluetooth beacons, but we can help in two ways:

* Guide you through configuring your existing hardware.
* Recommend suppliers we have already worked with, capable of quickly producing cost-effective, compatible beacons.

## Unique vehicle identification

Minimising the number of UUIDs across your iBeacon fleet is essential. iOS enforces a hard limit of 20 regions (UUIDs) per app, which strongly constrains system design.

For this reason, we recommend using a single UUID for all your iBeacon devices. The Major and Minor parameters are unsigned 16-bit integers, each ranging from 0 to 65,535. With a single UUID, the Major/Minor combination can uniquely identify over 4 billion vehicles — far beyond the needs of any fleet.

## iBeacon frame configuration

Recommended parameters differ depending on the intended use case.

### Trip Analysis

<table><thead><tr><th width="150.25">Parameter</th><th width="179.75" align="center">Recommended value</th><th>Notes</th></tr></thead><tbody><tr><td>Advertising interval</td><td align="center">500 ms</td><td>Good balance between detection responsiveness and battery consumption</td></tr><tr><td>Tx Power</td><td align="center">−12 dBm</td><td>10 m range in open air, sufficient to detect the beacon from the driver's smartphone</td></tr></tbody></table>

### Stolen Vehicle Locator

<table><thead><tr><th width="150.25">Parameter</th><th width="179.75" align="center">Recommended value</th><th>Notes</th></tr></thead><tbody><tr><td>Advertising interval</td><td align="center">300 ms</td><td>Good balance between detection responsiveness and battery consumption</td></tr><tr><td>Tx Power</td><td align="center">+2 dBm</td><td>40 m range in open air, sufficient to detect the beacon from any nearby smartphone</td></tr></tbody></table>

### Dual-use configuration (Trip Analysis + Stolen Vehicle Locator)&#x20;

If your app uses both features, a single beacon can emit two simultaneous iBeacon frames:

* Each frame uses its own dedicated UUID to distinguish the two use cases.
* The Major and Minor values are shared across both frames, providing consistent vehicle identification regardless of which component detects the beacon.
* Trip Analysis is configured to detect the short-range frame (−12 dBm).
* Stolen Vehicle Locator is configured to detect the long-range frame (+2 dBm).

{% hint style="warning" %}
Using two distinct UUIDs also prevents the long-range frame from triggering unwanted trip starts. At 40 m range, a beacon in a nearby parked vehicle (in a car park or at home) could otherwise activate trip detection simply because the user is within range.
{% endhint %}

### Configuration summary

<table data-header-hidden><thead><tr><th width="172.5"></th><th width="276.5"></th><th></th></tr></thead><tbody><tr><td></td><td><strong>Trip Analysis</strong></td><td><strong>Stolen Vehicle Locator</strong></td></tr><tr><td>Purpose</td><td>Detect the vehicle's beacon from its owner's smartphone</td><td>Good balance between detection responsiveness and battery consumption</td></tr><tr><td>UUID</td><td>Dedicated (short-range frame)</td><td>Dedicated (long-range frame)</td></tr><tr><td>Major/Minor</td><td>Shared — identify the vehicle</td><td>Shared — identify the vehicle</td></tr><tr><td>Advertising interval</td><td>500 ms</td><td>300 ms</td></tr><tr><td>Tx Power</td><td>-12 dBm</td><td>+2 dBm</td></tr><tr><td>Indicative range</td><td>10 m</td><td>40 m</td></tr></tbody></table>