Patent Grant
11334040
The present disclosure generally relates to automatically responding to the presence of a fire, and, more particularly, to systems and methods that leverage a plurality of smart appliances or devices to mitigate risks associated with the fire.
There are many emergency situations that may impact buildings and the people located within the buildings. In some such emergency situations, a building may be on fire and/or a fire may be present inside a building. Currently, many appliances and other goods are capable of communicating information about their operation via mesh networks as part of the “internet of things.” However, there is no way to aggregate and analyze all of this communicated data to detect the presence of the fire. Further, there is no way to analyze the data to determine the most appropriate response to mitigate the risks associated with the fire.
The present embodiments may, inter alia, detect the presence of a fire and determine a response that mitigates the risks associated with the presence of the fire. For instance, a system and method may facilitate communications with connected devices and items, and/or facilitate the evacuation of individuals located on a property (e.g., smart home) and/or alter a navigation state associated with a door. The present embodiments may monitor sensor data received from a plurality of devices populated on the premises of the property. Each of the plurality of devices may be configured to monitor various conditions of the property to determine the presence of a fire on the premises of the property. A controller may determine the location of the fire to determine which of the devices should perform an action that mitigates the risks associated with the presence of the fire. The controller may also determine a set of actions that may be performed by the plurality of devices that mitigates the risks. Additionally, the controller may transmit escape routes to individuals to ensure effective and efficient evacuation procedures while minimizing the risk of harm to the individuals.
In one aspect, a computer-implemented method of responding to a fire on a property may be provided. The property may be populated with a hardware controller in communication with a plurality of devices and each of the plurality of devices may be configured to monitor various conditions associated with the property. The method may include, with customer permission or affirmative consent, (1) receiving, by the hardware controller via a first communication network, a first set of sensor data from at least one of the plurality of devices, the first set of sensor data indicative of the fire being present on the property; (2) analyzing, by one or more processors, the first set of sensor data to determine a location of the fire on the property; (3) comparing, by the one or more processors, the location of the fire to a list of the plurality of devices, the list including for each device at least one of a location of the device and/or a set of functions that the device is capable of performing to mitigate risks associated with the fire; (4) based upon the comparison, determining, by the one or more processors, a set of actions to be performed by at least a portion of the plurality of devices; and/or (5) directing or controlling, by the one or more processors, the at least the portion of the plurality of devices to perform the set of actions to facilitate a set of individuals escaping the fire in a safe manner. The method may include additional, less, or alternate actions, including those discussed elsewhere herein.
In another aspect, a system for responding to a fire on a property may be provided. The property populated with a hardware controller in communication with a plurality of devices and each of the plurality of devices may be configured to monitor various conditions associated with the property. The system may include (i) a plurality of transceivers adapted to communicate data; (ii) a memory adapted to store non-transitory computer executable instructions; and/or (iii) one or more processors adapted to interface with the plurality of transceivers. The one or more processors may be configured to execute the non-transitory computer executable instructions to cause the system to, with customer permission, (1) receive, by the plurality of transceivers, a first set of sensor data from at least one of the plurality of devices, the first set of sensor data indicative of the fire being present on the property; (2) analyze, by the one or more processors, the first set of sensor data to determine a location of the fire on the property; (3) compare, by the one or more processors, the location of the fire to a list of the plurality of devices, the list including for each device at least one of a location of the device and/or a set of functions that the device is capable of performing to mitigate risks associated with the fire; (4) based upon the comparison, determine, by the one or more processors, a set of actions to be performed by at least a portion of the plurality of devices; and/or (5) direct or control, by the one or more processors, the at least the portion of the plurality of devices to perform the set of actions to facilitate a set of individuals escaping the fire in a safe manner. The system may include additional, less, or alternate actions, including those discussed elsewhere herein.
In another aspect, a non-transitory computer-readable storage medium storing processor-executable instructions may be provided. When executed, the instructions may cause one or more processors to (1) receive, via a first communication network, a first set of sensor data from at least one of the plurality of devices, the first set of sensor data indicative of the fire being present on the property; (2) analyze, by the one or more processors, the first set of sensor data to determine a location of the fire on the property; (3) compare, by the one or more processors, the location of the fire to a list of the plurality of devices, the list including for each device at least one of a location of the device and/or a set of functions that the device is capable of performing to mitigate risks associated with the fire; (4) based upon the comparison, determine, by the one or more processors, a set of actions to be performed by at least a portion of the plurality of devices; and/or (5) direct or control, by the one or more processors, the at least the portion of the plurality of devices to perform the set of actions to facilitate a set of individuals escaping the fire in a safe manner. The instructions may cause additional, less, or alternate actions, including those discussed elsewhere herein.
The figures described below depict various aspects of the system and methods disclosed herein. It should be understood that each figure depicts an embodiment of a particular aspect of the disclosed system and methods, and that each of the figures is intended to accord with a possible embodiment thereof. Further, wherever possible, the following description refers to the reference numerals included in the following figures, in which features depicted in multiple figures are designated with consistent reference numerals.
The present embodiments may relate to, inter alia, the mitigation, prevention, or other action to avoid risks caused by a fire on a property. The present embodiments may also relate to (a) detecting the presence of the fire; (b) determining a response; (c) directing the performance of the fore-mentioned response; (d) guiding an individual to avoid the fire while escaping; (e) managing insurance policies; (f) communicating with emergency services; and/or (g) other fire response-related activities.
A home may have a “smart” central controller (referred to as a “smart home controller” herein, or “smart building controller” for an office building) and be wirelessly interconnected, or even hard-wired, with various household related items and/or sensors. Despite being referred to as the “smart home controller,” the central controller may be associated with any type of property, such as offices, restaurants, farms, and/or other types of properties. The smart home controller may be in wireless or wired communication with various smart appliances (e.g., clothes washer, dryer, dish washer, refrigerator, etc.), smart heating devices (e.g., furnace, space heaters, etc.), smart cooling devices (e.g., air conditioning units, fans, ceiling fans, etc.), smart plumbing fixtures (e.g., toilets, showers, water heaters, piping, interior and yard sprinklers, etc.), smart cooking devices (e.g., stoves, ovens, grills, microwaves, etc.), smart wiring, lighting, and lamps, smart personal vehicles, smart thermostats, smart windows, doors, or garage doors, smart window blinds or shutters, and/or other smart devices and/or sensors capable of wireless or wired communication. Each smart device (or smart sensor), as well as the smart home controller, may be equipped with a processor, memory unit, software applications, wireless transceivers, local power supply, various types of sensors, and/or other components.
Each of the smart devices may be referenced by an inventory list associated with the property. The inventory list may detail a location (e.g., GPS coordinates, a room of the property, an area or section of the property, or other location indication) of each of the smart devices. In this regard, multiple smart devices may be associated with a single area or location of the property (e.g., a basement, a bathroom, a kitchen, a first floor, a hallway, a garage, a master bedroom, a child's bedroom, living room, family room, basement, higher floors for multi-story office buildings, etc.). Similarly, the inventory list may indicate the capabilities of each of the smart devices. For example, a smart fire ladder may be able to remotely receive instructions to deploy a ladder and/or roll the ladder back up. Of course, the capabilities of each smart device may vary between smart devices.
The smart home controller may remotely gather data from the smart devices (or smart sensors) dispersed around or otherwise interconnected within the property. The smart home controller may also receive data from an insurance provider (or other third party sources) that monitors potential risks to the property, such as inclement weather, crime patterns, recall data pertaining to goods disposed on or proximate to the property and/or other risks. The smart home controller may analyze the data and automatically detect the presence of a fire that may pose risks of damage to the property and/or individuals located thereon. Upon detection of a fire, the smart home controller may issue commands or messages via wireless or wired communication networks and/or data transmission that may mitigate the risks of damage.
The smart home controller may remotely gather this data to determine an occupancy state of the property. The occupancy state may indicate whether any individuals are currently located on the premises of the property, whereby the property may be deemed unoccupied if no individuals are currently located within, or in proximity to, the property or may be deemed occupied if at least one individual is located within, or in proximity to, the property. The occupancy state may also include an identity of which room the individuals located on the premises of the property are currently located.
As an example, the smart home controller may detect, via a heat sensor, a visual sensor, an infrared sensor, a sound sensor, and/or a smoke detector, that a fire is present on the property. The smart home controller may check the occupancy state of the property to determine whether any individuals need to evacuate the property. If there are any individuals on the property, the smart home controller may generate an escape route for each individual to safely evacuate the property. The smart home controller may communicate the escape routes to a mobile device associated with each individual. As a result, the mobile devices may display an interface that notifies the individual about the fire (or other emergency situation) and guides the individual along their respective escape route.
To mitigate the risk of damage to the property and/or ensure the safety of the individuals located thereon, the smart home controller may analyze the location of the smart devices compared to locations of the individual, the detected fire, and/or escape routes. The controller may then determine if the capabilities of the smart devices mitigate the risk of damage to the property or the individuals. For example, the smart home controller may transmit an instruction to a smart door that automatically causes the door to open to facilitate an easier escape. It should be appreciated that when there are multiple individuals located on the property, the smart home controller may ensure that performing the action to protect the safety of a first individual does not threaten the safety of a second individual.
The systems and methods discussed herein address a challenge that is particular to home automation. In particular, the challenge relates to a lack of user ability to effectively control certain components within a property while a fire is present. This is particularly apparent when the user is not aware of the fire and/or may not have time to manually perform actions to mitigate risks associated with the fire. For example, an individual may be located in a part of the property currently unaffected by the fire, and proper mitigation may require the individual to risk grievous bodily injury to manually perform a mitigative action. Moreover, during fire events, individuals may panic and be unable to decide on a proper course of action. Instead of requiring users to manually figure out the best way to mitigate damage to the property and/or deploy safety equipment, as required on conventional properties, the systems and methods dynamically determine the most appropriate actions to mitigate damage to the property and/or automatically adjust the operation of the smart devices accordingly. Therefore, because the systems and methods employ dynamic operation of connected devices within a property, the systems and methods are necessarily rooted in computer technology in order to overcome the noted shortcomings that specifically arise in the realm of home and/or building automation.
Similarly, the systems and methods provide improvements in a technical field, namely, home (and/or building) automation. Instead of the systems and methods merely being performed by hardware components using basic functions, the systems and methods employ complex steps that go beyond the mere concept of simply retrieving and combining data using a computer. In particular, the hardware components may compile operation data of connected devices, analyze the operation data, determine the presence of a fire, dynamically adjust device operation, generate escape routes, communicate relevant data between or among a set of devices, and/or alert emergency service providers, among other functionalities. This combination of elements impose meaningful limits in that the operations are applied to improve home automation by improving the consolidation and analysis of operation data, and by facilitating and/or enabling the efficient adjustment of connected device operation in a meaningful and effective way to mitigate risks associated with fires.
According to implementations, the systems and methods may support a dynamic, real-time or near-real-time analysis of any received sensor data. In particular, the central controller and/or insurance provider may retrieve and/or receive real-time sensor data from the smart devices, analyze the sensor data in real time, and dynamically determine a set of actions or commands based upon the analysis. Additionally, the central controller and/or insurance provider may provide, in real-time, the set of actions or commands to the smart device (and/or to another device) to perform the command to manage its operation. Accordingly, the real-time capability of the systems and methods enable the smart devices to dynamically modify their operation to mitigate risks associated with the presence of the fire on the property. Additionally, individuals associated with the property are afforded the benefit of being dynamically notified of the issues so that the individuals may take any additional or alternative mitigating actions.
The systems and methods therefore may offer a benefit by enabling homeowners to receive sufficient warning about fire events and to automatically minimize damage that may be caused by the fire. By communicating these instructions to homeowners, the smart home controller may minimize the risk of harm to devices disposed on the property and/or homeowners (and/or building occupants) themselves. Further, insurance providers may experience a reduction in the number of claims and/or a reduction in the amount claimed as a result of the mitigating the damage caused to the property by the fire, thus reducing their overall liabilities. The present systems and methods may also provide improvements, in certain aspects, to the technological fields of insurance, emergency response, appliance manufacturing, and/or urban planning.
As illustrated in
The plurality of smart devices 110 may be configured to communicate with a smart home controller 120 via the local communication network 115. The local network 115 may facilitate any type of data communication between devices and controllers located on or proximate to the property via any standard or technology (e.g., Bluetooth®, RFID, X10, UPnP®, IEEE 802 including Ethernet, GSM, CDMA, LTE, and/or others). According to present embodiments, the plurality of smart devices 110 may transmit, to the smart home controller 120 via the local network 115, sensor data gathered from sensors associated with the plurality of smart devices 110. The sensor data may be audio data, image or video data, or status data. For example, the sensor data may indicate the presence of smoke, thermal imaging data, the status of an alarm, sound detected by a smart device, and/or other information pertinent to determining the presence of a fire.
The smart home controller 120 (or other smart building controller) may analyze the received sensor data and transmit, via the local network 115, instructions or commands to the plurality of smart devices 110. As an example, the smart home controller 120 may determine, via a heat sensor, that there is a fire in a bedroom. As a result, the smart home controller 120 may transmit an instruction to activate a fire-suppressant and/or other actions to mitigate the risks associated with the fire. In some embodiments, the smart fire suppressant may respond by transmitting, to the smart home controller 120 via the local network 115, a confirmation that the action has been successfully performed.
According to present embodiments, the smart home controller 120 may be coupled to a database 122 that stores a list of smart devices on the property, such as the plurality of smart devices 110. In some embodiments, for each smart device listed in the database 122, the database 122 may contain a corresponding location of the smart device and/or a set of functions that the smart device is capable of performing. In some embodiments, the location of the smart device may indicate a specific location on a layout or virtual map of the property (whether a virtual map of a family home, multi-story office building, apartment building, or other type of structure, such as a luxury cruise ship). The smart home controller 120 may access the database 122 to determine a portion of the plurality of devices 110 located near the fire and/or that are capable of performing functions that mitigate the risks associated with the fire. Although
The smart home controller 120 may also be in communication, via the remote network 125, with an electronic device 145 associated with the homeowner 140. The electronic device 145 associated with the homeowner 140 may be a smartphone, a desktop computer, a laptop, a tablet, a smart watch, smart glasses, phablet, smart contact lenses, wearable electronics, pager, personal digital assistant, computing device configured for wireless communication, or any other electronic device. The remote network 125 may facilitate any data communication between the smart home controller 120 located on the property and entities or individuals remote to the property via any standard or technology (e.g., GSM, CDMA, TDMA, WCDMA, LTE, EDGE, OFDM, GPRS, EV-DO, UWB, IEEE 802 including Ethernet, WiMAX, and/or others). In some cases, both the local network 115 and the remote network 125 may utilize the same technology. Although
In some embodiments, when the smart home controller 120 determines that a fire is present on the property, the smart home controller 120 may generate and transmit notification to the electronic device 145 via the local network 115 and/or the remote network 125. The notification may include, inter alia, a location of the fire, a generated escape route (including instructions) to evacuate the property safely, visual location data depicting the escape route on a floor plan and/or map, safety tips to remember while evacuating, and/or any other information relevant to safely evacuating a property that is on fire. In some embodiments, the electronic device 145 may provide an interface such that the homeowner 140 may view any of the transmitted information. The interface may also enable the homeowner 145 to monitor, in substantially real time, a current location of the homeowner 145, a current status of the areas of the property made unsafe by the fire, progress along the escape route, and/or the like.
The smart home controller 120 may also be in communication with an insurance provider 130 via the remote network 125. According to present embodiments, the insurance provider 130 may include one or more processing servers 135 configured to facilitate the functionalities described herein. Although
According to present embodiments, the insurance provider 130 and/or smart home controller 120 may also be in communication with third party entities 150 pertaining to the detection of the fire on the property. For example, the smart home controller 120 and/or the processing sever 135 may transmit an alert to an emergency service provider informing the emergency service provider as to the presence of the fire. In response, the emergency service provider may dispatch responders to the property to extinguish the fire and/or otherwise mitigate damage caused by the fire. The exemplary environment 100 may include additional, fewer, or alternate equipment or components, including those discussed elsewhere herein.
Referring to
The signal diagram 200 may begin when the plurality of smart devices 210 transmit (250) sensor data to the smart home controller 220 (or other types of controllers, including those discussed elsewhere herein). The sensor data may include data, such as audio data, visual data, and status data, relevant to determining the presence of a fire and/or smoke on the property 205. The smart devices 210 may be configured to transmit the sensor data at a regular interval (e.g., every ten seconds) and/or in response to a trigger event (e.g., detecting the presence of smoke). It should be appreciated the length of the regular interval may vary based upon the type of each smart device 210 and the operational state of each smart device 210.
After receiving the sensor data from the plurality of smart devices 210, the smart home controller 220 may analyze the received data to determine (254) whether a fire is present on the premises of the property 205 and/or determine an extent of the fire. For example, the smart home controller 220 may analyze the received thermal imaging data to determine the presence of an abnormal heat condition indicative of a fire. As another example, the smart home controller 220 may then analyze status data from a smart smoke detector to determine the presence of smoke proximate to the smart smoke detector. In yet another example, the smart home controller 220 may analyze received audio data to detect that an audio pattern indicative of the presence of a fire. Of course, the smart home controller 220 may analyze any received data to determine the presence of a fire on the premises of the property 205.
If the smart home controller 220 analyzes the received data and determines that a fire does not currently exist on the premises of the property 205 (“NO”), processing may return to the beginning of the signal diagram 200 where the smart home controller 220 may await new data from the smart devices 210. In contrast, if the smart home controller 220 determines that there is a fire on the premises of the property 205 (“YES”), the smart home controller 220 may determine (258) a location of the fire. In some embodiments, the smart home controller 220 may determine the location of the fire by analyzing the source of the sensor data that indicated the presence of the fire. For example, if the sensor data that indicated the presence of the fire originated from a thermal sensor, then the smart home controller 220 may query the inventory list 222 to determine a location of the thermal sensor. In this example, if the inventory list 222 indicates that the thermal sensor is located and/or monitors the kitchen, the smart home controller 220 may determine that the fire is located in the kitchen. It should be appreciated, that in some scenarios, the fire may be located in a plurality of locations on the premises of the property 205 (such as on a first or fifth floor of a building or the third deck of a ship). Accordingly, the smart home controller 220 may determine a plurality of locations at which the fire is located.
Upon determining the location(s) of the fire, the smart home controller 220 may then compare (262) the determined location(s) of the fire to a list of smart devices stored in the inventory list 222. In particular, the smart home controller 220 may analyze location data associated with the plurality of devices 210 within the inventory list 222 to identify a set of smart devices that may potentially perform actions to mitigate risks associated with the fire. For example, the set of smart devices may initially include a list of smart devices in the same room (and/or on the same floor or level of a structure) as the fire and/or proximate to the fire. The smart controller 220 may then analyze the functionality supported by the smart devices within the set of smart devices to exclude smart devices that are incapable of performing actions to mitigate risks associated with the fire.
For example, if the fire is proximate to a smart water valve and a smart oven, the smart home controller 220 may determine that the smart water valve is unable to perform a function to mitigate risks associated with the fire whereas the smart oven may be capable of shutting off a power and/or gas flow into the smart oven. Accordingly, the smart home controller 220 may exclude and/or remove the smart water valve from the set of smart devices.
Additionally, the inventory list 222 may also track the location and/or occupancy state of the individual 240 while on the premises of the property 205 and/or otherwise have access to such information. Accordingly, the smart home controller 220 may determine that the individual 240 needs to evacuate the fire. In these scenarios, the smart home controller 220 may additionally compare the location of the individual 240 to the locations of the plurality of smart devices 210 in generating the set of smart devices. It should be understood that the set of data determinative of the presence of the individual 240 may be distinct from the set of data detecting the presence of the fire.
Based upon the comparison between the location of the fire and/or the individual 240 to the location of the plurality of smart devices 210, the smart home controller 220 may determine (266) a set of actions to mitigate the risks associated with the fire. Accordingly, the set of actions may include the performance of any functionality that caused the smart device to be included and/or remain in the set of smart devices (and/or a subset thereof). The set of actions may vary based upon the presence of the individual 240 on the premises of the property 205. For example, if the smart home controller 220 detects the presence of the individual 240 on the premises of the property 205, the smart home controller 220 may prioritize actions that facilitate the safe evacuation of the individual 240. Conversely, if the smart home controller 220 determines that the individual 240 is not located on the premises of the property 205, the smart home controller 220 may prioritize actions that facilitate a reduction in property damage caused by the fire. The differences between these priorities may be emphasized when the plurality of devices 210 includes one or more smart doors.
If the smart home controller 220 detects the presence of the individual 240 on the premises of the property 205, then the smart home controller 220 may determine that the set of actions includes opening a smart door (or smart window) to facilitate a faster evacuation. On the other hand, if the smart home controller 220 detects that the individual 240 is not present on the premises of the property 205, the smart home controller 220 may determine that the set of actions includes closing a smart door (or smart window) to facilitate the containment and/or suppression of the fire.
In embodiments in which the individual 240 is present and/or located on the premises of the property 205, the smart home controller 220 may generate an escape route for the individual 240. The escape routes may guide the individual 240 to a safe zone unaffected by the fire. To this end, the plurality of devices 210 may include smart evacuation equipment (e.g., an escape ladder, a rope, a set of stairs, etc.). If the escape route utilizes the smart evacuation equipment, then the smart home controller 220 may determine that the set of actions includes the deployment of the smart evacuation equipment, wherein deploying the smart evacuation equipment enables the smart evacuation equipment to become usable by the individual 240. Additionally, the smart home controller 220 may determine that the set of actions includes activating a lighted path and/or track lighting to further assist in guiding the individual 240 along the escape route.
Once the set of actions is determined, the smart home controller 220 may generate and transmit (270) instructions that cause the plurality of smart devices 210 to perform (274) the set of actions. The instructions may include an identity of the particular smart device 210 to perform the action and/or an action code associated with the particular functionality of each smart device 210. Each smart device 210 may analyze the instructions to determine whether the instructions identify that the particular smart device 210 should perform any actions. If the particular smart device 210 is to perform an action, the particular smart device 210 may analyze the action code to actually perform the instructed action. As an example, a smart water sprinkler may be identified as device abc123 and an action code of “ActivateSprinkler” may cause the smart water sprinkler to activate its sprinkler systems. Accordingly, if the smart water sprinkler determines that the instructions contain an instruction that device abc123 should perform the action “ActivateSprinkler,” the smart water sprinkler may activate its sprinkler systems.
If the smart home controller 220 detected the presence of the individual 240, the smart home controller 220 may also transmit (278) the escape route to the electronic device associated with the individual 240 via a communication network. After receiving the escape route, the electronic device may present the escape route to the individual 240. In some embodiments, this may include displaying a visual interface that depicts the escape route, and/or individual steps of the escape route superimposed on a map and/or a floor plan of the property 205. For example, an escape route that leads the individual 240 to a neighboring property may initially be displayed on a floor plan of the property 205; however, once the individual 240 leaves the premises of the property 240, the escape route may be displayed via a mapping program stored on the electronic device (e.g., Google Maps®). Additionally or alternatively, the electronic device may recite directions (such as audibly or visually) that guide the individual 240 along the escape route. It should be appreciated that any suitable method in which the electronic device may guide the individual 240 along the escape route is envisioned.
According to aspects, the smart home controller 220 may also transmit (282) a notification to the processing server 235. The notification may include an indication describing the set of actions (and/or a subset thereof) performed by the plurality of smart devices 210. In response, the processing server 235 may perform (286) an insurance related action. For example, the insurance-related action may include automatically generating an insurance claim for damage caused by the fire and/or appending received sensor data to the generated insurance claim. Additionally, in response to detecting the emergency situation, the smart home controller 220 may automatically alert an emergency services provider (not depicted) about the presence of the fire on the premises of the property 205. It should be appreciated that the signal diagram 200 may include additional, fewer, and/or alternative actions, including those discussed elsewhere herein. For example, in some embodiments, some of the actions described with respect to the smart home controller 220 may be alternatively performed by the processing server 235, and vice versa.
Additionally, if the smart door is initially in an open and/or partially open navigational state, the smart home controller may determine that the set of actions may include an instruction to change the navigational state of the smart door to shut. It should be appreciated that the smart home controller may ensure that shutting the smart door does not interfere and/or otherwise hinder an individual from proceeding along an escape route. Accordingly, in response to receiving an instruction to change a navigational state to shut, the smart door may cause the corresponding smart hinges to rotate in a manner to shut and/or close the smart door.
Moreover, as depicted in
Referring to
The method 400 may begin when the controller receives (block 405) sensor data indicative of a fire on the premises of the property from the plurality of devices disposed on the property. For example, the sensor data may include data indicating a fire alarm in a bedroom has been triggered and/or thermal sensor data indicating the presence of a fire in the bedroom. In some scenarios, the sensor data may additionally or alternatively indicate the presence of smoke on the premises of the property. In some embodiments, the sensor data may comprise data generated by thermal and/or heat sensors, smoke detectors, thermal imaging sensors, or any other sensor capable of determining the presence a fire and/or smoke on a property.
Once the controller determines that there is a fire present on the property, the controller may determine (block 410) a location on the property at which the fire is currently located and/or risks damaging persons and/or property. The determined location may include a GPS location, a coordinate associated with the property, and/or an identity of a room. To determine the location of the fire, the controller may determine a location of any sensor that generated data indicating the presence of the fire. For some sensors, the location of the sensor and the location of the property monitored by the sensor may be distinct locations. Accordingly, the controller may select the appropriate location based upon the type of sensor generating the sensor data. For example, a thermal camera located in a living room may be configured to receive data indicative of a thermal condition corresponding to an adjacent kitchen.
Upon determining the location of the fire, the controller may compare (block 415) the location of the fire to a list of devices on the property (such as an inventory list). In particular, the controller may compare the determined location of the fire to a plurality of locations respectively corresponding to the listed plurality of devices. For example, if the determined location of the fire is a basement, the controller may query the list to determine which of the plurality of smart devices are also located in the basement. In some cases, the smart device may be disposed in a different location than the room of which the smart device controls a condition. For example, a smart fuse controlling power to the basement may be disposed in a hallway closet. Accordingly, for each smart device in the list, the list may maintain a room in which the smart device is disposed as well as a set of rooms that the smart device may control and/or affect conditions associated therewith.
As a result of the comparison, the controller may determine a portion of the plurality of devices that are capable of performing functions that mitigate the risks associated with the fire and/or a presence thereof. Upon determining the portion of devices, the controller may then determine (block 420) an action for each of the portion of the plurality of devices to mitigate the aforementioned risks. As a result, the controller may determine a set of actions that may be performed by the portion of the plurality of devices. Some exemplary types of actions that may be included in the set of actions includes causing smart evacuation equipment to deploying, energizing smart emergency lighting, altering a navigation state of a smart door, de-energizing smart electronics, closing gas valves, activating sprinkler systems, and/or any other action that can mitigate the risk of damage to persons and/or property.
The controller may direct (block 425) devices disposed on the property to perform the set of actions. In some implementations, the controller may generate an instruction that, when received by a particular device, causes the device to perform a particular action of the set of actions. This instruction may be communicated over a local network. In some embodiments, the instruction may include an identification of the device to perform the action, an indication of device property to change, an indication of a value of the new device property, a time when the device property should change, and/or any other pertinent information to controlling a smart device.
In some implementations, in addition to directing the devices to perform the action, the controller may generate and/or communicate an escape route to an electronic device associated with the corresponding individual present on the property. The communication may provide the nature and location of the emergency situation, a layout of the property, step-by-step instructions directing the individual along the escape route, and/or any other information pertinent to the individual safely evacuating the property.
In some further implementations, the controller may also communicate a notification and/or an alert to an insurance provider associated with the property (e.g., the insurance provider 130). In response the insurance provider may perform an insurance-related action, such as automatically prepopulating an insurance claim. Additionally, the controller may communicate an alert to an emergency services provider informing the emergency services provider as to the presence of the fire on the premises of the property. As a result, the emergency services provider may dispatch a responder to facilitate mitigating risks of damage caused by the presence of the fire. The method 500 may include additional, less, or alternate actions, including those discussed elsewhere herein.
In one aspect, a computer-implemented method of responding to a fire on a property may be provided. The property may be populated with a hardware controller in communication with a plurality of devices and each of the plurality of devices may be configured to monitor various conditions associated with the property. The method may include (1) receiving, by the hardware controller via a first communication network, a first set of sensor data from at least one of the plurality of devices, the first set of sensor data indicative of the fire being present on the property; (2) analyzing, by one or more processors, the first set of sensor data to determine a location of the fire on the property; (3) comparing, by the one or more processors, the location of the fire to a list of the plurality of devices, the list including for each device at least one of a location of the device and/or a set of functions that the device is capable of performing to mitigate risks associated with the fire; (4) based upon the comparison, determining, by the one or more processors, a set of actions to be performed by at least a portion of the plurality of devices; and/or (5) directing or controlling, by the one or more processors, the at least the portion of the plurality of devices to perform the set of actions to facilitate a set of individuals escaping the fire in a safe manner. The method may include additional, less, or alternate actions, including those discussed elsewhere herein, and/or may be implemented via one or more local or remote processors (such as smart home controllers, smart office building controllers, smart ship controllers, mobile devices, insurance provider remote servers, etc.) and/or computer-executable instructions stored on non-transitory computer-readable medium or media.
For instance, the plurality of smart devices may include a smart door. Accordingly, directing or controlling the at least the portion of the plurality of devices may include directing or controlling, by the one or more processors, the smart door to cause a corresponding smart hinge to perform at least one of opening the smart door or closing the smart door.
Directing or controlling the smart door may include (1) receiving, by the hardware controller via a first communication network, a second set of sensor data from at least one of the plurality of devices, the second set of sensor data indicative of the presence of the set of individuals on the property; (2) analyzing, by one or more processors, the second set of sensor data to determine the number of individuals within the set of individuals present on the property; (3) when the set of individuals present on the property includes no individuals, directing or controlling, by the one or more processors, the smart door to close to facilitate fire suppression; and/or (4) when the set of individuals present on the property includes at least one individual, directing or controlling, by the one or more processors, the smart door to open to facilitate evacuation by the set of individuals.
Directing or controlling the at least the portion of the plurality of devices may include (1) analyzing, by one or more processors, the first set of sensor data to determine a location of smoke on the property; (2) comparing, by the one or more processors, the location of the smoke to a location of the smart door; and/or (3) when the location of the smoke is proximate to the location of the smart door, directing or controlling, by the one or more processors, the smart door to cause a corresponding smart door knob to glow and/or change color to increase a visibility of the smart door. Similarly, directing or controlling the at least the portion of the plurality of devices may include (1) comparing, by the one or more processors, the location of the fire to a location of the smart door; and/or (2) when the location of the fire is proximate to the location of the smart door, directing or controlling, by the one or more processors, the smart door to cause a corresponding smart door knob on a first side of the smart door to be illuminated in a color indicative of the fire being located proximate to a second side of the smart door. Receiving the first set of sensor data may include receiving, from a heat sensor located in a smart door knob corresponding to the smart door, a portion of the first set of sensor data.
The method may include the at least the portion of the plurality of devices including smart evacuation equipment. The smart evacuation equipment may include at least one of an escape ladder, a rope, and/or a set of stairs. Directing or controlling the at least the portion of the plurality of devices may include directing or controlling, by the one or more processors, a portion of the smart evacuation equipment to deploy, wherein deploying causes the smart evacuation equipment to become usable by the set of individuals.
The method may include transmitting, to an insurance provider associated with the property, a notification, wherein the notification includes an indication of at least one of the set of actions. Transmitting the notification may cause the insurance provider to perform an insurance-related action. The method may also include transmitting, to an emergency services provider, an alert, wherein the alert indicates that the fire is present on the property.
Determining the set of actions may include (1) generating, by the one or more processors, an escape route for an individual located on the premises of the property; and/or (2) transmitting, to an electronic device associated with the individual, the escape route.
In one aspect, a system for responding to a fire on a property may be provided. The property populated with a hardware controller in communication with a plurality of devices and each of the plurality of devices may be configured to monitor various conditions associated with the property. The system may include (i) a plurality of transceivers adapted to communicate data; (ii) a memory adapted to store non-transitory computer executable instructions; and/or (iii) one or more processors adapted to interface with the plurality of transceivers. The one or more processors may be configured to execute the non-transitory computer executable instructions to cause the system to (1) receive, by the plurality of transceivers, a first set of sensor data from at least one of the plurality of devices, the first set of sensor data indicative of the fire being present on the property; (2) analyze, by the one or more processors, the first set of sensor data to determine a location of the fire on the property; (3) compare, by the one or more processors, the location of the fire to a list of the plurality of devices, the list including for each device at least one of a location of the device and/or a set of functions that the device is capable of performing to mitigate risks associated with the fire; (4) based upon the comparison, determine, by the one or more processors, a set of actions to be performed by at least a portion of the plurality of devices; and/or (5) direct or control, by the one or more processors, the at least the portion of the plurality of devices to perform the set of actions to facilitate a set of individuals escaping the fire in a safe manner. The system may include additional, less, or alternate actions, including those discussed elsewhere herein.
For instance, to direct or control the at least the portion of the plurality of devices, the one or more processors may be configured to execute the non-transitory computer executable instructions to cause the system to direct or control, by the one or more processors, a smart door to cause a corresponding smart hinge to perform at least one of opening the smart door and/or closing the smart door.
To direct or control the smart door, the one or more processors may be configured to execute the non-transitory computer executable instructions to cause the system to (1) receive, by the plurality of transceivers, a second set of sensor data from at least one of the plurality of devices, the second set of sensor data indicative of the presence of the set of individuals on the property; (2) analyze, by one or more processors, the second set of sensor data to determine the number of individuals within the set of individuals present on the property; (3) when the number of individuals is zero, direct or control, by the one or more processors, the smart door to close to facilitate fire suppression; and/or (4) when the number of individuals is at least one, direct or control, by the one or more processors, the smart door to open to facilitate evacuation by the set of individuals.
To direct or control the at least the portion of the plurality of devices, the one or more processors may be configured to execute the non-transitory computer executable instructions to cause the system to (1) analyze, by one or more processors, the first set of sensor data to determine a location of smoke on the property; (2) compare, by the one or more processors, the location of the smoke to a location of the smart door; and/or (3) when the location of the smoke is proximate to the location of the smart door, direct or control, by the one or more processors, the smart door to cause a corresponding smart door knob to glow or change color to increase a visibility of the smart door. Additionally, to direct or control the at least the portion of the plurality of devices, the one or more processors may be configured to execute the non-transitory computer executable instructions to cause the system to (1) compare, by the one or more processors, the location of the fire to a location of the smart door; and/or (2) when the location of the fire is proximate to the location of the smart door, direct or control, by the one or more processors, the smart door to cause a corresponding smart door knob on a first side of the smart door to be illuminated in a color indicative of the fire being located proximate to a second side of the smart door.
The system may include the at least the portion of the plurality of devices including smart evacuation equipment. The smart evacuation equipment may include at least one of an escape ladder, a rope, and/or a set of stairs. To direct or control the at least the portion of the plurality of devices, the one or more processors may be configured to execute the non-transitory computer executable instructions to cause the system to direct or control, by the one or more processors, a portion of the smart evacuation equipment to deploy. Deploying may cause the smart evacuation equipment to become usable by the set of individuals.
The one or more processors may be further configured to execute the non-transitory computer executable instructions to cause the system to transmit, by the plurality of transceivers, a notification. The notification may include an indication of at least one of the set of actions, and transmitting the notification may cause an insurance provider to perform an insurance-related action. Additionally or alternatively, to determine the set of actions, the one or more processors may be configured to execute the non-transitory computer executable instructions to cause the system to (1) generate, by the one or more processors, an escape route for an individual located on the premises of the property; and/or (2) transmit, by the plurality of transceivers, the escape route to an electronic device associated with the individual.
The smart home controller 520 may include a processor 562, as well as a memory 578. The memory 578 may store an operating system 579 capable of facilitating the functionalities as described herein. The smart home controller 520 may also store a set of applications 575 (i.e., machine readable instructions). For example, one application of the set of applications 575 may be a fire response routine 584 configured to cause a plurality of smart devices to perform actions that mitigate the risks associated with the presence of a fire on the property. It should be appreciated that other applications may be included in the set of application 575.
The processor 562 may interface with the memory 578 to execute the operating system 579 and the set of applications 575. According to some embodiments, the memory 578 may also include an inventory list 522 that includes information related to the plurality of smart devices disposed on the premises of the property. The fire response routine 584 may access the inventory list 522 to determine an appropriate response to the presence of the fire. The memory 578 may include one or more forms of volatile and/or non-volatile, fixed and/or removable memory, such as read-only memory (ROM), electronic programmable read-only memory (EPROM), random access memory (RAM), erasable electronic programmable read-only memory (EEPROM), and/or other hard drives, flash memory, MicroSD cards, and others.
The smart home controller 520 may further include a plurality of transceivers 577 configured to communicate data via one or more networks 515. Network(s) 515 may include both a local network for communicating between devices mounted on, or proximate to, the property and a remote network for communicating between the property and external parties. According to some embodiments, the plurality of transceivers 577 may include one or more transceivers (e.g., WWAN, WLAN, and/or WPAN transceivers) functioning in accordance with IEEE standards, 3GPP standards, or other standards, and configured to receive and transmit data via one or more external ports 576. In some embodiments, the plurality of transceivers 577 may include separate transceivers configured to interact with the local and remote networks separately.
The smart home controller 520 may further include a user interface 581 configured to present information to a user and/or receive inputs from the user. As shown in
In general, a computer program product in accordance with an embodiment may include a computer usable storage medium (e.g., standard random access memory (RAM), an optical disc, a universal serial bus (USB) drive, or the like) having computer-readable program code embodied therein, wherein the computer-readable program code is adapted to be executed by the processor 562 (e.g., working in connection with the operating system 579) to facilitate the functions as described herein. In this regard, the program code may be implemented in any desired language, and may be implemented as machine code, assembly code, byte code, interpretable source code or the like (e.g., via C, C++, Java, Actionscript, Objective-C, Javascript, CSS, XML). In some embodiments, the computer program product may be part of a cloud network of resources.
The present embodiments may relate to, inter alia, managing operation of devices or personal property within a home or other type of property, such as household furniture, appliances, electronics, vehicles (e.g., cars, boats, motorcycles), and/or other personal belongings (e.g., clothing, jewelry, antiques). Generally, a home or property may have a “smart” central controller that may be wirelessly connected, or connected via hard-wire, with various household related items, devices, and/or sensors. The central controller may be associated with any type of property, such as homes, office buildings, restaurants, farms, ships, planes, vehicles, and/or other types of properties.
The central controller, and/or one or more remote processors or servers associated with an insurance provider, may be in wireless or wired communication with various “smart” items or devices, such as smart appliances (e.g., clothes washer, dryer, dish washer, refrigerator, etc.); smart heating devices (e.g., furnace, space heater, etc.); smart cooling devices (e.g., air conditioning units, fans, ceiling fans, etc.); smart plumbing fixtures (e.g., toilets, showers, water heaters, piping, interior and yard sprinklers, etc.); smart cooking devices (e.g., stoves, ovens, grills, microwaves, etc.); smart wiring, lighting, and lamps; smart personal vehicles; smart thermostats; smart windows, doors, or garage doors; smart window blinds or shutters; and/or other smart devices and/or sensors capable of wireless or wired communication. Each smart device (or sensor associated therewith), as well as the central controller and/or insurance provider remote processor(s), may be equipped with a processor, memory unit, software applications, wireless transceivers, local power supply, various types of sensors, and/or other components.
The central controller, and/or insurance provider remote processor(s), may collect or retrieve various data from the devices or personal property, analyze the data, and/or identify various actions to facilitate based upon the analysis. In particular, the central controller, and/or insurance provider remote processor(s), may issue commands to the devices or otherwise control operation of the devices. Upon receipt, the appropriate device may execute the command(s) to cause the smart device to perform an action or enter a preferred operation state. The central controller, and/or insurance provider remote processor(s), may also generate notifications of various operation states or completed actions, and communicate the notifications to individuals associated with the property.
Generally, the systems and methods offer numerous benefits to operation of devices within the property, as well as to individuals associated with the property. In particular, the systems and methods may automatically detect potential or actual issues with the property that the individuals may not realize exist, and may automatically facilitate preventative or corrective actions to address the issues. As a result, security associated with the property may improve. Further, the systems and methods improve loss prevention and mitigate actual loss. The systems and methods further apply to independent and/or assisted living situations, whereby patients may receive improved care and individuals associated with the patients may realize more effective communication. Additionally, the systems and methods may improve energy consumption.
The systems and methods may further offer a benefit to insurance providers and customers thereof. Particularly, the present embodiments may facilitate (a) providing and updating insurance policies; (b) the handling or adjusting of home insurance claims; (c) the disbursement of monies related to insurance claims; (d) modifying insurance coverage amounts; (e) updating and improving damage estimate models, and/or (f) other insurance-related activities. The systems and methods may further offer a benefit to customers by offering improved insurance claim processing. Further, the insurance providers may stand out as a cost-effective insurance provider, thereby retaining existing customers and attracting new customers. It should be appreciated that further benefits to the systems and methods are envisioned.
The smart home controller or remote processor may automatically direct or control (i) opening (and/or unlocking) smart windows and/or smart doors, and/or (ii) lighting up an evacuation path (e.g., remotely operating smart lighting or lamps) when a fire event is detected within the insured home by the smart home controller or remote processor to facilitate occupants evacuating the insured home during the fire event. Additionally or alternatively, the smart home controller or remote processor may automatically direct or control (i) lighting up an evacuation path (e.g., remotely operating smart lighting or lamps) and/or (2) deploying evacuation equipment (e.g., rope or ladder deployment) when a fire event is detected within the insured home by the smart home controller or remote processor to facilitate occupants evacuating the insured home during the fire event.
The insured home may have smart doors that include smart hinges. The smart hinges may be configured to (1) automatically open when a fire event is detected within the insured home by the smart home controller or remote processor, and (2) it is determined by the smart home controller or remote processor that the insured home is occupied to facilitate occupant evacuation. Additionally or alternatively, the smart hinges may be configured to (3) automatically close when a fire event is detected within the insured home by the smart home controller or remote processor, and (4) it is determined by the smart home controller or remote processor that the insured home is unoccupied to facilitate fire suppression.
In some embodiments, data from one of the smart devices may cause certain actions for another of the devices. For instance, if a smoke alarm triggers, then hinges (e.g., smart hinges) on a set of interior doors may cause the set of interior doors to close.
The insured home may have smart doors that include smart door knobs. The smart door knobs may be configured to change color or glow when a fire event is detected to facilitate insured home occupants finding doors within smoke-filled rooms or homes. Additionally or alternatively, the smart door knobs may be configured to change color or glow when a fire event is detected (such as by a heat sensor integrated with the smart door knob) to indicate that there is a fire, or potential fire, on the other side of the smart door.
As used herein, the term “smart” may refer to devices, sensors or appliances located inside or proximate to a property with the ability to remotely communicate information about the status of the device, sensor, or appliance and/or receive instructions that control the operation of the device, sensor, or appliance. For example, a smart thermostat may be able to remotely communicate the current temperature of the home and receive instructions to adjust the temperature to a new level. As another example, a smart water tank may be able to remotely communicate the level water contained therein and receive instructions to restrict the flow of water leaving the tank. In contrast, “dumb” devices, sensors, or appliances located inside or proximate to a property require manual control. Referring again to the thermostat example, to adjust the temperature on a “dumb” thermostat, a person would have to manually interact with the thermostat. As such, a person may be unable to use a communication network to remotely adjust a “dumb” device, sensor, or appliance.
For simplicity's sake, a “smart device” shall be used herein to refer to any of a smart device, sensor, appliance, and/or other smart equipment that may be disposed on or proximate to a property. In embodiments in which an appliance and a sensor external to the particular appliance are associated with each other, “smart device” may refer to both the external sensors and the appliance collectively. Some examples of devices that may be “smart devices” are, without limitation, valves, piping, clothes washers/dryers, dish washers, refrigerators, sprinkler systems, toilets, showers, sinks, soil monitors, doors, locks, windows, shutters, ovens, grills, fire places, furnaces, lighting, sump pumps, security cameras, and alarm systems. An individual associated with the property shall be referred to as the “homeowner,” but it is also envisioned that the individual is a family member of the homeowner, a person renting/subletting the property, a person living or working on the property, a neighbor of the property, an insured, or any other individual that may have an interest in preventing or mitigating damage to the property.
Further, any reference to “home” is meant to be exemplary and not limiting. The systems and methods described herein may be applied to any property, such as offices, farms, lots, parks, and/or other types of properties or buildings. Accordingly, “homeowner” may be used interchangeably with “property owner.” As used herein, “property” may also refer to any buildings, belongings and/or equipment disposed on the property itself.
It should be understood that the smart devices may be considered specific-purpose computers designed to perform specific tasks. For example, a smart window may comprise a processor specifically configured to monitor one or more networks for remotely-generated instructions to cause the smart window to open and/or close. The processor may additionally be specifically programmed to interpret the instructions to generate another instruction to cause a motor component corresponding to the smart window to physically open and/or close the smart window. In addition to the execution of instructions, the processor may also be specifically configured to monitor conditions associated with the smart window and to transmit the conditions via one or more networks. To this end, the processor corresponding to a smart device may be configured solely to perform specific actions indicated by received instructions and to communicate specific conditions associated with the smart device. Accordingly, the processor corresponding to the smart device may not be configurable to perform additional and/or alternative general-purpose functions typically associated with general-purpose computers. It should be understood that since the present application contemplates a variety of different smart devices, the specific-purpose of each processor may vary between and among the smart devices.
With the foregoing, an insurance customer may opt-in to a rewards, insurance discount, or other type of program. After the insurance customer provides their affirmative consent, an insurance provider remote server may collect data from the customer's mobile device, smart home controller, or other smart devices—such as with the customer's permission or affirmative consent. The data collected may be related to smart home functionality (e.g., fire mitigation functionality), and/or insured assets before (and/or after) an insurance-related event, including those events discussed elsewhere herein. In return, risk averse insureds, home owners, or home or apartment occupants may receive discounts or insurance cost savings related to home, renters, personal articles, auto, and other types of insurance from the insurance provider.
In one aspect, smart or interconnected home data, and/or other data, including the types of data discussed elsewhere herein, may be collected or received by an insurance provider remote server, such as via direct or indirect wireless communication or data transmission from a smart home controller, mobile device, or other customer computing device, after a customer affirmatively consents or otherwise opts-in to an insurance discount, reward, or other program. The insurance provider may then analyze the data received with the customer's permission to provide benefits to the customer. As a result, risk averse customers may receive insurance discounts or other insurance cost savings based upon data that reflects low risk behavior and/or technology that mitigates or prevents risk to (i) insured assets, such as homes, personal belongings, or vehicles, and/or (ii) home or apartment occupants.
Although the following text sets forth a detailed description of numerous different embodiments, it should be understood that the legal scope of the invention may be defined by the words of the claims set forth at the end of this patent. The detailed description is to be construed as exemplary only and does not describe every possible embodiment, as describing every possible embodiment would be impractical, if not impossible. One could implement numerous alternate embodiments, using either current technology or technology developed after the filing date of this patent, which would still fall within the scope of the claims.
Throughout this specification, plural instances may implement components, operations, or structures described as a single instance. Although individual operations of one or more methods are illustrated and described as separate operations, one or more of the individual operations may be performed concurrently, and nothing requires that the operations be performed in the order illustrated. Structures and functionality presented as separate components in example configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements fall within the scope of the subject matter herein.
Additionally, certain embodiments are described herein as including logic or a number of routines, subroutines, applications, or instructions. These may constitute either software (e.g., code embodied on a non-transitory, machine-readable medium) or hardware. In hardware, the routines, etc., are tangible units capable of performing certain operations and may be configured or arranged in a certain manner. In example embodiments, one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware modules of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware module that operates to perform certain operations as described herein.
In various embodiments, a hardware module may be implemented mechanically or electronically. For example, a hardware module may comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. It will be appreciated that the decision to implement a hardware module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.
Accordingly, the term “hardware module” should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. Considering embodiments in which hardware modules are temporarily configured (e.g., programmed), each of the hardware modules need not be configured or instantiated at any one instance in time. For example, where the hardware modules comprise a general-purpose processor configured using software, the general-purpose processor may be configured as respective different hardware modules at different times. Software may accordingly configure a processor, for example, to constitute a particular hardware module at one instance of time and to constitute a different hardware module at a different instance of time.
Hardware modules may provide information to, and receive information from, other hardware modules. Accordingly, the described hardware modules may be regarded as being communicatively coupled. Where multiple of such hardware modules exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) that connect the hardware modules. In embodiments in which multiple hardware modules are configured or instantiated at different times, communications between such hardware modules may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware modules have access. For example, one hardware module may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware module may then, at a later time, access the memory device to retrieve and process the stored output. Hardware modules may also initiate communications with input or output devices, and may operate on a resource (e.g., a collection of information).
The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented modules that operate to perform one or more operations or functions. The modules referred to herein may, in some example embodiments, comprise processor-implemented modules.
Similarly, the methods or routines described herein may be at least partially processor-implemented. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented hardware modules. The performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processor or processors may be located in a single location (e.g., within a home environment, an office environment, or as a server farm), while in other embodiments the processors may be distributed across a number of locations.
The performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the one or more processors or processor-implemented modules may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example embodiments, the one or more processors or processor-implemented modules may be distributed across a number of geographic locations.
Unless specifically stated otherwise, discussions herein using words such as “processing,” “computing,” “calculating,” “determining,” “presenting,” “displaying,” or the like may refer to actions or processes of a machine (e.g., a computer) that manipulates or transforms data represented as physical (e.g., electronic, magnetic, or optical) quantities within one or more memories (e.g., volatile memory, non-volatile memory, or a combination thereof), registers, or other machine components that receive, store, transmit, or display information.
As used herein any reference to “one embodiment” or “an embodiment” means that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.
The terms “insurer,” “insuring party,” and “insurance provider” are used interchangeably herein to generally refer to a party or entity (e.g., a business or other organizational entity) that provides insurance products, e.g., by offering and issuing insurance policies. Typically, but not necessarily, an insurance provider may be an insurance company.
Although the embodiments discussed herein relate to home or personal property insurance policies, it should be appreciated that an insurance provider may offer or provide one or more different types of insurance policies. Other types of insurance policies may include, for example, condominium owner insurance, renter's insurance, life insurance (e.g., whole-life, universal, variable, term), health insurance, disability insurance, long-term care insurance, annuities, business insurance (e.g., property, liability, commercial auto, workers compensation, professional and specialty liability, inland marine and mobile property, surety and fidelity bonds), automobile insurance, boat insurance, insurance for catastrophic events such as flood, fire, volcano damage and the like, motorcycle insurance, farm and ranch insurance, personal liability insurance, personal umbrella insurance, community organization insurance (e.g., for associations, religious organizations, cooperatives), and other types of insurance products. In embodiments as described herein, the insurance providers process claims related to insurance policies that cover one or more properties (e.g., homes, automobiles, personal property), although processing other insurance policies is also envisioned.
The terms “insured,” “insured party,” “policyholder,” “customer,” “claimant,” and “potential claimant” are used interchangeably herein to refer to a person, party, or entity (e.g., a business or other organizational entity) that is covered by the insurance policy, e.g., whose insured article or entity (e.g., property, life, health, auto, home, business) is covered by the policy. A “guarantor,” as used herein, generally refers to a person, party or entity that is responsible for payment of the insurance premiums. The guarantor may or may not be the same party as the insured, such as in situations when a guarantor has power of attorney for the insured. An “annuitant,” as referred to herein, generally refers to a person, party or entity that is entitled to receive benefits from an annuity insurance product offered by the insuring party. The annuitant may or may not be the same party as the guarantor.
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, or apparatus that comprises a list of elements is not necessarily limited to only those elements but may include other elements not expressly listed or inherent to such process, method, article, 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).
In addition, use of the “a” or “an” are employed to describe elements and components of the embodiments herein. This is done merely for convenience and to give a general sense of the description. This description, and the claims that follow, should be read to include one or at least one and the singular also includes the plural unless it is obvious that it is meant otherwise.
The patent claims at the end of this patent application are not intended to be construed under 35 U.S.C. § 112(f) unless traditional means-plus-function language is expressly recited, such as “means for” or “step for” language being explicitly recited in the claim(s).
This detailed description is to be construed as examples and does not describe every possible embodiment, as describing every possible embodiment would be impractical, if not impossible. One could implement numerous alternate embodiments, using either current technology or technology developed after the filing date of this application.
This application is a continuation of, and claims the benefit of, U.S. patent application Ser. No. 16/692,536 filed Nov. 22, 2019, which is a continuation of, and claims the benefit of, U.S. patent application Ser. No. 16/266,423 filed Feb. 4, 2019, which is a continuation of, and claims the benefit of, U.S. patent application Ser. No. 14/873,942 filed Oct. 2, 2015, which claims benefit of the filing date of U.S. Provisional Patent Application Nos. 62/060,962 (filed Oct. 7, 2014, and entitled “SYSTEMS AND METHODS FOR MANAGING DEVICES WITHIN A CONNECTED PROPERTY AND INSURANCE POLICIES ASSOCIATED THEREWITH”); 62/105,407 (filed Jan. 20, 2015, and entitled “SYSTEMS AND METHODS FOR MANAGING DEVICES WITHIN A CONNECTED PROPERTY AND INSURANCE POLICIES ASSOCIATED THEREWITH”); 62/187,624 (filed Jul. 1, 2015, and entitled “SYSTEMS AND METHODS FOR FACILITATING DEVICE REPLACEMENT WITHIN A CONNECTED PROPERTY”); 62/187,645 (filed Jul. 1, 2015, and entitled “SYSTEMS AND METHODS FOR MANAGING BUILDING CODE COMPLIANCE FOR A PROPERTY”); 62/187,651 (filed Jul. 1, 2015, and entitled “SYSTEMS AND METHODS FOR AUTOMATICALLY GENERATING AN ESCAPE ROUTE”); 62/187,642 (filed Jul. 1, 2015, and entitled “SYSTEMS AND METHODS FOR ANALYZING SENSOR DATA TO DETECT PROPERTY INTRUSION EVENTS”); 62/187,666 (filed Jul. 1, 2015, and entitled “SYSTEMS AND METHODS FOR IMPROVED ASSISTED OR INDEPENDENT LIVING ENVIRONMENTS”); 62/189,329 (filed Jul. 7, 2015, and entitled “SYSTEMS AND METHODS FOR MANAGING WARRANTY INFORMATION ASSOCIATED WITH DEVICES POPULATED WITHIN A PROPERTY”); 62/193,317 (filed Jul. 16, 2015, and entitled “SYSTEMS AND METHODS FOR MANAGING SMART DEVICES BASED UPON ELECTRICAL USAGE DATA”); 62/197,343 (filed Jul. 27, 2015, and entitled “SYSTEMS AND METHODS FOR CONTROLLING SMART DEVICES BASED UPON IMAGE DATA FROM IMAGE SENSORS”); 62/198,813 (filed Jul. 30, 2015, and entitled “SYSTEMS AND METHODS FOR MANAGING SERVICE LOG INFORMATION”); 62/200,375 (filed Aug. 3, 2015, and entitled “SYSTEMS AND METHODS FOR AUTOMATICALLY RESPONDING TO A FIRE”); 62/201,671 (filed Aug. 6, 2015, and entitled “SYSTEMS AND METHODS FOR AUTOMATICALLY MITIGATING RISK OF DAMAGE FROM BROKEN CIRCUITS”); 62/220,383 (filed Sep. 18, 2015, and entitled “METHODS AND SYSTEMS FOR RESPONDING TO A BROKEN CIRCUIT”)—which are all hereby incorporated by reference in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3648326 | Gaysowski | Mar 1972 | A |
| 3740739 | Griffin, III et al. | Jun 1973 | A |
| 3771823 | Schnarr | Nov 1973 | A |
| 3817161 | Koplon | Jun 1974 | A |
| 3875612 | Poitras | Apr 1975 | A |
| 3934306 | Farris | Jan 1976 | A |
| 4066072 | Cummins | Jan 1978 | A |
| 4418712 | Braley | Dec 1983 | A |
| 4688026 | Scribner et al. | Aug 1987 | A |
| 5005125 | Farrar et al. | Apr 1991 | A |
| 5038268 | Krause et al. | Aug 1991 | A |
| 5099751 | Newman | Mar 1992 | A |
| 5128859 | Carbone et al. | Jul 1992 | A |
| 5267587 | Brown | Dec 1993 | A |
| 5554433 | Perrone, Jr. | Sep 1996 | A |
| 5576952 | Stutman et al. | Nov 1996 | A |
| 5684710 | Ehlers et al. | Nov 1997 | A |
| 5903426 | Ehling | May 1999 | A |
| 5979607 | Allen | Nov 1999 | A |
| 6023762 | Dean et al. | Feb 2000 | A |
| 6084367 | Landert | Jul 2000 | A |
| 6104831 | Ruland | Aug 2000 | A |
| 6155324 | Elliott | Dec 2000 | A |
| 6222455 | Kaiser | Apr 2001 | B1 |
| 6237618 | Kushner | May 2001 | B1 |
| 6286682 | d'Arbelles | Sep 2001 | B1 |
| 6317047 | Stein | Nov 2001 | B1 |
| 6526807 | Doumit et al. | Mar 2003 | B1 |
| 6553336 | Johnson et al. | Apr 2003 | B1 |
| 6812848 | Candela | Nov 2004 | B2 |
| 6934692 | Duncan | Aug 2005 | B1 |
| 6977585 | Falk et al. | Dec 2005 | B2 |
| 6998960 | Buschmann | Feb 2006 | B2 |
| 7030767 | Candela | Apr 2006 | B2 |
| 7161483 | Chung | Jan 2007 | B2 |
| 7194416 | Provost et al. | Mar 2007 | B1 |
| 7259656 | Wright | Aug 2007 | B1 |
| 7309216 | Spadola, Jr. et al. | Dec 2007 | B1 |
| 7348882 | Adamczyk et al. | Mar 2008 | B2 |
| 7356516 | Richey et al. | Apr 2008 | B2 |
| 7395219 | Strech | Jul 2008 | B2 |
| 7598856 | Nick | Oct 2009 | B1 |
| 7657441 | Richey et al. | Feb 2010 | B2 |
| 7683793 | Li | Mar 2010 | B2 |
| 7715036 | Silverbrook et al. | May 2010 | B2 |
| 7809587 | Dorai et al. | Oct 2010 | B2 |
| 7813822 | Hoffberg | Oct 2010 | B1 |
| 7882514 | Nielsen et al. | Feb 2011 | B2 |
| 8010992 | Chang et al. | Aug 2011 | B1 |
| 8031079 | Kates | Oct 2011 | B2 |
| 8041636 | Hunter et al. | Oct 2011 | B1 |
| 8106769 | Maroney et al. | Jan 2012 | B1 |
| 8108271 | Duncan et al. | Jan 2012 | B1 |
| 8219558 | Trandal et al. | Jul 2012 | B1 |
| 8229861 | Trandal et al. | Jul 2012 | B1 |
| 8280633 | Eldering et al. | Oct 2012 | B1 |
| 8289160 | Billman | Oct 2012 | B1 |
| 8316237 | Felsher et al. | Nov 2012 | B1 |
| 8400299 | Maroney et al. | Mar 2013 | B1 |
| 8421475 | Thiim | Apr 2013 | B2 |
| 8490006 | Reeser et al. | Jul 2013 | B1 |
| 8510196 | Brandmaier et al. | Aug 2013 | B1 |
| 8527306 | Reeser et al. | Sep 2013 | B1 |
| 8533144 | Reeser et al. | Sep 2013 | B1 |
| 8595034 | Bauer et al. | Nov 2013 | B2 |
| 8595790 | Chang et al. | Nov 2013 | B2 |
| 8596293 | Mous et al. | Dec 2013 | B2 |
| 8605209 | Becker | Dec 2013 | B2 |
| 8620841 | Filson et al. | Dec 2013 | B1 |
| 8621097 | Venkatakrishnan et al. | Dec 2013 | B2 |
| 8640038 | Reeser et al. | Jan 2014 | B1 |
| 8650048 | Hopkins, III et al. | Feb 2014 | B1 |
| 8665084 | Shapiro et al. | Mar 2014 | B2 |
| 8694501 | Trandal et al. | Apr 2014 | B1 |
| 8712893 | Brandmaier et al. | Apr 2014 | B1 |
| 8719134 | Huls et al. | May 2014 | B1 |
| 8730039 | Billman | May 2014 | B1 |
| 8731975 | English et al. | May 2014 | B2 |
| 8749381 | Maroney et al. | Jun 2014 | B1 |
| 8786425 | Hutz | Jul 2014 | B1 |
| 8798289 | Every et al. | Aug 2014 | B1 |
| 8890680 | Reeser et al. | Nov 2014 | B2 |
| 8917186 | Grant | Dec 2014 | B1 |
| 8976937 | Shapiro et al. | Mar 2015 | B2 |
| 9009783 | Bartholomay et al. | Apr 2015 | B2 |
| 9049168 | Jacob et al. | Jun 2015 | B2 |
| 9057746 | Houlette et al. | Jun 2015 | B1 |
| 9076111 | Delorme et al. | Jul 2015 | B2 |
| 9107034 | Pham et al. | Aug 2015 | B2 |
| 9117318 | Ricci | Aug 2015 | B2 |
| 9117349 | Shapiro et al. | Aug 2015 | B2 |
| 9142119 | Grant | Sep 2015 | B1 |
| 9152737 | Micali et al. | Oct 2015 | B1 |
| 9183578 | Reeser et al. | Nov 2015 | B1 |
| 9202363 | Grant | Dec 2015 | B1 |
| 9244116 | Kabler et al. | Jan 2016 | B2 |
| 9257023 | Lee | Feb 2016 | B2 |
| 9262909 | Grant | Feb 2016 | B1 |
| 9280252 | Brandmaier et al. | Mar 2016 | B1 |
| 9286772 | Shapiro et al. | Mar 2016 | B2 |
| 9297150 | Klicpera | Mar 2016 | B2 |
| 9344330 | Jacob et al. | May 2016 | B2 |
| 9368009 | Lee et al. | Jun 2016 | B2 |
| 9424606 | Wilson, II et al. | Aug 2016 | B2 |
| 9424737 | Bailey et al. | Aug 2016 | B2 |
| 9429925 | Wait | Aug 2016 | B2 |
| 9443195 | Micali et al. | Sep 2016 | B2 |
| 9472092 | Grant | Oct 2016 | B1 |
| 9516141 | Dubois | Dec 2016 | B2 |
| 9589441 | Shapiro et al. | Mar 2017 | B2 |
| 9609003 | Chmielewski et al. | Mar 2017 | B1 |
| 9613523 | Davidson et al. | Apr 2017 | B2 |
| 9652976 | Bruck et al. | May 2017 | B2 |
| 9654434 | Sone et al. | May 2017 | B2 |
| 9665892 | Reeser et al. | May 2017 | B1 |
| 9666060 | Reeser et al. | May 2017 | B2 |
| 9683856 | Iyer et al. | Jun 2017 | B2 |
| 9685053 | Palmeri | Jun 2017 | B2 |
| 9699529 | Petri et al. | Jul 2017 | B1 |
| 9710858 | Devereaux et al. | Jul 2017 | B1 |
| 9721399 | Ishikawa | Aug 2017 | B2 |
| 9727921 | Cook et al. | Aug 2017 | B2 |
| 9739813 | Houlette et al. | Aug 2017 | B2 |
| 9786158 | Beaver et al. | Oct 2017 | B2 |
| 9798979 | Fadell et al. | Oct 2017 | B2 |
| 9798993 | Payne et al. | Oct 2017 | B2 |
| 9800570 | Bleisch | Oct 2017 | B1 |
| 9800958 | Petri et al. | Oct 2017 | B1 |
| 9812001 | Grant | Nov 2017 | B1 |
| 9823283 | Kabler et al. | Nov 2017 | B2 |
| 9824397 | Patel et al. | Nov 2017 | B1 |
| 9857414 | Kabler et al. | Jan 2018 | B1 |
| 9882985 | Esam et al. | Jan 2018 | B1 |
| 9888371 | Jacob | Feb 2018 | B1 |
| 9892463 | Hakimi-Boushehri et al. | Feb 2018 | B1 |
| 9898168 | Shapiro et al. | Feb 2018 | B2 |
| 9898912 | Jordan, II et al. | Feb 2018 | B1 |
| 9911042 | Cardona et al. | Mar 2018 | B1 |
| 9923971 | Madey et al. | Mar 2018 | B2 |
| 9942630 | Petri et al. | Apr 2018 | B1 |
| 9947051 | Allen et al. | Apr 2018 | B1 |
| 9947202 | Moon et al. | Apr 2018 | B1 |
| 9978033 | Payne et al. | May 2018 | B1 |
| 9997056 | Bleisch | Jun 2018 | B2 |
| 10002295 | Cardona et al. | Jun 2018 | B1 |
| 10005793 | Mazitschek et al. | Jun 2018 | B2 |
| 10042341 | Jacob | Aug 2018 | B1 |
| 10047974 | Riblet et al. | Aug 2018 | B1 |
| 10055793 | Call et al. | Aug 2018 | B1 |
| 10055803 | Orduna et al. | Aug 2018 | B2 |
| 10057664 | Moon et al. | Aug 2018 | B1 |
| 10062118 | Bernstein et al. | Aug 2018 | B1 |
| 10073929 | Vaynriber et al. | Sep 2018 | B2 |
| 10102584 | Devereaux et al. | Oct 2018 | B1 |
| 10102585 | Bryant et al. | Oct 2018 | B1 |
| 10107708 | Schick et al. | Oct 2018 | B1 |
| 10142394 | Chmielewski et al. | Nov 2018 | B2 |
| 10169771 | Devereaux et al. | Jan 2019 | B1 |
| 10176705 | Grant | Jan 2019 | B1 |
| 10181160 | Hakimi-Boushehri et al. | Jan 2019 | B1 |
| 10186134 | Moon et al. | Jan 2019 | B1 |
| 10198771 | Madigan et al. | Feb 2019 | B1 |
| 10217068 | Davis et al. | Feb 2019 | B1 |
| 10223750 | Loo et al. | Mar 2019 | B1 |
| 10229394 | Davis et al. | Mar 2019 | B1 |
| 10244294 | Moon et al. | Mar 2019 | B1 |
| 10249158 | Jordan, II et al. | Apr 2019 | B1 |
| 10255491 | Sekiguchi | Apr 2019 | B2 |
| 10269074 | Patel et al. | Apr 2019 | B1 |
| 10282787 | Hakimi-Boushehri et al. | May 2019 | B1 |
| 10282788 | Jordan, II et al. | May 2019 | B1 |
| 10282961 | Jordan, II et al. | May 2019 | B1 |
| 10295431 | Schick et al. | May 2019 | B1 |
| 10297138 | Reeser et al. | May 2019 | B2 |
| 10304313 | Moon et al. | May 2019 | B1 |
| 10323860 | Riblet et al. | Jun 2019 | B1 |
| 10325473 | Moon et al. | Jun 2019 | B1 |
| 10332059 | Matsuoka et al. | Jun 2019 | B2 |
| 10346811 | Jordan, II et al. | Jul 2019 | B1 |
| 10353359 | Jordan, II et al. | Jul 2019 | B1 |
| 10356303 | Jordan, II et al. | Jul 2019 | B1 |
| 10380692 | Parker et al. | Aug 2019 | B1 |
| 10387966 | Shah et al. | Aug 2019 | B1 |
| 10388135 | Jordan, II et al. | Aug 2019 | B1 |
| 10412169 | Madey et al. | Sep 2019 | B1 |
| 10430887 | Parker et al. | Oct 2019 | B1 |
| 10446000 | Friar et al. | Oct 2019 | B2 |
| 10467476 | Cardona et al. | Nov 2019 | B1 |
| 10467701 | Corder et al. | Nov 2019 | B1 |
| 10480825 | Riblet et al. | Nov 2019 | B1 |
| 10482746 | Moon et al. | Nov 2019 | B1 |
| 10506411 | Jacob | Dec 2019 | B1 |
| 10514669 | Call et al. | Dec 2019 | B1 |
| 10515372 | Jordan, II et al. | Dec 2019 | B1 |
| 10522009 | Jordan, II et al. | Dec 2019 | B1 |
| 10546478 | Moon et al. | Jan 2020 | B1 |
| 10547918 | Moon et al. | Jan 2020 | B1 |
| 10552911 | Allen et al. | Feb 2020 | B1 |
| 10565541 | Payne et al. | Feb 2020 | B2 |
| 10573146 | Jordan, II et al. | Feb 2020 | B1 |
| 10573149 | Jordan, II et al. | Feb 2020 | B1 |
| 10579028 | Jacob | Mar 2020 | B1 |
| 10586177 | Choueiter et al. | Mar 2020 | B1 |
| 10607295 | Hakimi-Boushehri et al. | Mar 2020 | B1 |
| 10634576 | Schick et al. | Apr 2020 | B1 |
| 10679292 | Call et al. | Jun 2020 | B1 |
| 10685402 | Bryant et al. | Jun 2020 | B1 |
| 10726494 | Shah et al. | Jul 2020 | B1 |
| 10726500 | Shah et al. | Jul 2020 | B1 |
| 10733671 | Hakimi-Boushehri et al. | Aug 2020 | B1 |
| 10733868 | Moon et al. | Aug 2020 | B2 |
| 10735829 | Petri et al. | Aug 2020 | B2 |
| 10740691 | Choueiter et al. | Aug 2020 | B2 |
| 10741033 | Jordan et al. | Aug 2020 | B1 |
| 10750252 | Petri et al. | Aug 2020 | B2 |
| 10795329 | Jordan, II et al. | Oct 2020 | B1 |
| 10796557 | Sundermeyer et al. | Oct 2020 | B2 |
| 10823458 | Riblet et al. | Nov 2020 | B1 |
| 10824971 | Davis et al. | Nov 2020 | B1 |
| 10825320 | Moon et al. | Nov 2020 | B1 |
| 10825321 | Moon et al. | Nov 2020 | B2 |
| 10832225 | Davis et al. | Nov 2020 | B1 |
| 10846800 | Bryant et al. | Nov 2020 | B1 |
| 10922756 | Call et al. | Feb 2021 | B1 |
| 10922948 | Moon et al. | Feb 2021 | B1 |
| 10943447 | Jordan, II et al. | Mar 2021 | B1 |
| 10970990 | Jacob | Apr 2021 | B1 |
| 10990069 | Jacob | Apr 2021 | B1 |
| 11004320 | Jordan, II et al. | May 2021 | B1 |
| 11015997 | Schick et al. | May 2021 | B1 |
| 11017480 | Shah et al. | May 2021 | B2 |
| 11042137 | Call et al. | Jun 2021 | B1 |
| 11042942 | Hakimi-Boushehri et al. | Jun 2021 | B1 |
| 11043098 | Jordan, II et al. | Jun 2021 | B1 |
| 11049078 | Jordan, II et al. | Jun 2021 | B1 |
| 11049189 | Shah et al. | Jun 2021 | B2 |
| 11074659 | Hakimi-Boushehri et al. | Jul 2021 | B1 |
| 11118812 | Riblet et al. | Sep 2021 | B1 |
| 11126708 | Reimer | Sep 2021 | B2 |
| 20010025349 | Sharood et al. | Sep 2001 | A1 |
| 20020040306 | Sugiyama et al. | Apr 2002 | A1 |
| 20020147006 | Coon et al. | Oct 2002 | A1 |
| 20020184643 | Fichet | Dec 2002 | A1 |
| 20030025599 | Monroe | Feb 2003 | A1 |
| 20030048191 | Denton | Mar 2003 | A1 |
| 20030192600 | Ford | Oct 2003 | A1 |
| 20030234725 | Lemelson et al. | Dec 2003 | A1 |
| 20040054789 | Breh et al. | Mar 2004 | A1 |
| 20040153346 | Grundel et al. | Aug 2004 | A1 |
| 20040153382 | Boccuzzi et al. | Aug 2004 | A1 |
| 20040177032 | Bradley et al. | Sep 2004 | A1 |
| 20040185844 | Neuman | Sep 2004 | A1 |
| 20040211228 | Nishio et al. | Oct 2004 | A1 |
| 20040214566 | Suzuki et al. | Oct 2004 | A1 |
| 20050030175 | Wolfe | Feb 2005 | A1 |
| 20050080520 | Kline et al. | Apr 2005 | A1 |
| 20050111696 | Baer | May 2005 | A1 |
| 20050139420 | Spoltore | Jun 2005 | A1 |
| 20050143956 | Long et al. | Jun 2005 | A1 |
| 20050241003 | Sweeney | Oct 2005 | A1 |
| 20050251427 | Dorai et al. | Nov 2005 | A1 |
| 20050275527 | Kates | Dec 2005 | A1 |
| 20060033625 | Johnson et al. | Feb 2006 | A1 |
| 20060058612 | Dave et al. | Mar 2006 | A1 |
| 20060100912 | Kumar et al. | May 2006 | A1 |
| 20060154642 | Scannell | Jul 2006 | A1 |
| 20060158339 | Brundula | Jul 2006 | A1 |
| 20060184379 | Tan et al. | Aug 2006 | A1 |
| 20070001904 | Mendelson | Jan 2007 | A1 |
| 20070096938 | Lopez et al. | May 2007 | A1 |
| 20070146150 | Calabrese | Jun 2007 | A1 |
| 20070262857 | Jackson | Nov 2007 | A1 |
| 20070276626 | Bruffey | Nov 2007 | A1 |
| 20070289635 | Ghazarian et al. | Dec 2007 | A1 |
| 20080018474 | Bergman | Jan 2008 | A1 |
| 20080019392 | Lee | Jan 2008 | A1 |
| 20080056722 | Hendrix et al. | Mar 2008 | A1 |
| 20080059351 | Richey et al. | Mar 2008 | A1 |
| 20080065427 | Helitzer et al. | Mar 2008 | A1 |
| 20080101160 | Besson | May 2008 | A1 |
| 20080157984 | Li et al. | Jul 2008 | A1 |
| 20080184272 | Brownewell | Jul 2008 | A1 |
| 20080231468 | Myllymaki | Sep 2008 | A1 |
| 20080285797 | Hammadou | Nov 2008 | A1 |
| 20080301216 | Han | Dec 2008 | A1 |
| 20090001891 | Patterson | Jan 2009 | A1 |
| 20090024420 | Winkler | Jan 2009 | A1 |
| 20090044595 | Vokey | Feb 2009 | A1 |
| 20090094129 | Rhodes et al. | Apr 2009 | A1 |
| 20090174364 | Onishi et al. | Jul 2009 | A1 |
| 20090195349 | Frader-Thompson et al. | Aug 2009 | A1 |
| 20090206059 | Kiko | Aug 2009 | A1 |
| 20090243852 | Haupt et al. | Oct 2009 | A1 |
| 20090259581 | Horowitz et al. | Oct 2009 | A1 |
| 20090265193 | Collins et al. | Oct 2009 | A1 |
| 20100025349 | Khoshnevis | Feb 2010 | A1 |
| 20100073840 | Hennessey, Jr. | Mar 2010 | A1 |
| 20100131416 | Means | May 2010 | A1 |
| 20100188023 | Anderson | Jul 2010 | A1 |
| 20100188206 | Kates | Jul 2010 | A1 |
| 20100235285 | Hoffberg | Sep 2010 | A1 |
| 20100241465 | Amigo et al. | Sep 2010 | A1 |
| 20100289643 | Trundle et al. | Nov 2010 | A1 |
| 20100299217 | Hui | Nov 2010 | A1 |
| 20110003577 | Rogalski et al. | Jan 2011 | A1 |
| 20110029145 | Dong | Feb 2011 | A1 |
| 20110040785 | Steenberg et al. | Feb 2011 | A1 |
| 20110077875 | Tran et al. | Mar 2011 | A1 |
| 20110112660 | Bergmann | May 2011 | A1 |
| 20110136463 | Ebdon et al. | Jun 2011 | A1 |
| 20110161117 | Busque et al. | Jun 2011 | A1 |
| 20110161119 | Collins | Jun 2011 | A1 |
| 20110166714 | Stachnik | Jul 2011 | A1 |
| 20110195687 | Das et al. | Aug 2011 | A1 |
| 20110203383 | Phelps | Aug 2011 | A1 |
| 20110251807 | Rada et al. | Oct 2011 | A1 |
| 20110270453 | Kalogridis et al. | Nov 2011 | A1 |
| 20120016695 | Bernard et al. | Jan 2012 | A1 |
| 20120046973 | Eshleman et al. | Feb 2012 | A1 |
| 20120054124 | Rodrigues | Mar 2012 | A1 |
| 20120079092 | Woxblom et al. | Mar 2012 | A1 |
| 20120101855 | Collins et al. | Apr 2012 | A1 |
| 20120116071 | Rao et al. | May 2012 | A1 |
| 20120116820 | English et al. | May 2012 | A1 |
| 20120131217 | Delorme et al. | May 2012 | A1 |
| 20120166115 | Apostolakis | Jun 2012 | A1 |
| 20120188081 | Van Katwijk | Jul 2012 | A1 |
| 20120191498 | Singh et al. | Jul 2012 | A1 |
| 20120204490 | Lanigan | Aug 2012 | A1 |
| 20120232935 | Voccola | Sep 2012 | A1 |
| 20120249121 | Pamulaparthy | Oct 2012 | A1 |
| 20120265586 | Mammone | Oct 2012 | A1 |
| 20120290333 | Birchall | Nov 2012 | A1 |
| 20120290497 | Magara et al. | Nov 2012 | A1 |
| 20120296580 | Barkay | Nov 2012 | A1 |
| 20120311620 | Conklin et al. | Dec 2012 | A1 |
| 20130022234 | U S et al. | Jan 2013 | A1 |
| 20130049950 | Wohlert | Feb 2013 | A1 |
| 20130073321 | Hofmann et al. | Mar 2013 | A1 |
| 20130083193 | Okuyama et al. | Apr 2013 | A1 |
| 20130085688 | Miller et al. | Apr 2013 | A1 |
| 20130096960 | English et al. | Apr 2013 | A1 |
| 20130107706 | Raleigh | May 2013 | A1 |
| 20130120137 | Lehmann | May 2013 | A1 |
| 20130144486 | Ricci | Jun 2013 | A1 |
| 20130145693 | Li | Jun 2013 | A1 |
| 20130159021 | Felsher | Jun 2013 | A1 |
| 20130166325 | Ganapathy et al. | Jun 2013 | A1 |
| 20130169817 | Jones et al. | Jul 2013 | A1 |
| 20130226624 | Blessman et al. | Aug 2013 | A1 |
| 20130234840 | Trundle et al. | Sep 2013 | A1 |
| 20130242074 | Sekiguchi | Sep 2013 | A1 |
| 20130257626 | Masli et al. | Oct 2013 | A1 |
| 20130263611 | Kearney et al. | Oct 2013 | A1 |
| 20130290013 | Forrester | Oct 2013 | A1 |
| 20130290033 | Reeser et al. | Oct 2013 | A1 |
| 20130317861 | Tofte et al. | Nov 2013 | A1 |
| 20140032433 | Eick et al. | Jan 2014 | A1 |
| 20140118140 | Amis | May 2014 | A1 |
| 20140122133 | Weisberg et al. | May 2014 | A1 |
| 20140136242 | Weekes et al. | May 2014 | A1 |
| 20140142989 | Grosso | May 2014 | A1 |
| 20140149127 | Storti | May 2014 | A1 |
| 20140172723 | Borisov et al. | Jun 2014 | A1 |
| 20140180723 | Cote et al. | Jun 2014 | A1 |
| 20140201315 | Jacob et al. | Jul 2014 | A1 |
| 20140201844 | Buck | Jul 2014 | A1 |
| 20140216071 | Broadbent | Aug 2014 | A1 |
| 20140222298 | Gurin | Aug 2014 | A1 |
| 20140222329 | Frey | Aug 2014 | A1 |
| 20140222469 | Stahl et al. | Aug 2014 | A1 |
| 20140229205 | Gibson | Aug 2014 | A1 |
| 20140238511 | Klicpera | Aug 2014 | A1 |
| 20140244997 | Goel et al. | Aug 2014 | A1 |
| 20140257862 | Billman et al. | Sep 2014 | A1 |
| 20140257871 | Christensen et al. | Sep 2014 | A1 |
| 20140257876 | English et al. | Sep 2014 | A1 |
| 20140266669 | Fadell et al. | Sep 2014 | A1 |
| 20140266717 | Warren et al. | Sep 2014 | A1 |
| 20140277625 | Gettings et al. | Sep 2014 | A1 |
| 20140278571 | Mullen et al. | Sep 2014 | A1 |
| 20140303801 | Ahn et al. | Oct 2014 | A1 |
| 20140306799 | Ricci | Oct 2014 | A1 |
| 20140306806 | Martinez de Velasco Cortina et al. | Oct 2014 | A1 |
| 20140310162 | Collins | Oct 2014 | A1 |
| 20140313044 | Thompson et al. | Oct 2014 | A1 |
| 20140317741 | Be'ery | Oct 2014 | A1 |
| 20140318200 | Ellis | Oct 2014 | A1 |
| 20140320295 | Kates | Oct 2014 | A1 |
| 20140340216 | Puskarich | Nov 2014 | A1 |
| 20140340222 | Thornton | Nov 2014 | A1 |
| 20140358592 | Wedig | Dec 2014 | A1 |
| 20140359552 | Misra et al. | Dec 2014 | A1 |
| 20140379156 | Kamel et al. | Dec 2014 | A1 |
| 20150020299 | Hsu | Jan 2015 | A1 |
| 20150025915 | Lekas | Jan 2015 | A1 |
| 20150032480 | Blackhurst et al. | Jan 2015 | A1 |
| 20150061859 | Matsuoka et al. | Mar 2015 | A1 |
| 20150116107 | Fadell et al. | Apr 2015 | A1 |
| 20150116112 | Flinsenberg et al. | Apr 2015 | A1 |
| 20150124087 | Jones, Jr. et al. | May 2015 | A1 |
| 20150135596 | Cooper | May 2015 | A1 |
| 20150154712 | Cook | Jun 2015 | A1 |
| 20150156031 | Fadell et al. | Jun 2015 | A1 |
| 20150160623 | Holley | Jun 2015 | A1 |
| 20150160636 | McCarthy, III | Jun 2015 | A1 |
| 20150163412 | Holley | Jun 2015 | A1 |
| 20150168976 | Loucks et al. | Jun 2015 | A1 |
| 20150170288 | Harton et al. | Jun 2015 | A1 |
| 20150206249 | Fini | Jul 2015 | A1 |
| 20150254940 | Graef et al. | Sep 2015 | A1 |
| 20150287310 | Deliuliis et al. | Oct 2015 | A1 |
| 20150305690 | Tan et al. | Oct 2015 | A1 |
| 20150332407 | Wilson, II et al. | Nov 2015 | A1 |
| 20150347910 | Fadell et al. | Dec 2015 | A1 |
| 20150364028 | Child et al. | Dec 2015 | A1 |
| 20160005130 | Devereaux et al. | Jan 2016 | A1 |
| 20160006723 | Wilson | Jan 2016 | A1 |
| 20160018226 | Plocher | Jan 2016 | A1 |
| 20160042463 | Gillespie | Feb 2016 | A1 |
| 20160078744 | Gieck | Mar 2016 | A1 |
| 20160104250 | Allen et al. | Apr 2016 | A1 |
| 20160119424 | Kane et al. | Apr 2016 | A1 |
| 20160161940 | Max | Jun 2016 | A1 |
| 20160163186 | Davidson et al. | Jun 2016 | A1 |
| 20160188829 | Southerland et al. | Jun 2016 | A1 |
| 20160225562 | Franks et al. | Aug 2016 | A1 |
| 20160269882 | Balthasar et al. | Sep 2016 | A1 |
| 20160269883 | Eswaran | Sep 2016 | A1 |
| 20160274154 | Kabler et al. | Sep 2016 | A1 |
| 20160292321 | Wall | Oct 2016 | A1 |
| 20160323771 | Raleigh | Nov 2016 | A1 |
| 20160337829 | Fletcher et al. | Nov 2016 | A1 |
| 20160343084 | Blessman et al. | Nov 2016 | A1 |
| 20170116676 | Blessman et al. | Apr 2017 | A1 |
| 20170147722 | Greenwood | May 2017 | A1 |
| 20170304659 | Chen | Oct 2017 | A1 |
| 20180000346 | Cronin | Jan 2018 | A1 |
| 20180146042 | Choi | May 2018 | A1 |
| 20180160988 | Miller et al. | Jun 2018 | A1 |
| 20190363746 | Zalewski et al. | Nov 2019 | A1 |
| 20200302549 | Jordan, II et al. | Sep 2020 | A1 |
| 20200327791 | Moon et al. | Oct 2020 | A1 |
| 20210035432 | Moon et al. | Feb 2021 | A1 |
| 20210042843 | Bryant et al. | Feb 2021 | A1 |
| 20210158671 | Jordan, II et al. | May 2021 | A1 |
| 20210248884 | Dougan | Aug 2021 | A1 |
| Number | Date | Country |
|---|---|---|
| 202865924 | Apr 2013 | CN |
| WO-2008155545 | Dec 2008 | WO |
| WO-2013076721 | May 2013 | WO |
| WO-2014207558 | Dec 2014 | WO |
| Entry |
|---|
| Knutsen, Confusion about causation in insurance: solutions for catastrophic losses, Ala. L. Rev., 5:957-1023 (2010). |
| Anonymous, “Systems and Methods for Insurers to Monitor Continuously Structural Status of Insured Homes”, ip.com Prior Art Database, Disclosure No. IPCOM000177511D, published Dec. 16, 2008 (Year: 2008). |
| Romero, Monsoon Mess?? Whom do you call?, Arizona Republic, Phoenix Arizona, May 26, 2012. |
| “System for Loss Prevention”, downloaded from the Internet at: <https://priorart.ip.com/IPCOM/000176198>, published Nov. 8, 2008. |
| Number | Date | Country | |
|---|---|---|---|
| 20210158671 A1 | May 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62220383 | Sep 2015 | US | |
| 62201671 | Aug 2015 | US | |
| 62200375 | Aug 2015 | US | |
| 62198813 | Jul 2015 | US | |
| 62197343 | Jul 2015 | US | |
| 62193317 | Jul 2015 | US | |
| 62189329 | Jul 2015 | US | |
| 62187624 | Jul 2015 | US | |
| 62187645 | Jul 2015 | US | |
| 62187666 | Jul 2015 | US | |
| 62187651 | Jul 2015 | US | |
| 62187642 | Jul 2015 | US | |
| 62105407 | Jan 2015 | US | |
| 62060962 | Oct 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16692536 | Nov 2019 | US |
| Child | 17170659 | US | |
| Parent | 16266423 | Feb 2019 | US |
| Child | 16692536 | US | |
| Parent | 14873942 | Oct 2015 | US |
| Child | 16266423 | US |
