UNITED STATES PATENT AND TRADEMARK OFFICE
`_____________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`_____________
`
`HONEYWELL INTERNATIONAL, INC.
`
`Petitioner
`
`v.
`
`ALLURE ENERGY, INC.
`
`Patent Owner
`_____________
`
`Case No. IPR2016-___
`Patent No. 8,509,954
`
`PETITIONER’S EXHIBIT NO. 1007
`
`

`
`Attorney Docket No.: 22888-0013P01
`
`REMOTE THERMOSTAT CONTROL/ENERGY
`MONITORING
`Techniques are described for providing remote thermostat control/energy monitoring. In
`
`some implementations, a native mobile device application enables use of a mobile device to
`
`monitor and control thermostat, lighting, and other energy-consuming appliances in a home,
`
`business, vacation or other property from anywhere. The native mobile device application
`
`provides alerts related to energy consumption and events that may impact user decision on
`
`energy consumption. The native mobile device application also tracks the mobile device's
`
`physical location and uses location tracking to automatically set thermostat, lights, and
`
`appliances accordingly.
`
`FIG. 1 illustrates an example of an electronic system 100 configured to provide remote
`
`thermostat control/energy monitoring using one or more mobile devices. The electronic system
`
`100 includes a network 105, a monitoring system control unit 110, one or more mobile devices
`
`140, 150, and a monitoring application server 160. In some examples, the network 105
`
`facilitates communications between the monitoring system control unit 110, the one or more
`
`mobile devices 140, 150, and the monitoring application server 160.
`
`The network 105 is configured to enable exchange of electronic communications between
`
`devices connected to the network 105. For example, the network 105 may be configured to
`
`enable exchange of electronic communications between the monitoring system control unit 110,
`
`the one or more mobile devices 140, 150, the monitoring application server 160, and the central
`
`alarm station server 170. The network 105 may include, for example, one or more of the
`
`Internet, Wide Area Networks (WANs), Local Area Networks (LANs), analog or digital wired
`
`and wireless telephone networks (e.g., a public switched telephone network (PSTN), Integrated
`
`Services Digital Network (ISDN), a cellular network, and Digital Subscriber Line (DSL)), radio,
`
`television, cable, satellite, or any other delivery or tunneling mechanism for carrying data.
`
`Network 105 may include multiple networks or subnetworks, each of which may include, for
`
`example, a wired or wireless data pathway. The network 105 may include a circuit-switched
`
`network, a packet-switched data network, or any other network able to carry electronic
`
`communications (e.g., data or voice communications). For example, the network 105 may
`
`include networks based on the Internet protocol (IP), asynchronous transfer mode (ATM), the
`
`PSTN, packet-switched networks based on IP, X.25, or Frame Relay, or other comparable
`
`1
`
`Honeywell Exhibit 1007, Page 1
`
`

`
`Attorney Docket No.: 22888-0013P01
`
`technologies and may support voice using, for example, VoIP, or other comparable protocols
`
`used for voice communications. The network 105 may include one or more networks that
`
`include wireless data channels and wireless voice channels. The network 105 may be a wireless
`
`network, a broadband network, or a combination of networks including a wireless network and a
`
`broadband network.
`
`The monitoring system control unit 110 includes a controller 112 and a network module
`
`114. The controller 112 is configured to control a monitoring system (e.g., a home alarm or
`
`security system) that includes the monitoring system control unit 110. In some examples, the
`
`controller 112 may include a processor or other control circuitry configured to execute
`
`instructions of a program that controls operation of an alarm system. In these examples, the
`
`controller 112 may be configured to receive input from sensors, detectors, or other devices
`
`included in the alarm system and control operations of devices included in the alarm system or
`
`other household devices (e.g., a thermostat, an appliance, lights, etc.). For example, the
`
`controller 112 may be configured to control operation of the network module 114 included in the
`
`monitoring system control unit 110.
`
`The network module 114 is a communication device configured to exchange
`
`communications over the network 105. The network module 114 may be a wireless
`
`communication module configured to exchange wireless communications over the network 105.
`
`For example, the network module 114 may be a wireless communication device configured to
`
`exchange communications over a wireless data channel and a wireless voice channel. In this
`
`example, the network module 114 may transmit alarm data over a wireless data channel and
`
`establish a two-way voice communication session over a wireless voice channel. The wireless
`
`communication device may include one or more of a GSM module, a radio modem, cellular
`
`transmission module, or any type of module configured to exchange communications in one of
`
`the following formats: GSM or GPRS, CDMA, EDGE or EGPRS, EV-DO or EVDO, UMTS, or
`
`P.
`
`The network module 114 also may be a wired communication module configured to
`
`exchange communications over the network 105 using a wired connection. For instance, the
`
`network module 114 may be a modem, a network interface card, or another type of network
`
`interface device. The network module 114 may be an Ethernet network card configured to
`
`enable the monitoring system control unit 110 to communicate over a local area network and/or
`
`2
`
`Honeywell Exhibit 1007, Page 2
`
`

`
`Attorney Docket No.: 22888-0013P01
`
`the Internet. The network module 114 also may be a voiceband modem configured to enable the
`
`alarm panel to communicate over the telephone lines of Plain Old Telephone Systems (POTS).
`
`The monitoring system that includes the monitoring system control unit 110 includes one
`
`or more sensors or detectors. For example, the monitoring system may include multiple sensors.
`
`The sensors may include a contact sensor, a motion sensor, a glass break sensor, or any other
`
`type of sensor included in an alarm system or security system. The sensors also may include an
`
`environmental sensor, such as a temperature sensor, a water sensor, a rain sensor, a wind sensor,
`
`a light sensor, a smoke detector, a carbon monoxide detector, an air quality sensor, etc. The
`
`sensors further may include a health monitoring sensor, such as a prescription bottle sensor that
`
`monitors taking of prescriptions, a blood pressure sensor, a blood sugar sensor, a bed mat
`
`configured to sense presence of liquid (e.g., bodily fluids) on the bed mat, etc. In some
`
`examples, the sensors may include a radio-frequency identification (RFID) sensor that identifies
`
`a particular article that includes a pre-assigned RFID tag. In addition, the sensors may include a
`
`video/photographic camera or other type of optical sensing device configured to capture images
`
`and may include an energy consumption sensor for appliances and devices in a property
`
`monitored by the monitoring system.
`
`The monitoring system control unit 110 communicates with modules 120, 122, and 130
`
`to perform thermostat control and energy monitoring. The module 120 is connected to one or
`
`more appliances, is configured to monitor energy consumption of the one or more appliances,
`
`and is configured to control operation of the one or more appliances. The module 120 may
`
`directly measure energy consumption of the one or more appliances or may estimate energy
`
`consumption of the one or more appliances based on detected usage of the one or more
`
`appliances. The module 120 may communicate energy monitoring information to the monitoring
`
`system control unit 110 and may control the one or more appliances based on commands
`
`received from the monitoring system control unit 110.
`
`The module 122 is connected to one or more lighting systems, is configured to monitor
`
`energy consumption of the one or more lighting systems, and is configured to control operation
`
`of the one or more lighting systems. The module 122 may directly measure energy consumption
`
`of the one or more lighting systems or may estimate energy consumption of the one or more
`
`lighting systems based on detected usage of the one or more lighting systems. The module 122
`
`may communicate energy monitoring information to the monitoring system control unit 110 and
`
`3
`
`Honeywell Exhibit 1007, Page 3
`
`

`
`Attorney Docket No.: 22888-0013P01
`
`may control the one or more lighting systems based on commands received from the monitoring
`
`system control unit 110.
`
`The module 130 is connected to a thermostat, is configured to monitor temperature and/or
`
`energy consumption of a temperature regulation system associated with the thermostat, and is
`
`configured to control operation of the thermostat. The module 130 may directly measure energy
`
`consumption of the temperature regulation system associated with the thermostat or may
`
`estimate energy consumption of the temperature regulation system associated with the thermostat
`
`based on detected usage of the temperature regulation system associated with the thermostat.
`
`The module 130 may communicate temperature and energy monitoring information to the
`
`monitoring system control unit 110 and may control the thermostat based on commands received
`
`from the monitoring system control unit 110.
`
`The modules 120, 122, and 130 communicate with the controller 112 over
`
`communication links 124, 126, and 128. The communication links 124, 126, and 128 may be a
`
`wired or wireless data pathway configured to transmit signals from the modules 120, 122, and
`
`130 to the controller 112. The modules 120, 122, and 130 may continuously transmit sensed
`
`values to the controller 112, periodically transmit sensed values to the controller 112, or transmit
`
`sensed values to the controller 112 in response to a change in a sensed value.
`
`The monitoring application server 160 is an electronic device configured to provide
`
`monitoring services by exchanging electronic communications with the monitoring system
`
`control unit 110 and the one or more mobile devices 140, 150 over the network 105. For
`
`example, the monitoring application server 160 may be configured to monitor events generated
`
`by the monitoring system control unit 110. In this example, the monitoring application server
`
`160 may exchange electronic communications with the network module 114 included in the
`
`monitoring system control unit 110 to receive information regarding alarm events detected by the
`
`monitoring system control unit 110. The monitoring application server 160 also may receive
`
`information regarding events from the one or more mobile devices 140, 150.
`
`The monitoring application server 160 may store sensor (e.g., thermostat and energy
`
`consumption) data received from the monitoring system and perform analysis of sensor data
`
`received from the monitoring system. Based on the analysis, the monitoring application server
`
`160 may communicate with and control aspects of the monitoring system control unit 110 or the
`
`one or more mobile devices 140, 150.
`
`4
`
`Honeywell Exhibit 1007, Page 4
`
`

`
`Attorney Docket No.: 22888-0013P01
`
`The one or more mobile devices 140, 150 are devices that host and display user interfaces
`
`and that host one or more native applications (e.g., the native monitoring application 142, 152).
`
`The one or more mobile devices 140, 150 may be cellular phones or non-cellular locally
`
`networked devices with displays. The one or more mobile devices 140, 150 may include a cell
`
`phone, a smart phone, a tablet PC, a personal digital assistant ("PDA"), or any other portable
`
`device configured to communicate over a network and display information. For example,
`
`implementations may also include Blackberry-type devices (e.g., as provided by Research in
`
`Motion), electronic organizers, iPhone-type devices (e.g., as provided by Apple), iPod devices
`
`(e.g., as provided by Apple) or other portable music players, other communication devices, and
`
`handheld or portable electronic devices for gaming, communications, and/or data organization.
`
`The one or more mobile devices 140, 150 may be the same or may include mobile devices of
`
`different types. The one or more mobile devices 140, 150 may perform functions unrelated to
`
`the monitoring system, such as placing personal telephone calls, playing music, playing video,
`
`displaying pictures, browsing the Internet, maintaining an electronic calendar, etc.
`
`The one or more mobile devices 140, 150 communicate with and receive monitoring
`
`system data from the monitoring system control unit 110 using the communication link 138. For
`
`instance, the one or more mobile devices 140, 150 may communicate with the monitoring system
`
`control unit 110 using various local wireless protocols such as wifi, Bluetooth, zwave, zigbee,
`
`HomePlug (ethernet over powerline), or wired protocols such as Ethernet and USB, to connect
`
`the one or more mobile devices 140, 150 to local security and automation equipment. The one or
`
`more mobile devices 140, 150 may connect locally to the monitoring system and its sensors and
`
`other devices. The local connection may improve the speed of status and control
`
`communications because communicating through the network 105 with a remote server (e.g., the
`
`monitoring application server 160) may be significantly slower.
`
`Although the one or more mobile devices 140, 150 are shown as communicating with the
`
`monitoring system control unit 110, the one or more mobile devices 140, 150 may communicate
`
`directly with the sensors and other devices controlled by the monitoring system control unit 110.
`
`In some implementations, the one or more mobile devices 140, 150 replace the monitoring
`
`system control unit 110 and perform the functions of the monitoring system control unit 110 for
`
`local monitoring and long range/offsite communication.
`
`5
`
`Honeywell Exhibit 1007, Page 5
`
`

`
`Attorney Docket No.: 22888-00131)01
`
`In other implementations, the one or more mobile devices 140, 150 receive monitoring
`
`system data captured by the monitoring system control unit 110 through the network 105. The
`
`one or more mobile devices 140, 150 may receive the data from the monitoring system control
`
`unit 110 through the network 105 or the monitoring application server 160 may relay data
`
`received from the monitoring system control unit 110 to the one or more mobile devices 140,
`
`150 through the network 105. In this regard, the monitoring application server 160 may facilitate
`
`communication between the one or more mobile devices 140, 150 and the monitoring system.
`
`In some implementations, the one or more mobile devices 140, 150 may be configured to
`
`switch whether the one or more mobile devices 140, 150 communicate with the monitoring
`
`system control unit 110 directly (e.g., through link 138) or through the monitoring application
`
`server 160 (e.g., through network 105) based on a location of the one or more mobile devices
`
`140, 150. For instance, when the one or more mobile devices 140, 150 are located close to the
`
`monitoring system control unit 110 and in range to communicate directly with the monitoring
`
`system control unit 110, the one or more mobile devices 140, 150 use direct communication.
`
`When the one or more mobile devices 140, 150 are located far from the monitoring system
`
`control unit 110 and not in range to communicate directly with the monitoring system control
`
`unit 110, the one or more mobile devices 140, 150 use communication through the monitoring
`
`application server 160.
`
`Although the one or more mobile devices 140, 150 are shown as being connected to the
`
`network 105, in some implementations, the one or more mobile devices 140, 150 are not
`
`connected to the network 105. In these implementations, the one or more mobile devices 140,
`
`150 communicate directly with one or more of the monitoring system components and no
`
`network (e.g., Internet) connection or reliance on remote servers is needed.
`
`In some implementations, the one or more mobile devices 140, 150 are used in
`
`conjunction with only local sensors and/or local devices in a house. In these implementations,
`
`the system 100 only includes the one or more mobile devices 140, 150 and the modules 120, 122,
`
`and 130. The one or more mobile devices 140, 150 receive data directly from the modules 120,
`
`122, and 130 and sends data directly to the modules 120, 122, and 130. The one or more mobile
`
`devices 140, 150 provide the appropriate interfaces/processing to provide monitoring
`
`information, generate alerts, modify settings, control the thermostat, lighting, and appliance
`
`devices, etc.
`
`6
`
`Honeywell Exhibit 1007, Page 6
`
`

`
`Attorney Docket No.: 22888-0013P01
`
`In other implementations, the system 100 further includes network 105 and the modules
`
`120, 122, and 130 are configured to communicate sensor data to the one or more mobile devices
`
`140, 150 over network 105 (e.g., the Internet, cellular network, etc.). In yet another
`
`implementation, the modules 120, 122, and 130 (or a component, such as a bridge/router) are
`
`intelligent enough to change the communication pathway from a direct local pathway when the
`
`one or more mobile devices 140, 150 are in close physical proximity to the modules 120, 122,
`
`and 130 to a pathway over network 105 when the one or more mobile devices 140, 150 are
`
`farther from the modules 120, 122, and 130. In some examples, the system leverages GPS
`
`information from the one or more mobile devices 140, 150 to determine whether the one or more
`
`mobile devices 140, 150 are close enough to the modules 120, 122, and 130 to use the direct
`
`local pathway or whether the one or more mobile devices 140, 150 are far enough from the
`
`modules 120, 122, and 130 that the pathway over network 105 is required. In other examples,
`
`the system leverages status communications (e.g., pinging) between the one or more mobile
`
`devices 140, 150 and the modules 120, 122, and 130 to determine whether communication using
`
`the direct local pathway is possible. If communication using the direct local pathway is possible,
`
`the one or more mobile devices 140, 150 communicate with the modules 120, 122, and 130 using
`
`the direct local pathway. If communication using the direct local pathway is not possible, the
`
`one or more mobile devices 140, 150 communicate with the modules 120, 122, and 130 using the
`
`pathway over network 105.
`
`The one or more mobile devices 140, 150 each include a native monitoring application
`
`142, 152, respectively. The native monitoring application 142, 152 refers to a software/firmware
`
`program running on the corresponding mobile device that enables the user interface and features
`
`describe below. The one or more mobile devices 140, 150 may load or install the native
`
`monitoring application 142, 152 based on data received over a network or data received from
`
`local media. The native monitoring application 142, 152 runs on mobile devices platforms, such
`
`as iPhone, iPod touch, Blackberry, Google Android, Windows Mobile, etc.
`
`The native monitoring application 142, 152 monitors and controls thermostat, lighting,
`
`and other energy-consuming appliances in a home, business, vacation or other property from
`
`anywhere. The native monitoring application 142, 152 enables users to easily monitor and
`
`control how much energy they are consuming. The native monitoring application 142, 152 also
`
`enables users to set up a comfortable environment with respect to temperature, lighting, etc.
`
`7
`
`Honeywell Exhibit 1007, Page 7
`
`

`
`Attorney Docket No.: 22888-0013P01
`
`In some implementations, the native monitoring application 142, 152 enables the mobile
`
`device to connect to thermostat(s) remotely and provide a user real-time, remote control of
`
`temperature in a building. For example, a user may take the user's mobile device on a business
`trip out of town. While the user is out of town, the weather at the user's home becomes
`
`unexpectedly hot. The user may use native monitoring application 142, 152 to control the
`
`thermostat(s) in the user's home to turn the air conditioning system on or adjust a temperature of
`
`the home to a desired level. In this example, when the temperature becomes hot and the user has
`
`a pet that remains in the home, the user may lower the temperature of the thermostat to cool the
`
`home to increase the comfort of the pet. Alternatively, when the temperature becomes hOt and
`
`no one remains in the home, the user may increase the temperature of the thermostat to save on
`
`energy costs of cooling the home unnecessarily.
`
`In some examples, the native monitoring application 142, 152 tracks the mobile device's
`
`physical location using GPS or other location protocols built into device and uses location
`
`tracking to control thermostat, lighting, and other energy-consuming appliances. For example,
`
`the native monitoring application 142, 152 may check location of the mobile device periodically
`
`and automatically detect when user is going toward or away from a home and sets thermostat,
`
`lights, appliances accordingly. For instance, when the user is detected as moving away from the
`
`home and lights remain on in the property, the native monitoring application 142, 152 may turn
`
`off the lights. When the user is detected is moving toward the home, the native monitoring
`
`application 142, 152 may turn on lights in the home, adjust the thermostat to a comfortable
`
`setting, and turn on useful appliances when the user is less than a threshold distance from the
`
`home.
`
`The native monitoring application 142, 152 also may alert the user during time frames
`
`when their energy utility company is charging more or less for energy, so user can take action
`
`through the native monitoring application 142, 152. For instance, the native monitoring
`
`application 142, 152 may receive information related to utility company rates from the
`
`monitoring application server 160, from another source on the Internet, or from a user entering
`
`information related to utility company rates (e.g., a user entering monthly billing statements).
`
`The native monitoring application 142, 152 may store the rate information for use in alerting the
`
`user. The native monitoring application 142, 152 may periodically update the rate information.
`
`In using rate information to alert the user, the native monitoring application 142, 152 may
`
`8
`
`Honeywell Exhibit 1007, Page 8
`
`

`
`Attorney Docket No.: 22888-0013P01
`
`provide an alert to the user when lights remain on in the home and the rate information indicates
`
`that the utility company is charging relatively high rates, but determine not to provide an alert to
`
`the user when lights remain on in the home and the rate information indicates that the utility
`
`company is charging relatively low rates. In another example, the native monitoring application
`
`142, 152 may alert the user when the native monitoring application 142, 152 detects the user
`
`starting an appliance (e.g., a dishwasher) at a time when the rate is relatively high. In this
`
`example, if the user determines not to use the appliance at the time, the native monitoring
`
`application 142, 152 may offer to provide another alert to the user when the utility company rate
`
`drops or offer to automatically start the appliance when the utility company rate drops.
`
`In further examples, native monitoring application 142, 152 may automatically change
`
`thermostat temperature on user behalf in response to utility pricing based on user settings. For
`
`instance, the native monitoring application 142, 152 may define rules for thermostat control
`
`based on user input. The rules may account utility pricing and prior energy consumption. For
`
`example, the native monitoring application 142, 152 may define a rule to automatically increase
`
`a temperature of a thermostat two degrees when the utility company rate is relatively high and
`
`the air conditioner is being used. In this example, the native monitoring application 142, 152
`
`may automatically decrease the temperature of the thermostat two degrees when the utility
`
`company rate falls back to a relatively low rate and the air conditioner is still being used.
`
`The native monitoring application 142, 152 further may account for prior monthly energy
`
`consumption in automatically setting temperatures. For instance, when monthly energy
`
`consumption has been relatively high, the native monitoring application 142, 152 may
`
`automatically increase a temperature of a thermostat two degrees when the utility company rate
`
`is relatively high and the air conditioner is being used. However, when monthly energy
`
`consumption has been relatively low, the native monitoring application 142, 152 may not
`
`automatically increase the temperature of the thermostat two degrees when the utility company
`
`rate is relatively high and the air conditioner is being used. Accounting for prior monthly energy
`
`consumption may assist a user in getting more consistent energy consumption bills and,
`
`therefore, may assist the user in budgeting monthly finances more accurately.
`
`In some implementations, native monitoring application 142, 152 uses a real-time
`
`weather feed (e.g. from national weather service) to help guide intelligent, automated decision
`
`making on thermostat temperature. The native monitoring application 142, 152 may receive
`
`9
`
`Honeywell Exhibit 1007, Page 9
`
`

`
`Attorney Docket No.: 22888-0013P01
`
`weather information from the monitoring application server 160 or from another source on the
`
`Internet. The native monitoring application 142, 152 may periodically update the weather
`
`information or receive weather related alerts. The native monitoring application 142, 152 may
`
`account for the weather information in automatically controlling thermostat, lighting, and other
`
`energy-consuming appliances and providing alerts to the user. For instance, in the example
`
`discussed above in which the weather at a user's home becomes unexpectedly hot when the user
`
`is out of town, the native monitoring application 142, 152 may detect that the weather has
`
`become unexpectedly hot based on the weather feed information and alert the user.
`
`The native monitoring application 142, 152 may include detailed and summary
`
`indoor/outdoor temperature and humidity reports to show users how they are setting temperature
`
`at various times of day. The reports could cross reference to money paid for energy at given
`
`time of day. The report data may be based on user input or automatically received or accessed
`
`from a utility company. For instance, users may manually enter their energy bill amount into the
`
`native monitoring application 142, 152 each month to get pulled into reporting, or accept a feed
`
`from the utility company.
`
`The native monitoring application 142, 152 may monitor sunrise/sunset times and
`
`automatically turn specified lights on/off at dusk/dawn. For instance, the native monitoring
`
`application 142, 152 may receive information related to sunrise/sunset times from the monitoring
`
`application server 160 or from another source on the Internet and store the information for use in
`
`controlling lights.
`
`The native monitoring application 142, 152 may provide user-defined schedules for
`
`controlling wake-up and turn-down schemes. For instance, at wake-up time, the native
`
`monitoring application 142, 152 may turn on a bedroom light, change a thermostat setting to a
`
`day setting, and turn on a coffee maker. At turn-down time, the native monitoring application
`
`142, 152 may turn off a bedroom light, change a thermostat setting to a night setting, and arm an
`
`alarm system to a "Stay" mode.
`
`The native monitoring application 142, 152 may operate in Home Mode, Away-Work
`
`Mode, Away-Vacation Mode and other user defined modes that control temperature, light,
`
`appliance behavior. The native monitoring application 142, 152 may define the modes and
`
`settings corresponding to the modes based on user input. The native monitoring application 142,
`
`152 also may switch between the modes based on user input or may automatically switch
`
`10
`
`Honeywell Exhibit 1007, Page 10
`
`

`
`Attorney Docket No.: 22888-0013P01
`
`between modes based on factors, such as location of the mobile device and status of an alarm
`
`system at one or more locations.
`
`The native monitoring application 142, 152 may work as a local remote control device
`
`for use when on or near the premises. Alternatively, the native monitoring application 142, 152
`
`may work as a long-range remote control that could work from anywhere in the world for long-
`
`range wireless protocols (e.g., GSM, CDMA, WiMax, etc.) via remote servers, such as the
`
`monitoring application server 160.
`
`The native monitoring application 142, 152 also may implement a permission system that
`
`provides a different level of control for different users. For instance, parent users may have full
`
`control of the monitoring system and a child user may have limited control (e.g., the child user
`
`may be able to control lighting systems, but may not be able to control appliances). The
`
`permission system may be implemented based on user-specific passcodes or particular mobile
`
`devices may be assigned to particular users.
`
`In implementations in which multiple mobile devices are included in the system 100, the
`
`native monitoring application 142, 152 may include rules that govern input from which of the
`
`multiple devices controls when conflicting input is received. For instance, when a parent user is
`
`attempting to perform a first action (e.g., raise temperature) and a child user is attempting to
`
`perform a second, different action that conflicts with the first action (e.g., lower temperature), the
`
`rules of the native monitoring application 142, 152 (or monitoring system in general) may
`
`perform only the first action because the parent user has higher priority than the child user.
`
`The described systems, methods, and techniques may be implemented in digital
`
`electronic circuitry, computer hardware, firmware, software, or in combinations of these
`
`elements. Apparatus implementing these techniques may include appropriate input and output
`
`devices, a computer processor, and a computer program product tangibly embodied in a
`
`machine-readable storage device for execution by a programmable processor. A process
`
`implementing these techniques may be performed by a programmable processor executing a
`
`program of instructions to perform desired functions by operating on input data and generating
`
`appropriate output. The techniques may be implemented in one or more computer programs that
`
`are executable on a programmable system including at least one programmable processor
`
`coupled to receive data and instructions from, and to transmit data and instructions to, a data
`
`storage system, at least one input device, and at least one output device. Each computer program
`
`11
`
`Honeywell Exhibit 1007, Page 11
`
`

`
`Attorney Docket No.: 22888-0013P01
`
`may be implemented in a high-level procedural or object-oriented programming language, or in
`
`assembly or machine language if desired; and in any case, the language may be a compiled or
`
`interpreted language. Suitable processors include, by way of example, both general and special
`
`purpose microprocessors. Generally, a processor will receive instructions and data from a read-
`
`only memory and/or a random access memory. Storage devices suitable for tangibly embodying
`
`computer program instructions and data include all forms of non-volatile memory, including by
`
`way of example semiconductor memory devices, such as Erasable Programmable Read-Only
`
`Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), and
`
`flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-
`
`optical disks; and Compact Disc Read-Only Memory (CD-ROM). Any of the foregoing may be
`
`supplemented by, or incorporated in, specially-designed ASICs (application-specific integrated
`
`circuits).
`
`It will be understood that various modifications may be made. For example, other useful
`
`implementations could be achieved if steps of the disclosed techniques were performed in a
`
`different order and/or if components in the disclosed systems were combined in a different
`
`manner and/or replaced or supplemented by other components. Accordingly, other
`
`implementations are within the scope of the disclosure.
`
`12
`
`Honeywell Exhibit 1007, Page 12
`
`

`
`REMOTE