Cisco Cisco Aironet 350 Mini-PCI Wireless LAN Client Adapter Guia Do Desenho
13-15
Enterprise Mobility 4.1 Design Guide
OL-14435-01
Chapter 13 Cisco Unified Wireless Location-Based Services
SOAP/XML Application Programming Interface
The “RFID Tag Considerations” section of Wi-Fi Location-Based Services: Design and Deployment
Considerations provides readers who are new to RFID with a foundation in both active and passive tag
technologies. Among other areas, this section comprehensively discusses the following:
Considerations provides readers who are new to RFID with a foundation in both active and passive tag
technologies. Among other areas, this section comprehensively discusses the following:
•
Passive RFID technology-Passive and semi-passive RFID tags
•
Active RFID technology-Beaconing, transponder, and 802.11 (Wi-Fi) RFID tags
•
Multimode RFID technology-A relatively new category offering multiple tag technologies in a
single device.
single device.
•
Chokepoint triggers-Proximity communication devices (often referred to simply as “chokepoints”)
that trigger tags to alter their configuration or behavior when the tag enters their area of operation.
that trigger tags to alter their configuration or behavior when the tag enters their area of operation.
•
Using RFID tags with the Location Appliance-Compatible RFID tags, enabling asset tag tracking,
configuring asset tags, and using 802.11b tags on 802.11g networks
configuring asset tags, and using 802.11b tags on 802.11g networks
•
Tag telemetry and notification considerations-Provides initial best practice recommendations and
other valuable information pertinent to the design of solutions dependent on telemetry and
emergency notification functions.
other valuable information pertinent to the design of solutions dependent on telemetry and
emergency notification functions.
•
Chokepoint design considerations- Provides best practice recommendations and other information
pertinent to the design of solutions augmenting the location capabilities of the Cisco UWN with
chokepoint-based proximity localization.
pertinent to the design of solutions augmenting the location capabilities of the Cisco UWN with
chokepoint-based proximity localization.
SOAP/XML Application Programming Interface
To facilitate the deployment of location-based applications in the enterprise, the Cisco Wireless
Location Appliance is equipped with a SOAP/XML API. Applications can make use of the location
information contained within the location appliance by importing components via the API such as entire
network maps including buildings, floors, access points, chokepoints, coverage areas, and device lists.
Actionable data can also be imported, such as recent and historical location as well as statistical device
information. Location-based alarms and notifications can be triggered in applications through area
boundary definitions, chokepoint proximity, tag emergency or missing status, tag battery status, allowed
areas, and allowed distances. All these capabilities allow the SOAP/XML API interface to the Cisco
Wireless Location Appliance API to be used for integration with external software applications such as
location-enabled asset management, enterprise-resource-planning (ERP) tools, and workflow
automation systems.
Location Appliance is equipped with a SOAP/XML API. Applications can make use of the location
information contained within the location appliance by importing components via the API such as entire
network maps including buildings, floors, access points, chokepoints, coverage areas, and device lists.
Actionable data can also be imported, such as recent and historical location as well as statistical device
information. Location-based alarms and notifications can be triggered in applications through area
boundary definitions, chokepoint proximity, tag emergency or missing status, tag battery status, allowed
areas, and allowed distances. All these capabilities allow the SOAP/XML API interface to the Cisco
Wireless Location Appliance API to be used for integration with external software applications such as
location-enabled asset management, enterprise-resource-planning (ERP) tools, and workflow
automation systems.
From a high-level perspective, a third-party application system can use the SOAP/XML API to
participate as a member of a location-aware system consisting of the following four basic components:
participate as a member of a location-aware system consisting of the following four basic components:
•
Location client—The primary role of the location client is to serve as the interface to the location
and asset information contained on the location server.
and asset information contained on the location server.
•
Control client—The primary role of the control client is to populate the server with information
about the physical environment (network designs, floors maps, calibration models, access point
locations, and so on) as well as the network elements that should be monitored.
about the physical environment (network designs, floors maps, calibration models, access point
locations, and so on) as well as the network elements that should be monitored.
•
Location server— The location server provides general location services for the Cisco UWN and is
responsible for running the algorithms that predict device location.
responsible for running the algorithms that predict device location.
•
WLAN system—All the monitored mobile devices (tags, mobile stations, rogue clients, and access
points) as well as supporting devices (such as chokepoint triggers) that serve as key components of
the wireless network, as well as the embedded software contained within WLAN controllers.
points) as well as supporting devices (such as chokepoint triggers) that serve as key components of
the wireless network, as well as the embedded software contained within WLAN controllers.
An in-depth examination of a location client implementation by a Cisco Technology Partner can be
found in the document entitled Design Considerations for Cisco – PanGo Asset Tracking, which is
located at the following URL:
found in the document entitled Design Considerations for Cisco – PanGo Asset Tracking, which is
located at the following URL: