iBeacon Region monitoring too aggressive -
we using ios's ibeacon region monitoring scan beacons. recommended way(if possible) control size of individual region? placing beacons close each others , regions overlapping. need regions smaller, gaps exist between regions fine.
thanks,
iox
both regions define , identifiers choose beacons should driven use cases. ask these 2 questions:
in cases important ios app woken in background detecting group of beacons?
in cases important ios app woken in background no longer detecting group of beacons?
for each use case defined 1 , 2 above, need define beacon region (a combination of proximity uuid , major fields) registered app ios.
you should refine list taking account 2 rules:
you can register maximum of 20 regions per app.
as have seen, if transmission range of multiple beacons overlap, , in same defined region, won't exit/entry event move 1 beacon next. there's nothing wrong long meets use cases.
if important use cases new entry/exit event move 1 beacon next, need 1 or more of following:
redefine regions.
configure beacons' transmitter power lower exit event , entry event.
move beacons further apart exit event , entry event.
designing region , identifier scheme of art science. again, important best practice let use cases drive identifiers , regions, , not organizational hierarchy or other abstract scheme.
Comments
Post a Comment