Methods and apparatus to discover network capabilities for connecting to an access network

Example methods and apparatus to discover network capabilities for connecting to an access network are disclosed. A disclosed example method involves sending a request to a first access network of a first network type. The request is addressed to a database and requests network connectivity information for connecting to a second access network of a second network type different from the first network type. The example method also involves receiving a response from the first access network. The response includes the network connectivity information for connecting to the second access network.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to network communications and, more particularly, to methods and apparatus to discover network capabilities for connecting to an access network.

BACKGROUND

Wireless network deployments, such as wireless local area networks (WLANs), allow wireless terminals to access network and Internet services when within proximity of wireless communication signals of those wireless networks. Sometimes, users of wireless terminals move between different locations that offer different types of access network technologies. In such instances, wireless terminals capable of operating with different access network technologies can establish communications with such different technologies when moved between different locations. When moved to a new location, a wireless terminal must determine whether an access network is available and identify the information required to establish a connection with the available access network.

DETAILED DESCRIPTION

Although the following discloses example methods and apparatus including, among other components, software executed on hardware, it should be noted that such methods and apparatus are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of these hardware and software components could be embodied exclusively in hardware, exclusively in software, exclusively in firmware, or in any combination of hardware, software, and/or firmware. Accordingly, while the following describes example methods and apparatus, persons having ordinary skill in the art will readily appreciate that the examples provided are not the only way to implement such methods and apparatus.

The example methods and apparatus described herein can be used to access (e.g., retrieve network connectivity information) a database storing network information pertaining to a plurality of access networks in different locations. The example methods and apparatus described herein can be used in connection with mobile communication devices, mobile computing devices, or any other device capable of communicating wirelessly with a wireless network. Such devices, also referred to as terminals, wireless terminals, TVWS devices, TV band devices (TVBDs), or user equipment (UE), may include mobile smart phones (e.g., a BLACKBERRY® smart phone), wireless personal digital assistants (PDA), laptop/notebook/netbook computers with wireless adapters, etc. The example methods and apparatus are described herein in connection with the wireless local area network (WLAN) communication standard known as IEEE® (Institute for Electrical and Electronics Engineers) 802.11, which, among other things, defines interworking with external networks. However, the example methods and apparatus may additionally or alternatively be implemented in connection with other wireless communication standards including, but not limited to, other WLAN standards, personal area network (PAN) standards, wide area network (WAN) standards, wireless metropolitan area network (WMAN) standards (e.g., IEEE® 802.16 or WiMAX networks), wireless regional area network (WRAN) standards (e.g., IEEE® 802.22), or cellular communication standards.

The example methods and apparatus described herein can be used to obtain information about connecting with television white space (TVWS) access networks before attempting to connect with such networks. A TVWS access network is a telecommunications network through which wireless terminals (e.g., TVWS devices or TVBDs having radio transceivers that operate in television bands) connect to information and services across one or more other networks (e.g., the Internet). A TVWS network allows wireless terminal connectivity and communications via unused channels between active digital television (DTV) (or analog television) channels. Alternatively, the example methods and apparatus described herein may also be used in connection with other white space technologies that use frequency bands of other, non-television, systems such as military communication systems, terrestrial broadcast radio systems, etc.

To store and provide information about TVWS connectivity capabilities and/or requirements at different locations supporting TVWS access networks, a networked TVWS database is hosted in an external network accessible through one or more types of access networks including wireless local area networks (WLANs) and TVWS access networks. In some example implementations, the TVWS database may provide capabilities/requirements information such as connection frequencies, available bandwidth, power, policy, locations, timing, and access rights to channels allocated for TVWS access network connectivity. This information can be provided for different locations in which TVWS access networks are available.

The example methods and apparatus described herein can be advantageously used to inform wireless terminals of the types of TVWS connectivity that are available in different locations before the wireless terminal attempts a TVWS connection at those locations. For example, a person travelling between different locations (e.g., different cities, states, countries, etc.) may, in advance, query a TVWS database about TVWS access network availability and connectivity capabilities/requirements at a future destination, so that upon arrival at the destination, the person's TVBD can connect to the available TVWS access network based on the retrieved TVWS access network connectivity capabilities/requirements information.

In the illustrated examples described herein, example wireless terminals used to connect with TVWS access networks are dual-mode wireless terminals having wireless capabilities for connecting to the TVWS access networks (using TVWS protocols and TVWS frequencies) and for connecting to an IEEE® 802.11 WLAN access network. In other example implementations, the example methods and apparatus described herein may be used by wireless terminals having TVWS connectivity capabilities in addition to capabilities for connecting to access network technologies other than IEEE® 802.11 WLAN access networks. Such other access network technologies may include both wireless and wired technologies such as cellular, Ethernet LAN and universal serial bus (USB), for example.

A dual-mode wireless terminal can be advantageously used to connect to a TVWS database via a non-TVWS access network (e.g., a WLAN access network) to retrieve information about TVWS access network connectivity capabilities/requirements before attempting to connect to a TVWS access network. In this manner, if TVWS connectivity is not available or not possible, a wireless terminal need not consume battery power in attempting to connect to a TVWS access network when such an access network is not available or such a connection is not possible.

Although the example methods and apparatus are described herein as accessing a TVWS database to access information about, for example, accessing TVWS access networks, the example methods and apparatus may similarly be used to access databases storing information (e.g., information servers) about accessing and connecting to other types of networks (e.g., WLAN access networks, cellular networks, etc.), including networks that use white space in bands other than TV bands, as regulatory domains make them available. In other example implementations, the information message exchanges described herein between a TVBD and a TVWS database may be implemented using other schemes such as email, short messaging service (SMS), and instant messaging.

Turning now toFIG. 1, an example communication network100in which the example methods and apparatus described herein may be implemented is shown. As shown inFIG. 1, the example communication network100includes a WLAN access network102having a WLAN access point (AP)104and a network access server (NAS)106that provide access to a TVWS database108in an external network110. The NAS106determines whether wireless terminals are permitted to gain network access and, thus, communicate with the WLAN access network102and other networks (e.g., the external network110). In the illustrated examples described herein, the NAS106also processes communications sent by a wireless terminal114to the WLAN AP104intended for delivery to the TVWS database108and forwards such communications or related portions (e.g., TVWSP frames discussed below in connection withFIGS. 6-8) to the TVWS database108. In addition, the NAS106receives responses from the TVWS database108and forwards the response information (e.g., via TVWSP frames ofFIGS. 6,10, and11) to the wireless terminal114through the WLAN AP104.

In the illustrated example ofFIG. 1, the external network110is a network that is logically separate from the WLAN access network102or logically separate from any other access network through which wireless terminals connect to the TVWS database108. In the illustrated example ofFIG. 1, connectivity to the TVWS database108is available through the Internet112. However, in other example implementations, connectivity to the TVWS database108via an access network (e.g., the WLAN access network102) may be available through a private network or other networking environment other than the Internet112including, for example, an intranet, an enterprise network, or a mobile operator's core network. In some example implementations, the TVWS database108may be distributed between different regions, with a hierarchy of databases that are managed and synchronized.

In some example implementations, the TVWS database108may be ‘open’ such that authentication or authorization is not required. In such instances, an authentication, authorization, and accounting (AAA) server (e.g., a RADIUS or Diameter server) is not required, as in the network configuration ofFIG. 1. When an AAA server is not used, the NAS106may employ a lightweight directory access protocol (LDAP) to exchange communications with the TVWS database108. In other example implementations, the TVWS database108may not be ‘open’ and an AAA server (or a home location register (HLR)) may be used to authenticate and authorize users to access the TVWS database108. Such an example network configuration including an AAA server is shown inFIG. 14. Example implementations for using AAA server-based communications in connection with the example methods and apparatus described herein are discussed below in connection withFIGS. 14-16.

As shown inFIG. 1, to communicate with the TVWS database108, a wireless terminal114connects to the WLAN AP104. In the illustrated examples described herein, the wireless terminal114includes a station (i.e., a STA), while the WLAN AP104includes an AP STA. The wireless terminal114can use an access network (AN) request message116to query the TVWS database108through the WLAN AP104(and the NAS106). A response from the TVWS database108sent to the WLAN access network102(through the NAS106) can be communicated by the WLAN AP104to the wireless terminal114through an AN response message118. The messaging exchange between the wireless terminal114, the WLAN AP104, and the TVWS database108is shown inFIG. 2. The formats or structures of the request message116and the response message118are shown inFIGS. 4 and 5, respectively.

In some example implementations, to inform the wireless terminal114whether the WLAN AP104supports TVWS connectivity and whether the WLAN AP104is capable of communicating with the TVWS database108, the WLAN AP104may transmit a TVWS advertisement indicating such capability information in a beacon signal120. The format and structure of the beacon signal120is shown inFIG. 3. In some example implementations, the TVWS connectivity and capability of communicating with the TVWS database108can be transmitted in a probe response message (e.g., the AN response message118). In the illustrated examples described herein, supporting TVWS connectivity indicates that an access point is capable of communicating with a TVBD using TVWS protocol and frequency requirements, and advertising a capability to communicate with (e.g., network reachability or connectivity) the TVWS database108indicates that the access point can route queries to the TVWS database108and receive responses from the TVWS database108(and route the responses to the requesting device).

In the illustrated example ofFIG. 1, the WLAN AP104does not support TVWS connectivity, but it is capable of communicating with the TVWS database108. Similar information indicating support for TVWS connectivity and communication with the TVWS database108may also be transmitted in beacon signals of TVWS access points (e.g., the TVWS access point128c) to indicate support for TVWS connectivity with TVBDs and capabilities to communicate with the TVWS database108. In this manner, the wireless terminal114can connect with a TVWS access network using a TVWS protocol and frequency to retrieve updated TVWS connectivity capability/requirements information for connecting to the TVWS access network and/or for retrieving TVWS connectivity capability/requirements information for connecting to a TVWS access network at another location.

In other example implementations, the beacon and probe responses can be transmitted using another radio access technology (RAT) such as a cellular system, if the TVBD is a multi-mode device also supporting this technology.

In the illustrated example ofFIG. 1, TVWS connectivity information122stored in the TVWS database108is shown as having record entries for each of three different TVWS access networks126a-c. The TVWS connectivity information122includes the capabilities and requirements for connecting to each of the TVWS access networks126a-c. Such TVWS connectivity capabilities and requirements include, for example, frequencies, available bandwidth, power, policy, timing, location, and access rights to channels allocated for TVWS connections. In the illustrated example, the TVWS access network126ais shown as located at location A, the TVWS access network126bis shown as located at location B, and the TVWS access network126cis shown as located at location C. To query the TVWS database108for TVWS connectivity information for a particular one of the locations A-C, the wireless terminal114can send a location identifier for the corresponding location (e.g., one of the locations A-C) to the TVWS database108. In this manner, the TVWS database108can use the received location identifier to locate, in its records, the requested TVWS connectivity information for a corresponding one of the TVWS access networks126a-c.

As shown inFIG. 1, an example operating scenario involves the wireless terminal114requesting connectivity information for the TVWS access network126cat location C while in communication with the WLAN access network102. In this manner, when the wireless terminal114is moved to location C, the wireless terminal114is aware of (e.g., has stored therein) all the TVWS connectivity capabilities and requirements of the TVWS access network126cto facilitate association of the wireless terminal114with the TVWS access network126c. The example methods and apparatus described herein may be employed in such a manner when, for example, a person travels between different regions or countries (e.g., the WLAN access network102and the TVWS access network126cmay be in different regions or countries). Alternatively, the wireless terminal114may access the TVWS database108to discover TVWS connectivity capabilities and requirements for a TVWS access network that is nearby and reachable from its current location (e.g., the WLAN access network102and one of the TVWS access networks126a-cmay be co-located in the same region or overlapping regions). Example processes that may be used to access the TVWS database108to, for example, retrieve TVWS connectivity capabilities and requirements, are described below in connection withFIG. 19.

In some instances, TVWS access networks may change their connectivity capabilities and requirements from time to time such that channels available for communication or useable transmission power levels may change. In such instances, the example methods and apparatus may also be used by a wireless terminal to retrieve updated TVWS information associated with a TVWS access network to which the wireless terminal is already connected. In such example implementations the wireless terminal may access the TVWS information via the TVWS access network or another access network (including another type of access network). Alternatively, this updated information may be broadcast to TVBDs, either in beacon (or broadcast) messages or unsolicited information element messages. Such broadcasting or pushing of updated TVWS connectivity information from the TVWS database108is described in detail below in connection with the flow diagram ofFIG. 20.

In the illustrated example, each of the TVWS access networks126a-cis represented by a television transmission tower. In such example implementations, each television transmission tower can be provided with a TVWS access point128a-cconnected to the external network110through, for example, a respective NAS (not shown). In this manner, the wireless terminal114can connect with the TVWS access networks126a-cusing a TVWS protocol and frequency.

In the illustrated example, the request message116and the response message118can be exchanged without needing the wireless terminal114to be in an associated state with (e.g., without registering with) the WLAN AP104. Example advantages of keeping the wireless terminal114in a non-associated state relative to the WLAN AP104include preserving battery power and processing resources of the wireless terminal114and preserving processing and bandwidth resources of the WLAN AP104that would otherwise be needed to negotiate an association/registration session with the WLAN AP104. A security mechanism may be applied to such non-associated database information exchange to maintain the integrity of the information. However, the example methods and apparatus described herein may also be implemented while the wireless terminal114is in an associated state relative to the WLAN AP104.

FIG. 2depicts an example communication exchange200between the wireless terminal114, the WLAN AP104, and the TVWS database108ofFIG. 1to access information in the TVWS database108. Although not shown, some or all of the message exchanges shown inFIG. 2as being performed by the WLAN AP104may be performed by a combination of the NAS106and the WLAN AP104. In the illustrated example, the wireless terminal114sends the AN request message116to the WLAN AP105. The AN request message116includes a database request202intended for delivery to the TVWS database108. In some example implementations, the AN request message116may be sent by the wireless terminal114in response to user input requesting to access (e.g., retrieve, store, modify, etc.) information in the TVWS database108, while in other example implementations, the AN request message116may be sent in response to a process of the wireless terminal114. The database request202may be, for example, a request for TVWS connectivity capabilities and requirements for different TVWS access networks (e.g., the TVWS access networks126a-c), a request for a database address, a request to register with the TVWS database108or any other request described below in connection withFIGS. 6-8.

After receiving the AN request message116, the WLAN AP104parses out the database request202and forwards the database request202to the TVWS database108. In response to the database request202, the TVWS database108performs a requested operation and sends a database response204to the WLAN AP104that is intended for delivery to the wireless terminal114. The WLAN AP104forms the AN response message118to forward the database response204therein to the wireless terminal114. Example frames that may be used for exchanging communications and information with the TVWS database108using the database request202and the database response204are described below in connection withFIGS. 6-8,10, and11.

In the illustrated example ofFIG. 2, the request and response messages116and118can be exchanged using a pre-defined query protocol such as Access Network Query Protocol (ANQP) that is transported using Generic Advertisement Service (GAS) query/response formatted frames. The GAS protocol, as defined in IEEE® 802.11, provides transport mechanisms for advertisement services between the WLAN APs and wireless terminals while the wireless terminals are in a non-associated state (or an associated state) with the wireless APs. As used in connection with the example methods and apparatus described herein, the ANQP enables STAs (e.g., the wireless terminal114) to discover the availability of information (e.g., TVWS connectivity capabilities/requirements, etc.) related to desired network services. The communications described herein between the wireless terminal114and the WLAN AP104(or any other AP) to access the TVWS database108may be performed at layer 2 (e.g., a media access control (MAC) layer) of the Open Systems Interconnect (OSI) model.

Alternatively, the request and response messages116and118may be exchanged using information elements as defined in IEEE® 802.11.

In some example implementations, to protect the information in messages116,118,202, and204, keys can be used to perform message integrity check (MIC) operations on the messages116, thus, securing messages116and118in OSI layer 2 exchanges. The keys may be derived using, for example, Diffie Hellman exchanges between the wireless terminal114and the TVWS database108, together with a unique White Space identifier of the wireless terminal114(e.g. a Federal Communications Commission (FCC) ID and its serial number). Additionally or alternatively, other procedures may also be used to secure the information exchange with the TVWS database108.

FIG. 3depicts an example beacon frame300that can be transmitted in the beacon signal120(FIG. 1) by the WLAN AP104ofFIG. 1. In the illustrated example, the example beacon frame300includes a TVWS capability (TVWSC) field302and a TVWS database reachability (TVWSD) field304. The TVWSC field302stores information indicative of whether an access point (e.g., the WLAN AP104or TVWS APs of the TVWS ANs126a-cofFIG. 1) has TVWS capabilities to enable connecting to a TVBD using a TVWS protocol and frequency. The TVWSD field304indicates whether an access point (e.g., the WLAN AP104or the TVWS APs128a-cofFIG. 1) is capable of exchanging communications with the TVWS database108. As such, the TVWSC field302and the TVWSD field304may be used in combination to indicate that a TVWS-capable AP lacks network reachability of a TVWS database (e.g., if the AP is in motion itself).

In the illustrated example ofFIG. 3, each of the TVWSC field302and the TVWSD field304is a one-bit field. Also in the illustrated example, the TVWSC field302may be set (i.e., TVWSC field=‘1’) to indicate support for connecting to a TVBD (e.g., the wireless terminal114) or cleared (i.e., TVWSC field=‘0’) to indicate non-support for connecting to a TVBD. Also in the illustrated example, the TVWSD field302may be set (i.e., TVWSD field=‘1’) to indicate support for exchanging communications with the TVWS database108(and network reachability of the TVWS database108) or cleared (i.e., TVWSD field=‘0’) to indicate non-support for exchanging communications with the TVWS database108(or non-reachability of the TVWS database108).

The wireless terminal114can use the information in the TVWSC field302to determine whether it can connect to a particular AP (e.g., one of the TVWS APs128a-cofFIG. 1) using a TVWS communication interface. The wireless terminal114can use the information in the TVWSD field304to determine whether to send the AN request message116to an AP (e.g., the WLAN AP104or one of the TVWS APs128a-cofFIG. 1) or whether such a communication would be unproductive (and wasteful of battery and processing power) because the AP lacks network reachability of the TVWS database108.

Although the TVWSC and TVWSD fields302and304are shown in the beacon frame300, which may be communicated via the beacon signal120(FIG. 1), the TVWSC and TVWSD fields302and304may alternatively be communicated by the WLAN AP104or the TVWS APs128a-cin probe response messages (e.g., the AN response message118ofFIGS. 1 and 2) to the wireless terminal114. In such example implementations, probe response messages from APs may be used to advertise AP capabilities to wireless terminals and/or request capability information from wireless terminals.

FIG. 4depicts the AN request message116ofFIGS. 1 and 2and the database request frame202ofFIG. 2. In the illustrated example, the AN request message116includes an INFO ID field402, a length field404, and a TVWS protocol (TVWSP) frame field406. In some example implementations, the AN request message116may be implemented using a GAS query/response format, and the fields402,404, and406may form an information element implemented in accordance with an access network query protocol (ANQP) defined in IEEE® 802.11. The ANQP supports information retrieval from an information repository on an AP (e.g., a copy of some or all of the contents of the TVWS database108stored in the WLAN AP104or the TVWS APs128a-c) or an external network (e.g., the TVWS database108in the external network110ofFIG. 1).

In the example implementations described herein, the wireless terminal114may use the ANQP information element to query the TVWS database108(or a copy of the TVWS database108stored locally in an AP or other entity in a local access network) and receive responses from the TVWS database108through the WLAN AP104. That is, when the WLAN AP104receives the AN request message116from the wireless terminal114, the WLAN AP104(or the NAS106ofFIG. 1) can parse out information from the INFO ID field402, the length field404, and the TVWSP frame field406, form the database request202based on the parsed out information, and send the database request202to the TVWSC database108. In the illustrated example, to indicate that the wireless terminal114is communicating a query intended for the TVWS database108, the wireless terminal114stores an identifier value in the INFO ID field402identifying the communication as containing a TVWSP frame. In addition, the length field404specifies the size of the information in the TVWSP frame field406, and the TVWSP frame field406includes the query intended for the TVWS database108. Example TVWSP frames that may be communicated in the TVWS frame field406are described below in connection withFIGS. 6-9.

FIG. 5depicts the database response frame204ofFIG. 2and the AN response message118ofFIGS. 1 and 2. In the illustrated example, the AN response message118includes an INFO ID field502, a length field504, and a TVWSP frame field506. The AN response message118may be implemented using a GAS query/response format, and the fields502,504, and506may form an ANQP information element.

In the example implementations described herein, the WLAN AP104may use the ANQP information element to forward the database response204from the TVWS database108to the wireless terminal114. That is, when the WLAN AP104receives the database response204from the TVWS database108, the WLAN AP104(or the NAS106ofFIG. 1) can provide information in the INFO ID field502, the length field504, and the TVWSP frame field506corresponding to the database response204, form the AN response message118, and send the AN response message118to the wireless terminal114. In the illustrated example, the INFO ID field502identifies the communication as including a TVWSP frame, the length field504specifies the size of the TVWSP frame field506, and the TVWSP frame field506includes the response from the information in the TVWS database108. Example response frames that may be communicated in the TVWS frame field506are described below in connection withFIGS. 10 and 11.

FIGS. 6,7, and8depict example TVWSP frames that the wireless terminal108can use to query the WLAN AP104and/or the TVWS database108regarding connectivity information associated with the TVWS access networks (e.g., the TVWS access networks126a-cofFIG. 1), andFIGS. 6,10, and11depict example TVWSP frames that can be used to send responses to the wireless terminal114.FIG. 6is a database network address frame600that can be used to query the WLAN AP104for network addresses of TVWS databases (e.g., the TVWS database108) accessible by the WLAN AP104. The example TVWSP frames ofFIGS. 7 and 8can be communicated by the wireless terminal114to the WLAN AP104in the TVWSP frame field406(FIG. 4) and from the WLAN AP104to the TVWS database108in the database request202(FIGS. 2 and 4). The example TVWSP frames ofFIGS. 10 and 11can be communicated by the TVWS database108to the WLAN AP104in the database response204(FIGS. 2 and 5) and from the WLAN AP104to the wireless terminal114in the TVWSP frame field506(FIG. 5). In some example implementations, not all of the TVWSP frame types ofFIGS. 6,7,8,10, and11may be required for the wireless terminal114to obtain information or make requests to the TVWS database108. For example, if an AAA server is co-located with the TVWS database108, the wireless terminal114may not need to discover the address of the TVWS database108and, thus, would not use the database network address frame600.

Now turning toFIG. 6, the example database network address frame600may be used to retrieve a network address of the TVWS database108ofFIGS. 1 and 2(or any other TVWS databases accessible by the WLAN AP104). In the illustrated example ofFIG. 6, the database network address frame600includes a location field602, a database address field604, and an optional signature field606. The location field602is a variable length field that contains the location for which the wireless terminal114is requesting to access TVWS information (e.g., TVWS connectivity capabilities and/or requirement information). The location could be a current location of the wireless terminal114or a location at which the wireless terminal114is expected to operate at some future time. Thus, the wireless terminal114could indicate any location (not just its current location) for which TVWS connectivity information is desired. In this manner, information from the TVWS database108could be retrieved via the Internet112from a user's home (e.g., through Ethernet, USB or over any wireless RAT on the wireless terminal114) and then used for TVWS connectivity (e.g., via the TVWS access networks126a-cofFIG. 1) in another location at some later time. The location information could be in the form of, for example, a hotspot ID, latitude/longitude global positioning system (GPS) coordinates, region identifiers (e.g., municipality names), civic address, etc. Omitting location information in the location field602indicates a current location as determined by the access network in communication with the wireless terminal114.

The database address field604is a variable length field used to indicate a network address to which the WLAN AP104can send a database query (e.g., the database request202ofFIGS. 2 and 4) related to a TVWS access network at a location indicated in the location field602. That is, if the location field602indicates location C (FIG. 1), the database address field604provides the network address of the TVWS database108, because the TVWS database108stores information about the TVWS access network126cat location C.

In some example implementations, the database address field604could also be used as a search field. For example, the string “local” in the database address field604could be used to retrieve a network address of a local TVWS database, the string “all” in the database address field604could return a list of all relevant TVWS databases, and the string “free” in the database address field604could be used to retrieve network addresses for TVWS databases that are free to access. In addition, the database address field604could be used to implement a rich query mechanism to discover different types of TVWS databases meeting different types of criteria for different purposes and information, for example.

In a valid response (i.e., success) from the WLAN AP104, the database address field604provides a network address of a TVWS database (e.g., the TVWS database108) meeting the criteria (e.g., location and/or any other criteria) provided by the wireless terminal114. For example, the network address of the TVWS database could be a uniform resource identifier (URI) (e.g., http://White_Space.regulator-fcc.org). In some example implementations, the network address of a local copy of a TVWS database could be returned (e.g., http://White_Space.rim.waterloo.org) and/or a list of alternative network addresses could be returned depending upon the information stored in those alternative TVWS databases. In some example implementations, a different uniform resource name (URN) could be used to address TVWS databases. Such a URN could be ‘tvbd’ rather than ‘http’ (e.g., tvbd://White_Space.regulator-fcc.org). The wireless terminal114can address further database requests to the provided network address to, for example, retrieve TVWS connectivity information (e.g., the TVWS connectivity information122ofFIG. 1) from the TVWS database108or send any other types of requests to the TVWS database108.

In some example implementations, the database network address frame600may also include information indicating whether TVWS databases require TVBDs to register therewith before allowing the TVBDs to access information stored in those TVWS databases. In some example implementations, TVBDs required to register with TVWS databases may be devices with fixed locations that supply a fixed set of GPS coordinates. The database network address frame600may also include information specifying the type of information parameters (e.g., authentication credentials, username/password, payment tokens, etc.) required to register wireless terminals with the TVWS databases.

In example implementations in which a TVWS database is located within a cellular core network (not shown) to which an AP (e.g., the WLAN AP104, the TVWS APs128a-cofFIG. 1, or a cellular access network AP) is connected, a network address of the TVWS database108may not be required. In such implementations, the TVWS database could be accessed directly using an IEEE® 802.11 3GPP Cellular Network Information frame (e.g., a generic container) shown inFIG. 13and discussed in detail below. Also in such example implementations, the capabilities of the AP (connected to the cellular network) related to network reachability of the TVWS databases (e.g., as indicated in the TVWSD field304ofFIG. 3) and the capabilities of the AP to connect with wireless terminals using a TVWS protocol and frequency (e.g., as indicated in the TVWSC field302ofFIG. 3) may be communicated by the AP in accordance with the access network and discovery selection function (ANDSF) defined in 3GPP TS 24.312 and/or in accordance with IEEE® 802.21 information servers (IS).

In the illustrated example ofFIG. 6, the signature field606is an optional field that can transmit a message integrity check (MIC) to provide message integrity with an AAA server (e.g., the AAA server1402ofFIG. 14) for instances in which registration or authentication is required to communicate with the TVWS database108. When such registration or authentication is required, a security parameter in the signature field606could be mandated by an AAA protocol (e.g., the RADIUS protocol or Diameter protocol) between the NAS106and the TVWS database108.

FIG. 7depicts an example database registration frame700that may be used by TVBDs (e.g., TVBDs with fixed locations) to register with TVWS database108ofFIGS. 1 and 2. In the illustrated example, the database registration frame700includes a device identifier field702, a location field704, and a database address field706. The device identifier field702is a variable field that stores an identification and/or credential, which may be mandated by an operator (e.g., an Internet/network service provider, a services provider, a database host, etc.) of the TVWS database108. In the United States of America, such an identification and/or credential could be a certificate based on the Federal Communications Commission (FCC) ID of the device.

The location field704is similar to the location field602ofFIG. 6, and the database address field706is used to communicate the network address received by the wireless terminal114in the database address field604ofFIG. 6. In communicating the database registration frame700, the wireless terminal114requests registration with the TVWS database108based on its device identifier and/or credential to perform queries or other requests to the TVWS database108(which is denoted by the network address in the database address field706) related to a TVWS access network at the location specified in the location field704. In some example implementations, other fields (e.g., authentication and/or registration information fields) could be added to the database registration frame700, as required by the addressed TVWS database.

FIG. 8depicts an example database request frame800that may be used in connection with the database request202ofFIGS. 2 and 4to send requests to the TVWS database108. In the illustrated example, the database request frame800includes a request ID field802, a request type field804, a request command information field806, a location field808, a database address field810, and a time field812. In the illustrated example, the request ID field802is a fixed length field that stores values corresponding to unique numbers that uniquely identify each request. These request IDs are used to identify corresponding responses from the TVWS database108.

The request type field804is a fixed length field that stores a request type value indicative of the type of request being made in each database request. Example request types are shown in an example request type values data structure900ofFIG. 9. The request command information field806is used to store a query, request, or other information sent to the TVWS database108. The information that may be stored in the request type field804and the request command information field806is described in greater detail below in connection withFIG. 9.

The location field808is similar to the location fields602(FIGS. 6) and 704(FIG. 7), and the database address field810is similar to the database address field706ofFIG. 7.

In the illustrated example, the time field812is a variable length field that may be used by the wireless terminal114to request information from the TVWS database108at a future time (e.g., there may be a prescheduled TV primary service, which would occupy some of the TVWS bands, so that these TVWS bands would no longer be available at the requested location at that future time).

In some example implementations, the database registration frame700and the database request frame800may be combined so that a TVBD can register and receive a channel assignment in the same response (e.g., the database response204ofFIGS. 2 and 5). In such implementations, the database request would be generated with a corresponding request type identifier (e.g., a database registration and channel request type ‘7’ shown inFIG. 9) in the request type field804.

Turning toFIG. 9, the example request type values data structure900includes different request types that can be indicated in the request type field804of the database request frame800ofFIG. 8to indicate different types of requests communicated to the TVWS database108. In the illustrated example ofFIG. 9, a request type of ‘1’ indicates a database query request for which the request command information field806ofFIG. 8contains a query for information from the TVWS database108. The request command information field806allows the wireless terminal114to send any type of query protocol (e.g., http GET, SQL, etc.) to the TVWS database108. For example, a query could be of many different types, depending on the amount and detail of information sought to be retrieved. Example queries include: (a) requesting all information (e.g., a mirror of the TVWS database108); (b) requesting all information for a particular location (e.g., for the location indicated in the location field808); (c) requesting information updates in a particular location (e.g., updates to network connectivity information that occurred since a particular time); and/or (d) requesting a listing of available TVWS channels for a particular location (and the radius of usage for each channel).

A request type of ‘2’ indicates a database update request for which the request command information field806ofFIG. 8contains a request for an update from the TVWS database108that could, for example, include an identifier of a specific update to TVWS network connectivity information. To make such an update request, any type of query protocol (e.g., http GET, SQL, etc.) could be used. Example update requests include: (a) a request to retrieve a most recent update; (b) a request to retrieve a specific update (e.g., using an update identifier); (c) a request to retrieve all updates having occurred during the previous 24 hours (or other time period); and (d) a request to retrieve all updates for a particular location having occurred during the previous 24 hours (or other time period).

A request type of ‘3’ indicates a database upload request for which the request command information field806contains a request to upload information to the TVWS database108and also contains the information to be uploaded. The upload request could be provided in the request command information field806using any type of query protocol (e.g. http GET, SQL, etc.). In some example implementations, the wireless terminal114may provide the upload information in a free format. Alternatively or additionally, the upload information could be provided in accordance with required database parameters, which could be retrieved from the TVWS database108(e.g., using a request type of ‘4’ described below). To upload extra information from the device to the TVWS database108, multiple database upload requests may be transmitted in seriatim as many times as required.

A request type of ‘4’ indicates a database access parameters request for which the request command information field806contains a request to determine the type of database access parameters that may be required by the TVWS database108to upload information. Such database access parameters may indicate the requirement of a username to allow access, or the parameters could be more complex such as a set of parameters (e.g., power level, authentication credentials, payment tokens, etc.).

In some example implementations, wireless terminals may be required to provide their location and power level to the TVWS database108, prior to operation on a particular RAT. In some example implementations, such data access parameters would have to be transmitted through another RAT-b (e.g., an IEEE® 802.11 RAT) of a wireless terminal, prior to RAT-a (e.g., a TVWS RAT) operation of that wireless terminal.

For the database access parameters request (e.g., a request type of ‘4’), the request command information field806may be left blank. A response information field of a database response frame (e.g., the database response frames ofFIGS. 10 and 11) would contain a list of parameter IDs, to indicate which parameters are required.

A request type of ‘5’ indicates a database modification request for which the request command information field806contains a request to modify (e.g., add, change, or delete) information in the TVWS database108. For this request type, the request command information field806may contain any type of query protocol (e.g. http GET, SQL, etc.) for sending to the TVWS database108to perform the requested modification. In some example implementations, the database modification request (e.g., the request type of ‘5’) can be used as an operation and maintenance type of command. In addition, the database modification request may be restricted to certain users. In some example implementations, the database modification request could alternatively be implemented using the database upload request (e.g., a request type of ‘3’)

A request type of ‘6’ indicates a database validation request for which the request command information field806contains a request to the TVWS database108to confirm whether previously retrieved information stored in the wireless terminal114(or at a data store local to, for example, the WLAN AP104) is still valid. For example, the wireless terminal114may periodically request such validations to ensure that the information it is using to connect to a TVWS access network is still valid and/or optimal. In addition, data stores local to WLAN APs or TVWS APs may store local copies of some or all of the database information from the TVWS database108to facilitate responding relatively quicker and more efficiently to queries from wireless terminals (e.g., the wireless terminal114). In such instances, the local data stores can use database validation requests to determine when information stored therein is invalid relative to information in the TVWS database108.

To perform the database validation request, the request command information field806allows any type of query protocol (e.g., http GET, SQL, etc.) to be sent to the TVWS database108to perform the validation. An example manner of performing a database validation request involves identifying the information desired to be validated and the time at which the information was retrieved from the TVWS database108.

A request type of ‘7’ indicates a database registration and channel request for which the request command information field806contains a request to register with the TVWS database108and receive a channel assignment from the TVWS database108in the same response from the TVWS database108that also confirms the registration therewith.

A request type of ‘8’ indicates a security parameter request for indicating a security key exchange for which the request command information field806contains key information (e.g., a Diffie-Hellman key information) for developing security parameters between the wireless terminal114and the TVWS database108.

FIG. 10depicts an example database response frame1000that may be used to communicate information from the TVWS database108to the wireless terminal114ofFIGS. 1 and 2. In the illustrated example, the database response frame1000includes a returned request ID field1002and a response information field1004. The returned request ID field1002is a fixed field to store values that uniquely identify a corresponding original request (e.g., a request sent using the database request frame800ofFIG. 8). For example, the values stored in the returned request ID field1002by the TVWS database108correspond to request IDs stored in the request ID field802of the database request frame800. In addition, the returned request ID field1002enables the wireless terminal114to detect duplicate (and/or dropped) responses. In some example implementations, to provide assurances that data in the received responses correspond to previously sent requests, the original request ID (stored in the request ID field802ofFIG. 8) may be hashed with a unique database identifier. When using hash techniques, the returned request ID may be longer (e.g., 2-times or 4-times longer).

The response information field1004is a variable length field that contains the response information from the TVWS database108in response to a corresponding original database request.

FIG. 11depicts an extended database response frame1100that may additionally or alternatively be used to communicate information from the TVWS database108to the wireless terminal114ofFIGS. 1 and 2. The extended database response frame1100may be used in example instances in which extended information fields can be used to facilitate transmitting more information from the TVWS database108to the wireless terminal114and/or the WLAN AP104. In addition, the extended information fields may be used to keep the frames ofFIGS. 6,7, and8to a reasonable length by including the extended information fields only in the responses.

Although not shown, other extended information fields could include a time stamp field and an error/warning/info code field to enable the wireless terminal114and/or the WLAN AP104to assess the current validity of information and/or a state of the TVWS database108.

FIG. 12depicts an example TVWS protocol (TVWSP) error/warning/info codes data structure1200including codes to inform the wireless terminal114(FIGS. 1 and 2) of error, warning, and/or other operating states of the TVWS database108(FIGS. 1 and 2). The codes shown inFIG. 12could be sent by the TVWS database108using the database response frame1000ofFIG. 10and/or the extended database response frame1100ofFIG. 11. In the illustrated example ofFIG. 12, the codes include a success code1202of ‘0’, a registration denied code1204of ‘1’, an information unavailable code1206of ‘2’, and a limited time use code1208of ‘3’. The success code1202indicates that the requested operation was successfully completed. The registration denied code1204indicates that the TVWS database108denied registration to a wireless terminal (e.g., the wireless terminal114). The information unavailable code1206indicates that queried information is unavailable in the TVWS database108. The limited time use code1208indicates that the TVWS database108has registered a wireless terminal for a limited duration.

FIG. 13depicts an example cellular network information frame1300for exchanging information with a TVWS database in a cellular network. In the illustrated example, the cellular network information frame1300is an IEEE® 802.11u 3GPP Cellular Network Information frame that provides a generic container (e.g., a payload) for use by an AP to exchange communications with a TVWS database located in a cellular network. In the illustrated example, the cellular network information frame1300includes an INFO ID field1302, a length field1304, and a payload field1306. The INFO ID field1302can store a code identifying the communication as a TVWS database query. The length field1304is used to indicate the size of the variable-length payload field1306. The payload field1306is used to encapsulate any of the TVWSP frames ofFIGS. 6-8,10, and11(or any other TVWSP frames) for exchanging information between an AP and the TVWS database in the cellular network.

FIG. 14depicts another example communication network1400in connection with an authentication, authorization, and accounting (AAA) server1402co-located with the TVWS database108in the external network110. In the illustrated example ofFIG. 14, wireless terminals are required to be authenticated and authorized by the AAA server1402to access the TVWS database108. Example authentication methods that may be employed by the AAA server1402include extensible authentication protocol (EAP) type authentication methods. The AAA server1402may be implemented using a Remote Authentication Dial In User Services (RADIUS) server or a Diameter server.

In the illustrated example ofFIG. 14, the AAA server1402uses an AAA protocol to enable exchanging TVWSP frames between the TVWS database108and the NAS106. This enables communicating requests and responses between the wireless terminal114and the TVWS database108based on an authentication policy. In example implementations in which the AAA server1402is implemented using a RADIUS server, the NAS106may use an example RADIUS time-length-value (TLV) structure1500ofFIG. 15to exchange information with the AAA server1402. In example implementations in which the AAA server1402is implemented using a Diameter server, the NAS106may use an example Diameter attribute-value-pair (AVP) structure1600ofFIG. 16to exchange information with the AAA server1402.

Turning toFIG. 15, the example RADIUS TLV structure1500includes a mandatory (‘M’) flag1502, a reserved (‘R’) flag1504, a TLV type field1506, a length field1508, and a TVWSP frame field1510. The ‘M’ flag1502is used to indicate whether use of the RADIUS TLV structure1500is required (e.g., ‘M’=1) to be communicated to the TVWS database108from the AAA server1402or whether it is optional (e.g., ‘M’=0) such that the AAA server1402may forward only a TVWSP frame (e.g., one of the TVWSP frames ofFIGS. 6-8) extracted from the RADIUS TLV structure1500to the TVWSP database108. In the illustrated example, the ‘R’ flag1504is set to zero (0). The TLV type field1506is used to indicate the type of TLV information that is being sent. An example TLV type for the TVWSP frames described herein could be indicated as a ‘TVWS_DP’ type to indicate that the information element in the TVWSP frame field1510is a TVWSP frame. The length field1508is used to indicate the size of the information element in the TVWSP frame field1510. The TVWSP frame field1510is used to encapsulate a TVWSP frame (e.g., the TVWSP frames ofFIGS. 6-8,10, and11) in the RADIUS TLV structure1500.

Turning toFIG. 15, the example Diameter AVP structure1600includes an AVP code field1602, a vendor (‘V’) flag1604, a mandatory (‘M’) flag1606, an encryption (‘P’) flag1608, an AVP length field1610, and a TVWSP frame field1612. The AVP code field1602is used to indicate the type of AVP information that is being sent. An example AVP code for the TVWSP frames described herein could be indicated by an AVP code indicating that the information element in the TVWSP frame field1612is a TVWSP frame. The ‘V’ flag1604is used to indicate whether the AVP information being sent is vendor specific. The ‘M’ flag1606is used to indicate whether use of the Diameter AVP structure1600is required (e.g., ‘M’=1) to be communicated to the TVWS database108from the AAA server1402or whether it is optional (e.g., ‘M’=0) such that the AAA server1402may forward only a TVWSP frame (e.g., one of the TVWSP frames ofFIGS. 6-8) extracted from the Diameter AVP structure1600to the TVWSP database108. The ‘P’ flag1608is used to indicate whether end-to-end encryption is required (e.g., ‘P’=1) or optional (e.g., ‘P’=0). The AVP length field1610is used to indicate the size of the information element in the TVWSP frame field1612. The TVWSP frame field1612is used to encapsulate a TVWSP frame (e.g., the TVWSP frames ofFIGS. 6-8,10, and11) in the Diameter AVP structure1600.

Referring now toFIG. 17, an example implementation of the wireless terminal114ofFIGS. 1 and 2is shown in block diagram form. In the illustrated example, the wireless terminal114includes a processor1702that may be used to control the overall operation of the wireless terminal114. The processor1702may be implemented using a controller, a general purpose processor, a digital signal processor, or any combination thereof

The wireless terminal114also includes a terminal message generator1704and a terminal data parser1706. The terminal message generator1704may be used to generate queries and/or requests (e.g., the AN request message116ofFIGS. 1 and 2) in accordance with request/query protocols and frame structures described herein. The terminal data parser1706may be used to retrieve frames of information from memory (e.g., a RAM1710) and retrieve particular information of interest from those frames. For example, the terminal data parser1706may be used to retrieve information communicated in the AN response message118ofFIGS. 1 and 2. Although the terminal message generator1704and the terminal data parser1706are shown as separate from and connected to the processor1702, in some example implementations, the terminal message generator1704and the terminal data parser1706may be implemented in the processor1702and/or in a wireless communication subsystem (e.g., a wireless communication subsystem1718). The terminal message generator1704and the terminal data parser1706may be implemented using any desired 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. Thus, for example, the terminal message generator1704and the terminal data parser1706, or parts thereof, could be implemented using one or more circuit(s), programmable processor(s), application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)), field programmable logic device(s) (FPLD(s)), etc. The terminal message generator1704and the terminal data parser1706, or parts thereof, may be implemented using instructions, code, and/or other software and/or firmware, etc. stored on a machine accessible medium and executable by, for example, a processor (e.g., the example processor1702). When any of the appended claims are read to cover a purely software implementation, at least one of the terminal message generator1704and the terminal data parser1706is hereby expressly defined to include a tangible medium such as a solid state memory, a magnetic memory, a DVD, a CD, etc.

The wireless terminal114also includes a FLASH memory1708, a random access memory (RAM)1710, and an expandable memory interface1712communicatively coupled to the processor1702. The FLASH memory1708can be used to, for example, store computer readable instructions and/or data. In some example implementations, the FLASH memory1708can be used to store one or more of the type of information and/or data structures discussed above in connection withFIGS. 6-13,15, and16. The RAM1710can also be used to, for example, store data and/or instructions.

The wireless terminal114is optionally provided with a security hardware interface1714to receive a subscriber identity module (SIM) card (or a universal SIM (USIM) card or a near field communication (NFC) secure element) from a wireless service provider. A SIM card may be used as an authentication parameter to authenticate the wireless terminal114for establishing a connection with a database (e.g., the TVWS database108ofFIG. 1), an access network (e.g., the WLAN access network104and/or the TVWS access networks126a-cofFIG. 1), and/or an external network (e.g., the external network110ofFIG. 1). The wireless terminal114is also provided with an external data I/O interface1716. The external data I/O interface1716may be used by a user to transfer information to the wireless terminal114through a wired medium (e.g., Ethernet, universal serial bus (USB), etc.). A wired data transfer path may, for example, be used to communicate with the TVWS database108.

The wireless terminal114is provided with a wireless communication subsystem1718to enable wireless communications with APs (e.g., the WLAN AP104and/or the TVWS APs128a-cofFIG. 1). Although not shown, the wireless terminal114may also have a long-range communication subsystem to receive messages from, and send messages to, a cellular wireless network. In the illustrated examples described herein, the wireless communication subsystem1718can be configured in accordance with the IEEE® 802.11 standard and/or a TVWS standard for communicating with TVWS access networks (e.g., the TVWS access networks126a-c). In other example implementations, the wireless communication subsystem1718can be implemented using a BLUETOOTH® radio, a ZIGBEE® device, a wireless USB device, a radio frequency identification (RFID) device, an NFC device, or an ultra-wideband (UWB) radio. In some example implementations, the wireless communication subsystem1718may be provided with multiple radio transceivers for multiple types of radio access technologies.

To enable a user to use and interact with or via the wireless terminal114, the wireless terminal114is provided with a speaker1720, a microphone1722, a display1724, and a user input interface1726. The display1724can be an LCD display, an e-paper display, etc. The user input interface1726could be an alphanumeric keyboard and/or telephone-type keypad, a multi-direction actuator or roller wheel with dynamic button pressing capability, a touch panel, etc. In the illustrated example, the wireless terminal114is a battery-powered device and is, thus, provided with a battery1728and a battery interface1730.

Turning now toFIG. 18, an example processor system1800for use in a network (e.g., the network100ofFIG. 1and/or the network1400ofFIG. 14) is shown in block diagram form. Processor systems similar or identical to the processor system1800may be used to implement the WLAN AP104, the NAS106, the TVWS APs128a-cofFIG. 1, and/or the AAA server1402ofFIG. 14. The processor system1800includes a processor1802to perform the overall operations of the processor system1800. In addition, the processor system1800includes a network message generator1804to generate messages (e.g., the database request202ofFIGS. 2 and 4and the AN response message118ofFIGS. 1,2, and5) and a network data parser1806to retrieve information from received messages (e.g., the AN request message116ofFIGS. 1,2, and4and the database response204ofFIGS. 2 and 5). The network message generator1804and the network data parser1806may be implemented in the processor1802and/or a communication subsystem (e.g., a wireless communication subsystem1812and/or a network interface1814) using any combination of hardware, firmware, and/or software including instructions stored on a computer-readable medium.

The processor system1800also includes a FLASH memory1808and a RAM1810, both of which are coupled to the processor1802. The FLASH memory1808may be configured to store one or more of the type of information and/or data structures discussed above in connection withFIGS. 6-13,15, and16.

In some example implementations (e.g., in the WLAN AP104and the TVWS APs128a-cofFIG. 1), to communicate with wireless terminals such as the wireless terminal114, the processor system1800is provided with a wireless communication subsystem1812, which may be substantially similar or identical to the wireless communication subsystem1718(FIG. 17) of the wireless terminal114. To exchange communications with the TVWS database108(and/or any intermediate network entities such as the NAS106ofFIGS. 1 and 14and the AAA server1402ofFIG. 14), the processor system1800is provided with a network interface1814.

FIGS. 19 and 20depict example flow diagrams representative of processes that may be implemented using, for example, computer readable instructions that may be used to obtain TVWS connectivity information from a database (e.g., the TVWS database108ofFIGS. 1 and 2) indicative of capabilities and requirements for connecting to a TVWS access network (e.g., one of the TVWS access networks126a-cofFIG. 1). The example processes ofFIGS. 19 and 20may be performed using one or more processors, controllers, and/or any other suitable processing devices. For example, the example processes ofFIGS. 19 and 20may be implemented using coded instructions (e.g., computer readable instructions) stored on one or more tangible computer readable media such as flash memory, read-only memory (ROM), and/or random-access memory (RAM). As used herein, the term tangible computer readable medium is expressly defined to include any type of computer readable storage and to exclude propagating signals. Additionally or alternatively, the example processes ofFIGS. 19 and 20may be implemented using coded instructions (e.g., computer readable instructions) stored on one or more non-transitory computer readable media such as flash memory, read-only memory (ROM), random-access memory (RAM), cache, or any other storage media in which information is stored for any duration (e.g., for extended time periods, permanently, brief instances, for temporarily buffering, and/or for caching of the information). As used herein, the term non-transitory computer readable medium is expressly defined to include any type of computer readable medium and to exclude propagating signals.

Alternatively, some or all of the example processes ofFIGS. 19 and 20may be implemented using any combination(s) of application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)), field programmable logic device(s) (FPLD(s)), discrete logic, hardware, firmware, etc. Also, some or all of the example processes ofFIGS. 19 and 20may be implemented manually or as any combination(s) of any of the foregoing techniques, for example, any combination of firmware, software, discrete logic and/or hardware. Further, although the example processes ofFIGS. 19 and 20are described with reference to the flow diagrams ofFIGS. 19 and 20, other methods of implementing the processes ofFIGS. 19 and 20may be employed. For example, the order of execution of the blocks may be changed, and/or some of the blocks described may be changed, eliminated, sub-divided, or combined. Additionally, any or all of the example processes ofFIGS. 19 and 20may be performed sequentially and/or in parallel by, for example, separate processing threads, processors, devices, discrete logic, circuits, etc.

Now turning toFIG. 19, example processes1902depict operations that may be performed by a wireless terminal (e.g., the wireless terminal114ofFIGS. 1 and 2) or any other TVBD to exchange requests and responses with an access network access point (e.g., the WLAN AP104and/or the TVWS APs128a-cofFIG. 1) and a database (e.g., the TVWS database108ofFIG. 1). Example processes1904depict operations that may be performed by an access network (e.g., the WLAN AP104and/or the NAS106of the WLAN access network102ofFIG. 1or the TVWS APs128a-cofFIG. 1). In some example implementations, the processes ofFIG. 19may be used to provide the wireless terminal114new and/or updated TVWS connectivity information indicative of capabilities and requirements for connecting to a TVWS access network (e.g., the TVWS access networks126a-cofFIG. 1). In other example implementations, the processes ofFIG. 19may be used to perform any other TVWS database related operations requested by the wireless terminal114as discussed above in connection with the TVWSP frames ofFIGS. 6-8and the request type values data structure ofFIG. 9. In addition, the processes ofFIG. 19may be performed while the wireless terminal114is in a non-associated state (or associated state) relative to an AP with which the wireless terminal114is communicating to access the TVWS database108.

Initially, the wireless terminal114receives a beacon signal (e.g., the beacon signal120ofFIG. 1) (block1906). Alternatively, the wireless terminal114may receive a probe response message (e.g., the AN response message118ofFIGS. 1,2, and5) from an AP at block1906, in response to a probe request message116from the wireless terminal114. The wireless terminal114determines the TVWS connect capability of the AP that broadcast the beacon signal (block1908). For example, if the beacon signal120(or probe response) was transmitted by the WLAN AP104ofFIG. 1, the beacon signal120(or probe response) would indicate in the TVWSC field302(FIG. 3) that the WLAN AP104is not capable of connecting with wireless terminals using a TVWS protocol and frequency. If, instead, the wireless terminal114received a beacon signal (or probe response) from one of the TVWS access networks126a-c, the beacon signal (or probe response) would indicate in the TVWSC field302that the TVWS access network is capable of connecting with wireless terminals using a TVWS protocol and frequency. If the AP (e.g., one of the TVWS APs128a-cofFIG. 1) is capable of connecting with the wireless terminal114using a TVWS protocol and frequency, further communications with the AP are performed via a TVWS connection. Otherwise, further communications with the AP are performed using a communication protocol compatible with the AP such as, for example, an IEEE® 802.11 protocol, a cellular protocol, a WiMAX protocol, etc.

The wireless terminal114determines whether the AP that broadcast the beacon signal is capable of connecting with a TVWS database (e.g., the TVWS database108) (block1910). Alternatively, the wireless terminal114may receive a probe response message (e.g., the AN response message118) from an AP at block1906, in response to a probe request message (e.g., the AN request message116ofFIGS. 1,2, and4) from the wireless terminal114. For example, the wireless terminal114may retrieve information from the TVWSD field304ofFIG. 3to determine whether the TVWS database108is reachable by the AP that broadcast the beacon signal (or probe response messages).

When the wireless terminal114determines that the TVWS database108is reachable by the AP that broadcast the beacon signal (block1910) (or the sent the probe response message), the wireless terminal114sends a database address request (block1912) to the AP. The database address request may be formatted and sent using the AN request message116and the database request202ofFIGS. 1,2, and4based on the database network address frame600ofFIG. 6as discussed above in connection withFIGS. 1,2,4, and6.

The AP receives the database address request (block1914) and retrieves one or more network address(es) for one or more reachable TVWS databases based on the information in the database address request (block1916). The AP sends the database address(es) to the wireless terminal114(block1918). If the AP cannot locate any database addresses matching the criteria in the database address request, the AP can instead send an error/warning/info code (e.g., the information unavailable code1206ofFIG. 12) to the wireless terminal114at block1918.

The wireless terminal114receives the database address(es) (block1920) from the AP. The wireless terminal114can select a TVWS database (e.g., the TVWS database108) with which to communicate (block1922) and determines whether the selected TVWS database108requires the wireless terminal114to register therewith (block1924). If the TVWS database108requires wireless terminal registration (block1924), the wireless terminal114sends a registration request to the AP (block1926). In the illustrated example, the wireless terminal114can format and send the registration request using the AN request message116ofFIGS. 1,2, and4based on the database registration frame700ofFIG. 7as discussed above in connection withFIGS. 1,2,4, and7.

In the illustrated example ofFIG. 19, the AP may perform the operations of blocks1928,1930,1932,1934,1936, and1938described below to process requests/queries (e.g., the AN request message116and the database request202ofFIGS. 1,2, and4) sent by the wireless terminal114for delivery to a TVWS database (e.g., the TVWS database108).

The AP receives the registration request from the wireless terminal114(block1928). For example, the AP may receive the registration request from the wireless terminal in the AN request116(FIGS. 1,2, and4) formatted in accordance with the database registration frame700(FIG. 7). If the AP determines that the TVWS database108requires authentication (block1930), the AP (or NAS106ofFIGS. 1 and 14) encapsulates the registration request in an authentication frame (e.g., one of the RADIUS TLV structure1500ofFIG. 15or the Diameter AVP structure1600ofFIG. 16).

The AP sends the registration request to the TVWS database108(block1934). For example, the AP may send the registration request to the TVWS database108in the database request202(FIG. 2) using the format of the database registration frame700(FIG. 7). For instances when authentication is required, the AP sends the authentication-encapsulated registration request to the TVWS database108via the AAA server1402ofFIG. 14.

The AP receives a database registration response from the TVWS database108(block1936) and sends a response to the wireless terminal114. For example, the AP may receive the database registration response from the TVWS database in the database response204ofFIG. 2based on a format according to the database response frame1000ofFIG. 10or the extended database response frame1100. In addition, the AP may forward the information from the database registration response to the wireless terminal114in the AN response message118ofFIGS. 1,2, and5. The contents of the database registration response may be an error/warning/informative code (e.g., success, registration denied, limited time use, etc.) from the TVWSP error/warning/info codes data structure1200ofFIG. 12.

The wireless terminal114receives the database registration response (block1940). If the registration was successful (block1942) or if the TVWS database108does not require registration (block1924), the wireless terminal114sends a request to access information in the TVWS database108to the AP (block1944). In the illustrated example, the wireless terminal114can format and send the access request using the AN request message116ofFIGS. 1,2, and4based on the database request frame800ofFIG. 8as discussed above in connection withFIGS. 1,2,4, and8. The request may be a request for TVWS connectivity information (e.g., the TVWS connectivity information122ofFIG. 1) describing capabilities and requirements of one or more of the TVWS access networks126a-cpertaining to the one or more locations specified by the wireless terminal114in the request. Alternatively, the request sent by the wireless terminal114may be any other type of request including one or more of the requests described above in connection with the request type values data structure900ofFIG. 9.

The AP receives the request (e.g., the AN request message116ofFIGS. 1,2, and4) (block1928). If authentication is required (block1930), the AP (or NAS) encapsulates the request in an authentication frame (e.g., one of the RADIUS TLV structure1500ofFIG. 15or the Diameter AVP structure1600ofFIG. 16). The AP sends the request (e.g., the database request202ofFIGS. 2 and 4) to the TVWS database108(block1934) (in an authentication frame, if required), receives a response (e.g., the database response204ofFIGS. 2 and 5) from the TVWS database108(block1936), and sends a response (e.g., the AN response message118ofFIGS. 1,2, and5) to the wireless terminal114(block1938).

The wireless terminal114receives the response from the AP (block1946) and stores (and/or uses) the information from the TVWS database108(block1948). For example, if the received information is TVWS connectivity information for connecting to one of the TVWS access networks126a-c(FIG. 1), the wireless terminal114can store the received TVWS connectivity information and subsequently (or immediately) use the TVWS connectivity information to connect to one of the TVWS access networks126a-c. After storing/using the TVWS information (block1948) or if the TVWS database registration was not successful (block1942) or if the AP exchange communications with a TVWS database (block1910), the example processes ofFIG. 19end.

Now turning toFIG. 20, the example flow diagram is representative of computer readable instructions that may be used to push TVWS connectivity information updates from the TVWS database108to a registered terminal (e.g., the wireless terminal114or any other TVBD) without needing the registered terminal to request such updated information. In the illustrated example ofFIG. 20, example processes2002depict operations that may be performed by a wireless terminal (e.g., the wireless terminal114ofFIGS. 1 and 2) or any other TVBD to register with the TVWS database108and receive broadcast or push updates therefrom. Example processes204depict operations that may be performed by the TVWS database108to register wireless terminals and push or broadcast TVWS connectivity information updates to registered wireless terminals.

Initially, the wireless terminal114requests to register with the TVWS database108(block2006). The wireless terminal114may perform the registration request by sending a message (e.g., the AN request message116ofFIGS. 1,2, and4) format in accordance with the database registration frame700(FIG. 7) to the WLAN AP104or any of the TVWS APs128a-c. The TVWS database108receives and registers the wireless terminal114(block2008). The TVWS database108sends a registration confirmation to the wireless terminal114(block2010), and the wireless terminal114receives the registration confirmation (block2012).

After some time, the TVWS database108receives TVWS access network connectivity parameter changes (block2014). Such updated information may be received from one or more TVWS access networks (e.g., one or more of the TVWS access networks126a-cofFIG. 1) in response to the one or more TVWS access networks detecting that it needs to change its connectivity parameters. For example, if a TVWS access network detects that a current one of its available channels will no longer be available (e.g., it is needed for another use such as broadcasting emergency, news information, operation of other wireless devices (e.g., wireless microphones) in the same or nearby frequencies, etc.), the TVWS access network can send such updated channel availability information to the TVWS database108for storing in the TVWS connectivity information122. In some example implementations, the TVWS access network may also send time information along with the connectivity information update indicative of when the updated information will take effect and/or the duration for which the updated information will be valid.

Although certain methods, apparatus, and articles of manufacture have been described herein, the scope of coverage of this patent is not limited thereto. To the contrary, this patent covers all methods, apparatus, and articles of manufacture fairly falling within the scope of the appended claims either literally or under the doctrine of equivalents.