This disclosure relates in general to the field of computer networks and, more particularly, to simplifying the setup and configuration of a secure network.
Computing devices and computer networking have become an integral part of daily life in today's society. Personal and business usage of computing devices, such as laptops, personal computers, smartphones (i.e., cell phones offering advanced computing capabilities), personal digital assistants (PDAs), and the like, have exploded in recent years. In addition, other electronic devices such as printers, gaming devices, smart appliances, etc. have also surged in popularity. For example, a home may include one or more personal computers, a printing device, a gaming device shared by family members, and one or more smartphones owned by individual family members. Small businesses may provide personal computers and smartphones or PDAs for employees, in addition to one or more printers shared by the employees.
Private local area networks (LANs) may be used to enhance the usefulness and potential of computing devices and other electronic devices in homes and small businesses. In a LAN, devices may be linked together through a networking device, such as a router. The router may be connected to other private and public networks, such as the Internet. In such a configuration, the router facilitates communication by routing packets of data between the devices within the LAN and also to and from other devices in private and public networks outside the LAN. Thus, home users and small businesses may use LANs to enable their computing devices and other electronic devices to communicate both within the private network and outside the private network. To setup and secure a LAN with a networking device such as a router, knowledge of router configuration is typically required. This can be daunting for most individuals who have little or no understanding of the technical aspects of computers or computer networks. Thus, a simplified approach for configuring secure networks would be useful.
To provide a more complete understanding of the present disclosure and features and advantages thereof, reference is made to the following description, taken in conjunction with the accompanying figures, wherein like reference numerals represent like parts, in which:
Overview
A method in one example implementation includes discovering a networking device within a wireless connectivity range from a first computing device. The networking device may be configured for wireless connectivity by sending new network configuration settings to the networking device to be stored in a memory element. The method also includes configuring the first computing device to initiate a wireless connection to the networking device, such that the wireless connection is created without requiring the user to provide any configuration settings associated with the wireless connection. In more specific embodiments, the method includes determining whether the networking device is unconfigured and if so, then generating the new network configuration settings. In other more specific embodiments, the new network configuration settings include a new network identifier and a new network password. In further specific embodiments, the method includes determining whether the networking device has made an operative connection to a wide area network, so that packets of data can be exchanged between the networking device and the wide area network.
In example embodiments, a system and method for simplifying secure network setup may be implemented in network 100 by providing setup key 140 and router 130 to simplify interconnecting wireless and/or hardwired computers and other electronic devices through router 130 such that packets of data can be securely exchanged by the networked devices. During the initial setup and configuration of network 100, setup key 140 may provide executable instructions to a computer, such as wireless computer 120b, for automatically configuring router 130 to securely communicate wirelessly with computer 120b, without the need for configuration settings or other substantive information from a user. During the initial setup, communication between router 130 and another network, such as Internet 160, may also be established. Once the initial setup and configuration of router 130 and wireless computer 120b has been completed, setup key 140 may be used to store configuration settings of router 130 to enable the secure connection of additional computers to router 130 by providing setup key 140 to the additional computers. In addition, an administrative tool application may be installed on computer 120b to provide a user with the ability to configure additional devices to be added to network 100 and to configure administrative settings for network 100, such as parental controls, guest access, and/or router settings.
For purposes of illustrating the techniques of such a system, it is important to understand the activities occurring within a network environment having a variety of networked devices such as computers and other electronic devices interconnected to each other and to other networks by a common networking device such as a router. The following foundational information may be viewed as a basis from which the present disclosure may be properly explained. Such information is offered earnestly for purposes of explanation only and, accordingly, should not be construed in any way to limit the broad scope of the present disclosure and its potential applications.
Although private networks utilizing wireless connections are highly desirable, the setup and configuration of such networks can be a difficult and cumbersome task for most users. Wireless networks are desirable because computers and other electronic devices can be easily moved and positioned throughout a home or small business. Incorporating wireless communication also helps minimize aesthetically unpleasant cable clutter. Wireless communication, however, can be more susceptible to security breaches. Therefore, such networks should be carefully configured with appropriate security settings.
Most users have limited knowledge of the technical aspects of computer networking, and consequently, have difficulty configuring secure wireless networks. A typical private network may include one or more computing devices, a common networking device such as a router, and an Internet connection. Depending upon the particular devices and existing network configuration, configuring a wireless router may require the user to input one or more of the following identifiers and passwords: web address of the router (e.g., 192.168.0.1, etc.), an administrative username and password, a network name or service set identifier (SSID) (i.e., a name that identifies a wireless LAN and may have up to 32 characters), a network password (i.e., security key or passphrase), and a media access control (MAC) address (i.e., a unique identifier assigned to a network adapter or network interface card, often referred to as a physical address). In addition, routers are often initially configured with open encryption so the first time the user powers up the router, it becomes an open access point with no encryption and with a published SSID, allowing anyone with an Internet connection immediate access to any devices connected behind the router. Therefore, properly securing the router during the setup configuration is essential and may require the user to select an encryption protocol such as, for example, Wired Equivalent Privacy (WEP) encryption or Wi-Fi Protected Access (WPA and WPA2) encryption.
Although various tools are available to help configure wireless networks, even most guided device setup programs or wizards ask the user numerous questions and require configuration settings and other substantive information to be provided by the user to properly configure the router. Most users have little understanding of the technical distinctions between identifiers, passwords, usernames, and addresses. For example, users may easily confuse an administrative username and password with an SSID and a network password, thereby complicating the setup process and creating frustration and aggravation on the part of the user. Often, the only solution is for the user to involve a third party with technical knowledge, such as a technical support group of a company that manufactured or sold the router. For small businesses, such a scenario could waste precious resources and valuable time.
Even when a user succeeds in setting up a network with a router and a computer, configuration problems often arise again when the user attempts to add another computer or other electronic device to the network. Adding a device to the network may require the user to again provide configuration settings and other substantive information, such as SSID, network password, encryption information, administrative username, administrative password, and the like. Unless the user recorded the configuration settings and other information during the initial network setup procedure, the same issues that may have occurred during the initial network setup may reoccur during any subsequent attempts to add other devices to the network.
A system for simplifying secure network setup, as outlined in
Turning to the infrastructure of
In
Network 100 may also be connected, through router 130, to another private network, a public network, such as Internet 160, or a combination of public and private networks. In the example embodiment shown in
Setup key 140 may provide a network application with a setup component and initial configuration settings to a computer such as, for example, wireless computer 120b, to initiate the secure setup and configuration of router 130 and computer 120b and the wireless connection therebetween. In one embodiment, setup key 140 may be a transportable computer readable medium such as a universal serial bus (USB) flash memory, a compact disc (CD), or the like. After router 130 has been initially configured and is connected to a computer, such as computer 120b, the configuration settings may be stored on setup key 140, if available, or on another computer readable medium, which may then be used to configure additional computers to access router 130. Also, after router 130 and computer 120b have been successfully configured and wirelessly connected, an administrative tool component, which may be part of the network application on setup key 140, may be installed on computer 120b for providing a user with administrative options for network 100. For example, the administrative tool component may offer the user the option to add additional computers or other electronic devices to network 100, configure parental controls on router 130, setup a guest access network through router 130, or manually modify configuration settings of router 130.
It should be understood that while an example network 100 has been shown and described herein, the system and method of the present disclosure may be implemented in any network environment capable of supporting the architecture. Accordingly, the description with reference to network 100 should be not be construed to imply architectural limitations, but rather, should be construed as illustrative.
Turning to
Not shown in
Other electronic devices added to network 100 may have one or more components as described with reference to computer 200 of
Referring to
Not shown in
Turning to
As shown in one embodiment in
In accordance with embodiments in the disclosure, network application 420 and configuration settings file 410 may guide a user to securely setup and configure a local area network (LAN) having a common networking device, such as a router, and a first computer with either a wireless or hardwired connection. In one embodiment, this setup and configuration may be accomplished without requiring any router configuration settings from the user, such as SSID, network password, encryption type, administrative username, administrative password, etc. Setup component 430 discovers an unconfigured router, reconfigures wireless settings on the router, configures the wireless settings on the computer, connects to the router, establishes a wide area network (WAN) connection, updates computer readable medium 400 with new configuration settings, and installs administrative tool component 440 on the computer after the setup and configuration has been successful. Once the initial configuration of the router has been completed, configuration settings file 410 may be updated to indicate that an initial setup and configuration of the router and first computer has been completed. In such an embodiment, connect computer component 450 may then be executed to configure additional computers to communicate with the router by either a wireless or hardwire connection using the updated configuration settings stored in configuration settings file 410 of computer readable medium 400.
In one alternative embodiment, the computer readable medium may be configured as a read-only medium such as, for example, a read-only compact disc (CD). In this embodiment, the computer readable medium may be manufactured such that configuration settings file includes new configuration settings such as a new network password, a new network identifier, and a new administrative password. These settings could be serialized or otherwise uniquely created for each computer readable medium. The new configuration settings may be used during the setup process to configure the router with the new configuration settings, and to set the wireless profile on the computer such that the computer can wirelessly connect to the router. Thus, in this embodiment, the computer readable medium may be read-only as it would not need to be updated with other new configuration settings.
When connecting a new computer to the router in this alternative embodiment, a determination may first need to be made as to whether the router has been previously configured with another computer. This may be accomplished, for example, by using the new configuration settings to attempt to access the router. If the router is found and a connection is established, then the software may assume the router has been previously configured and, therefore, will only need to perform a process such as process 2400 shown in
Turning now to
Once computer readable medium 400 has been inserted or otherwise connected to the computer, network application 420 may be launched in step 540. In certain embodiments, network application 420 may be automatically launched, such as, for example, using autorun software technology in Microsoft Windows XP operating system. In other embodiments, the user may be prompted in a dialog box with options for network application 420, and therefore, the user may have to select an option to run or launch network application 420. In one embodiment, if the mode element of configuration settings file is “Connect” for a 1st computer, then network application 420 knows to begin setup component 430. In step 550, setup component 430 may search for available network adapters on the computer. This search may be accomplished using operating system application programming interfaces (APIs). In step 555 a determination is made as to whether a wireless network adapter has been found. If a wireless network adapter has been found, then in step 560 setup component 430 configures a wireless network. However, if a wireless adapter is not found in step 555, then setup component 430 may configure a wired network in step 570. Thus, in one embodiment, setup component 430 defaults to configuring a wireless connection even if the computer includes both wired and wireless adapters. In addition, although not specifically shown in
In step 580 of
As shown in step 620 of
In step 645 of
If the determination in step 655, however, indicates that the computer has successfully connected wirelessly to the router, then flow passes to
After the connection has been successfully made to the unconfigured router, and any possible wireless and wired conflicts have been resolved, flow passes to step 681 where wireless settings are reconfigured on the router. The process 600 may gain administrative access to the router, using a known default password, in order to change the router configuration settings. In one embodiment, APIs may be used to perform the changes to the router settings. The SSID of the router, which is initially set to the predetermined format (e.g., “CISCOXXXXX”) as previously described herein, may be changed to a new SSID, which may be automatically generated using a random SSID generation algorithm. In one example embodiment, the new SSID could be a human readable random string including an adjective and a noun such as, for example, “ShortWillow.” In addition, the router may not be provided with open encryption, but rather, may be provided in a setup mode that includes enabled encryption by default, such as WPA and WPA2. A new network password may be generated using a password generation algorithm. In addition, a new administrative password may be generated using the password generation algorithm. The SSID and passwords may then be changed to the new SSID and passwords in the router. The combination of enabled encryption, a unique SSID generated by the setup component, and network and administrative passwords generated by the setup component provides a fully encrypted, fully secure, and fully locked down router, without requiring any configuration settings to be provided by the user during the setup process.
After the router settings have been reconfigured, a new wireless connection to the router is made using the new router settings. In step 684, the operating system of the computer scans for the new SSID. If the new SSID is not found in step 686, then a time out procedure is used in steps 688 and 690. In step 688, a determination is made as to whether polling for the new SSID has reached a maximum time limit, and if it has not, flow loops back to step 684 to continue polling to detect the new SSID. However, if a maximum time limit has been reached in step 688, then a display screen offering assistance to the user may be displayed in step 690. Referring back to step 686, however, if the new SSID is found, then the wireless profile in the computer is updated in step 691. The updated wireless profile may include, among other things, the new SSID, the new network password, and the encryption security type. After the wireless profile has been updated, the operating system attempts to wirelessly reconnect to the router through the wireless network adapter in step 692. In step 694, tests are again performed to determine whether a wireless connection has been made between the computer and the router, as previously described herein. If the determination in step 694 indicates that the computer is not wirelessly connected to the configured router with the new SSID, then a time out procedure is used in steps 696 and 698. In step 696, a determination is made as to whether attempts to wirelessly connect have reached a maximum time limit, and if not, flow loops back to step 692 to continue attempting to wirelessly connect to the configured router. However, if a maximum time limit has been reached in step 696, then a help screen offering assistance to the user may be displayed in step 698. With reference again to step 694, if the wireless connection has been successfully made to the router using the new SSID, then the wireless network configuration process 600 ends.
Turning to
As shown in step 950 in
If the router is determined to not have Internet connection at step 1104, because the settings are not valid or the URI has not been successfully contacted (e.g., HTTP Head or Get Request receives a response status code indicating an error or receives no response at all), then several checks may be performed to attempt to resolve the Internet connection problem. First, in step 1140 a call may be made to the router using any suitable protocol to get the WAN status. In one embodiment, the status call may be performed using HNAP protocol, which is described in detail in U.S. Pending patent application Ser. No. 11/457,783, filed Jul. 14, 2006, naming Hopmann et al. as inventors, and published on Jun. 7, 2007 as U.S. Publication No. 2007/0130286 A1, which is herein incorporated by reference in its entirety. It will be apparent, however, that any other suitable protocol may be used to obtain WAN status information. At step 1142, the WAN status is checked to determine whether the router indicates it is connected to something. If the router does not indicate any upstream connection, then a time out procedure is used in steps 1144-1148. In step 1144 a determination is made as to whether it is the first time an upstream cable link was not found, and if it is, then a wait time is activated in step 1146. After the wait time has completed, flow loops back to step 1140 to make HNAP protocol calls to get WAN status. However, if it is not the first time an upstream cable line was not found in step 1144, then a display screen offering assistance to the user may be displayed in step 1148. Referring again to step 1142, if the router indicates an upstream connection, then a second test is performed at step 1150 to determine Internet connectivity. If there is still no connection, then a repair attempt may be made to repair the Internet connection. Once the repair attempt is complete, another test is performed to determine if the repair was successful to restore Internet connectivity.
At step 1152, if the status calls still indicate there is no Internet connectivity, then the status information received from the HNAP protocol call is evaluated at step 1154 to determine what type of Internet connection the router should have. Process 1100 may attempt to resolve at least three possible errors: Double Network Address Translation (double NAT), Point-to-Point Protocol over Ethernet (PPPoE) connection type, and Media Access Control (MAC) address problem. In the case of a MAC address problem, some cable Internet Service Providers (ISPs) may lock their Internet connection against one MAC address for an Internet connection. Therefore, if the router is inserted between a computer with the particular MAC address and the ISP, then the ISP will not recognize and communicate with the new router. Therefore, if it is determined in step 1154 that the IP connection type is DHCP, then flow passes to step 1162 to determine whether the network adapter of the computer began as a public IP address. If it did not, then the problem is not a MAC address problem and a help screen may be displayed to the user in step 1166. However, if the adapter began as a public IP address, then flow passes to step 1164 and the MAC address is cloned. Specifically, the MAC address of the network adapter is copied to the router, so that the ISP may continue to believe it is communicating with the original network adapter. Flow then passes to step 1168 where Internet connectivity is tested again.
Referring again to step 1154, if it is determined that the IP connection type is PPPoE, then flow passes to step 1158 and a user interface screen is displayed to allow the user to enter their PPPoE credentials, such as a username and password, required by the particular ISP. Once these credentials have been entered, they are pushed into the router in step 1160 and flow passes to step 1168 to test for Internet connectivity again.
Referring again to step 1154, if it is determined that the router is in a double NAT configuration then flow passes to step 1156 to set the router to another subnet. This could occur if a user connects the router to another router that is connected to the modem rather than connecting the router directly to the modem. NAT is a technique that hides an entire address space, such as network addresses of devices connected to a private LAN, behind a single IP address, such as a public IP address assigned to a router connected to the LAN. In outgoing IP packets (i.e., packets received from the devices connected to the router), the router may use translation tables to map the “hidden” addresses of the originating devices into a single address, which is written in the outgoing packets so that they appear to originate from the router. Incoming response packets are mapped back to the originating IP address using the translation tables. In one embodiment, determining whether a double NAT configuration exists includes receiving a WAN IP address from the router and determining whether it is a loopback address (e.g., 127.0.0.1). If the router WAN IP address is the loopback address, then there is a conflict on the router's default IP address (e.g., 192.168.1.1). The router is assumed to be connected upstream to another router, and therefore, in a double NAT configuration. In this scenario, flow passes to step 1156 and the router being configured is set to another subnet (e.g., 192.168.0.1), in order to avoid conflict with the upstream router. Flow then passes to step 1168 to perform another test for Internet connectivity. The communication with the router may, in one embodiment, be achieved using the HNAP protocol.
With reference to step 1154, if the IP connection type is something other than DHCP, PPPoE, or a double NAT connection, then flow may pass to step 1166 where a help screen is displayed to assist the user in determining why there is no Internet connectivity. Similarly, if the error processing for DHCP, PPPoE and double NAT is performed and it is determined in step 1170 that there is still no Internet connectivity after testing for it in step 1168, then flow may pass to step 1166 where a help screen is displayed. It will be apparent that different help screens may be displayed depending on the particular Internet connection type and problems arising during the attempts to establish an Internet connection.
Once Internet connectivity has been established, either the first time it was tested at step 1102, or at step 1152 or 1168 after various error processing has occurred, a screen may be displayed in step 1106, such as the screen shown in
Referring to step 1134 of
With reference to step 1136 in
Turning now to
Configured XML file 1420 is a second stage of configuration settings file 410 in the example scenario, which may be stored on computer readable medium 400 (or on a new computer readable medium provided by the user) after a network has been configured with a first computer and a router. XML file 1420 may also be stored on the original or a new computer readable medium when a user launches administrative tool component 440 after it has been installed on a computer, as will be further discussed herein. Configured XML file 1420 may include a new wireless SSID, a new wireless (network) password, a new administrative password, and the serial number of the router. The mode element is set to “Connect” and a setup indicator (IsAlreadySetUp) is set to “true” so that the state of computer readable medium 400 will be recognized as Connect Mode for setup of an nth computer, where n>1. This mode indicates that a first computer has already been configured with the router, and therefore, when computer readable medium 400 is inserted in a computer, network application 420 knows to execute connect computer component 450 to configure a new computer to connect to the existing network.
Installed XML file 1430 is a third stage of configuration settings file 410 in the example scenario, which may be stored on the computer with administrative tool component 440, which is part of network application 420. With the exception of the mode element, the configuration settings in installed XML file 1430 may be the same as in configuration XML file 1420. The mode element in installed XML file 1430, however, is set to “Tool”, to indicate that the computer has been successfully configured for connection to the router, and administrative tool component 440 has been installed as part of network application 420 on the computer. Thus, when network application 420 is launched on the computer, it knows to execute administrative tool component 440 to provide users with the ability to configure administrative settings of the router and network or to add new computers or other devices to the network.
Turning now to
In one example embodiment, administrative tool component 440 gains administrative access on the router through a browser administration webpage. Typically, technology such as Basic Authentication requires an administrative username and password in order to gain access through the administration webpage so that router configurations and settings may be changed or otherwise modified. In one example embodiment, however, administrative tool component 440 sends a command to the router telling the router to trust access from the computer on which administrative tool component 440 is executing. The automatic access may be given for a specified period of time. This software to webpage transition enables administrative tool component 440 on the computer to change or otherwise modify router configurations and settings as necessary to carry out the selections requested by the user (e.g., connect computers or other devices, guest access, parental controls, router settings) without having to receive the administrative username or password from the user.
In step 1520, a screen is displayed with administrative tool options for a user to select, such as the screen shown in
Referring to
With reference again to step 1710 in
With reference again to step 1715 in
After the user has successfully connected a computer, a wireless printer or other wireless device and the user has clicked the NEXT user interface control button on the associated screen displayed on the first computer, flow passes to step 1765 where the operating system of the first computer polls the router for any new computers or other devices the router detects. In one embodiment, the router provides the network names of any detected computers and other devices to administrative tool component 440. The detected computers and other devices are then compared to a file stored in the first computer containing identifiers of configured network computers and other devices, to determine whether the router has detected anything new. If a new computer or device has been detected, the new identifier is added to the file in the first computer and the router also stores information about the new computer or device. If a new device is not found in step 1770, then a time out procedure is used in steps 1775 and 1780. In step 1775, a determination is made as to whether polling has reached a maximum time limit, and if it has not, flow loops back to step 1765 to continue polling to detect a new device in the network. However, if a maximum time limit has been reached in step 1775, then a display screen offering assistance to the user may be displayed in step 1780.
Once a new computer or device has been found on the network, and necessary information has been stored in the first computer and the router, a screen may be displayed on the first computer, such as the screen shown in
In another example embodiment, any of the networked devices may be given simple human readable names (e.g., “Joe's Phone”, etc.) by opening a browser on the particular device to be named. A simple word or phrase, (e.g., “IdentifyMe”, etc.) may be available for the router to capture a new name for the particular device. In this example, once a user types “IdentifyMe”, an HTML page may be sent to the device for the user to enter the new human readable name for the device. The router then matches the human readable name to the device so that the user can subsequently recognize the device when accessing the device through the network.
Referring now to
In step 2415, an operating system on the new computer may be used to search for available network adapters on the new computer. This search may be accomplished using operating system application programming interfaces (APIs). In step 2420, a determination is made as to whether a wireless network adapter has been found. In one embodiment, connect computer component 450 may default to configuring a wireless connection even if the new computer includes both wired and wireless adapters. In addition, although not specifically shown in
In one embodiment, logic shown and described with reference to
Not shown in
In step 2425, a wireless profile may be created in the new computer. The wireless profile may be created using existing configuration settings from configuration settings file 410 on the USB key. Configuration settings file 410 may contain configuration settings, such as those shown in example XML file 1420, which was shown and described with reference to
With reference to step 2430 of
With reference again to step 2420 in
Once the user finishes manually connecting the new computer to the router with a network cable, the user may click the NEXT user interface control button. As shown in step 2470 in
In another embodiment for guest networks, an option may be available for the authorized user to configure the guest network as a pay-per-use guest access model and/or as an ad-supported guest access model. For example, a guest network may be made available to any outside users, known or unknown to the authorized user of the host network, within a wireless connectivity range of the router. In one implementation, the outside user would be able to view the guest network in a list of available wireless networks whenever the outside user was within a wireless range of the router. Upon selecting the guest network, the outside user could be prompted to send a request seeking authorization to access the guest network. The authorization request could be sent to an authorized user of the host network. If the authorized user approves the outside user to access the guest network, then the outside user could be provided with the guest access password.
In a pay-per-use guest access model, the outside user could be charged a fee for usage. In one embodiment, the owner of the host network could have a dedicated account for receiving payments directly from such outside users. In another embodiment, an intermediary billing and payment provider (e.g., Paypal, etc.) could be used to process financial transactions between the owner of the host network and outside users. In an ad-supported guest access model, rather than receiving individual payments for access to the guest network, advertisements could be used in guest networks. For example, the login screen for the guest access network could contain various forms of advertisements. Thus, outside users could use the guest network without charge, but would become a captive audience for some advertisements during at least a portion of time spent accessing the guest network. In one embodiment, the owner of the host network, or any other authorized person, could sell such advertisements and receive payment directly from the advertisers. Alternatively, an Internet Service Provider (ISP) connected to the router could sell the advertisements. In this embodiment, payment to the owner of the host network could be arranged in any number of mutually acceptable ways, including, for example, as a deduction on a monthly bill from the ISP.
Turning now to
Turning to
In accordance with the present disclosure, embodiments of the system may include other screens to assist the setup and configuration of a network. For example, help screens may include instructions for the user to try to remedy the particular problem (e.g., wireless connection problem, Internet connection problem, etc.). Other help screens may suggest the user contact customer support and/or technical support and may provide, for example, a phone number, a web address, or other method to contact the particular support team. During some processing, a wait screen may be displayed to indicate that the system is currently processing. Screens may also be displayed when a particular connection that was previously established has been lost. Finally, various screens navigating the user through administrative options such as parental controls, guest access, and router settings may also be displayed when needed.
In an alternative embodiment of the system and method for simplifying secure network setup, computer readable medium 400 may be configured to directly access router 300 to provision a wireless network, such as network 100 shown in
In certain example implementations, the simplifying secure network setup activities outlined herein may be implemented in software, which can be provided at various locations. In one example implementation, this software, or portions thereof, is resident in one or more memory elements provided in a computer readable medium, a computer sought to be configured for connection to a network, and a router. In other examples, the software of the system for simplifying secure network setup activities could involve a proprietary element (e.g., as part of a network configuration and security solution), which could be provided in (or be proximate to) these identified elements, or be provided in any other device, network adapter, server, network appliance, console, firewall, switch, information technology (IT) device, distributed server, etc., or be provided as a complementary solution (e.g., in conjunction with parental controls), or provisioned somewhere in the network. For example, in the various embodiments described herein, the software may be provisioned in a memory element of a wireless network adapter provided to a computer to enable wireless connection to a router as described herein. In such embodiments, the wireless adapter may be configured to be plugged into a computer to provision a wireless network with the router or, in an alternative embodiment, may be configured to directly access the router to receive configuration settings prior to being plugged into the computer to provision the wireless network. In other embodiments, the software features may be provided externally to these elements, included in other devices to achieve these intended functionalities, or consolidated in any appropriate manner. For example, certain applications, components, or modules of the software could be separated and provided via another element such as a web server (e.g., application tool component 430). In a general sense, the arrangement depicted in
In some embodiments, these elements (e.g., computers 120, other electronic devices 110, router 130, computer readable medium 140, etc.) may include software (or reciprocating software) that can coordinate, manage, or otherwise cooperate in order to achieve the simplifying secure network setup operations, as outlined herein. One or all of these elements may also include any suitable algorithms, hardware, software, components, modules, interfaces, or objects that facilitate the operations thereof. In the implementation involving software, such a configuration may be inclusive of logic encoded in one or more tangible media (e.g., embedded logic provided in an application specific integrated circuit (ASIC), digital signal processor (DSP) instructions, software (potentially inclusive of object code and source code) to be executed by a processor, or other similar machine, etc.). In some of these instances, one or more memory elements (as shown in
Any of these elements (e.g., computer, computing device, electronic devices, router, etc.) can include memory elements for storing information to be used in achieving the system for simplifying secure network setup activities as outlined herein. Additionally, each of these devices may include a processor that can execute software or an algorithm to perform the secure network setup activities as discussed in this Specification. These devices may further keep information in any suitable memory element (e.g., random access memory (RAM), ROM, EPROM, EEPROM, ASIC, etc.), software, hardware, or in any other suitable component, device, element, or object where appropriate and based on particular needs. Any of the memory items discussed herein (e.g., computer readable medium 400, computer memory 220, router memory 320, etc.) should be construed as being encompassed within the broad term ‘memory element.’ Similarly, any of the potential processing elements, modules, and machines described in this Specification should be construed as being encompassed within the broad term ‘processor.’ Each of the computers, electronic devices, network appliances, routers, modems, servers, etc. may also include suitable wireless or hardwired interfaces for receiving, transmitting, and/or otherwise communicating data or information in a network environment.
Note that with the examples provided herein, interaction may be described in terms of two, three, four, or more network components (e.g., computer readable medium, router, adapters, computers, electronic devices, etc.). However, this has been done for purposes of clarity and example only. It should be appreciated that the system could be consolidated in any suitable manner, which is clearly within the broad scope of this Specification. In certain cases, it may be easier to describe one or more of the functionalities of a given set of flows by only referencing a limited number of components or network elements. Therefore, it should also be appreciated that the system of
It is also important to note that the operations described with reference to the preceding FIGURES illustrate only some of the possible scenarios that may be executed by, or within, the system and method in accordance with the present disclosure. Some of these operations may be deleted or removed where appropriate, or these operations may be modified or changed considerably without departing from the scope of the discussed concepts. In addition, the timing of these operations may be altered considerably and still achieve the results taught in this disclosure. The preceding operational flows have been offered for purposes of example and discussion. Substantial flexibility is possible in that any suitable arrangements, chronologies, configurations, and timing mechanisms may be provided without departing from the teachings of the discussed concepts.
Number | Name | Date | Kind |
---|---|---|---|
5383178 | Unverrich | Jan 1995 | A |
5396485 | Ohno et al. | Mar 1995 | A |
5420572 | Dolin et al. | May 1995 | A |
5712914 | Aucsmith et al. | Jan 1998 | A |
5758083 | Singh et al. | May 1998 | A |
5768483 | Maniwa et al. | Jun 1998 | A |
5774667 | Garvey et al. | Jun 1998 | A |
5838907 | Hansen | Nov 1998 | A |
5974237 | Shurmer et al. | Oct 1999 | A |
5978568 | Abraham et al. | Nov 1999 | A |
6006272 | Aravamudan et al. | Dec 1999 | A |
6023723 | McCormick et al. | Feb 2000 | A |
6157950 | Krishnan | Dec 2000 | A |
6456306 | Chin et al. | Sep 2002 | B1 |
6530018 | Fleming | Mar 2003 | B2 |
6584074 | Vasamsetti et al. | Jun 2003 | B1 |
6631118 | Jones | Oct 2003 | B1 |
6678250 | Grabelsky et al. | Jan 2004 | B1 |
6728262 | Woram | Apr 2004 | B1 |
6778505 | Bullman et al. | Aug 2004 | B1 |
6801941 | Stephens et al. | Oct 2004 | B1 |
6892245 | Crump et al. | May 2005 | B1 |
6925085 | Krishna et al. | Aug 2005 | B1 |
6954785 | Martin et al. | Oct 2005 | B1 |
6965614 | Osterhout et al. | Nov 2005 | B1 |
6980556 | Vimpari | Dec 2005 | B2 |
7020701 | Gelvin et al. | Mar 2006 | B1 |
7020720 | Donahue et al. | Mar 2006 | B1 |
7027808 | Wesby | Apr 2006 | B2 |
7039688 | Matsuda et al. | May 2006 | B2 |
7042988 | Juitt et al. | May 2006 | B2 |
7080141 | Baekelmans et al. | Jul 2006 | B1 |
7111054 | Lo | Sep 2006 | B2 |
7155493 | Weber | Dec 2006 | B1 |
7177957 | Vance | Feb 2007 | B2 |
7187461 | Schlonski et al. | Mar 2007 | B2 |
7200551 | Senez | Apr 2007 | B1 |
7240106 | Cochran et al. | Jul 2007 | B2 |
7249171 | Goto | Jul 2007 | B2 |
7269653 | Mentze et al. | Sep 2007 | B2 |
7283517 | Yan et al. | Oct 2007 | B2 |
7310664 | Merchant et al. | Dec 2007 | B1 |
7319873 | Zhang et al. | Jan 2008 | B2 |
7337910 | Cartmell et al. | Mar 2008 | B2 |
7340512 | Cochran et al. | Mar 2008 | B2 |
7388839 | Chafle et al. | Jun 2008 | B2 |
7392310 | Motoyama et al. | Jun 2008 | B2 |
7418702 | Tsao | Aug 2008 | B2 |
7421466 | Haines | Sep 2008 | B2 |
7457737 | Patiejunas | Nov 2008 | B2 |
7460546 | Anderson, IV | Dec 2008 | B2 |
7475133 | Nuggehalli | Jan 2009 | B2 |
7496660 | Blaisdell et al. | Feb 2009 | B2 |
7499999 | Ocepek et al. | Mar 2009 | B2 |
7506048 | Motoyama et al. | Mar 2009 | B1 |
7509415 | Baekelmans et al. | Mar 2009 | B2 |
7545762 | McConnell et al. | Jun 2009 | B1 |
7565418 | Ferrari et al. | Jul 2009 | B2 |
7581039 | Martinez et al. | Aug 2009 | B2 |
7603710 | Harvey et al. | Oct 2009 | B2 |
7657612 | Manchester et al. | Feb 2010 | B2 |
7769409 | Harris et al. | Aug 2010 | B2 |
7783777 | Pabla et al. | Aug 2010 | B1 |
7787416 | Gidwani | Aug 2010 | B2 |
7823199 | Rathi et al. | Oct 2010 | B1 |
7853880 | Porter | Dec 2010 | B2 |
8159949 | Pham | Apr 2012 | B2 |
20010039580 | Walker et al. | Nov 2001 | A1 |
20020004935 | Huotari et al. | Jan 2002 | A1 |
20020010866 | McCullough et al. | Jan 2002 | A1 |
20020026503 | Bendinelli et al. | Feb 2002 | A1 |
20020026505 | Terry | Feb 2002 | A1 |
20020112076 | Rueda et al. | Aug 2002 | A1 |
20020116544 | Barnard et al. | Aug 2002 | A1 |
20020147938 | Hamilton et al. | Oct 2002 | A1 |
20020161865 | Nguyen | Oct 2002 | A1 |
20020161867 | Cochran et al. | Oct 2002 | A1 |
20020174207 | Battou | Nov 2002 | A1 |
20020191556 | Krishnarajah et al. | Dec 2002 | A1 |
20020196463 | Schlonski et al. | Dec 2002 | A1 |
20030005112 | Krautkremer | Jan 2003 | A1 |
20030018889 | Burnett et al. | Jan 2003 | A1 |
20030033402 | Battat et al. | Feb 2003 | A1 |
20030040813 | Gonzales et al. | Feb 2003 | A1 |
20030041238 | French et al. | Feb 2003 | A1 |
20030061336 | Van Den Bosch et al. | Mar 2003 | A1 |
20030069947 | Lipinski | Apr 2003 | A1 |
20030078965 | Cocotis et al. | Apr 2003 | A1 |
20030078999 | Lund et al. | Apr 2003 | A1 |
20030086425 | Bearden et al. | May 2003 | A1 |
20030097439 | Strayer et al. | May 2003 | A1 |
20030115298 | Baker | Jun 2003 | A1 |
20030115314 | Kawashima | Jun 2003 | A1 |
20030187985 | Rohling et al. | Oct 2003 | A1 |
20030195937 | Kircher et al. | Oct 2003 | A1 |
20030200303 | Chong | Oct 2003 | A1 |
20030200318 | Chen et al. | Oct 2003 | A1 |
20030221122 | Hatori | Nov 2003 | A1 |
20030229688 | Liang | Dec 2003 | A1 |
20040003292 | Kato | Jan 2004 | A1 |
20040005873 | Groenendaal et al. | Jan 2004 | A1 |
20040015575 | Motoyama | Jan 2004 | A1 |
20040030620 | Benjamin et al. | Feb 2004 | A1 |
20040039704 | Gilliam et al. | Feb 2004 | A1 |
20040040023 | Ellis et al. | Feb 2004 | A1 |
20040049714 | Marples et al. | Mar 2004 | A1 |
20040064558 | Miyake | Apr 2004 | A1 |
20040083299 | Dietz et al. | Apr 2004 | A1 |
20040093383 | Huang et al. | May 2004 | A1 |
20040111505 | Callahan et al. | Jun 2004 | A1 |
20040146006 | Jackson | Jul 2004 | A1 |
20040155899 | Conrad | Aug 2004 | A1 |
20040156346 | O'Neill | Aug 2004 | A1 |
20040162986 | Metzger | Aug 2004 | A1 |
20040172469 | Takahashi et al. | Sep 2004 | A1 |
20040193709 | Selvaggi et al. | Sep 2004 | A1 |
20040199630 | Sarkissian et al. | Oct 2004 | A1 |
20040199647 | Ramarao et al. | Oct 2004 | A1 |
20040203592 | Kermode et al. | Oct 2004 | A1 |
20040204051 | Scott et al. | Oct 2004 | A1 |
20040236759 | Young | Nov 2004 | A1 |
20040255023 | Motoyama et al. | Dec 2004 | A1 |
20050004866 | Bonalle et al. | Jan 2005 | A1 |
20050005013 | Saint-Hailaire et al. | Jan 2005 | A1 |
20050018241 | Azami | Jan 2005 | A1 |
20050050189 | Yang | Mar 2005 | A1 |
20050050190 | Dube | Mar 2005 | A1 |
20050054326 | Rogers | Mar 2005 | A1 |
20050060535 | Bartas | Mar 2005 | A1 |
20050063350 | Choudhury et al. | Mar 2005 | A1 |
20050078681 | Sanuki et al. | Apr 2005 | A1 |
20050085244 | Choi et al. | Apr 2005 | A1 |
20050086197 | Boubez et al. | Apr 2005 | A1 |
20050086282 | Anderson et al. | Apr 2005 | A1 |
20050091504 | Shirogane | Apr 2005 | A1 |
20050111420 | Fujii | May 2005 | A1 |
20050114490 | Redlich et al. | May 2005 | A1 |
20050125527 | Lu et al. | Jun 2005 | A1 |
20050149626 | Manchester et al. | Jul 2005 | A1 |
20050160138 | Ishidoshiro | Jul 2005 | A1 |
20050165828 | Lango et al. | Jul 2005 | A1 |
20050165919 | Qian et al. | Jul 2005 | A1 |
20050184852 | Lee et al. | Aug 2005 | A1 |
20050198221 | Manchester et al. | Sep 2005 | A1 |
20050198274 | Day | Sep 2005 | A1 |
20050216602 | Armstrong et al. | Sep 2005 | A1 |
20050229238 | Ollis et al. | Oct 2005 | A1 |
20050234568 | Chung et al. | Oct 2005 | A1 |
20050234683 | Graves et al. | Oct 2005 | A1 |
20050235227 | Martineau et al. | Oct 2005 | A1 |
20050240665 | Gu et al. | Oct 2005 | A1 |
20050240758 | Lord et al. | Oct 2005 | A1 |
20050243777 | Fong | Nov 2005 | A1 |
20060015939 | Aston et al. | Jan 2006 | A1 |
20060031457 | Motoyama | Feb 2006 | A1 |
20060036847 | Bush et al. | Feb 2006 | A1 |
20060037036 | Min et al. | Feb 2006 | A1 |
20060037075 | Frattura et al. | Feb 2006 | A1 |
20060041891 | Aaron | Feb 2006 | A1 |
20060101109 | Nishio | May 2006 | A1 |
20060106918 | Evert et al. | May 2006 | A1 |
20060120293 | Wing | Jun 2006 | A1 |
20060129664 | Reimert et al. | Jun 2006 | A1 |
20060153080 | Palm | Jul 2006 | A1 |
20060168167 | Kushalnagar et al. | Jul 2006 | A1 |
20060168195 | Maturana et al. | Jul 2006 | A1 |
20060168263 | Blackmore | Jul 2006 | A1 |
20060172734 | Tak et al. | Aug 2006 | A1 |
20060258341 | Miller | Nov 2006 | A1 |
20060272014 | McRae et al. | Nov 2006 | A1 |
20060280189 | McRae et al. | Dec 2006 | A1 |
20060291443 | Harrington et al. | Dec 2006 | A1 |
20070015463 | Abel et al. | Jan 2007 | A1 |
20070022185 | Hamilton et al. | Jan 2007 | A1 |
20070058567 | Harrington et al. | Mar 2007 | A1 |
20070076621 | Malhotra et al. | Apr 2007 | A1 |
20070106768 | Frietsch et al. | May 2007 | A1 |
20070111568 | Ferrari et al. | May 2007 | A1 |
20070115950 | Karaguz et al. | May 2007 | A1 |
20070130286 | Hopmann et al. | Jun 2007 | A1 |
20070133569 | Lee et al. | Jun 2007 | A1 |
20070143749 | Date et al. | Jun 2007 | A1 |
20070204150 | Jokela et al. | Aug 2007 | A1 |
20070268506 | Zeldin | Nov 2007 | A1 |
20070268515 | Freund et al. | Nov 2007 | A1 |
20070268516 | Bugwadia et al. | Nov 2007 | A1 |
20070276931 | Mahdavi et al. | Nov 2007 | A1 |
20070291945 | Chuang et al. | Dec 2007 | A1 |
20080008125 | Pham et al. | Jan 2008 | A1 |
20080037552 | Dos Remedios et al. | Feb 2008 | A1 |
20080043989 | Furutono et al. | Feb 2008 | A1 |
20080049779 | Hopmann et al. | Feb 2008 | A1 |
20080052384 | Marl et al. | Feb 2008 | A1 |
20080065760 | Damm et al. | Mar 2008 | A1 |
20080070603 | Mao | Mar 2008 | A1 |
20080134164 | Stich et al. | Jun 2008 | A1 |
20080175187 | Lowry et al. | Jul 2008 | A1 |
20080216154 | Fontaine | Sep 2008 | A1 |
20080243699 | Hilerio et al. | Oct 2008 | A1 |
20090017832 | Tebbs et al. | Jan 2009 | A1 |
20090019141 | Bush et al. | Jan 2009 | A1 |
20090019147 | Ahlers et al. | Jan 2009 | A1 |
20090019314 | Younger et al. | Jan 2009 | A1 |
20090037606 | Diab | Feb 2009 | A1 |
20090046656 | Kitazoe et al. | Feb 2009 | A1 |
20090052338 | Kelley et al. | Feb 2009 | A1 |
20090055514 | Tebbs et al. | Feb 2009 | A1 |
20090109897 | Woo | Apr 2009 | A1 |
20100020694 | Jones | Jan 2010 | A1 |
20100035595 | Duggal et al. | Feb 2010 | A1 |
20100093278 | Abel | Apr 2010 | A1 |
20100250725 | Meenan et al. | Sep 2010 | A1 |
20110047254 | Vainionpaa et al. | Feb 2011 | A1 |
20120008529 | Averbuch et al. | Jan 2012 | A1 |
Number | Date | Country |
---|---|---|
1315334 | May 2003 | EP |
1370025 | Dec 2003 | EP |
1538792 | Jun 2005 | EP |
1553729 | Jul 2005 | EP |
1638258 | Mar 2006 | EP |
1639751 | Mar 2006 | EP |
1701478 | Sep 2006 | EP |
1894314 | Mar 2008 | EP |
1965541 | Sep 2008 | EP |
2324652 | May 2011 | EP |
2411801 | Sep 2005 | GB |
2001-222497 | Aug 2001 | JP |
2001-352328 | Dec 2001 | JP |
2004-0047209 | Jul 2004 | KR |
10-2005-0031175 | Apr 2005 | KR |
2005-0078541 | Aug 2005 | KR |
2005-0094247 | Sep 2005 | KR |
WO2005004401 | Jan 2005 | WO |
WO2007001629 | Jan 2007 | WO |
WO2007136804 | Nov 2007 | WO |
WO 2008156898 | Dec 2008 | WO |
WO 2009011962 | Jan 2009 | WO |
WO 2009011963 | Jan 2009 | WO |
WO 2009011964 | Jan 2009 | WO |
WO 2009011965 | Jan 2009 | WO |
WO 2009011966 | Jan 2009 | WO |
WO2010016855 | Feb 2010 | WO |
WO2011119264 | Sep 2011 | WO |
Entry |
---|
“Wi-Fi Alliance™ for Wi-Fi Protected Setup Specification,” Version 1.0h, Dec. 2006, 110 pages. |
PCT Notification of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration, International Application No. PCT/US2008/063318, mailed Sep. 25, 2008, 6 pages. |
U.S. Appl. No. 11/696,638, filed Apr. 4, 2007, entitled “Network Management Providing Network Health Information and Lockdown Security,” Inventor(s) Steve Bush et al. |
Marcia Zangrilli, et al., “Using Passive Traces of Application Traffic in a Network Monitoring System,” © 2004 IEEE, 11 pages. |
Kazuya Kubo, et al., “Hybrid Peer-to-Peer System for Network Monitoring of Field Devices,” Downloaded May 14, 2009 from IEEE Xplore, © 2003 SICE, 6 pages. |
International Search Report for International Application No. PCT/US2008/063335 mailed Sep. 22, 2008 (1 page). |
Written Opinion of the International Searching Authority for International Application No. PCT/US2008/063335 mailed Sep. 22, 2008 (4 pages). |
International Search Report for International Application No. PCT/US2008/063308 mailed Oct. 30, 2008 (2 pages). |
Written Opinion of the International Searching Authority for International Application No. PCT/US2008/063308 mailed Oct. 30, 2008 (4 pages). |
International Search Report for International Application No. PCT/US2008/063333 mailed Sep. 26, 2008 (2 pages). |
Written Opinion of the International Searching Authority for International Application No. PCT/US2008/063333 mailed Sep. 26, 2008 (4 pages). |
International Search Report for International Application No. PCT/US2008/059490 mailed Apr. 21, 2009 (2 pages). |
International Preliminary Report on Patentability issued Oct. 6, 2009 (1 page) and Written Opinion of the International Searching Authority mailed Apr. 21, 2009 (3 pages) for International Application No. PCT/US2008/059490. |
Notification Concerning Transmittal of International Preliminary Report on Patentability (1 page), International Preliminary Report on Patentability (1 page), and Written Report of the International Searching Authority (4 pages) mailed Jan. 28, 2010 for International Application No. PCT/US2008/063318. |
Barb Bowman, “Introduction to Windows XP Service Pack 2,” Published Aug. 25, 2004, 8 pages; © 2010 Microsoft Corporation http://www.microsoft.com/windowsxp/using/security/expert/bowman—introtosp2.mspx. |
Microsoft TechNet, “The Cable Guy—Jun. 2004: The New Wireless Network Setup Wizard in Windows XP Service Pack 2,” Published May 25, 2004; Updated Aug. 4, 2004, 10 pages; © 2010 Microsoft Corporation; http://technet.microsoft.com/en-us/library/bb878069.aspx. |
Microsoft Corporation, “Windows Connect Now-UFD for Windows XP Specification,” © 2010, Updated Sep. 15, 2006, 1 page; http://www.microsoft.com/whdc/connect/Rally/WCN-UFD—XPspec.mspx. |
Microsoft Corporation, “Windows Connect Now-UFD for Windows XP,” Version 1.1 © 2010—Sep. 15, 2006, 33 pages; http://www.microsoft.com/whdc/connect/Rally/WCN-Netspec.doc. |
Microsoft Corporation, “Windows Connect Now-UFD and Windows Vista Specification,” Version 1.0 © 2010—Sep. 15, 2006, 1 page; http://www.microsoft.com/whdc/connect/Rally/WCN-UFD—Vistaspec.mspx. |
Microsoft Corporation, “Windows Connect Now-UFD Windows Vista” Version 1.0 © 2010—Sep. 15, 2006, 28 pp.; http://www.microsoft.com/whdc/connect/Rally/WCN-UFD—Vistaspec.doc. |
Microsoft Corporation, “Windows Connect Now—Access Point has No USB Port in Wireless Networking,” © 2010, printed Mar. 24, 2010, 2 pages; http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windows.networking.wireless&tid=c55b567e-fec3-43be-8bd1-a3216125c7f9&cat=en—US—d02fc761-3f6b-402c-82f6-ba1a8875c1a7&lang=en&cr=&sloc=en-us&m=1&p=1. |
Flip Video, “Quick Start Guide: FlipshareTV,” © 2009 Cisco Systems, Inc., 19 pages; http://www.theflip.com/pdf/en-US/FlipShareTVQuickStartGuide.pdf. |
“Wi-Fi Certified™ for Wi-Fi Protected Setup™: Easing the User Experience for Home and Small Office Wi-Fi® Networks,” © 2007, 14 pages; http://www.wi-fi.org/files/kc/20090123—Wi-Fi—Protected—Setup. pdf. |
“Cisco Access Router USB Flash Memory Module and USB eToken Hardware Installation Guide,” © 2006 Cisco Systems, Inc., 12 pages; https://www.cisco.com/en/US/docs/routers/access/2800/hardware/notes/mithril.html. |
Byoung-Koo Kim/Jong-Su Jang/Tai M. Chung, Design of Network Security Control System for Cooperative Intrusion Detection, 2002, pp. 389-398. |
U.S. Appl. No. 13/029,335, filed Feb. 17, 2011, entitled “Network Management,” Inventor(s) Steven M. Bush, et al. |
U.S. Appl. No. 13/030,982, filed Feb. 18, 2011, entitled “Network Management,” inventor(s) Steven M. Bush, et al. |
U.S. Appl. No. 13/031,121, filed Feb. 18, 2011, entitiled “Network Management,” Inventor(s) Steven M. Bush, et al. |
“Near Field Communication White Paper,” Ecma International, 2005; 12 pages. http://www.ecma-international.org/activities/Communications/tc32-tg19-2005-012.pdf. |
“Universal Plug and Play Device Architecture, UPnP, Version 1.0,” Microsoft Corporation, Protocols, Jun. 8, 2000; 54 pages; http://upnp.org/specs/arch/UPnPDA10—20000613.pdf. |
EPO Nov. 15, 2007 European Search Report and Opinion from European Application No. EP07017509; 8 pages. |
Khedr, Mohamed, et al., “Acan-Ad Hoc Context Aware Networks,” Online! 2002, XP002300569; 5 pages;http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.20.1469. |
Krishnamurthy, Lakshman, et al., “Meeting the Demands of the Digital Home with high-Speed Multi-Hop Wireless Networks,” Intel Technology Journal, vol. 6, Nov. 15, 2002, pp. 57-68; http://download.intel.com/technology/itj/2002/volume06issue04/vol6iss4—interoperable—home—infrastructure.pdf. |
PCT Oct. 27, 2004 International Search Report from International Application PCT/US2004/021429; 3 pages. |
PCT Jan. 3, 2006 International Preliminary Report on Patentability and Written Opinion of the International Search Authority from International Application PCT/US2004/021429; 7 pages. |
PCT Dec. 24, 2007 International Preliminary Report on Patentability and Written Opinion of the International Search Authority from International Application PCT/US2006/17500; 6 pages. |
PCT Aug. 7, 2007 International Search Report from International Application PCT/US06/17500; 1 page. |
PCT Nov. 21, 2008 International Preliminary Report on Patentability and Written Opinion of the International Search Authority from International Application PCT/US2007/012016; 5 pages. |
PCT Jan. 4, 2008 International Search Report from International Application PCT/US07/12016; 1 page. |
PCT Apr. 24, 2009 International Search Report from International Application PCT/US2008/08544; 2 pages. |
PCT Aug. 2, 2011 International Preliminary Report on Patentability and Written Opinion of the International Search Authority from International Application PCT/US2008/08544; 7 pages. |
PCT Aug. 25, 2011 International Search Report and Written Opinion of the International Searching Authority from International Application PCT/US2011/024462. |
Rasheed, Yasser, et al, “Home Interoperability Framework for the Digital Home,” Intel Technology Journal, vol. 6, Nov. 15, 2002, pp. 5-16; http://download.intel.com/technology/itj/2002/volume06issue04/vol6iss4—interoperable—home—infrastructure.pdf. |
Walker, Mark, et al., “Remote I/O: Freeing the Experience from the Platform with UPnP Architecture,” Intel Technology Journal, vol. 6, Nov. 15, 2002, pp. 30-36; http://download.intel.com/technology/itj/2002/volume06issue04/vol6iss4—interoperable—home—infrastructure.pdf. |
U.S. Appl. No. 13/235,007, filed Sep. 16, 2011, entitled “Configuring a Secure Network,” Inventor(s) Aaron H. Averbuch, et al. |
Karygiannos, Tom, et al., “Wireless Network Security 802.11 Bluetooth and Handheld Devices,” NIST Special Publication 800-48, Technology Administration, Dept. of Commerce, 2002, 119 pages. |
EPO Apr. 5, 2012 Search Report and Written Opinion from European Application 08769420.4; 8 pages. |
PCT Oct. 11, 2012 Notification Concerning Transmittal of International Preliminary Report on Patentability and the International Preliminary Report on Patentability and Written Opinion of the International Searching Authority from Application No. PCT/US2011/024462; 9 pages. |
EPO Oct. 24, 2012 Response to Written Opinion from European Application 0876920.4; 21 pages. |
Number | Date | Country | |
---|---|---|---|
20110235549 A1 | Sep 2011 | US |