Patent Grant
10154409
The described embodiments relate generally to wireless networking. More particularly, the described embodiments relate to methods, systems and apparatuses for binding an authenticated user with a wireless device.
Many companies are building products that benefit from a connection to a cloud service via the internet. For example, whitegoods manufacturers are connecting appliances like dishwashers and refrigerators to the internet to provide better customer service through remote access to the devices, and TV manufacturers are using internet connectivity to enable content streaming. WiFi (Wireless Fidelity) is a trademarked phrase that means IEEE 802.11x, and is becoming the predominant connectivity model for consumer connected products as well as many industrial and commercial connected products.
There are typically two association processes that must be executed for the device to be fully functional. A first process includes a network association which includes connecting the device to the network. A second process includes an account association that includes logically associating the device with the account of a user. For example, the account association can include associating a specific light bulb (serial number 1234-5678-91011) with a specific user account (username joe@example.com).
The Account Association process can be done in a number of ways. A first solution includes the user entering the serial number. In this case the user finds the serial number for the product (it might be a sticker on the box or printed on the device, for example) and enters this into a web page or app (this entry might be typing in the serial number or taking a picture of a QR code). A second solution includes that application and device looking for each other on the local network. In this case the application (on a phone for example) looks on the local WiFi network for the device. The device manufacturer assumes that because the device is on the local WiFi network it is owned by the user that is using the app, so the Account Association is done dependent on the Network Association. A third solution includes a side channel. In this case the application (on a phone for example) uses some alternative local communication (for example, bluetooth, light, or sound) to communicate locally with the device. The device manufacturer assumes that because the device and application are in the same physical proximity, the device is owned by the user that is using the application.
The first solution has a few limitations. Specifically it requires user intervention, it's subject to error, and it can be confusing to users. The second and third solutions require a local network connection to the device. If a phone is operating without WiFi and/or bluetooth turned on these methods can fail. In addition, if a device is using a public network or a network that is not controlled by the user, the device may not be attached to the local physical network or connection to the same network may not indicate that the user owns the device.
It is desirable to have a system, method and apparatus for binding an authenticated user with a wireless device. Further, it is desirable that the system, method and apparatus make this above-described process smoother, easier, and less error prone.
An embodiment includes a method of binding an authenticated user with a wireless device. The method includes receiving, by a cloud system, local environment information from the wireless device, receiving, by the cloud system, local information from a computing device of the authenticated user, comparing, by the cloud system, the local environment information of the wireless device with the local information of the computing device, binding, by the cloud system, the wireless device with the computing device based on the comparison of the local environment information of the wireless device with the local information of the computing device, and communicating, by the cloud system, information to a wireless device cloud management system that indicates that the binding between the wireless device and the computing device has occurred.
Another embodiment includes a cloud system network. The cloud system network includes cloud system, wherein the cloud system is operative to bind an authenticated user with a wireless device. Further, the cloud system network includes a wireless device cloud management system connected through a network to the cloud system. Further, the wireless device is connected through the network to the cloud system. The cloud system is operative to receive local environment information from the wireless device, receive local information from a computing device of the authenticated user, compare the local environment information of the wireless device with the local information of the computing device, bind the wireless device with the computing device based on the comparison of the local environment information of the wireless device with the local information of the computing device, communicate information to the wireless device cloud management system that indicates that the binding between the wireless device and the computing device has occurred, wherein the wireless device cloud management system is operative to allow the authenticated user to control the wireless device upon receiving the information that indicates that the binding between the wireless device and the computing device has occurred.
Another embodiment includes a cloud system. The cloud system is operative to receive local environment information from a wireless device, receive local information from a computing device of an authenticated user, compare the local environment information of the wireless device with the local information of the computing device, bind the wireless device with the computing device based on the comparison of the local environment information of the wireless device with the local information of the computing device, communicate information to the wireless device cloud management system that indicates that the binding between the wireless device and the computing device has occurred, wherein the wireless device cloud management system is operative to allow the authenticated user to control the wireless device upon receiving the information that indicates that the binding between the wireless device and the computing device has occurred.
Other aspects and advantages of the described embodiments will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, illustrating by way of example the principles of the described embodiments.
The described embodiments include systems, methods, and apparatuses for binding an authenticated user with a wireless device.
For an embodiment, the cloud system 110 binds an authenticated user 145 with a wireless device 130. As shown, the wireless device 130 is connected through the network (which generally includes an access point connected, for example, to the internet 135) to the cloud system 110. The wireless device can include any consumer device, such as, an internet-connected washing machine, an internet-connected thermostat, an internet-connected television, or an internet-connected toy.
Further, the system includes a wireless device cloud management system 120 that is connected through the network to the cloud system 110. For at least some embodiments, the wireless device cloud management system 120 includes one or more servers that store information that binds specific wireless devices to specific user accounts, and allows authenticated users to retrieve data from or control the bound wireless devices.
For at least some embodiments, the cloud system 110 is operative to receive local environment information from the wireless device. The local environment information includes, for example, a location of the wireless device, an estimated location of the wireless device, and/or sensed signals or conditions proximate to the wireless device. For an embodiment, the local environment information of the wireless device includes a global position system (GPS) location or a determined latitude and longitude of the wireless device. For an embodiment, the local environment information of the wireless device includes sensed wireless access point signatures received by the wireless device. That wireless access point signatures can include received WiFi signatures, received Bluetooth signatures, received cellular signatures, or received long-range-radio signatures. For at least some embodiments, the local environment information includes other sensed signals as well. For example, for an embodiment, the other sensed signals include at least one of sensed audio, sensed images, sensed vibration, sensed light, sensed temperature, sensed biometrics, or sensed gasses.
For at least some embodiments, the cloud system 110 is operative to receive local information from a computing device of the authenticated user. For at least some of the described embodiments, the computing device can include a smartphone, a laptop computer, a tablet computer, a desktop computer, a router, or a standalone computing device.
Similar to the local environmental information of the wireless device, for at least some embodiments, the local environment information includes, for example, a location of the computing device, an estimated location of the computing device, and/or sensed signals or conditions proximate to the computing device. For an embodiment, the local environment information of the computing device includes a global position system (GPS) location or a determined latitude and longitude of the computing device. For an embodiment, the local environment information of the computing device includes sensed wireless access point signatures received by the computing device. That wireless access point signatures can include received WiFi signatures, received Bluetooth signatures, received cellular signatures, or received long-range-radio signatures. For at least some embodiments, the local environment information includes other sensed signals as well. For example, for an embodiment, the other sensed signals include at least one of sensed audio, sensed images, sensed vibration, sensed light, sensed temperature, or sensed gasses
For at least some embodiments, the cloud system 110 is operative to compare the local environment information of the wireless device with the local information of the computing device. For an embodiment, the comparison includes matching a physical location or an estimated physical location of the wireless device with a physical location or an estimated physical location of the computing device. For an embodiment, the comparison includes matching a wireless access point signature of the wireless device with a wireless access point signature of the computing device. For an embodiment, the comparison includes additionally or alternatively matching other sensed signals of the wireless device with other sensed signals of the computing device. For at least some embodiments, the other sensed signals includes at least one of sensed audio, sensed images, sensed vibration, sensed light, sensed temperature, sensed biometrics, or sensed gasses.
For at least some embodiments, the cloud system 110 is operative to bind the wireless device with the computing device based on the comparison of the local environment information of the wireless device with the local information of the computing device. For at least some embodiments, the binding is completed if the matching or comparison of the local environment information of the wireless device with the local information of the computing device is within a predetermined threshold. That is, for example, the binding is completed if the location or the estimated location of the wireless device is within a threshold distance from the location or the estimated location of the computing device. Further, for example, for an embodiment, the binding is completed upon determining that wireless access point signatures received by the wireless device are within a similarity of wireless access point signatures of the computing device. For example, if the computing device and the wireless device both receive wireless signals form the same Wi-Fi router, then it can be assume that the computing device and the wireless device are in physical proximity. Further, for example, for an embodiment, the binding is completed upon determining that other sensed signals of the wireless device are similar to the sensed signals of the computing device. For example, an audio recording from the wireless device and the computing device can be compared and it can be determine that the computing device and the wireless device are likely in the same room. As another example, a picture or video from the computing device can be compared with a picture or video from the wireless device. As another example, an audio sensed by the computing device can be compared with the audio sensed by the wireless device. As another example, a vibration sensed by the wireless device can be compared with a vibration sensed by the computing device.
For at least some embodiments, the cloud system 110 is operative communicate information to the wireless device cloud management system that indicates that the binding between the wireless device and the computing device has occurred.
At least some embodiments includes a connected wireless device (a wireless device that has internet connectivity), an access point or router (the device that allows joining of a network, for example a WiFi router in a home), a device cloud application (the software application, which may be owned and operated by the connected wireless device manufacturer, that connects to the device), the federated device cloud application (which may be run as a service by an operator), and the internet (providing connectivity from the access point or router to the wireless device connected application).
At least some of the described embodiments make it dramatically easier to connect internet-enabled products to wireless networks. Many of these devices (such as, Wi-Fi-enabled printers, lightbulbs, and/or kitchen appliances) do not have a rich user interface with a screen and keyboard, so it is difficult to configure these devices to connect to the wireless network. At least some of the described embodiments create a way to instantly and securely connect devices to the internet.
For at least some embodiments, the cloud system 340 includes one or more servers, and one or more databases. The databases include information on the wireless devices, the pre-shared keys and certificates, the access plans for the devices, the internet domains that the devices are allowed to communicate with, the networks that the devices are allowed to join, and the connection bandwidth parameters of the devices. The servers of the cloud system 340 receive the authentication requests from the routers and devices, and use the data in the database to decide whether to authenticate the device, and what internet domains and connection bandwidth parameters should be passed back to the router.
For at least some embodiments, the authentication request includes the negotiation of a set of security keys to secure the transmission of the wireless device credentials (pre-shared key or certificate). For an embodiment, the authentication process includes mutual authentication of the router and the cloud system through the use of digital certificates or a shared secret.
For an embodiment, the authentication process includes the router 330 redirecting the wireless device 310 to a captive portal, which resides on a server separate from the cloud system 340, and which negotiates the authorization and authentication process on behalf of the router 330 before passing the connection bandwidths and internet domain parameters back to the router 330.
For an embodiment, the authentication process include the router 330 implementing firewall rules on the router 330 to prevent the wireless device 110 from connecting to domains that are not on the list of approved domains.
For an embodiment, the authentication process includes the router 330 implementing bandwidth limitations on the device connection, which prevents the wireless device 310 from communicating outside the range of these bandwidth limitations.
At least some embodiments include a manufacturer of the wireless device 310 registering the wireless device 310 with the cloud system 340, and agreeing upon a credential for the wireless device 310. For an embodiment, the credential includes a pre-shared key (password) or a digital certificate. For an embodiment, the credentials are stored on non-volatile memory of the wireless device 310.
Further, for an embodiment, the manufacturer also specifies the internet domains the wireless device 340 needs to connect to, and chooses a data access plan, which may include connection bandwidths. For an embodiment, the connection bandwidth may include an upstream and/or downstream bandwidth, a duration of the connection, a total time on the network, an aggregate bandwidth of over time, and/or an aggregate data cap (for example 1 gigabyte per month). As will be described, for an embodiment, the connection bandwidth is adaptively adjusted.
For at least some embodiments, the cloud service 340 is coordinated with a set of wireless routers in homes of users that allow access to the internet if the wireless devices of the users are approved by the cloud service.
For an embodiment the cloud system 340 is connected to the router 330 via a proxy cloud system. The proxy cloud system in this case routes the authentication requests to the cloud system 340 based on the realm identified in the device credentials.
For at least some embodiments, the connection bandwidth is adaptively adjusted based on a variety of different parameters, including business agreements, available bandwidth, the service level agreed with the device manufacturer, the service level agreed with the router operator, the service level agreed with the internet service subscriber, the time of day, the amount of data the device has already used, the historical data usage of the wireless device 310, or other variables.
For at least some embodiments, the manufacturer puts the credential and the network configuration on the wireless device 310 when the wireless device 310 is manufactured. The network configuration defines the set of networks the wireless device 310 should try to join. For an embodiment, the network configuration is updated periodically, and the wireless device 310 receives, for example, the updated network configurations from time to time over the internet.
For an embodiment, the network configuration is updated based on new business relationships, aggregated or historical network performance data, network performance data from specific routers, or other variables.
For at least some embodiments, when the wireless device 310 is powered up (power turned on) by a user, the wireless device 310 automatically attempts to connect to one of the wireless networks included in the network configuration. When the device attempts to connect, the router (such as, router 330) the wireless device 310 is attempting to connect to queries the cloud service (of the cloud system 340) to authenticate the wireless device 310 and authorize the wireless device 310 to join the network. For an embodiment, the cloud service (of the cloud system 340) sends back to the router 330 allowed parameters of the connection. For an embodiment, the allowed parameters include the domains the wireless device 310 is allowed to access and the bandwidth and other connection parameters.
As described, at least some embodiments address some of the biggest security risks for wireless-connected products. The wireless device(s) are given access to the internet—but only very limited access, because the domains the wireless devices are allowed to connect to is limited to the domains preconfigured by the device manufacturer. This prevents devices from being hacked and used as part of denial-of-service and other security attacks.
At least some of the described embodiments provide users a way to use internet-connected devices that may not be trusted. The devices are joining the wireless network, but are not authorized to communicate with other devices in the local network—they are specifically bound to communicate only with the specified internet domains. This feature allows for safe, secure zero-touch joining. Further, because the device joins the wireless network automatically, and because the user may wish to have the device on a different, secure wireless network, there is some complexity on the device in managing the network configurations and the connections to the various networks.
For an embodiment, a wireless connection manager (WCM) that operates on the wireless device dynamically decides whether the wireless device should join the user's (user of the wireless device) secure personal network or the authorized network (the network that device is allowed to join through authentication from the cloud service of the cloud system). For an embodiment, the wireless connection manager prioritizes a secure personal network, but opting to use the network which is authorized by the cloud service of the cloud system if network performance of the secure personal network falls below a threshold level. For an embodiment, the wireless connection manager of the wireless device selects to send at least some data on a secure personal network, and send at least some other data on the network which is authorized by the cloud service of the cloud system. The partitioning of network connectivity across time and across data sources or data types can be done dynamically by the device, and can be directed by the cloud system or by configurations pulled by the device from the cloud system. That is, an embodiment includes dynamically partitioning between the sending of the at least some data on the secure personal network, and the sending the at least some other data on the network authorized by the cloud service of the cloud system, wherein the dynamic partitioning is performed by either the wireless device or by the cloud system.
For an embodiment, the WCM is software that runs on the wireless device 310 to manage the wireless connection and configuration. The WCM uses the network configuration to decide which network to join. If a user wants the wireless device 310 to connect on a different network, the WCM prioritizes that network, and stays connected to it if possible. It can fall back to another network if the preferred network is not available. For at least some embodiments, the WCM includes device code that manages the automatic joining the network.
Further, for an embodiment, the WCM may also include software to upload wireless network performance or technical information to the cloud service 340. The WCM can upload information such as network traffic patterns, availability or visibility of wireless networks, network performance parameters, device communication parameters, device usage data, device logs, or other device data.
For an embodiment, the WCM also updates the cloud service 340 with the real time status of the wireless device 310. This status may include information about the network the device is connected to such as the network name, router MAC address, and signal strength.
As previously described, at least some of the described embodiments make it dramatically easier to connect internet-enabled products to wireless networks. Many of these devices (such as, Wi-Fi-enabled printers, lightbulbs, and/or kitchen appliances) do not have a rich user interface with a screen and keyboard, so it is difficult to configure these devices to connect to the wireless network. At least some of the described embodiments create a way to instantly and securely connect devices to the internet.
For at least some embodiments, the wireless device 310 periodically retrieves a list of approved networks from a cloud service of the cloud system 340, wherein the list of approved networks includes a prioritization of the approved networks. When the wireless device 310 looks for networks to join, the wireless device 310 compares the list of available networks advertised from nearby routers from a scan of a local wireless environment with the list of approved networks, and chooses the highest priority network that is available to be joined. By updating the list of approved networks on the cloud service of the cloud system 340, the wireless device 310 is adaptively updated to associate with a specific set of routers.
For an embodiment, the adaptive updating is done based on a number of criteria including cost, network performance, device connectivity success rate, bandwidth, limitations on the connection parameters, limitations on the domains, signal strength, or other network parameters. For example, the wireless device could periodically update its connection information to the cloud system, and if the device repeatedly falls off of a particular network or has communications trouble on a particular network, the cloud system could update the network configuration to lower the priority of that network. That is, for an embodiment, the cloud service of the cloud system 140 adaptively updates the list of approved networks, wherein adaptive updating includes lowering a priority of an approved network if the wireless device repeatedly has problems communicating with the approved network.
For an embodiment the router 330 is one of a plurality of routers 330, 432, 434, 436 that the wireless device 110 is allowed to authenticate against, and wherein the plurality of routers 430, 432, 434, 436 that the wireless device 310 is allowed to authenticate against is adaptively updated in the cloud system 340.
For at least some embodiments, the cloud system 340 is configured to specify which devices are allowed to join which routers. For at least some embodiments, when a router sends a message to the cloud service of the cloud system 340 to authenticate a specific wireless device, the cloud service approves or rejects that request based on this configuration. For at least some embodiments, this configuration is dynamically updated to change which wireless devices can successfully associate with which routers.
For an embodiment, this configuration for approving devices on a router is done based on a number of different parameters including connectivity cost, network performance, network bandwidth, business relationships between the entity that designs, builds, or sells the device and the company that designs, builds, sells, or operates the router. For an embodiment, this configuration is updated over time as these parameters or relationships change.
An embodiment includes preconfiguring the internet domains and the connection bandwidth into the cloud system 340. For at least some embodiments, the internet domains and connection bandwidth configurations, which are stored in the cloud system, can be modified over time—even after a device has been deployed.
For an embodiment, this modification is done manually by an operator of the cloud system 340, based on business priorities or technical metrics like bandwidth or network performance. For an embodiment, these modifications are done automatically by analysis of the wireless device 310 or network performance, as monitored by the wireless device 310 or the cloud system 340.
For at least some embodiments, the internet domains and connection bandwidth parameters are updated at any time in the cloud system 340. When a wireless device attempts to associate with a router, and the router sends the authentication request to the cloud system 340, the cloud system 340 dynamically determines the domains and connection bandwidth configuration. For at least some embodiments, this configuration is updated at any time, and the new parameters are sent to the router the next time the wireless device attempts to associate.
This allows device manufacturers to provide dynamic services to their customers by expanding the network capability of the devices, to remotely turn on a network connection for a specific device or set of devices. For example, a kitchen appliance company makes a Wi-Fi connected appliance. The appliances are configured at the time of manufacture to connect only to the cloud service. If the appliance manufacturer receives a warranty claim or a service call, they can dynamically provision a direct connection to the device by adding an additional internet domain to the provisioned connection for the device. This allows the appliance manufacturer to communicate directly to the device to identify what is wrong. This can reduce the cost of providing service, eliminate field service calls, and enable better customer support.
For an embodiment, the cloud system 340 is preconfigured to accept authentication requests from the router. For an embodiment, the cloud system is configured to only accept authentication requests from a specific set of routers. By rejecting authentication requests from non-approved routers, the cloud system 340 eliminates some security vulnerabilities around repeated retries of passwords. For an embodiment, this pre-configuration can be periodically changed as a company rolls out new routers, or as old routers are removed from service.
For an embodiment, the router is configured to send the authentication request to the cloud system 340. For an embodiment, the deployed routers are configured to send authentication requests to the cloud system 340, either by provisioning a specific internet domain or IP address. For an embodiment, the routers are configured through software at the time of manufacture, or through a configuration or software update while in the field. This configuration tells the router that devices that attempt to associate should be authenticated and authorized by the cloud service 340.
For at least some embodiments, the cloud service (of the cloud system 340) is configured to and updated to allow or disallow specific wireless devices to associate with specific routers. For an embodiment, this configuration happens in two places: in the wireless device through its network configuration, and in the cloud service through the authorization process.
As previously described, the location detection devices 531, 541 can include any number of location detection devices, such as, global positioning systems (GPS), location detection through wireless access point signature matching, accelerometers, gyroscopes, magnetic sensors, and/or compasses. The location detection devices 531, 541 generate location information.
As previously described, the at least one sensors 532, 542 can include any number of sensors, such as, audio, vibration, image, etc. At least some embodiments include any number of sensors, wherein the sensed signals are maintained individually or combined. The at least one sensors 532, 542 generate sensed information.
The computing device 540 and the wireless device 530 upload (typically through a network) the location detection information and sensed information to the cloud system 510. As previously described, the cloud system 510 determines whether to bind the computing device 540 and the wireless device 530 based on matching or comparing or correlating the local environment information (including at least the location detection information and sensed information) of the wireless device 530 with the local information (including at least the location detection information and sensed information) of the computing device 540.
As shown, and previously described, the cloud system 510 can alternatively, or additionally match, compare or correlate timing of the environment information of the computing device 540 and the wireless device 530. That is, for example, the location environment information of the wireless device 520 and the local information of the computing device can be time-stamp before being uploaded to the cloud system 510. The cloud system can bind the computing device 540 with the wireless device 530 by time correlating features of the location detection information and sensed information of the computing device 540 with location detection information and sensed information of the wireless device 530.
For at least some embodiments, the cloud system 510 can further its ability to bind the computing device 540 with the wireless device 530 by causing or instructing a user to adaptively control changes of the environment (shown in
Once the binding of the computing device 540 with the wireless device 530 has occurred, an authenticated user 145 can be bound to the wireless device 530. Once the authenticated user 145 has been bound to the wireless device 530, the wireless device cloud management system allows the authenticated user to control the wireless device.
As previously described, for various embodiments the location environments information includes one or more of WiFi scan, GPS, lat/long information, Bluetooth scan, router information (IP, MAC), sound signature, sensed image, etc. Further, as previously described, other local environment information can include, for example, a picture taken by either the wireless device, or the computing device. For an embodiment, the picture includes an asset label of the wireless device or the computing device that includes an identifier of the wireless device or the computing device.
For at least some embodiments, the wireless device cloud management system allows the authenticated user to control the wireless device upon receiving the information that indicates that the binding between the wireless device and the computing device has occurred.
At least some embodiments further include preconfiguring the wireless device with credentials before the cloud system receives the local environment information from the device. At least some embodiments further include connecting the wireless device to a network of the cloud system. For at least some embodiments, connecting the wireless device to a network of the cloud system includes automatically requesting association, by the wireless device, to a router, receiving, by the cloud system, an authentication request from the router, wherein the router received the authentication request from the wireless device, returning, by the cloud system, a response to the authentication request to the router, wherein the response includes internet domains and connection bandwidths the wireless device is allowed to use, and preconfiguring the cloud system with the credentials that are also preconfigured in the wireless device.
At least some embodiments further include adaptively changing an environment local to the computing device, and the cloud system utilizing the adaptive change in the local environment of the computing device while comparing the local environment information of the wireless device with the local information of the computing device.
At least some embodiments further include adaptively changing an environment local to the wireless device, and the cloud system utilizing the adaptive change in the local environment of the wireless device while comparing the local environment information of the wireless device with the local information of the computing device.
For example, for an embodiment, the wireless device transmits a unique wireless signal, and the computing device senses that unique wireless signal to determine that the wireless device and the computing device are in proximity. As another example, for an embodiment, the computing device transmits an audio, and the wireless device receives that audio signal. The cloud system correlates the audio signal and the timing of the audio signal to determine that the wireless device and the computing device are in proximity. As another example, for an embodiment, the computing device give instructions to a user to take an action (clapping hands, pressing a button, or turning on/off a switch, for example). The wireless device senses the action and reports that information back to the cloud service. The cloud service then correlates the signals to determine that the wireless device and the computing device are in proximity.
At least some embodiments, the local environment information from the wireless device includes at least localization information. For an embodiment, the localization information includes GPS information. For an embodiment, the localization information includes latitude, and/or longitude information. For an embodiment, the localization information includes a WiFi Scan—which can be used to estimate location.
At least some embodiments, the local environment information from the wireless device includes at least sensed information. (For at least some embodiments, the GPS and WiFi scan information could be considered sensed information as well. Other sensed information can be used instead of, or to supplement the localization information).
For at least some embodiments, comparing the local environment information of the wireless device with the local information of the computing device further comprises time correlating at least one of sensing or reporting of the local environment information of the wireless device and the local information of the computing device.
In this case Device #1 may try to join Router Set A or Router Set C, but will only be approved to join Router Set A. This configuration can be dynamically changed in the Cloud System to update the network configurations on the devices, and to update which Router Sets the devices are approved to connect to. For example the configuration above may be updated as shown by Table 2 of
The parties involved in operating the system includes the User (the person who owns the access point (router) and the connected device), the ISP (internet service provider, which provides connectivity services to the user), the connected device manufacturer (which manufactures the connected device and associated cloud software), and the FDC operator.
As previously described, for an embodiment, the router is one of a plurality of routers that the wireless device is operable to attempt to associate with, and wherein the plurality of routers that wireless device is operable to associate with is adaptively updated at the wireless device.
As previously described, for an embodiment, the router is one of a plurality of routers that the wireless device is allowed to authenticate against, and wherein the plurality of routers that the wireless device is allowed to authenticate against is adaptively updated in the cloud system.
As previously described, an embodiment further includes preconfiguring the internet domains and the connection bandwidths into the cloud system.
As previously described, for an embodiment, the credentials comprise a pre-shared key or a digital certificate. As previously described, for an embodiment the credentials are stored on non-volatile memory.
As previously described, for an embodiment the connection bandwidths includes at least one of upstream bandwidth, downstream bandwidth, total time on network or aggregate bandwidth over a period of time. As previously described, for an embodiment, the connection bandwidths is adaptively adjusted.
As previously described, for an embodiment, the cloud system is preconfigured to accept authentication requests from the router.
As previously described, for an embodiment, the router is configured to send the authentication request to the cloud system.
An embodiment includes a program storage device readable by a machine of a cloud system, tangibly embodying a non-transitory program of instructions that when executed by the machine of the cloud system cause the machine to perform a method of connecting a wireless device to a network. For an embodiment, the method includes receiving, by a cloud system, an authentication request from a router, wherein the router received the authentication request from the wireless device, wherein the authentication request was automatically requested by the wireless device, and returning, by the cloud system, a response to the authentication request to the router, wherein the response includes internet domains and connection bandwidths the wireless device is allowed to use.
For an embodiment, the router is one of a plurality of routers that the wireless device is operable to attempt to associate with, and wherein the plurality of routers that wireless device is operable to associate with is adaptively updated at the wireless device. For an embodiment, the router is one of a plurality of routers that the wireless device is allowed to authenticate against, and wherein the plurality of routers that the wireless device is allowed to authenticate against is adaptively updated in the cloud system.
Although specific embodiments have been described and illustrated, the embodiments are not to be limited to the specific forms or arrangements of parts so described and illustrated.
This patent application is a continuation-in-part of U.S. patent application Ser. No. 14/800,980, filed Jul. 16, 2015 which claims priority to U.S. Provisional Patent Application No. 62/025,750, filed Jul. 17, 2014, entitled “Method and System for Federated Device Cloud”, further this patent application claims priority to U.S. Provisional Patent Application No. 62/079,501, filed Nov. 14, 2014, which are all incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5734718 | Prafullchandra | Mar 1998 | A |
| 6163794 | Lange et al. | Dec 2000 | A |
| 6839733 | Lange et al. | Jan 2005 | B1 |
| 7117359 | Wood et al. | Oct 2006 | B2 |
| 7155305 | Hayes | Dec 2006 | B2 |
| 7240211 | Hillhouse | Jul 2007 | B2 |
| 7379778 | Hayes | May 2008 | B2 |
| 7484008 | Gelvin | Jan 2009 | B1 |
| 7496953 | Andreev et al. | Feb 2009 | B2 |
| 7539862 | Edgett et al. | May 2009 | B2 |
| 7574496 | McCrory et al. | Aug 2009 | B2 |
| 7891004 | Gelvin | Feb 2011 | B1 |
| 7949752 | Lange et al. | May 2011 | B2 |
| 7958352 | Edgett et al. | Jun 2011 | B2 |
| 7958547 | Andreev et al. | Jun 2011 | B2 |
| 8290163 | Chang et al. | Oct 2012 | B2 |
| 8326914 | Lange et al. | Dec 2012 | B2 |
| 8502996 | St. Jacques, Jr. et al. | Aug 2013 | B2 |
| 8539247 | McGrew et al. | Sep 2013 | B2 |
| 8584221 | Mazur et al. | Nov 2013 | B2 |
| 8607330 | Childress et al. | Dec 2013 | B2 |
| 8627416 | Keeler | Jan 2014 | B2 |
| 8689297 | Pasquero et al. | Apr 2014 | B2 |
| 8743778 | Gordon et al. | Jun 2014 | B2 |
| 8769642 | O'Neill et al. | Jul 2014 | B1 |
| 8819851 | Johansson | Aug 2014 | B1 |
| 8875261 | Delia et al. | Oct 2014 | B2 |
| 8909928 | Ahmad et al. | Dec 2014 | B2 |
| 8955080 | Brunswig et al. | Feb 2015 | B2 |
| 8955082 | Mazur et al. | Feb 2015 | B2 |
| 8984589 | Liu | Mar 2015 | B2 |
| 9009815 | Pieczul et al. | Apr 2015 | B2 |
| 9043458 | Balaji et al. | May 2015 | B2 |
| 9053310 | Oberheide et al. | Jun 2015 | B2 |
| 9064278 | Fan et al. | Jun 2015 | B2 |
| 9077703 | Goshen et al. | Jul 2015 | B1 |
| 9088556 | Truskovsky et al. | Jul 2015 | B2 |
| 9088627 | Nelson et al. | Jul 2015 | B2 |
| 9118662 | Corrion | Aug 2015 | B2 |
| 9167053 | Marmolejo-Meillon et al. | Oct 2015 | B2 |
| 9191874 | Marmolejo-Meillon et al. | Nov 2015 | B2 |
| 9231981 | Delia et al. | Jan 2016 | B2 |
| 9256722 | Saxman et al. | Feb 2016 | B2 |
| 9270654 | Marmolejo-Meillon et al. | Feb 2016 | B2 |
| 9332018 | Liebl, III et al. | May 2016 | B2 |
| 9332069 | Aahlad et al. | May 2016 | B2 |
| 9332579 | Scherer | May 2016 | B2 |
| 9356962 | Ilieva et al. | May 2016 | B2 |
| 9378601 | Ricci | Jun 2016 | B2 |
| 9384339 | Griffin et al. | Jul 2016 | B2 |
| 9397990 | Taly et al. | Jul 2016 | B1 |
| 9418257 | Wassingbo | Aug 2016 | B2 |
| 9420045 | Marmolejo-Meillon et al. | Aug 2016 | B2 |
| 9426653 | Becker | Aug 2016 | B2 |
| 9445146 | Fan et al. | Sep 2016 | B2 |
| 9451464 | Fan et al. | Sep 2016 | B2 |
| 9454656 | Oberheide et al. | Sep 2016 | B2 |
| 9479503 | Griffin et al. | Oct 2016 | B2 |
| 9494694 | Dong | Nov 2016 | B1 |
| 9497187 | Griffith et al. | Nov 2016 | B2 |
| 9537857 | Koved et al. | Jan 2017 | B1 |
| 9563413 | Chan et al. | Feb 2017 | B2 |
| 9584507 | Koved et al. | Feb 2017 | B1 |
| 9602503 | Saxman et al. | Mar 2017 | B2 |
| 9628472 | Koved et al. | Apr 2017 | B1 |
| 9667710 | Wilbur | May 2017 | B2 |
| 9672071 | Gerganov | Jun 2017 | B2 |
| 9686682 | Kim et al. | Jun 2017 | B2 |
| 9705878 | Havercan | Jul 2017 | B2 |
| 9712513 | Trevathan et al. | Jul 2017 | B2 |
| 9713003 | Kim et al. | Jul 2017 | B2 |
| 9742750 | Obasanjo et al. | Aug 2017 | B2 |
| 9742763 | Neuman et al. | Aug 2017 | B2 |
| 9773051 | Smith | Sep 2017 | B2 |
| 9779404 | Spencer, II | Oct 2017 | B2 |
| 20030101359 | Aschen et al. | May 2003 | A1 |
| 20030105810 | McCrory et al. | Jun 2003 | A1 |
| 20030191949 | Odagawa | Oct 2003 | A1 |
| 20040250118 | Andreev et al. | Dec 2004 | A1 |
| 20050159823 | Hayes | Jul 2005 | A1 |
| 20050226423 | Li et al. | Oct 2005 | A1 |
| 20050228874 | Edgett et al. | Oct 2005 | A1 |
| 20050268330 | Di Rienzo | Dec 2005 | A1 |
| 20060191005 | Muhamed et al. | Aug 2006 | A1 |
| 20060259183 | Hayes | Nov 2006 | A1 |
| 20060259184 | Hayes | Nov 2006 | A1 |
| 20070011066 | Steeves | Jan 2007 | A1 |
| 20070174901 | Chang et al. | Jul 2007 | A1 |
| 20080159536 | Chang et al. | Jul 2008 | A1 |
| 20080189774 | Ansari | Aug 2008 | A1 |
| 20080271123 | Ollis | Oct 2008 | A1 |
| 20090126000 | Andreev et al. | May 2009 | A1 |
| 20090150525 | Edgett et al. | Jun 2009 | A1 |
| 20090320098 | Roberts | Dec 2009 | A1 |
| 20100100948 | Delia et al. | Apr 2010 | A1 |
| 20100127854 | Helvick | May 2010 | A1 |
| 20100217837 | Ansari | Aug 2010 | A1 |
| 20110029782 | Havercan | Feb 2011 | A1 |
| 20110040870 | Wynn et al. | Feb 2011 | A1 |
| 20110047603 | Gordon et al. | Feb 2011 | A1 |
| 20110099616 | Mazur et al. | Apr 2011 | A1 |
| 20110225648 | Channakeshava | Sep 2011 | A1 |
| 20110265147 | Liu | Oct 2011 | A1 |
| 20110313922 | Ben Ayed | Dec 2011 | A1 |
| 20110314294 | McGrew et al. | Dec 2011 | A1 |
| 20120060213 | Childress et al. | Mar 2012 | A1 |
| 20120131653 | Pasquero et al. | May 2012 | A1 |
| 20120173356 | Fan et al. | Jul 2012 | A1 |
| 20120230305 | Barbu et al. | Sep 2012 | A1 |
| 20120260320 | Keeler | Oct 2012 | A1 |
| 20120302219 | Vang | Nov 2012 | A1 |
| 20130007520 | Giammarresi | Jan 2013 | A1 |
| 20130013767 | Stober et al. | Jan 2013 | A1 |
| 20130046982 | Suh et al. | Feb 2013 | A1 |
| 20130097306 | Dhunay | Apr 2013 | A1 |
| 20130269020 | Griffin et al. | Oct 2013 | A1 |
| 20130339489 | Katara | Dec 2013 | A1 |
| 20140026193 | Saxman et al. | Jan 2014 | A1 |
| 20140075514 | Prasad | Mar 2014 | A1 |
| 20140108019 | Ehsani | Apr 2014 | A1 |
| 20140137261 | Chen et al. | May 2014 | A1 |
| 20140165150 | Brunswig et al. | Jun 2014 | A1 |
| 20140172947 | Ghai et al. | Jun 2014 | A1 |
| 20140181948 | Mazur et al. | Jun 2014 | A1 |
| 20140189004 | Aahlad et al. | Jul 2014 | A1 |
| 20140201517 | Corrion | Jul 2014 | A1 |
| 20140282939 | Pieczul et al. | Sep 2014 | A1 |
| 20140289195 | Chan et al. | Sep 2014 | A1 |
| 20140289391 | Balaji et al. | Sep 2014 | A1 |
| 20140306833 | Ricci | Oct 2014 | A1 |
| 20140325591 | Delia et al. | Oct 2014 | A1 |
| 20140337291 | Dorman et al. | Nov 2014 | A1 |
| 20140337937 | Truskovsky et al. | Nov 2014 | A1 |
| 20140373096 | Obasanjo et al. | Dec 2014 | A1 |
| 20140380453 | Alonso Cebrian et al. | Dec 2014 | A1 |
| 20150007273 | Lin | Jan 2015 | A1 |
| 20150024710 | Becker | Jan 2015 | A1 |
| 20150046990 | Oberheide et al. | Feb 2015 | A1 |
| 20150074582 | Shearer | Mar 2015 | A1 |
| 20150074670 | Gerganov | Mar 2015 | A1 |
| 20150074743 | Ilieva et al. | Mar 2015 | A1 |
| 20150089597 | Srinivasan et al. | Mar 2015 | A1 |
| 20150095999 | Toth | Apr 2015 | A1 |
| 20150142947 | Dyba et al. | May 2015 | A1 |
| 20150143486 | Hartmann | May 2015 | A1 |
| 20150195099 | Imes | Jul 2015 | A1 |
| 20150237031 | Neuman et al. | Aug 2015 | A1 |
| 20150261782 | McFerrin et al. | Sep 2015 | A1 |
| 20150288694 | Liebl, III et al. | Oct 2015 | A1 |
| 20150312041 | Choi | Oct 2015 | A1 |
| 20150317151 | Falcy et al. | Nov 2015 | A1 |
| 20150356328 | Wassingbo | Dec 2015 | A1 |
| 20160021538 | Conant et al. | Jan 2016 | A1 |
| 20160021607 | Conant | Jan 2016 | A1 |
| 20160024823 | McAndrew | Jan 2016 | A1 |
| 20160044032 | Kim et al. | Feb 2016 | A1 |
| 20160063491 | Steeves | Mar 2016 | A1 |
| 20160066183 | Conant | Mar 2016 | A1 |
| 20160080343 | Robinton | Mar 2016 | A1 |
| 20160081133 | Kim et al. | Mar 2016 | A1 |
| 20160087966 | Saxman et al. | Mar 2016 | A1 |
| 20160088478 | Kim et al. | Mar 2016 | A1 |
| 20160112434 | Chung | Apr 2016 | A1 |
| 20160173487 | Griffith et al. | Jun 2016 | A1 |
| 20160212113 | Banerjee | Jul 2016 | A1 |
| 20160212141 | Banerjee | Jul 2016 | A1 |
| 20160217638 | Child | Jul 2016 | A1 |
| 20160219044 | Karunakaran et al. | Jul 2016 | A1 |
| 20160219319 | Servignat et al. | Jul 2016 | A1 |
| 20160227371 | Wang | Aug 2016 | A1 |
| 20160234186 | Leblond et al. | Aug 2016 | A1 |
| 20160249395 | Logue | Aug 2016 | A1 |
| 20160255080 | Griffin et al. | Sep 2016 | A1 |
| 20160269398 | Chhabra et al. | Sep 2016 | A1 |
| 20160275731 | Prasad | Sep 2016 | A1 |
| 20160277374 | Reid et al. | Sep 2016 | A1 |
| 20160295364 | Zakaria | Oct 2016 | A1 |
| 20160308954 | Wilbur | Oct 2016 | A1 |
| 20160323257 | Kang et al. | Nov 2016 | A1 |
| 20160337334 | Murr | Nov 2016 | A1 |
| 20160337354 | Smadja | Nov 2016 | A1 |
| 20160344862 | Tucker | Nov 2016 | A1 |
| 20160359837 | Krstic et al. | Dec 2016 | A1 |
| 20160359847 | Griffith et al. | Dec 2016 | A1 |
| 20160359863 | Krstic et al. | Dec 2016 | A1 |
| 20160366233 | Le et al. | Dec 2016 | A1 |
| 20160381023 | Dulce et al. | Dec 2016 | A1 |
| 20170005820 | Zimmerman et al. | Jan 2017 | A1 |
| 20170026369 | Hao et al. | Jan 2017 | A1 |
| 20170026380 | Liebl, III et al. | Jan 2017 | A1 |
| 20170026465 | Aahlad et al. | Jan 2017 | A1 |
| 20170034142 | Camenisch et al. | Feb 2017 | A1 |
| 20170041316 | Setchell | Feb 2017 | A1 |
| 20170048172 | Chavez | Feb 2017 | A1 |
| 20170070504 | Ramachandran et al. | Mar 2017 | A1 |
| 20170078398 | Haidar | Mar 2017 | A1 |
| 20170085575 | Wynn et al. | Mar 2017 | A1 |
| 20170093587 | Glisson | Mar 2017 | A1 |
| 20170094706 | Kim et al. | Mar 2017 | A1 |
| 20170099281 | Trevathan et al. | Apr 2017 | A1 |
| 20170104738 | Brown | Apr 2017 | A1 |
| 20170111335 | Hibbert et al. | Apr 2017 | A1 |
| 20170150535 | Wynn et al. | May 2017 | A1 |
| 20170169422 | Ye et al. | Jun 2017 | A1 |
| 20170171747 | Britt et al. | Jun 2017 | A1 |
| 20170180347 | Koved et al. | Jun 2017 | A1 |
| 20170180530 | Tucker | Jun 2017 | A1 |
| 20170195331 | Wu et al. | Jul 2017 | A1 |
| 20170195332 | Wu et al. | Jul 2017 | A1 |
| 20170200001 | Bhullar et al. | Jul 2017 | A1 |
| 20170213206 | Shearer | Jul 2017 | A1 |
| 20170213212 | Dicker et al. | Jul 2017 | A1 |
| 20170213305 | Smith et al. | Jul 2017 | A1 |
| 20170257426 | Wilbur | Sep 2017 | A1 |
| 20170272316 | Johnson et al. | Sep 2017 | A1 |
| 20170277872 | Mercury et al. | Sep 2017 | A1 |
| 20170279614 | Mercury et al. | Sep 2017 | A1 |
| 20170279793 | Trevathan et al. | Sep 2017 | A1 |
| 20170288872 | Lu et al. | Oct 2017 | A1 |
| 20170295065 | Jain et al. | Oct 2017 | A1 |
| 20170324728 | Gilpin et al. | Nov 2017 | A1 |
| 20170337813 | Taylor | Nov 2017 | A1 |
| 20170339065 | Li et al. | Nov 2017 | A1 |
| 20170339436 | Buono et al. | Nov 2017 | A1 |
| 20170357936 | Byington et al. | Dec 2017 | A1 |
| 20170372091 | Lacey | Dec 2017 | A1 |
| 20180191867 | Siebel | Jul 2018 | A1 |
| Entry |
|---|
| Soumalainen, Smartphone Assisted Security Pairings for the Internet of Things, May 14, 2014, IEEE, 4th International Conference on Wireless Communications, Vehicular Technology, Information Theory and Aerospace & Electronic Systems (VITAE) (Year: 2014). |
| Number | Date | Country | |
|---|---|---|---|
| 20160021538 A1 | Jan 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62079501 | Nov 2014 | US | |
| 62025750 | Jul 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14800980 | Jul 2015 | US |
| Child | 14871525 | US |
