US 7,669,232 B2Grant
Dynamic authentication in secured wireless networks
Issue Date:2010-02-23
•13 Claims
•5 Drawing Sheets
Abstract
Systems and methods for authentication using paired dynamic secrets in secured wireless networks are provided. Each authenticated user is assigned a random secret generated so as to be unique to the user. The secret is associated with a wireless interface belonging to the user, so that no other wireless interface may use the same secret to access the network. The secret may be updated either periodically or at the request of a network administrator, and reauthentication of the wireless network may be required.
Metadata
Assignee
- Ruckus Wireless, Inc.
Inventors
- Tyan-Shu Jou
- Ming Sheu
- Bo-Chieh Yang
- Tian-Yuan Lin
- Ted Tsei Kuo
Application Information
Application Number:US 12/339,688
Filing Date:2008-12-19
Priority Date:2006-04-24
Art Unit:2431
Classifications
IPC:
H04L29/00H04L29/10H04L29/14H04L29/06
Patent Drawings (5 sheets)
Description
Cross-Reference to Related Applications
[0001] The present application is a continuation and claims the priority benefit of U.S. patent application Ser. No. 11/788,371 filed Apr. 18, 2007, which claims the priority benefit of U.S. provisional patent application Ser. No. 60/794,625 filed Apr. 24, 2006 and U.S. provisional patent application Ser. No. 60/796,845 filed May 2, 2006, the disclosures of the aforementioned applications being incorporated herein by reference.
Background of the Invention
[0002] 1. Field of the Invention
[0003] The present invention generally relates to information network security. More specifically, the present invention relates to user-friendly, low-maintenance authentication for secured wireless networks.
[0004] 2. Description of Related Art
[0005] A variety of user authentication and security measures for wireless networks have been proposed by a number of professional organizations. These professional organizations include the Institute of Electrical and Electronics Engineers (IEEE) 802.11 Working Group, the Wi-Fi Alliance, and the Internet Engineering Task Force (IETF). Implementing these proposals has generally been complicated, difficult to maintain, and requires a high level of technical knowledge by those implementing a particular proposal. Many commercial organizations (e.g., small- and medium-sized businesses), therefore, have been unable to deploy such measures, because of their lack of expertise and/or full-time professional technical support.
[0006] In early wireless networks (e.g., IEEE 802.11 or Wi-Fi), security was achieved by wired equivalent privacy (WEP) systems. Deploying a WEP system requires only that a network administrator define a WEP key set at an access point or access device. Any user can access a WEP-secured wireless network by having the same WEP key set manually configured on that user's client station (e.g., a laptop or mobile device). The wireless data communication between the client station and the access point would be encrypted by a defined encryption algorithm utilizing the shared WEP key set.
[0007] While WEP may work to prevent casual trespassers from accessing the wireless network, WEP would not likely withstand more serious security attacks. WEP keys can be easily discovered, for example, by using publicly available software. Further, WEP does not work to protect network users from each other since all users share the same key. Because of these flaws in WEP-based security systems, alternative security measures evolved. These new measures generally required that wireless network users first be authenticated in some manner and that a key set then be derived and used for wireless traffic encryption. These proposed authentication measures can generally be categorized into two groups: Extensible Authentication Protocol (EAP) and Pre-Shared Key (PSK).
[0008] The EAP group of security measures generally follows the IEEE 802.1× standard, which utilizes the extensible authentication protocol. EAP-based security systems enable mutual authentication between an authentication server and its users. The authentication server may reside in an access point, base station or an external device. Generally, the authentication server provides for a derived pair-wise master key to be shared between an access point and the user client station. That pair-wise master key may be used to derive a key set, which may be used for data encryption.
[0009] A major obstacle in implementing EAP or IEEE 802.1x-based security systems is their complexity. Deploying such systems requires a high level of technical expertise, as well as ongoing technical support for users. Most EAP-based systems, for example, require security certificates to be installed onto authentication servers. Depending on the exact requirements of the EAP-based system, the client stations may also need to be granted the authority to root certificate updates and/or have the security certificate pre-installed before access to the wireless network can be granted.
[0010] In contrast, PSK security systems are based on a secret shared between and stored at both the client station and the access point. The secret may be, for example, a long bit stream, such as a passphrase, a password, a hexadecimal string, or the like. Used by a client station and the access point to authenticate each other, the secret may also be used to generate an encryption key set.
[0011] A major shortcoming of PSK-based systems is that the secret has to be manually entered onto client stations and shared by all the client stations. Once the shared secret becomes known to unauthorized personnel, the security of the entire network is compromised. This may pose a problem in organizations that need to provide network access to temporary employees or that have a highly mobile workforce. To maintain the security of a PSK-based system, the secret must be changed on all client stations whenever a person with knowledge of the secret departs from the organization or is no longer authorized to access the network.
[0012] Notwithstanding the many measures available for securing a wireless network, implementing any one of these measures may be complicated, difficult, and/or require extensive maintenance. There is, therefore, a need in the art for improved systems and methods that provide security for wireless networks that are user-friendly and easily maintained without requiring a high degree of technical expertise and ongoing technical support.
Summary of the Invention
[0013] Exemplary systems and methods of the present invention provide for pairing dynamic secrets in secured wireless networks. A random secret is generated for each authenticated user. That secret is unique to the user, and no other users in the network may use that secret to access the network. Further, the secret is associated, or bound, with the wireless interface belonging to the user, so that no other wireless interface belonging to other users may use that secret to access the network.
[0014] Various embodiments of the present invention include methods for pairing such dynamic secrets. Associating the secret with a wireless interface may occur immediately after the secret is generated and/or associated with the access profile, or associating the secret with the wireless interface may occur after a delay. Some embodiments associate the secret with the wireless interface by generating an executable to configure the wireless interface to access the wireless network. Configuration may include transferring a copy of the executable to the wireless interface, along with copies of the secret, any security keys derived from the secret, and the user's access profile. Various embodiments of the present invention further include updating the secret, which requires that the wireless interface be reauthenticated before being allowed to reconnect or continue its connection to the wireless network.
[0015] Embodiments of the present invention include systems for pairing dynamic secrets in a secured wireless network. Such systems may include a secret generation module, a binding module, and a secret database. The secret is generated by the secret generation module and associated (bound) with a wireless interface by the binding module. The secret database stores information concerning secrets, associations with user profiles, associations with wireless interfaces, and the like. Some embodiments further include an access profile generation module, an executable generation module, and the like. The access profile generation module generates access profiles for users. The executable generation module generates executables for configuring wireless interfaces for access to wireless networks.
[0016] Some embodiments of the present invention include computer media and instructions for pairing dynamic secrets in a secured wireless network. Some embodiments further include instructions for updating the secrets and requiring that wireless interfaces be reauthenticated.
Brief Description of Figures
[0017] FIG. 1 is an illustration of an authentication system for a secured wireless network in accordance with an exemplary embodiment of the present invention.
[0018] FIG. 2 is a flowchart illustrating a method for using paired dynamic secrets in a secured wireless network.
[0019] FIG. 3 is a flowchart illustrating an alternative method for using paired dynamic secrets in a secured wireless network.
[0020] FIG. 4 is a flowchart illustrating a method for using security keys in a secured wireless network.
Detailed Description
[0021] The present invention includes systems and methods for using user-friendly, low-maintenance authentication in secured wireless networks through the use of dynamic secrets. Paired secrets are shared between a client station and an access point. These secrets are dynamically generated for each authenticated user and associated with the user's access profile. The secret may also be associated with a specific client station or wireless interface belonging to the user. In some embodiments of the present invention, the secret expires, at which point the user must reauthenticate in order to continue accessing the wireless network.
[0022] FIG. 1 is an illustration of an authentication system 100 for a secured wireless network 170 in accordance with an exemplary embodiment of the present invention. Authentication server 100, as illustrated in FIG. 1 , includes an authentication module 110, an access profile generation module 120, a secret generation module 130, a database of secrets 140, a binding module 150, and an executable generation module 160. The authentication server 100 may be used to maintain security in network 170. Various client devices, such as wireless workstation 180a, laptop 180b, and mobile device 180c belong to potential users of network 170.
[0023] A module (or application), as referenced in the present invention, should be generally understood as a collection of routines that perform various system-level functions and may be dynamically loaded and unloaded by hardware and device drivers as required. The modular software components described herein may also be incorporated as part of a larger software platform or integrated as part of an application specific component.
[0024] Authentication module 110 authenticates a user (e.g., laptop 180b) and verifies that the user is who they purport to be and that they are otherwise authorized to access network 170. The authentication module 110 may be used to verify a user name and password supplied by the user. Verification may occur through comparison with user names and passwords stored in an authentication database, which may be independent of or incorporated into authentication module 110. In some embodiments, the authentication database may be integrated with secret database 140 as is described below. Once authenticated by authentication module 110, the user may access data and perform actions within network 170 based on the user's security clearance level, the parameters of the user's role in the organization, as defined by a network administrator, and as may be further governed by a paired secret or derived keys.
[0025] Access profile generation module 120 generates an access profile for a user authenticated by authentication module 110. A user access profile may include, at the least, a random paired secret and an executable as is further described herein. An access profile may further include information concerning the user, such as authentication information, security information, user preferences, and the like. To access the network 170, a user copies, downloads, or otherwise transfers the user access profile to the user's client device (e.g., laptop 180b). Access profiles may be securely obtained via a common web browser utilizing hypertext transfer protocol over secure socket layer (HTTPS). The executable automatically configures a wireless device so that they may access the wireless network 170.
[0026] Secret generation module 130 generates a random secret for each user. Various algorithms and formulas may be used by secret generation module 130 to randomly generate secrets. By providing for random secrets, secret generation module 130 increases the difficulty for potential trespassers to deduce or otherwise determine a particular secret and illicitly gain access to network 170. Secret generation module 130 is further configured to determine that each secret is unique to each user, so that each secret may only be used by one user. The secret may be bundled as part of an access profile. The secret will be used to authenticate a wireless device so that the wireless device can access the wireless network 170. In some embodiments, secret generation module 130 may derive from a particular secret a set of one or more security keys for a user. Like secrets, security keys may be associated with a wireless device and used in configuring the wireless interface so that it may access the wireless network 170. Also like secrets, no other wireless device may then use those same security keys to access the network 170.
[0027] Secret database 140 stores information concerning various secrets generated by secret generation module 130. Secret database 140 may also store information concerning which user is associated with a particular secret, any security keys derived from a secret, which wireless device, if any, is associated with a user's secret or security keys, and the like. Secret database 140 may further store information concerning user names, passwords, security clearance levels, and the like. Secret database 140 may operate in conjunction with authentication module 110 to authenticate users and interfaces belonging to the users to the network 170.
[0028] Binding module 150 is configured to associate (bind) a user's secret to a wireless interface device belonging to the user (e.g., workstation 180a, laptop 180b, or mobile device 180c). The association formed by binding module 150 between a secret and a user's wireless interface device is required for the wireless interface to be authenticated and allowed access to the wireless network 170. In some instances, immediately after secret generation and/or association with an access profile, binding module 150 associates the user's secret to the user's wireless interface device (if the user is using a wireless interface device) or a profile assigned to the interface device. The immediate operation of binding module 150 may be referred to as prompt binding. Alternatively, the operations of binding module 150 may be delayed until the user initiates the first wireless connection via the wireless interface and the MAC address of the user's wireless device may be determined. The delayed operation of binding module 150 may be referred to as delayed binding.
[0029] An executable generation module 160 generates an executable application that configures a wireless interface for access to the wireless network 170. The executable generated by executable generation module 160 may then be copied, downloaded, or otherwise transferred to a wireless interface belonging to the user. The executable may be bundled as part of an access profile. The executable installs the access profile generated by access profile generation module 120 and the secret generated by secret generation module 130 onto the wireless device. Generation of this executable and the aforementioned access profile are further disclosed in U.S. provisional patent application 60/796,845, the disclosure of which has been previously incorporated by reference.
[0030] Network 170 may be configured to transmit various electromagnetic waves, including, for example, radio signals. Network 170 may be an IEEE 802.11 (Wi-Fi or Wireless LAN) network, IEEE 802.16 (WiMAX) network, IEEE 802.16c network, or the like. Network 170 may convey various kinds of information to interface devices, such as client interface devices 180a-c. Network 170 may be a local, proprietary network or may be a part of a larger wide-area network. Various subsidiary networks may reside within the realm of greater network 170 such as peer-top-peer or wireless mesh networks.
[0031] Client interface devices 180a-c illustrate a variety of wireless-capable interfaces, including desktop computers, laptop computers, handheld computers, and the like. A user wishing to access the wireless network 170 through wireless interface 180a, for example, may do so by copying, downloading, or otherwise transferring to wireless interface 180a a copy of the user's access profile generated by access profile generation module 120, a secret generated by secret generation module 130, and an installation executable generated by executable generation module 160. The executable configures wireless interface 180a so that wireless interface 180a can access the wireless network 170 utilizing an access profile and paired secret as part of an overall authentication operation. Wireless interface 180b and wireless interface 180c may be configured in similar fashion.
[0032] A user's secret may be updated periodically or in response to a request by a network administrator. A new secret may be generated for the user by secret generation module 130, associated with the user's access profile, and saved to the secret database 140. If the previous secret has expired, the wireless interface must be reauthenticated. The user must either reauthenticate immediately or reauthenticate at the next wireless connection. Reauthenticating the wireless device may include reauthenticating the user, transferring copies of the user's new secret, access profile, and/or a new executable, and, using binding module 140, forming a new association between the wireless interface and the new secret.
[0033] FIG. 2 is a flowchart illustrating a method 200 for using paired dynamic secrets in a secured wireless network 170. In method 200, a user is authenticated, a random and unique paired secret is generated for the user, the secret is associated with an access profile belonging to the user, and the secret is further associated (bound) with a wireless interface belonging to the user and further associated with a particular access profile.
[0034] In step 210, the user is authenticated using authentication module 110. Initial authentication may include providing a user name and password identifying the user as a particular user. That user may or may not be authorized to access the network 170 as may be determined with respect to paired secrets. If a user cannot be authenticated through a simple user name and password match (or subsequently with respect to paired secrets), the user may not be allowed to access the wireless network 170.
[0035] In step 220, a secret is generated for the provisionally authenticated user. Generated by secret generation module 130, the secret may be determined through various algorithms or formulas so that a randomly generated secret is produced for the authenticated user. Further, the secret is unique to each user in the network 170. The uniqueness of the secret for each user provides each user protection from all other users in the network 170. Because each user has a secret uniquely bound to that specific user (or their profile and/or interface device), there is no way for a user to use another user's secret. Further, when a particular user is no longer authorized to use the network 170, that user's de-authorization does not affect the ability of other users to continue using the network 170 as is the case in many prior art network security solutions. Further, de-authorization of a particular user does not require any particular technical expertise or technical support to maintain the security of the network 170. Also in step 220, other information entities associated with the wireless authentication mechanism, such as authority certificates, may be generated.
[0036] In step 230, the secret generated for an authenticated user is associated with that user's access profile, which may be further associated with a particular interface device. Information concerning the association between the secret and the user access profile may be saved in secret database 150.
[0037] In step 240, the secret is associated (bound) with a wireless interface belonging to the authenticated user, their profile, and/or device. The association may be formed by binding module 140 and allows for the wireless interface device to access the wireless network 170. The association, or binding, may include downloading an access profile, a paired secret and any associated derived security keys, and an executable for configuring and associating the wireless interface device with the secret. The secret may be associated with the wireless interface by associating the secret with a specific radio of the wireless interface, a MAC address of the wireless interface, or the like. Information concerning the association between the paired secret and wireless interface may be saved in secret database 150.
[0038] FIG. 3 is a flowchart illustrating an alternative method 300 for using secrets in a secured wireless network 170. In this method 300, the user is authenticated as may occur through an initial user name and password verification process, an access profile is generated, and a secret is generated. If a known wireless interface is connected to the network 170, then that wireless interface is associated (bound) with the secret. If there is no known wireless interface currently connected to the network 170, then the unassociated secret may be saved and can be later associated with a wireless interface.
[0039] In step 310, the user is authenticated by authentication module 110. The authentication may be performed in a similar fashion to the authentication performed in step 210.
[0040] In step 320, an access profile is generated for the authenticated user. The access profile, generated by access profile generation module 120, may be used to configure a wireless interface belonging to the user so that they may access the network 170.
[0041] In step 330, a secret is generated for the user. The generation of the secret may be performed in a manner similar to that of step 220 of FIG. 2 .
[0042] In step 340, the determination is made whether the current network connection is through a known wireless interface. The determination may be based on authentication information, user input, or the like.
[0043] In step 350, where the connection is (for example) determined not to be a known wireless interface already having a bound secret, the most recently generated secret is saved to a table. The table may be included in secret database 150. Where the user is not using a wireless interface, the wireless interface is not the intended interface to be used in a multi-wireless-interface (radio) device, the user is not using the user's own wireless interface, or the user is otherwise not ready to associate the wireless interface with the secret, the secret may be saved to the table for later use.
[0044] In step 360, where the connection is determined to be a known wireless interface not having a bound secret, having an expired secret, or otherwise in need of a bound secret, the secret is bound with the wireless interface. The association may be formed in a similar manner as the association formed in step 240.
[0045] FIG. 4 is a flowchart illustrating a method 400 for using security keys in a secured wireless network 170. In this method, an authentication request is received from a wireless interface. It is then determined whether a security key is associated with the interface, and if so, it is determined whether the security key is valid. If the security key is valid, then the wireless interface is successfully authenticated. If the security key is not valid, the authentication request is denied. If there is no security key associated with the interface, it is determined whether there are any unassociated security keys for the user. If there are unassociated security keys, then the next unassociated security key is obtained. It is then determined whether the security key is valid. If the security key is not valid, it is determined again whether there are any unassociated security keys. If there are no unassociated security keys left, the authentication request is denied. If there is an available unassociated security key and it is valid, then the security key is bound to the interface, and the wireless interface is successfully authenticated.
[0046] In step 410, an authentication request is received from a wireless interface belonging to a user. This request may occur when the wireless interface is new to the network 170, for wireless interfaces whose security key has expired, for wireless interfaces whose connection was terminated, or the like.
[0047] In step 420, it is determined whether there is a security key associated with the wireless interface. The determination may be made from information in the wireless interface authentication process. If there is an associated security key, the method proceeds to step 430. If there is no associated security key, the method proceeds to step 440.
[0048] In step 430, where the security key is determined to be associated with the wireless interface, it is then determined whether that security key is valid. The determination may be made by comparing the security key information from the authentication request with the security key in secret database 150.
[0049] In step 440, where there is no security key associated with the wireless network 170, it is determined whether there are any unassociated security keys for the user. The determination may be made based on information from the authentication request, security key information associated with the user access profile saved in secret database 150, and the like. If there is an unassociated security key available, the method proceeds to step 450. If there are no unassociated security keys available, the method proceeds to step 490.
[0050] In step 450, where it was determined that there are unassociated security keys available, the next unassociated security key is obtained. All unassociated security keys are saved to a table, as described in step 350. In some embodiments, the table is included in secret database 150. In step 450, the next available unassociated security key from the table is considered.
[0051] In step 460, it is determined whether the security key under consideration is valid. The determination of whether the security key is valid is similar to the determination made in step 430. If the security key is not valid, the method returns to step 440. If the security key is valid, the method proceeds to step 470.
[0052] In step 470, the security key is bound to the wireless interface. The binding, or association, is formed similarly to the association formed in steps 240 and 360.
[0053] In step 480, the authentication of the wireless interface by security key is successful. In some embodiments, the method may proceed with further authentication steps. For example, in step 500, a determination may be made as to whether the security key has expired. If the key has expired, a re-keying process may commence in step 520. In the interim, however, the user may be subjected to restricted access or no access whatsoever. In some embodiments, the re-keying process may be a part of a different process while the user has limited or no access privileges. If they key is still valid, however, the user may enjoy full service access in step 510. Authenticating the wireless interface, however, allows the wireless interface to access the wireless network 170.
[0054] In step 490, the authentication request is denied. The wireless interface is not allowed to access the wireless network 170, or if there is an existing connection, it may be terminated.
[0055] While the present invention has been described in connection with a series of preferred embodiment, these descriptions are not intended to limit the scope of the invention to the particular forms set forth herein. To the contrary, the present descriptions are intended to cover such alternatives, modifications, and equivalents as may be included within the spirit and scope of the invention as defined by the appended claims and otherwise appreciated by one of ordinary skill in the art.
Claims
What is claimed is:
1. A method for pairing dynamic secrets in a secured wireless network, the method comprising:
identifying an access profile belonging to an authenticated user, the user having been authenticated as being authorized to access the secured wireless network, the access profile being specific to the authenticated user;
randomly generating a secret for the authenticated user, wherein the secret is unique to the authenticated user;
storing the secret in memory, the secret being stored in association with the identified access profile belonging to the authenticated user;
deriving one or more security keys from the secret;
saving the one or more derived security keys to a table in memory, the table including information concerning the security keys and whether each security key is associated with a wireless interface device;
generating an executable for configuring the wireless interface device to access the secured wireless network;
downloading the executable and at least one of the security keys as a part of the access profile to a wireless interface device belonging to the authenticated user, wherein executing the transferred executable on the wireless interface device configures the wireless interface device to access the secured wireless network using the security key and the access profile belonging to the authenticated user; and
updating the table to include the association between the security key and the wireless interface device belonging to the authenticated user and further associated with the access profile, wherein use of the security key to access the secured wireless network is restricted to the associated wireless interface device belonging to the authenticated user as identified by the associated access profile.
2. The method of claim 1, wherein updating the table includes storing the association between the security key and an identification of the wireless interface.
3. The method of claim 1, wherein updating the table includes storing the association between the security key and a radio of the wireless interface device.
4. The method of claim 1, further comprising updating the secret.
5. The method of claim 2, wherein the wireless interface identification includes a MAC address.
6. The method of claim 4, wherein updating the secret occurs after a predefined period of time.
7. The method of claim 4, wherein updating the secret occurs upon request by a system administrator.
8. The method of claim 4, wherein updating the secret comprises:
generating a new random secret unique to the authenticated user;
storing the new secret in memory with the access profile belonging to the user; and
requiring that the wireless interface be reauthenticated by the authenticated user before associating the new secret to the wireless interface.
9. The method of claim 8, wherein requiring the wireless interface to be re-authenticated comprises terminating the wireless connection between the wireless interface and the secured wireless network.
10. A system for pairing dynamic secrets in a secured wireless network, the system comprising:
a secret generation module stored in memory and executable by a processor to:
randomly generate a secret unique to an authenticated user, the user having been authenticated as being authorized to access the secured wireless network, and
derive one or more security secrets from the secret;
a secret database configured to store information concerning the secret in association with an access profile identified as belonging to the authenticated user, the access profile being specific to the authenticated user, the secret database comprising a table including information concerning the re security keys and whether each security key is associated with a wireless interface device;
an access profile generation module executable by the processor to generate an access profile for the authenticated user;
an executable generation module executable by the processor to generate an executable for using the access profile and the security key to configure the wireless interface to access the secured wireless network; and
a binding module stored in memory and executable by the processor to download the executable and at least one of the security keys as part of the access profile to a wireless interface device belonging to the authenticated user,
wherein executing the transferred executable on the wireless interface device configures the wireless interface device to access the secured wireless network using the security key and the access profile belonging to the authenticated user, and
wherein the table is updated to include the association between the security key and the wireless interface device belonging to the authenticated user and further associated with the access profile, wherein use of the security key to access the secured wireless network is restricted to the associated wireless interface device belonging to the authenticated user as identified by the associated access profile.
11. The system of claim 10, wherein the secret generation module is further executable by the processor to update the secret by generating a new random secret unique to the user.
12. A computer-readable storage medium having embodied thereon a program, the program being executable by a computer processor to perform a method for pairing dynamic secrets in a secured wireless network, the method comprising:
identifying an access profile belonging to an authenticated user, the user having been authenticated as being authorized to access the secured wireless network, the access profile being specific to the authenticated user;
randomly generating a secret for the authenticated user, wherein the secret is unique to the authenticated user;
storing the secret in memory, the secret being stored in association with the identified access profile belonging to the authenticated user, the access profile;
deriving one or more security keys from the secret;
saving the one or more derived security keys to a table in memory, the table including information concerning the security keys and whether each security key is associated with a wireless interface device;
generating an executable for configuring the wireless interface device to access the secured wireless network;
downloading the executable and at least one of the security keys as a part of the access profile to a wireless interface device belonging to the authenticated user, wherein executing the transferred executable on the wireless interface device configures the wireless interface device to access the secured wireless network using the security key and the access profile belonging to the authenticated user; and
updating the table to include the association between the security key and the wireless interface belonging to the authenticated user, wherein use of the security key to access the secured wireless network is restricted to the associated wireless interface belonging to the authenticated user as identified by the associated access profile.
13. The computer-readable storage medium of claim 12, wherein the program is further executable by the processor to update the secret, wherein the wireless interface must be reauthenticated by the user.
Patent Citations (185)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4176356(A) | 1979-11-01 | Foster | Applicant |
| US4193077(A) | 1980-03-01 | Greenberg | Applicant |
| US4253193(A) | 1981-02-01 | Kennard | Applicant |
| US4305052(A) | 1981-12-01 | Baril | Applicant |
| US4513412(A) | 1985-04-01 | Cox | Applicant |
| US4814777(A) | 1989-03-01 | Monser | Applicant |
| US5097484(A) | 1992-03-01 | Akaiwa | Applicant |
| US5173711(A) | 1992-12-01 | Takeuchi | Applicant |
| US5203010(A) | 1993-04-01 | Felix | Applicant |
| US5220340(A) | 1993-06-01 | Shafai | Applicant |
| US5373548(A) | 1994-12-01 | McCarthy | Applicant |
| US5507035(A) | 1996-04-01 | Bantz | Applicant |
| US5559800(A) | 1996-09-01 | Mousseau | Applicant |
| US5754145(A) | 1998-05-01 | Evans | Applicant |
| US5767809(A) | 1998-06-01 | Chuang | Applicant |
| US5802312(A) | 1998-09-01 | Lazaridis | Applicant |
| US5964830(A) | 1999-10-01 | Durett | Applicant |
| US6034638(A) | 2000-03-01 | Thiel | Applicant |
| US6094177(A) | 2000-07-01 | Yamamoto | Applicant |
| US6266528(B1) | 2001-07-01 | Farzaneh | Applicant |
| US6292153(B1) | 2001-09-01 | Aiello | Applicant |
| US6307524(B1) | 2001-10-01 | Britain | Applicant |
| US6317599(B1) | 2001-11-01 | Rappaport | Applicant |
| US6326922(B1) | 2001-12-01 | Hegendoerfer | Applicant |
| US6337628(B2) | 2002-01-01 | Campana, Jr. | Applicant |
| US6337668(B1) | 2002-01-01 | Ito | Applicant |
| US6339404(B1) | 2002-01-01 | Johnson | Applicant |
| US6345043(B1) | 2002-02-01 | Hsu | Applicant |
| US6356242(B1) | 2002-03-01 | Ploussios | Applicant |
| US6356243(B1) | 2002-03-01 | Schneider | Applicant |
| US6356905(B1) | 2002-03-01 | Gershman | Applicant |
| US6377227(B1) | 2002-04-01 | Zhu | Applicant |
| US6392610(B1) | 2002-05-01 | Braun | Applicant |
| US6404386(B1) | 2002-06-01 | Proctor, Jr. | Applicant |
| US6407719(B1) | 2002-06-01 | Ohira | Applicant |
| US6442507(B1) | 2002-08-01 | Skidmore | Applicant |
| US6445688(B1) | 2002-09-01 | Garces | Applicant |
| US6493679(B1) | 2002-12-01 | Rappaport | Applicant |
| US6498589(B1) | 2002-12-01 | Horii | Applicant |
| US6499006(B1) | 2002-12-01 | Rappaport | Applicant |
| US6507321(B2) | 2003-01-01 | Oberschmidt | Applicant |
| US6625454(B1) | 2003-09-01 | Rappaport | Applicant |
| US6674459(B2) | 2004-01-01 | Ben-Shachar | Applicant |
| US6701522(B1) | 2004-03-01 | Rubin | Applicant |
| US6725281(B1) | 2004-04-01 | Zintel | Applicant |
| US6753814(B2) | 2004-06-01 | Killen | Applicant |
| US6762723(B2) | 2004-07-01 | Nallo | Applicant |
| US6779004(B1) | 2004-08-01 | Zintel | Applicant |
| US6807577(B1) | 2004-10-01 | Gillespie et al. | Examiner |
| US6819287(B2) | 2004-11-01 | Sullivan | Applicant |
| US6876280(B2) | 2005-04-01 | Nakano | Applicant |
| US6888504(B2) | 2005-05-01 | Chiang | Applicant |
| US6888893(B2) | 2005-05-01 | Li | Applicant |
| US6892230(B1) | 2005-05-01 | Gu | Applicant |
| US6906678(B2) | 2005-06-01 | Chen | Applicant |
| US6910068(B2) | 2005-06-01 | Zintel | Applicant |
| US6924768(B2) | 2005-08-01 | Wu | Applicant |
| US6931429(B2) | 2005-08-01 | Gouge | Applicant |
| US6941143(B2) | 2005-09-01 | Mathur | Applicant |
| US6947727(B1) | 2005-09-01 | Brynielsson | Applicant |
| US6950019(B2) | 2005-09-01 | Bellone | Applicant |
| US6950523(B1) | 2005-09-01 | Brickell | Applicant |
| US6961028(B2) | 2005-11-01 | Joy | Applicant |
| US6973622(B1) | 2005-12-01 | Rappaport | Applicant |
| US6975834(B1) | 2005-12-01 | Forster | Applicant |
| US7034770(B2) | 2006-04-01 | Yang | Applicant |
| US7043277(B1) | 2006-05-01 | Pfister | Applicant |
| US7043633(B1) | 2006-05-01 | Fink et al. | Examiner |
| US7050809(B2) | 2006-05-01 | Lim | Applicant |
| US7064717(B2) | 2006-06-01 | Kaluzni | Applicant |
| US7085814(B1) | 2006-08-01 | Gandhi | Applicant |
| US7089307(B2) | 2006-08-01 | Zintel | Applicant |
| US7127234(B2) | 2006-10-01 | Ishii | Examiner |
| US7130895(B2) | 2006-10-01 | Zintel | Applicant |
| US7171475(B2) | 2007-01-01 | Weisman | Applicant |
| US7181620(B1) | 2007-02-01 | Hur | Applicant |
| US7197297(B2) | 2007-03-01 | Myles et al. | Applicant |
| US7234063(B1) | 2007-06-01 | Baugher et al. | Applicant |
| US7234156(B2) | 2007-06-01 | French et al. | Examiner |
| US7421578(B1) | 2008-09-01 | Huang et al. | Examiner |
| US7562385(B2) | 2009-07-01 | Thione et al. | Examiner |
| US2002/0009199(A1) | 2002-01-01 | Ala-Laurila et al. | Examiner |
| US2002/0031130(A1) | 2002-03-01 | Tsuchiya | Applicant |
| US2002/0047800(A1) | 2002-04-01 | Proctor, Jr. | Applicant |
| US2002/0080767(A1) | 2002-06-01 | Lee | Applicant |
| US2002/0084942(A1) | 2002-07-01 | Tsai | Applicant |
| US2002/0105471(A1) | 2002-08-01 | Kojima | Applicant |
| US2002/0112058(A1) | 2002-08-01 | Weisman | Applicant |
| US2002/0158798(A1) | 2002-10-01 | Chiang | Applicant |
| US2002/0169966(A1) | 2002-11-01 | Nyman et al. | Examiner |
| US2002/0170064(A1) | 2002-11-01 | Monroe | Applicant |
| US2003/0026240(A1) | 2003-02-01 | Eyuboglu | Applicant |
| US2003/0030588(A1) | 2003-02-01 | Kalis | Applicant |
| US2003/0063591(A1) | 2003-04-01 | Leung | Applicant |
| US2003/0122714(A1) | 2003-07-01 | Wannagot | Applicant |
| US2003/0162533(A1) | 2003-08-01 | Moles | Applicant |
| US2003/0169330(A1) | 2003-09-01 | Ben-Shachar | Applicant |
| US2003/0184490(A1) | 2003-10-01 | Raiman | Applicant |
| US2003/0189514(A1) | 2003-10-01 | Miyano | Applicant |
| US2003/0189521(A1) | 2003-10-01 | Yamamoto | Applicant |
| US2003/0189523(A1) | 2003-10-01 | Ojantakanen | Applicant |
| US2003/0191935(A1) | 2003-10-01 | Ferguson | Examiner |
| US2003/0196084(A1) | 2003-10-01 | Okereke et al. | Examiner |
| US2003/0210207(A1) | 2003-11-01 | Suh | Applicant |
| US2003/0227414(A1) | 2003-12-01 | Saliga | Applicant |
| US2004/0014432(A1) | 2004-01-01 | Boyle | Applicant |
| US2004/0017310(A1) | 2004-01-01 | Vargas-Hurlston et al. | Applicant |
| US2004/0017860(A1) | 2004-01-01 | Liu | Applicant |
| US2004/0027291(A1) | 2004-02-01 | Zhang | Applicant |
| US2004/0027304(A1) | 2004-02-01 | Chiang | Applicant |
| US2004/0032378(A1) | 2004-02-01 | Volman | Applicant |
| US2004/0036651(A1) | 2004-02-01 | Toda | Applicant |
| US2004/0036654(A1) | 2004-02-01 | Hsieh | Applicant |
| US2004/0041732(A1) | 2004-03-01 | Aikawa | Applicant |
| US2004/0048593(A1) | 2004-03-01 | Sano | Applicant |
| US2004/0058690(A1) | 2004-03-01 | Ratzel | Applicant |
| US2004/0061653(A1) | 2004-04-01 | Webb | Applicant |
| US2004/0070543(A1) | 2004-04-01 | Masaki | Applicant |
| US2004/0073786(A1) | 2004-04-01 | O'Neill et al. | Examiner |
| US2004/0080455(A1) | 2004-04-01 | Lee | Applicant |
| US2004/0095278(A1) | 2004-05-01 | Kanemoto | Applicant |
| US2004/0097217(A1) | 2004-05-01 | McClain | Applicant |
| US2004/0114535(A1) | 2004-06-01 | Hoffmann | Applicant |
| US2004/0125777(A1) | 2004-07-01 | Doyle | Applicant |
| US2004/0190477(A1) | 2004-09-01 | Olson | Applicant |
| US2004/0203593(A1) | 2004-10-01 | Whelan et al. | Examiner |
| US2004/0214570(A1) | 2004-10-01 | Zhang | Applicant |
| US2004/0260800(A1) | 2004-12-01 | Gu | Applicant |
| US2005/0022210(A1) | 2005-01-01 | Zintel | Applicant |
| US2005/0041739(A1) | 2005-02-01 | Li | Applicant |
| US2005/0042988(A1) | 2005-02-01 | Hoek | Applicant |
| US2005/0074018(A1) | 2005-04-01 | Zintel | Applicant |
| US2005/0097503(A1) | 2005-05-01 | Zintel | Applicant |
| US2005/0100166(A1) | 2005-05-01 | Smetters et al. | Examiner |
| US2005/0135480(A1) | 2005-06-01 | Li | Applicant |
| US2005/0138137(A1) | 2005-06-01 | Encarnacion | Applicant |
| US2005/0138193(A1) | 2005-06-01 | Encarnacion | Applicant |
| US2005/0152305(A1) | 2005-07-01 | Ji et al. | Examiner |
| US2005/0180381(A1) | 2005-08-01 | Retzer | Applicant |
| US2005/0188193(A1) | 2005-08-01 | Kuehnel et al. | Examiner |
| US2005/0240665(A1) | 2005-10-01 | Gu | Applicant |
| US2005/0250472(A1) | 2005-11-01 | Silvester et al. | Applicant |
| US2005/0267935(A1) | 2005-12-01 | Ghandi | Applicant |
| US2005/0268107(A1) | 2005-12-01 | Harris | Applicant |
| US2006/0052085(A1) | 2006-03-01 | Gregrio Rodriguez et al. | Examiner |
| US2006/0080415(A1) | 2006-04-01 | Tu | Examiner |
| US2006/0080741(A1) | 2006-04-01 | Nair | Applicant |
| US2006/0089123(A1) | 2006-04-01 | Frank | Examiner |
| US2006/0094371(A1) | 2006-05-01 | Nguyen | Applicant |
| US2006/0098607(A1) | 2006-05-01 | Zeng | Applicant |
| US2006/0123124(A1) | 2006-06-01 | Weisman | Applicant |
| US2006/0123125(A1) | 2006-06-01 | Weisman | Applicant |
| US2006/0123455(A1) | 2006-06-01 | Pai | Applicant |
| US2006/0168159(A1) | 2006-07-01 | Weisman | Applicant |
| US2006/0184660(A1) | 2006-08-01 | Rao et al. | Applicant |
| US2006/0184661(A1) | 2006-08-01 | Weisman | Applicant |
| US2006/0184693(A1) | 2006-08-01 | Rao | Applicant |
| US2006/0189298(A1) | 2006-08-01 | Marcelli | Applicant |
| US2006/0224690(A1) | 2006-10-01 | Falkenburg | Applicant |
| US2006/0225107(A1) | 2006-10-01 | Seetharaman | Applicant |
| US2006/0227761(A1) | 2006-10-01 | Scott, III | Applicant |
| US2006/0239369(A1) | 2006-10-01 | Lee | Applicant |
| US2006/0291434(A1) | 2006-12-01 | Gu | Applicant |
| US2007/0027622(A1) | 2007-02-01 | Cleron | Applicant |
| US2007/0135167(A1) | 2007-06-01 | Liu | Applicant |
| US2007/0143832(A1) | 2007-06-01 | Perrella et al. | Examiner |
| US2007/0150736(A1) | 2007-06-01 | Cukier et al. | Examiner |
| US2007/0189537(A1) | 2007-08-01 | Zhang et al. | Examiner |
| US2007/0199053(A1) | 2007-08-01 | Sandhu et al. | Examiner |
| US2007/0211659(A1) | 2007-09-01 | Li et al. | Examiner |
| US2007/0294528(A1) | 2007-12-01 | Shoji et al. | Examiner |
| US2008/0119165(A1) | 2008-05-01 | Mittal et al. | Examiner |
| US2008/0307515(A1) | 2008-12-01 | Drokov et al. | Examiner |
| EP352787 | 1989-07-01 | Applicant | |
| EP534612 | 1993-03-01 | Applicant | |
| EP1315311 | 2003-05-01 | Applicant | |
| EP1450521 | 2004-08-01 | Applicant | |
| EP1608108 | 2005-12-01 | Applicant | |
| JP3038933 | 1989-07-01 | Applicant | |
| JP2008088633 | 1996-02-01 | Applicant | |
| JP2001057560 | 2002-02-01 | Applicant | |
| JP2005354249 | 2005-12-01 | Applicant | |
| JP2006060408 | 2006-03-01 | Applicant | |
| WO225967 | 2002-03-01 | Applicant | |
| WO3079484 | 2003-09-01 | Applicant |
Non-Patent Literature (22)
- Ken Tang, et al., “MAC Layer Broadcast Support in 802.11 Wireless Networks,” Computer Science Department, University of California, Los Angeles, 2000 IEEE, pp. 544-548.Applicant
- Ken Tang, et al., “MAC Reliable Broadcast in Ad Hoc Networks,” Computer Science Department, University of California, Los Angeles, 2001 IEEE, pp. 1008-1013.Applicant
- Vincent D. Park, et al., “A Performance Comparison of the Temporally-Ordered Routing Algorithm and Ideal Link-State Routing,” IEEE, Jul. 1998, pp. 592-598.Applicant
- Ian F. Akyildiz, et al., “A Virtual Topology Based Routing Protocol for Multihop Dynamic Wireless Networks,” Broadband and Wireless Networking Lab, School of Electrical and Computer Engineering, Georgia Institute of Technology.Applicant
- Dell Inc., “How Much Broadcast and Multicast Traffic Should I Allow in My Network,” PowerConnect Application Note #5, Nov. 2003.Applicant
- Toskala, Antti, “Enhancement of Broadcast and Introduction of Multicast Capabilities in RAN,” Nokia Networks, Palm Springs, California, Mar. 13-16, 2001.Applicant
- Microsoft Corporation, “IEEE 802.11 Networks and Windows XP,” Windows Hardware Developer Central, Dec. 4, 2001.Applicant
- Festag, Andreas, “What is MOMBASA?” Telecommunication Networks Group (TKN), Technical University of Berlin, Mar. 7, 2002.Applicant
- Hewlett Packard, “HP ProCurve Networking: Enterprise Wireless LAN Networking and Mobility Solutions,” 2003.Applicant
- Dutta, Ashutosh et al., “MarconiNet Supporting Streaming Media Over Localized Wireless Multicast,” Proc. of the 2d Int'l Workshop on Mobile Commerce, 2002.Applicant
- Dunkels, Adam et al., “Making TCP/IP Viable for Wireless Sensor Networks,” Proc. of the 1st Euro. Workshop on Wireless Sensor Networks, Berlin, Jan. 2004.Applicant
- Dunkels, Adam et al:, “Connecting Wireless Sensomets with TCP/IP Networks,” Proc. of the 2d Int'l Conf. on Wired Networks, Frankfurt, Feb. 2004.Applicant
- Cisco Systems, “Cisco Aironet Access Point Software Configuration Guide: Configuring Filters and Quality of Service,” Aug. 2003.Applicant
- Hirayama, Koji et al., “Next-Generation Mobile-Access IP Network,” Hitachi Review vol. 49, No. 4, 2000.Applicant
- Pat Calhoun et al., “802.11r strengthens wireless voice,” Technology Update, Network World, Aug. 22, 2005, http://www.networkworld.com/news/tech/2005/082208techupdate.html.Applicant
- Areg Alimian et al., “Analysis of Roaming Techniques,” doc.:IEEE 802.11-04/0377r1, Submission, Mar. 2004.Applicant
- Information Society Technologies Ultrawaves, “System Concept / Architecture Design and Communication Stack Requirement Document,” Feb. 23, 2004.Applicant
- Golmie, Nada, “Coexistence in Wireless Networks: Challenges and System-Level Solutions in the Unlicensed Bands,” Cambridge University Press, 2006.Applicant
- Mawa, Rakesh, “Power Control in 3G Systems,” Hughes Systique Corporation, Jun. 28, 2006.Applicant
- Wennstrom, Mattias et al., “Transmit Antenna Diversity in Ricean Fading MIMO Channels with Co-Channel Interference,” 2001.Applicant
- Steger, Christopher et al., “Performance of IEEE 802.11b Wireless LAN in an Emulated Mobile Channel,” 2003.Applicant
- Chang, Nicholas B. et al., “Optimal Channel Probing and Transmission Scheduling for Opportunistics Spectrum Access,” Sep. 2007.Applicant