Various arrangements for integrating control of multiple cloud-based smart-home devices are presented. Registration information may be received for a first and second smart-home device that are controlled using different cloud-based server systems. A determination may be made that that the first smart-home device and the second smart-home device share a common function. The first smart-home device and the second smart-home device may be assigned to a common operating characteristic group based on the common function being shared by the first smart-home device and the second smart-home device. A control element may be provided that allows for control of smart-home devices with the common operating characteristic group. The control element may control the common function at the first smart-home device via the first cloud-based server system and at the second smart-home device via the second cloud-based server system.
|
11. A system for integrating control of multiple cloud-based smart-home devices, the system comprising:
an application executed by a mobile device, wherein the application causes one or more processors of the mobile device to:
receive a first set of smart-home device registration information for a first smart-home device, wherein:
at least one function of the first smart-home device is controlled via communication with a first cloud-based server system; and
a first third-party manufacturer that provides the first smart-home device operates the first cloud-based server system;
receive a second set of smart-home device registration information for a second smart-home device, wherein:
at least one function of the second smart-home device is controlled via communication with a second cloud-based server system distinct from the first cloud-based server system; and
a second third-party manufacturer that provides the second smart-home device operates the second cloud-based server system, the second third-party manufacturer being distinct from the first third-party manufacturer and the second cloud-based server system being distinct from the first cloud-based server system;
determine that the first smart-home device and the second smart-home device share two common functions;
assign the first smart-home device controlled via communication with the first cloud-based server system and the second smart-home device controlled via communication with the second cloud-based server system to a common operating characteristic group based on a first common function being shared by the first smart-home device and the second smart-home device; and
output, for presentation, within a control interface of the application presented on a touchscreen display, a first control element and a second control element that control smart-home devices within the common operating characteristic group, wherein:
the first control element and the second control element are presented concurrently as part of the touchscreen control interface;
the control interface is configured such that the first control element and the second control element that control smart-home devices within the common operating characteristic group are selected via touch-based user input;
the first control element, when selected, controls the first common function at the first smart-home device via the first cloud-based server system and at the second smart-home device via the second cloud-based server system; and
the second control element, when selected, controls a second common function at the first smart-home device via the first cloud-based server system and at the second smart-home device via the second cloud-based server system.
20. A system for integrating control of multiple cloud-based smart-home devices, the system comprising:
a cloud-based host server system; and
an application executed by a mobile device, wherein one or more processors of the cloud-based host server system and the mobile device are configured to:
receive a first set of smart-home device registration information for a first smart-home device, wherein:
at least one function of the first smart-home device is controlled via communication with a first cloud-based server system; and
a first third-party manufacturer that provides the first smart-home device operates the first cloud-based server system;
receive a second set of smart-home device registration information for a second smart-home device, wherein:
at least one function of the second smart-home device is controlled via communication with a second cloud-based server system distinct from the first cloud-based server system; and
a second third-party manufacturer that provides the second smart-home device operates the second cloud-based server system, the second third-party manufacturer being distinct from the first third-party manufacturer and the second cloud-based server system being distinct from the first cloud-based server system;
determine that the first smart-home device and the second smart-home device share two common functions;
assign the first smart-home device controlled via communication with the first cloud-based server system and the second smart-home device controlled via communication with the second cloud-based server system to a common operating characteristic group based on a first common function being shared by the first smart-home device and the second smart-home device; and
output for presentation a first control element and a second control element within a touchscreen control interface of the application by the mobile device that control smart-home devices within the common operating characteristic group, wherein:
the first control element and the second control element are presented concurrently as part of the touchscreen control interface;
the touchscreen control interface is configured such that the first control element and the second control element that control smart-home devices within the common operating characteristic group are selected via a touch-based user input;
the first control element, when selected, controls the first common function at the first smart-home device via the first cloud-based server system and at the second smart-home device via the second cloud-based server system; and
the second control element, when selected, controls a second common function at the first smart-home device via the first cloud-based server system and at the second smart-home device via the second cloud-based server system.
1. A method for integrating control of multiple cloud-based smart-home devices, the method comprising:
receiving, by an application being executed by a mobile device, a first set of smart-home device registration information for a first smart-home device, wherein:
at least one function of the first smart-home device is controlled via communication with a first cloud-based server system; and
a first third-party manufacturer that provides the first smart-home device operates the first cloud-based server system;
receiving, by the application being executed by the mobile device, a second set of smart-home device registration information for a second smart-home device, wherein:
at least one function of the second smart-home device is controlled via communication with a second cloud-based server system distinct from the first cloud-based server system; and
a second third-party manufacturer that provides the second smart-home device operates the second cloud-based server system, the second third-party manufacturer being distinct from the first third-party manufacturer and the second cloud-based server system being distinct from the first cloud-based server system;
determining, by the application being executed by the mobile device, that the first smart-home device and the second smart-home device share two common functions;
assigning the first smart-home device controlled via communication with the first cloud-based server system and the second smart-home device controlled via communication with the second cloud-based server system to a common operating characteristic group based on a first common function being shared by the first smart-home device and the second smart-home device; and
generating, within a touchscreen control interface of the application being executed by the mobile device, a first selectable control element and a second selectable control element that control smart-home devices within the common operating characteristic group, wherein:
the first selectable control element and the second selectable control element are presented concurrently as part of the touchscreen control interface;
the touchscreen control interface is configured such that the selectable control element that controls smart-home devices within the common operating characteristic group is selected via a touch-based user input;
the first selectable control element, when selected, controls the first common function of the two common functions at the first smart-home device via the first cloud-based server system and at the second smart-home device via the second cloud-based server system; and
the second selectable control element, when selected, controls a second common function of the two common functions at the first smart-home device via the first cloud-based server system and at the second smart-home device via the second cloud-based server system.
2. The method for integrating control of multiple cloud-based smart-home devices of
3. The method for integrating control of multiple cloud-based smart-home devices of
4. The method for integrating control of multiple cloud-based smart-home devices of
receiving, by the application being executed by the mobile device, the first set of smart-home device registration information for the first smart-home device comprises receiving, by the application, from a user, a user-defined name.
5. The method for integrating control of the multiple cloud-based smart-home devices of
comparing the user-defined name to database of function-specific terms; and
determining the function of the first smart-home device based on comparing the user-defined name to the database of function-specific terms.
6. The method for integrating control of the multiple cloud-based smart-home devices of
determining the function of the first smart-home device that was determined based on the user-defined name matches the function of the second smart-home device.
7. The method for integrating control of the multiple cloud-based smart-home devices of
the first smart-home device is a smart outlet plug; and
receiving the first set of smart-home device registration information for the first smart-home device comprises receiving the user-defined name that includes a term meaning “light.”
8. The method for integrating control of the multiple cloud-based smart-home devices of
9. The method for integrating control of the multiple cloud-based smart-home devices of
10. The method for integrating control of the multiple cloud-based smart-home devices of
12. The system for integrating control of multiple cloud-based smart-home devices of
provide separate controls for the first smart-home device and the second smart-home device.
13. The system for integrating control of multiple cloud-based smart-home devices of
provide a third control element concurrently with the first control element that controls a third function that is only performed at one of the first smart-home device and the second smart-home device.
14. The system for integrating control of multiple cloud-based smart-home devices of
15. The system for integrating control of the multiple cloud-based smart-home devices of
compare the user-defined name to database of function-specific terms; and
determine the function of the first smart-home device based on comparing the user-defined name to the database of function-specific terms.
16. The system for integrating control of the multiple cloud-based smart-home devices of
determine the function of the first smart-home device that was determined based on the user-defined name matches the function of the second smart-home device.
17. The system for integrating control of the multiple cloud-based smart-home devices of
the first smart-home device is a smart outlet plug; and
the application causing the one or more processors to receive the first set of smart-home device registration information for the first smart-home device comprises the application causing the one or more processors of the mobile device to receive the user-defined name that includes a term meaning “light.”
18. The system for integrating control of the multiple cloud-based smart-home devices of
19. The system for integrating control of the multiple cloud-based smart-home devices of
|
This application is related U.S. patent application Ser. No. 16/154,512, filed on Oct. 8, 2018, entitled “Customized Interface based on Vocal Input,” the entire disclosure of which is hereby incorporated by reference for all purposes.
Smart-home devices, such as smart outlets, smart lights, smart speakers, home assistant devices, smart thermostats, and smart hazard detectors are becoming common in homes worldwide. Effectively allowing a single controller device to control various smart-home devices that have varying capabilities and that receive commands from different cloud-based server systems can result in significant technical challenges.
Various embodiments are described related to method for integrating control of multiple cloud-based smart-home devices. In some embodiments, a method for integrating control of multiple cloud-based smart-home devices is described. The method may include receiving, by an application being executed by a mobile device, a first set of smart-home device registration information for a first smart-home device. At least one function of the first smart-home device may be controlled via communication with a first cloud-based server system. The method may include receiving, by the application being executed by the mobile device, a second set of smart-home device registration information for a second smart-home device. At least one function of the second smart-home device may be controlled via communication with a second cloud-based server system distinct from the first cloud-based server system. The method may include determining, by the application being executed by the mobile device, that the first smart-home device and the second smart-home device share a common function. The method may include assigning the first smart-home device controlled via communication with the first cloud-based server system and the second smart-home device controlled via communication with the second cloud-based server system to a common operating characteristic group based on the common function being shared by the first smart-home device and the second smart-home device. The method may include providing, by the application being executed by the mobile device, a control element that allows for control of smart-home devices with the common operating characteristic group. The control element controls the common function at the first smart-home device via the first cloud-based server system and at the second smart-home device via the second cloud-based server system.
Embodiments of such a method may include one or more of the following features: providing separate controls for the first smart-home device and the second smart-home device. The method may include providing a second control element concurrently with the control element that controls a second function that may only be performed at one of the first smart-home device and the second smart-home device. Receiving, by the application being executed by the mobile device, the first set of smart-home device registration information for the first smart-home device may include receiving, by the application, from a user, a user-defined name. Determining that the first smart-home device and the second smart-home device share the common function may include comparing the user-defined name to database of function-specific terms and determining the function of the first smart-home device based on comparing the user-defined name to the database of function-specific terms. Determining that the first smart-home device and the second smart-home device share the common function may include determining the function of the first smart-home device that was determined based on the user-defined name matches the function of the second smart-home device. The first smart-home device may be a smart outlet plug. Receiving the first set of smart-home device registration information for the first smart-home device may include receiving the user-defined name that includes a term meaning “light.” The first smart-home device that may be the smart outlet plug may be assigned to a lighting group. The first set of smart-home device registration information may include an indication of a location and the second set of smart-home device registration information may include the indication of the location. Assigning the first smart-home device controlled via communication with the first cloud-based server system and the second smart-home device controlled via communication with the first cloud-based server system to the common operating characteristic group may be further based on the first smart-home device and the second smart-home device being mapped to the location.
In some embodiments, a system for integrating control of multiple cloud-based smart-home devices is described. The system may include an application executed by a mobile device. The application may cause one or more processors of the mobile device to receive a first set of smart-home device registration information for a first smart-home device. At least one function of the first smart-home device may be controlled via communication with a first cloud-based server system. The application may cause one or more processors of the mobile device to receive a second set of smart-home device registration information for a second smart-home device. At least one function of the second smart-home device may be controlled via communication with a second cloud-based server system distinct from the first cloud-based server system. The application may cause one or more processors of the mobile device to determine that the first smart-home device and the second smart-home device share a common function. The application may cause one or more processors of the mobile device to assign the first smart-home device controlled via communication with the first cloud-based server system and the second smart-home device controlled via communication with the second cloud-based server system to a common operating characteristic group based on the common function being shared by the first smart-home device and the second smart-home device. The application may cause one or more processors of the mobile device to output a control element that allows for control of smart-home devices with the common operating characteristic group. The control element may control the common function at the first smart-home device via the first cloud-based server system and at the second smart-home device via the second cloud-based server system.
Embodiments of such a system may include one or more of the following features: the application may further cause the one or more processors of the mobile device to provide separate controls for the first smart-home device and the second smart-home device. The application may further cause the one or more processors of the mobile device to provide a second control element concurrently with the control element that controls a second function that may only be performed at one of the first smart-home device and the second smart-home device. The application causing the one or more processors to receive the first set of smart-home device registration information for the first smart-home device may include the application causing the one or more processors of the mobile device to: receive, from a user, a user-defined name. The application causing the one or more processors to determine that the first smart-home device and the second smart-home device share the common function may include the application causing the one or more processors of the mobile device to compare the user-defined name to database of function-specific terms and determine the function of the first smart-home device based on comparing the user-defined name to the database of function-specific terms. The application causing the one or more processors to determine that the first smart-home device and the second smart-home device share the common function may include the application causing the one or more processors of the mobile device to determine the function of the first smart-home device that was determined based on the user-defined name matches the function of the second smart-home device. The first smart-home device may be a smart outlet plug. The application causing the one or more processors to receive the first set of smart-home device registration information for the first smart-home device may include the application causing the one or more processors of the mobile device to receive the user-defined name that includes a term meaning “light.” The first smart-home device that may be the smart outlet plug may be assigned to a lighting group. The first set of smart-home device registration information may include an indication of a location and the second set of smart-home device registration information may include the indication of the location.
In some embodiments, a system for integrating control of multiple cloud-based smart-home devices is described. The system may include a cloud-based host server system. The system may include an application executed by a mobile device. One or more processors of the cloud-based host server system and the mobile device may be configured to receive a first set of smart-home device registration information for a first smart-home device. At least one function of the first smart-home device may be controlled via communication with a first cloud-based server system. One or more processors of the cloud-based host server system and the mobile device may be configured to receive a second set of smart-home device registration information for a second smart-home device. At least one function of the second smart-home device may be controlled via communication with a second cloud-based server system distinct from the first cloud-based server system. One or more processors of the cloud-based host server system and the mobile device may be configured to determine that the first smart-home device and the second smart-home device share a common function. One or more processors of the cloud-based host server system and the mobile device may be configured to assign the first smart-home device controlled via communication with the first cloud-based server system and the second smart-home device controlled via communication with the second cloud-based server system to a common operating characteristic group based on the common function being shared by the first smart-home device and the second smart-home device. One or more processors of the cloud-based host server system and the mobile device may be configured to output a control element by the mobile device that allows for control of smart-home devices with the common operating characteristic group. The control element may control the common function at the first smart-home device via the first cloud-based server system and at the second smart-home device via the second cloud-based server system.
A further understanding of the nature and advantages of various embodiments may be realized by reference to the following figures. In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If only the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.
Smart-home devices may be controlled using a smart-home controller device. A smart-home controller device may be a wireless or mobile computerized device, such as a smartphone, tablet computer, laptop computer, dedicated home-controller device, or some other form of computerized device, that may execute an application that allows a user to control the functionality of one or more smart-home devices. The smart-home controller device may communicate with a cloud-based host server system. The cloud-based host system may communicate with various smart-home devices and may communicate with other cloud-based system to control smart-home devices that cannot be directly controlled by the cloud-based host system (e.g., smart devices manufactured and sold by other manufacturers).
The smart-home controller device may provide an interface that allows for smart-home devices to be controlled together and/or using a single input regardless of whether each smart-home device is controlled by the cloud-based host system or through another cloud-based system. The smart-home controller device may allow for smart-devices to be grouped based on location and/or function. Within such an arrangement, a common control element may be provided that allows a user to provide a single input that indicates a command that is to be implemented at multiple smart-home devices, regardless of whether the smart-home devices are controlled directly by the cloud-based host server system and/or through a separate cloud-based server system.
The smart-home controller device may additionally be configured to reclassify various types of smart-home devices based on user behavior. Such a reclassification may allow the smart-home controller device to determine when to send a command to a smart-home device more accurately and effectively. When a smart-home device is initially registered with the smart-home controller device or the registration is edited, a user may name the smart-home device and/or identify characteristics of the smart-home device. The words (and/or parts of words) submitted as part of the name may be compared to a smart-home device function database. The use of a particular word, part of a word, or phrase within a name of a smart-home device may be indicative of the smart-home device being used to perform a particular function. As an example, a smart outlet plug, if given the name of “dining room light” by a user, the smart outlet plug can be expected to control whether power is provided to a light located within the dining room. The smart-home controller device may classify the smart outlet plug in a lighting group (e.g., a dining room lighting group) because while the smart device is a smart outlet plug, it is effectively functioning as a controller for a light. Thus, if a user provides a command that indicates all of the lights within the dining room should be turned on or off, the smart-home controller device or cloud-based host server system may send the command to the smart outlet plug since it controls a light.
Additionally or alternatively, voice-based commands may be provided by a user to the smart-home controller device to control the functionality of multiple smart-home devices. The user may speak a command that does not correspond to a particular smart-home device or a predefined group of smart-home devices. For example, a user may say “turn on the dining room lights and the kitchen fan” or “turn off the dining room and the living room lights.” Embodiments detailed herein detail how a custom controller may be generated that controls at least one common function across all of the smart-home devices indicated in the spoken command. This interactive custom controller may allow a user to further change the state of the multiple smart-home devices that were the subject of the initial spoken command. The custom controller may include a graphical representation of a power button that, referring to the first example, controls both the dining room lights and the kitchen fan or, referring to the second example, all of the smart lights in the dining room and the living room. This custom controller may present some or all of the functions that all of the smart-home devices that were indicated in the spoken command have in common. Additionally or alternatively, the custom controller may present one or more functions that can only be performed at some of the smart-home devices indicated in the spoken command. For example, referring back to the example of the dining room lights and the kitchen fan, the custom controller may include a dimmer control that does not affect the state of the fan but allows at least a subset of the lights in the dining room to be dimmed via additional user input.
Further detail regarding the above embodiments and additional embodiments is provided in relation to the figures. While the following description is focused on smart-home devices, it should be understood that other forms of smart-devices may be controlled as detailed other than smart-home devices. For instance, smart devices in a factory, office, deployed in the field, or some other form of smart devices may be controlled as detailed herein.
Smart-home devices 110 represent various smart-home devices that may be present in a particular structure 105 (e.g., a home, an apartment, a condominium, an office, a warehouse, a factory, etc.). Smart-home devices 110 may have differing sensors on-board and may or may not have the ability to output information (e.g., via sound, light, or an electronic display). Specific forms of smart-home devices 110 are detailed in relation to
Smart-home devices 110 may have been acquired from varying sources. For example, a first entity (e.g., manufacturer) may produce smart-home devices 110-1 and 110-2, a second entity may produce smart-home device 110-3, and a third entity may produce smart-home devices 110-4 and 110-5. Such an arrangement in which smart-home devices from multiple entities is present within structure 105 may be fairly common: while a user may desire the feature set of one type of smart-home device, for another type of smart-home device, another entity may provide benefits that the user prefers.
Each smart-home device of smart-home devices 110 may communicate with a form of a cloud-based server system (120, 130). That is, each entity that provides smart-home devices may operate or have operated on its behalf a cloud-based server system that can receive data from its associated smart-home devices and send data (e.g., commands) to its associated smart-home devices. Cloud-based host server system 120 may communicate directly with smart-home devices 110-1 and 110-2. In this description, “directly” refers to the a server system communicating with a smart-home device via one or more networks without any additional intervening smart-home server systems. For example, the communication between smart-home device 110-1 and cloud-based host server system 120 may occur via a local wireless network (WLAN) provided by a router within structure 105. The router may be connected to an Internet service provider (ISP) that provides a wired or wireless communication link to the Internet. Cloud-based host server system 120 may be connected with the Internet, thus allowing data to be passed between smart-home device 110-1 and cloud-based host server system 120.
For other entities, separate cloud-based server systems may control associated smart-home devices: smart-home device 110-3 communicates directly with cloud-based server system 130-1 and smart-home devices 110-4 and 110-5 communicate directly with cloud-based server system 130-2. Cloud-based host server system 120 can additionally communicate with other cloud-based server systems 130 through one or more application programming interfaces (APIs). Therefore, cloud-based host server system 120 can receive data from and control smart-home devices 110-3 through 110-5, albeit not directly because communication via cloud-based server systems 130-1 and 130-2 is used. Further detail regarding cloud-based host server system 120 is provided in relation to
Smart-home controller devices 140 may serve as an interface for one or more users to interact with cloud-based host server system 120 to receive data from and control smart-home devices 110. Some or all of smart-home controller devices 140 may each receive auditory commands in the form of speech spoken by a user. Further, each of smart-home controller devices 140 may have a display or touchscreen that allows graphical user interfaces (GUIs) to be presented to the users. Smart-home controller devices 140 can include: smartphone 142; tablet computer 144; and laptop computer 146. Other forms of smart-home controller devices 140 may be possible, such as a dedicated smart-home device controller computerized device, a desktop computer, or a gaming device. Further detail regarding a smart-home controller device is provided in relation to
The depicted structure 250 includes a plurality of rooms 252, separated at least partly from each other via walls 254. The walls 254 can include interior walls or exterior walls. Each room can further include a floor 256 and a ceiling 258. Devices can be mounted on, integrated with and/or supported by a wall 254, floor 256 or ceiling 258.
In some embodiments, the smart-home environment 200 of
In some embodiments, the smart-home environment 200 of
In some embodiments, one or more smart indoor security cameras may be present such as indoor security camera 272. Indoor security camera 272 may wirelessly communicate with a cloud server system to capture and record video and audio. Indoor security camera 272 may be able to detect motion, recognize a resident (e.g., via facial detection), and detect the presence of a resident or other person via audio (e.g., detection of a human voice). Indoor and outdoor security cameras may be used to determine when a resident leaves home (for example, an OBM behavior may be a time range during the day when a resident typically leaves home, such as between 8 AM and 6 PM) or returns home. In some embodiments, as previously detailed, this data may be supplemented with location data derived from an electronic device, such as a smartphone, that a resident typically carries when going out. If the smartphone is forgotten by the resident, data from the cameras may be used to determine that the smartphone has been left behind and the resident has left the residence (e.g., a camera detects the resident leaving, the smartphone remains stationary in the residence, and there is no movement detected within the residence for a threshold period of time). When the environment is darkened, indoor security camera 272 may use infrared to detect the presence of a resident and/or other persons in the camera's field-of-view.
In some embodiments, one or more smart outdoor security cameras may be present such as outdoor security camera 276. Outdoor security camera 276 may wirelessly communicate with a cloud server system to capture and record video and audio and may function similarly to indoor security camera 272. Outdoor security camera 276 may include weatherproofing to protect against the outdoor environment. Outdoor security camera 276 may be able to detect motion, recognize a resident (e.g., via facial detection), and detect the presence of a resident or other person via audio (e.g., detection of a human voice). At night, outdoor security camera 276 may use infrared to detect the presence of a resident and/or other persons in the camera's field-of-view.
In some embodiments, one or more home assistant devices may be present in the residence, such as home assistant device 274. Home assistant device 274 may include one or more microphones. Home assistant device 274 may detect and analyze human speech and may be able to detect speech and/or movement by the resident. Clips of captured human speech may be provided to cloud-based host server system 120 for analysis. A response may be provide to home assistant device 274, which may output the response in the form of spoken audio. Cloud-based host server system 120 may cause one or more other smart-home devices in home environment 200 to perform a function based on a command identified from the received human speech.
Still further, in some embodiments, the smart-home environment 200 of
According to embodiments, the smart thermostats 202, the hazard detectors 204, the smart doorbells 206, the smart wall switches 208, the smart wall plugs 210, and other devices of the smart-home environment 200 are modular and can be incorporated into older and new houses. For example, the devices are designed around a modular platform consisting of two basic components: a head unit and a back plate, which is also referred to as a docking station. Multiple configurations of the docking station are provided so as to be compatible with any home, such as older and newer homes. However, all of the docking stations include a standard head-connection arrangement, such that any head unit can be removably attached to any docking station. Thus, in some embodiments, the docking stations are interfaces that serve as physical connections to the structure and the voltage wiring of the homes, and the interchangeable head units contain all of the sensors, processors, user interfaces, the batteries, and other functional components of the devices.
The smart-home environment 200 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 200 may include a pool heater monitor 214 that communicates a current pool temperature to other devices within the smart-home environment 200 or receives commands for controlling the pool temperature. Similarly, the smart-home environment 200 may include an irrigation monitor 216 that communicates information regarding irrigation systems within the smart-home environment 200 and/or receives control information for controlling such irrigation systems. According to embodiments, an algorithm is provided for considering the geographic location of the smart-home environment 200, such as based on the zip code or geographic coordinates of the home. The geographic information is then used to obtain data helpful for determining optimal times for watering; such data may include sun location information, temperature, due point, soil type of the land on which the home is located, etc.
By virtue of network connectivity, one or more of the smart-home devices of
As discussed, users can control and interact with the smart thermostat, hazard detectors 204, and other smart devices in the smart-home environment 200 using a network-connected computer or portable electronic device 266. In some examples, some or all of the occupants (e.g., individuals who live in the home) can register their electronic device 266 with the smart-home environment 200. Such registration can be made at cloud-based host server system 120 (or whichever cloud-based server system is associated with the entity that provided the smart-home devices to be controlled) 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 can use their registered electronic device 266 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 electronic devices 266, the smart-home environment 200 makes inferences about which individuals live in the home and are therefore occupants and which electronic devices 266 are associated with those individuals. As such, the smart-home environment “learns” who is an occupant and permits the electronic devices 266 associated with those individuals to control the smart devices of the home.
In some embodiments, in addition to containing processing and sensing capabilities, each of the devices 202, 204, 206, 208, 210, 212, 214, and 216 (collectively referred to as “the smart devices”) is capable of data communications and information sharing with any other of the smart devices, as well as to any central server or cloud-computing system or any other device that is network-connected anywhere in the world. The required data communications can be carried out using any of a variety of custom or standard wireless protocols (Wi-Fi, ZigBee, 6LoWPAN, etc.) and/or any of a variety of custom or standard wired protocols (CAT6 Ethernet, HomePlug, etc.)
According to embodiments, all or some of the smart devices can serve as wireless or wired repeaters. For example, a first one of the smart devices can communicate with a second one of the smart devices via a wireless router 260. The smart devices can further communicate with each other via a connection to a network, such as the Internet 299. Through the Internet 299, the smart devices can communicate with a cloud-computing system 264, which can include one or more centralized or distributed server systems. The cloud-computing system 264 can be associated with a manufacturer, support entity, or service provider associated with the device. For one embodiment, a user may be able to contact customer support using a device itself rather than needing to use other communication means such as a telephone or Internet-connected computer. Further, software updates can be automatically sent from cloud-computing system 264 to devices (e.g., when available, when purchased, or at routine intervals).
According to embodiments, the smart devices combine to create a mesh network of spokesman and low-power nodes in the smart-home environment 200, where some of the smart devices are “spokesman” nodes and others are “low-powered” nodes. Some of the smart devices in the smart-home environment 200 are battery powered, while others have a regular and reliable power source, such as by connecting to wiring (e.g., to 120V line voltage wires) behind the walls 254 of the smart-home environment. The smart devices that have a regular and reliable power source are referred to as “spokesman” nodes. These nodes are equipped with the capability of using any wireless protocol or manner to facilitate bidirectional communication with any of a variety of other devices in the smart-home environment 200 as well as with the cloud-computing system 264. On the other hand, the devices that are battery powered are referred to as “low-power” nodes. These nodes tend to be smaller than spokesman nodes and can only communicate using wireless protocols that require very little power, such as Zigbee, 6LoWPAN, etc. Further, some, but not all, 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 200, such as the spokesman nodes, cannot send information to these low-power nodes.
As described, the smart devices serve as low-power and spokesman nodes to create a mesh network in the smart-home environment 200. 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—repeat the messages, thereby causing the messages to travel from node to node (i.e., device to device) throughout the smart-home environment 200. The spokesman nodes in the smart-home environment 200 are able to “drop down” to low-powered communication protocols to receive these messages, translate the messages to other communication protocols, and send the translated messages to other spokesman nodes and/or cloud-computing system 264. Thus, the low-powered nodes using low-power communication protocols are able to send messages across the entire smart-home environment 200 as well as over the Internet 263 to cloud-computing system 264. According to embodiments, the mesh network enables cloud-computing system 264 to regularly receive data from all of the smart devices in the home, make inferences based on the data, and send commands back to one of the smart devices to accomplish some of the smart-home objectives described herein.
As described, the spokesman nodes and some of the low-powered nodes are capable of “listening.” Accordingly, users, other devices, and cloud-computing system 264 can communicate controls to the low-powered nodes. For example, a user can use the portable electronic device 266 (e.g., a smartphone) to send commands over the Internet to cloud-computing system 264, which then relays the commands to the spokesman nodes in the smart-home environment 200. The spokesman nodes drop down to a low-power protocol to communicate the commands to the low-power nodes throughout the smart-home environment, as well as to other spokesman nodes that did not receive the commands directly from the cloud-computing system 264.
An example of a low-power node is a smart nightlight 270. In addition to housing a light source, the smart nightlight 270 houses an occupancy sensor, such as an ultrasonic or passive IR sensor, and an ambient light sensor, such as a photoresistor or a single-pixel sensor that measures light in the room. In some embodiments, the smart nightlight 270 is configured to activate the light source when its ambient light sensor detects that the room is dark and when its occupancy sensor detects that someone is in the room. In other embodiments, the smart nightlight 270 is simply configured to activate the light source when its ambient light sensor detects that the room is dark. Further, according to embodiments, the smart nightlight 270 includes a low-power wireless communication chip (e.g., ZigBee chip) that regularly sends out messages regarding the occupancy of the room and the amount of light in the room, including instantaneous messages coincident with the occupancy sensor detecting the presence of a person in the room. As mentioned above, these messages may be sent wirelessly, using the mesh network, from node to node (i.e., smart device to smart device) within the smart-home environment 200 as well as over the Internet 299 to cloud-computing system 264.
Other examples of low-powered nodes include battery-operated versions of the hazard detectors 204. These hazard detectors 204 are often located in an area without access to constant and reliable (e.g., structural) power and, as discussed in detail below, may include any number and type of sensors, such as smoke/fire/heat sensors, carbon monoxide/dioxide sensors, occupancy/motion sensors, ambient light sensors, temperature sensors, humidity sensors, and the like. Furthermore, hazard detectors 204 can send messages that correspond to each of the respective sensors to the other devices and cloud-computing system 264, such as by using the mesh network as described above.
Examples of spokesman nodes include smart doorbells 206, smart thermostats 202, smart wall switches 208, and smart wall plugs 210. These devices 202, 206, 208, and 210 are often located near and connected to a reliable power source, and therefore can include more power-consuming components, such as one or more communication chips capable of bidirectional communication in any variety of protocols.
Further included and illustrated in the exemplary smart-home environment 200 of
As noted in relation to
Direct smart device control API 370 may be used to communicate directly with various smart-home devices. The smart devices controlled via direct smart device control API 370 may be manufactured or otherwise distributed by a same entity that operates or has cloud-based host server system 120 operated on its behalf. Through direct smart device control API 370, data from various smart-home devices may be received and commands may be transmitted to such smart-home devices. Direct smart device control API 370 may format commands appropriately for communication to smart devices and may format received data appropriately for analysis by smart device control engine 310. In contrast, smart device cloud API 360 may be used to communicate with various smart-home devices through other cloud-based server systems. The smart devices controlled via smart device cloud API 370 may be manufactured or otherwise distributed by a different entity than the entity that operates or has cloud-based host server system 120 operated on its behalf. Through smart device cloud API 360, data from various third-party smart-home devices may be received and commands may be transmitted to such third-party smart-home devices. Smart device cloud API 360 may format commands appropriately for communication to smart devices and may format received data appropriately for analysis by smart device control engine 310. Therefore, smart device cloud API 360 may have access to a library of command types and data types available for each third-party smart device.
Controller communication interface 320 may communicate with various smart-home controller devices. Through controller communication interface 320, requests for a command to be executed by one or more smart-home devices may be received. In some situations, the command may be intended to be executed by one or more smart-home devices directly communicated with by cloud-based host server system 120 via direct smart device control API 370 and one or more smart devices indirectly communicated with via smart device cloud API 360. Controller communication interface 320 may also be used by smart device control engine 310 to send information about data received from smart devices that communicate with cloud-based host server system 120 via smart device cloud API 360 and direct smart device control API 370.
Smart device control library 380 may be a library of the various functions that can be performed using smart devices that are directly communicated with via direct smart device control API 370. When a type of smart device is registered with cloud-based host server system 120, smart device control library 380 may be accessed to determine the particular functions which the smart device can perform and the particular commands available to be transmitted to smart-device control library 380.
Smart device and account databases 390 may serve to store indications of smart-home devices that have been registered with cloud-based host server system 120 with a particular user account. Requests to control a smart-home device received via controller communication interface 320 may be required to be linked with the same user account as indicated in smart device an account databases 390 for security purposes. Therefore, a user may only have permission to control the smart-home devices that have been linked to the user's account. In some embodiments, a user name and password is required to access the user account. In other embodiments, additional security measures may be taken, such as biometrics or two-factor identification. One or more smart device an account databases 390 may also store indications of third-party smart-home devices that have been registered with cloud-based host server system 120.
Audio communication interface 330 may serve to receive an audio clip captured by a smart-home controller, home assistant device, or some other smart-home device through which a user can submit a spoken command. Semantics engine 340 may perform natural language processing to determine what the user said, possibly including: a command; and the device for which the command is intended. Synthesized voice responses may be provided in response to the user via audio communication interface 330.
Vocal or spoken commands that are not directed to smart-home devices may be processed by assistant engine 350. For example, such spoken commands may be requesting data from some other source, such as the Internet. As an example, a request may be for weather information, the time, sports scores, a translation, a stock quote, calendar information, etc. semantics engine 340 may route smart-home device requests to smart device control engine 310.
Smart device control engine 310 may receive commands from controller communication interface 320 and as interpreted by semantics engine 340. Smart device control engine 310 may access smart device and account databases 390 to determine the smart devices associated with a particular account. Smart-device control engine may determine the appropriate smart-home devices to transmit a command and may transmit the command via smart device cloud API 360 (to the corresponding cloud-based server system that communicates directly with the smart-home device) and via direct smart device control API 370. Smart device control engine 310 may send smart device identifiers indicative of the smart devices that have been sent a command based on a spoken command to the smart-home controller via controller communication interface 320. Therefore, smart-home controller may receive information identifying the smart-home devices that were affected by a spoken command.
Smart-home control application 410 may include: smart-home control interface creation engine 420; smart-home device registration engine 430; customized controller interface generation engine 440; voice-based assistant engine 450; function-specific term database 460; and smart-home device function database 470. Smart-home device registration engine 430 may receive information about a new smart-home device that is the registered with smart-home control application 410 and cloud-based host server system 120, regardless of whether the smart-home device is directly controlled by cloud-based host server system or controlled via another cloud-based server system. As part of the registration process, a user may be requested to provide information about the smart-home device. For example, the user may be requested to provide a name for the smart-home device. The user may typically name the smart-home device based on the function performed by the smart-home device and the location. For example, a user may select a name such as “kitchen light” to describe a smart light in the kitchen. As another example, “kitchen light” may be used for a smart outlet plug in the kitchen to which a conventional light is connected. Registration data received by smart-home device registration engine 430 may be stored locally and may also be transmitted to cloud-based host server system 120. Functions that can be performed by the smart-home device may be discovered during the smart-home device registration process. Indications of such functions may be stored to smart-home device function database 470 in association with an identifier of the smart-home device. Indications of the available functions may be retrieved from the cloud-based host computer system. For third-party smart-home devices, the cloud-based host computer system may request and retrieve indications of such functions from the cloud-based server system operated by the entity that provided the third-party smart-home device. Alternatively, the cloud-based host server system may maintain a database of available functions of third-party smart-home devices.
When the user provides a name for a smart-home device as part of the registration process, if the ultimate function of the smart-home device is not inherently determined by the type of smart device itself, function-specific term database 460 may be used to determine the intended use of a smart-home device from the user's name for the smart-home device. For example, a smart outlet plug can be used to control a variety of types of devices, such as a legacy appliance, a light, electronics, etc. A user may be expected to name the smart outlet plug something related to the device it is controlling, such as “bedroom window fan” or “dining room light.” Function specific term database may store a variety of terms that are linked to a specific category of smart-home device. Table 1 provides some examples of terms and the associated smart-home device categories.
TABLE 1
Function-Specific Term
Smart-home Device Category
Light
lighting
Lamp
Lighting
Bulb
Lighting
Speaker
Music/sound output
Stereo
Music/sound output
If, during the registration process, a user provides a function specific term in the name of the smart-home device that performs an ambiguous function, based on the function specific term being present, smart-home device registration engine 430 may classify the smart-home device as being part of the smart-home device category mapped to the function specific term. For example, a smart outlet plug that has been named “dining room lamp” may be classified as part of the lighting smart-home device category. While
Voice-based assistant engine 450 may function similarly to voice-based assistant engine 480, but may be incorporated as part of smart-home control application 410 and may specifically be used for providing smart-home related commands. Voice-based assistant engine 450 may capture an audio clip via a microphone of the smart-home controller device 140 in response to a user saying a trigger phrase or providing some form of user input indicating that the user desires to provide a voice-based command. The captured audio may be transmitted from voice-based assistant engine 450 to audio communication interface 330 of cloud-based host server system 120. The audio may be analyzed at the cloud-based host server system rather than at smart-home controller device 140. In response to sending the captured audio, voice-based assistant engine 450 may receive a response from the cloud-based host computer system indicating the smart-home identifiers of the smart-home devices that were sent to command based on a spoken command in the captured audio. The response may also indicate the updated state of the smart-home devices to which the command was sent.
Smart-home control interface creation engine 420 may create graphical interfaces that can be interacted with by user via a touchscreen or other form of user input device and is presented by smart-home controller device 140 or otherwise output for presentation (e.g., to a separate monitor). Smart-home control interface creation engine 420 may create an output user interfaces such as those detailed in relation to
Smart-home device function database 470 may store an indication of each smart-home device that is controlled via smart-home control application 410 and the functions that can be performed at each of the smart-home devices. For example, many smart-home devices may be able to be turned on and off, some smart lights may be able to be dimmed, smart thermostats may be able to receive a temperature setting, etc. smart-home device function database 470 may be accessed by smart-home control interface creation engine 420 to determine the functions that can be performed by a particular smart-home device. Smart-home control interface creation engine 420 may access smart-home device function database 470 to determine what functions are in common across particular smart-home devices such that a single control can be presented that controls multiple smart-home devices, even if some of such smart-home devices are provided by different entities and are controlled via different cloud-based server systems.
Customized controller interface generation engine 440 may be used in conjunction with voice-based assistant engine 450. In response to a voice command, voice-based assistant engine 450 may receive smart device identifiers for the smart devices affected by a spoken command. When these smart device identifiers are received, the identifiers may be passed to customized controller interface generation engine 440. Customized controller interface generation engine 440 may access smart-home device function database 470 to determine one or more functions that each of the smart-home devices have in common. A graphical control may be created that allows a user to control the same group of smart-home devices that was indicated in the spoken command. This control may include at least one common function across each of the smart-home devices. The control may also include one or more functions that are specific to a subset of the smart-home devices that was indicated in the spoken command. Therefore, customized controller interface generation engine 440 may generate a graphical interface after a spoken command has been submitted via voice-based assistant engine 450 and may allow a user to provide user input in the form of touch or some other form of on-screen control for the same set of smart-home devices that was previously controlled via a vocal command. Additionally or alternatively, customized controller interface generation engine 440 may be used with voice-based assistant engine 480.
Top interface region 510 is devoted to whole-home smart-device controls. Top interface region 510 is labeled with location 505 that is indicative of the entire structure or other form of place where the smart-home devices are installed. Controls with top interface region 510 can include: off element 511; on element 512; play element 513; thermostat element 514; camera element 515; add element 516; and settings element 517.
The controls indicated by elements 511-516 pertain to smart-home devices controlled directly via the cloud-based host server system and third-party smart-home devices controlled by the cloud-based host server system via another cloud-based server system operated by another entity. Off element 511, when selected by a user, may trigger the smart-home control application to instruct the cloud-based host server system to turn off all lighting-related smart-home devices at location 505 that are located in lower location subcategories. (In other embodiments, when off element 511 is selected, a choice may be presented as to whether to turn off lighting-related devices for a given room or within the entire structure.) On element 512, when selected by a user, may trigger the smart-home control application to instruct the cloud-based host server system to turn on all lighting-related smart-home devices at location 505 that are located in lower location subcategories. (In other embodiments, when on element 512 is selected, a choice may be presented as to whether to turn off lighting-related devices for a given room or within the entire structure.) Play element 513, when selected by a user, may trigger the smart-home control application to instruct the cloud-based host server system to play or cease playing sound via eligible smart-home devices at location 505 that are located in lower location subcategories. Thermostat element 514, when selected by a user, may trigger the smart-home control application to instruct the cloud-based host server system to adjust the temperature or adjust an away/home setting at all smart thermostats installed in location 505 that are located in lower location subcategories. Camera element 515, when selected by a user, may trigger the smart-home control application to instruct the cloud-based host server system to stream video feeds to the smart-home control device for presentation from all cameras installed at location 505 that are located in lower location subcategories. Add element 516 may allow an additional function to be added to top interface region 510 based on one or more smart-home devices present in lower location subcategories. Alternatively, add element 516 may be used to link or register a new device. Settings element 517, when selected by a user, may trigger the smart-home control application to present various settings that a user is permitted to adjust for controlling smart-home devices located in lower location subcategories.
Based on received registration information received from a user via smart-home device registration engine 430, smart-home devices may be classified into one or more location subcategories. Location subcategories may be presented within control interface 500 at a lower location than top interface region 510. A first location subcategory presenting in control interface 500 is location subcategory 520 that has location 521 of “Attic.” A user may specify location 521 and indicate which smart-home devices are installed at location 521. All smart-home devices indicated as being at location 521 are included in location subcategory 520. In the illustrated embodiment, three smart-home devices (of which at least some may be third-party smart-home devices) is indicated by smart-home device count 522, which is presented near location 521. In the illustrated embodiment, two lights are present at location 521, therefore control element 524, which may also be referred to as a control “coin” or “tile” is presented that includes: 1) a graphic that represents a group of the type of smart-home device and may be selected to present control elements for the individual lights; 2) a title of the group of lights (“Attic lights”), and control elements that allow the group of lights to be controlled using a single user input (by a user selecting “off” or “on”). Additionally, location subcategory 520 may include a smart-home device (in this case, a home assistant device) that can be used as a speaker. Control element 523 include: 1) a graphic element that represents the type of smart-home device; and 2) a user-assigned title of the smart-home device. Additional location subcategories may be presented by control interface 500 by a user scrolling down, such as seen in the embodiment of
Additionally present in control interface 500 is spoken command control element 530. By a user selecting audio command control element 530, voice-based assistant engine 450 may be activated to capture audio using a microphone of smart-home controller device 140. This audio may be transmitted to cloud-based host server system 120 for analysis. When a user scrolls up or down within control interface 500, spoken command control element 530 remains fixed on control interface 500 such that while smart-home control application 410 is open, the user has an on-screen option to provide a spoken command to control the smart-home devices.
Location subcategory 620 which corresponds to location 621 only includes one smart-device as indicated by smart-device count 622. Control element 623 visually represents a smart door lock and indicates the current state of the door lock (unlocked).
Control element 703 comprises a graphical representation of a smart outlet plug. This smart outlet plug may have been grouped as part of the smart lights of location 611 on the basis of the name for the smart outlet plug provided for a user including the word “lamp.” The graphical representation may remain as a smart outlet plug. In some embodiments the smart outlet plug is included as part of location 611 based on the word “dining” being used as part of the user-provided name.
Various methods may be performed using the systems and control interfaces of
At block 905, the smart-home control application 410 may receive registration for a first smart-home device by the smart-home control application or the registration information may be received by the cloud-based host server system. This smart-home device may be associated with the manufacture or entity that operates cloud-based host server system 120. Therefore, the first smart-home device may be controlled via direct smart device control API 370. As part of the registration process, the user may provide a user-defined name for the smart-home device. The user may, additionally or alternatively, provide a location that indicates a room or other area within or at a structure where the first smart-home device is located or will be located. In some embodiments, the location is selected from a predefined list of locations available within smart-home control application 410. For example, smart-home control application 410 may list the names of rooms that are commonly found within a residential home. In other embodiments, a user may specify a custom name for the location. In still other embodiments, the location at which the smart-home device was installed may be inferred from a name for the smart-home device defined by the user. For example, if the name includes the word “dining” it may be determined that the first smart-home device is installed in a dining room. The registration information may also include an identifier of the smart-home device which can be used to register the smart-home device with the cloud-based host computer system and, if necessary, with the cloud-based server system with which the cloud-based host computer system can communicate. In some embodiments, the cloud-based host computer system may return in indication of the type of smart device being registered and functions that the smart-home device is capable of performing. For the purposes of the remainder of method 900, it is assumed that the first smart-home device was registered with the cloud-based host computer system and the first smart-home device communicates directly with the cloud-based host computer system.
At block 910, registration information for a second smart-home device may be received by the smart-home control application or the registration information may be received by the cloud-based host server system. Registration for the second smart-home device may proceed similarly to block 910. In the illustrated embodiment of method 900, the second smart-home device is controlled via a cloud-based server system distinct from the cloud-based host server system. Therefore, when the second smart-home devices registered with the cloud-based host server system, the cloud-based host server system may provide at least some of the registration information to the cloud-based server system. In response, the cloud-based server system may provide indications of functions that may be performed by the second smart-home device. For the purpose of method 900, the first smart-home device and the second smart-home device are of a same type (e.g., are both types of smart lights) and have at least one function in common, such as both devices can be turned on and off (e.g., a “power function”). However, the first smart-home device in the second smart-home device are provided by different manufacturers or entities and are controlled using different cloud-based systems.
At block 915, a determination may be made by the smart-home control application 410 that a common function exists for the first smart-home device and the second smart-home device. In some embodiments, block 915 may be performed by the cloud-based host server system. This determination may be made by comparing a list of available functions for the first smart-home device determined during the registration of block 905 and the list of available functions for the second smart-home device determined during the registration of block 910. Block 915 may only be performed if the first smart-home device and the second smart-home device are determined to be of the same type (e.g., lights, speakers, locks, fans, thermostats, etc.). Block 915 may further include determining that the first smart-home device in the second smart-home device are being or have been installed at the same location (e.g., within a same room).
At block 920, the first smart-home device and the second smart-home device may be assigned to a common operating characteristic group by the smart-home control application. In some embodiments, block 920 may be performed by the cloud-based host server system. In some embodiments, the first smart-home device in the second smart-home device may be assigned to multiple common operating characteristic groups. For example, a first common operating characteristic group may be created for all smart-home devices of the same type within a structure. For example, such an arrangement may allow a control element such as element 511 and element 512 to control all smart lights within a structure. Alternatively or additionally, a second common operating characteristic group may be created for all smart-home devices of the same type within a particular location at a structure. For example, such an arrangement may allow for a control element such as control element 613 to control all smart lights in the dining room, regardless of the entity that provided the smart light.
At block 925, the smart-home control application may provide a control element that includes a control for allowing a user to control the common function determined at block 915. Therefore, by a user providing a single input to the control, the user can adjust a function or setting of multiple smart-home devices. In the example of method 900, the single input may adjust a function at the first smart-home device in the second smart-home device, which are controlled via different cloud-based systems.
At block 930, user input may be received to the control of the control element that allows a user to control the common function. A single instance of user input may be received at block 930, such as a single touch or a single click. As an example, referring to control element 613, a user may touch the “on” control to turn three smart lights on or the “off” control to turn three smart lights off In this example, “on” and “off” would be common functions across the multiple smart lights. At block 935, the smart-home control application may cause the smart-home controller device to transmit a message to the cloud-based host system that indicates smart-home device identifiers of the first smart-home device in the second smart-home device (and any other smart-home devices that are of the same type, and, possibly location). The message may also include an indication of the command or function to be performed by each of the smart-home devices. In some embodiments, the user input may be provided to a device other than the device executing the smart-home control application. For instance, the user input may be provided to the cloud-based host server system.
At block 940, in response to the received message, the cloud-based host server system may cause the first smart-home device to perform the commander function. This may be performed by the cloud-based host server system communicating with the first smart-home device via direct smart device control API 370. Additionally, in response the received message, the cloud-based host server system may send an indication of the second smart-home device identifier and the command or function to a cloud-based server system that communicates with the second smart-home device. The cloud-based server system may then instruct the second smart-home device to perform the command or function. Therefore, by user providing a single user input at block 930, smart devices controlled via different cloud-based server systems may each be controlled. In some embodiments, the cloud-based server system may provide an acknowledgment as to whether the second smart-home device performed the command or function to the cloud-based host system. Additionally or alternatively, the cloud-based host server system may provide an acknowledgment to the smart-home control application indicating whether the function or command has been performed by the first smart-home device and/or the second smart-home device. Such an acknowledgment may permit presentation of an interface of the smart-home control application to be updated to reflect the current state of the first and second smart-home devices.
At block 1010, registration information may be received for a first smart-home device, as in block 905 of
At block 1020, a determination may be made at the first smart-home devices eligible to perform multiple of functions. Block 1020 may be performed by the smart-home application or by the cloud-based host server system. Which functions may be performed by the first smart-home device may be based on inquiry being made to the cloud-based host server system or a cloud-based server system which communicates with the cloud-based host server system. In other embodiments, a database may be maintained locally by the smart-home control application that indicates the available functions of various types of smart-home devices. An identifier of the first smart-home device may be used by either the smart-home host server system or the smart-home control application to perform a lookup within the database. As an example, a smart outlet plug may be considered one type of smart-home device that is eligible to perform multiple types of functions. The smart-home outlet plug may be able to turn on and off a device that is plugged into the smart-home all the plug. Therefore, the function of first smart-home device may be considered to be the function of whatever devices plugged into the smart-home outlet plug. Typical devices that may be plugged into the smart-home all the plug may be a light, a fan, or a small appliance (e.g., coffee maker, toaster oven, etc.).
Based on block 1020 being determined that the first smart-home devices eligible to perform multiple types of functions, a comparison may be made at block 1030 to compare the user-defined name received at block 1010 with the database of function specific terms. The database a function specific terms may be similar to those presented in Table 1. The comparison of block 1030 may be performed locally by the smart-home controller application or may be performed remotely by the cloud-based host server system. Block 1030 may be performed by the smart-home application or by the cloud-based host server system.
At block 1040, based on the comparison of block 1030, a determination may be made as far as the intended function of the first smart-home device. Block 1040 may be performed by the smart-home application or by the cloud-based host server system. Therefore, while the first smart-home device may be of a first type, the way the first smart-home devices being used may be more accurately described based on its intended function. As an example of this consider a smart-home outlet plug that is connected with a light. From a user's point of view, the first smart-home device is causing the light to function as a smart light. Therefore, the smart-home outlet plug may have its intended function be determined as lighting.
At block 1050, the first smart-home device may be grouped with a second smart-home device based on the intended function of the first smart-home device matching the function of the second smart-home device by the smart-home application or by the cloud-based host server system. Returning to the previous example, the smart outlet plug may be grouped with a smart light (the second smart-home device) due to the intended function of the first smart-home device matching the function of the smart light. Another example of this can be seen in
Additionally, grouping may be further based on location within a structure. For example, a smart outlet plug may only be grouped with a second smart-home device that matches the smart outlet plug's intended function if the smart-home outlet plug in the second smart-home device are indicated as being present at a same location. In some embodiments, similar to the user defined name being analyzed for an intended function using a database of function specific terms, the user defined name may be analyzed for an intended location using a database of location names. Therefore, rather than a user selecting a location from a list or otherwise providing a specific location, the user defined name may be used to determine the location.
As detailed in relation to
In some embodiments, one or more additional control elements may be present. In this embodiment, control element 1312 is present, which is a dimmer control that allows for some or all of the controlled smart-home devices to have their brightness controlled. By control element 1312 being present, this is an indication that at least one of the smart-home devices controlled via the spoken command can have its brightness controlled. In some embodiments, control element 1312 may only be presented and available if this function is available across all smart-home devices controlled by the spoken command indicated by representative text 1201.
At block 1505, a local recording may be captured using the smart-home controller device that includes a spoken command intended by the user to be directed to multiple smart-home devices. Alternatively, the recording may be captured using some other device. These multiple smart-home devices may be spread among multiple locations or concentrated at a particular location. These multiple smart-home devices may also represent a subset of smart-home devices located at a particular location. The multiple smart-home devices may be of different types or of the same type. The multiple smart-home devices may include smart-home devices that are directly controlled by the cloud-based host server system and may include smart-home devices that are controlled by the cloud-based host server system via another cloud-based server system. Therefore, the user has considerable flexibility in the smart-home devices that can be controlled using a single spoken command. As previously detailed the smart-home controller device may be ready to receive a spoken command when an interface similar to that of audio command control 1100 is presented.
At block 1510, the vocal recording may be transmitted to the cloud-based host server system to analyze the contents and meaning. In other embodiments, the vocal recording may be analyzed locally. The vocal recorded captured at block 1505 may be transmitted as the audio is received to the cloud-based host server system to allow for analysis as the voice recording is still being received. At block 1515, the vocal recording may be translated from audio into text by the cloud-based host server system. In other embodiments, the vocal recording may be analyzed locally by the smart-home controller device. A semantics engine may analyze the intended meaning of the text including the command to be performed the smart-home devices at which the command is intended to be executed.
At block 1520, the command may be transmitted to the smart-home devices determined at block 1515. The command may be transmitted to smart-home devices with which the cloud-based host server system directly communicates and smart-home devices with which the smart-home host server system communicates with via another cloud-based server system. In some embodiments, the smart-home controller device may communicate directly with the cloud-based host server systems associated with various smart-home devices. At block 1525, a response may be transmitted to the smart-home controller device at which the vocal recording was initially received. The response may indicate smart-home device identifiers indicative of each smart-home device to which the command was transmitted by the smart-home host server system. Therefore, if the smart-home host server system sent the command to six smart-home devices, six smart-home identifiers would be transmitted to the smart-home controller device. In some embodiments, rather than the smart-home devices being controlled via cloud-based server systems, the smart-home controller device may communicate with and control the smart-home devices directly (e.g., via a direct wireless communication method or via a mesh network).
At block 1530, the smart-home device identifiers may be received and then analyzed by the smart-home control application being executed by the smart-home controller device. Each of the smart-home device identifiers may be used to identify the associated smart-home devices and access a smart-home device function database to determine what one or more functions (or intended functions) each smart-home device is capable of. This analysis may include determining if there are one or more functions in common across all of the smart-home devices that were controlled via the spoken command this analysis may also include determining if there one or more functions in common across some of the smart-home devices that were controlled via the spoken command. (In other embodiments, such a function may be present at only one of the smart-home devices that were previously controlled via the voice-based command.) In some embodiments, rather than the analysis of block 1530 being performed at the application executed by the smart-home controller device, the analysis may be performed by the cloud-based host server system to determine what functions each device is capable of and determine if one or more functions are in common across the smart-home devices.
If there is at least one function that is in common across all of the smart-home devices that were controlled via the spoken command, a custom interface controller may be generated at block 1535 that includes one or more controls that allow for user control of the one or more common functions of the smart-home devices that were the subject of the spoken command. This custom interface controller may not have been available to a user via the application prior to block 1535. For example, no interface controller may be available that controls lights in two distinct rooms. Therefore, block 1530 results in the creation of an interface at block 1535 that otherwise would not exist or be available. The custom interface controller may also include one or more controls that control one or more functions that are in common across some of the smart-home devices that were controlled via the spoken command. Therefore, the presented custom interface controller allows a user to provide additional input to control the smart-home devices that were previously controlled via a voice-based command. In some embodiments, even if there is not one function in common across the smart-home devices indicated by the spoken command, a custom interface controller may be generated that includes a control for a majority of the smart-home devices controlled via the spoken command.
Using the custom interface controller generated at block 1535 that is being output for presentation, a user may provide user input (e.g., via touch) to further control all or some of the smart-home devices previously controlled via the spoken command. In response to such further input, the smart-home control application may determine one or more commands to be performed by the smart-home devices. The command, along with the smart-home device identifiers indicative of the smart-home devices that are to perform the command may be transmitted to the cloud-based host server system for execution. The cloud-based host server system then may control one or more smart-home devices directly and/or may communicate with one or more other cloud-based server systems to control the corresponding smart-home devices.
The methods, systems, and devices discussed above are examples. Various configurations may omit, substitute, or add various procedures or components as appropriate. For instance, in alternative configurations, the methods may be performed in an order different from that described, and/or various stages may be added, omitted, and/or combined. Also, features described with respect to certain configurations may be combined in various other configurations. Different aspects and elements of the configurations may be combined in a similar manner. Also, technology evolves and, thus, many of the elements are examples and do not limit the scope of the disclosure or claims.
Specific details are given in the description to provide a thorough understanding of example configurations (including implementations). However, configurations may be practiced without these specific details. For example, well-known circuits, processes, algorithms, structures, and techniques have been shown without unnecessary detail in order to avoid obscuring the configurations. This description provides example configurations only, and does not limit the scope, applicability, or configurations of the claims. Rather, the preceding description of the configurations will provide those skilled in the art with an enabling description for implementing described techniques. Various changes may be made in the function and arrangement of elements without departing from the spirit or scope of the disclosure.
Also, configurations may be described as a process which is depicted as a flow diagram or block diagram. Although each may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be rearranged. A process may have additional steps not included in the figure. Furthermore, examples of the methods may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware, or microcode, the program code or code segments to perform the necessary tasks may be stored in a non-transitory computer-readable medium such as a storage medium. Processors may perform the described tasks.
Having described several example configurations, various modifications, alternative constructions, and equivalents may be used without departing from the spirit of the disclosure. For example, the above elements may be components of a larger system, wherein other rules may take precedence over or otherwise modify the application of the invention. Also, a number of steps may be undertaken before, during, or after the above elements are considered.
Chung, Henry, Conover, Christopher, Williams, Lisa, Brown, Benjamin, Huang, Da
Patent | Priority | Assignee | Title |
Patent | Priority | Assignee | Title |
10091015, | Dec 16 2014 | Microsoft Technology Licensing, LLC | 3D mapping of internet of things devices |
20080062965, | |||
20120023157, | |||
20120310386, | |||
20140098247, | |||
20140176314, | |||
20150222517, | |||
20150341227, | |||
20160241660, | |||
20160261425, | |||
20160316007, | |||
20160330042, | |||
20170076523, | |||
20170185757, | |||
20170357425, | |||
20170359423, | |||
20180087795, | |||
20180108351, | |||
20180123818, | |||
20180213077, | |||
20180301148, | |||
20180357847, | |||
20190019504, | |||
20190311721, | |||
20200090068, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Oct 02 2018 | HUANG, DA | GOOGLE LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 047096 | /0517 | |
Oct 02 2018 | CONOVER, CHRISTOPHER | GOOGLE LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 047096 | /0517 | |
Oct 03 2018 | WILLIAMS, LISA | GOOGLE LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 047096 | /0517 | |
Oct 03 2018 | CHUNG, HENRY | GOOGLE LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 047096 | /0517 | |
Oct 05 2018 | BROWN, BENJAMIN | GOOGLE LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 047096 | /0517 | |
Oct 08 2018 | GOOGLE LLC | (assignment on the face of the patent) | / |
Date | Maintenance Fee Events |
Oct 08 2018 | BIG: Entity status set to Undiscounted (note the period is included in the code). |
Date | Maintenance Schedule |
Apr 26 2025 | 4 years fee payment window open |
Oct 26 2025 | 6 months grace period start (w surcharge) |
Apr 26 2026 | patent expiry (for year 4) |
Apr 26 2028 | 2 years to revive unintentionally abandoned end. (for year 4) |
Apr 26 2029 | 8 years fee payment window open |
Oct 26 2029 | 6 months grace period start (w surcharge) |
Apr 26 2030 | patent expiry (for year 8) |
Apr 26 2032 | 2 years to revive unintentionally abandoned end. (for year 8) |
Apr 26 2033 | 12 years fee payment window open |
Oct 26 2033 | 6 months grace period start (w surcharge) |
Apr 26 2034 | patent expiry (for year 12) |
Apr 26 2036 | 2 years to revive unintentionally abandoned end. (for year 12) |