Brocade Mobility RFS Controller CLI Reference Guide (Supporting software release 5.5.0.0 and later) - Manual (Page 1313)

Brocade Mobility RFS Controller CLI Reference Guide 1305
53-1003098-01
Chapter
28
PASSPOINT POLICY
There has been an exponential increase in the number and types of Wi-Fi mobile devices being
used globally, resulting in a phenomenal growth in the data traffic volume. Consequently, the
demand for secure, quick, and unlicensed access to public Wi-Fi hotspots, capable of handling this
sudden influx of mobile data traffic, has been increasing. However, public hotspots have certain
intrinsic usability issues, such as network discovery and selection, traffic prioritization, roaming
capabilities, user authentication etc. The IEEE 802.11u standards (includes Hotspot 2.0 protocol
extensions) were introduced to address these issues.
Hotspot 2.0 is a Wi-Fi Alliance standard that enables interoperability between clients,
infrastructure, and operators. It makes a portion of the IEEE 802.11u standard mandatory and
adds Hotspot 2.0 extensions that allow clients to query a network before actually attempting to join
it. For example, you are using a laptop at an airport and have a list of SSIDs to select from. You will
have to first identify the SSID you have the credentials for and then connect to the network. This
can be time consuming. In such a scenario, a Hotspot 2.0 enabled device would present only those
SSIDs for which you possess credentials. In short Hotspot 2.0 allows devices to query a network for
configuration details, such as WAN metrics, network type, hotspot service provider details, and
domain names without actually connecting to the network.
Hotspot 2.0 enabled clients can identify a Hotspot 2.0 capable access point (AP) from the new
elements present in the APs beacon/probe messages. Having ascertained that an AP is Hotspot
2.0 capable, the client uses action frames to send an Access Network Query Protocol (ANQP) query
inside a Generic Advertisement Service (GAS) request. The AP responds with an action frame
containing an ANQP response within a GAS response. Based on this response the mobile device
determines the type of credentials needed to log on to the AP.
The Brocade Mobility 5.5 Wi-Fi Alliance implementation defines a passpoint policy that allows a
single or a set of Hotspot 2.0 configuration to be global and referenced by the devices that use it.
This policy is applied to APs to make them Hotspot 2.0 Wi-Fi Alliance compliant. The passpoint
policy is mapped to a WLAN. However, only primary WLANs on a BSSID will have their passpoint
policy configuration used. For more information, see
“use” on page 355.
To migrate to the passpoint policy configuration mode, use the following command:
<DEVICE>(config)#passpoint-policy <POLICY-NAME>
rfs4000-229D58(config)#passpoint-policy test
rfs4000-229D58(config-passpoint-policy-test)#
rfs4000-229D58(config-passpoint-policy-test)#?
Passpoint Policy Mode commands:
3gpp Configure a 3gpp plmn (public land mobile network) id
access-network-type Set the access network type for the hotspot
connection-capability Configure the connection capability for the hotspot
domain-name Add a domain-name for the hotspot
hessid Set a homogeneous ESSID value for the hotspot
internet Advertise the hotspot having internet access
ip-address-type Configure the advertised ip-address-type
nai-realm Configure a NAI realm for the hotspot
net-auth-type Add a network authentication type to the hotspot