This disclosure relates to a automating use of sensor based data, and more particular toward a system, device and apparatus for coordinating environments using networked devices and remote sensory information.
Historically, devices that control items in the home have been limited in their abilities to be automatically adjusted based on a users current needs. For example, thermostats that are installed in hallways or other locations are used to control temperature throughout the entire residence. However, the temperature in a hallway may not be the same as temperature in a bedroom or a kitchen. Such traditional thermostats leave the homeowner with having to continuously adjust temperatures to achieve a desired goal. Other limitations of traditional thermostats or other power controlling devices within the home is their lack of working in unison to achieve a desired goal. Traditional light switches lack the ability to be altered automatically based on a user's desire to change an operating condition. Additionally, traditional light switches and other devices require extensive and costly wiring to implement and control devices in a home. Even more, such devices are not able to be programmed and may require expensive programming hardware and software that must be maintained and updated by a service provider. What is needed in the art is an automatic system to coordinate multiple environments at a residence on a room by room basis that is easy to program and cost effective.
According to an aspect of the disclosure, a system, method and device for automating use of remote resources using remote sensory information and operating conditions is provided.
According to an aspect of the disclosure, an intelligent remote sensor enabled apparatus is disclosed. The apparatus can include a wireless communication device configured to communicate with a mobile device and an environment coordinator located at a site. The apparatus further includes an operating condition selector capable of enabling a manual selection of an operating condition of a network connected device at the site. The apparatus also includes a processor configured to process a selection of the operating condition selector to enable activation of a setting of the network connected device, and detect a connection of the mobile device to the wireless communication device. The processor can further initiate communication of setting information to the environment coordinator to alter the operating condition of the network connected device. The apparatus further includes a memory configured to store the setting information used by the processor.
According to another aspect of the disclosure, a system is disclosed. The system can include an intelligent remote sensor configured to communicate sensory based information to a network device and a mobile device. The system further includes an environment coordinator configured to communicate with the intelligent remote sensor to initiate coordinating operating conditions of the network device at a site. The system also includes a mobile application configured to be deployed on the mobile device and communicate with the intelligent remote sensor to automatically alter an operating condition of the network device when the mobile device is within a specific region of the site.
Various other aspects of the disclosure are provided in the abstract, description of the drawings, and claims provided herein.
It will be appreciated that for simplicity and clarity of illustration, elements illustrated in the Figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements are exaggerated relative to other elements. Embodiments incorporating teachings of the present disclosure are shown and described with respect to the drawings presented herein, in which:
The use of the same reference symbols in different drawings indicates similar or identical items.
The following description in combination with the Figures is provided to assist in understanding the teachings disclosed herein. The following discussion will focus on specific implementations and embodiments of the teachings. This focus is provided to assist in describing the teachings and should not be interpreted as a limitation on the scope or applicability of the teachings. However, other teachings can certainly be utilized in this application. The teachings can also be utilized in other applications and with several different types of architectures such as distributed computing architectures, client/server architectures, or middleware server architectures and associated components.
Devices or programs that are in communication with one another need not be in continuous communication with each other unless expressly specified otherwise. In addition, devices or programs that are in communication with one another may communicate directly or indirectly through one or more intermediaries.
Embodiments discussed below describe, in part, distributed computing solutions that manage all or part of a communicative interaction between network elements. In this context, a communicative interaction may be intending to send information, sending information, requesting information, receiving information, receiving a request for information, or any combination thereof. As such, a communicative interaction could be unidirectional, bidirectional, multi-directional, or any combination thereof. In some circumstances, a communicative interaction could be relatively complex and involve two or more network elements. For example, a communicative interaction may be “a conversation” or series of related communications between a client and a server—each network element sending and receiving information to and from the other. The communicative interaction between the network elements is not necessarily limited to only one specific form. A network element may be a node, a piece of hardware, software, firmware, middleware, another component of a computing system, or any combination thereof.
For purposes of this disclosure, a network device, environment coordinator, or intelligent remote sensor can include various types of devices, software, applications, methods, drivers, media, services, controllers, platforms, interfaces, and can further include an environment management system, environment controller, energy management system, customer engagement portal, customer engagement platform, energy management apparatus, network device, controller, home automation controller, energy controller, controller module, site controller, processing resources, or any combination thereof can include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes.
For example, a network device, environment coordinator, or sensor can include one or any combination of an energy management system, an energy management device, a mobile device, a mobile application, a personal computer, a desktop application, a web-based interface, a hosted application, hosted software, hosted services, an application interface, a PDA, a consumer electronic device, a media device, a smart phone, a cellular or mobile phone, a smart utility meter, an advanced metering infrastructure, a smart energy device, an energy display device, a home automation controller, an energy hub, a smart energy gateway, a set-top box, a digital media subscriber system, a cable modem, a broadband communication device, a fiber optic enabled communications device, a media gateway, a home media management system, a robotically controlled device, a robotically controller cleaning device such as a Broomba®, a media server, a game console, a network server, a network storage device, a wireless speaker, a customer engagement platform, a customer engagement portal, retail energy provider's server, a wholesale energy provider's server, a COOP energy provider's server, a retail business server, a commercial site server, an industrial site server, a multi-residential site server, a temporary lodging server, a hotel server, a motel server, a condominium server, a utility provider's server which can include waste, water, power or combinations thereof, an energy substation, a news media server, a weather server, an advertisement server or service provider, a network radio server or service provider, a network media server or service provider, a music server or service provider, a search engine server or service provider, an information server or service provider, a wireless information network device, a vehicle charging station, a renewable energy production device, a renewable energy control device, an energy storage management system, a smart appliance, an HVAC system, a water pump, a heat pump, a hot water heater, a thermostat (TSTAT), an energy controller, an irrigation system, a lighting system, an alarm system, a smart power outlet, an energy detection device, a garage door opening system or device, a power measurement device, a power measurement unit, an air handler, a wireless air damper, a humidity control system, a heat and motion sensing device, a smart power outlet, a switch router, a wireless router, an automobile or transportation device, an electric vehicle, a network communication device, or any other suitable device or system, and can vary in size, shape, performance, functionality, and price.
According to an aspect, a network device, environment coordinator, or sensor can include one of a combination of memory, processing resources or controllers such as a microcontroller or central processing unit (CPU) or hardware or software control logic to enable management of a resource. Additional components can include one or more storage devices, one or more wireless, wired or any combination thereof of communication devices, modules, and ports to communicate with external resources as well as various input and output (I/O) devices, touch controllers, touch screens and display devices. A resource can also include one or more buses operable to transmit communication of management information between the various hardware components, and can communicate using wire-line communication data buses, wireless network communication, or any combination thereof. For example, a resource can deploy communication using a data bus internal to a device and can also include using a network, wireless network, wireless energy network, an information network, a wireless environment network, a wireless home environment network, or any other type of network capable of communicating resource information.
According to a further aspect, a network device, environment coordinator, or sensor can use any combination of components, devices or modules to communicate information, including various types and variants of wireless and wire-line communication configurable to manage and establish communication at a site, including associated protocols or enhancements thereto including, but not limited to, any combination or portion of, IP-based communication, Broad-band communication, IEEE 802.15-based wireless communication, Zigbee communication, INSETEON communication, X10 communication protocol, Z-Wave communication, Bluetooth communication, Bluetooth Low Energy (LE) communication, WIFI communication, IEEE 802.11-based communication, a communication within a frequency range of 900 MHz-2.5 GHz; Infrared communication device, 6LowPAN communication, power line communication device, RFID communication, NFC communication, IEEE 802.16-based communication, Infrared-based communication, various proprietary wireless communications, or any combination thereof.
According to a further aspect, information can include information that can be processed and used by a network device, environment coordinator, or intelligent remote sensor and can include information that can be used to manage an environment, or any combination of thereof, and can include information received from a variety of sources. According to an aspect, information can include customer engagement information, media management information, media availability information, resource management information, media data, energy data, control data, content, media content, advertisements, videos, music, animated advertisements, energy management information, profile information, user information, device information, provisioning information, device identifiers, device names, model numbers, serial numbers, activation data such as date and time first used, IP addresses, coordinates of a site, coordinates of a resource, device drivers, and various other types of information described herein.
As described herein, a flow charted technique, method, or algorithm may be described in a series of sequential actions. Unless expressly stated to the contrary, the sequence of the actions and the party performing the actions may be freely changed without departing from the scope of the teachings. Actions may be added, deleted, or altered in several ways. Similarly, the actions may be re-ordered or looped. Further, although processes, methods, algorithms or the like may be described in a sequential order, such processes, methods, algorithms, or any combination thereof may be operable to be performed in alternative orders. Further, some actions within a process, method, or algorithm may be performed simultaneously during at least a point in time (e.g., actions performed in parallel), can also be performed in whole, in part, or any combination thereof.
As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having” or any other variation thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, article, system, or apparatus that comprises a list of features is not necessarily limited only to those features but may include other features not expressly listed or inherent to such process, method, article, system, or apparatus. Further, unless expressly stated to the contrary, “or” refers to an inclusive-or and not to an exclusive-or. For example, a condition A or B is satisfied by any one of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and both A and B are true (or present).
Also, the use of “a” or “an” is employed to describe elements and components described herein. This is done merely for convenience and to give a general sense of the scope of the invention. This description should be read to include one or at least one and the singular also includes the plural, or vice versa, unless it is clear that it is meant otherwise. For example, when a single device is described herein, more than one device may be used in place of a single device. Similarly, where more than one device is described herein, a single device may be substituted for that one device.
Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Although methods and materials similar or equivalent to those described herein can be used in the practice or testing of embodiments of the present invention, suitable methods and materials are described below. All publications, patent applications, patents, and other references mentioned herein are incorporated by reference in their entirety, unless a particular passage is cited. In case of conflict, the present specification, including definitions, will control. In addition, the materials, methods, and examples are illustrative only and not intended to be limiting.
To the extent not described herein, many details regarding specific materials, processing acts, and circuits are conventional and may be found in textbooks and other sources within the computing, electronics, and software arts.
According to an aspect, system and network 100 are configured to automatically coordinate environments and network devices while users or mobile devices are away from a site, then provide automatic control within regions, rooms, or zones within the site as described herein. System and network 100 are configured to provide macro-proximity initiated environments and micro-proximity initiated environments to control coordinating home environments, resulting in user benefits that are simple to use, and cost effective.
According to an aspect, mobile device 102 can include various types of devices that can be portable, such as an iPhone® device, Android® device, Blackberry® device, Windows® device, or any other mobile device, and can also include a tablet device such as an iPad®, Kindle®, and the like, a portable computer such as a laptop, portable electronics such as camera's, wireless radios, wireless speakers, or various other portable devices capable of being used with environmental coordinating system and network 100.
According to an aspect, communication with environment coordinator 106 can exist in a variety of embodiments as described above, including but not limited to network devices, mobile devices, sensors, and systems and include using any combination of communication described herein. For example, mobile device 102 can communicate directly with environment coordinator 106 using a local WIFI or 802.11 based communication, Bluetooth communication, or various other local wireless communication, or any combination thereof. According to a further aspect, mobile device 102 can communication within a mobile environment using a subscriber based wireless data communication network such as a 3G network, 4G network, EDGE network, a cellular network, other wireless data communication, or any combination thereof.
According to another aspect, public resourced 112 can be provided. Pubic resources 112 can include hosted resources that are generally publically available, or with minimal effort, can be accessed and utilized. Resources can include storage resources, communication infrastructure resources such as PUB-SUB, XMPP, instant Messaging (IM), SMS messaging, TCP/IP, Internet communication infrastructure and protocol such as IPv4, IPv6 to support, in addition to other features, unique addresses for resources, and various other types of public resources that can be used in combination with communicating information using Internet 110.
According to another aspect, resource management system 100 can include using one or more cloud services 110. Cloud services 110 can be hosted by the same provider or in other instances, cloud services 110 can be hosted by multiple providers and accessed as needed or desired in various combinations. Cloud services 110 can include one or combinations of, but are not limited to, sources that can include resource information such as a streaming music library source, streaming radio source, streaming video source, pay-per-view media source, paid music source, subscription services source, on-line photo source, energy management source, customer engagement source, utility source, thermostat management source, web-services source, home security source, website, customer engagement source, savings tip source, video source, software update source, a streaming music library source, or any combination thereof.
According to a further aspect, a coordinator, for example, an environment coordinator 106 or an event coordinator can allow for enabling access to one or more on-line streaming media sources, such as Pandora, Slacker Radio, Spotify, TuneIn Radio, Weather services, YouTube, and any other combination of cloud services 112. For example, environment coordinator 106 can include encoded logic capable of accessing an API hosted by Pandora, and can manage streaming audio to one or more wireless speaker resources within a home. As such, environment coordinator 106 can act as a bridge between Pandora and a wireless speaker, or can also act as a temporary bridge to initiate direct communication with a speaker resource. Additionally, a user may be able to select music from mobile device 102 or another resource capable of allowing selection of music from Pandora's hosted services, and communicating to a speaker resource.
According to a further aspect, mobile device 102 can also include proximity control functionality. For example, proximity control can include using various types of location services to detect a location of mobile device 102, and outputting resource information based on the location, distance, travel time, travel speed, and various other parameters that can be determined using location services. According to an aspect, other web services that may be cloud services 110 can also be accessed upon detecting a location of mobile device 102. Additionally, environment information and sensor based information may be communicated in response to a location of mobile device 102.
According to an aspect, site 200 includes a kitchen 202, a living room 204, a utility room 206, a bedroom 208, and a hallway 210. Though not expressly illustrated, it should be understood that doors, windows, locks and various other building materials may be used at site 200. Each room also includes various other types of network devices that can be accessed within site 200. For example, kitchen 202 can include an oven, lights, a dishwasher, a refrigerator, and one or more power switches (each not expressly shown). Similarly, living room 204 can include a television, lights, a camera, and one or more power switches (each not expressly shown). Utility room 206 can include a camera, a washer, a dryer, indoor and outdoor lights, and one or more power switches (each not expressly shown). Bedroom 208 can include lights, shades, a TV, a fan, a speaker, and one or more power switches (each not expressly shown). Hallway 210 can include a thermostat, a camera, a doorbell, indoor and outdoor lights, and one or more power switches (each not expressly shown). Each network device shown in
For purposes of the disclosure, the network devices can be accessed and controlled by sensors and remote sensors, controllers and environment coordinators, mobile devices, mobile applications, or various other devices or combinations thereof at site 200. For example, an owner or user of site 200 can possess a mobile device 224 having an operating system, mobile applications, or various other device communication capabilities configured to modify, access, or control an environment at site 200.
According to a further aspect, site 200 also includes distributed sensors within each room of site 200. Each sensor can be placed within each room and can be provided as intelligent remote sensors (described below). For example, kitchen 202 can include a first sensor 214, living room 204 can include a second sensor 216, utility room 206 can include a third sensor 220, bedroom 208 can include a fourth sensor 218, and hallway 210 can include a fifth sensor 222. Although illustrated as being within each of the rooms, one or more of the sensors can be placed internal or external to the building or walls of site 200.
According to an aspect, site 200 also includes a thermostat 212 placed within hallway 210 to regulate temperature at site 200. Various forms of communication can be deployed to connect with thermostat 212 and thermostat 212 illustrates an example of a network device having environment coordinator capabilities (described below). For purposes of describing the system of
According to an aspect, the system of
In other forms, each sensor can communicate through mobile device 224 to provide sensory date to an environment coordinator. For example, a sensor can detect an availability to communicate sensory data using a mobile application of a mobile device configured to communicate with an environment coordinator such as thermostat 212. For example, mobile device may communicate with sensor using Bluetooth LE and mobile device may receive information using Bluetooth LE and communicate to thermostat 212 using another network such as Wi-Fi. In this manner,
In other forms, the sensors can communicate directly to an environment coordinator 212 and coordinator 212 can initiate coordinating environments on a room-by-room basis.
According to another aspect, site 200 can include thermostat 212 capable of coordinating environments within site 200. For example, thermostat 212 can be configured to communicate with each sensor installed at site 200 using low-power communication such as Bluetooth LE, Zigbee, or Z-Wave. Thermostat 212 can include an environment coordinator that manages environments using sensory-based information communicated from a sensor. For example, sensory-based information can include an operating status of a Z-wave enable LED light, and a Zigbee enabled power switch. Additionally, the intelligent remote sensor may communicate sensory-based information received from the Z-wave LED and the Zigbee enabled switch to thermostat 212 using Bluetooth LE communication. As such, multi-network communication can be combined into a Bluetooth LE communication that can be sent to thermosat 212 over a Bluetooth network.
According to a further aspect, intelligent remote sensor may also detect a temperature within a room and whether an individual is present within the room. As such, thermostat 212 can receive the sensory information and process accordingly. For example, if a user is present within a room, and an LED light is on, additional information such as room temperature may be obtained. A user may have set up an environment preference to have the temperature sensed by intelligent remote sensor used by thermostat 212 to manage temperature within another room. For example, thermostats are typically installed in remote places such as hallway 212 and away from living spaces such as living room 204. As such, the temperature read in the hallway is typically used to control the temperature throughout site 200, with no regard to a presence of a user or desire to have a temperature changed. Using sensor 216 within living room 204 and presence awareness, sensor information that includes the actual room temperature can be communicated to thermostat 212 and thermostat 212 can modify heating and cooling conditions using the temperature sensory information. In this manner, a user can move from room to room and have room temperatures sensed end communicated to thermostat 212. Thermostat 212 can then coordinate environments for the user.
According to a further aspect, mobile device 224 can be used to initiate or maintain coordination of environments at site 224. For example, general settings and applications loaded within mobile device 224 can be used to coordinate environments on a room-by-room, or site-by-site basis. Such coordination settings can be stored on mobile device 224, and can be sent to various other network devices at site 200, or another event coordinator deployed at site 200. According to an aspect, the system of
According to a further aspect, an environment can be coordinated without mobile device 224 being present within a room. For example, a user may be charging mobile device 224 in kitchen 202. However, as a user enters bedroom 208, a user may want the lights to turn on, music to begin playing, and shades to be drawn. Sensor 218 can be manually selected or touched to initiate having each desired network device be altered to a desired operating condition. Sensor 218 can then send a signal to an environment coordinator to initiate altering operating conditions and create an environment. In this manner, mobile device 224 need not be present to coordinate an environment.
According to a further aspect, a sensor can include multiple environments preloaded or created to be used. For example, a user may have programmed multiple environments to be used in a room either by manual selection, selection through a schedule, or automatic selection based on a presence. For example, a user may have various combinations of network devices and operating conditions altered by multiple taps on a touch button of a sensor. In this manner, lights can be increased or dimmed, colors changed, shades drawn up, down, partial, dishwasher turning on or off, temperature regulated in a room, television turning on or off, or a variety of other actions desired by a user to coordinate an environment. According to some aspects, actions or events can be preloaded and a user can access as network devices are installed and connected at site 200. According to a further aspect, a user can schedule use of a network device using a scheduling tool (not expressly show) to coordinate environments. A scheduling tool that creates time of day, days, weeks, etc. schedules can be created and accessed by intelligent remote sensor to coordinate an environment. As such, various combinations of environments can be accessed through manual selection, selecting a schedule, or automatic selection based on a presence.
According to an aspect, automatic environment coordination can be obtained using Bluetooth LE or iBeacon technology deployed by mobile device 224 and a sensor. For example, sensor 216 can be set up to transmit a Bluetooth LE signal having a specific range to create a zone within living room 204. As a user having mobile device 224 enters the zone or living room 204, sensory information can be read by mobile device 224 and an environment can be automatically coordinated for network devices. Similarly, as mobile device 224 leaves living room 204, a Bluetooth LE or iBeacon signal can be lost and another environment for living room 204 can be coordinated. In this manner, room-by-room or zone-by-zone environments can be automatically created. According to an aspect, a sensor, mobile device, or network device can be used to coordinate an environment when a Bluetooth LE or iBeacon signal is obtained or lost between a sensor and a mobile device.
According to an aspect, multiple mobile devices can be used at site 200. For example, the system in
According to a further aspect, sensors can be used to extend the range. For example, if a short range wireless communication is being used by a sensor, one ore more sensors can be used to connect or bridge a signal to another sensor. For example, thermostat 212 may want to receive sensory data from remote sensor 214 to manage temperature within kitchen 202. Additionally, thermostat 214 may be using Bluetooth LE as a primary wireless communication to sensors. However, sensor 214 may be out of range. As such, sensor 222 can serve as an extender to communicate sensory data between sensor 214 and thermostat 212. Other sensors can also be added or connected to such as sensor 216 or others as needed or desired. In this manner, a mesh-like network can be created to communicate sensory-enabled information at site 200.
According to another aspect, management of power consumption of sensors can be done based on a presence of a user external and internal to site 200. A key attribute to wireless devices such as sensors in
According to another aspect, battery consumption can be reduced based on a presence of a user at a site. For example, as mobile device 224 moves away from site 200, wireless signals of each sensor, or a select group of sensors, can be reduced. For example, signal strength and frequency can be reduced as a user exceeds a distance, geofence, loss of Wi-Fi, and the like. As a user begins to travel or arrives home and distance, geofence, Wi-Fi, etc. is detected, signal strength and frequency of a sensor can be increased as desired. In this manner, batteries that may normally only last for 6 months can be extended to 2-5 years thereby reducing the need to purchase and consume batteries on a frequent basis.
According to an aspect, front view 08 includes a front surface 310 including a lighting and touch sensors to manually activate use of sensor 300. Front surface 310 includes a main touch sensor 324, and several indicators or visual lighting surfaces that can be illuminated. For example, front surface 310 include a first LED 312, a second LED 314, a third LED 316, a fourth LED 320, and a fifth LED 322. Various other LEDs can be added or removed as desired. During use, touch sensor 324 can also be illuminated using an LED or light pipe that extends around touch sensor 324.
According to a further aspect, side view 328 illustrates sensor 300 having a wedge like or angled surface 330 to allow for ease of use. Sensor 300 also include a cavity 334 along side surface 332 to allow for accessing one or more batteries 336 used to power sensor 300.
During use, sensor 300 can be automatically used through the use of Bluetooth or other wireless communication as described herein. Sensor 300 can also be manually used to enable and disable use of various network devices. For example, a user can touch sensor 324 to enable manual use of sensor 300 which can include accessing a variety of sensor enabled information that can be used to alter an operating condition of a network device.
According to an aspect, various types of sensor based information can be used with sensor 400. For example, sensor based information can include information from temperature sensing, humidity sensing, network availability sensing, network device sensing, connected network device sensing, power management sending, proximity sensing, distance sensing, motion sensing, sound sensing, light sensing, airflow sensing, face recognition sensing, thumb or finger I.D. sensing, or various other types of sensing and combinations thereof.
During use, sensor 400 can be used to communicate information to an environment coordinator deployed by a remote device such as a network device. According to an aspect, communication device(s) 412 can be configured to communicate with a mobile device and an environment coordinator located at a site such as illustrated by example in
According to another aspect, According to a further aspect, memory 408 can include any combination of ROM, PROM, EPROM, EEPROM, Flash, or various other types of storage mediums including solid state, optical drives, HDD, or any combination thereof.
According to a further aspect, memory 408 can store setting information, sensory based information, modules, software, firmware, or various other types of information that can be used by processor 402. In other forms, portions or all of a module can be stored within a another electronic device that can be access by processor 402. In this manner, a component or device can provide sensory based information directly to processor 402 or in other forms processor 402 can operate a module as software or firmware using memory 408.
According to an aspect, processor 402 can include an ARM based processor, and in some forms can include Freescale® i.MX-based processor, Kinetis processor, an Intel Atom® processor, or a small form factor processor that may be integrated into another component such as a wireless module have processing capabilities. Various other types of processors can me used. Processor 402 can also include an operating system, such as Linux, that can be executed by processor 402, and in one aspect, can include a Java environment to process Java code and applications. Other software environments, included embedded software can also be supported in stead of, or in addition to, as needed or desired.
In other forms, lighting and display 424 can include various types of display technologies can be used having single color, multicolor, or any combination thereof, including, but not limited to LED displays, TFT displays, OLED displays, LCD displays, flexible lighting displays, flexible LED displays, thin film over LED, a pico projector, or any combination thereof. Touch sensor/selector 404 can include various types and combinations of touch technologies can also be used including, but not limited to, resistive touch sensors, capacitive touch sensors, motion detecting sensors, infrared sensors, heat sensors, or various other types of sensors that can be used to detect an input from a user.
According to a further aspect, communication device(s) 412 can be configured to use any combination of hardware, software, or firmware, and can include any combination or portion of a serial bus interface, a network bus interface, a parallel bus interface, a serial-parallel bus interface, a universal serial bus interface, industry standard bus interface, controller area network bus interface, a serial peripheral interface, an HDMI interface, a universal asynchronous receiver transmitter interface, a control bus interface, standard digital input output interface, a proprietary bus interface, or any combination thereof. Additionally, communication module 418 can also include an information network interface, a network device identifier and profile information of module, wireless energy network message information, network protocol configuration data, or any combination thereof. Further, communication tunneling module 428 can include portions or all of the configuration of communication device(s) 412 and an embodiment can be integrated as a part of communication devices (412).
According to an aspect, sensor 400 can be configured to include one or more communication device(s) 412 in module or chip form including, but not limited to, power-line communication, wire-line communication, wireless communication, Zigbee based communication, INSETEON based communication, X10 based communication, Z-Wave based communication, WiMAX based communication, Bluetooth-based communication, Bluetooth LE based communication, iBeacon communication, WIFI based communication, 802.11-based communication, 802.15-based communication, 802.16-based communication, proprietary communication, other communications described herein, or any combination thereof.
According to an aspect, sensor 400 can also include an expansion slot (not expressly illustrated) such as a network interface card (NIC), Ethernet port, one or more USB interfaces or mini-USB interfaces, an SDIO slot, additional data or plug interfaces, Zigbee and Z-wave slot interfaces, or any combination thereof to increase memory capacity or other functionality that be added to sensor 400.
According to a further aspect, sensor 400 can include use various other smart energy protocols configured to communicate using a smart energy protocol and one or more communication devices. According to an aspect, sensor 400 can incorporate Smart Energy Profile (SEP) version 2.0, herein incorporated by reference, or various other updates to SEP 2.0, and in some forms, previous versions of SEP can also co-exist with SEP 2.0 or later versions. For example, sensor 400 can receive information formatted to various versions of SEP standards and processed accordingly. As such, sensor 300 can be used to comply with Zigbee standards including, but not limited to, building automation, remote control, smart energy, health care, home automation, telecom services, network devices, gateways, wearables or any combination thereof. According to an aspect, various other types of profiles or protocols can be used by sensor 400 and can be updated to add, delete, and modify as needed and can include any combination of a Smart Energy based profile, a Echonet Lite based profile, a Echonet based profile, a UPNP based profile, a DLNA based profile, a environment management based profile, a customer engagement based profile, an AirPlay based profile, a user profile, a device profile, a system profile, a source profile, customer profile, a site profile, custom or proprietary profile, or any combination thereof stored within memory 408. According to an aspect, a profile can include only protocol information specific to a network device as well to limit the amount of memory 408 needed by sensor 400.
According to a further aspect, communication device(s) 412 can be used in one or more different operating modes including, but not limited to, a bridge, an access point, a router, a network, an end point, a mesh network, a star network or various other types of network topologies and configurations and needed or desired.
According to a further aspect, sensor 400 can include one or more input sensor(s) 430 capable of providing inputs and used by sensor 400 and modules. For example, inputs sensor(s) 430 can include temperature sensors, humidity sensors, light sensors, motion sensors, IR sensors, cameras or optical sensors, kinetic sensors, power sensing devices including electronic sensors, including, but not limited to current sensors, voltage sensors, impedance sensors, microphones, or any combination thereof. Other sensors can also include combinations of network bandwidth sensors, wireless signal sensors, bit-rate sensors communicating data, audio sensors, or various other types of input sensors that can be used by sensor 400.
According to a further aspect, sensor 400 can also include a near field communication (NFC) sensing module 426 that can be provided as a reader, a passive device or tag, or a combination thereof. For example, sensor 400 can use NFC sensing module 426 to add or provision additional network devices that can be access and managed by sensor 400. As such, a new network device can be placed in close proximity to sensor 400. Provisioning information of the additional resource can then be used as needed. For example, provisioning information can include communication profile information, device identifiers, or various other types of information that can be used to provision the network device.
According to a further aspect, NFC sensing module 426 can be scanned by a third party NFC reader interested in sensor 400. For example, model information, website information, mobile application, advertisement information, pricing information, supported communications, website reviews or links to reviews capable of providing reviews about sensor 400, or any combination thereof.
According to another aspect, sensor 400 can access information, such as a network device profile and use the network device profile to output a message receivable by a specific network device. For example, network device data can be formatted using a network device profile of a specific network type of the wireless energy network. In some forms, a network device profile may not include information sufficient to output network device data.
As such, profile modifiers can be provided and can include profile modification data of the resource. Sensor 400 can be used to access, create and manage operating conditions, home profiles, user profiles, device profiles, user schedules, proximity detection, demand response preferences, energy savings preferences, other control settings, or any combination thereof. Other settings and operating conditions can be accessed, monitored, or managed as needed or desired.
In other forms, provisioning of sensor 400 can include enabling sensor 400 to have access to one or more types of networks. For example, a sensor 400 may include a Z-Wave communication device. As such, an NFC sensing module 426 can include a Z-Wave profile information, and credentials to enable a network device to be used at a site. In other forms, a combination of communication devices may be provided within sensor 400. As such, an NFC sensing module 426 or an NFC device can include credentials for multiple communication devices and may communicate information to enable management or use of sensor 400.
According to a further aspect, communication device(s) 412 can also include using channel I.D.'s, PAN I.D.'s, Device I.D.'s, an can further include providing a location of a network device, a group of network devices, a device type, security information, a network key, device profile information including information sufficient to enable communication between a network device and sensor 400.
Note that not all of the activities described above in the general description or the examples are required, that a portion of a specific activity may not be required, and that one or more further activities may be performed in addition to those described. Still further, the order in which activities are listed are not necessarily the order in which they are performed.
The specification and illustrations of the embodiments described herein are intended to provide a general understanding of the structure of the various embodiments. The specification and illustrations are not intended to serve as an exhaustive and comprehensive description of all of the elements and features of apparatus and systems that use the structures or methods described herein. Many other embodiments may be apparent to those of skill in the art upon reviewing the disclosure. Other embodiments may be used and derived from the disclosure, such that a structural substitution, logical substitution, or another change may be made without departing from the scope of the disclosure. Accordingly, the disclosure is to be regarded as illustrative rather than restrictive.
Certain features are, for clarity, described herein in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features that are, for brevity, described in the context of a single embodiment, may also be provided separately or in any sub combination. Further, reference to values stated in ranges includes each and every value within that range.
Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any feature(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature of any or all the claims.
The above-disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover any and all such modifications, enhancements, and other embodiments that fall within the scope of the present invention. Thus, to the maximum extent allowed by law, the scope of the present invention is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description.
If terms used herein, including the specification or claims, are not expressly worded in means-plus-function format such as through the use of the terms “means”, it is the express intent of the inventor(s) that such terms are not to be governed by 35 U.S.C. 112(6).
Although only a few exemplary embodiments have been described in detail above, those skilled in the art will readily appreciate that many modifications are possible in the exemplary embodiments without materially departing from the novel teachings and advantages of the embodiments of the present disclosure. Accordingly, all such modifications are intended to be included within the scope of the embodiments of the present disclosure as defined in the following claims. In the claims, means-plus-function clauses are intended to cover the structures described herein as performing the recited function and not only structural equivalents, but also equivalent structures.
This application claims the benefit of and priority to U.S. provisional application Ser. No. 61/924,048 filed Jan. 6, 2014, the entire disclosure of which is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
1568584 | Blankenship | Jan 1926 | A |
2042633 | Richardson | Jun 1936 | A |
2427965 | Henderson | Sep 1947 | A |
2931006 | Klumpp, Jr. | Mar 1960 | A |
2960677 | Stearn et al. | Nov 1960 | A |
3194957 | Caldwell et al. | Jul 1965 | A |
3237148 | Ege | Feb 1966 | A |
3531759 | Hansen | Sep 1970 | A |
3675183 | Drake | Jul 1972 | A |
3808602 | Hoeffel et al. | Apr 1974 | A |
4407447 | Sayegh | Oct 1983 | A |
4437716 | Cooper | Mar 1984 | A |
4497031 | Froehling et al. | Jan 1985 | A |
4645286 | Isban et al. | Feb 1987 | A |
5127575 | Beerbaum | Jul 1992 | A |
5274571 | Hesse et al. | Dec 1993 | A |
5289362 | Liebl et al. | Feb 1994 | A |
5461390 | Hoshen | Oct 1995 | A |
5476221 | Seymour | Dec 1995 | A |
5537339 | Naganuma et al. | Jul 1996 | A |
5544036 | Brown, Jr. et al. | Aug 1996 | A |
5566084 | Cmar | Oct 1996 | A |
5595342 | McNair et al. | Jan 1997 | A |
5682949 | Ratcliffe et al. | Nov 1997 | A |
5725148 | Hartman | Mar 1998 | A |
5729442 | Frantz | Mar 1998 | A |
5764146 | Baldwin et al. | Jun 1998 | A |
5812949 | Taketsugu | Sep 1998 | A |
5819840 | Wilson et al. | Oct 1998 | A |
5884072 | Rasmussen | Mar 1999 | A |
5964625 | Farley | Oct 1999 | A |
5987379 | Smith | Nov 1999 | A |
6014080 | Layson, Jr. | Jan 2000 | A |
6073019 | Lowdon | Jun 2000 | A |
6108614 | Lincoln et al. | Aug 2000 | A |
6128661 | Flanagin et al. | Oct 2000 | A |
6175078 | Bambardekar et al. | Jan 2001 | B1 |
6353180 | Debartolo, Jr. et al. | Mar 2002 | B1 |
6400956 | Richton | Jun 2002 | B1 |
6442639 | McElhattan | Aug 2002 | B1 |
6478233 | Shah | Nov 2002 | B1 |
6483028 | Debartolo, Jr. et al. | Nov 2002 | B2 |
6553418 | Collins et al. | Apr 2003 | B1 |
6623311 | Dehan | Sep 2003 | B1 |
6636893 | Fong | Oct 2003 | B1 |
6684087 | Yu et al. | Jan 2004 | B1 |
6785542 | Blight et al. | Aug 2004 | B1 |
6785630 | Kolk et al. | Aug 2004 | B2 |
6850252 | Hoffberg | Feb 2005 | B1 |
6868293 | Schurr et al. | Mar 2005 | B1 |
6975958 | Bohrer et al. | Dec 2005 | B2 |
6976366 | Starling et al. | Dec 2005 | B2 |
6980659 | Barnum | Dec 2005 | B1 |
6999757 | Bates et al. | Feb 2006 | B2 |
7016751 | Nordquist et al. | Mar 2006 | B2 |
7031945 | Donner | Apr 2006 | B1 |
7082460 | Hansen et al. | Jul 2006 | B2 |
7083109 | Pouchak | Aug 2006 | B2 |
7099483 | Inagaki | Aug 2006 | B2 |
7114554 | Bergman et al. | Oct 2006 | B2 |
7127328 | Ransom | Oct 2006 | B2 |
7127734 | Amit | Oct 2006 | B1 |
7130719 | Ehlers et al. | Oct 2006 | B2 |
7139564 | Hebert | Nov 2006 | B2 |
7140551 | De Pauw et al. | Nov 2006 | B2 |
7155305 | Hayes et al. | Dec 2006 | B2 |
7159789 | Schwendinger et al. | Jan 2007 | B2 |
7188003 | Ransom et al. | Mar 2007 | B2 |
7197011 | Fong | Mar 2007 | B2 |
7216021 | Matsubara et al. | May 2007 | B2 |
7222800 | Wruck | May 2007 | B2 |
7224966 | Caspi et al. | May 2007 | B2 |
7257397 | Shamoon et al. | Aug 2007 | B2 |
7343226 | Ehlers et al. | Mar 2008 | B2 |
7349761 | Cruse | Mar 2008 | B1 |
7363053 | Dalton et al. | Apr 2008 | B2 |
7403838 | Deen et al. | Jul 2008 | B2 |
7444401 | Keyghobad et al. | Oct 2008 | B1 |
7451017 | McNally | Nov 2008 | B2 |
7460827 | Schuster et al. | Dec 2008 | B2 |
7477617 | Chen et al. | Jan 2009 | B2 |
7510126 | Rossi et al. | Mar 2009 | B2 |
7525425 | Diem | Apr 2009 | B2 |
7526539 | Hsu | Apr 2009 | B1 |
7554437 | Axelsen | Jun 2009 | B2 |
7565225 | Dushane | Jul 2009 | B2 |
7567844 | Thomas et al. | Jul 2009 | B2 |
7574208 | Hanson et al. | Aug 2009 | B2 |
7574283 | Wang et al. | Aug 2009 | B2 |
7590703 | Cashman et al. | Sep 2009 | B2 |
7644591 | Singh et al. | Jan 2010 | B2 |
7665670 | Ahmed | Feb 2010 | B2 |
7668532 | Shamoon et al. | Feb 2010 | B2 |
7671544 | Clark et al. | Mar 2010 | B2 |
7693581 | Callaghan et al. | Apr 2010 | B2 |
7706928 | Howell et al. | Apr 2010 | B1 |
7715951 | Forbes et al. | May 2010 | B2 |
7747739 | Bridges et al. | Jun 2010 | B2 |
7752309 | Keyghobad et al. | Jul 2010 | B2 |
7761910 | Ransom | Jul 2010 | B2 |
7775453 | Hara | Aug 2010 | B2 |
7783738 | Keyghobad et al. | Aug 2010 | B2 |
7792946 | Keyghobad et al. | Sep 2010 | B2 |
7798417 | Snyder et al. | Sep 2010 | B2 |
7812766 | Leblanc et al. | Oct 2010 | B2 |
7813831 | McCoy et al. | Oct 2010 | B2 |
7865252 | Clayton | Jan 2011 | B2 |
7881816 | Mathiesen et al. | Feb 2011 | B2 |
7884727 | Tran | Feb 2011 | B2 |
7886166 | Schnekendorf et al. | Feb 2011 | B2 |
7895257 | Helal et al. | Feb 2011 | B2 |
7908019 | Ebrom et al. | Mar 2011 | B2 |
7908116 | Steinberg et al. | Mar 2011 | B2 |
7908117 | Steinberg et al. | Mar 2011 | B2 |
7912559 | McCoy et al. | Mar 2011 | B2 |
7917914 | McCoy et al. | Mar 2011 | B2 |
7918406 | Rosen | Apr 2011 | B2 |
7921429 | McCoy et al. | Apr 2011 | B2 |
7941530 | Ha et al. | May 2011 | B2 |
7949615 | Ehlers et al. | May 2011 | B2 |
7953518 | Kansal et al. | May 2011 | B2 |
7973707 | Verechtchiagine | Jul 2011 | B2 |
7975051 | Saint Clair et al. | Jul 2011 | B2 |
7979163 | Terlson et al. | Jul 2011 | B2 |
8005780 | McCoy et al. | Aug 2011 | B2 |
8010237 | Cheung et al. | Aug 2011 | B2 |
8010418 | Lee | Aug 2011 | B1 |
8010812 | Forbes, Jr. et al. | Aug 2011 | B2 |
8019445 | Marhoefer | Sep 2011 | B2 |
8024073 | Imes et al. | Sep 2011 | B2 |
8028049 | Ellis et al. | Sep 2011 | B1 |
8028302 | Glotzbach et al. | Sep 2011 | B2 |
8032233 | Forbes, Jr. et al. | Oct 2011 | B2 |
8042048 | Wilson et al. | Oct 2011 | B2 |
8049592 | Wang et al. | Nov 2011 | B2 |
8063775 | Reed et al. | Nov 2011 | B2 |
8082065 | Imes et al. | Dec 2011 | B2 |
8090477 | Steinberg | Jan 2012 | B1 |
8091765 | Jiang et al. | Jan 2012 | B2 |
8091795 | McLellan et al. | Jan 2012 | B1 |
8099195 | Imes et al. | Jan 2012 | B2 |
8099198 | Gurin | Jan 2012 | B2 |
8108076 | Imes et al. | Jan 2012 | B2 |
8117299 | Narayanaswami et al. | Feb 2012 | B2 |
8126685 | Nasle | Feb 2012 | B2 |
8131401 | Nasle | Mar 2012 | B2 |
8140279 | Subbloie | Mar 2012 | B2 |
8140667 | Keyghobad et al. | Mar 2012 | B2 |
8176112 | Hicks, III et al. | May 2012 | B2 |
8204979 | Vutharkar et al. | Jun 2012 | B2 |
8214270 | Schaefer et al. | Jul 2012 | B2 |
8280556 | Besore et al. | Oct 2012 | B2 |
8306634 | Nguyen et al. | Nov 2012 | B2 |
8350694 | Trundle et al. | Jan 2013 | B1 |
8355865 | Wagner et al. | Jan 2013 | B2 |
8406783 | Eitan et al. | Mar 2013 | B2 |
8406933 | Nagel et al. | Mar 2013 | B2 |
20020073217 | Ma et al. | Jun 2002 | A1 |
20020147006 | Coon et al. | Oct 2002 | A1 |
20020194500 | Bajikar | Dec 2002 | A1 |
20020196151 | Troxler | Dec 2002 | A1 |
20020198984 | Goldstein et al. | Dec 2002 | A1 |
20030120817 | Ott et al. | Jun 2003 | A1 |
20030122684 | Porter et al. | Jul 2003 | A1 |
20030149734 | Aaltonen et al. | Aug 2003 | A1 |
20030210126 | Kanazawa | Nov 2003 | A1 |
20040034484 | Solomita, Jr. et al. | Feb 2004 | A1 |
20040078153 | Bartone et al. | Apr 2004 | A1 |
20040087314 | Duncan | May 2004 | A1 |
20040119600 | Hampton | Jun 2004 | A1 |
20040133314 | Ehlers et al. | Jul 2004 | A1 |
20040193329 | Ransom et al. | Sep 2004 | A1 |
20050038326 | Mathur | Feb 2005 | A1 |
20050040247 | Pouchak | Feb 2005 | A1 |
20050040250 | Wruck | Feb 2005 | A1 |
20050044427 | Dunstan et al. | Feb 2005 | A1 |
20050060575 | Trethewey et al. | Mar 2005 | A1 |
20050090267 | Kotzin | Apr 2005 | A1 |
20050131583 | Ransom | Jun 2005 | A1 |
20050143863 | Ruane et al. | Jun 2005 | A1 |
20050144437 | Ransom et al. | Jun 2005 | A1 |
20050172056 | Ahn | Aug 2005 | A1 |
20050194457 | Dolan | Sep 2005 | A1 |
20050242945 | Perkinson | Nov 2005 | A1 |
20050246561 | Wu et al. | Nov 2005 | A1 |
20060012489 | Yokota et al. | Jan 2006 | A1 |
20060063522 | McFarland | Mar 2006 | A1 |
20060097063 | Zeevi | May 2006 | A1 |
20060099971 | Staton et al. | May 2006 | A1 |
20060102732 | Garrett et al. | May 2006 | A1 |
20060122715 | Schroeder et al. | Jun 2006 | A1 |
20060161635 | Lamkin et al. | Jul 2006 | A1 |
20060179079 | Kolehmainen | Aug 2006 | A1 |
20060253894 | Bookman et al. | Nov 2006 | A1 |
20060265489 | Moore | Nov 2006 | A1 |
20060276175 | Chandran | Dec 2006 | A1 |
20060283965 | Mueller et al. | Dec 2006 | A1 |
20070032225 | Konicek et al. | Feb 2007 | A1 |
20070037554 | Feeny | Feb 2007 | A1 |
20070037605 | Logan | Feb 2007 | A1 |
20070043477 | Ehlers et al. | Feb 2007 | A1 |
20070043478 | Ehlers et al. | Feb 2007 | A1 |
20070045431 | Chapman et al. | Mar 2007 | A1 |
20070054616 | Culbert | Mar 2007 | A1 |
20070055760 | McCoy et al. | Mar 2007 | A1 |
20070060171 | Sudit et al. | Mar 2007 | A1 |
20070061050 | Hoffknecht | Mar 2007 | A1 |
20070061266 | Moore et al. | Mar 2007 | A1 |
20070061487 | Moore et al. | Mar 2007 | A1 |
20070112939 | Wilson et al. | May 2007 | A1 |
20070114295 | Jenkins | May 2007 | A1 |
20070115902 | Shamoon et al. | May 2007 | A1 |
20070124026 | Troxell et al. | May 2007 | A1 |
20070136217 | Johnson et al. | Jun 2007 | A1 |
20070155401 | Ward et al. | Jul 2007 | A1 |
20070156265 | McCoy et al. | Jul 2007 | A1 |
20070156864 | McCoy et al. | Jul 2007 | A1 |
20070156882 | McCoy et al. | Jul 2007 | A1 |
20070158442 | Chapman, Jr. | Jul 2007 | A1 |
20070160022 | McCoy et al. | Jul 2007 | A1 |
20070162158 | McCoy et al. | Jul 2007 | A1 |
20070168486 | McCoy et al. | Jul 2007 | A1 |
20070176771 | Doyle | Aug 2007 | A1 |
20070188319 | Upton | Aug 2007 | A1 |
20070197236 | Ahn et al. | Aug 2007 | A1 |
20070221741 | Wagner et al. | Sep 2007 | A1 |
20070240173 | McCoy et al. | Oct 2007 | A1 |
20070241203 | Wagner | Oct 2007 | A1 |
20070249319 | Faulkner et al. | Oct 2007 | A1 |
20070273307 | Westrick et al. | Nov 2007 | A1 |
20070274241 | Brothers | Nov 2007 | A1 |
20070282748 | Saint Clair et al. | Dec 2007 | A1 |
20070285510 | Lipton et al. | Dec 2007 | A1 |
20070287410 | Bae et al. | Dec 2007 | A1 |
20070287473 | Dupary | Dec 2007 | A1 |
20070288610 | Saint Clair et al. | Dec 2007 | A1 |
20070288975 | Cashman et al. | Dec 2007 | A1 |
20080004904 | Tran | Jan 2008 | A1 |
20080017722 | Snyder et al. | Jan 2008 | A1 |
20080046878 | Anderson | Feb 2008 | A1 |
20080082838 | Achariyakosol et al. | Apr 2008 | A1 |
20080099568 | Nicodem | May 2008 | A1 |
20080103610 | Ebrom et al. | May 2008 | A1 |
20080104208 | Ebrom et al. | May 2008 | A1 |
20080104212 | Ebrom et al. | May 2008 | A1 |
20080109830 | Giozbach et al. | May 2008 | A1 |
20080127325 | Ebrom et al. | May 2008 | A1 |
20080137670 | Ebrom et al. | Jun 2008 | A1 |
20080177678 | Di Martini et al. | Jul 2008 | A1 |
20080177994 | Mayer | Jul 2008 | A1 |
20080188963 | McCoy | Aug 2008 | A1 |
20080218307 | Schoettle | Sep 2008 | A1 |
20080219186 | Bell et al. | Sep 2008 | A1 |
20080219227 | Michaelis | Sep 2008 | A1 |
20080219239 | Bell et al. | Sep 2008 | A1 |
20080221737 | Josephson et al. | Sep 2008 | A1 |
20080249642 | Chen | Oct 2008 | A1 |
20080262820 | Nasle | Oct 2008 | A1 |
20080270562 | Jin | Oct 2008 | A1 |
20080271123 | Ollis et al. | Oct 2008 | A1 |
20080272934 | Wang et al. | Nov 2008 | A1 |
20080277486 | Seem et al. | Nov 2008 | A1 |
20080277487 | Mueller et al. | Nov 2008 | A1 |
20080281472 | Podgorny et al. | Nov 2008 | A1 |
20080281666 | Kessman et al. | Nov 2008 | A1 |
20080291855 | Bata et al. | Nov 2008 | A1 |
20080305644 | Noda | Dec 2008 | A1 |
20080313310 | Vasa et al. | Dec 2008 | A1 |
20090001182 | Siddaramanna et al. | Jan 2009 | A1 |
20090005061 | Ward et al. | Jan 2009 | A1 |
20090012704 | Franco et al. | Jan 2009 | A1 |
20090037938 | Frank | Feb 2009 | A1 |
20090062970 | Forbes, Jr. et al. | Mar 2009 | A1 |
20090063122 | Nasle | Mar 2009 | A1 |
20090063228 | Forbes, Jr. et al. | Mar 2009 | A1 |
20090065596 | Seem et al. | Mar 2009 | A1 |
20090070436 | Dawes et al. | Mar 2009 | A1 |
20090076749 | Nasle | Mar 2009 | A1 |
20090082888 | Johansen | Mar 2009 | A1 |
20090083167 | Subbloie | Mar 2009 | A1 |
20090093688 | Mathur | Apr 2009 | A1 |
20090098857 | De Atley | Apr 2009 | A1 |
20090098880 | Lindquist | Apr 2009 | A1 |
20090100492 | Hicks, III et al. | Apr 2009 | A1 |
20090103535 | McCoy et al. | Apr 2009 | A1 |
20090112522 | Rasmussen | Apr 2009 | A1 |
20090113037 | Pouchak | Apr 2009 | A1 |
20090129301 | Belimpasakis | May 2009 | A1 |
20090132070 | Ebrom et al. | May 2009 | A1 |
20090135836 | Veillette | May 2009 | A1 |
20090138099 | Veillette | May 2009 | A1 |
20090157529 | Ehlers et al. | Jun 2009 | A1 |
20090160626 | Jeon et al. | Jun 2009 | A1 |
20090164049 | Nibler et al. | Jun 2009 | A1 |
20090187499 | Mulder et al. | Jul 2009 | A1 |
20090193217 | Korecki et al. | Jul 2009 | A1 |
20090195349 | Frader-Thompson et al. | Aug 2009 | A1 |
20090204837 | Raval et al. | Aug 2009 | A1 |
20090240381 | Lane | Sep 2009 | A1 |
20090248702 | Schwartz et al. | Oct 2009 | A1 |
20090267787 | Pryor et al. | Oct 2009 | A1 |
20090270138 | Raveendran | Oct 2009 | A1 |
20090302994 | Rhee et al. | Dec 2009 | A1 |
20090305644 | Rhee | Dec 2009 | A1 |
20090312968 | Phillips et al. | Dec 2009 | A1 |
20090316671 | Rolf et al. | Dec 2009 | A1 |
20100017126 | Holcman et al. | Jan 2010 | A1 |
20100034386 | Choong et al. | Feb 2010 | A1 |
20100035587 | Bennett | Feb 2010 | A1 |
20100035613 | Schroter | Feb 2010 | A1 |
20100063867 | Proctor, Jr. et al. | Mar 2010 | A1 |
20100066507 | Myllymaeki | Mar 2010 | A1 |
20100069035 | Johnson | Mar 2010 | A1 |
20100069087 | Chow et al. | Mar 2010 | A1 |
20100070100 | Finlinson et al. | Mar 2010 | A1 |
20100070101 | Benes et al. | Mar 2010 | A1 |
20100075656 | Howarter et al. | Mar 2010 | A1 |
20100081375 | Rosenblatt et al. | Apr 2010 | A1 |
20100081468 | Brothers | Apr 2010 | A1 |
20100082174 | Weaver | Apr 2010 | A1 |
20100082176 | Chang | Apr 2010 | A1 |
20100082431 | Ramer et al. | Apr 2010 | A1 |
20100087932 | McCoy et al. | Apr 2010 | A1 |
20100088261 | Montalvo | Apr 2010 | A1 |
20100094475 | Masters et al. | Apr 2010 | A1 |
20100094737 | Lambird | Apr 2010 | A1 |
20100099410 | Sweeney et al. | Apr 2010 | A1 |
20100100253 | Fausak et al. | Apr 2010 | A1 |
20100113061 | Holcman | May 2010 | A1 |
20100115314 | Sultenfuss | May 2010 | A1 |
20100121499 | Besore et al. | May 2010 | A1 |
20100123414 | Antonopoulos | May 2010 | A1 |
20100127854 | Helvick et al. | May 2010 | A1 |
20100127889 | Vogel et al. | May 2010 | A1 |
20100130178 | Bennett et al. | May 2010 | A1 |
20100130213 | Vendrow et al. | May 2010 | A1 |
20100138764 | Hatambeiki et al. | Jun 2010 | A1 |
20100141437 | Karam et al. | Jun 2010 | A1 |
20100145534 | Forbes, Jr. et al. | Jun 2010 | A1 |
20100152997 | De Silva et al. | Jun 2010 | A1 |
20100156665 | Krzyzanowski et al. | Jun 2010 | A1 |
20100159936 | Brisbois et al. | Jun 2010 | A1 |
20100161148 | Forbes, Jr. et al. | Jun 2010 | A1 |
20100161149 | Nguyen et al. | Jun 2010 | A1 |
20100164713 | Wedig et al. | Jul 2010 | A1 |
20100165861 | Rrdland et al. | Jul 2010 | A1 |
20100169030 | Parlos et al. | Jul 2010 | A1 |
20100174643 | Schaefer et al. | Jul 2010 | A1 |
20100179670 | Forbes, Jr. et al. | Jul 2010 | A1 |
20100179672 | Beckmann et al. | Jul 2010 | A1 |
20100179708 | Watson et al. | Jul 2010 | A1 |
20100187219 | Besore et al. | Jul 2010 | A1 |
20100188239 | Rockwell | Jul 2010 | A1 |
20100188279 | Shamilian et al. | Jul 2010 | A1 |
20100191352 | Quail | Jul 2010 | A1 |
20100193592 | Simon et al. | Aug 2010 | A1 |
20100198713 | Forbes, Jr. et al. | Aug 2010 | A1 |
20100207728 | Roscoe et al. | Aug 2010 | A1 |
20100217450 | Beal et al. | Aug 2010 | A1 |
20100217451 | Kouda et al. | Aug 2010 | A1 |
20100217452 | McCord et al. | Aug 2010 | A1 |
20100217549 | Galvin et al. | Aug 2010 | A1 |
20100217550 | Crabtree et al. | Aug 2010 | A1 |
20100217642 | Crabtree et al. | Aug 2010 | A1 |
20100217651 | Crabtree et al. | Aug 2010 | A1 |
20100217837 | Ansari et al. | Aug 2010 | A1 |
20100218108 | Crabtree et al. | Aug 2010 | A1 |
20100222935 | Forbes, Jr. et al. | Sep 2010 | A1 |
20100228854 | Morrison et al. | Sep 2010 | A1 |
20100235008 | Forbes, Jr. et al. | Sep 2010 | A1 |
20100241275 | Crawford et al. | Sep 2010 | A1 |
20100249955 | Sitton | Sep 2010 | A1 |
20100250590 | Galvin | Sep 2010 | A1 |
20100256823 | Cherukuri et al. | Oct 2010 | A1 |
20100257539 | Narayanan et al. | Oct 2010 | A1 |
20100261465 | Rhoads et al. | Oct 2010 | A1 |
20100262298 | Johnson et al. | Oct 2010 | A1 |
20100262299 | Cheung et al. | Oct 2010 | A1 |
20100262336 | Rivas et al. | Oct 2010 | A1 |
20100272192 | Varadarajan et al. | Oct 2010 | A1 |
20100289643 | Trundle et al. | Nov 2010 | A1 |
20100299265 | Walters et al. | Nov 2010 | A1 |
20100299517 | Jukic et al. | Nov 2010 | A1 |
20100305773 | Cohen | Dec 2010 | A1 |
20100315235 | Adegoke et al. | Dec 2010 | A1 |
20100315438 | Horodezky et al. | Dec 2010 | A1 |
20100317332 | Bathiche et al. | Dec 2010 | A1 |
20100317371 | Westerinen et al. | Dec 2010 | A1 |
20100318198 | Smith et al. | Dec 2010 | A1 |
20100324956 | Lopez et al. | Dec 2010 | A1 |
20100324962 | Nesler et al. | Dec 2010 | A1 |
20100332373 | Crabtree et al. | Dec 2010 | A1 |
20110004350 | Cheifetz et al. | Jan 2011 | A1 |
20110004355 | Wang et al. | Jan 2011 | A1 |
20110004513 | Hoffberg | Jan 2011 | A1 |
20110015797 | Gilstrap | Jan 2011 | A1 |
20110015802 | Imes | Jan 2011 | A1 |
20110016023 | Zakas | Jan 2011 | A1 |
20110022239 | Forbes, Jr. et al. | Jan 2011 | A1 |
20110022242 | Bukhin et al. | Jan 2011 | A1 |
20110029655 | Forbes, Jr. et al. | Feb 2011 | A1 |
20110039518 | Maria | Feb 2011 | A1 |
20110040666 | Crabtree et al. | Feb 2011 | A1 |
20110046792 | Imes | Feb 2011 | A1 |
20110046798 | Imes et al. | Feb 2011 | A1 |
20110046799 | Imes et al. | Feb 2011 | A1 |
20110046800 | Imes et al. | Feb 2011 | A1 |
20110046801 | Imes et al. | Feb 2011 | A1 |
20110047482 | Arthurs et al. | Feb 2011 | A1 |
20110051823 | Imes et al. | Mar 2011 | A1 |
20110054699 | Imes et al. | Mar 2011 | A1 |
20110054710 | Imes et al. | Mar 2011 | A1 |
20110061014 | Frader-Thompson et al. | Mar 2011 | A1 |
20110063126 | Kennedy et al. | Mar 2011 | A1 |
20110063999 | Erdmann et al. | Mar 2011 | A1 |
20110069719 | Fries, IV et al. | Mar 2011 | A1 |
20110077789 | Sun | Mar 2011 | A1 |
20110098869 | Seo et al. | Apr 2011 | A1 |
20110106326 | Anunobi et al. | May 2011 | A1 |
20110106327 | Zhou et al. | May 2011 | A1 |
20110106681 | Cockerell et al. | May 2011 | A1 |
20110113090 | Peeri | May 2011 | A1 |
20110115875 | Sadwick et al. | May 2011 | A1 |
20110117878 | Barash et al. | May 2011 | A1 |
20110117927 | Doyle | May 2011 | A1 |
20110126035 | Kaneko | May 2011 | A1 |
20110138024 | Chen et al. | Jun 2011 | A1 |
20110148626 | Acevedo | Jun 2011 | A1 |
20110153525 | Benco et al. | Jun 2011 | A1 |
20110160881 | Grey | Jun 2011 | A1 |
20110172837 | Forbes, Jr. | Jul 2011 | A1 |
20110173542 | Imes et al. | Jul 2011 | A1 |
20110202185 | Imes et al. | Aug 2011 | A1 |
20110202195 | Finch et al. | Aug 2011 | A1 |
20110202293 | Kobraei et al. | Aug 2011 | A1 |
20110211584 | Mahmoud | Sep 2011 | A1 |
20110214060 | Imes et al. | Sep 2011 | A1 |
20110224838 | Imes et al. | Sep 2011 | A1 |
20110227704 | Padmanabhan et al. | Sep 2011 | A1 |
20110231020 | Ramachandran et al. | Sep 2011 | A1 |
20110246606 | Barbeau et al. | Oct 2011 | A1 |
20110246898 | Imes et al. | Oct 2011 | A1 |
20110251725 | Chan | Oct 2011 | A1 |
20110257809 | Forbes, Jr. et al. | Oct 2011 | A1 |
20110258022 | Forbes, Jr. et al. | Oct 2011 | A1 |
20110264290 | Drew | Oct 2011 | A1 |
20110264296 | Drake et al. | Oct 2011 | A1 |
20110282497 | Josephson et al. | Nov 2011 | A1 |
20110295393 | Lindahl | Dec 2011 | A1 |
20110296169 | Palmer | Dec 2011 | A1 |
20110302431 | Diab et al. | Dec 2011 | A1 |
20110307101 | Imes et al. | Dec 2011 | A1 |
20110316664 | Olcott et al. | Dec 2011 | A1 |
20120022709 | Taylor | Jan 2012 | A1 |
20120061480 | Deligiannis et al. | Mar 2012 | A1 |
20120077493 | Robbins | Mar 2012 | A1 |
20120126020 | Filson et al. | May 2012 | A1 |
20120169249 | Loveland et al. | Jul 2012 | A1 |
20120179547 | Besore et al. | Jul 2012 | A1 |
20120189140 | Hughes et al. | Jul 2012 | A1 |
20120312874 | Jonsson | Dec 2012 | A1 |
20130087629 | Stefanski et al. | Apr 2013 | A1 |
20130099010 | Filson et al. | Apr 2013 | A1 |
20140220883 | Emigh | Aug 2014 | A1 |
20140273822 | Gutierrez | Sep 2014 | A1 |
Number | Date | Country |
---|---|---|
1814260 | Aug 2007 | EP |
H0879840 | Mar 1996 | JP |
2006092035 | Apr 2006 | JP |
2002027639 | Apr 2002 | WO |
2007109557 | Sep 2007 | WO |
2008134460 | Nov 2008 | WO |
2009034720 | Mar 2009 | WO |
2009036764 | Mar 2009 | WO |
2009067251 | May 2009 | WO |
2009097400 | Aug 2009 | WO |
Entry |
---|
International Search Report, dated Apr. 30, 2015, 4 pages. |
Slavin, Alison Jane and Trundle, Stephen Scott, Remote Thermostat Control/Energy Monitoring, U.S. Appl. No. 61/179,224, filed May 18, 2009; 14 pages. |
Gupta, Manu, A Persuasive GPS-Controlled Thermostat System, Royal Institute of Technology, Stockholm, Sweden, Jun. 2006; Pune Institute of Computer Technology, University of Pune, India, Jun. 2003 and Massachusetts Institute of Technology, Sep. 2008; 89 pages. |
Gupta, Manu, Intille, Stephen S. and Larson, Kent, Adding GPS-Control to Traditional Thermostats: An Exploration of Potential Energy Savings and Design Challenges. House_n. Massachusetts Institute of Technology, Cambridge, MA 02142 USA. May 11-14, 2009, Springer-Verlag Berlin, Heideberg. |
“A step-by-step guide to installing the 1st generation Nest Learning Thermostat,” Article #1161, 2013 Nest Labs. pp. 1-6. http://http://support.nest.com/article/A-step-by-step-guide-to-installing-the-1st-generation-Nest-Learning-Thermostat, last accessed Feb. 1, 2013. |
Klym et al., The Evolution of RFID Networks: The Potential for Disruptive Innovation, Mar. 2006, MIT Communication Futures Program, pp. 1-20. |
Pering et al., Spontaneous Marriages of Mobile Devices and Interactive Space, Communication of the ACM, Sep. 2005, pp. 53-59. |
Jaring et al., Improving Mobile Solution Workflows and Usability Using Near Field Communication Technology, 2007, Springer-Verlag Berlin Heidelberg, pp. 358-373. |
“Wi-Fi”, Wikipedia, printed Jul. 8, 2013. |
Request Response, Wikipedia, printed Jul. 25, 2013. |
Inncom International, Inc. “Installation User Manual”, Revision 3.1, Sep. 12, 2006, pp. 1-36. |
Peffer, T., et al. “A Tale of Two Houses: The Human Dimension of Demand Response Enabling Technology from a Case Study of an Adaptive Wireless Thermostat,” ACEEE Summer Study on Energy Efficiency in Buildings, 2008. |
BAYweb Thermostat Owner's Manual, Bay Controls, LLC, published Nov. 11, 2009. |
Stigge, B. “Informed Home Energy Behavior: Developing a tool for homeowners to monitor, plan and learn about energy conservation,” Massachusetts Insitute of Technology, 2001. |
Mozer, M., et al. The Neurothermostat: Predictive Optimal Control of Residential Heating Systems. “Advances in Neural Information Processing Systems 9.” MIT Press, 1997. |
e4 Smart Digital Thermostat—E529, Inncom by Honeywell, published Aug. 2012. |
Seligman, C., et al. Behavior Approaches to Residential Energy Conservation. “Saving Energy in the Home.” Ballinger Publishing Co., 1978. |
Singapore Written Opinion dated Jun. 9, 2017 in corresponding Singapore Patent Application No. 11201605494Q. |
Singapore Intellectual Property Office, Written Opinion issued in Singapore Patent Application No. 11201605494Q dated Apr. 24, 2018 (6 pages). |
Mexican Patent Office Action issued in Mexican Patent Application No. MX/a/2016/008828 dated Sep. 15, 2018 (4 Total pages). |
Number | Date | Country | |
---|---|---|---|
20150195099 A1 | Jul 2015 | US |
Number | Date | Country | |
---|---|---|---|
61924048 | Jan 2014 | US |