Remote cable access point reset

Information

  • Patent Grant
  • 9792188
  • Patent Number
    9,792,188
  • Date Filed
    Tuesday, May 1, 2012
    12 years ago
  • Date Issued
    Tuesday, October 17, 2017
    7 years ago
Abstract
The system monitors a wireless device, detects when the device has failed or is not operating properly, and is able to remotely reset the device. The device may be reset remotely without a technician required to physically attend to the device. This out of band management allows for quicker, cheaper and more efficient handling of undesired states of a device, such as failure to operate. For a modem, the system may detect that the modem is not broadcasting a signal or is not communicating with the Internet or other network. The reset may be implemented through an access point in communication with the malfunctioning modem. For an access point, the system may detect that the access point is not communicating with a modem or another access point. The reset may be implemented by a neighboring access point or modem.
Description
BACKGROUND OF THE INVENTION

The World Wide Web has expanded to provide web services to many consumers. Many businesses provide a web service such as Wi-Fi for their employees and customers use. The web service may allow employees greater freedom and efficiency to access company assets and perform their jobs. Providing a web service to customers may allow for more efficient business transactions with the company.


Providing a reliable web service for employees and customers is important to may businesses. As such, it is useful to know when a web service has failed. When a failure has been detected, it is important to restore service to the web service as soon as possible.


There is a need in the art for providing improved web service maintenance and repair.


SUMMARY OF THE CLAIMED INVENTION

The present technology monitors a wireless device, detects when the device has failed or is not operating properly, and is able to remotely reset the device. The device may be reset remotely without a technician required to physically attend to the device. This out of band management allows for quicker, cheaper and more efficient handling of undesired states of a device, such as failure to operate. For a modem, the system may detect that the modem is not broadcasting a signal or is not communicating with the Internet or other network. The reset may be implemented through an access point in communication with the malfunctioning modem. For an access point, the system may detect that the access point is not communicating with a modem or another access point. The reset may be implemented by a neighboring access point or modem.


An embodiment may include a method for rebooting a remote device. An indication of a service failure may be received for a remote device. The indication may be received from a second device in communication with the remote device. A reboot command may be transmitted to the second device. The reboot command may be executable by the second device to cause the second device to initiate a reboot in the remote device. An embodiment may include a computer readable storage medium having executable instructions which, when executed by a processor, perform the method of rebooting a remote device.


An embodiment may include a system having a processor, memory, and one or more modules stored in memory. The one or more modules may be executable to receive an indication of a service failure for the remote device. The indication may be received from a second device in communication with the remote device. The one or more modules may further be executable to transmit a reboot command to the second device. The reboot command may be executable by the second device to cause the second device to initiate a reboot in the remote device.


An embodiment may include a method for rebooting a cable modem. An access point may detect a cable modem has failed. An indication of the cable modem failure may be transmitted to a remote device by the access point. A reboot command for the cable modem may be received by the access point from the remote device. Reboot of the cable modem may be initialized by the access point.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a block diagram of an exemplary system for remotely resetting a wireless device.



FIG. 2 is a flow chart of an exemplary method for remotely resetting a cable modem.



FIG. 3 is a flow chart of an exemplary method for detecting cable modem service failure.



FIG. 4 is a flow chart of an exemplary method for remotely resetting an access point.



FIG. 5 is a block diagram of an exemplary system for implementing a computing device.



FIG. 6 is a block diagram of an exemplary system for implementing a mobile device.





DETAILED DESCRIPTION

The present technology monitors a wireless device, detects when the device has failed or is not operating properly, and is able to remotely reset the device. The device may be reset remotely without a technician required to physically attend to the device. This out of band management allows for quicker, cheaper and more efficient handling of undesired states of a device, such as failure to operate. For a modem, the system may detect that the modem is not broadcasting a signal or is not communicating with the Internet or other network. The reset may be implemented through an access point in communication with the malfunctioning modem. For an access point, the system may detect that the access point is not communicating with a modem or another access point. The reset may be implemented by a neighboring access point or modem.


In some environments, a plurality of access points may be used to provide a wireless signals to an extended area. The plurality of access points may be used with one or more modems, such as a cable modem, and form a “mesh” of wireless signals.



FIG. 1 is a block diagram of an exemplary system for remotely resetting a wireless device. FIG. 1 includes mobile device 110, cable modem management sever 120, and wireless network management server 130. Each of mobile device 110 and servers 120 and 130 communicate with network 140.


Wireless network management server 130 may be implemented as one or more servers and machines, including one or more network servers, application servers, work stations, a combination of these or one or more other computing devices. Sever 130 may communicate and control one or more access points 160, 170 and 190, as well as cable modem 150. In some embodiments, management application 135, stored in memory and executable by a processor of wireless network management server 130, may manage communications with access point 170. Application 115 communications may include receiving status updates and pings from an access point, receiving fail-over messages from an access point, transmitting cable modem reset command to an access point in direct or indirect communication with the cable modem, and other communication. Application 115 may also provide an interface which provides information for one or more access points and cable modems. The interface may be updated periodically based on information received from an access point or cable modem and may be provided to an administrator. The interface may also receive input from an administrator regarding the management of the one or more access points and cable modem.


Mobile device 110 may be implemented as a smart phone, notebook computer, net book computer, a tablet computer, or other mobile computing device. Mobile device 110 may include management application 115, stored in mobile device memory and executable by a mobile device processor. When executed, management application 115 may perform operations similar to that of management application 135 of wireless network management server 130. For example, management application 115 may communicate with and manage cable modem 150 and one or more access points 160-180 through network 140. In some embodiments, management application 115 may receive messages originating from an access point 170 and communicated through cable modem 150, such as for example message indicating the status of the particular access point, another access point or the cable modem, a fail-over message, or other information. Management application 115 may also transmit information to cable modem 150, an access point 170 in direct communication with cable modem 150 or an access point in indirect communication with cable modem 150. The information may include a status request, reset request, or other information.


Cable modem management 120 may be implemented as one or more servers and machines, including one or more network servers, application servers, work stations, a combination of these or one or more other computing devices. Cable modem management 120 may include management application 125, which may be stored in cable modem management memory and executable by a cable modem management processor. When executed, the management application 125 may communicate with and manage cable modem 150. In some embodiments, management application 125 may reset cable modem 150, adjust settings and parameters of cable modem 150, control cable modem 150 communication with an access point, and perform other functions.


Network 140 may facilitate communication of data between different servers, devices and machines. The network may be implemented as a private network, public network, intranet, the Internet, or a combination of these networks.


Cable modem 150 and access points 160, 170 and 180 are included within a wireless environment 190. Cable modem 150 may communicate with network 140 and provide network access to access points 160-180. When network 140 is the Internet, cable modem 150 may provide internet access through access points 160-180. Through described herein as a cable modem, it is intended that other types of communication devices may be used interchangeably with a cable modem, such as for example, another access point, point to point link, macro or micro cellular backhaul, and so forth.


Access points 160-180 may directly or indirectly communicate with cable modem 150. For example, access points 160 and 170 directly receive a signal from cable modem 150 and broadcast a signal within wireless environment 190. Access point 180 receives a network signal from access point 170 rather than directly from cable modem 150. In some embodiments, a plurality of access points may be chained together to provided an extended signal coverage area within wireless environment 190.


Some access points may be in communication with more than one cable modem (not illustrated in FIG. 190). In some embodiments, when a cable modem 150 fails, an access point in communication with network 150 through modem 150 may “fail-over” to second cable modem. The second cable modem may be in direct communication or indirect communication with the access point when the access point “fails over” and communicates with network 140 via the second cable modem.


When an access point fails-over due to a failed cable modem, the access point may send a message to management application 135 of wireless network management 130. The message may indicate that the access point failed-over, the access point identify, the cable modem that failed and the cable modem now working with the access point, and other data. The management application 135 may receive the message and instruct the access point to reset the failed cable modem.


A failed over access point may restart a failed cable modem in many ways. In some embodiments, the access point may transmit a wireless signal to the cable modem that causes a reset. Alternatively, the access point may communicate with the modem via WiFi or a wired signal. The wireless signal may be a radio frequency signal, and optical signal, IR signal, or some other wireless signal. For example, the access point and cable modem may be configured to communicate via Bluetooth, and the reset command may be sent from the access point to the cable modem via Bluetooth message. In some embodiments, the failed over access point may restart the failed cable modem using a wired connection. In some embodiments, the failed cable modem and access point may share a wired connection. In some embodiments, the failed-over access point may transmit a reset command or other message to failed cable modem via power line communication. Power line communication may be configured between devices that are powered by the same electric power transmission system.


In some embodiments, the reset of a cable modem may be configurable. For example, communication between an access point and cable modem may be secure. The cable modem operator and access point operator may be different entities, and the operator of one may not want to provide a publicly accessible way to access their device. Communications between an access point and a cable modem may be secured by providing a layer two Ethernet level solution via a VLAN such that only known VLANs may be connected. Alternatively, a secure tunnel may be established between the access point and the cable modem. In embodiments, the communication may also be secured by use of encryption.


In some embodiments, such as a mesh configuration, different access points may be a master device and some access points and cable modems may be slaves. In this case, a master access point may transmit a beacon signal to a slave cable modem or access point only when a “send reset command” message is received from a management application 135 or 115.


A reset command may be sent to an access point to reset a cable modem remotely from over network 140 or locally. For example, an administrator may be within the wireless environment 190 to provide the reset command to an access point via mobile device 110. In this scenario, mobile device 110 may be brought within range of an access point, whether within the same room, the same building, or outside the building but within range of an access point. The operation status of the cable modem may be supplied by the access point to the mobile device, which can either wait for user's input to trigger a reset or automatically trigger a reset based on some pre-defined set of conditions (e.g., an outage time threshold) and/or policies (e.g., user with certain credential that is provided to the access point). The command can then be provided by mobile device 110 to reset the cable modem. Though not provided over network 140, providing a reset command from within the wireless environment may still be more efficient than getting within a few feet of cable modem 150 and physically initiating a reset operation.



FIG. 2 is a flow chart of an exemplary method for remotely resetting a cable modem. Cable modem 150 provides a wireless signal to one or more access points 160-180 directly or indirectly, at step 210. Access points 160-180 relay the signal and communicate with the cable modem at step 220. The cable modem 150 and access points 160-180 provide wireless signals that create wireless environment 190. Access points may communicate with wireless signal compatible devices, such as wireless computers and smart phones with wi-fi capability, within wireless environment 190 and facilitate communication between the wireless signal compatible devices and network 140.


A determination is made as to whether cable modem 150 is detected to fail at step 230. The cable modem may be detected to fail by periodically communicating with an external machine or gateway via the cable modem 150. Detecting cable modem failure is discussed in more detail with respect to the method of FIG. 3.


If cable modem is operational, the method of FIG. 2 returns to step 220. If the cable modem is detected to have failed, an access point notifies wireless network manager 135 of the cable modem failure at step 240. Notification by an access point may include a fail-over by the access point from the failed cable modem to an alternate cable modem that is operation and communicates with network 140. The communication with the alternate cable modem may be a direct communication or indirect communication via one or more intervening access points. In some embodiments, the failed over access point may notify cable modem management application 125 of the failure, and application 125 will instruct the access point how to proceed. For purposes of discussion, method 200 will be discussed in the context of communication with wireless network manager 135.


In some embodiments, an administrator may diagnose the cable modem from the wireless network manager 135 via an access point 170. The administrator may use the connectivity provided by the failover link to remotely login to the cable modem and verify its status, retrieve support information, and troubleshoot cause of failure. This process of retrieving information can also be automated by a manager application to retrieve support information as well as access point and cable modem status to help determine the cause of failure.


Wireless network manager 135 (or 115) receives the failure status message from the access point and transmits a reboot (or reset) instruction to the access point at step 250. The message may be sent from the wireless network manager through network 140 and the alternate cable modem through which the access point is communicating with network 140.


The access point receives the message and reboots (resets) cable modem at step 260. The reboot command may be sent via a wireless signal, such as a Bluetooth signal, or a wired signal such as a power line communication signal.


In some embodiments, it may be preferable to not immediately reset the modem to restore the original service level, but rather to diagnose the cause of failure. To limit service outage, a wireless service may be provided by the secondary access point while technicians conduct their troubleshooting work.



FIG. 3 is a flow chart of an exemplary method for detecting cable modem service failure. The method of FIG. 3 provides more detail for step 230 of the method of FIG. 2. An access point transmits a request to a network through a cable modem at step 310. The request may be to any anchor located over the network. For example, the request may be made to a network gateway as a ping, or some other simple request. A determination is made as to whether the access point receives a response to the request at step 320. The access point may wait a period of time before determining a time-out has occurred, or may receive a failed request message from the cable modem.


If a response is received by the access point, the cable modem service is determined to be operation at step 330. If a response is not received by the access point at step 320, the cable modem service is determined have failed at step 340.


In some embodiments, an access point may malfunction or fail. In this scenario, the access point may be reboot or reset similarly to reset of a cable modem. FIG. 4 is a flow chart of an exemplary method for remotely resetting an access point. Cable modem 150 provides a wireless signal to one or more access points 160-180 directly or indirectly, at step 210. Access points 160-180 relay the signal and communicate with the cable modem at step 220. The cable modem 150 and access points 160-180 provide wireless signals that create wireless environment 190.


A determination is made at step 430 as to whether the access point has failed. Access point failure may be detected by another access point in communication with the failed access point or a cable modem. For example, a cable modem may ping each access point in direct or indirect communication with the cable modem. An access point may be determined to fail when it does not respond to the ping or provides an error message in response to the ping. If access point failure is not detected, the method returns to step 420.


If access point failure is detected, the cable modem notifies the wireless network management application 135 (or 115) of the failed access point at step 440. The wireless network management application transmits a reboot instruction to the cable modem at step 450. The cable modem may reboot the access point at step 460. In some embodiments, the wireless network management application transmits a failure notice to cable modem management application 125, which in turn transmits an access point reboot command to cable modem 460.



FIG. 5 illustrates an exemplary computing system 500 that may be used to implement a computing device for use with the present technology. System 500 of FIG. 5 may be implemented in the contexts of the likes of cable modem management server 120, wireless network management server 130, and access points 160-180. The computing system 500 of FIG. 5 includes one or more processors 510 and memory 520. Main memory 520 stores, in part, instructions and data for execution by processor 510. Main memory 520 can store the executable code when in operation. The system 500 of FIG. 5 further includes a mass storage device 530, portable storage medium drive(s) 540, output devices 550, user input devices 560, a graphics display 570, and peripheral devices 580.


The components shown in FIG. 5 are depicted as being connected via a single bus 590. However, the components may be connected through one or more data transport means. For example, processor unit 510 and main memory 520 may be connected via a local microprocessor bus, and the mass storage device 530, peripheral device(s) 580, portable storage device 540, and display system 570 may be connected via one or more input/output (I/O) buses.


Mass storage device 530, which may be implemented with a magnetic disk drive or an optical disk drive, is a non-volatile storage device for storing data and instructions for use by processor unit 510. Mass storage device 530 can store the system software for implementing embodiments of the present invention for purposes of loading that software into main memory 520.


Portable storage device 540 operates in conjunction with a portable non-volatile storage medium, such as a floppy disk, compact disk or Digital video disc, to input and output data and code to and from the computer system 500 of FIG. 5. The system software for implementing embodiments of the present invention may be stored on such a portable medium and input to the computer system 500 via the portable storage device 540.


Input devices 560 provide a portion of a user interface. Input devices 560 may include an alpha-numeric keypad, such as a keyboard, for inputting alpha-numeric and other information, or a pointing device, such as a mouse, a trackball, stylus, or cursor direction keys. Additionally, the system 500 as shown in FIG. 5 includes output devices 550. Examples of suitable output devices include speakers, printers, network interfaces, and monitors.


Display system 570 may include a liquid crystal display (LCD) or other suitable display device. Display system 570 receives textual and graphical information, and processes the information for output to the display device.


Peripherals 580 may include any type of computer support device to add additional functionality to the computer system. For example, peripheral device(s) 580 may include a modem or a router.


The components contained in the computer system 500 of FIG. 5 are those typically found in computer systems that may be suitable for use with embodiments of the present invention and are intended to represent a broad category of such computer components that are well known in the art. Thus, the computer system 500 of FIG. 5 can be a personal computer, hand held computing device, telephone, mobile computing device, workstation, server, minicomputer, mainframe computer, or any other computing device. The computer can also include different bus configurations, networked platforms, multi-processor platforms, etc. Various operating systems can be used including Unix, Linux, Windows, Macintosh OS, Palm OS, and other suitable operating systems.



FIG. 6 is a block diagram of an exemplary system for implementing a mobile device for use with the present technology, such as for mobile device 110. The mobile device 600 of FIG. 6 includes one or more processors 610 and memory 660. Memory 660 stores, in part, programs, instructions and data for execution and processing by processor 610. The system 600 of FIG. 6 further includes storage 630, one or more antennas 640, a display system 650, inputs 660, one or more microphones 670, and one or more speakers 680.


The components shown in FIG. 6 are depicted as being connected via a single bus 626. However, the components 610-680 may be connected through one or more data transport means. For example, processor unit 610 and main memory 660 may be connected via a local microprocessor bus, and storage 630, display system 650, input 660, and microphone 670 and speaker 680 may be connected via one or more input/output (I/O) buses.


Memory 660 may include local memory such as RAM and ROM, portable memory in the form of an insertable memory card or other attachment (e.g., via universal serial bus), a magnetic disk drive or an optical disk drive, a form of FLASH or PROM memory, or other electronic storage medium. Memory 660 can store the system software for implementing embodiments of the present invention for purposes of loading that software into main memory 610.


Antenna 640 may include one or more antennas for communicating wirelessly with another device. Antenna 640 may be used, for example, to communicate wirelessly via Wi-Fi, Bluetooth, with a cellular network, or with other wireless protocols and systems. The one or more antennas may be controlled by a processor 610, which may include a controller, to transmit and receive wireless signals. For example, processor 610 execute programs stored in memory 660 to control antenna 640 transmit a wireless signal to a cellular network and receive a wireless signal from a cellular network.


Display system 650 may include a liquid crystal display (LCD), a touch screen display, or other suitable display device. Display system 670 may be controlled to display textual and graphical information and output to text and graphics through a display device. When implemented with a touch screen display, the display system may receive input and transmit the input to processor 610 and memory 660.


Input devices 660 provide a portion of a user interface. Input devices 660 may include an alpha-numeric keypad, such as a keyboard, for inputting alpha-numeric and other information, buttons or switches, a trackball, stylus, or cursor direction keys.


Microphone 670 may include one or more microphone devices which transmit captured acoustic signals to processor 610 and memory 660. The acoustic signals may be processed to transmit over a network via antenna 640.


Speaker 680 may provide an audio output for mobile device 600. For example, a signal received at antenna 640 may be processed by a program stored in memory 660 and executed by processor 610. The output of the executed program may be provided to speaker 680 which provides audio. Additionally, processor 610 may generate an audio signal, for example an audible alert, and output the audible alert through speaker 680.


The mobile device system 600 as shown in FIG. 6 may include devices and components in addition to those illustrated in FIG. 6. For example, mobile device system 600 may include an additional network interface such as a universal serial bus (USB) port.


The components contained in the computer system 600 of FIG. 6 are those typically found in mobile device systems that may be suitable for use with embodiments of the present invention and are intended to represent a broad category of such mobile device components that are well known in the art. Thus, the computer system 600 of FIG. 6 can be a cellular phone, smart phone, hand held computing device, minicomputer, or any other computing device. The mobile device can also include different bus configurations, networked platforms, multi-processor platforms, etc. Various operating systems can be used including Unix, Linux, Windows, Macintosh OS, Google OS, Palm OS, and other suitable operating systems.


The foregoing detailed description of the technology herein has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the technology to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. The described embodiments were chosen in order to best explain the principles of the technology and its practical application to thereby enable others skilled in the art to best utilize the technology in various embodiments and with various modifications as are suited to the particular use contemplated. It is intended that the scope of the technology be defined by the claims appended hereto.

Claims
  • 1. A method for rebooting a first cable modem by a wireless access point, the method comprising: detecting, by the wireless access point, a service failure of the first cable modem, in response to not receiving a response, or receiving a failed request message, from the first cable modem to a request sent by the wireless access point;generating, by the wireless access point, an indication of the service failure of the first cable modem, the indication being adapted for transmission to a management device; andin response to receiving a reboot command from the management device at the wireless access point, generating a wireless command signal for wireless transmission by the wireless access point, the wireless command signal being adapted to cause the first cable modem to reboot in response to wirelessly receiving the wireless command signal.
  • 2. The method of claim 1, wherein the wireless command signal is adapted for transmission to the first cable modem through a second access point.
  • 3. The method of claim 1, wherein the indication is adapted for transmission to the management device via a second cable modem.
  • 4. The method of claim 1, wherein the indication includes status information of the first cable modem.
  • 5. The method of claim 1, wherein the indication is adapted to be received by an application on the management device, the management device being a wireless device.
  • 6. The method of claim 1, wherein the wireless command signal is adapted for transmission to the first cable modem via a secure communication channel between the wireless access point and the first cable modem.
  • 7. The method of claim 1, wherein the indication is adapted for transmission to the management device via the internet, the management device being a remote server.
  • 8. The method of claim 1, further comprising: failing over, by the wireless access point, to a second cable modem until the first cable modem resumes operation after rebooting.
  • 9. A non-transitory computer readable storage medium having embodied thereon a program, the program being executable by a processor to perform a method for rebooting a first cable modem, the method comprising: receiving an indication of a service failure of the first cable modem, the indication being received from a wireless access point in communication with the first cable modem, the service failure detected following an absence of a response by the first cable modem to a request sent by the wireless access point; andgenerating a reboot command for transmission to the wireless access point, the reboot command being executable by the wireless access point to transmit a wireless command signal to the first cable modem, the wireless command signal being adapted to cause the first cable modem to reboot in response to wirelessly receiving the wireless command signal.
  • 10. The non-transitory computer readable storage medium of claim 9, wherein the reboot command is adapted for transmission to the wireless access point through a second access point.
  • 11. The non-transitory computer readable storage medium of claim 9, wherein the indication is received from the wireless access point via a second cable modem.
  • 12. The non-transitory computer readable storage medium of claim 9, wherein the wireless command signal is adapted for transmission to the first cable modem via a secure communication channel between the wireless access point and the first cable modem.
  • 13. The non-transitory computer readable storage medium of claim 9, wherein the reboot command is adapted for transmission to the wireless access point via the internet.
  • 14. The non-transitory computer readable storage medium of claim 9, wherein the reboot command is executable by the wireless access point to further fail over the wireless access point to a second cable modem until the first cable modem resumes operation after rebooting.
  • 15. A system for rebooting a first cable modem, the system comprising: a processor;a memory; andone or more modules stored in the memory and executable by the processor to: receive an indication of a service failure of the first cable modem, the indication received from a wireless access point in communication with the first cable modem, the service failure detected following an absence of a response by the first cable modem to a request sent by the wireless access point; andgenerate a reboot command for transmission to the wireless access point, the reboot command being executable by the wireless access point to transmit a wireless command signal to the first cable modem, the wireless command signal being adapted to cause the first cable modem to reboot in response to wirelessly receiving the wireless command signal.
  • 16. The system of claim 15, wherein the indication is received from the wireless access point via a second cable modem.
  • 17. The system of claim 15, wherein the reboot command is executable by the wireless access point to further fail over the wireless access point to a second cable modem until the first cable modem resumes operation after rebooting.
  • 18. A method for rebooting a first cable modem by an access point, the method comprising: detecting a service failure of the first cable modem by the access point;generating, by the access point, an indication of the service failure of the first cable modem, the indication of the service failure being adapted for transmission to a remote device;in response to receiving, at the access point, a reboot command from the remote device,generating a wireless command signal for transmission to the first cable modem, the wireless command signal being adapted to cause the first cable modem to reboot,failing over, by the access point, to a second cable modem until the first cable modem reboots in response to wirelessly receiving the wireless command signal.
  • 19. The method of claim 18, wherein the indication and the reboot command are adapted for transmission through the second cable modem.
  • 20. The method of claim 18, wherein the remote device is a mobile device and the reboot command is a Wi-Fi compliant signal.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the priority benefit of U.S. Provisional Application Ser. No. 61/481,203, titled “Remote Cable Access Point Reset,” filed May 1, 2011, the disclosure of which is incorporated herein by reference.

US Referenced Citations (294)
Number Name Date Kind
4176356 Foster Nov 1979 A
4193077 Greenberg Mar 1980 A
4253193 Kennard Feb 1981 A
4305052 Baril Dec 1981 A
4513412 Cox Apr 1985 A
4814777 Monser Mar 1989 A
5097484 Akaiwa Mar 1992 A
5173711 Takeuchi Dec 1992 A
5203010 Felix Apr 1993 A
5220340 Shafai Jun 1993 A
5373548 McCarthy Dec 1994 A
5507035 Bantz Apr 1996 A
5559800 Mousseau Sep 1996 A
5754145 Evans May 1998 A
5767809 Chuang Jun 1998 A
5802312 Lazaridis Sep 1998 A
5964830 Durett Oct 1999 A
6034638 Thiel Mar 2000 A
6094177 Yamamoto Jul 2000 A
6266528 Farzaneh Jul 2001 B1
6292153 Aiello Sep 2001 B1
6307524 Britain Oct 2001 B1
6317599 Rappaport Nov 2001 B1
6326922 Hegendoerfer Dec 2001 B1
6337628 Campana Jan 2002 B2
6337668 Ito Jan 2002 B1
6339404 Johnson Jan 2002 B1
6345043 Hsu Feb 2002 B1
6356242 Ploussios Mar 2002 B1
6356243 Schneider Mar 2002 B1
6356905 Gershman Mar 2002 B1
6377227 Zhu Apr 2002 B1
6392610 Braun May 2002 B1
6404386 Proctor Jun 2002 B1
6407719 Ohira Jun 2002 B1
6442507 Skidmore Aug 2002 B1
6445688 Garces Sep 2002 B1
6493679 Rappaport Dec 2002 B1
6498589 Horii Dec 2002 B1
6499006 Rappaport Dec 2002 B1
6507321 Oberschmidt Jan 2003 B2
6625454 Rappaport Sep 2003 B1
6674459 Ben-Shachar Jan 2004 B2
6701522 Rubin Mar 2004 B1
6725281 Zintel Apr 2004 B1
6753814 Killen Jun 2004 B2
6762723 Nallo Jul 2004 B2
6772331 Hind et al. Aug 2004 B1
6779004 Zintel Aug 2004 B1
6807577 Gillespie Oct 2004 B1
6819287 Sullivan Nov 2004 B2
6876280 Nakano Apr 2005 B2
6888504 Chiang May 2005 B2
6888893 Li May 2005 B2
6892230 Gu May 2005 B1
6906678 Chen Jun 2005 B2
6910068 Zintel Jun 2005 B2
6924768 Wu Aug 2005 B2
6931429 Gouge Aug 2005 B2
6941143 Mathur Sep 2005 B2
6947727 Brynielsson Sep 2005 B1
6950019 Bellone Sep 2005 B2
6950523 Brickell Sep 2005 B1
6961028 Joy Nov 2005 B2
6973622 Rappaport Dec 2005 B1
6975834 Forster Dec 2005 B1
7034770 Yang Apr 2006 B2
7043277 Pfister May 2006 B1
7043633 Fink et al. May 2006 B1
7050809 Lim May 2006 B2
7064717 Kaluzni Jun 2006 B2
7085814 Ghandi Aug 2006 B1
7089307 Zintel Aug 2006 B2
7116707 Armistead Oct 2006 B1
7127234 Ishii Oct 2006 B2
7130895 Zintel Oct 2006 B2
7171475 Weisman Jan 2007 B2
7181620 Hur Feb 2007 B1
7197297 Myles Mar 2007 B2
7234063 Baugher Jun 2007 B1
7234156 French et al. Jun 2007 B2
7263076 Leibovitz et al. Aug 2007 B1
7292870 Heredia et al. Nov 2007 B2
7363354 Lahti Apr 2008 B2
7421578 Huang et al. Sep 2008 B1
7477894 Sinha Jan 2009 B1
7505434 Backes Mar 2009 B1
7562385 Thione et al. Jul 2009 B2
7565529 Beck Jul 2009 B2
7599380 Whitten Oct 2009 B2
7669232 Jou Feb 2010 B2
7715833 Sanchez May 2010 B2
7722502 Holkkola May 2010 B2
7788703 Jou Aug 2010 B2
7966497 Gantman et al. Jun 2011 B2
8005459 Balsillie Aug 2011 B2
8009644 Kuo Aug 2011 B2
8091120 Perrella et al. Jan 2012 B2
8108904 Chickering et al. Jan 2012 B1
8260278 Landsman et al. Sep 2012 B2
8272036 Jou Sep 2012 B2
8355912 Keesey et al. Jan 2013 B1
8605697 Kuo Dec 2013 B2
8607315 Jou Dec 2013 B2
8756668 Ranade et al. Jun 2014 B2
8923265 Kuo Dec 2014 B2
9071583 Yang Jun 2015 B2
9092610 Sheu Jul 2015 B2
9131378 Jou Sep 2015 B2
9226146 Ranade et al. Dec 2015 B2
20020009199 Ala-Laurila et al. Jan 2002 A1
20020022483 Thompson et al. Feb 2002 A1
20020031130 Tsuchiya Mar 2002 A1
20020047800 Proctor Apr 2002 A1
20020080767 Lee Jun 2002 A1
20020084942 Tsai Jul 2002 A1
20020105471 Kojima Aug 2002 A1
20020112058 Weisman Aug 2002 A1
20020158798 Chang Oct 2002 A1
20020169966 Nyman Nov 2002 A1
20020170064 Monroe Nov 2002 A1
20030026240 Eyuboglu Feb 2003 A1
20030030588 Kalis Feb 2003 A1
20030063591 Leung Apr 2003 A1
20030122714 Wannagot Jul 2003 A1
20030156558 Cromer et al. Aug 2003 A1
20030162533 Moles Aug 2003 A1
20030169330 Ben-Shachar Sep 2003 A1
20030184490 Raiman Oct 2003 A1
20030189514 Miyano Oct 2003 A1
20030189521 Yamamoto Oct 2003 A1
20030189523 Ojantakanen Oct 2003 A1
20030191935 Ferguson Oct 2003 A1
20030196084 Okereke Oct 2003 A1
20030202486 Anton et al. Oct 2003 A1
20030210207 Suh Nov 2003 A1
20030227414 Saliga Dec 2003 A1
20040014432 Boyle Jan 2004 A1
20040017310 Vargas-Hurlston Jan 2004 A1
20040017860 Liu Jan 2004 A1
20040027291 Zhang Feb 2004 A1
20040027304 Chiang Feb 2004 A1
20040030900 Clark Feb 2004 A1
20040032378 Volman Feb 2004 A1
20040036651 Toda Feb 2004 A1
20040036654 Hsieh Feb 2004 A1
20040041732 Aikawa Mar 2004 A1
20040048593 Sano Mar 2004 A1
20040058690 Ratzel Mar 2004 A1
20040061653 Webb Apr 2004 A1
20040070543 Masaki Apr 2004 A1
20040073786 O'Neill Apr 2004 A1
20040080455 Lee Apr 2004 A1
20040095278 Kanemoto May 2004 A1
20040097217 McClain May 2004 A1
20040114535 Hoffmann Jun 2004 A1
20040121749 Cui et al. Jun 2004 A1
20040125777 Doyle Jul 2004 A1
20040141617 Volpano Jul 2004 A1
20040153647 Rotholtz et al. Aug 2004 A1
20040190477 Olson Sep 2004 A1
20040203593 Whelan Oct 2004 A1
20040214570 Zhang Oct 2004 A1
20040214572 Thompson et al. Oct 2004 A1
20040260800 Gu Dec 2004 A1
20050022210 Zintel Jan 2005 A1
20050041739 Li Feb 2005 A1
20050042988 Hoek Feb 2005 A1
20050050352 Narayanaswami et al. Mar 2005 A1
20050074018 Zintel Apr 2005 A1
20050097503 Zintel May 2005 A1
20050100166 Smetters May 2005 A1
20050129222 Creamer et al. Jun 2005 A1
20050135480 Li Jun 2005 A1
20050138137 Encamacion Jun 2005 A1
20050138193 Encamacion Jun 2005 A1
20050152305 Ji et al. Jul 2005 A1
20050165953 Oba et al. Jul 2005 A1
20050180381 Retzer Aug 2005 A1
20050188193 Kuehnel Aug 2005 A1
20050220048 Lee et al. Oct 2005 A1
20050222933 Wesby Oct 2005 A1
20050228874 Edgett Oct 2005 A1
20050240665 Gu Oct 2005 A1
20050250472 Silvester Nov 2005 A1
20050261970 Vucina et al. Nov 2005 A1
20050267935 Ghandi Dec 2005 A1
20050268107 Harris Dec 2005 A1
20060007897 Ishii Jan 2006 A1
20060031922 Sakai Feb 2006 A1
20060039276 Jain Feb 2006 A1
20060046730 Briancon et al. Mar 2006 A1
20060052085 Gregrio Rodriguez et al. Mar 2006 A1
20060080415 Tu Apr 2006 A1
20060080741 Nair Apr 2006 A1
20060089123 Frank Apr 2006 A1
20060094371 Nguyen May 2006 A1
20060094400 Beachem et al. May 2006 A1
20060098607 Zeng May 2006 A1
20060123124 Weisman Jun 2006 A1
20060123125 Weisman Jun 2006 A1
20060123455 Pai Jun 2006 A1
20060133405 Fee Jun 2006 A1
20060165103 Trudeau et al. Jul 2006 A1
20060168159 Weisman Jul 2006 A1
20060184660 Rao Aug 2006 A1
20060184661 Weisman Aug 2006 A1
20060184693 Rao Aug 2006 A1
20060189298 Marcelli Aug 2006 A1
20060200851 Hung Sep 2006 A1
20060223527 Lee et al. Oct 2006 A1
20060224690 Falkenburg Oct 2006 A1
20060225107 Seetharaman Oct 2006 A1
20060227761 Scott Oct 2006 A1
20060239369 Lee Oct 2006 A1
20060251256 Asokan et al. Nov 2006 A1
20060291434 Gu Dec 2006 A1
20070025302 Zhang et al. Feb 2007 A1
20070027622 Cleron Feb 2007 A1
20070047449 Berger et al. Mar 2007 A1
20070055752 Wiegand et al. Mar 2007 A1
20070121525 Jenster May 2007 A1
20070124490 Kalavade et al. May 2007 A1
20070130294 Nishio Jun 2007 A1
20070130456 Kuo Jun 2007 A1
20070135167 Liu Jun 2007 A1
20070143832 Perrella et al. Jun 2007 A1
20070150736 Cukier Jun 2007 A1
20070165582 Batta Jul 2007 A1
20070189537 Zhang et al. Aug 2007 A1
20070199053 Sandhu et al. Aug 2007 A1
20070211659 Li et al. Sep 2007 A1
20070249324 Jou Oct 2007 A1
20070287450 Yang Dec 2007 A1
20070293951 Takahashi Dec 2007 A1
20070294528 Shoji et al. Dec 2007 A1
20080060064 Wynn et al. Mar 2008 A1
20080075280 Ye et al. Mar 2008 A1
20080085723 Tsao et al. Apr 2008 A1
20080089242 Whitten Apr 2008 A1
20080109657 Bajaj et al. May 2008 A1
20080119165 Mittal et al. May 2008 A1
20080141244 Kelley Jun 2008 A1
20080208617 Onyon et al. Aug 2008 A1
20080212535 Karaoguz et al. Sep 2008 A1
20080307515 Drokov et al. Dec 2008 A1
20090005005 Forstall et al. Jan 2009 A1
20090013210 McIntosh et al. Jan 2009 A1
20090059288 Mitsui Mar 2009 A1
20090092255 Jou Apr 2009 A1
20090103731 Sarikaya Apr 2009 A1
20090119190 Realini May 2009 A1
20090187970 Mower et al. Jul 2009 A1
20090193118 Cox et al. Jul 2009 A1
20090217048 Smith Aug 2009 A1
20100070542 Feinsmith Mar 2010 A1
20100299518 Viswanathan et al. Nov 2010 A1
20100332828 Goto Dec 2010 A1
20110007705 Buddhikot et al. Jan 2011 A1
20110035624 Miller Feb 2011 A1
20110040870 Wynn et al. Feb 2011 A1
20110047603 Gordon et al. Feb 2011 A1
20110055898 Jou Mar 2011 A1
20110126016 Sun May 2011 A1
20110145593 Auradkar et al. Jun 2011 A1
20110167478 Krishnaswamy et al. Jul 2011 A1
20110208866 Marmolejo-Meillon et al. Aug 2011 A1
20110246765 Schibuk Oct 2011 A1
20110264906 Pourzandi et al. Oct 2011 A1
20110271111 Frank et al. Nov 2011 A1
20110281609 Kuo Nov 2011 A1
20120030466 Yamaguchi Feb 2012 A1
20120054338 Ando Mar 2012 A1
20120078949 Allen et al. Mar 2012 A1
20120089845 Raleigh Apr 2012 A1
20120134291 Raleigh May 2012 A1
20120257536 Kholaif et al. Oct 2012 A1
20120284785 Salkintzis et al. Nov 2012 A1
20120317625 Jou Dec 2012 A1
20120322035 Julia et al. Dec 2012 A1
20130007853 Gupta et al. Jan 2013 A1
20130047218 Smith Feb 2013 A1
20130111217 Kopasz et al. May 2013 A1
20130173916 Sato Jul 2013 A1
20130182693 Sperling et al. Jul 2013 A1
20130223222 Kotecha et al. Aug 2013 A1
20130269008 Shtrom Oct 2013 A1
20140007209 Zucker Jan 2014 A1
20140066112 Kuo Mar 2014 A1
20140068724 Jou Mar 2014 A1
20140282951 Ranade Sep 2014 A1
20150133089 Kuo May 2015 A1
20150257009 Sheu Sep 2015 A1
20150296377 Sheu Oct 2015 A1
Foreign Referenced Citations (30)
Number Date Country
1708162 Dec 2005 CN
1316862 Oct 2011 CN
103441984 Dec 2013 CN
103858106 Jun 2014 CN
0 352 787 Jul 1989 EP
0 534 612 Mar 1993 EP
1 315 311 May 2003 EP
1 450 521 Aug 2004 EP
1 608 108 Dec 2005 EP
1 638 261 Mar 2006 EP
1 724 691 Nov 2006 EP
2 705 429 Mar 2014 EP
1 958 369 Apr 2015 EP
3038933 Jul 1989 JP
2008088633 Feb 1996 JP
2001057560 Feb 2002 JP
2005354249 Dec 2005 JP
2006060408 Mar 2006 JP
2014-522142 Aug 2014 JP
201146029 Dec 2011 TW
201351188 Dec 2013 TW
WO 0184323 Nov 2001 WO
WO 0225967 Mar 2002 WO
WO 03079484 Sep 2003 WO
WO 2007064822 Jun 2007 WO
WO 2007127120 Nov 2007 WO
WO 2007127162 Nov 2007 WO
WO 2012151224 Nov 2012 WO
WO 2013119750 Aug 2013 WO
WO 2013152027 Oct 2013 WO
Non-Patent Literature Citations (87)
Entry
US 9,015,816, 04/2015, Sheu (withdrawn)
U.S. Appl. No. 13/191,383, Office Action dated Jul. 22, 2013.
U.S. Appl. No. 13/590,997, Office Action dated Jul. 18, 2013.
Aboba, Bernard “Virtual Access Points,” IEEEP802.11 Wireless LANs, XX, XX, No. 802.11-03/154rl, May 22, 2003.
Areg Alimian et al., “Analysis of Roaming Techniques,” doc.:IEEE 802.11-04/0377r1, Submission, Mar. 2004.
Chang, Nicholas B. et al., “Optimal Channel Probing and Transmission Scheduling for Opportunistics Spectrum Access,” Sep. 2007.
Cisco Systems, “Cisco Aironet Access Point Software Configuration Guide: Configuring Filters and Quality of Service,” Aug. 2003.
Dell Inc., “How Much Broadcast and Multicast Traffic Should I Allow in My Network,” PowerConnect Application Note #5, Nov. 2003.
Dunkels, Adam et al., “Connecting Wireless Sensornets with TCP/IP Networks,” Proc. of the 2d Int'l Conf. on Wired Networks, Frankfurt, Feb. 2004.
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.
Dutta, Ashutosh et al., “MarconiNet Supporting Streaming Media Over Localized Wireless Multicast,” Proc. of the 2d Int'l Workshop on Mobile Commerce, 2002.
Festag, Andreas, “What is MOMBASA?” Telecommunication Networks Group (TKN), Technical University of Berlin, Mar. 7, 2002.
Golmie, Nada, “Coexistence in Wireless Networks: Challenges and System-Level Solutions in the Unlicensed Bands,” Cambridge University Press, 2006.
Hewlett Packard, “HP ProCurve Networking: Enterprise Wireless LAN Networking and Mobility Solutions,” 2003.
Hirayama, Koji et al., “Next-Generation Mobile-Access IP Network,” Hitachi Review vol. 49, No. 4, 2000.
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.
Information Society Technologies Ultrawaves, “System Concept / Architecture Design and Communication Stack Requirement Document,” Feb. 23, 2004.
Keidl et al., TES2003, LNCS v. 2819, pp. 104-118, Sep. 2003.
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.
Ken Tang, et al., “MAC Reliable Broadcast in Ad Hoc Networks,” Computer Science Department, University of California, Los Angeles, 2001 IEEE, pp. 1008-1013.
Mawa, Rakesh, “Power Control in 3G Systems,” Hughes Systique Corporation, Jun. 28, 2006.
Microsoft Corporation, “IEEE 802.11 Networks and Windows XP,” Windows Hardware Developer Central, Dec. 4, 2001.
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.
Steger, Christopher et al., “Performance of IEEE 802.11b Wireless LAN in an Emulated Mobile Channel,” 2003.
Toskala, Antti, “Enhancement of Broadcast and Introduction of Multicast Capabilities in RAN,” Nokia Networks, Palm Springs, California, Mar. 13-16, 2001.
Tsunekawa, Kouichi, “Diversity Antennas for Portable Telephones”, 39th IEEE Vehicular Technology Conference, pp. 50-56, vol. 1, Gateway to New Concepts in Vehicular Technology, May 1-3, 1989, San Francisco, CA.
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.
Wennstrom, Mattias et al., “Transmit Antenna Diversity in Ricean Fading MIMO Channels with Co-Channel Interference,” 2001.
Extended European Search Report for EP application No. 07755678.5 dated Dec. 29, 2011.
Extended European Search Report for EP application No. 06838713.3 dated Jul. 13, 2011.
PCT Application No. PCT/US2006/045893, International Search Report and Written Opinion dated Sep. 25, 2007.
PCT Application No. PCT/US2007/09836, International Search Report and Written Opinion dated Sep. 12, 2008.
PCT Application No. PCT/US2007/09503, International Search Report and Written Opinion dated Mar. 3, 2008.
PCT Application No. PCT/US2012/036028, International Search Report and Written Opinion dated Aug. 7, 2012.
Chinese Office Action for CN Application No. 200680045272.7 dated Jul. 12, 2011.
Chinese Office Action for CN Application No. 200680045272.7 dated Feb. 1, 2011.
Chinese Office Action for CN Application No. 200680045272.7 dated Jul. 15, 2010.
Chinese Office Action for CN Application No. 200780019074.8 dated Jun. 15, 2011.
Chinese Office Action for CN Application No. 200780019389.2 dated Sep. 12, 2012.
Chinese Office Action for CN Application No. 200780019389.2 dated Feb. 14, 2012.
Chinese Office Action for CN Application No. 200780019389.2 dated Apr. 8, 2011.
European First Examination Report for EP Application No. 068387133 dated Apr. 3, 2012.
European First Examination Report for EP Application No. 07755678.5 dated Oct. 23, 2012.
U.S. Appl. No. 11/607,619, Office Action dated Oct. 13, 2010.
U.S. Appl. No. 11/607,619, Final Office Action dated Dec. 4, 2009.
U.S. Appl. No. 11/607,619, Office Action dated Apr. 29, 2009.
U.S. Appl. No. 11/788,371, Final Office Action dated Jan. 21, 2010.
U.S. Appl. No. 11/788,371, Office Action dated Sep. 17, 2009.
U.S. Appl. No. 11/789,446, Final Office Action dated Oct. 13, 2010.
U.S. Appl. No. 11/789,446, Office Action dated May 24, 2010.
U.S. Appl. No. 11/789,446, Final Office Action dated Jun. 24, 2009.
U.S. Appl. No. 11/789,446, Office Action dated Sep. 3, 2008.
U.S. Appl. No. 12/339,688, Office Action dated Sep. 15, 2009.
U.S. Appl. No. 12/845,089, Final Office Action dated Feb. 14, 2012.
U.S. Appl. No. 12/845,089, Office Action dated Sep. 6, 2011.
Supplementary European Search Report for EP application No. 07755678.5 dated Jan. 17, 2012.
Chinese Office Action for CN Application No. 200680045272.7 dated Jul. 29, 2013.
European First Examination Report for EP Application No. 07755913.6 dated Jul. 4, 2013.
IEEE Trial-Use Recommended Practice for Multi-Vendor Access Point Interoperability Via an Inter-Access Point Protocol Across Distribution Systems Supporting IEEE 802.11 Operation; IEEE Std 802.11F-2003 ED, IEEE Standard, IEEE, Piscataway, NJ, USA, Jan. 1, 2003, pp. 1-67.
Yang, Song Li, Virtual AP for 802.11 Seamless Handoff draft-song-80211-seamless-handoff-00.txt.
Extended European Search Report for EP application No. 14163071.5 dated Jul. 4, 2014.
Extended European Search Report for EP application No. 12779857.7 dated Mar. 30, 2015.
U.S. Appl. No. 14/078,947, Office Action dated Sep. 24, 2014.
European Second Examination Report for EP Application No. 07755678.5 dated Feb. 3, 2014.
Bargh et al., “Fast Authentication Methods for Handovers between IEEE 802.11 Wireless LANs”, Proceedings of the ACM International Workshop on Wireless Mobile Applications and Services on WLAN Hotspots. Oct. 1, 2004.
Encrypted Preshared key; cisco corp. 14 pages, 2010 (Date of Download: Nov. 20, 2013).
Kassab et al., “Fast Pre-Authentication Based on Proactive Key Distribution for 802.11 Infrastructure Networks”, WMuNeP'05, Oct. 13, 2005, Montreal, Quebec, Canada, Copyright 2005 ACM.
PCT Application No. PCT/US2013/34997, International Search Report dated Jun. 17, 2013.
PCT Application No. PCT/US2013/34997, Written Opinion dated Jun. 17, 2013 (Date of Online Publication: Oct. 4, 2014).
Chinese Office Action for CN Application No. 200680045272.7 dated Oct. 27, 2011.
U.S. Appl. No. 14/078,947, Final Office Action dated Feb. 23, 2015.
U.S. Appl. No. 13/370,201, Office Action dated May 13, 2013.
U.S. Appl. No. 14/294,012, Office Action dated Mar. 23, 2015.
U.S. Appl. No. 13/439,844, Office Action dated Apr. 22, 2014.
U.S. Appl. No. 13/439,844, Final Office Action dated Oct. 28, 2013.
U.S. Appl. No. 13/439,844, Office Action dated Jun. 5, 2013.
EPO Communication under Rule 71(3) EPC Intention to Grant for related EP Application No. 12779857.7, dated Dec. 3, 2015 (7 sheets).
Notice of Allowance for co-pending U.S. Appl. No. 14/586,396, dated Dec. 4, 2015 (16 sheets).
SIPO Office Action for co-pending Chinese Application No. 201310291285.4, dated Jan. 4, 2016 (16 sheets).
Office Action for co-pending U.S. Appl. No. 14/692,485, dated Feb. 16, 2016 (22 sheets).
EPO Communication under Rule 71(3) EPC Intention to Grant for co-pending EP Application No. 07755678.5, dated Feb. 17, 2016 (7 sheets).
JPO Office Action for corresponding Japanese Application No. 2014-509367, dated Mar. 8, 2016 (5 sheets).
Office Action for co-pending U.S. Appl. No. 14/981,579, dated Jun. 17, 2016 (33 sheets).
Chinese Office Action for CN Application No. 201280021332.7 dated Dec. 11, 2015.
U.S. Appl. No. 14/751,833, Ming-Jye Sheu, Sharing Security Keys With Headless Devices, filed Jun. 26, 2015.
U.S. Appl. No. 14/981,579, Prashant Ranade, Dynamic PSK for Hotspots, filed Dec. 28, 2015.
TIPO Office Action for related Taiwanese Application No. 102112203, dated Aug. 29, 2016 (12 sheets).
Related Publications (1)
Number Date Country
20120278654 A1 Nov 2012 US
Provisional Applications (1)
Number Date Country
61481203 May 2011 US