BLE beaconing interoperability – Basic guidelines

BLE beaconing interoperability – Basic guidelines

The NAO Suite is designed to be interoperable with 3rd party BLE beacons and tags. This page aims at providing a first layer of interoperability requirements to ease the compatibility assessment with beacons & tags vendors.

Disclaimer: This list is a public limited extract of Pole Star interoperability guidelines. The full guidelines require an NDA in place to be shared. To fully validate the interoperability of a 3rd party BLE beacon/tag before a customer project, Pole Star recommends going through a qualification phase in our Toulouse lab.

BLE Beacons interoperability (NAO Suite)

#CategoryRequested valueImportance
REQ1BLE beaconing (Bluetooth LE advertising)Broadcast Undirected Advertising PDU Type (ADV) packets, using LE_1M modulationMajor
REQ2Advertising parametersAdvertise on all 3-primary channels (37, 38, 39).Medium
REQ3Bluetooth MAC AddressStaticMedium
REQ4Transmit power>0 dBm
Static
Medium
REQ5Advertising PayloadShould be staticMajor
REQ6Advertising rate100ms to 1sMajor
REQ7Advertising Packet typeShould be of ADV_NON_CONN_IND type (not connectable)Medium
REQ8Advertising Payload typeiBeacon type.
follows Apple Proximity Beacon specification D1.0 (this includes UUID, Major and Minor different from '0').
See https://developer.apple.com/ibeacon
Major
REQ9Proximity UUID1 single static UUIDMajor
REQ10Major / minor identifiersUnique and static {major,minor} combination for every beaconMajor
REQ11iBeacon identifiers vs. MAC addressNo interleaving of different iBeacon frames/identifiers on the same MAC addressMajor

 

The NAO Suite is also interoperable with non-iBeacon BLE beacons, please contact Pole Star to assess the interoperability of such devices.

BLE Tags interoperability (NAO Track)

3rd party BLE tags implementing requirements 1 through 7 (included) in the table above can be used with Pole star NAO Track RTLS solution.

    • Related Articles

    • API – BLE Scan Callback Error

      NAOSDK integrates a new callback, onBleError, to notify the application when the SDK is unable to scan BLE measurements. Currently, this interface includes the error codes from the Android scanCallback API.” This callback is integrated into the ...
    • Background related guidelines

      Your app behavior should be adapted depending on the background permissions you asked for in the app plist, and on the ones granted by your users. Refer to https://docs.nao-cloud.com/docs/mobile-sdk/ios-sdk/configure-your-xcode-project/ for more ...
    • Overview

      Features Indoor positioning, using WiFI/BLE/GPS/MEMS sensors Beacon proximity detection, using BLE sensor Geofencing notification, using Indoor Positioning and Beacon proximity detection Geofencing-based analytics, using Geofencing notification ...
    • Release 22.09 (NAO SDK 4.11.8)

      Versions Component Version NAO® Cloud 22.09 NAO® SDK iOS 4.11.8 NAO® SDK Android 4.11.8 NAO® Logger iOS 4.11.8 NAO® Logger Android 4.11.8 New Features NAO® Cloud NAO Server, NAO Cloud self-hosted version is now available MappedIn maps compatibility ...
    • App publication

      If your application needs to use the service in background mode, you must follow a few rules to avoid a rejection of your application on AppStore. Basic rule Apple only accepts applications that use background modes when it is justified. Example use ...