HK1198853B - Discovering network information available via wireless networks - Google Patents

Description

Discovering network information available via a wireless network

Cross Reference to Related Applications

This application claims benefit and priority from U.S. patent application No.13/234,799 filed on 16/9/2011.

The contents of the above-mentioned patent application are hereby expressly incorporated by reference into the detailed description thereof.

Background

Wireless network deployments, such as wireless local area networks ("WLANs"), allow wireless terminals to access networks and internet services when in the vicinity of wireless communication signals of these wireless networks. Different networks provide different network information to the wireless client. Such network information may include access to a particular subscription service provider ("SSP") network ("SSPN"), roaming agreements to allow connections from wireless clients associated with different SSPs, authentication capabilities to enable secure communications, support for emergency services, support for particular types of multimedia access (e.g., audio and/or video streaming, downloading, etc.), or support for other types of network services. However, network information may only be provided when connected or associated with the network. Depending on the received network information, the device may need to disconnect or disassociate from the network and pursue a different network.

Drawings

FIG. 1 illustrates a communication network;

FIG. 2 illustrates a communication layer architecture;

FIG. 3 illustrates an alternative communication network;

FIG. 4 illustrates network information;

FIG. 5 illustrates a wireless terminal;

fig. 6 shows an access point;

FIG. 7 shows a table of IEEE802.11 ANQP information identifiers;

FIG. 8 shows a table of hotspot ANQP element subtype definitions; and

fig. 9 illustrates network communications.

Detailed Description

The disclosed systems and methods retrieve discovery information related to a network prior to associating with the network. The pre-association communication may be retrieved through a wireless protocol (e.g., access network query protocol ("ANQP")) that allows the wireless device to retrieve information related to the network before associating with the network. Communication prior to network association may be referred to as discovery communication or communication in a pre-association state. ANQP may allow a device to retrieve additional network information before network capabilities are established (i.e., before any authentication parameters are exchanged between the device and the network and before an identified session is established between the device and the network). Additional network information that may be discovered prior to network association includes, for example, network latency, cellular capabilities, hotspot capabilities, mobility capabilities, neighbor reports, station identification, and multiple hotspot session identification, as well as other similar parameters that provide network information. Network information that may be discovered prior to network association is further described with respect to fig. 4.

The wireless devices that communicate prior to network association may include mobile communication devices, mobile computing devices, or any other device capable of wireless communication with a wireless network. These devices may be referred to as terminals, wireless terminals, stations ("STAs"), or user equipment, and may also include mobile smart phones (e.g.,smart phone orTablet), wireless personal digital assistant ("PDA"), machine-to-machine device, device in a smart grid ("SmartGrid"), device in a mesh network (ad hoc or peer-to-peer), laptop/notebook/netbook computer with wireless adapter, etc.

Some devices may discover information related to external networks, such as a subscription service provider network ("SSPN"), which may include a wireless local area network ("WLAN"). Network discovery and connectivity in a WLAN may be facilitated by defining standards for access, control, and communication in the network (e.g., referred to asThe communications standard of 802.11 (institute of electrical and electronics engineers), which specifies among other things a revision entitled "interacting with external networks"). Alternatively, network discovery and connection may be compliant with other portions of the IEEE802.11 standard as well as other wireless communication standards, including the WLAN standard (which includes any802.xx standards (e.g., IEEE 802.15, IEEE 802.16, IEEE802.19, IEEE 802.20, and IEEE 802.22)), personal area network standards, and,A wide area network standard or a cellular communication standard.

One network shown below is a WLAN. Alternatively, devices may discover information related to other networks through other protocols and architectures, including cellular telephone networks or WiMax networks. The network may include a publicly accessible network (e.g., the internet), a private network (e.g., an intranet), or a combination thereof, and may use a variety of networking protocols now available or developed in the future, including but not limited to: TCP/IP based networking protocols. The network may include any communication method or use any form of machine-readable media for communicating information from one device to another.

Discovery of network information may be performed in many environments that provide WLAN access for network connections or in WLAN access locations or environments where one or more users that may be expected to carry respective wireless terminals will associate with (i.e., join or connect to) and disassociate with a wireless network, access point, or WLAN as they enter or leave the WLAN access location or environment. Some WLAN locations or environments may be referred to as "hotspots" with respect to locations or environments within communication range of WLAN signals. The WLAN locations or environments may include cafes, retail stores, residential locations (e.g., homes and apartments), educational facilities, office environments, airports, mass transit stations and vehicles, hotels, and the like. These WLANs are typically implemented as access networks that provide access to publicly accessible networks and may be associated with or support access to external networks (or WLAN-supported networks) owned and/or operated by subscription-based service providers. For example, an internet access service provider or telecommunications carrier/service provider that provides subscription-based internet access for a fee (e.g., a monthly fee) may own and/or operate an external network. In some systems, when a subscriber/user subscribed to the service is in communication proximity of the WLAN with a suitable wireless terminal, the subscriber may use wireless network access and/or internet access services based on the subscription. In some instances, different WLANs may provide access to different types of network information. For example, some WLANs may provide access to a particular subscription service provider network, and some WLANs may support roaming agreements to allow connections from wireless terminals associated with different SSPs.

During some network discovery procedures, a wireless terminal may send a query for specific network information from a wireless local area network ("WLAN"). The terminal may obtain network information made available by the WLAN to determine whether to continue a connection procedure for associating with the network based on the network information. According to embodiments described herein, the wireless terminal may request network information from the WLAN using access network query protocol ("ANQP"). ANQP supports information retrieval from advertisement servers that support generic advertisement services ("GAS"). ANQP and GAS are defined in802.11u^TMThe entire disclosure of which is incorporated by reference.

For advertising agreements, a Generic Advertisement Service ("GAS") may be used as the transport medium at layer 2 (see fig. 2). The advertisement protocol may connect the wireless terminal to one of a plurality of interaction servers. The advertisement protocol allows frames to be transmitted between the wireless terminal device and a server in the network prior to network connection. For example, the GAS provides support for network selection by the wireless terminal and for communication between the wireless terminal and other information resources in the network before the wireless terminal associates with the WLAN. The wireless terminal may connect to the layer 2 radio service without exchanging any authentication parameters or without having an identified session (because no session key is established and no internet protocol address is assigned). When the IEEE802.11 standard is followed, no data traffic is allowed in this state.

Other layer 2 transport mechanisms or even authentication mechanisms may be used. For example, extensible authentication protocol ("EAP") may be used for the transport advertisement protocol. The advertisement protocol information will be encapsulated in an appropriate EAP-TLV (type length value) method frame (or alternative EAP method frame) and transported over EAP. Using the security credentials exchanged during the EAP transaction will also provide a level of security for any information carried in the advertisement protocol. For example, if EAP-SIM (or EAP-AKA) becomes the authentication protocol, any advertising protocol information encapsulated (i.e., securely carried) in the appropriate EAP-TLV frame during the same EAP transaction may also be protected by the SIM credentials.

The access network query protocol ("ANQP") is an advertisement protocol and serves as a query and response protocol used by the wireless terminal to discover a range of information from a server, including the availability of accessible roaming partner internet protocol address types and other metadata useful in the network selection process of the wireless terminal. ANQP is able to discover information about hotspots or wireless networks before a wireless terminal establishes a network connection and associates with the network. Alternatively or additionally, other than inIn addition to the definition in 802.11u, additional ANQP messages may be defined in the Wi-Fi alliance ("WFA") hotspot 2.0 specification. These ANQP extensions in the WFA hotspot 2.0 specification may be referred to as hotspot ("HS") 2.0ANQP elements. Alternatively, other advertisement protocols may be used (e.g., inThe registered location query protocol "RLQP" defined in 802.11 af). ANQP provides one embodiment for communicating with a WLAN during a discovery phase without associating with the network. Network information transmitted prior to network association (or during a discovery phase) is discussed below. In alternative embodiments, other layer 2 transport mechanisms or even authentication mechanisms such as Extensible Authentication Protocol (EAP) may be used to carry the ANQP messages. The ANQP message will be encapsulated in a suitable EAP-TLV method frame (or alternative EAP method frame) and transported over EAP.

The network discovery exchange may involve requesting the wireless terminal to query another wireless terminal (e.g., a WLAN access point ("AP")) for network information. A WLAN AP (also referred to simply as an AP) is an entity that contains one station and provides access to distribution services for the associated station via the wireless medium. The queried or receiving terminal (e.g., AP) may respond to the received query with the requested information in a response. The queried or receiving terminal may provide the response information in a query to a server proxy (proxying) in an external network (e.g., a subscription service provider ("SSP") network) or without a query to a server proxy in an external network (e.g., a subscription service provider ("SSP") network). For example, an external network connected to the queried WLAN may have certain network information that is accessible via the WLAN and that may be made known to the querying wireless terminal. The network discovery exchange or communication prior to network association may use ANQP or other query protocols as well, just as information exchange services may be used instead.

Fig. 1 shows a communication network 100. Network information may be communicated over communication network 100 during network discovery using ANQP. Communication network 100 includes a plurality of WLAN access locations 102a-c having respective access points ("APs") 104a-c that provide access to respective access networks 106 a-c. The AP104a-c is further described with respect to fig. 6. Access network a 106a provides access to external network a 108a and access network B106B provides access to external network B108B. Unlike access networks a 106a and B106B, which are not directly connected to the internet 112, access network C106C may be directly connected to a publicly accessible network such as the internet. Thus, access network C106C may be a public network, while access networks a 106a and B106B may be private networks.

In one embodiment, each of external networks a 108a and B108B may be a subscription service provider network ("SSPN") owned or operated by a data subscription service provider, an internet subscription service provider, a media (e.g., audio/video) subscription service provider, a wireless communication subscription service provider, or any combination thereof. External networks a 108a and B108B may be connected to the internet 112 and may, for example, provide subscription-based internet access to wireless terminal devices. In some implementations, roaming agreements between different subscription service providers may enable external networks a 108a and B108B to support roaming connections for wireless terminals associated with other subscription service providers.

The WLAN access location 102a shows a wireless terminal 114 within wireless range of an access point ("AP") 104 a. The wireless terminal 114 is further described with respect to fig. 5. The AP104a is connected to an access network a 106a, and the access network a 106a may provide direct or indirect connectivity to other networks, including publicly accessible networks such as the internet 112. Before the wireless terminal 114 associates with access network a 106a, the wireless terminal 114 sends a discovery request 116 to the AP104 a. The AP104a may respond with a discovery response 118. In alternative embodiments, the discovery request 116 may originate from the AP104a and the discovery response 118 may originate from the wireless terminal 114, for example, through a mesh network, a peer-to-peer network, an ad-hoc network, or a Wi-Fi direct network. The discovery request 116 or discovery response 118 may include network information 120. The network information 120 (also referred to as discovery information, network discovery information, or discovery communications) may include network and/or device related information that is communicated between the device and the network prior to the device associating with the network. In one embodiment, the network information 120 may be transmitted using ANQP protocol. The network information 120 that may be discovered is further described with respect to fig. 4.

Discovery communications (request 116 and response 118) may be exchanged at the media access control ("MAC") sublayer of the data link layer of the open systems interconnection ("OSI") reference model while discovering network information 120 without using operations at or above the internet protocol ("IP") layer (i.e., the network layer) and without otherwise providing access to the IP layer. Using information exchanged at or over the network layer to discover network information may require more processing power of the wireless terminal than performing processing at the MAC sublayer. The layers in which discovery communications operate are further illustrated in fig. 2.

Each of the APs 104a-c and the wireless terminals 114 may include a network adapter or network interface card that facilitates connection with a wireless medium. The network interface components may be referred to as stations ("STAs"). Each of the access networks 106a-c and the external networks 108a-b may be associated with and/or provide access to different network information. The network information may include discovery information provided by the network prior to associating with the network. The network information may be set by the respective owners or operators of the networks 106a-c, 108a, and 108b based on different factors (e.g., subscription usage plans, desired security levels, business objectives, roaming agreements, supported emergency services, supported multimedia access, available internet access, etc.).

The wireless terminal 114 may associate with different APs (e.g., APs 104a-c) based at least in part on the received network information 120 relating to available external networks. The wireless terminal 114 may receive information from the APs as it moves within range of one of the WLAN access locations 102a-c, respectively. The wireless terminal 114 may dynamically discover network information available at any of the WLAN access locations 102a-c and may process this information when selecting whether to associate with one of the APs 104 a-c.

Fig. 2 illustrates a communication layer architecture 200. The communication layer architecture 200 includes seven layers, which may be implemented according to the open systems interconnection ("OSI") reference model. The communication layer architecture 200 includes a data link layer 202, the data link layer 202 including a medium access control ("MAC") sublayer 204. A wireless end device (e.g., wireless terminal 114 of fig. 1) may provide network information or discovery communications 120 (e.g., discovery request 116 and discovery response 118) with a wireless access point (e.g., wireless access points 102a-c of fig. 1) at the MAC sublayer 204. The wireless terminal device may access information from the memory or other hardware of the wireless terminal at the MAC sublayer 204 without having to perform operations at or above an internet protocol layer (e.g., the network layer 208) and without having to provide access to the internet protocol layer. Mobile wireless terminal devices (e.g., wireless terminal 114 of fig. 1) including mobile smart phones, PDAs, processor-based devices, etc., may have relatively limited processor cycles and less available power than fixed location computing devices powered using a wired (e.g., alternating current) power source. Low level resource operations at the MAC sublayer require relatively less system resources than user interface-intensive and operating system-intensive operations (e.g., web browser operations) at the application layer.

Using the MAC sublayer to discover network information available via the access point may be used to identify a suitable connection between the wireless terminal and the access point. The connection may occur without user involvement or with minimal user involvement. The network information 120 may indicate whether it is appropriate to associate with a particular network (e.g., SSPN). For example, the network information 120 may include WLAN latency information. The wireless terminal 114 may require minimal delay before associating with a particular network. Making this determination prior to associating with the network may significantly reduce or eliminate user frustration because the user will not need to engage in any attempt to associate with or connect to a particular access point when the access point or network does not meet the particular network capability requirements of the wireless terminal 114, thereby significantly enhancing the user experience. Communicating such attributes or characteristics prior to a persistent or discontinuous network connection may increase network bandwidth while reducing user frustration. In the case where fewer users attempt to connect (e.g., session access), network throughput may increase for those users served by the network. Further, those users who cannot maintain or maintain a connection may avoid the challenges of initiating or establishing such a connection.

Some communication or authentication techniques using hypertext transfer protocol ("HTTP") or other internet protocol procedures may require a connection to be established between a wireless terminal and a wireless access point at one or more of the following layers: a network layer 208 and an application layer 210 of the communication layer architecture 200. In these applications, the discovery communication 120 may not require a connection to or access of the network layer 208 or any layer in the protocol stack. The inclusion of the discovery communication 120 on the MAC sublayer 204 may allow wireless terminals to communicate with a network without associating with the network.

Fig. 3 shows a communication network 300. AP104a provides WLAN access network 1102 a, and WLAN access network 1102 a overlaps with WLAN access network 2102 b having AP104 b. In this figure, the wireless terminal 114 is physically within range of both WLAN access networks 102a, 102 b. The wireless terminal 114 may communicate with the WLAN access networks 102a, 102b and may receive network discovery information 120 from both networks without associating with either network. In other words, the wireless terminal 114 may receive the network discovery information 120 while in the pre-association state. As described below with respect to element 404 of fig. 4, the network discovery information 120 may include a neighbor report that includes information related to multiple networks, and thus the wireless terminal 114 in fig. 3 may receive information related to both access networks 102a, 102b from only one of the access networks 102a, 102 b.

Fig. 4 shows network information 120. The network information 120 may include or be referred to as discovery communications 120 because the transmitted network information 120 may be prior to associating with the network (i.e., while discovering the network). Access network query protocol ("ANQP") allows a wireless device or WLAN terminal (e.g., station ("STA")) to request additional network information before establishing a network connection. ANQP may use the general advertisement service protocol as a transport mechanism for these queries. The network information 120 obtained by ANQP may include: roaming relationships, network services, supported security methods (e.g., IEEE 802.1X and web-based authentication), emergency services capabilities, available subscription service providers, etc. FIG. 4 illustrates supplementing an existing oneAdditional or optional network information 120 of the 802.11 or WFA hotspot 2.0 wireless communication standard.

WAN latency

A wide area network ("WAN") delay 402 is one example of network information 120 provided in network communications prior to association with a network. A wireless terminal (e.g., wireless terminal 114) may not be able to associate with a network (e.g., WAN)A delay in the network is determined. WAN delay 402 provides a mechanism for a wireless terminal to identify the current and/or average delay period, static or dynamic, of a particular network before selecting whether to associate with that network. For mobile device wireless terminals, customers may desire high levels of service on a particular network (e.g., a cellular network) and may not wish to associate with a WAN with high latency. In thatA WLAN access location (or WLAN hotspot) operating under the 802.11 standard or under the WFA hotspot 2.0 wireless communication standard may not be able to receive WAN latency details related to the networks supported by the WLAN (e.g., external networks) prior to network association.

The WAN delay 402 or access delay may include the round trip delay time of the current network. The access point may measure the round trip time to obtain a measure of access delay, which may be independent of device-specific connection conditions (e.g., radio connections). WAN latency 402 may be a recent measurement that provides information about the current loading of a hotspot from an access point and network conditions after the hotspot is seen, for example, from the perspective of a WLAN terminal. WAN delay 402 may be communicated in IEEE802.11 and/or WFA hotspot 2.0 standards. In one embodiment, WAN delay 402 may be implemented in at least three ways: 1) WAN delay 402 may be a new IEEE802.11 ANQP element; 2) WAN latency may be new WFA hotspot 2.0 element; or 3) may include the WAN delay 402 by modifying an existing WFA hotspot 2.0WAN metrics element. These three implementations will be described below.

In a first example, the WAN delay 402 may be a new IEEE802.11 ANQP element. WAN delay 402 may include a round trip timing value from the access point to the network, which in one embodiment corresponds to a current value and an average value of the access delay. Table 1 shows how WAN latency 402 may be organized and transmitted. Alternative data, lengths or fields may be used.

Table 1: IEEE802.11 ANQP WAN delay information format.

The information identification ("information ID") field may be an identifier used in the IEEE802.11 ANQP information identifier definition. A table showing the network information 120 and the corresponding information ID is shown in fig. 7. The length field may be a 2 octet field which is equal to 2 or 4 depending on whether the WAN average delay field is present. The WAN current delay field may be a 2 octet field having a current round trip time value, which in one example indicates the network access delay measured in milliseconds. The round trip time may be measured using a suitable protocol such as a ping message or using an acknowledgement flag ("ACK") in a Transmission Control Protocol (TCP) message or using a hypertext protocol ("HTTP") send/get message. The WAN average delay field may be a 2 octet field having an average round trip time value averaged over a recent time period (e.g., the last minute), which in one example indicates the network access delay measured in milliseconds.

In a second example, WAN delay 402 may be a new WFA hotspot 2.0 element. As described herein, a WFA hotspot, WFA hotspot 2.0, or hotspot may refer to a Wi-Fi alliance hotspot or Wi-Fi alliance hotspot 2.0 specification. The new element in the WFA hotspot for WAN delay 402 may include a round trip timing value from the access point to the network, which corresponds to the current and average values of the access delay. In one embodiment, the format of the WAN delay element is shown in table 2:

table 2: WFA hotspot WAN delay element format.

The WAN current delay field may be a 2 octet field having a current round trip time value, which in one example indicates the network access delay measured in milliseconds. The round trip time may be measured using a suitable protocol such as a ping message or using an acknowledgement flag ("ACK") in a Transmission Control Protocol (TCP) message or using a hypertext protocol ("HTTP") send/get message. The WAN average delay field may be a 2 octet field having an average round trip time value averaged over a recent time period (e.g., the last minute), which in one example indicates the network access delay measured in milliseconds.

In a third example, WAN latency 402 may be included by modifying an existing WFA hotspot WAN metrics element. The WFA hotspot specification defines a WAN metrics element that may be modified to include the WAN latency 402 information discussed above. An existing hotspot ("HS") WAN measure element may be modified to include a WAN current delay element and to include a WAN measure element, as shown in table 3.

Table 3: modified WFA hotspot WAN measure element.

The ANQP protocol may also operate in reverse communication such that the access point may receive network information 120 (e.g., WAN delay 402) from the wireless terminal. For example, when the wireless terminal has been connected to an external network (e.g., connected to the wireless service provider's network via a cellular data link, etc.)Link to personal area network, etc.), the access point may be configured to discover network information 120 (e.g., WAN latency 402) associated with the external network by querying the wireless terminal. One example would be to use the described techniques. The described communication may also be used in conjunction with a mesh networking environment, a peer-to-peer network, or a Wi-Fi direct network to enable a first wireless terminal to discover network information 120 (e.g., WAN latency 402) by querying a second wireless terminal. Thus, if the associated network information 120 is deemed acceptableThe first wireless terminal may then connect to an external network associated with the second wireless terminal.

Neighbor AP reporting

A neighboring access point ("AP") report 404 is another example of network information 120 provided in a network discovery communication. The neighboring AP report 404 may inform the wireless terminal of the neighboring access points. In particular, the neighbor AP report 404 may be used to inform the wireless terminal of neighbor access points that are members of a basic service set ("BSS") or extended service set ("ESS") requested in a neighbor report request, where existing IEEE802.11 establishes neighbor report elements. Specifically, IEEE802.11 § 8.4.2.39 (draft P802.11-REVmb/D9.2, 7/2011) defines neighbor report elements and is incorporated herein by reference. Details or information from the neighbor report element may be transmitted as a neighbor AP report 404 during network discovery prior to associating with the network. The neighbor AP report 404 may be sent by an access point to provide information to the wireless terminal regarding not only the access point but also neighboring access points without the wireless terminal associating with the access point. The neighboring AP report 404 may also be for stations ("STAs") that are not access points such as mesh devices, peer devices, ad hoc devices, or Wi-Fi direct devices. The neighbor AP report 404 may be used by the wireless terminal to identify which access point or network to associate with.

A neighbor report request/response is sent to the access point, which returns a neighbor report containing information about known neighboring access points available to the wireless terminal. An access point may receive information about neighboring access points in measurements received from a basic service set ("BSS") or extended service set ("ESS"). In particular, the neighbor report may include information about access points that may be used as candidates for BSS transition. The neighbor AP report 404 may be provided prior to associating with a particular access point. During network discovery, a device may receive neighbor reports related to neighboring access points without associating with a particular access point.

The neighboring AP report 404 may include a timestamp field to provide an indication of when the neighbor report was compiled. Some information about the area where the neighbor is located may be included in the neighbor AP report 404. The geographic information may indicate whether the neighbor is a local hotspot, a local area network (e.g., 100 meters radius), or wider. This value may be included as a radius or coverage field in the neighbor AP report 404.

In one embodiment, the neighbor AP reporting 404 may be implemented in at least three ways: 1) the neighbor AP report 404 may be a first new IEEE802.11 ANQP element; 2) the neighbor AP report 404 may be a second new IEEE802.11 ANQP element; or 3) the neighboring AP report 404 may be a new WFA hotspot element. These three exemplary implementations will be described below. Additional embodiments may include different implementations.

In a first example, the neighboring AP report 404 may be a first new IEEE802.11 ANQP element. In one embodiment, the neighbor AP report 404 may be embodied with neighbor report elements as defined in IEEE 802.118.4.2.39, wherein the entire contents of 8.4.2.39 is incorporated herein by reference. However, the neighbor AP report 404 is provided during network discovery prior to network association or in a pre-association state. The format of the neighboring AP report 404 may include an information identification ("info ID") field that may correspond to the neighboring AP report 404 element. The information ID field may be an identification of a particular element in the IEEE802.11 specification. In one embodiment, fig. 7 shows the values of the information ID including the information ID of the neighboring AP report 404. Alternatively, the length of the neighbor report element may be variable. The length of the neighbor report element may also be set to its own element or variable. The length may vary depending on the number of neighboring access points included in the report. The neighbor report element may include "element ID" and "length" fields. In the case of the extended format, "information ID", "length", "element ID", and "length" may result in two octets of redundant data. Thus, in this example, the format may be simplified for efficiency, such that an exemplary format of the neighboring AP report 404 is:

table 4: IEEE802.11 ANQP neighbor AP report Format 1

In a second example, the neighboring AP report 404 may be a first new IEEE802.11 ANQP element. In this example, subfields from neighbor report elements as shown and described in § 8.4.2.39 (draft P802.11-REVmb/D9.2, 7/2011) in the IEEE802.11 specification may be used to avoid duplication of header fields. As defined in the IEEE802.11 specification, neighbor report elements include an information identifier, a length, a basic service set identifier ("BSSID"), BSSID information, an operation category, a channel number, a physical layer, and optional sub-elements.

Table 5: IEEE802.11 ANQP neighbor AP report Format 2

The BSSID is an identifier of the particular basic service set ("BSS") being reported. The other elements of table 5 relate to this particular BSS. The BSSID information field may be used to determine neighbor service set transition candidates.

In one embodiment, the BSSID information field includes access point reachability, security, key range, capability, mobility domain, and high throughput as its defined subfields in the IEEE802.11 specification. The reachability field indicates whether the wireless device or terminal requesting the neighbor report can reach the access point identified by the BSSID. Security may be to indicate whether the access point identified by the BSSID supports the same security provisioning as the security provisioning (provisioning) used by the wireless device in its current association. In an alternative embodiment, security may be a more detailed identification of the type of security used by the access point identified by the BSSID because the neighbor AP report 404 is sent prior to connecting with the network. The key range may indicate authentication and the capabilities may refer to selected capabilities that may be used with the access point.

Referring to table 5, the operation category may indicate a channel set of the access point indicated by the BSSID. The operation category in combination with the number of channels specifies the channel frequency and spacing of the access point indicated by the BSSID. The physical layer ("PHY") type field indicates the physical layer type of the access point indicated by the BSSID. Optional sub-elements are described and illustrated in tables 8-114 of § 8.4.2.39 of the IEEE802.11 specification (draft P802.11-REVmb/D9.2, 7/2011).

In a third example, the neighboring AP report 404 may be a new WFA hotspot element. New elements may be included in the WFA hotspot wireless communication standard. A WFA hotspot or hotspot may refer to a Wi-Fi alliance hotspot or Wi-Fi alliance hotspot 2.0 specification. The new elements in the WFA hotspot of the neighboring AP report 404 may include neighbor report elements discussed above in the other two examples. The format of the neighbor AP report 404 may be as shown in table 6:

table 6: WFA hotspot neighboring AP report format

Hotspot capability

Hotspot capability 406 is another example of network information 120 provided in a network discovery communication. The hotspot capability 406 information may be used to inform the wireless device of particular aspects of WFA hotspot 2.0 capabilities supported by a particular access point or hotspot. A WFA hotspot or hotspot may refer to a Wi-Fi alliance hotspot or Wi-Fi alliance hotspot 2.0 specification. The hotspot 2.0 specification includes a feature set that may or may not be usable for a particular hotspot. Features available in a particular hotspot from the hotspot 2.0 specification are included in the hotspot capability 406 information, which is returned by the hotspot during discovery and prior to association of the device with the hotspot 406. Compliance with hotspot 2.0 specifications and inclusion of particular features may be used to determine whether a wireless device should associate with a particular network. Thus, the hotspot capabilities 406 may be communicated during network discovery (e.g., using ANQP) prior to associating with the network. Hotspot capability 406 may be considered an advertisement for a particular hotspot to advertise which features it supports, which may make it a more desirable network to associate with than other networks that do not support the same features.

Specifically, the included elements with hotspot capabilities 406 are listed in table 9 below and may include:

security initial authentication (also referred to as online registration ("OSU")) capabilities can include a system in which mobile devices that do not have a previous relationship with a service provider can securely establish a relationship. The user may select the service provider to register with by selecting a friendly name or icon. It is part of the WFA hotspot 2.0 specification.

Subscription provisioning may include the credential mechanisms required to associate with the network and associated metadata. It may include information entered by the user or the presence of a SIM card. The pre-configuration may include the configuration of the device and include enabling and disabling features.

Policy pre-configuration may refer to the policies used by the device or network.

Open Mobile alliance ("OMA")/simple object Access protocol ("SOAP")

Extensible markup language ("XML") is a protocol for exchanging information in a network.

Managed objects may refer to managed network resources. For example, operation, administration, maintenance and provisioning application protocols may be used to manage resources in a telecommunications environment.

Open mobile alliance ("OMA") device management is a protocol for managing mobile devices, including support for provisioning, configuration, upgrade, and default management.

In one embodiment, hotspot capability 406 may be implemented in at least two ways: 1) hotspot capability 406 may be a new IEEE802.11 ANQP element; and 2) hotspot capability 406 may be a new WFA hotspot element. These two exemplary implementations will be described below. Additional embodiments may include different implementations.

In a first example, the hotspot capability 406 may be a new IEEE802.11 ANQP element. The new elements may include capabilities as part of the WFA hotspot 2.0 specification. Hotspot capabilities 406 may include a list of potential capabilities (e.g., online registration, subscription provisioning, policy provisioning, or XML protocol as discussed above). The information identification ("information ID") field may be an identifier used in the IEEE802.11 ANQP specification. A table showing exemplary network information 120 (including hotspot capabilities 406 and corresponding information IDs) is shown in fig. 7. The length may correspond to the length of the optional hotspot capability subfield. In one embodiment, the length may reflect the number of hotspot capability subfields present.

Table 7 shows one embodiment of the hotspot capability 406 element:

table 7: IEEE802.11 ANQP hotspot capability format

In one implementation, the format of each of the hotspot capability subfields includes a capability identifier and a capability version. In other words, each of the hotspot capability fields of table 7 includes an Identifier (ID) and a capability version. In one example, the format of the hotspot capability subfield is as shown in table 8.

Table 8: IEEE802.11 ANQP hotspot capability subfield format

The hotspot capability ID may include the following exemplary identifiers as shown in table 9:

entity name	Value of
		Reserved	0
Open Mobile alliance device management (OMA DM)	1
		Simple object access protocol-extensible markup language (SOAP-XML)	2
Security initial authentication/Online registration (OSU)	3
		Subscription provisioning	4
Policy pre-configuration	5
		Managed Object (MO)	6
User acceptance of terms and conditions	7
		Credential enrollment protocol	8

Table 9: hotspot capability Identifier (ID)

In alternative embodiments, there may be additional, fewer, or different hotspot capabilities included as part of hotspot capability 406.

The hotspot capability version may be a 16-octet field containing a value for the version number of the hotspot capability, e.g., "1.0.5". This provides an indication of which version is supported in the network. In an alternative embodiment, the hotspot capability version field may not be present.

In a second example, the hotspot capability 406 may be a new WFA hotspot element. New elements may be included in the WFA hotspot wireless communication standard. As described herein, a WFA hotspot may refer to a Wi-Fi alliance hotspot or a Wi-Fi alliance hotspot 2.0 specification. The new elements in the WFA hotspot for hotspot capability 406 may include hotspot capabilities as discussed above. In one embodiment, the format of the hotspot capability 406 is shown in table 10:

table 10: WFA hotspot capability format

The hot spot capability subfield may be similar to the hot spot capability subfield shown in table 8.

3GPP capabilities

Third generation partnership project ("3 GPP") capabilities 408 are another example of network information 120 provided in network discovery communications. The 3GPP is a group of carriers that create and maintain standards (e.g., third generation mobile telephone system specifications). The 3GPP may include additional standards and specifications for maintenance, such as global system for mobile communications ("GSM") and IP multimedia subsystem ("IMS").

Certain elements related to 3GPP may benefit a wireless device before the wireless device associates with a particular network. In particular, the 3GPP capabilities 408 transmitted prior to the network connection may include information regarding which 3GPP capabilities the network has. The 3GPP capabilities 408 may be used by the wireless device to determine which capabilities are supported by a particular network, which may be useful for selecting which network to associate with. The 3GPP capabilities 408 are included as part of the network information 120 that the wireless device can obtain from the access point without associating with the network. Some networks may not be able to connect to the 3GPP network, in which case the access point may respond to the request for 3GPP capabilities with an error value or null value.

Exemplary 3GPP capabilities include: 1) access network discovery and selection function ("ANDSF") support; 2) IP multimedia subsystem ("IMS") support; and/or 3) generic access network ("GAN") support. In other words, in one embodiment, the 3GPP capabilities 408 may include an indication as to whether the network has support for ANDSF, IMS, or GAN. ANDSF support may generally relate to whether a device may discover a non-3 GPP access network that may be used for data communications. In one example, ANDSF support may allow a wireless device or terminal to discover the cost of connecting to a WLAN network or cellular network (e.g., a T mobile or AT & T hotspot) supported by a mobile provider. ANDSF support may provide information about a cellular network through a WLAN network. Some IMS support may generally relate to whether multimedia may be delivered using IMS. In one example, IMS allows multimedia streaming over mobile stations or cellular networks. IMS support may allow users to switch between cellular/mobile networks and WLANs and maintain streaming multimedia. GAN support may generally relate to whether mobile voice, data, and IMS applications may be extended between networks.

In one embodiment, the 3GPP capabilities 408 may be implemented in at least two ways: 1) the 3GPP capability 408 may be a new IEEE802.11 ANQP element; or 2) the 3GPP capability 408 may be a new WFA hotspot element. These two exemplary implementations will be described below. Additional embodiments may include different implementations.

In a first example, the 3GPP capability 408 may be a new IEEE802.11 ANQP element. The 3GPP capability 408 may include an information ID (e.g., fig. 7) and a length field. The length field may correspond to the length of the included 3GPP entity. The 3GPP entity field may correspond to each capability included (e.g., supporting ANDSF, IMS, and/or GAN). The 3GPP capabilities 408 may also include a release that relates to the particular 3GPP release to which the capabilities conform. In one embodiment, the 3GPP capabilities 408 may be formatted as shown in table 11.

Table 11: IEEE802.11 ANQP 3GPP capability format

Each of the 3GPP entity fields may include an entity identifier subfield and a 3GPP entity version field, as shown in table 12:

table 12: IEEE802.11 ANQP 3GPP entity subfield format

The 3GPP entity ID may include a value of each 3GPP entity existing in the 3GPP network. In one embodiment, a 3GPP entity ID may be assigned, as shown in table 13:

entity name	Value of
		Reserved	0
Access Network Discovery and Selection Function (ANDSF)	1
		IP Multimedia Subsystem (IMS)	2
General Access Network (GAN)	3

Table 13: IEEE802.11 ANQP 3GPP entity ID

The 3GPP entity release is a 16-octet field containing a value for the release number of the 3GPP entity (e.g., "release 5.6.9"). This provides an indication of which version is supported in the network. In an alternative embodiment, the 3GPP entity version field may not be present.

In a second example, the 3GPP capability 408 may be a new WFA hotspot element. The new elements may be included in the WFA hotspot wireless communication standard. As described herein, a WFA hotspot may refer to a Wi-Fi alliance hotspot or a Wi-Fi alliance hotspot 2.0 specification. New elements in WFA hotspots for 3GPP capabilities 408 may include 3GPP capabilities as discussed above. In one embodiment, the format of the 3GPP capabilities 408 is shown in table 14:

table 14: WFA hotspot 3GPP capability format

The 3GPP entity subfield may be similar to the 3GPP entity subfield shown in table 12.

Ability to move

Mobility capability 410 is another example of network information 120 provided in a network discovery communication. Mobility capability 410 may include mobility protocols or entities that may be transferred with respect to a network prior to associating with the network. The mobility capability 410 information may be used to inform the wireless device of the particular mobility protocol that may or may not be used by the network. Whether a network communicates using a particular mobility protocol may be used during discovery when a wireless device is selecting a network to associate with. Accordingly, mobility capabilities 410 may be communicated during network discovery (e.g., using ANQP) prior to associating with the network.

Examples of mobility capabilities 410 include Columbia, mobile internet protocol ("IP"), cellular IP, layered mobile IP ("HMIP"), fast mobile IP ("FMIP"), general packet radio service ("GPRS") tunneling protocol ("GTP"), and proxy mobile IP version 6 ("PMIPv 6"). Columbia may refer to the mini mobility stack and whether communication is taking place with the software. Mobile IP may be a protocol for transporting connections between networks using anchored/tethered internet protocol ("IP") addresses. For example, a voice call may be communicated between networks using the mobile IP protocol. Cellular IP may be used to allow seamless IP mobility between different domains of packet data service nodes. Hierarchical mobile IP ("HMIP") is an enhancement to the mobile internet protocol ("mobile IP") that can reduce the amount of signaling required and improve the speed of handover of mobile connections. Fast mobile IP ("FMIP") is a mobility protocol designed to improve handovers between nodes. GTP is an IP-based set of communication protocols used to carry general packet radio service ("GPRS") in mobile or cellular networks. Proxy mobile IPv6 ("PMIPv 6") is a network-based mobility management protocol that is standardized and designed to accommodate multiple access technologies simultaneously, independent of the mobile network. The above is merely an example of mobility capabilities 410 that may be sent using ANQP during network discovery. Additional mobility capabilities and protocols may be included with mobility capability 410.

In one embodiment, the mobility capability 410: 1) may be implemented in at least two ways) the mobility capability 410 may be a new IEEE802.11 ANQP element; or 2) mobility capability 410 may be a new WFA hotspot element. These two exemplary implementations will be described below. Additional embodiments may include different implementations.

In a first example, mobility capability 410 may be a new IEEE802.11 ANQP element. Mobility capability 410 may include an information ID (e.g., fig. 7) and a length field. The length field may correspond to the length or number of mobility protocols involved. A mobility protocol may correspond to each of the capabilities involved. In one embodiment, mobility capability 410 may be formatted, as shown in table 15:

table 15: IEEE802.11 ANQP mobility capability format

Each of the 3GPP protocol fields may include a protocol identifier subfield and a mobility protocol version field, as shown in table 16:

table 16: IEEE802.11 ANQP mobility subfield format

The mobility protocol ID may include a value for each mobility protocol supported by the network. In one embodiment, a mobility protocol ID may be assigned, as shown in table 17:

entity name	Value of
		Reserved	0
Columbia	1
		Mobile IP	2
Cellular IP	3
		HMIP	4
Fast Mobile IP (FMIP)	5
		GPRS Tunneling Protocol (GTP)	6
Proxy Mobile IP version 6(PMIPv6)	7

Table 17: IEEE802.11 ANQP mobility protocol ID

The mobility protocol version is a 16-octet field, which may include a value for a version number of the mobility protocol (e.g., "v 1.2"). This may provide an indication of which version is supported in the network. In an alternative embodiment, the mobility protocol version field may not be present.

In a second example, mobility capability 410 may be a new WFA hotspot element. New elements may be included in the WFA hotspot wireless communication standard. As described herein, a WFA hotspot may refer to a Wi-Fi alliance hotspot or a Wi-Fi alliance hotspot 2.0 specification. New elements in WFA hotspots for mobility capability 410 may include mobility protocols as discussed above. In one embodiment, the format of mobility capability 410 is shown in table 18:

table 18: WFA hotspot mobility protocol format

The mobility protocol subfield may be similar to the mobility protocol subfield shown in table 16.

Device identification

The device identification 412 is another example of the network information 120 provided in the network discovery communication. The device identification 412 may be used to identify the type of station ("STA"). STA may refer to any side of the network, including: wireless device, terminal and access point. In particular, the WLAN terminal may be informed of the type of STA or wireless device from which it received the ANQP response. The WLAN terminal may take advantage of different capability differences between STAs with which it is attempting to communicate. The device identification 412 may include a type of device, and the communication of the device type may determine to communicate with the device. The device identification 412 may include identification information related to a network provider (e.g., access point 104a) and an end-user device (e.g., wireless device 114). In other words, the device identification 412 may identify the type of device at both ends of the network communication.

In one embodiment, device identification 412: 1) may be implemented in at least two ways device identification 412 may be a new IEEE802.11 ANQP element; or 2) the device identification 412 may be a new WFA hotspot element. These two exemplary implementations will be described below. Additional embodiments may include different implementations.

In a first example, the device identification 412 may be a new IEEE802.11 ANQP element. The device identification 412 may include an information ID (e.g., fig. 7) and a length field. The length field may correspond to the length or number of STA identifications included. The STA identification may correspond to each type of identified device. In one embodiment, the device identification 412 may be formatted, as shown in table 19:

table 19: IEEE802.11 ANQP device identification format

The STA identification subfield may be formatted as shown in table 20:

table 20: IEEE802.11 ANQP device identification subfield format

The STA identification subfield may include a set of bits (e.g., b0 through b15 of a 16-bit field) corresponding to the available type of the STA. Each of the bits of the STA identification subfield may correspond to a particular device or STA, as shown in table 21:

STA identification	Bits
		Reserved	0
non-AP STA	1
		AP	2
QoS AP	3
		QoS STA	4
HT STA	5
		VHT STA	6
60GHz STA	7
		Mesh STA	8
Slave STA	9
		Enabling STA	10
Reserved	11-15

Table 21: IEEE802.11 ANQP device identification subfield bits

The non-AP STA bit and the AP STA bit indicate whether the STA is an access point. Because the STA may be a wireless device/terminal or an access point, the non-AP STA bit and the AP bit identify whether the STA is an access point. Quality of service ("QoS") bits identify QoS stations or access points. High throughput ("HT") and very high throughput ("VHT") identify stations based on operating speed. A 60 gigahertz ("GHz") STA identifies stations operating at a 60GHz frequency. A mesh STA identifies stations that may operate in a mesh network environment. A mesh environment may not have a particular access point and terminal because all STAs in the network are autonomously connected through the network. A dependent STA (dependent STA) identifies a station that is dependent on an enabling STA (associating STA) for channel and band information that may be found in a "blank" operation. The enabling STA identifies a station that is capable of receiving channel and band information out-of-band (e.g., it may connect to the channel database over another medium).

In a second example, device identification 412 may be a new WFA hotspot element. New elements may be included in the WFA hotspot wireless communication standard. As described herein, a WFA hotspot may refer to a Wi-Fi alliance hotspot or a Wi-Fi alliance hotspot 2.0 specification. The new element in the WFA hotspot for device identification 412 may include a station identification type as discussed above. In one embodiment, the format of the device identification 412 is shown in table 22.

Table 22: WFA hotspot device identification format

The STA identification subfield may be similar to the STA identification subfield shown in table 21.

Multi-BSSID information

multi-BSSID information 414 is another example of network information 120 provided in a network discovery communication. A basic service set ("BSS") is a set of all stations that can communicate with each other. Each BSS has an identifier ("ID"), referred to as a BSSID, that is the MAC address of the access point serving the BSS. multi-BSSIDs allow information to be communicated from multiple access points or hotspots that have some form of intercommunication within an area. In particular, multi-BSSID information 414 may be transmitted using a single ANQP message (defined in IEEE802.11, WFA hotspot 2.0, or in this document) prior to association with the network, and multi-BSSID information 414 provides details regarding multiple access points or hotspots.

multi-BSSID information 416 may be used to identify a plurality of information about many access networks associated with a particular WLAN, not just the access network to which it is connected. A typical WLAN access point may be physically implemented as multiple logical access points. The multi-BSSID information request allows another single ANQP request (defined in IEEE802.11, WFA hotspot 2.0, or this document) to be sent to the access point. If the access point is one of multiple access points in an area with some form of intercommunication between them, the message may allow all information from these multiple access points to be returned in the multi-BSSID response. In other words, a single multi-BSSID message may be used to receive information related to multiple logical access points.

multi-BSSID information 416 may relay a specific ANQP request from one wireless terminal (or station ("STA")) through a single access point to determine information from neighboring STAs or terminals. For example, a list of location names of neighboring STAs may be returned. The multi-BSSID request may include an information ID for "multi-BSSID" (e.g., 278), followed by an information ID for "location name" (e.g., 258). The location name ANQP message may be as defined in IEEE 802.11. The ANQP request may be sent to a single access point and instead of responding directly with its own location name, the access point forwards the request to all neighboring STAs connected to it. For each response from its neighbors, the access point may provide a "multi-BSSID information subfield" (as described in table 24) in the final response. The mechanism can also be applied to virtual logical access points housed in one physical access point unit. Security considerations may limit the transfer of certain information from one logical STA domain to another. If this information cannot be determined, an appropriate error code may be passed back to the initiator STA.

In one embodiment, the multi-BSSID information 416 may be implemented in at least two ways: 1) multi-BSSID information 416 may be a new IEEE802.11 ANQP element; or 2) the multi-BSSID information 416 may be a new WFA hotspot element. These two exemplary implementations will be described below. Additional embodiments may include different implementations.

In a first example, the multi-BSSID information 416 may be a new IEEE802.11 ANQP element. The ANQP multi-BSSID information 416 may include information related to neighboring STAs based on a particular ANQP element ("AE"). In one embodiment, the format of the multi-BSSID information 416 is as shown in table 23:

table 23: IEEE802.11 ANQP Multi-BSSID information Format

The information identification ("information ID") field may be an identifier used in the IEEE802.11 ANQP information identifier definition. A table showing exemplary network information 120 and corresponding information IDs is shown in fig. 7. The length field may be a 2 octet field equal to the length of the optional ANQP BSSID information subfield. One embodiment of the ANQPBSSID information subfield is shown in table 24.

Table 24: IEEE802.11 ANQP Multi-BSSID information subfield format

A service set identifier ("SSID") element is an identifier of a particular WLAN. The SSID element may include a field length indication that establishes a length of the SSID. In one example, the SSID may be up to 32 characters. A basic service set identifier ("BSSID") element may identify a basic service set ("BSS"). In one example, SSIDs may be used in multiple or even overlapping BSSs. The BSSID may be a media access control ("MAC") address of the access point. The ANQP element ("AE") field may be a variable length field, containing any other AE. In alternative embodiments, elements from other advertising protocols may be used.

In a second example, the multi-BSSID information 416 may be a new WFA hotspot element. New elements may be included in the WFA hotspot wireless communication standard. As described herein, a WFA hotspot may refer to a Wi-Fi alliance hotspot or a Wi-Fi alliance hotspot 2.0 specification. New elements in the WFA hotspot for multi-BSSID information 416 may include SSID, BSSID, and ANQP elements as discussed above. In one embodiment, the format of the multi-BSSID information 416 is shown in table 25:

table 25: WFA hotspot multi-BSSID information format

In one embodiment, the format of the hotspot BSSID information subfield is shown in table 26:

table 26: WFA hotspot multi-BSSID information subfield format

The hotspot 2.0 element ("HE") field is a variable length field that may contain any other hotspot 2.0 element as defined in the WFA hotspot 2.0 or other hotspot specification. Elements from other advertising protocols may also be used.

Fig. 5 shows a wireless terminal 114 as shown in fig. 1 and 3. Wireless terminal 114 includes a processor 502, and processor 502 may be used to control the overall operation of wireless terminal 114. The processor 502 may be implemented using a controller, a general purpose processor, a digital signal processor, dedicated hardware, or any combination thereof. The processor 502 may include a central processing unit, a graphics processing unit, a digital signal processor, or other type of processing device. The processor 502 may be a component in any of a variety of systems. For example, the processor 502 may be part of a standard personal computer or workstation. The processor 502 may be one or more general processors, digital signal processors, application specific integrated circuits, field programmable gate arrays, servers, networks, digital circuits, analog circuits, combinations thereof, or other now known or later developed devices for analyzing and processing data. The processor 502 may operate in conjunction with a software program (e.g., manually generated (i.e., programmed) code).

The wireless terminal 114 also includes a terminal message generator 504 and a terminal data parser 506. The terminal message generator 504 may generate network information discovery messages, such as the discovery request 116 and the discovery response 118, for communicating the network information 120 of fig. 1. Terminal data parser 506 may be used to retrieve network information from a memory (e.g., random access memory 510, etc.). For example, terminal data parser 506 may retrieve network information 120 cached in wireless terminal 114 after receiving the network information 120 from a WLAN (e.g., access networks 106a-c of fig. 1).

In the illustrated embodiment, the terminal message generator 504 and the terminal data parser 506 are shown separate from the processor 502 and connected to the processor 502. In alternative embodiments, the terminal message generator 504 and the terminal data parser 506 may be implemented in the processor 502 and/or in a wireless communication subsystem (e.g., the wireless communication subsystem 518). The terminal message generator 504 and the terminal data parser 506 may be implemented using any combination of hardware, firmware, and/or software. For example, one or more integrated circuits, discrete semiconductor components, and/or passive electronic components may be used. For example, the terminal message generator 504 and the terminal data parser 506, or portions thereof, may be implemented using one or more circuits, programmable processors, application specific integrated circuits, programmable logic devices, field programmable logic devices, or the like.

The terminal message generator 504 and the terminal data parser 506, or portions thereof, may be implemented using instructions, code, and/or other software and/or firmware stored on a machine-accessible medium and executable by, for example, a processor (e.g., the processor 502). The terminal message generator 503 or the terminal data parser 506 may be stored on or include a tangible storage medium or memory. For example, the terminal message generator 504 or the terminal data parser 506 may be implemented in software stored on a memory that is executable by the processor 502. Alternatively, the terminal message generator 504 and/or the terminal data parser 506 may be implemented in hardware having a software function. The memory for storing software associated with the terminal message generator 504 and/or the terminal data parser 506 may include, but is not limited to: computer-readable storage media, for example, various types of volatile and non-volatile storage media, including: random access memory, read only memory, programmable read only memory, electrically erasable read only memory, flash memory, magnetic tape or disk, optical media, and the like. In one embodiment, the memory may include random access memory 510 for the processor 502, or may be an external storage device or database for storing recorded announcements or user data. Examples include hard drives, compact discs ("CDs"), digital video discs ("DVDs"), memory cards, memory sticks, floppy disks, universal serial bus ("USB") memory devices, or any other device operable to store announcements or user data. The memory is operable to store instructions that may be executed by the processor 502.

The wireless terminal 114 may include flash memory 508, random access memory 510, and/or an extensible memory interface 512 coupled to the processor 502. Flash memory 508 may store computer readable instructions and/or data. In some embodiments, the flash memory 508 and/or the RAM510 may store the network information 120 of FIG. 1 and instructions for transferring the network information 120. The processor 502 may be coupled with a memory (e.g., flash memory 508 or RAM510) for storing software instructions that may be executed by the processor 502. The memory may include, but is not limited to: computer-readable storage media, for example, various types of volatile and non-volatile storage media, including: random access memory, read only memory, programmable read only memory, electrically erasable read only memory, flash memory, magnetic tape or disk, optical media, and the like. The functions, acts or tasks illustrated in the figures or described herein may be performed by the programmed processor 502 executing instructions stored in the memory. The functions, acts or tasks may be independent of the particular type of instructions set, storage media, processor or processing strategy and may be performed by software, hardware, integrated circuits, firmware, micro code and the like, operating alone or in combination. Likewise, processing strategies may include multiprocessing, multitasking, parallel processing and the like.

The wireless terminal 114 may include a secure hardware interface 514 for receiving a SIM card from a wireless service provider. The SIM card may be used for network discovery communications, including authenticating the wireless terminal 114 to establish a connection with a WLAN-enabled network. The wireless terminal 114 may have an external data I/O interface 516. The external data I/O interface 516 may be used by a user to transfer information to the wireless terminal 114 over a wired medium.

Wireless terminal 114 may include a wireless communication subsystem 518 for enabling wireless communication with access points (e.g., access points 104a-c of fig. 1). Although not shown, wireless terminal 114 may also have a long-range communications subsystem for receiving messages from and transmitting messages to a cellular wireless network. In the examples shown and described herein, may be according toThe 802.11 standard configures the wireless communication subsystem 518. In other exemplary implementations, the use ofA radio station,A device, a wireless USB device, an ultra-wideband radio, a near field communication ("NFC") device, or a radio frequency identifier ("RFID") device to implement the wireless communication subsystem 518.

The wireless terminal 114 may include a user interface for communicating with the wireless terminal. The user interface may be a separate component or may include a speaker 520, a microphone 522, a display 524, and a user input interface 526. The display 524 may be a liquid crystal display, organic light emitting diode, flat panel display, solid state display, cathode ray tube, projector, printer, or other now known or later developed display device for outputting determined information. The user input interface 526 may include an alphanumeric keypad and/or a telephone-type keypad, a multi-directional actuator or scroll wheel with dynamic button press capability, a touch pad, and the like. Network discovery information that is communicated with the network prior to connection may be communicated with or without each of the user interfaces described herein. In alternative embodiments, the speaker 520, the microphone 522, the display 524, the user input interface 526, and/or any combination thereof, may be omitted. In one embodiment, wireless terminal 114 is a battery-powered device and includes a battery 528 and a battery interface 530.

Fig. 6 shows an access point ("AP") 104 a. The access point shown in fig. 6 is AP104a, but other access points (e.g., access points 104b, 104c) may also be illustrated. The AP104a includes a processor 602 for performing the operations of the AP104 a. The processor 602 may be similar to the processor 502 described above.

The AP104a includes an access point message generator 604 for generating network information communications and an access point data parser 606 for retrieving network information communications from the wireless terminal 114 and/or external network a 108a as shown in fig. 1. The access point message generator 604 may be similar to the terminal message generator 504 of fig. 5, and the access point data parser 606 may be similar to the terminal data parser 506 of fig. 5. As with the terminal message generator 504 and the terminal data parser 506 of fig. 5, the access point message generator 604 and the access point data parser 606 may be implemented in software stored on a memory that may be executed by the processor 602 or may be implemented in hardware having software functions executed by the processor 602. Alternatively, the access point message generator 604 and the access point data parser 606 may be implemented in a wireless communication subsystem (e.g., the wireless communication subsystem 612) using any combination of hardware, firmware, and/or software, including instructions stored on a tangible computer-readable medium and/or a non-transitory computer-readable medium.

The AP104a may also include flash memory 608 and RAM 610, each coupled to the processor 602. The flash memory 608 and/or random access memory ("RAM") 610 may be configured to store network information (e.g., the network information 120 of fig. 1 including discovery communications). RAM 610 may also be used to generate messages for communication with wireless terminal 114 and/or transmission to external network a 108 a. The RAM 610 may also store received messages transmitted by the wireless terminal 114 and/or the external network a 108 a.

To communicate with wireless terminals, such as wireless terminal 114, AP104a may include a wireless communication subsystem 612, and wireless communication subsystem 612 may be similar to wireless communication subsystem 518 of wireless terminal 114 shown in fig. 5. To communicate with a WLAN-enabled network or an external network (e.g., networks 106a-c, 108a, and 108b of fig. 1), the AP104a may include a network uplink communication interface 614.

Fig. 7 is a table of 802.11 ANQP information identifiers. The network information 120 described above may be assigned an identifier ("ID") in the existing 802.11 ANQP information ID definition. Fig. 7 illustrates one embodiment of an information ID that may be used for network information 120. Specifically, information IDs are assigned to WAN latency, 3GPP capabilities, mobility capabilities, hotspot capabilities, neighbor reports, device (STA) identification, and multi-BSSID information, an example of which is shown in fig. 7.

Fig. 8 is a table of hotspot ANQP element subtype definitions. The network information 120 described above may be a subtype value within the existing hotspot 2.0ANQP element. Fig. 8 illustrates one embodiment of a subtype value that may be assigned to network information 120. Specifically, subtype IDs are assigned to WAN latency, 3GPP capabilities, mobility capabilities, hotspot capabilities, neighbor reports, device (STA) identification, and multi-BSSID information, an example of which is shown in fig. 8.

Fig. 9 illustrates network communications. The wireless terminal 114 requests 902 the network information 120 from the access point 104. As discussed above, network information 120 may include any of the elements or features discussed with respect to fig. 4. The access point 104 responds 904 to the request with the requested network information 120. Communications (request 902 and response 904) during network discovery are located above discovery line 906, and communications after network discovery are shown as being located below discovery line 906. In other words, the request and response of the network information 120 occurs during network discovery. Below the discovery line 906, the wireless terminal analyzes the network and selects 908 a network or access point with which to associate 910. The communication below the discovery line 906 is discovered after a communication when connected or associated with a network. Network discovery may refer to communications or messages that occur prior to connecting or associating with a network. In one embodiment, the discovery communication may be in accordance with an access network query protocol ("ANQP") that establishes the discovery communication in the WLAN. Any of the network information 120 described with respect to fig. 4 may be communicated during network discovery. In alternative embodiments, the request may originate from the access point 104 and the response may originate from the wireless terminal 114. For example, for device identification 412, the access point 104 may request identification from the wireless terminal 114.

The described systems and processes may be encoded in a signal bearing medium, a computer readable medium (e.g., a memory), programmed in a device such as one or more integrated circuits and one or more processors, or processed by a controller or computer. If the method is performed by software, the software may reside in a memory that resides in or interfaces with a storage device in communication with the transmitter, a synchronizer, a communication interface, or a non-volatile or volatile memory. The circuit or electronic device is designed to transmit data to another location. The memory may include an ordered listing of executable instructions for implementing logical functions. The described logical functions or system elements may be implemented by optical circuits, digital circuits, by source code, by analog circuits, by analog sources such as analog electronic, audio, or video signals, or combinations thereof. The software may be embodied in a computer-readable or signal-bearing medium for use by or in connection with an instruction executable system, apparatus, or device. The system can include a computer-based system, a processor-containing system, or another system that can selectively obtain instructions from an instruction executable system, apparatus, or device that can also execute the instructions.

A "computer-readable medium," "machine-readable medium," "propagated-signal" medium, and/or "signal-bearing medium" may comprise any apparatus that can contain, store, communicate, propagate, or transport software for use by or in connection with an instruction-executable system, apparatus, or device. The machine-readable medium can optionally be, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. A non-exhaustive list of examples of machine-readable media would include: an electrical connection "electronically" having one or more wires, a portable magnetic or optical disk, a volatile memory (e.g., random access memory "RAM", read-only memory "ROM", erasable programmable read-only memory (EPROM or flash memory)), or an optical fiber. A machine-readable medium may also include a tangible medium upon which the software is printed, as the software may be electronically stored as an image or in another format (e.g., via optical scanning), then compiled, and/or interpreted or otherwise processed. The processed media may then be stored in a computer and/or machine memory.

In an alternative embodiment, dedicated hardware implementations (e.g., application specific integrated circuits), programmable logic arrays and other hardware devices may be constructed to perform one or more of the methodologies described herein. Applications that may include the apparatus and systems of various embodiments may broadly include a variety of electronic and computer systems. One or more embodiments described herein may perform functions using two or more dedicated interconnected hardware modules or devices with related control and data signals that may be communicated between and through the modules, or may perform functions using two or more dedicated interconnected hardware modules or devices as part of a dedicated integrated circuit. Accordingly, the present system encompasses software, firmware, and hardware implementations.

The illustrations of the embodiments described herein are intended to provide a general understanding of the structure of the various embodiments. The illustrations are not intended to serve as a complete description of all of the elements and features of apparatus and systems that utilize the structures or methods described herein. Many other embodiments will be apparent to those of skill in the art upon reading this disclosure. Other embodiments may be utilized or derived from the disclosure, such that structural and logical substitutions and changes may be made without departing from the scope of the disclosure. Furthermore, the illustrations are merely representative and may not be drawn to scale. Certain proportions within the illustrations may be exaggerated, while other proportions may be minimized. The present disclosure and figures are, therefore, to be regarded as illustrative rather than restrictive.

Claims (17)

1. A method for communicating in a wireless network, comprising:

transmitting, from a wireless device to a first Access Point (AP), a request for a neighbor report related to any neighboring AP before the wireless device associates with the first AP, wherein any neighboring AP and the first AP comprise APs within a same Basic Service Set (BSS) or a same Extended Service Set (ESS); and

receiving, at the wireless device, a response from the first access point, AP, prior to the wireless device associating with the first AP, wherein the response includes a neighbor report related to a neighboring AP and includes information describing the neighboring AP.

2. The method of claim 1, wherein the information describing the neighboring AP comprises an identifier indicating a BSS associated with the neighboring AP, reachability information indicating whether the wireless device requesting the neighbor report can reach the neighboring AP indicated by the BSS, and security information indicating whether the neighboring AP supports the same security pre-configuration utilized by the wireless device.

3. The method of claim 1, wherein the request and the response comprise Access Network Query Protocol (ANQP) messages.

4. The method of claim 3, wherein the ANQP message is sent using an extensible authentication protocol.

5. The method of claim 1, wherein the transmitting and the receiving prior to the wireless device associating with the first AP occur during a network discovery operation of the wireless device.

6. The method of claim 1, further comprising:

comparing, at the wireless device, the information describing the neighboring AP to information describing the first AP; and

determining, at the wireless device, to associate with the first AP or one of the neighboring APs based on the comparison.

7. A method at a first access point, AP, associated with a wireless local area network, comprising:

receiving, at the AP, a request from a wireless device for a neighbor report related to any neighboring AP prior to the wireless device associating with the first AP, wherein any neighboring AP and the first AP comprise APs within a same Basic Service Set (BSS) or a same Extended Service Set (ESS); and

transmitting a response from the first AP before the wireless device associates with the first AP, wherein the response includes a neighbor report related to a neighboring AP and includes information describing the neighboring AP.

8. The method of claim 7, wherein the request and the response are communicated using an Access Network Query Protocol (ANQP).

9. The method of claim 8, wherein the neighbor report is transmitted as an ANQP message sent using an extensible authentication protocol.

10. The method of claim 7, wherein the information describing the neighboring AP comprises an identifier indicating a BSS associated with the neighboring AP, reachability information indicating whether the wireless device requesting the neighbor report can reach the neighboring AP indicated by the BSS, and security information indicating whether the neighboring AP supports the same security pre-configuration utilized by the wireless device.

11. A wireless device, comprising:

a processor interconnected with the memory, the processor configured to:

transmitting, from the wireless device to a first Access Point (AP), a request for a neighbor report related to any neighboring AP prior to the wireless device associating with the first AP, wherein any neighboring AP and the first AP comprise APs within a same Basic Service Set (BSS) or a same Extended Service Set (ESS); and

receiving, at the wireless device, a response from the first access point, AP, prior to the wireless device associating with the first AP, wherein the response includes a neighbor report related to a neighboring AP and includes information describing the neighboring AP.

12. The wireless device of claim 11, wherein the information describing the neighboring AP includes an identifier indicating a BSS associated with the neighboring AP, reachability information indicating whether the wireless device requesting the neighbor report can reach the neighboring AP indicated by the BSS, and security information indicating whether the neighboring AP supports the same security pre-configuration utilized by the wireless device.

13. The wireless device of claim 11, wherein the request and the response comprise Access Network Query Protocol (ANQP) messages.

14. The wireless device of claim 13, wherein the ANQP message is sent using an extensible authentication protocol.

15. The wireless device of claim 11, wherein the processor is further configured to:

comparing the information describing the neighboring AP with information describing the first AP; and

determining to associate with the first AP or one of the neighboring APs based on the comparison.

16. A first access point, AP, associated with a wireless local area network, comprising:

a processor interconnected with the memory, the processor configured to:

receiving, at the AP, a request from a wireless device for a neighbor report related to any neighboring AP prior to the wireless device associating with the first AP, wherein any neighboring AP and the first AP comprise APs within a same Basic Service Set (BSS) or a same Extended Service Set (ESS); and

transmitting a response from the first AP before the wireless device associates with the first AP, wherein the response includes a neighbor report related to a neighboring AP and includes information describing the neighboring AP.

17. The first AP of claim 16, wherein the information describing the neighboring AP includes an identifier indicating a BSS associated with the neighboring AP, reachability information indicating whether the wireless device requesting the neighbor report can reach the neighboring AP indicated by the BSS, and security information indicating whether the neighboring AP supports the same security pre-configuration utilized by the wireless device.