- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
According to The bluetooth core 4.1 spec the advertisement packets should contain the advertiser's BD_ADDR for example if the PDU type is ADV_IND the payload will have the AdvA (6 byte BD address) and AdvData ...
Is this information available to central side? (ie, an iOS or Android device?) ... it seems like some of this raw data is not available. Why would that be the case? What if someone wanted to add data to an advertisement packet?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello vesto,
Apple controls/restricts what advertisements can be received in an iBeacon protocol.
However, you can "stuff" additional octets in the Non-iBeacon Advertising packet - But then you violate the iBeacon spec.
So the iOS App can see the Advertising Payload with additional octets.
This is described in the CoreBluetooth Framework on the Apple Developer site.
Thanks
JT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The payload contains the bdaddr (public or random) and advertisement information. This must be available to the central. Did you encounter any situation where it's otherwise?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, this information does not appear to be available iOS. I am not sure why this is.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello vesto,
Apple controls/restricts what advertisements can be received in an iBeacon protocol.
However, you can "stuff" additional octets in the Non-iBeacon Advertising packet - But then you violate the iBeacon spec.
So the iOS App can see the Advertising Payload with additional octets.
This is described in the CoreBluetooth Framework on the Apple Developer site.
Thanks
JT