The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Cisco Hyperlocation
The Cisco Hyperlocation radio module provides the following:
WSM Radio Module functions that are extended to:
Expanded location functionality:
Bluetooth Low Energy (BLE) capability
The Cisco Hyperlocation Radio Module is supported on Cisco Aironet 3600 and 3700 Series Access Points.
For more information about Cisco Hyperlocation, see the following documents:
Hyperlocation configurations are not supported on Cisco APs in Sniffer mode.
Configure Cisco Hyperlocation globally by entering this command: config advanced hyperlocation {enable | disable}
See a summary of Cisco Hyperlocation global configuration by entering this command: show advanced hyperlocation summary
Configure Cisco Hyperlocation on a per AP group basis by entering this command: config advanced hyperlocation apgroup group-name {enable | disable}
RFID Tracking
To optimize the monitoring and location calculation of RFID tags, you can enable tracking optimization on up to four channels within the 2.4-GHz band of an 802.11b/g access point radio. This feature allows you to scan only the channels on which tags are usually programmed to operate (such as channels 1, 6, and 11).
You can use the controller GUI or CLI to configure the access point for monitor mode and to then enable tracking optimization on the access point radio.
Step 1 | Configure an access point for monitor mode by entering this command: | ||||
Step 2 | When warned that the access point will be rebooted and asked if you want to continue, enter Y. | ||||
Step 3 | Save your changes by entering this command: save config | ||||
Step 4 | Disable the access point radio by entering this command: | ||||
Step 5 | Configure the access point to scan only the DCA channels supported by its country of operation by entering this command: config ap monitor-mode tracking-opt Cisco_AP
| ||||
Step 6 | After you have entered the command in Step 5, you can enter this command to choose up to four specific 802.11b channels to be scanned by the access point: config ap monitor-mode 802.11b fast-channel Cisco_AP channel1 channel2 channel3 channel4
| ||||
Step 7 | Reenable the access point radio by entering this command: | ||||
Step 8 | Save your changes by entering this command: save config | ||||
Step 9 | See a summary of all access points in monitor mode by entering this command: |
Location Settings
The controller determines the location of client devices by gathering received signal strength indication (RSSI) measurements from access points all around the client of interest. The controller can obtain location reports from up to 16 access points for clients, RFID tags, and rogue access points.
Improve location accuracy by configuring the path loss measurement (S60) request for normal clients or calibrating clients by entering this command:
where ? is one of the following:
client {enable | disable} burst_interval—Enables or disables the path loss measurement request for normal, noncalibrating clients. The valid range for the burst_interval parameter is 1 to 3600 seconds, and the default value is 60 seconds.
calibrating {enable | disable} {uniband | multiband}—Enables or disables the path loss measurement request for calibrating clients on the associated 802.11a or 802.11b/g radio or on the associated 802.11a/b/g radio.
If a client does not send probes often or sends them only on a few channels, its location cannot be updated or cannot be updated accurately. The config location plm command forces clients to send more packets on all channels. When a CCXv4 (or higher) client associates, the controller sends it a path loss measurement request, which instructs the client to transmit on the bands and channels that the access points are on (typically, channels 1, 6, and 11 for 2.4-GHz-only access points) at a configurable interval (such as 60 seconds) indefinitely.
These four additional location CLI commands are available; however, they are set to optimal default values, so we do not recommend that you use or modify them:
Configure the RSSI timeout value for various devices by entering this command:
where? is one of the following:
client timeout—Configures the RSSI timeout value for clients. The valid range for the timeout parameter is 5 to 3600 seconds, and the default value is 5 seconds.
calibrating-client timeout—Configures the RSSI timeout value for calibrating clients. The valid range for the timeout parameter is 0 to 3600 seconds, and the default value is 5 seconds.
tags timeout—Configures the RSSI timeout value for RFID tags. The valid range for the timeout parameter is 5 to 300 seconds, and the default value is 5 seconds.
rogue-aps timeout—Configures the RSSI timeout value for rogue access points. The valid range for the timeout parameter is 5 to 3600 seconds, and the default value is 5 seconds.
Ensuring that recent, strong RSSIs are retained by the CPU is critical to location accuracy. The config location expiry command enables you to specify the length of time after which old RSSI averages expire.
Note | We recommend that you do not use or modify the config location expiry command. |
Configure the RSSI half life for various devices by entering this command:
config location rssi-half-life ?
where ? is one of the following:
client half_life—Configures the RSSI half life for clients. The valid range for the half_life parameter is 0, 1, 2, 5, 10, 20, 30, 60, 90, 120, 180, or 300 seconds, and the default value is 0 seconds.
calibrating-client half_life—Configures the RSSI half life for calibrating clients. The valid range for the half_life parameter is 0, 1, 2, 5, 10, 20, 30, 60, 90, 120, 180, or 300 seconds, and the default value is 0 seconds.
tags half_life—Configures the RSSI half life for RFID tags. The valid range for the half_life parameter is 0, 1, 2, 5, 10, 20, 30, 60, 90, 120, 180, or 300 seconds, and the default value is 0 seconds.
rogue-aps half_life—Configures the RSSI half life for rogue access points. The valid range for the half_life parameter is 0, 1, 2, 5, 10, 20, 30, 60, 90, 120, 180, or 300 seconds, and the default value is 0 seconds.
Some client devices transmit at reduced power immediately after changing channels, and RF is variable, so RSSI values might vary considerably from packet to packet. The config location rssi-half-life command increases accuracy by averaging nonuniformly arriving data using a configurable forget period (or half life).
Note | We recommend that you do not use or modify the config location rssi-half-life command. |
Configure the NMSP notification threshold for RSSI measurements by entering this command:
config location notify-threshold ?
where ? is one of the following:
client threshold—Configures the NMSP notification threshold (in dB) for clients and rogue clients. The valid range for the threshold parameter is 0 to 10 dB, and the default value is 0 dB.
tags threshold—Configures the NMSP notification threshold (in dB) for RFID tags. The valid range for the threshold parameter is 0 to 10 dB, and the default value is 0 dB.
rogue-aps threshold—Configures the NMSP notification threshold (in dB) for rogue access points. The valid range for the threshold parameter is 0 to 10 dB, and the default value is 0 dB.
Note | We recommend that you do not use or modify the config location notify-threshold command. |
Configure the algorithm used to average RSSI and signal-to-noise ratio (SNR) values by entering this command:
To view location information, use these CLI commands:
View the current location configuration values by entering this command:
See the RSSI table for a particular client by entering this command:
See the location-based RFID statistics by entering this command:
Clear the location-based RFID statistics by entering this command:
Clear a specific RFID tag or all of the RFID tags in the entire database by entering this command:
See whether location presence (S69) is supported on a client by entering this command:
When location presence is supported by a client and enabled on a location appliance, the location appliance can provide the client with its location upon request. Location presence is enabled automatically on CCXv5 clients.
The Network Mobility Services Protocol (NMSP) manages communication between the mobility services engine and the controller for incoming and outgoing traffic. If your application requires more frequent location updates, you can modify the NMSP notification interval (to a value between 1 and 180 seconds) for clients, active RFID tags, and rogue access points and clients.
Note | The TCP port (16113) that the controller and mobility services engine communicate over must be open (not blocked) on any firewall that exists between the controller and the mobility services engine for NMSP to function. |
Step 1 | Set the NMSP notification interval value for clients, RFID tags, and rogue clients and access points by entering these commands, where interval is a value between 1 and 180 seconds: |
Step 2 | See the NMSP notification intervals by entering this command: show nmsp notification interval Information similar to the following appears: NMSP Notification Interval Summary RSSI Interval: Client.......................................... 2 sec RFID............................................ 2 sec Rogue AP........................................ 2 sec Rogue Client.................................... 2 sec Spectrum Interval: Interferer device............................... 2 sec |
To view NMSP information, use these CLI commands:
See the status of active NMSP connections by entering this command:
See the NMSP counters by entering this command:
See the mobility services that are active on the controller by entering this command:
Use these commands if you experience any problems with NMSP:
Configure NMSP debug options by entering this command:
where ? is one of the following:
all {enable | disable}—Enables or disables debugging for all NMSP messages.
connection {enable | disable}—Enables or disables debugging for NMSP connection events.
detail {enable | disable}—Enables or disables debugging for NMSP detailed events.
error {enable | disable}—Enables or disables debugging for NMSP error messages.
event {enable | disable}—Enables or disables debugging for NMSP events.
message {tx | rx} {enable | disable}—Enables or disables debugging for NMSP transmit or receive messages.
packet {enable | disable}—Enables or disables debugging for NMSP packet events.
Enable or disable debugging for NMSP interface events by entering this command:
Enable or disable debugging for IAPP NMSP events by entering this command:
Enable or disable debugging for RFID NMSP messages by entering this command:
Enable or disable debugging for access point monitor NMSP events by entering this command:
Enable or disable debugging for wIPS NMSP events by entering this command:
Probe Request Forwarding
Probe requests are 802.11 management frames sent by clients to request information about the capabilities of SSIDs. By default, access points forward acknowledged probe requests to the controller for processing. Acknowledged probe requests are probe requests for SSIDs that are supported by the access point. If desired, you can configure access points to forward both acknowledged and unacknowledged probe requests to the controller. The controller can use the information from unacknowledged probe requests to improve the location accuracy.
Step 1 | Enable or disable the
filtering of probe requests forwarded from an access point to the controller by
entering this command:
config advanced probe
filter {enable |
disable}
If you enable probe filtering, the default filter setting, the access point forwards only acknowledged probe requests to the controller. If you disable probe filtering, the access point forwards both acknowledged and unacknowledged probe requests to the controller. |
Step 2 | Limit the number
of probe requests sent to the controller per client per access point radio in a
given interval by entering this command:
config advanced probe limit
num_probes
interval
The default value for num_probes is 2 probe requests, and the default value for interval is 500 milliseconds. |
Step 3 | Enter the save config command to save your changes. |
Step 4 | Configure the backoff parameters for probe queue in a Cisco AP by entering this command: config advanced probe backoff {enable | disable} |
Step 5 | See the probe
request forwarding configuration by entering this command:
Information similar to the following appears: Probe request filtering.......................... Enabled Probes fwd to controller per client per radio.... 2 Probe request rate-limiting interval.......... 500 msec |
CCX Radio Management
You can configure two parameters that affect client location calculations:
These parameters are supported in Cisco Client Extensions (CCX) v2 and later releases are designed to enhance location accuracy and timeliness for participating CCX clients.
For the location features to operate properly, the access points must be configured for normal, monitor, or FlexConnect mode. However, for FlexConnect mode, the access point must be connected to the Cisco WLC.
When you enable the radio measurements requests feature, lightweight access points issue broadcast radio measurement request messages to clients running CCXv2 or later releases. The access points transmit these messages for every SSID over each enabled radio interface at a configured interval. In the process of performing 802.11 radio measurements, CCX clients send 802.11 broadcast probe requests on all the channels specified in the measurement request. The Cisco Location Appliance uses the uplink measurements based on these requests received at the access points to quickly and accurately calculate the client location. You do not need to specify on which channels the clients are to measure. The Cisco WLC, access point, and client automatically determine which channels to use.
The radio measurement feature enables the Cisco WLC to also obtain information on the radio environment from the client’s perspective (rather than from just that of the access point). In this case, the access points issue unicast radio measurement requests to a particular CCXv4 or v5 client. The client then sends various measurement reports back to the access point and onto the Cisco WLC. These reports include information about the radio environment and data used to interpret the location of the clients. To prevent the access points and Cisco WLC from being overwhelmed by radio measurement requests and reports, only two clients per access point and up to 20 clients per Cisco WLC are supported. You can view the status of radio measurement requests for a particular access point or client as well as radio measurement reports for a particular client from the Cisco WLC CLI.
The Cisco WLC software improves the ability of the mobility services engine to accurately interpret the location of a device through a CCXv4 feature called location-based services. The Cisco WLC issues a path-loss request to a particular CCXv4 or v5 client. If the client chooses to respond, it sends a path-loss measurement report to the Cisco WLC. These reports contain the channel and transmit power of the client.
Note | Non-CCX and CCXv1 clients ignore the CCX measurement requests and do not participate in the radio measurement activity. |
For CCX clients that need to be tracked more closely (for example, when a client calibration is performed), the Cisco WLC can be configured to command the access point to send unicast measurement requests to these clients at a configured interval and whenever a CCX client roams to a new access point. These unicast requests can be sent out more often to these specific CCX clients than the broadcast measurement requests, which are sent to all clients. When location calibration is configured for non-CCX and CCXv1 clients, the clients are forced to disassociate at a specified interval to generate location measurements.
Configuring CCX Radio Management
Step 1 | Choose Wireless > 802.11a/n/ac or 802.11b/g/n > Network to open the 802.11a/n/ac (or 802.11b/g/n) Global Parameters page. | ||
Step 2 | Under CCX Location Measurement, select the Mode check box to globally enable CCX radio management. This parameter causes the access points connected to this Cisco WLC to issue broadcast radio measurement requests to clients running CCX v2 or later releases. The default value is disabled (or unselected). | ||
Step 3 | If you selected the Mode check box in the previous step, enter a value in the Interval text box to specify how often the access points are to issue the broadcast radio measurement requests. | ||
Step 4 | Click Apply. | ||
Step 5 | Click Save Configuration. | ||
Step 6 | Follow the instructions in Step 2 of the Configuring CCX Radio Management (CLI) section below to enable access point customization.
| ||
Step 7 | If desired, repeat this procedure for the other radio band (802.11a/n/ac or 802.11b/g/n). |
Step 1 | Globally enable CCX radio
management by entering this command:
config advanced {802.11a | 802.11b} ccx location-meas global enable interval_seconds The range for the interval_seconds parameter is 60 to 32400 seconds, and the default value is 60 seconds. This command causes all access points connected to this Cisco WLC in the 802.11a or 802.11b/g network to issue broadcast radio measurement requests to clients running CCXv2 or later releases. |
Step 2 | Enable access
point customization by entering these commands:
|
Step 3 | Save your settings by entering this command: save config |
To see the CCX broadcast location measurement request configuration for all access points connected to this Cisco WLC in the 802.11a or 802.11b/g network, enter this command:
To see the CCX broadcast location measurement request configuration for a particular access point in the 802.11a or 802.11b/g network, enter this command:
To see the status of radio measurement requests for a particular access point, enter this command:
show ap ccx rm Cisco_AP status
Information similar to the following appears:
A Radio Beacon Request................................. Enabled Channel Load Request........................... Enabled Frame Request.................................. Disabled Noise Histogram Request........................ Disabled Path Loss Request.............................. Disabled Interval....................................... 60 Iteration...................................... 5 B Radio Beacon Request................................. Disabled Channel Load Request........................... Enabled Frame Request.................................. Disabled Noise Histogram Request........................ Enabled Path Loss Request.............................. Disabled Interval....................................... 60 Iteration................................... 5
To see the status of radio measurement requests for a particular client, enter this command:
show client ccx rm client_mac status
Information similar to the following appears:
Client Mac Address............................... 00:40:96:ae:53:b4 Beacon Request................................... Enabled Channel Load Request............................. Disabled Frame Request.................................... Disabled Noise Histogram Request.......................... Disabled Path Loss Request................................ Disabled Interval......................................... 5 Iteration........................................ 3
To see radio measurement reports for a particular client, enter these commands:
show client ccx rm client_mac report beacon—Shows the beacon report for the specified client.
show client ccx rm client_mac report chan-load—Shows the channel-load report for the specified client.
show client ccx rm client_mac report noise-hist—Shows the noise-histogram report for the specified client.
show client ccx rm client_mac report frame—Shows the frame report for the specified client.
To see the clients configured for location calibration, enter this command:
To see the RSSI reported for both antennas on each access point that heard the client, enter this command:
Debug CCX broadcast measurement request activity by entering this command:
Debug client location calibration activity by entering this command:
debug ccxrm [all | error | warning | message | packet | detail {enable | disable}]
The CCX radio measurement report packets are encapsulated in Internet Access Point Protocol (IAPP) packets. Therefore, if the previous debug ccxrm command does not provide any debugs, enter this command to provide debugs at the IAPP level:
Debug the output for forwarded probes and their included RSSI for both antennas by entering this command:
Mobile Concierge
Mobile Concierge is a solution that enables 802.1X capable clients to interwork with external networks. The Mobile Concierge feature provides service availability information to clients and can help them to associate available networks.
The services offered by the network can be broadly classified into two protocols:
Step 1 | Choose WLAN to open the WLANs page. |
Step 2 | Hover your mouse over the blue drop-down arrow for the desired WLAN on which you want to configure the 802.11u parameters and select 802.11u. The 802.11u page appears. |
Step 3 | Select the 802.11u Status check box to enable 802.11u on the WLAN. |
Step 4 | In the 802.11u General Parameters area, do the following:
|
Step 5 | In the OUI List area, do the following: |
Step 6 | In the Domain List area, do the following: |
Step 7 | In the Realm List area, do the following: |
Step 8 | In the Cellular Network Information List area, do the following: |
Step 9 | Click Apply. |
To enable or disable 802.11u on a WLAN, enter this command:
config wlan hotspot dot11u {enable | disable} wlan-id
To add or delete information about a third generation partnership project's cellular network, enter this command:
config wlan hotspot dot11u 3gpp-info {add index mobile-country-code network-code wlan-id | delete index wlan-id}
To configure the domain name for the entity operating in the 802.11u network, enter this command:
config wlan hotspot dot11u domain {{{add | modify} wlan-id domain-index domain-name} | {delete wlan-id domain-index}}
To configure a homogenous extended service set identifier (HESSID) value for a WLAN, enter this command:
config wlan hotspot dot11u hessid hessid wlan-id
The HESSID is a 6-octet MAC address that identifies the homogeneous ESS.
To configure the IP address availability type for the IPv4 and IPv6 IP addresses on the WLAN, enter this command:
config wlan hotspot dot11u ipaddr-type ipv4-type ipv6-type wlan-id
To configure the network authentication type, enter this command:
config wlan hotspot dot11u auth-type network-auth wlan-id
To configure the Roaming Consortium OI list, enter this command:
config wlan hotspot dot11u roam-oi {{{add | modify} wlan-id oi-index oi is-beacon} | {delete wlan-id oi-index}}
To configure the 802.11u network type and internet access, enter this command:
config wlan hotspot dot11u network-type wlan-id network-type internet-access
To configure the realm for the WLAN, enter this command:
config wlan hotspot dot11u nai-realm {{{add | modify} realm-name wlan-id realm-index realm-name | {delete realm-name wlan-id realm-index}}
To configure the authentication method for the realm, enter this command:
config wlan hotspot dot11u nai-realm {add | modify} auth-method wlan-id realm-index eap-index auth-index auth-method auth-parameter
To delete the authentication method for the realm, enter this command:
config wlan hotspot dot11u nai-realm delete auth-method wlan-id realm-index eap-index auth-index
To configure the extensible authentication protocol (EAP) method for the realm, enter this command:
config wlan hotpspot dot11u nai-realm {add | modify} eap-method wlan-id realm-index eap-index eap-method
To delete the EAP method for the realm, enter this command:
config wlan hotspot dot11u nai-realm delete eap-method wlan-id realm-index eap-index
Configuring 802.11u Mobility Services Advertisement Protocol
MSAP (Mobility Services Advertisement Protocol) is designed to be used primarily by mobile devices that are configured with a set of policies for establishing network services. These services are available for devices that offer higher-layer services, or network services that are enabled through service providers.
Service advertisements use MSAP to provide services to mobile devices prior to association to a Wi-Fi access network. This information is conveyed in a service advertisement. A single-mode or dual-mode mobile device queries the network for service advertisements before association. The device's network discovery and the selection function may use the service advertisements in its decision to join the network.
Step 1 | Choose WLAN to open the WLANs page. |
Step 2 | Hover your mouse over the blue drop-down arrow for the desired WLAN on which you want to configure the MSAP parameters and select Service Advertisements. The Service Advertisement page appears. |
Step 3 | Enable the service advertisements. |
Step 4 | Enter the server index for this WLAN. The server index field uniquely identifies an MSAP server instance serving a venue that is reachable through the BSSID. |
Step 5 | Click Apply. |
To enable or disable MSAP on a WLAN, enter this command:
config wlan hotspot msap {enable | disable} wlan-id
To assign a server ID, enter this command:
config wlan hotspot msap server-id server-id wlan-id
Configuring 802.11u HotSpot
This feature, which enables IEEE 802.11 devices to interwork with external networks, is typically found in hotspots or other public networks irrespective of whether the service is subscription based or free.
The interworking service aids network discovery and selection, enabling information transfer from external networks. It provides information to the stations about the networks prior to association. Interworking not only helps users within the home, enterprise, and public access, but also assists manufacturers and operators to provide common components and services for IEEE 802.11 customers. These services are configured on a per WLAN basis on the controller.
Note | The Downstream Group-Addressed Forwarding (DGAF) bit in the Hotspot 2.0 IE will not be updated automatically until you disable and enable the WLAN. |
Step 1 | Choose WLAN to open the WLANs window. |
Step 2 | Hover your mouse over the blue drop-down arrow that corresponds to the desired WLAN on which you want to configure the HotSpot parameters and choose HotSpot. The WLAN > HotSpot 2.0 page is displayed. |
Step 3 | On the WLAN > HotSpot 2.0 window, enable HotSpot2. |
Step 4 | To set the WAN link parameters, perform the following tasks: |
Step 5 | In the
Operator Name List area, perform the following
tasks:
|
Step 6 | In the
Port Config List area, perform the following
tasks:
|
Step 7 | Click Apply. |
Note | The character '?' is not supported in the value part of the commands. |
To enable or disable HotSpot2 on a WLAN, enter this command:
config wlan hotspot hs2 {enable | disable}
To configure the operator name on a WLAN, enter this command:
config wlan hotspot hs2 operator-name {add | modify} wlan-id index operator-name lang-code
wlan-id—The WLAN ID on which you want to configure the operator-name.
index—The operator index of the operator. The range is 1 to 32.
operator-name—The name of the 802.11an operator.
Tip | Press the tab key after entering a keyword or argument to get a list of valid values for the command. |
To delete the operator name, enter this command:
config wlan hotspot hs2 operator-name delete wlan-id index
To configure the port configuration parameters, enter this command:
config wlan hotspot hs2 port-config {add | modify} wlan-id index ip-protocol port-number
To delete a port configuration, enter this command:
config wlan hotspot hs2 port-config delete wlan-id index
To configure the WAN metrics, enter this command:
config wlan hotspot hs2 wan-metrics wlan-id link-status symet-link downlink-speed uplink-speed
link-status—The link status. The valid range is 1 to 3.
symet-link—The symmetric link status. For example, you can configure the uplink and downlink to have different speeds or same speeds.
downlink-speed—The downlink speed. The maximum value is 4,194,304 kbps.
uplink-speed—The uplink speed. The maximum value is 4,194,304 kbps.
To clear all HotSpot configurations, enter this command:
config wlan hotspot clear-all wlan-id
To configure the Access Network Query Protocol (ANQP) 4-way messaging, enter this command:
config advanced hotspot anqp-4way {enable | disable | threshold value}
To configure the ANQP comeback delay value in terms of TUs, enter this command:
config advanced hotspot cmbk-delay value
To configure the gratuitous ARP (GARP) forwarding to wireless networks, enter this command:
config advanced hotspot garp {enable | disable}
To limit the number of GAS request action frames to be sent to the controller by an AP in a given interval, enter this command:
config advanced hotspot gas-limit {enable num-of-GAS-required interval | disable}
When HotSpot2 is configured, the access points that are part of the network must be configured to support HotSpot2.
Step 1 | Click Wireless > All APs to open the All APs page. |
Step 2 | Click the AP Name link to configure the HotSpot parameters on the desired access point. The AP Details page appears. |
Step 3 | Under the General Tab, configure the following parameters:
|
Step 4 | Click Apply. |
config ap venue add venue-name venue-group venue-type lang-code ap-name–Adds the venue details to the access point indicating support for HotSpot2.
venue-name—Name of the venue where this access point is located.
venue-type—Type of the venue. Depending on the venue-group chosen, select the venue type. See the following table.
lang-code—The language used. An ISO-14962-1997 encoded string defining the language. This is a three character language code. Enter the first three letters of the language in English (For example: eng for English)
Tip | Press the tab key after entering a keyword or argument to get a list of valid values for the command. |
config ap venue delete ap-name—Deletes the venue related information from the access point.
You can configure unique icons of the service providers to be displayed on the client devices. You can download these icon files to the Cisco WLC for the icon files to be sent through a gas message and displayed on the client devices. This feature enhances the user interface on the client devices wherein users can differentiate between service providers based on the icons displayed.