This disclosure generally relates to the field of communication systems and, more particularly, to configuration of a new enrollee device in a home communication network.
Home communication networks may comprise one or more networking technologies (e.g., various combinations that may include wireless local area network (WLAN) technologies, powerline communication (PLC) technologies, multimedia over coaxial (MoCA), IEEE 1901, Ethernet, etc.). A home communication network may also be referred to as a hybrid communication network, home environment network, mixed communication network, or simply a “home network.” Typically, the communication mechanisms and protocol specifics (e.g., device and topology discovery protocols, bridging protocols, etc.) are unique to each networking technology.
Some devices that are expected to be used in the home network may be considered a “headless” device. Headless devices are devices which do not have a graphical user interface. Furthermore, headless devices may use one or more networking technology associated with a home network. Examples of headless devices might include sensors, light bulbs, cameras, actuators, appliances, game controllers, audio equipment or other devices that may be capable of communicating via the home network but which may not have a graphical user interface due to commercial or technical limitations. In addition to headless devices, some devices are hard to reach (e.g. light bulb, motion sensors, etc., such as devices that may be utilized on a ceiling). These devices may be considered “unreachable” devices due to their physical placement.
A new device introduced to a home network is referred to as a new enrollee device because it must be configured (e.g. via an enrollment process) with various network configurations and settings. However, initial network configuration of a headless or unreachable device is currently difficult due to the lack of a graphical user interface. In order to configure headless or unreachable devices, configuration of such a device may require an out of band channel. An administrator of home network devices may be non-technical or have difficulty with current process used to configure a headless or unreachable device to operate in the home network.
Disclosed are various embodiments of configuring a new enrollee device for a communication network. In one embodiment, an electronic device obtains, at a sensor, sensor information that is indicative of a device key associated with a new enrollee device to be configured for a communication network. The new enrollee device is a headless device that lacks a first user interface for configuring the new enrollee device for the communication network. The electronic device determines the device key based on the sensor information. The device key is provided to a network registrar to cause the network registrar to configure the new enrollee device for the communication network.
The present embodiments may be better understood, and numerous objects, features, and advantages made apparent to those skilled in the art by referencing the accompanying drawings, in which like reference numerals refer to substantially similar items throughout.
The description that follows includes exemplary systems, methods, techniques, instruction sequences, and computer program products that embody techniques of the present inventive subject matter. However, it is understood that the described embodiments may be practiced without these specific details. For instance, although examples refer to configuration of a particular headless device, such as a light bulb, for a home communication network comprising wireless local area network (WLAN) devices (e.g., IEEE 802.11), power line network devices (e.g., HomePlug AV), coax network devices (MoCA), and Ethernet devices, the present disclosure relates to a variety of new enrollee devices that may be configured for use in a communication network comprising other networking technologies. In other instances, well-known instruction instances, protocols, structures, and techniques have not been shown in detail in order not to obfuscate the description.
New enrollee devices (e.g., smart lighting systems, smart thermostats, etc.) are typically configured for use with a home communication network (e.g., a home WLAN, a powerline network, etc.) before the new enrollee devices and their corresponding services can be utilized. For example, some networking protocols (e.g., Bonjour, universal plug and play (UPnP), etc.) may typically require the new enrollee device to be connected to the local network (e.g., the home WLAN). A network name, password, configuration settings, or other information, may be needed by the new enrollee device to properly utilize one or more networking technologies associated with the home network. However, the new enrollee device (such as a headless device) may have little to no user input capability. Configuring and controlling the new enrollee device via an Internet-based configuration page or via a panel of buttons/dials on the new enrollee device can be difficult. This can make the process of configuring the new enrollee device time consuming, complicated, expensive, and frustrating to users. Existing techniques for new enrollee device configuration typically employ a network password method, a static personal identification number (PIN) method, or a push button method to initiate the Wi-Fi® Protected Setup (WPS) connection procedures and to connect the new enrollee device to an access point of the home network. However, the push-button may break, may be physically awkward, and implementing the push-button on the new enrollee devices can increase the cost and size of the new enrollee devices and may not be user-friendly. The push-button method may also not be feasible for unreachable devices due to their physical placement out of the reach of a user. Furthermore, communications exchanged after the push-button is activated may be susceptible to security and privacy issues (e.g., active eavesdroppers). The static PIN method may involve the user employing a computer or another communication device to input the PIN (e.g., because the access point and/or the new enrollee device may not have a user input panel). The user may also lose/forget the predetermined static PIN or may select an easily compromised PIN; thus the static PIN method may be neither easy to implement nor secure. The network password method may be unavailable for headless devices because there is no user interface available on the headless device for a user to enter the network password.
The present disclosure describes various methods and mechanisms to configure a new enrollee device, such as a headless device or a difficult to reach device. The process for configuring the new enrollment device for a communication network may be called an enrollment process. As a result of the enrollment process, the new enrollee device is added to the communication network. According to embodiments of the present disclosure, an electronic device may be used as an intermediary device and coordinate the exchange of a device password (which may also be referred to a PIN, device identifier, device key, etc.) associated with a new enrollee device to a network registrar to cause the network registrar to configure the new enrollee device for the home network. In some embodiments, an electronic device or another user-friendly electronic device (e.g., a tablet computer) can implement functionality for assisting the new enrollee device (e.g., the new enrollee device that is not currently part of network) by obtaining a device password from the new enrollee device and providing the device password to a network registrar, thereby causing the network registrar to add the new enrollee device to the home network with very little manual intervention from the user.
The electronic device 110 may be a portable electronic device such as a smartphone, mobile device, a tablet computer, a laptop computer, or another suitable electronic device configured to execute functionality described herein. The electronic device 110 acts as an intermediary device between the new enrollee device 140 and the network registrar 130 by obtaining (shown as arrow 150) a device password from the new enrollee device 140 and providing (shown as arrow 154) the device password to the network registrar 130. The network registrar 130 may initiate (shown as arrow 158) an enrollment process 126 in response to receiving the device password for the new enrollee device 140. Upon successfully completing the enrollment process 126 (i.e. the new enrollee device 140 is configured for use in the communication network 120), the network registrar 130 may provide a network feedback indicator 160 back to the electronic device 110 to indicate that the enrollment process 126 completed successfully.
Having disclosed the high level features of this embodiment, various details and aspects will now be described using an example implementation. The following descriptions of operations are non-limiting examples.
At stage A, the electronic device 110 may obtain the device password from the new enrollee device 140 using a variety of methods, such as scanning a visual tag, detecting an audio signal, detecting a light signal, detecting the device password via a near-field communication (NFC) tag, radio frequency identifier (RFID), or other ways in which the new enrollee device 140 may communicate the device password with the electronic device 110. It is noted that while Bluetooth radio signal or Wi-Fi Direct handshake may also be used by the electronic device to obtain the device password from the new enrollee device 140, such mechanisms may not be used in some implementations if they are prone to wireless signal eavesdropping. In a first example, the electronic device 110 is a personal mobile device and the new enrollee device 140 is a smart light bulb. The smart light bulb has a visual tag printed on it (or on the packaging, or insert in the packaging), such as a barcode, matrix code, two-dimensional code. A common example of a barcode that may be used for a new enrollee device may be a Quick Response (QR) Code®. The electronic device 110 may detect the QR Code (or similar visual tag) using a camera and corresponding software. The electronic device 110 may obtain the device password by decoding the QR Code. The device password may be a manufacturer-configured PIN or device key for the new enrollee device 140. For example, the device password may be a device access key (DAK) used for powerline communications, or may be a Wi-Fi® Simple Config (WSC) PIN. In addition to the device password, other information may also be encoded on the QR Code, such as a management Uniform Resource Allocator (URL), name and/or model of the new enrollee device, or other information relevant to the configuration, management, or utilization of the new enrollee device.
At stage B, once the electronic device 110 has obtained the device password for the new enrollee device 140, the electronic device 110 communicates the device password to the network registrar 130 (which may also be referred to as a server or network registrar device) to cause the network registrar 130 to configure the new enrollee device 140 for the communication network 120. The network registrar 130 may be configured to manage devices in the communication network 120. For example, the network registrar 130 may be a hybrid network device with multiple home networking technologies. In the example of the smart light bulb, the smart light bulb may require a connection via a powerline communication network technology of the hybrid home network. The electronic device 110 may utilize a WLAN network to communicate the device password (e.g. PLC DAK) to the network registrar 130 which is capable of using the device password on the powerline communication network of the home network. In some embodiments, the electronic device 110 is already part of the communication network 120 and can therefore provide the device password to the network registrar 130 in a secure manner (the communication channel provide integrity and confidentiality).
At stage C, the network registrar 130 uses the device password to initiate the enrollment process 126 to configure the new enrollee device 140. In some embodiments, the network registrar 130 may also be an access point or router of the communication network 120. In other embodiments, the network registrar 130 instructs another network node (such as a PLC/Router) to configure the new enrollee device 140. The enrollment process 126 in this example is initiated by the network registrar 130 in response to receiving the new enrollee device's device password from the electronic device 110. In one embodiment, the electronic device 110 is considered a trusted intermediary because it may already be associated with the communication network 120 and registered with the network registrar 130.
At stage D, the new enrollee device 140 is added to the communication network via the enrollment process 126. The enrollment process 126 may be one of several known processes or protocols that are used to provide the network configuration information for a home network. For example, the network registrar 130 may generate a network membership key for the new enrollee device 140 and transmit the network membership key encrypted using the device password so that the new enrollee device 140 can decrypt and receive the network membership key securely. Having the network membership key, the new enrollee device 140 may be enabled for communication via the home network. Other examples of the enrollment process 126 may include the use of a PLC DAK protocol and/or WSC PIN protocol with the new enrollee device 140.
At stage E, the network registrar 130 may provide feedback regarding enrollment process and/or the new enrollee device 140 information. The feedback may be provided via a network feedback indicator 160 (e.g. acknowledgement or confirmation message) back to the electronic device 110. The network feedback indicator 160 may, for example, confirm that the device password was received properly. The network feedback indicator 160 may also indicate whether or not the enrollment process 126 was successfully completed. In another example, the network feedback indicator 160 is provided back to the electronic device 110 upon successfully completing the enrollment process 126 with the new enrollee device 140. In this example, the user of the electronic device 110 is made aware that the configuration was properly completed. In example embodiments, the feedback may also include an internet protocol (IP) address or other network identifier associated with the configured new enrollee device 140, such that a management application on the electronic device 110 could provide further configuration and otherwise manage/control the operation of the new enrollee device 140. Alternatively, the IP address or other network identifier may be used to indicate to a user of the electronic device 110 that the new enrollee device 140 is activated on the communication network 120. For example, an indication may be presented via a user interface of the electronic device 110 to indicate whether the new enrollee device 140 was enrolled (added) to the communication network 120. It may be advantageous to receive this indicator if the new enrollee device 140 is a headless device because otherwise a user may be left to wonder or test through trial-and-error to determine whether the headless device has been properly added to the communication network 120.
At stage A, a device password may be embedded in a barcode, QR-code, smart tag, NFC, or other detectable encoding format. Thus, state A shows an implementation option where the device password is encoded in a tag 250 that is associated with the new enrollee device 140. The tag 250 in
At stage B, an enrollment process 226 may involve a network node 230 such as a router, access point, and/or a PLC controller. Thus, stage B shows another implementation option where the enrollment process 226 involves the network node 230 that is separate from the network registrar 130. For example, the network registrar 130 may have a link 225 (e.g., a logical connection) to the network node 230 using one type of home networking technology (such as WLAN) and the network node 230 may utilize a different type of home networking technology (such as PLC) for the enrollment process 226.
As shown in
Finally, at stage C of
At stage B, the electronic device 110 communicates (shown as arrow 350) the new device password to the new enrollee device 140 using a variety of techniques. For example, the new device password may be communicating using optical, audio, or radio frequency signals that are detectable by the new enrollee device 140. In one implementation example, the new enrollee device 140 is a device that has a photo sensor. It may be cost effective to utilize photo sensors rather than radio frequency sensors for low cost smart devices, such as smart light bulbs. The new enrollee device 140 may recover the new device password based on decoding data-encoded variations in amplitude, frequency, or duration (or any combinations thereof) of optical, audio, or radio frequency signals.
At stage C, the electronic device 110 communicates the new device password to the network registrar 130 to cause the network registrar 130 to configure the new enrollee device 140 for the communication network 120. Thus, at stage C the electronic device 110 may invoke an enrollment process 126 on behalf of the new enrollee device 140. The remaining stages D and E function similarly to those described in
At 842, the network registrar 830 may provide further device information to the electronic device 810, as described previously in relation to
It should be understood that
Embodiments may take the form of an entirely hardware embodiment, a software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, embodiments of the inventive subject matter may take the form of a computer program product embodied in any tangible medium of expression having computer usable program code embodied in the medium. The described embodiments may be provided as a computer program product, or software, that may include a machine-readable medium having stored thereon instructions, which may be used to program a computer system (or other electronic device(s)) to perform a process according to embodiments, whether presently described or not, since every conceivable variation is not enumerated herein. A machine-readable medium includes any mechanism for storing or transmitting information in a form (e.g., software, processing application) readable by a machine (e.g., a computer). A machine-readable medium may be a machine-readable storage medium, or a machine-readable signal medium. A machine-readable storage medium may include, for example, but is not limited to, magnetic storage medium (e.g., floppy diskette); optical storage medium (e.g., CD-ROM); magneto-optical storage medium; read only memory (ROM); random access memory (RAM); erasable programmable memory (e.g., erasable programmable read only memory (EPROM) and electrically erasable programmable read only memory (EEPROM)); flash memory; or other types of tangible medium suitable for storing electronic instructions. A machine-readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, an electrical, optical, acoustical, or other form of propagated signal (e.g., carrier waves, infrared signals, digital signals, etc.). Program code embodied on a machine-readable signal medium may be transmitted using any suitable medium, including, but not limited to, wireline, wireless, optical fiber cable, RF, or other communications medium.
Computer program code for carrying out operations of the embodiments may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on a user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN), a personal area network (PAN), or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider)
The electronic device 900 also includes a sensor interface 920. The sensor interface 920 may be capable of detecting optical, audio, or radio frequency signals from an electronic device. For example, the sensor interface 920 may allow the electronic device 900 to receive a generated device password from the electronic device and utilize the generated device password to perform an enrollment process via the network interfaces 904.
The electronic device 900 also includes an actuator interface 930. The actuator interface 930 may be capable of emitting optical, audio, or radio frequency signals from an electronic device. For example, the actuator interface 930 may allow the electronic device 900 to send a static or dynamic device password to the electronic device and utilize this device password to perform an enrollment process via the network interfaces 904.
Any one of these functionalities may be partially (or entirely) implemented in hardware and/or on the processor unit 902. For example, the functionality may be implemented with an application specific integrated circuit, in logic implemented in the processor unit 902, in a co-processor on a peripheral device or card, etc. Further, realizations may include fewer or additional components not illustrated in
While the embodiments are described with reference to various implementations and exploitations, it will be understood that these embodiments are illustrative and that the scope of the inventive subject matter is not limited to them. In general, techniques for configuring a new enrollee device for use in a hybrid communication networks as described herein may be implemented with facilities consistent with any hardware system or hardware systems. Many variations, modifications, additions, and improvements are possible. For example, although described as separate devices in the foregoing example embodiments, in some embodiments the electronic device and the network registrar may be parts of a common system or apparatus. Alternatively, the electronic device may be a separate apparatus from the network registrar as described in the foregoing example embodiments.
Plural instances may be provided for components, operations, or structures described herein as a single instance. Finally, boundaries between various components, operations, and data stores are somewhat arbitrary, and particular operations are illustrated in the context of specific illustrative configurations. Other allocations of functionality are envisioned and may fall within the scope of the inventive subject matter. In general, structures and functionality presented as separate components in the exemplary configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements may fall within the scope of the inventive subject matter.
This application is a continuation of and claims priority benefit of U.S. application Ser. No. 13/659,689 filed Oct. 24, 2012, which claims priority to U.S. Provisional Application No. 61/691,235 filed Aug. 20, 2012, the entire contents of which are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
7043230 | Geddes et al. | May 2006 | B1 |
7319853 | Luebke et al. | Jan 2008 | B2 |
7499548 | Meandzija et al. | Mar 2009 | B2 |
7616594 | Roberts et al. | Nov 2009 | B2 |
7908643 | Huotari et al. | Mar 2011 | B2 |
8001584 | Lortz et al. | Aug 2011 | B2 |
8224246 | Suumaki et al. | Jul 2012 | B2 |
8234492 | Kim et al. | Jul 2012 | B2 |
8429403 | Moret et al. | Apr 2013 | B2 |
8806567 | Venable, Sr. | Aug 2014 | B1 |
9357385 | Benoit et al. | May 2016 | B2 |
20030126243 | Kudo et al. | Jul 2003 | A1 |
20040098581 | Balfanz et al. | May 2004 | A1 |
20040107366 | Balfanz et al. | Jun 2004 | A1 |
20050010680 | Zick et al. | Jan 2005 | A1 |
20050076216 | Nyberg | Apr 2005 | A1 |
20050159823 | Hayes et al. | Jul 2005 | A1 |
20060015937 | Illowsky et al. | Jan 2006 | A1 |
20060053276 | Lortz et al. | Mar 2006 | A1 |
20060062391 | Lee et al. | Mar 2006 | A1 |
20060236105 | Brok et al. | Oct 2006 | A1 |
20060239208 | Roberts et al. | Oct 2006 | A1 |
20070079362 | Lortz et al. | Apr 2007 | A1 |
20070101136 | Lai et al. | May 2007 | A1 |
20070113269 | Zhang | May 2007 | A1 |
20070287450 | Yang et al. | Dec 2007 | A1 |
20080037444 | Chhabra | Feb 2008 | A1 |
20080189398 | Solyanik | Aug 2008 | A1 |
20080203148 | Young | Aug 2008 | A1 |
20080271131 | Moore | Oct 2008 | A1 |
20090102655 | Yi et al. | Apr 2009 | A1 |
20090224906 | Balgard et al. | Sep 2009 | A1 |
20090300746 | Ahn | Dec 2009 | A1 |
20100260069 | Sakamoto et al. | Oct 2010 | A1 |
20110044208 | Yun et al. | Feb 2011 | A1 |
20110090896 | Bradley | Apr 2011 | A1 |
20110191842 | Lindholm et al. | Aug 2011 | A1 |
20110197267 | Gravel et al. | Aug 2011 | A1 |
20110219427 | Hito et al. | Sep 2011 | A1 |
20110271334 | Yang et al. | Nov 2011 | A1 |
20110275316 | Suumäki et al. | Nov 2011 | A1 |
20110277020 | Morita et al. | Nov 2011 | A1 |
20120079123 | Brown et al. | Mar 2012 | A1 |
20120099566 | Laine | Apr 2012 | A1 |
20120100803 | Suumaki et al. | Apr 2012 | A1 |
20120128157 | Braun | May 2012 | A1 |
20120148043 | Tofighbakhsh | Jun 2012 | A1 |
20120167175 | Choi | Jun 2012 | A1 |
20120252405 | Lortz et al. | Oct 2012 | A1 |
20120262281 | Edwards et al. | Oct 2012 | A1 |
20120270505 | Prakash et al. | Oct 2012 | A1 |
20120284785 | Salkintzis et al. | Nov 2012 | A1 |
20120311165 | Renschler et al. | Dec 2012 | A1 |
20120324553 | Bernardo et al. | Dec 2012 | A1 |
20120329429 | Jabara et al. | Dec 2012 | A1 |
20130024685 | Kolavennu et al. | Jan 2013 | A1 |
20130029597 | Liu et al. | Jan 2013 | A1 |
20130052946 | Chatterjee et al. | Feb 2013 | A1 |
20130058274 | Scherzer et al. | Mar 2013 | A1 |
20130068837 | Dollard | Mar 2013 | A1 |
20130104202 | Yin et al. | Apr 2013 | A1 |
20130111208 | Sabin et al. | May 2013 | A1 |
20130139233 | Maity | May 2013 | A1 |
20130173915 | Haulund | Jul 2013 | A1 |
20130185210 | Dodson et al. | Jul 2013 | A1 |
20130185559 | Morel et al. | Jul 2013 | A1 |
20130196647 | Raleigh et al. | Aug 2013 | A1 |
20130198816 | Bohli et al. | Aug 2013 | A1 |
20130221083 | Doss et al. | Aug 2013 | A1 |
20130221084 | Doss et al. | Aug 2013 | A1 |
20130223279 | Tinnakornsrisuphap et al. | Aug 2013 | A1 |
20130227656 | Holtmanns et al. | Aug 2013 | A1 |
20130239104 | Savant et al. | Sep 2013 | A1 |
20130262687 | Avery et al. | Oct 2013 | A1 |
20130262873 | Read et al. | Oct 2013 | A1 |
20130276079 | Foulds et al. | Oct 2013 | A1 |
20130305329 | Zhang | Nov 2013 | A1 |
20130309971 | Kiukkonen et al. | Nov 2013 | A1 |
20130318343 | Bjarnason et al. | Nov 2013 | A1 |
20140007200 | Zisimopoulos et al. | Jan 2014 | A1 |
20140028817 | Brockway, III et al. | Jan 2014 | A1 |
20140028818 | Brockway, III et al. | Jan 2014 | A1 |
20140053281 | Benoit et al. | Feb 2014 | A1 |
20140068719 | Kiukkonen et al. | Mar 2014 | A1 |
20140169567 | Wendling | Jun 2014 | A1 |
20140226819 | Dittrich | Aug 2014 | A1 |
20140245410 | Frelechoux | Aug 2014 | A1 |
20140281478 | Huang et al. | Sep 2014 | A1 |
20140282960 | Tinnakornsrisuphap et al. | Sep 2014 | A1 |
20150089216 | Benoit et al. | Mar 2015 | A1 |
20150229475 | Benoit et al. | Aug 2015 | A1 |
20150244708 | Ballard | Aug 2015 | A1 |
20150312089 | Yang et al. | Oct 2015 | A1 |
Number | Date | Country |
---|---|---|
2096505 | Sep 2009 | EP |
2009039548 | Apr 2009 | WO |
2009063734 | Jun 2009 | WO |
2010028681 | Mar 2010 | WO |
2011141618 | Nov 2011 | WO |
2013126731 | Aug 2013 | WO |
2014031542 | Feb 2014 | WO |
2014151892 | Sep 2014 | WO |
2015120373 | Aug 2015 | WO |
Entry |
---|
“U.S. Appl. No. 13/837,703 Office Action”, Sep. 8, 2016, 32 pages. |
“Wi-Fi Protected Setup Specification Version 1.0h”, XP055031152, Internet Retrieved from the Internet: URL: http://gpl.back2roots.org/source/puma5/netgear/CG3200-1TDNDS—GPL/ap/apps/wpa2/original/Wi-Fi Protected Setup Specification 1.0h.pdf [retrieved on Jun. 26, 2012] Section 4 and subsections, Dec. 31, 2006, pp. 1-110. |
“PCT Application No. PCT/2014/026625 International Search Report and Written Opinion”, Jun. 26, 2014, 9 pages. |
“PCT Application No. PCT/US2013/055600 International Preliminary Report on Patentability”, Dec. 3, 2014, 9 pages. |
“PCT Application No. PCT/US2013/055600 Written Opinion of the IPEA”, Aug. 25, 2014, 6 pages. |
“PCT Application No. PCT/US2013/055600, International Search Report and Written Opinion”, Dec. 20, 2013, 11 pages. |
“PCT Application No. PCT/US2014/026625 International Preliminary Report on Patentability”, Aug. 13, 2015, 16 pages. |
“PCT Application No. PCT/US2014/026625 Written Opinion”, Jul. 9, 2015, 5 pages. |
“PCT Application No. PCT/US2014/026625Written Opinion”, Feb. 19, 2015, 5 pages. |
“PCT Application No. PCT/US2015/014992 International Search Report”, Jun. 26, 2015, 13 pages. |
“PCT Application No. PCT/US2015/014992 Written Opinion”, Jan. 29, 2016, 6 pages. |
“U.S. Appl. No. 13/659,689 Office Action”, Dec. 16, 2013, 29 pages. |
“U.S. Appl. No. 13/659,689 Final Office Action”, May 5, 2015, 25 pages. |
“U.S. Appl. No. 13/659,689 Final Office Action”, Jul. 21, 2014, 33 pages. |
“U.S. Appl. No. 13/659,689 Office Action”, Jan. 22, 2015, 25 pages. |
“U.S. Appl. No. 13/659,689 Office Action”, Sep. 29, 2015, 21 pages. |
“U.S. Appl. No. 13/837,703 Final Office Action”, Jul. 6, 2015, 35 pages. |
“U.S. Appl. No. 13/837,703 Final Office Action”, Nov. 7, 2014, 36 pages. |
“U.S. Appl. No. 13/837,703 Office Action”, Jan. 20, 2016, 29 pages. |
“U.S. Appl. No. 13/837,703 Office Action”, Feb. 6, 2015, 30 pages. |
“U.S. Appl. No. 13/837,703 Office Action”, Jul. 15, 2014, 35 Pages. |
“Wi-Fi Certified for Wi-Fi Protected Setup: Easing the User Experience for Home and Small Office Wi-Fi Networks”, 2009, 14 Pages. |
“Wi-Fi Certified™ for Wi-Fi Protected Setup: Easing the User Experience for Home and Small Office Wi-Fi® Networks”, Internet Citation, 2007, pp. 1-16, XP002567243, Retrieved from the Internet: URL:http://www.wi-fi.org/wp/witi-protected-setup., 2007, 16 pages. |
“Wi-Fi Simple Configuration Technical Specification”, Jan. 30, 2012, 155 pages. |
Zhang, ““Wi-Fi Direct based Smart Set-up (WDSS) in Lighting Systems””, M.Sc. Thesis Delft University of Technology, XP055092589 May 15, 2012, 76 pages. |
“U.S. Appl. No. 13/837,703 Final Office Action”, May 12, 2016, 33 pages. |
Co-Pending U.S. Appl. No. US 14/616,551, filed Feb. 6, 2015, 72 pages. |
Co-Pending U.S. Appl. No. US 61/691,235, filed Aug. 20, 2012, 36 pages. |
Co-Pending U.S. Appl. No. US 13/659,689, filed Oct. 24, 2012, 37 pages. |
Number | Date | Country | |
---|---|---|---|
20160242137 A1 | Aug 2016 | US |
Number | Date | Country | |
---|---|---|---|
61691235 | Aug 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13659689 | Oct 2012 | US |
Child | 15139797 | US |