Difference between revisions of "Template:IBeacon Data Structure"

From Wiki Knowledge Base | Teltonika SAS
Line 14: Line 14:
 
|-
 
|-
 
| style="background:red;" |
 
| style="background:red;" |
|Beacon flag
+
|iBeacon with RSSI flag
 
|21
 
|21
 
|-
 
|-
Line 36: Line 36:
 
|-
 
|-
 
| style="background:red;" |
 
| style="background:red;" |
|Beacon flag
+
|iBeacon with RSSI flag
 
|21
 
|21
 
|-
 
|-

Revision as of 15:19, 31 July 2020

iBeacon data packet structure


Example of data parsing with two detected Beacons:

11213102030405060708090A0B0C0D0E0F104545010ABC212102030405060708090A0B0C0D0E0F10020B010AAD
First Beacon:
Data Part* 11
iBeacon with RSSI flag 21
UUID (Beacon #1) 3102030405060708090A0B0C0D0E0F10
Major 4545
Minor 010A
RSSI (Signal Strength: Signed 2's complement) BC
Second Beacon:
iBeacon with RSSI flag 21
UUID (Beacon #2) 2102030405060708090A0B0C0D0E0F10
Major 020B
Minor 010A
RSSI (Signal Strength: Signed 2's complement) AD


  • Data part 11 - 1 Record out of 1 Beacon record. First half byte specifies current record, second half specifies how many there are in total. For example: 25 - second record out of 5 records (that means the server can expect 3 more records with Event I/O ID 385). If the data does not fit in a single data transfer, they are separated. Data Part is used to determine if more data will be coming from the device.