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:

  1. in cases important ios app woken in background detecting group of beacons?

  2. 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:

  1. you can register maximum of 20 regions per app.

  2. 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:

  1. redefine regions.

  2. configure beacons' transmitter power lower exit event , entry event.

  3. 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

Popular posts from this blog

angularjs - ADAL JS Angular- WebAPI add a new role claim to the token -

php - CakePHP HttpSockets send array of paramms -

node.js - Using Node without global install -