Systems and methods for real time detection and reporting of personal emergencies

• US 10,003,945 B2
• Filed: 11/12/2015
• Issued: 06/19/2018
• Est. Priority Date: 11/13/2014
• Status: Active Grant

• Current Assignee: Mobiltron, Inc.
• Original Assignee: Mobiltron, Inc.
• Inventors: Papakonstantinou, Vassilis, Schizas, Stavros
• Primary Examiner(s): Sabouri, Mazda
• Application Number:
  US14/939,678
• Publication Number:
  US 20160142894A1
• Time in Patent Office: 950 Days
• CPC Class Codes: A61B 5/00 Measuring for diagnostic purposes radiation diagnosis A61B6/00; diagnosis by ultrasonic, sonic or infrasonic waves A61B8/00; Identification of persons
• CPC Class Codes: A61B 5/0022 Monitoring a patient using a global network, e.g. telephone networks, internet
• CPC Class Codes: A61B 5/02055 Simultaneously evaluating both cardiovascular condition and temperature
• CPC Class Codes: A61B 5/1112 Global tracking of patients, e.g. by using GPS
• CPC Class Codes: A61B 5/747 in case of emergency, i.e. alerting emergency services
• CPC Class Codes: G08B 21/0453 worn on the body to detect health condition by physiological monitoring, e.g. electrocardiogram, temperature, breathing detecting, measuring or recording for diagnostic purposes A61B5/00
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: G16H 50/20 for computer-aided diagnosis, e.g. based on medical expert systems
• CPC Class Codes: G16H 50/30 for calculating health indices; for individual health risk assessment
• CPC Class Codes: H04W 4/023 using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
• CPC Class Codes: H04W 4/90 Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
• CPC Class Codes: H04W 76/50 for emergency connections

Abstract

According to at least one aspect, a system and corresponding method for detecting and reporting personal emergency events includes a mobile application running on a client device of a user and a backend application running on a backend system. The mobile application and the backend application can communicate on a regular basis. The mobile application or the backend application can regularly monitor sensor data, user contextual data or other data indicative of user state of health, activities or environment and detect or predict an emergency event of the user based on the monitored data. Upon detecting an emergency event, the mobile application or the backend application can warn the user or notify emergency contacts of the user of the emergency event. The backend application can use the sensor data or other user data to update an emergency predictive model specific to the user employed to detect or predict emergency events.

Claims

1. A method for predicting an emergency event is to occur to a user, the method comprising:

(a) generating, by a micro-virtual machine (mVM) executed by the server, a user-customized emergency predictive model using, at least in part, user-specific data;

(b) launching, by the server, the mVM upon determining that a mobile application is activated on a mobile device;

(c) receiving, by the mobile device, data about at least one of a health, an activity or an environment of the user;

(d) analyzing, by one of the mobile device or the server, using the user-customized emergency predictive model, the data about at least one of the health, the activity or the environment of the user;

(e) determining, by one of the mobile device or the server, from the analyzed data and using the user-customized emergency predictive model, a score value indicative of a likelihood of an emergency event occurring to the user; and

(f) communicating, by one of the mobile device or the server responsive to the score value being greater than a threshold, a notification to the user to change behavior to avoid the emergency event; and

(g) encrypting, by the server, the mVM upon detecting that the mobile application is turned off on the mobile device, the mVM encapsulating the user specific data.

2. The method of claim 1, further comprising detecting, by one of the mobile device or the server, that the behavior of the user did not change and responsive to the detecting initiating, by one of the mobile device or the server, emergency reporting.

3. The method of claim 2, further comprising sending, by one of the mobile device or the server, a distress signal to one or more of the following:

emergency contacts of the user, an emergency response service or an ad-hoc safety network created by the user.

4. The method of claim 1, wherein the data comprises contextual data about the user and data from one or more sensors associated with the user.

9. The method of claim 1 further comprising:

providing, by the server, at least one parameter of the user-customized emergency predictive model to the mobile device.

10. The method of claim 1 further comprising:

updating one or more parameters of the user-customized emergency predictive model using the received data about at least one of the health, activity or environment of the user.

11. The method of claim 3, wherein the distress signal includes a uniform resource locator (URL).

12. The method of claim 11, wherein access to the URL is limited, via credential authentication, to one or more of the emergency contacts of the user, the emergency response service or the ad-hoc safety network created by the user.

5. A system for predicting an emergency event is to occur to a user, the system comprising:

a mobile application configured to be executable on a mobile device to receive data about at least one of a health, an activity or an environment of the user;

a server configured to communicate with the mobile application and receive data from the mobile device;

wherein the server is configured to;

execute a micro-virtual machine (mVM) to generate a user-customized emergency predictive model using, at least in part, user-specific data; and

launch the mVM upon determining that a mobile application is activated on the mobile device; and

encrypt the mVM upon detecting that the mobile application is turned off on the mobile device, the mVM encapsulating the user specific data, and

wherein at least one of the mobile application or the server is configured to;

receive data about at least one of a health, an activity or an environment of the user;

analyze, using a user-customized emergency predictive model, the data about at least one of the health, the activity or the environment of the user;

determine, from the analyzed data and using a user-customized emergency predictive model, a score value indicative of a likelihood of an emergency event occurring to the user; and

communicate, responsive to the score value being greater than a threshold, a notification to the user to change behavior to avoid the emergency event.

6. The system of claim 5, wherein one of the mobile device or the server is further configured to detect that the behavior of the user did not change and responsive to the detecting initiating, by one of the mobile device or the server, emergency reporting.

7. The system of claim 6, wherein one of the mobile device or the server is further configured to send responsive to the detection a distress signal to one or more of the following:

emergency contacts of the user, an emergency response service or an ad-hoc safety network created by the user.

8. The system of claim 5, wherein the data comprises contextual data about the user and data from one or more sensors associated with the user.

13. The system of claim 5, wherein the server is further configured to:

provide at least one parameter of the user-customized emergency predictive model to the mobile device.

14. The system of claim 5, wherein the server is configured to:

update one or more parameters of the user-customized emergency predictive model using the received data about at least one of the health, activity or environment of the user.

15. The system of claim 7, wherein the distress signal includes a uniform resource locator (URL).

16. The system of claim 15, wherein access to the URL is limited, via credential authentication, to one or more of the emergency contacts of the user, the emergency response service or the ad-hoc safety network created by the user.