An RFID tag is a WIFI 802.11 device equipped with a transmitter and an antenna. It does not associate to access points so it is not acting like other wireless clients. An RFID tag transmits information on a regular basis. This information can be called beacons. The Nature of the beacons is multicast traffic sent at low rates. Every X amount of seconds the RFID tag sends Y amount of beacons on its configured channels. When completing a cycle across all configured channels, the RFID tag sits on standby and waits for the next round to do the same actions over and over again.
When deploying RFID for asset tracking in WIFI, you may want to consider the following:
1.How many beacons per channel will the RFID Send?
Due to the nature of Multicast traffic, shoot and forget, no ACK, increasing the amount of beacons per channel is a good practice.
Under clean RF environment Access points will receive tag updates and report it to their WLC even if the tag is configured to send one beacon per channel.
However, under challenging RF environment, there is a possibility to miss a tag update on a certain Access Point. Missing a tag update on an important nearby AP can lead into inacurate location. By increasing the beacon amount per channel to two or three instead of one, we will be lowering down the possibility of the tag update not to be heard by the Access Points around it.
You have to take into consideration the Battery life affected by the extra transmission for your RFID tags from the vendor.
2. Which Channels?
In 2.4 GHz deployment, channels 1, 6 and 11 are the non overlapping channels in the spectrum. The recommended channels to be configured on an RFID tag will be 1,6 and 11. Note that in some scenarios, an Access Point will be able to hear RFID tag updates on a channel that is different from the one it is operating on. By design, the Access Point will drop these updates and will not forward them to the WLC.
3. How much time between Iterations?
Configuring the Beaconing interval plays an important role for Location Tracking since it is defining how much time separates every location calculation. For stationary tags you may want to define a beaconing interval of 60 seconds.
Keep in mind that when a tag moves you need more real time information to base the calculation upon. For this enable motion beaconing on the RFID tag for it to beacon every 10 seconds.
4. How much time does an RFID wait between each packet transmission?
Time between each packet transmission can be configured on an RFID tag. Example configuring: 1 packet per channel with 512 msec spacing results in having 1.5 seconds required for an RFID to finish a complete iteration on all three channels.
Further more, there is a factor that could add up additional time for an RFID tag to complete all 3 channels updates. It is called CCA (Clear Channel Assessment). Most of the RFID tags do carrier sensing before transmitting. If the medium is busy they back off for additional time and refrain from transmission. After some time, if the medium is clear they will transmit and move to the next channel. If the medium is still busy then they will not transmit on that channel during that iteration and they will move to the next channel. The maximum amount of time for the back off is not a fixed and may vary from vendor to vendor.
Hello EveryoneWe have a very serious issue going on with our cisco access points. This is our fourth AP which is fully burned out. We are using cisco WS-C2960X-48LPD-L to connect these access points. And i am getting following errors on the switch.&n...
Hello All, I have an issue where we had a 3rd party contractor mount and connect a large number of 2802 AP's around a building and patch in 2 cables to each AP so that both ports are connected. Its not a problem as we only patched in a single c...
I have a problem with vWLC (8.10.151) and multicast. I don't have this problem with a 2504 controller, with which everything works perfectly. At this stage I'd just like to know if it is in fact possible to do what I need or if this is not supported ...
I am researching using open roaming and I found cisco documentation on how to enable open roaming on meraki devices. It all seems straight forward but where I am lost is how do I capture the info of the authorized user? If a user authenticates with ...
Hello, I'm facing an issue setting up a RootAP(With DHCP) and a Repeater.When I connect a wireless device to my RootAP (192.168.1.240), no problem, is authenticates, gets and IP, and reaches what is behind the ethernet port (192.168.1.10 for example).But,...