Controlled connection of a wireless device to a network

Information

  • Patent Grant
  • 10856171
  • Patent Number
    10,856,171
  • Date Filed
    Wednesday, June 5, 2019
    5 years ago
  • Date Issued
    Tuesday, December 1, 2020
    3 years ago
Abstract
Methods, systems and apparatus for connecting a wireless device to a network are disclosed. One method includes automatically associating, by the wireless device, to a cloud system through a router, retrieving, by the wireless device, after automatically associating, a list of approved networks from a cloud service of the cloud system, wherein the list of approved networks includes a prioritization of the approved networks, scanning, by the wireless device, a local wireless environment, comparing, by the wireless device, a list of available networks advertised from nearby routers from the scan of a local wireless environment with the list of approved networks when the wireless device is looking for networks to join, and choosing, by the wireless device, an available network from the list of available networks advertised based at least in part on the comparing and the prioritization of the approved networks.
Description
FIELD OF THE DESCRIBED EMBODIMENTS

The described embodiments relate generally to wireless networking. More particularly, the described embodiments relate to methods, systems and apparatuses for controlling a connection of a wireless device to a network.


BACKGROUND

Binding and provisioning devices to a network can be technically complicated. Methods like WiFi Protected Setup were developed to address this challenge, but fail to simplify the process sufficiently to allow seamless connectivity for connected devices.


It is desirable to have a system, method and apparatus for controlling a connection of a wireless device to a network that provides binding and provisioning of the wireless device to the network.


SUMMARY

An embodiment includes a method for connecting a wireless device to a network. The method includes automatically associating, by the wireless device, to a cloud system through a router, retrieving, by the wireless device, after automatically associating, a list of approved networks from a cloud service of the cloud system, wherein the list of approved networks includes a prioritization of the approved networks, scanning, by the wireless device, a local wireless environment, comparing, by the wireless device, a list of available networks advertised from nearby routers from the scan of a local wireless environment with the list of approved networks when the wireless device is looking for networks to join, and choosing, by the wireless device, an available network from the list of available networks advertised based at least in part on the comparing and the prioritization of the approved networks.


Another embodiment includes a wireless device. The wireless device includes a wireless interface, and a controller. The controller operative to automatically associate to a cloud system through a router, retrieve after automatically associating, a list of approved networks from a cloud service of the cloud system, wherein the list of approved networks includes a prioritization of the approved networks, scan a local wireless environment, compare a list of available networks advertised from nearby routers from the scan of a local wireless environment with the list of approved networks when the wireless device is looking for networks to join, and choose an available network from the list of available networks advertised based at least in part on the comparing and the prioritization of the approved networks.


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.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 shows a system for connecting a wireless device to a network, according to an embodiment.



FIG. 2 shows another system for connecting a wireless device to a network, according to an embodiment.



FIG. 3 shows tables that depicts wireless device and router configurations, according to an embodiment.



FIG. 4 is a flow chart that includes steps of an example of a method of connecting a wireless device to a network, according to an embodiment.





DETAILED DESCRIPTION

The described embodiments include systems, methods, and apparatuses for connecting a wireless device to a network. At least some embodiments provide for simplification of provisioning and onboarding of the wireless device through coordination of the device manufacturer and the network equipment manufacturer.


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.



FIG. 1 shows a system for connecting a wireless device 110 to a network, according to an embodiment. For an embodiment, the wireless device 110 automatically requests association to a router 130. Further, for at least some embodiments, a cloud system 140 receives an authentication request from the router 130, wherein the router 130 received the authentication request from the wireless device 110. Further, for at least some embodiments, the cloud system 140, returns a response to the authentication request to the router 130, wherein the response includes internet domains and connection bandwidths the wireless device is allowed to use, wherein the wireless device has been preconfigured with credentials that are also preconfigured into the cloud system. As shown, for an embodiment, the cloud system 140 is connected to the router 130 through, for example, the internet 130.


For at least some embodiments, the cloud system 140 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 140 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 130 redirecting the wireless device 110 to a captive portal, which resides on a server separate from the cloud system 140, and which negotiates the authorization and authentication process on behalf of the router 130 before passing the connection bandwidths and internet domain parameters back to the router 130.


For an embodiment, the authentication process include the router 130 implementing firewall rules on the router 130 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 130 implementing bandwidth limitations on the device connection which prevents the wireless device 110 from communicating outside the range of these bandwidth limitations.


At least some embodiments include a manufacturer of the wireless device 110 registering the wireless device 110 with the cloud system 140, and agreeing upon a credential for the wireless device 110. 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 110.


Further, for an embodiment, the manufacturer also specifies the internet domains the wireless device 140 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 140 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 140 is connected to the router 130 via a proxy cloud system. The proxy cloud system in this case routes the authentication requests to the cloud system 140 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 110, or other variables.


For at least some embodiments, the manufacturer puts the credential and the network configuration on the wireless device 110 when the wireless device 110 is manufactured. The network configuration defines the set of networks the wireless device 110 should try to join. For an embodiment, the network configuration is updated periodically, and the wireless device 110 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 110 is powered up (power turned on) by a user, the wireless device 110 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 130) the wireless device 110 is attempting to connect to queries the cloud service (of the cloud system 140) to authenticate the wireless device 110 and authorize the wireless device 110 to join the network. For an embodiment, the cloud service (of the cloud system 140) sends back to the router 130 allowed parameters of the connection. For an embodiment, the allowed parameters include the domains the wireless device 110 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 110 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 110 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 140. 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 140 with the real time status of the wireless device 110. 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.



FIG. 2 shows another system for connecting a wireless device to a network, according to an embodiment. For an embodiment the router 130 is one of a plurality of routers 232, 234, 236 that the wireless device 110 is operable to attempt to associate with, and wherein the plurality of routers that wireless device 110 is operable to associate with is adaptively updated at the wireless device.


For at least some embodiments, the wireless device 110 periodically retrieves a list of approved networks from a cloud service of the cloud system 140, wherein the list of approved networks includes a prioritization of the approved networks. When the wireless device 110 looks for networks to join, the wireless device 110 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 140, the wireless device 110 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 130 is one of a plurality of routers 130, 232, 234, 236 that the wireless device 110 is allowed to authenticate against, and wherein the plurality of routers 130, 232, 234, 236 that the wireless device 110 is allowed to authenticate against is adaptively updated in the cloud system 140.


For at least some embodiments, the cloud system 140 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 140 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 140. 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 140, 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 110 or network performance, as monitored by the wireless device 110 or the cloud system 140.


For at least some embodiments, the internet domains and connection bandwidth parameters are updated at any time in the cloud system 140. When a wireless device attempts to associate with a router, and the router sends the authentication request to the cloud system 140, the cloud system 140 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 140 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 140 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 140. For an embodiment, the deployed routers are configured to send authentication requests to the cloud system 140, 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 140.


For at least some embodiments, the cloud service (of the cloud system 140) 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.



FIG. 3 shows tables that depicts wireless device and router configurations, according to an embodiment. As shown in Table 1 of FIG. 3, there may be Devices (#1, #2, and #3) and three sets of Routers (set A, set B, and set C). The Devices and Routers may be configured as shown in the table 1 of FIG. 3.


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 FIG. 3, wherein Device #1 is allowed to join Router Set C.


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.



FIG. 4 is a flow chart that includes steps of an example of a method of connecting a wireless device to a network, according to an embodiment. A first step 410 includes preconfiguring the wireless device with credentials. A second step 420 includes automatically requesting association, by the wireless device, to a router. A third step 430 includes receiving, by a cloud system, an authentication request from the router, wherein the router received the authentication request from the wireless device. A fourth step 440 includes 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. A fifth step 450 includes preconfiguring the cloud system with the credentials that are also preconfigured in the wireless device.


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.

Claims
  • 1. A method for connecting a wireless device to a network, comprising: automatically associating, by the wireless device, to a cloud system through a router;retrieving, by the wireless device, after automatically associating, a list of approved networks from a cloud service of the cloud system, wherein the list of approved networks includes a prioritization of the approved networks;scanning, by the wireless device, a local wireless environment;comparing, by the wireless device, a list of available networks advertised from nearby routers from the scan of a local wireless environment with the list of approved networks when the wireless device is looking for networks to join;choosing, by the wireless device, an available network from the list of available networks advertised based at least in part on the comparing and the prioritization of the approved networks; andprioritizing, by the wireless device, 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.
  • 2. The method of claim 1, wherein choosing, by the wireless device, the available network comprises choosing a highest priority network that is available to be joined.
  • 3. The method of claim 1, wherein after automatically associating with the cloud system, the wireless device receives connection bandwidths the wireless device is allowed to use, wherein the connection bandwidths includes at least one of upstream bandwidth, downstream bandwidth, total time on network or aggregate bandwidth over a period of time.
  • 4. The method of claim 1, wherein after automatically associating with the cloud system, the wireless device receives connection bandwidths the wireless device is allowed to use, wherein the connection bandwidths are adaptively adjusted.
  • 5. The method of claim 4, wherein the connection bandwidths are adaptively adjusted based on one or more of business agreements, available bandwidth, a service level agreed with a device manufacturer, a service level agreed with a router operator, a service level agreed with an interne service subscriber, a time of day, an amount of data the wireless device has already used, historical data usage of the wireless device.
  • 6. The method of claim 1, wherein 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.
  • 7. The method of claim 1, wherein 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.
  • 8. A wireless device, comprising: a wireless interface;a controller, the controller operative to:automatically associate to a cloud system through a router;retrieve after automatically associating, a list of approved networks from a cloud service of the cloud system, wherein the list of approved networks includes a prioritization of the approved networks;scan a local wireless environment;compare a list of available networks advertised from nearby routers from the scan of a local wireless environment with the list of approved networks when the wireless device is looking for networks to join;choose an available network from the list of available networks advertised based at least in part on the comparing and the prioritization of the approved networks; andprioritize 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.
  • 9. The wireless device of claim 8, wherein choosing the available network comprises choosing a highest priority network that is available to be joined.
  • 10. The wireless device of claim 8, wherein the response further includes connection bandwidths the wireless device is allowed to use, wherein the connection bandwidths includes at least one of upstream bandwidth, downstream bandwidth, total time on network or aggregate bandwidth over a period of time.
  • 11. The wireless device of claim 8, wherein the response further includes connection bandwidths the wireless device is allowed to use, wherein the connection bandwidths are adaptively adjusted.
  • 12. The wireless device of claim 11, wherein the connection bandwidths are adaptively adjusted based on one or more of business agreements, available bandwidth, a service level agreed with a device manufacturer, a service level agreed with a router operator, a service level agreed with an internet service subscriber, a time of day, an amount of data the wireless device has already used, historical data usage of the wireless device.
  • 13. The wireless device of claim 8, wherein 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.
  • 14. The wireless device of claim 8, wherein 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.
  • 15. A method for connecting a wireless device to a network, comprising: automatically associating, by the wireless device, to a cloud system through a router;retrieving, by the wireless device, after automatically associating, a list of approved networks from a cloud service of the cloud system, wherein the list of approved networks includes a prioritization of the approved networks;scanning, by the wireless device, a local wireless environment;comparing, by the wireless device, a list of available networks advertised from nearby routers from the scan of a local wireless environment with the list of approved networks when the wireless device is looking for networks to join;choosing, by the wireless device, an available network from the list of available networks advertised based at least in part on the comparing and the prioritization of the approved networks;selecting, by the wireless device, to send at least some data on a secure personal network, and send at least some other data on the authorized network;dynamically partitioning, by the wireless device, 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.
  • 16. A wireless device, comprising: a wireless interface;a controller, the controller operative to:automatically associate to a cloud system through a router;retrieve after automatically associating, a list of approved networks from a cloud service of the cloud system, wherein the list of approved networks includes a prioritization of the approved networks;scan a local wireless environment;compare a list of available networks advertised from nearby routers from the scan of a local wireless environment with the list of approved networks when the wireless device is looking for networks to join;choose an available network from the list of available networks advertised based at least in part on the comparing and the prioritization of the approved networks;select 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; anddynamically partition between the sending of the at least some data on the secure personal network, and the send the at least some other data on the network authorized by the cloud service of the cloud system.
RELATED APPLICATIONS

This patent application is a continuation 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,” which are incorporated herein by reference.

US Referenced Citations (276)
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 et al. Dec 2006 B2
7240211 Hillhouse Jul 2007 B2
7379778 Hayes et al. May 2008 B2
7406596 Tararukhina et al. Jul 2008 B2
7484008 Gelvin et al. Jan 2009 B1
7496953 Andreev et al. Feb 2009 B2
7539862 Edgett et al. May 2009 B2
7558564 Wesby Jul 2009 B2
7567510 Gai et al. Jul 2009 B2
7574496 McCrory et al. Aug 2009 B2
7613927 Holovacs Nov 2009 B2
7891004 Gelvin et al. Feb 2011 B1
7949752 Lange et al. May 2011 B2
7958352 Edgett et al. Jun 2011 B2
7958547 Andreev et al. Jun 2011 B2
8234701 Cheung et al. Jul 2012 B2
8290163 Chang et al. Oct 2012 B2
8326914 Lange et al. Dec 2012 B2
8443089 Mosleh et al. May 2013 B2
8457622 Wesby Jun 2013 B2
8502996 St. Jacques, Jr. et al. Aug 2013 B2
8539247 McGrew et al. Sep 2013 B2
8579189 Gazdzinski Nov 2013 B2
8584221 Mazur et al. Nov 2013 B2
8607330 Childress et al. Dec 2013 B2
8622286 Gazdzinski Jan 2014 B2
8627416 Keeler et al. Jan 2014 B2
8640944 Gazdzinski Feb 2014 B1
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
8869236 Tonogai et al. Oct 2014 B1
8875261 Delia et al. Oct 2014 B2
8880054 Wesby Nov 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
9137108 Rezvani et al. Sep 2015 B2
9167053 Marmolejo-Meillon et al. Oct 2015 B2
9172606 Rezvani 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
9264905 Ferguson-Jarnes 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 et al. 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 et al. Aug 2016 B2
9445146 Fan et al. Sep 2016 B2
9454656 Oberheide et al. Sep 2016 B2
9479503 Griffin et al. Oct 2016 B2
9494694 Dong et al. 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 et al. 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
9830589 Xing Nov 2017 B2
9843624 Taaghol Dec 2017 B1
9847964 Logue Dec 2017 B2
10070313 Schrecker Sep 2018 B2
10102510 Yau et al. Oct 2018 B2
10143053 Wilson et al. Nov 2018 B1
10154409 Conant Dec 2018 B2
10181985 Passaglia et al. Jan 2019 B1
20030101359 Aschen et al. May 2003 A1
20030105810 McCrory et al. Jun 2003 A1
20030191949 Odagawa Oct 2003 A1
20040122687 Creamer et al. Jun 2004 A1
20040250118 Andreev et al. Dec 2004 A1
20050159823 Hayes et al. 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 et al. Nov 2006 A1
20060259184 Hayes et al. Nov 2006 A1
20070174901 Chang et al. Jul 2007 A1
20080159536 Chang et al. Jul 2008 A1
20080189774 Ansari et al. Aug 2008 A1
20080198866 Shahar Aug 2008 A1
20080271123 Ollis et al. Oct 2008 A1
20090126000 Andreev et al. May 2009 A1
20090150525 Edgett et al. Jun 2009 A1
20090320098 Roberts et al. Dec 2009 A1
20100100948 Delia et al. Apr 2010 A1
20100127854 Helvick et al. May 2010 A1
20100217837 Ansari et al. 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
20110138048 Dawson Jun 2011 A1
20110225648 Channakeshava Sep 2011 A1
20110243553 Russell Oct 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
20120110650 Van Biljon et al. May 2012 A1
20120131653 Pasquero et al. May 2012 A1
20120173356 Fan et al. Jul 2012 A1
20120230304 Barbu et al. Sep 2012 A1
20120243686 Wesby Sep 2012 A1
20120260320 Keeler et al. Oct 2012 A1
20120302219 Vang Nov 2012 A1
20120329429 Jabara et al. Dec 2012 A1
20130007520 Giammarresi et al. Jan 2013 A1
20130013767 Stober et al. Jan 2013 A1
20130046982 Suh et al. Feb 2013 A1
20130097306 Dhunay Apr 2013 A1
20130191231 Gazdzinski Jul 2013 A1
20130206835 Gazdzinski Aug 2013 A1
20130268687 Schrecker Oct 2013 A1
20130269020 Griffin et al. Oct 2013 A1
20130311597 Arrouye et al. Nov 2013 A1
20130339489 Katara et al. Dec 2013 A1
20140026193 Saxman et al. Jan 2014 A1
20140068261 Malek et al. Mar 2014 A1
20140075514 Prasad et al. Mar 2014 A1
20140108019 Ehsani et al. Apr 2014 A1
20140137261 Chen et al. May 2014 A1
20140156715 Lee et al. Jun 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
20140375437 Rezvani et al. Dec 2014 A1
20140380453 Alonso Cebrian et al. Dec 2014 A1
20150007273 Lin Jan 2015 A1
20150024710 Becker et al. Jan 2015 A1
20150038074 Buckley Feb 2015 A1
20150046990 Oberheide et al. Feb 2015 A1
20150058406 Rezvani et al. Feb 2015 A1
20150074275 Ashley Mar 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 et al. Jul 2015 A1
20150237031 Neuman et al. Aug 2015 A1
20150244694 Lin et al. Aug 2015 A1
20150261782 McFerrin et al. Sep 2015 A1
20150281955 Zhang Oct 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
20150378658 Mandigo et al. 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 et al. 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
20160105314 Logue Apr 2016 A1
20160112434 Chung et al. Apr 2016 A1
20160173487 Griffith et al. Jun 2016 A1
20160210429 Ortiz et al. Jul 2016 A1
20160212113 Banerjee Jul 2016 A1
20160212141 Banerjee Jul 2016 A1
20160217638 Child et al. Jul 2016 A1
20160219044 Karunakaran et al. Jul 2016 A1
20160219319 Servignat et al. Jul 2016 A1
20160227371 Wang et al. Aug 2016 A1
20160234186 Leblond et al. Aug 2016 A1
20160249395 Logue et al. Aug 2016 A1
20160255080 Griffin et al. Sep 2016 A1
20160261411 Yau et al. Sep 2016 A1
20160269398 Chhabra et al. Sep 2016 A1
20160275731 Prasad et al. Sep 2016 A1
20160277374 Reid et al. Sep 2016 A1
20160295364 Zakaria Oct 2016 A1
20160308954 Wilbur et al. 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
20170026902 Roskind 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 et al. 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
20170181054 DeCerbo, Jr. Jun 2017 A1
20170181114 Lu 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
20170243195 Xing Aug 2017 A1
20170257426 Wilbur et al. 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
20180091975 Schrecker Mar 2018 A1
20180191867 Siebel et al. Jul 2018 A1
Non-Patent Literature Citations (1)
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).
Related Publications (1)
Number Date Country
20190289490 A1 Sep 2019 US
Provisional Applications (1)
Number Date Country
62025750 Jul 2014 US
Continuations (1)
Number Date Country
Parent 14800980 Jul 2015 US
Child 16431997 US