IP Library Granted Patent US 11,558,728
Granted Patent B2
US 11,558,728 · App. 17/143,819 · Granted Jan 17, 2023

Systems and methods for emergency data integration

Inventors: William Pellegrini (Graham, WA); Lucas Richard Eager Leavitt (Forest Hill, NY); BingJun Sy (Flushing, NY); Henry Katz (Brookline, MA); Gabriel Mahoney (Brooklyn, NY); Andrew Hwang (Brooklyn, NY); Zvika Ferentz (Rye Brook, NY); Riccardo Pellegrini (New York, NY); Angela Lynn Orthmeyer (Brooklyn, NY)
Assignee: RAPIDSOS, INC.
H04W4/90G06F16/29G06Q50/265H04W4/021H04W76/15H04W80/06
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,558,728
App. No.
17/143,819
Granted
Jan 17, 2023
Kind
B2
Abstract

A disclosed apparatus obtains emergency data for multiple device types from a plurality of emergency data sources and provides a jurisdictional map view to a plurality of emergency network entities, where each emergency network entity corresponds to a given geographic boundary. The jurisdictional map view corresponds to a respective emergency network entity's geographic boundary. The apparatus determines portions of the emergency data corresponding to emergencies occurring within each respective emergency network entity geographic boundary, and provides location indicators within each respective jurisdictional map view, with each location indicator corresponding to an emergency.

Claims (72)

1. A method comprising:

providing a map view to an emergency network entity from a cloud-based server, the map view corresponding to a geographic area within which emergency calls from mobile devices are routed to the emergency network entity based upon the mobile devices being located within the geographic area;

receiving emergency data related to emergency calls initiating from mobile devices within the geographic area, independently from emergency call routing to the emergency network entity via an internet connection, the mobile devices sending the emergency data comprising hybrid location data to the cloud-based server via mobile device internet connectivity; and

displaying location indicators within the map view at the emergency network entity corresponding to locations of the mobile devices based on the hybrid location data received by the cloud-based server.

2. The method of claim 1 , wherein receiving the emergency data related to emergency calls comprises:

sending the emergency data from the cloud-based server to the emergency network entity prior to establishment of the emergency call to the emergency network entity.

3. The method of claim 1 , further comprising:

sending the emergency data from the cloud-based server to the emergency network entity without requiring the cloud-based server to receive a query from the emergency network entity.

4. The method of claim 3 , further comprising:

displaying the location indicators within the map view corresponding to the locations of the mobile devices, such that each mobile device location indicator is displayed prior to a corresponding emergency call from each mobile device being received by the emergency network entity.

5. The method of claim 1 , further comprising:

displaying the location indicators within the map view corresponding to the locations of the mobile devices, the location indicators selectable to provide access to the emergency data.

6. The method of claim 1 , further comprising:

updating the position of each location indicator within the map view corresponding to movement of each mobile device, such that the location indicators reflect a most recent location of each mobile device.

7. The method of claim 1 , further comprising:

providing the map view within a web browser displayed on a display of the emergency network entity.

8. The method of claim 1 , further comprising:

providing the map view via a software-as-a-service application.

9. The method of claim 1 , further comprising:

obtaining the emergency data from a plurality of emergency data sources.

10. A method comprising:

obtaining emergency data, by a cloud-based server, from a plurality of emergency data sources comprising databases that are external to an emergency network, the emergency data corresponding to mobile devices from which emergency calls have been initiated;

receiving hybrid location data from the mobile devices by the cloud-based server via internet connectivity of the mobile devices, the mobile devices sending the location data upon initiation of emergency calls to the emergency network;

providing a map view by the cloud-based server via a software-as-a-service portal to an emergency network entity of the emergency network; and

providing a location indicator on the map view linked to corresponding emergency data for the mobile devices from which emergency calls have been initiated, the location indicator based on the hybrid location data.

11. The method of claim 10 , further comprising:

providing a call queue via software-as-a-service portal, along with the map view.

12. The method of claim 11 , further comprising:

providing the call queue independently from emergency call routing to the emergency network entity.

13. The method of claim 12 , further comprising:

providing the call queue independently from a computer-aided dispatch system.

14. The method of claim 12 , further comprising:

providing the call queue independently from a call handling system.

15. The method of claim 12 , further comprising:

displaying a mobile device identifier in the call queue, wherein the mobile device identifier is obtained as part of the emergency data, independently from emergency call routing caller identification data.

16. A cloud-based server comprising:

a network component, operative to connect to the Internet;

a processor, operatively coupled to the network component, the processor operative to:

provide a map view to an emergency network entity, the map view corresponding to a geographic area within which emergency calls from mobile devices are routed to the emergency network entity based upon the mobile devices being located within the geographic area;

receive emergency data related to emergency calls initiating from mobile devices within the geographic area, independently from emergency call routing; to the emergency network entity via an internet connection, the mobile devices sending the emergency data comprising hybrid location data to the cloud-based server via mobile device internet connectivity; and

display location indicators within the map view at the emergency network entity corresponding to locations of the mobile devices based on the hybrid location data received by the cloud-based server.

17. The cloud-based server of claim 16 , wherein the processor is further operative to:

display the location indicators within the map view corresponding to the locations of the mobile devices, prior to completion of emergency call routing to the emergency network entity.

18. The cloud-based server of claim 16 , wherein the processor is further operative to:

display the location indicators within the map view corresponding to the locations of the mobile devices, such that each mobile device location indicator is displayed prior to a corresponding emergency call from each mobile device being received by the emergency network entity.

19. The cloud-based server of claim 16 , wherein the processor is further operative to:

display the location indicators within the map view corresponding to the locations of the mobile devices, the location indicators selectable to provide access to the emergency data.

20. The cloud-based server of claim 16 , wherein the processor is further operative to:

update the position of each location indicator within the map view corresponding to movement of each mobile device, such that the location indicators reflect a most recent location of each mobile device.

21. The cloud-based server of claim 16 , wherein the processor is further operative to:

provide the map view within a web browser displayed on a display of the emergency network entity.

22. The cloud-based server of claim 16 , wherein the processor is further operative to:

provide the map view via a software-as-a-service application.

23. The cloud-based server of claim 16 , wherein the processor is further operative to:

obtain the emergency data from a plurality of emergency data sources.

24. An cloud-based server comprising:

a network component, operative to connect to the Internet;

a processor, operatively coupled to the network component, the processor operative to:

obtain emergency data, by the cloud-based server, from a plurality of emergency data sources comprising databases that are external to an emergency network, the emergency data corresponding to mobile devices from which emergency calls have been initiated;

receive hybrid location data from the mobile devices by the cloud-based server via internet connectivity of the mobile devices, the mobile devices sending the location data upon initiation of emergency calls to the emergency network;

provide a map view by the cloud-based server via a software-as-a-service portal to an emergency network entity of the emergency network; and

provide a location indicator on the map view linked to corresponding emergency data for the mobile devices from which emergency calls have been initiated, the location indicator based on the hybrid location data.

25. The cloud-based server of claim 24 , wherein the processor is further operative to:

provide a call queue via software-as-a-service portal, along with the map view.

26. The cloud-based server of claim 25 , wherein the processor is further operative to:

provide the call queue independently from emergency call routing to the emergency network entity.

27. The cloud-based server of claim 26 , wherein the processor is further operative to:

provide the call queue independently from a computer-aided dispatch system.

28. The cloud-based server of claim 24 , wherein the processor is further operative to:

provide the call queue independently from a call handling system.

29. The cloud-based server of claim 24 , wherein the processor is further operative to:

display a mobile device identifier in the call queue, wherein the mobile device identifier is obtained as part of the emergency data, independently from emergency call routing caller identification data.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 1, 2022
From: PELLEGRINI, WILLIAM; LEAVITT, LUCAS RICHARD EAGER; SY, BINGJUN; KATZ, HENRY; MAHONEY, GABRIEL; HWANG, ANDREW; FERENTZ, ZVIKA; PELLEGRINI, RICCARDO; ORTHMEYER, ANGELA LYNN
To: RAPIDSOS, INC.
Reel/Frame 060689/0531 →
Continuity (5)
Continuation 16740207 · Jan 10, 2020
Provisional Application 62946961 · Dec 11, 2019
Provisional Application 62926466 · Oct 26, 2019
Provisional Application 62826680 · Mar 29, 2019
Related Publication 20210266722A1 · Aug 26, 2021
Cited By (6)
US 12,316,806 US 12,323,557 US 12,615,500 US 12,634,670 US 12,695,829 US 12,726,804