IP Library Granted Patent US 11,496,874
Granted Patent B2
US 11,496,874 · App. 16/365,281 · Granted Nov 8, 2022

Modular emergency communication flow management system

Inventors: Henry Katz (Brookline, MA); Zvika Ferentz (Rye Brook, NY); Jeffrey Sternberg (New York, NY); Nicholas Edward Horelik (Long Island City, NY); Michael John Martin (Long Island City, NY)
Assignee: RAPIDSOS, INC.
H04W4/90H04M3/4217H04M3/5116H04W4/50H04L67/306H04M2203/355
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,496,874
App. No.
16/365,281
Granted
Nov 8, 2022
Kind
B2
Abstract

Disclosed are systems, methods, and media capable of generating and implementing emergency flows. The emergency flow is highly customizable and can connect with various stakeholders (user, emergency contacts, corporate representatives, emergency service provider personnel, etc.). The systems, methods, and media can be triggered in various ways including user input (e.g. voice command) or by sensors (e.g. by using sound detection capabilities).

Claims (28)

1. An emergency management system comprising at least one processor, a memory, a network element, and a computer program including computer-executable instructions that, when executed by the at least one processor, cause the emergency management system to:

(a) provide an emergency trigger program or emergency trigger script configured to be integrated within an application installed on a triggering device, wherein the emergency trigger program or emergency trigger script comprises an emergency flow identifier linked to an emergency flow script configured for an organization and is configured to cause the triggering device to generate and send an emergency alert comprising the emergency flow identifier, a user identifier, and an emergency location in response to detecting an indication of an emergency, wherein the organization is not an emergency service provider, and wherein the emergency flow identifier is not a type of emergency;

(b) receive the emergency alert comprising the emergency flow identifier, the user identifier, and the emergency location sent from the triggering device in response to the triggering device detecting the indication of the emergency;

(c) identify, using the emergency flow identifier, the emergency flow script linked to the emergency flow identifier from an emergency flow database comprising a plurality of emergency flow scripts associated with a plurality of organizations, wherein the emergency flow script is a compilation of programming commands and defines one or more emergency response functions; and

(d) execute the emergency flow script associated with the emergency flow identifier to perform the one or more emergency response functions comprising providing emergency data comprising the user identifier and the emergency location associated with the triggering device to one or more output services.

2. The system of claim 1 , wherein the emergency alert is an application programming interface (API) call comprising the emergency flow identifier within a payload of the API call.

3. The system of claim 1 , wherein execution of the emergency flow script associated with the emergency flow identifier in step (d) further comprises delivering a text-based message to one or more recipients.

4. The system of claim 1 , wherein the indication of the emergency is a selection of a soft or physical button on the triggering device by a user.

5. The system of claim 1 , wherein the indication of the emergency is a voice command.

6. The system of claim 1 , wherein the indication of the emergency comprises sensor data generated by a sensor communicatively coupled to the triggering device.

7. The system of claim 1 , wherein the one or more output services comprises a call center or a public safety answering point (PSAP).

8. The system of claim 1 , wherein the emergency alert comprises a list of emergency contacts for a user associated with the triggering device.

9. The system of claim 1 , wherein the triggering device is a communication device, a wearable device, or an internet of things (IoT) device.

10. The system of claim 1 , wherein the emergency trigger script is an application programming interface (API) script.

11. The system of claim 1 , wherein the organization is a provider of the application installed on the triggering device or a manufacturer of the triggering device.

12. A computer-implemented method for managing emergency flows, the method comprising:

(a) providing an emergency trigger program or emergency trigger script configured to be integrated within an application installed on a triggering device, wherein the emergency trigger program or emergency trigger script comprises an emergency flow identifier linked to an emergency flow script configured for an organization and is configured to cause the triggering device to generate and send an emergency alert comprising the emergency flow identifier, a user identifier, and an emergency location in response to detecting an indication of an emergency, wherein the organization is not an emergency service provider, and wherein the emergency flow identifier is not a type of emergency;

(b) receiving the emergency alert comprising the emergency flow identifier, the user identifier, and the emergency location sent from the triggering device in response to the triggering device detecting the indication of the emergency;

(c) identifying, using the emergency flow identifier, the emergency flow script linked to the emergency flow identifier from an emergency flow database comprising a plurality of emergency flow scripts associated with a plurality of organizations, wherein the emergency flow script is a compilation of programming commands and defines one or more emergency response functions; and

(d) executing the emergency flow script associated with the emergency flow identifier to perform the one or more emergency response functions comprising providing emergency data comprising the user identifier and the emergency location associated with the triggering device to one or more output services.

13. The method of claim 12 , wherein the emergency alert is an application programming interface (API) call comprising the emergency flow identifier within a payload of the API call.

14. The method of claim 12 , wherein executing the emergency flow script associated with the emergency flow identifier in step (d) further comprises delivering a text-based message to one or more recipients.

15. The method of claim 12 , wherein the indication of the emergency is a selection of a soft or physical button on the triggering device by a user.

16. The method of claim 12 , wherein the indication of the emergency is a voice command.

17. The method of claim 12 , wherein the indication of the emergency comprises sensor data generated by a sensor communicatively coupled to the triggering device.

18. The method of claim 12 , wherein the one or more output services comprises a call center or a public safety answering point (PSAP).

19. The method of claim 12 , wherein the emergency alert comprises a list of emergency contacts for a user associated with the triggering device.

20. The method of claim 12 , wherein the triggering device is a communication device, a wearable device, or an internet of things (IoT) device.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 1, 2022
From: KATZ, HENRY; FERENTZ, ZVIKA; STERNBERG, JEFFREY; HORELIK, NICHOLAS EDWARD; MARTIN, MICHAEL JOHN
To: RAPIDSOS, INC.
Reel/Frame 060689/0285 →
Continuity (5)
Continuation 15960384 · Apr 23, 2018
Provisional Application 62614027 · Jan 5, 2018
Provisional Application 62575935 · Oct 23, 2017
Provisional Application 62489373 · Apr 24, 2017
Related Publication 20190327597A1 · Oct 24, 2019
Cited By (4)
US 12,375,895 US 12,425,828 US 12,615,500 US 12,634,670