Patent Application
20160132031
This relates generally to computer technology, including but not limited to methods and systems for provisioning an electronic device by associating a user account with the electronic device and establishing a secure network connection for the electronic device.
Smart home automation devices are being developed and fielded at such a rapid pace that new devices appear on the market practically every day. Because of the proliferation of low-power wireless network and smart phone technologies, it is not uncommon to find home and business owners in possession of smart home devices such as wireless lights, music systems, door locks, thermostats and alarm systems. And wireless white goods are just over the horizon. Based on current trends, it is expected that the average consumer will own as many as five to ten smart home devices in just a few years.
One issue with this proliferation of devices is that many such smart home devices use different communication protocols (e.g., Z-Wave, ZigBee or Insteon) so devices that use different protocols cannot interoperate seamlessly out of the box. In addition, many such devices are configured with different set-up procedures (sometimes called commissioning or provisioning procedures) depending on one or more of: the type of the device, capabilities of the device (e.g., degree of smartness of the device) and/or the particular communication protocol employed by that device. As a result, owners of these devices often face a confusing experience every time they attempt to configure and/or commission a new device. Furthermore, different devices of the same type (e.g., thermostats) can have different capabilities, so users might not have access to expected or desirable product features for a particular type of device depending on the specific device they purchased.
Therefore, it would be desirable to develop user-friendly solutions to address the above-recited issues associated with smart home devices.
Accordingly, there is a need for methods, systems, devices, and interfaces for emulating advanced functionality on devices. By translating a command for an advanced functionality into sub-commands that, when executed, perform respective constituent functionalities, execution of sub-commands by respective devices can be managed such that the advanced functionality is emulated on a device that does not individually have such capabilities. Advantageously, devices—despite their inherent capability—can emulate advanced functionalities by coordinating and using the capabilities of multiple devices.
In one aspect, in accordance with some implementations, a method is performed at a first device (e.g., a hub device) with one or more processors and memory storing instructions for execution by the one or more processors. The method includes receiving a first command for performing a first functionality on at least a second device, the first functionality comprising a plurality of constituent functionalities, wherein the second device is not configured to execute the first command. The first command is translated into a plurality of sub-commands for execution by respective devices. Each of the plurality of sub-commands, when executed, performs a respective constituent functionality of the plurality of constituent functionalities, and execution of any one of the sub-commands individually does not perform the entire first functionality. The first device manages execution of the plurality of sub-commands by the respective devices, wherein execution of the plurality of sub-commands by the respective devices emulates performance of the first functionality on at least the second device.
In accordance with some implementations, a first device (e.g., a hub device) includes one or more processors, memory, and one or more programs; the one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for performing the operations of the method described above. In accordance with some implementations, a non-transitory computer-readable storage medium has stored therein instructions that, when executed by the first device, cause the electronic device to perform the operations of the method described above. In accordance with some implementations, a device includes means for performing the operations of the method described above.
In another aspect, in accordance with some implementations, a first functionality to be performed on a first device is identified, the first functionality comprising a plurality of constituent functionalities. Respective sets of functionalities are obtained for a plurality of devices including the first device. Two or more devices, of the plurality of devices and including the first device, having respective sets of functionalities that together include the plurality of constituent functionalities are then identified. Furthermore, a plurality of sub-commands is generated, each of the plurality of sub-commands for execution by a corresponding device of the two or more devices. Execution of a respective one of the plurality of sub-commands enables performance of a respective one of the plurality of constituent functionalities, and execution of the plurality of sub-commands emulates performance of the first functionality on at least the first device.
Devices are therefore provided with the ability to emulate advanced functionalities, thereby increasing the effectiveness and user satisfaction with such devices.
For a better understanding of the various described implementations, reference should be made to the Description of Implementations below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
Like reference numerals refer to corresponding parts throughout the several views of the drawings.
Reference will now be made in detail to implementations, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various described implementations. However, it will be apparent to one of ordinary skill in the art that the various described implementations may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the implementations.
It will also be understood that, although the terms first, second, etc. are, in some instances, used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first type of request could be termed a second type of request, and, similarly, a second type of request could be termed a first type of request, without departing from the scope of the various described implementations. The first type of request and the second type of request are both types of requests, but they are not the same type of request.
The terminology used in the description of the various described implementations herein is for the purpose of describing particular implementations only and is not intended to be limiting. As used in the description of the various described implementations and the appended claims, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting” or “in accordance with a determination that,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event]” or “in accordance with a determination that [a stated condition or event] is detected,” depending on the context.
It is to be appreciated that “smart home environments” may refer to smart environments for homes such as a single-family house, but the scope of the present teachings is not so limited. The present teachings are also applicable, without limitation, to duplexes, townhomes, multi-unit apartment buildings, hotels, retail stores, office buildings, industrial buildings, and more generally any living space or work space.
It is also to be appreciated that while the terms user, customer, installer, homeowner, occupant, guest, tenant, landlord, repair person, and the like may be used to refer to the person or persons acting in the context of some particularly situations described herein, these references do not limit the scope of the present teachings with respect to the person or persons who are performing such actions. Thus, for example, the terms user, customer, purchaser, installer, subscriber, and homeowner may often refer to the same person in the case of a single-family residential dwelling, because the head of the household is often the person who makes the purchasing decision, buys the unit, and installs and configures the unit, and is also one of the users of the unit. However, in other scenarios, such as a landlord-tenant environment, the customer may be the landlord with respect to purchasing the unit, the installer may be a local apartment supervisor, a first user may be the tenant, and a second user may again be the landlord with respect to remote control functionality. Importantly, while the identity of the person performing the action may be germane to a particular advantage provided by one or more of the implementations, such identity should not be construed in the descriptions that follow as necessarily limiting the scope of the present teachings to those particular individuals having those particular identities.
The depicted structure 150 includes a plurality of rooms 152, separated at least partly from each other via walls 154. The walls 154 may include interior walls or exterior walls. Each room may further include a floor 156 and a ceiling 158. Devices may be mounted on, integrated with and/or supported by a wall 154, floor 156 or ceiling 158.
In some implementations, the integrated devices of the smart home environment 100 include intelligent, multi-sensing, network-connected devices that integrate seamlessly with each other in a smart home network (e.g., 202
In some implementations, the one or more smart thermostats 102 detect ambient climate characteristics (e.g., temperature and/or humidity) and control a HVAC system 103 accordingly. For example, a respective smart thermostat 102 includes an ambient temperature sensor.
The one or more smart hazard detectors 104 may include thermal radiation sensors directed at respective heat sources (e.g., a stove, oven, other appliances, a fireplace, etc.). For example, a smart hazard detector 104 in a kitchen 153 includes a thermal radiation sensor directed at a stove/oven (e.g., a smart appliance 112). A thermal radiation sensor may determine the temperature of the respective heat source (or a portion thereof) at which it is directed and may provide corresponding blackbody radiation data as output.
The smart doorbell 106 may detect a person's approach to or departure from a location (e.g., an outer door), control doorbell functionality, announce a person's approach or departure via audio or visual means, and/or control settings on a security system (e.g., to activate or deactivate the security system when occupants go and come).
In some implementations, the smart home environment 100 includes one or more intelligent, multi-sensing, network-connected wall switches 108 (hereinafter referred to as “smart wall switches 108”), along with one or more intelligent, multi-sensing, network-connected wall plug interfaces 110 (hereinafter referred to as “smart wall plugs 110”). The smart wall switches 108 may detect ambient lighting conditions, detect room-occupancy states, and control a power and/or dim state of one or more lights. In some instances, smart wall switches 108 may also control a power state or speed of a fan, such as a ceiling fan. The smart wall plugs 110 may detect occupancy of a room or enclosure and control supply of power to one or more wall plugs (e.g., such that power is not supplied to the plug if nobody is at home).
In some implementations, the smart home environment 100 of
In some implementations, the smart home environment 100 includes one or more network-connected cameras 118 that are configured to provide video monitoring and security in the smart home environment 100. The cameras 118 may be used to determine occupancy of the structure 150 and/or particular rooms 152 in the structure 150, and thus may act as occupancy sensors. For example, video captured by the cameras 118 may be processed to identify the presence of an occupant in the structure 150 (e.g., in a particular room 152). Specific individuals may be identified based, for example, on their appearance (e.g., height, face) and/or movement (e.g., their walk/gate). The smart home environment 100 may additionally or alternatively include one or more other occupancy sensors (e.g., the smart doorbell 106, smart doorlocks, touch screens, IR sensors, microphones, ambient light sensors, motion detectors, smart nightlights 170, etc.). In some implementations, the smart home environment 100 includes radio-frequency identification (RFID) readers (e.g., in each room 152 or a portion thereof) that determine occupancy based on RFID tags located on or embedded in occupants. For example, RFID readers may be integrated into the smart hazard detectors 104.
The smart home environment 100 may also include communication with devices outside of the physical home but within a proximate geographical range of the home. For example, the smart home environment 100 may include a pool heater monitor 114 that communicates a current pool temperature to other devices within the smart home environment 100 and/or receives commands for controlling the pool temperature. Similarly, the smart home environment 100 may include an irrigation monitor 116 that communicates information regarding irrigation systems within the smart home environment 100 and/or receives control information for controlling such irrigation systems.
By virtue of network connectivity, one or more of the smart home devices of
As discussed above, users may control smart devices in the smart home environment 100 using a network-connected computer or portable electronic device 166. In some examples, some or all of the occupants (e.g., individuals who live in the home) may register their device 166 with the smart home environment 100. Such registration may be made at a central server to authenticate the occupant and/or the device as being associated with the home and to give permission to the occupant to use the device to control the smart devices in the home. An occupant may use their registered device 166 to remotely control the smart devices of the home, such as when the occupant is at work or on vacation. The occupant may also use their registered device to control the smart devices when the occupant is actually located inside the home, such as when the occupant is sitting on a couch inside the home. It should be appreciated that instead of or in addition to registering devices 166, the smart home environment 100 may make inferences about which individuals live in the home and are therefore occupants and which devices 166 are associated with those individuals. As such, the smart home environment may “learn” who is an occupant and permit the devices 166 associated with those individuals to control the smart devices of the home.
In some implementations, in addition to containing processing and sensing capabilities, devices 102, 104, 106, 108, 110, 112, 114, 116 and/or 118 (collectively referred to as “the smart devices”) are capable of data communications and information sharing with other smart devices, a central server or cloud-computing system, and/or other devices that are network-connected. Data communications may be carried out using any of a variety of custom or standard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) and/or any of a variety of custom or standard wired protocols (e.g., Ethernet, HomePlug, etc.), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
In some implementations, the smart devices serve as wireless or wired repeaters. In some implementations, a first one of the smart devices communicates with a second one of the smart devices via a wireless router. The smart devices may further communicate with each other via a connection (e.g., network interface 160) to a network, such as the Internet 162. Through the Internet 162, the smart devices may communicate with a smart home provider server system 164 (also called a central server system and/or a cloud-computing system herein). The smart home provider server system 164 may be associated with a manufacturer, support entity, or service provider associated with the smart device(s). In some implementations, a user is able to contact customer support using a smart device itself rather than needing to use other communication means, such as a telephone or Internet-connected computer. In some implementations, software updates are automatically sent from the smart home provider server system 164 to smart devices (e.g., when available, when purchased, or at routine intervals).
In some implementations, the network interface 160 includes a conventional network device (e.g., a router), and the smart home environment 100 of
Generally, in some implementations, the network interface 160 includes a conventional network device (e.g., a router), and the smart home environment 100 of
In some implementations, some low-power nodes are incapable of bidirectional communication. These low-power nodes send messages, but they are unable to “listen”. Thus, other devices in the smart home environment 100, such as the spokesman nodes, cannot send information to these low-power nodes.
In some implementations, some low-power nodes are capable of only a limited bidirectional communication. For example, other devices are able to communicate with the low-power nodes only during a certain time period.
As described, in some implementations, the smart devices serve as low-power and spokesman nodes to create a mesh network in the smart home environment 100. In some implementations, individual low-power nodes in the smart home environment regularly send out messages regarding what they are sensing, and the other low-powered nodes in the smart home environment—in addition to sending out their own messages—forward the messages, thereby causing the messages to travel from node to node (i.e., device to device) throughout the smart home network 202. In some implementations, the spokesman nodes in the smart home network 202, which are able to communicate using a relatively high-power communication protocol, such as IEEE 802.11, are able to switch to a relatively low-power communication protocol, such as IEEE 802.15.4, to receive these messages, translate the messages to other communication protocols, and send the translated messages to other spokesman nodes and/or the smart home provider server system 164 (using, e.g., the relatively high-power communication protocol). Thus, the low-powered nodes using low-power communication protocols are able to send and/or receive messages across the entire smart home network 202, as well as over the Internet 162 to the smart home provider server system 164. In some implementations, the mesh network enables the smart home provider server system 164 to regularly receive data from most or all of the smart devices in the home, make inferences based on the data, facilitate state synchronization across devices within and outside of the smart home network 202, and send commands back to one or more of the smart devices to perform tasks in the smart home environment.
As described, the spokesman nodes and some of the low-powered nodes are capable of “listening.” Accordingly, users, other devices, and/or the smart home provider server system 164 may communicate control commands to the low-powered nodes. For example, a user may use the electronic device 166 (e.g., a smart phone) to send commands over the Internet to the smart home provider server system 164, which then relays the commands to one or more spokesman nodes in the smart home network 202. The spokesman nodes may use a low-power protocol to communicate the commands to the low-power nodes throughout the smart home network 202, as well as to other spokesman nodes that did not receive the commands directly from the smart home provider server system 164.
In some implementations, a smart nightlight 170 (
Other examples of low-power nodes include battery-operated versions of the smart hazard detectors 104. These smart hazard detectors 104 are often located in an area without access to constant and reliable power and may include any number and type of sensors, such as smoke/fire/heat sensors (e.g., thermal radiation sensors), carbon monoxide/dioxide sensors, occupancy/motion sensors, ambient light sensors, ambient temperature sensors, humidity sensors, and the like. Furthermore, smart hazard detectors 104 may send messages that correspond to each of the respective sensors to the other devices and/or the smart home provider server system 164, such as by using the mesh network as described above.
Examples of spokesman nodes include smart doorbells 106, smart thermostats 102, smart wall switches 108, and smart wall plugs 110. These devices 102, 106, 108, and 110 are often located near and connected to a reliable power source, and therefore may include more power-consuming components, such as one or more communication chips capable of bidirectional communication in a variety of protocols.
In some implementations, the smart home environment 100 includes service robots 168 (
As explained above with reference to
In some implementations, the devices and services platform 300 communicates with and collects data from the smart devices of the smart home environment 100. In addition, in some implementations, the devices and services platform 300 communicates with and collects data from a plurality of smart home environments across the world. For example, the smart home provider server system 164 collects home data 302 from the devices of one or more smart home environments 100, where the devices may routinely transmit home data or may transmit home data in specific instances (e.g., when a device queries the home data 302). Exemplary collected home data 302 includes, without limitation, power consumption data, blackbody radiation data, occupancy data, HVAC settings and usage data, carbon monoxide levels data, carbon dioxide levels data, volatile organic compounds levels data, sleeping schedule data, cooking schedule data, inside and outside temperature humidity data, television viewership data, inside and outside noise level data, pressure data, video data, etc.
In some implementations, the smart home provider server system 164 provides one or more services 304 to smart homes and/or third parties. Exemplary services 304 include, without limitation, software updates, customer support, sensor data collection/logging, remote access, remote or distributed control, and/or use suggestions (e.g., based on collected home data 302) to improve performance, reduce utility cost, increase safety, etc. In some implementations, data associated with the services 304 is stored at the smart home provider server system 164, and the smart home provider server system 164 retrieves and transmits the data at appropriate times (e.g., at regular intervals, upon receiving a request from a user, etc.).
In some implementations, the extensible devices and services platform 300 includes a processing engine 306, which may be concentrated at a single server or distributed among several different computing entities without limitation. In some implementations, the processing engine 306 includes engines configured to receive data from the devices of smart home environments 100 (e.g., via the Internet 162 and/or a network interface 160), to index the data, to analyze the data and/or to generate statistics based on the analysis or as part of the analysis. In some implementations, the analyzed data is stored as derived home data 308.
Results of the analysis or statistics may thereafter be transmitted back to the device that provided home data used to derive the results, to other devices, to a server providing a webpage to a user of the device, or to other non-smart device entities. In some implementations, use statistics, use statistics relative to use of other devices, use patterns, and/or statistics summarizing sensor readings are generated by the processing engine 306 and transmitted. The results or statistics may be provided via the Internet 162. In this manner, the processing engine 306 may be configured and programmed to derive a variety of useful information from the home data 302. A single server may include one or more processing engines.
The derived home data 308 may be used at different granularities for a variety of useful purposes, ranging from explicit programmed control of the devices on a per-home, per-neighborhood, or per-region basis (for example, demand-response programs for electrical utilities), to the generation of inferential abstractions that may assist on a per-home basis (for example, an inference may be drawn that the homeowner has left for vacation and so security detection equipment may be put on heightened sensitivity), to the generation of statistics and associated inferential abstractions that may be used for government or charitable purposes. For example, processing engine 306 may generate statistics about device usage across a population of devices and send the statistics to device users, service providers or other entities (e.g., entities that have requested the statistics and/or entities that have provided monetary compensation for the statistics).
In some implementations, to encourage innovation and research and to increase products and services available to users, the devices and services platform 300 exposes a range of application programming interfaces (APIs) 310 to third parties, such as charities 314, governmental entities 316 (e.g., the Food and Drug Administration or the Environmental Protection Agency), academic institutions 318 (e.g., university researchers), businesses 320 (e.g., providing device warranties or service to related equipment, targeting advertisements based on home data), utility companies 324, and other third parties. The APIs 310 are coupled to and permit third-party systems to communicate with the smart home provider server system 164, including the services 304, the processing engine 306, the home data 302, and the derived home data 308. In some implementations, the APIs 310 allow applications executed by the third parties to initiate specific data processing tasks that are executed by the smart home provider server system 164, as well as to receive dynamic updates to the home data 302 and the derived home data 308.
For example, third parties may develop programs and/or applications, such as web applications or mobile applications, that integrate with the smart home provider server system 164 to provide services and information to users. Such programs and applications may be, for example, designed to help users reduce energy consumption, to preemptively service faulty equipment, to prepare for high service demands, to track past service performance, etc., and/or to perform other beneficial functions or tasks.
In some implementations, processing engine 306 includes a challenges/rules/compliance/rewards paradigm 410d that informs a user of challenges, competitions, rules, compliance regulations and/or rewards and/or that uses operation data to determine whether a challenge has been met, a rule or regulation has been complied with and/or a reward has been earned. The challenges, rules, and/or regulations may relate to efforts to conserve energy, to live safely (e.g., reducing the occurrence of heat-source alerts) (e.g., reducing exposure to toxins or carcinogens), to conserve money and/or equipment life, to improve health, etc. For example, one challenge may involve participants turning down their thermostat by one degree for one week. Those participants that successfully complete the challenge are rewarded, such as with coupons, virtual currency, status, etc. Regarding compliance, an example involves a rental-property owner making a rule that no renters are permitted to access certain owner's rooms. The devices in the room having occupancy sensors may send updates to the owner when the room is accessed.
In some implementations, processing engine 306 integrates or otherwise uses extrinsic information 412 from extrinsic sources to improve the functioning of one or more processing paradigms. Extrinsic information 412 may be used to interpret data received from a device, to determine a characteristic of the environment near the device (e.g., outside a structure that the device is enclosed in), to determine services or products available to the user, to identify a social network or social-network information, to determine contact information of entities (e.g., public-service entities such as an emergency-response team, the police or a hospital) near the device, to identify statistical or environmental conditions, trends or other information associated with a home or neighborhood, and so forth.
In some implementations, the smart home provider server system 164 or a component thereof serves as the hub server system 508. In some implementations, the hub server system 508 is a dedicated video processing server that provides video processing services to video sources and client devices 504 independent of other services provided by the hub server system 508.
In some implementations, each of the video sources 522 includes one or more video cameras 118 that capture video and send the captured video to the hub server system 508 substantially in real-time. In some implementations, each of the video sources 522 optionally includes a controller device (not shown) that serves as an intermediary between the one or more cameras 118 and the hub server system 508. The controller device receives the video data from the one or more cameras 118, optionally, performs some preliminary processing on the video data, and sends the video data to the hub server system 508 on behalf of the one or more cameras 118 substantially in real-time. In some implementations, each camera has its own on-board processing capabilities to perform some preliminary processing on the captured video data before sending the processed video data (along with metadata obtained through the preliminary processing) to the controller device and/or the hub server system 508.
As shown in
In some implementations, the server-side module 506 includes one or more processors 512, a video storage database 514, device and account databases 516, an I/O interface to one or more client devices 518, and an I/O interface to one or more video sources 520. The I/O interface to one or more clients 518 facilitates the client-facing input and output processing for the server-side module 506. The databases 516 store a plurality of profiles for reviewer accounts registered with the video processing server, where a respective user profile includes account credentials for a respective reviewer account, and one or more video sources linked to the respective reviewer account. The I/O interface to one or more video sources 520 facilitates communications with one or more video sources 522 (e.g., groups of one or more cameras 118 and associated controller devices). The video storage database 514 stores raw video data received from the video sources 522, as well as various types of metadata, such as motion events, event categories, event category models, event filters, and event masks, for use in data processing for event monitoring and review for each reviewer account.
Examples of a representative client device 504 include, but are not limited to, a handheld computer, a wearable computing device, a personal digital assistant (PDA), a tablet computer, a laptop computer, a desktop computer, a cellular telephone, a smart phone, an enhanced general packet radio service (EGPRS) mobile phone, a media player, a navigation device, a game console, a television, a remote control, a point-of-sale (POS) terminal, vehicle-mounted computer, an ebook reader, or a combination of any two or more of these data processing devices or other data processing devices.
Examples of the one or more networks 162 include local area networks (LAN) and wide area networks (WAN) such as the Internet. The one or more networks 162 are, optionally, implemented using any known network protocol, including various wired or wireless protocols, such as Ethernet, Universal Serial Bus (USB), FIREWIRE, Long Term Evolution (LTE), Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wi-Fi, voice over Internet Protocol (VoIP), Wi-MAX, or any other suitable communication protocol.
In some implementations, the hub server system 508 is implemented on one or more standalone data processing apparatuses or a distributed network of computers. In some implementations, the hub server system 508 also employs various virtual devices and/or services of third party service providers (e.g., third-party cloud service providers) to provide the underlying computing resources and/or infrastructure resources of the hub server system 508. In some implementations, the hub server system 508 includes, but is not limited to, a handheld computer, a tablet computer, a laptop computer, a desktop computer, or a combination of any two or more of these data processing devices or other data processing devices.
The server-client environment 500 shown in
It should be understood that operating environment 500 that involves the hub server system 508, the video sources 522 and the video cameras 118 is merely an example. Many aspects of operating environment 500 are generally applicable in other operating environments in which a server system provides data processing for monitoring and facilitating review of data captured by other types of electronic devices (e.g., smart thermostats 102, smart hazard detectors 104, smart doorbells 106, smart wall plugs 110, appliances 112 and the like).
The electronic devices, the client devices or the server system communicate with each other using the one or more communication networks 162. In an exemplary smart home environment, two or more devices (e.g., the network interface device 160, the hub device 180, and the client devices 504-m) are located in close proximity to each other, such that they could be communicatively coupled in the same sub-network 162A via wired connections, a WLAN or a Bluetooth Personal Area Network (PAN). The Bluetooth PAN is optionally established based on classical Bluetooth technology or Bluetooth Low Energy (BLE) technology. This smart home environment further includes one or more other radio communication networks 162B via which at least some of the electronic devices 522-m exchange data with the hub device 160. Alternatively, in some situations, some of the electronic devices 522-m communicate with the network interface device 160 directly via the same sub-network 162A that couples devices 160, 180 and 504-m. In some implementations (e.g., in the network 162C), both the client device 504-m and the electronic devices 522-n communicate directly via the network(s) 162 without passing the network interface device 160 or the hub device 180.
In some implementations, during normal operation, the network interface device 160 and the hub device 180 communicate with each other to form a network gateway through which data are exchanged with the electronic device 522-n. As explained above, the network interface device 160 and the hub device 180 optionally communicate with each other via a sub-network 162A. However, a provisioning process is required to establish the communication between the network interface device 160 and the hub device 180 via the sub-network 162A. Specifically, a new hub device 180 has to receive a network identification and a network password associated with the sub-network 162A, such that the hub device 180 could communicate device information of the hub device 180 to the server 508 and allow the server 508 to associate the hub device 180 with one or more user accounts.
In some implementations, at least an optical link is formed between the client device 504-m and the hub device 180. The client device 504-m is configured to generate optical data (e.g., light flashes) coded with network information and user account information. The hub device 180 includes a light sensor that captures the optical data and recovers the network and user account information. Then, the hub device 180 uses the recovered network and user account information to access the sub-network 162A, the network(s) 162 and the server 508 and associate with a user account on the server 508.
The radios 640 enables one or more radio communication networks in the smart home environments, and allows a hub device to communicate with smart devices. In some implementations, the radios 640 are capable of data communications using any of a variety of custom or standard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) custom or standard wired protocols (e.g., Ethernet, HomePlug, etc.), and/or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document. The light sensor 650 senses light flashes from a device that is placed in proximity to the light sensor 650.
Communication interfaces 604 include, for example, hardware capable of data communications using any of a variety of custom or standard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) and/or any of a variety of custom or standard wired protocols (e.g., Ethernet, HomePlug, etc.), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Memory 606 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and, optionally, includes non-volatile memory, such as one or more magnetic disk storage devices, one or more optical disk storage devices, one or more flash memory devices, or one or more other non-volatile solid state storage devices. Memory 606, or alternatively the non-volatile memory within memory 606, includes a non-transitory computer readable storage medium. In some implementations, memory 606, or the non-transitory computer readable storage medium of memory 606, stores the following programs, modules, and data structures, or a subset or superset thereof:
Each of the above identified elements (e.g., modules stored in memory 206 of hub device 180) may be stored in one or more of the previously mentioned memory devices (e.g., the memory of any of the smart devices in smart home environment 100,
Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various implementations. In some implementations, memory 706, optionally, stores a subset of the modules and data structures identified above. Furthermore, memory 706, optionally, stores additional modules and data structures not described above.
Memory 806 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and, optionally, includes non-volatile memory, such as one or more magnetic disk storage devices, one or more optical disk storage devices, one or more flash memory devices, or one or more other non-volatile solid state storage devices. Memory 806, optionally, includes one or more storage devices remotely located from one or more processing units 802. Memory 806, or alternatively the non-volatile memory within memory 806, includes a non-transitory computer readable storage medium. In some implementations, memory 806, or the non-transitory computer readable storage medium of memory 806, stores the following programs, modules, and data structures, or a subset or superset thereof:
Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, modules or data structures, and thus various subsets of these modules may be combined or otherwise re-arranged in various implementations. In some implementations, memory 806, optionally, stores a subset of the modules and data structures identified above. Furthermore, memory 806, optionally, stores additional modules and data structures not described above.
In some implementations, at least some of the functions of the server system 508 are performed by the client device 604, and the corresponding sub-modules of these functions may be located within the client device rather than server system 508. In some implementations, at least some of the functions of the client device are performed by the server system 508, and the corresponding sub-modules of these functions may be located within the server system 508 rather than client device 604. The client device 604 and the server system 508 shown in
Enabling High-Level Features to Devices with Lower Levels of Functionality
Connected devices of the same fundamental type come with a variety of actual capabilities or functionalities. For example, one thermostat type may only enable adjustments to temperature, while other types may include advanced features such as device scheduling (e.g., running HVAC system at a particular time each day). Some implementations enable the capabilities of less capable devices to be extended to match or even exceed those of more capable devices of the same type through the use smart programming in the hub device 180 (or remote servers/cloud computers, other devices in the smart home environment, etc.) to which the connected device is coupled and controlled.
The techniques and methods described below enable the following extensions to the capabilities of various connected devices:
(1) Through advanced learning capabilities and other techniques, a hub device (or remote servers/cloud computers, other devices in the smart home environment, etc.) intercepts advanced commands and emulates the advanced capability, using a combination of simple capabilities, to provide advanced functionality from/to less sophisticated devices.
(2) The hub (or remote servers/cloud computers, other devices in the smart home environment, etc.) presents, to a mobile device (e.g., a user controller electronic device 166,
(3) Multiple simple devices can be combined into a single “virtual device” with the capability of a more complex device type. (For example, separate single-purpose weather sensing devices such as a connected thermometer, barometer and wind gauge can be represented by and controlled from the hub 180 device as if they were a more sophisticated connected home weather station).
In many cases, a device description maintained in the hub 180 (or remote servers/cloud computers, other devices in the smart home environment, etc.) is abstracted to the lowest common denominator of capabilities of available devices within its category. In some implementations, a fully capable device interface is presented by the hub 180 (or remote servers/cloud computers, other devices in the smart home environment, etc.) and, in some implementations, reflected in a user interface of a user controller electronic device 166 (
On devices where a particular advanced capability exists (e.g., scheduling a thermostat for different times and days of the week), respective advances commands are sent directly to the device. In other cases in which devices do not have the particular advanced capability by default, however, a hub (or remote servers/cloud computers, other devices in the smart home environment, etc.) provides extra logic to perform and emulate the same task. As described below, this is accomplished through device configurations that include fully emulated functionality, but which can be overridden to call the device directly when it supports the capability. For example, as shown in
In one example, thermostats with no scheduling capabilities are provided by the hub 180 (or remote servers/cloud computers, other devices in the smart home environment, etc.) with the ability to run on a schedule. As described above, in some implementations the hub (or remote servers/cloud computers, other devices in the smart home environment, etc.) intercepts an advanced command from a user device (e.g., electronic device 166,
In another example, certain dimmer switches have an advanced functionality for continuously brightening/diming a light source, useful, for example, when a holding a button on a remote. For dimmers without this capability, the hub (or remote servers/cloud computers, other devices in the smart home environment, etc.) implements a timer to manually increment the dim value over time to emulate the advanced functionality. This example is described in detail with respect to the method 1000-B in
Example logic for implementing such functionality of advanced dimmers is provided below. In this example, the advanced capability as implemented in the hub 180 (or remote servers/cloud computers, other devices in the smart home environment, etc.) commands a light source to continuously brighten until it receives a command to stop (e.g., to be used while a user holds a “brighten” button on a remote). The top trait/interface describes the device methods which must be defined by the physical device mappings (note here that only setLevel must be implemented). It includes full implementations of the adjust capability. Also shown are two physical implementations: the first for a capable device which maps the complex capability to the physical devices capability, and the second for physically implementing setLevel and using the internal implementation to create the same capability.
Example code (e.g., representing source code for a main processor on the hub (e.g., CPU(s) 602 of hub device 180) and written in Scala programming language):
In yet another example, location and time information are used to calculate day/night hours and enable lights to run only during nighttime hours. More specifically, location and time are obtained by the hub (e.g., sunrise/sunset dependent device control module 6264,
For virtual devices composed of multiple simple devices, a device type profile contains minimum functionalities required of the various simple devices. If the minimum requirements are met, a composite virtual device emulates the functionality of the complex device using the various simple capabilities. One example includes using a relay switch and an open/close sensor to emulate a garage door opener. In particular, a garage door minimally requires: (i) a mechanism to determine the current position of the door (e.g., mechanism for determining whether the door closed) and (ii) a temporary contact relay to activate the door. Thus, if the user positions a sensor detecting the closed position of the door, and a smart relay connected to the manual button of the garage door opener, the devices could be operated remotely and show the door's current position, allowing a user to open or close it. Failures to close or open can similarly be reported.
Other example includes a simple pushbutton, camera, and a music system combined to create a whole-house doorbell. Here, the music system is not purposed solely to the doorbell setup. This example is described in detail with respect to the method 1000-F in Figure H.
As another example, a user mounts a simple thermostat conveniently in a hallway, but also wants to use the temperature from a different room to run it. By using the techniques discussed above, a temperature sensor may be used in the room with the desired temperature, while still allowing the thermostat unit to be positioned in the hallway as desired. This example is described in detail with respect to the method 1000-D in
At the top, a device interface 900 (“Device Complete Interface Definition”) contains the complete fully functional interface definition of a particular device type (e.g., garage door system, thermostat, light system, etc.) (e.g., stored and managed by high-level device feature module 626 or a sub-module thereof,
At the top, a device interface 950 (“Garage Door Complete Interface Definition”) contains the complete fully functional interface definition of a particular device type (e.g., stored and managed by high-level device feature module 626 or a sub-module thereof,
Referring to
The first device receives (1008) (e.g., from a client device displaying a user interface for controlling smart devices in a smart home environment) a first command for performing a first functionality on at least the second device, the first functionality comprising a plurality of constituent functionalities. The second device is not configured to execute the first command. For example, the first functionality is an advanced feature for scheduling operation of a thermostat for different times and days of the week, the second device being a basic thermostat that does not provide the advanced scheduling functionality and can only perform basic temperature setting capabilities. Different functionalities and the devices on which such functionalities are emulated are described in greater detail below.
In some implementations, the second device is (1010) a smart plug device (e.g., smart wall plug 110) that provides power to a coupled device. In some implementations, the second device is (1012) a thermostat device (e.g., thermostat 102). In some implementations, the second device is (1014) a lock device (e.g., a smart doorlock).
In some implementations, the first functionality is (1016) for operating the second device in accordance with a predefined schedule (e.g., scheduling operation of a thermostat for different times and days of the week). In some implementations, the predefined schedule is specified with respect to days of the week. Additionally and/or alternatively, the predefined schedule is specified with respect to hours for each day of the week. In some implementations, the first functionality is for operating the second device in accordance with detection of a sunrise or sunset condition in a local area in which the second device is situated (e.g., closing a smart curtain in response to detecting the sun setting).
Referring now to
In some implementations, the plurality of constituent functionalities for the first functionality includes (1020) a first constituent functionality for enabling or disabling an operation of the second device. Execution of a first one of the plurality of sub-commands by the second device performs the first constituent functionality. For example, in some implementations, enabling or disabling the operation includes (1022) turning on or off the cooling or heating functionality of the thermostat device. Furthermore, in some implementations, enabling or disabling the operation includes (1024) permitting or denying the locking or unlocking of the lock device. In some implementations, the first sub-command, when executed, causes the lock device to replace an existing list of valid access codes with a new list of valid access codes.
In some implementations, the plurality of constituent functionalities includes (1026) a second constituent functionality for sending commands, including the first sub-command, in accordance with the predefined schedule. Execution of a second one of the plurality of sub-commands by the first device performs the second constituent functionality, the first device being configured with scheduling capabilities. For example, execution of the second sub-command results in the first sub-command (e.g., command for turning on/off a cooling functionality of a thermostat device) being sent to a device based on a schedule.
In some implementations, the plurality of constituent functionalities further includes a third constituent functionality for detecting the sunrise or sunset conditions, wherein execution of a third one of the plurality of sub-commands performs the third constituent functionality. Furthermore, in some implementations, the second constituent functionality is for sending the commands, including the first sub-command, in accordance with detection of the sunrise or sunset conditions.
The first device manages (1028) execution of the plurality of sub-commands by the respective devices, wherein execution of the plurality of sub-commands by the respective devices emulates performance of the first functionality on at least the second device. In some implementations, managing execution includes (1030) executing the second sub-command on the first device, including (1032) sending the first sub-command to the second device in accordance with the predefined schedule. Referring to the example above, if a first device is a hub device that includes scheduling capabilities (e.g., sending commands based on a predefined schedule), execution of the second sub-command by the hub device results in the first sub-command (e.g., command for turning on/off a cooling functionality of a thermostat device) being sent to a thermostat device in accordance with a schedule. Thus, while the thermostat device in this example does not itself have scheduling functionalities built-in, managing execution of the first and second sub-commands effectively emulates such functionality on the thermostat device. In some implementations, executing the second sub-command further includes (1034) sending the first sub-command to the second device upon detection of the sunrise or sunset conditions (e.g., sending a command to a smart device to automatically close window blinds at sunset).
Referring to
In some implementations, the second device is (1036) a lamp device. Furthermore, in some implementations, the first functionality is (1038) for continuously dimming or brightening the lamp device.
In some implementations, the plurality of constituent functionalities includes (1040) a first constituent functionality for setting a dim value of the lamp device. The first constituent functionality corresponds to a plurality of first sub-commands, of the plurality of sub-commands, to be executed by the lamp device. Each of the plurality of first sub-commands corresponds to a respective dim value, of a range of dim values for the lamp device, that is set upon execution of a respective first-subcommand. For example, each of the first sub-commands corresponds to a different brightness/dim value, and the lamp device is capable of executing the sub-commands (and therefore setting a brightness or dim value) one at a time.
In some implementations, the plurality of constituent functionalities includes (1042) a second constituent functionality for incrementally sending commands, including the plurality of first sub-commands, in accordance with a timer. Execution of a second one of the plurality of sub-commands by the first device performs the second constituent functionality. For example, execution of the second sub-command results in the plurality of first sub-command (e.g., commands for setting a lamp device at different specified dim values) being sent to a device based on a timer (e.g., a different first sub-command being sent every 0.2 ms).
In some implementations, managing (step 1028) execution of the plurality of sub-commands by the respective devices includes (1044) executing the second sub-command on the first device, which includes sending the plurality of first sub-commands one at a time based on the timer, in order of either decreasing dim value for continuously dimming the lamp device, or increasing dim value for continuously brightening the lamp device. Referring to the example above, if a first device is a remote server with timing capabilities (e.g., sending sub-commands at specified intervals of time), execution of the second sub-command by the remote server results in the plurality of first sub-commands (e.g., for setting a lamp device at different specified dim values) being sent to the lamp device either in order of decreasing or increasing dim value to emulate the functionality of a light dimmer. Thus, while the lamp device in this example does not itself have dimming capabilities built-in, managing execution of the plurality of first sub-commands and the second sub-command effectively emulates such functionality on the lamp device.
Referring to
In some implementations, the second device is (1046) a garage door opener coupled to a garage door. Furthermore, in some implementations, the first functionality is (1048) for providing an indication of a percentage by which a garage door operation is complete (e.g., displaying a progress indicator on a client device user interface), wherein a garage door operation for opening the garage door is associated with a first completion time for opening the garage door, and a garage door operation for closing the garage door is associated with a second completion time for closing the garage door.
In some implementations, the plurality of constituent functionalities includes (1050) a first constituent functionality for opening or closing the garage door. Execution of a first one of the plurality of sub-commands by the garage door opener performs the first constituent functionality. For example, execution of the first sub-command by the garage door opener (e.g., a motor) results in the coupled garage door to either physically open or close.
In some implementations, the plurality of constituent functionalities includes (1052) a second constituent functionality for identifying an elapsed time since commencing a garage door operation. Execution of a second one of the plurality of sub-commands by a timer device (e.g., a component or module of a hub device 180) performs the second constituent functionality. For example, execution of the second sub-command by the timer device causes the timer device to output (e.g., and send back to the device that transmitted the second sub-command to the timer device) a reading that indicates an elapsed time since beginning a current garage door operation.
In some implementations, the plurality of constituent functionalities includes (1054) a third constituent functionality for determining whether the garage door is fully opened or fully closed. Execution of a third one of the plurality of sub-commands by a sensor device (e.g., separate from the garage door opener and positioned in line-of-sight of the garage door) performs the third constituent functionality. For example, execution of the third sub-command by the sensor device causes the sensor to output (e.g., and send back to the device that transmitted the third sub-command to the sensor device) a reading that indicates whether the garage door is partially/fully open or closed.
In some implementations, managing (step 1028) execution of the plurality of sub-commands by the respective devices includes, for a garage door operation for opening the garage door, and until receiving a determination that the garage door is fully open (1056): determining (1058) the percentage by which the garage door operation is complete by dividing the elapsed time by the first completion time; and providing (1060) the indication of the determined percentage. For example, the first sub-command for opening a garage door is first sent to the garage door opener. Once the garage door open operation commences, the elapsed time is obtained by continuously sending (e.g., at predefined intervals) the second sub-command to the timer device thereafter until the garage door is fully opened, which is determined by continuously sending (e.g., at predefined intervals) the third sub-command to the sensor device until an indication that the garage door is fully open is returned. Until the garage door is fully opened, the elapsed time readings obtained from the timer device are used in conjunction with the first completion time (e.g., for opening the garage door) to determine the percentage by which a garage door operation is complete.
In some implementations, managing (step 1028) execution of the plurality of sub-commands by the respective devices includes, for a garage door operation for closing the garage door, and until receiving a determination that the garage door is fully closed (1062): determining (1064) the percentage by which the garage door operation is complete by dividing the elapsed time by the second completion time; and providing (1066) the indication of the determined percentage. For example, the first sub-command for closing a garage door is first sent to the garage door opener. Once the garage door closing operation commences, the elapsed time is obtained by continuously sending (e.g., at predefined intervals) the second sub-command to the timer device thereafter until the garage door is fully closed, which is determined by continuously sending (e.g., at predefined intervals) the third sub-command to the sensor device until an indication that the garage door is fully open is returned. Until the garage door is fully opened, the elapsed time readings obtained from the timer device is used in conjunction with the second completion time (e.g., for closing the garage door) to determine the percentage by which a garage door operation is complete. Thus, while none of the devices in this example are individually capable of determining a real-time progress of a garage door operation, managing execution of the sub-commands across the respective devices effectively emulates such functionality.
Referring to
In some implementations, the second device is (1068) a thermostat device. Furthermore, in some implementations, the first functionality is (1070) for operating the thermostat device in accordance with temperature readings obtained from a distinct sensor device located remotely from the thermostat device. For example, the distinct sensor device may be a device equipped with temperature sensors (e.g., a hazard detector 104) that is located in a different room from the thermostat.
In some implementations, the plurality of constituent functionalities includes (1072) a first constituent functionality for turning the thermostat device on or off (e.g., command for turning on/off a cooling/heating functionality of a thermostat device). Execution of a first one of the plurality of sub-commands by the thermostat device performs the first constituent functionality.
In some implementations, the plurality of constituent functionalities includes (1074) a second constituent functionality for obtaining temperature readings. Execution of a second one of the plurality of sub-commands by the sensor device (e.g., hazard detector 104) performs the second constituent functionality.
In some implementations, managing (step 1028) execution of the plurality of sub-commands by the respective devices includes (1076) the execution of the first sub-command by the thermostat device in accordance with the temperature readings obtained by the sensor device. For example, execution of the second sub-command by the sensor device causes the sensor to output (e.g., and send back to the device that transmitted the second sub-command to the sensor device) a temperature reading of the room in which the sensor device is located. This temperature reading obtained from the sensor device is then used by the thermostat device in performing its basic operations of turning on/off its cooling or heating functionality. Advantageously, a temperature sensor may be used in a room with the desired temperature, while allowing a thermostat unit to be positioned in a different room as desired.
Referring to
In some implementations, the first functionality is (1078) for operating the second device (e.g., a thermostat) in accordance with an occupancy model developed by presence detection readings obtained from a plurality of sensor devices. As described with respect to
In some implementations, the plurality of constituent functionalities includes (1082) a first constituent functionality for enabling or disabling an operation of the second device (e.g., turning device on/off). Execution of a first one of the plurality of sub-commands by the second device performs the first constituent functionality.
In some implementations, the plurality of constituent functionalities includes (1084) a second constituent functionality for obtaining presence detection readings. Execution of a second one of the plurality of sub-commands by the plurality of sensor devices performs the second constituent functionality. For example, execution of the second sub-command by one or more sensor devices causes the devices to output (e.g., and send back to the device that transmitted the second sub-command to the sensor devices) a reading that indicates a current occupancy of a specified area.
In some implementations, managing (step 1028) execution of the plurality of sub-commands by the respective devices includes (1086) execution of the first sub-command by the second device in accordance with the occupancy model developed by presence detection readings obtained from the plurality of sensor devices. In one example, a camera device may be turned on (e.g., by executing the first sub-command) in response to detecting an unexpected occupancy within a household, based on an occupancy model developed by multiple sensor devices within the household that execute the second sub-commands. Thus, although some devices do not have built-in presence sensors and are not operated based on an occupancy they detect, such functionality is emulated by managing execution of the sub-commands across the respective devices.
Referring to
In some implementations, the second device is (1088) a sound system for playing audio from multiple sources (e.g., a home theater system). Furthermore, in some implementations, the first functionality is (1090) for operating the sound system in response to detecting activation of a push button. For example, the push button may be a doorbell device (or other electronic device having a button) configured to transmit signals to other devices either wirelessly or using a wired connection. In some implementations, the sound system and the push button are located remotely from each other (e.g., in different regions of a premises). Additionally and/or alternatively, the first functionality is further for operating a camera device in response to detecting activation of the push button (e.g., capture surveillance image in response to detecting a trigger signal from activating the push button).
In some implementations, the plurality of constituent functionalities includes (1092) a first constituent functionality for playing audio (e.g., a sound effect) on the sound system. Execution of a first one of the plurality of sub-commands by the sound system performs the first constituent functionality. In some implementations, the audio played back is stored as a file in the sound system.
In some implementations, the plurality of constituent functionalities includes (1094) a second constituent functionality for transmitting a trigger signal to one or more remote devices, including the sound system, in response to detecting activation of the push button. Execution of a second one of the plurality of sub-commands by the push button performs the second constituent functionality. The trigger signal may be a simple command that causes playback of a pre-configured audio file or sound effect.
In some implementations, the plurality of constituent functionalities includes a third constituent functionality for capturing an image, wherein execution of a third one of the plurality of sub-commands by the camera device performs the third constituent functionality.
In some implementations, managing (step 1028) execution of the plurality of sub-commands by the respective devices includes (1096) execution of the first sub-command by the sound system is in response to the sound system receiving the trigger signal from the push button, the push button transmitting the trigger signal in response to detecting activation of the push button. As an example, if a doorbell button is activated in response to a user pressing the button, a trigger signal is sent (e.g., wirelessly) to a sound system, and the sound system plays audio in response to receiving the trigger signal. In effect, while a doorbell may typically be limited to outputting sound in a particular region (e.g., front region of household), the advanced functionality of using an existing sound system to operate concurrently with a doorbell is emulated by managing execution of the sub-commands across the respective devices. Furthermore, in some implementations, execution of the third sub-command by the camera device is in response to the camera device receiving the trigger signal from the push button, the push button transmitting the trigger signal in response to detecting activation of the push button. Thus, in addition to playing a sound effect on the sound system, the trigger signal is additionally transmitted to a surveillance camera (e.g., positioned at the front door) and causes the camera to capture an image.
The first device identifies (1102) a first functionality to be performed on a first device, the first functionality comprising a plurality of constituent functionalities (various functionalities and respective constituent functionalities are described above with respect to
Furthermore, the first device obtains (1104) respective sets of functionalities for a plurality of devices including the first device. The respective sets of functionalities correspond to various device capabilities, functionalities, and features of a particular device. For example, a thermostat device 102 (
The first device then identifies (1106) two or more devices, of the plurality of devices and including the first device, having respective sets of functionalities that together include the plurality of constituent functionalities. For example, given a first functionality for operating a thermostat in accordance with a predefined schedule, constituent functionalities include functionality for (1) operating a thermostat device (e.g., turning cooling/heating functions on/off), and (2) sending commands to the thermostat device in accordance with a predefined schedule (e.g., during specific hours in a day). Continuing the example above, both the thermostat device (e.g., cooling/heating functionality) and the hub device (e.g., scheduling capabilities) are therefore identified and selected as having sets of functionalities that together include the required constituent functionalities.
After identifying the two or more devices, a plurality of sub-commands is generated (1108), each of the plurality of sub-commands for execution by a corresponding device of the two or more devices. Execution of a respective one of the plurality of sub-commands enables performance of a respective one of the plurality of constituent functionalities, and execution of the plurality of sub-commands emulates performance of the first functionality on at least the first device. Referring to the example above, a first sub-command (or set of first sub-commands) is generated for the thermostat device 102 for activating or deactivating the cooling/heating functionality, while a second sub-command (or set of second sub-commands) is generated for the hub device 180 to enable the sending of the first sub-command to the thermostat in accordance with a predefined schedule. In doing so, the first functionality for operating a thermostat in accordance with a predefined schedule is enabled for the thermostat, although neither the thermostat nor the hub device itself has such capabilities. Stages of methods 1000-A through 1000-F (
For situations in which the systems discussed above collect information about users, the users may be provided with an opportunity to opt in/out of programs or features that may collect personal information (e.g., information about a user's preferences or usage of a smart device). In addition, in some implementations, certain data may be anonymized in one or more ways before it is stored or used, so that personally identifiable information is removed. For example, a user's identity may be anonymized so that the personally identifiable information cannot be determined for or associated with the user, and so that user preferences or user interactions are generalized (for example, generalized based on user demographics) rather than associated with a particular user.
Although some of various drawings illustrate a number of logical stages in a particular order, stages that are not order dependent may be reordered and other stages may be combined or broken out. While some reordering or other groupings are specifically mentioned, others will be obvious to those of ordinary skill in the art, so the ordering and groupings presented herein are not an exhaustive list of alternatives. Moreover, it should be recognized that the stages could be implemented in hardware, firmware, software or any combination thereof.
The foregoing description, for purpose of explanation, has been described with reference to specific implementations. However, the illustrative discussions above are not intended to be exhaustive or to limit the scope of the claims to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The implementations were chosen in order to best explain the principles underlying the claims and their practical applications, to thereby enable others skilled in the art to best use the implementations with various modifications as are suited to the particular uses contemplated.
This application claims priority to U.S. Provisional Patent Application No. 62/078,912, filed Nov. 12, 2014, which is hereby incorporated by reference in its entirety. This application is related to U.S. patent application Ser. No. ______ (Attorney Docket No. 104248-5037-US), filed ______, entitled “______,” U.S. patent application Ser. No. ______ (Attorney Docket No. 104248-5039-US), filed ______, entitled “______,” U.S. patent application Ser. No. ______ (Attorney Docket No. 104248-5040-US), filed ______, entitled “______,” and U.S. patent application Ser. No. ______ (Attorney Docket No. 104248-5040-US01), filed ______, entitled “______,” which are hereby incorporated by reference in their entirety.
| Number | Date | Country | |
|---|---|---|---|
| 62078912 | Nov 2014 | US |
