WO2018152365A1 - Activity monitoring system - Google Patents

Abstract

A system for monitoring people's activity and/or health. Monitoring is accomplished by detecting state of people's electronic devices, e.g., a smart phone. When use of the monitored device deviates from an expected use an alert is automatically sent to a monitoring device. The relationships between users are optionally maintained in a social network. Optionally an activity monitoring system receives data from multiple sources such as a home security system, IoT devices and a smartphone. The use of multiple data sources provides an improved activity monitoring system capable of distinguishing normal activity from abnormal activity that may be indicative of a physical or mental health condition. Variations in the monitored activity are used to identify potential health issues for the user. If a health issue is identified, an alert may be sent to a remote third party.

Description

Activity Monitoring System

CROSS-REFERENCE TO RELATED APPLICATIONS

[001] This application claims priority to and benefit of US provisional patent applications Ser. No. 62/459,519 filed Feb 15, 2017; 62/480,537 filed Apr. 3, 2017; 62/553,845 filed Sept. 2, 2017; 62/566,935 filed Oct. 2, 2017 and 62/629,697 filed Feb. 13, 2018. The disclosures of which are hereby incorporated herein by reference.

BACKGROUND

[002] Field of the invention

[003] The invention is in the field of user activity monitoring, and in some embodiments monitoring for detection of medical conditions.

[004] Related art

[005] Medical alert devices have existed for a number of years. These devices enable a user to push a button during a medical emergency in order to make a call for help. There are also mobile applications that report one user's activity to third parties. However, these applications are highly intrusive and report activity without sufficient regard to the user's privacy.

[006] Home security systems include detection devices such as camera, optical motion sensors, window sensors and pressure sensors. Such systems are typically configured to detect intrusion. Health monitoring systems include wearable devices that allow a user to press a button to request help.

SUMMARY

[007] Various embodiments of the invention represent significant improvement over past monitoring systems. For example, mobile devices such as a smartphone, tablet computer, or wearable computer can be used to monitor activity of a user, by detecting use of the mobile device. The monitored activity can include movement, location, use of a device interface, etc. If the monitored activity or lack thereof deviates from an expected use of the device, an alert is generated. For example, alerts may be generated in response to a lack of movement of a device over an extended period, which may be indicative of a problem. By reporting information indicative of a problem, rather than normal every-day expected use of a device, the user's privacy is greatly improved.

[008] The alert may be sent to close friends in a passive social network and/or via a messaging application. Alerts may be sent automatically in response to the monitored activity. As such, the user is not required to explicitly (manually) send an alert. In addition to alerts, which are indicative of problems, a user may choose to send a regular "digest" of their activity to those that follow their activity. A digest typically includes a high-level summary of the user's activity. For example, a daily or weekly digest can include an indication that the user walked more than 2000 steps/day and got out of their house at least once. The digest is configured to provide an indication of the well-being of the user without having to include a detailed private log of their activities. The digests, thus, do not compromise the user's privacy unnecessarily.

[009] The monitored activity can include discrete events such as a rapid deceleration or a visit to a hospital. The monitored activity can include activity patterns such as how long a person sleeps or how often a person leaves home. In some embodiments, expected activity patterns are determined using a machine based analysis of historic activity patterns, e.g., using an artificial neural network or other machine learning system.

[0010] The monitored activity optionally includes monitoring the use of multiple devices. For example, if a user has a smartphone, tablet computer, desktop and home security system, then use of all these devices may be jointly considered in determining whether or not to send an alert. For example, a lack of activity on oil of these devices may indicate a problem and a need to send an alert. In contrast, if the tablet computer and desktop computer are not used for a predetermined period, but the smartphone is used and the home security detects movement within the user's home, then an alert may not be sent. [0011] In some embodiments, a social network includes both a basic and enhanced connection between members. The basic connections are similar to those found in Facebook or Linkedln and allow basic functionality such as text messaging and sharing of content. Enhanced connections allow a first network member to (passively) monitor activity of a second network member. The monitored activity is typically distinct from those activities found in a basic connection. For example, a first user may monitor the movement of a mobile device of the second user, and automatically receive an alert if there is a lack of movement for a predetermined time.

[0012] In some embodiments, a messaging application configured to automatically generate messages between parties. The messaging application can include any of the features found in Facebook

Messenger, WhatsUp, and/or iMessage. In addition, enhanced features allow a first user to (passively) monitor activity of a second user. The monitored activity being distinct from that activities found in traditional text messaging (e.g, the manual sending, and automatic acknowledgement and receipt of messages). For example, a first user may monitor the movement of a mobile device of the second user, and automatically receive an alert if there is a lack of movement for a predetermined time.

[0013] In some embodiments, the activity of a user may also be monitored using movement detectors that are each configured to detect movement within their respective area of regard. Such sensors may be sonic or infrared based, for example. If movement is not detected by a set of movement detectors within a specified time period, then an alert is generated. Optionally a lack of movement within the areas of regard and also lack of movement of a mobile device is required for the automatic generation of an alert.

[0014] In various embodiments, an activity monitoring system uses sensors, such as those found in security systems, personal electronic devices, medical devices and loT (Internet of Things) devices, to detect activity of a user. An alert may be sent to third parties when the detected activity deviates from an expected activity. For example, the activity monitoring system is optionally configured to send an alert in response to a lack of or decrease in activity of the user. A deviation from expected activity can be indicative of a physical or mental health condition. The change in activity can be determined using a plurality of sensors. For example, a lack of activity may be concluded if no activity is detected at any of a set of motion sensors. These motion sensors are optionally configured to both monitor activity of a user and to detect intruders. Sensors of different types of devices may be used to draw conclusions about the activity of a user. For example, if a user is at a grocery store as determined by their smartphone GPS, then a lack of motion detected by their home security system would be considered normal. In contrast, if a user is home and normally gets up early, then a lack of motion detected by their home security system by 10AM may be considered an unexpected deviation from normal activity. Likewise, if a user is active on a tablet computer, that fact that they are not using their smartphone or moving around their home is less relevant than if they were not active on their tablet computer.

[0015] The activity monitoring system does not require an affirmative action by a user in order to send an alert indicating that there may be a problem related to the user's health. To the contrary, an alert may be sent as a result of a lack of action by the user. This approach provides benefit to the user in situations wherein the user is unable to press a button or wherein a health-related issue develops gradually over time.

[0016] The activity monitoring system can receive input from a variety of sources. For example, a user's activity may be monitored using a home security system, a smartphone, an loT (Internet of Things) thermostat, and/or a vehicle GPS system. The abilities to select different inputs and to apply activity analysis logic to data received from these different inputs are distinguishing features of some embodiments. Further, trained machine learning may be configured to use the received data in combination to detect deviations from a particular user's detected activity.

[0017] Machine learning systems are optionally used for several functions of the activity monitoring system. For example, machine learning systems may be used to interpret sensor data and determine a specific activity or level of activity therefrom; and/or machine learning systems may be used to determine an expected activity level for a user.

[0018] Various embodiments of the invention include a computing device comprising: a display (e.g., a touch screen) configured to present a user interface to a user; an I/O configured to communicate data from the computing device using at least one communication channel; activity logic configured to detect use of the mobile computing device, wherein the use comprises use of the user interface, use of the communication channel, movement of the computing device, or any other sensor connected to the mobile computing device; reporting logic configured to report the detected use of the mobile computing device to a remote destination; and a microprocessor configured to execute at least the activity logic. The computing device is optionally a mobile device.

[0019] Various embodiments of the invention include a monitoring system comprising: an I/O configured to communicate to and from remote clients; connection logic configured to establish a relationship between a first of the remote clients and a second of the remote clients in a social network; alert logic configured to provide an alert to the second of the remote clients, the alert being in response to data characterizing use of the first of the remote clients, the data characterizing use indicating deviant use of the first of the remote clients (e.g., use that deviates from expected use), the alert being sent to the second of the remote clients because of the relationship between the first and second of the remote clients; and a microprocessor configured to execute at least the alert logic.

[0020] Various embodiments of the invention include a method of monitoring a person's activity, the method comprising: determining an expected use of a mobile device, the expected use including location of the mobile device, movement of the mobile device or use of a peripheral connected to the mobile device; detecting use of the mobile device; comparing the detected use of the mobile device to the expected use of the mobile device; and sending an alert to a remote location, the alert indicating that the detected use of the mobile device has deviated from the expected use of the mobile device. [0021] Various embodiments of the invention include a method of managing a social network, the method comprising: providing the social network to multiple members, the social network including a basic connection between members and an enhanced connection between members, the enhanced connection including automatic monitoring of use of a mobile device of a first user; detecting a use of the mobile device; determining that the detected use is outside of an expected (predetermined or learned) use pattern; and providing an alert to a second user that the detected use is outside of the predetermined or learned user pattern, the provision of the alert being based on an enhanced connection between the first user and the second user.

[0022] Various embodiments of the invention include a method of managing a social network, the method comprising: receiving data representing a social network including multiple members, the social network further including features that allow text messaging between the members, each of the members having a set of connections to one or more others of the members; and providing an upgrade opportunity to a first of the members, the upgrade opportunity including an ability to establish an enhanced connection between the first of the members and a second of the members, the enhanced connection including automatic monitoring of use of a mobile device of the second of the members and reporting of the automatic monitoring to the first of the members, wherein the monitored use is a use other than the messaging between the first and second members.

[0023] Various embodiments of the invention include an activity monitoring system comprising: a first motion sensor configured to detect movement within a first area of regard; a second motion sensor configured to detect movement within a second area of regard; activity logic configured to determine a lack of movement detected by both the first motion sensor and the second motion sensor for a first predetermined period of time; and reporting logic configured to report the lack of movement for the predetermined period of time to a remote destination. [0024] Various embodiments of the invention include a method of monitoring a first person's activity, the method comprising: providing a first motion sensor having a first area of regard; providing a second motion sensor having a second area of regard; determining that motion has not been detected by either the first or second motion sensor for a predetermined period of time; and providing an alert to a remote destination, the alert indicating the lack of detected motion by either the first or second motion sensor.

[0025] BRIEF DESCRIPTION OF THE DRAWINGS

[0026] FIG. 1 illustrates a block diagram of a passive monitoring network, according to various embodiments of the invention.

[0027] FIG. 2 illustrates a social network having more than one type of connection, according to various embodiments if the invention.

[0028] FIG. 3 illustrates methods of passively monitoring a user, according to various embodiments of the invention.

[0029] FIG. 4 illustrates methods of managing a social network, according to various embodiments of the invention.

[0030] FIG. 5 illustrates methods of upgrading a social network, according to various embodiments of the invention.

[0031] FIG. 6 illustrates methods of monitoring a person's activity, according to various embodiments of the invention.

[0032] FIG. 7 illustrates a sensor based activity monitoring system, according to various embodiments of the invention.

[0033] FIG. 8 illustrates a device selection interface, according to various embodiments of the invention.

[0034] FIG. 9 illustrates methods of generating an alert, according to various embodiments of the invention. [0035] FIG. 10 illustrates methods of training a machine learning system for a particular user, according to various embodiments of the invention.

[0036] FIG. 11 illustrates methods of generating an alert based on a dynamic threshold, according to various embodiments of the invention.

[0037] FIGs. 12A, 12B and 12C illustrate a real-time alert an alert cancellation interface and a digest, according to various embodiments of the invention.

[0038] DETAILED DESCRIPTION

[0039] FIG. 1 illustrates a block diagram of a Monitoring System 100, according to various embodiments of the invention. The Monitoring System 100 is configured to enable a (first) user of a Monitoring Device 120A to monitor activity of a (second) user of a Monitored Device 110A. Monitoring System 100 is configured to make the activity monitoring simple and passive, while at the same time allowing the second user to protect their privacy and optionally to control how their activity is reported. As disclosed herein, the type of monitoring, activity monitoring and privacy controls may vary significantly between embodiments. Monitoring System 100 typically includes multiple Monitored Devices 110 and

Monitoring Devices 120, individually referenced as 110A, HOB... and 120A, HOB, etc.

[0040] Activity monitoring typically occurs via a Network 115 and may be facilitated by a Monitoring System 123. Network 115 can include the Internet, a cellular network, a telephone network, a cable network, and/or any other network configured to communicate digital data. Monitoring System 123 is configured to manage activity monitoring between multiple users, e.g., users of multiple Monitored Devices 110 and/or multiple Monitoring Devices 120. Monitoring System 123 is optionally configured to maintain a social network between the multiple users. This social network establishes which users are followers (monitors) and which are monitored by followers. A user may be both followed and a follower. For example, a specific mobile device may be both an embodiment of Monitored Device 110A and a Monitoring Device 120A. Typical embodiments include many more Monitored Devices 110 and Monitoring Devices 120 than are illustrated in FIG. 1.

[0041] In an exemplary embodiment, Monitored Device 110A is configured to detect physical movement using an accelerometer and/or gyroscope. If physical movement is not detected for a predetermined amount of time, e.g., 15 hours. Then an alert indicating this fact is sent to Monitoring Device 120A. Management of the alert can be performed on Monitored Device 110A and/or Monitoring System 123. The conditions for, content of and criteria for alerts can vary widely and are optionally set by the users of Monitored Device 110A and/or Monitoring Device 120A.

[0042] Monitored Devices 110 can include, for example, a smartphone, a tablet computer, a personal computer, a wearable device (e.g., pet collar, necklace, shoe, watch, ring, bracelet, armband or medical sensor), a television set, smoke or C0₂ detector, a refrigerator, a microwave, a washer, a dryer, a coffee maker, body position sensor, television/internet interface device (e.g., Roku) , a remote control, a telephone, a camera, a vehicle (e.g., car or truck), a stove, a light switch, a motion sensor, a door sensor, a security system, a light, and/or the like.

[0043] Monitored Device 110A optionally includes a Display 125 configured to present a user interface to a user of Monitored Device 110A. Display 125 can include, for example, a touch screen of a smartphone, a security system control panel or a television screen. Display 125 is optionally configured for a user to enter commands or select controls.

[0044] Monitored Device 110A also includes an I/O (Input/Output) 130 configured to communicate data to and/or from Monitored Device 110A. I/O 130 can include, for example a cellular telephone transmitter, a Wifi interface, a Bluetooth interface, a Universal Serial Bus, an Ethernet connection, a coax interface, a fiber optic interface, and/or the like. I/O 130 is configured to communicate data using one or more communication channels. In some embodiments, I/O 130 is configured to communicate via TCP/IP or similar protocol. [0045] Monitored Device 110A further includes Activity Logic 135. Activity Logic 135 is configured to detect use of Monitored Device 110A. In various embodiments, the detected use includes a wide variety of activities. For example, the detected use a can include one or any combination of: movement of Monitored Device 110A, use of Display 125, use of I/O 130, a location of Monitored Device 110A, horizontal deceleration of Monitored Device 110A, vertical deceleration of Monitored Device 110A, charging/power level of Monitored Devices 110A, wifi connection made by Monitored Device 110A, use of a camera included in Monitored Device 110A, use of peripheral device having a direct wired or wireless connection to Monitored Device 110A, execution of a software or hardware application on Monitored Device 110A, detection of sound by Monitored Device 110A (e.g., monitoring of an audio environment), use of Monitored Device 110A to make or receive calls, video sent by Monitored Device 110A, detection of movement in an environment near Monitored Device 110A, detection of signals by Monitored Device 110, measurements made by Monitored Device 110A, control of objects by

Monitored Device 110A, use of a communication channel (e.g., cellular telephone connection, an internet connection, a wireless connection, etc.) to communicate from Monitored Device 110A, and/or the like. Movement of Monitored Device 110A is optionally detected using a gyroscope, an

accelerometer, barometer, a local positioning system, and/or a global positioning system. The detected use of Monitored Device 110 optionally includes the presence of Monitored Device 110 at a geographic location. Importantly, the detected use optionally includes a lack of use in specific time period.

[0046] As used herein, the term "area of regard" is meant to indicate the area in which a sensor can detected movement or other activity. For example, a camera or infrared motion detector may have a "field of view" in which movement can be detected. This field of view would be considered the "area of regard" for these sensors. A pressure sensor under a carpet has an area of regard that includes the part of the carpet on which it may detect a step. Window and door sensors have an area of regard that typically includes the opening and closing of the window or door. Internet of Things (loT) devices may include sensors whose area of regard include a use of that specific device, e.g., opening a refrigerator door or adjusting a thermostat.

[0047] Monitored Device 110 optionally further includes a Motion Sensor 140. Movement Sensor 140 is configured to detect movement of Monitored Device 110 and/or movement within an environment around Monitored Device 110. For example, Motion Sensor 140 can include a gyroscope and accelerometers such as those commonly found in smartphones or table computers. In another example, Motion Sensor 140 includes a camera and logic configured to detect movement in images recorded by the camera, an ultrasonic sensor, microphone, a pressure sensor, an electric eye, an infrared sensor, a light sensor, a vibration sensor, a magnetic sensor, a mechanical sensor, and/or the like. Motion Sensor 140 may be configured to detect motion of a person and/or an object. For example, Motion Sensor 140 may be configured to detect movement of a person within a area of regard, opening or closing of a door, etc. Motion detected by Motion Sensor 140 is reported to Activity Logic 135 and may be considered to reflect a use of Monitored Device 110.

[0048] In some embodiments, one, two or more of Motion Sensors 140 are disposed external to Monitored Device 110. Each of these Motion Sensors 140 typically have a different area of regard in which they can detect motion. For example, one of Motion Sensors 140 may be placed in a bathroom and another of Motion Sensors 140 may be placed in a hallway. In combination, they can detect movement (and lack thereof) in both these spaces.

[0049] Monitored Device 110 optionally further includes a Location Logic 142. Location Logic 142 is configured to determine and report a location of Monitored Device 110. The determination can include interpretation of a signal from a global positioning system (GPS), for mapped Wi-Fi signals, from a local positioning system, from inertial measurements, and/or the like. Location Logic 142 can include an antenna and/or timing circuit configured to receive wireless signals used to determine location. [0050] In some more specific examples, the use of Monitored Device 110A as detected by Activity Logic 135 includes the following.

[0051] 1) Presence or absence of Monitored Device 110A at a specific location, optionally as determined by Location Logic 142. The specific location can be a hospital, police station, employment location, a school, a city, a state, a care facility, and/or the like. For example, Monitored Device 110A may be detected to be at a hospital or not to be at a school. The location may be a critical location such as a hospital or police station.

[0052] 2) Use of a Peripheral Device 172 coupled to Monitored Device 110A. Peripheral Device 172 may be coupled using a wireless or direct wired connection. For example, Peripheral Device 172 may be coupled to Monitored Device IdOA using Bluetooth. The use of Peripheral Device 172 can include any of the uses of monitored Device 110A discussed herein. In some examples, the use of Peripheral Device 172 includes the detection of signals or collection of data using sensors of Peripheral Device 172. For example, use of Peripheral Device 172 can include detection of movement using a camera or ultrasonic movement sensor. Use of Peripheral Device 172 can include detection of a door opening or closing, operation of a vehicle or reading of an RFID tag. Use of Peripheral Device 172 can include detection of a person's actions, movement (e.g., steps) or vitals. For example, the detected use may include opening of a medication container, that a person has visited a bathroom, a blood glucose measurement, how much a person walks, and/or the like.

[0053] 3) Measurement of a physical activity of a user. For example, the use may include a person's steps taken or heart rate as measured by a wearable device. The use may include changing channels or inputs sources on a television or video monitor, optionally via a remote control. The use may include a signal detected from a pressure sensor in a bed or on a floor. [0054] 4) Movement of Monitored Device 110A, including for example, being picked up, turned over, and/or the like. The detected use can include quantitative measurement of acceleration in specific directions.

[0055] 5) Operation of Monitored Device 110A, including, turning on/off, execution of software and/or hardware applications on Monitored Device 110A. These can include use of a camera, microphone, speaker, and/or display. In some embodiments, the detected use of Monitored Device 110A includes predicting and reporting a loss of power to Monitored Device 110A. For example, Monitored Device 110A may be configured to provide a location prior to losing power.

[0056] The use of Monitored Device 110A, as detected by Activity Logic 135, is optionally stored in an Activity Log Storage 137. Activity Log Storage 137 includes a non-transient digital storage such as random access memory, static memory, optical memory, a hard drive, flash memory, and/or the like. Activity Log Storage 137 optionally further includes a data structure configured to store data records of use activity. Activity Log Storage 137 is optionally additionally or alternatively disposed on Monitoring System 123. In an illustrative embodiment, Activity Log Storage 137 is configured to store a record of a time a last movement was detected using Activity Logic 135 and Motion Sensor 140 (or Location Logic 142). This movement can be of Monitored Device 110A or of an object with an environment of Monitored Device 110A. This movement can be small, e.g., Monitored Device 110A was merely picked up or turned over. This movement can be larger, e.g., as may be detected by Location Logic 142.

[0057] Monitored Device 110A further includes Reporting Logic 145. Reporting Logic 145 is configured to report detected use of Monitored Device 110A to a remote destination, e.g., to Monitoring System 123 and/or directly to Monitoring Device 120A. The remote destination can be a cloud based data storage facility. The remote destination is optionally managed by a third party. Reporting Logic 145 may report details of all detected use, an abstracted representation of detected use, a summary of detected use (e.g. a "digest"), and/or a filtered version of detected use. The information reported is optionally selected by a user of Monitored Device 110A using Setup Logic 160 discussed elsewhere herein. Further, in some embodiments, Reporting Logic 145 only reports detected use of Monitored Device 110A if certain criteria are met, and/or the content of information reported may be dependent on meeting some criteria. The information reported may be extracted from other data. For example, a number of footsteps might be extracted from accelerometer data, walking distance might be extracted from footsteps, a car crash extracted from horizontal accelerometer data, a summary over time might be extracted from discrete events, etc. These extractions may be subject to privacy settings selected by a user of Monitored Device 110A.

[0058] In some embodiments, sensor data is partially processed on Monitored Device 110A and then communicated to Monitoring System 123 for further processing. For example, acceleration data indicative of a traffic accident or a dropped phone may first be analyzed first on Monitored Device 110A by Activity Logic 135, the results of this analysis may be then sent to Monitoring System 123 by

Reporting Logic 145 for further analysis, if the acceleration data is likely to represent a reportable event. At Monitoring System 123 more thorough analysis of the data may confirm a traffic accident or dropped phone. In a more specific example, Activity Logic 125 may be configured to detect sharp acceleration events (as detected by an accelerometer), only when these events are above a threshold are they reported to Monitoring System 123. At Monitoring System 123 the acceleration events are further analyzed, perhaps using a machine based system to confirm whether or not they are indicative of a reportable event. The machine based system optionally includes, for example, an artificial neural network trained to identify acceleration patterns as would be expected in a traffic accident.

[0059] For example, Reporting Logic 145 may be configured to report that Monitored Device 110A has not been moved for more than 8 hours during the daytime (or 13 hours at nighttime), to report that Monitored Device 110A experienced a rapid horizontal deceleration such as would be detected during a vehicle accident, to report that Monitored Device 110A is unexpectedly at a hospital, to report that Monitored Device 110A did not go to a grocery store for over a week, to report that Monitored Device 110A did not go to church on Sunday, to report that Monitored Device 110A left a geographic region, and/or the like. Reporting Logic 145 may be configured to report deviations from expected use of Monitored Device 110A as determined by Deviation Logic 160, which is discussed further elsewhere herein.

[0060] In some embodiments, Reporting Logic 145 is configured to respond to a polling signal from Monitoring System 123. The response can be a simple "I'm alive" response or a response that include more data regarding the state of Monitored Device 110A. For example, Reporting Logic 145 may be configured to response to a poll from Monitoring System 123 by providing a report of the use of Monitored Device 110A to Monitoring System 123.

[0061] Alternatively, Reporting Logic 145 may be configured to push reports of activity to Monitoring System 123. The pushed reports may be sent on a regular basis (e.g., at a fixed frequency or period), sent in response to specific activity detected using Activity Logic 135, and/or sent in response to a specific command from a user of Monitored Device 110A. A report is considered an "alert," e.g., a communication configured to alert a user of Monitoring Device 120A of a use (or lack thereof) of Monitored Device 110A, if the report is triggered in response to a specific detected use. Such an alert may be triggered and generated based on any of the uses detected by Activity Logic 135 discussed herein, e.g., Monitored Device 110A has not moved in 14 hours or just experienced a rapid deceleration. The alert may include an identity of Monitored Device 110A, a user's identity, and/or the use of Monitored Device 110A on which the alert was based. Alerts are triggered as a result of specific events (or lack thereof) and may be sent automatically without requiring further action by the user being monitored or a follower of the user. In contrast, digests are typically sent at regular time periods chosen by a user and are sent without being triggered by a specific event (or lack thereof). Embodiments of the invention include either or both alerts and digests. [0062] In some embodiments, Reporting Logic 145 is configured to provide a user of Monitored Device 110A with an opportunity to prevent an alert from being communicated to Monitoring Device 120A. For example, a Confirmation Logic 147 is optionally configured to confirm that an alert should be sent to Monitoring Devices 120. Confirmation Logic 147 is configured to provide notice to a user of Monitored Device 110A that an alert will soon be sent. For example, Confirmation Logic 147 may cause a message to appear on Display 125, may cause Monitored Device 110A to make a sound, may send a text message to Monitored Device 110A, and/or may make a telephone call to Monitored Device 110A. All or part of Confirmation Logic 147 is optionally disposed on Monitoring System 123.

[0063] For example, in some embodiments, Confirmation Logic 147 is configured to present a notice on Display 125. The notice including a message that an alert is about to be sent, contents and/or reasons for the alert (e.g., a deviation from an expected use of Monitored Device 110A), and/or an opportunity to confirm or cancel the alert. The opportunity to confirm or cancel can include a command input (e.g., virtual button). By way of example, a message may be displayed saying that an alert will be sent in 2 minutes because Monitored Device 110A has just detected an abnormal sugar level via an insulin pump. The display includes a button labeled "Cancel," activation of which would cancel the pending alert. The amount of time given to cancel the alert is optionally dependent on the cause of the alert. For example, a short period may be given if Monitored Device 110A has experienced deceleration as would be expected in a car accident while a longer period may be give if Monitored Device 110A has not been moved at all for 12 hours. Confirmation Logic 147 is optionally configured for a user to provide information that would be included in an alert. For example, if the alert is generated because

Monitored Device 110A is at a hospital, the user may add a comment "just picking up medication" or "David hit his thumb with a hammer."

[0064] Monitored Device 110A optionally further includes Filter Logic 150. Filter Logic 150 is configured to summarize use detected by Activity Logic 135. One purpose of Filter Logic 150 is to enhance the privacy of Monitoring System 100, with respect to the user of Monitored Device 110A by applying a privacy filter. The action of Filter Logic 150 can prevent the user from feeling that their every action is being monitored or watched. Specifically, by summarizing detected movement of Monitored Device 110A the only information that need be reported is when the movement triggers an alert rule, which can be set by the user of Monitored Device 110A. For example, the user may select (or agree to a default) that a lack of movement for 15 hours overnight is grounds for an alert. In this case, Filter Logic 150 is configured to eliminate detailed movement data and just report that Monitored Device 110A has not been moved for 15 hours. Filter Logic 150 restricts the information that is included in reports/alerts that are sent by Reporting Logic 145. In typical embodiments, the filtering performed by Filter Logic 150 is configurable by the user of Monitored Device 110A. For example, they may select what actions would cause an alert to be sent, what is included in an alert, and/or a subset of Monitoring Devices 120 to which particular alerts are sent. For example, the user may have alerts that relate to medical conditions, being at a police station etc. sent to close family members and alerts that involve lack of movement of Monitored Device 110A or activation of a home alarm system, to be sent to friends. A user may specify that specific types of uses not be reported by specifying a privacy filter.

[0065] In some embodiments, Filter Logic 150 is further configured to generate digests of a user's activity. Filter Logic 150 is optionally disposed on Monitoring System 123 in addition to or as an alternative to Monitored Device 110A. In this case, part of the filtering is performed on Monitoring System 123.

[0066] Monitored Device 110A optionally further includes a Setup Logic 155. Setup Logic 155 is configured for the user of Monitored Device 110A to customize operation of Activity Logic 135,

Reporting Logic 145, Filter Logic 150, and/or other logic within Monitored Device 110A (as discussed elsewhere herein). For example, Setup Logic 155 may be used to select which use of Monitored Device 110A is included in reports sent by Reporting Logic 145. In some embodiments only use selected by the user of Monitored Devices 110A is reported to third parties. Setup Logic 155 is optionally configured for a user of monitored Device 110A or Monitoring Device 120A to select which detected use of Monitored Device 110A is reported to Monitoring System 123 or Monitoring Device 120A. Setup Logic 155 is optionally further configured for the user of Monitored Device 110A to select which of Monitoring Devices 120 are to receive alerts in response to Reporting Logic 145, e.g., to select who is permitted to be a follower of the user. Setup Logic 155 is optionally configured to customize operation of Monitoring System 100 on a follower by follower basis, allowing different followers to receive different information.

[0067] Examples of the customization for which Setup Logic 155 may be configured include, but are not limited to:

[0068] Setting periods for which non-movement and/or lack of other use of Monitored Device 110A would result in an alert. These periods may be dependent on time of day and/or day of the week.

[0069] Setting locations at which the presence of Monitored Device 110A would cause an alert. For example, a hospital, police station, airport, travel out of county or out of state, doctor's office, and/or the like.

[0070] Setting locations at which absence of Monitored Device 110A would cause an alert. For example, not being at a church on Sunday morning, not being in a class room at an expected time, not being at work during worktime, not being along a delivery route when expected, not being at an appointment, and/or the like. Appointment times may be determined by calendar integration.

[0071] Setting connections with, and alert rules for, peripheral devices such as Peripheral 172. The "alert rules" being rules that result in an alert when broken. E.g., send an alert if blood glucose is detected to be above 300.

[0072] Setting privacy criteria that specify criteria for protecting the privacy of users. The criteria limiting, for example, what use of Monitored Device 110A can be shared with specific Monitoring Devices 120. [0073] Acceptance of followers.

[0074] Setting parameters that define expected use of Monitored Device 110A.

[0075] Selecting apps (executing in Monitored Device 110A) whose use is monitored by Activity Logic

135.

[0076] Setting the content of alerts under various conditions.

[0077] All or part of Setup Logic 155 may be disposed on Monitoring System 123. In this case, the user of Setup Logic 155 may access Setup Logic 155 via a browser or other application on Monitored Device 110A or on a separate computing device.

[0078] Monitored Device 110A optionally further includes Deviation Logic 160. Deviation Logic 160 is configured for determining if use of Monitored Device 110A, as detected by Activity Logic 135, deviates from an expected use of Monitored Device 110A. The detection of the deviation typically results in generation of a report by Reporting Logic 145. The expected use may be defined by alert rules discussed elsewhere herein. The deviation in use may include a temporal and/or a spatial deviation. For example, a use may be time based (e.g., no activity for a day) or location based (presence in an unexpected space)

[0079] The deviations detected by Deviation Logic 160 optionally include more than merely violation of alert rules. The deviations can include deviations from patterns of activity. For example, if Monitored Device 110A is normally taken to a grocery store at least once a week, a failure to do so for two weeks may be grounds for a report to Monitoring System 123 or Monitoring Device 120A. If the user of Monitored Device 110A normally walks for an hour each day (as detected by Motion Sensor 140 or Location Logic 142. A reduction to 10 minutes of walking per day may be grounds for a report and alert.

[0080] The "expected use," to which detected use is compared, may be defined manually by a user of Monitored Device 110A and/or Monitoring Device 120A. The expected use may be defined by predefined (e.g., default) alert rules. Further, the expected use may be defined by looking for and detecting past use patterns. For example, Deviation Logic 160 may be configured to detect a pattern (e.g., frequency, times, etc.) at which the user visits a pharmacy, visits church, goes to work or school, exercises, and/or other class of activity. The detected pattern can be based on the activity of a specific individual being followed, on a group of people having similar characteristics (e.g., women between 60 and 65 years old), on the general population, and/or any combination thereof. For example, an expected use for everyone would be to use the restroom at least once a day, an expected use of women between 60 and 65 may be walking at least 3000 steps a day, and an expected use for a specific person would be to go to her bridge club on Tuesday evenings. The expected use for an individual may change over time. In some embodiments, Deviation Logic 160 includes a machine based system. As used herein a "machine based system" is used to specifically mean: an artificial neural network, artificial intelligence, Bayesian statistical system, deep learning system, machine learning system, expert system, and/or the like. The machine based system is optionally configured to learn (e.g., is trained) from past use of Monitored Device 110A, and detect when a later use deviates from patterns detected in the past use. The past use is optionally based on logs of use stored in Activity Log Storage 137. In some

embodiments, the machine based system is trained based on multiple Monitored Devices 110A used by the same user or by multiple different users, respectively.

[0081] When Deviation Logic 160 detects a use that deviates from the expected use, Reporting Logic 145 is optionally configured to report this detected deviation. As a result, a corresponding alert may be sent to one or more of Monitoring Devices 120.

[0082] Monitored Device 110A optionally further includes Voice Logic 165. Voice Logic 165 is configured to activate a voice channel between Monitored Device 110A and Monitoring Device 120A. For example, Voice Logic 165 may be configured to automatically initiate a call using the mobile computing features of Monitored Device 110A and/or Monitoring Device 120. This call may be in response to a command received from a remote source. For example, in response to an alert received at Monitoring Device 120A, a command may be sent to Voice Logic 165 on Monitored Device 110A. In response to receiving this command, Voice Logic 165 may be configured to place a telephone call from Monitored Device 110A and optionally turn on a "speaker" mode.

[0083] The command sent by Monitoring Device 120A optionally includes authentication data or a security certificate configured to prevent Voice Logic 165 from being used to initiate unauthorized calls. This security feature may be uniquely associated with the corresponding alert.

[0084] Monitored Device 110A optionally further includes Peripheral Monitoring Logic 170. Peripheral Monitoring Logic is configured to monitor and received data from one or more Peripheral 172.

Peripheral Device 172 can include, for example, a vehicle, a wearable device, an earring, a defibrillator, a necklace, a shoe, a medical device, a medicine delivery device, a medication container, an insulin pump, a pacemaker, a wearable activity sensor (e.g, Fitbit^® or AppleWatch^®), a blood/oxygen level detector, a pulse measurement device, a blood pressure measurement device, a prosthetic, a mouse, a keyboard, a camera, an (external) Motion Sensor 140, a vehicle control system, a remote control, a set-top box, an electronic door lock, a door or window sensor, a pressure sensor, a physical security system, headphones (earbuds), and/or the like.

[0085] In some embodiments, Peripheral Monitoring Logic 170 is configured to received data from Peripheral 172 and determine if the data represents an abnormal condition, e.g., an abnormal use of Monitored Device 110A. As noted elsewhere herein, use of Peripheral 172 and/or data received therefrom, can be considered an example of use of Monitored Device 110A. Peripheral 172 and Monitored Device 110A may be connected via a wire, optically, and/or via a wireless connection. For example, in one embodiment Monitored Device 110A is an iPhone^® and Peripheral 172 is an Apple Watch^® connected by wireless Bluetooth^®.

[0086] In some embodiments, Monitored Device 110A further includes Messaging Logic 175.

Messaging Logic 175 is configured to communicate at least text messages (SMS or MMS) between the Monitored Devices 110 and Monitoring Devices 120. For example, a user of Monitoring Device 120A may send texts or images to Monitored Device 110A. In some embodiments, Messaging Logic 175 is configured to display received images using Display 125. These received images (or texts) may appear sequentially or randomly on Display 125 as occurs on an electronic picture frame. The texts or images are optionally sent in response to a daily digest received by Monitoring Device 120A.

[0087] Monitoring System 123 may be configured to both manage activity monitoring between multiple Monitored Devices 110 and multiple Monitoring Devices 120, and also manage a social network between the users of these devices. The social network optionally includes more than one type of connection. For example, in some embodiments, the social network includes a basic connection and an enhanced connection. The basic connection is similar to those found in social networking applications such as Facebook^®, Linkedln^® and Instagram^®. These connections allow manual sharing of content, messaging and automatic acknowledgement that a message was received. The enhanced connections provide the functionality of the basic connections and in addition provide the automated monitoring functions described herein. For example, the enhanced connection may provide automatic alerts of deviations from the expected use of Monitored Device 110A.

[0088] Monitoring System 123 includes an embodiment of I/O 130. This embodiment is configured to communicate via Network 115 to multiple instances of Monitored Devices 110 and Monitoring Devices 120.

[0089] Monitoring System 123 further includes Connection Logic 182. Connection Logic 182 is configured to establish and maintain social connections between users of Monitored Devices 110 and Monitoring Devices 120, and optionally other types of network access devices. The connections can be uni-directional, e.g., from a follower to a person being followed, or bi-directional. A person who is a followed can also be a follower. Embodiments of Connection Logic 182 are optionally included in Monitored Devices 110. [0090] Connection Logic 182 is typically configured to establish connections between people. For example, a first person may request to follow a second person, following approval by the second person, a connection is established. The second person can set alert rules, privacy criteria and the like using Setup Logic 155. The rules and criteria may be applied to all followers of the second person or to a specific follower. Thus, alert rules and privacy criteria can be specified on an individual basis if desired. Part of Setup Logic 155 may be disposed within Connection Logic 182 for this purpose.

[0091] Connection Logic 182 may also be configured to establish which Monitored Devices 110 are associated with which users. For example, a user may have a smartphone, tablet computer, home security system, and personal glucose sensor. The user may use Connection Logic 182 to identify which Monitored Devices 110 are to be monitored on their behalf. Further, Connection Logic 182 may be configured to identify which Monitoring Devices 120 alerts should be sent to. For example, a follower may designate that alerts should be sent via text message to a cell phone and via e-mail to an e-mail account.

[0092] Connection Logic 182 is optionally configured to provide basic social networking functions such as those found on FaceBook^® or Instagram^®. These functions include sharing of content, messaging between connections, and the like.

[0093] In some embodiments, Connection Logic 182 is configured to manage a social network having at least two different types of connections between members. These connections include a basic connection having the basic social networking functions of the prior art, and an enhanced connection that includes the monitoring of user activity and generation of alerts when use of Monitored Device 110A meets the criteria for sending an alert to Monitoring Device 120A. A managed social network optionally includes at least a basic connection between all connected members, and an enhanced connection between a subset of the connected members. [0094] FIG. 2 illustrates a Social Network 200 having more than one type of connection, according to various embodiments if the invention. A Basic Connection 210 is indicated by a solid line and an

Enhanced Connection 220 is indicated by a dashed line. Optionally, the Enhanced Connections 220 include all of the properties of the Basic Connections 210 and also additional functionality. The members of Social Network 200, individually identified as 230A, 230B, etc., can have Basic Connections 210 in which both members have equal roles (symmetric). Further, they can have Enhanced

Connections 220 that are directional, one member being followed and the other member being a follower (asymmetric). The same pair of members can have both types of connections at the same time. In FIG. 2, arrowheads are used on Enhanced Connections 220 to indicate who is following whom. For example, Sophie 230A and Nori 230B are following each other, while Hans 230G is following Nicky 230E, but Nicky 230E is not following Hans 230G. Even while the Enhanced Connection 220 between Hans 230G and Nicky 230E is asymmetric they may simultaneously have a Basic Connection 210 that is symmetric.

[0095] In some embodiments, Connection Logic 182 is configured for a member of Social Network 200 to upgrade a connection to another member from a Basic Connection 210 to an Enhanced Connection 220. Such an upgrade may be suggested by a manager of Social Network 200, and may involve a fee or other consideration. For example, the manager of Social Network 200 may suggest an upgrade between members of Social Network 200 that are identified as family members. The manager may be Facebook, Inc. or Linkedln, Inc. etc.

[0096] In some embodiments, Connection Logic 182 is configured for a user to register multiple Monitored Devices 110 to a single account. For example, the user Artemis 230C may have a

smartphone, a tablet computer, and additional personal electronic devices, each of which is a

Monitored Device 110. The use of all the registered devices registered to Artemis 230C's account can be used to monitor her activity in parallel. [0097] The use of Connection Logic 182 to create an Enhanced Connection 220 optionally includes using Setup Logic 155 to establish alert rules and privacy criteria for the Enhanced Connection 220. All or part of Setup Logic 155 may be disposed on Monitoring System 123. For example, Artemis 230C may request to follow Sophie 230A in an Enhanced Connection 220 (an upgrade of their existing Basic Connection 210). Connection Logic 182 is configured to send Sophie 230A an option of accepting the request from Artemis 230C. If Sophie 230A accepts the request, Connection Logic 182 typically directs Sophie 230A so that she can choose how information regarding her activities is provided to Artemis 230C in activity alerts. Optionally, a selection of default privacy levels is provided, each of which can be further customized.

[0098] Monitoring System 123 typically further includes an Alert Data Storage 184 configured to store alert rules, privacy criteria, and/or any other data indicating under which conditions the an alert should be sent to one or more members of Monitoring Devices 120. This data stored in Alert Data Storage 184 may include default rules/criteria and/or rules/criteria specified using Setup Logic 155. Alert Data Storage 184 optionally further includes account information of users of Monitoring Devices 120. This account information can include enhanced connections (discussed elsewhere herein), names, telephone numbers, e-mail addresses, IP addresses, MAC addresses, and/or the like. Such account information can be used to direct alerts to the proper locations. Alert Data Storage 184 optionally further includes a log of alerts sent and/or records of use received from Monitored Devices 110. Alert Data Storage 184 optionally includes data structures specifically configured for storing the data discussed herein.

[0099] Monitoring System 123 typically further includes Alert Logic 186 configured to provide an alert to one or more of Monitoring Devices 120. The same alert is optionally sent to multiple Monitoring Devices 120. The alert is sent in response to data characterizing use of the first of one or more of Monitored Devices 110. For example, an alert may be sent in response to use data received from Reporting Logic 145. Alert Logic 186 may be configured to compare received use data with alert rules stored in Alert Data Storage 184, and if the actual use represented by the received use data violates a rule that an alert may be sent. The contents and the recipients of the alert is governed by privacy criteria. Specifically, if the actual use of Monitored Device 110A is found to be outside of the expected use, e.g., is an abnormal use, then an alert is generated by Alert Logic 186. The abnormal use can, of course, be a lack of use. The use data is received from Monitored Device 110A because the user has an enhanced connection with at least one follower, e.g., with a user of Monitoring Device 120A.

[00100] In some embodiments, Alert Logic 186 is configured to associate multiple Monitored Devices 110 with a single user and to apply alert rules to the Monitored Devices 110 as a group. For example, if an alert rule includes that a device be moved or touched at least once a day, that rule could be applied such that at least one of a group of devices is moved or touched then the use is considered to be within the "expected use." As applied, this means that if a user has a smartphone, a tablet computer, a monitored vehicle and a front door motion sensor, the activation/movement/use of any of these devices indicates that the user is doing things (e.g., not sick or fallen) and an alert need not be sent. Only if none of these devices is used is an alert sent. Such relationships between Monitored Devices 110 is optionally established using Setup Logic 155 on Monitoring System 123 or Monitored Device 110A. wherein the alert logic is configured to compare the alert data to the data characterizing the use of the first of the remote clients and to provide the alert in response to this comparison

[00101] Alert Logic 186 is optionally configured to use Deviation Logic 160 disposed on Monitored Device 110A and/or Monitoring System 123. As discussed elsewhere herein, Deviation Logic 160 is configured to determine if an actual use of one or more of Monitored Devices 110 deviates from an expected use.

[00102] Monitoring System 123 optionally further includes Modeling Logic 192. Modeling Logic 192 is configured to model the use of one or more Monitored Devices 110. The model is configured for distinguishing between expected use and a use that is not expected, e.g., deviates from the expected use. Modeling Logic 192 is optionally configured to train a machine based system to distinguish between the expected use and the use that is not expected. Modeling Logic 192 is optionally configured to train the artificial intelligence system based on use of multiple monitored devices used by different users. Modeling Logic 192 is optionally configured to train the artificial intelligence system based on a specific user and a resulting trained artificial intelligence system is customized to the specific user. In a specific example, Modeling Logic 192 may start with a machine based system trained based on the activities of a multiple users, and then further train this machine based system based on the historic activities of a particular user. The multiple users may include a group to which the particular user is a member. For example, if the particular user may be a member of a group consisting of men 55-60 years old that are former professional athletes or the particular user may be a member of a group consisting of female college students of a specific race. A wide variety of criteria can be used to define such groups. A model produced by Modeling Logic 192 can be used by Deviation Logic 160 to determine if actual usage of Monitored Device 110 is abnormal.

[00103] Monitoring System 123 optionally further includes Polling Logic 188 configured to poll members of Monitored Devices 110. This polling can be used to determine if Monitored Device 110A is operational. The response to a polling request can be considered a use of Monitored Device 110A to be considered by Deviation Logic 160.

[00104] Monitored Device 110A and/or Monitoring System 123 further include a Microprocessor 180. Microprocessor 180 includes a microprocessor, an ASIC, a programmable logic array, a communication circuit, a central processing unit, and/or the like. Microprocessor 180 is typically configured to perform specific tasks by the addition of software and/or firmware. For example, Microprocessor 180 may be configured to execute Activity Logic 135, Reporting Logic 145, Deviation Logic 155, Modeling Logic 192, Alert Logic 186, and/or any of the other logic discussed herein. [00105] Monitoring Device 120 can include any communication device capable of receiving an alert message. In various embodiments Monitoring Device 120 includes a smartphone, personal computing device, e-mail account, and/or the like. Monitoring Device 120 includes a Monitoring Interface 196 configured to receive an alert and present the received alert to a user. The alert can be tactile, audible, and/or visual.

[00106] Monitoring Device 120A optionally includes Alert Response Logic 198 configured to respond to a received alert. Alert Response Logic 198 may be configured to send a text message or place a call to Monitored Device 110A. In some embodiments, Alert Response Logic 198 is configured to automatically connect a call to Monitored Device 110A via Voice Logic 165.

[00107] FIG. 3 illustrates methods of passively monitoring a user, according to various embodiments of the invention. In these methods, a user of Monitored Device 110A is monitored and alerts are generated according to an established set of alert rules. These rules can result in an alert as a result of specific actions and/or as a result of a lack of action. The methods illustrated by FIG. 3 may be performed using Monitored Devices 110 and/or Management Server 123.

[00108] In an optional Receive Settings Step 310, a set of alert rules and/or privacy criteria are received. These may be received at Monitored Device 110 and/or Management Server 123. The alert rules and/or privacy criteria are used to control issuance of and/or content of alert rules. The received alert rules are may be received from Monitored Device 110A and/or from Monitoring Device 120A. Typically, a user of Monitored Device 110A has an option to approve or disapprove any alert rules and privacy criteria. Receive Settings Step 310 is optional in embodiments wherein a default set of alert rules and/or privacy criteria are established. Receive Settings Step 310 is optionally performed using Setup Logic 155.

Different alert rules and privacy criteria are optionally set received for different Monitoring Devices 120A. The received rules and criteria optionally apply to more than one Monitored Device 110 associated with the same user. 18 018426

[00109] As discussed elsewhere herein, the alert rules can relate to specific events, e.g., presence at a hospital or police station, and also may relate to a lack of specific events, e.g., a lack of movement or other user of Monitored Device 110A for a period of time. The alert rules and/or privacy criteria are optionally received by using Setup Logic 155 to provide a user interface to Display 125 that is configured to request that a user modify a set of default alert rules and/or privacy criteria. The alert rules and privacy criteria received in Receive Settings Step 310 can include any of those discussed elsewhere herein.

[00110] Receive Settings Step 310 optionally further includes receiving identities of Monitored Devices 110 and/or Monitoring Devices 120. For example, a user may designate their cellular phone, iPad, desktop computer, car and/or home security systems as monitored Devices 110. Each of these devices can be associated with one particular user. For example, a user may designate that their car can report an accident to Management Server 123, that at least one of their cellular phone, iPad and desk computer be used at least once every 16 hours, and/or that their home security system detect movement within their home at least once a day. The alert rules may include logical relationships between these designations. For example, an alert may be sent only if none of the computing devices are used and the home security system doesn't detect any use during the same period. The sending of an alert is, thus, dependent on the use of several monitored devices, which may be separate and independent of each other.

[00111] Receive Settings Step 310 optionally further includes receiving privacy criteria from a user of Monitored Device 110A or Monitoring Device 120A. Privacy criteria can include: specific criteria of what information about a user's activity can be sent to third parties. This information may be sent as part of a digest and/or as part of an alert. For example, a privacy policy may specify that location information may not be disclosed unless Monitoring Device 120A is involved in a vehicle accident, found at a police station, found at a hospital, and/or the like. Privacy criteria are optionally dependent on the Monitoring Devices 120 to which the information is being sent. Thus, one may provide more personal information to some followers relative to other followers.

[00112] With respect to digests, Receive Settings Step 310 can include privacy criteria for determining what to include in digests and how often digests are to be provided to Monitoring Devices 120. For example, a user may specify that daily digests include a general characterization of how active a user was for the day, e.g., activity ranked on a scale of 1-5. Such a ranking can be calculated by Activity Logic 135 and can be based o , how many steps the user took, use of peripheral devices (e.g., a TV remote), if the user left their house, if the user went to work, and/or the like. Further, the user may specify that a weekly digest includes a graph showing relative activity for each day of the week. A user may provide for adding manually entered comments in a digest, thus the user can add statements such as "I felt great today" or "I'm lonely" to a digest.

[00113] In Receive Settings Step 310 a user can optionally designate alert cancellation criteria. These criteria provide users' of Monitored Devices 110 an opportunity to cancel an alert. A user may specify that there should be 3 minute delay if an alert is related to an vehicle accident, a 15 minute delay if an alert is related to presence at a hospital and a 30 min delay if an alert is related to a lack of movement for a period of time. Typically, cancellation of an alert is accomplished by posting a notice that an alert will occur shortly on Display 125. The notice may indicate the reason for the alert, a time remaining to cancel the alert, and inputs configured to cancel the alert and or send it immediately.

[00114] In some embodiments, Receive Settings Step 310 includes receiving data related to a machine based system configured to characterize use of Monitored Device 110A. For example, Receive Setting Step 310 may include receiving coefficients for an artificial neural network trained to distinguish expected use from deviant use of Monitored Device 110A. These coefficients are optionally specific to the user of Monitored Device 110A, and/or to a group of which the user is a member. [00115] In some embodiments, Receive Settings Step 310 includes identification of Peripheral Devices 172, in direct communication with Monitored Device 110A. Peripheral Devices 172 can be assigned any of the settings, e.g., alert rules and privacy criteria, etc., discussed wherein with respect to Monitored Device 110A.

[00116] In a Determine Expected Use Step 315, an expected use of Monitored Device 120A is determined. In a simple implementation, the expected use is merely that the use will not violate alert rules received in Settings Step 310 and/or a default set of alert rules. The expected use can include a location of Monitored Device 110A. For example, the expected use can include that Monitored Device 110A will not be at a hospital, will be at church on Sunday mornings, will leave a home of a user at least once a day, will be present at a school in certain hours, will not leave a defined geographic area, and/or the like. The expected use can include a movement of the Monitored Device 110A or a Peripheral Device 172 connected to Monitored Device 110A. For example, the expected use can include not traveling at a speed greater than 75 mph, walking at least 5000 steps per day, being picked up at least once in a predetermined time period, opening of a door, flushing of a toilet, getting out of bed as determined by a pressure sensor, activation of a pressure sensor or motion detector, and/or the like. In some embodiments, the expected use includes use of Internet of Things (loT) devices, use of a vehicle (e.g., car or motorized wheelchair), and/or use of a security system.

[00117]The expected use can take into consideration multiple devices. For example, in may be expected that the user use at least one of a vehicle, a tablet computer, a cell phone or home motion sensors at least once every 12 hours. If just one of these devices is used, then the expected use is satisfied.

[00118] In a Detect Use Step 320, the use of Monitored Device 110A is detected. The use may be detected in a variety of ways. For example, if Monitored Device 110A is a mobile device, e.g., a smart phone or tablet computer or vehicle, then the detected use may be detected by receiving a signal from Motion Sensor 140, a gyroscope, accelerometer, or Global Positioning System (GPS). The use may be detected by detecting use of Display 125 and/or a specific application on Monitored Device 110A. The detected use of a tablet computer or smartphone may include merely picking up the device.

[00119]The use detected in Detect Use Step 320 can include detection of loT devices or a security system. For example, opening of a smart refrigerator door, use of a bathroom, adjustment of a thermostat, use of a remote control (e.g., a TV remote), opening of a door or window as detected by a security system, placing or removing weight from a pressure sensor, sue of a dishwasher, use of a washer/dryer, noise detected by a microphone, motion detected by an infrared motion detector, motion detected by a camera, use of a mechanical bed, turning on/off lights or other appliances, use of a CO sensor, use of a smoke/fire sensor, use of a stove or oven, use of a toothbrush, use of a door lock, use of a firearm, use of a heater or air conditioner, use of a temperature sensor, use of electricity, use of a coffee maker, use of a toaster, use of a mechanical chair, use of a television, use of an audio system, use of a wearable device, use of a battery charging device, use of a personal computer, and/or the like.

[00120)The use detected in Detect Use Step 320 optionally includes detecting use of multiple

Monitored Devices 110 and/or of Peripheral 172. For example, the detected use may include use of an Apple Watch™, a Fitbit™, a glucose sensor, a heart sensor, an insulin pump, a pacemaker, an automatic defibrillation device, a pulse monitor, electronic glasses, a prosthetic, an oxygen sensor, a hearing aide, and/or the like. More specifically, the detected use may include determining that a user is asleep at night based on a heart sensor and that upon waking they use the restroom, turn on the TV and check their messages on their smartphone.

[00121] Note that the use detected in Detect Use Step 320 optionally includes a lack of use.

[00122] In an optional Poll Step 325, Management Server 123 sends message to Monitored Device 110A and receives a response if Monitored Device 110A is on and functional, e.g., awake. Lack of response for a designated period is optionally grounds for sending an alert. Poll Step 325 is optionally performed using Poll Logic 188.

[00123] In a Compare Step 330, the use detected in Detect Use Step 320 is compared with the expected use as determined in Determine Use Step 315. This comparison may be performed by Activity Logic 135 and may be performed on either Monitored Device 110A or Management Server 123. If the detected use deviates from the expected use, then an alert may be sent to Monitoring Device 120A. In one example, the expected use is determined in part by alert rules set in Receive Setting Step 310. These alert rules include that the user use at least one of their television, smartphone, personal computer or tablet computer at least once a day. If the detected use does not include use of any of these devices for a day, then an alert may be sent.

[00124] In an optional Filter Step 335, the use as detected in Detect Use Step 320 is filtered using Filter Logic 150. This filtering is optionally performed according to privacy criteria set in Receive Settings 310. The filtering optionally results in creation of a summary of detected use, e.g., a digest of the detected use. The detected use may be filtered on Monitored Device 110A and/or on Management Server 123 (using an embodiment of Filter Logic 150 included therein). Filtering of the detected use an improve privacy.

[00125] Filtering of the detected use is optionally dependent on a destination of an alert or a digest. For example, a user may have indicated that a greater amount of information be sent to Monitoring Device 120A relative to Monitoring Device 120B.

[00126] In an illustrative embodiment, prior to sending an alert, Filter Step 335 includes removal of all detected use that isn't relevant to the alert. Specifically, if the alert is a result of Monitored Device 110A visiting a hospital or being in a car accident, then the location of the hospital or accident may be included in the alert, but additional information as to where a user has traveled is removed. Prior to sending a digest, Filter Step 335 may include removing information as determined by privacy criteria. This information may be summarized, e.g., stating merely that the user was "inactive," "somewhat active," "active" or "very active" based on the amount of activity detected.

[00127] In an Alert Step 340, an alert is sent to one or more of Monitoring Devices 120. The alert may be sent from Monitored Device 110A or from Management Server 123. The alert is based on the comparison of Compare Step 330 and a determination therein that an alert rule was violated and/or that the actual use deviated from the expected use. Alert Step 340 is optionally performed using Alert Logic 186.

[00128]The alert may be sent to a specialty application executing on Monitoring Device 120A, e.g., to an application supporting Monitoring Interface 196. Alternatively, the alert may be sent as a voice call, a text message or e-mail. In some embodiments, Alert Step 340 includes providing the user of Monitored Device 110A an opportunity to cancel the alert or add information to the alert. For example, this user may provide text indicating that she is only at the hospital to visit the pharmacy.

[00129]Typically, the alert includes an explanation as to why the alert is being sent. For example, that Monitored Devices 110A has not been moved, that a person has not gotten out of bed, that a person is in unusual location, a person has only walked 300 steps in a day, and/or the like. An alert may be sent to more than one Monitoring Devices 120.

[00130] In some embodiments, Alert Step 340 includes sending a response to the alert from Monitoring Device 120A to Monitored Device 110A. This response may be initiated using Monitoring Interface 196 and/or may use Voice Logic 165 to open a voice channel. The response may include text message(s), voice communication, and/or the like.

[00131] FIG. 4 illustrates methods of managing a social network, according to various embodiments of the invention. In these methods, a social network includes two types of connections, referred to herein as "basic" and "enhanced" connections. The enhanced connection including automatic monitoring of use of Monitored Devices 110. The monitoring including generation of alerts if use of the Monitored Devices 110 deviates from an expected use and/or violates alert rules set by users of the Monitored Devices 110. Typically, the basic connection does not include automatic monitoring of the use of the mobile device of the first user.

[00132] In a Provide Network Step 410, a social network is provided to multiple members. The provided social network includes basic connections between some members and also enhanced connections between a subset of those members having basic connections. The enhanced connections are optionally one-way, e.g., between a follower and person being followed. The basic connections may be similar to those found in Facebook™, Linkedln™, Snapchat™ and Instagram™. Provide Network Step 410 optionally includes an embodiment of Receive settings Step 310 for each network member that is part of an enhanced connection, or a followed member of the enhanced connection.

[00133] In an embodiment of Detect Use Step 320, discussed elsewhere herein, the use of Monitored Devices 110 are detected. This monitoring is optionally only performed for those members of

Monitored Devices 110 associated with network members that are followed members of an enhanced connection, e.g., for Monitored Device 110A.

[00134] In a Determine Deviation Step 430, it is determined that the detected use of Monitored Device 110A is outside of the expected use and/or alert rules are violated. Determine Deviation Step 430 optionally includes Determine Use Step 315, Detect Use Step 320, Poll Step 325, and/or Compare Step 330.

[00135] In an optional Confirm Step 440, the user of Monitored Device 110A is provided with an opportunity to cancel automatic delivery of the alert to a second member of the social network, e.g., to a follower of the user of Monitored Device 110A who is associated with Monitoring Device 120A.

[00136] If the second member does not take assertive action to cancel the alert within a predetermined time period, the alert is sent to Monitoring Device 120A in an embodiment of Alert Step 340. As discussed elsewhere herein, in Alert Step 340 an alert is provided to a second user associated with Monitoring Device 120A. The alert indicates that the detected use of Monitored Device 110A has deviated from the expected use. The provision of the alert to the second user is based on an enhanced connection between the first user and the second user.

[00137] FIG. 5 illustrates methods of upgrading a social network, according to various embodiments of the invention. In these methods, a number of enhanced connections relative to basic connections in a social network is increased. For example, a social network having 100 basic connections and 0, 2 or 10 enhanced connections, may be upgraded to include at least 15 or 20 enhanced connections for every 100 basic connections. In some embodiments, a user may pay for enhanced connections.

[00138] In Provide Network Step 410, the data representing a social network including multiple members is received. This data may include information characterizing members of the network and. which members have basic connections with each other. The social network optionally further including features that allow text messaging and sharing of content (e.g., videos, images or links) between the members. Each of the members of the social network has a set of basic connections to one or more other members of the social network.

[00139] In Offer Upgrade Step 520, one or more members of the social network are provided an upgrade opportunity. The upgrade opportunity includes an ability to establish an enhanced connection between the first of the members and a second of the members of the social network. The enhanced connection includes automatic monitoring of use of a mobile device, e.g, of Monitored Deice 110A, of the second of the members and reporting of the automatic monitoring to the first of the members, e.g., reporting to Monitoring Device 120A. The automatic monitoring includes detection of use that violates alert rules and/or deviates from an expected use of Monitored Device 110A. This excludes expected use such as an acknowledgement that a user has read a text massage, that Monitored Device 110A is low on power, or that a user is in an expected location. [00140] Optionally, the automatic monitoring includes detection of movement of the mobile device using an accelerometer or gyroscope. This movement can be as small is picking up or rotating the mobile device.

[00141] Optionally the enhanced connection is enhanced relative to a basic connection between the first and second members, the basic connection not including automatic monitoring of user of the mobile device of the second of the members.

[00142] In a Monitor Step 530, the use of Monitored Device 110A is monitored using the methods and/or systems discussed elsewhere herein. For example, using the methods illustrated in FIG. 3.

[00143] In an embodiment of Alert Step 340, an alert is sent to Monitoring Device 120A based on the monitoring. The alert is sent if the use of Monitored Device 110A deviates from and expected use and/or violates an alert rule agreed to by the user of Monitored Device 110A. As noted elsewhere herein, the alert is optionally based on a lack of use includes a lack of movement of Monitored Device 110A. The alert is optionally based on receiving a report that the mobile device has not been used for a period of time and automatically reporting the lack of use to monitoring Device 120A.

[00144] FIG. 6 illustrates methods of monitoring a person's activity using multiple sensors, according to various embodiments of the invention. In these methods, the outputs of the multiple sensors are used to determine if an alert should be sent. Some alert rules are dependent on the output of either sensor, some alert rules are dependent on the outputs of one sensor but not others, some alert rules are dependent on multiple sensor outputs.

[00145] For example, if a first sensor is an accelerometer within a smartphone, then one alert rule may be that an alert should be sent if the smartphone undergoes a deceleration indicative of a car accident. This alert rule is optionally dependent on the output of just the first sensor. In another example, if the first sensor is a accelerometer in a smartphone and a second sensor is a pressure pad under a carpet. Then an alert rule may specify that if the smartphone isn't moved and the pressure pad does not detect a step for a period of time, then an alert should be sent.

[00146] In a Provide 1^st Sensor Step 610, a first sensor having a first area of regard is provided. In a Provide 2^nd Sensor Step 620, a second sensor having a second area of regard is provided. The first and second sensors may either or both be motion sensors. The first and second sensor may include any combination of the sensors discussed elsewhere herein. In some embodiments, both the first sensor and the second sensor are both part of a home security system.

[00147] In a Detect Step 630, outputs of the first and second sensors are considered. For example, in some embodiments, it is determined that motion has not been detected by either the first or second sensor for a predetermined period of time. This may mean that the user of Monitored Device 110A has neither picked up their phone nor walked down the hall to the bathroom in the time period under consideration. Alert rules optionally specify that Boolean operations be applied to the outputs of the first and second sensors in order to determine if an alert should be sent.

[00148] In Alert Step 340, an alert is provided to a remote destination, e.g., Monitoring Device 120A. The alert may indicate a lack of detected motion by both or either the first and second motion sensor. The alert is optionally sent to a plurality of Monitoring Devices 120. Typically, the Monitoring Devices 120 to which the alert is sent are associated with followers of a person associated with Monitored Device 110A.

[00149] FIG. 7 illustrates a sensor based Activity Monitoring System 1100, according to various embodiments of the invention. Activity Monitoring System 1100 is optionally an embodiment of Monitoring System 100, or included in an embodiment thereof. In these embodiments, a variety of different sensors are used to detect the activity of a user. These sensors may be embodied in different types of devices. Data received from the sensors are optionally used in combination. For example, an unexpected lack of activity may be determined using a combination of sensors in a smartphone, a personal computer and motion detectors that are part of a home security system. The lack of activity is determined based on a lack of detected activity in any of the devices. Thus, even if no activity is detected on the smartphone, the user is considered active if activity is detected on the home security system. Activity Monitoring System 100 can include mobile device, a cloud-based computing system, a server, and/or distributed set of computing devices.

[00150] As used herein, "different types of devices" are devices of different primary functionality or different form factor. For example, smartphones having different operating systems would both be considered devices of the same type, but a smartphone and a tablet computer would be considered different devices because the tablet computer does not include the primary functionality of communications via a cellular network. A tablet computer and a laptop computer would be considered different types of devices because of their different form factors. Further examples of different types of devices include wearable devices, TV remotes, video display devices, internet TV devices, smartphones, home security components, vehicles, thermostats, loT appliances, heart beat sensing devices, glucose sensing devices, blood pressure sensing devices, a motion detector, a security device, a bed pressure detector, a toilet use detector, an entry detection device, a vehicle, a medical device, a thermostat, a personal assistant, a television or television remote, a microwave, a stove, a refrigerator, a tablet computer, a personal computer, a toothbrush, a coffee maker, a smoke detector, and/or the like.

[00151] Activity Monitoring System 100 includes multiple Monitored Devices 110, individually referenced as Monitored Device 110A, HOB, HOC, etc. Monitored Devices 110 can include any combination of the various devices discussed herein. As discussed, Monitored Devices 110 are configured to monitor activity of a user using Sensors 1115, such as Motion Sensor 140. Different types of Monitored Devices 110 and Sensors 1115 can detect different types of activity. For example, a smartphone may use motion sensors that detect motion of the smartphone to detect a number of steps a person takes or the evenness of their gait. A medical device may detect glucose levels, electrical signals within a user's body, heart rate, and/or the like. Pressure sensors may detect movement within a house, a user laying in bed or use of a toilet. Each of Monitored Devices 110 includes at least one of Sensors 1115, individually referenced as 1115A, 1115B, etc.

[00152] Sensors 1115 may detect different physical phenomena and transduce these to electrical signals. Sensors 1115 my optionally further digitize and communicate the electrical signals to other parts of Activity Monitoring System 100. Sensors 1115 may detect pressure, motion, orientation, chemicals, temperature, mass, strain, sound, light, voltage, current, location, acceleration, physiological conditions, and/or the like. Sensors 1115 may include a keyboard or touch screen.

[00153] Activity Monitoring Systems 100 further includes Data Input 1120 configured to receive the electrical signals from Sensors 1115. As Monitored Devices 110 can include a wide variety of devices, these devices may communicate to Data Input 1120 via a variety of different communication channels. For example, communication between Monitored Device HOB and Data Input 1120 may occur through a Network 125. Network 125 can include the internet, a local area network, a wireless network, a cellular network, a telephone network, a digital network. In one illustrative example, Monitored Device 110A is a smartphone that communicates data using a cellular data network; Monitored Device HOB is a tablet computer that communicates data using a virtual private network connected to the internet; and Monitored Device HOC is a home security system that communicates data via a telephone network. The data communicated can include raw sensor data, partially processed sensor data, and/or conclusions generated from the analysis of sensor data. Data Input 1120 can include modems, gateways, firewalls, serial ports, Ethernet ports, radio frequency antennas, and/or computing instructions configured to receive data generated using or derived from Sensors 1115.

[00154] Activity Monitoring System 100 further includes Activity Analysis Logic 1130. Activity Analysis Logic 1130 is configured to determine an activity level of a user based on data generated using Sensors 1115 and optionally received via Data Input 1120. All or parts of Activity Analysis Logic 1130 is optionally disposed on members of Monitored Devices 110. For example, part of Activity Analysis Logic 1130 may be disposed as an application on a smartphone or tablet computer. This part of Activity Analysis Logic 1130 may be used to perform initial processing of data generated using Sensors 1115, the output of this initial processing may then be sent via Network 125 to other parts of Activity Analysis Logic 1130 for further processing.

[00155] Activity Analysis Logic 1130 is configured to detect changes in a person's activity. Changes in a person's activity can be suggestive of a wide variety of medical conditions. By way of example:

a) depression may be indicated by isolation (not going out), the use of online social networks (rather than face-to-face interaction), changes in sleep patterns; and/or lack of physical activity; b) sleep disorders may be indicated by frequent waking and irregular sleep patterns;

c) digestive disorders may be indicated by frequent visits to the toilet;

d) diabetes may be indicated by frequent urination or getting up several times during the night; e) mental illness (of which there are many varieties) may be indicated by erratic or repetitive behavior, by dramatic changes in activity levels or by changes in social patterns;

f) arthritis may be indicated by changes in physical activity, for example, typing or walking speed; g) cardiac distress may be indicated by a reduction in a person's ability to walk a distance without breaks or to climb stairs at a steady pace;

h) anemia may be indicated by a decline in general physical activity;

i) alcoholism may be indicated by visits to locations selling alcohol, by frequent occurrence of an unsteady erratic gait or by driving patterns;

j) memory loss may be indicated by an inability to remember passwords, by becoming lost or by forgetting keys or a smartphone;

k) stroke may by indicated by a sudden change in gait, loss of balance or by differences in typing speed between the right and left hand; I) vision loss may be indicated by changes in display font size or frequent movement of a smartphone toward and away from the eyes;

m) loss of joint function (e.g., hip) may be indicated by changes in walking speed, uneven gait or reduced physical activity;

n) physical therapy progress may be indicated by range of motion;

o) compliance with advice to elevate a limb may be indicated by limb position;

p) asthma may be indicated by a shortening of periods of physical activity;

q) allergy may be indicated by seasonal changes in physical activity;

r) colds and flu may be indicated by a reduction in physical activity and extended time spent in bed or at home;

s) fatigue and low energy may be indicated by a decline in physical activity;

t) hearing loss may be indicated by a gradual increase in volume settings on electronic devices; u) kidney disease may be indicated by changes in urination patterns;

v) Parkinson's disease may be indicated by muscle tremors;

w) dementia may be indicated by a reduction in ability to remember things (e.g., passwords), changes in typing speed, getting lost, or changing in driving patterns;

x) stress may be indicated by changes in sleep patterns and physical activity; and/or

y) cancer may be indicated by activity related to the impacted organ or organs, for example

Pancreatic Cancer may be indicated by a decrease in appetite, brain cancers may have indications similar to stroke, but with slower onset, leukemia may have indications similar to anemia.

[00156] Activity Analysis Logic 1130 can be configured to detect these and many other activity changes that may be indicative of health problems. [00157] Activity Analysis Logic 1130 is optionally configured to determine the activity level of a user based on a set of rules. For example, if the user's smartphone is determined to be at a hospital using GPS sensors, then the activity level of the user may be determined to include visiting a hospital. In another example, the activity level of the user may be based on use of a TV remote, on use of a computer keyboard, or on use of a specific software application/website.

[00158] Activity Analysis Logic 1130 optionally includes one or more Machine Learning System 1135. Machine Learning System 1135 is configured to derive the activity level of the user based on a trained neural network or other trained expert system. Machine Learning System 1135 is configured to receive data resulting from Sensors 1115 to determine the activity level. For example, Machine Learning System 1135 may be trained to determine that a specific pattern of acceleration of a smartphone is indicative of a car crash, that a pattern of motion can be used to determine a number of steps taken by a user, that a pattern of typing on a keyboard can be indicative of a stroke, that an uneven gait can indicate a hip problem, alcohol consumption or a stroke, that a specific pattern of acceleration can indicate a cough or sneeze, and/or any of the other activity conditions discussed herein.

[00159] All or part of Machine Learning System 1135 is optionally disposed on members of Monitored Devices 110. For example, acceleration data generated by Sensor 1115A on Monitored Device 110A may be processed by Machine Learning System 1135 to produce a preliminary result indicative of an activity, this preliminary result on communicated from Monitored Device 110A to other parts of Activity Analysis Logic 1130 (e.g., via Data Input 1120 and/or Network 125) only if the preliminary result is indicative of a car accident, presence at a hospital or police station, and/or other specific activity of concern. Thus, sensor data may first be analyzed on Monitored Device 110A and then further analyzed at a remote location including elements of Activity Monitoring System 100. The remote location can include a server including a Microprocessor 180 configured to execute any of the various logic discussed herein. [00160] Activity Analysis Logic 1130 and/or Machine Learning System 1135 are optionally configured to use data received from multiple Monitored Devices 110 to determine an activity level of a user.

Specifically, lack of activity detected at multiple Monitored Devices 110 may be used to determine a low level of activity of a user. Different Monitored Devices 110 are optionally associated with different users. For example, in a household in which two users live the home security system and the TV remote may be associated with both users, while personal cell phones or tablet computers may be separately associated with the different users. In such embodiments, Activity Analysis Logic 1130 may be configured for associating different activity data with the different users. Some activity data (e.g., a motion or door sensor that is part of a home security system) may be associated with more than one user.

[00161] Activity Monitoring System 100 optionally further includes Activity Expectation Logic 140.

Activity Expectation Logic 140 is configured to determine an expected activity level for a user. The expected activity level may be based on demographics of the user and/or actual activity of the user measured using one or more of Monitored Devices 110. For example, the expected activity may be based on the user's age, profession, gender, residence location, health history, etc. Specifically, if the user is a nurse then visits to a hospital may be considered part of an expected activity level for that user. If the user is a college student then at least 5000 steps per day may be considered part of an expected activity level for that user.

[00162]The determination of an expected activity level of a user based on actual (detected) activity of the user, may be dependent on how long the user has been monitored using Activity Monitoring System 100. For example, when the user is first monitored, a lack of sensor data may make such a

determination unreliable. As more data representative of the user's actual activity is collected, the calculation of expected activity from actual activity is expected to become more reliable. In some embodiments, Activity Expectation Logic 140 is configured to first determine an expected activity of the user based on demographics of the user, and then to further refine the expected activity based on actual activity of the user as determined by Activity Analysis Logic 11130 based on data from Sensors 1115. In these cases, the expected activity is based on both demographics and measured activity. The relative weight of the dependencies on these two sources may change over time.

[00163]The activity level of a user (expected or actual) can be a multi-dimensional or multi-component parameter. For example, the activity level can include a number of steps taken, time spent in bed, time spent at home, locations visited, toilet or appliance use, number of falls, use of specific software applications (e.g. Facebook), time spent at work, number of coughs, medication taken, heart rate range, walking speed, glucose levels, and/or the like.

[00164] Activity Expectation Logic 140 optionally includes a Machine Learning System 1145. Machine Learning System 1145 is a "machine based system" as defined elsewhere herein and is optionally part of Deviation Logic 160 and/or Modeling Logic 192. Machine Learning System 1145 is configured to receive actual activity of a user and based on the actual activity calculate a likely range of expected activity for the user. The range of expected activity is optionally represented by probability distributions over multiple dimensions. Machine Learning System 1145 can be trained based on the measured activities of multiple users.

[00165] As such, Activity Monitoring System 100 can include multiple machine learning systems, optionally implemented on the same computing device(s). Machine Learning System 1135 is trained to determine an actual activity level based on sensor data and Machine Learning System 1145 is trained to determine an expected activity level for one or more specific users. Both of these machine learning systems are optionally configured to perform pattern recognition and temporal analysis on their input data.

[00166] Activity Monitoring System 100 further includes Threshold Logic 1150. Threshold Logic 1150 is configured to determine if a difference between expected activity of a user and measured actual activity of the user is greater than a threshold. Threshold Logic 1150 is optionally part of Deviation Logic 160. The threshold may be different for different dimensions of the activity level of the user. For example, presence at a police station or hospital may be compared using a simple yes/no threshold, while a number of daily steps taken or a heart rate may have a threshold based on a fixed value or a probability. For example, a number of steps taken during a day may have a threshold set to be exceeded with less than a 2% probability based on a probability distribution of an expected user activity level.

[00167]Thresholds used by Threshold Logic 1150 are optionally time dependent. For example, a lower level of activity may be expected at night when a user is sleeping, or during weekdays when the user spends time working at a desk, relative to weekend days when the user regularly goes mountain biking.

[00168]Thresholds used by Threshold Logic 1150 are optionally dependent on a predicted accuracy of the expected activity level of the user. For example, if the threshold is based only on demographic information about the user, then the threshold may be set higher, relative to a case in which a substantial amount of actual user activity has been determined using Monitored Devices 110. As such, threshold(s) may be reduced as more data is collected about a user actual activity levels based on data collected at Monitored Devices 110. An additional machine learning system (not shown) is optionally trained to determine dynamic thresholds. This machine learning system may be trained using activity data collected from multiple users using Activity Monitoring System 100. The threshold(s) may be adjusted (for one or more dimensions) in order to achieve a desired false positive and/or false negative rate. Thresholds may also take into account changes in more than one dimension. For example, if driving patterns, typing patterns and gait all change in a way that could be indicative of a stroke, then the correlation between these changes may justify use of a lower threshold, relative to thresholds for each of the individual changes.

[00169] Activity Monitoring System 100 further includes an Alert Logic 1155 configured to send an alert to one or more followers of a user. Alert Logic 1155 is optionally an embodiment of Alert Logic 186. As discussed elsewhere herein, An alert is sent if one or more dimensions of the (measured) activity level of the user is sufficiently different than the expected activity level. The alert may be sent via text message, multi-media message, e-mail, telephone call, and/or any other communication system. Alerts are optionally sent via Network 125. Typically, the sent alert includes an indication of why the alert was sent. For example, an alert may state that the user has coughed repeatedly for 6 hours, has not used to toilet for 10 hours, or has not gotten out of bed by 11AM, has stroke symptoms, has not left the house in 4 days, and/or the like. An alert may be generated for acute events that happen in a short time or for events that develop over time. For example, an alert may be generated if it is observed that a user's blood glucose has been progressively unstable over several days, that a user's walking distance each day has slowly dropped over a month, and/or that the user's activity level has changed over several weeks in a way that indicates depression. Alerts may include a location of Monitored Device 110A. For example, if an alert is based on presence at a hospital or on data suggestive of a car accident, the alert may include a geographic location.

[00170] Alerts typically suggest that the user receive medical attention rather than providing a medical diagnosis. Once such activity levels (or changes) are detected, that may indicate a problem. The user, and optionally their followers, are advised to seek advice of a medical professional who can make a medical diagnosis. Detection of specific conditions can be more precise if the data is generated by an loT enabled medical devices. For example, an insulin pump or an inhaler can detect a specific physiological condition or distress. Activity Analysis Logic 1130 is typically configured to detect both acute events such as a car crash or fall, and also medically relevant events that take place overtime. For example, some of the conditions discussed above are indicated by changes in a person's activity over time.

[00171] In some embodiments Alert Logic 1155 is further configured to periodically send a digest to followers of the user. For example, Alert Logic 186 may send a daily digest that includes a high-level summary of the activity level of a user. The digest may include a graph representing daily activity level. This representation can be based on multiple factors, such as trips out of the house, number of steps taken, meals cooked, exercise, etc. In some embodiments, detailed information regarding a user's activity, such as their exact location or where they went is excluded from digests to preserver privacy of the user.

[00172]The followers of a user are typically people that have specifically been approved by the user to receive alerts and digests. Followers may include family, close friends, medical providers, and/or other members of the user's support network. In some embodiments, Activity Monitoring System 100 includes logic and a user interface (not shown) configured for a user to approve followers and to indicate what information each follower may receive.

[00173jAlert Logic 1155 is optionally configured to open a communication channel between the user and a follower. For example, Alert Logic 1155 may be configured to automatically place a call between Monitored Device 110A and a smartphone of a follower. This communication channel can include audio or video communication between the user and follower.

[00174] Activity Monitoring System 100 optionally further includes Alert Cancellation Logic 1160 configured for the user to cancel an alert before it is sent to followers of the user. Alert Cancellation Logic 1160 is optionally part of Confirmation Logic 147. For example, Alert Cancellation Logic 1160 may be configured to display a message on Monitored Device 110A stating that an alert will be sent to all followers because Monitored Device 110A has been detected as being at a hospital or may have been in a car crash. This message may give the user a specific time in which to cancel the alert or to select which followers receive the alert. Alert Cancellation Logic 1160 may also e configured for a user to include a audio or text message in an alert. For example, the user may wish to send a message stating "I'm just at the police station for a fundraising event." [00175] In some embodiments, cancellation of an alert is considered a false positive event and is used by Threshold Logic 1150 to adjust one or more threshold levels. For example, if a new user cancels a lot of alerts, then thresholds may be expanded to reduce the false positive rate. If an alert is cancelled, then the activity that resulted in the alert may be used to adjust the expected activity of the user. In one example, a user may volunteer at a hospital every Saturday morning, then a hospital visit at this time may become part of their expected activity. After a few cancellations on Saturday morning of alerts resulting from hospital visits, the cancellations are used to improve the prediction of the future activity levels of the user.

[00176] Activity Monitoring System 100 optionally further includes Device Registration Logic 1165. Device Registration Logic 1165 is configured to register Monitored Devices 110 and optionally to associate these devices with specific users. For example, a user may use Device Registration Logic 1165 to identify their home security system, their smartphone, their tablet computer, and their vehicle global positioning system (e.g., OnStar, GPS navigation, or airbag system) as including devices that represent their activity levels. As discussed elsewhere herein, some Monitored Devices 110 may represent the activity of more than one user. Thus, a TV remote, toilet use sensor or home security sensor may be associated with several people living in the same residence. In some embodiments, the location of one registered devices can affect how use of a second device is interpreted by Activity Analysis Logic 130. For example, a TV remote may be registered as representing activity of both a husband and wife.

However, if a smartphone associated with a wife has traveled to a distant city, then use (or lack thereof) of a TV remote may be treated as representing activity of just the husband.

[00177] Activity Monitoring System 100 optionally further includes Digest Logic 1170. Digest Logic 1170 is configured do generate a digest that includes a summary of the activity of a user. The summary optionally includes filtered information about the activity level of the user. For example, it may include that the user spent time outside or was active without specifying exactly where the user went. In some embodiments, the daily digest includes a quantitative representation of the activity level of the user, such as a score, number or bar graph. The digest may be sent daily, weekly or on some other periodic basis. FIG. 12B illustrates an example of a daily digest. Users are optionally encouraged to improve their activity score.

[00178] FIG. 8 illustrates a device selection Interface 200, according to various embodiments of the invention. Such an Interface 200 may be generated by Device Registration Logic 1165 and provided to a device of a user. Interface 200 is configured for the user to register devices that generate data that may be indicative of their activity. For example, Sasha's iPhone, and the other devices listed, may each be embodiments of Monitored Devices 110. Some of the devices illustrated in FIG. 8 are registered to more than one user. The registration process performed by Device Registration Logic 1165 may include providing IP addresses, device serial number, phone numbers, and or the like. In some embodiments, registration includes connecting each of the devices to a central server that includes Device Registration Logic 1165. In some cases, registration includes connecting a third-party service, such as a home security monitoring services, to Activity Monitoring System 100.

[00179] FIG. 9 illustrates methods of generating an alert, according to various embodiments of the invention. In these methods, a sensor data is received from multiple devices and used to determine an activity level of a user. The determined activity level is compared with an expected activity for the user, and if the comparison shows a difference greater than a threshold, then an alert may be generated and sent to followers. The received sensor data is optionally further used to train a machine learning to predict the expected activity for the user and/or to train a machine learning system to interpret what activity is represented by specific data received from one or more sensors.

[00180] In a Receive Data Step 1310 data is received from Monitored Device 110A. This data is generated from signals produced by Sensor 1115A and/or additional sensors included in Monitored Device 110A. The data is optionally received via Network 125. [00181] In an optional Receive Data Step 1315 data is received from Monitored Device HOB. This data is generated from signals produced by a Sensor 1115B (not shown) and/or additional sensors included in Monitored Device 110A.

[00182] Note that additional receive data steps similar to Steps 1310 and 1315 may be the methods illustrated by FIG. 9. These receive data steps may include receiving data from additional devices such as Monitored Device HOC, etc. The data received in Steps 1310 can be from different types of Sensors 1115 and/or different types of Monitored Devices 110. Steps 1310 and 1315 may occur

contemporaneously or may occur at different times. In some embodiments, Steps 1310 and/or 1315 occur at regular time intervals, such as once per minute, hour, day or week. In some embodiments, Steps 1310 and/or 1315 are triggered by specific events, such as detection of unusual acceleration of a smartphone (such as would indicate an accident), lack of use of Monitored Device 110A for a time period, presence of Monitored Device 110A at an unexpected location (e.g., hospital or police station), and/or any of the other acute events discussed herein.

[00183] In an optional Train Step 1320 the data received in Steps 1310, 1315 and/or additional receive data steps is used to train a machine learning system, such as Machine Learning System 1135 and/or Machine Learning System 1145. The training may be directed toward determining what activity may be represented by the sensor data received in Steps 1310 and 1315; and/or the training may be directed toward determining expected activity for a specific user and/or a cohort of users.

[00184] In a Determine Activity Step 1325, the data received in Steps 1310, 1315 and/or additional receive data steps are used to determine actual activity of the user. Determine Activity Step 1325 is optionally performed using Machine Learning System 1135. In some embodiments, all or part of Determine Activity Step 1325 is performed on Monitored Device 110A. For example, initial processing of sensor data may occur on Monitored Device 110A and further processing of the sensor data may occur on a server included in Activity Monitoring System 100. This server may include a Microprocessor 180 configured to execute part of Activity Analysis Logic 1130. In some embodiments, communication of the data from Monitored Device 110A in Receive Data Step 1310 is dependent on a result of the initial processing of sensor data that occurs on Monitored Device 110A. For example, Sensor 1115A may be configured to detect acceleration, and only when the detected acceleration is indicative of a reportable event are the data communicated from Monitored Device 110A in Step 1310. In various embodiments, reportable events can include any one or more of the acute events discussed herein.

[00185] In a Determine Expected Activity Step 1330, the expected activity of the user is determined. As noted elsewhere herein the expected activity may be determined using Machine Learning System 1145. Further, the expected activity may be determined using actual activity of the user and/or activity of a cohort of users of which the user is a member. The expected activity may be determined prior to any of the other steps illustrated in FIG. 9. In some instances, expected activity is based on presumptions about normal activity. For example, most people don't decelerate from 45 to 0 MPH in less than 3 seconds. The expected activity can include many different dimensions, as discussed herein, such as location, physiological functions, travel, exercise, steps taken, movement patterns, sleep patterns, etc. Expected activity may include temporal dependencies. For example, the activity expected on Sunday morning may be different than that expected on Saturday night. Or, staying in bed for 9 hours may be more expected at night than during the day.

[00186] In a Determine Difference Step 1335, one or more differences between the expected activity of the user (from Step 1330) and the actual activity of the user (from Step 1325) is determined. Determine Difference Step 1335 is optionally an embodiment of Compare Step 330 or Determine Deviation Step 1430. The differences between the expected and actual activity is optionally represented by a cosine distance is a multi-variable space. Determine Difference Step 1335 can include differences in a single dimension, and in addition differences between expected correlation between different dimensions. For example, if a user either plays golf or paintball every Sunday then an activity level that includes neither golf or paintball may be unexpected. A lack of movement detected by a home security system may be more likely when the user's smartphone is visiting at a friend's residence, relative to when the smartphone is home.

[00187] In an Determine Threshold Step 1340, a threshold is determined for the difference between expected activity of the use and the actual activity as measured using Sensors 1115. This threshold can include multiple dimensions and/or can be determined for individual dimensions or for dimensions in combination. For example, a threshold may be determined for a combination of, or function of, steps taken in a day and time spent on social networking websites. In some embodiments, the threshold is dynamic. For example, the threshold may be dependent on how accurately the estimated activity is (believed to be) known and/or how accurately the interpretation of the data from Sensors is believed to represent an actual activity of the user. Determine Threshold Step 1340 is optionally performed using Threshold Logic 1150. Determine Threshold Step 1340 is optional if thresholds are already known, or are set to default values.

[00188] In a Generate Alert Step 1345 an alert is generated in response to one or more of the thresholds of Determine Threshold Step 1340 being greater than the respective one or more differences determined in Determine Difference Step 1335. The alert typically includes reasons that the alert was generated. For example, if the user's activity has declined over several days, the alert may state this fact. The alert may also suggest possible remedies or that the follower contact the user being followed. Contact and location information regarding the user may also be included in the alert.

[00189]Generate Alert Step 1345 optionally includes providing the user with an opportunity to cancel the alert, using Alert Cancellation Logic 1160. Cancellation of alerts can reduce incorrect alerts and gives the user a final step of control over their privacy. In some embodiments, the user may cancel delivery of the alert to some followers but not other followers. For example, the user may wish to notify only a subset of their followers that they are at a police station. The length time provided to cancel the alert is optionally dependent on the type or and/or reason for the alert. For example, a reduction in general physical activity may result in an alert that can be cancelled within an hour, while an alert resulting from a suspected car accident may only provide a 3 minute window to cancel. The contents and/or delivery of the alert are optionally responsive to a magnitude of the difference between the expected and actual activity, or a magnitude by which a threshold is acceded.

[00190] In a Report Step 1350, the alert, if not cancelled, is sent to followers of the user. Depending on the type and reason for the alert, the alert may be sent to different sets of followers. For example, an alert that the user is at a hospital may be sent so a first set of followers and an alert that the user has been coughing may be sent to a different set of followers. The user may predetermine these sets of followers. The alert may be included as part of a daily digest or may be sent to a follower via any other communication means. For example, the alert may be sent as an instant message or e-mail to a follower's smart phone. The method of communication is optionally dependent on an urgency of the alert. Generate Alert Step 1345 and Report Step 1350 are optionally embodiments of Alert Step 340.

[00191] FIG. 10 illustrates methods of training a machine learning system for a particular user, according to various embodiments of the invention. These methods may be used to train either Machine Learning System 1135 or Machine Learning System 1145. In other words, the method may be used to train a machine learning system to generate an expected activity for a particular user or to train a machine learning system to estimate actual activity based on data from Sensors 1115. In either case, an initial state for the machine learning system is selected/generated based on information that is not specific to just one user. Following this initial state, data gathered from Monitored Devices 110 of the user is used to further train the machine learning system. The steps discussed below are related to training a system to determine expected activity levels, however, the may be adapted to training for sensor data interpretation. [00192] In a Receive Data Step 1410, activity data is received regarding multiple users. The data is optionally based on sensor data received from multiple instances of Monitored Devices 110 associated with the multiple users. The data may be collected over an extended period of time.

[00193] In a Receive Demographics Step 1415, demographics are received regarding the multiple users. The demographics may include gender, age, weight, residence location, profession, medical history, and/or any other data that may be used to divide the users into different cohorts. The demographics and activity data are associated with specific users.

[00194] In a Determine Expected Activity Step 1420, an expected activity levels for the multiple users are determined. The expected activity levels are optionally dependent on the demographics of the multiple user and optionally include one or more statistical distributions of activity levels as a function of the demographics. The expected activity may be determined by a statistical analysis of activity data received in Receive Data Step 1410. The expected activity may be represented by a state of a machine learning system, e.g., Machine Learning System 1145 trained using the activity data.

[00195] In a Receive Demographics 1415, demographics of a first user are received. The first user is not necessarily a member of the multiple users. The demographics may be received by having the first user register for an account, from medical data, by having the first user enter data on a user interface, and/or the like.

[00196] In a Determine Activity Step 1420, an expected activity of the first user is determined. This determination may be determined by retrieving the expected activity, from the expected activities for the multiple users, the retrieval being based on the demographics of the first user. For example, an expected activity level across multiple dimensions of activity may be determined based on a statistical correlation between the demographics and the activity distributions of the multiple users. Alternatively, the expected activity may be determined by retrieving a state of Machine Learning System 1145 associated with the demographics. In Determine Activity Step 1420 the expected activity is based on the demographics of the first user, and not necessarily on any sensor data received regarding the first user.

[00197] In an optional Train Step 1425, Machine Learning System 1145 is trained to predict the expected activity of the first user. In some embodiments, the training is based on the activity of the multiple users, the demographics of the multiple users and the demographics of the first user. In some embodiments, the training produces a state of Machine Learning System 1145 representative of the expected activity level of the first user. Train Step 1425 may be performed by a third party and received in Determine Activity Step 1420, in which case Train Step 1425 is optional.

[00198] In a Receive 1^st Activity Step 1430 a first activity data regarding the first user is received, the activity data representing an activity level of one or more dimensions. This activity may be determined based on sensor data produced by Sensor 1115A. The sensor data is optionally interpreted using Machine Learning System 1135. As described elsewhere herein the activity may be determined using Activity Analysis Logic 1130.

[00199] In a Train Further Step 1435, Machine Learning System 1145 is trained further using the activity data received in Receive 1^st Activity Step 1430. Steps 1430 and 1435 may be repeated, 2, 3 or more times. As such, the training may employ temporal machine learning techniques. These repetitions are indicated at Receive 2^nd Activity Step 1445, etc. in FIG. 10.

[00200] In a Generate Expected Activity Step 1440, a new expected activity of the first user is generated using Machine Learning System 1145. This expected activity is based on both the state of Machine Learning System 1145 generated/trained on the activity of the multiple users (Step 1425) and also on the further training that occurs with each execution of Step 1435.

[00201] In a Receive 2^nd Activity Step 1445, further activity data indicating an activity level of the user is received. Receive 2^nd Activity Step 1445 is an embodiment of Receive 1^st Activity Step 1430 that occurs later in time. [00202] In a Determine Deviation Step 1450, it is determined that activity data received in a Receive 2 Activity Step 1445 represents a deviation from the expected activity of the user.

[00203] In a Generate Alert Step 1455, an alert is generated in response to the deviation. Generate Alert Step 1455 is optionally an embodiment of Generate Alert Step 1345. The alert is optionally dependent on embodiments of Determine Difference Stop 1335 and/or Determine Threshold Step 1340, as illustrated in FIG. 9.

[00204] In a Report Step 1460, the alert is reported to one or more followers of the user. Report Step 1460 is optionally an embodiment of Report Step 1350 of FIG. 9.

[00205] FIG. 11 illustrates methods of generating an alert based on a dynamic threshold. This dynamic threshold is optionally generated using Threshold Logic 1150. The dynamic threshold can include multiple dimensions and may be different for each dimension. The dynamic threshold is used to determine if a deviation from expected activity is sufficient to generate an alert. Different dimensions of the dynamic threshold may change by different amounts and/or in different directions.

[00206] In some embodiments, a threshold can have multiple levels that result in different actions when exceeded. For example, an initial threshold level may result in the inclusion of concerning activity changes in a daily digest, while a higher threshold level may result in generation of a real-time alert. In an illustrative example, a blood glucose level of that drops to 70 mg/dL may result in a notation in a daily digest, while a blood glucose level that drops to 40 may result in a urgent real-time alert.

[00207] In a Receive Activity Step 1510 an activity level of a user is received. As noted elsewhere herein the activity level may be determined using Activity Analysis Logic 1130 and data received from Sensors 1115. Receive Activity Step 1510 optionally includes Steps 1310, 1315, 1320, 1325, described with respect to FIG. 9.

[00208] In a Receive Expected Activity Step 1515 an expected activity is received. Receive Expected Activity Step 1515 optionally includes Determine Expected Activity Step 1330, discussed with respect to FIG. 9. The expected activity may be based on an output of Machine Learning System 1145, activity levels of the user, and/or activity levels of multiple users. For example, if one of the methods of FIG. 10 is used to train Machine Learning System 1145, then the expected activity may be initially based on the activities of a cohort of multiple users, and after further training of Machine Learning System 1145 may be later and further based on activities of the user.

[00209] In a Determine Deviation Step 1520 it is determined that activity level of the user received in Receive Activity Step 1510 represents a deviation from the expected activity of the user as received in Receive Expected Activity Step 1515. Determine Deviation Step 1520 optionally includes an

embodiment of Determine Difference Step 1335, discussed with respect to FIG. 9. The deviation may be of different amounts for different dimensions of the activity.

[00210] In a Determine Threshold Step 1525 a threshold for the deviation is determined. The threshold typically different for different dimensions of activity, and is dynamic. A dynamic threshold is one that may vary depending on different criteria. In various embodiments, the threshold varies as a function of time, as a function of an expected confidence (accuracy) of the expected activity level, as a function of an expected accuracy of the received activity level, as a function of an amount of activity data received for the user, as a function of the demographics of the user, as a function of the medical history of the user, and/or the like.

[00211]The expected confidence of the expected activity level may be a multi-dimensional statistical function (e.g., probability distributions), and may be based on an amount of training received by Machine Learning System 1145, on a meta-analysis of Machine Learning System 1145, on historical accuracy of Machine Learning System 1145, on demographics of the user, how much of the training data is specific to the user, on the accuracy of past expected activity levels, and/or the like. For example, in some embodiments, it may be determined statistically that after an amount of training X that dimension D of expected activity has a Y% probability of fitting within a specific distribution. Such statistical determination may be based on the training of many instances of Machine Learning System 1145 for many individual users.

[00212]The expected accuracy of the received activity level may be dependent on the quality and/or quantity of sensor data received, the age of the sensor data, the type of sensor data received, the training of Machine Learning System 1135 (possibly dependent on the same factors relevant to training of Machine Learning System 1145 discussed above), and/or the like.

[00213] Medical history may be used to dynamically vary the dynamic threshold for one or more dimensions. For example, if a user is diagnosed with Type I diabetes, their thresholds for blood glucose levels may be adjusted for this medical condition.

[00214] In a Determine Deviation Larger Step 1530, it is determined that the deviation of Determine Deviation Step 1520 is larger than the dynamic threshold in one or more dimension of activity. In some embodiments, correlations between multiple activity dimensions are considered in this determination.

[00215] In a Generate Alert Step 1535 an alert is generated in response to the determination of Step 1530. Generate Alert Step 1535 is optionally an embodiment of Generate Alert Step 1345 or Generate Alert Step 1455. The Alert may then be reported in instances of Report Step 1350 or Report Step 1460.

[00216] In an optional Change Confidence Step 1545 a confidence in the accuracy of either the expected accuracy of the received activity level and/or the expected confidence of the expected activity level may be changed. This change in confidence is optionally used to change associated dimensions of the dynamic threshold. The confidence may be changed, for example, if the alert is canceled by the user, if the user provides feedback on the alert, and/or the like. For example, if and alert resulting from the same cause is cancelled by a user several times, then the threshold for the activity dimension that caused the alert may be increased. As such, thresholds may be dynamically responsive to alert cancellations made using Alert Cancellation Logic 1160. [00217]The methods illustrated in FIGs. 9-11 are optionally performed in combination with those performed in FIGs. 3-6.

[00218] FIGs. 12A, 12B and 12C illustrate a real-time alert an alert cancellation interface and a digest, according to various embodiments of the invention.

[00219] Several embodiments are specifically illustrated and/or described herein. However, it will be appreciated that modifications and variations are covered by the above teachings and within the scope of the appended claims without departing from the spirit and intended scope thereof. For example, a Security System may be configured to change between modes; intruder detection mode and a health monitoring mode. Sending an alert due to inactivity is contrary to the operation of typical security systems. Machine Learning Systems 1135 and 1145 can include a deep learning system, a neural network, an adaptive expert system, and/or the like. The examples provided may be adapted to a peer- to-peer network that does not include a separate Management Server 123.

[00220] Examples of loT devices that may include Monitored Devices 110 include: Passive or active I detectors, Wheelchair - travel measurement, Walking cane - steps, pressure measurement, Electronic personal attendant - robot - Amazon Alexia^®, Bixby^®, TV remote, baby monitor, Smart home devices, thermostat, oven fridge, physical therapy devices (e.g., weight machines or limb position measurement devices) microwave, coffee maker, car, entry locks, garage door, key Fob, finger ring, bracelet, Animal movement (collar) - dog has not gotten up all day, Wearable device, Medical device (pacemaker, insulin pump, pill container, Security system, Animal tracking (combined with electronic fence, livestock). Some instances of Monitored Devices 110 may be configured for delayed data transmission, when the device is plugged in or within radio range. Normally security systems provide notice when an event occurs, or perhaps a status ping to show that they are operational.

[00221]Some embodiments include a security system that also sends a notice when there is a lack of action or an unexpectedly low amount of action. In some embodiments, the security system is configured to report signals detected at specific sensors to a remote processing system. Some embodiments provide both home security and a health monitoring services. Sensors used to detect the presence of an intruder are also used to monitor activity of a user.

[00222] An alert system configured to detect when current activity of a user deviates from an expected activity, and to provide an alert to a remote client when the deviation is detected. The expected activity is based at least in part on a measured activity. The measured activity is optionally measured over time using at least one sensor. The alerts are sent when the deviation is greater than a dynamic threshold. The threshold represents a permitted difference between current activity of the user and the expected activity, and is dynamic because it is dependent on a confidence to which the expected use and/or actual use are known. For example, in some embodiments, as the measured activity is measured over time a probability that the measured use represents a true expected use increases. In response to the increased probability the threshold is reduced.

[00223]This approach to alert generation results in a high initial threshold that is reduced over time to a lower value as a user's activity is monitored. The high initial threshold prevents alerts from being sent when they shouldn't be (false positive errors), relative to a system that initially used the lower threshold value. The change in threshold as a function of the probability increase can be based on a linear relationship, or on a stochastic model that attempts to achieve at least a desired false positive rate. The stochastic model may be based on measured activity of many users over time.

[00224] Further examples:

[00225] In an illustrative example, a new user is provided with one or more sensors configured to measure activity of the new user. Initially the expected activity is optionally based on a classification of the user. For example, the user may be assigned to a cohort based on their gender, age, wealth, weight, height, education, employment, and/or other demographic. The initial expected activity for the new user may then be assumed to be that of historical expected activity for members of the cohort. The historical activity for the cohort may be associated with an expected deviation (e.g., a standard deviation over a Gaussian distribution.) This deviation allows for a calculation that the expected activity of the cohort will represent the true expected use for the new user. It also allows for calculation of a threshold that will likely result in a false positive rate of less than a predetermined rate. For example, the predetermined rate may be set to one false positive (incorrect alert) per month.

[00226] As actual activity of the new user is measured over time. The measured activity can be used to modify their expected use, thus bringing the expected use closer to the true expected use. This also increases the probability that the estimated expected user activity level represents the true expected user activity level. The threshold can be reduced in response to this increased probability. Optionally, the threshold is reduced to keep or improve false positive rate.

[00227]

[00228]The activity of a user can be measured in many different aspects. For example, assuming the sensor used to measure activity is an accelerometer in an Apple Watch^®, the activity can be represented by the user's heart rate, a number of steps the user takes each day, and the frequency of sudden accelerations measured by the sensor. Dynamic thresholds are optionally set for each of these measurement types. The different types of activity are referred to herein as "dimensions" of activity.

[00229]Take for example, a new user that is a 30 years old overweight male. His initial expected activity may include taking 4000 steps per day and rarely experiencing rapid acceleration of the watch. There is a calculated probability that the initial expected activity represents his true activity. This probability is relatively low, resulting in a high threshold. On day 1 several potential alerts are detected but cancelled by the user. As a result, the thresholds are automatically raised. This reduces the number of false alerts. After measuring the new user's actual activity for a week it is found that he actually walks 8000 steps a day, keeps his heart rate above 100 bpm for at least an hour a day and has a resting heart rate of 80, and experiences sudden accelerations over 50 times per day. This activity is summarized in a daily digest. The expected activity for this user has now been adjusted based on actual measured activity for this user. As confidence in the expected activity increases the thresholds can be lowered. If this user now has a day of only 2000 steps, this may be sufficient to cause an alert, or to at least be noted in a digest.

[00230]Some embodiments include small inexpensive sensor devices equipped with motion sensors and a radio frequency transmitter. The sensor devices are configured to send a radio signal responsive to movement or lack of movement. The sensor devices are optionally configured to be attached to common objects such as a laptop computer, bathroom door, bed, refrigerator door, dishwasher, TV remote, etc. so as to detect use of these devices. The sensor devices are optionally configured to be plugged into an AC power outlet.

[00231]Some of the sensor devices may be configured to report a lack of use during a predetermined period, while some of the sensor devices may be configured to report use. In either case, the reporting is made by radio frequency signal to a monitored device. The monitored device is configured to determine if activity has not been detected by a set of sensor devices during a period of time and if a lack of detection occurs in all of the members of the set, to then send an alert to a remote destination. The alert indicating the lack of activity in all members of the set.

[00232] For an individual sensor device to report a lack of use typically includes: a clock, logic to measure predetermined period and determine that it has been exceeded, and a transmitter to report the lack of use. This sensor device may also include a circuit configured to receive setup data.

[00233]The embodiments discussed herein are illustrative of the present invention. As these embodiments of the present invention are described with reference to illustrations, various

modifications or adaptations of the methods and or specific structures described may become apparent to those skilled in the art. All such modifications, adaptations, or variations that rely upon the teachings of the present invention, and through which these teachings have advanced the art, are considered to be within the spirit and scope of the present invention. Hence, these descriptions and drawings should not be considered in a limiting sense, as it is understood that the present invention is in no way limited to only the embodiments illustrated.

[00234] Computing systems referred to herein can comprise an integrated circuit, a microprocessor, a personal computer, a server, a distributed computing system, a communication device, a network device, or the like, and various combinations of the same. A computing system may also comprise volatile and/or non-volatile memory such as random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), magnetic media, optical media, nano-media, a hard drive, a compact disk, a digital versatile disc (DVD), and/or other devices configured for storing analog or digital information, such as in a database. The various examples of logic noted above can comprise hardware, firmware, or software stored on a computer-readable medium, or combinations thereof. A computer-readable medium, as used herein, expressly excludes paper. Computer- implemented steps of the methods noted herein can comprise a set of instructions stored on a computer -readable medium that when executed cause the computing system to perform the steps. A computing system programmed to perform particular functions pursuant to instructions from program software is a special purpose computing system for performing those particular functions. Data that is manipulated by a special purpose computing system while performing those particular functions is at least electronically saved in buffers of the computing system, physically changing the special purpose computing system from one state to the next with each change to the stored data.

[00235]The logic discussed herein includes hardware, firmware and/or software stored on a computer readable medium. This logic may be implemented in an electronic device, e.g., circuit, to produce a special purpose computing system.

Claims

1. A monitored device comprising:

a display configured to present a user interface to a user;

an I/O configured to communicate data from the computing device using at least one

communication channel;

activity logic configured to detect use of the mobile computing device, wherein the use

comprises use of the user interface, use of the communication channel or movement of the computing device;

reporting logic configured to report the detected use of the mobile computing device to a

remote destination; and

a microprocessor configured to execute at least the activity logic.

2. The device of claim 1, further comprising filter logic configured to summarize the detected use prior to reporting the detected use to the remote destination.

3. The device of claim 1 or 2, further comprising deviation logic configured to determine if the detected use of the mobile computing device deviates from an expected use of the mobile computing device.

4. The device of claim 1, 2 or 3, further comprising setup logic configured for a user to select which detected use of the mobile computing device is reported to the remote destination.

5. The device of claim 1-3 or 4, further comprising voice logic configured to initiate a call using the

mobile computing device in response to a command received from a remote source.

6. The device of claim 1-4 or 5, further comprising peripheral monitoring logic configured to detect activity of a peripheral device connected wirelessly to the mobile computing device.

7. The device of claim 1-5 or 6, further comprising confirmation logic configured for a user to confirm or cancel an alert, the alert including a message to a third party and indicating a deviation from an expected use of the mobile computing device.

8. The device of claim 1-6 or 7, further comprising activity log storage configured to store a log of the detected use of the mobile computing device, the log including use of the user interface, use of the communication channel and movement of the computing device.

9. The device of claim 1-7 or 8, wherein the use of the mobile computing device further includes a

location of the mobile computing device, horizontal deceleration, vertical deceleration, charging/power level, WiFi connection, camera use, peripheral use, execution of an app, monitoring of an audio environment, calls answered/made, or the like.

10. The device of claim 9, wherein peripheral use includes connection to a peripheral device, heartbeat measurement, step measurement, changing TV channel, open refrigerator door, peripheral device movement, or the like.

11. The device of claim 9 or 10, wherein the peripheral device is a wearable device,

12. The device of claim 1-10 or 11, wherein the activity logic is configured to detect presence of the mobile device in a critical location, the critical location including a school, a hospital or a police station.

13. The device of claim 1-11 or 12, wherein the remote destination is a server or a mobile device of a third party.

14. The device of claim 1-12 or 13, wherein the reporting logic is configured to report only detected use that meets criteria selected by the user.

15. The device of claim 1-13 or l4, wherein the reporting logic is configured to report that the mobile device has not moved for a predetermined amount of time.

16. The device of claim 1-14 or 15, wherein the detected use includes a lack of movement of the mobile computing device for a period of time.

17. The device of claim 1-15 or 16, wherein the reporting logic is configured to report inactivity of the mobile device during a period of time in which activity is expected.

18. The device of claim 1-16 or 17, wherein the reporting logic is configured to report absence of a predeterminedjocation in the activity log.

19. The device of claim 1-17 or 18, wherein the reporting logic is configured to report a summary of the detected use, the summary generated by filter logic and including an abstracted representation of the detected use of the mobile computing device over a period of time.

20. The device of claim 2-18 or 19, wherein the filter logic configured to generate abstracted

representations of raw activity data in response to privacy settings selected by the user.

21. The device of claim 2-19 or 20, wherein the reporting logic is configured to summarize use of the mobile computing device, the use occurring over a period of time.

22. The device of claim 3-20 or 21, wherein the deviation logic is configured to identify use of the mobile device that deviates from an expected use by a predetermined amount.

23. The device of claim 3-21 or 22, wherein the deviation logic is configured to detect a temporal

deviation or a spatial deviation.

24. The device of claim 3-22 or 23, wherein expected use of the mobile computing device is determined using a machine based system or a set of alert rules.

25. The device of claim 3-23 or 24, wherein the expected use of the mobile computing devices is

determined using a log of activity of the user.

26. The device of claim 3-24 or 25, wherein the expected use of the mobile computing device is

determined using the use of multiple mobile devises by multiple users, respectively.

27. The device of claim 3-25 or 26, wherein the expected use of the mobile computing device is determined using a set of criteria set by the user.

28 The device of claim 4-26 or 27, wherein the expected use of the mobile computing device is

determined using a machine based system.

29. The device of claim 1-27 or 28, wherein the reporting logic configured to report the detected use of the mobile computing device to the remote destination only if the detected use violates an alert rule.

30. The device of claim 1-28 or 29, wherein the reporting logic is configured to periodically report a summary of the detected use, the summary being generated by filter logic configured to apply a privacy filter to the detected use of the mobile computing device.

31. A monitored device comprising:

a display configured to present a user interface to a user;

an I/O configured to communicate data from the computing device using at least one

communication channel;

activity logic configured to detect use of the mobile computing device;

reporting logic configured to periodically report a digest of the detected use, the summary being generated by filter logic configured to apply privacy criteria to the detected use of the mobile computing device; and

a microprocessor configured to execute at least the activity logic.

32. The device of claim 1-29 or 31, wherein the privacy criteria are set by the user.

33. The device of claim 1-31 or 32, wherein the reporting logic is further configured to send an alert if the detected use deviates from an expected use.

34. The device of claim 1-32 or 33, wherein the reporting logic is further configured to send an alert if the detected use violates an alert rule.

35. The device of claim 1-33 or 34, wherein the digest includes a summary of the user's activity.

36. The device of claim 1-34 or 35, wherein the digest includes an activity ranking.

37. The device of claim 1-35 or 36, wherein the digest includes a comment added by the user.

38. The device of claim 1-36 or 37, wherein reporting logic is configured report the digest to a remote computing device.

39. The device of claim 1-37 or 38, wherein the digest includes an activity ranking based on use of peripheral devices.

40. The device of claim 1-38 or 39, wherein the digest includes an activity ranking based on a number of steps taken by the user.

41. The device of claim 1-39 or 40, wherein the digest is generated by filter logic and includes an

abstracted representation of the detected use of the mobile computing device over a period of time.

42. The device of claim 1-40 or 41, wherein the monitored device is a smartphone or tablet computer.

43. A monitored device comprising:

a display configured to present a user interface to a user;

an I/O configured to communicate data from the computing device using at least one

communication channel;

activity logic configured to detect use of the mobile computing device, wherein the use

comprises use of the user interface, use of the communication channel or movement of the computing device;

reporting logic configured to send an alert to a remote destination if the detected use deviates from an expected use, wherein expected use of the mobile computing device is determined using a machine based system or a set of alert rules; and

a microprocessor configured to execute at least the activity logic.

44. The device of claim 1-42 or 43, wherein the expected use of the mobile computing device is determined using a machine based system.

45. The device of claim 1-43 or 44, wherein the machine based system includes an artificial neural network.

46. The device of claim 1-44 or 45, wherein the machine based system is trained based on detected use of the monitored device.

47. The device of claim 1-45 or 46, wherein the machine based system is trained based on use of

monitored devices by a class of users.

48. The device of claim 1-46 or 47, wherein at least part of the machine based system is disposed on the monitored device.

49. The device of claim 1-47 or 48, wherein at least part of the machine based system is disposed on a server remote from the monitored device.

50. A monitoring system comprising:

an I/O configured to communicate to and from remote clients;

connection logic configured to establish a relationship between a first of the remote clients and a second of the remote clients in a social network;

alert logic configured to provide an alert to the second of the remote clients, the alert being in response to data characterizing use of the first of the remote clients, the data characterizing use indicating a deviation from an expected use of the first of the remote clients, the alert being sent to the second of the remote clients because of the relationship between the first and second of the remote clients; and

a microprocessor configured to execute at least the alert logic.

51. The system or device of claim 1-49 or 50, further comprising poll logic configured to pole members of the remote clients, the pole including a request for data characterizing use of the remote client.

52. The system or device of claim 1-49 or 51, further comprising alert data storage configured to store alert data indicating under which the alert should be sent to the second of the remote clients, wherein the alert logic is configured to compare the alert data to the data characterizing the use of the first of the remote clients and to provide the alert in response to this comparison.

53. The system or device of claim 1-51 or 52, further comprising connection logic configured to establish two different types of relationships including a basic relationship and an enhanced relationship, the enhanced relationships including monitoring use of a monitored device and the basic relationships not including monitoring use of a monitored device, wherein the monitoring results in an automatic alert if the use deviates from an expected use.

54. The system or device of claim 1-52 or 53, further comprising deviation logic configured to determine if a detected use deviates from an expected use.

55. The system or device of claim 54, wherein the deviation logic is configured to compare the detected use to a set of predetermined rules or to process the detected use using an artificial intelligence system.

56. The system or device of claim 1-54 or 55, wherein the detected use includes use of a peripheral, presence at a geographic location, operation of the monitored device, or movement of the monitored device.

57. The system or device of claim 1-55 or 56, further comprising modeling logic configured to model the use of a monitored device, the model being configured to distinguish between expected use and a use that is not expected.

58. The system or device of claim 57, wherein the modeling logic is configured to train an artificial intelligence system to distinguish between the expected use and the use that is not expected.

59. The system or device of claim 58, wherein the modeling logic is configured to train the artificial intelligence system based on use of multiple monitored devices used by different users.

60. The system or device of claim 58 or 59, wherein the modeling logic is configured to train the artificial intelligence system based on a specific user and a resulting trained artificial intelligence system is customized to the specific user.

61. The system or device of claim 1-59 or 60, wherein the alert is responsive to data characterizing use of the first of the remote clients and a third of the remote clients.

62. The system or device of claim 1-60 or 61, wherein the alert is responsive to a lack of use of both the first and third of the remote clients over a predetermined time.

63. The system or device of claim 1-61 or 62, wherein the first of the remote clients and the third of the remote clients include any two of: a smartphone, a tablet computer, a personal computer, a television set, a refrigerator, a stove, a microwave, a washer, a dryer, a coffee maker, dog collar, television/internet interface device, a remote control, a telephone, a camera, a vehicle, a stove, a motion sensor, a door, a security system and a light.

64. The system or device of claim 1-62 or 63, wherein the third of the remote clients is connected to the first of the remote clients via a wired or wireless local connection.

65. The system or device of claim 1-63 or 64, wherein the third of the remote clients is a wearable

device.

66. The system or device of claim 1-64 or 65, wherein the alert logic is configured to provide the alert based on a set of rules regarding the use of at least the first and third remote clients.

67. The system or device of claim 1-65 or 66, wherein the first and third remote clients are both

associated with a same user.

68. The system or device of claim 1-66 or 67, wherein the alert logic is configured to provide the alert to the second of the remote clients in response to both a lack of movement of the first remote client and a lack of use of the third of the remote clients, for a predetermined period of time.

69. The system or device of claim 1-67 or 68, wherein the alert logic is configured to provide the alert to the second of the remote clients in response to both a lack of movement of the first remote client and a lack of detected movement near the third of the remote clients, for a

predetermined period of time.

70. A method of monitoring a person's activity, the method comprising:

determining an expected use of a mobile device, the expected use including location of the mobile device, movement of the mobile device or use of a peripheral connected to the mobile device;

detecting use of the mobile device;

comparing the detected use of the mobile device to the expected use of the mobile device; and sending an alert to a remote location in response to the comparison indicating that the detected use of the mobile device has deviated from the expected use of the mobile device, the alert being configured to notify a third party of the deviation.

71. The method of claim 70, further comprising receiving alert rules or privacy criteria at the mobile device, wherein content of the alert is dependent on the alert rules or privacy criteria.

72. The method of claim 70 or 71, further comprising filtering the detected use to create a summary of the detected use, prior to sending the alert to the remote location.

73. The method of claim 70, 71 or 72, further comprising exchanging a periodic awake signal between the mobile device and the remote location.

74. The method of claim 70-72 or 73, wherein the detected use includes electrical charging of the mobile device, location of the mobile device, acceleration of the mobile device, use of an Ul or application of the mobile device, movement of the mobile device, and/or the like.

75. The method of claim 70-73 or 74, wherein use of the mobile device includes a horizontal or vertical acceleration greater than predetermined amount.

76. The method of claim 70-74 or 75, wherein the expected use of a mobile device includes the

movement of the peripheral, and the peripheral is configured to be attached to a medicine container.

77. A method of managing a social network, the method comprising:

providing the social network to multiple members, the social network including a basic

connection between members and an enhanced connection between members, the enhanced connection including automatic monitoring of use of a mobile device of a first user;

detecting a use of the mobile device;

determining that the detected use is outside of an expected predetermined use pattern; and providing an alert to a second user that the detected use is outside of the predetermined user pattern, the provision of the alert being based on an enhanced connection between the first user and the second user.

78. The method of claim 70-76 or 77, further comprising providing the first user with an opportunity to cancel automatic delivery of the alert to the second user.

79. The method of claim 70-77 or 78, wherein the basic connection does not include automatic

monitoring of the use of the mobile device of the first user.

80. A method of managing a social network, the method comprising: receiving data representing a social network including multiple members, the social network further including features that allow text messaging between the members, each of the members having a set of connections to one or more others of the members; and providing an upgrade opportunity to a first of the members, the upgrade opportunity including an ability to establish an enhanced connection between the first of the members and a second of the members, the enhanced connection including automatic monitoring of use of a mobile device of the second of the members and reporting of the automatic monitoring to the first of the members, wherein the monitored use is a use other than the messaging between the first and second members.

81. The method of claim 70-79 or 80, wherein the automatic monitoring includes detection of

movement of the mobile device using an accelerometer or gyroscope.

82. The method of claim 70-80 or 81, further comprising receiving a report that the mobile device has not been used for a period of time and automatically reporting the lack of use to the first of the members.

83. The method of claim 70-81 or 82, wherein the lack of use includes a lack of movement.

84. The method of claim 70-82 or 83, wherein the enhanced connection is enhanced relative to a basic connection between the first and second members, the basic connection not including automatic monitoring of user of the mobile device of the second of the members.

85. An activity monitoring system comprising:

a first motion sensor configured to detect movement within a first area of regard;

a second motion sensor configured to detect movement within^'a second area of regard;

activity logic configured to determine a lack of movement detected by both the first motion sensor and the second motion sensor for a first predetermined period of time; and reporting logic configured to report the lack of movement for the predetermined period of time to a remote destination.

86. The system or device of claim 1-69 or 85, further comprising a mobile device, the mobile device including a third motion sensor configured to detect movement of the mobile device, wherein the activity logic is configured to determine a lack of movement of the mobile device for a second predetermined period of time, and the activity reporting logic is configured to report the lack of movement if the lack of movement is detected by the first remote monitoring sensor; the second remote monitoring sensor and the movement sensor.

87. The s system or device of claim 1-69, 85 or 86, wherein the activity reporting logic is configured to report the lack of movement by sending an alert to members of a social network.

88. The system or device of claim 1-69, 85-86 or 87, wherein the reporting logic is configured to not report a lack of movement if movement is detected by any of the first, second, or third motion sensor.

89. An activity monitoring system comprising:

a first motion sensor configured to detect movement of a mobile device;

a second motion sensor configured to detect movement within an area of regard;

activity logic configured to determine a lack of movement detected by both the first motion sensor and the second motion sensor for a first predetermined period of time; and reporting logic configured to report the lack of movement for the predetermined period of time to a remote destination.

90. The system or device or device of claim 1-69, 85-88 or 89, wherein the second motion sensor

includes a pressure sensor, a camera or a IR motion detector.

91. The system or device or device of claim 1-69, 85-89 or 90, wherein the second motion sensor is part of a home security system.

92. The system or device or device of claim 1-69, 85-90 or 91, wherein the second motion sensor is part of an internet connected appliance.

93. A method of monitoring a first person's activity, the method comprising:

providing a first motion sensor having a first area of regard;

providing a second motion sensor having a second area of regard;

determining that motion has not been detected by either the first or second motion sensor for a predetermined period of time; and

providing an alert to a remote destination, the alert indicating the lack of detected motion by either the first or second motion sensor.

94. The method of claim 70-84 or 93, wherein the alert is sent to a plurality of remote destinations.

95. The method of claim 70-84, 93 or 94, wherein the alert is sent to a second person, the second

person being a follower of the first person.

96. The method of claim 70-84, 93-94 or 95, wherein the alert further indicates that a mobile device of the first person has not been used for a predetermined period of time.

97. A mobile computing device comprising:

a display configured to present a user interface to a user;

an I/O configured to communicate data from the computing device using at least one

communication channel;

activity logic configured to detect use of the mobile computing device, wherein the use

comprises use of the user interface, use of the communication channel or movement of the computing device;

messaging logic configured to communicate at least text messages between the computing device and a remote destination; reporting logic configured to report a lack of detected use of the mobile computing device for a predetermined amount of time, to the remote destination via the messaging logic; and a microprocessor configured to execute at least the activity logic.

98. A mobile computing device comprising:

a display configured to present a user interface to a user;

an I/O configured to communicate data from the computing device using at least one

communication channel;

activity logic configured to detect use of the mobile computing device, wherein the use

comprises use of the user interface, use of the communication channel or movement of the computing device;

messaging logic configured to communicate at least text messages between the computing device and a remote destination;

reporting logic configured to report a use of the mobile computing device that deviates from an expected use, to a remote destination via the messing logic; and

a microprocessor configured to execute at least the activity logic.

99. The device of claim 1-69, 85-92, 97 or 98, further comprising connection logic configured to establish a relationship between the user and a second user at the remote destination.

100. The device of claim 1-69, 85-92, 97-98 or 99, further comprising setup logic configured to

predetermine the remote destination.

101. The device of claim 1-69, 85-92, 97-99 or 100, further comprising setup logic configured for the user to set up criteria for sending the report to the remote destination.

102. The device of claim 1-69, 85-92, 97-100 or 101, wherein the criteria include presence of the

computing device at a hospital or police station.

103. The device of claim 1-69, 85-92, 97-101 or 102, wherein the criteria include a lack of use of a plurality of devices for a predetermined time period.

104. The device of claim 1-69, 85-92, 97-102 or 103, wherein the criteria are dependent on an identity of the remote destination, the setup logic being configured to set up criteria for sending the report to multiple remote destinations.

105. The device of claim 1-69, 85-92, 97-103 or 104, wherein the detected use incudes picking up or rotating the device.

106. The device of claim 1-69, 85-92, 97-104 or 105, further comprising confirmation logic configured to provide the user with an opportunity to cancel an automatic text message.

107. The device of claim 1-69, 85-92, 97-105 or 106, further comprising alert response logic configured for responding to the report of use.

108. The device of claim 1-69, 85-92, 97-106 or 107, wherein the alert response logic is configured to automatically open a voice channel between the device and the remote destination.

109. A method of detecting a vehicular accident, the method comprising:

obtaining acceleration data from an accelerometer within a mobile computing device;

using a gyroscope to determine direction of an acceleration represented by the acceleration data;

determining that a horizontal component of the acceleration is above a predetermined

threshold;

based on the determination, sending the acceleration data to a remote server;

at the remote server, processing the acceleration data using a machine based system to

determine that the acceleration data represents acceleration representative of a vehicular accident; and based on the determination that the acceleration data represents a vehicular accident, sending an alert to a remote client, the alert indicating that the mobile computing device has experienced the vehicular accident.

110. The method of claim 70-84, 93- 96 or 109, further comprising training the machine based system using acceleration data obtained from multiple vehicular accidents.

111. The method of claim 70-84, 93- 96, 109 or 110, wherein the machine based system includes an artificial neural network.

112. An activity monitoring system comprising:

a plurality of sensors disposed in at least two different types of devices, each of the sensors being configured to detect an activity of a user and to produce data representative of the activity;

an input configured to receive the data from the different types of devices;

activity analysis logic configured to determine an activity level of the user based on the received data;

reporting logic configured to report the activity level of the user to a remote device.

113. The system or device of claim 1-69, 85-92, 97-108 or 112, wherein the different types of devices include at least two of a camera, a motion detector, a security device, a smartphone, a bed pressure detector, a toilet use detector, an entry detection device, a vehicle, a medical device, a thermostat, a personal assistant, a television or television remote, a microwave, a stove, a refrigerator, a wearable device, a tablet computer, a personal computer, a toothbrush, a coffee maker, or a smoke detector.

114. The system or device of claim 1-69, 85-92, 97-108, 112 or 113, wherein the sensors include at least two of a motion sensor, a pressure sensor, a current sensor, a voltage sensor, a location sensor, an optical sensor, an infrared sensor, a physiological sensor, or a chemical sensor.

115. The system or device of claim 1-69, 85-92, 97-108, 112-113 or 114, further comprising alert logic configured to compare the activity level of the user to an expected activity level of the user, and to generate an alert if a difference between the activity level and the expected activity level is greater than a threshold.

116. The system or device of claim 1-69, 85-92, 97-108, 112-114 or 115, further comprising threshold logic configured to determine the threshold based on a confidence in an accuracy of the expected activity level of the user.

117. The system or device of claim 1-69, 85-92, 97-108, 112-115 or 116, further comprising a first

trained machine learning system configured to determine the expected activity level of the user.

118. The system or device of claim 1-69, 85-92, 97-108, 112-116 or 117, further comprising alert

cancellation logic configured for the user to cancel an alert before the alert is sent to a follower.

119. The system or device of claim 1-69, 85-92, 97-108, 112-117 or 118, further comprising device

registration logic configured to register at least two devices as providing data representative of the activity of the user, the at least two devices being of different types.

120. The system or device of claim 1-69, 85-92, 97-108, 112-118 or 119, wherein the at least two

different devices include at least one device configured to detect movement of the user and at least one device configured to detect a physiological state of the user.

121. The system or device of claim 1-69, 85-92, 97-108, 112-119 or 120, wherein the input is configured to receive the data via a computer network.

122. The system or device of claim 1-69, 85-92, 97-108, 112-120 or 121, wherein the input is configured to receive the data as an SMS or MMS message.

123. The system or device of claim 1-69, 85-92, 97-108, 112-121 or 122, wherein the input is configured to receive the data from different types of device via different communication channels.

124. The system or device of claim 1-69, 85-92, 97-108, 112-122 or 123, wherein the activity level of the user includes two or more of: a location of the user, a sleep pattern of the user, a drug use of the user, maintenance of a physical state of the user, travel of the user, steps taken by the user, food or drink intake by the user, bathing of the user, use of a toilet by the user, driving patterns of the user, use of electronic devices by the user, or use of websites or computer applications by the user.

125. The system or device of claim 1-69, 85-92, 97-108, 112-123 or 124, wherein the activity analysis logic is configured to determine the activity level of the user based on the received data using a second trained machine learning system.

126. The system or device of claim 1-69, 85-92, 97-108, 112-124 or 125, wherein at least part of the activity analysis logic is selected based on the types of devices.

127. The system or device of claim 11-69, 85-92, 97-108, 112-125 or 126, wherein the activity analysis logic includes data processing logic located on a device of the user and data processing logic located on a device remote from the device of the user, the processing logic located on the device of the user being configured to preprocess data and to send a result of the preprocessing to the device remote from the device of the user.

128. The system or device of claim 1-69, 85-92, 97-108, 112-126 or 127, wherein the activity analysis logic is configured to detect activity indicative of depression, sleep disorders, digestive disorders, diabetes, mental illness, arthritis, cardiac distress, anemia, alcoholism, memory loss, stroke, vision loss, loss of joint function

129. The system or device of claim 1-69, 85-92, 97-108, 112-127 or 128, wherein the activity analysis logic is configured to determine the activity level of the user based on data from at least two different types of devices.

130. The system or device of claim 1-69, 85-92, 97-108, 112-128 or 129, wherein the reporting logic is configured to report the activity level of the user in real-time if the activity level is significantly different than an expected activity of the user, and to report the activity level of the user in a periodic digest if the activity level is not significantly different than the expected activity of the user, the significance being relative to a threshold difference.

131. The system or device of claim 1-69, 85-92, 97-108, 112-129 or 130, wherein the reporting logic is configured to report the activity level to one of the devices.

132. The system or device of claim 1-69, 85-92, 97-108, 112-130 or 131, wherein the reporting logic is configured to report the activity level to a remote device of a registered follower of the user.

133. The system or device of claim 41-69, 85-92, 97-108, 112-131 or 132, wherein the alert logic is configured to compare the activity level of the user to the expected activity using a plurality of activity criteria.

134. The system or device of claim 41-69, 85-92, 97-108, 112-132 or 133, wherein the alert logic is

configured to generate alerts in response to both acute events and events that develop over time.

135. The system or device of claim 1-69, 85-92, 97-108, 112-133 or 134, wherein the threshold logic is configured to reduce the threshold as a confidence increases that the expected activity of the user represents future activity of the user.

136. The system or device of claim 1-69, 85-92, 97-108, 112-134 or 135, wherein the expected activity of the user is represented by probability distribution for at least one activity aspect.

137. The system or device of claim 1-69, 85-92, 97-108, 112-135 or 136, wherein the expected activity of the user is represented by multiple activity aspects including at least two of: urination frequency, location, steps taken, time spent on social networking sites, hours of sleep, time in bed, presence at a hospital, data indicative of a car crash, steady gait, non-symmetric movement, time outside, range of motion or driving pattern

138. The system or device of claim 1-69, 85-92, 97-108, 112-136 or 137, wherein the expected activity of the user is determined using demographics of the user.

139. The system or device of claim 1-69, 85-92, 97-108, 112-137 or 138, wherein the alert logic is further configured to send a digest on a periodic basis, the digest including a summary of the activity of the user during a time period, the summary optionally including a value representative of an activity level of the user.

140. The system or device of claim 1-69, 85-92, 97-108, 112-138 or 139, wherein the alert logic is

configured to send an alert if the user is determined to be at a police station or hospital, determined to have experienced a vehicular accident, or if the received data is suggestive of a medical condition requiring immediate medical attention.

141. The system or device of claim 1-69, 85-92, 97-108, 112-139 or 140, wherein the expected activity level of the user is dependent on a time of day or day of the week.

142. The system or device of claim 1-69, 85-92, 97-108, 112-140 or 141, wherein the reporting logic is configured to determine if the activity level of the user should be reported to the remote device as, alternatively, an alert or a digest, the determination being based at least in part on aspects of the activity level.

143. The system or device of claim 1-69, 85-92, 97-108, 112-141 or 142, wherein the threshold logic is configured to determine different thresholds for different aspects of the activity of the user, each of the different thresholds being separately variable based on data received from the received data.

144. The system or device of claim 1-69, 85-92, 97-108, 112-142 or 143, wherein the threshold logic is configured to automatically increase the threshold in response to cancellation of one or more alerts by the user.

145. The system or device of claim 1-69, 85-92, 97-108, 112-143 or 144, wherein the first trained

machine learning system includes a neural network.

146. The system or device of claim 1-69, 85-92, 97-108, 112-144 or 145, wherein the first trained

machine learning system is trained based on a demographic of the user.

147. The system or device of claim 1-69, 85-92, 97-108, 112-145 or 146, wherein the first trained

machine learning system is trained based on detected activity of the user.

148. The system or device of claim 1-69, 85-92, 97-108, 112-146 or 147, wherein the first trained

machine learning system is trained based on detected activity of the user over a period greater than one day, one week or one month.

148. The system or device of claim 1-69, 85-92, 97-108, 112-147 or 148, wherein the first trained

machine learning system is trained to adapt for changes in the expected behavior of the user over time.

150. The system or device of claim 1-69, 85-92, 97-108, 112-148 or 149, wherein the alert cancellation system is configured to provide the user with a time period in which to prevent an alert from being sent to a follower, the time period being dependent on a reason for the alert.

151. The system or device of claim 1-69, 85-92, 97-108, 112-149 or 150, wherein the alert cancellation system is configured to allow the user to add a comment to an alert prior to the alert being sent to a follower.

152. The system or device of claim 1-69, 85-92, 97-108, 112-150 or 151, wherein the device registration logic is configured for the user to add or remove devices from a set of devices from which the data is received.

153. The system or device of claim 1-69, 85-92, 97-108, 112-151 or 152, wherein the device registration logic is configured for a particular device to be associated with measuring activity of more than one user.

154. The system or device of claim 1-69, 85-92, 97-108, 112-152 or 153, wherein the device registration logic is configured to provide the user with a user interface configured to receive device identification information.

155. A method of generating an alert, the method comprising:

receiving first data from a first type of device, the first data being indicative of an activity of a user;

receiving second data from a second type of device, the second data being indicative of an activity of the user;

determining an activity level of the user based on both the first data and the second data; optionally determining an expected activity level of the user;

optionally determining a difference between the determined activity level of the user and the expected activity level of the user;

optionally determining a threshold for an expected magnitude of the difference;

generating alert an alert regarding the detected activity of the user; and

reporting the alert to an authorized follower of the user.

156. The method of claim 70-84, 93- 96, 109-111 or 155, wherein generation of the alert is responsive to a magnitude of the difference being greater than the threshold.

157. The method of claim 70-84, 93- 96, 109-111, 155 or 156, further comprising using the first and second data to train a first machine learning system.

158. The method of claim 70-84, 93- 96, 109-111, 155-156 or 157, wherein the first machine learning system is used to determine the expected activity level of the user.

159. The method of claim 70-84, 93- 96, 109-111, 155-157 or 158, wherein a second machine learning system is used to determine the activity level of the user based on both the first data and the second data.

160. A method of training a machine learning system, the method comprising:

receiving activity data regarding multiple users;

receiving demographics regarding the multiple users;

determining expected activity levels for the multiple users, the expected activity levels being dependent on the demographics and including a statistical distribution; receiving demographics of a first user, the first user not being a member of the multiple users; determining or retrieving an expected activity of the first user, from the expected activities for the multiple users, the retrieval being based on the demographics of the first user; training a machine learning system to predict the expected activity of the first user;

receiving first activity data regarding the first user;

further training the machine learning system based on the received activity data regarding the first user;

generate an expected activity of the first user, using the machine learning system;

receiving second activity data regarding the first user;

determining that the second activity data is a deviation from the expected activity of the first user;

generating an alert based on the deviation; and

reporting the alert to a follower of the first user.

161. The method of claim 70-84, 93- 96, 109-111, 155-159 or 160, wherein the activity data regarding multiple users is received from at least two different types of devices.

162. A method of generating an alert based on a dynamic threshold, the method comprising:

receiving first activity data regarding a first user;

receiving an expected activity of the first user;

determining that the first activity data represents a deviation from the expected activity of the first user;

determining a threshold for the deviation, the threshold being based on a confidence of the expected activity;

determining that the deviation is larger than the threshold;

generated an alert regarding activity of the first user, responsive to the determination that the deviation is larger; and

reporting the alert to a follower of the first user.

163. The method of claim 70-84, 93- 96, 109-111, 155-151 or 162, further comprising using additional data regarding activity of the user to increase the confidence of the expected activity.

164. The method of claim 70-84, 93- 96, 109-111, 155-162 or 163, further comprising receiving a

cancellation of the alert and reducing the confidence of the expected activity, in response to the cancellation.

165. A security system comprising:

a first sensor configured to detect movement;

a second sensor configured to detect movement;

a control circuit configured to receive outputs of the first and second sensor;

a logic circuit configured to determine a lack of movement at both the first and second sensor for a predetermined period of time; and

an output configured to communicate the determination of lack of movement to a remote destination via a computer network or a telephone network.

166. A security system comprising:

a first sensor configured to detect movement;

a second sensor configured to detect movement;

a control circuit configured to receive outputs of the first and second sensor;

an output configured to communicate the outputs of the first and second sensor to a remote destination via a computer network or a telephone network;

a logic circuit configured to determine a lack of movement at both the first and second sensor for a predetermined period of time based on the outputs received from the sensors.

167. A security system comprising:

a first sensor configured to detect movement;

a second sensor configured to detect movement;

a control circuit configured to receive outputs of the first and second sensors;

a logic circuit configured to determine an unexpectedly low amount of movement at the first or second sensor for a predetermined period of time based on the outputs received from the sensors; and

an output configured to communicate the determination of the unexpectedly low amount of movement to a remote destination via a computer network or a telephone network.

168. The system of claim 70-84, 93- 96, 109-111, 155-158, or 165-167, further comprising notification logic configured to provide an alert to one or more remote clients based on the determination.

169. The system of claim 70-84, 93- 96, 109-111, 155-158, 165-167 or 168, wherein the first and second sensors include an optical sensor and a pressure sensor.

170. The system of claim 70-84, 93- 96, 109-111, 155-158, 165-168, or 169, wherein the first and second sensors include a bed sensor, a stove sensor, a refrigerator sensor, a door sensor, a toilet sensor or

171. A personal assistant system comprising:

a sensor configured to receive verbal or visual input from a user;

response logic configured to provide a response to the input, the response including providing an audio output to the user;

a logic circuit configured to determine an unexpectedly low amount of input at the sensor for a predetermined period of time; and

an output configured to communicate the determination of the unexpectedly low amount of input to a remote destination via a computer network or a telephone network.

172. The system of claim 70-84, 93- 96, 109-111, 155-158, 165-170 or 171, wherein the logic circuit is further configured to detect a poor emotional state based on the input, and the output is configured to communicate the detected poor emotional state to the remote destination.

173. The system of claim 70-84, 93- 96, 109-111, 155-158, 165-171 or 172, further comprising

movement activators configured to move part of the personal assistant device in response to the input.