Source: http://www.google.com/patents/US20100024007?ie=ISO-8859-1&dq=5,815,794
Timestamp: 2014-08-29 00:30:17
Document Index: 449206474

Matched Legal Cases: ['art 200', 'art 200', 'art 200', 'art 200', 'art 200', 'art 200', 'art 400', 'art 400', 'art 400', 'art 400', 'art 400', 'art 400']

Patent US20100024007 - Affirming network relationships and resource access via related networks - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign in<nobr>Advanced Patent Search</nobr>PatentsA technique for providing a prediction as to whether a resource will be accessible to a user is described. The technique can involve comparing asserted membership in a wireless realm with membership records. Advantageously, a user can be made aware of the likelihood of access to a resource before attempting...http://www.google.com/patents/US20100024007?utm_source=gb-gplus-sharePatent US20100024007 - Affirming network relationships and resource access via related networksAdvanced Patent SearchPublication numberUS20100024007 A1Publication typeApplicationApplication numberUS 12/336,492Publication dateJan 28, 2010Filing dateDec 16, 2008Priority dateJul 25, 2008Publication number12336492, 336492, US 2010/0024007 A1, US 2010/024007 A1, US 20100024007 A1, US 20100024007A1, US 2010024007 A1, US 2010024007A1, US-A1-20100024007, US-A1-2010024007, US2010/0024007A1, US2010/024007A1, US20100024007 A1, US20100024007A1, US2010024007 A1, US2010024007A1InventorsMatthew S. GastOriginal AssigneeTrapeze Networks, Inc.Export CitationBiBTeX, EndNote, RefManPatent Citations (2), Classifications (11), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetAffirming network relationships and resource access via related networksUS 20100024007 A1Abstract A technique for providing a prediction as to whether a resource will be accessible to a user is described. The technique can involve comparing asserted membership in a wireless realm with membership records. Advantageously, a user can be made aware of the likelihood of access to a resource before attempting to reach the resource.
receiving a query transport protocol (QTP) query including an asserted membership in a wireless realm; comparing the asserted membership in the wireless realm to membership records; transmitting a QTP query response when the asserted membership matches the membership records, indicating an association possibility. 2. The method of claim 1, wherein access to the network resource is allowed as a benefit of membership in the wireless realm, further comprising identifying a relationship between the asserted membership in the wireless realm and a network resource.
3. The method of claim 1, wherein membership in the wireless realm does not include access to the network resource, further comprising predicting a prospective denial of access to a network resource.
4. The method of claim 1, wherein access to the network resource is allowed, but access to at least one other resource on the network is not allowed, further comprising predicting an allowance of access to a network resource as a benefit of membership in the wireless realm.
5. The method of claim 1, wherein access to all other resources via the network is disallowed, further comprising predicting an allowance of access to a network resource independent of membership in the wireless realm.
6. The method of claim 1, wherein absence of membership in the wireless realm is indicative of access to the network, further comprising denying access to a network resource, the denial determined by the membership in the wireless realm.
7. The method of claim 1, further comprising, defining access to a network resource, wherein there is a relationship between the membership in the wireless realm and third party indicating access to the network resource.
transmitting from a wireless station a query transport protocol (QTP) query including an asserted membership in a wireless realm; receiving a QTP query response including a prediction that the asserted membership is associated with permission to access a network resource; attaching to an access point (AP), wherein attaching to the AP couples the wireless station to the network resource. 9. The method of claim 8, further comprising, receiving a plurality of subsequent indications of relationships between a plurality of networks and the asserted membership in the wireless realm, wherein the plurality of subsequent relationships includes at least one prediction of allowance to the network resource.
10. The method of claim 9, further comprising, displaying one or more networks, wherein each of the one or more networks predicts that access to the network resource will be allowed for the asserted membership.
11. The method of claim 8, further comprising, displaying one or more networks including networks predicted to allow access to the network resource via one or more other networks.
12. The method of claim 8, further comprising, selecting one or more criteria indicative of membership in the wireless realm and including the criteria in the QTP query.
13. The method of claim 8, further comprising, accessing the network resource in accordance with the prediction that the wireless station will be allowed access to the network resource.
14. The method of claim 8, further comprising, refraining from attempting to access the network resource in accordance with an indication that the wireless station will be denied access to the network resource.
15. The method of claim 8, further comprising, automatically accessing the network resource upon indication from a first access point that the access point will allow the wireless station to access the network resource via the access point.
a query front-end processor (QFP) engine; a membership comparison engine coupled to the QFP engine; a network resource name (NRN) table coupled to the membership comparison engine; a network resource access prediction engine coupled to the membership comparison engine and to the query front-end processor; wherein in operation, the QFP engine receives a query transport protocol (QTP) query from a station, the QTP query including an asserted membership in a wireless realm; the QFP engine provides the asserted membership to the membership comparison engine to compare the asserted membership with configured memberships from the NRN table; the membership comparison engine provides a result of the comparison to the network resource access prediction engine to predict whether the station will be allowed to access a network resource; the network resource access prediction engine provides an access prediction to the QFP engine; the QFP engine transmits a QTP query response indicating the access prediction. 17. The system of claim 16, wherein, the NRN table includes multiple records of third parties allowed access to the wireless realm based on membership in other wireless realms.
18. The system of claim 16, wherein the network resource access prediction engine predicts access to a fringe of a mesh network will be allowed.
19. Them system of claim 16, further comprising a controller defining control of an enterprise network, wherein the controller includes the QFP engine, the NRN table, the membership comparison engine, and the network resource access prediction engine.
20. The system of claim 16, further comprising an access point, wherein the access point includes the QFP engine, the NRN table, the membership comparison engine, and the network resource access prediction engine. Description
CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Application 61/083,876, filed Jul. 25, 2008, entitled ROAMING CONSORTIUM, which is hereby incorporated by reference in its entirety.
BACKGROUND In 802.11 network communications, a user of a wireless station may desire to access a network resource. Often a plurality of different access points will be available to a user. At times, some of these networks may provide access to the network resource, whereas others may not. For example, consider wireless network access points in an airport where networks compete for users by offering competitive network pricing.
Networks may or may not offer service to a network resource without cost. Often, network access is provided with a cost. However, there are times when a network provider may offer selective network access without cost such as where economic benefits will inure to the network provider for doing so.
For example, consider a partnership or agreement between network owners or operators that defines permission for users to use networks. The network owners can enlarge their networks by sharing access to their networks. At times the access can be provided without additional cost to the user over the user's payment to access one of many such networks.
For example, multiple networks in different countries or regions could agree to allow common use of each network in each country or region. The use could be without additional cost to that paid for the use in a user's home country or region.
Alternatively, a first commercial establishment may allow access to specific network resources offered by other commercial establishments. The commercial establishments can benefit by sharing patrons.
For example, a hotel might offer free network access to airport/airline websites from within the hotel and the airport/airlines might similarly offer reciprocal access from within an airport. This would allow for mutually beneficial use of the networks leading to repeat business and other economic benefits to the hotel and airport/airline.
When many commercial establishments or networks present a user with access points the user may not know that the networks will allow access without cost. Often the user can have permission to use a partner network to reach a network resource, but will have to try different networks before finding one that she has permission to use. The user can be left wondering which networks are available to her. Such a user could waste time trying to determine which networks will allow access to the network resource.
A technique for providing a prediction as to whether a resource will be accessible to a user is described. The technique can involve comparing asserted membership in a wireless realm with membership records. Advantageously, a user can be made aware of the likelihood of access to a resource before attempting to reach the resource.
Typically, one or more access points (APs) in range of a station associated with the user can be identified as providing direct or indirect access to a network resource. The APs providing such access, with or without cost depending upon the implementation and/or configuration, can be presented to the user for selection. If the user can attach to the AP and has appropriate membership rights, then the user can access the network resource.
A potential authentication indication (PAI) engine can determine whether it is possible for a station to authenticate to a network. A user of the station can assert membership in a wireless realm, and send the asserted membership to the PAI engine. The PAI engine can compare the asserted membership to membership records, and indicate whether a user having the asserted membership can potentially authenticate with a target network.
Advantageously, the PAI can inform a user of the possibility that the user can authenticate to a target network before trying to authenticate. The PAI can provide a list of networks and the user can select one from the list. By identifying possible networks, the user can save time by avoiding networks that will not allow authentication. Also, the station associated with the user may save power by avoiding unnecessary attempts.
A system designed in accordance with the technique can include a query front-end processing (QFP) engine, a membership comparison engine coupled to the QFP engine, a network resource name (NRN) table coupled to the membership comparison engine, and a network resource access prediction engine coupled to the membership comparison engine and the QFP engine. The QFP engine, membership comparison engine, and NRN table can work together to indicate to a user of a station whether it is possible for the station to authenticate to a target network.
In a method designed with the technique, a station can transmit a query transport protocol (QTP) query to an AP. The query can include an asserted membership of a user in a network, such as a wireless realm, home network, or other applicable network. A response to the QTP query can include an indication as to whether authentication to a target network is possible. Thus, the QTP query is useful in eliciting a response from an AP that indicates whether it is possible to authenticate to a target network. The target network need not be the network in which membership is asserted.
BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 depicts an example of a system for determining whether it is possible for a station with a user having an asserted membership to authenticate to a target network.
FIG. 2 depicts a flowchart of an example of a process for predicting access to a network resource for a station, and attaching if the prediction is favorable.
FIG. 3 depicts an example of a potential authentication indication (PAI) engine.
FIG. 4 depicts a flowchart of an example of a method for predicting access to a network resource.
FIG. 5 depicts an example of an infrastructure network including potential locations for a PAI engine.
FIG. 6 depicts an example of a system in which a station in the context of an infrastructure network queries for a prediction as to whether it is possible to access a resource.
FIG. 7 depicts an example of a system in which a station, in the context of multiple networks, queries whether a network resource is predicted to be accessible to a user of the station.
FIG. 1 depicts an example of a system 100 for determining whether it is possible for a station with a user having an asserted membership to authenticate to a target network. The system 100 includes a station 102, an access point (AP) 104, and a potential authentication indication (PAI) engine 106. The station 102 is coupled to the AP 104 and the AP 104 is coupled to the PAI engine 106.
In the example of FIG. 1, the station 102 can include a laptop, a wireless telephone, portable digital assistant (PDA), desktop computer, or any other applicable computing device capable of communication on a wireless network. A �station,� as used herein, may or may not be referred to as a device with a media access control (MAC) address and a physical layer (PHY) interface to the wireless medium that comply with the Institute of Electrical and Electronic Engineers (IEEE) 802.11 standard. In general, a station can comply with any wireless standard or none at all, and may have any known or convenient interface to a wireless or other medium.
The station 102 can include a radio capable of generating signals compatible with communication on one or more networks. The station 102 can transmit and receive data as radio frequency (RF) signals. The radio can operate on any band in which a wireless standard, e.g., 802.11, is standardized. The station 102 can also include multiple radios. For example, the station 102 could include a 2.4 and a 5 GHz radio.
The station 102 can be associated with membership in a network. The network can be, for example, a wireless realm. A �wireless realm� can be a network operated by a particular entity, such as a wireless access provider. A user of the station 102 can purchase or otherwise be given a membership allowing use of the wireless realm such as by various �hot spots� or locations where the entity provides wireless access. At times the entity responsible for the network partners with other wireless access providers to provide access to shared networks. The station 102 can be used to access a resource of a network through the network or a shared network. Of course, the station 102 can also be used to access the resource through some other network, such as a free or subscription network.
In the example of FIG. 1, the AP 104 is in radio communication with the station 102. The AP 104 can retransmit received wireless signals over, for example, an Ethernet connection. The AP can be implemented as a station, but is generally referred to as an AP in this paper so as to distinguish the AP 104 from the station 102. Depending upon the context and/or implementation, the station 102 and AP 104 could be referred to as stations, or the station 102 could be referred to as a non-AP station.
In the example of FIG. 1, the PAI engine 106 can include special purpose hardware, firmware, software, system, or arrangement operable to predict access to a network resource. Modules of an example PAI engine are discussed later with reference to FIG. 2.
In the example of FIG. 1, in operation, the station 102 transmits a generic query transport protocol (QTP) query to the AP 104. The QTP query can include a domain name container defining membership in a wireless realm and can include one or more units of information defining the membership of a station to the wireless realm. The QTP query can be structured to include multiple domain name containers and/or can define membership to multiple wireless realms.
The QTP query is structured to enable the station 102 to query the AP 104. The purpose of the QTP query in this case is to answer the question, �will a user be allowed access to a network resource upon a yet un-attempted access request for the network resource?� The QTP query may or may not be used to answer other questions at the same or other times.
A generic advertising service (GAS) query is an example of a basic structure of an 802.11-compatible QTP. The GAS is a protocol that allows a station to ask questions of an AP and get answers. In the 802.11 standard GAS query, a domain name container includes data sufficient to identify an asserted membership. More generally, an asserted membership is a wireless realm, or data sufficient to identify a wireless realm, in any format.
In the example of FIG. 1, in operation, the AP 104 receives the QTP query and provides the QTP query to the PAI engine 106. The PAI engine 106 can receive the QTP query including the domain name container that includes the one or more units of information defining a membership in the wireless realm.
The PAI engine 106 compares the membership in the wireless realm(s) to membership access for the network resource. The PAI engine 106 determines whether the station 102 has access to the wireless realm(s) necessary to access the network resource.
The PAI engine 106 provides a response to the AP 104, which transmits a response defining membership access to the network resource to the station 102. The response predicts whether the station will be allowed access to the network resource upon an attempt to access the network resource.
The station 102 receives the response from the AP 104 including an indication of a relationship between the network resource and the membership in the wireless realm. The indication can predict that the station 102 will be allowed access by the AP 104 to the network resource. The response can be displayed to a user of the station 102, or can be automatically acted on by another processor in the station 102.
FIG. 2 depicts a flowchart 200 of an example of a process for predicting access to a network resource for a station, and attaching if the prediction is favorable. The process is organized as a sequence of modules in the flowchart 200. However, it should be understood that these and modules associated with other processes and methods described herein may be reordered for parallel execution or into different sequences of modules.
In the example of FIG. 2, the flowchart 200 starts at module 202 with transmitting, to a first AP, a QTP query including an asserted membership. The QTP query can include, for example, a domain name container defining membership in a wireless realm. The query can seek to determine whether a station associated with the QTP query will be allowed access to a network resource if the asserted membership is true.
In the example of FIG. 2, the flowchart 200 continues to module 204 with receiving, from a second AP, an indication of a relationship between the network resource and membership in a wireless realm. The membership in the wireless realm can be indirectly determined using the membership in the domain container, or the membership in the domain name container could itself be the membership in the wireless realm. It should be noted that, depending upon the implementation, configuration, and/or environmental factors (e.g., roaming) the first AP and the second AP can be the same AP or different APs. Depending upon the implementation, the fact that the indication of a relationship is received can indicate the relationship is likely to enable attachment to an AP, while a failure to receive the indication of a relationship can indicate that the relationship is unlikely to enable attachment to the AP. (Of course, a lack of a response can also be for other reasons, such as a message failure.)
In the example of FIG. 2, the flowchart 200 continues to module 206 with attaching to a third AP. It should be noted that, depending upon the implementation, configuration, and/or environmental factors, the first AP and the third AP can be the same or different APs. Also, the second AP and the third AP can be the same or different APs. As used in this paper, �attaching� refers to actions taken at a station to associate, authenticate, and/or otherwise wirelessly connect to an AP. A station having attached to the third AP after receiving a favorable prediction, the flowchart 200 ends.
FIG. 3 depicts an example of a PAI engine 300, such as the PAI engine described with reference to FIG. 1. The PAI engine 300 includes a query front-end processing (QFP) engine 302, a network resource name (NRN) table 304, a membership comparison engine 306, and a network resource access prediction engine 308.
In the example of FIG. 3, the QFP engine 302, can include hardware, firmware, or software implemented in hardware or firmware and executed by a processor, such as a microprocessor. The QFP engine 302 can include routines, circuitry, procedures or other sub modules for receiving requests and transmitting responses, such as by inter-process communications with systems operating on an AP.
In the example of FIG. 3, the NRN table 304 can include a database, file, data store, list of records, table, or other data management device for storing information describing membership of users and/or groups in wireless realms. The NRN table 304 can include a cache of such information compiled by an entity managing a wireless realm. The location of or distributed nature of the NRN table 304 is not critical so long as an NRN table interface is available to access the data.
In the example of FIG. 3, the membership comparison engine 306 can include hardware, firmware, or software implemented in hardware or firmware for execution by a processor. The membership comparison engine 306 can compare an asserted membership received in, for example, a QTP query, with a configured membership stored in the NRN table 304.
In the example of FIG. 3, the network resource access prediction engine 308 can include hardware, firmware, or software implemented in hardware or firmware for execution by a processor. The network resource access prediction engine 308 can provide an access prediction based on the result of a comparison from the membership comparison engine 306. The QFP engine 302 can provide the access prediction as a response to an asserted membership, if applicable.
In the example of FIG. 3, in operation, the NRN table typically receives membership configurations for users and/or groups, as is depicted by the Membership Configurations arrow pointing toward the NRN table 304 in the example of FIG. 3. The membership configurations can be provided to the NRN table in an automated or manual fashion.
In the example of FIG. 3, in operation, the QFP engine 302 receives an asserted membership. The asserted membership can be received in, for example, a QTP query. The asserted membership can be received or otherwise originate at a station.
In the example of FIG. 3, in operation, the QFP engine 302 provides the asserted membership to the membership comparison engine 306. The membership comparison engine 306 compares the asserted membership with configured memberships from the NRN table 304. If there is a match, then the user associated with the asserted membership appears to have access to the network resource in question, assuming the asserted membership is true.
In the example of FIG. 3, in operation, the membership comparison engine 306 provides the result of the comparison to the network resource access prediction engine 308, which, in turn, provides an access prediction to the QFP engine 302 in accordance with the result of the comparison. In a specific implementation, the QFP engine 302 provides a response to the asserted membership if the access prediction is favorable, and does not respond if the access prediction is not favorable.
FIG. 4 depicts a flowchart 400 of an example of a method for predicting access to a network resource. The method is organized as a sequence of modules in the flowchart 400. However, it should be understood that these and modules associated with other processes and methods described herein may be reordered for parallel execution or into different sequences of modules.
In the example of FIG. 4, the flowchart 400 starts at module with 402 with receiving a QTP query including an asserted membership. The asserted membership can be provided in a container that includes information sufficient to define a membership of a user (or group in which the user is a member) in a wireless realm. The QTP query can query whether a station associated with the user will be able to attach to an AP, and through the AP to a network resource in an as-of-yet un-attempted access request for the network resource.
In the example of FIG. 4, the flowchart 400 continues to module 404 with comparing the asserted membership to membership records. Wireless realms can allow access to stations because of membership in a wireless realm that a user of the station already has. Such membership can be based on a partnership agreement between operators of various wireless realms.
In the example of FIG. 4, the flowchart 400 continues to module 406 with transmitting a QTP query response, indicating an attachment possibility. The response itself can be indicative of an attachment possibility, or the response can include a prediction regarding whether access to the network resource for the as-of-yet un-attempted request will be allowed. Having indicated an attachment possibility, the flowchart 400 ends. A station, having received an indication of an attachment possibility, may attempt to attach (not shown), and the success of the attempt will depend upon whether the asserted membership can be shown by the station to be true.
FIG. 5 depicts an example of an infrastructure network including potential locations for a PAI engine. FIG. 5 includes controller 502, network 503, PAI engine 504, wireless switch 506-1 through wireless switch 506-n (collectively wireless switches 506), AP 512-1 through AP 512-n (collectively APs 512).
In the example of FIG. 5, the controller 502 can be practically any type of device that is capable of communicating with a communications network, for example, a mainframe or a workstation, server class computing device, or other computing device. The controller 502 can be connected to a wired backbone network (not shown), either directly or indirectly through a wireless network. The controller 502 can include, by way of example but not limitation, a Lightweight Directory Access Protocol (LDAP) server, a policy server, a combination of these servers, or another known or convenient server.
In the example of FIG. 5, the network 503 can be practically any type of communications network, such as, by way of example but not limitation, the Internet or an infrastructure network. The term �Internet� as used herein refers to a network of networks which uses certain protocols, such as the TCP/IP protocol, and possibly other protocols such as the hypertext transfer protocol (HTTP) for hypertext markup language (HTML) documents that make up the World Wide Web (the web).
In the example of FIG. 5, the PAI engine 504 can be located in a variety of locations as depicted, for example, as a module or component of the controller 502, as a module or component of the wireless switches 506, or as a module or component of the APs 512. The PAI engine 504 could be located in or as an intermediate entity within or coupled to the APs 512, the controller 502, the wireless switches 506, or the network 503.
In the example of FIG. 5, the wireless switches 506 are devices, such as specific purpose computing devices coupled together by a wired backbone. The wireless switches 506 can swap data and client information including authentication and authorization attributes and information. The wireless switches 506 can provide forwarding, queuing, tunneling, and/or some security services for the information the wireless switches 506 receive from APs 512. The wireless switches 506 can coordinate, provide power to, and/or manage the configuration of the APs 512. In a non-limiting example, the wireless switches are Trapeze Networks Mobility Exchange� Switches, available from Trapeze Networks, Inc., of Pleasanton, Calif.
In the example of FIG. 5, the APs 512 are stations that transmit and receive data (and may therefore be referred to as transceivers) using one or more radios. For example, an AP may have a radio that is configured for any band in which, for example, 802.11 is standardized. As another example, an AP may have multiple radios, such as a 2.4 GHz and a 5 GHz radio. In a non-limiting example, an access point transmits and receives information as radio frequency (RF) signals to and from a wireless client over an Ethernet connection. The access points 512 transmit and receive information to and from their associated wireless exchange switches 506. Connection to a second wireless exchange switch can provide redundancy.
In the example of FIG. 5, in operation, supposing the PAI engine 504 is located within the AP 512-1, the station 514 transmits a request for a prediction of the ability of the station 514 to attach to one of the APs 512, and through the AP to a network resource. The request is processed within the PAI engine 504 and a response, if appropriate, can be transmitted by the AP 512-1.
Alternatively, in the example of FIG. 5, supposing the PAI engine 504 is located within the wireless switch 506-1, the station 514 transmits a request for a prediction of the ability of the station 514 to attach to one of the APs 512, and through the AP to a network resource. The request is retransmitted to the wireless switch 506-1 where the PAI engine 504 is located. The PAI engine 504 processes the request and provides a response to the wireless switch 506-1 which transmits the response back to AP 512-1 which in turn transmits the response to the station 514, if appropriate.
Alternatively, in the example of FIG. 5, supposing the PAI engine 504 is located within the controller 502, the station 514 transmits a request for a prediction of the ability of the station 514 to attach to one of the APs 512, and through the AP to a network resource. The request is transmitted to the wireless switch 506-1 which sends the request to the controller 502 via the network 503. The controller 502 provides the request to the PAI engine 504 which processes the request and provides a response. The controller 502 sends a response to wireless switch 506-1 via the network 503, and the wireless switch 506-1 provides the response to the AP 512-1. The AP 512-1 then transmits the response to the station 514, if appropriate.
FIG. 6 depicts an example of a system 600 in which a station in the context of an infrastructure network queries for a prediction as to whether it is possible to access a resource. In the example of FIG. 6, the infrastructure network is an infrastructure network as discussed in reference to FIG. 5. In the example of FIG. 6, a resource 616 can be a network, part of a network, computing system, cluster, website, or other desirable system or unit of information.
In a non-limiting example, a user of the station 612 can attempt to access an airlines reservation website from within an airport. Assume the providers of wireless access have a partnership with the airport allowing access to the reservation site. The user can communicate a request to the AP 610 which can provide the request to the PAI engine 604, and the PAI engine 604 can consider membership required to access the resource 616 to determine whether the user might potentially have appropriate membership rights. A prediction can be provided to the AP 610. As can be noted, the closer the PAI engine 604 is to the AP 610, the shorter the distance (and, presumably, the fewer network resources consumed).
Depending upon the implementation, embodiment, and/or user preferences, a user of the station 612 may decide to attach to the AP 610 only after receiving a favorable prediction.
FIG. 7 depicts an example of a system 700 in which a station, in the context of multiple networks, queries whether a network resource is predicted to be accessible to a user of the station. FIG. 7 includes station 702, AP 704-1 through AP 704-n (collectively APs 704), PAI engine 705-1 through PAI engine 705-n (collectively PAI engines 705), partner network 706-1 through 706-2 (collectively partner networks 706), non-partner networks 708-1 through 708-2, resource 710.
In the example of FIG. 7, the station 702 can be a station as defined in reference to, for example, FIG. 1. The APs 704 can be APs as defined in reference to, for example, FIG. 1 or FIG. 5. The PAI engines 705 can be as defined in the figures described above, and the resource 710 can be as defined in reference to, for example, FIG. 6.
In the example of FIG. 7, the partner networks 706 can be networks having agreements to allow access to the resource 710 for members of another network, in which the user associated with the station 702 is a member. Contrarily, the non-partner networks 706 can be networks lacking agreements to allow access to the resource 710.
In the example of FIG. 7, in operation, the station 702 can transmit a query to all APs in range of the station 702 to gather predictions from the APs 704 indicating whether any of the APs 704 will allow access to the resource 710. The APs 704-1 and 704-3, which are connected to partner networks 706 can determine that access to the resource 710 is predicted to be allowed. However, the APs 704-1 and 704-n are connected to non-partner networks 708. As such, for illustrative purposes, no access is predicted to be allowed. The APs 704 transmit responses to the station 702 indicating that access is predicted to be allowed, or the APs 704 either do not transmit responses or transmit negative responses if access is not predicted to be allowed. The station 702 can then display a list of the APs, or data associated with the APs, predicted to allow access. Also the station 102 could take action to automatically access the resource 710.
FIG. 8 depicts an example of a computing system that is representative of the computing systems discussed herein. The system 800 may be a conventional computer system that can be used as a client computer system, such as a wireless client or a workstation, or a server computer system. The system 800 includes a device 802, I/O devices 804, and a display device 806. The device 802 includes a processor 808, a communications interface 810, memory 812, display controller 814, non-volatile storage 816, I/O controller 818, clock 822, and radio 824. The device 802 may be coupled to or include the I/O devices 804 and the display device 806.
The device 802 interfaces to external systems through the communications interface 810, which may include a modem or network interface. It will be appreciated that the communications interface 810 can be considered to be part of the system 800 or a part of the device 802. The communications interface 810 can be an analog modem, ISDN modem or terminal adapter, cable modem, token ring IEEE 802.5 interface, Ethernet/IEEE 802.3 interface, wireless 802.11 interface, satellite transmission interface (e.g. �direct PC�), WiMAX/IEEE 802.16 interface, Bluetooth interface, cellular/mobile phone interface, third generation (3G) mobile phone interface, code division multiple access (CDMA) interface, Evolution-Data Optimized (EVDO) interface, general packet radio service (GPRS) interface, Enhanced GPRS (EDGE/EGPRS), High-Speed Downlink Packet Access (HSPDA) interface, or other interfaces for coupling a computer system to other computer systems.
The non-volatile storage 816 is often a magnetic hard disk, flash memory, an optical disk, or another form of storage for large amounts of data. Some of this data is often written, by a direct memory access process, into memory 812 during execution of software in the device 802. One of skill in the art will immediately recognize that the terms �machine-readable medium� or �computer-readable medium� includes any type of storage device that is accessible by the processor 808.
In addition, the system 800 is controlled by operating system software which includes a file management system, such as a disk operating system, which is part of the operating system software. One example of operating system software with its associated file management system software is the family of operating systems known as Windows� from Microsoft Corporation of Redmond, Wash., and their associated file management systems. Another example of operating system software with its associated file management system software is the Linux operating system and its associated file management system. The file management system is typically stored in the non-volatile storage 816 and causes the processor 808 to execute the various acts required by the operating system to input and output data and to store data in memory, including storing files on the non-volatile storage 816.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS20040248557 *Jun 4, 2004Dec 9, 2004Nec CorporationMethod, system, and program for connecting network service, storage medium storing same program, access point structure and wireless user terminalUS20090010206 *Jun 6, 2008Jan 8, 2009Qualcomm IncorporatedMobile ip home agent discovery* Cited by examinerClassifications U.S. Classification726/4International ClassificationG06F21/00Cooperative ClassificationH04W48/14, H04W12/08, G06F21/6218, H04W88/14, H04L63/102European ClassificationH04L63/10B, G06F21/62B, H04W12/08, H04W48/14Legal EventsDateCodeEventDescriptionNov 8, 2010ASAssignmentFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BELDEN INC.;REEL/FRAME:025327/0302Owner name: TRAPEZE NETWORKS, INC., CALIFORNIAEffective date: 20101108Feb 25, 2010ASAssignmentOwner name: BELDEN INC.,MISSOURIFree format text: CHANGE OF NAME;ASSIGNOR:TRAPEZE NETWORKS, INC.;US-ASSIGNMENT DATABASE UPDATED:20100226;REEL/FRAME:23985/751Effective date: 20091221Free format text: CHANGE OF NAME;ASSIGNOR:TRAPEZE NETWORKS, INC.;US-ASSIGNMENT DATABASE UPDATED:20100318;REEL/FRAME:23985/751Free format text: CHANGE OF NAME;ASSIGNOR:TRAPEZE NETWORKS, INC.;US-ASSIGNMENT DATABASE UPDATED:20100427;REEL/FRAME:23985/751Free format text: CHANGE OF NAME;ASSIGNOR:TRAPEZE NETWORKS, INC.;US-ASSIGNMENT DATABASE UPDATED:20100429;REEL/FRAME:23985/751Free format text: CHANGE OF NAME;ASSIGNOR:TRAPEZE NETWORKS, INC.;US-ASSIGNMENT DATABASE UPDATED:20100513;REEL/FRAME:23985/751Free format text: CHANGE OF NAME;ASSIGNOR:TRAPEZE NETWORKS, INC.;US-ASSIGNMENT DATABASE UPDATED:20100525;REEL/FRAME:23985/751Free format text: CHANGE OF NAME;ASSIGNOR:TRAPEZE NETWORKS, INC.;REEL/FRAME:23985/751Free format text: CHANGE OF NAME;ASSIGNOR:TRAPEZE NETWORKS, INC.;REEL/FRAME:023985/0751Owner name: BELDEN INC., MISSOURIDec 17, 2008ASAssignmentOwner name: TRAPEZE NETWORKS, INC., CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:GAST, MATTHEW S.;REEL/FRAME:021993/0073Effective date: 20081216RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google