# US 12,604,368 B2 · Apparatus and method for obtaining emergency data and providing a map view > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,604,368 B2 - Document ID: US12604368B2 - Status: Granted - Kind: B2 - Application number: 18/440,899 - Filed: 2024-02-13 - Published: 2024-12-26 - Granted: 2026-04-14 - Earliest claimed: 2022-05-10 - Assignees: Rapidsos, Inc. - Applicants: RapidSOS, Inc. - Inventors: Michael John Martin; Nicholas Edward Horelik - Web page: https://patentgrep.com/patent/US12604368B2 ## CPC - H04L 65/1069: Session establishment or de-establishment - H04W 76/50: for emergency connections - H04L 65/1033: Signalling gateways - H04L 65/1104: Session initiation protocol [SIP] - H04L 65/65: Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP] - H04M 3/5116: {for emergency applications} - H04M 3/5183: {Call or contact centers with computer-telephony arrangements} - H04M 11/04: with alarm systems, e.g. fire, police or burglar alarm systems - H04W 4/02: Services making use of location information - H04W 4/021: Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences - H04W 4/025: {using location based information parameters} - H04W 4/90: Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS] - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08) ## Abstract A cloud-based emergency data management system with emergency response logic that has a network component operative to connect to a PSAP (public safety access point) via a local area network connection to the PSAP and to support at least one local connection to a PSAP network entity of the PSAP, and further operative to maintain an Internet Protocol (IP) connection to a cloud-based server; and a processor, operatively coupled to the network component and that is operative to receive voice-over-internet-protocol (VOIP) emergency call data via the local connection to the PSAP network entity. The cloud-based server is operative to: maintain the IP connection with the emergency response logic; and provide a cloud-based application instance to a PSAP workstation via a browser executing on the PSAP workstation; and provide the VoIP emergency call data within a map view of a graphical user interface. ## Claims ### Claim 1 A cloud-based emergency data management system comprising: emergency response logic, comprising: a network component, operative to connect to a PSAP (public safety access point) via a local area network connection to the PSAP and to support a first local connection to a first PSAP network entity of the PSAP, and a second local connection to a second PSAP network entity of the PSAP and further operative to maintain an Internet Protocol (IP) connection to a cloud-based server; and a processor, operatively coupled to the network component, the processor operative to: receive voice-over-internet-protocol (VoIP) emergency call data via the first local connection to the first PSAP network entity; obtain additional metadata from the second local connection to the second PSAP network entity; and the cloud-based server, operative to: maintain the IP connection with the emergency response logic; provide a cloud-based application instance to a PSAP workstation via a browser executing on the PSAP workstation, the application instance having a graphical user interface via the browser and the browser having an IP connection to the cloud-based server; and provide the VoIP emergency call data within a map view of the graphical user interface. ### Claim 2 (depends on 1) The cloud-based emergency data management system of claim 1, wherein the cloud-based server is further operative to: provide location indicators within the map view for VoIP emergency calls related to the VoIP emergency call data. ### Claim 3 (depends on 1) The cloud-based emergency data management system of claim 1, wherein the cloud-server is further operative to: obtain metadata for VOIP emergency calls related to the VoIP emergency call data, independently from the PSAP; aggregate the metadata with the VoIP emergency call data; and provide the VoIP emergency call data aggregated with the metadata to the cloud-based application instance. ### Claim 4 (depends on 1) The cloud-based emergency data management system of claim 1, wherein the cloud-server is further operative to: obtain metadata comprising a mobile device identifier and mobile device hybrid location data for each VoIP emergency calls related to the VoIP emergency call data, independently from the PSAP. ### Claim 5 (depends on 1) The cloud-based emergency data management system of claim 1, wherein the cloud-based server is further operative to: provide an emergency call queue to the cloud-based application instance for VOIP emergency calls related to the additional metadata. ### Claim 6 (depends on 1) The cloud-based emergency data management system of claim 1, wherein the cloud-based server is further operative to: provide an emergency call queue to the cloud-based application instance for VOIP emergency calls related to the VoIP emergency call data and related to the additional metadata wherein the metadata comprises information for emergency calls not included in the VoIP emergency call data. ### Claim 7 (depends on 1) The cloud-based emergency data management system of claim 1, wherein the processor is further operative to: receive the voice-over-internet-protocol (VOIP) emergency call data comprising SIP (session initiation protocol) data. ### Claim 8 (depends on 1) The cloud-based emergency data management system of claim 1, wherein the processor is further operative to: receive the voice-over-internet-protocol (VOIP) emergency call data comprising SIP (session initiation protocol) headers. ### Claim 9 (depends on 1) The cloud-based emergency data management system of claim 1, wherein the cloud-based server is further operative to: provide an emergency call queue to the cloud-based application instance for VoIP emergency calls related to the VoIP emergency call data. ### Claim 10 A method comprising: receiving, by emergency response logic operatively connected to a PSAP, voice-over-internet-protocol (VOIP) emergency call data via a first local connection to a first PSAP network entity; obtaining additional metadata from a second local connection to a second PSAP network entity; maintaining, by a cloud-based server, an IP connection with the emergency response logic; providing, by the cloud-based server, a cloud-based application instance to a PSAP workstation via a browser executing on the PSAP workstation, the application instance having a graphical user interface via the browser and the browser having an IP connection to the cloud-based server; and providing, by the cloud-based server, the VoIP emergency call data within a map view of the graphical user interface. ### Claim 11 (depends on 10) The method of claim 10, further comprising: providing location indicators within the map view for VoIP emergency calls related to the VoIP emergency call data. ### Claim 12 (depends on 10) The method of claim 10, further comprising: obtaining metadata for VoIP emergency calls related to the VoIP emergency call data, independently from the PSAP; aggregating the metadata with the VoIP emergency call data; and providing the VoIP emergency call data aggregated with the metadata to the cloud-based application instance. ### Claim 13 (depends on 10) The method of claim 10, further comprising: obtaining metadata comprising a mobile device identifier and mobile device hybrid location data for each VoIP emergency calls related to the VoIP emergency call data, independently from the PSAP. ### Claim 14 (depends on 10) The method of claim 10, further comprising: providing an emergency call queue to the cloud-based application instance for VoIP emergency calls related to the additional metadata. ### Claim 15 (depends on 10) The method of claim 10, further comprising: providing an emergency call queue to the cloud-based application instance for VoIP emergency calls related to the VOIP emergency call data and related to the additional metadata wherein the metadata comprises information for emergency calls not included in the VoIP emergency call data. ### Claim 16 (depends on 10) The method of claim 10, further comprising: receiving the voice-over-internet-protocol (VOIP) emergency call data comprising SIP (session initiation protocol) data. ### Claim 17 (depends on 10) The method of claim 10, further comprising: receiving the voice-over-internet-protocol (VOIP) emergency call data comprising SIP (session initiation protocol) headers. ### Claim 18 (depends on 10) The method of claim 10, further comprising: providing an emergency call queue to the cloud-based application instance for VOIP emergency calls related to the VoIP emergency call data.