Emergency Data Manager for VoIP Caller Location Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Emergency networks struggle to accurately determine the location of mobile devices and non-landline devices during emergencies due to the complexity introduced by wireless communication and over-the-top voice-over-Internet-protocol communications, leading to inefficiencies and inaccuracies in call routing and response.

Innovation Solution

An emergency data manager system that independently obtains and provides location data and other emergency data to emergency networks, even during network outages, using a geofence database and multimedia streaming connections to display a map view of mobile device locations, enabling accurate dispatch before call completion.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional PSTN landline telephones are used for emergency calls, then location determination is straightforward and reliable, but the system cannot handle mobile devices and over-the-top communications

Engineering Contradiction:
Improveability to handle diverse communication devicesVSAvoidlocation determination accuracy
Core Design Contradiction:
Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The patent introduces an emergency data manager as an intermediary system that sits between the diverse communication sources (mobile devices, VoIP applications) and the emergency network. This mediator collects location data from various sources including GPS, cell tower triangulation, and Wi-Fi positioning, then standardizes and delivers it to the emergency network, resolving the contradiction between handling diverse devices and maintaining location accuracy

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the location determination function from the call routing function. The emergency data manager independently handles location data collection and processing, while the emergency network focuses on call routing and response. This separation allows each component to optimize for its specific function, improving both adaptability to diverse devices and location determination precision

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If mobile devices with wireless communication are used for emergency calls, then accessibility and mobility are improved, but location determination becomes complex and inaccurate

Engineering Contradiction:
Improveemergency call accessibilityVSAvoidcaller location accuracy
Core Design Contradiction:
Ease of operationVSMeasurement precision

Solution Approach 1:

The emergency data manager acts as a mediator that handles the complexity of mobile location determination. It collects location data from mobile devices using multiple methods (GPS, cell tower triangulation, Wi-Fi positioning), processes and validates this data, then delivers it to the emergency network. This allows mobile devices to remain easily accessible for emergency calls while maintaining location accuracy through sophisticated data collection and processing

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If over-the-top VoIP and messaging applications are used for emergency communications, then communication versatility is improved, but location determination and call routing become challenging

Engineering Contradiction:
Improvecommunication application diversityVSAvoidcall routing and location determination
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The emergency data manager serves as a central intermediary that handles the complexity of diverse communication applications. It receives emergency data from various sources including VoIP applications and messaging services, extracts location information using multiple determination methods, and standardizes the data format for delivery to the emergency network. This mediator approach simplifies the overall system architecture by centralizing the complex location determination and data standardization functions

Inventive Principle:
Principle #24Intermediary (Mediator)

4Loss of time

If emergency networks wait for call completion before obtaining location data, then network resources are conserved, but response time is delayed

Engineering Contradiction:
Improveemergency response timeVSAvoidlocation data availability during network outages
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The system performs preliminary action by obtaining and processing location data independently of the call routing process. The emergency data manager collects and validates location information from mobile devices and emergency data sources before the emergency network needs to respond. This preliminary data collection ensures that location information is ready and available when the emergency network receives the call, even during network outages or when call routing is delayed

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent segments the location data collection process from the call routing process. The emergency data manager independently handles location data acquisition and processing, while the emergency network focuses on receiving and responding to emergency calls. This segmentation allows location data to be prepared in advance without blocking or delaying the call routing process, improving both response time and data availability during network outages

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12604368B2Apparatus and method for obtaining emergency data and providing a map view
Publication Date: 2026.04.14 RAPIDSOS
  • US12604368B2 patent drawing
  • US12604368B2 patent drawing
  • US12604368B2 patent drawing

AI summary

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.