An anomaly detection system includes appliances connected to a network and circuitry configured to receive statuses of the appliances. Patterns of use are determined for the appliances including time periods in which the appliances are most likely to be used. The circuitry is also configured to determine that anomalous events have occurred when an amount of deviation from a normal baseline status for the appliances is greater than a predetermined threshold. Cyber-attack events are detected based on changes to network configuration settings of the appliances. Alerts are output to an external device based on the one or more anomalous events and/or cyber-attack events related to the appliances. The patterns of use are updated based on the status of the appliances and a response from the external device related to the anomalous events or cyber-attack events.
|
18. An apparatus for detecting anomalous events, comprising:
circuitry configured to
receive, from at least one appliance, a status based on at least one of a setting, an operational sate, or sensor values associated with the at least one appliance,
monitor the received status of the at least one appliance over one or more periods of time including at least one of a time of day, day of a week, or season to generate historical data for the status of the at least one appliance,
determine patterns of use for the at least one appliance by applying learning techniques to the generated historical data of the at least one appliance,
determine a normal baseline status based on the patterns of use of the at least one appliance,
determine, based on the patterns of use, one or more anomalous events have occurred when an amount of deviation in the status of the at least one appliance from the normal baseline status for the at least one appliance is greater than a predetermined threshold,
detect that the one or more anomalous events are cyber-attack events based on changes to network configuration settings of the at least one appliance,
classify the one or more anomalous events as at least one of an appliance failure, an attack, and danger to a homeowner based on the status of the at least one appliance and the patterns of use, wherein the circuitry classifies an anomalous event as a danger to homeowner based on an absence of appliance use without a received indication that the homeowner is away from home,
update the patterns of use for the at least one appliance based on at least one of the status of the at least one appliance and a response from the at least one external device related to the one or more anomalous events or the cyber-attack events,
determine, based on the patterns of use of the at least one appliance, a predetermined sampling rate for receiving the status of the at least one appliance wherein the predetermined sampling rate increases as a probability of use of the at least one appliance increases, and
output alerts, to at least one external device, based the determining of an occurrence of an anomalous event and based on the classification of the anomalous event.
1. An anomaly detection system comprising:
at least one appliance configured to connect to at least one network; and
circuitry configured to
receive, from the at least one appliance, a status based on at least one of a setting, an operational sate, or sensor values associated with the at least one appliance,
monitor the received status of the at least one appliance over one or more periods of time including at least one of a time of day, day of a week, or season to generate historical data for the status of the at least one appliance,
determine patterns of use for the at least one appliance by applying learning techniques to the generated historical data of the at least one appliance,
determine a normal baseline status based on the patterns of use of the at least one appliance,
determine, based on the patterns of use, one or more anomalous events have occurred when an amount of deviation in the status of the at least one appliance from the normal baseline status for the at least one appliance is greater than a predetermined threshold,
detect that the one or more anomalous events are cyber-attack events based on changes to network configuration settings of the at least one appliance,
classify the one or more anomalous events as at least one of an appliance failure, an attack, and danger to a homeowner based on the status of the at least one appliance and the patterns of use, wherein the circuitry classifies an anomalous event as a danger to homeowner based on an absence of appliance use without a received indication that the homeowner is away from home,
update the patterns of use for the at least one appliance based on at least one of the status of the at least one appliance and a response from the at least one external device related to the one or more anomalous events,
determine, based on the patterns of use of the at least one appliance, a predetermined sampling rate for receiving the status of the at least one appliance wherein the predetermined sampling rate increases as a probability of use of the at least one appliance increases, and
output alerts, to at least one external device, based the determining of an occurrence of an anomalous event and based on the classification of the anomalous event.
19. A method for detecting anomalous events, comprising:
receiving, from at least one appliance, a status based on at least one of a setting, an operational sate, or sensor values associated with the at least one appliance;
monitoring the received status of the at least one appliance over one or more periods of time including at least one of a time of day, day of a week, or season to generate historical data for the status of the at least one appliance;
determining, via processing circuitry, patterns of use for the at least one appliance by applying learning techniques to the generated historical data of the at least one appliance;
determining, via the processing circuitry, a normal baseline status based on the patterns of use of the at least one appliance;
determining, via the processing circuitry, based on the patterns of use, one or more anomalous events have occurred when an amount of deviation in the status of the at least one appliance from the normal baseline status for the at least one appliance is greater than a predetermined threshold;
detecting, via the processing circuitry, that the one or more anomalous events are cyber-attack events based on changes to network configuration settings of the at least one appliance;
classifying, via the processing circuitry, the one or more anomalous events as at least one of an appliance failure, an attack, and danger to a homeowner based on the status of the at least one appliance and the patterns of use, wherein the processing circuitry classifies an anomalous event as a danger to homeowner based on an absence of appliance use without a received indication that the homeowner is away from home,
updating, via the processing circuitry, the patterns of use for the at least one appliance based on at least one of the status of the at least one appliance and a response from the at least one external device related to the one or more anomalous events or the cyber-attack events;
determining, via the processing circuitry, a predetermined sampling rate for receiving the status of the at least one appliance wherein the predetermined sampling rate increases as a probability of use of the at least one appliance increases based on the patterns of use of the at least one appliance; and
outputting alerts, to at least one external device, based the determining of an occurrence of an anomalous event and based on the classification of the anomalous event.
2. The system of
3. The system of
4. The system of
5. The system of
6. The system of
7. The system of
8. The system of
9. The system of
10. The system of
11. The system of
12. The system of
13. The system of
14. The system of
15. The system of
16. The system of
17. The system of
|
This application was prepared with financial support from the Saudi Arabian Cultural Mission, and in consideration therefore the present inventor has granted, the Kingdom of Saudi Arabia a non-exclusive right to practice the present invention.
The “background” description provided herein is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description which may not otherwise qualify as prior art at the time of filing, are neither expressly or impliedly admitted as prior art against the present invention.
Keeping a home safe from intrusions, other physical attacks, and cyber-attacks is often a priority for homeowners. Homes are increasingly equipped with smart appliances and home controllers that connect to a network to allow a homeowner to remotely operate the smart appliances via a Smart Phone, tablet, or computer.
According to an exemplary embodiment, an anomaly detection system includes appliances connected to a network and circuitry configured to receive statuses of the appliances. Patterns of use are determined for the appliances including time periods in which the appliances are most likely to be used. The circuitry is also configured to determine that anomalous events have occurred when an amount of deviation from a normal baseline status for the appliances is greater than a predetermined threshold. Cyber-attack events are detected based on changes to network configuration settings of the appliances. Alerts are output to an external device based on the one or more anomalous events and/or cyber-attack events related to the appliances. The patterns of use are updated based on the status of the appliances and a response from the external device related to the anomalous events or cyber-attack events.
The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure, and are not restrictive.
A more complete appreciation of this disclosure and many of the attendant advantages thereof will be readily obtained as the same becomes better understood by reference to the following detailed description when considered in connection with the accompanying drawings, wherein:
In the drawings, like reference numerals designate identical or corresponding parts throughout the several views. Further, as used herein, the words “a,” “an” and the like generally carry a meaning of “one or more,” unless stated otherwise. The drawings are generally drawn to scale unless specified otherwise or illustrating schematic structures or flowcharts.
Furthermore, the terms “approximately,” “approximate,” “about,” and similar terms generally refer to ranges that include the identified value within a margin of 20%, 10%, or preferably 5%, and any values therebetween.
Aspects of this disclosure are directed to a smart home anomaly detector that detects anomalous occurrences in a home by monitoring statuses of at least one smart appliance in the home. According to some implementations, a smart appliance is any type of electronic device that can be configured to connect to a wired or wireless network. Examples of smart appliances may include refrigerators, washing machines, dishwashers, media controllers, wireless routers, smoke detectors, home security systems, and the like that can be controlled by a user via an external device, such as a computer or mobile device.
The smart home anomaly detector can determine whether the current status of the smart appliances is normal or abnormal based on learned patterns of use. In certain embodiments, the smart home anomaly detector can notify a homeowner via a phone call, text message, email, or the like, that one or more appliances are in an abnormal status. The smart home anomaly detector can also notify emergency response personnel, such as a police and/or fire department that an emergency, such as a fire or burglary, may have occurred due to a change in status of the smart appliances in the home.
In addition, the smart home anomaly detector can detect occurrences of cyber-attacks related to the smart appliances, which may include instances of when network configuration settings for the smart appliances are compromised, and the smart appliances are used for malicious purposes, such as performing multiple data requests in order to overwhelm a computer system or network. In addition, the smart home anomaly detector may detect when the security settings of a smart appliance, which may include personal identification information, have been violated, which may be indicative of a cyber-attack.
The mobile device 112 represents one or more mobile devices connected to the computer 110, the server 106, the database 108, the smart appliance 114, the smart grid 116, and the SHAD 102 via the network 104. The network 104 represents one or more networks, such as the Internet, connecting the computer 110, the server 106, the database 108, the mobile device 112, the smart appliance 114, the smart grid 116, and the SHAD 102. In some embodiments, more than one SHAD 102 is included in the smart home anomaly detection system 100. As such, the terms referring to the one or more than one SHAD 102 can be used interchangeably.
The smart appliance 114 represents one or more smart appliances connected to the computer 110, the server 106, the database 108, the mobile device 112, the smart grid 116, and the SHAD 102 via the network 104. According to certain embodiments, the smart appliance 114 is configured to conduct two-way communications via the network 104. For example, the smart appliance 114, such as a washing machine, can receive a signal to commence a wash cycle from a user at an external device, such as the mobile device 112. The washing machine is also able to output a signal to the user at the mobile device 112 when the wash cycle has completed. In addition, the at least one smart appliance 114 can include home security devices, such as a smoke detectors and security systems that can be armed and/or disarmed remotely. The home security devices can also output a signal to alert the user, such as a homeowner, that an alarming condition exists.
The smart grid 116 represents one or more smart grids connected to the computer 110, the server 106, the database 108, the mobile device 112, the smart appliance 114, and the SHAD 102 via the network 104. According to certain embodiments, the smart grid 116 is an electrical grid that can predict and respond to the behaviors of electric power consumers. The smart grid 116 can control power distribution through a wide area network (WAN) that covers an area that may include one or more substations, capacitor banks, and voltage regulators. On a smaller level than the WAN, the neighborhood area network (NAN) controls power distribution to a community metering network, such as a in a residential neighborhood or one or more city blocks. The smart grid 116 can also monitor and control the power distribution to one or more electrical components in a home, such as the at least one smart appliance 114. Through communication with the at least one smart appliance 114 via the network 104, the smart grid 116 can determine patterns of how much power is consumed by the at least one smart appliance 114 and can tailor energy distribution to the home based on the power consumption patterns.
In certain embodiments, the SHAD 102 performs wireless or wired communications with at least one smart appliance 114. In some implementations, the at least one smart appliance 114 includes any appliance with circuitry that outputs a current status to the SHAD 102. For example, a refrigerator may be able to output a temperature and/or a status of a door being opened or closed. Examples of the at least one smart appliance 114 include home security systems, washing machines, kitchen appliances, HVAC systems, smoke detectors, and the like. The SHAD 102 and the at least one smart appliance 114 can communicate via wireless networks such as WI-FI, BLUETOOTH, cellular networks including EDGE, 3G and 4G wireless cellular systems, or any other wireless form of communication that is known. Other types of wireless networks used in smart homes with at least one smart appliance 114 can include ZIGBEE, Z-WAVE, HOMEPLUG, and the like.
As would be understood by one of ordinary skill in the art, based on the teachings herein, the mobile device 112 or any other external device could also be used in the same manner as the computer 110 to receive status updates regarding one or more anomalous conditions of the at least one smart appliance 114 from the SHAD 102. For example, when the SHAD 102 detects that the refrigerator door has been left open for a period of time that is greater than a predetermined threshold, the server 106 can output a text message or email to the mobile device 112 of the homeowner to alert the homeowner that an abnormal condition has occurred. In addition, the homeowner can access alerts from the SHAD 102 via an application on the mobile device 112. The SHAD 102 can also issue an alert to the mobile device 112 of the homeowner when one or more conditions exist that may indicate that the physical security and/or cyber security of the home has been violated. Details regarding the processes performed by the smart home anomaly detection system 100 are discussed further herein.
The detector module 202 receives inputs from one or more sensors via network 104 to detect a change in status of the at least one smart appliance 114. For example, a refrigerator can have a temperature sensor and a door sensor to determine whether the door to the refrigerator has been opened or closed. If the temperature of the refrigerator increases above a predetermined range, such as 40° F.-45° F. and the door sensor indicates that the refrigerator has remained closed during the period of temperature increase, the detector module 202 may determine that an anomalous event has occurred, such as a loss of power to the refrigerator. The network 104 can include wired and wireless connections between the SHAD 102, the at least one smart appliance 114, and/or external devices, such as the computer 110 or mobile device 112. For example, the detector module 202 also receives data from the external devices which may include responses by the homeowner regarding anomalous events that have occurred.
In addition, the detector module 202 can also receive inputs from the smart grid 116 for the home that include power consumption, voltage, and current readings for the at least one smart appliance 114. For example, the processing circuitry of the detector module 202 can detect that a power failure has occurred with the at least one smart appliance 114 based on an immediate drop in voltage and/or current at the smart grid 116. In certain embodiments, the detector module 202 continuously monitors the one or more sensors to detect a change in the status of the smart appliances. In other implementations, the detector module 202 receives sensor values at a predetermined sampling rate based on the patterns of appliance status change determined by the learner module 204.
In some implementations, the processing circuitry of the detector module 202 is configured to detect instances of cyber-attack on the at least one smart appliance 114. For example, the detector module 202 can execute one or more software processes directed to detecting malicious use of the at least one smart appliance 114, such as a compromising of an IP address, network configuration settings, or security control settings, and other types of cyber hacking.
The detector module 202 compares the observed status for the appliance to a normal status of the appliance that has been determined by the learner module 204, as will be discussed further herein. Throughout the disclosure, the “normal” status of an appliance refers to an “expected” or “learned” status based on user preferences, learned patterns of appliance use, and the like. In addition, an “abnormal” or “anomalous” status of an appliance refers to an “unexpected” status that differs from one or more normal or learned statuses of the appliance. The normal or abnormal status of the at least one smart appliance 114 determined by the detector module is output to the learner module 204 and informer module 206. Details regarding processes performed by the detector module 202 are discussed further herein.
The learner module 204 employs machine learning techniques, such as artificial neural networks, support vector machines, the like, to determine patterns of use and patterns of status change of the at least one smart appliance 114 in the home. In certain embodiments, the learner module 204 determines a normal baseline status for the at least one smart appliance 114 based on time of day, day of the week, season, and the like. The normal baseline status based on patterns of use and historical data obtained by monitoring the statuses of the at least one smart appliance 114 and can include an average sensor value associated with the at least one smart appliance 114 based on time of day or an expected operational state. The learner module 204 also outputs the statuses of the at least one smart appliance 114 along with an associated normality or abnormality determination to appliance status logs that are saved in the database 108. According to certain embodiments, the appliance status logs are data structures that include cumulative appliance status data for a period of time. The processing circuitry of the SHAD 102 applies the machine learning techniques to the data in the appliance status logs to determine the normal baseline status for the at least one smart appliance 114. Details regarding processes performed by the learner module 204 are discussed further herein.
The informer module 206 receives alerts from the detector module 202 regarding one or more anomalous events with respect to the at least one smart appliance 114 and issues alerts to external devices of one or more interested parties, such as a homeowner, an emergency contact, or an emergency first responder. The alerts can be issued to the external devices, such as mobile devices 112, of the one or more interested parties via text message, voice call, email, or a notification via an application on the mobile device 112.
According to certain embodiments, the informer module 206 receives a response from the external device of an interested party, such as the homeowner, verifying whether the status of the smart appliance is actually anomalous. For example, based on the learned patterns of use of a washing machine, the processing circuitry of the detector module 202 may determine that the status of “running” for the washing machine at 12:00 PM on a Wednesday is anomalous, and the informer module 206 issues an alert to the mobile device 112 of the homeowner via the network 104 regarding the anomalous event of the running washing machine. If, in fact, the homeowner is using the washing machine at the time that the alert is issued, the homeowner can respond to the alert to indicate that the running washing machine is a normal event. The informer module 206 outputs the response from the interested party to the learner module 204 so that the historical data can be updated based on the response of the homeowner. Details regarding processes performed by the informer module 206 are discussed further herein.
In some implementations, the processing circuitry of the detector module 202 is configured to detect instances of cyber-attack on the at least one smart appliance 114, which are considered by be anomalous activities. For example, the detector module 202 can execute one or more software processes directed to detecting malicious use of the at least one smart appliance 114, such as a compromising of an IP address or network security settings and other types of cyber-hacking.
At step S304, the detector module 202 determines an amount of deviation from the normal baseline status for the at least one smart appliance 114. In certain embodiments, the amount of deviation from the normal baseline status is assigned a value of “very low,” “low,” “medium,” or “high,” which may be determined based on the historical data saved in the appliance status logs by the learner module 204. In some implementations, the amount of deviation from the normal baseline status is based on a probability of occurrence of the smart appliance 114 status based on the historical data saved in the appliance status logs. For a received status with a probability of occurrence of approximately one, the amount of deviation from the normal baseline status is assigned a value of very low. For a received status with a probability of occurrence of approximately zero, the amount of deviation from the normal baseline status is assigned a value of high. In addition, for instances of suspected cyber-attack on the at least one smart appliance 114, the amount of deviation from the normal baseline status is assigned a value of high.
For example, the learner module 204 may determine that the washing machine is normally run between 5:00 PM and 10:00 PM on Sundays. If the detector module 202 receives the appliance status of “running” from the washing machine at 6:00 PM on a Sunday, then the amount of deviation from the normal baseline status is determined to be “very low.” Likewise, if the detector module 202 receives the operational state of “off,” “standby,” or “sleep” for the washing machine at 3:00 AM on a Friday, then the amount of deviation from the normal baseline status is also determined to be “very low.” In addition, if the washing machine is running at 4:00 PM on a Sunday, the detector module 202 may assign an amount of deviation of “low” to the status of the washing machine. However, if the washing machine is running at 10:00 AM on a Tuesday, the detector module 202 may assign an amount of deviation of “high” to the status of the washing machine.
At step S306, it is determined whether the status of the smart appliance 114 is normal or anomalous. Throughout the disclosure, normal and anomalous statuses of the at least one smart appliance 114 are also referred to as normal and anomalous events. In certain embodiments, the detector module 202 determines that the status of the smart appliance 114 is normal if the amount of deviation from the normal baseline status is less than a predetermined threshold, such as when the amount of deviation from the normal baseline status is very low or low. In addition, the detector module 202 may determine that the status of the smart appliance 114 is anomalous if the amount of deviation from the normal baseline status is greater than a predetermined threshold, such as a medium or high amount of deviation. If it is determined that the status of the smart appliance 114 is normal, resulting in a “yes” at step S306, then step S310 is performed. Otherwise, if it is determined that the status of the smart appliance 114 is anomalous, resulting in a “no” at step S306, then step S308 is performed.
In some implementations, when an anomalous event is detected by the detector module 202 for the at least one smart appliance 114, the anomalous event is categorized by type. For example, types of anomalous events can include appliance failures, attacks, and dangers to homeowner. Appliance failures include anomalous events that indicate that the at least one smart appliance 114 has lost power due to a smart grid 116 failure or due to failure of the smart appliance 114. Failures can be detect by sensing a loss of voltage and/or current supplied to the at least one smart appliance 116.
Attacks can include physical attacks where the physical security of the home has been violated. This may be detected by an alarming security system, lights or fans that are turned on while the homeowner is away from home, and the like. Attacks can also include cyber-attacks where the integrity of communications for the at least one smart appliance 114 is violated, such as through a compromising of network security settings for the at least one smart appliance. Anomalous events that indicate dangers to the homeowner can include lack of use of the at least one smart appliance 114 for hours, days, and weeks, which may indicate that the homeowner may away from home or may be injured and unable to call for help. In some implementations, the SHAD 102 can receive input from an external device regarding instances when the homeowner is scheduled to be away from home. For example, the homeowner can send an email or text message to indicate to the SHAD 102 that he or she is away from home.
At step S308, if it is determined at step S306 that the status of the smart appliance 114 is anomalous, then an alert is issued to the informer module 206. For example, if the detector module 202 receives a status that the washing machine is running at 3:00 AM on a Wednesday, then the status may be assigned a high amount of deviation from the normal baseline status for the washing machine, resulting in an anomalous event. The detector module 202 can output the status of the washing machine, normality determination, and an associated time of occurrence to the informer module 206. The informer module 206 alerts the homeowner that the anomalous event has occurred regarding the at least one smart appliance 114 via email, text message, voice call, and the like, as will be discussed further herein.
At step S310, if it is determined at step S306 that the status of the smart appliance 114 is normal, then the result is output to the learner module 204. For example, if the detector module 202 receives a status that the washing machine is running at 5:30 PM on a Sunday, then the status may be assigned an amount of deviation from the normal baseline status of very low for the washing machine, resulting in a normal event. The detector module 202 can output the status of the washing machine, normality determination, and an associated time of occurrence to the learner module 204.
In other implementations, the learner module 204 records sensor values in the appliance status logs at a predetermined sampling rate based on patterns of appliance use. For example, the learner module 204 may determine one or more time periods during the day or week when the at least one smart appliance 114 is most likely to be used. The predetermined sampling rate with which the learner module 204 records the status of the at least one smart appliance 114 in the appliance status log may be higher than the sampling rate at time periods during the day or week when the at least one smart appliance 114 is less likely to be used. For example, the sampling rate with which the learner module 204 records the status of the oven may be higher at times of the day when the oven is more likely to be used, such as between 12:00 PM and 10:00 PM, than during time periods when the oven is less likely to be used, such as between 12:00 AM and 6:00 AM.
In addition, the learner module 204 receives the normality determinations for the at least one smart appliance 114 from the detector module 202 during steps S308 and S310 of the detector module process 300. In some implementations, the learner module 204 records the normality determination along with the associated appliance status and time of occurrence in the appliance status log. For example, the processing circuitry of the detector module 202 may make a normality determination of normal for an oven that has status of “bake” and a temperature sensor at 400° F. at 6:00 PM. The learner module 204 records the normality determination in the appliance status log for the oven along with the time, status, and temperature sensor value.
According to certain embodiments, the learner module 204 also receives one or more homeowner responses to alerts regarding anomalous statuses for the at least one smart appliance 114. As will be discussed further herein, the processing circuitry of the SHAD 102 issues alerts to the homeowner via text message, email, voice call, and the like when the detector module 202 determines that an anomalous condition exists with the at least one smart appliance 114. The response by the homeowner to the alert from the informer module 206 is received by the learner module 204 and saved in the appliance status log for the at least one smart appliance 114.
At step S404, the processing circuitry of the learner module 204 analyzes the data in the appliance status logs to determine one or more patterns of use for the at least one smart appliance 114, according to certain embodiments. The processing circuitry employs machine learning techniques, such as artificial neural networks, support vector machines, the like, to determine patterns of use and patterns of status change of the at least one smart appliance 114 in the home. As the SHAD 102 acquires more data regarding how the at least one smart appliance 114 is used, the learner module 204 adapts the patterns of use based on changes in the home environment or in the homeowner's habits. In some implementations, the processing circuitry of the detector module 202 may determine that the current status of the at least one smart appliance 114 is anomalous based on the patterns of use determined by the learner module 204.
However, the homeowner may report that the current status of the at least one smart appliance is actually not anomalous when informed by the SHAD 102. The learner module 204 uses the information input by the homeowner to modify the patterns of use. In addition, in some implementations, the learner module 204 can analyze the security settings, network communication speed, network configuration, and the like of the at least one smart appliance 114 to determine a likelihood of cyber-attack. For example, an immediate reduction in the network communication speed may indicate that cyber-attackers are using the at least one smart appliance 114 to overwhelm the network 104. In addition, the patterns of use of the at least one smart appliance can be translated into the normal baseline status for the at least one smart appliance 114 that is used by the detector module 202 to determine whether the current status of the at least one smart appliance 114 is normal or anomalous.
At step S406, the processing circuitry of the learner module 204 stores the result of the data analysis in the database 108. According to certain embodiments, the results of the data analysis include the patterns of use of the at least one smart appliance 114 determined at step S404.
For each hour of the day, the processing circuitry of the learner module 204 determines a probability of use of the dishwasher based on historical data of dishwasher use saved in the appliance status log for the dishwasher. The probability of use can also be used to determine the normal baseline status for the at least one smart appliance 114. For the example of the dishwasher data analysis results 450 in
In some implementations, the normal baseline status for smart appliances with statuses dependent on temperature sensors, such as HVAC systems, refrigerators, freezers, ovens, and the like, the normal baseline status can include an average temperature for each hour of the day. The amount of deviation from the normal baseline status determined at step S304 of the detector module process 300 may be based on the normal baseline status as well as the probability of use. For example, the processing circuitry may use the equation, D=|xi−m(X)| to determine the amount of deviation from the normal baseline status for the HVAC system based on temperature. D represents the deviation from the normal baseline status, xi represents a sample temperature value, and m(X) is the mean value of temperature sensor values over a predetermined period of time. In some implementations, the mean of the temperature sensor values is determined to be the normal baseline status for the HVAC system.
At step S504, the processing circuitry of the informer module 206 prioritizes the anomalous event alerts issued by the detector module at step S308 of the detector module process 300. According to certain embodiments, the prioritization is based on a predetermined severity level for the anomalous events based on ensuring safety of the home, user preferences, and learned patterns of use of the at least one smart appliance 114. For example, in some implementations, an alarming smoke detector or an alarming home security system is assigned a higher priority over the anomalous event of a refrigerator temperature that is outside the designated range of 40° F. to 45° F. In addition, anomalous events that are classified as attacks or dangers to the homeowner are assigned a higher priority than failures of the at least one appliance 114.
At step S506, an anomalous event alert is issued to a primary user, such as a homeowner, via a text message, email, voice call, or the like, which is received at an external device, such as the mobile device 112 or computer 110. In some implementations, the primary user is notified of the anomalous event via one or more alert screens of an application on an external device, such as the mobile device 112.
Referring back to
At step S510, if it is determined at step S508 that the primary user has not responded to the anomalous event alert within the predetermined period of time, then the informer module 206 issues the anomalous event alert to a secondary user, such as an emergency contact indicated by the primary user at an interface at an interface at the SHAD 102 or other external device, such as the computer 110 or mobile device 112. According to certain embodiments, the anomalous event alert is issued to the emergency contact via text message, email, voice call, or the like, which is received at an external device, such as the mobile device 112 or computer 110. In some implementations, the emergency contact is notified of the anomalous event via one or more alert screens of an application on an external device, such as the mobile device 112 as described previously with respect to
At step S512, a determination is made regarding whether the emergency contact has responded to the anomalous event alert within a predetermined period of time. According to some implementations, a user can specify the predetermined period of time for the secondary user, such as the emergency contact, to respond to the anomalous event via an interface at the SHAD 102, mobile device 112, or computer 110. For example, predetermined period of time for responding to the anomalous event can be set to 1 minute, 5 minutes, 10 minutes, and any other time period. If the emergency contact has responded to the anomalous event alert within the predetermined period of time, resulting in a “yes” at step S512, then step S518 is performed. Otherwise, if the homeowner has not responded to the anomalous event alert within the predetermined period of time, resulting in a “no” at step S512, then step S514 is performed.
At step S514, if it is determined at step S512 that the secondary user has not responded to the anomalous event alert within the predetermined period of time, then the informer module 206 issues the anomalous event alert to an emergency responder via emergency response system, such as a dispatch center for emergency responders that may include medical first responders, law enforcement, and the like. According to certain embodiments, the anomalous event alert is issued to the emergency response system via text message, email, voice call, or the like, which is received at an external device, such as the mobile device 112 or computer 110. In some implementations, the emergency response system is notified of the anomalous event via one or more alert screens of an application on an external device, such as the mobile device 112 as described previously with respect to
According to some embodiments, the emergency responder notification of step S514 is performed if the anomalous event is related to a potential safety or security issue for the home. For example, anomalous events related to the home security system or smoke detector are reported to the emergency responder at step S514, but anomalous events such as an unexpectedly running washing machine or dishwasher may not be reported to the emergency responder.
At step S518, if it is determined at step S508 or step S512 that the homeowner or the emergency contact has responded to the anomalous event alert, resulting in a “yes” at step S508 or step S512, then it is determined whether the anomalous event was truly abnormal based on the response of the homeowner or emergency contact. In the example of
At step S516, the user response by the homeowner, emergency contact, or emergency responder to the anomalous event is output to the learner module 204. The user response to the anomalous event can be associated with appliance data recorded in the appliance status logs at step S402 in order to update the patterns of use for the at least one smart appliance 114.
The smart home anomaly detection system 100 allows homeowners to know and maintain a level of safety of their homes by monitoring changes in the statuses of the at least one smart appliance 114 that communicates with the SHAD 102 so that the at least one smart appliance 114 contributes to the overall integrity and security of the home. In addition, as the number of devices and appliances within a home that can communicate with the network 104 increases, the devices and appliances become increasingly vulnerable to cyber-attack. The SHAD 102 is able to detect compromises in network configurations and security settings of the at least one smart appliance 104 to minimize the effects of potential cyber-attacks.
A hardware description of the smart home anomaly detector 102 according to exemplary embodiments is described with reference to
Further, the claimed advancements may be provided as a utility application, background daemon, or component of an operating system, or combination thereof, executing in conjunction with CPU 700 and an operating system such as Microsoft Windows 7, UNIX, Solaris, LINUX, Apple MAC-OS and other systems known to those skilled in the art.
CPU 700 may be a Xenon or Core processor from Intel of America or an Opteron processor from AMD of America, or may be other processor types that would be recognized by one of ordinary skill in the art. Alternatively, the CPU 700 may be implemented on an FPGA, ASIC, PLD or using discrete logic circuits, as one of ordinary skill in the art would recognize. Further, CPU 700 may be implemented as multiple processors cooperatively working in parallel to perform the instructions of the inventive processes described above.
The SHAD 102 in
The SHAD 102 further includes a display controller 708, such as a NVIDIA GeForce GTX or Quadro graphics adaptor from NVIDIA Corporation of America for interfacing with display 710 of the SHAD 102 and the computer 110, such as a Hewlett Packard HPL2445w LCD monitor. A general purpose I/O interface 712 at the SHAD 102 interfaces with a keyboard and/or mouse 714 as well as a touch screen panel 716 on or separate from display 710. General purpose I/O interface 712 also connects to a variety of peripherals 718 including printers and scanners, such as an OfficeJet or DeskJet from Hewlett Packard.
A sound controller 720 is also provided in the SHAD 102, such as Sound Blaster X-Fi Titanium from Creative, to interface with speakers/microphone 722 thereby providing sounds and/or music.
The general purpose storage controller 724 connects the storage medium disk 704 with communication bus 726, which may be an ISA, EISA, VESA, PCI, or similar, for interconnecting all of the components of the SHAD 102. A description of the general features and functionality of the display 710, keyboard and/or mouse 714, as well as the display controller 708, storage controller 724, network controller 706, sound controller 720, and general purpose I/O interface 712 is omitted herein for brevity as these features are known.
In other alternate embodiments, processing features according to the present disclosure may be implemented and commercialized as hardware, a software solution, or a combination thereof. Moreover, instructions corresponding to the detector module process 300, learner module process 400, and informer module process 500 in accordance with the present disclosure could be stored in a thumb drive that hosts a secure process.
A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of this disclosure. For example, preferable results may be achieved if the steps of the disclosed techniques were performed in a different sequence, if components in the disclosed systems were combined in a different manner, or if the components were replaced or supplemented by other components. The functions, processes and algorithms described herein may be performed in hardware or software executed by hardware, including computer processors and/or programmable circuits configured to execute program code and/or computer instructions to execute the functions, processes and algorithms described herein. Additionally, an implementation may be performed on modules or hardware not identical to those described. Accordingly, other implementations are within the scope that may be claimed.
Patent | Priority | Assignee | Title |
10126725, | Mar 08 2016 | Samsung Electronics Co., Ltd. | Elastic rule engine for a smart home |
10504306, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Accident response using autonomous vehicle monitoring |
10545024, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle trip routing |
10579070, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Method and system for repairing a malfunctioning autonomous vehicle |
10679497, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle application |
10685403, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Fault determination with autonomous feature use monitoring |
10691126, | Jan 22 2016 | Hyundai Motor Company; Kia Corporation | Autonomous vehicle refueling |
10719885, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Autonomous feature use monitoring and insurance pricing |
10719886, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Accident fault determination for autonomous vehicles |
10723312, | Jul 21 2014 | State Farm Mutual Automobile Insurance Company | Methods of theft prevention or mitigation |
10726498, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Accident fault determination for autonomous vehicles |
10726499, | May 20 2014 | State Farm Mutual Automoible Insurance Company | Accident fault determination for autonomous vehicles |
10747234, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Method and system for enhancing the functionality of a vehicle |
10748218, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle technology effectiveness determination for insurance pricing |
10748419, | Aug 28 2015 | State Farm Mutual Automobile Insurance Company | Vehicular traffic alerts for avoidance of abnormal traffic conditions |
10769954, | Aug 28 2015 | State Farm Mutual Automobile Insurance Company | Vehicular driver warnings |
10802477, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Virtual testing of autonomous environment control system |
10818105, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Sensor malfunction detection |
10821971, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle automatic parking |
10824144, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle control assessment and selection |
10824145, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle component maintenance and repair |
10824415, | Nov 13 2014 | State Farm Automobile Insurance Company | Autonomous vehicle software version assessment |
10825326, | Jul 21 2014 | State Farm Mutual Automobile Insurance Company | Methods of facilitating emergency assistance |
10828999, | Jan 22 2016 | Hyundai Motor Company; Kia Corporation | Autonomous electric vehicle charging |
10829063, | Jan 22 2016 | Hyundai Motor Company; Kia Corporation | Autonomous vehicle damage and salvage assessment |
10831191, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle accident and emergency response |
10831204, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle automatic parking |
10832327, | Jul 21 2014 | State Farm Mutual Automobile Insurance Company | Methods of providing insurance savings based upon telematics and driving behavior identification |
10915965, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle insurance based upon usage |
10940866, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operating status assessment |
10943303, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operating style and mode monitoring |
10950065, | Aug 28 2015 | Hyundai Motor Company; Kia Corporation | Shared vehicle usage, monitoring and feedback |
10963969, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Autonomous communication feature use and insurance pricing |
10974693, | Jul 21 2014 | State Farm Mutual Automobile Insurance Company | Methods of theft prevention or mitigation |
10977945, | Aug 28 2015 | State Farm Mutual Automobile Insurance Company | Vehicular driver warnings |
10997849, | Jul 21 2014 | State Farm Mutual Automobile Insurance Company | Methods of facilitating emergency assistance |
11010840, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Fault determination with autonomous feature use monitoring |
11014567, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operator identification |
11015942, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle routing |
11016504, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Method and system for repairing a malfunctioning autonomous vehicle |
11022978, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle routing during emergencies |
11023629, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature evaluation |
11030696, | Jul 21 2014 | State Farm Mutual Automobile Insurance Company | Methods of providing insurance savings based upon telematics and anonymous driver data |
11057774, | May 14 2020 | T-Mobile USA, Inc. | Intelligent GNODEB cybersecurity protection system |
11062396, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Determining autonomous vehicle technology performance for insurance pricing and offering |
11062414, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | System and method for autonomous vehicle ride sharing using facial recognition |
11068995, | Jul 21 2014 | State Farm Mutual Automobile Insurance Company | Methods of reconstructing an accident scene using telematics data |
11069221, | Jul 21 2014 | State Farm Mutual Automobile Insurance Company | Methods of facilitating emergency assistance |
11070982, | Apr 15 2020 | T-Mobile USA, Inc. | Self-cleaning function for a network access node of a network |
11080794, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle technology effectiveness determination for insurance pricing |
11115824, | May 14 2020 | T-Mobile USA, Inc. | 5G cybersecurity protection system |
11119477, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Anomalous condition detection and response for autonomous vehicles |
11124186, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle control signal |
11126184, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle parking |
11127083, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Driver feedback alerts based upon monitoring use of autonomous vehicle operation features |
11127086, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Accident fault determination for autonomous vehicles |
11127290, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle infrastructure communication device |
11136024, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Detecting and responding to autonomous environment incidents |
11173918, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle control assessment and selection |
11175660, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle control assessment and selection |
11181930, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Method and system for enhancing the functionality of a vehicle |
11189112, | Dec 14 2015 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle sensor malfunction detection |
11194303, | Dec 03 2018 | International Business Machines Corporation | Method and system for anomaly detection and notification through profiled context |
11206542, | May 14 2020 | T-Mobile USA, Inc. | 5G cybersecurity protection system using personalized signatures |
11238538, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Accident risk model determination using autonomous vehicle operating data |
11242051, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle action communications |
11247670, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle control assessment and selection |
11257163, | Jul 21 2014 | State Farm Mutual Automobile Insurance Company | Methods of pre-generating insurance claims |
11282143, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Fully autonomous vehicle insurance pricing |
11288751, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature monitoring and evaluation of effectiveness |
11348182, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature monitoring and evaluation of effectiveness |
11348193, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Component damage and salvage assessment |
11386501, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Accident fault determination for autonomous vehicles |
11436685, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Fault determination with autonomous feature use monitoring |
11440494, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Detecting and responding to autonomous vehicle incidents |
11441916, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle trip routing |
11444980, | Apr 15 2020 | T-Mobile USA, Inc. | On-demand wireless device centric security for a 5G wireless network |
11450206, | Aug 28 2015 | State Farm Mutual Automobile Insurance Company | Vehicular traffic alerts for avoidance of abnormal traffic conditions |
11494175, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operating status assessment |
11500377, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle control assessment and selection |
11511736, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle retrieval |
11513521, | Jan 22 2016 | STATE FARM MUTUAL AUTOMOBILE INSURANCE COPMANY | Autonomous vehicle refueling |
11522877, | Dec 16 2019 | SECUREWORKS CORP | Systems and methods for identifying malicious actors or activities |
11526167, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle component maintenance and repair |
11528294, | Feb 18 2021 | SECUREWORKS CORP | Systems and methods for automated threat detection |
11532187, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operating status assessment |
11533624, | Apr 15 2020 | T-Mobile USA, Inc. | On-demand security for network resources or nodes, such as for a wireless 5G network |
11558747, | May 14 2020 | T-Mobile USA, Inc. | Intelligent cybersecurity protection system, such as for use in 5G networks |
11565654, | Jul 21 2014 | State Farm Mutual Automobile Insurance Company | Methods of providing insurance savings based upon telematics and driving behavior identification |
11580604, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature monitoring and evaluation of effectiveness |
11588834, | Sep 03 2020 | SECUREWORKS CORP | Systems and methods for identifying attack patterns or suspicious activity in client networks |
11600177, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle application |
11615695, | Jun 12 2018 | Intergraph Corporation | Coverage agent for computer-aided dispatch systems |
11625802, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Coordinated autonomous vehicle automatic area scanning |
11632398, | Nov 06 2017 | SECUREWORKS CORP. | Systems and methods for sharing, distributing, or accessing security data and/or security applications, models, or analytics |
11634102, | Jul 21 2014 | State Farm Mutual Automobile Insurance Company | Methods of facilitating emergency assistance |
11634103, | Jul 21 2014 | State Farm Mutual Automobile Insurance Company | Methods of facilitating emergency assistance |
11645064, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle accident and emergency response |
11656978, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Virtual testing of autonomous environment control system |
11659396, | May 14 2020 | T-Mobile USA, Inc. | Intelligent cybersecurity protection system, such as for use in 5G networks |
11665201, | Nov 28 2016 | SECUREWORKS CORP. | Computer implemented system and method, and computer program product for reversibly remediating a security risk |
11669090, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature monitoring and evaluation of effectiveness |
11682244, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Smart home sensor malfunction detection |
11710097, | Mar 22 2019 | QUANATA, LLC | Systems and methods for obtaining incident information to reduce fraud |
11710188, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Autonomous communication feature use and insurance pricing |
11719545, | Jan 22 2016 | Hyundai Motor Company; Kia Corporation | Autonomous vehicle component damage and salvage assessment |
11720968, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle insurance based upon usage |
11726763, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle automatic parking |
11735028, | Jun 12 2018 | Intergraph Corporation | Artificial intelligence applications for computer-aided dispatch systems |
11735043, | Oct 29 2019 | QUANATA, LLC | Systems and methods for fraud prevention based on video analytics |
11736505, | Feb 07 2020 | MASTERCARD TECHNOLOGIES CANADA ULC | Automated web traffic anomaly detection |
11740885, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle software version assessment |
11748085, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operator identification |
11765171, | Jun 04 2019 | Bank of America Corporation | Monitoring security configurations of cloud-based services |
11777785, | Jan 21 2018 | Cisco Technology, Inc | Alert throttling |
11799878, | Apr 15 2020 | T-Mobile USA, Inc. | On-demand software-defined security service orchestration for a 5G wireless network |
11824881, | Apr 15 2020 | T-Mobile USA, Inc. | On-demand security layer for a 5G wireless network |
11869092, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature monitoring and evaluation of effectiveness |
11879742, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle application |
11920938, | Jan 22 2016 | Hyundai Motor Company; Kia Corporation | Autonomous electric vehicle charging |
11934522, | Sep 04 2018 | Carrier Corporation | System and method for detecting malicious activities and anomalies in building systems |
11949999, | Oct 29 2019 | QUANATA, LLC | Systems and methods for gate-based vehicle image capture |
11954482, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle control assessment and selection |
11962604, | Jul 03 2017 | Home-based physical and cyber integrated security-intrusion detection system (PCIS-IDS) | |
11977874, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle control assessment and selection |
11995610, | Mar 22 2019 | QUANATA, LLC | Systems and methods for obtaining incident information to reduce fraud |
12055399, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle trip routing |
12086583, | Nov 13 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle insurance based upon usage |
12104912, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Coordinated autonomous vehicle automatic area scanning |
12106657, | Jun 12 2018 | Intergraph Corporation | Similarity agent for computer-aided dispatch systems |
12111165, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle retrieval |
12125368, | Jun 12 2018 | Intergraph Corporation | Statistic agent for computer-aided dispatch systems |
12125383, | Oct 29 2019 | QUANATA, LLC | Systems and methods for fraud prevention based on video analytics |
12135789, | Aug 04 2021 | SECUREWORKS CORP | Systems and methods of attack type and likelihood prediction |
12140959, | May 20 2014 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature monitoring and evaluation of effectiveness |
12151644, | Jul 21 2014 | State Farm Mutual Automobile Insurance Company | Methods of facilitating emergency assistance |
12159317, | Aug 28 2015 | State Farm Mutual Automobile Insurance Company | Vehicular traffic alerts for avoidance of abnormal traffic conditions |
12174027, | Jan 22 2016 | State Farm Mutual Automobile Insurance Company | Detecting and responding to autonomous vehicle incidents and unusual conditions |
12179695, | Jul 21 2014 | State Farm Mutual Automobile Insurance Company | Methods of facilitating emergency assistance |
ER4580, | |||
ER6055, |
Patent | Priority | Assignee | Title |
8560134, | Sep 10 2010 | Kwangduk Douglas, Lee | System and method for electric load recognition from centrally monitored power signal and its application to home energy management |
8973133, | Dec 19 2012 | GEN DIGITAL INC | Systems and methods for detecting abnormal behavior of networked devices |
20030172302, | |||
20070016918, | |||
20090193436, | |||
20110208849, | |||
20110238234, | |||
20120323381, | |||
20130073094, | |||
20140293046, | |||
20140324192, | |||
20150026806, | |||
20150048679, | |||
20150048684, | |||
20150106933, | |||
20150309484, | |||
20160148496, | |||
CN103345211, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Jan 08 2015 | Imam Abdulrahman Bin Faisal University | (assignment on the face of the patent) | / | |||
Jun 13 2017 | ALMURAYH, ABDULLAH SAEED | Imam Abdulrahman Bin Faisal University | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 042706 | /0737 |
Date | Maintenance Fee Events |
Mar 08 2021 | REM: Maintenance Fee Reminder Mailed. |
Jul 16 2021 | M2551: Payment of Maintenance Fee, 4th Yr, Small Entity. |
Jul 16 2021 | M2554: Surcharge for late Payment, Small Entity. |
Jul 16 2021 | SMAL: Entity status set to Small. |
Dec 31 2024 | M2552: Payment of Maintenance Fee, 8th Yr, Small Entity. |
Date | Maintenance Schedule |
Jul 18 2020 | 4 years fee payment window open |
Jan 18 2021 | 6 months grace period start (w surcharge) |
Jul 18 2021 | patent expiry (for year 4) |
Jul 18 2023 | 2 years to revive unintentionally abandoned end. (for year 4) |
Jul 18 2024 | 8 years fee payment window open |
Jan 18 2025 | 6 months grace period start (w surcharge) |
Jul 18 2025 | patent expiry (for year 8) |
Jul 18 2027 | 2 years to revive unintentionally abandoned end. (for year 8) |
Jul 18 2028 | 12 years fee payment window open |
Jan 18 2029 | 6 months grace period start (w surcharge) |
Jul 18 2029 | patent expiry (for year 12) |
Jul 18 2031 | 2 years to revive unintentionally abandoned end. (for year 12) |