The disclosed embodiments generally relate to a method and computerized system for managing electronic sensors.
Smart home technology refers to control and even automation of different house functionalities, such as lighting, heating, ventilation, air conditioning (HVAC), and security, as well as home appliances such as washer/dryers, ovens or refrigerators/freezers or even home entertainment system. Homeowners may install several sensors (each configured to collect a certain type of data) and may monitor different aspects and functionalities within their homes. For example, a homeowner may install a smart thermostat, which monitors temperature patterns and may even adjust the temperature of the house based on the detected pattern.
As the smart home technology has advanced recently, several technical challenges have also been identified. For instance, conventional smart home software solutions provide a single category solution with limited intra-communication ability. For example, a smart thermostat may determine a temperature pattern or adjust the temperature; however, (due to technical challenges) the smart thermostat may not be able to communicate with other sensors. In another example, a motion detector (configured to use infrared technology and detect motion and heat) may monitor movement and alert the homeowner when it detects movement within the house. However, the motion sensor is not in communication with other sensors (such as camera sensors) and may provide erroneous alerts simply because it detects motions. Furthermore, existing and conventional methods do not provide a method for a central server to receive data from the motion sensor, activate a camera sensor, and verify the data received form the motion sensor. Existing and conventional methods fail to provide fast and efficient analysis of building condition data and fail to provide effective communication between different sensors due to a high volume of building condition data captured by different sensors on different networks and/or computing infrastructures. Managing such information is difficult due to data type, size, or content associated with different sensors.
For the aforementioned reasons, there is a need for a central server to actively communicate with different sensors, analyze the data, and further control the functional behavior of one or more sensors. This summary section is provided to introduce a selection of concepts in a simplified form that are further described subsequently in the detailed description section. This summary section is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
In an embodiment, a method comprises receiving, by a server, a set of building condition data from a motion sensor device associated with a building and connected to a network of the building, wherein the set of building condition data comprises at least a heat map indicating presence of one or more inhabitants within the building; upon receiving the set of building condition data, generating a first instruction commanding an immediate capture of an image; upon transmitting the first instructions to a camera sensor device connected to the network of the building, receiving, by the server, at least one image captured by the camera sensor device; identifying, by the server, at least one inhabitant present within the building based on the set of building condition data and the at least one image received; retrieving, by the server, profile data corresponding to the identified inhabitant present within the building, the profile data comprising at least an environmental preference value of the identified inhabitant's; generating, by the server, a second instruction in accordance with the environmental preference value; and transmitting, by the server, the second instruction to one or more environmental devices coupled to the network of the building, whereby the second instructions commands the one or more environmental devices to modify environmental condition of the building in accordance with the environmental preference value.
In another embodiment, a computer system comprising: a plurality of home sensors devices connected to a network of a building and configured to collect building condition data, wherein the plurality of home sensor devices comprises at least a camera sensor device and a motion sensor device; one or more environmental devices coupled to the network of the building and configured to modify environmental conditions of the building; and a server connected to the network and in connection with the one or more environmental devices and the plurality of home sensors devices, wherein the server is configured to: receive a set of building condition data from the motion sensor device associated with the building and connected to the network of the building, wherein the set of building condition data comprises at least a heat map indicating presence of one or more inhabitants within the building; upon receiving the set of building condition data, generate a first instruction commanding an immediate capture of an image; upon transmitting the first instructions to the camera sensor device connected to the network of the building, receive at least one image captured by the camera sensor device; identify at least one inhabitant present within the building based on the set of building condition data and the at least one image received; retrieve profile data corresponding to the identified inhabitant present within the building, the profile data comprising at least an environmental preference value of the identified inhabitant's; generate a second instruction in accordance with the environmental preference value; and transmit the second instruction to one or more environmental devices coupled to the network of the building, whereby the second instructions commands the one or more environmental devices to modify environmental condition of the building in accordance with the environmental preference value.
The accompanying appendices and/or drawings illustrate various non-limiting, example, inventive aspects in accordance with the present disclosure:
The illustrated embodiments are now described more fully with reference to the accompanying drawings wherein like reference numerals identify similar structural/functional features. The illustrated embodiments are not limited in any way to what is illustrated, as the illustrated embodiments described below are merely exemplary, which can be embodied in various forms, as appreciated by one skilled in the art. Therefore, it is to be understood that any structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a basis for the claims and as a representation for teaching one skilled in the art to employ the discussed embodiments. Furthermore, the terms and phrases used herein are not intended to be limiting but rather to provide an understandable description of the illustrated embodiments.
As used herein, the term “software” is meant to be synonymous with any code or program that can be in a processor of a host computer, regardless of whether the implementation is in hardware, firmware or as a software computer product available on a disc, a memory storage device, or for download from a remote machine. The embodiments described herein include such software to implement the equations, relationships and algorithms described above. One skilled in the art will appreciate further features and advantages of the illustrated embodiments based on the above-described embodiments. Accordingly, the illustrated embodiments are not to be limited by what has been particularly shown and described, except as indicated by the appended claims. All publications and references cited herein are expressly incorporated herein by reference in their entirety. For instance, commonly assigned U.S. Pat. Nos. 8,289,160 and 8,400,299 are related to certain embodiments described here and are each incorporated herein by reference in their entirety.
Turning now descriptively to the drawings,
Aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
Computing server device 200 is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computing server device 200 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed data processing environments that include any of the above systems or devices, and the like.
Computing server device 200 may be described in the general context of computer system-executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computing server device 200 may be practiced in distributed data processing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed data processing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.
The components of computing device 200 may include, but are not limited to, one or more processors or processing units 216, a system memory 228, and a bus 218 that couples various system components including system memory 228 to processing unit 216. Bus 218 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.
Computing device 200 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computing device 200, and it includes both volatile and non-volatile media, removable and non-removable media. System memory 228 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 230 and/or cache memory 232. Computing device 200 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 234 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk, and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus 218 by one or more data media interfaces. As will be further depicted and described below, the system memory 228 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
Program/utility 240, having a set (at least one) of program modules 215, such as analyzer module 306 and the profile engine 308 described below, may be stored in the system memory 228 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules 215 generally carry out the functions and/or methodologies of embodiments of the invention as described herein.
Computing server device 200 may also communicate with one or more external devices 214 such as a keyboard, a pointing device, a display 224, etc.; one or more devices that enable a user to interact with computing device 200; and/or any devices (e.g., network card, modem, etc.) that enable computing device 200 to communicate with one or more other computing devices. Such communication can occur via Input/Output (I/O) interfaces 222. Still yet, computing device 200 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 220. As depicted, network adapter 220 communicates with the other components of computing device 200 via bus 218. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computing device 200. Examples, include, but are not limited to microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.
With the exemplary communication network 100 (
Computing server device 103 is preferably configured and operational to receive (capture) data from various sensors 102 regarding certain aspects (including functional and operational) of property 300 (described further below) and transmit that captured data to a management server 106 (remote or installed on site), via the communication network 100. Computing server device 103 may perform analytics regarding the captured sensor data regarding property 300 and/or the remote management server 106 may perform such analytics, as also further described below. In some embodiments, data from sensors 102 may be transmitted directly to the management server 106, via the communication network 100 or any other suitable data transfer means, thus either obviating the need for computing server device 103 or mitigating its functionality to capture all data from sensors 102.
In the illustrated embodiment of
Temperature sensor—configured and operational to preferably detect the temperature present at the property 300. For example, the temperature may rise and fall with the change of seasons and/or the time of day. Moreover, in the event of a fire, the temperature present at the property 300 may rise quickly—possibly to a level of extreme high heat. The temperature sensor may make use of probes placed at various locations in and around the property 300, in order to collect a representative profile of the temperature present at the property 300. These probes may be connected to the computing server device 103 by wire, or by a wireless technology. For example, if the computing server device 103 is positioned in the attic of the property 300, the temperature may be higher than the general temperature present in the property. Thus, probes placed at various locations (e.g., in the basement, on the various levels of a multi-level property 300, in different rooms that receive different amounts of sun, etc.), in order to obtain an accurate picture of the temperature present at the property. Moreover, the computing server device 103 may record both the indoor and outdoor temperature present at the property 300. For example, data regarding the indoor temperature, the outdoor temperature, and/or the differential between indoor and outdoor temperatures, may be used as part of some analysis model, and thus all of the different values could be stored. The computing server device 103 may store an abstract representation of temperature (e.g., the average indoor temperature, as collected at all of the probes), or may store each temperature reading individually so that the individual readings may be provided as input to an analysis model.
Humidity sensor—configured and operational to preferably detect the humidity present at the property 300. Humidity sensor may comprise the humidity-detection hardware, or may employ one or more remote probes, which may be located inside and/or outside the property 300. Humidity readings from one or more locations inside and/or outside the property could thus be recorded by computing server device 103.
Water Sensor(s)/Water pressure sensor(s) —configured and operational to preferably monitor water related conditions, including (but not limited to): the detection of water and water pressure detection, for instance in the plumbing system in the property 300. With regards to a water pressure sensor, it may have one or more probes attached to various locations of the property's 300 plumbing, and thus computing server device 103 may record the pressure present in the plumbing, and/or any changes in that pressure. For example, plumbing systems may be designed to withstand a certain amount of pressure, and if the pressure rises above that amount, the plumbing system may be at risk for leaking, bursting, or other failure. Thus, the computing server device 103 may record the water pressure (and water flow) that is present in the plumbing system at various points in time.
Wind speed sensor—configured and operational to record the wind speed present at the property 300. For example, one or more wind sensors may be placed outside the property 300, at the wind speed and/or direction may be recorded at various points in time. Computing server device 103 may record these wind speed and/or wind direction readings. The wind speed may be used by an analysis model to plan for future losses and/or to make underwriting, pricing, or other decisions.
Motion sensor—configured and operational to sense motion in the property 300 to which motion sensor 102 is attached. Typically, property's 300 do not move significantly, except in the event of a catastrophe. Motion sensor may indicate that the property 300 is sliding down a hill (e.g., in the event of an extreme flood or mudslide), or is experiencing a measurable earthquake. A motion sensor may further include earth sensors for detecting sinkholes and earth movement. In addition, a motion sensor may be configured and operational to sense the motion of objects within the property. In some embodiments, the motion sensor may utilize micro-location technology to detect presence of inhabitants within the property 300. In other embodiments, the motion sensor may use infrared technology to detect heat sources moving within the property 300. For example, the motion sensor 102 may capture an infrared heat map (e.g., capture the infrared radiation) of the property, which may illustrates warm bodies within the property 300.
Electrical system sensor/analyzer configured and operational to assess the condition of the property's 300 electrical system. For example, potentiometers may be connected to various points in the property's 300 electrical system to measure voltage. Readings from the potentiometers could be used to determine if the voltage is persistently too high, or too low, or if the voltage frequently drops and/or spikes. Such conditions may suggest that the property 300 is at risk for fire. Other types of electrical measurements could be taken, such as readings of current flowing through the electrical system. Any type of data about the property's 300 electrical system could be captured by computing server device 103.
Camera Sensor—Camera sensors include visible light cameras, infrared cameras, two-dimensional (2D) cameras, three-dimensional (3D) cameras, thermal cameras, aerial imagery cameras, Smartphone camera images, radar-capable sensors, sensors that detect other wavelengths, and/or any combination thereof. In some embodiments, the camera sensor 102 may capture and transmit low-resolution images of different areas within the property 300 to the computing server device 103 or directly to a third party server. Threes images may be used (in conjunction with facial recognition software and technology) to determine the identity of the inhabitants within the property 300. In some embodiments, the camera may be configured to capture images within a field of vision, which is controllable via instructions received from the management server 106 and/or the computing server device 103.
Structural sensor—configured and operational to preferably detect various structural conditions relating to property 300. A structural sensor may comprise detection hardware, or may employ one or more remote probes, which may be located inside and/or outside the property 300. Conditions recorded by structural sensor may include (but are not limited to) the condition of the wall structure, floor structure, ceiling structure and roof structure of property 300, which may be achieved via: load bearing detectors; components which measure the slope of a floor/wall/ceiling; carpet conditions (e.g., via nano sensor) or any other components functional to detect such conditions. Structural readings from one or more locations inside and/or outside the property 300 could thus be recorded by computing server device 103 and used by an analysis model in various ways.
Environmental Sensor—configured and operational to preferably detect various environmental conditions relating to property 300. An environmental sensor may comprise detection hardware, or may employ one or more remote probes, which may be located inside and/or outside the property 300. Conditions recorded by an environmental sensor may include (but are not limited to) the air quality present in property 300, the presence of mold/bacteria/algae/lead paint or any contaminant adverse to human health (whether airborne or attached to a portion of the structure of property 300). Such environmental readings from one or more locations inside and/or outside the property 300 could thus be recorded by the computing server device 103 and used by an analysis model in various ways.
Appliance Sensor—configured and operational to preferably detect various operating parameters relating to appliances within a property 300. Examples of appliances include (but are not limited to) all kitchen appliances (e.g., refrigerator, freezer, stove, cooktop, oven, grill, dishwasher, etc.); HVAC components (air conditioner, heating system, air handlers, humidifiers/de-humidifiers, etc.), water purification system, media entertainment system (e.g., televisions), networking components (routers, switches, extenders, etc.) electrical generator system, pool filtration and heating system, garage door openers, sump pump and water well system, septic tank system, garage door opener, etc. An appliance sensor may comprise detection hardware, or may employ one or more remote probes, which may be located inside and/or outside the property 300 functional to detect certain operating parameters of appliances. Operating parameters detected by an appliance sensor 102 may include (but are not limited to): the operating efficiency of an appliance (energy usage, output performance); the time an appliance operates, the age of an appliance; maintenance needs of an appliance (e.g., change a filter component or schedule a periodic examination/tune-up); and repair needs of an appliance (which may also include the identification of parts needed). Such appliance readings from one or more property appliances could thus be recorded by the computing server device 103 and used by an analysis model in various ways.
With exemplary sensors 102 identified and briefly described above, and as will be further discussed below, it is to be generally understood that sensors 102 preferably record certain data parameters relating to the condition data of a property. It is to be understood and appreciated the aforementioned sensors 102 may be configured as wired and wireless types integrated in a networked environment (e.g., WAN, LAN, WiFi, 802.11X, 3G, LTE, etc.), which may also have an associated IP address. It is to be further appreciated the sensors 102 may consist of internal sensors located within the structure of the property 300; external sensors located external of the structure of the property 300; sound sensors for detecting ambient noise (e.g., for detecting termite and rodent activity, glass breakage, intruders, etc.); camera sensors such as those consisting of camera standalone devices, or by integrating into existing camera devices in the property 300. It is additionally to be understood and appreciated that sensors 102 can be networked into a central computer hub (e.g., the computing server device 103) in a property to aggregate and/or encrypt collected sensor data packets. Aggregated and/or encrypted data packets can be analyzed either in a computer system (e.g., computing server device 103) or via an external computer environment (e.g., management server 106). Additionally, it is to be understood that data packets collected from sensors 102 can be aggregated and/or encrypted in computing server device 103 and sent as an aggregated and/or encrypted packet to the management server 106 for subsequent analysis whereby data packets may be transmitted at prescribed time intervals (e.g., a benefit is to reduce cellular charges in that some property 300 may not have Internet access or cellular service is backup when property Internet service is nonfunctioning).
In accordance with an illustrated embodiment, in addition to the aforementioned, the sensors 102 being utilized relative to property 300, computing server device 103 may additionally be coupled to a Clock 320 (e.g., timer), which may keep track of time for the computing server device 103, thereby allowing a given item of data to be associated with the time at which the data was captured. For example, the computing server device 103 may recurrently capture readings of temperature, wind speed, humidity, appliance operating times, etc., and may timestamp each reading. The time at which the readings are taken may be used to reconstruct events or for other analytic purposes, such as those described below. For example, the timestamps on wall structure readings taken by a structural sensor during a hurricane may allow it to be determined, after the hurricane has occurred, if the property is in need of immediate repair.
A storage component 322 may further be provided and utilized to store data readings and/or timestamps in the computing server device 103. For example, storage component 322 may comprise, or may otherwise make use of, magnetic or optical disks, volatile random-access memory, non-volatile random-access-memory, or any other type of storage device. There may be sufficient data storage capacity to store data generated as a result of several hours or several days of readings. For example, a plurality of water flow sensors 102 might be measuring and recording the amount of water flowing through each of the faucets/showerheads in a property 300. Storage component 322 might have sufficient storage capacity to allow, for example, five days of readings to be stored, thereby allowing determining daily water consumption pattern.
A communication component 324 may further be provided and utilized to communicate recorded information from computing server device 103 to an external location, such as computer management server 106. Communication component 324 may be, or may comprise, a network communication card such as an Ethernet card, a Wi-Fi card, or any other communication mechanism. However, communication component 324 could take any form and is not limited to these examples. Communication component 324 might encrypt data that it communicates, in order to protect the security and/or privacy of the data. Communication component 324 may communicate data recorded by the computing server device 103 (e.g., data stored in storage component 322) to an external location, such as management server 106. For example, management server 106 may collect data from computing server device 103 in order to learn about habits, trends and other analytics relative to property 300 in which the computing server device 103 located. Communication component 324 may initiate communication sessions with management server 106. Additionally or alternatively, the management server 106 may contact computing server device 103, through communication component 324, in order to receive data that has been stored by the computing server device 103 or command a functionally behavior modification for any sensor 102.
Management server 106 may further include a command generation engine. The command generation engine may send commands to sensors 102 or to the computing server device 103 to be sent to the sensors 102 at predefined times. Such commands may include, for exemplary purposes only and without limitation, an instruction to take an immediate reading, an instruction to take a series of readings (e.g., every five minutes for one hour, every minute for one week), an instruction to take more frequent readings (e.g., every hour rather than every six hours), an instruction to take less frequent readings (e.g., every day rather than every hour), and/or any permutations or derivations thereof, such as any modification to a frequency of data capture associated with any sensor 102.
In some embodiments, the data packets received by the management server 106 may be immediately analyzed and then discarded. In some embodiments, the data packets may be analyzed and stored temporarily. For example, the management server 106 may transmit and store the captured data into an internal or an external database. The management server 106 may also utilize specific memory components (such as cache) for different types of data captured. The data packets may be temporarily stored in the cache, whereby the management server 106 deletes the oldest data and adds the newest data. The cache may store the data until the management server 106 determines whether to delete some or all of the cache data or move some or all of the data to a different memory. For example, the management server 106 may store data associated with the motion sensor 102 in a memory structure that offers faster retrieval (e.g., cache) and store other captured data (e.g., electricity voltage reading when the electricity voltage does not have an unexpected surge or decrease and does not indicate an electrical problem) in a conventional memory (e.g., conventional database, which may be internal or external and does not offer a faster data retrieval option). In yet another embodiment, the data packets received, may be stored by the management server 106 for later analysis. In addition, in still another embodiment, the information is stored via another device/module/engine. The management server 106 may then determine and update one or more data records associated with the property 300 in a database to reflect the determined conditions of the structure. In some embodiments, the management server 106 may only store a portion of the data captured. For example, the management server 106 may discard any captured data that is deemed “normal” (e.g., does not indicate a risk to the dwelling) and satisfies a time threshold (e.g., one year, one month, or any other pre-determined time threshold). Because the volume of data captured by multiple sensors may become very large, the management server 106 may utilize the above-mentioned methods to manage memory space and increase the efficiency of data collection, retrieval, and analysis.
Additionally, data from sensors 102, clock 320 and/or storage component 322 may be communicated directly to management server 106, via the communication network 100, thus obviating or mitigating the need for computing server device 103. In the example of
Management server 106 may further include profile engine 308. The inhabitant profile engine 308 may analyze the data such as described above with respect to different sensors 102. The profile engine 308 may also generate an inhabitant dataset and continuously monitor the building condition data received to generate thresholds used by the computing server device 103. For example, the profile engine 308 may monitor water usage of the property and determine that the water usage is typically higher when a particular inhabitant is present in the property 300. As described below, the computing server device 103 or the management server 106 may generate a dynamic threshold for different building condition data (e.g., water usage, electricity, and the like) based on the inhabitant's habits.
Referring now to
As described above, each home sensor is configured to directly communicate with the management server 106 or, in some embodiments, communicate with the management server 106 through the computing server device 103. In some embodiments, each home sensor is wirelessly (or using LAN) connected with the property computing device 300, which may receive, aggregate, encrypt and/or store data before transmitting the data captured from the home sensors to the management server 106 using a wireless network such as the communication network 100 (described in detail in
In addition to the home sensors described above, the management server 106 may also use beacons to detect the presence (or location of) one or more inhabitants within the property 400. For example, the beacon 422 may be a hardware transmitter and a communication device, which communicates with electronic devices such as the mobile device of the inhabitants within the property. The beacon 422, in some embodiments, may utilize Bluetooth low energy (BLE) transmission technology to communicate with electronic devices within a pre-determined proximity zone, such as the proximity zone represented by the geo-fence 423. The beacon 422 may broadcast an identifier to nearby portable electronic devices located within the geo-fence 423, such as the mobile device of the inhabitants of the property. In an embodiment, geo-fence 423 represents the range of transmission of identifier by the beacon 422. For example, the beacon 422 may be instructed (by the management server 106) to transmit identifiers within a radius of 10 feet (within the geo-fence 423).
In some embodiments, the beacon 422 may transmit a Universally Unique Identifier (UUID) as an identifier. A UUID is a 128-bit value identifier used in software construction. The beacon 422 may also receive UUID of the mobile device of the inhabitant of the property and transmit said UUID to the management server 106. The management server 106, may then, transmit said UUID and query a database for any information associated with said UUID and the mobile device transmitting the UUID. For example, the database may transmit identifying information (e.g., profile data) associated with the mobile device transmitting the UUID to the management server 106. The management server may then (matching the UUID for the property 400 and the identifying information received from the database) determine a location associated with the inhabitant of the room.
For example, beacon 422 may broadcast a UUID of 12345X within the geo-fence 423. Upon an inhabitant entering the geo-fence 423, his mobile device receives the UUID and transmits (using an application executing on the mobile device that is associated with the management server 106) the UUID to the management server 106. The management server 106 may then match the UUID received and determine that the UUID received matches the UUID of beacon 422. The management server 106 may then further determine that the mobile device transmitting the UUID of beacon 422 is associated with John Smith (using a unique electronic identifier associated with the mobile device). The management server 106 may then determine that John Smith in in bedroom 420.
With reference to
In an embodiment, this step may involve the computing device periodically contacting (via the communication network 100 or any other suitable means), at prescribed time intervals, the management server to send data collected by a plurality of motion sensors. A variety of motion sensors are preferably installed at various points around the property, such as in the living room, bedroom, kitchen, and bathroom. The sensors are arranged to communicate with the computing device, which, for example, may be located in a hallway near a main entrance of the property. The one or more motion sensors may be configured and operational to monitor movement of property inhabitants in different areas of the property. In an embodiment, motion sensors may comprise passive infrared detectors. Upon receiving the data packets from the motions sensors, the management server may determine, for example, whether the property was occupied by more than one inhabitant by detecting substantially simultaneous motion patterns at various points around the property. As described below, the management server may analyze the data received from one or more motion sensors to identify the inhabitant.
At 504, the management server preferably processes the informatics data collected by a plurality of motion sensors to determine daily rest-activity pattern for each inhabitant. For example, the management server may estimate rest-activity parameters such as bedtime, rise time, sleep latency, and naptime for one or more inhabitants of the property by combining data from multiple sensors located around the property. As another example, the management server may be configured to determine whether the property remains unoccupied for an extended period of time. This information may be used by the management server (e.g., the profile engine) to refine a habit profile associated with the property and with each inhabitant of the property.
At 506, based on data collected from different sensors installed on the property, the management server preferably conducts an analysis to determine daily cooking activity pattern of one or more property inhabitants. In an embodiment, one or more appliance sensors may be employed to measure the use of cooking appliances such as a kettle, a microwave oven or an electric cooker. For example, the management server may detect the cooking time trends by detecting that a rice cooker or microwave oven is turned on/off, detecting that a gas range or an IH (Induction-Heating) cooking heater is turned on/off or detecting other cooking home electric appliances are turned on/off. As another example, the management server may combine data collected from various types of sensors, such as motion and appliance sensors, to determine, for instance, whether any of the cooking appliances remain unattended for an extended period of time, thus increasing the risk of fire. The daily cooking activity tracking may be adaptive. In other words, the management server may gradually adjust to the inhabitant's new activities and/or habits if they change over time. In general, the management server may assess the risk of fires or other events arising from various activities of inhabitants of a property or location and/or observed events and use this information to provide targeted specific advice and guidance at the property to reduce the chance of fires or other events arising from the activities.
At 508, the management server conducts an analysis to determine daily water consumption pattern. For example, based upon analysis of a plumbing system, the management server may have detected long-term stress on pipes and may predict future plumbing leaks. In order to prevent water leaks, the management server may recommend reducing water pressure (e.g., by installing a water softener). Property inhabitants' behavior patterns during a storm can also increase the risk of flooding. For example, a combination of washing clothes, taking a shower, and running the dishwasher could add water to a system that may already be overloaded. The water may have nowhere to go but into the basement of the property. Thus, the management server may identify certain water consumption patterns of property inhabitants as hazardous and use this information to provide targeted specific advice and guidance to reduce the risk of water losses at the property.
Similarly, at 510, the management server preferably performs an analysis to determine daily energy consumption pattern. For example, based upon analysis of the property's electrical system, the management server may have detected the load pattern and energy amount are different in weekdays and weekends. For instance, during the weekday the minimum load may occur between 2:00 and 6:00 in the morning when most of property occupants are sleeping and morning peak may be between approximately 7:00 AM and 10:00 AM, while the night peak may occur between approximately 7:00 PM and midnight when the property inhabitants are at home, making dinner and using the entertainment appliances. On weekends, there might be a mid-day peak load between approximately 10:00 AM and 03:00 PM, while night peak may occur between approximately 07:00 PM and 10:00 PM. In addition, in this step, the management server may flag certain energy consumption patterns of inhabitants as hazardous.
Thus, in steps 502-510, the management server collects various characteristics indicative of habits and activities of the property's inhabitants. At 512, the management server preferably transmits these characteristics to the profile engine. In an embodiment, the property's inhabitants' habits and characteristics may include, but not limited to, daily water consumption and energy consumption patterns, daily cooking activity pattern, number of inhabitants, hazardous activities pattern, and the like. In an alternative embodiment, the management server may store these habits and characteristics in a local or remote database. The readings of the amount of energy/water used at the property can be used to analyze and forecast an expected energy/water bill. This can also be used for budgeting and finance management because a history of energy/water usage at the property or certain appliances can be measured and displayed to the inhabitants. Additionally, the homeowner can track energy/water use and determine based upon the rate of energy consumption that the homeowner is on a pace to use more or less energy/water use than is budgeted. In addition to generating a profile for the property, the management server may also generate a habit profile for each inhabitant of the property. This individual profile is also adaptive and may be refined by the management server over time.
Referring now to
As described in
At 604, the management server may identify one or more inhabitants within the property. The management server may receive a set of data from the motions sensor and the camera sensor and identify one or more inhabitants based on the data packets received from each sensor. For example, the motion sensor may detect heat emitting from bodies within the properties (using infrared technology) and transmit heat maps of warm bodies within the property to the management server. The management server may determine the identities of the inhabitants by comparing the heat map with an existing profile of the inhabitants. For example, the management server may retrieve data associated with each inhabitant of the property (e.g., height, weight, image of each inhabitant, and the like) from the inhabitants (e.g., inhabitants may log into a graphical user interface, such as a website, and input the above-mentioned data). The management server may then identify the inhabitants based on the heat map received from the motion sensors. For example, when a heat map received from the motion sensor indicates that a person of 6′2″ height is present in the property; the management server may query a database, receive a profile of all inhabitants of the property, and determine that the father's height is 6′2″. The management server may then determine that the father is present in the property.
In some other embodiments, the camera sensor may periodically capture images (e.g., low-resolution images) from the property. The camera sensor may transmit the captured images to the management server, which may then use facial recognition techniques to identify the inhabitants present within the property. For example, the management server may identify that the image captured within the living room resembles an image of the father by comparing the received image with an image of the father stored within the property profile, as described above. In some embodiments, the management server may transmit the images received from the camera sensor to a third-party server (e.g., cloud computing device associated with a third party) that is configured to perform facial recognition and transmit the results to the management server.
In some embodiments, the management server may utilize both the motion sensor and the camera sensor to identify the inhabitants present within the property. For example, when the management server receives an indication (from the motion sensor) that a person is present within the property, the management server may generate and transmit an instruction to the camera sensor to modify its data capture frequency and immediately capture an image of different areas within the property. The management server may then perform facial recognition on the received images and identify the inhabitant present. In some embodiments, the management server may also command the camera sensor to capture an image from a specific part of the property. For example, if the motion sensor captures movement (or heat) associated with a person within the living room, the management sensor may command the camera sensor to only capture images from the living room. In some other embodiments, the management server may also modify the field of vision associated with the camera sensor in order to receive an image of the inhabitants present within the property.
The management server may also activate, reconfigure, or modify the functional behavior of the motion sensor based on data packets received from the camera sensor. For example, the management sensor may receive an image from the camera sensor that indicates presence of an inhabitant within the living room. If the management server is unable to identify the inhabitant (e.g., if the facial recognition fails), the management server may activate the motion sensor and (as described above) command the motion sensor to modify its functional behavior (e.g., frequency of data capture) and capture a heat map of the property. The management server may also modify the motion sensor's field of vision and command a heat/motion capture associated with a specific area within the property. The management server may then use the data received from the camera sensor and the motion sensor to identify the inhabitant present.
In some embodiments, the management server may use micro location and beacon technology to identify one or more inhabitants present within the property. As described above, the management server may also use a location-aware mobile device associated with an inhabitant of the property (e.g., mobile device) to identify a location of the inhabitants within the property.
At step 606, the management server may modify one or more environmental sensors based on the inhabitant's profile. The management server may generate and transmit an instruction to one or more environmental sensors/devices to comply with the inhabitant's profile. In a non-limiting example, the management sever may first determine that the father is the only person present within the property and the father has a temperature preference of 74 degrees; the management server may then reconfigure a thermostat within the property to 74 degrees. In another example, the management server may automatically shut the blinds, turn on or off the humidifier, or modify (e.g., turn on or off) the lighting within the property (e.g., in certain areas of the property based on the father's preferences).
In some embodiments, the management server may use predetermined rules to generate the instruction for the one or more environmental sensors. For example, in an embodiment, the management server may determine that two inhabitants are present within the property (e.g., father and his son). Consequently, the management server may query a set of preexisting rules to determine that when the father and son are both present within the property, the environmental settings may be modified based on the father's environmental preferences. The set of predetermined rules may be inputted by the inhabitants or may be monitored and determined by the management server (e.g., based on previous data received from different sensors). For example, the father may add the above-mentioned rule to the property profile. Additionally or alternatively, the management server may determine that when the father and son are both present within the property, the environmental building condition data (received from the temperature sensor) is consistent with the father environmental preferences. Consequently, the management server may generate a rule that allows the environmental conditions to be modified based on the father's environmental preferences when the father and son are both present within the property.
At step 608, the management server may also modify an entertainment system associated with the property in accordance with the inhabitant's preferences. As described above, the management server may generate an instruction to play the identified inhabitant's favorite music or radio program. The management server may transmit the instruction to any home entertainment devices within the property. For example, when the father arrives, the management server may instruct a radio to play the father's favorite radio channel. In other embodiments, when the management server detects presence of a young adult within the property, the management server may prevent any adult rated television programs to be played. In some embodiments, the management server may directly contact the home entertainment devices. For example, the home entertainment devices may be connected to a home network using a wireless router (e.g., home wireless router 401 described in
Referring now to
At step 708, the management server may transmit an electronic notification to an electronic device associated with at least one inhabitant present within the property based on the maintenance needs identified and the inhabitant's profile data. The management server may identify one or more inhabitants who have indicated a desire to receive maintenance alerts. In a non-limiting example, and as described above, an inhabitant may indicate a desire to receive maintenance alerts on his/her profile. For example, the property profile may indicate the father and the mother of the family as available to receive alerts regarding maintenance needs and requirements. Consequently, the management server may only notify the father and mother (and not the children) when a maintenance need arises.
Upon identifying the right party, the management server may retrieve an electronic identifier associated with an electronic device of the father and/or mother (e.g., query a database to identify a phone number or email address of the father or mother). The management server may then transmit an electronic notification to the electronic device associated with the designated inhabitants. The notification may be in form of a text, email, push notification, and the like. The notification may include identification of the appliance, maintenance requirements, and/or a hyperlink directing the inhabitants to the footage of the appliance (captured from the camera sensor). Furthermore, the management server may also notify a third party (e.g., a third party computing device such as a home security, maintenance service, pest control, insurance company, or an emergency service).
In some embodiments, the management server may notify an inhabitant when the inhabitant is within a predetermined proximity to the appliance in need of maintenance. For example, the management server may identify water leakage in a bathroom. In a non-limiting example, and in conjunction with the illustrated embodiment in
The various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
Embodiments implemented in computer software may be implemented in software, firmware, middleware, microcode, hardware description languages, or any combination thereof. A code segment or machine-executable instructions may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.
The actual software code or specialized control hardware used to implement these systems and methods is not limiting of the invention. Thus, the operation and behavior of the systems and methods were described without reference to the specific software code being understood that software and control hardware can be designed to implement the systems and methods based on the description herein.
When implemented in software, the functions may be stored as one or more instructions or code on a non-transitory computer-readable or processor-readable storage medium. The steps of a method or algorithm disclosed herein may be embodied in a processor-executable software module, which may reside on a computer-readable or processor-readable storage medium. A non-transitory computer-readable or processor-readable media includes both computer storage media and tangible storage media that facilitate transfer of a computer program from one place to another. A non-transitory processor-readable storage media may be any available media that may be accessed by a computer. By way of example, and not limitation, such non-transitory processor-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other tangible storage medium that may be used to store desired program code in the form of instructions or data structures and that may be accessed by a computer or processor. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a non-transitory processor-readable medium and/or computer-readable medium, which may be incorporated into a computer program product.
The preceding description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the following claims and the principles and novel features disclosed herein.
While various aspects and embodiments have been disclosed, other aspects and embodiments are contemplated. The various aspects and embodiments disclosed are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims.
The term “module”/“engine” is used herein to denote a functional operation that may be embodied either as a stand-alone component or as an integrated configuration of a plurality of subordinate components. Thus, “modules”/“engines” may be implemented as a single module or as a plurality of modules that operate in cooperation with one another. Moreover, although “modules”/“engines” may be described herein as being implemented as software, they could be implemented in any of hardware (e.g. electronic circuitry), firmware, software, or a combination thereof.
With certain illustrated embodiments described above, it is to be appreciated that various non-limiting embodiments described herein may be used separately, combined or selectively combined for specific applications. Further, some of the various features of the above non-limiting embodiments may be used without the corresponding use of other described features. The foregoing description should therefore be considered as merely illustrative of the principles, teachings and exemplary embodiments of this invention, and not in limitation thereof.
It is to be understood that the above-described arrangements are only illustrative of the application of the principles of the illustrated embodiments. Numerous modifications and alternative arrangements may be devised by those skilled in the art without departing from the scope of the illustrated embodiments, and the appended claims are intended to cover such modifications and arrangements.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Although any methods and materials similar or equivalent to those described herein can also be used in the practice or testing of the illustrated embodiments, exemplary methods and materials are now described. All publications mentioned herein are incorporated herein by reference to disclose and describe the methods and/or materials in connection with which the publications are cited.
This application is a Continuation-in-Part of U.S. patent application Ser. No. 15/724,103, filed on Oct. 3, 2017, which is a Continuation Application of U.S. patent application Ser. No. 14/303,382, filed Jun. 12, 2014, which claims priority to U.S. Provisional Patent Application Ser. Nos.: 61/926,093 filed Jan. 10, 2014; 61/926,091 filed Jan. 10, 2014; 61/926,095 filed Jan. 10, 2014; 61/926,098 filed Jan. 10, 2014; 61/926,103 filed Jan. 10, 2014; 61/926,108 filed Jan. 10, 2014; 61/926,111 filed Jan. 10, 2014; 61/926,114 filed Jan. 10, 2014; 61/926,118 filed Jan. 10, 2014; 61/926,119 filed Jan. 10, 2014; 61/926,121 filed Jan. 10, 2014; 61/926,123 filed Jan. 10, 2014; 61/926,536 filed Jan. 13, 2014; 61/926,541 filed Jan. 13, 2014; 61/926,534 filed Jan. 13, 2014; 61/926,532 filed Jan. 13, 2014; 61/943,897 filed Feb. 24, 2014; 61/943,901 filed Feb. 24, 2014; 61/943,906 filed Feb. 24, 2014; and 61/948,192 filed Mar. 5, 2014, all of which are incorporated herein by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
4247757 | Crump, Jr. | Jan 1981 | A |
5182705 | Barr et al. | Jan 1993 | A |
5235507 | Sackler et al. | Aug 1993 | A |
5325291 | Garrett et al. | Jun 1994 | A |
5526609 | Lee et al. | Jun 1996 | A |
5724261 | Denny et al. | Mar 1998 | A |
5950169 | Borghesi et al. | Sep 1999 | A |
5960338 | Foti | Sep 1999 | A |
5991733 | Aleia et al. | Nov 1999 | A |
6029141 | Bezos et al. | Feb 2000 | A |
6049773 | McCormack et al. | Apr 2000 | A |
6141686 | Jackowski et al. | Oct 2000 | A |
6526807 | Doumit et al. | Mar 2003 | B1 |
6686838 | Rezvani et al. | Feb 2004 | B1 |
6766322 | Bell | Jul 2004 | B1 |
6826607 | Gelvin et al. | Nov 2004 | B1 |
6985907 | Zambo et al. | Jan 2006 | B2 |
7015789 | Helgeson | Mar 2006 | B1 |
7138914 | Culpepper et al. | Nov 2006 | B2 |
7142099 | Ross et al. | Nov 2006 | B2 |
7170418 | Rose-Pehrsson et al. | Jan 2007 | B2 |
7203654 | Menendez | Apr 2007 | B2 |
7398218 | Bemaski et al. | Jul 2008 | B1 |
7406436 | Reisman | Jul 2008 | B1 |
7602196 | Vokey | Oct 2009 | B2 |
7610210 | Helitzer et al. | Oct 2009 | B2 |
7624031 | Simpson et al. | Nov 2009 | B2 |
7624069 | Padgette | Nov 2009 | B2 |
7711584 | Helitzer et al. | May 2010 | B2 |
7716076 | Block et al. | May 2010 | B1 |
7739133 | Hail et al. | Jun 2010 | B1 |
7809587 | Dorai et al. | Oct 2010 | B2 |
7869944 | Deaton et al. | Jan 2011 | B2 |
7885831 | Burton et al. | Feb 2011 | B2 |
7899560 | Eck | Mar 2011 | B2 |
7937437 | Fujii | May 2011 | B2 |
7945497 | Kenefick et al. | May 2011 | B2 |
7949548 | Mathai et al. | May 2011 | B2 |
7958184 | Barsness et al. | Jun 2011 | B2 |
7969296 | Stell | Jun 2011 | B1 |
8004404 | Izumi et al. | Aug 2011 | B2 |
8041636 | Hunter et al. | Oct 2011 | B1 |
8046243 | Winkler | Oct 2011 | B2 |
8069181 | Krishnan et al. | Nov 2011 | B1 |
8081795 | Brown | Dec 2011 | B2 |
8086523 | Palmer | Dec 2011 | B1 |
8090598 | Bauer et al. | Jan 2012 | B2 |
8095394 | Nowak et al. | Jan 2012 | B2 |
8103527 | Lasalle et al. | Jan 2012 | B1 |
8106769 | Maroney et al. | Jan 2012 | B1 |
8229767 | Birchall | Jul 2012 | B2 |
8249968 | Oldham et al. | Aug 2012 | B1 |
8265963 | Hanson et al. | Sep 2012 | B1 |
8271303 | Helitzer et al. | Sep 2012 | B2 |
8271308 | Winkler | Sep 2012 | B2 |
8271321 | Kestenbaum | Sep 2012 | B1 |
8289160 | Billman | Oct 2012 | B1 |
8294567 | Stell | Oct 2012 | B1 |
8306258 | Brown | Nov 2012 | B2 |
8332242 | Medina, III | Dec 2012 | B1 |
8332348 | Avery | Dec 2012 | B1 |
8384538 | Breed | Feb 2013 | B2 |
8400299 | Maroney et al. | Mar 2013 | B1 |
8428972 | Noles et al. | Apr 2013 | B1 |
8452678 | Feldman et al. | May 2013 | B2 |
8510196 | Brandmaier et al. | Aug 2013 | B1 |
8515788 | Tracy et al. | Aug 2013 | B2 |
8521542 | Stotts | Aug 2013 | B1 |
8527306 | Reeser et al. | Sep 2013 | B1 |
8600104 | Brown | Dec 2013 | B2 |
8635091 | Amigo et al. | Jan 2014 | B2 |
8638228 | Amigo et al. | Jan 2014 | B2 |
8650048 | Hopkins, III et al. | Feb 2014 | B1 |
8676612 | Helitzer et al. | Mar 2014 | B2 |
8719061 | Birchall | May 2014 | B2 |
8731975 | English et al. | May 2014 | B2 |
8760285 | Billman et al. | Jun 2014 | B2 |
8774525 | Pershing | Jul 2014 | B2 |
8782395 | Ly | Jul 2014 | B1 |
8788299 | Medina, III | Jul 2014 | B1 |
8788301 | Marlow et al. | Jul 2014 | B1 |
8799034 | Brandmaier et al. | Aug 2014 | B1 |
8812414 | Arthur et al. | Aug 2014 | B2 |
8813065 | Zygmuntowicz et al. | Aug 2014 | B2 |
8868541 | Lin et al. | Oct 2014 | B2 |
8872818 | Freeman et al. | Oct 2014 | B2 |
8910298 | Gettings et al. | Dec 2014 | B2 |
8924241 | Grosso | Dec 2014 | B2 |
8930581 | Anton et al. | Jan 2015 | B2 |
9015238 | Anton et al. | Apr 2015 | B1 |
9049168 | Jacob et al. | Jun 2015 | B2 |
9053516 | Stempora | Jun 2015 | B2 |
9082015 | Christopulos et al. | Jul 2015 | B2 |
9141995 | Brinkmann et al. | Sep 2015 | B1 |
9158869 | Labrie et al. | Oct 2015 | B2 |
9165084 | Isberg et al. | Oct 2015 | B2 |
9183560 | Abelow | Nov 2015 | B2 |
9252980 | Raman | Feb 2016 | B2 |
9311676 | Helitzer et al. | Apr 2016 | B2 |
9330550 | Zribi et al. | May 2016 | B2 |
9363322 | Anton et al. | Jun 2016 | B1 |
9454907 | Hafeez et al. | Sep 2016 | B2 |
9460471 | Bernard et al. | Oct 2016 | B2 |
9481459 | Staskevich et al. | Nov 2016 | B2 |
9611038 | Dahlstrom | Apr 2017 | B2 |
9613523 | Davidson et al. | Apr 2017 | B2 |
9652805 | Clawson, II et al. | May 2017 | B1 |
9665074 | Lentzitzky | May 2017 | B2 |
9710858 | Devereaux et al. | Jul 2017 | B1 |
9747571 | Ballew et al. | Aug 2017 | B2 |
9754325 | Konrardy et al. | Sep 2017 | B1 |
9792656 | Konrardy et al. | Oct 2017 | B1 |
9811862 | Allen et al. | Nov 2017 | B1 |
9818158 | Devereaux et al. | Nov 2017 | B1 |
9842310 | Lekas | Dec 2017 | B2 |
9886723 | Devereaux et al. | Feb 2018 | B1 |
9892463 | Hakimi-Boushehri et al. | Feb 2018 | B1 |
9915438 | Cheatham, III | Mar 2018 | B2 |
9934675 | Coyne et al. | Apr 2018 | B2 |
9947051 | Allen et al. | Apr 2018 | B1 |
9959581 | Pershing | May 2018 | B2 |
9984417 | Allen et al. | May 2018 | B1 |
10032224 | Helitzer et al. | Jul 2018 | B2 |
10055793 | Call et al. | Aug 2018 | B1 |
10055794 | Konrardy et al. | Aug 2018 | B1 |
10121207 | Devereaux et al. | Nov 2018 | B1 |
10163162 | Devereaux et al. | Dec 2018 | B1 |
10181159 | Allen et al. | Jan 2019 | B1 |
20020007289 | Malin et al. | Jan 2002 | A1 |
20020032586 | Joao | Mar 2002 | A1 |
20020035528 | Simpson et al. | Mar 2002 | A1 |
20020049618 | McClure et al. | Apr 2002 | A1 |
20020055861 | King et al. | May 2002 | A1 |
20020087364 | Lerner et al. | Jul 2002 | A1 |
20020103622 | Burge | Aug 2002 | A1 |
20020111835 | Hele et al. | Aug 2002 | A1 |
20020116254 | Stein et al. | Aug 2002 | A1 |
20020129001 | Levkoff et al. | Sep 2002 | A1 |
20020178033 | Yoshioka et al. | Nov 2002 | A1 |
20030040934 | Skidmore et al. | Feb 2003 | A1 |
20030078816 | Filep | Apr 2003 | A1 |
20030097335 | Moskowitz et al. | May 2003 | A1 |
20030182441 | Andrew et al. | Sep 2003 | A1 |
20040019507 | Yaruss et al. | Jan 2004 | A1 |
20040034657 | Zambo et al. | Feb 2004 | A1 |
20040039586 | Garvey et al. | Feb 2004 | A1 |
20040046033 | Kolodziej et al. | Mar 2004 | A1 |
20040064345 | Ajamian et al. | Apr 2004 | A1 |
20040172304 | Joao | Sep 2004 | A1 |
20040181621 | Mathur et al. | Sep 2004 | A1 |
20040260406 | Ljunggren et al. | Dec 2004 | A1 |
20050050017 | Ross et al. | Mar 2005 | A1 |
20050055248 | Helitzer et al. | Mar 2005 | A1 |
20050055249 | Helitzer et al. | Mar 2005 | A1 |
20050057365 | Qualey | Mar 2005 | A1 |
20050128074 | Culpepper et al. | Jun 2005 | A1 |
20050197847 | Smith | Sep 2005 | A1 |
20050226273 | Qian | Oct 2005 | A1 |
20050251427 | Dorai et al. | Nov 2005 | A1 |
20050278082 | Weekes | Dec 2005 | A1 |
20060017558 | Albert et al. | Jan 2006 | A1 |
20060026044 | Smith | Feb 2006 | A1 |
20060052905 | Pfingsten et al. | Mar 2006 | A1 |
20060111874 | Curtis et al. | May 2006 | A1 |
20060161450 | Carey et al. | Jul 2006 | A1 |
20060200008 | Moore-Ede | Sep 2006 | A1 |
20060218018 | Schmitt | Sep 2006 | A1 |
20060219705 | Beier et al. | Oct 2006 | A1 |
20060229923 | Adi et al. | Oct 2006 | A1 |
20060235611 | Deaton et al. | Oct 2006 | A1 |
20070005400 | Eggenberger et al. | Jan 2007 | A1 |
20070005404 | Raz et al. | Jan 2007 | A1 |
20070043803 | Whitehouse et al. | Feb 2007 | A1 |
20070088579 | Richards | Apr 2007 | A1 |
20070100669 | Wargin et al. | May 2007 | A1 |
20070118399 | Avinash et al. | May 2007 | A1 |
20070136078 | Plante | Jun 2007 | A1 |
20070150319 | Menendez | Jun 2007 | A1 |
20070156463 | Burton et al. | Jul 2007 | A1 |
20070161940 | Blanchard et al. | Jul 2007 | A1 |
20070174467 | Ballou et al. | Jul 2007 | A1 |
20070214023 | Mathai et al. | Sep 2007 | A1 |
20070282639 | Leszuk et al. | Dec 2007 | A1 |
20070299677 | Maertz | Dec 2007 | A1 |
20080033847 | McIntosh | Feb 2008 | A1 |
20080052134 | Nowak et al. | Feb 2008 | A1 |
20080062258 | Bentkovski | Mar 2008 | A1 |
20080065427 | Helitzer et al. | Mar 2008 | A1 |
20080077451 | Anthony et al. | Mar 2008 | A1 |
20080086320 | Ballew et al. | Apr 2008 | A1 |
20080114655 | Skidmore | May 2008 | A1 |
20080140857 | Conner et al. | Jun 2008 | A1 |
20080154651 | Kenefick et al. | Jun 2008 | A1 |
20080154686 | Vicino | Jun 2008 | A1 |
20080154851 | Jean | Jun 2008 | A1 |
20080154886 | Podowski et al. | Jun 2008 | A1 |
20080164769 | Eck | Jul 2008 | A1 |
20080243558 | Gupte | Oct 2008 | A1 |
20080244329 | Shinbo et al. | Oct 2008 | A1 |
20080282817 | Breed | Nov 2008 | A1 |
20080306799 | Sopko, III et al. | Dec 2008 | A1 |
20080307104 | Amini et al. | Dec 2008 | A1 |
20080319787 | Stivoric et al. | Dec 2008 | A1 |
20090006175 | Maertz | Jan 2009 | A1 |
20090024420 | Winkler | Jan 2009 | A1 |
20090031175 | Aggarwal et al. | Jan 2009 | A1 |
20090109037 | Farmer | Apr 2009 | A1 |
20090119132 | Bolano et al. | May 2009 | A1 |
20090135009 | Little et al. | May 2009 | A1 |
20090177500 | Swahn | Jul 2009 | A1 |
20090188202 | Vokey | Jul 2009 | A1 |
20090205054 | Blotenberg et al. | Aug 2009 | A1 |
20090216349 | Kwon et al. | Aug 2009 | A1 |
20090240531 | Hilborn | Sep 2009 | A1 |
20090240550 | McCarty | Sep 2009 | A1 |
20090265193 | Collins et al. | Oct 2009 | A1 |
20090265207 | Johnson | Oct 2009 | A1 |
20090266565 | Char | Oct 2009 | A1 |
20090279734 | Brown | Nov 2009 | A1 |
20090287509 | Basak et al. | Nov 2009 | A1 |
20100030586 | Taylor et al. | Feb 2010 | A1 |
20100049552 | Fini et al. | Feb 2010 | A1 |
20100131300 | Collopy et al. | May 2010 | A1 |
20100131307 | Collopy et al. | May 2010 | A1 |
20100174566 | Helitzer et al. | Jul 2010 | A1 |
20100241464 | Amigo et al. | Sep 2010 | A1 |
20100274590 | Compangano et al. | Oct 2010 | A1 |
20100274859 | Bucuk | Oct 2010 | A1 |
20100299161 | Burdick et al. | Nov 2010 | A1 |
20100299162 | Kwan | Nov 2010 | A1 |
20110043958 | Nakamura et al. | Feb 2011 | A1 |
20110061697 | Behrenbruch et al. | Mar 2011 | A1 |
20110112848 | Beraja et al. | May 2011 | A1 |
20110137684 | Peak et al. | Jun 2011 | A1 |
20110137685 | Tracy et al. | Jun 2011 | A1 |
20110137885 | Isberg et al. | Jun 2011 | A1 |
20110161117 | Busque et al. | Jun 2011 | A1 |
20110161119 | Collins | Jun 2011 | A1 |
20110295624 | Chapin et al. | Dec 2011 | A1 |
20110320226 | Graziano et al. | Dec 2011 | A1 |
20120004935 | Winkler | Jan 2012 | A1 |
20120016695 | Bernard et al. | Jan 2012 | A1 |
20120022897 | Shafer | Jan 2012 | A1 |
20120025994 | Morris | Feb 2012 | A1 |
20120028635 | Borg et al. | Feb 2012 | A1 |
20120028835 | Wild et al. | Feb 2012 | A1 |
20120046975 | Stolze | Feb 2012 | A1 |
20120072240 | Grosso et al. | Mar 2012 | A1 |
20120096149 | Sunkara et al. | Apr 2012 | A1 |
20120101855 | Collins et al. | Apr 2012 | A1 |
20120116820 | English et al. | May 2012 | A1 |
20120130751 | McHugh et al. | May 2012 | A1 |
20120143634 | Beyda et al. | Jun 2012 | A1 |
20120158436 | Bauer et al. | Jun 2012 | A1 |
20120176237 | Tabe | Jul 2012 | A1 |
20120215568 | Vahidi et al. | Aug 2012 | A1 |
20120290333 | Birchall | Nov 2012 | A1 |
20120311053 | Labrie et al. | Dec 2012 | A1 |
20120311614 | DeAnna et al. | Dec 2012 | A1 |
20120323609 | Fini | Dec 2012 | A1 |
20130006608 | Dehors et al. | Jan 2013 | A1 |
20130018936 | DAmico et al. | Jan 2013 | A1 |
20130040636 | Borg et al. | Feb 2013 | A1 |
20130040836 | Himmler et al. | Feb 2013 | A1 |
20130055060 | Folsom et al. | Feb 2013 | A1 |
20130060583 | CoIlins et al. | Mar 2013 | A1 |
20130073303 | Hsu | Mar 2013 | A1 |
20130144658 | Schnabolk et al. | Jun 2013 | A1 |
20130144858 | Lin et al. | Jun 2013 | A1 |
20130182002 | Macciola et al. | Jul 2013 | A1 |
20130185716 | Yin et al. | Jul 2013 | A1 |
20130197945 | Anderson | Aug 2013 | A1 |
20130201018 | Horstemeyer et al. | Aug 2013 | A1 |
20130226623 | Diana et al. | Aug 2013 | A1 |
20130226624 | Blessman et al. | Aug 2013 | A1 |
20130245796 | Lentzitzky et al. | Sep 2013 | A1 |
20130253961 | Feldman et al. | Sep 2013 | A1 |
20130268358 | Haas | Oct 2013 | A1 |
20130282408 | Snyder et al. | Oct 2013 | A1 |
20130317732 | Borg et al. | Nov 2013 | A1 |
20140040343 | Nickolov et al. | Feb 2014 | A1 |
20140046701 | Steinberg et al. | Feb 2014 | A1 |
20140050147 | Beale | Feb 2014 | A1 |
20140058761 | Freiberger et al. | Feb 2014 | A1 |
20140067137 | Amelio et al. | Mar 2014 | A1 |
20140081675 | Ives et al. | Mar 2014 | A1 |
20140089156 | Williams et al. | Mar 2014 | A1 |
20140089990 | van Deventer et al. | Mar 2014 | A1 |
20140108275 | Heptonstall | Apr 2014 | A1 |
20140114693 | Helitzer et al. | Apr 2014 | A1 |
20140114893 | Arthur et al. | Apr 2014 | A1 |
20140123292 | Schmidt et al. | May 2014 | A1 |
20140123309 | Jung et al. | May 2014 | A1 |
20140132409 | Billman et al. | May 2014 | A1 |
20140136242 | Weekes | May 2014 | A1 |
20140142989 | Grosso | May 2014 | A1 |
20140149485 | Sharma et al. | May 2014 | A1 |
20140180723 | Cote et al. | Jun 2014 | A1 |
20140192646 | Mir et al. | Jul 2014 | A1 |
20140195272 | Sadiq et al. | Jul 2014 | A1 |
20140201072 | Reeser et al. | Jul 2014 | A1 |
20140201315 | Jacob et al. | Jul 2014 | A1 |
20140214458 | Vahidi et al. | Jul 2014 | A1 |
20140257862 | Billman et al. | Sep 2014 | A1 |
20140257863 | Maastricht et al. | Sep 2014 | A1 |
20140266669 | Fadell et al. | Sep 2014 | A1 |
20140270492 | Christopulos et al. | Sep 2014 | A1 |
20140278573 | Cook | Sep 2014 | A1 |
20140279593 | Pershing | Sep 2014 | A1 |
20140280457 | Anton et al. | Sep 2014 | A1 |
20140304007 | Kimball et al. | Oct 2014 | A1 |
20140316614 | Newman | Oct 2014 | A1 |
20140322676 | Raman | Oct 2014 | A1 |
20140327995 | Panjwani et al. | Nov 2014 | A1 |
20140334492 | Mack-Crane | Nov 2014 | A1 |
20140358592 | Wedig et al. | Dec 2014 | A1 |
20140371941 | Keller et al. | Dec 2014 | A1 |
20140375440 | Rezvani et al. | Dec 2014 | A1 |
20140380264 | Misra et al. | Dec 2014 | A1 |
20150006206 | Mdeway | Jan 2015 | A1 |
20150019266 | Stempora | Jan 2015 | A1 |
20150025915 | Lekas | Jan 2015 | A1 |
20150025917 | Stempora | Jan 2015 | A1 |
20150026074 | Cotten | Jan 2015 | A1 |
20150112504 | Binion et al. | Apr 2015 | A1 |
20150154709 | Cook | Jun 2015 | A1 |
20150154712 | Cook | Jun 2015 | A1 |
20150161738 | Stempora | Jun 2015 | A1 |
20150221051 | Settino | Aug 2015 | A1 |
20150332407 | Wilson et al. | Nov 2015 | A1 |
20150339911 | Coyne et al. | Nov 2015 | A1 |
20150370272 | Reddy et al. | Dec 2015 | A1 |
20150372832 | Kortz et al. | Dec 2015 | A1 |
20160005130 | Devereaux et al. | Jan 2016 | A1 |
20160039921 | Luo et al. | Feb 2016 | A1 |
20160055594 | Emison | Feb 2016 | A1 |
20160067547 | Anthony et al. | Mar 2016 | A1 |
20160104250 | Allen et al. | Apr 2016 | A1 |
20160125170 | Abramowitz | May 2016 | A1 |
20160163186 | Davidson et al. | Jun 2016 | A1 |
20160225098 | Helitzer et al. | Aug 2016 | A1 |
20170178424 | Wright | Jun 2017 | A1 |
20170365008 | Schreier et al. | Dec 2017 | A1 |
20180033087 | Delinselle | Feb 2018 | A1 |
Number | Date | Country |
---|---|---|
503861 | Jun 2008 | AT |
2478911 | Sep 2003 | CA |
2518482 | Mar 2007 | CA |
2805226 | Aug 2013 | CA |
2882086 | Feb 2014 | CA |
103203054 | Jul 2013 | CN |
102005015028 | Oct 2006 | DE |
102008008317 | Aug 2009 | DE |
722145 | Jul 1996 | EP |
0722145 | Jul 1996 | EP |
1790057 | May 2012 | EP |
2795757 | Oct 2014 | EP |
2276135 | Apr 2015 | EP |
3255613 | Dec 2017 | EP |
2449510 | Nov 2008 | GB |
3282937 | May 2002 | JP |
2002358425 | Dec 2002 | JP |
2008250594 | Oct 2008 | JP |
20090090461 | Aug 2009 | KR |
337513 | Aug 2009 | MX |
2015109725 | Oct 2016 | RU |
2004034232 | Apr 2004 | WO |
2006074682 | Jul 2006 | WO |
2010136163 | Dec 2010 | WO |
2012075442 | Jun 2012 | WO |
2013036677 | Mar 2013 | WO |
2013036677 | Mar 2013 | WO |
Entry |
---|
“After an Auto Accident Understanding the Claims Process,” Financial Services Commission on Ontario, 2011, 10 pgs. |
“Truck Crash Event Data Recorder Downloading,” Crash Forensic; 2012, pp. 1-25. |
Aiyagar, Sanjay et al., “AMQP Message Queuing Protocol Specification,” Version Dec. 9, 2006. https://www.rabbitmq.com/resources/specs/amqp0-9. |
Amanda Love, “How Recoverable Depreciation Works”, Aug. 6, 2012, http://www.stateroofingtexas.com/recoverable-depreciation-works/. |
AMQP is the Internet Protocol for Business Messaging Website. Jul. 4, 2011. https://web.archive.org/web/20110704212632/http://www.amqp.org/about/what. |
Cloudera.com, “Migrating from MapReduce 1 (MRv1) to Map Reduce 2 (MRv2, YARN)”, https://www.cloudera.com/documentation/enterprise/5-9-x/topics/cdh_ig_mapreduce_to_yam_migrate.html, page generated Feb. 6, 2018. |
Corbett et al., “Spanner: Google's Globally-Distributed Database,” Google, Inc., pp. 1-14, 2012. |
Das, Sudipto et al., “Ricardo: Integrating R and Hadoop,” IBM Almaden Research Center, SIGMOD'10, Jun. 6-11, 2010. |
Dean et al., “A New Age of Data Mining in the High-Performance World,” SAS Institute Inc., 2012. |
Deerwester et al., “Indexing by Latent Semantic Analysis,” Journal of the American Society for Information Science, 1990.41 (6), pp. 391-407. |
Fong et al., “Toward a scale-out data-management middleware for low-latency enterprise computing,” IBM J. Res & Dev. vol. 57, No. 3/4 Paper, May 6/Jul. 2013. |
Glennon, Jr., John C.; “Motor Vehicle Crash Investigation and Reconstruction,” BSAT, 2001, 4 pgs. |
Hopkins, Brian, “Big Opportunities in Big Data Positioning Your Firm to Capitalize in a Sea of Information,” Enterprise Architecture Professionals, Forrester Research, Inc., pp. 1-9, May 2011. |
Iwasaki, Yoji; Yamazaki, Fumimo, Publication Info: 32nd Asian Conference on Remote Sensing 2011, ACRS 2011 1: 550-555 Asian Association on Remote Sensing. (Dec. 1, 2011) (Year: 2011). |
Kopp et al., “Full-scale testing of low-rise, residential buildings with realistic wind loads”, 2012, 15 pages. |
McKeown et al., “OpenFlow: Enabling Innovation in Campus Networks,” pp. 1-6, Mar. 14, 2008. |
Melnik, Sergey et al., “Dremel: Interactive Analysis of Web-Scale Datasets,” 36th International Conference on Very Large Data Bases, Sep. 13-17, 2010, Singapore, Proceedings of the VLDB Endowment, vol. No. 1. |
NYSE Technologies Website and Fact Sheet for Data Fabric 6.0 Aug. 2011, https://web.archive.org/web/20110823124532/http://nysetechnologies.nyx.com/data-technology/data-fabric-6-0. |
Richardson, Alexis, “Introduction to RabbitMQ, An Open Source Message Broker That Just Works,” Rabbit MQ, Open Source Enterprise Messaging, pp. 1-36, May 13, 2009. |
Stefan Theuβl, “Applied High Performance Computing Using R,” Diploma Thesis, Univ. Prof, Dipl, Ing. Dr. Kurt Hornik, pp. 1-126, Sep. 27, 2007. |
STIC search dated Jan. 4, 2019 (Year 2019). |
Wang, Guohul et al., “Programming Your Network at Run-time for Big Data Applications,” IBM T.J. Watson Research Center, Rice University, HotSDN'12, Aug. 13, 2012, Helsinki, Finland. |
Wang, Jianwu et al., “Kepler + Hadoop: A General Architecture Facilitating Data-lntensive Applications in Scientific Workflow Systems,” Works 09, Nov. 15, 2009, Portland, Oregon, USA. |
Webb, Kevin C. et al., “Topology Switching for Data Center Networks,” Published in: Proceeding Hot-ICE'11 Proceedings of the 11th USENIX conference on Hot topics in management of Internet, cloud, and enterprise networks and services, Mar. 29, 2011. |
Xi et al., “Enabling Flow-Based Routing Control in Data Center Networks using Probe and ECMP,” Polytechnic Institute of New York University, IEE INFOCOM 2011, pp. 614-619. |
T. Sanidas et al., U.S. Appl. No. 61/800,561, filed Mar. 15, 2013, Specification, 29 pages. |
Telematics Set the Stage the Improved Auto Claims Management by Sam Friedman (Oct. 10, 2012); 3 pages. |
U.S. Appl. No. 61/800,561, Sanidas et al., filed Mar. 15, 2013. |
U.S. Appl. No. 61/866,779, Bergner, filed Aug. 16, 2013. |
U.S. Appl. No. 61/926,091, Allen et al., filed Jan. 10, 2014. |
U.S. Appl. No. 61/926,093, Allen et al., filed Jan. 10, 2014. |
U.S. Appl. No. 61/926,095, Allen et al., filed Jan. 10, 2014. |
U.S. Appl. No. 61/926,098, Allen et al., filed Jan. 10, 2014. |
U.S. Appl. No. 61/926,103, Devereaux et al., filed Jan. 10, 2014. |
U.S. Appl. No. 61/926,108, Allen et al., filed Jan. 10, 2014. |
U.S. Appl. No. 61/926,111, Allen et al., filed Jan. 10, 2014. |
U.S. Appl. No. 61/926,114, Devereaux et al., filed Jan. 10, 2014. |
U.S. Appl. No. 61/926,118, Devereaux et al., filed Jan. 10, 2014. |
U.S. Appl. No. 61/926,119, Devereaux et al., filed Jan. 10, 2014. |
U.S. Appl. No. 61/926,121, Devereaux et al., filed Jan. 10, 2014. |
U.S. Appl. No. 61/926,123, Devereaux et al., filed Jan. 10, 2014. |
U.S. Appl. No. 61/926,532, Allen et al., filed Jan. 13, 2014. |
U.S. Appl. No. 61/926,534, Allen et al., filed Jan. 13, 2014. |
U.S. Appl. No. 61/926,536, Allen et al., filed Jan. 13, 2014. |
U.S. Appl. No. 61/926,541, Allen et al., filed Jan. 13, 2014. |
U.S. Appl. No. 61/943,897, Devereaux et al., filed Feb. 24, 2014. |
U.S. Appl. No. 61/943,901, Devereaux et al., filed Feb. 24, 2014. |
U.S. Appl. No. 61/943,906, Devereaux et al., filed Feb. 24, 2014. |
U.S. Appl. No. 61/948,192, Davis et al., filed Mar. 5, 2014. |
U.S. Appl. No. 62/311,491, Moy, filed Mar. 22, 2016. |
U.S. Appl. No. 62/325,250, Rodgers et al., filed Apr. 20, 2016. |
U.S. Appl. No. 62/351,427, Devereaux et al., filed Jun. 17, 2016. |
U.S. Appl. No. 62/351,441, Flachsbart et al., filed Jun. 17, 2016. |
U.S. Appl. No. 62/351,451, Chavez et al., filed Jun. 17, 2016. |
Zevnik, Richard. The Complete Book of Insurance. Sphinx. 2004. pp. 76-78. |
U.S. Appl. No. 14/251,377, filed Apr. 11, 2014, Devereaux et al. |
U.S. Appl. No. 14/251,392, filed Apr. 11, 2014, Allen et al. |
U.S. Appl. No. 14/251,404, filed Apr. 11, 2014, Devereaux et al. |
U.S. Appl. No. 14/251,411, filed Apr. 11, 2014, Allen et al. |
U.S. Appl. No. 14/273,877, filed May 9, 2014, Allen et al. |
U.S. Appl. No. 14/273,889, filed May 9, 2014, Devereaux et al. |
U.S. Appl. No. 14/273,918, filed May 9, 2014, Allen et al. |
U.S. Appl. No. 14/278,182, filed May 15, 2014, Allen et al. |
U.S. Appl. No. 14/278,202, filed May 15, 2014, Allen et al. |
U.S. Appl. No. 14/303,336, filed Jun. 12, 2014, Devereaux et al. |
U.S. Appl. No. 14/303,347, filed Jun. 12, 2014, Devereaux et al. |
U.S. Appl. No. 14/303,370, filed Jun. 12, 2014, Allen et al. |
U.S. Appl. No. 14/303,382, filed Jun. 12, 2014, Allen et al. |
U.S. Appl. No. 14/305,732, filed Jun. 16, 2014, Devereaux et al. |
U.S. Appl. No. 14/324,534, filed Jul. 7, 2014, Devereaux et al. |
U.S. Appl. No. 14/324,546, filed Jul. 7, 2014, Devereaux et al. |
U.S. Appl. No. 14/324,609, filed Jul. 7, 2014, Devereaux et al. |
U.S. Appl. No. 14/324,618, filed Jul. 7, 2014, Devereaux et al. |
U.S. Appl. No. 14/324,748, filed Jul. 7, 2014, Devereaux et al. |
U.S. Appl. No. 14/324,759, filed Jul. 7, 2014, Devereaux et al. |
U.S. Appl. No. 14/494,207, filed Sep. 23, 2014, Campbell. |
U.S. Appl. No. 14/572,413, filed Dec. 16, 2014, Devereaux et al. |
U.S. Appl. No. 14/573,981, filed Dec. 15, 2014, Allen et al. |
U.S. Appl. No. 14/862,776, filed Sep. 23, 2015, Devereaux et al. |
U.S. Appl. No. 14/941,225, filed Nov. 13, 2015, Billman et al. |
U.S. Appl. No. 14/941,262, filed Nov. 13, 2015, Hopkins et al. |
U.S. Appl. No. 15/244,847, filed Aug. 23, 2016, Devereaux et al. |
U.S. Appl. No. 15/365,555, filed Nov. 30, 2016, Devereaux et al. |
U.S. Appl. No. 15/365,611, filed Nov. 30, 2016, Devereaux et al. |
U.S. Appl. No. 15/365,676, filed Nov. 30, 2016, Devereaux et al. |
U.S. Appl. No. 15/365,706, filed Nov. 30, 2016, Devereaux et al. |
U.S. Appl. No. 15/365,721, filed Nov. 30, 2016, Devereaux et al. |
U.S. Appl. No. 15/365,725, filed Nov. 30, 2016, Devereaux et al. |
U.S. Appl. No. 15/365,736, filed Nov. 30, 2016, Devereaux et al. |
U.S. Appl. No. 15/365,745, filed Nov. 30, 2016, Devereaux et al. |
U.S. Appl. No. 15/365,754, filed Nov. 30, 2016, Devereaux et al. |
U.S. Appl. No. 15/365,764, filed Nov. 30, 2016, Devereaux et al. |
U.S. Appl. No. 15/365,773, filed Nov. 30, 2016, Devereaux et al. |
U.S. Appl. No. 15/365,786, filed Nov. 30, 2016, Devereaux et al. |
Farmers Next Generation Homeowners Policy, Missouri, by Farmers insurance Exchange; 2008; 50 pages. |
Gonzalez Ribeiro, Ana, “Surprising things your home insurance covers,” Jan. 12, 2012 in Insurance; 4 pages. |
Number | Date | Country | |
---|---|---|---|
61948192 | Mar 2014 | US | |
61943897 | Feb 2014 | US | |
61943901 | Feb 2014 | US | |
61943906 | Feb 2014 | US | |
61926532 | Jan 2014 | US | |
61926541 | Jan 2014 | US | |
61926536 | Jan 2014 | US | |
61926534 | Jan 2014 | US | |
61926103 | Jan 2014 | US | |
61926095 | Jan 2014 | US | |
61926111 | Jan 2014 | US | |
61926118 | Jan 2014 | US | |
61926119 | Jan 2014 | US | |
61926121 | Jan 2014 | US | |
61926123 | Jan 2014 | US | |
61926091 | Jan 2014 | US | |
61926108 | Jan 2014 | US | |
61926114 | Jan 2014 | US | |
61926093 | Jan 2014 | US | |
61926098 | Jan 2014 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14303382 | Jun 2014 | US |
Child | 15724103 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15724103 | Oct 2017 | US |
Child | 15896848 | US |