This application claims priority under 35 USC 119(e) from U.S. Provisional Patent Application No. 60/862,995, filed Oct. 26, 2006, and which is incorporated by reference herein.
A wireless local area network (WLAN) client device may store in its memory one or more persistent connection profiles of wireless local area networks. A persistent connection profile may include, for example, the service set identity (SSID) of the network, WLAN configuration parameters, security credentials, and Internet Protocol (IP) network parameters. The SSID is also known as the network name. The persistent connection profiles may be assigned priorities, for example, by a user that has purchased the client device, a carrier who controls the sale of the client device, or an administrator of an enterprise that has purchased the client device. Generally, user action is required to delete a persistent connection profile from a client device.
Scanning is the process of identifying existing networks. SSIDs in scan results are compared to the SSIDs of one or more of the persistent connection profiles stored in the client device. The order in which SSIDs of the persistent connection profiles are compared to the SSIDs in the scan results may be determined by one or more factors. For example, the SSIDs of the persistent connection profiles may be compared in order of decreasing priority for the persistent connection profiles. In another example, the SSIDs in the scan results may be compared in order of decreasing received signal strength. If there is a match, a WLAN controller of the client device may initiate an authentication process and, if the authentication process is successful, may initiate an association or re-association process with an access point (AP) or, in the case of an ad hoc network, another WLAN client device that carries the wireless local area network the SSID of which matches the SSID of one of the persistent connection profiles. If the comparison does not yield any matches, but there are scan results, the client device may present a list of identified networks (based on the SSIDs in the scan results) to the user of the client device, so that the user can select which, if any, of the networks to join. If there are no scan results, the client device may have its radio enter a low-power state for a period of time, until more scanning is to be done.
If the user of the client device selects an identified network to join, the user may be prompted to enter connection parameters in order to successfully connect to the selected network. A non-exhaustive list of examples for the connection parameters includes WLAN configuration parameters, security credentials, Internet Protocol (IP) network parameters, or any combination thereof. The user may also be prompted whether to save these connection parameters and the SSID of the selected network in a new persistent connection profile. Once saved, the new persistent connection profile is not deleted from the client device until explicit user action is taken to do so. The user may also be able to set the relative priority of the new persistent connection profile. If the user chooses not to save these connection parameters and the SSID of the selected network in a persistent connection profile, then the next time the user selects that identified network to join, the user may be prompted to once again enter the connection parameters in order to successfully connect to the selected network.
Consider a scenario where a user travels by airplane to a three-day conference. The user's client device may connect to a WLAN in an airport lounge, to another WLAN at the hotel and to yet another WLAN at the conference center. If the user chooses to save persistent connection profiles for each of these WLANs, then there will be three additional persistent connection profiles stored in the client device. Until such time as the user explicitly deletes these profiles, they will be compared to the scan results if there is no match to a higher priority profile. If the user chooses not to save persistent connection profiles for these WLANs, then the user will be required to reenter the connection parameters on each occasion that the client device is connecting to the WLAN.
For battery-operated client devices, the process of network discovery and association in a timely manner consumes significant battery life.
Embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like reference numerals indicate corresponding, analogous or similar elements, and in which:
It will be appreciated that for simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity.
In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of embodiments. However it will be understood by those of ordinary skill in the art that the embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the embodiments.
A wireless local area network (WLAN) client device is able to store one or more transient connection profiles. A transient connection profile of a WLAN may be overwritten by a transient connection profile of another WLAN.
If the user chooses not to save the connection parameters and the SSID of the selected network in a new persistent connection profile, they may be saved instead in client device 102 in a transient connection profile. If client device 102 is disconnected from the WLAN and then subsequently scans for wireless local area networks while in the coverage area of AP 106 or any other AP carrying the WLAN, the scan results will be compared to this transient connection profile, and since there is a match, client device 102 will attempt to connect to the WLAN using the connection parameters in the transient connection profile. The user will therefore be spared having to re-enter those connection parameters, as would have been the case had the connection parameters not been stored in client device 102.
If the user chooses not to save the connection parameters and the SSID of the selected network in a new persistent connection profile, they may be saved instead in client device 102 in a transient connection profile. If client device 102 is capable of storing only one transient connection profile at a time, then at this point, the data in the transient connection profile from the WLAN at the conference center is overwritten with the connection parameters and the SSID of the WLAN at the airport. The user of client device 102 is therefore spared having to explicitly delete the connection profile for the WLAN at the conference center. Even if client device 102 is capable of having more than one transient connection profile stored concurrently therein, at some point in time the transient connection profile storing the connection parameters and SSID for the WLAN at the conference center will be overwritten with the connection parameters and SSID of another WLAN. Client device 102 may automatically delete the transient connection profile after a period of time has elapsed, without an explicit user action to delete the transient connection profile. For example, client device 102 may automatically delete a transient connection profile once a certain period of time, for example, 24 hours, has elapsed since a most recent disconnection of client device 102 from a WLAN described in the transient connection profile. In another example, client device 102 may automatically delete a transient connection profile once a certain period of time, for example, 24 hours, has elapsed since a most recent connection of client device 102 from a WLAN described in the transient connection profile. The transient connection profile may include a timestamp indicating the latest time at which the client device connected to or disconnected from the network described in the profile.
Client device 300 comprises a WLAN interface 310, compatible with one or more WLAN standards, for example, one or more of the IEEE 802.11 wireless communication standards, or one or more of the ETSI HiperLAN wireless communication standards. WLAN interface 310 is coupled to processor 302 and includes at least a WLAN controller 312 and a radio 314. Client device 300 also comprises an antenna 316 coupled to radio 314. For example, client device 300 may be able to communicate with APs or, in the case of ad hoc networks, other WLAN client devices, via WLAN interface 310 and antenna 316.
Memory 304 is able to store one or more persistent connection profiles 318 and one or more transient connection profiles 320. Memory 304 may also be able to store priorities 322 for the profiles as a factor in determining the order in which scan results are compared to the profiles, as a factor in determining the order in which scanning for a wireless local area network matching a particular profile is done, or both. A WLAN for which an SSID and connection parameters are stored in a connection profile 318 or 320 may be an infrastructure WLAN or an ad hoc WLAN.
Memory 304 stores code 324 that, when executed by processor 302, may implement the methods described herein together with WLAN controller 312.
Client device 300 includes other components that, for clarity, are not shown in
Referring first to
The user will be prompted by the client device to enter connection parameters for the selected network, and at 406 the client device will receive those connection parameters. The user may be prompted by the client device whether to save the connection parameters in a persistent connection profile. The user's choice may also be received by the client device at 406. Alternatively, the user may be prompted by the client device whether to save the connection parameters in a persistent connection profile after the parameters have been received by the client device at 406.
If the user has chosen to save the SSID of the selected network and the connection parameters in a persistent connection profile, as checked at 408, then at 410, the client device creates a new persistent connection profile with the SSID of the selected network and the connection parameters. Otherwise, the client device will check at 412 whether a transient connection profile is currently stored in the client device. If not, then the client device creates at 414 a new transient connection profile with the SSID of the selected network and the connection parameters received at 406. The priority of the new transient connection profile may be set by default to the lowest priority, although the user may be able to adjust the priority of the new transient connection profile. Other schemes for setting the priority of the new transient connection profile are also contemplated. If a transient connection profile is currently stored in the client device, then the client device overwrites the stored transient connection profile at 416 with the SSID of the selected network and the connection parameters received at 406.
Referring now to
If the maximum number of transient connection profiles are currently stored in the client device, then the client device overwrites one of the transient connection profiles at 516 with the SSID of the selected network and the connection parameters received at 406. The transient connection profiles may include a timestamp indicating the latest time at which the client device connected to or disconnected from the network described in the profile, and the transient connection profile with the least recent timestamp may be the one which is overwritten at 516.
Referring now to
If the user has chosen to save the SSID of the selected network and the connection parameters in a persistent connection profile, as checked at 408, then at 410, the client device creates a new persistent connection profile with the SSID of the selected network and the connection parameters. Otherwise, the client device will check at 612 whether a transient connection profile of the same classification is currently stored in the client device. If not, then the client device creates at 614 a new transient connection profile with the SSID of the selected network and the connection parameters received at 606. The new transient connection profile is classified with the classification specified by the user at 606. The priority of the new transient connection profile may be set by default to the lowest priority, although the user may be able to adjust the priority of the new transient connection profile. Other schemes for setting the priority of the new transient connection profile are also contemplated. If a transient connection profile of the same classification is currently stored in the client device, then the client device overwrites that transient connection profile at 616 with the SSID of the selected network and the connection parameters received at 606.
For example, a user of a client device may visit an airport lounge and a transient connection profile for the WLAN at the airport lounge may be created. The user may arrive at a hotel, and a separate transient connection profile for the WLAN at the hotel may be created. The user may then attend a three-day conference, and a separate transient connection profile for the WLAN at the conference center may be created. When the user then moves to a different hotel, the transient connection profile classified “hotel” may be overwritten with information of the WLAN at the different hotel. The next time the user attends a conference, the transient connection profile classified “conference” may be overwritten with information of the WLAN at the new conference.
The methods of
At 804, the client device checks the scan results against the persistent connection profiles and the transient connection profile(s) that are stored in the client device. The order in which the connection profiles are checked against the scan results may be determined according to any suitable scheme. The relative priorities assigned to the connection profiles may be a factor in determining this order. The received signal strengths of the scan results may be a factor in determining this order.
If there is a match, as checked at 806, then the client device attempts at 808 to connect to the WLAN that matches the connection profile. The attempt may involve initiating an authentication process and, if the authentication process is successful, initiating an association or re-association process with an AP, or in the case of an ad hoc network, another WLAN client device, the WLAN of which is identified in the matching scan results. The details of this are beyond the scope of this document.
If there is no match but there are additional communication channels to scan, as checked at 810, then the method resumes from 802. If all suitable communication channels have been scanned without resulting in a matched connection profile, and there were indeed scan results (checked at 812), the client device may present the identified networks to a user of the client device at 814. If there were no scan results (which will occur, for example, when the client device is out of coverage), then the client device may wait for a period of time at 816. When this period of time (the “back-off” period) has elapsed, the method may resume from 802. The back-off period may be fixed, or may vary from one scan session to another. For example, successive scan sessions may be separated by increasing periods of time, subject to an upper limit. The client device may enter a lower power state during all or part of the back-off period.
Although the subject matter has been described in language specific to structural features, methodological acts or both, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Number | Name | Date | Kind |
---|---|---|---|
5870744 | Sprague | Feb 1999 | A |
5903832 | Seppanen et al. | May 1999 | A |
6718339 | Eden | Apr 2004 | B2 |
6961762 | Yeap et al. | Nov 2005 | B1 |
20020007407 | Klein | Jan 2002 | A1 |
20030003933 | Deshpande et al. | Jan 2003 | A1 |
20030219022 | Dillon et al. | Nov 2003 | A1 |
20040077341 | Chandranmenon et al. | Apr 2004 | A1 |
20040100973 | Prasad | May 2004 | A1 |
20040114601 | Hiroyuki et al. | Jun 2004 | A1 |
20040264427 | Jaakkola et al. | Dec 2004 | A1 |
20050181734 | Coutts et al. | Aug 2005 | A1 |
20050237967 | Lee et al. | Oct 2005 | A1 |
20050254435 | Moakley et al. | Nov 2005 | A1 |
20050260973 | van de Groenendaal | Nov 2005 | A1 |
20050260989 | Pourtier et al. | Nov 2005 | A1 |
20050260996 | van de Groenendaal | Nov 2005 | A1 |
20060069760 | Yeap et al. | Mar 2006 | A1 |
20060075090 | Bocking et al. | Apr 2006 | A1 |
20060168438 | Klein | Jul 2006 | A1 |
20060173844 | Zhang et al. | Aug 2006 | A1 |
20060174127 | Kalavade et al. | Aug 2006 | A1 |
20060209773 | Sukhdeep et al. | Sep 2006 | A1 |
20060242305 | Alnas | Oct 2006 | A1 |
20070067446 | Jones et al. | Mar 2007 | A1 |
20070079013 | Tumsi Dayakar et al. | Apr 2007 | A1 |
20070130468 | Cunningham et al. | Jun 2007 | A1 |
20070208937 | Cam-Winget et al. | Sep 2007 | A1 |
20070264991 | Jones et al. | Nov 2007 | A1 |
20080281952 | Fedotenko | Nov 2008 | A1 |
20090300722 | Haverinen et al. | Dec 2009 | A1 |
20130128815 | Scherzer et al. | May 2013 | A1 |
Number | Date | Country |
---|---|---|
0781064 | Jun 1997 | EP |
1394988 | Mar 2004 | EP |
1395077 | Mar 2004 | EP |
1638357 | Mar 2006 | EP |
0141392 | Jun 2001 | WO |
WO-2004077752 | Sep 2004 | WO |
2005020002 | Mar 2005 | WO |
2005057860 | Jun 2005 | WO |
2006004786 | Jan 2006 | WO |
2006031927 | Mar 2006 | WO |
WO-2006066181 | Jun 2006 | WO |
2006111951 | Oct 2006 | WO |
Entry |
---|
Savin, Daniela , Written Opinion of the International Searching Authority for PCT/CA2007/001887, Feb. 7, 2008. |
Elena, Mikhailova , Written Opinion of the International Searching Authority for PCT/CA2007/002074, Mar. 28, 2008. |
“Wireless LAN Enhancements in Windows XP Service Pack 2”, http://www.microsoft.com/technet/community/columns/cableguy/about.mspx 2008. |
Garcia Bolos, Ruth, Extended European Search Report for EP 07845544.1, Oct. 27, 2009. |
“iPhone user guide”, http://en.wikipedia.org/wiki/AirPort, published Jun. 29, 2007. |
Belkin Corporation: “User Manual F5D6020” 1-14, Jul. 17, 2003, XP002604419, http://cache-www.belkin.com/support/dl/f5d6020v3.pdf. |
Planex Communications: “Airgo Wireless Adapter Installation and User Guide”, Jul. 2004, XP002604418, http://www.planex.net/pdf/wireless/CQW-NS108AG—Manual—Eng.pdf, Chapters 2,3. |
Matar, G., First Office Action for CA2,607,823, Oct. 25, 2010. |
Straniero, Roberto, Extended European Search Report for EP 07816037.1, Nov. 18, 2010. |
Ma, Cathy; First Office Action for CA 2,670,033, Oct. 19, 2011. |
Planex Communications, Installation and User Guide(CQW-NS108AG), Jul. 31, 2004. |
Ma, Cathy, Second Office Action for CA 2,670,033, Nov. 21, 2012. |
Qian, Zijuan, Second Office Action for CN 200780039406.9, Dec. 5, 2012. |
Utreja, Neeraj K., Fifth Office Action for U.S. Appl. No. 11/943,332, Nov. 15, 2012. |
Utreja, Neeraj K., Second Office Action for U.S. Appl. No. 13/093,099, Oct. 29, 2012. |
Qian, Zijuan , First Office Action for CN 200780039406.9, Mar. 1, 2012. |
Garcia Bolos, Ruth, Second Exam Report for EP 07845544.1, Jul. 4, 2012. |
Patel, R.B. et al., Mobile Agents in Wireless LAN and Cellular Data Networks, Journal of Computer Science, vol. 2, Issue 5, pp. 410-418, May 1, 2006. |
Plata, Edd Rianne L., Final Office Action for U.S. Appl. No. 12/389,584, Feb. 1, 2012. |
Yeow, Leslie, Third Office Action for CA 2,607,823, Aug. 13, 2012. |
Yeow, Leslie, Second Office Action for CA 2,607,823, Aug. 1, 2011. |
Planex Communications: “108 Mbps Wireless LAN PC Card”, Installation and User Guide, Jul. 2004 , p. 20-22, XP002506563. |
Casio, “User's Guide, Cassiopeia DT-10 Pegasus Setting”, 2005 , 1-19. |
Chin, Allan et al., “Seamless Connectivity to Wireless Local Area Networks”, Intel Technology Journal, Wireless Technologies, vol. 7, No. 3, XP008109356, pp. 63-67, Aug. 19, 2003. |
Garcia Bolos, Ruth, Extended European Search Report for EP 07845545.8, Oct. 29, 2009. |
Garcia Bolos, Ruth, Extended European Search Report for EP 07845546.6, Nov. 2, 2009. |
Garcia Bolos, Ruth, Second Exam Report for EP 07845543.3, May 5, 2009. |
Garcia Bolos, Ruth, Third Exam Report for EP 07845543.3, Nov. 2, 2009. |
Garcia Bolos, Ruth, Extended European Search Report for EP 07845543.3, Dec. 19, 2008. |
Intel, “User Guide, Intel PRO/Wireless 2915ABG Network Connection”, Jun. 2005. |
Utreja, Neeraj K., Restriction Requirement for U.S. Appl. No. 11/943,332, Feb. 17, 2010. |
Utreja, Neeraj K., Second Office Action for U.S. Appl. No. 11/943,332, Jul. 9, 2010. |
Utreja, Neeraj K., Third Office Action for U.S. Appl. No. 11/943,332, Dec. 27, 2010. |
Plata, Edd R., Office Action for U.S. Appl. No. 12/389,584, Sep. 27, 2011. |
Utreja, Neeraj K., First Office Action for U.S. Appl. No. 13/027,823, Dec. 29, 2011. |
Utreja, Neeraj K., First Office Action for U.S. Appl. No. 13/093,099, Dec. 22, 2011. |
Widhalm, Angela M., Advisory Action for U.S. Appl. No. 11/943,332, Mar. 15, 2013. |
Widhalm, Angela M., Advisory Action for U.S. Appl. No. 13/093,099, Feb. 14, 2013. |
Winder, Patrice L., Second Office Action for U.S. Appl. No. 13/027,823, Jul. 12, 2013. |
Number | Date | Country | |
---|---|---|---|
20080147882 A1 | Jun 2008 | US |
Number | Date | Country | |
---|---|---|---|
60862995 | Oct 2006 | US |