Patent Grant
10649421
This relates generally to protecting children in a home or other dwelling by disabling potential hazards and/or by providing child-protection alerts.
Various elements in a home or other dwelling, such as unused electrical outlets, may present a hazard to young children and other vulnerable persons. Typically, these hazards are avoided by not leaving children unattended in the first place. However, there may be situations where children are left unattended within the home due to circumstances beyond a parent or guardian's control. In these situations, the parent or guardian may not have had the opportunity to make safe those potentially hazardous elements, thus putting the unattended children at risk.
Accordingly, there is a need for improved devices and methods for protecting unattended children in a home or other structure. Such devices and methods optionally complement or replace conventional methods for protecting unattended children in a home or other structure.
In accordance with some embodiments, a method is performed at a computing system. The method includes receiving occupancy data for a room in a dwelling from one or more sensors in the room. The room includes one or more unused electrical outlets and/or one or more electronically-controlled door handles. Whether a predetermined child-protection condition is met is determined based at least in part on the received occupancy data for the room. In accordance with a determination that the predetermined child-protection condition is met, at least one of the one or more unused electrical outlets and/or at least one of the one or more electronically-controlled door handles in the room are disabled, or instructions to disable same are sent.
In accordance with some embodiments, a computing system includes one or more processors and memory. The memory stores one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for performing the operations of any of the methods described above. In accordance with some embodiments, a non-transitory computer readable storage medium has stored therein instructions which when executed by a computing system with one or more processors, cause the computing system to perform the operations of any of the methods described above. In accordance with some embodiments, a computing system includes means for performing the operations of any of the methods described above.
Thus, computing systems are provided with improved methods for protecting unattended children in the home, thereby increasing the effectiveness, efficiency, and user satisfaction with such systems. Such methods may complement or replace conventional methods for protecting unattended children in the home.
For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
As noted above, there is a need for improved devices and methods for protecting unattended children in the home or other structure. Here, a computing system disables, or sends instructions to disable, unused electrical outlets and/or door handles in a room in a dwelling in response to a determination that a child-protection condition has been met. This determination is based at least in part on occupancy data for the room. The occupancy data may indicate, for example, that a child is alone in a room for at least some amount of time. A safety hazard thus exists that merits disabling of the unused electrical outlets and/or door handles in the room.
Furthermore, the computing system may adjust the child-protection condition used to determine whether to disable the unused outlets/door handles based on feedback from requests to cancel the disablements of the unused outlets/door handles. For example, if an occupant's request to cancel a disablement is of a type that indicates that the disablement is a false alarm, the child-protection condition may be changed to reduce the likelihood of another false alarm (e.g., lengthening the amount of time that a child is alone in the room before disabling the unused outlets/door handles). Conversely, if an occupant's request to cancel a disablement is of a type that indicates that the disablement was proper, but should have been given sooner, the child-protection condition may be changed to shorten the amount of time that a child is alone in the room before disabling the unused outlets/door handles. Thus, the child-protection condition changes with time so that more accurate disablements are performed, with fewer instances of unneeded disablements or late disablements.
Furthermore, the computing system may generate a child-protection alert in response to a determination that a child-protection alert condition has been met. The child-protection alert condition may the same as, or different from, the child-protection condition that triggers disablement of the unused outlets/door handles. The computer system may also, analogous to the adjustment of the child-protection condition, adjust the condition used to determine whether to provide a child-protection alert based on feedback from requests to cancel the child-protection alerts. Thus, the child-protection alert condition changes with time so that more accurate child-protection alerts are provided, with fewer instances of unneeded alerts or late alerts.
Below,
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various described embodiments. However, it will be apparent to one of ordinary skill in the art that the various described embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
It will also be understood that, although the terms first, second, etc. are, in some instances, used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first type of request could be termed a second type of request, and, similarly, a second type of request could be termed a first type of request, without departing from the scope of the various described embodiments. The first type of request and the second type of request are both types of requests, but they are not the same type of request.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting” or “in accordance with a determination that,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event]” or “in accordance with a determination that [a stated condition or event] is detected,” depending on the context.
It is to be appreciated that “smart home environments” may refer to smart environments for homes such as a single-family house, but the scope of the present teachings is not so limited. The present teachings are also applicable, without limitation, to duplexes, townhomes, multi-unit apartment buildings, hotels, retail stores, office buildings, industrial buildings, and more generally any living space or work space.
It is also to be appreciated that while the terms user, customer, installer, homeowner, occupant, guest, tenant, landlord, repair person, and the like may be used to refer to the person or persons acting in the context of some particularly situations described herein, these references do not limit the scope of the present teachings with respect to the person or persons who are performing such actions. Thus, for example, the terms user, customer, purchaser, installer, subscriber, and homeowner may often refer to the same person in the case of a single-family residential dwelling, because the head of the household is often the person who makes the purchasing decision, buys the unit, and installs and configures the unit, and is also one of the users of the unit. However, in other scenarios, such as a landlord-tenant environment, the customer may be the landlord with respect to purchasing the unit, the installer may be a local apartment supervisor, a first user may be the tenant, and a second user may again be the landlord with respect to remote control functionality. Importantly, while the identity of the person performing the action may be germane to a particular advantage provided by one or more of the embodiments, such identity should not be construed in the descriptions that follow as necessarily limiting the scope of the present teachings to those particular individuals having those particular identities.
The depicted structure 150 includes a plurality of rooms 152, separated at least partly from each other via walls 154. The walls 154 may include interior walls or exterior walls. Each room may further include a floor 156 and a ceiling 158. Devices may be mounted on, integrated with and/or supported by a wall 154, floor 156 or ceiling 158.
In some embodiments, the integrated devices of the smart home environment 100 include intelligent, multi-sensing, network-connected devices that integrate seamlessly with each other in a smart home network (e.g., 202
In some embodiments, the one or more smart thermostats 102 detect ambient climate characteristics (e.g., temperature and/or humidity) and control a HVAC system 103 accordingly. For example, a respective smart thermostat 102 includes an ambient temperature sensor.
In some embodiments, the one or more smart hazard detectors 104 may detect the presence of a hazardous substance or a substance indicative of a hazardous substance (e.g., smoke, fire, and/or carbon monoxide). In some embodiments, the one or more smart hazard detectors 104 may include thermal radiation sensors directed at respective heat sources (e.g., a stove, oven, other appliances, a fireplace, etc.). For example, a smart hazard detector 104 in a kitchen 153 includes a thermal radiation sensor directed at a stove/oven 112. A thermal radiation sensor may determine the temperature of the respective heat source (or a portion thereof) at which it is directed and may provide corresponding blackbody radiation data as output.
The smart doorbell 106 may detect a person's approach to or departure from a location (e.g., an outer door), control doorbell functionality, announce a person's approach or departure via audio or visual means, and/or control settings on a security system (e.g., to activate or deactivate the security system when occupants go and come).
In some embodiments, the smart home environment 100 includes one or more network-connected, electrically-controlled, and optionally intelligent and/or multi-sensing, door handles 172 (hereinafter referred to as “smart door handles 172”). Smart door handle 172 may be mounted on any type of door, including but not limited to swinging doors (e.g., a door between two adjacent rooms 152), sliding doors (e.g., a sliding glass door between a room and a balcony), and folding doors (e.g., a folding door between a room and a patio). In some embodiments, a smart door handle 172 is also intelligent and/or multi-sensing (e.g., the smart door handle 172 includes sensors to detect touch and pressure from pulling or pushing by an occupant). In some embodiments, a smart door handle 172 enables or disables itself in accordance with detection of conditions that satisfy one or more specified criteria and/or instructions transmitted from another device or system (e.g., one or more occupancy detection devices, a smart home controller, a smart home provider server system 164). It should be appreciated that while smart door handles 172 are described as handles in this specification, smart door handles 172 also includes other door operation mechanisms (e.g., a door knob, finger pull, door locking system, etc.) that are network-connected and electrically-controlled, and optionally intelligent and/or multi-sensing.
In some embodiments, the smart home environment 100 includes one or more intelligent, multi-sensing, network-connected wall switches 108 (hereinafter referred to as “smart wall switches 108”), along with one or more intelligent, multi-sensing, network-connected wall plug or socket interfaces 110 (hereinafter referred to as “smart wall plugs 110”). The smart wall switches 108 may detect ambient lighting conditions, detect room-occupancy states, and control a power and/or dim state of one or more lights. In some instances, smart wall switches 108 may also control a power state or speed of a fan, such as a ceiling fan.
The smart wall plugs 110 may detect occupancy of a room or enclosure and control supply of power to one or more wall plugs/sockets (e.g., such that power is not supplied to the plug/socket if nobody is at home or if one or more children or other vulnerable persons are left unattended in a room with the wall plug). In some embodiments, a smart wall plug 110 controls supply of power to one or more wall plugs/sockets (including itself) in accordance with detection of conditions that satisfy one or more specified criteria and/or instructions transmitted from another device or system (e.g., one or more occupancy detection devices, a smart home controller, a smart home provider server system 164).
In some embodiments, the smart home environment 100 of
In some embodiments, the smart home environment 100 includes one or more network-connected cameras 118 that are configured to provide video monitoring and security in the smart home environment 100. The cameras 118 may be used to determine occupancy of the structure 150 and/or particular rooms 152 in the structure 150, and thus may act as occupancy sensors or occupancy detection devices. For example, video captured by the cameras 118 may be processed to identify the presence of an occupant in the structure 150 (e.g., in a particular room 152). Specific individuals and/or categories of individuals (e.g., adult, child, etc.) may be identified based, for example, on their appearance (e.g., height, face) and/or movement (e.g., their walk/gate). The smart home environment 100 may additionally or alternatively include one or more other occupancy sensors or occupancy detection devices (e.g., the smart doorbell 106, smart doorlocks, touch screens, IR sensors, microphones, ambient light sensors, motion detectors or sensors, smart nightlights 170, optical sensors, audio sensors, touch sensors, etc.). In some embodiments, the smart home environment 100 includes radio-frequency identification (RFID) readers (e.g., in each room 152 or a portion thereof) that determine occupancy based on RFID tags located on or embedded in occupants. For example, RFID readers may be integrated into the smart hazard detectors 104. In some embodiments, the various sensors and devices that detect or determine occupancy generate occupancy data and transmit the occupancy data to other devices (e.g., a smart home controller, other smart device) in the smart home environment 100 or to the smart home provider server system 164. The occupancy data includes one or more of: motion data, video audio data, touch data, and RFID presence data.
The smart home environment 100 may also include communication with devices outside of the physical home but within a proximate geographical range of the home. For example, the smart home environment 100 may include a pool heater monitor 114 that communicates a current pool temperature to other devices within the smart home environment 100 and/or receives commands for controlling the pool temperature. Similarly, the smart home environment 100 may include an irrigation monitor 116 that communicates information regarding irrigation systems within the smart home environment 100 and/or receives control information for controlling such irrigation systems.
By virtue of network connectivity, one or more of the smart home devices of
As discussed above, users may control smart devices in the smart home environment 100 using a network-connected computer or portable electronic device 166. In some examples, some or all of the occupants (e.g., individuals who live in the home) may register their device 166 with the smart home environment 100. Such registration may be made at a central server to authenticate the occupant and/or the device as being associated with the home and to give permission to the occupant to use the device to control the smart devices in the home. An occupant may use their registered device 166 to remotely control the smart devices of the home, such as when the occupant is at work or on vacation. The occupant may also use their registered device to control the smart devices when the occupant is actually located inside the home, such as when the occupant is sitting on a couch inside the home. It should be appreciated that instead of or in addition to registering devices 166, the smart home environment 100 may make inferences about which individuals live in the home and are therefore occupants and which devices 166 are associated with those individuals. As such, the smart home environment 100 may “learn” who is an occupant and permit the devices 166 associated with those individuals to control the smart devices of the home.
In some embodiments, one or more specific occupants are registered with the smart home environment 100 and categorized. For example, an occupant may be registered and assigned to one or more occupant categories (e.g., adult, child, disabled, elderly, etc.). The registration of an occupant may include detection by a camera 118 and corresponding data input using a device 166 to identify and categorize the occupant. The cameras 118 and other occupancy sensors and occupancy detection devices may be used to detect the specific occupants.
In some embodiments, in addition to containing processing and sensing capabilities, devices 102, 104, 106, 108, 110, 112, 114, 116, 118, 170, and/or 172 (collectively referred to as “the smart devices”) are capable of data communications and information sharing with other smart devices, a central server or cloud-computing system, and/or other devices that are network-connected. Data communications may be carried out using any of a variety of custom or standard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, MiWi, etc.) and/or any of a variety of custom or standard wired protocols (e.g., Ethernet, HomePlug, etc.), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
In some embodiments, the smart devices serve as wireless or wired repeaters. In some embodiments, a first one of the smart devices communicates with a second one of the smart devices via a wireless router. The smart devices may further communicate with each other via a connection (e.g., network interface 160) to a network, such as the Internet 162. Through the Internet 162, the smart devices may communicate with a smart home provider server system 164 (also called a central server system and/or a cloud-computing system herein). The smart home provider server system 164 may be associated with a manufacturer, support entity, or service provider associated with the smart device(s). In some embodiments, a user is able to contact customer support using a smart device itself rather than needing to use other communication means, such as a telephone or Internet-connected computer. In some embodiments, software updates are automatically sent from the smart home provider server system 164 to smart devices (e.g., when available, when purchased, or at routine intervals).
In some embodiments, some low-power nodes are incapable of bidirectional communication. These low-power nodes send messages, but they are unable to “listen”. Thus, other devices in the smart home environment 100, such as the spokesman nodes, cannot send information to these low-power nodes.
In some embodiments, some low-power nodes are capable of only a limited bidirectional communication. For example, other devices are able to communicate with the low-power nodes only during a certain time period.
As described, in some embodiments, the smart devices serve as low-power and spokesman nodes to create a mesh network in the smart home environment 100. In some embodiments, individual low-power nodes in the smart home environment regularly send out messages regarding what they are sensing, and the other low-powered nodes in the smart home environment—in addition to sending out their own messages—forward the messages, thereby causing the messages to travel from node to node (i.e., device to device) throughout the smart home network 202. In some embodiments, the spokesman nodes in the smart home network 202, which are able to communicate using a relatively high-power communication protocol, such as IEEE 802.11, are able to switch to a relatively low-power communication protocol, such as IEEE 802.15.4, to receive these messages, translate the messages to other communication protocols, and send the translated messages to other spokesman nodes and/or the smart home provider server system 164 (using, e.g., the relatively high-power communication protocol). Thus, the low-powered nodes using low-power communication protocols are able to send and/or receive messages across the entire smart home network 202, as well as over the Internet 162 to the smart home provider server system 164. In some embodiments, the mesh network enables the smart home provider server system 164 to regularly receive data from most or all of the smart devices in the home, make inferences based on the data, facilitate state synchronization across devices within and outside of the smart home network 202, and send commands back to one or more of the smart devices to perform tasks in the smart home environment.
As described, the spokesman nodes and some of the low-powered nodes are capable of “listening.” Accordingly, users, other devices, and/or the smart home provider server system 164 may communicate control commands to the low-powered nodes. For example, a user may use the electronic device 166 (e.g., a smart phone) to send commands over the Internet to the smart home provider server system 164, which then relays the commands to one or more spokesman nodes in the smart home network 202. The spokesman nodes may use a low-power protocol to communicate the commands to the low-power nodes throughout the smart home network 202, as well as to other spokesman nodes that did not receive the commands directly from the smart home provider server system 164.
In some embodiments, a smart nightlight 170 (
Other examples of low-power nodes include battery-operated versions of the smart hazard detectors 104. These smart hazard detectors 104 are often located in an area without access to constant and reliable power and may include any number and type of sensors, such as smoke/fire/heat sensors (e.g., thermal radiation sensors), carbon monoxide/dioxide sensors, occupancy/motion sensors, ambient light sensors, ambient temperature sensors, humidity sensors, and the like. Furthermore, smart hazard detectors 104 may send messages that correspond to each of the respective sensors to the other devices and/or the smart home provider server system 164, such as by using the mesh network as described above. In some embodiments, smart wall plugs 110 and/or smart door handles 172 are also low-power nodes or may operate in a low-power mode.
Examples of spokesman nodes include smart doorbells 106, smart thermostats 102, smart wall switches 108, and smart wall plugs 110. These devices 102, 106, 108, and 110 are often located near and connected to a reliable power source, and therefore may include more power-consuming components, such as one or more communication chips capable of bidirectional communication in a variety of protocols.
In some embodiments, the smart home environment 100 includes service robots 168 (
In some embodiments, the devices and services platform 300 communicates with and collects data from the smart devices of the smart home environment 100. In addition, in some embodiments, the devices and services platform 300 communicates with and collects data from a plurality of smart home environments across the world. For example, the smart home provider server system 164 collects home data 302 from the devices of one or more smart home environments 100, where the devices may routinely transmit home data or may transmit home data in specific instances (e.g., when a device queries the home data 302). Exemplary collected home data 302 includes, without limitation, power consumption data, blackbody radiation data, occupancy data, HVAC settings and usage data, carbon monoxide levels data, carbon dioxide levels data, volatile organic compounds levels data, sleeping schedule data, cooking schedule data, inside and outside temperature humidity data, television viewership data, inside and outside noise level data, pressure data, video data, etc.
In some embodiments, the smart home provider server system 164 provides one or more services 304 to smart homes and/or third parties. Exemplary services 304 include, without limitation, software updates, customer support, sensor data collection/logging, remote access, remote or distributed control, and/or use suggestions (e.g., based on collected home data 302) to improve performance, reduce utility cost, increase safety, etc. In some embodiments, data associated with the services 304 is stored at the smart home provider server system 164, and the smart home provider server system 164 retrieves and transmits the data at appropriate times (e.g., at regular intervals, upon receiving a request from a user, etc.).
In some embodiments, the extensible devices and services platform 300 includes a processing engine 306, which may be concentrated at a single server or distributed among several different computing entities without limitation. In some embodiments, the processing engine 306 includes engines configured to receive data from the devices of smart home environments 100 (e.g., via the Internet 162 and/or a network interface 160), to index the data, to analyze the data and/or to generate statistics based on the analysis or as part of the analysis. In some embodiments, the analyzed data is stored as derived home data 308.
Results of the analysis or statistics may thereafter be transmitted back to the device that provided home data used to derive the results, to other devices, to a server providing a webpage to a user of the device, or to other non-smart device entities. In some embodiments, use statistics, use statistics relative to use of other devices, use patterns, and/or statistics summarizing sensor readings are generated by the processing engine 306 and transmitted. The results or statistics may be provided via the Internet 162. In this manner, the processing engine 306 may be configured and programmed to derive a variety of useful information from the home data 302. A single server may include one or more processing engines.
The derived home data 308 may be used at different granularities for a variety of useful purposes, ranging from explicit programmed control of the devices on a per-home, per-neighborhood, or per-region basis (for example, demand-response programs for electrical utilities), to the generation of inferential abstractions that may assist on a per-home basis (for example, an inference may be drawn that the homeowner has left for vacation and so security detection equipment may be put on heightened sensitivity), to the generation of statistics and associated inferential abstractions that may be used for government or charitable purposes. For example, processing engine 306 may generate statistics about device usage across a population of devices and send the statistics to device users, service providers or other entities (e.g., entities that have requested the statistics and/or entities that have provided monetary compensation for the statistics).
In some embodiments, to encourage innovation and research and to increase products and services available to users, the devices and services platform 300 exposes a range of application programming interfaces (APIs) 310 to third parties, such as charities 314, governmental entities 316 (e.g., the Food and Drug Administration or the Environmental Protection Agency), academic institutions 318 (e.g., university researchers), businesses 320 (e.g., providing device warranties or service to related equipment, targeting advertisements based on home data), utility companies 324, and other third parties. The APIs 310 are coupled to and permit third-party systems to communicate with the smart home provider server system 164, including the services 304, the processing engine 306, the home data 302, and the derived home data 308. In some embodiments, the APIs 310 allow applications executed by the third parties to initiate specific data processing tasks that are executed by the smart home provider server system 164, as well as to receive dynamic updates to the home data 302 and the derived home data 308.
For example, third parties may develop programs and/or applications, such as web applications or mobile applications, that integrate with the smart home provider server system 164 to provide services and information to users. Such programs and applications may be, for example, designed to help users reduce energy consumption, to preemptively service faulty equipment, to prepare for high service demands, to track past service performance, etc., and/or to perform other beneficial functions or tasks.
In some embodiments, processing engine 306 includes a challenges/rules/compliance/rewards paradigm 410d that informs a user of challenges, competitions, rules, compliance regulations and/or rewards and/or that uses operation data to determine whether a challenge has been met, a rule or regulation has been complied with and/or a reward has been earned. The challenges, rules, and/or regulations may relate to efforts to conserve energy, to live safely (e.g., reducing the occurrence of child-protection alerts, reducing occurrences of disablement of a wall plug 110 or a smart door handle 172) (e.g., reducing exposure to toxins or carcinogens), to conserve money and/or equipment life, to improve health, etc. For example, one challenge may involve participants turning down their thermostat by one degree for one week. Those participants that successfully complete the challenge are rewarded, such as with coupons, virtual currency, status, etc. Regarding compliance, an example involves a rental-property owner making a rule that no renters are permitted to access certain owner's rooms. The devices in the room having occupancy sensors may send updates to the owner when the room is accessed.
In some embodiments, processing engine 306 integrates or otherwise uses extrinsic information 412 from extrinsic sources to improve the functioning of one or more processing paradigms. Extrinsic information 412 may be used to interpret data received from a device, to determine a characteristic of the environment near the device (e.g., outside a structure that the device is enclosed in), to determine services or products available to the user, to identify a social network or social-network information, to determine contact information of entities (e.g., public-service entities such as an emergency-response team, the police or a hospital) near the device, to identify statistical or environmental conditions, trends or other information associated with a home or neighborhood, and so forth.
In some embodiments, the smart device 204 includes one or more motion sensors 522 (e.g., a passive infrared sensor) that detect motion by one or more occupants. In some embodiments, the smart device 204 includes one or more ambient light sensors 525 that measure the ambient light at the location of the smart device 204. In some embodiments, the smart device 204 includes one or more touch sensors 554 (e.g., a touch-sensitive surface separate from the touch-sensitive surface 514 associated with the display 512) to detect touch and/or pressure made by occupants (e.g., with the occupants' hands). In some embodiments, the smart device 204 includes other occupancy sensors in addition to or as an alternative to the image/video capture device 524, motion sensor 522, ambient light sensor 525, audio input device 520, and/or touch sensor 554.
Memory 506 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices; and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 506 may optionally include one or more storage devices remotely located from the processor(s) 502. Memory 506, or alternately the non-volatile memory device(s) within memory 506, includes a non-transitory computer readable storage medium. In some embodiments, memory 506 or the computer readable storage medium of memory 506 stores the following programs, modules and data structures, or a subset or superset thereof:
In some embodiments, a smart device 204 includes a subset of the components and/or modules described above in
As another example of a smart device 204 with a subset of the components and/or modules described above in
It should be appreciated that the smart wall plug 110 and smart door handle 172 may include more or less components and/or modules than shown in
The computing system 600 typically includes one or more processing units (processors or cores) 602, one or more network or other communications interfaces 604, memory 606, and one or more communication buses 608 for interconnecting these components. The communication buses 608 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. In some embodiments, the computing system 600 includes a user interface 605 (e.g., which is analogous to the user interface 510,
Memory 606 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices; and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 606 may optionally include one or more storage devices remotely located from the processor(s) 602. Memory 606, or alternately the non-volatile memory device(s) within memory 606, includes a non-transitory computer readable storage medium. In some embodiments, memory 606 or the computer readable storage medium of memory 606 stores the following programs, modules and data structures, or a subset or superset thereof:
In some embodiments, the computer system 600 includes one or more of: image capture device 524, audio input device 520, motion sensor 522, ambient light sensor 525, touch sensor 554, and/or other occupancy sensors and their respective corresponding modules (e.g., image/video capture module 530, audio input module 532, motion data module 534, ambient light data module 537, and touch data module 556, respectively) and/or occupancy data module 536.
Each of the above identified modules and applications of
Attention is now directed towards embodiments of graphical user interfaces (“UI”) and associated processes that may be implemented on an electronic device to present child-protection alerts and/or alert a user of disablement of a wall plug or door handle, and allow a user to respond to (e.g., cancel) child-protection alerts and/or disablements.
The GUI 704 displays a child-protection alert 706, which in this example indicates that there is a child unattended in a room 152 (e.g., the study room) of the structure 150, and electrical outlets (e.g., smart wall plugs 110) in the study room that are unused (i.e., nothing plugged in) have been disabled (e.g., terminals blocked from physical access, and/or electrical power to the terminals in the outlet is cut off). The GUI 704 also presents user-interface elements 708, 710, and/or 712 that allow the user to cancel the child-protection alert and to cancel the disablement of the electrical outlets (i.e., enable them). Selection of the element 708 (e.g., through an appropriate gesture on the screen 702, such as a tap) cancels the child-protection alert 706 and indicates that the child-protection alert 706 was valid. Selection of the element 710 cancels the child-protection alert 706 and indicates that the child-protection alert 706 was a false alarm. Selection of the element 712 cancels the child-protection alert 706 and indicates that the child-protection alert 706 was valid but was late in being presented. If the child-protection alert 706 was provided by another device (e.g., a computing system 600,
One or more occupancy sensors (e.g., cameras 118, audio input device 520, motion sensor 522, ambient light sensor 525, touch sensor 554, and/or other occupancy sensors) send (802) occupancy data for a room in a dwelling. The computing system 600 receives (804) this data and determines an occupancy of the room. The one or more occupancy sensors thus include an occupancy sensor in the room.
The computing system 600 determines (806) that a child-protection condition and/or a child-protection alert condition are met, based at least in part on the determined occupancy of the room. In some embodiments, the child-protection condition includes a first threshold time, and the child-protection alert condition includes a second threshold time, which may be the same as or different from the first threshold time. In some embodiments, the child-protection condition and the child-protection alert condition are the same. For example, the child-protection condition and/or the child-protection alert condition requires that a child be detected as the lone occupant in the room for at least a specified amount of time. The child-protection condition and the child-protection alert condition thus applies the first threshold time and the second threshold time, respectively, to a specified occupancy state of the room, in accordance with some embodiments. In some embodiments, the specified period of time is measured in minutes (e.g., is in the range of 5-15 minutes).
In response to determining (806) that the child-protection condition is met, the computing system 600 disables (808) or sends instructions to disable unused electrical outlets and/or electrically-controlled door handles in the room. In response to determining (806) that the child-protection alert condition is met, the computing system 600 presents (808) or sends instructions to present a child-protection alert. In some embodiments, the operation 808 includes displaying a flashing light or other visual warning in one or more rooms, sounding an audible warning (e.g., “Your child is approaching an electrical outlet” or “Your child is alone for 10 minutes”) in one or more rooms, and/or sending a notification (e.g., a text message or email) to one or more occupants of the structure or to a third party (e.g., a caregiver of an occupant or a home security provider). The child-protection alert 706 (
An electronic device (e.g., a portable electronic device 166 or smart device 204) sends (810) a request to cancel disablement of the electrical outlets and door handles, and/or the child-protection alert, based on a corresponding user input (e.g., a user input provided through the touch-sensitive surface 514 or an input 516,
The request may be of a first type or a second type. In some embodiments, a request of the first type results from a first type of activation of a cancel button or touch-sensitive surface, while a request of the second type results from a second type of activation of the cancel button or touch-sensitive surface. For example, the first type of activation of the cancel button or touch-sensitive surface is a press-and-hold or double-tap gesture, while the second type of activation of the cancel button or touch-sensitive surface is a single-tap gesture (or vice versa). In another example, the first type of activation is selection of the user-interface element 710 or 712 (
The computing system 600 receives (812) the request. If the request is of the first type, the computing system 600 cancels (812) the child-protection alert and modifies the child-protection condition and/or the child-protection alert condition. Examples of modifying the child-protection condition and/or the child-protection alert condition are provided below with respect to operation 930 and 948 (
The computer system 600 receives (902) occupancy data (e.g. information 615 thru 620,
In some embodiments, an electrical outlet is unused if no power cord is plugged into the electrical outlet. In some embodiments, whether an electrical outlet is used may be considered for the outlet as a whole or per socket. For example, if viewing the outlet as a whole, the outlet is considered unused if any of the sockets is open (i.e., no power cord plugged into that socket). If viewing the outlet on a per-socket basis, then a socket of the outlet is unused if no power cord is plugged into that socket, but a socket with a power cord plugged in is considered to be used. An unused electrical outlet poses a potential electrical shock hazard to children and other vulnerable persons.
In some embodiments, the one or more sensors in the room include (908) a motion sensor (e.g., a passive IR sensor) (e.g., motion sensor 522), an optical sensor (e.g., a video camera) (e.g., camera 118, image/video capture device 524), an audio sensor (e.g., a microphone) (e.g., audio input device 520), a touch sensor (e.g., a touch-sensitive surface on or near an unused electrical outlet or an electronically-controlled door handle) (e.g., touch sensor 554), and/or an ambient light sensor (e.g., ambient light sensor 525).
In some embodiments, the received occupancy data for the room include (910) motion data (e.g., data from a motion sensor), video data (e.g., data from an optical sensor), audio data (e.g., data from an audio sensor), and/or touch data (e.g., data from a touch sensor).
The computer system 600 determines (904), based at least in part on the received occupancy data for the room, whether a predetermined child-protection condition is met. For example, the occupancy-determination module 622 analyzes the information 615-620, and determines whether a child-protection condition (e.g., child-protection condition 552) is met based on the analysis.
In some embodiments, determining, based at least in part on the received occupancy data for the room, whether the predetermined child-protection condition is met includes: determining (912) that a child (e.g., a crawling baby, toddler, a child whose height is less than a threshold value, or a person previously identified as a child to the computer system while the computer system is in a settings mode) is the lone occupant in the room for at least a threshold amount of time (e.g., based on video data for the room); determining (914) that there are one or more small children in the room and no adults for at least a threshold amount of time (e.g., based on video data for the room); determining (916) that a child is moving towards an unused electrical outlet or an electronically-controlled door handle (e.g., based on motion data and/or video data for the room); determining (918) that a child is less than a predetermined distance from an unused electrical outlet or an electronically-controlled door handle (e.g., based on video data for the room); and/or determining (920) that a child is touching an unused electrical outlet or an electronically-controlled door handle (e.g., based on touch data from a touch-sensitive surface on or near an unused electrical outlet or an electronically-controlled door handle). Thus, for example, the child-protection is met if the computer system 600 determines that a child (or some other vulnerable person, e.g., an elderly person) is alone in the room for at least a threshold amount of time, that there are one or more children and/or other vulnerable persons in the room without any adults for at least a threshold amount of time, that a child or other vulnerable person is moving towards an unused electrical outlet or electrically-controlled door handle, that a child is less than a predetermined distance away from an unused electrical outlet or electrically-controlled door handle, and/or that a child is touching an unused electrical outlet or electrically-controlled door handle. Thus, in some embodiments, the child-protection condition includes one or more threshold or predefined times and/or one or more threshold or predefined distances.
In accordance with a determination that the predetermined child-protection condition is met, the computer system 600 disables or sends instructions to disable (906) at least one of the one or more unused electrical outlets (e.g., wall plug(s) 110) and/or at least one of the one or more electronically-controlled door handles in the room. In some embodiments, power is shut off to the unused electrical outlet that a child is moving towards, near, or touching. In some embodiments, power is shut off to all of the unused electrical outlets in the room. In some embodiments, power is shut off to all of the unused electrical outlets in the room that are within a predetermined distance of the child. In some embodiments, power is shut off to just the unused sockets of an outlet in lieu of shutting off power to the entire outlet. In some embodiments, an electronically-controlled door handle that a child is moving towards, near, or touching is locked so that the child cannot operate the door handle. In some embodiments, an electronically-controlled door handle that a child is moving towards, near, or touching is disengaged so that the child cannot operate the door handle. In some embodiments, all of the electronically-controlled door handles in the room are locked, disengaged, or otherwise disabled.
In some embodiments, after disabling or sending instructions to disable at least one of the one or more unused electrical outlets and/or at least one of the one or more electronically-controlled door handles, the computer system 600 receives (922) a request to enable the disabled one or more unused electrical outlets and/or the disabled one or more electronically-controlled door handles in the room. For example, the computer system detects an activation of a cancel button or a user interface element by a user (e.g., tapping on user interface icon 708, 710, or 712), a gesture by a user, or a voice command.
In some embodiments, the computer system 600 determines (924) a type for the request to enable the disabled one or more unused electrical outlets and/or the disabled one or more electronically-controlled door handles in the room. For example, the computer system detects a first type of activation of a cancel button by a user (e.g., a “press and hold” or “double tap” gesture on the cancel button; activation of a user interface element associated with the first type of activation (e.g., user element 710 or 712)), a first type of gesture by a user (e.g., a wave), or a first type of voice command (e.g., “False alarm”) by a user. Alternatively, the computer system detects a second type of activation of a cancel button by a user (e.g., a “single tap” gesture on the cancel button; activation of a user interface element associated with the second type of activation (e.g., user element 708)), a second type of gesture by a user (e.g., a thumbs up), or a second type voice command (e.g., “Cancel”) by a user.}
In some embodiments, in accordance with a determination that the request to enable the disabled one or more unused electrical outlets and/or the disabled one or more electronically-controlled door handles in the room is a first type of enablement request (926), the computer system 600 enables (928) the disabled one or more unused electrical outlets and/or the disabled one or more electronically-controlled door handles in the room, and modifies (930) the predetermined child-protection condition. For example, in
In accordance with a determination that the request to enable the disabled one or more unused electrical outlets and/or the disabled one or more electronically-controlled door handles in the room is a second type of enablement request, distinct from the first type of enablement request (932), the computer system 600 enables (934) the disabled one or more unused electrical outlets and/or the disabled one or more electronically-controlled door handles in the room without modifying the predetermined child-protection condition. For example, in
In some embodiments, after disabling or sending instructions to disable at least one of the one or more unused electrical outlets and/or at least one of the one or more electronically-controlled door handles, the computer system receives a request to enable the disabled one or more unused electrical outlets and/or the disabled one or more electronically-controlled door handles in the room and determines whether the enablement request is of a first type or a second type.
In some embodiments, the first type corresponds to a request to cancel a disablement that was unneeded (and possibly annoying), whereas the second type corresponds to a request to cancel a disablement that was needed and properly performed. In accordance with a determination that the request to cancel the disablement is of the first type, the computer system cancels the disablement and modifies the child-protection condition (to reduce future unneeded disablements). In accordance with a determination that the request to cancel the disablement is of the second type, the computer system cancels the disablement without modifying the child-protection condition (because the disablement was properly performed).
In some embodiments, the first type corresponds to a request to cancel a disablement that was needed but which should have occurred sooner, whereas the second type corresponds to a request to cancel a disablement that was needed and properly performed. In accordance with a determination that the request to cancel the disablement is of the first type, the computer system cancels the disablement and modifies the child-protection condition (to have future disablements given sooner, e.g., by setting lower threshold times and/or larger threshold distances to an unused electrical outlet or electronically-controlled door handle). In accordance with a determination that the request to cancel the disablement is of the second type, the computer system cancels the disablement without modifying the child-protection condition (because the disablement was properly performed).
In some embodiments, after disabling or sending instructions to disable at least one of the one or more unused electrical outlets and/or at least one of the one or more electronically-controlled door handles, the computer system receives a request to enable the disabled one or more unused electrical outlets and/or the disabled one or more electronically-controlled door handles in the room and determines whether the enablement request is of a first type, a second type, or a third type.
In some embodiments, the first type corresponds to a request to cancel a disablement that was an unneeded (and possibly annoying), the second type corresponds to a request to cancel a disablement that was needed and properly performed, and the third type corresponds to a request to cancel a disablement that was needed but which should have occurred sooner. In accordance with a determination that the request to cancel the disablement is of the first type, the computer system cancels the disablement and modifies the child-protection condition (to reduce future unneeded disablements). In accordance with a determination that the request to cancel the disablement is of the second type, the computer system cancels the disablement without modifying the child-protection condition (because the disablement was properly performed). In accordance with a determination that the request to cancel the disablement is of the third type, the computer system cancels the disablement and modifies the child-protection condition (to have future disablements given sooner, e.g., by setting lower threshold times and/or larger threshold distances to an unused electrical outlet or electronically-controlled door handle).
In some embodiments, the computer system 600 determines (936), based at least in part on the received occupancy data for the room, whether a predetermined child-protection alert condition (e.g., child-protection alert condition 548) is met. In accordance with a determination that the child-protection alert condition is met, the computer system 600 presents or sends instructions to present (938) a child-protection alert (e.g., alert 706). In some embodiments, the child-protection alert includes displaying a flashing light in one or more rooms in the dwelling, sounding an audible warning such as “[Name] is unattended in the [ ] room” or “Toddler unattended” in one or more rooms in the dwelling, and/or sending a notification (e.g., an instant message, text message, or email) to one or more occupants of the dwelling or a third party (e.g., a parent or caregiver for the child in the dwelling or a home security provider).
In some embodiments, the child-protection condition 552 and the child-protection alert condition 548 are the same; circumstances that meet the child-protection condition 552 also meets the child-protection alert condition 548. The child-protection condition 552 and the child-protection alert condition 548 may be the same, or are modified in unison. The child-protection alert also informs the user of the disablement of the unused electrical outlets and door handles, and canceling the alert also enables the unused electrical outlets and door handles (e.g., as in alert 706).
In some other embodiments, the child-protection condition 552 and the child-protection alert condition 548 are different and independent of each other; circumstances that meet the child-protection condition 552 may not necessarily meet the child-protection alert condition 548, and vice versa. The child-protection condition 552 and the child-protection alert condition 548 are modified independently of each other. The child-protection alert is not necessarily tied with disablement of the unused electrical outlets and door handles, and thus does not necessarily inform the user of the disablement, and canceling the child-protection alert does not affect the disablement. In other words, the child-protection alert and the disablement alert are separate, and their cancellations are also separate.
In some embodiments, after presenting or sending instructions to present the child-protection alert, the computer system 600 receives a request to cancel the child-protection alert. For example, the computer system detects an activation of a cancel button or a user interface element by a user (e.g., tapping on user interface element 708, 710, or 712), a gesture by a user, or a voice command.
The computer system 600 determines (942) a type for the request to cancel the child-protection alert. For example, the computer system detects a first type of activation of a cancel button by a user (e.g., a “press and hold” or “double tap” gesture on the cancel button; activation of a user interface element associated with the first type of activation (e.g., user element 710 or 712)), a first type of gesture by a user (e.g., a wave), or a first type of voice command (e.g., “False alarm”) by a user. Alternatively, the computer system detects a second type of activation of a cancel button by a user (e.g., a “single tap” gesture on the cancel button; activation of a user interface element associated with the second type of activation (e.g., user element 708)), a second type of gesture by a user (e.g., a thumbs up), or a second type voice command (e.g., “Cancel”) by a user.
In accordance with a determination (944) that the request to cancel the child-protection alert is a first type of cancellation request, the computer system 600 cancels (946) the child-protection alert (e.g., alert 706), and modifies (948) the predetermined child-protection alert condition (e.g., child-protection alert condition 548). For example, in
In some embodiments, the child-protection alert condition (e.g., child-protection alert condition 548) for presenting or sending instructions to present the child-protection alert is the same as the child-protection condition (e.g., child-protection condition 552) for disabling or sending instructions to disable at least one of the one or more unused electrical outlets and/or at least one of the one or more electronically-controlled door handles in the room.
In accordance with a determination (950) that the request to cancel the child-protection alert is a second type of cancellation request, distinct from the first type of cancellation request, the computer system 600 cancels (952) the child-protection alert (e.g., alert 706) without modifying the predetermined child-protection alert condition (e.g., child-protection alert condition 548). For example, in
In some embodiments, after presenting or sending instructions to present the child-protection alert, the computer system receives a request to cancel the child-protection alert and determines whether the request to cancel the child-protection alert is of a first type or a second type.
In some embodiments, the first type corresponds to a request to cancel an alert that was an unneeded (and possibly annoying) false alarm, whereas the second type corresponds to a request to cancel an alert that was needed and properly given. In accordance with a determination that the request to cancel the child-protection alert is of the first type, the computer system cancels the child-protection alert and modifies the child-protection alert condition (to reduce future false alerts). In accordance with a determination that the request to cancel the child-protection alert is of the second type, the computer system cancels the child-protection alert without modifying the child-protection alert condition (because the alert was properly given).
In some embodiments, the first type corresponds to a request to cancel an alert that was needed but which should have issued sooner, whereas the second type corresponds to a request to cancel an alert that was needed and properly given. In accordance with a determination that the request to cancel the child-protection alert is of the first type, the computer system cancels the child-protection alert and modifies the child-protection alert condition (to have future child-protection alerts given sooner, e.g., by setting lower threshold times and/or larger threshold distances to an unused electrical outlet or electronically-controlled door handle). In accordance with a determination that the request to cancel the child-protection alert is of the second type, the computer system cancels the child-protection alert without modifying the child-protection alert condition (because the alert was properly given).
In some embodiments, after presenting or sending instructions to present the child-protection alert, the computer system receives a request to cancel the child-protection alert and determines whether the request to cancel the child-protection alert is of a first type, a second type, or a third type.
In some embodiments, the first type corresponds to a request to cancel an alert that was an unneeded (and possibly annoying) false alarm, the second type corresponds to a request to cancel an alert that was needed and properly given, and the third type corresponds to a request to cancel an alert that was needed but which should have issued sooner. In accordance with a determination that the request to cancel the child-protection alert is of the first type, the computer system cancels the child-protection alert and modifies the child-protection alert condition (to reduce future false alerts). In accordance with a determination that the request to cancel the child-protection alert is of the second type, the computer system cancels the child-protection alert without modifying the child-protection alert condition (because the alert was properly given). In accordance with a determination that the request to cancel the child-protection alert is of the third type, the computer system cancels the child-protection alert and modifies the child-protection alert condition (to have future child-protection alerts given sooner, e.g., by setting lower threshold times and/or larger threshold distances to an unused electrical outlet or electronically-controlled door handle).
In some embodiments, a housing that contains the computer system (e.g., computer system 600) also contains (954) at least one of the one or more sensors in the room providing occupancy data (e.g., image/video capture device 524, motion sensor 522, etc.).
In some embodiments, the computer system (e.g., computer system 600) is located (956) in the dwelling at a separate location from the one or more sensors in the room (e.g., the computer system is a controller for the dwelling that receives data from multiple sensors in the dwelling). For example, the computer system 600 is in a different room 152 than the room that includes the sensors.
In some embodiments, the computer system (e.g., computer system 600) is located (958) in a smart home provider server system (e.g., smart home provider server system 164) remote from the dwelling.
For situations in which the systems discussed above collect information about users, the users may be provided with an opportunity to opt in/out of programs or features that may collect personal information (e.g., information about a user's preferences or usage of a smart device). In addition, in some embodiments, certain data may be anonymized in one or more ways before it is stored or used, so that personally identifiable information is removed. For example, a user's identity may be anonymized so that the personally identifiable information cannot be determined for or associated with the user, and so that user preferences or user interactions are generalized (for example, generalized based on user demographics) rather than associated with a particular user.
Although some of various drawings illustrate a number of logical stages in a particular order, stages that are not order dependent may be reordered and other stages may be combined or broken out. While some reordering or other groupings are specifically mentioned, others will be obvious to those of ordinary skill in the art, so the ordering and groupings presented herein are not an exhaustive list of alternatives. Moreover, it should be recognized that the stages could be implemented in hardware, firmware, software or any combination thereof.
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the scope of the claims to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. For example, the teachings above concerning smart door handles could be applied in an analogous manner to smart window handles. The embodiments were chosen in order to best explain the principles underlying the claims and their practical applications, to thereby enable others skilled in the art to best use the embodiments with various modifications as are suited to the particular uses contemplated.
This application is a continuation of U.S. application Ser. No. 14/675,642, filed Mar. 31, 2015, entitled “Devices and Methods for Protecting Unattended Children in the Home,” which is hereby incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4305130 | Kelley | Dec 1981 | A |
| 4412293 | Kelley | Oct 1983 | A |
| 4781517 | Pearce | Nov 1988 | A |
| 4813125 | Dacey, Jr. | Mar 1989 | A |
| 4815190 | Haba, Jr. | Mar 1989 | A |
| 4831549 | Red | May 1989 | A |
| 4894908 | Haba, Jr. | Jan 1990 | A |
| 5040056 | Sager | Aug 1991 | A |
| 5041907 | Sager | Aug 1991 | A |
| 5091780 | Pomerleau | Feb 1992 | A |
| 5120190 | Smith | Jun 1992 | A |
| 5125149 | Inaba | Jun 1992 | A |
| 5184766 | Takahashi | Feb 1993 | A |
| 5353495 | Terabayashi | Oct 1994 | A |
| 5380978 | Pryor | Jan 1995 | A |
| 5506682 | Pryor | Apr 1996 | A |
| 5521652 | Shalvi | May 1996 | A |
| 5793290 | Eagleson | Aug 1998 | A |
| 5910894 | Pryor | Jun 1999 | A |
| 5930144 | Kondo | Jul 1999 | A |
| 6011328 | Smith | Jan 2000 | A |
| 6167607 | Pryor | Jan 2001 | B1 |
| 6314631 | Pryor | Nov 2001 | B1 |
| 6415204 | Hirabayashi | Jul 2002 | B1 |
| 6611206 | Eshelman et al. | Aug 2003 | B2 |
| 6720880 | Gutta et al. | Apr 2004 | B2 |
| 6825761 | Christ | Nov 2004 | B2 |
| 6859677 | Mitterholzer | Feb 2005 | B2 |
| 7109861 | Rao | Sep 2006 | B2 |
| 7138921 | Fontaine | Nov 2006 | B1 |
| 7143494 | Savoy | Dec 2006 | B2 |
| 7164354 | Panzer | Jan 2007 | B1 |
| 7254403 | La | Aug 2007 | B2 |
| 7313464 | Perreault | Dec 2007 | B1 |
| 7554444 | Rao | Jun 2009 | B2 |
| 7634382 | Andenna et al. | Dec 2009 | B2 |
| 7657763 | Nelson et al. | Feb 2010 | B2 |
| 7817029 | Hillenburg | Oct 2010 | B1 |
| 7825546 | Li et al. | Nov 2010 | B2 |
| 7843081 | Lim | Nov 2010 | B2 |
| 7906869 | Lee et al. | Mar 2011 | B2 |
| 7911746 | Zaretsky et al. | Mar 2011 | B2 |
| 8004123 | Hodges et al. | Aug 2011 | B2 |
| 8138626 | Jonsson et al. | Mar 2012 | B2 |
| 8244405 | Kao et al. | Aug 2012 | B2 |
| 8659657 | Brumfield | Feb 2014 | B2 |
| 8818532 | Vasquez | Aug 2014 | B1 |
| 8904042 | Dellecave, Jr. | Dec 2014 | B1 |
| 8930146 | Katsukura et al. | Jan 2015 | B2 |
| 9008841 | Fuhlbrigge | Apr 2015 | B2 |
| 9084937 | Gadher | Jul 2015 | B2 |
| 9110450 | Alberth, Jr. et al. | Aug 2015 | B2 |
| 9189709 | Saruta | Nov 2015 | B2 |
| 9227484 | Justice et al. | Jan 2016 | B1 |
| 9279661 | Tateno | Mar 2016 | B2 |
| 9459772 | Nihal | Oct 2016 | B2 |
| 9460596 | Moses | Oct 2016 | B1 |
| 9508091 | Quady | Nov 2016 | B2 |
| 9513625 | Kilibarda | Dec 2016 | B2 |
| 10135856 | Tripp | Nov 2018 | B2 |
| 10157529 | Rubinstein | Dec 2018 | B2 |
| 10163314 | Tofighbakhsh | Dec 2018 | B2 |
| 20020022991 | Sharood et al. | Feb 2002 | A1 |
| 20020158763 | Takarada et al. | Oct 2002 | A1 |
| 20030081825 | Mitterholzer | May 2003 | A1 |
| 20030093200 | Gutta | May 2003 | A1 |
| 20030208302 | Lemelson | Nov 2003 | A1 |
| 20040071321 | Watkins | Apr 2004 | A1 |
| 20040088553 | Levin et al. | May 2004 | A1 |
| 20040176041 | Smith | Sep 2004 | A1 |
| 20050068172 | King | Mar 2005 | A1 |
| 20050240959 | Kuhn | Oct 2005 | A1 |
| 20060111816 | Spalink et al. | May 2006 | A1 |
| 20060167587 | Read | Jul 2006 | A1 |
| 20060238035 | Wainewright | Oct 2006 | A1 |
| 20060267780 | Adams | Nov 2006 | A1 |
| 20070039155 | Savoy | Feb 2007 | A1 |
| 20070096927 | Albert | May 2007 | A1 |
| 20070149013 | Eastham et al. | Jun 2007 | A1 |
| 20070276776 | Sagher | Nov 2007 | A1 |
| 20080048826 | Agrawal et al. | Feb 2008 | A1 |
| 20080048870 | Laitta | Feb 2008 | A1 |
| 20080181485 | Beis | Jul 2008 | A1 |
| 20080201277 | Ozdemir | Aug 2008 | A1 |
| 20080214935 | Levin | Sep 2008 | A1 |
| 20080268897 | Seier | Oct 2008 | A1 |
| 20080309164 | Lim | Dec 2008 | A1 |
| 20090098754 | Li et al. | Apr 2009 | A1 |
| 20090118858 | Wallace | May 2009 | A1 |
| 20090133249 | Case | May 2009 | A1 |
| 20090192927 | Berg et al. | Jul 2009 | A1 |
| 20090222142 | Kao et al. | Sep 2009 | A1 |
| 20100045461 | Caler | Feb 2010 | A1 |
| 20100138378 | Jannarone | Jun 2010 | A1 |
| 20100180711 | Kilibarda | Jul 2010 | A1 |
| 20100225469 | Yoshioka | Sep 2010 | A1 |
| 20110015795 | Boyer et al. | Jan 2011 | A1 |
| 20110031950 | Hodges et al. | Feb 2011 | A1 |
| 20110131008 | Swanson | Jun 2011 | A1 |
| 20110202495 | Gawlick | Aug 2011 | A1 |
| 20110228080 | Ding | Sep 2011 | A1 |
| 20110282497 | Josephson et al. | Nov 2011 | A1 |
| 20110307743 | Khalak | Dec 2011 | A1 |
| 20110314665 | Kilibarda | Dec 2011 | A1 |
| 20120086568 | Scott et al. | Apr 2012 | A1 |
| 20120158180 | Iio | Jun 2012 | A1 |
| 20120165986 | Fuhlbrigge | Jun 2012 | A1 |
| 20120259462 | Aoba | Oct 2012 | A1 |
| 20120271782 | Blowers | Oct 2012 | A1 |
| 20120283873 | Le | Nov 2012 | A1 |
| 20120330109 | Tran | Dec 2012 | A1 |
| 20130001422 | Lavon et al. | Jan 2013 | A1 |
| 20130011018 | Tateno | Jan 2013 | A1 |
| 20130031384 | Yamamoto | Jan 2013 | A1 |
| 20130033363 | Gabara | Feb 2013 | A1 |
| 20130037165 | Okawachi et al. | Feb 2013 | A1 |
| 20130049955 | Hoover et al. | Feb 2013 | A1 |
| 20130072807 | Tran | Mar 2013 | A1 |
| 20130090213 | Amini et al. | Apr 2013 | A1 |
| 20130093573 | Kwong | Apr 2013 | A1 |
| 20130109342 | Welch | May 2013 | A1 |
| 20130147944 | Zhang | Jun 2013 | A1 |
| 20130154808 | Han et al. | Jun 2013 | A1 |
| 20130158696 | Wallace | Jun 2013 | A1 |
| 20130190095 | Gadher | Jul 2013 | A1 |
| 20130329035 | Yamamoto | Dec 2013 | A1 |
| 20140012415 | Benaim | Jan 2014 | A1 |
| 20140032003 | Chapel | Jan 2014 | A1 |
| 20140054973 | Asanuma et al. | Feb 2014 | A1 |
| 20140067137 | Amelio et al. | Mar 2014 | A1 |
| 20140140590 | Wilson et al. | May 2014 | A1 |
| 20140208563 | Black | Jul 2014 | A1 |
| 20140266600 | Alberth, Jr. et al. | Sep 2014 | A1 |
| 20140266669 | Fadell | Sep 2014 | A1 |
| 20140297278 | Flanagan | Oct 2014 | A1 |
| 20140320312 | Sager | Oct 2014 | A1 |
| 20140320649 | Starr et al. | Oct 2014 | A1 |
| 20140375451 | Douglas | Dec 2014 | A1 |
| 20150009029 | Martin | Jan 2015 | A1 |
| 20150029020 | Bailey | Jan 2015 | A1 |
| 20150061859 | Matsuoka | Mar 2015 | A1 |
| 20150066200 | McCarthy | Mar 2015 | A1 |
| 20150120596 | Fadell | Apr 2015 | A1 |
| 20150127712 | Fadell | May 2015 | A1 |
| 20150137969 | Blum | May 2015 | A1 |
| 20150254716 | Quady | Sep 2015 | A1 |
| 20150301527 | Erickson | Oct 2015 | A1 |
| 20150302725 | Sager | Oct 2015 | A1 |
| 20150325107 | Poder | Nov 2015 | A1 |
| 20150348400 | Zribi | Dec 2015 | A1 |
| 20150364022 | Dyell | Dec 2015 | A1 |
| 20160018800 | Gettings et al. | Jan 2016 | A1 |
| 20160019780 | Gettings et al. | Jan 2016 | A1 |
| 20160027278 | McIntosh et al. | Jan 2016 | A1 |
| 20160031339 | Geo | Feb 2016 | A1 |
| 20160044451 | Marth | Feb 2016 | A1 |
| 20160078387 | Bak et al. | Mar 2016 | A1 |
| 20160091872 | Marti et al. | Mar 2016 | A1 |
| 20160117903 | Striemer | Apr 2016 | A1 |
| 20160182558 | Tripp | Jun 2016 | A1 |
| 20160232779 | Sloo et al. | Aug 2016 | A1 |
| 20160240060 | Wang | Aug 2016 | A1 |
| 20160259308 | Fadell | Sep 2016 | A1 |
| 20160261932 | Fadell | Sep 2016 | A1 |
| 20160287073 | Pradeep et al. | Oct 2016 | A1 |
| 20160287166 | Tran | Oct 2016 | A1 |
| 20160293026 | Pradeep et al. | Oct 2016 | A1 |
| 20160293042 | Pradeep et al. | Oct 2016 | A1 |
| 20160329751 | Mach et al. | Nov 2016 | A1 |
| 20160336816 | Mach et al. | Nov 2016 | A1 |
| 20160379458 | Eyring | Dec 2016 | A1 |
| 20170076562 | Hicks, III | Mar 2017 | A1 |
| 20170084160 | Piccolo, III | Mar 2017 | A1 |
| 20170186309 | Sager | Jun 2017 | A1 |
| 20180040223 | Bodi | Feb 2018 | A1 |
| 20180047212 | Long | Feb 2018 | A1 |
| 20180047230 | Nye | Feb 2018 | A1 |
| 20180130327 | Rogers | May 2018 | A1 |
| 20180158315 | Sloo | Jun 2018 | A1 |
| 20180165946 | Poder | Jun 2018 | A1 |
| 20180315301 | Subramanian | Nov 2018 | A1 |
| 20180322758 | Rubinstein | Nov 2018 | A1 |
| 20180330602 | Kleihorst | Nov 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| WO 2011037564 | Mar 2011 | WO |
| Entry |
|---|
| How to protect your child from electrical hazards, sheknows, 120CT2008, 9 pgs, http://www.sheknows.com/home-and-gardening/articles/7068/how-to-protect-your-child-from-electrical-hazards. |
| Locker, Industrial GFCIs are finally here, Control Engineering, Jun. 11, 2013, 4 pgs, http://www.controleng.com/single-article/industrial-gfcis-are-finally-here/846313cb95aeddfl 3d6f6575b37beeb9.html? rint=1. |
| Testing GFCI Outlets, The Family Handyman, Feb. 2007, 3 pgs, http://vvww.familyhandyman.com/electrical/wiring-outlets/testing-gfci-outlets/print. |
| Number | Date | Country | |
|---|---|---|---|
| 20180095482 A1 | Apr 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14675642 | Mar 2015 | US |
| Child | 15832703 | US |
