Technical data

Using AeroScout

For this reason, the combination of AeroScout’s solution architecture with Meru’s

Virtual Cell deployments and Air Traffic Control

technology provide a more accu-

rate location for tags. In other words, Meru’s APs can all be deployed in a single

channel with a virtualized BSSID, thereby providing more reference points for the tag

messages and a more accurate location.

For the location of a tag to be calculated accurately, at least three access points

need to report the Wi-Fi message transmitted by the tag. A message received and

reported by less than three APs provides only a very general location which, in most

cases, is the location of the AP closest to the tag. To see the tag locations, use Aero-

Scout. Tags do not show up when you use the Meru CLI command show discov-

ered-station or anywhere else from the Meru CLI.

It is important to place APs closer to the perimeter of the space that will tag and

track assets, filling in coverage holes in the center of the coverage area. It is better

to surround the tracking area. Aside from this, use standard Meru Networks deploy-

ment guidelines in placing the APs and distancing them from one another. In other

words, plan for coverage and optimal data rates. When AeroScout Exciters are used

for choke-point location, one AP receiving the Tag message is enough to deliver an

accurate location report.

Tag Protocol Implementation

The Tag protocol operates between access points and the AeroScout engine. The Meru

AeroScout implementation supports tag (but not laptop) messages transmitted in

either in IBSS (default) or WDS frame format, although Meru APs receive and process

tag frames only in IBSS format.

Once the Meru controller and access points are upgraded to the current version, the

tag protocol is enabled automatically. No additional configuration steps are neces-

sary. Management of the AeroScout Tags, Engine, and MobileView application are

managed through the AeroScout platform. Figure 4 shows the operation and

messages used in the Tag protocol: