excerpt from Deep Dive: Mobility Services APIs (with Sample Code!) by
Notification APIs are very useful as they generate event notifications when predefined events occur. These APIs are mostly used to track wireless (WIFI) devices. The CMX provides event notifications for the following use case scenarios:
- User is tracking a set of devices and he/she needs to get alert when any of them is absent for more than the specified time period (Absence event)
- User has setup a number of RFID tags that have batteries. In case of battery power goes low, he/she needs to get alert that batteries need to be replaced (Battery event)
- User wants to monitor the movement a set of assets that have attached RFID tags. As they pass in or out of a zone where Exciters are placed, he needs to get alerted (Exciter event)
- User wants to know all the wireless devices that enter or leave a configured zone (Containment event)
- User has set a number of RFID tags to secure his assets. If the RFID tags are detached or tampered, he/she needs to get alert so that the assets do not get lost/stolen (Emergency event)
- User wants to track real time location of a set of wireless devices and he/she needs to get reported as these devices move more than a configured distance from its old location or a configured Marker (Movement event)
- User wants to know any new wireless device that enters into his/her premise (Presence event)
The majority of RFID tags currently produced commercially are passive RFID tags, consisting basically of a micro-circuit and an antenna. They are referred to as passive tags because they are actively communicating only when they are within the electromagnetic field of a passive RFID tag reader or interrogator.
Another type of common RFID tag in the current marketplace is known as the active RFID tag, which usually contains a battery that directly powers RF communication. This onboard power source allows an active RFID tag to transmit information about itself at great range, either by constantly beaconing this information to a RFID tag reader or by transmitting only when it is prompted to do so.
Rogue access points, which are access points that are detected by the wireless LAN infrastructure and determined not to be members of the same mobility group or WLAN system.
Rogue clients, which are clients associated to rogue access points.
Interferers as reported by Clean Air in PI so that they can be removed to improve the wireless communication.
Standard WLAN clients - id is MacAddress, IP Address or Username of the wireless client.
RFID tags - id is MacAddress of the Tag
Rogue clients - id is MacAddress of the Rogue Client
Rogue access points - id is MacAddress of the Rogue AP
Interferers - id is MacAddress of the Interferer