Installation guide

23
Wi-Fi Location-Based Services—Design and Deployment Considerations
OL-11612-01
Cisco Location-Based Services Architecture
participating in location tracking during controller synchronization. Synchronization occurs either
on-demand or as a scheduled task, the timing of which is determined by the Administration > Scheduled
Tasks main menu option under the Cisco Wireless Control System (WCS).
Location information is displayed to the end user using a location client application in conjunction with
the Cisco Wireless Location Appliance. Typically this role is fulfilled by the Cisco WCS, which, as is
explained in subsequent sections of this document, is capable of displaying a wide multitude of
information regarding the location of clients, asset tags, rogue access points, and rogue clients.
Note For important information regarding compatibility between versions of WCS and the Cisco Wireless
Location Appliance, see “Release Notes for Cisco Wireless Location Appliance” at the following URL:
http://www.cisco.com/en/US/products/ps6386/prod_release_note09186a00806b5ec7.html.
Location client functionality is not limited to the WCS, because other third-party applications written in
accordance with the Cisco Location Appliance Application Programming Interface (API) and using the
SOAP/XML protocol can also serve as a location client to the Wireless Location Appliance (as shown
in Figure 8). The Cisco Location Appliance is also capable of issuing notifications to external systems
via email (SMTP), syslog, SNMP traps, or the SOAP/XML protocol. These notifications can be issued
depending on the occurrence of a variety of events, as is discussed in subsequent sections of this
document.
Role of the Location Appliance
When a Cisco Location Appliance is added to a Cisco LWAPP-enabled Unified Wireless Network with
a location-enabled WCS, the location appliance assumes responsibility for several important tasks. Key
among these are the execution of positioning algorithms, maintenance of calibration information,
triggering and dispatch of location notifications, and the ongoing processing of historical location and
statistics information. WCS acts in concert with the location appliance by serving as the user interface
(UI) for the services provided by the location appliance. Although it is possible to access the location
appliance directly via SSH or a console session, all end user interaction with the location appliance is
typically via WCS or a third-party location client application (except for initial setup of the location
appliance and whenever it is necessary to quiesce the appliance).
The integration of a Cisco Location Appliance into a Cisco Unified Wireless Network architecture
immediately enables improvements in the location capabilities of the network, such as the following:
• Scalability—Adding a Cisco Location Appliance greatly increases the scalability of the Cisco LBS
solution from on-demand tracking of a single device to a maximum capacity of 2500 devices
(WLAN clients, RFID tags, rogue access points, and rogue clients). For deployments requiring
support of a greater number of devices, additional location appliances can be deployed and managed
under a common WCS.
• Historical and statistics trending—The appliance records and maintains historical location and
statistics information, which is available for viewing via WCS.
• Location notifications—The Cisco Location Appliance can dispatch location-based event
notifications via email (SMTP), syslog, SNMP traps, and SOAP/XML directly to specified
destinations. These notifications can be triggered simply if the client or asset location changes,
strays beyond set distances from pre-determined marker locations, or otherwise becomes missing or
enters/leaves coverage areas. Notifications can also be generated for asset tag battery levels (that is,
low battery notification).